From 01a97a81c5b748ec94841a2cb2331a5e9c756f43 Mon Sep 17 00:00:00 2001
From: OpenStack Proposal Bot <openstack-infra@lists.openstack.org>
Date: Tue, 3 Jun 2014 06:12:12 +0000
Subject: [PATCH] Imported Translations from Transifex

Change-Id: I397b40d7925e539ac1852e5c5402827e789e7be8
---
 .../locale/admin-guide-cloud.pot              | 11436 +--
 doc/cli-reference/locale/cli-reference.pot    |   556 +-
 doc/common/locale/common.pot                  | 46078 +++++------
 doc/common/locale/fr.po                       | 67321 ++++++++--------
 doc/common/locale/ja.po                       | 66991 +++++++--------
 .../locale/config-reference.pot               | 13878 ++--
 doc/glossary/locale/glossary.pot              |    28 +-
 .../locale/high-availability-guide.pot        |  2176 +-
 doc/high-availability-guide/locale/ja.po      |  3254 +-
 doc/image-guide/locale/image-guide.pot        |  1204 +-
 doc/install-guide/locale/install-guide.pot    |  6104 +-
 doc/install-guide/locale/ja.po                | 11715 +--
 doc/security-guide/locale/ja.po               | 14882 ++--
 doc/security-guide/locale/security-guide.pot  |  7944 +-
 .../locale/training-guides.pot                |  8068 +-
 doc/user-guide-admin/locale/ja.po             |  4282 +-
 .../locale/user-guide-admin.pot               |  2800 +-
 doc/user-guide/locale/ja.po                   |  6904 +-
 doc/user-guide/locale/user-guide.pot          |  4688 +-
 19 files changed, 140170 insertions(+), 140139 deletions(-)

diff --git a/doc/admin-guide-cloud/locale/admin-guide-cloud.pot b/doc/admin-guide-cloud/locale/admin-guide-cloud.pot
index a9d4562969..6b817d2934 100644
--- a/doc/admin-guide-cloud/locale/admin-guide-cloud.pot
+++ b/doc/admin-guide-cloud/locale/admin-guide-cloud.pot
@@ -1,7 +1,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2014-06-02 06:10+0000\n"
+"POT-Creation-Date: 2014-06-03 06:11+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -9,6 +9,391 @@ msgstr ""
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
+#. ... Based on a blog, should be replaced with original material...
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:7(title)
+msgid "Object Storage monitoring"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:9(para)
+msgid "Excerpted from a blog post by <link href=\"http://swiftstack.com/blog/2012/04/11/swift-monitoring-with-statsd\">Darrell Bishop</link>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:12(para)
+msgid "An OpenStack Object Storage cluster is a collection of many daemons that work together across many nodes. With so many different components, you must be able to tell what is going on inside the cluster. Tracking server-level metrics like CPU utilization, load, memory consumption, disk usage and utilization, and so on is necessary, but not sufficient."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:19(para)
+msgid "What are different daemons are doing on each server? What is the volume of object replication on node8? How long is it taking? Are there errors? If so, when did they happen?"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:22(para)
+msgid "In such a complex ecosystem, you can use multiple approaches to get the answers to these questions. This section describes several approaches."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:26(title)
+msgid "Swift Recon"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:27(para)
+msgid "The Swift Recon middleware (see <link href=\"http://swift.openstack.org/admin_guide.html#cluster-telemetry-and-monitoring\">http://swift.openstack.org/admin_guide.html#cluster-telemetry-and-monitoring</link>) provides general machine statistics, such as load average, socket statistics, <code>/proc/meminfo</code> contents, and so on, as well as Swift-specific metrics:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:35(para)
+msgid "The MD5 sum of each ring file."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:38(para)
+msgid "The most recent object replication time."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:41(para)
+msgid "Count of each type of quarantined file: Account, container, or object."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:45(para)
+msgid "Count of “async_pendings” (deferred container updates) on disk."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:49(para)
+msgid "Swift Recon is middleware that is installed in the object servers pipeline and takes one required option: A local cache directory. To track <literal>async_pendings</literal>, you must set up an additional cron job for each object server. You access data by either sending HTTP requests directly to the object server or using the <placeholder-1/> command-line client."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:57(para)
+msgid "There are some good Object Storage cluster statistics but the general server metrics overlap with existing server monitoring systems. To get the Swift-specific metrics into a monitoring system, they must be polled. Swift Recon essentially acts as a middleware metrics collector. The process that feeds metrics to your statistics system, such as <literal>collectd</literal> and <literal>gmond</literal>, probably already runs on the storage node. So, you can choose to either talk to Swift Recon or collect the metrics directly."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:69(title)
+msgid "Swift-Informant"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:70(para)
+msgid "Florian Hines developed the Swift-Informant middleware (see <link href=\"http://pandemicsyn.posterous.com/swift-informant-statsd-getting-realtime-telem\">http://pandemicsyn.posterous.com/swift-informant-statsd-getting-realtime-telem</link>) to get real-time visibility into Object Storage client requests. It sits in the pipeline for the proxy server, and after each request to the proxy server, sends three metrics to a StatsD server (see <link href=\"http://codeascraft.etsy.com/2011/02/15/measure-anything-measure-everything/\">http://codeascraft.etsy.com/2011/02/15/measure-anything-measure-everything/</link>):"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:82(para)
+msgid "A counter increment for a metric like <code>obj.GET.200</code> or <code>cont.PUT.404</code>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:87(para)
+msgid "Timing data for a metric like <code>acct.GET.200</code> or <code>obj.GET.200</code>. [The README says the metrics look like <code>duration.acct.GET.200</code>, but I do not see the <literal>duration</literal> in the code. I am not sure what the Etsy server does but our StatsD server turns timing metrics into five derivative metrics with new segments appended, so it probably works as coded. The first metric turns into <code>acct.GET.200.lower</code>, <code>acct.GET.200.upper</code>, <code>acct.GET.200.mean</code>, <code>acct.GET.200.upper_90</code>, and <code>acct.GET.200.count</code>]."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:104(para)
+msgid "A counter increase by the bytes transferred for a metric like <code>tfer.obj.PUT.201</code>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:109(para)
+msgid "This is good for getting a feel for the quality of service clients are experiencing with the timing metrics, as well as getting a feel for the volume of the various permutations of request server type, command, and response code. Swift-Informant also requires no change to core Object Storage code because it is implemented as middleware. However, it gives you no insight into the workings of the cluster past the proxy server. If the responsiveness of one storage node degrades, you can only see that some of your requests are bad, either as high latency or error status codes. You do not know exactly why or where that request tried to go. Maybe the container server in question was on a good node but the object server was on a different, poorly-performing node."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:125(title)
+msgid "Statsdlog"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:126(para)
+msgid "Florian’s <link href=\"https://github.com/pandemicsyn/statsdlog\">Statsdlog</link> project increments StatsD counters based on logged events. Like Swift-Informant, it is also non-intrusive, but statsdlog can track events from all Object Storage daemons, not just proxy-server. The daemon listens to a UDP stream of syslog messages and StatsD counters are incremented when a log line matches a regular expression. Metric names are mapped to regex match patterns in a JSON file, allowing flexible configuration of what metrics are extracted from the log stream."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:137(para)
+msgid "Currently, only the first matching regex triggers a StatsD counter increment, and the counter is always incremented by one. There is no way to increment a counter by more than one or send timing data to StatsD based on the log line content. The tool could be extended to handle more metrics for each line and data extraction, including timing data. But a coupling would still exist between the log textual format and the log parsing regexes, which would themselves be more complex to support multiple matches for each line and data extraction. Also, log processing introduces a delay between the triggering event and sending the data to StatsD. It would be preferable to increment error counters where they occur and send timing data as soon as it is known to avoid coupling between a log string and a parsing regex and prevent a time delay between events and sending data to StatsD."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:153(para)
+msgid "The next section describes another method for gathering Object Storage operational metrics."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:157(title)
+msgid "Swift StatsD logging"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:158(para)
+msgid "StatsD (see <link href=\"http://codeascraft.etsy.com/2011/02/15/measure-anything-measure-everything/\">http://codeascraft.etsy.com/2011/02/15/measure-anything-measure-everything/</link>) was designed for application code to be deeply instrumented; metrics are sent in real-time by the code that just noticed or did something. The overhead of sending a metric is extremely low: a <code>sendto</code> of one UDP packet. If that overhead is still too high, the StatsD client library can send only a random portion of samples and StatsD approximates the actual number when flushing metrics upstream."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:169(para)
+msgid "To avoid the problems inherent with middleware-based monitoring and after-the-fact log processing, the sending of StatsD metrics is integrated into Object Storage itself. The submitted change set (see <link href=\"https://review.openstack.org/#change,6058\">https://review.openstack.org/#change,6058</link>) currently reports 124 metrics across 15 Object Storage daemons and the tempauth middleware. Details of the metrics tracked are in the <link href=\"http://docs.openstack.org/developer/swift/admin_guide.html\">Administrator's Guide</link>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:180(para)
+msgid "The sending of metrics is integrated with the logging framework. To enable, configure <code>log_statsd_host</code> in the relevant config file. You can also specify the port and a default sample rate. The specified default sample rate is used unless a specific call to a statsd logging method (see the list below) overrides it. Currently, no logging calls override the sample rate, but it is conceivable that some metrics may require accuracy (sample_rate == 1) while others may not."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:195(para)
+msgid "Then the LogAdapter object returned by <code>get_logger()</code>, usually stored in <code>self.logger</code>, has these new methods:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:201(para)
+msgid "<code>set_statsd_prefix(self, prefix)</code> Sets the client library stat prefix value which gets prefixed to every metric. The default prefix is the “name” of the logger (such as, . “object-server”, “container-auditor”, etc.). This is currently used to turn “proxy-server” into one of “proxy-server.Account”, “proxy-server.Container”, or “proxy-server.Object” as soon as the Controller object is determined and instantiated for the request."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:213(para)
+msgid "<code>update_stats(self, metric, amount, sample_rate=1)</code> Increments the supplied metric by the given amount. This is used when you need to add or subtract more that one from a counter, like incrementing “suffix.hashes” by the number of computed hashes in the object replicator."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:222(para)
+msgid "<code>increment(self, metric, sample_rate=1)</code> Increments the given counter metric by one."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:227(para)
+msgid "<code>decrement(self, metric, sample_rate=1)</code> Lowers the given counter metric by one."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:232(para)
+msgid "<code>timing(self, metric, timing_ms, sample_rate=1)</code> Record that the given metric took the supplied number of milliseconds."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:238(para)
+msgid "<code>timing_since(self, metric, orig_time, sample_rate=1)</code> Convenience method to record a timing metric whose value is “now” minus an existing timestamp."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:244(para)
+msgid "Note that these logging methods may safely be called anywhere you have a logger object. If StatsD logging has not been configured, the methods are no-ops. This avoids messy conditional logic each place a metric is recorded. These example usages show the new logging methods:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:287(para)
+msgid "The development team of StatsD wanted to use the <link href=\"https://github.com/sivy/py-statsd\">pystatsd</link> client library (not to be confused with a <link href=\"https://github.com/sivy/py-statsd\">similar-looking project</link> also hosted on GitHub), but the released version on PyPi was missing two desired features the latest version in GitHub had: the ability to configure a metrics prefix in the client object and a convenience method for sending timing data between “now” and a “start” timestamp you already have. So they just implemented a simple StatsD client library from scratch with the same interface. This has the nice fringe benefit of not introducing another external library dependency into Object Storage."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-admin.xml:6(title)
+msgid "System administration for Object Storage"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-admin.xml:7(para)
+msgid "By understanding Object Storage concepts, you can better monitor and administer your storage solution. The majority of the administration information is maintained in developer documentation at <link href=\"http://docs.openstack.org/developer/swift/\">docs.openstack.org/developer/swift/</link>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/section_object-storage-admin.xml:13(para)
+msgid "See the <link href=\"http://docs.openstack.org/icehouse/config-reference/content/\"><citetitle>OpenStack Configuration Reference</citetitle></link> for a list of configuration options for Object Storage."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_dashboard.xml:6(title) ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:109(title)
+msgid "Dashboard"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_dashboard.xml:7(para)
+msgid "The OpenStack dashboard is a web-based interface that allows you to manage OpenStack resources and services. The dashboard allows you to interact with the OpenStack Compute cloud controller using the OpenStack APIs. For more information about installing and configuring the dashboard, see the <citetitle>OpenStack Installation Guide</citetitle> for your operating system."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_dashboard.xml:19(para)
+msgid "<xref linkend=\"dashboard-custom-brand\"/>, for customizing the dashboard."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_dashboard.xml:23(para)
+msgid "<xref linkend=\"dashboard-sessions\"/>, for setting up session storage for the dashboard."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_dashboard.xml:27(para)
+msgid "The <link href=\"http://docs.openstack.org/developer/horizon/topics/deployment.html\"> Horizon documentation</link>, for deploying the dashboard."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_dashboard.xml:31(para)
+msgid "The <link href=\"http://docs.openstack.org/user-guide/content/\"><citetitle>OpenStack End User Guide</citetitle></link>, for launching instances with the dashboard.."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_dashboard.xml:15(para)
+msgid "For more information about using the dashboard, see: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_objectstorage.xml:6(title)
+msgid "Object Storage"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_blockstorage.xml:10(title)
+msgid "Block Storage"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_blockstorage.xml:11(para)
+msgid "The OpenStack Block Storage service works through the interaction of a series of daemon processes named <systemitem class=\"daemon\">cinder-*</systemitem> that reside persistently on the host machine or machines. The binaries can all be run from a single node, or spread across multiple nodes. They can also be run on the same node as other OpenStack services."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_blockstorage.xml:19(title)
+msgid "Introduction to Block Storage"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_blockstorage.xml:20(para)
+msgid "To administer the OpenStack Block Storage service, it is helpful to understand a number of concepts. You must make certain choices when you configure the Block Storage service in OpenStack. The bulk of the options come down to two choices, single node or multi-node install. You can read a longer discussion about storage decisions in <link href=\"http://docs.openstack.org/trunk/openstack-ops/content/storage_decision.html\">Storage Decisions</link> in the <citetitle>OpenStack Operations Guide</citetitle>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_blockstorage.xml:29(para)
+msgid "OpenStack Block Storage enables you to add extra block-level storage to your OpenStack Compute instances. This service is similar to the Amazon EC2 Elastic Block Storage (EBS) offering."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_blockstorage.xml:37(title)
+msgid "Manage volumes"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_blockstorage.xml:38(para)
+msgid "The default OpenStack Block Storage service implementation is an iSCSI solution that uses Logical Volume Manager (LVM) for Linux."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_blockstorage.xml:42(para)
+msgid "The OpenStack Block Storage service is not a shared storage solution like a Storage Area Network (SAN) of NFS volumes, where you can attach a volume to multiple servers. With the OpenStack Block Storage service, you can attach a volume to only one instance at a time."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_blockstorage.xml:48(para)
+msgid "The OpenStack Block Storage service also provides drivers that enable you to use several vendors' back-end storage devices, in addition to or instead of the base LVM implementation."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_blockstorage.xml:53(para)
+msgid "This high-level procedure shows you how to create and attach a volume to a server instance."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_blockstorage.xml:57(para)
+msgid "You must configure both OpenStack Compute and the OpenStack Block Storage service through the <filename>cinder.conf</filename> file."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_blockstorage.xml:62(para)
+msgid "Create a volume through the <placeholder-1/> command. This command creates an LV into the volume group (VG) <literal>cinder-volumes</literal>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_blockstorage.xml:68(para)
+msgid "Attach the volume to an instance through the <placeholder-1/> command. This command creates a unique iSCSI IQN that is exposed to the compute node."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_blockstorage.xml:74(para)
+msgid "The compute node, which runs the instance, now has an active ISCSI session and new local storage (usually a <filename>/dev/sdX</filename> disk)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_blockstorage.xml:81(para)
+msgid "libvirt uses that local storage as storage for the instance. The instance gets a new disk (usually a <filename>/dev/vdX</filename> disk)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_blockstorage.xml:90(para)
+msgid "For this particular walk through, one cloud controller runs <systemitem class=\"service\">nova-api</systemitem>, <systemitem class=\"service\">nova-scheduler</systemitem>, <systemitem class=\"service\">nova-objectstore</systemitem>, <literal>nova-network</literal> and <literal>cinder-*</literal> services. Two additional compute nodes run <systemitem class=\"service\">nova-compute</systemitem>. The walk through uses a custom partitioning scheme that carves out 60GB of space and labels it as LVM. The network uses the FlatManager and NetworkManager settings for OpenStack Compute."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_blockstorage.xml:104(para)
+msgid "The network mode does not interfere with the way cinder works, but you must set up networking for cinder to work. For details, see <xref linkend=\"ch_networking\"/>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_blockstorage.xml:107(para)
+msgid "To set up Compute to use volumes, ensure that Block Storage is installed along with <package>lvm2</package>. This guide describes how to troubleshoot your installation and back up your Compute volumes."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_blockstorage.xml:113(title)
+msgid "Boot from volume"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_blockstorage.xml:114(para)
+msgid "In some cases, instances can be stored and run from inside volumes. For information, see the <link href=\"http://docs.openstack.org/user-guide/content/boot_from_volume.html\">Launch an instance from a volume</link> section in the <link href=\"http://docs.openstack.org/user-guide/content/\"><citetitle>OpenStack End User Guide</citetitle></link>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_blockstorage.xml:134(title)
+msgid "Troubleshoot your installation"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_blockstorage.xml:135(para)
+msgid "This section provides useful tips to help troubleshoot your Block Storage installation."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_networking.xml:6(title)
+msgid "Networking"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/ch_networking.xml:7(para)
+msgid "Learn OpenStack Networking concepts, architecture, and basic and advanced <placeholder-1/> and <placeholder-2/> command-line interface (CLI) commands."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:7(title)
+msgid "OpenStack Cloud Administrator Guide"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:9(titleabbrev)
+msgid "Cloud Administrator Guide"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:17(orgname) ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:23(holder)
+msgid "OpenStack Foundation"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:21(year)
+msgid "2013"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:22(year)
+msgid "2014"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:25(releaseinfo)
+msgid "current"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:26(productname)
+msgid "OpenStack"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:30(remark)
+msgid "Copyright details are filled in by the template."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:36(remark)
+msgid "Remaining licensing details are filled in by the template."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:41(para)
+msgid "OpenStack offers open source software for cloud administrators to manage and troubleshoot an OpenStack cloud."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:48(date)
+msgid "2014-04-17"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:52(para)
+msgid "For the Icehouse release, the guide was organized with system administration and system architecture sections. Also, how-to sections were moved to this guide instead of the <citetitle>OpenStack Configuration Reference</citetitle>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:65(date)
+msgid "2013-11-12"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:69(para)
+msgid "Adds options for tuning operational status synchronization in the NSX plug-in."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:77(date)
+msgid "2013-10-17"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:81(para)
+msgid "Havana release."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:87(date)
+msgid "2013-09-05"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:91(para)
+msgid "Moves object storage monitoring section to this guide."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:95(para)
+msgid "Removes redundant object storage information."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:102(date)
+msgid "2013-09-03"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:106(para)
+msgid "Moved all but configuration and installation information from these component guides to create the new guide:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:112(para)
+msgid "OpenStack Compute Administration Guide"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:116(para)
+msgid "OpenStack Networking Administration Guide"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:120(para)
+msgid "OpenStack Object Storage Administration Guide"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:124(para)
+msgid "OpenStack Block Storage Service Administration Guide"
+msgstr ""
+
 #: ./doc/admin-guide-cloud/ch_identity_mgmt.xml:6(title)
 msgid "Identity management"
 msgstr ""
@@ -237,391 +622,6 @@ msgstr ""
 msgid "A clean installation could start with the standard policy file, to allow creation of the admin_domain with the first users within it. You could then obtain the domain_id of the admin domain, paste the ID into a modified version of <filename>policy.v3cloudsample.json</filename>, and then enable it as the main policy file."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/ch_blockstorage.xml:10(title)
-msgid "Block Storage"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_blockstorage.xml:11(para)
-msgid "The OpenStack Block Storage service works through the interaction of a series of daemon processes named <systemitem class=\"daemon\">cinder-*</systemitem> that reside persistently on the host machine or machines. The binaries can all be run from a single node, or spread across multiple nodes. They can also be run on the same node as other OpenStack services."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_blockstorage.xml:19(title)
-msgid "Introduction to Block Storage"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_blockstorage.xml:20(para)
-msgid "To administer the OpenStack Block Storage service, it is helpful to understand a number of concepts. You must make certain choices when you configure the Block Storage service in OpenStack. The bulk of the options come down to two choices, single node or multi-node install. You can read a longer discussion about storage decisions in <link href=\"http://docs.openstack.org/trunk/openstack-ops/content/storage_decision.html\">Storage Decisions</link> in the <citetitle>OpenStack Operations Guide</citetitle>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_blockstorage.xml:29(para)
-msgid "OpenStack Block Storage enables you to add extra block-level storage to your OpenStack Compute instances. This service is similar to the Amazon EC2 Elastic Block Storage (EBS) offering."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_blockstorage.xml:37(title)
-msgid "Manage volumes"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_blockstorage.xml:38(para)
-msgid "The default OpenStack Block Storage service implementation is an iSCSI solution that uses Logical Volume Manager (LVM) for Linux."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_blockstorage.xml:42(para)
-msgid "The OpenStack Block Storage service is not a shared storage solution like a Storage Area Network (SAN) of NFS volumes, where you can attach a volume to multiple servers. With the OpenStack Block Storage service, you can attach a volume to only one instance at a time."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_blockstorage.xml:48(para)
-msgid "The OpenStack Block Storage service also provides drivers that enable you to use several vendors' back-end storage devices, in addition to or instead of the base LVM implementation."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_blockstorage.xml:53(para)
-msgid "This high-level procedure shows you how to create and attach a volume to a server instance."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_blockstorage.xml:57(para)
-msgid "You must configure both OpenStack Compute and the OpenStack Block Storage service through the <filename>cinder.conf</filename> file."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_blockstorage.xml:62(para)
-msgid "Create a volume through the <placeholder-1/> command. This command creates an LV into the volume group (VG) <literal>cinder-volumes</literal>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_blockstorage.xml:68(para)
-msgid "Attach the volume to an instance through the <placeholder-1/> command. This command creates a unique iSCSI IQN that is exposed to the compute node."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_blockstorage.xml:74(para)
-msgid "The compute node, which runs the instance, now has an active ISCSI session and new local storage (usually a <filename>/dev/sdX</filename> disk)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_blockstorage.xml:81(para)
-msgid "libvirt uses that local storage as storage for the instance. The instance gets a new disk (usually a <filename>/dev/vdX</filename> disk)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_blockstorage.xml:90(para)
-msgid "For this particular walk through, one cloud controller runs <systemitem class=\"service\">nova-api</systemitem>, <systemitem class=\"service\">nova-scheduler</systemitem>, <systemitem class=\"service\">nova-objectstore</systemitem>, <literal>nova-network</literal> and <literal>cinder-*</literal> services. Two additional compute nodes run <systemitem class=\"service\">nova-compute</systemitem>. The walk through uses a custom partitioning scheme that carves out 60GB of space and labels it as LVM. The network uses the FlatManager and NetworkManager settings for OpenStack Compute."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_blockstorage.xml:104(para)
-msgid "The network mode does not interfere with the way cinder works, but you must set up networking for cinder to work. For details, see <xref linkend=\"ch_networking\"/>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_blockstorage.xml:107(para)
-msgid "To set up Compute to use volumes, ensure that Block Storage is installed along with <package>lvm2</package>. This guide describes how to troubleshoot your installation and back up your Compute volumes."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_blockstorage.xml:113(title)
-msgid "Boot from volume"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_blockstorage.xml:114(para)
-msgid "In some cases, instances can be stored and run from inside volumes. For information, see the <link href=\"http://docs.openstack.org/user-guide/content/boot_from_volume.html\">Launch an instance from a volume</link> section in the <link href=\"http://docs.openstack.org/user-guide/content/\"><citetitle>OpenStack End User Guide</citetitle></link>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_blockstorage.xml:134(title)
-msgid "Troubleshoot your installation"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_blockstorage.xml:135(para)
-msgid "This section provides useful tips to help troubleshoot your Block Storage installation."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-admin.xml:6(title)
-msgid "System administration for Object Storage"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-admin.xml:7(para)
-msgid "By understanding Object Storage concepts, you can better monitor and administer your storage solution. The majority of the administration information is maintained in developer documentation at <link href=\"http://docs.openstack.org/developer/swift/\">docs.openstack.org/developer/swift/</link>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-admin.xml:13(para)
-msgid "See the <link href=\"http://docs.openstack.org/icehouse/config-reference/content/\"><citetitle>OpenStack Configuration Reference</citetitle></link> for a list of configuration options for Object Storage."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_objectstorage.xml:6(title)
-msgid "Object Storage"
-msgstr ""
-
-#. ... Based on a blog, should be replaced with original material...
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:7(title)
-msgid "Object Storage monitoring"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:9(para)
-msgid "Excerpted from a blog post by <link href=\"http://swiftstack.com/blog/2012/04/11/swift-monitoring-with-statsd\">Darrell Bishop</link>"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:12(para)
-msgid "An OpenStack Object Storage cluster is a collection of many daemons that work together across many nodes. With so many different components, you must be able to tell what is going on inside the cluster. Tracking server-level metrics like CPU utilization, load, memory consumption, disk usage and utilization, and so on is necessary, but not sufficient."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:19(para)
-msgid "What are different daemons are doing on each server? What is the volume of object replication on node8? How long is it taking? Are there errors? If so, when did they happen?"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:22(para)
-msgid "In such a complex ecosystem, you can use multiple approaches to get the answers to these questions. This section describes several approaches."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:26(title)
-msgid "Swift Recon"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:27(para)
-msgid "The Swift Recon middleware (see <link href=\"http://swift.openstack.org/admin_guide.html#cluster-telemetry-and-monitoring\">http://swift.openstack.org/admin_guide.html#cluster-telemetry-and-monitoring</link>) provides general machine statistics, such as load average, socket statistics, <code>/proc/meminfo</code> contents, and so on, as well as Swift-specific metrics:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:35(para)
-msgid "The MD5 sum of each ring file."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:38(para)
-msgid "The most recent object replication time."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:41(para)
-msgid "Count of each type of quarantined file: Account, container, or object."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:45(para)
-msgid "Count of “async_pendings” (deferred container updates) on disk."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:49(para)
-msgid "Swift Recon is middleware that is installed in the object servers pipeline and takes one required option: A local cache directory. To track <literal>async_pendings</literal>, you must set up an additional cron job for each object server. You access data by either sending HTTP requests directly to the object server or using the <placeholder-1/> command-line client."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:57(para)
-msgid "There are some good Object Storage cluster statistics but the general server metrics overlap with existing server monitoring systems. To get the Swift-specific metrics into a monitoring system, they must be polled. Swift Recon essentially acts as a middleware metrics collector. The process that feeds metrics to your statistics system, such as <literal>collectd</literal> and <literal>gmond</literal>, probably already runs on the storage node. So, you can choose to either talk to Swift Recon or collect the metrics directly."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:69(title)
-msgid "Swift-Informant"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:70(para)
-msgid "Florian Hines developed the Swift-Informant middleware (see <link href=\"http://pandemicsyn.posterous.com/swift-informant-statsd-getting-realtime-telem\">http://pandemicsyn.posterous.com/swift-informant-statsd-getting-realtime-telem</link>) to get real-time visibility into Object Storage client requests. It sits in the pipeline for the proxy server, and after each request to the proxy server, sends three metrics to a StatsD server (see <link href=\"http://codeascraft.etsy.com/2011/02/15/measure-anything-measure-everything/\">http://codeascraft.etsy.com/2011/02/15/measure-anything-measure-everything/</link>):"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:82(para)
-msgid "A counter increment for a metric like <code>obj.GET.200</code> or <code>cont.PUT.404</code>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:87(para)
-msgid "Timing data for a metric like <code>acct.GET.200</code> or <code>obj.GET.200</code>. [The README says the metrics look like <code>duration.acct.GET.200</code>, but I do not see the <literal>duration</literal> in the code. I am not sure what the Etsy server does but our StatsD server turns timing metrics into five derivative metrics with new segments appended, so it probably works as coded. The first metric turns into <code>acct.GET.200.lower</code>, <code>acct.GET.200.upper</code>, <code>acct.GET.200.mean</code>, <code>acct.GET.200.upper_90</code>, and <code>acct.GET.200.count</code>]."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:104(para)
-msgid "A counter increase by the bytes transferred for a metric like <code>tfer.obj.PUT.201</code>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:109(para)
-msgid "This is good for getting a feel for the quality of service clients are experiencing with the timing metrics, as well as getting a feel for the volume of the various permutations of request server type, command, and response code. Swift-Informant also requires no change to core Object Storage code because it is implemented as middleware. However, it gives you no insight into the workings of the cluster past the proxy server. If the responsiveness of one storage node degrades, you can only see that some of your requests are bad, either as high latency or error status codes. You do not know exactly why or where that request tried to go. Maybe the container server in question was on a good node but the object server was on a different, poorly-performing node."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:125(title)
-msgid "Statsdlog"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:126(para)
-msgid "Florian’s <link href=\"https://github.com/pandemicsyn/statsdlog\">Statsdlog</link> project increments StatsD counters based on logged events. Like Swift-Informant, it is also non-intrusive, but statsdlog can track events from all Object Storage daemons, not just proxy-server. The daemon listens to a UDP stream of syslog messages and StatsD counters are incremented when a log line matches a regular expression. Metric names are mapped to regex match patterns in a JSON file, allowing flexible configuration of what metrics are extracted from the log stream."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:137(para)
-msgid "Currently, only the first matching regex triggers a StatsD counter increment, and the counter is always incremented by one. There is no way to increment a counter by more than one or send timing data to StatsD based on the log line content. The tool could be extended to handle more metrics for each line and data extraction, including timing data. But a coupling would still exist between the log textual format and the log parsing regexes, which would themselves be more complex to support multiple matches for each line and data extraction. Also, log processing introduces a delay between the triggering event and sending the data to StatsD. It would be preferable to increment error counters where they occur and send timing data as soon as it is known to avoid coupling between a log string and a parsing regex and prevent a time delay between events and sending data to StatsD."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:153(para)
-msgid "The next section describes another method for gathering Object Storage operational metrics."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:157(title)
-msgid "Swift StatsD logging"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:158(para)
-msgid "StatsD (see <link href=\"http://codeascraft.etsy.com/2011/02/15/measure-anything-measure-everything/\">http://codeascraft.etsy.com/2011/02/15/measure-anything-measure-everything/</link>) was designed for application code to be deeply instrumented; metrics are sent in real-time by the code that just noticed or did something. The overhead of sending a metric is extremely low: a <code>sendto</code> of one UDP packet. If that overhead is still too high, the StatsD client library can send only a random portion of samples and StatsD approximates the actual number when flushing metrics upstream."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:169(para)
-msgid "To avoid the problems inherent with middleware-based monitoring and after-the-fact log processing, the sending of StatsD metrics is integrated into Object Storage itself. The submitted change set (see <link href=\"https://review.openstack.org/#change,6058\">https://review.openstack.org/#change,6058</link>) currently reports 124 metrics across 15 Object Storage daemons and the tempauth middleware. Details of the metrics tracked are in the <link href=\"http://docs.openstack.org/developer/swift/admin_guide.html\">Administrator's Guide</link>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:180(para)
-msgid "The sending of metrics is integrated with the logging framework. To enable, configure <code>log_statsd_host</code> in the relevant config file. You can also specify the port and a default sample rate. The specified default sample rate is used unless a specific call to a statsd logging method (see the list below) overrides it. Currently, no logging calls override the sample rate, but it is conceivable that some metrics may require accuracy (sample_rate == 1) while others may not."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:195(para)
-msgid "Then the LogAdapter object returned by <code>get_logger()</code>, usually stored in <code>self.logger</code>, has these new methods:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:201(para)
-msgid "<code>set_statsd_prefix(self, prefix)</code> Sets the client library stat prefix value which gets prefixed to every metric. The default prefix is the “name” of the logger (such as, . “object-server”, “container-auditor”, etc.). This is currently used to turn “proxy-server” into one of “proxy-server.Account”, “proxy-server.Container”, or “proxy-server.Object” as soon as the Controller object is determined and instantiated for the request."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:213(para)
-msgid "<code>update_stats(self, metric, amount, sample_rate=1)</code> Increments the supplied metric by the given amount. This is used when you need to add or subtract more that one from a counter, like incrementing “suffix.hashes” by the number of computed hashes in the object replicator."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:222(para)
-msgid "<code>increment(self, metric, sample_rate=1)</code> Increments the given counter metric by one."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:227(para)
-msgid "<code>decrement(self, metric, sample_rate=1)</code> Lowers the given counter metric by one."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:232(para)
-msgid "<code>timing(self, metric, timing_ms, sample_rate=1)</code> Record that the given metric took the supplied number of milliseconds."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:238(para)
-msgid "<code>timing_since(self, metric, orig_time, sample_rate=1)</code> Convenience method to record a timing metric whose value is “now” minus an existing timestamp."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:244(para)
-msgid "Note that these logging methods may safely be called anywhere you have a logger object. If StatsD logging has not been configured, the methods are no-ops. This avoids messy conditional logic each place a metric is recorded. These example usages show the new logging methods:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/section_object-storage-monitoring.xml:287(para)
-msgid "The development team of StatsD wanted to use the <link href=\"https://github.com/sivy/py-statsd\">pystatsd</link> client library (not to be confused with a <link href=\"https://github.com/sivy/py-statsd\">similar-looking project</link> also hosted on GitHub), but the released version on PyPi was missing two desired features the latest version in GitHub had: the ability to configure a metrics prefix in the client object and a convenience method for sending timing data between “now” and a “start” timestamp you already have. So they just implemented a simple StatsD client library from scratch with the same interface. This has the nice fringe benefit of not introducing another external library dependency into Object Storage."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_networking.xml:6(title)
-msgid "Networking"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_networking.xml:7(para)
-msgid "Learn OpenStack Networking concepts, architecture, and basic and advanced <placeholder-1/> and <placeholder-2/> command-line interface (CLI) commands."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:7(title)
-msgid "OpenStack Cloud Administrator Guide"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:9(titleabbrev)
-msgid "Cloud Administrator Guide"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:17(orgname) ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:23(holder)
-msgid "OpenStack Foundation"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:21(year)
-msgid "2013"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:22(year)
-msgid "2014"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:25(releaseinfo)
-msgid "current"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:26(productname)
-msgid "OpenStack"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:30(remark)
-msgid "Copyright details are filled in by the template."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:36(remark)
-msgid "Remaining licensing details are filled in by the template."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:41(para)
-msgid "OpenStack offers open source software for cloud administrators to manage and troubleshoot an OpenStack cloud."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:48(date)
-msgid "2014-04-17"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:52(para)
-msgid "For the Icehouse release, the guide was organized with system administration and system architecture sections. Also, how-to sections were moved to this guide instead of the <citetitle>OpenStack Configuration Reference</citetitle>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:65(date)
-msgid "2013-11-12"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:69(para)
-msgid "Adds options for tuning operational status synchronization in the NSX plug-in."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:77(date)
-msgid "2013-10-17"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:81(para)
-msgid "Havana release."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:87(date)
-msgid "2013-09-05"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:91(para)
-msgid "Moves object storage monitoring section to this guide."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:95(para)
-msgid "Removes redundant object storage information."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:102(date)
-msgid "2013-09-03"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:106(para)
-msgid "Moved all but configuration and installation information from these component guides to create the new guide:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:112(para)
-msgid "OpenStack Compute Administration Guide"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:116(para)
-msgid "OpenStack Networking Administration Guide"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:120(para)
-msgid "OpenStack Object Storage Administration Guide"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/bk-admin-guide-cloud.xml:124(para)
-msgid "OpenStack Block Storage Service Administration Guide"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_dashboard.xml:6(title) ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:109(title)
-msgid "Dashboard"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_dashboard.xml:7(para)
-msgid "The OpenStack dashboard is a web-based interface that allows you to manage OpenStack resources and services. The dashboard allows you to interact with the OpenStack Compute cloud controller using the OpenStack APIs. For more information about installing and configuring the dashboard, see the <citetitle>OpenStack Installation Guide</citetitle> for your operating system."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_dashboard.xml:19(para)
-msgid "<xref linkend=\"dashboard-custom-brand\"/>, for customizing the dashboard."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_dashboard.xml:23(para)
-msgid "<xref linkend=\"dashboard-sessions\"/>, for setting up session storage for the dashboard."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_dashboard.xml:27(para)
-msgid "The <link href=\"http://docs.openstack.org/developer/horizon/topics/deployment.html\"> Horizon documentation</link>, for deploying the dashboard."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_dashboard.xml:31(para)
-msgid "The <link href=\"http://docs.openstack.org/user-guide/content/\"><citetitle>OpenStack End User Guide</citetitle></link>, for launching instances with the dashboard.."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/ch_dashboard.xml:15(para)
-msgid "For more information about using the dashboard, see: <placeholder-1/>"
-msgstr ""
-
 #: ./doc/admin-guide-cloud/ch_compute.xml:11(title) ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:102(title)
 msgid "Compute"
 msgstr ""
@@ -982,2122 +982,6 @@ msgstr ""
 msgid "Configuring networks for compute nodes"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:7(title)
-msgid "Instance building blocks"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:8(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 shutdown."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:11(para)
-msgid "You can also put an operating system on a persistent volume in Compute or the Block Storage volume system. This gives a more traditional, persistent system that accumulates states, which are preserved across restarts. To get a list of available images on your system, run: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:29(para)
-msgid "Automatically generated UUID of the image."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:35(para)
-msgid "Free form, human-readable name for image."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:56(para)
-msgid "Virtual hardware templates are called <literal>flavors</literal>. The default installation provides five flavors. By default, these are configurable by administrative users. However, you can change this behavior 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/compute/section_compute-instance-building-blocks.xml:62(para)
-msgid "For a list of flavors that are available on your system, run:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:6(title)
-msgid "Image management"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:7(para)
-msgid "The OpenStack Image Service discovers, registers, and retrieves virtual machine images. The service also includes a RESTful API that allows you to query VM image metadata and retrieve the actual image with HTTP requests. For more information about the API, see the <link href=\"http://developer.openstack.org/api-ref.html\">OpenStack API Complete Reference</link> and the <link href=\"http://docs.openstack.org/developer/python-glanceclient/\">Python API</link>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:16(para)
-msgid "The OpenStack Image Service can be controlled using a command-line tool. For more information about the using OpenStack Image command-line tool, see the <link href=\"http://docs.openstack.org/user-guide/content/cli_manage_images.html\">Manage Images</link> section in the <citetitle>OpenStack End User Guide</citetitle>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:22(para)
-msgid "Virtual images that have been made available through the Image Service can be stored in a variety of ways. In order to use these services, you must have a working installation of the Image Service, with a working endpoint, and users that have been created in OpenStack Identity. Additionally, you must meet the environment variables required by the Compute and Image Service clients."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:29(para)
-msgid "The Image Service supports these back-end stores:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:32(term)
-msgid "File system"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:34(para)
-msgid "The OpenStack Image Service stores virtual machine images in the file system back end by default. This simple back end writes image files to the local file system."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:41(term)
-msgid "Object Storage service"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:43(para)
-msgid "The OpenStack highly available service for storing objects."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:48(term)
-msgid "S3"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:50(para)
-msgid "The Amazon S3 service."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:54(term)
-msgid "HTTP"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:56(para)
-msgid "OpenStack Image Service can read virtual machine images that are available on the internet using HTTP. This store is read only."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:62(term)
-msgid "Rados block device (RBD)"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:64(para)
-msgid "Stores images inside of a Ceph storage cluster using Ceph's RBD interface."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:69(term)
-msgid "GridFS"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:71(para)
-msgid "Stores images using MongoDB."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:6(title)
-msgid "Secure with root wrappers"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:7(para)
-msgid "The root wrapper enables an unprivileged user to run a number of Compute actions as the root user in the safest manner possible. Historically, Compute used a specific <filename>sudoers</filename> file that listed every command that the Compute user was allowed to run, and used <placeholder-1/> to run that command as <literal>root</literal>. However this was difficult to maintain (the <filename>sudoers</filename> file was in packaging), and did not enable complex filtering of parameters (advanced filters). The rootwrap was designed to solve those issues."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:16(title)
-msgid "How rootwrap works"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:17(para)
-msgid "Instead of calling <placeholder-1/>, Compute services start with a <placeholder-2/> call; for example, <placeholder-3/>. A generic sudoers entry lets the Compute user run <placeholder-4/> as root. The <placeholder-5/> code looks for filter definition directories in its configuration file, and loads command filters from them. Then it checks if the command requested by Compute matches one of those filters, in which case it executes the command (as root). If no filter matches, it denies the request."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:25(para)
-msgid "To use <placeholder-1/>, you must be aware of the issues with using NFS and root-owned files. The NFS share must be configured with the <option>no_root_squash</option> option enabled."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:31(title)
-msgid "Security model"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:32(para)
-msgid "The escalation path is fully controlled by the root user. A sudoers entry (owned by root) allows Compute to run (as root) a specific rootwrap executable, and only with a specific configuration file (which should be owned by root). <placeholder-1/> imports the Python modules it needs from a cleaned (and system-default) <replaceable>PYTHONPATH</replaceable>. The configuration file (also root-owned) points to root-owned filter definition directories, which contain root-owned filters definition files. This chain ensures that the Compute user itself is not in control of the configuration or modules used by the <placeholder-2/> executable."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:43(title)
-msgid "Details of rootwrap.conf"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:44(para)
-msgid "You configure <placeholder-1/> in the <filename>rootwrap.conf</filename> file. Because it's in the trusted security path, it must be owned and writable by only the root user. The file's location is specified both in the sudoers entry and in the <filename>nova.conf</filename> configuration file with the <code>rootwrap_config=entry</code>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:49(para)
-msgid "The <filename>rootwrap.conf</filename> file uses an INI file format with these sections and parameters:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:53(caption)
-msgid "rootwrap.conf configuration options"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:58(para) ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:96(para)
-msgid "Configuration option=Default value"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:60(para) ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:98(para)
-msgid "(Type) Description"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:65(para)
-msgid "[DEFAULT]"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:66(para)
-msgid "filters_path=/etc/nova/rootwrap.d,/usr/share/nova/rootwrap"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:68(para)
-msgid "(ListOpt) Comma-separated list of directories containing filter definition files. Defines where filters for root wrap are stored. Directories defined on this line should all exist, be owned and writable only by the root user."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:80(title)
-msgid "Details of .filters files"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:81(para)
-msgid "Filters definition files contain lists of filters that <placeholder-1/> will use to allow or deny a specific command. They are generally suffixed by .filters. Since they are in the trusted security path, they need to be owned and writable only by the root user. Their location is specified in the <filename>rootwrap.conf</filename> file."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:86(para)
-msgid "Filter definition files use an INI file format with a [Filters] section and several lines, each with a unique parameter name (different for each filter that you define):"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:91(caption)
-msgid ".filters configuration options"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:103(para)
-msgid "[Filters]"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:104(para)
-msgid "filter_name=kpartx: CommandFilter, /sbin/kpartx, root"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:106(para)
-msgid "(ListOpt) Comma-separated list containing first the Filter class to use, followed by that Filter arguments (which vary depending on the Filter class selected)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:6(title)
-msgid "Configure Compute to use IPv6 addresses"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:7(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."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:15(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."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:22(title)
-msgid "Switch into IPv4/IPv6 dual-stack mode"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:23(para)
-msgid "On all nodes 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:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:31(para)
-msgid "Edit the <filename>nova.conf</filename> file on all nodes to specify <literal>use_ipv6 = True</literal>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:33(para)
-msgid "Restart all <literal>nova-*</literal> services."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:35(para)
-msgid "You can add a fixed range for IPv6 addresses to the <placeholder-1/> command. Specify <option>public</option> or <option>private</option> after the <option>network-create</option> parameter."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:38(replaceable)
-msgid "fixed_range_v4"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:38(replaceable)
-msgid "vlan_id"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:38(replaceable)
-msgid "vpn_start"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:38(replaceable)
-msgid "fixed_range_v6"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:39(para)
-msgid "You can set IPv6 global routing prefix by using the <option>--fixed_range_v6</option> parameter. The default value for the parameter is: <literal>fd00::/48</literal>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:44(para)
-msgid "When you use <literal>FlatDHCPManager</literal>, the command uses the original <option>--fixed_range_v6</option> value. For example:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:49(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 ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:604(None)
-msgid "@@image: '../../common/figures/SCH_5007_V00_NUAC-multi_nic_OpenStack-Flat-manager.jpg'; md5=31f7e15a45d042bd9d6499631e2f3ccc"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:614(None)
-msgid "@@image: '../../common/figures/SCH_5007_V00_NUAC-multi_nic_OpenStack-Flat-DHCP-manager.jpg'; md5=0f33a228f1dec4a4e4424dd5ee81bde8"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:624(None)
-msgid "@@image: '../../common/figures/SCH_5007_V00_NUAC-multi_nic_OpenStack-VLAN-manager.jpg'; md5=0acaf3e2041f941d8fee2d111f37e7ac"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:7(title)
-msgid "Networking with nova-network"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:8(para)
-msgid "Understanding the networking configuration options helps you design the best configuration for your Compute instances."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:11(para)
-msgid "You can choose to either install and configure <systemitem class=\"service\">nova-network</systemitem> for networking between VMs or use the OpenStack Networking service (neutron) for networking. To configure Compute networking options with OpenStack Networking, see the <xref linkend=\"ch_networking\"/>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:16(title)
-msgid "Networking concepts"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:17(para)
-msgid "This section offers a brief overview of networking concepts for Compute."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:18(para)
-msgid "Compute assigns a private IP address to each VM instance. (Currently, Compute with <systemitem class=\"service\">nova-network</systemitem> only supports Linux bridge networking that enables the virtual interfaces to connect to the outside network through the physical interface.) Compute makes a distinction between <emphasis role=\"italic\">fixed IPs</emphasis> and <emphasis role=\"italic\">floating IPs</emphasis>. Fixed IPs are IP addresses that are assigned to an instance on creation and stay the same until the instance is explicitly terminated. By contrast, floating IPs are addresses that can be dynamically associated with an instance. A floating IP address can be disassociated and associated with another instance at any time. A user can reserve a floating IP for their project."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:28(para)
-msgid "The network controller with <systemitem class=\"service\">nova-network</systemitem> provides virtual networks to enable compute servers to interact with each other and with the public network. Compute with <systemitem class=\"service\">nova-network</systemitem> supports the following network modes, which are implemented as “Network Manager” types."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:34(term)
-msgid "Flat Network Manager"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:35(para)
-msgid "In <emphasis role=\"bold\">Flat</emphasis> mode, a network administrator specifies a subnet. IP addresses for VM instances are assigned from the subnet, and then injected into the image on launch. Each instance receives a fixed IP address from the pool of available addresses. A system administrator must create the Linux networking bridge (typically named <literal>br100</literal>, although this is configurable) on the systems running the <systemitem class=\"service\">nova-network</systemitem> service. All instances of the system are attached to the same bridge, and this is configured manually by the network administrator."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:45(para)
-msgid "Configuration injection currently only works on Linux-style systems that keep networking configuration in <filename>/etc/network/interfaces</filename>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:50(term)
-msgid "Flat DHCP Network Manager"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:51(para)
-msgid "In <emphasis role=\"bold\">FlatDHCP</emphasis> mode, OpenStack starts a DHCP server (<systemitem>dnsmasq</systemitem>) to allocate IP addresses to VM instances from the specified subnet, in addition to manually configuring the networking bridge. IP addresses for VM instances are assigned from a subnet specified by the network administrator."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:56(para)
-msgid "Like Flat Mode, all instances are attached to a single bridge on the compute node. Additionally, a DHCP server is running to configure instances (depending on single-/multi-host mode, alongside each <systemitem class=\"service\">nova-network</systemitem>). In this mode, Compute does a bit more configuration in that it attempts to bridge into an ethernet device (<literal>flat_interface</literal>, eth0 by default). For every instance, Compute allocates a fixed IP address and configures dnsmasq with the MAC/IP pair for the VM. Dnsmasq does not take part in the IP address allocation process, it only hands out IPs according to the mapping done by Compute. Instances receive their fixed IPs by doing a <placeholder-1/>. These IPs are <emphasis role=\"italic\">not</emphasis> assigned to any of the host's network interfaces, only to the VM's guest-side interface."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:69(para)
-msgid "In any setup with flat networking, the hosts providing the <systemitem class=\"service\">nova-network</systemitem> service are responsible for forwarding traffic from the private network. They also run and configure <systemitem>dnsmasq</systemitem> as a DHCP server listening on this bridge, usually on IP address 10.0.0.1 (see <link linkend=\"section_dnsmasq\">DHCP server: dnsmasq </link>). Compute can determine the NAT entries for each network, although sometimes NAT is not used, such as when configured with all public IPs or a hardware router is used (one of the HA options). Such hosts need to have <literal>br100</literal> configured and physically connected to any other nodes that are hosting VMs. You must set the <literal>flat_network_bridge</literal> option or create networks with the bridge parameter in order to avoid raising an error. Compute nodes have iptables/ebtables entries created for each project and instance to protect against IP/MAC address spoofing and ARP poisoning."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:84(para)
-msgid "In single-host Flat DHCP mode you <emphasis role=\"italic\">will</emphasis> be able to ping VMs through their fixed IP from the <systemitem>nova-network</systemitem> node, but you <emphasis role=\"italic\">cannot</emphasis> ping them from the compute nodes. This is expected behavior."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:91(term)
-msgid "VLAN Network Manager"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:92(para)
-msgid "<emphasis role=\"bold\">VLANManager</emphasis> mode is the default mode for OpenStack Compute. In this mode, Compute creates a VLAN and bridge for each tenant. For multiple-machine installation, the VLAN Network Mode requires a switch that supports VLAN tagging (IEEE 802.1Q). The tenant gets a range of private IPs that are only accessible from inside the VLAN. In order for a user to access the instances in their tenant, a special VPN instance (code named cloudpipe) needs to be created. Compute generates a certificate and key for the user to access the VPN and starts the VPN automatically. It provides a private network segment for each tenant's instances that can be accessed through a dedicated VPN connection from the Internet. In this mode, each tenant gets its own VLAN, Linux networking bridge, and subnet."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:103(para)
-msgid "The subnets are specified by the network administrator, and are assigned dynamically to a tenant when required. A DHCP Server is started for each VLAN to pass out IP addresses to VM instances from the subnet assigned to the tenant. All instances belonging to one tenant are bridged into the same VLAN for that tenant. OpenStack Compute creates the Linux networking bridges and VLANs when required."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:111(para)
-msgid "These network managers can co-exist in a cloud system. However, because you cannot select the type of network for a given tenant, you cannot configure multiple network types in a single Compute installation."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:114(para)
-msgid "All network managers configure the network using <emphasis role=\"italic\">network drivers</emphasis>. For example, the Linux L3 driver (<literal>l3.py</literal> and <literal>linux_net.py</literal>), which makes use of <literal>iptables</literal>, <literal>route</literal> and other network management facilities, and libvirt's <link href=\"http://libvirt.org/formatnwfilter.html\">network filtering facilities</link>. The driver is not tied to any particular network manager; all network managers use the same driver. The driver usually initializes (creates bridges and so on) only when the first VM lands on this host node."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:122(para)
-msgid "All network managers operate in either <emphasis role=\"italic\">single-host</emphasis> or <emphasis role=\"italic\">multi-host</emphasis> mode. This choice greatly influences the network configuration. In single-host mode, a single <systemitem class=\"service\">nova-network</systemitem> service provides a default gateway for VMs and hosts a single DHCP server (<systemitem>dnsmasq</systemitem>). In multi-host mode, each compute node runs its own <systemitem class=\"service\">nova-network</systemitem> service. In both cases, all traffic between VMs and the outer world flows through <systemitem class=\"service\">nova-network</systemitem>. Each mode has its pros and cons (see the <citetitle>Network Topology</citetitle> section in the <link href=\"http://docs.openstack.org/trunk/openstack-ops/content/\"><citetitle>OpenStack Operations Guide</citetitle></link>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:134(para)
-msgid "All networking options require network connectivity to be already set up between OpenStack physical nodes. OpenStack does not configure any physical network interfaces. All network managers automatically create VM virtual interfaces. Some, but not all, managers create network bridges such as <literal>br100</literal>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:139(para)
-msgid "All machines must have a <emphasis role=\"italic\">public</emphasis> and <emphasis role=\"italic\">internal</emphasis> network interface (controlled by the options: <literal>public_interface</literal> for the public interface, and <literal>flat_interface</literal> and <literal>vlan_interface</literal> for the internal interface with flat / VLAN managers). This guide refers to the public network as the external network and the private network as the internal or tenant network."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:151(para)
-msgid "The internal network interface is used for communication with VMs; the interface should not have an IP address attached to it before OpenStack installation (it serves merely as a fabric where the actual endpoints are VMs and dnsmasq). Also, you must put the internal network interface in <emphasis role=\"italic\">promiscuous mode</emphasis>, because it must receive packets whose target MAC address is of the guest VM, not of the host."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:157(para)
-msgid "Throughout this documentation, the public network is sometimes referred to as the external network, while the internal network is also sometimes referred to as the private network or tenant network."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:163(para)
-msgid "For flat and flat DHCP modes, use the following command to create a network:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:168(para)
-msgid "<option>--fixed-range-v4-</option> specifies the network subnet."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:171(para)
-msgid "<option>--fixed-cidr</option> specifies a range of fixed IP addresses to allocate, and can be a subset of the <option>--fixed-range-v4</option> argument."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:176(para)
-msgid "<option>--bridge</option> specifies the bridge device to which this network is connected on every compute node."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:166(para)
-msgid "Where:<placeholder-1/>"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:182(title)
-msgid "DHCP server: dnsmasq"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:183(para)
-msgid "The Compute service uses <link href=\"http://www.thekelleys.org.uk/dnsmasq/doc.html\">dnsmasq</link> as the DHCP server when running with either that Flat DHCP Network Manager or the VLAN Network Manager. The <systemitem class=\"service\">nova-network</systemitem> service is responsible for starting up <systemitem>dnsmasq</systemitem> processes."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:188(para)
-msgid "The behavior of <systemitem>dnsmasq</systemitem> can be customized by creating a <systemitem>dnsmasq</systemitem> configuration file. Specify the configuration file using the <literal>dnsmasq_config_file</literal> configuration option. For example:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:193(para)
-msgid "For an example of how to change the behavior of <systemitem>dnsmasq</systemitem> using a <systemitem>dnsmasq</systemitem> configuration file, see the <link href=\"http://docs.openstack.org/trunk/config-reference/content/\"><citetitle>OpenStack Configuration Reference</citetitle></link>. The <systemitem>dnsmasq</systemitem> documentation also has a more comprehensive <link href=\"http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq.conf.example\">dnsmasq configuration file example</link>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:200(para)
-msgid "<systemitem>dnsmasq</systemitem> also acts as a caching DNS server for instances. You can explicitly specify the DNS server that <systemitem>dnsmasq</systemitem> should use by setting the <literal>dns_server</literal> configuration option in <filename>/etc/nova/nova.conf</filename>. The following example would configure <systemitem>dnsmasq</systemitem> to use Google's public DNS server:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:206(para)
-msgid "Logging output for <systemitem>dnsmasq</systemitem> goes to the <systemitem>syslog</systemitem> (typically <filename>/var/log/syslog</filename> or <filename>/var/log/messages</filename>, depending on Linux distribution). <systemitem>dnsmasq</systemitem> logging output can be useful for troubleshooting if VM instances boot successfully but are not reachable over the network."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:211(para)
-msgid "A network administrator can run <code>nova-manage fixed reserve --address=<replaceable>x.x.x.x</replaceable></code> to specify the starting point IP address (x.x.x.x) to reserve with the DHCP server. This reservation only affects which IP address the VMs start at, not the fixed IP addresses that the <systemitem class=\"service\">nova-network</systemitem> service places on the bridges."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:223(title)
-msgid "Metadata service"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:225(title)
-msgid "Introduction"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:226(para)
-msgid "The Compute service uses a special metadata service to enable virtual machine instances to retrieve instance-specific data. Instances access the metadata service at <literal>http://169.254.169.254</literal>. The metadata service supports two sets of APIs: an OpenStack metadata API and an EC2-compatible API. Each of the APIs is versioned by date."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:234(para)
-msgid "To retrieve a list of supported versions for the OpenStack metadata API, make a GET request to <literal>http://169.254.169.254/openstack</literal> For example:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:241(para)
-msgid "To list supported versions for the EC2-compatible metadata API, make a GET request to <literal>http://169.254.169.254</literal>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:244(para) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:268(para) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:278(para) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:295(para) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:325(para) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:331(para) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:518(para) ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:47(para) ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:61(para) ./doc/admin-guide-cloud/networking/section_networking-use.xml:461(para)
-msgid "For example:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:256(para)
-msgid "If you write a consumer for one of these APIs, always attempt to access the most recent API version supported by your consumer first, then fall back to an earlier version if the most recent one is not available."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:263(title)
-msgid "OpenStack metadata API"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:264(para)
-msgid "Metadata from the OpenStack API is distributed in JSON format. To retrieve the metadata, make a GET request to <literal>http://169.254.169.254/openstack/2012-08-10/meta_data.json</literal>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:271(para)
-msgid "Instances also retrieve user data (passed as the <literal>user_data</literal> parameter in the API call or by the <literal>--user_data</literal> flag in the <placeholder-1/> command) through the metadata service, by making a GET request to <literal>http://169.254.169.254/openstack/2012-08-10/user_data</literal>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:284(title)
-msgid "EC2 metadata API"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:285(para)
-msgid "The metadata service has an API that is compatible with version 2009-04-04 of the <link href=\"http://docs.amazonwebservices.com/AWSEC2/2009-04-04/UserGuide/AESDG-chapter-instancedata.html\">Amazon EC2 metadata service</link>; virtual machine images that are designed for EC2 work properly with OpenStack."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:291(para)
-msgid "The EC2 API exposes a separate URL for each metadata. You can retrieve a listing of these elements by making a GET query to <literal>http://169.254.169.254/2009-04-04/meta-data/</literal>"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:321(para)
-msgid "Instances can retrieve the public SSH key (identified by keypair name when a user requests a new instance) by making a GET request to <literal>http://169.254.169.254/2009-04-04/meta-data/public-keys/0/openssh-key</literal>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:328(para)
-msgid "Instances can retrieve user data by making a GET request to <literal>http://169.254.169.254/2009-04-04/user-data</literal>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:337(title)
-msgid "Run the metadata service"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:338(para)
-msgid "The metadata service is implemented by either the <systemitem class=\"service\">nova-api</systemitem> service or the <systemitem class=\"service\">nova-api-metadata</systemitem> service. (The <systemitem class=\"service\">nova-api-metadata</systemitem> service is generally only used when running in multi-host mode, it retrieves instance-specific metadata). If you are running the <systemitem class=\"service\">nova-api</systemitem> service, you must have <literal>metadata</literal> as one of the elements of the list of the <literal>enabled_apis</literal> configuration option in <filename>/etc/nova/nova.conf</filename>. The default <literal>enabled_apis</literal> configuration setting includes the metadata service, so you should not need to modify it."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:349(para)
-msgid "Hosts access the service at <literal>169.254.169.254:80</literal>, and this is translated to <literal>metadata_host:metadata_port</literal> by an iptables rule established by the <systemitem class=\"service\">nova-network</systemitem> service. In multi-host mode, you can set <option>metadata_host</option> to <literal>127.0.0.1</literal>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:354(para)
-msgid "To enable instances to reach the metadata service, the <systemitem class=\"service\">nova-network</systemitem> service configures iptables to NAT port <literal>80</literal> of the <literal>169.254.169.254</literal> address to the IP address specified in <option>metadata_host</option> (default <literal>$my_ip</literal>, which is the IP address of the <systemitem class=\"service\">nova-network</systemitem> service) and port specified in <option>metadata_port</option> (default <literal>8775</literal>) in <filename>/etc/nova/nova.conf</filename>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:368(para)
-msgid "The <literal>metadata_host</literal> configuration option must be an IP address, not a host name."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:373(para)
-msgid "The default Compute service settings assume that the <systemitem class=\"service\">nova-network</systemitem> service and the <systemitem class=\"service\">nova-api</systemitem> service are running on the same host. If this is not the case, you must make this change in the <filename>/etc/nova/nova.conf</filename> file on the host running the <systemitem class=\"service\">nova-network</systemitem> service:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:384(para)
-msgid "Set the <literal>metadata_host</literal> configuration option to the IP address of the host where the <systemitem class=\"service\">nova-api</systemitem> service runs."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:395(title)
-msgid "Enable ping and SSH on VMs"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:396(para)
-msgid "Be sure you enable access to your VMs by using the <placeholder-1/> or <placeholder-2/> command. These commands enable you to <placeholder-3/> and <placeholder-4/> to your VMs:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:402(para)
-msgid "You must run these commands as root only if the credentials used to interact with <systemitem class=\"service\">nova-api</systemitem> are in <filename>/root/.bashrc</filename>. If the EC2 credentials are the <filename>.bashrc</filename> file for another user, you must run these commands as the user."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:410(para)
-msgid "Run <placeholder-1/> commands:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:413(para)
-msgid "Using euca2ools:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:416(para)
-msgid "If you still cannot ping or SSH your instances after issuing the <placeholder-1/> commands, look at the number of <literal>dnsmasq</literal> processes that are running. If you have a running instance, check to see that TWO <literal>dnsmasq</literal> processes are running. If not, perform the following commands as root:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:425(title)
-msgid "Configure public (floating) IP addresses"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:427(para)
-msgid "If you are using Compute's <systemitem class=\"service\">nova-network</systemitem> instead of OpenStack Networking (neutron) for networking in OpenStack, use procedures in this section to configure floating IP addresses. For instructions on how to configure OpenStack Networking (neutron) to provide access to instances through floating IP addresses, see <xref linkend=\"section_l3_router_and_nat\"/>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:433(title)
-msgid "Private and public IP addresses"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:434(para)
-msgid "Every virtual instance is automatically assigned a private IP address. You can optionally assign public IP addresses to instances. The term <glossterm baseform=\"floating IP address\">floating IP</glossterm> refers to an IP address, typically public, that you can dynamically add to a running virtual instance. OpenStack Compute uses Network Address Translation (NAT) to assign floating IPs to virtual instances."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:444(para)
-msgid "If you plan to use this feature, you must add edit the <filename>/etc/nova/nova.conf</filename> file to specify to which interface the <systemitem class=\"service\">nova-network</systemitem> service binds public IP addresses, as follows:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:450(replaceable)
-msgid "vlan100"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:451(para)
-msgid "If you make changes to the <filename>/etc/nova/nova.conf</filename> file while the <systemitem class=\"service\">nova-network</systemitem> service is running, you must restart the service."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:457(title)
-msgid "Traffic between VMs using floating IPs"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:459(para)
-msgid "Because floating IPs are implemented by using a source NAT (SNAT rule in iptables), security groups can display inconsistent behavior if VMs use their floating IP to communicate with other VMs, particularly on the same physical host. Traffic from VM to VM across the fixed network does not have this issue, and so this is the recommended path. To ensure that traffic does not get SNATed to the floating range, explicitly set: <placeholder-1/>The <literal>x.x.x.x/y</literal> value specifies the range of floating IPs for each pool of floating IPs that you define. If the VMs in the source group have floating IPs, this configuration is also required."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:472(title)
-msgid "Enable IP forwarding"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:473(para)
-msgid "By default, IP forwarding is disabled on most Linux distributions. To use the floating IP feature, you must enable IP forwarding."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:477(para)
-msgid "You must enable IP forwarding only on the nodes that run the <systemitem class=\"service\">nova-network</systemitem> service. If you use <literal>multi_host</literal> mode, ensure that you enable it on all compute nodes. Otherwise, enable it on only the node that runs the <systemitem class=\"service\">nova-network</systemitem> service."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:483(para)
-msgid "To check whether forwarding is enabled, run:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:486(para)
-msgid "Alternatively, you can run:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:489(para)
-msgid "In the previous example, IP forwarding is <emphasis role=\"bold\">disabled</emphasis>. To enable it dynamically, run:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:492(para)
-msgid "Or:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:494(para)
-msgid "To make the changes permanent, edit the <filename>/etc/sysctl.conf</filename> file and update the IP forwarding setting:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:498(para)
-msgid "Save the file and run the following command to apply the changes:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:500(para)
-msgid "You can also update the setting by restarting the network service:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:503(para)
-msgid "On Ubuntu, run:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:507(para)
-msgid "On RHEL/Fedora/CentOS, run:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:513(title)
-msgid "Create a list of available floating IP addresses"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:515(para)
-msgid "Compute maintains a list of floating IP addresses that you can assign to instances. Use the <placeholder-1/> command to add entries to this list."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:520(para)
-msgid "You can use the following <placeholder-1/> commands to perform floating IP operations:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:526(para)
-msgid "Lists the floating IP addresses in the pool."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:530(replaceable)
-msgid "[pool name]"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:530(replaceable) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:535(replaceable)
-msgid "[CIDR]"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:531(para)
-msgid "Creates specific floating IPs for either a single address or a subnet."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:536(para)
-msgid "Removes floating IP addresses using the same parameters as the create command."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:541(para)
-msgid "For information about how administrators can associate floating IPs with instances, see <link href=\"http://docs.openstack.org/user-guide-admin/content/manage_ip_addresses.html\">Manage IP addresses</link> in the <citetitle>OpenStack Admin User Guide</citetitle>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:549(title)
-msgid "Automatically add floating IPs"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:550(para)
-msgid "You can configure the <systemitem class=\"service\">nova-network</systemitem> service to automatically allocate and assign a floating IP address to virtual instances when they are launched. Add the following line to the <filename>/etc/nova/nova.conf</filename> file and restart the <systemitem class=\"service\">nova-network</systemitem> service:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:560(para)
-msgid "If you enable this option and all floating IP addresses have already been allocated, the <placeholder-1/> command fails."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:568(title)
-msgid "Remove a network from a project"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:569(para)
-msgid "You cannot remove a network that has already been associated to a project by simply deleting it."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:571(para)
-msgid "To determine the project ID, you must have administrative rights. You can disassociate the project from the network with a scrub command and the project ID as the final parameter:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:574(replaceable)
-msgid "&lt;id&gt;"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:577(title)
-msgid "Multiple interfaces for your instances (multinic)"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:580(para)
-msgid "The multinic feature allows you to plug more than one interface to your instances, making it possible to make several use cases available:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:584(para)
-msgid "SSL Configurations (VIPs)"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:587(para)
-msgid "Services failover/ HA"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:590(para)
-msgid "Bandwidth Allocation"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:593(para)
-msgid "Administrative/ Public access to your instances"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:599(title)
-msgid "multinic flat manager"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:609(title)
-msgid "multinic flatdhcp manager"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:619(title)
-msgid "multinic VLAN manager"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:597(para)
-msgid "Each VIF is representative of a separate network with its own IP block. Every network mode introduces its own set of changes regarding the multinic usage: <placeholder-1/><placeholder-2/><placeholder-3/>"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:630(title)
-msgid "Use the multinic feature"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:631(para)
-msgid "In order to use the multinic feature, first create two networks, and attach them to your tenant (still named 'project' on the command line): <placeholder-1/> Now every time you spawn a new instance, it gets two IP addresses from the respective DHCP servers:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:644(para)
-msgid "Make sure to power up the second interface on the instance, otherwise that last won't be reachable through its second IP. Here is an example of how to setup the interfaces within the instance (this is the configuration that needs to be applied inside the image):"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:650(filename)
-msgid "/etc/network/interfaces"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:662(para)
-msgid "If the Virtual Network Service Neutron is installed, it is possible to specify the networks to attach to the respective interfaces by using the <literal>--nic</literal> flag when invoking the <literal>nova</literal> command: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:674(title)
-msgid "Troubleshoot Networking"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:676(title)
-msgid "Cannot reach floating IPs"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:677(para)
-msgid "If you cannot reach your instances through the floating IP address, check the following:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:679(para)
-msgid "Ensure the default security group allows ICMP (ping) and SSH (port 22), so that you can reach the instances:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:689(para)
-msgid "Ensure the NAT rules have been added to <systemitem>iptables</systemitem> on the node that <systemitem>nova-network</systemitem> is running on, as root:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:694(para)
-msgid "Check that the public address, in this example \"68.99.26.170\", has been added to your public interface. You should see the address in the listing when you enter \"ip addr\" at the command prompt."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:704(para)
-msgid "Note that you cannot SSH to an instance with a public IP from within the same server as the routing configuration won't allow it."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:707(para)
-msgid "You can use <placeholder-1/> to identify if packets are being routed to the inbound interface on the compute host. If the packets are reaching the compute hosts but the connection is failing, the issue may be that the packet is being dropped by reverse path filtering. Try disabling reverse-path filtering on the inbound interface. For example, if the inbound interface is <literal>eth2</literal>, as root, run:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:713(replaceable)
-msgid "eth2"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:714(para)
-msgid "If this solves your issue, add the following line to <filename>/etc/sysctl.conf</filename> so that the reverse-path filter is disabled the next time the compute host reboots: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:721(title)
-msgid "Disable firewall"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:722(para)
-msgid "To help debug networking issues with reaching VMs, you can disable the firewall by setting the following option in <filename>/etc/nova/nova.conf</filename>:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:727(para)
-msgid "We strongly recommend you remove this line to re-enable the firewall once your networking issues have been resolved."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:732(title)
-msgid "Packet loss from instances to nova-network server (VLANManager mode)"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:734(para)
-msgid "If you can SSH to your instances but you find that the network interactions to your instance is slow, or if you find that running certain operations are slower than they should be (for example, <placeholder-1/>), then there may be packet loss occurring on the connection to the instance."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:741(para)
-msgid "Packet loss can be caused by Linux networking configuration settings related to bridges. Certain settings can cause packets to be dropped between the VLAN interface (for example, <literal>vlan100</literal>) and the associated bridge interface (for example, <literal>br100</literal>) on the host running the <systemitem class=\"service\">nova-network</systemitem> service."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:750(para)
-msgid "One way to check whether this is the issue in your setup, is to open up three terminals and run the following commands:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:755(para)
-msgid "In the first terminal, on the host running nova-network, use <placeholder-1/> on the VLAN interface to monitor DNS-related traffic (UDP, port 53). As root, run:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:760(para)
-msgid "In the second terminal, also on the host running nova-network, use <placeholder-1/> to monitor DNS-related traffic on the bridge interface. As root, run:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:764(para)
-msgid "In the third terminal, SSH inside of the instance and generate DNS requests by using the <placeholder-1/> command:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:768(para)
-msgid "The symptoms may be intermittent, so try running <placeholder-1/> multiple times. If the network configuration is correct, the command should return immediately each time. If it is not functioning properly, the command hangs for several seconds."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:774(para)
-msgid "If the <placeholder-1/> command sometimes hangs, and there are packets that appear in the first terminal but not the second, then the problem may be due to filtering done on the bridges. Try to disable filtering, run the following commands as root:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:781(para)
-msgid "If this solves your issue, add the following line to <filename>/etc/sysctl.conf</filename> so that these changes take effect the next time the host reboots:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:791(title)
-msgid "KVM: Network connectivity works initially, then fails"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:793(para)
-msgid "Some administrators have observed an issue with the KVM hypervisor where instances running Ubuntu 12.04 sometimes loses network connectivity after functioning properly for a period of time. Some users have reported success with loading the vhost_net kernel module as a workaround for this issue (see <link href=\"https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/997978/\">bug #997978</link>) . This kernel module may also <link href=\"http://www.linux-kvm.org/page/VhostNet\">improve network performance on KVM</link>. To load the kernel module, as root:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:808(para)
-msgid "Loading the module has no effect on running instances."
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:64(None)
-msgid "@@image: '../../common/figures/instance-life-1.png'; md5=c7e56263f9ffb5a5cffb59fbc5ffba35"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:83(None)
-msgid "@@image: '../../common/figures/instance-life-2.png'; md5=84aed8a4c2575548c2f8bacf496465ac"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:121(None)
-msgid "@@image: '../../common/figures/instance-life-3.png'; md5=e25d1bd617373f95e1b8a12605a65ac6"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:7(title)
-msgid "Images and instances"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:8(para)
-msgid "Disk images provide templates for virtual machine file systems. The Image Service manages storage and management of images."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:11(para)
-msgid "Instances are the individual virtual machines that run on physical compute nodes. Users can launch any number of instances from the same image. Each launched instance runs from a copy of the base image so that any changes made to the instance do not affect the base image. You can take snapshots of running instances to create an image based on the current disk state of a particular instance. The Compute services manages instances."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:19(para)
-msgid "When you launch an instance, you must choose a <literal>flavor</literal>, which represents a set of virtual resources. Flavors define how many virtual CPUs an instance has and the amount of RAM and size of its ephemeral disks. OpenStack provides a number of predefined flavors that you can edit or add to. Users must select from the set of available flavors defined on their cloud."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:26(para)
-msgid "For more information about creating and troubleshooting images, see the <link href=\"http://docs.openstack.org/image-guide/content/\"><citetitle>OpenStack Virtual Machine Image Guide</citetitle></link>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:33(para)
-msgid "For more information about image configuration options, see the <link href=\"http://docs.openstack.org/trunk/config-reference/content/ch_configuring-openstack-image-service.html\">Image Services</link> section of the <citetitle>OpenStack Configuration Reference</citetitle>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:39(para)
-msgid "For more information about flavors, see <xref linkend=\"customize-flavors\"/> or the <link href=\"http://docs.openstack.org/trunk/openstack-ops/content/flavors.html\">Flavors</link> section in the <citetitle>OpenStack Operations Guide</citetitle>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:45(para)
-msgid "You can add and remove additional resources from running instances, such as persistent volume storage, or public IP addresses. The example used in this chapter is of a typical virtual system within an OpenStack cloud. It uses the <systemitem class=\"service\">cinder-volume</systemitem> service, which provides persistent block storage, instead of the ephemeral storage provided by the selected instance flavor."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:53(para)
-msgid "This diagram shows the system state prior to launching an instance. The image store, fronted by the Image service (glance) has a number of predefined images. Inside the cloud, a compute node contains the available vCPU, memory, and local disk resources. Additionally, the <systemitem class=\"service\">cinder-volume</systemitem> service provides a number of predefined volumes."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:59(title)
-msgid "Base image state with no running instances"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:68(para)
-msgid "To launch an instance, select an image, a flavor, and other optional attributes. The selected flavor provides a root volume, labeled <literal>vda</literal> in this diagram, and additional ephemeral storage, labeled <literal>vdb</literal>. In this example, the <systemitem class=\"service\">cinder-volume</systemitem> store is mapped to the third virtual disk on this instance, <literal>vdc</literal>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:77(title)
-msgid "Instance creation from image and runtime state"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:87(para)
-msgid "The base image is copied from the image store to the local disk. The local disk is the first disk that the instance accesses, and is labeled <literal>vda</literal>. By using smaller images, your instances start up faster as less data needs to be copied across the network."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:92(para)
-msgid "A new empty disk, labeled <literal>vdb</literal> is also created. This is an empty ephemeral disk, which is destroyed when you delete the instance."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:95(para)
-msgid "The compute node is attached to the <systemitem class=\"service\">cinder-volume</systemitem> using iSCSI, and maps to the third disk, <literal>vdc</literal>. The vCPU and memory resources are provisioned and the instance is booted from <literal>vda</literal>. The instance runs and changes data on the disks as indicated in red in the diagram."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:105(para)
-msgid "Some of the details in this example scenario might be different in your environment. For example, you might use a different type of back-end storage or different network protocols. One common variant is that the ephemeral storage used for volumes <literal>vda</literal> and <literal>vdb</literal> could be backed by network storage rather than a local disk."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:111(para)
-msgid "When the instance is deleted, the state is reclaimed with the exception of the persistent volume. The ephemeral storage is purged; memory and vCPU resources are released. The image remains unchanged throughout."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:115(title)
-msgid "End state of image and volume after instance exits"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:130(title)
-msgid "Control where instances run"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:131(para)
-msgid "The <link href=\"http://docs.openstack.org/trunk/config-reference/content/\"><citetitle>OpenStack Configuration Reference</citetitle></link> provides detailed information on controlling where your instances run, including ensuring a set of instances run on different compute nodes for service resiliency or on the same node for high performance inter-instance communications."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:141(replaceable)
-msgid "availability-zone"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:141(replaceable)
-msgid "compute-host"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:139(para)
-msgid "Admin users can specify an exact compute node to run on using the command <placeholder-1/>"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:9(title)
-msgid "Configure Compute service groups"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:10(para)
-msgid "To effectively manage and utilize compute nodes, the Compute service must know their statuses. For example, when a user launches a new VM, the Compute scheduler sends the request to a live node; the Compute service queries the ServiceGroup API to get information about whether a node is alive."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:14(para)
-msgid "When a compute worker (running the <systemitem class=\"service\">nova-compute</systemitem> daemon) starts, it calls the <systemitem>join</systemitem> API to join the compute group. Any interested service (for example, the scheduler) can query the group's membership and the status of its nodes. Internally, the <systemitem>ServiceGroup</systemitem> client driver automatically updates the compute worker status."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:19(para)
-msgid "The database, ZooKeeper, and Memcache drivers are available."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:21(title)
-msgid "Database ServiceGroup driver"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:22(para)
-msgid "By default, Compute uses the database driver to track node liveness. In a compute worker, this driver periodically sends a <placeholder-1/> command to the database, saying <quote>I'm OK</quote> with a timestamp. Compute uses a pre-defined timeout (<literal>service_down_time</literal>) to determine whether a node is dead."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:26(para)
-msgid "The driver has limitations, which can be an issue depending on your setup. The more compute worker nodes that you have, the more pressure you put on the database. By default, the timeout is 60 seconds so it might take some time to detect node failures. You could reduce the timeout value, but you must also make the database update more frequently, which again increases the database workload."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:31(para)
-msgid "The database contains data that is both transient (whether the node is alive) and persistent (for example, entries for VM owners). With the ServiceGroup abstraction, Compute can treat each type separately."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:36(title)
-msgid "ZooKeeper ServiceGroup driver"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:37(para)
-msgid "The ZooKeeper ServiceGroup driver works by using ZooKeeper ephemeral nodes. ZooKeeper, in contrast to databases, is a distributed system. Its load is divided among several servers. At a compute worker node, after establishing a ZooKeeper session, the driver creates an ephemeral znode in the group directory. Ephemeral znodes have the same lifespan as the session. If the worker node or the <systemitem class=\"service\">nova-compute</systemitem> daemon crashes, or a network partition is in place between the worker and the ZooKeeper server quorums, the ephemeral znodes are removed automatically. The driver gets the group membership by running the <placeholder-1/> command in the group directory."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:47(para)
-msgid "To use the ZooKeeper driver, you must install ZooKeeper servers and client libraries. Setting up ZooKeeper servers is outside the scope of this guide (for more information, see <link href=\"http://zookeeper.apache.org/\">Apache Zookeeper</link>)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:51(para)
-msgid "To use ZooKeeper, you must install client-side Python libraries on every nova node: <literal>python-zookeeper</literal> the official Zookeeper Python binding and evzookeeper the library to make the binding work with the eventlet threading model."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:55(para)
-msgid "The following example assumes the ZooKeeper server addresses and ports are <literal>192.168.2.1:2181</literal>, <literal>192.168.2.2:2181</literal>, and <literal>192.168.2.3:2181</literal>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:58(para)
-msgid "The following values in the <filename>/etc/nova/nova.conf</filename> file (on every node) are required for the <systemitem>ZooKeeper</systemitem> driver:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:65(para)
-msgid "To customize the Compute Service groups, use the following configuration option settings:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:70(title)
-msgid "Memcache ServiceGroup driver"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:71(para)
-msgid "The <systemitem>memcache</systemitem> ServiceGroup driver uses memcached, which is a distributed memory object caching system that is often used to increase site performance. For more details, see <link href=\"http://memcached.org/\">memcached.org</link>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:75(para)
-msgid "To use the <systemitem>memcache</systemitem> driver, you must install <systemitem>memcached</systemitem>. However, because <systemitem>memcached</systemitem> is often used for both OpenStack Object Storage and OpenStack dashboard, it might already be installed. If <systemitem>memcached</systemitem> is not installed, refer to the <link href=\"http://docs.openstack.org/icehouse\"><citetitle>OpenStack Installation Guide</citetitle></link> for more information."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:83(para)
-msgid "The following values in the <filename>/etc/nova/nova.conf</filename> file (on every node) are required for the <systemitem>memcache</systemitem> driver:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:7(title)
-msgid "Recover from a failed compute node"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:8(para)
-msgid "If you deployed Compute with a shared file system, you can quickly recover from a failed compute node. Of the two methods covered in these sections, evacuating is the preferred method even in the absence of shared storage. Evacuating provides many benefits over manual recovery, such as re-attachment of volumes and floating IPs."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:14(title)
-msgid "Manual recovery"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:15(para)
-msgid "To recover a KVM/libvirt compute node, see the previous section. Use the following procedure for all other hypervisors."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:18(title)
-msgid "Review host information"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:20(para)
-msgid "Identify the VMs on the affected hosts, using tools such as a combination of <literal>nova list</literal> and <literal>nova show</literal> or <literal>euca-describe-instances</literal>. For example, the following output displays information about instance <systemitem>i-000015b9</systemitem> that is running on node <systemitem>np-rcc54</systemitem>:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:29(para)
-msgid "Review the status of the host by querying the Compute database. Some of the important information is highlighted below. The following example converts an EC2 API instance ID into an OpenStack ID; if you used the <literal>nova</literal> commands, you can substitute the ID directly. You can find the credentials for your database in <filename>/etc/nova.conf</filename>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:55(title)
-msgid "Recover the VM"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:57(para)
-msgid "After you have determined the status of the VM on the failed host, decide to which compute host the affected VM should be moved. For example, run the following database command to move the VM to <systemitem>np-rcc46</systemitem>:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:64(para)
-msgid "If using a hypervisor that relies on libvirt (such as KVM), it is a good idea to update the <literal>libvirt.xml</literal> file (found in <literal>/var/lib/nova/instances/[instance ID]</literal>). The important changes to make are:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:71(para)
-msgid "Change the <literal>DHCPSERVER</literal> value to the host IP address of the compute host that is now the VM's new home."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:76(para)
-msgid "Update the VNC IP, if it isn't already updated, to: <literal>0.0.0.0</literal>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:83(para)
-msgid "Reboot the VM:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:87(para)
-msgid "In theory, the above database update and <literal>nova reboot</literal> command are all that is required to recover a VM from a failed host. However, if further problems occur, consider looking at recreating the network filter configuration using <literal>virsh</literal>, restarting the Compute services or updating the <literal>vm_state</literal> and <literal>power_state</literal> in the Compute database."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:95(title)
-msgid "Recover from a UID/GID mismatch"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:96(para)
-msgid "When running OpenStack Compute, using a shared file system or an automated configuration tool, you could encounter a situation where some files on your compute node are using the wrong UID or GID. This causes a number of errors, such as being unable to do live migration or start virtual machines."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:100(para)
-msgid "The following procedure runs on <systemitem class=\"service\">nova-compute</systemitem> hosts, based on the KVM hypervisor, and could help to restore the situation:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:104(title)
-msgid "To recover from a UID/GID mismatch"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:106(para)
-msgid "Ensure you do not use numbers that are already used for some other user/group."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:110(para)
-msgid "Set the nova uid in <filename>/etc/passwd</filename> to the same number in all hosts (for example, 112)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:114(para)
-msgid "Set the libvirt-qemu uid in <filename>/etc/passwd</filename> to the same number in all hosts (for example, 119)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:120(para)
-msgid "Set the nova group in <filename>/etc/group</filename> file to the same number in all hosts (for example, 120)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:126(para)
-msgid "Set the libvirtd group in <filename>/etc/group</filename> file to the same number in all hosts (for example, 119)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:132(para)
-msgid "Stop the services on the compute node."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:136(para)
-msgid "Change all the files owned by user <systemitem>nova</systemitem> or by group <systemitem>nova</systemitem>. For example:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:142(para)
-msgid "Repeat the steps for the libvirt-qemu owned files if those needed to change."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:146(para)
-msgid "Restart the services."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:149(para)
-msgid "Now you can run the <placeholder-1/> command to verify that all files using the correct identifiers."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:156(title)
-msgid "Recover cloud after disaster"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:157(para)
-msgid "Use the following procedures to manage your cloud after a disaster, and to easily back up its persistent storage volumes. Backups <emphasis role=\"bold\">are</emphasis> mandatory, even outside of disaster scenarios."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:160(para)
-msgid "For a DRP definition, see <link href=\"http://en.wikipedia.org/wiki/Disaster_Recovery_Plan\">http://en.wikipedia.org/wiki/Disaster_Recovery_Plan</link>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:164(title)
-msgid "Disaster recovery example"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:165(para)
-msgid "A disaster could happen to several components of your architecture (for example, a disk crash, a network loss, or a power cut). In this example, the following components are configured:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:170(para)
-msgid "A cloud controller (<systemitem>nova-api</systemitem>, <systemitem>nova-objectstore</systemitem>, <systemitem>nova-network</systemitem>)"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:175(para)
-msgid "A compute node (<systemitem class=\"service\">nova-compute</systemitem>)"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:180(para)
-msgid "A Storage Area Network (SAN) used by OpenStack Block Storage (<systemitem class=\"service\">cinder-volumes</systemitem>)"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:184(para)
-msgid "The worst disaster for a cloud is a power loss, which applies to all three components. Before a power loss:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:188(para)
-msgid "From the SAN to the cloud controller, we have an active iSCSI session (used for the \"cinder-volumes\" LVM's VG)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:192(para)
-msgid "From the cloud controller to the compute node, we also have active iSCSI sessions (managed by <systemitem class=\"service\">cinder-volume</systemitem>)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:197(para)
-msgid "For every volume, an iSCSI session is made (so 14 ebs volumes equals 14 sessions)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:201(para)
-msgid "From the cloud controller to the compute node, we also have iptables/ ebtables rules, which allow access from the cloud controller to the running instance."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:206(para)
-msgid "And at least, from the cloud controller to the compute node; saved into database, the current state of the instances (in that case \"running\" ), and their volumes attachment (mount point, volume ID, volume status, and so on.)"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:212(para)
-msgid "After the power loss occurs and all hardware components restart:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:215(para)
-msgid "From the SAN to the cloud, the iSCSI session no longer exists."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:218(para)
-msgid "From the cloud controller to the compute node, the iSCSI sessions no longer exist."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:222(para)
-msgid "From the cloud controller to the compute node, the iptables and ebtables are recreated, since at boot, <systemitem>nova-network</systemitem> reapplies configurations."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:227(para)
-msgid "From the cloud controller, instances are in a shutdown state (because they are no longer running)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:231(para)
-msgid "In the database, data was not updated at all, since Compute could not have anticipated the crash."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:235(para)
-msgid "Before going further, and to prevent the administrator from making fatal mistakes,<emphasis role=\"bold\"> instances won't be lost</emphasis>, because no \"<placeholder-1/>\" or \"<placeholder-2/>\" command was invoked, so the files for the instances remain on the compute node."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:240(para)
-msgid "Do not add any extra steps at this stage."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:239(para)
-msgid "Perform these tasks in the following order. <placeholder-1/>"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:244(para)
-msgid "Get the current relation from a volume to its instance, so that you can recreate the attachment."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:249(para)
-msgid "Update the database to clean the stalled state. (After that, you cannot perform the first step)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:254(para)
-msgid "Restart the instances. In other words, go from a shutdown to running state."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:259(para)
-msgid "After the restart, reattach the volumes to their respective instances (optional)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:263(para)
-msgid "SSH into the instances to reboot them."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:269(title)
-msgid "Recover after a disaster"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:271(title)
-msgid "To perform disaster recovery"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:273(title)
-msgid "Get the instance-to-volume relationship"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:275(para)
-msgid "You must determine the current relationship from a volume to its instance, because you will re-create the attachment."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:277(para)
-msgid "You can find this relationship by running <placeholder-1/>. Note that the <placeholder-2/> client includes the ability to get volume information from OpenStack Block Storage."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:283(title)
-msgid "Update the database"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:284(para)
-msgid "Update the database to clean the stalled state. You must restore for every volume, using these queries to clean up the database:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:291(para)
-msgid "You can then run <placeholder-1/> commands to list all volumes."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:295(title)
-msgid "Restart instances"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:297(replaceable)
-msgid "$instance"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:296(para)
-msgid "Restart the instances using the <placeholder-1/> command."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:298(para)
-msgid "At this stage, depending on your image, some instances completely reboot and become reachable, while others stop on the \"plymouth\" stage."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:303(title)
-msgid "DO NOT reboot a second time"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:304(para)
-msgid "Do not reboot instances that are stopped at this point. Instance state depends on whether you added an <filename>/etc/fstab</filename> entry for that volume. Images built with the <package>cloud-init</package> package remain in a pending state, while others skip the missing volume and start. The idea of that stage is only to ask Compute to reboot every instance, so the stored state is preserved. For more information about <package>cloud-init</package>, see <link href=\"https://help.ubuntu.com/community/CloudInit\">help.ubuntu.com/community/CloudInit</link>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:315(title)
-msgid "Reattach volumes"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:316(para)
-msgid "After the restart, and Compute has restored the right status, you can reattach the volumes to their respective instances using the <placeholder-1/> command. The following snippet uses a file of listed volumes to reattach them:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:330(para)
-msgid "At this stage, instances that were pending on the boot sequence (<application>plymouth</application>) automatically continue their boot, and restart normally, while the ones that booted see the volume."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:335(title)
-msgid "SSH into instances"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:336(para)
-msgid "If some services depend on the volume, or if a volume has an entry into <systemitem>fstab</systemitem>, you should now simply restart the instance. This restart needs to be made from the instance itself, not through <placeholder-1/>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:340(para)
-msgid "SSH into the instance and perform a reboot:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:344(para)
-msgid "By completing this procedure, you can successfully recover your cloud."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:347(para)
-msgid "Follow these guidelines:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:350(para)
-msgid "Use the <parameter> errors=remount</parameter> parameter in the <filename>fstab</filename> file, which prevents data corruption."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:353(para)
-msgid "The system locks any write to the disk if it detects an I/O error. This configuration option should be added into the <systemitem class=\"service\">cinder-volume</systemitem> server (the one which performs the iSCSI connection to the SAN), but also into the instances' <filename>fstab</filename> file."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:360(para)
-msgid "Do not add the entry for the SAN's disks to the <systemitem class=\"service\">cinder-volume</systemitem>'s <filename>fstab</filename> file."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:363(para)
-msgid "Some systems hang on that step, which means you could lose access to your cloud-controller. To re-run the session manually, run the following command before performing the mount: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:369(para)
-msgid "For your instances, if you have the whole <filename>/home/</filename> directory on the disk, leave a user's directory with the user's bash files and the <filename>authorized_keys</filename> file (instead of emptying the <filename>/home</filename> directory and mapping the disk on it)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:374(para)
-msgid "This enables you to connect to the instance, even without the volume attached, if you allow only connections through public keys."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:381(title)
-msgid "Script the DRP"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:382(para)
-msgid "You can download from <link href=\"https://github.com/Razique/BashStuff/blob/master/SYSTEMS/OpenStack/SCR_5006_V00_NUAC-OPENSTACK-DRP-OpenStack.sh\">here</link> a bash script which performs the following steps:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:386(para)
-msgid "An array is created for instances and their attached volumes."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:387(para)
-msgid "The MySQL database is updated."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:388(para)
-msgid "Using <systemitem>euca2ools</systemitem>, all instances are restarted."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:389(para)
-msgid "The volume attachment is made."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:390(para)
-msgid "An SSH connection is performed into every instance using Compute credentials."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:392(para)
-msgid "The \"test mode\" allows you to perform that whole sequence for only one instance."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:395(para)
-msgid "To reproduce the power loss, connect to the compute node which runs that same instance and close the iSCSI session. Do not detach the volume using the <placeholder-1/> command; instead, manually close the iSCSI session. For the following example command uses an iSCSI session with the number 15:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:400(para)
-msgid "Do not forget the <literal>-r</literal> flag. Otherwise, you close ALL sessions."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-instance-mgt-tools.xml:7(title)
-msgid "Instance management tools"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-instance-mgt-tools.xml:8(para)
-msgid "OpenStack provides command-line, web-based, and API-based instance management tools. Additionally, a number of third-party management tools are available, using either the native API or the provided EC2-compatible API."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-instance-mgt-tools.xml:13(para)
-msgid "The OpenStack <application>python-novaclient</application> package provides a basic command-line utility, which uses the <placeholder-1/> command. This is available as a native package for most Linux distributions, or you can install the latest version using the <application>pip</application> python package installer:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-instance-mgt-tools.xml:22(para)
-msgid "For more information about <application>python-novaclient</application> and other available command-line tools, see the <link href=\"http://docs.openstack.org/user-guide/content/index.html\"><citetitle>OpenStack End User Guide</citetitle></link>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:7(title)
-msgid "System administration"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:8(para)
-msgid "By understanding how the different installed nodes interact with each other, you can administer the Compute installation. Compute offers many ways to install using multiple servers but the general idea is that you can have multiple compute nodes that control the virtual servers and a cloud controller node that contains the remaining Compute services."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:15(para)
-msgid "The Compute cloud works through the interaction of a series of daemon processes named <systemitem>nova-*</systemitem> that reside persistently on the host machine or machines. These binaries can all run on the same machine or be spread out on multiple boxes in a large deployment. The responsibilities of services and drivers are:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:22(para)
-msgid "Services:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:25(para)
-msgid "<systemitem class=\"service\">nova-api</systemitem>. Receives xml requests and sends them to the rest of the system. It is a wsgi app that routes and authenticate requests. It supports the EC2 and OpenStack APIs. There is a <filename>nova-api.conf</filename> file created when you install Compute."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:32(para)
-msgid "<systemitem>nova-cert</systemitem>. Provides the certificate manager."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:36(para)
-msgid "<systemitem class=\"service\">nova-compute</systemitem>. Responsible for managing virtual machines. It loads a Service object, which exposes the public methods on ComputeManager through Remote Procedure Call (RPC)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:42(para)
-msgid "<systemitem>nova-conductor</systemitem>. Provides database-access support for Compute nodes (thereby reducing security risks)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:46(para)
-msgid "<systemitem>nova-consoleauth</systemitem>. Handles console authentication."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:50(para)
-msgid "<systemitem class=\"service\">nova-objectstore</systemitem>: The <systemitem class=\"service\">nova-objectstore</systemitem> service is an ultra simple file-based storage system for images that replicates most of the S3 API. It can be replaced with OpenStack Image Service and a simple image manager or use OpenStack Object Storage as the virtual machine image storage facility. It must reside on the same node as <systemitem class=\"service\">nova-compute</systemitem>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:59(para)
-msgid "<systemitem class=\"service\">nova-network</systemitem>. Responsible for managing floating and fixed IPs, DHCP, bridging and VLANs. It loads a Service object which exposes the public methods on one of the subclasses of NetworkManager. Different networking strategies are available to the service by changing the network_manager configuration option to FlatManager, FlatDHCPManager, or VlanManager (default is VLAN if no other is specified)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:68(para)
-msgid "<systemitem>nova-scheduler</systemitem>. Dispatches requests for new virtual machines to the correct node."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:72(para)
-msgid "<systemitem>nova-novncproxy</systemitem>. Provides a VNC proxy for browsers (enabling VNC consoles to access virtual machines)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:78(para)
-msgid "Some services have drivers that change how the service implements the core of its functionality. For example, the <systemitem>nova-compute</systemitem> service supports drivers that let you choose with which hypervisor type it will talk. <systemitem>nova-network</systemitem> and <systemitem>nova-scheduler</systemitem> also have drivers."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:87(title)
-msgid "Manage Compute users"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:88(para)
-msgid "Access to the Euca2ools (ec2) API is controlled by an access and secret key. The user’s access key needs to be included in the request, and the request must be signed with the secret key. Upon receipt of API requests, Compute verifies the signature and runs commands on behalf of the user."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:94(para)
-msgid "To begin using Compute, you must create a user with the Identity Service."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:102(title)
-msgid "Inject administrator password"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:103(para)
-msgid "You can configure Compute to generate a random administrator (root) password and inject that password into the instance. If this feature is enabled, a user can <placeholder-1/> to an instance without an <placeholder-2/> keypair. The random password appears in the output of the <placeholder-3/> command. You can also view and set the <literal>admin</literal> password from the dashboard."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:110(para)
-msgid "The dashboard is configured by default to display the <literal>admin</literal> password and allow the user to modify it."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:112(para)
-msgid "If you do not want to support password injection, we recommend disabling the password fields by editing your Dashboard <filename>local_settings</filename> file (file location will vary by Linux distribution, on Fedora/RHEL/CentOS: <filename> /etc/openstack-dashboard/local_settings</filename>, on Ubuntu and Debian: <filename>/etc/openstack-dashboard/local_settings.py</filename> and on openSUSE and SUSE Linux Enterprise Server: <filename>/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py</filename>) <placeholder-1/>"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:128(title)
-msgid "Libvirt-based hypervisors (KVM, QEMU, LXC)"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:129(para)
-msgid "For hypervisors such as KVM that use the libvirt backend, <literal>admin</literal> password injection is disabled by default. To enable it, set the following option in <filename>/etc/nova/nova.conf</filename>:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:136(para)
-msgid "When enabled, Compute will modify the password of the root account by editing the <filename>/etc/shadow</filename> file inside of the virtual machine instance."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:141(para)
-msgid "Users can only ssh to the instance by using the admin password if:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:145(para)
-msgid "The virtual machine image is a Linux distribution"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:149(para)
-msgid "The virtual machine has been configured to allow users to <placeholder-1/> as the root user. This is not the case for <link href=\"http://cloud-images.ubuntu.com/\">Ubuntu cloud images</link>, which disallow <placeholder-2/> to the root account by default."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:159(title)
-msgid "XenAPI (XenServer/XCP)"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:160(para)
-msgid "Compute uses the XenAPI agent to inject passwords into guests when using the XenAPI hypervisor backend. The virtual-machine image must be configured with the agent for password injection to work."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:165(title)
-msgid "Windows images (all hypervisors)"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:166(para)
-msgid "To support the <literal>admin</literal> password for Windows virtual machines, you must configure the Windows image to retrieve the <literal>admin</literal> password on boot by installing an agent such as <link href=\"https://github.com/cloudbase/cloudbase-init\">cloudbase-init</link>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:174(title)
-msgid "Manage the cloud"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:175(para)
-msgid "A system administrator can use the <placeholder-1/> client and the <placeholder-2/> commands to manage the cloud."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:177(para)
-msgid "Both nova client and euca2ools can be used by all users, though specific commands might be restricted by Role Based Access Control in the Identity Service."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:180(title)
-msgid "To use the nova client"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:182(para)
-msgid "Installing the <package>python-novaclient</package> package gives you a <code>nova</code> shell command that enables Compute API interactions from the command line. Install the client, and then provide your user name and password (typically set as environment variables for convenience), and then you have the ability to send commands to your cloud on the command line."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:187(para)
-msgid "To install <package>python-novaclient</package>, download the tarball from <link href=\"http://pypi.python.org/pypi/python-novaclient/2.6.3#downloads\">http://pypi.python.org/pypi/python-novaclient/2.6.3#downloads</link> and then install it in your favorite python environment."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:195(para) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:663(para)
-msgid "As <systemitem class=\"username\">root</systemitem> execute:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:199(para)
-msgid "Confirm the installation by running:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:214(para)
-msgid "This command returns a list of <placeholder-1/> commands and parameters. To obtain help for a subcommand, run:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:216(replaceable)
-msgid "subcommand"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:217(para)
-msgid "You can also refer to the <link href=\"http://docs.openstack.org/cli-reference/content/\"><citetitle>OpenStack Command-Line Reference</citetitle></link> for a complete listing of <placeholder-1/> commands and parameters."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:224(para)
-msgid "Set the required parameters as environment variables to make running commands easier. For example, you can add <parameter>--os-username</parameter> as a <placeholder-1/> option, or set it as an environment variable. To set the user name, password, and tenant as environment variables, use:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:233(para)
-msgid "Using the Identity Service, you are supplied with an authentication endpoint, which Compute recognizes as the <literal>OS_AUTH_URL</literal>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:242(title)
-msgid "Use the euca2ools commands"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:243(para)
-msgid "For a command-line interface to EC2 API calls, use the <placeholder-1/> command-line tool. See <link href=\"http://open.eucalyptus.com/wiki/Euca2oolsGuide_v1.3\">http://open.eucalyptus.com/wiki/Euca2oolsGuide_v1.3</link>"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:251(title)
-msgid "Manage logs"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:253(title)
-msgid "Logging module"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:254(para)
-msgid "To specify a configuration file to change the logging behavior, add this line to the <filename>/etc/nova/nova.conf</filename> file . To change the logging level, such as <literal>DEBUG</literal>, <literal>INFO</literal>, <literal>WARNING</literal>, <literal>ERROR</literal>), use: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:259(para)
-msgid "The logging configuration file is an ini-style configuration file, which must contain a section called <literal>logger_nova</literal>, which controls the behavior of the logging facility in the <literal>nova-*</literal> services. For example:<placeholder-1/>"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:269(para)
-msgid "For more details on the logging configuration syntax, including the meaning of the <literal>handlers</literal> and <literal>quaname</literal> variables, see the <link href=\"http://docs.python.org/release/2.7/library/logging.html#configuration-file-format\">Python documentation on logging configuration file format </link>f."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:277(para)
-msgid "For an example <filename>logging.conf</filename> file with various defined handlers, see the <link href=\"http://docs.openstack.org/trunk/config-reference/content/\"><citetitle>OpenStack Configuration Reference</citetitle></link>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:266(para)
-msgid "This example sets the debugging level to <literal>INFO</literal> (which less verbose than the default <literal>DEBUG</literal> setting). <placeholder-1/>"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:286(title)
-msgid "Syslog"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:287(para)
-msgid "You can configure OpenStack Compute services to send logging information to <systemitem>syslog</systemitem>. This is useful if you want to use <systemitem>rsyslog</systemitem>, which forwards the logs to a remote machine. You need to separately configure the Compute service (nova), the Identity service (keystone), the Image Service (glance), and, if you are using it, the Block Storage service (cinder) to send log messages to <systemitem>syslog</systemitem>. To do so, add the following lines to:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:296(filename)
-msgid "/etc/nova/nova.conf"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:299(filename)
-msgid "/etc/keystone/keystone.conf"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:302(filename)
-msgid "/etc/glance/glance-api.conf"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:305(filename)
-msgid "/etc/glance/glance-registry.conf"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:308(filename)
-msgid "/etc/cinder/cinder.conf"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:317(para)
-msgid "Although the example above uses the same local facility for each service (<literal>LOG_LOCAL0</literal>, which corresponds to <systemitem>syslog</systemitem> facility <literal>LOCAL0</literal>), we recommend that you configure a separate local facility for each service, as this provides better isolation and more flexibility. For example, you may want to capture logging information at different severity levels for different services. <systemitem>syslog</systemitem> allows you to define up to seven local facilities, <literal>LOCAL0, LOCAL1, ..., LOCAL7</literal>. For more details, see the <systemitem>syslog</systemitem> documentation."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:315(para)
-msgid "In addition to enabling <systemitem>syslog</systemitem>, these settings also turn off more verbose output and debugging output from the log.<placeholder-1/>"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:330(title)
-msgid "Rsyslog"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:331(para)
-msgid "<systemitem>rsyslog</systemitem> is a useful tool for setting up a centralized log server across multiple machines. We briefly describe the configuration to set up an <systemitem>rsyslog</systemitem> server; a full treatment of <systemitem>rsyslog</systemitem> is beyond the scope of this document. We assume <systemitem>rsyslog</systemitem> has already been installed on your hosts (default for most Linux distributions)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:337(para)
-msgid "This example provides a minimal configuration for <filename>/etc/rsyslog.conf</filename> on the log server host, which receives the log files:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:343(para)
-msgid "Add a filter rule to <filename>/etc/rsyslog.conf</filename> which looks for a host name. The example below uses <replaceable>compute-01</replaceable> as an example of a compute host name:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:346(replaceable)
-msgid "compute-01"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:347(para)
-msgid "On each compute host, create a file named <filename>/etc/rsyslog.d/60-nova.conf</filename>, with the following content:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:354(para)
-msgid "Once you have created this file, restart your <systemitem>rsyslog</systemitem> daemon. Error-level log messages on the compute hosts should now be sent to your log server."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:362(title)
-msgid "Migrate instances"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:363(para)
-msgid "Before starting migrations, review the <link linkend=\"section_configuring-compute-migrations\">Configure migrations section</link>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:364(para)
-msgid "Migration provides a scheme to migrate running instances from one OpenStack Compute server to another OpenStack Compute server."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:368(title)
-msgid "To migrate instances"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:370(para)
-msgid "Look at the running instances, to get the ID of the instance you wish to migrate."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:381(para)
-msgid "Look at information associated with that instance. This example uses 'vm1' from above."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:397(para)
-msgid "In this example, vm1 is running on HostB."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:400(para)
-msgid "Select the server to which instances will be migrated:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:412(para)
-msgid "In this example, HostC can be picked up because <systemitem class=\"service\">nova-compute</systemitem> is running on it."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:417(para)
-msgid "Ensure that HostC has enough resources for migration."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:431(para)
-msgid "<emphasis role=\"bold\">cpu:</emphasis>the number of cpu"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:436(para)
-msgid "<emphasis role=\"bold\">memory_mb:</emphasis>total amount of memory (in MB)"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:440(para)
-msgid "<emphasis role=\"bold\">disk_gb:</emphasis>total amount of space for NOVA-INST-DIR/instances (in GB)"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:444(para)
-msgid "<emphasis role=\"bold\">1st line shows </emphasis>total amount of resources for the physical server."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:448(para)
-msgid "<emphasis role=\"bold\">2nd line shows </emphasis>currently used resources."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:452(para)
-msgid "<emphasis role=\"bold\">3rd line shows </emphasis>maximum used resources."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:456(para)
-msgid "<emphasis role=\"bold\">4th line and under</emphasis> shows the resource for each project."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:464(replaceable)
-msgid "server"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:464(replaceable)
-msgid "host_name"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:463(para)
-msgid "Use the <placeholder-1/> command to migrate the instances:<placeholder-2/>"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:465(para)
-msgid "Where <replaceable>server</replaceable> can be either the server's ID or name. For example:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:473(para)
-msgid "Although the <placeholder-1/> command is called <placeholder-2/>, under the default Compute configuration options the instances are suspended before migration."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:477(para)
-msgid "For more details, see <link href=\"http://docs.openstack.org/trunk/config-reference/content/configuring-openstack-compute-basics.html\">Configure migrations</link> in <citetitle>OpenStack Configuration Reference</citetitle>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:469(para)
-msgid "Ensure instances are migrated successfully with <placeholder-1/>. If instances are still running on HostB, check log files (src/dest <systemitem class=\"service\">nova-compute</systemitem> and <systemitem class=\"service\">nova-scheduler</systemitem>) to determine why. <placeholder-2/>"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-security.xml:6(title)
-msgid "Security hardening"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-security.xml:7(para)
-msgid "OpenStack Compute can be integrated with various third-party technologies to increase security. For more information, see the <link href=\"http://docs.openstack.org/sec/\"><citetitle>OpenStack Security Guide</citetitle></link>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-security.xml:13(title)
-msgid "Encrypt Compute metadata traffic"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-security.xml:18(para)
-msgid "Enable the HTTPS protocol: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-security.xml:23(para)
-msgid "Determine whether insecure SSL connections are accepted for Compute metadata server requests. The default value is <option>False</option>: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-security.xml:31(replaceable)
-msgid "PATH_TO_CERT"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-security.xml:29(para)
-msgid "Specify the path to the client certificate: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-security.xml:36(replaceable)
-msgid "PATH_TO_KEY"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-security.xml:34(para)
-msgid "Specify the path to the private key: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-security.xml:14(para)
-msgid "OpenStack Juno supports encrypting Compute metadata traffic with HTTPS. Enable SSL encryption in the <filename>metadata_agent.ini</filename> file:<placeholder-1/>"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:7(title)
-msgid "Configure migrations"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:9(para)
-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:13(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:17(para)
-msgid "The migration types are:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:20(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."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:31(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:36(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:43(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: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 types of <firstterm>live migration</firstterm> are: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:53(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:57(title)
-msgid "KVM-Libvirt"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:59(title) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:264(title) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:339(title)
-msgid "Prerequisites"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:61(para)
-msgid "<emphasis role=\"bold\">Hypervisor:</emphasis> KVM with libvirt"
-msgstr ""
-
-#: ./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:74(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:81(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:88(para)
-msgid "This guide assumes the default value for <option>instances_path</option> 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."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:97(para)
-msgid "You must specify <literal>vncserver_listen=0.0.0.0</literal> or live migration does not work correctly."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:104(title)
-msgid "Example Compute installation environment"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:110(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:118(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:107(para)
-msgid "Prepare at least three servers; for example, <literal>HostA</literal>, <literal>HostB</literal>, and <literal>HostC</literal>: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:123(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:128(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."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:136(title)
-msgid "To configure your system"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:138(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:148(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:153(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:156(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 / Redhat: Setup NFS v4.0 File Server</link>"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:163(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:165(replaceable) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:180(replaceable) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:185(replaceable) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:191(replaceable) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:195(replaceable)
-msgid "NOVA-INST-DIR"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:166(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:174(para)
-msgid "Set the 'execute/search' bit on your shared directory."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:176(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:183(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:186(para)
-msgid "Ensure that you can mount the exported directory can be mounted:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:188(para)
-msgid "Check that HostA can see the \"<filename><replaceable>NOVA-INST-DIR</replaceable>/instances/</filename>\" directory:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:191(filename) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:195(filename)
-msgid "<placeholder-1/>/instances/"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:193(para)
-msgid "Perform the same check at HostB and HostC, paying special attention to the permissions (Compute should be able to write):"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:208(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."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:212(para)
-msgid "SSH tunnel to libvirtd's UNIX socket"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:213(para)
-msgid "libvirtd TCP socket, with GSSAPI/Kerberos for auth+data encryption"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:215(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:216(para)
-msgid "libvirtd TCP socket, with TLS for encryption and Kerberos for authentication"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:220(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:227(para)
-msgid "Configure your firewall to allow libvirt to communicate between nodes."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:229(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:237(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:245(title)
-msgid "Enable true live migration"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:246(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:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:251(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."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:260(title) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:493(th)
-msgid "XenServer"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:262(title)
-msgid "Shared storage"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:266(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:275(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:278(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:285(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."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:291(title)
-msgid "To use shared storage live migration with XenServer hypervisors"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:294(para)
-msgid "Add an NFS VHD storage to your master XenServer, and set it as default SR. For more information, please refer to the <link href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/reference.html#id1002701\">NFS VHD</link> section in the <citetitle>XenServer Administrator's Guide</citetitle>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:302(para)
-msgid "Configure all the compute nodes to use the default sr for pool operations. Add this line to your <filename>nova.conf</filename> configuration files across your compute nodes:<placeholder-1/>"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:309(para)
-msgid "Create a host aggregate:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:311(para)
-msgid "The command displays a table that contains the ID of the newly created aggregate."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:313(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:317(para)
-msgid "Make the first compute node part of that aggregate:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:320(para)
-msgid "At this point, the host is part of a XenServer pool."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:324(para)
-msgid "Add additional hosts to the pool:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:327(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."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:337(title)
-msgid "Block migration"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:341(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:350(para)
-msgid "To use block migration, you must use the CHANGE THIS == <parameter>==block-migrate</parameter> parameter with the live migration command."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:355(para)
-msgid "Block migration works only with EXT local storage SRs, and the server must not have any volumes attached."
-msgstr ""
-
 #. When image changes, this message will be marked fuzzy or untranslated for you.
 #. It doesn't matter what you translate it to: it's not used at all.
 #: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:255(None)
@@ -3136,11 +1020,11 @@ msgstr ""
 msgid "Resource"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:37(th) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:191(th) ./doc/admin-guide-cloud/networking/section_networking_arch.xml:35(th) ./doc/admin-guide-cloud/networking/section_networking_arch.xml:138(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:41(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:132(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:260(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:318(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:614(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:657(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:869(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:991(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1059(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1180(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1495(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1584(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1625(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:62(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:126(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:199(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:303(th)
+#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:37(th) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:191(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:62(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:126(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:199(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:303(th) ./doc/admin-guide-cloud/networking/section_networking_arch.xml:35(th) ./doc/admin-guide-cloud/networking/section_networking_arch.xml:138(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:41(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:132(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:260(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:318(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:614(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:657(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:869(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:991(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1059(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1180(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1495(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1584(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1625(th)
 msgid "Description"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:42(emphasis) ./doc/admin-guide-cloud/networking/section_networking_arch.xml:137(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:68(emphasis)
+#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:42(emphasis) ./doc/admin-guide-cloud/networking/section_networking-use.xml:68(emphasis) ./doc/admin-guide-cloud/networking/section_networking_arch.xml:137(th)
 msgid "Network"
 msgstr ""
 
@@ -3608,6 +1492,10 @@ msgstr ""
 msgid "Libvirt (KVM/QEMU)"
 msgstr ""
 
+#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:493(th) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:260(title)
+msgid "XenServer"
+msgstr ""
+
 #: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:494(th)
 msgid "VMware"
 msgstr ""
@@ -3632,7 +1520,7 @@ msgstr ""
 msgid "Cloudbase Hyper-V"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:533(td) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:102(emphasis) ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:29(td) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:452(title)
+#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:533(td) ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:29(td) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:102(emphasis) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:452(title)
 msgid "Linux Bridge"
 msgstr ""
 
@@ -3652,7 +1540,7 @@ msgstr ""
 msgid "NEC OpenFlow"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:573(td) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:79(emphasis) ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:24(td) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:12(title)
+#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:573(td) ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:24(td) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:79(emphasis) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:12(title)
 msgid "Open vSwitch"
 msgstr ""
 
@@ -3712,6 +1600,10 @@ msgstr ""
 msgid "Install the Brocade-modified Python netconf client (ncclient) library, which is available at <link href=\"https://github.com/brocade/ncclient\">https://github.com/brocade/ncclient</link>:"
 msgstr ""
 
+#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:663(para) ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:195(para)
+msgid "As <systemitem class=\"username\">root</systemitem> execute:"
+msgstr ""
+
 #: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:667(para)
 msgid "Edit the <filename>/etc/neutron/neutron.conf</filename> file and set the following option:"
 msgstr ""
@@ -4338,7 +2230,7 @@ msgstr ""
 msgid "There will be three hosts in the setup. <table rules=\"all\"><caption>Hosts for demo</caption><thead><tr><th>Host</th><th>Description</th></tr></thead><tbody><tr><td>OpenStack controller host - controlnode</td><placeholder-1/></tr><tr><td>HostA</td><td>Runs <systemitem class=\"service\">nova-compute</systemitem>, the Neutron L2 agent and DHCP agent</td></tr><tr><td>HostB</td><td>Same as HostA</td></tr></tbody></table>"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking-multi-dhcp-agents.xml:71(title) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:16(title) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:458(title) ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:146(th) ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:221(td) ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:256(td)
+#: ./doc/admin-guide-cloud/networking/section_networking-multi-dhcp-agents.xml:71(title) ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:146(th) ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:221(td) ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:256(td) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:16(title) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:458(title)
 msgid "Configuration"
 msgstr ""
 
@@ -4554,6 +2446,2460 @@ msgstr ""
 msgid "After deletion, if you restart the DHCP agent, it appears on the agent list again."
 msgstr ""
 
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:5(title)
+msgid "Use Networking"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:6(para)
+msgid "You can manage OpenStack Networking services using the <systemitem>service</systemitem> command. For example:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:13(para)
+msgid "Log files are in the <systemitem>/var/log/neutron</systemitem> directory."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:16(para)
+msgid "Configuration files are in the <systemitem>/etc/neutron</systemitem> directory."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:19(para)
+msgid "You can use Networking in the following ways:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:22(para)
+msgid "Expose the Networking API to cloud tenants, enabling them to build rich network topologies."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:26(para)
+msgid "Have the cloud administrator, or an automated administrative tool, create network connectivity on behalf of tenants."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:31(para)
+msgid "A tenant or cloud administrator can both perform the following procedures."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:34(title)
+msgid "Core Networking API features"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:35(para)
+msgid "After you install and run Networking, tenants and administrators can perform create-read-update-delete (CRUD) API networking operations by using the Networking API directly or the neutron command-line interface (CLI). The neutron CLI is a wrapper around the Networking API. Every Networking API call has a corresponding neutron command."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:42(para)
+msgid "The CLI includes a number of options. For details, refer to the <link href=\"http://docs.openstack.org/user-guide/content/\"><citetitle>OpenStack End User Guide</citetitle></link>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:48(title) ./doc/admin-guide-cloud/networking/section_networking-use.xml:56(caption)
+msgid "API abstractions"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:49(para)
+msgid "The Networking v2.0 API provides control over both L2 network topologies and their allocated IP addresses (IP Address Management or IPAM). There is also an extension to cover basic L3 forwarding and NAT, which provides capabilities similar to <placeholder-1/>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:61(th)
+msgid "Abstraction"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:69(td)
+msgid "An isolated L2 network segment (similar to a VLAN) that forms the basis for describing the L2 network topology available in an Networking deployment."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:78(td)
+msgid "Associates a block of IP addresses and other network configuration, such as default gateways or dns-servers, with an Networking network. Each subnet represents an IPv4 or IPv6 address block, and each Networking network can have multiple subnets."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:90(td)
+msgid "Represents an attachment port to a L2 Networking network. When a port is created on the network, by default it is allocated an available fixed IP address out of one of the designated subnets for each IP version (if one exists). When the port is destroyed, its allocated addresses return to the pool of available IPs on the subnet. Users of the Networking API can either choose a specific IP address from the block, or let Networking choose the first available IP address."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:109(para)
+msgid "This table summarizes the attributes available for each networking abstraction. For information about API abstraction and operations, see the <link href=\"http://docs.openstack.org/api/openstack-network/2.0/content/\">Networking API v2.0 Reference</link>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:116(caption)
+msgid "Network attributes"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:123(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:196(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:300(th)
+msgid "Attribute"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:124(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:197(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:301(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:130(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:258(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:316(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:612(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:655(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:867(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:989(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1057(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1178(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1582(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1623(th)
+msgid "Type"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:125(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1393(th)
+msgid "Default value"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:131(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:308(option) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:277(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1090(td)
+msgid "admin_state_up"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:132(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:154(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:233(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:309(td)
+msgid "bool"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:133(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:234(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:279(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:973(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1092(td) ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:20(td) ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:21(td) ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:25(td) ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:26(td) ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:30(td) ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:31(td)
+msgid "True"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:134(td)
+msgid "Administrative state of the network. If specified as False (down), this network does not forward packets."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:140(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:255(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:340(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:422(option) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:265(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:323(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:619(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:662(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:874(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:996(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1064(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1185(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1589(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1630(td)
+msgid "id"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:141(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:178(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:266(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:293(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:324(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:337(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:346(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:353(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:368(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:620(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:639(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:663(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:717(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:875(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:881(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:997(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1003(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1065(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1071(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1186(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1230(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1590(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1608(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1631(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1644(td)
+msgid "uuid-str"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:142(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:257(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:342(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:348(td)
+msgid "Generated"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:143(td)
+msgid "UUID for this network."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:146(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:267(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:352(option) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:271(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:625(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:887(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1009(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1077(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1199(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1595(td)
+msgid "name"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:147(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:164(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:219(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:240(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:268(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:317(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:325(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:347(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:353(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:367(td)
+msgid "string"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:148(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:269(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:318(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:326(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:354(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:273(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:627(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:634(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:682(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:688(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:694(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:700(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:706(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:889(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:895(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:920(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:932(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:938(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:945(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:952(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:958(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1011(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1017(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1032(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1079(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1085(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1128(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1201(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1597(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1603(td)
+msgid "None"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:149(td)
+msgid "Human-readable name for this network; is not required to be unique."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:153(option) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:910(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1022(td)
+msgid "shared"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:155(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:912(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1024(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1039(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1447(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1653(td)
+msgid "False"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:156(td)
+msgid "Specifies whether this network resource can be accessed by any tenant. The default policy setting restricts usage of this attribute to administrative users only."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:163(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:366(option) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:284(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1097(td)
+msgid "status"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:165(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:179(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:220(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:276(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:283(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:361(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:368(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:375(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:139(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:164(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:286(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:294(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:338(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:347(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:369(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:640(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:676(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:718(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:882(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1004(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1072(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1099(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1213(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1231(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1609(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1645(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1661(td)
+msgid "N/A"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:166(td)
+msgid "Indicates whether this network is currently operational."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:170(option)
+msgid "subnets"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:171(td)
+msgid "list(uuid-str)"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:172(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:227(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:249(td)
+msgid "Empty list"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:173(td)
+msgid "List of subnets associated with this network."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:177(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:281(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:373(option) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:292(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:367(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:638(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:716(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:880(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1002(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1070(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1229(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1607(td)
+msgid "tenant_id"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:180(td)
+msgid "Tenant owner of the network. Only administrative users can set the tenant identifier; this cannot be changed using authorization policies."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:189(caption)
+msgid "Subnet attributes"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:198(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:302(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:131(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:259(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:317(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:613(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:656(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:868(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:990(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1058(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1179(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1583(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1624(th)
+msgid "Default Value"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:204(option)
+msgid "allocation_pools"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:205(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:248(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:332(td)
+msgid "list(dict)"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:207(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:218(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:241(option) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1724(replaceable)
+msgid "cidr"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:208(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:239(option)
+msgid "gateway_ip"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:206(td)
+msgid "Every address in <placeholder-1/>, excluding <placeholder-2/> (if configured)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:210(para)
+msgid "List of cidr sub-ranges that are available for dynamic allocation to ports. Syntax:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:221(td)
+msgid "IP range for this subnet, based on the IP version."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:225(option)
+msgid "dns_nameservers"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:226(td)
+msgid "list(string)"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:228(td)
+msgid "List of DNS name servers used by hosts in this subnet."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:232(option)
+msgid "enable_dhcp"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:235(td)
+msgid "Specifies whether DHCP is enabled for this subnet."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:241(td)
+msgid "First address in <placeholder-1/>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:243(td)
+msgid "Default gateway used by devices in this subnet."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:247(option)
+msgid "host_routes"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:250(td)
+msgid "Routes that should be used by devices with IPs from this subnet (not including local subnet route)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:256(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:275(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:282(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:341(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:360(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:374(td)
+msgid "uuid-string"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:258(td)
+msgid "UUID representing this subnet."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:261(option) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:924(td)
+msgid "ip_version"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:262(td)
+msgid "int"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:263(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:926(td)
+msgid "4"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:264(td)
+msgid "IP version."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:270(td)
+msgid "Human-readable name for this subnet (might not be unique)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:274(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:359(option)
+msgid "network_id"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:277(td)
+msgid "Network with which this subnet is associated."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:284(td)
+msgid "Owner of network. Only administrative users can set the tenant identifier; this cannot be changed using authorization policies."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:293(caption)
+msgid "Port attributes"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:310(td)
+msgid "true"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:311(td)
+msgid "Administrative state of this port. If specified as False (down), this port does not forward packets."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:316(option)
+msgid "device_id"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:319(td)
+msgid "Identifies the device using this port (for example, a virtual server's ID)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:324(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:424(option)
+msgid "device_owner"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:327(td)
+msgid "Identifies the entity using this port (for example, a dhcp agent)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:331(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:423(option)
+msgid "fixed_ips"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:333(td)
+msgid "Automatically allocated from pool"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:334(td)
+msgid "Specifies IP addresses for this port; associates the port with the subnets containing the listed IP addresses."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:343(td)
+msgid "UUID for this port."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:346(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:568(option)
+msgid "mac_address"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:349(td)
+msgid "Mac address to use on this port."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:355(td)
+msgid "Human-readable name for this port (might not be unique)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:362(td)
+msgid "Network with which this port is associated."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:369(td)
+msgid "Indicates whether the network is currently operational."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:376(td)
+msgid "Owner of the network. Only administrative users can set the tenant identifier; this cannot be changed using authorization policies."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:386(title) ./doc/admin-guide-cloud/networking/section_networking-use.xml:396(caption)
+msgid "Basic Networking operations"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:387(para)
+msgid "To learn about advanced capabilities available through the neutron command-line interface (CLI), read the networking section in the <link href=\"http://docs.openstack.org/user-guide/content/index.html\"> OpenStack End User Guide</link>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:392(para)
+msgid "This table shows example neutron commands that enable you to complete basic network operations:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:401(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:482(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:614(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:390(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:735(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1247(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1680(th)
+msgid "Operation"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:402(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:483(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:542(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:615(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:391(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:736(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1248(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1681(th)
+msgid "Command"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:407(td)
+msgid "Creates a network."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:411(td)
+msgid "Creates a subnet that is associated with net1."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:416(td)
+msgid "Lists ports for a specified tenant."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:421(td)
+msgid "Lists ports for a specified tenant and displays the <placeholder-1/>, <placeholder-2/>, and <placeholder-3/> columns."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:430(td)
+msgid "Shows information for a specified port."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:432(replaceable) ./doc/admin-guide-cloud/networking/section_networking-use.xml:574(replaceable) ./doc/admin-guide-cloud/networking/section_networking-use.xml:627(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:631(replaceable)
+msgid "port-id"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:437(para)
+msgid "The <option>device_owner</option> field describes who owns the port. A port whose <option>device_owner</option> begins with:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:443(para)
+msgid "<literal>network</literal> is created by Networking."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:447(para)
+msgid "<literal>compute</literal> is created by Compute."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:454(title)
+msgid "Administrative operations"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:455(para)
+msgid "The cloud administrator can run any <placeholder-1/> command on behalf of tenants by specifying an Identity <option>tenant_id</option> in the command, as follows:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:460(replaceable)
+msgid "tenant-id"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:460(replaceable)
+msgid "network-name"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:461(para) ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:47(para) ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:61(para) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:244(para) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:268(para) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:278(para) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:295(para) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:325(para) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:331(para) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:518(para)
+msgid "For example:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:464(para)
+msgid "To view all tenant IDs in Identity, run the following command as an Identity Service admin user:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:472(title) ./doc/admin-guide-cloud/networking/section_networking-use.xml:477(caption)
+msgid "Advanced Networking operations"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:473(para)
+msgid "This table shows example Networking commands that enable you to complete advanced network operations:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:488(td)
+msgid "Creates a network that all tenants can use."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:493(td)
+msgid "Creates a subnet with a specified gateway IP address."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:498(td)
+msgid "Creates a subnet that has no gateway IP address."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:503(td)
+msgid "Creates a subnet with DHCP disabled."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:508(td)
+msgid "Creates a subnet with a specified set of host routes."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:513(td)
+msgid "Creates a subnet with a specified set of dns name servers."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:518(td)
+msgid "Displays all ports and IPs allocated on a network."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:520(replaceable) ./doc/admin-guide-cloud/networking/section_networking-use.xml:553(replaceable) ./doc/admin-guide-cloud/networking/section_networking-use.xml:629(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:630(replaceable)
+msgid "net-id"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:528(title)
+msgid "Use Compute with Networking"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:530(title) ./doc/admin-guide-cloud/networking/section_networking-use.xml:535(caption)
+msgid "Basic Compute and Networking operations"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:531(para)
+msgid "This table shows example neutron and nova commands that enable you to complete basic VM networking operations:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:541(th)
+msgid "Action"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:547(td)
+msgid "Checks available networks."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:551(td)
+msgid "Boots a VM with a single NIC on a selected Networking network."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:553(replaceable) ./doc/admin-guide-cloud/networking/section_networking-use.xml:621(replaceable) ./doc/admin-guide-cloud/networking/section_networking-use.xml:631(replaceable) ./doc/admin-guide-cloud/networking/section_networking-use.xml:640(replaceable)
+msgid "img"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:553(replaceable) ./doc/admin-guide-cloud/networking/section_networking-use.xml:621(replaceable) ./doc/admin-guide-cloud/networking/section_networking-use.xml:631(replaceable) ./doc/admin-guide-cloud/networking/section_networking-use.xml:640(replaceable)
+msgid "flavor"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:553(replaceable) ./doc/admin-guide-cloud/networking/section_networking-use.xml:621(replaceable) ./doc/admin-guide-cloud/networking/section_networking-use.xml:631(replaceable) ./doc/admin-guide-cloud/networking/section_networking-use.xml:640(replaceable)
+msgid "vm-name"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:557(para)
+msgid "Searches for ports with a <option>device_id</option> that matches the Compute instance UUID. See <xref linkend=\"network_compute_note\"/>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:564(replaceable) ./doc/admin-guide-cloud/networking/section_networking-use.xml:569(replaceable)
+msgid "vm-id"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:567(td)
+msgid "Searches for ports, but shows only the <placeholder-1/> of the port."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:572(td)
+msgid "Temporarily disables a port from sending traffic."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:579(para)
+msgid "The <option>device_id</option> can also be a logical router ID."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:583(title)
+msgid "Create and delete VMs"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:586(para)
+msgid "When you boot a Compute VM, a port on the network that corresponds to the VM NIC is automatically created and associated with the default security group. You can configure <link linkend=\"enabling_ping_and_ssh\">security group rules</link> to enable users to access the VM."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:596(para)
+msgid "When you delete a Compute VM, the underlying Networking port is automatically deleted."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:604(title) ./doc/admin-guide-cloud/networking/section_networking-use.xml:609(caption)
+msgid "Advanced VM creation operations"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:605(para)
+msgid "This table shows example nova and neutron commands that enable you to complete advanced VM creation operations:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:620(td)
+msgid "Boots a VM with multiple NICs."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:621(replaceable)
+msgid "net1-id"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:621(replaceable)
+msgid "net2-id"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:624(td)
+msgid "Boots a VM with a specific IP address. First, create an Networking port with a specific IP address. Then, boot a VM specifying a <placeholder-1/> rather than a <placeholder-2/>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:630(replaceable)
+msgid "subnet-id"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:630(replaceable)
+msgid "IP"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:638(parameter)
+msgid "--nic"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:635(td)
+msgid "Boots a VM that connects to all networks that are accessible to the tenant who submits the request (without the <placeholder-1/> option)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:646(para)
+msgid "Networking does not currently support the <parameter>v4-fixed-ip</parameter> parameter of the <parameter>--nic</parameter> option for the <placeholder-1/> command."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:653(title)
+msgid "Enable ping and SSH on VMs (security groups)"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:655(para)
+msgid "You must configure security group rules depending on the type of plug-in you are using. If you are using a plug-in that:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:660(para)
+msgid "Implements Networking security groups, you can configure security group rules directly by using <placeholder-1/>. This example enables <placeholder-2/> and <placeholder-3/> access to your VMs."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:674(para)
+msgid "Does not implement Networking security groups, you can configure security group rules by using the <placeholder-1/> or <placeholder-2/> command. These <placeholder-3/> commands enable <placeholder-4/> and <placeholder-5/> access to your VMs."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:688(para)
+msgid "If your plug-in implements Networking security groups, you can also leverage Compute security groups by setting <code>security_group_api = neutron</code> in the <filename>nova.conf</filename> file. After you set this option, all Compute security group commands are proxied to Networking."
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:123(None)
+msgid "@@image: '../../common/figures/Neutron-PhysNet-Diagram.png'; md5=ea581fd58c57da1a6c9512b82027a195"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:199(None)
+msgid "@@image: '../../common/figures/NetworkTypes.png'; md5=c424894383b701a38a6dc3ccf2e916f3"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:286(None)
+msgid "@@image: '../../common/figures/vmware_nsx.png'; md5=fba7420fae8c2cb386147408e7a06416"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:5(title)
+msgid "Networking architecture"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:6(para)
+msgid "Before you deploy Networking, it's useful to understand the Networking services and how they interact with the OpenStack components."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:10(title)
+msgid "Overview"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:11(para)
+msgid "Networking is a standalone component in the OpenStack modular architecture. It's positioned alongside OpenStack components such as Compute, Image Service, Identity, or the Dashboard. Like those components, a deployment of Networking often involves deploying several services to a variety of hosts."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:16(para)
+msgid "The Networking server uses the <systemitem class=\"service\">neutron-server</systemitem> daemon to expose the Networking API and enable administration of the configured Networking plug-in. Typically, the plug-in requires access to a database for persistent storage (also similar to other OpenStack services)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:22(para)
+msgid "If your deployment uses a controller host to run centralized Compute components, you can deploy the Networking server to that same host. However, Networking is entirely standalone and can be deployed to a dedicated host. Depending on your configuration, Networking can also include the following agents:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:29(caption)
+msgid "Networking agents"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:34(th) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:98(td) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:121(td)
+msgid "Agent"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:40(emphasis)
+msgid "plug-in agent"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:42(literal)
+msgid "neutron-*-agent"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:40(td) ./doc/admin-guide-cloud/networking/section_networking_arch.xml:49(td) ./doc/admin-guide-cloud/networking/section_networking_arch.xml:56(td) ./doc/admin-guide-cloud/networking/section_networking_arch.xml:64(td)
+msgid "<placeholder-1/> (<placeholder-2/>)"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:43(td)
+msgid "Runs on each hypervisor to perform local vSwitch configuration. The agent that runs, depends on the plug-in that you use. Certain plug-ins do not require an agent."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:49(emphasis)
+msgid "dhcp agent"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:51(literal)
+msgid "neutron-dhcp-agent"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:52(td)
+msgid "Provides DHCP services to tenant networks. Required by certain plug-ins."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:56(emphasis)
+msgid "l3 agent"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:58(literal)
+msgid "neutron-l3-agent"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:59(td)
+msgid "Provides L3/NAT forwarding to provide external network access for VMs on tenant networks. Required by certain plug-ins."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:64(emphasis)
+msgid "metering agent"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:65(literal)
+msgid "neutron-metering-agent"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:66(td)
+msgid "Provides L3 traffic metering for tenant networks."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:71(para)
+msgid "These agents interact with the main neutron process through RPC (for example, RabbitMQ or Qpid) or through the standard Networking API. In addition, Networking integrates with OpenStack components in a number of ways:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:77(para)
+msgid "Networking relies on the Identity service (keystone) for the authentication and authorization of all API requests."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:82(para)
+msgid "Compute (nova) interacts with Networking through calls to its standard API. As part of creating a VM, the <systemitem class=\"service\">nova-compute</systemitem> service communicates with the Networking API to plug each virtual NIC on the VM into a particular network."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:91(para)
+msgid "The dashboard (horizon) integrates with the Networking API, enabling administrators and tenant users to create and manage network services through a web-based GUI."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:99(title)
+msgid "Place services on physical hosts"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:100(para)
+msgid "Like other OpenStack services, Networking enables you to run services across multiple physical devices. It is also possible to run all service daemons on a single physical host for evaluation purposes. Alternatively, you can run each service on a dedicated physical host and replicate certain services across multiple hosts for redundancy purposes. For more information, see the <citetitle>OpenStack Configuration Reference</citetitle>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:107(para)
+msgid "A standard architectural design includes a cloud controller host, a network gateway host, and a number of hypervisors for hosting virtual machines. The cloud controller and network gateway can be on the same host. However, if you expect VMs to send significant traffic to or from the Internet, a dedicated network gateway host helps avoid CPU contention between the <systemitem class=\"service\">neutron-l3-agent</systemitem> and other OpenStack services that forward packets."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:118(title)
+msgid "Network connectivity for physical hosts"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:126(para)
+msgid "A standard Networking deployment includes one or more of the following physical networks:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:131(caption)
+msgid "General distinct physical data center networks"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:143(emphasis)
+msgid "Management network"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:145(td)
+msgid "Provides internal communication between OpenStack components. IP addresses on this network should be reachable only within the data center."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:151(emphasis)
+msgid "Data network"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:153(td)
+msgid "Provides VM data communication within the cloud deployment. The IP addressing requirements of this network depend on the Networking plug-in that is used."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:160(emphasis)
+msgid "External network"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:162(td)
+msgid "Provides VMs with Internet access in some deployment scenarios. Anyone on the Internet can reach IP addresses on this network."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:168(emphasis)
+msgid "API network"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:170(td)
+msgid "Exposes all OpenStack APIs, including the Networking API, to tenants. IP addresses on this network should be reachable by anyone on the Internet. The API network might be the same as the external network, because it is possible to create an external-network subnet that has allocated IP ranges that use less than the full range of IP addresses in an IP block."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:187(title) ./doc/admin-guide-cloud/networking/section_networking_arch.xml:195(title)
+msgid "Tenant and provider networks"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:188(para)
+msgid "The following diagram presents an overview of the tenant and provider network types, and illustrates how they interact within the overall Networking topology:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:205(title)
+msgid "Tenant networks"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:206(para)
+msgid "Users create tenant networks for connectivity within projects; they are fully isolated by default and are not shared with other projects. Networking supports a range of tenant network types:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:214(term)
+msgid "Flat"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:216(para)
+msgid "All instances reside on the same network, which can also be shared with the hosts. No VLAN tagging or other network segregation takes place."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:223(term)
+msgid "Local"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:225(para)
+msgid "Instances reside on the local compute host and are effectively isolated from any external networks."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:231(term)
+msgid "VLAN"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:233(para)
+msgid "Networking allows users to create multiple provider or tenant networks using VLAN IDs (802.1Q tagged) that correspond to VLANs present in the physical network. This allows instances to communicate with each other across the environment. They can also communicate with dedicated servers, firewalls, load balancers and other networking infrastructure on the same layer 2 VLAN."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:243(term)
+msgid "VXLAN and GRE"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:245(para)
+msgid "VXLAN and GRE use network overlays to support private communication between instances. A Networking router is required to enable traffic to traverse outside of the GRE or VXLAN tenant network. A router is also required to connect directly-connected tenant networks with external networks, including the Internet; the router provides the ability to connect to instances directly from an external network using floating IP addresses."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:258(title) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:11(title)
+msgid "Provider networks"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:259(para)
+msgid "Provider networks are created by the OpenStack administrator and map directly to an existing physical network in the data center. Useful network types in this category are flat (untagged) and VLAN (802.1Q tagged). It is possible to allow provider networks to be shared among tenants as part of the network creation process."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:267(title)
+msgid "VMware NSX integration"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:268(para)
+msgid "OpenStack Networking uses the NSX plugin for Networking to integrate with an existing VMware vCenter deployment. When installed on the network nodes, the NSX plugin enables a NSX controller to centrally manage configuration settings and push them to managed network nodes. Network nodes are considered managed when they're added as hypervisors to the NSX controller."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:274(para)
+msgid "The diagram below depicts an example NSX deployment and illustrates the route inter-VM traffic takes between separate Compute nodes. Note the placement of the VMware NSX plugin and the <systemitem class=\"service\">neutron-server</systemitem> service on the network node. The NSX controller features centrally with a green line to the network node to indicate the management relationship:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:281(title)
+msgid "VMware NSX overview"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:6(title)
+msgid "Advanced features through API extensions"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:7(para)
+msgid "Several plug-ins implement API extensions that provide capabilities similar to what was available in nova-network: These plug-ins are likely to be of interest to the OpenStack community."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:12(para)
+msgid "Networks can be categorized as either \"tenant networks\" or \"provider networks\". Tenant networks are created by normal users and details about how they are physically realized are hidden from those users. Provider networks are created with administrative credentials, specifying the details of how the network is physically realized, usually to match some existing network in the data center."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:17(para)
+msgid "Provider networks enable cloud administrators to create Networking networks that map directly to the physical networks in the data center. This is commonly used to give tenants direct access to a public network that can be used to reach the Internet. It might also be used to integrate with VLANs in the network that already have a defined meaning (for example, enable a VM from the \"marketing\" department to be placed on the same VLAN as bare-metal marketing hosts in the same data center)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:23(para)
+msgid "The provider extension allows administrators to explicitly manage the relationship between Networking virtual networks and underlying physical mechanisms such as VLANs and tunnels. When this extension is supported, Networking client users with administrative privileges see additional provider attributes on all virtual networks and are able to specify these attributes in order to create provider networks."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:28(para)
+msgid "The provider extension is supported by the Open vSwitch and Linux Bridge plug-ins. Configuration of these plug-ins requires familiarity with this extension."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:31(title)
+msgid "Terminology"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:32(para)
+msgid "A number of terms are used in the provider extension and in the configuration of plug-ins supporting the provider extension:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:35(caption)
+msgid "Provider extension terminology"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:40(th)
+msgid "Term"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:46(emphasis)
+msgid "virtual network"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:47(td)
+msgid "An Networking L2 network (identified by a UUID and optional name) whose ports can be attached as vNICs to Compute instances and to various Networking agents. The Open vSwitch and Linux Bridge plug-ins each support several different mechanisms to realize virtual networks."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:53(emphasis)
+msgid "physical network"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:54(td)
+msgid "A network connecting virtualization hosts (such as compute nodes) with each other and with other network resources. Each physical network might support multiple virtual networks. The provider extension and the plug-in configurations identify physical networks using simple string names."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:61(emphasis)
+msgid "tenant network"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:62(td)
+msgid "A virtual network that a tenant or an administrator creates. The physical details of the network are not exposed to the tenant."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:66(emphasis)
+msgid "provider network"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:67(td)
+msgid "A virtual network administratively created to map to a specific network in the data center, typically to enable direct access to non-OpenStack resources on that network. Tenants can be given access to provider networks."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:73(emphasis)
+msgid "VLAN network"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:74(td)
+msgid "A virtual network implemented as packets on a specific physical network containing IEEE 802.1Q headers with a specific VID field value. VLAN networks sharing the same physical network are isolated from each other at L2 and can even have overlapping IP address spaces. Each distinct physical network supporting VLAN networks is treated as a separate VLAN trunk, with a distinct space of VID values. Valid VID values are 1 through 4094."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:83(emphasis)
+msgid "flat network"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:84(td)
+msgid "A virtual network implemented as packets on a specific physical network containing no IEEE 802.1Q header. Each physical network can realize at most one flat network."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:89(emphasis)
+msgid "local network"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:90(td)
+msgid "A virtual network that allows communication within each host, but not across a network. Local networks are intended mainly for single-node test scenarios, but can have other uses."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:95(emphasis)
+msgid "GRE network"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:98(emphasis)
+msgid "tunnels"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:96(td)
+msgid "A virtual network implemented as network packets encapsulated using GRE. GRE networks are also referred to as <placeholder-1/>. GRE tunnel packets are routed by the IP routing table for the host, so GRE networks are not associated by Networking with specific physical networks."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:103(emphasis)
+msgid "Virtual Extensible LAN (VXLAN) network"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:105(td)
+msgid "VXLAN is a proposed encapsulation protocol for running an overlay network on existing Layer 3 infrastructure. An overlay network is a virtual network that is built on top of existing network Layer 2 and Layer 3 technologies to support elastic compute architectures."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:112(para)
+msgid "The ML2, Open vSwitch, and Linux Bridge plug-ins support VLAN networks, flat networks, and local networks. Only the ML2 and Open vSwitch plug-ins currently support GRE and VXLAN networks, provided that the required features exist in the hosts Linux kernel, Open vSwitch, and iproute2 packages."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:118(title)
+msgid "Provider attributes"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:119(para)
+msgid "The provider extension extends the Networking network resource with these attributes:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:122(caption)
+msgid "Provider network attributes"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:129(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:257(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:315(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:611(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:654(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:866(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:988(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1056(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1177(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1492(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1581(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1622(th)
+msgid "Attribute name"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:137(td)
+msgid "provider:network_type"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:138(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:152(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:272(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:285(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:626(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:633(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:675(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:681(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:699(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:888(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:894(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:919(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:965(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1010(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1016(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1078(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1084(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1098(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1200(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1218(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1596(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1602(td)
+msgid "String"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:141(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:154(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:168(literal)
+msgid "flat"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:141(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:146(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:155(literal)
+msgid "vlan"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:142(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:147(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:158(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:169(literal)
+msgid "local"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:142(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:146(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:158(literal) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:739(replaceable)
+msgid "gre"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:140(td)
+msgid "The physical mechanism by which the virtual network is implemented. Possible values are <placeholder-1/>, <placeholder-2/>, <placeholder-3/>, and <placeholder-4/>, corresponding to flat networks, VLAN networks, local networks, and GRE networks as defined above. All types of provider networks can be created by administrators, while tenant networks can be implemented as <placeholder-5/>, <placeholder-6/>, or <placeholder-7/> network types depending on plug-in configuration."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:151(td)
+msgid "provider:physical_network"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:153(td)
+msgid "If a physical network named \"default\" has been configured and if provider:network_type is <placeholder-1/> or <placeholder-2/>, then \"default\" is used."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:156(td)
+msgid "The name of the physical network over which the virtual network is implemented for flat and VLAN networks. Not applicable to the <placeholder-1/> or <placeholder-2/> network types."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:162(td)
+msgid "provider:segmentation_id"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:163(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:687(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:693(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:957(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1206(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1212(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1224(td)
+msgid "Integer"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:165(td)
+msgid "For VLAN networks, the VLAN VID on the physical network that realizes the virtual network. Valid VLAN VIDs are 1 through 4094. For GRE networks, the tunnel ID. Valid tunnel IDs are any 32 bit unsigned integer. Not applicable to the <placeholder-1/> or <placeholder-2/> network types."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:173(para)
+msgid "To view or set provider extended attributes, a client must be authorized for the <code>extension:provider_network:view</code> and <code>extension:provider_network:set</code> actions in the Networking policy configuration. The default Networking configuration authorizes both actions for users with the admin role. An authorized client or an administrative user can view and set the provider extended attributes through Networking API calls. See <xref linkend=\"section_networking_auth\"/> for details on policy configuration."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:182(title)
+msgid "Provider extension API operations"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:183(para)
+msgid "To use the provider extension with the default policy settings, you must have the administrative role."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:185(para)
+msgid "This list shows example neutron commands that enable you to complete basic provider extension API operations:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:189(para)
+msgid "Shows all attributes of a network, including provider attributes:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:194(para)
+msgid "Creates a local provider network:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:198(para)
+msgid "When you create flat networks, &lt;phys-net-name&gt; must be known to the plug-in. See the <citetitle>OpenStack Configuration Reference</citetitle> for details. Creates a flat provider network:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:205(para)
+msgid "When you create VLAN networks, &lt;phys-net-name&gt; must be known to the plug-in. See the <citetitle>OpenStack Configuration Reference</citetitle> for details on configuring network_vlan_ranges to identify all physical networks. When you create VLAN networks, &lt;VID&gt; can fall either within or outside any configured ranges of VLAN IDs from which tenant networks are allocated. Creates a VLAN provider network:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:216(para)
+msgid "When you create GRE networks, &lt;tunnel-id&gt; can be either inside or outside any tunnel ID ranges from which tenant networks are allocated."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:219(para)
+msgid "After you create provider networks, you can allocate subnets, which you can use in the same way as other virtual networks, subject to authorization policy based on the specified &lt;tenant_id&gt;. Creates a GRE provider network:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:229(title)
+msgid "L3 routing and NAT"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:230(para)
+msgid "The Networking API provides abstract L2 network segments that are decoupled from the technology used to implement the L2 network. Networking includes an API extension that provides abstract L3 routers that API users can dynamically provision and configure. These Networking routers can connect multiple L2 Networking networks and can also provide a gateway that connects one or more private L2 networks to a shared external network. For example, a public network for access to the Internet. See the <citetitle>OpenStack Configuration Reference</citetitle> for details on common models of deploying Networking L3 routers."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:239(para)
+msgid "The L3 router provides basic NAT capabilities on gateway ports that uplink the router to external networks. This router SNATs all traffic by default and supports floating IPs, which creates a static one-to-one mapping from a public IP on the external network to a private IP on one of the other subnets attached to the router. This allows a tenant to selectively expose VMs on private networks to other hosts on the external network (and often to all hosts on the Internet). You can allocate and map floating IPs from one port to another, as needed."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:248(title)
+msgid "L3 API abstractions"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:250(caption)
+msgid "Router"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:267(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:325(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:621(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:664(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:876(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:998(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1066(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1187(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1591(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1632(td)
+msgid "generated"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:268(td)
+msgid "UUID for the router."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:274(td)
+msgid "Human-readable name for the router. Might not be unique."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:278(td)
+msgid "Bool"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:280(td)
+msgid "The administrative state of router. If false (down), the router does not forward packets."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:288(para)
+msgid "Indicates whether router is currently operational."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:295(td)
+msgid "Owner of the router. Only admin users can specify a tenant_id other than its own."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:299(td)
+msgid "external_gateway_info"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:300(td)
+msgid "dict contain 'network_id' key-value pair"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:301(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:354(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:361(td)
+msgid "Null"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:302(td)
+msgid "External network that this router connects to for gateway services (for example, NAT)"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:308(caption)
+msgid "Floating IP"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:326(td)
+msgid "UUID for the floating IP."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:329(td)
+msgid "floating_ip_address"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:330(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:360(td)
+msgid "string (IP address)"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:331(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:670(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:902(td)
+msgid "allocated by Networking"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:332(td)
+msgid "The external network IP address available to be mapped to an internal IP address."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:336(td)
+msgid "floating_network_id"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:340(para)
+msgid "The network indicating the set of subnets from which the floating IP should be allocated"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:345(td)
+msgid "router_id"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:348(td)
+msgid "Read-only value indicating the router that connects the external network to the associated internal port, if a port is associated."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:352(td)
+msgid "port_id"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:355(td)
+msgid "Indicates the internal Networking port associated with the external floating IP."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:359(td)
+msgid "fixed_ip_address"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:362(td)
+msgid "Indicates the IP address on the internal port that is mapped to by the floating IP (since an Networking port might have more than one IP address)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:370(td)
+msgid "Owner of the Floating IP. Only admin users can specify a tenant_id other than its own."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:378(title) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:385(caption) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1675(caption)
+msgid "Basic L3 operations"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:379(para)
+msgid "External networks are visible to all users. However, the default policy settings enable only administrative users to create, update, and delete external networks."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:382(para)
+msgid "This table shows example neutron commands that enable you to complete basic L3 operations:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:397(para)
+msgid "Creates external networks."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:406(para)
+msgid "Lists external networks."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:414(para)
+msgid "Creates an internal-only router that connects to multiple L2 networks privately."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:429(para)
+msgid "Connects a router to an external network, which enables that router to act as a NAT gateway for external connectivity."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:434(para)
+msgid "The router obtains an interface with the gateway_ip address of the subnet and this interface is attached to a port on the L2 Networking network associated with the subnet. The router also gets a gateway interface to the specified external network. This provides SNAT connectivity to the external network as well as support for floating IPs allocated on that external networks. Commonly an external network maps to a network in the provider"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:445(para)
+msgid "Lists routers."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:453(para)
+msgid "Shows information for a specified router."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:461(para)
+msgid "Shows all internal interfaces for a router."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:466(para)
+msgid "Identifies the <literal>port-id</literal> that represents the VM NIC to which the floating IP should map."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:471(para)
+msgid "This port must be on an Networking subnet that is attached to a router uplinked to the external network used to create the floating IP. Conceptually, this is because the router must be able to perform the Destination NAT (DNAT) rewriting of packets from the Floating IP address (chosen from a subnet on the external network) to the internal Fixed IP (chosen from a private subnet that is behind the router)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:482(para)
+msgid "Creates a floating IP address and associates it with a port."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:492(para)
+msgid "Creates a floating IP address and associates it with a port, in a single step."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:501(para)
+msgid "Lists floating IPs."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:509(para)
+msgid "Finds floating IP for a specified VM port."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:517(para)
+msgid "Disassociates a floating IP address."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:525(para)
+msgid "Deletes the floating IP address."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:533(para)
+msgid "Clears the gateway."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:541(para)
+msgid "Removes the interfaces from the router."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:549(para)
+msgid "Deletes the router."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:561(title)
+msgid "Security groups"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:562(para)
+msgid "Security groups and security group rules allows administrators and tenants the ability to specify the type of traffic and direction (ingress/egress) that is allowed to pass through a port. A security group is a container for security group rules."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:565(para)
+msgid "When a port is created in Networking it is associated with a security group. If a security group is not specified the port is associated with a 'default' security group. By default, this group drops all ingress traffic and allows all egress. Rules can be added to this group in order to change the behaviour."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:569(para)
+msgid "To use the Compute security group APIs or use Compute to orchestrate the creation of ports for instances on specific security groups, you must complete additional configuration. You must configure the <filename>/etc/nova/nova.conf</filename> file and set the <code>security_group_api=neutron</code> option on every node that runs <systemitem class=\"service\">nova-compute</systemitem> and <systemitem class=\"service\">nova-api</systemitem>. After you make this change, restart <systemitem class=\"service\">nova-api</systemitem> and <systemitem class=\"service\">nova-compute</systemitem> to pick up this change. Then, you can use both the Compute and OpenStack Network security group APIs at the same time."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:581(para)
+msgid "To use the Compute security group API with Networking, the Networking plug-in must implement the security group API. The following plug-ins currently implement this: ML2, Open vSwitch, Linux Bridge, NEC, Ryu, and VMware NSX."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:587(para)
+msgid "You must configure the correct firewall driver in the <literal>securitygroup</literal> section of the plug-in/agent configuration file. Some plug-ins and agents, such as Linux Bridge Agent and Open vSwitch Agent, use the no-operation driver as the default, which results in non-working security groups."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:594(para)
+msgid "When using the security group API through Compute, security groups are applied to all ports on an instance. The reason for this is that Compute security group APIs are instances based and not port based as Networking."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:602(title)
+msgid "Security group API abstractions"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:604(caption)
+msgid "Security group attributes"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:622(td)
+msgid "UUID for the security group."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:628(td)
+msgid "Human-readable name for the security group. Might not be unique. Cannot be named default as that is automatically created for a tenant."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:632(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:893(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1015(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1083(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1601(td)
+msgid "description"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:635(td)
+msgid "Human-readable description of a security group."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:641(td)
+msgid "Owner of the security group. Only admin users can specify a tenant_id other than their own."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:647(caption)
+msgid "Security group rules"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:665(td)
+msgid "UUID for the security group rule."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:668(td)
+msgid "security_group_id"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:669(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:711(td)
+msgid "uuid-str or Integer"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:671(td)
+msgid "The security group to associate rule with."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:674(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1636(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1724(replaceable)
+msgid "direction"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:677(td)
+msgid "The direction the traffic is allow (ingress/egress) from a VM."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:680(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:918(td)
+msgid "protocol"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:683(td)
+msgid "IP Protocol (icmp, tcp, udp, and so on)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:686(td)
+msgid "port_range_min"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:689(td)
+msgid "Port at start of range"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:692(td)
+msgid "port_range_max"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:695(td)
+msgid "Port at end of range"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:698(td)
+msgid "ethertype"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:701(td)
+msgid "ethertype in L2 packet (IPv4, IPv6, and so on)"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:704(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1659(td)
+msgid "remote_ip_prefix"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:705(td)
+msgid "string (IP cidr)"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:707(td)
+msgid "CIDR for address range"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:710(td)
+msgid "remote_group_id"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:712(td)
+msgid "allocated by Networking or Compute"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:713(td)
+msgid "Source security group to apply to rule."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:719(td)
+msgid "Owner of the security group rule. Only admin users can specify a tenant_id other than its own."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:726(title) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:730(caption)
+msgid "Basic security group operations"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:727(para)
+msgid "This table shows example neutron commands that enable you to complete basic security group operations:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:742(para)
+msgid "Creates a security group for our web servers."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:750(para)
+msgid "Lists security groups."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:758(para)
+msgid "Creates a security group rule to allow port 80 ingress."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:766(para)
+msgid "Lists security group rules."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:774(para)
+msgid "Deletes a security group rule."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:782(para)
+msgid "Deletes a security group."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:790(para)
+msgid "Creates a port and associates two security groups."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:798(para)
+msgid "Removes security groups from a port."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:810(title)
+msgid "Basic Load-Balancer-as-a-Service operations"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:812(para)
+msgid "The Load-Balancer-as-a-Service (LBaaS) API provisions and configures load balancers. The Havana release offers a reference implementation that is based on the HAProxy software load balancer."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:816(para)
+msgid "This list shows example neutron commands that enable you to complete basic LBaaS operations:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:820(para)
+msgid "Creates a load balancer pool by using specific provider."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:821(para)
+msgid "<parameter>--provider</parameter> is an optional argument. If not used, the pool is created with default provider for LBaaS service. You should configure the default provider in the <literal>[service_providers]</literal> section of <filename>neutron.conf</filename> file. If no default provider is specified for LBaaS, the <parameter>--provider</parameter> option is required for pool creation."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:828(parameter)
+msgid "--provider &lt;provider_name&gt;"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:831(para)
+msgid "Associates two web servers with pool."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:836(para)
+msgid "Creates a health monitor which checks to make sure our instances are still running on the specified protocol-port."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:841(para)
+msgid "Associates a health monitor with pool."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:845(para)
+msgid "Creates a virtual IP (VIP) address that, when accessed through the load balancer, directs the requests to one of the pool members."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:853(title)
+msgid "Firewall-as-a-Service"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:854(para)
+msgid "The Firewall-as-a-Service (FWaaS) API is an experimental API that enables early adopters and vendors to test their networking implementations."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:857(title)
+msgid "Firewall-as-a-Service API abstractions"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:859(caption)
+msgid "Firewall rules"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:877(td)
+msgid "UUID for the firewall rule."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:883(td)
+msgid "Owner of the firewall rule. Only admin users can specify a tenant_id other than its own."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:890(td)
+msgid "Human readable name for the firewall rule (255 characters limit)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:896(td)
+msgid "Human readable description for the firewall rule (1024 characters limit)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:900(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1126(td)
+msgid "firewall_policy_id"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:901(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1127(td)
+msgid "uuid-str or None"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:903(td)
+msgid "This is a read-only attribute that gets populated with the uuid of the firewall policy when this firewall rule is associated with a firewall policy. A firewall rule can be associated with only one firewall policy at a time. However, the association can be changed to a different firewall policy."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:911(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:972(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1023(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1038(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1091(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1192(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1652(td)
+msgid "Boolean"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:913(td)
+msgid "When set to True makes this firewall rule visible to tenants other than its owner and it can be used in firewall policies not owned by its tenant."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:921(td)
+msgid "IP Protocol (icmp, tcp, udp, None)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:925(td)
+msgid "Integer or String"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:927(td)
+msgid "IP Version (4, 6)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:930(td)
+msgid "source_ip_address"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:931(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:937(td)
+msgid "String (IP address or CIDR)"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:933(td)
+msgid "Source IP address or CIDR."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:936(td)
+msgid "destination_ip_address"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:939(td)
+msgid "Destination IP address or CIDR."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:942(td)
+msgid "source_port"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:943(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:950(td)
+msgid "Integer or String (either as a single port number or in the format of a ':' separated range)"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:946(td)
+msgid "Source port number or a range."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:949(td)
+msgid "destination_port"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:953(td)
+msgid "Destination port number or a range."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:956(td)
+msgid "position"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:959(td)
+msgid "This is a read-only attribute that gets assigned to this rule when the rule is associated with a firewall policy. It indicates the position of this rule in that firewall policy."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:964(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1514(td)
+msgid "action"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:966(td)
+msgid "deny"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:967(td)
+msgid "Action to be performed on the traffic matching the rule (allow, deny)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:971(td)
+msgid "enabled"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:974(td)
+msgid "When set to False, disables this rule in the firewall policy. Facilitates selectively turning off rules without having to disassociate the rule from the firewall policy."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:981(caption)
+msgid "Firewall policies"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:999(td)
+msgid "UUID for the firewall policy."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1005(td)
+msgid "Owner of the firewall policy. Only admin users can specify a tenant_id other their own."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1012(td)
+msgid "Human readable name for the firewall policy (255 characters limit)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1018(td)
+msgid "Human readable description for the firewall policy (1024 characters limit)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1025(td)
+msgid "When set to True makes this firewall policy visible to tenants other than its owner and can be used to associate with firewalls not owned by its tenant."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1030(td)
+msgid "firewall_rules"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1031(td)
+msgid "List of uuid-str or None"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1033(td)
+msgid "This is an ordered list of firewall rule uuids. The firewall applies the rules in the order in which they appear in this list."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1037(td)
+msgid "audited"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1040(td)
+msgid "When set to True by the policy owner indicates that the firewall policy has been audited. This attribute is meant to aid in the firewall policy audit workflows. Each time the firewall policy or the associated firewall rules are changed, this attribute is set to False and must be explicitly set to True through an update operation."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1049(caption)
+msgid "Firewalls"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1067(td)
+msgid "UUID for the firewall."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1073(td)
+msgid "Owner of the firewall. Only admin users can specify a tenant_id other than its own."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1080(td)
+msgid "Human readable name for the firewall (255 characters limit)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1086(td)
+msgid "Human readable description for the firewall (1024 characters limit)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1093(td)
+msgid "The administrative state of the firewall. If False (down), the firewall does not forward any packets."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1101(para)
+msgid "Indicates whether the firewall is currently operational. Possible values include:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1105(para)
+msgid "ACTIVE"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1108(para)
+msgid "DOWN"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1111(para)
+msgid "PENDING_CREATE"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1114(para)
+msgid "PENDING_UPDATE"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1117(para)
+msgid "PENDING_DELETE"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1120(para)
+msgid "ERROR"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1129(td)
+msgid "The firewall policy uuid that this firewall is associated with. This firewall implements the rules contained in the firewall policy represented by this uuid."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1139(title)
+msgid "Plug-in specific extensions"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1141(para)
+msgid "Each vendor can choose to implement additional API extensions to the core API. This section describes the extensions for each plug-in."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1144(title)
+msgid "VMware NSX extensions"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1145(para)
+msgid "These sections explain NSX plug-in extensions."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1147(title)
+msgid "VMware NSX QoS extension"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1148(para)
+msgid "The VMware NSX QoS extension rate-limits network ports to guarantee a specific amount of bandwidth for each port. This extension, by default, is only accessible by a tenant with an admin role but is configurable through the <filename>policy.json</filename> file. To use this extension, create a queue and specify the min/max bandwidth rates (kbps) and optionally set the QoS Marking and DSCP value (if your network fabric uses these values to make forwarding decisions). Once created, you can associate a queue with a network. Then, when ports are created on that network they are automatically created and associated with the specific queue size that was associated with the network. Because one size queue for a every port on a network might not be optimal, a scaling factor from the nova flavor 'rxtx_factor' is passed in from Compute when creating the port to scale the queue."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1160(para)
+msgid "Lastly, if you want to set a specific baseline QoS policy for the amount of bandwidth a single port can use (unless a network queue is specified with the network a port is created on) a default queue can be created in Networking which then causes ports created to be associated with a queue of that size times the rxtx scaling factor. Note that after a network or default queue is specified, queues are added to ports that are subsequently created but are not added to existing ports."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1168(title)
+msgid "VMware NSX QoS API abstractions"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1170(caption)
+msgid "VMware NSX QoS attributes"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1188(td)
+msgid "UUID for the QoS queue."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1193(td)
+msgid "False by default"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1194(td)
+msgid "If True, ports are created with this queue size unless the network port is created or associated with a queue at port creation time."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1202(td)
+msgid "Name for QoS queue."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1205(td)
+msgid "min"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1207(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1225(td)
+msgid "0"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1208(td)
+msgid "Minimum Bandwidth Rate (kbps)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1211(td)
+msgid "max"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1214(td)
+msgid "Maximum Bandwidth Rate (kbps)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1217(td)
+msgid "qos_marking"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1219(td)
+msgid "untrusted by default"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1220(td)
+msgid "Whether QoS marking should be trusted or untrusted."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1223(td)
+msgid "dscp"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1226(td)
+msgid "DSCP Marking value."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1232(td)
+msgid "The owner of the QoS queue."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1238(title) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1242(caption)
+msgid "Basic VMware NSX QoS operations"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1239(para)
+msgid "This table shows example neutron commands that enable you to complete basic queue operations:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1254(para)
+msgid "Creates QoS Queue (admin-only)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1262(para)
+msgid "Associates a queue with a network."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1270(para)
+msgid "Creates a default system queue."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1278(para)
+msgid "Lists QoS queues."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1286(para)
+msgid "Deletes a QoS queue."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1297(title)
+msgid "VMware NSX provider networks extension"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1298(para)
+msgid "Provider networks can be implemented in different ways by the underlying NSX platform."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1300(para)
+msgid "The <emphasis>FLAT</emphasis> and <emphasis>VLAN</emphasis> network types use bridged transport connectors. These network types enable the attachment of large number of ports. To handle the increased scale, the NSX plug-in can back a single OpenStack Network with a chain of NSX logical switches. You can specify the maximum number of ports on each logical switch in this chain on the <literal>max_lp_per_bridged_ls</literal> parameter, which has a default value of 5,000."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1307(para)
+msgid "The recommended value for this parameter varies with the NSX version running in the back-end, as shown in the following table."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1310(caption)
+msgid "Recommended values for max_lp_per_bridged_ls"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1315(td)
+msgid "NSX version"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1316(td)
+msgid "Recommended Value"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1321(td)
+msgid "2.x"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1322(td)
+msgid "64"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1325(td)
+msgid "3.0.x"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1326(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1330(td)
+msgid "5,000"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1329(td)
+msgid "3.1.x"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1333(td)
+msgid "3.2.x"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1334(td)
+msgid "10,000"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1338(para)
+msgid "In addition to these network types, the NSX plug-in also supports a special <emphasis>l3_ext</emphasis> network type, which maps external networks to specific NSX gateway services as discussed in the next section."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1343(title)
+msgid "VMware NSX L3 extension"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1344(para)
+msgid "NSX exposes its L3 capabilities through gateway services which are usually configured out of band from OpenStack. To use NSX with L3 capabilities, first create a L3 gateway service in the NSX Manager. Next, in <filename> /etc/neutron/plugins/vmware/nsx.ini</filename> set <literal>default_l3_gw_service_uuid</literal> to this value. By default, routers are mapped to this gateway service."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1351(title)
+msgid "VMware NSX L3 extension operations"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1352(para)
+msgid "Create external network and map it to a specific NSX gateway service:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1356(para)
+msgid "Terminate traffic on a specific VLAN from a NSX gateway service:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1362(title)
+msgid "Operational status synchronization in the VMware NSX plug-in"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1363(para)
+msgid "Starting with the Havana release, the VMware NSX plug-in provides an asynchronous mechanism for retrieving the operational status for neutron resources from the NSX back-end; this applies to <emphasis>network</emphasis>, <emphasis>port</emphasis> and <emphasis>router</emphasis> resources."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1367(para)
+msgid "The back-end is polled periodically and the status for every resource is retrieved; then the status in the Networking database is updated only for the resources for which a status change occurred. As operational status is now retrieved asynchronously, performance for <literal>GET</literal> operations is consistently improved."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1372(para)
+msgid "Data to retrieve from the back-end are divided in chunks in order to avoid expensive API requests; this is achieved leveraging NSX APIs response paging capabilities. The minimum chunk size can be specified using a configuration option; the actual chunk size is then determined dynamically according to: total number of resources to retrieve, interval between two synchronization task runs, minimum delay between two subsequent requests to the NSX back-end."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1378(para)
+msgid "The operational status synchronization can be tuned or disabled using the configuration options reported in this table; it is however worth noting that the default values work fine in most cases."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1382(caption)
+msgid "Configuration options for tuning operational status synchronization in the NSX plug-in"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1391(th)
+msgid "Option name"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1392(th)
+msgid "Group"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1394(th)
+msgid "Type and constraints"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1395(th)
+msgid "Notes"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1400(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1406(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1425(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1438(literal)
+msgid "state_sync_interval"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1401(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1413(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1422(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1433(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1446(literal)
+msgid "nsx_sync"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1402(td)
+msgid "120 seconds"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1403(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1435(td)
+msgid "Integer; no constraint."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1404(td)
+msgid "Interval in seconds between two run of the synchronization task. If the synchronization task takes more than <placeholder-1/> seconds to execute, a new instance of the task is started as soon as the other is completed. Setting the value for this option to 0 will disable the synchronization task."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1412(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1417(literal)
+msgid "max_random_sync_delay"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1414(td)
+msgid "0 seconds"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1415(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1421(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1439(literal)
+msgid "min_sync_req_delay"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1415(td)
+msgid "Integer. Must not exceed <placeholder-1/>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1416(td)
+msgid "When different from zero, a random delay between 0 and <placeholder-1/> will be added before processing the next chunk."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1423(td)
+msgid "10 seconds"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1424(td)
+msgid "Integer. Must not exceed <placeholder-1/>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1426(td)
+msgid "The value of this option can be tuned according to the observed load on the NSX controllers. Lower values will result in faster synchronization, but might increase the load on the controller cluster."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1432(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1441(literal)
+msgid "min_chunk_size"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1434(td)
+msgid "500 resources"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1436(td)
+msgid "Minimum number of resources to retrieve from the back-end for each synchronization chunk. The expected number of synchronization chunks is given by the ratio between <placeholder-1/> and <placeholder-2/>. This size of a chunk might increase if the total number of resources is such that more than <placeholder-3/> resources must be fetched in one chunk with the current number of chunks."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1445(literal)
+msgid "always_read_status"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1448(td)
+msgid "Boolean; no constraint."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1450(literal)
+msgid "GET"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1449(td)
+msgid "When this option is enabled, the operational status will always be retrieved from the NSX back-end ad every <placeholder-1/> request. In this case it is advisable to disable the synchronization task."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1456(para)
+msgid "When running multiple OpenStack Networking server instances, the status synchronization task should not run on every node; doing so sends unnecessary traffic to the NSX back-end and performs unnecessary DB operations. Set the <option>state_sync_interval</option> configuration option to a non-zero value exclusively on a node designated for back-end status synchronization."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1462(para)
+msgid "The <parameter>fields=status</parameter> parameter in Networking API requests always triggers an explicit query to the NSX back end, even when you enable asynchronous state synchronization. For example, <code>GET /v2.0/networks/&lt;net-id&gt;?fields=status&amp;fields=name</code>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1469(title)
+msgid "Big Switch plug-in extensions"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1470(para)
+msgid "This section explains the Big Switch neutron plug-in-specific extension."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1472(title)
+msgid "Big Switch router rules"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1473(para)
+msgid "Big Switch allows router rules to be added to each tenant router. These rules can be used to enforce routing policies such as denying traffic between subnets or traffic to external networks. By enforcing these at the router level, network segmentation policies can be enforced across many VMs that have differing security groups."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1479(title)
+msgid "Router rule attributes"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1480(para)
+msgid "Each tenant router has a set of router rules associated with it. Each router rule has the attributes in this table. Router rules and their attributes can be set using the <placeholder-1/> command, through the horizon interface or the Networking API."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1485(caption)
+msgid "Big Switch Router rule attributes"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1493(th)
+msgid "Required"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1494(th)
+msgid "Input Type"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1500(td)
+msgid "source"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1502(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1509(td)
+msgid "A valid CIDR or one of the keywords 'any' or 'external'"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1503(td)
+msgid "The network that a packet's source IP must match for the rule to be applied"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1507(td)
+msgid "destination"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1510(td)
+msgid "The network that a packet's destination IP must match for the rule to be applied"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1516(td)
+msgid "'permit' or 'deny'"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1517(td)
+msgid "Determines whether or not the matched packets will allowed to cross the router"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1521(td)
+msgid "nexthop"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1522(td)
+msgid "No"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1524(literal)
+msgid "1.1.1.1+1.1.1.2"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1523(td)
+msgid "A plus-separated (+) list of next-hop IP addresses. For example, <placeholder-1/>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1525(td)
+msgid "Overrides the default virtual router used to handle traffic for packets that match the rule"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1532(title)
+msgid "Order of rule processing"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1533(para)
+msgid "The order of router rules has no effect. Overlapping rules are evaluated using longest prefix matching on the source and destination fields. The source field is matched first so it always takes higher precedence over the destination field. In other words, longest prefix matching is used on the destination field only if there are multiple matching rules with the same source."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1541(title)
+msgid "Big Switch router rules operations"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1542(para)
+msgid "Router rules are configured with a router update operation in OpenStack Networking. The update overrides any previous rules so all rules must be provided at the same time."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1545(para)
+msgid "Update a router with rules to permit traffic by default but block traffic from external networks to the 10.10.10.0/24 subnet:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1547(replaceable) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1551(replaceable) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1555(replaceable)
+msgid "Router-UUID"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1550(para)
+msgid "Specify alternate next-hop addresses for a specific subnet:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1554(para)
+msgid "Block traffic between two subnets while allowing everything else:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1563(title)
+msgid "L3 metering"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1564(para)
+msgid "The L3 metering API extension enables administrators to configure IP ranges and assign a specified label to them to be able to measure traffic that goes through a virtual router."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1567(para)
+msgid "The L3 metering extension is decoupled from the technology that implements the measurement. Two abstractions have been added: One is the metering label that can contain metering rules. Because a metering label is associated with a tenant, all virtual routers in this tenant are associated with this label."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1572(title)
+msgid "L3 metering API abstractions"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1574(caption)
+msgid "Label"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1592(td)
+msgid "UUID for the metering label."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1598(td)
+msgid "Human-readable name for the metering label. Might not be unique."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1604(td)
+msgid "The optional description for the metering label."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1610(td)
+msgid "Owner of the metering label."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1615(caption)
+msgid "Rules"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1633(td)
+msgid "UUID for the metering rule."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1637(td)
+msgid "String (Either ingress or egress)"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1638(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1725(replaceable)
+msgid "ingress"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1639(td)
+msgid "The direction in which metering rule is applied, either ingress or egress."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1643(td)
+msgid "metering_label_id"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1647(para)
+msgid "The metering label ID to associate with this metering rule."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1651(td)
+msgid "excluded"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1654(td)
+msgid "Specify whether the remote_ip_prefix will be excluded or not from traffic counters of the metering label (for example, to not count the traffic of a specific IP address of a range)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1660(td)
+msgid "String (CIDR)"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1662(td)
+msgid "Indicates remote IP prefix to be associated with this metering rule."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1670(title)
+msgid "Basic L3 metering operations"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1671(para)
+msgid "Only administrators can manage the L3 metering labels and rules."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1672(para)
+msgid "This table shows example <placeholder-1/> commands that enable you to complete basic L3 metering operations:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1687(para)
+msgid "Creates a metering label."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1690(replaceable) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1707(replaceable) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1716(replaceable) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1725(replaceable) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1726(replaceable)
+msgid "label1"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1690(replaceable)
+msgid "\"description of label1\""
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1695(para)
+msgid "Lists metering labels."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1703(para)
+msgid "Shows information for a specified label."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1706(replaceable) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1715(replaceable) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1724(replaceable)
+msgid "label-uuid"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1712(para)
+msgid "Deletes a metering label."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1721(para)
+msgid "Creates a metering rule."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1725(replaceable)
+msgid "10.0.0.0/24"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1726(replaceable)
+msgid "20.0.0.0/24"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1731(para)
+msgid "Lists metering all label rules."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1739(para)
+msgid "Shows information for a specified label rule."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1742(replaceable) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1748(replaceable)
+msgid "rule-uuid"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1746(td)
+msgid "Deletes a metering label rule."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_high_avail.xml:6(title)
+msgid "High availability"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_high_avail.xml:7(para)
+msgid "The use of high availability in a Networking deployment helps mitigate the impact of individual node failures. In general, you can run <systemitem class=\"service\">neutron-server</systemitem> and <systemitem class=\"service\">neutron-dhcp-agent</systemitem> in an <glossterm baseform=\"active/active configuration\">active/active</glossterm> fashion. You can run the <systemitem class=\"service\">neutron-l3-agent</systemitem> service as <glossterm baseform=\"active/passive configuration\">active/passive</glossterm>, which avoids IP conflicts with respect to gateway IP addresses."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_high_avail.xml:21(title)
+msgid "Networking high availability with Pacemaker"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_high_avail.xml:22(para)
+msgid "You can run some Networking services in a cluster configuration (active/passive or active/active for Networking server only) with Pacemaker."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_high_avail.xml:25(para)
+msgid "Download the latest resources agents:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_high_avail.xml:28(para)
+msgid "neutron-server: <link href=\"https://github.com/madkiss/openstack-resource-agents/blob/master/ocf/neutron-server\">https://github.com/madkiss/openstack-resource-agents</link>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_high_avail.xml:33(para)
+msgid "neutron-dhcp-agent: <link href=\"https://github.com/madkiss/openstack-resource-agents/blob/master/ocf/neutron-agent-dhcp\">https://github.com/madkiss/openstack-resource-agents</link>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_high_avail.xml:38(para)
+msgid "neutron-l3-agent: <link href=\"https://github.com/madkiss/openstack-resource-agents/blob/master/ocf/neutron-agent-l3\">https://github.com/madkiss/openstack-resource-agents</link>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_high_avail.xml:44(para)
+msgid "For information about how to build a cluster, see <link href=\"http://www.clusterlabs.org/wiki/Documentation\">Pacemaker documentation</link>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:6(title)
+msgid "Advanced operational features"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:8(title)
+msgid "Logging settings"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:9(para)
+msgid "Networking components use Python logging module to do logging. Logging configuration can be provided in <filename>neutron.conf</filename> or as command-line options. Command options override ones in <filename>neutron.conf</filename>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:14(para)
+msgid "To configure logging for Networking components, use one of these methods:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:18(para)
+msgid "Provide logging settings in a logging configuration file."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:20(para)
+msgid "See <link href=\"http://docs.python.org/howto/logging.html\">Python logging how-to</link> to learn more about logging."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:24(para)
+msgid "Provide logging setting in <filename>neutron.conf</filename>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:49(title)
+msgid "Notifications"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:50(para)
+msgid "Notifications can be sent when Networking resources such as network, subnet and port are created, updated or deleted."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:54(title)
+msgid "Notification options"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:55(para)
+msgid "To support DHCP agent, rpc_notifier driver must be set. To set up the notification, edit notification options in <filename>neutron.conf</filename>:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:85(title)
+msgid "Setting cases"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:87(title)
+msgid "Logging and RPC"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:88(para)
+msgid "These options configure the Networking server to send notifications through logging and RPC. The logging options are described in <citetitle>OpenStack Configuration Reference</citetitle> . RPC notifications go to 'notifications.info' queue bound to a topic exchange defined by 'control_exchange' in <filename>neutron.conf</filename>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:125(title)
+msgid "Multiple RPC topics"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:126(para)
+msgid "These options configure the Networking server to send notifications to multiple RPC topics. RPC notifications go to 'notifications_one.info' and 'notifications_two.info' queues bound to a topic exchange defined by 'control_exchange' in <filename>neutron.conf</filename>."
+msgstr ""
+
 #: ./doc/admin-guide-cloud/networking/section_networking_auth.xml:6(title)
 msgid "Authentication and authorization"
 msgstr ""
@@ -4630,6 +4976,22 @@ msgstr ""
 msgid "In some cases, some operations are restricted to administrators only. This example shows you how to modify a policy file to permit tenants to define networks, see their resources, and permit administrative users to perform all other operations:"
 msgstr ""
 
+#: ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:6(title)
+msgid "Plug-in pagination and sorting support"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:8(caption)
+msgid "Plug-ins that support native pagination and sorting"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:13(th)
+msgid "Support Native Pagination"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:14(th)
+msgid "Support Native Sorting"
+msgstr ""
+
 #: ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:6(title)
 msgid "Advanced configuration options"
 msgstr ""
@@ -4721,10 +5083,6 @@ msgstr ""
 msgid "$NEUTRON_CONF_DIR/plugins/openvswitch/ovs_neutron_plugin.ini"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:98(td) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:121(td) ./doc/admin-guide-cloud/networking/section_networking_arch.xml:34(th)
-msgid "Agent"
-msgstr ""
-
 #: ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:99(td)
 msgid "neutron-openvswitch-agent"
 msgstr ""
@@ -4945,124 +5303,248 @@ msgstr ""
 msgid "<emphasis>MetaPlugin is experimental</emphasis>: This release includes a MetaPlugin that is intended to support multiple plug-ins at the same time for different API requests, based on the content of those API requests. The core team has not thoroughly reviewed or tested this functionality. Consider this functionality to be experimental until further validation is performed."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:6(title)
-msgid "Plug-in pagination and sorting support"
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:6(title)
+msgid "Configure Identity Service for Networking"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:8(caption)
-msgid "Plug-ins that support native pagination and sorting"
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:8(title)
+msgid "To configure the Identity Service for use with Networking"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:13(th)
-msgid "Support Native Pagination"
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:11(title)
+msgid "Create the <function>get_id()</function> function"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:14(th)
-msgid "Support Native Sorting"
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:12(para)
+msgid "The <function>get_id()</function> function stores the ID of created objects, and removes the need to copy and paste object IDs in later steps:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:20(td) ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:21(td) ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:25(td) ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:26(td) ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:30(td) ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:31(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:279(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:973(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1092(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:133(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:234(td)
-msgid "True"
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:16(para)
+msgid "Add the following function to your <filename>.bashrc</filename> file:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_high_avail.xml:6(title)
-msgid "High availability"
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:23(para)
+msgid "Source the <filename>.bashrc</filename> file:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_high_avail.xml:7(para)
-msgid "The use of high availability in a Networking deployment helps mitigate the impact of individual node failures. In general, you can run <systemitem class=\"service\">neutron-server</systemitem> and <systemitem class=\"service\">neutron-dhcp-agent</systemitem> in an <glossterm baseform=\"active/active configuration\">active/active</glossterm> fashion. You can run the <systemitem class=\"service\">neutron-l3-agent</systemitem> service as <glossterm baseform=\"active/passive configuration\">active/passive</glossterm>, which avoids IP conflicts with respect to gateway IP addresses."
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:29(title)
+msgid "Create the Networking service entry"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_high_avail.xml:21(title)
-msgid "Networking high availability with Pacemaker"
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:30(para)
+msgid "Networking must be available in the Compute service catalog. Create the service:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_high_avail.xml:22(para)
-msgid "You can run some Networking services in a cluster configuration (active/passive or active/active for Networking server only) with Pacemaker."
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:34(title)
+msgid "Create the Networking service endpoint entry"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_high_avail.xml:25(para)
-msgid "Download the latest resources agents:"
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:36(para)
+msgid "The way that you create a Networking endpoint entry depends on whether you are using the SQL or the template catalog driver:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_high_avail.xml:28(para)
-msgid "neutron-server: <link href=\"https://github.com/madkiss/openstack-resource-agents/blob/master/ocf/neutron-server\">https://github.com/madkiss/openstack-resource-agents</link>"
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:40(para)
+msgid "If you use the <emphasis>SQL driver</emphasis>, run the following command with the specified region (<literal>$REGION</literal>), IP address of the Networking server (<literal>$IP</literal>), and service ID (<literal>$NEUTRON_SERVICE_ID</literal>, obtained in the previous step)."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_high_avail.xml:33(para)
-msgid "neutron-dhcp-agent: <link href=\"https://github.com/madkiss/openstack-resource-agents/blob/master/ocf/neutron-agent-dhcp\">https://github.com/madkiss/openstack-resource-agents</link>"
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:52(para)
+msgid "If you are using the <emphasis>template driver</emphasis>, specify the following parameters in your Compute catalog template file (<filename>default_catalog.templates</filename>), along with the region (<literal>$REGION</literal>) and IP address of the Networking server (<literal>$IP</literal>)."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_high_avail.xml:38(para)
-msgid "neutron-l3-agent: <link href=\"https://github.com/madkiss/openstack-resource-agents/blob/master/ocf/neutron-agent-l3\">https://github.com/madkiss/openstack-resource-agents</link>"
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:70(title)
+msgid "Create the Networking service user"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_high_avail.xml:44(para)
-msgid "For information about how to build a cluster, see <link href=\"http://www.clusterlabs.org/wiki/Documentation\">Pacemaker documentation</link>."
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:71(para)
+msgid "You must provide admin user credentials that Compute and some internal Networking components can use to access the Networking API. Create a special <literal>service</literal> tenant and a <literal>neutron</literal> user within this tenant, and assign an <literal>admin</literal> role to this role."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:6(title)
-msgid "Advanced operational features"
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:77(para)
+msgid "Create the <literal>admin</literal> role:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:8(title)
-msgid "Logging settings"
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:82(para)
+msgid "Create the <literal>neutron</literal> user:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:9(para)
-msgid "Networking components use Python logging module to do logging. Logging configuration can be provided in <filename>neutron.conf</filename> or as command-line options. Command options override ones in <filename>neutron.conf</filename>."
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:87(para)
+msgid "Create the <literal>service</literal> tenant:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:14(para)
-msgid "To configure logging for Networking components, use one of these methods:"
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:91(para)
+msgid "Establish the relationship among the tenant, user, and role:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:18(para)
-msgid "Provide logging settings in a logging configuration file."
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:98(para)
+msgid "For information about how to create service entries and users, see the <citetitle>OpenStack Installation Guide</citetitle> for your distribution (<link href=\"docs.openstack.org\">docs.openstack.org</link>)."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:20(para)
-msgid "See <link href=\"http://docs.python.org/howto/logging.html\">Python logging how-to</link> to learn more about logging."
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:103(para)
+msgid "If you use Networking, do not run the Compute <systemitem class=\"service\">nova-network</systemitem> service (like you do in traditional Compute deployments). Instead, Compute delegates most network-related decisions to Networking. Compute proxies tenant-facing API calls to manage security groups and floating IPs to Networking APIs. However, operator-facing tools such as <systemitem class=\"service\">nova-manage</systemitem>, are not proxied and should not be used."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:24(para)
-msgid "Provide logging setting in <filename>neutron.conf</filename>"
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:110(para)
+msgid "When you configure networking, you must use this guide. Do not rely on Compute networking documentation or past experience with Compute. If a <placeholder-1/> command or configuration option related to networking is not mentioned in this guide, the command is probably not supported for use with Networking. In particular, you cannot use CLI tools like <placeholder-2/> and <placeholder-3/> to manage networks or IP addressing, including both fixed and floating IPs, with Networking."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:49(title)
-msgid "Notifications"
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:118(para)
+msgid "Uninstall <systemitem class=\"service\">nova-network</systemitem> and reboot any physical nodes that have been running <systemitem class=\"service\">nova-network</systemitem> before using them to run Networking. Inadvertently running the <systemitem class=\"service\">nova-network</systemitem> process while using Networking can cause problems, as can stale iptables rules pushed down by previously running <systemitem class=\"service\">nova-network</systemitem>."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:50(para)
-msgid "Notifications can be sent when Networking resources such as network, subnet and port are created, updated or deleted."
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:126(para)
+msgid "To ensure that Compute works properly with Networking (rather than the legacy <systemitem class=\"service\">nova-network</systemitem> mechanism), you must adjust settings in the <filename>nova.conf</filename> configuration file."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:54(title)
-msgid "Notification options"
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:133(title)
+msgid "Networking API and credential configuration"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:55(para)
-msgid "To support DHCP agent, rpc_notifier driver must be set. To set up the notification, edit notification options in <filename>neutron.conf</filename>:"
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:134(para)
+msgid "Each time you provision or de-provision a VM in Compute, <systemitem class=\"service\">nova-*</systemitem> services communicate with Networking using the standard API. For this to happen, you must configure the following items in the <filename>nova.conf</filename> file (used by each <systemitem class=\"service\">nova-compute</systemitem> and <systemitem class=\"service\">nova-api</systemitem> instance)."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:85(title)
-msgid "Setting cases"
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:140(caption)
+msgid "nova.conf API and credential settings"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:87(title)
-msgid "Logging and RPC"
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:145(th) ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:220(td) ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:255(td)
+msgid "Item"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:88(para)
-msgid "These options configure the Networking server to send notifications through logging and RPC. The logging options are described in <citetitle>OpenStack Configuration Reference</citetitle> . RPC notifications go to 'notifications.info' queue bound to a topic exchange defined by 'control_exchange' in <filename>neutron.conf</filename>."
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:151(literal)
+msgid "network_api_class"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:125(title)
-msgid "Multiple RPC topics"
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:153(para)
+msgid "Modify from the default to <literal>nova.network.neutronv2.api.API</literal>, to indicate that Networking should be used rather than the traditional <systemitem class=\"service\">nova-network </systemitem> networking model."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_operational_features.xml:126(para)
-msgid "These options configure the Networking server to send notifications to multiple RPC topics. RPC notifications go to 'notifications_one.info' and 'notifications_two.info' queues bound to a topic exchange defined by 'control_exchange' in <filename>neutron.conf</filename>."
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:161(literal)
+msgid "neutron_url"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:162(para)
+msgid "Update to the hostname/IP and port of the <systemitem class=\"service\">neutron-server</systemitem> instance for this deployment."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:168(literal)
+msgid "neutron_auth_strategy"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:169(para)
+msgid "Keep the default <literal>keystone</literal> value for all production deployments."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:173(literal)
+msgid "neutron_admin_tenant_name"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:175(para)
+msgid "Update to the name of the service tenant created in the above section on Identity configuration."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:180(literal)
+msgid "neutron_admin_username"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:182(para)
+msgid "Update to the name of the user created in the above section on Identity configuration."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:187(literal)
+msgid "neutron_admin_password"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:189(para)
+msgid "Update to the password of the user created in the above section on Identity configuration."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:194(literal)
+msgid "neutron_admin_auth_url"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:196(para)
+msgid "Update to the Identity server IP and port. This is the Identity (keystone) admin API server IP and port value, and not the Identity service API IP and port."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:206(title)
+msgid "Configure security groups"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:207(para)
+msgid "The Networking Service provides security group functionality using a mechanism that is more flexible and powerful than the security group capabilities built into Compute. Therefore, if you use Networking, you should always disable built-in security groups and proxy all security group calls to the Networking API . If you do not, security policies will conflict by being simultaneously applied by both services."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:212(para)
+msgid "To proxy security groups to Networking, use the following configuration values in <filename>nova.conf</filename>:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:215(caption)
+msgid "nova.conf security group settings"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:226(literal)
+msgid "firewall_driver"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:227(para)
+msgid "Update to <literal>nova.virt.firewall.NoopFirewallDriver</literal>, so that <systemitem class=\"service\">nova-compute</systemitem> does not perform iptables-based filtering itself."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:234(literal)
+msgid "security_group_api"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:235(para)
+msgid "Update to <literal>neutron</literal>, so that all security group requests are proxied to the Network Service."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:242(title)
+msgid "Configure metadata"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:243(para)
+msgid "The Compute service allows VMs to query metadata associated with a VM by making a web request to a special 169.254.169.254 address. Networking supports proxying those requests to <systemitem class=\"service\">nova-api</systemitem>, even when the requests are made from isolated networks, or from multiple networks that use overlapping IP addresses."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:247(para)
+msgid "To enable proxying the requests, you must update the following fields in <filename>nova.conf</filename>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:250(caption)
+msgid "nova.conf metadata settings"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:261(literal)
+msgid "service_neutron_metadata_proxy"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:263(para)
+msgid "Update to <literal>true</literal>, otherwise <systemitem class=\"service\">nova-api</systemitem> will not properly respond to requests from the <systemitem class=\"service\">neutron-metadata-agent</systemitem>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:270(literal)
+msgid "neutron_metadata_proxy_shared_secret"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:272(para)
+msgid "Update to a string \"password\" value. You must also configure the same value in the <filename>metadata_agent.ini</filename> file, to authenticate requests made for metadata."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:276(para)
+msgid "The default value of an empty string in both files will allow metadata to function, but will not be secure if any non-trusted entities have access to the metadata APIs exposed by <systemitem class=\"service\">nova-api</systemitem>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:285(para)
+msgid "As a precaution, even when using <literal>neutron_metadata_proxy_shared_secret</literal>, it is recommended that you do not expose metadata using the same <systemitem class=\"service\">nova-api</systemitem> instances that are used for tenants. Instead, you should run a dedicated set of <systemitem class=\"service\">nova-api</systemitem> instances for metadata that are available only on your management network. Whether a given <systemitem class=\"service\">nova-api</systemitem> instance exposes metadata APIs is determined by the value of <literal>enabled_apis</literal> in its <filename>nova.conf</filename>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:300(title)
+msgid "Example nova.conf (for <systemitem class=\"service\">nova-compute</systemitem> and <systemitem class=\"service\">nova-api</systemitem>)"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:303(para)
+msgid "Example values for the above settings, assuming a cloud controller node running Compute and Networking with an IP address of 192.168.1.2:"
 msgstr ""
 
 #. When image changes, this message will be marked fuzzy or untranslated for you.
@@ -5543,10 +6025,6 @@ msgstr ""
 msgid "192.168.1.10"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:739(replaceable) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:142(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:146(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:158(literal)
-msgid "gre"
-msgstr ""
-
 #: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:739(replaceable)
 msgid "vxlan"
 msgstr ""
@@ -5571,2586 +6049,352 @@ msgstr ""
 msgid "Since the ML2 plug-in can concurrently support different L2 agents (or other mechanisms) with different configuration files, the actual <option>firewall_driver </option> value in the <filename>ml2_conf.ini</filename> file does not matter in the server, but <option>firewall_driver</option> must be set to a non-default value in the ml2 configuration to enable the securitygroup extension. To enable securitygroup API, edit the <filename>ml2_conf.ini</filename> file:<placeholder-1/> Each L2 agent configuration file (such as <filename>ovs_neutron_plugin.ini</filename> or <filename>linuxbridge_conf.ini</filename>) should contain the appropriate <option>firewall_driver</option> value for that agent. To disable securitygroup API, edit the <filename>ml2_conf.ini</filename> file:<placeholder-2/> Also, each L2 agent configuration file (such as <filename>ovs_neutron_plugin.ini</filename> or <filename>linuxbridge_conf.ini</filename>) should contain this value in <option>firewall_driver</option> parameter for that agent."
 msgstr ""
 
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:123(None)
-msgid "@@image: '../../common/figures/Neutron-PhysNet-Diagram.png'; md5=ea581fd58c57da1a6c9512b82027a195"
+#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:6(title)
+msgid "Configure Identity service for token binding"
 msgstr ""
 
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:199(None)
-msgid "@@image: '../../common/figures/NetworkTypes.png'; md5=c424894383b701a38a6dc3ccf2e916f3"
+#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:7(para)
+msgid "Token binding embeds information from an external authentication mechanism, such as a Kerberos server or X.509 certificate, inside a token. By using token binding, a client can enforce the use of a specified external authentication mechanism with the token. This additional security mechanism ensures that if a token is stolen, for example, it is not usable without external authentication."
 msgstr ""
 
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:286(None)
-msgid "@@image: '../../common/figures/vmware_nsx.png'; md5=fba7420fae8c2cb386147408e7a06416"
+#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:14(para)
+msgid "You configure the authentication types for a token binding in the <filename>keystone.conf</filename> file:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:5(title)
-msgid "Networking architecture"
+#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:18(para)
+msgid "or"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:6(para)
-msgid "Before you deploy Networking, it's useful to understand the Networking services and how they interact with the OpenStack components."
+#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:21(para)
+msgid "Currently <literal>kerberos</literal> and <literal>x509</literal> are supported."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:10(title)
-msgid "Overview"
+#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:23(para)
+msgid "To enforce checking of token binding, set the <option>enforce_token_bind</option> option to one of these modes:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:11(para)
-msgid "Networking is a standalone component in the OpenStack modular architecture. It's positioned alongside OpenStack components such as Compute, Image Service, Identity, or the Dashboard. Like those components, a deployment of Networking often involves deploying several services to a variety of hosts."
+#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:28(literal)
+msgid "disabled"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:16(para)
-msgid "The Networking server uses the <systemitem class=\"service\">neutron-server</systemitem> daemon to expose the Networking API and enable administration of the configured Networking plug-in. Typically, the plug-in requires access to a database for persistent storage (also similar to other OpenStack services)."
+#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:29(para)
+msgid "Disables token bind checking."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:22(para)
-msgid "If your deployment uses a controller host to run centralized Compute components, you can deploy the Networking server to that same host. However, Networking is entirely standalone and can be deployed to a dedicated host. Depending on your configuration, Networking can also include the following agents:"
+#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:32(literal)
+msgid "permissive"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:29(caption)
-msgid "Networking agents"
+#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:33(para)
+msgid "Enables bind checking. If a token is bound to an unknown authentication mechanism, the server ignores it. The default is this mode."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:40(emphasis)
-msgid "plug-in agent"
+#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:38(literal)
+msgid "strict"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:42(literal)
-msgid "neutron-*-agent"
+#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:39(para)
+msgid "Enables bind checking. If a token is bound to an unknown authentication mechanism, the server rejects it."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:40(td) ./doc/admin-guide-cloud/networking/section_networking_arch.xml:49(td) ./doc/admin-guide-cloud/networking/section_networking_arch.xml:56(td) ./doc/admin-guide-cloud/networking/section_networking_arch.xml:64(td)
-msgid "<placeholder-1/> (<placeholder-2/>)"
+#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:43(literal)
+msgid "required"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:43(td)
-msgid "Runs on each hypervisor to perform local vSwitch configuration. The agent that runs, depends on the plug-in that you use. Certain plug-ins do not require an agent."
+#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:44(para)
+msgid "Enables bind checking. Requires use of at least authentication mechanism for tokens."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:49(emphasis)
-msgid "dhcp agent"
+#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:48(literal)
+msgid "kerberos"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:51(literal)
-msgid "neutron-dhcp-agent"
+#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:49(para)
+msgid "Enables bind checking. Requires use of kerberos as the authentication mechanism for tokens:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:52(td)
-msgid "Provides DHCP services to tenant networks. Required by certain plug-ins."
+#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:55(literal)
+msgid "x509"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:56(emphasis)
-msgid "l3 agent"
+#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:56(para)
+msgid "Enables bind checking. Requires use of X.509 as the authentication mechanism for tokens:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:58(literal)
-msgid "neutron-l3-agent"
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_HTTP_bad_req_in_cinder_vol_log.xml:5(title) ./doc/admin-guide-cloud/blockstorage/section_ts_failed_attach_vol_after_detach.xml:5(title)
+msgid "Failed to attach volume after detaching"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:59(td)
-msgid "Provides L3/NAT forwarding to provide external network access for VMs on tenant networks. Required by certain plug-ins."
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_HTTP_bad_req_in_cinder_vol_log.xml:8(title) ./doc/admin-guide-cloud/blockstorage/section_ts_non_existent_vlun.xml:6(title) ./doc/admin-guide-cloud/blockstorage/section_ts_vol_attach_miss_sg_scan.xml:10(title) ./doc/admin-guide-cloud/blockstorage/section_ts_failed_attach_vol_no_sysfsutils.xml:6(title) ./doc/admin-guide-cloud/blockstorage/section_ts_failed_connect_vol_FC_SAN.xml:6(title) ./doc/admin-guide-cloud/blockstorage/section_ts_non_existent_host.xml:6(title) ./doc/admin-guide-cloud/blockstorage/section_ts_no_emulator_x86_64.xml:6(title) ./doc/admin-guide-cloud/blockstorage/section_ts_multipath_warn.xml:8(title) ./doc/admin-guide-cloud/blockstorage/section_ts_failed_attach_vol_after_detach.xml:8(title) ./doc/admin-guide-cloud/blockstorage/section_ts_duplicate_3par_host.xml:6(title)
+msgid "Problem"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:64(emphasis)
-msgid "metering agent"
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_HTTP_bad_req_in_cinder_vol_log.xml:9(para)
+msgid "These errors appear in the <filename>cinder-volume.log</filename> file."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:65(literal)
-msgid "neutron-metering-agent"
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_HTTP_bad_req_in_cinder_vol_log.xml:43(title) ./doc/admin-guide-cloud/blockstorage/section_ts_non_existent_vlun.xml:12(title) ./doc/admin-guide-cloud/blockstorage/section_ts_vol_attach_miss_sg_scan.xml:24(title) ./doc/admin-guide-cloud/blockstorage/section_ts_failed_attach_vol_no_sysfsutils.xml:15(title) ./doc/admin-guide-cloud/blockstorage/section_ts_failed_connect_vol_FC_SAN.xml:15(title) ./doc/admin-guide-cloud/blockstorage/section_ts_non_existent_host.xml:14(title) ./doc/admin-guide-cloud/blockstorage/section_ts_no_emulator_x86_64.xml:11(title) ./doc/admin-guide-cloud/blockstorage/section_ts_multipath_warn.xml:20(title) ./doc/admin-guide-cloud/blockstorage/section_ts_failed_attach_vol_after_detach.xml:14(title) ./doc/admin-guide-cloud/blockstorage/section_ts_duplicate_3par_host.xml:12(title)
+msgid "Solution"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:66(td)
-msgid "Provides L3 traffic metering for tenant networks."
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_HTTP_bad_req_in_cinder_vol_log.xml:44(para)
+msgid "You need to update your copy of the <filename>hp_3par_fc.py</filename> driver which contains the synchronization code."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:71(para)
-msgid "These agents interact with the main neutron process through RPC (for example, RabbitMQ or Qpid) or through the standard Networking API. In addition, Networking integrates with OpenStack components in a number of ways:"
+#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:5(title)
+msgid "Configure a multiple-storage back-end"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:77(para)
-msgid "Networking relies on the Identity service (keystone) for the authentication and authorization of all API requests."
+#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:6(para)
+msgid "With multiple storage back-ends configured, you can create several back-end storage solutions serving the same OpenStack Compute configuration. Basically, multi back-end launches one <systemitem class=\"service\">cinder-volume</systemitem> for each back-end."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:82(para)
-msgid "Compute (nova) interacts with Networking through calls to its standard API. As part of creating a VM, the <systemitem class=\"service\">nova-compute</systemitem> service communicates with the Networking API to plug each virtual NIC on the VM into a particular network."
+#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:11(para)
+msgid "In a multi back-end configuration, each back-end has a name (<literal>volume_backend_name</literal>). Several back-ends can have the same name. In that case, the scheduler properly decides which back-end the volume has to be created in."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:91(para)
-msgid "The dashboard (horizon) integrates with the Networking API, enabling administrators and tenant users to create and manage network services through a web-based GUI."
+#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:16(para)
+msgid "The name of the back-end is declared as an extra-specification of a volume type (such as, <literal>volume_backend_name=LVM_iSCSI</literal>). When a volume is created, the scheduler chooses an appropriate back-end to handle the request, according to the volume type specified by the user."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:99(title)
-msgid "Place services on physical hosts"
+#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:23(title)
+msgid "Enable multi back-end"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:100(para)
-msgid "Like other OpenStack services, Networking enables you to run services across multiple physical devices. It is also possible to run all service daemons on a single physical host for evaluation purposes. Alternatively, you can run each service on a dedicated physical host and replicate certain services across multiple hosts for redundancy purposes. For more information, see the <citetitle>OpenStack Configuration Reference</citetitle>."
+#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:24(para)
+msgid "To enable a multi back-end configuration, you must set the <option>enabled_backends</option> flag in the <filename>cinder.conf</filename> file. This flag defines the names (separated by a comma) of the configuration groups for the different back-ends: one name is associated to one configuration group for a back-end (such as, <literal>[lvmdriver-1]</literal>)."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:107(para)
-msgid "A standard architectural design includes a cloud controller host, a network gateway host, and a number of hypervisors for hosting virtual machines. The cloud controller and network gateway can be on the same host. However, if you expect VMs to send significant traffic to or from the Internet, a dedicated network gateway host helps avoid CPU contention between the <systemitem class=\"service\">neutron-l3-agent</systemitem> and other OpenStack services that forward packets."
+#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:32(para)
+msgid "The configuration group name is not related to the <literal>volume_backend_name</literal>."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:118(title)
-msgid "Network connectivity for physical hosts"
+#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:35(para)
+msgid "The options for a configuration group must be defined in the group (or default options are used). All the standard Block Storage configuration options (<literal>volume_group</literal>, <literal>volume_driver</literal>, and so on) might be used in a configuration group. Configuration values in the <literal>[DEFAULT]</literal> configuration group are not used."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:126(para)
-msgid "A standard Networking deployment includes one or more of the following physical networks:"
+#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:43(para)
+msgid "These examples show three back-ends:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:131(caption)
-msgid "General distinct physical data center networks"
+#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:57(para)
+msgid "In this configuration, <literal>lvmdriver-1</literal> and <literal>lvmdriver-2</literal> have the same <literal>volume_backend_name</literal>. If a volume creation requests the <literal>LVM_iSCSI</literal> back-end name, the scheduler uses the capacity filter scheduler to choose the most suitable driver, which is either <literal>lvmdriver-1</literal> or <literal>lvmdriver-2</literal>. The capacity filter scheduler is enabled by default. The next section provides more information. In addition, this example presents a <literal>lvmdriver-3</literal> back-end."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:143(emphasis)
-msgid "Management network"
+#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:70(title)
+msgid "Configure Block Storage scheduler multi back-end"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:145(td)
-msgid "Provides internal communication between OpenStack components. IP addresses on this network should be reachable only within the data center."
+#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:71(para)
+msgid "You must enable the <option>filter_scheduler</option> option to use multi back-end. Filter scheduler acts in two steps:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:151(emphasis)
-msgid "Data network"
+#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:76(para)
+msgid "The filter scheduler filters the available back-ends. By default, <literal>AvailabilityZoneFilter</literal>, <literal>CapacityFilter</literal> and <literal>CapabilitiesFilter</literal> are enabled."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:153(td)
-msgid "Provides VM data communication within the cloud deployment. The IP addressing requirements of this network depend on the Networking plug-in that is used."
+#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:84(para)
+msgid "The filter scheduler weighs the previously filtered back-ends. By default, <literal>CapacityWeigher</literal> is enabled. The <literal>CapacityWeigher</literal> attributes higher scores to back-ends with the most available."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:160(emphasis)
-msgid "External network"
+#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:92(para)
+msgid "The scheduler uses the filtering and weighing process to pick the best back-end to handle the request, and explicitly creates volumes on specific back-ends through the use of volume types."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:162(td)
-msgid "Provides VMs with Internet access in some deployment scenarios. Anyone on the Internet can reach IP addresses on this network."
+#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:99(title)
+msgid "Volume type"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:168(emphasis)
-msgid "API network"
+#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:100(para)
+msgid "Before using it, a volume type has to be declared to Block Storage. This can be done by the following command:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:170(td)
-msgid "Exposes all OpenStack APIs, including the Networking API, to tenants. IP addresses on this network should be reachable by anyone on the Internet. The API network might be the same as the external network, because it is possible to create an external-network subnet that has allocated IP ranges that use less than the full range of IP addresses in an IP block."
+#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:103(para)
+msgid "Then, an extra-specification has to be created to link the volume type to a back-end name. Run this command:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:187(title) ./doc/admin-guide-cloud/networking/section_networking_arch.xml:195(title)
-msgid "Tenant and provider networks"
+#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:107(para)
+msgid "This example creates a <literal>lvm</literal> volume type with <literal>volume_backend_name=LVM_iSCSI</literal> as extra-specifications."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:188(para)
-msgid "The following diagram presents an overview of the tenant and provider network types, and illustrates how they interact within the overall Networking topology:"
+#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:110(para)
+msgid "Create another volume type:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:205(title)
-msgid "Tenant networks"
+#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:113(para)
+msgid "This second volume type is named <literal>lvm_gold</literal> and has <literal>LVM_iSCSI_b</literal> as back-end name."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:206(para)
-msgid "Users create tenant networks for connectivity within projects; they are fully isolated by default and are not shared with other projects. Networking supports a range of tenant network types:"
+#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:118(para)
+msgid "To list the extra-specifications, use this command:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:214(term)
-msgid "Flat"
+#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:123(para)
+msgid "If a volume type points to a <literal>volume_backend_name</literal> that does not exist in the Block Storage configuration, the <literal>filter_scheduler</literal> returns an error that it cannot find a valid host with the suitable back-end."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:216(para)
-msgid "All instances reside on the same network, which can also be shared with the hosts. No VLAN tagging or other network segregation takes place."
+#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:132(title)
+msgid "Usage"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:223(term)
-msgid "Local"
+#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:133(para)
+msgid "When you create a volume, you must specify the volume type. The extra-specifications of the volume type are used to determine which back-end has to be used. <placeholder-1/> Considering the <literal>cinder.conf</literal> described previously, the scheduler creates this volume on <literal>lvmdriver-1</literal> or <literal>lvmdriver-2</literal>."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:225(para)
-msgid "Instances reside on the local compute host and are effectively isolated from any external networks."
+#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:142(para)
+msgid "This second volume is created on <literal>lvmdriver-3</literal>."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:231(term)
-msgid "VLAN"
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:6(title)
+msgid "Migrate volumes"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:233(para)
-msgid "Networking allows users to create multiple provider or tenant networks using VLAN IDs (802.1Q tagged) that correspond to VLANs present in the physical network. This allows instances to communicate with each other across the environment. They can also communicate with dedicated servers, firewalls, load balancers and other networking infrastructure on the same layer 2 VLAN."
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:7(para)
+msgid "OpenStack has the ability to migrate volumes between back-ends. Migrating a volume transparently moves its data from the current back-end for the volume to a new one. This is an administrator function, and can be used for functions including storage evacuation (for maintenance or decommissioning), or manual optimizations (for example, performance, reliability, or cost)."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:243(term)
-msgid "VXLAN and GRE"
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:14(para)
+msgid "These workflows are possible for a migration:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:245(para)
-msgid "VXLAN and GRE use network overlays to support private communication between instances. A Networking router is required to enable traffic to traverse outside of the GRE or VXLAN tenant network. A router is also required to connect directly-connected tenant networks with external networks, including the Internet; the router provides the ability to connect to instances directly from an external network using floating IP addresses."
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:17(para)
+msgid "If the storage can migrate the volume on its own, it is given the opportunity to do so. This allows the Block Storage driver to enable optimizations that the storage might be able to perform. If the back-end is not able to perform the migration, the Block Storage uses one of two generic flows, as follows."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:258(title) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:11(title)
-msgid "Provider networks"
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:25(para)
+msgid "If the volume is not attached, the Block Storage service creates a volume and copies the data from the original to the new volume."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:259(para)
-msgid "Provider networks are created by the OpenStack administrator and map directly to an existing physical network in the data center. Useful network types in this category are flat (untagged) and VLAN (802.1Q tagged). It is possible to allow provider networks to be shared among tenants as part of the network creation process."
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:29(para)
+msgid "While most back-ends support this function, not all do. See the driver documentation in the <link href=\"http://docs.openstack.org/icehouse/config-reference/content/\"><citetitle>OpenStack Configuration Reference</citetitle></link> for more details."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:267(title)
-msgid "VMware NSX integration"
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:38(para)
+msgid "If the volume is attached to a VM instance, the Block Storage creates a volume, and calls Compute to copy the data from the original to the new volume. Currently this is supported only by the Compute libvirt driver."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:268(para)
-msgid "OpenStack Networking uses the NSX plugin for Networking to integrate with an existing VMware vCenter deployment. When installed on the network nodes, the NSX plugin enables a NSX controller to centrally manage configuration settings and push them to managed network nodes. Network nodes are considered managed when they're added as hypervisors to the NSX controller."
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:45(para)
+msgid "As an example, this scenario shows two LVM back-ends and migrates an attached volume from one to the other. This scenario uses the third migration flow."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:274(para)
-msgid "The diagram below depicts an example NSX deployment and illustrates the route inter-VM traffic takes between separate Compute nodes. Note the placement of the VMware NSX plugin and the <systemitem class=\"service\">neutron-server</systemitem> service on the network node. The NSX controller features centrally with a green line to the network node to indicate the management relationship:"
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:48(para)
+msgid "First, list the available back-ends:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_arch.xml:281(title)
-msgid "VMware NSX overview"
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:52(para)
+msgid "Next, as the admin user, you can see the current status of the volume (replace the example ID with your own):"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:6(title)
-msgid "Advanced features through API extensions"
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:76(para)
+msgid "Note these attributes:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:7(para)
-msgid "Several plug-ins implement API extensions that provide capabilities similar to what was available in nova-network: These plug-ins are likely to be of interest to the OpenStack community."
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:79(para)
+msgid "<literal>os-vol-host-attr:host</literal> - the volume's current back-end."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:12(para)
-msgid "Networks can be categorized as either \"tenant networks\" or \"provider networks\". Tenant networks are created by normal users and details about how they are physically realized are hidden from those users. Provider networks are created with administrative credentials, specifying the details of how the network is physically realized, usually to match some existing network in the data center."
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:83(para)
+msgid "<literal>os-vol-mig-status-attr:migstat</literal> - the status of this volume's migration (<literal>None</literal> means that a migration is not currently in progress)."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:17(para)
-msgid "Provider networks enable cloud administrators to create Networking networks that map directly to the physical networks in the data center. This is commonly used to give tenants direct access to a public network that can be used to reach the Internet. It might also be used to integrate with VLANs in the network that already have a defined meaning (for example, enable a VM from the \"marketing\" department to be placed on the same VLAN as bare-metal marketing hosts in the same data center)."
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:88(para)
+msgid "<literal>os-vol-mig-status-attr:name_id</literal> - the volume ID that this volume's name on the back-end is based on. Before a volume is ever migrated, its name on the back-end storage may be based on the volume's ID (see the <option>volume_name_template</option> configuration parameter). For example, if <option>volume_name_template</option> is kept as the default value (<literal>volume-%s</literal>), your first LVM back-end has a logical volume named <literal>volume-6088f80a-f116-4331-ad48-9afb0dfb196c</literal>. During the course of a migration, if you create a volume and copy over the data, the volume get the new name but keeps its original ID. This is exposed by the <literal>name_id</literal> attribute."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:23(para)
-msgid "The provider extension allows administrators to explicitly manage the relationship between Networking virtual networks and underlying physical mechanisms such as VLANs and tunnels. When this extension is supported, Networking client users with administrative privileges see additional provider attributes on all virtual networks and are able to specify these attributes in order to create provider networks."
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:106(para)
+msgid "If you plan to decommission a block storage node, you must stop the <systemitem class=\"service\">cinder</systemitem> volume service on the node after performing the migration."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:28(para)
-msgid "The provider extension is supported by the Open vSwitch and Linux Bridge plug-ins. Configuration of these plug-ins requires familiarity with this extension."
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:109(para)
+msgid "On nodes that run CentOS, Fedora, openSUSE, RedHat Enterprise Linux, or SUSE Linux Enterprise, run:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:31(title)
-msgid "Terminology"
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:114(para)
+msgid "On nodes that run Ubuntu or Debian, run:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:32(para)
-msgid "A number of terms are used in the provider extension and in the configuration of plug-ins supporting the provider extension:"
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:118(para)
+msgid "Stopping the <systemitem>cinder</systemitem> volume service will prevent volumes from being allocated to the node."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:35(caption)
-msgid "Provider extension terminology"
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:121(para)
+msgid "Migrate this volume to the second LVM back-end:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:40(th)
-msgid "Term"
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:123(para)
+msgid "You can use the <placeholder-1/> command to see the status of the migration. While migrating, the <literal>migstat</literal> attribute shows states such as <literal>migrating</literal> or <literal>completing</literal>. On error, <literal>migstat</literal> is set to <literal>None</literal> and the <literal>host</literal> attribute shows the original host. On success, in this example, the output looks like:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:46(emphasis)
-msgid "virtual network"
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:153(para)
+msgid "Note that <literal>migstat</literal> is None, <literal>host</literal> is the new host, and <literal>name_id</literal> holds the ID of the volume created by the migration. If you look at the second LVM back end, you find the logical volume <literal>volume-133d1f56-9ffc-4f57-8798-d5217d851862</literal>."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:47(td)
-msgid "An Networking L2 network (identified by a UUID and optional name) whose ports can be attached as vNICs to Compute instances and to various Networking agents. The Open vSwitch and Linux Bridge plug-ins each support several different mechanisms to realize virtual networks."
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:160(para)
+msgid "The migration is not visible to non-admin users (for example, through the volume <literal>status</literal>). However, some operations are not allowed while a migration is taking place, such as attaching/detaching a volume and deleting a volume. If a user performs such an action during a migration, an error is returned."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:53(emphasis)
-msgid "physical network"
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:168(para)
+msgid "Migrating volumes that have snapshots are currently not allowed."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:54(td)
-msgid "A network connecting virtualization hosts (such as compute nodes) with each other and with other network resources. Each physical network might support multiple virtual networks. The provider extension and the plug-in configurations identify physical networks using simple string names."
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_non_existent_vlun.xml:4(title)
+msgid "Non-existent VLUN"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:61(emphasis)
-msgid "tenant network"
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_non_existent_vlun.xml:7(para)
+msgid "This error occurs if the 3PAR host exists with the correct host name that the OpenStack Block Storage drivers expect but the volume was created in a different Domain."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:62(td)
-msgid "A virtual network that a tenant or an administrator creates. The physical details of the network are not exposed to the tenant."
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_non_existent_vlun.xml:13(para)
+msgid "The <code>hp3par_domain</code> configuration items either need to be updated to use the domain the 3PAR host currently resides in, or the 3PAR host needs to be moved to the domain that the volume was created in."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:66(emphasis)
-msgid "provider network"
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-backups-export-import.xml:6(title)
+msgid "Export and import backup metadata"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:67(td)
-msgid "A virtual network administratively created to map to a specific network in the data center, typically to enable direct access to non-OpenStack resources on that network. Tenants can be given access to provider networks."
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-backups-export-import.xml:7(para)
+msgid "A volume backup can only be restored on the same Block Storage service. This is because restoring a volume from a backup requires metadata available on the database used by the Block Storage service."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:73(emphasis)
-msgid "VLAN network"
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-backups-export-import.xml:11(para)
+msgid "For information on how to back up and restore a volume, see <xref linkend=\"volume-backup-restore\"/>."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:74(td)
-msgid "A virtual network implemented as packets on a specific physical network containing IEEE 802.1Q headers with a specific VID field value. VLAN networks sharing the same physical network are isolated from each other at L2 and can even have overlapping IP address spaces. Each distinct physical network supporting VLAN networks is treated as a separate VLAN trunk, with a distinct space of VID values. Valid VID values are 1 through 4094."
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-backups-export-import.xml:13(para)
+msgid "You can, however, export the metadata of a volume backup. To do so, run this command as an OpenStack <literal>admin</literal> user (presumably, after creating a volume backup):"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:83(emphasis)
-msgid "flat network"
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-backups-export-import.xml:17(replaceable) ./doc/admin-guide-cloud/blockstorage/section_volume-backups.xml:19(replaceable)
+msgid "backup_ID"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:84(td)
-msgid "A virtual network implemented as packets on a specific physical network containing no IEEE 802.1Q header. Each physical network can realize at most one flat network."
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-backups-export-import.xml:18(para)
+msgid "Where <replaceable>backup_ID</replaceable> is the volume backup's ID. This command should return the backup's corresponding database information as encoded string metadata."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:89(emphasis)
-msgid "local network"
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-backups-export-import.xml:21(para)
+msgid "Exporting and storing this encoded string metadata allows you to completely restore the backup, even in the event of a catastrophic database failure. This will preclude the need to back up the entire Block Storage database, particularly if you only need to keep complete backups of a small subset of volumes."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:90(td)
-msgid "A virtual network that allows communication within each host, but not across a network. Local networks are intended mainly for single-node test scenarios, but can have other uses."
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-backups-export-import.xml:27(para)
+msgid "In addition, having a volume backup and its backup metadata also provides volume portability. Specifically, backing up a volume and exporting its metadata will allow you to restore the volume on a completely different Block Storage database, or even on a different cloud service. To do so, first import the backup metadata to the Block Storage database and then restore the backup."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:95(emphasis)
-msgid "GRE network"
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-backups-export-import.xml:33(para)
+msgid "To import backup metadata, run the following command as an OpenStack <literal>admin</literal>:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:98(emphasis)
-msgid "tunnels"
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-backups-export-import.xml:35(replaceable)
+msgid "metadata"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:96(td)
-msgid "A virtual network implemented as network packets encapsulated using GRE. GRE networks are also referred to as <placeholder-1/>. GRE tunnel packets are routed by the IP routing table for the host, so GRE networks are not associated by Networking with specific physical networks."
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-backups-export-import.xml:36(para)
+msgid "Where <replaceable>metadata</replaceable> is the backup metadata exported earlier."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:103(emphasis)
-msgid "Virtual Extensible LAN (VXLAN) network"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:105(td)
-msgid "VXLAN is a proposed encapsulation protocol for running an overlay network on existing Layer 3 infrastructure. An overlay network is a virtual network that is built on top of existing network Layer 2 and Layer 3 technologies to support elastic compute architectures."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:112(para)
-msgid "The ML2, Open vSwitch, and Linux Bridge plug-ins support VLAN networks, flat networks, and local networks. Only the ML2 and Open vSwitch plug-ins currently support GRE and VXLAN networks, provided that the required features exist in the hosts Linux kernel, Open vSwitch, and iproute2 packages."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:118(title)
-msgid "Provider attributes"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:119(para)
-msgid "The provider extension extends the Networking network resource with these attributes:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:122(caption)
-msgid "Provider network attributes"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:129(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:257(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:315(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:611(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:654(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:866(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:988(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1056(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1177(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1492(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1581(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1622(th)
-msgid "Attribute name"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:130(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:258(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:316(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:612(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:655(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:867(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:989(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1057(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1178(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1582(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1623(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:124(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:197(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:301(th)
-msgid "Type"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:131(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:259(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:317(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:613(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:656(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:868(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:990(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1058(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1179(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1583(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1624(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:198(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:302(th)
-msgid "Default Value"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:137(td)
-msgid "provider:network_type"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:138(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:152(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:272(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:285(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:626(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:633(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:675(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:681(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:699(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:888(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:894(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:919(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:965(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1010(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1016(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1078(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1084(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1098(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1200(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1218(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1596(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1602(td)
-msgid "String"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:139(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:164(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:286(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:294(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:338(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:347(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:369(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:640(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:676(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:718(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:882(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1004(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1072(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1099(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1213(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1231(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1609(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1645(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1661(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:165(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:179(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:220(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:276(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:283(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:361(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:368(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:375(td)
-msgid "N/A"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:141(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:154(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:168(literal)
-msgid "flat"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:141(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:146(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:155(literal)
-msgid "vlan"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:142(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:147(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:158(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:169(literal)
-msgid "local"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:140(td)
-msgid "The physical mechanism by which the virtual network is implemented. Possible values are <placeholder-1/>, <placeholder-2/>, <placeholder-3/>, and <placeholder-4/>, corresponding to flat networks, VLAN networks, local networks, and GRE networks as defined above. All types of provider networks can be created by administrators, while tenant networks can be implemented as <placeholder-5/>, <placeholder-6/>, or <placeholder-7/> network types depending on plug-in configuration."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:151(td)
-msgid "provider:physical_network"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:153(td)
-msgid "If a physical network named \"default\" has been configured and if provider:network_type is <placeholder-1/> or <placeholder-2/>, then \"default\" is used."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:156(td)
-msgid "The name of the physical network over which the virtual network is implemented for flat and VLAN networks. Not applicable to the <placeholder-1/> or <placeholder-2/> network types."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:162(td)
-msgid "provider:segmentation_id"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:163(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:687(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:693(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:957(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1206(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1212(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1224(td)
-msgid "Integer"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:165(td)
-msgid "For VLAN networks, the VLAN VID on the physical network that realizes the virtual network. Valid VLAN VIDs are 1 through 4094. For GRE networks, the tunnel ID. Valid tunnel IDs are any 32 bit unsigned integer. Not applicable to the <placeholder-1/> or <placeholder-2/> network types."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:173(para)
-msgid "To view or set provider extended attributes, a client must be authorized for the <code>extension:provider_network:view</code> and <code>extension:provider_network:set</code> actions in the Networking policy configuration. The default Networking configuration authorizes both actions for users with the admin role. An authorized client or an administrative user can view and set the provider extended attributes through Networking API calls. See <xref linkend=\"section_networking_auth\"/> for details on policy configuration."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:182(title)
-msgid "Provider extension API operations"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:183(para)
-msgid "To use the provider extension with the default policy settings, you must have the administrative role."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:185(para)
-msgid "This list shows example neutron commands that enable you to complete basic provider extension API operations:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:189(para)
-msgid "Shows all attributes of a network, including provider attributes:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:194(para)
-msgid "Creates a local provider network:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:198(para)
-msgid "When you create flat networks, &lt;phys-net-name&gt; must be known to the plug-in. See the <citetitle>OpenStack Configuration Reference</citetitle> for details. Creates a flat provider network:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:205(para)
-msgid "When you create VLAN networks, &lt;phys-net-name&gt; must be known to the plug-in. See the <citetitle>OpenStack Configuration Reference</citetitle> for details on configuring network_vlan_ranges to identify all physical networks. When you create VLAN networks, &lt;VID&gt; can fall either within or outside any configured ranges of VLAN IDs from which tenant networks are allocated. Creates a VLAN provider network:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:216(para)
-msgid "When you create GRE networks, &lt;tunnel-id&gt; can be either inside or outside any tunnel ID ranges from which tenant networks are allocated."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:219(para)
-msgid "After you create provider networks, you can allocate subnets, which you can use in the same way as other virtual networks, subject to authorization policy based on the specified &lt;tenant_id&gt;. Creates a GRE provider network:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:229(title)
-msgid "L3 routing and NAT"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:230(para)
-msgid "The Networking API provides abstract L2 network segments that are decoupled from the technology used to implement the L2 network. Networking includes an API extension that provides abstract L3 routers that API users can dynamically provision and configure. These Networking routers can connect multiple L2 Networking networks and can also provide a gateway that connects one or more private L2 networks to a shared external network. For example, a public network for access to the Internet. See the <citetitle>OpenStack Configuration Reference</citetitle> for details on common models of deploying Networking L3 routers."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:239(para)
-msgid "The L3 router provides basic NAT capabilities on gateway ports that uplink the router to external networks. This router SNATs all traffic by default and supports floating IPs, which creates a static one-to-one mapping from a public IP on the external network to a private IP on one of the other subnets attached to the router. This allows a tenant to selectively expose VMs on private networks to other hosts on the external network (and often to all hosts on the Internet). You can allocate and map floating IPs from one port to another, as needed."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:248(title)
-msgid "L3 API abstractions"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:250(caption)
-msgid "Router"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:265(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:323(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:619(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:662(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:874(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:996(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1064(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1185(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1589(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1630(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:140(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:255(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:340(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:422(option)
-msgid "id"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:266(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:293(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:324(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:337(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:346(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:353(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:368(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:620(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:639(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:663(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:717(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:875(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:881(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:997(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1003(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1065(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1071(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1186(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1230(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1590(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1608(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1631(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1644(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:141(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:178(td)
-msgid "uuid-str"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:267(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:325(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:621(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:664(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:876(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:998(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1066(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1187(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1591(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1632(td)
-msgid "generated"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:268(td)
-msgid "UUID for the router."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:271(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:625(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:887(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1009(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1077(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1199(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1595(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:146(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:267(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:352(option)
-msgid "name"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:273(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:627(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:634(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:682(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:688(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:694(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:700(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:706(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:889(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:895(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:920(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:932(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:938(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:945(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:952(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:958(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1011(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1017(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1032(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1079(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1085(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1128(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1201(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1597(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1603(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:148(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:269(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:318(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:326(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:354(td)
-msgid "None"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:274(td)
-msgid "Human-readable name for the router. Might not be unique."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:277(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1090(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:131(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:308(option)
-msgid "admin_state_up"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:278(td)
-msgid "Bool"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:280(td)
-msgid "The administrative state of router. If false (down), the router does not forward packets."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:284(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1097(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:163(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:366(option)
-msgid "status"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:288(para)
-msgid "Indicates whether router is currently operational."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:292(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:367(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:638(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:716(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:880(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1002(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1070(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1229(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1607(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:177(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:281(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:373(option)
-msgid "tenant_id"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:295(td)
-msgid "Owner of the router. Only admin users can specify a tenant_id other than its own."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:299(td)
-msgid "external_gateway_info"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:300(td)
-msgid "dict contain 'network_id' key-value pair"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:301(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:354(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:361(td)
-msgid "Null"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:302(td)
-msgid "External network that this router connects to for gateway services (for example, NAT)"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:308(caption)
-msgid "Floating IP"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:326(td)
-msgid "UUID for the floating IP."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:329(td)
-msgid "floating_ip_address"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:330(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:360(td)
-msgid "string (IP address)"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:331(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:670(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:902(td)
-msgid "allocated by Networking"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:332(td)
-msgid "The external network IP address available to be mapped to an internal IP address."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:336(td)
-msgid "floating_network_id"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:340(para)
-msgid "The network indicating the set of subnets from which the floating IP should be allocated"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:345(td)
-msgid "router_id"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:348(td)
-msgid "Read-only value indicating the router that connects the external network to the associated internal port, if a port is associated."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:352(td)
-msgid "port_id"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:355(td)
-msgid "Indicates the internal Networking port associated with the external floating IP."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:359(td)
-msgid "fixed_ip_address"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:362(td)
-msgid "Indicates the IP address on the internal port that is mapped to by the floating IP (since an Networking port might have more than one IP address)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:370(td)
-msgid "Owner of the Floating IP. Only admin users can specify a tenant_id other than its own."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:378(title) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:385(caption) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1675(caption)
-msgid "Basic L3 operations"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:379(para)
-msgid "External networks are visible to all users. However, the default policy settings enable only administrative users to create, update, and delete external networks."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:382(para)
-msgid "This table shows example neutron commands that enable you to complete basic L3 operations:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:390(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:735(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1247(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1680(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:401(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:482(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:614(th)
-msgid "Operation"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:391(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:736(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1248(th) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1681(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:402(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:483(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:542(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:615(th)
-msgid "Command"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:397(para)
-msgid "Creates external networks."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:406(para)
-msgid "Lists external networks."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:414(para)
-msgid "Creates an internal-only router that connects to multiple L2 networks privately."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:429(para)
-msgid "Connects a router to an external network, which enables that router to act as a NAT gateway for external connectivity."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:434(para)
-msgid "The router obtains an interface with the gateway_ip address of the subnet and this interface is attached to a port on the L2 Networking network associated with the subnet. The router also gets a gateway interface to the specified external network. This provides SNAT connectivity to the external network as well as support for floating IPs allocated on that external networks. Commonly an external network maps to a network in the provider"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:445(para)
-msgid "Lists routers."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:453(para)
-msgid "Shows information for a specified router."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:461(para)
-msgid "Shows all internal interfaces for a router."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:466(para)
-msgid "Identifies the <literal>port-id</literal> that represents the VM NIC to which the floating IP should map."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:471(para)
-msgid "This port must be on an Networking subnet that is attached to a router uplinked to the external network used to create the floating IP. Conceptually, this is because the router must be able to perform the Destination NAT (DNAT) rewriting of packets from the Floating IP address (chosen from a subnet on the external network) to the internal Fixed IP (chosen from a private subnet that is behind the router)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:482(para)
-msgid "Creates a floating IP address and associates it with a port."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:492(para)
-msgid "Creates a floating IP address and associates it with a port, in a single step."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:501(para)
-msgid "Lists floating IPs."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:509(para)
-msgid "Finds floating IP for a specified VM port."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:517(para)
-msgid "Disassociates a floating IP address."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:525(para)
-msgid "Deletes the floating IP address."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:533(para)
-msgid "Clears the gateway."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:541(para)
-msgid "Removes the interfaces from the router."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:549(para)
-msgid "Deletes the router."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:561(title)
-msgid "Security groups"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:562(para)
-msgid "Security groups and security group rules allows administrators and tenants the ability to specify the type of traffic and direction (ingress/egress) that is allowed to pass through a port. A security group is a container for security group rules."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:565(para)
-msgid "When a port is created in Networking it is associated with a security group. If a security group is not specified the port is associated with a 'default' security group. By default, this group drops all ingress traffic and allows all egress. Rules can be added to this group in order to change the behaviour."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:569(para)
-msgid "To use the Compute security group APIs or use Compute to orchestrate the creation of ports for instances on specific security groups, you must complete additional configuration. You must configure the <filename>/etc/nova/nova.conf</filename> file and set the <code>security_group_api=neutron</code> option on every node that runs <systemitem class=\"service\">nova-compute</systemitem> and <systemitem class=\"service\">nova-api</systemitem>. After you make this change, restart <systemitem class=\"service\">nova-api</systemitem> and <systemitem class=\"service\">nova-compute</systemitem> to pick up this change. Then, you can use both the Compute and OpenStack Network security group APIs at the same time."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:581(para)
-msgid "To use the Compute security group API with Networking, the Networking plug-in must implement the security group API. The following plug-ins currently implement this: ML2, Open vSwitch, Linux Bridge, NEC, Ryu, and VMware NSX."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:587(para)
-msgid "You must configure the correct firewall driver in the <literal>securitygroup</literal> section of the plug-in/agent configuration file. Some plug-ins and agents, such as Linux Bridge Agent and Open vSwitch Agent, use the no-operation driver as the default, which results in non-working security groups."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:594(para)
-msgid "When using the security group API through Compute, security groups are applied to all ports on an instance. The reason for this is that Compute security group APIs are instances based and not port based as Networking."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:602(title)
-msgid "Security group API abstractions"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:604(caption)
-msgid "Security group attributes"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:622(td)
-msgid "UUID for the security group."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:628(td)
-msgid "Human-readable name for the security group. Might not be unique. Cannot be named default as that is automatically created for a tenant."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:632(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:893(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1015(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1083(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1601(td)
-msgid "description"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:635(td)
-msgid "Human-readable description of a security group."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:641(td)
-msgid "Owner of the security group. Only admin users can specify a tenant_id other than their own."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:647(caption)
-msgid "Security group rules"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:665(td)
-msgid "UUID for the security group rule."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:668(td)
-msgid "security_group_id"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:669(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:711(td)
-msgid "uuid-str or Integer"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:671(td)
-msgid "The security group to associate rule with."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:674(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1636(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1724(replaceable)
-msgid "direction"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:677(td)
-msgid "The direction the traffic is allow (ingress/egress) from a VM."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:680(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:918(td)
-msgid "protocol"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:683(td)
-msgid "IP Protocol (icmp, tcp, udp, and so on)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:686(td)
-msgid "port_range_min"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:689(td)
-msgid "Port at start of range"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:692(td)
-msgid "port_range_max"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:695(td)
-msgid "Port at end of range"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:698(td)
-msgid "ethertype"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:701(td)
-msgid "ethertype in L2 packet (IPv4, IPv6, and so on)"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:704(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1659(td)
-msgid "remote_ip_prefix"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:705(td)
-msgid "string (IP cidr)"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:707(td)
-msgid "CIDR for address range"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:710(td)
-msgid "remote_group_id"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:712(td)
-msgid "allocated by Networking or Compute"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:713(td)
-msgid "Source security group to apply to rule."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:719(td)
-msgid "Owner of the security group rule. Only admin users can specify a tenant_id other than its own."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:726(title) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:730(caption)
-msgid "Basic security group operations"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:727(para)
-msgid "This table shows example neutron commands that enable you to complete basic security group operations:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:742(para)
-msgid "Creates a security group for our web servers."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:750(para)
-msgid "Lists security groups."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:758(para)
-msgid "Creates a security group rule to allow port 80 ingress."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:766(para)
-msgid "Lists security group rules."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:774(para)
-msgid "Deletes a security group rule."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:782(para)
-msgid "Deletes a security group."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:790(para)
-msgid "Creates a port and associates two security groups."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:798(para)
-msgid "Removes security groups from a port."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:810(title)
-msgid "Basic Load-Balancer-as-a-Service operations"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:812(para)
-msgid "The Load-Balancer-as-a-Service (LBaaS) API provisions and configures load balancers. The Havana release offers a reference implementation that is based on the HAProxy software load balancer."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:816(para)
-msgid "This list shows example neutron commands that enable you to complete basic LBaaS operations:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:820(para)
-msgid "Creates a load balancer pool by using specific provider."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:821(para)
-msgid "<parameter>--provider</parameter> is an optional argument. If not used, the pool is created with default provider for LBaaS service. You should configure the default provider in the <literal>[service_providers]</literal> section of <filename>neutron.conf</filename> file. If no default provider is specified for LBaaS, the <parameter>--provider</parameter> option is required for pool creation."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:828(parameter)
-msgid "--provider &lt;provider_name&gt;"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:831(para)
-msgid "Associates two web servers with pool."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:836(para)
-msgid "Creates a health monitor which checks to make sure our instances are still running on the specified protocol-port."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:841(para)
-msgid "Associates a health monitor with pool."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:845(para)
-msgid "Creates a virtual IP (VIP) address that, when accessed through the load balancer, directs the requests to one of the pool members."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:853(title)
-msgid "Firewall-as-a-Service"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:854(para)
-msgid "The Firewall-as-a-Service (FWaaS) API is an experimental API that enables early adopters and vendors to test their networking implementations."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:857(title)
-msgid "Firewall-as-a-Service API abstractions"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:859(caption)
-msgid "Firewall rules"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:877(td)
-msgid "UUID for the firewall rule."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:883(td)
-msgid "Owner of the firewall rule. Only admin users can specify a tenant_id other than its own."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:890(td)
-msgid "Human readable name for the firewall rule (255 characters limit)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:896(td)
-msgid "Human readable description for the firewall rule (1024 characters limit)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:900(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1126(td)
-msgid "firewall_policy_id"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:901(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1127(td)
-msgid "uuid-str or None"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:903(td)
-msgid "This is a read-only attribute that gets populated with the uuid of the firewall policy when this firewall rule is associated with a firewall policy. A firewall rule can be associated with only one firewall policy at a time. However, the association can be changed to a different firewall policy."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:910(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1022(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:153(option)
-msgid "shared"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:911(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:972(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1023(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1038(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1091(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1192(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1652(td)
-msgid "Boolean"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:912(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1024(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1039(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1447(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1653(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:155(td)
-msgid "False"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:913(td)
-msgid "When set to True makes this firewall rule visible to tenants other than its owner and it can be used in firewall policies not owned by its tenant."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:921(td)
-msgid "IP Protocol (icmp, tcp, udp, None)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:924(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:261(option)
-msgid "ip_version"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:925(td)
-msgid "Integer or String"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:926(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:263(td)
-msgid "4"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:927(td)
-msgid "IP Version (4, 6)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:930(td)
-msgid "source_ip_address"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:931(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:937(td)
-msgid "String (IP address or CIDR)"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:933(td)
-msgid "Source IP address or CIDR."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:936(td)
-msgid "destination_ip_address"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:939(td)
-msgid "Destination IP address or CIDR."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:942(td)
-msgid "source_port"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:943(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:950(td)
-msgid "Integer or String (either as a single port number or in the format of a ':' separated range)"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:946(td)
-msgid "Source port number or a range."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:949(td)
-msgid "destination_port"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:953(td)
-msgid "Destination port number or a range."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:956(td)
-msgid "position"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:959(td)
-msgid "This is a read-only attribute that gets assigned to this rule when the rule is associated with a firewall policy. It indicates the position of this rule in that firewall policy."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:964(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1514(td)
-msgid "action"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:966(td)
-msgid "deny"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:967(td)
-msgid "Action to be performed on the traffic matching the rule (allow, deny)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:971(td)
-msgid "enabled"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:974(td)
-msgid "When set to False, disables this rule in the firewall policy. Facilitates selectively turning off rules without having to disassociate the rule from the firewall policy."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:981(caption)
-msgid "Firewall policies"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:999(td)
-msgid "UUID for the firewall policy."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1005(td)
-msgid "Owner of the firewall policy. Only admin users can specify a tenant_id other their own."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1012(td)
-msgid "Human readable name for the firewall policy (255 characters limit)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1018(td)
-msgid "Human readable description for the firewall policy (1024 characters limit)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1025(td)
-msgid "When set to True makes this firewall policy visible to tenants other than its owner and can be used to associate with firewalls not owned by its tenant."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1030(td)
-msgid "firewall_rules"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1031(td)
-msgid "List of uuid-str or None"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1033(td)
-msgid "This is an ordered list of firewall rule uuids. The firewall applies the rules in the order in which they appear in this list."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1037(td)
-msgid "audited"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1040(td)
-msgid "When set to True by the policy owner indicates that the firewall policy has been audited. This attribute is meant to aid in the firewall policy audit workflows. Each time the firewall policy or the associated firewall rules are changed, this attribute is set to False and must be explicitly set to True through an update operation."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1049(caption)
-msgid "Firewalls"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1067(td)
-msgid "UUID for the firewall."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1073(td)
-msgid "Owner of the firewall. Only admin users can specify a tenant_id other than its own."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1080(td)
-msgid "Human readable name for the firewall (255 characters limit)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1086(td)
-msgid "Human readable description for the firewall (1024 characters limit)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1093(td)
-msgid "The administrative state of the firewall. If False (down), the firewall does not forward any packets."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1101(para)
-msgid "Indicates whether the firewall is currently operational. Possible values include:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1105(para)
-msgid "ACTIVE"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1108(para)
-msgid "DOWN"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1111(para)
-msgid "PENDING_CREATE"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1114(para)
-msgid "PENDING_UPDATE"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1117(para)
-msgid "PENDING_DELETE"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1120(para)
-msgid "ERROR"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1129(td)
-msgid "The firewall policy uuid that this firewall is associated with. This firewall implements the rules contained in the firewall policy represented by this uuid."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1139(title)
-msgid "Plug-in specific extensions"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1141(para)
-msgid "Each vendor can choose to implement additional API extensions to the core API. This section describes the extensions for each plug-in."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1144(title)
-msgid "VMware NSX extensions"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1145(para)
-msgid "These sections explain NSX plug-in extensions."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1147(title)
-msgid "VMware NSX QoS extension"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1148(para)
-msgid "The VMware NSX QoS extension rate-limits network ports to guarantee a specific amount of bandwidth for each port. This extension, by default, is only accessible by a tenant with an admin role but is configurable through the <filename>policy.json</filename> file. To use this extension, create a queue and specify the min/max bandwidth rates (kbps) and optionally set the QoS Marking and DSCP value (if your network fabric uses these values to make forwarding decisions). Once created, you can associate a queue with a network. Then, when ports are created on that network they are automatically created and associated with the specific queue size that was associated with the network. Because one size queue for a every port on a network might not be optimal, a scaling factor from the nova flavor 'rxtx_factor' is passed in from Compute when creating the port to scale the queue."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1160(para)
-msgid "Lastly, if you want to set a specific baseline QoS policy for the amount of bandwidth a single port can use (unless a network queue is specified with the network a port is created on) a default queue can be created in Networking which then causes ports created to be associated with a queue of that size times the rxtx scaling factor. Note that after a network or default queue is specified, queues are added to ports that are subsequently created but are not added to existing ports."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1168(title)
-msgid "VMware NSX QoS API abstractions"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1170(caption)
-msgid "VMware NSX QoS attributes"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1188(td)
-msgid "UUID for the QoS queue."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1193(td)
-msgid "False by default"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1194(td)
-msgid "If True, ports are created with this queue size unless the network port is created or associated with a queue at port creation time."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1202(td)
-msgid "Name for QoS queue."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1205(td)
-msgid "min"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1207(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1225(td)
-msgid "0"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1208(td)
-msgid "Minimum Bandwidth Rate (kbps)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1211(td)
-msgid "max"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1214(td)
-msgid "Maximum Bandwidth Rate (kbps)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1217(td)
-msgid "qos_marking"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1219(td)
-msgid "untrusted by default"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1220(td)
-msgid "Whether QoS marking should be trusted or untrusted."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1223(td)
-msgid "dscp"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1226(td)
-msgid "DSCP Marking value."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1232(td)
-msgid "The owner of the QoS queue."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1238(title) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1242(caption)
-msgid "Basic VMware NSX QoS operations"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1239(para)
-msgid "This table shows example neutron commands that enable you to complete basic queue operations:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1254(para)
-msgid "Creates QoS Queue (admin-only)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1262(para)
-msgid "Associates a queue with a network."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1270(para)
-msgid "Creates a default system queue."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1278(para)
-msgid "Lists QoS queues."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1286(para)
-msgid "Deletes a QoS queue."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1297(title)
-msgid "VMware NSX provider networks extension"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1298(para)
-msgid "Provider networks can be implemented in different ways by the underlying NSX platform."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1300(para)
-msgid "The <emphasis>FLAT</emphasis> and <emphasis>VLAN</emphasis> network types use bridged transport connectors. These network types enable the attachment of large number of ports. To handle the increased scale, the NSX plug-in can back a single OpenStack Network with a chain of NSX logical switches. You can specify the maximum number of ports on each logical switch in this chain on the <literal>max_lp_per_bridged_ls</literal> parameter, which has a default value of 5,000."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1307(para)
-msgid "The recommended value for this parameter varies with the NSX version running in the back-end, as shown in the following table."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1310(caption)
-msgid "Recommended values for max_lp_per_bridged_ls"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1315(td)
-msgid "NSX version"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1316(td)
-msgid "Recommended Value"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1321(td)
-msgid "2.x"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1322(td)
-msgid "64"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1325(td)
-msgid "3.0.x"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1326(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1330(td)
-msgid "5,000"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1329(td)
-msgid "3.1.x"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1333(td)
-msgid "3.2.x"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1334(td)
-msgid "10,000"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1338(para)
-msgid "In addition to these network types, the NSX plug-in also supports a special <emphasis>l3_ext</emphasis> network type, which maps external networks to specific NSX gateway services as discussed in the next section."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1343(title)
-msgid "VMware NSX L3 extension"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1344(para)
-msgid "NSX exposes its L3 capabilities through gateway services which are usually configured out of band from OpenStack. To use NSX with L3 capabilities, first create a L3 gateway service in the NSX Manager. Next, in <filename> /etc/neutron/plugins/vmware/nsx.ini</filename> set <literal>default_l3_gw_service_uuid</literal> to this value. By default, routers are mapped to this gateway service."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1351(title)
-msgid "VMware NSX L3 extension operations"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1352(para)
-msgid "Create external network and map it to a specific NSX gateway service:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1356(para)
-msgid "Terminate traffic on a specific VLAN from a NSX gateway service:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1362(title)
-msgid "Operational status synchronization in the VMware NSX plug-in"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1363(para)
-msgid "Starting with the Havana release, the VMware NSX plug-in provides an asynchronous mechanism for retrieving the operational status for neutron resources from the NSX back-end; this applies to <emphasis>network</emphasis>, <emphasis>port</emphasis> and <emphasis>router</emphasis> resources."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1367(para)
-msgid "The back-end is polled periodically and the status for every resource is retrieved; then the status in the Networking database is updated only for the resources for which a status change occurred. As operational status is now retrieved asynchronously, performance for <literal>GET</literal> operations is consistently improved."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1372(para)
-msgid "Data to retrieve from the back-end are divided in chunks in order to avoid expensive API requests; this is achieved leveraging NSX APIs response paging capabilities. The minimum chunk size can be specified using a configuration option; the actual chunk size is then determined dynamically according to: total number of resources to retrieve, interval between two synchronization task runs, minimum delay between two subsequent requests to the NSX back-end."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1378(para)
-msgid "The operational status synchronization can be tuned or disabled using the configuration options reported in this table; it is however worth noting that the default values work fine in most cases."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1382(caption)
-msgid "Configuration options for tuning operational status synchronization in the NSX plug-in"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1391(th)
-msgid "Option name"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1392(th)
-msgid "Group"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1393(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:125(th)
-msgid "Default value"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1394(th)
-msgid "Type and constraints"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1395(th)
-msgid "Notes"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1400(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1406(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1425(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1438(literal)
-msgid "state_sync_interval"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1401(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1413(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1422(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1433(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1446(literal)
-msgid "nsx_sync"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1402(td)
-msgid "120 seconds"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1403(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1435(td)
-msgid "Integer; no constraint."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1404(td)
-msgid "Interval in seconds between two run of the synchronization task. If the synchronization task takes more than <placeholder-1/> seconds to execute, a new instance of the task is started as soon as the other is completed. Setting the value for this option to 0 will disable the synchronization task."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1412(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1417(literal)
-msgid "max_random_sync_delay"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1414(td)
-msgid "0 seconds"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1415(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1421(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1439(literal)
-msgid "min_sync_req_delay"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1415(td)
-msgid "Integer. Must not exceed <placeholder-1/>"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1416(td)
-msgid "When different from zero, a random delay between 0 and <placeholder-1/> will be added before processing the next chunk."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1423(td)
-msgid "10 seconds"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1424(td)
-msgid "Integer. Must not exceed <placeholder-1/>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1426(td)
-msgid "The value of this option can be tuned according to the observed load on the NSX controllers. Lower values will result in faster synchronization, but might increase the load on the controller cluster."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1432(literal) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1441(literal)
-msgid "min_chunk_size"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1434(td)
-msgid "500 resources"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1436(td)
-msgid "Minimum number of resources to retrieve from the back-end for each synchronization chunk. The expected number of synchronization chunks is given by the ratio between <placeholder-1/> and <placeholder-2/>. This size of a chunk might increase if the total number of resources is such that more than <placeholder-3/> resources must be fetched in one chunk with the current number of chunks."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1445(literal)
-msgid "always_read_status"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1448(td)
-msgid "Boolean; no constraint."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1450(literal)
-msgid "GET"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1449(td)
-msgid "When this option is enabled, the operational status will always be retrieved from the NSX back-end ad every <placeholder-1/> request. In this case it is advisable to disable the synchronization task."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1456(para)
-msgid "When running multiple OpenStack Networking server instances, the status synchronization task should not run on every node; doing so sends unnecessary traffic to the NSX back-end and performs unnecessary DB operations. Set the <option>state_sync_interval</option> configuration option to a non-zero value exclusively on a node designated for back-end status synchronization."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1462(para)
-msgid "The <parameter>fields=status</parameter> parameter in Networking API requests always triggers an explicit query to the NSX back end, even when you enable asynchronous state synchronization. For example, <code>GET /v2.0/networks/&lt;net-id&gt;?fields=status&amp;fields=name</code>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1469(title)
-msgid "Big Switch plug-in extensions"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1470(para)
-msgid "This section explains the Big Switch neutron plug-in-specific extension."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1472(title)
-msgid "Big Switch router rules"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1473(para)
-msgid "Big Switch allows router rules to be added to each tenant router. These rules can be used to enforce routing policies such as denying traffic between subnets or traffic to external networks. By enforcing these at the router level, network segmentation policies can be enforced across many VMs that have differing security groups."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1479(title)
-msgid "Router rule attributes"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1480(para)
-msgid "Each tenant router has a set of router rules associated with it. Each router rule has the attributes in this table. Router rules and their attributes can be set using the <placeholder-1/> command, through the horizon interface or the Networking API."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1485(caption)
-msgid "Big Switch Router rule attributes"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1493(th)
-msgid "Required"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1494(th)
-msgid "Input Type"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1500(td)
-msgid "source"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1502(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1509(td)
-msgid "A valid CIDR or one of the keywords 'any' or 'external'"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1503(td)
-msgid "The network that a packet's source IP must match for the rule to be applied"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1507(td)
-msgid "destination"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1510(td)
-msgid "The network that a packet's destination IP must match for the rule to be applied"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1516(td)
-msgid "'permit' or 'deny'"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1517(td)
-msgid "Determines whether or not the matched packets will allowed to cross the router"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1521(td)
-msgid "nexthop"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1522(td)
-msgid "No"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1524(literal)
-msgid "1.1.1.1+1.1.1.2"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1523(td)
-msgid "A plus-separated (+) list of next-hop IP addresses. For example, <placeholder-1/>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1525(td)
-msgid "Overrides the default virtual router used to handle traffic for packets that match the rule"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1532(title)
-msgid "Order of rule processing"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1533(para)
-msgid "The order of router rules has no effect. Overlapping rules are evaluated using longest prefix matching on the source and destination fields. The source field is matched first so it always takes higher precedence over the destination field. In other words, longest prefix matching is used on the destination field only if there are multiple matching rules with the same source."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1541(title)
-msgid "Big Switch router rules operations"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1542(para)
-msgid "Router rules are configured with a router update operation in OpenStack Networking. The update overrides any previous rules so all rules must be provided at the same time."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1545(para)
-msgid "Update a router with rules to permit traffic by default but block traffic from external networks to the 10.10.10.0/24 subnet:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1547(replaceable) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1551(replaceable) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1555(replaceable)
-msgid "Router-UUID"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1550(para)
-msgid "Specify alternate next-hop addresses for a specific subnet:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1554(para)
-msgid "Block traffic between two subnets while allowing everything else:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1563(title)
-msgid "L3 metering"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1564(para)
-msgid "The L3 metering API extension enables administrators to configure IP ranges and assign a specified label to them to be able to measure traffic that goes through a virtual router."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1567(para)
-msgid "The L3 metering extension is decoupled from the technology that implements the measurement. Two abstractions have been added: One is the metering label that can contain metering rules. Because a metering label is associated with a tenant, all virtual routers in this tenant are associated with this label."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1572(title)
-msgid "L3 metering API abstractions"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1574(caption)
-msgid "Label"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1592(td)
-msgid "UUID for the metering label."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1598(td)
-msgid "Human-readable name for the metering label. Might not be unique."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1604(td)
-msgid "The optional description for the metering label."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1610(td)
-msgid "Owner of the metering label."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1615(caption)
-msgid "Rules"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1633(td)
-msgid "UUID for the metering rule."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1637(td)
-msgid "String (Either ingress or egress)"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1638(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1725(replaceable)
-msgid "ingress"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1639(td)
-msgid "The direction in which metering rule is applied, either ingress or egress."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1643(td)
-msgid "metering_label_id"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1647(para)
-msgid "The metering label ID to associate with this metering rule."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1651(td)
-msgid "excluded"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1654(td)
-msgid "Specify whether the remote_ip_prefix will be excluded or not from traffic counters of the metering label (for example, to not count the traffic of a specific IP address of a range)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1660(td)
-msgid "String (CIDR)"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1662(td)
-msgid "Indicates remote IP prefix to be associated with this metering rule."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1670(title)
-msgid "Basic L3 metering operations"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1671(para)
-msgid "Only administrators can manage the L3 metering labels and rules."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1672(para)
-msgid "This table shows example <placeholder-1/> commands that enable you to complete basic L3 metering operations:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1687(para)
-msgid "Creates a metering label."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1690(replaceable) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1707(replaceable) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1716(replaceable) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1725(replaceable) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1726(replaceable)
-msgid "label1"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1690(replaceable)
-msgid "\"description of label1\""
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1695(para)
-msgid "Lists metering labels."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1703(para)
-msgid "Shows information for a specified label."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1706(replaceable) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1715(replaceable) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1724(replaceable)
-msgid "label-uuid"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1712(para)
-msgid "Deletes a metering label."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1721(para)
-msgid "Creates a metering rule."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1724(replaceable) ./doc/admin-guide-cloud/networking/section_networking-use.xml:207(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:218(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:241(option)
-msgid "cidr"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1725(replaceable)
-msgid "10.0.0.0/24"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1726(replaceable)
-msgid "20.0.0.0/24"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1731(para)
-msgid "Lists metering all label rules."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1739(para)
-msgid "Shows information for a specified label rule."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1742(replaceable) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1748(replaceable)
-msgid "rule-uuid"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1746(td)
-msgid "Deletes a metering label rule."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:6(title)
-msgid "Configure Identity Service for Networking"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:8(title)
-msgid "To configure the Identity Service for use with Networking"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:11(title)
-msgid "Create the <function>get_id()</function> function"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:12(para)
-msgid "The <function>get_id()</function> function stores the ID of created objects, and removes the need to copy and paste object IDs in later steps:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:16(para)
-msgid "Add the following function to your <filename>.bashrc</filename> file:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:23(para)
-msgid "Source the <filename>.bashrc</filename> file:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:29(title)
-msgid "Create the Networking service entry"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:30(para)
-msgid "Networking must be available in the Compute service catalog. Create the service:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:34(title)
-msgid "Create the Networking service endpoint entry"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:36(para)
-msgid "The way that you create a Networking endpoint entry depends on whether you are using the SQL or the template catalog driver:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:40(para)
-msgid "If you use the <emphasis>SQL driver</emphasis>, run the following command with the specified region (<literal>$REGION</literal>), IP address of the Networking server (<literal>$IP</literal>), and service ID (<literal>$NEUTRON_SERVICE_ID</literal>, obtained in the previous step)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:52(para)
-msgid "If you are using the <emphasis>template driver</emphasis>, specify the following parameters in your Compute catalog template file (<filename>default_catalog.templates</filename>), along with the region (<literal>$REGION</literal>) and IP address of the Networking server (<literal>$IP</literal>)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:70(title)
-msgid "Create the Networking service user"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:71(para)
-msgid "You must provide admin user credentials that Compute and some internal Networking components can use to access the Networking API. Create a special <literal>service</literal> tenant and a <literal>neutron</literal> user within this tenant, and assign an <literal>admin</literal> role to this role."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:77(para)
-msgid "Create the <literal>admin</literal> role:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:82(para)
-msgid "Create the <literal>neutron</literal> user:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:87(para)
-msgid "Create the <literal>service</literal> tenant:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:91(para)
-msgid "Establish the relationship among the tenant, user, and role:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:98(para)
-msgid "For information about how to create service entries and users, see the <citetitle>OpenStack Installation Guide</citetitle> for your distribution (<link href=\"docs.openstack.org\">docs.openstack.org</link>)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:103(para)
-msgid "If you use Networking, do not run the Compute <systemitem class=\"service\">nova-network</systemitem> service (like you do in traditional Compute deployments). Instead, Compute delegates most network-related decisions to Networking. Compute proxies tenant-facing API calls to manage security groups and floating IPs to Networking APIs. However, operator-facing tools such as <systemitem class=\"service\">nova-manage</systemitem>, are not proxied and should not be used."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:110(para)
-msgid "When you configure networking, you must use this guide. Do not rely on Compute networking documentation or past experience with Compute. If a <placeholder-1/> command or configuration option related to networking is not mentioned in this guide, the command is probably not supported for use with Networking. In particular, you cannot use CLI tools like <placeholder-2/> and <placeholder-3/> to manage networks or IP addressing, including both fixed and floating IPs, with Networking."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:118(para)
-msgid "Uninstall <systemitem class=\"service\">nova-network</systemitem> and reboot any physical nodes that have been running <systemitem class=\"service\">nova-network</systemitem> before using them to run Networking. Inadvertently running the <systemitem class=\"service\">nova-network</systemitem> process while using Networking can cause problems, as can stale iptables rules pushed down by previously running <systemitem class=\"service\">nova-network</systemitem>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:126(para)
-msgid "To ensure that Compute works properly with Networking (rather than the legacy <systemitem class=\"service\">nova-network</systemitem> mechanism), you must adjust settings in the <filename>nova.conf</filename> configuration file."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:133(title)
-msgid "Networking API and credential configuration"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:134(para)
-msgid "Each time you provision or de-provision a VM in Compute, <systemitem class=\"service\">nova-*</systemitem> services communicate with Networking using the standard API. For this to happen, you must configure the following items in the <filename>nova.conf</filename> file (used by each <systemitem class=\"service\">nova-compute</systemitem> and <systemitem class=\"service\">nova-api</systemitem> instance)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:140(caption)
-msgid "nova.conf API and credential settings"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:145(th) ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:220(td) ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:255(td)
-msgid "Item"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:151(literal)
-msgid "network_api_class"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:153(para)
-msgid "Modify from the default to <literal>nova.network.neutronv2.api.API</literal>, to indicate that Networking should be used rather than the traditional <systemitem class=\"service\">nova-network </systemitem> networking model."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:161(literal)
-msgid "neutron_url"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:162(para)
-msgid "Update to the hostname/IP and port of the <systemitem class=\"service\">neutron-server</systemitem> instance for this deployment."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:168(literal)
-msgid "neutron_auth_strategy"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:169(para)
-msgid "Keep the default <literal>keystone</literal> value for all production deployments."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:173(literal)
-msgid "neutron_admin_tenant_name"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:175(para)
-msgid "Update to the name of the service tenant created in the above section on Identity configuration."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:180(literal)
-msgid "neutron_admin_username"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:182(para)
-msgid "Update to the name of the user created in the above section on Identity configuration."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:187(literal)
-msgid "neutron_admin_password"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:189(para)
-msgid "Update to the password of the user created in the above section on Identity configuration."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:194(literal)
-msgid "neutron_admin_auth_url"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:196(para)
-msgid "Update to the Identity server IP and port. This is the Identity (keystone) admin API server IP and port value, and not the Identity service API IP and port."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:206(title)
-msgid "Configure security groups"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:207(para)
-msgid "The Networking Service provides security group functionality using a mechanism that is more flexible and powerful than the security group capabilities built into Compute. Therefore, if you use Networking, you should always disable built-in security groups and proxy all security group calls to the Networking API . If you do not, security policies will conflict by being simultaneously applied by both services."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:212(para)
-msgid "To proxy security groups to Networking, use the following configuration values in <filename>nova.conf</filename>:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:215(caption)
-msgid "nova.conf security group settings"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:226(literal)
-msgid "firewall_driver"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:227(para)
-msgid "Update to <literal>nova.virt.firewall.NoopFirewallDriver</literal>, so that <systemitem class=\"service\">nova-compute</systemitem> does not perform iptables-based filtering itself."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:234(literal)
-msgid "security_group_api"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:235(para)
-msgid "Update to <literal>neutron</literal>, so that all security group requests are proxied to the Network Service."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:242(title)
-msgid "Configure metadata"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:243(para)
-msgid "The Compute service allows VMs to query metadata associated with a VM by making a web request to a special 169.254.169.254 address. Networking supports proxying those requests to <systemitem class=\"service\">nova-api</systemitem>, even when the requests are made from isolated networks, or from multiple networks that use overlapping IP addresses."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:247(para)
-msgid "To enable proxying the requests, you must update the following fields in <filename>nova.conf</filename>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:250(caption)
-msgid "nova.conf metadata settings"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:261(literal)
-msgid "service_neutron_metadata_proxy"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:263(para)
-msgid "Update to <literal>true</literal>, otherwise <systemitem class=\"service\">nova-api</systemitem> will not properly respond to requests from the <systemitem class=\"service\">neutron-metadata-agent</systemitem>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:270(literal)
-msgid "neutron_metadata_proxy_shared_secret"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:272(para)
-msgid "Update to a string \"password\" value. You must also configure the same value in the <filename>metadata_agent.ini</filename> file, to authenticate requests made for metadata."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:276(para)
-msgid "The default value of an empty string in both files will allow metadata to function, but will not be secure if any non-trusted entities have access to the metadata APIs exposed by <systemitem class=\"service\">nova-api</systemitem>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:285(para)
-msgid "As a precaution, even when using <literal>neutron_metadata_proxy_shared_secret</literal>, it is recommended that you do not expose metadata using the same <systemitem class=\"service\">nova-api</systemitem> instances that are used for tenants. Instead, you should run a dedicated set of <systemitem class=\"service\">nova-api</systemitem> instances for metadata that are available only on your management network. Whether a given <systemitem class=\"service\">nova-api</systemitem> instance exposes metadata APIs is determined by the value of <literal>enabled_apis</literal> in its <filename>nova.conf</filename>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:300(title)
-msgid "Example nova.conf (for <systemitem class=\"service\">nova-compute</systemitem> and <systemitem class=\"service\">nova-api</systemitem>)"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:303(para)
-msgid "Example values for the above settings, assuming a cloud controller node running Compute and Networking with an IP address of 192.168.1.2:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:5(title)
-msgid "Use Networking"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:6(para)
-msgid "You can manage OpenStack Networking services using the <systemitem>service</systemitem> command. For example:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:13(para)
-msgid "Log files are in the <systemitem>/var/log/neutron</systemitem> directory."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:16(para)
-msgid "Configuration files are in the <systemitem>/etc/neutron</systemitem> directory."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:19(para)
-msgid "You can use Networking in the following ways:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:22(para)
-msgid "Expose the Networking API to cloud tenants, enabling them to build rich network topologies."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:26(para)
-msgid "Have the cloud administrator, or an automated administrative tool, create network connectivity on behalf of tenants."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:31(para)
-msgid "A tenant or cloud administrator can both perform the following procedures."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:34(title)
-msgid "Core Networking API features"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:35(para)
-msgid "After you install and run Networking, tenants and administrators can perform create-read-update-delete (CRUD) API networking operations by using the Networking API directly or the neutron command-line interface (CLI). The neutron CLI is a wrapper around the Networking API. Every Networking API call has a corresponding neutron command."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:42(para)
-msgid "The CLI includes a number of options. For details, refer to the <link href=\"http://docs.openstack.org/user-guide/content/\"><citetitle>OpenStack End User Guide</citetitle></link>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:48(title) ./doc/admin-guide-cloud/networking/section_networking-use.xml:56(caption)
-msgid "API abstractions"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:49(para)
-msgid "The Networking v2.0 API provides control over both L2 network topologies and their allocated IP addresses (IP Address Management or IPAM). There is also an extension to cover basic L3 forwarding and NAT, which provides capabilities similar to <placeholder-1/>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:61(th)
-msgid "Abstraction"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:69(td)
-msgid "An isolated L2 network segment (similar to a VLAN) that forms the basis for describing the L2 network topology available in an Networking deployment."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:78(td)
-msgid "Associates a block of IP addresses and other network configuration, such as default gateways or dns-servers, with an Networking network. Each subnet represents an IPv4 or IPv6 address block, and each Networking network can have multiple subnets."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:90(td)
-msgid "Represents an attachment port to a L2 Networking network. When a port is created on the network, by default it is allocated an available fixed IP address out of one of the designated subnets for each IP version (if one exists). When the port is destroyed, its allocated addresses return to the pool of available IPs on the subnet. Users of the Networking API can either choose a specific IP address from the block, or let Networking choose the first available IP address."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:109(para)
-msgid "This table summarizes the attributes available for each networking abstraction. For information about API abstraction and operations, see the <link href=\"http://docs.openstack.org/api/openstack-network/2.0/content/\">Networking API v2.0 Reference</link>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:116(caption)
-msgid "Network attributes"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:123(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:196(th) ./doc/admin-guide-cloud/networking/section_networking-use.xml:300(th)
-msgid "Attribute"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:132(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:154(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:233(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:309(td)
-msgid "bool"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:134(td)
-msgid "Administrative state of the network. If specified as False (down), this network does not forward packets."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:142(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:257(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:342(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:348(td)
-msgid "Generated"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:143(td)
-msgid "UUID for this network."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:147(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:164(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:219(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:240(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:268(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:317(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:325(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:347(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:353(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:367(td)
-msgid "string"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:149(td)
-msgid "Human-readable name for this network; is not required to be unique."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:156(td)
-msgid "Specifies whether this network resource can be accessed by any tenant. The default policy setting restricts usage of this attribute to administrative users only."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:166(td)
-msgid "Indicates whether this network is currently operational."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:170(option)
-msgid "subnets"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:171(td)
-msgid "list(uuid-str)"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:172(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:227(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:249(td)
-msgid "Empty list"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:173(td)
-msgid "List of subnets associated with this network."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:180(td)
-msgid "Tenant owner of the network. Only administrative users can set the tenant identifier; this cannot be changed using authorization policies."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:189(caption)
-msgid "Subnet attributes"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:204(option)
-msgid "allocation_pools"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:205(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:248(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:332(td)
-msgid "list(dict)"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:208(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:239(option)
-msgid "gateway_ip"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:206(td)
-msgid "Every address in <placeholder-1/>, excluding <placeholder-2/> (if configured)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:210(para)
-msgid "List of cidr sub-ranges that are available for dynamic allocation to ports. Syntax:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:221(td)
-msgid "IP range for this subnet, based on the IP version."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:225(option)
-msgid "dns_nameservers"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:226(td)
-msgid "list(string)"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:228(td)
-msgid "List of DNS name servers used by hosts in this subnet."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:232(option)
-msgid "enable_dhcp"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:235(td)
-msgid "Specifies whether DHCP is enabled for this subnet."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:241(td)
-msgid "First address in <placeholder-1/>"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:243(td)
-msgid "Default gateway used by devices in this subnet."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:247(option)
-msgid "host_routes"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:250(td)
-msgid "Routes that should be used by devices with IPs from this subnet (not including local subnet route)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:256(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:275(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:282(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:341(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:360(td) ./doc/admin-guide-cloud/networking/section_networking-use.xml:374(td)
-msgid "uuid-string"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:258(td)
-msgid "UUID representing this subnet."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:262(td)
-msgid "int"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:264(td)
-msgid "IP version."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:270(td)
-msgid "Human-readable name for this subnet (might not be unique)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:274(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:359(option)
-msgid "network_id"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:277(td)
-msgid "Network with which this subnet is associated."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:284(td)
-msgid "Owner of network. Only administrative users can set the tenant identifier; this cannot be changed using authorization policies."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:293(caption)
-msgid "Port attributes"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:310(td)
-msgid "true"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:311(td)
-msgid "Administrative state of this port. If specified as False (down), this port does not forward packets."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:316(option)
-msgid "device_id"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:319(td)
-msgid "Identifies the device using this port (for example, a virtual server's ID)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:324(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:424(option)
-msgid "device_owner"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:327(td)
-msgid "Identifies the entity using this port (for example, a dhcp agent)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:331(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:423(option)
-msgid "fixed_ips"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:333(td)
-msgid "Automatically allocated from pool"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:334(td)
-msgid "Specifies IP addresses for this port; associates the port with the subnets containing the listed IP addresses."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:343(td)
-msgid "UUID for this port."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:346(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:568(option)
-msgid "mac_address"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:349(td)
-msgid "Mac address to use on this port."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:355(td)
-msgid "Human-readable name for this port (might not be unique)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:362(td)
-msgid "Network with which this port is associated."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:369(td)
-msgid "Indicates whether the network is currently operational."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:376(td)
-msgid "Owner of the network. Only administrative users can set the tenant identifier; this cannot be changed using authorization policies."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:386(title) ./doc/admin-guide-cloud/networking/section_networking-use.xml:396(caption)
-msgid "Basic Networking operations"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:387(para)
-msgid "To learn about advanced capabilities available through the neutron command-line interface (CLI), read the networking section in the <link href=\"http://docs.openstack.org/user-guide/content/index.html\"> OpenStack End User Guide</link>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:392(para)
-msgid "This table shows example neutron commands that enable you to complete basic network operations:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:407(td)
-msgid "Creates a network."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:411(td)
-msgid "Creates a subnet that is associated with net1."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:416(td)
-msgid "Lists ports for a specified tenant."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:421(td)
-msgid "Lists ports for a specified tenant and displays the <placeholder-1/>, <placeholder-2/>, and <placeholder-3/> columns."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:430(td)
-msgid "Shows information for a specified port."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:432(replaceable) ./doc/admin-guide-cloud/networking/section_networking-use.xml:574(replaceable) ./doc/admin-guide-cloud/networking/section_networking-use.xml:627(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:631(replaceable)
-msgid "port-id"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:437(para)
-msgid "The <option>device_owner</option> field describes who owns the port. A port whose <option>device_owner</option> begins with:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:443(para)
-msgid "<literal>network</literal> is created by Networking."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:447(para)
-msgid "<literal>compute</literal> is created by Compute."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:454(title)
-msgid "Administrative operations"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:455(para)
-msgid "The cloud administrator can run any <placeholder-1/> command on behalf of tenants by specifying an Identity <option>tenant_id</option> in the command, as follows:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:460(replaceable)
-msgid "tenant-id"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:460(replaceable)
-msgid "network-name"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:464(para)
-msgid "To view all tenant IDs in Identity, run the following command as an Identity Service admin user:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:472(title) ./doc/admin-guide-cloud/networking/section_networking-use.xml:477(caption)
-msgid "Advanced Networking operations"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:473(para)
-msgid "This table shows example Networking commands that enable you to complete advanced network operations:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:488(td)
-msgid "Creates a network that all tenants can use."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:493(td)
-msgid "Creates a subnet with a specified gateway IP address."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:498(td)
-msgid "Creates a subnet that has no gateway IP address."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:503(td)
-msgid "Creates a subnet with DHCP disabled."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:508(td)
-msgid "Creates a subnet with a specified set of host routes."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:513(td)
-msgid "Creates a subnet with a specified set of dns name servers."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:518(td)
-msgid "Displays all ports and IPs allocated on a network."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:520(replaceable) ./doc/admin-guide-cloud/networking/section_networking-use.xml:553(replaceable) ./doc/admin-guide-cloud/networking/section_networking-use.xml:629(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:630(replaceable)
-msgid "net-id"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:528(title)
-msgid "Use Compute with Networking"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:530(title) ./doc/admin-guide-cloud/networking/section_networking-use.xml:535(caption)
-msgid "Basic Compute and Networking operations"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:531(para)
-msgid "This table shows example neutron and nova commands that enable you to complete basic VM networking operations:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:541(th)
-msgid "Action"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:547(td)
-msgid "Checks available networks."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:551(td)
-msgid "Boots a VM with a single NIC on a selected Networking network."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:553(replaceable) ./doc/admin-guide-cloud/networking/section_networking-use.xml:621(replaceable) ./doc/admin-guide-cloud/networking/section_networking-use.xml:631(replaceable) ./doc/admin-guide-cloud/networking/section_networking-use.xml:640(replaceable)
-msgid "img"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:553(replaceable) ./doc/admin-guide-cloud/networking/section_networking-use.xml:621(replaceable) ./doc/admin-guide-cloud/networking/section_networking-use.xml:631(replaceable) ./doc/admin-guide-cloud/networking/section_networking-use.xml:640(replaceable)
-msgid "flavor"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:553(replaceable) ./doc/admin-guide-cloud/networking/section_networking-use.xml:621(replaceable) ./doc/admin-guide-cloud/networking/section_networking-use.xml:631(replaceable) ./doc/admin-guide-cloud/networking/section_networking-use.xml:640(replaceable)
-msgid "vm-name"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:557(para)
-msgid "Searches for ports with a <option>device_id</option> that matches the Compute instance UUID. See <xref linkend=\"network_compute_note\"/>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:564(replaceable) ./doc/admin-guide-cloud/networking/section_networking-use.xml:569(replaceable)
-msgid "vm-id"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:567(td)
-msgid "Searches for ports, but shows only the <placeholder-1/> of the port."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:572(td)
-msgid "Temporarily disables a port from sending traffic."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:579(para)
-msgid "The <option>device_id</option> can also be a logical router ID."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:583(title)
-msgid "Create and delete VMs"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:586(para)
-msgid "When you boot a Compute VM, a port on the network that corresponds to the VM NIC is automatically created and associated with the default security group. You can configure <link linkend=\"enabling_ping_and_ssh\">security group rules</link> to enable users to access the VM."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:596(para)
-msgid "When you delete a Compute VM, the underlying Networking port is automatically deleted."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:604(title) ./doc/admin-guide-cloud/networking/section_networking-use.xml:609(caption)
-msgid "Advanced VM creation operations"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:605(para)
-msgid "This table shows example nova and neutron commands that enable you to complete advanced VM creation operations:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:620(td)
-msgid "Boots a VM with multiple NICs."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:621(replaceable)
-msgid "net1-id"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:621(replaceable)
-msgid "net2-id"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:624(td)
-msgid "Boots a VM with a specific IP address. First, create an Networking port with a specific IP address. Then, boot a VM specifying a <placeholder-1/> rather than a <placeholder-2/>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:630(replaceable)
-msgid "subnet-id"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:630(replaceable)
-msgid "IP"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:638(parameter)
-msgid "--nic"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:635(td)
-msgid "Boots a VM that connects to all networks that are accessible to the tenant who submits the request (without the <placeholder-1/> option)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:646(para)
-msgid "Networking does not currently support the <parameter>v4-fixed-ip</parameter> parameter of the <parameter>--nic</parameter> option for the <placeholder-1/> command."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:653(title)
-msgid "Enable ping and SSH on VMs (security groups)"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:655(para)
-msgid "You must configure security group rules depending on the type of plug-in you are using. If you are using a plug-in that:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:660(para)
-msgid "Implements Networking security groups, you can configure security group rules directly by using <placeholder-1/>. This example enables <placeholder-2/> and <placeholder-3/> access to your VMs."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:674(para)
-msgid "Does not implement Networking security groups, you can configure security group rules by using the <placeholder-1/> or <placeholder-2/> command. These <placeholder-3/> commands enable <placeholder-4/> and <placeholder-5/> access to your VMs."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:688(para)
-msgid "If your plug-in implements Networking security groups, you can also leverage Compute security groups by setting <code>security_group_api = neutron</code> in the <filename>nova.conf</filename> file. After you set this option, all Compute security group commands are proxied to Networking."
+#: ./doc/admin-guide-cloud/blockstorage/section_volume-backups-export-import.xml:38(para)
+msgid "Once you have imported the backup metadata into a Block Storage database, restore the volume (<xref linkend=\"volume-backup-restore\"/>)."
 msgstr ""
 
 #: ./doc/admin-guide-cloud/blockstorage/section_volume-backups.xml:6(title)
@@ -8177,10 +6421,6 @@ msgstr ""
 msgid "The previous command will also return a backup ID. Use this backup ID when restoring the volume, as in:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-backups.xml:19(replaceable) ./doc/admin-guide-cloud/blockstorage/section_volume-backups-export-import.xml:17(replaceable)
-msgid "backup_ID"
-msgstr ""
-
 #: ./doc/admin-guide-cloud/blockstorage/section_volume-backups.xml:20(para)
 msgid "As mentioned earlier, volume backups are dependent on the Block Storage database. Because of this, we recommend that you also back up your Block Storage database regularly in order to ensure data recovery."
 msgstr ""
@@ -8193,88 +6433,308 @@ msgstr ""
 msgid "For more information on how to export and import volume backup metadata, see <xref linkend=\"volume-backup-restore-export-import\"/>."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:11(title)
-msgid "Troubleshoot the Block Storage configuration"
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:5(title)
+msgid "Configure a GlusterFS back end"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:13(para)
-msgid "Most Block Storage errors are caused by incorrect volume configurations that result in volume creation failures. To resolve these failures, review these logs:"
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:6(para)
+msgid "This section explains how to configure OpenStack Block Storage to use GlusterFS as a back end. You must be able to access the GlusterFS shares from the server that hosts the <systemitem class=\"service\">cinder</systemitem> volume service."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:17(para)
-msgid "<systemitem class=\"service\">cinder-api</systemitem> log (<filename>/var/log/cinder/api.log</filename>)"
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:14(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:12(para)
+msgid "The <systemitem class=\"service\">cinder</systemitem> volume service is named <literal>openstack-cinder-volume</literal> on the following distributions:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:19(para)
-msgid "<systemitem class=\"service\">cinder-volume</systemitem> log (<filename>/var/log/cinder/volume.log</filename>)"
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:19(para) ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:194(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:17(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:100(para)
+msgid "CentOS"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:22(para)
-msgid "The <systemitem class=\"service\">cinder-api</systemitem> log is useful for determining if you have endpoint or connectivity issues. If you send a request to create a volume and it fails, review the <systemitem class=\"service\">cinder-api</systemitem> log to determine whether the request made it to the Block Storage service. If the request is logged and you see no errors or trace-backs, check the <systemitem class=\"service\">cinder-volume</systemitem> log for errors or trace-backs."
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:20(para) ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:197(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:18(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:103(para)
+msgid "Fedora"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:32(para)
-msgid "Create commands are listed in the <systemitem class=\"service\">cinder-api</systemitem> log."
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:21(para) ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:200(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:19(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:106(para)
+msgid "openSUSE"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:35(para)
-msgid "These entries in the <filename>cinder.openstack.common.log</filename> file can be used to assist in troubleshooting your block storage configuration."
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:22(para) ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:203(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:20(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:109(para)
+msgid "Red Hat Enterprise Linux"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:107(para)
-msgid "These common issues might occur during configuration. To correct, use these suggested solutions."
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:24(para) ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:206(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:22(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:112(para)
+msgid "SUSE Linux Enterprise"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:111(para)
-msgid "Issues with <literal>state_path</literal> and <literal>volumes_dir</literal> settings."
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:27(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:25(para)
+msgid "In Ubuntu and Debian distributions, the <systemitem class=\"service\">cinder</systemitem> volume service is named <literal>cinder-volume</literal>."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:113(para)
-msgid "The OpenStack Block Storage uses <placeholder-1/> as the default iscsi helper and implements persistent targets. This means that in the case of a tgt restart or even a node reboot your existing volumes on that node will be restored automatically with their original IQN."
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:31(para)
+msgid "Mounting GlusterFS volumes requires utilities and libraries from the <package>glusterfs-fuse</package> package. This package must be installed on all systems that will access volumes backed by GlusterFS."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:118(para)
-msgid "In order to make this possible the iSCSI target information needs to be stored in a file on creation that can be queried in case of restart of the tgt daemon. By default, Block Storage uses a <literal>state_path</literal> variable, which if installing with Yum or APT should be set to <filename>/var/lib/cinder/</filename>. The next part is the <literal>volumes_dir</literal> variable, by default this just simply appends a \"<literal>volumes</literal>\" directory to the <literal>state_path</literal>. The result is a file-tree <filename>/var/lib/cinder/volumes/</filename>."
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:38(para)
+msgid "The utilities and libraries required for mounting GlusterFS volumes on Ubuntu and Debian distributions are available from the <package>glusterfs-client</package> package instead."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:131(para)
-msgid "While the installer should handle all this, it can go wrong. If you have trouble creating volumes and this directory does not exist you should see an error message in the <systemitem class=\"service\">cinder-volume</systemitem> log indicating that the <literal>volumes_dir</literal> does not exist, and it should provide information about which path it was looking for."
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:44(para)
+msgid "For information on how to install and configure GlusterFS, refer to the <link href=\"http://gluster.org/community/documentation/index.php/Main_Page\">GlusterDocumentation</link> page."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:141(para)
-msgid "The persistent tgt include file."
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:49(title)
+msgid "Configure GlusterFS for OpenStack Block Storage"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:142(para)
-msgid "Along with the <option>volumes_dir</option> option, the iSCSI target driver also needs to be configured to look in the correct place for the persist files. This is a simple entry in the <filename>/etc/tgt/conf.d</filename> file that you should have set when you installed OpenStack. If issues occur, verify that you have a <filename>/etc/tgt/conf.d/cinder.conf</filename> file."
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:50(para)
+msgid "The GlusterFS server must also be configured accordingly in order to allow OpenStack Block Storage to use GlusterFS shares:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:151(para)
-msgid "If the file is not present, create it with this command:"
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:55(para)
+msgid "Log in as <systemitem>root</systemitem> to the GlusterFS server."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:156(para)
-msgid "No sign of attach call in the <systemitem class=\"service\">cinder-api</systemitem> log."
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:61(para)
+msgid "Set each Gluster volume to use the same UID and GID as the <systemitem>cinder</systemitem> user:"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:159(para)
-msgid "This is most likely going to be a minor adjustment to your <filename>nova.conf</filename> file. Make sure that your <filename>nova.conf</filename> has this entry:"
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:65(replaceable) ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:66(replaceable) ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:88(replaceable) ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:129(replaceable) ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:153(replaceable)
+msgid "VOL_NAME"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:166(para)
-msgid "Failed to create iscsi target error in the <filename>cinder-volume.log</filename> file."
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:65(replaceable)
+msgid "cinder-uid"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:170(para)
-msgid "You might see this error in <filename>cinder-volume.log</filename> after trying to create a volume that is 1GB. To fix this issue:"
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:66(replaceable)
+msgid "cinder-gid"
 msgstr ""
 
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:174(para)
-msgid "Change content of the <filename>/etc/tgt/targets.conf</filename> from <literal>include /etc/tgt/conf.d/*.conf</literal> to <literal>include /etc/tgt/conf.d/cinder_tgt.conf</literal>, as follows:"
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:69(para)
+msgid "<replaceable>VOL_NAME</replaceable> is the Gluster volume name."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:183(para)
-msgid "Restart <systemitem class=\"service\">tgt</systemitem> and <systemitem class=\"service\">cinder-*</systemitem> services so they pick up the new configuration."
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:71(para)
+msgid "<replaceable>cinder-uid</replaceable> is the UID of the <systemitem>cinder</systemitem> user."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:72(para)
+msgid "<replaceable>cinder-gid</replaceable> is the GID of the <systemitem>cinder</systemitem> user."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:75(para)
+msgid "The default UID and GID of the <systemitem>cinder</systemitem> user is <literal>165</literal> on most distributions."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:83(para)
+msgid "Configure each Gluster volume to accept <systemitem>libgfapi</systemitem> connections. To do this, set each Gluster volume to allow insecure ports:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:91(para)
+msgid "Enable client connections from unprivileged ports. To do this, add the following line to <filename>/etc/glusterfs/glusterd.vol</filename>:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:99(para)
+msgid "Restart the <systemitem>glusterd</systemitem> service:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:106(title)
+msgid "Configure Block Storage to use a GlusterFS back end"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:107(para)
+msgid "After you configure the GlusterFS service, complete these steps:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:112(para)
+msgid "Log in as <systemitem>root</systemitem> to the system hosting the cinder volume service."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:118(para)
+msgid "Create a text file named <filename>glusterfs</filename> in <filename>/etc/cinder/</filename>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:124(para)
+msgid "Add an entry to <filename>/etc/cinder/glusterfs</filename> for each GlusterFS share that OpenStack Block Storage should use for back end storage. Each entry should be a separate line, and should use the following format:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:129(replaceable) ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:153(replaceable) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:51(replaceable)
+msgid "HOST"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:135(para)
+msgid "<replaceable>HOST</replaceable> is the IP address or host name of the Red Hat Storage server."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:141(para)
+msgid "<replaceable>VOL_NAME</replaceable> is the name an existing and accessible volume on the GlusterFS server."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:148(para)
+msgid "Optionally, if your environment requires additional mount options for a share, you can add them to the share's entry:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:153(replaceable) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:131(replaceable)
+msgid "OPTIONS"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:154(para)
+msgid "Replace <replaceable>OPTIONS</replaceable> with a comma-separated list of mount options."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:160(para)
+msgid "Set <filename>/etc/cinder/glusterfs</filename> to be owned by the <systemitem>root</systemitem> user and the <systemitem>cinder</systemitem> group."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:167(para)
+msgid "Set <filename>/etc/cinder/glusterfs</filename> to be readable by members of the <systemitem>cinder</systemitem> group:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:171(replaceable)
+msgid "FILE"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:174(para)
+msgid "Configure OpenStack Block Storage to use the <filename>/etc/cinder/glusterfs</filename> file created earlier. To do so, open the <filename>/etc/cinder/cinder.conf</filename> configuration file and set the <literal>glusterfs_shares_config</literal> configuration key to <filename>/etc/cinder/glusterfs</filename>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:182(para) ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:219(para) ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:263(para) ./doc/admin-guide-cloud/blockstorage/section_increase-api-throughput.xml:37(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:88(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:125(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:150(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:191(para)
+msgid "On distributions that include <application>openstack-config</application>, you can configure this by running the following command instead:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:189(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:95(para)
+msgid "The following distributions include <application>openstack-config</application>:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:211(para)
+msgid "Configure OpenStack Block Storage to use the correct volume driver, namely <literal>cinder.volume.drivers.glusterfs</literal>. To do so, open the <filename>/etc/cinder/cinder.conf</filename> configuration file and set the <literal>volume_driver</literal> configuration key to <literal>cinder.volume.drivers.glusterfs</literal>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:227(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:158(para)
+msgid "You can now restart the service to apply the configuration."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:230(para)
+msgid "To restart the <systemitem class=\"service\">cinder</systemitem> volume service on CentOS, Fedora, openSUSE, RedHat Enterprise Linux, or SUSE Linux Enterprise, run:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:235(para)
+msgid "To restart the <systemitem class=\"service\">cinder</systemitem> volume service on Ubuntu or Debian, run:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:240(para)
+msgid "OpenStack Block Storage is now configured to use a GlusterFS back end."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:243(para)
+msgid "In <filename>/etc/cinder/cinder.conf</filename>, the <literal>glusterfs_sparsed_volumes</literal> configuration key determines whether volumes are created as sparse files and grown as needed or fully allocated up front. The default and recommended value of this key is <literal>true</literal>, which ensures volumes are initially created as sparse files."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:252(para)
+msgid "Setting <literal>glusterfs_sparsed_volumes</literal> to <literal>false</literal> will result in volumes being fully allocated at the time of creation. This leads to increased delays in volume creation."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:258(para)
+msgid "However, should you choose to set <literal>glusterfs_sparsed_volumes</literal> to <literal>false</literal>, you can do so directly in <filename>/etc/cinder/cinder.conf</filename>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:272(para)
+msgid "If a client host has SELinux enabled, the <systemitem>virt_use_fusefs</systemitem> Boolean should also be enabled if the host requires access to GlusterFS volumes on an instance. To enable this Boolean, run the following command as the <systemitem>root</systemitem> user:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:279(para)
+msgid "This command also makes the Boolean persistent across reboots. Run this command on all client hosts that require access to GlusterFS volumes on an instance. This includes all compute nodes."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_increase-api-throughput.xml:7(title)
+msgid "Increase Block Storage API service throughput"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_increase-api-throughput.xml:8(para)
+msgid "By default, the Block Storage API service runs in one process. This limits the number of API requests that the Block Storage service can process at any given time. In a production environment, you should increase the Block Storage API throughput by allowing the Block Storage API service to run in as many processes as the machine capacity allows."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_increase-api-throughput.xml:17(para)
+msgid "The Block Storage API service is named <literal>openstack-cinder-api</literal> on the following distributions: CentOS, Fedora, openSUSE, Red Hat Enterprise Linux, and SUSE Linux Enterprise. In Ubuntu and Debian distributions, the Block Storage API service is named <literal>cinder-api</literal>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_increase-api-throughput.xml:25(para)
+msgid "To do so, use the Block Storage API service option <parameter>osapi_volume_workers</parameter>. This option allows you to specify the number of API service workers (or OS processes) to launch for the Block Storage API service."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_increase-api-throughput.xml:31(para)
+msgid "To configure this option, open the <filename>/etc/cinder/cinder.conf</filename> configuration file and set the <literal>osapi_volume_workers</literal> configuration key to the number of CPU cores/threads on a machine."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_increase-api-throughput.xml:43(replaceable)
+msgid "CORES"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_increase-api-throughput.xml:44(para)
+msgid "Replace <replaceable>CORES</replaceable> with the number of CPU cores/threads on a machine."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_vol_attach_miss_sg_scan.xml:8(title)
+msgid "Failed to Attach Volume, Missing sg_scan"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_vol_attach_miss_sg_scan.xml:11(para)
+msgid "Failed to attach volume to an instance, <filename>sg_scan</filename> file not found. This warning and error occur when the <package>sg3-utils</package> package is not installed on the compute node. The IDs in your message are unique to your system:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_vol_attach_miss_sg_scan.xml:25(para)
+msgid "Run this command on the compute node to install the <package>sg3-utils</package> package:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_failed_attach_vol_no_sysfsutils.xml:4(title)
+msgid "Failed to attach volume, systool is not installed"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_failed_attach_vol_no_sysfsutils.xml:7(para)
+msgid "This warning and error occurs if you do not have the required <filename>sysfsutils</filename> package installed on the compute node."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_failed_attach_vol_no_sysfsutils.xml:16(para)
+msgid "Run the following command on the compute node to install the <filename>sysfsutils</filename> packages."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_failed_connect_vol_FC_SAN.xml:4(title)
+msgid "Failed to connect volume in FC SAN"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_failed_connect_vol_FC_SAN.xml:7(para)
+msgid "Compute node failed to connect to a volume in a Fibre Channel (FC) SAN configuration. The WWN may not be zoned correctly in your FC SAN that links the compute host to the storage array."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_failed_connect_vol_FC_SAN.xml:16(para)
+msgid "The network administrator must configure the FC SAN fabric by correctly zoning the WWN (port names) from your compute node HBAs."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_removal.xml:5(title)
+msgid "Gracefully remove a GlusterFS volume from usage"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_removal.xml:6(para)
+msgid "Configuring the <systemitem>cinder</systemitem> volume service to use GlusterFS involves creating a shares file (for example, <filename>/etc/cinder/glusterfs</filename>). This shares file lists each GlusterFS volume (with its corresponding storage server) that the <systemitem>cinder</systemitem> volume service can use for back end storage."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_removal.xml:13(para)
+msgid "To remove a GlusterFS volume from usage as a back end, delete the volume's corresponding entry from the shares file. After doing so, restart the Block Storage services."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_removal.xml:16(para)
+msgid "To restart the Block Storage services on CentOS, Fedora, openSUSE, Red Hat Enterprise Linux, or SUSE Linux Enterprise, run:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_removal.xml:20(para)
+msgid "To restart the Block Storage services on Ubuntu or Debian, run:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_removal.xml:23(para)
+msgid "Restarting the Block Storage services will prevent the <systemitem>cinder</systemitem> volume service from exporting the deleted GlusterFS volume. This will prevent any instances from mounting the volume from that point onwards."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_removal.xml:28(para)
+msgid "However, the removed GlusterFS volume might still be mounted on an instance at this point. Typically, this is the case when the volume was already mounted while its entry was deleted from the shares file. Whenever this occurs, you will have to unmount the volume as normal after the Block Storage services are restarted."
 msgstr ""
 
 #: ./doc/admin-guide-cloud/blockstorage/section_backup-block-storage-disks.xml:10(title)
@@ -8473,54 +6933,6 @@ msgstr ""
 msgid "The script also enables you to SSH to your instances and run a <placeholder-1/> command into them. To make this work, enable the connection to the Compute project keys. If you do not want to run the <placeholder-2/> command, you can add <literal>enable_mysql_dump=0</literal> to the script to turn off this functionality."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_failed_connect_vol_FC_SAN.xml:4(title)
-msgid "Failed to connect volume in FC SAN"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_failed_connect_vol_FC_SAN.xml:6(title) ./doc/admin-guide-cloud/blockstorage/section_ts_vol_attach_miss_sg_scan.xml:10(title) ./doc/admin-guide-cloud/blockstorage/section_ts_failed_attach_vol_after_detach.xml:8(title) ./doc/admin-guide-cloud/blockstorage/section_ts_non_existent_host.xml:6(title) ./doc/admin-guide-cloud/blockstorage/section_ts_no_emulator_x86_64.xml:6(title) ./doc/admin-guide-cloud/blockstorage/section_ts_HTTP_bad_req_in_cinder_vol_log.xml:8(title) ./doc/admin-guide-cloud/blockstorage/section_ts_non_existent_vlun.xml:6(title) ./doc/admin-guide-cloud/blockstorage/section_ts_failed_attach_vol_no_sysfsutils.xml:6(title) ./doc/admin-guide-cloud/blockstorage/section_ts_multipath_warn.xml:8(title) ./doc/admin-guide-cloud/blockstorage/section_ts_duplicate_3par_host.xml:6(title)
-msgid "Problem"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_failed_connect_vol_FC_SAN.xml:7(para)
-msgid "Compute node failed to connect to a volume in a Fibre Channel (FC) SAN configuration. The WWN may not be zoned correctly in your FC SAN that links the compute host to the storage array."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_failed_connect_vol_FC_SAN.xml:15(title) ./doc/admin-guide-cloud/blockstorage/section_ts_vol_attach_miss_sg_scan.xml:24(title) ./doc/admin-guide-cloud/blockstorage/section_ts_failed_attach_vol_after_detach.xml:14(title) ./doc/admin-guide-cloud/blockstorage/section_ts_non_existent_host.xml:14(title) ./doc/admin-guide-cloud/blockstorage/section_ts_no_emulator_x86_64.xml:11(title) ./doc/admin-guide-cloud/blockstorage/section_ts_HTTP_bad_req_in_cinder_vol_log.xml:43(title) ./doc/admin-guide-cloud/blockstorage/section_ts_non_existent_vlun.xml:12(title) ./doc/admin-guide-cloud/blockstorage/section_ts_failed_attach_vol_no_sysfsutils.xml:15(title) ./doc/admin-guide-cloud/blockstorage/section_ts_multipath_warn.xml:20(title) ./doc/admin-guide-cloud/blockstorage/section_ts_duplicate_3par_host.xml:12(title)
-msgid "Solution"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_failed_connect_vol_FC_SAN.xml:16(para)
-msgid "The network administrator must configure the FC SAN fabric by correctly zoning the WWN (port names) from your compute node HBAs."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_vol_attach_miss_sg_scan.xml:8(title)
-msgid "Failed to Attach Volume, Missing sg_scan"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_vol_attach_miss_sg_scan.xml:11(para)
-msgid "Failed to attach volume to an instance, <filename>sg_scan</filename> file not found. This warning and error occur when the <package>sg3-utils</package> package is not installed on the compute node. The IDs in your message are unique to your system:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_vol_attach_miss_sg_scan.xml:25(para)
-msgid "Run this command on the compute node to install the <package>sg3-utils</package> package:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_failed_attach_vol_after_detach.xml:5(title) ./doc/admin-guide-cloud/blockstorage/section_ts_HTTP_bad_req_in_cinder_vol_log.xml:5(title)
-msgid "Failed to attach volume after detaching"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_failed_attach_vol_after_detach.xml:9(para)
-msgid "Failed to attach a volume after detaching the same volume."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_failed_attach_vol_after_detach.xml:15(para)
-msgid "You must change the device name on the <placeholder-1/> command. The VM might not clean up after a <placeholder-2/> command runs. This example shows how the <placeholder-3/> command fails when you use the <code>vdb</code>, <code>vdc</code>, or <code>vdd</code> device names:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_failed_attach_vol_after_detach.xml:34(para)
-msgid "You might also have this problem after attaching and detaching the same volume from the same VM with the same mount point multiple times. In this case, restart the KVM host."
-msgstr ""
-
 #: ./doc/admin-guide-cloud/blockstorage/section_ts_non_existent_host.xml:4(title)
 msgid "Non-existent host"
 msgstr ""
@@ -8533,574 +6945,6 @@ msgstr ""
 msgid "Host names constructed by the driver use just the local hostname, not the fully qualified domain name (FQDN) of the Compute host. For example, if the FQDN was <emphasis>myhost.example.com</emphasis>, just <emphasis>myhost</emphasis> would be used as the 3PAR hostname. IP addresses are not allowed as host names on the 3PAR storage server."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/blockstorage/section_increase-api-throughput.xml:7(title)
-msgid "Increase Block Storage API service throughput"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_increase-api-throughput.xml:8(para)
-msgid "By default, the Block Storage API service runs in one process. This limits the number of API requests that the Block Storage service can process at any given time. In a production environment, you should increase the Block Storage API throughput by allowing the Block Storage API service to run in as many processes as the machine capacity allows."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_increase-api-throughput.xml:17(para)
-msgid "The Block Storage API service is named <literal>openstack-cinder-api</literal> on the following distributions: CentOS, Fedora, openSUSE, Red Hat Enterprise Linux, and SUSE Linux Enterprise. In Ubuntu and Debian distributions, the Block Storage API service is named <literal>cinder-api</literal>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_increase-api-throughput.xml:25(para)
-msgid "To do so, use the Block Storage API service option <parameter>osapi_volume_workers</parameter>. This option allows you to specify the number of API service workers (or OS processes) to launch for the Block Storage API service."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_increase-api-throughput.xml:31(para)
-msgid "To configure this option, open the <filename>/etc/cinder/cinder.conf</filename> configuration file and set the <literal>osapi_volume_workers</literal> configuration key to the number of CPU cores/threads on a machine."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_increase-api-throughput.xml:37(para) ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:182(para) ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:219(para) ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:263(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:88(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:125(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:150(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:191(para)
-msgid "On distributions that include <application>openstack-config</application>, you can configure this by running the following command instead:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_increase-api-throughput.xml:43(replaceable)
-msgid "CORES"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_increase-api-throughput.xml:44(para)
-msgid "Replace <replaceable>CORES</replaceable> with the number of CPU cores/threads on a machine."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-backups-export-import.xml:6(title)
-msgid "Export and import backup metadata"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-backups-export-import.xml:7(para)
-msgid "A volume backup can only be restored on the same Block Storage service. This is because restoring a volume from a backup requires metadata available on the database used by the Block Storage service."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-backups-export-import.xml:11(para)
-msgid "For information on how to back up and restore a volume, see <xref linkend=\"volume-backup-restore\"/>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-backups-export-import.xml:13(para)
-msgid "You can, however, export the metadata of a volume backup. To do so, run this command as an OpenStack <literal>admin</literal> user (presumably, after creating a volume backup):"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-backups-export-import.xml:18(para)
-msgid "Where <replaceable>backup_ID</replaceable> is the volume backup's ID. This command should return the backup's corresponding database information as encoded string metadata."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-backups-export-import.xml:21(para)
-msgid "Exporting and storing this encoded string metadata allows you to completely restore the backup, even in the event of a catastrophic database failure. This will preclude the need to back up the entire Block Storage database, particularly if you only need to keep complete backups of a small subset of volumes."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-backups-export-import.xml:27(para)
-msgid "In addition, having a volume backup and its backup metadata also provides volume portability. Specifically, backing up a volume and exporting its metadata will allow you to restore the volume on a completely different Block Storage database, or even on a different cloud service. To do so, first import the backup metadata to the Block Storage database and then restore the backup."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-backups-export-import.xml:33(para)
-msgid "To import backup metadata, run the following command as an OpenStack <literal>admin</literal>:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-backups-export-import.xml:35(replaceable)
-msgid "metadata"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-backups-export-import.xml:36(para)
-msgid "Where <replaceable>metadata</replaceable> is the backup metadata exported earlier."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-backups-export-import.xml:38(para)
-msgid "Once you have imported the backup metadata into a Block Storage database, restore the volume (<xref linkend=\"volume-backup-restore\"/>)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_no_emulator_x86_64.xml:4(title)
-msgid "Cannot find suitable emulator for x86_64"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_no_emulator_x86_64.xml:7(para)
-msgid "When you attempt to create a VM, the error shows the VM is in the <code>BUILD</code> then <code>ERROR</code> state."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_no_emulator_x86_64.xml:12(para)
-msgid "On the KVM host run, <code>cat /proc/cpuinfo</code>. Make sure the <code>vme</code> and <code>svm</code> flags are set."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_no_emulator_x86_64.xml:14(para)
-msgid "Follow the instructions in the <link href=\"http://docs.openstack.org/icehouse/config-reference/content/kvm.html#section_kvm_enable\"> enabling KVM section</link> of the <citetitle>Configuration Reference</citetitle> to enable hardware virtualization support in your BIOS."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:5(title)
-msgid "Configure a GlusterFS back end"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:6(para)
-msgid "This section explains how to configure OpenStack Block Storage to use GlusterFS as a back end. You must be able to access the GlusterFS shares from the server that hosts the <systemitem class=\"service\">cinder</systemitem> volume service."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:14(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:12(para)
-msgid "The <systemitem class=\"service\">cinder</systemitem> volume service is named <literal>openstack-cinder-volume</literal> on the following distributions:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:19(para) ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:194(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:17(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:100(para)
-msgid "CentOS"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:20(para) ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:197(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:18(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:103(para)
-msgid "Fedora"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:21(para) ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:200(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:19(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:106(para)
-msgid "openSUSE"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:22(para) ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:203(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:20(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:109(para)
-msgid "Red Hat Enterprise Linux"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:24(para) ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:206(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:22(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:112(para)
-msgid "SUSE Linux Enterprise"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:27(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:25(para)
-msgid "In Ubuntu and Debian distributions, the <systemitem class=\"service\">cinder</systemitem> volume service is named <literal>cinder-volume</literal>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:31(para)
-msgid "Mounting GlusterFS volumes requires utilities and libraries from the <package>glusterfs-fuse</package> package. This package must be installed on all systems that will access volumes backed by GlusterFS."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:38(para)
-msgid "The utilities and libraries required for mounting GlusterFS volumes on Ubuntu and Debian distributions are available from the <package>glusterfs-client</package> package instead."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:44(para)
-msgid "For information on how to install and configure GlusterFS, refer to the <link href=\"http://gluster.org/community/documentation/index.php/Main_Page\">GlusterDocumentation</link> page."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:49(title)
-msgid "Configure GlusterFS for OpenStack Block Storage"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:50(para)
-msgid "The GlusterFS server must also be configured accordingly in order to allow OpenStack Block Storage to use GlusterFS shares:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:55(para)
-msgid "Log in as <systemitem>root</systemitem> to the GlusterFS server."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:61(para)
-msgid "Set each Gluster volume to use the same UID and GID as the <systemitem>cinder</systemitem> user:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:65(replaceable) ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:66(replaceable) ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:88(replaceable) ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:129(replaceable) ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:153(replaceable)
-msgid "VOL_NAME"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:65(replaceable)
-msgid "cinder-uid"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:66(replaceable)
-msgid "cinder-gid"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:69(para)
-msgid "<replaceable>VOL_NAME</replaceable> is the Gluster volume name."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:71(para)
-msgid "<replaceable>cinder-uid</replaceable> is the UID of the <systemitem>cinder</systemitem> user."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:72(para)
-msgid "<replaceable>cinder-gid</replaceable> is the GID of the <systemitem>cinder</systemitem> user."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:75(para)
-msgid "The default UID and GID of the <systemitem>cinder</systemitem> user is <literal>165</literal> on most distributions."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:83(para)
-msgid "Configure each Gluster volume to accept <systemitem>libgfapi</systemitem> connections. To do this, set each Gluster volume to allow insecure ports:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:91(para)
-msgid "Enable client connections from unprivileged ports. To do this, add the following line to <filename>/etc/glusterfs/glusterd.vol</filename>:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:99(para)
-msgid "Restart the <systemitem>glusterd</systemitem> service:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:106(title)
-msgid "Configure Block Storage to use a GlusterFS back end"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:107(para)
-msgid "After you configure the GlusterFS service, complete these steps:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:112(para)
-msgid "Log in as <systemitem>root</systemitem> to the system hosting the cinder volume service."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:118(para)
-msgid "Create a text file named <filename>glusterfs</filename> in <filename>/etc/cinder/</filename>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:124(para)
-msgid "Add an entry to <filename>/etc/cinder/glusterfs</filename> for each GlusterFS share that OpenStack Block Storage should use for back end storage. Each entry should be a separate line, and should use the following format:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:129(replaceable) ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:153(replaceable) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:51(replaceable)
-msgid "HOST"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:135(para)
-msgid "<replaceable>HOST</replaceable> is the IP address or host name of the Red Hat Storage server."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:141(para)
-msgid "<replaceable>VOL_NAME</replaceable> is the name an existing and accessible volume on the GlusterFS server."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:148(para)
-msgid "Optionally, if your environment requires additional mount options for a share, you can add them to the share's entry:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:153(replaceable) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:131(replaceable)
-msgid "OPTIONS"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:154(para)
-msgid "Replace <replaceable>OPTIONS</replaceable> with a comma-separated list of mount options."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:160(para)
-msgid "Set <filename>/etc/cinder/glusterfs</filename> to be owned by the <systemitem>root</systemitem> user and the <systemitem>cinder</systemitem> group."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:167(para)
-msgid "Set <filename>/etc/cinder/glusterfs</filename> to be readable by members of the <systemitem>cinder</systemitem> group:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:171(replaceable)
-msgid "FILE"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:174(para)
-msgid "Configure OpenStack Block Storage to use the <filename>/etc/cinder/glusterfs</filename> file created earlier. To do so, open the <filename>/etc/cinder/cinder.conf</filename> configuration file and set the <literal>glusterfs_shares_config</literal> configuration key to <filename>/etc/cinder/glusterfs</filename>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:189(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:95(para)
-msgid "The following distributions include <application>openstack-config</application>:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:211(para)
-msgid "Configure OpenStack Block Storage to use the correct volume driver, namely <literal>cinder.volume.drivers.glusterfs</literal>. To do so, open the <filename>/etc/cinder/cinder.conf</filename> configuration file and set the <literal>volume_driver</literal> configuration key to <literal>cinder.volume.drivers.glusterfs</literal>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:227(para) ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:158(para)
-msgid "You can now restart the service to apply the configuration."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:230(para)
-msgid "To restart the <systemitem class=\"service\">cinder</systemitem> volume service on CentOS, Fedora, openSUSE, RedHat Enterprise Linux, or SUSE Linux Enterprise, run:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:235(para)
-msgid "To restart the <systemitem class=\"service\">cinder</systemitem> volume service on Ubuntu or Debian, run:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:240(para)
-msgid "OpenStack Block Storage is now configured to use a GlusterFS back end."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:243(para)
-msgid "In <filename>/etc/cinder/cinder.conf</filename>, the <literal>glusterfs_sparsed_volumes</literal> configuration key determines whether volumes are created as sparse files and grown as needed or fully allocated up front. The default and recommended value of this key is <literal>true</literal>, which ensures volumes are initially created as sparse files."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:252(para)
-msgid "Setting <literal>glusterfs_sparsed_volumes</literal> to <literal>false</literal> will result in volumes being fully allocated at the time of creation. This leads to increased delays in volume creation."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:258(para)
-msgid "However, should you choose to set <literal>glusterfs_sparsed_volumes</literal> to <literal>false</literal>, you can do so directly in <filename>/etc/cinder/cinder.conf</filename>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:272(para)
-msgid "If a client host has SELinux enabled, the <systemitem>virt_use_fusefs</systemitem> Boolean should also be enabled if the host requires access to GlusterFS volumes on an instance. To enable this Boolean, run the following command as the <systemitem>root</systemitem> user:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_backend.xml:279(para)
-msgid "This command also makes the Boolean persistent across reboots. Run this command on all client hosts that require access to GlusterFS volumes on an instance. This includes all compute nodes."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_HTTP_bad_req_in_cinder_vol_log.xml:9(para)
-msgid "These errors appear in the <filename>cinder-volume.log</filename> file."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_HTTP_bad_req_in_cinder_vol_log.xml:44(para)
-msgid "You need to update your copy of the <filename>hp_3par_fc.py</filename> driver which contains the synchronization code."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_non_existent_vlun.xml:4(title)
-msgid "Non-existent VLUN"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_non_existent_vlun.xml:7(para)
-msgid "This error occurs if the 3PAR host exists with the correct host name that the OpenStack Block Storage drivers expect but the volume was created in a different Domain."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_non_existent_vlun.xml:13(para)
-msgid "The <code>hp3par_domain</code> configuration items either need to be updated to use the domain the 3PAR host currently resides in, or the 3PAR host needs to be moved to the domain that the volume was created in."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_removal.xml:5(title)
-msgid "Gracefully remove a GlusterFS volume from usage"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_removal.xml:6(para)
-msgid "Configuring the <systemitem>cinder</systemitem> volume service to use GlusterFS involves creating a shares file (for example, <filename>/etc/cinder/glusterfs</filename>). This shares file lists each GlusterFS volume (with its corresponding storage server) that the <systemitem>cinder</systemitem> volume service can use for back end storage."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_removal.xml:13(para)
-msgid "To remove a GlusterFS volume from usage as a back end, delete the volume's corresponding entry from the shares file. After doing so, restart the Block Storage services."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_removal.xml:16(para)
-msgid "To restart the Block Storage services on CentOS, Fedora, openSUSE, Red Hat Enterprise Linux, or SUSE Linux Enterprise, run:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_removal.xml:20(para)
-msgid "To restart the Block Storage services on Ubuntu or Debian, run:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_removal.xml:23(para)
-msgid "Restarting the Block Storage services will prevent the <systemitem>cinder</systemitem> volume service from exporting the deleted GlusterFS volume. This will prevent any instances from mounting the volume from that point onwards."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_glusterfs_removal.xml:28(para)
-msgid "However, the removed GlusterFS volume might still be mounted on an instance at this point. Typically, this is the case when the volume was already mounted while its entry was deleted from the shares file. Whenever this occurs, you will have to unmount the volume as normal after the Block Storage services are restarted."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_failed_attach_vol_no_sysfsutils.xml:4(title)
-msgid "Failed to attach volume, systool is not installed"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_failed_attach_vol_no_sysfsutils.xml:7(para)
-msgid "This warning and error occurs if you do not have the required <filename>sysfsutils</filename> package installed on the compute node."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_failed_attach_vol_no_sysfsutils.xml:16(para)
-msgid "Run the following command on the compute node to install the <filename>sysfsutils</filename> packages."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:5(title)
-msgid "Configure a multiple-storage back-end"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:6(para)
-msgid "With multiple storage back-ends configured, you can create several back-end storage solutions serving the same OpenStack Compute configuration. Basically, multi back-end launches one <systemitem class=\"service\">cinder-volume</systemitem> for each back-end."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:11(para)
-msgid "In a multi back-end configuration, each back-end has a name (<literal>volume_backend_name</literal>). Several back-ends can have the same name. In that case, the scheduler properly decides which back-end the volume has to be created in."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:16(para)
-msgid "The name of the back-end is declared as an extra-specification of a volume type (such as, <literal>volume_backend_name=LVM_iSCSI</literal>). When a volume is created, the scheduler chooses an appropriate back-end to handle the request, according to the volume type specified by the user."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:23(title)
-msgid "Enable multi back-end"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:24(para)
-msgid "To enable a multi back-end configuration, you must set the <option>enabled_backends</option> flag in the <filename>cinder.conf</filename> file. This flag defines the names (separated by a comma) of the configuration groups for the different back-ends: one name is associated to one configuration group for a back-end (such as, <literal>[lvmdriver-1]</literal>)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:32(para)
-msgid "The configuration group name is not related to the <literal>volume_backend_name</literal>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:35(para)
-msgid "The options for a configuration group must be defined in the group (or default options are used). All the standard Block Storage configuration options (<literal>volume_group</literal>, <literal>volume_driver</literal>, and so on) might be used in a configuration group. Configuration values in the <literal>[DEFAULT]</literal> configuration group are not used."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:43(para)
-msgid "These examples show three back-ends:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:57(para)
-msgid "In this configuration, <literal>lvmdriver-1</literal> and <literal>lvmdriver-2</literal> have the same <literal>volume_backend_name</literal>. If a volume creation requests the <literal>LVM_iSCSI</literal> back-end name, the scheduler uses the capacity filter scheduler to choose the most suitable driver, which is either <literal>lvmdriver-1</literal> or <literal>lvmdriver-2</literal>. The capacity filter scheduler is enabled by default. The next section provides more information. In addition, this example presents a <literal>lvmdriver-3</literal> back-end."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:70(title)
-msgid "Configure Block Storage scheduler multi back-end"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:71(para)
-msgid "You must enable the <option>filter_scheduler</option> option to use multi back-end. Filter scheduler acts in two steps:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:76(para)
-msgid "The filter scheduler filters the available back-ends. By default, <literal>AvailabilityZoneFilter</literal>, <literal>CapacityFilter</literal> and <literal>CapabilitiesFilter</literal> are enabled."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:84(para)
-msgid "The filter scheduler weighs the previously filtered back-ends. By default, <literal>CapacityWeigher</literal> is enabled. The <literal>CapacityWeigher</literal> attributes higher scores to back-ends with the most available."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:92(para)
-msgid "The scheduler uses the filtering and weighing process to pick the best back-end to handle the request, and explicitly creates volumes on specific back-ends through the use of volume types."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:99(title)
-msgid "Volume type"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:100(para)
-msgid "Before using it, a volume type has to be declared to Block Storage. This can be done by the following command:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:103(para)
-msgid "Then, an extra-specification has to be created to link the volume type to a back-end name. Run this command:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:107(para)
-msgid "This example creates a <literal>lvm</literal> volume type with <literal>volume_backend_name=LVM_iSCSI</literal> as extra-specifications."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:110(para)
-msgid "Create another volume type:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:113(para)
-msgid "This second volume type is named <literal>lvm_gold</literal> and has <literal>LVM_iSCSI_b</literal> as back-end name."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:118(para)
-msgid "To list the extra-specifications, use this command:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:123(para)
-msgid "If a volume type points to a <literal>volume_backend_name</literal> that does not exist in the Block Storage configuration, the <literal>filter_scheduler</literal> returns an error that it cannot find a valid host with the suitable back-end."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:132(title)
-msgid "Usage"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:133(para)
-msgid "When you create a volume, you must specify the volume type. The extra-specifications of the volume type are used to determine which back-end has to be used. <placeholder-1/> Considering the <literal>cinder.conf</literal> described previously, the scheduler creates this volume on <literal>lvmdriver-1</literal> or <literal>lvmdriver-2</literal>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_multi_backend.xml:142(para)
-msgid "This second volume is created on <literal>lvmdriver-3</literal>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_multipath_warn.xml:6(title)
-msgid "Multipath Call Failed Exit"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_multipath_warn.xml:9(para)
-msgid "Multipath call failed exit. This warning occurs in the Compute log if you do not have the optional <filename>multipath-tools</filename> package installed on the compute node. This is an optional package and the volume attachment does work without the multipath tools installed. If the <filename>multipath-tools</filename> package is installed on the compute node, it is used to perform the volume attachment. The IDs in your message are unique to your system."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_ts_multipath_warn.xml:21(para)
-msgid "Run the following command on the compute node to install the <filename>multipath-tools</filename> packages."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:6(title)
-msgid "Migrate volumes"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:7(para)
-msgid "OpenStack has the ability to migrate volumes between back-ends. Migrating a volume transparently moves its data from the current back-end for the volume to a new one. This is an administrator function, and can be used for functions including storage evacuation (for maintenance or decommissioning), or manual optimizations (for example, performance, reliability, or cost)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:14(para)
-msgid "These workflows are possible for a migration:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:17(para)
-msgid "If the storage can migrate the volume on its own, it is given the opportunity to do so. This allows the Block Storage driver to enable optimizations that the storage might be able to perform. If the back-end is not able to perform the migration, the Block Storage uses one of two generic flows, as follows."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:25(para)
-msgid "If the volume is not attached, the Block Storage service creates a volume and copies the data from the original to the new volume."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:29(para)
-msgid "While most back-ends support this function, not all do. See the driver documentation in the <link href=\"http://docs.openstack.org/icehouse/config-reference/content/\"><citetitle>OpenStack Configuration Reference</citetitle></link> for more details."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:38(para)
-msgid "If the volume is attached to a VM instance, the Block Storage creates a volume, and calls Compute to copy the data from the original to the new volume. Currently this is supported only by the Compute libvirt driver."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:45(para)
-msgid "As an example, this scenario shows two LVM back-ends and migrates an attached volume from one to the other. This scenario uses the third migration flow."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:48(para)
-msgid "First, list the available back-ends:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:52(para)
-msgid "Next, as the admin user, you can see the current status of the volume (replace the example ID with your own):"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:76(para)
-msgid "Note these attributes:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:79(para)
-msgid "<literal>os-vol-host-attr:host</literal> - the volume's current back-end."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:83(para)
-msgid "<literal>os-vol-mig-status-attr:migstat</literal> - the status of this volume's migration (<literal>None</literal> means that a migration is not currently in progress)."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:88(para)
-msgid "<literal>os-vol-mig-status-attr:name_id</literal> - the volume ID that this volume's name on the back-end is based on. Before a volume is ever migrated, its name on the back-end storage may be based on the volume's ID (see the <option>volume_name_template</option> configuration parameter). For example, if <option>volume_name_template</option> is kept as the default value (<literal>volume-%s</literal>), your first LVM back-end has a logical volume named <literal>volume-6088f80a-f116-4331-ad48-9afb0dfb196c</literal>. During the course of a migration, if you create a volume and copy over the data, the volume get the new name but keeps its original ID. This is exposed by the <literal>name_id</literal> attribute."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:106(para)
-msgid "If you plan to decommission a block storage node, you must stop the <systemitem class=\"service\">cinder</systemitem> volume service on the node after performing the migration."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:109(para)
-msgid "On nodes that run CentOS, Fedora, openSUSE, RedHat Enterprise Linux, or SUSE Linux Enterprise, run:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:114(para)
-msgid "On nodes that run Ubuntu or Debian, run:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:118(para)
-msgid "Stopping the <systemitem>cinder</systemitem> volume service will prevent volumes from being allocated to the node."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:121(para)
-msgid "Migrate this volume to the second LVM back-end:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:123(para)
-msgid "You can use the <placeholder-1/> command to see the status of the migration. While migrating, the <literal>migstat</literal> attribute shows states such as <literal>migrating</literal> or <literal>completing</literal>. On error, <literal>migstat</literal> is set to <literal>None</literal> and the <literal>host</literal> attribute shows the original host. On success, in this example, the output looks like:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:153(para)
-msgid "Note that <literal>migstat</literal> is None, <literal>host</literal> is the new host, and <literal>name_id</literal> holds the ID of the volume created by the migration. If you look at the second LVM back end, you find the logical volume <literal>volume-133d1f56-9ffc-4f57-8798-d5217d851862</literal>."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:160(para)
-msgid "The migration is not visible to non-admin users (for example, through the volume <literal>status</literal>). However, some operations are not allowed while a migration is taking place, such as attaching/detaching a volume and deleting a volume. If a user performs such an action during a migration, an error is returned."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/blockstorage/section_volume-migration.xml:168(para)
-msgid "Migrating volumes that have snapshots are currently not allowed."
-msgstr ""
-
 #: ./doc/admin-guide-cloud/blockstorage/section_nfs_backend.xml:5(title)
 msgid "Configure an NFS storage back end"
 msgstr ""
@@ -9189,6 +7033,130 @@ msgstr ""
 msgid "This command also makes the Boolean persistent across reboots. Run this command on all client hosts that require access to NFS volumes on an instance. This includes all Compute nodes."
 msgstr ""
 
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_no_emulator_x86_64.xml:4(title)
+msgid "Cannot find suitable emulator for x86_64"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_no_emulator_x86_64.xml:7(para)
+msgid "When you attempt to create a VM, the error shows the VM is in the <code>BUILD</code> then <code>ERROR</code> state."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_no_emulator_x86_64.xml:12(para)
+msgid "On the KVM host run, <code>cat /proc/cpuinfo</code>. Make sure the <code>vme</code> and <code>svm</code> flags are set."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_no_emulator_x86_64.xml:14(para)
+msgid "Follow the instructions in the <link href=\"http://docs.openstack.org/icehouse/config-reference/content/kvm.html#section_kvm_enable\"> enabling KVM section</link> of the <citetitle>Configuration Reference</citetitle> to enable hardware virtualization support in your BIOS."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:11(title)
+msgid "Troubleshoot the Block Storage configuration"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:13(para)
+msgid "Most Block Storage errors are caused by incorrect volume configurations that result in volume creation failures. To resolve these failures, review these logs:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:17(para)
+msgid "<systemitem class=\"service\">cinder-api</systemitem> log (<filename>/var/log/cinder/api.log</filename>)"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:19(para)
+msgid "<systemitem class=\"service\">cinder-volume</systemitem> log (<filename>/var/log/cinder/volume.log</filename>)"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:22(para)
+msgid "The <systemitem class=\"service\">cinder-api</systemitem> log is useful for determining if you have endpoint or connectivity issues. If you send a request to create a volume and it fails, review the <systemitem class=\"service\">cinder-api</systemitem> log to determine whether the request made it to the Block Storage service. If the request is logged and you see no errors or trace-backs, check the <systemitem class=\"service\">cinder-volume</systemitem> log for errors or trace-backs."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:32(para)
+msgid "Create commands are listed in the <systemitem class=\"service\">cinder-api</systemitem> log."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:35(para)
+msgid "These entries in the <filename>cinder.openstack.common.log</filename> file can be used to assist in troubleshooting your block storage configuration."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:107(para)
+msgid "These common issues might occur during configuration. To correct, use these suggested solutions."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:111(para)
+msgid "Issues with <literal>state_path</literal> and <literal>volumes_dir</literal> settings."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:113(para)
+msgid "The OpenStack Block Storage uses <placeholder-1/> as the default iscsi helper and implements persistent targets. This means that in the case of a tgt restart or even a node reboot your existing volumes on that node will be restored automatically with their original IQN."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:118(para)
+msgid "In order to make this possible the iSCSI target information needs to be stored in a file on creation that can be queried in case of restart of the tgt daemon. By default, Block Storage uses a <literal>state_path</literal> variable, which if installing with Yum or APT should be set to <filename>/var/lib/cinder/</filename>. The next part is the <literal>volumes_dir</literal> variable, by default this just simply appends a \"<literal>volumes</literal>\" directory to the <literal>state_path</literal>. The result is a file-tree <filename>/var/lib/cinder/volumes/</filename>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:131(para)
+msgid "While the installer should handle all this, it can go wrong. If you have trouble creating volumes and this directory does not exist you should see an error message in the <systemitem class=\"service\">cinder-volume</systemitem> log indicating that the <literal>volumes_dir</literal> does not exist, and it should provide information about which path it was looking for."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:141(para)
+msgid "The persistent tgt include file."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:142(para)
+msgid "Along with the <option>volumes_dir</option> option, the iSCSI target driver also needs to be configured to look in the correct place for the persist files. This is a simple entry in the <filename>/etc/tgt/conf.d</filename> file that you should have set when you installed OpenStack. If issues occur, verify that you have a <filename>/etc/tgt/conf.d/cinder.conf</filename> file."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:151(para)
+msgid "If the file is not present, create it with this command:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:156(para)
+msgid "No sign of attach call in the <systemitem class=\"service\">cinder-api</systemitem> log."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:159(para)
+msgid "This is most likely going to be a minor adjustment to your <filename>nova.conf</filename> file. Make sure that your <filename>nova.conf</filename> has this entry:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:166(para)
+msgid "Failed to create iscsi target error in the <filename>cinder-volume.log</filename> file."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:170(para)
+msgid "You might see this error in <filename>cinder-volume.log</filename> after trying to create a volume that is 1GB. To fix this issue:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:174(para)
+msgid "Change content of the <filename>/etc/tgt/targets.conf</filename> from <literal>include /etc/tgt/conf.d/*.conf</literal> to <literal>include /etc/tgt/conf.d/cinder_tgt.conf</literal>, as follows:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml:183(para)
+msgid "Restart <systemitem class=\"service\">tgt</systemitem> and <systemitem class=\"service\">cinder-*</systemitem> services so they pick up the new configuration."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_multipath_warn.xml:6(title)
+msgid "Multipath Call Failed Exit"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_multipath_warn.xml:9(para)
+msgid "Multipath call failed exit. This warning occurs in the Compute log if you do not have the optional <filename>multipath-tools</filename> package installed on the compute node. This is an optional package and the volume attachment does work without the multipath tools installed. If the <filename>multipath-tools</filename> package is installed on the compute node, it is used to perform the volume attachment. The IDs in your message are unique to your system."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_multipath_warn.xml:21(para)
+msgid "Run the following command on the compute node to install the <filename>multipath-tools</filename> packages."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_failed_attach_vol_after_detach.xml:9(para)
+msgid "Failed to attach a volume after detaching the same volume."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_failed_attach_vol_after_detach.xml:15(para)
+msgid "You must change the device name on the <placeholder-1/> command. The VM might not clean up after a <placeholder-2/> command runs. This example shows how the <placeholder-3/> command fails when you use the <code>vdb</code>, <code>vdc</code>, or <code>vdd</code> device names:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/blockstorage/section_ts_failed_attach_vol_after_detach.xml:34(para)
+msgid "You might also have this problem after attaching and detaching the same volume from the same VM with the same mount point multiple times. In this case, restart the KVM host."
+msgstr ""
+
 #: ./doc/admin-guide-cloud/blockstorage/section_ts_duplicate_3par_host.xml:4(title)
 msgid "Duplicate 3PAR host"
 msgstr ""
@@ -9201,6 +7169,2110 @@ msgstr ""
 msgid "Change the 3PAR host name to match the one that OpenStack expects. The 3PAR host constructed by the driver uses just the local hostname, not the fully qualified domain name (FQDN) of the compute host. For example, if the FQDN was <emphasis>myhost.example.com</emphasis>, just <emphasis>myhost</emphasis> would be used as the 3PAR hostname. IP addresses are not allowed as host names on the 3PAR storage server."
 msgstr ""
 
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:9(title)
+msgid "Configure Compute service groups"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:10(para)
+msgid "To effectively manage and utilize compute nodes, the Compute service must know their statuses. For example, when a user launches a new VM, the Compute scheduler sends the request to a live node; the Compute service queries the ServiceGroup API to get information about whether a node is alive."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:14(para)
+msgid "When a compute worker (running the <systemitem class=\"service\">nova-compute</systemitem> daemon) starts, it calls the <systemitem>join</systemitem> API to join the compute group. Any interested service (for example, the scheduler) can query the group's membership and the status of its nodes. Internally, the <systemitem>ServiceGroup</systemitem> client driver automatically updates the compute worker status."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:19(para)
+msgid "The database, ZooKeeper, and Memcache drivers are available."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:21(title)
+msgid "Database ServiceGroup driver"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:22(para)
+msgid "By default, Compute uses the database driver to track node liveness. In a compute worker, this driver periodically sends a <placeholder-1/> command to the database, saying <quote>I'm OK</quote> with a timestamp. Compute uses a pre-defined timeout (<literal>service_down_time</literal>) to determine whether a node is dead."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:26(para)
+msgid "The driver has limitations, which can be an issue depending on your setup. The more compute worker nodes that you have, the more pressure you put on the database. By default, the timeout is 60 seconds so it might take some time to detect node failures. You could reduce the timeout value, but you must also make the database update more frequently, which again increases the database workload."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:31(para)
+msgid "The database contains data that is both transient (whether the node is alive) and persistent (for example, entries for VM owners). With the ServiceGroup abstraction, Compute can treat each type separately."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:36(title)
+msgid "ZooKeeper ServiceGroup driver"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:37(para)
+msgid "The ZooKeeper ServiceGroup driver works by using ZooKeeper ephemeral nodes. ZooKeeper, in contrast to databases, is a distributed system. Its load is divided among several servers. At a compute worker node, after establishing a ZooKeeper session, the driver creates an ephemeral znode in the group directory. Ephemeral znodes have the same lifespan as the session. If the worker node or the <systemitem class=\"service\">nova-compute</systemitem> daemon crashes, or a network partition is in place between the worker and the ZooKeeper server quorums, the ephemeral znodes are removed automatically. The driver gets the group membership by running the <placeholder-1/> command in the group directory."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:47(para)
+msgid "To use the ZooKeeper driver, you must install ZooKeeper servers and client libraries. Setting up ZooKeeper servers is outside the scope of this guide (for more information, see <link href=\"http://zookeeper.apache.org/\">Apache Zookeeper</link>)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:51(para)
+msgid "To use ZooKeeper, you must install client-side Python libraries on every nova node: <literal>python-zookeeper</literal> the official Zookeeper Python binding and evzookeeper the library to make the binding work with the eventlet threading model."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:55(para)
+msgid "The following example assumes the ZooKeeper server addresses and ports are <literal>192.168.2.1:2181</literal>, <literal>192.168.2.2:2181</literal>, and <literal>192.168.2.3:2181</literal>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:58(para)
+msgid "The following values in the <filename>/etc/nova/nova.conf</filename> file (on every node) are required for the <systemitem>ZooKeeper</systemitem> driver:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:65(para)
+msgid "To customize the Compute Service groups, use the following configuration option settings:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:70(title)
+msgid "Memcache ServiceGroup driver"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:71(para)
+msgid "The <systemitem>memcache</systemitem> ServiceGroup driver uses memcached, which is a distributed memory object caching system that is often used to increase site performance. For more details, see <link href=\"http://memcached.org/\">memcached.org</link>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:75(para)
+msgid "To use the <systemitem>memcache</systemitem> driver, you must install <systemitem>memcached</systemitem>. However, because <systemitem>memcached</systemitem> is often used for both OpenStack Object Storage and OpenStack dashboard, it might already be installed. If <systemitem>memcached</systemitem> is not installed, refer to the <link href=\"http://docs.openstack.org/icehouse\"><citetitle>OpenStack Installation Guide</citetitle></link> for more information."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-service-groups.xml:83(para)
+msgid "The following values in the <filename>/etc/nova/nova.conf</filename> file (on every node) are required for the <systemitem>memcache</systemitem> driver:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:7(title)
+msgid "Instance building blocks"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:8(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 shutdown."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:11(para)
+msgid "You can also put an operating system on a persistent volume in Compute or the Block Storage volume system. This gives a more traditional, persistent system that accumulates states, which are preserved across restarts. To get a list of available images on your system, run: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:29(para)
+msgid "Automatically generated UUID of the image."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:35(para)
+msgid "Free form, human-readable name for image."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:56(para)
+msgid "Virtual hardware templates are called <literal>flavors</literal>. The default installation provides five flavors. By default, these are configurable by administrative users. However, you can change this behavior 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/compute/section_compute-instance-building-blocks.xml:62(para)
+msgid "For a list of flavors that are available on your system, run:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-security.xml:6(title)
+msgid "Security hardening"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-security.xml:7(para)
+msgid "OpenStack Compute can be integrated with various third-party technologies to increase security. For more information, see the <link href=\"http://docs.openstack.org/sec/\"><citetitle>OpenStack Security Guide</citetitle></link>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-security.xml:13(title)
+msgid "Encrypt Compute metadata traffic"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-security.xml:18(para)
+msgid "Enable the HTTPS protocol: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-security.xml:23(para)
+msgid "Determine whether insecure SSL connections are accepted for Compute metadata server requests. The default value is <option>False</option>: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-security.xml:31(replaceable)
+msgid "PATH_TO_CERT"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-security.xml:29(para)
+msgid "Specify the path to the client certificate: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-security.xml:36(replaceable)
+msgid "PATH_TO_KEY"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-security.xml:34(para)
+msgid "Specify the path to the private key: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-security.xml:14(para)
+msgid "OpenStack Juno supports encrypting Compute metadata traffic with HTTPS. Enable SSL encryption in the <filename>metadata_agent.ini</filename> file:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:6(title)
+msgid "Configure Compute to use IPv6 addresses"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:7(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."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:15(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."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:22(title)
+msgid "Switch into IPv4/IPv6 dual-stack mode"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:23(para)
+msgid "On all nodes 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:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:31(para)
+msgid "Edit the <filename>nova.conf</filename> file on all nodes to specify <literal>use_ipv6 = True</literal>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:33(para)
+msgid "Restart all <literal>nova-*</literal> services."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:35(para)
+msgid "You can add a fixed range for IPv6 addresses to the <placeholder-1/> command. Specify <option>public</option> or <option>private</option> after the <option>network-create</option> parameter."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:38(replaceable)
+msgid "fixed_range_v4"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:38(replaceable)
+msgid "vlan_id"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:38(replaceable)
+msgid "vpn_start"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:38(replaceable)
+msgid "fixed_range_v6"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:39(para)
+msgid "You can set IPv6 global routing prefix by using the <option>--fixed_range_v6</option> parameter. The default value for the parameter is: <literal>fd00::/48</literal>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:44(para)
+msgid "When you use <literal>FlatDHCPManager</literal>, the command uses the original <option>--fixed_range_v6</option> value. For example:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-ipv6.xml:49(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 ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:604(None)
+msgid "@@image: '../../common/figures/SCH_5007_V00_NUAC-multi_nic_OpenStack-Flat-manager.jpg'; md5=31f7e15a45d042bd9d6499631e2f3ccc"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:614(None)
+msgid "@@image: '../../common/figures/SCH_5007_V00_NUAC-multi_nic_OpenStack-Flat-DHCP-manager.jpg'; md5=0f33a228f1dec4a4e4424dd5ee81bde8"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:624(None)
+msgid "@@image: '../../common/figures/SCH_5007_V00_NUAC-multi_nic_OpenStack-VLAN-manager.jpg'; md5=0acaf3e2041f941d8fee2d111f37e7ac"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:7(title)
+msgid "Networking with nova-network"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:8(para)
+msgid "Understanding the networking configuration options helps you design the best configuration for your Compute instances."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:11(para)
+msgid "You can choose to either install and configure <systemitem class=\"service\">nova-network</systemitem> for networking between VMs or use the OpenStack Networking service (neutron) for networking. To configure Compute networking options with OpenStack Networking, see the <xref linkend=\"ch_networking\"/>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:16(title)
+msgid "Networking concepts"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:17(para)
+msgid "This section offers a brief overview of networking concepts for Compute."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:18(para)
+msgid "Compute assigns a private IP address to each VM instance. (Currently, Compute with <systemitem class=\"service\">nova-network</systemitem> only supports Linux bridge networking that enables the virtual interfaces to connect to the outside network through the physical interface.) Compute makes a distinction between <emphasis role=\"italic\">fixed IPs</emphasis> and <emphasis role=\"italic\">floating IPs</emphasis>. Fixed IPs are IP addresses that are assigned to an instance on creation and stay the same until the instance is explicitly terminated. By contrast, floating IPs are addresses that can be dynamically associated with an instance. A floating IP address can be disassociated and associated with another instance at any time. A user can reserve a floating IP for their project."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:28(para)
+msgid "The network controller with <systemitem class=\"service\">nova-network</systemitem> provides virtual networks to enable compute servers to interact with each other and with the public network. Compute with <systemitem class=\"service\">nova-network</systemitem> supports the following network modes, which are implemented as “Network Manager” types."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:34(term)
+msgid "Flat Network Manager"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:35(para)
+msgid "In <emphasis role=\"bold\">Flat</emphasis> mode, a network administrator specifies a subnet. IP addresses for VM instances are assigned from the subnet, and then injected into the image on launch. Each instance receives a fixed IP address from the pool of available addresses. A system administrator must create the Linux networking bridge (typically named <literal>br100</literal>, although this is configurable) on the systems running the <systemitem class=\"service\">nova-network</systemitem> service. All instances of the system are attached to the same bridge, and this is configured manually by the network administrator."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:45(para)
+msgid "Configuration injection currently only works on Linux-style systems that keep networking configuration in <filename>/etc/network/interfaces</filename>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:50(term)
+msgid "Flat DHCP Network Manager"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:51(para)
+msgid "In <emphasis role=\"bold\">FlatDHCP</emphasis> mode, OpenStack starts a DHCP server (<systemitem>dnsmasq</systemitem>) to allocate IP addresses to VM instances from the specified subnet, in addition to manually configuring the networking bridge. IP addresses for VM instances are assigned from a subnet specified by the network administrator."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:56(para)
+msgid "Like Flat Mode, all instances are attached to a single bridge on the compute node. Additionally, a DHCP server is running to configure instances (depending on single-/multi-host mode, alongside each <systemitem class=\"service\">nova-network</systemitem>). In this mode, Compute does a bit more configuration in that it attempts to bridge into an ethernet device (<literal>flat_interface</literal>, eth0 by default). For every instance, Compute allocates a fixed IP address and configures dnsmasq with the MAC/IP pair for the VM. Dnsmasq does not take part in the IP address allocation process, it only hands out IPs according to the mapping done by Compute. Instances receive their fixed IPs by doing a <placeholder-1/>. These IPs are <emphasis role=\"italic\">not</emphasis> assigned to any of the host's network interfaces, only to the VM's guest-side interface."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:69(para)
+msgid "In any setup with flat networking, the hosts providing the <systemitem class=\"service\">nova-network</systemitem> service are responsible for forwarding traffic from the private network. They also run and configure <systemitem>dnsmasq</systemitem> as a DHCP server listening on this bridge, usually on IP address 10.0.0.1 (see <link linkend=\"section_dnsmasq\">DHCP server: dnsmasq </link>). Compute can determine the NAT entries for each network, although sometimes NAT is not used, such as when configured with all public IPs or a hardware router is used (one of the HA options). Such hosts need to have <literal>br100</literal> configured and physically connected to any other nodes that are hosting VMs. You must set the <literal>flat_network_bridge</literal> option or create networks with the bridge parameter in order to avoid raising an error. Compute nodes have iptables/ebtables entries created for each project and instance to protect against IP/MAC address spoofing and ARP poisoning."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:84(para)
+msgid "In single-host Flat DHCP mode you <emphasis role=\"italic\">will</emphasis> be able to ping VMs through their fixed IP from the <systemitem>nova-network</systemitem> node, but you <emphasis role=\"italic\">cannot</emphasis> ping them from the compute nodes. This is expected behavior."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:91(term)
+msgid "VLAN Network Manager"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:92(para)
+msgid "<emphasis role=\"bold\">VLANManager</emphasis> mode is the default mode for OpenStack Compute. In this mode, Compute creates a VLAN and bridge for each tenant. For multiple-machine installation, the VLAN Network Mode requires a switch that supports VLAN tagging (IEEE 802.1Q). The tenant gets a range of private IPs that are only accessible from inside the VLAN. In order for a user to access the instances in their tenant, a special VPN instance (code named cloudpipe) needs to be created. Compute generates a certificate and key for the user to access the VPN and starts the VPN automatically. It provides a private network segment for each tenant's instances that can be accessed through a dedicated VPN connection from the Internet. In this mode, each tenant gets its own VLAN, Linux networking bridge, and subnet."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:103(para)
+msgid "The subnets are specified by the network administrator, and are assigned dynamically to a tenant when required. A DHCP Server is started for each VLAN to pass out IP addresses to VM instances from the subnet assigned to the tenant. All instances belonging to one tenant are bridged into the same VLAN for that tenant. OpenStack Compute creates the Linux networking bridges and VLANs when required."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:111(para)
+msgid "These network managers can co-exist in a cloud system. However, because you cannot select the type of network for a given tenant, you cannot configure multiple network types in a single Compute installation."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:114(para)
+msgid "All network managers configure the network using <emphasis role=\"italic\">network drivers</emphasis>. For example, the Linux L3 driver (<literal>l3.py</literal> and <literal>linux_net.py</literal>), which makes use of <literal>iptables</literal>, <literal>route</literal> and other network management facilities, and libvirt's <link href=\"http://libvirt.org/formatnwfilter.html\">network filtering facilities</link>. The driver is not tied to any particular network manager; all network managers use the same driver. The driver usually initializes (creates bridges and so on) only when the first VM lands on this host node."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:122(para)
+msgid "All network managers operate in either <emphasis role=\"italic\">single-host</emphasis> or <emphasis role=\"italic\">multi-host</emphasis> mode. This choice greatly influences the network configuration. In single-host mode, a single <systemitem class=\"service\">nova-network</systemitem> service provides a default gateway for VMs and hosts a single DHCP server (<systemitem>dnsmasq</systemitem>). In multi-host mode, each compute node runs its own <systemitem class=\"service\">nova-network</systemitem> service. In both cases, all traffic between VMs and the outer world flows through <systemitem class=\"service\">nova-network</systemitem>. Each mode has its pros and cons (see the <citetitle>Network Topology</citetitle> section in the <link href=\"http://docs.openstack.org/trunk/openstack-ops/content/\"><citetitle>OpenStack Operations Guide</citetitle></link>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:134(para)
+msgid "All networking options require network connectivity to be already set up between OpenStack physical nodes. OpenStack does not configure any physical network interfaces. All network managers automatically create VM virtual interfaces. Some, but not all, managers create network bridges such as <literal>br100</literal>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:139(para)
+msgid "All machines must have a <emphasis role=\"italic\">public</emphasis> and <emphasis role=\"italic\">internal</emphasis> network interface (controlled by the options: <literal>public_interface</literal> for the public interface, and <literal>flat_interface</literal> and <literal>vlan_interface</literal> for the internal interface with flat / VLAN managers). This guide refers to the public network as the external network and the private network as the internal or tenant network."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:151(para)
+msgid "The internal network interface is used for communication with VMs; the interface should not have an IP address attached to it before OpenStack installation (it serves merely as a fabric where the actual endpoints are VMs and dnsmasq). Also, you must put the internal network interface in <emphasis role=\"italic\">promiscuous mode</emphasis>, because it must receive packets whose target MAC address is of the guest VM, not of the host."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:157(para)
+msgid "Throughout this documentation, the public network is sometimes referred to as the external network, while the internal network is also sometimes referred to as the private network or tenant network."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:163(para)
+msgid "For flat and flat DHCP modes, use the following command to create a network:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:168(para)
+msgid "<option>--fixed-range-v4-</option> specifies the network subnet."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:171(para)
+msgid "<option>--fixed-cidr</option> specifies a range of fixed IP addresses to allocate, and can be a subset of the <option>--fixed-range-v4</option> argument."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:176(para)
+msgid "<option>--bridge</option> specifies the bridge device to which this network is connected on every compute node."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:166(para)
+msgid "Where:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:182(title)
+msgid "DHCP server: dnsmasq"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:183(para)
+msgid "The Compute service uses <link href=\"http://www.thekelleys.org.uk/dnsmasq/doc.html\">dnsmasq</link> as the DHCP server when running with either that Flat DHCP Network Manager or the VLAN Network Manager. The <systemitem class=\"service\">nova-network</systemitem> service is responsible for starting up <systemitem>dnsmasq</systemitem> processes."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:188(para)
+msgid "The behavior of <systemitem>dnsmasq</systemitem> can be customized by creating a <systemitem>dnsmasq</systemitem> configuration file. Specify the configuration file using the <literal>dnsmasq_config_file</literal> configuration option. For example:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:193(para)
+msgid "For an example of how to change the behavior of <systemitem>dnsmasq</systemitem> using a <systemitem>dnsmasq</systemitem> configuration file, see the <link href=\"http://docs.openstack.org/trunk/config-reference/content/\"><citetitle>OpenStack Configuration Reference</citetitle></link>. The <systemitem>dnsmasq</systemitem> documentation also has a more comprehensive <link href=\"http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq.conf.example\">dnsmasq configuration file example</link>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:200(para)
+msgid "<systemitem>dnsmasq</systemitem> also acts as a caching DNS server for instances. You can explicitly specify the DNS server that <systemitem>dnsmasq</systemitem> should use by setting the <literal>dns_server</literal> configuration option in <filename>/etc/nova/nova.conf</filename>. The following example would configure <systemitem>dnsmasq</systemitem> to use Google's public DNS server:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:206(para)
+msgid "Logging output for <systemitem>dnsmasq</systemitem> goes to the <systemitem>syslog</systemitem> (typically <filename>/var/log/syslog</filename> or <filename>/var/log/messages</filename>, depending on Linux distribution). <systemitem>dnsmasq</systemitem> logging output can be useful for troubleshooting if VM instances boot successfully but are not reachable over the network."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:211(para)
+msgid "A network administrator can run <code>nova-manage fixed reserve --address=<replaceable>x.x.x.x</replaceable></code> to specify the starting point IP address (x.x.x.x) to reserve with the DHCP server. This reservation only affects which IP address the VMs start at, not the fixed IP addresses that the <systemitem class=\"service\">nova-network</systemitem> service places on the bridges."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:223(title)
+msgid "Metadata service"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:225(title)
+msgid "Introduction"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:226(para)
+msgid "The Compute service uses a special metadata service to enable virtual machine instances to retrieve instance-specific data. Instances access the metadata service at <literal>http://169.254.169.254</literal>. The metadata service supports two sets of APIs: an OpenStack metadata API and an EC2-compatible API. Each of the APIs is versioned by date."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:234(para)
+msgid "To retrieve a list of supported versions for the OpenStack metadata API, make a GET request to <literal>http://169.254.169.254/openstack</literal> For example:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:241(para)
+msgid "To list supported versions for the EC2-compatible metadata API, make a GET request to <literal>http://169.254.169.254</literal>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:256(para)
+msgid "If you write a consumer for one of these APIs, always attempt to access the most recent API version supported by your consumer first, then fall back to an earlier version if the most recent one is not available."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:263(title)
+msgid "OpenStack metadata API"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:264(para)
+msgid "Metadata from the OpenStack API is distributed in JSON format. To retrieve the metadata, make a GET request to <literal>http://169.254.169.254/openstack/2012-08-10/meta_data.json</literal>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:271(para)
+msgid "Instances also retrieve user data (passed as the <literal>user_data</literal> parameter in the API call or by the <literal>--user_data</literal> flag in the <placeholder-1/> command) through the metadata service, by making a GET request to <literal>http://169.254.169.254/openstack/2012-08-10/user_data</literal>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:284(title)
+msgid "EC2 metadata API"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:285(para)
+msgid "The metadata service has an API that is compatible with version 2009-04-04 of the <link href=\"http://docs.amazonwebservices.com/AWSEC2/2009-04-04/UserGuide/AESDG-chapter-instancedata.html\">Amazon EC2 metadata service</link>; virtual machine images that are designed for EC2 work properly with OpenStack."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:291(para)
+msgid "The EC2 API exposes a separate URL for each metadata. You can retrieve a listing of these elements by making a GET query to <literal>http://169.254.169.254/2009-04-04/meta-data/</literal>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:321(para)
+msgid "Instances can retrieve the public SSH key (identified by keypair name when a user requests a new instance) by making a GET request to <literal>http://169.254.169.254/2009-04-04/meta-data/public-keys/0/openssh-key</literal>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:328(para)
+msgid "Instances can retrieve user data by making a GET request to <literal>http://169.254.169.254/2009-04-04/user-data</literal>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:337(title)
+msgid "Run the metadata service"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:338(para)
+msgid "The metadata service is implemented by either the <systemitem class=\"service\">nova-api</systemitem> service or the <systemitem class=\"service\">nova-api-metadata</systemitem> service. (The <systemitem class=\"service\">nova-api-metadata</systemitem> service is generally only used when running in multi-host mode, it retrieves instance-specific metadata). If you are running the <systemitem class=\"service\">nova-api</systemitem> service, you must have <literal>metadata</literal> as one of the elements of the list of the <literal>enabled_apis</literal> configuration option in <filename>/etc/nova/nova.conf</filename>. The default <literal>enabled_apis</literal> configuration setting includes the metadata service, so you should not need to modify it."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:349(para)
+msgid "Hosts access the service at <literal>169.254.169.254:80</literal>, and this is translated to <literal>metadata_host:metadata_port</literal> by an iptables rule established by the <systemitem class=\"service\">nova-network</systemitem> service. In multi-host mode, you can set <option>metadata_host</option> to <literal>127.0.0.1</literal>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:354(para)
+msgid "To enable instances to reach the metadata service, the <systemitem class=\"service\">nova-network</systemitem> service configures iptables to NAT port <literal>80</literal> of the <literal>169.254.169.254</literal> address to the IP address specified in <option>metadata_host</option> (default <literal>$my_ip</literal>, which is the IP address of the <systemitem class=\"service\">nova-network</systemitem> service) and port specified in <option>metadata_port</option> (default <literal>8775</literal>) in <filename>/etc/nova/nova.conf</filename>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:368(para)
+msgid "The <literal>metadata_host</literal> configuration option must be an IP address, not a host name."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:373(para)
+msgid "The default Compute service settings assume that the <systemitem class=\"service\">nova-network</systemitem> service and the <systemitem class=\"service\">nova-api</systemitem> service are running on the same host. If this is not the case, you must make this change in the <filename>/etc/nova/nova.conf</filename> file on the host running the <systemitem class=\"service\">nova-network</systemitem> service:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:384(para)
+msgid "Set the <literal>metadata_host</literal> configuration option to the IP address of the host where the <systemitem class=\"service\">nova-api</systemitem> service runs."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:395(title)
+msgid "Enable ping and SSH on VMs"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:396(para)
+msgid "Be sure you enable access to your VMs by using the <placeholder-1/> or <placeholder-2/> command. These commands enable you to <placeholder-3/> and <placeholder-4/> to your VMs:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:402(para)
+msgid "You must run these commands as root only if the credentials used to interact with <systemitem class=\"service\">nova-api</systemitem> are in <filename>/root/.bashrc</filename>. If the EC2 credentials are the <filename>.bashrc</filename> file for another user, you must run these commands as the user."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:410(para)
+msgid "Run <placeholder-1/> commands:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:413(para)
+msgid "Using euca2ools:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:416(para)
+msgid "If you still cannot ping or SSH your instances after issuing the <placeholder-1/> commands, look at the number of <literal>dnsmasq</literal> processes that are running. If you have a running instance, check to see that TWO <literal>dnsmasq</literal> processes are running. If not, perform the following commands as root:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:425(title)
+msgid "Configure public (floating) IP addresses"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:427(para)
+msgid "If you are using Compute's <systemitem class=\"service\">nova-network</systemitem> instead of OpenStack Networking (neutron) for networking in OpenStack, use procedures in this section to configure floating IP addresses. For instructions on how to configure OpenStack Networking (neutron) to provide access to instances through floating IP addresses, see <xref linkend=\"section_l3_router_and_nat\"/>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:433(title)
+msgid "Private and public IP addresses"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:434(para)
+msgid "Every virtual instance is automatically assigned a private IP address. You can optionally assign public IP addresses to instances. The term <glossterm baseform=\"floating IP address\">floating IP</glossterm> refers to an IP address, typically public, that you can dynamically add to a running virtual instance. OpenStack Compute uses Network Address Translation (NAT) to assign floating IPs to virtual instances."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:444(para)
+msgid "If you plan to use this feature, you must add edit the <filename>/etc/nova/nova.conf</filename> file to specify to which interface the <systemitem class=\"service\">nova-network</systemitem> service binds public IP addresses, as follows:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:450(replaceable)
+msgid "vlan100"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:451(para)
+msgid "If you make changes to the <filename>/etc/nova/nova.conf</filename> file while the <systemitem class=\"service\">nova-network</systemitem> service is running, you must restart the service."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:457(title)
+msgid "Traffic between VMs using floating IPs"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:459(para)
+msgid "Because floating IPs are implemented by using a source NAT (SNAT rule in iptables), security groups can display inconsistent behavior if VMs use their floating IP to communicate with other VMs, particularly on the same physical host. Traffic from VM to VM across the fixed network does not have this issue, and so this is the recommended path. To ensure that traffic does not get SNATed to the floating range, explicitly set: <placeholder-1/>The <literal>x.x.x.x/y</literal> value specifies the range of floating IPs for each pool of floating IPs that you define. If the VMs in the source group have floating IPs, this configuration is also required."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:472(title)
+msgid "Enable IP forwarding"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:473(para)
+msgid "By default, IP forwarding is disabled on most Linux distributions. To use the floating IP feature, you must enable IP forwarding."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:477(para)
+msgid "You must enable IP forwarding only on the nodes that run the <systemitem class=\"service\">nova-network</systemitem> service. If you use <literal>multi_host</literal> mode, ensure that you enable it on all compute nodes. Otherwise, enable it on only the node that runs the <systemitem class=\"service\">nova-network</systemitem> service."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:483(para)
+msgid "To check whether forwarding is enabled, run:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:486(para)
+msgid "Alternatively, you can run:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:489(para)
+msgid "In the previous example, IP forwarding is <emphasis role=\"bold\">disabled</emphasis>. To enable it dynamically, run:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:492(para)
+msgid "Or:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:494(para)
+msgid "To make the changes permanent, edit the <filename>/etc/sysctl.conf</filename> file and update the IP forwarding setting:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:498(para)
+msgid "Save the file and run the following command to apply the changes:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:500(para)
+msgid "You can also update the setting by restarting the network service:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:503(para)
+msgid "On Ubuntu, run:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:507(para)
+msgid "On RHEL/Fedora/CentOS, run:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:513(title)
+msgid "Create a list of available floating IP addresses"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:515(para)
+msgid "Compute maintains a list of floating IP addresses that you can assign to instances. Use the <placeholder-1/> command to add entries to this list."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:520(para)
+msgid "You can use the following <placeholder-1/> commands to perform floating IP operations:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:526(para)
+msgid "Lists the floating IP addresses in the pool."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:530(replaceable)
+msgid "[pool name]"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:530(replaceable) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:535(replaceable)
+msgid "[CIDR]"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:531(para)
+msgid "Creates specific floating IPs for either a single address or a subnet."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:536(para)
+msgid "Removes floating IP addresses using the same parameters as the create command."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:541(para)
+msgid "For information about how administrators can associate floating IPs with instances, see <link href=\"http://docs.openstack.org/user-guide-admin/content/manage_ip_addresses.html\">Manage IP addresses</link> in the <citetitle>OpenStack Admin User Guide</citetitle>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:549(title)
+msgid "Automatically add floating IPs"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:550(para)
+msgid "You can configure the <systemitem class=\"service\">nova-network</systemitem> service to automatically allocate and assign a floating IP address to virtual instances when they are launched. Add the following line to the <filename>/etc/nova/nova.conf</filename> file and restart the <systemitem class=\"service\">nova-network</systemitem> service:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:560(para)
+msgid "If you enable this option and all floating IP addresses have already been allocated, the <placeholder-1/> command fails."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:568(title)
+msgid "Remove a network from a project"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:569(para)
+msgid "You cannot remove a network that has already been associated to a project by simply deleting it."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:571(para)
+msgid "To determine the project ID, you must have administrative rights. You can disassociate the project from the network with a scrub command and the project ID as the final parameter:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:574(replaceable)
+msgid "&lt;id&gt;"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:577(title)
+msgid "Multiple interfaces for your instances (multinic)"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:580(para)
+msgid "The multinic feature allows you to plug more than one interface to your instances, making it possible to make several use cases available:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:584(para)
+msgid "SSL Configurations (VIPs)"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:587(para)
+msgid "Services failover/ HA"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:590(para)
+msgid "Bandwidth Allocation"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:593(para)
+msgid "Administrative/ Public access to your instances"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:599(title)
+msgid "multinic flat manager"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:609(title)
+msgid "multinic flatdhcp manager"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:619(title)
+msgid "multinic VLAN manager"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:597(para)
+msgid "Each VIF is representative of a separate network with its own IP block. Every network mode introduces its own set of changes regarding the multinic usage: <placeholder-1/><placeholder-2/><placeholder-3/>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:630(title)
+msgid "Use the multinic feature"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:631(para)
+msgid "In order to use the multinic feature, first create two networks, and attach them to your tenant (still named 'project' on the command line): <placeholder-1/> Now every time you spawn a new instance, it gets two IP addresses from the respective DHCP servers:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:644(para)
+msgid "Make sure to power up the second interface on the instance, otherwise that last won't be reachable through its second IP. Here is an example of how to setup the interfaces within the instance (this is the configuration that needs to be applied inside the image):"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:650(filename)
+msgid "/etc/network/interfaces"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:662(para)
+msgid "If the Virtual Network Service Neutron is installed, it is possible to specify the networks to attach to the respective interfaces by using the <literal>--nic</literal> flag when invoking the <literal>nova</literal> command: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:674(title)
+msgid "Troubleshoot Networking"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:676(title)
+msgid "Cannot reach floating IPs"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:677(para)
+msgid "If you cannot reach your instances through the floating IP address, check the following:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:679(para)
+msgid "Ensure the default security group allows ICMP (ping) and SSH (port 22), so that you can reach the instances:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:689(para)
+msgid "Ensure the NAT rules have been added to <systemitem>iptables</systemitem> on the node that <systemitem>nova-network</systemitem> is running on, as root:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:694(para)
+msgid "Check that the public address, in this example \"68.99.26.170\", has been added to your public interface. You should see the address in the listing when you enter \"ip addr\" at the command prompt."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:704(para)
+msgid "Note that you cannot SSH to an instance with a public IP from within the same server as the routing configuration won't allow it."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:707(para)
+msgid "You can use <placeholder-1/> to identify if packets are being routed to the inbound interface on the compute host. If the packets are reaching the compute hosts but the connection is failing, the issue may be that the packet is being dropped by reverse path filtering. Try disabling reverse-path filtering on the inbound interface. For example, if the inbound interface is <literal>eth2</literal>, as root, run:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:713(replaceable)
+msgid "eth2"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:714(para)
+msgid "If this solves your issue, add the following line to <filename>/etc/sysctl.conf</filename> so that the reverse-path filter is disabled the next time the compute host reboots: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:721(title)
+msgid "Disable firewall"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:722(para)
+msgid "To help debug networking issues with reaching VMs, you can disable the firewall by setting the following option in <filename>/etc/nova/nova.conf</filename>:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:727(para)
+msgid "We strongly recommend you remove this line to re-enable the firewall once your networking issues have been resolved."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:732(title)
+msgid "Packet loss from instances to nova-network server (VLANManager mode)"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:734(para)
+msgid "If you can SSH to your instances but you find that the network interactions to your instance is slow, or if you find that running certain operations are slower than they should be (for example, <placeholder-1/>), then there may be packet loss occurring on the connection to the instance."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:741(para)
+msgid "Packet loss can be caused by Linux networking configuration settings related to bridges. Certain settings can cause packets to be dropped between the VLAN interface (for example, <literal>vlan100</literal>) and the associated bridge interface (for example, <literal>br100</literal>) on the host running the <systemitem class=\"service\">nova-network</systemitem> service."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:750(para)
+msgid "One way to check whether this is the issue in your setup, is to open up three terminals and run the following commands:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:755(para)
+msgid "In the first terminal, on the host running nova-network, use <placeholder-1/> on the VLAN interface to monitor DNS-related traffic (UDP, port 53). As root, run:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:760(para)
+msgid "In the second terminal, also on the host running nova-network, use <placeholder-1/> to monitor DNS-related traffic on the bridge interface. As root, run:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:764(para)
+msgid "In the third terminal, SSH inside of the instance and generate DNS requests by using the <placeholder-1/> command:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:768(para)
+msgid "The symptoms may be intermittent, so try running <placeholder-1/> multiple times. If the network configuration is correct, the command should return immediately each time. If it is not functioning properly, the command hangs for several seconds."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:774(para)
+msgid "If the <placeholder-1/> command sometimes hangs, and there are packets that appear in the first terminal but not the second, then the problem may be due to filtering done on the bridges. Try to disable filtering, run the following commands as root:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:781(para)
+msgid "If this solves your issue, add the following line to <filename>/etc/sysctl.conf</filename> so that these changes take effect the next time the host reboots:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:791(title)
+msgid "KVM: Network connectivity works initially, then fails"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:793(para)
+msgid "Some administrators have observed an issue with the KVM hypervisor where instances running Ubuntu 12.04 sometimes loses network connectivity after functioning properly for a period of time. Some users have reported success with loading the vhost_net kernel module as a workaround for this issue (see <link href=\"https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/997978/\">bug #997978</link>) . This kernel module may also <link href=\"http://www.linux-kvm.org/page/VhostNet\">improve network performance on KVM</link>. To load the kernel module, as root:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:808(para)
+msgid "Loading the module has no effect on running instances."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-instance-mgt-tools.xml:7(title)
+msgid "Instance management tools"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-instance-mgt-tools.xml:8(para)
+msgid "OpenStack provides command-line, web-based, and API-based instance management tools. Additionally, a number of third-party management tools are available, using either the native API or the provided EC2-compatible API."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-instance-mgt-tools.xml:13(para)
+msgid "The OpenStack <application>python-novaclient</application> package provides a basic command-line utility, which uses the <placeholder-1/> command. This is available as a native package for most Linux distributions, or you can install the latest version using the <application>pip</application> python package installer:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-instance-mgt-tools.xml:22(para)
+msgid "For more information about <application>python-novaclient</application> and other available command-line tools, see the <link href=\"http://docs.openstack.org/user-guide/content/index.html\"><citetitle>OpenStack End User Guide</citetitle></link>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:7(title)
+msgid "System administration"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:8(para)
+msgid "By understanding how the different installed nodes interact with each other, you can administer the Compute installation. Compute offers many ways to install using multiple servers but the general idea is that you can have multiple compute nodes that control the virtual servers and a cloud controller node that contains the remaining Compute services."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:15(para)
+msgid "The Compute cloud works through the interaction of a series of daemon processes named <systemitem>nova-*</systemitem> that reside persistently on the host machine or machines. These binaries can all run on the same machine or be spread out on multiple boxes in a large deployment. The responsibilities of services and drivers are:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:22(para)
+msgid "Services:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:25(para)
+msgid "<systemitem class=\"service\">nova-api</systemitem>. Receives xml requests and sends them to the rest of the system. It is a wsgi app that routes and authenticate requests. It supports the EC2 and OpenStack APIs. There is a <filename>nova-api.conf</filename> file created when you install Compute."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:32(para)
+msgid "<systemitem>nova-cert</systemitem>. Provides the certificate manager."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:36(para)
+msgid "<systemitem class=\"service\">nova-compute</systemitem>. Responsible for managing virtual machines. It loads a Service object, which exposes the public methods on ComputeManager through Remote Procedure Call (RPC)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:42(para)
+msgid "<systemitem>nova-conductor</systemitem>. Provides database-access support for Compute nodes (thereby reducing security risks)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:46(para)
+msgid "<systemitem>nova-consoleauth</systemitem>. Handles console authentication."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:50(para)
+msgid "<systemitem class=\"service\">nova-objectstore</systemitem>: The <systemitem class=\"service\">nova-objectstore</systemitem> service is an ultra simple file-based storage system for images that replicates most of the S3 API. It can be replaced with OpenStack Image Service and a simple image manager or use OpenStack Object Storage as the virtual machine image storage facility. It must reside on the same node as <systemitem class=\"service\">nova-compute</systemitem>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:59(para)
+msgid "<systemitem class=\"service\">nova-network</systemitem>. Responsible for managing floating and fixed IPs, DHCP, bridging and VLANs. It loads a Service object which exposes the public methods on one of the subclasses of NetworkManager. Different networking strategies are available to the service by changing the network_manager configuration option to FlatManager, FlatDHCPManager, or VlanManager (default is VLAN if no other is specified)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:68(para)
+msgid "<systemitem>nova-scheduler</systemitem>. Dispatches requests for new virtual machines to the correct node."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:72(para)
+msgid "<systemitem>nova-novncproxy</systemitem>. Provides a VNC proxy for browsers (enabling VNC consoles to access virtual machines)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:78(para)
+msgid "Some services have drivers that change how the service implements the core of its functionality. For example, the <systemitem>nova-compute</systemitem> service supports drivers that let you choose with which hypervisor type it will talk. <systemitem>nova-network</systemitem> and <systemitem>nova-scheduler</systemitem> also have drivers."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:87(title)
+msgid "Manage Compute users"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:88(para)
+msgid "Access to the Euca2ools (ec2) API is controlled by an access and secret key. The user’s access key needs to be included in the request, and the request must be signed with the secret key. Upon receipt of API requests, Compute verifies the signature and runs commands on behalf of the user."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:94(para)
+msgid "To begin using Compute, you must create a user with the Identity Service."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:102(title)
+msgid "Inject administrator password"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:103(para)
+msgid "You can configure Compute to generate a random administrator (root) password and inject that password into the instance. If this feature is enabled, a user can <placeholder-1/> to an instance without an <placeholder-2/> keypair. The random password appears in the output of the <placeholder-3/> command. You can also view and set the <literal>admin</literal> password from the dashboard."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:110(para)
+msgid "The dashboard is configured by default to display the <literal>admin</literal> password and allow the user to modify it."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:112(para)
+msgid "If you do not want to support password injection, we recommend disabling the password fields by editing your Dashboard <filename>local_settings</filename> file (file location will vary by Linux distribution, on Fedora/RHEL/CentOS: <filename> /etc/openstack-dashboard/local_settings</filename>, on Ubuntu and Debian: <filename>/etc/openstack-dashboard/local_settings.py</filename> and on openSUSE and SUSE Linux Enterprise Server: <filename>/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py</filename>) <placeholder-1/>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:128(title)
+msgid "Libvirt-based hypervisors (KVM, QEMU, LXC)"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:129(para)
+msgid "For hypervisors such as KVM that use the libvirt backend, <literal>admin</literal> password injection is disabled by default. To enable it, set the following option in <filename>/etc/nova/nova.conf</filename>:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:136(para)
+msgid "When enabled, Compute will modify the password of the root account by editing the <filename>/etc/shadow</filename> file inside of the virtual machine instance."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:141(para)
+msgid "Users can only ssh to the instance by using the admin password if:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:145(para)
+msgid "The virtual machine image is a Linux distribution"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:149(para)
+msgid "The virtual machine has been configured to allow users to <placeholder-1/> as the root user. This is not the case for <link href=\"http://cloud-images.ubuntu.com/\">Ubuntu cloud images</link>, which disallow <placeholder-2/> to the root account by default."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:159(title)
+msgid "XenAPI (XenServer/XCP)"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:160(para)
+msgid "Compute uses the XenAPI agent to inject passwords into guests when using the XenAPI hypervisor backend. The virtual-machine image must be configured with the agent for password injection to work."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:165(title)
+msgid "Windows images (all hypervisors)"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:166(para)
+msgid "To support the <literal>admin</literal> password for Windows virtual machines, you must configure the Windows image to retrieve the <literal>admin</literal> password on boot by installing an agent such as <link href=\"https://github.com/cloudbase/cloudbase-init\">cloudbase-init</link>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:174(title)
+msgid "Manage the cloud"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:175(para)
+msgid "A system administrator can use the <placeholder-1/> client and the <placeholder-2/> commands to manage the cloud."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:177(para)
+msgid "Both nova client and euca2ools can be used by all users, though specific commands might be restricted by Role Based Access Control in the Identity Service."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:180(title)
+msgid "To use the nova client"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:182(para)
+msgid "Installing the <package>python-novaclient</package> package gives you a <code>nova</code> shell command that enables Compute API interactions from the command line. Install the client, and then provide your user name and password (typically set as environment variables for convenience), and then you have the ability to send commands to your cloud on the command line."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:187(para)
+msgid "To install <package>python-novaclient</package>, download the tarball from <link href=\"http://pypi.python.org/pypi/python-novaclient/2.6.3#downloads\">http://pypi.python.org/pypi/python-novaclient/2.6.3#downloads</link> and then install it in your favorite python environment."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:199(para)
+msgid "Confirm the installation by running:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:214(para)
+msgid "This command returns a list of <placeholder-1/> commands and parameters. To obtain help for a subcommand, run:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:216(replaceable)
+msgid "subcommand"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:217(para)
+msgid "You can also refer to the <link href=\"http://docs.openstack.org/cli-reference/content/\"><citetitle>OpenStack Command-Line Reference</citetitle></link> for a complete listing of <placeholder-1/> commands and parameters."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:224(para)
+msgid "Set the required parameters as environment variables to make running commands easier. For example, you can add <parameter>--os-username</parameter> as a <placeholder-1/> option, or set it as an environment variable. To set the user name, password, and tenant as environment variables, use:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:233(para)
+msgid "Using the Identity Service, you are supplied with an authentication endpoint, which Compute recognizes as the <literal>OS_AUTH_URL</literal>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:242(title)
+msgid "Use the euca2ools commands"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:243(para)
+msgid "For a command-line interface to EC2 API calls, use the <placeholder-1/> command-line tool. See <link href=\"http://open.eucalyptus.com/wiki/Euca2oolsGuide_v1.3\">http://open.eucalyptus.com/wiki/Euca2oolsGuide_v1.3</link>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:251(title)
+msgid "Manage logs"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:253(title)
+msgid "Logging module"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:254(para)
+msgid "To specify a configuration file to change the logging behavior, add this line to the <filename>/etc/nova/nova.conf</filename> file . To change the logging level, such as <literal>DEBUG</literal>, <literal>INFO</literal>, <literal>WARNING</literal>, <literal>ERROR</literal>), use: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:259(para)
+msgid "The logging configuration file is an ini-style configuration file, which must contain a section called <literal>logger_nova</literal>, which controls the behavior of the logging facility in the <literal>nova-*</literal> services. For example:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:269(para)
+msgid "For more details on the logging configuration syntax, including the meaning of the <literal>handlers</literal> and <literal>quaname</literal> variables, see the <link href=\"http://docs.python.org/release/2.7/library/logging.html#configuration-file-format\">Python documentation on logging configuration file format </link>f."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:277(para)
+msgid "For an example <filename>logging.conf</filename> file with various defined handlers, see the <link href=\"http://docs.openstack.org/trunk/config-reference/content/\"><citetitle>OpenStack Configuration Reference</citetitle></link>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:266(para)
+msgid "This example sets the debugging level to <literal>INFO</literal> (which less verbose than the default <literal>DEBUG</literal> setting). <placeholder-1/>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:286(title)
+msgid "Syslog"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:287(para)
+msgid "You can configure OpenStack Compute services to send logging information to <systemitem>syslog</systemitem>. This is useful if you want to use <systemitem>rsyslog</systemitem>, which forwards the logs to a remote machine. You need to separately configure the Compute service (nova), the Identity service (keystone), the Image Service (glance), and, if you are using it, the Block Storage service (cinder) to send log messages to <systemitem>syslog</systemitem>. To do so, add the following lines to:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:296(filename)
+msgid "/etc/nova/nova.conf"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:299(filename)
+msgid "/etc/keystone/keystone.conf"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:302(filename)
+msgid "/etc/glance/glance-api.conf"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:305(filename)
+msgid "/etc/glance/glance-registry.conf"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:308(filename)
+msgid "/etc/cinder/cinder.conf"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:317(para)
+msgid "Although the example above uses the same local facility for each service (<literal>LOG_LOCAL0</literal>, which corresponds to <systemitem>syslog</systemitem> facility <literal>LOCAL0</literal>), we recommend that you configure a separate local facility for each service, as this provides better isolation and more flexibility. For example, you may want to capture logging information at different severity levels for different services. <systemitem>syslog</systemitem> allows you to define up to seven local facilities, <literal>LOCAL0, LOCAL1, ..., LOCAL7</literal>. For more details, see the <systemitem>syslog</systemitem> documentation."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:315(para)
+msgid "In addition to enabling <systemitem>syslog</systemitem>, these settings also turn off more verbose output and debugging output from the log.<placeholder-1/>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:330(title)
+msgid "Rsyslog"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:331(para)
+msgid "<systemitem>rsyslog</systemitem> is a useful tool for setting up a centralized log server across multiple machines. We briefly describe the configuration to set up an <systemitem>rsyslog</systemitem> server; a full treatment of <systemitem>rsyslog</systemitem> is beyond the scope of this document. We assume <systemitem>rsyslog</systemitem> has already been installed on your hosts (default for most Linux distributions)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:337(para)
+msgid "This example provides a minimal configuration for <filename>/etc/rsyslog.conf</filename> on the log server host, which receives the log files:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:343(para)
+msgid "Add a filter rule to <filename>/etc/rsyslog.conf</filename> which looks for a host name. The example below uses <replaceable>compute-01</replaceable> as an example of a compute host name:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:346(replaceable)
+msgid "compute-01"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:347(para)
+msgid "On each compute host, create a file named <filename>/etc/rsyslog.d/60-nova.conf</filename>, with the following content:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:354(para)
+msgid "Once you have created this file, restart your <systemitem>rsyslog</systemitem> daemon. Error-level log messages on the compute hosts should now be sent to your log server."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:362(title)
+msgid "Migrate instances"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:363(para)
+msgid "Before starting migrations, review the <link linkend=\"section_configuring-compute-migrations\">Configure migrations section</link>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:364(para)
+msgid "Migration provides a scheme to migrate running instances from one OpenStack Compute server to another OpenStack Compute server."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:368(title)
+msgid "To migrate instances"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:370(para)
+msgid "Look at the running instances, to get the ID of the instance you wish to migrate."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:381(para)
+msgid "Look at information associated with that instance. This example uses 'vm1' from above."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:397(para)
+msgid "In this example, vm1 is running on HostB."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:400(para)
+msgid "Select the server to which instances will be migrated:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:412(para)
+msgid "In this example, HostC can be picked up because <systemitem class=\"service\">nova-compute</systemitem> is running on it."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:417(para)
+msgid "Ensure that HostC has enough resources for migration."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:431(para)
+msgid "<emphasis role=\"bold\">cpu:</emphasis>the number of cpu"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:436(para)
+msgid "<emphasis role=\"bold\">memory_mb:</emphasis>total amount of memory (in MB)"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:440(para)
+msgid "<emphasis role=\"bold\">disk_gb:</emphasis>total amount of space for NOVA-INST-DIR/instances (in GB)"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:444(para)
+msgid "<emphasis role=\"bold\">1st line shows </emphasis>total amount of resources for the physical server."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:448(para)
+msgid "<emphasis role=\"bold\">2nd line shows </emphasis>currently used resources."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:452(para)
+msgid "<emphasis role=\"bold\">3rd line shows </emphasis>maximum used resources."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:456(para)
+msgid "<emphasis role=\"bold\">4th line and under</emphasis> shows the resource for each project."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:464(replaceable)
+msgid "server"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:464(replaceable)
+msgid "host_name"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:463(para)
+msgid "Use the <placeholder-1/> command to migrate the instances:<placeholder-2/>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:465(para)
+msgid "Where <replaceable>server</replaceable> can be either the server's ID or name. For example:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:473(para)
+msgid "Although the <placeholder-1/> command is called <placeholder-2/>, under the default Compute configuration options the instances are suspended before migration."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:477(para)
+msgid "For more details, see <link href=\"http://docs.openstack.org/trunk/config-reference/content/configuring-openstack-compute-basics.html\">Configure migrations</link> in <citetitle>OpenStack Configuration Reference</citetitle>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:469(para)
+msgid "Ensure instances are migrated successfully with <placeholder-1/>. If instances are still running on HostB, check log files (src/dest <systemitem class=\"service\">nova-compute</systemitem> and <systemitem class=\"service\">nova-scheduler</systemitem>) to determine why. <placeholder-2/>"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:64(None)
+msgid "@@image: '../../common/figures/instance-life-1.png'; md5=c7e56263f9ffb5a5cffb59fbc5ffba35"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:83(None)
+msgid "@@image: '../../common/figures/instance-life-2.png'; md5=84aed8a4c2575548c2f8bacf496465ac"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:121(None)
+msgid "@@image: '../../common/figures/instance-life-3.png'; md5=e25d1bd617373f95e1b8a12605a65ac6"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:7(title)
+msgid "Images and instances"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:8(para)
+msgid "Disk images provide templates for virtual machine file systems. The Image Service manages storage and management of images."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:11(para)
+msgid "Instances are the individual virtual machines that run on physical compute nodes. Users can launch any number of instances from the same image. Each launched instance runs from a copy of the base image so that any changes made to the instance do not affect the base image. You can take snapshots of running instances to create an image based on the current disk state of a particular instance. The Compute services manages instances."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:19(para)
+msgid "When you launch an instance, you must choose a <literal>flavor</literal>, which represents a set of virtual resources. Flavors define how many virtual CPUs an instance has and the amount of RAM and size of its ephemeral disks. OpenStack provides a number of predefined flavors that you can edit or add to. Users must select from the set of available flavors defined on their cloud."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:26(para)
+msgid "For more information about creating and troubleshooting images, see the <link href=\"http://docs.openstack.org/image-guide/content/\"><citetitle>OpenStack Virtual Machine Image Guide</citetitle></link>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:33(para)
+msgid "For more information about image configuration options, see the <link href=\"http://docs.openstack.org/trunk/config-reference/content/ch_configuring-openstack-image-service.html\">Image Services</link> section of the <citetitle>OpenStack Configuration Reference</citetitle>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:39(para)
+msgid "For more information about flavors, see <xref linkend=\"customize-flavors\"/> or the <link href=\"http://docs.openstack.org/trunk/openstack-ops/content/flavors.html\">Flavors</link> section in the <citetitle>OpenStack Operations Guide</citetitle>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:45(para)
+msgid "You can add and remove additional resources from running instances, such as persistent volume storage, or public IP addresses. The example used in this chapter is of a typical virtual system within an OpenStack cloud. It uses the <systemitem class=\"service\">cinder-volume</systemitem> service, which provides persistent block storage, instead of the ephemeral storage provided by the selected instance flavor."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:53(para)
+msgid "This diagram shows the system state prior to launching an instance. The image store, fronted by the Image service (glance) has a number of predefined images. Inside the cloud, a compute node contains the available vCPU, memory, and local disk resources. Additionally, the <systemitem class=\"service\">cinder-volume</systemitem> service provides a number of predefined volumes."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:59(title)
+msgid "Base image state with no running instances"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:68(para)
+msgid "To launch an instance, select an image, a flavor, and other optional attributes. The selected flavor provides a root volume, labeled <literal>vda</literal> in this diagram, and additional ephemeral storage, labeled <literal>vdb</literal>. In this example, the <systemitem class=\"service\">cinder-volume</systemitem> store is mapped to the third virtual disk on this instance, <literal>vdc</literal>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:77(title)
+msgid "Instance creation from image and runtime state"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:87(para)
+msgid "The base image is copied from the image store to the local disk. The local disk is the first disk that the instance accesses, and is labeled <literal>vda</literal>. By using smaller images, your instances start up faster as less data needs to be copied across the network."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:92(para)
+msgid "A new empty disk, labeled <literal>vdb</literal> is also created. This is an empty ephemeral disk, which is destroyed when you delete the instance."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:95(para)
+msgid "The compute node is attached to the <systemitem class=\"service\">cinder-volume</systemitem> using iSCSI, and maps to the third disk, <literal>vdc</literal>. The vCPU and memory resources are provisioned and the instance is booted from <literal>vda</literal>. The instance runs and changes data on the disks as indicated in red in the diagram."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:105(para)
+msgid "Some of the details in this example scenario might be different in your environment. For example, you might use a different type of back-end storage or different network protocols. One common variant is that the ephemeral storage used for volumes <literal>vda</literal> and <literal>vdb</literal> could be backed by network storage rather than a local disk."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:111(para)
+msgid "When the instance is deleted, the state is reclaimed with the exception of the persistent volume. The ephemeral storage is purged; memory and vCPU resources are released. The image remains unchanged throughout."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:115(title)
+msgid "End state of image and volume after instance exits"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:130(title)
+msgid "Control where instances run"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:131(para)
+msgid "The <link href=\"http://docs.openstack.org/trunk/config-reference/content/\"><citetitle>OpenStack Configuration Reference</citetitle></link> provides detailed information on controlling where your instances run, including ensuring a set of instances run on different compute nodes for service resiliency or on the same node for high performance inter-instance communications."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:141(replaceable)
+msgid "availability-zone"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:141(replaceable)
+msgid "compute-host"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-images-instances.xml:139(para)
+msgid "Admin users can specify an exact compute node to run on using the command <placeholder-1/>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:6(title)
+msgid "Image management"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:7(para)
+msgid "The OpenStack Image Service discovers, registers, and retrieves virtual machine images. The service also includes a RESTful API that allows you to query VM image metadata and retrieve the actual image with HTTP requests. For more information about the API, see the <link href=\"http://developer.openstack.org/api-ref.html\">OpenStack API Complete Reference</link> and the <link href=\"http://docs.openstack.org/developer/python-glanceclient/\">Python API</link>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:16(para)
+msgid "The OpenStack Image Service can be controlled using a command-line tool. For more information about the using OpenStack Image command-line tool, see the <link href=\"http://docs.openstack.org/user-guide/content/cli_manage_images.html\">Manage Images</link> section in the <citetitle>OpenStack End User Guide</citetitle>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:22(para)
+msgid "Virtual images that have been made available through the Image Service can be stored in a variety of ways. In order to use these services, you must have a working installation of the Image Service, with a working endpoint, and users that have been created in OpenStack Identity. Additionally, you must meet the environment variables required by the Compute and Image Service clients."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:29(para)
+msgid "The Image Service supports these back-end stores:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:32(term)
+msgid "File system"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:34(para)
+msgid "The OpenStack Image Service stores virtual machine images in the file system back end by default. This simple back end writes image files to the local file system."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:41(term)
+msgid "Object Storage service"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:43(para)
+msgid "The OpenStack highly available service for storing objects."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:48(term)
+msgid "S3"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:50(para)
+msgid "The Amazon S3 service."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:54(term)
+msgid "HTTP"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:56(para)
+msgid "OpenStack Image Service can read virtual machine images that are available on the internet using HTTP. This store is read only."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:62(term)
+msgid "Rados block device (RBD)"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:64(para)
+msgid "Stores images inside of a Ceph storage cluster using Ceph's RBD interface."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:69(term)
+msgid "GridFS"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-image-mgt.xml:71(para)
+msgid "Stores images using MongoDB."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:6(title)
+msgid "Secure with root wrappers"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:7(para)
+msgid "The root wrapper enables an unprivileged user to run a number of Compute actions as the root user in the safest manner possible. Historically, Compute used a specific <filename>sudoers</filename> file that listed every command that the Compute user was allowed to run, and used <placeholder-1/> to run that command as <literal>root</literal>. However this was difficult to maintain (the <filename>sudoers</filename> file was in packaging), and did not enable complex filtering of parameters (advanced filters). The rootwrap was designed to solve those issues."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:16(title)
+msgid "How rootwrap works"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:17(para)
+msgid "Instead of calling <placeholder-1/>, Compute services start with a <placeholder-2/> call; for example, <placeholder-3/>. A generic sudoers entry lets the Compute user run <placeholder-4/> as root. The <placeholder-5/> code looks for filter definition directories in its configuration file, and loads command filters from them. Then it checks if the command requested by Compute matches one of those filters, in which case it executes the command (as root). If no filter matches, it denies the request."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:25(para)
+msgid "To use <placeholder-1/>, you must be aware of the issues with using NFS and root-owned files. The NFS share must be configured with the <option>no_root_squash</option> option enabled."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:31(title)
+msgid "Security model"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:32(para)
+msgid "The escalation path is fully controlled by the root user. A sudoers entry (owned by root) allows Compute to run (as root) a specific rootwrap executable, and only with a specific configuration file (which should be owned by root). <placeholder-1/> imports the Python modules it needs from a cleaned (and system-default) <replaceable>PYTHONPATH</replaceable>. The configuration file (also root-owned) points to root-owned filter definition directories, which contain root-owned filters definition files. This chain ensures that the Compute user itself is not in control of the configuration or modules used by the <placeholder-2/> executable."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:43(title)
+msgid "Details of rootwrap.conf"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:44(para)
+msgid "You configure <placeholder-1/> in the <filename>rootwrap.conf</filename> file. Because it's in the trusted security path, it must be owned and writable by only the root user. The file's location is specified both in the sudoers entry and in the <filename>nova.conf</filename> configuration file with the <code>rootwrap_config=entry</code>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:49(para)
+msgid "The <filename>rootwrap.conf</filename> file uses an INI file format with these sections and parameters:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:53(caption)
+msgid "rootwrap.conf configuration options"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:58(para) ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:96(para)
+msgid "Configuration option=Default value"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:60(para) ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:98(para)
+msgid "(Type) Description"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:65(para)
+msgid "[DEFAULT]"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:66(para)
+msgid "filters_path=/etc/nova/rootwrap.d,/usr/share/nova/rootwrap"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:68(para)
+msgid "(ListOpt) Comma-separated list of directories containing filter definition files. Defines where filters for root wrap are stored. Directories defined on this line should all exist, be owned and writable only by the root user."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:80(title)
+msgid "Details of .filters files"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:81(para)
+msgid "Filters definition files contain lists of filters that <placeholder-1/> will use to allow or deny a specific command. They are generally suffixed by .filters. Since they are in the trusted security path, they need to be owned and writable only by the root user. Their location is specified in the <filename>rootwrap.conf</filename> file."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:86(para)
+msgid "Filter definition files use an INI file format with a [Filters] section and several lines, each with a unique parameter name (different for each filter that you define):"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:91(caption)
+msgid ".filters configuration options"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:103(para)
+msgid "[Filters]"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:104(para)
+msgid "filter_name=kpartx: CommandFilter, /sbin/kpartx, root"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-rootwrap.xml:106(para)
+msgid "(ListOpt) Comma-separated list containing first the Filter class to use, followed by that Filter arguments (which vary depending on the Filter class selected)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:7(title)
+msgid "Configure migrations"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:9(para)
+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:13(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:17(para)
+msgid "The migration types are:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:20(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."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:31(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:36(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:43(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: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 types of <firstterm>live migration</firstterm> are: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:53(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:57(title)
+msgid "KVM-Libvirt"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:59(title) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:264(title) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:339(title)
+msgid "Prerequisites"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:61(para)
+msgid "<emphasis role=\"bold\">Hypervisor:</emphasis> KVM with libvirt"
+msgstr ""
+
+#: ./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:74(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:81(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:88(para)
+msgid "This guide assumes the default value for <option>instances_path</option> 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."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:97(para)
+msgid "You must specify <literal>vncserver_listen=0.0.0.0</literal> or live migration does not work correctly."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:104(title)
+msgid "Example Compute installation environment"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:110(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:118(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:107(para)
+msgid "Prepare at least three servers; for example, <literal>HostA</literal>, <literal>HostB</literal>, and <literal>HostC</literal>: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:123(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:128(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."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:136(title)
+msgid "To configure your system"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:138(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:148(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:153(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:156(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 / Redhat: Setup NFS v4.0 File Server</link>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:163(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:165(replaceable) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:180(replaceable) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:185(replaceable) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:191(replaceable) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:195(replaceable)
+msgid "NOVA-INST-DIR"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:166(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:174(para)
+msgid "Set the 'execute/search' bit on your shared directory."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:176(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:183(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:186(para)
+msgid "Ensure that you can mount the exported directory can be mounted:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:188(para)
+msgid "Check that HostA can see the \"<filename><replaceable>NOVA-INST-DIR</replaceable>/instances/</filename>\" directory:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:191(filename) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:195(filename)
+msgid "<placeholder-1/>/instances/"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:193(para)
+msgid "Perform the same check at HostB and HostC, paying special attention to the permissions (Compute should be able to write):"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:208(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."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:212(para)
+msgid "SSH tunnel to libvirtd's UNIX socket"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:213(para)
+msgid "libvirtd TCP socket, with GSSAPI/Kerberos for auth+data encryption"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:215(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:216(para)
+msgid "libvirtd TCP socket, with TLS for encryption and Kerberos for authentication"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:220(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:227(para)
+msgid "Configure your firewall to allow libvirt to communicate between nodes."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:229(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:237(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:245(title)
+msgid "Enable true live migration"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:246(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:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:251(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."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:262(title)
+msgid "Shared storage"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:266(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:275(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:278(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:285(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."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:291(title)
+msgid "To use shared storage live migration with XenServer hypervisors"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:294(para)
+msgid "Add an NFS VHD storage to your master XenServer, and set it as default SR. For more information, please refer to the <link href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/reference.html#id1002701\">NFS VHD</link> section in the <citetitle>XenServer Administrator's Guide</citetitle>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:302(para)
+msgid "Configure all the compute nodes to use the default sr for pool operations. Add this line to your <filename>nova.conf</filename> configuration files across your compute nodes:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:309(para)
+msgid "Create a host aggregate:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:311(para)
+msgid "The command displays a table that contains the ID of the newly created aggregate."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:313(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:317(para)
+msgid "Make the first compute node part of that aggregate:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:320(para)
+msgid "At this point, the host is part of a XenServer pool."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:324(para)
+msgid "Add additional hosts to the pool:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:327(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."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:337(title)
+msgid "Block migration"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:341(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:350(para)
+msgid "To use block migration, you must use the CHANGE THIS == <parameter>==block-migrate</parameter> parameter with the live migration command."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:355(para)
+msgid "Block migration works only with EXT local storage SRs, and the server must not have any volumes attached."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:7(title)
+msgid "Recover from a failed compute node"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:8(para)
+msgid "If you deployed Compute with a shared file system, you can quickly recover from a failed compute node. Of the two methods covered in these sections, evacuating is the preferred method even in the absence of shared storage. Evacuating provides many benefits over manual recovery, such as re-attachment of volumes and floating IPs."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:14(title)
+msgid "Manual recovery"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:15(para)
+msgid "To recover a KVM/libvirt compute node, see the previous section. Use the following procedure for all other hypervisors."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:18(title)
+msgid "Review host information"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:20(para)
+msgid "Identify the VMs on the affected hosts, using tools such as a combination of <literal>nova list</literal> and <literal>nova show</literal> or <literal>euca-describe-instances</literal>. For example, the following output displays information about instance <systemitem>i-000015b9</systemitem> that is running on node <systemitem>np-rcc54</systemitem>:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:29(para)
+msgid "Review the status of the host by querying the Compute database. Some of the important information is highlighted below. The following example converts an EC2 API instance ID into an OpenStack ID; if you used the <literal>nova</literal> commands, you can substitute the ID directly. You can find the credentials for your database in <filename>/etc/nova.conf</filename>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:55(title)
+msgid "Recover the VM"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:57(para)
+msgid "After you have determined the status of the VM on the failed host, decide to which compute host the affected VM should be moved. For example, run the following database command to move the VM to <systemitem>np-rcc46</systemitem>:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:64(para)
+msgid "If using a hypervisor that relies on libvirt (such as KVM), it is a good idea to update the <literal>libvirt.xml</literal> file (found in <literal>/var/lib/nova/instances/[instance ID]</literal>). The important changes to make are:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:71(para)
+msgid "Change the <literal>DHCPSERVER</literal> value to the host IP address of the compute host that is now the VM's new home."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:76(para)
+msgid "Update the VNC IP, if it isn't already updated, to: <literal>0.0.0.0</literal>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:83(para)
+msgid "Reboot the VM:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:87(para)
+msgid "In theory, the above database update and <literal>nova reboot</literal> command are all that is required to recover a VM from a failed host. However, if further problems occur, consider looking at recreating the network filter configuration using <literal>virsh</literal>, restarting the Compute services or updating the <literal>vm_state</literal> and <literal>power_state</literal> in the Compute database."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:95(title)
+msgid "Recover from a UID/GID mismatch"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:96(para)
+msgid "When running OpenStack Compute, using a shared file system or an automated configuration tool, you could encounter a situation where some files on your compute node are using the wrong UID or GID. This causes a number of errors, such as being unable to do live migration or start virtual machines."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:100(para)
+msgid "The following procedure runs on <systemitem class=\"service\">nova-compute</systemitem> hosts, based on the KVM hypervisor, and could help to restore the situation:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:104(title)
+msgid "To recover from a UID/GID mismatch"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:106(para)
+msgid "Ensure you do not use numbers that are already used for some other user/group."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:110(para)
+msgid "Set the nova uid in <filename>/etc/passwd</filename> to the same number in all hosts (for example, 112)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:114(para)
+msgid "Set the libvirt-qemu uid in <filename>/etc/passwd</filename> to the same number in all hosts (for example, 119)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:120(para)
+msgid "Set the nova group in <filename>/etc/group</filename> file to the same number in all hosts (for example, 120)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:126(para)
+msgid "Set the libvirtd group in <filename>/etc/group</filename> file to the same number in all hosts (for example, 119)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:132(para)
+msgid "Stop the services on the compute node."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:136(para)
+msgid "Change all the files owned by user <systemitem>nova</systemitem> or by group <systemitem>nova</systemitem>. For example:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:142(para)
+msgid "Repeat the steps for the libvirt-qemu owned files if those needed to change."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:146(para)
+msgid "Restart the services."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:149(para)
+msgid "Now you can run the <placeholder-1/> command to verify that all files using the correct identifiers."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:156(title)
+msgid "Recover cloud after disaster"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:157(para)
+msgid "Use the following procedures to manage your cloud after a disaster, and to easily back up its persistent storage volumes. Backups <emphasis role=\"bold\">are</emphasis> mandatory, even outside of disaster scenarios."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:160(para)
+msgid "For a DRP definition, see <link href=\"http://en.wikipedia.org/wiki/Disaster_Recovery_Plan\">http://en.wikipedia.org/wiki/Disaster_Recovery_Plan</link>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:164(title)
+msgid "Disaster recovery example"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:165(para)
+msgid "A disaster could happen to several components of your architecture (for example, a disk crash, a network loss, or a power cut). In this example, the following components are configured:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:170(para)
+msgid "A cloud controller (<systemitem>nova-api</systemitem>, <systemitem>nova-objectstore</systemitem>, <systemitem>nova-network</systemitem>)"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:175(para)
+msgid "A compute node (<systemitem class=\"service\">nova-compute</systemitem>)"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:180(para)
+msgid "A Storage Area Network (SAN) used by OpenStack Block Storage (<systemitem class=\"service\">cinder-volumes</systemitem>)"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:184(para)
+msgid "The worst disaster for a cloud is a power loss, which applies to all three components. Before a power loss:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:188(para)
+msgid "From the SAN to the cloud controller, we have an active iSCSI session (used for the \"cinder-volumes\" LVM's VG)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:192(para)
+msgid "From the cloud controller to the compute node, we also have active iSCSI sessions (managed by <systemitem class=\"service\">cinder-volume</systemitem>)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:197(para)
+msgid "For every volume, an iSCSI session is made (so 14 ebs volumes equals 14 sessions)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:201(para)
+msgid "From the cloud controller to the compute node, we also have iptables/ ebtables rules, which allow access from the cloud controller to the running instance."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:206(para)
+msgid "And at least, from the cloud controller to the compute node; saved into database, the current state of the instances (in that case \"running\" ), and their volumes attachment (mount point, volume ID, volume status, and so on.)"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:212(para)
+msgid "After the power loss occurs and all hardware components restart:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:215(para)
+msgid "From the SAN to the cloud, the iSCSI session no longer exists."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:218(para)
+msgid "From the cloud controller to the compute node, the iSCSI sessions no longer exist."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:222(para)
+msgid "From the cloud controller to the compute node, the iptables and ebtables are recreated, since at boot, <systemitem>nova-network</systemitem> reapplies configurations."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:227(para)
+msgid "From the cloud controller, instances are in a shutdown state (because they are no longer running)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:231(para)
+msgid "In the database, data was not updated at all, since Compute could not have anticipated the crash."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:235(para)
+msgid "Before going further, and to prevent the administrator from making fatal mistakes,<emphasis role=\"bold\"> instances won't be lost</emphasis>, because no \"<placeholder-1/>\" or \"<placeholder-2/>\" command was invoked, so the files for the instances remain on the compute node."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:240(para)
+msgid "Do not add any extra steps at this stage."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:239(para)
+msgid "Perform these tasks in the following order. <placeholder-1/>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:244(para)
+msgid "Get the current relation from a volume to its instance, so that you can recreate the attachment."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:249(para)
+msgid "Update the database to clean the stalled state. (After that, you cannot perform the first step)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:254(para)
+msgid "Restart the instances. In other words, go from a shutdown to running state."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:259(para)
+msgid "After the restart, reattach the volumes to their respective instances (optional)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:263(para)
+msgid "SSH into the instances to reboot them."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:269(title)
+msgid "Recover after a disaster"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:271(title)
+msgid "To perform disaster recovery"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:273(title)
+msgid "Get the instance-to-volume relationship"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:275(para)
+msgid "You must determine the current relationship from a volume to its instance, because you will re-create the attachment."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:277(para)
+msgid "You can find this relationship by running <placeholder-1/>. Note that the <placeholder-2/> client includes the ability to get volume information from OpenStack Block Storage."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:283(title)
+msgid "Update the database"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:284(para)
+msgid "Update the database to clean the stalled state. You must restore for every volume, using these queries to clean up the database:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:291(para)
+msgid "You can then run <placeholder-1/> commands to list all volumes."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:295(title)
+msgid "Restart instances"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:297(replaceable)
+msgid "$instance"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:296(para)
+msgid "Restart the instances using the <placeholder-1/> command."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:298(para)
+msgid "At this stage, depending on your image, some instances completely reboot and become reachable, while others stop on the \"plymouth\" stage."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:303(title)
+msgid "DO NOT reboot a second time"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:304(para)
+msgid "Do not reboot instances that are stopped at this point. Instance state depends on whether you added an <filename>/etc/fstab</filename> entry for that volume. Images built with the <package>cloud-init</package> package remain in a pending state, while others skip the missing volume and start. The idea of that stage is only to ask Compute to reboot every instance, so the stored state is preserved. For more information about <package>cloud-init</package>, see <link href=\"https://help.ubuntu.com/community/CloudInit\">help.ubuntu.com/community/CloudInit</link>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:315(title)
+msgid "Reattach volumes"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:316(para)
+msgid "After the restart, and Compute has restored the right status, you can reattach the volumes to their respective instances using the <placeholder-1/> command. The following snippet uses a file of listed volumes to reattach them:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:330(para)
+msgid "At this stage, instances that were pending on the boot sequence (<application>plymouth</application>) automatically continue their boot, and restart normally, while the ones that booted see the volume."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:335(title)
+msgid "SSH into instances"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:336(para)
+msgid "If some services depend on the volume, or if a volume has an entry into <systemitem>fstab</systemitem>, you should now simply restart the instance. This restart needs to be made from the instance itself, not through <placeholder-1/>."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:340(para)
+msgid "SSH into the instance and perform a reboot:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:344(para)
+msgid "By completing this procedure, you can successfully recover your cloud."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:347(para)
+msgid "Follow these guidelines:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:350(para)
+msgid "Use the <parameter> errors=remount</parameter> parameter in the <filename>fstab</filename> file, which prevents data corruption."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:353(para)
+msgid "The system locks any write to the disk if it detects an I/O error. This configuration option should be added into the <systemitem class=\"service\">cinder-volume</systemitem> server (the one which performs the iSCSI connection to the SAN), but also into the instances' <filename>fstab</filename> file."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:360(para)
+msgid "Do not add the entry for the SAN's disks to the <systemitem class=\"service\">cinder-volume</systemitem>'s <filename>fstab</filename> file."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:363(para)
+msgid "Some systems hang on that step, which means you could lose access to your cloud-controller. To re-run the session manually, run the following command before performing the mount: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:369(para)
+msgid "For your instances, if you have the whole <filename>/home/</filename> directory on the disk, leave a user's directory with the user's bash files and the <filename>authorized_keys</filename> file (instead of emptying the <filename>/home</filename> directory and mapping the disk on it)."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:374(para)
+msgid "This enables you to connect to the instance, even without the volume attached, if you allow only connections through public keys."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:381(title)
+msgid "Script the DRP"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:382(para)
+msgid "You can download from <link href=\"https://github.com/Razique/BashStuff/blob/master/SYSTEMS/OpenStack/SCR_5006_V00_NUAC-OPENSTACK-DRP-OpenStack.sh\">here</link> a bash script which performs the following steps:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:386(para)
+msgid "An array is created for instances and their attached volumes."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:387(para)
+msgid "The MySQL database is updated."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:388(para)
+msgid "Using <systemitem>euca2ools</systemitem>, all instances are restarted."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:389(para)
+msgid "The volume attachment is made."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:390(para)
+msgid "An SSH connection is performed into every instance using Compute credentials."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:392(para)
+msgid "The \"test mode\" allows you to perform that whole sequence for only one instance."
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:395(para)
+msgid "To reproduce the power loss, connect to the compute node which runs that same instance and close the iSCSI session. Do not detach the volume using the <placeholder-1/> command; instead, manually close the iSCSI session. For the following example command uses an iSCSI session with the number 15:"
+msgstr ""
+
+#: ./doc/admin-guide-cloud/compute/section_compute-recover-nodes.xml:400(para)
+msgid "Do not forget the <literal>-r</literal> flag. Otherwise, you close ALL sessions."
+msgstr ""
+
 #: ./doc/admin-guide-cloud/image/section_glance-property-protection.xml:6(title)
 msgid "Image property protection"
 msgstr ""
@@ -9233,80 +9305,8 @@ msgstr ""
 msgid "Define which roles can manage which properties in the <filename>/etc/glance/property-protections.conf</filename> file."
 msgstr ""
 
-#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:6(title)
-msgid "Configure Identity service for token binding"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:7(para)
-msgid "Token binding embeds information from an external authentication mechanism, such as a Kerberos server or X.509 certificate, inside a token. By using token binding, a client can enforce the use of a specified external authentication mechanism with the token. This additional security mechanism ensures that if a token is stolen, for example, it is not usable without external authentication."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:14(para)
-msgid "You configure the authentication types for a token binding in the <filename>keystone.conf</filename> file:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:18(para)
-msgid "or"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:21(para)
-msgid "Currently <literal>kerberos</literal> and <literal>x509</literal> are supported."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:23(para)
-msgid "To enforce checking of token binding, set the <option>enforce_token_bind</option> option to one of these modes:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:28(literal)
-msgid "disabled"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:29(para)
-msgid "Disables token bind checking."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:32(literal)
-msgid "permissive"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:33(para)
-msgid "Enables bind checking. If a token is bound to an unknown authentication mechanism, the server ignores it. The default is this mode."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:38(literal)
-msgid "strict"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:39(para)
-msgid "Enables bind checking. If a token is bound to an unknown authentication mechanism, the server rejects it."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:43(literal)
-msgid "required"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:44(para)
-msgid "Enables bind checking. Requires use of at least authentication mechanism for tokens."
-msgstr ""
-
-#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:48(literal)
-msgid "kerberos"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:49(para)
-msgid "Enables bind checking. Requires use of kerberos as the authentication mechanism for tokens:"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:55(literal)
-msgid "x509"
-msgstr ""
-
-#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:56(para)
-msgid "Enables bind checking. Requires use of X.509 as the authentication mechanism for tokens:"
-msgstr ""
-
 #. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
-#: ./doc/admin-guide-cloud/identity/section_keystone-token-binding.xml:0(None)
+#: ./doc/admin-guide-cloud/image/section_glance-property-protection.xml:0(None)
 msgid "translator-credits"
 msgstr ""
 
diff --git a/doc/cli-reference/locale/cli-reference.pot b/doc/cli-reference/locale/cli-reference.pot
index b90244ed0b..e7c94d8c41 100644
--- a/doc/cli-reference/locale/cli-reference.pot
+++ b/doc/cli-reference/locale/cli-reference.pot
@@ -1,7 +1,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2014-05-16 06:33+0000\n"
+"POT-Creation-Date: 2014-06-03 06:11+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -9,282 +9,6 @@ msgstr ""
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:11(title)
-msgid "neutron-debug command-line client"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:12(para)
-msgid "The <placeholder-1/> client is an extension to the <placeholder-2/> command-line interface (CLI) for the OpenStack neutron-debug tool. This chapter documents <placeholder-3/> version 2.3.0."
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:16(para)
-msgid "For help on a specific <placeholder-1/> command, enter:"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:18(option)
-msgid "help"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:18(replaceable)
-msgid "COMMAND"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:21(title)
-msgid "neutron-debug usage"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:34(title)
-msgid "Subcommands"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:38(para)
-msgid "Create probe port - create port and interface within a network namespace."
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:46(para)
-msgid "List all probes."
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:54(para) ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:239(para)
-msgid "Clear all probes."
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:62(para)
-msgid "Delete probe - delete port then delete the namespace."
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:70(para)
-msgid "Execute commands in the namespace of the probe."
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:78(para)
-msgid "ping-all is all-in-one command to ping all fixed IP's in a specified network."
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:86(title)
-msgid "neutron-debug optional arguments"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:91(para)
-msgid "Show version number and exit."
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:97(para)
-msgid "Increase verbosity of output and show tracebacks on errors. Can be repeated."
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:104(para)
-msgid "Suppress output except warnings and errors"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:110(para)
-msgid "Show this help message and exit"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:117(para)
-msgid "Authentication strategy (Env: OS_AUTH_STRATEGY, default keystone). For now, any other value will disable the authentication"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:125(para)
-msgid "Authentication URL (Env: OS_AUTH_URL)"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:132(para)
-msgid "Authentication tenant name (Env: OS_TENANT_NAME)"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:140(para)
-msgid "Authentication tenant name (Env: OS_TENANT_ID)"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:148(para)
-msgid "Authentication username (Env: OS_USERNAME)"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:155(para)
-msgid "Authentication password (Env: OS_PASSWORD)"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:162(para)
-msgid "Authentication region name (Env: OS_REGION_NAME)"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:169(para)
-msgid "Defaults to <code>env[OS_TOKEN]</code>"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:177(para)
-msgid "Defaults to <code>env[OS_ENDPOINT_TYPE]</code> or public URL."
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:184(para)
-msgid "Defaults to <code>env[OS_URL]</code>"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:192(para)
-msgid "Specify a CA bundle file to use in verifying a TLS (https) server certificate. Defaults to <code>env[OS_CACERT]</code>"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:201(para)
-msgid "Explicitly allow neutron-debug to perform \"insecure\" SSL (https) requests. The server's certificate will not be verified against any certificate authorities. This option should be used with caution."
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:210(para)
-msgid "Config file for interface driver (You may also use l3_agent.ini)"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:217(title)
-msgid "neutron-debug probe-create command"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:219(para)
-msgid "Create probe port - create port and interface, then place it into the created network namespace."
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:221(title) ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:247(title) ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:266(title)
-msgid "Positional arguments"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:225(para)
-msgid "ID of the network in which the probe will be created."
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:232(title)
-msgid "neutron-debug probe-list command"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:234(para)
-msgid "List probes."
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:237(title)
-msgid "neutron-debug probe-clear command"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:242(title)
-msgid "neutron-debug probe-delete command"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:244(para)
-msgid "Remove a probe."
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:251(para)
-msgid "ID of the probe to delete."
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:257(title)
-msgid "neutron-debug probe-exec command"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:259(para)
-msgid "Execute commands in the namespace of the probe"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:262(title)
-msgid "neutron-debug ping-all command"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:264(para)
-msgid "All-in-one command to ping all fixed IP's in a specified network."
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:270(para)
-msgid "ID of the port to use."
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:275(title)
-msgid "Optional arguments"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:280(para)
-msgid "Optional ping timeout."
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:286(title)
-msgid "neutron-debug example"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:288(para)
-msgid "Create a probe namespace within the network identified by NET_ID. The namespace will have the name of qprobe-&lt;UUID of the probe port&gt;"
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:291(para)
-msgid "For the following examples to function, the security group rules may need to be modified to allow the SSH (TCP port 22) or ping (ICMP) traffic into network."
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:295(para)
-msgid "SSH to an instance within the network."
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:297(para)
-msgid "Ping all instances on this network to verify they are responding."
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:300(para)
-msgid "Ping the DHCP server for this network using dhcping to verify it is working."
-msgstr ""
-
-#: ./doc/cli-reference/bk-cli-reference.xml:8(title)
-msgid "OpenStack Command-Line Interface Reference"
-msgstr ""
-
-#: ./doc/cli-reference/bk-cli-reference.xml:10(titleabbrev)
-msgid "CLI Reference"
-msgstr ""
-
-#: ./doc/cli-reference/bk-cli-reference.xml:18(orgname) ./doc/cli-reference/bk-cli-reference.xml:23(holder)
-msgid "OpenStack Foundation"
-msgstr ""
-
-#: ./doc/cli-reference/bk-cli-reference.xml:22(year)
-msgid "2014"
-msgstr ""
-
-#: ./doc/cli-reference/bk-cli-reference.xml:25(releaseinfo)
-msgid "current"
-msgstr ""
-
-#: ./doc/cli-reference/bk-cli-reference.xml:26(productname)
-msgid "OpenStack"
-msgstr ""
-
-#: ./doc/cli-reference/bk-cli-reference.xml:30(remark)
-msgid "Remaining licensing details are filled in by the template."
-msgstr ""
-
-#: ./doc/cli-reference/bk-cli-reference.xml:35(para)
-msgid "This guide documents the OpenStack command-line clients."
-msgstr ""
-
-#: ./doc/cli-reference/bk-cli-reference.xml:43(date)
-msgid "2014-04-16"
-msgstr ""
-
-#: ./doc/cli-reference/bk-cli-reference.xml:47(para)
-msgid "For the Icehouse release, updated documentation for clients, add trove options, document neutron-debug, document Image Service property keys."
-msgstr ""
-
-#: ./doc/cli-reference/bk-cli-reference.xml:57(date)
-msgid "2014-01-29"
-msgstr ""
-
-#: ./doc/cli-reference/bk-cli-reference.xml:61(para)
-msgid "Initial version."
-msgstr ""
-
-#: ./doc/cli-reference/bk-cli-reference.xml:67(date)
-msgid "2014-03-14"
-msgstr ""
-
-#: ./doc/cli-reference/bk-cli-reference.xml:71(para)
-msgid "Added documentation for the neutron-debug command."
-msgstr ""
-
-#: ./doc/cli-reference/ch_cli.xml:10(title)
-msgid "OpenStack command-line clients"
-msgstr ""
-
 #. This file is manually generated, unlike many of the other chapters.
 #: ./doc/cli-reference/ch_cli_glance_property_keys.xml:11(title)
 msgid "Image Service property keys"
@@ -1066,8 +790,284 @@ msgstr ""
 msgid "<placeholder-1/> or <placeholder-2/>"
 msgstr ""
 
+#: ./doc/cli-reference/bk-cli-reference.xml:8(title)
+msgid "OpenStack Command-Line Interface Reference"
+msgstr ""
+
+#: ./doc/cli-reference/bk-cli-reference.xml:10(titleabbrev)
+msgid "CLI Reference"
+msgstr ""
+
+#: ./doc/cli-reference/bk-cli-reference.xml:18(orgname) ./doc/cli-reference/bk-cli-reference.xml:23(holder)
+msgid "OpenStack Foundation"
+msgstr ""
+
+#: ./doc/cli-reference/bk-cli-reference.xml:22(year)
+msgid "2014"
+msgstr ""
+
+#: ./doc/cli-reference/bk-cli-reference.xml:25(releaseinfo)
+msgid "current"
+msgstr ""
+
+#: ./doc/cli-reference/bk-cli-reference.xml:26(productname)
+msgid "OpenStack"
+msgstr ""
+
+#: ./doc/cli-reference/bk-cli-reference.xml:30(remark)
+msgid "Remaining licensing details are filled in by the template."
+msgstr ""
+
+#: ./doc/cli-reference/bk-cli-reference.xml:35(para)
+msgid "This guide documents the OpenStack command-line clients."
+msgstr ""
+
+#: ./doc/cli-reference/bk-cli-reference.xml:43(date)
+msgid "2014-04-16"
+msgstr ""
+
+#: ./doc/cli-reference/bk-cli-reference.xml:47(para)
+msgid "For the Icehouse release, updated documentation for clients, add trove options, document neutron-debug, document Image Service property keys."
+msgstr ""
+
+#: ./doc/cli-reference/bk-cli-reference.xml:57(date)
+msgid "2014-01-29"
+msgstr ""
+
+#: ./doc/cli-reference/bk-cli-reference.xml:61(para)
+msgid "Initial version."
+msgstr ""
+
+#: ./doc/cli-reference/bk-cli-reference.xml:67(date)
+msgid "2014-03-14"
+msgstr ""
+
+#: ./doc/cli-reference/bk-cli-reference.xml:71(para)
+msgid "Added documentation for the neutron-debug command."
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli.xml:10(title)
+msgid "OpenStack command-line clients"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:11(title)
+msgid "neutron-debug command-line client"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:12(para)
+msgid "The <placeholder-1/> client is an extension to the <placeholder-2/> command-line interface (CLI) for the OpenStack neutron-debug tool. This chapter documents <placeholder-3/> version 2.3.0."
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:16(para)
+msgid "For help on a specific <placeholder-1/> command, enter:"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:18(option)
+msgid "help"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:18(replaceable)
+msgid "COMMAND"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:21(title)
+msgid "neutron-debug usage"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:34(title)
+msgid "Subcommands"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:38(para)
+msgid "Create probe port - create port and interface within a network namespace."
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:46(para)
+msgid "List all probes."
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:54(para) ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:239(para)
+msgid "Clear all probes."
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:62(para)
+msgid "Delete probe - delete port then delete the namespace."
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:70(para)
+msgid "Execute commands in the namespace of the probe."
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:78(para)
+msgid "ping-all is all-in-one command to ping all fixed IP's in a specified network."
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:86(title)
+msgid "neutron-debug optional arguments"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:91(para)
+msgid "Show version number and exit."
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:97(para)
+msgid "Increase verbosity of output and show tracebacks on errors. Can be repeated."
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:104(para)
+msgid "Suppress output except warnings and errors"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:110(para)
+msgid "Show this help message and exit"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:117(para)
+msgid "Authentication strategy (Env: OS_AUTH_STRATEGY, default keystone). For now, any other value will disable the authentication"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:125(para)
+msgid "Authentication URL (Env: OS_AUTH_URL)"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:132(para)
+msgid "Authentication tenant name (Env: OS_TENANT_NAME)"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:140(para)
+msgid "Authentication tenant name (Env: OS_TENANT_ID)"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:148(para)
+msgid "Authentication username (Env: OS_USERNAME)"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:155(para)
+msgid "Authentication password (Env: OS_PASSWORD)"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:162(para)
+msgid "Authentication region name (Env: OS_REGION_NAME)"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:169(para)
+msgid "Defaults to <code>env[OS_TOKEN]</code>"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:177(para)
+msgid "Defaults to <code>env[OS_ENDPOINT_TYPE]</code> or public URL."
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:184(para)
+msgid "Defaults to <code>env[OS_URL]</code>"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:192(para)
+msgid "Specify a CA bundle file to use in verifying a TLS (https) server certificate. Defaults to <code>env[OS_CACERT]</code>"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:201(para)
+msgid "Explicitly allow neutron-debug to perform \"insecure\" SSL (https) requests. The server's certificate will not be verified against any certificate authorities. This option should be used with caution."
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:210(para)
+msgid "Config file for interface driver (You may also use l3_agent.ini)"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:217(title)
+msgid "neutron-debug probe-create command"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:219(para)
+msgid "Create probe port - create port and interface, then place it into the created network namespace."
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:221(title) ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:247(title) ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:266(title)
+msgid "Positional arguments"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:225(para)
+msgid "ID of the network in which the probe will be created."
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:232(title)
+msgid "neutron-debug probe-list command"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:234(para)
+msgid "List probes."
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:237(title)
+msgid "neutron-debug probe-clear command"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:242(title)
+msgid "neutron-debug probe-delete command"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:244(para)
+msgid "Remove a probe."
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:251(para)
+msgid "ID of the probe to delete."
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:257(title)
+msgid "neutron-debug probe-exec command"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:259(para)
+msgid "Execute commands in the namespace of the probe"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:262(title)
+msgid "neutron-debug ping-all command"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:264(para)
+msgid "All-in-one command to ping all fixed IP's in a specified network."
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:270(para)
+msgid "ID of the port to use."
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:275(title)
+msgid "Optional arguments"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:280(para)
+msgid "Optional ping timeout."
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:286(title)
+msgid "neutron-debug example"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:288(para)
+msgid "Create a probe namespace within the network identified by NET_ID. The namespace will have the name of qprobe-&lt;UUID of the probe port&gt;"
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:291(para)
+msgid "For the following examples to function, the security group rules may need to be modified to allow the SSH (TCP port 22) or ping (ICMP) traffic into network."
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:295(para)
+msgid "SSH to an instance within the network."
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:297(para)
+msgid "Ping all instances on this network to verify they are responding."
+msgstr ""
+
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:300(para)
+msgid "Ping the DHCP server for this network using dhcping to verify it is working."
+msgstr ""
+
 #. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
-#: ./doc/cli-reference/ch_cli_glance_property_keys.xml:0(None)
+#: ./doc/cli-reference/ch_cli_neutron-debug_commands.xml:0(None)
 msgid "translator-credits"
 msgstr ""
 
diff --git a/doc/common/locale/common.pot b/doc/common/locale/common.pot
index d8b3b08266..2b35a2a5be 100644
--- a/doc/common/locale/common.pot
+++ b/doc/common/locale/common.pot
@@ -1,7 +1,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2014-06-02 06:10+0000\n"
+"POT-Creation-Date: 2014-06-03 06:11+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -9,946 +9,46 @@ msgstr ""
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
-#: ./doc/common/app_support.xml:7(title)
-msgid "Community support"
-msgstr ""
-
-#: ./doc/common/app_support.xml:8(para)
-msgid "The following resources are available to help you run and use OpenStack. The OpenStack community constantly improves and adds to the main features of OpenStack, but if you have any questions, do not hesitate to ask. Use the following resources to get OpenStack support, and troubleshoot your installations."
-msgstr ""
-
-#: ./doc/common/app_support.xml:15(title)
-msgid "Documentation"
-msgstr ""
-
-#: ./doc/common/app_support.xml:16(para)
-msgid "For the available OpenStack documentation, see <link href=\"http://docs.openstack.org\">docs.openstack.org</link>."
-msgstr ""
-
-#: ./doc/common/app_support.xml:19(para) ./doc/common/app_support.xml:393(para) ./doc/common/ch_getstart.xml:208(para)
-msgid "To provide feedback on documentation, join and use the <email>openstack-docs@lists.openstack.org</email> mailing list at <link href=\"http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs\">OpenStack Documentation Mailing List</link>, or <link href=\"https://bugs.launchpad.net/openstack-manuals/+filebug\">report a bug</link>."
-msgstr ""
-
-#: ./doc/common/app_support.xml:26(para)
-msgid "The following books explain how to install an OpenStack cloud and its associated components:"
-msgstr ""
-
-#: ./doc/common/app_support.xml:33(citetitle)
-msgid "Installation Guide for Debian 7.0"
-msgstr ""
-
-#: ./doc/common/app_support.xml:41(citetitle)
-msgid "Installation Guide for openSUSE and SUSE Linux Enterprise Server"
-msgstr ""
-
-#: ./doc/common/app_support.xml:49(citetitle)
-msgid "Installation Guide for Red Hat Enterprise Linux, CentOS, and Fedora"
-msgstr ""
-
-#: ./doc/common/app_support.xml:58(citetitle)
-msgid "Installation Guide for Ubuntu 12.04/14.04 (LTS)"
-msgstr ""
-
-#: ./doc/common/app_support.xml:63(para)
-msgid "The following books explain how to configure and run an OpenStack cloud:"
-msgstr ""
-
-#: ./doc/common/app_support.xml:70(citetitle)
-msgid "Cloud Administrator Guide"
-msgstr ""
-
-#: ./doc/common/app_support.xml:76(citetitle)
-msgid "Configuration Reference"
-msgstr ""
-
-#: ./doc/common/app_support.xml:82(citetitle)
-msgid "Operations Guide"
-msgstr ""
-
-#: ./doc/common/app_support.xml:88(citetitle)
-msgid "High Availability Guide"
-msgstr ""
-
-#: ./doc/common/app_support.xml:94(citetitle)
-msgid "Security Guide"
-msgstr ""
-
-#: ./doc/common/app_support.xml:100(citetitle)
-msgid "Virtual Machine Image Guide"
-msgstr ""
-
-#: ./doc/common/app_support.xml:104(para)
-msgid "The following books explain how to use the OpenStack dashboard and command-line clients:"
-msgstr ""
-
-#: ./doc/common/app_support.xml:111(citetitle)
-msgid "API Quick Start"
-msgstr ""
-
-#: ./doc/common/app_support.xml:118(citetitle)
-msgid "End User Guide"
-msgstr ""
-
-#: ./doc/common/app_support.xml:125(citetitle)
-msgid "Admin User Guide"
-msgstr ""
-
-#: ./doc/common/app_support.xml:132(citetitle)
-msgid "Command-Line Interface Reference"
-msgstr ""
-
-#: ./doc/common/app_support.xml:136(para)
-msgid "The following documentation provides reference and guidance information for the OpenStack APIs:"
-msgstr ""
-
-#: ./doc/common/app_support.xml:142(link)
-msgid "OpenStack API Complete Reference (HTML)"
-msgstr ""
-
-#: ./doc/common/app_support.xml:148(link)
-msgid "API Complete Reference (PDF)"
-msgstr ""
-
-#: ./doc/common/app_support.xml:153(citetitle)
-msgid "OpenStack Block Storage Service API v2 Reference"
-msgstr ""
-
-#: ./doc/common/app_support.xml:160(citetitle)
-msgid "OpenStack Compute API v2 and Extensions Reference"
-msgstr ""
-
-#: ./doc/common/app_support.xml:167(citetitle)
-msgid "OpenStack Identity Service API v2.0 Reference"
-msgstr ""
-
-#: ./doc/common/app_support.xml:173(citetitle)
-msgid "OpenStack Image Service API v2 Reference"
-msgstr ""
-
-#: ./doc/common/app_support.xml:179(citetitle)
-msgid "OpenStack Networking API v2.0 Reference"
-msgstr ""
-
-#: ./doc/common/app_support.xml:185(citetitle)
-msgid "OpenStack Object Storage API v1 Reference"
-msgstr ""
-
-#: ./doc/common/app_support.xml:189(para)
-msgid "The <link href=\"http://docs.openstack.org/training-guides/content/\"><citetitle>Training Guides</citetitle></link> offer software training for cloud administration and management."
-msgstr ""
-
-#: ./doc/common/app_support.xml:196(title)
-msgid "ask.openstack.org"
-msgstr ""
-
-#: ./doc/common/app_support.xml:197(para)
-msgid "During the set up or testing of OpenStack, you might have questions about how a specific task is completed or be in a situation where a feature does not work correctly. Use the <link href=\"http://ask.openstack.org\">ask.openstack.org</link> site to ask questions and get answers. When you visit the <link href=\"http://ask.openstack.org\">http://ask.openstack.org</link> site, scan the recently asked questions to see whether your question has already been answered. If not, ask a new question. Be sure to give a clear, concise summary in the title and provide as much detail as possible in the description. Paste in your command output or stack traces, links to screen shots, and any other information which might be useful."
-msgstr ""
-
-#: ./doc/common/app_support.xml:214(title)
-msgid "OpenStack mailing lists"
-msgstr ""
-
-#: ./doc/common/app_support.xml:215(para)
-msgid "A great way to get answers and insights is to post your question or problematic scenario to the OpenStack mailing list. You can learn from and help others who might have similar issues. To subscribe or view the archives, go to <link href=\"http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack\">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</link>. You might be interested in the other mailing lists for specific projects or development, which you can find <link href=\"http://wiki.openstack.org/MailingLists\">on the wiki</link>. A description of all mailing lists is available at <link href=\"http://wiki.openstack.org/MailingLists\">http://wiki.openstack.org/MailingLists</link>."
-msgstr ""
-
-#: ./doc/common/app_support.xml:231(title)
-msgid "The OpenStack wiki"
-msgstr ""
-
-#: ./doc/common/app_support.xml:232(para)
-msgid "The <link href=\"http://wiki.openstack.org/\">OpenStack wiki</link> contains a broad range of topics but some of the information can be difficult to find or is a few pages deep. Fortunately, the wiki search feature enables you to search by title or content. If you search for specific information, such as about networking or nova, you can find a large amount of relevant material. More is being added all the time, so be sure to check back often. You can find the search box in the upper-right corner of any OpenStack wiki page."
-msgstr ""
-
-#: ./doc/common/app_support.xml:243(title)
-msgid "The Launchpad Bugs area"
-msgstr ""
-
-#: ./doc/common/app_support.xml:244(para)
-msgid "The OpenStack community values your set up and testing efforts and wants your feedback. To log a bug, you must sign up for a Launchpad account at <link href=\"https://launchpad.net/+login\">https://launchpad.net/+login</link>. You can view existing bugs and report bugs in the Launchpad Bugs area. Use the search feature to determine whether the bug has already been reported or already been fixed. If it still seems like your bug is unreported, fill out a bug report."
-msgstr ""
-
-#: ./doc/common/app_support.xml:252(para)
-msgid "Some tips:"
-msgstr ""
-
-#: ./doc/common/app_support.xml:255(para)
-msgid "Give a clear, concise summary."
-msgstr ""
-
-#: ./doc/common/app_support.xml:258(para)
-msgid "Provide as much detail as possible in the description. Paste in your command output or stack traces, links to screen shots, and any other information which might be useful."
-msgstr ""
-
-#: ./doc/common/app_support.xml:264(para)
-msgid "Be sure to include the software and package versions that you are using, especially if you are using a development branch, such as, <literal>\"Juno release\" vs git commit bc79c3ecc55929bac585d04a03475b72e06a3208</literal>."
-msgstr ""
-
-#: ./doc/common/app_support.xml:271(para)
-msgid "Any deployment-specific information is helpful, such as whether you are using Ubuntu 14.04 or are performing a multi-node installation."
-msgstr ""
-
-#: ./doc/common/app_support.xml:276(para)
-msgid "The following Launchpad Bugs areas are available:"
-msgstr ""
-
-#: ./doc/common/app_support.xml:282(link)
-msgid "Bugs: OpenStack Block Storage (cinder)"
-msgstr ""
-
-#: ./doc/common/app_support.xml:288(link)
-msgid "Bugs: OpenStack Compute (nova)"
-msgstr ""
-
-#: ./doc/common/app_support.xml:293(link)
-msgid "Bugs: OpenStack Dashboard (horizon)"
-msgstr ""
-
-#: ./doc/common/app_support.xml:299(link)
-msgid "Bugs: OpenStack Identity (keystone)"
-msgstr ""
-
-#: ./doc/common/app_support.xml:305(link)
-msgid "Bugs: OpenStack Image Service (glance)"
-msgstr ""
-
-#: ./doc/common/app_support.xml:311(link)
-msgid "Bugs: OpenStack Networking (neutron)"
-msgstr ""
-
-#: ./doc/common/app_support.xml:317(link)
-msgid "Bugs: OpenStack Object Storage (swift)"
-msgstr ""
-
-#: ./doc/common/app_support.xml:324(link)
-msgid "Bugs: Bare Metal (ironic)"
-msgstr ""
-
-#: ./doc/common/app_support.xml:329(link)
-msgid "Bugs: Data Processing Service (sahara)"
-msgstr ""
-
-#: ./doc/common/app_support.xml:335(link)
-msgid "Bugs: Database Service (trove)"
-msgstr ""
-
-#: ./doc/common/app_support.xml:340(link)
-msgid "Bugs: Orchestration (heat)"
-msgstr ""
-
-#: ./doc/common/app_support.xml:345(link)
-msgid "Bugs: Telemetry (ceilometer)"
-msgstr ""
-
-#: ./doc/common/app_support.xml:350(link)
-msgid "Bugs: Queue Service (marconi)"
-msgstr ""
-
-#: ./doc/common/app_support.xml:356(link)
-msgid "Bugs: OpenStack API Documentation (developer.openstack.org)"
-msgstr ""
-
-#: ./doc/common/app_support.xml:362(link)
-msgid "Bugs: OpenStack Documentation (docs.openstack.org)"
-msgstr ""
-
-#: ./doc/common/app_support.xml:368(title)
-msgid "The OpenStack IRC channel"
-msgstr ""
-
-#: ./doc/common/app_support.xml:369(para)
-msgid "The OpenStack community lives in the #openstack IRC channel on the Freenode network. You can hang out, ask questions, or get immediate feedback for urgent and pressing issues. To install an IRC client or use a browser-based client, go to <link href=\"http://webchat.freenode.net\">http://webchat.freenode.net/</link>. You can also use Colloquy (Mac OS X, <link href=\"http://colloquy.info/\">http://colloquy.info/</link>), mIRC (Windows, <link href=\"http://www.mirc.com/\">http://www.mirc.com/</link>), or XChat (Linux). When you are in the IRC channel and want to share code or command output, the generally accepted method is to use a Paste Bin. The OpenStack project has one at <link href=\"http://paste.openstack.org\">http://paste.openstack.org</link>. Just paste your longer amounts of text or logs in the web form and you get a URL that you can paste into the channel. The OpenStack IRC channel is <literal>#openstack</literal> on <literal>irc.freenode.net</literal>. You can find a list of all OpenStack IRC channels at <link href=\"https://wiki.openstack.org/wiki/IRC\">https://wiki.openstack.org/wiki/IRC</link>."
-msgstr ""
-
-#: ./doc/common/app_support.xml:392(title)
-msgid "Documentation feedback"
-msgstr ""
-
-#: ./doc/common/app_support.xml:399(title)
-msgid "OpenStack distribution packages"
-msgstr ""
-
-#: ./doc/common/app_support.xml:400(para)
-msgid "The following Linux distributions provide community-supported packages for OpenStack:"
-msgstr ""
-
-#: ./doc/common/app_support.xml:404(emphasis)
-msgid "Debian:"
-msgstr ""
-
-#: ./doc/common/app_support.xml:407(link)
-msgid "http://wiki.debian.org/OpenStack"
-msgstr ""
-
-#: ./doc/common/app_support.xml:410(emphasis)
-msgid "CentOS, Fedora, and Red Hat Enterprise Linux:"
-msgstr ""
-
-#: ./doc/common/app_support.xml:413(link)
-msgid "http://openstack.redhat.com/"
-msgstr ""
-
-#: ./doc/common/app_support.xml:416(emphasis)
-msgid "openSUSE and SUSE Linux Enterprise Server:"
-msgstr ""
-
-#: ./doc/common/app_support.xml:420(link)
-msgid "http://en.opensuse.org/Portal:OpenStack"
-msgstr ""
-
-#: ./doc/common/app_support.xml:423(emphasis)
-msgid "Ubuntu:"
-msgstr ""
-
-#: ./doc/common/app_support.xml:426(link)
-msgid "https://wiki.ubuntu.com/ServerTeam/CloudArchive"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:7(title)
-msgid "Manage images"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:8(para)
-msgid "The cloud operator assigns roles to users. Roles determine who can upload and manage images. The operator might restrict image upload and management to only cloud administrators or operators."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:12(para)
-msgid "You can upload images through the <placeholder-1/> client or the Image Service API. You can also use the <placeholder-2/> client to list images, set and delete image metadata, delete images, and take a snapshot of a running instance to create an image. After you upload an image, you cannot change it."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:16(para)
-msgid "For details about image creation, see the <link href=\"http://docs.openstack.org/image-guide/content/\"><citetitle>Virtual Machine Image Guide</citetitle></link>."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:21(title)
-msgid "List or get details for images (glance)"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:22(para)
-msgid "To get a list of images and to then get further details about a single image, use <placeholder-1/> and <placeholder-2/>."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:74(para)
-msgid "When viewing a list of images, you can also use <placeholder-1/> to filter the list, as follows:"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:80(para)
-msgid "To store location metadata for images, which enables direct file access for a client, update the <filename>/etc/glance/glance.conf</filename> file with the following statements:"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:87(code)
-msgid "show_multiple_locations = True"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:90(para)
-msgid "<code>filesystem_store_metadata_file = <replaceable>filePath</replaceable></code>, where <replaceable>filePath</replaceable> points to a JSON file that defines the mount point for OpenStack images on your system and a unique ID. For example: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:102(para)
-msgid "After you restart the Image Service, you can use the following syntax to view the image's location information:"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:103(replaceable)
-msgid "imageID"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:104(para)
-msgid "For example, using the image ID shown above, you would issue the command as follows:"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:109(title)
-msgid "Create or update an image (glance)"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:110(para)
-msgid "To create an image, use <placeholder-1/>:"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:111(replaceable) ./doc/common/section_cli_glance_manage_images.xml:114(replaceable)
-msgid "imageName"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:112(para)
-msgid "To update an image by name or ID, use <placeholder-1/>:"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:116(para)
-msgid "The following table lists the optional arguments that you can use with the <placeholder-1/> and <placeholder-2/> commands to modify image properties. For more information, refer to Image Service chapter in the <link href=\"http://docs.openstack.org/cli-reference/content/index.html\">OpenStack Command-Line Interface Reference</link>."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:126(parameter)
-msgid "--name NAME"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:129(para)
-msgid "The name of the image."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:134(parameter)
-msgid "--disk-format DISK_FORMAT"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:137(para)
-msgid "The disk format of the image. Acceptable formats are ami, ari, aki, vhd, vmdk, raw, qcow2, vdi, and iso."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:143(parameter)
-msgid "--container-format CONTAINER_FORMAT"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:146(para)
-msgid "The container format of the image. Acceptable formats are ami, ari, aki, bare, and ovf."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:152(parameter)
-msgid "--owner TENANT_ID"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:155(para)
-msgid "The tenant who should own the image."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:160(parameter)
-msgid "--size SIZE"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:163(para)
-msgid "The size of image data, in bytes."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:168(parameter)
-msgid "--min-disk DISK_GB"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:171(para)
-msgid "The minimum size of the disk needed to boot the image, in gigabytes."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:177(parameter)
-msgid "--min-ram DISK_RAM"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:180(para)
-msgid "The minimum amount of RAM needed to boot the image, in megabytes."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:185(parameter)
-msgid "--location IMAGE_URL"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:188(para)
-msgid "The URL where the data for this image resides. For example, if the image data is stored in swift, you could specify <literal>swift://account:key@example.com/container/obj</literal>."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:195(parameter)
-msgid "--file FILE"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:198(para)
-msgid "Local file that contains the disk image to be uploaded during the update. Alternatively, you can pass images to the client through stdin."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:204(parameter)
-msgid "--checksum CHECKSUM"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:207(para)
-msgid "Hash of image data to use for verification."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:212(parameter)
-msgid "--copy-from IMAGE_URL"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:215(para)
-msgid "Similar to <parameter>--location</parameter> in usage, but indicates that the image server should immediately copy the data and store it in its configured image store."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:222(parameter)
-msgid "--is-public [True|False]"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:225(para)
-msgid "Makes an image accessible for all the tenants."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:230(parameter)
-msgid "--is-protected [True|False]"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:233(para)
-msgid "Prevents an image from being deleted."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:238(parameter)
-msgid "--property KEY=VALUE"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:241(para)
-msgid "Arbitrary property to associate with image. This option can be used multiple times."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:247(parameter)
-msgid "--purge-props"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:250(para)
-msgid "Deletes all image properties that are not explicitly set in the update request. Otherwise, those properties not referenced are preserved."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:256(parameter)
-msgid "--human-readable"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:259(para)
-msgid "Prints the image size in a human-friendly format."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:263(para)
-msgid "The following example shows the command that you would use to upload a CentOS 6.3 image in qcow2 format and configure it for public access:"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:267(para)
-msgid "The following example shows how to update an existing image with a properties that describe the disk bus, the CD-ROM bus, and the VIF model:"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:274(para)
-msgid "Currently the libvirt virtualization tool determines the disk, CD-ROM, and VIF device models based on the configured hypervisor type (<literal>libvirt_type</literal> in <filename>/etc/nova/nova.conf</filename>). For the sake of optimal performance, libvirt defaults to using virtio for both disk and VIF (NIC) models. The disadvantage of this approach is that it is not possible to run operating systems that lack virtio drivers, for example, BSD, Solaris, and older versions of Linux and Windows."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:280(para)
-msgid "If you specify a disk or CD-ROM bus model that is not supported, see <xref linkend=\"bus_models\"/>. If you specify a VIF model that is not supported, the instance fails to launch. See <xref linkend=\"vif_models\"/>."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:284(para)
-msgid "The valid model values depend on the <literal>libvirt_type</literal> setting, as shown in the following tables."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:287(caption)
-msgid "Disk and CD-ROM bus model values"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:292(th) ./doc/common/section_cli_glance_manage_images.xml:336(th)
-msgid "libvirt_type setting"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:293(th) ./doc/common/section_cli_glance_manage_images.xml:337(th)
-msgid "Supported model values"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:298(td) ./doc/common/section_cli_glance_manage_images.xml:342(td)
-msgid "qemu or kvm"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:303(para) ./doc/common/section_cli_glance_manage_images.xml:320(para)
-msgid "ide"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:306(para)
-msgid "scsi"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:309(para) ./doc/common/section_cli_glance_manage_images.xml:359(para)
-msgid "virtio"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:316(td) ./doc/common/section_cli_glance_manage_images.xml:323(para) ./doc/common/section_cli_glance_manage_images.xml:366(td)
-msgid "xen"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:331(caption)
-msgid "VIF model values"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:347(para) ./doc/common/section_cli_glance_manage_images.xml:370(para)
-msgid "e1000"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:350(para) ./doc/common/section_cli_glance_manage_images.xml:376(para)
-msgid "ne2k_pci"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:353(para) ./doc/common/section_cli_glance_manage_images.xml:379(para)
-msgid "pcnet"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:356(para) ./doc/common/section_cli_glance_manage_images.xml:382(para)
-msgid "rtl8139"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:373(para)
-msgid "netfront"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:388(td)
-msgid "vmware"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:393(para)
-msgid "VirtualE1000"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:396(para)
-msgid "VirtualPCNet32"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:399(para)
-msgid "VirtualVmxnet"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:410(title) ./doc/common/section_cli_nova_images.xml:125(title)
-msgid "Troubleshoot image creation"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:411(para)
-msgid "If you encounter problems in creating an image in Image Service or Compute, the following information may help you troubleshoot the creation process."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:415(para)
-msgid "Ensure that the version of qemu you are using is version 0.14 or later. Earlier versions of qemu result in an <literal>unknown option -s</literal> error message in the <filename>nova-compute.log</filename> file."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml:420(para) ./doc/common/section_cli_nova_images.xml:140(para)
-msgid "Examine the <filename>/var/log/nova-api.log</filename> and <filename>/var/log/nova-compute.log</filename> log files for error messages."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_manage_images.xml:6(title)
-msgid "Create an image (nova)"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_manage_images.xml:7(para)
-msgid "You can use the <placeholder-1/> client to take a snapshot of a running instance to create an image."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_manage_images.xml:9(para)
-msgid "To minimize the potential for data loss and ensure that you create an accurate image, you should shut down the instance before you take a snapshot."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_manage_images.xml:12(para)
-msgid "You cannot create a snapshot from an instance that has an attached volume. Detach the volume, create the image, and remount the volume."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_manage_images.xml:17(para) ./doc/common/section_cli_nova_images.xml:18(para)
-msgid "Write any buffered data to disk."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_manage_images.xml:18(para)
-msgid "For more information, see <link href=\"http://docs.openstack.org/trunk/openstack-ops/content/snapshots.html\">Taking Snapshots</link> in the <citetitle>OpenStack Operations Guide</citetitle>."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_manage_images.xml:24(para)
-msgid "List instances to get the server name:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_manage_images.xml:31(para)
-msgid "In this example, the server is named <literal>myCirrosServer</literal>."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_manage_images.xml:33(para)
-msgid "Use this server to create a snapshot: <placeholder-1/>The command creates a qemu snapshot and automatically uploads the image to your repository. Only the tenant that creates the image has access to it."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_manage_images.xml:40(para) ./doc/common/section_cli_nova_images.xml:43(para)
-msgid "Get details for your image to check its status:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_manage_images.xml:75(para) ./doc/common/section_cli_nova_images.xml:79(para)
-msgid "The image status changes from <literal>SAVING</literal> to <literal>ACTIVE</literal>. Only the tenant who creates the image has access to it."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_manage_images.xml:81(para)
-msgid "To launch an instance from your image, include the image ID and flavor ID, as in the following example:"
-msgstr ""
-
 #. When image changes, this message will be marked fuzzy or untranslated for you.
 #. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_compute-configure-vnc.xml:63(None)
-msgid "@@image: '../common/figures/novnc/SCH_5009_V00_NUAC-VNC_OpenStack.png'; md5=182dc38019a220c851e1c94aa50f4565"
+#: ./doc/common/section_getstart_dashboard.xml:14(None)
+msgid "@@image: 'figures/horizon-screenshot.jpg'; md5=9471047adf0d93713be7f54b9db2b53c"
 msgstr ""
 
-#: ./doc/common/section_compute-configure-vnc.xml:6(title)
-msgid "VNC console proxy"
+#: ./doc/common/section_getstart_dashboard.xml:5(title)
+msgid "OpenStack dashboard"
 msgstr ""
 
-#: ./doc/common/section_compute-configure-vnc.xml:7(para)
-msgid "The VNC proxy is an OpenStack component that enables compute service users to access their instances through VNC clients."
+#: ./doc/common/section_getstart_dashboard.xml:6(para)
+msgid "The OpenStack dashboard is a modular <link href=\"https://www.djangoproject.com/\">Django web application</link> that provides a graphical interface to OpenStack services."
 msgstr ""
 
-#: ./doc/common/section_compute-configure-vnc.xml:10(para)
-msgid "The VNC console connection works as follows:"
+#: ./doc/common/section_getstart_dashboard.xml:18(para)
+msgid "The dashboard is usually deployed through <link href=\"http://code.google.com/p/modwsgi/\">mod_wsgi</link> in Apache. You can modify the dashboard code to make it suitable for different sites."
 msgstr ""
 
-#: ./doc/common/section_compute-configure-vnc.xml:13(para)
-msgid "A user connects to the API and gets an <literal>access_url</literal> such as, <literal>http://<replaceable>ip:port</replaceable>/?token=xyz</literal>."
+#: ./doc/common/section_getstart_dashboard.xml:22(para)
+msgid "From a network architecture point of view, this service must be accessible to customers and the public API for each OpenStack service. To use the administrator functionality for other services, it must also connect to Admin API endpoints, which should not be accessible by customers."
 msgstr ""
 
-#: ./doc/common/section_compute-configure-vnc.xml:19(para)
-msgid "The user pastes the URL in a browser or uses it as a client parameter."
+#: ./doc/common/section_cli_nova_reboot.xml:5(title)
+msgid "Reboot an instance"
 msgstr ""
 
-#: ./doc/common/section_compute-configure-vnc.xml:23(para)
-msgid "The browser or client connects to the proxy."
+#: ./doc/common/section_cli_nova_reboot.xml:6(para)
+msgid "You can soft or hard reboot a running instance. A soft reboot attempts a graceful shut down and restart of the instance. A hard reboot power cycles the instance."
 msgstr ""
 
-#: ./doc/common/section_compute-configure-vnc.xml:26(para)
-msgid "The proxy talks to <systemitem class=\"service\">nova-consoleauth</systemitem> to authorize the token for the user, and maps the token to the <emphasis>private</emphasis> host and port of the VNC server for an instance."
+#: ./doc/common/section_cli_nova_reboot.xml:9(para)
+msgid "By default, when you reboot a server, it is a soft reboot."
 msgstr ""
 
-#: ./doc/common/section_compute-configure-vnc.xml:31(para)
-msgid "The compute host specifies the address that the proxy should use to connect through the <filename>nova.conf</filename> file option, <option>vncserver_proxyclient_address</option>. In this way, the VNC proxy works as a bridge between the public network and private host network."
+#: ./doc/common/section_cli_nova_reboot.xml:10(replaceable) ./doc/common/section_cli_nova_reboot.xml:12(replaceable)
+msgid "SERVER"
 msgstr ""
 
-#: ./doc/common/section_compute-configure-vnc.xml:39(para)
-msgid "The proxy initiates the connection to VNC server and continues to proxy until the session ends."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:43(para)
-msgid "The proxy also tunnels the VNC protocol over WebSockets so that the <systemitem>noVNC</systemitem> client can talk to VNC servers. In general, the VNC proxy:"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:48(para)
-msgid "Bridges between the public network where the clients live and the private network where VNC servers live."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:52(para)
-msgid "Mediates token authentication."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:55(para)
-msgid "Transparently deals with hypervisor-specific connection details to provide a uniform client experience."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:58(title)
-msgid "noVNC process"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:71(title)
-msgid "About nova-consoleauth"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:73(para)
-msgid "Both client proxies leverage a shared service to manage token authentication called <systemitem class=\"service\">nova-consoleauth</systemitem>. This service must be running for either proxy to work. Many proxies of either type can be run against a single <systemitem class=\"service\">nova-consoleauth</systemitem> service in a cluster configuration."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:80(para)
-msgid "Do not confuse the <systemitem class=\"service\">nova-consoleauth</systemitem> shared service with <literal>nova-console</literal>, which is a XenAPI-specific service that most recent VNC proxy architectures do not use."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:87(title)
-msgid "Typical deployment"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:88(para)
-msgid "A typical deployment has the following components:"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:91(para)
-msgid "A <systemitem class=\"service\">nova-consoleauth</systemitem> process. Typically runs on the controller host."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:96(para)
-msgid "One or more <systemitem class=\"service\">nova-novncproxy</systemitem> services. Supports browser-based noVNC clients. For simple deployments, this service typically runs on the same machine as <systemitem class=\"service\">nova-api</systemitem> because it operates as a proxy between the public network and the private compute host network."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:105(para)
-msgid "One or more <literal>nova-xvpvncproxy</literal> services. Supports the special Java client discussed here. For simple deployments, this service typically runs on the same machine as <systemitem class=\"service\">nova-api</systemitem> because it acts as a proxy between the public network and the private compute host network."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:114(para)
-msgid "One or more compute hosts. These compute hosts must have correctly configured options, as follows."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:120(title)
-msgid "VNC configuration options"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:121(para)
-msgid "To customize the VNC console, use the following configuration options:"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:124(para)
-msgid "To support <link href=\"http://docs.openstack.org/trunk/config-reference/content/configuring-openstack-compute-basics.html#section_configuring-compute-migrations\">live migration</link>, you cannot specify a specific IP address for <literal>vncserver_listen</literal>, because that IP address does not exist on the destination host."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:134(para)
-msgid "The <literal>vncserver_proxyclient_address</literal> defaults to <literal>127.0.0.1</literal>, which is the address of the compute host that Compute instructs proxies to use when connecting to instance servers."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:139(para)
-msgid "For all-in-one XenServer domU deployments, set this to 169.254.0.1."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:140(para)
-msgid "For multi-host XenServer domU deployments, set to a dom0 management IP on the same network as the proxies."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:142(para)
-msgid "For multi-host libvirt deployments, set to a host management IP on the same network as the proxies."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:150(title)
-msgid "nova-novncproxy (noVNC)"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:152(para)
-msgid "You must install the <package>noVNC</package> package, which contains the <systemitem class=\"service\">nova-novncproxy</systemitem> service. As root, run the following command:"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:156(para)
-msgid "The service starts automatically on installation."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:157(para)
-msgid "To restart the service, run:"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:159(para)
-msgid "The configuration option parameter should point to your <filename>nova.conf</filename> file, which includes the message queue server address and credentials."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:162(para)
-msgid "By default, <systemitem class=\"service\">nova-novncproxy</systemitem> binds on <literal>0.0.0.0:6080</literal>."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:165(para)
-msgid "To connect the service to your Compute deployment, add the following configuration options to your <filename>nova.conf</filename> file:"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:169(para)
-msgid "<literal>vncserver_listen</literal>=<replaceable>0.0.0.0</replaceable>"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:172(para)
-msgid "Specifies the address on which the VNC service should bind. Make sure it is assigned one of the compute node interfaces. This address is the one used by your domain file."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:178(para)
-msgid "To use live migration, use the <replaceable>0.0.0.0</replaceable> address."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:183(para)
-msgid "<literal>vncserver_proxyclient_address</literal>=<replaceable>127.0.0.1</replaceable>"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:186(para)
-msgid "The address of the compute host that Compute instructs proxies to use when connecting to instance <literal>vncservers</literal>."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:193(title)
-msgid "Frequently asked questions about VNC access to virtual machines"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:199(literal)
-msgid "nova-xvpvncproxy"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:200(systemitem)
-msgid "nova-novncproxy"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:198(emphasis)
-msgid "Q: What is the difference between <placeholder-1/> and <placeholder-2/>?"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:202(para)
-msgid "A: <literal>nova-xvpvncproxy</literal>, which ships with OpenStack Compute, is a proxy that supports a simple Java client. <systemitem class=\"service\">nova-novncproxy</systemitem> uses noVNC to provide VNC support through a web browser."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:208(emphasis)
-msgid "Q: I want VNC support in the OpenStack dashboard. What services do I need?"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:210(para)
-msgid "A: You need <systemitem class=\"service\">nova-novncproxy</systemitem>, <systemitem class=\"service\">nova-consoleauth</systemitem>, and correctly configured compute hosts."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:216(emphasis)
-msgid "Q: When I use <placeholder-1/> or click on the VNC tab of the OpenStack dashboard, it hangs. Why?"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:218(para)
-msgid "A: Make sure you are running <systemitem class=\"service\">nova-consoleauth</systemitem> (in addition to <systemitem class=\"service\">nova-novncproxy</systemitem>). The proxies rely on <systemitem class=\"service\">nova-consoleauth</systemitem> to validate tokens, and waits for a reply from them until a timeout is reached."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:227(emphasis)
-msgid "Q: My VNC proxy worked fine during my all-in-one test, but now it doesn't work on multi host. Why?"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:230(para)
-msgid "A: The default options work for an all-in-one install, but changes must be made on your compute hosts once you start to build a cluster. As an example, suppose you have two servers:"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:236(para)
-msgid "Your <systemitem class=\"service\">nova-compute</systemitem> configuration file must set the following values:"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:248(para)
-msgid "<literal>novncproxy_base_url</literal> and <literal>xvpvncproxy_base_url</literal> use a public IP; this is the URL that is ultimately returned to clients, which generally do not have access to your private network. Your PROXYSERVER must be able to reach <literal>vncserver_proxyclient_address</literal>, because that is the address over which the VNC connection is proxied."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:260(emphasis)
-msgid "Q: My noVNC does not work with recent versions of web browsers. Why?"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:263(para)
-msgid "A: Make sure you have installed <literal>python-numpy</literal>, which is required to support a newer version of the WebSocket protocol (HyBi-07+)."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:270(emphasis)
-msgid "Q: How do I adjust the dimensions of the VNC window image in the OpenStack dashboard?"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:273(para)
-msgid "A: These values are hard-coded in a Django HTML template. To alter them, edit the <filename>_detail_vnc.html</filename> template file. The location of this file varies based on Linux distribution. On Ubuntu 12.04, the file is at <filename>/usr/share/pyshared/horizon/dashboards/nova/instances/templates/instances/_detail_vnc.html</filename>."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml:279(para)
-msgid "Modify the <option>width</option> and <option>height</option> options, as follows:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml:6(title)
-msgid "Change the size of your server"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml:7(para)
-msgid "You change the size of a server by changing its flavor."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml:10(para)
-msgid "Show information about your server, including its size, which is shown as the value of the flavor property."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml:43(para)
-msgid "The size (flavor) of the server is <literal>m1.small (2)</literal>."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml:46(para)
-msgid "List the available flavors with the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml:59(para)
-msgid "To resize the server, pass the server ID or name and the new flavor to the <placeholder-1/> command. Include the <literal>--poll</literal> parameter to report the resize progress."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml:67(para)
-msgid "Show the status for your server:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml:74(para)
-msgid "When the resize completes, the status becomes VERIFY_RESIZE."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml:77(para)
-msgid "Confirm the resize:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml:79(para) ./doc/common/section_cli_nova_resizerebuild.xml:85(para)
-msgid "The server status becomes ACTIVE."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml:82(para)
-msgid "If the resize fails or does not work as expected, you can revert the resize:"
+#: ./doc/common/section_cli_nova_reboot.xml:11(para)
+msgid "To perform a hard reboot, pass the <parameter>--hard</parameter> parameter, as follows:"
 msgstr ""
 
 #: ./doc/common/ch_cli_nova_commands.xml:11(title)
@@ -959,15 +59,15 @@ msgstr ""
 msgid "The <placeholder-1/> client is the command-line interface (CLI) for the OpenStack Compute API and its extensions. This chapter documents <placeholder-2/> version 2.17.0."
 msgstr ""
 
-#: ./doc/common/ch_cli_nova_commands.xml:16(para) ./doc/common/ch_cli_ceilometer_commands.xml:16(para) ./doc/common/ch_cli_neutron_commands.xml:16(para) ./doc/common/ch_cli_keystone_commands.xml:16(para) ./doc/common/ch_cli_swift_commands.xml:16(para) ./doc/common/ch_cli_cinder_commands.xml:16(para) ./doc/common/ch_cli_glance_commands.xml:16(para) ./doc/common/ch_cli_heat_commands.xml:16(para) ./doc/common/ch_cli_trove_commands.xml:16(para)
+#: ./doc/common/ch_cli_nova_commands.xml:16(para) ./doc/common/ch_cli_neutron_commands.xml:16(para) ./doc/common/ch_cli_heat_commands.xml:16(para) ./doc/common/ch_cli_swift_commands.xml:16(para) ./doc/common/ch_cli_glance_commands.xml:16(para) ./doc/common/ch_cli_keystone_commands.xml:16(para) ./doc/common/ch_cli_ceilometer_commands.xml:16(para) ./doc/common/ch_cli_cinder_commands.xml:16(para) ./doc/common/ch_cli_trove_commands.xml:16(para)
 msgid "For help on a specific <placeholder-1/> command, enter:"
 msgstr ""
 
-#: ./doc/common/ch_cli_nova_commands.xml:19(option) ./doc/common/ch_cli_ceilometer_commands.xml:19(option) ./doc/common/ch_cli_neutron_commands.xml:19(option) ./doc/common/ch_cli_keystone_commands.xml:19(option) ./doc/common/ch_cli_swift_commands.xml:19(option) ./doc/common/ch_cli_cinder_commands.xml:19(option) ./doc/common/ch_cli_glance_commands.xml:19(option) ./doc/common/ch_cli_heat_commands.xml:19(option) ./doc/common/ch_cli_trove_commands.xml:19(option)
+#: ./doc/common/ch_cli_nova_commands.xml:19(option) ./doc/common/ch_cli_neutron_commands.xml:19(option) ./doc/common/ch_cli_heat_commands.xml:19(option) ./doc/common/ch_cli_swift_commands.xml:19(option) ./doc/common/ch_cli_glance_commands.xml:19(option) ./doc/common/ch_cli_keystone_commands.xml:19(option) ./doc/common/ch_cli_ceilometer_commands.xml:19(option) ./doc/common/ch_cli_cinder_commands.xml:19(option) ./doc/common/ch_cli_trove_commands.xml:19(option)
 msgid "help"
 msgstr ""
 
-#: ./doc/common/ch_cli_nova_commands.xml:19(replaceable) ./doc/common/ch_cli_ceilometer_commands.xml:19(replaceable) ./doc/common/ch_cli_neutron_commands.xml:19(replaceable) ./doc/common/ch_cli_keystone_commands.xml:19(replaceable) ./doc/common/ch_cli_swift_commands.xml:19(replaceable) ./doc/common/section_cli_keystone_example_usage.xml:12(replaceable) ./doc/common/ch_cli_cinder_commands.xml:19(replaceable) ./doc/common/ch_cli_glance_commands.xml:19(replaceable) ./doc/common/ch_cli_heat_commands.xml:19(replaceable) ./doc/common/ch_cli_trove_commands.xml:19(replaceable)
+#: ./doc/common/ch_cli_nova_commands.xml:19(replaceable) ./doc/common/ch_cli_neutron_commands.xml:19(replaceable) ./doc/common/ch_cli_heat_commands.xml:19(replaceable) ./doc/common/ch_cli_swift_commands.xml:19(replaceable) ./doc/common/section_cli_keystone_example_usage.xml:12(replaceable) ./doc/common/ch_cli_glance_commands.xml:19(replaceable) ./doc/common/ch_cli_keystone_commands.xml:19(replaceable) ./doc/common/ch_cli_ceilometer_commands.xml:19(replaceable) ./doc/common/ch_cli_cinder_commands.xml:19(replaceable) ./doc/common/ch_cli_trove_commands.xml:19(replaceable)
 msgid "COMMAND"
 msgstr ""
 
@@ -975,7 +75,7 @@ msgstr ""
 msgid "nova usage"
 msgstr ""
 
-#: ./doc/common/ch_cli_nova_commands.xml:37(title) ./doc/common/ch_cli_ceilometer_commands.xml:38(title) ./doc/common/ch_cli_keystone_commands.xml:37(title) ./doc/common/ch_cli_swift_commands.xml:37(title) ./doc/common/ch_cli_cinder_commands.xml:35(title) ./doc/common/ch_cli_glance_commands.xml:39(title) ./doc/common/ch_cli_heat_commands.xml:35(title) ./doc/common/ch_cli_trove_commands.xml:35(title)
+#: ./doc/common/ch_cli_nova_commands.xml:37(title) ./doc/common/ch_cli_heat_commands.xml:35(title) ./doc/common/ch_cli_swift_commands.xml:37(title) ./doc/common/ch_cli_glance_commands.xml:39(title) ./doc/common/ch_cli_keystone_commands.xml:37(title) ./doc/common/ch_cli_ceilometer_commands.xml:38(title) ./doc/common/ch_cli_cinder_commands.xml:35(title) ./doc/common/ch_cli_trove_commands.xml:35(title)
 msgid "Subcommands"
 msgstr ""
 
@@ -1607,7 +707,7 @@ msgstr ""
 msgid "Prints all of the commands and options to stdout so that the nova.bash_completion script doesn't have to hard code them."
 msgstr ""
 
-#: ./doc/common/ch_cli_nova_commands.xml:1326(para) ./doc/common/ch_cli_ceilometer_commands.xml:261(para) ./doc/common/ch_cli_keystone_commands.xml:332(para) ./doc/common/ch_cli_cinder_commands.xml:575(para) ./doc/common/ch_cli_glance_commands.xml:203(para) ./doc/common/ch_cli_heat_commands.xml:311(para)
+#: ./doc/common/ch_cli_nova_commands.xml:1326(para) ./doc/common/ch_cli_heat_commands.xml:311(para) ./doc/common/ch_cli_glance_commands.xml:203(para) ./doc/common/ch_cli_keystone_commands.xml:332(para) ./doc/common/ch_cli_ceilometer_commands.xml:261(para) ./doc/common/ch_cli_cinder_commands.xml:575(para)
 msgid "Display help about this program or one of its subcommands."
 msgstr ""
 
@@ -1703,7 +803,7 @@ msgstr ""
 msgid "nova optional arguments"
 msgstr ""
 
-#: ./doc/common/ch_cli_nova_commands.xml:1519(para) ./doc/common/ch_cli_ceilometer_commands.xml:275(para) ./doc/common/ch_cli_neutron_commands.xml:38(para) ./doc/common/ch_cli_swift_commands.xml:115(para) ./doc/common/ch_cli_cinder_commands.xml:597(para) ./doc/common/ch_cli_glance_commands.xml:217(para) ./doc/common/ch_cli_trove_commands.xml:446(para)
+#: ./doc/common/ch_cli_nova_commands.xml:1519(para) ./doc/common/ch_cli_neutron_commands.xml:38(para) ./doc/common/ch_cli_swift_commands.xml:115(para) ./doc/common/ch_cli_glance_commands.xml:217(para) ./doc/common/ch_cli_ceilometer_commands.xml:275(para) ./doc/common/ch_cli_cinder_commands.xml:597(para) ./doc/common/ch_cli_trove_commands.xml:446(para)
 msgid "show program's version number and exit"
 msgstr ""
 
@@ -1727,27 +827,27 @@ msgstr ""
 msgid "Defaults to <code>env[OS_AUTH_TOKEN]</code>"
 msgstr ""
 
-#: ./doc/common/ch_cli_nova_commands.xml:1568(para) ./doc/common/ch_cli_ceilometer_commands.xml:357(para) ./doc/common/ch_cli_cinder_commands.xml:613(para) ./doc/common/ch_cli_heat_commands.xml:399(para) ./doc/common/ch_cli_trove_commands.xml:462(para)
+#: ./doc/common/ch_cli_nova_commands.xml:1568(para) ./doc/common/ch_cli_heat_commands.xml:399(para) ./doc/common/ch_cli_ceilometer_commands.xml:357(para) ./doc/common/ch_cli_cinder_commands.xml:613(para) ./doc/common/ch_cli_trove_commands.xml:462(para)
 msgid "Defaults to <code>env[OS_USERNAME]</code>."
 msgstr ""
 
-#: ./doc/common/ch_cli_nova_commands.xml:1576(para) ./doc/common/ch_cli_ceilometer_commands.xml:365(para) ./doc/common/ch_cli_cinder_commands.xml:621(para) ./doc/common/ch_cli_heat_commands.xml:407(para) ./doc/common/ch_cli_trove_commands.xml:470(para)
+#: ./doc/common/ch_cli_nova_commands.xml:1576(para) ./doc/common/ch_cli_heat_commands.xml:407(para) ./doc/common/ch_cli_ceilometer_commands.xml:365(para) ./doc/common/ch_cli_cinder_commands.xml:621(para) ./doc/common/ch_cli_trove_commands.xml:470(para)
 msgid "Defaults to <code>env[OS_PASSWORD]</code>."
 msgstr ""
 
-#: ./doc/common/ch_cli_nova_commands.xml:1584(para) ./doc/common/ch_cli_ceilometer_commands.xml:381(para) ./doc/common/ch_cli_cinder_commands.xml:629(para) ./doc/common/ch_cli_heat_commands.xml:423(para) ./doc/common/ch_cli_trove_commands.xml:478(para)
+#: ./doc/common/ch_cli_nova_commands.xml:1584(para) ./doc/common/ch_cli_heat_commands.xml:423(para) ./doc/common/ch_cli_ceilometer_commands.xml:381(para) ./doc/common/ch_cli_cinder_commands.xml:629(para) ./doc/common/ch_cli_trove_commands.xml:478(para)
 msgid "Defaults to <code>env[OS_TENANT_NAME]</code>."
 msgstr ""
 
-#: ./doc/common/ch_cli_nova_commands.xml:1592(para) ./doc/common/ch_cli_ceilometer_commands.xml:373(para) ./doc/common/ch_cli_cinder_commands.xml:637(para) ./doc/common/ch_cli_heat_commands.xml:415(para) ./doc/common/ch_cli_trove_commands.xml:486(para)
+#: ./doc/common/ch_cli_nova_commands.xml:1592(para) ./doc/common/ch_cli_heat_commands.xml:415(para) ./doc/common/ch_cli_ceilometer_commands.xml:373(para) ./doc/common/ch_cli_cinder_commands.xml:637(para) ./doc/common/ch_cli_trove_commands.xml:486(para)
 msgid "Defaults to <code>env[OS_TENANT_ID]</code>."
 msgstr ""
 
-#: ./doc/common/ch_cli_nova_commands.xml:1600(para) ./doc/common/ch_cli_ceilometer_commands.xml:389(para) ./doc/common/ch_cli_cinder_commands.xml:645(para) ./doc/common/ch_cli_heat_commands.xml:431(para) ./doc/common/ch_cli_trove_commands.xml:494(para)
+#: ./doc/common/ch_cli_nova_commands.xml:1600(para) ./doc/common/ch_cli_heat_commands.xml:431(para) ./doc/common/ch_cli_ceilometer_commands.xml:389(para) ./doc/common/ch_cli_cinder_commands.xml:645(para) ./doc/common/ch_cli_trove_commands.xml:494(para)
 msgid "Defaults to <code>env[OS_AUTH_URL]</code>."
 msgstr ""
 
-#: ./doc/common/ch_cli_nova_commands.xml:1608(para) ./doc/common/ch_cli_ceilometer_commands.xml:397(para) ./doc/common/ch_cli_cinder_commands.xml:653(para) ./doc/common/ch_cli_heat_commands.xml:439(para) ./doc/common/ch_cli_trove_commands.xml:502(para)
+#: ./doc/common/ch_cli_nova_commands.xml:1608(para) ./doc/common/ch_cli_heat_commands.xml:439(para) ./doc/common/ch_cli_ceilometer_commands.xml:397(para) ./doc/common/ch_cli_cinder_commands.xml:653(para) ./doc/common/ch_cli_trove_commands.xml:502(para)
 msgid "Defaults to <code>env[OS_REGION_NAME]</code>."
 msgstr ""
 
@@ -1791,7 +891,7 @@ msgstr ""
 msgid "nova absolute-limits command"
 msgstr ""
 
-#: ./doc/common/ch_cli_nova_commands.xml:1698(title) ./doc/common/ch_cli_nova_commands.xml:1848(title) ./doc/common/ch_cli_nova_commands.xml:2149(title) ./doc/common/ch_cli_nova_commands.xml:2265(title) ./doc/common/ch_cli_nova_commands.xml:2372(title) ./doc/common/ch_cli_nova_commands.xml:2567(title) ./doc/common/ch_cli_nova_commands.xml:2678(title) ./doc/common/ch_cli_nova_commands.xml:2695(title) ./doc/common/ch_cli_nova_commands.xml:2773(title) ./doc/common/ch_cli_nova_commands.xml:2803(title) ./doc/common/ch_cli_nova_commands.xml:2832(title) ./doc/common/ch_cli_nova_commands.xml:2910(title) ./doc/common/ch_cli_nova_commands.xml:2962(title) ./doc/common/ch_cli_nova_commands.xml:3065(title) ./doc/common/ch_cli_nova_commands.xml:3161(title) ./doc/common/ch_cli_nova_commands.xml:3252(title) ./doc/common/ch_cli_nova_commands.xml:3314(title) ./doc/common/ch_cli_nova_commands.xml:3343(title) ./doc/common/ch_cli_nova_commands.xml:3385(title) ./doc/common/ch_cli_nova_commands.xml:3606(title) ./doc/common/ch_cli_nova_commands.xml:3652(title) ./doc/common/ch_cli_nova_commands.xml:3678(title) ./doc/common/ch_cli_nova_commands.xml:3759(title) ./doc/common/ch_cli_nova_commands.xml:3784(title) ./doc/common/ch_cli_nova_commands.xml:3878(title) ./doc/common/ch_cli_nova_commands.xml:3920(title) ./doc/common/ch_cli_nova_commands.xml:4043(title) ./doc/common/ch_cli_nova_commands.xml:4129(title) ./doc/common/ch_cli_nova_commands.xml:4192(title) ./doc/common/ch_cli_nova_commands.xml:4362(title) ./doc/common/ch_cli_nova_commands.xml:4449(title) ./doc/common/ch_cli_nova_commands.xml:4467(title) ./doc/common/ch_cli_nova_commands.xml:4629(title) ./doc/common/ch_cli_nova_commands.xml:4773(title) ./doc/common/ch_cli_nova_commands.xml:4874(title) ./doc/common/ch_cli_nova_commands.xml:4971(title) ./doc/common/ch_cli_nova_commands.xml:4988(title) ./doc/common/ch_cli_nova_commands.xml:5013(title) ./doc/common/ch_cli_nova_commands.xml:5061(title) ./doc/common/ch_cli_nova_commands.xml:5201(title) ./doc/common/ch_cli_nova_commands.xml:5247(title) ./doc/common/ch_cli_nova_commands.xml:5428(title) ./doc/common/ch_cli_nova_commands.xml:5465(title) ./doc/common/ch_cli_nova_commands.xml:5826(title) ./doc/common/ch_cli_nova_commands.xml:5912(title) ./doc/common/ch_cli_nova_commands.xml:5954(title) ./doc/common/ch_cli_nova_commands.xml:6024(title) ./doc/common/ch_cli_nova_commands.xml:6054(title) ./doc/common/ch_cli_nova_commands.xml:6236(title) ./doc/common/ch_cli_nova_commands.xml:6271(title) ./doc/common/ch_cli_nova_commands.xml:6347(title) ./doc/common/ch_cli_nova_commands.xml:6448(title) ./doc/common/ch_cli_nova_commands.xml:6496(title) ./doc/common/ch_cli_ceilometer_commands.xml:462(title) ./doc/common/ch_cli_ceilometer_commands.xml:604(title) ./doc/common/ch_cli_ceilometer_commands.xml:749(title) ./doc/common/ch_cli_ceilometer_commands.xml:766(title) ./doc/common/ch_cli_ceilometer_commands.xml:793(title) ./doc/common/ch_cli_ceilometer_commands.xml:812(title) ./doc/common/ch_cli_ceilometer_commands.xml:829(title) ./doc/common/ch_cli_ceilometer_commands.xml:846(title) ./doc/common/ch_cli_ceilometer_commands.xml:887(title) ./doc/common/ch_cli_ceilometer_commands.xml:1077(title) ./doc/common/ch_cli_ceilometer_commands.xml:1282(title) ./doc/common/ch_cli_ceilometer_commands.xml:1471(title) ./doc/common/ch_cli_ceilometer_commands.xml:1490(title) ./doc/common/ch_cli_ceilometer_commands.xml:1514(title) ./doc/common/ch_cli_ceilometer_commands.xml:1534(title) ./doc/common/ch_cli_ceilometer_commands.xml:1570(title) ./doc/common/ch_cli_ceilometer_commands.xml:1606(title) ./doc/common/ch_cli_ceilometer_commands.xml:1642(title) ./doc/common/ch_cli_ceilometer_commands.xml:1661(title) ./doc/common/ch_cli_ceilometer_commands.xml:1684(title) ./doc/common/ch_cli_ceilometer_commands.xml:1767(title) ./doc/common/ch_cli_ceilometer_commands.xml:1803(title) ./doc/common/ch_cli_ceilometer_commands.xml:1856(title) ./doc/common/ch_cli_ceilometer_commands.xml:1874(title) ./doc/common/ch_cli_neutron_commands.xml:1434(title) ./doc/common/ch_cli_neutron_commands.xml:1461(title) ./doc/common/ch_cli_neutron_commands.xml:1517(title) ./doc/common/ch_cli_neutron_commands.xml:1570(title) ./doc/common/ch_cli_neutron_commands.xml:1620(title) ./doc/common/ch_cli_neutron_commands.xml:1681(title) ./doc/common/ch_cli_neutron_commands.xml:1709(title) ./doc/common/ch_cli_neutron_commands.xml:1766(title) ./doc/common/ch_cli_neutron_commands.xml:1838(title) ./doc/common/ch_cli_neutron_commands.xml:1925(title) ./doc/common/ch_cli_neutron_commands.xml:1953(title) ./doc/common/ch_cli_neutron_commands.xml:2011(title) ./doc/common/ch_cli_neutron_commands.xml:2065(title) ./doc/common/ch_cli_neutron_commands.xml:2093(title) ./doc/common/ch_cli_neutron_commands.xml:2151(title) ./doc/common/ch_cli_neutron_commands.xml:2205(title) ./doc/common/ch_cli_neutron_commands.xml:2245(title) ./doc/common/ch_cli_neutron_commands.xml:2307(title) ./doc/common/ch_cli_neutron_commands.xml:2352(title) ./doc/common/ch_cli_neutron_commands.xml:2379(title) ./doc/common/ch_cli_neutron_commands.xml:2435(title) ./doc/common/ch_cli_neutron_commands.xml:2494(title) ./doc/common/ch_cli_neutron_commands.xml:2570(title) ./doc/common/ch_cli_neutron_commands.xml:2599(title) ./doc/common/ch_cli_neutron_commands.xml:2689(title) ./doc/common/ch_cli_neutron_commands.xml:2767(title) ./doc/common/ch_cli_neutron_commands.xml:2814(title) ./doc/common/ch_cli_neutron_commands.xml:2859(title) ./doc/common/ch_cli_neutron_commands.xml:2951(title) ./doc/common/ch_cli_neutron_commands.xml:2991(title) ./doc/common/ch_cli_neutron_commands.xml:3045(title) ./doc/common/ch_cli_neutron_commands.xml:3080(title) ./doc/common/ch_cli_neutron_commands.xml:3206(title) ./doc/common/ch_cli_neutron_commands.xml:3235(title) ./doc/common/ch_cli_neutron_commands.xml:3322(title) ./doc/common/ch_cli_neutron_commands.xml:3377(title) ./doc/common/ch_cli_neutron_commands.xml:3424(title) ./doc/common/ch_cli_neutron_commands.xml:3477(title) ./doc/common/ch_cli_neutron_commands.xml:3524(title) ./doc/common/ch_cli_neutron_commands.xml:3574(title) ./doc/common/ch_cli_neutron_commands.xml:3635(title) ./doc/common/ch_cli_neutron_commands.xml:3672(title) ./doc/common/ch_cli_neutron_commands.xml:3701(title) ./doc/common/ch_cli_neutron_commands.xml:3787(title) ./doc/common/ch_cli_neutron_commands.xml:3844(title) ./doc/common/ch_cli_neutron_commands.xml:4000(title) ./doc/common/ch_cli_neutron_commands.xml:4030(title) ./doc/common/ch_cli_neutron_commands.xml:4118(title) ./doc/common/ch_cli_neutron_commands.xml:4173(title) ./doc/common/ch_cli_neutron_commands.xml:4227(title) ./doc/common/ch_cli_neutron_commands.xml:4289(title) ./doc/common/ch_cli_neutron_commands.xml:4334(title) ./doc/common/ch_cli_neutron_commands.xml:4376(title) ./doc/common/ch_cli_neutron_commands.xml:4439(title) ./doc/common/ch_cli_neutron_commands.xml:4473(title) ./doc/common/ch_cli_neutron_commands.xml:4592(title) ./doc/common/ch_cli_neutron_commands.xml:4639(title) ./doc/common/ch_cli_neutron_commands.xml:4668(title) ./doc/common/ch_cli_neutron_commands.xml:4755(title) ./doc/common/ch_cli_neutron_commands.xml:4809(title) ./doc/common/ch_cli_neutron_commands.xml:4851(title) ./doc/common/ch_cli_neutron_commands.xml:4929(title) ./doc/common/ch_cli_neutron_commands.xml:4958(title) ./doc/common/ch_cli_neutron_commands.xml:5044(title) ./doc/common/ch_cli_neutron_commands.xml:5097(title) ./doc/common/ch_cli_neutron_commands.xml:5129(title) ./doc/common/ch_cli_neutron_commands.xml:5231(title) ./doc/common/ch_cli_neutron_commands.xml:5260(title) ./doc/common/ch_cli_neutron_commands.xml:5347(title) ./doc/common/ch_cli_neutron_commands.xml:5403(title) ./doc/common/ch_cli_neutron_commands.xml:5459(title) ./doc/common/ch_cli_neutron_commands.xml:5512(title) ./doc/common/ch_cli_neutron_commands.xml:5557(title) ./doc/common/ch_cli_neutron_commands.xml:5668(title) ./doc/common/ch_cli_neutron_commands.xml:5697(title) ./doc/common/ch_cli_neutron_commands.xml:5783(title) ./doc/common/ch_cli_neutron_commands.xml:5836(title) ./doc/common/ch_cli_neutron_commands.xml:5877(title) ./doc/common/ch_cli_neutron_commands.xml:5930(title) ./doc/common/ch_cli_neutron_commands.xml:5959(title) ./doc/common/ch_cli_neutron_commands.xml:6056(title) ./doc/common/ch_cli_neutron_commands.xml:6117(title) ./doc/common/ch_cli_neutron_commands.xml:6146(title) ./doc/common/ch_cli_neutron_commands.xml:6233(title) ./doc/common/ch_cli_neutron_commands.xml:6289(title) ./doc/common/ch_cli_neutron_commands.xml:6347(title) ./doc/common/ch_cli_neutron_commands.xml:6407(title) ./doc/common/ch_cli_neutron_commands.xml:6436(title) ./doc/common/ch_cli_neutron_commands.xml:6530(title) ./doc/common/ch_cli_neutron_commands.xml:6588(title) ./doc/common/ch_cli_neutron_commands.xml:6643(title) ./doc/common/ch_cli_neutron_commands.xml:6690(title) ./doc/common/ch_cli_neutron_commands.xml:6735(title) ./doc/common/ch_cli_neutron_commands.xml:6791(title) ./doc/common/ch_cli_neutron_commands.xml:6845(title) ./doc/common/ch_cli_neutron_commands.xml:6873(title) ./doc/common/ch_cli_neutron_commands.xml:6961(title) ./doc/common/ch_cli_neutron_commands.xml:7047(title) ./doc/common/ch_cli_neutron_commands.xml:7100(title) ./doc/common/ch_cli_neutron_commands.xml:7145(title) ./doc/common/ch_cli_neutron_commands.xml:7259(title) ./doc/common/ch_cli_neutron_commands.xml:7287(title) ./doc/common/ch_cli_neutron_commands.xml:7373(title) ./doc/common/ch_cli_neutron_commands.xml:7429(title) ./doc/common/ch_cli_neutron_commands.xml:7498(title) ./doc/common/ch_cli_neutron_commands.xml:7583(title) ./doc/common/ch_cli_neutron_commands.xml:7610(title) ./doc/common/ch_cli_neutron_commands.xml:7666(title) ./doc/common/ch_cli_neutron_commands.xml:7709(title) ./doc/common/ch_cli_neutron_commands.xml:7745(title) ./doc/common/ch_cli_neutron_commands.xml:7773(title) ./doc/common/ch_cli_neutron_commands.xml:7814(title) ./doc/common/ch_cli_neutron_commands.xml:7930(title) ./doc/common/ch_cli_neutron_commands.xml:7982(title) ./doc/common/ch_cli_neutron_commands.xml:8019(title) ./doc/common/ch_cli_neutron_commands.xml:8065(title) ./doc/common/ch_cli_neutron_commands.xml:8121(title) ./doc/common/ch_cli_neutron_commands.xml:8169(title) ./doc/common/ch_cli_neutron_commands.xml:8198(title) ./doc/common/ch_cli_neutron_commands.xml:8285(title) ./doc/common/ch_cli_neutron_commands.xml:8343(title) ./doc/common/ch_cli_neutron_commands.xml:8429(title) ./doc/common/ch_cli_neutron_commands.xml:8482(title) ./doc/common/ch_cli_neutron_commands.xml:8523(title) ./doc/common/ch_cli_neutron_commands.xml:8576(title) ./doc/common/ch_cli_neutron_commands.xml:8605(title) ./doc/common/ch_cli_neutron_commands.xml:8700(title) ./doc/common/ch_cli_neutron_commands.xml:8801(title) ./doc/common/ch_cli_neutron_commands.xml:8832(title) ./doc/common/ch_cli_neutron_commands.xml:8928(title) ./doc/common/ch_cli_neutron_commands.xml:8985(title) ./doc/common/ch_cli_neutron_commands.xml:9040(title) ./doc/common/ch_cli_neutron_commands.xml:9085(title) ./doc/common/ch_cli_neutron_commands.xml:9186(title) ./doc/common/ch_cli_neutron_commands.xml:9298(title) ./doc/common/ch_cli_neutron_commands.xml:9327(title) ./doc/common/ch_cli_neutron_commands.xml:9413(title) ./doc/common/ch_cli_neutron_commands.xml:9466(title) ./doc/common/ch_cli_neutron_commands.xml:9513(title) ./doc/common/ch_cli_neutron_commands.xml:9617(title) ./doc/common/ch_cli_neutron_commands.xml:9646(title) ./doc/common/ch_cli_neutron_commands.xml:9733(title) ./doc/common/ch_cli_neutron_commands.xml:9788(title) ./doc/common/ch_cli_neutron_commands.xml:9846(title) ./doc/common/ch_cli_neutron_commands.xml:9950(title) ./doc/common/ch_cli_neutron_commands.xml:9979(title) ./doc/common/ch_cli_neutron_commands.xml:10066(title) ./doc/common/ch_cli_neutron_commands.xml:10121(title) ./doc/common/ch_cli_neutron_commands.xml:10181(title) ./doc/common/ch_cli_neutron_commands.xml:10250(title) ./doc/common/ch_cli_neutron_commands.xml:10279(title) ./doc/common/ch_cli_neutron_commands.xml:10365(title) ./doc/common/ch_cli_neutron_commands.xml:10419(title) ./doc/common/ch_cli_swift_commands.xml:358(title) ./doc/common/ch_cli_swift_commands.xml:424(title) ./doc/common/ch_cli_swift_commands.xml:527(title) ./doc/common/ch_cli_swift_commands.xml:601(title) ./doc/common/ch_cli_swift_commands.xml:684(title) ./doc/common/ch_cli_swift_commands.xml:723(title) ./doc/common/ch_cli_cinder_commands.xml:751(title) ./doc/common/ch_cli_cinder_commands.xml:819(title) ./doc/common/ch_cli_cinder_commands.xml:871(title) ./doc/common/ch_cli_cinder_commands.xml:992(title) ./doc/common/ch_cli_cinder_commands.xml:1128(title) ./doc/common/ch_cli_cinder_commands.xml:1270(title) ./doc/common/ch_cli_cinder_commands.xml:1350(title) ./doc/common/ch_cli_cinder_commands.xml:1516(title) ./doc/common/ch_cli_cinder_commands.xml:1605(title) ./doc/common/ch_cli_cinder_commands.xml:1716(title) ./doc/common/ch_cli_cinder_commands.xml:1744(title) ./doc/common/ch_cli_cinder_commands.xml:1813(title) ./doc/common/ch_cli_cinder_commands.xml:1869(title) ./doc/common/ch_cli_cinder_commands.xml:1922(title) ./doc/common/ch_cli_cinder_commands.xml:2060(title) ./doc/common/ch_cli_cinder_commands.xml:2089(title) ./doc/common/ch_cli_cinder_commands.xml:2162(title) ./doc/common/ch_cli_cinder_commands.xml:2316(title) ./doc/common/ch_cli_glance_commands.xml:527(title) ./doc/common/ch_cli_glance_commands.xml:718(title) ./doc/common/ch_cli_glance_commands.xml:862(title) ./doc/common/ch_cli_glance_commands.xml:900(title) ./doc/common/ch_cli_glance_commands.xml:1079(title) ./doc/common/ch_cli_glance_commands.xml:1121(title) ./doc/common/ch_cli_heat_commands.xml:561(title) ./doc/common/ch_cli_heat_commands.xml:739(title) ./doc/common/ch_cli_heat_commands.xml:776(title) ./doc/common/ch_cli_heat_commands.xml:848(title) ./doc/common/ch_cli_heat_commands.xml:946(title) ./doc/common/ch_cli_heat_commands.xml:1040(title) ./doc/common/ch_cli_heat_commands.xml:1090(title) ./doc/common/ch_cli_heat_commands.xml:1187(title) ./doc/common/ch_cli_heat_commands.xml:1264(title) ./doc/common/ch_cli_trove_commands.xml:610(title) ./doc/common/ch_cli_trove_commands.xml:653(title) ./doc/common/ch_cli_trove_commands.xml:681(title) ./doc/common/ch_cli_trove_commands.xml:762(title) ./doc/common/ch_cli_trove_commands.xml:884(title) ./doc/common/ch_cli_trove_commands.xml:924(title) ./doc/common/ch_cli_trove_commands.xml:1006(title) ./doc/common/ch_cli_trove_commands.xml:1058(title) ./doc/common/ch_cli_trove_commands.xml:1166(title) ./doc/common/ch_cli_trove_commands.xml:1286(title) ./doc/common/ch_cli_trove_commands.xml:1572(title) ./doc/common/ch_cli_trove_commands.xml:1616(title) ./doc/common/ch_cli_trove_commands.xml:1661(title) ./doc/common/ch_cli_trove_commands.xml:1722(title) ./doc/common/ch_cli_trove_commands.xml:1758(title) ./doc/common/ch_cli_trove_commands.xml:1794(title) ./doc/common/ch_cli_trove_commands.xml:1833(title)
+#: ./doc/common/ch_cli_nova_commands.xml:1698(title) ./doc/common/ch_cli_nova_commands.xml:1848(title) ./doc/common/ch_cli_nova_commands.xml:2149(title) ./doc/common/ch_cli_nova_commands.xml:2265(title) ./doc/common/ch_cli_nova_commands.xml:2372(title) ./doc/common/ch_cli_nova_commands.xml:2567(title) ./doc/common/ch_cli_nova_commands.xml:2678(title) ./doc/common/ch_cli_nova_commands.xml:2695(title) ./doc/common/ch_cli_nova_commands.xml:2773(title) ./doc/common/ch_cli_nova_commands.xml:2803(title) ./doc/common/ch_cli_nova_commands.xml:2832(title) ./doc/common/ch_cli_nova_commands.xml:2910(title) ./doc/common/ch_cli_nova_commands.xml:2962(title) ./doc/common/ch_cli_nova_commands.xml:3065(title) ./doc/common/ch_cli_nova_commands.xml:3161(title) ./doc/common/ch_cli_nova_commands.xml:3252(title) ./doc/common/ch_cli_nova_commands.xml:3314(title) ./doc/common/ch_cli_nova_commands.xml:3343(title) ./doc/common/ch_cli_nova_commands.xml:3385(title) ./doc/common/ch_cli_nova_commands.xml:3606(title) ./doc/common/ch_cli_nova_commands.xml:3652(title) ./doc/common/ch_cli_nova_commands.xml:3678(title) ./doc/common/ch_cli_nova_commands.xml:3759(title) ./doc/common/ch_cli_nova_commands.xml:3784(title) ./doc/common/ch_cli_nova_commands.xml:3878(title) ./doc/common/ch_cli_nova_commands.xml:3920(title) ./doc/common/ch_cli_nova_commands.xml:4043(title) ./doc/common/ch_cli_nova_commands.xml:4129(title) ./doc/common/ch_cli_nova_commands.xml:4192(title) ./doc/common/ch_cli_nova_commands.xml:4362(title) ./doc/common/ch_cli_nova_commands.xml:4449(title) ./doc/common/ch_cli_nova_commands.xml:4467(title) ./doc/common/ch_cli_nova_commands.xml:4629(title) ./doc/common/ch_cli_nova_commands.xml:4773(title) ./doc/common/ch_cli_nova_commands.xml:4874(title) ./doc/common/ch_cli_nova_commands.xml:4971(title) ./doc/common/ch_cli_nova_commands.xml:4988(title) ./doc/common/ch_cli_nova_commands.xml:5013(title) ./doc/common/ch_cli_nova_commands.xml:5061(title) ./doc/common/ch_cli_nova_commands.xml:5201(title) ./doc/common/ch_cli_nova_commands.xml:5247(title) ./doc/common/ch_cli_nova_commands.xml:5428(title) ./doc/common/ch_cli_nova_commands.xml:5465(title) ./doc/common/ch_cli_nova_commands.xml:5826(title) ./doc/common/ch_cli_nova_commands.xml:5912(title) ./doc/common/ch_cli_nova_commands.xml:5954(title) ./doc/common/ch_cli_nova_commands.xml:6024(title) ./doc/common/ch_cli_nova_commands.xml:6054(title) ./doc/common/ch_cli_nova_commands.xml:6236(title) ./doc/common/ch_cli_nova_commands.xml:6271(title) ./doc/common/ch_cli_nova_commands.xml:6347(title) ./doc/common/ch_cli_nova_commands.xml:6448(title) ./doc/common/ch_cli_nova_commands.xml:6496(title) ./doc/common/ch_cli_neutron_commands.xml:1434(title) ./doc/common/ch_cli_neutron_commands.xml:1461(title) ./doc/common/ch_cli_neutron_commands.xml:1517(title) ./doc/common/ch_cli_neutron_commands.xml:1570(title) ./doc/common/ch_cli_neutron_commands.xml:1620(title) ./doc/common/ch_cli_neutron_commands.xml:1681(title) ./doc/common/ch_cli_neutron_commands.xml:1709(title) ./doc/common/ch_cli_neutron_commands.xml:1766(title) ./doc/common/ch_cli_neutron_commands.xml:1838(title) ./doc/common/ch_cli_neutron_commands.xml:1925(title) ./doc/common/ch_cli_neutron_commands.xml:1953(title) ./doc/common/ch_cli_neutron_commands.xml:2011(title) ./doc/common/ch_cli_neutron_commands.xml:2065(title) ./doc/common/ch_cli_neutron_commands.xml:2093(title) ./doc/common/ch_cli_neutron_commands.xml:2151(title) ./doc/common/ch_cli_neutron_commands.xml:2205(title) ./doc/common/ch_cli_neutron_commands.xml:2245(title) ./doc/common/ch_cli_neutron_commands.xml:2307(title) ./doc/common/ch_cli_neutron_commands.xml:2352(title) ./doc/common/ch_cli_neutron_commands.xml:2379(title) ./doc/common/ch_cli_neutron_commands.xml:2435(title) ./doc/common/ch_cli_neutron_commands.xml:2494(title) ./doc/common/ch_cli_neutron_commands.xml:2570(title) ./doc/common/ch_cli_neutron_commands.xml:2599(title) ./doc/common/ch_cli_neutron_commands.xml:2689(title) ./doc/common/ch_cli_neutron_commands.xml:2767(title) ./doc/common/ch_cli_neutron_commands.xml:2814(title) ./doc/common/ch_cli_neutron_commands.xml:2859(title) ./doc/common/ch_cli_neutron_commands.xml:2951(title) ./doc/common/ch_cli_neutron_commands.xml:2991(title) ./doc/common/ch_cli_neutron_commands.xml:3045(title) ./doc/common/ch_cli_neutron_commands.xml:3080(title) ./doc/common/ch_cli_neutron_commands.xml:3206(title) ./doc/common/ch_cli_neutron_commands.xml:3235(title) ./doc/common/ch_cli_neutron_commands.xml:3322(title) ./doc/common/ch_cli_neutron_commands.xml:3377(title) ./doc/common/ch_cli_neutron_commands.xml:3424(title) ./doc/common/ch_cli_neutron_commands.xml:3477(title) ./doc/common/ch_cli_neutron_commands.xml:3524(title) ./doc/common/ch_cli_neutron_commands.xml:3574(title) ./doc/common/ch_cli_neutron_commands.xml:3635(title) ./doc/common/ch_cli_neutron_commands.xml:3672(title) ./doc/common/ch_cli_neutron_commands.xml:3701(title) ./doc/common/ch_cli_neutron_commands.xml:3787(title) ./doc/common/ch_cli_neutron_commands.xml:3844(title) ./doc/common/ch_cli_neutron_commands.xml:4000(title) ./doc/common/ch_cli_neutron_commands.xml:4030(title) ./doc/common/ch_cli_neutron_commands.xml:4118(title) ./doc/common/ch_cli_neutron_commands.xml:4173(title) ./doc/common/ch_cli_neutron_commands.xml:4227(title) ./doc/common/ch_cli_neutron_commands.xml:4289(title) ./doc/common/ch_cli_neutron_commands.xml:4334(title) ./doc/common/ch_cli_neutron_commands.xml:4376(title) ./doc/common/ch_cli_neutron_commands.xml:4439(title) ./doc/common/ch_cli_neutron_commands.xml:4473(title) ./doc/common/ch_cli_neutron_commands.xml:4592(title) ./doc/common/ch_cli_neutron_commands.xml:4639(title) ./doc/common/ch_cli_neutron_commands.xml:4668(title) ./doc/common/ch_cli_neutron_commands.xml:4755(title) ./doc/common/ch_cli_neutron_commands.xml:4809(title) ./doc/common/ch_cli_neutron_commands.xml:4851(title) ./doc/common/ch_cli_neutron_commands.xml:4929(title) ./doc/common/ch_cli_neutron_commands.xml:4958(title) ./doc/common/ch_cli_neutron_commands.xml:5044(title) ./doc/common/ch_cli_neutron_commands.xml:5097(title) ./doc/common/ch_cli_neutron_commands.xml:5129(title) ./doc/common/ch_cli_neutron_commands.xml:5231(title) ./doc/common/ch_cli_neutron_commands.xml:5260(title) ./doc/common/ch_cli_neutron_commands.xml:5347(title) ./doc/common/ch_cli_neutron_commands.xml:5403(title) ./doc/common/ch_cli_neutron_commands.xml:5459(title) ./doc/common/ch_cli_neutron_commands.xml:5512(title) ./doc/common/ch_cli_neutron_commands.xml:5557(title) ./doc/common/ch_cli_neutron_commands.xml:5668(title) ./doc/common/ch_cli_neutron_commands.xml:5697(title) ./doc/common/ch_cli_neutron_commands.xml:5783(title) ./doc/common/ch_cli_neutron_commands.xml:5836(title) ./doc/common/ch_cli_neutron_commands.xml:5877(title) ./doc/common/ch_cli_neutron_commands.xml:5930(title) ./doc/common/ch_cli_neutron_commands.xml:5959(title) ./doc/common/ch_cli_neutron_commands.xml:6056(title) ./doc/common/ch_cli_neutron_commands.xml:6117(title) ./doc/common/ch_cli_neutron_commands.xml:6146(title) ./doc/common/ch_cli_neutron_commands.xml:6233(title) ./doc/common/ch_cli_neutron_commands.xml:6289(title) ./doc/common/ch_cli_neutron_commands.xml:6347(title) ./doc/common/ch_cli_neutron_commands.xml:6407(title) ./doc/common/ch_cli_neutron_commands.xml:6436(title) ./doc/common/ch_cli_neutron_commands.xml:6530(title) ./doc/common/ch_cli_neutron_commands.xml:6588(title) ./doc/common/ch_cli_neutron_commands.xml:6643(title) ./doc/common/ch_cli_neutron_commands.xml:6690(title) ./doc/common/ch_cli_neutron_commands.xml:6735(title) ./doc/common/ch_cli_neutron_commands.xml:6791(title) ./doc/common/ch_cli_neutron_commands.xml:6845(title) ./doc/common/ch_cli_neutron_commands.xml:6873(title) ./doc/common/ch_cli_neutron_commands.xml:6961(title) ./doc/common/ch_cli_neutron_commands.xml:7047(title) ./doc/common/ch_cli_neutron_commands.xml:7100(title) ./doc/common/ch_cli_neutron_commands.xml:7145(title) ./doc/common/ch_cli_neutron_commands.xml:7259(title) ./doc/common/ch_cli_neutron_commands.xml:7287(title) ./doc/common/ch_cli_neutron_commands.xml:7373(title) ./doc/common/ch_cli_neutron_commands.xml:7429(title) ./doc/common/ch_cli_neutron_commands.xml:7498(title) ./doc/common/ch_cli_neutron_commands.xml:7583(title) ./doc/common/ch_cli_neutron_commands.xml:7610(title) ./doc/common/ch_cli_neutron_commands.xml:7666(title) ./doc/common/ch_cli_neutron_commands.xml:7709(title) ./doc/common/ch_cli_neutron_commands.xml:7745(title) ./doc/common/ch_cli_neutron_commands.xml:7773(title) ./doc/common/ch_cli_neutron_commands.xml:7814(title) ./doc/common/ch_cli_neutron_commands.xml:7930(title) ./doc/common/ch_cli_neutron_commands.xml:7982(title) ./doc/common/ch_cli_neutron_commands.xml:8019(title) ./doc/common/ch_cli_neutron_commands.xml:8065(title) ./doc/common/ch_cli_neutron_commands.xml:8121(title) ./doc/common/ch_cli_neutron_commands.xml:8169(title) ./doc/common/ch_cli_neutron_commands.xml:8198(title) ./doc/common/ch_cli_neutron_commands.xml:8285(title) ./doc/common/ch_cli_neutron_commands.xml:8343(title) ./doc/common/ch_cli_neutron_commands.xml:8429(title) ./doc/common/ch_cli_neutron_commands.xml:8482(title) ./doc/common/ch_cli_neutron_commands.xml:8523(title) ./doc/common/ch_cli_neutron_commands.xml:8576(title) ./doc/common/ch_cli_neutron_commands.xml:8605(title) ./doc/common/ch_cli_neutron_commands.xml:8700(title) ./doc/common/ch_cli_neutron_commands.xml:8801(title) ./doc/common/ch_cli_neutron_commands.xml:8832(title) ./doc/common/ch_cli_neutron_commands.xml:8928(title) ./doc/common/ch_cli_neutron_commands.xml:8985(title) ./doc/common/ch_cli_neutron_commands.xml:9040(title) ./doc/common/ch_cli_neutron_commands.xml:9085(title) ./doc/common/ch_cli_neutron_commands.xml:9186(title) ./doc/common/ch_cli_neutron_commands.xml:9298(title) ./doc/common/ch_cli_neutron_commands.xml:9327(title) ./doc/common/ch_cli_neutron_commands.xml:9413(title) ./doc/common/ch_cli_neutron_commands.xml:9466(title) ./doc/common/ch_cli_neutron_commands.xml:9513(title) ./doc/common/ch_cli_neutron_commands.xml:9617(title) ./doc/common/ch_cli_neutron_commands.xml:9646(title) ./doc/common/ch_cli_neutron_commands.xml:9733(title) ./doc/common/ch_cli_neutron_commands.xml:9788(title) ./doc/common/ch_cli_neutron_commands.xml:9846(title) ./doc/common/ch_cli_neutron_commands.xml:9950(title) ./doc/common/ch_cli_neutron_commands.xml:9979(title) ./doc/common/ch_cli_neutron_commands.xml:10066(title) ./doc/common/ch_cli_neutron_commands.xml:10121(title) ./doc/common/ch_cli_neutron_commands.xml:10181(title) ./doc/common/ch_cli_neutron_commands.xml:10250(title) ./doc/common/ch_cli_neutron_commands.xml:10279(title) ./doc/common/ch_cli_neutron_commands.xml:10365(title) ./doc/common/ch_cli_neutron_commands.xml:10419(title) ./doc/common/ch_cli_heat_commands.xml:561(title) ./doc/common/ch_cli_heat_commands.xml:739(title) ./doc/common/ch_cli_heat_commands.xml:776(title) ./doc/common/ch_cli_heat_commands.xml:848(title) ./doc/common/ch_cli_heat_commands.xml:946(title) ./doc/common/ch_cli_heat_commands.xml:1040(title) ./doc/common/ch_cli_heat_commands.xml:1090(title) ./doc/common/ch_cli_heat_commands.xml:1187(title) ./doc/common/ch_cli_heat_commands.xml:1264(title) ./doc/common/ch_cli_swift_commands.xml:358(title) ./doc/common/ch_cli_swift_commands.xml:424(title) ./doc/common/ch_cli_swift_commands.xml:527(title) ./doc/common/ch_cli_swift_commands.xml:601(title) ./doc/common/ch_cli_swift_commands.xml:684(title) ./doc/common/ch_cli_swift_commands.xml:723(title) ./doc/common/ch_cli_glance_commands.xml:527(title) ./doc/common/ch_cli_glance_commands.xml:718(title) ./doc/common/ch_cli_glance_commands.xml:862(title) ./doc/common/ch_cli_glance_commands.xml:900(title) ./doc/common/ch_cli_glance_commands.xml:1079(title) ./doc/common/ch_cli_glance_commands.xml:1121(title) ./doc/common/ch_cli_ceilometer_commands.xml:462(title) ./doc/common/ch_cli_ceilometer_commands.xml:604(title) ./doc/common/ch_cli_ceilometer_commands.xml:749(title) ./doc/common/ch_cli_ceilometer_commands.xml:766(title) ./doc/common/ch_cli_ceilometer_commands.xml:793(title) ./doc/common/ch_cli_ceilometer_commands.xml:812(title) ./doc/common/ch_cli_ceilometer_commands.xml:829(title) ./doc/common/ch_cli_ceilometer_commands.xml:846(title) ./doc/common/ch_cli_ceilometer_commands.xml:887(title) ./doc/common/ch_cli_ceilometer_commands.xml:1077(title) ./doc/common/ch_cli_ceilometer_commands.xml:1282(title) ./doc/common/ch_cli_ceilometer_commands.xml:1471(title) ./doc/common/ch_cli_ceilometer_commands.xml:1490(title) ./doc/common/ch_cli_ceilometer_commands.xml:1514(title) ./doc/common/ch_cli_ceilometer_commands.xml:1534(title) ./doc/common/ch_cli_ceilometer_commands.xml:1570(title) ./doc/common/ch_cli_ceilometer_commands.xml:1606(title) ./doc/common/ch_cli_ceilometer_commands.xml:1642(title) ./doc/common/ch_cli_ceilometer_commands.xml:1661(title) ./doc/common/ch_cli_ceilometer_commands.xml:1684(title) ./doc/common/ch_cli_ceilometer_commands.xml:1767(title) ./doc/common/ch_cli_ceilometer_commands.xml:1803(title) ./doc/common/ch_cli_ceilometer_commands.xml:1856(title) ./doc/common/ch_cli_ceilometer_commands.xml:1874(title) ./doc/common/ch_cli_cinder_commands.xml:751(title) ./doc/common/ch_cli_cinder_commands.xml:819(title) ./doc/common/ch_cli_cinder_commands.xml:871(title) ./doc/common/ch_cli_cinder_commands.xml:992(title) ./doc/common/ch_cli_cinder_commands.xml:1128(title) ./doc/common/ch_cli_cinder_commands.xml:1270(title) ./doc/common/ch_cli_cinder_commands.xml:1350(title) ./doc/common/ch_cli_cinder_commands.xml:1516(title) ./doc/common/ch_cli_cinder_commands.xml:1605(title) ./doc/common/ch_cli_cinder_commands.xml:1716(title) ./doc/common/ch_cli_cinder_commands.xml:1744(title) ./doc/common/ch_cli_cinder_commands.xml:1813(title) ./doc/common/ch_cli_cinder_commands.xml:1869(title) ./doc/common/ch_cli_cinder_commands.xml:1922(title) ./doc/common/ch_cli_cinder_commands.xml:2060(title) ./doc/common/ch_cli_cinder_commands.xml:2089(title) ./doc/common/ch_cli_cinder_commands.xml:2162(title) ./doc/common/ch_cli_cinder_commands.xml:2316(title) ./doc/common/ch_cli_trove_commands.xml:610(title) ./doc/common/ch_cli_trove_commands.xml:653(title) ./doc/common/ch_cli_trove_commands.xml:681(title) ./doc/common/ch_cli_trove_commands.xml:762(title) ./doc/common/ch_cli_trove_commands.xml:884(title) ./doc/common/ch_cli_trove_commands.xml:924(title) ./doc/common/ch_cli_trove_commands.xml:1006(title) ./doc/common/ch_cli_trove_commands.xml:1058(title) ./doc/common/ch_cli_trove_commands.xml:1166(title) ./doc/common/ch_cli_trove_commands.xml:1286(title) ./doc/common/ch_cli_trove_commands.xml:1572(title) ./doc/common/ch_cli_trove_commands.xml:1616(title) ./doc/common/ch_cli_trove_commands.xml:1661(title) ./doc/common/ch_cli_trove_commands.xml:1722(title) ./doc/common/ch_cli_trove_commands.xml:1758(title) ./doc/common/ch_cli_trove_commands.xml:1794(title) ./doc/common/ch_cli_trove_commands.xml:1833(title)
 msgid "Optional arguments"
 msgstr ""
 
@@ -1807,7 +907,7 @@ msgstr ""
 msgid "nova add-fixed-ip command"
 msgstr ""
 
-#: ./doc/common/ch_cli_nova_commands.xml:1723(title) ./doc/common/ch_cli_nova_commands.xml:1748(title) ./doc/common/ch_cli_nova_commands.xml:1774(title) ./doc/common/ch_cli_nova_commands.xml:1831(title) ./doc/common/ch_cli_nova_commands.xml:1865(title) ./doc/common/ch_cli_nova_commands.xml:1906(title) ./doc/common/ch_cli_nova_commands.xml:1931(title) ./doc/common/ch_cli_nova_commands.xml:1956(title) ./doc/common/ch_cli_nova_commands.xml:1973(title) ./doc/common/ch_cli_nova_commands.xml:1997(title) ./doc/common/ch_cli_nova_commands.xml:2022(title) ./doc/common/ch_cli_nova_commands.xml:2047(title) ./doc/common/ch_cli_nova_commands.xml:2087(title) ./doc/common/ch_cli_nova_commands.xml:2130(title) ./doc/common/ch_cli_nova_commands.xml:2174(title) ./doc/common/ch_cli_nova_commands.xml:2191(title) ./doc/common/ch_cli_nova_commands.xml:2221(title) ./doc/common/ch_cli_nova_commands.xml:2306(title) ./doc/common/ch_cli_nova_commands.xml:2330(title) ./doc/common/ch_cli_nova_commands.xml:2361(title) ./doc/common/ch_cli_nova_commands.xml:2584(title) ./doc/common/ch_cli_nova_commands.xml:2601(title) ./doc/common/ch_cli_nova_commands.xml:2618(title) ./doc/common/ch_cli_nova_commands.xml:2643(title) ./doc/common/ch_cli_nova_commands.xml:2667(title) ./doc/common/ch_cli_nova_commands.xml:2712(title) ./doc/common/ch_cli_nova_commands.xml:2729(title) ./doc/common/ch_cli_nova_commands.xml:2746(title) ./doc/common/ch_cli_nova_commands.xml:2792(title) ./doc/common/ch_cli_nova_commands.xml:2821(title) ./doc/common/ch_cli_nova_commands.xml:2850(title) ./doc/common/ch_cli_nova_commands.xml:2875(title) ./doc/common/ch_cli_nova_commands.xml:2899(title) ./doc/common/ch_cli_nova_commands.xml:2943(title) ./doc/common/ch_cli_nova_commands.xml:2989(title) ./doc/common/ch_cli_nova_commands.xml:3006(title) ./doc/common/ch_cli_nova_commands.xml:3023(title) ./doc/common/ch_cli_nova_commands.xml:3040(title) ./doc/common/ch_cli_nova_commands.xml:3090(title) ./doc/common/ch_cli_nova_commands.xml:3117(title) ./doc/common/ch_cli_nova_commands.xml:3202(title) ./doc/common/ch_cli_nova_commands.xml:3219(title) ./doc/common/ch_cli_nova_commands.xml:3277(title) ./doc/common/ch_cli_nova_commands.xml:3295(title) ./doc/common/ch_cli_nova_commands.xml:3332(title) ./doc/common/ch_cli_nova_commands.xml:3368(title) ./doc/common/ch_cli_nova_commands.xml:3402(title) ./doc/common/ch_cli_nova_commands.xml:3419(title) ./doc/common/ch_cli_nova_commands.xml:3436(title) ./doc/common/ch_cli_nova_commands.xml:3475(title) ./doc/common/ch_cli_nova_commands.xml:3492(title) ./doc/common/ch_cli_nova_commands.xml:3520(title) ./doc/common/ch_cli_nova_commands.xml:3545(title) ./doc/common/ch_cli_nova_commands.xml:3570(title) ./doc/common/ch_cli_nova_commands.xml:3595(title) ./doc/common/ch_cli_nova_commands.xml:3623(title) ./doc/common/ch_cli_nova_commands.xml:3641(title) ./doc/common/ch_cli_nova_commands.xml:3696(title) ./doc/common/ch_cli_nova_commands.xml:3729(title) ./doc/common/ch_cli_nova_commands.xml:3748(title) ./doc/common/ch_cli_nova_commands.xml:3801(title) ./doc/common/ch_cli_nova_commands.xml:3818(title) ./doc/common/ch_cli_nova_commands.xml:3842(title) ./doc/common/ch_cli_nova_commands.xml:3859(title) ./doc/common/ch_cli_nova_commands.xml:3903(title) ./doc/common/ch_cli_nova_commands.xml:3937(title) ./doc/common/ch_cli_nova_commands.xml:3971(title) ./doc/common/ch_cli_nova_commands.xml:3988(title) ./doc/common/ch_cli_nova_commands.xml:4013(title) ./doc/common/ch_cli_nova_commands.xml:4032(title) ./doc/common/ch_cli_nova_commands.xml:4076(title) ./doc/common/ch_cli_nova_commands.xml:4101(title) ./doc/common/ch_cli_nova_commands.xml:4118(title) ./doc/common/ch_cli_nova_commands.xml:4146(title) ./doc/common/ch_cli_nova_commands.xml:4170(title) ./doc/common/ch_cli_nova_commands.xml:4325(title) ./doc/common/ch_cli_nova_commands.xml:4343(title) ./doc/common/ch_cli_nova_commands.xml:4388(title) ./doc/common/ch_cli_nova_commands.xml:4405(title) ./doc/common/ch_cli_nova_commands.xml:4438(title) ./doc/common/ch_cli_nova_commands.xml:4500(title) ./doc/common/ch_cli_nova_commands.xml:4517(title) ./doc/common/ch_cli_nova_commands.xml:4543(title) ./doc/common/ch_cli_nova_commands.xml:4567(title) ./doc/common/ch_cli_nova_commands.xml:4592(title) ./doc/common/ch_cli_nova_commands.xml:4618(title) ./doc/common/ch_cli_nova_commands.xml:4762(title) ./doc/common/ch_cli_nova_commands.xml:4803(title) ./doc/common/ch_cli_nova_commands.xml:4820(title) ./doc/common/ch_cli_nova_commands.xml:4837(title) ./doc/common/ch_cli_nova_commands.xml:4863(title) ./doc/common/ch_cli_nova_commands.xml:5050(title) ./doc/common/ch_cli_nova_commands.xml:5190(title) ./doc/common/ch_cli_nova_commands.xml:5228(title) ./doc/common/ch_cli_nova_commands.xml:5290(title) ./doc/common/ch_cli_nova_commands.xml:5308(title) ./doc/common/ch_cli_nova_commands.xml:5333(title) ./doc/common/ch_cli_nova_commands.xml:5358(title) ./doc/common/ch_cli_nova_commands.xml:5383(title) ./doc/common/ch_cli_nova_commands.xml:5400(title) ./doc/common/ch_cli_nova_commands.xml:5417(title) ./doc/common/ch_cli_nova_commands.xml:5446(title) ./doc/common/ch_cli_nova_commands.xml:5482(title) ./doc/common/ch_cli_nova_commands.xml:5499(title) ./doc/common/ch_cli_nova_commands.xml:5516(title) ./doc/common/ch_cli_nova_commands.xml:5533(title) ./doc/common/ch_cli_nova_commands.xml:5550(title) ./doc/common/ch_cli_nova_commands.xml:5567(title) ./doc/common/ch_cli_nova_commands.xml:5585(title) ./doc/common/ch_cli_nova_commands.xml:5635(title) ./doc/common/ch_cli_nova_commands.xml:5684(title) ./doc/common/ch_cli_nova_commands.xml:5709(title) ./doc/common/ch_cli_nova_commands.xml:5727(title) ./doc/common/ch_cli_nova_commands.xml:5777(title) ./doc/common/ch_cli_nova_commands.xml:5843(title) ./doc/common/ch_cli_nova_commands.xml:5860(title) ./doc/common/ch_cli_nova_commands.xml:5893(title) ./doc/common/ch_cli_nova_commands.xml:5929(title) ./doc/common/ch_cli_nova_commands.xml:5979(title) ./doc/common/ch_cli_nova_commands.xml:5996(title) ./doc/common/ch_cli_nova_commands.xml:6013(title) ./doc/common/ch_cli_nova_commands.xml:6043(title) ./doc/common/ch_cli_nova_commands.xml:6117(title) ./doc/common/ch_cli_nova_commands.xml:6134(title) ./doc/common/ch_cli_nova_commands.xml:6151(title) ./doc/common/ch_cli_nova_commands.xml:6168(title) ./doc/common/ch_cli_nova_commands.xml:6185(title) ./doc/common/ch_cli_nova_commands.xml:6202(title) ./doc/common/ch_cli_nova_commands.xml:6219(title) ./doc/common/ch_cli_nova_commands.xml:6296(title) ./doc/common/ch_cli_nova_commands.xml:6336(title) ./doc/common/ch_cli_nova_commands.xml:6406(title) ./doc/common/ch_cli_nova_commands.xml:6423(title) ./doc/common/ch_cli_nova_commands.xml:6465(title) ./doc/common/ch_cli_nova_commands.xml:6485(title) ./doc/common/ch_cli_nova_commands.xml:6530(title) ./doc/common/ch_cli_nova_commands.xml:6554(title) ./doc/common/ch_cli_nova_commands.xml:6571(title) ./doc/common/ch_cli_nova_commands.xml:6588(title) ./doc/common/ch_cli_nova_commands.xml:6612(title) ./doc/common/ch_cli_nova_commands.xml:6645(title) ./doc/common/ch_cli_nova_commands.xml:6670(title) ./doc/common/ch_cli_neutron_commands.xml:1423(title) ./doc/common/ch_cli_neutron_commands.xml:1506(title) ./doc/common/ch_cli_neutron_commands.xml:1559(title) ./doc/common/ch_cli_neutron_commands.xml:1601(title) ./doc/common/ch_cli_neutron_commands.xml:1670(title) ./doc/common/ch_cli_neutron_commands.xml:1755(title) ./doc/common/ch_cli_neutron_commands.xml:1819(title) ./doc/common/ch_cli_neutron_commands.xml:1914(title) ./doc/common/ch_cli_neutron_commands.xml:2000(title) ./doc/common/ch_cli_neutron_commands.xml:2054(title) ./doc/common/ch_cli_neutron_commands.xml:2140(title) ./doc/common/ch_cli_neutron_commands.xml:2194(title) ./doc/common/ch_cli_neutron_commands.xml:2234(title) ./doc/common/ch_cli_neutron_commands.xml:2288(title) ./doc/common/ch_cli_neutron_commands.xml:2333(title) ./doc/common/ch_cli_neutron_commands.xml:2424(title) ./doc/common/ch_cli_neutron_commands.xml:2483(title) ./doc/common/ch_cli_neutron_commands.xml:2559(title) ./doc/common/ch_cli_neutron_commands.xml:2678(title) ./doc/common/ch_cli_neutron_commands.xml:2756(title) ./doc/common/ch_cli_neutron_commands.xml:2795(title) ./doc/common/ch_cli_neutron_commands.xml:2932(title) ./doc/common/ch_cli_neutron_commands.xml:2980(title) ./doc/common/ch_cli_neutron_commands.xml:3034(title) ./doc/common/ch_cli_neutron_commands.xml:3195(title) ./doc/common/ch_cli_neutron_commands.xml:3311(title) ./doc/common/ch_cli_neutron_commands.xml:3366(title) ./doc/common/ch_cli_neutron_commands.xml:3413(title) ./doc/common/ch_cli_neutron_commands.xml:3466(title) ./doc/common/ch_cli_neutron_commands.xml:3504(title) ./doc/common/ch_cli_neutron_commands.xml:3563(title) ./doc/common/ch_cli_neutron_commands.xml:3624(title) ./doc/common/ch_cli_neutron_commands.xml:3661(title) ./doc/common/ch_cli_neutron_commands.xml:3776(title) ./doc/common/ch_cli_neutron_commands.xml:3989(title) ./doc/common/ch_cli_neutron_commands.xml:4107(title) ./doc/common/ch_cli_neutron_commands.xml:4162(title) ./doc/common/ch_cli_neutron_commands.xml:4216(title) ./doc/common/ch_cli_neutron_commands.xml:4270(title) ./doc/common/ch_cli_neutron_commands.xml:4315(title) ./doc/common/ch_cli_neutron_commands.xml:4365(title) ./doc/common/ch_cli_neutron_commands.xml:4419(title) ./doc/common/ch_cli_neutron_commands.xml:4581(title) ./doc/common/ch_cli_neutron_commands.xml:4619(title) ./doc/common/ch_cli_neutron_commands.xml:4744(title) ./doc/common/ch_cli_neutron_commands.xml:4798(title) ./doc/common/ch_cli_neutron_commands.xml:4840(title) ./doc/common/ch_cli_neutron_commands.xml:4918(title) ./doc/common/ch_cli_neutron_commands.xml:5033(title) ./doc/common/ch_cli_neutron_commands.xml:5086(title) ./doc/common/ch_cli_neutron_commands.xml:5220(title) ./doc/common/ch_cli_neutron_commands.xml:5336(title) ./doc/common/ch_cli_neutron_commands.xml:5392(title) ./doc/common/ch_cli_neutron_commands.xml:5448(title) ./doc/common/ch_cli_neutron_commands.xml:5501(title) ./doc/common/ch_cli_neutron_commands.xml:5546(title) ./doc/common/ch_cli_neutron_commands.xml:5657(title) ./doc/common/ch_cli_neutron_commands.xml:5772(title) ./doc/common/ch_cli_neutron_commands.xml:5825(title) ./doc/common/ch_cli_neutron_commands.xml:5866(title) ./doc/common/ch_cli_neutron_commands.xml:5919(title) ./doc/common/ch_cli_neutron_commands.xml:6037(title) ./doc/common/ch_cli_neutron_commands.xml:6106(title) ./doc/common/ch_cli_neutron_commands.xml:6222(title) ./doc/common/ch_cli_neutron_commands.xml:6278(title) ./doc/common/ch_cli_neutron_commands.xml:6336(title) ./doc/common/ch_cli_neutron_commands.xml:6396(title) ./doc/common/ch_cli_neutron_commands.xml:6511(title) ./doc/common/ch_cli_neutron_commands.xml:6577(title) ./doc/common/ch_cli_neutron_commands.xml:6632(title) ./doc/common/ch_cli_neutron_commands.xml:6671(title) ./doc/common/ch_cli_neutron_commands.xml:6780(title) ./doc/common/ch_cli_neutron_commands.xml:6834(title) ./doc/common/ch_cli_neutron_commands.xml:6950(title) ./doc/common/ch_cli_neutron_commands.xml:7036(title) ./doc/common/ch_cli_neutron_commands.xml:7089(title) ./doc/common/ch_cli_neutron_commands.xml:7134(title) ./doc/common/ch_cli_neutron_commands.xml:7248(title) ./doc/common/ch_cli_neutron_commands.xml:7362(title) ./doc/common/ch_cli_neutron_commands.xml:7418(title) ./doc/common/ch_cli_neutron_commands.xml:7487(title) ./doc/common/ch_cli_neutron_commands.xml:7572(title) ./doc/common/ch_cli_neutron_commands.xml:7655(title) ./doc/common/ch_cli_neutron_commands.xml:7911(title) ./doc/common/ch_cli_neutron_commands.xml:7971(title) ./doc/common/ch_cli_neutron_commands.xml:8008(title) ./doc/common/ch_cli_neutron_commands.xml:8046(title) ./doc/common/ch_cli_neutron_commands.xml:8099(title) ./doc/common/ch_cli_neutron_commands.xml:8147(title) ./doc/common/ch_cli_neutron_commands.xml:8274(title) ./doc/common/ch_cli_neutron_commands.xml:8332(title) ./doc/common/ch_cli_neutron_commands.xml:8418(title) ./doc/common/ch_cli_neutron_commands.xml:8471(title) ./doc/common/ch_cli_neutron_commands.xml:8512(title) ./doc/common/ch_cli_neutron_commands.xml:8565(title) ./doc/common/ch_cli_neutron_commands.xml:8689(title) ./doc/common/ch_cli_neutron_commands.xml:8790(title) ./doc/common/ch_cli_neutron_commands.xml:8917(title) ./doc/common/ch_cli_neutron_commands.xml:8974(title) ./doc/common/ch_cli_neutron_commands.xml:9029(title) ./doc/common/ch_cli_neutron_commands.xml:9167(title) ./doc/common/ch_cli_neutron_commands.xml:9287(title) ./doc/common/ch_cli_neutron_commands.xml:9402(title) ./doc/common/ch_cli_neutron_commands.xml:9455(title) ./doc/common/ch_cli_neutron_commands.xml:9502(title) ./doc/common/ch_cli_neutron_commands.xml:9606(title) ./doc/common/ch_cli_neutron_commands.xml:9722(title) ./doc/common/ch_cli_neutron_commands.xml:9777(title) ./doc/common/ch_cli_neutron_commands.xml:9835(title) ./doc/common/ch_cli_neutron_commands.xml:9939(title) ./doc/common/ch_cli_neutron_commands.xml:10055(title) ./doc/common/ch_cli_neutron_commands.xml:10110(title) ./doc/common/ch_cli_neutron_commands.xml:10162(title) ./doc/common/ch_cli_neutron_commands.xml:10239(title) ./doc/common/ch_cli_neutron_commands.xml:10354(title) ./doc/common/ch_cli_neutron_commands.xml:10408(title) ./doc/common/ch_cli_swift_commands.xml:338(title) ./doc/common/ch_cli_swift_commands.xml:402(title) ./doc/common/ch_cli_swift_commands.xml:516(title) ./doc/common/ch_cli_swift_commands.xml:581(title) ./doc/common/ch_cli_swift_commands.xml:664(title) ./doc/common/ch_cli_swift_commands.xml:703(title) ./doc/common/ch_cli_cinder_commands.xml:740(title) ./doc/common/ch_cli_cinder_commands.xml:784(title) ./doc/common/ch_cli_cinder_commands.xml:808(title) ./doc/common/ch_cli_cinder_commands.xml:836(title) ./doc/common/ch_cli_cinder_commands.xml:860(title) ./doc/common/ch_cli_cinder_commands.xml:952(title) ./doc/common/ch_cli_cinder_commands.xml:972(title) ./doc/common/ch_cli_cinder_commands.xml:1029(title) ./doc/common/ch_cli_cinder_commands.xml:1053(title) ./doc/common/ch_cli_cinder_commands.xml:1077(title) ./doc/common/ch_cli_cinder_commands.xml:1109(title) ./doc/common/ch_cli_cinder_commands.xml:1176(title) ./doc/common/ch_cli_cinder_commands.xml:1209(title) ./doc/common/ch_cli_cinder_commands.xml:1226(title) ./doc/common/ch_cli_cinder_commands.xml:1251(title) ./doc/common/ch_cli_cinder_commands.xml:1289(title) ./doc/common/ch_cli_cinder_commands.xml:1314(title) ./doc/common/ch_cli_cinder_commands.xml:1339(title) ./doc/common/ch_cli_cinder_commands.xml:1368(title) ./doc/common/ch_cli_cinder_commands.xml:1393(title) ./doc/common/ch_cli_cinder_commands.xml:1410(title) ./doc/common/ch_cli_cinder_commands.xml:1427(title) ./doc/common/ch_cli_cinder_commands.xml:1467(title) ./doc/common/ch_cli_cinder_commands.xml:1484(title) ./doc/common/ch_cli_cinder_commands.xml:1505(title) ./doc/common/ch_cli_cinder_commands.xml:1557(title) ./doc/common/ch_cli_cinder_commands.xml:1574(title) ./doc/common/ch_cli_cinder_commands.xml:1594(title) ./doc/common/ch_cli_cinder_commands.xml:1646(title) ./doc/common/ch_cli_cinder_commands.xml:1670(title) ./doc/common/ch_cli_cinder_commands.xml:1697(title) ./doc/common/ch_cli_cinder_commands.xml:1733(title) ./doc/common/ch_cli_cinder_commands.xml:1763(title) ./doc/common/ch_cli_cinder_commands.xml:1788(title) ./doc/common/ch_cli_cinder_commands.xml:1838(title) ./doc/common/ch_cli_cinder_commands.xml:1858(title) ./doc/common/ch_cli_cinder_commands.xml:1903(title) ./doc/common/ch_cli_cinder_commands.xml:1964(title) ./doc/common/ch_cli_cinder_commands.xml:1997(title) ./doc/common/ch_cli_cinder_commands.xml:2015(title) ./doc/common/ch_cli_cinder_commands.xml:2041(title) ./doc/common/ch_cli_cinder_commands.xml:2078(title) ./doc/common/ch_cli_cinder_commands.xml:2109(title) ./doc/common/ch_cli_cinder_commands.xml:2126(title) ./doc/common/ch_cli_cinder_commands.xml:2151(title) ./doc/common/ch_cli_cinder_commands.xml:2179(title) ./doc/common/ch_cli_cinder_commands.xml:2203(title) ./doc/common/ch_cli_cinder_commands.xml:2220(title) ./doc/common/ch_cli_cinder_commands.xml:2237(title) ./doc/common/ch_cli_cinder_commands.xml:2254(title) ./doc/common/ch_cli_cinder_commands.xml:2297(title) ./doc/common/ch_cli_glance_commands.xml:694(title) ./doc/common/ch_cli_glance_commands.xml:851(title) ./doc/common/ch_cli_glance_commands.xml:889(title) ./doc/common/ch_cli_glance_commands.xml:1060(title) ./doc/common/ch_cli_glance_commands.xml:1096(title) ./doc/common/ch_cli_heat_commands.xml:509(title) ./doc/common/ch_cli_heat_commands.xml:526(title) ./doc/common/ch_cli_heat_commands.xml:550(title) ./doc/common/ch_cli_heat_commands.xml:578(title) ./doc/common/ch_cli_heat_commands.xml:611(title) ./doc/common/ch_cli_heat_commands.xml:628(title) ./doc/common/ch_cli_heat_commands.xml:653(title) ./doc/common/ch_cli_heat_commands.xml:670(title) ./doc/common/ch_cli_heat_commands.xml:695(title) ./doc/common/ch_cli_heat_commands.xml:720(title) ./doc/common/ch_cli_heat_commands.xml:765(title) ./doc/common/ch_cli_heat_commands.xml:800(title) ./doc/common/ch_cli_heat_commands.xml:817(title) ./doc/common/ch_cli_heat_commands.xml:837(title) ./doc/common/ch_cli_heat_commands.xml:935(title) ./doc/common/ch_cli_heat_commands.xml:1022(title) ./doc/common/ch_cli_heat_commands.xml:1079(title) ./doc/common/ch_cli_heat_commands.xml:1157(title) ./doc/common/ch_cli_heat_commands.xml:1176(title) ./doc/common/ch_cli_heat_commands.xml:1246(title) ./doc/common/ch_cli_trove_commands.xml:591(title) ./doc/common/ch_cli_trove_commands.xml:636(title) ./doc/common/ch_cli_trove_commands.xml:670(title) ./doc/common/ch_cli_trove_commands.xml:698(title) ./doc/common/ch_cli_trove_commands.xml:715(title) ./doc/common/ch_cli_trove_commands.xml:743(title) ./doc/common/ch_cli_trove_commands.xml:796(title) ./doc/common/ch_cli_trove_commands.xml:813(title) ./doc/common/ch_cli_trove_commands.xml:830(title) ./doc/common/ch_cli_trove_commands.xml:847(title) ./doc/common/ch_cli_trove_commands.xml:872(title) ./doc/common/ch_cli_trove_commands.xml:904(title) ./doc/common/ch_cli_trove_commands.xml:943(title) ./doc/common/ch_cli_trove_commands.xml:968(title) ./doc/common/ch_cli_trove_commands.xml:987(title) ./doc/common/ch_cli_trove_commands.xml:1039(title) ./doc/common/ch_cli_trove_commands.xml:1147(title) ./doc/common/ch_cli_trove_commands.xml:1191(title) ./doc/common/ch_cli_trove_commands.xml:1216(title) ./doc/common/ch_cli_trove_commands.xml:1240(title) ./doc/common/ch_cli_trove_commands.xml:1257(title) ./doc/common/ch_cli_trove_commands.xml:1275(title) ./doc/common/ch_cli_trove_commands.xml:1304(title) ./doc/common/ch_cli_trove_commands.xml:1328(title) ./doc/common/ch_cli_trove_commands.xml:1359(title) ./doc/common/ch_cli_trove_commands.xml:1384(title) ./doc/common/ch_cli_trove_commands.xml:1409(title) ./doc/common/ch_cli_trove_commands.xml:1426(title) ./doc/common/ch_cli_trove_commands.xml:1443(title) ./doc/common/ch_cli_trove_commands.xml:1460(title) ./doc/common/ch_cli_trove_commands.xml:1485(title) ./doc/common/ch_cli_trove_commands.xml:1509(title) ./doc/common/ch_cli_trove_commands.xml:1526(title) ./doc/common/ch_cli_trove_commands.xml:1545(title) ./doc/common/ch_cli_trove_commands.xml:1597(title) ./doc/common/ch_cli_trove_commands.xml:1634(title) ./doc/common/ch_cli_trove_commands.xml:1678(title) ./doc/common/ch_cli_trove_commands.xml:1695(title) ./doc/common/ch_cli_trove_commands.xml:1739(title) ./doc/common/ch_cli_trove_commands.xml:1775(title) ./doc/common/ch_cli_trove_commands.xml:1814(title)
+#: ./doc/common/ch_cli_nova_commands.xml:1723(title) ./doc/common/ch_cli_nova_commands.xml:1748(title) ./doc/common/ch_cli_nova_commands.xml:1774(title) ./doc/common/ch_cli_nova_commands.xml:1831(title) ./doc/common/ch_cli_nova_commands.xml:1865(title) ./doc/common/ch_cli_nova_commands.xml:1906(title) ./doc/common/ch_cli_nova_commands.xml:1931(title) ./doc/common/ch_cli_nova_commands.xml:1956(title) ./doc/common/ch_cli_nova_commands.xml:1973(title) ./doc/common/ch_cli_nova_commands.xml:1997(title) ./doc/common/ch_cli_nova_commands.xml:2022(title) ./doc/common/ch_cli_nova_commands.xml:2047(title) ./doc/common/ch_cli_nova_commands.xml:2087(title) ./doc/common/ch_cli_nova_commands.xml:2130(title) ./doc/common/ch_cli_nova_commands.xml:2174(title) ./doc/common/ch_cli_nova_commands.xml:2191(title) ./doc/common/ch_cli_nova_commands.xml:2221(title) ./doc/common/ch_cli_nova_commands.xml:2306(title) ./doc/common/ch_cli_nova_commands.xml:2330(title) ./doc/common/ch_cli_nova_commands.xml:2361(title) ./doc/common/ch_cli_nova_commands.xml:2584(title) ./doc/common/ch_cli_nova_commands.xml:2601(title) ./doc/common/ch_cli_nova_commands.xml:2618(title) ./doc/common/ch_cli_nova_commands.xml:2643(title) ./doc/common/ch_cli_nova_commands.xml:2667(title) ./doc/common/ch_cli_nova_commands.xml:2712(title) ./doc/common/ch_cli_nova_commands.xml:2729(title) ./doc/common/ch_cli_nova_commands.xml:2746(title) ./doc/common/ch_cli_nova_commands.xml:2792(title) ./doc/common/ch_cli_nova_commands.xml:2821(title) ./doc/common/ch_cli_nova_commands.xml:2850(title) ./doc/common/ch_cli_nova_commands.xml:2875(title) ./doc/common/ch_cli_nova_commands.xml:2899(title) ./doc/common/ch_cli_nova_commands.xml:2943(title) ./doc/common/ch_cli_nova_commands.xml:2989(title) ./doc/common/ch_cli_nova_commands.xml:3006(title) ./doc/common/ch_cli_nova_commands.xml:3023(title) ./doc/common/ch_cli_nova_commands.xml:3040(title) ./doc/common/ch_cli_nova_commands.xml:3090(title) ./doc/common/ch_cli_nova_commands.xml:3117(title) ./doc/common/ch_cli_nova_commands.xml:3202(title) ./doc/common/ch_cli_nova_commands.xml:3219(title) ./doc/common/ch_cli_nova_commands.xml:3277(title) ./doc/common/ch_cli_nova_commands.xml:3295(title) ./doc/common/ch_cli_nova_commands.xml:3332(title) ./doc/common/ch_cli_nova_commands.xml:3368(title) ./doc/common/ch_cli_nova_commands.xml:3402(title) ./doc/common/ch_cli_nova_commands.xml:3419(title) ./doc/common/ch_cli_nova_commands.xml:3436(title) ./doc/common/ch_cli_nova_commands.xml:3475(title) ./doc/common/ch_cli_nova_commands.xml:3492(title) ./doc/common/ch_cli_nova_commands.xml:3520(title) ./doc/common/ch_cli_nova_commands.xml:3545(title) ./doc/common/ch_cli_nova_commands.xml:3570(title) ./doc/common/ch_cli_nova_commands.xml:3595(title) ./doc/common/ch_cli_nova_commands.xml:3623(title) ./doc/common/ch_cli_nova_commands.xml:3641(title) ./doc/common/ch_cli_nova_commands.xml:3696(title) ./doc/common/ch_cli_nova_commands.xml:3729(title) ./doc/common/ch_cli_nova_commands.xml:3748(title) ./doc/common/ch_cli_nova_commands.xml:3801(title) ./doc/common/ch_cli_nova_commands.xml:3818(title) ./doc/common/ch_cli_nova_commands.xml:3842(title) ./doc/common/ch_cli_nova_commands.xml:3859(title) ./doc/common/ch_cli_nova_commands.xml:3903(title) ./doc/common/ch_cli_nova_commands.xml:3937(title) ./doc/common/ch_cli_nova_commands.xml:3971(title) ./doc/common/ch_cli_nova_commands.xml:3988(title) ./doc/common/ch_cli_nova_commands.xml:4013(title) ./doc/common/ch_cli_nova_commands.xml:4032(title) ./doc/common/ch_cli_nova_commands.xml:4076(title) ./doc/common/ch_cli_nova_commands.xml:4101(title) ./doc/common/ch_cli_nova_commands.xml:4118(title) ./doc/common/ch_cli_nova_commands.xml:4146(title) ./doc/common/ch_cli_nova_commands.xml:4170(title) ./doc/common/ch_cli_nova_commands.xml:4325(title) ./doc/common/ch_cli_nova_commands.xml:4343(title) ./doc/common/ch_cli_nova_commands.xml:4388(title) ./doc/common/ch_cli_nova_commands.xml:4405(title) ./doc/common/ch_cli_nova_commands.xml:4438(title) ./doc/common/ch_cli_nova_commands.xml:4500(title) ./doc/common/ch_cli_nova_commands.xml:4517(title) ./doc/common/ch_cli_nova_commands.xml:4543(title) ./doc/common/ch_cli_nova_commands.xml:4567(title) ./doc/common/ch_cli_nova_commands.xml:4592(title) ./doc/common/ch_cli_nova_commands.xml:4618(title) ./doc/common/ch_cli_nova_commands.xml:4762(title) ./doc/common/ch_cli_nova_commands.xml:4803(title) ./doc/common/ch_cli_nova_commands.xml:4820(title) ./doc/common/ch_cli_nova_commands.xml:4837(title) ./doc/common/ch_cli_nova_commands.xml:4863(title) ./doc/common/ch_cli_nova_commands.xml:5050(title) ./doc/common/ch_cli_nova_commands.xml:5190(title) ./doc/common/ch_cli_nova_commands.xml:5228(title) ./doc/common/ch_cli_nova_commands.xml:5290(title) ./doc/common/ch_cli_nova_commands.xml:5308(title) ./doc/common/ch_cli_nova_commands.xml:5333(title) ./doc/common/ch_cli_nova_commands.xml:5358(title) ./doc/common/ch_cli_nova_commands.xml:5383(title) ./doc/common/ch_cli_nova_commands.xml:5400(title) ./doc/common/ch_cli_nova_commands.xml:5417(title) ./doc/common/ch_cli_nova_commands.xml:5446(title) ./doc/common/ch_cli_nova_commands.xml:5482(title) ./doc/common/ch_cli_nova_commands.xml:5499(title) ./doc/common/ch_cli_nova_commands.xml:5516(title) ./doc/common/ch_cli_nova_commands.xml:5533(title) ./doc/common/ch_cli_nova_commands.xml:5550(title) ./doc/common/ch_cli_nova_commands.xml:5567(title) ./doc/common/ch_cli_nova_commands.xml:5585(title) ./doc/common/ch_cli_nova_commands.xml:5635(title) ./doc/common/ch_cli_nova_commands.xml:5684(title) ./doc/common/ch_cli_nova_commands.xml:5709(title) ./doc/common/ch_cli_nova_commands.xml:5727(title) ./doc/common/ch_cli_nova_commands.xml:5777(title) ./doc/common/ch_cli_nova_commands.xml:5843(title) ./doc/common/ch_cli_nova_commands.xml:5860(title) ./doc/common/ch_cli_nova_commands.xml:5893(title) ./doc/common/ch_cli_nova_commands.xml:5929(title) ./doc/common/ch_cli_nova_commands.xml:5979(title) ./doc/common/ch_cli_nova_commands.xml:5996(title) ./doc/common/ch_cli_nova_commands.xml:6013(title) ./doc/common/ch_cli_nova_commands.xml:6043(title) ./doc/common/ch_cli_nova_commands.xml:6117(title) ./doc/common/ch_cli_nova_commands.xml:6134(title) ./doc/common/ch_cli_nova_commands.xml:6151(title) ./doc/common/ch_cli_nova_commands.xml:6168(title) ./doc/common/ch_cli_nova_commands.xml:6185(title) ./doc/common/ch_cli_nova_commands.xml:6202(title) ./doc/common/ch_cli_nova_commands.xml:6219(title) ./doc/common/ch_cli_nova_commands.xml:6296(title) ./doc/common/ch_cli_nova_commands.xml:6336(title) ./doc/common/ch_cli_nova_commands.xml:6406(title) ./doc/common/ch_cli_nova_commands.xml:6423(title) ./doc/common/ch_cli_nova_commands.xml:6465(title) ./doc/common/ch_cli_nova_commands.xml:6485(title) ./doc/common/ch_cli_nova_commands.xml:6530(title) ./doc/common/ch_cli_nova_commands.xml:6554(title) ./doc/common/ch_cli_nova_commands.xml:6571(title) ./doc/common/ch_cli_nova_commands.xml:6588(title) ./doc/common/ch_cli_nova_commands.xml:6612(title) ./doc/common/ch_cli_nova_commands.xml:6645(title) ./doc/common/ch_cli_nova_commands.xml:6670(title) ./doc/common/ch_cli_neutron_commands.xml:1423(title) ./doc/common/ch_cli_neutron_commands.xml:1506(title) ./doc/common/ch_cli_neutron_commands.xml:1559(title) ./doc/common/ch_cli_neutron_commands.xml:1601(title) ./doc/common/ch_cli_neutron_commands.xml:1670(title) ./doc/common/ch_cli_neutron_commands.xml:1755(title) ./doc/common/ch_cli_neutron_commands.xml:1819(title) ./doc/common/ch_cli_neutron_commands.xml:1914(title) ./doc/common/ch_cli_neutron_commands.xml:2000(title) ./doc/common/ch_cli_neutron_commands.xml:2054(title) ./doc/common/ch_cli_neutron_commands.xml:2140(title) ./doc/common/ch_cli_neutron_commands.xml:2194(title) ./doc/common/ch_cli_neutron_commands.xml:2234(title) ./doc/common/ch_cli_neutron_commands.xml:2288(title) ./doc/common/ch_cli_neutron_commands.xml:2333(title) ./doc/common/ch_cli_neutron_commands.xml:2424(title) ./doc/common/ch_cli_neutron_commands.xml:2483(title) ./doc/common/ch_cli_neutron_commands.xml:2559(title) ./doc/common/ch_cli_neutron_commands.xml:2678(title) ./doc/common/ch_cli_neutron_commands.xml:2756(title) ./doc/common/ch_cli_neutron_commands.xml:2795(title) ./doc/common/ch_cli_neutron_commands.xml:2932(title) ./doc/common/ch_cli_neutron_commands.xml:2980(title) ./doc/common/ch_cli_neutron_commands.xml:3034(title) ./doc/common/ch_cli_neutron_commands.xml:3195(title) ./doc/common/ch_cli_neutron_commands.xml:3311(title) ./doc/common/ch_cli_neutron_commands.xml:3366(title) ./doc/common/ch_cli_neutron_commands.xml:3413(title) ./doc/common/ch_cli_neutron_commands.xml:3466(title) ./doc/common/ch_cli_neutron_commands.xml:3504(title) ./doc/common/ch_cli_neutron_commands.xml:3563(title) ./doc/common/ch_cli_neutron_commands.xml:3624(title) ./doc/common/ch_cli_neutron_commands.xml:3661(title) ./doc/common/ch_cli_neutron_commands.xml:3776(title) ./doc/common/ch_cli_neutron_commands.xml:3989(title) ./doc/common/ch_cli_neutron_commands.xml:4107(title) ./doc/common/ch_cli_neutron_commands.xml:4162(title) ./doc/common/ch_cli_neutron_commands.xml:4216(title) ./doc/common/ch_cli_neutron_commands.xml:4270(title) ./doc/common/ch_cli_neutron_commands.xml:4315(title) ./doc/common/ch_cli_neutron_commands.xml:4365(title) ./doc/common/ch_cli_neutron_commands.xml:4419(title) ./doc/common/ch_cli_neutron_commands.xml:4581(title) ./doc/common/ch_cli_neutron_commands.xml:4619(title) ./doc/common/ch_cli_neutron_commands.xml:4744(title) ./doc/common/ch_cli_neutron_commands.xml:4798(title) ./doc/common/ch_cli_neutron_commands.xml:4840(title) ./doc/common/ch_cli_neutron_commands.xml:4918(title) ./doc/common/ch_cli_neutron_commands.xml:5033(title) ./doc/common/ch_cli_neutron_commands.xml:5086(title) ./doc/common/ch_cli_neutron_commands.xml:5220(title) ./doc/common/ch_cli_neutron_commands.xml:5336(title) ./doc/common/ch_cli_neutron_commands.xml:5392(title) ./doc/common/ch_cli_neutron_commands.xml:5448(title) ./doc/common/ch_cli_neutron_commands.xml:5501(title) ./doc/common/ch_cli_neutron_commands.xml:5546(title) ./doc/common/ch_cli_neutron_commands.xml:5657(title) ./doc/common/ch_cli_neutron_commands.xml:5772(title) ./doc/common/ch_cli_neutron_commands.xml:5825(title) ./doc/common/ch_cli_neutron_commands.xml:5866(title) ./doc/common/ch_cli_neutron_commands.xml:5919(title) ./doc/common/ch_cli_neutron_commands.xml:6037(title) ./doc/common/ch_cli_neutron_commands.xml:6106(title) ./doc/common/ch_cli_neutron_commands.xml:6222(title) ./doc/common/ch_cli_neutron_commands.xml:6278(title) ./doc/common/ch_cli_neutron_commands.xml:6336(title) ./doc/common/ch_cli_neutron_commands.xml:6396(title) ./doc/common/ch_cli_neutron_commands.xml:6511(title) ./doc/common/ch_cli_neutron_commands.xml:6577(title) ./doc/common/ch_cli_neutron_commands.xml:6632(title) ./doc/common/ch_cli_neutron_commands.xml:6671(title) ./doc/common/ch_cli_neutron_commands.xml:6780(title) ./doc/common/ch_cli_neutron_commands.xml:6834(title) ./doc/common/ch_cli_neutron_commands.xml:6950(title) ./doc/common/ch_cli_neutron_commands.xml:7036(title) ./doc/common/ch_cli_neutron_commands.xml:7089(title) ./doc/common/ch_cli_neutron_commands.xml:7134(title) ./doc/common/ch_cli_neutron_commands.xml:7248(title) ./doc/common/ch_cli_neutron_commands.xml:7362(title) ./doc/common/ch_cli_neutron_commands.xml:7418(title) ./doc/common/ch_cli_neutron_commands.xml:7487(title) ./doc/common/ch_cli_neutron_commands.xml:7572(title) ./doc/common/ch_cli_neutron_commands.xml:7655(title) ./doc/common/ch_cli_neutron_commands.xml:7911(title) ./doc/common/ch_cli_neutron_commands.xml:7971(title) ./doc/common/ch_cli_neutron_commands.xml:8008(title) ./doc/common/ch_cli_neutron_commands.xml:8046(title) ./doc/common/ch_cli_neutron_commands.xml:8099(title) ./doc/common/ch_cli_neutron_commands.xml:8147(title) ./doc/common/ch_cli_neutron_commands.xml:8274(title) ./doc/common/ch_cli_neutron_commands.xml:8332(title) ./doc/common/ch_cli_neutron_commands.xml:8418(title) ./doc/common/ch_cli_neutron_commands.xml:8471(title) ./doc/common/ch_cli_neutron_commands.xml:8512(title) ./doc/common/ch_cli_neutron_commands.xml:8565(title) ./doc/common/ch_cli_neutron_commands.xml:8689(title) ./doc/common/ch_cli_neutron_commands.xml:8790(title) ./doc/common/ch_cli_neutron_commands.xml:8917(title) ./doc/common/ch_cli_neutron_commands.xml:8974(title) ./doc/common/ch_cli_neutron_commands.xml:9029(title) ./doc/common/ch_cli_neutron_commands.xml:9167(title) ./doc/common/ch_cli_neutron_commands.xml:9287(title) ./doc/common/ch_cli_neutron_commands.xml:9402(title) ./doc/common/ch_cli_neutron_commands.xml:9455(title) ./doc/common/ch_cli_neutron_commands.xml:9502(title) ./doc/common/ch_cli_neutron_commands.xml:9606(title) ./doc/common/ch_cli_neutron_commands.xml:9722(title) ./doc/common/ch_cli_neutron_commands.xml:9777(title) ./doc/common/ch_cli_neutron_commands.xml:9835(title) ./doc/common/ch_cli_neutron_commands.xml:9939(title) ./doc/common/ch_cli_neutron_commands.xml:10055(title) ./doc/common/ch_cli_neutron_commands.xml:10110(title) ./doc/common/ch_cli_neutron_commands.xml:10162(title) ./doc/common/ch_cli_neutron_commands.xml:10239(title) ./doc/common/ch_cli_neutron_commands.xml:10354(title) ./doc/common/ch_cli_neutron_commands.xml:10408(title) ./doc/common/ch_cli_heat_commands.xml:509(title) ./doc/common/ch_cli_heat_commands.xml:526(title) ./doc/common/ch_cli_heat_commands.xml:550(title) ./doc/common/ch_cli_heat_commands.xml:578(title) ./doc/common/ch_cli_heat_commands.xml:611(title) ./doc/common/ch_cli_heat_commands.xml:628(title) ./doc/common/ch_cli_heat_commands.xml:653(title) ./doc/common/ch_cli_heat_commands.xml:670(title) ./doc/common/ch_cli_heat_commands.xml:695(title) ./doc/common/ch_cli_heat_commands.xml:720(title) ./doc/common/ch_cli_heat_commands.xml:765(title) ./doc/common/ch_cli_heat_commands.xml:800(title) ./doc/common/ch_cli_heat_commands.xml:817(title) ./doc/common/ch_cli_heat_commands.xml:837(title) ./doc/common/ch_cli_heat_commands.xml:935(title) ./doc/common/ch_cli_heat_commands.xml:1022(title) ./doc/common/ch_cli_heat_commands.xml:1079(title) ./doc/common/ch_cli_heat_commands.xml:1157(title) ./doc/common/ch_cli_heat_commands.xml:1176(title) ./doc/common/ch_cli_heat_commands.xml:1246(title) ./doc/common/ch_cli_swift_commands.xml:338(title) ./doc/common/ch_cli_swift_commands.xml:402(title) ./doc/common/ch_cli_swift_commands.xml:516(title) ./doc/common/ch_cli_swift_commands.xml:581(title) ./doc/common/ch_cli_swift_commands.xml:664(title) ./doc/common/ch_cli_swift_commands.xml:703(title) ./doc/common/ch_cli_glance_commands.xml:694(title) ./doc/common/ch_cli_glance_commands.xml:851(title) ./doc/common/ch_cli_glance_commands.xml:889(title) ./doc/common/ch_cli_glance_commands.xml:1060(title) ./doc/common/ch_cli_glance_commands.xml:1096(title) ./doc/common/ch_cli_cinder_commands.xml:740(title) ./doc/common/ch_cli_cinder_commands.xml:784(title) ./doc/common/ch_cli_cinder_commands.xml:808(title) ./doc/common/ch_cli_cinder_commands.xml:836(title) ./doc/common/ch_cli_cinder_commands.xml:860(title) ./doc/common/ch_cli_cinder_commands.xml:952(title) ./doc/common/ch_cli_cinder_commands.xml:972(title) ./doc/common/ch_cli_cinder_commands.xml:1029(title) ./doc/common/ch_cli_cinder_commands.xml:1053(title) ./doc/common/ch_cli_cinder_commands.xml:1077(title) ./doc/common/ch_cli_cinder_commands.xml:1109(title) ./doc/common/ch_cli_cinder_commands.xml:1176(title) ./doc/common/ch_cli_cinder_commands.xml:1209(title) ./doc/common/ch_cli_cinder_commands.xml:1226(title) ./doc/common/ch_cli_cinder_commands.xml:1251(title) ./doc/common/ch_cli_cinder_commands.xml:1289(title) ./doc/common/ch_cli_cinder_commands.xml:1314(title) ./doc/common/ch_cli_cinder_commands.xml:1339(title) ./doc/common/ch_cli_cinder_commands.xml:1368(title) ./doc/common/ch_cli_cinder_commands.xml:1393(title) ./doc/common/ch_cli_cinder_commands.xml:1410(title) ./doc/common/ch_cli_cinder_commands.xml:1427(title) ./doc/common/ch_cli_cinder_commands.xml:1467(title) ./doc/common/ch_cli_cinder_commands.xml:1484(title) ./doc/common/ch_cli_cinder_commands.xml:1505(title) ./doc/common/ch_cli_cinder_commands.xml:1557(title) ./doc/common/ch_cli_cinder_commands.xml:1574(title) ./doc/common/ch_cli_cinder_commands.xml:1594(title) ./doc/common/ch_cli_cinder_commands.xml:1646(title) ./doc/common/ch_cli_cinder_commands.xml:1670(title) ./doc/common/ch_cli_cinder_commands.xml:1697(title) ./doc/common/ch_cli_cinder_commands.xml:1733(title) ./doc/common/ch_cli_cinder_commands.xml:1763(title) ./doc/common/ch_cli_cinder_commands.xml:1788(title) ./doc/common/ch_cli_cinder_commands.xml:1838(title) ./doc/common/ch_cli_cinder_commands.xml:1858(title) ./doc/common/ch_cli_cinder_commands.xml:1903(title) ./doc/common/ch_cli_cinder_commands.xml:1964(title) ./doc/common/ch_cli_cinder_commands.xml:1997(title) ./doc/common/ch_cli_cinder_commands.xml:2015(title) ./doc/common/ch_cli_cinder_commands.xml:2041(title) ./doc/common/ch_cli_cinder_commands.xml:2078(title) ./doc/common/ch_cli_cinder_commands.xml:2109(title) ./doc/common/ch_cli_cinder_commands.xml:2126(title) ./doc/common/ch_cli_cinder_commands.xml:2151(title) ./doc/common/ch_cli_cinder_commands.xml:2179(title) ./doc/common/ch_cli_cinder_commands.xml:2203(title) ./doc/common/ch_cli_cinder_commands.xml:2220(title) ./doc/common/ch_cli_cinder_commands.xml:2237(title) ./doc/common/ch_cli_cinder_commands.xml:2254(title) ./doc/common/ch_cli_cinder_commands.xml:2297(title) ./doc/common/ch_cli_trove_commands.xml:591(title) ./doc/common/ch_cli_trove_commands.xml:636(title) ./doc/common/ch_cli_trove_commands.xml:670(title) ./doc/common/ch_cli_trove_commands.xml:698(title) ./doc/common/ch_cli_trove_commands.xml:715(title) ./doc/common/ch_cli_trove_commands.xml:743(title) ./doc/common/ch_cli_trove_commands.xml:796(title) ./doc/common/ch_cli_trove_commands.xml:813(title) ./doc/common/ch_cli_trove_commands.xml:830(title) ./doc/common/ch_cli_trove_commands.xml:847(title) ./doc/common/ch_cli_trove_commands.xml:872(title) ./doc/common/ch_cli_trove_commands.xml:904(title) ./doc/common/ch_cli_trove_commands.xml:943(title) ./doc/common/ch_cli_trove_commands.xml:968(title) ./doc/common/ch_cli_trove_commands.xml:987(title) ./doc/common/ch_cli_trove_commands.xml:1039(title) ./doc/common/ch_cli_trove_commands.xml:1147(title) ./doc/common/ch_cli_trove_commands.xml:1191(title) ./doc/common/ch_cli_trove_commands.xml:1216(title) ./doc/common/ch_cli_trove_commands.xml:1240(title) ./doc/common/ch_cli_trove_commands.xml:1257(title) ./doc/common/ch_cli_trove_commands.xml:1275(title) ./doc/common/ch_cli_trove_commands.xml:1304(title) ./doc/common/ch_cli_trove_commands.xml:1328(title) ./doc/common/ch_cli_trove_commands.xml:1359(title) ./doc/common/ch_cli_trove_commands.xml:1384(title) ./doc/common/ch_cli_trove_commands.xml:1409(title) ./doc/common/ch_cli_trove_commands.xml:1426(title) ./doc/common/ch_cli_trove_commands.xml:1443(title) ./doc/common/ch_cli_trove_commands.xml:1460(title) ./doc/common/ch_cli_trove_commands.xml:1485(title) ./doc/common/ch_cli_trove_commands.xml:1509(title) ./doc/common/ch_cli_trove_commands.xml:1526(title) ./doc/common/ch_cli_trove_commands.xml:1545(title) ./doc/common/ch_cli_trove_commands.xml:1597(title) ./doc/common/ch_cli_trove_commands.xml:1634(title) ./doc/common/ch_cli_trove_commands.xml:1678(title) ./doc/common/ch_cli_trove_commands.xml:1695(title) ./doc/common/ch_cli_trove_commands.xml:1739(title) ./doc/common/ch_cli_trove_commands.xml:1775(title) ./doc/common/ch_cli_trove_commands.xml:1814(title)
 msgid "Positional arguments"
 msgstr ""
 
@@ -3559,26 +2659,184 @@ msgstr ""
 msgid "Filename to write the x509 root cert."
 msgstr ""
 
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_getstart_dashboard.xml:14(None)
-msgid "@@image: 'figures/horizon-screenshot.jpg'; md5=9471047adf0d93713be7f54b9db2b53c"
+#: ./doc/common/section_xapi-ami-setup.xml:7(title)
+msgid "Prepare for AMI type images"
 msgstr ""
 
-#: ./doc/common/section_getstart_dashboard.xml:5(title)
-msgid "OpenStack dashboard"
+#: ./doc/common/section_xapi-ami-setup.xml:8(para)
+msgid "To support AMI type images in your OpenStack installation, you must create a <filename>/boot/guest</filename> directory inside Dom0. The OpenStack VM extracts the kernel and ramdisk from the AKI and ARI images puts them in this location."
 msgstr ""
 
-#: ./doc/common/section_getstart_dashboard.xml:6(para)
-msgid "The OpenStack dashboard is a modular <link href=\"https://www.djangoproject.com/\">Django web application</link> that provides a graphical interface to OpenStack services."
+#: ./doc/common/section_xapi-ami-setup.xml:12(para)
+msgid "OpenStack maintains the contents of this directory and its size should not increase during normal operation. However, in case of power failures or accidental shutdowns, some files might be left over. To prevent these files from filling the Dom0 disk, set up this directory as a symlink that points to a subdirectory of the local SR."
 msgstr ""
 
-#: ./doc/common/section_getstart_dashboard.xml:18(para)
-msgid "The dashboard is usually deployed through <link href=\"http://code.google.com/p/modwsgi/\">mod_wsgi</link> in Apache. You can modify the dashboard code to make it suitable for different sites."
+#: ./doc/common/section_xapi-ami-setup.xml:18(para)
+msgid "Run these commands in Dom0 to achieve this setup:"
 msgstr ""
 
-#: ./doc/common/section_getstart_dashboard.xml:22(para)
-msgid "From a network architecture point of view, this service must be accessible to customers and the public API for each OpenStack service. To use the administrator functionality for other services, it must also connect to Admin API endpoints, which should not be accessible by customers."
+#: ./doc/common/section_dashboard-configure-http.xml:6(title)
+msgid "Configure the dashboard for HTTP"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-http.xml:8(para)
+msgid "You can configure the dashboard for a simple HTTP deployment. The standard installation uses a non-encrypted HTTP channel."
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-http.xml:12(para)
+msgid "Specify the host for your OpenStack Identity Service endpoint in the <filename>/etc/openstack-dashboard/local_settings.py</filename> file with the <literal>OPENSTACK_HOST</literal> setting."
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-http.xml:17(para)
+msgid "The following example shows this setting:"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-http.xml:19(para)
+msgid "The service catalog configuration in the Identity Service determines whether a service appears in the dashboard. For the full listing, see <link href=\"http://docs.openstack.org/developer/horizon/topics/settings.html\">Horizon Settings and Configuration</link>."
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-http.xml:28(para)
+msgid "Restart Apache http server. For Ubuntu/Debian/SUSE:"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-http.xml:30(para)
+msgid "or for Fedora/RHEL/CentOS:"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-http.xml:32(para) ./doc/common/section_dashboard-configure-https.xml:98(para)
+msgid "Next, restart memcached:"
+msgstr ""
+
+#: ./doc/common/section_rpc.xml:7(title) ./doc/common/section_rpc-for-networking.xml:7(title)
+msgid "Configure the Oslo RPC messaging system"
+msgstr ""
+
+#: ./doc/common/section_rpc.xml:8(para)
+msgid "OpenStack projects use AMQP, an open standard for messaging middleware. OpenStack services that run on multiple servers to talk to each other. OpenStack Oslo RPC supports three implementations of AMQP: <application>RabbitMQ</application>, <application>Qpid</application>, and <application>ZeroMQ</application>."
+msgstr ""
+
+#: ./doc/common/section_rpc.xml:15(title) ./doc/common/section_rpc-for-networking.xml:18(title)
+msgid "Configure RabbitMQ"
+msgstr ""
+
+#: ./doc/common/section_rpc.xml:16(para)
+msgid "OpenStack Oslo RPC uses <application>RabbitMQ</application> by default. Use these options to configure the <application>RabbitMQ</application> message system. The <literal>rpc_backend</literal> option is not required as long as <application>RabbitMQ</application> is the default messaging system. However, if it is included the configuration, you must set it to <literal>nova.openstack.common.rpc.impl_kombu</literal>."
+msgstr ""
+
+#: ./doc/common/section_rpc.xml:25(para)
+msgid "You can use these additional options to configure the <application>RabbitMQ</application> messaging system. You can configure messaging communication for different installation scenarios, tune retries for RabbitMQ, and define the size of the RPC thread pool. To monitor notifications through RabbitMQ, you must set the <option>notification_driver</option> option to <literal>nova.notifier.rabbit_notifier</literal> in the <filename>nova.conf</filename> file. The default for sending usage data is sixty seconds plus a random number of seconds from zero to sixty."
+msgstr ""
+
+#: ./doc/common/section_rpc.xml:39(title) ./doc/common/section_rpc-for-networking.xml:46(title)
+msgid "Configure Qpid"
+msgstr ""
+
+#: ./doc/common/section_rpc.xml:40(para)
+msgid "Use these options to configure the <application>Qpid</application> messaging system for OpenStack Oslo RPC. <application>Qpid</application> is not the default messaging system, so you must enable it by setting the <option>rpc_backend</option> option in the <filename>nova.conf</filename> file."
+msgstr ""
+
+#: ./doc/common/section_rpc.xml:47(para)
+msgid "This critical option points the compute nodes to the <application>Qpid</application> broker (server). Set <option>qpid_hostname</option> to the host name where the broker runs in the <filename>nova.conf</filename> file."
+msgstr ""
+
+#: ./doc/common/section_rpc.xml:52(para) ./doc/common/section_rpc-for-networking.xml:62(para)
+msgid "The <option>--qpid_hostname</option> option accepts a host name or IP address value."
+msgstr ""
+
+#: ./doc/common/section_rpc.xml:56(para) ./doc/common/section_rpc-for-networking.xml:69(para)
+msgid "If the <application>Qpid</application> broker listens on a port other than the AMQP default of <literal>5672</literal>, you must set the <option>qpid_port</option> option to that value:"
+msgstr ""
+
+#: ./doc/common/section_rpc.xml:61(para) ./doc/common/section_rpc-for-networking.xml:78(para)
+msgid "If you configure the <application>Qpid</application> broker to require authentication, you must add a user name and password to the configuration:"
+msgstr ""
+
+#: ./doc/common/section_rpc.xml:66(para) ./doc/common/section_rpc-for-networking.xml:87(para)
+msgid "By default, TCP is used as the transport. To enable SSL, set the <option>qpid_protocol</option> option:"
+msgstr ""
+
+#: ./doc/common/section_rpc.xml:69(para)
+msgid "This table lists additional options that you use to configure the Qpid messaging driver for OpenStack Oslo RPC. These options are used infrequently."
+msgstr ""
+
+#: ./doc/common/section_rpc.xml:75(title) ./doc/common/section_rpc-for-networking.xml:102(title)
+msgid "Configure ZeroMQ"
+msgstr ""
+
+#: ./doc/common/section_rpc.xml:76(para)
+msgid "Use these options to configure the <application>ZeroMQ</application> messaging system for OpenStack Oslo RPC. <application>ZeroMQ</application> is not the default messaging system, so you must enable it by setting the <option>rpc_backend</option> option in the <filename>nova.conf</filename> file."
+msgstr ""
+
+#: ./doc/common/section_rpc.xml:85(title) ./doc/common/section_rpc-for-networking.xml:112(title)
+msgid "Configure messaging"
+msgstr ""
+
+#: ./doc/common/section_rpc.xml:86(para)
+msgid "Use these options to configure the <application>RabbitMQ</application> and <application>Qpid</application> messaging drivers."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml:6(title)
+msgid "User management"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml:7(para)
+msgid "The main components of Identity user management are:"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml:10(para)
+msgid "<emphasis role=\"bold\">User</emphasis>. Represents a human user. Has associated information such as user name, password, and email. This example creates a user named <literal>alice</literal>:"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml:17(para)
+msgid "<emphasis role=\"bold\">Tenant</emphasis>. A project, group, or organization. When you make requests to OpenStack services, you must specify a tenant. For example, if you query the Compute service for a list of running instances, you get a list of all running instances in the tenant that you specified in your query. This example creates a tenant named <literal>acme</literal>:"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml:27(para)
+msgid "Because the term <emphasis>project</emphasis> was used instead of <emphasis>tenant</emphasis> in earlier versions of OpenStack Compute, some command-line tools use <literal>--project_id</literal> instead of <literal>--tenant-id</literal> or <literal>--os-tenant-id</literal> to refer to a tenant ID."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml:38(para)
+msgid "<emphasis role=\"bold\">Role</emphasis>. Captures the operations that a user can perform in a given tenant."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml:40(para)
+msgid "This example creates a role named <literal>compute-user</literal>:"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml:44(para)
+msgid "Individual services, such as Compute and the Image Service, assign meaning to roles. In the Identity Service, a role is simply a name."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml:51(para)
+msgid "The Identity Service assigns a tenant and a role to a user. You might assign the <literal>compute-user</literal> role to the <literal>alice</literal> user in the <literal>acme</literal> tenant:"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml:74(para)
+msgid "A user can have different roles in different tenants. For example, Alice might also have the <literal>admin</literal> role in the <literal>Cyberdyne</literal> tenant. A user can also have multiple roles in the same tenant."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml:78(para)
+msgid "The <filename>/etc/<replaceable>[SERVICE_CODENAME]</replaceable>/policy.json</filename> file controls the tasks that users can perform for a given service. For example, <filename>/etc/nova/policy.json</filename> specifies the access policy for the Compute service, <filename>/etc/glance/policy.json</filename> specifies the access policy for the Image Service, and <filename>/etc/keystone/policy.json</filename> specifies the access policy for the Identity Service."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml:88(para)
+msgid "The default <filename>policy.json</filename> files in the Compute, Identity, and Image Service recognize only the <literal>admin</literal> role: all operations that do not require the <literal>admin</literal> role are accessible by any user that has any role in a tenant."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml:93(para)
+msgid "If you wish to restrict users from performing operations in, say, the Compute service, you need to create a role in the Identity Service and then modify <filename>/etc/nova/policy.json</filename> so that this role is required for Compute operations."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml:99(para)
+msgid "For example, this line in <filename>/etc/nova/policy.json</filename> specifies that there are no restrictions on which users can create volumes: if the user has any role in a tenant, they can create volumes in that tenant."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml:105(para)
+msgid "To restrict creation of volumes to users who had the <literal>compute-user</literal> role in a particular tenant, you would add <literal>\"role:compute-user\"</literal>, like so:"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml:110(para)
+msgid "To restrict all Compute service requests to require this role, the resulting file would look like:"
 msgstr ""
 
 #: ./doc/common/section_cli_nova_quotas.xml:6(title)
@@ -3597,7 +2855,7 @@ msgstr ""
 msgid "Quota name"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_quotas.xml:20(th) ./doc/common/ch_getstart.xml:31(th) ./doc/common/section_cli_nova_customize_flavors.xml:40(td) ./doc/common/section_cli_overview.xml:36(th) ./doc/common/section_cli_install.xml:22(th) ./doc/common/tables/nova-cells.xml:14(th) ./doc/common/tables/trove-db_mongodb.xml:14(th) ./doc/common/tables/keystone-debug.xml:14(th) ./doc/common/tables/glance-policy.xml:14(th) ./doc/common/tables/neutron-mlnx.xml:14(th) ./doc/common/tables/nova-ipv6.xml:14(th) ./doc/common/tables/cinder-eqlx.xml:14(th) ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml:13(th) ./doc/common/tables/swift-object-expirer-filter-cache.xml:13(th) ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-cache.xml:13(th) ./doc/common/tables/nova-rpc_all.xml:14(th) ./doc/common/tables/neutron-ml2_l2pop.xml:14(th) ./doc/common/tables/glance-qpid.xml:14(th) ./doc/common/tables/swift-container-server-DEFAULT.xml:13(th) ./doc/common/tables/neutron-ml2_bigswitch.xml:14(th) ./doc/common/tables/neutron-ml2_gre.xml:14(th) ./doc/common/tables/nova-volumes.xml:14(th) ./doc/common/tables/glance-gridfs.xml:14(th) ./doc/common/tables/neutron-ml2_arista.xml:14(th) ./doc/common/tables/glance-filesystem.xml:14(th) ./doc/common/tables/heat-redis.xml:14(th) ./doc/common/tables/trove-logging.xml:14(th) ./doc/common/tables/swift-container-server-container-updater.xml:13(th) ./doc/common/tables/cinder-storage_gpfs.xml:14(th) ./doc/common/tables/cinder-nexenta_iscsi.xml:14(th) ./doc/common/tables/nova-tilera.xml:14(th) ./doc/common/tables/nova-ca.xml:14(th) ./doc/common/tables/heat-clients_nova.xml:14(th) ./doc/common/tables/swift-account-server-filter-recon.xml:13(th) ./doc/common/tables/cinder-huawei.xml:14(th) ./doc/common/tables/keystone-qpid.xml:14(th) ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:14(th) ./doc/common/tables/swift-container-server-container-replicator.xml:13(th) ./doc/common/tables/nova-glance.xml:14(th) ./doc/common/tables/neutron-dhcp_agent.xml:14(th) ./doc/common/tables/nova-neutron.xml:14(th) ./doc/common/tables/cinder-backups_ceph.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-name_check.xml:13(th) ./doc/common/tables/nova-metadata.xml:14(th) ./doc/common/tables/glance-s3.xml:14(th) ./doc/common/tables/glance-auth_token.xml:14(th) ./doc/common/tables/neutron-kombu.xml:14(th) ./doc/common/tables/trove-redis.xml:14(th) ./doc/common/tables/trove-qpid.xml:14(th) ./doc/common/tables/trove-compute.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:13(th) ./doc/common/tables/trove-nova.xml:14(th) ./doc/common/tables/ceilometer-cells.xml:14(th) ./doc/common/tables/keystone-oauth.xml:14(th) ./doc/common/tables/cinder-block-device.xml:14(th) ./doc/common/tables/cinder-zones.xml:14(th) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:14(th) ./doc/common/tables/swift-container-server-container-sync.xml:13(th) ./doc/common/tables/neutron-common.xml:14(th) ./doc/common/tables/neutron-compute.xml:14(th) ./doc/common/tables/swift-object-server-object-auditor.xml:13(th) ./doc/common/tables/keystone-ldap.xml:14(th) ./doc/common/tables/heat-rpc.xml:14(th) ./doc/common/tables/neutron-openvswitch_agent.xml:14(th) ./doc/common/tables/cinder-compute.xml:14(th) ./doc/common/tables/keystone-identity.xml:14(th) ./doc/common/tables/cinder-lvm.xml:14(th) ./doc/common/tables/keystone-trust.xml:14(th) ./doc/common/tables/cinder-storage_nfs.xml:14(th) ./doc/common/tables/neutron-plumgrid.xml:14(th) ./doc/common/tables/heat-cfn_api.xml:14(th) ./doc/common/tables/nova-hypervisor.xml:14(th) ./doc/common/tables/trove-rabbitmq.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:13(th) ./doc/common/tables/trove-api.xml:14(th) ./doc/common/tables/cinder-quota.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml:13(th) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:13(th) ./doc/common/tables/nova-console.xml:14(th) ./doc/common/tables/ceilometer-events.xml:14(th) ./doc/common/tables/keystone-os_inherit.xml:14(th) ./doc/common/tables/heat-clients.xml:14(th) ./doc/common/tables/heat-notification.xml:14(th) ./doc/common/tables/keystone-assignment.xml:14(th) ./doc/common/tables/nova-common.xml:14(th) ./doc/common/tables/swift-object-server-object-updater.xml:13(th) ./doc/common/tables/glance-zmq.xml:14(th) ./doc/common/tables/neutron-metering_agent.xml:14(th) ./doc/common/tables/trove-taskmanager.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml:13(th) ./doc/common/tables/keystone-zeromq.xml:14(th) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:13(th) ./doc/common/tables/nova-keymgr.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-dlo.xml:13(th) ./doc/common/tables/neutron-api.xml:14(th) ./doc/common/tables/ceilometer-redis.xml:14(th) ./doc/common/tables/ceilometer-swift.xml:14(th) ./doc/common/tables/cinder-hplefthand.xml:14(th) ./doc/common/tables/heat-qpid.xml:14(th) ./doc/common/tables/nova-testing.xml:14(th) ./doc/common/tables/cinder-backups.xml:14(th) ./doc/common/tables/swift-container-server-pipeline-main.xml:13(th) ./doc/common/tables/neutron-ml2_ofa.xml:14(th) ./doc/common/tables/trove-debug.xml:14(th) ./doc/common/tables/swift-rsyncd-object.xml:13(th) ./doc/common/tables/nova-s3.xml:14(th) ./doc/common/tables/nova-zookeeper.xml:14(th) ./doc/common/tables/cinder-rpc.xml:14(th) ./doc/common/tables/cinder-api.xml:14(th) ./doc/common/tables/cinder-windows.xml:14(th) ./doc/common/tables/glance-vmware.xml:14(th) ./doc/common/tables/swift-object-server-pipeline-main.xml:13(th) ./doc/common/tables/trove-backup.xml:14(th) ./doc/common/tables/nova-auth_token.xml:14(th) ./doc/common/tables/cinder-san.xml:14(th) ./doc/common/tables/swift-account-server-app-account-server.xml:13(th) ./doc/common/tables/keystone-rpc.xml:14(th) ./doc/common/tables/cinder-keymgr.xml:14(th) ./doc/common/tables/nova-db.xml:14(th) ./doc/common/tables/neutron-ml2_vxlan.xml:14(th) ./doc/common/tables/glance-logging.xml:14(th) ./doc/common/tables/cinder-zoning.xml:14(th) ./doc/common/tables/glance-wsgi.xml:14(th) ./doc/common/tables/nova-periodic.xml:14(th) ./doc/common/tables/swift-account-server-filter-healthcheck.xml:13(th) ./doc/common/tables/cinder-images.xml:14(th) ./doc/common/tables/trove-swift.xml:14(th) ./doc/common/tables/swift-container-server-app-container-server.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-slo.xml:13(th) ./doc/common/tables/cinder-auth_token.xml:14(th) ./doc/common/tables/heat-crypt.xml:14(th) ./doc/common/tables/neutron-wsgi.xml:14(th) ./doc/common/tables/neutron-scheduler.xml:14(th) ./doc/common/tables/keystone-security.xml:14(th) ./doc/common/tables/ceilometer-vmware.xml:14(th) ./doc/common/tables/glance-rbd.xml:14(th) ./doc/common/tables/heat-clients_heat.xml:14(th) ./doc/common/tables/heat-rabbitmq.xml:14(th) ./doc/common/tables/ceilometer-logging.xml:14(th) ./doc/common/tables/neutron-metadata.xml:14(th) ./doc/common/tables/glance-redis.xml:14(th) ./doc/common/tables/keystone-stats.xml:14(th) ./doc/common/tables/cinder-hp3par.xml:14(th) ./doc/common/tables/cinder-storage_ceph.xml:14(th) ./doc/common/tables/nova-livemigration.xml:14(th) ./doc/common/tables/nova-ldap.xml:14(th) ./doc/common/tables/nova-fping.xml:14(th) ./doc/common/tables/heat-clients_swift.xml:14(th) ./doc/common/tables/neutron-securitygroups.xml:14(th) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:14(th) ./doc/common/tables/nova-ec2.xml:14(th) ./doc/common/tables/swift-account-server-account-auditor.xml:13(th) ./doc/common/tables/trove-zeromq.xml:14(th) ./doc/common/tables/heat-database.xml:14(th) ./doc/common/tables/keystone-catalog.xml:14(th) ./doc/common/tables/swift-object-server-DEFAULT.xml:13(th) ./doc/common/tables/cinder-rootwrap.xml:14(th) ./doc/common/tables/ceilometer-database.xml:14(th) ./doc/common/tables/heat-debug.xml:14(th) ./doc/common/tables/cinder-nexenta_nfs.xml:14(th) ./doc/common/tables/trove-auth_token.xml:14(th) ./doc/common/tables/heat-waitcondition_api.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:13(th) ./doc/common/tables/neutron-ml2_vlan.xml:14(th) ./doc/common/tables/nova-policy.xml:14(th) ./doc/common/tables/keystone-amqp.xml:14(th) ./doc/common/tables/neutron-logging.xml:14(th) ./doc/common/tables/trove-db_cassandra.xml:14(th) ./doc/common/tables/glance-rpc.xml:14(th) ./doc/common/tables/nova-authentication.xml:14(th) ./doc/common/tables/cinder-vmware.xml:14(th) ./doc/common/tables/glance-sheepdog.xml:14(th) ./doc/common/tables/heat-logging.xml:14(th) ./doc/common/tables/keystone-notification.xml:14(th) ./doc/common/tables/neutron-qpid.xml:14(th) ./doc/common/tables/neutron-hyperv_agent.xml:14(th) ./doc/common/tables/glance-swift.xml:14(th) ./doc/common/tables/swift-account-server-DEFAULT.xml:13(th) ./doc/common/tables/neutron-bigswitch.xml:14(th) ./doc/common/tables/nova-libvirt.xml:14(th) ./doc/common/tables/neutron-lbaas.xml:14(th) ./doc/common/tables/cinder-backups_swift.xml:14(th) ./doc/common/tables/neutron-ml2_cisco.xml:14(th) ./doc/common/tables/ceilometer-rpc.xml:14(th) ./doc/common/tables/heat-loadbalancer.xml:14(th) ./doc/common/tables/heat-cloudwatch_api.xml:14(th) ./doc/common/tables/nova-pci.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:13(th) ./doc/common/tables/heat-clients_ceilometer.xml:14(th) ./doc/common/tables/neutron-varmour.xml:14(th) ./doc/common/tables/glance-imagecache.xml:14(th) ./doc/common/tables/trove-quota.xml:14(th) ./doc/common/tables/swift-rsyncd-account.xml:13(th) ./doc/common/tables/cinder-storage.xml:14(th) ./doc/common/tables/cinder-nas.xml:14(th) ./doc/common/tables/nova-vpn.xml:14(th) ./doc/common/tables/nova-wsgi.xml:14(th) ./doc/common/tables/cinder-storage_glusterfs.xml:14(th) ./doc/common/tables/swift-container-sync-realms-realm1.xml:13(th) ./doc/common/tables/swift-container-server-filter-healthcheck.xml:13(th) ./doc/common/tables/nova-availabilityzones.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-container_sync.xml:13(th) ./doc/common/tables/heat-zeromq.xml:14(th) ./doc/common/tables/keystone-memcache.xml:14(th) ./doc/common/tables/nova-vnc.xml:14(th) ./doc/common/tables/swift-swift-swift-constraints.xml:13(th) ./doc/common/tables/neutron-cisco.xml:14(th) ./doc/common/tables/keystone-logging.xml:14(th) ./doc/common/tables/nova-hyperv.xml:14(th) ./doc/common/tables/neutron-l3_agent.xml:14(th) ./doc/common/tables/swift-object-server-filter-recon.xml:13(th) ./doc/common/tables/cinder-coraid.xml:14(th) ./doc/common/tables/swift-container-server-container-auditor.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:13(th) ./doc/common/tables/nova-vmware.xml:14(th) ./doc/common/tables/nova-logging.xml:14(th) ./doc/common/tables/nova-xen.xml:14(th) ./doc/common/tables/ceilometer-collector.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml:13(th) ./doc/common/tables/keystone-ec2.xml:14(th) ./doc/common/tables/keystone-auth.xml:14(th) ./doc/common/tables/swift-memcache-memcache.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:13(th) ./doc/common/tables/neutron-ml2.xml:14(th) ./doc/common/tables/ceilometer-api.xml:14(th) ./doc/common/tables/heat-clients_trove.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:13(th) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:14(th) ./doc/common/tables/glance-common.xml:14(th) ./doc/common/tables/nova-network.xml:14(th) ./doc/common/tables/cinder-scality.xml:14(th) ./doc/common/tables/neutron-notifier.xml:14(th) ./doc/common/tables/cinder-common.xml:14(th) ./doc/common/tables/nova-trustedcomputing.xml:14(th) ./doc/common/tables/neutron-ml2_flat.xml:14(th) ./doc/common/tables/heat-clients_cinder.xml:14(th) ./doc/common/tables/nova-configdrive.xml:14(th) ./doc/common/tables/cinder-database.xml:14(th) ./doc/common/tables/neutron-rpc.xml:14(th) ./doc/common/tables/cinder-zoning_manager.xml:14(th) ./doc/common/tables/trove-volume.xml:14(th) ./doc/common/tables/keystone-cache.xml:14(th) ./doc/common/tables/nova-zeromq.xml:14(th) ./doc/common/tables/glance-testing.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:13(th) ./doc/common/tables/glance-registry.xml:14(th) ./doc/common/tables/glance-amqp.xml:14(th) ./doc/common/tables/swift-object-server-object-replicator.xml:13(th) ./doc/common/tables/trove-database.xml:14(th) ./doc/common/tables/heat-clients_backends.xml:14(th) ./doc/common/tables/heat-amqp.xml:14(th) ./doc/common/tables/swift-dispersion-dispersion.xml:13(th) ./doc/common/tables/cinder-hpmsa.xml:14(th) ./doc/common/tables/cinder-emc.xml:14(th) ./doc/common/tables/swift-account-server-account-replicator.xml:13(th) ./doc/common/tables/neutron-fwaas.xml:14(th) ./doc/common/tables/glance-rabbitmq.xml:14(th) ./doc/common/tables/cinder-backups_tsm.xml:14(th) ./doc/common/tables/neutron-sdnve.xml:14(th) ./doc/common/tables/trove-db_mysql.xml:14(th) ./doc/common/tables/nova-qpid.xml:14(th) ./doc/common/tables/trove-rpc.xml:14(th) ./doc/common/tables/cinder-connection.xml:14(th) ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:13(th) ./doc/common/tables/trove-db_redis.xml:14(th) ./doc/common/tables/ceilometer-qpid.xml:14(th) ./doc/common/tables/neutron-zeromq.xml:14(th) ./doc/common/tables/keystone-token.xml:14(th) ./doc/common/tables/neutron-vpn.xml:14(th) ./doc/common/tables/neutron-agent.xml:14(th) ./doc/common/tables/neutron-ryu.xml:14(th) ./doc/common/tables/swift-object-server-app-object-server.xml:13(th) ./doc/common/tables/trove-db_couchbase.xml:14(th) ./doc/common/tables/neutron-policy.xml:14(th) ./doc/common/tables/neutron-rootwrap.xml:14(th) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-staticweb.xml:13(th) ./doc/common/tables/trove-common.xml:14(th) ./doc/common/tables/cinder-ssl.xml:14(th) ./doc/common/tables/heat-api.xml:14(th) ./doc/common/tables/trove-db_percona.xml:14(th) ./doc/common/tables/swift-object-expirer-app-proxy-server.xml:13(th) ./doc/common/tables/ceilometer-amqp.xml:14(th) ./doc/common/tables/keystone-auth_token.xml:14(th) ./doc/common/tables/neutron-meta.xml:14(th) ./doc/common/tables/neutron-redis.xml:14(th) ./doc/common/tables/neutron-ssl.xml:14(th) ./doc/common/tables/ceilometer-exchange.xml:14(th) ./doc/common/tables/ceilometer-common.xml:14(th) ./doc/common/tables/ceilometer-alarm.xml:14(th) ./doc/common/tables/keystone-misc.xml:14(th) ./doc/common/tables/nova-scheduling.xml:14(th) ./doc/common/tables/ceilometer-auth.xml:14(th) ./doc/common/tables/swift-drive-audit-drive-audit.xml:13(th) ./doc/common/tables/neutron-ml2_mlnx.xml:14(th) ./doc/common/tables/swift-container-server-filter-recon.xml:13(th) ./doc/common/tables/trove-dns.xml:14(th) ./doc/common/tables/neutron-db.xml:14(th) ./doc/common/tables/neutron-ml2_brocade.xml:14(th) ./doc/common/tables/neutron-brocade.xml:14(th) ./doc/common/tables/keystone-redis.xml:14(th) ./doc/common/tables/heat-auth_token.xml:14(th) ./doc/common/tables/keystone-database.xml:14(th) ./doc/common/tables/swift-object-expirer-pipeline-main.xml:13(th) ./doc/common/tables/heat-clients_neutron.xml:14(th) ./doc/common/tables/neutron-linuxbridge_agent.xml:14(th) ./doc/common/tables/cinder-xiv.xml:14(th) ./doc/common/tables/cinder-hds-hus.xml:14(th) ./doc/common/tables/neutron-rabbitmq.xml:14(th) ./doc/common/tables/keystone-kvs.xml:14(th) ./doc/common/tables/trove-ssl.xml:14(th) ./doc/common/tables/keystone-policy.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml:13(th) ./doc/common/tables/swift-swift-swift-hash.xml:13(th) ./doc/common/tables/cinder-auth.xml:14(th) ./doc/common/tables/nova-kombu.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-formpost.xml:13(th) ./doc/common/tables/neutron-ml2_odl.xml:14(th) ./doc/common/tables/heat-quota.xml:14(th) ./doc/common/tables/nova-spice.xml:14(th) ./doc/common/tables/cinder-zoning_fabric.xml:14(th) ./doc/common/tables/neutron-midonet.xml:14(th) ./doc/common/tables/neutron-nvsd.xml:14(th) ./doc/common/tables/neutron-embrane_lb.xml:14(th) ./doc/common/tables/neutron-auth_token.xml:14(th) ./doc/common/tables/cinder-storwize.xml:14(th) ./doc/common/tables/nova-rootwrap.xml:14(th) ./doc/common/tables/cinder-solidfire.xml:14(th) ./doc/common/tables/keystone-revoke.xml:14(th) ./doc/common/tables/glance-ssl.xml:14(th) ./doc/common/tables/heat-metadata_api.xml:14(th) ./doc/common/tables/nova-apiv3.xml:14(th) ./doc/common/tables/glance-db.xml:14(th) ./doc/common/tables/neutron-vmware.xml:14(th) ./doc/common/tables/swift-container-sync-realms-realm2.xml:13(th) ./doc/common/tables/nova-api.xml:14(th) ./doc/common/tables/glance-matchmaker.xml:14(th) ./doc/common/tables/keystone-ssl.xml:14(th) ./doc/common/tables/swift-rsyncd-container.xml:13(th) ./doc/common/tables/cinder-san-solaris.xml:14(th) ./doc/common/tables/trove-heat.xml:14(th) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:14(th) ./doc/common/tables/swift-object-server-filter-healthcheck.xml:13(th) ./doc/common/tables/glance-paste.xml:14(th) ./doc/common/tables/nova-rdp.xml:14(th) ./doc/common/tables/neutron-quotas.xml:14(th) ./doc/common/tables/nova-rpc.xml:14(th) ./doc/common/tables/trove-guestagent.xml:14(th) ./doc/common/tables/nova-baremetal.xml:14(th) ./doc/common/tables/heat-clients_keystone.xml:14(th) ./doc/common/tables/swift-account-server-pipeline-main.xml:13(th) ./doc/common/tables/keystone-rabbit.xml:14(th) ./doc/common/tables/glance-api.xml:14(th) ./doc/common/tables/cinder-scheduler.xml:14(th) ./doc/common/tables/keystone-api.xml:14(th) ./doc/common/tables/neutron-ml2_ncs.xml:14(th) ./doc/common/tables/neutron-nec.xml:14(th) ./doc/common/tables/ceilometer-rabbitmq.xml:14(th) ./doc/common/tables/neutron-cadf.xml:14(th) ./doc/common/tables/neutron-testing.xml:14(th) ./doc/common/tables/swift-object-expirer-object-expirer.xml:13(th) ./doc/common/tables/glance-cinder.xml:14(th) ./doc/common/tables/nova-redis.xml:14(th) ./doc/common/tables/neutron-embrane.xml:14(th) ./doc/common/tables/swift-proxy-server-pipeline-main.xml:13(th) ./doc/common/tables/nova-upgrade_levels.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:13(th) ./doc/common/tables/ceilometer-inspector.xml:14(th) ./doc/common/tables/nova-rabbitmq.xml:14(th) ./doc/common/tables/heat-common.xml:14(th) ./doc/common/tables/keystone-federation.xml:14(th) ./doc/common/tables/cinder-zadara.xml:14(th) ./doc/common/tables/neutron-nuage.xml:14(th) ./doc/common/tables/swift-account-server-account-reaper.xml:13(th) ./doc/common/tables/ceilometer-ssl.xml:14(th) ./doc/common/tables/nova-quota.xml:14(th) ./doc/common/tables/nova-conductor.xml:14(th) ./doc/common/tables/nova-compute.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:13(th) ./doc/common/tables/cinder-storage_xen.xml:14(th) ./doc/common/tables/keystone-credential.xml:14(th) ./doc/common/tables/trove-amqp.xml:14(th) ./doc/common/tables/nova-xvpnvncproxy.xml:14(th)
+#: ./doc/common/section_cli_nova_quotas.xml:20(th) ./doc/common/section_cli_nova_customize_flavors.xml:40(td) ./doc/common/section_cli_overview.xml:43(th) ./doc/common/section_cli_install.xml:30(th) ./doc/common/ch_getstart.xml:31(th) ./doc/common/tables/ceilometer-database.xml:14(th) ./doc/common/tables/neutron-openvswitch_agent.xml:14(th) ./doc/common/tables/heat-clients.xml:14(th) ./doc/common/tables/cinder-solidfire.xml:14(th) ./doc/common/tables/neutron-rpc.xml:14(th) ./doc/common/tables/trove-db_percona.xml:14(th) ./doc/common/tables/nova-periodic.xml:14(th) ./doc/common/tables/keystone-auth.xml:14(th) ./doc/common/tables/keystone-policy.xml:14(th) ./doc/common/tables/glance-auth_token.xml:14(th) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:14(th) ./doc/common/tables/swift-container-server-container-sync.xml:13(th) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:13(th) ./doc/common/tables/cinder-zoning_fabric.xml:14(th) ./doc/common/tables/ceilometer-redis.xml:14(th) ./doc/common/tables/cinder-storage_ceph.xml:14(th) ./doc/common/tables/ceilometer-vmware.xml:14(th) ./doc/common/tables/neutron-cisco.xml:14(th) ./doc/common/tables/nova-testing.xml:14(th) ./doc/common/tables/nova-metadata.xml:14(th) ./doc/common/tables/heat-clients_nova.xml:14(th) ./doc/common/tables/cinder-hp3par.xml:14(th) ./doc/common/tables/keystone-misc.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:13(th) ./doc/common/tables/neutron-scheduler.xml:14(th) ./doc/common/tables/glance-rbd.xml:14(th) ./doc/common/tables/cinder-storage_xen.xml:14(th) ./doc/common/tables/ceilometer-common.xml:14(th) ./doc/common/tables/cinder-database.xml:14(th) ./doc/common/tables/ceilometer-logging.xml:14(th) ./doc/common/tables/heat-common.xml:14(th) ./doc/common/tables/nova-ipv6.xml:14(th) ./doc/common/tables/nova-vnc.xml:14(th) ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:13(th) ./doc/common/tables/trove-qpid.xml:14(th) ./doc/common/tables/keystone-api.xml:14(th) ./doc/common/tables/swift-object-expirer-pipeline-main.xml:13(th) ./doc/common/tables/swift-container-server-container-auditor.xml:13(th) ./doc/common/tables/glance-rpc.xml:14(th) ./doc/common/tables/neutron-policy.xml:14(th) ./doc/common/tables/nova-spice.xml:14(th) ./doc/common/tables/heat-clients_heat.xml:14(th) ./doc/common/tables/nova-xen.xml:14(th) ./doc/common/tables/trove-amqp.xml:14(th) ./doc/common/tables/glance-matchmaker.xml:14(th) ./doc/common/tables/nova-rabbitmq.xml:14(th) ./doc/common/tables/neutron-ml2_cisco.xml:14(th) ./doc/common/tables/nova-policy.xml:14(th) ./doc/common/tables/keystone-identity.xml:14(th) ./doc/common/tables/ceilometer-inspector.xml:14(th) ./doc/common/tables/cinder-scheduler.xml:14(th) ./doc/common/tables/trove-db_cassandra.xml:14(th) ./doc/common/tables/neutron-logging.xml:14(th) ./doc/common/tables/nova-availabilityzones.xml:14(th) ./doc/common/tables/keystone-catalog.xml:14(th) ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:14(th) ./doc/common/tables/neutron-rootwrap.xml:14(th) ./doc/common/tables/cinder-auth.xml:14(th) ./doc/common/tables/swift-swift-swift-constraints.xml:13(th) ./doc/common/tables/heat-qpid.xml:14(th) ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-slo.xml:13(th) ./doc/common/tables/nova-zookeeper.xml:14(th) ./doc/common/tables/nova-keymgr.xml:14(th) ./doc/common/tables/neutron-auth_token.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-cache.xml:13(th) ./doc/common/tables/nova-ldap.xml:14(th) ./doc/common/tables/swift-container-server-filter-recon.xml:13(th) ./doc/common/tables/swift-proxy-server-pipeline-main.xml:13(th) ./doc/common/tables/ceilometer-auth.xml:14(th) ./doc/common/tables/cinder-quota.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml:13(th) ./doc/common/tables/keystone-os_inherit.xml:14(th) ./doc/common/tables/neutron-sdnve.xml:14(th) ./doc/common/tables/nova-compute.xml:14(th) ./doc/common/tables/keystone-rabbit.xml:14(th) ./doc/common/tables/cinder-backups_ceph.xml:14(th) ./doc/common/tables/nova-vmware.xml:14(th) ./doc/common/tables/heat-cfn_api.xml:14(th) ./doc/common/tables/neutron-vmware.xml:14(th) ./doc/common/tables/nova-rdp.xml:14(th) ./doc/common/tables/keystone-assignment.xml:14(th) ./doc/common/tables/nova-zeromq.xml:14(th) ./doc/common/tables/cinder-storage.xml:14(th) ./doc/common/tables/glance-registry.xml:14(th) ./doc/common/tables/neutron-embrane.xml:14(th) ./doc/common/tables/heat-quota.xml:14(th) ./doc/common/tables/swift-account-server-filter-healthcheck.xml:13(th) ./doc/common/tables/nova-common.xml:14(th) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:13(th) ./doc/common/tables/nova-volumes.xml:14(th) ./doc/common/tables/neutron-redis.xml:14(th) ./doc/common/tables/trove-db_mysql.xml:14(th) ./doc/common/tables/heat-zeromq.xml:14(th) ./doc/common/tables/heat-amqp.xml:14(th) ./doc/common/tables/neutron-linuxbridge_agent.xml:14(th) ./doc/common/tables/nova-redis.xml:14(th) ./doc/common/tables/swift-container-server-DEFAULT.xml:13(th) ./doc/common/tables/nova-db.xml:14(th) ./doc/common/tables/glance-rabbitmq.xml:14(th) ./doc/common/tables/neutron-l3_agent.xml:14(th) ./doc/common/tables/swift-container-server-pipeline-main.xml:13(th) ./doc/common/tables/glance-policy.xml:14(th) ./doc/common/tables/nova-neutron.xml:14(th) ./doc/common/tables/cinder-backups.xml:14(th) ./doc/common/tables/cinder-keymgr.xml:14(th) ./doc/common/tables/ceilometer-cells.xml:14(th) ./doc/common/tables/keystone-ldap.xml:14(th) ./doc/common/tables/glance-vmware.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml:13(th) ./doc/common/tables/cinder-zoning.xml:14(th) ./doc/common/tables/heat-notification.xml:14(th) ./doc/common/tables/swift-container-server-filter-healthcheck.xml:13(th) ./doc/common/tables/nova-vpn.xml:14(th) ./doc/common/tables/neutron-vpn.xml:14(th) ./doc/common/tables/swift-object-expirer-object-expirer.xml:13(th) ./doc/common/tables/trove-common.xml:14(th) ./doc/common/tables/trove-api.xml:14(th) ./doc/common/tables/cinder-zadara.xml:14(th) ./doc/common/tables/swift-object-server-filter-healthcheck.xml:13(th) ./doc/common/tables/nova-conductor.xml:14(th) ./doc/common/tables/swift-object-server-app-object-server.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:13(th) ./doc/common/tables/nova-livemigration.xml:14(th) ./doc/common/tables/heat-rabbitmq.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:13(th) ./doc/common/tables/neutron-cadf.xml:14(th) ./doc/common/tables/keystone-amqp.xml:14(th) ./doc/common/tables/keystone-rpc.xml:14(th) ./doc/common/tables/swift-object-server-DEFAULT.xml:13(th) ./doc/common/tables/cinder-zones.xml:14(th) ./doc/common/tables/cinder-scality.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:13(th) ./doc/common/tables/neutron-agent.xml:14(th) ./doc/common/tables/cinder-emc.xml:14(th) ./doc/common/tables/cinder-vmware.xml:14(th) ./doc/common/tables/neutron-ml2_flat.xml:14(th) ./doc/common/tables/heat-metadata_api.xml:14(th) ./doc/common/tables/trove-rabbitmq.xml:14(th) ./doc/common/tables/nova-upgrade_levels.xml:14(th) ./doc/common/tables/neutron-kombu.xml:14(th) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:14(th) ./doc/common/tables/neutron-ml2_ofa.xml:14(th) ./doc/common/tables/glance-api.xml:14(th) ./doc/common/tables/heat-waitcondition_api.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:13(th) ./doc/common/tables/swift-rsyncd-container.xml:13(th) ./doc/common/tables/cinder-storwize.xml:14(th) ./doc/common/tables/cinder-hplefthand.xml:14(th) ./doc/common/tables/glance-s3.xml:14(th) ./doc/common/tables/nova-rootwrap.xml:14(th) ./doc/common/tables/heat-loadbalancer.xml:14(th) ./doc/common/tables/ceilometer-api.xml:14(th) ./doc/common/tables/ceilometer-exchange.xml:14(th) ./doc/common/tables/cinder-lvm.xml:14(th) ./doc/common/tables/trove-dns.xml:14(th) ./doc/common/tables/nova-cells.xml:14(th) ./doc/common/tables/trove-volume.xml:14(th) ./doc/common/tables/heat-auth_token.xml:14(th) ./doc/common/tables/neutron-quotas.xml:14(th) ./doc/common/tables/nova-auth_token.xml:14(th) ./doc/common/tables/cinder-storage_nfs.xml:14(th) ./doc/common/tables/heat-api.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:13(th) ./doc/common/tables/heat-clients_ceilometer.xml:14(th) ./doc/common/tables/neutron-ryu.xml:14(th) ./doc/common/tables/glance-logging.xml:14(th) ./doc/common/tables/swift-rsyncd-account.xml:13(th) ./doc/common/tables/neutron-metering_agent.xml:14(th) ./doc/common/tables/neutron-zeromq.xml:14(th) ./doc/common/tables/cinder-storage_glusterfs.xml:14(th) ./doc/common/tables/cinder-common.xml:14(th) ./doc/common/tables/glance-swift.xml:14(th) ./doc/common/tables/trove-quota.xml:14(th) ./doc/common/tables/cinder-auth_token.xml:14(th) ./doc/common/tables/ceilometer-alarm.xml:14(th) ./doc/common/tables/ceilometer-events.xml:14(th) ./doc/common/tables/cinder-xiv.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-name_check.xml:13(th) ./doc/common/tables/neutron-ml2_bigswitch.xml:14(th) ./doc/common/tables/nova-glance.xml:14(th) ./doc/common/tables/keystone-auth_token.xml:14(th) ./doc/common/tables/nova-s3.xml:14(th) ./doc/common/tables/nova-pci.xml:14(th) ./doc/common/tables/swift-account-server-filter-recon.xml:13(th) ./doc/common/tables/heat-clients_cinder.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:13(th) ./doc/common/tables/keystone-revoke.xml:14(th) ./doc/common/tables/cinder-api.xml:14(th) ./doc/common/tables/trove-db_couchbase.xml:14(th) ./doc/common/tables/heat-clients_trove.xml:14(th) ./doc/common/tables/swift-account-server-account-replicator.xml:13(th) ./doc/common/tables/neutron-plumgrid.xml:14(th) ./doc/common/tables/trove-heat.xml:14(th) ./doc/common/tables/glance-sheepdog.xml:14(th) ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml:13(th) ./doc/common/tables/cinder-windows.xml:14(th) ./doc/common/tables/cinder-san-solaris.xml:14(th) ./doc/common/tables/neutron-nuage.xml:14(th) ./doc/common/tables/keystone-zeromq.xml:14(th) ./doc/common/tables/neutron-bigswitch.xml:14(th) ./doc/common/tables/ceilometer-rpc.xml:14(th) ./doc/common/tables/swift-container-server-container-updater.xml:13(th) ./doc/common/tables/trove-db_mongodb.xml:14(th) ./doc/common/tables/swift-object-server-object-replicator.xml:13(th) ./doc/common/tables/glance-filesystem.xml:14(th) ./doc/common/tables/trove-rpc.xml:14(th) ./doc/common/tables/ceilometer-swift.xml:14(th) ./doc/common/tables/trove-backup.xml:14(th) ./doc/common/tables/nova-network.xml:14(th) ./doc/common/tables/glance-redis.xml:14(th) ./doc/common/tables/keystone-ssl.xml:14(th) ./doc/common/tables/nova-ca.xml:14(th) ./doc/common/tables/neutron-dhcp_agent.xml:14(th) ./doc/common/tables/ceilometer-collector.xml:14(th) ./doc/common/tables/cinder-hds-hus.xml:14(th) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:14(th) ./doc/common/tables/swift-swift-swift-hash.xml:13(th) ./doc/common/tables/neutron-ml2_gre.xml:14(th) ./doc/common/tables/neutron-varmour.xml:14(th) ./doc/common/tables/heat-debug.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-dlo.xml:13(th) ./doc/common/tables/nova-kombu.xml:14(th) ./doc/common/tables/trove-guestagent.xml:14(th) ./doc/common/tables/nova-qpid.xml:14(th) ./doc/common/tables/glance-qpid.xml:14(th) ./doc/common/tables/neutron-ml2_l2pop.xml:14(th) ./doc/common/tables/glance-amqp.xml:14(th) ./doc/common/tables/glance-zmq.xml:14(th) ./doc/common/tables/neutron-embrane_lb.xml:14(th) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:13(th) ./doc/common/tables/neutron-testing.xml:14(th) ./doc/common/tables/swift-object-server-pipeline-main.xml:13(th) ./doc/common/tables/swift-memcache-memcache.xml:13(th) ./doc/common/tables/swift-account-server-app-account-server.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-formpost.xml:13(th) ./doc/common/tables/trove-compute.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:13(th) ./doc/common/tables/swift-object-expirer-filter-cache.xml:13(th) ./doc/common/tables/trove-db_redis.xml:14(th) ./doc/common/tables/cinder-rpc.xml:14(th) ./doc/common/tables/swift-container-sync-realms-realm2.xml:13(th) ./doc/common/tables/cinder-hpmsa.xml:14(th) ./doc/common/tables/nova-apiv3.xml:14(th) ./doc/common/tables/keystone-oauth.xml:14(th) ./doc/common/tables/cinder-storage_gpfs.xml:14(th) ./doc/common/tables/neutron-ml2_vlan.xml:14(th) ./doc/common/tables/keystone-notification.xml:14(th) ./doc/common/tables/swift-object-server-object-auditor.xml:13(th) ./doc/common/tables/trove-zeromq.xml:14(th) ./doc/common/tables/neutron-lbaas.xml:14(th) ./doc/common/tables/cinder-backups_swift.xml:14(th) ./doc/common/tables/trove-database.xml:14(th) ./doc/common/tables/swift-container-server-app-container-server.xml:13(th) ./doc/common/tables/nova-authentication.xml:14(th) ./doc/common/tables/neutron-nvsd.xml:14(th) ./doc/common/tables/swift-account-server-pipeline-main.xml:13(th) ./doc/common/tables/glance-gridfs.xml:14(th) ./doc/common/tables/neutron-notifier.xml:14(th) ./doc/common/tables/nova-rpc_all.xml:14(th) ./doc/common/tables/neutron-hyperv_agent.xml:14(th) ./doc/common/tables/keystone-federation.xml:14(th) ./doc/common/tables/nova-scheduling.xml:14(th) ./doc/common/tables/cinder-ssl.xml:14(th) ./doc/common/tables/trove-ssl.xml:14(th) ./doc/common/tables/cinder-eqlx.xml:14(th) ./doc/common/tables/heat-redis.xml:14(th) ./doc/common/tables/nova-ec2.xml:14(th) ./doc/common/tables/keystone-credential.xml:14(th) ./doc/common/tables/cinder-block-device.xml:14(th) ./doc/common/tables/neutron-metadata.xml:14(th) ./doc/common/tables/nova-fping.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-staticweb.xml:13(th) ./doc/common/tables/swift-container-server-container-replicator.xml:13(th) ./doc/common/tables/neutron-ml2_ncs.xml:14(th) ./doc/common/tables/neutron-ml2_arista.xml:14(th) ./doc/common/tables/nova-trustedcomputing.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:13(th) ./doc/common/tables/swift-object-expirer-app-proxy-server.xml:13(th) ./doc/common/tables/neutron-compute.xml:14(th) ./doc/common/tables/glance-imagecache.xml:14(th) ./doc/common/tables/neutron-ml2_brocade.xml:14(th) ./doc/common/tables/swift-account-server-account-auditor.xml:13(th) ./doc/common/tables/cinder-nas.xml:14(th) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:14(th) ./doc/common/tables/heat-clients_swift.xml:14(th) ./doc/common/tables/keystone-logging.xml:14(th) ./doc/common/tables/neutron-brocade.xml:14(th) ./doc/common/tables/neutron-ml2_odl.xml:14(th) ./doc/common/tables/swift-object-server-filter-recon.xml:13(th) ./doc/common/tables/cinder-connection.xml:14(th) ./doc/common/tables/heat-rpc.xml:14(th) ./doc/common/tables/trove-taskmanager.xml:14(th) ./doc/common/tables/heat-cloudwatch_api.xml:14(th) ./doc/common/tables/cinder-images.xml:14(th) ./doc/common/tables/cinder-huawei.xml:14(th) ./doc/common/tables/nova-console.xml:14(th) ./doc/common/tables/neutron-fwaas.xml:14(th) ./doc/common/tables/cinder-nexenta_nfs.xml:14(th) ./doc/common/tables/nova-quota.xml:14(th) ./doc/common/tables/heat-logging.xml:14(th) ./doc/common/tables/trove-redis.xml:14(th) ./doc/common/tables/keystone-stats.xml:14(th) ./doc/common/tables/heat-crypt.xml:14(th) ./doc/common/tables/neutron-ssl.xml:14(th) ./doc/common/tables/neutron-midonet.xml:14(th) ./doc/common/tables/cinder-coraid.xml:14(th) ./doc/common/tables/neutron-wsgi.xml:14(th) ./doc/common/tables/cinder-compute.xml:14(th) ./doc/common/tables/swift-rsyncd-object.xml:13(th) ./doc/common/tables/glance-wsgi.xml:14(th) ./doc/common/tables/swift-drive-audit-drive-audit.xml:13(th) ./doc/common/tables/nova-baremetal.xml:14(th) ./doc/common/tables/neutron-qpid.xml:14(th) ./doc/common/tables/nova-rpc.xml:14(th) ./doc/common/tables/cinder-backups_tsm.xml:14(th) ./doc/common/tables/cinder-san.xml:14(th) ./doc/common/tables/nova-logging.xml:14(th) ./doc/common/tables/neutron-nec.xml:14(th) ./doc/common/tables/keystone-security.xml:14(th) ./doc/common/tables/heat-clients_neutron.xml:14(th) ./doc/common/tables/nova-api.xml:14(th) ./doc/common/tables/neutron-ml2_mlnx.xml:14(th) ./doc/common/tables/trove-auth_token.xml:14(th) ./doc/common/tables/keystone-trust.xml:14(th) ./doc/common/tables/glance-cinder.xml:14(th) ./doc/common/tables/swift-object-server-object-updater.xml:13(th) ./doc/common/tables/glance-common.xml:14(th) ./doc/common/tables/neutron-ml2_vxlan.xml:14(th) ./doc/common/tables/swift-dispersion-dispersion.xml:13(th) ./doc/common/tables/swift-account-server-DEFAULT.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:13(th) ./doc/common/tables/trove-nova.xml:14(th) ./doc/common/tables/neutron-meta.xml:14(th) ./doc/common/tables/neutron-rabbitmq.xml:14(th) ./doc/common/tables/keystone-ec2.xml:14(th) ./doc/common/tables/heat-clients_keystone.xml:14(th) ./doc/common/tables/neutron-api.xml:14(th) ./doc/common/tables/trove-logging.xml:14(th) ./doc/common/tables/glance-db.xml:14(th) ./doc/common/tables/keystone-kvs.xml:14(th) ./doc/common/tables/keystone-redis.xml:14(th) ./doc/common/tables/nova-xvpnvncproxy.xml:14(th) ./doc/common/tables/glance-paste.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml:13(th) ./doc/common/tables/swift-account-server-account-reaper.xml:13(th) ./doc/common/tables/nova-hyperv.xml:14(th) ./doc/common/tables/swift-proxy-server-filter-container_sync.xml:13(th) ./doc/common/tables/heat-clients_backends.xml:14(th) ./doc/common/tables/glance-testing.xml:14(th) ./doc/common/tables/neutron-common.xml:14(th) ./doc/common/tables/nova-hypervisor.xml:14(th) ./doc/common/tables/keystone-qpid.xml:14(th) ./doc/common/tables/swift-container-sync-realms-realm1.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml:13(th) ./doc/common/tables/nova-wsgi.xml:14(th) ./doc/common/tables/keystone-cache.xml:14(th) ./doc/common/tables/nova-configdrive.xml:14(th) ./doc/common/tables/keystone-token.xml:14(th) ./doc/common/tables/ceilometer-ssl.xml:14(th) ./doc/common/tables/ceilometer-qpid.xml:14(th) ./doc/common/tables/heat-database.xml:14(th) ./doc/common/tables/ceilometer-rabbitmq.xml:14(th) ./doc/common/tables/neutron-ml2.xml:14(th) ./doc/common/tables/neutron-db.xml:14(th) ./doc/common/tables/keystone-database.xml:14(th) ./doc/common/tables/keystone-memcache.xml:14(th) ./doc/common/tables/trove-debug.xml:14(th) ./doc/common/tables/trove-swift.xml:14(th) ./doc/common/tables/nova-tilera.xml:14(th) ./doc/common/tables/nova-libvirt.xml:14(th) ./doc/common/tables/neutron-mlnx.xml:14(th) ./doc/common/tables/cinder-zoning_manager.xml:14(th) ./doc/common/tables/ceilometer-amqp.xml:14(th) ./doc/common/tables/glance-ssl.xml:14(th) ./doc/common/tables/neutron-securitygroups.xml:14(th) ./doc/common/tables/keystone-debug.xml:14(th) ./doc/common/tables/cinder-rootwrap.xml:14(th) ./doc/common/tables/cinder-nexenta_iscsi.xml:14(th)
 msgid "Description"
 msgstr ""
 
@@ -3709,7 +2967,7 @@ msgstr ""
 msgid "List all default quotas for all tenants, as follows:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_quotas.xml:183(para) ./doc/common/section_cli_nova_quotas.xml:207(para) ./doc/common/section_cli_nova_quotas.xml:221(para) ./doc/common/section_cli_nova_quotas.xml:249(para) ./doc/common/section_cli_nova_quotas.xml:292(para) ./doc/common/section_cli_nova_quotas.xml:324(para) ./doc/common/section_cli_keystone_services.xml:100(para) ./doc/common/section_cli_nova_boot_from_volume.xml:190(para) ./doc/common/section_keystone_certificates-for-pki.xml:180(para) ./doc/common/section_cli_cinder_manage_volumes.xml:335(para) ./doc/common/section_cli_cinder_manage_volumes.xml:349(para) ./doc/common/section_cli_cinder_manage_volumes.xml:393(para) ./doc/common/section_objectstorage-ringbuilder.xml:82(para)
+#: ./doc/common/section_cli_nova_quotas.xml:183(para) ./doc/common/section_cli_nova_quotas.xml:207(para) ./doc/common/section_cli_nova_quotas.xml:221(para) ./doc/common/section_cli_nova_quotas.xml:249(para) ./doc/common/section_cli_nova_quotas.xml:292(para) ./doc/common/section_cli_nova_quotas.xml:324(para) ./doc/common/section_objectstorage-ringbuilder.xml:82(para) ./doc/common/section_keystone_certificates-for-pki.xml:180(para) ./doc/common/section_cli_nova_boot_from_volume.xml:190(para) ./doc/common/section_cli_cinder_manage_volumes.xml:335(para) ./doc/common/section_cli_cinder_manage_volumes.xml:349(para) ./doc/common/section_cli_cinder_manage_volumes.xml:393(para) ./doc/common/section_cli_keystone_services.xml:100(para)
 msgid "For example:"
 msgstr ""
 
@@ -3797,772 +3055,346 @@ msgstr ""
 msgid "To update quota values for a tenant user"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-intro.xml:7(title) ./doc/common/section_about-object-storage.xml:7(title)
-msgid "Introduction to Object Storage"
+#: ./doc/common/section_cli_nova_boot.xml:6(title)
+msgid "Launch instances"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-intro.xml:8(para)
-msgid "OpenStack Object Storage (code-named swift) is open source software for creating redundant, scalable data storage using clusters of standardized servers to store petabytes of accessible data. It is a long-term storage system for large amounts of static data that can be retrieved, leveraged, and updated. Object Storage uses a distributed architecture with no central point of control, providing greater scalability, redundancy, and permanence. Objects are written to multiple hardware devices, with the OpenStack software responsible for ensuring data replication and integrity across the cluster. Storage clusters scale horizontally by adding new nodes. Should a node fail, OpenStack works to replicate its content from other active nodes. Because OpenStack uses software logic to ensure data replication and distribution across different devices, inexpensive commodity hard drives and servers can be used in lieu of more expensive equipment."
+#: ./doc/common/section_cli_nova_boot.xml:7(para) ./doc/common/section_dashboard_launch_instances_from_image.xml:8(para)
+msgid "Instances are virtual machines that run inside the cloud."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-intro.xml:19(para)
-msgid "Object Storage is ideal for cost effective, scale-out storage. It provides a fully distributed, API-accessible storage platform that can be integrated directly into applications or used for backup, archiving, and data retention."
+#: ./doc/common/section_cli_nova_boot.xml:9(para)
+msgid "Before you can launch an instance, gather the following parameters:"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml:6(title)
-msgid "Set up credentials for the keystone client"
+#: ./doc/common/section_cli_nova_boot.xml:13(para)
+msgid "The <emphasis role=\"bold\">instance source</emphasis> can be an image, snapshot, or block storage volume that contains an image or snapshot."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml:7(para)
-msgid "You can configure the <package>python-keystoneclient</package> with admin credentials with either an authentication token or a user name and password."
+#: ./doc/common/section_cli_nova_boot.xml:18(para)
+msgid "A <emphasis role=\"bold\">name</emphasis> for your instance."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml:12(title)
-msgid "To configure the keystone client with an authentication token"
+#: ./doc/common/section_cli_nova_boot.xml:21(para) ./doc/common/section_dashboard_launch_instances_from_image.xml:37(para)
+msgid "The <emphasis role=\"bold\">flavor</emphasis> for your instance, which defines the compute, memory, and storage capacity of nova computing instances. A flavor is an available hardware configuration for a server. It defines the size of a virtual server that can be launched."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml:15(para)
-msgid "Export your keystone endpoint to the <varname>OS_SERVICE_ENDPOINT</varname> environment variable:"
+#: ./doc/common/section_cli_nova_boot.xml:29(para)
+msgid "Any <emphasis role=\"bold\">user data</emphasis> files. A user data file is a special key in the metadata service that holds a file that cloud-aware applications in the guest instance can access. For example, one application that uses user data is the <link href=\"https://help.ubuntu.com/community/CloudInit\">cloud-init</link> system, which is an open-source package from Ubuntu that is available on various Linux distributions and that handles early initialization of a cloud instance."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml:21(para)
-msgid "Export the administrator service token to the <varname>OS_SERVICE_TOKEN</varname> environment variable:"
+#: ./doc/common/section_cli_nova_boot.xml:42(para) ./doc/common/section_dashboard_launch_instances_from_image.xml:45(para)
+msgid "Access and security credentials, which include one or both of the following credentials:"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml:26(para) ./doc/common/section_cli_keystone_credentials.xml:80(para)
-msgid "Alternatively, you can specify these parameters on any keystone client command:"
+#: ./doc/common/section_cli_nova_boot.xml:46(para)
+msgid "A <emphasis role=\"bold\">key pair</emphasis> for your instance, which are SSH credentials that are injected into images when they are launched. For the key pair to be successfully injected, the image must contain the <literal>cloud-init</literal> package. Create at least one key pair for each project. If you already have generated a key pair with an external tool, you can import it into OpenStack. You can use the key pair for multiple instances that belong to that project."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml:30(para)
-msgid "<parameter>--os-endpoint <replaceable>SERVICE_ENDPOINT</replaceable></parameter>. An endpoint to use instead of the one in the service catalog. Defaults to <code>env[OS_SERVICE_ENDPOINT]</code>."
+#: ./doc/common/section_cli_nova_boot.xml:60(para)
+msgid "A <emphasis role=\"bold\">security group</emphasis> that defines which incoming network traffic is forwarded to instances. Security groups hold a set of firewall policies, known as <emphasis role=\"italic\">security group rules</emphasis>."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml:39(para)
-msgid "<parameter>--os-token <replaceable>SERVICE_TOKEN</replaceable></parameter>. An existing token to use instead of the one generated by authentication. Defaults to <code>env[OS_SERVICE_TOKEN]</code>."
+#: ./doc/common/section_cli_nova_boot.xml:71(para)
+msgid "If needed, you can assign a <emphasis role=\"bold\">floating (public) IP address</emphasis> to a running instance."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml:52(title)
-msgid "To configure the keystone client with a user name and password"
+#: ./doc/common/section_cli_nova_boot.xml:76(para)
+msgid "You can also attach a block storage device, or <emphasis role=\"bold\">volume</emphasis>, for persistent storage."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml:55(para)
-msgid "Export the administrator user name to the <varname>OS_USERNAME</varname> environment variable:"
+#: ./doc/common/section_cli_nova_boot.xml:82(para)
+msgid "Instances that use the default security group cannot, by default, be accessed from any IP address outside of the cloud. If you want those IP addresses to access the instances, you must modify the rules for the default security group."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml:61(para)
-msgid "Export the administrator password to the <varname>OS_PASSWORD</varname> environment variable:"
+#: ./doc/common/section_cli_nova_boot.xml:87(para)
+msgid "You can also assign a floating IP address to a running instance to make it accessible from outside the cloud. See <xref linkend=\"manage_ip_addresses\"/>."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml:67(para)
-msgid "Export the tenant name to the <varname>OS_TENANT_NAME</varname> environment variable:"
+#: ./doc/common/section_cli_nova_boot.xml:91(para)
+msgid "After you gather the parameters that you need to launch an instance, you can launch it from an <link linkend=\"launch_from_image\">image</link> or a <link linkend=\"boot_from_volume\">volume</link>. You can launch an instance directly from one of the available OpenStack images or from an image that you have copied to a persistent volume. The OpenStack Image Service provides a pool of images that are accessible to members of different projects."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml:73(para)
-msgid "Export the URL of the keystone auth server, for example <link href=\"http://localhost:5000/v2.0'\">http://localhost:5000/v2.0'</link>, to the <varname>OS_AUTH_URL</varname> environment variable:"
+#: ./doc/common/section_cli_nova_boot.xml:101(title)
+msgid "Gather parameters to launch an instance"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml:84(para)
-msgid "<literal>--os-username <replaceable>OS_USERNAME</replaceable></literal>. Name used for authentication with the Identity Service. Defaults to <code>env[OS_USERNAME]</code>."
+#: ./doc/common/section_cli_nova_boot.xml:103(para)
+msgid "Before you begin, source the OpenStack RC file."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml:92(para)
-msgid "<literal>--os-password <replaceable>OS_PASSWORD</replaceable></literal>. Password used for authentication with the Identity Service. Defaults to <code>env[OS_PASSWORD]</code>."
+#: ./doc/common/section_cli_nova_boot.xml:106(para) ./doc/common/section_cli_nova_boot_from_volume.xml:169(para)
+msgid "List the available flavors:"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml:100(para)
-msgid "<literal>--os-tenant_name <replaceable>OS_TENANT_NAME</replaceable></literal>. Tenant for which to request authentication. Defaults to <code>env[OS_TENANT_NAME]</code>."
+#: ./doc/common/section_cli_nova_boot.xml:108(para)
+msgid "Note the ID of the flavor that you want to use for your instance:"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml:108(para)
-msgid "<literal>--os-auth_url <replaceable>OS_AUTH_URL</replaceable></literal>. The Identity Service endpoint to use for authentication. Defaults to <code>env[OS_AUTH_URL]</code>."
+#: ./doc/common/section_cli_nova_boot.xml:121(para) ./doc/common/section_cli_nova_boot_from_volume.xml:155(para)
+msgid "List the available images:"
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml:6(title)
-msgid "Use the VNC console"
+#: ./doc/common/section_cli_nova_boot.xml:123(para)
+msgid "Note the ID of the image from which you want to boot your instance:"
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml:7(para)
-msgid "To interact through the VNC console, you can use a VNC client directly, a special Java client, or a web browser. For information about how to configure the console, see <xref linkend=\"installing-openstack-dashboard\"/>."
+#: ./doc/common/section_cli_nova_boot.xml:131(para)
+msgid "You can also filter the image list by using <placeholder-1/> to find a specific image, as follows:"
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml:15(title)
-msgid "Get an access URL"
+#: ./doc/common/section_cli_nova_boot.xml:138(para)
+msgid "List the available security groups:"
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml:16(para)
-msgid "The Compute service enables you to create access_urls through the os-consoles extension. Support for accessing this URL is provided by the nova client:"
+#: ./doc/common/section_cli_nova_boot.xml:140(para)
+msgid "If you are an admin user, specify the <option>--all-tenants</option> parameter to list groups for all tenants."
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml:19(replaceable) ./doc/common/section_using-vnc-console.xml:25(replaceable) ./doc/common/section_using-vnc-console.xml:52(replaceable) ./doc/common/section_using-vnc-console.xml:65(replaceable)
-msgid "[server_id]"
+#: ./doc/common/section_cli_nova_boot.xml:145(para)
+msgid "Note the ID of the security group that you want to use for your instance:"
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml:19(replaceable)
-msgid "[novnc|xvpvnc]"
+#: ./doc/common/section_cli_nova_boot.xml:151(para)
+msgid "If you have not created any security groups, you can assign the instance to only the default security group."
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml:20(para)
-msgid "Specify '<literal>novnc</literal>' to get a URL suitable for pasting into a web browser."
+#: ./doc/common/section_cli_nova_boot.xml:154(para)
+msgid "You can view rules for a specified security group:"
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml:22(para)
-msgid "Specify '<literal>xvpvnc</literal>' for a URL suitable for pasting into the Java client."
+#: ./doc/common/section_cli_nova_boot.xml:159(para)
+msgid "List the available key pairs and note the name of the key pair that you use for SSH access."
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml:24(para)
-msgid "To request a web browser URL:"
+#: ./doc/common/section_cli_nova_boot.xml:168(title) ./doc/common/section_dashboard_launch_instances_from_image.xml:6(title)
+msgid "Launch an instance from an image"
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml:28(title)
-msgid "Access a VNC console with a Java client"
+#: ./doc/common/section_cli_nova_boot.xml:171(para)
+msgid "After you gather required parameters, run the following command to launch an instance. Specify the server name, flavor ID, and image ID."
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml:29(para)
-msgid "To enable support for the OpenStack Java VNC client in compute, run the <literal>nova-xvpvncproxy</literal> service."
+#: ./doc/common/section_cli_nova_boot.xml:174(para)
+msgid "Optionally, you can provide a key name for access control and a security group for security. You can also include metadata key and value pairs. For example, you can add a description for your server by providing the <parameter>--meta description=\"My Server\"</parameter> parameter."
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml:34(para)
-msgid "<literal>xvpvncproxy_port</literal>=<replaceable>[port]</replaceable> - port to bind (defaults to 6081)"
+#: ./doc/common/section_cli_nova_boot.xml:181(para)
+msgid "You can pass user data in a local file at instance launch by using the <parameter>--user-data <replaceable>USER-DATA-FILE</replaceable></parameter> parameter."
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml:38(para)
-msgid "<literal>xvpvncproxy_host</literal>=<replaceable>[host]</replaceable> - host to bind (defaults to 0.0.0.0)"
+#: ./doc/common/section_cli_nova_boot.xml:186(replaceable)
+msgid "FLAVOR_ID"
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml:42(para)
-msgid "As a client, you need a special Java client, which is a slightly modified version of TightVNC that supports our token auth:"
+#: ./doc/common/section_cli_nova_boot.xml:186(replaceable) ./doc/common/section_cli_nova_boot_from_volume.xml:329(replaceable)
+msgid "IMAGE_ID"
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml:48(para)
-msgid "To create a session, request an access URL by using <placeholder-1/>. Then, run the client as follows."
+#: ./doc/common/section_cli_nova_boot.xml:186(replaceable)
+msgid "KEY_NAME"
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml:51(para)
-msgid "To get an access URL:"
+#: ./doc/common/section_cli_nova_boot.xml:187(replaceable)
+msgid "USER_DATA_FILE"
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml:53(para)
-msgid "To run the client:"
+#: ./doc/common/section_cli_nova_boot.xml:187(replaceable)
+msgid "SEC_GROUP"
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml:54(replaceable)
-msgid "[access_url]"
+#: ./doc/common/section_cli_nova_boot.xml:187(replaceable)
+msgid "KEY=VALUE"
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml:59(title)
-msgid "Access a VNC console with a web browser"
+#: ./doc/common/section_cli_nova_boot.xml:188(replaceable) ./doc/common/section_cli_nova_startstop.xml:14(replaceable) ./doc/common/section_cli_nova_startstop.xml:18(replaceable) ./doc/common/section_cli_nova_startstop.xml:35(replaceable) ./doc/common/section_cli_nova_startstop.xml:40(replaceable) ./doc/common/section_cli_nova_get_console.xml:8(replaceable)
+msgid "INSTANCE_NAME"
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml:61(para)
-msgid "Retrieving an access_url for a web browser is similar to the flow for the Java client."
+#: ./doc/common/section_cli_nova_boot.xml:189(para)
+msgid "The following command launches the <literal>MyCirrosServer</literal> instance with the <literal>m1.small</literal> flavor (ID of <literal>1</literal>), <literal>cirros-0.3.2-x86_64-uec</literal> image (ID of <literal>397e713c-b95b-4186-ad46-6126863ea0a9</literal>), <literal>default</literal> security group, <literal>KeyPair01</literal> key, and a user data file called <filename>cloudinit.file</filename>:"
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml:63(para)
-msgid "To get the access URL, run the following command:"
+#: ./doc/common/section_cli_nova_boot.xml:202(replaceable)
+msgid "myCirrosServer"
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml:66(para)
-msgid "Paste the URL into your web browser."
+#: ./doc/common/section_cli_nova_boot.xml:203(para)
+msgid "Depending on the parameters that you provide, the command returns a list of server properties."
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml:68(para)
-msgid "Additionally, you can use the OpenStack dashboard, known as horizon, to access browser-based VNC consoles for instances."
+#: ./doc/common/section_cli_nova_boot.xml:206(para)
+msgid "A status of <literal>BUILD</literal> indicates that the instance has started, but is not yet online."
 msgstr ""
 
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:6(title)
-msgid "Configure tenant-specific image locations with Object Storage"
+#: ./doc/common/section_cli_nova_boot.xml:209(para)
+msgid "A status of <literal>ACTIVE</literal> indicates that the instance is active."
 msgstr ""
 
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:14(para)
-msgid "The tenant who owns the image"
+#: ./doc/common/section_cli_nova_boot.xml:241(para)
+msgid "Copy the server ID value from the <literal>id</literal> field in the output. You use this ID to get details for or delete your server."
 msgstr ""
 
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:17(para)
-msgid "Tenants that are defined in <option>swift_store_admin_tenants</option> and that have admin-level accounts"
+#: ./doc/common/section_cli_nova_boot.xml:245(para)
+msgid "Copy the administrative password value from the <literal>adminPass</literal> field. You use this value to log in to your server."
 msgstr ""
 
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:8(para)
-msgid "For some deployers, it is not ideal to store all images in one place to enable all tenants and users to access them. You can configure the Image Service to store image data in tenant-specific image locations. Then, only the following tenants can use the Image Service to access the created image:<placeholder-1/>"
+#: ./doc/common/section_cli_nova_boot.xml:249(para)
+msgid "You can also place arbitrary local files into the instance file system at creation time by using the <option>--file &lt;dst-path=src-path&gt;</option> option. You can store up to five files. For example, if you have a special authorized keys file named <filename>special_authorized_keysfile</filename> that you want to put on the instance rather than using the regular SSH key injection, you can use the <option>--file</option> option as shown in the following example:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:23(title)
-msgid "To configure tenant-specific image locations"
+#: ./doc/common/section_cli_nova_boot.xml:266(para)
+msgid "Check if the instance is online:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:25(para)
-msgid "Configure swift as your <option>default_store</option> in the <filename>glance-api.conf</filename> file."
+#: ./doc/common/section_cli_nova_boot.xml:268(para)
+msgid "The list shows the ID, name, status, and private (and if assigned, public) IP addresses for all instances in the project to which you belong:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:33(para)
-msgid "<option>swift_store_multi_tenant</option>. Set to <literal>True</literal> to enable tenant-specific storage locations. Default is <literal>False</literal>."
+#: ./doc/common/section_cli_nova_boot.xml:278(para)
+msgid "If the status for the instance is ACTIVE, the instance is online."
 msgstr ""
 
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:39(para)
-msgid "<option>swift_store_admin_tenants</option>. Specify a list of tenant IDs that can grant read and write access to all Object Storage containers that are created by the Image Service."
+#: ./doc/common/section_cli_nova_boot.xml:280(para)
+msgid "To view the available options for the <placeholder-1/> command, run the following command:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:30(para)
-msgid "Set these configuration options in the <filename>glance-api.conf</filename> file: <placeholder-1/>"
+#: ./doc/common/section_cli_nova_boot.xml:287(para)
+msgid "If you did not provide a key pair, security groups, or rules, you can access the instance only from inside the cloud through VNC. Even pinging the instance is not possible."
 msgstr ""
 
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:48(para)
-msgid "With this configuration, images are stored in an Object Storage service (swift) endpoint that is pulled from the service catalog for the authenticated user."
+#: ./doc/common/section_user-data.xml:6(title)
+msgid "Configure instances at boot"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:11(title)
-msgid "Telemetry command-line client"
+#: ./doc/common/section_user-data.xml:7(para)
+msgid "When you boot instances in an OpenStack cloud, you can use user data or <package>cloud-init</package> to automatically configure instances at boot time. You might want to install some packages, start services, or manage your instance by using a Puppet or Chef server."
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:12(para)
-msgid "The <placeholder-1/> client is the command-line interface (CLI) for the Telemetry API and its extensions. This chapter documents <placeholder-2/> version 1.0.10."
+#: ./doc/common/section_user-data.xml:13(title)
+msgid "User data"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:22(title)
-msgid "ceilometer usage"
+#: ./doc/common/section_user-data.xml:14(para)
+msgid "User data is the mechanism by which a user can pass information contained in a local file to an instance at launch time. The typical use case is to pass something like a shell script or a configuration file as user data."
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:42(para) ./doc/common/ch_cli_ceilometer_commands.xml:459(para)
-msgid "Create a new alarm based on state of other alarms."
+#: ./doc/common/section_user-data.xml:19(para)
+msgid "User data is sent using the <literal>--user-data <replaceable>/path/to/filename</replaceable></literal> option when calling <placeholder-1/>. This example creates a text file and sends its contents as user data to the instance:"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:50(para) ./doc/common/ch_cli_ceilometer_commands.xml:601(para)
-msgid "Update an existing alarm based on state of other alarms."
+#: ./doc/common/section_user-data.xml:26(para)
+msgid "The instance can get user data by querying the metadata service through either the OpenStack metadata API or the EC2 compatibility API:"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:59(para)
-msgid "Create a new alarm (Deprecated). Use alarm-threshold- create instead."
+#: ./doc/common/section_user-data.xml:34(para)
+msgid "The Compute service treats user data as a blob. While the previous example uses a text file, user data can be in any format."
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:68(para) ./doc/common/ch_cli_ceilometer_commands.xml:746(para)
-msgid "Delete an alarm."
+#: ./doc/common/section_user-data.xml:38(para)
+msgid "For more information, see <xref linkend=\"config-drive\"/>."
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:76(para) ./doc/common/ch_cli_ceilometer_commands.xml:763(para)
-msgid "Display the change history of an alarm."
+#: ./doc/common/section_user-data.xml:42(package)
+msgid "cloud-init"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:84(para) ./doc/common/ch_cli_ceilometer_commands.xml:790(para)
-msgid "List the user's alarms."
+#: ./doc/common/section_user-data.xml:43(para)
+msgid "To do something useful with the user data, you must configure the virtual machine image to run a service on boot that gets user data from the metadata service and takes some action based on the contents of the data. The <package>cloud-init</package> package does exactly this. This package is compatible with the Compute metadata service and the Compute configuration drive."
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:92(para) ./doc/common/ch_cli_ceilometer_commands.xml:809(para)
-msgid "Show an alarm."
+#: ./doc/common/section_user-data.xml:51(para)
+msgid "The <package>cloud-init</package> package supports multiple cloud providers. You can use the same virtual machine image in different clouds without modification. The <package>cloud-init</package> package is an open source project and the source code is available on <link href=\"http://launchpad.net/cloud-init\">Launchpad</link>. It is maintained by Canonical, the company that runs the Ubuntu project. All Ubuntu cloud images come pre-installed with <package>cloud-init</package>. However, <package>cloud-init</package> is not designed to be Ubuntu-specific and has been successfully ported to several other platforms including Fedora."
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:100(para) ./doc/common/ch_cli_ceilometer_commands.xml:826(para)
-msgid "Get the state of an alarm."
+#: ./doc/common/section_user-data.xml:66(para)
+msgid "Even if you do not use user data to configure instance behavior at boot time, install <package>cloud-init</package> on images that you create because this package provides useful functionality. For example, the <package>cloud-init</package> package enables you to copy the public key to an account (the <literal>ubuntu</literal> account by default on Ubuntu instances, the <literal>ec2-user</literal> by default in Fedora instances)."
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:108(para) ./doc/common/ch_cli_ceilometer_commands.xml:843(para)
-msgid "Set the state of an alarm."
+#: ./doc/common/section_user-data.xml:75(para)
+msgid "If you do not have <package>cloud-init</package> installed, you must manually configure your image to get the public key from the metadata service on boot and copy it to the appropriate account."
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:116(para) ./doc/common/ch_cli_ceilometer_commands.xml:884(para)
-msgid "Create a new alarm based on computed statistics."
+#: ./doc/common/section_user-data.xml:81(title)
+msgid "<package>cloud-init</package> supported formats and documentation"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:124(para) ./doc/common/ch_cli_ceilometer_commands.xml:1074(para)
-msgid "Update an existing alarm based on computed statistics."
+#: ./doc/common/section_user-data.xml:83(para)
+msgid "Look at the <package>cloud-init</package><link href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/userdata.txt\">doc/userdata.txt</link> file the <link href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/files/head:/doc/examples/\">examples</link> directory and the <link href=\"https://help.ubuntu.com/community/CloudInit\">Ubuntu community documentation</link> for details about how to use <package>cloud-init</package>. Some basic examples are provided here."
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:132(para) ./doc/common/ch_cli_ceilometer_commands.xml:1279(para)
-msgid "Update an existing alarm (Deprecated)."
+#: ./doc/common/section_user-data.xml:93(para)
+msgid "<package>cloud-init</package> supports several input formats for user data. Two commonly used formats are:"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:140(para) ./doc/common/ch_cli_ceilometer_commands.xml:1468(para)
-msgid "List events."
+#: ./doc/common/section_user-data.xml:98(para)
+msgid "Shell scripts (starts with <literal>#!</literal>)"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:148(para) ./doc/common/ch_cli_ceilometer_commands.xml:1487(para)
-msgid "Show a particular event."
+#: ./doc/common/section_user-data.xml:102(para)
+msgid "Cloud config files (starts with <literal>#cloud-config</literal>)"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:156(para) ./doc/common/ch_cli_ceilometer_commands.xml:1504(para)
-msgid "List event types."
+#: ./doc/common/section_user-data.xml:108(title)
+msgid "Run a shell script on boot"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:164(para) ./doc/common/ch_cli_ceilometer_commands.xml:1511(para)
-msgid "List the user's meters."
+#: ./doc/common/section_user-data.xml:109(para)
+msgid "Assuming you have <package>cloud-init</package> installed, the simplest way to configure an instance on boot is to pass a shell script as user data. The shell file must begin with <literal>#!</literal> in order for <package>cloud-init</package> to recognize it as a shell script. This example shows a script that creates a <literal>clouduser</literal> account:"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:172(para) ./doc/common/ch_cli_ceilometer_commands.xml:1531(para)
-msgid "Query Alarm History."
+#: ./doc/common/section_user-data.xml:118(para)
+msgid "Sending a shell script as user data has a similar effect to writing an <filename>/etc/rc.local</filename> script: it executes very late in the boot sequence as root."
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:180(para) ./doc/common/ch_cli_ceilometer_commands.xml:1567(para)
-msgid "Query Alarms."
+#: ./doc/common/section_user-data.xml:123(title)
+msgid "Cloud-config format"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:188(para) ./doc/common/ch_cli_ceilometer_commands.xml:1603(para)
-msgid "Query samples."
+#: ./doc/common/section_user-data.xml:124(para)
+msgid "<package>cloud-init</package> supports a YAML-based config format that allows the user to configure a large number of options on a system. User data that begins with <literal>#cloud-config</literal> will be interpreted by <package>cloud-init</package> as cloud-config format."
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:196(para) ./doc/common/ch_cli_ceilometer_commands.xml:1639(para)
-msgid "List the resources."
+#: ./doc/common/section_user-data.xml:132(title)
+msgid "Example: Set the host name"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:204(para) ./doc/common/ch_cli_ceilometer_commands.xml:1658(para)
-msgid "Show the resource."
+#: ./doc/common/section_user-data.xml:133(para)
+msgid "This <package>cloud-init</package> user data example sets the hostname and the FQDN, as well as updating <filename>/etc/hosts</filename> on the instance:"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:212(para) ./doc/common/ch_cli_ceilometer_commands.xml:1681(para)
-msgid "Create a sample."
+#: ./doc/common/section_user-data.xml:145(title)
+msgid "Example: Configure instances with Puppet"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:220(para) ./doc/common/ch_cli_ceilometer_commands.xml:1764(para)
-msgid "List the samples for a meter."
+#: ./doc/common/section_user-data.xml:146(para)
+msgid "This <package>cloud-init</package> user data example, based on <link href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/examples/cloud-config-puppet.txt\">doc/examples/cloud-config-puppet.txt</link>, would configure the instance to contact a Puppet server at puppetmaster.example.org and verify its identity by using a certificate."
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:228(para) ./doc/common/ch_cli_ceilometer_commands.xml:1800(para)
-msgid "List the statistics for a meter."
+#: ./doc/common/section_user-data.xml:174(title)
+msgid "Example: Configure instances with Chef"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:236(para) ./doc/common/ch_cli_ceilometer_commands.xml:1853(para)
-msgid "List trait info for an event type."
+#: ./doc/common/section_user-data.xml:175(para)
+msgid "This <package>cloud-init</package> user data example, based on <link href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/examples/cloud-config-chef.txt\">doc/examples/cloud-config/chef.txt</link> and intended for use in an Ubuntu image, adds the Chef apt repository, installs Chef, connects to a Chef server at <literal>https://chefserver.example.com:4000</literal>, and installs Apache:"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:244(para)
-msgid "List trait all traits with name &lt;trait_name&gt; for Event Type"
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_getstart_conceptual_arch.xml:16(None)
+msgid "@@image: 'figures/openstack_havana_conceptual_arch.png'; md5=96e1d5492d4c865fc9145710bb294a91"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:253(para) ./doc/common/ch_cli_keystone_commands.xml:324(para) ./doc/common/ch_cli_heat_commands.xml:303(para)
-msgid "Prints all of the commands and options to stdout."
+#: ./doc/common/section_getstart_conceptual_arch.xml:6(title)
+msgid "Conceptual architecture"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:270(title)
-msgid "ceilometer optional arguments"
+#: ./doc/common/section_getstart_conceptual_arch.xml:7(para)
+msgid "The following diagram shows the relationships among the OpenStack services:"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml:283(para)
-msgid "Defaults to <code>env[CEILOMETERCLIENT_DEBUG]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:291(para) ./doc/common/ch_cli_heat_commands.xml:341(para)
-msgid "Print more verbose output."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:299(para)
-msgid "Explicitly allow ceilometerclient to perform \"insecure\" SSL (https) requests. The server's certificate will not be verified against any certificate authorities. This option should be used with caution."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:311(para) ./doc/common/ch_cli_glance_commands.xml:262(para) ./doc/common/ch_cli_heat_commands.xml:360(para)
-msgid "Path of certificate file to use in SSL connection. This file can optionally be prepended with the private key."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:321(para) ./doc/common/ch_cli_glance_commands.xml:272(para)
-msgid "Path of client key to use in SSL connection. This option is not necessary if your key is prepended to your cert file."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:331(para)
-msgid "Path of CA TLS certificate(s) used to verifythe remote server's certificate. Without this option ceilometer looks for the default system CA certificates."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:341(para) ./doc/common/ch_cli_glance_commands.xml:292(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use --os-cacert."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:349(para)
-msgid "Number of seconds to wait for a response."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:405(para) ./doc/common/ch_cli_heat_commands.xml:447(para)
-msgid "Defaults to <code>env[OS_AUTH_TOKEN]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:413(para)
-msgid "Defaults to <code>env[CEILOMETER_URL]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:421(para)
-msgid "Defaults to <code>env[CEILOMETER_API_VERSION]</code> or 2."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:429(para) ./doc/common/ch_cli_heat_commands.xml:480(para)
-msgid "Defaults to <code>env[OS_SERVICE_TYPE]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:437(para) ./doc/common/ch_cli_heat_commands.xml:488(para)
-msgid "Defaults to <code>env[OS_ENDPOINT_TYPE]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:445(title)
-msgid "ceilometer alarm-combination-create command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:466(para) ./doc/common/ch_cli_ceilometer_commands.xml:891(para)
-msgid "Name of the alarm (must be unique per tenant). Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:475(para) ./doc/common/ch_cli_ceilometer_commands.xml:624(para) ./doc/common/ch_cli_ceilometer_commands.xml:900(para) ./doc/common/ch_cli_ceilometer_commands.xml:1097(para) ./doc/common/ch_cli_ceilometer_commands.xml:1302(para)
-msgid "Tenant to associate with alarm (only settable by admin users)."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:484(para) ./doc/common/ch_cli_ceilometer_commands.xml:633(para) ./doc/common/ch_cli_ceilometer_commands.xml:909(para) ./doc/common/ch_cli_ceilometer_commands.xml:1106(para) ./doc/common/ch_cli_ceilometer_commands.xml:1311(para)
-msgid "User to associate with alarm (only settable by admin users)."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:493(para) ./doc/common/ch_cli_ceilometer_commands.xml:642(para) ./doc/common/ch_cli_ceilometer_commands.xml:918(para) ./doc/common/ch_cli_ceilometer_commands.xml:1115(para) ./doc/common/ch_cli_ceilometer_commands.xml:1320(para)
-msgid "Free text description of the alarm."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:501(para) ./doc/common/ch_cli_ceilometer_commands.xml:650(para) ./doc/common/ch_cli_ceilometer_commands.xml:926(para) ./doc/common/ch_cli_ceilometer_commands.xml:1123(para) ./doc/common/ch_cli_ceilometer_commands.xml:1328(para)
-msgid "State of the alarm, one of: ['ok', 'alarm', 'insufficient_data']"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:510(para) ./doc/common/ch_cli_ceilometer_commands.xml:659(para) ./doc/common/ch_cli_ceilometer_commands.xml:935(para) ./doc/common/ch_cli_ceilometer_commands.xml:1132(para) ./doc/common/ch_cli_ceilometer_commands.xml:1337(para)
-msgid "True if alarm evaluation/actioning is enabled."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:518(para) ./doc/common/ch_cli_ceilometer_commands.xml:667(para) ./doc/common/ch_cli_ceilometer_commands.xml:943(para) ./doc/common/ch_cli_ceilometer_commands.xml:1140(para) ./doc/common/ch_cli_ceilometer_commands.xml:1345(para)
-msgid "URL to invoke when state transitions to alarm. May be used multiple times. Defaults to None."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:527(para) ./doc/common/ch_cli_ceilometer_commands.xml:676(para) ./doc/common/ch_cli_ceilometer_commands.xml:952(para) ./doc/common/ch_cli_ceilometer_commands.xml:1149(para) ./doc/common/ch_cli_ceilometer_commands.xml:1354(para)
-msgid "URL to invoke when state transitions to OK. May be used multiple times. Defaults to None."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:536(para) ./doc/common/ch_cli_ceilometer_commands.xml:685(para) ./doc/common/ch_cli_ceilometer_commands.xml:961(para) ./doc/common/ch_cli_ceilometer_commands.xml:1158(para) ./doc/common/ch_cli_ceilometer_commands.xml:1363(para)
-msgid "URL to invoke when state transitions to insufficient_data. May be used multiple times. Defaults to None."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:546(para) ./doc/common/ch_cli_ceilometer_commands.xml:695(para) ./doc/common/ch_cli_ceilometer_commands.xml:971(para) ./doc/common/ch_cli_ceilometer_commands.xml:1168(para) ./doc/common/ch_cli_ceilometer_commands.xml:1373(para)
-msgid "Only evaluate the alarm if the time at evaluation is within this time constraint. Start point(s) of the constraint are specified with a cron expression , whereas its duration is given in seconds. Can be specified multiple times for multiple time constraints, format is: name=&lt;CONSTRAINT_NAME&gt;;start=&lt; CRON&gt;;duration=&lt;SECONDS&gt;;[description=&lt;DESCRIPTION&gt;;[t imezone=&lt;IANA Timezone&gt;]] Defaults to None."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:561(para)
-msgid "List of alarm ids. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:569(para) ./doc/common/ch_cli_ceilometer_commands.xml:727(para)
-msgid "Operator to compare with, one of: ['and', 'or']."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:577(para) ./doc/common/ch_cli_ceilometer_commands.xml:1046(para)
-msgid "True if actions should be repeatedly notified while alarm remains in target state. Defaults to False."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:586(title)
-msgid "ceilometer alarm-combination-update command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:608(para) ./doc/common/ch_cli_ceilometer_commands.xml:1081(para) ./doc/common/ch_cli_ceilometer_commands.xml:1286(para)
-msgid "ID of the alarm to update. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:616(para) ./doc/common/ch_cli_ceilometer_commands.xml:1089(para) ./doc/common/ch_cli_ceilometer_commands.xml:1294(para)
-msgid "Name of the alarm (must be unique per tenant)."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:710(para) ./doc/common/ch_cli_ceilometer_commands.xml:1183(para) ./doc/common/ch_cli_ceilometer_commands.xml:1388(para)
-msgid "Name or list of names of the time constraints to remove."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:719(para)
-msgid "List of alarm id."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:735(para) ./doc/common/ch_cli_ceilometer_commands.xml:1252(para) ./doc/common/ch_cli_ceilometer_commands.xml:1457(para)
-msgid "True if actions should be repeatedly notified while alarm remains in target state."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:744(title)
-msgid "ceilometer alarm-delete command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:753(para)
-msgid "ID of the alarm to delete. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:761(title)
-msgid "ceilometer alarm-history command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:770(para)
-msgid "ID of the alarm for which history is shown. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:778(para) ./doc/common/ch_cli_ceilometer_commands.xml:797(para) ./doc/common/ch_cli_ceilometer_commands.xml:1036(para) ./doc/common/ch_cli_ceilometer_commands.xml:1242(para) ./doc/common/ch_cli_ceilometer_commands.xml:1518(para) ./doc/common/ch_cli_ceilometer_commands.xml:1646(para) ./doc/common/ch_cli_ceilometer_commands.xml:1771(para) ./doc/common/ch_cli_ceilometer_commands.xml:1807(para)
-msgid "key[op]data_type::value; list. data_type is optional, but if supplied must be string, integer, float, or boolean."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:788(title)
-msgid "ceilometer alarm-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:807(title)
-msgid "ceilometer alarm-show command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:816(para)
-msgid "ID of the alarm to show. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:824(title)
-msgid "ceilometer alarm-state-get command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:833(para)
-msgid "ID of the alarm state to show. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:841(title)
-msgid "ceilometer alarm-state-set command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:850(para)
-msgid "ID of the alarm state to set. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:858(para)
-msgid "State of the alarm, one of: ['ok', 'alarm', 'insufficient_data']. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:867(title)
-msgid "ceilometer alarm-threshold-create command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:986(para)
-msgid "Metric to evaluate against. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:994(para) ./doc/common/ch_cli_ceilometer_commands.xml:1200(para) ./doc/common/ch_cli_ceilometer_commands.xml:1397(para)
-msgid "Length of each period (seconds) to evaluate over."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1002(para) ./doc/common/ch_cli_ceilometer_commands.xml:1208(para) ./doc/common/ch_cli_ceilometer_commands.xml:1405(para)
-msgid "Number of periods to evaluate over."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1010(para) ./doc/common/ch_cli_ceilometer_commands.xml:1216(para)
-msgid "Statistic to evaluate, one of: ['max', 'min', 'avg', 'sum', 'count']."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1019(para) ./doc/common/ch_cli_ceilometer_commands.xml:1225(para) ./doc/common/ch_cli_ceilometer_commands.xml:1430(para)
-msgid "Operator to compare with, one of: ['lt', 'le', 'eq', 'ne', 'ge', 'gt']."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1028(para)
-msgid "Threshold to evaluate against. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1055(title)
-msgid "ceilometer alarm-threshold-update command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1192(para) ./doc/common/ch_cli_ceilometer_commands.xml:1413(para)
-msgid "Metric to evaluate against."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1234(para) ./doc/common/ch_cli_ceilometer_commands.xml:1439(para)
-msgid "Threshold to evaluate against."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1261(title)
-msgid "ceilometer alarm-update command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1421(para)
-msgid "Statistic to evaluate, one of: ['max', 'min', 'avg', 'sum', 'count']"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1447(para)
-msgid "A meter should match this resource metadata (key=value) additionally to the meter_name. Defaults to None."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1466(title)
-msgid "ceilometer event-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1475(para)
-msgid "key[op]data_type::value; list. data_type is optional, but if supplied must be string, integer, floator datetime."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1485(title)
-msgid "ceilometer event-show command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1494(para)
-msgid "The id of the event. Should be a UUID Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1502(title)
-msgid "ceilometer event-type-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1509(title)
-msgid "ceilometer meter-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1528(title)
-msgid "ceilometer query-alarm-history command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1538(para) ./doc/common/ch_cli_ceilometer_commands.xml:1574(para) ./doc/common/ch_cli_ceilometer_commands.xml:1610(para)
-msgid "{complex_op: [{simple_op: {field_name: value}}]} The complex_op is one of: ['and', 'or'], simple_op is one of: ['=', '!=', '&lt;', '&lt;=', '&gt;', '&gt;=']."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1548(para) ./doc/common/ch_cli_ceilometer_commands.xml:1584(para) ./doc/common/ch_cli_ceilometer_commands.xml:1620(para)
-msgid "[{field_name: direction}, {field_name: direction}] The direction is one of: ['asc', 'desc']."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1557(para)
-msgid "Maximum number of alarm history items to return."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1565(title)
-msgid "ceilometer query-alarms command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1593(para)
-msgid "Maximum number of alarms to return."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1601(title)
-msgid "ceilometer query-samples command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1629(para) ./doc/common/ch_cli_ceilometer_commands.xml:1789(para)
-msgid "Maximum number of samples to return."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1637(title)
-msgid "ceilometer resource-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1656(title)
-msgid "ceilometer resource-show command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1665(para)
-msgid "ID of the resource to show. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1673(title)
-msgid "ceilometer sample-create command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1688(para)
-msgid "Tenant to associate with sample (only settable by admin users)."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1697(para)
-msgid "User to associate with sample (only settable by admin users)."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1706(para)
-msgid "ID of the resource. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1714(para)
-msgid "The meter name. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1722(para)
-msgid "The meter type. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1730(para)
-msgid "The meter unit. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1738(para)
-msgid "The sample volume. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1746(para)
-msgid "Resource metadata."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1754(para)
-msgid "The sample timestamp."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1762(title)
-msgid "ceilometer sample-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1781(para) ./doc/common/ch_cli_ceilometer_commands.xml:1817(para)
-msgid "Name of meter to show samples for. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1797(title)
-msgid "ceilometer statistics command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1825(para)
-msgid "Period in seconds over which to group samples."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1833(para)
-msgid "Field for group by."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1841(para)
-msgid "Function for data aggregation. Available aggregates are: count, cardinality, min, max, sum, stddev, avg. Defaults to []."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1851(title)
-msgid "ceilometer trait-description-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1860(para)
-msgid "Type of the event for which traits will be shown. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1869(title)
-msgid "ceilometer trait-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1871(para)
-msgid "List trait all traits with name &lt;trait_name&gt; for Event Type &lt;event_type&gt;."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1878(para)
-msgid "Type of the event for which traits will listed. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml:1887(para)
-msgid "The name of the trait to list. Required."
-msgstr ""
-
-#: ./doc/common/section_conventions.xml:8(title)
-msgid "Conventions"
-msgstr ""
-
-#: ./doc/common/section_conventions.xml:9(para)
-msgid "The OpenStack documentation uses several typesetting conventions."
-msgstr ""
-
-#: ./doc/common/section_conventions.xml:13(title)
-msgid "Notices"
-msgstr ""
-
-#: ./doc/common/section_conventions.xml:14(para)
-msgid "Notices take three forms:"
-msgstr ""
-
-#: ./doc/common/section_conventions.xml:16(para)
-msgid "The information in a note is usually in the form of a handy tip or reminder."
-msgstr ""
-
-#: ./doc/common/section_conventions.xml:20(para)
-msgid "The information in an important notice is something you must be aware of before proceeding."
-msgstr ""
-
-#: ./doc/common/section_conventions.xml:24(para)
-msgid "The information in warnings is critical. Warnings provide additional information about risk of data loss or security issues."
-msgstr ""
-
-#: ./doc/common/section_conventions.xml:31(title)
-msgid "Command prompts"
-msgstr ""
-
-#: ./doc/common/section_conventions.xml:32(para)
-msgid "Commands prefixed with the <literal>#</literal> prompt are to be executed by the <literal>root</literal> user. These examples can also be executed by using the <placeholder-1/> command, if available."
-msgstr ""
-
-#: ./doc/common/section_conventions.xml:36(para)
-msgid "Commands prefixed with the <literal>$</literal> prompt can be executed by any user, including <literal>root</literal>."
+#: ./doc/common/section_getstart_conceptual_arch.xml:11(title)
+msgid "OpenStack conceptual architecture"
 msgstr ""
 
 #: ./doc/common/ch_cli_neutron_commands.xml:11(title)
@@ -6853,372 +5685,660 @@ msgstr ""
 msgid "ID or name of vpnservice to update"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:7(title)
-msgid "Create and manage services and service users"
+#: ./doc/common/section_keystone-concepts-service-management.xml:5(title)
+msgid "Service management"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:8(para)
-msgid "The Identity Service enables you to define services, as follows:"
+#: ./doc/common/section_keystone-concepts-service-management.xml:6(para)
+msgid "The Identity Service provides identity, token, catalog, and policy services. It consists of:"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:12(para)
-msgid "Service catalog template. The Identity Service acts as a service catalog of endpoints for other OpenStack services. The <literal>etc/default_catalog.templates</literal> template file defines the endpoints for services. When the Identity Service uses a template file back end, any changes that are made to the endpoints are cached. These changes do not persist when you restart the service or reboot the machine."
+#: ./doc/common/section_keystone-concepts-service-management.xml:11(para)
+msgid "<systemitem class=\"service\">keystone-all</systemitem>. Starts both the service and administrative APIs in a single process to provide Catalog, Authorization, and Authentication services for OpenStack."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:23(para)
-msgid "A SQL back end for the catalog service. When the Identity Service is online, you must add the services to the catalog. When you deploy a system for production, use the SQL back end."
+#: ./doc/common/section_keystone-concepts-service-management.xml:17(para)
+msgid "Identity Service functions. Each has a pluggable back end that allows different ways to use the particular service. Most support standard back ends like LDAP or SQL."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:29(para)
-msgid "The <literal>auth_token</literal> middleware supports the use of either a shared secret or users for each service."
+#: ./doc/common/section_keystone-concepts-service-management.xml:23(para)
+msgid "The Identity Service also maintains a user that corresponds to each service, such as, a user named <emphasis>nova</emphasis> for the Compute service, and a special service tenant called <emphasis>service</emphasis>."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:32(para)
-msgid "To authenticate users against the Identity Service, you must create a service user for each OpenStack service. For example, create a service user for the Compute, Block Storage, and Networking services."
+#: ./doc/common/section_keystone-concepts-service-management.xml:28(para)
+msgid "For information about how to create services and endpoints, see the <link href=\"http://docs.openstack.org/user-guide-admin/content/index.html\"><citetitle>OpenStack Admin User Guide</citetitle></link>."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:36(para)
-msgid "To configure the OpenStack services with service users, create a project for all services and create users for each service. Assign the admin role to each service user and project pair. This role enables users to validate tokens and authenticate and authorize other user requests."
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_trusted-compute-pools.xml:45(None) ./doc/common/section_trusted-compute-pools.xml:50(None)
+msgid "@@image: 'figures/OpenStackTrustedComputePool1.png'; md5=858fbd6148b927723cea5ad2c88d54bd"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:42(title)
-msgid "Create a service"
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_trusted-compute-pools.xml:150(None) ./doc/common/section_trusted-compute-pools.xml:155(None)
+msgid "@@image: 'figures/OpenStackTrustedComputePool2.png'; md5=077261c595464638c4b3fcc92b6afb9a"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:45(para)
-msgid "List the available services:"
+#: ./doc/common/section_trusted-compute-pools.xml:6(title)
+msgid "Trusted compute pools"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:59(para)
-msgid "To create a service, run this command:"
+#: ./doc/common/section_trusted-compute-pools.xml:7(para)
+msgid "Trusted compute pools enable administrators to designate a group of compute hosts as trusted. These hosts use hardware-based security features, such as the Intel Trusted Execution Technology (TXT), to provide an additional level of security. Combined with an external stand-alone, web-based remote attestation server, cloud providers can ensure that the compute node runs only software with verified measurements and can ensure a secure cloud stack."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:60(replaceable)
-msgid "service_name"
+#: ./doc/common/section_trusted-compute-pools.xml:13(para)
+msgid "Using the trusted compute pools, cloud subscribers can request services to run on verified compute nodes."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:60(replaceable)
-msgid "service_type"
+#: ./doc/common/section_trusted-compute-pools.xml:15(para)
+msgid "The remote attestation server performs node verification as follows:"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:60(replaceable)
-msgid "service_description"
+#: ./doc/common/section_trusted-compute-pools.xml:19(para)
+msgid "Compute nodes boot with Intel TXT technology enabled."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:61(para)
-msgid "The arguments are:"
+#: ./doc/common/section_trusted-compute-pools.xml:23(para)
+msgid "The compute node BIOS, hypervisor, and OS are measured."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:64(para)
-msgid "<code><replaceable>service_name</replaceable></code>. The unique name of the new service."
+#: ./doc/common/section_trusted-compute-pools.xml:27(para)
+msgid "Measured data is sent to the attestation server when challenged by the attestation server."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:68(para)
-msgid "<code><replaceable>service_type</replaceable></code>. The service type, such as <code>identity</code>, <code>compute</code>, <code>network</code>, <code>image</code>, <code>object-store</code> or any other service identifier string."
+#: ./doc/common/section_trusted-compute-pools.xml:31(para)
+msgid "The attestation server verifies those measurements against a good and known database to determine node trustworthiness."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:78(para)
-msgid "<code><replaceable>service_description</replaceable></code>. The description of the service."
+#: ./doc/common/section_trusted-compute-pools.xml:35(para)
+msgid "A description of how to set up an attestation service is beyond the scope of this document. For an open source project that you can use to implement an attestation service, see the <link href=\"https://github.com/OpenAttestation/OpenAttestation\">Open Attestation</link> project."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:82(para)
-msgid "For example, to create a <literal>swift</literal> service of type <literal>object-store</literal>, run this command:"
+#: ./doc/common/section_trusted-compute-pools.xml:54(title)
+msgid "Configure Compute to use trusted compute pools"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:97(para)
-msgid "To get details for a service, run this command:"
+#: ./doc/common/section_trusted-compute-pools.xml:57(para)
+msgid "Enable scheduling support for trusted compute pools by adding the following lines in the <literal>DEFAULT</literal> section in the <filename>/etc/nova/nova.conf</filename> file:"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:99(replaceable)
-msgid "service_ID"
+#: ./doc/common/section_trusted-compute-pools.xml:66(para)
+msgid "Specify the connection information for your attestation service by adding the following lines to the <literal>trusted_computing</literal> section in the <filename>/etc/nova/nova.conf</filename> file:"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:114(title)
-msgid "Create service users"
+#: ./doc/common/section_trusted-compute-pools.xml:78(para) ./doc/common/section_cli_nova_customize_flavors.xml:260(para) ./doc/common/section_keystone_config_ldap-hardening.xml:83(para)
+msgid "Where:"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:117(para)
-msgid "Create a project for the service users. Typically, this project is named <literal>service</literal>, but choose any name you like:"
+#: ./doc/common/section_trusted-compute-pools.xml:81(term)
+msgid "server"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:122(para)
-msgid "The output shows the ID for the project."
+#: ./doc/common/section_trusted-compute-pools.xml:83(para)
+msgid "Host name or IP address of the host that runs the attestation service."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:123(para)
-msgid "Make a note of this ID. You need it to create service users and assign roles."
+#: ./doc/common/section_trusted-compute-pools.xml:88(term)
+msgid "port"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:135(para)
-msgid "Create service users for the relevant services for your deployment."
+#: ./doc/common/section_trusted-compute-pools.xml:90(para)
+msgid "HTTPS port for the attestation service."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:139(para)
-msgid "To assign the admin role to the service user-project pairs, run this command to get the ID of the admin role:"
+#: ./doc/common/section_trusted-compute-pools.xml:94(term)
+msgid "server_ca_file"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:155(para)
-msgid "Assign the admin role to the user-project pair:"
+#: ./doc/common/section_trusted-compute-pools.xml:96(para)
+msgid "Certificate file used to verify the attestation server's identity."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:157(replaceable)
-msgid "SERVICE_USER_ID"
+#: ./doc/common/section_trusted-compute-pools.xml:101(term)
+msgid "api_url"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:157(replaceable)
-msgid "ADMIN_ROLE_ID"
+#: ./doc/common/section_trusted-compute-pools.xml:103(para)
+msgid "The attestation service's URL path."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:157(replaceable)
-msgid "SERVICE_PROJECT_ID"
+#: ./doc/common/section_trusted-compute-pools.xml:107(term)
+msgid "auth_blob"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:162(title)
-msgid "Delete a service"
+#: ./doc/common/section_trusted-compute-pools.xml:109(para)
+msgid "An authentication blob, which is required by the attestation service."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:163(para)
-msgid "To delete a specified service, specify its ID:"
+#: ./doc/common/section_trusted-compute-pools.xml:117(para)
+msgid "Restart the <systemitem class=\"service\">nova-compute</systemitem> and <systemitem class=\"service\">nova-scheduler</systemitem> services."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml:164(replaceable)
-msgid "SERVICE_ID"
+#: ./doc/common/section_trusted-compute-pools.xml:124(title) ./doc/common/section_compute_config-api.xml:183(title)
+msgid "Configuration reference"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:10(title)
-msgid "Launch an instance from a volume"
+#: ./doc/common/section_trusted-compute-pools.xml:125(para)
+msgid "To customize the trusted compute pools, use the following configuration option settings:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:11(para)
-msgid "You can boot instances from a volume instead of an image."
+#: ./doc/common/section_trusted-compute-pools.xml:132(title)
+msgid "Specify trusted flavors"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:12(para)
-msgid "To complete these tasks, use these parameters on the nova <placeholder-1/> command:"
+#: ./doc/common/section_trusted-compute-pools.xml:133(para)
+msgid "To designate hosts as trusted:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:20(th)
-msgid "Task"
+#: ./doc/common/section_trusted-compute-pools.xml:136(para)
+msgid "Configure one or more flavors as trusted by using the <placeholder-1/> command. For example, to set the <literal>m1.tiny</literal> flavor as trusted:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:21(th)
-msgid "nova boot parameter"
+#: ./doc/common/section_trusted-compute-pools.xml:141(para)
+msgid "Request that your instance be run on a trusted host, by specifying a trusted flavor when booting the instance. For example:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:22(th)
-msgid "See"
+#: ./doc/common/section_trusted-compute-pools.xml:145(title)
+msgid "Trusted compute pool"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:27(td)
-msgid "Boot an instance from an image and attach a non-bootable volume."
+#: ./doc/common/ch_cli_heat_commands.xml:11(title)
+msgid "Orchestration command-line client"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:29(parameter) ./doc/common/section_cli_nova_boot_from_volume.xml:35(parameter) ./doc/common/section_cli_nova_boot_from_volume.xml:41(parameter)
-msgid "--block-device"
+#: ./doc/common/ch_cli_heat_commands.xml:12(para)
+msgid "The <placeholder-1/> client is the command-line interface (CLI) for the Orchestration API and its extensions. This chapter documents <placeholder-2/> version 0.2.9."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:33(td)
-msgid "Create a volume from an image and boot an instance from that volume."
+#: ./doc/common/ch_cli_heat_commands.xml:22(title)
+msgid "heat usage"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:39(td)
-msgid "Boot from an existing source image, volume, or snapshot."
+#: ./doc/common/ch_cli_heat_commands.xml:39(para) ./doc/common/ch_cli_heat_commands.xml:506(para)
+msgid "Resume the stack."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:45(td)
-msgid "Attach a swap disk to an instance."
+#: ./doc/common/ch_cli_heat_commands.xml:47(para) ./doc/common/ch_cli_heat_commands.xml:523(para)
+msgid "Suspend the stack."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:47(parameter)
-msgid "--swap"
+#: ./doc/common/ch_cli_heat_commands.xml:55(para) ./doc/common/ch_cli_heat_commands.xml:540(para)
+msgid "Retrieve build information."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:51(td)
-msgid "Attach an ephemeral disk to an instance."
+#: ./doc/common/ch_cli_heat_commands.xml:63(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use stack-create instead."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:52(parameter)
-msgid "--ephemeral"
+#: ./doc/common/ch_cli_heat_commands.xml:71(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use stack-delete instead."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:58(para)
-msgid "To attach a volume to a running instance, see <xref linkend=\"cli_attach_volume\"/>."
+#: ./doc/common/ch_cli_heat_commands.xml:79(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use stack-show instead."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:62(title)
-msgid "Boot instance from image and attach non-bootable volume"
+#: ./doc/common/ch_cli_heat_commands.xml:87(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use event-show instead."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:64(para)
-msgid "Create a non-bootable volume and attach that volume to an instance that you boot from an image."
+#: ./doc/common/ch_cli_heat_commands.xml:95(para) ./doc/common/ch_cli_heat_commands.xml:547(para)
+msgid "List events for a stack."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:66(para)
-msgid "To create a non-bootable volume, do not create it from an image. The volume must be entirely empty with no partition table and no file system."
+#: ./doc/common/ch_cli_heat_commands.xml:103(para) ./doc/common/ch_cli_heat_commands.xml:575(para)
+msgid "Describe the event."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:71(para)
-msgid "Create a non-bootable volume:"
+#: ./doc/common/ch_cli_heat_commands.xml:111(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use template-show instead."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:98(para) ./doc/common/section_cli_cinder_manage_volumes.xml:176(para)
-msgid "List volumes:"
+#: ./doc/common/ch_cli_heat_commands.xml:119(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use stack-list instead."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:107(para)
-msgid "Boot an instance from an image and attach the empty volume to the instance:"
+#: ./doc/common/ch_cli_heat_commands.xml:127(para) ./doc/common/ch_cli_heat_commands.xml:608(para)
+msgid "Show available outputs."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:149(title)
-msgid "Create volume from image and boot instance"
+#: ./doc/common/ch_cli_heat_commands.xml:135(para) ./doc/common/ch_cli_heat_commands.xml:625(para)
+msgid "Show a specific stack output."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:150(para)
-msgid "You can create a volume from an existing image, volume, or snapshot. This procedure shows you how to create a volume from an image, and use the volume to boot an instance."
+#: ./doc/common/ch_cli_heat_commands.xml:143(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use resource-show instead."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:155(para) ./doc/common/section_cli_nova_boot.xml:121(para)
-msgid "List the available images:"
+#: ./doc/common/ch_cli_heat_commands.xml:151(para) ./doc/common/ch_cli_heat_commands.xml:650(para)
+msgid "Show list of resources belonging to a stack."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:165(para)
-msgid "Note the ID of the image that you want to use to create a volume."
+#: ./doc/common/ch_cli_heat_commands.xml:159(para) ./doc/common/ch_cli_heat_commands.xml:667(para)
+msgid "List resource metadata."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:169(para) ./doc/common/section_cli_nova_boot.xml:106(para)
-msgid "List the available flavors:"
+#: ./doc/common/ch_cli_heat_commands.xml:167(para) ./doc/common/ch_cli_heat_commands.xml:692(para)
+msgid "Describe the resource."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:183(para)
-msgid "Note the ID of the flavor that you want to use to create a volume."
+#: ./doc/common/ch_cli_heat_commands.xml:175(para) ./doc/common/ch_cli_heat_commands.xml:717(para)
+msgid "Send a signal to a resource."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:187(para)
-msgid "To create a bootable volume from an image and launch an instance from this volume, use the <parameter>--block-device</parameter> parameter."
+#: ./doc/common/ch_cli_heat_commands.xml:183(para) ./doc/common/ch_cli_heat_commands.xml:762(para)
+msgid "Generate a template based on a resource."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:191(replaceable) ./doc/common/section_cli_nova_boot_from_volume.xml:329(replaceable)
-msgid "FLAVOR"
+#: ./doc/common/ch_cli_heat_commands.xml:191(para) ./doc/common/ch_cli_heat_commands.xml:790(para)
+msgid "List the available resource types."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:191(replaceable) ./doc/common/section_cli_nova_boot_from_volume.xml:205(replaceable)
-msgid "SOURCE"
+#: ./doc/common/ch_cli_heat_commands.xml:199(para) ./doc/common/ch_cli_heat_commands.xml:797(para)
+msgid "Show the resource type."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:191(replaceable) ./doc/common/section_cli_nova_boot_from_volume.xml:217(replaceable)
-msgid "ID"
+#: ./doc/common/ch_cli_heat_commands.xml:207(para) ./doc/common/ch_cli_heat_commands.xml:814(para)
+msgid "Abandon the stack."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:191(replaceable) ./doc/common/section_cli_nova_boot_from_volume.xml:224(replaceable)
-msgid "DEST"
+#: ./doc/common/ch_cli_heat_commands.xml:215(para) ./doc/common/ch_cli_heat_commands.xml:834(para)
+msgid "Adopt a stack."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:191(replaceable) ./doc/common/section_cli_nova_boot_from_volume.xml:233(replaceable)
-msgid "SIZE"
+#: ./doc/common/ch_cli_heat_commands.xml:223(para) ./doc/common/ch_cli_heat_commands.xml:932(para)
+msgid "Create the stack."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:191(replaceable)
-msgid "PRESERVE"
+#: ./doc/common/ch_cli_heat_commands.xml:231(para) ./doc/common/ch_cli_heat_commands.xml:1019(para)
+msgid "Delete the stack(s)."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:191(replaceable) ./doc/common/section_cli_nova_boot_from_volume.xml:250(replaceable)
-msgid "INDEX"
+#: ./doc/common/ch_cli_heat_commands.xml:239(para) ./doc/common/ch_cli_heat_commands.xml:1037(para)
+msgid "List the user's stacks."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:191(replaceable) ./doc/common/section_cli_nova_boot_from_volume.xml:329(replaceable)
-msgid "NAME"
+#: ./doc/common/ch_cli_heat_commands.xml:247(para) ./doc/common/ch_cli_heat_commands.xml:1076(para)
+msgid "Preview the stack."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:192(para)
-msgid "The parameters are:"
+#: ./doc/common/ch_cli_heat_commands.xml:255(para) ./doc/common/ch_cli_heat_commands.xml:1154(para)
+msgid "Describe the stack."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:195(para)
-msgid "<parameter>--flavor</parameter><replaceable>FLAVOR</replaceable>. The flavor ID or name."
+#: ./doc/common/ch_cli_heat_commands.xml:263(para) ./doc/common/ch_cli_heat_commands.xml:1173(para)
+msgid "Update the stack."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:200(para)
-msgid "<parameter>--block-device</parameter> source=<replaceable>SOURCE</replaceable>,id=<replaceable>ID</replaceable>,dest=<replaceable>DEST</replaceable>,size=<replaceable>SIZE</replaceable>,shutdown=<replaceable>PRESERVE</replaceable>,bootindex=<replaceable>INDEX</replaceable>"
+#: ./doc/common/ch_cli_heat_commands.xml:271(para) ./doc/common/ch_cli_heat_commands.xml:1243(para)
+msgid "Get the template for the specified stack."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:205(emphasis)
-msgid "source=<placeholder-1/>"
+#: ./doc/common/ch_cli_heat_commands.xml:279(para) ./doc/common/ch_cli_heat_commands.xml:1261(para)
+msgid "Validate a template with parameters."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:207(para)
-msgid "The type of object used to create the block device. Valid values are <literal>volume</literal>, <literal>snapshot</literal>, <literal>image</literal>, and <literal>blank</literal>."
+#: ./doc/common/ch_cli_heat_commands.xml:287(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use stack-update instead."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:217(emphasis)
-msgid "id=<placeholder-1/>"
+#: ./doc/common/ch_cli_heat_commands.xml:295(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use template-validate instead."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:219(para)
-msgid "The ID of the source object."
+#: ./doc/common/ch_cli_heat_commands.xml:303(para) ./doc/common/ch_cli_keystone_commands.xml:324(para) ./doc/common/ch_cli_ceilometer_commands.xml:253(para)
+msgid "Prints all of the commands and options to stdout."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:224(emphasis)
-msgid "dest=<placeholder-1/>"
+#: ./doc/common/ch_cli_heat_commands.xml:320(title)
+msgid "heat optional arguments"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:226(para)
-msgid "The type of the target virtual device. Valid values are <literal>volume</literal> and <literal>local</literal>."
+#: ./doc/common/ch_cli_heat_commands.xml:325(para) ./doc/common/ch_cli_keystone_commands.xml:346(para)
+msgid "Shows the client version and exits."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:233(emphasis)
-msgid "size=<placeholder-1/>"
+#: ./doc/common/ch_cli_heat_commands.xml:333(para)
+msgid "Defaults to <code>env[HEATCLIENT_DEBUG]</code>."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:235(para)
-msgid "The size of the volume that is created."
+#: ./doc/common/ch_cli_heat_commands.xml:341(para) ./doc/common/ch_cli_ceilometer_commands.xml:291(para)
+msgid "Print more verbose output."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:240(emphasis)
-msgid "shutdown={preserve|remove}"
+#: ./doc/common/ch_cli_heat_commands.xml:349(para)
+msgid "Explicitly allow the client to perform \"insecure\" SSL (https) requests. The server's certificate will not be verified against any certificate authorities. This option should be used with caution."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:242(para)
-msgid "What to do with the volume when the instance is deleted. <literal>preserve</literal> does not delete the volume. <literal>remove</literal> deletes the volume."
+#: ./doc/common/ch_cli_heat_commands.xml:360(para) ./doc/common/ch_cli_glance_commands.xml:262(para) ./doc/common/ch_cli_ceilometer_commands.xml:311(para)
+msgid "Path of certificate file to use in SSL connection. This file can optionally be prepended with the private key."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:250(emphasis)
-msgid "bootindex=<placeholder-1/>"
+#: ./doc/common/ch_cli_heat_commands.xml:370(para)
+msgid "Path of client key to use in SSL connection.This option is not necessary if your key is prepended to your cert file."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:252(para)
-msgid "Orders the boot disks. Use <literal>0</literal> to boot from this volume."
+#: ./doc/common/ch_cli_heat_commands.xml:380(para)
+msgid "Path of CA SSL certificate(s) used to verify the remote server's certificate. Without this option the client looks for the default system CA certificates."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:260(para)
-msgid "<replaceable>NAME</replaceable>. The name for the server."
+#: ./doc/common/ch_cli_heat_commands.xml:390(para)
+msgid "Number of seconds to wait for an API response, defaults to system socket timeout"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:266(para)
-msgid "Create a bootable volume from an image, before the instance boots. The volume is not deleted when the instance is terminated:"
+#: ./doc/common/ch_cli_heat_commands.xml:447(para) ./doc/common/ch_cli_ceilometer_commands.xml:405(para)
+msgid "Defaults to <code>env[OS_AUTH_TOKEN]</code>."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:307(para)
-msgid "List volumes to see the bootable volume and its attached <literal>myInstanceFromVolume</literal> instance:"
+#: ./doc/common/ch_cli_heat_commands.xml:455(para)
+msgid "Do not contact keystone for a token. Defaults to <code>env[OS_NO_CLIENT_AUTH]</code>."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:320(title)
-msgid "Attach swap or ephemeral disk to an instance"
+#: ./doc/common/ch_cli_heat_commands.xml:464(para)
+msgid "Defaults to <code>env[HEAT_URL]</code>."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:321(para)
-msgid "Use the nova <placeholder-1/><parameter>--swap</parameter> parameter to attach a swap disk on boot or the nova <placeholder-2/><parameter>--ephemeral</parameter> parameter to attach an ephemeral disk on boot. When you terminate the instance, both disks are deleted."
+#: ./doc/common/ch_cli_heat_commands.xml:472(para)
+msgid "Defaults to <code>env[HEAT_API_VERSION]</code> or 1."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:327(para)
-msgid "Boot an instance with a 512MB swap disk and 2GB ephemeral disk:"
+#: ./doc/common/ch_cli_heat_commands.xml:480(para) ./doc/common/ch_cli_ceilometer_commands.xml:429(para)
+msgid "Defaults to <code>env[OS_SERVICE_TYPE]</code>."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:329(replaceable) ./doc/common/section_cli_nova_boot.xml:186(replaceable)
-msgid "IMAGE_ID"
+#: ./doc/common/ch_cli_heat_commands.xml:488(para) ./doc/common/ch_cli_ceilometer_commands.xml:437(para)
+msgid "Defaults to <code>env[OS_ENDPOINT_TYPE]</code>."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml:331(para)
-msgid "The flavor defines the maximum swap and ephemeral disk size. You cannot exceed these maximum values."
+#: ./doc/common/ch_cli_heat_commands.xml:496(para)
+msgid "Send os-username and os-password to heat."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:504(title)
+msgid "heat action-resume command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:513(para)
+msgid "Name or ID of stack to resume."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:521(title)
+msgid "heat action-suspend command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:530(para)
+msgid "Name or ID of stack to suspend."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:538(title)
+msgid "heat build-info command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:545(title)
+msgid "heat event-list command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:554(para) ./doc/common/ch_cli_heat_commands.xml:582(para)
+msgid "Name or ID of stack to show the events for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:565(para)
+msgid "Name of the resource to filter events by."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:573(title)
+msgid "heat event-show command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:590(para)
+msgid "Name of the resource the event belongs to."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:598(para)
+msgid "ID of event to display details for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:606(title)
+msgid "heat output-list command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:615(para) ./doc/common/ch_cli_heat_commands.xml:632(para)
+msgid "Name or ID of stack to query."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:623(title)
+msgid "heat output-show command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:640(para)
+msgid "Name of an output to display."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:648(title)
+msgid "heat resource-list command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:657(para)
+msgid "Name or ID of stack to show the resources for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:665(title)
+msgid "heat resource-metadata command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:674(para)
+msgid "Name or ID of stack to show the resource metadata for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:682(para)
+msgid "Name of the resource to show the metadata for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:690(title)
+msgid "heat resource-show command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:699(para)
+msgid "Name or ID of stack to show the resource for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:707(para)
+msgid "Name of the resource to show the details for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:715(title)
+msgid "heat resource-signal command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:724(para)
+msgid "Name or ID of stack the resource belongs to."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:732(para)
+msgid "Name of the resource to signal."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:743(para)
+msgid "JSON Data to send to the signal handler."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:751(para)
+msgid "File containing JSON data to send to the signal handler."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:760(title)
+msgid "heat resource-template command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:769(para)
+msgid "Name of the resource to generate a template for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:780(para)
+msgid "The template output format, one of: yaml, json."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:788(title)
+msgid "heat resource-type-list command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:795(title)
+msgid "heat resource-type-show command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:804(para)
+msgid "Resource type to get the details for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:812(title)
+msgid "heat stack-abandon command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:821(para)
+msgid "Name or ID of stack to abandon."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:829(title)
+msgid "heat stack-adopt command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:841(para)
+msgid "Name of the stack to adopt."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:852(para) ./doc/common/ch_cli_heat_commands.xml:950(para) ./doc/common/ch_cli_heat_commands.xml:1094(para) ./doc/common/ch_cli_heat_commands.xml:1191(para) ./doc/common/ch_cli_heat_commands.xml:1276(para)
+msgid "Path to the template."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:860(para) ./doc/common/ch_cli_heat_commands.xml:958(para) ./doc/common/ch_cli_heat_commands.xml:1102(para) ./doc/common/ch_cli_heat_commands.xml:1199(para) ./doc/common/ch_cli_heat_commands.xml:1284(para)
+msgid "Path to the environment."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:868(para) ./doc/common/ch_cli_heat_commands.xml:966(para) ./doc/common/ch_cli_heat_commands.xml:1110(para) ./doc/common/ch_cli_heat_commands.xml:1207(para) ./doc/common/ch_cli_heat_commands.xml:1268(para)
+msgid "URL of template."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:876(para)
+msgid "URL to retrieve template object (e.g from swift)."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:884(para) ./doc/common/ch_cli_heat_commands.xml:982(para)
+msgid "Stack creation timeout in minutes. <emphasis>DEPRECATED</emphasis> use --timeout instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:893(para) ./doc/common/ch_cli_heat_commands.xml:991(para)
+msgid "Stack creation timeout in minutes."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:901(para)
+msgid "Path to adopt stack data file."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:909(para) ./doc/common/ch_cli_heat_commands.xml:999(para)
+msgid "Enable rollback on create/update failure."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:917(para) ./doc/common/ch_cli_heat_commands.xml:1007(para) ./doc/common/ch_cli_heat_commands.xml:1231(para)
+msgid "Parameter values used to create the stack. This can be specified multiple times, or once with parameters separated by a semicolon."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:927(title)
+msgid "heat stack-create command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:939(para)
+msgid "Name of the stack to create."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:974(para) ./doc/common/ch_cli_heat_commands.xml:1215(para) ./doc/common/ch_cli_heat_commands.xml:1292(para)
+msgid "URL to retrieve template object (e.g. from swift)."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:1017(title)
+msgid "heat stack-delete command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:1026(para)
+msgid "Name or ID of stack(s) to delete."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:1034(title)
+msgid "heat stack-list command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:1044(para)
+msgid "Filter parameters to apply on returned stacks. This can be specified multiple times, or once with parameters separated by a semicolon."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:1054(para)
+msgid "Limit the number of stacks returned."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:1062(para)
+msgid "Only return stacks that appear after the given stack ID."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:1071(title)
+msgid "heat stack-preview command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:1083(para)
+msgid "Name of the stack to preview."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:1118(para)
+msgid "URL to retrieve template object (e.g from swift)"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:1126(para)
+msgid "Stack timeout in minutes. Default: 60"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:1134(para)
+msgid "Enable rollback on failure"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:1142(para)
+msgid "Parameter values used to preview the stack. This can be specified multiple times, or once with parameters separated by semicolon."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:1152(title)
+msgid "heat stack-show command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:1161(para)
+msgid "Name or ID of stack to describe."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:1169(title)
+msgid "heat stack-update command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:1180(para)
+msgid "Name or ID of stack to update."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:1223(para)
+msgid "Stack update timeout in minutes."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:1241(title)
+msgid "heat template-show command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:1250(para)
+msgid "Name or ID of stack to get the template for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:1258(title)
+msgid "heat template-validate command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml:1300(para)
+msgid "Parameter values to validate. This can be specified multiple times, or once with parameters separated by a semicolon."
 msgstr ""
 
 #: ./doc/common/section_cli_nova_images.xml:6(title)
@@ -7241,6 +6361,10 @@ msgstr ""
 msgid "To create an image"
 msgstr ""
 
+#: ./doc/common/section_cli_nova_images.xml:18(para) ./doc/common/section_cli_nova_manage_images.xml:17(para)
+msgid "Write any buffered data to disk."
+msgstr ""
+
 #: ./doc/common/section_cli_nova_images.xml:19(para)
 msgid "For more information, see the <link href=\"http://docs.openstack.org/trunk/openstack-ops/content/snapsnots.html\">Taking Snapshots</link> in the <citetitle>OpenStack Operations Guide</citetitle>."
 msgstr ""
@@ -7253,10 +6377,18 @@ msgstr ""
 msgid "In this example, the server is named <literal>myCirrosServer</literal>. Use this server to create a snapshot, as follows: <placeholder-1/>The command creates a qemu snapshot and automatically uploads the image to your repository. Only the tenant that creates the image has access to it."
 msgstr ""
 
+#: ./doc/common/section_cli_nova_images.xml:43(para) ./doc/common/section_cli_nova_manage_images.xml:40(para)
+msgid "Get details for your image to check its status:"
+msgstr ""
+
 #: ./doc/common/section_cli_nova_images.xml:45(replaceable)
 msgid "IMAGE"
 msgstr ""
 
+#: ./doc/common/section_cli_nova_images.xml:79(para) ./doc/common/section_cli_nova_manage_images.xml:75(para)
+msgid "The image status changes from <literal>SAVING</literal> to <literal>ACTIVE</literal>. Only the tenant who creates the image has access to it."
+msgstr ""
+
 #: ./doc/common/section_cli_nova_images.xml:86(title)
 msgid "To launch an instance from your image"
 msgstr ""
@@ -7265,408 +6397,1208 @@ msgstr ""
 msgid "To launch an instance from your image, include the image ID and flavor ID, as follows:"
 msgstr ""
 
+#: ./doc/common/section_cli_nova_images.xml:125(title) ./doc/common/section_cli_glance_manage_images.xml:410(title)
+msgid "Troubleshoot image creation"
+msgstr ""
+
 #: ./doc/common/section_cli_nova_images.xml:133(para)
 msgid "Make sure the version of qemu you are using is version 0.14 or greater. Older versions of qemu result in an \"<literal>unknown option -s</literal>\" error message in the <filename>nova-compute.log</filename>."
 msgstr ""
 
-#: ./doc/common/section_keystone-external-auth.xml:7(title)
-msgid "External authentication with Identity"
+#: ./doc/common/section_cli_nova_images.xml:140(para) ./doc/common/section_cli_glance_manage_images.xml:420(para)
+msgid "Examine the <filename>/var/log/nova-api.log</filename> and <filename>/var/log/nova-compute.log</filename> log files for error messages."
 msgstr ""
 
-#: ./doc/common/section_keystone-external-auth.xml:8(para)
-msgid "When Identity runs in <literal>apache-httpd</literal>, you can use external authentication methods that differ from the authentication provided by the identity store back end. For example, you can use an SQL identity back end together with X.509 authentication, Kerberos, and so on instead of using the user name and password combination."
+#: ./doc/common/section_dochistory.xml:6(title)
+msgid "Document change history"
 msgstr ""
 
-#: ./doc/common/section_keystone-external-auth.xml:15(title)
-msgid "Use HTTPD authentication"
+#: ./doc/common/section_dochistory.xml:8(para)
+msgid "This version of the guide replaces and obsoletes all previous versions. The following table describes the most recent changes:"
 msgstr ""
 
-#: ./doc/common/section_keystone-external-auth.xml:16(para)
-msgid "Web servers, like Apache HTTP, support many methods of authentication. Identity can allow the web server to perform the authentication. The web server then passes the authenticated user to Identity by using the <literal>REMOTE_USER</literal> environment variable. This user must already exist in the Identity back end to get a token from the controller. To use this method, Identity should run on <literal>apache-httpd</literal>."
+#: ./doc/common/ch_cli_swift_commands.xml:11(title)
+msgid "Object Storage command-line client"
 msgstr ""
 
-#: ./doc/common/section_keystone-external-auth.xml:27(title)
-msgid "Use X.509"
+#: ./doc/common/ch_cli_swift_commands.xml:12(para)
+msgid "The <placeholder-1/> client is the command-line interface (CLI) for the OpenStack Object Storage API and its extensions. This chapter documents <placeholder-2/> version 2.1.0."
 msgstr ""
 
-#: ./doc/common/section_keystone-external-auth.xml:28(para)
-msgid "The following Apache configuration snippet authenticates the user based on a valid X.509 certificate from a known CA:"
+#: ./doc/common/ch_cli_swift_commands.xml:22(title)
+msgid "swift usage"
 msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml:5(title)
-msgid "Orchestration module"
+#: ./doc/common/ch_cli_swift_commands.xml:41(para) ./doc/common/ch_cli_swift_commands.xml:335(para)
+msgid "Delete a container or objects within a container."
 msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml:6(para)
-msgid "The Orchestration module provides a template-based orchestration for describing a cloud application, by running OpenStack API calls to generate running cloud applications. The software integrates other core components of OpenStack into a one-file template system. The templates allow you to create most OpenStack resource types, such as instances, floating IPs, volumes, security groups and users. It also provides advanced functionality, such as instance high availability, instance auto-scaling, and nested stacks. This enables OpenStack core projects to receive a larger user base."
+#: ./doc/common/ch_cli_swift_commands.xml:49(para) ./doc/common/ch_cli_swift_commands.xml:399(para)
+msgid "Download objects from containers."
 msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml:16(para)
-msgid "The service enables deployers to integrate with the Orchestration module directly or through custom plug-ins."
+#: ./doc/common/ch_cli_swift_commands.xml:57(para) ./doc/common/ch_cli_swift_commands.xml:513(para)
+msgid "Lists the containers for the account or the objects for a container."
 msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml:18(para)
-msgid "The Orchestration module consists of the following components:"
+#: ./doc/common/ch_cli_swift_commands.xml:66(para)
+msgid "Updates meta information for the account, container, or object; creates containers if not present."
 msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml:22(term)
-msgid "<code>heat</code> command-line client"
+#: ./doc/common/ch_cli_swift_commands.xml:75(para) ./doc/common/ch_cli_swift_commands.xml:661(para)
+msgid "Displays information for the account, container, or object."
 msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml:23(para)
-msgid "A CLI that communicates with the heat-api to run AWS CloudFormation APIs. End developers can directly use the Orchestration REST API."
+#: ./doc/common/ch_cli_swift_commands.xml:84(para)
+msgid "Uploads files or directories to the given container."
 msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml:28(term)
-msgid "<code>heat-api</code> component"
+#: ./doc/common/ch_cli_swift_commands.xml:92(para)
+msgid "List cluster capabilities."
 msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml:28(para)
-msgid "An OpenStack-native REST API that processes API requests by sending them to the heat-engine over Remote Procedure Call (RPC)."
+#: ./doc/common/ch_cli_swift_commands.xml:100(title)
+msgid "swift examples"
 msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml:34(term)
-msgid "<code>heat-api-cfn</code> component"
+#: ./doc/common/ch_cli_swift_commands.xml:110(title)
+msgid "swift optional arguments"
 msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml:34(para)
-msgid "An AWS Query API that is compatible with AWS CloudFormation. It processes API requests by sending them to the heat-engine over RPC."
+#: ./doc/common/ch_cli_swift_commands.xml:131(para)
+msgid "Use SERVICENET internal network."
 msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml:40(code)
-msgid "heat-engine"
+#: ./doc/common/ch_cli_swift_commands.xml:139(para)
+msgid "Print more info."
 msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml:41(para)
-msgid "Orchestrates the launching of templates and provides events back to the API consumer."
+#: ./doc/common/ch_cli_swift_commands.xml:147(para)
+msgid "Show the curl commands and results of all http queries regardless of result status."
 msgstr ""
 
-#: ./doc/common/section_getstart_networking.xml:5(title)
-msgid "OpenStack Networking"
+#: ./doc/common/ch_cli_swift_commands.xml:156(para)
+msgid "Show the curl commands and results of all http queries which return an error."
 msgstr ""
 
-#: ./doc/common/section_getstart_networking.xml:6(para)
-msgid "OpenStack Networking allows you to create and attach interface devices managed by other OpenStack services to networks. Plug-ins can be implemented to accomodate different networking equipment and software, providing flexibility to OpenStack architecture and deployment."
+#: ./doc/common/ch_cli_swift_commands.xml:165(para)
+msgid "Suppress status output."
 msgstr ""
 
-#: ./doc/common/section_getstart_networking.xml:11(para) ./doc/common/section_getstart_object-storage.xml:9(para)
-msgid "It includes the following components:"
+#: ./doc/common/ch_cli_swift_commands.xml:173(para)
+msgid "for obtaining an auth token."
 msgstr ""
 
-#: ./doc/common/section_getstart_networking.xml:14(systemitem)
-msgid "neutron-server"
+#: ./doc/common/ch_cli_swift_commands.xml:181(para)
+msgid "Specify a version for authentication. Defaults to 1.0."
 msgstr ""
 
-#: ./doc/common/section_getstart_networking.xml:15(para)
-msgid "Accepts and routes API requests to the appropriate OpenStack Networking plug-in for action."
+#: ./doc/common/ch_cli_swift_commands.xml:189(para)
+msgid "User name for obtaining an auth token."
 msgstr ""
 
-#: ./doc/common/section_getstart_networking.xml:19(term)
-msgid "OpenStack Networking plug-ins and agents"
+#: ./doc/common/ch_cli_swift_commands.xml:197(para)
+msgid "Key for obtaining an auth token."
 msgstr ""
 
-#: ./doc/common/section_getstart_networking.xml:20(para)
-msgid "Plugs and unplugs ports, creates networks or subnets, and provides IP addressing. These plug-ins and agents differ depending on the vendor and technologies used in the particular cloud. OpenStack Networking ships with plug-ins and agents for Cisco virtual and physical switches, NEC OpenFlow products, Open vSwitch, Linux bridging, Ryu Network Operating System, and the VMware NSX product."
+#: ./doc/common/ch_cli_swift_commands.xml:205(para)
+msgid "The number of times to retry a failed connection."
 msgstr ""
 
-#: ./doc/common/section_getstart_networking.xml:27(para)
-msgid "The common agents are L3 (layer 3), DHCP (dynamic host IP addressing), and a plug-in agent."
+#: ./doc/common/ch_cli_swift_commands.xml:213(para)
+msgid "OpenStack username. Defaults to <code>env[OS_USERNAME]</code>."
 msgstr ""
 
-#: ./doc/common/section_getstart_networking.xml:31(term) ./doc/common/section_getstart_block-storage.xml:35(term)
-msgid "Messaging queue"
+#: ./doc/common/ch_cli_swift_commands.xml:221(para)
+msgid "OpenStack password. Defaults to <code>env[OS_PASSWORD]</code>."
 msgstr ""
 
-#: ./doc/common/section_getstart_networking.xml:32(para)
-msgid "Used by most OpenStack Networking installations to route information between the neutron-server and various agents, as well as a database to store networking state for particular plug-ins."
+#: ./doc/common/ch_cli_swift_commands.xml:229(para)
+msgid "OpenStack tenant ID. Defaults to <code>env[OS_TENANT_ID]</code>."
 msgstr ""
 
-#: ./doc/common/section_getstart_networking.xml:38(para)
-msgid "OpenStack Networking mainly interacts with OpenStack Compute to provide networks and connectivity for its instances."
+#: ./doc/common/ch_cli_swift_commands.xml:237(para)
+msgid "OpenStack tenant name. Defaults to <code>env[OS_TENANT_NAME]</code>."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml:6(title)
-msgid "Configure instances at boot"
+#: ./doc/common/ch_cli_swift_commands.xml:246(para)
+msgid "OpenStack auth URL. Defaults to <code>env[OS_AUTH_URL]</code>."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml:7(para)
-msgid "When you boot instances in an OpenStack cloud, you can use user data or <package>cloud-init</package> to automatically configure instances at boot time. You might want to install some packages, start services, or manage your instance by using a Puppet or Chef server."
+#: ./doc/common/ch_cli_swift_commands.xml:254(para)
+msgid "OpenStack token. Defaults to <code>env[OS_AUTH_TOKEN]</code>. Used with --os-storage-url to bypass the usual username/password authentication."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml:13(title)
-msgid "User data"
+#: ./doc/common/ch_cli_swift_commands.xml:264(para)
+msgid "OpenStack storage URL. Defaults to <code>env[OS_STORAGE_URL]</code>. Overrides the storage url returned during auth. Will bypass authentication when used with --os-auth-token."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml:14(para)
-msgid "User data is the mechanism by which a user can pass information contained in a local file to an instance at launch time. The typical use case is to pass something like a shell script or a configuration file as user data."
+#: ./doc/common/ch_cli_swift_commands.xml:275(para)
+msgid "OpenStack region name. Defaults to <code>env[OS_REGION_NAME]</code>."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml:19(para)
-msgid "User data is sent using the <literal>--user-data <replaceable>/path/to/filename</replaceable></literal> option when calling <placeholder-1/>. This example creates a text file and sends its contents as user data to the instance:"
+#: ./doc/common/ch_cli_swift_commands.xml:284(para)
+msgid "OpenStack Service type. Defaults to <code>env[OS_SERVICE_TYPE]</code>."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml:26(para)
-msgid "The instance can get user data by querying the metadata service through either the OpenStack metadata API or the EC2 compatibility API:"
+#: ./doc/common/ch_cli_swift_commands.xml:293(para)
+msgid "OpenStack Endpoint type. Defaults to <code>env[OS_ENDPOINT_TYPE]</code>."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml:34(para)
-msgid "The Compute service treats user data as a blob. While the previous example uses a text file, user data can be in any format."
+#: ./doc/common/ch_cli_swift_commands.xml:302(para) ./doc/common/ch_cli_keystone_commands.xml:445(para) ./doc/common/ch_cli_trove_commands.xml:558(para)
+msgid "Specify a CA bundle file to use in verifying a TLS (https) server certificate. Defaults to <code>env[OS_CACERT]</code>."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml:38(para)
-msgid "For more information, see <xref linkend=\"config-drive\"/>."
+#: ./doc/common/ch_cli_swift_commands.xml:312(para)
+msgid "Allow swiftclient to access servers without having to verify the SSL certificate. Defaults to <code>env[SWIFTCLIENT_INSECURE]</code> (set to 'true' to enable)."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml:42(package)
-msgid "cloud-init"
+#: ./doc/common/ch_cli_swift_commands.xml:322(para)
+msgid "This option is deprecated and not used anymore. SSL compression should be disabled by default by the system SSL library."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml:43(para)
-msgid "To do something useful with the user data, you must configure the virtual machine image to run a service on boot that gets user data from the metadata service and takes some action based on the contents of the data. The <package>cloud-init</package> package does exactly this. This package is compatible with the Compute metadata service and the Compute configuration drive."
+#: ./doc/common/ch_cli_swift_commands.xml:332(title)
+msgid "swift delete command"
 msgstr ""
 
-#: ./doc/common/section_user-data.xml:51(para)
-msgid "The <package>cloud-init</package> package supports multiple cloud providers. You can use the same virtual machine image in different clouds without modification. The <package>cloud-init</package> package is an open source project and the source code is available on <link href=\"http://launchpad.net/cloud-init\">Launchpad</link>. It is maintained by Canonical, the company that runs the Ubuntu project. All Ubuntu cloud images come pre-installed with <package>cloud-init</package>. However, <package>cloud-init</package> is not designed to be Ubuntu-specific and has been successfully ported to several other platforms including Fedora."
+#: ./doc/common/ch_cli_swift_commands.xml:342(para)
+msgid "Name of container to delete from."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml:66(para)
-msgid "Even if you do not use user data to configure instance behavior at boot time, install <package>cloud-init</package> on images that you create because this package provides useful functionality. For example, the <package>cloud-init</package> package enables you to copy the public key to an account (the <literal>ubuntu</literal> account by default on Ubuntu instances, the <literal>ec2-user</literal> by default in Fedora instances)."
+#: ./doc/common/ch_cli_swift_commands.xml:350(para)
+msgid "Name of object to delete. Specify multiple times for multiple objects."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml:75(para)
-msgid "If you do not have <package>cloud-init</package> installed, you must manually configure your image to get the public key from the metadata service on boot and copy it to the appropriate account."
+#: ./doc/common/ch_cli_swift_commands.xml:362(para)
+msgid "Delete all containers and objects."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml:81(title)
-msgid "<package>cloud-init</package> supported formats and documentation"
+#: ./doc/common/ch_cli_swift_commands.xml:370(para)
+msgid "Do not delete segments of manifest objects."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml:83(para)
-msgid "Look at the <package>cloud-init</package><link href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/userdata.txt\">doc/userdata.txt</link> file the <link href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/files/head:/doc/examples/\">examples</link> directory and the <link href=\"https://help.ubuntu.com/community/CloudInit\">Ubuntu community documentation</link> for details about how to use <package>cloud-init</package>. Some basic examples are provided here."
+#: ./doc/common/ch_cli_swift_commands.xml:378(para)
+msgid "Number of threads to use for deleting objects. Default is 10."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml:93(para)
-msgid "<package>cloud-init</package> supports several input formats for user data. Two commonly used formats are:"
+#: ./doc/common/ch_cli_swift_commands.xml:387(para)
+msgid "Number of threads to use for deleting containers. Default is 10."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml:98(para)
-msgid "Shell scripts (starts with <literal>#!</literal>)"
+#: ./doc/common/ch_cli_swift_commands.xml:396(title)
+msgid "swift download command"
 msgstr ""
 
-#: ./doc/common/section_user-data.xml:102(para)
-msgid "Cloud config files (starts with <literal>#cloud-config</literal>)"
+#: ./doc/common/ch_cli_swift_commands.xml:406(para)
+msgid "Name of container to download from. To download a whole account, omit this and specify --all."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml:108(title)
-msgid "Run a shell script on boot"
+#: ./doc/common/ch_cli_swift_commands.xml:415(para)
+msgid "Name of object to download. Specify multiple times for multiple objects. Omit this to download all objects from the container."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml:109(para)
-msgid "Assuming you have <package>cloud-init</package> installed, the simplest way to configure an instance on boot is to pass a shell script as user data. The shell file must begin with <literal>#!</literal> in order for <package>cloud-init</package> to recognize it as a shell script. This example shows a script that creates a <literal>clouduser</literal> account:"
+#: ./doc/common/ch_cli_swift_commands.xml:428(para)
+msgid "Indicates that you really want to download everything in the account."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml:118(para)
-msgid "Sending a shell script as user data has a similar effect to writing an <filename>/etc/rc.local</filename> script: it executes very late in the boot sequence as root."
+#: ./doc/common/ch_cli_swift_commands.xml:437(para)
+msgid "Marker to use when starting a container or account download."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml:123(title)
-msgid "Cloud-config format"
+#: ./doc/common/ch_cli_swift_commands.xml:446(para)
+msgid "Only download items beginning with &lt;prefix&gt;."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml:124(para)
-msgid "<package>cloud-init</package> supports a YAML-based config format that allows the user to configure a large number of options on a system. User data that begins with <literal>#cloud-config</literal> will be interpreted by <package>cloud-init</package> as cloud-config format."
+#: ./doc/common/ch_cli_swift_commands.xml:454(para)
+msgid "For a single file download, stream the output to &lt;out_file&gt;. Specifying \"-\" as &lt;out_file&gt; will redirect to stdout."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml:132(title)
-msgid "Example: Set the host name"
+#: ./doc/common/ch_cli_swift_commands.xml:464(para)
+msgid "Number of threads to use for downloading objects. Default is 10"
 msgstr ""
 
-#: ./doc/common/section_user-data.xml:133(para)
-msgid "This <package>cloud-init</package> user data example sets the hostname and the FQDN, as well as updating <filename>/etc/hosts</filename> on the instance:"
+#: ./doc/common/ch_cli_swift_commands.xml:473(para)
+msgid "Number of threads to use for downloading containers. Default is 10"
 msgstr ""
 
-#: ./doc/common/section_user-data.xml:145(title)
-msgid "Example: Configure instances with Puppet"
+#: ./doc/common/ch_cli_swift_commands.xml:482(para)
+msgid "Perform download(s), but don't actually write anything to disk."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml:146(para)
-msgid "This <package>cloud-init</package> user data example, based on <link href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/examples/cloud-config-puppet.txt\">doc/examples/cloud-config-puppet.txt</link>, would configure the instance to contact a Puppet server at puppetmaster.example.org and verify its identity by using a certificate."
+#: ./doc/common/ch_cli_swift_commands.xml:491(para)
+msgid "Adds a customized request header to the query, like \"Range\" or \"If-Match\". This argument is repeatable. Example --header \"content-type:text/plain\""
 msgstr ""
 
-#: ./doc/common/section_user-data.xml:174(title)
-msgid "Example: Configure instances with Chef"
+#: ./doc/common/ch_cli_swift_commands.xml:501(para)
+msgid "Skip downloading files that are identical on both sides."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml:175(para)
-msgid "This <package>cloud-init</package> user data example, based on <link href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/examples/cloud-config-chef.txt\">doc/examples/cloud-config/chef.txt</link> and intended for use in an Ubuntu image, adds the Chef apt repository, installs Chef, connects to a Chef server at <literal>https://chefserver.example.com:4000</literal>, and installs Apache:"
+#: ./doc/common/ch_cli_swift_commands.xml:510(title)
+msgid "swift list command"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:6(title)
-msgid "Add security group and rules"
+#: ./doc/common/ch_cli_swift_commands.xml:520(para)
+msgid "Name of container to list object in."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:7(para)
-msgid "The following procedure shows you how to add security groups and add rules to the default security group."
+#: ./doc/common/ch_cli_swift_commands.xml:531(para)
+msgid "Long listing format, similar to ls -l."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:10(title)
-msgid "Add or delete a security group"
+#: ./doc/common/ch_cli_swift_commands.xml:539(para) ./doc/common/ch_cli_swift_commands.xml:688(para)
+msgid "Report sizes in human readable format similar to ls -lh."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:11(para)
-msgid "Use the <placeholder-1/> command to add security groups."
+#: ./doc/common/ch_cli_swift_commands.xml:548(para)
+msgid "Used with -l or --lh, only report totals."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:13(para)
-msgid "The following example shows how to create the <literal>secure1</literal> security group:"
+#: ./doc/common/ch_cli_swift_commands.xml:556(para)
+msgid "Only list items beginning with the prefix."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:21(para)
-msgid "After you create the security group, you can view it in the security group list:"
+#: ./doc/common/ch_cli_swift_commands.xml:564(para)
+msgid "Roll up items with the given delimiter. For containers only. See OpenStack Swift API documentation for what this means."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:30(para)
-msgid "Use the <placeholder-1/> command to delete security groups. You cannot delete the default security group. The default security group has these initial settings:"
+#: ./doc/common/ch_cli_swift_commands.xml:574(title)
+msgid "swift post command"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:36(para)
-msgid "All the traffic originated by the instances (outbound traffic) is allowed"
+#: ./doc/common/ch_cli_swift_commands.xml:577(para)
+msgid "Updates meta information for the account, container, or object. If the container is not found, it will be created automatically."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:40(para)
-msgid "All the traffic destined to instances (inbound traffic) is denied"
+#: ./doc/common/ch_cli_swift_commands.xml:585(para)
+msgid "Name of container to post to."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:44(para)
-msgid "All the instances inside the group are allowed to talk to each other"
+#: ./doc/common/ch_cli_swift_commands.xml:593(para)
+msgid "Name of object to post. Specify multiple times for multiple objects."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:49(para)
-msgid "You can add extra rules into the default security group for handling the egress traffic. Rules are ingress only at this time."
+#: ./doc/common/ch_cli_swift_commands.xml:605(para)
+msgid "Read ACL for containers. Quick summary of ACL syntax: .r:*, .r:-.example.com, .r:www.example.com, account1, account2:user2"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:53(para)
-msgid "The following example deletes the <literal>secure1</literal> group. When you view the security group list, it no longer appears:"
+#: ./doc/common/ch_cli_swift_commands.xml:615(para)
+msgid "Write ACL for containers. Quick summary of ACL syntax: account1 account2:user2"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:65(title)
-msgid "Modify security group rules"
+#: ./doc/common/ch_cli_swift_commands.xml:624(para)
+msgid "Sync To for containers, for multi-cluster replication."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:69(para)
-msgid "You cannot change the default outbound behavior."
+#: ./doc/common/ch_cli_swift_commands.xml:632(para)
+msgid "Sync Key for containers, for multi-cluster replication."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:66(para)
-msgid "The security group rules control the incoming traffic that can access the instances in the group, while all outbound traffic is automatically allowed. <placeholder-1/>Every security group rule is a policy that allows you to specify inbound connections that can access the instance by source address, destination port, and IP protocol (TCP, UDP or ICMP). Currently, you cannot manage ipv6 and other protocols through the security rules, making them permitted by default. To manage such protocols, you can deploy a firewall in front of your OpenStack cloud to control other types of traffic. The command requires the following arguments for both TCP and UDP rules:"
+#: ./doc/common/ch_cli_swift_commands.xml:640(para)
+msgid "Sets a meta data item. This option may be repeated. Example: -m Color:Blue -m Size:Large"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:84(emphasis) ./doc/common/section_cli_nova_secgroups.xml:124(emphasis) ./doc/common/section_cli_nova_secgroups.xml:209(emphasis)
-msgid "&lt;secgroup&gt;"
+#: ./doc/common/ch_cli_swift_commands.xml:649(para)
+msgid "Set request headers. This option may be repeated. Example -H \"content-type:text/plain\""
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:86(para) ./doc/common/section_cli_nova_secgroups.xml:126(para) ./doc/common/section_cli_nova_secgroups.xml:211(para)
-msgid "ID of security group."
+#: ./doc/common/ch_cli_swift_commands.xml:658(title)
+msgid "swift stat command"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:91(emphasis) ./doc/common/section_cli_nova_secgroups.xml:131(emphasis) ./doc/common/section_cli_nova_secgroups.xml:216(emphasis)
-msgid "&lt;ip_proto&gt;"
+#: ./doc/common/ch_cli_swift_commands.xml:668(para)
+msgid "Name of container to stat from."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:98(emphasis) ./doc/common/section_cli_nova_secgroups.xml:223(emphasis)
-msgid "&lt;from_port&gt;"
+#: ./doc/common/ch_cli_swift_commands.xml:676(para)
+msgid "Name of object to stat. Specify multiple times for multiple objects."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:105(emphasis) ./doc/common/section_cli_nova_secgroups.xml:230(emphasis)
-msgid "&lt;to_port&gt;"
+#: ./doc/common/ch_cli_swift_commands.xml:697(title)
+msgid "swift upload command"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:112(emphasis) ./doc/common/section_cli_nova_secgroups.xml:152(emphasis) ./doc/common/section_cli_nova_secgroups.xml:237(emphasis)
-msgid "&lt;cidr&gt;"
+#: ./doc/common/ch_cli_swift_commands.xml:700(para)
+msgid "Uploads specified files and directories to the given container."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:118(para)
-msgid "For ICMP rules, instead of specifying a begin and end port, you specify the allowed ICMP code and ICMP type:"
+#: ./doc/common/ch_cli_swift_commands.xml:707(para)
+msgid "Name of container to upload to."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:133(para)
-msgid "IP protocol (with icmp specified)."
+#: ./doc/common/ch_cli_swift_commands.xml:715(para)
+msgid "Name of file or directory to upload. Specify multiple times for multiple uploads."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:138(emphasis)
-msgid "&lt;ICMP_code&gt;"
+#: ./doc/common/ch_cli_swift_commands.xml:727(para)
+msgid "Only upload files that have changed since the last upload."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:140(para)
-msgid "The ICMP code."
+#: ./doc/common/ch_cli_swift_commands.xml:736(para)
+msgid "Skip uploading files that are identical on both sides."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:145(emphasis)
-msgid "&lt;ICMP_type&gt;"
+#: ./doc/common/ch_cli_swift_commands.xml:744(para)
+msgid "Upload files in segments no larger than &lt;size&gt; (in Bytes) and then create a \"manifest\" file that will download all the segments as if it were the original file."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:147(para)
-msgid "The ICMP type."
+#: ./doc/common/ch_cli_swift_commands.xml:755(para)
+msgid "Upload the segments into the specified container. If not specified, the segments will be uploaded to a &lt;container&gt;_segments container to not pollute the main &lt;container&gt; listings."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:154(para)
-msgid "CIDR for the source address range."
+#: ./doc/common/ch_cli_swift_commands.xml:766(para)
+msgid "Indicates that you want the older segments of manifest objects left alone (in the case of overwrites)."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:159(para)
-msgid "Entering <literal>-1</literal> for both code and type indicates that all ICMP codes and types are allowed."
+#: ./doc/common/ch_cli_swift_commands.xml:775(para)
+msgid "Number of threads to use for uploading full objects. Default is 10."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:164(title)
-msgid "The CIDR notation"
+#: ./doc/common/ch_cli_swift_commands.xml:784(para)
+msgid "Number of threads to use for uploading object segments. Default is 10."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:165(para)
-msgid "That notation allows you to specify a base IP address and a suffix that designates the number of significant bits in the IP address used to identify the network. For example, by specifying a <literal>88.170.60.32/27</literal>, you specify <literal>88.170.60.32</literal> as the <emphasis role=\"bold\">base IP</emphasis> and <literal>27</literal> as the <emphasis role=\"bold\">suffix</emphasis>. Because you use an IPV4 format, only 5 bits are available for the host part (32 minus 27). The <literal>0.0.0.0/0</literal> notation means you allow the entire IPV4 range, which allows all addresses."
+#: ./doc/common/ch_cli_swift_commands.xml:793(para)
+msgid "Set request headers with the syntax header:value. This option may be repeated. Example -H \"content-type:text/plain\"."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:179(para)
-msgid "For example, to allow any IP address to access a web server running on one of your instances inside the default security group:"
+#: ./doc/common/ch_cli_swift_commands.xml:803(para)
+msgid "When used in conjunction with --segment-size it will create a Static Large Object instead of the default Dynamic Large Object."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:188(para)
-msgid "To allow any IP address to ping an instance inside the default security group (Code 0, Type 8 for the ECHO request):"
+#: ./doc/common/ch_cli_swift_commands.xml:813(para)
+msgid "Upload file and name object to &lt;object-name&gt; or upload dir and use &lt;object-name&gt; as object prefix instead of folder name."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml:204(para)
-msgid "To delete a rule, you must specify exactly the same arguments that you used to create it:"
+#: ./doc/common/section_cli_neutron_manage_networks.xml:7(title)
+msgid "Create and manage networks"
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts-domain-management.xml:6(title)
-msgid "Domains"
+#: ./doc/common/section_cli_neutron_manage_networks.xml:8(para)
+msgid "Before you run commands, set the following environment variables:"
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts-domain-management.xml:7(para)
-msgid "A domain defines administrative boundaries for the management of Identity entities. A domain may represent an individual, company, or operator-owned space. It is used for exposing administrative activities directly to the system users."
+#: ./doc/common/section_cli_neutron_manage_networks.xml:15(title)
+msgid "Create networks"
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts-domain-management.xml:10(para)
-msgid "A domain is a collection of tenants, users, and roles. Users may be given a domain's administrator role. A domain administrator may create tenants, users, and groups within a domain and assign roles to users and groups."
+#: ./doc/common/section_cli_neutron_manage_networks.xml:18(para)
+msgid "List the extensions of the system:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_get_console.xml:6(title)
-msgid "Access an instance through a console"
+#: ./doc/common/section_cli_neutron_manage_networks.xml:34(para)
+msgid "Create a network:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_get_console.xml:7(para)
-msgid "To access an instance through a VNC console, run the following command:"
+#: ./doc/common/section_cli_neutron_manage_networks.xml:53(para)
+msgid "Some fields of the created network are invisible to non-admin users."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_get_console.xml:8(replaceable) ./doc/common/section_cli_nova_startstop.xml:14(replaceable) ./doc/common/section_cli_nova_startstop.xml:18(replaceable) ./doc/common/section_cli_nova_startstop.xml:35(replaceable) ./doc/common/section_cli_nova_startstop.xml:40(replaceable) ./doc/common/section_cli_nova_boot.xml:188(replaceable)
-msgid "INSTANCE_NAME"
+#: ./doc/common/section_cli_neutron_manage_networks.xml:58(para)
+msgid "Create a network with specified provider network type:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_get_console.xml:9(para)
-msgid "The command returns a URL from which you can access your instance:"
+#: ./doc/common/section_cli_neutron_manage_networks.xml:77(para)
+msgid "Just as shown previously, the unknown option <literal>--provider:network-type</literal> is used to create a <literal>local</literal> provider network."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_get_console.xml:15(para)
-msgid "To access an instance through a non-VNC console, specify the <parameter>novnc</parameter> parameter instead of the <parameter>xvpvnc</parameter> parameter."
+#: ./doc/common/section_cli_neutron_manage_networks.xml:85(title)
+msgid "Create subnets"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml:88(para)
+msgid "Create a subnet:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml:106(para)
+msgid "The <placeholder-1/> command has the following positional and optional parameters:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml:111(para)
+msgid "The name or ID of the network to which the subnet belongs."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml:113(para)
+msgid "In this example, <literal>net1</literal> is a positional argument that specifies the network name."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml:118(para)
+msgid "The CIDR of the subnet."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml:119(para)
+msgid "In this example, <literal>192.168.2.0/24</literal> is a positional argument that specifies the CIDR."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml:125(para)
+msgid "The subnet name, which is optional."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml:127(para)
+msgid "In this example, <literal>--name subnet1</literal> specifies the name of the subnet."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml:136(title)
+msgid "Create routers"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml:139(para)
+msgid "Create a router:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml:140(replaceable)
+msgid "router1"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml:152(para)
+msgid "Take note of the unique router identifier returned, this will be required in subsequent steps."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml:156(para)
+msgid "Link the router to the external provider network:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml:157(replaceable) ./doc/common/section_cli_neutron_manage_networks.xml:164(replaceable)
+msgid "ROUTER"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml:157(replaceable)
+msgid "NETWORK"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml:158(para)
+msgid "Replace <replaceable>ROUTER</replaceable> with the unique identifier of the router, replace <replaceable>NETWORK</replaceable> with the unique identifier of the external provider network."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml:163(para)
+msgid "Link the router to the subnet:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml:164(replaceable)
+msgid "SUBNET"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml:165(para)
+msgid "Replace <replaceable>ROUTER</replaceable> with the unique identifier of the router, replace <replaceable>SUBNET</replaceable> with the unique identifier of the subnet."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml:172(title)
+msgid "Create ports"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml:175(para)
+msgid "Create a port with specified IP address:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml:194(para)
+msgid "In the previous command, <literal>net1</literal> is the network name, which is a positional argument. <literal>--fixed-ip ip_address=192.168.2.40</literal> is an option, which specifies the port's fixed IP address we wanted."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml:201(para)
+msgid "When creating a port, you can specify any unallocated IP in the subnet even if the address is not in a pre-defined pool of allocated IP addresses (set by your cloud provider)."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml:208(para)
+msgid "Create a port without specified IP address:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml:229(para)
+msgid "Note that the system allocates one IP address if you do not specify an IP address in the <placeholder-1/> command."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml:234(para)
+msgid "Query ports with specified fixed IP addresses:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml:243(para)
+msgid "<literal>--fixed-ips ip_address=192.168.2.2 ip_address=192.168.2.40</literal> is one unknown option."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml:246(para)
+msgid "<emphasis role=\"bold\">How to find unknown options?</emphasis> The unknown options can be easily found by watching the output of <literal>create_xxx</literal> or <literal>show_xxx</literal> command. For example, in the port creation command, we see the fixed_ips fields, which can be used as an unknown option."
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-arch.xml:23(None)
+msgid "@@image: '../common/figures/objectstorage-arch.png'; md5=90f6c7cf3947d7987eeb55d657cdc927"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-arch.xml:60(None)
+msgid "@@image: '../common/figures/objectstorage-nodes.png'; md5=2aa7eb3bddcf6826f33469920dc2a9c3"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-arch.xml:11(title)
+msgid "Cluster architecture"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-arch.xml:13(title)
+msgid "Access tier"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-arch.xml:14(para)
+msgid "Large-scale deployments segment off an access tier, which is considered the Object Storage system's central hub. The access tier fields the incoming API requests from clients and moves data in and out of the system. This tier consists of front-end load balancers, ssl-terminators, and authentication services. It runs the (distributed) brain of the Object Storage system: the proxy server processes."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-arch.xml:20(title)
+msgid "Object Storage architecture"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-arch.xml:27(para)
+msgid "Because access servers are collocated in their own tier, you can scale out read/write access regardless of the storage capacity. For example, if a cluster is on the public Internet, requires SSL termination, and has a high demand for data access, you can provision many access servers. However, if the cluster is on a private network and used primarily for archival purposes, you need fewer access servers."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-arch.xml:32(para)
+msgid "Since this is an HTTP addressable storage service, you may incorporate a load balancer into the access tier."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-arch.xml:34(para)
+msgid "Typically, the tier consists of a collection of 1U servers. These machines use a moderate amount of RAM and are network I/O intensive. Since these systems field each incoming API request, you should provision them with two high-throughput (10GbE) interfaces - one for the incoming \"front-end\" requests and the other for the \"back-end\" access to the object storage nodes to put and fetch data."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-arch.xml:40(title) ./doc/common/section_objectstorage-arch.xml:69(title)
+msgid "Factors to consider"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-arch.xml:41(para)
+msgid "For most publicly facing deployments as well as private deployments available across a wide-reaching corporate network, you use SSL to encrypt traffic to the client. SSL adds significant processing load to establish sessions between clients, which is why you have to provision more capacity in the access layer. SSL may not be required for private deployments on trusted networks."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-arch.xml:49(title)
+msgid "Storage nodes"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-arch.xml:50(para)
+msgid "In most configurations, each of the five zones should have an equal amount of storage capacity. Storage nodes use a reasonable amount of memory and CPU. Metadata needs to be readily available to return objects quickly. The object stores run services not only to field incoming requests from the access tier, but to also run replicators, auditors, and reapers. You can provision object stores provisioned with single gigabit or 10 gigabit network interface depending on the expected workload and desired performance."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-arch.xml:57(title) ./doc/common/section_objectstorage-characteristics.xml:46(title) ./doc/common/section_storage-concepts.xml:21(td)
+msgid "Object Storage (swift)"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-arch.xml:64(para)
+msgid "Currently, a 2TB or 3TB SATA disk delivers good performance for the price. You can use desktop-grade drives if you have responsive remote hands in the datacenter and enterprise-grade drives if you don't."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-arch.xml:70(para)
+msgid "You should keep in mind the desired I/O performance for single-threaded requests . This system does not use RAID, so a single disk handles each request for an object. Disk performance impacts single-threaded response rates."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-arch.xml:73(para)
+msgid "To achieve apparent higher throughput, the object storage system is designed to handle concurrent uploads/downloads. The network I/O capacity (1GbE, bonded 1GbE pair, or 10GbE) should match your desired concurrent throughput needs for reads and writes."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_example_usage.xml:6(title)
+msgid "keystone command-line client example usage"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_example_usage.xml:7(para)
+msgid "Before you can use keystone client commands, you must download and source an OpenStack RC file. For information, see the <citetitle>OpenStack Admin User Guide</citetitle>."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_example_usage.xml:10(para)
+msgid "The keystone command-line client uses the following syntax:"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_example_usage.xml:12(replaceable)
+msgid "PARAMETER"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_example_usage.xml:12(replaceable)
+msgid "ARGUMENT"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_example_usage.xml:13(para)
+msgid "For example, you can run the <placeholder-1/> and <placeholder-2/> commands, as follows:"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_example_usage.xml:22(replaceable) ./doc/common/section_cli_keystone_example_usage.xml:23(replaceable)
+msgid "token"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_example_usage.xml:22(replaceable) ./doc/common/section_cli_keystone_example_usage.xml:23(replaceable)
+msgid "endpoint"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_example_usage.xml:31(replaceable)
+msgid "id"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_example_usage.xml:34(para)
+msgid "For information about using the keystone client commands to create and manage users, roles, and projects, see the <citetitle>OpenStack Admin User Guide</citetitle>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml:5(title)
+msgid "Manage bare-metal nodes"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml:6(para)
+msgid "The bare-metal driver for OpenStack Compute manages provisioning of physical hardware by using common cloud APIs and tools such as Orchestration (Heat). The use case for this driver is for single tenant clouds such as a high-performance computing cluster or for deploying OpenStack itself."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml:10(para)
+msgid "If you use the bare-metal driver, you must create a network interface and add it to a bare-metal node. Then, you can launch an instance from a bare-metal image."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml:13(para)
+msgid "Development efforts are focused on moving the driver out of the Compute code base in the Icehouse release."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml:15(para)
+msgid "You can list and delete bare-metal nodes. When you delete a node, any associated network interfaces are removed. You can list and remove network interfaces that are associated with a bare-metal node."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml:19(title)
+msgid "Commands"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml:20(para)
+msgid "The following commands can be used to manage bare-metal nodes."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml:22(para)
+msgid "<placeholder-1/>. Adds a network interface to a bare-metal node."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml:26(para)
+msgid "<placeholder-1/>. Lists network interfaces associated with a bare-metal node."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml:30(para)
+msgid "<placeholder-1/>. Removes a network interface from a bare-metal node."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml:34(para)
+msgid "<placeholder-1/>. Creates a bare-metal node."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml:38(para)
+msgid "<placeholder-1/>. Removes a bare-metal node and any associated interfaces."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml:42(para)
+msgid "<placeholder-1/>. Lists available bare-metal nodes."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml:46(para)
+msgid "<placeholder-1/>. Shows information about a bare-metal node."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml:51(title)
+msgid "Create a bare-metal node"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml:52(para)
+msgid "When you create a bare-metal node, your PM address, username, and password should match those that are configured in your hardware's BIOS/IPMI configuration."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml:57(para)
+msgid "The following example shows the command and results from creating a node with the PM address <filename>1.2.3.4</filename>, the PM username <literal>ipmi</literal>, and password <literal>ipmi</literal>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml:79(title)
+msgid "Add a network interface to the node:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml:80(para)
+msgid "For each NIC on the node, you must create an interface, specifying the interface's MAC address."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml:92(title)
+msgid "Launch an instance from a bare-metal image:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml:94(para)
+msgid "A bare-metal instance is an instance created directly on a physical machine without any virtualization layer running underneath it. Nova retains power control via IPMI. In some situations, Nova may retain network control via Neutron and OpenFlow."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml:107(para)
+msgid "Set the <parameter>--availability_zone</parameter> parameter to specify which zone or node to use to start the server. Separate the zone from the host name with a comma. For example:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml:110(replaceable)
+msgid "HOST"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml:110(replaceable)
+msgid "NODE"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml:111(para)
+msgid "<literal>host</literal> is optional for the <literal>--availability_zone</literal> parameter. You can specify simply <literal>zone:,node</literal>. You must still use the comma."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml:118(title)
+msgid "List bare-metal nodes and interfaces:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml:120(para)
+msgid "Use the <placeholder-1/> command to view all bare-metal nodes and interfaces. When a node is in use, its status includes the UUID of the instance that runs on it:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml:130(title)
+msgid "Show details for a bare-metal node:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml:131(para)
+msgid "Use the <placeholder-1/> command to view the details for a bare-metal node."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml:6(title)
+msgid "Troubleshoot the Identity service"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml:7(para)
+msgid "To troubleshoot the Identity service, review the logs in the <filename>/var/log/keystone/keystone.log</filename> file."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml:10(para)
+msgid "Use the <filename>/etc/keystone/logging.conf</filename> file to configure the location of log files."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml:13(para)
+msgid "The logs show the components that have come in to the WSGI request, and ideally show an error that explains why an authorization request failed. If you do not see the request in the logs, run keystone with <parameter>--debug</parameter> parameter. Pass the <parameter>--debug</parameter> parameter before the command parameters."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml:20(title)
+msgid "Debug PKI middleware"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml:21(para)
+msgid "If you receive an <literal>Invalid OpenStack Identity Credentials</literal> message when you talk to an OpenStack service, it might be caused by the changeover from UUID tokens to PKI tokens in the Grizzly release. Learn how to troubleshoot this error."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml:26(para)
+msgid "The PKI-based token validation scheme relies on certificates from Identity that are fetched through HTTP and stored in a local directory. The location for this directory is specified by the <literal>signing_dir</literal> configuration option. In your services configuration file, look for a section like this:"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml:41(para)
+msgid "If your service lacks this stanza, the <link href=\"https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/middleware/auth_token.py#L198\">keystoneclient/middleware/auth_token.py</link> file specifies the defaults. If no value is specified for this directory, it <link href=\"https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/middleware/auth_token.py#L299\">defaults to a secure temporary directory.</link> Initialization code for the service checks that the directory exists and is writable. If it does not exist, the code tries to create it. If this fails, the service fails to start. However, it often succeeds but problems occur later."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml:53(para)
+msgid "The first thing to check is that the <literal>signing_dir</literal> does, in fact, exist. If it does, check for the presence of the certificate files inside there:"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml:64(para)
+msgid "This directory contains two certificates and the token revocation list. If these files are not present, your service cannot fetch them from Identity. To troubleshoot, try to talk to Identity to make sure it correctly serves files, as follows:"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml:70(para)
+msgid "This command fetches the signing certificate:"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml:81(para)
+msgid "Note the expiration dates of the certificate:"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml:84(para)
+msgid "The token revocation list is updated once a minute, but the certificates are not. One possible problem is that the certificates are the wrong files or garbage. You can remove these files and run another command against your server: They are fetched on demand."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml:89(para)
+msgid "The Identity service log should show the access of the certificate files. You might have to turn up your logging levels. Set <literal>debug = True</literal> and <literal>verbose = True</literal> in your Identity configuration file and restart the Identity server."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml:98(para)
+msgid "If the files do not appear in your directory after this, it is likely one of the following issues:"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml:102(para)
+msgid "Your service is configured incorrectly and cannot talk to Identity. Check the <literal>auth_port</literal> and <literal>auth_host</literal> values and make sure that you can talk to that service through cURL, as shown previously."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml:110(para)
+msgid "Your signing directory is not writable. Use the <placeholder-1/> command to change its permissions so that the service (POSIX) user can write to it. Verify the change through <placeholder-2/> and <placeholder-3/> commands."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml:118(para)
+msgid "The SELinux policy is denying access to the directory."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml:122(para)
+msgid "SELinux troubles often occur when you use Fedora/RHEL-based packages and you choose configuration options that do not match the standard policy. Run the <placeholder-1/> command. If that makes a difference, you should relabel the directory. If you are using a sub-directory of the <filename>/var/cache/</filename> directory, run the following command:"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml:131(para)
+msgid "If you are not using a <filename>/var/cache</filename> sub-directory, you should. Modify the <literal>signing_dir</literal> configuration option for your service and restart."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml:135(para)
+msgid "Set back to <literal>setenforce enforcing</literal> to confirm that your changes solve the problem."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml:137(para)
+msgid "If your certificates are fetched on demand, the PKI validation is working properly. Most likely, the token from Identity is not valid for the operation you are attempting to perform, and your user needs a different role for the operation."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml:144(title)
+msgid "Debug signing key file errors"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml:145(para)
+msgid "If an error occurs when the signing key file opens, it is possible that the person who ran the <placeholder-1/> command to generate certificates and keys did not use the correct user. When you run the <placeholder-2/> command, Identity generates a set of certificates and keys in <filename>/etc/keystone/ssl*</filename>, which is owned by root:root."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml:154(para)
+msgid "This can present a problem when you run the Identity daemon under the keystone user account (nologin) when you try to run PKI. Unless you run the <placeholder-1/> command against the files keystone:keystone or run the <placeholder-2/> command with the <parameter>--keystone-user</parameter> and <parameter>--keystone-group</parameter> parameters, you get an error, as follows:"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml:172(title)
+msgid "Flush expired tokens from the token database table"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml:174(para)
+msgid "As you generate tokens, the token database table on the Identity server grows. To clear the token table, an administrative user must run the <placeholder-1/> command to flush the tokens. When you flush tokens, expired tokens are deleted and traceability is eliminated."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml:180(para)
+msgid "Use <placeholder-1/> to schedule this command to run frequently based on your workload. For large workloads, running it every minute is recommended."
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml:5(title)
+msgid "Database service overview"
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml:6(para)
+msgid "The Database service provides scalable and reliable cloud provisioning functionality for both relational and non-relational database engines. Users can quickly and easily utilize database features without the burden of handling complex administrative tasks. Cloud users and database administrators can provision and manage multiple database instances as needed."
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml:7(para)
+msgid "The Database service provides resource isolation at high performance levels, and automates complex administrative tasks such as deployment, configuration, patching, backups, restores, and monitoring."
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml:9(title)
+msgid "Process flow example."
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml:9(para)
+msgid "Here is a high-level process flow example for using Database services:"
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml:12(para)
+msgid "Administrator sets up infrastructure:"
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml:15(para)
+msgid "OpenStack administrator installs the Database service."
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml:18(para)
+msgid "She creates one image for each type of database the administrator wants to have (one for MySQL, one for MongoDB, and so on)."
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml:23(para)
+msgid "OpenStack administrator updates the datastore to use the new images, using the <placeholder-1/> command."
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml:30(para)
+msgid "End user uses database service:"
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml:33(para)
+msgid "Now that the basic infrastructure is set up, an end user can create a Trove instance (database) whenever the user wants, using the <placeholder-1/> command."
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml:41(replaceable)
+msgid "instanceID"
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml:39(para)
+msgid "The end user gets the IP address of the Trove instance by using the <placeholder-1/> command to get the ID of the instance, and then using the <placeholder-2/> command to get the IP address."
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml:44(para)
+msgid "The end user can now access the Trove instance using typical database access commands. MySQL example:"
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml:45(replaceable)
+msgid "trove_ip_address"
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml:51(title)
+msgid "Components:"
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml:51(para)
+msgid "The Database service includes the following components:"
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml:55(para)
+msgid "<code>python-troveclient</code> command-line client. A CLI that communicates with the <code>trove-api</code> component."
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml:58(para)
+msgid "<code>trove-api</code> component. Provides an OpenStack-native RESTful API that supports JSON to provision and manage Trove instances."
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml:62(para)
+msgid "<code>trove-conductor</code> service. Runs on the host, and receives messages from guest instances that want to update information on the host."
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml:65(para)
+msgid "<code>trove-taskmanager</code> service. Instruments the complex system flows that support provisioning instances, managing the lifecycle of instances, and performing operations on instances."
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml:68(para)
+msgid "<code>trove-guestagent</code> service. Runs within the guest instance. Manages and performs operations on the database itself."
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml:6(title)
+msgid "Migrate the Identity Service database"
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml:7(para)
+msgid "Between revisions of the Identity Service project, you might need to complete SQL migrations. The Identity Service project uses SQLAlchemy-migrate (see <link href=\"http://code.google.com/p/sqlalchemy-migrate/\">http://code.google.com/p/sqlalchemy-migrate/</link>) to migrate the SQL database between revisions. For core components, the source code stores migrations in a central repository under a <filename>keystone/common/sql/migrate_repo</filename> directory."
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml:17(para)
+msgid "Extensions to the Identity Service might also require SQL migrations. The directory <filename>keystone/contrib/example</filename> in the keystone repository contains a sample extension migration."
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml:23(title)
+msgid "To set up a migration for an extension"
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml:25(para)
+msgid "Create a directory structure where <literal>my_extension</literal> is the name of the extension, as follows: <filename>keystone/contrib/my_extension/migrate_repo/versions/</filename>."
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml:31(para)
+msgid "Create empty <filename>__init__.py</filename> files in the <filename>migrate_repo</filename> and <filename>versions</filename> subdirectories."
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml:37(para)
+msgid "Create a <filename>migrate.cfg</filename> configuration file in the <filename>migrate_repo</filename> subdirectory, which conforms to a key/value <filename>.ini</filename> file format."
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml:41(para)
+msgid "An example configuration file:"
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml:49(title)
+msgid "To test a migration for a specific extension"
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml:50(para)
+msgid "You can use the <placeholder-1/> command with the <parameter>--extension</parameter> parameter for both the <placeholder-2/> and <placeholder-3/> commands. Ensure that the required configuration files exist before completing these steps."
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml:57(para)
+msgid "Test your migrations with an <literal>example</literal> extension:"
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml:62(para)
+msgid "Migrate to version 1:"
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml:66(para)
+msgid "Migrate back to version 0:"
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml:70(para)
+msgid "Check the version:"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:9(title)
+msgid "Troubleshoot Compute"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:10(para)
+msgid "Common problems for Compute typically involve misconfigured networking or credentials that are not sourced properly in the environment. Also, most flat networking configurations do not enable <placeholder-1/> or <placeholder-2/> from a compute node to the instances that run on that node. Another common problem is trying to run 32-bit images on a 64-bit compute node. This section shows you how to troubleshoot Compute."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:19(title)
+msgid "Compute service logging"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:20(para)
+msgid "Compute stores a log file for each service in <filename>/var/log/nova</filename>. For example, <filename>nova-compute.log</filename> is the log for the <systemitem class=\"service\">nova-compute</systemitem> service. You can set the following options to format log strings for the nova.log module in the <filename>nova.conf</filename> file:"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:29(literal)
+msgid "logging_context_format_string"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:32(literal)
+msgid "logging_default_format_string"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:35(para)
+msgid "If the log level is set to <literal>debug</literal>, you can also specify <literal>logging_debug_format_suffix</literal> to append extra formatting. For information about what variables are available for the formatter see: <link href=\"http://docs.python.org/library/logging.html#formatter\">http://docs.python.org/library/logging.html#formatter</link>."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:42(para)
+msgid "You have two options for logging for OpenStack Compute based on configuration settings. In <filename>nova.conf</filename>, include the <literal>logfile</literal> option to enable logging. Alternatively you can set <literal>use_syslog = 1</literal> so that the nova daemon logs to syslog."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:50(title)
+msgid "Guru Meditation reports"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:51(para)
+msgid "A Guru Meditation report is sent by the Compute Service upon receipt of the <systemitem>SIGUSR1</systemitem> signal. This report is a general-purpose error report, including a complete report of the service's current state, and is sent to <systemitem>stderr</systemitem>."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:55(para)
+msgid "For example, if you redirect error output to <filename>nova-api-err.log</filename> using <placeholder-1/>, resulting in the process ID 8675, you can then run:"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:59(para)
+msgid "This command triggers the Guru Meditation report to be printed to <filename>/var/log/nova/nova-api-err.log</filename>."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:63(para)
+msgid "Package Displays information about the package to which the process belongs, including version information."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:65(para)
+msgid "Threads Displays stack traces and thread IDs for each of the threads within the process."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:67(para)
+msgid "Green Threads Displays stack traces for each of the green threads within the process (green threads do not have thread IDs)."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:69(para)
+msgid "Configuration Lists all configuration options currently accessible through the CONF object for the current process."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:61(para)
+msgid "The report has the following sections: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:72(para)
+msgid "For more information, see <link href=\"http://docs.openstack.org/developer/nova/devref/gmr.html\">Guru Meditation Reports</link>."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:77(title)
+msgid "Common errors and fixes for Compute"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:78(para)
+msgid "The <link href=\"ask.openstack.org\">ask.openstack.org</link> site offers a place to ask and answer questions, and you can also mark questions as frequently asked questions. This section describes some errors people have posted previously. Bugs are constantly being fixed, so online resources are a great way to get the most up-to-date errors and fixes."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:86(title)
+msgid "Credential errors, 401, and 403 forbidden errors"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:93(para)
+msgid "<emphasis role=\"bold\">Manual method</emphasis>. Get get the <filename>novarc</filename> file from the project ZIP file, save existing credentials in case of override. and manually source the <filename>novarc</filename> file."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:103(para)
+msgid "<emphasis role=\"bold\">Script method</emphasis>. Generates <filename>novarc</filename> from the project ZIP file and sources it for you."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:88(para)
+msgid "Missing credentials cause a <errorcode>403</errorcode><errortext>forbidden</errortext> error. To resolve this issue, use one of these methods:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:110(para)
+msgid "When you run <systemitem class=\"service\">nova-api</systemitem> the first time, it generates the certificate authority information, including <filename>openssl.cnf</filename>. If you start the CA services before this, you might not be able to create your ZIP file. Restart the services. When your CA information is available, create your ZIP file."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:118(para)
+msgid "Also, check your HTTP proxy settings to see whether they cause problems with <filename>novarc</filename> creation."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:123(title)
+msgid "Instance errors"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:124(para)
+msgid "Sometimes a particular instance shows <literal>pending</literal> or you cannot SSH to it. Sometimes the image itself is the problem. For example, when you use flat manager networking, you do not have a DHCP server and certain images do not support interface injection; you cannot connect to them. The fix for this problem is to use an image that does support this method, such as Ubuntu, which obtains an IP address correctly with FlatManager network settings."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:134(para)
+msgid "To troubleshoot other possible problems with an instance, such as an instance that stays in a spawning state, check the directory for the particular instance under <filename>/var/lib/nova/instances</filename> on the <systemitem class=\"service\">nova-compute</systemitem> host and make sure that these files are present:"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:143(filename)
+msgid "libvirt.xml"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:146(filename)
+msgid "disk"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:149(filename)
+msgid "disk-raw"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:152(filename)
+msgid "kernel"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:155(filename)
+msgid "ramdisk"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:158(para)
+msgid "After the instance starts, <filename>console.log</filename>"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:162(para)
+msgid "If any files are missing, empty, or very small, the <systemitem class=\"service\">nova-compute</systemitem> service did not successfully download the images from the Image Service."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:167(para)
+msgid "Also check <filename>nova-compute.log</filename> for exceptions. Sometimes they do not appear in the console output."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:170(para)
+msgid "Next, check the log file for the instance in the <filename>/var/log/libvirt/qemu</filename> directory to see if it exists and has any useful error messages in it."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:174(para)
+msgid "Finally, from the <filename>/var/lib/nova/instances</filename> directory for the instance, see if this command returns an error:"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:181(title)
+msgid "Empty log output for Linux instances"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:182(para)
+msgid "You can view the log output of running instances from either the <guilabel>Log</guilabel> tab of the dashboard or the output of <placeholder-1/>. In some cases, the log output of a running Linux instance will be empty or only display a single character (for example, the <keycap>?</keycap> character)."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:189(para)
+msgid "This occurs when the Compute service attempts to retrieve the log output of the instance via a serial console while the instance itself is not configured to send output to the console. To rectify this, append the following parameters to kernel arguments specified in the instance's boot loader:"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:196(para)
+msgid "Upon rebooting, the instance will be configured to send output to the Compute service."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:201(title)
+msgid "Reset the state of an instance"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:202(para)
+msgid "If an instance remains in an intermediate state, such as <literal>deleting</literal>, you can use the <placeholder-1/> command to manually reset the state of an instance to an error state. You can then delete the instance. For example:"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:209(para)
+msgid "You can also use the <parameter>--active</parameter> parameter to force the instance back to an active state instead of an error state. For example:"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:215(title)
+msgid "Injection problems"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:216(para)
+msgid "If instances do not boot or boot slowly, investigate file injection as a cause."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:218(para)
+msgid "To disable injection in libvirt, set the following in <filename>nova.conf</filename>:"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml:223(para)
+msgid "If you have not enabled the configuration drive and you want to make user-specified files available from the metadata server for to improve performance and avoid boot failure if injection fails, you must disable injection."
 msgstr ""
 
 #: ./doc/common/section_getstart_telemetry.xml:5(title)
@@ -7753,116 +7685,1742 @@ msgstr ""
 msgid "These services communicate by using the OpenStack messaging bus. Only the collector and API server have access to the data store."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml:6(title)
-msgid "Install XenServer and XCP"
+#: ./doc/common/section_cli_cinder_read-only-volumes.xml:6(title)
+msgid "Set a volume to read-only access"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml:8(para)
-msgid "Before you can run OpenStack with XCP or XenServer, you must install the software on <link href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/installation.html#sys_requirements\">an appropriate server</link>."
+#: ./doc/common/section_cli_cinder_read-only-volumes.xml:7(para)
+msgid "To give multiple users shared, secure access to the same data, you can set a volume to read-only access."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml:13(para)
-msgid "Xen is a type 1 hypervisor: When your server starts, Xen is the first software that runs. Consequently, you must install XenServer or XCP before you install the operating system where you want to run OpenStack code. The OpenStack services then run in a virtual machine that you install on top of XenServer."
+#: ./doc/common/section_cli_cinder_read-only-volumes.xml:9(para)
+msgid "Run the following command to set a volume to read-only access:"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml:20(para)
-msgid "Before you can install your system, decide whether to install a free or paid edition of Citrix XenServer or Xen Cloud Platform from Xen.org. Download the software from these locations:"
+#: ./doc/common/section_cli_cinder_read-only-volumes.xml:11(replaceable)
+msgid "VOLUME"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml:28(link)
-msgid "http://www.citrix.com/XenServer/download"
+#: ./doc/common/section_cli_cinder_read-only-volumes.xml:11(replaceable)
+msgid "BOOLEAN"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml:33(link)
-msgid "http://www.xen.org/download/xcp/index.html"
+#: ./doc/common/section_cli_cinder_read-only-volumes.xml:12(para)
+msgid "<replaceable>VOLUME</replaceable> is the ID of the target volume and <replaceable>BOOLEAN</replaceable> is a flag that enables read-only or read/write access to the volume."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml:36(para)
-msgid "When you install many servers, you might find it easier to perform <link href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/installation.html#pxe_boot_install\">PXE boot installations of XenServer or XCP</link>. You can also package any post-installation changes that you want to make to your XenServer by <link href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/supplemental_pack_ddk.html\">creating your own XenServer supplemental pack</link>."
+#: ./doc/common/section_cli_cinder_read-only-volumes.xml:15(para)
+msgid "The following values for <replaceable>BOOLEAN</replaceable> are valid:"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml:46(para)
-msgid "You can also install the <package>xcp-xenapi</package> package on Debian-based distributions to get XCP. However, this is not as mature or feature complete as above distributions. This modifies your boot loader to first boot Xen and boot your existing OS on top of Xen as Dom0. The xapi daemon runs in Dom0. Find more details at <link href=\"http://wiki.xen.org/wiki/Project_Kronos\">http://wiki.xen.org/wiki/Project_Kronos</link>."
+#: ./doc/common/section_cli_cinder_read-only-volumes.xml:19(para)
+msgid "<literal>true</literal>. Sets the read-only flag in the volume. When you attach the volume to an instance, the instance checks for this flag to determine whether to restrict volume access to read-only."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml:55(para)
-msgid "Make sure you use the EXT type of storage repository (SR). Features that require access to VHD files (such as copy on write, snapshot and migration) do not work when you use the LVM SR. Storage repository (SR) is a XenAPI-specific term relating to the physical storage where virtual disks are stored."
+#: ./doc/common/section_cli_cinder_read-only-volumes.xml:25(para)
+msgid "<literal>false</literal>. Sets the volume to read/write access."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml:61(para)
-msgid "On the XenServer/XCP installation screen, choose the <guilabel>XenDesktop Optimized</guilabel> option. If you use an answer file, make sure you use <literal>srtype=\"ext\"</literal> in the <option>installation</option> tag of the answer file."
+#: ./doc/common/section_compute-configure-ec2.xml:6(title)
+msgid "Configure the EC2 API"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml:69(title)
-msgid "Post-installation steps"
+#: ./doc/common/section_compute-configure-ec2.xml:7(para)
+msgid "You can set options in the <filename>nova.conf</filename> configuration file to control which network address and port the EC2 API listens on, the formatting of some API responses, and authentication related options."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml:70(para)
-msgid "Complete these steps to install OpenStack in your XenServer system:"
+#: ./doc/common/section_compute-configure-ec2.xml:11(para)
+msgid "To customize these options for OpenStack EC2 API, use the configuration option settings documented in <xref linkend=\"config_table_nova_ec2\"/>."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml:74(para)
-msgid "For resize and migrate functionality, complete the changes described in the <citetitle>Configure resize</citetitle> section in the <link href=\"../config-reference/content/index.html\"><citetitle>OpenStack Configuration Reference</citetitle></link>."
+#: ./doc/common/section_cli_keystone_credentials.xml:6(title)
+msgid "Set up credentials for the keystone client"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml:82(para)
-msgid "Install the VIF isolation rules to help prevent mac and IP address spoofing."
+#: ./doc/common/section_cli_keystone_credentials.xml:7(para)
+msgid "You can configure the <package>python-keystoneclient</package> with admin credentials with either an authentication token or a user name and password."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml:86(para)
-msgid "Install the XenAPI plug-ins. See the following section."
+#: ./doc/common/section_cli_keystone_credentials.xml:12(title)
+msgid "To configure the keystone client with an authentication token"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml:90(para)
-msgid "To support AMI type images, you must set up <literal>/boot/guest</literal> symlink/directory in Dom0. For detailed instructions, see next section."
+#: ./doc/common/section_cli_keystone_credentials.xml:15(para)
+msgid "Export your keystone endpoint to the <varname>OS_SERVICE_ENDPOINT</varname> environment variable:"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml:96(para)
-msgid "To support resize/migration, set up an ssh trust relation between your XenServer hosts, and ensure <literal>/images</literal> is properly set up. See next section for more details."
+#: ./doc/common/section_cli_keystone_credentials.xml:21(para)
+msgid "Export the administrator service token to the <varname>OS_SERVICE_TOKEN</varname> environment variable:"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml:102(para)
-msgid "Create a Paravirtualized virtual machine that can run the OpenStack compute code."
+#: ./doc/common/section_cli_keystone_credentials.xml:26(para) ./doc/common/section_cli_keystone_credentials.xml:80(para)
+msgid "Alternatively, you can specify these parameters on any keystone client command:"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml:106(para)
-msgid "Install and configure the <systemitem class=\"service\">nova-compute</systemitem> in the above virtual machine."
+#: ./doc/common/section_cli_keystone_credentials.xml:30(para)
+msgid "<parameter>--os-endpoint <replaceable>SERVICE_ENDPOINT</replaceable></parameter>. An endpoint to use instead of the one in the service catalog. Defaults to <code>env[OS_SERVICE_ENDPOINT]</code>."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml:111(para)
-msgid "For more information, see how DevStack performs the last three steps for developer deployments. For more information about DevStack, see <citetitle>Getting Started With XenServer and Devstack</citetitle> (<link href=\"https://github.com/openstack-dev/devstack/blob/master/tools/xen/README.md\">https://github.com/openstack-dev/devstack/blob/master/tools/xen/README.md</link>). Find more information about the first step, see <citetitle>Multi Tenancy Networking Protections in XenServer</citetitle> (<link href=\"https://github.com/openstack/nova/blob/master/plugins/xenserver/doc/networking.rst\">https://github.com/openstack/nova/blob/master/plugins/xenserver/doc/networking.rst</link>). For information about how to install the XenAPI plug-ins, see <citetitle>XenAPI README</citetitle> (<link href=\"https://github.com/openstack/nova/blob/master/plugins/xenserver/xenapi/README\">https://github.com/openstack/nova/blob/master/plugins/xenserver/xenapi/README</link>)."
+#: ./doc/common/section_cli_keystone_credentials.xml:39(para)
+msgid "<parameter>--os-token <replaceable>SERVICE_TOKEN</replaceable></parameter>. An existing token to use instead of the one generated by authentication. Defaults to <code>env[OS_SERVICE_TOKEN]</code>."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml:131(title)
-msgid "Xen boot from ISO"
+#: ./doc/common/section_cli_keystone_credentials.xml:52(title)
+msgid "To configure the keystone client with a user name and password"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml:132(para)
-msgid "XenServer, through the XenAPI integration with OpenStack, provides a feature to boot instances from an ISO file. To activate the Boot From ISO feature, you must configure the SR elements on XenServer host, as follows:"
+#: ./doc/common/section_cli_keystone_credentials.xml:55(para)
+msgid "Export the administrator user name to the <varname>OS_USERNAME</varname> environment variable:"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml:139(para)
-msgid "Create an ISO-typed SR, such as an NFS ISO library, for instance. For this, using XenCenter is a simple method. You must export an NFS volume from a remote NFS server. Make sure it is exported in read-write mode."
+#: ./doc/common/section_cli_keystone_credentials.xml:61(para)
+msgid "Export the administrator password to the <varname>OS_PASSWORD</varname> environment variable:"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml:146(para)
-msgid "On the compute host, find and record the uuid of this ISO SR:"
+#: ./doc/common/section_cli_keystone_credentials.xml:67(para)
+msgid "Export the tenant name to the <varname>OS_TENANT_NAME</varname> environment variable:"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml:151(para)
-msgid "Locate the uuid of the NFS ISO library:"
+#: ./doc/common/section_cli_keystone_credentials.xml:73(para)
+msgid "Export the URL of the keystone auth server, for example <link href=\"http://localhost:5000/v2.0'\">http://localhost:5000/v2.0'</link>, to the <varname>OS_AUTH_URL</varname> environment variable:"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml:155(para)
-msgid "Set the uuid and configuration. Even if an NFS mount point is not local, you must specify <literal>local-storage-iso</literal>."
+#: ./doc/common/section_cli_keystone_credentials.xml:84(para)
+msgid "<literal>--os-username <replaceable>OS_USERNAME</replaceable></literal>. Name used for authentication with the Identity Service. Defaults to <code>env[OS_USERNAME]</code>."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml:161(para)
-msgid "Make sure the host-uuid from <literal>xe pbd-list</literal> equals the uuid of the host you found previously:"
+#: ./doc/common/section_cli_keystone_credentials.xml:92(para)
+msgid "<literal>--os-password <replaceable>OS_PASSWORD</replaceable></literal>. Password used for authentication with the Identity Service. Defaults to <code>env[OS_PASSWORD]</code>."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml:167(para)
-msgid "You can now add images through the OpenStack Image Service with <literal>disk-format=iso</literal>, and boot them in OpenStack Compute:"
+#: ./doc/common/section_cli_keystone_credentials.xml:100(para)
+msgid "<literal>--os-tenant_name <replaceable>OS_TENANT_NAME</replaceable></literal>. Tenant for which to request authentication. Defaults to <code>env[OS_TENANT_NAME]</code>."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_credentials.xml:108(para)
+msgid "<literal>--os-auth_url <replaceable>OS_AUTH_URL</replaceable></literal>. The Identity Service endpoint to use for authentication. Defaults to <code>env[OS_AUTH_URL]</code>."
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_compute-configure-vnc.xml:63(None)
+msgid "@@image: '../common/figures/novnc/SCH_5009_V00_NUAC-VNC_OpenStack.png'; md5=182dc38019a220c851e1c94aa50f4565"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:6(title)
+msgid "VNC console proxy"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:7(para)
+msgid "The VNC proxy is an OpenStack component that enables compute service users to access their instances through VNC clients."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:10(para)
+msgid "The VNC console connection works as follows:"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:13(para)
+msgid "A user connects to the API and gets an <literal>access_url</literal> such as, <literal>http://<replaceable>ip:port</replaceable>/?token=xyz</literal>."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:19(para)
+msgid "The user pastes the URL in a browser or uses it as a client parameter."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:23(para)
+msgid "The browser or client connects to the proxy."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:26(para)
+msgid "The proxy talks to <systemitem class=\"service\">nova-consoleauth</systemitem> to authorize the token for the user, and maps the token to the <emphasis>private</emphasis> host and port of the VNC server for an instance."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:31(para)
+msgid "The compute host specifies the address that the proxy should use to connect through the <filename>nova.conf</filename> file option, <option>vncserver_proxyclient_address</option>. In this way, the VNC proxy works as a bridge between the public network and private host network."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:39(para)
+msgid "The proxy initiates the connection to VNC server and continues to proxy until the session ends."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:43(para)
+msgid "The proxy also tunnels the VNC protocol over WebSockets so that the <systemitem>noVNC</systemitem> client can talk to VNC servers. In general, the VNC proxy:"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:48(para)
+msgid "Bridges between the public network where the clients live and the private network where VNC servers live."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:52(para)
+msgid "Mediates token authentication."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:55(para)
+msgid "Transparently deals with hypervisor-specific connection details to provide a uniform client experience."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:58(title)
+msgid "noVNC process"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:71(title)
+msgid "About nova-consoleauth"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:73(para)
+msgid "Both client proxies leverage a shared service to manage token authentication called <systemitem class=\"service\">nova-consoleauth</systemitem>. This service must be running for either proxy to work. Many proxies of either type can be run against a single <systemitem class=\"service\">nova-consoleauth</systemitem> service in a cluster configuration."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:80(para)
+msgid "Do not confuse the <systemitem class=\"service\">nova-consoleauth</systemitem> shared service with <literal>nova-console</literal>, which is a XenAPI-specific service that most recent VNC proxy architectures do not use."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:87(title)
+msgid "Typical deployment"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:88(para)
+msgid "A typical deployment has the following components:"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:91(para)
+msgid "A <systemitem class=\"service\">nova-consoleauth</systemitem> process. Typically runs on the controller host."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:96(para)
+msgid "One or more <systemitem class=\"service\">nova-novncproxy</systemitem> services. Supports browser-based noVNC clients. For simple deployments, this service typically runs on the same machine as <systemitem class=\"service\">nova-api</systemitem> because it operates as a proxy between the public network and the private compute host network."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:105(para)
+msgid "One or more <literal>nova-xvpvncproxy</literal> services. Supports the special Java client discussed here. For simple deployments, this service typically runs on the same machine as <systemitem class=\"service\">nova-api</systemitem> because it acts as a proxy between the public network and the private compute host network."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:114(para)
+msgid "One or more compute hosts. These compute hosts must have correctly configured options, as follows."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:120(title)
+msgid "VNC configuration options"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:121(para)
+msgid "To customize the VNC console, use the following configuration options:"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:124(para)
+msgid "To support <link href=\"http://docs.openstack.org/trunk/config-reference/content/configuring-openstack-compute-basics.html#section_configuring-compute-migrations\">live migration</link>, you cannot specify a specific IP address for <literal>vncserver_listen</literal>, because that IP address does not exist on the destination host."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:134(para)
+msgid "The <literal>vncserver_proxyclient_address</literal> defaults to <literal>127.0.0.1</literal>, which is the address of the compute host that Compute instructs proxies to use when connecting to instance servers."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:139(para)
+msgid "For all-in-one XenServer domU deployments, set this to 169.254.0.1."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:140(para)
+msgid "For multi-host XenServer domU deployments, set to a dom0 management IP on the same network as the proxies."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:142(para)
+msgid "For multi-host libvirt deployments, set to a host management IP on the same network as the proxies."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:150(title)
+msgid "nova-novncproxy (noVNC)"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:152(para)
+msgid "You must install the <package>noVNC</package> package, which contains the <systemitem class=\"service\">nova-novncproxy</systemitem> service. As root, run the following command:"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:156(para)
+msgid "The service starts automatically on installation."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:157(para)
+msgid "To restart the service, run:"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:159(para)
+msgid "The configuration option parameter should point to your <filename>nova.conf</filename> file, which includes the message queue server address and credentials."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:162(para)
+msgid "By default, <systemitem class=\"service\">nova-novncproxy</systemitem> binds on <literal>0.0.0.0:6080</literal>."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:165(para)
+msgid "To connect the service to your Compute deployment, add the following configuration options to your <filename>nova.conf</filename> file:"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:169(para)
+msgid "<literal>vncserver_listen</literal>=<replaceable>0.0.0.0</replaceable>"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:172(para)
+msgid "Specifies the address on which the VNC service should bind. Make sure it is assigned one of the compute node interfaces. This address is the one used by your domain file."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:178(para)
+msgid "To use live migration, use the <replaceable>0.0.0.0</replaceable> address."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:183(para)
+msgid "<literal>vncserver_proxyclient_address</literal>=<replaceable>127.0.0.1</replaceable>"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:186(para)
+msgid "The address of the compute host that Compute instructs proxies to use when connecting to instance <literal>vncservers</literal>."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:193(title)
+msgid "Frequently asked questions about VNC access to virtual machines"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:199(literal)
+msgid "nova-xvpvncproxy"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:200(systemitem)
+msgid "nova-novncproxy"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:198(emphasis)
+msgid "Q: What is the difference between <placeholder-1/> and <placeholder-2/>?"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:202(para)
+msgid "A: <literal>nova-xvpvncproxy</literal>, which ships with OpenStack Compute, is a proxy that supports a simple Java client. <systemitem class=\"service\">nova-novncproxy</systemitem> uses noVNC to provide VNC support through a web browser."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:208(emphasis)
+msgid "Q: I want VNC support in the OpenStack dashboard. What services do I need?"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:210(para)
+msgid "A: You need <systemitem class=\"service\">nova-novncproxy</systemitem>, <systemitem class=\"service\">nova-consoleauth</systemitem>, and correctly configured compute hosts."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:216(emphasis)
+msgid "Q: When I use <placeholder-1/> or click on the VNC tab of the OpenStack dashboard, it hangs. Why?"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:218(para)
+msgid "A: Make sure you are running <systemitem class=\"service\">nova-consoleauth</systemitem> (in addition to <systemitem class=\"service\">nova-novncproxy</systemitem>). The proxies rely on <systemitem class=\"service\">nova-consoleauth</systemitem> to validate tokens, and waits for a reply from them until a timeout is reached."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:227(emphasis)
+msgid "Q: My VNC proxy worked fine during my all-in-one test, but now it doesn't work on multi host. Why?"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:230(para)
+msgid "A: The default options work for an all-in-one install, but changes must be made on your compute hosts once you start to build a cluster. As an example, suppose you have two servers:"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:236(para)
+msgid "Your <systemitem class=\"service\">nova-compute</systemitem> configuration file must set the following values:"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:248(para)
+msgid "<literal>novncproxy_base_url</literal> and <literal>xvpvncproxy_base_url</literal> use a public IP; this is the URL that is ultimately returned to clients, which generally do not have access to your private network. Your PROXYSERVER must be able to reach <literal>vncserver_proxyclient_address</literal>, because that is the address over which the VNC connection is proxied."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:260(emphasis)
+msgid "Q: My noVNC does not work with recent versions of web browsers. Why?"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:263(para)
+msgid "A: Make sure you have installed <literal>python-numpy</literal>, which is required to support a newer version of the WebSocket protocol (HyBi-07+)."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:270(emphasis)
+msgid "Q: How do I adjust the dimensions of the VNC window image in the OpenStack dashboard?"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:273(para)
+msgid "A: These values are hard-coded in a Django HTML template. To alter them, edit the <filename>_detail_vnc.html</filename> template file. The location of this file varies based on Linux distribution. On Ubuntu 12.04, the file is at <filename>/usr/share/pyshared/horizon/dashboards/nova/instances/templates/instances/_detail_vnc.html</filename>."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml:279(para)
+msgid "Modify the <option>width</option> and <option>height</option> options, as follows:"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:11(title)
+msgid "Image Service command-line client"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:12(para)
+msgid "The <placeholder-1/> client is the command-line interface (CLI) for the OpenStack Image Service API and its extensions. This chapter documents <placeholder-2/> version 0.12.0."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:22(title)
+msgid "glance usage"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:43(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use image-create instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:52(emphasis) ./doc/common/ch_cli_glance_commands.xml:180(emphasis)
+msgid "DEPRECATED!"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:59(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use image-delete instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:67(para) ./doc/common/ch_cli_glance_commands.xml:131(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use image-list instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:75(para) ./doc/common/ch_cli_glance_commands.xml:524(para)
+msgid "Create a new image."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:91(para)
+msgid "Download a specific image."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:99(para) ./doc/common/ch_cli_glance_commands.xml:715(para)
+msgid "List images you can access."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:107(para) ./doc/common/ch_cli_glance_commands.xml:163(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use member-list instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:115(para) ./doc/common/ch_cli_glance_commands.xml:848(para)
+msgid "Describe a specific image."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:123(para) ./doc/common/ch_cli_glance_commands.xml:886(para)
+msgid "Update a specific image."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:139(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use member-create instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:147(para) ./doc/common/ch_cli_glance_commands.xml:1057(para)
+msgid "Share a specific image with a tenant."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:155(para) ./doc/common/ch_cli_glance_commands.xml:1093(para)
+msgid "Remove a shared image from a tenant."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:171(para) ./doc/common/ch_cli_glance_commands.xml:1118(para)
+msgid "Describe sharing permissions by image or tenant."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:187(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use image-show instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:195(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use image-update instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:212(title)
+msgid "glance optional arguments"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:225(para)
+msgid "Defaults to <code>env[GLANCECLIENT_DEBUG]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:233(para)
+msgid "Print more verbose output"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:241(para)
+msgid "Force retrieving the schema used to generate portions of the help text rather than using a cached copy. Ignored with api version 1"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:251(para)
+msgid "Explicitly allow glanceclient to perform \"insecure SSL\" (https) requests. The server's certificate will not be verified against any certificate authorities. This option should be used with caution."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:272(para) ./doc/common/ch_cli_ceilometer_commands.xml:321(para)
+msgid "Path of client key to use in SSL connection. This option is not necessary if your key is prepended to your cert file."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:282(para)
+msgid "Path of CA TLS certificate(s) used to verify the remote server's certificate. Without this option glance looks for the default system CA certificates."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:292(para) ./doc/common/ch_cli_ceilometer_commands.xml:341(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use --os-cacert."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:300(para)
+msgid "Number of seconds to wait for a response"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:308(para)
+msgid "Disable SSL compression when using https."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:316(para)
+msgid "Prevent select actions from requesting user confirmation."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:325(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Only used for deprecated legacy commands."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:333(para) ./doc/common/ch_cli_glance_commands.xml:342(para) ./doc/common/ch_cli_glance_commands.xml:351(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Send a fully-formed endpoint using --os- image-url instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:360(para)
+msgid "Defaults to <code>env[OS_USERNAME]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:368(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use --os-username."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:376(para)
+msgid "Defaults to <code>env[OS_PASSWORD]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:384(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use --os-password."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:392(para)
+msgid "Defaults to <code>env[OS_TENANT_ID]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:400(para)
+msgid "Defaults to <code>env[OS_TENANT_NAME]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:408(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use --os-tenant-name."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:416(para)
+msgid "Defaults to <code>env[OS_AUTH_URL]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:424(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use --os-auth-url."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:432(para)
+msgid "Defaults to <code>env[OS_REGION_NAME]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:440(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use --os-region-name."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:456(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use --os-auth-token."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:464(para)
+msgid "Defaults to <code>env[OS_IMAGE_URL]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:472(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use --os-image-url."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:480(para)
+msgid "Defaults to <code>env[OS_IMAGE_API_VERSION]</code> or 1"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:488(para)
+msgid "Defaults to <code>env[OS_SERVICE_TYPE]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:496(para)
+msgid "Defaults to <code>env[OS_ENDPOINT_TYPE]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:504(para)
+msgid "<emphasis>DEPRECATED!</emphasis> This option is completely ignored."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:512(title)
+msgid "glance image-create command"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:531(para)
+msgid "of image to reserve."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:539(para) ./doc/common/ch_cli_glance_commands.xml:904(para)
+msgid "Name of image."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:547(para)
+msgid "Store to upload image to."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:555(para) ./doc/common/ch_cli_glance_commands.xml:912(para)
+msgid "Disk format of image. Acceptable formats: ami, ari, aki, vhd, vmdk, raw, qcow2, vdi, and iso."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:564(para) ./doc/common/ch_cli_glance_commands.xml:921(para)
+msgid "Container format of image. Acceptable formats: ami, ari, aki, bare, and ovf."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:573(para) ./doc/common/ch_cli_glance_commands.xml:930(para)
+msgid "Tenant who should own image."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:581(para)
+msgid "Size of image data (in bytes). Only used with '-- location' and '--copy_from'."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:590(para) ./doc/common/ch_cli_glance_commands.xml:946(para)
+msgid "Minimum size of disk needed to boot image (in gigabytes)."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:599(para) ./doc/common/ch_cli_glance_commands.xml:955(para)
+msgid "Minimum amount of ram needed to boot image (in megabytes)."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:608(para) ./doc/common/ch_cli_glance_commands.xml:964(para)
+msgid "URL where the data for this image already resides. For example, if the image data is stored in swift, you could specify 'swift://account:key@example.com/container/obj'."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:619(para)
+msgid "Local file that contains disk image to be uploaded during creation. Alternatively, images can be passed to the client via stdin."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:629(para)
+msgid "Hash of image data used Glance can use for verification. Provide a md5 checksum here."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:638(para) ./doc/common/ch_cli_glance_commands.xml:994(para)
+msgid "Similar to '--location' in usage, but this indicates that the Glance server should immediately copy the data and store it in its configured image store."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:648(para) ./doc/common/ch_cli_glance_commands.xml:1004(para)
+msgid "Make image accessible to the public."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:656(para) ./doc/common/ch_cli_glance_commands.xml:1012(para)
+msgid "Prevent image from being deleted."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:664(para) ./doc/common/ch_cli_glance_commands.xml:1020(para)
+msgid "Arbitrary property to associate with image. May be used multiple times."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:673(para) ./doc/common/ch_cli_glance_commands.xml:790(para) ./doc/common/ch_cli_glance_commands.xml:866(para) ./doc/common/ch_cli_glance_commands.xml:1039(para)
+msgid "Print image size in a human-friendly format."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:681(para) ./doc/common/ch_cli_glance_commands.xml:1047(para)
+msgid "Show upload progress bar."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:689(title)
+msgid "glance image-delete command"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:698(para)
+msgid "Name or ID of image(s) to delete."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:706(title)
+msgid "glance image-list command"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:722(para)
+msgid "Filter images to those that have this name."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:730(para)
+msgid "Filter images to those that have this status."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:738(para)
+msgid "Filter images to those that have this container format. Acceptable formats: ami, ari, aki, bare, and ovf."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:748(para)
+msgid "Filter images to those that have this disk format. Acceptable formats: ami, ari, aki, vhd, vmdk, raw, qcow2, vdi, and iso."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:758(para)
+msgid "Filter images to those with a size greater than this."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:766(para)
+msgid "Filter images to those with a size less than this."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:774(para)
+msgid "Filter images by a user-defined image property."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:782(para)
+msgid "Number of images to request in each paginated request."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:798(para)
+msgid "Sort image list by specified field."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:806(para)
+msgid "Sort image list in specified direction."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:814(para)
+msgid "Allows the user to select a listing of public or non public images."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:823(para)
+msgid "Display only images owned by this tenant id. Filtering occurs on the client side so may be inefficient. This option is mainly intended for admin use. Use an empty string ('') to list images with no owner. Note: This option overrides the --is-public argument if present. Note: the v2 API supports more efficient server-side owner based filtering."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:837(para)
+msgid "Allows the admin user to list all images irrespective of the image's owner or is_public value."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:846(title)
+msgid "glance image-show command"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:855(para)
+msgid "Name or ID of image to describe."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:874(title)
+msgid "glance image-update command"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:893(para)
+msgid "Name or ID of image to modify."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:938(para)
+msgid "Size of image data (in bytes)."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:975(para)
+msgid "Local file that contains disk image to be uploaded during update. Alternatively, images can be passed to the client via stdin."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:985(para)
+msgid "Hash of image data used Glance can use for verification."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:1029(para)
+msgid "If this flag is present, delete all image properties not explicitly set in the update request. Otherwise, those properties not referenced are preserved."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:1055(title)
+msgid "glance member-create command"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:1064(para)
+msgid "Image to add member to."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:1072(para)
+msgid "Tenant to add as member"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:1083(para)
+msgid "Allow the specified tenant to share this image."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:1091(title)
+msgid "glance member-delete command"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:1100(para)
+msgid "Image from which to remove member"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:1108(para)
+msgid "Tenant to remove as member"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:1116(title)
+msgid "glance member-list command"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:1125(para)
+msgid "Filter results by an image ID."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml:1133(para)
+msgid "Filter results by a tenant ID."
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml:106(None)
+msgid "@@image: 'figures/launch_instances.png'; md5=8a7e6864bce97f6478db572daf3ef5de"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml:164(None)
+msgid "@@image: 'figures/instances.png'; md5=6b0f5cb3009d447334ff8b5c5b2cd121"
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml:10(para)
+msgid "You can launch an instance directly from one of the available OpenStack images. The OpenStack Image Service provides a pool of images that are accessible to members of different projects. When you launch an instance from an image, OpenStack creates a local copy of the image on the respective compute node where the instance is started."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml:16(para)
+msgid "Alternatively, you can launch an instance from an image that you have copied to a persistent volume."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml:18(para)
+msgid "To launch an instance, specify the following parameters:"
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml:22(para)
+msgid "The <guilabel>instance source</guilabel>, which is an image or snapshot. Alternatively, you can boot from a volume, which is block storage, to which you've copied an image or snapshot."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml:28(para)
+msgid "The <guilabel>image</guilabel> or <guilabel>snapshot</guilabel>, which represents the operating system."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml:33(para)
+msgid "A <guilabel>name</guilabel> for your instance."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml:49(para)
+msgid "A <emphasis role=\"bold\">keypair</emphasis> for your instance, which are SSH credentials that are injected into images when they are launched. For this to work, the image must contain the <literal>cloud-init</literal> package. Create at least one keypair for each project. If you already have generated a keypair with an external tool, you can import it into OpenStack. You can use the keypair for multiple instances that belong to that project."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml:62(para)
+msgid "A <emphasis role=\"bold\">security group</emphasis>, which defines which incoming network traffic is forwarded to instances. Security groups hold a set of firewall policies, known as <emphasis role=\"italic\">security group rules</emphasis>."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml:73(para)
+msgid "If needed, you can assign a <emphasis role=\"bold\">floating (public) IP address</emphasis> to a running instance and attach a block storage device, or volume, for persistent storage."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml:80(title)
+msgid "To launch an instance:"
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml:82(para)
+msgid "Log in to the OpenStack dashboard."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml:85(para)
+msgid "If you are a member of multiple projects, select a project from the drop-down list at the top of the <guilabel>Project</guilabel> tab."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml:90(para)
+msgid "Click the <guilabel>Images &amp; Snapshot</guilabel> category."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml:92(para)
+msgid "The dashboard shows the images that have been uploaded to OpenStack Image Service and are available for this project."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml:100(title)
+msgid "OpenStack dashboard - Launch Instances window"
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml:97(para)
+msgid "Select an image and click <guibutton>Launch</guibutton>. The <guilabel>Launch Image</guilabel> window appears: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml:112(para)
+msgid "Specify the following parameters:"
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml:116(para)
+msgid "Enter an instance name to assign to the virtual machine."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml:120(para)
+msgid "From the <guilabel>Flavor</guilabel> drop-down list, select the size of the virtual machine to launch."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml:125(para)
+msgid "Optionally, select a keypair."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml:126(para)
+msgid "In case an image uses a static root password or a static key set (neither is recommended), you do not need to provide a keypair on starting the instance."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml:132(para)
+msgid "In <guilabel>Instance Count</guilabel>, enter the number of virtual machines to launch from this image."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml:137(para)
+msgid "Assign the instance to the default security group. If you added rules to this group, the instance implements these rules."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml:150(para)
+msgid "Click <guibutton>Launch Instance</guibutton>. The instance is launched on any of the compute nodes in the cloud."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml:155(para)
+msgid "After you have launched an instance, switch to the <guilabel>Instances &amp; Volumes</guilabel> category to view the instance name, its (private or public) IP address, size, status, task, and power state."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml:160(title)
+msgid "OpenStack dashboard - Instances"
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml:168(para)
+msgid "If you did not provide a keypair on starting and have not touched security groups or rules so far, by default the instance can only be accessed from inside the cloud through VNC at this point. Even pinging the instance is not possible."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml:6(title)
+msgid "Integrate Identity with LDAP"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml:7(para)
+msgid "Identity Service supports integration with an existing LDAP directory for authentication and authorization services."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml:11(para)
+msgid "For OpenStack Identity to access an LDAP back end, you must enable the <option>authlogin_nsswitch_use_ldap</option> boolean value for SELinux on the Identity server. To enable and make the option persistent across reboots:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml:18(para)
+msgid "You can integrate Identity with a single LDAP server."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml:21(para)
+msgid "To configure Identity, set options in the <filename>/etc/keystone/keystone.conf</filename> file. Modify these examples as needed."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml:25(title)
+msgid "To integrate Identity with LDAP"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml:27(para)
+msgid "Enable the LDAP driver in the <filename>keystone.conf</filename> file:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml:34(para)
+msgid "Define the destination LDAP server in the <filename>keystone.conf</filename> file:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml:45(para)
+msgid "Create the organizational units (OU) in the LDAP directory, and define their corresponding location in the <filename>keystone.conf</filename> file:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml:58(para)
+msgid "These schema attributes are extensible for compatibility with various schemas. For example, this entry maps to the <systemitem>person</systemitem> attribute in Active Directory:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml:67(para)
+msgid "A read-only implementation is recommended for LDAP integration. These permissions are applied to object types in the <filename>keystone.conf</filename> file:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml:85(para)
+msgid "Restart the Identity service:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml:87(para)
+msgid "During service restart, authentication and authorization are unavailable."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml:92(title)
+msgid "Additional LDAP integration settings"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml:93(para)
+msgid "Set these options in the <filename>keystone.conf</filename> file."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml:98(term)
+msgid "Filters"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml:100(para)
+msgid "Use filters to control the scope of data presented through LDAP."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml:109(term)
+msgid "LDAP Account Status"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml:111(para)
+msgid "Mask account status values for compatibility with various directory services. Superfluous accounts are filtered with <systemitem>user_filter</systemitem>."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml:115(para)
+msgid "For example, you can mask Active Directory account status attributes in the <filename>keystone.conf</filename> file:"
+msgstr ""
+
+#: ./doc/common/app_support.xml:7(title)
+msgid "Community support"
+msgstr ""
+
+#: ./doc/common/app_support.xml:8(para)
+msgid "The following resources are available to help you run and use OpenStack. The OpenStack community constantly improves and adds to the main features of OpenStack, but if you have any questions, do not hesitate to ask. Use the following resources to get OpenStack support, and troubleshoot your installations."
+msgstr ""
+
+#: ./doc/common/app_support.xml:15(title)
+msgid "Documentation"
+msgstr ""
+
+#: ./doc/common/app_support.xml:16(para)
+msgid "For the available OpenStack documentation, see <link href=\"http://docs.openstack.org\">docs.openstack.org</link>."
+msgstr ""
+
+#: ./doc/common/app_support.xml:19(para) ./doc/common/app_support.xml:393(para) ./doc/common/ch_getstart.xml:208(para)
+msgid "To provide feedback on documentation, join and use the <email>openstack-docs@lists.openstack.org</email> mailing list at <link href=\"http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs\">OpenStack Documentation Mailing List</link>, or <link href=\"https://bugs.launchpad.net/openstack-manuals/+filebug\">report a bug</link>."
+msgstr ""
+
+#: ./doc/common/app_support.xml:26(para)
+msgid "The following books explain how to install an OpenStack cloud and its associated components:"
+msgstr ""
+
+#: ./doc/common/app_support.xml:33(citetitle)
+msgid "Installation Guide for Debian 7.0"
+msgstr ""
+
+#: ./doc/common/app_support.xml:41(citetitle)
+msgid "Installation Guide for openSUSE and SUSE Linux Enterprise Server"
+msgstr ""
+
+#: ./doc/common/app_support.xml:49(citetitle)
+msgid "Installation Guide for Red Hat Enterprise Linux, CentOS, and Fedora"
+msgstr ""
+
+#: ./doc/common/app_support.xml:58(citetitle)
+msgid "Installation Guide for Ubuntu 12.04/14.04 (LTS)"
+msgstr ""
+
+#: ./doc/common/app_support.xml:63(para)
+msgid "The following books explain how to configure and run an OpenStack cloud:"
+msgstr ""
+
+#: ./doc/common/app_support.xml:70(citetitle)
+msgid "Cloud Administrator Guide"
+msgstr ""
+
+#: ./doc/common/app_support.xml:76(citetitle)
+msgid "Configuration Reference"
+msgstr ""
+
+#: ./doc/common/app_support.xml:82(citetitle)
+msgid "Operations Guide"
+msgstr ""
+
+#: ./doc/common/app_support.xml:88(citetitle)
+msgid "High Availability Guide"
+msgstr ""
+
+#: ./doc/common/app_support.xml:94(citetitle)
+msgid "Security Guide"
+msgstr ""
+
+#: ./doc/common/app_support.xml:100(citetitle)
+msgid "Virtual Machine Image Guide"
+msgstr ""
+
+#: ./doc/common/app_support.xml:104(para)
+msgid "The following books explain how to use the OpenStack dashboard and command-line clients:"
+msgstr ""
+
+#: ./doc/common/app_support.xml:111(citetitle)
+msgid "API Quick Start"
+msgstr ""
+
+#: ./doc/common/app_support.xml:118(citetitle)
+msgid "End User Guide"
+msgstr ""
+
+#: ./doc/common/app_support.xml:125(citetitle)
+msgid "Admin User Guide"
+msgstr ""
+
+#: ./doc/common/app_support.xml:132(citetitle)
+msgid "Command-Line Interface Reference"
+msgstr ""
+
+#: ./doc/common/app_support.xml:136(para)
+msgid "The following documentation provides reference and guidance information for the OpenStack APIs:"
+msgstr ""
+
+#: ./doc/common/app_support.xml:142(link)
+msgid "OpenStack API Complete Reference (HTML)"
+msgstr ""
+
+#: ./doc/common/app_support.xml:148(link)
+msgid "API Complete Reference (PDF)"
+msgstr ""
+
+#: ./doc/common/app_support.xml:153(citetitle)
+msgid "OpenStack Block Storage Service API v2 Reference"
+msgstr ""
+
+#: ./doc/common/app_support.xml:160(citetitle)
+msgid "OpenStack Compute API v2 and Extensions Reference"
+msgstr ""
+
+#: ./doc/common/app_support.xml:167(citetitle)
+msgid "OpenStack Identity Service API v2.0 Reference"
+msgstr ""
+
+#: ./doc/common/app_support.xml:173(citetitle)
+msgid "OpenStack Image Service API v2 Reference"
+msgstr ""
+
+#: ./doc/common/app_support.xml:179(citetitle)
+msgid "OpenStack Networking API v2.0 Reference"
+msgstr ""
+
+#: ./doc/common/app_support.xml:185(citetitle)
+msgid "OpenStack Object Storage API v1 Reference"
+msgstr ""
+
+#: ./doc/common/app_support.xml:189(para)
+msgid "The <link href=\"http://docs.openstack.org/training-guides/content/\"><citetitle>Training Guides</citetitle></link> offer software training for cloud administration and management."
+msgstr ""
+
+#: ./doc/common/app_support.xml:196(title)
+msgid "ask.openstack.org"
+msgstr ""
+
+#: ./doc/common/app_support.xml:197(para)
+msgid "During the set up or testing of OpenStack, you might have questions about how a specific task is completed or be in a situation where a feature does not work correctly. Use the <link href=\"http://ask.openstack.org\">ask.openstack.org</link> site to ask questions and get answers. When you visit the <link href=\"http://ask.openstack.org\">http://ask.openstack.org</link> site, scan the recently asked questions to see whether your question has already been answered. If not, ask a new question. Be sure to give a clear, concise summary in the title and provide as much detail as possible in the description. Paste in your command output or stack traces, links to screen shots, and any other information which might be useful."
+msgstr ""
+
+#: ./doc/common/app_support.xml:214(title)
+msgid "OpenStack mailing lists"
+msgstr ""
+
+#: ./doc/common/app_support.xml:215(para)
+msgid "A great way to get answers and insights is to post your question or problematic scenario to the OpenStack mailing list. You can learn from and help others who might have similar issues. To subscribe or view the archives, go to <link href=\"http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack\">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</link>. You might be interested in the other mailing lists for specific projects or development, which you can find <link href=\"http://wiki.openstack.org/MailingLists\">on the wiki</link>. A description of all mailing lists is available at <link href=\"http://wiki.openstack.org/MailingLists\">http://wiki.openstack.org/MailingLists</link>."
+msgstr ""
+
+#: ./doc/common/app_support.xml:231(title)
+msgid "The OpenStack wiki"
+msgstr ""
+
+#: ./doc/common/app_support.xml:232(para)
+msgid "The <link href=\"http://wiki.openstack.org/\">OpenStack wiki</link> contains a broad range of topics but some of the information can be difficult to find or is a few pages deep. Fortunately, the wiki search feature enables you to search by title or content. If you search for specific information, such as about networking or nova, you can find a large amount of relevant material. More is being added all the time, so be sure to check back often. You can find the search box in the upper-right corner of any OpenStack wiki page."
+msgstr ""
+
+#: ./doc/common/app_support.xml:243(title)
+msgid "The Launchpad Bugs area"
+msgstr ""
+
+#: ./doc/common/app_support.xml:244(para)
+msgid "The OpenStack community values your set up and testing efforts and wants your feedback. To log a bug, you must sign up for a Launchpad account at <link href=\"https://launchpad.net/+login\">https://launchpad.net/+login</link>. You can view existing bugs and report bugs in the Launchpad Bugs area. Use the search feature to determine whether the bug has already been reported or already been fixed. If it still seems like your bug is unreported, fill out a bug report."
+msgstr ""
+
+#: ./doc/common/app_support.xml:252(para)
+msgid "Some tips:"
+msgstr ""
+
+#: ./doc/common/app_support.xml:255(para)
+msgid "Give a clear, concise summary."
+msgstr ""
+
+#: ./doc/common/app_support.xml:258(para)
+msgid "Provide as much detail as possible in the description. Paste in your command output or stack traces, links to screen shots, and any other information which might be useful."
+msgstr ""
+
+#: ./doc/common/app_support.xml:264(para)
+msgid "Be sure to include the software and package versions that you are using, especially if you are using a development branch, such as, <literal>\"Juno release\" vs git commit bc79c3ecc55929bac585d04a03475b72e06a3208</literal>."
+msgstr ""
+
+#: ./doc/common/app_support.xml:271(para)
+msgid "Any deployment-specific information is helpful, such as whether you are using Ubuntu 14.04 or are performing a multi-node installation."
+msgstr ""
+
+#: ./doc/common/app_support.xml:276(para)
+msgid "The following Launchpad Bugs areas are available:"
+msgstr ""
+
+#: ./doc/common/app_support.xml:282(link)
+msgid "Bugs: OpenStack Block Storage (cinder)"
+msgstr ""
+
+#: ./doc/common/app_support.xml:288(link)
+msgid "Bugs: OpenStack Compute (nova)"
+msgstr ""
+
+#: ./doc/common/app_support.xml:293(link)
+msgid "Bugs: OpenStack Dashboard (horizon)"
+msgstr ""
+
+#: ./doc/common/app_support.xml:299(link)
+msgid "Bugs: OpenStack Identity (keystone)"
+msgstr ""
+
+#: ./doc/common/app_support.xml:305(link)
+msgid "Bugs: OpenStack Image Service (glance)"
+msgstr ""
+
+#: ./doc/common/app_support.xml:311(link)
+msgid "Bugs: OpenStack Networking (neutron)"
+msgstr ""
+
+#: ./doc/common/app_support.xml:317(link)
+msgid "Bugs: OpenStack Object Storage (swift)"
+msgstr ""
+
+#: ./doc/common/app_support.xml:324(link)
+msgid "Bugs: Bare Metal (ironic)"
+msgstr ""
+
+#: ./doc/common/app_support.xml:329(link)
+msgid "Bugs: Data Processing Service (sahara)"
+msgstr ""
+
+#: ./doc/common/app_support.xml:335(link)
+msgid "Bugs: Database Service (trove)"
+msgstr ""
+
+#: ./doc/common/app_support.xml:340(link)
+msgid "Bugs: Orchestration (heat)"
+msgstr ""
+
+#: ./doc/common/app_support.xml:345(link)
+msgid "Bugs: Telemetry (ceilometer)"
+msgstr ""
+
+#: ./doc/common/app_support.xml:350(link)
+msgid "Bugs: Queue Service (marconi)"
+msgstr ""
+
+#: ./doc/common/app_support.xml:356(link)
+msgid "Bugs: OpenStack API Documentation (developer.openstack.org)"
+msgstr ""
+
+#: ./doc/common/app_support.xml:362(link)
+msgid "Bugs: OpenStack Documentation (docs.openstack.org)"
+msgstr ""
+
+#: ./doc/common/app_support.xml:368(title)
+msgid "The OpenStack IRC channel"
+msgstr ""
+
+#: ./doc/common/app_support.xml:369(para)
+msgid "The OpenStack community lives in the #openstack IRC channel on the Freenode network. You can hang out, ask questions, or get immediate feedback for urgent and pressing issues. To install an IRC client or use a browser-based client, go to <link href=\"http://webchat.freenode.net\">http://webchat.freenode.net/</link>. You can also use Colloquy (Mac OS X, <link href=\"http://colloquy.info/\">http://colloquy.info/</link>), mIRC (Windows, <link href=\"http://www.mirc.com/\">http://www.mirc.com/</link>), or XChat (Linux). When you are in the IRC channel and want to share code or command output, the generally accepted method is to use a Paste Bin. The OpenStack project has one at <link href=\"http://paste.openstack.org\">http://paste.openstack.org</link>. Just paste your longer amounts of text or logs in the web form and you get a URL that you can paste into the channel. The OpenStack IRC channel is <literal>#openstack</literal> on <literal>irc.freenode.net</literal>. You can find a list of all OpenStack IRC channels at <link href=\"https://wiki.openstack.org/wiki/IRC\">https://wiki.openstack.org/wiki/IRC</link>."
+msgstr ""
+
+#: ./doc/common/app_support.xml:392(title)
+msgid "Documentation feedback"
+msgstr ""
+
+#: ./doc/common/app_support.xml:399(title)
+msgid "OpenStack distribution packages"
+msgstr ""
+
+#: ./doc/common/app_support.xml:400(para)
+msgid "The following Linux distributions provide community-supported packages for OpenStack:"
+msgstr ""
+
+#: ./doc/common/app_support.xml:404(emphasis)
+msgid "Debian:"
+msgstr ""
+
+#: ./doc/common/app_support.xml:407(link)
+msgid "http://wiki.debian.org/OpenStack"
+msgstr ""
+
+#: ./doc/common/app_support.xml:410(emphasis)
+msgid "CentOS, Fedora, and Red Hat Enterprise Linux:"
+msgstr ""
+
+#: ./doc/common/app_support.xml:413(link)
+msgid "http://openstack.redhat.com/"
+msgstr ""
+
+#: ./doc/common/app_support.xml:416(emphasis)
+msgid "openSUSE and SUSE Linux Enterprise Server:"
+msgstr ""
+
+#: ./doc/common/app_support.xml:420(link)
+msgid "http://en.opensuse.org/Portal:OpenStack"
+msgstr ""
+
+#: ./doc/common/app_support.xml:423(emphasis)
+msgid "Ubuntu:"
+msgstr ""
+
+#: ./doc/common/app_support.xml:426(link)
+msgid "https://wiki.ubuntu.com/ServerTeam/CloudArchive"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml:6(title)
+msgid "Troubleshoot Object Storage"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml:7(para)
+msgid "For Object Storage, everything is logged in <filename>/var/log/syslog</filename> (or messages on some distros). Several settings enable further customization of logging, such as <literal>log_name</literal>, <literal>log_facility</literal>, and <literal>log_level</literal>, within the object server configuration files."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml:11(title)
+msgid "Drive failure"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml:12(para)
+msgid "In the event that a drive has failed, the first step is to make sure the drive is unmounted. This will make it easier for Object Storage to work around the failure until it has been resolved. If the drive is going to be replaced immediately, then it is just best to replace the drive, format it, remount it, and let replication fill it up."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml:16(para)
+msgid "If the drive can’t be replaced immediately, then it is best to leave it unmounted, and remove the drive from the ring. This will allow all the replicas that were on that drive to be replicated elsewhere until the drive is replaced. Once the drive is replaced, it can be re-added to the ring."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml:20(para)
+msgid "You can look at error messages in <filename>/var/log/kern.log</filename> for hints of drive failure."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml:23(title)
+msgid "Server failure"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml:24(para)
+msgid "If a server is having hardware issues, it is a good idea to make sure the Object Storage services are not running. This will allow Object Storage to work around the failure while you troubleshoot."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml:27(para)
+msgid "If the server just needs a reboot, or a small amount of work that should only last a couple of hours, then it is probably best to let Object Storage work around the failure and get the machine fixed and back online. When the machine comes back online, replication will make sure that anything that is missing during the downtime will get updated."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml:32(para)
+msgid "If the server has more serious issues, then it is probably best to remove all of the server’s devices from the ring. Once the server has been repaired and is back online, the server’s devices can be added back into the ring. It is important that the devices are reformatted before putting them back into the ring as it is likely to be responsible for a different set of partitions than before."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml:40(title)
+msgid "Detect failed drives"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml:41(para)
+msgid "It has been our experience that when a drive is about to fail, error messages will spew into /var/log/kern.log. There is a script called swift-drive-audit that can be run via cron to watch for bad drives. If errors are detected, it will unmount the bad drive, so that Object Storage can work around it. The script takes a configuration file with the following settings:"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml:47(para)
+msgid "This script has only been tested on Ubuntu 10.04, so if you are using a different distro or OS, some care should be taken before using in production."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml:52(title)
+msgid "Emergency recovery of ring builder files"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml:53(para)
+msgid "You should always keep a backup of swift ring builder files. However, if an emergency occurs, this procedure may assist in returning your cluster to an operational state."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml:56(para)
+msgid "Using existing swift tools, there is no way to recover a builder file from a <filename>ring.gz</filename> file. However, if you have a knowledge of Python, it is possible to construct a builder file that is pretty close to the one you have lost. The following is what you will need to do."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml:61(para)
+msgid "This procedure is a last-resort for emergency circumstances. It requires knowledge of the swift python code and may not succeed."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml:64(para)
+msgid "First, load the ring and a new ringbuilder object in a Python REPL:"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml:67(para)
+msgid "Now, start copying the data we have in the ring into the builder."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml:84(para)
+msgid "This is the extent of the recoverable fields. For <literal>min_part_hours</literal> you'll either have to remember what the value you used was, or just make up a new one."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml:89(para)
+msgid "Try some validation: if this doesn't raise an exception, you may feel some hope. Not too much, though."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml:92(para)
+msgid "Save the builder."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml:96(para)
+msgid "You should now have a file called 'account.builder' in the current working directory. Next, run <literal>swift-ring-builder account.builder write_ring</literal> and compare the new account.ring.gz to the account.ring.gz that you started from. They probably won't be byte-for-byte identical, but if you load them up in a REPL and their <literal>_replica2part2dev_id</literal> and <literal>devs</literal> attributes are the same (or nearly so), then you're in good shape."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml:103(para)
+msgid "Next, repeat the procedure for <filename>container.ring.gz</filename> and <filename>object.ring.gz</filename>, and you might get usable builder files."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-account-reaper.xml:7(title)
+msgid "Account reaper"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-account-reaper.xml:8(para)
+msgid "In the background, the account reaper removes data from the deleted accounts."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-account-reaper.xml:9(para)
+msgid "A reseller marks an account for deletion by issuing a <code>DELETE</code> request on the account’s storage URL. This action sets the <code>status</code> column of the account_stat table in the account database and replicas to <code>DELETED</code>, marking the account's data for deletion."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-account-reaper.xml:17(para)
+msgid "It's on the developers' to-do list to write a utility that performs this task, preferably through a ReST call."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-account-reaper.xml:12(para)
+msgid "Typically, a specific retention time or undelete are not provided. However, you can set a <code>delay_reaping</code> value in the <code>[account-reaper]</code> section of the account-server.conf to delay the actual deletion of data. At this time, to undelete you have to update the account database replicas directly, setting the status column to an empty string and updating the put_timestamp to be greater than the delete_timestamp. <placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-account-reaper.xml:20(para)
+msgid "The account reaper runs on each account server and scans the server occasionally for account databases marked for deletion. It only fires up on the accounts for which the server is the primary node, so that multiple account servers aren’t trying to do it simultaneously. Using multiple servers to delete one account might improve the deletion speed but requires coordination to avoid duplication. Speed really is not a big concern with data deletion, and large accounts aren’t deleted often."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-account-reaper.xml:26(para)
+msgid "Deleting an account is simple. For each account container, all objects are deleted and then the container is deleted. Deletion requests that fail will not stop the overall process but will cause the overall process to fail eventually (for example, if an object delete times out, you will not be able to delete the container or the account). The account reaper keeps trying to delete an account until it is empty, at which point the database reclaim process within the db_replicator will remove the database files."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-account-reaper.xml:32(para)
+msgid "A persistent error state may prevent the deletion of an object or container. If this happens, you will see a message such as <code>“Account &lt;name&gt; has not been reaped since &lt;date&gt;”</code> in the log. You can control when this is logged with the <code>reap_warn_after</code> value in the <code>[account-reaper]</code> section of the account-server.conf file. The default value is 30 days."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:7(title) ./doc/common/section_dashboard_access.xml:304(guilabel)
+msgid "Flavors"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:8(para)
+msgid "Admin users can use the <placeholder-1/> commands to customize and manage flavors. To see the available flavor-related commands, run:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:22(para)
+msgid "Configuration rights can be delegated to additional users by redefining the access controls for <option>compute_extension:flavormanage</option> in <filename>/etc/nova/policy.json</filename> on the <systemitem class=\"server\">nova-api</systemitem> server."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:26(para)
+msgid "To modify an existing flavor in the dashboard, you must delete the flavor and create a modified one with the same name."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:31(para)
+msgid "Flavors define these elements:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:33(caption)
+msgid "Identity Service configuration file sections"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:39(td)
+msgid "Element"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:45(literal)
+msgid "Name"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:47(replaceable)
+msgid "XX"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:47(replaceable)
+msgid "SIZE_NAME"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:46(td)
+msgid "A descriptive name. <placeholder-1/>.<placeholder-2/> is typically not required, though some third party tools may rely on it."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:52(literal)
+msgid "Memory_MB"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:53(td)
+msgid "Virtual machine memory in megabytes."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:56(literal)
+msgid "Disk"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:57(td)
+msgid "Virtual root disk size in gigabytes. This is an ephemeral disk that the base image is copied into. When booting from a persistent volume it is not used. The \"0\" size is a special case which uses the native base image size as the size of the ephemeral root volume."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:65(literal)
+msgid "Ephemeral"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:66(td)
+msgid "Specifies the size of a secondary ephemeral data disk. This is an empty, unformatted disk and exists only for the life of the instance."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:71(literal)
+msgid "Swap"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:72(td)
+msgid "Optional swap space allocation for the instance."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:76(literal)
+msgid "VCPUs"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:77(td)
+msgid "Number of virtual CPUs presented to the instance."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:81(literal)
+msgid "RXTX_Factor"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:82(td)
+msgid "Optional property allows created servers to have a different bandwidth cap than that defined in the network they are attached to. This factor is multiplied by the rxtx_base property of the network. Default value is 1.0. That is, the same as attached network."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:90(literal)
+msgid "Is_Public"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:91(td)
+msgid "Boolean value, whether flavor is available to all users or private to the tenant it was created in. Defaults to True."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:96(literal)
+msgid "extra_specs"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:97(para)
+msgid "Key and value pairs that define on which compute nodes a flavor can run. These pairs must match corresponding pairs on the compute nodes. Use to implement special resources, such as flavors that run on only compute nodes with GPU hardware."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:105(para)
+msgid "Flavor customization can be limited by the hypervisor in use. For example the <systemitem>libvirt</systemitem> driver enables quotas on CPUs available to a VM, disk tuning, bandwidth I/O, watchdog behavior, random number generator device control, and instance VIF traffic control."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:110(term)
+msgid "CPU limits"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:111(para)
+msgid "You can configure the CPU limits with control parameters with the <placeholder-1/> client. For example, to configure the I/O limit, use:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:115(para)
+msgid "There are optional CPU control parameters for weight shares, enforcement intervals for runtime quotas, and a quota for maximum allowed bandwidth:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:121(para)
+msgid "<literal>cpu_shares</literal> specifies the proportional weighted share for the domain. If this element is omitted, the service defaults to the OS provided defaults. There is no unit for the value; it is a relative measure based on the setting of other VMs. For example, a VM configured with value 2048 gets twice as much CPU time as a VM configured with value 1024."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:130(para)
+msgid "<literal>cpu_period</literal> specifies the enforcement interval (unit: microseconds) for QEMU and LXC hypervisors. Within a period, each VCPU of the domain is not allowed to consume more than the quota worth of runtime. The value should be in range <literal>[1000, 1000000]</literal>. A period with value 0 means no value."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:138(para)
+msgid "<literal>cpu_quota</literal> specifies the maximum allowed bandwidth (unit: microseconds). A domain with a negative-value quota indicates that the domain has infinite bandwidth, which means that it is not bandwidth controlled. The value should be in range <literal>[1000, 18446744073709551]</literal> or less than 0. A quota with value 0 means no value. You can use this feature to ensure that all vCPUs run at the same speed. For example:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:147(para)
+msgid "In this example, the instance of <literal>m1.low_cpu</literal> can only consume a maximum of 50% CPU of a physical CPU computing capability."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:155(term)
+msgid "Disk tuning"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:156(para)
+msgid "Using disk I/O quotas, you can set maximum disk write to 10 MB per second for a VM user. For example:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:159(para)
+msgid "The disk I/O options are:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:162(para)
+msgid "disk_read_bytes_sec"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:165(para)
+msgid "disk_read_iops_sec"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:168(para)
+msgid "disk_write_bytes_sec"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:171(para)
+msgid "disk_write_iops_sec"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:174(para)
+msgid "disk_total_bytes_sec"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:177(para)
+msgid "disk_total_iops_sec"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:180(para)
+msgid "The vif I/O options are:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:183(para)
+msgid "vif_inbound_ average"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:186(para)
+msgid "vif_inbound_burst"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:189(para)
+msgid "vif_inbound_peak"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:192(para)
+msgid "vif_outbound_ average"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:195(para)
+msgid "vif_outbound_burst"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:198(para)
+msgid "vif_outbound_peak"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:202(term)
+msgid "Bandwidth I/O"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:203(para)
+msgid "Incoming and outgoing traffic can be shaped independently. The bandwidth element can have at most one inbound and at most one outbound child element. If you leave any of these children element out, no quality of service (QoS) is applied on that traffic direction. So, if you want to shape only the network's incoming traffic, use inbound only (and vice versa). Each element has one mandatory attribute average, which specifies the average bit rate on the interface being shaped."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:209(para)
+msgid "There are also two optional attributes (integer): <option>peak</option>, which specifies maximum rate at which bridge can send data (kilobytes/second), and <option>burst</option>, the amount of bytes that can be burst at peak speed (kilobytes). The rate is shared equally within domains connected to the network."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:214(para)
+msgid "The following example configures a bandwidth limit for instance network traffic:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:219(term)
+msgid "Watchdog behavior"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:220(para)
+msgid "For the <systemitem>libvirt</systemitem> driver, you can enable and set the behavior of a virtual hardware watchdog device for each flavor. Watchdog devices keep an eye on the guest server, and carry out the configured action if the server hangs. The watchdog uses the i6300esb device (emulating a PCI Intel 6300ESB). If <literal>hw_watchdog_action</literal> is not specified, the watchdog is disabled."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:226(para)
+msgid "To set the behavior, use:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:227(replaceable) ./doc/common/section_cli_nova_customize_flavors.xml:257(replaceable) ./doc/common/section_cli_nova_customize_flavors.xml:258(replaceable) ./doc/common/section_cli_nova_customize_flavors.xml:259(replaceable)
+msgid "FLAVOR-NAME"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:227(replaceable)
+msgid "ACTION"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:228(para)
+msgid "Valid <replaceable>ACTION</replaceable> values are:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:231(para)
+msgid "<literal>disabled</literal>(default) The device is not attached."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:234(para)
+msgid "<literal>reset</literal>Forcefully reset the guest."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:238(para)
+msgid "<literal>poweroff</literal>Forcefully power off the guest."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:242(para)
+msgid "<literal>pause</literal>Pause the guest."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:245(para)
+msgid "<literal>none</literal>Only enable the watchdog; do nothing if the server hangs."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:249(para)
+msgid "Watchdog behavior set using a specific image's properties will override behavior set using flavors."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:254(term)
+msgid "Random-number generator"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:255(para)
+msgid "If a random-number generator device has been added to the instance through its image properties, the device can be enabled and configured using:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:258(replaceable)
+msgid "RATE-BYTES"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:259(replaceable)
+msgid "RATE-PERIOD"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:263(para)
+msgid "<replaceable>RATE-BYTES</replaceable>(Integer) Allowed amount of bytes that the guest can read from the host's entropy per period."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:267(para)
+msgid "<replaceable>RATE-PERIOD</replaceable>(Integer) Duration of the read period in seconds."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:273(term)
+msgid "Instance VIF traffic control"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml:274(para)
+msgid "Flavors can also be assigned to particular projects. By default, a flavor is public and available to all projects. Private flavors are only accessible to those on the access list and are invisible to other projects. To create and assign a private flavor to a project, run these commands:"
+msgstr ""
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:6(title)
+msgid "Configure tenant-specific image locations with Object Storage"
+msgstr ""
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:14(para)
+msgid "The tenant who owns the image"
+msgstr ""
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:17(para)
+msgid "Tenants that are defined in <option>swift_store_admin_tenants</option> and that have admin-level accounts"
+msgstr ""
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:8(para)
+msgid "For some deployers, it is not ideal to store all images in one place to enable all tenants and users to access them. You can configure the Image Service to store image data in tenant-specific image locations. Then, only the following tenants can use the Image Service to access the created image:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:23(title)
+msgid "To configure tenant-specific image locations"
+msgstr ""
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:25(para)
+msgid "Configure swift as your <option>default_store</option> in the <filename>glance-api.conf</filename> file."
+msgstr ""
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:33(para)
+msgid "<option>swift_store_multi_tenant</option>. Set to <literal>True</literal> to enable tenant-specific storage locations. Default is <literal>False</literal>."
+msgstr ""
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:39(para)
+msgid "<option>swift_store_admin_tenants</option>. Specify a list of tenant IDs that can grant read and write access to all Object Storage containers that are created by the Image Service."
+msgstr ""
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:30(para)
+msgid "Set these configuration options in the <filename>glance-api.conf</filename> file: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml:48(para)
+msgid "With this configuration, images are stored in an Object Storage service (swift) endpoint that is pulled from the service catalog for the authenticated user."
 msgstr ""
 
 #: ./doc/common/ch_cli_keystone_commands.xml:11(title)
@@ -8021,10 +9579,6 @@ msgstr ""
 msgid "keystone optional arguments"
 msgstr ""
 
-#: ./doc/common/ch_cli_keystone_commands.xml:346(para) ./doc/common/ch_cli_heat_commands.xml:325(para)
-msgid "Shows the client version and exits."
-msgstr ""
-
 #: ./doc/common/ch_cli_keystone_commands.xml:354(para)
 msgid "Set request timeout (in seconds)."
 msgstr ""
@@ -8065,10 +9619,6 @@ msgstr ""
 msgid "Specify an endpoint to use instead of retrieving one from the service catalog (via authentication). Defaults to <code>env[OS_SERVICE_ENDPOINT]</code>."
 msgstr ""
 
-#: ./doc/common/ch_cli_keystone_commands.xml:445(para) ./doc/common/ch_cli_swift_commands.xml:302(para) ./doc/common/ch_cli_trove_commands.xml:558(para)
-msgid "Specify a CA bundle file to use in verifying a TLS (https) server certificate. Defaults to <code>env[OS_CACERT]</code>."
-msgstr ""
-
 #: ./doc/common/ch_cli_keystone_commands.xml:455(para)
 msgid "Explicitly allow keystoneclient to perform \"insecure\" TLS (https) requests. The server's certificate will not be verified against any certificate authorities. This option should be used with caution."
 msgstr ""
@@ -8465,2248 +10015,812 @@ msgstr ""
 msgid "Name or ID of user to update."
 msgstr ""
 
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_getstart_conceptual_arch.xml:16(None)
-msgid "@@image: 'figures/openstack_havana_conceptual_arch.png'; md5=96e1d5492d4c865fc9145710bb294a91"
+#: ./doc/common/section_objectstorage-ringbuilder.xml:6(title)
+msgid "Ring-builder"
 msgstr ""
 
-#: ./doc/common/section_getstart_conceptual_arch.xml:6(title)
-msgid "Conceptual architecture"
+#: ./doc/common/section_objectstorage-ringbuilder.xml:7(para)
+msgid "Use the swift-ring-builder utility to build and manage rings. This utility assigns partitions to devices and writes an optimized Python structure to a gzipped, serialized file on disk for transmission to the servers. The server processes occasionally check the modification time of the file and reload in-memory copies of the ring structure as needed. If you use a slightly older version of the ring, one of the three replicas for a partition subset will be incorrect because of the way the ring-builder manages changes to the ring. You can work around this issue."
 msgstr ""
 
-#: ./doc/common/section_getstart_conceptual_arch.xml:7(para)
-msgid "The following diagram shows the relationships among the OpenStack services:"
+#: ./doc/common/section_objectstorage-ringbuilder.xml:17(para)
+msgid "The ring-builder also keeps its own builder file with the ring information and additional data required to build future rings. It is very important to keep multiple backup copies of these builder files. One option is to copy the builder files out to every server while copying the ring files themselves. Another is to upload the builder files into the cluster itself. If you lose the builder file, you have to create a new ring from scratch. Nearly all partitions would be assigned to different devices and, therefore, nearly all of the stored data would have to be replicated to new locations. So, recovery from a builder file loss is possible, but data would be unreachable for an extended time."
 msgstr ""
 
-#: ./doc/common/section_getstart_conceptual_arch.xml:11(title)
-msgid "OpenStack conceptual architecture"
+#: ./doc/common/section_objectstorage-ringbuilder.xml:30(title)
+msgid "Ring data structure"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_metadata.xml:9(title)
-msgid "Insert metadata during launch"
+#: ./doc/common/section_objectstorage-ringbuilder.xml:31(para)
+msgid "The ring data structure consists of three top level fields: a list of devices in the cluster, a list of lists of device ids indicating partition to device assignments, and an integer indicating the number of bits to shift an MD5 hash to calculate the partition for the hash."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_metadata.xml:10(para)
-msgid "When booting a server, you can also add metadata, so that you can more easily identify it amongst your ever-growing elastic cloud. Use the <literal>--meta</literal> option with a key=value pair, where you can make up the string for both the key and the value. For example, you could add a description and also the creator of the server. <placeholder-1/>"
+#: ./doc/common/section_objectstorage-ringbuilder.xml:38(title)
+msgid "Partition assignment list"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_metadata.xml:18(para)
-msgid "When viewing the server information, you can see the metadata included on the <literal>metadata</literal> line: <placeholder-1/>"
+#: ./doc/common/section_objectstorage-ringbuilder.xml:39(para)
+msgid "This is a list of <literal>array(‘H’)</literal> of devices ids. The outermost list contains an <literal>array(‘H’)</literal> for each replica. Each <literal>array(‘H’)</literal> has a length equal to the partition count for the ring. Each integer in the <literal>array(‘H’)</literal> is an index into the above list of devices. The partition list is known internally to the Ring class as <literal>_replica2part2dev_id</literal>."
 msgstr ""
 
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-arch.xml:23(None)
-msgid "@@image: '../common/figures/objectstorage-arch.png'; md5=90f6c7cf3947d7987eeb55d657cdc927"
+#: ./doc/common/section_objectstorage-ringbuilder.xml:48(para)
+msgid "So, to create a list of device dictionaries assigned to a partition, the Python code would look like: <placeholder-1/>"
 msgstr ""
 
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-arch.xml:60(None)
-msgid "@@image: '../common/figures/objectstorage-nodes.png'; md5=2aa7eb3bddcf6826f33469920dc2a9c3"
+#: ./doc/common/section_objectstorage-ringbuilder.xml:52(para)
+msgid "That code is a little simplistic because it does not account for the removal of duplicate devices. If a ring has more replicas than devices, a partition will have more than one replica on a device."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml:11(title)
-msgid "Cluster architecture"
+#: ./doc/common/section_objectstorage-ringbuilder.xml:56(para)
+msgid "<literal>array(‘H’)</literal> is used for memory conservation as there may be millions of partitions."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml:13(title)
-msgid "Access tier"
+#: ./doc/common/section_objectstorage-ringbuilder.xml:61(title)
+msgid "Replica counts"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml:14(para)
-msgid "Large-scale deployments segment off an access tier, which is considered the Object Storage system's central hub. The access tier fields the incoming API requests from clients and moves data in and out of the system. This tier consists of front-end load balancers, ssl-terminators, and authentication services. It runs the (distributed) brain of the Object Storage system: the proxy server processes."
+#: ./doc/common/section_objectstorage-ringbuilder.xml:62(para)
+msgid "To support the gradual change in replica counts, a ring can have a real number of replicas and is not restricted to an integer number of replicas."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml:20(title)
-msgid "Object Storage architecture"
+#: ./doc/common/section_objectstorage-ringbuilder.xml:65(para)
+msgid "A fractional replica count is for the whole ring and not for individual partitions. It indicates the average number of replicas for each partition. For example, a replica count of 3.2 means that 20 percent of partitions have four replicas and 80 percent have three replicas."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml:27(para)
-msgid "Because access servers are collocated in their own tier, you can scale out read/write access regardless of the storage capacity. For example, if a cluster is on the public Internet, requires SSL termination, and has a high demand for data access, you can provision many access servers. However, if the cluster is on a private network and used primarily for archival purposes, you need fewer access servers."
+#: ./doc/common/section_objectstorage-ringbuilder.xml:70(para)
+msgid "The replica count is adjustable."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml:32(para)
-msgid "Since this is an HTTP addressable storage service, you may incorporate a load balancer into the access tier."
+#: ./doc/common/section_objectstorage-ringbuilder.xml:71(para)
+msgid "Example:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml:34(para)
-msgid "Typically, the tier consists of a collection of 1U servers. These machines use a moderate amount of RAM and are network I/O intensive. Since these systems field each incoming API request, you should provision them with two high-throughput (10GbE) interfaces - one for the incoming \"front-end\" requests and the other for the \"back-end\" access to the object storage nodes to put and fetch data."
+#: ./doc/common/section_objectstorage-ringbuilder.xml:74(para)
+msgid "You must rebalance the replica ring in globally distributed clusters. Operators of these clusters generally want an equal number of replicas and regions. Therefore, when an operator adds or removes a region, the operator adds or removes a replica. Removing unneeded replicas saves on the cost of disks."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml:40(title) ./doc/common/section_objectstorage-arch.xml:69(title)
-msgid "Factors to consider"
+#: ./doc/common/section_objectstorage-ringbuilder.xml:80(para)
+msgid "You can gradually increase the replica count at a rate that does not adversely affect cluster performance."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml:41(para)
-msgid "For most publicly facing deployments as well as private deployments available across a wide-reaching corporate network, you use SSL to encrypt traffic to the client. SSL adds significant processing load to establish sessions between clients, which is why you have to provision more capacity in the access layer. SSL may not be required for private deployments on trusted networks."
+#: ./doc/common/section_objectstorage-ringbuilder.xml:90(para)
+msgid "Changes take effect after the ring is rebalanced. Therefore, if you intend to change from 3 replicas to 3.01 but you accidentally type <literal>2.01</literal>, no data is lost."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml:49(title)
-msgid "Storage nodes"
+#: ./doc/common/section_objectstorage-ringbuilder.xml:95(replaceable)
+msgid "X.builder"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml:50(para)
-msgid "In most configurations, each of the five zones should have an equal amount of storage capacity. Storage nodes use a reasonable amount of memory and CPU. Metadata needs to be readily available to return objects quickly. The object stores run services not only to field incoming requests from the access tier, but to also run replicators, auditors, and reapers. You can provision object stores provisioned with single gigabit or 10 gigabit network interface depending on the expected workload and desired performance."
+#: ./doc/common/section_objectstorage-ringbuilder.xml:94(para)
+msgid "Additionally, <placeholder-1/> can now take a decimal argument for the number of replicas."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml:57(title) ./doc/common/section_storage-concepts.xml:21(td) ./doc/common/section_objectstorage-characteristics.xml:46(title)
-msgid "Object Storage (swift)"
+#: ./doc/common/section_objectstorage-ringbuilder.xml:100(title)
+msgid "Partition shift value"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml:64(para)
-msgid "Currently, a 2TB or 3TB SATA disk delivers good performance for the price. You can use desktop-grade drives if you have responsive remote hands in the datacenter and enterprise-grade drives if you don't."
+#: ./doc/common/section_objectstorage-ringbuilder.xml:101(para)
+msgid "The partition shift value is known internally to the Ring class as <literal>_part_shift</literal>. This value is used to shift an MD5 hash to calculate the partition where the data for that hash should reside. Only the top four bytes of the hash is used in this process. For example, to compute the partition for the <literal>/account/container/object</literal> path, the Python code might look like the following code: <placeholder-1/>"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml:70(para)
-msgid "You should keep in mind the desired I/O performance for single-threaded requests . This system does not use RAID, so a single disk handles each request for an object. Disk performance impacts single-threaded response rates."
+#: ./doc/common/section_objectstorage-ringbuilder.xml:112(para)
+msgid "For a ring generated with part_power P, the partition shift value is <literal>32 - P</literal>."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml:73(para)
-msgid "To achieve apparent higher throughput, the object storage system is designed to handle concurrent uploads/downloads. The network I/O capacity (1GbE, bonded 1GbE pair, or 10GbE) should match your desired concurrent throughput needs for reads and writes."
+#: ./doc/common/section_objectstorage-ringbuilder.xml:116(title)
+msgid "Build the ring"
 msgstr ""
 
-#: ./doc/common/section_dochistory.xml:6(title)
-msgid "Document change history"
+#: ./doc/common/section_objectstorage-ringbuilder.xml:117(para)
+msgid "The ring builder process includes these high-level steps:"
 msgstr ""
 
-#: ./doc/common/section_dochistory.xml:8(para)
-msgid "This version of the guide replaces and obsoletes all previous versions. The following table describes the most recent changes:"
+#: ./doc/common/section_objectstorage-ringbuilder.xml:121(para)
+msgid "The utility calculates the number of partitions to assign to each device based on the weight of the device. For example, for a partition at the power of 20, the ring has 1,048,576 partitions. One thousand devices of equal weight will each want 1,048.576 partitions. The devices are sorted by the number of partitions they desire and kept in order throughout the initialization process."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:10(title)
-msgid "Host aggregates"
+#: ./doc/common/section_objectstorage-ringbuilder.xml:131(para)
+msgid "Each device is also assigned a random tiebreaker value that is used when two devices desire the same number of partitions. This tiebreaker is not stored on disk anywhere, and so two different rings created with the same parameters will have different partition assignments. For repeatable partition assignments, <literal>RingBuilder.rebalance()</literal> takes an optional seed value that seeds the Python pseudo-random number generator."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:11(para)
-msgid "Host aggregates are a mechanism to further partition an availability zone; while availability zones are visible to users, host aggregates are only visible to administrators. Host Aggregates provide a mechanism to allow administrators to assign key-value pairs to groups of machines. Each node can have multiple aggregates, each aggregate can have multiple key-value pairs, and the same key-value pair can be assigned to multiple aggregates. This information can be used in the scheduler to enable advanced scheduling, to set up hypervisor resource pools or to define logical groups for migration."
+#: ./doc/common/section_objectstorage-ringbuilder.xml:145(para)
+msgid "The ring builder assigns each partition replica to the device that requires most partitions at that point while keeping it as far away as possible from other replicas. The ring builder prefers to assign a replica to a device in a region that does not already have a replica. If no such region is available, the ring builder searches for a device in a different zone, or on a different server. If it does not find one, it looks for a device with no replicas. Finally, if all options are exhausted, the ring builder assigns the replica to the device that has the fewest replicas already assigned."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:23(title)
-msgid "Command-line interface"
+#: ./doc/common/section_objectstorage-ringbuilder.xml:159(para)
+msgid "The ring builder assigns multiple replicas to one device only if the ring has fewer devices than it has replicas."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:35(replaceable) ./doc/common/section_cli_nova_host_aggregates.xml:111(replaceable)
-msgid "&lt;name&gt;"
+#: ./doc/common/section_objectstorage-ringbuilder.xml:165(para)
+msgid "When building a new ring from an old ring, the ring builder recalculates the desired number of partitions that each device wants."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:36(replaceable)
-msgid "&lt;availability-zone&gt;"
+#: ./doc/common/section_objectstorage-ringbuilder.xml:174(para)
+msgid "The ring builder unassigns any assigned partitions from any removed devices and adds these partitions to the gathered list."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:38(para)
-msgid "Create a new aggregate named <replaceable>&lt;name&gt;</replaceable> in availability zone <replaceable>&lt;availability-zone&gt;</replaceable>. Returns the ID of the newly created aggregate. Hosts can be made available to multiple availability zones, but administrators should be careful when adding the host to a different host aggregate within the same availability zone and pay attention when using the <placeholder-1/> and <placeholder-2/> commands to avoid user confusion when they boot instances in different availability zones. An error occurs if you cannot add a particular host to an aggregate zone for which it is not intended."
+#: ./doc/common/section_objectstorage-ringbuilder.xml:180(para)
+msgid "The ring builder unassigns any partition replicas that can be spread out for better durability and adds these partitions to the gathered list."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:60(replaceable) ./doc/common/section_cli_nova_host_aggregates.xml:68(replaceable) ./doc/common/section_cli_nova_host_aggregates.xml:76(replaceable) ./doc/common/section_cli_nova_host_aggregates.xml:87(replaceable) ./doc/common/section_cli_nova_host_aggregates.xml:98(replaceable) ./doc/common/section_cli_nova_host_aggregates.xml:110(replaceable)
-msgid "&lt;id&gt;"
+#: ./doc/common/section_objectstorage-ringbuilder.xml:187(para)
+msgid "The ring builder unassigns random partitions from any devices that have more partitions than they need and adds these partitions to the gathered list."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:62(para)
-msgid "Delete an aggregate with id <replaceable>&lt;id&gt;</replaceable>."
+#: ./doc/common/section_objectstorage-ringbuilder.xml:170(para)
+msgid "The ring builder unassigns partitions and gathers these partitions for reassignment, as follows: <placeholder-1/>"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:70(para)
-msgid "Show details of the aggregate with id <replaceable>&lt;id&gt;</replaceable>."
+#: ./doc/common/section_objectstorage-ringbuilder.xml:197(para)
+msgid "The ring builder reassigns the gathered partitions to devices by using a similar method to the one described previously."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:77(replaceable) ./doc/common/section_cli_nova_host_aggregates.xml:88(replaceable)
-msgid "&lt;host&gt;"
+#: ./doc/common/section_objectstorage-ringbuilder.xml:202(para)
+msgid "When the ring builder reassigns a replica to a partition, the ring builder records the time of the reassignment. The ring builder uses this value when it gathers partitions for reassignment so that no partition is moved twice in a configurable amount of time. The RingBuilder class knows this configurable amount of time as <literal>min_part_hours</literal>. The ring builder ignores this restriction for replicas of partitions on removed devices because removal of a device happens on device failure only, and reassignment is the only choice."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:79(para)
-msgid "Add host with name <replaceable>&lt;host&gt;</replaceable> to aggregate with id <replaceable>&lt;id&gt;</replaceable>."
+#: ./doc/common/section_objectstorage-ringbuilder.xml:216(para)
+msgid "Theses steps do not always perfectly rebalance a ring due to the random nature of gathering partitions for reassignment. To help reach a more balanced ring, the rebalance process is repeated until near perfect (less than 1 percent off) or when the balance does not improve by at least 1 percent (indicating we probably cannot get perfect balance due to wildly imbalanced zones or too many partitions recently moved)."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:90(para)
-msgid "Remove the host with name <replaceable>&lt;host&gt;</replaceable> from the aggregate with id <replaceable>&lt;id&gt;</replaceable>."
+#: ./doc/common/section_keystone-ssl-config.xml:7(title)
+msgid "Configure the Identity Service with SSL"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:99(replaceable) ./doc/common/section_cli_nova_host_aggregates.xml:100(replaceable)
-msgid "&lt;key=value&gt;"
+#: ./doc/common/section_keystone-ssl-config.xml:8(para)
+msgid "You can configure the Identity Service to support two-way SSL."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:103(para)
-msgid "Add or update metadata (key-value pairs) associated with the aggregate with id <replaceable>&lt;id&gt;</replaceable>."
+#: ./doc/common/section_keystone-ssl-config.xml:10(para)
+msgid "You must obtain the x509 certificates externally and configure them."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:112(replaceable)
-msgid "&lt;availability_zone&gt;"
+#: ./doc/common/section_keystone-ssl-config.xml:12(para)
+msgid "The Identity Service provides a set of sample certificates in the <filename class=\"directory\">examples/pki/certs</filename> and <filename class=\"directory\">examples/pki/private</filename> directories:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:114(para)
-msgid "Update the name and availability zone (optional) for the aggregate."
+#: ./doc/common/section_keystone-ssl-config.xml:18(title)
+msgid "Certificate types"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:128(para)
-msgid "Put/resume host into/from maintenance."
+#: ./doc/common/section_keystone-ssl-config.xml:20(term)
+msgid "cacert.pem"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:24(para)
-msgid "The <placeholder-1/> command-line tool supports the following aggregate-related commands. <placeholder-2/>"
+#: ./doc/common/section_keystone-ssl-config.xml:22(para)
+msgid "Certificate Authority chain to validate against."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:134(para)
-msgid "Only administrators can access these commands. If you try to use these commands and the user name and tenant that you use to access the Compute service do not have the <literal>admin</literal> role or the appropriate privileges, these errors occur:"
+#: ./doc/common/section_keystone-ssl-config.xml:27(term)
+msgid "ssl_cert.pem"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:146(title)
-msgid "Configure scheduler to support host aggregates"
+#: ./doc/common/section_keystone-ssl-config.xml:29(para)
+msgid "Public certificate for Identity Service server."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:147(para)
-msgid "One common use case for host aggregates is when you want to support scheduling instances to a subset of compute hosts because they have a specific capability. For example, you may want to allow users to request compute hosts that have SSD drives if they need access to faster disk I/O, or access to compute hosts that have GPU cards to take advantage of GPU-accelerated code."
+#: ./doc/common/section_keystone-ssl-config.xml:34(term)
+msgid "middleware.pem"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:154(para)
-msgid "To configure the scheduler to support host aggregates, the <literal>scheduler_default_filters</literal> configuration option must contain the <literal>AggregateInstanceExtraSpecsFilter</literal> in addition to the other filters used by the scheduler. Add the following line to <filename>/etc/nova/nova.conf</filename> on the host that runs the <systemitem class=\"service\">nova-scheduler</systemitem> service to enable host aggregates filtering, as well as the other filters that are typically enabled:<placeholder-1/>"
+#: ./doc/common/section_keystone-ssl-config.xml:36(para)
+msgid "Public and private certificate for Identity Service middleware/client."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:168(title)
-msgid "Example: Specify compute hosts with SSDs"
+#: ./doc/common/section_keystone-ssl-config.xml:41(term)
+msgid "cakey.pem"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:169(para)
-msgid "This example configures the Compute service to enable users to request nodes that have solid-state drives (SSDs). You create a <literal>fast-io</literal> host aggregate in the <literal>nova</literal> availability zone and you add the <literal>ssd=true</literal> key-value pair to the aggregate. Then, you add the <literal>node1</literal>, and <literal>node2</literal> compute nodes to it."
+#: ./doc/common/section_keystone-ssl-config.xml:43(para)
+msgid "Private key for the CA."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:204(para)
-msgid "Use the <placeholder-1/> command to create the <replaceable>ssd.large</replaceable> flavor called with an ID of 6, 8GB of RAM, 80GB root disk, and four vCPUs."
+#: ./doc/common/section_keystone-ssl-config.xml:47(term)
+msgid "ssl_key.pem"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:207(replaceable) ./doc/common/section_cli_nova_host_aggregates.xml:219(replaceable)
-msgid "ssd.large"
+#: ./doc/common/section_keystone-ssl-config.xml:49(para)
+msgid "Private key for the Identity Service server."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:207(replaceable)
-msgid "6"
+#: ./doc/common/section_keystone-ssl-config.xml:55(para)
+msgid "You can choose names for these certificates. You can also combine the public/private keys in the same file, if you wish. These certificates are provided as an example."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:207(replaceable)
-msgid "8192"
+#: ./doc/common/section_keystone-ssl-config.xml:61(title)
+msgid "SSL configuration"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:207(replaceable)
-msgid "80"
+#: ./doc/common/section_keystone-ssl-config.xml:62(para)
+msgid "To enable SSL with client authentication, modify the <literal>[ssl]</literal> section in the <filename>etc/keystone.conf</filename> file. The following SSL configuration example uses the included sample certificates:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:207(replaceable)
-msgid "4"
+#: ./doc/common/section_keystone-ssl-config.xml:74(title)
+msgid "Options"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:213(para)
-msgid "Once the flavor is created, specify one or more key-value pairs that match the key-value pairs on the host aggregates. In this case, that is the <replaceable>ssd=true</replaceable> key-value pair. Setting a key-value pair on a flavor is done using the <placeholder-1/> command."
+#: ./doc/common/section_keystone-ssl-config.xml:76(para)
+msgid "<literal>enable</literal>. True enables SSL. Default is False."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:219(replaceable)
-msgid "ssd=true"
+#: ./doc/common/section_keystone-ssl-config.xml:80(para)
+msgid "<literal>certfile</literal>. Path to the Identity Service public certificate file."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:220(para)
-msgid "Once it is set, you should see the <literal>extra_specs</literal> property of the <literal>ssd.large</literal> flavor populated with a key of <literal>ssd</literal> and a corresponding value of <literal>true</literal>."
+#: ./doc/common/section_keystone-ssl-config.xml:84(para)
+msgid "<literal>keyfile</literal>. Path to the Identity Service private certificate file. If you include the private key in the certfile, you can omit the keyfile."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:241(para)
-msgid "Now, when a user requests an instance with the <literal>ssd.large</literal> flavor, the scheduler only considers hosts with the <literal>ssd=true</literal> key-value pair. In this example, these are <literal>node1</literal> and <literal>node2</literal>."
+#: ./doc/common/section_keystone-ssl-config.xml:90(para)
+msgid "<literal>ca_certs</literal>. Path to the CA trust chain."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:249(title)
-msgid "XenServer hypervisor pools to support live migration"
+#: ./doc/common/section_keystone-ssl-config.xml:94(para)
+msgid "<literal>cert_required</literal>. Requires client certificate. Default is False."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml:251(para)
-msgid "When using the XenAPI-based hypervisor, the Compute service uses host aggregates to manage XenServer Resource pools, which are used in supporting live migration."
+#: ./doc/common/section_cli_keystone_apiv3.xml:5(title)
+msgid "Use Identity Service API v3 instead of API v2.0"
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml:6(title)
-msgid "Migrate the Identity Service database"
+#: ./doc/common/section_cli_keystone_apiv3.xml:6(para)
+msgid "Use the following parameters in combination on any keystone command to specify which version of the API to use:"
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml:7(para)
-msgid "Between revisions of the Identity Service project, you might need to complete SQL migrations. The Identity Service project uses SQLAlchemy-migrate (see <link href=\"http://code.google.com/p/sqlalchemy-migrate/\">http://code.google.com/p/sqlalchemy-migrate/</link>) to migrate the SQL database between revisions. For core components, the source code stores migrations in a central repository under a <filename>keystone/common/sql/migrate_repo</filename> directory."
+#: ./doc/common/section_cli_keystone_apiv3.xml:11(para)
+msgid "<parameter>--os-endpoint</parameter>. The endpoint to use instead of the one in the service catalog. Defaults to <code>env[OS_SERVICE_ENDPOINT]</code>."
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml:17(para)
-msgid "Extensions to the Identity Service might also require SQL migrations. The directory <filename>keystone/contrib/example</filename> in the keystone repository contains a sample extension migration."
+#: ./doc/common/section_cli_keystone_apiv3.xml:15(para)
+msgid "The <literal>keystone</literal> client detects the version of the API from this parameter."
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml:23(title)
-msgid "To set up a migration for an extension"
+#: ./doc/common/section_cli_keystone_apiv3.xml:19(para)
+msgid "<parameter>--os-auth_url</parameter>. The Identity Service endpoint to use for authentication. Defaults to <code>env[OS_AUTH_URL]</code>."
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml:25(para)
-msgid "Create a directory structure where <literal>my_extension</literal> is the name of the extension, as follows: <filename>keystone/contrib/my_extension/migrate_repo/versions/</filename>."
+#: ./doc/common/section_cli_keystone_apiv3.xml:25(para)
+msgid "<parameter>--os-identity-api-version</parameter>. The Identity Service API version. Defaults to <code>env[OS_IDENTITY_API_VERSION]</code> or <literal>2.0</literal>."
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml:31(para)
-msgid "Create empty <filename>__init__.py</filename> files in the <filename>migrate_repo</filename> and <filename>versions</filename> subdirectories."
+#: ./doc/common/section_cli_keystone_apiv3.xml:31(para)
+msgid "For example, use the following parameters to use API v3:"
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml:37(para)
-msgid "Create a <filename>migrate.cfg</filename> configuration file in the <filename>migrate_repo</filename> subdirectory, which conforms to a key/value <filename>.ini</filename> file format."
+#: ./doc/common/section_cli_keystone_apiv3.xml:33(parameter) ./doc/common/section_cli_keystone_apiv3.xml:35(parameter)
+msgid "--os-auth_url"
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml:41(para)
-msgid "An example configuration file:"
+#: ./doc/common/section_cli_keystone_apiv3.xml:33(parameter) ./doc/common/section_cli_keystone_apiv3.xml:35(parameter)
+msgid "--os-identity-api-version"
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml:49(title)
-msgid "To test a migration for a specific extension"
+#: ./doc/common/section_cli_keystone_apiv3.xml:34(para)
+msgid "Use the following parameters to use API v2.0:"
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml:50(para)
-msgid "You can use the <placeholder-1/> command with the <parameter>--extension</parameter> parameter for both the <placeholder-2/> and <placeholder-3/> commands. Ensure that the required configuration files exist before completing these steps."
+#: ./doc/common/section_conventions.xml:8(title)
+msgid "Conventions"
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml:57(para)
-msgid "Test your migrations with an <literal>example</literal> extension:"
+#: ./doc/common/section_conventions.xml:9(para)
+msgid "The OpenStack documentation uses several typesetting conventions."
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml:62(para)
-msgid "Migrate to version 1:"
+#: ./doc/common/section_conventions.xml:13(title)
+msgid "Notices"
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml:66(para)
-msgid "Migrate back to version 0:"
+#: ./doc/common/section_conventions.xml:14(para)
+msgid "Notices take three forms:"
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml:70(para)
-msgid "Check the version:"
+#: ./doc/common/section_conventions.xml:16(para)
+msgid "The information in a note is usually in the form of a handy tip or reminder."
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml:5(title)
-msgid "Database service overview"
+#: ./doc/common/section_conventions.xml:20(para)
+msgid "The information in an important notice is something you must be aware of before proceeding."
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml:6(para)
-msgid "The Database service provides scalable and reliable cloud provisioning functionality for both relational and non-relational database engines. Users can quickly and easily utilize database features without the burden of handling complex administrative tasks. Cloud users and database administrators can provision and manage multiple database instances as needed."
+#: ./doc/common/section_conventions.xml:24(para)
+msgid "The information in warnings is critical. Warnings provide additional information about risk of data loss or security issues."
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml:7(para)
-msgid "The Database service provides resource isolation at high performance levels, and automates complex administrative tasks such as deployment, configuration, patching, backups, restores, and monitoring."
+#: ./doc/common/section_conventions.xml:31(title)
+msgid "Command prompts"
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml:9(title)
-msgid "Process flow example."
+#: ./doc/common/section_conventions.xml:32(para)
+msgid "Commands prefixed with the <literal>#</literal> prompt are to be executed by the <literal>root</literal> user. These examples can also be executed by using the <placeholder-1/> command, if available."
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml:9(para)
-msgid "Here is a high-level process flow example for using Database services:"
+#: ./doc/common/section_conventions.xml:36(para)
+msgid "Commands prefixed with the <literal>$</literal> prompt can be executed by any user, including <literal>root</literal>."
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml:12(para)
-msgid "Administrator sets up infrastructure:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml:11(title)
+msgid "Telemetry command-line client"
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml:15(para)
-msgid "OpenStack administrator installs the Database service."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:12(para)
+msgid "The <placeholder-1/> client is the command-line interface (CLI) for the Telemetry API and its extensions. This chapter documents <placeholder-2/> version 1.0.10."
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml:18(para)
-msgid "She creates one image for each type of database the administrator wants to have (one for MySQL, one for MongoDB, and so on)."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:22(title)
+msgid "ceilometer usage"
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml:23(para)
-msgid "OpenStack administrator updates the datastore to use the new images, using the <placeholder-1/> command."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:42(para) ./doc/common/ch_cli_ceilometer_commands.xml:459(para)
+msgid "Create a new alarm based on state of other alarms."
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml:30(para)
-msgid "End user uses database service:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml:50(para) ./doc/common/ch_cli_ceilometer_commands.xml:601(para)
+msgid "Update an existing alarm based on state of other alarms."
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml:33(para)
-msgid "Now that the basic infrastructure is set up, an end user can create a Trove instance (database) whenever the user wants, using the <placeholder-1/> command."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:59(para)
+msgid "Create a new alarm (Deprecated). Use alarm-threshold- create instead."
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml:41(replaceable)
-msgid "instanceID"
+#: ./doc/common/ch_cli_ceilometer_commands.xml:68(para) ./doc/common/ch_cli_ceilometer_commands.xml:746(para)
+msgid "Delete an alarm."
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml:39(para)
-msgid "The end user gets the IP address of the Trove instance by using the <placeholder-1/> command to get the ID of the instance, and then using the <placeholder-2/> command to get the IP address."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:76(para) ./doc/common/ch_cli_ceilometer_commands.xml:763(para)
+msgid "Display the change history of an alarm."
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml:44(para)
-msgid "The end user can now access the Trove instance using typical database access commands. MySQL example:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml:84(para) ./doc/common/ch_cli_ceilometer_commands.xml:790(para)
+msgid "List the user's alarms."
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml:45(replaceable)
-msgid "trove_ip_address"
+#: ./doc/common/ch_cli_ceilometer_commands.xml:92(para) ./doc/common/ch_cli_ceilometer_commands.xml:809(para)
+msgid "Show an alarm."
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml:51(title)
-msgid "Components:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml:100(para) ./doc/common/ch_cli_ceilometer_commands.xml:826(para)
+msgid "Get the state of an alarm."
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml:51(para)
-msgid "The Database service includes the following components:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml:108(para) ./doc/common/ch_cli_ceilometer_commands.xml:843(para)
+msgid "Set the state of an alarm."
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml:55(para)
-msgid "<code>python-troveclient</code> command-line client. A CLI that communicates with the <code>trove-api</code> component."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:116(para) ./doc/common/ch_cli_ceilometer_commands.xml:884(para)
+msgid "Create a new alarm based on computed statistics."
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml:58(para)
-msgid "<code>trove-api</code> component. Provides an OpenStack-native RESTful API that supports JSON to provision and manage Trove instances."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:124(para) ./doc/common/ch_cli_ceilometer_commands.xml:1074(para)
+msgid "Update an existing alarm based on computed statistics."
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml:62(para)
-msgid "<code>trove-conductor</code> service. Runs on the host, and receives messages from guest instances that want to update information on the host."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:132(para) ./doc/common/ch_cli_ceilometer_commands.xml:1279(para)
+msgid "Update an existing alarm (Deprecated)."
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml:65(para)
-msgid "<code>trove-taskmanager</code> service. Instruments the complex system flows that support provisioning instances, managing the lifecycle of instances, and performing operations on instances."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:140(para) ./doc/common/ch_cli_ceilometer_commands.xml:1468(para)
+msgid "List events."
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml:68(para)
-msgid "<code>trove-guestagent</code> service. Runs within the guest instance. Manages and performs operations on the database itself."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:148(para) ./doc/common/ch_cli_ceilometer_commands.xml:1487(para)
+msgid "Show a particular event."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:11(title)
-msgid "Object Storage command-line client"
+#: ./doc/common/ch_cli_ceilometer_commands.xml:156(para) ./doc/common/ch_cli_ceilometer_commands.xml:1504(para)
+msgid "List event types."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:12(para)
-msgid "The <placeholder-1/> client is the command-line interface (CLI) for the OpenStack Object Storage API and its extensions. This chapter documents <placeholder-2/> version 2.1.0."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:164(para) ./doc/common/ch_cli_ceilometer_commands.xml:1511(para)
+msgid "List the user's meters."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:22(title)
-msgid "swift usage"
+#: ./doc/common/ch_cli_ceilometer_commands.xml:172(para) ./doc/common/ch_cli_ceilometer_commands.xml:1531(para)
+msgid "Query Alarm History."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:41(para) ./doc/common/ch_cli_swift_commands.xml:335(para)
-msgid "Delete a container or objects within a container."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:180(para) ./doc/common/ch_cli_ceilometer_commands.xml:1567(para)
+msgid "Query Alarms."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:49(para) ./doc/common/ch_cli_swift_commands.xml:399(para)
-msgid "Download objects from containers."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:188(para) ./doc/common/ch_cli_ceilometer_commands.xml:1603(para)
+msgid "Query samples."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:57(para) ./doc/common/ch_cli_swift_commands.xml:513(para)
-msgid "Lists the containers for the account or the objects for a container."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:196(para) ./doc/common/ch_cli_ceilometer_commands.xml:1639(para)
+msgid "List the resources."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:66(para)
-msgid "Updates meta information for the account, container, or object; creates containers if not present."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:204(para) ./doc/common/ch_cli_ceilometer_commands.xml:1658(para)
+msgid "Show the resource."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:75(para) ./doc/common/ch_cli_swift_commands.xml:661(para)
-msgid "Displays information for the account, container, or object."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:212(para) ./doc/common/ch_cli_ceilometer_commands.xml:1681(para)
+msgid "Create a sample."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:84(para)
-msgid "Uploads files or directories to the given container."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:220(para) ./doc/common/ch_cli_ceilometer_commands.xml:1764(para)
+msgid "List the samples for a meter."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:92(para)
-msgid "List cluster capabilities."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:228(para) ./doc/common/ch_cli_ceilometer_commands.xml:1800(para)
+msgid "List the statistics for a meter."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:100(title)
-msgid "swift examples"
+#: ./doc/common/ch_cli_ceilometer_commands.xml:236(para) ./doc/common/ch_cli_ceilometer_commands.xml:1853(para)
+msgid "List trait info for an event type."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:110(title)
-msgid "swift optional arguments"
+#: ./doc/common/ch_cli_ceilometer_commands.xml:244(para)
+msgid "List trait all traits with name &lt;trait_name&gt; for Event Type"
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:131(para)
-msgid "Use SERVICENET internal network."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:270(title)
+msgid "ceilometer optional arguments"
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:139(para)
-msgid "Print more info."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:283(para)
+msgid "Defaults to <code>env[CEILOMETERCLIENT_DEBUG]</code>."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:147(para)
-msgid "Show the curl commands and results of all http queries regardless of result status."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:299(para)
+msgid "Explicitly allow ceilometerclient to perform \"insecure\" SSL (https) requests. The server's certificate will not be verified against any certificate authorities. This option should be used with caution."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:156(para)
-msgid "Show the curl commands and results of all http queries which return an error."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:331(para)
+msgid "Path of CA TLS certificate(s) used to verifythe remote server's certificate. Without this option ceilometer looks for the default system CA certificates."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:165(para)
-msgid "Suppress status output."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:349(para)
+msgid "Number of seconds to wait for a response."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:173(para)
-msgid "for obtaining an auth token."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:413(para)
+msgid "Defaults to <code>env[CEILOMETER_URL]</code>."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:181(para)
-msgid "Specify a version for authentication. Defaults to 1.0."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:421(para)
+msgid "Defaults to <code>env[CEILOMETER_API_VERSION]</code> or 2."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:189(para)
-msgid "User name for obtaining an auth token."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:445(title)
+msgid "ceilometer alarm-combination-create command"
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:197(para)
-msgid "Key for obtaining an auth token."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:466(para) ./doc/common/ch_cli_ceilometer_commands.xml:891(para)
+msgid "Name of the alarm (must be unique per tenant). Required."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:205(para)
-msgid "The number of times to retry a failed connection."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:475(para) ./doc/common/ch_cli_ceilometer_commands.xml:624(para) ./doc/common/ch_cli_ceilometer_commands.xml:900(para) ./doc/common/ch_cli_ceilometer_commands.xml:1097(para) ./doc/common/ch_cli_ceilometer_commands.xml:1302(para)
+msgid "Tenant to associate with alarm (only settable by admin users)."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:213(para)
-msgid "OpenStack username. Defaults to <code>env[OS_USERNAME]</code>."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:484(para) ./doc/common/ch_cli_ceilometer_commands.xml:633(para) ./doc/common/ch_cli_ceilometer_commands.xml:909(para) ./doc/common/ch_cli_ceilometer_commands.xml:1106(para) ./doc/common/ch_cli_ceilometer_commands.xml:1311(para)
+msgid "User to associate with alarm (only settable by admin users)."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:221(para)
-msgid "OpenStack password. Defaults to <code>env[OS_PASSWORD]</code>."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:493(para) ./doc/common/ch_cli_ceilometer_commands.xml:642(para) ./doc/common/ch_cli_ceilometer_commands.xml:918(para) ./doc/common/ch_cli_ceilometer_commands.xml:1115(para) ./doc/common/ch_cli_ceilometer_commands.xml:1320(para)
+msgid "Free text description of the alarm."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:229(para)
-msgid "OpenStack tenant ID. Defaults to <code>env[OS_TENANT_ID]</code>."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:501(para) ./doc/common/ch_cli_ceilometer_commands.xml:650(para) ./doc/common/ch_cli_ceilometer_commands.xml:926(para) ./doc/common/ch_cli_ceilometer_commands.xml:1123(para) ./doc/common/ch_cli_ceilometer_commands.xml:1328(para)
+msgid "State of the alarm, one of: ['ok', 'alarm', 'insufficient_data']"
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:237(para)
-msgid "OpenStack tenant name. Defaults to <code>env[OS_TENANT_NAME]</code>."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:510(para) ./doc/common/ch_cli_ceilometer_commands.xml:659(para) ./doc/common/ch_cli_ceilometer_commands.xml:935(para) ./doc/common/ch_cli_ceilometer_commands.xml:1132(para) ./doc/common/ch_cli_ceilometer_commands.xml:1337(para)
+msgid "True if alarm evaluation/actioning is enabled."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:246(para)
-msgid "OpenStack auth URL. Defaults to <code>env[OS_AUTH_URL]</code>."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:518(para) ./doc/common/ch_cli_ceilometer_commands.xml:667(para) ./doc/common/ch_cli_ceilometer_commands.xml:943(para) ./doc/common/ch_cli_ceilometer_commands.xml:1140(para) ./doc/common/ch_cli_ceilometer_commands.xml:1345(para)
+msgid "URL to invoke when state transitions to alarm. May be used multiple times. Defaults to None."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:254(para)
-msgid "OpenStack token. Defaults to <code>env[OS_AUTH_TOKEN]</code>. Used with --os-storage-url to bypass the usual username/password authentication."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:527(para) ./doc/common/ch_cli_ceilometer_commands.xml:676(para) ./doc/common/ch_cli_ceilometer_commands.xml:952(para) ./doc/common/ch_cli_ceilometer_commands.xml:1149(para) ./doc/common/ch_cli_ceilometer_commands.xml:1354(para)
+msgid "URL to invoke when state transitions to OK. May be used multiple times. Defaults to None."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:264(para)
-msgid "OpenStack storage URL. Defaults to <code>env[OS_STORAGE_URL]</code>. Overrides the storage url returned during auth. Will bypass authentication when used with --os-auth-token."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:536(para) ./doc/common/ch_cli_ceilometer_commands.xml:685(para) ./doc/common/ch_cli_ceilometer_commands.xml:961(para) ./doc/common/ch_cli_ceilometer_commands.xml:1158(para) ./doc/common/ch_cli_ceilometer_commands.xml:1363(para)
+msgid "URL to invoke when state transitions to insufficient_data. May be used multiple times. Defaults to None."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:275(para)
-msgid "OpenStack region name. Defaults to <code>env[OS_REGION_NAME]</code>."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:546(para) ./doc/common/ch_cli_ceilometer_commands.xml:695(para) ./doc/common/ch_cli_ceilometer_commands.xml:971(para) ./doc/common/ch_cli_ceilometer_commands.xml:1168(para) ./doc/common/ch_cli_ceilometer_commands.xml:1373(para)
+msgid "Only evaluate the alarm if the time at evaluation is within this time constraint. Start point(s) of the constraint are specified with a cron expression , whereas its duration is given in seconds. Can be specified multiple times for multiple time constraints, format is: name=&lt;CONSTRAINT_NAME&gt;;start=&lt; CRON&gt;;duration=&lt;SECONDS&gt;;[description=&lt;DESCRIPTION&gt;;[t imezone=&lt;IANA Timezone&gt;]] Defaults to None."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:284(para)
-msgid "OpenStack Service type. Defaults to <code>env[OS_SERVICE_TYPE]</code>."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:561(para)
+msgid "List of alarm ids. Required."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:293(para)
-msgid "OpenStack Endpoint type. Defaults to <code>env[OS_ENDPOINT_TYPE]</code>."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:569(para) ./doc/common/ch_cli_ceilometer_commands.xml:727(para)
+msgid "Operator to compare with, one of: ['and', 'or']."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:312(para)
-msgid "Allow swiftclient to access servers without having to verify the SSL certificate. Defaults to <code>env[SWIFTCLIENT_INSECURE]</code> (set to 'true' to enable)."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:577(para) ./doc/common/ch_cli_ceilometer_commands.xml:1046(para)
+msgid "True if actions should be repeatedly notified while alarm remains in target state. Defaults to False."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:322(para)
-msgid "This option is deprecated and not used anymore. SSL compression should be disabled by default by the system SSL library."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:586(title)
+msgid "ceilometer alarm-combination-update command"
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:332(title)
-msgid "swift delete command"
+#: ./doc/common/ch_cli_ceilometer_commands.xml:608(para) ./doc/common/ch_cli_ceilometer_commands.xml:1081(para) ./doc/common/ch_cli_ceilometer_commands.xml:1286(para)
+msgid "ID of the alarm to update. Required."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:342(para)
-msgid "Name of container to delete from."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:616(para) ./doc/common/ch_cli_ceilometer_commands.xml:1089(para) ./doc/common/ch_cli_ceilometer_commands.xml:1294(para)
+msgid "Name of the alarm (must be unique per tenant)."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:350(para)
-msgid "Name of object to delete. Specify multiple times for multiple objects."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:710(para) ./doc/common/ch_cli_ceilometer_commands.xml:1183(para) ./doc/common/ch_cli_ceilometer_commands.xml:1388(para)
+msgid "Name or list of names of the time constraints to remove."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:362(para)
-msgid "Delete all containers and objects."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:719(para)
+msgid "List of alarm id."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:370(para)
-msgid "Do not delete segments of manifest objects."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:735(para) ./doc/common/ch_cli_ceilometer_commands.xml:1252(para) ./doc/common/ch_cli_ceilometer_commands.xml:1457(para)
+msgid "True if actions should be repeatedly notified while alarm remains in target state."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:378(para)
-msgid "Number of threads to use for deleting objects. Default is 10."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:744(title)
+msgid "ceilometer alarm-delete command"
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:387(para)
-msgid "Number of threads to use for deleting containers. Default is 10."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:753(para)
+msgid "ID of the alarm to delete. Required."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:396(title)
-msgid "swift download command"
+#: ./doc/common/ch_cli_ceilometer_commands.xml:761(title)
+msgid "ceilometer alarm-history command"
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:406(para)
-msgid "Name of container to download from. To download a whole account, omit this and specify --all."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:770(para)
+msgid "ID of the alarm for which history is shown. Required."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:415(para)
-msgid "Name of object to download. Specify multiple times for multiple objects. Omit this to download all objects from the container."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:778(para) ./doc/common/ch_cli_ceilometer_commands.xml:797(para) ./doc/common/ch_cli_ceilometer_commands.xml:1036(para) ./doc/common/ch_cli_ceilometer_commands.xml:1242(para) ./doc/common/ch_cli_ceilometer_commands.xml:1518(para) ./doc/common/ch_cli_ceilometer_commands.xml:1646(para) ./doc/common/ch_cli_ceilometer_commands.xml:1771(para) ./doc/common/ch_cli_ceilometer_commands.xml:1807(para)
+msgid "key[op]data_type::value; list. data_type is optional, but if supplied must be string, integer, float, or boolean."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:428(para)
-msgid "Indicates that you really want to download everything in the account."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:788(title)
+msgid "ceilometer alarm-list command"
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:437(para)
-msgid "Marker to use when starting a container or account download."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:807(title)
+msgid "ceilometer alarm-show command"
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:446(para)
-msgid "Only download items beginning with &lt;prefix&gt;."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:816(para)
+msgid "ID of the alarm to show. Required."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:454(para)
-msgid "For a single file download, stream the output to &lt;out_file&gt;. Specifying \"-\" as &lt;out_file&gt; will redirect to stdout."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:824(title)
+msgid "ceilometer alarm-state-get command"
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:464(para)
-msgid "Number of threads to use for downloading objects. Default is 10"
+#: ./doc/common/ch_cli_ceilometer_commands.xml:833(para)
+msgid "ID of the alarm state to show. Required."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:473(para)
-msgid "Number of threads to use for downloading containers. Default is 10"
+#: ./doc/common/ch_cli_ceilometer_commands.xml:841(title)
+msgid "ceilometer alarm-state-set command"
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:482(para)
-msgid "Perform download(s), but don't actually write anything to disk."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:850(para)
+msgid "ID of the alarm state to set. Required."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:491(para)
-msgid "Adds a customized request header to the query, like \"Range\" or \"If-Match\". This argument is repeatable. Example --header \"content-type:text/plain\""
+#: ./doc/common/ch_cli_ceilometer_commands.xml:858(para)
+msgid "State of the alarm, one of: ['ok', 'alarm', 'insufficient_data']. Required."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:501(para)
-msgid "Skip downloading files that are identical on both sides."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:867(title)
+msgid "ceilometer alarm-threshold-create command"
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:510(title)
-msgid "swift list command"
+#: ./doc/common/ch_cli_ceilometer_commands.xml:986(para)
+msgid "Metric to evaluate against. Required."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:520(para)
-msgid "Name of container to list object in."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:994(para) ./doc/common/ch_cli_ceilometer_commands.xml:1200(para) ./doc/common/ch_cli_ceilometer_commands.xml:1397(para)
+msgid "Length of each period (seconds) to evaluate over."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:531(para)
-msgid "Long listing format, similar to ls -l."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1002(para) ./doc/common/ch_cli_ceilometer_commands.xml:1208(para) ./doc/common/ch_cli_ceilometer_commands.xml:1405(para)
+msgid "Number of periods to evaluate over."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:539(para) ./doc/common/ch_cli_swift_commands.xml:688(para)
-msgid "Report sizes in human readable format similar to ls -lh."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1010(para) ./doc/common/ch_cli_ceilometer_commands.xml:1216(para)
+msgid "Statistic to evaluate, one of: ['max', 'min', 'avg', 'sum', 'count']."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:548(para)
-msgid "Used with -l or --lh, only report totals."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1019(para) ./doc/common/ch_cli_ceilometer_commands.xml:1225(para) ./doc/common/ch_cli_ceilometer_commands.xml:1430(para)
+msgid "Operator to compare with, one of: ['lt', 'le', 'eq', 'ne', 'ge', 'gt']."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:556(para)
-msgid "Only list items beginning with the prefix."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1028(para)
+msgid "Threshold to evaluate against. Required."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:564(para)
-msgid "Roll up items with the given delimiter. For containers only. See OpenStack Swift API documentation for what this means."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1055(title)
+msgid "ceilometer alarm-threshold-update command"
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:574(title)
-msgid "swift post command"
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1192(para) ./doc/common/ch_cli_ceilometer_commands.xml:1413(para)
+msgid "Metric to evaluate against."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:577(para)
-msgid "Updates meta information for the account, container, or object. If the container is not found, it will be created automatically."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1234(para) ./doc/common/ch_cli_ceilometer_commands.xml:1439(para)
+msgid "Threshold to evaluate against."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:585(para)
-msgid "Name of container to post to."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1261(title)
+msgid "ceilometer alarm-update command"
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:593(para)
-msgid "Name of object to post. Specify multiple times for multiple objects."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1421(para)
+msgid "Statistic to evaluate, one of: ['max', 'min', 'avg', 'sum', 'count']"
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:605(para)
-msgid "Read ACL for containers. Quick summary of ACL syntax: .r:*, .r:-.example.com, .r:www.example.com, account1, account2:user2"
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1447(para)
+msgid "A meter should match this resource metadata (key=value) additionally to the meter_name. Defaults to None."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:615(para)
-msgid "Write ACL for containers. Quick summary of ACL syntax: account1 account2:user2"
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1466(title)
+msgid "ceilometer event-list command"
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:624(para)
-msgid "Sync To for containers, for multi-cluster replication."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1475(para)
+msgid "key[op]data_type::value; list. data_type is optional, but if supplied must be string, integer, floator datetime."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:632(para)
-msgid "Sync Key for containers, for multi-cluster replication."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1485(title)
+msgid "ceilometer event-show command"
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:640(para)
-msgid "Sets a meta data item. This option may be repeated. Example: -m Color:Blue -m Size:Large"
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1494(para)
+msgid "The id of the event. Should be a UUID Required."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:649(para)
-msgid "Set request headers. This option may be repeated. Example -H \"content-type:text/plain\""
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1502(title)
+msgid "ceilometer event-type-list command"
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:658(title)
-msgid "swift stat command"
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1509(title)
+msgid "ceilometer meter-list command"
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:668(para)
-msgid "Name of container to stat from."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1528(title)
+msgid "ceilometer query-alarm-history command"
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:676(para)
-msgid "Name of object to stat. Specify multiple times for multiple objects."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1538(para) ./doc/common/ch_cli_ceilometer_commands.xml:1574(para) ./doc/common/ch_cli_ceilometer_commands.xml:1610(para)
+msgid "{complex_op: [{simple_op: {field_name: value}}]} The complex_op is one of: ['and', 'or'], simple_op is one of: ['=', '!=', '&lt;', '&lt;=', '&gt;', '&gt;=']."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:697(title)
-msgid "swift upload command"
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1548(para) ./doc/common/ch_cli_ceilometer_commands.xml:1584(para) ./doc/common/ch_cli_ceilometer_commands.xml:1620(para)
+msgid "[{field_name: direction}, {field_name: direction}] The direction is one of: ['asc', 'desc']."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:700(para)
-msgid "Uploads specified files and directories to the given container."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1557(para)
+msgid "Maximum number of alarm history items to return."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:707(para)
-msgid "Name of container to upload to."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1565(title)
+msgid "ceilometer query-alarms command"
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:715(para)
-msgid "Name of file or directory to upload. Specify multiple times for multiple uploads."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1593(para)
+msgid "Maximum number of alarms to return."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:727(para)
-msgid "Only upload files that have changed since the last upload."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1601(title)
+msgid "ceilometer query-samples command"
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:736(para)
-msgid "Skip uploading files that are identical on both sides."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1629(para) ./doc/common/ch_cli_ceilometer_commands.xml:1789(para)
+msgid "Maximum number of samples to return."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:744(para)
-msgid "Upload files in segments no larger than &lt;size&gt; (in Bytes) and then create a \"manifest\" file that will download all the segments as if it were the original file."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1637(title)
+msgid "ceilometer resource-list command"
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:755(para)
-msgid "Upload the segments into the specified container. If not specified, the segments will be uploaded to a &lt;container&gt;_segments container to not pollute the main &lt;container&gt; listings."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1656(title)
+msgid "ceilometer resource-show command"
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:766(para)
-msgid "Indicates that you want the older segments of manifest objects left alone (in the case of overwrites)."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1665(para)
+msgid "ID of the resource to show. Required."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:775(para)
-msgid "Number of threads to use for uploading full objects. Default is 10."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1673(title)
+msgid "ceilometer sample-create command"
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:784(para)
-msgid "Number of threads to use for uploading object segments. Default is 10."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1688(para)
+msgid "Tenant to associate with sample (only settable by admin users)."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:793(para)
-msgid "Set request headers with the syntax header:value. This option may be repeated. Example -H \"content-type:text/plain\"."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1697(para)
+msgid "User to associate with sample (only settable by admin users)."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:803(para)
-msgid "When used in conjunction with --segment-size it will create a Static Large Object instead of the default Dynamic Large Object."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1706(para)
+msgid "ID of the resource. Required."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml:813(para)
-msgid "Upload file and name object to &lt;object-name&gt; or upload dir and use &lt;object-name&gt; as object prefix instead of folder name."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1714(para)
+msgid "The meter name. Required."
 msgstr ""
 
-#: ./doc/common/section_cli_neutron-quotas.xml:6(title)
-msgid "Manage Networking service quotas"
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1722(para)
+msgid "The meter type. Required."
 msgstr ""
 
-#: ./doc/common/section_cli_neutron-quotas.xml:7(para)
-msgid "A quota limits the number of available resources. A default quota might be enforced for all tenants. When you try to create more resources than the quota allows, an error occurs:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1730(para)
+msgid "The meter unit. Required."
 msgstr ""
 
-#: ./doc/common/section_cli_neutron-quotas.xml:12(para)
-msgid "Per-tenant quota configuration is also supported by the quota extension API. See <link linkend=\"cfg_quotas_per_tenant\"> Per-tenant quota configuration</link> for details."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1738(para)
+msgid "The sample volume. Required."
 msgstr ""
 
-#: ./doc/common/section_cli_neutron-quotas.xml:16(title)
-msgid "Basic quota configuration"
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1746(para)
+msgid "Resource metadata."
 msgstr ""
 
-#: ./doc/common/section_cli_neutron-quotas.xml:17(para)
-msgid "In the Networking default quota mechanism, all tenants have the same quota values, such as the number of resources that a tenant can create."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1754(para)
+msgid "The sample timestamp."
 msgstr ""
 
-#: ./doc/common/section_cli_neutron-quotas.xml:20(para)
-msgid "The quota value is defined in the OpenStack Networking <filename>neutron.conf</filename> configuration file. To disable quotas for a specific resource, such as network, subnet, or port, remove a corresponding item from <option>quota_items</option>. This example shows the default quota values:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1762(title)
+msgid "ceilometer sample-list command"
 msgstr ""
 
-#: ./doc/common/section_cli_neutron-quotas.xml:41(para)
-msgid "OpenStack Networking also supports quotas for L3 resources: router and floating IP. Add these lines to the <literal>quotas</literal> section in the <filename>neutron.conf</filename> file."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1781(para) ./doc/common/ch_cli_ceilometer_commands.xml:1817(para)
+msgid "Name of meter to show samples for. Required."
 msgstr ""
 
-#: ./doc/common/section_cli_neutron-quotas.xml:52(para) ./doc/common/section_cli_neutron-quotas.xml:67(para)
-msgid "The <option>quota_items</option> option does not affect these quotas."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1797(title)
+msgid "ceilometer statistics command"
 msgstr ""
 
-#: ./doc/common/section_cli_neutron-quotas.xml:55(para)
-msgid "OpenStack Networking also supports quotas for security group resources: number of security groups and the number of rules for each security group. Add these lines to the <literal>quotas</literal> section in the <filename>neutron.conf</filename> file:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1825(para)
+msgid "Period in seconds over which to group samples."
 msgstr ""
 
-#: ./doc/common/section_cli_neutron-quotas.xml:72(title)
-msgid "Configure per-tenant quotas"
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1833(para)
+msgid "Field for group by."
 msgstr ""
 
-#: ./doc/common/section_cli_neutron-quotas.xml:73(para)
-msgid "OpenStack Networking also supports per-tenant quota limit by quota extension API."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1841(para)
+msgid "Function for data aggregation. Available aggregates are: count, cardinality, min, max, sum, stddev, avg. Defaults to []."
 msgstr ""
 
-#: ./doc/common/section_cli_neutron-quotas.xml:77(para)
-msgid "<placeholder-1/>. Deletes defined quotas for a specified tenant."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1851(title)
+msgid "ceilometer trait-description-list command"
 msgstr ""
 
-#: ./doc/common/section_cli_neutron-quotas.xml:81(para)
-msgid "<placeholder-1/>. Lists defined quotas for all tenants."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1860(para)
+msgid "Type of the event for which traits will be shown. Required."
 msgstr ""
 
-#: ./doc/common/section_cli_neutron-quotas.xml:85(para)
-msgid "<placeholder-1/>. Shows quotas for a specified tenant."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1869(title)
+msgid "ceilometer trait-list command"
 msgstr ""
 
-#: ./doc/common/section_cli_neutron-quotas.xml:89(para)
-msgid "<placeholder-1/>. Updates quotas for a specified tenant."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1871(para)
+msgid "List trait all traits with name &lt;trait_name&gt; for Event Type &lt;event_type&gt;."
 msgstr ""
 
-#: ./doc/common/section_cli_neutron-quotas.xml:75(para)
-msgid "Use these commands to manage per-tenant quotas:<placeholder-1/>Only users with the <literal>admin</literal> role can change a quota value. By default, the default set of quotas are enforced for all tenants, so no <placeholder-2/> command exists."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1878(para)
+msgid "Type of the event for which traits will listed. Required."
 msgstr ""
 
-#: ./doc/common/section_cli_neutron-quotas.xml:98(title)
-msgid "Configure Networking to show per-tenant quotas"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml:99(para)
-msgid "Set the <literal>quota_driver</literal> option in the <literal>neutron.conf</literal> file:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml:102(para)
-msgid "When you set this option, the output for Networking commands shows <literal>quotas</literal>."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml:106(title)
-msgid "List Networking extensions"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml:107(para)
-msgid "To list the Networking extensions, run this command:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml:110(para)
-msgid "The command shows the <literal>quotas</literal> extension, which provides per-tenant quota management support:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml:128(title)
-msgid "Show information for the quotas extension"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml:129(para)
-msgid "To show information for the <literal>quotas</literal> extension, run this command:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml:143(para)
-msgid "Only some plug-ins support per-tenant quotas. Specifically, Open vSwitch, Linux Bridge, and VMware NSX support them, but new versions of other plug-ins might bring additional functionality. See the documentation for each plug-in."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml:151(title)
-msgid "List tenants who have per-tenant quota support"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml:152(para)
-msgid "The <placeholder-1/> command lists tenants for which the per-tenant quota is enabled. The command does not list tenants with default quota support. You must be an administrative user to run this command:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml:165(title)
-msgid "Show per-tenant quota values"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml:166(para)
-msgid "The <placeholder-1/> reports the current set of quota limits for the specified tenant. Non-administrative users can run this command without the <parameter>--tenant_id</parameter> parameter. If per-tenant quota limits are not enabled for the tenant, the command shows the default set of quotas:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml:182(para)
-msgid "The following command shows the command output for a non-administrative user:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml:196(title)
-msgid "Update quota values for a specified tenant"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml:197(para)
-msgid "Use the <placeholder-1/> command to update a quota for a specified tenant:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml:209(para)
-msgid "You can update quotas for multiple resources through one command:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml:221(para)
-msgid "To update the limits for an L3 resource such as, router or floating IP, you must define new values for the quotas after the <parameter>--</parameter> directive."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml:224(para)
-msgid "This example updates the limit of the number of floating IPs for the specified tenant:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml:236(para)
-msgid "You can update the limits of multiple resources by including L2 resources and L3 resource through one command."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml:251(title)
-msgid "Delete per-tenant quota values"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml:252(para)
-msgid "To clear per-tenant quota limits, use the <placeholder-1/> command:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml:256(para)
-msgid "After you run this command, you can see that quota values for the tenant are reset to the default values:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_terminate.xml:8(title)
-msgid "Delete an instance"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_terminate.xml:9(para)
-msgid "When you no longer need an instance, you can delete it."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_terminate.xml:11(para)
-msgid "List all instances:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_terminate.xml:21(para)
-msgid "Run the <placeholder-1/> command to delete the instance. The following example shows deletion of the <filename>newServer</filename> instance, which is in <literal>ERROR</literal> state:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_terminate.xml:24(para)
-msgid "The command does not notify that your server was deleted."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_terminate.xml:25(para)
-msgid "To verify that the server was deleted, run the <placeholder-1/> command:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_terminate.xml:33(para)
-msgid "The deleted instance does not appear in the list."
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_example_usage.xml:6(title)
-msgid "keystone command-line client example usage"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_example_usage.xml:7(para)
-msgid "Before you can use keystone client commands, you must download and source an OpenStack RC file. For information, see the <citetitle>OpenStack Admin User Guide</citetitle>."
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_example_usage.xml:10(para)
-msgid "The keystone command-line client uses the following syntax:"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_example_usage.xml:12(replaceable)
-msgid "PARAMETER"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_example_usage.xml:12(replaceable)
-msgid "ARGUMENT"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_example_usage.xml:13(para)
-msgid "For example, you can run the <placeholder-1/> and <placeholder-2/> commands, as follows:"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_example_usage.xml:22(replaceable) ./doc/common/section_cli_keystone_example_usage.xml:23(replaceable)
-msgid "token"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_example_usage.xml:22(replaceable) ./doc/common/section_cli_keystone_example_usage.xml:23(replaceable)
-msgid "endpoint"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_example_usage.xml:31(replaceable)
-msgid "id"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_example_usage.xml:34(para)
-msgid "For information about using the keystone client commands to create and manage users, roles, and projects, see the <citetitle>OpenStack Admin User Guide</citetitle>."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_volumes.xml:8(title)
-msgid "Manage Volumes"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_volumes.xml:9(para)
-msgid "Depending on the setup of your cloud provider, they may give you an endpoint to use to manage volumes, or there may be an extension under the covers. In either case, you can use the <placeholder-1/> CLI to manage volumes:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_volumes.xml:26(para)
-msgid "For example, to list IDs and names of Compute volumes, run:"
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml:5(title)
-msgid "OpenStack Object Storage"
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml:6(para)
-msgid "The OpenStack Object Storage is a multi-tenant object storage system. It is highly scalable and can manage large amounts of unstructured data at low cost through a RESTful HTTP API."
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml:11(term)
-msgid "Proxy servers (<systemitem class=\"service\">swift-proxy-server</systemitem>)"
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml:13(para)
-msgid "Accepts OpenStack Object Storage API and raw HTTP requests to upload files, modify metadata, and create containers. It also serves file or container listings to web browsers. To improve performance, the proxy server can use an optional cache usually deployed with memcache."
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml:20(term)
-msgid "Account servers (<systemitem class=\"service\">swift-account-server</systemitem>)"
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml:22(para)
-msgid "Manages accounts defined with Object Storage."
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml:26(term)
-msgid "Container servers (<systemitem class=\"service\">swift-container-server</systemitem>)"
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml:28(para)
-msgid "Manages the mapping of containers or folders, within Object Storage."
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml:32(term)
-msgid "Object servers (<systemitem class=\"service\">swift-object-server</systemitem>)"
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml:34(para)
-msgid "Manages actual objects,such as files, on the storage nodes."
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml:38(term)
-msgid "Various periodic processes"
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml:39(para)
-msgid "Performs housekeeping tasks on the large data store. The replication services ensure consistency and availability through the cluster. Other periodic processes include auditors, updaters, and reapers."
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml:45(term)
-msgid "WSGI middleware"
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml:46(para)
-msgid "Handles authentication and is usually OpenStack Identity."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml:6(title)
-msgid "Secure the OpenStack Identity service connection to an LDAP back end"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml:8(para)
-msgid "The Identity service supports the use of TLS to encrypt LDAP traffic. Before configuring this, you must first verify where your certificate authority file is located. For more information, see <xref linkend=\"certificates-for-pki\"/>."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml:12(para)
-msgid "Once you verify the location of your certificate authority file:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml:15(title)
-msgid "Configuring TLS encryption on LDAP traffic"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml:17(para)
-msgid "Open the <filename>/etc/keystone/keystone.conf</filename> configuration file."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml:23(para)
-msgid "Find the <literal>[ldap]</literal> section."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml:26(para)
-msgid "In the <literal>[ldap]</literal> section, set the <literal>use_tls</literal> configuration key to <literal>True</literal>. Doing so will enable TLS."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml:31(para)
-msgid "Configure the Identity service to use your certificate authorities file. To do so, set the <literal>tls_cacertfile</literal> configuration key in the <literal>ldap</literal> section to the certificate authorities file's path."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml:37(para)
-msgid "You can also set the <literal>tls_cacertdir</literal> (also in the <literal>ldap</literal> section) to the directory where all certificate authorities files are kept. If both <literal>tls_cacertfile</literal> and <literal>tls_cacertdir</literal> are set, then the latter will be ignored."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml:46(para)
-msgid "Specify what client certificate checks to perform on incoming TLS sessions from the LDAP server. To do so, set the <literal>tls_req_cert</literal> configuration key in the <literal>[ldap]</literal> section to <literal>demand</literal>, <literal>allow</literal>, or <literal>never</literal>:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml:53(para)
-msgid "<parameter>demand</parameter>: a certificate will always be requested from the LDAP server. The session will be terminated if no certificate is provided, or if the certificate provided cannot be verified against the existing certificate authorities file."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml:60(para)
-msgid "<parameter>allow</parameter>: a certificate will always be requested from the LDAP server. The session will proceed as normal even if a certificate is not provided. If a certificate is provided but it cannot be verified against the existing certificate authorities file, the certificate will be ignored and the session will proceed as normal."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml:67(para)
-msgid "<parameter>never</parameter>: a certificate will never be requested."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml:72(para)
-msgid "On distributions that include <application>openstack-config</application>, you can configure TLS encryption on LDAP traffic by running the following commands instead:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml:80(replaceable)
-msgid "CA_FILE"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml:82(replaceable)
-msgid "CERT_BEHAVIOR"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml:83(para) ./doc/common/section_cli_nova_customize_flavors.xml:260(para) ./doc/common/section_trusted-compute-pools.xml:78(para)
-msgid "Where:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml:85(para)
-msgid "<replaceable>CA_FILE</replaceable> is the absolute path to the certificate authorities file that should be used to encrypt LDAP traffic."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml:88(para)
-msgid "<replaceable>CERT_BEHAVIOR</replaceable>: specifies what client certificate checks to perform on an incoming TLS session from the LDAP server (<literal>demand</literal>, <literal>allow</literal>, or <literal>never</literal>)."
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml:7(title) ./doc/common/section_rpc.xml:7(title)
-msgid "Configure the Oslo RPC messaging system"
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml:9(para)
-msgid "OpenStack projects use an open standard for messaging middleware known as AMQP. This messaging middleware enables the OpenStack services that run on multiple servers to talk to each other. OpenStack Oslo RPC supports three implementations of AMQP: <application>RabbitMQ</application>, <application>Qpid</application>, and <application>ZeroMQ</application>."
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml:18(title) ./doc/common/section_rpc.xml:15(title)
-msgid "Configure RabbitMQ"
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml:20(para)
-msgid "OpenStack Oslo RPC uses <application>RabbitMQ</application> by default. Use these options to configure the <application>RabbitMQ</application> message system. The <option>rpc_backend</option> option is optional as long as <application>RabbitMQ</application> is the default messaging system. However, if it is included the configuration, you must set it to <literal>neutron.openstack.common.rpc.impl_kombu</literal>."
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml:34(para)
-msgid "Use these options to configure the <application>RabbitMQ</application> messaging system. You can configure messaging communication for different installation scenarios, tune retries for RabbitMQ, and define the size of the RPC thread pool. To monitor notifications through RabbitMQ, you must set the <option>notification_driver</option> option to <literal>neutron.notifier.rabbit_notifier</literal> in the <filename>neutron.conf</filename> file:"
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml:46(title) ./doc/common/section_rpc.xml:39(title)
-msgid "Configure Qpid"
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml:47(para)
-msgid "Use these options to configure the <application>Qpid</application> messaging system for OpenStack Oslo RPC. <application>Qpid</application> is not the default messaging system, so you must enable it by setting the <option>rpc_backend</option> option in the <filename>neutron.conf</filename> file:"
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml:56(para)
-msgid "This critical option points the compute nodes to the <application>Qpid</application> broker (server). Set the <option>qpid_hostname</option> option to the host name where the broker runs in the <filename>neutron.conf</filename> file."
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml:62(para) ./doc/common/section_rpc.xml:52(para)
-msgid "The <option>--qpid_hostname</option> option accepts a host name or IP address value."
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml:69(para) ./doc/common/section_rpc.xml:56(para)
-msgid "If the <application>Qpid</application> broker listens on a port other than the AMQP default of <literal>5672</literal>, you must set the <option>qpid_port</option> option to that value:"
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml:78(para) ./doc/common/section_rpc.xml:61(para)
-msgid "If you configure the <application>Qpid</application> broker to require authentication, you must add a user name and password to the configuration:"
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml:87(para) ./doc/common/section_rpc.xml:66(para)
-msgid "By default, TCP is used as the transport. To enable SSL, set the <option>qpid_protocol</option> option:"
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml:94(para)
-msgid "Use these additional options to configure the Qpid messaging driver for OpenStack Oslo RPC. These options are used infrequently."
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml:102(title) ./doc/common/section_rpc.xml:75(title)
-msgid "Configure ZeroMQ"
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml:103(para)
-msgid "Use these options to configure the <application>ZeroMQ</application> messaging system for OpenStack Oslo RPC. <application>ZeroMQ</application> is not the default messaging system, so you must enable it by setting the <option>rpc_backend</option> option in the <filename>neutron.conf</filename> file:"
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml:112(title) ./doc/common/section_rpc.xml:85(title)
-msgid "Configure messaging"
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml:114(para)
-msgid "Use these common options to configure the <application>RabbitMQ</application>, <application>Qpid</application>, and <application>ZeroMq</application> messaging drivers:"
-msgstr ""
-
-#: ./doc/common/section_fibrechannel.xml:5(title)
-msgid "Fibre Channel support in Compute"
-msgstr ""
-
-#: ./doc/common/section_fibrechannel.xml:6(para)
-msgid "Fibre Channel support in OpenStack Compute is remote block storage attached to compute nodes for VMs."
-msgstr ""
-
-#. TODO: This below statement needs to be verified for current release
-#: ./doc/common/section_fibrechannel.xml:9(para)
-msgid "In the Grizzly release, Fibre Channel supported only the KVM hypervisor."
-msgstr ""
-
-#: ./doc/common/section_fibrechannel.xml:11(para)
-msgid "Compute and Block Storage for Fibre Channel do not support automatic zoning. Fibre Channel arrays must be pre-zoned or directly attached to the KVM hosts."
-msgstr ""
-
-#: ./doc/common/section_fibrechannel.xml:15(title)
-msgid "KVM host requirements"
-msgstr ""
-
-#: ./doc/common/section_fibrechannel.xml:16(para)
-msgid "You must install these packages on the KVM host:"
-msgstr ""
-
-#: ./doc/common/section_fibrechannel.xml:19(para)
-msgid "<package>sysfsutils</package> - Nova uses the <package>systool</package> application in this package."
-msgstr ""
-
-#: ./doc/common/section_fibrechannel.xml:25(para)
-msgid "<package>sg3-utils</package> - Nova uses the <package>sg_scan</package> and <package>sginfo</package> applications."
-msgstr ""
-
-#: ./doc/common/section_fibrechannel.xml:31(para)
-msgid "Installing the <package>multipath-tools</package> package is optional."
-msgstr ""
-
-#: ./doc/common/section_fibrechannel.xml:35(title)
-msgid "Install required packages"
-msgstr ""
-
-#: ./doc/common/section_fibrechannel.xml:36(para)
-msgid "Use these commands to install the system packages:"
-msgstr ""
-
-#: ./doc/common/section_fibrechannel.xml:40(para)
-msgid "For systems running openSUSE or SUSE Linux Enterprise Server:"
-msgstr ""
-
-#: ./doc/common/section_fibrechannel.xml:45(para)
-msgid "For systems running Red Hat:"
-msgstr ""
-
-#: ./doc/common/section_fibrechannel.xml:49(para)
-msgid "For systems running Ubuntu:"
-msgstr ""
-
-#: ./doc/common/section_cli_help.xml:6(title)
-msgid "Get help for client commands"
-msgstr ""
-
-#: ./doc/common/section_cli_help.xml:7(para)
-msgid "To get usage information, including a list of commands with descriptions, for a client, run the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_help.xml:9(replaceable) ./doc/common/section_cli_help.xml:59(replaceable)
-msgid "CLIENT_NAME"
-msgstr ""
-
-#: ./doc/common/section_cli_help.xml:10(para)
-msgid "For example, to get help information for the swift client, run the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_help.xml:54(para)
-msgid "Depending on your credentials, you might not have permission to use every command."
-msgstr ""
-
-#: ./doc/common/section_cli_help.xml:57(para)
-msgid "After the <option>help</option> command, you can enter a command name to get help for that command, as follows:"
-msgstr ""
-
-#: ./doc/common/section_cli_help.xml:59(replaceable)
-msgid "COMMAND_NAME"
-msgstr ""
-
-#: ./doc/common/section_cli_help.xml:60(para)
-msgid "For example, to get help for the glance <placeholder-1/> command, enter the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_help.xml:64(para)
-msgid "The command returns a description of the command and its positional and optional arguments:"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:6(title)
-msgid "Get started with OpenStack"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:7(para)
-msgid "The OpenStack project is an open source cloud computing platform for all types of clouds, which aims to be simple to implement, massively scalable, and feature rich. Developers and cloud computing technologists from around the world create the OpenStack project."
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:12(para)
-msgid "OpenStack provides an Infrastructure-as-a-Service (<glossterm>IaaS</glossterm>) solution through a set of interrelated services. Each service offers an application programming interface (<glossterm>API</glossterm>) that facilitates this integration. Depending on your needs, you can install some or all services."
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:20(para)
-msgid "The following table describes the OpenStack services that make up the OpenStack architecture:"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:23(caption) ./doc/common/ch_getstart.xml:188(title)
-msgid "OpenStack services"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:29(th) ./doc/common/section_keystone-concepts.xml:83(term) ./doc/common/section_cli_overview.xml:33(th)
-msgid "Service"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:30(th)
-msgid "Project name"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:38(glossterm)
-msgid "Dashboard"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:42(glossterm)
-msgid "Horizon"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:44(td)
-msgid "Provides a web-based self-service portal to interact with underlying OpenStack services, such as launching an instance, assigning IP addresses and configuring access controls."
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:52(glossterm) ./doc/common/section_dashboard_access.xml:100(guilabel) ./doc/common/section_cli_overview.xml:47(td)
-msgid "Compute"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:56(glossterm)
-msgid "Nova"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:58(td)
-msgid "Manages the lifecycle of compute instances in an OpenStack environment. Responsibilities include spawning, scheduling and decommissioning of virtual machines on demand."
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:66(glossterm) ./doc/common/section_cli_overview.xml:71(td)
-msgid "Networking"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:70(glossterm)
-msgid "Neutron"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:72(td)
-msgid "Enables network connectivity as a service for other OpenStack services, such as OpenStack Compute. Provides an API for users to define networks and the attachments into them. Has a pluggable architecture that supports many popular networking vendors and technologies."
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:79(th)
-msgid "Storage"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:83(glossterm) ./doc/common/section_cli_overview.xml:78(td)
-msgid "Object Storage"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:87(glossterm)
-msgid "Swift"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:90(glossterm)
-msgid "RESTful"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:89(td)
-msgid "Stores and retrieves arbitrary unstructured data objects via a <placeholder-1/>, HTTP based API. It is highly fault tolerant with its data replication and scale out architecture. Its implementation is not like a file server with mountable directories."
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:99(glossterm) ./doc/common/section_cli_overview.xml:41(td)
-msgid "Block Storage"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:103(glossterm)
-msgid "Cinder"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:105(td)
-msgid "Provides persistent block storage to running instances. Its pluggable driver architecture facilitates the creation and management of block storage devices."
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:110(th)
-msgid "Shared services"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:114(glossterm)
-msgid "Identity service"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:118(glossterm)
-msgid "Keystone"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:120(td)
-msgid "Provides an authentication and authorization service for other OpenStack services. Provides a catalog of endpoints for all OpenStack services."
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:127(glossterm) ./doc/common/section_cli_overview.xml:65(td)
-msgid "Image Service"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:131(glossterm)
-msgid "Glance"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:133(td)
-msgid "Stores and retrieves virtual machine disk images. OpenStack Compute makes use of this during instance provisioning."
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:142(glossterm) ./doc/common/section_cli_overview.xml:93(td)
-msgid "Telemetry"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:146(glossterm)
-msgid "Ceilometer"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:148(td)
-msgid "Monitors and meters the OpenStack cloud for billing, benchmarking, scalability, and statistical purposes."
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:153(th)
-msgid "Higher-level services"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:157(glossterm) ./doc/common/section_dashboard_access.xml:192(guilabel) ./doc/common/section_cli_overview.xml:86(td)
-msgid "Orchestration"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:160(glossterm)
-msgid "Heat"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:164(glossterm)
-msgid "HOT"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:162(td)
-msgid "Orchestrates multiple composite cloud applications by using either the native <placeholder-1/> template format or the AWS CloudFormation template format, through both an OpenStack-native REST API and a CloudFormation-compatible Query API."
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:172(glossterm) ./doc/common/section_cli_overview.xml:53(td)
-msgid "Database Service"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:176(glossterm)
-msgid "Trove"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:178(td)
-msgid "Provides scalable and reliable Cloud Database-as-a-Service functionality for both relational and non-relational database engines."
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:189(para)
-msgid "This section describes OpenStack services in detail."
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml:207(title)
-msgid "Feedback"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:5(title)
-msgid "OpenStack Compute"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:6(para)
-msgid "OpenStack Compute is used to host and manage cloud computing systems and is a major part of an infrastructure-as-a-service (IaaS) system. The main modules are implemented in Python."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:9(para)
-msgid "OpenStack Compute interacts with OpenStack Identity for authentication, OpenStack Image Service for images, and OpenStack dashboard for the user and administrative interface. Access to images is limited by project and by user; quotas are limited per project (for example, the number of instances). OpenStack Compute can scale horizontally on standard hardware, and download images to launch instances."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:15(para)
-msgid "OpenStack Compute consists of the following areas and their components:"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:17(title)
-msgid "API"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:19(systemitem)
-msgid "nova-api service"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:20(para)
-msgid "Accepts and responds to end user compute API calls. Supports the OpenStack Compute API, the Amazon EC2 API, and a special Admin API for privileged users to perform administrative actions. It enforces some policies and initiates most orchestration activities, such as running an instance."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:28(term)
-msgid "<systemitem class=\"service\">nova-api-metadata</systemitem> service"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:30(para)
-msgid "Accepts metadata requests from instances. The <systemitem class=\"service\">nova-api-metadata</systemitem> service is generally used when you run in multi-host mode with <systemitem class=\"service\">nova-network</systemitem> installations. For details, see <link href=\"http://docs.openstack.org/admin-guide-cloud/content/section_metadata-service.html\">Metadata service</link> in the <citetitle>Cloud Administrator Guide</citetitle>."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:38(para)
-msgid "On Debian systems, it is included in the <systemitem class=\"service\">nova-api</systemitem> package, and can be selected through <package>debconf</package>."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:44(title)
-msgid "Compute core"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:46(term)
-msgid "<systemitem class=\"service\">nova-compute</systemitem> process"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:47(para)
-msgid "A worker daemon that creates and terminates virtual machine instances through hypervisor APIs. For example, XenAPI for XenServer/XCP, libvirt for KVM or QEMU and VMwareAPI for VMware. Processing is fairly complex but fundamentally it accepts actions from the queue and performs a series of system commands, like launching a KVM instance, whilst updating its state in the database."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:56(term)
-msgid "<systemitem class=\"service\">nova-scheduler</systemitem> process"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:58(para)
-msgid "Conceptually the simplest piece of code in OpenStack Compute. It takes a virtual machine instance request from the queue and determines on which compute server host it will run."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:64(term)
-msgid "<systemitem class=\"service\">nova-conductor</systemitem> module"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:65(para)
-msgid "Mediates interactions between <systemitem class=\"service\">nova-compute</systemitem> and the database. It eliminates direct accesses to the cloud database made by <systemitem class=\"service\">nova-compute</systemitem>. The <systemitem class=\"service\">nova-conductor</systemitem> module scales horizontally. However, do not deploy it on any nodes where <systemitem class=\"service\">nova-compute</systemitem> runs. For more information, see <link href=\"http://russellbryantnet.wordpress.com/2012/11/19/a-new-nova-service-nova-conductor/\">A new Nova service: nova-conductor</link>."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:79(title)
-msgid "Networking for VMs"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:80(term)
-msgid "<systemitem class=\"service\">nova-network</systemitem> worker daemon"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:82(para)
-msgid "Similar to <systemitem class=\"service\">nova-compute</systemitem>, it accepts networking tasks from the queue and performs tasks to manipulate the network, such as setting up bridging interfaces or changing iptables rules. This functionality is being migrated to OpenStack Networking."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:90(term)
-msgid "<systemitem class=\"service\">nova-dhcpbridge</systemitem> script"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:92(para)
-msgid "The IP address leases and is recorded in the database using the dnsmasq <literal>dhcp-script</literal> facility. This functionality is being migrated to OpenStack Networkin which provides a different script."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:99(title)
-msgid "Console interface"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:101(term)
-msgid "<systemitem class=\"service\">nova-consoleauth</systemitem> daemon"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:102(para)
-msgid "Authorizes tokens for users that console proxies provide. See <systemitem class=\"service\">nova-novncproxy</systemitem> and <systemitem class=\"service\">nova-xvpnvcproxy</systemitem>. This service must be running for console proxies to work. Many proxies of either type can be run against a single <systemitem class=\"service\">nova-consoleauth</systemitem> service in a cluster configuration. For information, see <link href=\"http://docs.openstack.org/trunk/config-reference/content/about-nova-consoleauth.html\">About nova-consoleauth</link>."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:114(term)
-msgid "<systemitem class=\"service\">nova-novncproxy</systemitem> daemon"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:116(para)
-msgid "Provides a proxy for accessing running instances through a VNC connection. Supports browser-based novnc clients."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:121(term)
-msgid "<systemitem class=\"service\">nova-xvpnvncproxy</systemitem> daemon"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:123(para)
-msgid "A proxy for accessing running instances through a VNC connection. It supports a Java client specifically designed for OpenStack."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:128(term)
-msgid "<systemitem class=\"service\">nova-cert</systemitem> daemon"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:129(para)
-msgid "x509 certificates."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:132(para)
-msgid "In Debian, a unique <package>nova-consoleproxy</package> package provides the <package>nova-novncproxy</package>, <package>nova-spicehtml5proxy</package>, and <package>nova-xvpvncproxy</package> packages. To select packages, edit the <filename>/etc/default/nova-consoleproxy</filename> file or use the <package>debconf</package> interface. You can also manually edit the <filename>/etc/default/nova-consoleproxy</filename> file, and stop and start the console daemons."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:142(title)
-msgid "Image management (EC2 scenario)"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:144(term)
-msgid "<systemitem class=\"service\">nova-objectstore</systemitem> daemon"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:145(para)
-msgid "A S3 interface for registering images with the OpenStack Image Service. It is mainly used for installations that must support euca2ools. The euca2ools tools talk to <systemitem class=\"service\">nova-objectstore</systemitem> in <emphasis role=\"italic\">S3 language</emphasis>, and <systemitem class=\"service\">nova-objectstore</systemitem> translates S3 requests into Image service requests."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:154(term)
-msgid "euca2ools client"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:155(para)
-msgid "A set of command-line interpreter commands for managing cloud resources. Although it is not an OpenStack module, you can configure <systemitem class=\"service\">nova-api</systemitem> to support this EC2 interface. For more information, see the <link href=\"https://www.eucalyptus.com/docs/eucalyptus/3.4/index.html\">Eucalyptus 3.4 Documentation</link>."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:163(title)
-msgid "Command-line clients and other interfaces"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:164(term)
-msgid "nova client"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:165(para)
-msgid "Allows users to submit commands as a tenant administrator or end user."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:169(term)
-msgid "nova-manage client"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:170(para)
-msgid "Enables cloud administrators to submit commands."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:174(title)
-msgid "Other components"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:175(term)
-msgid "The queue"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:175(para)
-msgid "A central hub for passing messages between daemons. It is usually implemented with <link href=\"http://www.rabbitmq.com/\">RabbitMQ</link>, but could be any AMQP message queue, such as <link href=\"http://qpid.apache.org/\">Apache Qpid</link> or <link href=\"http://www.zeromq.org/\">Zero MQ</link>."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:183(term)
-msgid "SQL database"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:184(para)
-msgid "Stores most build-time and runtime states for a cloud infrastructure. It includes instance types that are available for use, instances in use, available networks, and projects. Theoretically, OpenStack Compute can support any database that is supported by SQL-Alchemy. Note the databases which are widely used are SQLite3 databases (for test and development work), MySQL, and PostgreSQL."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml:192(para)
-msgid "OpenStack Compute interacts with OpenStack Identity for authentication; OpenStack Image Service for images; and the OpenStack dashboard for a web interface."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-console.xml:5(title)
-msgid "Configure remote console access"
-msgstr ""
-
-#. <?dbhtml stop-chunking?>
-#: ./doc/common/section_compute-configure-console.xml:7(para)
-msgid "To provide a remote console or remote desktop access to guest virtual machines, use VNC or SPICE HTML5 through either the OpenStack dashboard or the command line. Best practice is to select one or the other to run."
-msgstr ""
-
-#: ./doc/common/section_xapi-resize-setup.xml:7(title)
-msgid "Modify Dom0 for resize/migration support"
-msgstr ""
-
-#: ./doc/common/section_xapi-resize-setup.xml:8(para)
-msgid "To resize servers with XenServer and XCP, you must:"
-msgstr ""
-
-#: ./doc/common/section_xapi-resize-setup.xml:11(para)
-msgid "Establish a root trust between all hypervisor nodes of your deployment:"
-msgstr ""
-
-#: ./doc/common/section_xapi-resize-setup.xml:13(para)
-msgid "To do so, generate an ssh key-pair with the <placeholder-1/> command. Ensure that each of your dom0's <filename>authorized_keys</filename> file (located in <filename>/root/.ssh/authorized_keys</filename>) contains the public key fingerprint (located in <filename>/root/.ssh/id_rsa.pub</filename>)."
-msgstr ""
-
-#: ./doc/common/section_xapi-resize-setup.xml:22(para)
-msgid "Provide an <filename>/images</filename> mount point to the dom0 for your hypervisor:"
-msgstr ""
-
-#: ./doc/common/section_xapi-resize-setup.xml:24(para)
-msgid "Dom0 space is at a premium so creating a directory in dom0 is potentially dangerous and likely to fail especially when you resize large servers. The least you can do is to symlink <filename>/images</filename> to your local storage SR. The following instructions work for an English-based installation of XenServer (and XCP) and in the case of ext3-based SR (with which the resize functionality is known to work correctly)."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_sshkeys.xml:6(title)
-msgid "Add keypair"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_sshkeys.xml:7(para)
-msgid "Create at least one keypair for each project. If you have generated a keypair with an external tool, you can import it into OpenStack. The keypair can be used for multiple instances that belong to a project."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_sshkeys.xml:13(para)
-msgid "Create a key."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_sshkeys.xml:14(para)
-msgid "To create a <literal>mykey</literal> key that you can associate with instances, run the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_sshkeys.xml:17(para)
-msgid "Save the <filename>mykey.pem</filename> file to a secure location. It enables root access to any instances with which the <literal>mykey</literal> key is associated."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_sshkeys.xml:22(para)
-msgid "Alternatively, you can import a keypair."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_sshkeys.xml:23(para)
-msgid "To import an existing public key, <literal>mykey.pub</literal>, and associate it with the <literal>mykey</literal> key, run the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_sshkeys.xml:28(para)
-msgid "You must have the matching private key to access instances that are associated with this key."
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-https.xml:4(title)
-msgid "Configure the dashboard for HTTPS"
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-https.xml:5(para) ./doc/common/section_dashboard-configure.xml:10(para)
-msgid "You can configure the dashboard for a secured HTTPS deployment. While the standard installation uses a non-encrypted HTTP channel, you can enable SSL support for the dashboard."
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-https.xml:9(para)
-msgid "The following example uses the domain, \"http://openstack.example.com.\" Use a domain that fits your current setup."
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-https.xml:13(para)
-msgid "In<filename>/etc/openstack-dashboard/local_settings.py</filename> update the following directives:"
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-https.xml:19(para)
-msgid "The first option is required to enable HTTPS. The other recommended settings defend against cross-site scripting and require HTTPS."
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-https.xml:24(para)
-msgid "Edit <filename>/etc/apache2/ports.conf</filename> and add the following line:"
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-https.xml:30(para)
-msgid "Edit <filename>/etc/apache2/conf.d/openstack-dashboard.conf:</filename>"
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-https.xml:33(para)
-msgid "Before:"
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-https.xml:46(para)
-msgid "After:"
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-https.xml:87(para)
-msgid "In this configuration, Apache http server listens on the port 443 and redirects all the hits to the HTTPS protocol for all the non-secured requests. The secured section defines the private key, public key, and certificate to use."
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-https.xml:94(para)
-msgid "Restart Apache http server. For Debian/Ubuntu/SUSE:"
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-https.xml:96(para)
-msgid "Or for Fedora/RHEL/CentOS:"
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-https.xml:98(para) ./doc/common/section_dashboard-configure-http.xml:32(para)
-msgid "Next, restart memcached:"
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-https.xml:100(para)
-msgid "If you try to access the dashboard through HTTP, the browser redirects you to the HTTPS page."
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_getstart_logical_arch.xml:38(None)
-msgid "@@image: 'figures/openstack-arch-havana-logical-v1.jpg'; md5=e7acaaee72722626b045eda3fae81841"
-msgstr ""
-
-#: ./doc/common/section_getstart_logical_arch.xml:5(title) ./doc/common/section_getstart_logical_arch.xml:33(title)
-msgid "Logical architecture"
-msgstr ""
-
-#: ./doc/common/section_getstart_logical_arch.xml:6(para)
-msgid "To design, deploy, and configure OpenStack, administrators must understand the logical architecture."
-msgstr ""
-
-#: ./doc/common/section_getstart_logical_arch.xml:7(para)
-msgid "OpenStack modules are one of the following types:"
-msgstr ""
-
-#: ./doc/common/section_getstart_logical_arch.xml:9(term)
-msgid "Daemon"
-msgstr ""
-
-#: ./doc/common/section_getstart_logical_arch.xml:11(para)
-msgid "Runs as a background process. On Linux platforms, a daemon is usually installed as a service."
-msgstr ""
-
-#: ./doc/common/section_getstart_logical_arch.xml:15(term)
-msgid "Script"
-msgstr ""
-
-#: ./doc/common/section_getstart_logical_arch.xml:17(para)
-msgid "Installs a virtual environment and runs tests. For example, the <code>run_tests.sh</code> script installs a virtual environment and runs unit tests on a service."
-msgstr ""
-
-#: ./doc/common/section_getstart_logical_arch.xml:21(term)
-msgid "Command-line interface (CLI)"
-msgstr ""
-
-#: ./doc/common/section_getstart_logical_arch.xml:23(para)
-msgid "Enables users to submit API calls to OpenStack services through easy-to-use commands."
-msgstr ""
-
-#: ./doc/common/section_getstart_logical_arch.xml:29(para)
-msgid "The following diagram shows the most common, but not the only, architecture for an OpenStack cloud:"
-msgstr ""
-
-#: ./doc/common/section_getstart_logical_arch.xml:42(para)
-msgid "As in <xref linkend=\"concept_arch\"/>, end users can interact through the dashboard, CLIs, and APIs. All services authenticate through a common Identity Service and individual services interact with each other through public APIs, except where privileged administrator commands are necessary."
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_keystone-concepts.xml:120(None) ./doc/common/section_keystone-concepts.xml:125(None)
-msgid "@@image: 'figures/SCH_5002_V00_NUAC-Keystone.png'; md5=734714c50c99fc1d74bdfd9f9cd049a6"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts.xml:7(title)
-msgid "OpenStack Identity concepts"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts.xml:8(para)
-msgid "The OpenStack<glossterm>Identity Service</glossterm> performs the following functions:"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts.xml:12(para)
-msgid "Tracking users and their permissions."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts.xml:15(para)
-msgid "Providing a catalog of available services with their API endpoints."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts.xml:19(para)
-msgid "To understand OpenStack Identity, you must understand the following concepts:"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts.xml:23(term)
-msgid "User"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts.xml:25(para)
-msgid "Digital representation of a person, system, or service who uses OpenStack cloud services. The Identity service validates that incoming requests are made by the user who claims to be making the call. Users have a login and may be assigned tokens to access resources. Users can be directly assigned to a particular tenant and behave as if they are contained in that tenant."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts.xml:36(term)
-msgid "Credentials"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts.xml:38(para)
-msgid "Data that confirms the user's identity. For example, user name and password; user name and API key; or an authentication token provided by the Identity Service."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts.xml:45(term)
-msgid "Authentication"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts.xml:47(para)
-msgid "The process of confirming the identity of a user. OpenStack Identity confirms an incoming request by validating a set of credentials supplied by the user."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts.xml:51(para)
-msgid "These credentials are initially a user name and password; or a user name and API key. When user credentials are validated, OpenStack Identity issues an authentication token which the user provides in subsequent requests."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts.xml:59(term)
-msgid "Token"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts.xml:61(para)
-msgid "An arbitrary bit of text that is used to access resources. Each token has information which defines access to resources. A token may be revoked at any time and is valid for a finite duration."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts.xml:65(para)
-msgid "While OpenStack Identity supports token-based authentication in this release, the intention is to support additional protocols in the future. Its main purpose is to be an integration service, and not aspire to be a full-fledged identity store and management solution."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts.xml:74(term)
-msgid "Tenant"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts.xml:76(para)
-msgid "A container used to group or isolate resources and/or identity objects. Depending on the service operator, a tenant may map to a customer, account, organization, or project."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts.xml:85(para)
-msgid "An OpenStack service, such as Compute (nova), Object Storage (swift), or Image Service (glance). It provides one or more endpoints through which users can access resources and perform operations."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts.xml:92(term)
-msgid "Endpoint"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts.xml:94(para)
-msgid "A network-accessible address where you access a service, usually a URL address. If you are using an extension for templates, an endpoint template can be created, which represents the templates of all the consumable services that are available across the regions."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts.xml:102(term)
-msgid "Role"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts.xml:104(para)
-msgid "A personality with a defined set of user rights and privileges to perform a specific set of operations."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts.xml:106(para)
-msgid "In the Identity service, a token that is issued to a user includes the list of roles. Services that are being called by that user determine how they interpret the set of roles a user has and to which operations or resources each role grants access."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts.xml:114(para)
-msgid "The following diagram shows the OpenStack Identity process flow:"
-msgstr ""
-
-#: ./doc/common/section_kvm_enable.xml:6(title)
-msgid "Enable KVM"
-msgstr ""
-
-#: ./doc/common/section_kvm_enable.xml:7(para)
-msgid "To perform these steps, you must be logged in as the <systemitem>root</systemitem> user."
-msgstr ""
-
-#: ./doc/common/section_kvm_enable.xml:11(para)
-msgid "To determine whether the <literal>svm</literal> or <literal>vmx</literal> CPU extensions are present, run this command:"
-msgstr ""
-
-#: ./doc/common/section_kvm_enable.xml:15(para)
-msgid "This command generates output if the CPU is hardware-virtualization capable. Even if output is shown, you might still need to enable virtualization in the system BIOS for full support."
-msgstr ""
-
-#: ./doc/common/section_kvm_enable.xml:19(para)
-msgid "If no output appears, consult your system documentation to ensure that your CPU and motherboard support hardware virtualization. Verify that any relevant hardware virtualization options are enabled in the system BIOS."
-msgstr ""
-
-#: ./doc/common/section_kvm_enable.xml:24(para)
-msgid "The BIOS for each manufacturer is different. If you must enable virtualization in the BIOS, look for an option containing the words <literal>virtualization</literal>, <literal>VT</literal>, <literal>VMX</literal>, or <literal>SVM</literal>."
-msgstr ""
-
-#: ./doc/common/section_kvm_enable.xml:32(para)
-msgid "To list the loaded kernel modules and verify that the <literal>kvm</literal> modules are loaded, run this command:"
-msgstr ""
-
-#: ./doc/common/section_kvm_enable.xml:36(para)
-msgid "If the output includes <systemitem>kvm_intel</systemitem> or <systemitem>kvm_amd</systemitem>, the <systemitem>kvm</systemitem> hardware virtualization modules are loaded and your kernel meets the module requirements for OpenStack Compute."
-msgstr ""
-
-#: ./doc/common/section_kvm_enable.xml:43(para)
-msgid "If the output does not show that the <literal>kvm</literal> module is loaded, run this command to load it:"
-msgstr ""
-
-#: ./doc/common/section_kvm_enable.xml:47(para)
-msgid "Run the command for your CPU. For Intel, run this command:"
-msgstr ""
-
-#: ./doc/common/section_kvm_enable.xml:50(para)
-msgid "For AMD, run this command:"
-msgstr ""
-
-#: ./doc/common/section_kvm_enable.xml:52(para)
-msgid "Because a KVM installation can change user group membership, you might need to log in again for changes to take effect."
-msgstr ""
-
-#: ./doc/common/section_kvm_enable.xml:55(para)
-msgid "If the kernel modules do not load automatically, use the procedures listed in these subsections."
-msgstr ""
-
-#: ./doc/common/section_kvm_enable.xml:59(para)
-msgid "If the checks indicate that required hardware virtualization support or kernel modules are disabled or unavailable, you must either enable this support on the system or find a system with this support."
-msgstr ""
-
-#: ./doc/common/section_kvm_enable.xml:64(para)
-msgid "Some systems require that you enable VT support in the system BIOS. If you believe your processor supports hardware acceleration but the previous command did not produce output, reboot your machine, enter the system BIOS, and enable the VT option."
-msgstr ""
-
-#: ./doc/common/section_kvm_enable.xml:70(para)
-msgid "If KVM acceleration is not supported, configure Compute to use a different hypervisor, such as <link href=\"http://docs.openstack.org/trunk/config-reference/content/qemu.html\">QEMU</link> or <link href=\"http://docs.openstack.org/trunk/config-reference/content/introduction-to-xen.html\">Xen</link>."
-msgstr ""
-
-#: ./doc/common/section_kvm_enable.xml:76(para)
-msgid "These procedures help you load the kernel modules for Intel-based and AMD-based processors if they do not load automatically during KVM installation."
-msgstr ""
-
-#: ./doc/common/section_kvm_enable.xml:80(title)
-msgid "Intel-based processors"
-msgstr ""
-
-#: ./doc/common/section_kvm_enable.xml:81(para)
-msgid "If your compute host is Intel-based, run these commands as root to load the kernel modules:"
-msgstr ""
-
-#: ./doc/common/section_kvm_enable.xml:85(para)
-msgid "Add these lines to the <filename>/etc/modules</filename> file so that these modules load on reboot:"
-msgstr ""
-
-#: ./doc/common/section_kvm_enable.xml:91(title)
-msgid "AMD-based processors"
-msgstr ""
-
-#: ./doc/common/section_kvm_enable.xml:92(para)
-msgid "If your compute host is AMD-based, run these commands as root to load the kernel modules:"
-msgstr ""
-
-#: ./doc/common/section_kvm_enable.xml:96(para)
-msgid "Add these lines to <filename>/etc/modules</filename> file so that these modules load on reboot:"
-msgstr ""
-
-#: ./doc/common/section_xapi-install-plugins.xml:7(title)
-msgid "Install the XenAPI plug-ins"
-msgstr ""
-
-#: ./doc/common/section_xapi-install-plugins.xml:8(para)
-msgid "When you use Xen as the hypervisor for OpenStack Compute, you can install a Python script (or any executable) on the host side, and call that through the XenAPI. These scripts are called plug-ins. The XenAPI plug-ins live in the nova code repository. These plug-ins have to be copied to the Dom0 for the hypervisor, to the appropriate directory, where xapi can find them. There are several options for the installation. The important thing is to ensure that the version of the plug-ins are in line with the nova installation by only installing plug-ins from a matching nova repository."
-msgstr ""
-
-#: ./doc/common/section_xapi-install-plugins.xml:19(title)
-msgid "Manually install the plug-in"
-msgstr ""
-
-#: ./doc/common/section_xapi-install-plugins.xml:22(para)
-msgid "Create temporary files/directories:"
-msgstr ""
-
-#: ./doc/common/section_xapi-install-plugins.xml:27(para)
-msgid "Get the source from github. The example assumes the master branch is used. Amend the URL to match the version being used:"
-msgstr ""
-
-#: ./doc/common/section_xapi-install-plugins.xml:32(para)
-msgid "(Alternatively) To use the official Ubuntu packages, use the following commands to get the nova code base:"
-msgstr ""
-
-#: ./doc/common/section_xapi-install-plugins.xml:39(para)
-msgid "Copy the plug-ins to the hypervisor:"
-msgstr ""
-
-#: ./doc/common/section_xapi-install-plugins.xml:44(para)
-msgid "Remove the temporary files/directories:"
-msgstr ""
-
-#: ./doc/common/section_xapi-install-plugins.xml:51(title)
-msgid "Package a XenServer supplemental pack"
-msgstr ""
-
-#: ./doc/common/section_xapi-install-plugins.xml:52(para)
-msgid "Follow these steps to produce a supplemental pack from the nova sources, and package it as a XenServer supplemental pack."
-msgstr ""
-
-#: ./doc/common/section_xapi-install-plugins.xml:57(para)
-msgid "Create RPM packages. Given you have the nova sources. Use one of the methods in <xref linkend=\"manual_install\"/>:"
-msgstr ""
-
-#: ./doc/common/section_xapi-install-plugins.xml:62(para)
-msgid "These commands leave an <filename>.rpm</filename> file in the <filename>rpmbuild/RPMS/noarch/</filename> directory."
-msgstr ""
-
-#: ./doc/common/section_xapi-install-plugins.xml:68(para)
-msgid "Pack the RPM packages to a Supplemental Pack, using the XenServer DDK (the following command should be issued on the XenServer DDK virtual appliance, after the produced rpm file has been copied over):"
-msgstr ""
-
-#: ./doc/common/section_xapi-install-plugins.xml:81(para)
-msgid "This command produces an <filename>.iso</filename> file in the output directory specified. Copy that file to the hypervisor."
-msgstr ""
-
-#: ./doc/common/section_xapi-install-plugins.xml:87(para)
-msgid "Install the Supplemental Pack. Log in to the hypervisor, and issue:"
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-vnc-window.xml:6(title)
-msgid "Change the size of the dashboard VNC window"
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-vnc-window.xml:7(para)
-msgid "The <filename>_detail_vnc.html</filename> file defines the size of the VNC window. To change the window size, edit this file."
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-vnc-window.xml:12(para)
-msgid "Edit <filename>/usr/share/pyshared/horizon/dashboards/nova/instances/templates/instances/_detail_vnc.html.</filename>"
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-vnc-window.xml:16(para)
-msgid "Modify the <literal>width</literal> and <literal>height</literal> parameters, as follows:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_fileinjection.xml:10(title)
-msgid "Inject files into instances"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_fileinjection.xml:11(para)
-msgid "You can inject local files into the instance file system when you launch an instance."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_fileinjection.xml:13(para)
-msgid "Use the <parameter>--file dst-path=src-path</parameter> parameter on the nova <placeholder-1/> command."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_fileinjection.xml:15(para)
-msgid "You can inject up to five files."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_fileinjection.xml:16(para)
-msgid "For example, you might inject the <filename>special_authorized_keysfile</filename> file into the instance rather than using the regular ssh key injection."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_fileinjection.xml:19(para)
-msgid "Run the following command:<placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:7(title)
-msgid "Certificates for PKI"
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:8(para)
-msgid "PKI stands for Public Key Infrastructure. Tokens are documents, cryptographically signed using the X509 standard. In order to work correctly token generation requires a public/private key pair. The public key must be signed in an X509 certificate, and the certificate used to sign it must be available as Certificate Authority (CA) certificate. These files can be generated either using the <placeholder-1/> utility, or externally generated. The files need to be in the locations specified by the top level Identity Service configuration file <filename>keystone.conf</filename> as specified in the above section. Additionally, the private key should only be readable by the system user that will run the Identity Service."
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:23(para)
-msgid "The certificates can be world readable, but the private key cannot be. The private key should only be readable by the account that is going to sign tokens. When generating files with the <placeholder-1/> command, your best option is to run as the pki user. If you run nova-manage as root, you can append --keystone-user and --keystone-group parameters to set the username and group keystone is going to run under."
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:33(para)
-msgid "The values that specify where to read the certificates are under the <literal>[signing]</literal> section of the configuration file. The configuration values are:"
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:38(para)
-msgid "<literal>token_format</literal> - Determines the algorithm used to generate tokens. Can be either <literal>UUID</literal> or <literal>PKI</literal>. Defaults to <literal>PKI</literal>."
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:45(para)
-msgid "<literal>certfile</literal> - Location of certificate used to verify tokens. Default is <literal>/etc/keystone/ssl/certs/signing_cert.pem</literal>."
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:51(para)
-msgid "<literal>keyfile</literal> - Location of private key used to sign tokens. Default is <literal>/etc/keystone/ssl/private/signing_key.pem</literal>."
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:57(para)
-msgid "<literal>ca_certs</literal> - Location of certificate for the authority that issued the above certificate. Default is <literal>/etc/keystone/ssl/certs/ca.pem</literal>."
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:64(para)
-msgid "<literal>key_size</literal> - Default is <literal>1024</literal>."
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:69(para)
-msgid "<literal>valid_days</literal> - Default is <literal>3650</literal>."
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:74(para)
-msgid "<literal>ca_password</literal> - Password required to read the <literal>ca_file</literal>. Default is <literal>None</literal>."
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:80(para)
-msgid "If <literal>token_format=UUID</literal>, a typical token looks like <literal>53f7f6ef0cc344b5be706bcc8b1479e1</literal>. If <literal>token_format=PKI</literal>, a typical token is a much longer string, such as:"
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:113(title)
-msgid "Sign certificate issued by external CA"
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:114(para)
-msgid "You can use a signing certificate issued by an external CA instead of generated by <placeholder-1/>. However, a certificate issued by an external CA must satisfy the following conditions:"
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:121(para)
-msgid "all certificate and key files must be in Privacy Enhanced Mail (PEM) format"
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:125(para)
-msgid "private key files must not be protected by a password"
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:129(para)
-msgid "When using signing certificate issued by an external CA, you do not need to specify <literal>key_size</literal>, <literal>valid_days</literal>, and <literal>ca_password</literal> as they will be ignored."
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:134(para)
-msgid "The basic workflow for using a signing certificate issued by an external CA involves:"
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:138(para)
-msgid "Request Signing Certificate from External CA"
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:142(para)
-msgid "Convert certificate and private key to PEM if needed"
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:146(para)
-msgid "Install External Signing Certificate"
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:151(title)
-msgid "Request a signing certificate from an external CA"
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:153(para)
-msgid "One way to request a signing certificate from an external CA is to first generate a PKCS #10 Certificate Request Syntax (CRS) using OpenSSL CLI."
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:156(para)
-msgid "Create a certificate request configuration file. For example, create the <filename>cert_req.conf</filename> file, as follows:"
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:176(para)
-msgid "Then generate a CRS with OpenSSL CLI. <emphasis role=\"strong\">Do not encrypt the generated private key. Must use the -nodes option.</emphasis>"
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:183(para)
-msgid "If everything is successful, you should end up with <filename>signing_cert_req.pem</filename> and <filename>signing_key.pem</filename>. Send <filename>signing_cert_req.pem</filename> to your CA to request a token signing certificate and make sure to ask the certificate to be in PEM format. Also, make sure your trusted CA certificate chain is also in PEM format."
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:193(title)
-msgid "Install an external signing certificate"
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:194(para)
-msgid "Assuming you have the following already:"
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:197(para)
-msgid "<filename>signing_cert.pem</filename> - (Keystone token) signing certificate in PEM format"
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:202(para)
-msgid "<filename>signing_key.pem</filename> - corresponding (non-encrypted) private key in PEM format"
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:208(para)
-msgid "<filename>cacert.pem</filename> - trust CA certificate chain in PEM format"
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:213(para)
-msgid "Copy the above to your certificate directory. For example:"
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:221(para)
-msgid "Make sure the certificate directory is only accessible by root."
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml:224(para)
-msgid "If your certificate directory path is different from the default <filename>/etc/keystone/ssl/certs</filename>, make sure it is reflected in the <literal>[signing]</literal> section of the configuration file."
+#: ./doc/common/ch_cli_ceilometer_commands.xml:1887(para)
+msgid "The name of the trait to list. Required."
 msgstr ""
 
 #: ./doc/common/ch_cli_cinder_commands.xml:11(title)
@@ -11509,4932 +11623,388 @@ msgstr ""
 msgid "Optional type for disk format (Default=raw)"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:7(title) ./doc/common/section_dashboard_access.xml:304(guilabel)
-msgid "Flavors"
+#: ./doc/common/section_cli_glance_manage_images.xml:7(title)
+msgid "Manage images"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:8(para)
-msgid "Admin users can use the <placeholder-1/> commands to customize and manage flavors. To see the available flavor-related commands, run:"
+#: ./doc/common/section_cli_glance_manage_images.xml:8(para)
+msgid "The cloud operator assigns roles to users. Roles determine who can upload and manage images. The operator might restrict image upload and management to only cloud administrators or operators."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:22(para)
-msgid "Configuration rights can be delegated to additional users by redefining the access controls for <option>compute_extension:flavormanage</option> in <filename>/etc/nova/policy.json</filename> on the <systemitem class=\"server\">nova-api</systemitem> server."
+#: ./doc/common/section_cli_glance_manage_images.xml:12(para)
+msgid "You can upload images through the <placeholder-1/> client or the Image Service API. You can also use the <placeholder-2/> client to list images, set and delete image metadata, delete images, and take a snapshot of a running instance to create an image. After you upload an image, you cannot change it."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:26(para)
-msgid "To modify an existing flavor in the dashboard, you must delete the flavor and create a modified one with the same name."
+#: ./doc/common/section_cli_glance_manage_images.xml:16(para)
+msgid "For details about image creation, see the <link href=\"http://docs.openstack.org/image-guide/content/\"><citetitle>Virtual Machine Image Guide</citetitle></link>."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:31(para)
-msgid "Flavors define these elements:"
+#: ./doc/common/section_cli_glance_manage_images.xml:21(title)
+msgid "List or get details for images (glance)"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:33(caption)
-msgid "Identity Service configuration file sections"
+#: ./doc/common/section_cli_glance_manage_images.xml:22(para)
+msgid "To get a list of images and to then get further details about a single image, use <placeholder-1/> and <placeholder-2/>."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:39(td)
-msgid "Element"
+#: ./doc/common/section_cli_glance_manage_images.xml:74(para)
+msgid "When viewing a list of images, you can also use <placeholder-1/> to filter the list, as follows:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:45(literal)
-msgid "Name"
+#: ./doc/common/section_cli_glance_manage_images.xml:80(para)
+msgid "To store location metadata for images, which enables direct file access for a client, update the <filename>/etc/glance/glance.conf</filename> file with the following statements:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:47(replaceable)
-msgid "XX"
+#: ./doc/common/section_cli_glance_manage_images.xml:87(code)
+msgid "show_multiple_locations = True"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:47(replaceable)
-msgid "SIZE_NAME"
+#: ./doc/common/section_cli_glance_manage_images.xml:90(para)
+msgid "<code>filesystem_store_metadata_file = <replaceable>filePath</replaceable></code>, where <replaceable>filePath</replaceable> points to a JSON file that defines the mount point for OpenStack images on your system and a unique ID. For example: <placeholder-1/>"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:46(td)
-msgid "A descriptive name. <placeholder-1/>.<placeholder-2/> is typically not required, though some third party tools may rely on it."
+#: ./doc/common/section_cli_glance_manage_images.xml:102(para)
+msgid "After you restart the Image Service, you can use the following syntax to view the image's location information:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:52(literal)
-msgid "Memory_MB"
+#: ./doc/common/section_cli_glance_manage_images.xml:103(replaceable)
+msgid "imageID"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:53(td)
-msgid "Virtual machine memory in megabytes."
+#: ./doc/common/section_cli_glance_manage_images.xml:104(para)
+msgid "For example, using the image ID shown above, you would issue the command as follows:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:56(literal)
-msgid "Disk"
+#: ./doc/common/section_cli_glance_manage_images.xml:109(title)
+msgid "Create or update an image (glance)"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:57(td)
-msgid "Virtual root disk size in gigabytes. This is an ephemeral disk that the base image is copied into. When booting from a persistent volume it is not used. The \"0\" size is a special case which uses the native base image size as the size of the ephemeral root volume."
+#: ./doc/common/section_cli_glance_manage_images.xml:110(para)
+msgid "To create an image, use <placeholder-1/>:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:65(literal)
-msgid "Ephemeral"
+#: ./doc/common/section_cli_glance_manage_images.xml:111(replaceable) ./doc/common/section_cli_glance_manage_images.xml:114(replaceable)
+msgid "imageName"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:66(td)
-msgid "Specifies the size of a secondary ephemeral data disk. This is an empty, unformatted disk and exists only for the life of the instance."
+#: ./doc/common/section_cli_glance_manage_images.xml:112(para)
+msgid "To update an image by name or ID, use <placeholder-1/>:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:71(literal)
-msgid "Swap"
+#: ./doc/common/section_cli_glance_manage_images.xml:116(para)
+msgid "The following table lists the optional arguments that you can use with the <placeholder-1/> and <placeholder-2/> commands to modify image properties. For more information, refer to Image Service chapter in the <link href=\"http://docs.openstack.org/cli-reference/content/index.html\">OpenStack Command-Line Interface Reference</link>."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:72(td)
-msgid "Optional swap space allocation for the instance."
+#: ./doc/common/section_cli_glance_manage_images.xml:126(parameter)
+msgid "--name NAME"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:76(literal)
-msgid "VCPUs"
+#: ./doc/common/section_cli_glance_manage_images.xml:129(para)
+msgid "The name of the image."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:77(td)
-msgid "Number of virtual CPUs presented to the instance."
+#: ./doc/common/section_cli_glance_manage_images.xml:134(parameter)
+msgid "--disk-format DISK_FORMAT"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:81(literal)
-msgid "RXTX_Factor"
+#: ./doc/common/section_cli_glance_manage_images.xml:137(para)
+msgid "The disk format of the image. Acceptable formats are ami, ari, aki, vhd, vmdk, raw, qcow2, vdi, and iso."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:82(td)
-msgid "Optional property allows created servers to have a different bandwidth cap than that defined in the network they are attached to. This factor is multiplied by the rxtx_base property of the network. Default value is 1.0. That is, the same as attached network."
+#: ./doc/common/section_cli_glance_manage_images.xml:143(parameter)
+msgid "--container-format CONTAINER_FORMAT"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:90(literal)
-msgid "Is_Public"
+#: ./doc/common/section_cli_glance_manage_images.xml:146(para)
+msgid "The container format of the image. Acceptable formats are ami, ari, aki, bare, and ovf."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:91(td)
-msgid "Boolean value, whether flavor is available to all users or private to the tenant it was created in. Defaults to True."
+#: ./doc/common/section_cli_glance_manage_images.xml:152(parameter)
+msgid "--owner TENANT_ID"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:96(literal)
-msgid "extra_specs"
+#: ./doc/common/section_cli_glance_manage_images.xml:155(para)
+msgid "The tenant who should own the image."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:97(para)
-msgid "Key and value pairs that define on which compute nodes a flavor can run. These pairs must match corresponding pairs on the compute nodes. Use to implement special resources, such as flavors that run on only compute nodes with GPU hardware."
+#: ./doc/common/section_cli_glance_manage_images.xml:160(parameter)
+msgid "--size SIZE"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:105(para)
-msgid "Flavor customization can be limited by the hypervisor in use. For example the <systemitem>libvirt</systemitem> driver enables quotas on CPUs available to a VM, disk tuning, bandwidth I/O, watchdog behavior, random number generator device control, and instance VIF traffic control."
+#: ./doc/common/section_cli_glance_manage_images.xml:163(para)
+msgid "The size of image data, in bytes."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:110(term)
-msgid "CPU limits"
+#: ./doc/common/section_cli_glance_manage_images.xml:168(parameter)
+msgid "--min-disk DISK_GB"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:111(para)
-msgid "You can configure the CPU limits with control parameters with the <placeholder-1/> client. For example, to configure the I/O limit, use:"
+#: ./doc/common/section_cli_glance_manage_images.xml:171(para)
+msgid "The minimum size of the disk needed to boot the image, in gigabytes."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:115(para)
-msgid "There are optional CPU control parameters for weight shares, enforcement intervals for runtime quotas, and a quota for maximum allowed bandwidth:"
+#: ./doc/common/section_cli_glance_manage_images.xml:177(parameter)
+msgid "--min-ram DISK_RAM"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:121(para)
-msgid "<literal>cpu_shares</literal> specifies the proportional weighted share for the domain. If this element is omitted, the service defaults to the OS provided defaults. There is no unit for the value; it is a relative measure based on the setting of other VMs. For example, a VM configured with value 2048 gets twice as much CPU time as a VM configured with value 1024."
+#: ./doc/common/section_cli_glance_manage_images.xml:180(para)
+msgid "The minimum amount of RAM needed to boot the image, in megabytes."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:130(para)
-msgid "<literal>cpu_period</literal> specifies the enforcement interval (unit: microseconds) for QEMU and LXC hypervisors. Within a period, each VCPU of the domain is not allowed to consume more than the quota worth of runtime. The value should be in range <literal>[1000, 1000000]</literal>. A period with value 0 means no value."
+#: ./doc/common/section_cli_glance_manage_images.xml:185(parameter)
+msgid "--location IMAGE_URL"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:138(para)
-msgid "<literal>cpu_quota</literal> specifies the maximum allowed bandwidth (unit: microseconds). A domain with a negative-value quota indicates that the domain has infinite bandwidth, which means that it is not bandwidth controlled. The value should be in range <literal>[1000, 18446744073709551]</literal> or less than 0. A quota with value 0 means no value. You can use this feature to ensure that all vCPUs run at the same speed. For example:"
+#: ./doc/common/section_cli_glance_manage_images.xml:188(para)
+msgid "The URL where the data for this image resides. For example, if the image data is stored in swift, you could specify <literal>swift://account:key@example.com/container/obj</literal>."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:147(para)
-msgid "In this example, the instance of <literal>m1.low_cpu</literal> can only consume a maximum of 50% CPU of a physical CPU computing capability."
+#: ./doc/common/section_cli_glance_manage_images.xml:195(parameter)
+msgid "--file FILE"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:155(term)
-msgid "Disk tuning"
+#: ./doc/common/section_cli_glance_manage_images.xml:198(para)
+msgid "Local file that contains the disk image to be uploaded during the update. Alternatively, you can pass images to the client through stdin."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:156(para)
-msgid "Using disk I/O quotas, you can set maximum disk write to 10 MB per second for a VM user. For example:"
+#: ./doc/common/section_cli_glance_manage_images.xml:204(parameter)
+msgid "--checksum CHECKSUM"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:159(para)
-msgid "The disk I/O options are:"
+#: ./doc/common/section_cli_glance_manage_images.xml:207(para)
+msgid "Hash of image data to use for verification."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:162(para)
-msgid "disk_read_bytes_sec"
+#: ./doc/common/section_cli_glance_manage_images.xml:212(parameter)
+msgid "--copy-from IMAGE_URL"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:165(para)
-msgid "disk_read_iops_sec"
+#: ./doc/common/section_cli_glance_manage_images.xml:215(para)
+msgid "Similar to <parameter>--location</parameter> in usage, but indicates that the image server should immediately copy the data and store it in its configured image store."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:168(para)
-msgid "disk_write_bytes_sec"
+#: ./doc/common/section_cli_glance_manage_images.xml:222(parameter)
+msgid "--is-public [True|False]"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:171(para)
-msgid "disk_write_iops_sec"
+#: ./doc/common/section_cli_glance_manage_images.xml:225(para)
+msgid "Makes an image accessible for all the tenants."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:174(para)
-msgid "disk_total_bytes_sec"
+#: ./doc/common/section_cli_glance_manage_images.xml:230(parameter)
+msgid "--is-protected [True|False]"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:177(para)
-msgid "disk_total_iops_sec"
+#: ./doc/common/section_cli_glance_manage_images.xml:233(para)
+msgid "Prevents an image from being deleted."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:180(para)
-msgid "The vif I/O options are:"
+#: ./doc/common/section_cli_glance_manage_images.xml:238(parameter)
+msgid "--property KEY=VALUE"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:183(para)
-msgid "vif_inbound_ average"
+#: ./doc/common/section_cli_glance_manage_images.xml:241(para)
+msgid "Arbitrary property to associate with image. This option can be used multiple times."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:186(para)
-msgid "vif_inbound_burst"
+#: ./doc/common/section_cli_glance_manage_images.xml:247(parameter)
+msgid "--purge-props"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:189(para)
-msgid "vif_inbound_peak"
+#: ./doc/common/section_cli_glance_manage_images.xml:250(para)
+msgid "Deletes all image properties that are not explicitly set in the update request. Otherwise, those properties not referenced are preserved."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:192(para)
-msgid "vif_outbound_ average"
+#: ./doc/common/section_cli_glance_manage_images.xml:256(parameter)
+msgid "--human-readable"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:195(para)
-msgid "vif_outbound_burst"
+#: ./doc/common/section_cli_glance_manage_images.xml:259(para)
+msgid "Prints the image size in a human-friendly format."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:198(para)
-msgid "vif_outbound_peak"
+#: ./doc/common/section_cli_glance_manage_images.xml:263(para)
+msgid "The following example shows the command that you would use to upload a CentOS 6.3 image in qcow2 format and configure it for public access:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:202(term)
-msgid "Bandwidth I/O"
+#: ./doc/common/section_cli_glance_manage_images.xml:267(para)
+msgid "The following example shows how to update an existing image with a properties that describe the disk bus, the CD-ROM bus, and the VIF model:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:203(para)
-msgid "Incoming and outgoing traffic can be shaped independently. The bandwidth element can have at most one inbound and at most one outbound child element. If you leave any of these children element out, no quality of service (QoS) is applied on that traffic direction. So, if you want to shape only the network's incoming traffic, use inbound only (and vice versa). Each element has one mandatory attribute average, which specifies the average bit rate on the interface being shaped."
+#: ./doc/common/section_cli_glance_manage_images.xml:274(para)
+msgid "Currently the libvirt virtualization tool determines the disk, CD-ROM, and VIF device models based on the configured hypervisor type (<literal>libvirt_type</literal> in <filename>/etc/nova/nova.conf</filename>). For the sake of optimal performance, libvirt defaults to using virtio for both disk and VIF (NIC) models. The disadvantage of this approach is that it is not possible to run operating systems that lack virtio drivers, for example, BSD, Solaris, and older versions of Linux and Windows."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:209(para)
-msgid "There are also two optional attributes (integer): <option>peak</option>, which specifies maximum rate at which bridge can send data (kilobytes/second), and <option>burst</option>, the amount of bytes that can be burst at peak speed (kilobytes). The rate is shared equally within domains connected to the network."
+#: ./doc/common/section_cli_glance_manage_images.xml:280(para)
+msgid "If you specify a disk or CD-ROM bus model that is not supported, see <xref linkend=\"bus_models\"/>. If you specify a VIF model that is not supported, the instance fails to launch. See <xref linkend=\"vif_models\"/>."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:214(para)
-msgid "The following example configures a bandwidth limit for instance network traffic:"
+#: ./doc/common/section_cli_glance_manage_images.xml:284(para)
+msgid "The valid model values depend on the <literal>libvirt_type</literal> setting, as shown in the following tables."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:219(term)
-msgid "Watchdog behavior"
+#: ./doc/common/section_cli_glance_manage_images.xml:287(caption)
+msgid "Disk and CD-ROM bus model values"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:220(para)
-msgid "For the <systemitem>libvirt</systemitem> driver, you can enable and set the behavior of a virtual hardware watchdog device for each flavor. Watchdog devices keep an eye on the guest server, and carry out the configured action if the server hangs. The watchdog uses the i6300esb device (emulating a PCI Intel 6300ESB). If <literal>hw_watchdog_action</literal> is not specified, the watchdog is disabled."
+#: ./doc/common/section_cli_glance_manage_images.xml:292(th) ./doc/common/section_cli_glance_manage_images.xml:336(th)
+msgid "libvirt_type setting"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:226(para)
-msgid "To set the behavior, use:"
+#: ./doc/common/section_cli_glance_manage_images.xml:293(th) ./doc/common/section_cli_glance_manage_images.xml:337(th)
+msgid "Supported model values"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:227(replaceable) ./doc/common/section_cli_nova_customize_flavors.xml:257(replaceable) ./doc/common/section_cli_nova_customize_flavors.xml:258(replaceable) ./doc/common/section_cli_nova_customize_flavors.xml:259(replaceable)
-msgid "FLAVOR-NAME"
+#: ./doc/common/section_cli_glance_manage_images.xml:298(td) ./doc/common/section_cli_glance_manage_images.xml:342(td)
+msgid "qemu or kvm"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:227(replaceable)
-msgid "ACTION"
+#: ./doc/common/section_cli_glance_manage_images.xml:303(para) ./doc/common/section_cli_glance_manage_images.xml:320(para)
+msgid "ide"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:228(para)
-msgid "Valid <replaceable>ACTION</replaceable> values are:"
+#: ./doc/common/section_cli_glance_manage_images.xml:306(para)
+msgid "scsi"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:231(para)
-msgid "<literal>disabled</literal>(default) The device is not attached."
+#: ./doc/common/section_cli_glance_manage_images.xml:309(para) ./doc/common/section_cli_glance_manage_images.xml:359(para)
+msgid "virtio"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:234(para)
-msgid "<literal>reset</literal>Forcefully reset the guest."
+#: ./doc/common/section_cli_glance_manage_images.xml:316(td) ./doc/common/section_cli_glance_manage_images.xml:323(para) ./doc/common/section_cli_glance_manage_images.xml:366(td)
+msgid "xen"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:238(para)
-msgid "<literal>poweroff</literal>Forcefully power off the guest."
+#: ./doc/common/section_cli_glance_manage_images.xml:331(caption)
+msgid "VIF model values"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:242(para)
-msgid "<literal>pause</literal>Pause the guest."
+#: ./doc/common/section_cli_glance_manage_images.xml:347(para) ./doc/common/section_cli_glance_manage_images.xml:370(para)
+msgid "e1000"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:245(para)
-msgid "<literal>none</literal>Only enable the watchdog; do nothing if the server hangs."
+#: ./doc/common/section_cli_glance_manage_images.xml:350(para) ./doc/common/section_cli_glance_manage_images.xml:376(para)
+msgid "ne2k_pci"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:249(para)
-msgid "Watchdog behavior set using a specific image's properties will override behavior set using flavors."
+#: ./doc/common/section_cli_glance_manage_images.xml:353(para) ./doc/common/section_cli_glance_manage_images.xml:379(para)
+msgid "pcnet"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:254(term)
-msgid "Random-number generator"
+#: ./doc/common/section_cli_glance_manage_images.xml:356(para) ./doc/common/section_cli_glance_manage_images.xml:382(para)
+msgid "rtl8139"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:255(para)
-msgid "If a random-number generator device has been added to the instance through its image properties, the device can be enabled and configured using:"
+#: ./doc/common/section_cli_glance_manage_images.xml:373(para)
+msgid "netfront"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:258(replaceable)
-msgid "RATE-BYTES"
+#: ./doc/common/section_cli_glance_manage_images.xml:388(td)
+msgid "vmware"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:259(replaceable)
-msgid "RATE-PERIOD"
+#: ./doc/common/section_cli_glance_manage_images.xml:393(para)
+msgid "VirtualE1000"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:263(para)
-msgid "<replaceable>RATE-BYTES</replaceable>(Integer) Allowed amount of bytes that the guest can read from the host's entropy per period."
+#: ./doc/common/section_cli_glance_manage_images.xml:396(para)
+msgid "VirtualPCNet32"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:267(para)
-msgid "<replaceable>RATE-PERIOD</replaceable>(Integer) Duration of the read period in seconds."
+#: ./doc/common/section_cli_glance_manage_images.xml:399(para)
+msgid "VirtualVmxnet"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:273(term)
-msgid "Instance VIF traffic control"
+#: ./doc/common/section_cli_glance_manage_images.xml:411(para)
+msgid "If you encounter problems in creating an image in Image Service or Compute, the following information may help you troubleshoot the creation process."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml:274(para)
-msgid "Flavors can also be assigned to particular projects. By default, a flavor is public and available to all projects. Private flavors are only accessible to those on the access list and are invisible to other projects. To create and assign a private flavor to a project, run these commands:"
+#: ./doc/common/section_cli_glance_manage_images.xml:415(para)
+msgid "Ensure that the version of qemu you are using is version 0.14 or later. Earlier versions of qemu result in an <literal>unknown option -s</literal> error message in the <filename>nova-compute.log</filename> file."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_evacuate.xml:6(title)
-msgid "Evacuate instances"
+#: ./doc/common/section_keystone-external-auth.xml:7(title)
+msgid "External authentication with Identity"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_evacuate.xml:7(para)
-msgid "If a cloud compute node fails due to a hardware malfunction or another reason, you can evacuate instances to make them available again. You can choose evacuation parameters for your use case."
+#: ./doc/common/section_keystone-external-auth.xml:8(para)
+msgid "When Identity runs in <literal>apache-httpd</literal>, you can use external authentication methods that differ from the authentication provided by the identity store back end. For example, you can use an SQL identity back end together with X.509 authentication, Kerberos, and so on instead of using the user name and password combination."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_evacuate.xml:10(para)
-msgid "To preserve user data on server disk, you must configure shared storage on the target host. Also, you must validate that the current VM host is down; otherwise, the evacuation fails with an error."
+#: ./doc/common/section_keystone-external-auth.xml:15(title)
+msgid "Use HTTPD authentication"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_evacuate.xml:15(para)
-msgid "To list hosts and find a different host for the evacuated instance, run:"
+#: ./doc/common/section_keystone-external-auth.xml:16(para)
+msgid "Web servers, like Apache HTTP, support many methods of authentication. Identity can allow the web server to perform the authentication. The web server then passes the authenticated user to Identity by using the <literal>REMOTE_USER</literal> environment variable. This user must already exist in the Identity back end to get a token from the controller. To use this method, Identity should run on <literal>apache-httpd</literal>."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_evacuate.xml:19(para)
-msgid "Evacuate the instance. You can pass the instance password to the command by using the <literal>--password &lt;pwd&gt;</literal> option. If you do not specify a password, one is generated and printed after the command finishes successfully. The following command evacuates a server without shared storage from a host that is down to the specified <replaceable>host_b</replaceable>:"
+#: ./doc/common/section_keystone-external-auth.xml:27(title)
+msgid "Use X.509"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_evacuate.xml:24(replaceable) ./doc/common/section_cli_nova_evacuate.xml:40(replaceable)
-msgid "evacuated_server_name"
+#: ./doc/common/section_keystone-external-auth.xml:28(para)
+msgid "The following Apache configuration snippet authenticates the user based on a valid X.509 certificate from a known CA:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_evacuate.xml:24(replaceable) ./doc/common/section_cli_nova_evacuate.xml:40(replaceable)
-msgid "host_b"
+#: ./doc/common/section_getstart_object-storage.xml:5(title)
+msgid "OpenStack Object Storage"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_evacuate.xml:25(para)
-msgid "The instance is booted from a new disk, but preserves its configuration including its ID, name, uid, IP address, and so on. The command returns a password:"
+#: ./doc/common/section_getstart_object-storage.xml:6(para)
+msgid "The OpenStack Object Storage is a multi-tenant object storage system. It is highly scalable and can manage large amounts of unstructured data at low cost through a RESTful HTTP API."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_evacuate.xml:34(para)
-msgid "To preserve the user disk data on the evacuated server, deploy OpenStack Compute with a shared file system. To configure your system, see <link href=\"http://docs.openstack.org/icehouse/config-reference/content/configuring-openstack-compute-basics.html#section_configuring-compute-migrations\">Configure migrations</link> in <citetitle>OpenStack Configuration Reference</citetitle>. In the following example, the password remains unchanged:"
+#: ./doc/common/section_getstart_object-storage.xml:9(para) ./doc/common/section_getstart_networking.xml:11(para)
+msgid "It includes the following components:"
 msgstr ""
 
-#: ./doc/common/section_cli_cinder_read-only-volumes.xml:6(title)
-msgid "Set a volume to read-only access"
+#: ./doc/common/section_getstart_object-storage.xml:11(term)
+msgid "Proxy servers (<systemitem class=\"service\">swift-proxy-server</systemitem>)"
 msgstr ""
 
-#: ./doc/common/section_cli_cinder_read-only-volumes.xml:7(para)
-msgid "To give multiple users shared, secure access to the same data, you can set a volume to read-only access."
+#: ./doc/common/section_getstart_object-storage.xml:13(para)
+msgid "Accepts OpenStack Object Storage API and raw HTTP requests to upload files, modify metadata, and create containers. It also serves file or container listings to web browsers. To improve performance, the proxy server can use an optional cache usually deployed with memcache."
 msgstr ""
 
-#: ./doc/common/section_cli_cinder_read-only-volumes.xml:9(para)
-msgid "Run the following command to set a volume to read-only access:"
+#: ./doc/common/section_getstart_object-storage.xml:20(term)
+msgid "Account servers (<systemitem class=\"service\">swift-account-server</systemitem>)"
 msgstr ""
 
-#: ./doc/common/section_cli_cinder_read-only-volumes.xml:11(replaceable)
-msgid "VOLUME"
+#: ./doc/common/section_getstart_object-storage.xml:22(para)
+msgid "Manages accounts defined with Object Storage."
 msgstr ""
 
-#: ./doc/common/section_cli_cinder_read-only-volumes.xml:11(replaceable)
-msgid "BOOLEAN"
+#: ./doc/common/section_getstart_object-storage.xml:26(term)
+msgid "Container servers (<systemitem class=\"service\">swift-container-server</systemitem>)"
 msgstr ""
 
-#: ./doc/common/section_cli_cinder_read-only-volumes.xml:12(para)
-msgid "<replaceable>VOLUME</replaceable> is the ID of the target volume and <replaceable>BOOLEAN</replaceable> is a flag that enables read-only or read/write access to the volume."
+#: ./doc/common/section_getstart_object-storage.xml:28(para)
+msgid "Manages the mapping of containers or folders, within Object Storage."
 msgstr ""
 
-#: ./doc/common/section_cli_cinder_read-only-volumes.xml:15(para)
-msgid "The following values for <replaceable>BOOLEAN</replaceable> are valid:"
+#: ./doc/common/section_getstart_object-storage.xml:32(term)
+msgid "Object servers (<systemitem class=\"service\">swift-object-server</systemitem>)"
 msgstr ""
 
-#: ./doc/common/section_cli_cinder_read-only-volumes.xml:19(para)
-msgid "<literal>true</literal>. Sets the read-only flag in the volume. When you attach the volume to an instance, the instance checks for this flag to determine whether to restrict volume access to read-only."
+#: ./doc/common/section_getstart_object-storage.xml:34(para)
+msgid "Manages actual objects,such as files, on the storage nodes."
 msgstr ""
 
-#: ./doc/common/section_cli_cinder_read-only-volumes.xml:25(para)
-msgid "<literal>false</literal>. Sets the volume to read/write access."
+#: ./doc/common/section_getstart_object-storage.xml:38(term)
+msgid "Various periodic processes"
 msgstr ""
 
-#: ./doc/common/section_cli_neutron_manage_networks.xml:7(title)
-msgid "Create and manage networks"
+#: ./doc/common/section_getstart_object-storage.xml:39(para)
+msgid "Performs housekeeping tasks on the large data store. The replication services ensure consistency and availability through the cluster. Other periodic processes include auditors, updaters, and reapers."
 msgstr ""
 
-#: ./doc/common/section_cli_neutron_manage_networks.xml:8(para)
-msgid "Before you run commands, set the following environment variables:"
+#: ./doc/common/section_getstart_object-storage.xml:45(term)
+msgid "WSGI middleware"
 msgstr ""
 
-#: ./doc/common/section_cli_neutron_manage_networks.xml:15(title)
-msgid "Create networks"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:18(para)
-msgid "List the extensions of the system:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:34(para)
-msgid "Create a network:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:53(para)
-msgid "Some fields of the created network are invisible to non-admin users."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:58(para)
-msgid "Create a network with specified provider network type:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:77(para)
-msgid "Just as shown previously, the unknown option <literal>--provider:network-type</literal> is used to create a <literal>local</literal> provider network."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:85(title)
-msgid "Create subnets"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:88(para)
-msgid "Create a subnet:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:106(para)
-msgid "The <placeholder-1/> command has the following positional and optional parameters:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:111(para)
-msgid "The name or ID of the network to which the subnet belongs."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:113(para)
-msgid "In this example, <literal>net1</literal> is a positional argument that specifies the network name."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:118(para)
-msgid "The CIDR of the subnet."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:119(para)
-msgid "In this example, <literal>192.168.2.0/24</literal> is a positional argument that specifies the CIDR."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:125(para)
-msgid "The subnet name, which is optional."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:127(para)
-msgid "In this example, <literal>--name subnet1</literal> specifies the name of the subnet."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:136(title)
-msgid "Create routers"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:139(para)
-msgid "Create a router:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:140(replaceable)
-msgid "router1"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:152(para)
-msgid "Take note of the unique router identifier returned, this will be required in subsequent steps."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:156(para)
-msgid "Link the router to the external provider network:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:157(replaceable) ./doc/common/section_cli_neutron_manage_networks.xml:164(replaceable)
-msgid "ROUTER"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:157(replaceable)
-msgid "NETWORK"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:158(para)
-msgid "Replace <replaceable>ROUTER</replaceable> with the unique identifier of the router, replace <replaceable>NETWORK</replaceable> with the unique identifier of the external provider network."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:163(para)
-msgid "Link the router to the subnet:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:164(replaceable)
-msgid "SUBNET"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:165(para)
-msgid "Replace <replaceable>ROUTER</replaceable> with the unique identifier of the router, replace <replaceable>SUBNET</replaceable> with the unique identifier of the subnet."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:172(title)
-msgid "Create ports"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:175(para)
-msgid "Create a port with specified IP address:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:194(para)
-msgid "In the previous command, <literal>net1</literal> is the network name, which is a positional argument. <literal>--fixed-ip ip_address=192.168.2.40</literal> is an option, which specifies the port's fixed IP address we wanted."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:201(para)
-msgid "When creating a port, you can specify any unallocated IP in the subnet even if the address is not in a pre-defined pool of allocated IP addresses (set by your cloud provider)."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:208(para)
-msgid "Create a port without specified IP address:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:229(para)
-msgid "Note that the system allocates one IP address if you do not specify an IP address in the <placeholder-1/> command."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:234(para)
-msgid "Query ports with specified fixed IP addresses:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:243(para)
-msgid "<literal>--fixed-ips ip_address=192.168.2.2 ip_address=192.168.2.40</literal> is one unknown option."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml:246(para)
-msgid "<emphasis role=\"bold\">How to find unknown options?</emphasis> The unknown options can be easily found by watching the output of <literal>create_xxx</literal> or <literal>show_xxx</literal> command. For example, in the port creation command, we see the fixed_ips fields, which can be used as an unknown option."
-msgstr ""
-
-#: ./doc/common/ch_preface.xml:7(title)
-msgid "Preface"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_apiv3.xml:5(title)
-msgid "Use Identity Service API v3 instead of API v2.0"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_apiv3.xml:6(para)
-msgid "Use the following parameters in combination on any keystone command to specify which version of the API to use:"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_apiv3.xml:11(para)
-msgid "<parameter>--os-endpoint</parameter>. The endpoint to use instead of the one in the service catalog. Defaults to <code>env[OS_SERVICE_ENDPOINT]</code>."
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_apiv3.xml:15(para)
-msgid "The <literal>keystone</literal> client detects the version of the API from this parameter."
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_apiv3.xml:19(para)
-msgid "<parameter>--os-auth_url</parameter>. The Identity Service endpoint to use for authentication. Defaults to <code>env[OS_AUTH_URL]</code>."
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_apiv3.xml:25(para)
-msgid "<parameter>--os-identity-api-version</parameter>. The Identity Service API version. Defaults to <code>env[OS_IDENTITY_API_VERSION]</code> or <literal>2.0</literal>."
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_apiv3.xml:31(para)
-msgid "For example, use the following parameters to use API v3:"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_apiv3.xml:33(parameter) ./doc/common/section_cli_keystone_apiv3.xml:35(parameter)
-msgid "--os-auth_url"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_apiv3.xml:33(parameter) ./doc/common/section_cli_keystone_apiv3.xml:35(parameter)
-msgid "--os-identity-api-version"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_apiv3.xml:34(para)
-msgid "Use the following parameters to use API v2.0:"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_trusted-compute-pools.xml:45(None) ./doc/common/section_trusted-compute-pools.xml:50(None)
-msgid "@@image: 'figures/OpenStackTrustedComputePool1.png'; md5=858fbd6148b927723cea5ad2c88d54bd"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_trusted-compute-pools.xml:150(None) ./doc/common/section_trusted-compute-pools.xml:155(None)
-msgid "@@image: 'figures/OpenStackTrustedComputePool2.png'; md5=077261c595464638c4b3fcc92b6afb9a"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:6(title)
-msgid "Trusted compute pools"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:7(para)
-msgid "Trusted compute pools enable administrators to designate a group of compute hosts as trusted. These hosts use hardware-based security features, such as the Intel Trusted Execution Technology (TXT), to provide an additional level of security. Combined with an external stand-alone, web-based remote attestation server, cloud providers can ensure that the compute node runs only software with verified measurements and can ensure a secure cloud stack."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:13(para)
-msgid "Using the trusted compute pools, cloud subscribers can request services to run on verified compute nodes."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:15(para)
-msgid "The remote attestation server performs node verification as follows:"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:19(para)
-msgid "Compute nodes boot with Intel TXT technology enabled."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:23(para)
-msgid "The compute node BIOS, hypervisor, and OS are measured."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:27(para)
-msgid "Measured data is sent to the attestation server when challenged by the attestation server."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:31(para)
-msgid "The attestation server verifies those measurements against a good and known database to determine node trustworthiness."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:35(para)
-msgid "A description of how to set up an attestation service is beyond the scope of this document. For an open source project that you can use to implement an attestation service, see the <link href=\"https://github.com/OpenAttestation/OpenAttestation\">Open Attestation</link> project."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:54(title)
-msgid "Configure Compute to use trusted compute pools"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:57(para)
-msgid "Enable scheduling support for trusted compute pools by adding the following lines in the <literal>DEFAULT</literal> section in the <filename>/etc/nova/nova.conf</filename> file:"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:66(para)
-msgid "Specify the connection information for your attestation service by adding the following lines to the <literal>trusted_computing</literal> section in the <filename>/etc/nova/nova.conf</filename> file:"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:81(term)
-msgid "server"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:83(para)
-msgid "Host name or IP address of the host that runs the attestation service."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:88(term)
-msgid "port"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:90(para)
-msgid "HTTPS port for the attestation service."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:94(term)
-msgid "server_ca_file"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:96(para)
-msgid "Certificate file used to verify the attestation server's identity."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:101(term)
-msgid "api_url"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:103(para)
-msgid "The attestation service's URL path."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:107(term)
-msgid "auth_blob"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:109(para)
-msgid "An authentication blob, which is required by the attestation service."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:117(para)
-msgid "Restart the <systemitem class=\"service\">nova-compute</systemitem> and <systemitem class=\"service\">nova-scheduler</systemitem> services."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:124(title) ./doc/common/section_compute_config-api.xml:183(title)
-msgid "Configuration reference"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:125(para)
-msgid "To customize the trusted compute pools, use the following configuration option settings:"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:132(title)
-msgid "Specify trusted flavors"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:133(para)
-msgid "To designate hosts as trusted:"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:136(para)
-msgid "Configure one or more flavors as trusted by using the <placeholder-1/> command. For example, to set the <literal>m1.tiny</literal> flavor as trusted:"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:141(para)
-msgid "Request that your instance be run on a trusted host, by specifying a trusted flavor when booting the instance. For example:"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml:145(title)
-msgid "Trusted compute pool"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-ec2.xml:6(title)
-msgid "Configure the EC2 API"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-ec2.xml:7(para)
-msgid "You can set options in the <filename>nova.conf</filename> configuration file to control which network address and port the EC2 API listens on, the formatting of some API responses, and authentication related options."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-ec2.xml:11(para)
-msgid "To customize these options for OpenStack EC2 API, use the configuration option settings documented in <xref linkend=\"config_table_nova_ec2\"/>."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:7(title)
-msgid "Features and benefits"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:12(th)
-msgid "Features"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:13(th)
-msgid "Benefits"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:18(emphasis)
-msgid "Leverages commodity hardware"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:19(td)
-msgid "No lock-in, lower price/GB."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:22(emphasis)
-msgid "HDD/node failure agnostic"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:23(td)
-msgid "Self-healing, reliable, data redundancy protects from failures."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:27(emphasis)
-msgid "Unlimited storage"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:28(td)
-msgid "Large and flat namespace, highly scalable read/write access, able to serve content directly from storage system."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:32(emphasis)
-msgid "Multi-dimensional scalability"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:34(td)
-msgid "Scale-out architecture: Scale vertically and horizontally-distributed storage. Backs up and archives large amounts of data with linear performance."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:39(emphasis)
-msgid "Account/container/object structure"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:40(td)
-msgid "No nesting, not a traditional file system: Optimized for scale, it scales to multiple petabytes and billions of objects."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:45(emphasis)
-msgid "Built-in replication 3✕ + data redundancy (compared with 2✕ on RAID)"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:48(td)
-msgid "A configurable number of accounts, containers and object copies for high availability."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:52(emphasis)
-msgid "Easily add capacity (unlike RAID resize)"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:54(td)
-msgid "Elastic data scaling with ease"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:57(emphasis)
-msgid "No central database"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:58(td)
-msgid "Higher performance, no bottlenecks"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:61(emphasis)
-msgid "RAID not required"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:62(td)
-msgid "Handle many small, random reads and writes efficiently"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:65(emphasis)
-msgid "Built-in management utilities"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:66(td)
-msgid "Account management: Create, add, verify, and delete users; Container management: Upload, download, and verify; Monitoring: Capacity, host, network, log trawling, and cluster health."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:72(emphasis)
-msgid "Drive auditing"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:73(td)
-msgid "Detect drive failures preempting data corruption"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:76(emphasis)
-msgid "Expiring objects"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:77(td)
-msgid "Users can set an expiration time or a TTL on an object to control access"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:81(emphasis)
-msgid "Direct object access"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:82(td)
-msgid "Enable direct browser access to content, such as for a control panel"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:86(emphasis)
-msgid "Realtime visibility into client requests"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:88(td)
-msgid "Know what users are requesting."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:91(emphasis)
-msgid "Supports S3 API"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:92(td)
-msgid "Utilize tools that were designed for the popular S3 API."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:96(emphasis)
-msgid "Restrict containers per account"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:98(td)
-msgid "Limit access to control usage by user."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:101(emphasis)
-msgid "Support for NetApp, Nexenta, SolidFire"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:103(td)
-msgid "Unified support for block volumes using a variety of storage systems."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:107(emphasis)
-msgid "Snapshot and backup API for block volumes"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:109(td)
-msgid "Data protection and recovery for VM data."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:112(emphasis)
-msgid "Standalone volume API available"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:114(td)
-msgid "Separate endpoint and API for integration with other compute systems."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:118(emphasis)
-msgid "Integration with Compute"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml:120(td)
-msgid "Fully integrated with Compute for attaching block volumes and reporting on usage."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml:6(title)
-msgid "User management"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml:7(para)
-msgid "The main components of Identity user management are:"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml:10(para)
-msgid "<emphasis role=\"bold\">User</emphasis>. Represents a human user. Has associated information such as user name, password, and email. This example creates a user named <literal>alice</literal>:"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml:17(para)
-msgid "<emphasis role=\"bold\">Tenant</emphasis>. A project, group, or organization. When you make requests to OpenStack services, you must specify a tenant. For example, if you query the Compute service for a list of running instances, you get a list of all running instances in the tenant that you specified in your query. This example creates a tenant named <literal>acme</literal>:"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml:27(para)
-msgid "Because the term <emphasis>project</emphasis> was used instead of <emphasis>tenant</emphasis> in earlier versions of OpenStack Compute, some command-line tools use <literal>--project_id</literal> instead of <literal>--tenant-id</literal> or <literal>--os-tenant-id</literal> to refer to a tenant ID."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml:38(para)
-msgid "<emphasis role=\"bold\">Role</emphasis>. Captures the operations that a user can perform in a given tenant."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml:40(para)
-msgid "This example creates a role named <literal>compute-user</literal>:"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml:44(para)
-msgid "Individual services, such as Compute and the Image Service, assign meaning to roles. In the Identity Service, a role is simply a name."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml:51(para)
-msgid "The Identity Service assigns a tenant and a role to a user. You might assign the <literal>compute-user</literal> role to the <literal>alice</literal> user in the <literal>acme</literal> tenant:"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml:74(para)
-msgid "A user can have different roles in different tenants. For example, Alice might also have the <literal>admin</literal> role in the <literal>Cyberdyne</literal> tenant. A user can also have multiple roles in the same tenant."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml:78(para)
-msgid "The <filename>/etc/<replaceable>[SERVICE_CODENAME]</replaceable>/policy.json</filename> file controls the tasks that users can perform for a given service. For example, <filename>/etc/nova/policy.json</filename> specifies the access policy for the Compute service, <filename>/etc/glance/policy.json</filename> specifies the access policy for the Image Service, and <filename>/etc/keystone/policy.json</filename> specifies the access policy for the Identity Service."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml:88(para)
-msgid "The default <filename>policy.json</filename> files in the Compute, Identity, and Image Service recognize only the <literal>admin</literal> role: all operations that do not require the <literal>admin</literal> role are accessible by any user that has any role in a tenant."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml:93(para)
-msgid "If you wish to restrict users from performing operations in, say, the Compute service, you need to create a role in the Identity Service and then modify <filename>/etc/nova/policy.json</filename> so that this role is required for Compute operations."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml:99(para)
-msgid "For example, this line in <filename>/etc/nova/policy.json</filename> specifies that there are no restrictions on which users can create volumes: if the user has any role in a tenant, they can create volumes in that tenant."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml:105(para)
-msgid "To restrict creation of volumes to users who had the <literal>compute-user</literal> role in a particular tenant, you would add <literal>\"role:compute-user\"</literal>, like so:"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml:110(para)
-msgid "To restrict all Compute service requests to require this role, the resulting file would look like:"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-spice.xml:6(title)
-msgid "SPICE console"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-spice.xml:7(para)
-msgid "OpenStack Compute supports VNC consoles to guests. The VNC protocol is fairly limited, lacking support for multiple monitors, bi-directional audio, reliable cut-and-paste, video streaming and more. SPICE is a new protocol that aims to address the limitations in VNC and provide good remote desktop support."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-spice.xml:12(para)
-msgid "SPICE support in OpenStack Compute shares a similar architecture to the VNC implementation. The OpenStack dashboard uses a SPICE-HTML5 widget in its console tab that communicates to the <systemitem class=\"service\">nova-spicehtml5proxy</systemitem> service by using SPICE-over-websockets. The <systemitem class=\"service\">nova-spicehtml5proxy</systemitem> service communicates directly with the hypervisor process by using SPICE."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-spice.xml:19(para)
-msgid "VNC must be explicitly disabled to get access to the SPICE console. Set the <option>vnc_enabled</option> option to <literal>False</literal> in the <literal>[DEFAULT]</literal> section to disable the VNC console."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-spice.xml:22(para)
-msgid "Use the following options to configure SPICE as the console for OpenStack Compute:"
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure.xml:6(title)
-msgid "Configure the dashboard"
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure.xml:8(para)
-msgid "You can configure the dashboard for a simple HTTP deployment."
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure.xml:14(para)
-msgid "Also, you can configure the size of the VNC window in the dashboard."
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-http.xml:6(title)
-msgid "Configure the dashboard for HTTP"
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-http.xml:8(para)
-msgid "You can configure the dashboard for a simple HTTP deployment. The standard installation uses a non-encrypted HTTP channel."
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-http.xml:12(para)
-msgid "Specify the host for your OpenStack Identity Service endpoint in the <filename>/etc/openstack-dashboard/local_settings.py</filename> file with the <literal>OPENSTACK_HOST</literal> setting."
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-http.xml:17(para)
-msgid "The following example shows this setting:"
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-http.xml:19(para)
-msgid "The service catalog configuration in the Identity Service determines whether a service appears in the dashboard. For the full listing, see <link href=\"http://docs.openstack.org/developer/horizon/topics/settings.html\">Horizon Settings and Configuration</link>."
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-http.xml:28(para)
-msgid "Restart Apache http server. For Ubuntu/Debian/SUSE:"
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-http.xml:30(para)
-msgid "or for Fedora/RHEL/CentOS:"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_dashboard_access.xml:89(None)
-msgid "@@image: 'figures/dashboard-project-tab.png'; md5=5b192a3d34c9285dbacd875395b8e4cc"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_dashboard_access.xml:214(None)
-msgid "@@image: 'figures/dashboard-admin-tab.png'; md5=039358c76c549d7d423da5b8aa826435"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:12(title)
-msgid "Log in to the dashboard"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:13(para)
-msgid "The dashboard is available on the node with the <literal>nova-dashboard</literal> server role."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:17(para)
-msgid "Ask the cloud operator for the host name or public IP address from which you can access the dashboard, and for your user name and password."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:22(para)
-msgid "Open a web browser that has JavaScript and cookies enabled."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:25(para)
-msgid "To use the Virtual Network Computing (VNC) client for the dashboard, your browser must support HTML5 Canvas and HTML5 WebSockets. The VNC client is based on noVNC. For details, see <link href=\"https://github.com/kanaka/noVNC/blob/master/README.md\">noVNC: HTML5 VNC Client</link>. For a list of supported browsers, see <link href=\"https://github.com/kanaka/noVNC/wiki/Browser-support\">Browser support</link>."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:38(para)
-msgid "In the address bar, enter the host name or IP address for the dashboard."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:40(replaceable)
-msgid "ipAddressOrHostName"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:42(para)
-msgid "If a certificate warning appears when you try to access the URL for the first time, a self-signed certificate is in use, which is not considered trustworthy by default. Verify the certificate or add an exception in the browser to bypass the warning."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:51(para)
-msgid "On the <guilabel>Log In</guilabel> page, enter your user name and password, and click <guibutton>Sign In</guibutton>."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:54(para)
-msgid "The top of the window displays your user name. You can also access <guilabel>Settings</guilabel> or sign out of the dashboard."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:61(para)
-msgid "If you are logged in as an end user, the <link linkend=\"dashboard_project_tab\">Project</link> tab is displayed."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:65(para)
-msgid "If you are logged in as an administrator, the <link linkend=\"dashboard_project_tab\">Project</link> tab and <link linkend=\"dashboard_admin_tab\">Admin</link> tab are displayed."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:57(para)
-msgid "The visible tabs and functions in the dashboard depend on the access permissions, or <emphasis role=\"italic\">roles</emphasis>, of the user you are logged in as.<placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:75(title)
-msgid "OpenStack dashboardProject tab"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:76(para)
-msgid "Projects are organizational units in the cloud, and are also known as tenants or accounts. Each user is a member of one or more projects. Within a project, a user creates and manages instances."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:80(para)
-msgid "From the <guilabel>Project</guilabel> tab, you can view and manage the resources in a selected project, including instances and images. You select the project from the <guilabel>CURRENT PROJECT</guilabel> list at the top of the tab."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:85(title)
-msgid "Project tab"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:93(para)
-msgid "From the <guilabel>Project</guilabel> tab, you can access the following tabs:"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:100(th) ./doc/common/section_dashboard_access.xml:170(th) ./doc/common/section_dashboard_access.xml:185(th) ./doc/common/section_dashboard_access.xml:192(th) ./doc/common/section_dashboard_access.xml:224(th) ./doc/common/section_dashboard_access.xml:350(th)
-msgid "<placeholder-1/> tab"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:105(guilabel) ./doc/common/section_dashboard_access.xml:229(guilabel) ./doc/common/section_cli_overview.xml:7(title)
-msgid "Overview"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:106(para)
-msgid "View reports for the project."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:109(guilabel) ./doc/common/section_dashboard_access.xml:292(guilabel)
-msgid "Instances"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:110(para)
-msgid "View, launch, create a snapshot from, stop, pause, or reboot instances, or connect to them through VNC."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:114(guilabel) ./doc/common/section_dashboard_access.xml:119(guilabel) ./doc/common/section_dashboard_access.xml:299(guilabel)
-msgid "Volumes"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:115(para) ./doc/common/section_dashboard_access.xml:141(para)
-msgid "Use the following tabs to complete these tasks:"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:121(para)
-msgid "View, create, edit, and delete volumes."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:125(guilabel)
-msgid "Volume Snapshots"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:127(para)
-msgid "View, create, edit, and delete volume snapshots."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:133(guilabel) ./doc/common/section_dashboard_access.xml:309(guilabel)
-msgid "Images"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:134(para)
-msgid "View images and instance snapshots created by project users, plus any images that are publicly available. Create, edit, and delete images, and launch instances from images and snapshots."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:140(guilabel)
-msgid "Access &amp; Security"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:144(guilabel)
-msgid "Security Groups"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:145(para)
-msgid "View, create, edit, and delete security groups and security group rules."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:150(guilabel)
-msgid "Key Pairs"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:151(para)
-msgid "View, create, edit, import, and delete key pairs."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:156(guilabel)
-msgid "Floating IPs"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:158(para)
-msgid "Allocate an IP address to or release it from a project."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:163(guilabel)
-msgid "API Access"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:164(para)
-msgid "View API endpoints."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:170(guilabel)
-msgid "Network"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:173(guilabel)
-msgid "Network Topology"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:174(para)
-msgid "View the network topology."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:177(guilabel) ./doc/common/section_dashboard_access.xml:314(guilabel)
-msgid "Networks"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:178(para)
-msgid "Create and manage public and private networks."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:181(guilabel) ./doc/common/section_dashboard_access.xml:318(guilabel)
-msgid "Routers"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:182(para)
-msgid "Create and manage subnets."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:185(guilabel)
-msgid "Object Store"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:188(guilabel) ./doc/common/section_dashboard_access.xml:195(guilabel)
-msgid "Containers"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:189(para)
-msgid "Create and manage containers and objects."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:196(para)
-msgid "Use the REST API to orchestrate multiple composite cloud applications."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:203(title)
-msgid "OpenStack dashboardAdmin tab"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:204(para)
-msgid "Administrative users can use the <guilabel>Admin</guilabel> tab to view usage and to manage instances, volumes, flavors, images, projects, users, services, and quotas."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:209(title)
-msgid "Admin tab"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:218(para)
-msgid "Access the following categories to complete these tasks:"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:224(guilabel)
-msgid "System Panel"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:230(para)
-msgid "View basic reports."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:233(guilabel)
-msgid "Resource Usage"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:234(para)
-msgid "Use the following tabs to view the following usages:"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:269(guilabel)
-msgid "Daily Report"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:271(para)
-msgid "View the daily report."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:275(guilabel)
-msgid "Stats"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:277(para)
-msgid "View the statistics of all resources."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:283(guilabel)
-msgid "Hypervisors"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:284(para)
-msgid "View the hypervisor summary."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:287(guilabel)
-msgid "Host Aggregates"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:288(para)
-msgid "View, create, and edit host aggregates. View the list of availability zones."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:293(para)
-msgid "View, pause, resume, suspend, migrate, soft or hard reboot, and delete running instances that belong to users of some, but not all, projects. Also, view the log for an instance or access an instance through VNC."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:300(para)
-msgid "View, create, edit, and delete volumes and volume types."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:305(para)
-msgid "View, create, edit, view extra specifications for, and delete flavors. A flavor is size of an instance."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:310(para)
-msgid "View, create, edit properties for, and delete custom images."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:315(para)
-msgid "View, create, edit properties for, and delete networks."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:319(para)
-msgid "View, create, edit properties for, and delete routers."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:322(guilabel)
-msgid "System Info"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:323(para)
-msgid "Use the following tabs to view the service information:"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:326(guilabel)
-msgid "Services"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:327(para)
-msgid "View a list of the services."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:331(guilabel)
-msgid "Compute Services"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:332(para)
-msgid "View a list of all Compute services."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:336(guilabel)
-msgid "Network Agents"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:337(para)
-msgid "View the network agents."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:341(guilabel)
-msgid "Default Quotas"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:342(para)
-msgid "View default quota values. Quotas are hard-coded in OpenStack Compute and define the maximum allowable size and number of resources."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:350(guilabel)
-msgid "Identity Panel"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:358(guilabel)
-msgid "Projects"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:359(para)
-msgid "View, create, assign users to, remove users from, and delete projects."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:363(guilabel)
-msgid "Users"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml:364(para)
-msgid "View, create, enable, disable, and delete users."
-msgstr ""
-
-#: ./doc/common/ch_using_openstack_overview.xml:7(title)
-msgid "How can I <phrase audience=\"enduser\">use</phrase><phrase audience=\"adminuser\">administer</phrase> an OpenStack cloud?"
-msgstr ""
-
-#: ./doc/common/ch_using_openstack_overview.xml:11(para)
-msgid "As an OpenStack cloud end user, you can provision your own resources within the limits set by administrators."
-msgstr ""
-
-#: ./doc/common/ch_using_openstack_overview.xml:14(para)
-msgid "As an OpenStack cloud administrative user, you can manage tenants, known as <glossterm baseform=\"project\">projects</glossterm>, users, services, images, flavors, and quotas."
-msgstr ""
-
-#: ./doc/common/ch_using_openstack_overview.xml:18(para)
-msgid "The examples in this guide show you how to perform tasks by using the following methods:"
-msgstr ""
-
-#: ./doc/common/ch_using_openstack_overview.xml:22(para)
-msgid "OpenStack dashboard. Use this web-based graphical interface, code named <link href=\"https://github.com/openstack/horizon/\">horizon</link>, to view, create, and manage resources<phrase audience=\"adminuser\"> and services</phrase>."
-msgstr ""
-
-#: ./doc/common/ch_using_openstack_overview.xml:30(para)
-msgid "OpenStack command-line clients. Each core OpenStack project has a command-line client that you can use to run simple commands to view, create, and manage resources<phrase audience=\"adminuser\"> and services</phrase> in a cloud and automate tasks by using scripts."
-msgstr ""
-
-#: ./doc/common/ch_using_openstack_overview.xml:38(para)
-msgid "You can modify these examples for your specific use cases."
-msgstr ""
-
-#: ./doc/common/ch_using_openstack_overview.xml:40(para)
-msgid "In addition to these ways of interacting with a cloud, you can access the OpenStack APIs directly or indirectly through <link href=\"http://curl.haxx.se/\">cURL</link> commands or open SDKs. You can automate access or build tools to manage resources and services by using the native OpenStack APIs or the EC2 compatibility API."
-msgstr ""
-
-#: ./doc/common/ch_using_openstack_overview.xml:46(para)
-msgid "To use the OpenStack APIs, it helps to be familiar with HTTP/1.1, RESTful web services, the OpenStack services, and JSON or XML data serialization formats."
-msgstr ""
-
-#: ./doc/common/section_xapi-ami-setup.xml:7(title)
-msgid "Prepare for AMI type images"
-msgstr ""
-
-#: ./doc/common/section_xapi-ami-setup.xml:8(para)
-msgid "To support AMI type images in your OpenStack installation, you must create a <filename>/boot/guest</filename> directory inside Dom0. The OpenStack VM extracts the kernel and ramdisk from the AKI and ARI images puts them in this location."
-msgstr ""
-
-#: ./doc/common/section_xapi-ami-setup.xml:12(para)
-msgid "OpenStack maintains the contents of this directory and its size should not increase during normal operation. However, in case of power failures or accidental shutdowns, some files might be left over. To prevent these files from filling the Dom0 disk, set up this directory as a symlink that points to a subdirectory of the local SR."
-msgstr ""
-
-#: ./doc/common/section_xapi-ami-setup.xml:18(para)
-msgid "Run these commands in Dom0 to achieve this setup:"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:8(title)
-msgid "Configuration file format"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:10(para)
-msgid "OpenStack uses the <glossterm>INI</glossterm> file format for configuration files. An INI file is a simple text file that specifies options as <literal>key=value</literal> pairs, grouped into sections. The <literal>DEFAULT</literal> section contains most of the configuration options. Lines starting with a hash sign (<literal>#</literal>) are comment lines. For example:"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:29(replaceable)
-msgid "KEYSTONE_DBPASS"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:29(replaceable)
-msgid "controller"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:32(para)
-msgid "Options can have different type for values. The comments in the sample config files always mention these. The following types are used by OpenStack:"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:39(term)
-msgid "boolean value"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:41(para)
-msgid "Enables or disables an option. The allowed values are <literal>true</literal> and <literal>false</literal>."
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:51(term)
-msgid "floating point value"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:53(para)
-msgid "A floating point number like <literal>0.25</literal> or <literal>1000</literal>."
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:62(term)
-msgid "integer value"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:64(para)
-msgid "An integer number is a number without fractional components, like <literal>0</literal> or <literal>42</literal>."
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:74(term)
-msgid "list value"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:76(para)
-msgid "Represents values of other types, separated by commas. As an example, the following sets <option>allowed_rpc_exception_modules</option> to a list containing the four elements <literal>oslo.messaging.exceptions</literal>, <literal>nova.exception</literal>, <literal>cinder.exception</literal>, and <literal>exceptions</literal>:"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:92(term)
-msgid "multi valued"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:94(para)
-msgid "A multi-valued option is a string value and can be given more than once, all values will be used."
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:105(term)
-msgid "string value"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:107(para)
-msgid "Strings can be optionally enclosed with single or double quotes."
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:127(title)
-msgid "Sections"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:134(literal) ./doc/common/tables/keystone-debug.xml:19(th) ./doc/common/tables/glance-policy.xml:19(th) ./doc/common/tables/nova-ipv6.xml:19(th) ./doc/common/tables/cinder-eqlx.xml:19(th) ./doc/common/tables/nova-rpc_all.xml:19(th) ./doc/common/tables/glance-qpid.xml:19(th) ./doc/common/tables/swift-container-server-DEFAULT.xml:7(literal) ./doc/common/tables/nova-volumes.xml:19(th) ./doc/common/tables/glance-gridfs.xml:19(th) ./doc/common/tables/glance-filesystem.xml:19(th) ./doc/common/tables/heat-redis.xml:19(th) ./doc/common/tables/trove-logging.xml:19(th) ./doc/common/tables/cinder-storage_gpfs.xml:19(th) ./doc/common/tables/cinder-nexenta_iscsi.xml:19(th) ./doc/common/tables/nova-ca.xml:19(th) ./doc/common/tables/cinder-huawei.xml:19(th) ./doc/common/tables/keystone-qpid.xml:19(th) ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:19(th) ./doc/common/tables/nova-glance.xml:19(th) ./doc/common/tables/neutron-dhcp_agent.xml:19(th) ./doc/common/tables/nova-neutron.xml:19(th) ./doc/common/tables/cinder-backups_ceph.xml:19(th) ./doc/common/tables/nova-metadata.xml:19(th) ./doc/common/tables/glance-s3.xml:19(th) ./doc/common/tables/glance-auth_token.xml:19(th) ./doc/common/tables/neutron-kombu.xml:19(th) ./doc/common/tables/trove-qpid.xml:19(th) ./doc/common/tables/trove-compute.xml:19(th) ./doc/common/tables/trove-nova.xml:19(th) ./doc/common/tables/cinder-block-device.xml:19(th) ./doc/common/tables/cinder-zones.xml:19(th) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:19(th) ./doc/common/tables/neutron-common.xml:19(th) ./doc/common/tables/neutron-compute.xml:19(th) ./doc/common/tables/heat-rpc.xml:19(th) ./doc/common/tables/neutron-openvswitch_agent.xml:19(th) ./doc/common/tables/cinder-compute.xml:19(th) ./doc/common/tables/cinder-lvm.xml:19(th) ./doc/common/tables/cinder-storage_nfs.xml:19(th) ./doc/common/tables/heat-cfn_api.xml:19(th) ./doc/common/tables/nova-hypervisor.xml:19(th) ./doc/common/tables/trove-rabbitmq.xml:19(th) ./doc/common/tables/trove-api.xml:19(th) ./doc/common/tables/cinder-quota.xml:19(th) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:7(literal) ./doc/common/tables/nova-console.xml:19(th) ./doc/common/tables/heat-clients.xml:19(th) ./doc/common/tables/heat-notification.xml:19(th) ./doc/common/tables/nova-common.xml:19(th) ./doc/common/tables/glance-zmq.xml:19(th) ./doc/common/tables/neutron-metering_agent.xml:19(th) ./doc/common/tables/trove-taskmanager.xml:19(th) ./doc/common/tables/keystone-zeromq.xml:19(th) ./doc/common/tables/neutron-api.xml:19(th) ./doc/common/tables/ceilometer-redis.xml:19(th) ./doc/common/tables/ceilometer-swift.xml:19(th) ./doc/common/tables/cinder-hplefthand.xml:19(th) ./doc/common/tables/heat-qpid.xml:19(th) ./doc/common/tables/nova-testing.xml:19(th) ./doc/common/tables/cinder-backups.xml:19(th) ./doc/common/tables/neutron-ml2_ofa.xml:19(th) ./doc/common/tables/trove-debug.xml:19(th) ./doc/common/tables/nova-s3.xml:19(th) ./doc/common/tables/cinder-rpc.xml:19(th) ./doc/common/tables/cinder-api.xml:19(th) ./doc/common/tables/cinder-windows.xml:19(th) ./doc/common/tables/glance-vmware.xml:19(th) ./doc/common/tables/trove-backup.xml:19(th) ./doc/common/tables/cinder-san.xml:19(th) ./doc/common/tables/keystone-rpc.xml:19(th) ./doc/common/tables/nova-db.xml:19(th) ./doc/common/tables/glance-logging.xml:19(th) ./doc/common/tables/cinder-zoning.xml:19(th) ./doc/common/tables/glance-wsgi.xml:19(th) ./doc/common/tables/nova-periodic.xml:19(th) ./doc/common/tables/cinder-images.xml:19(th) ./doc/common/tables/trove-swift.xml:19(th) ./doc/common/tables/cinder-auth_token.xml:19(th) ./doc/common/tables/heat-crypt.xml:19(th) ./doc/common/tables/neutron-wsgi.xml:19(th) ./doc/common/tables/neutron-scheduler.xml:19(th) ./doc/common/tables/keystone-security.xml:19(th) ./doc/common/tables/glance-rbd.xml:19(th) ./doc/common/tables/heat-rabbitmq.xml:19(th) ./doc/common/tables/ceilometer-logging.xml:19(th) ./doc/common/tables/neutron-metadata.xml:19(th) ./doc/common/tables/glance-redis.xml:19(th) ./doc/common/tables/cinder-hp3par.xml:19(th) ./doc/common/tables/cinder-storage_ceph.xml:19(th) ./doc/common/tables/nova-livemigration.xml:19(th) ./doc/common/tables/nova-ldap.xml:19(th) ./doc/common/tables/nova-fping.xml:19(th) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:19(th) ./doc/common/tables/nova-ec2.xml:19(th) ./doc/common/tables/trove-zeromq.xml:19(th) ./doc/common/tables/heat-database.xml:19(th) ./doc/common/tables/swift-object-server-DEFAULT.xml:7(literal) ./doc/common/tables/cinder-rootwrap.xml:19(th) ./doc/common/tables/ceilometer-database.xml:19(th) ./doc/common/tables/heat-debug.xml:19(th) ./doc/common/tables/cinder-nexenta_nfs.xml:19(th) ./doc/common/tables/trove-auth_token.xml:19(th) ./doc/common/tables/heat-waitcondition_api.xml:19(th) ./doc/common/tables/nova-policy.xml:19(th) ./doc/common/tables/keystone-amqp.xml:19(th) ./doc/common/tables/neutron-logging.xml:19(th) ./doc/common/tables/glance-rpc.xml:19(th) ./doc/common/tables/nova-authentication.xml:19(th) ./doc/common/tables/cinder-vmware.xml:19(th) ./doc/common/tables/glance-sheepdog.xml:19(th) ./doc/common/tables/heat-logging.xml:19(th) ./doc/common/tables/keystone-notification.xml:19(th) ./doc/common/tables/neutron-qpid.xml:19(th) ./doc/common/tables/glance-swift.xml:19(th) ./doc/common/tables/swift-account-server-DEFAULT.xml:7(literal) ./doc/common/tables/nova-libvirt.xml:19(th) ./doc/common/tables/neutron-lbaas.xml:19(th) ./doc/common/tables/cinder-backups_swift.xml:19(th) ./doc/common/tables/ceilometer-rpc.xml:19(th) ./doc/common/tables/heat-loadbalancer.xml:19(th) ./doc/common/tables/heat-cloudwatch_api.xml:19(th) ./doc/common/tables/nova-pci.xml:19(th) ./doc/common/tables/glance-imagecache.xml:19(th) ./doc/common/tables/trove-quota.xml:19(th) ./doc/common/tables/cinder-storage.xml:19(th) ./doc/common/tables/cinder-nas.xml:19(th) ./doc/common/tables/nova-vpn.xml:19(th) ./doc/common/tables/nova-wsgi.xml:19(th) ./doc/common/tables/cinder-storage_glusterfs.xml:19(th) ./doc/common/tables/nova-availabilityzones.xml:19(th) ./doc/common/tables/heat-zeromq.xml:19(th) ./doc/common/tables/nova-vnc.xml:19(th) ./doc/common/tables/keystone-logging.xml:19(th) ./doc/common/tables/neutron-l3_agent.xml:19(th) ./doc/common/tables/cinder-coraid.xml:19(th) ./doc/common/tables/nova-logging.xml:19(th) ./doc/common/tables/nova-xen.xml:19(th) ./doc/common/tables/ceilometer-collector.xml:19(th) ./doc/common/tables/keystone-ec2.xml:19(th) ./doc/common/tables/ceilometer-api.xml:19(th) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:19(th) ./doc/common/tables/glance-common.xml:19(th) ./doc/common/tables/nova-network.xml:19(th) ./doc/common/tables/cinder-scality.xml:19(th) ./doc/common/tables/neutron-notifier.xml:19(th) ./doc/common/tables/cinder-common.xml:19(th) ./doc/common/tables/nova-configdrive.xml:19(th) ./doc/common/tables/cinder-database.xml:19(th) ./doc/common/tables/neutron-rpc.xml:19(th) ./doc/common/tables/trove-volume.xml:19(th) ./doc/common/tables/nova-zeromq.xml:19(th) ./doc/common/tables/glance-testing.xml:19(th) ./doc/common/tables/glance-registry.xml:19(th) ./doc/common/tables/glance-amqp.xml:19(th) ./doc/common/tables/trove-database.xml:19(th) ./doc/common/tables/heat-clients_backends.xml:19(th) ./doc/common/tables/heat-amqp.xml:19(th) ./doc/common/tables/cinder-hpmsa.xml:19(th) ./doc/common/tables/cinder-emc.xml:19(th) ./doc/common/tables/glance-rabbitmq.xml:19(th) ./doc/common/tables/cinder-backups_tsm.xml:19(th) ./doc/common/tables/nova-qpid.xml:19(th) ./doc/common/tables/trove-rpc.xml:19(th) ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml:7(literal) ./doc/common/tables/ceilometer-qpid.xml:19(th) ./doc/common/tables/neutron-zeromq.xml:19(th) ./doc/common/tables/neutron-agent.xml:19(th) ./doc/common/tables/neutron-policy.xml:19(th) ./doc/common/tables/neutron-rootwrap.xml:19(th) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:7(literal) ./doc/common/tables/trove-common.xml:19(th) ./doc/common/tables/heat-api.xml:19(th) ./doc/common/tables/ceilometer-amqp.xml:19(th) ./doc/common/tables/keystone-auth_token.xml:19(th) ./doc/common/tables/neutron-redis.xml:19(th) ./doc/common/tables/neutron-ssl.xml:19(th) ./doc/common/tables/ceilometer-exchange.xml:19(th) ./doc/common/tables/ceilometer-common.xml:19(th) ./doc/common/tables/keystone-misc.xml:19(th) ./doc/common/tables/nova-scheduling.xml:19(th) ./doc/common/tables/ceilometer-auth.xml:19(th) ./doc/common/tables/trove-dns.xml:19(th) ./doc/common/tables/neutron-db.xml:19(th) ./doc/common/tables/keystone-redis.xml:19(th) ./doc/common/tables/heat-auth_token.xml:19(th) ./doc/common/tables/cinder-xiv.xml:19(th) ./doc/common/tables/cinder-hds-hus.xml:19(th) ./doc/common/tables/neutron-rabbitmq.xml:19(th) ./doc/common/tables/keystone-policy.xml:19(th) ./doc/common/tables/cinder-auth.xml:19(th) ./doc/common/tables/nova-kombu.xml:19(th) ./doc/common/tables/heat-quota.xml:19(th) ./doc/common/tables/neutron-auth_token.xml:19(th) ./doc/common/tables/cinder-storwize.xml:19(th) ./doc/common/tables/nova-rootwrap.xml:19(th) ./doc/common/tables/cinder-solidfire.xml:19(th) ./doc/common/tables/glance-ssl.xml:19(th) ./doc/common/tables/heat-metadata_api.xml:19(th) ./doc/common/tables/neutron-vmware.xml:19(th) ./doc/common/tables/nova-api.xml:19(th) ./doc/common/tables/glance-matchmaker.xml:19(th) ./doc/common/tables/cinder-san-solaris.xml:19(th) ./doc/common/tables/trove-heat.xml:19(th) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:19(th) ./doc/common/tables/neutron-quotas.xml:19(th) ./doc/common/tables/nova-rpc.xml:19(th) ./doc/common/tables/trove-guestagent.xml:19(th) ./doc/common/tables/keystone-rabbit.xml:19(th) ./doc/common/tables/glance-api.xml:19(th) ./doc/common/tables/cinder-scheduler.xml:19(th) ./doc/common/tables/keystone-api.xml:19(th) ./doc/common/tables/ceilometer-rabbitmq.xml:19(th) ./doc/common/tables/neutron-testing.xml:19(th) ./doc/common/tables/glance-cinder.xml:19(th) ./doc/common/tables/nova-redis.xml:19(th) ./doc/common/tables/ceilometer-inspector.xml:19(th) ./doc/common/tables/nova-rabbitmq.xml:19(th) ./doc/common/tables/heat-common.xml:19(th) ./doc/common/tables/cinder-zadara.xml:19(th) ./doc/common/tables/nova-quota.xml:19(th) ./doc/common/tables/nova-conductor.xml:19(th) ./doc/common/tables/nova-compute.xml:19(th) ./doc/common/tables/cinder-storage_xen.xml:19(th) ./doc/common/tables/trove-amqp.xml:19(th) ./doc/common/tables/nova-xvpnvncproxy.xml:19(th)
-msgid "[DEFAULT]"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:136(para)
-msgid "Contains most configuration options. If the documentation for a configuration option does not specify its section, assume that it appears in this section."
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:145(literal) ./doc/common/tables/nova-db.xml:33(th) ./doc/common/tables/heat-database.xml:34(th) ./doc/common/tables/ceilometer-database.xml:38(th) ./doc/common/tables/cinder-storage.xml:134(th) ./doc/common/tables/cinder-common.xml:226(th) ./doc/common/tables/cinder-connection.xml:19(th) ./doc/common/tables/neutron-db.xml:30(th) ./doc/common/tables/keystone-database.xml:19(th) ./doc/common/tables/glance-db.xml:19(th)
-msgid "[database]"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:147(para)
-msgid "Configuration options for the database that stores the state of the OpenStack service."
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:128(para)
-msgid "Configuration options are grouped by section. Most configuration file supports at least the following sections: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:158(title)
-msgid "Substitution"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:160(para)
-msgid "The configuration file supports variable substitution. After you set a configuration option, it can be referenced in later configuration values when you precede it with a <literal>$</literal>, like <literal>$OPTION</literal>."
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:167(para)
-msgid "The following example uses the values of <literal>rabbit_host</literal> and <literal>rabbit_port</literal> to define the value of the <literal>rabbit_hosts</literal> option, in this case as <literal>controller:5672</literal>."
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:185(para)
-msgid "To avoid substitution, use <literal>$$</literal>, it is replaced by a single <literal>$</literal>. For example, if your LDAP DNS password is <literal>$xkj432</literal>, specify it, as follows: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:191(para)
-msgid "The code uses the Python <literal>string.Template.safe_substitute()</literal> method to implement variable substitution. For more details on how variable substitution is resolved, see <link href=\"http://docs.python.org/2/library/string.html#template-strings\">http://docs.python.org/2/library/string.html#template-strings</link> and <link href=\"http://www.python.org/dev/peps/pep-0292/\">PEP 292</link>."
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:204(title)
-msgid "Whitespace"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:205(para)
-msgid "To include whitespace in a configuration value, use a quoted string. For example:"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:211(title)
-msgid "Define an alternate location for a config file"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml:212(para)
-msgid "Most services and the and the <placeholder-1/> command-line clients load the configuration file. To define an alternate location for the configuration file, pass the <parameter>--config-file <replaceable>CONFIG_FILE</replaceable></parameter> parameter when you start a service or call a <placeholder-2/> command."
-msgstr ""
-
-#: ./doc/common/section_about-object-storage.xml:8(para)
-msgid "Object Storage is a robust, highly scalable and fault tolerant storage platform for unstructured data such as objects. Objects are stored bits, accessed through a RESTful, HTTP-based interface. You cannot access data at the block or file level. Object Storage is commonly used to archive and back up data, with use cases in virtual machine image, photo, video and music storage."
-msgstr ""
-
-#: ./doc/common/section_about-object-storage.xml:15(para)
-msgid "Object Storage provides a high degree of availability, throughput, and performance with its scale out architecture. Each object is replicated across multiple servers, residing within the same data center or across data centers, which mitigates the risk of network and hardware failure. In the event of hardware failure, Object Storage will automatically copy objects to a new location to ensure that there are always three copies available. Object Storage is an eventually consistent distributed storage platform; it sacrifices consistency for maximum availability and partition tolerance. Object Storage enables you to create a reliable platform by using commodity hardware and inexpensive storage."
-msgstr ""
-
-#: ./doc/common/section_about-object-storage.xml:27(para)
-msgid "For more information, review the key concepts in the developer documentation at <link href=\"http://docs.openstack.org/developer/swift/\">docs.openstack.org/developer/swift/</link>."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-assignments.xml:6(title)
-msgid "Separate role authorization and user authentication"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-assignments.xml:7(para)
-msgid "When you configure the Identity service to use an LDAP back end, you can split authentication and authorization using the <emphasis>Assignments</emphasis> feature."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-assignments.xml:10(para)
-msgid "The Assignments feature enables administrators to manage project role authorization using the Identity service's own SQL database, while still providing user authentication through the LDAP directory."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-assignments.xml:14(para)
-msgid "To configure this:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-assignments.xml:16(title)
-msgid "Separating role authorization and user authentication through Assignments"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-assignments.xml:19(para)
-msgid "Configure the Identity service to authenticate users through the LDAP driver. To do so, first find the <literal>[identity]</literal> section in the <filename>/etc/keystone/keystone.conf</filename> configuration file. Then, set the <literal>driver</literal> configuration key in that section to <literal>keystone.identity.backends.ldap.Identity</literal>:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-assignments.xml:30(para)
-msgid "Next, enable the Assignment driver. To do so, find the <literal>[assignment]</literal> section in the <filename>/etc/keystone/keystone.conf</filename> configuration file. Then, set the <literal>driver</literal> configuration key in that section to <literal>keystone.assignment.backends.sql.Assignment</literal>:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-assignments.xml:41(para)
-msgid "On distributions that include <application>openstack-config</application>, you can configure both drivers by running the following commands instead:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:11(title)
-msgid "Manage volumes"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:12(para)
-msgid "A volume is a detachable block storage device, similar to a USB hard drive. You can attach a volume to only one instance. To create and manage volumes, you use a combination of <placeholder-1/> and <placeholder-2/> client commands."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:16(title)
-msgid "Migrate a volume"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:17(para)
-msgid "As an administrator, you can migrate a volume with its data from one location to another in a manner that is transparent to users and workloads. You can migrate only detached volumes with no snapshots."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:21(para)
-msgid "Possible use cases for data migration include:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:24(para)
-msgid "Bring down a physical storage device for maintenance without disrupting workloads."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:28(para)
-msgid "Modify the properties of a volume."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:31(para)
-msgid "Free up space in a thinly-provisioned back end."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:35(para)
-msgid "Migrate a volume with the <placeholder-1/> command, as shown in the following example:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:36(replaceable) ./doc/common/section_cli_cinder_manage_volumes.xml:274(replaceable)
-msgid "volumeID"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:36(replaceable)
-msgid "destinationHost"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:36(replaceable)
-msgid "True|False"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:37(para)
-msgid "In this example, <literal>--force-host-copy=True</literal> forces the generic host-based migration mechanism and bypasses any driver optimizations."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:40(para)
-msgid "If the volume is in use or has snapshots, the specified host destination cannot accept the volume. If the user is not an administrator, the migration fails."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:45(title)
-msgid "Create a volume"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:46(para)
-msgid "This example creates a my-new-volume volume based on an image."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:49(para)
-msgid "List images, and note the ID of the image that you want to use for your volume:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:62(para)
-msgid "List the availability zones, and note the ID of the availability zone in which you want to create your volume:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:81(para)
-msgid "Create a volume with 8GB of space, and specify the availability zone and image:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:103(para)
-msgid "To verify that your volume was created successfully, list the available volumes:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:112(para)
-msgid "If your volume was created successfully, its status is <literal>available</literal>. If its status is <literal>error</literal>, you might have exceeded your quota."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:120(title)
-msgid "Attach a volume to an instance"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:123(para)
-msgid "Attach your volume to a server, specifying the server ID and the volume ID:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:133(para)
-msgid "Note the ID of your volume."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:136(para)
-msgid "Show information for your volume:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:138(para)
-msgid "The output shows that the volume is attached to the server with ID <literal>84c6e57d-a6b1-44b6-81eb-fcb36afd31b5</literal>, is in the nova availability zone, and is bootable."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:165(title)
-msgid "Resize a volume"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:168(para)
-msgid "To resize your volume, you must first detach it from the server."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:170(para)
-msgid "To detach the volume from your server, pass the server ID and volume ID to the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:172(para) ./doc/common/section_cli_cinder_manage_volumes.xml:191(para)
-msgid "The <placeholder-1/> command does not return any output."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:184(para)
-msgid "Note that the volume is now available."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:187(para)
-msgid "Resize the volume by passing the volume ID and the new size (a value greater than the old one) as parameters:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:197(title)
-msgid "Delete a volume"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:200(para)
-msgid "To delete your volume, you must first detach it from the server."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:202(para)
-msgid "To detach the volume from your server and check for the list of existing volumes, see steps 1 and 2 in <xref linkend=\"cli_extend_volumes\"/>."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:206(para)
-msgid "Delete the volume using either the volume name or ID:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:208(para)
-msgid "The delete command does not return any output."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:212(para)
-msgid "List the volumes again, and note that the status of your volume is <literal>deleting</literal>:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:222(para)
-msgid "When the volume is fully deleted, it disappears from the list of volumes:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:234(title)
-msgid "Transfer a volume"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:235(para)
-msgid "You can transfer a volume from one owner to another by using the <placeholder-1/> commands. The volume donor, or original owner, creates a transfer request and sends the created transfer ID and authorization key to the volume recipient. The volume recipient, or new owner, accepts the transfer by using the ID and key."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:243(para)
-msgid "The procedure for volume transfer is intended for tenants (both the volume donor and recipient) within the same cloud."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:245(para)
-msgid "Use cases include:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:248(para)
-msgid "Create a custom bootable volume or a volume with a large data set and transfer it to a customer."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:251(para)
-msgid "For bulk import of data to the cloud, the data ingress system creates a new Block Storage volume, copies data from the physical device, and transfers device ownership to the end user."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:258(title)
-msgid "Create a volume transfer request"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:261(para)
-msgid "While logged in as the volume donor, list the available volumes:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:271(para)
-msgid "As the volume donor, request a volume transfer authorization code for a specific volume:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:275(para)
-msgid "The volume must be in an <literal>available</literal> state or the request will be denied. If the transfer request is valid in the database (that is, it has not expired or been deleted), the volume is placed in an <literal>awaiting transfer</literal> state. For example:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:279(para)
-msgid "The output shows the volume transfer ID in the <literal>id</literal> row and the authorization key."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:291(para)
-msgid "Optionally, you can specify a name for the transfer by using the <code>--display-name <replaceable>displayName</replaceable></code> parameter."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:299(para)
-msgid "Send the volume transfer ID and authorization key to the new owner (for example, by email)."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:304(para)
-msgid "View pending transfers:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:313(para)
-msgid "After the volume recipient, or new owner, accepts the transfer, you can see that the transfer is no longer available:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:325(title)
-msgid "Accept a volume transfer request"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:328(para)
-msgid "As the volume recipient, you must first obtain the transfer ID and authorization key from the original owner."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:333(para)
-msgid "Display the transfer request details by using the ID:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:334(replaceable) ./doc/common/section_cli_cinder_manage_volumes.xml:348(replaceable) ./doc/common/section_cli_cinder_manage_volumes.xml:392(replaceable)
-msgid "transferID"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:347(para)
-msgid "Accept the request:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:348(replaceable)
-msgid "authKey"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:359(para)
-msgid "If you do not have a sufficient quota for the transfer, the transfer is refused."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:367(title)
-msgid "Delete a volume transfer"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:371(para)
-msgid "List available volumes and their statuses:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:382(para)
-msgid "Find the matching transfer ID:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:391(para)
-msgid "Delete the volume:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml:397(para)
-msgid "Verify that transfer list is now empty and that the volume is again available for transfer:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml:6(title)
-msgid "Show usage statistics for hosts and instances"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml:7(para)
-msgid "You can show basic statistics on resource usage for hosts and instances."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml:10(para)
-msgid "For more sophisticated monitoring, see the <link href=\"https://launchpad.net/ceilometer\">ceilometer</link> project. You can also use tools, such as <link href=\"http://ganglia.info/\">Ganglia</link> or <link href=\"http://graphite.wikidot.com/\">Graphite</link>, to gather more detailed data."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml:20(title)
-msgid "Show host usage statistics"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml:21(para)
-msgid "The following examples show the host usage statistics for a host called <filename>devstack</filename>."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml:25(para)
-msgid "List the hosts and the nova-related services that run on them:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml:37(para)
-msgid "Get a summary of resource usage of all of the instances running on the host:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml:49(para)
-msgid "The <literal>cpu</literal> column shows the sum of the virtual CPUs for instances running on the host."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml:51(para)
-msgid "The <literal>memory_mb</literal> column shows the sum of the memory (in MB) allocated to the instances that run on the host."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml:54(para)
-msgid "The <literal>disk_gb</literal> column shows the sum of the root and ephemeral disk sizes (in GB) of the instances that run on the host."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml:57(para)
-msgid "The row that has the value <literal>used_now</literal> in the <literal>PROJECT</literal> column shows the sum of the resources allocated to the instances that run on the host, plus the resources allocated to the virtual machine of the host itself."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml:62(para)
-msgid "The row that has the value <literal>used_max</literal> row in the <literal>PROJECT</literal> column shows the sum of the resources allocated to the instances that run on the host."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml:68(para)
-msgid "These values are computed by using information about the flavors of the instances that run on the hosts. This command does not query the CPU usage, memory usage, or hard disk usage of the physical host."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml:75(title)
-msgid "Show instance usage statistics"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml:77(para)
-msgid "Get CPU, memory, I/O, and network statistics for an instance."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml:79(para)
-msgid "List instances:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml:87(para)
-msgid "Get diagnostic statistics:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml:108(para)
-msgid "Get summary statistics for each tenant:"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:11(title)
-msgid "Image Service command-line client"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:12(para)
-msgid "The <placeholder-1/> client is the command-line interface (CLI) for the OpenStack Image Service API and its extensions. This chapter documents <placeholder-2/> version 0.12.0."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:22(title)
-msgid "glance usage"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:43(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use image-create instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:52(emphasis) ./doc/common/ch_cli_glance_commands.xml:180(emphasis)
-msgid "DEPRECATED!"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:59(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use image-delete instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:67(para) ./doc/common/ch_cli_glance_commands.xml:131(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use image-list instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:75(para) ./doc/common/ch_cli_glance_commands.xml:524(para)
-msgid "Create a new image."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:91(para)
-msgid "Download a specific image."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:99(para) ./doc/common/ch_cli_glance_commands.xml:715(para)
-msgid "List images you can access."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:107(para) ./doc/common/ch_cli_glance_commands.xml:163(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use member-list instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:115(para) ./doc/common/ch_cli_glance_commands.xml:848(para)
-msgid "Describe a specific image."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:123(para) ./doc/common/ch_cli_glance_commands.xml:886(para)
-msgid "Update a specific image."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:139(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use member-create instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:147(para) ./doc/common/ch_cli_glance_commands.xml:1057(para)
-msgid "Share a specific image with a tenant."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:155(para) ./doc/common/ch_cli_glance_commands.xml:1093(para)
-msgid "Remove a shared image from a tenant."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:171(para) ./doc/common/ch_cli_glance_commands.xml:1118(para)
-msgid "Describe sharing permissions by image or tenant."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:187(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use image-show instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:195(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use image-update instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:212(title)
-msgid "glance optional arguments"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:225(para)
-msgid "Defaults to <code>env[GLANCECLIENT_DEBUG]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:233(para)
-msgid "Print more verbose output"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:241(para)
-msgid "Force retrieving the schema used to generate portions of the help text rather than using a cached copy. Ignored with api version 1"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:251(para)
-msgid "Explicitly allow glanceclient to perform \"insecure SSL\" (https) requests. The server's certificate will not be verified against any certificate authorities. This option should be used with caution."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:282(para)
-msgid "Path of CA TLS certificate(s) used to verify the remote server's certificate. Without this option glance looks for the default system CA certificates."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:300(para)
-msgid "Number of seconds to wait for a response"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:308(para)
-msgid "Disable SSL compression when using https."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:316(para)
-msgid "Prevent select actions from requesting user confirmation."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:325(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Only used for deprecated legacy commands."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:333(para) ./doc/common/ch_cli_glance_commands.xml:342(para) ./doc/common/ch_cli_glance_commands.xml:351(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Send a fully-formed endpoint using --os- image-url instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:360(para)
-msgid "Defaults to <code>env[OS_USERNAME]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:368(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use --os-username."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:376(para)
-msgid "Defaults to <code>env[OS_PASSWORD]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:384(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use --os-password."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:392(para)
-msgid "Defaults to <code>env[OS_TENANT_ID]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:400(para)
-msgid "Defaults to <code>env[OS_TENANT_NAME]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:408(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use --os-tenant-name."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:416(para)
-msgid "Defaults to <code>env[OS_AUTH_URL]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:424(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use --os-auth-url."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:432(para)
-msgid "Defaults to <code>env[OS_REGION_NAME]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:440(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use --os-region-name."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:456(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use --os-auth-token."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:464(para)
-msgid "Defaults to <code>env[OS_IMAGE_URL]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:472(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use --os-image-url."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:480(para)
-msgid "Defaults to <code>env[OS_IMAGE_API_VERSION]</code> or 1"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:488(para)
-msgid "Defaults to <code>env[OS_SERVICE_TYPE]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:496(para)
-msgid "Defaults to <code>env[OS_ENDPOINT_TYPE]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:504(para)
-msgid "<emphasis>DEPRECATED!</emphasis> This option is completely ignored."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:512(title)
-msgid "glance image-create command"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:531(para)
-msgid "of image to reserve."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:539(para) ./doc/common/ch_cli_glance_commands.xml:904(para)
-msgid "Name of image."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:547(para)
-msgid "Store to upload image to."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:555(para) ./doc/common/ch_cli_glance_commands.xml:912(para)
-msgid "Disk format of image. Acceptable formats: ami, ari, aki, vhd, vmdk, raw, qcow2, vdi, and iso."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:564(para) ./doc/common/ch_cli_glance_commands.xml:921(para)
-msgid "Container format of image. Acceptable formats: ami, ari, aki, bare, and ovf."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:573(para) ./doc/common/ch_cli_glance_commands.xml:930(para)
-msgid "Tenant who should own image."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:581(para)
-msgid "Size of image data (in bytes). Only used with '-- location' and '--copy_from'."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:590(para) ./doc/common/ch_cli_glance_commands.xml:946(para)
-msgid "Minimum size of disk needed to boot image (in gigabytes)."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:599(para) ./doc/common/ch_cli_glance_commands.xml:955(para)
-msgid "Minimum amount of ram needed to boot image (in megabytes)."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:608(para) ./doc/common/ch_cli_glance_commands.xml:964(para)
-msgid "URL where the data for this image already resides. For example, if the image data is stored in swift, you could specify 'swift://account:key@example.com/container/obj'."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:619(para)
-msgid "Local file that contains disk image to be uploaded during creation. Alternatively, images can be passed to the client via stdin."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:629(para)
-msgid "Hash of image data used Glance can use for verification. Provide a md5 checksum here."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:638(para) ./doc/common/ch_cli_glance_commands.xml:994(para)
-msgid "Similar to '--location' in usage, but this indicates that the Glance server should immediately copy the data and store it in its configured image store."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:648(para) ./doc/common/ch_cli_glance_commands.xml:1004(para)
-msgid "Make image accessible to the public."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:656(para) ./doc/common/ch_cli_glance_commands.xml:1012(para)
-msgid "Prevent image from being deleted."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:664(para) ./doc/common/ch_cli_glance_commands.xml:1020(para)
-msgid "Arbitrary property to associate with image. May be used multiple times."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:673(para) ./doc/common/ch_cli_glance_commands.xml:790(para) ./doc/common/ch_cli_glance_commands.xml:866(para) ./doc/common/ch_cli_glance_commands.xml:1039(para)
-msgid "Print image size in a human-friendly format."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:681(para) ./doc/common/ch_cli_glance_commands.xml:1047(para)
-msgid "Show upload progress bar."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:689(title)
-msgid "glance image-delete command"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:698(para)
-msgid "Name or ID of image(s) to delete."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:706(title)
-msgid "glance image-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:722(para)
-msgid "Filter images to those that have this name."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:730(para)
-msgid "Filter images to those that have this status."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:738(para)
-msgid "Filter images to those that have this container format. Acceptable formats: ami, ari, aki, bare, and ovf."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:748(para)
-msgid "Filter images to those that have this disk format. Acceptable formats: ami, ari, aki, vhd, vmdk, raw, qcow2, vdi, and iso."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:758(para)
-msgid "Filter images to those with a size greater than this."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:766(para)
-msgid "Filter images to those with a size less than this."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:774(para)
-msgid "Filter images by a user-defined image property."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:782(para)
-msgid "Number of images to request in each paginated request."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:798(para)
-msgid "Sort image list by specified field."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:806(para)
-msgid "Sort image list in specified direction."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:814(para)
-msgid "Allows the user to select a listing of public or non public images."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:823(para)
-msgid "Display only images owned by this tenant id. Filtering occurs on the client side so may be inefficient. This option is mainly intended for admin use. Use an empty string ('') to list images with no owner. Note: This option overrides the --is-public argument if present. Note: the v2 API supports more efficient server-side owner based filtering."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:837(para)
-msgid "Allows the admin user to list all images irrespective of the image's owner or is_public value."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:846(title)
-msgid "glance image-show command"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:855(para)
-msgid "Name or ID of image to describe."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:874(title)
-msgid "glance image-update command"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:893(para)
-msgid "Name or ID of image to modify."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:938(para)
-msgid "Size of image data (in bytes)."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:975(para)
-msgid "Local file that contains disk image to be uploaded during update. Alternatively, images can be passed to the client via stdin."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:985(para)
-msgid "Hash of image data used Glance can use for verification."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:1029(para)
-msgid "If this flag is present, delete all image properties not explicitly set in the update request. Otherwise, those properties not referenced are preserved."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:1055(title)
-msgid "glance member-create command"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:1064(para)
-msgid "Image to add member to."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:1072(para)
-msgid "Tenant to add as member"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:1083(para)
-msgid "Allow the specified tenant to share this image."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:1091(title)
-msgid "glance member-delete command"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:1100(para)
-msgid "Image from which to remove member"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:1108(para)
-msgid "Tenant to remove as member"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:1116(title)
-msgid "glance member-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:1125(para)
-msgid "Filter results by an image ID."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml:1133(para)
-msgid "Filter results by a tenant ID."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_userdata.xml:6(title)
-msgid "Provide user data to instances"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_userdata.xml:7(para)
-msgid "A <glossterm baseform=\"user data\">user data</glossterm> file is a special key in the metadata service that holds a file that cloud-aware applications in the guest instance can access. For example, one application that uses user data is the <link href=\"https://help.ubuntu.com/community/CloudInit\">cloud-init</link> system, which is an open-source package from Ubuntu that is available on various Linux distributions and which handles early initialization of a cloud instance."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_userdata.xml:14(para)
-msgid "You can place user data in a local file and pass it through the <parameter>--user-data &lt;user-data-file&gt;</parameter> parameter at instance creation:"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml:6(title) ./doc/common/section_objectstorage-components.xml:192(title)
-msgid "Replication"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml:7(para)
-msgid "Because each replica in Object Storage functions independently and clients generally require only a simple majority of nodes to respond to consider an operation successful, transient failures like network partitions can quickly cause replicas to diverge. These differences are eventually reconciled by asynchronous, peer-to-peer replicator processes. The replicator processes traverse their local file systems and concurrently perform operations in a manner that balances load across physical disks."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml:16(para)
-msgid "Replication uses a push model, with records and files generally only being copied from local to remote replicas. This is important because data on the node might not belong there (as in the case of hand offs and ring changes), and a replicator cannot know which data it should pull in from elsewhere in the cluster. Any node that contains data must ensure that data gets to where it belongs. The ring handles replica placement."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml:24(para)
-msgid "To replicate deletions in addition to creations, every deleted record or file in the system is marked by a tombstone. The replication process cleans up tombstones after a time period known as the <emphasis role=\"italic\">consistency window</emphasis>. This window defines the duration of the replication and how long transient failure can remove a node from the cluster. Tombstone cleanup must be tied to replication to reach replica convergence."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml:32(para)
-msgid "If a replicator detects that a remote drive has failed, the replicator uses the <literal>get_more_nodes</literal> interface for the ring to choose an alternate node with which to synchronize. The replicator can maintain desired levels of replication during disk failures, though some replicas might not be in an immediately usable location."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml:39(para)
-msgid "The replicator does not maintain desired levels of replication when failures such as entire node failures occur; most failures are transient."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml:43(para)
-msgid "The main replication types are:"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml:46(para)
-msgid "<emphasis role=\"bold\">Database replication</emphasis>. Replicates containers and objects."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml:51(para)
-msgid "<emphasis role=\"bold\">Object replication</emphasis>. Replicates object data."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml:56(title)
-msgid "Database replication"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml:57(para)
-msgid "Database replication completes a low-cost hash comparison to determine whether two replicas already match. Normally, this check can quickly verify that most databases in the system are already synchronized. If the hashes differ, the replicator synchronizes the databases by sharing records added since the last synchronization point."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml:64(para)
-msgid "This synchronization point is a high water mark that notes the last record at which two databases were known to be synchronized, and is stored in each database as a tuple of the remote database ID and record ID. Database IDs are unique across all replicas of the database, and record IDs are monotonically increasing integers. After all new records are pushed to the remote database, the entire synchronization table of the local database is pushed, so the remote database can guarantee that it is synchronized with everything with which the local database was previously synchronized."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml:75(para)
-msgid "If a replica is missing, the whole local database file is transmitted to the peer by using rsync(1) and is assigned a new unique ID."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml:78(para)
-msgid "In practice, database replication can process hundreds of databases per concurrency setting per second (up to the number of available CPUs or disks) and is bound by the number of database transactions that must be performed."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml:85(title)
-msgid "Object replication"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml:86(para)
-msgid "The initial implementation of object replication performed an rsync to push data from a local partition to all remote servers where it was expected to reside. While this worked at small scale, replication times skyrocketed once directory structures could no longer be held in RAM. This scheme was modified to save a hash of the contents for each suffix directory to a per-partition hashes file. The hash for a suffix directory is no longer valid when the contents of that suffix directory is modified."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml:95(para)
-msgid "The object replication process reads in hash files and calculates any invalidated hashes. Then, it transmits the hashes to each remote server that should hold the partition, and only suffix directories with differing hashes on the remote server are rsynced. After pushing files to the remote server, the replication process notifies it to recalculate hashes for the rsynced suffix directories."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml:103(para)
-msgid "The number of uncached directories that object replication must traverse, usually as a result of invalidated suffix directory hashes, impedes performance. To provide acceptable replication speeds, object replication is designed to invalidate around 2 percent of the hash space on a normal node each day."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_reboot.xml:5(title)
-msgid "Reboot an instance"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_reboot.xml:6(para)
-msgid "You can soft or hard reboot a running instance. A soft reboot attempts a graceful shut down and restart of the instance. A hard reboot power cycles the instance."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_reboot.xml:9(para)
-msgid "By default, when you reboot a server, it is a soft reboot."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_reboot.xml:10(replaceable) ./doc/common/section_cli_nova_reboot.xml:12(replaceable)
-msgid "SERVER"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_reboot.xml:11(para)
-msgid "To perform a hard reboot, pass the <parameter>--hard</parameter> parameter, as follows:"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:6(title)
-msgid "Ring-builder"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:7(para)
-msgid "Use the swift-ring-builder utility to build and manage rings. This utility assigns partitions to devices and writes an optimized Python structure to a gzipped, serialized file on disk for transmission to the servers. The server processes occasionally check the modification time of the file and reload in-memory copies of the ring structure as needed. If you use a slightly older version of the ring, one of the three replicas for a partition subset will be incorrect because of the way the ring-builder manages changes to the ring. You can work around this issue."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:17(para)
-msgid "The ring-builder also keeps its own builder file with the ring information and additional data required to build future rings. It is very important to keep multiple backup copies of these builder files. One option is to copy the builder files out to every server while copying the ring files themselves. Another is to upload the builder files into the cluster itself. If you lose the builder file, you have to create a new ring from scratch. Nearly all partitions would be assigned to different devices and, therefore, nearly all of the stored data would have to be replicated to new locations. So, recovery from a builder file loss is possible, but data would be unreachable for an extended time."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:30(title)
-msgid "Ring data structure"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:31(para)
-msgid "The ring data structure consists of three top level fields: a list of devices in the cluster, a list of lists of device ids indicating partition to device assignments, and an integer indicating the number of bits to shift an MD5 hash to calculate the partition for the hash."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:38(title)
-msgid "Partition assignment list"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:39(para)
-msgid "This is a list of <literal>array(‘H’)</literal> of devices ids. The outermost list contains an <literal>array(‘H’)</literal> for each replica. Each <literal>array(‘H’)</literal> has a length equal to the partition count for the ring. Each integer in the <literal>array(‘H’)</literal> is an index into the above list of devices. The partition list is known internally to the Ring class as <literal>_replica2part2dev_id</literal>."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:48(para)
-msgid "So, to create a list of device dictionaries assigned to a partition, the Python code would look like: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:52(para)
-msgid "That code is a little simplistic because it does not account for the removal of duplicate devices. If a ring has more replicas than devices, a partition will have more than one replica on a device."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:56(para)
-msgid "<literal>array(‘H’)</literal> is used for memory conservation as there may be millions of partitions."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:61(title)
-msgid "Replica counts"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:62(para)
-msgid "To support the gradual change in replica counts, a ring can have a real number of replicas and is not restricted to an integer number of replicas."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:65(para)
-msgid "A fractional replica count is for the whole ring and not for individual partitions. It indicates the average number of replicas for each partition. For example, a replica count of 3.2 means that 20 percent of partitions have four replicas and 80 percent have three replicas."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:70(para)
-msgid "The replica count is adjustable."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:71(para)
-msgid "Example:"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:74(para)
-msgid "You must rebalance the replica ring in globally distributed clusters. Operators of these clusters generally want an equal number of replicas and regions. Therefore, when an operator adds or removes a region, the operator adds or removes a replica. Removing unneeded replicas saves on the cost of disks."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:80(para)
-msgid "You can gradually increase the replica count at a rate that does not adversely affect cluster performance."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:90(para)
-msgid "Changes take effect after the ring is rebalanced. Therefore, if you intend to change from 3 replicas to 3.01 but you accidentally type <literal>2.01</literal>, no data is lost."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:95(replaceable)
-msgid "X.builder"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:94(para)
-msgid "Additionally, <placeholder-1/> can now take a decimal argument for the number of replicas."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:100(title)
-msgid "Partition shift value"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:101(para)
-msgid "The partition shift value is known internally to the Ring class as <literal>_part_shift</literal>. This value is used to shift an MD5 hash to calculate the partition where the data for that hash should reside. Only the top four bytes of the hash is used in this process. For example, to compute the partition for the <literal>/account/container/object</literal> path, the Python code might look like the following code: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:112(para)
-msgid "For a ring generated with part_power P, the partition shift value is <literal>32 - P</literal>."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:116(title)
-msgid "Build the ring"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:117(para)
-msgid "The ring builder process includes these high-level steps:"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:121(para)
-msgid "The utility calculates the number of partitions to assign to each device based on the weight of the device. For example, for a partition at the power of 20, the ring has 1,048,576 partitions. One thousand devices of equal weight will each want 1,048.576 partitions. The devices are sorted by the number of partitions they desire and kept in order throughout the initialization process."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:131(para)
-msgid "Each device is also assigned a random tiebreaker value that is used when two devices desire the same number of partitions. This tiebreaker is not stored on disk anywhere, and so two different rings created with the same parameters will have different partition assignments. For repeatable partition assignments, <literal>RingBuilder.rebalance()</literal> takes an optional seed value that seeds the Python pseudo-random number generator."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:145(para)
-msgid "The ring builder assigns each partition replica to the device that requires most partitions at that point while keeping it as far away as possible from other replicas. The ring builder prefers to assign a replica to a device in a region that does not already have a replica. If no such region is available, the ring builder searches for a device in a different zone, or on a different server. If it does not find one, it looks for a device with no replicas. Finally, if all options are exhausted, the ring builder assigns the replica to the device that has the fewest replicas already assigned."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:159(para)
-msgid "The ring builder assigns multiple replicas to one device only if the ring has fewer devices than it has replicas."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:165(para)
-msgid "When building a new ring from an old ring, the ring builder recalculates the desired number of partitions that each device wants."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:174(para)
-msgid "The ring builder unassigns any assigned partitions from any removed devices and adds these partitions to the gathered list."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:180(para)
-msgid "The ring builder unassigns any partition replicas that can be spread out for better durability and adds these partitions to the gathered list."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:187(para)
-msgid "The ring builder unassigns random partitions from any devices that have more partitions than they need and adds these partitions to the gathered list."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:170(para)
-msgid "The ring builder unassigns partitions and gathers these partitions for reassignment, as follows: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:197(para)
-msgid "The ring builder reassigns the gathered partitions to devices by using a similar method to the one described previously."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:202(para)
-msgid "When the ring builder reassigns a replica to a partition, the ring builder records the time of the reassignment. The ring builder uses this value when it gathers partitions for reassignment so that no partition is moved twice in a configurable amount of time. The RingBuilder class knows this configurable amount of time as <literal>min_part_hours</literal>. The ring builder ignores this restriction for replicas of partitions on removed devices because removal of a device happens on device failure only, and reassignment is the only choice."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml:216(para)
-msgid "Theses steps do not always perfectly rebalance a ring due to the random nature of gathering partitions for reassignment. To help reach a more balanced ring, the rebalance process is repeated until near perfect (less than 1 percent off) or when the balance does not improve by at least 1 percent (indicating we probably cannot get perfect balance due to wildly imbalanced zones or too many partitions recently moved)."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-account-reaper.xml:7(title)
-msgid "Account reaper"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-account-reaper.xml:8(para)
-msgid "In the background, the account reaper removes data from the deleted accounts."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-account-reaper.xml:9(para)
-msgid "A reseller marks an account for deletion by issuing a <code>DELETE</code> request on the account’s storage URL. This action sets the <code>status</code> column of the account_stat table in the account database and replicas to <code>DELETED</code>, marking the account's data for deletion."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-account-reaper.xml:17(para)
-msgid "It's on the developers' to-do list to write a utility that performs this task, preferably through a ReST call."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-account-reaper.xml:12(para)
-msgid "Typically, a specific retention time or undelete are not provided. However, you can set a <code>delay_reaping</code> value in the <code>[account-reaper]</code> section of the account-server.conf to delay the actual deletion of data. At this time, to undelete you have to update the account database replicas directly, setting the status column to an empty string and updating the put_timestamp to be greater than the delete_timestamp. <placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-account-reaper.xml:20(para)
-msgid "The account reaper runs on each account server and scans the server occasionally for account databases marked for deletion. It only fires up on the accounts for which the server is the primary node, so that multiple account servers aren’t trying to do it simultaneously. Using multiple servers to delete one account might improve the deletion speed but requires coordination to avoid duplication. Speed really is not a big concern with data deletion, and large accounts aren’t deleted often."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-account-reaper.xml:26(para)
-msgid "Deleting an account is simple. For each account container, all objects are deleted and then the container is deleted. Deletion requests that fail will not stop the overall process but will cause the overall process to fail eventually (for example, if an object delete times out, you will not be able to delete the container or the account). The account reaper keeps trying to delete an account until it is empty, at which point the database reclaim process within the db_replicator will remove the database files."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-account-reaper.xml:32(para)
-msgid "A persistent error state may prevent the deletion of an object or container. If this happens, you will see a message such as <code>“Account &lt;name&gt; has not been reaped since &lt;date&gt;”</code> in the log. You can control when this is logged with the <code>reap_warn_after</code> value in the <code>[account-reaper]</code> section of the account-server.conf file. The default value is 30 days."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:9(title)
-msgid "Troubleshoot Compute"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:10(para)
-msgid "Common problems for Compute typically involve misconfigured networking or credentials that are not sourced properly in the environment. Also, most flat networking configurations do not enable <placeholder-1/> or <placeholder-2/> from a compute node to the instances that run on that node. Another common problem is trying to run 32-bit images on a 64-bit compute node. This section shows you how to troubleshoot Compute."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:19(title)
-msgid "Compute service logging"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:20(para)
-msgid "Compute stores a log file for each service in <filename>/var/log/nova</filename>. For example, <filename>nova-compute.log</filename> is the log for the <systemitem class=\"service\">nova-compute</systemitem> service. You can set the following options to format log strings for the nova.log module in the <filename>nova.conf</filename> file:"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:29(literal)
-msgid "logging_context_format_string"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:32(literal)
-msgid "logging_default_format_string"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:35(para)
-msgid "If the log level is set to <literal>debug</literal>, you can also specify <literal>logging_debug_format_suffix</literal> to append extra formatting. For information about what variables are available for the formatter see: <link href=\"http://docs.python.org/library/logging.html#formatter\">http://docs.python.org/library/logging.html#formatter</link>."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:42(para)
-msgid "You have two options for logging for OpenStack Compute based on configuration settings. In <filename>nova.conf</filename>, include the <literal>logfile</literal> option to enable logging. Alternatively you can set <literal>use_syslog = 1</literal> so that the nova daemon logs to syslog."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:50(title)
-msgid "Guru Meditation reports"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:51(para)
-msgid "A Guru Meditation report is sent by the Compute Service upon receipt of the <systemitem>SIGUSR1</systemitem> signal. This report is a general-purpose error report, including a complete report of the service's current state, and is sent to <systemitem>stderr</systemitem>."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:55(para)
-msgid "For example, if you redirect error output to <filename>nova-api-err.log</filename> using <placeholder-1/>, resulting in the process ID 8675, you can then run:"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:59(para)
-msgid "This command triggers the Guru Meditation report to be printed to <filename>/var/log/nova/nova-api-err.log</filename>."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:63(para)
-msgid "Package Displays information about the package to which the process belongs, including version information."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:65(para)
-msgid "Threads Displays stack traces and thread IDs for each of the threads within the process."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:67(para)
-msgid "Green Threads Displays stack traces for each of the green threads within the process (green threads do not have thread IDs)."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:69(para)
-msgid "Configuration Lists all configuration options currently accessible through the CONF object for the current process."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:61(para)
-msgid "The report has the following sections: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:72(para)
-msgid "For more information, see <link href=\"http://docs.openstack.org/developer/nova/devref/gmr.html\">Guru Meditation Reports</link>."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:77(title)
-msgid "Common errors and fixes for Compute"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:78(para)
-msgid "The <link href=\"ask.openstack.org\">ask.openstack.org</link> site offers a place to ask and answer questions, and you can also mark questions as frequently asked questions. This section describes some errors people have posted previously. Bugs are constantly being fixed, so online resources are a great way to get the most up-to-date errors and fixes."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:86(title)
-msgid "Credential errors, 401, and 403 forbidden errors"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:93(para)
-msgid "<emphasis role=\"bold\">Manual method</emphasis>. Get get the <filename>novarc</filename> file from the project ZIP file, save existing credentials in case of override. and manually source the <filename>novarc</filename> file."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:103(para)
-msgid "<emphasis role=\"bold\">Script method</emphasis>. Generates <filename>novarc</filename> from the project ZIP file and sources it for you."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:88(para)
-msgid "Missing credentials cause a <errorcode>403</errorcode><errortext>forbidden</errortext> error. To resolve this issue, use one of these methods:<placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:110(para)
-msgid "When you run <systemitem class=\"service\">nova-api</systemitem> the first time, it generates the certificate authority information, including <filename>openssl.cnf</filename>. If you start the CA services before this, you might not be able to create your ZIP file. Restart the services. When your CA information is available, create your ZIP file."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:118(para)
-msgid "Also, check your HTTP proxy settings to see whether they cause problems with <filename>novarc</filename> creation."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:123(title)
-msgid "Instance errors"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:124(para)
-msgid "Sometimes a particular instance shows <literal>pending</literal> or you cannot SSH to it. Sometimes the image itself is the problem. For example, when you use flat manager networking, you do not have a DHCP server and certain images do not support interface injection; you cannot connect to them. The fix for this problem is to use an image that does support this method, such as Ubuntu, which obtains an IP address correctly with FlatManager network settings."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:134(para)
-msgid "To troubleshoot other possible problems with an instance, such as an instance that stays in a spawning state, check the directory for the particular instance under <filename>/var/lib/nova/instances</filename> on the <systemitem class=\"service\">nova-compute</systemitem> host and make sure that these files are present:"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:143(filename)
-msgid "libvirt.xml"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:146(filename)
-msgid "disk"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:149(filename)
-msgid "disk-raw"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:152(filename)
-msgid "kernel"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:155(filename)
-msgid "ramdisk"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:158(para)
-msgid "After the instance starts, <filename>console.log</filename>"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:162(para)
-msgid "If any files are missing, empty, or very small, the <systemitem class=\"service\">nova-compute</systemitem> service did not successfully download the images from the Image Service."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:167(para)
-msgid "Also check <filename>nova-compute.log</filename> for exceptions. Sometimes they do not appear in the console output."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:170(para)
-msgid "Next, check the log file for the instance in the <filename>/var/log/libvirt/qemu</filename> directory to see if it exists and has any useful error messages in it."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:174(para)
-msgid "Finally, from the <filename>/var/lib/nova/instances</filename> directory for the instance, see if this command returns an error:"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:181(title)
-msgid "Empty log output for Linux instances"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:182(para)
-msgid "You can view the log output of running instances from either the <guilabel>Log</guilabel> tab of the dashboard or the output of <placeholder-1/>. In some cases, the log output of a running Linux instance will be empty or only display a single character (for example, the <keycap>?</keycap> character)."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:189(para)
-msgid "This occurs when the Compute service attempts to retrieve the log output of the instance via a serial console while the instance itself is not configured to send output to the console. To rectify this, append the following parameters to kernel arguments specified in the instance's boot loader:"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:196(para)
-msgid "Upon rebooting, the instance will be configured to send output to the Compute service."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:201(title)
-msgid "Reset the state of an instance"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:202(para)
-msgid "If an instance remains in an intermediate state, such as <literal>deleting</literal>, you can use the <placeholder-1/> command to manually reset the state of an instance to an error state. You can then delete the instance. For example:"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:209(para)
-msgid "You can also use the <parameter>--active</parameter> parameter to force the instance back to an active state instead of an error state. For example:"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:215(title)
-msgid "Injection problems"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:216(para)
-msgid "If instances do not boot or boot slowly, investigate file injection as a cause."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:218(para)
-msgid "To disable injection in libvirt, set the following in <filename>nova.conf</filename>:"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml:223(para)
-msgid "If you have not enabled the configuration drive and you want to make user-specified files available from the metadata server for to improve performance and avoid boot failure if injection fails, you must disable injection."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_search_ip.xml:7(title)
-msgid "Search for an instance using IP address"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_search_ip.xml:8(para)
-msgid "You can search for an instance using the IP address parameter, <literal>--ip</literal>, with the <placeholder-1/> command."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_search_ip.xml:11(parameter) ./doc/common/section_cli_nova_search_ip.xml:14(parameter)
-msgid "ip"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_search_ip.xml:11(replaceable)
-msgid "IP_ADDRESS"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_search_ip.xml:12(para)
-msgid "The following example shows the results of a search on <filename>10.0.0.4</filename>."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_search_ip.xml:14(replaceable)
-msgid "10.0.0.4"
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml:7(title)
-msgid "Configure the Identity Service with SSL"
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml:8(para)
-msgid "You can configure the Identity Service to support two-way SSL."
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml:10(para)
-msgid "You must obtain the x509 certificates externally and configure them."
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml:12(para)
-msgid "The Identity Service provides a set of sample certificates in the <filename class=\"directory\">examples/pki/certs</filename> and <filename class=\"directory\">examples/pki/private</filename> directories:"
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml:18(title)
-msgid "Certificate types"
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml:20(term)
-msgid "cacert.pem"
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml:22(para)
-msgid "Certificate Authority chain to validate against."
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml:27(term)
-msgid "ssl_cert.pem"
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml:29(para)
-msgid "Public certificate for Identity Service server."
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml:34(term)
-msgid "middleware.pem"
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml:36(para)
-msgid "Public and private certificate for Identity Service middleware/client."
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml:41(term)
-msgid "cakey.pem"
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml:43(para)
-msgid "Private key for the CA."
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml:47(term)
-msgid "ssl_key.pem"
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml:49(para)
-msgid "Private key for the Identity Service server."
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml:55(para)
-msgid "You can choose names for these certificates. You can also combine the public/private keys in the same file, if you wish. These certificates are provided as an example."
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml:61(title)
-msgid "SSL configuration"
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml:62(para)
-msgid "To enable SSL with client authentication, modify the <literal>[ssl]</literal> section in the <filename>etc/keystone.conf</filename> file. The following SSL configuration example uses the included sample certificates:"
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml:74(title)
-msgid "Options"
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml:76(para)
-msgid "<literal>enable</literal>. True enables SSL. Default is False."
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml:80(para)
-msgid "<literal>certfile</literal>. Path to the Identity Service public certificate file."
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml:84(para)
-msgid "<literal>keyfile</literal>. Path to the Identity Service private certificate file. If you include the private key in the certfile, you can omit the keyfile."
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml:90(para)
-msgid "<literal>ca_certs</literal>. Path to the CA trust chain."
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml:94(para)
-msgid "<literal>cert_required</literal>. Requires client certificate. Default is False."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml:6(title)
-msgid "Stop and start an instance"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml:7(para)
-msgid "Use one of the following methods to stop and start an instance."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml:10(title)
-msgid "Pause and unpause an instance"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml:13(para)
-msgid "To pause an instance, run the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml:15(para)
-msgid "This command stores the state of the VM in RAM. A paused instance continues to run in a frozen state."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml:17(para)
-msgid "To unpause the instance, run the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml:23(title)
-msgid "Suspend and resume an instance"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml:25(para)
-msgid "Administrative users might want to suspend an instance if it is infrequently used or to perform system maintenance. When you suspend an instance, its VM state is stored on disk, all memory is written to disk, and the virtual machine is stopped. Suspending an instance is similar to placing a device in hibernation; memory and vCPUs become available to create other instances."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml:33(para)
-msgid "To initiate a hypervisor-level suspend operation, run the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml:38(para)
-msgid "To resume a suspended instance, run the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml:45(title)
-msgid "Shelve and unshelve an instance"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml:46(para)
-msgid "Shelving is useful if you have an instance that you are not using, but would like retain in your list of servers. For example, you can stop an instance at the end of a work week, and resume work again at the start of the next week. All associated data and resources are kept; however, anything still in memory is not retained. If a shelved instance is no longer needed, it can also be entirely removed."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml:51(para)
-msgid "You can complete the following shelving tasks:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml:53(term)
-msgid "Shelve an instance"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml:54(para)
-msgid "Shuts down the instance, and stores it together with associated data and resources (a snapshot is taken if not volume backed). Anything in memory is lost. Use the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml:57(replaceable) ./doc/common/section_cli_nova_startstop.xml:62(replaceable) ./doc/common/section_cli_nova_startstop.xml:69(replaceable)
-msgid "SERVERNAME"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml:60(term)
-msgid "Unshelve an instance"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml:61(para)
-msgid "Restores the instance:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml:65(term)
-msgid "Remove a shelved instance"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml:66(para)
-msgid "Removes the instance from the server; data and resource associations are deleted. If an instance is no longer needed, you can move that instance off the hypervisor in order to minimize resource usage:"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-components.xml:43(None)
-msgid "@@image: '../common/figures/objectstorage-buildingblocks.png'; md5=ed79466c8464513dbeaf1e0954280e5e"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-components.xml:86(None)
-msgid "@@image: '../common/figures/objectstorage-ring.png'; md5=a94e26734cec6980c3684d9e824eac2d"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-components.xml:126(None)
-msgid "@@image: '../common/figures/objectstorage-zones.png'; md5=1b1dc0abe6ea0c516f22ce399deb75ed"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-components.xml:144(None)
-msgid "@@image: '../common/figures/objectstorage-accountscontainers.png'; md5=4b15e5a202db5bde53c9b369058aeab8"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-components.xml:169(None)
-msgid "@@image: '../common/figures/objectstorage-partitions.png'; md5=2c161c2e92d6fefc8140ec86e79e9492"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-components.xml:195(None)
-msgid "@@image: '../common/figures/objectstorage-replication.png'; md5=9d55594d7f445764569ab04d8d4373b2"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-components.xml:222(None)
-msgid "@@image: '../common/figures/objectstorage-usecase.png'; md5=07480e7175b383171173775fb96d70d7"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:7(title)
-msgid "Components"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:8(para)
-msgid "The components that enable Object Storage to deliver high availability, high durability, and high concurrency are:"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:12(para)
-msgid "<emphasis role=\"bold\">Proxy servers.</emphasis> Handle all of the incoming API requests."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:16(para)
-msgid "<emphasis role=\"bold\">Rings.</emphasis> Map logical names of data to locations on particular disks."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:20(para)
-msgid "<emphasis role=\"bold\">Zones.</emphasis> Isolate data from other zones. A failure in one zone doesn’t impact the rest of the cluster because data is replicated across zones."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:25(para)
-msgid "<emphasis role=\"bold\">Accounts and containers.</emphasis> Each account and container are individual databases that are distributed across the cluster. An account database contains the list of containers in that account. A container database contains the list of objects in that container."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:31(para)
-msgid "<emphasis role=\"bold\">Objects.</emphasis> The data itself."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:34(para)
-msgid "<emphasis role=\"bold\">Partitions.</emphasis> A partition stores objects, account databases, and container databases and helps manage locations where data lives in the cluster."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:40(title)
-msgid "Object Storage building blocks"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:48(title)
-msgid "Proxy servers"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:49(para)
-msgid "Proxy servers are the public face of Object Storage and handle all of the incoming API requests. Once a proxy server receives a request, it determines the storage node based on the object's URL, for example, https://swift.example.com/v1/account/container/object. Proxy servers also coordinate responses, handle failures, and coordinate timestamps."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:54(para)
-msgid "Proxy servers use a shared-nothing architecture and can be scaled as needed based on projected workloads. A minimum of two proxy servers should be deployed for redundancy. If one proxy server fails, the others take over."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:59(title)
-msgid "Rings"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:60(para)
-msgid "A ring represents a mapping between the names of entities stored on disk and their physical locations. There are separate rings for accounts, containers, and objects. When other components need to perform any operation on an object, container, or account, they need to interact with the appropriate ring to determine their location in the cluster."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:65(para)
-msgid "The ring maintains this mapping using zones, devices, partitions, and replicas. Each partition in the ring is replicated, by default, three times across the cluster, and partition locations are stored in the mapping maintained by the ring. The ring is also responsible for determining which devices are used for handoff in failure scenarios."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:70(para)
-msgid "Data can be isolated into zones in the ring. Each partition replica is guaranteed to reside in a different zone. A zone could represent a drive, a server, a cabinet, a switch, or even a data center."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:73(para)
-msgid "The partitions of the ring are equally divided among all of the devices in the Object Storage installation. When partitions need to be moved around (for example, if a device is added to the cluster), the ring ensures that a minimum number of partitions are moved at a time, and only one replica of a partition is moved at a time."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:77(para)
-msgid "Weights can be used to balance the distribution of partitions on drives across the cluster. This can be useful, for example, when differently sized drives are used in a cluster."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:80(para)
-msgid "The ring is used by the proxy server and several background processes (like replication)."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:83(title)
-msgid "The <emphasis role=\"bold\">ring</emphasis>"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:90(para)
-msgid "These rings are externally managed, in that the server processes themselves do not modify the rings, they are instead given new rings modified by other tools."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:92(para)
-msgid "The ring uses a configurable number of bits from a path’s MD5 hash as a partition index that designates a device. The number of bits kept from the hash is known as the partition power, and 2 to the partition power indicates the partition count. Partitioning the full MD5 hash ring allows other parts of the cluster to work in batches of items at once which ends up either more efficient or at least less complex than working with each item separately or the entire cluster all at once."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:101(para)
-msgid "Another configurable value is the replica count, which indicates how many of the partition-device assignments make up a single ring. For a given partition number, each replica’s device will not be in the same zone as any other replica's device. Zones can be used to group devices based on physical locations, power separations, network separations, or any other attribute that would improve the availability of multiple replicas at the same time."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:109(title) ./doc/common/section_objectstorage-components.xml:123(title)
-msgid "Zones"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:110(para)
-msgid "Object Storage allows configuring zones in order to isolate failure boundaries. Each data replica resides in a separate zone, if possible. At the smallest level, a zone could be a single drive or a grouping of a few drives. If there were five object storage servers, then each server would represent its own zone. Larger deployments would have an entire rack (or multiple racks) of object servers, each representing a zone. The goal of zones is to allow the cluster to tolerate significant outages of storage servers without losing all replicas of the data."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:117(para)
-msgid "As mentioned earlier, everything in Object Storage is stored, by default, three times. Swift will place each replica \"as-uniquely-as-possible\" to ensure both high availability and high durability. This means that when chosing a replica location, Object Storage chooses a server in an unused zone before an unused server in a zone that already has a replica of the data."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:130(para)
-msgid "When a disk fails, replica data is automatically distributed to the other zones to ensure there are three copies of the data."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:134(title) ./doc/common/section_objectstorage-components.xml:141(title)
-msgid "Accounts and containers"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:135(para)
-msgid "Each account and container is an individual SQLite database that is distributed across the cluster. An account database contains the list of containers in that account. A container database contains the list of objects in that container."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:148(para)
-msgid "To keep track of object data locations, each account in the system has a database that references all of its containers, and each container database references each object."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:153(title) ./doc/common/section_objectstorage-components.xml:166(title)
-msgid "Partitions"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:154(para)
-msgid "A partition is a collection of stored data, including account databases, container databases, and objects. Partitions are core to the replication system."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:156(para)
-msgid "Think of a partition as a bin moving throughout a fulfillment center warehouse. Individual orders get thrown into the bin. The system treats that bin as a cohesive entity as it moves throughout the system. A bin is easier to deal with than many little things. It makes for fewer moving parts throughout the system."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:160(para)
-msgid "System replicators and object uploads/downloads operate on partitions. As the system scales up, its behavior continues to be predictable because the number of partitions is a fixed number."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:163(para)
-msgid "Implementing a partition is conceptually simple, a partition is just a directory sitting on a disk with a corresponding hash table of what it contains."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:175(title)
-msgid "Replicators"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:176(para)
-msgid "In order to ensure that there are three copies of the data everywhere, replicators continuously examine each partition. For each local partition, the replicator compares it against the replicated copies in the other zones to see if there are any differences."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:180(para)
-msgid "The replicator knows if replication needs to take place by examining hashes. A hash file is created for each partition, which contains hashes of each directory in the partition. Each of the three hash files is compared. For a given partition, the hash files for each of the partition's copies are compared. If the hashes are different, then it is time to replicate, and the directory that needs to be replicated is copied over."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:186(para)
-msgid "This is where partitions come in handy. With fewer things in the system, larger chunks of data are transferred around (rather than lots of little TCP connections, which is inefficient) and there is a consistent number of hashes to compare."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:189(para)
-msgid "The cluster eventually has a consistent behavior where the newest data has a priority."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:199(para)
-msgid "If a zone goes down, one of the nodes containing a replica notices and proactively copies data to a handoff location."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:203(title)
-msgid "Use cases"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:204(para)
-msgid "The following sections show use cases for object uploads and downloads and introduce the components."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:206(title)
-msgid "Upload"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:207(para)
-msgid "A client uses the REST API to make a HTTP request to PUT an object into an existing container. The cluster receives the request. First, the system must figure out where the data is going to go. To do this, the account name, container name, and object name are all used to determine the partition where this object should live."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:211(para)
-msgid "Then a lookup in the ring figures out which storage nodes contain the partitions in question."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:213(para)
-msgid "The data is then sent to each storage node where it is placed in the appropriate partition. At least two of the three writes must be successful before the client is notified that the upload was successful."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:216(para)
-msgid "Next, the container database is updated asynchronously to reflect that there is a new object in it."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:219(title)
-msgid "Object Storage in use"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:228(title)
-msgid "Download"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml:229(para)
-msgid "A request comes in for an account/container/object. Using the same consistent hashing, the partition name is generated. A lookup in the ring reveals which storage nodes contain that partition. A request is made to one of the storage nodes to fetch the object and, if that fails, requests are made to the other nodes."
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml:10(title)
-msgid "Storage concepts"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml:11(para)
-msgid "The OpenStack stack uses the following storage types:"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml:13(caption)
-msgid "Storage types"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml:19(td)
-msgid "On-instance / ephemeral"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml:20(td)
-msgid "Block storage (cinder)"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml:26(td)
-msgid "Runs operating systems and provides scratch space"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml:27(td)
-msgid "Used for adding additional persistent storage to a virtual machine (VM)"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml:29(td)
-msgid "Used for storing virtual machine images and data"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml:32(td)
-msgid "Persists until VM is terminated"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml:33(td) ./doc/common/section_storage-concepts.xml:34(td)
-msgid "Persists until deleted"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml:37(td) ./doc/common/section_storage-concepts.xml:38(td)
-msgid "Access associated with a VM"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml:39(td)
-msgid "Available from anywhere"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml:42(td)
-msgid "Implemented as a filesystem underlying OpenStack Compute"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml:44(td)
-msgid "Mounted via OpenStack Block Storage controlled protocol (for example, iSCSI)"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml:46(td)
-msgid "REST API"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml:49(td)
-msgid "Administrator configures size setting, based on flavors"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml:51(td)
-msgid "Sizings based on need"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml:52(td)
-msgid "Easily scalable for future growth"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml:55(td)
-msgid "Example: 10GB first disk, 30GB/core second disk"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml:56(td)
-msgid "Example: 1TB \"extra hard drive\""
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml:57(td)
-msgid "Example: 10s of TBs of data set storage"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml:64(para)
-msgid "<emphasis>You cannot use OpenStack Object Storage like a traditional hard drive.</emphasis> The Object Storage relaxes some of the constraints of a POSIX-style file system to get other gains. You can access the objects through an API which uses HTTP. Subsequently you don't have to provide atomic operations (that is, relying on eventual consistency), you can scale a storage system easily and avoid a central point of failure."
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml:73(para)
-msgid "<emphasis>The OpenStack Image Service is used to manage the virtual machine images in an OpenStack cluster, not store them.</emphasis> It provides an abstraction to different methods for storage - a bridge to the storage, not the storage itself."
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml:80(para)
-msgid "<emphasis>The OpenStack Object Storage can function on its own.</emphasis> The Object Storage (swift) product can be used independently of the Compute (nova) product."
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml:62(para)
-msgid "You should note that:<placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:6(title)
-msgid "Launch instances"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:7(para) ./doc/common/section_dashboard_launch_instances_from_image.xml:8(para)
-msgid "Instances are virtual machines that run inside the cloud."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:9(para)
-msgid "Before you can launch an instance, gather the following parameters:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:13(para)
-msgid "The <emphasis role=\"bold\">instance source</emphasis> can be an image, snapshot, or block storage volume that contains an image or snapshot."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:18(para)
-msgid "A <emphasis role=\"bold\">name</emphasis> for your instance."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:21(para) ./doc/common/section_dashboard_launch_instances_from_image.xml:37(para)
-msgid "The <emphasis role=\"bold\">flavor</emphasis> for your instance, which defines the compute, memory, and storage capacity of nova computing instances. A flavor is an available hardware configuration for a server. It defines the size of a virtual server that can be launched."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:29(para)
-msgid "Any <emphasis role=\"bold\">user data</emphasis> files. A user data file is a special key in the metadata service that holds a file that cloud-aware applications in the guest instance can access. For example, one application that uses user data is the <link href=\"https://help.ubuntu.com/community/CloudInit\">cloud-init</link> system, which is an open-source package from Ubuntu that is available on various Linux distributions and that handles early initialization of a cloud instance."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:42(para) ./doc/common/section_dashboard_launch_instances_from_image.xml:45(para)
-msgid "Access and security credentials, which include one or both of the following credentials:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:46(para)
-msgid "A <emphasis role=\"bold\">key pair</emphasis> for your instance, which are SSH credentials that are injected into images when they are launched. For the key pair to be successfully injected, the image must contain the <literal>cloud-init</literal> package. Create at least one key pair for each project. If you already have generated a key pair with an external tool, you can import it into OpenStack. You can use the key pair for multiple instances that belong to that project."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:60(para)
-msgid "A <emphasis role=\"bold\">security group</emphasis> that defines which incoming network traffic is forwarded to instances. Security groups hold a set of firewall policies, known as <emphasis role=\"italic\">security group rules</emphasis>."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:71(para)
-msgid "If needed, you can assign a <emphasis role=\"bold\">floating (public) IP address</emphasis> to a running instance."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:76(para)
-msgid "You can also attach a block storage device, or <emphasis role=\"bold\">volume</emphasis>, for persistent storage."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:82(para)
-msgid "Instances that use the default security group cannot, by default, be accessed from any IP address outside of the cloud. If you want those IP addresses to access the instances, you must modify the rules for the default security group."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:87(para)
-msgid "You can also assign a floating IP address to a running instance to make it accessible from outside the cloud. See <xref linkend=\"manage_ip_addresses\"/>."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:91(para)
-msgid "After you gather the parameters that you need to launch an instance, you can launch it from an <link linkend=\"launch_from_image\">image</link> or a <link linkend=\"boot_from_volume\">volume</link>. You can launch an instance directly from one of the available OpenStack images or from an image that you have copied to a persistent volume. The OpenStack Image Service provides a pool of images that are accessible to members of different projects."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:101(title)
-msgid "Gather parameters to launch an instance"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:103(para)
-msgid "Before you begin, source the OpenStack RC file."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:108(para)
-msgid "Note the ID of the flavor that you want to use for your instance:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:123(para)
-msgid "Note the ID of the image from which you want to boot your instance:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:131(para)
-msgid "You can also filter the image list by using <placeholder-1/> to find a specific image, as follows:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:138(para)
-msgid "List the available security groups:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:140(para)
-msgid "If you are an admin user, specify the <option>--all-tenants</option> parameter to list groups for all tenants."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:145(para)
-msgid "Note the ID of the security group that you want to use for your instance:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:151(para)
-msgid "If you have not created any security groups, you can assign the instance to only the default security group."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:154(para)
-msgid "You can view rules for a specified security group:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:159(para)
-msgid "List the available key pairs and note the name of the key pair that you use for SSH access."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:168(title) ./doc/common/section_dashboard_launch_instances_from_image.xml:6(title)
-msgid "Launch an instance from an image"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:171(para)
-msgid "After you gather required parameters, run the following command to launch an instance. Specify the server name, flavor ID, and image ID."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:174(para)
-msgid "Optionally, you can provide a key name for access control and a security group for security. You can also include metadata key and value pairs. For example, you can add a description for your server by providing the <parameter>--meta description=\"My Server\"</parameter> parameter."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:181(para)
-msgid "You can pass user data in a local file at instance launch by using the <parameter>--user-data <replaceable>USER-DATA-FILE</replaceable></parameter> parameter."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:186(replaceable)
-msgid "FLAVOR_ID"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:186(replaceable)
-msgid "KEY_NAME"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:187(replaceable)
-msgid "USER_DATA_FILE"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:187(replaceable)
-msgid "SEC_GROUP"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:187(replaceable)
-msgid "KEY=VALUE"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:189(para)
-msgid "The following command launches the <literal>MyCirrosServer</literal> instance with the <literal>m1.small</literal> flavor (ID of <literal>1</literal>), <literal>cirros-0.3.2-x86_64-uec</literal> image (ID of <literal>397e713c-b95b-4186-ad46-6126863ea0a9</literal>), <literal>default</literal> security group, <literal>KeyPair01</literal> key, and a user data file called <filename>cloudinit.file</filename>:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:202(replaceable)
-msgid "myCirrosServer"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:203(para)
-msgid "Depending on the parameters that you provide, the command returns a list of server properties."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:206(para)
-msgid "A status of <literal>BUILD</literal> indicates that the instance has started, but is not yet online."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:209(para)
-msgid "A status of <literal>ACTIVE</literal> indicates that the instance is active."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:241(para)
-msgid "Copy the server ID value from the <literal>id</literal> field in the output. You use this ID to get details for or delete your server."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:245(para)
-msgid "Copy the administrative password value from the <literal>adminPass</literal> field. You use this value to log in to your server."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:249(para)
-msgid "You can also place arbitrary local files into the instance file system at creation time by using the <option>--file &lt;dst-path=src-path&gt;</option> option. You can store up to five files. For example, if you have a special authorized keys file named <filename>special_authorized_keysfile</filename> that you want to put on the instance rather than using the regular SSH key injection, you can use the <option>--file</option> option as shown in the following example:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:266(para)
-msgid "Check if the instance is online:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:268(para)
-msgid "The list shows the ID, name, status, and private (and if assigned, public) IP addresses for all instances in the project to which you belong:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:278(para)
-msgid "If the status for the instance is ACTIVE, the instance is online."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:280(para)
-msgid "To view the available options for the <placeholder-1/> command, run the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml:287(para)
-msgid "If you did not provide a key pair, security groups, or rules, you can access the instance only from inside the cloud through VNC. Even pinging the instance is not possible."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml:6(title)
-msgid "Integrate Identity with LDAP"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml:7(para)
-msgid "Identity Service supports integration with an existing LDAP directory for authentication and authorization services."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml:11(para)
-msgid "For OpenStack Identity to access an LDAP back end, you must enable the <option>authlogin_nsswitch_use_ldap</option> boolean value for SELinux on the Identity server. To enable and make the option persistent across reboots:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml:18(para)
-msgid "You can integrate Identity with a single LDAP server."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml:21(para)
-msgid "To configure Identity, set options in the <filename>/etc/keystone/keystone.conf</filename> file. Modify these examples as needed."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml:25(title)
-msgid "To integrate Identity with LDAP"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml:27(para)
-msgid "Enable the LDAP driver in the <filename>keystone.conf</filename> file:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml:34(para)
-msgid "Define the destination LDAP server in the <filename>keystone.conf</filename> file:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml:45(para)
-msgid "Create the organizational units (OU) in the LDAP directory, and define their corresponding location in the <filename>keystone.conf</filename> file:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml:58(para)
-msgid "These schema attributes are extensible for compatibility with various schemas. For example, this entry maps to the <systemitem>person</systemitem> attribute in Active Directory:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml:67(para)
-msgid "A read-only implementation is recommended for LDAP integration. These permissions are applied to object types in the <filename>keystone.conf</filename> file:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml:85(para)
-msgid "Restart the Identity service:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml:87(para)
-msgid "During service restart, authentication and authorization are unavailable."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml:92(title)
-msgid "Additional LDAP integration settings"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml:93(para)
-msgid "Set these options in the <filename>keystone.conf</filename> file."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml:98(term)
-msgid "Filters"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml:100(para)
-msgid "Use filters to control the scope of data presented through LDAP."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml:109(term)
-msgid "LDAP Account Status"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml:111(para)
-msgid "Mask account status values for compatibility with various directory services. Superfluous accounts are filtered with <systemitem>user_filter</systemitem>."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml:115(para)
-msgid "For example, you can mask Active Directory account status attributes in the <filename>keystone.conf</filename> file:"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml:106(None)
-msgid "@@image: 'figures/launch_instances.png'; md5=8a7e6864bce97f6478db572daf3ef5de"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml:164(None)
-msgid "@@image: 'figures/instances.png'; md5=6b0f5cb3009d447334ff8b5c5b2cd121"
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml:10(para)
-msgid "You can launch an instance directly from one of the available OpenStack images. The OpenStack Image Service provides a pool of images that are accessible to members of different projects. When you launch an instance from an image, OpenStack creates a local copy of the image on the respective compute node where the instance is started."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml:16(para)
-msgid "Alternatively, you can launch an instance from an image that you have copied to a persistent volume."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml:18(para)
-msgid "To launch an instance, specify the following parameters:"
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml:22(para)
-msgid "The <guilabel>instance source</guilabel>, which is an image or snapshot. Alternatively, you can boot from a volume, which is block storage, to which you've copied an image or snapshot."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml:28(para)
-msgid "The <guilabel>image</guilabel> or <guilabel>snapshot</guilabel>, which represents the operating system."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml:33(para)
-msgid "A <guilabel>name</guilabel> for your instance."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml:49(para)
-msgid "A <emphasis role=\"bold\">keypair</emphasis> for your instance, which are SSH credentials that are injected into images when they are launched. For this to work, the image must contain the <literal>cloud-init</literal> package. Create at least one keypair for each project. If you already have generated a keypair with an external tool, you can import it into OpenStack. You can use the keypair for multiple instances that belong to that project."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml:62(para)
-msgid "A <emphasis role=\"bold\">security group</emphasis>, which defines which incoming network traffic is forwarded to instances. Security groups hold a set of firewall policies, known as <emphasis role=\"italic\">security group rules</emphasis>."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml:73(para)
-msgid "If needed, you can assign a <emphasis role=\"bold\">floating (public) IP address</emphasis> to a running instance and attach a block storage device, or volume, for persistent storage."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml:80(title)
-msgid "To launch an instance:"
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml:82(para)
-msgid "Log in to the OpenStack dashboard."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml:85(para)
-msgid "If you are a member of multiple projects, select a project from the drop-down list at the top of the <guilabel>Project</guilabel> tab."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml:90(para)
-msgid "Click the <guilabel>Images &amp; Snapshot</guilabel> category."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml:92(para)
-msgid "The dashboard shows the images that have been uploaded to OpenStack Image Service and are available for this project."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml:100(title)
-msgid "OpenStack dashboard - Launch Instances window"
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml:97(para)
-msgid "Select an image and click <guibutton>Launch</guibutton>. The <guilabel>Launch Image</guilabel> window appears: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml:112(para)
-msgid "Specify the following parameters:"
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml:116(para)
-msgid "Enter an instance name to assign to the virtual machine."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml:120(para)
-msgid "From the <guilabel>Flavor</guilabel> drop-down list, select the size of the virtual machine to launch."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml:125(para)
-msgid "Optionally, select a keypair."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml:126(para)
-msgid "In case an image uses a static root password or a static key set (neither is recommended), you do not need to provide a keypair on starting the instance."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml:132(para)
-msgid "In <guilabel>Instance Count</guilabel>, enter the number of virtual machines to launch from this image."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml:137(para)
-msgid "Assign the instance to the default security group. If you added rules to this group, the instance implements these rules."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml:150(para)
-msgid "Click <guibutton>Launch Instance</guibutton>. The instance is launched on any of the compute nodes in the cloud."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml:155(para)
-msgid "After you have launched an instance, switch to the <guilabel>Instances &amp; Volumes</guilabel> category to view the instance name, its (private or public) IP address, size, status, task, and power state."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml:160(title)
-msgid "OpenStack dashboard - Instances"
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml:168(para)
-msgid "If you did not provide a keypair on starting and have not touched security groups or rules so far, by default the instance can only be accessed from inside the cloud through VNC at this point. Even pinging the instance is not possible."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml:6(title)
-msgid "Troubleshoot the Identity service"
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml:7(para)
-msgid "To troubleshoot the Identity service, review the logs in the <filename>/var/log/keystone/keystone.log</filename> file."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml:10(para)
-msgid "Use the <filename>/etc/keystone/logging.conf</filename> file to configure the location of log files."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml:13(para)
-msgid "The logs show the components that have come in to the WSGI request, and ideally show an error that explains why an authorization request failed. If you do not see the request in the logs, run keystone with <parameter>--debug</parameter> parameter. Pass the <parameter>--debug</parameter> parameter before the command parameters."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml:20(title)
-msgid "Debug PKI middleware"
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml:21(para)
-msgid "If you receive an <literal>Invalid OpenStack Identity Credentials</literal> message when you talk to an OpenStack service, it might be caused by the changeover from UUID tokens to PKI tokens in the Grizzly release. Learn how to troubleshoot this error."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml:26(para)
-msgid "The PKI-based token validation scheme relies on certificates from Identity that are fetched through HTTP and stored in a local directory. The location for this directory is specified by the <literal>signing_dir</literal> configuration option. In your services configuration file, look for a section like this:"
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml:41(para)
-msgid "If your service lacks this stanza, the <link href=\"https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/middleware/auth_token.py#L198\">keystoneclient/middleware/auth_token.py</link> file specifies the defaults. If no value is specified for this directory, it <link href=\"https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/middleware/auth_token.py#L299\">defaults to a secure temporary directory.</link> Initialization code for the service checks that the directory exists and is writable. If it does not exist, the code tries to create it. If this fails, the service fails to start. However, it often succeeds but problems occur later."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml:53(para)
-msgid "The first thing to check is that the <literal>signing_dir</literal> does, in fact, exist. If it does, check for the presence of the certificate files inside there:"
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml:64(para)
-msgid "This directory contains two certificates and the token revocation list. If these files are not present, your service cannot fetch them from Identity. To troubleshoot, try to talk to Identity to make sure it correctly serves files, as follows:"
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml:70(para)
-msgid "This command fetches the signing certificate:"
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml:81(para)
-msgid "Note the expiration dates of the certificate:"
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml:84(para)
-msgid "The token revocation list is updated once a minute, but the certificates are not. One possible problem is that the certificates are the wrong files or garbage. You can remove these files and run another command against your server: They are fetched on demand."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml:89(para)
-msgid "The Identity service log should show the access of the certificate files. You might have to turn up your logging levels. Set <literal>debug = True</literal> and <literal>verbose = True</literal> in your Identity configuration file and restart the Identity server."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml:98(para)
-msgid "If the files do not appear in your directory after this, it is likely one of the following issues:"
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml:102(para)
-msgid "Your service is configured incorrectly and cannot talk to Identity. Check the <literal>auth_port</literal> and <literal>auth_host</literal> values and make sure that you can talk to that service through cURL, as shown previously."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml:110(para)
-msgid "Your signing directory is not writable. Use the <placeholder-1/> command to change its permissions so that the service (POSIX) user can write to it. Verify the change through <placeholder-2/> and <placeholder-3/> commands."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml:118(para)
-msgid "The SELinux policy is denying access to the directory."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml:122(para)
-msgid "SELinux troubles often occur when you use Fedora/RHEL-based packages and you choose configuration options that do not match the standard policy. Run the <placeholder-1/> command. If that makes a difference, you should relabel the directory. If you are using a sub-directory of the <filename>/var/cache/</filename> directory, run the following command:"
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml:131(para)
-msgid "If you are not using a <filename>/var/cache</filename> sub-directory, you should. Modify the <literal>signing_dir</literal> configuration option for your service and restart."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml:135(para)
-msgid "Set back to <literal>setenforce enforcing</literal> to confirm that your changes solve the problem."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml:137(para)
-msgid "If your certificates are fetched on demand, the PKI validation is working properly. Most likely, the token from Identity is not valid for the operation you are attempting to perform, and your user needs a different role for the operation."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml:144(title)
-msgid "Debug signing key file errors"
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml:145(para)
-msgid "If an error occurs when the signing key file opens, it is possible that the person who ran the <placeholder-1/> command to generate certificates and keys did not use the correct user. When you run the <placeholder-2/> command, Identity generates a set of certificates and keys in <filename>/etc/keystone/ssl*</filename>, which is owned by root:root."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml:154(para)
-msgid "This can present a problem when you run the Identity daemon under the keystone user account (nologin) when you try to run PKI. Unless you run the <placeholder-1/> command against the files keystone:keystone or run the <placeholder-2/> command with the <parameter>--keystone-user</parameter> and <parameter>--keystone-group</parameter> parameters, you get an error, as follows:"
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml:172(title)
-msgid "Flush expired tokens from the token database table"
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml:174(para)
-msgid "As you generate tokens, the token database table on the Identity server grows. To clear the token table, an administrative user must run the <placeholder-1/> command to flush the tokens. When you flush tokens, expired tokens are deleted and traceability is eliminated."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml:180(para)
-msgid "Use <placeholder-1/> to schedule this command to run frequently based on your workload. For large workloads, running it every minute is recommended."
-msgstr ""
-
-#: ./doc/common/section_compute_config-firewalls.xml:6(title)
-msgid "Compute service node firewall requirements"
-msgstr ""
-
-#: ./doc/common/section_compute_config-firewalls.xml:7(para)
-msgid "Console connections for virtual machines, whether direct or through a proxy, are received on ports <literal>5900</literal> to <literal>5999</literal>. You must configure the firewall on each Compute service node to enable network traffic on these ports."
-msgstr ""
-
-#: ./doc/common/section_compute_config-firewalls.xml:11(title)
-msgid "Configure the service-node firewall"
-msgstr ""
-
-#: ./doc/common/section_compute_config-firewalls.xml:12(para)
-msgid "On the server that hosts the Compute service, log in as <systemitem>root</systemitem>."
-msgstr ""
-
-#: ./doc/common/section_compute_config-firewalls.xml:14(para)
-msgid "Edit the <filename>/etc/sysconfig/iptables</filename> file."
-msgstr ""
-
-#: ./doc/common/section_compute_config-firewalls.xml:20(para)
-msgid "Add an INPUT rule that allows TCP traffic on ports that range from <literal>5900</literal> to <literal>5999</literal>:"
-msgstr ""
-
-#: ./doc/common/section_compute_config-firewalls.xml:26(para)
-msgid "The new rule must appear before any INPUT rules that REJECT traffic."
-msgstr ""
-
-#: ./doc/common/section_compute_config-firewalls.xml:32(para)
-msgid "Save the changes to the <filename>/etc/sysconfig/iptables</filename> file."
-msgstr ""
-
-#: ./doc/common/section_compute_config-firewalls.xml:38(para)
-msgid "Restart the <systemitem>iptables</systemitem> service to ensure that the change takes effect."
-msgstr ""
-
-#: ./doc/common/section_compute_config-firewalls.xml:45(para)
-msgid "The <systemitem>iptables</systemitem> firewall now enables incoming connections to the Compute services. Repeat this process for each Compute service node."
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml:6(title)
-msgid "Customize the dashboard"
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml:7(para)
-msgid "Adapted from <link href=\"http://www.prestonlee.com/2012/05/09/how-to-custom-brand-the-openstack-horizon-dashboard/\">How To Custom Brand The OpenStack “Horizon” Dashboard</link>."
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml:11(para)
-msgid "You install the OpenStack dashboard through the <literal>openstack-dashboard</literal> package. You can customize the dashboard with your own colors, logo, and site title through a CSS file."
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml:15(para)
-msgid "Canonical also provides an <literal>openstack-dashboard-ubuntu-theme</literal> package that brands the Python-based Django interface."
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml:47(para)
-msgid "Create a graphical logo with a transparent background. The text <literal>TGen Cloud</literal> in this example is rendered through <filename>.png</filename> files of multiple sizes created with a graphics program."
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml:52(para)
-msgid "Use a 200×27 for the logged-in banner graphic, and 365×50 for the login screen graphic."
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml:56(para)
-msgid "Set the HTML title, which appears at the top of the browser window, by adding the following line to <filename>/etc/openstack-dashboard/local_settings.py</filename>:"
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml:59(code)
-msgid "SITE_BRANDING = \"Example, Inc. Cloud\""
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml:63(para)
-msgid "Upload your new graphic files to the following location: <filename>/usr/share/openstack-dashboard/openstack_dashboard/static/dashboard/img/</filename>"
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml:68(para)
-msgid "Create a CSS style sheet in the following directory: <filename>/usr/share/openstack-dashboard/openstack_dashboard/static/dashboard/css/</filename>"
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml:72(para)
-msgid "Edit your CSS file to override the Ubuntu customizations in the <filename>ubuntu.css</filename> file."
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml:75(para)
-msgid "Change the colors and image file names as appropriate, though the relative directory paths should be the same. The following example file shows you how to customize your CSS file:"
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml:114(para)
-msgid "Open the following HTML template in an editor: <filename>/usr/share/openstack-dashboard/openstack_dashboard/templates/_stylesheets.html</filename>"
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml:118(para)
-msgid "Add a line to include your <filename>custom.css</filename> file:"
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml:123(emphasis)
-msgid "&lt;link href='{{ STATIC_URL }}dashboard/css/custom.css' media='screen' rel='stylesheet' /&gt;"
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml:127(title)
-msgid "Restart Apache:"
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml:128(para) ./doc/common/section_dashboard_sessions.xml:180(para)
-msgid "On Ubuntu: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml:131(para)
-msgid "On Fedora, RHEL, CentOS: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml:134(para) ./doc/common/section_dashboard_sessions.xml:187(para)
-msgid "On openSUSE: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml:139(para)
-msgid "Reload the dashboard in your browser to view your changes."
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml:141(para)
-msgid "Modify your CSS file as appropriate."
-msgstr ""
-
-#: ./doc/common/section_cli_version.xml:6(title)
-msgid "Discover the version number for a client"
-msgstr ""
-
-#: ./doc/common/section_cli_version.xml:7(para)
-msgid "Run the following command to discover the version number for a client:"
-msgstr ""
-
-#: ./doc/common/section_cli_version.xml:9(replaceable) ./doc/common/section_cli_install.xml:208(replaceable) ./doc/common/section_cli_install.xml:210(replaceable) ./doc/common/section_cli_install.xml:222(replaceable) ./doc/common/section_cli_install.xml:228(replaceable) ./doc/common/section_cli_install.xml:236(replaceable) ./doc/common/section_cli_install.xml:239(replaceable)
-msgid "PROJECT"
-msgstr ""
-
-#: ./doc/common/section_cli_version.xml:10(para)
-msgid "For example, to see the version number for the <placeholder-1/> client, run the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_version.xml:14(para)
-msgid "The version number (2.15.0 in the example) is returned."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml:6(title)
-msgid "Groups"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml:7(para)
-msgid "A group is a collection of users. Administrators can create groups and add users to them. Then, rather than assign a role to each user individually, assign a role to the group. Every group is in a domain. Groups were introduced with the Identity API v3."
-msgstr ""
-
-#. TODO: eventually remove the last sentence, when v3 is
-#.              commonplace
-#: ./doc/common/section_keystone-concepts-group-management.xml:14(para)
-msgid "Identity API V3 provides the following group-related operations:"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml:18(para)
-msgid "Create a group"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml:21(para)
-msgid "Delete a group"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml:24(para)
-msgid "Update a group (change its name or description)"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml:28(para)
-msgid "Add a user to a group"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml:31(para)
-msgid "Remove a user from a group"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml:34(para)
-msgid "List group members"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml:37(para)
-msgid "List groups for a user"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml:40(para)
-msgid "Assign a role on a tenant to a group"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml:43(para)
-msgid "Assign a role on a domain to a group"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml:46(para)
-msgid "Query role assignments to groups"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml:50(para)
-msgid "The Identity service server might not allow all operations. For example, if using the Identity server with the LDAP Identity back end and group updates are disabled, then a request to create, delete, or update a group fails."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml:56(para)
-msgid "Here are a couple of examples:"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml:59(para)
-msgid "Group A is granted Role A on Tenant A. If User A is a member of Group A, when User A gets a token scoped to Tenant A, the token also includes Role A."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml:65(para)
-msgid "Group B is granted Role B on Domain B. If User B is a member of Domain B, if User B gets a token scoped to Domain B, the token also includes Role B."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:11(title)
-msgid "Orchestration command-line client"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:12(para)
-msgid "The <placeholder-1/> client is the command-line interface (CLI) for the Orchestration API and its extensions. This chapter documents <placeholder-2/> version 0.2.9."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:22(title)
-msgid "heat usage"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:39(para) ./doc/common/ch_cli_heat_commands.xml:506(para)
-msgid "Resume the stack."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:47(para) ./doc/common/ch_cli_heat_commands.xml:523(para)
-msgid "Suspend the stack."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:55(para) ./doc/common/ch_cli_heat_commands.xml:540(para)
-msgid "Retrieve build information."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:63(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use stack-create instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:71(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use stack-delete instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:79(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use stack-show instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:87(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use event-show instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:95(para) ./doc/common/ch_cli_heat_commands.xml:547(para)
-msgid "List events for a stack."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:103(para) ./doc/common/ch_cli_heat_commands.xml:575(para)
-msgid "Describe the event."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:111(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use template-show instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:119(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use stack-list instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:127(para) ./doc/common/ch_cli_heat_commands.xml:608(para)
-msgid "Show available outputs."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:135(para) ./doc/common/ch_cli_heat_commands.xml:625(para)
-msgid "Show a specific stack output."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:143(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use resource-show instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:151(para) ./doc/common/ch_cli_heat_commands.xml:650(para)
-msgid "Show list of resources belonging to a stack."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:159(para) ./doc/common/ch_cli_heat_commands.xml:667(para)
-msgid "List resource metadata."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:167(para) ./doc/common/ch_cli_heat_commands.xml:692(para)
-msgid "Describe the resource."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:175(para) ./doc/common/ch_cli_heat_commands.xml:717(para)
-msgid "Send a signal to a resource."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:183(para) ./doc/common/ch_cli_heat_commands.xml:762(para)
-msgid "Generate a template based on a resource."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:191(para) ./doc/common/ch_cli_heat_commands.xml:790(para)
-msgid "List the available resource types."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:199(para) ./doc/common/ch_cli_heat_commands.xml:797(para)
-msgid "Show the resource type."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:207(para) ./doc/common/ch_cli_heat_commands.xml:814(para)
-msgid "Abandon the stack."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:215(para) ./doc/common/ch_cli_heat_commands.xml:834(para)
-msgid "Adopt a stack."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:223(para) ./doc/common/ch_cli_heat_commands.xml:932(para)
-msgid "Create the stack."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:231(para) ./doc/common/ch_cli_heat_commands.xml:1019(para)
-msgid "Delete the stack(s)."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:239(para) ./doc/common/ch_cli_heat_commands.xml:1037(para)
-msgid "List the user's stacks."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:247(para) ./doc/common/ch_cli_heat_commands.xml:1076(para)
-msgid "Preview the stack."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:255(para) ./doc/common/ch_cli_heat_commands.xml:1154(para)
-msgid "Describe the stack."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:263(para) ./doc/common/ch_cli_heat_commands.xml:1173(para)
-msgid "Update the stack."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:271(para) ./doc/common/ch_cli_heat_commands.xml:1243(para)
-msgid "Get the template for the specified stack."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:279(para) ./doc/common/ch_cli_heat_commands.xml:1261(para)
-msgid "Validate a template with parameters."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:287(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use stack-update instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:295(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use template-validate instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:320(title)
-msgid "heat optional arguments"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:333(para)
-msgid "Defaults to <code>env[HEATCLIENT_DEBUG]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:349(para)
-msgid "Explicitly allow the client to perform \"insecure\" SSL (https) requests. The server's certificate will not be verified against any certificate authorities. This option should be used with caution."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:370(para)
-msgid "Path of client key to use in SSL connection.This option is not necessary if your key is prepended to your cert file."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:380(para)
-msgid "Path of CA SSL certificate(s) used to verify the remote server's certificate. Without this option the client looks for the default system CA certificates."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:390(para)
-msgid "Number of seconds to wait for an API response, defaults to system socket timeout"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:455(para)
-msgid "Do not contact keystone for a token. Defaults to <code>env[OS_NO_CLIENT_AUTH]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:464(para)
-msgid "Defaults to <code>env[HEAT_URL]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:472(para)
-msgid "Defaults to <code>env[HEAT_API_VERSION]</code> or 1."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:496(para)
-msgid "Send os-username and os-password to heat."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:504(title)
-msgid "heat action-resume command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:513(para)
-msgid "Name or ID of stack to resume."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:521(title)
-msgid "heat action-suspend command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:530(para)
-msgid "Name or ID of stack to suspend."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:538(title)
-msgid "heat build-info command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:545(title)
-msgid "heat event-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:554(para) ./doc/common/ch_cli_heat_commands.xml:582(para)
-msgid "Name or ID of stack to show the events for."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:565(para)
-msgid "Name of the resource to filter events by."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:573(title)
-msgid "heat event-show command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:590(para)
-msgid "Name of the resource the event belongs to."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:598(para)
-msgid "ID of event to display details for."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:606(title)
-msgid "heat output-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:615(para) ./doc/common/ch_cli_heat_commands.xml:632(para)
-msgid "Name or ID of stack to query."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:623(title)
-msgid "heat output-show command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:640(para)
-msgid "Name of an output to display."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:648(title)
-msgid "heat resource-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:657(para)
-msgid "Name or ID of stack to show the resources for."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:665(title)
-msgid "heat resource-metadata command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:674(para)
-msgid "Name or ID of stack to show the resource metadata for."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:682(para)
-msgid "Name of the resource to show the metadata for."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:690(title)
-msgid "heat resource-show command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:699(para)
-msgid "Name or ID of stack to show the resource for."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:707(para)
-msgid "Name of the resource to show the details for."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:715(title)
-msgid "heat resource-signal command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:724(para)
-msgid "Name or ID of stack the resource belongs to."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:732(para)
-msgid "Name of the resource to signal."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:743(para)
-msgid "JSON Data to send to the signal handler."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:751(para)
-msgid "File containing JSON data to send to the signal handler."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:760(title)
-msgid "heat resource-template command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:769(para)
-msgid "Name of the resource to generate a template for."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:780(para)
-msgid "The template output format, one of: yaml, json."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:788(title)
-msgid "heat resource-type-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:795(title)
-msgid "heat resource-type-show command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:804(para)
-msgid "Resource type to get the details for."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:812(title)
-msgid "heat stack-abandon command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:821(para)
-msgid "Name or ID of stack to abandon."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:829(title)
-msgid "heat stack-adopt command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:841(para)
-msgid "Name of the stack to adopt."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:852(para) ./doc/common/ch_cli_heat_commands.xml:950(para) ./doc/common/ch_cli_heat_commands.xml:1094(para) ./doc/common/ch_cli_heat_commands.xml:1191(para) ./doc/common/ch_cli_heat_commands.xml:1276(para)
-msgid "Path to the template."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:860(para) ./doc/common/ch_cli_heat_commands.xml:958(para) ./doc/common/ch_cli_heat_commands.xml:1102(para) ./doc/common/ch_cli_heat_commands.xml:1199(para) ./doc/common/ch_cli_heat_commands.xml:1284(para)
-msgid "Path to the environment."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:868(para) ./doc/common/ch_cli_heat_commands.xml:966(para) ./doc/common/ch_cli_heat_commands.xml:1110(para) ./doc/common/ch_cli_heat_commands.xml:1207(para) ./doc/common/ch_cli_heat_commands.xml:1268(para)
-msgid "URL of template."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:876(para)
-msgid "URL to retrieve template object (e.g from swift)."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:884(para) ./doc/common/ch_cli_heat_commands.xml:982(para)
-msgid "Stack creation timeout in minutes. <emphasis>DEPRECATED</emphasis> use --timeout instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:893(para) ./doc/common/ch_cli_heat_commands.xml:991(para)
-msgid "Stack creation timeout in minutes."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:901(para)
-msgid "Path to adopt stack data file."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:909(para) ./doc/common/ch_cli_heat_commands.xml:999(para)
-msgid "Enable rollback on create/update failure."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:917(para) ./doc/common/ch_cli_heat_commands.xml:1007(para) ./doc/common/ch_cli_heat_commands.xml:1231(para)
-msgid "Parameter values used to create the stack. This can be specified multiple times, or once with parameters separated by a semicolon."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:927(title)
-msgid "heat stack-create command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:939(para)
-msgid "Name of the stack to create."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:974(para) ./doc/common/ch_cli_heat_commands.xml:1215(para) ./doc/common/ch_cli_heat_commands.xml:1292(para)
-msgid "URL to retrieve template object (e.g. from swift)."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:1017(title)
-msgid "heat stack-delete command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:1026(para)
-msgid "Name or ID of stack(s) to delete."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:1034(title)
-msgid "heat stack-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:1044(para)
-msgid "Filter parameters to apply on returned stacks. This can be specified multiple times, or once with parameters separated by a semicolon."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:1054(para)
-msgid "Limit the number of stacks returned."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:1062(para)
-msgid "Only return stacks that appear after the given stack ID."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:1071(title)
-msgid "heat stack-preview command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:1083(para)
-msgid "Name of the stack to preview."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:1118(para)
-msgid "URL to retrieve template object (e.g from swift)"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:1126(para)
-msgid "Stack timeout in minutes. Default: 60"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:1134(para)
-msgid "Enable rollback on failure"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:1142(para)
-msgid "Parameter values used to preview the stack. This can be specified multiple times, or once with parameters separated by semicolon."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:1152(title)
-msgid "heat stack-show command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:1161(para)
-msgid "Name or ID of stack to describe."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:1169(title)
-msgid "heat stack-update command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:1180(para)
-msgid "Name or ID of stack to update."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:1223(para)
-msgid "Stack update timeout in minutes."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:1241(title)
-msgid "heat template-show command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:1250(para)
-msgid "Name or ID of stack to get the template for."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:1258(title)
-msgid "heat template-validate command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml:1300(para)
-msgid "Parameter values to validate. This can be specified multiple times, or once with parameters separated by a semicolon."
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml:8(para)
-msgid "You can use the OpenStack command-line clients to run simple commands that make API calls. You can run these commands from the command line or in scripts to automate tasks. If you provide OpenStack credentials, you can run these commands on any computer."
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml:12(para)
-msgid "Internally, each client command runs cURL commands that embed API requests. The OpenStack APIs are RESTful APIs that use the HTTP protocol, including methods, URIs, media types, and response codes."
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml:16(para)
-msgid "These open-source Python clients run on Linux or Mac OS X systems and are easy to learn and use. Each OpenStack service has its own command-line client. On some client commands, you can specify a <placeholder-1/> parameter to show the underlying API request for the command. This is a good way to become familiar with the OpenStack API calls."
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml:23(para)
-msgid "The following table lists the command-line client for each OpenStack service with its package name and description."
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml:26(caption)
-msgid "OpenStack services and clients"
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml:34(th)
-msgid "Client"
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml:35(th)
-msgid "Package"
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml:43(package)
-msgid "python-cinderclient"
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml:44(td)
-msgid "Create and manage volumes."
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml:49(package)
-msgid "python-novaclient"
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml:50(td)
-msgid "Create and manage images, instances, and flavors."
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml:55(package)
-msgid "python-troveclient"
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml:56(td)
-msgid "Create and manage databases."
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml:59(td)
-msgid "Identity"
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml:61(package)
-msgid "python-keystoneclient"
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml:62(td)
-msgid "Create and manage users, tenants, roles, endpoints, and credentials."
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml:67(package)
-msgid "python-glanceclient"
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml:68(td)
-msgid "Create and manage images."
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml:73(package)
-msgid "python-neutronclient"
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml:74(td)
-msgid "Configure networks for guest servers. This client was previously called <placeholder-1/>."
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml:80(package)
-msgid "python-swiftclient"
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml:81(td)
-msgid "Gather statistics, list items, update metadata, and upload, download, and delete files stored by the Object Storage service. Gain access to an Object Storage installation for ad hoc processing."
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml:88(package)
-msgid "python-heatclient"
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml:89(td)
-msgid "Launch stacks from templates, view details of running stacks including events and resources, and update and delete stacks."
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml:95(package)
-msgid "python-ceilometerclient"
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml:96(td)
-msgid "Create and collect measurements across OpenStack."
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml:100(para)
-msgid "An OpenStack <placeholder-1/> client is in development."
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml:102(para)
-msgid "For client installation instructions, see <link href=\"http://docs.openstack.org/user-guide/content/install_clients.html\">Install the OpenStack command-line clients</link>. For information about the OpenStack RC file, see <link href=\"http://docs.openstack.org/user-guide/content/cli_openrc.html\">Download and source the OpenStack RC file</link>."
-msgstr ""
-
-#: ./doc/common/section_rpc.xml:8(para)
-msgid "OpenStack projects use AMQP, an open standard for messaging middleware. OpenStack services that run on multiple servers to talk to each other. OpenStack Oslo RPC supports three implementations of AMQP: <application>RabbitMQ</application>, <application>Qpid</application>, and <application>ZeroMQ</application>."
-msgstr ""
-
-#: ./doc/common/section_rpc.xml:16(para)
-msgid "OpenStack Oslo RPC uses <application>RabbitMQ</application> by default. Use these options to configure the <application>RabbitMQ</application> message system. The <literal>rpc_backend</literal> option is not required as long as <application>RabbitMQ</application> is the default messaging system. However, if it is included the configuration, you must set it to <literal>nova.openstack.common.rpc.impl_kombu</literal>."
-msgstr ""
-
-#: ./doc/common/section_rpc.xml:25(para)
-msgid "You can use these additional options to configure the <application>RabbitMQ</application> messaging system. You can configure messaging communication for different installation scenarios, tune retries for RabbitMQ, and define the size of the RPC thread pool. To monitor notifications through RabbitMQ, you must set the <option>notification_driver</option> option to <literal>nova.notifier.rabbit_notifier</literal> in the <filename>nova.conf</filename> file. The default for sending usage data is sixty seconds plus a random number of seconds from zero to sixty."
-msgstr ""
-
-#: ./doc/common/section_rpc.xml:40(para)
-msgid "Use these options to configure the <application>Qpid</application> messaging system for OpenStack Oslo RPC. <application>Qpid</application> is not the default messaging system, so you must enable it by setting the <option>rpc_backend</option> option in the <filename>nova.conf</filename> file."
-msgstr ""
-
-#: ./doc/common/section_rpc.xml:47(para)
-msgid "This critical option points the compute nodes to the <application>Qpid</application> broker (server). Set <option>qpid_hostname</option> to the host name where the broker runs in the <filename>nova.conf</filename> file."
-msgstr ""
-
-#: ./doc/common/section_rpc.xml:69(para)
-msgid "This table lists additional options that you use to configure the Qpid messaging driver for OpenStack Oslo RPC. These options are used infrequently."
-msgstr ""
-
-#: ./doc/common/section_rpc.xml:76(para)
-msgid "Use these options to configure the <application>ZeroMQ</application> messaging system for OpenStack Oslo RPC. <application>ZeroMQ</application> is not the default messaging system, so you must enable it by setting the <option>rpc_backend</option> option in the <filename>nova.conf</filename> file."
-msgstr ""
-
-#: ./doc/common/section_rpc.xml:86(para)
-msgid "Use these options to configure the <application>RabbitMQ</application> and <application>Qpid</application> messaging drivers."
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:7(title)
-msgid "Install the OpenStack command-line clients"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:8(para)
-msgid "Install the prerequisite software and the Python package for each OpenStack client."
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:11(title)
-msgid "Install the prerequisite software"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:12(para)
-msgid "The following table lists the software that you need to have to run the command-line clients, and provides installation instructions as needed."
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:16(caption)
-msgid "Prerequisite software"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:21(th)
-msgid "Prerequisite"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:28(para)
-msgid "Python 2.6 or later"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:31(para)
-msgid "Currently, the clients do not support Python 3."
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:37(para)
-msgid "<package>setuptools</package> package"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:40(para)
-msgid "Installed by default on Mac OS X."
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:41(para)
-msgid "Many Linux distributions provide packages to make <package>setuptools</package> easy to install. Search your package manager for <package>setuptools</package> to find an installation package. If you cannot find one, download the <package>setuptools</package> package directly from <link href=\"http://pypi.python.org/pypi/setuptools\">http://pypi.python.org/pypi/setuptools</link>."
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:49(para)
-msgid "The recommended way to install <package>setuptools</package> on Microsoft Windows is to follow the documentation provided <link href=\"https://pypi.python.org/pypi/setuptools#windows\">on the setuptools website</link>. Another option is to use the unofficial binary installer maintained by Christoph Gohlke (<link href=\"http://www.lfd.uci.edu/~gohlke/pythonlibs/#setuptools\">http://www.lfd.uci.edu/~gohlke/pythonlibs/#setuptools</link>)."
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:62(package)
-msgid "pip"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:62(td)
-msgid "<placeholder-1/> package"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:64(para)
-msgid "To install the clients on a Linux, Mac OS X, or Microsoft Windows system, use <package>pip</package>. It is easy to use, ensures that you get the latest version of the clients from the <link href=\"http://pypi.python.org/pypi/python-novaclient/\">Python Package Index</link>, and lets you update or remove the packages later on."
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:73(para)
-msgid "Install <package>pip</package> through the package manager for your system:"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:76(title)
-msgid "MacOS"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:80(title)
-msgid "Microsoft Windows"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:81(para)
-msgid "Ensure that the <filename>C:\\Python27\\Scripts</filename> directory is defined in the <literal>PATH</literal> environment variable, and use the <placeholder-1/> command from the <package>setuptools</package> package: <placeholder-2/>Another option is to use the unofficial binary installer provided by Christoph Gohlke (<link href=\"http://www.lfd.uci.edu/~gohlke/pythonlibs/#pip\">http://www.lfd.uci.edu/~gohlke/pythonlibs/#pip</link>)."
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:98(title)
-msgid "Ubuntu 12.04/14.04"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:99(para)
-msgid "A packaged version enables you to use <package>dpkg</package> or <package>apt-get</package> to install the <package>python-novaclient</package>: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:108(title)
-msgid "Ubuntu and Debian"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:114(title)
-msgid "Red Hat Enterprise Linux, CentOS, or Fedora"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:115(para)
-msgid "A packaged version available in <link href=\"http://openstack.redhat.com/\">RDO</link> enables you to use <package>yum</package> to install the clients, or you can install <package>pip</package> and use it to manage client installation: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:123(title)
-msgid "openSUSE 12.2 and earlier"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:124(para)
-msgid "A <link href=\"https://build.opensuse.org/package/show?package=python-novaclient&amp;project=Cloud:OpenStack:Master\">packaged version available in the Open Build Service</link> enables you to use <package>rpm</package> or <package>zypper</package> to install the clients, or you can install <package>pip</package> and use it to manage client installation: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:135(title)
-msgid "openSUSE 12.3 and later"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:136(para)
-msgid "A packaged version enables you to use <package>rpm</package> or <package>zypper</package> to install the clients. See <xref linkend=\"cli_clients_install\"/>"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:147(title)
-msgid "Install the clients"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:148(para)
-msgid "When following the instructions in this section, replace <replaceable>PROJECT</replaceable> with the lowercase name of the client to install, such as <placeholder-1/>. Repeat for each client. The following values are valid:"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:155(para)
-msgid "<literal>ceilometer</literal> - Telemetry API"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:159(para)
-msgid "<literal>cinder</literal> - Block Storage API and extensions"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:163(para)
-msgid "<literal>glance</literal> - Image Service API"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:167(para)
-msgid "<literal>heat</literal> - Orchestration API"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:171(para)
-msgid "<literal>keystone</literal> - Identity service API and extensions"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:175(para)
-msgid "<literal>neutron</literal> - Networking API"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:179(para)
-msgid "<literal>nova</literal> - Compute API and extensions"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:183(para)
-msgid "<literal>swift</literal> - Object Storage API"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:187(para)
-msgid "<literal>trove</literal> - Database Service API"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:191(para)
-msgid "The following example shows the command for installing the nova client with <replaceable>pip</replaceable>."
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:196(title)
-msgid "Installing with pip"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:197(para)
-msgid "Use <package>pip</package> to install the OpenStack clients on a Linux, Mac OS X, or Microsoft Windows system. It is easy to use and ensures that you get the latest version of the client from the <link href=\"http://pypi.python.org/pypi\">Python Package Index</link>. Also, <package>pip</package> enables you to update or remove a package."
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:204(para)
-msgid "Install each client separately by using the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:207(para)
-msgid "For Mac OS X or Linux:"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:209(para)
-msgid "For Microsoft Windows:"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:214(title)
-msgid "Installing from packages"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:215(para)
-msgid "RDO and openSUSE have client packages that can be installed without <filename>pip</filename>."
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:217(para)
-msgid "On Red Hat Enterprise Linux, CentOS, or Fedora, use <placeholder-1/> to install the clients from the packaged versions available in <link href=\"http://openstack.redhat.com/\">RDO</link>: <placeholder-2/>"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:223(para)
-msgid "For openSUSE, use <package>rpm</package> or <package>zypper</package> to install the clients from the packaged versions available in <link href=\"https://build.opensuse.org/package/show?package=python-novaclient&amp;project=Cloud:OpenStack:Master\">the Open Build Service</link>:<placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:232(title)
-msgid "Upgrade or remove clients"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:233(para)
-msgid "To upgrade a client, add the <literal>--upgrade</literal> option to the <placeholder-1/> command:"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:237(para)
-msgid "To remove the a client, run the <placeholder-1/> command:"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:242(title)
-msgid "What's next"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml:243(para)
-msgid "Before you can run client commands, you must create and source the <filename><replaceable>PROJECT</replaceable>-openrc.sh</filename> file to set environment variables. See <xref linkend=\"cli_openrc\"/>."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-service-management.xml:5(title)
-msgid "Service management"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-service-management.xml:6(para)
-msgid "The Identity Service provides identity, token, catalog, and policy services. It consists of:"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-service-management.xml:11(para)
-msgid "<systemitem class=\"service\">keystone-all</systemitem>. Starts both the service and administrative APIs in a single process to provide Catalog, Authorization, and Authentication services for OpenStack."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-service-management.xml:17(para)
-msgid "Identity Service functions. Each has a pluggable back end that allows different ways to use the particular service. Most support standard back ends like LDAP or SQL."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-service-management.xml:23(para)
-msgid "The Identity Service also maintains a user that corresponds to each service, such as, a user named <emphasis>nova</emphasis> for the Compute service, and a special service tenant called <emphasis>service</emphasis>."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-service-management.xml:28(para)
-msgid "For information about how to create services and endpoints, see the <link href=\"http://docs.openstack.org/user-guide-admin/content/index.html\"><citetitle>OpenStack Admin User Guide</citetitle></link>."
+#: ./doc/common/section_getstart_object-storage.xml:46(para)
+msgid "Handles authentication and is usually OpenStack Identity."
 msgstr ""
 
 #: ./doc/common/ch_cli_trove_commands.xml:11(title)
@@ -17057,6 +12627,2079 @@ msgstr ""
 msgid "Optional new host of user."
 msgstr ""
 
+#: ./doc/common/section_dashboard-configure-https.xml:4(title)
+msgid "Configure the dashboard for HTTPS"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml:5(para) ./doc/common/section_dashboard-configure.xml:10(para)
+msgid "You can configure the dashboard for a secured HTTPS deployment. While the standard installation uses a non-encrypted HTTP channel, you can enable SSL support for the dashboard."
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml:9(para)
+msgid "The following example uses the domain, \"http://openstack.example.com.\" Use a domain that fits your current setup."
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml:13(para)
+msgid "In<filename>/etc/openstack-dashboard/local_settings.py</filename> update the following directives:"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml:19(para)
+msgid "The first option is required to enable HTTPS. The other recommended settings defend against cross-site scripting and require HTTPS."
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml:24(para)
+msgid "Edit <filename>/etc/apache2/ports.conf</filename> and add the following line:"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml:30(para)
+msgid "Edit <filename>/etc/apache2/conf.d/openstack-dashboard.conf:</filename>"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml:33(para)
+msgid "Before:"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml:46(para)
+msgid "After:"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml:87(para)
+msgid "In this configuration, Apache http server listens on the port 443 and redirects all the hits to the HTTPS protocol for all the non-secured requests. The secured section defines the private key, public key, and certificate to use."
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml:94(para)
+msgid "Restart Apache http server. For Debian/Ubuntu/SUSE:"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml:96(para)
+msgid "Or for Fedora/RHEL/CentOS:"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml:100(para)
+msgid "If you try to access the dashboard through HTTP, the browser redirects you to the HTTPS page."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_volumes.xml:8(title)
+msgid "Manage Volumes"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_volumes.xml:9(para)
+msgid "Depending on the setup of your cloud provider, they may give you an endpoint to use to manage volumes, or there may be an extension under the covers. In either case, you can use the <placeholder-1/> CLI to manage volumes:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_volumes.xml:26(para)
+msgid "For example, to list IDs and names of Compute volumes, run:"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-console.xml:5(title)
+msgid "Configure remote console access"
+msgstr ""
+
+#. <?dbhtml stop-chunking?>
+#: ./doc/common/section_compute-configure-console.xml:7(para)
+msgid "To provide a remote console or remote desktop access to guest virtual machines, use VNC or SPICE HTML5 through either the OpenStack dashboard or the command line. Best practice is to select one or the other to run."
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-characteristics.xml:49(None)
+msgid "@@image: '../common/figures/objectstorage.png'; md5=e26e374ace84070f5fed24e73adcd562"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml:7(title)
+msgid "Object Storage characteristics"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml:8(para)
+msgid "The key characteristics of Object Storage are that:"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml:11(para)
+msgid "All objects stored in Object Storage have a URL."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml:14(para)
+msgid "All objects stored are replicated 3✕ in as-unique-as-possible zones, which can be defined as a group of drives, a node, a rack, and so on."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml:18(para)
+msgid "All objects have their own metadata."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml:21(para)
+msgid "Developers interact with the object storage system through a RESTful HTTP API."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml:25(para)
+msgid "Object data can be located anywhere in the cluster."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml:28(para)
+msgid "The cluster scales by adding additional nodes without sacrificing performance, which allows a more cost-effective linear storage expansion than fork-lift upgrades."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml:33(para)
+msgid "Data doesn't have to be migrate to an entirely new storage system."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml:36(para)
+msgid "New nodes can be added to the cluster without downtime."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml:39(para)
+msgid "Failed nodes and disks can be swapped out without downtime."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml:42(para)
+msgid "It runs on industry-standard hardware, such as Dell, HP, and Supermicro."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml:53(para)
+msgid "Developers can either write directly to the Swift API or use one of the many client libraries that exist for all of the popular programming languages, such as Java, Python, Ruby, and C#. Amazon S3 and RackSpace Cloud Files users should be very familiar with Object Storage. Users new to object storage systems will have to adjust to a different approach and mindset than those required for a traditional filesystem."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml:6(title)
+msgid "Stop and start an instance"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml:7(para)
+msgid "Use one of the following methods to stop and start an instance."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml:10(title)
+msgid "Pause and unpause an instance"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml:13(para)
+msgid "To pause an instance, run the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml:15(para)
+msgid "This command stores the state of the VM in RAM. A paused instance continues to run in a frozen state."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml:17(para)
+msgid "To unpause the instance, run the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml:23(title)
+msgid "Suspend and resume an instance"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml:25(para)
+msgid "Administrative users might want to suspend an instance if it is infrequently used or to perform system maintenance. When you suspend an instance, its VM state is stored on disk, all memory is written to disk, and the virtual machine is stopped. Suspending an instance is similar to placing a device in hibernation; memory and vCPUs become available to create other instances."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml:33(para)
+msgid "To initiate a hypervisor-level suspend operation, run the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml:38(para)
+msgid "To resume a suspended instance, run the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml:45(title)
+msgid "Shelve and unshelve an instance"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml:46(para)
+msgid "Shelving is useful if you have an instance that you are not using, but would like retain in your list of servers. For example, you can stop an instance at the end of a work week, and resume work again at the start of the next week. All associated data and resources are kept; however, anything still in memory is not retained. If a shelved instance is no longer needed, it can also be entirely removed."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml:51(para)
+msgid "You can complete the following shelving tasks:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml:53(term)
+msgid "Shelve an instance"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml:54(para)
+msgid "Shuts down the instance, and stores it together with associated data and resources (a snapshot is taken if not volume backed). Anything in memory is lost. Use the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml:57(replaceable) ./doc/common/section_cli_nova_startstop.xml:62(replaceable) ./doc/common/section_cli_nova_startstop.xml:69(replaceable)
+msgid "SERVERNAME"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml:60(term)
+msgid "Unshelve an instance"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml:61(para)
+msgid "Restores the instance:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml:65(term)
+msgid "Remove a shelved instance"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml:66(para)
+msgid "Removes the instance from the server; data and resource associations are deleted. If an instance is no longer needed, you can move that instance off the hypervisor in order to minimize resource usage:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_metadata.xml:9(title)
+msgid "Insert metadata during launch"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_metadata.xml:10(para)
+msgid "When booting a server, you can also add metadata, so that you can more easily identify it amongst your ever-growing elastic cloud. Use the <literal>--meta</literal> option with a key=value pair, where you can make up the string for both the key and the value. For example, you could add a description and also the creator of the server. <placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_metadata.xml:18(para)
+msgid "When viewing the server information, you can see the metadata included on the <literal>metadata</literal> line: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:7(title) ./doc/common/section_dashboard_access.xml:105(guilabel) ./doc/common/section_dashboard_access.xml:229(guilabel)
+msgid "Overview"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:8(para)
+msgid "Each OpenStack project provides a command-line client, which enables you to access the project API through easy-to-use commands. For example, the Compute service provides a nova command-line client."
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:13(para)
+msgid "You can run the commands from the command line, or include the commands within scripts to automate tasks. If you provide OpenStack credentials, such as your user name and password, you can run these commands on any computer."
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:19(para)
+msgid "Internally, each command uses cURL command-line tools, which embed API requests. OpenStack APIs are RESTful APIs, and use the HTTP protocol. They include methods, URIs, media types, and response codes."
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:24(para)
+msgid "OpenStack APIs are open-source Python clients, and can run on Linux or Mac OS X systems. On some client commands, you can specify a <placeholder-1/> parameter to show the underlying API request for the command. This is a good way to become familiar with the OpenStack API calls."
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:30(para)
+msgid "The following table lists the command-line client for each OpenStack service with its package name and description."
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:33(caption)
+msgid "OpenStack services and clients"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:40(th) ./doc/common/ch_getstart.xml:29(th) ./doc/common/section_keystone-concepts.xml:83(term)
+msgid "Service"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:41(th)
+msgid "Client"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:42(th)
+msgid "Package"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:48(td) ./doc/common/ch_getstart.xml:99(glossterm)
+msgid "Block Storage"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:50(package)
+msgid "python-cinderclient"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:51(td)
+msgid "Create and manage volumes."
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:54(td) ./doc/common/section_dashboard_access.xml:100(guilabel) ./doc/common/ch_getstart.xml:52(glossterm)
+msgid "Compute"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:56(package)
+msgid "python-novaclient"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:57(td)
+msgid "Create and manage images, instances, and flavors."
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:60(td) ./doc/common/ch_getstart.xml:172(glossterm)
+msgid "Database Service"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:62(package)
+msgid "python-troveclient"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:63(td)
+msgid "Create and manage databases."
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:66(td)
+msgid "Identity"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:68(package)
+msgid "python-keystoneclient"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:69(td)
+msgid "Create and manage users, tenants, roles, endpoints, and credentials."
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:72(td) ./doc/common/ch_getstart.xml:127(glossterm)
+msgid "Image Service"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:74(package)
+msgid "python-glanceclient"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:75(td)
+msgid "Create and manage images."
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:78(td) ./doc/common/ch_getstart.xml:66(glossterm)
+msgid "Networking"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:80(package)
+msgid "python-neutronclient"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:81(td)
+msgid "Configure networks for guest servers. This client was previously called <placeholder-1/>."
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:85(td) ./doc/common/ch_getstart.xml:83(glossterm)
+msgid "Object Storage"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:87(package)
+msgid "python-swiftclient"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:88(td)
+msgid "Gather statistics, list items, update metadata, and upload, download, and delete files stored by the Object Storage service. Gain access to an Object Storage installation for ad hoc processing."
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:93(td) ./doc/common/section_dashboard_access.xml:192(guilabel) ./doc/common/ch_getstart.xml:157(glossterm)
+msgid "Orchestration"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:95(package)
+msgid "python-heatclient"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:96(td)
+msgid "Launch stacks from templates, view details of running stacks including events and resources, and update and delete stacks."
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:100(td) ./doc/common/ch_getstart.xml:142(glossterm)
+msgid "Telemetry"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:102(package)
+msgid "python-ceilometerclient"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:103(td)
+msgid "Create and collect measurements across OpenStack."
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:107(para)
+msgid "An OpenStack <placeholder-1/> client is in development."
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml:109(para)
+msgid "For client installation instructions, see <link href=\"http://docs.openstack.org/user-guide/content/install_clients.html\">Install the OpenStack command-line clients</link>. For information about the OpenStack RC file, see <link href=\"http://docs.openstack.org/user-guide/content/cli_openrc.html\">Download and source the OpenStack RC file</link>."
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_getstart_logical_arch.xml:38(None)
+msgid "@@image: 'figures/openstack-arch-havana-logical-v1.jpg'; md5=e7acaaee72722626b045eda3fae81841"
+msgstr ""
+
+#: ./doc/common/section_getstart_logical_arch.xml:5(title) ./doc/common/section_getstart_logical_arch.xml:33(title)
+msgid "Logical architecture"
+msgstr ""
+
+#: ./doc/common/section_getstart_logical_arch.xml:6(para)
+msgid "To design, deploy, and configure OpenStack, administrators must understand the logical architecture."
+msgstr ""
+
+#: ./doc/common/section_getstart_logical_arch.xml:7(para)
+msgid "OpenStack modules are one of the following types:"
+msgstr ""
+
+#: ./doc/common/section_getstart_logical_arch.xml:9(term)
+msgid "Daemon"
+msgstr ""
+
+#: ./doc/common/section_getstart_logical_arch.xml:11(para)
+msgid "Runs as a background process. On Linux platforms, a daemon is usually installed as a service."
+msgstr ""
+
+#: ./doc/common/section_getstart_logical_arch.xml:15(term)
+msgid "Script"
+msgstr ""
+
+#: ./doc/common/section_getstart_logical_arch.xml:17(para)
+msgid "Installs a virtual environment and runs tests. For example, the <code>run_tests.sh</code> script installs a virtual environment and runs unit tests on a service."
+msgstr ""
+
+#: ./doc/common/section_getstart_logical_arch.xml:21(term)
+msgid "Command-line interface (CLI)"
+msgstr ""
+
+#: ./doc/common/section_getstart_logical_arch.xml:23(para)
+msgid "Enables users to submit API calls to OpenStack services through easy-to-use commands."
+msgstr ""
+
+#: ./doc/common/section_getstart_logical_arch.xml:29(para)
+msgid "The following diagram shows the most common, but not the only, architecture for an OpenStack cloud:"
+msgstr ""
+
+#: ./doc/common/section_getstart_logical_arch.xml:42(para)
+msgid "As in <xref linkend=\"concept_arch\"/>, end users can interact through the dashboard, CLIs, and APIs. All services authenticate through a common Identity Service and individual services interact with each other through public APIs, except where privileged administrator commands are necessary."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:6(title)
+msgid "Manage Networking service quotas"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:7(para)
+msgid "A quota limits the number of available resources. A default quota might be enforced for all tenants. When you try to create more resources than the quota allows, an error occurs:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:12(para)
+msgid "Per-tenant quota configuration is also supported by the quota extension API. See <link linkend=\"cfg_quotas_per_tenant\"> Per-tenant quota configuration</link> for details."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:16(title)
+msgid "Basic quota configuration"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:17(para)
+msgid "In the Networking default quota mechanism, all tenants have the same quota values, such as the number of resources that a tenant can create."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:20(para)
+msgid "The quota value is defined in the OpenStack Networking <filename>neutron.conf</filename> configuration file. To disable quotas for a specific resource, such as network, subnet, or port, remove a corresponding item from <option>quota_items</option>. This example shows the default quota values:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:41(para)
+msgid "OpenStack Networking also supports quotas for L3 resources: router and floating IP. Add these lines to the <literal>quotas</literal> section in the <filename>neutron.conf</filename> file."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:52(para) ./doc/common/section_cli_neutron-quotas.xml:67(para)
+msgid "The <option>quota_items</option> option does not affect these quotas."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:55(para)
+msgid "OpenStack Networking also supports quotas for security group resources: number of security groups and the number of rules for each security group. Add these lines to the <literal>quotas</literal> section in the <filename>neutron.conf</filename> file:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:72(title)
+msgid "Configure per-tenant quotas"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:73(para)
+msgid "OpenStack Networking also supports per-tenant quota limit by quota extension API."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:77(para)
+msgid "<placeholder-1/>. Deletes defined quotas for a specified tenant."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:81(para)
+msgid "<placeholder-1/>. Lists defined quotas for all tenants."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:85(para)
+msgid "<placeholder-1/>. Shows quotas for a specified tenant."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:89(para)
+msgid "<placeholder-1/>. Updates quotas for a specified tenant."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:75(para)
+msgid "Use these commands to manage per-tenant quotas:<placeholder-1/>Only users with the <literal>admin</literal> role can change a quota value. By default, the default set of quotas are enforced for all tenants, so no <placeholder-2/> command exists."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:98(title)
+msgid "Configure Networking to show per-tenant quotas"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:99(para)
+msgid "Set the <literal>quota_driver</literal> option in the <literal>neutron.conf</literal> file:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:102(para)
+msgid "When you set this option, the output for Networking commands shows <literal>quotas</literal>."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:106(title)
+msgid "List Networking extensions"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:107(para)
+msgid "To list the Networking extensions, run this command:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:110(para)
+msgid "The command shows the <literal>quotas</literal> extension, which provides per-tenant quota management support:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:128(title)
+msgid "Show information for the quotas extension"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:129(para)
+msgid "To show information for the <literal>quotas</literal> extension, run this command:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:143(para)
+msgid "Only some plug-ins support per-tenant quotas. Specifically, Open vSwitch, Linux Bridge, and VMware NSX support them, but new versions of other plug-ins might bring additional functionality. See the documentation for each plug-in."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:151(title)
+msgid "List tenants who have per-tenant quota support"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:152(para)
+msgid "The <placeholder-1/> command lists tenants for which the per-tenant quota is enabled. The command does not list tenants with default quota support. You must be an administrative user to run this command:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:165(title)
+msgid "Show per-tenant quota values"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:166(para)
+msgid "The <placeholder-1/> reports the current set of quota limits for the specified tenant. Non-administrative users can run this command without the <parameter>--tenant_id</parameter> parameter. If per-tenant quota limits are not enabled for the tenant, the command shows the default set of quotas:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:182(para)
+msgid "The following command shows the command output for a non-administrative user:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:196(title)
+msgid "Update quota values for a specified tenant"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:197(para)
+msgid "Use the <placeholder-1/> command to update a quota for a specified tenant:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:209(para)
+msgid "You can update quotas for multiple resources through one command:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:221(para)
+msgid "To update the limits for an L3 resource such as, router or floating IP, you must define new values for the quotas after the <parameter>--</parameter> directive."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:224(para)
+msgid "This example updates the limit of the number of floating IPs for the specified tenant:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:236(para)
+msgid "You can update the limits of multiple resources by including L2 resources and L3 resource through one command."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:251(title)
+msgid "Delete per-tenant quota values"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:252(para)
+msgid "To clear per-tenant quota limits, use the <placeholder-1/> command:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml:256(para)
+msgid "After you run this command, you can see that quota values for the tenant are reset to the default values:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:10(title)
+msgid "Host aggregates"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:11(para)
+msgid "Host aggregates are a mechanism to further partition an availability zone; while availability zones are visible to users, host aggregates are only visible to administrators. Host Aggregates provide a mechanism to allow administrators to assign key-value pairs to groups of machines. Each node can have multiple aggregates, each aggregate can have multiple key-value pairs, and the same key-value pair can be assigned to multiple aggregates. This information can be used in the scheduler to enable advanced scheduling, to set up hypervisor resource pools or to define logical groups for migration."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:23(title)
+msgid "Command-line interface"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:35(replaceable) ./doc/common/section_cli_nova_host_aggregates.xml:111(replaceable)
+msgid "&lt;name&gt;"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:36(replaceable)
+msgid "&lt;availability-zone&gt;"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:38(para)
+msgid "Create a new aggregate named <replaceable>&lt;name&gt;</replaceable> in availability zone <replaceable>&lt;availability-zone&gt;</replaceable>. Returns the ID of the newly created aggregate. Hosts can be made available to multiple availability zones, but administrators should be careful when adding the host to a different host aggregate within the same availability zone and pay attention when using the <placeholder-1/> and <placeholder-2/> commands to avoid user confusion when they boot instances in different availability zones. An error occurs if you cannot add a particular host to an aggregate zone for which it is not intended."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:60(replaceable) ./doc/common/section_cli_nova_host_aggregates.xml:68(replaceable) ./doc/common/section_cli_nova_host_aggregates.xml:76(replaceable) ./doc/common/section_cli_nova_host_aggregates.xml:87(replaceable) ./doc/common/section_cli_nova_host_aggregates.xml:98(replaceable) ./doc/common/section_cli_nova_host_aggregates.xml:110(replaceable)
+msgid "&lt;id&gt;"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:62(para)
+msgid "Delete an aggregate with id <replaceable>&lt;id&gt;</replaceable>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:70(para)
+msgid "Show details of the aggregate with id <replaceable>&lt;id&gt;</replaceable>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:77(replaceable) ./doc/common/section_cli_nova_host_aggregates.xml:88(replaceable)
+msgid "&lt;host&gt;"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:79(para)
+msgid "Add host with name <replaceable>&lt;host&gt;</replaceable> to aggregate with id <replaceable>&lt;id&gt;</replaceable>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:90(para)
+msgid "Remove the host with name <replaceable>&lt;host&gt;</replaceable> from the aggregate with id <replaceable>&lt;id&gt;</replaceable>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:99(replaceable) ./doc/common/section_cli_nova_host_aggregates.xml:100(replaceable)
+msgid "&lt;key=value&gt;"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:103(para)
+msgid "Add or update metadata (key-value pairs) associated with the aggregate with id <replaceable>&lt;id&gt;</replaceable>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:112(replaceable)
+msgid "&lt;availability_zone&gt;"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:114(para)
+msgid "Update the name and availability zone (optional) for the aggregate."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:128(para)
+msgid "Put/resume host into/from maintenance."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:24(para)
+msgid "The <placeholder-1/> command-line tool supports the following aggregate-related commands. <placeholder-2/>"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:134(para)
+msgid "Only administrators can access these commands. If you try to use these commands and the user name and tenant that you use to access the Compute service do not have the <literal>admin</literal> role or the appropriate privileges, these errors occur:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:146(title)
+msgid "Configure scheduler to support host aggregates"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:147(para)
+msgid "One common use case for host aggregates is when you want to support scheduling instances to a subset of compute hosts because they have a specific capability. For example, you may want to allow users to request compute hosts that have SSD drives if they need access to faster disk I/O, or access to compute hosts that have GPU cards to take advantage of GPU-accelerated code."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:154(para)
+msgid "To configure the scheduler to support host aggregates, the <literal>scheduler_default_filters</literal> configuration option must contain the <literal>AggregateInstanceExtraSpecsFilter</literal> in addition to the other filters used by the scheduler. Add the following line to <filename>/etc/nova/nova.conf</filename> on the host that runs the <systemitem class=\"service\">nova-scheduler</systemitem> service to enable host aggregates filtering, as well as the other filters that are typically enabled:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:168(title)
+msgid "Example: Specify compute hosts with SSDs"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:169(para)
+msgid "This example configures the Compute service to enable users to request nodes that have solid-state drives (SSDs). You create a <literal>fast-io</literal> host aggregate in the <literal>nova</literal> availability zone and you add the <literal>ssd=true</literal> key-value pair to the aggregate. Then, you add the <literal>node1</literal>, and <literal>node2</literal> compute nodes to it."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:204(para)
+msgid "Use the <placeholder-1/> command to create the <replaceable>ssd.large</replaceable> flavor called with an ID of 6, 8GB of RAM, 80GB root disk, and four vCPUs."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:207(replaceable) ./doc/common/section_cli_nova_host_aggregates.xml:219(replaceable)
+msgid "ssd.large"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:207(replaceable)
+msgid "6"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:207(replaceable)
+msgid "8192"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:207(replaceable)
+msgid "80"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:207(replaceable)
+msgid "4"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:213(para)
+msgid "Once the flavor is created, specify one or more key-value pairs that match the key-value pairs on the host aggregates. In this case, that is the <replaceable>ssd=true</replaceable> key-value pair. Setting a key-value pair on a flavor is done using the <placeholder-1/> command."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:219(replaceable)
+msgid "ssd=true"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:220(para)
+msgid "Once it is set, you should see the <literal>extra_specs</literal> property of the <literal>ssd.large</literal> flavor populated with a key of <literal>ssd</literal> and a corresponding value of <literal>true</literal>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:241(para)
+msgid "Now, when a user requests an instance with the <literal>ssd.large</literal> flavor, the scheduler only considers hosts with the <literal>ssd=true</literal> key-value pair. In this example, these are <literal>node1</literal> and <literal>node2</literal>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:249(title)
+msgid "XenServer hypervisor pools to support live migration"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml:251(para)
+msgid "When using the XenAPI-based hypervisor, the Compute service uses host aggregates to manage XenServer Resource pools, which are used in supporting live migration."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml:6(title) ./doc/common/section_objectstorage-components.xml:192(title)
+msgid "Replication"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml:7(para)
+msgid "Because each replica in Object Storage functions independently and clients generally require only a simple majority of nodes to respond to consider an operation successful, transient failures like network partitions can quickly cause replicas to diverge. These differences are eventually reconciled by asynchronous, peer-to-peer replicator processes. The replicator processes traverse their local file systems and concurrently perform operations in a manner that balances load across physical disks."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml:16(para)
+msgid "Replication uses a push model, with records and files generally only being copied from local to remote replicas. This is important because data on the node might not belong there (as in the case of hand offs and ring changes), and a replicator cannot know which data it should pull in from elsewhere in the cluster. Any node that contains data must ensure that data gets to where it belongs. The ring handles replica placement."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml:24(para)
+msgid "To replicate deletions in addition to creations, every deleted record or file in the system is marked by a tombstone. The replication process cleans up tombstones after a time period known as the <emphasis role=\"italic\">consistency window</emphasis>. This window defines the duration of the replication and how long transient failure can remove a node from the cluster. Tombstone cleanup must be tied to replication to reach replica convergence."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml:32(para)
+msgid "If a replicator detects that a remote drive has failed, the replicator uses the <literal>get_more_nodes</literal> interface for the ring to choose an alternate node with which to synchronize. The replicator can maintain desired levels of replication during disk failures, though some replicas might not be in an immediately usable location."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml:39(para)
+msgid "The replicator does not maintain desired levels of replication when failures such as entire node failures occur; most failures are transient."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml:43(para)
+msgid "The main replication types are:"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml:46(para)
+msgid "<emphasis role=\"bold\">Database replication</emphasis>. Replicates containers and objects."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml:51(para)
+msgid "<emphasis role=\"bold\">Object replication</emphasis>. Replicates object data."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml:56(title)
+msgid "Database replication"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml:57(para)
+msgid "Database replication completes a low-cost hash comparison to determine whether two replicas already match. Normally, this check can quickly verify that most databases in the system are already synchronized. If the hashes differ, the replicator synchronizes the databases by sharing records added since the last synchronization point."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml:64(para)
+msgid "This synchronization point is a high water mark that notes the last record at which two databases were known to be synchronized, and is stored in each database as a tuple of the remote database ID and record ID. Database IDs are unique across all replicas of the database, and record IDs are monotonically increasing integers. After all new records are pushed to the remote database, the entire synchronization table of the local database is pushed, so the remote database can guarantee that it is synchronized with everything with which the local database was previously synchronized."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml:75(para)
+msgid "If a replica is missing, the whole local database file is transmitted to the peer by using rsync(1) and is assigned a new unique ID."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml:78(para)
+msgid "In practice, database replication can process hundreds of databases per concurrency setting per second (up to the number of available CPUs or disks) and is bound by the number of database transactions that must be performed."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml:85(title)
+msgid "Object replication"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml:86(para)
+msgid "The initial implementation of object replication performed an rsync to push data from a local partition to all remote servers where it was expected to reside. While this worked at small scale, replication times skyrocketed once directory structures could no longer be held in RAM. This scheme was modified to save a hash of the contents for each suffix directory to a per-partition hashes file. The hash for a suffix directory is no longer valid when the contents of that suffix directory is modified."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml:95(para)
+msgid "The object replication process reads in hash files and calculates any invalidated hashes. Then, it transmits the hashes to each remote server that should hold the partition, and only suffix directories with differing hashes on the remote server are rsynced. After pushing files to the remote server, the replication process notifies it to recalculate hashes for the rsynced suffix directories."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml:103(para)
+msgid "The number of uncached directories that object replication must traverse, usually as a result of invalidated suffix directory hashes, impedes performance. To provide acceptable replication speeds, object replication is designed to invalidate around 2 percent of the hash space on a normal node each day."
+msgstr ""
+
+#: ./doc/common/section_getstart_networking.xml:5(title)
+msgid "OpenStack Networking"
+msgstr ""
+
+#: ./doc/common/section_getstart_networking.xml:6(para)
+msgid "OpenStack Networking allows you to create and attach interface devices managed by other OpenStack services to networks. Plug-ins can be implemented to accomodate different networking equipment and software, providing flexibility to OpenStack architecture and deployment."
+msgstr ""
+
+#: ./doc/common/section_getstart_networking.xml:14(systemitem)
+msgid "neutron-server"
+msgstr ""
+
+#: ./doc/common/section_getstart_networking.xml:15(para)
+msgid "Accepts and routes API requests to the appropriate OpenStack Networking plug-in for action."
+msgstr ""
+
+#: ./doc/common/section_getstart_networking.xml:19(term)
+msgid "OpenStack Networking plug-ins and agents"
+msgstr ""
+
+#: ./doc/common/section_getstart_networking.xml:20(para)
+msgid "Plugs and unplugs ports, creates networks or subnets, and provides IP addressing. These plug-ins and agents differ depending on the vendor and technologies used in the particular cloud. OpenStack Networking ships with plug-ins and agents for Cisco virtual and physical switches, NEC OpenFlow products, Open vSwitch, Linux bridging, Ryu Network Operating System, and the VMware NSX product."
+msgstr ""
+
+#: ./doc/common/section_getstart_networking.xml:27(para)
+msgid "The common agents are L3 (layer 3), DHCP (dynamic host IP addressing), and a plug-in agent."
+msgstr ""
+
+#: ./doc/common/section_getstart_networking.xml:31(term) ./doc/common/section_getstart_block-storage.xml:35(term)
+msgid "Messaging queue"
+msgstr ""
+
+#: ./doc/common/section_getstart_networking.xml:32(para)
+msgid "Used by most OpenStack Networking installations to route information between the neutron-server and various agents, as well as a database to store networking state for particular plug-ins."
+msgstr ""
+
+#: ./doc/common/section_getstart_networking.xml:38(para)
+msgid "OpenStack Networking mainly interacts with OpenStack Compute to provide networks and connectivity for its instances."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_evacuate.xml:6(title)
+msgid "Evacuate instances"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_evacuate.xml:7(para)
+msgid "If a cloud compute node fails due to a hardware malfunction or another reason, you can evacuate instances to make them available again. You can choose evacuation parameters for your use case."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_evacuate.xml:10(para)
+msgid "To preserve user data on server disk, you must configure shared storage on the target host. Also, you must validate that the current VM host is down; otherwise, the evacuation fails with an error."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_evacuate.xml:15(para)
+msgid "To list hosts and find a different host for the evacuated instance, run:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_evacuate.xml:19(para)
+msgid "Evacuate the instance. You can pass the instance password to the command by using the <literal>--password &lt;pwd&gt;</literal> option. If you do not specify a password, one is generated and printed after the command finishes successfully. The following command evacuates a server without shared storage from a host that is down to the specified <replaceable>host_b</replaceable>:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_evacuate.xml:24(replaceable) ./doc/common/section_cli_nova_evacuate.xml:40(replaceable)
+msgid "evacuated_server_name"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_evacuate.xml:24(replaceable) ./doc/common/section_cli_nova_evacuate.xml:40(replaceable)
+msgid "host_b"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_evacuate.xml:25(para)
+msgid "The instance is booted from a new disk, but preserves its configuration including its ID, name, uid, IP address, and so on. The command returns a password:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_evacuate.xml:34(para)
+msgid "To preserve the user disk data on the evacuated server, deploy OpenStack Compute with a shared file system. To configure your system, see <link href=\"http://docs.openstack.org/icehouse/config-reference/content/configuring-openstack-compute-basics.html#section_configuring-compute-migrations\">Configure migrations</link> in <citetitle>OpenStack Configuration Reference</citetitle>. In the following example, the password remains unchanged:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_terminate.xml:8(title)
+msgid "Delete an instance"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_terminate.xml:9(para)
+msgid "When you no longer need an instance, you can delete it."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_terminate.xml:11(para)
+msgid "List all instances:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_terminate.xml:21(para)
+msgid "Run the <placeholder-1/> command to delete the instance. The following example shows deletion of the <filename>newServer</filename> instance, which is in <literal>ERROR</literal> state:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_terminate.xml:24(para)
+msgid "The command does not notify that your server was deleted."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_terminate.xml:25(para)
+msgid "To verify that the server was deleted, run the <placeholder-1/> command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_terminate.xml:33(para)
+msgid "The deleted instance does not appear in the list."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-spice.xml:6(title)
+msgid "SPICE console"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-spice.xml:7(para)
+msgid "OpenStack Compute supports VNC consoles to guests. The VNC protocol is fairly limited, lacking support for multiple monitors, bi-directional audio, reliable cut-and-paste, video streaming and more. SPICE is a new protocol that aims to address the limitations in VNC and provide good remote desktop support."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-spice.xml:12(para)
+msgid "SPICE support in OpenStack Compute shares a similar architecture to the VNC implementation. The OpenStack dashboard uses a SPICE-HTML5 widget in its console tab that communicates to the <systemitem class=\"service\">nova-spicehtml5proxy</systemitem> service by using SPICE-over-websockets. The <systemitem class=\"service\">nova-spicehtml5proxy</systemitem> service communicates directly with the hypervisor process by using SPICE."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-spice.xml:19(para)
+msgid "VNC must be explicitly disabled to get access to the SPICE console. Set the <option>vnc_enabled</option> option to <literal>False</literal> in the <literal>[DEFAULT]</literal> section to disable the VNC console."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-spice.xml:22(para)
+msgid "Use the following options to configure SPICE as the console for OpenStack Compute:"
+msgstr ""
+
+#: ./doc/common/section_getstart_block-storage.xml:5(title)
+msgid "OpenStack Block Storage"
+msgstr ""
+
+#: ./doc/common/section_getstart_block-storage.xml:6(para)
+msgid "OpenStack Block Storage enables management of volumes, volume snapshots, and volume types. It consists of the following components:"
+msgstr ""
+
+#: ./doc/common/section_getstart_block-storage.xml:11(systemitem)
+msgid "cinder-api"
+msgstr ""
+
+#: ./doc/common/section_getstart_block-storage.xml:12(para)
+msgid "Accepts API requests and routes them to <systemitem class=\"service\">cinder-volume</systemitem> for action."
+msgstr ""
+
+#: ./doc/common/section_getstart_block-storage.xml:17(systemitem)
+msgid "cinder-volume"
+msgstr ""
+
+#: ./doc/common/section_getstart_block-storage.xml:18(para)
+msgid "Responds to requests to read from and write to the OpenStack Block Storage database to maintain state, interacting with other processes (like <systemitem class=\"service\">cinder-scheduler</systemitem>) through a message queue and directly upon block storage providing hardware or software. It can interact with a variety of storage providers through a driver architecture."
+msgstr ""
+
+#: ./doc/common/section_getstart_block-storage.xml:28(term)
+msgid "<systemitem class=\"service\">cinder-scheduler</systemitem> daemon"
+msgstr ""
+
+#: ./doc/common/section_getstart_block-storage.xml:30(para)
+msgid "Like the <systemitem class=\"service\">nova-scheduler</systemitem>, picks the optimal block storage provider node on which to create the volume."
+msgstr ""
+
+#: ./doc/common/section_getstart_block-storage.xml:36(para)
+msgid "Routes information between the Block Storage processes."
+msgstr ""
+
+#: ./doc/common/section_getstart_block-storage.xml:40(para)
+msgid "OpenStack Block Storage interacts with OpenStack Compute to provide volumes for instances."
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-vnc-window.xml:6(title)
+msgid "Change the size of the dashboard VNC window"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-vnc-window.xml:7(para)
+msgid "The <filename>_detail_vnc.html</filename> file defines the size of the VNC window. To change the window size, edit this file."
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-vnc-window.xml:12(para)
+msgid "Edit <filename>/usr/share/pyshared/horizon/dashboards/nova/instances/templates/instances/_detail_vnc.html.</filename>"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-vnc-window.xml:16(para)
+msgid "Modify the <literal>width</literal> and <literal>height</literal> parameters, as follows:"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml:6(title)
+msgid "Use the VNC console"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml:7(para)
+msgid "To interact through the VNC console, you can use a VNC client directly, a special Java client, or a web browser. For information about how to configure the console, see <xref linkend=\"installing-openstack-dashboard\"/>."
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml:15(title)
+msgid "Get an access URL"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml:16(para)
+msgid "The Compute service enables you to create access_urls through the os-consoles extension. Support for accessing this URL is provided by the nova client:"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml:19(replaceable) ./doc/common/section_using-vnc-console.xml:25(replaceable) ./doc/common/section_using-vnc-console.xml:52(replaceable) ./doc/common/section_using-vnc-console.xml:65(replaceable)
+msgid "[server_id]"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml:19(replaceable)
+msgid "[novnc|xvpvnc]"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml:20(para)
+msgid "Specify '<literal>novnc</literal>' to get a URL suitable for pasting into a web browser."
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml:22(para)
+msgid "Specify '<literal>xvpvnc</literal>' for a URL suitable for pasting into the Java client."
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml:24(para)
+msgid "To request a web browser URL:"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml:28(title)
+msgid "Access a VNC console with a Java client"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml:29(para)
+msgid "To enable support for the OpenStack Java VNC client in compute, run the <literal>nova-xvpvncproxy</literal> service."
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml:34(para)
+msgid "<literal>xvpvncproxy_port</literal>=<replaceable>[port]</replaceable> - port to bind (defaults to 6081)"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml:38(para)
+msgid "<literal>xvpvncproxy_host</literal>=<replaceable>[host]</replaceable> - host to bind (defaults to 0.0.0.0)"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml:42(para)
+msgid "As a client, you need a special Java client, which is a slightly modified version of TightVNC that supports our token auth:"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml:48(para)
+msgid "To create a session, request an access URL by using <placeholder-1/>. Then, run the client as follows."
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml:51(para)
+msgid "To get an access URL:"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml:53(para)
+msgid "To run the client:"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml:54(replaceable)
+msgid "[access_url]"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml:59(title)
+msgid "Access a VNC console with a web browser"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml:61(para)
+msgid "Retrieving an access_url for a web browser is similar to the flow for the Java client."
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml:63(para)
+msgid "To get the access URL, run the following command:"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml:66(para)
+msgid "Paste the URL into your web browser."
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml:68(para)
+msgid "Additionally, you can use the OpenStack dashboard, known as horizon, to access browser-based VNC consoles for instances."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_userdata.xml:6(title)
+msgid "Provide user data to instances"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_userdata.xml:7(para)
+msgid "A <glossterm baseform=\"user data\">user data</glossterm> file is a special key in the metadata service that holds a file that cloud-aware applications in the guest instance can access. For example, one application that uses user data is the <link href=\"https://help.ubuntu.com/community/CloudInit\">cloud-init</link> system, which is an open-source package from Ubuntu that is available on various Linux distributions and which handles early initialization of a cloud instance."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_userdata.xml:14(para)
+msgid "You can place user data in a local file and pass it through the <parameter>--user-data &lt;user-data-file&gt;</parameter> parameter at instance creation:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_sshkeys.xml:6(title)
+msgid "Add keypair"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_sshkeys.xml:7(para)
+msgid "Create at least one keypair for each project. If you have generated a keypair with an external tool, you can import it into OpenStack. The keypair can be used for multiple instances that belong to a project."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_sshkeys.xml:13(para)
+msgid "Create a key."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_sshkeys.xml:14(para)
+msgid "To create a <literal>mykey</literal> key that you can associate with instances, run the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_sshkeys.xml:17(para)
+msgid "Save the <filename>mykey.pem</filename> file to a secure location. It enables root access to any instances with which the <literal>mykey</literal> key is associated."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_sshkeys.xml:22(para)
+msgid "Alternatively, you can import a keypair."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_sshkeys.xml:23(para)
+msgid "To import an existing public key, <literal>mykey.pub</literal>, and associate it with the <literal>mykey</literal> key, run the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_sshkeys.xml:28(para)
+msgid "You must have the matching private key to access instances that are associated with this key."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml:6(title)
+msgid "Secure the OpenStack Identity service connection to an LDAP back end"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml:8(para)
+msgid "The Identity service supports the use of TLS to encrypt LDAP traffic. Before configuring this, you must first verify where your certificate authority file is located. For more information, see <xref linkend=\"certificates-for-pki\"/>."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml:12(para)
+msgid "Once you verify the location of your certificate authority file:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml:15(title)
+msgid "Configuring TLS encryption on LDAP traffic"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml:17(para)
+msgid "Open the <filename>/etc/keystone/keystone.conf</filename> configuration file."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml:23(para)
+msgid "Find the <literal>[ldap]</literal> section."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml:26(para)
+msgid "In the <literal>[ldap]</literal> section, set the <literal>use_tls</literal> configuration key to <literal>True</literal>. Doing so will enable TLS."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml:31(para)
+msgid "Configure the Identity service to use your certificate authorities file. To do so, set the <literal>tls_cacertfile</literal> configuration key in the <literal>ldap</literal> section to the certificate authorities file's path."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml:37(para)
+msgid "You can also set the <literal>tls_cacertdir</literal> (also in the <literal>ldap</literal> section) to the directory where all certificate authorities files are kept. If both <literal>tls_cacertfile</literal> and <literal>tls_cacertdir</literal> are set, then the latter will be ignored."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml:46(para)
+msgid "Specify what client certificate checks to perform on incoming TLS sessions from the LDAP server. To do so, set the <literal>tls_req_cert</literal> configuration key in the <literal>[ldap]</literal> section to <literal>demand</literal>, <literal>allow</literal>, or <literal>never</literal>:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml:53(para)
+msgid "<parameter>demand</parameter>: a certificate will always be requested from the LDAP server. The session will be terminated if no certificate is provided, or if the certificate provided cannot be verified against the existing certificate authorities file."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml:60(para)
+msgid "<parameter>allow</parameter>: a certificate will always be requested from the LDAP server. The session will proceed as normal even if a certificate is not provided. If a certificate is provided but it cannot be verified against the existing certificate authorities file, the certificate will be ignored and the session will proceed as normal."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml:67(para)
+msgid "<parameter>never</parameter>: a certificate will never be requested."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml:72(para)
+msgid "On distributions that include <application>openstack-config</application>, you can configure TLS encryption on LDAP traffic by running the following commands instead:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml:80(replaceable)
+msgid "CA_FILE"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml:82(replaceable)
+msgid "CERT_BEHAVIOR"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml:85(para)
+msgid "<replaceable>CA_FILE</replaceable> is the absolute path to the certificate authorities file that should be used to encrypt LDAP traffic."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml:88(para)
+msgid "<replaceable>CERT_BEHAVIOR</replaceable>: specifies what client certificate checks to perform on an incoming TLS session from the LDAP server (<literal>demand</literal>, <literal>allow</literal>, or <literal>never</literal>)."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:7(title)
+msgid "Certificates for PKI"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:8(para)
+msgid "PKI stands for Public Key Infrastructure. Tokens are documents, cryptographically signed using the X509 standard. In order to work correctly token generation requires a public/private key pair. The public key must be signed in an X509 certificate, and the certificate used to sign it must be available as Certificate Authority (CA) certificate. These files can be generated either using the <placeholder-1/> utility, or externally generated. The files need to be in the locations specified by the top level Identity Service configuration file <filename>keystone.conf</filename> as specified in the above section. Additionally, the private key should only be readable by the system user that will run the Identity Service."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:23(para)
+msgid "The certificates can be world readable, but the private key cannot be. The private key should only be readable by the account that is going to sign tokens. When generating files with the <placeholder-1/> command, your best option is to run as the pki user. If you run nova-manage as root, you can append --keystone-user and --keystone-group parameters to set the username and group keystone is going to run under."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:33(para)
+msgid "The values that specify where to read the certificates are under the <literal>[signing]</literal> section of the configuration file. The configuration values are:"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:38(para)
+msgid "<literal>token_format</literal> - Determines the algorithm used to generate tokens. Can be either <literal>UUID</literal> or <literal>PKI</literal>. Defaults to <literal>PKI</literal>."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:45(para)
+msgid "<literal>certfile</literal> - Location of certificate used to verify tokens. Default is <literal>/etc/keystone/ssl/certs/signing_cert.pem</literal>."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:51(para)
+msgid "<literal>keyfile</literal> - Location of private key used to sign tokens. Default is <literal>/etc/keystone/ssl/private/signing_key.pem</literal>."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:57(para)
+msgid "<literal>ca_certs</literal> - Location of certificate for the authority that issued the above certificate. Default is <literal>/etc/keystone/ssl/certs/ca.pem</literal>."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:64(para)
+msgid "<literal>key_size</literal> - Default is <literal>1024</literal>."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:69(para)
+msgid "<literal>valid_days</literal> - Default is <literal>3650</literal>."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:74(para)
+msgid "<literal>ca_password</literal> - Password required to read the <literal>ca_file</literal>. Default is <literal>None</literal>."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:80(para)
+msgid "If <literal>token_format=UUID</literal>, a typical token looks like <literal>53f7f6ef0cc344b5be706bcc8b1479e1</literal>. If <literal>token_format=PKI</literal>, a typical token is a much longer string, such as:"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:113(title)
+msgid "Sign certificate issued by external CA"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:114(para)
+msgid "You can use a signing certificate issued by an external CA instead of generated by <placeholder-1/>. However, a certificate issued by an external CA must satisfy the following conditions:"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:121(para)
+msgid "all certificate and key files must be in Privacy Enhanced Mail (PEM) format"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:125(para)
+msgid "private key files must not be protected by a password"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:129(para)
+msgid "When using signing certificate issued by an external CA, you do not need to specify <literal>key_size</literal>, <literal>valid_days</literal>, and <literal>ca_password</literal> as they will be ignored."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:134(para)
+msgid "The basic workflow for using a signing certificate issued by an external CA involves:"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:138(para)
+msgid "Request Signing Certificate from External CA"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:142(para)
+msgid "Convert certificate and private key to PEM if needed"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:146(para)
+msgid "Install External Signing Certificate"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:151(title)
+msgid "Request a signing certificate from an external CA"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:153(para)
+msgid "One way to request a signing certificate from an external CA is to first generate a PKCS #10 Certificate Request Syntax (CRS) using OpenSSL CLI."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:156(para)
+msgid "Create a certificate request configuration file. For example, create the <filename>cert_req.conf</filename> file, as follows:"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:176(para)
+msgid "Then generate a CRS with OpenSSL CLI. <emphasis role=\"strong\">Do not encrypt the generated private key. Must use the -nodes option.</emphasis>"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:183(para)
+msgid "If everything is successful, you should end up with <filename>signing_cert_req.pem</filename> and <filename>signing_key.pem</filename>. Send <filename>signing_cert_req.pem</filename> to your CA to request a token signing certificate and make sure to ask the certificate to be in PEM format. Also, make sure your trusted CA certificate chain is also in PEM format."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:193(title)
+msgid "Install an external signing certificate"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:194(para)
+msgid "Assuming you have the following already:"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:197(para)
+msgid "<filename>signing_cert.pem</filename> - (Keystone token) signing certificate in PEM format"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:202(para)
+msgid "<filename>signing_key.pem</filename> - corresponding (non-encrypted) private key in PEM format"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:208(para)
+msgid "<filename>cacert.pem</filename> - trust CA certificate chain in PEM format"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:213(para)
+msgid "Copy the above to your certificate directory. For example:"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:221(para)
+msgid "Make sure the certificate directory is only accessible by root."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml:224(para)
+msgid "If your certificate directory path is different from the default <filename>/etc/keystone/ssl/certs</filename>, make sure it is reflected in the <literal>[signing]</literal> section of the configuration file."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_get_console.xml:6(title)
+msgid "Access an instance through a console"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_get_console.xml:7(para)
+msgid "To access an instance through a VNC console, run the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_get_console.xml:9(para)
+msgid "The command returns a URL from which you can access your instance:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_get_console.xml:15(para)
+msgid "To access an instance through a non-VNC console, specify the <parameter>novnc</parameter> parameter instead of the <parameter>xvpvnc</parameter> parameter."
+msgstr ""
+
+#: ./doc/common/section_compute_config-firewalls.xml:6(title)
+msgid "Compute service node firewall requirements"
+msgstr ""
+
+#: ./doc/common/section_compute_config-firewalls.xml:7(para)
+msgid "Console connections for virtual machines, whether direct or through a proxy, are received on ports <literal>5900</literal> to <literal>5999</literal>. You must configure the firewall on each Compute service node to enable network traffic on these ports."
+msgstr ""
+
+#: ./doc/common/section_compute_config-firewalls.xml:11(title)
+msgid "Configure the service-node firewall"
+msgstr ""
+
+#: ./doc/common/section_compute_config-firewalls.xml:12(para)
+msgid "On the server that hosts the Compute service, log in as <systemitem>root</systemitem>."
+msgstr ""
+
+#: ./doc/common/section_compute_config-firewalls.xml:14(para)
+msgid "Edit the <filename>/etc/sysconfig/iptables</filename> file."
+msgstr ""
+
+#: ./doc/common/section_compute_config-firewalls.xml:20(para)
+msgid "Add an INPUT rule that allows TCP traffic on ports that range from <literal>5900</literal> to <literal>5999</literal>:"
+msgstr ""
+
+#: ./doc/common/section_compute_config-firewalls.xml:26(para)
+msgid "The new rule must appear before any INPUT rules that REJECT traffic."
+msgstr ""
+
+#: ./doc/common/section_compute_config-firewalls.xml:32(para)
+msgid "Save the changes to the <filename>/etc/sysconfig/iptables</filename> file."
+msgstr ""
+
+#: ./doc/common/section_compute_config-firewalls.xml:38(para)
+msgid "Restart the <systemitem>iptables</systemitem> service to ensure that the change takes effect."
+msgstr ""
+
+#: ./doc/common/section_compute_config-firewalls.xml:45(para)
+msgid "The <systemitem>iptables</systemitem> firewall now enables incoming connections to the Compute services. Repeat this process for each Compute service node."
+msgstr ""
+
+#: ./doc/common/section_about-object-storage.xml:7(title) ./doc/common/section_objectstorage-intro.xml:7(title)
+msgid "Introduction to Object Storage"
+msgstr ""
+
+#: ./doc/common/section_about-object-storage.xml:8(para)
+msgid "Object Storage is a robust, highly scalable and fault tolerant storage platform for unstructured data such as objects. Objects are stored bits, accessed through a RESTful, HTTP-based interface. You cannot access data at the block or file level. Object Storage is commonly used to archive and back up data, with use cases in virtual machine image, photo, video and music storage."
+msgstr ""
+
+#: ./doc/common/section_about-object-storage.xml:15(para)
+msgid "Object Storage provides a high degree of availability, throughput, and performance with its scale out architecture. Each object is replicated across multiple servers, residing within the same data center or across data centers, which mitigates the risk of network and hardware failure. In the event of hardware failure, Object Storage will automatically copy objects to a new location to ensure that there are always three copies available. Object Storage is an eventually consistent distributed storage platform; it sacrifices consistency for maximum availability and partition tolerance. Object Storage enables you to create a reliable platform by using commodity hardware and inexpensive storage."
+msgstr ""
+
+#: ./doc/common/section_about-object-storage.xml:27(para)
+msgid "For more information, review the key concepts in the developer documentation at <link href=\"http://docs.openstack.org/developer/swift/\">docs.openstack.org/developer/swift/</link>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:10(title)
+msgid "Launch an instance from a volume"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:11(para)
+msgid "You can boot instances from a volume instead of an image."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:12(para)
+msgid "To complete these tasks, use these parameters on the nova <placeholder-1/> command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:20(th)
+msgid "Task"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:21(th)
+msgid "nova boot parameter"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:22(th)
+msgid "See"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:27(td)
+msgid "Boot an instance from an image and attach a non-bootable volume."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:29(parameter) ./doc/common/section_cli_nova_boot_from_volume.xml:35(parameter) ./doc/common/section_cli_nova_boot_from_volume.xml:41(parameter)
+msgid "--block-device"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:33(td)
+msgid "Create a volume from an image and boot an instance from that volume."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:39(td)
+msgid "Boot from an existing source image, volume, or snapshot."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:45(td)
+msgid "Attach a swap disk to an instance."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:47(parameter)
+msgid "--swap"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:51(td)
+msgid "Attach an ephemeral disk to an instance."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:52(parameter)
+msgid "--ephemeral"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:58(para)
+msgid "To attach a volume to a running instance, see <xref linkend=\"cli_attach_volume\"/>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:62(title)
+msgid "Boot instance from image and attach non-bootable volume"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:64(para)
+msgid "Create a non-bootable volume and attach that volume to an instance that you boot from an image."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:66(para)
+msgid "To create a non-bootable volume, do not create it from an image. The volume must be entirely empty with no partition table and no file system."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:71(para)
+msgid "Create a non-bootable volume:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:98(para) ./doc/common/section_cli_cinder_manage_volumes.xml:176(para)
+msgid "List volumes:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:107(para)
+msgid "Boot an instance from an image and attach the empty volume to the instance:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:149(title)
+msgid "Create volume from image and boot instance"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:150(para)
+msgid "You can create a volume from an existing image, volume, or snapshot. This procedure shows you how to create a volume from an image, and use the volume to boot an instance."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:165(para)
+msgid "Note the ID of the image that you want to use to create a volume."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:183(para)
+msgid "Note the ID of the flavor that you want to use to create a volume."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:187(para)
+msgid "To create a bootable volume from an image and launch an instance from this volume, use the <parameter>--block-device</parameter> parameter."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:191(replaceable) ./doc/common/section_cli_nova_boot_from_volume.xml:329(replaceable)
+msgid "FLAVOR"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:191(replaceable) ./doc/common/section_cli_nova_boot_from_volume.xml:205(replaceable)
+msgid "SOURCE"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:191(replaceable) ./doc/common/section_cli_nova_boot_from_volume.xml:217(replaceable)
+msgid "ID"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:191(replaceable) ./doc/common/section_cli_nova_boot_from_volume.xml:224(replaceable)
+msgid "DEST"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:191(replaceable) ./doc/common/section_cli_nova_boot_from_volume.xml:233(replaceable)
+msgid "SIZE"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:191(replaceable)
+msgid "PRESERVE"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:191(replaceable) ./doc/common/section_cli_nova_boot_from_volume.xml:250(replaceable)
+msgid "INDEX"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:191(replaceable) ./doc/common/section_cli_nova_boot_from_volume.xml:329(replaceable)
+msgid "NAME"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:192(para)
+msgid "The parameters are:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:195(para)
+msgid "<parameter>--flavor</parameter><replaceable>FLAVOR</replaceable>. The flavor ID or name."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:200(para)
+msgid "<parameter>--block-device</parameter> source=<replaceable>SOURCE</replaceable>,id=<replaceable>ID</replaceable>,dest=<replaceable>DEST</replaceable>,size=<replaceable>SIZE</replaceable>,shutdown=<replaceable>PRESERVE</replaceable>,bootindex=<replaceable>INDEX</replaceable>"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:205(emphasis)
+msgid "source=<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:207(para)
+msgid "The type of object used to create the block device. Valid values are <literal>volume</literal>, <literal>snapshot</literal>, <literal>image</literal>, and <literal>blank</literal>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:217(emphasis)
+msgid "id=<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:219(para)
+msgid "The ID of the source object."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:224(emphasis)
+msgid "dest=<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:226(para)
+msgid "The type of the target virtual device. Valid values are <literal>volume</literal> and <literal>local</literal>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:233(emphasis)
+msgid "size=<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:235(para)
+msgid "The size of the volume that is created."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:240(emphasis)
+msgid "shutdown={preserve|remove}"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:242(para)
+msgid "What to do with the volume when the instance is deleted. <literal>preserve</literal> does not delete the volume. <literal>remove</literal> deletes the volume."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:250(emphasis)
+msgid "bootindex=<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:252(para)
+msgid "Orders the boot disks. Use <literal>0</literal> to boot from this volume."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:260(para)
+msgid "<replaceable>NAME</replaceable>. The name for the server."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:266(para)
+msgid "Create a bootable volume from an image, before the instance boots. The volume is not deleted when the instance is terminated:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:307(para)
+msgid "List volumes to see the bootable volume and its attached <literal>myInstanceFromVolume</literal> instance:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:320(title)
+msgid "Attach swap or ephemeral disk to an instance"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:321(para)
+msgid "Use the nova <placeholder-1/><parameter>--swap</parameter> parameter to attach a swap disk on boot or the nova <placeholder-2/><parameter>--ephemeral</parameter> parameter to attach an ephemeral disk on boot. When you terminate the instance, both disks are deleted."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:327(para)
+msgid "Boot an instance with a 512MB swap disk and 2GB ephemeral disk:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml:331(para)
+msgid "The flavor defines the maximum swap and ephemeral disk size. You cannot exceed these maximum values."
+msgstr ""
+
+#: ./doc/common/section_xapi-resize-setup.xml:7(title)
+msgid "Modify Dom0 for resize/migration support"
+msgstr ""
+
+#: ./doc/common/section_xapi-resize-setup.xml:8(para)
+msgid "To resize servers with XenServer and XCP, you must:"
+msgstr ""
+
+#: ./doc/common/section_xapi-resize-setup.xml:11(para)
+msgid "Establish a root trust between all hypervisor nodes of your deployment:"
+msgstr ""
+
+#: ./doc/common/section_xapi-resize-setup.xml:13(para)
+msgid "To do so, generate an ssh key-pair with the <placeholder-1/> command. Ensure that each of your dom0's <filename>authorized_keys</filename> file (located in <filename>/root/.ssh/authorized_keys</filename>) contains the public key fingerprint (located in <filename>/root/.ssh/id_rsa.pub</filename>)."
+msgstr ""
+
+#: ./doc/common/section_xapi-resize-setup.xml:22(para)
+msgid "Provide an <filename>/images</filename> mount point to the dom0 for your hypervisor:"
+msgstr ""
+
+#: ./doc/common/section_xapi-resize-setup.xml:24(para)
+msgid "Dom0 space is at a premium so creating a directory in dom0 is potentially dangerous and likely to fail especially when you resize large servers. The least you can do is to symlink <filename>/images</filename> to your local storage SR. The following instructions work for an English-based installation of XenServer (and XCP) and in the case of ext3-based SR (with which the resize functionality is known to work correctly)."
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_dashboard_access.xml:89(None)
+msgid "@@image: 'figures/dashboard-project-tab.png'; md5=5b192a3d34c9285dbacd875395b8e4cc"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_dashboard_access.xml:214(None)
+msgid "@@image: 'figures/dashboard-admin-tab.png'; md5=039358c76c549d7d423da5b8aa826435"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:12(title)
+msgid "Log in to the dashboard"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:13(para)
+msgid "The dashboard is available on the node with the <literal>nova-dashboard</literal> server role."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:17(para)
+msgid "Ask the cloud operator for the host name or public IP address from which you can access the dashboard, and for your user name and password."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:22(para)
+msgid "Open a web browser that has JavaScript and cookies enabled."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:25(para)
+msgid "To use the Virtual Network Computing (VNC) client for the dashboard, your browser must support HTML5 Canvas and HTML5 WebSockets. The VNC client is based on noVNC. For details, see <link href=\"https://github.com/kanaka/noVNC/blob/master/README.md\">noVNC: HTML5 VNC Client</link>. For a list of supported browsers, see <link href=\"https://github.com/kanaka/noVNC/wiki/Browser-support\">Browser support</link>."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:38(para)
+msgid "In the address bar, enter the host name or IP address for the dashboard."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:40(replaceable)
+msgid "ipAddressOrHostName"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:42(para)
+msgid "If a certificate warning appears when you try to access the URL for the first time, a self-signed certificate is in use, which is not considered trustworthy by default. Verify the certificate or add an exception in the browser to bypass the warning."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:51(para)
+msgid "On the <guilabel>Log In</guilabel> page, enter your user name and password, and click <guibutton>Sign In</guibutton>."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:54(para)
+msgid "The top of the window displays your user name. You can also access <guilabel>Settings</guilabel> or sign out of the dashboard."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:61(para)
+msgid "If you are logged in as an end user, the <link linkend=\"dashboard_project_tab\">Project</link> tab is displayed."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:65(para)
+msgid "If you are logged in as an administrator, the <link linkend=\"dashboard_project_tab\">Project</link> tab and <link linkend=\"dashboard_admin_tab\">Admin</link> tab are displayed."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:57(para)
+msgid "The visible tabs and functions in the dashboard depend on the access permissions, or <emphasis role=\"italic\">roles</emphasis>, of the user you are logged in as.<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:75(title)
+msgid "OpenStack dashboardProject tab"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:76(para)
+msgid "Projects are organizational units in the cloud, and are also known as tenants or accounts. Each user is a member of one or more projects. Within a project, a user creates and manages instances."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:80(para)
+msgid "From the <guilabel>Project</guilabel> tab, you can view and manage the resources in a selected project, including instances and images. You select the project from the <guilabel>CURRENT PROJECT</guilabel> list at the top of the tab."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:85(title)
+msgid "Project tab"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:93(para)
+msgid "From the <guilabel>Project</guilabel> tab, you can access the following tabs:"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:100(th) ./doc/common/section_dashboard_access.xml:170(th) ./doc/common/section_dashboard_access.xml:185(th) ./doc/common/section_dashboard_access.xml:192(th) ./doc/common/section_dashboard_access.xml:224(th) ./doc/common/section_dashboard_access.xml:350(th)
+msgid "<placeholder-1/> tab"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:106(para)
+msgid "View reports for the project."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:109(guilabel) ./doc/common/section_dashboard_access.xml:292(guilabel)
+msgid "Instances"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:110(para)
+msgid "View, launch, create a snapshot from, stop, pause, or reboot instances, or connect to them through VNC."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:114(guilabel) ./doc/common/section_dashboard_access.xml:119(guilabel) ./doc/common/section_dashboard_access.xml:299(guilabel)
+msgid "Volumes"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:115(para) ./doc/common/section_dashboard_access.xml:141(para)
+msgid "Use the following tabs to complete these tasks:"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:121(para)
+msgid "View, create, edit, and delete volumes."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:125(guilabel)
+msgid "Volume Snapshots"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:127(para)
+msgid "View, create, edit, and delete volume snapshots."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:133(guilabel) ./doc/common/section_dashboard_access.xml:309(guilabel)
+msgid "Images"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:134(para)
+msgid "View images and instance snapshots created by project users, plus any images that are publicly available. Create, edit, and delete images, and launch instances from images and snapshots."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:140(guilabel)
+msgid "Access &amp; Security"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:144(guilabel)
+msgid "Security Groups"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:145(para)
+msgid "View, create, edit, and delete security groups and security group rules."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:150(guilabel)
+msgid "Key Pairs"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:151(para)
+msgid "View, create, edit, import, and delete key pairs."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:156(guilabel)
+msgid "Floating IPs"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:158(para)
+msgid "Allocate an IP address to or release it from a project."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:163(guilabel)
+msgid "API Access"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:164(para)
+msgid "View API endpoints."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:170(guilabel)
+msgid "Network"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:173(guilabel)
+msgid "Network Topology"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:174(para)
+msgid "View the network topology."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:177(guilabel) ./doc/common/section_dashboard_access.xml:314(guilabel)
+msgid "Networks"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:178(para)
+msgid "Create and manage public and private networks."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:181(guilabel) ./doc/common/section_dashboard_access.xml:318(guilabel)
+msgid "Routers"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:182(para)
+msgid "Create and manage subnets."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:185(guilabel)
+msgid "Object Store"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:188(guilabel) ./doc/common/section_dashboard_access.xml:195(guilabel)
+msgid "Containers"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:189(para)
+msgid "Create and manage containers and objects."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:196(para)
+msgid "Use the REST API to orchestrate multiple composite cloud applications."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:203(title)
+msgid "OpenStack dashboardAdmin tab"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:204(para)
+msgid "Administrative users can use the <guilabel>Admin</guilabel> tab to view usage and to manage instances, volumes, flavors, images, projects, users, services, and quotas."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:209(title)
+msgid "Admin tab"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:218(para)
+msgid "Access the following categories to complete these tasks:"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:224(guilabel)
+msgid "System Panel"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:230(para)
+msgid "View basic reports."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:233(guilabel)
+msgid "Resource Usage"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:234(para)
+msgid "Use the following tabs to view the following usages:"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:269(guilabel)
+msgid "Daily Report"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:271(para)
+msgid "View the daily report."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:275(guilabel)
+msgid "Stats"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:277(para)
+msgid "View the statistics of all resources."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:283(guilabel)
+msgid "Hypervisors"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:284(para)
+msgid "View the hypervisor summary."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:287(guilabel)
+msgid "Host Aggregates"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:288(para)
+msgid "View, create, and edit host aggregates. View the list of availability zones."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:293(para)
+msgid "View, pause, resume, suspend, migrate, soft or hard reboot, and delete running instances that belong to users of some, but not all, projects. Also, view the log for an instance or access an instance through VNC."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:300(para)
+msgid "View, create, edit, and delete volumes and volume types."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:305(para)
+msgid "View, create, edit, view extra specifications for, and delete flavors. A flavor is size of an instance."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:310(para)
+msgid "View, create, edit properties for, and delete custom images."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:315(para)
+msgid "View, create, edit properties for, and delete networks."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:319(para)
+msgid "View, create, edit properties for, and delete routers."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:322(guilabel)
+msgid "System Info"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:323(para)
+msgid "Use the following tabs to view the service information:"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:326(guilabel)
+msgid "Services"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:327(para)
+msgid "View a list of the services."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:331(guilabel)
+msgid "Compute Services"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:332(para)
+msgid "View a list of all Compute services."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:336(guilabel)
+msgid "Network Agents"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:337(para)
+msgid "View the network agents."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:341(guilabel)
+msgid "Default Quotas"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:342(para)
+msgid "View default quota values. Quotas are hard-coded in OpenStack Compute and define the maximum allowable size and number of resources."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:350(guilabel)
+msgid "Identity Panel"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:358(guilabel)
+msgid "Projects"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:359(para)
+msgid "View, create, assign users to, remove users from, and delete projects."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:363(guilabel)
+msgid "Users"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml:364(para)
+msgid "View, create, enable, disable, and delete users."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml:6(title)
+msgid "Show usage statistics for hosts and instances"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml:7(para)
+msgid "You can show basic statistics on resource usage for hosts and instances."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml:10(para)
+msgid "For more sophisticated monitoring, see the <link href=\"https://launchpad.net/ceilometer\">ceilometer</link> project. You can also use tools, such as <link href=\"http://ganglia.info/\">Ganglia</link> or <link href=\"http://graphite.wikidot.com/\">Graphite</link>, to gather more detailed data."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml:20(title)
+msgid "Show host usage statistics"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml:21(para)
+msgid "The following examples show the host usage statistics for a host called <filename>devstack</filename>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml:25(para)
+msgid "List the hosts and the nova-related services that run on them:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml:37(para)
+msgid "Get a summary of resource usage of all of the instances running on the host:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml:49(para)
+msgid "The <literal>cpu</literal> column shows the sum of the virtual CPUs for instances running on the host."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml:51(para)
+msgid "The <literal>memory_mb</literal> column shows the sum of the memory (in MB) allocated to the instances that run on the host."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml:54(para)
+msgid "The <literal>disk_gb</literal> column shows the sum of the root and ephemeral disk sizes (in GB) of the instances that run on the host."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml:57(para)
+msgid "The row that has the value <literal>used_now</literal> in the <literal>PROJECT</literal> column shows the sum of the resources allocated to the instances that run on the host, plus the resources allocated to the virtual machine of the host itself."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml:62(para)
+msgid "The row that has the value <literal>used_max</literal> row in the <literal>PROJECT</literal> column shows the sum of the resources allocated to the instances that run on the host."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml:68(para)
+msgid "These values are computed by using information about the flavors of the instances that run on the hosts. This command does not query the CPU usage, memory usage, or hard disk usage of the physical host."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml:75(title)
+msgid "Show instance usage statistics"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml:77(para)
+msgid "Get CPU, memory, I/O, and network statistics for an instance."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml:79(para)
+msgid "List instances:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml:87(para)
+msgid "Get diagnostic statistics:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml:108(para)
+msgid "Get summary statistics for each tenant:"
+msgstr ""
+
 #: ./doc/common/section_cli_openrc.xml:7(title)
 msgid "Set environment variables using the OpenStack RC file"
 msgstr ""
@@ -17173,120 +14816,1741 @@ msgstr ""
 msgid "Where <replaceable>PASSWORD</replaceable> is your password."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml:5(title)
-msgid "Manage bare-metal nodes"
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-components.xml:43(None)
+msgid "@@image: '../common/figures/objectstorage-buildingblocks.png'; md5=ed79466c8464513dbeaf1e0954280e5e"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml:6(para)
-msgid "The bare-metal driver for OpenStack Compute manages provisioning of physical hardware by using common cloud APIs and tools such as Orchestration (Heat). The use case for this driver is for single tenant clouds such as a high-performance computing cluster or for deploying OpenStack itself."
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-components.xml:86(None)
+msgid "@@image: '../common/figures/objectstorage-ring.png'; md5=a94e26734cec6980c3684d9e824eac2d"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml:10(para)
-msgid "If you use the bare-metal driver, you must create a network interface and add it to a bare-metal node. Then, you can launch an instance from a bare-metal image."
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-components.xml:126(None)
+msgid "@@image: '../common/figures/objectstorage-zones.png'; md5=1b1dc0abe6ea0c516f22ce399deb75ed"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml:13(para)
-msgid "Development efforts are focused on moving the driver out of the Compute code base in the Icehouse release."
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-components.xml:144(None)
+msgid "@@image: '../common/figures/objectstorage-accountscontainers.png'; md5=4b15e5a202db5bde53c9b369058aeab8"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml:15(para)
-msgid "You can list and delete bare-metal nodes. When you delete a node, any associated network interfaces are removed. You can list and remove network interfaces that are associated with a bare-metal node."
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-components.xml:169(None)
+msgid "@@image: '../common/figures/objectstorage-partitions.png'; md5=2c161c2e92d6fefc8140ec86e79e9492"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml:19(title)
-msgid "Commands"
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-components.xml:195(None)
+msgid "@@image: '../common/figures/objectstorage-replication.png'; md5=9d55594d7f445764569ab04d8d4373b2"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml:20(para)
-msgid "The following commands can be used to manage bare-metal nodes."
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-components.xml:222(None)
+msgid "@@image: '../common/figures/objectstorage-usecase.png'; md5=07480e7175b383171173775fb96d70d7"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml:22(para)
-msgid "<placeholder-1/>. Adds a network interface to a bare-metal node."
+#: ./doc/common/section_objectstorage-components.xml:7(title)
+msgid "Components"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml:26(para)
-msgid "<placeholder-1/>. Lists network interfaces associated with a bare-metal node."
+#: ./doc/common/section_objectstorage-components.xml:8(para)
+msgid "The components that enable Object Storage to deliver high availability, high durability, and high concurrency are:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml:30(para)
-msgid "<placeholder-1/>. Removes a network interface from a bare-metal node."
+#: ./doc/common/section_objectstorage-components.xml:12(para)
+msgid "<emphasis role=\"bold\">Proxy servers.</emphasis> Handle all of the incoming API requests."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml:34(para)
-msgid "<placeholder-1/>. Creates a bare-metal node."
+#: ./doc/common/section_objectstorage-components.xml:16(para)
+msgid "<emphasis role=\"bold\">Rings.</emphasis> Map logical names of data to locations on particular disks."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml:38(para)
-msgid "<placeholder-1/>. Removes a bare-metal node and any associated interfaces."
+#: ./doc/common/section_objectstorage-components.xml:20(para)
+msgid "<emphasis role=\"bold\">Zones.</emphasis> Isolate data from other zones. A failure in one zone doesn’t impact the rest of the cluster because data is replicated across zones."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml:42(para)
-msgid "<placeholder-1/>. Lists available bare-metal nodes."
+#: ./doc/common/section_objectstorage-components.xml:25(para)
+msgid "<emphasis role=\"bold\">Accounts and containers.</emphasis> Each account and container are individual databases that are distributed across the cluster. An account database contains the list of containers in that account. A container database contains the list of objects in that container."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml:46(para)
-msgid "<placeholder-1/>. Shows information about a bare-metal node."
+#: ./doc/common/section_objectstorage-components.xml:31(para)
+msgid "<emphasis role=\"bold\">Objects.</emphasis> The data itself."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml:51(title)
-msgid "Create a bare-metal node"
+#: ./doc/common/section_objectstorage-components.xml:34(para)
+msgid "<emphasis role=\"bold\">Partitions.</emphasis> A partition stores objects, account databases, and container databases and helps manage locations where data lives in the cluster."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml:52(para)
-msgid "When you create a bare-metal node, your PM address, username, and password should match those that are configured in your hardware's BIOS/IPMI configuration."
+#: ./doc/common/section_objectstorage-components.xml:40(title)
+msgid "Object Storage building blocks"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml:57(para)
-msgid "The following example shows the command and results from creating a node with the PM address <filename>1.2.3.4</filename>, the PM username <literal>ipmi</literal>, and password <literal>ipmi</literal>."
+#: ./doc/common/section_objectstorage-components.xml:48(title)
+msgid "Proxy servers"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml:79(title)
-msgid "Add a network interface to the node:"
+#: ./doc/common/section_objectstorage-components.xml:49(para)
+msgid "Proxy servers are the public face of Object Storage and handle all of the incoming API requests. Once a proxy server receives a request, it determines the storage node based on the object's URL, for example, https://swift.example.com/v1/account/container/object. Proxy servers also coordinate responses, handle failures, and coordinate timestamps."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml:80(para)
-msgid "For each NIC on the node, you must create an interface, specifying the interface's MAC address."
+#: ./doc/common/section_objectstorage-components.xml:54(para)
+msgid "Proxy servers use a shared-nothing architecture and can be scaled as needed based on projected workloads. A minimum of two proxy servers should be deployed for redundancy. If one proxy server fails, the others take over."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml:92(title)
-msgid "Launch an instance from a bare-metal image:"
+#: ./doc/common/section_objectstorage-components.xml:59(title)
+msgid "Rings"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml:94(para)
-msgid "A bare-metal instance is an instance created directly on a physical machine without any virtualization layer running underneath it. Nova retains power control via IPMI. In some situations, Nova may retain network control via Neutron and OpenFlow."
+#: ./doc/common/section_objectstorage-components.xml:60(para)
+msgid "A ring represents a mapping between the names of entities stored on disk and their physical locations. There are separate rings for accounts, containers, and objects. When other components need to perform any operation on an object, container, or account, they need to interact with the appropriate ring to determine their location in the cluster."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml:107(para)
-msgid "Set the <parameter>--availability_zone</parameter> parameter to specify which zone or node to use to start the server. Separate the zone from the host name with a comma. For example:"
+#: ./doc/common/section_objectstorage-components.xml:65(para)
+msgid "The ring maintains this mapping using zones, devices, partitions, and replicas. Each partition in the ring is replicated, by default, three times across the cluster, and partition locations are stored in the mapping maintained by the ring. The ring is also responsible for determining which devices are used for handoff in failure scenarios."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml:110(replaceable)
-msgid "HOST"
+#: ./doc/common/section_objectstorage-components.xml:70(para)
+msgid "Data can be isolated into zones in the ring. Each partition replica is guaranteed to reside in a different zone. A zone could represent a drive, a server, a cabinet, a switch, or even a data center."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml:110(replaceable)
-msgid "NODE"
+#: ./doc/common/section_objectstorage-components.xml:73(para)
+msgid "The partitions of the ring are equally divided among all of the devices in the Object Storage installation. When partitions need to be moved around (for example, if a device is added to the cluster), the ring ensures that a minimum number of partitions are moved at a time, and only one replica of a partition is moved at a time."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml:111(para)
-msgid "<literal>host</literal> is optional for the <literal>--availability_zone</literal> parameter. You can specify simply <literal>zone:,node</literal>. You must still use the comma."
+#: ./doc/common/section_objectstorage-components.xml:77(para)
+msgid "Weights can be used to balance the distribution of partitions on drives across the cluster. This can be useful, for example, when differently sized drives are used in a cluster."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml:118(title)
-msgid "List bare-metal nodes and interfaces:"
+#: ./doc/common/section_objectstorage-components.xml:80(para)
+msgid "The ring is used by the proxy server and several background processes (like replication)."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml:120(para)
-msgid "Use the <placeholder-1/> command to view all bare-metal nodes and interfaces. When a node is in use, its status includes the UUID of the instance that runs on it:"
+#: ./doc/common/section_objectstorage-components.xml:83(title)
+msgid "The <emphasis role=\"bold\">ring</emphasis>"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml:130(title)
-msgid "Show details for a bare-metal node:"
+#: ./doc/common/section_objectstorage-components.xml:90(para)
+msgid "These rings are externally managed, in that the server processes themselves do not modify the rings, they are instead given new rings modified by other tools."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml:131(para)
-msgid "Use the <placeholder-1/> command to view the details for a bare-metal node."
+#: ./doc/common/section_objectstorage-components.xml:92(para)
+msgid "The ring uses a configurable number of bits from a path’s MD5 hash as a partition index that designates a device. The number of bits kept from the hash is known as the partition power, and 2 to the partition power indicates the partition count. Partitioning the full MD5 hash ring allows other parts of the cluster to work in batches of items at once which ends up either more efficient or at least less complex than working with each item separately or the entire cluster all at once."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml:101(para)
+msgid "Another configurable value is the replica count, which indicates how many of the partition-device assignments make up a single ring. For a given partition number, each replica’s device will not be in the same zone as any other replica's device. Zones can be used to group devices based on physical locations, power separations, network separations, or any other attribute that would improve the availability of multiple replicas at the same time."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml:109(title) ./doc/common/section_objectstorage-components.xml:123(title)
+msgid "Zones"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml:110(para)
+msgid "Object Storage allows configuring zones in order to isolate failure boundaries. Each data replica resides in a separate zone, if possible. At the smallest level, a zone could be a single drive or a grouping of a few drives. If there were five object storage servers, then each server would represent its own zone. Larger deployments would have an entire rack (or multiple racks) of object servers, each representing a zone. The goal of zones is to allow the cluster to tolerate significant outages of storage servers without losing all replicas of the data."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml:117(para)
+msgid "As mentioned earlier, everything in Object Storage is stored, by default, three times. Swift will place each replica \"as-uniquely-as-possible\" to ensure both high availability and high durability. This means that when chosing a replica location, Object Storage chooses a server in an unused zone before an unused server in a zone that already has a replica of the data."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml:130(para)
+msgid "When a disk fails, replica data is automatically distributed to the other zones to ensure there are three copies of the data."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml:134(title) ./doc/common/section_objectstorage-components.xml:141(title)
+msgid "Accounts and containers"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml:135(para)
+msgid "Each account and container is an individual SQLite database that is distributed across the cluster. An account database contains the list of containers in that account. A container database contains the list of objects in that container."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml:148(para)
+msgid "To keep track of object data locations, each account in the system has a database that references all of its containers, and each container database references each object."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml:153(title) ./doc/common/section_objectstorage-components.xml:166(title)
+msgid "Partitions"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml:154(para)
+msgid "A partition is a collection of stored data, including account databases, container databases, and objects. Partitions are core to the replication system."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml:156(para)
+msgid "Think of a partition as a bin moving throughout a fulfillment center warehouse. Individual orders get thrown into the bin. The system treats that bin as a cohesive entity as it moves throughout the system. A bin is easier to deal with than many little things. It makes for fewer moving parts throughout the system."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml:160(para)
+msgid "System replicators and object uploads/downloads operate on partitions. As the system scales up, its behavior continues to be predictable because the number of partitions is a fixed number."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml:163(para)
+msgid "Implementing a partition is conceptually simple, a partition is just a directory sitting on a disk with a corresponding hash table of what it contains."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml:175(title)
+msgid "Replicators"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml:176(para)
+msgid "In order to ensure that there are three copies of the data everywhere, replicators continuously examine each partition. For each local partition, the replicator compares it against the replicated copies in the other zones to see if there are any differences."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml:180(para)
+msgid "The replicator knows if replication needs to take place by examining hashes. A hash file is created for each partition, which contains hashes of each directory in the partition. Each of the three hash files is compared. For a given partition, the hash files for each of the partition's copies are compared. If the hashes are different, then it is time to replicate, and the directory that needs to be replicated is copied over."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml:186(para)
+msgid "This is where partitions come in handy. With fewer things in the system, larger chunks of data are transferred around (rather than lots of little TCP connections, which is inefficient) and there is a consistent number of hashes to compare."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml:189(para)
+msgid "The cluster eventually has a consistent behavior where the newest data has a priority."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml:199(para)
+msgid "If a zone goes down, one of the nodes containing a replica notices and proactively copies data to a handoff location."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml:203(title)
+msgid "Use cases"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml:204(para)
+msgid "The following sections show use cases for object uploads and downloads and introduce the components."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml:206(title)
+msgid "Upload"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml:207(para)
+msgid "A client uses the REST API to make a HTTP request to PUT an object into an existing container. The cluster receives the request. First, the system must figure out where the data is going to go. To do this, the account name, container name, and object name are all used to determine the partition where this object should live."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml:211(para)
+msgid "Then a lookup in the ring figures out which storage nodes contain the partitions in question."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml:213(para)
+msgid "The data is then sent to each storage node where it is placed in the appropriate partition. At least two of the three writes must be successful before the client is notified that the upload was successful."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml:216(para)
+msgid "Next, the container database is updated asynchronously to reflect that there is a new object in it."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml:219(title)
+msgid "Object Storage in use"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml:228(title)
+msgid "Download"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml:229(para)
+msgid "A request comes in for an account/container/object. Using the same consistent hashing, the partition name is generated. A lookup in the ring reveals which storage nodes contain that partition. A request is made to one of the storage nodes to fetch the object and, if that fails, requests are made to the other nodes."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:11(title)
+msgid "Manage volumes"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:12(para)
+msgid "A volume is a detachable block storage device, similar to a USB hard drive. You can attach a volume to only one instance. To create and manage volumes, you use a combination of <placeholder-1/> and <placeholder-2/> client commands."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:16(title)
+msgid "Migrate a volume"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:17(para)
+msgid "As an administrator, you can migrate a volume with its data from one location to another in a manner that is transparent to users and workloads. You can migrate only detached volumes with no snapshots."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:21(para)
+msgid "Possible use cases for data migration include:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:24(para)
+msgid "Bring down a physical storage device for maintenance without disrupting workloads."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:28(para)
+msgid "Modify the properties of a volume."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:31(para)
+msgid "Free up space in a thinly-provisioned back end."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:35(para)
+msgid "Migrate a volume with the <placeholder-1/> command, as shown in the following example:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:36(replaceable) ./doc/common/section_cli_cinder_manage_volumes.xml:274(replaceable)
+msgid "volumeID"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:36(replaceable)
+msgid "destinationHost"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:36(replaceable)
+msgid "True|False"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:37(para)
+msgid "In this example, <literal>--force-host-copy=True</literal> forces the generic host-based migration mechanism and bypasses any driver optimizations."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:40(para)
+msgid "If the volume is in use or has snapshots, the specified host destination cannot accept the volume. If the user is not an administrator, the migration fails."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:45(title)
+msgid "Create a volume"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:46(para)
+msgid "This example creates a my-new-volume volume based on an image."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:49(para)
+msgid "List images, and note the ID of the image that you want to use for your volume:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:62(para)
+msgid "List the availability zones, and note the ID of the availability zone in which you want to create your volume:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:81(para)
+msgid "Create a volume with 8GB of space, and specify the availability zone and image:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:103(para)
+msgid "To verify that your volume was created successfully, list the available volumes:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:112(para)
+msgid "If your volume was created successfully, its status is <literal>available</literal>. If its status is <literal>error</literal>, you might have exceeded your quota."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:120(title)
+msgid "Attach a volume to an instance"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:123(para)
+msgid "Attach your volume to a server, specifying the server ID and the volume ID:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:133(para)
+msgid "Note the ID of your volume."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:136(para)
+msgid "Show information for your volume:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:138(para)
+msgid "The output shows that the volume is attached to the server with ID <literal>84c6e57d-a6b1-44b6-81eb-fcb36afd31b5</literal>, is in the nova availability zone, and is bootable."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:165(title)
+msgid "Resize a volume"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:168(para)
+msgid "To resize your volume, you must first detach it from the server."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:170(para)
+msgid "To detach the volume from your server, pass the server ID and volume ID to the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:172(para) ./doc/common/section_cli_cinder_manage_volumes.xml:191(para)
+msgid "The <placeholder-1/> command does not return any output."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:184(para)
+msgid "Note that the volume is now available."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:187(para)
+msgid "Resize the volume by passing the volume ID and the new size (a value greater than the old one) as parameters:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:197(title)
+msgid "Delete a volume"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:200(para)
+msgid "To delete your volume, you must first detach it from the server."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:202(para)
+msgid "To detach the volume from your server and check for the list of existing volumes, see steps 1 and 2 in <xref linkend=\"cli_extend_volumes\"/>."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:206(para)
+msgid "Delete the volume using either the volume name or ID:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:208(para)
+msgid "The delete command does not return any output."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:212(para)
+msgid "List the volumes again, and note that the status of your volume is <literal>deleting</literal>:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:222(para)
+msgid "When the volume is fully deleted, it disappears from the list of volumes:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:234(title)
+msgid "Transfer a volume"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:235(para)
+msgid "You can transfer a volume from one owner to another by using the <placeholder-1/> commands. The volume donor, or original owner, creates a transfer request and sends the created transfer ID and authorization key to the volume recipient. The volume recipient, or new owner, accepts the transfer by using the ID and key."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:243(para)
+msgid "The procedure for volume transfer is intended for tenants (both the volume donor and recipient) within the same cloud."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:245(para)
+msgid "Use cases include:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:248(para)
+msgid "Create a custom bootable volume or a volume with a large data set and transfer it to a customer."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:251(para)
+msgid "For bulk import of data to the cloud, the data ingress system creates a new Block Storage volume, copies data from the physical device, and transfers device ownership to the end user."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:258(title)
+msgid "Create a volume transfer request"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:261(para)
+msgid "While logged in as the volume donor, list the available volumes:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:271(para)
+msgid "As the volume donor, request a volume transfer authorization code for a specific volume:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:275(para)
+msgid "The volume must be in an <literal>available</literal> state or the request will be denied. If the transfer request is valid in the database (that is, it has not expired or been deleted), the volume is placed in an <literal>awaiting transfer</literal> state. For example:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:279(para)
+msgid "The output shows the volume transfer ID in the <literal>id</literal> row and the authorization key."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:291(para)
+msgid "Optionally, you can specify a name for the transfer by using the <code>--display-name <replaceable>displayName</replaceable></code> parameter."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:299(para)
+msgid "Send the volume transfer ID and authorization key to the new owner (for example, by email)."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:304(para)
+msgid "View pending transfers:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:313(para)
+msgid "After the volume recipient, or new owner, accepts the transfer, you can see that the transfer is no longer available:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:325(title)
+msgid "Accept a volume transfer request"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:328(para)
+msgid "As the volume recipient, you must first obtain the transfer ID and authorization key from the original owner."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:333(para)
+msgid "Display the transfer request details by using the ID:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:334(replaceable) ./doc/common/section_cli_cinder_manage_volumes.xml:348(replaceable) ./doc/common/section_cli_cinder_manage_volumes.xml:392(replaceable)
+msgid "transferID"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:347(para)
+msgid "Accept the request:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:348(replaceable)
+msgid "authKey"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:359(para)
+msgid "If you do not have a sufficient quota for the transfer, the transfer is refused."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:367(title)
+msgid "Delete a volume transfer"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:371(para)
+msgid "List available volumes and their statuses:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:382(para)
+msgid "Find the matching transfer ID:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:391(para)
+msgid "Delete the volume:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml:397(para)
+msgid "Verify that transfer list is now empty and that the volume is again available for transfer:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_search_ip.xml:7(title)
+msgid "Search for an instance using IP address"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_search_ip.xml:8(para)
+msgid "You can search for an instance using the IP address parameter, <literal>--ip</literal>, with the <placeholder-1/> command."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_search_ip.xml:11(parameter) ./doc/common/section_cli_nova_search_ip.xml:14(parameter)
+msgid "ip"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_search_ip.xml:11(replaceable)
+msgid "IP_ADDRESS"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_search_ip.xml:12(para)
+msgid "The following example shows the results of a search on <filename>10.0.0.4</filename>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_search_ip.xml:14(replaceable)
+msgid "10.0.0.4"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:5(title)
+msgid "OpenStack Compute"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:6(para)
+msgid "OpenStack Compute is used to host and manage cloud computing systems and is a major part of an infrastructure-as-a-service (IaaS) system. The main modules are implemented in Python."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:9(para)
+msgid "OpenStack Compute interacts with OpenStack Identity for authentication, OpenStack Image Service for images, and OpenStack dashboard for the user and administrative interface. Access to images is limited by project and by user; quotas are limited per project (for example, the number of instances). OpenStack Compute can scale horizontally on standard hardware, and download images to launch instances."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:15(para)
+msgid "OpenStack Compute consists of the following areas and their components:"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:17(title)
+msgid "API"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:19(systemitem)
+msgid "nova-api service"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:20(para)
+msgid "Accepts and responds to end user compute API calls. Supports the OpenStack Compute API, the Amazon EC2 API, and a special Admin API for privileged users to perform administrative actions. It enforces some policies and initiates most orchestration activities, such as running an instance."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:28(term)
+msgid "<systemitem class=\"service\">nova-api-metadata</systemitem> service"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:30(para)
+msgid "Accepts metadata requests from instances. The <systemitem class=\"service\">nova-api-metadata</systemitem> service is generally used when you run in multi-host mode with <systemitem class=\"service\">nova-network</systemitem> installations. For details, see <link href=\"http://docs.openstack.org/admin-guide-cloud/content/section_metadata-service.html\">Metadata service</link> in the <citetitle>Cloud Administrator Guide</citetitle>."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:38(para)
+msgid "On Debian systems, it is included in the <systemitem class=\"service\">nova-api</systemitem> package, and can be selected through <package>debconf</package>."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:44(title)
+msgid "Compute core"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:46(term)
+msgid "<systemitem class=\"service\">nova-compute</systemitem> process"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:47(para)
+msgid "A worker daemon that creates and terminates virtual machine instances through hypervisor APIs. For example, XenAPI for XenServer/XCP, libvirt for KVM or QEMU and VMwareAPI for VMware. Processing is fairly complex but fundamentally it accepts actions from the queue and performs a series of system commands, like launching a KVM instance, whilst updating its state in the database."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:56(term)
+msgid "<systemitem class=\"service\">nova-scheduler</systemitem> process"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:58(para)
+msgid "Conceptually the simplest piece of code in OpenStack Compute. It takes a virtual machine instance request from the queue and determines on which compute server host it will run."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:64(term)
+msgid "<systemitem class=\"service\">nova-conductor</systemitem> module"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:65(para)
+msgid "Mediates interactions between <systemitem class=\"service\">nova-compute</systemitem> and the database. It eliminates direct accesses to the cloud database made by <systemitem class=\"service\">nova-compute</systemitem>. The <systemitem class=\"service\">nova-conductor</systemitem> module scales horizontally. However, do not deploy it on any nodes where <systemitem class=\"service\">nova-compute</systemitem> runs. For more information, see <link href=\"http://russellbryantnet.wordpress.com/2012/11/19/a-new-nova-service-nova-conductor/\">A new Nova service: nova-conductor</link>."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:79(title)
+msgid "Networking for VMs"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:80(term)
+msgid "<systemitem class=\"service\">nova-network</systemitem> worker daemon"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:82(para)
+msgid "Similar to <systemitem class=\"service\">nova-compute</systemitem>, it accepts networking tasks from the queue and performs tasks to manipulate the network, such as setting up bridging interfaces or changing iptables rules. This functionality is being migrated to OpenStack Networking."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:90(term)
+msgid "<systemitem class=\"service\">nova-dhcpbridge</systemitem> script"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:92(para)
+msgid "The IP address leases and is recorded in the database using the dnsmasq <literal>dhcp-script</literal> facility. This functionality is being migrated to OpenStack Networkin which provides a different script."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:99(title)
+msgid "Console interface"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:101(term)
+msgid "<systemitem class=\"service\">nova-consoleauth</systemitem> daemon"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:102(para)
+msgid "Authorizes tokens for users that console proxies provide. See <systemitem class=\"service\">nova-novncproxy</systemitem> and <systemitem class=\"service\">nova-xvpnvcproxy</systemitem>. This service must be running for console proxies to work. Many proxies of either type can be run against a single <systemitem class=\"service\">nova-consoleauth</systemitem> service in a cluster configuration. For information, see <link href=\"http://docs.openstack.org/trunk/config-reference/content/about-nova-consoleauth.html\">About nova-consoleauth</link>."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:114(term)
+msgid "<systemitem class=\"service\">nova-novncproxy</systemitem> daemon"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:116(para)
+msgid "Provides a proxy for accessing running instances through a VNC connection. Supports browser-based novnc clients."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:121(term)
+msgid "<systemitem class=\"service\">nova-xvpnvncproxy</systemitem> daemon"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:123(para)
+msgid "A proxy for accessing running instances through a VNC connection. It supports a Java client specifically designed for OpenStack."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:128(term)
+msgid "<systemitem class=\"service\">nova-cert</systemitem> daemon"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:129(para)
+msgid "x509 certificates."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:132(para)
+msgid "In Debian, a unique <package>nova-consoleproxy</package> package provides the <package>nova-novncproxy</package>, <package>nova-spicehtml5proxy</package>, and <package>nova-xvpvncproxy</package> packages. To select packages, edit the <filename>/etc/default/nova-consoleproxy</filename> file or use the <package>debconf</package> interface. You can also manually edit the <filename>/etc/default/nova-consoleproxy</filename> file, and stop and start the console daemons."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:142(title)
+msgid "Image management (EC2 scenario)"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:144(term)
+msgid "<systemitem class=\"service\">nova-objectstore</systemitem> daemon"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:145(para)
+msgid "A S3 interface for registering images with the OpenStack Image Service. It is mainly used for installations that must support euca2ools. The euca2ools tools talk to <systemitem class=\"service\">nova-objectstore</systemitem> in <emphasis role=\"italic\">S3 language</emphasis>, and <systemitem class=\"service\">nova-objectstore</systemitem> translates S3 requests into Image service requests."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:154(term)
+msgid "euca2ools client"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:155(para)
+msgid "A set of command-line interpreter commands for managing cloud resources. Although it is not an OpenStack module, you can configure <systemitem class=\"service\">nova-api</systemitem> to support this EC2 interface. For more information, see the <link href=\"https://www.eucalyptus.com/docs/eucalyptus/3.4/index.html\">Eucalyptus 3.4 Documentation</link>."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:163(title)
+msgid "Command-line clients and other interfaces"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:164(term)
+msgid "nova client"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:165(para)
+msgid "Allows users to submit commands as a tenant administrator or end user."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:169(term)
+msgid "nova-manage client"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:170(para)
+msgid "Enables cloud administrators to submit commands."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:174(title)
+msgid "Other components"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:175(term)
+msgid "The queue"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:175(para)
+msgid "A central hub for passing messages between daemons. It is usually implemented with <link href=\"http://www.rabbitmq.com/\">RabbitMQ</link>, but could be any AMQP message queue, such as <link href=\"http://qpid.apache.org/\">Apache Qpid</link> or <link href=\"http://www.zeromq.org/\">Zero MQ</link>."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:183(term)
+msgid "SQL database"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:184(para)
+msgid "Stores most build-time and runtime states for a cloud infrastructure. It includes instance types that are available for use, instances in use, available networks, and projects. Theoretically, OpenStack Compute can support any database that is supported by SQL-Alchemy. Note the databases which are widely used are SQLite3 databases (for test and development work), MySQL, and PostgreSQL."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml:192(para)
+msgid "OpenStack Compute interacts with OpenStack Identity for authentication; OpenStack Image Service for images; and the OpenStack dashboard for a web interface."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_manage_images.xml:6(title)
+msgid "Create an image (nova)"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_manage_images.xml:7(para)
+msgid "You can use the <placeholder-1/> client to take a snapshot of a running instance to create an image."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_manage_images.xml:9(para)
+msgid "To minimize the potential for data loss and ensure that you create an accurate image, you should shut down the instance before you take a snapshot."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_manage_images.xml:12(para)
+msgid "You cannot create a snapshot from an instance that has an attached volume. Detach the volume, create the image, and remount the volume."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_manage_images.xml:18(para)
+msgid "For more information, see <link href=\"http://docs.openstack.org/trunk/openstack-ops/content/snapshots.html\">Taking Snapshots</link> in the <citetitle>OpenStack Operations Guide</citetitle>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_manage_images.xml:24(para)
+msgid "List instances to get the server name:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_manage_images.xml:31(para)
+msgid "In this example, the server is named <literal>myCirrosServer</literal>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_manage_images.xml:33(para)
+msgid "Use this server to create a snapshot: <placeholder-1/>The command creates a qemu snapshot and automatically uploads the image to your repository. Only the tenant that creates the image has access to it."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_manage_images.xml:81(para)
+msgid "To launch an instance from your image, include the image ID and flavor ID, as in the following example:"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml:6(title)
+msgid "Groups"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml:7(para)
+msgid "A group is a collection of users. Administrators can create groups and add users to them. Then, rather than assign a role to each user individually, assign a role to the group. Every group is in a domain. Groups were introduced with the Identity API v3."
+msgstr ""
+
+#. TODO: eventually remove the last sentence, when v3 is
+#.              commonplace
+#: ./doc/common/section_keystone-concepts-group-management.xml:14(para)
+msgid "Identity API V3 provides the following group-related operations:"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml:18(para)
+msgid "Create a group"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml:21(para)
+msgid "Delete a group"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml:24(para)
+msgid "Update a group (change its name or description)"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml:28(para)
+msgid "Add a user to a group"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml:31(para)
+msgid "Remove a user from a group"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml:34(para)
+msgid "List group members"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml:37(para)
+msgid "List groups for a user"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml:40(para)
+msgid "Assign a role on a tenant to a group"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml:43(para)
+msgid "Assign a role on a domain to a group"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml:46(para)
+msgid "Query role assignments to groups"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml:50(para)
+msgid "The Identity service server might not allow all operations. For example, if using the Identity server with the LDAP Identity back end and group updates are disabled, then a request to create, delete, or update a group fails."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml:56(para)
+msgid "Here are a couple of examples:"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml:59(para)
+msgid "Group A is granted Role A on Tenant A. If User A is a member of Group A, when User A gets a token scoped to Tenant A, the token also includes Role A."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml:65(para)
+msgid "Group B is granted Role B on Domain B. If User B is a member of Domain B, if User B gets a token scoped to Domain B, the token also includes Role B."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-assignments.xml:6(title)
+msgid "Separate role authorization and user authentication"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-assignments.xml:7(para)
+msgid "When you configure the Identity service to use an LDAP back end, you can split authentication and authorization using the <emphasis>Assignments</emphasis> feature."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-assignments.xml:10(para)
+msgid "The Assignments feature enables administrators to manage project role authorization using the Identity service's own SQL database, while still providing user authentication through the LDAP directory."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-assignments.xml:14(para)
+msgid "To configure this:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-assignments.xml:16(title)
+msgid "Separating role authorization and user authentication through Assignments"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-assignments.xml:19(para)
+msgid "Configure the Identity service to authenticate users through the LDAP driver. To do so, first find the <literal>[identity]</literal> section in the <filename>/etc/keystone/keystone.conf</filename> configuration file. Then, set the <literal>driver</literal> configuration key in that section to <literal>keystone.identity.backends.ldap.Identity</literal>:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-assignments.xml:30(para)
+msgid "Next, enable the Assignment driver. To do so, find the <literal>[assignment]</literal> section in the <filename>/etc/keystone/keystone.conf</filename> configuration file. Then, set the <literal>driver</literal> configuration key in that section to <literal>keystone.assignment.backends.sql.Assignment</literal>:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-assignments.xml:41(para)
+msgid "On distributions that include <application>openstack-config</application>, you can configure both drivers by running the following commands instead:"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:7(title)
+msgid "Install the OpenStack command-line clients"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:8(para)
+msgid "Install the prerequisite software and the Python package for each OpenStack client."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:11(title)
+msgid "Install the prerequisite software"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:13(para)
+msgid "Most Linux distributions include packaged versions of the command-line clients that you can install directly, see <xref linkend=\"cli_clients_install_packages\"/>."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:17(para)
+msgid "If you need to install the command-line packages source packages, the following table lists the software that you need to have to run the command-line clients, and provides installation instructions as needed."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:24(caption)
+msgid "Prerequisite software"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:29(th)
+msgid "Prerequisite"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:36(para)
+msgid "Python 2.6 or later"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:39(para)
+msgid "Currently, the clients do not support Python 3."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:45(para)
+msgid "<package>setuptools</package> package"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:48(para)
+msgid "Installed by default on Mac OS X."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:49(para)
+msgid "Many Linux distributions provide packages to make <package>setuptools</package> easy to install. Search your package manager for <package>setuptools</package> to find an installation package. If you cannot find one, download the <package>setuptools</package> package directly from <link href=\"http://pypi.python.org/pypi/setuptools\">http://pypi.python.org/pypi/setuptools</link>."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:57(para)
+msgid "The recommended way to install <package>setuptools</package> on Microsoft Windows is to follow the documentation provided <link href=\"https://pypi.python.org/pypi/setuptools#windows\">on the setuptools website</link>. Another option is to use the unofficial binary installer maintained by Christoph Gohlke (<link href=\"http://www.lfd.uci.edu/~gohlke/pythonlibs/#setuptools\">http://www.lfd.uci.edu/~gohlke/pythonlibs/#setuptools</link>)."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:70(package)
+msgid "pip"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:70(td)
+msgid "<placeholder-1/> package"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:72(para)
+msgid "To install the clients on a Linux, Mac OS X, or Microsoft Windows system, use <package>pip</package>. It is easy to use, ensures that you get the latest version of the clients from the <link href=\"http://pypi.python.org/\">Python Package Index</link>, and lets you update or remove the packages later on."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:81(para)
+msgid "Install <package>pip</package> through the package manager for your system:"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:84(title)
+msgid "MacOS"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:88(title)
+msgid "Microsoft Windows"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:89(para)
+msgid "Ensure that the <filename>C:\\Python27\\Scripts</filename> directory is defined in the <literal>PATH</literal> environment variable, and use the <placeholder-1/> command from the <package>setuptools</package> package: <placeholder-2/>Another option is to use the unofficial binary installer provided by Christoph Gohlke (<link href=\"http://www.lfd.uci.edu/~gohlke/pythonlibs/#pip\">http://www.lfd.uci.edu/~gohlke/pythonlibs/#pip</link>)."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:106(title)
+msgid "Ubuntu and Debian"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:112(title)
+msgid "Red Hat Enterprise Linux, CentOS, or Fedora"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:113(para)
+msgid "A packaged version enables you to use <package>yum</package> to install the package: <placeholder-1/> There are also packaged versions of the clients available in <link href=\"http://openstack.redhat.com/\">RDO</link> that enable <package>yum</package> to install the clients as described in <xref linkend=\"cli_clients_install_packages\"/>."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:125(title)
+msgid "SUSE Linux Enterprise Linux 11"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:126(para)
+msgid "A <link href=\"https://build.opensuse.org/package/show?package=python-pip&amp;project=Cloud:OpenStack:Master\">packaged version available in the Open Build Service</link> enables you to use or <package>zypper</package> to install the package. First, add the Open Build Service repository: <placeholder-1/> Then install <package>pip</package> and use it to manage client installation: <placeholder-2/> There are also packaged versions of the clients available that enable <package>zypper</package> to install the clients as described in <xref linkend=\"cli_clients_install_packages\"/>."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:141(title)
+msgid "openSUSE"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:142(para)
+msgid "You can install <package>pip</package> and use it to manage client installation: <placeholder-1/> There are also packaged versions of the clients available that enable <package>zypper</package> to install the clients as described in <xref linkend=\"cli_clients_install_packages\"/>"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:157(title)
+msgid "Install the clients"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:158(para)
+msgid "When following the instructions in this section, replace <replaceable>PROJECT</replaceable> with the lowercase name of the client to install, such as <placeholder-1/>. Repeat for each client. The following values are valid:"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:165(para)
+msgid "<literal>ceilometer</literal> - Telemetry API"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:169(para)
+msgid "<literal>cinder</literal> - Block Storage API and extensions"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:173(para)
+msgid "<literal>glance</literal> - Image Service API"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:177(para)
+msgid "<literal>heat</literal> - Orchestration API"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:181(para)
+msgid "<literal>keystone</literal> - Identity service API and extensions"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:185(para)
+msgid "<literal>neutron</literal> - Networking API"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:189(para)
+msgid "<literal>nova</literal> - Compute API and extensions"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:193(para)
+msgid "<literal>swift</literal> - Object Storage API"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:197(para)
+msgid "<literal>trove</literal> - Database Service API"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:201(para)
+msgid "The following example shows the command for installing the nova client with <replaceable>pip</replaceable>."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:206(title)
+msgid "Installing with pip"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:207(para)
+msgid "Use <package>pip</package> to install the OpenStack clients on a Linux, Mac OS X, or Microsoft Windows system. It is easy to use and ensures that you get the latest version of the client from the <link href=\"http://pypi.python.org/pypi\">Python Package Index</link>. Also, <package>pip</package> enables you to update or remove a package."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:214(para)
+msgid "Install each client separately by using the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:217(para)
+msgid "For Mac OS X or Linux:"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:218(replaceable) ./doc/common/section_cli_install.xml:220(replaceable) ./doc/common/section_cli_install.xml:232(replaceable) ./doc/common/section_cli_install.xml:236(replaceable) ./doc/common/section_cli_install.xml:243(replaceable) ./doc/common/section_cli_install.xml:252(replaceable) ./doc/common/section_cli_install.xml:255(replaceable) ./doc/common/section_cli_version.xml:9(replaceable)
+msgid "PROJECT"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:219(para)
+msgid "For Microsoft Windows:"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:224(title)
+msgid "Installing from packages"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:225(para)
+msgid "RDO, openSUSE and SUSE Linux Enterprise have client packages that can be installed without <filename>pip</filename>."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:227(para)
+msgid "On Red Hat Enterprise Linux, CentOS, or Fedora, use <placeholder-1/> to install the clients from the packaged versions available in <link href=\"http://openstack.redhat.com/\">RDO</link>: <placeholder-2/>"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:233(para)
+msgid "For openSUSE, use <package>zypper</package> to install the clients from the distribution packages Service: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:237(para)
+msgid "For SUSE Linux Enterprise Server, use <package>zypper</package> to install the clients from the distribution packages in the Open Build Service. First, add the Open Build Service repository: <placeholder-1/> Then you can install the packages: <placeholder-2/>"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:248(title)
+msgid "Upgrade or remove clients"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:249(para)
+msgid "To upgrade a client, add the <literal>--upgrade</literal> option to the <placeholder-1/> command:"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:253(para)
+msgid "To remove the a client, run the <placeholder-1/> command:"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:258(title)
+msgid "What's next"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml:259(para)
+msgid "Before you can run client commands, you must create and source the <filename><replaceable>PROJECT</replaceable>-openrc.sh</filename> file to set environment variables. See <xref linkend=\"cli_openrc\"/>."
+msgstr ""
+
+#: ./doc/common/section_cli_help.xml:6(title)
+msgid "Get help for client commands"
+msgstr ""
+
+#: ./doc/common/section_cli_help.xml:7(para)
+msgid "To get usage information, including a list of commands with descriptions, for a client, run the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_help.xml:9(replaceable) ./doc/common/section_cli_help.xml:59(replaceable)
+msgid "CLIENT_NAME"
+msgstr ""
+
+#: ./doc/common/section_cli_help.xml:10(para)
+msgid "For example, to get help information for the swift client, run the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_help.xml:54(para)
+msgid "Depending on your credentials, you might not have permission to use every command."
+msgstr ""
+
+#: ./doc/common/section_cli_help.xml:57(para)
+msgid "After the <option>help</option> command, you can enter a command name to get help for that command, as follows:"
+msgstr ""
+
+#: ./doc/common/section_cli_help.xml:59(replaceable)
+msgid "COMMAND_NAME"
+msgstr ""
+
+#: ./doc/common/section_cli_help.xml:60(para)
+msgid "For example, to get help for the glance <placeholder-1/> command, enter the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_help.xml:64(para)
+msgid "The command returns a description of the command and its positional and optional arguments:"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-intro.xml:8(para)
+msgid "OpenStack Object Storage (code-named swift) is open source software for creating redundant, scalable data storage using clusters of standardized servers to store petabytes of accessible data. It is a long-term storage system for large amounts of static data that can be retrieved, leveraged, and updated. Object Storage uses a distributed architecture with no central point of control, providing greater scalability, redundancy, and permanence. Objects are written to multiple hardware devices, with the OpenStack software responsible for ensuring data replication and integrity across the cluster. Storage clusters scale horizontally by adding new nodes. Should a node fail, OpenStack works to replicate its content from other active nodes. Because OpenStack uses software logic to ensure data replication and distribution across different devices, inexpensive commodity hard drives and servers can be used in lieu of more expensive equipment."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-intro.xml:19(para)
+msgid "Object Storage is ideal for cost effective, scale-out storage. It provides a fully distributed, API-accessible storage platform that can be integrated directly into applications or used for backup, archiving, and data retention."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:8(title)
+msgid "Configuration file format"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:10(para)
+msgid "OpenStack uses the <glossterm>INI</glossterm> file format for configuration files. An INI file is a simple text file that specifies options as <literal>key=value</literal> pairs, grouped into sections. The <literal>DEFAULT</literal> section contains most of the configuration options. Lines starting with a hash sign (<literal>#</literal>) are comment lines. For example:"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:29(replaceable)
+msgid "KEYSTONE_DBPASS"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:29(replaceable)
+msgid "controller"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:32(para)
+msgid "Options can have different type for values. The comments in the sample config files always mention these. The following types are used by OpenStack:"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:39(term)
+msgid "boolean value"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:41(para)
+msgid "Enables or disables an option. The allowed values are <literal>true</literal> and <literal>false</literal>."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:51(term)
+msgid "floating point value"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:53(para)
+msgid "A floating point number like <literal>0.25</literal> or <literal>1000</literal>."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:62(term)
+msgid "integer value"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:64(para)
+msgid "An integer number is a number without fractional components, like <literal>0</literal> or <literal>42</literal>."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:74(term)
+msgid "list value"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:76(para)
+msgid "Represents values of other types, separated by commas. As an example, the following sets <option>allowed_rpc_exception_modules</option> to a list containing the four elements <literal>oslo.messaging.exceptions</literal>, <literal>nova.exception</literal>, <literal>cinder.exception</literal>, and <literal>exceptions</literal>:"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:92(term)
+msgid "multi valued"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:94(para)
+msgid "A multi-valued option is a string value and can be given more than once, all values will be used."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:105(term)
+msgid "string value"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:107(para)
+msgid "Strings can be optionally enclosed with single or double quotes."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:127(title)
+msgid "Sections"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:134(literal) ./doc/common/tables/ceilometer-database.xml:19(th) ./doc/common/tables/neutron-openvswitch_agent.xml:19(th) ./doc/common/tables/heat-clients.xml:19(th) ./doc/common/tables/cinder-solidfire.xml:19(th) ./doc/common/tables/neutron-rpc.xml:19(th) ./doc/common/tables/nova-periodic.xml:19(th) ./doc/common/tables/keystone-policy.xml:19(th) ./doc/common/tables/glance-auth_token.xml:19(th) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:19(th) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:7(literal) ./doc/common/tables/ceilometer-redis.xml:19(th) ./doc/common/tables/cinder-storage_ceph.xml:19(th) ./doc/common/tables/nova-testing.xml:19(th) ./doc/common/tables/nova-metadata.xml:19(th) ./doc/common/tables/cinder-hp3par.xml:19(th) ./doc/common/tables/keystone-misc.xml:19(th) ./doc/common/tables/neutron-scheduler.xml:19(th) ./doc/common/tables/glance-rbd.xml:19(th) ./doc/common/tables/cinder-storage_xen.xml:19(th) ./doc/common/tables/ceilometer-common.xml:19(th) ./doc/common/tables/cinder-database.xml:19(th) ./doc/common/tables/ceilometer-logging.xml:19(th) ./doc/common/tables/heat-common.xml:19(th) ./doc/common/tables/nova-ipv6.xml:19(th) ./doc/common/tables/nova-vnc.xml:19(th) ./doc/common/tables/trove-qpid.xml:19(th) ./doc/common/tables/keystone-api.xml:19(th) ./doc/common/tables/glance-rpc.xml:19(th) ./doc/common/tables/neutron-policy.xml:19(th) ./doc/common/tables/nova-xen.xml:19(th) ./doc/common/tables/trove-amqp.xml:19(th) ./doc/common/tables/glance-matchmaker.xml:19(th) ./doc/common/tables/nova-rabbitmq.xml:19(th) ./doc/common/tables/nova-policy.xml:19(th) ./doc/common/tables/ceilometer-inspector.xml:19(th) ./doc/common/tables/cinder-scheduler.xml:19(th) ./doc/common/tables/neutron-logging.xml:19(th) ./doc/common/tables/nova-availabilityzones.xml:19(th) ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:19(th) ./doc/common/tables/neutron-rootwrap.xml:19(th) ./doc/common/tables/cinder-auth.xml:19(th) ./doc/common/tables/heat-qpid.xml:19(th) ./doc/common/tables/neutron-auth_token.xml:19(th) ./doc/common/tables/nova-ldap.xml:19(th) ./doc/common/tables/ceilometer-auth.xml:19(th) ./doc/common/tables/cinder-quota.xml:19(th) ./doc/common/tables/nova-compute.xml:19(th) ./doc/common/tables/keystone-rabbit.xml:19(th) ./doc/common/tables/cinder-backups_ceph.xml:19(th) ./doc/common/tables/heat-cfn_api.xml:19(th) ./doc/common/tables/neutron-vmware.xml:19(th) ./doc/common/tables/nova-zeromq.xml:19(th) ./doc/common/tables/cinder-storage.xml:19(th) ./doc/common/tables/glance-registry.xml:19(th) ./doc/common/tables/heat-quota.xml:19(th) ./doc/common/tables/nova-common.xml:19(th) ./doc/common/tables/nova-volumes.xml:19(th) ./doc/common/tables/neutron-redis.xml:19(th) ./doc/common/tables/heat-zeromq.xml:19(th) ./doc/common/tables/heat-amqp.xml:19(th) ./doc/common/tables/nova-redis.xml:19(th) ./doc/common/tables/swift-container-server-DEFAULT.xml:7(literal) ./doc/common/tables/nova-db.xml:19(th) ./doc/common/tables/glance-rabbitmq.xml:19(th) ./doc/common/tables/neutron-l3_agent.xml:19(th) ./doc/common/tables/glance-policy.xml:19(th) ./doc/common/tables/nova-neutron.xml:19(th) ./doc/common/tables/cinder-backups.xml:19(th) ./doc/common/tables/glance-vmware.xml:19(th) ./doc/common/tables/cinder-zoning.xml:19(th) ./doc/common/tables/heat-notification.xml:19(th) ./doc/common/tables/nova-vpn.xml:19(th) ./doc/common/tables/trove-common.xml:19(th) ./doc/common/tables/trove-api.xml:19(th) ./doc/common/tables/cinder-zadara.xml:19(th) ./doc/common/tables/nova-conductor.xml:19(th) ./doc/common/tables/nova-livemigration.xml:19(th) ./doc/common/tables/heat-rabbitmq.xml:19(th) ./doc/common/tables/keystone-amqp.xml:19(th) ./doc/common/tables/keystone-rpc.xml:19(th) ./doc/common/tables/swift-object-server-DEFAULT.xml:7(literal) ./doc/common/tables/cinder-zones.xml:19(th) ./doc/common/tables/cinder-scality.xml:19(th) ./doc/common/tables/neutron-agent.xml:19(th) ./doc/common/tables/cinder-emc.xml:19(th) ./doc/common/tables/cinder-vmware.xml:19(th) ./doc/common/tables/heat-metadata_api.xml:19(th) ./doc/common/tables/trove-rabbitmq.xml:19(th) ./doc/common/tables/neutron-kombu.xml:19(th) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:19(th) ./doc/common/tables/neutron-ml2_ofa.xml:19(th) ./doc/common/tables/glance-api.xml:19(th) ./doc/common/tables/heat-waitcondition_api.xml:19(th) ./doc/common/tables/cinder-storwize.xml:19(th) ./doc/common/tables/cinder-hplefthand.xml:19(th) ./doc/common/tables/glance-s3.xml:19(th) ./doc/common/tables/nova-rootwrap.xml:19(th) ./doc/common/tables/heat-loadbalancer.xml:19(th) ./doc/common/tables/ceilometer-api.xml:19(th) ./doc/common/tables/ceilometer-exchange.xml:19(th) ./doc/common/tables/cinder-lvm.xml:19(th) ./doc/common/tables/trove-dns.xml:19(th) ./doc/common/tables/trove-volume.xml:19(th) ./doc/common/tables/heat-auth_token.xml:19(th) ./doc/common/tables/neutron-quotas.xml:19(th) ./doc/common/tables/cinder-storage_nfs.xml:19(th) ./doc/common/tables/heat-api.xml:19(th) ./doc/common/tables/glance-logging.xml:19(th) ./doc/common/tables/neutron-metering_agent.xml:19(th) ./doc/common/tables/neutron-zeromq.xml:19(th) ./doc/common/tables/cinder-storage_glusterfs.xml:19(th) ./doc/common/tables/cinder-common.xml:19(th) ./doc/common/tables/glance-swift.xml:19(th) ./doc/common/tables/trove-quota.xml:19(th) ./doc/common/tables/cinder-auth_token.xml:19(th) ./doc/common/tables/cinder-xiv.xml:19(th) ./doc/common/tables/nova-glance.xml:19(th) ./doc/common/tables/keystone-auth_token.xml:19(th) ./doc/common/tables/nova-s3.xml:19(th) ./doc/common/tables/nova-pci.xml:19(th) ./doc/common/tables/cinder-api.xml:19(th) ./doc/common/tables/trove-heat.xml:19(th) ./doc/common/tables/glance-sheepdog.xml:19(th) ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml:7(literal) ./doc/common/tables/cinder-windows.xml:19(th) ./doc/common/tables/cinder-san-solaris.xml:19(th) ./doc/common/tables/keystone-zeromq.xml:19(th) ./doc/common/tables/ceilometer-rpc.xml:19(th) ./doc/common/tables/glance-filesystem.xml:19(th) ./doc/common/tables/trove-rpc.xml:19(th) ./doc/common/tables/ceilometer-swift.xml:19(th) ./doc/common/tables/trove-backup.xml:19(th) ./doc/common/tables/nova-network.xml:19(th) ./doc/common/tables/glance-redis.xml:19(th) ./doc/common/tables/nova-ca.xml:19(th) ./doc/common/tables/neutron-dhcp_agent.xml:19(th) ./doc/common/tables/ceilometer-collector.xml:19(th) ./doc/common/tables/cinder-hds-hus.xml:19(th) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:19(th) ./doc/common/tables/heat-debug.xml:19(th) ./doc/common/tables/nova-kombu.xml:19(th) ./doc/common/tables/trove-guestagent.xml:19(th) ./doc/common/tables/nova-qpid.xml:19(th) ./doc/common/tables/glance-qpid.xml:19(th) ./doc/common/tables/glance-amqp.xml:19(th) ./doc/common/tables/glance-zmq.xml:19(th) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:7(literal) ./doc/common/tables/neutron-testing.xml:19(th) ./doc/common/tables/trove-compute.xml:19(th) ./doc/common/tables/cinder-rpc.xml:19(th) ./doc/common/tables/cinder-hpmsa.xml:19(th) ./doc/common/tables/cinder-storage_gpfs.xml:19(th) ./doc/common/tables/keystone-notification.xml:19(th) ./doc/common/tables/trove-zeromq.xml:19(th) ./doc/common/tables/neutron-lbaas.xml:19(th) ./doc/common/tables/cinder-backups_swift.xml:19(th) ./doc/common/tables/trove-database.xml:19(th) ./doc/common/tables/nova-authentication.xml:19(th) ./doc/common/tables/glance-gridfs.xml:19(th) ./doc/common/tables/neutron-notifier.xml:19(th) ./doc/common/tables/nova-rpc_all.xml:19(th) ./doc/common/tables/nova-scheduling.xml:19(th) ./doc/common/tables/cinder-eqlx.xml:19(th) ./doc/common/tables/heat-redis.xml:19(th) ./doc/common/tables/nova-ec2.xml:19(th) ./doc/common/tables/cinder-block-device.xml:19(th) ./doc/common/tables/neutron-metadata.xml:19(th) ./doc/common/tables/nova-fping.xml:19(th) ./doc/common/tables/neutron-compute.xml:19(th) ./doc/common/tables/glance-imagecache.xml:19(th) ./doc/common/tables/cinder-nas.xml:19(th) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:19(th) ./doc/common/tables/keystone-logging.xml:19(th) ./doc/common/tables/heat-rpc.xml:19(th) ./doc/common/tables/trove-taskmanager.xml:19(th) ./doc/common/tables/heat-cloudwatch_api.xml:19(th) ./doc/common/tables/cinder-images.xml:19(th) ./doc/common/tables/cinder-huawei.xml:19(th) ./doc/common/tables/nova-console.xml:19(th) ./doc/common/tables/cinder-nexenta_nfs.xml:19(th) ./doc/common/tables/nova-quota.xml:19(th) ./doc/common/tables/heat-logging.xml:19(th) ./doc/common/tables/heat-crypt.xml:19(th) ./doc/common/tables/neutron-ssl.xml:19(th) ./doc/common/tables/cinder-coraid.xml:19(th) ./doc/common/tables/neutron-wsgi.xml:19(th) ./doc/common/tables/cinder-compute.xml:19(th) ./doc/common/tables/glance-wsgi.xml:19(th) ./doc/common/tables/neutron-qpid.xml:19(th) ./doc/common/tables/nova-rpc.xml:19(th) ./doc/common/tables/cinder-backups_tsm.xml:19(th) ./doc/common/tables/cinder-san.xml:19(th) ./doc/common/tables/nova-logging.xml:19(th) ./doc/common/tables/keystone-security.xml:19(th) ./doc/common/tables/nova-api.xml:19(th) ./doc/common/tables/trove-auth_token.xml:19(th) ./doc/common/tables/glance-cinder.xml:19(th) ./doc/common/tables/glance-common.xml:19(th) ./doc/common/tables/swift-account-server-DEFAULT.xml:7(literal) ./doc/common/tables/trove-nova.xml:19(th) ./doc/common/tables/neutron-rabbitmq.xml:19(th) ./doc/common/tables/keystone-ec2.xml:19(th) ./doc/common/tables/neutron-api.xml:19(th) ./doc/common/tables/trove-logging.xml:19(th) ./doc/common/tables/keystone-redis.xml:19(th) ./doc/common/tables/nova-xvpnvncproxy.xml:19(th) ./doc/common/tables/heat-clients_backends.xml:19(th) ./doc/common/tables/glance-testing.xml:19(th) ./doc/common/tables/neutron-common.xml:19(th) ./doc/common/tables/nova-hypervisor.xml:19(th) ./doc/common/tables/keystone-qpid.xml:19(th) ./doc/common/tables/nova-wsgi.xml:19(th) ./doc/common/tables/nova-configdrive.xml:19(th) ./doc/common/tables/ceilometer-qpid.xml:19(th) ./doc/common/tables/heat-database.xml:19(th) ./doc/common/tables/ceilometer-rabbitmq.xml:19(th) ./doc/common/tables/neutron-db.xml:19(th) ./doc/common/tables/trove-debug.xml:19(th) ./doc/common/tables/trove-swift.xml:19(th) ./doc/common/tables/nova-libvirt.xml:19(th) ./doc/common/tables/ceilometer-amqp.xml:19(th) ./doc/common/tables/glance-ssl.xml:19(th) ./doc/common/tables/keystone-debug.xml:19(th) ./doc/common/tables/cinder-rootwrap.xml:19(th) ./doc/common/tables/cinder-nexenta_iscsi.xml:19(th)
+msgid "[DEFAULT]"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:136(para)
+msgid "Contains most configuration options. If the documentation for a configuration option does not specify its section, assume that it appears in this section."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:145(literal) ./doc/common/tables/ceilometer-database.xml:38(th) ./doc/common/tables/cinder-storage.xml:134(th) ./doc/common/tables/nova-db.xml:33(th) ./doc/common/tables/cinder-common.xml:226(th) ./doc/common/tables/cinder-connection.xml:19(th) ./doc/common/tables/glance-db.xml:19(th) ./doc/common/tables/heat-database.xml:34(th) ./doc/common/tables/neutron-db.xml:30(th) ./doc/common/tables/keystone-database.xml:19(th)
+msgid "[database]"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:147(para)
+msgid "Configuration options for the database that stores the state of the OpenStack service."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:128(para)
+msgid "Configuration options are grouped by section. Most configuration file supports at least the following sections: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:158(title)
+msgid "Substitution"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:160(para)
+msgid "The configuration file supports variable substitution. After you set a configuration option, it can be referenced in later configuration values when you precede it with a <literal>$</literal>, like <literal>$OPTION</literal>."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:167(para)
+msgid "The following example uses the values of <literal>rabbit_host</literal> and <literal>rabbit_port</literal> to define the value of the <literal>rabbit_hosts</literal> option, in this case as <literal>controller:5672</literal>."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:185(para)
+msgid "To avoid substitution, use <literal>$$</literal>, it is replaced by a single <literal>$</literal>. For example, if your LDAP DNS password is <literal>$xkj432</literal>, specify it, as follows: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:191(para)
+msgid "The code uses the Python <literal>string.Template.safe_substitute()</literal> method to implement variable substitution. For more details on how variable substitution is resolved, see <link href=\"http://docs.python.org/2/library/string.html#template-strings\">http://docs.python.org/2/library/string.html#template-strings</link> and <link href=\"http://www.python.org/dev/peps/pep-0292/\">PEP 292</link>."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:204(title)
+msgid "Whitespace"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:205(para)
+msgid "To include whitespace in a configuration value, use a quoted string. For example:"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:211(title)
+msgid "Define an alternate location for a config file"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml:212(para)
+msgid "Most services and the and the <placeholder-1/> command-line clients load the configuration file. To define an alternate location for the configuration file, pass the <parameter>--config-file <replaceable>CONFIG_FILE</replaceable></parameter> parameter when you start a service or call a <placeholder-2/> command."
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml:5(title)
+msgid "OpenStack Image Service"
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml:6(para)
+msgid "The OpenStack Image Service is central to infrastructure-as-a-service (IaaS) as shown in <xref linkend=\"conceptual-architecture\"/>. It accepts API requests for disk or server images, and image metadata from end users or OpenStack Compute components. It also supports the storage of disk or server images on various repository types, including OpenStack Object Storage."
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml:12(para)
+msgid "A number of periodic processes run on the OpenStack Image Service to support caching. Replication services ensures consistency and availability through the cluster. Other periodic processes include auditors, updaters, and reapers."
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml:16(para)
+msgid "The OpenStack Image Service includes the following components:"
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml:20(systemitem)
+msgid "glance-api"
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml:21(para)
+msgid "Accepts Image API calls for image discovery, retrieval, and storage."
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml:25(systemitem)
+msgid "glance-registry"
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml:26(para)
+msgid "Stores, processes, and retrieves metadata about images. Metadata includes items such as size and type."
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml:28(title)
+msgid "Security note"
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml:29(para)
+msgid "The registry is a private internal service meant for use by OpenStack Image Service. Do not disclose it to users."
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml:35(term)
+msgid "Database"
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml:36(para)
+msgid "Stores image metadata and you can choose your database depending on your preference. Most deployments use MySQL or SQlite."
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml:41(term)
+msgid "Storage repository for image files"
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml:42(para)
+msgid "Various repository types are supported including normal file systems, Object Storage, RADOS block devices, HTTP, and Amazon S3. Note that some repositories will only support read-only usage."
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:6(title)
+msgid "Get started with OpenStack"
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:7(para)
+msgid "The OpenStack project is an open source cloud computing platform for all types of clouds, which aims to be simple to implement, massively scalable, and feature rich. Developers and cloud computing technologists from around the world create the OpenStack project."
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:12(para)
+msgid "OpenStack provides an Infrastructure-as-a-Service (<glossterm>IaaS</glossterm>) solution through a set of interrelated services. Each service offers an application programming interface (<glossterm>API</glossterm>) that facilitates this integration. Depending on your needs, you can install some or all services."
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:20(para)
+msgid "The following table describes the OpenStack services that make up the OpenStack architecture:"
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:23(caption) ./doc/common/ch_getstart.xml:188(title)
+msgid "OpenStack services"
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:30(th)
+msgid "Project name"
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:38(glossterm)
+msgid "Dashboard"
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:42(glossterm)
+msgid "Horizon"
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:44(td)
+msgid "Provides a web-based self-service portal to interact with underlying OpenStack services, such as launching an instance, assigning IP addresses and configuring access controls."
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:56(glossterm)
+msgid "Nova"
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:58(td)
+msgid "Manages the lifecycle of compute instances in an OpenStack environment. Responsibilities include spawning, scheduling and decommissioning of virtual machines on demand."
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:70(glossterm)
+msgid "Neutron"
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:72(td)
+msgid "Enables network connectivity as a service for other OpenStack services, such as OpenStack Compute. Provides an API for users to define networks and the attachments into them. Has a pluggable architecture that supports many popular networking vendors and technologies."
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:79(th)
+msgid "Storage"
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:87(glossterm)
+msgid "Swift"
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:90(glossterm)
+msgid "RESTful"
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:89(td)
+msgid "Stores and retrieves arbitrary unstructured data objects via a <placeholder-1/>, HTTP based API. It is highly fault tolerant with its data replication and scale out architecture. Its implementation is not like a file server with mountable directories."
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:103(glossterm)
+msgid "Cinder"
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:105(td)
+msgid "Provides persistent block storage to running instances. Its pluggable driver architecture facilitates the creation and management of block storage devices."
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:110(th)
+msgid "Shared services"
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:114(glossterm)
+msgid "Identity service"
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:118(glossterm)
+msgid "Keystone"
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:120(td)
+msgid "Provides an authentication and authorization service for other OpenStack services. Provides a catalog of endpoints for all OpenStack services."
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:131(glossterm)
+msgid "Glance"
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:133(td)
+msgid "Stores and retrieves virtual machine disk images. OpenStack Compute makes use of this during instance provisioning."
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:146(glossterm)
+msgid "Ceilometer"
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:148(td)
+msgid "Monitors and meters the OpenStack cloud for billing, benchmarking, scalability, and statistical purposes."
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:153(th)
+msgid "Higher-level services"
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:160(glossterm)
+msgid "Heat"
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:164(glossterm)
+msgid "HOT"
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:162(td)
+msgid "Orchestrates multiple composite cloud applications by using either the native <placeholder-1/> template format or the AWS CloudFormation template format, through both an OpenStack-native REST API and a CloudFormation-compatible Query API."
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:176(glossterm)
+msgid "Trove"
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:178(td)
+msgid "Provides scalable and reliable Cloud Database-as-a-Service functionality for both relational and non-relational database engines."
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:189(para)
+msgid "This section describes OpenStack services in detail."
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml:207(title)
+msgid "Feedback"
+msgstr ""
+
+#: ./doc/common/section_fibrechannel.xml:5(title)
+msgid "Fibre Channel support in Compute"
+msgstr ""
+
+#: ./doc/common/section_fibrechannel.xml:6(para)
+msgid "Fibre Channel support in OpenStack Compute is remote block storage attached to compute nodes for VMs."
+msgstr ""
+
+#. TODO: This below statement needs to be verified for current release
+#: ./doc/common/section_fibrechannel.xml:9(para)
+msgid "In the Grizzly release, Fibre Channel supported only the KVM hypervisor."
+msgstr ""
+
+#: ./doc/common/section_fibrechannel.xml:11(para)
+msgid "Compute and Block Storage for Fibre Channel do not support automatic zoning. Fibre Channel arrays must be pre-zoned or directly attached to the KVM hosts."
+msgstr ""
+
+#: ./doc/common/section_fibrechannel.xml:15(title)
+msgid "KVM host requirements"
+msgstr ""
+
+#: ./doc/common/section_fibrechannel.xml:16(para)
+msgid "You must install these packages on the KVM host:"
+msgstr ""
+
+#: ./doc/common/section_fibrechannel.xml:19(para)
+msgid "<package>sysfsutils</package> - Nova uses the <package>systool</package> application in this package."
+msgstr ""
+
+#: ./doc/common/section_fibrechannel.xml:25(para)
+msgid "<package>sg3-utils</package> - Nova uses the <package>sg_scan</package> and <package>sginfo</package> applications."
+msgstr ""
+
+#: ./doc/common/section_fibrechannel.xml:31(para)
+msgid "Installing the <package>multipath-tools</package> package is optional."
+msgstr ""
+
+#: ./doc/common/section_fibrechannel.xml:35(title)
+msgid "Install required packages"
+msgstr ""
+
+#: ./doc/common/section_fibrechannel.xml:36(para)
+msgid "Use these commands to install the system packages:"
+msgstr ""
+
+#: ./doc/common/section_fibrechannel.xml:40(para)
+msgid "For systems running openSUSE or SUSE Linux Enterprise Server:"
+msgstr ""
+
+#: ./doc/common/section_fibrechannel.xml:45(para)
+msgid "For systems running Red Hat:"
+msgstr ""
+
+#: ./doc/common/section_fibrechannel.xml:49(para)
+msgid "For systems running Ubuntu:"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:7(title)
+msgid "Create and manage services and service users"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:8(para)
+msgid "The Identity Service enables you to define services, as follows:"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:12(para)
+msgid "Service catalog template. The Identity Service acts as a service catalog of endpoints for other OpenStack services. The <literal>etc/default_catalog.templates</literal> template file defines the endpoints for services. When the Identity Service uses a template file back end, any changes that are made to the endpoints are cached. These changes do not persist when you restart the service or reboot the machine."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:23(para)
+msgid "A SQL back end for the catalog service. When the Identity Service is online, you must add the services to the catalog. When you deploy a system for production, use the SQL back end."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:29(para)
+msgid "The <literal>auth_token</literal> middleware supports the use of either a shared secret or users for each service."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:32(para)
+msgid "To authenticate users against the Identity Service, you must create a service user for each OpenStack service. For example, create a service user for the Compute, Block Storage, and Networking services."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:36(para)
+msgid "To configure the OpenStack services with service users, create a project for all services and create users for each service. Assign the admin role to each service user and project pair. This role enables users to validate tokens and authenticate and authorize other user requests."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:42(title)
+msgid "Create a service"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:45(para)
+msgid "List the available services:"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:59(para)
+msgid "To create a service, run this command:"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:60(replaceable)
+msgid "service_name"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:60(replaceable)
+msgid "service_type"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:60(replaceable)
+msgid "service_description"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:61(para)
+msgid "The arguments are:"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:64(para)
+msgid "<code><replaceable>service_name</replaceable></code>. The unique name of the new service."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:68(para)
+msgid "<code><replaceable>service_type</replaceable></code>. The service type, such as <code>identity</code>, <code>compute</code>, <code>network</code>, <code>image</code>, <code>object-store</code> or any other service identifier string."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:78(para)
+msgid "<code><replaceable>service_description</replaceable></code>. The description of the service."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:82(para)
+msgid "For example, to create a <literal>swift</literal> service of type <literal>object-store</literal>, run this command:"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:97(para)
+msgid "To get details for a service, run this command:"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:99(replaceable)
+msgid "service_ID"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:114(title)
+msgid "Create service users"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:117(para)
+msgid "Create a project for the service users. Typically, this project is named <literal>service</literal>, but choose any name you like:"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:122(para)
+msgid "The output shows the ID for the project."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:123(para)
+msgid "Make a note of this ID. You need it to create service users and assign roles."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:135(para)
+msgid "Create service users for the relevant services for your deployment."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:139(para)
+msgid "To assign the admin role to the service user-project pairs, run this command to get the ID of the admin role:"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:155(para)
+msgid "Assign the admin role to the user-project pair:"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:157(replaceable)
+msgid "SERVICE_USER_ID"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:157(replaceable)
+msgid "ADMIN_ROLE_ID"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:157(replaceable)
+msgid "SERVICE_PROJECT_ID"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:162(title)
+msgid "Delete a service"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:163(para)
+msgid "To delete a specified service, specify its ID:"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml:164(replaceable)
+msgid "SERVICE_ID"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-domain-management.xml:6(title)
+msgid "Domains"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-domain-management.xml:7(para)
+msgid "A domain defines administrative boundaries for the management of Identity entities. A domain may represent an individual, company, or operator-owned space. It is used for exposing administrative activities directly to the system users."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-domain-management.xml:10(para)
+msgid "A domain is a collection of tenants, users, and roles. Users may be given a domain's administrator role. A domain administrator may create tenants, users, and groups within a domain and assign roles to users and groups."
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml:6(title)
+msgid "Customize the dashboard"
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml:7(para)
+msgid "Adapted from <link href=\"http://www.prestonlee.com/2012/05/09/how-to-custom-brand-the-openstack-horizon-dashboard/\">How To Custom Brand The OpenStack “Horizon” Dashboard</link>."
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml:11(para)
+msgid "You install the OpenStack dashboard through the <literal>openstack-dashboard</literal> package. You can customize the dashboard with your own colors, logo, and site title through a CSS file."
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml:15(para)
+msgid "Canonical also provides an <literal>openstack-dashboard-ubuntu-theme</literal> package that brands the Python-based Django interface."
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml:47(para)
+msgid "Create a graphical logo with a transparent background. The text <literal>TGen Cloud</literal> in this example is rendered through <filename>.png</filename> files of multiple sizes created with a graphics program."
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml:52(para)
+msgid "Use a 200×27 for the logged-in banner graphic, and 365×50 for the login screen graphic."
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml:56(para)
+msgid "Set the HTML title, which appears at the top of the browser window, by adding the following line to <filename>/etc/openstack-dashboard/local_settings.py</filename>:"
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml:59(code)
+msgid "SITE_BRANDING = \"Example, Inc. Cloud\""
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml:63(para)
+msgid "Upload your new graphic files to the following location: <filename>/usr/share/openstack-dashboard/openstack_dashboard/static/dashboard/img/</filename>"
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml:68(para)
+msgid "Create a CSS style sheet in the following directory: <filename>/usr/share/openstack-dashboard/openstack_dashboard/static/dashboard/css/</filename>"
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml:72(para)
+msgid "Edit your CSS file to override the Ubuntu customizations in the <filename>ubuntu.css</filename> file."
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml:75(para)
+msgid "Change the colors and image file names as appropriate, though the relative directory paths should be the same. The following example file shows you how to customize your CSS file:"
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml:114(para)
+msgid "Open the following HTML template in an editor: <filename>/usr/share/openstack-dashboard/openstack_dashboard/templates/_stylesheets.html</filename>"
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml:118(para)
+msgid "Add a line to include your <filename>custom.css</filename> file:"
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml:123(emphasis)
+msgid "&lt;link href='{{ STATIC_URL }}dashboard/css/custom.css' media='screen' rel='stylesheet' /&gt;"
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml:127(title)
+msgid "Restart Apache:"
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml:128(para) ./doc/common/section_dashboard_sessions.xml:180(para)
+msgid "On Ubuntu: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml:131(para)
+msgid "On Fedora, RHEL, CentOS: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml:134(para) ./doc/common/section_dashboard_sessions.xml:187(para)
+msgid "On openSUSE: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml:139(para)
+msgid "Reload the dashboard in your browser to view your changes."
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml:141(para)
+msgid "Modify your CSS file as appropriate."
 msgstr ""
 
 #: ./doc/common/section_compute_config-api.xml:6(title)
@@ -17485,158 +16749,902 @@ msgstr ""
 msgid "The Compute API configuration options are documented in <xref linkend=\"config_table_nova_api\"/>."
 msgstr ""
 
-#: ./doc/common/section_getstart_block-storage.xml:5(title)
-msgid "OpenStack Block Storage"
+#: ./doc/common/section_cli_nova_fileinjection.xml:10(title)
+msgid "Inject files into instances"
 msgstr ""
 
-#: ./doc/common/section_getstart_block-storage.xml:6(para)
-msgid "OpenStack Block Storage enables management of volumes, volume snapshots, and volume types. It consists of the following components:"
+#: ./doc/common/section_cli_nova_fileinjection.xml:11(para)
+msgid "You can inject local files into the instance file system when you launch an instance."
 msgstr ""
 
-#: ./doc/common/section_getstart_block-storage.xml:11(systemitem)
-msgid "cinder-api"
+#: ./doc/common/section_cli_nova_fileinjection.xml:13(para)
+msgid "Use the <parameter>--file dst-path=src-path</parameter> parameter on the nova <placeholder-1/> command."
 msgstr ""
 
-#: ./doc/common/section_getstart_block-storage.xml:12(para)
-msgid "Accepts API requests and routes them to <systemitem class=\"service\">cinder-volume</systemitem> for action."
+#: ./doc/common/section_cli_nova_fileinjection.xml:15(para)
+msgid "You can inject up to five files."
 msgstr ""
 
-#: ./doc/common/section_getstart_block-storage.xml:17(systemitem)
-msgid "cinder-volume"
+#: ./doc/common/section_cli_nova_fileinjection.xml:16(para)
+msgid "For example, you might inject the <filename>special_authorized_keysfile</filename> file into the instance rather than using the regular ssh key injection."
 msgstr ""
 
-#: ./doc/common/section_getstart_block-storage.xml:18(para)
-msgid "Responds to requests to read from and write to the OpenStack Block Storage database to maintain state, interacting with other processes (like <systemitem class=\"service\">cinder-scheduler</systemitem>) through a message queue and directly upon block storage providing hardware or software. It can interact with a variety of storage providers through a driver architecture."
+#: ./doc/common/section_cli_nova_fileinjection.xml:19(para)
+msgid "Run the following command:<placeholder-1/>"
 msgstr ""
 
-#: ./doc/common/section_getstart_block-storage.xml:28(term)
-msgid "<systemitem class=\"service\">cinder-scheduler</systemitem> daemon"
+#: ./doc/common/ch_preface.xml:7(title)
+msgid "Preface"
 msgstr ""
 
-#: ./doc/common/section_getstart_block-storage.xml:30(para)
-msgid "Like the <systemitem class=\"service\">nova-scheduler</systemitem>, picks the optimal block storage provider node on which to create the volume."
+#: ./doc/common/section_cli_nova_resizerebuild.xml:6(title)
+msgid "Change the size of your server"
 msgstr ""
 
-#: ./doc/common/section_getstart_block-storage.xml:36(para)
-msgid "Routes information between the Block Storage processes."
+#: ./doc/common/section_cli_nova_resizerebuild.xml:7(para)
+msgid "You change the size of a server by changing its flavor."
 msgstr ""
 
-#: ./doc/common/section_getstart_block-storage.xml:40(para)
-msgid "OpenStack Block Storage interacts with OpenStack Compute to provide volumes for instances."
+#: ./doc/common/section_cli_nova_resizerebuild.xml:10(para)
+msgid "Show information about your server, including its size, which is shown as the value of the flavor property."
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml:5(title)
-msgid "OpenStack Image Service"
+#: ./doc/common/section_cli_nova_resizerebuild.xml:43(para)
+msgid "The size (flavor) of the server is <literal>m1.small (2)</literal>."
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml:6(para)
-msgid "The OpenStack Image Service is central to infrastructure-as-a-service (IaaS) as shown in <xref linkend=\"conceptual-architecture\"/>. It accepts API requests for disk or server images, and image metadata from end users or OpenStack Compute components. It also supports the storage of disk or server images on various repository types, including OpenStack Object Storage."
+#: ./doc/common/section_cli_nova_resizerebuild.xml:46(para)
+msgid "List the available flavors with the following command:"
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml:12(para)
-msgid "A number of periodic processes run on the OpenStack Image Service to support caching. Replication services ensures consistency and availability through the cluster. Other periodic processes include auditors, updaters, and reapers."
+#: ./doc/common/section_cli_nova_resizerebuild.xml:59(para)
+msgid "To resize the server, pass the server ID or name and the new flavor to the <placeholder-1/> command. Include the <literal>--poll</literal> parameter to report the resize progress."
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml:16(para)
-msgid "The OpenStack Image Service includes the following components:"
+#: ./doc/common/section_cli_nova_resizerebuild.xml:67(para)
+msgid "Show the status for your server:"
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml:20(systemitem)
-msgid "glance-api"
+#: ./doc/common/section_cli_nova_resizerebuild.xml:74(para)
+msgid "When the resize completes, the status becomes VERIFY_RESIZE."
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml:21(para)
-msgid "Accepts Image API calls for image discovery, retrieval, and storage."
+#: ./doc/common/section_cli_nova_resizerebuild.xml:77(para)
+msgid "Confirm the resize:"
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml:25(systemitem)
-msgid "glance-registry"
+#: ./doc/common/section_cli_nova_resizerebuild.xml:79(para) ./doc/common/section_cli_nova_resizerebuild.xml:85(para)
+msgid "The server status becomes ACTIVE."
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml:26(para)
-msgid "Stores, processes, and retrieves metadata about images. Metadata includes items such as size and type."
+#: ./doc/common/section_cli_nova_resizerebuild.xml:82(para)
+msgid "If the resize fails or does not work as expected, you can revert the resize:"
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml:28(title)
-msgid "Security note"
+#: ./doc/common/section_dashboard-configure.xml:6(title)
+msgid "Configure the dashboard"
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml:29(para)
-msgid "The registry is a private internal service meant for use by OpenStack Image Service. Do not disclose it to users."
+#: ./doc/common/section_dashboard-configure.xml:8(para)
+msgid "You can configure the dashboard for a simple HTTP deployment."
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml:35(term)
-msgid "Database"
+#: ./doc/common/section_dashboard-configure.xml:14(para)
+msgid "Also, you can configure the size of the VNC window in the dashboard."
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml:36(para)
-msgid "Stores image metadata and you can choose your database depending on your preference. Most deployments use MySQL or SQlite."
+#: ./doc/common/section_storage-concepts.xml:10(title)
+msgid "Storage concepts"
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml:41(term)
-msgid "Storage repository for image files"
+#: ./doc/common/section_storage-concepts.xml:11(para)
+msgid "The OpenStack stack uses the following storage types:"
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml:42(para)
-msgid "Various repository types are supported including normal file systems, Object Storage, RADOS block devices, HTTP, and Amazon S3. Note that some repositories will only support read-only usage."
+#: ./doc/common/section_storage-concepts.xml:13(caption)
+msgid "Storage types"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml:19(td)
+msgid "On-instance / ephemeral"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml:20(td)
+msgid "Block storage (cinder)"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml:26(td)
+msgid "Runs operating systems and provides scratch space"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml:27(td)
+msgid "Used for adding additional persistent storage to a virtual machine (VM)"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml:29(td)
+msgid "Used for storing virtual machine images and data"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml:32(td)
+msgid "Persists until VM is terminated"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml:33(td) ./doc/common/section_storage-concepts.xml:34(td)
+msgid "Persists until deleted"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml:37(td) ./doc/common/section_storage-concepts.xml:38(td)
+msgid "Access associated with a VM"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml:39(td)
+msgid "Available from anywhere"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml:42(td)
+msgid "Implemented as a filesystem underlying OpenStack Compute"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml:44(td)
+msgid "Mounted via OpenStack Block Storage controlled protocol (for example, iSCSI)"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml:46(td)
+msgid "REST API"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml:49(td)
+msgid "Administrator configures size setting, based on flavors"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml:51(td)
+msgid "Sizings based on need"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml:52(td)
+msgid "Easily scalable for future growth"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml:55(td)
+msgid "Example: 10GB first disk, 30GB/core second disk"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml:56(td)
+msgid "Example: 1TB \"extra hard drive\""
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml:57(td)
+msgid "Example: 10s of TBs of data set storage"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml:64(para)
+msgid "<emphasis>You cannot use OpenStack Object Storage like a traditional hard drive.</emphasis> The Object Storage relaxes some of the constraints of a POSIX-style file system to get other gains. You can access the objects through an API which uses HTTP. Subsequently you don't have to provide atomic operations (that is, relying on eventual consistency), you can scale a storage system easily and avoid a central point of failure."
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml:73(para)
+msgid "<emphasis>The OpenStack Image Service is used to manage the virtual machine images in an OpenStack cluster, not store them.</emphasis> It provides an abstraction to different methods for storage - a bridge to the storage, not the storage itself."
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml:80(para)
+msgid "<emphasis>The OpenStack Object Storage can function on its own.</emphasis> The Object Storage (swift) product can be used independently of the Compute (nova) product."
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml:62(para)
+msgid "You should note that:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_rpc-for-networking.xml:9(para)
+msgid "OpenStack projects use an open standard for messaging middleware known as AMQP. This messaging middleware enables the OpenStack services that run on multiple servers to talk to each other. OpenStack Oslo RPC supports three implementations of AMQP: <application>RabbitMQ</application>, <application>Qpid</application>, and <application>ZeroMQ</application>."
+msgstr ""
+
+#: ./doc/common/section_rpc-for-networking.xml:20(para)
+msgid "OpenStack Oslo RPC uses <application>RabbitMQ</application> by default. Use these options to configure the <application>RabbitMQ</application> message system. The <option>rpc_backend</option> option is optional as long as <application>RabbitMQ</application> is the default messaging system. However, if it is included the configuration, you must set it to <literal>neutron.openstack.common.rpc.impl_kombu</literal>."
+msgstr ""
+
+#: ./doc/common/section_rpc-for-networking.xml:34(para)
+msgid "Use these options to configure the <application>RabbitMQ</application> messaging system. You can configure messaging communication for different installation scenarios, tune retries for RabbitMQ, and define the size of the RPC thread pool. To monitor notifications through RabbitMQ, you must set the <option>notification_driver</option> option to <literal>neutron.notifier.rabbit_notifier</literal> in the <filename>neutron.conf</filename> file:"
+msgstr ""
+
+#: ./doc/common/section_rpc-for-networking.xml:47(para)
+msgid "Use these options to configure the <application>Qpid</application> messaging system for OpenStack Oslo RPC. <application>Qpid</application> is not the default messaging system, so you must enable it by setting the <option>rpc_backend</option> option in the <filename>neutron.conf</filename> file:"
+msgstr ""
+
+#: ./doc/common/section_rpc-for-networking.xml:56(para)
+msgid "This critical option points the compute nodes to the <application>Qpid</application> broker (server). Set the <option>qpid_hostname</option> option to the host name where the broker runs in the <filename>neutron.conf</filename> file."
+msgstr ""
+
+#: ./doc/common/section_rpc-for-networking.xml:94(para)
+msgid "Use these additional options to configure the Qpid messaging driver for OpenStack Oslo RPC. These options are used infrequently."
+msgstr ""
+
+#: ./doc/common/section_rpc-for-networking.xml:103(para)
+msgid "Use these options to configure the <application>ZeroMQ</application> messaging system for OpenStack Oslo RPC. <application>ZeroMQ</application> is not the default messaging system, so you must enable it by setting the <option>rpc_backend</option> option in the <filename>neutron.conf</filename> file:"
+msgstr ""
+
+#: ./doc/common/section_rpc-for-networking.xml:114(para)
+msgid "Use these common options to configure the <application>RabbitMQ</application>, <application>Qpid</application>, and <application>ZeroMq</application> messaging drivers:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:6(title)
+msgid "Add security group and rules"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:7(para)
+msgid "The following procedure shows you how to add security groups and add rules to the default security group."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:10(title)
+msgid "Add or delete a security group"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:11(para)
+msgid "Use the <placeholder-1/> command to add security groups."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:13(para)
+msgid "The following example shows how to create the <literal>secure1</literal> security group:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:21(para)
+msgid "After you create the security group, you can view it in the security group list:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:30(para)
+msgid "Use the <placeholder-1/> command to delete security groups. You cannot delete the default security group. The default security group has these initial settings:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:36(para)
+msgid "All the traffic originated by the instances (outbound traffic) is allowed"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:40(para)
+msgid "All the traffic destined to instances (inbound traffic) is denied"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:44(para)
+msgid "All the instances inside the group are allowed to talk to each other"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:49(para)
+msgid "You can add extra rules into the default security group for handling the egress traffic. Rules are ingress only at this time."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:53(para)
+msgid "The following example deletes the <literal>secure1</literal> group. When you view the security group list, it no longer appears:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:65(title)
+msgid "Modify security group rules"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:69(para)
+msgid "You cannot change the default outbound behavior."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:66(para)
+msgid "The security group rules control the incoming traffic that can access the instances in the group, while all outbound traffic is automatically allowed. <placeholder-1/>Every security group rule is a policy that allows you to specify inbound connections that can access the instance by source address, destination port, and IP protocol (TCP, UDP or ICMP). Currently, you cannot manage ipv6 and other protocols through the security rules, making them permitted by default. To manage such protocols, you can deploy a firewall in front of your OpenStack cloud to control other types of traffic. The command requires the following arguments for both TCP and UDP rules:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:84(emphasis) ./doc/common/section_cli_nova_secgroups.xml:124(emphasis) ./doc/common/section_cli_nova_secgroups.xml:209(emphasis)
+msgid "&lt;secgroup&gt;"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:86(para) ./doc/common/section_cli_nova_secgroups.xml:126(para) ./doc/common/section_cli_nova_secgroups.xml:211(para)
+msgid "ID of security group."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:91(emphasis) ./doc/common/section_cli_nova_secgroups.xml:131(emphasis) ./doc/common/section_cli_nova_secgroups.xml:216(emphasis)
+msgid "&lt;ip_proto&gt;"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:98(emphasis) ./doc/common/section_cli_nova_secgroups.xml:223(emphasis)
+msgid "&lt;from_port&gt;"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:105(emphasis) ./doc/common/section_cli_nova_secgroups.xml:230(emphasis)
+msgid "&lt;to_port&gt;"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:112(emphasis) ./doc/common/section_cli_nova_secgroups.xml:152(emphasis) ./doc/common/section_cli_nova_secgroups.xml:237(emphasis)
+msgid "&lt;cidr&gt;"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:118(para)
+msgid "For ICMP rules, instead of specifying a begin and end port, you specify the allowed ICMP code and ICMP type:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:133(para)
+msgid "IP protocol (with icmp specified)."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:138(emphasis)
+msgid "&lt;ICMP_code&gt;"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:140(para)
+msgid "The ICMP code."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:145(emphasis)
+msgid "&lt;ICMP_type&gt;"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:147(para)
+msgid "The ICMP type."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:154(para)
+msgid "CIDR for the source address range."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:159(para)
+msgid "Entering <literal>-1</literal> for both code and type indicates that all ICMP codes and types are allowed."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:164(title)
+msgid "The CIDR notation"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:165(para)
+msgid "That notation allows you to specify a base IP address and a suffix that designates the number of significant bits in the IP address used to identify the network. For example, by specifying a <literal>88.170.60.32/27</literal>, you specify <literal>88.170.60.32</literal> as the <emphasis role=\"bold\">base IP</emphasis> and <literal>27</literal> as the <emphasis role=\"bold\">suffix</emphasis>. Because you use an IPV4 format, only 5 bits are available for the host part (32 minus 27). The <literal>0.0.0.0/0</literal> notation means you allow the entire IPV4 range, which allows all addresses."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:179(para)
+msgid "For example, to allow any IP address to access a web server running on one of your instances inside the default security group:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:188(para)
+msgid "To allow any IP address to ping an instance inside the default security group (Code 0, Type 8 for the ECHO request):"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml:204(para)
+msgid "To delete a rule, you must specify exactly the same arguments that you used to create it:"
+msgstr ""
+
+#: ./doc/common/section_cli_version.xml:6(title)
+msgid "Discover the version number for a client"
+msgstr ""
+
+#: ./doc/common/section_cli_version.xml:7(para)
+msgid "Run the following command to discover the version number for a client:"
+msgstr ""
+
+#: ./doc/common/section_cli_version.xml:10(para)
+msgid "For example, to see the version number for the <placeholder-1/> client, run the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_version.xml:14(para)
+msgid "The version number (2.15.0 in the example) is returned."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml:6(title)
+msgid "Install XenServer and XCP"
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml:8(para)
+msgid "Before you can run OpenStack with XCP or XenServer, you must install the software on <link href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/installation.html#sys_requirements\">an appropriate server</link>."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml:13(para)
+msgid "Xen is a type 1 hypervisor: When your server starts, Xen is the first software that runs. Consequently, you must install XenServer or XCP before you install the operating system where you want to run OpenStack code. The OpenStack services then run in a virtual machine that you install on top of XenServer."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml:20(para)
+msgid "Before you can install your system, decide whether to install a free or paid edition of Citrix XenServer or Xen Cloud Platform from Xen.org. Download the software from these locations:"
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml:28(link)
+msgid "http://www.citrix.com/XenServer/download"
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml:33(link)
+msgid "http://www.xen.org/download/xcp/index.html"
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml:36(para)
+msgid "When you install many servers, you might find it easier to perform <link href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/installation.html#pxe_boot_install\">PXE boot installations of XenServer or XCP</link>. You can also package any post-installation changes that you want to make to your XenServer by <link href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/supplemental_pack_ddk.html\">creating your own XenServer supplemental pack</link>."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml:46(para)
+msgid "You can also install the <package>xcp-xenapi</package> package on Debian-based distributions to get XCP. However, this is not as mature or feature complete as above distributions. This modifies your boot loader to first boot Xen and boot your existing OS on top of Xen as Dom0. The xapi daemon runs in Dom0. Find more details at <link href=\"http://wiki.xen.org/wiki/Project_Kronos\">http://wiki.xen.org/wiki/Project_Kronos</link>."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml:55(para)
+msgid "Make sure you use the EXT type of storage repository (SR). Features that require access to VHD files (such as copy on write, snapshot and migration) do not work when you use the LVM SR. Storage repository (SR) is a XenAPI-specific term relating to the physical storage where virtual disks are stored."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml:61(para)
+msgid "On the XenServer/XCP installation screen, choose the <guilabel>XenDesktop Optimized</guilabel> option. If you use an answer file, make sure you use <literal>srtype=\"ext\"</literal> in the <option>installation</option> tag of the answer file."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml:69(title)
+msgid "Post-installation steps"
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml:70(para)
+msgid "Complete these steps to install OpenStack in your XenServer system:"
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml:74(para)
+msgid "For resize and migrate functionality, complete the changes described in the <citetitle>Configure resize</citetitle> section in the <link href=\"../config-reference/content/index.html\"><citetitle>OpenStack Configuration Reference</citetitle></link>."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml:82(para)
+msgid "Install the VIF isolation rules to help prevent mac and IP address spoofing."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml:86(para)
+msgid "Install the XenAPI plug-ins. See the following section."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml:90(para)
+msgid "To support AMI type images, you must set up <literal>/boot/guest</literal> symlink/directory in Dom0. For detailed instructions, see next section."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml:96(para)
+msgid "To support resize/migration, set up an ssh trust relation between your XenServer hosts, and ensure <literal>/images</literal> is properly set up. See next section for more details."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml:102(para)
+msgid "Create a Paravirtualized virtual machine that can run the OpenStack compute code."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml:106(para)
+msgid "Install and configure the <systemitem class=\"service\">nova-compute</systemitem> in the above virtual machine."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml:111(para)
+msgid "For more information, see how DevStack performs the last three steps for developer deployments. For more information about DevStack, see <citetitle>Getting Started With XenServer and Devstack</citetitle> (<link href=\"https://github.com/openstack-dev/devstack/blob/master/tools/xen/README.md\">https://github.com/openstack-dev/devstack/blob/master/tools/xen/README.md</link>). Find more information about the first step, see <citetitle>Multi Tenancy Networking Protections in XenServer</citetitle> (<link href=\"https://github.com/openstack/nova/blob/master/plugins/xenserver/doc/networking.rst\">https://github.com/openstack/nova/blob/master/plugins/xenserver/doc/networking.rst</link>). For information about how to install the XenAPI plug-ins, see <citetitle>XenAPI README</citetitle> (<link href=\"https://github.com/openstack/nova/blob/master/plugins/xenserver/xenapi/README\">https://github.com/openstack/nova/blob/master/plugins/xenserver/xenapi/README</link>)."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml:131(title)
+msgid "Xen boot from ISO"
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml:132(para)
+msgid "XenServer, through the XenAPI integration with OpenStack, provides a feature to boot instances from an ISO file. To activate the Boot From ISO feature, you must configure the SR elements on XenServer host, as follows:"
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml:139(para)
+msgid "Create an ISO-typed SR, such as an NFS ISO library, for instance. For this, using XenCenter is a simple method. You must export an NFS volume from a remote NFS server. Make sure it is exported in read-write mode."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml:146(para)
+msgid "On the compute host, find and record the uuid of this ISO SR:"
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml:151(para)
+msgid "Locate the uuid of the NFS ISO library:"
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml:155(para)
+msgid "Set the uuid and configuration. Even if an NFS mount point is not local, you must specify <literal>local-storage-iso</literal>."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml:161(para)
+msgid "Make sure the host-uuid from <literal>xe pbd-list</literal> equals the uuid of the host you found previously:"
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml:167(para)
+msgid "You can now add images through the OpenStack Image Service with <literal>disk-format=iso</literal>, and boot them in OpenStack Compute:"
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml:7(title)
+msgid "Install the XenAPI plug-ins"
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml:8(para)
+msgid "When you use Xen as the hypervisor for OpenStack Compute, you can install a Python script (or any executable) on the host side, and call that through the XenAPI. These scripts are called plug-ins. The XenAPI plug-ins live in the nova code repository. These plug-ins have to be copied to the Dom0 for the hypervisor, to the appropriate directory, where xapi can find them. There are several options for the installation. The important thing is to ensure that the version of the plug-ins are in line with the nova installation by only installing plug-ins from a matching nova repository."
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml:19(title)
+msgid "Manually install the plug-in"
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml:22(para)
+msgid "Create temporary files/directories:"
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml:27(para)
+msgid "Get the source from github. The example assumes the master branch is used. Amend the URL to match the version being used:"
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml:32(para)
+msgid "(Alternatively) To use the official Ubuntu packages, use the following commands to get the nova code base:"
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml:39(para)
+msgid "Copy the plug-ins to the hypervisor:"
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml:44(para)
+msgid "Remove the temporary files/directories:"
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml:51(title)
+msgid "Package a XenServer supplemental pack"
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml:52(para)
+msgid "Follow these steps to produce a supplemental pack from the nova sources, and package it as a XenServer supplemental pack."
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml:57(para)
+msgid "Create RPM packages. Given you have the nova sources. Use one of the methods in <xref linkend=\"manual_install\"/>:"
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml:62(para)
+msgid "These commands leave an <filename>.rpm</filename> file in the <filename>rpmbuild/RPMS/noarch/</filename> directory."
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml:68(para)
+msgid "Pack the RPM packages to a Supplemental Pack, using the XenServer DDK (the following command should be issued on the XenServer DDK virtual appliance, after the produced rpm file has been copied over):"
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml:81(para)
+msgid "This command produces an <filename>.iso</filename> file in the output directory specified. Copy that file to the hypervisor."
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml:87(para)
+msgid "Install the Supplemental Pack. Log in to the hypervisor, and issue:"
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml:5(title)
+msgid "Orchestration module"
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml:6(para)
+msgid "The Orchestration module provides a template-based orchestration for describing a cloud application, by running OpenStack API calls to generate running cloud applications. The software integrates other core components of OpenStack into a one-file template system. The templates allow you to create most OpenStack resource types, such as instances, floating IPs, volumes, security groups and users. It also provides advanced functionality, such as instance high availability, instance auto-scaling, and nested stacks. This enables OpenStack core projects to receive a larger user base."
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml:16(para)
+msgid "The service enables deployers to integrate with the Orchestration module directly or through custom plug-ins."
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml:18(para)
+msgid "The Orchestration module consists of the following components:"
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml:22(term)
+msgid "<code>heat</code> command-line client"
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml:23(para)
+msgid "A CLI that communicates with the heat-api to run AWS CloudFormation APIs. End developers can directly use the Orchestration REST API."
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml:28(term)
+msgid "<code>heat-api</code> component"
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml:28(para)
+msgid "An OpenStack-native REST API that processes API requests by sending them to the heat-engine over Remote Procedure Call (RPC)."
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml:34(term)
+msgid "<code>heat-api-cfn</code> component"
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml:34(para)
+msgid "An AWS Query API that is compatible with AWS CloudFormation. It processes API requests by sending them to the heat-engine over RPC."
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml:40(code)
+msgid "heat-engine"
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml:41(para)
+msgid "Orchestrates the launching of templates and provides events back to the API consumer."
+msgstr ""
+
+#: ./doc/common/ch_using_openstack_overview.xml:7(title)
+msgid "How can I <phrase audience=\"enduser\">use</phrase><phrase audience=\"adminuser\">administer</phrase> an OpenStack cloud?"
+msgstr ""
+
+#: ./doc/common/ch_using_openstack_overview.xml:11(para)
+msgid "As an OpenStack cloud end user, you can provision your own resources within the limits set by administrators."
+msgstr ""
+
+#: ./doc/common/ch_using_openstack_overview.xml:14(para)
+msgid "As an OpenStack cloud administrative user, you can manage tenants, known as <glossterm baseform=\"project\">projects</glossterm>, users, services, images, flavors, and quotas."
+msgstr ""
+
+#: ./doc/common/ch_using_openstack_overview.xml:18(para)
+msgid "The examples in this guide show you how to perform tasks by using the following methods:"
+msgstr ""
+
+#: ./doc/common/ch_using_openstack_overview.xml:22(para)
+msgid "OpenStack dashboard. Use this web-based graphical interface, code named <link href=\"https://github.com/openstack/horizon/\">horizon</link>, to view, create, and manage resources<phrase audience=\"adminuser\"> and services</phrase>."
+msgstr ""
+
+#: ./doc/common/ch_using_openstack_overview.xml:30(para)
+msgid "OpenStack command-line clients. Each core OpenStack project has a command-line client that you can use to run simple commands to view, create, and manage resources<phrase audience=\"adminuser\"> and services</phrase> in a cloud and automate tasks by using scripts."
+msgstr ""
+
+#: ./doc/common/ch_using_openstack_overview.xml:38(para)
+msgid "You can modify these examples for your specific use cases."
+msgstr ""
+
+#: ./doc/common/ch_using_openstack_overview.xml:40(para)
+msgid "In addition to these ways of interacting with a cloud, you can access the OpenStack APIs directly or indirectly through <link href=\"http://curl.haxx.se/\">cURL</link> commands or open SDKs. You can automate access or build tools to manage resources and services by using the native OpenStack APIs or the EC2 compatibility API."
+msgstr ""
+
+#: ./doc/common/ch_using_openstack_overview.xml:46(para)
+msgid "To use the OpenStack APIs, it helps to be familiar with HTTP/1.1, RESTful web services, the OpenStack services, and JSON or XML data serialization formats."
 msgstr ""
 
 #. When image changes, this message will be marked fuzzy or untranslated for you.
 #. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-characteristics.xml:49(None)
-msgid "@@image: '../common/figures/objectstorage.png'; md5=e26e374ace84070f5fed24e73adcd562"
+#: ./doc/common/section_keystone-concepts.xml:120(None) ./doc/common/section_keystone-concepts.xml:125(None)
+msgid "@@image: 'figures/SCH_5002_V00_NUAC-Keystone.png'; md5=734714c50c99fc1d74bdfd9f9cd049a6"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-characteristics.xml:7(title)
-msgid "Object Storage characteristics"
+#: ./doc/common/section_keystone-concepts.xml:7(title)
+msgid "OpenStack Identity concepts"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-characteristics.xml:8(para)
-msgid "The key characteristics of Object Storage are that:"
+#: ./doc/common/section_keystone-concepts.xml:8(para)
+msgid "The OpenStack<glossterm>Identity Service</glossterm> performs the following functions:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-characteristics.xml:11(para)
-msgid "All objects stored in Object Storage have a URL."
+#: ./doc/common/section_keystone-concepts.xml:12(para)
+msgid "Tracking users and their permissions."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-characteristics.xml:14(para)
-msgid "All objects stored are replicated 3✕ in as-unique-as-possible zones, which can be defined as a group of drives, a node, a rack, and so on."
+#: ./doc/common/section_keystone-concepts.xml:15(para)
+msgid "Providing a catalog of available services with their API endpoints."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-characteristics.xml:18(para)
-msgid "All objects have their own metadata."
+#: ./doc/common/section_keystone-concepts.xml:19(para)
+msgid "To understand OpenStack Identity, you must understand the following concepts:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-characteristics.xml:21(para)
-msgid "Developers interact with the object storage system through a RESTful HTTP API."
+#: ./doc/common/section_keystone-concepts.xml:23(term)
+msgid "User"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-characteristics.xml:25(para)
-msgid "Object data can be located anywhere in the cluster."
+#: ./doc/common/section_keystone-concepts.xml:25(para)
+msgid "Digital representation of a person, system, or service who uses OpenStack cloud services. The Identity service validates that incoming requests are made by the user who claims to be making the call. Users have a login and may be assigned tokens to access resources. Users can be directly assigned to a particular tenant and behave as if they are contained in that tenant."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-characteristics.xml:28(para)
-msgid "The cluster scales by adding additional nodes without sacrificing performance, which allows a more cost-effective linear storage expansion than fork-lift upgrades."
+#: ./doc/common/section_keystone-concepts.xml:36(term)
+msgid "Credentials"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-characteristics.xml:33(para)
-msgid "Data doesn't have to be migrate to an entirely new storage system."
+#: ./doc/common/section_keystone-concepts.xml:38(para)
+msgid "Data that confirms the user's identity. For example, user name and password; user name and API key; or an authentication token provided by the Identity Service."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-characteristics.xml:36(para)
-msgid "New nodes can be added to the cluster without downtime."
+#: ./doc/common/section_keystone-concepts.xml:45(term)
+msgid "Authentication"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-characteristics.xml:39(para)
-msgid "Failed nodes and disks can be swapped out without downtime."
+#: ./doc/common/section_keystone-concepts.xml:47(para)
+msgid "The process of confirming the identity of a user. OpenStack Identity confirms an incoming request by validating a set of credentials supplied by the user."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-characteristics.xml:42(para)
-msgid "It runs on industry-standard hardware, such as Dell, HP, and Supermicro."
+#: ./doc/common/section_keystone-concepts.xml:51(para)
+msgid "These credentials are initially a user name and password; or a user name and API key. When user credentials are validated, OpenStack Identity issues an authentication token which the user provides in subsequent requests."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-characteristics.xml:53(para)
-msgid "Developers can either write directly to the Swift API or use one of the many client libraries that exist for all of the popular programming languages, such as Java, Python, Ruby, and C#. Amazon S3 and RackSpace Cloud Files users should be very familiar with Object Storage. Users new to object storage systems will have to adjust to a different approach and mindset than those required for a traditional filesystem."
+#: ./doc/common/section_keystone-concepts.xml:59(term)
+msgid "Token"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts.xml:61(para)
+msgid "An arbitrary bit of text that is used to access resources. Each token has information which defines access to resources. A token may be revoked at any time and is valid for a finite duration."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts.xml:65(para)
+msgid "While OpenStack Identity supports token-based authentication in this release, the intention is to support additional protocols in the future. Its main purpose is to be an integration service, and not aspire to be a full-fledged identity store and management solution."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts.xml:74(term)
+msgid "Tenant"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts.xml:76(para)
+msgid "A container used to group or isolate resources and/or identity objects. Depending on the service operator, a tenant may map to a customer, account, organization, or project."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts.xml:85(para)
+msgid "An OpenStack service, such as Compute (nova), Object Storage (swift), or Image Service (glance). It provides one or more endpoints through which users can access resources and perform operations."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts.xml:92(term)
+msgid "Endpoint"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts.xml:94(para)
+msgid "A network-accessible address where you access a service, usually a URL address. If you are using an extension for templates, an endpoint template can be created, which represents the templates of all the consumable services that are available across the regions."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts.xml:102(term)
+msgid "Role"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts.xml:104(para)
+msgid "A personality with a defined set of user rights and privileges to perform a specific set of operations."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts.xml:106(para)
+msgid "In the Identity service, a token that is issued to a user includes the list of roles. Services that are being called by that user determine how they interpret the set of roles a user has and to which operations or resources each role grants access."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts.xml:114(para)
+msgid "The following diagram shows the OpenStack Identity process flow:"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:7(title)
+msgid "Features and benefits"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:12(th)
+msgid "Features"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:13(th)
+msgid "Benefits"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:18(emphasis)
+msgid "Leverages commodity hardware"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:19(td)
+msgid "No lock-in, lower price/GB."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:22(emphasis)
+msgid "HDD/node failure agnostic"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:23(td)
+msgid "Self-healing, reliable, data redundancy protects from failures."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:27(emphasis)
+msgid "Unlimited storage"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:28(td)
+msgid "Large and flat namespace, highly scalable read/write access, able to serve content directly from storage system."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:32(emphasis)
+msgid "Multi-dimensional scalability"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:34(td)
+msgid "Scale-out architecture: Scale vertically and horizontally-distributed storage. Backs up and archives large amounts of data with linear performance."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:39(emphasis)
+msgid "Account/container/object structure"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:40(td)
+msgid "No nesting, not a traditional file system: Optimized for scale, it scales to multiple petabytes and billions of objects."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:45(emphasis)
+msgid "Built-in replication 3✕ + data redundancy (compared with 2✕ on RAID)"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:48(td)
+msgid "A configurable number of accounts, containers and object copies for high availability."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:52(emphasis)
+msgid "Easily add capacity (unlike RAID resize)"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:54(td)
+msgid "Elastic data scaling with ease"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:57(emphasis)
+msgid "No central database"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:58(td)
+msgid "Higher performance, no bottlenecks"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:61(emphasis)
+msgid "RAID not required"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:62(td)
+msgid "Handle many small, random reads and writes efficiently"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:65(emphasis)
+msgid "Built-in management utilities"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:66(td)
+msgid "Account management: Create, add, verify, and delete users; Container management: Upload, download, and verify; Monitoring: Capacity, host, network, log trawling, and cluster health."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:72(emphasis)
+msgid "Drive auditing"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:73(td)
+msgid "Detect drive failures preempting data corruption"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:76(emphasis)
+msgid "Expiring objects"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:77(td)
+msgid "Users can set an expiration time or a TTL on an object to control access"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:81(emphasis)
+msgid "Direct object access"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:82(td)
+msgid "Enable direct browser access to content, such as for a control panel"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:86(emphasis)
+msgid "Realtime visibility into client requests"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:88(td)
+msgid "Know what users are requesting."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:91(emphasis)
+msgid "Supports S3 API"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:92(td)
+msgid "Utilize tools that were designed for the popular S3 API."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:96(emphasis)
+msgid "Restrict containers per account"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:98(td)
+msgid "Limit access to control usage by user."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:101(emphasis)
+msgid "Support for NetApp, Nexenta, SolidFire"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:103(td)
+msgid "Unified support for block volumes using a variety of storage systems."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:107(emphasis)
+msgid "Snapshot and backup API for block volumes"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:109(td)
+msgid "Data protection and recovery for VM data."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:112(emphasis)
+msgid "Standalone volume API available"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:114(td)
+msgid "Separate endpoint and API for integration with other compute systems."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:118(emphasis)
+msgid "Integration with Compute"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml:120(td)
+msgid "Fully integrated with Compute for attaching block volumes and reporting on usage."
 msgstr ""
 
 #: ./doc/common/section_dashboard_sessions.xml:6(title)
@@ -17823,472 +17831,2504 @@ msgstr ""
 msgid "See the Django <link href=\"https://docs.djangoproject.com/en/dev/topics/http/sessions/#using-cookie-based-sessions\">cookie-based sessions</link> documentation."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml:6(title)
-msgid "Troubleshoot Object Storage"
+#: ./doc/common/section_kvm_enable.xml:6(title)
+msgid "Enable KVM"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml:7(para)
-msgid "For Object Storage, everything is logged in <filename>/var/log/syslog</filename> (or messages on some distros). Several settings enable further customization of logging, such as <literal>log_name</literal>, <literal>log_facility</literal>, and <literal>log_level</literal>, within the object server configuration files."
+#: ./doc/common/section_kvm_enable.xml:7(para)
+msgid "To perform these steps, you must be logged in as the <systemitem>root</systemitem> user."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml:11(title)
-msgid "Drive failure"
+#: ./doc/common/section_kvm_enable.xml:11(para)
+msgid "To determine whether the <literal>svm</literal> or <literal>vmx</literal> CPU extensions are present, run this command:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml:12(para)
-msgid "In the event that a drive has failed, the first step is to make sure the drive is unmounted. This will make it easier for Object Storage to work around the failure until it has been resolved. If the drive is going to be replaced immediately, then it is just best to replace the drive, format it, remount it, and let replication fill it up."
+#: ./doc/common/section_kvm_enable.xml:15(para)
+msgid "This command generates output if the CPU is hardware-virtualization capable. Even if output is shown, you might still need to enable virtualization in the system BIOS for full support."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml:16(para)
-msgid "If the drive can’t be replaced immediately, then it is best to leave it unmounted, and remove the drive from the ring. This will allow all the replicas that were on that drive to be replicated elsewhere until the drive is replaced. Once the drive is replaced, it can be re-added to the ring."
+#: ./doc/common/section_kvm_enable.xml:19(para)
+msgid "If no output appears, consult your system documentation to ensure that your CPU and motherboard support hardware virtualization. Verify that any relevant hardware virtualization options are enabled in the system BIOS."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml:20(para)
-msgid "You can look at error messages in <filename>/var/log/kern.log</filename> for hints of drive failure."
+#: ./doc/common/section_kvm_enable.xml:24(para)
+msgid "The BIOS for each manufacturer is different. If you must enable virtualization in the BIOS, look for an option containing the words <literal>virtualization</literal>, <literal>VT</literal>, <literal>VMX</literal>, or <literal>SVM</literal>."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml:23(title)
-msgid "Server failure"
+#: ./doc/common/section_kvm_enable.xml:32(para)
+msgid "To list the loaded kernel modules and verify that the <literal>kvm</literal> modules are loaded, run this command:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml:24(para)
-msgid "If a server is having hardware issues, it is a good idea to make sure the Object Storage services are not running. This will allow Object Storage to work around the failure while you troubleshoot."
+#: ./doc/common/section_kvm_enable.xml:36(para)
+msgid "If the output includes <systemitem>kvm_intel</systemitem> or <systemitem>kvm_amd</systemitem>, the <systemitem>kvm</systemitem> hardware virtualization modules are loaded and your kernel meets the module requirements for OpenStack Compute."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml:27(para)
-msgid "If the server just needs a reboot, or a small amount of work that should only last a couple of hours, then it is probably best to let Object Storage work around the failure and get the machine fixed and back online. When the machine comes back online, replication will make sure that anything that is missing during the downtime will get updated."
+#: ./doc/common/section_kvm_enable.xml:43(para)
+msgid "If the output does not show that the <literal>kvm</literal> module is loaded, run this command to load it:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml:32(para)
-msgid "If the server has more serious issues, then it is probably best to remove all of the server’s devices from the ring. Once the server has been repaired and is back online, the server’s devices can be added back into the ring. It is important that the devices are reformatted before putting them back into the ring as it is likely to be responsible for a different set of partitions than before."
+#: ./doc/common/section_kvm_enable.xml:47(para)
+msgid "Run the command for your CPU. For Intel, run this command:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml:40(title)
-msgid "Detect failed drives"
+#: ./doc/common/section_kvm_enable.xml:50(para)
+msgid "For AMD, run this command:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml:41(para)
-msgid "It has been our experience that when a drive is about to fail, error messages will spew into /var/log/kern.log. There is a script called swift-drive-audit that can be run via cron to watch for bad drives. If errors are detected, it will unmount the bad drive, so that Object Storage can work around it. The script takes a configuration file with the following settings:"
+#: ./doc/common/section_kvm_enable.xml:52(para)
+msgid "Because a KVM installation can change user group membership, you might need to log in again for changes to take effect."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml:47(para)
-msgid "This script has only been tested on Ubuntu 10.04, so if you are using a different distro or OS, some care should be taken before using in production."
+#: ./doc/common/section_kvm_enable.xml:55(para)
+msgid "If the kernel modules do not load automatically, use the procedures listed in these subsections."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml:52(title)
-msgid "Emergency recovery of ring builder files"
+#: ./doc/common/section_kvm_enable.xml:59(para)
+msgid "If the checks indicate that required hardware virtualization support or kernel modules are disabled or unavailable, you must either enable this support on the system or find a system with this support."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml:53(para)
-msgid "You should always keep a backup of swift ring builder files. However, if an emergency occurs, this procedure may assist in returning your cluster to an operational state."
+#: ./doc/common/section_kvm_enable.xml:64(para)
+msgid "Some systems require that you enable VT support in the system BIOS. If you believe your processor supports hardware acceleration but the previous command did not produce output, reboot your machine, enter the system BIOS, and enable the VT option."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml:56(para)
-msgid "Using existing swift tools, there is no way to recover a builder file from a <filename>ring.gz</filename> file. However, if you have a knowledge of Python, it is possible to construct a builder file that is pretty close to the one you have lost. The following is what you will need to do."
+#: ./doc/common/section_kvm_enable.xml:70(para)
+msgid "If KVM acceleration is not supported, configure Compute to use a different hypervisor, such as <link href=\"http://docs.openstack.org/trunk/config-reference/content/qemu.html\">QEMU</link> or <link href=\"http://docs.openstack.org/trunk/config-reference/content/introduction-to-xen.html\">Xen</link>."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml:61(para)
-msgid "This procedure is a last-resort for emergency circumstances. It requires knowledge of the swift python code and may not succeed."
+#: ./doc/common/section_kvm_enable.xml:76(para)
+msgid "These procedures help you load the kernel modules for Intel-based and AMD-based processors if they do not load automatically during KVM installation."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml:64(para)
-msgid "First, load the ring and a new ringbuilder object in a Python REPL:"
+#: ./doc/common/section_kvm_enable.xml:80(title)
+msgid "Intel-based processors"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml:67(para)
-msgid "Now, start copying the data we have in the ring into the builder."
+#: ./doc/common/section_kvm_enable.xml:81(para)
+msgid "If your compute host is Intel-based, run these commands as root to load the kernel modules:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml:84(para)
-msgid "This is the extent of the recoverable fields. For <literal>min_part_hours</literal> you'll either have to remember what the value you used was, or just make up a new one."
+#: ./doc/common/section_kvm_enable.xml:85(para)
+msgid "Add these lines to the <filename>/etc/modules</filename> file so that these modules load on reboot:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml:89(para)
-msgid "Try some validation: if this doesn't raise an exception, you may feel some hope. Not too much, though."
+#: ./doc/common/section_kvm_enable.xml:91(title)
+msgid "AMD-based processors"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml:92(para)
-msgid "Save the builder."
+#: ./doc/common/section_kvm_enable.xml:92(para)
+msgid "If your compute host is AMD-based, run these commands as root to load the kernel modules:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml:96(para)
-msgid "You should now have a file called 'account.builder' in the current working directory. Next, run <literal>swift-ring-builder account.builder write_ring</literal> and compare the new account.ring.gz to the account.ring.gz that you started from. They probably won't be byte-for-byte identical, but if you load them up in a REPL and their <literal>_replica2part2dev_id</literal> and <literal>devs</literal> attributes are the same (or nearly so), then you're in good shape."
+#: ./doc/common/section_kvm_enable.xml:96(para)
+msgid "Add these lines to <filename>/etc/modules</filename> file so that these modules load on reboot:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml:103(para)
-msgid "Next, repeat the procedure for <filename>container.ring.gz</filename> and <filename>object.ring.gz</filename>, and you might get usable builder files."
+#: ./doc/common/tables/ceilometer-database.xml:8(caption) ./doc/common/tables/cinder-database.xml:8(caption) ./doc/common/tables/trove-database.xml:8(caption) ./doc/common/tables/heat-database.xml:8(caption) ./doc/common/tables/keystone-database.xml:8(caption)
+msgid "Description of configuration options for database"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:8(caption) ./doc/common/tables/ceilometer-cells.xml:8(caption)
-msgid "Description of configuration options for cells"
-msgstr ""
-
-#: ./doc/common/tables/nova-cells.xml:13(th) ./doc/common/tables/trove-db_mongodb.xml:13(th) ./doc/common/tables/keystone-debug.xml:13(th) ./doc/common/tables/glance-policy.xml:13(th) ./doc/common/tables/neutron-mlnx.xml:13(th) ./doc/common/tables/nova-ipv6.xml:13(th) ./doc/common/tables/cinder-eqlx.xml:13(th) ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml:12(th) ./doc/common/tables/swift-object-expirer-filter-cache.xml:12(th) ./doc/common/tables/swift-proxy-server-filter-cache.xml:12(th) ./doc/common/tables/nova-rpc_all.xml:13(th) ./doc/common/tables/neutron-ml2_l2pop.xml:13(th) ./doc/common/tables/glance-qpid.xml:13(th) ./doc/common/tables/swift-container-server-DEFAULT.xml:12(th) ./doc/common/tables/neutron-ml2_bigswitch.xml:13(th) ./doc/common/tables/neutron-ml2_gre.xml:13(th) ./doc/common/tables/nova-volumes.xml:13(th) ./doc/common/tables/glance-gridfs.xml:13(th) ./doc/common/tables/neutron-ml2_arista.xml:13(th) ./doc/common/tables/glance-filesystem.xml:13(th) ./doc/common/tables/heat-redis.xml:13(th) ./doc/common/tables/trove-logging.xml:13(th) ./doc/common/tables/swift-container-server-container-updater.xml:12(th) ./doc/common/tables/cinder-storage_gpfs.xml:13(th) ./doc/common/tables/cinder-nexenta_iscsi.xml:13(th) ./doc/common/tables/nova-tilera.xml:13(th) ./doc/common/tables/nova-ca.xml:13(th) ./doc/common/tables/heat-clients_nova.xml:13(th) ./doc/common/tables/swift-account-server-filter-recon.xml:12(th) ./doc/common/tables/cinder-huawei.xml:13(th) ./doc/common/tables/keystone-qpid.xml:13(th) ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:13(th) ./doc/common/tables/swift-container-server-container-replicator.xml:12(th) ./doc/common/tables/nova-glance.xml:13(th) ./doc/common/tables/neutron-dhcp_agent.xml:13(th) ./doc/common/tables/nova-neutron.xml:13(th) ./doc/common/tables/cinder-backups_ceph.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-name_check.xml:12(th) ./doc/common/tables/nova-metadata.xml:13(th) ./doc/common/tables/glance-s3.xml:13(th) ./doc/common/tables/glance-auth_token.xml:13(th) ./doc/common/tables/neutron-kombu.xml:13(th) ./doc/common/tables/trove-redis.xml:13(th) ./doc/common/tables/trove-qpid.xml:13(th) ./doc/common/tables/trove-compute.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:12(th) ./doc/common/tables/trove-nova.xml:13(th) ./doc/common/tables/ceilometer-cells.xml:13(th) ./doc/common/tables/keystone-oauth.xml:13(th) ./doc/common/tables/cinder-block-device.xml:13(th) ./doc/common/tables/cinder-zones.xml:13(th) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:13(th) ./doc/common/tables/swift-container-server-container-sync.xml:12(th) ./doc/common/tables/neutron-common.xml:13(th) ./doc/common/tables/neutron-compute.xml:13(th) ./doc/common/tables/swift-object-server-object-auditor.xml:12(th) ./doc/common/tables/keystone-ldap.xml:13(th) ./doc/common/tables/heat-rpc.xml:13(th) ./doc/common/tables/neutron-openvswitch_agent.xml:13(th) ./doc/common/tables/cinder-compute.xml:13(th) ./doc/common/tables/keystone-identity.xml:13(th) ./doc/common/tables/cinder-lvm.xml:13(th) ./doc/common/tables/keystone-trust.xml:13(th) ./doc/common/tables/cinder-storage_nfs.xml:13(th) ./doc/common/tables/neutron-plumgrid.xml:13(th) ./doc/common/tables/heat-cfn_api.xml:13(th) ./doc/common/tables/nova-hypervisor.xml:13(th) ./doc/common/tables/trove-rabbitmq.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:12(th) ./doc/common/tables/trove-api.xml:13(th) ./doc/common/tables/cinder-quota.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml:12(th) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:12(th) ./doc/common/tables/nova-console.xml:13(th) ./doc/common/tables/ceilometer-events.xml:13(th) ./doc/common/tables/keystone-os_inherit.xml:13(th) ./doc/common/tables/heat-clients.xml:13(th) ./doc/common/tables/heat-notification.xml:13(th) ./doc/common/tables/keystone-assignment.xml:13(th) ./doc/common/tables/nova-common.xml:13(th) ./doc/common/tables/swift-object-server-object-updater.xml:12(th) ./doc/common/tables/glance-zmq.xml:13(th) ./doc/common/tables/neutron-metering_agent.xml:13(th) ./doc/common/tables/trove-taskmanager.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml:12(th) ./doc/common/tables/keystone-zeromq.xml:13(th) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:12(th) ./doc/common/tables/nova-keymgr.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-dlo.xml:12(th) ./doc/common/tables/neutron-api.xml:13(th) ./doc/common/tables/ceilometer-redis.xml:13(th) ./doc/common/tables/ceilometer-swift.xml:13(th) ./doc/common/tables/cinder-hplefthand.xml:13(th) ./doc/common/tables/heat-qpid.xml:13(th) ./doc/common/tables/nova-testing.xml:13(th) ./doc/common/tables/cinder-backups.xml:13(th) ./doc/common/tables/swift-container-server-pipeline-main.xml:12(th) ./doc/common/tables/neutron-ml2_ofa.xml:13(th) ./doc/common/tables/trove-debug.xml:13(th) ./doc/common/tables/swift-rsyncd-object.xml:12(th) ./doc/common/tables/nova-s3.xml:13(th) ./doc/common/tables/nova-zookeeper.xml:13(th) ./doc/common/tables/cinder-rpc.xml:13(th) ./doc/common/tables/cinder-api.xml:13(th) ./doc/common/tables/cinder-windows.xml:13(th) ./doc/common/tables/glance-vmware.xml:13(th) ./doc/common/tables/swift-object-server-pipeline-main.xml:12(th) ./doc/common/tables/trove-backup.xml:13(th) ./doc/common/tables/nova-auth_token.xml:13(th) ./doc/common/tables/cinder-san.xml:13(th) ./doc/common/tables/swift-account-server-app-account-server.xml:12(th) ./doc/common/tables/keystone-rpc.xml:13(th) ./doc/common/tables/cinder-keymgr.xml:13(th) ./doc/common/tables/nova-db.xml:13(th) ./doc/common/tables/neutron-ml2_vxlan.xml:13(th) ./doc/common/tables/glance-logging.xml:13(th) ./doc/common/tables/cinder-zoning.xml:13(th) ./doc/common/tables/glance-wsgi.xml:13(th) ./doc/common/tables/nova-periodic.xml:13(th) ./doc/common/tables/swift-account-server-filter-healthcheck.xml:12(th) ./doc/common/tables/cinder-images.xml:13(th) ./doc/common/tables/trove-swift.xml:13(th) ./doc/common/tables/swift-container-server-app-container-server.xml:12(th) ./doc/common/tables/swift-proxy-server-filter-slo.xml:12(th) ./doc/common/tables/cinder-auth_token.xml:13(th) ./doc/common/tables/heat-crypt.xml:13(th) ./doc/common/tables/neutron-wsgi.xml:13(th) ./doc/common/tables/neutron-scheduler.xml:13(th) ./doc/common/tables/keystone-security.xml:13(th) ./doc/common/tables/ceilometer-vmware.xml:13(th) ./doc/common/tables/glance-rbd.xml:13(th) ./doc/common/tables/heat-clients_heat.xml:13(th) ./doc/common/tables/heat-rabbitmq.xml:13(th) ./doc/common/tables/ceilometer-logging.xml:13(th) ./doc/common/tables/neutron-metadata.xml:13(th) ./doc/common/tables/glance-redis.xml:13(th) ./doc/common/tables/keystone-stats.xml:13(th) ./doc/common/tables/cinder-hp3par.xml:13(th) ./doc/common/tables/cinder-storage_ceph.xml:13(th) ./doc/common/tables/nova-livemigration.xml:13(th) ./doc/common/tables/nova-ldap.xml:13(th) ./doc/common/tables/nova-fping.xml:13(th) ./doc/common/tables/heat-clients_swift.xml:13(th) ./doc/common/tables/neutron-securitygroups.xml:13(th) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:13(th) ./doc/common/tables/nova-ec2.xml:13(th) ./doc/common/tables/swift-account-server-account-auditor.xml:12(th) ./doc/common/tables/trove-zeromq.xml:13(th) ./doc/common/tables/heat-database.xml:13(th) ./doc/common/tables/keystone-catalog.xml:13(th) ./doc/common/tables/swift-object-server-DEFAULT.xml:12(th) ./doc/common/tables/cinder-rootwrap.xml:13(th) ./doc/common/tables/ceilometer-database.xml:13(th) ./doc/common/tables/heat-debug.xml:13(th) ./doc/common/tables/cinder-nexenta_nfs.xml:13(th) ./doc/common/tables/trove-auth_token.xml:13(th) ./doc/common/tables/heat-waitcondition_api.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:12(th) ./doc/common/tables/neutron-ml2_vlan.xml:13(th) ./doc/common/tables/nova-policy.xml:13(th) ./doc/common/tables/keystone-amqp.xml:13(th) ./doc/common/tables/neutron-logging.xml:13(th) ./doc/common/tables/trove-db_cassandra.xml:13(th) ./doc/common/tables/glance-rpc.xml:13(th) ./doc/common/tables/nova-authentication.xml:13(th) ./doc/common/tables/cinder-vmware.xml:13(th) ./doc/common/tables/glance-sheepdog.xml:13(th) ./doc/common/tables/heat-logging.xml:13(th) ./doc/common/tables/keystone-notification.xml:13(th) ./doc/common/tables/neutron-qpid.xml:13(th) ./doc/common/tables/neutron-hyperv_agent.xml:13(th) ./doc/common/tables/glance-swift.xml:13(th) ./doc/common/tables/swift-account-server-DEFAULT.xml:12(th) ./doc/common/tables/neutron-bigswitch.xml:13(th) ./doc/common/tables/nova-libvirt.xml:13(th) ./doc/common/tables/neutron-lbaas.xml:13(th) ./doc/common/tables/cinder-backups_swift.xml:13(th) ./doc/common/tables/neutron-ml2_cisco.xml:13(th) ./doc/common/tables/ceilometer-rpc.xml:13(th) ./doc/common/tables/heat-loadbalancer.xml:13(th) ./doc/common/tables/heat-cloudwatch_api.xml:13(th) ./doc/common/tables/nova-pci.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:12(th) ./doc/common/tables/heat-clients_ceilometer.xml:13(th) ./doc/common/tables/neutron-varmour.xml:13(th) ./doc/common/tables/glance-imagecache.xml:13(th) ./doc/common/tables/trove-quota.xml:13(th) ./doc/common/tables/swift-rsyncd-account.xml:12(th) ./doc/common/tables/cinder-storage.xml:13(th) ./doc/common/tables/cinder-nas.xml:13(th) ./doc/common/tables/nova-vpn.xml:13(th) ./doc/common/tables/nova-wsgi.xml:13(th) ./doc/common/tables/cinder-storage_glusterfs.xml:13(th) ./doc/common/tables/swift-container-sync-realms-realm1.xml:12(th) ./doc/common/tables/swift-container-server-filter-healthcheck.xml:12(th) ./doc/common/tables/nova-availabilityzones.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-container_sync.xml:12(th) ./doc/common/tables/heat-zeromq.xml:13(th) ./doc/common/tables/keystone-memcache.xml:13(th) ./doc/common/tables/nova-vnc.xml:13(th) ./doc/common/tables/swift-swift-swift-constraints.xml:12(th) ./doc/common/tables/neutron-cisco.xml:13(th) ./doc/common/tables/keystone-logging.xml:13(th) ./doc/common/tables/nova-hyperv.xml:13(th) ./doc/common/tables/neutron-l3_agent.xml:13(th) ./doc/common/tables/swift-object-server-filter-recon.xml:12(th) ./doc/common/tables/cinder-coraid.xml:13(th) ./doc/common/tables/swift-container-server-container-auditor.xml:12(th) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:12(th) ./doc/common/tables/nova-vmware.xml:13(th) ./doc/common/tables/nova-logging.xml:13(th) ./doc/common/tables/nova-xen.xml:13(th) ./doc/common/tables/ceilometer-collector.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml:12(th) ./doc/common/tables/keystone-ec2.xml:13(th) ./doc/common/tables/keystone-auth.xml:13(th) ./doc/common/tables/swift-memcache-memcache.xml:12(th) ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:12(th) ./doc/common/tables/neutron-ml2.xml:13(th) ./doc/common/tables/ceilometer-api.xml:13(th) ./doc/common/tables/heat-clients_trove.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:12(th) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:13(th) ./doc/common/tables/glance-common.xml:13(th) ./doc/common/tables/nova-network.xml:13(th) ./doc/common/tables/cinder-scality.xml:13(th) ./doc/common/tables/neutron-notifier.xml:13(th) ./doc/common/tables/cinder-common.xml:13(th) ./doc/common/tables/nova-trustedcomputing.xml:13(th) ./doc/common/tables/neutron-ml2_flat.xml:13(th) ./doc/common/tables/heat-clients_cinder.xml:13(th) ./doc/common/tables/nova-configdrive.xml:13(th) ./doc/common/tables/cinder-database.xml:13(th) ./doc/common/tables/neutron-rpc.xml:13(th) ./doc/common/tables/cinder-zoning_manager.xml:13(th) ./doc/common/tables/trove-volume.xml:13(th) ./doc/common/tables/keystone-cache.xml:13(th) ./doc/common/tables/nova-zeromq.xml:13(th) ./doc/common/tables/glance-testing.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:12(th) ./doc/common/tables/glance-registry.xml:13(th) ./doc/common/tables/glance-amqp.xml:13(th) ./doc/common/tables/swift-object-server-object-replicator.xml:12(th) ./doc/common/tables/trove-database.xml:13(th) ./doc/common/tables/heat-clients_backends.xml:13(th) ./doc/common/tables/heat-amqp.xml:13(th) ./doc/common/tables/swift-dispersion-dispersion.xml:12(th) ./doc/common/tables/cinder-hpmsa.xml:13(th) ./doc/common/tables/cinder-emc.xml:13(th) ./doc/common/tables/swift-account-server-account-replicator.xml:12(th) ./doc/common/tables/neutron-fwaas.xml:13(th) ./doc/common/tables/glance-rabbitmq.xml:13(th) ./doc/common/tables/cinder-backups_tsm.xml:13(th) ./doc/common/tables/neutron-sdnve.xml:13(th) ./doc/common/tables/trove-db_mysql.xml:13(th) ./doc/common/tables/nova-qpid.xml:13(th) ./doc/common/tables/trove-rpc.xml:13(th) ./doc/common/tables/cinder-connection.xml:13(th) ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml:12(th) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:12(th) ./doc/common/tables/trove-db_redis.xml:13(th) ./doc/common/tables/ceilometer-qpid.xml:13(th) ./doc/common/tables/neutron-zeromq.xml:13(th) ./doc/common/tables/keystone-token.xml:13(th) ./doc/common/tables/neutron-vpn.xml:13(th) ./doc/common/tables/neutron-agent.xml:13(th) ./doc/common/tables/neutron-ryu.xml:13(th) ./doc/common/tables/swift-object-server-app-object-server.xml:12(th) ./doc/common/tables/trove-db_couchbase.xml:13(th) ./doc/common/tables/neutron-policy.xml:13(th) ./doc/common/tables/neutron-rootwrap.xml:13(th) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:12(th) ./doc/common/tables/swift-proxy-server-filter-staticweb.xml:12(th) ./doc/common/tables/trove-common.xml:13(th) ./doc/common/tables/cinder-ssl.xml:13(th) ./doc/common/tables/heat-api.xml:13(th) ./doc/common/tables/trove-db_percona.xml:13(th) ./doc/common/tables/swift-object-expirer-app-proxy-server.xml:12(th) ./doc/common/tables/ceilometer-amqp.xml:13(th) ./doc/common/tables/keystone-auth_token.xml:13(th) ./doc/common/tables/neutron-meta.xml:13(th) ./doc/common/tables/neutron-redis.xml:13(th) ./doc/common/tables/neutron-ssl.xml:13(th) ./doc/common/tables/ceilometer-exchange.xml:13(th) ./doc/common/tables/ceilometer-common.xml:13(th) ./doc/common/tables/ceilometer-alarm.xml:13(th) ./doc/common/tables/keystone-misc.xml:13(th) ./doc/common/tables/nova-scheduling.xml:13(th) ./doc/common/tables/ceilometer-auth.xml:13(th) ./doc/common/tables/swift-drive-audit-drive-audit.xml:12(th) ./doc/common/tables/neutron-ml2_mlnx.xml:13(th) ./doc/common/tables/swift-container-server-filter-recon.xml:12(th) ./doc/common/tables/trove-dns.xml:13(th) ./doc/common/tables/neutron-db.xml:13(th) ./doc/common/tables/neutron-ml2_brocade.xml:13(th) ./doc/common/tables/neutron-brocade.xml:13(th) ./doc/common/tables/keystone-redis.xml:13(th) ./doc/common/tables/heat-auth_token.xml:13(th) ./doc/common/tables/keystone-database.xml:13(th) ./doc/common/tables/swift-object-expirer-pipeline-main.xml:12(th) ./doc/common/tables/heat-clients_neutron.xml:13(th) ./doc/common/tables/neutron-linuxbridge_agent.xml:13(th) ./doc/common/tables/cinder-xiv.xml:13(th) ./doc/common/tables/cinder-hds-hus.xml:13(th) ./doc/common/tables/neutron-rabbitmq.xml:13(th) ./doc/common/tables/keystone-kvs.xml:13(th) ./doc/common/tables/trove-ssl.xml:13(th) ./doc/common/tables/keystone-policy.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml:12(th) ./doc/common/tables/swift-swift-swift-hash.xml:12(th) ./doc/common/tables/cinder-auth.xml:13(th) ./doc/common/tables/nova-kombu.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-formpost.xml:12(th) ./doc/common/tables/neutron-ml2_odl.xml:13(th) ./doc/common/tables/heat-quota.xml:13(th) ./doc/common/tables/nova-spice.xml:13(th) ./doc/common/tables/cinder-zoning_fabric.xml:13(th) ./doc/common/tables/neutron-midonet.xml:13(th) ./doc/common/tables/neutron-nvsd.xml:13(th) ./doc/common/tables/neutron-embrane_lb.xml:13(th) ./doc/common/tables/neutron-auth_token.xml:13(th) ./doc/common/tables/cinder-storwize.xml:13(th) ./doc/common/tables/nova-rootwrap.xml:13(th) ./doc/common/tables/cinder-solidfire.xml:13(th) ./doc/common/tables/keystone-revoke.xml:13(th) ./doc/common/tables/glance-ssl.xml:13(th) ./doc/common/tables/heat-metadata_api.xml:13(th) ./doc/common/tables/nova-apiv3.xml:13(th) ./doc/common/tables/glance-db.xml:13(th) ./doc/common/tables/neutron-vmware.xml:13(th) ./doc/common/tables/swift-container-sync-realms-realm2.xml:12(th) ./doc/common/tables/nova-api.xml:13(th) ./doc/common/tables/glance-matchmaker.xml:13(th) ./doc/common/tables/keystone-ssl.xml:13(th) ./doc/common/tables/swift-rsyncd-container.xml:12(th) ./doc/common/tables/cinder-san-solaris.xml:13(th) ./doc/common/tables/trove-heat.xml:13(th) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:13(th) ./doc/common/tables/swift-object-server-filter-healthcheck.xml:12(th) ./doc/common/tables/glance-paste.xml:13(th) ./doc/common/tables/nova-rdp.xml:13(th) ./doc/common/tables/neutron-quotas.xml:13(th) ./doc/common/tables/nova-rpc.xml:13(th) ./doc/common/tables/trove-guestagent.xml:13(th) ./doc/common/tables/nova-baremetal.xml:13(th) ./doc/common/tables/heat-clients_keystone.xml:13(th) ./doc/common/tables/swift-account-server-pipeline-main.xml:12(th) ./doc/common/tables/keystone-rabbit.xml:13(th) ./doc/common/tables/glance-api.xml:13(th) ./doc/common/tables/cinder-scheduler.xml:13(th) ./doc/common/tables/keystone-api.xml:13(th) ./doc/common/tables/neutron-ml2_ncs.xml:13(th) ./doc/common/tables/neutron-nec.xml:13(th) ./doc/common/tables/ceilometer-rabbitmq.xml:13(th) ./doc/common/tables/neutron-cadf.xml:13(th) ./doc/common/tables/neutron-testing.xml:13(th) ./doc/common/tables/swift-object-expirer-object-expirer.xml:12(th) ./doc/common/tables/glance-cinder.xml:13(th) ./doc/common/tables/nova-redis.xml:13(th) ./doc/common/tables/neutron-embrane.xml:13(th) ./doc/common/tables/swift-proxy-server-pipeline-main.xml:12(th) ./doc/common/tables/nova-upgrade_levels.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:12(th) ./doc/common/tables/ceilometer-inspector.xml:13(th) ./doc/common/tables/nova-rabbitmq.xml:13(th) ./doc/common/tables/heat-common.xml:13(th) ./doc/common/tables/keystone-federation.xml:13(th) ./doc/common/tables/cinder-zadara.xml:13(th) ./doc/common/tables/neutron-nuage.xml:13(th) ./doc/common/tables/swift-account-server-account-reaper.xml:12(th) ./doc/common/tables/ceilometer-ssl.xml:13(th) ./doc/common/tables/nova-quota.xml:13(th) ./doc/common/tables/nova-conductor.xml:13(th) ./doc/common/tables/nova-compute.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:12(th) ./doc/common/tables/cinder-storage_xen.xml:13(th) ./doc/common/tables/keystone-credential.xml:13(th) ./doc/common/tables/trove-amqp.xml:13(th) ./doc/common/tables/nova-xvpnvncproxy.xml:13(th)
+#: ./doc/common/tables/ceilometer-database.xml:13(th) ./doc/common/tables/neutron-openvswitch_agent.xml:13(th) ./doc/common/tables/heat-clients.xml:13(th) ./doc/common/tables/cinder-solidfire.xml:13(th) ./doc/common/tables/neutron-rpc.xml:13(th) ./doc/common/tables/trove-db_percona.xml:13(th) ./doc/common/tables/nova-periodic.xml:13(th) ./doc/common/tables/keystone-auth.xml:13(th) ./doc/common/tables/keystone-policy.xml:13(th) ./doc/common/tables/glance-auth_token.xml:13(th) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:13(th) ./doc/common/tables/swift-container-server-container-sync.xml:12(th) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:12(th) ./doc/common/tables/cinder-zoning_fabric.xml:13(th) ./doc/common/tables/ceilometer-redis.xml:13(th) ./doc/common/tables/cinder-storage_ceph.xml:13(th) ./doc/common/tables/ceilometer-vmware.xml:13(th) ./doc/common/tables/neutron-cisco.xml:13(th) ./doc/common/tables/nova-testing.xml:13(th) ./doc/common/tables/nova-metadata.xml:13(th) ./doc/common/tables/heat-clients_nova.xml:13(th) ./doc/common/tables/cinder-hp3par.xml:13(th) ./doc/common/tables/keystone-misc.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:12(th) ./doc/common/tables/neutron-scheduler.xml:13(th) ./doc/common/tables/glance-rbd.xml:13(th) ./doc/common/tables/cinder-storage_xen.xml:13(th) ./doc/common/tables/ceilometer-common.xml:13(th) ./doc/common/tables/cinder-database.xml:13(th) ./doc/common/tables/ceilometer-logging.xml:13(th) ./doc/common/tables/heat-common.xml:13(th) ./doc/common/tables/nova-ipv6.xml:13(th) ./doc/common/tables/nova-vnc.xml:13(th) ./doc/common/tables/trove-qpid.xml:13(th) ./doc/common/tables/keystone-api.xml:13(th) ./doc/common/tables/swift-object-expirer-pipeline-main.xml:12(th) ./doc/common/tables/swift-container-server-container-auditor.xml:12(th) ./doc/common/tables/glance-rpc.xml:13(th) ./doc/common/tables/neutron-policy.xml:13(th) ./doc/common/tables/nova-spice.xml:13(th) ./doc/common/tables/heat-clients_heat.xml:13(th) ./doc/common/tables/nova-xen.xml:13(th) ./doc/common/tables/trove-amqp.xml:13(th) ./doc/common/tables/glance-matchmaker.xml:13(th) ./doc/common/tables/nova-rabbitmq.xml:13(th) ./doc/common/tables/neutron-ml2_cisco.xml:13(th) ./doc/common/tables/nova-policy.xml:13(th) ./doc/common/tables/keystone-identity.xml:13(th) ./doc/common/tables/ceilometer-inspector.xml:13(th) ./doc/common/tables/cinder-scheduler.xml:13(th) ./doc/common/tables/trove-db_cassandra.xml:13(th) ./doc/common/tables/neutron-logging.xml:13(th) ./doc/common/tables/nova-availabilityzones.xml:13(th) ./doc/common/tables/keystone-catalog.xml:13(th) ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:13(th) ./doc/common/tables/neutron-rootwrap.xml:13(th) ./doc/common/tables/cinder-auth.xml:13(th) ./doc/common/tables/swift-swift-swift-constraints.xml:12(th) ./doc/common/tables/heat-qpid.xml:13(th) ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml:12(th) ./doc/common/tables/swift-proxy-server-filter-slo.xml:12(th) ./doc/common/tables/nova-zookeeper.xml:13(th) ./doc/common/tables/nova-keymgr.xml:13(th) ./doc/common/tables/neutron-auth_token.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-cache.xml:12(th) ./doc/common/tables/nova-ldap.xml:13(th) ./doc/common/tables/swift-container-server-filter-recon.xml:12(th) ./doc/common/tables/swift-proxy-server-pipeline-main.xml:12(th) ./doc/common/tables/ceilometer-auth.xml:13(th) ./doc/common/tables/cinder-quota.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml:12(th) ./doc/common/tables/keystone-os_inherit.xml:13(th) ./doc/common/tables/neutron-sdnve.xml:13(th) ./doc/common/tables/nova-compute.xml:13(th) ./doc/common/tables/keystone-rabbit.xml:13(th) ./doc/common/tables/cinder-backups_ceph.xml:13(th) ./doc/common/tables/nova-vmware.xml:13(th) ./doc/common/tables/heat-cfn_api.xml:13(th) ./doc/common/tables/neutron-vmware.xml:13(th) ./doc/common/tables/nova-rdp.xml:13(th) ./doc/common/tables/keystone-assignment.xml:13(th) ./doc/common/tables/nova-zeromq.xml:13(th) ./doc/common/tables/cinder-storage.xml:13(th) ./doc/common/tables/glance-registry.xml:13(th) ./doc/common/tables/neutron-embrane.xml:13(th) ./doc/common/tables/heat-quota.xml:13(th) ./doc/common/tables/swift-account-server-filter-healthcheck.xml:12(th) ./doc/common/tables/nova-common.xml:13(th) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:12(th) ./doc/common/tables/nova-volumes.xml:13(th) ./doc/common/tables/neutron-redis.xml:13(th) ./doc/common/tables/trove-db_mysql.xml:13(th) ./doc/common/tables/heat-zeromq.xml:13(th) ./doc/common/tables/heat-amqp.xml:13(th) ./doc/common/tables/neutron-linuxbridge_agent.xml:13(th) ./doc/common/tables/nova-redis.xml:13(th) ./doc/common/tables/swift-container-server-DEFAULT.xml:12(th) ./doc/common/tables/nova-db.xml:13(th) ./doc/common/tables/glance-rabbitmq.xml:13(th) ./doc/common/tables/neutron-l3_agent.xml:13(th) ./doc/common/tables/swift-container-server-pipeline-main.xml:12(th) ./doc/common/tables/glance-policy.xml:13(th) ./doc/common/tables/nova-neutron.xml:13(th) ./doc/common/tables/cinder-backups.xml:13(th) ./doc/common/tables/cinder-keymgr.xml:13(th) ./doc/common/tables/ceilometer-cells.xml:13(th) ./doc/common/tables/keystone-ldap.xml:13(th) ./doc/common/tables/glance-vmware.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml:12(th) ./doc/common/tables/cinder-zoning.xml:13(th) ./doc/common/tables/heat-notification.xml:13(th) ./doc/common/tables/swift-container-server-filter-healthcheck.xml:12(th) ./doc/common/tables/nova-vpn.xml:13(th) ./doc/common/tables/neutron-vpn.xml:13(th) ./doc/common/tables/swift-object-expirer-object-expirer.xml:12(th) ./doc/common/tables/trove-common.xml:13(th) ./doc/common/tables/trove-api.xml:13(th) ./doc/common/tables/cinder-zadara.xml:13(th) ./doc/common/tables/swift-object-server-filter-healthcheck.xml:12(th) ./doc/common/tables/nova-conductor.xml:13(th) ./doc/common/tables/swift-object-server-app-object-server.xml:12(th) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:12(th) ./doc/common/tables/nova-livemigration.xml:13(th) ./doc/common/tables/heat-rabbitmq.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:12(th) ./doc/common/tables/neutron-cadf.xml:13(th) ./doc/common/tables/keystone-amqp.xml:13(th) ./doc/common/tables/keystone-rpc.xml:13(th) ./doc/common/tables/swift-object-server-DEFAULT.xml:12(th) ./doc/common/tables/cinder-zones.xml:13(th) ./doc/common/tables/cinder-scality.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:12(th) ./doc/common/tables/neutron-agent.xml:13(th) ./doc/common/tables/cinder-emc.xml:13(th) ./doc/common/tables/cinder-vmware.xml:13(th) ./doc/common/tables/neutron-ml2_flat.xml:13(th) ./doc/common/tables/heat-metadata_api.xml:13(th) ./doc/common/tables/trove-rabbitmq.xml:13(th) ./doc/common/tables/nova-upgrade_levels.xml:13(th) ./doc/common/tables/neutron-kombu.xml:13(th) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:13(th) ./doc/common/tables/neutron-ml2_ofa.xml:13(th) ./doc/common/tables/glance-api.xml:13(th) ./doc/common/tables/heat-waitcondition_api.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:12(th) ./doc/common/tables/swift-rsyncd-container.xml:12(th) ./doc/common/tables/cinder-storwize.xml:13(th) ./doc/common/tables/cinder-hplefthand.xml:13(th) ./doc/common/tables/glance-s3.xml:13(th) ./doc/common/tables/nova-rootwrap.xml:13(th) ./doc/common/tables/heat-loadbalancer.xml:13(th) ./doc/common/tables/ceilometer-api.xml:13(th) ./doc/common/tables/ceilometer-exchange.xml:13(th) ./doc/common/tables/cinder-lvm.xml:13(th) ./doc/common/tables/trove-dns.xml:13(th) ./doc/common/tables/nova-cells.xml:13(th) ./doc/common/tables/trove-volume.xml:13(th) ./doc/common/tables/heat-auth_token.xml:13(th) ./doc/common/tables/neutron-quotas.xml:13(th) ./doc/common/tables/nova-auth_token.xml:13(th) ./doc/common/tables/cinder-storage_nfs.xml:13(th) ./doc/common/tables/heat-api.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:12(th) ./doc/common/tables/heat-clients_ceilometer.xml:13(th) ./doc/common/tables/neutron-ryu.xml:13(th) ./doc/common/tables/glance-logging.xml:13(th) ./doc/common/tables/swift-rsyncd-account.xml:12(th) ./doc/common/tables/neutron-metering_agent.xml:13(th) ./doc/common/tables/neutron-zeromq.xml:13(th) ./doc/common/tables/cinder-storage_glusterfs.xml:13(th) ./doc/common/tables/cinder-common.xml:13(th) ./doc/common/tables/glance-swift.xml:13(th) ./doc/common/tables/trove-quota.xml:13(th) ./doc/common/tables/cinder-auth_token.xml:13(th) ./doc/common/tables/ceilometer-alarm.xml:13(th) ./doc/common/tables/ceilometer-events.xml:13(th) ./doc/common/tables/cinder-xiv.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-name_check.xml:12(th) ./doc/common/tables/neutron-ml2_bigswitch.xml:13(th) ./doc/common/tables/nova-glance.xml:13(th) ./doc/common/tables/keystone-auth_token.xml:13(th) ./doc/common/tables/nova-s3.xml:13(th) ./doc/common/tables/nova-pci.xml:13(th) ./doc/common/tables/swift-account-server-filter-recon.xml:12(th) ./doc/common/tables/heat-clients_cinder.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:12(th) ./doc/common/tables/keystone-revoke.xml:13(th) ./doc/common/tables/cinder-api.xml:13(th) ./doc/common/tables/trove-db_couchbase.xml:13(th) ./doc/common/tables/heat-clients_trove.xml:13(th) ./doc/common/tables/swift-account-server-account-replicator.xml:12(th) ./doc/common/tables/neutron-plumgrid.xml:13(th) ./doc/common/tables/trove-heat.xml:13(th) ./doc/common/tables/glance-sheepdog.xml:13(th) ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml:12(th) ./doc/common/tables/cinder-windows.xml:13(th) ./doc/common/tables/cinder-san-solaris.xml:13(th) ./doc/common/tables/neutron-nuage.xml:13(th) ./doc/common/tables/keystone-zeromq.xml:13(th) ./doc/common/tables/neutron-bigswitch.xml:13(th) ./doc/common/tables/ceilometer-rpc.xml:13(th) ./doc/common/tables/swift-container-server-container-updater.xml:12(th) ./doc/common/tables/trove-db_mongodb.xml:13(th) ./doc/common/tables/swift-object-server-object-replicator.xml:12(th) ./doc/common/tables/glance-filesystem.xml:13(th) ./doc/common/tables/trove-rpc.xml:13(th) ./doc/common/tables/ceilometer-swift.xml:13(th) ./doc/common/tables/trove-backup.xml:13(th) ./doc/common/tables/nova-network.xml:13(th) ./doc/common/tables/glance-redis.xml:13(th) ./doc/common/tables/keystone-ssl.xml:13(th) ./doc/common/tables/nova-ca.xml:13(th) ./doc/common/tables/neutron-dhcp_agent.xml:13(th) ./doc/common/tables/ceilometer-collector.xml:13(th) ./doc/common/tables/cinder-hds-hus.xml:13(th) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:13(th) ./doc/common/tables/swift-swift-swift-hash.xml:12(th) ./doc/common/tables/neutron-ml2_gre.xml:13(th) ./doc/common/tables/neutron-varmour.xml:13(th) ./doc/common/tables/heat-debug.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-dlo.xml:12(th) ./doc/common/tables/nova-kombu.xml:13(th) ./doc/common/tables/trove-guestagent.xml:13(th) ./doc/common/tables/nova-qpid.xml:13(th) ./doc/common/tables/glance-qpid.xml:13(th) ./doc/common/tables/neutron-ml2_l2pop.xml:13(th) ./doc/common/tables/glance-amqp.xml:13(th) ./doc/common/tables/glance-zmq.xml:13(th) ./doc/common/tables/neutron-embrane_lb.xml:13(th) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:12(th) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:12(th) ./doc/common/tables/neutron-testing.xml:13(th) ./doc/common/tables/swift-object-server-pipeline-main.xml:12(th) ./doc/common/tables/swift-memcache-memcache.xml:12(th) ./doc/common/tables/swift-account-server-app-account-server.xml:12(th) ./doc/common/tables/swift-proxy-server-filter-formpost.xml:12(th) ./doc/common/tables/trove-compute.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:12(th) ./doc/common/tables/swift-object-expirer-filter-cache.xml:12(th) ./doc/common/tables/trove-db_redis.xml:13(th) ./doc/common/tables/cinder-rpc.xml:13(th) ./doc/common/tables/swift-container-sync-realms-realm2.xml:12(th) ./doc/common/tables/cinder-hpmsa.xml:13(th) ./doc/common/tables/nova-apiv3.xml:13(th) ./doc/common/tables/keystone-oauth.xml:13(th) ./doc/common/tables/cinder-storage_gpfs.xml:13(th) ./doc/common/tables/neutron-ml2_vlan.xml:13(th) ./doc/common/tables/keystone-notification.xml:13(th) ./doc/common/tables/swift-object-server-object-auditor.xml:12(th) ./doc/common/tables/trove-zeromq.xml:13(th) ./doc/common/tables/neutron-lbaas.xml:13(th) ./doc/common/tables/cinder-backups_swift.xml:13(th) ./doc/common/tables/trove-database.xml:13(th) ./doc/common/tables/swift-container-server-app-container-server.xml:12(th) ./doc/common/tables/nova-authentication.xml:13(th) ./doc/common/tables/neutron-nvsd.xml:13(th) ./doc/common/tables/swift-account-server-pipeline-main.xml:12(th) ./doc/common/tables/glance-gridfs.xml:13(th) ./doc/common/tables/neutron-notifier.xml:13(th) ./doc/common/tables/nova-rpc_all.xml:13(th) ./doc/common/tables/neutron-hyperv_agent.xml:13(th) ./doc/common/tables/keystone-federation.xml:13(th) ./doc/common/tables/nova-scheduling.xml:13(th) ./doc/common/tables/cinder-ssl.xml:13(th) ./doc/common/tables/trove-ssl.xml:13(th) ./doc/common/tables/cinder-eqlx.xml:13(th) ./doc/common/tables/heat-redis.xml:13(th) ./doc/common/tables/nova-ec2.xml:13(th) ./doc/common/tables/keystone-credential.xml:13(th) ./doc/common/tables/cinder-block-device.xml:13(th) ./doc/common/tables/neutron-metadata.xml:13(th) ./doc/common/tables/nova-fping.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-staticweb.xml:12(th) ./doc/common/tables/swift-container-server-container-replicator.xml:12(th) ./doc/common/tables/neutron-ml2_ncs.xml:13(th) ./doc/common/tables/neutron-ml2_arista.xml:13(th) ./doc/common/tables/nova-trustedcomputing.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:12(th) ./doc/common/tables/swift-object-expirer-app-proxy-server.xml:12(th) ./doc/common/tables/neutron-compute.xml:13(th) ./doc/common/tables/glance-imagecache.xml:13(th) ./doc/common/tables/neutron-ml2_brocade.xml:13(th) ./doc/common/tables/swift-account-server-account-auditor.xml:12(th) ./doc/common/tables/cinder-nas.xml:13(th) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:13(th) ./doc/common/tables/heat-clients_swift.xml:13(th) ./doc/common/tables/keystone-logging.xml:13(th) ./doc/common/tables/neutron-brocade.xml:13(th) ./doc/common/tables/neutron-ml2_odl.xml:13(th) ./doc/common/tables/swift-object-server-filter-recon.xml:12(th) ./doc/common/tables/cinder-connection.xml:13(th) ./doc/common/tables/heat-rpc.xml:13(th) ./doc/common/tables/trove-taskmanager.xml:13(th) ./doc/common/tables/heat-cloudwatch_api.xml:13(th) ./doc/common/tables/cinder-images.xml:13(th) ./doc/common/tables/cinder-huawei.xml:13(th) ./doc/common/tables/nova-console.xml:13(th) ./doc/common/tables/neutron-fwaas.xml:13(th) ./doc/common/tables/cinder-nexenta_nfs.xml:13(th) ./doc/common/tables/nova-quota.xml:13(th) ./doc/common/tables/heat-logging.xml:13(th) ./doc/common/tables/trove-redis.xml:13(th) ./doc/common/tables/keystone-stats.xml:13(th) ./doc/common/tables/heat-crypt.xml:13(th) ./doc/common/tables/neutron-ssl.xml:13(th) ./doc/common/tables/neutron-midonet.xml:13(th) ./doc/common/tables/cinder-coraid.xml:13(th) ./doc/common/tables/neutron-wsgi.xml:13(th) ./doc/common/tables/cinder-compute.xml:13(th) ./doc/common/tables/swift-rsyncd-object.xml:12(th) ./doc/common/tables/glance-wsgi.xml:13(th) ./doc/common/tables/swift-drive-audit-drive-audit.xml:12(th) ./doc/common/tables/nova-baremetal.xml:13(th) ./doc/common/tables/neutron-qpid.xml:13(th) ./doc/common/tables/nova-rpc.xml:13(th) ./doc/common/tables/cinder-backups_tsm.xml:13(th) ./doc/common/tables/cinder-san.xml:13(th) ./doc/common/tables/nova-logging.xml:13(th) ./doc/common/tables/neutron-nec.xml:13(th) ./doc/common/tables/keystone-security.xml:13(th) ./doc/common/tables/heat-clients_neutron.xml:13(th) ./doc/common/tables/nova-api.xml:13(th) ./doc/common/tables/neutron-ml2_mlnx.xml:13(th) ./doc/common/tables/trove-auth_token.xml:13(th) ./doc/common/tables/keystone-trust.xml:13(th) ./doc/common/tables/glance-cinder.xml:13(th) ./doc/common/tables/swift-object-server-object-updater.xml:12(th) ./doc/common/tables/glance-common.xml:13(th) ./doc/common/tables/neutron-ml2_vxlan.xml:13(th) ./doc/common/tables/swift-dispersion-dispersion.xml:12(th) ./doc/common/tables/swift-account-server-DEFAULT.xml:12(th) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:12(th) ./doc/common/tables/trove-nova.xml:13(th) ./doc/common/tables/neutron-meta.xml:13(th) ./doc/common/tables/neutron-rabbitmq.xml:13(th) ./doc/common/tables/keystone-ec2.xml:13(th) ./doc/common/tables/heat-clients_keystone.xml:13(th) ./doc/common/tables/neutron-api.xml:13(th) ./doc/common/tables/trove-logging.xml:13(th) ./doc/common/tables/glance-db.xml:13(th) ./doc/common/tables/keystone-kvs.xml:13(th) ./doc/common/tables/keystone-redis.xml:13(th) ./doc/common/tables/nova-xvpnvncproxy.xml:13(th) ./doc/common/tables/glance-paste.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml:12(th) ./doc/common/tables/swift-account-server-account-reaper.xml:12(th) ./doc/common/tables/nova-hyperv.xml:13(th) ./doc/common/tables/swift-proxy-server-filter-container_sync.xml:12(th) ./doc/common/tables/heat-clients_backends.xml:13(th) ./doc/common/tables/glance-testing.xml:13(th) ./doc/common/tables/neutron-common.xml:13(th) ./doc/common/tables/nova-hypervisor.xml:13(th) ./doc/common/tables/keystone-qpid.xml:13(th) ./doc/common/tables/swift-container-sync-realms-realm1.xml:12(th) ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml:12(th) ./doc/common/tables/nova-wsgi.xml:13(th) ./doc/common/tables/keystone-cache.xml:13(th) ./doc/common/tables/nova-configdrive.xml:13(th) ./doc/common/tables/keystone-token.xml:13(th) ./doc/common/tables/ceilometer-ssl.xml:13(th) ./doc/common/tables/ceilometer-qpid.xml:13(th) ./doc/common/tables/heat-database.xml:13(th) ./doc/common/tables/ceilometer-rabbitmq.xml:13(th) ./doc/common/tables/neutron-ml2.xml:13(th) ./doc/common/tables/neutron-db.xml:13(th) ./doc/common/tables/keystone-database.xml:13(th) ./doc/common/tables/keystone-memcache.xml:13(th) ./doc/common/tables/trove-debug.xml:13(th) ./doc/common/tables/trove-swift.xml:13(th) ./doc/common/tables/nova-tilera.xml:13(th) ./doc/common/tables/nova-libvirt.xml:13(th) ./doc/common/tables/neutron-mlnx.xml:13(th) ./doc/common/tables/cinder-zoning_manager.xml:13(th) ./doc/common/tables/ceilometer-amqp.xml:13(th) ./doc/common/tables/glance-ssl.xml:13(th) ./doc/common/tables/neutron-securitygroups.xml:13(th) ./doc/common/tables/keystone-debug.xml:13(th) ./doc/common/tables/cinder-rootwrap.xml:13(th) ./doc/common/tables/cinder-nexenta_iscsi.xml:13(th)
 msgid "Configuration option = Default value"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:19(th) ./doc/common/tables/nova-rpc_all.xml:198(th) ./doc/common/tables/ceilometer-cells.xml:19(th) ./doc/common/tables/nova-db.xml:26(th) ./doc/common/tables/nova-scheduling.xml:118(th) ./doc/common/tables/nova-rpc.xml:62(th) ./doc/common/tables/nova-upgrade_levels.xml:19(th) ./doc/common/tables/nova-quota.xml:82(th)
-msgid "[cells]"
+#: ./doc/common/tables/ceilometer-database.xml:22(td)
+msgid "database_connection = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:22(td) ./doc/common/tables/ceilometer-cells.xml:26(td)
-msgid "call_timeout = 60"
+#: ./doc/common/tables/ceilometer-database.xml:23(td)
+msgid "(StrOpt) DEPRECATED - Database connection string."
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:23(td) ./doc/common/tables/ceilometer-cells.xml:27(td)
-msgid "(IntOpt) Seconds to wait for response from a call to a cell."
+#: ./doc/common/tables/ceilometer-database.xml:26(td)
+msgid "mysql_engine = InnoDB"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:26(td) ./doc/common/tables/ceilometer-cells.xml:30(td)
-msgid "capabilities = hypervisor=xenserver;kvm, os=linux;windows"
+#: ./doc/common/tables/ceilometer-database.xml:27(td)
+msgid "(StrOpt) MySQL engine to use."
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:27(td) ./doc/common/tables/ceilometer-cells.xml:31(td)
-msgid "(ListOpt) Key/Multi-value list with the capabilities of the cell"
+#: ./doc/common/tables/ceilometer-database.xml:30(td)
+msgid "sqlite_db = ceilometer.sqlite"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:30(td) ./doc/common/tables/ceilometer-cells.xml:34(td)
-msgid "cell_type = compute"
+#: ./doc/common/tables/ceilometer-database.xml:31(td) ./doc/common/tables/nova-db.xml:105(td) ./doc/common/tables/glance-db.xml:87(td) ./doc/common/tables/neutron-db.xml:23(td) ./doc/common/tables/keystone-database.xml:87(td)
+msgid "(StrOpt) The file name to use with SQLite"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:31(td) ./doc/common/tables/ceilometer-cells.xml:35(td)
-msgid "(StrOpt) Type of cell: api or compute"
+#: ./doc/common/tables/ceilometer-database.xml:34(td) ./doc/common/tables/nova-db.xml:108(td) ./doc/common/tables/cinder-common.xml:170(td) ./doc/common/tables/glance-db.xml:90(td) ./doc/common/tables/heat-database.xml:30(td) ./doc/common/tables/neutron-db.xml:26(td) ./doc/common/tables/keystone-database.xml:90(td)
+msgid "sqlite_synchronous = True"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:34(td)
-msgid "cells_config = None"
+#: ./doc/common/tables/ceilometer-database.xml:35(td) ./doc/common/tables/nova-db.xml:109(td) ./doc/common/tables/glance-db.xml:91(td) ./doc/common/tables/neutron-db.xml:27(td) ./doc/common/tables/keystone-database.xml:91(td)
+msgid "(BoolOpt) If True, SQLite uses synchronous mode"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:35(td)
-msgid "(StrOpt) Configuration file from which to read cells configuration. If given, overrides reading cells from the database."
+#: ./doc/common/tables/ceilometer-database.xml:41(td) ./doc/common/tables/cinder-storage.xml:137(td) ./doc/common/tables/nova-db.xml:36(td) ./doc/common/tables/glance-db.xml:22(td) ./doc/common/tables/heat-database.xml:37(td) ./doc/common/tables/neutron-db.xml:33(td) ./doc/common/tables/keystone-database.xml:22(td)
+msgid "backend = sqlalchemy"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:38(td)
-msgid "driver = nova.cells.rpc_driver.CellsRPCDriver"
+#: ./doc/common/tables/ceilometer-database.xml:42(td) ./doc/common/tables/cinder-database.xml:23(td) ./doc/common/tables/cinder-storage.xml:138(td) ./doc/common/tables/nova-db.xml:37(td) ./doc/common/tables/glance-db.xml:23(td) ./doc/common/tables/heat-database.xml:38(td) ./doc/common/tables/neutron-db.xml:34(td) ./doc/common/tables/keystone-database.xml:23(td)
+msgid "(StrOpt) The backend to use for db"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:39(td)
-msgid "(StrOpt) Cells communication driver to use"
+#: ./doc/common/tables/ceilometer-database.xml:45(td)
+msgid "connection = sqlite:////usr/lib/python/site-packages/ceilometer/openstack/common/db/$sqlite_db"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:42(td) ./doc/common/tables/ceilometer-cells.xml:38(td) ./doc/common/tables/keystone-ssl.xml:77(td)
-msgid "enable = False"
+#: ./doc/common/tables/ceilometer-database.xml:46(td) ./doc/common/tables/nova-db.xml:41(td) ./doc/common/tables/cinder-connection.xml:23(td) ./doc/common/tables/glance-db.xml:27(td) ./doc/common/tables/heat-database.xml:42(td) ./doc/common/tables/neutron-db.xml:38(td) ./doc/common/tables/keystone-database.xml:27(td)
+msgid "(StrOpt) The SQLAlchemy connection string used to connect to the database"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:43(td) ./doc/common/tables/ceilometer-cells.xml:39(td)
-msgid "(BoolOpt) Enable cell functionality"
+#: ./doc/common/tables/ceilometer-database.xml:49(td) ./doc/common/tables/nova-db.xml:44(td) ./doc/common/tables/cinder-connection.xml:26(td) ./doc/common/tables/glance-db.xml:30(td) ./doc/common/tables/heat-database.xml:45(td) ./doc/common/tables/neutron-db.xml:41(td) ./doc/common/tables/keystone-database.xml:30(td)
+msgid "connection_debug = 0"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:46(td)
-msgid "instance_update_num_instances = 1"
+#: ./doc/common/tables/ceilometer-database.xml:50(td) ./doc/common/tables/nova-db.xml:45(td) ./doc/common/tables/cinder-connection.xml:27(td) ./doc/common/tables/glance-db.xml:31(td) ./doc/common/tables/heat-database.xml:46(td) ./doc/common/tables/neutron-db.xml:42(td) ./doc/common/tables/keystone-database.xml:31(td)
+msgid "(IntOpt) Verbosity of SQL debugging information. 0=None, 100=Everything"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:47(td)
-msgid "(IntOpt) Number of instances to update per periodic task run"
+#: ./doc/common/tables/ceilometer-database.xml:53(td) ./doc/common/tables/nova-db.xml:48(td) ./doc/common/tables/cinder-connection.xml:30(td) ./doc/common/tables/glance-db.xml:34(td) ./doc/common/tables/heat-database.xml:49(td) ./doc/common/tables/neutron-db.xml:45(td) ./doc/common/tables/keystone-database.xml:34(td)
+msgid "connection_trace = False"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:50(td)
-msgid "instance_updated_at_threshold = 3600"
+#: ./doc/common/tables/ceilometer-database.xml:54(td) ./doc/common/tables/nova-db.xml:49(td) ./doc/common/tables/cinder-connection.xml:31(td) ./doc/common/tables/glance-db.xml:35(td) ./doc/common/tables/heat-database.xml:50(td) ./doc/common/tables/neutron-db.xml:46(td) ./doc/common/tables/keystone-database.xml:35(td)
+msgid "(BoolOpt) Add python stack traces to SQL as comment strings"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:51(td)
-msgid "(IntOpt) Number of seconds after an instance was updated or deleted to continue to update cells"
+#: ./doc/common/tables/ceilometer-database.xml:57(td) ./doc/common/tables/nova-db.xml:68(td) ./doc/common/tables/cinder-common.xml:229(td) ./doc/common/tables/glance-db.xml:54(td) ./doc/common/tables/heat-database.xml:53(td) ./doc/common/tables/neutron-db.xml:65(td) ./doc/common/tables/keystone-database.xml:54(td)
+msgid "idle_timeout = 3600"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:54(td) ./doc/common/tables/ceilometer-cells.xml:42(td)
-msgid "manager = nova.cells.manager.CellsManager"
+#: ./doc/common/tables/ceilometer-database.xml:58(td) ./doc/common/tables/nova-db.xml:69(td) ./doc/common/tables/glance-db.xml:55(td) ./doc/common/tables/neutron-db.xml:66(td) ./doc/common/tables/keystone-database.xml:55(td)
+msgid "(IntOpt) Timeout before idle sql connections are reaped"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:55(td) ./doc/common/tables/ceilometer-cells.xml:43(td)
-msgid "(StrOpt) Manager for cells"
+#: ./doc/common/tables/ceilometer-database.xml:61(td) ./doc/common/tables/cinder-storage.xml:141(td) ./doc/common/tables/nova-db.xml:72(td) ./doc/common/tables/glance-db.xml:58(td) ./doc/common/tables/heat-database.xml:57(td) ./doc/common/tables/keystone-database.xml:58(td)
+msgid "max_overflow = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:58(td)
-msgid "max_hop_count = 10"
+#: ./doc/common/tables/ceilometer-database.xml:62(td) ./doc/common/tables/cinder-storage.xml:142(td) ./doc/common/tables/nova-db.xml:73(td) ./doc/common/tables/glance-db.xml:59(td) ./doc/common/tables/heat-database.xml:58(td) ./doc/common/tables/neutron-db.xml:70(td) ./doc/common/tables/keystone-database.xml:59(td)
+msgid "(IntOpt) If set, use this value for max_overflow with sqlalchemy"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:59(td)
-msgid "(IntOpt) Maximum number of hops for cells routing."
+#: ./doc/common/tables/ceilometer-database.xml:65(td) ./doc/common/tables/nova-db.xml:76(td) ./doc/common/tables/glance-db.xml:62(td) ./doc/common/tables/heat-database.xml:61(td) ./doc/common/tables/keystone-database.xml:62(td)
+msgid "max_pool_size = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:62(td) ./doc/common/tables/ceilometer-cells.xml:46(td)
-msgid "mute_child_interval = 300"
+#: ./doc/common/tables/ceilometer-database.xml:66(td) ./doc/common/tables/cinder-storage.xml:146(td) ./doc/common/tables/nova-db.xml:77(td) ./doc/common/tables/glance-db.xml:63(td) ./doc/common/tables/heat-database.xml:62(td) ./doc/common/tables/neutron-db.xml:74(td) ./doc/common/tables/keystone-database.xml:63(td)
+msgid "(IntOpt) Maximum number of SQL connections to keep open in a pool"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:63(td) ./doc/common/tables/ceilometer-cells.xml:47(td)
-msgid "(IntOpt) Number of seconds after which a lack of capability and capacity updates signals the child cell is to be treated as a mute."
+#: ./doc/common/tables/ceilometer-database.xml:69(td) ./doc/common/tables/cinder-storage.xml:149(td) ./doc/common/tables/nova-db.xml:80(td) ./doc/common/tables/glance-db.xml:66(td) ./doc/common/tables/heat-database.xml:65(td) ./doc/common/tables/neutron-db.xml:77(td) ./doc/common/tables/keystone-database.xml:66(td)
+msgid "max_retries = 10"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:66(td)
-msgid "mute_weight_multiplier = -10.0"
+#: ./doc/common/tables/ceilometer-database.xml:70(td) ./doc/common/tables/nova-db.xml:81(td) ./doc/common/tables/glance-db.xml:67(td) ./doc/common/tables/neutron-db.xml:78(td) ./doc/common/tables/keystone-database.xml:67(td)
+msgid "(IntOpt) Maximum db connection retries during startup. (setting -1 implies an infinite retry count)"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:67(td)
-msgid "(FloatOpt) Multiplier used to weigh mute children. (The value should be negative.)"
+#: ./doc/common/tables/ceilometer-database.xml:73(td) ./doc/common/tables/cinder-storage.xml:153(td) ./doc/common/tables/nova-db.xml:84(td) ./doc/common/tables/glance-db.xml:70(td) ./doc/common/tables/heat-database.xml:69(td) ./doc/common/tables/neutron-db.xml:81(td) ./doc/common/tables/keystone-database.xml:70(td)
+msgid "min_pool_size = 1"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:70(td)
-msgid "mute_weight_value = 1000.0"
+#: ./doc/common/tables/ceilometer-database.xml:74(td) ./doc/common/tables/cinder-storage.xml:154(td) ./doc/common/tables/nova-db.xml:85(td) ./doc/common/tables/glance-db.xml:71(td) ./doc/common/tables/heat-database.xml:70(td) ./doc/common/tables/neutron-db.xml:82(td) ./doc/common/tables/keystone-database.xml:71(td)
+msgid "(IntOpt) Minimum number of SQL connections to keep open in a pool"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:71(td)
-msgid "(FloatOpt) Weight value assigned to mute children. (The value should be positive.)"
+#: ./doc/common/tables/ceilometer-database.xml:77(td) ./doc/common/tables/nova-db.xml:92(td) ./doc/common/tables/glance-db.xml:78(td) ./doc/common/tables/heat-database.xml:73(td) ./doc/common/tables/keystone-database.xml:78(td)
+msgid "pool_timeout = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:74(td) ./doc/common/tables/ceilometer-cells.xml:50(td)
-msgid "name = nova"
+#: ./doc/common/tables/ceilometer-database.xml:78(td) ./doc/common/tables/nova-db.xml:93(td) ./doc/common/tables/glance-db.xml:79(td) ./doc/common/tables/heat-database.xml:74(td) ./doc/common/tables/neutron-db.xml:86(td) ./doc/common/tables/keystone-database.xml:79(td)
+msgid "(IntOpt) If set, use this value for pool_timeout with sqlalchemy"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:75(td) ./doc/common/tables/ceilometer-cells.xml:51(td)
-msgid "(StrOpt) Name of this cell"
+#: ./doc/common/tables/ceilometer-database.xml:81(td) ./doc/common/tables/nova-db.xml:96(td) ./doc/common/tables/cinder-common.xml:233(td) ./doc/common/tables/glance-db.xml:82(td) ./doc/common/tables/heat-database.xml:77(td) ./doc/common/tables/neutron-db.xml:89(td) ./doc/common/tables/keystone-database.xml:82(td)
+msgid "retry_interval = 10"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:78(td)
-msgid "offset_weight_multiplier = 1.0"
+#: ./doc/common/tables/ceilometer-database.xml:82(td) ./doc/common/tables/nova-db.xml:97(td) ./doc/common/tables/glance-db.xml:83(td) ./doc/common/tables/neutron-db.xml:90(td) ./doc/common/tables/keystone-database.xml:83(td)
+msgid "(IntOpt) Interval between retries of opening a sql connection"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:79(td)
-msgid "(FloatOpt) Multiplier used to weigh offset weigher."
+#: ./doc/common/tables/ceilometer-database.xml:85(td) ./doc/common/tables/heat-database.xml:81(td) ./doc/common/tables/neutron-db.xml:93(td)
+msgid "slave_connection ="
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:82(td) ./doc/common/tables/ceilometer-cells.xml:54(td)
-msgid "reserve_percent = 10.0"
+#: ./doc/common/tables/ceilometer-database.xml:86(td) ./doc/common/tables/nova-db.xml:101(td) ./doc/common/tables/heat-database.xml:82(td) ./doc/common/tables/neutron-db.xml:94(td)
+msgid "(StrOpt) The SQLAlchemy connection string used to connect to the slave database"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:83(td) ./doc/common/tables/ceilometer-cells.xml:55(td)
-msgid "(FloatOpt) Percentage of cell capacity to hold in reserve. Affects both memory and disk utilization"
+#: ./doc/common/tables/ceilometer-database.xml:89(td)
+msgid "time_to_live = -1"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:86(td) ./doc/common/tables/ceilometer-cells.xml:58(td)
-msgid "topic = cells"
+#: ./doc/common/tables/ceilometer-database.xml:90(td)
+msgid "(IntOpt) Number of seconds that samples are kept in the database for (&lt;= 0 means forever)."
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml:87(td) ./doc/common/tables/ceilometer-cells.xml:59(td)
-msgid "(StrOpt) The topic cells nodes listen on"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:8(caption)
+msgid "Description of configuration options for openvswitch_agent"
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml:8(caption)
-msgid "Description of configuration options for db_mongodb"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:22(td)
+msgid "ovs_integration_bridge = br-int"
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml:19(th)
-msgid "[mongodb]"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:23(td)
+msgid "(StrOpt) Name of Open vSwitch bridge to use"
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml:22(td) ./doc/common/tables/trove-db_cassandra.xml:22(td) ./doc/common/tables/trove-db_redis.xml:22(td) ./doc/common/tables/trove-db_couchbase.xml:22(td)
-msgid "backup_strategy = None"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:26(td)
+msgid "ovs_use_veth = False"
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml:23(td) ./doc/common/tables/trove-backup.xml:51(td) ./doc/common/tables/trove-db_cassandra.xml:23(td) ./doc/common/tables/trove-db_mysql.xml:23(td) ./doc/common/tables/trove-db_redis.xml:23(td) ./doc/common/tables/trove-db_couchbase.xml:23(td) ./doc/common/tables/trove-db_percona.xml:23(td)
-msgid "(StrOpt) Default strategy to perform backups."
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:27(td)
+msgid "(BoolOpt) Uses veth for an interface or not"
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml:26(td)
-msgid "mount_point = /var/lib/mongodb"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:30(td)
+msgid "ovs_vsctl_timeout = 10"
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml:27(td) ./doc/common/tables/trove-db_cassandra.xml:27(td) ./doc/common/tables/trove-db_mysql.xml:27(td) ./doc/common/tables/trove-db_redis.xml:27(td) ./doc/common/tables/trove-db_couchbase.xml:27(td) ./doc/common/tables/trove-db_percona.xml:27(td)
-msgid "(StrOpt) Filesystem path for mounting volumes if volume support is enabled"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:31(td)
+msgid "(IntOpt) Timeout in seconds for ovs-vsctl commands"
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml:30(td)
-msgid "tcp_ports = 2500, 27017"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:34(th) ./doc/common/tables/neutron-rpc.xml:66(th) ./doc/common/tables/neutron-ml2_ofa.xml:34(th) ./doc/common/tables/neutron-metering_agent.xml:30(th) ./doc/common/tables/neutron-nvsd.xml:19(th) ./doc/common/tables/neutron-hyperv_agent.xml:19(th) ./doc/common/tables/neutron-common.xml:182(th)
+msgid "[AGENT]"
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml:31(td) ./doc/common/tables/trove-db_cassandra.xml:31(td) ./doc/common/tables/trove-db_mysql.xml:35(td) ./doc/common/tables/trove-db_redis.xml:31(td) ./doc/common/tables/trove-db_couchbase.xml:31(td) ./doc/common/tables/trove-db_percona.xml:35(td)
-msgid "(ListOpt) List of TCP ports and/or port ranges to open in the security group (only applicable if trove_security_groups_support is True)"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:37(td) ./doc/common/tables/neutron-linuxbridge_agent.xml:44(td)
+msgid "l2_population = False"
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml:34(td) ./doc/common/tables/trove-db_cassandra.xml:34(td) ./doc/common/tables/trove-db_mysql.xml:38(td) ./doc/common/tables/trove-db_redis.xml:34(td) ./doc/common/tables/trove-db_couchbase.xml:34(td) ./doc/common/tables/trove-db_percona.xml:38(td)
-msgid "udp_ports ="
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:38(td)
+msgid "(BoolOpt) Use ml2 l2population mechanism driver to learn remote mac and IPs and improve tunnel scalability"
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml:35(td)
-msgid "(ListOpt) List of UPD ports and/or port ranges to open in the security group (only applicable if trove_security_groups_support is True)"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:41(td)
+msgid "minimize_polling = True"
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml:38(td) ./doc/common/tables/trove-db_redis.xml:38(td) ./doc/common/tables/trove-db_couchbase.xml:38(td) ./doc/common/tables/trove-db_percona.xml:42(td)
-msgid "usage_timeout = 450"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:42(td)
+msgid "(BoolOpt) Minimize polling by monitoring ovsdb for interface changes."
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml:39(td) ./doc/common/tables/trove-db_cassandra.xml:39(td) ./doc/common/tables/trove-db_mysql.xml:43(td) ./doc/common/tables/trove-db_redis.xml:39(td) ./doc/common/tables/trove-db_couchbase.xml:39(td) ./doc/common/tables/trove-db_percona.xml:43(td)
-msgid "(IntOpt) Timeout to wait for a guest to become active."
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:45(td)
+msgid "ovsdb_monitor_respawn_interval = 30"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml:8(caption) ./doc/common/tables/trove-debug.xml:8(caption) ./doc/common/tables/heat-debug.xml:8(caption)
-msgid "Description of configuration options for debug"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:46(td)
+msgid "(IntOpt) The number of seconds to wait before respawning the ovsdb monitor after losing communication with it"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml:22(td) ./doc/common/tables/nova-testing.xml:26(td) ./doc/common/tables/trove-debug.xml:22(td) ./doc/common/tables/cinder-api.xml:30(td) ./doc/common/tables/glance-wsgi.xml:22(td) ./doc/common/tables/heat-debug.xml:22(td) ./doc/common/tables/ceilometer-common.xml:22(td) ./doc/common/tables/neutron-testing.xml:22(td)
-msgid "backdoor_port = None"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:49(td)
+msgid "tunnel_types ="
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml:23(td) ./doc/common/tables/trove-debug.xml:23(td) ./doc/common/tables/cinder-api.xml:31(td) ./doc/common/tables/heat-debug.xml:23(td) ./doc/common/tables/ceilometer-common.xml:23(td) ./doc/common/tables/neutron-testing.xml:23(td)
-msgid "(StrOpt) Enable eventlet backdoor. Acceptable values are 0, &lt;port&gt;, and &lt;start&gt;:&lt;end&gt;, where 0 results in listening on a random tcp port number; &lt;port&gt; results in listening on the specified port number (and not enabling backdoor if that port is in use); and &lt;start&gt;:&lt;end&gt; results in listening on the smallest unused port number within the specified range of port numbers. The chosen port is displayed in the service's log file."
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:50(td)
+msgid "(ListOpt) Network types supported by the agent (gre and/or vxlan)"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml:26(td) ./doc/common/tables/trove-debug.xml:30(td) ./doc/common/tables/glance-logging.xml:22(td) ./doc/common/tables/ceilometer-logging.xml:22(td) ./doc/common/tables/heat-debug.xml:26(td) ./doc/common/tables/neutron-logging.xml:22(td) ./doc/common/tables/nova-logging.xml:22(td) ./doc/common/tables/cinder-common.xml:26(td)
-msgid "debug = False"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:53(td)
+msgid "veth_mtu = None"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml:27(td) ./doc/common/tables/trove-debug.xml:31(td) ./doc/common/tables/glance-logging.xml:23(td) ./doc/common/tables/ceilometer-logging.xml:23(td) ./doc/common/tables/heat-debug.xml:27(td) ./doc/common/tables/neutron-logging.xml:23(td) ./doc/common/tables/nova-logging.xml:23(td) ./doc/common/tables/cinder-common.xml:27(td)
-msgid "(BoolOpt) Print debugging output (set logging level to DEBUG instead of default WARNING level)."
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:54(td)
+msgid "(IntOpt) MTU size of veth interfaces"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml:30(td) ./doc/common/tables/neutron-common.xml:122(td) ./doc/common/tables/nova-common.xml:38(td) ./doc/common/tables/trove-debug.xml:34(td) ./doc/common/tables/heat-debug.xml:30(td) ./doc/common/tables/glance-common.xml:46(td) ./doc/common/tables/cinder-common.xml:42(td) ./doc/common/tables/ceilometer-common.xml:26(td)
-msgid "disable_process_locking = False"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:57(td)
+msgid "vxlan_udp_port = 4789"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml:31(td) ./doc/common/tables/neutron-common.xml:123(td) ./doc/common/tables/nova-common.xml:39(td) ./doc/common/tables/trove-debug.xml:35(td) ./doc/common/tables/heat-debug.xml:31(td) ./doc/common/tables/glance-common.xml:47(td) ./doc/common/tables/cinder-common.xml:43(td)
-msgid "(BoolOpt) Whether to disable inter-process locks"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:58(td)
+msgid "(IntOpt) The UDP port to use for VXLAN tunnels."
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml:34(td) ./doc/common/tables/trove-debug.xml:38(td) ./doc/common/tables/glance-logging.xml:30(td) ./doc/common/tables/heat-debug.xml:34(td) ./doc/common/tables/neutron-logging.xml:30(td) ./doc/common/tables/nova-logging.xml:30(td) ./doc/common/tables/cinder-common.xml:50(td) ./doc/common/tables/ceilometer-common.xml:30(td)
-msgid "fatal_deprecations = False"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:61(th) ./doc/common/tables/neutron-cisco.xml:54(th)
+msgid "[CISCO_N1K]"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml:35(td) ./doc/common/tables/glance-logging.xml:31(td) ./doc/common/tables/cinder-common.xml:51(td) ./doc/common/tables/ceilometer-common.xml:31(td)
-msgid "(BoolOpt) Make deprecations fatal"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:64(td)
+msgid "local_ip = 10.0.0.3"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml:38(td) ./doc/common/tables/trove-logging.xml:74(td) ./doc/common/tables/heat-notification.xml:26(td) ./doc/common/tables/cinder-rpc.xml:90(td) ./doc/common/tables/glance-logging.xml:78(td) ./doc/common/tables/ceilometer-logging.xml:78(td) ./doc/common/tables/neutron-logging.xml:78(td) ./doc/common/tables/nova-logging.xml:82(td)
-msgid "publish_errors = False"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:65(td)
+msgid "(StrOpt) N1K Local IP"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml:39(td) ./doc/common/tables/cinder-rpc.xml:91(td) ./doc/common/tables/glance-logging.xml:79(td) ./doc/common/tables/ceilometer-logging.xml:79(td)
-msgid "(BoolOpt) Publish error events"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:68(th) ./doc/common/tables/neutron-ryu.xml:19(th)
+msgid "[OVS]"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml:42(td) ./doc/common/tables/trove-debug.xml:46(td)
-msgid "pydev_debug_host = None"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:71(td) ./doc/common/tables/neutron-cisco.xml:57(td)
+msgid "bridge_mappings ="
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml:43(td)
-msgid "(StrOpt) Host to connect to for remote debugger."
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:72(td)
+msgid "(ListOpt) List of &lt;physical_network&gt;:&lt;bridge&gt;"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml:46(td) ./doc/common/tables/trove-debug.xml:50(td)
-msgid "pydev_debug_port = None"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:75(td)
+msgid "enable_tunneling = False"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml:47(td)
-msgid "(IntOpt) Port to connect to for remote debugger."
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:76(td)
+msgid "(BoolOpt) Enable tunneling support"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml:50(td)
-msgid "standard_threads = False"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:79(td)
+msgid "int_peer_patch_port = patch-tun"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml:51(td)
-msgid "(BoolOpt) Do not monkey-patch threading system modules."
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:80(td)
+msgid "(StrOpt) Peer patch port in integration bridge for tunnel bridge"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml:54(th) ./doc/common/tables/ceilometer-logging.xml:102(th) ./doc/common/tables/neutron-cadf.xml:19(th)
-msgid "[audit]"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:83(td) ./doc/common/tables/neutron-cisco.xml:73(td) ./doc/common/tables/nova-vmware.xml:46(td) ./doc/common/tables/neutron-ml2_bigswitch.xml:140(td) ./doc/common/tables/neutron-bigswitch.xml:140(td) ./doc/common/tables/neutron-nvsd.xml:22(td)
+msgid "integration_bridge = br-int"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml:57(td) ./doc/common/tables/ceilometer-logging.xml:109(td) ./doc/common/tables/neutron-cadf.xml:26(td)
-msgid "namespace = openstack"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:84(td) ./doc/common/tables/neutron-sdnve.xml:43(td)
+msgid "(StrOpt) Integration bridge to use"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml:58(td) ./doc/common/tables/ceilometer-logging.xml:110(td) ./doc/common/tables/neutron-cadf.xml:27(td)
-msgid "(StrOpt) namespace prefix for generated id"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:87(td) ./doc/common/tables/neutron-linuxbridge_agent.xml:48(td)
+msgid "local_ip ="
 msgstr ""
 
-#: ./doc/common/tables/glance-policy.xml:8(caption) ./doc/common/tables/nova-policy.xml:8(caption) ./doc/common/tables/neutron-policy.xml:8(caption) ./doc/common/tables/keystone-policy.xml:8(caption)
-msgid "Description of configuration options for policy"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:88(td)
+msgid "(StrOpt) Local IP address of GRE tunnel endpoints."
 msgstr ""
 
-#: ./doc/common/tables/glance-policy.xml:22(td) ./doc/common/tables/nova-policy.xml:58(td) ./doc/common/tables/ceilometer-api.xml:34(td) ./doc/common/tables/cinder-common.xml:138(td) ./doc/common/tables/heat-api.xml:42(td) ./doc/common/tables/keystone-policy.xml:22(td)
-msgid "policy_default_rule = default"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:91(td) ./doc/common/tables/neutron-linuxbridge_agent.xml:29(td) ./doc/common/tables/neutron-ml2_vlan.xml:22(td) ./doc/common/tables/neutron-hyperv_agent.xml:45(td)
+msgid "network_vlan_ranges ="
 msgstr ""
 
-#: ./doc/common/tables/glance-policy.xml:23(td)
-msgid "(StrOpt) The default policy to use."
-msgstr ""
-
-#: ./doc/common/tables/glance-policy.xml:26(td) ./doc/common/tables/nova-policy.xml:62(td) ./doc/common/tables/ceilometer-api.xml:38(td) ./doc/common/tables/cinder-common.xml:142(td) ./doc/common/tables/neutron-policy.xml:26(td) ./doc/common/tables/heat-api.xml:46(td) ./doc/common/tables/keystone-policy.xml:26(td)
-msgid "policy_file = policy.json"
-msgstr ""
-
-#: ./doc/common/tables/glance-policy.xml:27(td)
-msgid "(StrOpt) The location of the policy file."
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml:8(caption)
-msgid "Description of configuration options for mlnx"
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml:19(th) ./doc/common/tables/neutron-ml2_mlnx.xml:19(th) ./doc/common/tables/neutron-vmware.xml:70(th)
-msgid "[ESWITCH]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml:22(td)
-msgid "backoff_rate = 2"
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml:23(td)
-msgid "(IntOpt) backoff rate multiplier for waiting period between retries for request to daemon, i.e. value of 2 will double the request timeout each retry"
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml:26(td)
-msgid "daemon_endpoint = tcp://127.0.0.1:60001"
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml:27(td)
-msgid "(StrOpt) eswitch daemon end point"
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml:30(td) ./doc/common/tables/neutron-linuxbridge_agent.xml:22(td)
-msgid "physical_interface_mappings ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml:31(td) ./doc/common/tables/neutron-linuxbridge_agent.xml:23(td)
-msgid "(ListOpt) List of &lt;physical_network&gt;:&lt;physical_interface&gt;"
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml:34(td)
-msgid "request_timeout = 3000"
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml:35(td)
-msgid "(IntOpt) The number of milliseconds the agent will wait for response on request to daemon."
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml:38(th)
-msgid "[MLNX]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml:41(td)
-msgid "network_vlan_ranges = default:1:1000"
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml:42(td) ./doc/common/tables/neutron-openvswitch_agent.xml:92(td) ./doc/common/tables/neutron-hyperv_agent.xml:46(td) ./doc/common/tables/neutron-linuxbridge_agent.xml:30(td)
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:92(td) ./doc/common/tables/neutron-linuxbridge_agent.xml:30(td) ./doc/common/tables/neutron-hyperv_agent.xml:46(td) ./doc/common/tables/neutron-mlnx.xml:42(td)
 msgid "(ListOpt) List of &lt;physical_network&gt;:&lt;vlan_min&gt;:&lt;vlan_max&gt; or &lt;physical_network&gt;"
 msgstr ""
 
-#: ./doc/common/tables/neutron-mlnx.xml:45(td)
-msgid "physical_network_type = eth"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:95(td) ./doc/common/tables/neutron-cisco.xml:89(td) ./doc/common/tables/neutron-linuxbridge_agent.xml:33(td) ./doc/common/tables/neutron-hyperv_agent.xml:49(td)
+msgid "tenant_network_type = local"
 msgstr ""
 
-#: ./doc/common/tables/neutron-mlnx.xml:46(td)
-msgid "(StrOpt) Physical network type for provider network (eth or ib)"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:96(td)
+msgid "(StrOpt) Network type for tenant networks (local, vlan, gre, vxlan, or none)"
 msgstr ""
 
-#: ./doc/common/tables/neutron-mlnx.xml:49(td)
-msgid "physical_network_type_mappings ="
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:99(td)
+msgid "tun_peer_patch_port = patch-int"
 msgstr ""
 
-#: ./doc/common/tables/neutron-mlnx.xml:50(td)
-msgid "(ListOpt) List of &lt;physical_network&gt;:&lt;physical_network_type&gt; with physical_network_type is either eth or ib"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:100(td)
+msgid "(StrOpt) Peer patch port in tunnel bridge for integration bridge"
 msgstr ""
 
-#: ./doc/common/tables/neutron-mlnx.xml:53(td)
-msgid "tenant_network_type = vlan"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:103(td) ./doc/common/tables/neutron-cisco.xml:93(td)
+msgid "tunnel_bridge = br-tun"
 msgstr ""
 
-#: ./doc/common/tables/neutron-mlnx.xml:54(td) ./doc/common/tables/neutron-linuxbridge_agent.xml:34(td)
-msgid "(StrOpt) Network type for tenant networks (local, vlan, or none)"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:104(td)
+msgid "(StrOpt) Tunnel bridge to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:107(td) ./doc/common/tables/neutron-ml2_gre.xml:22(td)
+msgid "tunnel_id_ranges ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:108(td)
+msgid "(ListOpt) List of &lt;tun_min&gt;:&lt;tun_max&gt;"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:111(td)
+msgid "tunnel_type ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml:112(td)
+msgid "(StrOpt) The type of tunnels to use when utilizing tunnels, either 'gre' or 'vxlan'"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml:8(caption)
+msgid "Description of configuration options for clients"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml:22(td)
+msgid "region_name_for_services = None"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml:23(td)
+msgid "(StrOpt) Default region name used to get services endpoints."
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml:26(th)
+msgid "[clients]"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml:29(td) ./doc/common/tables/heat-clients_nova.xml:22(td) ./doc/common/tables/heat-clients_heat.xml:22(td) ./doc/common/tables/heat-cfn_api.xml:64(td) ./doc/common/tables/heat-api.xml:145(td) ./doc/common/tables/heat-clients_ceilometer.xml:22(td) ./doc/common/tables/heat-clients_cinder.xml:22(td) ./doc/common/tables/heat-clients_trove.xml:22(td) ./doc/common/tables/nova-ca.xml:65(td) ./doc/common/tables/cinder-ssl.xml:22(td) ./doc/common/tables/trove-ssl.xml:22(td) ./doc/common/tables/heat-clients_swift.xml:22(td) ./doc/common/tables/heat-cloudwatch_api.xml:60(td) ./doc/common/tables/neutron-ssl.xml:37(td) ./doc/common/tables/heat-clients_neutron.xml:22(td) ./doc/common/tables/heat-clients_keystone.xml:22(td) ./doc/common/tables/ceilometer-ssl.xml:22(td) ./doc/common/tables/glance-ssl.xml:22(td)
+msgid "ca_file = None"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml:30(td) ./doc/common/tables/heat-clients_nova.xml:23(td) ./doc/common/tables/heat-clients_heat.xml:23(td) ./doc/common/tables/heat-clients_ceilometer.xml:23(td) ./doc/common/tables/heat-clients_cinder.xml:23(td) ./doc/common/tables/heat-clients_trove.xml:23(td) ./doc/common/tables/heat-clients_swift.xml:23(td) ./doc/common/tables/heat-clients_neutron.xml:23(td) ./doc/common/tables/heat-clients_keystone.xml:23(td)
+msgid "(StrOpt) Optional CA cert file to use in SSL connections."
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml:33(td) ./doc/common/tables/heat-clients_nova.xml:26(td) ./doc/common/tables/heat-clients_heat.xml:26(td) ./doc/common/tables/heat-cfn_api.xml:45(td) ./doc/common/tables/heat-cfn_api.xml:68(td) ./doc/common/tables/heat-api.xml:115(td) ./doc/common/tables/heat-api.xml:149(td) ./doc/common/tables/heat-clients_ceilometer.xml:26(td) ./doc/common/tables/heat-clients_cinder.xml:26(td) ./doc/common/tables/heat-clients_trove.xml:26(td) ./doc/common/tables/nova-ca.xml:69(td) ./doc/common/tables/cinder-ssl.xml:26(td) ./doc/common/tables/trove-ssl.xml:26(td) ./doc/common/tables/heat-clients_swift.xml:26(td) ./doc/common/tables/heat-cloudwatch_api.xml:41(td) ./doc/common/tables/heat-cloudwatch_api.xml:64(td) ./doc/common/tables/neutron-ssl.xml:41(td) ./doc/common/tables/neutron-nec.xml:26(td) ./doc/common/tables/heat-clients_neutron.xml:26(td) ./doc/common/tables/heat-clients_keystone.xml:26(td) ./doc/common/tables/ceilometer-ssl.xml:26(td) ./doc/common/tables/glance-ssl.xml:26(td)
+msgid "cert_file = None"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml:34(td) ./doc/common/tables/heat-clients_nova.xml:27(td) ./doc/common/tables/heat-clients_heat.xml:27(td) ./doc/common/tables/heat-clients_ceilometer.xml:27(td) ./doc/common/tables/heat-clients_cinder.xml:27(td) ./doc/common/tables/heat-clients_trove.xml:27(td) ./doc/common/tables/heat-clients_swift.xml:27(td) ./doc/common/tables/heat-clients_neutron.xml:27(td) ./doc/common/tables/heat-clients_keystone.xml:27(td)
+msgid "(StrOpt) Optional PEM-formatted certificate chain file."
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml:37(td) ./doc/common/tables/heat-clients_nova.xml:30(td) ./doc/common/tables/heat-clients_heat.xml:30(td) ./doc/common/tables/heat-clients_ceilometer.xml:30(td) ./doc/common/tables/heat-clients_cinder.xml:30(td) ./doc/common/tables/heat-clients_trove.xml:30(td) ./doc/common/tables/heat-clients_swift.xml:30(td) ./doc/common/tables/heat-clients_neutron.xml:30(td) ./doc/common/tables/swift-dispersion-dispersion.xml:39(td) ./doc/common/tables/heat-clients_keystone.xml:30(td)
+msgid "endpoint_type = publicURL"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml:38(td) ./doc/common/tables/heat-clients_nova.xml:31(td) ./doc/common/tables/heat-clients_heat.xml:31(td) ./doc/common/tables/heat-clients_ceilometer.xml:31(td) ./doc/common/tables/heat-clients_cinder.xml:31(td) ./doc/common/tables/heat-clients_trove.xml:31(td) ./doc/common/tables/heat-clients_swift.xml:31(td) ./doc/common/tables/heat-clients_neutron.xml:31(td) ./doc/common/tables/heat-clients_keystone.xml:31(td)
+msgid "(StrOpt) Type of endpoint in Identity service catalog to use for communication with the OpenStack service."
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml:41(td) ./doc/common/tables/glance-auth_token.xml:101(td) ./doc/common/tables/heat-clients_nova.xml:34(td) ./doc/common/tables/heat-clients_heat.xml:34(td) ./doc/common/tables/neutron-auth_token.xml:101(td) ./doc/common/tables/ceilometer-auth.xml:101(td) ./doc/common/tables/ceilometer-auth.xml:136(td) ./doc/common/tables/heat-auth_token.xml:101(td) ./doc/common/tables/nova-auth_token.xml:94(td) ./doc/common/tables/heat-clients_ceilometer.xml:34(td) ./doc/common/tables/cinder-auth_token.xml:101(td) ./doc/common/tables/keystone-auth_token.xml:101(td) ./doc/common/tables/heat-clients_cinder.xml:34(td) ./doc/common/tables/heat-clients_trove.xml:34(td) ./doc/common/tables/heat-clients_swift.xml:34(td) ./doc/common/tables/heat-clients_neutron.xml:34(td) ./doc/common/tables/trove-auth_token.xml:101(td) ./doc/common/tables/heat-clients_keystone.xml:34(td)
+msgid "insecure = False"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml:42(td) ./doc/common/tables/heat-clients_nova.xml:35(td) ./doc/common/tables/heat-clients_heat.xml:35(td) ./doc/common/tables/heat-clients_ceilometer.xml:35(td) ./doc/common/tables/heat-clients_cinder.xml:35(td) ./doc/common/tables/heat-clients_trove.xml:35(td) ./doc/common/tables/heat-clients_swift.xml:35(td) ./doc/common/tables/heat-clients_neutron.xml:35(td) ./doc/common/tables/heat-clients_keystone.xml:35(td)
+msgid "(BoolOpt) If set, then the server's certificate will not be verified."
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml:45(td) ./doc/common/tables/heat-clients_nova.xml:38(td) ./doc/common/tables/heat-clients_heat.xml:38(td) ./doc/common/tables/heat-cfn_api.xml:49(td) ./doc/common/tables/heat-cfn_api.xml:72(td) ./doc/common/tables/heat-api.xml:119(td) ./doc/common/tables/heat-api.xml:153(td) ./doc/common/tables/heat-clients_ceilometer.xml:38(td) ./doc/common/tables/heat-clients_cinder.xml:38(td) ./doc/common/tables/heat-clients_trove.xml:38(td) ./doc/common/tables/nova-ca.xml:73(td) ./doc/common/tables/cinder-ssl.xml:30(td) ./doc/common/tables/trove-ssl.xml:30(td) ./doc/common/tables/heat-clients_swift.xml:38(td) ./doc/common/tables/heat-cloudwatch_api.xml:45(td) ./doc/common/tables/heat-cloudwatch_api.xml:68(td) ./doc/common/tables/neutron-ssl.xml:45(td) ./doc/common/tables/neutron-nec.xml:46(td) ./doc/common/tables/heat-clients_neutron.xml:38(td) ./doc/common/tables/heat-clients_keystone.xml:38(td) ./doc/common/tables/ceilometer-ssl.xml:30(td) ./doc/common/tables/glance-ssl.xml:30(td)
+msgid "key_file = None"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml:46(td) ./doc/common/tables/heat-clients_nova.xml:39(td) ./doc/common/tables/heat-clients_heat.xml:39(td) ./doc/common/tables/heat-clients_ceilometer.xml:39(td) ./doc/common/tables/heat-clients_cinder.xml:39(td) ./doc/common/tables/heat-clients_trove.xml:39(td) ./doc/common/tables/heat-clients_swift.xml:39(td) ./doc/common/tables/heat-clients_neutron.xml:39(td) ./doc/common/tables/heat-clients_keystone.xml:39(td)
+msgid "(StrOpt) Optional PEM-formatted file that contains the private key."
+msgstr ""
+
+#: ./doc/common/tables/cinder-solidfire.xml:8(caption)
+msgid "Description of configuration options for solidfire"
+msgstr ""
+
+#: ./doc/common/tables/cinder-solidfire.xml:22(td)
+msgid "sf_account_prefix = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-solidfire.xml:23(td)
+msgid "(StrOpt) Create SolidFire accounts with this prefix. Any string can be used here, but the string \"hostname\" is special and will create a prefix using the cinder node hostsname (previous default behavior). The default is NO prefix."
+msgstr ""
+
+#: ./doc/common/tables/cinder-solidfire.xml:26(td)
+msgid "sf_allow_tenant_qos = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-solidfire.xml:27(td)
+msgid "(BoolOpt) Allow tenants to specify QOS on create"
+msgstr ""
+
+#: ./doc/common/tables/cinder-solidfire.xml:30(td)
+msgid "sf_api_port = 443"
+msgstr ""
+
+#: ./doc/common/tables/cinder-solidfire.xml:31(td)
+msgid "(IntOpt) SolidFire API port. Useful if the device api is behind a proxy on a different port."
+msgstr ""
+
+#: ./doc/common/tables/cinder-solidfire.xml:34(td)
+msgid "sf_emulate_512 = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-solidfire.xml:35(td)
+msgid "(BoolOpt) Set 512 byte emulation on volume creation;"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:8(caption) ./doc/common/tables/glance-rpc.xml:8(caption) ./doc/common/tables/keystone-rpc.xml:8(caption) ./doc/common/tables/ceilometer-rpc.xml:8(caption) ./doc/common/tables/trove-rpc.xml:8(caption) ./doc/common/tables/cinder-rpc.xml:8(caption) ./doc/common/tables/heat-rpc.xml:8(caption) ./doc/common/tables/nova-rpc.xml:8(caption)
+msgid "Description of configuration options for rpc"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:22(td) ./doc/common/tables/trove-amqp.xml:22(td) ./doc/common/tables/heat-amqp.xml:22(td) ./doc/common/tables/keystone-amqp.xml:22(td) ./doc/common/tables/glance-amqp.xml:22(td) ./doc/common/tables/cinder-rpc.xml:26(td) ./doc/common/tables/nova-rpc_all.xml:22(td) ./doc/common/tables/nova-rpc.xml:22(td) ./doc/common/tables/ceilometer-amqp.xml:22(td)
+msgid "amqp_auto_delete = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:23(td) ./doc/common/tables/trove-amqp.xml:23(td) ./doc/common/tables/heat-amqp.xml:23(td) ./doc/common/tables/keystone-amqp.xml:23(td) ./doc/common/tables/glance-amqp.xml:23(td) ./doc/common/tables/cinder-rpc.xml:27(td) ./doc/common/tables/nova-rpc_all.xml:23(td) ./doc/common/tables/nova-rpc.xml:23(td) ./doc/common/tables/ceilometer-amqp.xml:23(td)
+msgid "(BoolOpt) Auto-delete queues in amqp."
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:26(td) ./doc/common/tables/trove-amqp.xml:26(td) ./doc/common/tables/heat-amqp.xml:26(td) ./doc/common/tables/keystone-amqp.xml:26(td) ./doc/common/tables/glance-amqp.xml:26(td) ./doc/common/tables/cinder-rpc.xml:30(td) ./doc/common/tables/nova-rpc_all.xml:26(td) ./doc/common/tables/nova-rpc.xml:26(td) ./doc/common/tables/ceilometer-amqp.xml:26(td)
+msgid "amqp_durable_queues = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:27(td) ./doc/common/tables/trove-amqp.xml:27(td) ./doc/common/tables/heat-amqp.xml:27(td) ./doc/common/tables/keystone-amqp.xml:27(td) ./doc/common/tables/glance-amqp.xml:27(td) ./doc/common/tables/cinder-rpc.xml:31(td) ./doc/common/tables/nova-rpc_all.xml:27(td) ./doc/common/tables/nova-rpc.xml:27(td) ./doc/common/tables/ceilometer-amqp.xml:27(td)
+msgid "(BoolOpt) Use durable queues in amqp."
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:30(td)
+msgid "control_exchange = neutron"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:31(td) ./doc/common/tables/trove-amqp.xml:35(td) ./doc/common/tables/heat-amqp.xml:31(td) ./doc/common/tables/ceilometer-exchange.xml:27(td)
+msgid "(StrOpt) AMQP exchange to connect to if using RabbitMQ or Qpid"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:34(td) ./doc/common/tables/ceilometer-redis.xml:26(td) ./doc/common/tables/glance-matchmaker.xml:22(td) ./doc/common/tables/trove-rpc.xml:30(td) ./doc/common/tables/cinder-rpc.xml:66(td) ./doc/common/tables/nova-rpc_all.xml:54(td) ./doc/common/tables/heat-rpc.xml:30(td) ./doc/common/tables/nova-rpc.xml:34(td) ./doc/common/tables/keystone-redis.xml:26(td)
+msgid "matchmaker_heartbeat_freq = 300"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:35(td) ./doc/common/tables/ceilometer-redis.xml:27(td) ./doc/common/tables/trove-rpc.xml:31(td) ./doc/common/tables/heat-rpc.xml:31(td)
+msgid "(IntOpt) Heartbeat frequency"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:38(td) ./doc/common/tables/ceilometer-redis.xml:30(td) ./doc/common/tables/glance-matchmaker.xml:26(td) ./doc/common/tables/trove-rpc.xml:34(td) ./doc/common/tables/cinder-rpc.xml:70(td) ./doc/common/tables/nova-rpc_all.xml:58(td) ./doc/common/tables/heat-rpc.xml:34(td) ./doc/common/tables/nova-rpc.xml:38(td) ./doc/common/tables/keystone-redis.xml:30(td)
+msgid "matchmaker_heartbeat_ttl = 600"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:39(td) ./doc/common/tables/ceilometer-redis.xml:31(td) ./doc/common/tables/glance-matchmaker.xml:27(td) ./doc/common/tables/trove-rpc.xml:35(td) ./doc/common/tables/cinder-rpc.xml:71(td) ./doc/common/tables/nova-rpc_all.xml:59(td) ./doc/common/tables/heat-rpc.xml:35(td) ./doc/common/tables/nova-rpc.xml:39(td) ./doc/common/tables/keystone-redis.xml:31(td)
+msgid "(IntOpt) Heartbeat time-to-live."
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:42(td)
+msgid "rpc_backend = neutron.openstack.common.rpc.impl_kombu"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:43(td) ./doc/common/tables/ceilometer-rpc.xml:31(td) ./doc/common/tables/trove-rpc.xml:51(td) ./doc/common/tables/heat-rpc.xml:39(td)
+msgid "(StrOpt) The messaging module to use, defaults to kombu."
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:46(td) ./doc/common/tables/keystone-amqp.xml:50(td) ./doc/common/tables/ceilometer-rpc.xml:34(td) ./doc/common/tables/trove-rpc.xml:54(td) ./doc/common/tables/glance-zmq.xml:22(td) ./doc/common/tables/cinder-rpc.xml:186(td) ./doc/common/tables/nova-rpc_all.xml:154(td) ./doc/common/tables/heat-rpc.xml:42(td) ./doc/common/tables/nova-rpc.xml:46(td)
+msgid "rpc_cast_timeout = 30"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:47(td) ./doc/common/tables/keystone-amqp.xml:51(td) ./doc/common/tables/ceilometer-rpc.xml:35(td) ./doc/common/tables/trove-rpc.xml:55(td) ./doc/common/tables/glance-zmq.xml:23(td) ./doc/common/tables/cinder-rpc.xml:187(td) ./doc/common/tables/nova-rpc_all.xml:155(td) ./doc/common/tables/heat-rpc.xml:43(td) ./doc/common/tables/nova-rpc.xml:47(td)
+msgid "(IntOpt) Seconds to wait before a cast expires (TTL). Only supported by impl_zmq."
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:50(td) ./doc/common/tables/keystone-amqp.xml:54(td) ./doc/common/tables/ceilometer-rpc.xml:38(td) ./doc/common/tables/trove-rpc.xml:58(td) ./doc/common/tables/glance-amqp.xml:42(td) ./doc/common/tables/cinder-rpc.xml:190(td) ./doc/common/tables/nova-rpc_all.xml:158(td) ./doc/common/tables/heat-rpc.xml:46(td) ./doc/common/tables/nova-rpc.xml:50(td)
+msgid "rpc_conn_pool_size = 30"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:51(td) ./doc/common/tables/ceilometer-rpc.xml:39(td) ./doc/common/tables/trove-rpc.xml:59(td) ./doc/common/tables/heat-rpc.xml:47(td)
+msgid "(IntOpt) Size of RPC connection pool"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:54(td) ./doc/common/tables/keystone-amqp.xml:58(td) ./doc/common/tables/ceilometer-rpc.xml:42(td) ./doc/common/tables/trove-rpc.xml:62(td) ./doc/common/tables/glance-amqp.xml:46(td) ./doc/common/tables/cinder-rpc.xml:194(td) ./doc/common/tables/nova-rpc_all.xml:162(td) ./doc/common/tables/heat-rpc.xml:50(td) ./doc/common/tables/nova-rpc.xml:54(td)
+msgid "rpc_response_timeout = 60"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:55(td) ./doc/common/tables/ceilometer-rpc.xml:43(td) ./doc/common/tables/trove-rpc.xml:63(td) ./doc/common/tables/heat-rpc.xml:51(td)
+msgid "(IntOpt) Seconds to wait for a response from call or multicall"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:58(td) ./doc/common/tables/keystone-amqp.xml:62(td) ./doc/common/tables/ceilometer-rpc.xml:46(td) ./doc/common/tables/trove-rpc.xml:66(td) ./doc/common/tables/glance-amqp.xml:50(td) ./doc/common/tables/cinder-rpc.xml:198(td) ./doc/common/tables/nova-rpc_all.xml:166(td) ./doc/common/tables/heat-rpc.xml:54(td) ./doc/common/tables/nova-rpc.xml:58(td)
+msgid "rpc_thread_pool_size = 64"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:59(td) ./doc/common/tables/ceilometer-rpc.xml:47(td) ./doc/common/tables/trove-rpc.xml:67(td) ./doc/common/tables/heat-rpc.xml:55(td)
+msgid "(IntOpt) Size of RPC thread pool"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:62(td)
+msgid "rpc_workers = 0"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:63(td)
+msgid "(IntOpt) Number of RPC worker processes for service"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:69(td)
+msgid "rpc_support_old_agents = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:70(td)
+msgid "(BoolOpt) Enable server RPC compatibility with old agents"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:73(th) ./doc/common/tables/ceilometer-redis.xml:49(th) ./doc/common/tables/glance-matchmaker.xml:30(th) ./doc/common/tables/cinder-rpc.xml:238(th) ./doc/common/tables/nova-rpc_all.xml:205(th) ./doc/common/tables/heat-rpc.xml:58(th) ./doc/common/tables/trove-redis.xml:34(th) ./doc/common/tables/nova-rpc.xml:69(th) ./doc/common/tables/keystone-redis.xml:42(th)
+msgid "[matchmaker_ring]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:76(td) ./doc/common/tables/ceilometer-redis.xml:52(td) ./doc/common/tables/glance-matchmaker.xml:33(td) ./doc/common/tables/cinder-rpc.xml:241(td) ./doc/common/tables/nova-rpc_all.xml:208(td) ./doc/common/tables/heat-rpc.xml:61(td) ./doc/common/tables/trove-redis.xml:37(td) ./doc/common/tables/nova-rpc.xml:72(td) ./doc/common/tables/keystone-redis.xml:45(td)
+msgid "ringfile = /etc/oslo/matchmaker_ring.json"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:77(td) ./doc/common/tables/ceilometer-redis.xml:53(td) ./doc/common/tables/heat-rpc.xml:62(td) ./doc/common/tables/trove-redis.xml:38(td)
+msgid "(StrOpt) Matchmaker ring file (JSON)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:80(th) ./doc/common/tables/ceilometer-rpc.xml:92(th) ./doc/common/tables/trove-rpc.xml:70(th) ./doc/common/tables/heat-rpc.xml:65(th)
+msgid "[rpc_notifier2]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:83(td) ./doc/common/tables/ceilometer-rpc.xml:95(td) ./doc/common/tables/trove-rpc.xml:73(td) ./doc/common/tables/heat-rpc.xml:68(td)
+msgid "topics = notifications"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml:84(td) ./doc/common/tables/trove-rpc.xml:74(td)
+msgid "(ListOpt) AMQP topic(s) used for openstack notifications"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_percona.xml:8(caption)
+msgid "Description of configuration options for db_percona"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_percona.xml:19(th)
+msgid "[percona]"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_percona.xml:22(td) ./doc/common/tables/trove-db_mysql.xml:22(td) ./doc/common/tables/trove-backup.xml:50(td)
+msgid "backup_strategy = InnoBackupEx"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_percona.xml:23(td) ./doc/common/tables/trove-db_cassandra.xml:23(td) ./doc/common/tables/trove-db_mysql.xml:23(td) ./doc/common/tables/trove-db_couchbase.xml:23(td) ./doc/common/tables/trove-db_mongodb.xml:23(td) ./doc/common/tables/trove-backup.xml:51(td) ./doc/common/tables/trove-db_redis.xml:23(td)
+msgid "(StrOpt) Default strategy to perform backups."
+msgstr ""
+
+#: ./doc/common/tables/trove-db_percona.xml:26(td) ./doc/common/tables/trove-db_mysql.xml:26(td)
+msgid "mount_point = /var/lib/mysql"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_percona.xml:27(td) ./doc/common/tables/trove-db_cassandra.xml:27(td) ./doc/common/tables/trove-db_mysql.xml:27(td) ./doc/common/tables/trove-db_couchbase.xml:27(td) ./doc/common/tables/trove-db_mongodb.xml:27(td) ./doc/common/tables/trove-db_redis.xml:27(td)
+msgid "(StrOpt) Filesystem path for mounting volumes if volume support is enabled"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_percona.xml:30(td) ./doc/common/tables/trove-db_mysql.xml:30(td)
+msgid "root_on_create = False"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_percona.xml:31(td) ./doc/common/tables/trove-db_mysql.xml:31(td)
+msgid "(BoolOpt) Enable the automatic creation of the root user for the service during instance-create. The generated password for the root user is immediately returned in the response of instance-create as the 'password' field."
+msgstr ""
+
+#: ./doc/common/tables/trove-db_percona.xml:34(td) ./doc/common/tables/trove-db_mysql.xml:34(td)
+msgid "tcp_ports = 3306"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_percona.xml:35(td) ./doc/common/tables/trove-db_cassandra.xml:31(td) ./doc/common/tables/trove-db_mysql.xml:35(td) ./doc/common/tables/trove-db_couchbase.xml:31(td) ./doc/common/tables/trove-db_mongodb.xml:31(td) ./doc/common/tables/trove-db_redis.xml:31(td)
+msgid "(ListOpt) List of TCP ports and/or port ranges to open in the security group (only applicable if trove_security_groups_support is True)"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_percona.xml:38(td) ./doc/common/tables/trove-db_cassandra.xml:34(td) ./doc/common/tables/trove-db_mysql.xml:38(td) ./doc/common/tables/trove-db_couchbase.xml:34(td) ./doc/common/tables/trove-db_mongodb.xml:34(td) ./doc/common/tables/trove-db_redis.xml:34(td)
+msgid "udp_ports ="
+msgstr ""
+
+#: ./doc/common/tables/trove-db_percona.xml:39(td) ./doc/common/tables/trove-db_cassandra.xml:35(td) ./doc/common/tables/trove-db_mysql.xml:39(td) ./doc/common/tables/trove-db_couchbase.xml:35(td) ./doc/common/tables/trove-db_redis.xml:35(td)
+msgid "(ListOpt) List of UDP ports and/or port ranges to open in the security group (only applicable if trove_security_groups_support is True)"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_percona.xml:42(td) ./doc/common/tables/trove-db_couchbase.xml:38(td) ./doc/common/tables/trove-db_mongodb.xml:38(td) ./doc/common/tables/trove-db_redis.xml:38(td)
+msgid "usage_timeout = 450"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_percona.xml:43(td) ./doc/common/tables/trove-db_cassandra.xml:39(td) ./doc/common/tables/trove-db_mysql.xml:43(td) ./doc/common/tables/trove-db_couchbase.xml:39(td) ./doc/common/tables/trove-db_mongodb.xml:39(td) ./doc/common/tables/trove-db_redis.xml:39(td)
+msgid "(IntOpt) Timeout to wait for a guest to become active."
+msgstr ""
+
+#: ./doc/common/tables/nova-periodic.xml:8(caption)
+msgid "Description of configuration options for periodic"
+msgstr ""
+
+#: ./doc/common/tables/nova-periodic.xml:22(td)
+msgid "periodic_enable = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-periodic.xml:23(td)
+msgid "(BoolOpt) Enable periodic tasks"
+msgstr ""
+
+#: ./doc/common/tables/nova-periodic.xml:26(td) ./doc/common/tables/cinder-common.xml:130(td)
+msgid "periodic_fuzzy_delay = 60"
+msgstr ""
+
+#: ./doc/common/tables/nova-periodic.xml:27(td) ./doc/common/tables/neutron-common.xml:163(td)
+msgid "(IntOpt) Range of seconds to randomly delay when starting the periodic task scheduler to reduce stampeding. (Disable by setting to 0)"
+msgstr ""
+
+#: ./doc/common/tables/nova-periodic.xml:30(td) ./doc/common/tables/cinder-common.xml:158(td) ./doc/common/tables/neutron-api.xml:54(td)
+msgid "run_external_periodic_tasks = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-periodic.xml:31(td) ./doc/common/tables/cinder-common.xml:159(td) ./doc/common/tables/neutron-api.xml:55(td)
+msgid "(BoolOpt) Some periodic tasks can be run in a separate process. Should we run them here?"
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml:8(caption) ./doc/common/tables/cinder-auth.xml:8(caption) ./doc/common/tables/ceilometer-auth.xml:8(caption)
+msgid "Description of configuration options for auth"
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml:19(th)
+msgid "[auth]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml:22(td)
+msgid "external = keystone.auth.plugins.external.DefaultDomain"
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml:23(td)
+msgid "(StrOpt) The external (REMOTE_USER) auth plugin module."
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml:26(td)
+msgid "methods = external, password, token"
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml:27(td)
+msgid "(ListOpt) Default auth methods."
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml:30(td)
+msgid "password = keystone.auth.plugins.password.Password"
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml:31(td)
+msgid "(StrOpt) The password auth plugin module."
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml:34(td)
+msgid "token = keystone.auth.plugins.token.Token"
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml:35(td)
+msgid "(StrOpt) The token auth plugin module."
+msgstr ""
+
+#: ./doc/common/tables/keystone-policy.xml:8(caption) ./doc/common/tables/neutron-policy.xml:8(caption) ./doc/common/tables/nova-policy.xml:8(caption) ./doc/common/tables/glance-policy.xml:8(caption)
+msgid "Description of configuration options for policy"
+msgstr ""
+
+#: ./doc/common/tables/keystone-policy.xml:22(td) ./doc/common/tables/nova-policy.xml:58(td) ./doc/common/tables/glance-policy.xml:22(td) ./doc/common/tables/ceilometer-api.xml:34(td) ./doc/common/tables/heat-api.xml:42(td) ./doc/common/tables/cinder-common.xml:138(td)
+msgid "policy_default_rule = default"
+msgstr ""
+
+#: ./doc/common/tables/keystone-policy.xml:23(td) ./doc/common/tables/ceilometer-api.xml:35(td) ./doc/common/tables/heat-api.xml:43(td)
+msgid "(StrOpt) Rule enforced when requested rule is not found"
+msgstr ""
+
+#: ./doc/common/tables/keystone-policy.xml:26(td) ./doc/common/tables/neutron-policy.xml:26(td) ./doc/common/tables/nova-policy.xml:62(td) ./doc/common/tables/glance-policy.xml:26(td) ./doc/common/tables/ceilometer-api.xml:38(td) ./doc/common/tables/heat-api.xml:46(td) ./doc/common/tables/cinder-common.xml:142(td)
+msgid "policy_file = policy.json"
+msgstr ""
+
+#: ./doc/common/tables/keystone-policy.xml:27(td) ./doc/common/tables/ceilometer-api.xml:39(td) ./doc/common/tables/heat-api.xml:47(td)
+msgid "(StrOpt) JSON file containing policy"
+msgstr ""
+
+#: ./doc/common/tables/keystone-policy.xml:30(th)
+msgid "[policy]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-policy.xml:33(td)
+msgid "driver = keystone.policy.backends.sql.Policy"
+msgstr ""
+
+#: ./doc/common/tables/keystone-policy.xml:34(td)
+msgid "(StrOpt) Keystone Policy backend driver."
+msgstr ""
+
+#: ./doc/common/tables/keystone-policy.xml:37(td) ./doc/common/tables/keystone-api.xml:46(td) ./doc/common/tables/keystone-identity.xml:38(td) ./doc/common/tables/keystone-catalog.xml:26(td) ./doc/common/tables/keystone-assignment.xml:34(td)
+msgid "list_limit = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-policy.xml:38(td)
+msgid "(IntOpt) Maximum number of entities that will be returned in a policy collection."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:8(caption) ./doc/common/tables/neutron-auth_token.xml:8(caption) ./doc/common/tables/heat-auth_token.xml:8(caption) ./doc/common/tables/nova-auth_token.xml:8(caption) ./doc/common/tables/cinder-auth_token.xml:8(caption) ./doc/common/tables/keystone-auth_token.xml:8(caption) ./doc/common/tables/trove-auth_token.xml:8(caption)
+msgid "Description of configuration options for auth_token"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:22(td) ./doc/common/tables/glance-auth_token.xml:117(td) ./doc/common/tables/ceilometer-common.xml:38(td) ./doc/common/tables/neutron-auth_token.xml:22(td) ./doc/common/tables/neutron-auth_token.xml:117(td) ./doc/common/tables/ceilometer-auth.xml:117(td) ./doc/common/tables/nova-common.xml:50(td) ./doc/common/tables/heat-auth_token.xml:22(td) ./doc/common/tables/heat-auth_token.xml:117(td) ./doc/common/tables/nova-auth_token.xml:110(td) ./doc/common/tables/cinder-auth_token.xml:22(td) ./doc/common/tables/cinder-auth_token.xml:117(td) ./doc/common/tables/keystone-auth_token.xml:22(td) ./doc/common/tables/keystone-auth_token.xml:117(td) ./doc/common/tables/trove-auth_token.xml:22(td) ./doc/common/tables/trove-auth_token.xml:117(td)
+msgid "memcached_servers = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:23(td) ./doc/common/tables/ceilometer-common.xml:39(td) ./doc/common/tables/neutron-auth_token.xml:23(td) ./doc/common/tables/nova-common.xml:51(td) ./doc/common/tables/heat-auth_token.xml:23(td) ./doc/common/tables/cinder-auth_token.xml:23(td) ./doc/common/tables/keystone-auth_token.xml:23(td) ./doc/common/tables/trove-auth_token.xml:23(td)
+msgid "(ListOpt) Memcached servers or None for in process cache."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:26(th) ./doc/common/tables/neutron-auth_token.xml:26(th) ./doc/common/tables/ceilometer-auth.xml:26(th) ./doc/common/tables/heat-auth_token.xml:26(th) ./doc/common/tables/nova-auth_token.xml:19(th) ./doc/common/tables/cinder-auth_token.xml:26(th) ./doc/common/tables/keystone-auth_token.xml:26(th) ./doc/common/tables/trove-auth_token.xml:26(th)
+msgid "[keystone_authtoken]"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:29(td) ./doc/common/tables/neutron-auth_token.xml:29(td) ./doc/common/tables/ceilometer-auth.xml:29(td) ./doc/common/tables/glance-registry.xml:22(td) ./doc/common/tables/heat-auth_token.xml:29(td) ./doc/common/tables/nova-auth_token.xml:22(td) ./doc/common/tables/cinder-auth_token.xml:29(td) ./doc/common/tables/keystone-auth_token.xml:29(td) ./doc/common/tables/neutron-embrane_lb.xml:22(td) ./doc/common/tables/trove-auth_token.xml:29(td) ./doc/common/tables/neutron-common.xml:22(td) ./doc/common/tables/neutron-common.xml:192(td) ./doc/common/tables/neutron-common.xml:219(td)
+msgid "admin_password = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:30(td) ./doc/common/tables/neutron-auth_token.xml:30(td) ./doc/common/tables/ceilometer-auth.xml:30(td) ./doc/common/tables/heat-auth_token.xml:30(td) ./doc/common/tables/nova-auth_token.xml:23(td) ./doc/common/tables/cinder-auth_token.xml:30(td) ./doc/common/tables/keystone-auth_token.xml:30(td) ./doc/common/tables/trove-auth_token.xml:30(td)
+msgid "(StrOpt) Keystone account password"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:33(td) ./doc/common/tables/neutron-auth_token.xml:33(td) ./doc/common/tables/ceilometer-auth.xml:33(td) ./doc/common/tables/heat-auth_token.xml:33(td) ./doc/common/tables/nova-auth_token.xml:26(td) ./doc/common/tables/cinder-auth_token.xml:33(td) ./doc/common/tables/keystone-auth_token.xml:33(td) ./doc/common/tables/trove-auth_token.xml:33(td)
+msgid "admin_tenant_name = admin"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:34(td) ./doc/common/tables/neutron-auth_token.xml:34(td) ./doc/common/tables/ceilometer-auth.xml:34(td) ./doc/common/tables/heat-auth_token.xml:34(td) ./doc/common/tables/nova-auth_token.xml:27(td) ./doc/common/tables/cinder-auth_token.xml:34(td) ./doc/common/tables/keystone-auth_token.xml:34(td) ./doc/common/tables/trove-auth_token.xml:34(td)
+msgid "(StrOpt) Keystone service account tenant name to validate user tokens"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:37(td) ./doc/common/tables/neutron-auth_token.xml:37(td) ./doc/common/tables/ceilometer-auth.xml:37(td) ./doc/common/tables/heat-auth_token.xml:37(td) ./doc/common/tables/nova-auth_token.xml:30(td) ./doc/common/tables/cinder-auth_token.xml:37(td) ./doc/common/tables/keystone-auth_token.xml:37(td) ./doc/common/tables/trove-auth_token.xml:37(td)
+msgid "admin_token = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:38(td) ./doc/common/tables/neutron-auth_token.xml:38(td) ./doc/common/tables/ceilometer-auth.xml:38(td) ./doc/common/tables/heat-auth_token.xml:38(td) ./doc/common/tables/nova-auth_token.xml:31(td) ./doc/common/tables/cinder-auth_token.xml:38(td) ./doc/common/tables/keystone-auth_token.xml:38(td) ./doc/common/tables/trove-auth_token.xml:38(td)
+msgid "(StrOpt) Single shared secret with the Keystone configuration used for bootstrapping a Keystone installation, or otherwise bypassing the normal authentication process."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:41(td) ./doc/common/tables/neutron-auth_token.xml:41(td) ./doc/common/tables/ceilometer-auth.xml:41(td) ./doc/common/tables/glance-registry.xml:30(td) ./doc/common/tables/heat-auth_token.xml:41(td) ./doc/common/tables/nova-auth_token.xml:34(td) ./doc/common/tables/cinder-auth_token.xml:41(td) ./doc/common/tables/keystone-auth_token.xml:41(td) ./doc/common/tables/trove-auth_token.xml:41(td) ./doc/common/tables/neutron-common.xml:30(td) ./doc/common/tables/neutron-common.xml:200(td)
+msgid "admin_user = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:42(td) ./doc/common/tables/neutron-auth_token.xml:42(td) ./doc/common/tables/ceilometer-auth.xml:42(td) ./doc/common/tables/heat-auth_token.xml:42(td) ./doc/common/tables/nova-auth_token.xml:35(td) ./doc/common/tables/cinder-auth_token.xml:42(td) ./doc/common/tables/keystone-auth_token.xml:42(td) ./doc/common/tables/trove-auth_token.xml:42(td)
+msgid "(StrOpt) Keystone account username"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:45(td) ./doc/common/tables/neutron-auth_token.xml:45(td) ./doc/common/tables/ceilometer-auth.xml:45(td) ./doc/common/tables/heat-auth_token.xml:45(td) ./doc/common/tables/nova-auth_token.xml:38(td) ./doc/common/tables/cinder-auth_token.xml:45(td) ./doc/common/tables/keystone-auth_token.xml:45(td) ./doc/common/tables/trove-auth_token.xml:45(td)
+msgid "auth_admin_prefix ="
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:46(td) ./doc/common/tables/neutron-auth_token.xml:46(td) ./doc/common/tables/ceilometer-auth.xml:46(td) ./doc/common/tables/heat-auth_token.xml:46(td) ./doc/common/tables/nova-auth_token.xml:39(td) ./doc/common/tables/cinder-auth_token.xml:46(td) ./doc/common/tables/keystone-auth_token.xml:46(td) ./doc/common/tables/trove-auth_token.xml:46(td)
+msgid "(StrOpt) Prefix to prepend at the beginning of the path"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:49(td) ./doc/common/tables/neutron-auth_token.xml:49(td) ./doc/common/tables/ceilometer-auth.xml:49(td) ./doc/common/tables/heat-auth_token.xml:49(td) ./doc/common/tables/nova-auth_token.xml:42(td) ./doc/common/tables/cinder-auth_token.xml:49(td) ./doc/common/tables/keystone-auth_token.xml:49(td) ./doc/common/tables/trove-auth_token.xml:49(td)
+msgid "auth_host = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:50(td) ./doc/common/tables/neutron-auth_token.xml:50(td) ./doc/common/tables/ceilometer-auth.xml:50(td) ./doc/common/tables/heat-auth_token.xml:50(td) ./doc/common/tables/nova-auth_token.xml:43(td) ./doc/common/tables/cinder-auth_token.xml:50(td) ./doc/common/tables/keystone-auth_token.xml:50(td) ./doc/common/tables/trove-auth_token.xml:50(td)
+msgid "(StrOpt) Host providing the admin Identity API endpoint"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:53(td) ./doc/common/tables/neutron-auth_token.xml:53(td) ./doc/common/tables/ceilometer-auth.xml:53(td) ./doc/common/tables/heat-auth_token.xml:53(td) ./doc/common/tables/nova-auth_token.xml:46(td) ./doc/common/tables/cinder-auth_token.xml:53(td) ./doc/common/tables/keystone-auth_token.xml:53(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:21(td) ./doc/common/tables/trove-auth_token.xml:53(td)
+msgid "auth_port = 35357"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:54(td) ./doc/common/tables/neutron-auth_token.xml:54(td) ./doc/common/tables/ceilometer-auth.xml:54(td) ./doc/common/tables/heat-auth_token.xml:54(td) ./doc/common/tables/nova-auth_token.xml:47(td) ./doc/common/tables/cinder-auth_token.xml:54(td) ./doc/common/tables/keystone-auth_token.xml:54(td) ./doc/common/tables/trove-auth_token.xml:54(td)
+msgid "(IntOpt) Port of the admin Identity API endpoint"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:57(td) ./doc/common/tables/neutron-auth_token.xml:57(td) ./doc/common/tables/ceilometer-auth.xml:57(td) ./doc/common/tables/heat-auth_token.xml:57(td) ./doc/common/tables/nova-auth_token.xml:50(td) ./doc/common/tables/cinder-auth_token.xml:57(td) ./doc/common/tables/keystone-auth_token.xml:57(td) ./doc/common/tables/trove-auth_token.xml:57(td)
+msgid "auth_protocol = https"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:58(td) ./doc/common/tables/neutron-auth_token.xml:58(td) ./doc/common/tables/ceilometer-auth.xml:58(td) ./doc/common/tables/heat-auth_token.xml:58(td) ./doc/common/tables/nova-auth_token.xml:51(td) ./doc/common/tables/cinder-auth_token.xml:58(td) ./doc/common/tables/keystone-auth_token.xml:58(td) ./doc/common/tables/trove-auth_token.xml:58(td)
+msgid "(StrOpt) Protocol of the admin Identity API endpoint(http or https)"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:61(td) ./doc/common/tables/neutron-auth_token.xml:61(td) ./doc/common/tables/ceilometer-auth.xml:61(td) ./doc/common/tables/heat-auth_token.xml:61(td) ./doc/common/tables/nova-auth_token.xml:54(td) ./doc/common/tables/heat-api.xml:92(td) ./doc/common/tables/cinder-auth_token.xml:61(td) ./doc/common/tables/keystone-auth_token.xml:61(td) ./doc/common/tables/trove-auth_token.xml:61(td)
+msgid "auth_uri = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:62(td) ./doc/common/tables/neutron-auth_token.xml:62(td) ./doc/common/tables/ceilometer-auth.xml:62(td) ./doc/common/tables/heat-auth_token.xml:62(td) ./doc/common/tables/nova-auth_token.xml:55(td) ./doc/common/tables/cinder-auth_token.xml:62(td) ./doc/common/tables/keystone-auth_token.xml:62(td) ./doc/common/tables/trove-auth_token.xml:62(td)
+msgid "(StrOpt) Complete public Identity API endpoint"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:65(td) ./doc/common/tables/neutron-auth_token.xml:65(td) ./doc/common/tables/ceilometer-auth.xml:65(td) ./doc/common/tables/heat-auth_token.xml:65(td) ./doc/common/tables/nova-auth_token.xml:58(td) ./doc/common/tables/cinder-auth_token.xml:65(td) ./doc/common/tables/keystone-auth_token.xml:65(td) ./doc/common/tables/trove-auth_token.xml:65(td)
+msgid "auth_version = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:66(td) ./doc/common/tables/neutron-auth_token.xml:66(td) ./doc/common/tables/ceilometer-auth.xml:66(td) ./doc/common/tables/heat-auth_token.xml:66(td) ./doc/common/tables/nova-auth_token.xml:59(td) ./doc/common/tables/cinder-auth_token.xml:66(td) ./doc/common/tables/keystone-auth_token.xml:66(td) ./doc/common/tables/trove-auth_token.xml:66(td)
+msgid "(StrOpt) API version of the admin Identity API endpoint"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:69(td) ./doc/common/tables/neutron-auth_token.xml:69(td) ./doc/common/tables/ceilometer-auth.xml:69(td) ./doc/common/tables/heat-auth_token.xml:69(td) ./doc/common/tables/nova-auth_token.xml:62(td) ./doc/common/tables/cinder-auth_token.xml:69(td) ./doc/common/tables/keystone-auth_token.xml:69(td) ./doc/common/tables/trove-auth_token.xml:69(td)
+msgid "cache = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:70(td) ./doc/common/tables/neutron-auth_token.xml:70(td) ./doc/common/tables/ceilometer-auth.xml:70(td) ./doc/common/tables/heat-auth_token.xml:70(td) ./doc/common/tables/nova-auth_token.xml:63(td) ./doc/common/tables/cinder-auth_token.xml:70(td) ./doc/common/tables/keystone-auth_token.xml:70(td) ./doc/common/tables/trove-auth_token.xml:70(td)
+msgid "(StrOpt) Env key for the swift cache"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:73(td) ./doc/common/tables/neutron-auth_token.xml:73(td) ./doc/common/tables/ceilometer-auth.xml:73(td) ./doc/common/tables/heat-auth_token.xml:73(td) ./doc/common/tables/nova-auth_token.xml:66(td) ./doc/common/tables/cinder-auth_token.xml:73(td) ./doc/common/tables/keystone-auth_token.xml:73(td) ./doc/common/tables/trove-auth_token.xml:73(td)
+msgid "cafile = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:74(td) ./doc/common/tables/neutron-auth_token.xml:74(td) ./doc/common/tables/ceilometer-auth.xml:74(td) ./doc/common/tables/heat-auth_token.xml:74(td) ./doc/common/tables/nova-auth_token.xml:67(td) ./doc/common/tables/cinder-auth_token.xml:74(td) ./doc/common/tables/keystone-auth_token.xml:74(td) ./doc/common/tables/trove-auth_token.xml:74(td)
+msgid "(StrOpt) A PEM encoded Certificate Authority to use when verifying HTTPs connections. Defaults to system CAs."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:77(td) ./doc/common/tables/neutron-auth_token.xml:77(td) ./doc/common/tables/ceilometer-auth.xml:77(td) ./doc/common/tables/heat-auth_token.xml:77(td) ./doc/common/tables/nova-auth_token.xml:70(td) ./doc/common/tables/cinder-auth_token.xml:77(td) ./doc/common/tables/keystone-auth_token.xml:77(td) ./doc/common/tables/trove-auth_token.xml:77(td)
+msgid "certfile = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:78(td) ./doc/common/tables/glance-auth_token.xml:106(td) ./doc/common/tables/neutron-auth_token.xml:78(td) ./doc/common/tables/neutron-auth_token.xml:106(td) ./doc/common/tables/ceilometer-auth.xml:78(td) ./doc/common/tables/ceilometer-auth.xml:106(td) ./doc/common/tables/heat-auth_token.xml:78(td) ./doc/common/tables/heat-auth_token.xml:106(td) ./doc/common/tables/nova-auth_token.xml:71(td) ./doc/common/tables/nova-auth_token.xml:99(td) ./doc/common/tables/cinder-auth_token.xml:78(td) ./doc/common/tables/cinder-auth_token.xml:106(td) ./doc/common/tables/keystone-auth_token.xml:78(td) ./doc/common/tables/keystone-auth_token.xml:106(td) ./doc/common/tables/trove-auth_token.xml:78(td) ./doc/common/tables/trove-auth_token.xml:106(td)
+msgid "(StrOpt) Required if Keystone server requires client certificate"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:81(td) ./doc/common/tables/neutron-auth_token.xml:81(td) ./doc/common/tables/ceilometer-auth.xml:81(td) ./doc/common/tables/heat-auth_token.xml:81(td) ./doc/common/tables/nova-auth_token.xml:74(td) ./doc/common/tables/cinder-auth_token.xml:81(td) ./doc/common/tables/keystone-auth_token.xml:81(td) ./doc/common/tables/trove-auth_token.xml:81(td)
+msgid "delay_auth_decision = False"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:82(td) ./doc/common/tables/neutron-auth_token.xml:82(td) ./doc/common/tables/ceilometer-auth.xml:82(td) ./doc/common/tables/heat-auth_token.xml:82(td) ./doc/common/tables/nova-auth_token.xml:75(td) ./doc/common/tables/cinder-auth_token.xml:82(td) ./doc/common/tables/keystone-auth_token.xml:82(td) ./doc/common/tables/trove-auth_token.xml:82(td)
+msgid "(BoolOpt) Do not handle authorization requests within the middleware, but delegate the authorization decision to downstream WSGI components"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:85(td) ./doc/common/tables/neutron-auth_token.xml:85(td) ./doc/common/tables/ceilometer-auth.xml:85(td) ./doc/common/tables/heat-auth_token.xml:85(td) ./doc/common/tables/nova-auth_token.xml:78(td) ./doc/common/tables/cinder-auth_token.xml:85(td) ./doc/common/tables/keystone-auth_token.xml:85(td) ./doc/common/tables/trove-auth_token.xml:85(td) ./doc/common/tables/keystone-token.xml:38(td)
+msgid "enforce_token_bind = permissive"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:86(td) ./doc/common/tables/neutron-auth_token.xml:86(td) ./doc/common/tables/ceilometer-auth.xml:86(td) ./doc/common/tables/heat-auth_token.xml:86(td) ./doc/common/tables/nova-auth_token.xml:79(td) ./doc/common/tables/cinder-auth_token.xml:86(td) ./doc/common/tables/keystone-auth_token.xml:86(td) ./doc/common/tables/trove-auth_token.xml:86(td)
+msgid "(StrOpt) Used to control the use and type of token binding. Can be set to: \"disabled\" to not check token binding. \"permissive\" (default) to validate binding information if the bind type is of a form known to the server and ignore it if not. \"strict\" like \"permissive\" but if the bind type is unknown the token will be rejected. \"required\" any form of token binding is needed to be allowed. Finally the name of a binding method that must be present in tokens."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:89(td) ./doc/common/tables/neutron-auth_token.xml:89(td) ./doc/common/tables/ceilometer-auth.xml:89(td) ./doc/common/tables/heat-auth_token.xml:89(td) ./doc/common/tables/nova-auth_token.xml:82(td) ./doc/common/tables/cinder-auth_token.xml:89(td) ./doc/common/tables/keystone-auth_token.xml:89(td) ./doc/common/tables/trove-auth_token.xml:89(td)
+msgid "http_connect_timeout = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:90(td) ./doc/common/tables/neutron-auth_token.xml:90(td) ./doc/common/tables/ceilometer-auth.xml:90(td) ./doc/common/tables/heat-auth_token.xml:90(td) ./doc/common/tables/nova-auth_token.xml:83(td) ./doc/common/tables/cinder-auth_token.xml:90(td) ./doc/common/tables/keystone-auth_token.xml:90(td) ./doc/common/tables/trove-auth_token.xml:90(td)
+msgid "(BoolOpt) Request timeout value for communicating with Identity API server."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:93(td) ./doc/common/tables/neutron-auth_token.xml:93(td) ./doc/common/tables/ceilometer-auth.xml:93(td) ./doc/common/tables/heat-auth_token.xml:93(td) ./doc/common/tables/nova-auth_token.xml:86(td) ./doc/common/tables/cinder-auth_token.xml:93(td) ./doc/common/tables/keystone-auth_token.xml:93(td) ./doc/common/tables/trove-auth_token.xml:93(td)
+msgid "http_request_max_retries = 3"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:94(td) ./doc/common/tables/neutron-auth_token.xml:94(td) ./doc/common/tables/ceilometer-auth.xml:94(td) ./doc/common/tables/heat-auth_token.xml:94(td) ./doc/common/tables/nova-auth_token.xml:87(td) ./doc/common/tables/cinder-auth_token.xml:94(td) ./doc/common/tables/keystone-auth_token.xml:94(td) ./doc/common/tables/trove-auth_token.xml:94(td)
+msgid "(IntOpt) How many times are we trying to reconnect when communicating with Identity API Server."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:97(td) ./doc/common/tables/neutron-auth_token.xml:97(td) ./doc/common/tables/ceilometer-auth.xml:97(td) ./doc/common/tables/heat-auth_token.xml:97(td) ./doc/common/tables/nova-auth_token.xml:90(td) ./doc/common/tables/cinder-auth_token.xml:97(td) ./doc/common/tables/keystone-auth_token.xml:97(td) ./doc/common/tables/trove-auth_token.xml:97(td)
+msgid "include_service_catalog = True"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:98(td) ./doc/common/tables/neutron-auth_token.xml:98(td) ./doc/common/tables/ceilometer-auth.xml:98(td) ./doc/common/tables/heat-auth_token.xml:98(td) ./doc/common/tables/nova-auth_token.xml:91(td) ./doc/common/tables/cinder-auth_token.xml:98(td) ./doc/common/tables/keystone-auth_token.xml:98(td) ./doc/common/tables/trove-auth_token.xml:98(td)
+msgid "(BoolOpt) (optional) indicate whether to set the X-Service-Catalog header. If False, middleware will not ask for service catalog on token validation and will not set the X-Service-Catalog header."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:102(td) ./doc/common/tables/neutron-auth_token.xml:102(td) ./doc/common/tables/ceilometer-auth.xml:102(td) ./doc/common/tables/heat-auth_token.xml:102(td) ./doc/common/tables/nova-auth_token.xml:95(td) ./doc/common/tables/cinder-auth_token.xml:102(td) ./doc/common/tables/keystone-auth_token.xml:102(td) ./doc/common/tables/trove-auth_token.xml:102(td)
+msgid "(BoolOpt) Verify HTTPS connections."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:105(td) ./doc/common/tables/neutron-auth_token.xml:105(td) ./doc/common/tables/ceilometer-auth.xml:105(td) ./doc/common/tables/heat-auth_token.xml:105(td) ./doc/common/tables/nova-auth_token.xml:98(td) ./doc/common/tables/cinder-auth_token.xml:105(td) ./doc/common/tables/keystone-auth_token.xml:105(td) ./doc/common/tables/trove-auth_token.xml:105(td)
+msgid "keyfile = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:109(td) ./doc/common/tables/neutron-auth_token.xml:109(td) ./doc/common/tables/ceilometer-auth.xml:109(td) ./doc/common/tables/heat-auth_token.xml:109(td) ./doc/common/tables/nova-auth_token.xml:102(td) ./doc/common/tables/cinder-auth_token.xml:109(td) ./doc/common/tables/keystone-auth_token.xml:109(td) ./doc/common/tables/trove-auth_token.xml:109(td)
+msgid "memcache_secret_key = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:110(td) ./doc/common/tables/neutron-auth_token.xml:110(td) ./doc/common/tables/ceilometer-auth.xml:110(td) ./doc/common/tables/heat-auth_token.xml:110(td) ./doc/common/tables/nova-auth_token.xml:103(td) ./doc/common/tables/cinder-auth_token.xml:110(td) ./doc/common/tables/keystone-auth_token.xml:110(td) ./doc/common/tables/trove-auth_token.xml:110(td)
+msgid "(StrOpt) (optional, mandatory if memcache_security_strategy is defined) this string is used for key derivation."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:113(td) ./doc/common/tables/neutron-auth_token.xml:113(td) ./doc/common/tables/ceilometer-auth.xml:113(td) ./doc/common/tables/heat-auth_token.xml:113(td) ./doc/common/tables/nova-auth_token.xml:106(td) ./doc/common/tables/cinder-auth_token.xml:113(td) ./doc/common/tables/keystone-auth_token.xml:113(td) ./doc/common/tables/trove-auth_token.xml:113(td)
+msgid "memcache_security_strategy = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:114(td) ./doc/common/tables/neutron-auth_token.xml:114(td) ./doc/common/tables/ceilometer-auth.xml:114(td) ./doc/common/tables/heat-auth_token.xml:114(td) ./doc/common/tables/nova-auth_token.xml:107(td) ./doc/common/tables/cinder-auth_token.xml:114(td) ./doc/common/tables/keystone-auth_token.xml:114(td) ./doc/common/tables/trove-auth_token.xml:114(td)
+msgid "(StrOpt) (optional) if defined, indicate whether token data should be authenticated or authenticated and encrypted. Acceptable values are MAC or ENCRYPT. If MAC, token data is authenticated (with HMAC) in the cache. If ENCRYPT, token data is encrypted and authenticated in the cache. If the value is not one of these options or empty, auth_token will raise an exception on initialization."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:118(td) ./doc/common/tables/neutron-auth_token.xml:118(td) ./doc/common/tables/ceilometer-auth.xml:118(td) ./doc/common/tables/heat-auth_token.xml:118(td) ./doc/common/tables/nova-auth_token.xml:111(td) ./doc/common/tables/cinder-auth_token.xml:118(td) ./doc/common/tables/keystone-auth_token.xml:118(td) ./doc/common/tables/trove-auth_token.xml:118(td)
+msgid "(ListOpt) Optionally specify a list of memcached server(s) to use for caching. If left undefined, tokens will instead be cached in-process."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:121(td) ./doc/common/tables/neutron-auth_token.xml:121(td) ./doc/common/tables/ceilometer-auth.xml:121(td) ./doc/common/tables/heat-auth_token.xml:121(td) ./doc/common/tables/nova-auth_token.xml:114(td) ./doc/common/tables/cinder-auth_token.xml:121(td) ./doc/common/tables/keystone-auth_token.xml:121(td) ./doc/common/tables/trove-auth_token.xml:121(td)
+msgid "revocation_cache_time = 300"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:122(td) ./doc/common/tables/neutron-auth_token.xml:122(td) ./doc/common/tables/ceilometer-auth.xml:122(td) ./doc/common/tables/heat-auth_token.xml:122(td) ./doc/common/tables/nova-auth_token.xml:115(td) ./doc/common/tables/cinder-auth_token.xml:122(td) ./doc/common/tables/keystone-auth_token.xml:122(td) ./doc/common/tables/trove-auth_token.xml:122(td)
+msgid "(IntOpt) Determines the frequency at which the list of revoked tokens is retrieved from the Identity service (in seconds). A high number of revocation events combined with a low cache duration may significantly reduce performance."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:125(td) ./doc/common/tables/neutron-auth_token.xml:125(td) ./doc/common/tables/ceilometer-auth.xml:125(td) ./doc/common/tables/heat-auth_token.xml:125(td) ./doc/common/tables/nova-auth_token.xml:118(td) ./doc/common/tables/cinder-auth_token.xml:125(td) ./doc/common/tables/keystone-auth_token.xml:125(td) ./doc/common/tables/trove-auth_token.xml:125(td)
+msgid "signing_dir = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:126(td) ./doc/common/tables/neutron-auth_token.xml:126(td) ./doc/common/tables/ceilometer-auth.xml:126(td) ./doc/common/tables/heat-auth_token.xml:126(td) ./doc/common/tables/nova-auth_token.xml:119(td) ./doc/common/tables/cinder-auth_token.xml:126(td) ./doc/common/tables/keystone-auth_token.xml:126(td) ./doc/common/tables/trove-auth_token.xml:126(td)
+msgid "(StrOpt) Directory used to cache files related to PKI tokens"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:129(td) ./doc/common/tables/neutron-auth_token.xml:129(td) ./doc/common/tables/ceilometer-auth.xml:129(td) ./doc/common/tables/heat-auth_token.xml:129(td) ./doc/common/tables/nova-auth_token.xml:122(td) ./doc/common/tables/cinder-auth_token.xml:129(td) ./doc/common/tables/keystone-auth_token.xml:129(td) ./doc/common/tables/trove-auth_token.xml:129(td)
+msgid "token_cache_time = 300"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml:130(td) ./doc/common/tables/neutron-auth_token.xml:130(td) ./doc/common/tables/ceilometer-auth.xml:130(td) ./doc/common/tables/heat-auth_token.xml:130(td) ./doc/common/tables/nova-auth_token.xml:123(td) ./doc/common/tables/cinder-auth_token.xml:130(td) ./doc/common/tables/keystone-auth_token.xml:130(td) ./doc/common/tables/trove-auth_token.xml:130(td)
+msgid "(IntOpt) In order to prevent excessive effort spent validating tokens, the middleware caches previously-seen tokens for a configurable duration (in seconds). Set to -1 to disable caching completely."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:8(caption)
+msgid "Description of configuration options for netapp_7mode_nfs"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:22(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:22(td)
+msgid "expiry_thres_minutes = 720"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:23(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:23(td)
+msgid "(IntOpt) This option specifies the threshold for last access time for images in the NFS image cache. When a cache cleaning cycle begins, images in the cache that have not been accessed in the last M minutes, where M is the value of this parameter, will be deleted from the cache to create free space on the NFS share."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:26(td) ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:26(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:22(td) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:22(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:30(td)
+msgid "netapp_login = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:27(td) ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:27(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:23(td) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:23(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:31(td)
+msgid "(StrOpt) Administrative user account name used to access the storage system or proxy server."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:30(td) ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:30(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:26(td) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:26(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:34(td)
+msgid "netapp_password = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:31(td) ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:31(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:27(td) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:27(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:35(td)
+msgid "(StrOpt) Password for the administrative user account specified in the netapp_login option."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:34(td) ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:38(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:30(td) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:30(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:38(td)
+msgid "netapp_server_hostname = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:35(td) ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:39(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:31(td) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:31(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:39(td)
+msgid "(StrOpt) The hostname (or IP address) for the storage system or proxy server."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:38(td) ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:42(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:34(td) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:34(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:42(td)
+msgid "netapp_server_port = 80"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:39(td) ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:43(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:35(td) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:35(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:43(td)
+msgid "(IntOpt) The TCP port to use for communication with the storage system or proxy server. Traditionally, port 80 is used for HTTP and port 443 is used for HTTPS; however, this value should be changed if an alternate port has been configured on the storage system or proxy server."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:42(td) ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:46(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:42(td) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:42(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:46(td)
+msgid "netapp_storage_family = ontap_cluster"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:43(td) ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:47(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:43(td) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:43(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:47(td)
+msgid "(StrOpt) The storage family type used on the storage system; valid values are ontap_7mode for using Data ONTAP operating in 7-Mode, ontap_cluster for using clustered Data ONTAP, or eseries for using E-Series."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:46(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:46(td) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:46(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:50(td)
+msgid "netapp_storage_protocol = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:47(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:47(td) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:47(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:51(td)
+msgid "(StrOpt) The storage protocol to be used on the data path with the storage system; valid values are iscsi or nfs."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:50(td) ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:54(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:50(td) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:50(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:54(td)
+msgid "netapp_transport_type = http"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:51(td) ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:55(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:51(td) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:51(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:55(td)
+msgid "(StrOpt) The transport protocol used when communicating with the storage system or proxy server. Valid values are http or https."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:54(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:62(td)
+msgid "thres_avl_size_perc_start = 20"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:55(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:63(td)
+msgid "(IntOpt) If the percentage of available space for an NFS share has dropped below the value specified by this option, the NFS image cache will be cleaned."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:58(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:66(td)
+msgid "thres_avl_size_perc_stop = 60"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:59(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:67(td)
+msgid "(IntOpt) When the percentage of available space on an NFS share has reached the percentage specified by this option, the driver will stop clearing files from the NFS image cache that have not been accessed in the last M minutes, where M is the value of the expiry_thres_minutes configuration option."
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml:7(literal)
+msgid "[container-sync]"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml:7(literal) ./doc/common/tables/swift-container-server-container-auditor.xml:7(literal) ./doc/common/tables/swift-container-server-filter-recon.xml:7(literal) ./doc/common/tables/swift-container-server-DEFAULT.xml:7(literal) ./doc/common/tables/swift-container-server-pipeline-main.xml:7(literal) ./doc/common/tables/swift-container-server-filter-healthcheck.xml:7(literal) ./doc/common/tables/swift-container-server-container-updater.xml:7(literal) ./doc/common/tables/swift-container-server-app-container-server.xml:7(literal) ./doc/common/tables/swift-container-server-container-replicator.xml:7(literal)
+msgid "container-server.conf-sample"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml:7(caption) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:7(caption) ./doc/common/tables/swift-object-expirer-pipeline-main.xml:7(caption) ./doc/common/tables/swift-container-server-container-auditor.xml:7(caption) ./doc/common/tables/swift-swift-swift-constraints.xml:7(caption) ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-slo.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-cache.xml:7(caption) ./doc/common/tables/swift-container-server-filter-recon.xml:7(caption) ./doc/common/tables/swift-proxy-server-pipeline-main.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml:7(caption) ./doc/common/tables/swift-account-server-filter-healthcheck.xml:7(caption) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:7(caption) ./doc/common/tables/swift-container-server-DEFAULT.xml:7(caption) ./doc/common/tables/swift-container-server-pipeline-main.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml:7(caption) ./doc/common/tables/swift-container-server-filter-healthcheck.xml:7(caption) ./doc/common/tables/swift-object-expirer-object-expirer.xml:7(caption) ./doc/common/tables/swift-object-server-filter-healthcheck.xml:7(caption) ./doc/common/tables/swift-object-server-app-object-server.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:7(caption) ./doc/common/tables/swift-object-server-DEFAULT.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:7(caption) ./doc/common/tables/swift-rsyncd-container.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:7(caption) ./doc/common/tables/swift-rsyncd-account.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-name_check.xml:7(caption) ./doc/common/tables/swift-account-server-filter-recon.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:7(caption) ./doc/common/tables/swift-account-server-account-replicator.xml:7(caption) ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml:7(caption) ./doc/common/tables/swift-container-server-container-updater.xml:7(caption) ./doc/common/tables/swift-object-server-object-replicator.xml:7(caption) ./doc/common/tables/swift-swift-swift-hash.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-dlo.xml:7(caption) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:7(caption) ./doc/common/tables/swift-object-server-pipeline-main.xml:7(caption) ./doc/common/tables/swift-memcache-memcache.xml:7(caption) ./doc/common/tables/swift-account-server-app-account-server.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-formpost.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:7(caption) ./doc/common/tables/swift-object-expirer-filter-cache.xml:7(caption) ./doc/common/tables/swift-container-sync-realms-realm2.xml:7(caption) ./doc/common/tables/swift-object-server-object-auditor.xml:7(caption) ./doc/common/tables/swift-container-server-app-container-server.xml:7(caption) ./doc/common/tables/swift-account-server-pipeline-main.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-staticweb.xml:7(caption) ./doc/common/tables/swift-container-server-container-replicator.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:7(caption) ./doc/common/tables/swift-object-expirer-app-proxy-server.xml:7(caption) ./doc/common/tables/swift-account-server-account-auditor.xml:7(caption) ./doc/common/tables/swift-object-server-filter-recon.xml:7(caption) ./doc/common/tables/swift-rsyncd-object.xml:7(caption) ./doc/common/tables/swift-drive-audit-drive-audit.xml:7(caption) ./doc/common/tables/swift-object-server-object-updater.xml:7(caption) ./doc/common/tables/swift-dispersion-dispersion.xml:7(caption) ./doc/common/tables/swift-account-server-DEFAULT.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml:7(caption) ./doc/common/tables/swift-account-server-account-reaper.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-container_sync.xml:7(caption) ./doc/common/tables/swift-container-sync-realms-realm1.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml:7(caption)
+msgid "Description of configuration options for <placeholder-1/> in <placeholder-2/>"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml:18(td)
+msgid "log_name = container-sync"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml:18(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:70(td) ./doc/common/tables/swift-container-server-container-auditor.xml:18(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:61(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:64(td) ./doc/common/tables/swift-account-server-account-replicator.xml:18(td) ./doc/common/tables/swift-container-server-container-updater.xml:18(td) ./doc/common/tables/swift-object-server-object-replicator.xml:18(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:24(td) ./doc/common/tables/swift-object-server-object-auditor.xml:18(td) ./doc/common/tables/swift-container-server-container-replicator.xml:18(td) ./doc/common/tables/swift-account-server-account-auditor.xml:18(td) ./doc/common/tables/swift-object-server-object-updater.xml:18(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:58(td) ./doc/common/tables/swift-account-server-account-reaper.xml:18(td)
+msgid "Label used when logging"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml:21(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:73(td) ./doc/common/tables/swift-container-server-container-auditor.xml:21(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:64(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:67(td) ./doc/common/tables/swift-account-server-account-replicator.xml:21(td) ./doc/common/tables/swift-container-server-container-updater.xml:21(td) ./doc/common/tables/swift-object-server-object-replicator.xml:21(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:27(td) ./doc/common/tables/swift-object-server-object-auditor.xml:21(td) ./doc/common/tables/swift-container-server-container-replicator.xml:21(td) ./doc/common/tables/swift-account-server-account-auditor.xml:21(td) ./doc/common/tables/swift-account-server-account-auditor.xml:33(td) ./doc/common/tables/swift-drive-audit-drive-audit.xml:21(td) ./doc/common/tables/swift-object-server-object-updater.xml:21(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:61(td) ./doc/common/tables/swift-account-server-account-reaper.xml:21(td)
+msgid "log_facility = LOG_LOCAL0"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml:21(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:73(td) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:24(td) ./doc/common/tables/swift-container-server-container-auditor.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-cache.xml:24(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:24(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:64(td) ./doc/common/tables/swift-object-server-app-object-server.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:24(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:67(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:24(td) ./doc/common/tables/swift-account-server-account-replicator.xml:21(td) ./doc/common/tables/swift-container-server-container-updater.xml:21(td) ./doc/common/tables/swift-object-server-object-replicator.xml:21(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:27(td) ./doc/common/tables/swift-account-server-app-account-server.xml:24(td) ./doc/common/tables/swift-object-server-object-auditor.xml:21(td) ./doc/common/tables/swift-container-server-app-container-server.xml:24(td) ./doc/common/tables/swift-container-server-container-replicator.xml:21(td) ./doc/common/tables/swift-account-server-account-auditor.xml:21(td) ./doc/common/tables/swift-account-server-account-auditor.xml:33(td) ./doc/common/tables/swift-drive-audit-drive-audit.xml:21(td) ./doc/common/tables/swift-object-server-object-updater.xml:21(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:61(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:24(td) ./doc/common/tables/swift-account-server-account-reaper.xml:21(td)
+msgid "Syslog log facility"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml:24(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:76(td) ./doc/common/tables/swift-container-server-container-auditor.xml:24(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:67(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:70(td) ./doc/common/tables/swift-account-server-account-replicator.xml:24(td) ./doc/common/tables/swift-container-server-container-updater.xml:24(td) ./doc/common/tables/swift-object-server-object-replicator.xml:24(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:30(td) ./doc/common/tables/swift-object-server-object-auditor.xml:24(td) ./doc/common/tables/swift-container-server-container-replicator.xml:24(td) ./doc/common/tables/swift-account-server-account-auditor.xml:24(td) ./doc/common/tables/swift-account-server-account-auditor.xml:36(td) ./doc/common/tables/swift-drive-audit-drive-audit.xml:24(td) ./doc/common/tables/swift-object-server-object-updater.xml:24(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:64(td) ./doc/common/tables/swift-account-server-account-reaper.xml:24(td)
+msgid "log_level = INFO"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml:24(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:76(td) ./doc/common/tables/swift-container-server-container-auditor.xml:24(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:67(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:70(td) ./doc/common/tables/swift-account-server-account-replicator.xml:24(td) ./doc/common/tables/swift-container-server-container-updater.xml:24(td) ./doc/common/tables/swift-object-server-object-replicator.xml:24(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:30(td) ./doc/common/tables/swift-object-server-object-auditor.xml:24(td) ./doc/common/tables/swift-container-server-container-replicator.xml:24(td) ./doc/common/tables/swift-account-server-account-auditor.xml:24(td) ./doc/common/tables/swift-account-server-account-auditor.xml:36(td) ./doc/common/tables/swift-drive-audit-drive-audit.xml:24(td) ./doc/common/tables/swift-object-server-object-updater.xml:24(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:64(td) ./doc/common/tables/swift-account-server-account-reaper.xml:24(td)
+msgid "Logging level"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml:27(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:82(td) ./doc/common/tables/swift-container-server-container-auditor.xml:27(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:70(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:73(td) ./doc/common/tables/swift-account-server-account-replicator.xml:27(td) ./doc/common/tables/swift-container-server-container-updater.xml:27(td) ./doc/common/tables/swift-object-server-object-replicator.xml:27(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:33(td) ./doc/common/tables/swift-object-server-object-auditor.xml:27(td) ./doc/common/tables/swift-container-server-container-replicator.xml:27(td) ./doc/common/tables/swift-account-server-account-auditor.xml:27(td) ./doc/common/tables/swift-drive-audit-drive-audit.xml:27(td) ./doc/common/tables/swift-object-server-object-updater.xml:27(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:67(td) ./doc/common/tables/swift-account-server-account-reaper.xml:27(td)
+msgid "log_address = /dev/log"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml:27(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:82(td) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:33(td) ./doc/common/tables/swift-container-server-container-auditor.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-cache.xml:33(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:30(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:70(td) ./doc/common/tables/swift-object-server-app-object-server.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:33(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:73(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:33(td) ./doc/common/tables/swift-account-server-account-replicator.xml:27(td) ./doc/common/tables/swift-container-server-container-updater.xml:27(td) ./doc/common/tables/swift-object-server-object-replicator.xml:27(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:33(td) ./doc/common/tables/swift-account-server-app-account-server.xml:33(td) ./doc/common/tables/swift-object-server-object-auditor.xml:27(td) ./doc/common/tables/swift-container-server-app-container-server.xml:33(td) ./doc/common/tables/swift-container-server-container-replicator.xml:27(td) ./doc/common/tables/swift-account-server-account-auditor.xml:27(td) ./doc/common/tables/swift-drive-audit-drive-audit.xml:27(td) ./doc/common/tables/swift-object-server-object-updater.xml:27(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:67(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:33(td) ./doc/common/tables/swift-account-server-account-reaper.xml:27(td)
+msgid "Location where syslog sends the logs to"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml:30(td)
+msgid "sync_proxy = http://10.1.1.1:8888,http://10.1.1.2:8888"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml:30(td)
+msgid "If you need to use an HTTP proxy, set it here. Defaults to no proxy."
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml:33(td) ./doc/common/tables/swift-object-expirer-object-expirer.xml:18(td) ./doc/common/tables/swift-container-server-container-updater.xml:30(td) ./doc/common/tables/swift-object-server-object-updater.xml:30(td)
+msgid "interval = 300"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml:33(td) ./doc/common/tables/swift-container-server-container-auditor.xml:30(td) ./doc/common/tables/swift-object-expirer-object-expirer.xml:18(td) ./doc/common/tables/swift-account-server-account-replicator.xml:42(td) ./doc/common/tables/swift-container-server-container-updater.xml:30(td) ./doc/common/tables/swift-container-server-container-replicator.xml:42(td) ./doc/common/tables/swift-account-server-account-auditor.xml:30(td) ./doc/common/tables/swift-object-server-object-updater.xml:30(td) ./doc/common/tables/swift-account-server-account-reaper.xml:33(td)
+msgid "Minimum time for a pass to take"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml:36(td)
+msgid "container_time = 60"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml:36(td)
+msgid "Maximum amount of time to spend syncing each container"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-slo.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-cache.xml:7(literal) ./doc/common/tables/swift-proxy-server-pipeline-main.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml:7(literal) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-name_check.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-dlo.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-formpost.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-staticweb.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-container_sync.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml:7(literal)
+msgid "proxy-server.conf-sample"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:18(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:18(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:18(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:18(td)
+msgid "bind_ip = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:18(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:18(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:18(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:18(td)
+msgid "IP Address for server to bind to"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:21(td)
+msgid "bind_port = 80"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:21(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:21(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:21(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:21(td)
+msgid "Port for server to bind to"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:24(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:24(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:24(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:24(td)
+msgid "bind_timeout = 30"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:24(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:24(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:24(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:24(td)
+msgid "Seconds to attempt bind before giving up"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:27(td) ./doc/common/tables/heat-cfn_api.xml:33(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:27(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:27(td) ./doc/common/tables/heat-api.xml:103(td) ./doc/common/tables/heat-cloudwatch_api.xml:29(td) ./doc/common/tables/neutron-wsgi.xml:22(td) ./doc/common/tables/glance-common.xml:30(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:27(td) ./doc/common/tables/trove-debug.xml:26(td)
+msgid "backlog = 4096"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:27(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:27(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:27(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:27(td)
+msgid "Maximum number of allowed pending TCP connections"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:30(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:33(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:33(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:18(td) ./doc/common/tables/swift-dispersion-dispersion.xml:45(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:33(td)
+msgid "swift_dir = /etc/swift"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:30(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:33(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:33(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:18(td) ./doc/common/tables/swift-dispersion-dispersion.xml:45(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:33(td)
+msgid "Swift configuration directory"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:33(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:30(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:30(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:21(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:30(td)
+msgid "user = swift"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:33(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:30(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:30(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:21(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:30(td)
+msgid "User to run as"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:36(td)
+msgid "expose_info = true"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:36(td)
+msgid "Enables exposing configuration settings via HTTP GET /info."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:39(td)
+msgid "admin_key = secret_admin_key"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:39(td)
+msgid "to use for admin calls that are HMAC signed. Default is empty, which will disable admin calls to /info. the proxy server. For most cases, this should be `egg:swift#proxy`. request whenever it has to failover to a handoff node"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:42(td)
+msgid "disallowed_sections = container_quotas, tempurl"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:42(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:64(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:67(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:79(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:85(td) ./doc/common/tables/swift-object-expirer-pipeline-main.xml:18(td) ./doc/common/tables/neutron-rootwrap.xml:50(td) ./doc/common/tables/neutron-rootwrap.xml:54(td) ./doc/common/tables/swift-proxy-server-filter-slo.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-slo.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-slo.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-slo.xml:36(td) ./doc/common/tables/swift-proxy-server-filter-cache.xml:39(td) ./doc/common/tables/swift-proxy-server-pipeline-main.xml:18(td) ./doc/common/tables/swift-account-server-filter-healthcheck.xml:21(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:33(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:57(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:81(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:87(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:90(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:93(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:96(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:102(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:105(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:108(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:111(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:114(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:58(td) ./doc/common/tables/swift-container-server-pipeline-main.xml:18(td) ./doc/common/tables/swift-container-server-filter-healthcheck.xml:21(td) ./doc/common/tables/swift-object-expirer-object-expirer.xml:24(td) ./doc/common/tables/swift-object-expirer-object-expirer.xml:27(td) ./doc/common/tables/swift-object-expirer-object-expirer.xml:33(td) ./doc/common/tables/swift-object-server-filter-healthcheck.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:24(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:45(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:48(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:45(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:51(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:54(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:57(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:60(td) ./doc/common/tables/swift-rsyncd-container.xml:18(td) ./doc/common/tables/swift-rsyncd-container.xml:21(td) ./doc/common/tables/swift-rsyncd-container.xml:24(td) ./doc/common/tables/swift-rsyncd-container.xml:27(td) ./doc/common/tables/swift-rsyncd-account.xml:18(td) ./doc/common/tables/swift-rsyncd-account.xml:21(td) ./doc/common/tables/swift-rsyncd-account.xml:24(td) ./doc/common/tables/swift-rsyncd-account.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:57(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:60(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:63(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:66(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:69(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:72(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:75(td) ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml:18(td) ./doc/common/tables/swift-object-server-object-replicator.xml:45(td) ./doc/common/tables/swift-object-server-object-replicator.xml:51(td) ./doc/common/tables/swift-object-server-object-replicator.xml:75(td) ./doc/common/tables/swift-proxy-server-filter-dlo.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:36(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:39(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:42(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:45(td) ./doc/common/tables/swift-object-server-pipeline-main.xml:18(td) ./doc/common/tables/swift-memcache-memcache.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:36(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:39(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:42(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:45(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:48(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:51(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:54(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:57(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:60(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:72(td) ./doc/common/tables/swift-container-sync-realms-realm2.xml:18(td) ./doc/common/tables/swift-container-sync-realms-realm2.xml:21(td) ./doc/common/tables/swift-container-sync-realms-realm2.xml:24(td) ./doc/common/tables/swift-container-sync-realms-realm2.xml:27(td) ./doc/common/tables/swift-object-server-object-auditor.xml:45(td) ./doc/common/tables/swift-account-server-pipeline-main.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:36(td) ./doc/common/tables/swift-object-server-filter-recon.xml:24(td) ./doc/common/tables/swift-rsyncd-object.xml:18(td) ./doc/common/tables/swift-rsyncd-object.xml:21(td) ./doc/common/tables/swift-rsyncd-object.xml:24(td) ./doc/common/tables/swift-rsyncd-object.xml:27(td) ./doc/common/tables/swift-drive-audit-drive-audit.xml:39(td) ./doc/common/tables/swift-dispersion-dispersion.xml:24(td) ./doc/common/tables/swift-dispersion-dispersion.xml:33(td) ./doc/common/tables/swift-dispersion-dispersion.xml:42(td) ./doc/common/tables/swift-dispersion-dispersion.xml:48(td) ./doc/common/tables/swift-dispersion-dispersion.xml:51(td) ./doc/common/tables/swift-dispersion-dispersion.xml:57(td) ./doc/common/tables/swift-dispersion-dispersion.xml:60(td) ./doc/common/tables/swift-dispersion-dispersion.xml:63(td) ./doc/common/tables/swift-dispersion-dispersion.xml:66(td) ./doc/common/tables/swift-dispersion-dispersion.xml:69(td) ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml:21(td) ./doc/common/tables/swift-account-server-account-reaper.xml:45(td) ./doc/common/tables/swift-proxy-server-filter-container_sync.xml:21(td) ./doc/common/tables/swift-container-sync-realms-realm1.xml:18(td) ./doc/common/tables/swift-container-sync-realms-realm1.xml:21(td) ./doc/common/tables/swift-container-sync-realms-realm1.xml:24(td) ./doc/common/tables/swift-container-sync-realms-realm1.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml:21(td)
+msgid "No help text available for this option."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:45(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:45(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:51(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:45(td)
+msgid "workers = auto"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:45(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:45(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:51(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:45(td)
+msgid "a much higher value, one can reduce the impact of slow file system operations in one request from negatively impacting other requests."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:48(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:48(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:54(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:48(td)
+msgid "max_clients = 1024"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:48(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:48(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:54(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:48(td)
+msgid "Maximum number of clients one worker can process simultaneously Lowering the number of clients handled per worker, and raising the number of workers can lessen the impact that a CPU intensive, or blocking, request can have on other requests served by the same worker. If the maximum number of clients is set to one, then a given worker will not perform another call while processing, allowing other workers a chance to process it."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:58(td)
+msgid "cert_file = /etc/swift/proxy.crt"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:58(td)
+msgid "to the ssl .crt. This should be enabled for testing purposes only."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:61(td)
+msgid "key_file = /etc/swift/proxy.key"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:61(td)
+msgid "to the ssl .key. This should be enabled for testing purposes only."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:64(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:45(td)
+msgid "expiring_objects_container_divisor = 86400"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:67(td) ./doc/common/tables/swift-object-expirer-object-expirer.xml:24(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:48(td)
+msgid "expiring_objects_account_name = expiring_objects"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:70(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:61(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:64(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:24(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:58(td)
+msgid "log_name = swift"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:79(td)
+msgid "log_headers = false"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:85(td)
+msgid "trans_id_suffix ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:88(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:73(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:76(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:36(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:70(td)
+msgid "log_custom_handlers ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:88(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:73(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:76(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:36(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:70(td)
+msgid "Comma-separated list of functions to call to setup custom log handlers."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:91(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:76(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:79(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:39(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:73(td)
+msgid "log_udp_host ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:91(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:76(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:79(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:39(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:73(td)
+msgid "If not set, the UDB receiver for syslog is disabled."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:94(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:79(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:82(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:42(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:76(td)
+msgid "log_udp_port = 514"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:94(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:79(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:82(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:42(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:76(td)
+msgid "Port value for UDB receiver, if enabled."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:97(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:82(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:85(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:45(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:79(td)
+msgid "log_statsd_host = localhost"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:97(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:82(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:85(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:45(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:79(td)
+msgid "If not set, the StatsD feature is disabled."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:100(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:85(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:88(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:48(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:82(td)
+msgid "log_statsd_port = 8125"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:100(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:85(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:88(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:48(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:82(td)
+msgid "Port value for the StatsD server."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:103(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:88(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:91(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:51(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:85(td)
+msgid "log_statsd_default_sample_rate = 1.0"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:103(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:88(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:91(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:51(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:85(td)
+msgid "Defines the probability of sending a sample for any given event or timing measurement."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:107(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:92(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:95(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:55(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:89(td)
+msgid "log_statsd_sample_rate_factor = 1.0"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:107(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:92(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:95(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:55(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:89(td)
+msgid "Not recommended to set this to a value less than 1.0, if frequency of logging is too high, tune the log_statsd_default_sample_rate instead."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:112(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:97(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:100(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:60(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:94(td)
+msgid "log_statsd_metric_prefix ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:112(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:97(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:100(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:60(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:94(td)
+msgid "Value will be prepended to every metric sent to the StatsD server."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:115(td)
+msgid "cors_allow_origin ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:115(td)
+msgid "is a list of hosts that are included with any CORS request by default and returned with the Access-Control-Allow-Origin header in addition to what the container has set. to call to setup custom log handlers. for eventlet the proxy server. For most cases, this should be `egg:swift#proxy`. request whenever it has to failover to a handoff node"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:118(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:115(td)
+msgid "client_timeout = 60"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:118(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:115(td)
+msgid "Timeout to read one chunk from a client external services"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:121(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:103(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:103(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:100(td)
+msgid "eventlet_debug = false"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:121(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:103(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:103(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:100(td)
+msgid "If true, turn on debug logging for eventlet"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml:8(caption)
+msgid "Description of configuration options for zoning_fabric"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml:19(th)
+msgid "[BRCD_FABRIC_EXAMPLE]"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml:22(td)
+msgid "fc_fabric_address ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml:23(td)
+msgid "(StrOpt) Management IP of fabric"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml:26(td)
+msgid "fc_fabric_password ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml:27(td)
+msgid "(StrOpt) Password for user"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml:30(td)
+msgid "fc_fabric_port = 22"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml:31(td)
+msgid "(IntOpt) Connecting port"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml:34(td)
+msgid "fc_fabric_user ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml:35(td)
+msgid "(StrOpt) Fabric user ID"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml:38(td)
+msgid "principal_switch_wwn = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml:39(td)
+msgid "(StrOpt) Principal switch WWN of the fabric"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml:42(td)
+msgid "zone_activate = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml:43(td)
+msgid "(BoolOpt) overridden zoning activation state"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml:46(td)
+msgid "zone_name_prefix = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml:47(td)
+msgid "(StrOpt) overridden zone name prefix"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml:50(td) ./doc/common/tables/cinder-zoning.xml:33(td)
+msgid "zoning_policy = initiator-target"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml:51(td)
+msgid "(StrOpt) overridden zoning policy"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-redis.xml:8(caption) ./doc/common/tables/neutron-redis.xml:8(caption) ./doc/common/tables/nova-redis.xml:8(caption) ./doc/common/tables/glance-redis.xml:8(caption) ./doc/common/tables/heat-redis.xml:8(caption) ./doc/common/tables/trove-redis.xml:8(caption) ./doc/common/tables/keystone-redis.xml:8(caption)
+msgid "Description of configuration options for redis"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-redis.xml:22(td) ./doc/common/tables/nova-common.xml:42(td) ./doc/common/tables/neutron-redis.xml:22(td) ./doc/common/tables/cinder-common.xml:58(td) ./doc/common/tables/heat-redis.xml:22(td)
+msgid "host = oslo"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-redis.xml:23(td)
+msgid "(StrOpt) Name of this node, which must be valid in an AMQP key. Can be an opaque identifier. For ZeroMQ only, must be a valid host name, FQDN, or IP address."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-redis.xml:34(th) ./doc/common/tables/neutron-redis.xml:26(th) ./doc/common/tables/heat-redis.xml:26(th) ./doc/common/tables/trove-redis.xml:19(th)
+msgid "[matchmaker_redis]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-redis.xml:37(td) ./doc/common/tables/neutron-redis.xml:29(td) ./doc/common/tables/glance-redis.xml:22(td) ./doc/common/tables/heat-redis.xml:29(td) ./doc/common/tables/trove-redis.xml:22(td) ./doc/common/tables/neutron-nec.xml:38(td) ./doc/common/tables/keystone-redis.xml:22(td)
+msgid "host = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-redis.xml:38(td) ./doc/common/tables/neutron-redis.xml:30(td) ./doc/common/tables/heat-redis.xml:30(td) ./doc/common/tables/trove-redis.xml:23(td)
+msgid "(StrOpt) Host to locate redis"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-redis.xml:41(td) ./doc/common/tables/neutron-redis.xml:33(td) ./doc/common/tables/nova-redis.xml:22(td) ./doc/common/tables/keystone-ldap.xml:90(td) ./doc/common/tables/glance-redis.xml:26(td) ./doc/common/tables/cinder-rpc.xml:82(td) ./doc/common/tables/heat-redis.xml:33(td) ./doc/common/tables/neutron-ml2_ncs.xml:22(td) ./doc/common/tables/neutron-ml2_odl.xml:22(td) ./doc/common/tables/trove-redis.xml:26(td) ./doc/common/tables/keystone-redis.xml:34(td)
+msgid "password = None"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-redis.xml:42(td) ./doc/common/tables/neutron-redis.xml:34(td) ./doc/common/tables/heat-redis.xml:34(td) ./doc/common/tables/trove-redis.xml:27(td)
+msgid "(StrOpt) Password for Redis server. (optional)"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-redis.xml:45(td) ./doc/common/tables/nova-common.xml:74(td) ./doc/common/tables/neutron-redis.xml:37(td) ./doc/common/tables/glance-redis.xml:30(td) ./doc/common/tables/cinder-rpc.xml:86(td) ./doc/common/tables/heat-redis.xml:37(td) ./doc/common/tables/trove-redis.xml:30(td) ./doc/common/tables/keystone-redis.xml:38(td)
+msgid "port = 6379"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-redis.xml:46(td) ./doc/common/tables/nova-common.xml:75(td) ./doc/common/tables/neutron-redis.xml:38(td) ./doc/common/tables/glance-redis.xml:31(td) ./doc/common/tables/cinder-rpc.xml:87(td) ./doc/common/tables/heat-redis.xml:38(td) ./doc/common/tables/trove-redis.xml:31(td) ./doc/common/tables/keystone-redis.xml:39(td)
+msgid "(IntOpt) Use this port to connect to redis host."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml:8(caption)
+msgid "Description of configuration options for storage_ceph"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml:22(td)
+msgid "rbd_ceph_conf ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml:23(td)
+msgid "(StrOpt) path to the ceph configuration file to use"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml:26(td)
+msgid "rbd_flatten_volume_from_snapshot = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml:27(td)
+msgid "(BoolOpt) flatten volumes created from snapshots to remove dependency"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml:30(td)
+msgid "rbd_max_clone_depth = 5"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml:31(td)
+msgid "(IntOpt) maximum number of nested clones that can be taken of a volume before enforcing a flatten prior to next clone. A value of zero disables cloning"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml:34(td)
+msgid "rbd_pool = rbd"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml:35(td)
+msgid "(StrOpt) the RADOS pool in which rbd volumes are stored"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml:38(td) ./doc/common/tables/nova-volumes.xml:115(td)
+msgid "rbd_secret_uuid = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml:39(td)
+msgid "(StrOpt) the libvirt uuid of the secret for the rbd_uservolumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml:42(td) ./doc/common/tables/nova-volumes.xml:119(td)
+msgid "rbd_user = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml:43(td)
+msgid "(StrOpt) the RADOS client name for accessing rbd volumes - only set when using cephx authentication"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml:46(td)
+msgid "volume_tmp_dir = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml:47(td)
+msgid "(StrOpt) where to store temporary image files if the volume driver does not write them directly to the volume"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml:8(caption) ./doc/common/tables/nova-vmware.xml:8(caption) ./doc/common/tables/neutron-vmware.xml:8(caption) ./doc/common/tables/glance-vmware.xml:8(caption) ./doc/common/tables/cinder-vmware.xml:8(caption)
+msgid "Description of configuration options for vmware"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml:19(th) ./doc/common/tables/nova-vnc.xml:42(th) ./doc/common/tables/nova-vmware.xml:19(th) ./doc/common/tables/nova-network.xml:254(th)
+msgid "[vmware]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml:22(td) ./doc/common/tables/nova-vmware.xml:22(td)
+msgid "api_retry_count = 10"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml:23(td)
+msgid "(IntOpt) Number of times a VMware Vsphere API must be retried"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml:26(td)
+msgid "host_ip ="
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml:27(td)
+msgid "(StrOpt) IP address of the VMware Vsphere host"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml:30(td)
+msgid "host_password ="
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml:31(td)
+msgid "(StrOpt) Password of VMware Vsphere"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml:34(td)
+msgid "host_username ="
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml:35(td)
+msgid "(StrOpt) Username of VMware Vsphere"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml:38(td) ./doc/common/tables/nova-vmware.xml:54(td)
+msgid "task_poll_interval = 0.5"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml:39(td)
+msgid "(FloatOpt) Sleep time in seconds for polling an ongoing async task"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:8(caption)
+msgid "Description of configuration options for cisco"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:19(th)
+msgid "[CISCO]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:22(td)
+msgid "model_class = neutron.plugins.cisco.models.virt_phy_sw_v2.VirtualPhysicalSwitchModelV2"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:23(td)
+msgid "(StrOpt) Model Class"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:26(td)
+msgid "nexus_driver = neutron.plugins.cisco.test.nexus.fake_nexus_driver.CiscoNEXUSFakeDriver"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:27(td)
+msgid "(StrOpt) Nexus Driver Name"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:30(td)
+msgid "nexus_l3_enable = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:31(td)
+msgid "(BoolOpt) Enable L3 support on the Nexus switches"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:34(td)
+msgid "provider_vlan_auto_create = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:35(td)
+msgid "(BoolOpt) Provider VLANs are automatically created as needed on the Nexus switch"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:38(td)
+msgid "provider_vlan_auto_trunk = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:39(td)
+msgid "(BoolOpt) Provider VLANs are automatically trunked as needed on the ports of the Nexus switch"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:42(td)
+msgid "provider_vlan_name_prefix = p-"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:43(td)
+msgid "(StrOpt) VLAN Name prefix for provider vlans"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:46(td) ./doc/common/tables/neutron-cisco.xml:122(td)
+msgid "svi_round_robin = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:47(td) ./doc/common/tables/neutron-cisco.xml:123(td)
+msgid "(BoolOpt) Distribute SVI interfaces over all switches"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:50(td) ./doc/common/tables/neutron-cisco.xml:126(td)
+msgid "vlan_name_prefix = q-"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:51(td) ./doc/common/tables/neutron-cisco.xml:127(td)
+msgid "(StrOpt) VLAN Name prefix"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:58(td)
+msgid "(StrOpt) N1K Bridge Mappings"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:61(td)
+msgid "default_network_profile = default_network_profile"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:62(td)
+msgid "(StrOpt) N1K default network profile"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:65(td)
+msgid "default_policy_profile = service_profile"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:66(td)
+msgid "(StrOpt) N1K default policy profile"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:69(td)
+msgid "enable_tunneling = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:70(td)
+msgid "(BoolOpt) N1K Enable Tunneling"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:74(td)
+msgid "(StrOpt) N1K Integration Bridge"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:77(td)
+msgid "network_node_policy_profile = dhcp_pp"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:78(td)
+msgid "(StrOpt) N1K policy profile for network node"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:81(td)
+msgid "network_vlan_ranges = vlan:1:4095"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:82(td)
+msgid "(StrOpt) N1K Network VLAN Ranges"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:85(td)
+msgid "poll_duration = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:86(td)
+msgid "(StrOpt) N1K Policy profile polling duration in seconds"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:90(td)
+msgid "(StrOpt) N1K Tenant Network Type"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:94(td)
+msgid "(StrOpt) N1K Tunnel Bridge"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:97(td)
+msgid "vxlan_id_ranges = 5000:10000"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:98(td)
+msgid "(StrOpt) N1K VXLAN ID Ranges"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:101(th)
+msgid "[CISCO_PLUGINS]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:104(td)
+msgid "nexus_plugin = neutron.plugins.cisco.nexus.cisco_nexus_plugin_v2.NexusPlugin"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:105(td)
+msgid "(StrOpt) Nexus Switch to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:108(td)
+msgid "vswitch_plugin = neutron.plugins.openvswitch.ovs_neutron_plugin.OVSNeutronPluginV2"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:109(td)
+msgid "(StrOpt) Virtual Switch to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:112(th)
+msgid "[cisco_csr_ipsec]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:115(td)
+msgid "status_check_interval = 60"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:116(td)
+msgid "(IntOpt) Status check interval for Cisco CSR IPSec connections"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml:119(th) ./doc/common/tables/neutron-ml2_cisco.xml:19(th)
+msgid "[ml2_cisco]"
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml:8(caption) ./doc/common/tables/neutron-testing.xml:8(caption) ./doc/common/tables/glance-testing.xml:8(caption)
+msgid "Description of configuration options for testing"
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml:22(td) ./doc/common/tables/keystone-rpc.xml:22(td) ./doc/common/tables/cinder-rpc.xml:22(td)
+msgid "allowed_rpc_exception_modules = oslo.messaging.exceptions, nova.exception, cinder.exception, exceptions"
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml:23(td) ./doc/common/tables/keystone-rpc.xml:23(td) ./doc/common/tables/ceilometer-rpc.xml:23(td) ./doc/common/tables/cinder-rpc.xml:23(td) ./doc/common/tables/heat-rpc.xml:23(td) ./doc/common/tables/neutron-common.xml:39(td)
+msgid "(ListOpt) Modules of exceptions that are permitted to be recreated upon receiving exception data from an rpc call."
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml:26(td) ./doc/common/tables/ceilometer-common.xml:22(td) ./doc/common/tables/cinder-api.xml:30(td) ./doc/common/tables/heat-debug.xml:22(td) ./doc/common/tables/neutron-testing.xml:22(td) ./doc/common/tables/glance-wsgi.xml:22(td) ./doc/common/tables/trove-debug.xml:22(td) ./doc/common/tables/keystone-debug.xml:22(td)
+msgid "backdoor_port = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml:27(td)
+msgid "(StrOpt) Enable eventlet backdoor. Acceptable values are 0, &lt;port&gt; and &lt;start&gt;:&lt;end&gt;, where 0 results in listening on a random tcp port number, &lt;port&gt; results in listening on the specified port number and not enabling backdoorif it is in use and &lt;start&gt;:&lt;end&gt; results in listening on the smallest unused port number within the specified range of port numbers. The chosen port is displayed in the service's log file."
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml:30(td)
+msgid "fake_call = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml:31(td)
+msgid "(BoolOpt) If True, skip using the queue and make local calls"
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml:34(td)
+msgid "fake_network = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml:35(td)
+msgid "(BoolOpt) If passed, use fake network devices and addresses"
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml:38(td) ./doc/common/tables/trove-amqp.xml:38(td) ./doc/common/tables/keystone-rabbit.xml:22(td) ./doc/common/tables/heat-amqp.xml:42(td) ./doc/common/tables/glance-rabbitmq.xml:26(td) ./doc/common/tables/neutron-testing.xml:26(td) ./doc/common/tables/cinder-rpc.xml:42(td) ./doc/common/tables/ceilometer-rabbitmq.xml:22(td)
+msgid "fake_rabbit = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml:39(td) ./doc/common/tables/keystone-rabbit.xml:23(td) ./doc/common/tables/glance-rabbitmq.xml:27(td) ./doc/common/tables/cinder-rpc.xml:43(td)
+msgid "(BoolOpt) If passed, use a fake RabbitMQ provider."
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml:42(td) ./doc/common/tables/cinder-common.xml:110(td)
+msgid "monkey_patch = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml:43(td)
+msgid "(BoolOpt) Whether to log monkey patching"
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml:46(td)
+msgid "monkey_patch_modules = nova.api.ec2.cloud:nova.notifications.notify_decorator, nova.compute.api:nova.notifications.notify_decorator"
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml:47(td) ./doc/common/tables/cinder-common.xml:115(td)
+msgid "(ListOpt) List of modules/decorators to monkey patch"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml:8(caption) ./doc/common/tables/neutron-metadata.xml:8(caption)
+msgid "Description of configuration options for metadata"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml:22(td)
+msgid "metadata_host = $my_ip"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml:23(td)
+msgid "(StrOpt) The IP address for the metadata API server"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml:26(td)
+msgid "metadata_listen = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml:27(td)
+msgid "(StrOpt) The IP address on which the metadata API will listen."
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml:30(td)
+msgid "metadata_listen_port = 8775"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml:31(td)
+msgid "(IntOpt) The port on which the metadata API will listen."
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml:34(td)
+msgid "metadata_manager = nova.api.manager.MetadataManager"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml:35(td)
+msgid "(StrOpt) OpenStack metadata service manager"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml:38(td)
+msgid "metadata_port = 8775"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml:39(td)
+msgid "(IntOpt) The port for the metadata API port"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml:42(td)
+msgid "metadata_workers = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml:43(td)
+msgid "(IntOpt) Number of workers for metadata service. The default will be the number of CPUs available."
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml:46(td)
+msgid "vendordata_driver = nova.api.metadata.vendordata_json.JsonFileVendorData"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml:47(td)
+msgid "(StrOpt) Driver to use for vendor data"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml:50(td)
+msgid "vendordata_jsonfile_path = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml:51(td)
+msgid "(StrOpt) File to load json formatted vendor data from"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_nova.xml:8(caption)
+msgid "Description of configuration options for clients_nova"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_nova.xml:19(th)
+msgid "[clients_nova]"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml:8(caption)
+msgid "Description of configuration options for hp3par"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml:22(td)
+msgid "hp3par_api_url ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml:23(td)
+msgid "(StrOpt) 3PAR WSAPI Server Url like https://&lt;3par ip&gt;:8080/api/v1"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml:26(td)
+msgid "hp3par_cpg = OpenStack"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml:27(td)
+msgid "(StrOpt) The CPG to use for volume creation"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml:30(td)
+msgid "hp3par_cpg_snap ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml:31(td)
+msgid "(StrOpt) The CPG to use for Snapshots for volumes. If empty hp3par_cpg will be used"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml:34(td)
+msgid "hp3par_debug = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml:35(td)
+msgid "(BoolOpt) Enable HTTP debugging to 3PAR"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml:38(td)
+msgid "hp3par_iscsi_ips ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml:39(td)
+msgid "(ListOpt) List of target iSCSI addresses to use."
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml:42(td)
+msgid "hp3par_password ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml:43(td)
+msgid "(StrOpt) 3PAR Super user password"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml:46(td)
+msgid "hp3par_snapshot_expiration ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml:47(td)
+msgid "(StrOpt) The time in hours when a snapshot expires and is deleted. This must be larger than expiration"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml:50(td)
+msgid "hp3par_snapshot_retention ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml:51(td)
+msgid "(StrOpt) The time in hours to retain a snapshot. You can't delete it before this expires."
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml:54(td)
+msgid "hp3par_username ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml:55(td)
+msgid "(StrOpt) 3PAR Super user username"
+msgstr ""
+
+#: ./doc/common/tables/keystone-misc.xml:8(caption)
+msgid "Description of configuration options for misc"
+msgstr ""
+
+#: ./doc/common/tables/keystone-misc.xml:22(td) ./doc/common/tables/ceilometer-common.xml:34(td) ./doc/common/tables/nova-common.xml:46(td) ./doc/common/tables/trove-common.xml:58(td) ./doc/common/tables/cinder-common.xml:70(td) ./doc/common/tables/heat-debug.xml:38(td) ./doc/common/tables/glance-common.xml:70(td) ./doc/common/tables/neutron-common.xml:142(td)
+msgid "lock_path = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-misc.xml:23(td) ./doc/common/tables/ceilometer-common.xml:35(td) ./doc/common/tables/nova-common.xml:47(td) ./doc/common/tables/trove-common.xml:59(td) ./doc/common/tables/heat-debug.xml:39(td) ./doc/common/tables/glance-common.xml:71(td) ./doc/common/tables/neutron-common.xml:143(td)
+msgid "(StrOpt) Directory to use for lock files."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:7(literal)
+msgid "[filter:cname_lookup]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:18(td)
+msgid "use = egg:swift#cname_lookup"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:18(td) ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-slo.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-cache.xml:18(td) ./doc/common/tables/swift-container-server-filter-recon.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml:18(td) ./doc/common/tables/swift-account-server-filter-healthcheck.xml:18(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml:18(td) ./doc/common/tables/swift-container-server-filter-healthcheck.xml:18(td) ./doc/common/tables/swift-object-server-filter-healthcheck.xml:18(td) ./doc/common/tables/swift-object-server-app-object-server.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-name_check.xml:18(td) ./doc/common/tables/swift-account-server-filter-recon.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-dlo.xml:18(td) ./doc/common/tables/swift-account-server-app-account-server.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-formpost.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:18(td) ./doc/common/tables/swift-object-expirer-filter-cache.xml:18(td) ./doc/common/tables/swift-container-server-app-container-server.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-staticweb.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:18(td) ./doc/common/tables/swift-object-expirer-app-proxy-server.xml:18(td) ./doc/common/tables/swift-object-server-filter-recon.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-container_sync.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml:18(td)
+msgid "Entry point of paste.deploy in the server"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:21(td)
+msgid "set log_name = cname_lookup"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-cache.xml:21(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:21(td) ./doc/common/tables/swift-object-server-app-object-server.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:21(td) ./doc/common/tables/swift-account-server-app-account-server.xml:21(td) ./doc/common/tables/swift-container-server-app-container-server.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:21(td)
+msgid "Label to use when logging"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-cache.xml:24(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:24(td) ./doc/common/tables/swift-object-server-app-object-server.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:24(td) ./doc/common/tables/swift-account-server-app-account-server.xml:24(td) ./doc/common/tables/swift-container-server-app-container-server.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:24(td)
+msgid "set log_facility = LOG_LOCAL0"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-cache.xml:27(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:27(td) ./doc/common/tables/swift-object-server-app-object-server.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:27(td) ./doc/common/tables/swift-account-server-app-account-server.xml:27(td) ./doc/common/tables/swift-container-server-app-container-server.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:27(td)
+msgid "set log_level = INFO"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-cache.xml:27(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:27(td) ./doc/common/tables/swift-object-server-app-object-server.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:27(td) ./doc/common/tables/swift-account-server-app-account-server.xml:27(td) ./doc/common/tables/swift-container-server-app-container-server.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:27(td)
+msgid "Log level"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-cache.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:30(td)
+msgid "set log_headers = false"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-cache.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:30(td)
+msgid "If True, log headers in each request"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-cache.xml:33(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:30(td) ./doc/common/tables/swift-object-server-app-object-server.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:33(td) ./doc/common/tables/swift-account-server-app-account-server.xml:33(td) ./doc/common/tables/swift-container-server-app-container-server.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:33(td)
+msgid "set log_address = /dev/log"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:36(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:36(td)
+msgid "storage_domain = example.com"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:36(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:36(td)
+msgid "Domain that matches your cloud. Multiple domains can be specified using a comma-separated list."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:40(td)
+msgid "lookup_depth = 1"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:40(td)
+msgid "Because CNAMES can be recursive, specifies the number of levels through which to search."
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml:8(caption) ./doc/common/tables/cinder-scheduler.xml:8(caption)
+msgid "Description of configuration options for scheduler"
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml:22(td)
+msgid "network_auto_schedule = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml:23(td)
+msgid "(BoolOpt) Allow auto scheduling networks to DHCP agent."
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml:26(td)
+msgid "network_scheduler_driver = neutron.scheduler.dhcp_agent_scheduler.ChanceScheduler"
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml:27(td)
+msgid "(StrOpt) Driver to use for scheduling network to DHCP agent"
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml:30(td)
+msgid "router_auto_schedule = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml:31(td)
+msgid "(BoolOpt) Allow auto scheduling of routers to L3 agent."
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml:34(td)
+msgid "router_delete_namespaces = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml:35(td)
+msgid "(BoolOpt) Delete namespace after removing a router."
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml:38(td)
+msgid "router_scheduler_driver = neutron.scheduler.l3_agent_scheduler.ChanceScheduler"
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml:39(td)
+msgid "(StrOpt) Driver to use for scheduling router to a default L3 agent"
+msgstr ""
+
+#: ./doc/common/tables/glance-rbd.xml:8(caption)
+msgid "Description of configuration options for rbd"
+msgstr ""
+
+#: ./doc/common/tables/glance-rbd.xml:22(td)
+msgid "rbd_store_ceph_conf = /etc/ceph/ceph.conf"
+msgstr ""
+
+#: ./doc/common/tables/glance-rbd.xml:23(td)
+msgid "(StrOpt) Ceph configuration file path. If &lt;None&gt;, librados will locate the default config. If using cephx authentication, this file should include a reference to the right keyring in a client.&lt;USER&gt; section."
+msgstr ""
+
+#: ./doc/common/tables/glance-rbd.xml:26(td)
+msgid "rbd_store_chunk_size = 8"
+msgstr ""
+
+#: ./doc/common/tables/glance-rbd.xml:27(td)
+msgid "(IntOpt) RADOS images will be chunked into objects of this size (in megabytes). For best performance, this should be a power of two."
+msgstr ""
+
+#: ./doc/common/tables/glance-rbd.xml:30(td)
+msgid "rbd_store_pool = images"
+msgstr ""
+
+#: ./doc/common/tables/glance-rbd.xml:31(td)
+msgid "(StrOpt) RADOS pool in which images are stored."
+msgstr ""
+
+#: ./doc/common/tables/glance-rbd.xml:34(td)
+msgid "rbd_store_user = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-rbd.xml:35(td)
+msgid "(StrOpt) RADOS user to authenticate as (only applicable if using Cephx. If &lt;None&gt;, a default will be chosen based on the client. section in rbd_store_ceph_conf)."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml:8(caption)
+msgid "Description of configuration options for storage_xen"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml:22(td)
+msgid "xenapi_connection_password = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml:23(td)
+msgid "(StrOpt) Password for XenAPI connection"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml:26(td)
+msgid "xenapi_connection_url = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml:27(td)
+msgid "(StrOpt) URL for XenAPI connection"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml:30(td) ./doc/common/tables/neutron-rootwrap.xml:49(td)
+msgid "xenapi_connection_username = root"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml:31(td)
+msgid "(StrOpt) Username for XenAPI connection"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml:34(td)
+msgid "xenapi_nfs_server = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml:35(td)
+msgid "(StrOpt) NFS server to be used by XenAPINFSDriver"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml:38(td)
+msgid "xenapi_nfs_serverpath = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml:39(td)
+msgid "(StrOpt) Path of exported NFS, used by XenAPINFSDriver"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml:42(td)
+msgid "xenapi_sr_base_path = /var/run/sr-mount"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml:43(td) ./doc/common/tables/nova-xen.xml:177(td)
+msgid "(StrOpt) Base path to the storage repository"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-common.xml:8(caption) ./doc/common/tables/heat-common.xml:8(caption) ./doc/common/tables/nova-common.xml:8(caption) ./doc/common/tables/trove-common.xml:8(caption) ./doc/common/tables/cinder-common.xml:8(caption) ./doc/common/tables/glance-common.xml:8(caption) ./doc/common/tables/neutron-common.xml:8(caption)
+msgid "Description of configuration options for common"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-common.xml:23(td) ./doc/common/tables/cinder-api.xml:31(td) ./doc/common/tables/heat-debug.xml:23(td) ./doc/common/tables/neutron-testing.xml:23(td) ./doc/common/tables/trove-debug.xml:23(td) ./doc/common/tables/keystone-debug.xml:23(td)
+msgid "(StrOpt) Enable eventlet backdoor. Acceptable values are 0, &lt;port&gt;, and &lt;start&gt;:&lt;end&gt;, where 0 results in listening on a random tcp port number; &lt;port&gt; results in listening on the specified port number (and not enabling backdoor if that port is in use); and &lt;start&gt;:&lt;end&gt; results in listening on the smallest unused port number within the specified range of port numbers. The chosen port is displayed in the service's log file."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-common.xml:26(td) ./doc/common/tables/nova-common.xml:38(td) ./doc/common/tables/cinder-common.xml:42(td) ./doc/common/tables/heat-debug.xml:30(td) ./doc/common/tables/glance-common.xml:46(td) ./doc/common/tables/neutron-common.xml:122(td) ./doc/common/tables/trove-debug.xml:34(td) ./doc/common/tables/keystone-debug.xml:30(td)
+msgid "disable_process_locking = False"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-common.xml:27(td)
+msgid "(BoolOpt) Whether to disable inter-process locks."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-common.xml:30(td) ./doc/common/tables/neutron-logging.xml:30(td) ./doc/common/tables/glance-logging.xml:30(td) ./doc/common/tables/cinder-common.xml:50(td) ./doc/common/tables/heat-debug.xml:34(td) ./doc/common/tables/nova-logging.xml:30(td) ./doc/common/tables/trove-debug.xml:38(td) ./doc/common/tables/keystone-debug.xml:34(td)
+msgid "fatal_deprecations = False"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-common.xml:31(td) ./doc/common/tables/glance-logging.xml:31(td) ./doc/common/tables/cinder-common.xml:51(td) ./doc/common/tables/keystone-debug.xml:35(td)
+msgid "(BoolOpt) Make deprecations fatal"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-common.xml:42(td)
+msgid "notification_workers = 1"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-common.xml:43(td)
+msgid "(IntOpt) Number of workers for notification service. A single notification agent is enabled by default."
+msgstr ""
+
+#: ./doc/common/tables/cinder-database.xml:22(td) ./doc/common/tables/nova-baremetal.xml:22(td) ./doc/common/tables/heat-database.xml:22(td)
+msgid "db_backend = sqlalchemy"
+msgstr ""
+
+#: ./doc/common/tables/cinder-database.xml:26(td)
+msgid "db_driver = cinder.db"
+msgstr ""
+
+#: ./doc/common/tables/cinder-database.xml:27(td)
+msgid "(StrOpt) driver to use for database access"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:8(caption) ./doc/common/tables/neutron-logging.xml:8(caption) ./doc/common/tables/glance-logging.xml:8(caption) ./doc/common/tables/keystone-logging.xml:8(caption) ./doc/common/tables/heat-logging.xml:8(caption) ./doc/common/tables/nova-logging.xml:8(caption) ./doc/common/tables/trove-logging.xml:8(caption)
+msgid "Description of configuration options for logging"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:22(td) ./doc/common/tables/neutron-logging.xml:22(td) ./doc/common/tables/glance-logging.xml:22(td) ./doc/common/tables/cinder-common.xml:26(td) ./doc/common/tables/heat-debug.xml:26(td) ./doc/common/tables/nova-logging.xml:22(td) ./doc/common/tables/trove-debug.xml:30(td) ./doc/common/tables/keystone-debug.xml:26(td)
+msgid "debug = False"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:23(td) ./doc/common/tables/neutron-logging.xml:23(td) ./doc/common/tables/glance-logging.xml:23(td) ./doc/common/tables/cinder-common.xml:27(td) ./doc/common/tables/heat-debug.xml:27(td) ./doc/common/tables/nova-logging.xml:23(td) ./doc/common/tables/trove-debug.xml:31(td) ./doc/common/tables/keystone-debug.xml:27(td)
+msgid "(BoolOpt) Print debugging output (set logging level to DEBUG instead of default WARNING level)."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:26(td) ./doc/common/tables/glance-logging.xml:26(td) ./doc/common/tables/keystone-logging.xml:22(td)
+msgid "default_log_levels = amqp=WARN, amqplib=WARN, boto=WARN, qpid=WARN, sqlalchemy=WARN, suds=INFO, iso8601=WARN, requests.packages.urllib3.connectionpool=WARN"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:27(td) ./doc/common/tables/glance-logging.xml:27(td) ./doc/common/tables/cinder-common.xml:35(td) ./doc/common/tables/keystone-logging.xml:23(td)
+msgid "(ListOpt) List of logger=LEVEL pairs"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:30(td) ./doc/common/tables/nova-compute.xml:54(td) ./doc/common/tables/heat-amqp.xml:34(td) ./doc/common/tables/trove-common.xml:42(td) ./doc/common/tables/neutron-notifier.xml:22(td)
+msgid "default_notification_level = INFO"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:31(td) ./doc/common/tables/nova-compute.xml:55(td) ./doc/common/tables/heat-amqp.xml:35(td) ./doc/common/tables/trove-common.xml:43(td) ./doc/common/tables/neutron-notifier.xml:23(td)
+msgid "(StrOpt) Default notification level for outgoing notifications"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:34(td) ./doc/common/tables/neutron-logging.xml:34(td) ./doc/common/tables/glance-logging.xml:34(td) ./doc/common/tables/keystone-logging.xml:26(td) ./doc/common/tables/cinder-images.xml:62(td) ./doc/common/tables/heat-logging.xml:26(td) ./doc/common/tables/nova-logging.xml:38(td) ./doc/common/tables/trove-logging.xml:26(td)
+msgid "instance_format = \"[instance: %(uuid)s] \""
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:35(td) ./doc/common/tables/neutron-logging.xml:35(td) ./doc/common/tables/glance-logging.xml:35(td) ./doc/common/tables/keystone-logging.xml:27(td) ./doc/common/tables/cinder-images.xml:63(td) ./doc/common/tables/heat-logging.xml:27(td) ./doc/common/tables/nova-logging.xml:39(td) ./doc/common/tables/trove-logging.xml:27(td)
+msgid "(StrOpt) If an instance is passed with the log message, format it like this"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:38(td) ./doc/common/tables/neutron-logging.xml:38(td) ./doc/common/tables/glance-logging.xml:38(td) ./doc/common/tables/keystone-logging.xml:30(td) ./doc/common/tables/cinder-images.xml:66(td) ./doc/common/tables/heat-logging.xml:30(td) ./doc/common/tables/nova-logging.xml:42(td) ./doc/common/tables/trove-logging.xml:30(td)
+msgid "instance_uuid_format = \"[instance: %(uuid)s] \""
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:39(td) ./doc/common/tables/neutron-logging.xml:39(td) ./doc/common/tables/glance-logging.xml:39(td) ./doc/common/tables/keystone-logging.xml:31(td) ./doc/common/tables/cinder-images.xml:67(td) ./doc/common/tables/heat-logging.xml:31(td) ./doc/common/tables/nova-logging.xml:43(td) ./doc/common/tables/trove-logging.xml:31(td)
+msgid "(StrOpt) If an instance UUID is passed with the log message, format it like this"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:42(td) ./doc/common/tables/neutron-logging.xml:42(td) ./doc/common/tables/glance-logging.xml:42(td) ./doc/common/tables/cinder-common.xml:74(td) ./doc/common/tables/keystone-logging.xml:34(td) ./doc/common/tables/heat-logging.xml:34(td) ./doc/common/tables/nova-logging.xml:46(td) ./doc/common/tables/trove-logging.xml:34(td)
+msgid "log_config_append = None"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:43(td) ./doc/common/tables/neutron-logging.xml:43(td) ./doc/common/tables/glance-logging.xml:43(td) ./doc/common/tables/cinder-common.xml:75(td) ./doc/common/tables/keystone-logging.xml:35(td) ./doc/common/tables/heat-logging.xml:35(td) ./doc/common/tables/nova-logging.xml:47(td) ./doc/common/tables/trove-logging.xml:35(td)
+msgid "(StrOpt) The name of logging configuration file. It does not disable existing loggers, but just appends specified logging configuration to any other existing logging options. Please see the Python logging module documentation for details on logging configuration files."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:46(td) ./doc/common/tables/neutron-logging.xml:46(td) ./doc/common/tables/glance-logging.xml:46(td) ./doc/common/tables/cinder-common.xml:78(td) ./doc/common/tables/keystone-logging.xml:38(td) ./doc/common/tables/heat-logging.xml:38(td) ./doc/common/tables/nova-logging.xml:50(td) ./doc/common/tables/trove-logging.xml:38(td)
+msgid "log_date_format = %Y-%m-%d %H:%M:%S"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:47(td) ./doc/common/tables/neutron-logging.xml:47(td) ./doc/common/tables/glance-logging.xml:47(td) ./doc/common/tables/cinder-common.xml:79(td) ./doc/common/tables/keystone-logging.xml:39(td) ./doc/common/tables/heat-logging.xml:39(td) ./doc/common/tables/nova-logging.xml:51(td) ./doc/common/tables/trove-logging.xml:39(td)
+msgid "(StrOpt) Format string for %%(asctime)s in log records. Default: %(default)s"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:50(td) ./doc/common/tables/neutron-logging.xml:50(td) ./doc/common/tables/glance-logging.xml:50(td) ./doc/common/tables/cinder-common.xml:82(td) ./doc/common/tables/keystone-logging.xml:42(td) ./doc/common/tables/heat-logging.xml:42(td) ./doc/common/tables/nova-logging.xml:54(td) ./doc/common/tables/trove-logging.xml:42(td)
+msgid "log_dir = None"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:51(td) ./doc/common/tables/neutron-logging.xml:51(td) ./doc/common/tables/glance-logging.xml:51(td) ./doc/common/tables/cinder-common.xml:83(td) ./doc/common/tables/keystone-logging.xml:43(td) ./doc/common/tables/heat-logging.xml:43(td) ./doc/common/tables/nova-logging.xml:55(td) ./doc/common/tables/trove-logging.xml:43(td)
+msgid "(StrOpt) (Optional) The base directory used for relative --log-file paths"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:54(td) ./doc/common/tables/neutron-logging.xml:54(td) ./doc/common/tables/glance-logging.xml:54(td) ./doc/common/tables/cinder-common.xml:86(td) ./doc/common/tables/keystone-logging.xml:46(td) ./doc/common/tables/heat-logging.xml:46(td) ./doc/common/tables/nova-logging.xml:58(td) ./doc/common/tables/trove-logging.xml:46(td)
+msgid "log_file = None"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:55(td) ./doc/common/tables/neutron-logging.xml:55(td) ./doc/common/tables/glance-logging.xml:55(td) ./doc/common/tables/cinder-common.xml:87(td) ./doc/common/tables/keystone-logging.xml:47(td) ./doc/common/tables/heat-logging.xml:47(td) ./doc/common/tables/nova-logging.xml:59(td) ./doc/common/tables/trove-logging.xml:47(td)
+msgid "(StrOpt) (Optional) Name of log file to output to. If no default is set, logging will go to stdout."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:58(td) ./doc/common/tables/neutron-logging.xml:58(td) ./doc/common/tables/glance-logging.xml:58(td) ./doc/common/tables/cinder-common.xml:90(td) ./doc/common/tables/keystone-logging.xml:50(td) ./doc/common/tables/heat-logging.xml:50(td) ./doc/common/tables/nova-logging.xml:62(td) ./doc/common/tables/trove-logging.xml:50(td)
+msgid "log_format = None"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:59(td) ./doc/common/tables/neutron-logging.xml:59(td) ./doc/common/tables/glance-logging.xml:59(td) ./doc/common/tables/cinder-common.xml:91(td) ./doc/common/tables/keystone-logging.xml:51(td) ./doc/common/tables/heat-logging.xml:51(td) ./doc/common/tables/nova-logging.xml:63(td) ./doc/common/tables/trove-logging.xml:51(td)
+msgid "(StrOpt) DEPRECATED. A logging.Formatter log message format string which may use any of the available logging.LogRecord attributes. This option is deprecated. Please use logging_context_format_string and logging_default_format_string instead."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:62(td) ./doc/common/tables/neutron-logging.xml:62(td) ./doc/common/tables/glance-logging.xml:62(td) ./doc/common/tables/cinder-common.xml:94(td) ./doc/common/tables/keystone-logging.xml:54(td) ./doc/common/tables/heat-logging.xml:54(td) ./doc/common/tables/trove-logging.xml:54(td)
+msgid "logging_context_format_string = %(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [%(request_id)s %(user_identity)s] %(instance)s%(message)s"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:63(td) ./doc/common/tables/glance-logging.xml:63(td) ./doc/common/tables/cinder-common.xml:95(td) ./doc/common/tables/keystone-logging.xml:55(td)
+msgid "(StrOpt) Format string to use for log messages with context"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:66(td) ./doc/common/tables/neutron-logging.xml:66(td) ./doc/common/tables/glance-logging.xml:66(td) ./doc/common/tables/cinder-common.xml:98(td) ./doc/common/tables/keystone-logging.xml:58(td) ./doc/common/tables/heat-logging.xml:58(td) ./doc/common/tables/nova-logging.xml:70(td) ./doc/common/tables/trove-logging.xml:58(td)
+msgid "logging_debug_format_suffix = %(funcName)s %(pathname)s:%(lineno)d"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:67(td) ./doc/common/tables/glance-logging.xml:67(td) ./doc/common/tables/cinder-common.xml:99(td) ./doc/common/tables/keystone-logging.xml:59(td)
+msgid "(StrOpt) Data to append to log format when level is DEBUG"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:70(td) ./doc/common/tables/neutron-logging.xml:70(td) ./doc/common/tables/glance-logging.xml:70(td) ./doc/common/tables/cinder-common.xml:102(td) ./doc/common/tables/keystone-logging.xml:62(td) ./doc/common/tables/heat-logging.xml:62(td) ./doc/common/tables/nova-logging.xml:74(td) ./doc/common/tables/trove-logging.xml:62(td)
+msgid "logging_default_format_string = %(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [-] %(instance)s%(message)s"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:71(td) ./doc/common/tables/glance-logging.xml:71(td) ./doc/common/tables/cinder-common.xml:103(td) ./doc/common/tables/keystone-logging.xml:63(td)
+msgid "(StrOpt) Format string to use for log messages without context"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:74(td) ./doc/common/tables/neutron-logging.xml:74(td) ./doc/common/tables/glance-logging.xml:74(td) ./doc/common/tables/cinder-common.xml:106(td) ./doc/common/tables/keystone-logging.xml:66(td) ./doc/common/tables/heat-logging.xml:66(td) ./doc/common/tables/nova-logging.xml:78(td) ./doc/common/tables/trove-logging.xml:66(td)
+msgid "logging_exception_prefix = %(asctime)s.%(msecs)03d %(process)d TRACE %(name)s %(instance)s"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:75(td) ./doc/common/tables/glance-logging.xml:75(td) ./doc/common/tables/cinder-common.xml:107(td) ./doc/common/tables/keystone-logging.xml:67(td)
+msgid "(StrOpt) Prefix each line of exception output with this format"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:78(td) ./doc/common/tables/neutron-logging.xml:78(td) ./doc/common/tables/heat-notification.xml:26(td) ./doc/common/tables/glance-logging.xml:78(td) ./doc/common/tables/cinder-rpc.xml:90(td) ./doc/common/tables/nova-logging.xml:82(td) ./doc/common/tables/trove-logging.xml:74(td) ./doc/common/tables/keystone-debug.xml:38(td)
+msgid "publish_errors = False"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:79(td) ./doc/common/tables/glance-logging.xml:79(td) ./doc/common/tables/cinder-rpc.xml:91(td) ./doc/common/tables/keystone-debug.xml:39(td)
+msgid "(BoolOpt) Publish error events"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:82(td) ./doc/common/tables/neutron-logging.xml:82(td) ./doc/common/tables/glance-logging.xml:82(td) ./doc/common/tables/cinder-common.xml:194(td) ./doc/common/tables/keystone-logging.xml:70(td) ./doc/common/tables/heat-logging.xml:70(td) ./doc/common/tables/nova-logging.xml:86(td) ./doc/common/tables/trove-logging.xml:78(td)
+msgid "syslog_log_facility = LOG_USER"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:83(td) ./doc/common/tables/glance-logging.xml:83(td) ./doc/common/tables/cinder-common.xml:195(td) ./doc/common/tables/keystone-logging.xml:71(td)
+msgid "(StrOpt) Syslog facility to receive log lines"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:86(td) ./doc/common/tables/neutron-logging.xml:90(td) ./doc/common/tables/glance-logging.xml:86(td) ./doc/common/tables/cinder-common.xml:210(td) ./doc/common/tables/keystone-logging.xml:74(td) ./doc/common/tables/heat-logging.xml:74(td) ./doc/common/tables/nova-logging.xml:90(td) ./doc/common/tables/trove-logging.xml:82(td)
+msgid "use_stderr = True"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:87(td) ./doc/common/tables/neutron-logging.xml:91(td) ./doc/common/tables/glance-logging.xml:87(td) ./doc/common/tables/cinder-common.xml:211(td) ./doc/common/tables/keystone-logging.xml:75(td) ./doc/common/tables/heat-logging.xml:75(td) ./doc/common/tables/nova-logging.xml:91(td) ./doc/common/tables/trove-logging.xml:83(td)
+msgid "(BoolOpt) Log output to standard error"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:90(td) ./doc/common/tables/neutron-logging.xml:94(td) ./doc/common/tables/neutron-rootwrap.xml:30(td) ./doc/common/tables/nova-rootwrap.xml:30(td) ./doc/common/tables/glance-logging.xml:90(td) ./doc/common/tables/cinder-common.xml:214(td) ./doc/common/tables/keystone-logging.xml:78(td) ./doc/common/tables/heat-logging.xml:78(td) ./doc/common/tables/nova-logging.xml:94(td) ./doc/common/tables/trove-logging.xml:86(td) ./doc/common/tables/cinder-rootwrap.xml:30(td)
+msgid "use_syslog = False"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:91(td) ./doc/common/tables/glance-logging.xml:91(td) ./doc/common/tables/cinder-common.xml:215(td) ./doc/common/tables/keystone-logging.xml:79(td) ./doc/common/tables/nova-logging.xml:95(td)
+msgid "(BoolOpt) Use syslog for logging. Existing syslog format is DEPRECATED during I, and then will be changed in J to honor RFC5424"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:94(td) ./doc/common/tables/glance-logging.xml:94(td) ./doc/common/tables/cinder-common.xml:218(td) ./doc/common/tables/keystone-logging.xml:82(td) ./doc/common/tables/nova-logging.xml:98(td)
+msgid "use_syslog_rfc_format = False"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:95(td) ./doc/common/tables/glance-logging.xml:95(td) ./doc/common/tables/cinder-common.xml:219(td) ./doc/common/tables/keystone-logging.xml:83(td) ./doc/common/tables/nova-logging.xml:99(td)
+msgid "(BoolOpt) (Optional) Use syslog rfc5424 format for logging. If enabled, will add APP-NAME (RFC5424) before the MSG part of the syslog message. The old format without APP-NAME is deprecated in I, and will be removed in J."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:98(td) ./doc/common/tables/neutron-logging.xml:98(td) ./doc/common/tables/glance-logging.xml:98(td) ./doc/common/tables/cinder-common.xml:222(td) ./doc/common/tables/keystone-logging.xml:86(td) ./doc/common/tables/heat-logging.xml:82(td) ./doc/common/tables/nova-logging.xml:102(td) ./doc/common/tables/trove-debug.xml:78(td)
+msgid "verbose = False"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:99(td) ./doc/common/tables/neutron-logging.xml:99(td) ./doc/common/tables/glance-logging.xml:99(td) ./doc/common/tables/cinder-common.xml:223(td) ./doc/common/tables/keystone-logging.xml:87(td) ./doc/common/tables/heat-logging.xml:83(td) ./doc/common/tables/nova-logging.xml:103(td) ./doc/common/tables/trove-debug.xml:79(td)
+msgid "(BoolOpt) Print more verbose output (set logging level to INFO instead of default WARNING level)."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:102(th) ./doc/common/tables/neutron-cadf.xml:19(th) ./doc/common/tables/keystone-debug.xml:54(th)
+msgid "[audit]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:105(td) ./doc/common/tables/neutron-cadf.xml:22(td)
+msgid "api_audit_map = api_audit_map.conf"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:106(td) ./doc/common/tables/neutron-cadf.xml:23(td)
+msgid "(StrOpt) File containing mapping for api paths and service endpoints"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:109(td) ./doc/common/tables/neutron-cadf.xml:26(td) ./doc/common/tables/keystone-debug.xml:57(td)
+msgid "namespace = openstack"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml:110(td) ./doc/common/tables/neutron-cadf.xml:27(td) ./doc/common/tables/keystone-debug.xml:58(td)
+msgid "(StrOpt) namespace prefix for generated id"
+msgstr ""
+
+#: ./doc/common/tables/heat-common.xml:22(td)
+msgid "deferred_auth_method = password"
+msgstr ""
+
+#: ./doc/common/tables/heat-common.xml:23(td)
+msgid "(StrOpt) Select deferred auth method, stored password or trusts."
+msgstr ""
+
+#: ./doc/common/tables/heat-common.xml:26(td)
+msgid "environment_dir = /etc/heat/environment.d"
+msgstr ""
+
+#: ./doc/common/tables/heat-common.xml:27(td)
+msgid "(StrOpt) The directory to search for environment files."
+msgstr ""
+
+#: ./doc/common/tables/heat-common.xml:30(td)
+msgid "event_purge_batch_size = 10"
+msgstr ""
+
+#: ./doc/common/tables/heat-common.xml:31(td)
+msgid "(IntOpt) Controls how many events will be pruned whenever a stack's events exceed max_events_per_stack. Set this lower to keep more events at the expense of more frequent purges."
+msgstr ""
+
+#: ./doc/common/tables/heat-common.xml:34(td)
+msgid "instance_driver = heat.engine.nova"
+msgstr ""
+
+#: ./doc/common/tables/heat-common.xml:35(td)
+msgid "(StrOpt) Driver to use for controlling instances."
+msgstr ""
+
+#: ./doc/common/tables/heat-common.xml:38(td)
+msgid "instance_user = ec2-user"
+msgstr ""
+
+#: ./doc/common/tables/heat-common.xml:39(td)
+msgid "(StrOpt) The default user for new instances. This option is deprecated and will be removed in the Juno release. If it's empty, Heat will use the default user set up with your cloud image (for OS::Nova::Server) or 'ec2-user' (for AWS::EC2::Instance)."
+msgstr ""
+
+#: ./doc/common/tables/heat-common.xml:42(td)
+msgid "keystone_backend = heat.common.heat_keystoneclient.KeystoneClientV3"
+msgstr ""
+
+#: ./doc/common/tables/heat-common.xml:43(td)
+msgid "(StrOpt) Fully qualified class name to use as a keystone backend."
+msgstr ""
+
+#: ./doc/common/tables/heat-common.xml:46(td) ./doc/common/tables/cinder-common.xml:134(td) ./doc/common/tables/trove-rpc.xml:42(td)
+msgid "periodic_interval = 60"
+msgstr ""
+
+#: ./doc/common/tables/heat-common.xml:47(td)
+msgid "(IntOpt) Seconds between running periodic tasks."
+msgstr ""
+
+#: ./doc/common/tables/heat-common.xml:50(td)
+msgid "plugin_dirs = /usr/lib64/heat, /usr/lib/heat"
+msgstr ""
+
+#: ./doc/common/tables/heat-common.xml:51(td)
+msgid "(ListOpt) List of directories to search for plug-ins."
+msgstr ""
+
+#: ./doc/common/tables/heat-common.xml:54(th)
+msgid "[revision]"
+msgstr ""
+
+#: ./doc/common/tables/heat-common.xml:57(td)
+msgid "heat_revision = unknown"
+msgstr ""
+
+#: ./doc/common/tables/heat-common.xml:58(td)
+msgid "(StrOpt) Heat build revision. If you would prefer to manage your build revision separately, you can move this section to a different file and add it as another config option."
 msgstr ""
 
 #: ./doc/common/tables/nova-ipv6.xml:8(caption)
@@ -18327,92 +20367,64 @@ msgstr ""
 msgid "(BoolOpt) Use IPv6"
 msgstr ""
 
-#: ./doc/common/tables/cinder-eqlx.xml:8(caption)
-msgid "Description of configuration options for eqlx"
+#: ./doc/common/tables/nova-vnc.xml:8(caption)
+msgid "Description of configuration options for vnc"
 msgstr ""
 
-#: ./doc/common/tables/cinder-eqlx.xml:22(td)
-msgid "eqlx_chap_login = admin"
+#: ./doc/common/tables/nova-vnc.xml:22(td)
+msgid "novncproxy_base_url = http://127.0.0.1:6080/vnc_auto.html"
 msgstr ""
 
-#: ./doc/common/tables/cinder-eqlx.xml:23(td)
-msgid "(StrOpt) Existing CHAP account name"
+#: ./doc/common/tables/nova-vnc.xml:23(td)
+msgid "(StrOpt) Location of VNC console proxy, in the form \"http://127.0.0.1:6080/vnc_auto.html\""
 msgstr ""
 
-#: ./doc/common/tables/cinder-eqlx.xml:26(td)
-msgid "eqlx_chap_password = password"
+#: ./doc/common/tables/nova-vnc.xml:26(td)
+msgid "vnc_enabled = True"
 msgstr ""
 
-#: ./doc/common/tables/cinder-eqlx.xml:27(td)
-msgid "(StrOpt) Password for specified CHAP account name"
+#: ./doc/common/tables/nova-vnc.xml:27(td)
+msgid "(BoolOpt) Enable VNC related features"
 msgstr ""
 
-#: ./doc/common/tables/cinder-eqlx.xml:30(td)
-msgid "eqlx_cli_max_retries = 5"
+#: ./doc/common/tables/nova-vnc.xml:30(td)
+msgid "vnc_keymap = en-us"
 msgstr ""
 
-#: ./doc/common/tables/cinder-eqlx.xml:31(td)
-msgid "(IntOpt) Maximum retry count for reconnection"
+#: ./doc/common/tables/nova-vnc.xml:31(td)
+msgid "(StrOpt) Keymap for VNC"
 msgstr ""
 
-#: ./doc/common/tables/cinder-eqlx.xml:34(td)
-msgid "eqlx_cli_timeout = 30"
+#: ./doc/common/tables/nova-vnc.xml:34(td)
+msgid "vncserver_listen = 127.0.0.1"
 msgstr ""
 
-#: ./doc/common/tables/cinder-eqlx.xml:35(td)
-msgid "(IntOpt) Timeout for the Group Manager cli command execution"
+#: ./doc/common/tables/nova-vnc.xml:35(td)
+msgid "(StrOpt) IP address on which instance vncservers should listen"
 msgstr ""
 
-#: ./doc/common/tables/cinder-eqlx.xml:38(td)
-msgid "eqlx_group_name = group-0"
+#: ./doc/common/tables/nova-vnc.xml:38(td)
+msgid "vncserver_proxyclient_address = 127.0.0.1"
 msgstr ""
 
-#: ./doc/common/tables/cinder-eqlx.xml:39(td)
-msgid "(StrOpt) Group name to use for creating volumes"
+#: ./doc/common/tables/nova-vnc.xml:39(td)
+msgid "(StrOpt) The address to which proxy clients (like nova-xvpvncproxy) should connect"
 msgstr ""
 
-#: ./doc/common/tables/cinder-eqlx.xml:42(td)
-msgid "eqlx_pool = default"
+#: ./doc/common/tables/nova-vnc.xml:45(td)
+msgid "vnc_port = 5900"
 msgstr ""
 
-#: ./doc/common/tables/cinder-eqlx.xml:43(td)
-msgid "(StrOpt) Pool in which volumes will be created"
+#: ./doc/common/tables/nova-vnc.xml:46(td)
+msgid "(IntOpt) VNC starting port"
 msgstr ""
 
-#: ./doc/common/tables/cinder-eqlx.xml:46(td)
-msgid "eqlx_use_chap = False"
+#: ./doc/common/tables/nova-vnc.xml:49(td)
+msgid "vnc_port_total = 10000"
 msgstr ""
 
-#: ./doc/common/tables/cinder-eqlx.xml:47(td)
-msgid "(BoolOpt) Use CHAP authentication for targets?"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:7(literal)
-msgid "[filter:catch_errors]"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml:7(literal) ./doc/common/tables/swift-object-expirer-filter-cache.xml:7(literal) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:7(literal) ./doc/common/tables/swift-object-expirer-app-proxy-server.xml:7(literal) ./doc/common/tables/swift-object-expirer-pipeline-main.xml:7(literal) ./doc/common/tables/swift-object-expirer-object-expirer.xml:7(literal)
-msgid "object-expirer.conf-sample"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml:7(caption) ./doc/common/tables/swift-object-expirer-filter-cache.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-cache.xml:7(caption) ./doc/common/tables/swift-container-server-DEFAULT.xml:7(caption) ./doc/common/tables/swift-container-server-container-updater.xml:7(caption) ./doc/common/tables/swift-account-server-filter-recon.xml:7(caption) ./doc/common/tables/swift-container-server-container-replicator.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-name_check.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:7(caption) ./doc/common/tables/swift-container-server-container-sync.xml:7(caption) ./doc/common/tables/swift-object-server-object-auditor.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml:7(caption) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:7(caption) ./doc/common/tables/swift-object-server-object-updater.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml:7(caption) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-dlo.xml:7(caption) ./doc/common/tables/swift-container-server-pipeline-main.xml:7(caption) ./doc/common/tables/swift-rsyncd-object.xml:7(caption) ./doc/common/tables/swift-object-server-pipeline-main.xml:7(caption) ./doc/common/tables/swift-account-server-app-account-server.xml:7(caption) ./doc/common/tables/swift-account-server-filter-healthcheck.xml:7(caption) ./doc/common/tables/swift-container-server-app-container-server.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-slo.xml:7(caption) ./doc/common/tables/swift-account-server-account-auditor.xml:7(caption) ./doc/common/tables/swift-object-server-DEFAULT.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:7(caption) ./doc/common/tables/swift-account-server-DEFAULT.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:7(caption) ./doc/common/tables/swift-rsyncd-account.xml:7(caption) ./doc/common/tables/swift-container-sync-realms-realm1.xml:7(caption) ./doc/common/tables/swift-container-server-filter-healthcheck.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-container_sync.xml:7(caption) ./doc/common/tables/swift-swift-swift-constraints.xml:7(caption) ./doc/common/tables/swift-object-server-filter-recon.xml:7(caption) ./doc/common/tables/swift-container-server-container-auditor.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml:7(caption) ./doc/common/tables/swift-memcache-memcache.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:7(caption) ./doc/common/tables/swift-object-server-object-replicator.xml:7(caption) ./doc/common/tables/swift-dispersion-dispersion.xml:7(caption) ./doc/common/tables/swift-account-server-account-replicator.xml:7(caption) ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:7(caption) ./doc/common/tables/swift-object-server-app-object-server.xml:7(caption) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-staticweb.xml:7(caption) ./doc/common/tables/swift-object-expirer-app-proxy-server.xml:7(caption) ./doc/common/tables/swift-drive-audit-drive-audit.xml:7(caption) ./doc/common/tables/swift-container-server-filter-recon.xml:7(caption) ./doc/common/tables/swift-object-expirer-pipeline-main.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml:7(caption) ./doc/common/tables/swift-swift-swift-hash.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-formpost.xml:7(caption) ./doc/common/tables/swift-container-sync-realms-realm2.xml:7(caption) ./doc/common/tables/swift-rsyncd-container.xml:7(caption) ./doc/common/tables/swift-object-server-filter-healthcheck.xml:7(caption) ./doc/common/tables/swift-account-server-pipeline-main.xml:7(caption) ./doc/common/tables/swift-object-expirer-object-expirer.xml:7(caption) ./doc/common/tables/swift-proxy-server-pipeline-main.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:7(caption) ./doc/common/tables/swift-account-server-account-reaper.xml:7(caption) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:7(caption)
-msgid "Description of configuration options for <placeholder-1/> in <placeholder-2/>"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:18(td)
-msgid "use = egg:swift#catch_errors"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml:18(td) ./doc/common/tables/swift-object-expirer-filter-cache.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-cache.xml:18(td) ./doc/common/tables/swift-account-server-filter-recon.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-name_check.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml:18(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-dlo.xml:18(td) ./doc/common/tables/swift-account-server-app-account-server.xml:18(td) ./doc/common/tables/swift-account-server-filter-healthcheck.xml:18(td) ./doc/common/tables/swift-container-server-app-container-server.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-slo.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:18(td) ./doc/common/tables/swift-container-server-filter-healthcheck.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-container_sync.xml:18(td) ./doc/common/tables/swift-object-server-filter-recon.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:18(td) ./doc/common/tables/swift-object-server-app-object-server.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-staticweb.xml:18(td) ./doc/common/tables/swift-object-expirer-app-proxy-server.xml:18(td) ./doc/common/tables/swift-container-server-filter-recon.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-formpost.xml:18(td) ./doc/common/tables/swift-object-server-filter-healthcheck.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:18(td)
-msgid "Entry point of paste.deploy in the server"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-expirer-filter-cache.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-cache.xml:7(literal)
-msgid "[filter:cache]"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-expirer-filter-cache.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-cache.xml:18(td)
-msgid "use = egg:swift#memcache"
+#: ./doc/common/tables/nova-vnc.xml:50(td)
+msgid "(IntOpt) Total number of VNC ports"
 msgstr ""
 
 #: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml:5(caption)
@@ -18535,50 +20547,1726 @@ msgstr ""
 msgid "Limit the candidate volume list to only the ones that support thick provisioning on the storage controller."
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-name_check.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml:7(literal) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-dlo.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-slo.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-container_sync.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:7(literal) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-staticweb.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-formpost.xml:7(literal) ./doc/common/tables/swift-proxy-server-pipeline-main.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:7(literal)
-msgid "proxy-server.conf-sample"
+#: ./doc/common/tables/trove-qpid.xml:8(caption) ./doc/common/tables/heat-qpid.xml:8(caption) ./doc/common/tables/nova-qpid.xml:8(caption) ./doc/common/tables/glance-qpid.xml:8(caption) ./doc/common/tables/neutron-qpid.xml:8(caption) ./doc/common/tables/keystone-qpid.xml:8(caption) ./doc/common/tables/ceilometer-qpid.xml:8(caption)
+msgid "Description of configuration options for qpid"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml:22(td) ./doc/common/tables/heat-qpid.xml:22(td) ./doc/common/tables/nova-qpid.xml:22(td) ./doc/common/tables/glance-qpid.xml:22(td) ./doc/common/tables/cinder-rpc.xml:94(td) ./doc/common/tables/nova-rpc_all.xml:62(td) ./doc/common/tables/neutron-qpid.xml:22(td) ./doc/common/tables/keystone-qpid.xml:22(td) ./doc/common/tables/ceilometer-qpid.xml:22(td)
+msgid "qpid_heartbeat = 60"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml:23(td) ./doc/common/tables/heat-qpid.xml:23(td) ./doc/common/tables/neutron-qpid.xml:23(td) ./doc/common/tables/ceilometer-qpid.xml:23(td)
+msgid "(IntOpt) Seconds between connection keepalive heartbeats"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml:26(td) ./doc/common/tables/heat-qpid.xml:26(td) ./doc/common/tables/nova-qpid.xml:26(td) ./doc/common/tables/glance-qpid.xml:26(td) ./doc/common/tables/cinder-rpc.xml:98(td) ./doc/common/tables/nova-rpc_all.xml:66(td) ./doc/common/tables/neutron-qpid.xml:26(td) ./doc/common/tables/keystone-qpid.xml:26(td) ./doc/common/tables/ceilometer-qpid.xml:26(td)
+msgid "qpid_hostname = localhost"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml:27(td) ./doc/common/tables/heat-qpid.xml:27(td) ./doc/common/tables/neutron-qpid.xml:27(td) ./doc/common/tables/ceilometer-qpid.xml:27(td)
+msgid "(StrOpt) Qpid broker hostname"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml:30(td) ./doc/common/tables/heat-qpid.xml:30(td) ./doc/common/tables/nova-qpid.xml:30(td) ./doc/common/tables/glance-qpid.xml:30(td) ./doc/common/tables/cinder-rpc.xml:102(td) ./doc/common/tables/nova-rpc_all.xml:70(td) ./doc/common/tables/neutron-qpid.xml:30(td) ./doc/common/tables/keystone-qpid.xml:30(td) ./doc/common/tables/ceilometer-qpid.xml:30(td)
+msgid "qpid_hosts = $qpid_hostname:$qpid_port"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml:31(td) ./doc/common/tables/heat-qpid.xml:31(td) ./doc/common/tables/neutron-qpid.xml:31(td) ./doc/common/tables/ceilometer-qpid.xml:31(td)
+msgid "(ListOpt) Qpid HA cluster host:port pairs"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml:34(td) ./doc/common/tables/heat-qpid.xml:34(td) ./doc/common/tables/nova-qpid.xml:34(td) ./doc/common/tables/glance-qpid.xml:34(td) ./doc/common/tables/cinder-rpc.xml:106(td) ./doc/common/tables/nova-rpc_all.xml:74(td) ./doc/common/tables/neutron-qpid.xml:34(td) ./doc/common/tables/keystone-qpid.xml:34(td) ./doc/common/tables/ceilometer-qpid.xml:34(td)
+msgid "qpid_password ="
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml:35(td) ./doc/common/tables/heat-qpid.xml:35(td) ./doc/common/tables/neutron-qpid.xml:35(td) ./doc/common/tables/ceilometer-qpid.xml:35(td)
+msgid "(StrOpt) Password for qpid connection"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml:38(td) ./doc/common/tables/heat-qpid.xml:38(td) ./doc/common/tables/nova-qpid.xml:38(td) ./doc/common/tables/glance-qpid.xml:38(td) ./doc/common/tables/cinder-rpc.xml:110(td) ./doc/common/tables/nova-rpc_all.xml:78(td) ./doc/common/tables/neutron-qpid.xml:38(td) ./doc/common/tables/keystone-qpid.xml:38(td) ./doc/common/tables/ceilometer-qpid.xml:38(td)
+msgid "qpid_port = 5672"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml:39(td) ./doc/common/tables/heat-qpid.xml:39(td) ./doc/common/tables/neutron-qpid.xml:39(td) ./doc/common/tables/ceilometer-qpid.xml:39(td)
+msgid "(IntOpt) Qpid broker port"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml:42(td) ./doc/common/tables/heat-qpid.xml:42(td) ./doc/common/tables/nova-qpid.xml:42(td) ./doc/common/tables/glance-qpid.xml:42(td) ./doc/common/tables/cinder-rpc.xml:114(td) ./doc/common/tables/nova-rpc_all.xml:82(td) ./doc/common/tables/neutron-qpid.xml:42(td) ./doc/common/tables/keystone-qpid.xml:42(td) ./doc/common/tables/ceilometer-qpid.xml:42(td)
+msgid "qpid_protocol = tcp"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml:43(td) ./doc/common/tables/heat-qpid.xml:43(td) ./doc/common/tables/neutron-qpid.xml:43(td) ./doc/common/tables/ceilometer-qpid.xml:43(td)
+msgid "(StrOpt) Transport to use, either 'tcp' or 'ssl'"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml:46(td) ./doc/common/tables/heat-qpid.xml:46(td) ./doc/common/tables/nova-qpid.xml:46(td) ./doc/common/tables/glance-qpid.xml:46(td) ./doc/common/tables/cinder-rpc.xml:118(td) ./doc/common/tables/nova-rpc_all.xml:86(td) ./doc/common/tables/neutron-qpid.xml:46(td) ./doc/common/tables/keystone-qpid.xml:46(td) ./doc/common/tables/ceilometer-qpid.xml:46(td)
+msgid "qpid_sasl_mechanisms ="
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml:47(td) ./doc/common/tables/heat-qpid.xml:47(td) ./doc/common/tables/neutron-qpid.xml:47(td) ./doc/common/tables/ceilometer-qpid.xml:47(td)
+msgid "(StrOpt) Space separated list of SASL mechanisms to use for auth"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml:50(td) ./doc/common/tables/heat-qpid.xml:50(td) ./doc/common/tables/nova-qpid.xml:50(td) ./doc/common/tables/glance-qpid.xml:50(td) ./doc/common/tables/cinder-rpc.xml:122(td) ./doc/common/tables/nova-rpc_all.xml:90(td) ./doc/common/tables/neutron-qpid.xml:50(td) ./doc/common/tables/keystone-qpid.xml:50(td) ./doc/common/tables/ceilometer-qpid.xml:50(td)
+msgid "qpid_tcp_nodelay = True"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml:51(td) ./doc/common/tables/heat-qpid.xml:51(td) ./doc/common/tables/neutron-qpid.xml:51(td) ./doc/common/tables/ceilometer-qpid.xml:51(td)
+msgid "(BoolOpt) Disable Nagle algorithm"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml:54(td) ./doc/common/tables/heat-qpid.xml:58(td) ./doc/common/tables/nova-qpid.xml:58(td) ./doc/common/tables/glance-qpid.xml:58(td) ./doc/common/tables/cinder-rpc.xml:130(td) ./doc/common/tables/nova-rpc_all.xml:98(td) ./doc/common/tables/neutron-qpid.xml:58(td) ./doc/common/tables/keystone-qpid.xml:58(td) ./doc/common/tables/ceilometer-qpid.xml:58(td)
+msgid "qpid_username ="
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml:55(td) ./doc/common/tables/heat-qpid.xml:59(td) ./doc/common/tables/neutron-qpid.xml:59(td) ./doc/common/tables/ceilometer-qpid.xml:59(td)
+msgid "(StrOpt) Username for qpid connection"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:8(caption) ./doc/common/tables/trove-api.xml:8(caption) ./doc/common/tables/glance-api.xml:8(caption) ./doc/common/tables/ceilometer-api.xml:8(caption) ./doc/common/tables/heat-api.xml:8(caption) ./doc/common/tables/cinder-api.xml:8(caption) ./doc/common/tables/nova-api.xml:8(caption) ./doc/common/tables/neutron-api.xml:8(caption)
+msgid "Description of configuration options for api"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:22(td)
+msgid "admin_bind_host = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:23(td)
+msgid "(StrOpt) The IP Address of the network interface to for the admin service to listen on."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:26(td)
+msgid "admin_endpoint = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:27(td)
+msgid "(StrOpt) The base admin endpoint URL for keystone that are advertised to clients (NOTE: this does NOT affect how keystone listens for connections). Defaults to the base host URL of the request. Eg a request to http://server:35357/v2.0/users will default to http://server:35357. You should only need to set this value if the base URL contains a path (eg /prefix/v2.0) or the endpoint should be found on a different server."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:30(td)
+msgid "admin_port = 35357"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:31(td)
+msgid "(IntOpt) The port number which the admin service listens on."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:34(td)
+msgid "admin_token = ADMIN"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:35(td)
+msgid "(StrOpt) A \"shared secret\" that can be used to bootstrap Keystone. This \"token\" does not represent a user, and carries no explicit authorization. To disable in production (highly recommended), remove AdminTokenAuthMiddleware from your paste application pipelines (for example, in keystone-paste.ini)."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:38(td)
+msgid "compute_port = 8774"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:39(td)
+msgid "(IntOpt) The port which the OpenStack Compute service listens on."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:42(td)
+msgid "domain_id_immutable = True"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:43(td)
+msgid "(BoolOpt) Set this to false if you want to enable the ability for user, group and project entities to be moved between domains by updating their domain_id. Allowing such movement is not recommended if the scope of a domain admin is being restricted by use of an appropriate policy file (see policy.v3cloudsample as an example)."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:47(td)
+msgid "(IntOpt) The maximum number of entities that will be returned in a collection can be set with list_limit, with no limit set by default. This global limit may be then overridden for a specific driver, by specifying a list_limit in the appropriate section (e.g. [assignment])."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:50(td)
+msgid "max_param_size = 64"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:51(td)
+msgid "(IntOpt) limit the sizes of user &amp; tenant ID/names."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:54(td) ./doc/common/tables/ceilometer-api.xml:26(td) ./doc/common/tables/neutron-api.xml:46(td)
+msgid "max_request_body_size = 114688"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:55(td)
+msgid "(IntOpt) enforced by optional sizelimit middleware (keystone.middleware:RequestBodySizeLimiter)."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:58(td)
+msgid "max_token_size = 8192"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:59(td)
+msgid "(IntOpt) similar to max_param_size, but provides an exception for token values."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:62(td)
+msgid "member_role_id = 9fe2ff9ee4384b1894a90878d3e92bab"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:63(td)
+msgid "(StrOpt) During a SQL upgrade member_role_id will be used to create a new role that will replace records in the user_tenant_membership table with explicit role grants. After migration, the member_role_id will be used in the API add_user_to_project."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:66(td)
+msgid "member_role_name = _member_"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:67(td)
+msgid "(StrOpt) During a SQL upgrade member_role_id will be used to create a new role that will replace records in the user_tenant_membership table with explicit role grants. After migration, member_role_name will be ignored."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:70(td)
+msgid "public_bind_host = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:71(td)
+msgid "(StrOpt) The IP Address of the network interface to for the public service to listen on."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:74(td)
+msgid "public_endpoint = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:75(td)
+msgid "(StrOpt) The base public endpoint URL for keystone that are advertised to clients (NOTE: this does NOT affect how keystone listens for connections). Defaults to the base host URL of the request. Eg a request to http://server:5000/v2.0/users will default to http://server:5000. You should only need to set this value if the base URL contains a path (eg /prefix/v2.0) or the endpoint should be found on a different server."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:78(td)
+msgid "public_port = 5000"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:79(td)
+msgid "(IntOpt) The port number which the public service listens on."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:82(td)
+msgid "tcp_keepalive = False"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:83(td)
+msgid "(BoolOpt) Set this to True if you want to enable TCP_KEEPALIVE on server sockets i.e. sockets used by the keystone wsgi server for client connections."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:86(td) ./doc/common/tables/trove-api.xml:74(td) ./doc/common/tables/cinder-common.xml:198(td) ./doc/common/tables/neutron-wsgi.xml:30(td) ./doc/common/tables/glance-wsgi.xml:34(td) ./doc/common/tables/nova-wsgi.xml:38(td)
+msgid "tcp_keepidle = 600"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:87(td)
+msgid "(IntOpt) Sets the value of TCP_KEEPIDLE in seconds for each server socket. Only applies if tcp_keepalive is True. Not supported on OS X."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:90(th)
+msgid "[endpoint_filter]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:93(td)
+msgid "driver = keystone.contrib.endpoint_filter.backends.sql.EndpointFilter"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:94(td)
+msgid "(StrOpt) Keystone Endpoint Filter backend driver"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:97(td)
+msgid "return_all_endpoints_if_no_filter = True"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:98(td)
+msgid "(BoolOpt) Toggle to return all active endpoints if no filter exists."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:101(th) ./doc/common/tables/heat-api.xml:131(th) ./doc/common/tables/glance-paste.xml:19(th)
+msgid "[paste_deploy]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:104(td)
+msgid "config_file = keystone-paste.ini"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml:105(td)
+msgid "(StrOpt) Name of the paste configuration file that defines the available pipelines."
+msgstr ""
+
+#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml:7(literal) ./doc/common/tables/swift-proxy-server-pipeline-main.xml:7(literal) ./doc/common/tables/swift-container-server-pipeline-main.xml:7(literal) ./doc/common/tables/swift-object-server-pipeline-main.xml:7(literal) ./doc/common/tables/swift-account-server-pipeline-main.xml:7(literal)
+msgid "[pipeline:main]"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml:7(literal) ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml:7(literal) ./doc/common/tables/swift-object-expirer-object-expirer.xml:7(literal) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:7(literal) ./doc/common/tables/swift-object-expirer-filter-cache.xml:7(literal) ./doc/common/tables/swift-object-expirer-app-proxy-server.xml:7(literal)
+msgid "object-expirer.conf-sample"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml:18(td)
+msgid "pipeline = catch_errors cache proxy-server"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-auditor.xml:7(literal)
+msgid "[container-auditor]"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-auditor.xml:18(td)
+msgid "log_name = container-auditor"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-auditor.xml:30(td) ./doc/common/tables/swift-account-server-account-auditor.xml:30(td)
+msgid "interval = 1800"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-auditor.xml:33(td)
+msgid "containers_per_second = 200"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-auditor.xml:33(td)
+msgid "Maximum containers audited per second. Should be tuned according to individual system specs. 0 is unlimited. mounted to prevent accidentally writing to the root device process simultaneously (it will actually accept(2) N + 1). Setting this to one (1) will only handle one request at a time, without accepting another request concurrently. By increasing the number of workers to a much higher value, one can reduce the impact of slow file system operations in one request from negatively impacting other requests."
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-auditor.xml:36(td) ./doc/common/tables/swift-container-server-filter-recon.xml:21(td) ./doc/common/tables/swift-account-server-filter-recon.xml:21(td) ./doc/common/tables/swift-account-server-account-replicator.xml:63(td) ./doc/common/tables/swift-container-server-container-updater.xml:49(td) ./doc/common/tables/swift-object-server-object-replicator.xml:72(td) ./doc/common/tables/swift-object-server-object-auditor.xml:42(td) ./doc/common/tables/swift-container-server-container-replicator.xml:57(td) ./doc/common/tables/swift-account-server-account-auditor.xml:42(td) ./doc/common/tables/swift-object-server-filter-recon.xml:21(td) ./doc/common/tables/swift-object-server-object-updater.xml:42(td)
+msgid "recon_cache_path = /var/cache/swift"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-auditor.xml:36(td) ./doc/common/tables/swift-container-server-filter-recon.xml:21(td) ./doc/common/tables/swift-account-server-filter-recon.xml:21(td) ./doc/common/tables/swift-account-server-account-replicator.xml:63(td) ./doc/common/tables/swift-container-server-container-updater.xml:49(td) ./doc/common/tables/swift-object-server-object-replicator.xml:72(td) ./doc/common/tables/swift-object-server-object-auditor.xml:42(td) ./doc/common/tables/swift-container-server-container-replicator.xml:57(td) ./doc/common/tables/swift-account-server-account-auditor.xml:42(td) ./doc/common/tables/swift-object-server-filter-recon.xml:21(td) ./doc/common/tables/swift-object-server-object-updater.xml:42(td)
+msgid "Directory where stats for a few items will be stored"
+msgstr ""
+
+#: ./doc/common/tables/glance-rpc.xml:22(td)
+msgid "allowed_rpc_exception_modules = openstack.common.exception, glance.common.exception, exceptions"
+msgstr ""
+
+#: ./doc/common/tables/glance-rpc.xml:23(td) ./doc/common/tables/trove-rpc.xml:23(td)
+msgid "(ListOpt) Modules of exceptions that are permitted to be recreatedupon receiving exception data from an rpc call."
+msgstr ""
+
+#: ./doc/common/tables/neutron-policy.xml:22(td)
+msgid "allow_overlapping_ips = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-policy.xml:23(td)
+msgid "(BoolOpt) Allow overlapping IP support in Neutron"
+msgstr ""
+
+#: ./doc/common/tables/neutron-policy.xml:27(td)
+msgid "(StrOpt) The policy file to use"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml:8(caption)
+msgid "Description of configuration options for spice"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml:19(th)
+msgid "[spice]"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml:22(td)
+msgid "agent_enabled = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml:23(td)
+msgid "(BoolOpt) Enable spice guest agent support"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml:26(td) ./doc/common/tables/keystone-os_inherit.xml:22(td) ./doc/common/tables/nova-rdp.xml:22(td) ./doc/common/tables/nova-apiv3.xml:22(td) ./doc/common/tables/neutron-fwaas.xml:22(td) ./doc/common/tables/keystone-cache.xml:38(td)
+msgid "enabled = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml:27(td)
+msgid "(BoolOpt) Enable spice related features"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml:30(td)
+msgid "html5proxy_base_url = http://127.0.0.1:6082/spice_auto.html"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml:31(td)
+msgid "(StrOpt) Location of spice HTML5 console proxy, in the form \"http://127.0.0.1:6082/spice_auto.html\""
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml:34(td)
+msgid "keymap = en-us"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml:35(td)
+msgid "(StrOpt) Keymap for spice"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml:38(td)
+msgid "server_listen = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml:39(td)
+msgid "(StrOpt) IP address on which instance spice server should listen"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml:42(td)
+msgid "server_proxyclient_address = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml:43(td)
+msgid "(StrOpt) The address to which proxy clients (like nova-spicehtml5proxy) should connect"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_heat.xml:8(caption)
+msgid "Description of configuration options for clients_heat"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_heat.xml:19(th)
+msgid "[clients_heat]"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_heat.xml:42(td) ./doc/common/tables/neutron-ml2_ncs.xml:30(td) ./doc/common/tables/neutron-ml2_odl.xml:34(td)
+msgid "url = None"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_heat.xml:43(td)
+msgid "(StrOpt) Optional heat url in format like http://0.0.0.0:8004/v1/%(tenant_id)s."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:8(caption)
+msgid "Description of configuration options for xen"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:22(td)
+msgid "console_driver = nova.console.xvp.XVPConsoleProxy"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:23(td)
+msgid "(StrOpt) Driver to use for the console proxy"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:26(td)
+msgid "console_vmrc_error_retries = 10"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:27(td)
+msgid "(IntOpt) Number of retries for retrieving VMRC information"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:30(td)
+msgid "console_vmrc_port = 443"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:31(td)
+msgid "(IntOpt) Port for VMware VMRC connections"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:34(td)
+msgid "console_xvp_conf = /etc/xvp.conf"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:35(td)
+msgid "(StrOpt) Generated XVP conf file"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:38(td)
+msgid "console_xvp_conf_template = $pybasedir/nova/console/xvp.conf.template"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:39(td)
+msgid "(StrOpt) XVP conf template"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:42(td)
+msgid "console_xvp_log = /var/log/xvp.log"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:43(td)
+msgid "(StrOpt) XVP log file"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:46(td)
+msgid "console_xvp_multiplex_port = 5900"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:47(td)
+msgid "(IntOpt) Port for XVP to multiplex VNC connections on"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:50(td)
+msgid "console_xvp_pid = /var/run/xvp.pid"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:51(td)
+msgid "(StrOpt) XVP master process pid file"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:54(td)
+msgid "stub_compute = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:55(td)
+msgid "(BoolOpt) Stub calls to compute worker for tests"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:58(th) ./doc/common/tables/nova-volumes.xml:84(th) ./doc/common/tables/nova-livemigration.xml:26(th) ./doc/common/tables/nova-hypervisor.xml:54(th) ./doc/common/tables/nova-libvirt.xml:30(th)
+msgid "[libvirt]"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:61(td)
+msgid "xen_hvmloader_path = /usr/lib/xen/boot/hvmloader"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:62(td)
+msgid "(StrOpt) Location where the Xen hvmloader is kept"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:65(th) ./doc/common/tables/nova-volumes.xml:131(th) ./doc/common/tables/nova-baremetal.xml:130(th)
+msgid "[xenserver]"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:68(td)
+msgid "agent_path = usr/sbin/xe-update-networking"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:69(td)
+msgid "(StrOpt) Specifies the path in which the XenAPI guest agent should be located. If the agent is present, network configuration is not injected into the image. Used if compute_driver=xenapi.XenAPIDriver and flat_injected=True"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:72(td)
+msgid "agent_resetnetwork_timeout = 60"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:73(td)
+msgid "(IntOpt) Number of seconds to wait for agent reply to resetnetwork request"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:76(td)
+msgid "agent_timeout = 30"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:77(td)
+msgid "(IntOpt) Number of seconds to wait for agent reply"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:80(td)
+msgid "agent_version_timeout = 300"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:81(td)
+msgid "(IntOpt) Number of seconds to wait for agent to be fully operational"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:84(td)
+msgid "cache_images = all"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:85(td)
+msgid "(StrOpt) Cache glance images locally. `all` will cache all images, `some` will only cache images that have the image_property `cache_in_nova=True`, and `none` turns off caching entirely"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:88(td)
+msgid "check_host = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:89(td)
+msgid "(BoolOpt) Ensure compute service is running on host XenAPI connects to."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:92(td)
+msgid "connection_concurrent = 5"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:93(td)
+msgid "(IntOpt) Maximum number of concurrent XenAPI connections. Used only if compute_driver=xenapi.XenAPIDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:96(td)
+msgid "connection_password = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:97(td)
+msgid "(StrOpt) Password for connection to XenServer/Xen Cloud Platform. Used only if compute_driver=xenapi.XenAPIDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:100(td)
+msgid "connection_url = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:101(td)
+msgid "(StrOpt) URL for connection to XenServer/Xen Cloud Platform. A special value of unix://local can be used to connect to the local unix socket. Required if compute_driver=xenapi.XenAPIDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:104(td)
+msgid "connection_username = root"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:105(td)
+msgid "(StrOpt) Username for connection to XenServer/Xen Cloud Platform. Used only if compute_driver=xenapi.XenAPIDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:108(td)
+msgid "default_os_type = linux"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:109(td)
+msgid "(StrOpt) Default OS type"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:112(td)
+msgid "disable_agent = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:113(td)
+msgid "(BoolOpt) Disables the use of the XenAPI agent in any image regardless of what image properties are present."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:116(td)
+msgid "image_compression_level = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:117(td)
+msgid "(IntOpt) Compression level for images, e.g., 9 for gzip -9. Range is 1-9, 9 being most compressed but most CPU intensive on dom0."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:120(td)
+msgid "image_upload_handler = nova.virt.xenapi.image.glance.GlanceStore"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:121(td)
+msgid "(StrOpt) Dom0 plugin driver used to handle image uploads."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:124(td)
+msgid "introduce_vdi_retry_wait = 20"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:125(td)
+msgid "(IntOpt) Number of seconds to wait for an SR to settle if the VDI does not exist when first introduced"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:128(td)
+msgid "ipxe_boot_menu_url = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:129(td)
+msgid "(StrOpt) URL to the iPXE boot menu"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:132(td)
+msgid "ipxe_mkisofs_cmd = mkisofs"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:133(td) ./doc/common/tables/nova-configdrive.xml:39(td)
+msgid "(StrOpt) Name and optionally path of the tool used for ISO image creation"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:136(td)
+msgid "ipxe_network_name = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:137(td)
+msgid "(StrOpt) Name of network to use for booting iPXE ISOs"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:140(td)
+msgid "iqn_prefix = iqn.2010-10.org.openstack"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:141(td)
+msgid "(StrOpt) IQN Prefix"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:144(td)
+msgid "login_timeout = 10"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:145(td)
+msgid "(IntOpt) Timeout in seconds for XenAPI login."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:148(td)
+msgid "max_kernel_ramdisk_size = 16777216"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:149(td)
+msgid "(IntOpt) Maximum size in bytes of kernel or ramdisk images"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:152(td)
+msgid "num_vbd_unplug_retries = 10"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:153(td)
+msgid "(IntOpt) Maximum number of retries to unplug VBD"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:156(td)
+msgid "ovs_integration_bridge = xapi1"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:157(td) ./doc/common/tables/nova-neutron.xml:67(td)
+msgid "(StrOpt) Name of Integration Bridge used by Open vSwitch"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:160(td)
+msgid "remap_vbd_dev = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:161(td)
+msgid "(BoolOpt) Used to enable the remapping of VBD dev (Works around an issue in Ubuntu Maverick)"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:164(td)
+msgid "remap_vbd_dev_prefix = sd"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:165(td)
+msgid "(StrOpt) Specify prefix to remap VBD dev to (ex. /dev/xvdb -&gt; /dev/sdb)"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:168(td)
+msgid "running_timeout = 60"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:169(td)
+msgid "(IntOpt) Number of seconds to wait for instance to go to running state"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:172(td)
+msgid "sparse_copy = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:173(td)
+msgid "(BoolOpt) Whether to use sparse_copy for copying data on a resize down (False will use standard dd). This speeds up resizes down considerably since large runs of zeros won't have to be rsynced"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:176(td)
+msgid "sr_base_path = /var/run/sr-mount"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:180(td)
+msgid "sr_matching_filter = default-sr:true"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:181(td)
+msgid "(StrOpt) Filter for finding the SR to be used to install guest instances on. To use the Local Storage in default XenServer/XCP installations set this flag to other-config:i18n-key=local-storage. To select an SR with a different matching criteria, you could set it to other-config:my_favorite_sr=true. On the other hand, to fall back on the Default SR, as displayed by XenCenter, set this flag to: default-sr:true"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:184(td)
+msgid "target_host = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:185(td)
+msgid "(StrOpt) The iSCSI Target Host"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:188(td)
+msgid "target_port = 3260"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:189(td)
+msgid "(StrOpt) The iSCSI Target Port, default is port 3260"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:192(td)
+msgid "torrent_base_url = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:193(td)
+msgid "(StrOpt) Base URL for torrent files."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:196(td)
+msgid "torrent_download_stall_cutoff = 600"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:197(td)
+msgid "(IntOpt) Number of seconds a download can remain at the same progress percentage w/o being considered a stall"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:200(td)
+msgid "torrent_images = none"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:201(td)
+msgid "(StrOpt) Whether or not to download images via Bit Torrent (all|some|none)."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:204(td)
+msgid "torrent_listen_port_end = 6891"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:205(td)
+msgid "(IntOpt) End of port range to listen on"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:208(td)
+msgid "torrent_listen_port_start = 6881"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:209(td)
+msgid "(IntOpt) Beginning of port range to listen on"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:212(td)
+msgid "torrent_max_last_accessed = 86400"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:213(td)
+msgid "(IntOpt) Cached torrent files not accessed within this number of seconds can be reaped"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:216(td)
+msgid "torrent_max_seeder_processes_per_host = 1"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:217(td)
+msgid "(IntOpt) Maximum number of seeder processes to run concurrently within a given dom0. (-1 = no limit)"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:220(td)
+msgid "torrent_seed_chance = 1.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:221(td)
+msgid "(FloatOpt) Probability that peer will become a seeder. (1.0 = 100%)"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:224(td)
+msgid "torrent_seed_duration = 3600"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:225(td)
+msgid "(IntOpt) Number of seconds after downloading an image via BitTorrent that it should be seeded for other peers."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:228(td)
+msgid "use_agent_default = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:229(td)
+msgid "(BoolOpt) Determines if the XenAPI agent should be used when the image used does not contain a hint to declare if the agent is present or not. The hint is a glance property \"xenapi_use_agent\" that has the value \"True\" or \"False\". Note that waiting for the agent when it is not present will significantly increase server boot times."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:232(td)
+msgid "use_join_force = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:233(td)
+msgid "(BoolOpt) To use for hosts with different CPUs"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:236(td)
+msgid "vhd_coalesce_max_attempts = 20"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:237(td)
+msgid "(IntOpt) Max number of times to poll for VHD to coalesce. Used only if compute_driver=xenapi.XenAPIDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:240(td)
+msgid "vhd_coalesce_poll_interval = 5.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml:241(td)
+msgid "(FloatOpt) The interval used for polling of coalescing vhds. Used only if compute_driver=xenapi.XenAPIDriver"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml:8(caption) ./doc/common/tables/heat-amqp.xml:8(caption) ./doc/common/tables/keystone-amqp.xml:8(caption) ./doc/common/tables/glance-amqp.xml:8(caption) ./doc/common/tables/ceilometer-amqp.xml:8(caption)
+msgid "Description of configuration options for amqp"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml:30(td)
+msgid "conductor_queue = trove-conductor"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml:31(td) ./doc/common/tables/trove-common.xml:71(td) ./doc/common/tables/trove-api.xml:39(td) ./doc/common/tables/trove-api.xml:83(td) ./doc/common/tables/trove-api.xml:91(td) ./doc/common/tables/trove-api.xml:95(td) ./doc/common/tables/trove-dns.xml:23(td) ./doc/common/tables/trove-dns.xml:27(td) ./doc/common/tables/trove-dns.xml:31(td) ./doc/common/tables/trove-dns.xml:35(td) ./doc/common/tables/trove-dns.xml:39(td) ./doc/common/tables/trove-dns.xml:43(td) ./doc/common/tables/trove-dns.xml:47(td) ./doc/common/tables/trove-dns.xml:51(td) ./doc/common/tables/trove-dns.xml:55(td) ./doc/common/tables/trove-dns.xml:59(td) ./doc/common/tables/trove-dns.xml:63(td) ./doc/common/tables/trove-dns.xml:67(td) ./doc/common/tables/trove-dns.xml:79(td) ./doc/common/tables/trove-volume.xml:23(td) ./doc/common/tables/trove-volume.xml:27(td) ./doc/common/tables/trove-volume.xml:31(td) ./doc/common/tables/trove-volume.xml:43(td) ./doc/common/tables/trove-heat.xml:27(td) ./doc/common/tables/trove-rpc.xml:27(td) ./doc/common/tables/trove-backup.xml:39(td) ./doc/common/tables/trove-backup.xml:55(td) ./doc/common/tables/trove-guestagent.xml:39(td) ./doc/common/tables/trove-guestagent.xml:51(td) ./doc/common/tables/trove-compute.xml:23(td) ./doc/common/tables/trove-compute.xml:27(td) ./doc/common/tables/trove-logging.xml:23(td) ./doc/common/tables/trove-logging.xml:71(td) ./doc/common/tables/trove-debug.xml:55(td) ./doc/common/tables/trove-debug.xml:59(td) ./doc/common/tables/trove-debug.xml:63(td) ./doc/common/tables/trove-debug.xml:67(td) ./doc/common/tables/trove-debug.xml:71(td) ./doc/common/tables/trove-debug.xml:75(td) ./doc/common/tables/trove-swift.xml:23(td)
+msgid "(StrOpt) No help text available for this option."
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml:34(td) ./doc/common/tables/glance-rabbitmq.xml:22(td) ./doc/common/tables/keystone-amqp.xml:30(td) ./doc/common/tables/ceilometer-exchange.xml:26(td) ./doc/common/tables/cinder-rpc.xml:34(td) ./doc/common/tables/nova-rpc_all.xml:30(td) ./doc/common/tables/nova-rpc.xml:30(td)
+msgid "control_exchange = openstack"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml:39(td) ./doc/common/tables/heat-amqp.xml:43(td) ./doc/common/tables/neutron-testing.xml:27(td) ./doc/common/tables/ceilometer-rabbitmq.xml:23(td)
+msgid "(BoolOpt) If passed, use a fake RabbitMQ provider"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml:42(td) ./doc/common/tables/keystone-rabbit.xml:30(td) ./doc/common/tables/glance-rabbitmq.xml:34(td) ./doc/common/tables/heat-rabbitmq.xml:22(td) ./doc/common/tables/neutron-kombu.xml:22(td) ./doc/common/tables/nova-kombu.xml:26(td) ./doc/common/tables/cinder-rpc.xml:50(td) ./doc/common/tables/nova-rpc_all.xml:38(td) ./doc/common/tables/ceilometer-rabbitmq.xml:26(td)
+msgid "kombu_ssl_ca_certs ="
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml:43(td) ./doc/common/tables/heat-rabbitmq.xml:23(td) ./doc/common/tables/neutron-kombu.xml:23(td) ./doc/common/tables/ceilometer-rabbitmq.xml:27(td)
+msgid "(StrOpt) SSL certification authority file (valid only if SSL enabled)"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml:46(td) ./doc/common/tables/keystone-rabbit.xml:34(td) ./doc/common/tables/glance-rabbitmq.xml:38(td) ./doc/common/tables/heat-rabbitmq.xml:26(td) ./doc/common/tables/neutron-kombu.xml:26(td) ./doc/common/tables/nova-kombu.xml:30(td) ./doc/common/tables/cinder-rpc.xml:54(td) ./doc/common/tables/nova-rpc_all.xml:42(td) ./doc/common/tables/ceilometer-rabbitmq.xml:30(td)
+msgid "kombu_ssl_certfile ="
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml:47(td) ./doc/common/tables/heat-rabbitmq.xml:27(td) ./doc/common/tables/neutron-kombu.xml:27(td) ./doc/common/tables/ceilometer-rabbitmq.xml:31(td)
+msgid "(StrOpt) SSL cert file (valid only if SSL enabled)"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml:50(td) ./doc/common/tables/keystone-rabbit.xml:38(td) ./doc/common/tables/glance-rabbitmq.xml:42(td) ./doc/common/tables/heat-rabbitmq.xml:30(td) ./doc/common/tables/neutron-kombu.xml:30(td) ./doc/common/tables/nova-kombu.xml:34(td) ./doc/common/tables/cinder-rpc.xml:58(td) ./doc/common/tables/nova-rpc_all.xml:46(td) ./doc/common/tables/ceilometer-rabbitmq.xml:34(td)
+msgid "kombu_ssl_keyfile ="
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml:51(td) ./doc/common/tables/heat-rabbitmq.xml:31(td) ./doc/common/tables/neutron-kombu.xml:31(td) ./doc/common/tables/ceilometer-rabbitmq.xml:35(td)
+msgid "(StrOpt) SSL key file (valid only if SSL enabled)"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml:54(td) ./doc/common/tables/keystone-rabbit.xml:42(td) ./doc/common/tables/glance-rabbitmq.xml:46(td) ./doc/common/tables/heat-rabbitmq.xml:34(td) ./doc/common/tables/neutron-kombu.xml:34(td) ./doc/common/tables/nova-kombu.xml:38(td) ./doc/common/tables/cinder-rpc.xml:62(td) ./doc/common/tables/nova-rpc_all.xml:50(td) ./doc/common/tables/ceilometer-rabbitmq.xml:38(td)
+msgid "kombu_ssl_version ="
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml:55(td) ./doc/common/tables/heat-rabbitmq.xml:35(td)
+msgid "(StrOpt) SSL version to use (valid only if SSL enabled). valid values are TLSv1, SSLv23 and SSLv3. SSLv2 may be available on some distributions"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml:58(td) ./doc/common/tables/nova-common.xml:58(td) ./doc/common/tables/heat-amqp.xml:50(td) ./doc/common/tables/keystone-amqp.xml:38(td) ./doc/common/tables/glance-amqp.xml:30(td) ./doc/common/tables/cinder-rpc.xml:74(td) ./doc/common/tables/neutron-notifier.xml:30(td) ./doc/common/tables/ceilometer-amqp.xml:30(td)
+msgid "notification_driver = []"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml:59(td) ./doc/common/tables/heat-amqp.xml:51(td) ./doc/common/tables/neutron-notifier.xml:31(td) ./doc/common/tables/ceilometer-amqp.xml:31(td)
+msgid "(MultiStrOpt) Driver or drivers to handle sending notifications"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml:62(td)
+msgid "notification_service_id = {'couchbase': 'fa62fe68-74d9-4779-a24e-36f19602c415', 'mongodb': 'c8c907af-7375-456f-b929-b637ff9209ee', 'cassandra': '459a230d-4e97-4344-9067-2a54a310b0ed', 'redis': 'b216ffc5-1947-456c-a4cf-70f94c05f7d0', 'mysql': '2f3ff068-2bfb-4f70-9a9d-a6bb65bc084b'}"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml:63(td)
+msgid "(DictOpt) Unique ID to tag notification events."
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml:66(td) ./doc/common/tables/nova-common.xml:62(td) ./doc/common/tables/heat-amqp.xml:54(td) ./doc/common/tables/keystone-amqp.xml:42(td) ./doc/common/tables/glance-amqp.xml:34(td) ./doc/common/tables/cinder-rpc.xml:78(td) ./doc/common/tables/neutron-notifier.xml:34(td) ./doc/common/tables/ceilometer-amqp.xml:34(td)
+msgid "notification_topics = notifications"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml:67(td) ./doc/common/tables/neutron-notifier.xml:35(td)
+msgid "(ListOpt) AMQP topic used for openstack notifications"
+msgstr ""
+
+#: ./doc/common/tables/glance-matchmaker.xml:8(caption)
+msgid "Description of configuration options for matchmaker"
+msgstr ""
+
+#: ./doc/common/tables/glance-matchmaker.xml:23(td) ./doc/common/tables/cinder-rpc.xml:67(td) ./doc/common/tables/nova-rpc_all.xml:55(td) ./doc/common/tables/nova-rpc.xml:35(td) ./doc/common/tables/keystone-redis.xml:27(td)
+msgid "(IntOpt) Heartbeat frequency."
+msgstr ""
+
+#: ./doc/common/tables/glance-matchmaker.xml:34(td) ./doc/common/tables/cinder-rpc.xml:242(td) ./doc/common/tables/nova-rpc_all.xml:209(td) ./doc/common/tables/nova-rpc.xml:73(td) ./doc/common/tables/keystone-redis.xml:46(td)
+msgid "(StrOpt) Matchmaker ring file (JSON)."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml:8(caption) ./doc/common/tables/glance-rabbitmq.xml:8(caption) ./doc/common/tables/heat-rabbitmq.xml:8(caption) ./doc/common/tables/trove-rabbitmq.xml:8(caption) ./doc/common/tables/neutron-rabbitmq.xml:8(caption) ./doc/common/tables/ceilometer-rabbitmq.xml:8(caption)
+msgid "Description of configuration options for rabbitmq"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml:22(td) ./doc/common/tables/keystone-rabbit.xml:46(td) ./doc/common/tables/glance-rabbitmq.xml:50(td) ./doc/common/tables/heat-rabbitmq.xml:38(td) ./doc/common/tables/trove-rabbitmq.xml:22(td) ./doc/common/tables/cinder-rpc.xml:134(td) ./doc/common/tables/nova-rpc_all.xml:102(td) ./doc/common/tables/neutron-rabbitmq.xml:22(td) ./doc/common/tables/ceilometer-rabbitmq.xml:42(td)
+msgid "rabbit_ha_queues = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml:23(td) ./doc/common/tables/keystone-rabbit.xml:47(td) ./doc/common/tables/glance-rabbitmq.xml:51(td) ./doc/common/tables/cinder-rpc.xml:135(td) ./doc/common/tables/nova-rpc_all.xml:103(td) ./doc/common/tables/neutron-rabbitmq.xml:23(td) ./doc/common/tables/ceilometer-rabbitmq.xml:43(td)
+msgid "(BoolOpt) Use HA queues in RabbitMQ (x-ha-policy: all). If you change this option, you must wipe the RabbitMQ database."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml:26(td) ./doc/common/tables/keystone-rabbit.xml:50(td) ./doc/common/tables/glance-rabbitmq.xml:54(td) ./doc/common/tables/heat-rabbitmq.xml:42(td) ./doc/common/tables/trove-rabbitmq.xml:26(td) ./doc/common/tables/cinder-rpc.xml:138(td) ./doc/common/tables/nova-rpc_all.xml:106(td) ./doc/common/tables/neutron-rabbitmq.xml:26(td) ./doc/common/tables/ceilometer-rabbitmq.xml:46(td)
+msgid "rabbit_host = localhost"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml:27(td) ./doc/common/tables/keystone-rabbit.xml:51(td) ./doc/common/tables/glance-rabbitmq.xml:55(td) ./doc/common/tables/cinder-rpc.xml:139(td) ./doc/common/tables/nova-rpc_all.xml:107(td)
+msgid "(StrOpt) The RabbitMQ broker address where a single node is used."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml:30(td) ./doc/common/tables/keystone-rabbit.xml:54(td) ./doc/common/tables/glance-rabbitmq.xml:58(td) ./doc/common/tables/heat-rabbitmq.xml:46(td) ./doc/common/tables/trove-rabbitmq.xml:30(td) ./doc/common/tables/cinder-rpc.xml:142(td) ./doc/common/tables/nova-rpc_all.xml:110(td) ./doc/common/tables/neutron-rabbitmq.xml:30(td) ./doc/common/tables/ceilometer-rabbitmq.xml:50(td)
+msgid "rabbit_hosts = $rabbit_host:$rabbit_port"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml:31(td) ./doc/common/tables/keystone-rabbit.xml:55(td) ./doc/common/tables/glance-rabbitmq.xml:59(td) ./doc/common/tables/cinder-rpc.xml:143(td) ./doc/common/tables/nova-rpc_all.xml:111(td)
+msgid "(ListOpt) RabbitMQ HA cluster host:port pairs."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml:34(td) ./doc/common/tables/keystone-rabbit.xml:58(td) ./doc/common/tables/glance-rabbitmq.xml:62(td) ./doc/common/tables/cinder-rpc.xml:146(td) ./doc/common/tables/nova-rpc_all.xml:114(td)
+msgid "rabbit_login_method = AMQPLAIN"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml:35(td) ./doc/common/tables/keystone-rabbit.xml:59(td) ./doc/common/tables/glance-rabbitmq.xml:63(td) ./doc/common/tables/cinder-rpc.xml:147(td) ./doc/common/tables/nova-rpc_all.xml:115(td)
+msgid "(StrOpt) the RabbitMQ login method"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml:38(td) ./doc/common/tables/keystone-rabbit.xml:62(td) ./doc/common/tables/glance-rabbitmq.xml:66(td) ./doc/common/tables/heat-rabbitmq.xml:50(td) ./doc/common/tables/trove-rabbitmq.xml:34(td) ./doc/common/tables/cinder-rpc.xml:150(td) ./doc/common/tables/nova-rpc_all.xml:118(td) ./doc/common/tables/neutron-rabbitmq.xml:34(td) ./doc/common/tables/ceilometer-rabbitmq.xml:54(td)
+msgid "rabbit_max_retries = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml:39(td) ./doc/common/tables/keystone-rabbit.xml:63(td) ./doc/common/tables/glance-rabbitmq.xml:67(td) ./doc/common/tables/cinder-rpc.xml:151(td) ./doc/common/tables/nova-rpc_all.xml:119(td)
+msgid "(IntOpt) Maximum number of RabbitMQ connection retries. Default is 0 (infinite retry count)."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml:42(td) ./doc/common/tables/keystone-rabbit.xml:66(td) ./doc/common/tables/glance-rabbitmq.xml:70(td) ./doc/common/tables/heat-rabbitmq.xml:54(td) ./doc/common/tables/trove-rabbitmq.xml:38(td) ./doc/common/tables/cinder-rpc.xml:154(td) ./doc/common/tables/nova-rpc_all.xml:122(td) ./doc/common/tables/neutron-rabbitmq.xml:38(td) ./doc/common/tables/ceilometer-rabbitmq.xml:58(td)
+msgid "rabbit_password = guest"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml:43(td) ./doc/common/tables/keystone-rabbit.xml:67(td) ./doc/common/tables/glance-rabbitmq.xml:71(td) ./doc/common/tables/cinder-rpc.xml:155(td) ./doc/common/tables/nova-rpc_all.xml:123(td)
+msgid "(StrOpt) The RabbitMQ password."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml:46(td) ./doc/common/tables/keystone-rabbit.xml:70(td) ./doc/common/tables/glance-rabbitmq.xml:74(td) ./doc/common/tables/heat-rabbitmq.xml:58(td) ./doc/common/tables/trove-rabbitmq.xml:42(td) ./doc/common/tables/cinder-rpc.xml:158(td) ./doc/common/tables/nova-rpc_all.xml:126(td) ./doc/common/tables/neutron-rabbitmq.xml:42(td) ./doc/common/tables/ceilometer-rabbitmq.xml:62(td)
+msgid "rabbit_port = 5672"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml:47(td) ./doc/common/tables/keystone-rabbit.xml:71(td) ./doc/common/tables/glance-rabbitmq.xml:75(td) ./doc/common/tables/cinder-rpc.xml:159(td) ./doc/common/tables/nova-rpc_all.xml:127(td)
+msgid "(IntOpt) The RabbitMQ broker port where a single node is used."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml:50(td) ./doc/common/tables/keystone-rabbit.xml:74(td) ./doc/common/tables/glance-rabbitmq.xml:78(td) ./doc/common/tables/heat-rabbitmq.xml:62(td) ./doc/common/tables/trove-rabbitmq.xml:46(td) ./doc/common/tables/cinder-rpc.xml:162(td) ./doc/common/tables/nova-rpc_all.xml:130(td) ./doc/common/tables/neutron-rabbitmq.xml:46(td) ./doc/common/tables/ceilometer-rabbitmq.xml:66(td)
+msgid "rabbit_retry_backoff = 2"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml:51(td) ./doc/common/tables/keystone-rabbit.xml:75(td) ./doc/common/tables/glance-rabbitmq.xml:79(td) ./doc/common/tables/cinder-rpc.xml:163(td) ./doc/common/tables/nova-rpc_all.xml:131(td)
+msgid "(IntOpt) How long to backoff for between retries when connecting to RabbitMQ."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml:54(td) ./doc/common/tables/keystone-rabbit.xml:78(td) ./doc/common/tables/glance-rabbitmq.xml:82(td) ./doc/common/tables/heat-rabbitmq.xml:66(td) ./doc/common/tables/trove-rabbitmq.xml:50(td) ./doc/common/tables/cinder-rpc.xml:166(td) ./doc/common/tables/nova-rpc_all.xml:134(td) ./doc/common/tables/neutron-rabbitmq.xml:50(td) ./doc/common/tables/ceilometer-rabbitmq.xml:70(td)
+msgid "rabbit_retry_interval = 1"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml:55(td) ./doc/common/tables/keystone-rabbit.xml:79(td) ./doc/common/tables/glance-rabbitmq.xml:83(td) ./doc/common/tables/cinder-rpc.xml:167(td) ./doc/common/tables/nova-rpc_all.xml:135(td)
+msgid "(IntOpt) How frequently to retry connecting with RabbitMQ."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml:58(td) ./doc/common/tables/keystone-rabbit.xml:82(td) ./doc/common/tables/glance-rabbitmq.xml:86(td) ./doc/common/tables/heat-rabbitmq.xml:70(td) ./doc/common/tables/trove-rabbitmq.xml:54(td) ./doc/common/tables/cinder-rpc.xml:170(td) ./doc/common/tables/nova-rpc_all.xml:138(td) ./doc/common/tables/neutron-rabbitmq.xml:54(td) ./doc/common/tables/ceilometer-rabbitmq.xml:74(td)
+msgid "rabbit_use_ssl = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml:59(td) ./doc/common/tables/keystone-rabbit.xml:83(td) ./doc/common/tables/glance-rabbitmq.xml:87(td) ./doc/common/tables/cinder-rpc.xml:171(td) ./doc/common/tables/nova-rpc_all.xml:139(td)
+msgid "(BoolOpt) Connect over SSL for RabbitMQ."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml:62(td) ./doc/common/tables/keystone-rabbit.xml:86(td) ./doc/common/tables/glance-rabbitmq.xml:90(td) ./doc/common/tables/heat-rabbitmq.xml:74(td) ./doc/common/tables/trove-rabbitmq.xml:58(td) ./doc/common/tables/cinder-rpc.xml:174(td) ./doc/common/tables/nova-rpc_all.xml:142(td) ./doc/common/tables/neutron-rabbitmq.xml:58(td) ./doc/common/tables/ceilometer-rabbitmq.xml:78(td)
+msgid "rabbit_userid = guest"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml:63(td) ./doc/common/tables/keystone-rabbit.xml:87(td) ./doc/common/tables/glance-rabbitmq.xml:91(td) ./doc/common/tables/cinder-rpc.xml:175(td) ./doc/common/tables/nova-rpc_all.xml:143(td)
+msgid "(StrOpt) The RabbitMQ userid."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml:66(td) ./doc/common/tables/keystone-rabbit.xml:90(td) ./doc/common/tables/glance-rabbitmq.xml:94(td) ./doc/common/tables/heat-rabbitmq.xml:78(td) ./doc/common/tables/trove-rabbitmq.xml:62(td) ./doc/common/tables/cinder-rpc.xml:178(td) ./doc/common/tables/nova-rpc_all.xml:146(td) ./doc/common/tables/neutron-rabbitmq.xml:62(td) ./doc/common/tables/ceilometer-rabbitmq.xml:82(td)
+msgid "rabbit_virtual_host = /"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml:67(td) ./doc/common/tables/keystone-rabbit.xml:91(td) ./doc/common/tables/glance-rabbitmq.xml:95(td) ./doc/common/tables/cinder-rpc.xml:179(td) ./doc/common/tables/nova-rpc_all.xml:147(td)
+msgid "(StrOpt) The RabbitMQ virtual host."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_cisco.xml:8(caption)
+msgid "Description of configuration options for ml2_cisco"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_cisco.xml:22(td)
+msgid "managed_physical_network = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_cisco.xml:23(td)
+msgid "(StrOpt) The physical network managed by the switches."
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml:22(td)
+msgid "allow_instance_snapshots = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml:23(td)
+msgid "(BoolOpt) Permit instance snapshot operations."
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml:26(td)
+msgid "allow_migrate_to_same_host = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml:27(td)
+msgid "(BoolOpt) Allow migrate machine to the same host. Useful when testing in single-host environments."
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml:30(td)
+msgid "allow_resize_to_same_host = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml:31(td)
+msgid "(BoolOpt) Allow destination machine to match source for resize. Useful when testing in single-host environments."
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml:34(td) ./doc/common/tables/cinder-quota.xml:22(td)
+msgid "max_age = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml:35(td)
+msgid "(IntOpt) Number of seconds between subsequent usage refreshes"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml:38(td)
+msgid "max_local_block_devices = 3"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml:39(td)
+msgid "(IntOpt) Maximum number of devices that will result in a local image being created on the hypervisor node. Setting this to 0 means nova will allow only boot from volume. A negative number means unlimited."
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml:42(td)
+msgid "osapi_compute_unique_server_name_scope ="
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml:43(td)
+msgid "(StrOpt) When set, compute API will consider duplicate hostnames invalid within the specified scope, regardless of case. Should be empty, \"project\" or \"global\"."
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml:46(td) ./doc/common/tables/cinder-api.xml:50(td)
+msgid "osapi_max_limit = 1000"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml:47(td)
+msgid "(IntOpt) The maximum number of items returned in a single response from a collection resource"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml:50(td) ./doc/common/tables/cinder-api.xml:54(td)
+msgid "osapi_max_request_body_size = 114688"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml:51(td)
+msgid "(IntOpt) The maximum body size per each osapi request(bytes)"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml:54(td)
+msgid "password_length = 12"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml:55(td)
+msgid "(IntOpt) Length of generated instance admin passwords"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml:59(td) ./doc/common/tables/cinder-common.xml:139(td)
+msgid "(StrOpt) Rule checked when requested rule is not found"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml:63(td) ./doc/common/tables/cinder-common.xml:143(td)
+msgid "(StrOpt) JSON file representing policy"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml:66(td) ./doc/common/tables/cinder-quota.xml:42(td)
+msgid "reservation_expire = 86400"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml:67(td)
+msgid "(IntOpt) Number of seconds until a reservation expires"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml:70(td)
+msgid "resize_fs_using_block_device = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml:71(td)
+msgid "(BoolOpt) Attempt to resize the filesystem by accessing the image over a block device. This is done by the host and may not be necessary if the image contains a recent version of cloud-init. Possible mechanisms require the nbd driver (for qcow and raw), or loop (for raw)."
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml:74(td) ./doc/common/tables/cinder-common.xml:202(td)
+msgid "until_refresh = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml:75(td)
+msgid "(IntOpt) Count of reservations until usage is refreshed"
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml:8(caption)
+msgid "Description of configuration options for identity"
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml:19(th)
+msgid "[identity]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml:22(td)
+msgid "default_domain_id = default"
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml:23(td)
+msgid "(StrOpt) This references the domain to use for all Identity API v2 requests (which are not aware of domains). A domain with this ID will be created for you by keystone-manage db_sync in migration 008. The domain referenced by this ID cannot be deleted on the v3 API, to prevent accidentally breaking the v2 API. There is nothing special about this domain, other than the fact that it must exist to order to maintain support for your v2 clients."
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml:26(td)
+msgid "domain_config_dir = /etc/keystone/domains"
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml:27(td)
+msgid "(StrOpt) Path for Keystone to locate the domain specificidentity configuration files if domain_specific_drivers_enabled is set to true."
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml:30(td)
+msgid "domain_specific_drivers_enabled = False"
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml:31(td)
+msgid "(BoolOpt) A subset (or all) of domains can have their own identity driver, each with their own partial configuration file in a domain configuration directory. Only values specific to the domain need to be placed in the domain specific configuration file. This feature is disabled by default; set to True to enable."
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml:34(td)
+msgid "driver = keystone.identity.backends.sql.Identity"
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml:35(td)
+msgid "(StrOpt) Keystone Identity backend driver."
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml:39(td)
+msgid "(IntOpt) Maximum number of entities that will be returned in an identity collection."
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml:42(td)
+msgid "max_password_length = 4096"
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml:43(td)
+msgid "(IntOpt) Maximum supported length for user passwords; decrease to improve performance."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-inspector.xml:8(caption)
+msgid "Description of configuration options for inspector"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-inspector.xml:22(td)
+msgid "hypervisor_inspector = libvirt"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-inspector.xml:23(td)
+msgid "(StrOpt) Inspector to use for inspecting the hypervisor layer."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-inspector.xml:26(td)
+msgid "libvirt_type = kvm"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-inspector.xml:27(td)
+msgid "(StrOpt) Libvirt domain type (valid options are: kvm, lxc, qemu, uml, xen)."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-inspector.xml:30(td)
+msgid "libvirt_uri ="
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-inspector.xml:31(td)
+msgid "(StrOpt) Override the default libvirt URI (which is dependent on libvirt_type)."
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml:22(td)
+msgid "scheduler_default_filters = AvailabilityZoneFilter, CapacityFilter, CapabilitiesFilter"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml:23(td) ./doc/common/tables/nova-scheduling.xml:79(td)
+msgid "(ListOpt) Which filter class names to use for filtering hosts when not specified in the request."
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml:26(td)
+msgid "scheduler_default_weighers = CapacityWeigher"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml:27(td)
+msgid "(ListOpt) Which weigher class names to use for weighing hosts."
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml:30(td)
+msgid "scheduler_driver = cinder.scheduler.filter_scheduler.FilterScheduler"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml:31(td)
+msgid "(StrOpt) Default scheduler driver to use"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml:34(td)
+msgid "scheduler_host_manager = cinder.scheduler.host_manager.HostManager"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml:35(td) ./doc/common/tables/nova-scheduling.xml:91(td)
+msgid "(StrOpt) The scheduler host manager class to use"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml:38(td) ./doc/common/tables/nova-scheduling.xml:98(td)
+msgid "scheduler_json_config_location ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml:39(td) ./doc/common/tables/nova-scheduling.xml:99(td)
+msgid "(StrOpt) Absolute path to scheduler configuration JSON file."
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml:42(td)
+msgid "scheduler_manager = cinder.scheduler.manager.SchedulerManager"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml:43(td)
+msgid "(StrOpt) full class name for the Manager for scheduler"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml:46(td) ./doc/common/tables/nova-scheduling.xml:106(td)
+msgid "scheduler_max_attempts = 3"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml:47(td)
+msgid "(IntOpt) Maximum number of attempts to schedule an volume"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml:50(td)
+msgid "scheduler_topic = cinder-scheduler"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml:51(td)
+msgid "(StrOpt) the topic scheduler nodes listen on"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_cassandra.xml:8(caption)
+msgid "Description of configuration options for db_cassandra"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_cassandra.xml:19(th)
+msgid "[cassandra]"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_cassandra.xml:22(td) ./doc/common/tables/trove-db_couchbase.xml:22(td) ./doc/common/tables/trove-db_mongodb.xml:22(td) ./doc/common/tables/trove-db_redis.xml:22(td)
+msgid "backup_strategy = None"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_cassandra.xml:26(td)
+msgid "mount_point = /var/lib/cassandra"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_cassandra.xml:30(td)
+msgid "tcp_ports = 7000, 7001, 9042, 9160"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_cassandra.xml:38(td)
+msgid "usage_timeout = 600"
+msgstr ""
+
+#: ./doc/common/tables/neutron-logging.xml:26(td) ./doc/common/tables/trove-common.xml:34(td) ./doc/common/tables/heat-logging.xml:22(td)
+msgid "default_log_levels = amqp=WARN, amqplib=WARN, boto=WARN, qpid=WARN, sqlalchemy=WARN, suds=INFO, iso8601=WARN"
+msgstr ""
+
+#: ./doc/common/tables/neutron-logging.xml:27(td) ./doc/common/tables/trove-common.xml:35(td) ./doc/common/tables/heat-logging.xml:23(td) ./doc/common/tables/nova-logging.xml:27(td)
+msgid "(ListOpt) list of logger=LEVEL pairs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-logging.xml:31(td) ./doc/common/tables/heat-debug.xml:35(td) ./doc/common/tables/nova-logging.xml:31(td) ./doc/common/tables/trove-debug.xml:39(td)
+msgid "(BoolOpt) make deprecations fatal"
+msgstr ""
+
+#: ./doc/common/tables/neutron-logging.xml:63(td) ./doc/common/tables/heat-logging.xml:55(td) ./doc/common/tables/nova-logging.xml:67(td) ./doc/common/tables/trove-logging.xml:55(td)
+msgid "(StrOpt) format string to use for log messages with context"
+msgstr ""
+
+#: ./doc/common/tables/neutron-logging.xml:67(td) ./doc/common/tables/heat-logging.xml:59(td) ./doc/common/tables/nova-logging.xml:71(td) ./doc/common/tables/trove-logging.xml:59(td)
+msgid "(StrOpt) data to append to log format when level is DEBUG"
+msgstr ""
+
+#: ./doc/common/tables/neutron-logging.xml:71(td) ./doc/common/tables/heat-logging.xml:63(td) ./doc/common/tables/nova-logging.xml:75(td) ./doc/common/tables/trove-logging.xml:63(td)
+msgid "(StrOpt) format string to use for log messages without context"
+msgstr ""
+
+#: ./doc/common/tables/neutron-logging.xml:75(td) ./doc/common/tables/heat-logging.xml:67(td) ./doc/common/tables/nova-logging.xml:79(td) ./doc/common/tables/trove-logging.xml:67(td)
+msgid "(StrOpt) prefix each line of exception output with this format"
+msgstr ""
+
+#: ./doc/common/tables/neutron-logging.xml:79(td) ./doc/common/tables/heat-notification.xml:27(td) ./doc/common/tables/nova-logging.xml:83(td) ./doc/common/tables/trove-logging.xml:75(td)
+msgid "(BoolOpt) publish error events"
+msgstr ""
+
+#: ./doc/common/tables/neutron-logging.xml:83(td) ./doc/common/tables/heat-logging.xml:71(td) ./doc/common/tables/nova-logging.xml:87(td) ./doc/common/tables/trove-logging.xml:79(td)
+msgid "(StrOpt) syslog facility to receive log lines"
+msgstr ""
+
+#: ./doc/common/tables/neutron-logging.xml:86(td) ./doc/common/tables/neutron-nec.xml:58(td)
+msgid "use_ssl = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-logging.xml:87(td)
+msgid "(BoolOpt) Enable SSL on the API server"
+msgstr ""
+
+#: ./doc/common/tables/neutron-logging.xml:95(td) ./doc/common/tables/heat-logging.xml:79(td) ./doc/common/tables/trove-logging.xml:87(td)
+msgid "(BoolOpt) Use syslog for logging."
+msgstr ""
+
+#: ./doc/common/tables/nova-availabilityzones.xml:8(caption)
+msgid "Description of configuration options for availabilityzones"
+msgstr ""
+
+#: ./doc/common/tables/nova-availabilityzones.xml:22(td)
+msgid "default_availability_zone = nova"
+msgstr ""
+
+#: ./doc/common/tables/nova-availabilityzones.xml:23(td)
+msgid "(StrOpt) Default compute node availability_zone"
+msgstr ""
+
+#: ./doc/common/tables/nova-availabilityzones.xml:26(td)
+msgid "default_schedule_zone = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-availabilityzones.xml:27(td)
+msgid "(StrOpt) Availability zone to use when user doesn't specify one"
+msgstr ""
+
+#: ./doc/common/tables/nova-availabilityzones.xml:30(td)
+msgid "internal_service_availability_zone = internal"
+msgstr ""
+
+#: ./doc/common/tables/nova-availabilityzones.xml:31(td)
+msgid "(StrOpt) The availability_zone to show internal services under"
+msgstr ""
+
+#: ./doc/common/tables/keystone-catalog.xml:8(caption)
+msgid "Description of configuration options for catalog"
+msgstr ""
+
+#: ./doc/common/tables/keystone-catalog.xml:19(th)
+msgid "[catalog]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-catalog.xml:22(td)
+msgid "driver = keystone.catalog.backends.sql.Catalog"
+msgstr ""
+
+#: ./doc/common/tables/keystone-catalog.xml:23(td)
+msgid "(StrOpt) Keystone catalog backend driver."
+msgstr ""
+
+#: ./doc/common/tables/keystone-catalog.xml:27(td)
+msgid "(IntOpt) Maximum number of entities that will be returned in a catalog collection."
+msgstr ""
+
+#: ./doc/common/tables/keystone-catalog.xml:30(td)
+msgid "template_file = default_catalog.templates"
+msgstr ""
+
+#: ./doc/common/tables/keystone-catalog.xml:31(td)
+msgid "(StrOpt) Catalog template file name for use with the template catalog backend."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:8(caption)
+msgid "Description of configuration options for netapp_eseries_iscsi"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:22(td)
+msgid "netapp_controller_ips = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:23(td)
+msgid "(StrOpt) This option is only utilized when the storage family is configured to eseries. This option is used to restrict provisioning to the specified controllers. Specify the value of this option to be a comma separated list of controller hostnames or IP addresses to be used for provisioning."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:34(td)
+msgid "netapp_sa_password = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:35(td)
+msgid "(StrOpt) Password for the NetApp E-Series storage array."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:50(td)
+msgid "netapp_storage_pools = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:51(td)
+msgid "(StrOpt) This option is used to restrict provisioning to the specified storage pools. Only dynamic disk pools are currently supported. Specify the value of this option to be a comma separated list of disk pool names to be used for provisioning."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:58(td)
+msgid "netapp_webservice_path = /devmgr/v2"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:59(td)
+msgid "(StrOpt) This option is used to specify the path to the E-Series proxy application on a proxy server. The value is combined with the value of the netapp_transport_type, netapp_server_hostname, and netapp_server_port options to create the URL used by the driver to connect to the proxy application."
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml:8(caption) ./doc/common/tables/nova-rootwrap.xml:8(caption) ./doc/common/tables/cinder-rootwrap.xml:8(caption)
+msgid "Description of configuration options for rootwrap"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml:22(td)
+msgid "filters_path = /etc/neutron/rootwrap.d,/usr/share/neutron/rootwrap,/etc/quantum/rootwrap.d,/usr/share/quantum/rootwrap"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml:23(td) ./doc/common/tables/nova-rootwrap.xml:23(td) ./doc/common/tables/cinder-rootwrap.xml:23(td)
+msgid "List of directories to load filter definitions from (separated by ','). These directories MUST all be only writeable by root !"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml:26(td) ./doc/common/tables/nova-rootwrap.xml:26(td) ./doc/common/tables/cinder-rootwrap.xml:26(td)
+msgid "exec_dirs = /sbin,/usr/sbin,/bin,/usr/bin"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml:27(td) ./doc/common/tables/nova-rootwrap.xml:27(td) ./doc/common/tables/cinder-rootwrap.xml:27(td)
+msgid "List of directories to search executables in, in case filters do not explicitely specify a full path (separated by ',') If not specified, defaults to system PATH environment variable. These directories MUST all be only writeable by root !"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml:31(td) ./doc/common/tables/nova-rootwrap.xml:31(td) ./doc/common/tables/cinder-rootwrap.xml:31(td)
+msgid "Enable logging to syslog Default value is False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml:34(td) ./doc/common/tables/nova-rootwrap.xml:34(td) ./doc/common/tables/cinder-rootwrap.xml:34(td)
+msgid "syslog_log_facility = syslog"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml:35(td) ./doc/common/tables/cinder-rootwrap.xml:35(td)
+msgid "Which syslog facility to use. Valid values include auth, authpriv, syslog, local0, local1... Default value is 'syslog'"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml:38(td) ./doc/common/tables/nova-rootwrap.xml:38(td) ./doc/common/tables/cinder-rootwrap.xml:38(td)
+msgid "syslog_log_level = ERROR"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml:39(td) ./doc/common/tables/nova-rootwrap.xml:39(td) ./doc/common/tables/cinder-rootwrap.xml:39(td)
+msgid "Which messages to log. INFO means log all usage ERROR means only log unsuccessful attempts"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml:42(th)
+msgid "[xenapi]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml:45(td)
+msgid "xenapi_connection_url = &lt;None&gt;"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml:46(td)
+msgid "XenAPI configuration is only required by the L2 agent if it is to target a XenServer/XCP compute host's dom0."
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml:53(td)
+msgid "xenapi_connection_password = &lt;None&gt;"
+msgstr ""
+
+#: ./doc/common/tables/cinder-auth.xml:22(td) ./doc/common/tables/glance-registry.xml:38(td) ./doc/common/tables/nova-authentication.xml:22(td)
+msgid "auth_strategy = noauth"
+msgstr ""
+
+#: ./doc/common/tables/cinder-auth.xml:23(td)
+msgid "(StrOpt) The strategy to use for auth. Supports noauth, keystone, and deprecated."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml:7(literal)
+msgid "[swift-constraints]"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml:7(literal) ./doc/common/tables/swift-swift-swift-hash.xml:7(literal)
+msgid "swift.conf-sample"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml:18(td)
+msgid "max_file_size = 5368709122"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml:18(td)
+msgid "The largest normal object that can be saved in the cluster. This is also the limit on the size of each segment of a large object when using the large object manifest support. This value is set in bytes. Setting it to lower than 1MiB will cause some tests to fail. It is STRONGLY recommended to leave this value at the default (5 * 2**30 + 2)."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml:29(td)
+msgid "max_meta_name_length = 128"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml:29(td)
+msgid "The maximum number of bytes in the utf8 encoding of the name portion of a metadata header."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml:34(td)
+msgid "max_meta_value_length = 256"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml:34(td)
+msgid "The max number of bytes in the utf8 encoding of a metadata value."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml:38(td)
+msgid "max_meta_count = 90"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml:38(td)
+msgid "The maximum number of metadata keys that can be stored on a single account, container, or object."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml:43(td)
+msgid "max_meta_overall_size = 4096"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml:43(td)
+msgid "The maximum number of bytes in the utf8 encoding of the metadata (keys + values)."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml:48(td)
+msgid "max_header_size = 8192"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml:48(td)
+msgid "The maximum number of bytes in the utf8 encoding of each header."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml:52(td)
+msgid "max_object_name_length = 1024"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml:52(td)
+msgid "The maximum number of bytes in the utf8 encoding of an object name."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml:56(td)
+msgid "container_listing_limit = 10000"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml:56(td)
+msgid "The default (and maximum) number of items returned for a container listing request."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml:61(td)
+msgid "account_listing_limit = 10000"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml:61(td)
+msgid "The default (and maximum) number of items returned for an account listing request."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml:65(td)
+msgid "max_account_name_length = 256"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml:65(td)
+msgid "The maximum number of bytes in the utf8 encoding of an account name."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml:69(td)
+msgid "max_container_name_length = 256"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml:69(td)
+msgid "The maximum number of bytes in the utf8 encoding of a container name."
+msgstr ""
+
+#: ./doc/common/tables/heat-qpid.xml:54(td) ./doc/common/tables/nova-qpid.xml:54(td) ./doc/common/tables/glance-qpid.xml:54(td) ./doc/common/tables/cinder-rpc.xml:126(td) ./doc/common/tables/nova-rpc_all.xml:94(td) ./doc/common/tables/neutron-qpid.xml:54(td) ./doc/common/tables/keystone-qpid.xml:54(td) ./doc/common/tables/ceilometer-qpid.xml:54(td)
+msgid "qpid_topology_version = 1"
+msgstr ""
+
+#: ./doc/common/tables/heat-qpid.xml:55(td) ./doc/common/tables/nova-qpid.xml:55(td) ./doc/common/tables/glance-qpid.xml:55(td) ./doc/common/tables/cinder-rpc.xml:127(td) ./doc/common/tables/nova-rpc_all.xml:95(td) ./doc/common/tables/neutron-qpid.xml:55(td) ./doc/common/tables/keystone-qpid.xml:55(td) ./doc/common/tables/ceilometer-qpid.xml:55(td)
+msgid "(IntOpt) The qpid topology version to use. Version 1 is what was originally used by impl_qpid. Version 2 includes some backwards-incompatible changes that allow broker federation to work. Users should update to version 2 when they are able to take everything down, as it requires a clean break."
+msgstr ""
+
+#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:7(literal)
+msgid "[filter:catch_errors]"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:18(td)
+msgid "use = egg:swift#catch_errors"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml:7(literal)
+msgid "[filter:slo]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml:18(td)
+msgid "use = egg:swift#slo"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml:21(td)
+msgid "max_manifest_segments = 1000"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml:24(td)
+msgid "max_manifest_size = 2097152"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml:27(td)
+msgid "min_segment_size = 1048576"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-dlo.xml:21(td)
+msgid "rate_limit_after_segment = 10"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-dlo.xml:21(td)
+msgid "Rate limit the download of large object segments after this segment is downloaded."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml:33(td)
+msgid "rate_limit_segments_per_sec = 0"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-dlo.xml:24(td)
+msgid "Rate limit large object downloads at this rate. contact for a normal request. You can use '* replicas' at the end to have it use the number given times the number of replicas for the ring being used for the request. paste.deploy to use for auth. To use tempauth set to: `egg:swift#tempauth` each request"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml:36(td) ./doc/common/tables/swift-proxy-server-filter-dlo.xml:27(td)
+msgid "max_get_time = 86400"
+msgstr ""
+
+#: ./doc/common/tables/nova-zookeeper.xml:8(caption)
+msgid "Description of configuration options for zookeeper"
+msgstr ""
+
+#: ./doc/common/tables/nova-zookeeper.xml:19(th)
+msgid "[zookeeper]"
+msgstr ""
+
+#: ./doc/common/tables/nova-zookeeper.xml:22(td)
+msgid "address = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-zookeeper.xml:23(td)
+msgid "(StrOpt) The ZooKeeper addresses for servicegroup service in the format of host1:port,host2:port,host3:port"
+msgstr ""
+
+#: ./doc/common/tables/nova-zookeeper.xml:26(td)
+msgid "recv_timeout = 4000"
+msgstr ""
+
+#: ./doc/common/tables/nova-zookeeper.xml:27(td)
+msgid "(IntOpt) The recv_timeout parameter for the zk session"
+msgstr ""
+
+#: ./doc/common/tables/nova-zookeeper.xml:30(td)
+msgid "sg_prefix = /servicegroups"
+msgstr ""
+
+#: ./doc/common/tables/nova-zookeeper.xml:31(td)
+msgid "(StrOpt) The prefix used in ZooKeeper to store ephemeral nodes"
+msgstr ""
+
+#: ./doc/common/tables/nova-zookeeper.xml:34(td)
+msgid "sg_retry_interval = 5"
+msgstr ""
+
+#: ./doc/common/tables/nova-zookeeper.xml:35(td)
+msgid "(IntOpt) Number of seconds to wait until retrying to join the session"
+msgstr ""
+
+#: ./doc/common/tables/nova-keymgr.xml:8(caption) ./doc/common/tables/cinder-keymgr.xml:8(caption)
+msgid "Description of configuration options for keymgr"
+msgstr ""
+
+#: ./doc/common/tables/nova-keymgr.xml:19(th) ./doc/common/tables/cinder-keymgr.xml:19(th)
+msgid "[keymgr]"
+msgstr ""
+
+#: ./doc/common/tables/nova-keymgr.xml:22(td)
+msgid "api_class = nova.keymgr.conf_key_mgr.ConfKeyManager"
+msgstr ""
+
+#: ./doc/common/tables/nova-keymgr.xml:23(td) ./doc/common/tables/cinder-keymgr.xml:23(td)
+msgid "(StrOpt) The full class name of the key manager API class"
+msgstr ""
+
+#: ./doc/common/tables/nova-keymgr.xml:26(td) ./doc/common/tables/cinder-keymgr.xml:26(td)
+msgid "fixed_key = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-keymgr.xml:27(td) ./doc/common/tables/cinder-keymgr.xml:27(td)
+msgid "(StrOpt) Fixed key returned by key manager, specified in hex"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml:7(literal) ./doc/common/tables/swift-object-expirer-filter-cache.xml:7(literal)
+msgid "[filter:cache]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml:18(td) ./doc/common/tables/swift-object-expirer-filter-cache.xml:18(td)
+msgid "use = egg:swift#memcache"
 msgstr ""
 
 #: ./doc/common/tables/swift-proxy-server-filter-cache.xml:21(td)
 msgid "set log_name = cache"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:21(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:21(td) ./doc/common/tables/swift-account-server-app-account-server.xml:21(td) ./doc/common/tables/swift-container-server-app-container-server.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:21(td) ./doc/common/tables/swift-object-server-app-object-server.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:21(td)
-msgid "Label to use when logging"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:24(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:24(td) ./doc/common/tables/swift-account-server-app-account-server.xml:24(td) ./doc/common/tables/swift-container-server-app-container-server.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:24(td) ./doc/common/tables/swift-object-server-app-object-server.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:24(td)
-msgid "set log_facility = LOG_LOCAL0"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml:24(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:64(td) ./doc/common/tables/swift-container-server-container-updater.xml:21(td) ./doc/common/tables/swift-container-server-container-replicator.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:24(td) ./doc/common/tables/swift-container-server-container-sync.xml:21(td) ./doc/common/tables/swift-object-server-object-auditor.xml:21(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:27(td) ./doc/common/tables/swift-object-server-object-updater.xml:21(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:24(td) ./doc/common/tables/swift-account-server-app-account-server.xml:24(td) ./doc/common/tables/swift-container-server-app-container-server.xml:24(td) ./doc/common/tables/swift-account-server-account-auditor.xml:21(td) ./doc/common/tables/swift-account-server-account-auditor.xml:33(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:67(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:61(td) ./doc/common/tables/swift-container-server-container-auditor.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:24(td) ./doc/common/tables/swift-object-server-object-replicator.xml:21(td) ./doc/common/tables/swift-account-server-account-replicator.xml:21(td) ./doc/common/tables/swift-object-server-app-object-server.xml:24(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:73(td) ./doc/common/tables/swift-drive-audit-drive-audit.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:24(td) ./doc/common/tables/swift-account-server-account-reaper.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:24(td)
-msgid "Syslog log facility"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:27(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:27(td) ./doc/common/tables/swift-account-server-app-account-server.xml:27(td) ./doc/common/tables/swift-container-server-app-container-server.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:27(td) ./doc/common/tables/swift-object-server-app-object-server.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:27(td)
-msgid "set log_level = INFO"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:27(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:27(td) ./doc/common/tables/swift-account-server-app-account-server.xml:27(td) ./doc/common/tables/swift-container-server-app-container-server.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:27(td) ./doc/common/tables/swift-object-server-app-object-server.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:27(td)
-msgid "Log level"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:30(td)
-msgid "set log_headers = false"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:30(td)
-msgid "If True, log headers in each request"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:33(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:30(td) ./doc/common/tables/swift-account-server-app-account-server.xml:33(td) ./doc/common/tables/swift-container-server-app-container-server.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:33(td) ./doc/common/tables/swift-object-server-app-object-server.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:33(td)
-msgid "set log_address = /dev/log"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml:33(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:70(td) ./doc/common/tables/swift-container-server-container-updater.xml:27(td) ./doc/common/tables/swift-container-server-container-replicator.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:33(td) ./doc/common/tables/swift-container-server-container-sync.xml:27(td) ./doc/common/tables/swift-object-server-object-auditor.xml:27(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:33(td) ./doc/common/tables/swift-object-server-object-updater.xml:27(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:30(td) ./doc/common/tables/swift-account-server-app-account-server.xml:33(td) ./doc/common/tables/swift-container-server-app-container-server.xml:33(td) ./doc/common/tables/swift-account-server-account-auditor.xml:27(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:73(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:67(td) ./doc/common/tables/swift-container-server-container-auditor.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:33(td) ./doc/common/tables/swift-object-server-object-replicator.xml:27(td) ./doc/common/tables/swift-account-server-account-replicator.xml:27(td) ./doc/common/tables/swift-object-server-app-object-server.xml:33(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:82(td) ./doc/common/tables/swift-drive-audit-drive-audit.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:33(td) ./doc/common/tables/swift-account-server-account-reaper.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:33(td)
-msgid "Location where syslog sends the logs to"
-msgstr ""
-
 #: ./doc/common/tables/swift-proxy-server-filter-cache.xml:36(td) ./doc/common/tables/swift-memcache-memcache.xml:18(td)
 msgid "memcache_servers = 127.0.0.1:11211"
 msgstr ""
@@ -18591,10 +22279,6 @@ msgstr ""
 msgid "memcache_serialization_support = 2"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml:39(td) ./doc/common/tables/swift-container-server-DEFAULT.xml:58(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:57(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:60(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:63(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:66(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:69(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:72(td) ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:75(td) ./doc/common/tables/swift-object-server-object-auditor.xml:45(td) ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml:21(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:33(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:57(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:81(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:87(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:90(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:93(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:96(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:102(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:105(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:108(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:111(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:114(td) ./doc/common/tables/swift-proxy-server-filter-dlo.xml:27(td) ./doc/common/tables/swift-container-server-pipeline-main.xml:18(td) ./doc/common/tables/swift-rsyncd-object.xml:18(td) ./doc/common/tables/swift-rsyncd-object.xml:21(td) ./doc/common/tables/swift-rsyncd-object.xml:24(td) ./doc/common/tables/swift-rsyncd-object.xml:27(td) ./doc/common/tables/swift-object-server-pipeline-main.xml:18(td) ./doc/common/tables/swift-account-server-filter-healthcheck.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-slo.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-slo.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-slo.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-slo.xml:36(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:45(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:48(td) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-bulk.xml:36(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:36(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:39(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:42(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:45(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:48(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:51(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:54(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:57(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:60(td) ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:72(td) ./doc/common/tables/swift-rsyncd-account.xml:18(td) ./doc/common/tables/swift-rsyncd-account.xml:21(td) ./doc/common/tables/swift-rsyncd-account.xml:24(td) ./doc/common/tables/swift-rsyncd-account.xml:27(td) ./doc/common/tables/swift-container-sync-realms-realm1.xml:18(td) ./doc/common/tables/swift-container-sync-realms-realm1.xml:21(td) ./doc/common/tables/swift-container-sync-realms-realm1.xml:24(td) ./doc/common/tables/swift-container-sync-realms-realm1.xml:27(td) ./doc/common/tables/swift-container-server-filter-healthcheck.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-container_sync.xml:21(td) ./doc/common/tables/swift-object-server-filter-recon.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml:21(td) ./doc/common/tables/swift-memcache-memcache.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:45(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:51(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:54(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:57(td) ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:60(td) ./doc/common/tables/swift-object-server-object-replicator.xml:45(td) ./doc/common/tables/swift-object-server-object-replicator.xml:51(td) ./doc/common/tables/swift-object-server-object-replicator.xml:75(td) ./doc/common/tables/swift-dispersion-dispersion.xml:24(td) ./doc/common/tables/swift-dispersion-dispersion.xml:33(td) ./doc/common/tables/swift-dispersion-dispersion.xml:42(td) ./doc/common/tables/swift-dispersion-dispersion.xml:48(td) ./doc/common/tables/swift-dispersion-dispersion.xml:51(td) ./doc/common/tables/swift-dispersion-dispersion.xml:57(td) ./doc/common/tables/swift-dispersion-dispersion.xml:60(td) ./doc/common/tables/swift-dispersion-dispersion.xml:63(td) ./doc/common/tables/swift-dispersion-dispersion.xml:66(td) ./doc/common/tables/swift-dispersion-dispersion.xml:69(td) ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:30(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:33(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:36(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:39(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:42(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:45(td) ./doc/common/tables/neutron-rootwrap.xml:50(td) ./doc/common/tables/neutron-rootwrap.xml:54(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:42(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:64(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:67(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:79(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:85(td) ./doc/common/tables/swift-drive-audit-drive-audit.xml:39(td) ./doc/common/tables/swift-object-expirer-pipeline-main.xml:18(td) ./doc/common/tables/swift-container-sync-realms-realm2.xml:18(td) ./doc/common/tables/swift-container-sync-realms-realm2.xml:21(td) ./doc/common/tables/swift-container-sync-realms-realm2.xml:24(td) ./doc/common/tables/swift-container-sync-realms-realm2.xml:27(td) ./doc/common/tables/swift-rsyncd-container.xml:18(td) ./doc/common/tables/swift-rsyncd-container.xml:21(td) ./doc/common/tables/swift-rsyncd-container.xml:24(td) ./doc/common/tables/swift-rsyncd-container.xml:27(td) ./doc/common/tables/swift-object-server-filter-healthcheck.xml:21(td) ./doc/common/tables/swift-account-server-pipeline-main.xml:18(td) ./doc/common/tables/swift-object-expirer-object-expirer.xml:24(td) ./doc/common/tables/swift-object-expirer-object-expirer.xml:27(td) ./doc/common/tables/swift-object-expirer-object-expirer.xml:33(td) ./doc/common/tables/swift-proxy-server-pipeline-main.xml:18(td) ./doc/common/tables/swift-account-server-account-reaper.xml:45(td)
-msgid "No help text available for this option."
-msgstr ""
-
 #: ./doc/common/tables/swift-proxy-server-filter-cache.xml:42(td) ./doc/common/tables/swift-memcache-memcache.xml:24(td)
 msgid "memcache_max_connections = 2"
 msgstr ""
@@ -18603,920 +22287,2184 @@ msgstr ""
 msgid "Max number of connections to each memcached server per worker services"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:8(caption)
-msgid "Description of configuration options for rpc_all"
+#: ./doc/common/tables/nova-ldap.xml:8(caption) ./doc/common/tables/keystone-ldap.xml:8(caption)
+msgid "Description of configuration options for ldap"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:22(td) ./doc/common/tables/cinder-rpc.xml:26(td) ./doc/common/tables/keystone-amqp.xml:22(td) ./doc/common/tables/neutron-rpc.xml:22(td) ./doc/common/tables/glance-amqp.xml:22(td) ./doc/common/tables/heat-amqp.xml:22(td) ./doc/common/tables/ceilometer-amqp.xml:22(td) ./doc/common/tables/nova-rpc.xml:22(td) ./doc/common/tables/trove-amqp.xml:22(td)
-msgid "amqp_auto_delete = False"
+#: ./doc/common/tables/nova-ldap.xml:22(td)
+msgid "ldap_dns_base_dn = ou=hosts,dc=example,dc=org"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:23(td) ./doc/common/tables/cinder-rpc.xml:27(td) ./doc/common/tables/keystone-amqp.xml:23(td) ./doc/common/tables/neutron-rpc.xml:23(td) ./doc/common/tables/glance-amqp.xml:23(td) ./doc/common/tables/heat-amqp.xml:23(td) ./doc/common/tables/ceilometer-amqp.xml:23(td) ./doc/common/tables/nova-rpc.xml:23(td) ./doc/common/tables/trove-amqp.xml:23(td)
-msgid "(BoolOpt) Auto-delete queues in amqp."
+#: ./doc/common/tables/nova-ldap.xml:23(td)
+msgid "(StrOpt) Base DN for DNS entries in LDAP"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:26(td) ./doc/common/tables/cinder-rpc.xml:30(td) ./doc/common/tables/keystone-amqp.xml:26(td) ./doc/common/tables/neutron-rpc.xml:26(td) ./doc/common/tables/glance-amqp.xml:26(td) ./doc/common/tables/heat-amqp.xml:26(td) ./doc/common/tables/ceilometer-amqp.xml:26(td) ./doc/common/tables/nova-rpc.xml:26(td) ./doc/common/tables/trove-amqp.xml:26(td)
-msgid "amqp_durable_queues = False"
+#: ./doc/common/tables/nova-ldap.xml:26(td)
+msgid "ldap_dns_password = password"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:27(td) ./doc/common/tables/cinder-rpc.xml:31(td) ./doc/common/tables/keystone-amqp.xml:27(td) ./doc/common/tables/neutron-rpc.xml:27(td) ./doc/common/tables/glance-amqp.xml:27(td) ./doc/common/tables/heat-amqp.xml:27(td) ./doc/common/tables/ceilometer-amqp.xml:27(td) ./doc/common/tables/nova-rpc.xml:27(td) ./doc/common/tables/trove-amqp.xml:27(td)
-msgid "(BoolOpt) Use durable queues in amqp."
+#: ./doc/common/tables/nova-ldap.xml:27(td)
+msgid "(StrOpt) Password for LDAP DNS"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:30(td) ./doc/common/tables/cinder-rpc.xml:34(td) ./doc/common/tables/keystone-amqp.xml:30(td) ./doc/common/tables/glance-rabbitmq.xml:22(td) ./doc/common/tables/ceilometer-exchange.xml:26(td) ./doc/common/tables/nova-rpc.xml:30(td) ./doc/common/tables/trove-amqp.xml:34(td)
-msgid "control_exchange = openstack"
+#: ./doc/common/tables/nova-ldap.xml:30(td)
+msgid "ldap_dns_servers = ['dns.example.org']"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:31(td) ./doc/common/tables/cinder-rpc.xml:35(td) ./doc/common/tables/keystone-amqp.xml:31(td) ./doc/common/tables/glance-rabbitmq.xml:23(td) ./doc/common/tables/nova-rpc.xml:31(td)
-msgid "(StrOpt) The default exchange under which topics are scoped. May be overridden by an exchange name specified in the transport_url option."
+#: ./doc/common/tables/nova-ldap.xml:31(td)
+msgid "(MultiStrOpt) DNS Servers for LDAP DNS driver"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:34(td) ./doc/common/tables/cinder-rpc.xml:46(td) ./doc/common/tables/glance-rabbitmq.xml:30(td) ./doc/common/tables/nova-kombu.xml:22(td) ./doc/common/tables/keystone-rabbit.xml:26(td)
+#: ./doc/common/tables/nova-ldap.xml:34(td)
+msgid "ldap_dns_soa_expiry = 86400"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml:35(td)
+msgid "(StrOpt) Expiry interval (in seconds) for LDAP DNS driver Statement of Authority"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml:38(td)
+msgid "ldap_dns_soa_hostmaster = hostmaster@example.org"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml:39(td)
+msgid "(StrOpt) Hostmaster for LDAP DNS driver Statement of Authority"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml:42(td)
+msgid "ldap_dns_soa_minimum = 7200"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml:43(td)
+msgid "(StrOpt) Minimum interval (in seconds) for LDAP DNS driver Statement of Authority"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml:46(td)
+msgid "ldap_dns_soa_refresh = 1800"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml:47(td)
+msgid "(StrOpt) Refresh interval (in seconds) for LDAP DNS driver Statement of Authority"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml:50(td)
+msgid "ldap_dns_soa_retry = 3600"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml:51(td)
+msgid "(StrOpt) Retry interval (in seconds) for LDAP DNS driver Statement of Authority"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml:54(td)
+msgid "ldap_dns_url = ldap://ldap.example.com:389"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml:55(td)
+msgid "(StrOpt) URL for LDAP server which will store DNS entries"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml:58(td)
+msgid "ldap_dns_user = uid=admin,ou=people,dc=example,dc=org"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml:59(td)
+msgid "(StrOpt) User for LDAP DNS"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-filter-recon.xml:7(literal) ./doc/common/tables/swift-account-server-filter-recon.xml:7(literal) ./doc/common/tables/swift-object-server-filter-recon.xml:7(literal)
+msgid "[filter:recon]"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-filter-recon.xml:18(td) ./doc/common/tables/swift-account-server-filter-recon.xml:18(td) ./doc/common/tables/swift-object-server-filter-recon.xml:18(td)
+msgid "use = egg:swift#recon"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml:18(td)
+msgid "pipeline = catch_errors gatekeeper healthcheck proxy-logging cache container_sync bulk tempurl slo dlo ratelimit tempauth container-quotas account-quotas proxy-logging proxy-server"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml:22(td) ./doc/common/tables/neutron-common.xml:58(td) ./doc/common/tables/neutron-common.xml:208(td)
+msgid "auth_strategy = keystone"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml:23(td) ./doc/common/tables/nova-authentication.xml:23(td)
+msgid "(StrOpt) The strategy to use for auth: noauth or keystone."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml:133(th)
+msgid "[service_credentials]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml:137(td)
+msgid "(BoolOpt) Disables X.509 certificate validation when an SSL connection to Identity Service is established."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml:140(td)
+msgid "os_auth_url = http://localhost:5000/v2.0"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml:141(td)
+msgid "(StrOpt) Auth URL to use for OpenStack service access."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml:144(td)
+msgid "os_cacert = None"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml:145(td)
+msgid "(StrOpt) Certificate chain for SSL validation."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml:148(td)
+msgid "os_endpoint_type = publicURL"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml:149(td)
+msgid "(StrOpt) Type of endpoint in Identity service catalog to use for communication with OpenStack services."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml:152(td)
+msgid "os_password = admin"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml:153(td)
+msgid "(StrOpt) Password to use for OpenStack service access."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml:156(td) ./doc/common/tables/nova-volumes.xml:46(td) ./doc/common/tables/cinder-compute.xml:46(td) ./doc/common/tables/glance-common.xml:82(td)
+msgid "os_region_name = None"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml:157(td)
+msgid "(StrOpt) Region name to use for OpenStack service endpoints."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml:160(td)
+msgid "os_tenant_id ="
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml:161(td)
+msgid "(StrOpt) Tenant ID to use for OpenStack service access."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml:164(td)
+msgid "os_tenant_name = admin"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml:165(td)
+msgid "(StrOpt) Tenant name to use for OpenStack service access."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml:168(td)
+msgid "os_username = ceilometer"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml:169(td)
+msgid "(StrOpt) User name to use for OpenStack service access."
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml:8(caption) ./doc/common/tables/heat-quota.xml:8(caption) ./doc/common/tables/trove-quota.xml:8(caption) ./doc/common/tables/nova-quota.xml:8(caption)
+msgid "Description of configuration options for quota"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml:23(td)
+msgid "(IntOpt) number of seconds between subsequent usage refreshes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml:26(td)
+msgid "quota_driver = cinder.quota.DbQuotaDriver"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml:27(td)
+msgid "(StrOpt) default driver to use for quota checks"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml:30(td)
+msgid "quota_gigabytes = 1000"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml:31(td)
+msgid "(IntOpt) number of volume gigabytes (snapshots are also included) allowed per project"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml:34(td)
+msgid "quota_snapshots = 10"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml:35(td)
+msgid "(IntOpt) number of volume snapshots allowed per project"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml:38(td)
+msgid "quota_volumes = 10"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml:39(td)
+msgid "(IntOpt) number of volumes allowed per project"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml:43(td)
+msgid "(IntOpt) number of seconds until a reservation expires"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml:46(td)
+msgid "use_default_quota_class = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml:47(td)
+msgid "(BoolOpt) whether to use default quota class for default quota"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml:7(literal)
+msgid "[filter:account-quotas]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml:18(td)
+msgid "use = egg:swift#account_quotas"
+msgstr ""
+
+#: ./doc/common/tables/keystone-os_inherit.xml:8(caption)
+msgid "Description of configuration options for os_inherit"
+msgstr ""
+
+#: ./doc/common/tables/keystone-os_inherit.xml:19(th)
+msgid "[os_inherit]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-os_inherit.xml:23(td)
+msgid "(BoolOpt) role-assignment inheritance to projects from owning domain can be optionally enabled."
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:8(caption)
+msgid "Description of configuration options for sdnve"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:19(th)
+msgid "[SDNVE]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:22(td)
+msgid "base_url = /one/nb/v2/"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:23(td)
+msgid "(StrOpt) Base URL for SDN-VE controller REST API"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:26(td)
+msgid "controller_ips = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:27(td)
+msgid "(ListOpt) List of IP addresses of SDN-VE controller(s)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:30(td)
+msgid "default_tenant_type = OF"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:31(td)
+msgid "(StrOpt) Tenant type: OF (default) and OVERLAY"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:34(td)
+msgid "format = json"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:35(td)
+msgid "(StrOpt) SDN-VE request/response format"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:38(td)
+msgid "info = sdnve_info_string"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:39(td)
+msgid "(StrOpt) SDN-VE RPC subject"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:42(td)
+msgid "integration_bridge = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:46(td)
+msgid "interface_mappings ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:47(td)
+msgid "(ListOpt) List of &lt;physical_network_name&gt;:&lt;interface_name&gt;"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:50(td)
+msgid "of_signature = SDNVE-OF"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:51(td)
+msgid "(StrOpt) The string in tenant description that indicates the tenant is a OF tenant"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:54(td)
+msgid "out_of_band = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:55(td)
+msgid "(BoolOpt) Indicating if controller is out of band or not"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:58(td)
+msgid "overlay_signature = SDNVE-OVERLAY"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:59(td)
+msgid "(StrOpt) The string in tenant description that indicates the tenant is a OVERLAY tenant"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:62(td)
+msgid "password = admin"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:63(td)
+msgid "(StrOpt) SDN-VE administrator password"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:66(td)
+msgid "port = 8443"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:67(td)
+msgid "(StrOpt) SDN-VE controller port number"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:70(td)
+msgid "reset_bridge = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:71(td)
+msgid "(BoolOpt) Reset the integration bridge before use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:74(td)
+msgid "use_fake_controller = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:75(td)
+msgid "(BoolOpt) If set to True uses a fake controller."
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:78(td)
+msgid "userid = admin"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:79(td)
+msgid "(StrOpt) SDN-VE administrator user id"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:82(th)
+msgid "[SDNVE_AGENT]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:85(td) ./doc/common/tables/neutron-hyperv_agent.xml:38(td)
+msgid "polling_interval = 2"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:86(td)
+msgid "(IntOpt) Agent polling interval if necessary"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:89(td) ./doc/common/tables/neutron-common.xml:174(td) ./doc/common/tables/neutron-common.xml:185(td)
+msgid "root_helper = sudo"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:90(td)
+msgid "(StrOpt) Using root helper"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:93(td)
+msgid "rpc = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml:94(td)
+msgid "(BoolOpt) Whether using rpc"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:8(caption) ./doc/common/tables/trove-compute.xml:8(caption) ./doc/common/tables/neutron-compute.xml:8(caption) ./doc/common/tables/cinder-compute.xml:8(caption)
+msgid "Description of configuration options for compute"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:22(td)
+msgid "compute_available_monitors = ['nova.compute.monitors.all_monitors']"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:23(td)
+msgid "(MultiStrOpt) Monitor classes available to the compute which may be specified more than once."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:26(td)
+msgid "compute_driver = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:27(td)
+msgid "(StrOpt) Driver to use for controlling virtualization. Options include: libvirt.LibvirtDriver, xenapi.XenAPIDriver, fake.FakeDriver, baremetal.BareMetalDriver, vmwareapi.VMwareESXDriver, vmwareapi.VMwareVCDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:30(td)
+msgid "compute_manager = nova.compute.manager.ComputeManager"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:31(td)
+msgid "(StrOpt) Full class name for the Manager for compute"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:34(td)
+msgid "compute_monitors ="
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:35(td)
+msgid "(ListOpt) A list of monitors that can be used for getting compute metrics."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:38(td)
+msgid "compute_stats_class = nova.compute.stats.Stats"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:39(td)
+msgid "(StrOpt) Class that will manage stats for the local compute host"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:42(td)
+msgid "console_host = oslo"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:43(td)
+msgid "(StrOpt) Console proxy host to use to connect to instances on this host."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:46(td)
+msgid "console_manager = nova.console.manager.ConsoleProxyManager"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:47(td)
+msgid "(StrOpt) Full class name for the Manager for console proxy"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:50(td)
+msgid "default_flavor = m1.small"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:51(td)
+msgid "(StrOpt) Default flavor to use for the EC2 API only. The Nova API does not support a default flavor."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:58(td) ./doc/common/tables/heat-amqp.xml:38(td) ./doc/common/tables/keystone-amqp.xml:34(td) ./doc/common/tables/ceilometer-exchange.xml:30(td)
+msgid "default_publisher_id = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:59(td) ./doc/common/tables/heat-amqp.xml:39(td) ./doc/common/tables/trove-common.xml:51(td) ./doc/common/tables/keystone-amqp.xml:35(td) ./doc/common/tables/ceilometer-exchange.xml:31(td) ./doc/common/tables/neutron-notifier.xml:27(td)
+msgid "(StrOpt) Default publisher_id for outgoing notifications"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:62(td)
+msgid "enable_instance_password = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:63(td)
+msgid "(BoolOpt) Enables returning of the instance password by the relevant server API calls such as create, rebuild or rescue, If the hypervisor does not support password injection then the password returned will not be correct"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:66(td)
+msgid "heal_instance_info_cache_interval = 60"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:67(td)
+msgid "(IntOpt) Number of seconds between instance info_cache self healing updates"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:70(td)
+msgid "image_cache_manager_interval = 2400"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:71(td)
+msgid "(IntOpt) Number of seconds to wait between runs of the image cache manager"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:74(td)
+msgid "image_cache_subdirectory_name = _base"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:75(td)
+msgid "(StrOpt) Where cached images are stored under $instances_path. This is NOT the full path - just a folder name. For per-compute-host cached images, set to _base_$my_ip"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:78(td)
+msgid "image_handlers = download"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:79(td)
+msgid "(ListOpt) Specifies which image handler extension names to use for handling images. The first extension in the list which can handle the image with a suitable location will be used."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:82(td)
+msgid "instance_build_timeout = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:83(td)
+msgid "(IntOpt) Amount of time in seconds an instance can be in BUILD before going into ERROR status.Set to 0 to disable."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:86(td)
+msgid "instance_delete_interval = 300"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:87(td)
+msgid "(IntOpt) Interval in seconds for retrying failed instance file deletes"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:90(td)
+msgid "instance_usage_audit = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:91(td)
+msgid "(BoolOpt) Generate periodic compute.instance.exists notifications"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:94(td)
+msgid "instance_usage_audit_period = month"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:95(td)
+msgid "(StrOpt) Time period to generate instance usages for. Time period must be hour, day, month or year"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:98(td)
+msgid "instances_path = $state_path/instances"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:99(td)
+msgid "(StrOpt) Where instances are stored on disk"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:102(td)
+msgid "maximum_instance_delete_attempts = 5"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:103(td)
+msgid "(IntOpt) The number of times to attempt to reap an instance's files."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:106(td)
+msgid "reboot_timeout = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:107(td)
+msgid "(IntOpt) Automatically hard reboot an instance if it has been stuck in a rebooting state longer than N seconds. Set to 0 to disable."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:110(td)
+msgid "reclaim_instance_interval = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:111(td)
+msgid "(IntOpt) Interval in seconds for reclaiming deleted instances"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:114(td)
+msgid "resize_confirm_window = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:115(td)
+msgid "(IntOpt) Automatically confirm resizes after N seconds. Set to 0 to disable."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:118(td)
+msgid "resume_guests_state_on_host_boot = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:119(td)
+msgid "(BoolOpt) Whether to start guests that were running before the host rebooted"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:122(td)
+msgid "running_deleted_instance_action = reap"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:123(td)
+msgid "(StrOpt) Action to take if a running deleted instance is detected.Valid options are 'noop', 'log', 'shutdown', or 'reap'. Set to 'noop' to take no action."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:126(td)
+msgid "running_deleted_instance_poll_interval = 1800"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:127(td)
+msgid "(IntOpt) Number of seconds to wait between runs of the cleanup task."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:130(td)
+msgid "running_deleted_instance_timeout = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:131(td)
+msgid "(IntOpt) Number of seconds after being deleted when a running instance should be considered eligible for cleanup."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:134(td)
+msgid "shelved_offload_time = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:135(td)
+msgid "(IntOpt) Time in seconds before a shelved instance is eligible for removing from a host. -1 never offload, 0 offload when shelved"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:138(td)
+msgid "shelved_poll_interval = 3600"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:139(td)
+msgid "(IntOpt) Interval in seconds for polling shelved instances to offload"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:142(td)
+msgid "sync_power_state_interval = 600"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:143(td)
+msgid "(IntOpt) Interval to sync power states between the database and the hypervisor"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:146(td)
+msgid "vif_plugging_is_fatal = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:147(td)
+msgid "(BoolOpt) Fail instance boot if vif plugging fails"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:150(td)
+msgid "vif_plugging_timeout = 300"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml:151(td)
+msgid "(IntOpt) Number of seconds to wait for neutron vif plugging events to arrive before continuing or failing (see vif_plugging_is_fatal). If this is set to zero and vif_plugging_is_fatal is False, events should not be expected to arrive at all."
+msgstr ""
+
+#: ./doc/common/tables/keystone-rabbit.xml:8(caption)
+msgid "Description of configuration options for rabbit"
+msgstr ""
+
+#: ./doc/common/tables/keystone-rabbit.xml:26(td) ./doc/common/tables/glance-rabbitmq.xml:30(td) ./doc/common/tables/nova-kombu.xml:22(td) ./doc/common/tables/cinder-rpc.xml:46(td) ./doc/common/tables/nova-rpc_all.xml:34(td)
 msgid "kombu_reconnect_delay = 1.0"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:35(td) ./doc/common/tables/cinder-rpc.xml:47(td) ./doc/common/tables/glance-rabbitmq.xml:31(td) ./doc/common/tables/nova-kombu.xml:23(td) ./doc/common/tables/keystone-rabbit.xml:27(td)
+#: ./doc/common/tables/keystone-rabbit.xml:27(td) ./doc/common/tables/glance-rabbitmq.xml:31(td) ./doc/common/tables/nova-kombu.xml:23(td) ./doc/common/tables/cinder-rpc.xml:47(td) ./doc/common/tables/nova-rpc_all.xml:35(td)
 msgid "(FloatOpt) How long to wait before reconnecting in response to an AMQP consumer cancel notification."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:38(td) ./doc/common/tables/neutron-kombu.xml:22(td) ./doc/common/tables/cinder-rpc.xml:50(td) ./doc/common/tables/heat-rabbitmq.xml:22(td) ./doc/common/tables/glance-rabbitmq.xml:34(td) ./doc/common/tables/nova-kombu.xml:26(td) ./doc/common/tables/keystone-rabbit.xml:30(td) ./doc/common/tables/ceilometer-rabbitmq.xml:26(td) ./doc/common/tables/trove-amqp.xml:42(td)
-msgid "kombu_ssl_ca_certs ="
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml:39(td) ./doc/common/tables/cinder-rpc.xml:51(td) ./doc/common/tables/glance-rabbitmq.xml:35(td) ./doc/common/tables/nova-kombu.xml:27(td) ./doc/common/tables/keystone-rabbit.xml:31(td)
+#: ./doc/common/tables/keystone-rabbit.xml:31(td) ./doc/common/tables/glance-rabbitmq.xml:35(td) ./doc/common/tables/nova-kombu.xml:27(td) ./doc/common/tables/cinder-rpc.xml:51(td) ./doc/common/tables/nova-rpc_all.xml:39(td)
 msgid "(StrOpt) SSL certification authority file (valid only if SSL enabled)."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:42(td) ./doc/common/tables/neutron-kombu.xml:26(td) ./doc/common/tables/cinder-rpc.xml:54(td) ./doc/common/tables/heat-rabbitmq.xml:26(td) ./doc/common/tables/glance-rabbitmq.xml:38(td) ./doc/common/tables/nova-kombu.xml:30(td) ./doc/common/tables/keystone-rabbit.xml:34(td) ./doc/common/tables/ceilometer-rabbitmq.xml:30(td) ./doc/common/tables/trove-amqp.xml:46(td)
-msgid "kombu_ssl_certfile ="
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml:43(td) ./doc/common/tables/cinder-rpc.xml:55(td) ./doc/common/tables/glance-rabbitmq.xml:39(td) ./doc/common/tables/nova-kombu.xml:31(td) ./doc/common/tables/keystone-rabbit.xml:35(td)
+#: ./doc/common/tables/keystone-rabbit.xml:35(td) ./doc/common/tables/glance-rabbitmq.xml:39(td) ./doc/common/tables/nova-kombu.xml:31(td) ./doc/common/tables/cinder-rpc.xml:55(td) ./doc/common/tables/nova-rpc_all.xml:43(td)
 msgid "(StrOpt) SSL cert file (valid only if SSL enabled)."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:46(td) ./doc/common/tables/neutron-kombu.xml:30(td) ./doc/common/tables/cinder-rpc.xml:58(td) ./doc/common/tables/heat-rabbitmq.xml:30(td) ./doc/common/tables/glance-rabbitmq.xml:42(td) ./doc/common/tables/nova-kombu.xml:34(td) ./doc/common/tables/keystone-rabbit.xml:38(td) ./doc/common/tables/ceilometer-rabbitmq.xml:34(td) ./doc/common/tables/trove-amqp.xml:50(td)
-msgid "kombu_ssl_keyfile ="
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml:47(td) ./doc/common/tables/cinder-rpc.xml:59(td) ./doc/common/tables/glance-rabbitmq.xml:43(td) ./doc/common/tables/nova-kombu.xml:35(td) ./doc/common/tables/keystone-rabbit.xml:39(td)
+#: ./doc/common/tables/keystone-rabbit.xml:39(td) ./doc/common/tables/glance-rabbitmq.xml:43(td) ./doc/common/tables/nova-kombu.xml:35(td) ./doc/common/tables/cinder-rpc.xml:59(td) ./doc/common/tables/nova-rpc_all.xml:47(td)
 msgid "(StrOpt) SSL key file (valid only if SSL enabled)."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:50(td) ./doc/common/tables/neutron-kombu.xml:34(td) ./doc/common/tables/cinder-rpc.xml:62(td) ./doc/common/tables/heat-rabbitmq.xml:34(td) ./doc/common/tables/glance-rabbitmq.xml:46(td) ./doc/common/tables/nova-kombu.xml:38(td) ./doc/common/tables/keystone-rabbit.xml:42(td) ./doc/common/tables/ceilometer-rabbitmq.xml:38(td) ./doc/common/tables/trove-amqp.xml:54(td)
-msgid "kombu_ssl_version ="
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml:51(td) ./doc/common/tables/cinder-rpc.xml:63(td) ./doc/common/tables/glance-rabbitmq.xml:47(td) ./doc/common/tables/nova-kombu.xml:39(td) ./doc/common/tables/keystone-rabbit.xml:43(td)
+#: ./doc/common/tables/keystone-rabbit.xml:43(td) ./doc/common/tables/glance-rabbitmq.xml:47(td) ./doc/common/tables/nova-kombu.xml:39(td) ./doc/common/tables/cinder-rpc.xml:63(td) ./doc/common/tables/nova-rpc_all.xml:51(td)
 msgid "(StrOpt) SSL version to use (valid only if SSL enabled). valid values are TLSv1, SSLv23 and SSLv3. SSLv2 may be available on some distributions."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:54(td) ./doc/common/tables/heat-rpc.xml:30(td) ./doc/common/tables/ceilometer-redis.xml:26(td) ./doc/common/tables/cinder-rpc.xml:66(td) ./doc/common/tables/neutron-rpc.xml:34(td) ./doc/common/tables/trove-rpc.xml:30(td) ./doc/common/tables/keystone-redis.xml:26(td) ./doc/common/tables/glance-matchmaker.xml:22(td) ./doc/common/tables/nova-rpc.xml:34(td)
-msgid "matchmaker_heartbeat_freq = 300"
+#: ./doc/common/tables/cinder-backups_ceph.xml:8(caption)
+msgid "Description of configuration options for backups_ceph"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:55(td) ./doc/common/tables/cinder-rpc.xml:67(td) ./doc/common/tables/keystone-redis.xml:27(td) ./doc/common/tables/glance-matchmaker.xml:23(td) ./doc/common/tables/nova-rpc.xml:35(td)
-msgid "(IntOpt) Heartbeat frequency."
+#: ./doc/common/tables/cinder-backups_ceph.xml:22(td)
+msgid "backup_ceph_chunk_size = 134217728"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:58(td) ./doc/common/tables/heat-rpc.xml:34(td) ./doc/common/tables/ceilometer-redis.xml:30(td) ./doc/common/tables/cinder-rpc.xml:70(td) ./doc/common/tables/neutron-rpc.xml:38(td) ./doc/common/tables/trove-rpc.xml:34(td) ./doc/common/tables/keystone-redis.xml:30(td) ./doc/common/tables/glance-matchmaker.xml:26(td) ./doc/common/tables/nova-rpc.xml:38(td)
-msgid "matchmaker_heartbeat_ttl = 600"
+#: ./doc/common/tables/cinder-backups_ceph.xml:23(td)
+msgid "(IntOpt) The chunk size, in bytes, that a backup is broken into before transfer to the Ceph object store."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:59(td) ./doc/common/tables/heat-rpc.xml:35(td) ./doc/common/tables/ceilometer-redis.xml:31(td) ./doc/common/tables/cinder-rpc.xml:71(td) ./doc/common/tables/neutron-rpc.xml:39(td) ./doc/common/tables/trove-rpc.xml:35(td) ./doc/common/tables/keystone-redis.xml:31(td) ./doc/common/tables/glance-matchmaker.xml:27(td) ./doc/common/tables/nova-rpc.xml:39(td)
-msgid "(IntOpt) Heartbeat time-to-live."
+#: ./doc/common/tables/cinder-backups_ceph.xml:26(td)
+msgid "backup_ceph_conf = /etc/ceph/ceph.conf"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:62(td) ./doc/common/tables/glance-qpid.xml:22(td) ./doc/common/tables/keystone-qpid.xml:22(td) ./doc/common/tables/trove-qpid.xml:22(td) ./doc/common/tables/heat-qpid.xml:22(td) ./doc/common/tables/cinder-rpc.xml:94(td) ./doc/common/tables/neutron-qpid.xml:22(td) ./doc/common/tables/nova-qpid.xml:22(td) ./doc/common/tables/ceilometer-qpid.xml:22(td)
-msgid "qpid_heartbeat = 60"
+#: ./doc/common/tables/cinder-backups_ceph.xml:27(td)
+msgid "(StrOpt) Ceph configuration file to use."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:63(td) ./doc/common/tables/glance-qpid.xml:23(td) ./doc/common/tables/keystone-qpid.xml:23(td) ./doc/common/tables/cinder-rpc.xml:95(td) ./doc/common/tables/nova-qpid.xml:23(td)
-msgid "(IntOpt) Seconds between connection keepalive heartbeats."
+#: ./doc/common/tables/cinder-backups_ceph.xml:30(td)
+msgid "backup_ceph_pool = backups"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:66(td) ./doc/common/tables/glance-qpid.xml:26(td) ./doc/common/tables/keystone-qpid.xml:26(td) ./doc/common/tables/trove-qpid.xml:26(td) ./doc/common/tables/heat-qpid.xml:26(td) ./doc/common/tables/cinder-rpc.xml:98(td) ./doc/common/tables/neutron-qpid.xml:26(td) ./doc/common/tables/nova-qpid.xml:26(td) ./doc/common/tables/ceilometer-qpid.xml:26(td)
-msgid "qpid_hostname = localhost"
+#: ./doc/common/tables/cinder-backups_ceph.xml:31(td)
+msgid "(StrOpt) The Ceph pool where volume backups are stored."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:67(td) ./doc/common/tables/glance-qpid.xml:27(td) ./doc/common/tables/keystone-qpid.xml:27(td) ./doc/common/tables/cinder-rpc.xml:99(td) ./doc/common/tables/nova-qpid.xml:27(td)
-msgid "(StrOpt) Qpid broker hostname."
+#: ./doc/common/tables/cinder-backups_ceph.xml:34(td)
+msgid "backup_ceph_stripe_count = 0"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:70(td) ./doc/common/tables/glance-qpid.xml:30(td) ./doc/common/tables/keystone-qpid.xml:30(td) ./doc/common/tables/trove-qpid.xml:30(td) ./doc/common/tables/heat-qpid.xml:30(td) ./doc/common/tables/cinder-rpc.xml:102(td) ./doc/common/tables/neutron-qpid.xml:30(td) ./doc/common/tables/nova-qpid.xml:30(td) ./doc/common/tables/ceilometer-qpid.xml:30(td)
-msgid "qpid_hosts = $qpid_hostname:$qpid_port"
+#: ./doc/common/tables/cinder-backups_ceph.xml:35(td)
+msgid "(IntOpt) RBD stripe count to use when creating a backup image."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:71(td) ./doc/common/tables/glance-qpid.xml:31(td) ./doc/common/tables/keystone-qpid.xml:31(td) ./doc/common/tables/cinder-rpc.xml:103(td) ./doc/common/tables/nova-qpid.xml:31(td)
-msgid "(ListOpt) Qpid HA cluster host:port pairs."
+#: ./doc/common/tables/cinder-backups_ceph.xml:38(td)
+msgid "backup_ceph_stripe_unit = 0"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:74(td) ./doc/common/tables/glance-qpid.xml:34(td) ./doc/common/tables/keystone-qpid.xml:34(td) ./doc/common/tables/trove-qpid.xml:34(td) ./doc/common/tables/heat-qpid.xml:34(td) ./doc/common/tables/cinder-rpc.xml:106(td) ./doc/common/tables/neutron-qpid.xml:34(td) ./doc/common/tables/nova-qpid.xml:34(td) ./doc/common/tables/ceilometer-qpid.xml:34(td)
-msgid "qpid_password ="
+#: ./doc/common/tables/cinder-backups_ceph.xml:39(td)
+msgid "(IntOpt) RBD stripe unit to use when creating a backup image."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:75(td) ./doc/common/tables/glance-qpid.xml:35(td) ./doc/common/tables/keystone-qpid.xml:35(td) ./doc/common/tables/cinder-rpc.xml:107(td) ./doc/common/tables/nova-qpid.xml:35(td)
-msgid "(StrOpt) Password for Qpid connection."
+#: ./doc/common/tables/cinder-backups_ceph.xml:42(td)
+msgid "backup_ceph_user = cinder"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:78(td) ./doc/common/tables/glance-qpid.xml:38(td) ./doc/common/tables/keystone-qpid.xml:38(td) ./doc/common/tables/trove-qpid.xml:38(td) ./doc/common/tables/heat-qpid.xml:38(td) ./doc/common/tables/cinder-rpc.xml:110(td) ./doc/common/tables/neutron-qpid.xml:38(td) ./doc/common/tables/nova-qpid.xml:38(td) ./doc/common/tables/ceilometer-qpid.xml:38(td)
-msgid "qpid_port = 5672"
+#: ./doc/common/tables/cinder-backups_ceph.xml:43(td)
+msgid "(StrOpt) The Ceph user to connect with. Default here is to use the same user as for Cinder volumes. If not using cephx this should be set to None."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:79(td) ./doc/common/tables/glance-qpid.xml:39(td) ./doc/common/tables/keystone-qpid.xml:39(td) ./doc/common/tables/cinder-rpc.xml:111(td) ./doc/common/tables/nova-qpid.xml:39(td)
-msgid "(IntOpt) Qpid broker port."
+#: ./doc/common/tables/cinder-backups_ceph.xml:46(td)
+msgid "restore_discard_excess_bytes = True"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:82(td) ./doc/common/tables/glance-qpid.xml:42(td) ./doc/common/tables/keystone-qpid.xml:42(td) ./doc/common/tables/trove-qpid.xml:42(td) ./doc/common/tables/heat-qpid.xml:42(td) ./doc/common/tables/cinder-rpc.xml:114(td) ./doc/common/tables/neutron-qpid.xml:42(td) ./doc/common/tables/nova-qpid.xml:42(td) ./doc/common/tables/ceilometer-qpid.xml:42(td)
-msgid "qpid_protocol = tcp"
+#: ./doc/common/tables/cinder-backups_ceph.xml:47(td)
+msgid "(BoolOpt) If True, always discard excess bytes when restoring volumes i.e. pad with zeroes."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:83(td) ./doc/common/tables/glance-qpid.xml:43(td) ./doc/common/tables/keystone-qpid.xml:43(td) ./doc/common/tables/cinder-rpc.xml:115(td) ./doc/common/tables/nova-qpid.xml:43(td)
-msgid "(StrOpt) Transport to use, either 'tcp' or 'ssl'."
+#: ./doc/common/tables/nova-vmware.xml:23(td)
+msgid "(IntOpt) The number of times we retry on failures, e.g., socket error, etc."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:86(td) ./doc/common/tables/glance-qpid.xml:46(td) ./doc/common/tables/keystone-qpid.xml:46(td) ./doc/common/tables/trove-qpid.xml:46(td) ./doc/common/tables/heat-qpid.xml:46(td) ./doc/common/tables/cinder-rpc.xml:118(td) ./doc/common/tables/neutron-qpid.xml:46(td) ./doc/common/tables/nova-qpid.xml:46(td) ./doc/common/tables/ceilometer-qpid.xml:46(td)
-msgid "qpid_sasl_mechanisms ="
+#: ./doc/common/tables/nova-vmware.xml:26(td)
+msgid "cluster_name = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:87(td) ./doc/common/tables/glance-qpid.xml:47(td) ./doc/common/tables/keystone-qpid.xml:47(td) ./doc/common/tables/cinder-rpc.xml:119(td) ./doc/common/tables/nova-qpid.xml:47(td)
-msgid "(StrOpt) Space separated list of SASL mechanisms to use for auth."
+#: ./doc/common/tables/nova-vmware.xml:27(td)
+msgid "(MultiStrOpt) Name of a VMware Cluster ComputeResource. Used only if compute_driver is vmwareapi.VMwareVCDriver."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:90(td) ./doc/common/tables/glance-qpid.xml:50(td) ./doc/common/tables/keystone-qpid.xml:50(td) ./doc/common/tables/trove-qpid.xml:50(td) ./doc/common/tables/heat-qpid.xml:50(td) ./doc/common/tables/cinder-rpc.xml:122(td) ./doc/common/tables/neutron-qpid.xml:50(td) ./doc/common/tables/nova-qpid.xml:50(td) ./doc/common/tables/ceilometer-qpid.xml:50(td)
-msgid "qpid_tcp_nodelay = True"
+#: ./doc/common/tables/nova-vmware.xml:30(td)
+msgid "datastore_regex = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:91(td) ./doc/common/tables/glance-qpid.xml:51(td) ./doc/common/tables/keystone-qpid.xml:51(td) ./doc/common/tables/cinder-rpc.xml:123(td) ./doc/common/tables/nova-qpid.xml:51(td)
-msgid "(BoolOpt) Whether to disable the Nagle algorithm."
+#: ./doc/common/tables/nova-vmware.xml:31(td)
+msgid "(StrOpt) Regex to match the name of a datastore."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:94(td) ./doc/common/tables/glance-qpid.xml:54(td) ./doc/common/tables/keystone-qpid.xml:54(td) ./doc/common/tables/heat-qpid.xml:54(td) ./doc/common/tables/cinder-rpc.xml:126(td) ./doc/common/tables/neutron-qpid.xml:54(td) ./doc/common/tables/nova-qpid.xml:54(td) ./doc/common/tables/ceilometer-qpid.xml:54(td)
-msgid "qpid_topology_version = 1"
+#: ./doc/common/tables/nova-vmware.xml:34(td)
+msgid "host_ip = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:95(td) ./doc/common/tables/glance-qpid.xml:55(td) ./doc/common/tables/keystone-qpid.xml:55(td) ./doc/common/tables/heat-qpid.xml:55(td) ./doc/common/tables/cinder-rpc.xml:127(td) ./doc/common/tables/neutron-qpid.xml:55(td) ./doc/common/tables/nova-qpid.xml:55(td) ./doc/common/tables/ceilometer-qpid.xml:55(td)
-msgid "(IntOpt) The qpid topology version to use. Version 1 is what was originally used by impl_qpid. Version 2 includes some backwards-incompatible changes that allow broker federation to work. Users should update to version 2 when they are able to take everything down, as it requires a clean break."
+#: ./doc/common/tables/nova-vmware.xml:35(td)
+msgid "(StrOpt) Hostname or IP address for connection to VMware ESX/VC host."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:98(td) ./doc/common/tables/glance-qpid.xml:58(td) ./doc/common/tables/keystone-qpid.xml:58(td) ./doc/common/tables/trove-qpid.xml:54(td) ./doc/common/tables/heat-qpid.xml:58(td) ./doc/common/tables/cinder-rpc.xml:130(td) ./doc/common/tables/neutron-qpid.xml:58(td) ./doc/common/tables/nova-qpid.xml:58(td) ./doc/common/tables/ceilometer-qpid.xml:58(td)
-msgid "qpid_username ="
+#: ./doc/common/tables/nova-vmware.xml:38(td)
+msgid "host_password = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:99(td) ./doc/common/tables/glance-qpid.xml:59(td) ./doc/common/tables/keystone-qpid.xml:59(td) ./doc/common/tables/cinder-rpc.xml:131(td) ./doc/common/tables/nova-qpid.xml:59(td)
-msgid "(StrOpt) Username for Qpid connection."
+#: ./doc/common/tables/nova-vmware.xml:39(td)
+msgid "(StrOpt) Password for connection to VMware ESX/VC host."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:102(td) ./doc/common/tables/trove-rabbitmq.xml:22(td) ./doc/common/tables/cinder-rpc.xml:134(td) ./doc/common/tables/heat-rabbitmq.xml:38(td) ./doc/common/tables/glance-rabbitmq.xml:50(td) ./doc/common/tables/neutron-rabbitmq.xml:22(td) ./doc/common/tables/keystone-rabbit.xml:46(td) ./doc/common/tables/ceilometer-rabbitmq.xml:42(td) ./doc/common/tables/nova-rabbitmq.xml:22(td)
-msgid "rabbit_ha_queues = False"
+#: ./doc/common/tables/nova-vmware.xml:42(td)
+msgid "host_username = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:103(td) ./doc/common/tables/cinder-rpc.xml:135(td) ./doc/common/tables/glance-rabbitmq.xml:51(td) ./doc/common/tables/neutron-rabbitmq.xml:23(td) ./doc/common/tables/keystone-rabbit.xml:47(td) ./doc/common/tables/ceilometer-rabbitmq.xml:43(td) ./doc/common/tables/nova-rabbitmq.xml:23(td)
-msgid "(BoolOpt) Use HA queues in RabbitMQ (x-ha-policy: all). If you change this option, you must wipe the RabbitMQ database."
+#: ./doc/common/tables/nova-vmware.xml:43(td)
+msgid "(StrOpt) Username for connection to VMware ESX/VC host."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:106(td) ./doc/common/tables/trove-rabbitmq.xml:26(td) ./doc/common/tables/cinder-rpc.xml:138(td) ./doc/common/tables/heat-rabbitmq.xml:42(td) ./doc/common/tables/glance-rabbitmq.xml:54(td) ./doc/common/tables/neutron-rabbitmq.xml:26(td) ./doc/common/tables/keystone-rabbit.xml:50(td) ./doc/common/tables/ceilometer-rabbitmq.xml:46(td) ./doc/common/tables/nova-rabbitmq.xml:26(td)
-msgid "rabbit_host = localhost"
+#: ./doc/common/tables/nova-vmware.xml:47(td)
+msgid "(StrOpt) Name of Integration Bridge"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:107(td) ./doc/common/tables/cinder-rpc.xml:139(td) ./doc/common/tables/glance-rabbitmq.xml:55(td) ./doc/common/tables/keystone-rabbit.xml:51(td) ./doc/common/tables/nova-rabbitmq.xml:27(td)
-msgid "(StrOpt) The RabbitMQ broker address where a single node is used."
+#: ./doc/common/tables/nova-vmware.xml:50(td)
+msgid "maximum_objects = 100"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:110(td) ./doc/common/tables/trove-rabbitmq.xml:30(td) ./doc/common/tables/cinder-rpc.xml:142(td) ./doc/common/tables/heat-rabbitmq.xml:46(td) ./doc/common/tables/glance-rabbitmq.xml:58(td) ./doc/common/tables/neutron-rabbitmq.xml:30(td) ./doc/common/tables/keystone-rabbit.xml:54(td) ./doc/common/tables/ceilometer-rabbitmq.xml:50(td) ./doc/common/tables/nova-rabbitmq.xml:30(td)
-msgid "rabbit_hosts = $rabbit_host:$rabbit_port"
+#: ./doc/common/tables/nova-vmware.xml:51(td)
+msgid "(IntOpt) The maximum number of ObjectContent data objects that should be returned in a single result. A positive value will cause the operation to suspend the retrieval when the count of objects reaches the specified maximum. The server may still limit the count to something less than the configured value. Any remaining objects may be retrieved with additional requests."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:111(td) ./doc/common/tables/cinder-rpc.xml:143(td) ./doc/common/tables/glance-rabbitmq.xml:59(td) ./doc/common/tables/keystone-rabbit.xml:55(td) ./doc/common/tables/nova-rabbitmq.xml:31(td)
-msgid "(ListOpt) RabbitMQ HA cluster host:port pairs."
+#: ./doc/common/tables/nova-vmware.xml:55(td)
+msgid "(FloatOpt) The interval used for polling of remote tasks."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:114(td) ./doc/common/tables/cinder-rpc.xml:146(td) ./doc/common/tables/glance-rabbitmq.xml:62(td) ./doc/common/tables/keystone-rabbit.xml:58(td) ./doc/common/tables/nova-rabbitmq.xml:34(td)
-msgid "rabbit_login_method = AMQPLAIN"
+#: ./doc/common/tables/nova-vmware.xml:58(td)
+msgid "use_linked_clone = True"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:115(td) ./doc/common/tables/cinder-rpc.xml:147(td) ./doc/common/tables/glance-rabbitmq.xml:63(td) ./doc/common/tables/keystone-rabbit.xml:59(td) ./doc/common/tables/nova-rabbitmq.xml:35(td)
-msgid "(StrOpt) the RabbitMQ login method"
+#: ./doc/common/tables/nova-vmware.xml:59(td)
+msgid "(BoolOpt) Whether to use linked clone"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:118(td) ./doc/common/tables/trove-rabbitmq.xml:34(td) ./doc/common/tables/cinder-rpc.xml:150(td) ./doc/common/tables/heat-rabbitmq.xml:50(td) ./doc/common/tables/glance-rabbitmq.xml:66(td) ./doc/common/tables/neutron-rabbitmq.xml:34(td) ./doc/common/tables/keystone-rabbit.xml:62(td) ./doc/common/tables/ceilometer-rabbitmq.xml:54(td) ./doc/common/tables/nova-rabbitmq.xml:38(td)
-msgid "rabbit_max_retries = 0"
+#: ./doc/common/tables/nova-vmware.xml:62(td)
+msgid "wsdl_location = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:119(td) ./doc/common/tables/cinder-rpc.xml:151(td) ./doc/common/tables/glance-rabbitmq.xml:67(td) ./doc/common/tables/keystone-rabbit.xml:63(td) ./doc/common/tables/nova-rabbitmq.xml:39(td)
-msgid "(IntOpt) Maximum number of RabbitMQ connection retries. Default is 0 (infinite retry count)."
+#: ./doc/common/tables/nova-vmware.xml:63(td)
+msgid "(StrOpt) Optional VIM Service WSDL Location e.g http://&lt;server&gt;/vimService.wsdl. Optional over-ride to default location for bug work-arounds"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:122(td) ./doc/common/tables/trove-rabbitmq.xml:38(td) ./doc/common/tables/cinder-rpc.xml:154(td) ./doc/common/tables/heat-rabbitmq.xml:54(td) ./doc/common/tables/glance-rabbitmq.xml:70(td) ./doc/common/tables/neutron-rabbitmq.xml:38(td) ./doc/common/tables/keystone-rabbit.xml:66(td) ./doc/common/tables/ceilometer-rabbitmq.xml:58(td) ./doc/common/tables/nova-rabbitmq.xml:42(td)
-msgid "rabbit_password = guest"
+#: ./doc/common/tables/heat-cfn_api.xml:8(caption)
+msgid "Description of configuration options for cfn_api"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:123(td) ./doc/common/tables/cinder-rpc.xml:155(td) ./doc/common/tables/glance-rabbitmq.xml:71(td) ./doc/common/tables/keystone-rabbit.xml:67(td) ./doc/common/tables/nova-rabbitmq.xml:43(td)
-msgid "(StrOpt) The RabbitMQ password."
+#: ./doc/common/tables/heat-cfn_api.xml:22(td)
+msgid "instance_connection_https_validate_certificates = 1"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:126(td) ./doc/common/tables/trove-rabbitmq.xml:42(td) ./doc/common/tables/cinder-rpc.xml:158(td) ./doc/common/tables/heat-rabbitmq.xml:58(td) ./doc/common/tables/glance-rabbitmq.xml:74(td) ./doc/common/tables/neutron-rabbitmq.xml:42(td) ./doc/common/tables/keystone-rabbit.xml:70(td) ./doc/common/tables/ceilometer-rabbitmq.xml:62(td) ./doc/common/tables/nova-rabbitmq.xml:46(td)
-msgid "rabbit_port = 5672"
+#: ./doc/common/tables/heat-cfn_api.xml:23(td)
+msgid "(StrOpt) Instance connection to CFN/CW API validate certs if SSL is used."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:127(td) ./doc/common/tables/cinder-rpc.xml:159(td) ./doc/common/tables/glance-rabbitmq.xml:75(td) ./doc/common/tables/keystone-rabbit.xml:71(td) ./doc/common/tables/nova-rabbitmq.xml:47(td)
-msgid "(IntOpt) The RabbitMQ broker port where a single node is used."
+#: ./doc/common/tables/heat-cfn_api.xml:26(td)
+msgid "instance_connection_is_secure = 0"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:130(td) ./doc/common/tables/trove-rabbitmq.xml:46(td) ./doc/common/tables/cinder-rpc.xml:162(td) ./doc/common/tables/heat-rabbitmq.xml:62(td) ./doc/common/tables/glance-rabbitmq.xml:78(td) ./doc/common/tables/neutron-rabbitmq.xml:46(td) ./doc/common/tables/keystone-rabbit.xml:74(td) ./doc/common/tables/ceilometer-rabbitmq.xml:66(td) ./doc/common/tables/nova-rabbitmq.xml:50(td)
-msgid "rabbit_retry_backoff = 2"
+#: ./doc/common/tables/heat-cfn_api.xml:27(td)
+msgid "(StrOpt) Instance connection to CFN/CW API via https."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:131(td) ./doc/common/tables/cinder-rpc.xml:163(td) ./doc/common/tables/glance-rabbitmq.xml:79(td) ./doc/common/tables/keystone-rabbit.xml:75(td) ./doc/common/tables/nova-rabbitmq.xml:51(td)
-msgid "(IntOpt) How long to backoff for between retries when connecting to RabbitMQ."
+#: ./doc/common/tables/heat-cfn_api.xml:30(th)
+msgid "[heat_api_cfn]"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:134(td) ./doc/common/tables/trove-rabbitmq.xml:50(td) ./doc/common/tables/cinder-rpc.xml:166(td) ./doc/common/tables/heat-rabbitmq.xml:66(td) ./doc/common/tables/glance-rabbitmq.xml:82(td) ./doc/common/tables/neutron-rabbitmq.xml:50(td) ./doc/common/tables/keystone-rabbit.xml:78(td) ./doc/common/tables/ceilometer-rabbitmq.xml:70(td) ./doc/common/tables/nova-rabbitmq.xml:54(td)
-msgid "rabbit_retry_interval = 1"
+#: ./doc/common/tables/heat-cfn_api.xml:34(td) ./doc/common/tables/heat-api.xml:104(td) ./doc/common/tables/heat-cloudwatch_api.xml:30(td)
+msgid "(IntOpt) Number of backlog requests to configure the socket with."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:135(td) ./doc/common/tables/cinder-rpc.xml:167(td) ./doc/common/tables/glance-rabbitmq.xml:83(td) ./doc/common/tables/keystone-rabbit.xml:79(td) ./doc/common/tables/nova-rabbitmq.xml:55(td)
-msgid "(IntOpt) How frequently to retry connecting with RabbitMQ."
+#: ./doc/common/tables/heat-cfn_api.xml:37(td) ./doc/common/tables/heat-api.xml:107(td) ./doc/common/tables/heat-cloudwatch_api.xml:33(td) ./doc/common/tables/glance-common.xml:34(td) ./doc/common/tables/neutron-common.xml:70(td)
+msgid "bind_host = 0.0.0.0"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:138(td) ./doc/common/tables/trove-rabbitmq.xml:54(td) ./doc/common/tables/cinder-rpc.xml:170(td) ./doc/common/tables/heat-rabbitmq.xml:70(td) ./doc/common/tables/glance-rabbitmq.xml:86(td) ./doc/common/tables/neutron-rabbitmq.xml:54(td) ./doc/common/tables/keystone-rabbit.xml:82(td) ./doc/common/tables/ceilometer-rabbitmq.xml:74(td) ./doc/common/tables/nova-rabbitmq.xml:58(td)
-msgid "rabbit_use_ssl = False"
+#: ./doc/common/tables/heat-cfn_api.xml:38(td) ./doc/common/tables/heat-api.xml:108(td) ./doc/common/tables/heat-cloudwatch_api.xml:34(td) ./doc/common/tables/glance-common.xml:35(td)
+msgid "(StrOpt) Address to bind the server. Useful when selecting a particular network interface."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:139(td) ./doc/common/tables/cinder-rpc.xml:171(td) ./doc/common/tables/glance-rabbitmq.xml:87(td) ./doc/common/tables/keystone-rabbit.xml:83(td) ./doc/common/tables/nova-rabbitmq.xml:59(td)
-msgid "(BoolOpt) Connect over SSL for RabbitMQ."
+#: ./doc/common/tables/heat-cfn_api.xml:41(td)
+msgid "bind_port = 8000"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:142(td) ./doc/common/tables/trove-rabbitmq.xml:58(td) ./doc/common/tables/cinder-rpc.xml:174(td) ./doc/common/tables/heat-rabbitmq.xml:74(td) ./doc/common/tables/glance-rabbitmq.xml:90(td) ./doc/common/tables/neutron-rabbitmq.xml:58(td) ./doc/common/tables/keystone-rabbit.xml:86(td) ./doc/common/tables/ceilometer-rabbitmq.xml:78(td) ./doc/common/tables/nova-rabbitmq.xml:62(td)
-msgid "rabbit_userid = guest"
+#: ./doc/common/tables/heat-cfn_api.xml:42(td) ./doc/common/tables/heat-api.xml:112(td) ./doc/common/tables/heat-cloudwatch_api.xml:38(td) ./doc/common/tables/glance-common.xml:39(td)
+msgid "(IntOpt) The port on which the server will listen."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:143(td) ./doc/common/tables/cinder-rpc.xml:175(td) ./doc/common/tables/glance-rabbitmq.xml:91(td) ./doc/common/tables/keystone-rabbit.xml:87(td) ./doc/common/tables/nova-rabbitmq.xml:63(td)
-msgid "(StrOpt) The RabbitMQ userid."
+#: ./doc/common/tables/heat-cfn_api.xml:46(td) ./doc/common/tables/heat-api.xml:116(td) ./doc/common/tables/heat-cloudwatch_api.xml:42(td)
+msgid "(StrOpt) Location of the SSL certificate file to use for SSL mode."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:146(td) ./doc/common/tables/trove-rabbitmq.xml:62(td) ./doc/common/tables/cinder-rpc.xml:178(td) ./doc/common/tables/heat-rabbitmq.xml:78(td) ./doc/common/tables/glance-rabbitmq.xml:94(td) ./doc/common/tables/neutron-rabbitmq.xml:62(td) ./doc/common/tables/keystone-rabbit.xml:90(td) ./doc/common/tables/ceilometer-rabbitmq.xml:82(td) ./doc/common/tables/nova-rabbitmq.xml:66(td)
-msgid "rabbit_virtual_host = /"
+#: ./doc/common/tables/heat-cfn_api.xml:50(td) ./doc/common/tables/heat-api.xml:120(td) ./doc/common/tables/heat-cloudwatch_api.xml:46(td)
+msgid "(StrOpt) Location of the SSL key file to use for enabling SSL mode."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:147(td) ./doc/common/tables/cinder-rpc.xml:179(td) ./doc/common/tables/glance-rabbitmq.xml:95(td) ./doc/common/tables/keystone-rabbit.xml:91(td) ./doc/common/tables/nova-rabbitmq.xml:67(td)
-msgid "(StrOpt) The RabbitMQ virtual host."
+#: ./doc/common/tables/heat-cfn_api.xml:53(td) ./doc/common/tables/trove-api.xml:66(td) ./doc/common/tables/heat-api.xml:123(td) ./doc/common/tables/cinder-api.xml:46(td) ./doc/common/tables/heat-cloudwatch_api.xml:49(td) ./doc/common/tables/glance-wsgi.xml:30(td) ./doc/common/tables/nova-api.xml:42(td) ./doc/common/tables/neutron-api.xml:42(td)
+msgid "max_header_line = 16384"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:150(td) ./doc/common/tables/cinder-rpc.xml:182(td) ./doc/common/tables/keystone-amqp.xml:46(td) ./doc/common/tables/glance-amqp.xml:38(td) ./doc/common/tables/nova-rpc.xml:42(td)
-msgid "rpc_backend = rabbit"
+#: ./doc/common/tables/heat-cfn_api.xml:54(td) ./doc/common/tables/heat-api.xml:124(td) ./doc/common/tables/cinder-api.xml:47(td) ./doc/common/tables/nova-api.xml:43(td)
+msgid "(IntOpt) Maximum line size of message headers to be accepted. max_header_line may need to be increased when using large tokens (typically those generated by the Keystone v3 API with big service catalogs)."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:151(td) ./doc/common/tables/cinder-rpc.xml:183(td) ./doc/common/tables/keystone-amqp.xml:47(td) ./doc/common/tables/glance-amqp.xml:39(td) ./doc/common/tables/nova-rpc.xml:43(td)
-msgid "(StrOpt) The messaging driver to use, defaults to rabbit. Other drivers include qpid and zmq."
+#: ./doc/common/tables/heat-cfn_api.xml:57(td) ./doc/common/tables/heat-api.xml:127(td) ./doc/common/tables/heat-cloudwatch_api.xml:53(td)
+msgid "workers = 0"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:154(td) ./doc/common/tables/heat-rpc.xml:42(td) ./doc/common/tables/glance-zmq.xml:22(td) ./doc/common/tables/cinder-rpc.xml:186(td) ./doc/common/tables/keystone-amqp.xml:50(td) ./doc/common/tables/ceilometer-rpc.xml:34(td) ./doc/common/tables/neutron-rpc.xml:46(td) ./doc/common/tables/trove-rpc.xml:54(td) ./doc/common/tables/nova-rpc.xml:46(td)
-msgid "rpc_cast_timeout = 30"
+#: ./doc/common/tables/heat-cfn_api.xml:58(td) ./doc/common/tables/heat-api.xml:128(td) ./doc/common/tables/heat-cloudwatch_api.xml:54(td)
+msgid "(IntOpt) Number of workers for Heat service."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:155(td) ./doc/common/tables/heat-rpc.xml:43(td) ./doc/common/tables/glance-zmq.xml:23(td) ./doc/common/tables/cinder-rpc.xml:187(td) ./doc/common/tables/keystone-amqp.xml:51(td) ./doc/common/tables/ceilometer-rpc.xml:35(td) ./doc/common/tables/neutron-rpc.xml:47(td) ./doc/common/tables/trove-rpc.xml:55(td) ./doc/common/tables/nova-rpc.xml:47(td)
-msgid "(IntOpt) Seconds to wait before a cast expires (TTL). Only supported by impl_zmq."
+#: ./doc/common/tables/heat-cfn_api.xml:61(th) ./doc/common/tables/heat-api.xml:142(th) ./doc/common/tables/keystone-ssl.xml:54(th) ./doc/common/tables/nova-ca.xml:62(th) ./doc/common/tables/cinder-ssl.xml:19(th) ./doc/common/tables/trove-ssl.xml:19(th) ./doc/common/tables/heat-cloudwatch_api.xml:57(th) ./doc/common/tables/neutron-ssl.xml:34(th) ./doc/common/tables/ceilometer-ssl.xml:19(th)
+msgid "[ssl]"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:158(td) ./doc/common/tables/heat-rpc.xml:46(td) ./doc/common/tables/cinder-rpc.xml:190(td) ./doc/common/tables/keystone-amqp.xml:54(td) ./doc/common/tables/ceilometer-rpc.xml:38(td) ./doc/common/tables/neutron-rpc.xml:50(td) ./doc/common/tables/glance-amqp.xml:42(td) ./doc/common/tables/trove-rpc.xml:58(td) ./doc/common/tables/nova-rpc.xml:50(td)
-msgid "rpc_conn_pool_size = 30"
+#: ./doc/common/tables/heat-cfn_api.xml:65(td) ./doc/common/tables/heat-api.xml:146(td) ./doc/common/tables/cinder-common.xml:175(td) ./doc/common/tables/cinder-ssl.xml:23(td) ./doc/common/tables/trove-ssl.xml:23(td) ./doc/common/tables/heat-cloudwatch_api.xml:61(td) ./doc/common/tables/neutron-ssl.xml:23(td) ./doc/common/tables/neutron-ssl.xml:38(td) ./doc/common/tables/nova-wsgi.xml:27(td) ./doc/common/tables/ceilometer-ssl.xml:23(td)
+msgid "(StrOpt) CA certificate file to use to verify connecting clients"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:159(td) ./doc/common/tables/cinder-rpc.xml:191(td) ./doc/common/tables/keystone-amqp.xml:55(td) ./doc/common/tables/glance-amqp.xml:43(td) ./doc/common/tables/nova-rpc.xml:51(td)
-msgid "(IntOpt) Size of RPC connection pool."
+#: ./doc/common/tables/heat-cfn_api.xml:69(td) ./doc/common/tables/heat-api.xml:150(td) ./doc/common/tables/cinder-common.xml:179(td) ./doc/common/tables/cinder-ssl.xml:27(td) ./doc/common/tables/trove-ssl.xml:27(td) ./doc/common/tables/heat-cloudwatch_api.xml:65(td) ./doc/common/tables/neutron-ssl.xml:27(td) ./doc/common/tables/neutron-ssl.xml:42(td) ./doc/common/tables/ceilometer-ssl.xml:27(td)
+msgid "(StrOpt) Certificate file to use when starting the server securely"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:162(td) ./doc/common/tables/heat-rpc.xml:50(td) ./doc/common/tables/cinder-rpc.xml:194(td) ./doc/common/tables/keystone-amqp.xml:58(td) ./doc/common/tables/ceilometer-rpc.xml:42(td) ./doc/common/tables/neutron-rpc.xml:54(td) ./doc/common/tables/glance-amqp.xml:46(td) ./doc/common/tables/trove-rpc.xml:62(td) ./doc/common/tables/nova-rpc.xml:54(td)
-msgid "rpc_response_timeout = 60"
+#: ./doc/common/tables/heat-cfn_api.xml:73(td) ./doc/common/tables/heat-api.xml:154(td) ./doc/common/tables/cinder-common.xml:183(td) ./doc/common/tables/cinder-ssl.xml:31(td) ./doc/common/tables/trove-ssl.xml:31(td) ./doc/common/tables/heat-cloudwatch_api.xml:69(td) ./doc/common/tables/neutron-ssl.xml:31(td) ./doc/common/tables/neutron-ssl.xml:46(td) ./doc/common/tables/ceilometer-ssl.xml:31(td)
+msgid "(StrOpt) Private key file to use when starting the server securely"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:163(td) ./doc/common/tables/cinder-rpc.xml:195(td) ./doc/common/tables/keystone-amqp.xml:59(td) ./doc/common/tables/glance-amqp.xml:47(td) ./doc/common/tables/nova-rpc.xml:55(td)
-msgid "(IntOpt) Seconds to wait for a response from a call."
+#: ./doc/common/tables/neutron-vmware.xml:22(td)
+msgid "default_interface_name = breth0"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:166(td) ./doc/common/tables/heat-rpc.xml:54(td) ./doc/common/tables/cinder-rpc.xml:198(td) ./doc/common/tables/keystone-amqp.xml:62(td) ./doc/common/tables/ceilometer-rpc.xml:46(td) ./doc/common/tables/neutron-rpc.xml:58(td) ./doc/common/tables/glance-amqp.xml:50(td) ./doc/common/tables/trove-rpc.xml:66(td) ./doc/common/tables/nova-rpc.xml:58(td)
-msgid "rpc_thread_pool_size = 64"
+#: ./doc/common/tables/neutron-vmware.xml:23(td)
+msgid "(StrOpt) Name of the interface on a L2 Gateway transport nodewhich should be used by default when setting up a network connection"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:167(td) ./doc/common/tables/cinder-rpc.xml:199(td) ./doc/common/tables/keystone-amqp.xml:63(td) ./doc/common/tables/glance-amqp.xml:51(td) ./doc/common/tables/nova-rpc.xml:59(td)
-msgid "(IntOpt) Size of RPC greenthread pool."
+#: ./doc/common/tables/neutron-vmware.xml:26(td)
+msgid "default_l2_gw_service_uuid = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:170(td) ./doc/common/tables/glance-zmq.xml:26(td) ./doc/common/tables/keystone-zeromq.xml:22(td) ./doc/common/tables/cinder-rpc.xml:202(td) ./doc/common/tables/trove-zeromq.xml:22(td) ./doc/common/tables/ceilometer-rpc.xml:50(td) ./doc/common/tables/heat-zeromq.xml:22(td) ./doc/common/tables/nova-zeromq.xml:22(td) ./doc/common/tables/neutron-zeromq.xml:22(td)
+#: ./doc/common/tables/neutron-vmware.xml:27(td)
+msgid "(StrOpt) Unique identifier of the NSX L2 Gateway service which will be used by default for network gateways"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:30(td)
+msgid "default_l3_gw_service_uuid = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:31(td)
+msgid "(StrOpt) Unique identifier of the NSX L3 Gateway service which will be used for implementing routers and floating IPs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:34(td)
+msgid "default_service_cluster_uuid = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:35(td)
+msgid "(StrOpt) Unique identifier of the Service Cluster which will be used by logical services like dhcp and metadata"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:38(td)
+msgid "default_tz_uuid = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:39(td)
+msgid "(StrOpt) This is uuid of the default NSX Transport zone that will be used for creating tunneled isolated \"Neutron\" networks. It needs to be created in NSX before starting Neutron with the nsx plugin."
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:42(td)
+msgid "http_timeout = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:43(td)
+msgid "(IntOpt) Time before aborting a request"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:46(td)
+msgid "nsx_controllers = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:47(td)
+msgid "(ListOpt) Lists the NSX controllers in this cluster"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:50(td)
+msgid "nsx_password = admin"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:51(td)
+msgid "(StrOpt) Password for NSX controllers in this cluster"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:54(td)
+msgid "nsx_user = admin"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:55(td)
+msgid "(StrOpt) User name for NSX controllers in this cluster"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:58(td)
+msgid "redirects = 2"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:59(td)
+msgid "(IntOpt) Number of times a redirect should be followed"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:62(td)
+msgid "req_timeout = 30"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:63(td)
+msgid "(IntOpt) Total time limit for a cluster request"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:66(td)
+msgid "retries = 2"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:67(td)
+msgid "(IntOpt) Number of time a request should be retried"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:70(th) ./doc/common/tables/neutron-ml2_mlnx.xml:19(th) ./doc/common/tables/neutron-mlnx.xml:19(th)
+msgid "[ESWITCH]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:73(td)
+msgid "retries = 3"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:74(td)
+msgid "(IntOpt) The number of retries the agent will send request to daemon before giving up"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:77(th)
+msgid "[NSX]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:80(td)
+msgid "agent_mode = agent"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:81(td)
+msgid "(StrOpt) The mode used to implement DHCP/metadata services."
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:84(td)
+msgid "concurrent_connections = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:85(td)
+msgid "(IntOpt) Maximum concurrent connections to each NSX controller."
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:88(td)
+msgid "default_transport_type = stt"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:89(td)
+msgid "(StrOpt) The default network tranport type to use (stt, gre, bridge, ipsec_gre, or ipsec_stt)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:92(td)
+msgid "max_lp_per_bridged_ls = 5000"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:93(td)
+msgid "(IntOpt) Maximum number of ports of a logical switch on a bridged transport zone (default 5000)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:96(td)
+msgid "max_lp_per_overlay_ls = 256"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:97(td)
+msgid "(IntOpt) Maximum number of ports of a logical switch on an overlay transport zone (default 256)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:100(td)
+msgid "metadata_mode = access_network"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:101(td)
+msgid "(StrOpt) If set to access_network this enables a dedicated connection to the metadata proxy for metadata server access via Neutron router. If set to dhcp_host_route this enables host route injection via the dhcp agent. This option is only useful if running on a host that does not support namespaces otherwise access_network should be used."
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:104(td)
+msgid "nsx_gen_timeout = -1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:105(td)
+msgid "(IntOpt) Number of seconds a generation id should be valid for (default -1 meaning do not time out)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:108(td)
+msgid "replication_mode = service"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:109(td)
+msgid "(StrOpt) The default option leverages service nodes to perform packet replication though one could set to this to 'source' to perform replication locally. This is useful if one does not want to deploy a service node(s)."
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:112(th)
+msgid "[NSX_DHCP]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:115(td)
+msgid "default_lease_time = 43200"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:116(td)
+msgid "(IntOpt) Default DHCP lease time"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:119(td)
+msgid "domain_name = openstacklocal"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:120(td) ./doc/common/tables/nova-network.xml:51(td) ./doc/common/tables/neutron-common.xml:111(td)
+msgid "(StrOpt) Domain to use for building the hostnames"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:123(td)
+msgid "extra_domain_name_servers ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:124(td)
+msgid "(ListOpt) Comma separated list of additional domain name servers"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:127(th)
+msgid "[NSX_LSN]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:130(td)
+msgid "sync_on_missing_data = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:131(td)
+msgid "(BoolOpt) Pull LSN information from NSX in case it is missing from the local data store. This is useful to rebuild the local store in case of server recovery."
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:134(th)
+msgid "[NSX_METADATA]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:137(td)
+msgid "metadata_server_address = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:138(td)
+msgid "(StrOpt) IP address used by Metadata server."
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:141(td)
+msgid "metadata_server_port = 8775"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:142(td)
+msgid "(IntOpt) TCP Port used by Metadata server."
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:145(td)
+msgid "metadata_shared_secret ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:146(td) ./doc/common/tables/neutron-metadata.xml:35(td)
+msgid "(StrOpt) Shared secret to sign instance-id request"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:149(th)
+msgid "[NSX_SYNC]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:152(td)
+msgid "always_read_status = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:153(td)
+msgid "(BoolOpt) Always read operational status from backend on show operations. Enabling this option might slow down the system."
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:156(td)
+msgid "max_random_sync_delay = 0"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:157(td)
+msgid "(IntOpt) Maximum value for the additional random delay in seconds between runs of the state synchronization task"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:160(td)
+msgid "min_chunk_size = 500"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:161(td)
+msgid "(IntOpt) Minimum number of resources to be retrieved from NSX during state synchronization"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:164(td)
+msgid "min_sync_req_delay = 1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:165(td)
+msgid "(IntOpt) Minimum delay, in seconds, between two state synchronization queries to NSX. It must not exceed state_sync_interval"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:168(td)
+msgid "state_sync_interval = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:169(td)
+msgid "(IntOpt) Interval in seconds between runs of the state synchronization task. Set it to 0 to disable it"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:172(th)
+msgid "[vcns]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:175(td)
+msgid "datacenter_moid = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:176(td)
+msgid "(StrOpt) Optional parameter identifying the ID of datacenter to deploy NSX Edges"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:179(td)
+msgid "datastore_id = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:180(td) ./doc/common/tables/neutron-vmware.xml:184(td)
+msgid "(StrOpt) Optional parameter identifying the ID of datastore to deploy NSX Edges"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:183(td)
+msgid "deployment_container_id = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:187(td)
+msgid "external_network = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:188(td)
+msgid "(StrOpt) Network ID for physical network connectivity"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:191(td)
+msgid "manager_uri = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:192(td)
+msgid "(StrOpt) uri for vsm"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:195(td)
+msgid "password = default"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:196(td)
+msgid "(StrOpt) Password for vsm"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:199(td) ./doc/common/tables/neutron-embrane_lb.xml:62(td)
+msgid "resource_pool_id = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:200(td)
+msgid "(StrOpt) Optional parameter identifying the ID of resource to deploy NSX Edges"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:203(td)
+msgid "task_status_check_interval = 2000"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:204(td)
+msgid "(IntOpt) Task status check interval"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:207(td)
+msgid "user = admin"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml:208(td)
+msgid "(StrOpt) User name for vsm"
+msgstr ""
+
+#: ./doc/common/tables/nova-rdp.xml:8(caption)
+msgid "Description of configuration options for rdp"
+msgstr ""
+
+#: ./doc/common/tables/nova-rdp.xml:19(th)
+msgid "[rdp]"
+msgstr ""
+
+#: ./doc/common/tables/nova-rdp.xml:23(td)
+msgid "(BoolOpt) Enable RDP related features"
+msgstr ""
+
+#: ./doc/common/tables/nova-rdp.xml:26(td)
+msgid "html5_proxy_base_url = http://127.0.0.1:6083/"
+msgstr ""
+
+#: ./doc/common/tables/nova-rdp.xml:27(td)
+msgid "(StrOpt) Location of RDP html5 console proxy, in the form \"http://127.0.0.1:6083/\""
+msgstr ""
+
+#: ./doc/common/tables/keystone-assignment.xml:8(caption)
+msgid "Description of configuration options for assignment"
+msgstr ""
+
+#: ./doc/common/tables/keystone-assignment.xml:19(th)
+msgid "[assignment]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-assignment.xml:22(td) ./doc/common/tables/keystone-token.xml:26(td)
+msgid "cache_time = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-assignment.xml:23(td)
+msgid "(IntOpt) TTL (in seconds) to cache assignment data. This has no effect unless global caching is enabled."
+msgstr ""
+
+#: ./doc/common/tables/keystone-assignment.xml:26(td) ./doc/common/tables/keystone-revoke.xml:22(td) ./doc/common/tables/keystone-token.xml:30(td)
+msgid "caching = True"
+msgstr ""
+
+#: ./doc/common/tables/keystone-assignment.xml:27(td)
+msgid "(BoolOpt) Toggle for assignment caching. This has no effect unless global caching is enabled."
+msgstr ""
+
+#: ./doc/common/tables/keystone-assignment.xml:30(td)
+msgid "driver = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-assignment.xml:31(td)
+msgid "(StrOpt) Keystone Assignment backend driver."
+msgstr ""
+
+#: ./doc/common/tables/keystone-assignment.xml:35(td)
+msgid "(IntOpt) Maximum number of entities that will be returned in an assignment collection."
+msgstr ""
+
+#: ./doc/common/tables/nova-zeromq.xml:8(caption) ./doc/common/tables/heat-zeromq.xml:8(caption) ./doc/common/tables/neutron-zeromq.xml:8(caption) ./doc/common/tables/keystone-zeromq.xml:8(caption) ./doc/common/tables/trove-zeromq.xml:8(caption)
+msgid "Description of configuration options for zeromq"
+msgstr ""
+
+#: ./doc/common/tables/nova-zeromq.xml:22(td) ./doc/common/tables/heat-zeromq.xml:22(td) ./doc/common/tables/neutron-zeromq.xml:22(td) ./doc/common/tables/keystone-zeromq.xml:22(td) ./doc/common/tables/ceilometer-rpc.xml:50(td) ./doc/common/tables/glance-zmq.xml:26(td) ./doc/common/tables/cinder-rpc.xml:202(td) ./doc/common/tables/trove-zeromq.xml:22(td) ./doc/common/tables/nova-rpc_all.xml:170(td)
 msgid "rpc_zmq_bind_address = *"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:171(td) ./doc/common/tables/glance-zmq.xml:27(td) ./doc/common/tables/keystone-zeromq.xml:23(td) ./doc/common/tables/cinder-rpc.xml:203(td) ./doc/common/tables/trove-zeromq.xml:23(td) ./doc/common/tables/ceilometer-rpc.xml:51(td) ./doc/common/tables/heat-zeromq.xml:23(td) ./doc/common/tables/nova-zeromq.xml:23(td) ./doc/common/tables/neutron-zeromq.xml:23(td)
+#: ./doc/common/tables/nova-zeromq.xml:23(td) ./doc/common/tables/heat-zeromq.xml:23(td) ./doc/common/tables/neutron-zeromq.xml:23(td) ./doc/common/tables/keystone-zeromq.xml:23(td) ./doc/common/tables/ceilometer-rpc.xml:51(td) ./doc/common/tables/glance-zmq.xml:27(td) ./doc/common/tables/cinder-rpc.xml:203(td) ./doc/common/tables/trove-zeromq.xml:23(td) ./doc/common/tables/nova-rpc_all.xml:171(td)
 msgid "(StrOpt) ZeroMQ bind address. Should be a wildcard (*), an ethernet interface, or IP. The \"host\" option should point or resolve to this address."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:174(td) ./doc/common/tables/glance-zmq.xml:30(td) ./doc/common/tables/keystone-zeromq.xml:26(td) ./doc/common/tables/cinder-rpc.xml:206(td) ./doc/common/tables/trove-zeromq.xml:26(td) ./doc/common/tables/ceilometer-rpc.xml:54(td) ./doc/common/tables/heat-zeromq.xml:26(td) ./doc/common/tables/nova-zeromq.xml:26(td) ./doc/common/tables/neutron-zeromq.xml:26(td)
+#: ./doc/common/tables/nova-zeromq.xml:26(td) ./doc/common/tables/heat-zeromq.xml:26(td) ./doc/common/tables/neutron-zeromq.xml:26(td) ./doc/common/tables/keystone-zeromq.xml:26(td) ./doc/common/tables/ceilometer-rpc.xml:54(td) ./doc/common/tables/glance-zmq.xml:30(td) ./doc/common/tables/cinder-rpc.xml:206(td) ./doc/common/tables/trove-zeromq.xml:26(td) ./doc/common/tables/nova-rpc_all.xml:174(td)
 msgid "rpc_zmq_contexts = 1"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:175(td) ./doc/common/tables/glance-zmq.xml:31(td) ./doc/common/tables/keystone-zeromq.xml:27(td) ./doc/common/tables/cinder-rpc.xml:207(td) ./doc/common/tables/nova-zeromq.xml:27(td)
+#: ./doc/common/tables/nova-zeromq.xml:27(td) ./doc/common/tables/keystone-zeromq.xml:27(td) ./doc/common/tables/glance-zmq.xml:31(td) ./doc/common/tables/cinder-rpc.xml:207(td) ./doc/common/tables/nova-rpc_all.xml:175(td)
 msgid "(IntOpt) Number of ZeroMQ contexts, defaults to 1."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:178(td) ./doc/common/tables/glance-zmq.xml:34(td) ./doc/common/tables/keystone-zeromq.xml:30(td) ./doc/common/tables/cinder-rpc.xml:210(td) ./doc/common/tables/trove-zeromq.xml:30(td) ./doc/common/tables/ceilometer-rpc.xml:58(td) ./doc/common/tables/heat-zeromq.xml:30(td) ./doc/common/tables/nova-zeromq.xml:30(td) ./doc/common/tables/neutron-zeromq.xml:30(td)
+#: ./doc/common/tables/nova-zeromq.xml:30(td) ./doc/common/tables/heat-zeromq.xml:30(td) ./doc/common/tables/neutron-zeromq.xml:30(td) ./doc/common/tables/keystone-zeromq.xml:30(td) ./doc/common/tables/ceilometer-rpc.xml:58(td) ./doc/common/tables/glance-zmq.xml:34(td) ./doc/common/tables/cinder-rpc.xml:210(td) ./doc/common/tables/trove-zeromq.xml:30(td) ./doc/common/tables/nova-rpc_all.xml:178(td)
 msgid "rpc_zmq_host = oslo"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:179(td) ./doc/common/tables/glance-zmq.xml:35(td) ./doc/common/tables/keystone-zeromq.xml:31(td) ./doc/common/tables/cinder-rpc.xml:211(td) ./doc/common/tables/trove-zeromq.xml:31(td) ./doc/common/tables/ceilometer-rpc.xml:59(td) ./doc/common/tables/heat-zeromq.xml:31(td) ./doc/common/tables/nova-zeromq.xml:31(td) ./doc/common/tables/neutron-zeromq.xml:31(td)
+#: ./doc/common/tables/nova-zeromq.xml:31(td) ./doc/common/tables/heat-zeromq.xml:31(td) ./doc/common/tables/neutron-zeromq.xml:31(td) ./doc/common/tables/keystone-zeromq.xml:31(td) ./doc/common/tables/ceilometer-rpc.xml:59(td) ./doc/common/tables/glance-zmq.xml:35(td) ./doc/common/tables/cinder-rpc.xml:211(td) ./doc/common/tables/trove-zeromq.xml:31(td) ./doc/common/tables/nova-rpc_all.xml:179(td)
 msgid "(StrOpt) Name of this node. Must be a valid hostname, FQDN, or IP address. Must match \"host\" option, if running Nova."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:182(td) ./doc/common/tables/glance-zmq.xml:38(td) ./doc/common/tables/keystone-zeromq.xml:34(td) ./doc/common/tables/cinder-rpc.xml:214(td) ./doc/common/tables/trove-zeromq.xml:34(td) ./doc/common/tables/ceilometer-rpc.xml:62(td) ./doc/common/tables/heat-zeromq.xml:34(td) ./doc/common/tables/nova-zeromq.xml:34(td) ./doc/common/tables/neutron-zeromq.xml:34(td)
+#: ./doc/common/tables/nova-zeromq.xml:34(td) ./doc/common/tables/heat-zeromq.xml:34(td) ./doc/common/tables/neutron-zeromq.xml:34(td) ./doc/common/tables/keystone-zeromq.xml:34(td) ./doc/common/tables/ceilometer-rpc.xml:62(td) ./doc/common/tables/glance-zmq.xml:38(td) ./doc/common/tables/cinder-rpc.xml:214(td) ./doc/common/tables/trove-zeromq.xml:34(td) ./doc/common/tables/nova-rpc_all.xml:182(td)
 msgid "rpc_zmq_ipc_dir = /var/run/openstack"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:183(td) ./doc/common/tables/glance-zmq.xml:39(td) ./doc/common/tables/keystone-zeromq.xml:35(td) ./doc/common/tables/cinder-rpc.xml:215(td) ./doc/common/tables/nova-zeromq.xml:35(td)
+#: ./doc/common/tables/nova-zeromq.xml:35(td) ./doc/common/tables/keystone-zeromq.xml:35(td) ./doc/common/tables/glance-zmq.xml:39(td) ./doc/common/tables/cinder-rpc.xml:215(td) ./doc/common/tables/nova-rpc_all.xml:183(td)
 msgid "(StrOpt) Directory for holding IPC sockets."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:186(td) ./doc/common/tables/glance-zmq.xml:42(td) ./doc/common/tables/keystone-zeromq.xml:38(td) ./doc/common/tables/cinder-rpc.xml:218(td) ./doc/common/tables/nova-zeromq.xml:38(td)
+#: ./doc/common/tables/nova-zeromq.xml:38(td) ./doc/common/tables/keystone-zeromq.xml:38(td) ./doc/common/tables/glance-zmq.xml:42(td) ./doc/common/tables/cinder-rpc.xml:218(td) ./doc/common/tables/nova-rpc_all.xml:186(td)
 msgid "rpc_zmq_matchmaker = oslo.messaging._drivers.matchmaker.MatchMakerLocalhost"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:187(td) ./doc/common/tables/glance-zmq.xml:43(td) ./doc/common/tables/keystone-zeromq.xml:39(td) ./doc/common/tables/cinder-rpc.xml:219(td) ./doc/common/tables/nova-zeromq.xml:39(td)
+#: ./doc/common/tables/nova-zeromq.xml:39(td) ./doc/common/tables/keystone-zeromq.xml:39(td) ./doc/common/tables/glance-zmq.xml:43(td) ./doc/common/tables/cinder-rpc.xml:219(td) ./doc/common/tables/nova-rpc_all.xml:187(td)
 msgid "(StrOpt) MatchMaker driver."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:190(td) ./doc/common/tables/glance-zmq.xml:46(td) ./doc/common/tables/keystone-zeromq.xml:42(td) ./doc/common/tables/cinder-rpc.xml:222(td) ./doc/common/tables/trove-zeromq.xml:42(td) ./doc/common/tables/ceilometer-rpc.xml:70(td) ./doc/common/tables/heat-zeromq.xml:42(td) ./doc/common/tables/nova-zeromq.xml:42(td) ./doc/common/tables/neutron-zeromq.xml:42(td)
+#: ./doc/common/tables/nova-zeromq.xml:42(td) ./doc/common/tables/heat-zeromq.xml:42(td) ./doc/common/tables/neutron-zeromq.xml:42(td) ./doc/common/tables/keystone-zeromq.xml:42(td) ./doc/common/tables/ceilometer-rpc.xml:70(td) ./doc/common/tables/glance-zmq.xml:46(td) ./doc/common/tables/cinder-rpc.xml:222(td) ./doc/common/tables/trove-zeromq.xml:42(td) ./doc/common/tables/nova-rpc_all.xml:190(td)
 msgid "rpc_zmq_port = 9501"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:191(td) ./doc/common/tables/glance-zmq.xml:47(td) ./doc/common/tables/keystone-zeromq.xml:43(td) ./doc/common/tables/cinder-rpc.xml:223(td) ./doc/common/tables/nova-zeromq.xml:43(td)
+#: ./doc/common/tables/nova-zeromq.xml:43(td) ./doc/common/tables/keystone-zeromq.xml:43(td) ./doc/common/tables/glance-zmq.xml:47(td) ./doc/common/tables/cinder-rpc.xml:223(td) ./doc/common/tables/nova-rpc_all.xml:191(td)
 msgid "(IntOpt) ZeroMQ receiver listening port."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:194(td) ./doc/common/tables/glance-zmq.xml:50(td) ./doc/common/tables/keystone-zeromq.xml:46(td) ./doc/common/tables/cinder-rpc.xml:226(td) ./doc/common/tables/trove-zeromq.xml:46(td) ./doc/common/tables/ceilometer-rpc.xml:74(td) ./doc/common/tables/heat-zeromq.xml:46(td) ./doc/common/tables/nova-zeromq.xml:46(td) ./doc/common/tables/neutron-zeromq.xml:46(td)
+#: ./doc/common/tables/nova-zeromq.xml:46(td) ./doc/common/tables/heat-zeromq.xml:46(td) ./doc/common/tables/neutron-zeromq.xml:46(td) ./doc/common/tables/keystone-zeromq.xml:46(td) ./doc/common/tables/ceilometer-rpc.xml:74(td) ./doc/common/tables/glance-zmq.xml:50(td) ./doc/common/tables/cinder-rpc.xml:226(td) ./doc/common/tables/trove-zeromq.xml:46(td) ./doc/common/tables/nova-rpc_all.xml:194(td)
 msgid "rpc_zmq_topic_backlog = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:195(td) ./doc/common/tables/glance-zmq.xml:51(td) ./doc/common/tables/keystone-zeromq.xml:47(td) ./doc/common/tables/cinder-rpc.xml:227(td) ./doc/common/tables/trove-zeromq.xml:47(td) ./doc/common/tables/ceilometer-rpc.xml:75(td) ./doc/common/tables/heat-zeromq.xml:47(td) ./doc/common/tables/nova-zeromq.xml:47(td) ./doc/common/tables/neutron-zeromq.xml:47(td)
+#: ./doc/common/tables/nova-zeromq.xml:47(td) ./doc/common/tables/heat-zeromq.xml:47(td) ./doc/common/tables/neutron-zeromq.xml:47(td) ./doc/common/tables/keystone-zeromq.xml:47(td) ./doc/common/tables/ceilometer-rpc.xml:75(td) ./doc/common/tables/glance-zmq.xml:51(td) ./doc/common/tables/cinder-rpc.xml:227(td) ./doc/common/tables/trove-zeromq.xml:47(td) ./doc/common/tables/nova-rpc_all.xml:195(td)
 msgid "(IntOpt) Maximum number of ingress messages to locally buffer per topic. Default is unlimited."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:201(td) ./doc/common/tables/nova-rpc.xml:65(td)
-msgid "rpc_driver_queue_base = cells.intercell"
+#: ./doc/common/tables/cinder-storage.xml:8(caption)
+msgid "Description of configuration options for storage"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:202(td) ./doc/common/tables/nova-rpc.xml:66(td)
-msgid "(StrOpt) Base queue name to use when communicating between cells. Various topics by message type will be appended to this."
+#: ./doc/common/tables/cinder-storage.xml:22(td)
+msgid "allocated_capacity_weight_multiplier = -1.0"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:205(th) ./doc/common/tables/trove-redis.xml:34(th) ./doc/common/tables/heat-rpc.xml:58(th) ./doc/common/tables/ceilometer-redis.xml:49(th) ./doc/common/tables/cinder-rpc.xml:238(th) ./doc/common/tables/neutron-rpc.xml:73(th) ./doc/common/tables/keystone-redis.xml:42(th) ./doc/common/tables/glance-matchmaker.xml:30(th) ./doc/common/tables/nova-rpc.xml:69(th)
-msgid "[matchmaker_ring]"
+#: ./doc/common/tables/cinder-storage.xml:23(td) ./doc/common/tables/cinder-storage.xml:27(td)
+msgid "(FloatOpt) Multiplier used for weighing volume capacity. Negative numbers mean to stack vs spread."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:208(td) ./doc/common/tables/trove-redis.xml:37(td) ./doc/common/tables/heat-rpc.xml:61(td) ./doc/common/tables/ceilometer-redis.xml:52(td) ./doc/common/tables/cinder-rpc.xml:241(td) ./doc/common/tables/neutron-rpc.xml:76(td) ./doc/common/tables/keystone-redis.xml:45(td) ./doc/common/tables/glance-matchmaker.xml:33(td) ./doc/common/tables/nova-rpc.xml:72(td)
-msgid "ringfile = /etc/oslo/matchmaker_ring.json"
+#: ./doc/common/tables/cinder-storage.xml:26(td)
+msgid "capacity_weight_multiplier = 1.0"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:209(td) ./doc/common/tables/cinder-rpc.xml:242(td) ./doc/common/tables/keystone-redis.xml:46(td) ./doc/common/tables/glance-matchmaker.xml:34(td) ./doc/common/tables/nova-rpc.xml:73(td)
-msgid "(StrOpt) Matchmaker ring file (JSON)."
+#: ./doc/common/tables/cinder-storage.xml:30(td)
+msgid "enabled_backends = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:212(th) ./doc/common/tables/nova-rpc.xml:76(th) ./doc/common/tables/nova-upgrade_levels.xml:26(th)
-msgid "[upgrade_levels]"
+#: ./doc/common/tables/cinder-storage.xml:31(td)
+msgid "(ListOpt) A list of backend names to use. These backend names should be backed by a unique [CONFIG] group with its options"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:215(td) ./doc/common/tables/nova-rpc.xml:79(td)
-msgid "baseapi = None"
+#: ./doc/common/tables/cinder-storage.xml:34(td)
+msgid "iscsi_helper = tgtadm"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml:216(td) ./doc/common/tables/nova-rpc.xml:80(td)
-msgid "(StrOpt) Set a version cap for messages sent to the base api in any service"
+#: ./doc/common/tables/cinder-storage.xml:35(td)
+msgid "(StrOpt) iscsi target user-land tool to use"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_l2pop.xml:8(caption)
-msgid "Description of configuration options for ml2_l2pop"
+#: ./doc/common/tables/cinder-storage.xml:38(td)
+msgid "iscsi_iotype = fileio"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_l2pop.xml:19(th)
-msgid "[l2pop]"
+#: ./doc/common/tables/cinder-storage.xml:39(td)
+msgid "(StrOpt) Sets the behavior of the iSCSI target to either perform blockio or fileio optionally, auto can be set and Cinder will autodetect type of backing device"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_l2pop.xml:22(td)
-msgid "agent_boot_time = 180"
+#: ./doc/common/tables/cinder-storage.xml:42(td)
+msgid "iscsi_ip_address = $my_ip"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_l2pop.xml:23(td)
-msgid "(IntOpt) Delay within which agent is expected to update existing ports whent it restarts"
+#: ./doc/common/tables/cinder-storage.xml:43(td)
+msgid "(StrOpt) The IP address that the iSCSI daemon is listening on"
 msgstr ""
 
-#: ./doc/common/tables/glance-qpid.xml:8(caption) ./doc/common/tables/keystone-qpid.xml:8(caption) ./doc/common/tables/trove-qpid.xml:8(caption) ./doc/common/tables/heat-qpid.xml:8(caption) ./doc/common/tables/neutron-qpid.xml:8(caption) ./doc/common/tables/nova-qpid.xml:8(caption) ./doc/common/tables/ceilometer-qpid.xml:8(caption)
-msgid "Description of configuration options for qpid"
+#: ./doc/common/tables/cinder-storage.xml:46(td)
+msgid "iscsi_num_targets = 100"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:7(literal) ./doc/common/tables/swift-container-server-container-updater.xml:7(literal) ./doc/common/tables/swift-container-server-container-replicator.xml:7(literal) ./doc/common/tables/swift-container-server-container-sync.xml:7(literal) ./doc/common/tables/swift-container-server-pipeline-main.xml:7(literal) ./doc/common/tables/swift-container-server-app-container-server.xml:7(literal) ./doc/common/tables/swift-container-server-filter-healthcheck.xml:7(literal) ./doc/common/tables/swift-container-server-container-auditor.xml:7(literal) ./doc/common/tables/swift-container-server-filter-recon.xml:7(literal)
-msgid "container-server.conf-sample"
+#: ./doc/common/tables/cinder-storage.xml:47(td)
+msgid "(IntOpt) The maximum number of iscsi target ids per host"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:18(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:18(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:18(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:18(td)
-msgid "bind_ip = 0.0.0.0"
+#: ./doc/common/tables/cinder-storage.xml:50(td)
+msgid "iscsi_port = 3260"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:18(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:18(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:18(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:18(td)
-msgid "IP Address for server to bind to"
+#: ./doc/common/tables/cinder-storage.xml:51(td)
+msgid "(IntOpt) The port that the iSCSI daemon is listening on"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:21(td)
-msgid "bind_port = 6001"
+#: ./doc/common/tables/cinder-storage.xml:54(td)
+msgid "iscsi_target_prefix = iqn.2010-10.org.openstack:"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:21(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:21(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:21(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:21(td)
-msgid "Port for server to bind to"
+#: ./doc/common/tables/cinder-storage.xml:55(td)
+msgid "(StrOpt) prefix for iscsi volumes"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:24(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:24(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:24(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:24(td)
-msgid "bind_timeout = 30"
+#: ./doc/common/tables/cinder-storage.xml:58(td)
+msgid "iser_helper = tgtadm"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:24(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:24(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:24(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:24(td)
-msgid "Seconds to attempt bind before giving up"
+#: ./doc/common/tables/cinder-storage.xml:59(td)
+msgid "(StrOpt) iser target user-land tool to use"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:27(td) ./doc/common/tables/heat-cfn_api.xml:33(td) ./doc/common/tables/trove-debug.xml:26(td) ./doc/common/tables/neutron-wsgi.xml:22(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:27(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:27(td) ./doc/common/tables/heat-cloudwatch_api.xml:29(td) ./doc/common/tables/glance-common.xml:30(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:27(td) ./doc/common/tables/heat-api.xml:103(td)
-msgid "backlog = 4096"
+#: ./doc/common/tables/cinder-storage.xml:62(td)
+msgid "iser_ip_address = $my_ip"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:27(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:27(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:27(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:27(td)
-msgid "Maximum number of allowed pending TCP connections"
+#: ./doc/common/tables/cinder-storage.xml:63(td)
+msgid "(StrOpt) The IP address that the iSER daemon is listening on"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:30(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:21(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:30(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:30(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:33(td)
-msgid "user = swift"
+#: ./doc/common/tables/cinder-storage.xml:66(td)
+msgid "iser_num_targets = 100"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:30(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:21(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:30(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:30(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:33(td)
-msgid "User to run as"
+#: ./doc/common/tables/cinder-storage.xml:67(td)
+msgid "(IntOpt) The maximum number of iser target ids per host"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:33(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:18(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:33(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:33(td) ./doc/common/tables/swift-dispersion-dispersion.xml:45(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:30(td)
-msgid "swift_dir = /etc/swift"
+#: ./doc/common/tables/cinder-storage.xml:70(td)
+msgid "iser_port = 3260"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:33(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:18(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:33(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:33(td) ./doc/common/tables/swift-dispersion-dispersion.xml:45(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:30(td)
-msgid "Swift configuration directory"
+#: ./doc/common/tables/cinder-storage.xml:71(td)
+msgid "(IntOpt) The port that the iSER daemon is listening on"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:36(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:36(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:36(td)
-msgid "devices = /srv/node"
+#: ./doc/common/tables/cinder-storage.xml:74(td)
+msgid "iser_target_prefix = iqn.2010-10.org.iser.openstack:"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:36(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:36(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:36(td)
-msgid "Parent directory of where devices are mounted"
+#: ./doc/common/tables/cinder-storage.xml:75(td)
+msgid "(StrOpt) prefix for iser volumes"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:39(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:39(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:39(td)
-msgid "mount_check = true"
+#: ./doc/common/tables/cinder-storage.xml:78(td)
+msgid "max_gigabytes = 10000"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:39(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:39(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:39(td)
-msgid "Whether or not check if the devices are mounted to prevent accidentally writing to the root device"
+#: ./doc/common/tables/cinder-storage.xml:79(td)
+msgid "(IntOpt) This configure option has been deprecated along with the SimpleScheduler. New scheduler is able to gather capacity information for each host, thus setting the maximum number of volume gigabytes for host is no longer needed. It's safe to remove this configure from cinder.conf."
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:42(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:42(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:42(td)
-msgid "disable_fallocate = false"
+#: ./doc/common/tables/cinder-storage.xml:82(td)
+msgid "migration_create_volume_timeout_secs = 300"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:42(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:42(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:42(td)
-msgid "Disable \"fast fail\" fallocate checks if the underlying filesystem does not support it."
+#: ./doc/common/tables/cinder-storage.xml:83(td)
+msgid "(IntOpt) Timeout for creating the volume to migrate to when performing volume migration (seconds)"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:45(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:51(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:45(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:45(td)
-msgid "workers = auto"
+#: ./doc/common/tables/cinder-storage.xml:86(td)
+msgid "num_iser_scan_tries = 3"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:45(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:51(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:45(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:45(td)
-msgid "a much higher value, one can reduce the impact of slow file system operations in one request from negatively impacting other requests."
+#: ./doc/common/tables/cinder-storage.xml:87(td)
+msgid "(IntOpt) The maximum number of times to rescan iSER targetto find volume"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:48(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:54(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:48(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:48(td)
-msgid "max_clients = 1024"
+#: ./doc/common/tables/cinder-storage.xml:90(td)
+msgid "num_volume_device_scan_tries = 3"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:48(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:54(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:48(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:48(td)
-msgid "Maximum number of clients one worker can process simultaneously Lowering the number of clients handled per worker, and raising the number of workers can lessen the impact that a CPU intensive, or blocking, request can have on other requests served by the same worker. If the maximum number of clients is set to one, then a given worker will not perform another call while processing, allowing other workers a chance to process it."
+#: ./doc/common/tables/cinder-storage.xml:91(td)
+msgid "(IntOpt) The maximum number of times to rescan targets to find volume"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:58(td)
-msgid "allowed_sync_hosts = 127.0.0.1"
+#: ./doc/common/tables/cinder-storage.xml:94(td)
+msgid "volume_backend_name = None"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:61(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:24(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:64(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:58(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:70(td)
-msgid "log_name = swift"
+#: ./doc/common/tables/cinder-storage.xml:95(td)
+msgid "(StrOpt) The backend name for a given driver implementation"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:61(td) ./doc/common/tables/swift-container-server-container-updater.xml:18(td) ./doc/common/tables/swift-container-server-container-replicator.xml:18(td) ./doc/common/tables/swift-container-server-container-sync.xml:18(td) ./doc/common/tables/swift-object-server-object-auditor.xml:18(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:24(td) ./doc/common/tables/swift-object-server-object-updater.xml:18(td) ./doc/common/tables/swift-account-server-account-auditor.xml:18(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:64(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:58(td) ./doc/common/tables/swift-container-server-container-auditor.xml:18(td) ./doc/common/tables/swift-object-server-object-replicator.xml:18(td) ./doc/common/tables/swift-account-server-account-replicator.xml:18(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:70(td) ./doc/common/tables/swift-account-server-account-reaper.xml:18(td)
-msgid "Label used when logging"
+#: ./doc/common/tables/cinder-storage.xml:98(td) ./doc/common/tables/nova-libvirt.xml:85(td)
+msgid "volume_clear = zero"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:64(td) ./doc/common/tables/swift-container-server-container-updater.xml:21(td) ./doc/common/tables/swift-container-server-container-replicator.xml:21(td) ./doc/common/tables/swift-container-server-container-sync.xml:21(td) ./doc/common/tables/swift-object-server-object-auditor.xml:21(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:27(td) ./doc/common/tables/swift-object-server-object-updater.xml:21(td) ./doc/common/tables/swift-account-server-account-auditor.xml:21(td) ./doc/common/tables/swift-account-server-account-auditor.xml:33(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:67(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:61(td) ./doc/common/tables/swift-container-server-container-auditor.xml:21(td) ./doc/common/tables/swift-object-server-object-replicator.xml:21(td) ./doc/common/tables/swift-account-server-account-replicator.xml:21(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:73(td) ./doc/common/tables/swift-drive-audit-drive-audit.xml:21(td) ./doc/common/tables/swift-account-server-account-reaper.xml:21(td)
-msgid "log_facility = LOG_LOCAL0"
+#: ./doc/common/tables/cinder-storage.xml:99(td)
+msgid "(StrOpt) Method used to wipe old voumes (valid options are: none, zero, shred)"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:67(td) ./doc/common/tables/swift-container-server-container-updater.xml:24(td) ./doc/common/tables/swift-container-server-container-replicator.xml:24(td) ./doc/common/tables/swift-container-server-container-sync.xml:24(td) ./doc/common/tables/swift-object-server-object-auditor.xml:24(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:30(td) ./doc/common/tables/swift-object-server-object-updater.xml:24(td) ./doc/common/tables/swift-account-server-account-auditor.xml:24(td) ./doc/common/tables/swift-account-server-account-auditor.xml:36(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:70(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:64(td) ./doc/common/tables/swift-container-server-container-auditor.xml:24(td) ./doc/common/tables/swift-object-server-object-replicator.xml:24(td) ./doc/common/tables/swift-account-server-account-replicator.xml:24(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:76(td) ./doc/common/tables/swift-drive-audit-drive-audit.xml:24(td) ./doc/common/tables/swift-account-server-account-reaper.xml:24(td)
-msgid "log_level = INFO"
+#: ./doc/common/tables/cinder-storage.xml:102(td)
+msgid "volume_clear_ionice = None"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:67(td) ./doc/common/tables/swift-container-server-container-updater.xml:24(td) ./doc/common/tables/swift-container-server-container-replicator.xml:24(td) ./doc/common/tables/swift-container-server-container-sync.xml:24(td) ./doc/common/tables/swift-object-server-object-auditor.xml:24(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:30(td) ./doc/common/tables/swift-object-server-object-updater.xml:24(td) ./doc/common/tables/swift-account-server-account-auditor.xml:24(td) ./doc/common/tables/swift-account-server-account-auditor.xml:36(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:70(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:64(td) ./doc/common/tables/swift-container-server-container-auditor.xml:24(td) ./doc/common/tables/swift-object-server-object-replicator.xml:24(td) ./doc/common/tables/swift-account-server-account-replicator.xml:24(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:76(td) ./doc/common/tables/swift-drive-audit-drive-audit.xml:24(td) ./doc/common/tables/swift-account-server-account-reaper.xml:24(td)
-msgid "Logging level"
+#: ./doc/common/tables/cinder-storage.xml:103(td)
+msgid "(StrOpt) The flag to pass to ionice to alter the i/o priority of the process used to zero a volume after deletion, for example \"-c3\" for idle only priority."
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:70(td) ./doc/common/tables/swift-container-server-container-updater.xml:27(td) ./doc/common/tables/swift-container-server-container-replicator.xml:27(td) ./doc/common/tables/swift-container-server-container-sync.xml:27(td) ./doc/common/tables/swift-object-server-object-auditor.xml:27(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:33(td) ./doc/common/tables/swift-object-server-object-updater.xml:27(td) ./doc/common/tables/swift-account-server-account-auditor.xml:27(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:73(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:67(td) ./doc/common/tables/swift-container-server-container-auditor.xml:27(td) ./doc/common/tables/swift-object-server-object-replicator.xml:27(td) ./doc/common/tables/swift-account-server-account-replicator.xml:27(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:82(td) ./doc/common/tables/swift-drive-audit-drive-audit.xml:27(td) ./doc/common/tables/swift-account-server-account-reaper.xml:27(td)
-msgid "log_address = /dev/log"
+#: ./doc/common/tables/cinder-storage.xml:106(td) ./doc/common/tables/nova-libvirt.xml:89(td)
+msgid "volume_clear_size = 0"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:73(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:36(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:76(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:70(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:88(td)
-msgid "log_custom_handlers ="
+#: ./doc/common/tables/cinder-storage.xml:107(td) ./doc/common/tables/nova-libvirt.xml:90(td)
+msgid "(IntOpt) Size in MiB to wipe at start of old volumes. 0 =&gt; all"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:73(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:36(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:76(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:70(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:88(td)
-msgid "Comma-separated list of functions to call to setup custom log handlers."
+#: ./doc/common/tables/cinder-storage.xml:110(td)
+msgid "volume_dd_blocksize = 1M"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:76(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:39(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:79(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:73(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:91(td)
-msgid "log_udp_host ="
+#: ./doc/common/tables/cinder-storage.xml:111(td)
+msgid "(StrOpt) The default block size used when copying/clearing volumes"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:76(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:39(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:79(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:73(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:91(td)
-msgid "If not set, the UDB receiver for syslog is disabled."
+#: ./doc/common/tables/cinder-storage.xml:114(td)
+msgid "volume_driver = cinder.volume.drivers.lvm.LVMISCSIDriver"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:79(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:42(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:82(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:76(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:94(td)
-msgid "log_udp_port = 514"
+#: ./doc/common/tables/cinder-storage.xml:115(td)
+msgid "(StrOpt) Driver to use for volume creation"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:79(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:42(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:82(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:76(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:94(td)
-msgid "Port value for UDB receiver, if enabled."
+#: ./doc/common/tables/cinder-storage.xml:118(td)
+msgid "volume_manager = cinder.volume.manager.VolumeManager"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:82(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:45(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:85(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:79(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:97(td)
-msgid "log_statsd_host = localhost"
+#: ./doc/common/tables/cinder-storage.xml:119(td)
+msgid "(StrOpt) full class name for the Manager for volume"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:82(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:45(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:85(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:79(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:97(td)
-msgid "If not set, the StatsD feature is disabled."
+#: ./doc/common/tables/cinder-storage.xml:122(td)
+msgid "volume_service_inithost_offload = False"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:85(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:48(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:88(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:82(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:100(td)
-msgid "log_statsd_port = 8125"
+#: ./doc/common/tables/cinder-storage.xml:123(td)
+msgid "(BoolOpt) Offload pending volume delete during volume service startup"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:85(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:48(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:88(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:82(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:100(td)
-msgid "Port value for the StatsD server."
+#: ./doc/common/tables/cinder-storage.xml:126(td)
+msgid "volume_usage_audit_period = month"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:88(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:51(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:91(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:85(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:103(td)
-msgid "log_statsd_default_sample_rate = 1.0"
+#: ./doc/common/tables/cinder-storage.xml:127(td)
+msgid "(StrOpt) time period to generate volume usages for. Time period must be hour, day, month or year"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:88(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:51(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:91(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:85(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:103(td)
-msgid "Defines the probability of sending a sample for any given event or timing measurement."
+#: ./doc/common/tables/cinder-storage.xml:130(td)
+msgid "volumes_dir = $state_path/volumes"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:92(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:55(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:95(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:89(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:107(td)
-msgid "log_statsd_sample_rate_factor = 1.0"
+#: ./doc/common/tables/cinder-storage.xml:131(td)
+msgid "(StrOpt) Volume configuration file storage directory"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:92(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:55(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:95(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:89(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:107(td)
-msgid "Not recommended to set this to a value less than 1.0, if frequency of logging is too high, tune the log_statsd_default_sample_rate instead."
+#: ./doc/common/tables/cinder-storage.xml:145(td)
+msgid "max_pool_size = 5"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:97(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:60(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:100(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:94(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:112(td)
-msgid "log_statsd_metric_prefix ="
+#: ./doc/common/tables/cinder-storage.xml:150(td) ./doc/common/tables/heat-database.xml:66(td)
+msgid "(IntOpt) maximum db connection retries during startup. (setting -1 implies an infinite retry count)"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:97(td) ./doc/common/tables/swift-object-expirer-DEFAULT.xml:60(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:100(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:94(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:112(td)
-msgid "Value will be prepended to every metric sent to the StatsD server."
+#: ./doc/common/tables/glance-registry.xml:8(caption)
+msgid "Description of configuration options for registry"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:100(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:97(td)
-msgid "db_preallocation = off"
+#: ./doc/common/tables/glance-registry.xml:23(td)
+msgid "(StrOpt) The administrators password."
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:100(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:97(td)
-msgid "If you don't mind the extra disk space usage in overhead, you can turn this on to preallocate disk space with SQLite databases to decrease fragmentation. underlying filesystem does not support it. to setup custom log handlers. bytes you'd like fallocate to reserve, whether there is space for the given file size or not. This is useful for systems that behave badly when they completely run out of space; you can make the services pretend they're out of space early. server. For most cases, this should be `egg:swift#account`. replication passes account can be reclaimed"
+#: ./doc/common/tables/glance-registry.xml:26(td) ./doc/common/tables/neutron-common.xml:26(td) ./doc/common/tables/neutron-common.xml:196(td)
+msgid "admin_tenant_name = None"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:103(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:103(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:100(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:121(td)
-msgid "eventlet_debug = false"
+#: ./doc/common/tables/glance-registry.xml:27(td)
+msgid "(StrOpt) The tenant name of the administrative user."
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:103(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:103(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:100(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:121(td)
-msgid "If true, turn on debug logging for eventlet"
+#: ./doc/common/tables/glance-registry.xml:31(td)
+msgid "(StrOpt) The administrators user name."
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:106(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:106(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:103(td)
-msgid "fallocate_reserve = 0"
+#: ./doc/common/tables/glance-registry.xml:34(td) ./doc/common/tables/neutron-common.xml:54(td) ./doc/common/tables/neutron-common.xml:204(td)
+msgid "auth_region = None"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml:106(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:106(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:103(td)
-msgid "You can set fallocate_reserve to the number of bytes you'd like fallocate to reserve, whether there is space for the given file size or not. This is useful for systems that behave badly when they completely run out of space; you can make the services pretend they're out of space early. server. For most cases, this should be `egg:swift#object`."
+#: ./doc/common/tables/glance-registry.xml:35(td)
+msgid "(StrOpt) The region for the authentication service."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:8(caption)
-msgid "Description of configuration options for ml2_bigswitch"
+#: ./doc/common/tables/glance-registry.xml:39(td)
+msgid "(StrOpt) The strategy to use for authentication."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:19(th) ./doc/common/tables/neutron-bigswitch.xml:19(th)
-msgid "[NOVA]"
+#: ./doc/common/tables/glance-registry.xml:42(td) ./doc/common/tables/neutron-common.xml:62(td) ./doc/common/tables/neutron-common.xml:212(td)
+msgid "auth_url = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:22(td) ./doc/common/tables/neutron-bigswitch.xml:22(td)
-msgid "node_override_vif_802.1qbg ="
+#: ./doc/common/tables/glance-registry.xml:43(td)
+msgid "(StrOpt) The URL to the keystone service."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:23(td) ./doc/common/tables/neutron-bigswitch.xml:23(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to 802.1qbg"
+#: ./doc/common/tables/glance-registry.xml:46(td)
+msgid "registry_client_ca_file = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:26(td) ./doc/common/tables/neutron-bigswitch.xml:26(td)
-msgid "node_override_vif_802.1qbh ="
+#: ./doc/common/tables/glance-registry.xml:47(td)
+msgid "(StrOpt) The path to the certifying authority cert file to use in SSL connections to the registry server."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:27(td) ./doc/common/tables/neutron-bigswitch.xml:27(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to 802.1qbh"
+#: ./doc/common/tables/glance-registry.xml:50(td)
+msgid "registry_client_cert_file = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:30(td) ./doc/common/tables/neutron-bigswitch.xml:30(td)
-msgid "node_override_vif_binding_failed ="
+#: ./doc/common/tables/glance-registry.xml:51(td)
+msgid "(StrOpt) The path to the cert file to use in SSL connections to the registry server."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:31(td) ./doc/common/tables/neutron-bigswitch.xml:31(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to binding_failed"
+#: ./doc/common/tables/glance-registry.xml:54(td)
+msgid "registry_client_insecure = False"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:34(td) ./doc/common/tables/neutron-bigswitch.xml:34(td)
-msgid "node_override_vif_bridge ="
+#: ./doc/common/tables/glance-registry.xml:55(td)
+msgid "(BoolOpt) When using SSL in connections to the registry server, do not require validation via a certifying authority."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:35(td) ./doc/common/tables/neutron-bigswitch.xml:35(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to bridge"
+#: ./doc/common/tables/glance-registry.xml:58(td)
+msgid "registry_client_key_file = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:38(td) ./doc/common/tables/neutron-bigswitch.xml:38(td)
-msgid "node_override_vif_hostdev ="
+#: ./doc/common/tables/glance-registry.xml:59(td)
+msgid "(StrOpt) The path to the key file to use in SSL connections to the registry server."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:39(td) ./doc/common/tables/neutron-bigswitch.xml:39(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to hostdev"
+#: ./doc/common/tables/glance-registry.xml:62(td)
+msgid "registry_client_protocol = http"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:42(td) ./doc/common/tables/neutron-bigswitch.xml:42(td)
-msgid "node_override_vif_hyperv ="
+#: ./doc/common/tables/glance-registry.xml:63(td)
+msgid "(StrOpt) The protocol to use for communication with the registry server. Either http or https."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:43(td) ./doc/common/tables/neutron-bigswitch.xml:43(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to hyperv"
+#: ./doc/common/tables/glance-registry.xml:66(td)
+msgid "registry_client_timeout = 600"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:46(td) ./doc/common/tables/neutron-bigswitch.xml:46(td)
-msgid "node_override_vif_ivs ="
+#: ./doc/common/tables/glance-registry.xml:67(td)
+msgid "(IntOpt) The period of time, in seconds, that the API server will wait for a registry request to complete. A value of 0 implies no timeout."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:47(td) ./doc/common/tables/neutron-bigswitch.xml:47(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to ivs"
+#: ./doc/common/tables/glance-registry.xml:70(td)
+msgid "registry_host = 0.0.0.0"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:50(td) ./doc/common/tables/neutron-bigswitch.xml:50(td)
-msgid "node_override_vif_midonet ="
+#: ./doc/common/tables/glance-registry.xml:71(td)
+msgid "(StrOpt) Address to find the registry server."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:51(td) ./doc/common/tables/neutron-bigswitch.xml:51(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to midonet"
+#: ./doc/common/tables/glance-registry.xml:74(td)
+msgid "registry_port = 9191"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:54(td) ./doc/common/tables/neutron-bigswitch.xml:54(td)
-msgid "node_override_vif_mlnx_direct ="
+#: ./doc/common/tables/glance-registry.xml:75(td)
+msgid "(IntOpt) Port the registry server is listening on."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:55(td) ./doc/common/tables/neutron-bigswitch.xml:55(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to mlnx_direct"
+#: ./doc/common/tables/neutron-embrane.xml:8(caption)
+msgid "Description of configuration options for embrane"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:58(td) ./doc/common/tables/neutron-bigswitch.xml:58(td)
-msgid "node_override_vif_other ="
+#: ./doc/common/tables/neutron-embrane.xml:19(th) ./doc/common/tables/neutron-common.xml:216(th)
+msgid "[heleos]"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:59(td) ./doc/common/tables/neutron-bigswitch.xml:59(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to other"
+#: ./doc/common/tables/neutron-embrane.xml:22(td)
+msgid "admin_username = admin"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:62(td) ./doc/common/tables/neutron-bigswitch.xml:62(td)
-msgid "node_override_vif_ovs ="
+#: ./doc/common/tables/neutron-embrane.xml:23(td) ./doc/common/tables/neutron-embrane_lb.xml:27(td)
+msgid "(StrOpt) ESM admin username."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:63(td) ./doc/common/tables/neutron-bigswitch.xml:63(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to ovs"
+#: ./doc/common/tables/neutron-embrane.xml:26(td)
+msgid "async_requests = True"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:66(td) ./doc/common/tables/neutron-bigswitch.xml:66(td)
-msgid "node_override_vif_unbound ="
+#: ./doc/common/tables/neutron-embrane.xml:27(td) ./doc/common/tables/neutron-embrane_lb.xml:31(td)
+msgid "(BoolOpt) Define if the requests have run asynchronously or not"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:67(td) ./doc/common/tables/neutron-bigswitch.xml:67(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to unbound"
+#: ./doc/common/tables/neutron-embrane.xml:30(td) ./doc/common/tables/neutron-embrane_lb.xml:34(td)
+msgid "dummy_utif_id = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:70(td) ./doc/common/tables/neutron-bigswitch.xml:70(td)
-msgid "vif_type = ovs"
+#: ./doc/common/tables/neutron-embrane.xml:31(td)
+msgid "(StrOpt) Dummy user traffic Security Zone id"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:71(td) ./doc/common/tables/neutron-bigswitch.xml:71(td)
-msgid "(StrOpt) Virtual interface type to configure on Nova compute nodes"
+#: ./doc/common/tables/neutron-embrane.xml:34(td) ./doc/common/tables/neutron-embrane_lb.xml:38(td)
+msgid "esm_mgmt = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:74(td) ./doc/common/tables/neutron-bigswitch.xml:74(td)
-msgid "vif_types = unbound, binding_failed, ovs, ivs, bridge, 802.1qbg, 802.1qbh, hyperv, midonet, mlnx_direct, hostdev, other"
+#: ./doc/common/tables/neutron-embrane.xml:35(td) ./doc/common/tables/neutron-embrane_lb.xml:39(td)
+msgid "(StrOpt) ESM management root address"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:75(td) ./doc/common/tables/neutron-bigswitch.xml:75(td)
-msgid "(ListOpt) List of allowed vif_type values."
+#: ./doc/common/tables/neutron-embrane.xml:38(td) ./doc/common/tables/neutron-embrane_lb.xml:42(td)
+msgid "inband_id = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:78(th) ./doc/common/tables/neutron-bigswitch.xml:78(th) ./doc/common/tables/neutron-nuage.xml:19(th)
-msgid "[RESTPROXY]"
+#: ./doc/common/tables/neutron-embrane.xml:39(td)
+msgid "(StrOpt) In band Security Zone id"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:81(td) ./doc/common/tables/neutron-bigswitch.xml:81(td)
-msgid "add_meta_server_route = True"
+#: ./doc/common/tables/neutron-embrane.xml:42(td) ./doc/common/tables/neutron-embrane_lb.xml:54(td)
+msgid "mgmt_id = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:82(td) ./doc/common/tables/neutron-bigswitch.xml:82(td)
-msgid "(BoolOpt) Flag to decide if a route to the metadata server should be injected into the VM"
+#: ./doc/common/tables/neutron-embrane.xml:43(td)
+msgid "(StrOpt) Management Security Zone id"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:85(td) ./doc/common/tables/neutron-bigswitch.xml:85(td)
-msgid "auto_sync_on_failure = True"
+#: ./doc/common/tables/neutron-embrane.xml:46(td) ./doc/common/tables/neutron-embrane_lb.xml:58(td)
+msgid "oob_id = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:86(td) ./doc/common/tables/neutron-bigswitch.xml:86(td)
-msgid "(BoolOpt) If neutron fails to create a resource because the backend controller doesn't know of a dependency, the plugin automatically triggers a full data synchronization to the controller."
+#: ./doc/common/tables/neutron-embrane.xml:47(td)
+msgid "(StrOpt) Out of band Security Zone id"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:89(td) ./doc/common/tables/neutron-bigswitch.xml:89(td)
-msgid "cache_connections = True"
+#: ./doc/common/tables/neutron-embrane.xml:50(td)
+msgid "resource_pool_id = default"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:90(td) ./doc/common/tables/neutron-bigswitch.xml:90(td)
-msgid "(BoolOpt) Re-use HTTP/HTTPS connections to the controller."
+#: ./doc/common/tables/neutron-embrane.xml:51(td) ./doc/common/tables/neutron-embrane_lb.xml:63(td)
+msgid "(StrOpt) Shared resource pool id"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:93(td) ./doc/common/tables/neutron-bigswitch.xml:93(td)
-msgid "consistency_interval = 60"
+#: ./doc/common/tables/neutron-embrane.xml:54(td)
+msgid "router_image = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:94(td) ./doc/common/tables/neutron-bigswitch.xml:94(td)
-msgid "(IntOpt) Time between verifications that the backend controller database is consistent with Neutron"
+#: ./doc/common/tables/neutron-embrane.xml:55(td)
+msgid "(StrOpt) Router image id (Embrane FW/VPN)"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:97(td) ./doc/common/tables/neutron-bigswitch.xml:97(td)
-msgid "neutron_id = neutron-oslo"
+#: ./doc/common/tables/heat-quota.xml:22(td)
+msgid "max_events_per_stack = 1000"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:98(td) ./doc/common/tables/neutron-bigswitch.xml:98(td)
-msgid "(StrOpt) User defined identifier for this Neutron deployment"
+#: ./doc/common/tables/heat-quota.xml:23(td)
+msgid "(IntOpt) Maximum events that will be available per stack. Older events will be deleted when this is reached. Set to 0 for unlimited events per stack."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:101(td) ./doc/common/tables/neutron-bigswitch.xml:101(td)
-msgid "no_ssl_validation = False"
+#: ./doc/common/tables/heat-quota.xml:26(td)
+msgid "max_nested_stack_depth = 3"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:102(td) ./doc/common/tables/neutron-bigswitch.xml:102(td)
-msgid "(BoolOpt) Disables SSL certificate validation for controllers"
+#: ./doc/common/tables/heat-quota.xml:27(td)
+msgid "(IntOpt) Maximum depth allowed when using nested stacks."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:105(td) ./doc/common/tables/neutron-bigswitch.xml:105(td)
-msgid "server_auth = None"
+#: ./doc/common/tables/heat-quota.xml:30(td)
+msgid "max_resources_per_stack = 1000"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:106(td) ./doc/common/tables/neutron-bigswitch.xml:106(td)
-msgid "(StrOpt) The username and password for authenticating against the Big Switch or Floodlight controller."
+#: ./doc/common/tables/heat-quota.xml:31(td)
+msgid "(IntOpt) Maximum resources allowed per top-level stack."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:109(td) ./doc/common/tables/neutron-bigswitch.xml:109(td)
-msgid "server_ssl = True"
+#: ./doc/common/tables/heat-quota.xml:34(td)
+msgid "max_stacks_per_tenant = 100"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:110(td) ./doc/common/tables/neutron-bigswitch.xml:110(td)
-msgid "(BoolOpt) If True, Use SSL when connecting to the Big Switch or Floodlight controller."
+#: ./doc/common/tables/heat-quota.xml:35(td)
+msgid "(IntOpt) Maximum number of stacks any one tenant may have active at one time."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:113(td) ./doc/common/tables/neutron-bigswitch.xml:113(td)
-msgid "server_timeout = 10"
+#: ./doc/common/tables/heat-quota.xml:38(td)
+msgid "max_template_size = 524288"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:114(td) ./doc/common/tables/neutron-bigswitch.xml:114(td)
-msgid "(IntOpt) Maximum number of seconds to wait for proxy request to connect and complete."
+#: ./doc/common/tables/heat-quota.xml:39(td)
+msgid "(IntOpt) Maximum raw byte size of any template."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:117(td) ./doc/common/tables/neutron-bigswitch.xml:117(td)
-msgid "servers = localhost:8800"
+#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml:7(literal) ./doc/common/tables/swift-container-server-filter-healthcheck.xml:7(literal) ./doc/common/tables/swift-object-server-filter-healthcheck.xml:7(literal) ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml:7(literal)
+msgid "[filter:healthcheck]"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:118(td) ./doc/common/tables/neutron-bigswitch.xml:118(td)
-msgid "(ListOpt) A comma separated list of Big Switch or Floodlight servers and port numbers. The plugin proxies the requests to the Big Switch/Floodlight server, which performs the networking configuration. Only oneserver is needed per deployment, but you may wish todeploy multiple servers to support failover."
+#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml:7(literal) ./doc/common/tables/swift-account-server-filter-recon.xml:7(literal) ./doc/common/tables/swift-account-server-account-replicator.xml:7(literal) ./doc/common/tables/swift-account-server-app-account-server.xml:7(literal) ./doc/common/tables/swift-account-server-pipeline-main.xml:7(literal) ./doc/common/tables/swift-account-server-account-auditor.xml:7(literal) ./doc/common/tables/swift-account-server-DEFAULT.xml:7(literal) ./doc/common/tables/swift-account-server-account-reaper.xml:7(literal)
+msgid "account-server.conf-sample"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:121(td) ./doc/common/tables/neutron-bigswitch.xml:121(td)
-msgid "ssl_cert_directory = /etc/neutron/plugins/bigswitch/ssl"
+#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml:18(td) ./doc/common/tables/swift-container-server-filter-healthcheck.xml:18(td) ./doc/common/tables/swift-object-server-filter-healthcheck.xml:18(td) ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml:18(td)
+msgid "use = egg:swift#healthcheck"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:122(td) ./doc/common/tables/neutron-bigswitch.xml:122(td)
-msgid "(StrOpt) Directory containing ca_certs and host_certs certificate directories."
+#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml:21(td) ./doc/common/tables/swift-container-server-filter-healthcheck.xml:21(td) ./doc/common/tables/swift-object-server-filter-healthcheck.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml:21(td)
+msgid "disable_path ="
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:125(td) ./doc/common/tables/neutron-bigswitch.xml:125(td)
-msgid "ssl_sticky = True"
+#: ./doc/common/tables/nova-common.xml:22(td)
+msgid "bindir = /usr/local/bin"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:126(td) ./doc/common/tables/neutron-bigswitch.xml:126(td)
-msgid "(BoolOpt) Trust and store the first certificate received for each controller address and use it to validate future connections to that address."
+#: ./doc/common/tables/nova-common.xml:23(td)
+msgid "(StrOpt) Directory where nova binaries are installed"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:129(td) ./doc/common/tables/neutron-bigswitch.xml:129(td)
-msgid "sync_data = False"
+#: ./doc/common/tables/nova-common.xml:26(td)
+msgid "compute_topic = compute"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:130(td) ./doc/common/tables/neutron-bigswitch.xml:130(td)
-msgid "(BoolOpt) Sync data on connect"
+#: ./doc/common/tables/nova-common.xml:27(td)
+msgid "(StrOpt) The topic compute nodes listen on"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:133(td) ./doc/common/tables/neutron-bigswitch.xml:133(td)
-msgid "thread_pool_size = 4"
+#: ./doc/common/tables/nova-common.xml:30(td)
+msgid "console_topic = console"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:134(td) ./doc/common/tables/neutron-bigswitch.xml:134(td)
-msgid "(IntOpt) Maximum number of threads to spawn to handle large volumes of port creations."
+#: ./doc/common/tables/nova-common.xml:31(td)
+msgid "(StrOpt) The topic console proxy nodes listen on"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:137(th) ./doc/common/tables/neutron-bigswitch.xml:137(th)
-msgid "[RESTPROXYAGENT]"
+#: ./doc/common/tables/nova-common.xml:34(td)
+msgid "consoleauth_topic = consoleauth"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:140(td) ./doc/common/tables/neutron-openvswitch_agent.xml:83(td) ./doc/common/tables/neutron-bigswitch.xml:140(td) ./doc/common/tables/neutron-cisco.xml:73(td) ./doc/common/tables/nova-vmware.xml:46(td) ./doc/common/tables/neutron-nvsd.xml:22(td)
-msgid "integration_bridge = br-int"
+#: ./doc/common/tables/nova-common.xml:35(td)
+msgid "(StrOpt) The topic console auth proxy nodes listen on"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:141(td) ./doc/common/tables/neutron-bigswitch.xml:141(td)
-msgid "(StrOpt) Name of integration bridge on compute nodes used for security group insertion."
+#: ./doc/common/tables/nova-common.xml:39(td) ./doc/common/tables/cinder-common.xml:43(td) ./doc/common/tables/heat-debug.xml:31(td) ./doc/common/tables/glance-common.xml:47(td) ./doc/common/tables/neutron-common.xml:123(td) ./doc/common/tables/trove-debug.xml:35(td) ./doc/common/tables/keystone-debug.xml:31(td)
+msgid "(BoolOpt) Whether to disable inter-process locks"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:144(td) ./doc/common/tables/neutron-bigswitch.xml:144(td)
-msgid "polling_interval = 5"
+#: ./doc/common/tables/nova-common.xml:43(td)
+msgid "(StrOpt) Name of this node. This can be an opaque identifier. It is not necessarily a hostname, FQDN, or IP address. However, the node name must be valid within an AMQP key, and if using ZeroMQ, a valid hostname, FQDN, or IP address"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:145(td) ./doc/common/tables/neutron-bigswitch.xml:145(td)
-msgid "(IntOpt) Seconds between agent checks for port changes"
+#: ./doc/common/tables/nova-common.xml:54(td) ./doc/common/tables/cinder-common.xml:118(td)
+msgid "my_ip = 10.0.0.1"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:148(td) ./doc/common/tables/neutron-bigswitch.xml:148(td)
-msgid "virtual_switch_type = ovs"
+#: ./doc/common/tables/nova-common.xml:55(td)
+msgid "(StrOpt) IP address of this host"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:149(td) ./doc/common/tables/neutron-bigswitch.xml:149(td)
-msgid "(StrOpt) Virtual switch type."
+#: ./doc/common/tables/nova-common.xml:59(td) ./doc/common/tables/keystone-amqp.xml:39(td) ./doc/common/tables/glance-amqp.xml:31(td) ./doc/common/tables/cinder-rpc.xml:75(td)
+msgid "(MultiStrOpt) Driver or drivers to handle sending notifications."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:152(th) ./doc/common/tables/neutron-bigswitch.xml:152(th)
-msgid "[ROUTER]"
+#: ./doc/common/tables/nova-common.xml:63(td) ./doc/common/tables/keystone-amqp.xml:43(td) ./doc/common/tables/glance-amqp.xml:35(td) ./doc/common/tables/cinder-rpc.xml:79(td)
+msgid "(ListOpt) AMQP topic used for OpenStack notifications."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:155(td) ./doc/common/tables/neutron-bigswitch.xml:155(td)
-msgid "max_router_rules = 200"
+#: ./doc/common/tables/nova-common.xml:66(td)
+msgid "notify_api_faults = False"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:156(td) ./doc/common/tables/neutron-bigswitch.xml:156(td)
-msgid "(IntOpt) Maximum number of router rules"
+#: ./doc/common/tables/nova-common.xml:67(td)
+msgid "(BoolOpt) If set, send api.fault notifications on caught exceptions in the API service."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:159(td) ./doc/common/tables/neutron-bigswitch.xml:159(td)
-msgid "tenant_default_router_rule = ['*:any:any:permit']"
+#: ./doc/common/tables/nova-common.xml:70(td)
+msgid "notify_on_state_change = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml:160(td) ./doc/common/tables/neutron-bigswitch.xml:160(td)
-msgid "(MultiStrOpt) The default router rules installed in new tenant routers. Repeat the config option for each rule. Format is &lt;tenant&gt;:&lt;source&gt;:&lt;destination&gt;:&lt;action&gt; Use an * to specify default for all tenants."
+#: ./doc/common/tables/nova-common.xml:71(td)
+msgid "(StrOpt) If set, send compute.instance.update notifications on instance state changes. Valid values are None for no notifications, \"vm_state\" for notifications on VM state changes, or \"vm_and_task_state\" for notifications on VM and task state changes."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_gre.xml:8(caption)
-msgid "Description of configuration options for ml2_gre"
+#: ./doc/common/tables/nova-common.xml:78(td)
+msgid "pybasedir = /usr/lib/python/site-packages"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_gre.xml:19(th)
-msgid "[ml2_type_gre]"
+#: ./doc/common/tables/nova-common.xml:79(td)
+msgid "(StrOpt) Directory where the nova python module is installed"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_gre.xml:22(td) ./doc/common/tables/neutron-openvswitch_agent.xml:107(td)
-msgid "tunnel_id_ranges ="
+#: ./doc/common/tables/nova-common.xml:82(td) ./doc/common/tables/cinder-common.xml:146(td) ./doc/common/tables/trove-rpc.xml:46(td)
+msgid "report_interval = 10"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_gre.xml:23(td)
-msgid "(ListOpt) Comma-separated list of &lt;tun_min&gt;:&lt;tun_max&gt; tuples enumerating ranges of GRE tunnel IDs that are available for tenant network allocation"
+#: ./doc/common/tables/nova-common.xml:83(td)
+msgid "(IntOpt) Seconds between nodes reporting state to datastore"
+msgstr ""
+
+#: ./doc/common/tables/nova-common.xml:86(td)
+msgid "rootwrap_config = /etc/nova/rootwrap.conf"
+msgstr ""
+
+#: ./doc/common/tables/nova-common.xml:87(td) ./doc/common/tables/cinder-common.xml:155(td)
+msgid "(StrOpt) Path to the rootwrap configuration file to use for running commands as root"
+msgstr ""
+
+#: ./doc/common/tables/nova-common.xml:90(td) ./doc/common/tables/cinder-common.xml:162(td)
+msgid "service_down_time = 60"
+msgstr ""
+
+#: ./doc/common/tables/nova-common.xml:91(td)
+msgid "(IntOpt) Maximum time since last check-in for up service"
+msgstr ""
+
+#: ./doc/common/tables/nova-common.xml:94(td)
+msgid "state_path = $pybasedir"
+msgstr ""
+
+#: ./doc/common/tables/nova-common.xml:95(td)
+msgid "(StrOpt) Top-level directory for maintaining nova's state"
+msgstr ""
+
+#: ./doc/common/tables/nova-common.xml:98(td)
+msgid "tempdir = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-common.xml:99(td)
+msgid "(StrOpt) Explicitly specify the temporary working directory"
+msgstr ""
+
+#: ./doc/common/tables/nova-common.xml:102(td) ./doc/common/tables/keystone-amqp.xml:66(td) ./doc/common/tables/glance-amqp.xml:54(td) ./doc/common/tables/cinder-rpc.xml:230(td)
+msgid "transport_url = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-common.xml:103(td) ./doc/common/tables/keystone-amqp.xml:67(td) ./doc/common/tables/glance-amqp.xml:55(td) ./doc/common/tables/cinder-rpc.xml:231(td)
+msgid "(StrOpt) A URL representing the messaging driver to use and its full configuration. If not set, we fall back to the rpc_backend option and driver specific configuration."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:7(literal) ./doc/common/tables/swift-object-expirer-app-proxy-server.xml:7(literal)
+msgid "[app:proxy-server]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:18(td) ./doc/common/tables/swift-object-expirer-app-proxy-server.xml:18(td)
+msgid "use = egg:swift#proxy"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:21(td)
+msgid "set log_name = proxy-server"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:33(td)
+msgid "log_handoffs = true"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:36(td)
+msgid "recheck_account_existence = 60"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:36(td)
+msgid "Cache timeout in seconds to send memcached for account existence"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:39(td)
+msgid "recheck_container_existence = 60"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:39(td)
+msgid "Cache timeout in seconds to send memcached for container existence"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:42(td)
+msgid "object_chunk_size = 8192"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:42(td)
+msgid "Chunk size to read from object servers"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:45(td)
+msgid "client_chunk_size = 8192"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:45(td)
+msgid "Chunk size to read from clients"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:48(td) ./doc/common/tables/swift-account-server-account-replicator.xml:51(td) ./doc/common/tables/swift-container-server-container-replicator.xml:45(td) ./doc/common/tables/swift-account-server-account-reaper.xml:36(td)
+msgid "node_timeout = 10"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:48(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:112(td) ./doc/common/tables/swift-account-server-account-replicator.xml:51(td) ./doc/common/tables/swift-container-server-container-updater.xml:36(td) ./doc/common/tables/swift-object-server-object-replicator.xml:57(td) ./doc/common/tables/swift-container-server-app-container-server.xml:36(td) ./doc/common/tables/swift-container-server-container-replicator.xml:45(td) ./doc/common/tables/swift-object-server-object-updater.xml:36(td) ./doc/common/tables/swift-account-server-account-reaper.xml:36(td)
+msgid "Request timeout to external services"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:51(td)
+msgid "recoverable_node_timeout = node_timeout"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:51(td)
+msgid "Request timeout to external services for requests that, on failure, can be recovered from. For example, object GET. from a client external services"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:54(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:109(td) ./doc/common/tables/swift-account-server-account-replicator.xml:54(td) ./doc/common/tables/swift-container-server-container-updater.xml:39(td) ./doc/common/tables/swift-container-server-app-container-server.xml:39(td) ./doc/common/tables/swift-container-server-container-replicator.xml:48(td) ./doc/common/tables/swift-account-server-account-reaper.xml:39(td)
+msgid "conn_timeout = 0.5"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:54(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:109(td) ./doc/common/tables/swift-account-server-account-replicator.xml:54(td) ./doc/common/tables/swift-container-server-container-updater.xml:39(td) ./doc/common/tables/swift-container-server-app-container-server.xml:39(td) ./doc/common/tables/swift-container-server-container-replicator.xml:48(td) ./doc/common/tables/swift-account-server-account-reaper.xml:39(td)
+msgid "Connection timeout to external services"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:57(td)
+msgid "post_quorum_timeout = 0.5"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:60(td) ./doc/common/tables/swift-account-server-account-replicator.xml:45(td)
+msgid "error_suppression_interval = 60"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:60(td) ./doc/common/tables/swift-account-server-account-replicator.xml:45(td)
+msgid "Time in seconds that must elapse since the last error for a node to be considered no longer error limited"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:63(td) ./doc/common/tables/swift-account-server-account-replicator.xml:48(td)
+msgid "error_suppression_limit = 10"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:63(td) ./doc/common/tables/swift-account-server-account-replicator.xml:48(td)
+msgid "Error count to consider a node error limited"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:66(td)
+msgid "allow_account_management = false"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:66(td)
+msgid "Whether account PUTs and DELETEs are even callable"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:69(td)
+msgid "object_post_as_copy = true"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:69(td)
+msgid "Set object_post_as_copy = false to turn on fast posts where only the metadata changes are stored anew and the original data file is kept in place. This makes for quicker posts; but since the container metadata isn't updated in this mode, features like container sync won't be able to sync posts."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:72(td)
+msgid "account_autocreate = false"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:72(td)
+msgid "If set to 'true' authorized accounts that do not yet exist within the Swift cluster will be automatically created."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:75(td)
+msgid "max_containers_per_account = 0"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:75(td)
+msgid "If set to a positive value, trying to create a container when the account already has at least this maximum containers will result in a 403 Forbidden. Note: This is a soft limit, meaning a user might exceed the cap for recheck_account_existence before the 403s kick in."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:78(td)
+msgid "max_containers_whitelist ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:78(td)
+msgid "is a comma separated list of account names that ignore the max_containers_per_account cap."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:81(td)
+msgid "deny_host_headers ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:84(td) ./doc/common/tables/swift-object-expirer-object-expirer.xml:21(td) ./doc/common/tables/swift-object-server-app-object-server.xml:54(td) ./doc/common/tables/swift-account-server-app-account-server.xml:36(td) ./doc/common/tables/swift-container-server-app-container-server.xml:45(td)
+msgid "auto_create_account_prefix = ."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:84(td) ./doc/common/tables/swift-object-expirer-object-expirer.xml:21(td) ./doc/common/tables/swift-object-server-app-object-server.xml:54(td) ./doc/common/tables/swift-account-server-app-account-server.xml:36(td) ./doc/common/tables/swift-container-server-app-container-server.xml:45(td)
+msgid "Prefix to use when automatically creating accounts"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:87(td)
+msgid "put_queue_depth = 10"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:90(td)
+msgid "sorting_method = shuffle"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:93(td)
+msgid "timing_expiry = 300"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:96(td)
+msgid "max_large_object_get_time = 86400"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:99(td)
+msgid "request_node_count = 2 * replicas"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:99(td)
+msgid "* replicas Set to the number of nodes to contact for a normal request. You can use '* replicas' at the end to have it use the number given times the number of replicas for the ring being used for the request. conf file for values will only be shown to the list of swift_owners. The exact default definition of a swift_owner is headers&gt; up to the auth system in use, but usually indicates administrative responsibilities. paste.deploy to use for auth. To use tempauth set to: `egg:swift#tempauth` each request"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:102(td)
+msgid "read_affinity = r1z1=100, r1z2=200, r2=300"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:105(td)
+msgid "read_affinity ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:108(td)
+msgid "write_affinity = r1, r2"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:111(td)
+msgid "write_affinity ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:114(td)
+msgid "write_affinity_node_count = 2 * replicas"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:117(td)
+msgid "swift_owner_headers = x-container-read, x-container-write, x-container-sync-key, x-container-sync-to, x-account-meta-temp-url-key, x-account-meta-temp-url-key-2, x-account-access-control"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:117(td)
+msgid "the sample These are the headers whose conf file for values will only be shown to the list of swift_owners. The exact default definition of a swift_owner is headers&gt; up to the auth system in use, but usually indicates administrative responsibilities. paste.deploy to use for auth. To use tempauth set to: `egg:swift#tempauth` each request"
 msgstr ""
 
 #: ./doc/common/tables/nova-volumes.xml:8(caption)
@@ -19571,10 +24519,6 @@ msgstr ""
 msgid "(IntOpt) Number of cinderclient retries on failed http calls"
 msgstr ""
 
-#: ./doc/common/tables/nova-volumes.xml:46(td) ./doc/common/tables/cinder-compute.xml:46(td) ./doc/common/tables/glance-common.xml:82(td) ./doc/common/tables/ceilometer-auth.xml:156(td)
-msgid "os_region_name = None"
-msgstr ""
-
 #: ./doc/common/tables/nova-volumes.xml:47(td)
 msgid "(StrOpt) Region name of this node"
 msgstr ""
@@ -19595,7 +24539,7 @@ msgstr ""
 msgid "(IntOpt) Interval in seconds for gathering volume usages"
 msgstr ""
 
-#: ./doc/common/tables/nova-volumes.xml:58(th) ./doc/common/tables/nova-tilera.xml:19(th) ./doc/common/tables/nova-baremetal.xml:19(th)
+#: ./doc/common/tables/nova-volumes.xml:58(th) ./doc/common/tables/nova-baremetal.xml:19(th) ./doc/common/tables/nova-tilera.xml:19(th)
 msgid "[baremetal]"
 msgstr ""
 
@@ -19643,10 +24587,6 @@ msgstr ""
 msgid "(IntOpt) Interval between volume attachment attempts, in seconds"
 msgstr ""
 
-#: ./doc/common/tables/nova-volumes.xml:84(th) ./doc/common/tables/nova-hypervisor.xml:54(th) ./doc/common/tables/nova-livemigration.xml:26(th) ./doc/common/tables/nova-libvirt.xml:30(th) ./doc/common/tables/nova-xen.xml:58(th)
-msgid "[libvirt]"
-msgstr ""
-
 #: ./doc/common/tables/nova-volumes.xml:87(td) ./doc/common/tables/cinder-storage_glusterfs.xml:22(td)
 msgid "glusterfs_mount_point_base = $state_path/mnt"
 msgstr ""
@@ -19703,18 +24643,10 @@ msgstr ""
 msgid "(ListOpt) Protocols listed here will be accessed directly from QEMU. Currently supported protocols: [gluster]"
 msgstr ""
 
-#: ./doc/common/tables/nova-volumes.xml:115(td) ./doc/common/tables/cinder-storage_ceph.xml:38(td)
-msgid "rbd_secret_uuid = None"
-msgstr ""
-
 #: ./doc/common/tables/nova-volumes.xml:116(td)
 msgid "(StrOpt) The libvirt UUID of the secret for the rbd_uservolumes"
 msgstr ""
 
-#: ./doc/common/tables/nova-volumes.xml:119(td) ./doc/common/tables/cinder-storage_ceph.xml:42(td)
-msgid "rbd_user = None"
-msgstr ""
-
 #: ./doc/common/tables/nova-volumes.xml:120(td)
 msgid "(StrOpt) The RADOS client name for accessing rbd volumes"
 msgstr ""
@@ -19735,10 +24667,6 @@ msgstr ""
 msgid "(StrOpt) Base dir where Scality SOFS shall be mounted"
 msgstr ""
 
-#: ./doc/common/tables/nova-volumes.xml:131(th) ./doc/common/tables/nova-xen.xml:65(th) ./doc/common/tables/nova-baremetal.xml:130(th)
-msgid "[xenserver]"
-msgstr ""
-
 #: ./doc/common/tables/nova-volumes.xml:134(td)
 msgid "block_device_creation_timeout = 10"
 msgstr ""
@@ -19747,1036 +24675,328 @@ msgstr ""
 msgid "(IntOpt) Time to wait for a block device to be created"
 msgstr ""
 
-#: ./doc/common/tables/glance-gridfs.xml:8(caption)
-msgid "Description of configuration options for gridfs"
+#: ./doc/common/tables/neutron-redis.xml:23(td)
+msgid "(StrOpt) The hostname Neutron is running on"
 msgstr ""
 
-#: ./doc/common/tables/glance-gridfs.xml:22(td)
-msgid "mongodb_store_db = None"
+#: ./doc/common/tables/trove-db_mysql.xml:8(caption)
+msgid "Description of configuration options for db_mysql"
 msgstr ""
 
-#: ./doc/common/tables/glance-gridfs.xml:23(td)
-msgid "(StrOpt) Database to use."
+#: ./doc/common/tables/trove-db_mysql.xml:19(th)
+msgid "[mysql]"
 msgstr ""
 
-#: ./doc/common/tables/glance-gridfs.xml:26(td)
-msgid "mongodb_store_uri = None"
+#: ./doc/common/tables/trove-db_mysql.xml:42(td)
+msgid "usage_timeout = 400"
 msgstr ""
 
-#: ./doc/common/tables/glance-gridfs.xml:27(td)
-msgid "(StrOpt) Hostname or IP address of the instance to connect to, or a mongodb URI, or a list of hostnames / mongodb URIs. If host is an IPv6 literal it must be enclosed in '[' and ']' characters following the RFC2732 URL syntax (e.g. '[::1]' for localhost)."
+#: ./doc/common/tables/heat-zeromq.xml:27(td) ./doc/common/tables/neutron-zeromq.xml:27(td) ./doc/common/tables/ceilometer-rpc.xml:55(td) ./doc/common/tables/trove-zeromq.xml:27(td)
+msgid "(IntOpt) Number of ZeroMQ contexts, defaults to 1"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml:8(caption)
-msgid "Description of configuration options for ml2_arista"
+#: ./doc/common/tables/heat-zeromq.xml:35(td) ./doc/common/tables/neutron-zeromq.xml:35(td) ./doc/common/tables/ceilometer-rpc.xml:63(td) ./doc/common/tables/trove-zeromq.xml:35(td)
+msgid "(StrOpt) Directory for holding IPC sockets"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml:19(th)
-msgid "[ml2_arista]"
+#: ./doc/common/tables/heat-zeromq.xml:38(td)
+msgid "rpc_zmq_matchmaker = heat.openstack.common.rpc.matchmaker.MatchMakerLocalhost"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml:22(td)
-msgid "eapi_host ="
+#: ./doc/common/tables/heat-zeromq.xml:39(td) ./doc/common/tables/neutron-zeromq.xml:39(td) ./doc/common/tables/ceilometer-rpc.xml:67(td) ./doc/common/tables/trove-zeromq.xml:39(td)
+msgid "(StrOpt) MatchMaker driver"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml:23(td)
-msgid "(StrOpt) Arista EOS IP address. This is required field.If not set, all communications to Arista EOSwill fail"
+#: ./doc/common/tables/heat-zeromq.xml:43(td) ./doc/common/tables/neutron-zeromq.xml:43(td) ./doc/common/tables/ceilometer-rpc.xml:71(td) ./doc/common/tables/trove-zeromq.xml:43(td)
+msgid "(IntOpt) ZeroMQ receiver listening port"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml:26(td)
-msgid "eapi_password ="
+#: ./doc/common/tables/heat-amqp.xml:30(td)
+msgid "control_exchange = heat"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml:27(td)
-msgid "(StrOpt) Password for Arista EOS. This is required field.if not set, all communications to Arista EOSwill fail"
+#: ./doc/common/tables/heat-amqp.xml:46(td)
+msgid "list_notifier_drivers = ['heat.openstack.common.notifier.no_op_notifier']"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml:30(td)
-msgid "eapi_username ="
+#: ./doc/common/tables/heat-amqp.xml:47(td)
+msgid "(MultiStrOpt) List of drivers to send notifications"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml:31(td)
-msgid "(StrOpt) Username for Arista EOS. This is required field.if not set, all communications to Arista EOSwill fail"
+#: ./doc/common/tables/heat-amqp.xml:55(td) ./doc/common/tables/ceilometer-amqp.xml:35(td)
+msgid "(ListOpt) AMQP topic used for OpenStack notifications"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml:34(td)
-msgid "region_name = RegionOne"
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml:8(caption)
+msgid "Description of configuration options for linuxbridge_agent"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml:35(td)
-msgid "(StrOpt) Defines Region Name that is assigned to this OpenStackController. This is useful when multipleOpenStack/Neutron controllers are managing the sameArista HW clusters. Note that this name must match withthe region name registered (or known) to keystoneservice. Authentication with Keysotne is performed byEOS. This is optional. If not set, a value of\"RegionOne\" is assumed"
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml:19(th)
+msgid "[LINUX_BRIDGE]"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml:38(td)
-msgid "sync_interval = 180"
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml:22(td) ./doc/common/tables/neutron-mlnx.xml:30(td)
+msgid "physical_interface_mappings ="
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml:39(td)
-msgid "(IntOpt) Sync interval in seconds between Neutron plugin andEOS. This interval defines how often thesynchronization is performed. This is an optionalfield. If not set, a value of 180 seconds is assumed"
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml:23(td) ./doc/common/tables/neutron-mlnx.xml:31(td)
+msgid "(ListOpt) List of &lt;physical_network&gt;:&lt;physical_interface&gt;"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml:42(td)
-msgid "use_fqdn = True"
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml:26(th)
+msgid "[VLANS]"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml:43(td)
-msgid "(BoolOpt) Defines if hostnames are sent to Arista EOS as FQDNs(\"node1.domain.com\") or as short names (\"node1\").This is optional. If not set, a value of \"True\"is assumed."
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml:34(td) ./doc/common/tables/neutron-mlnx.xml:54(td)
+msgid "(StrOpt) Network type for tenant networks (local, vlan, or none)"
 msgstr ""
 
-#: ./doc/common/tables/glance-filesystem.xml:8(caption)
-msgid "Description of configuration options for filesystem"
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml:37(th)
+msgid "[VXLAN]"
 msgstr ""
 
-#: ./doc/common/tables/glance-filesystem.xml:22(td)
-msgid "filesystem_store_datadir = None"
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml:40(td)
+msgid "enable_vxlan = False"
 msgstr ""
 
-#: ./doc/common/tables/glance-filesystem.xml:23(td)
-msgid "(StrOpt) Directory to which the Filesystem backend store writes images."
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml:41(td)
+msgid "(BoolOpt) Enable VXLAN on the agent. Can be enabled when agent is managed by ml2 plugin using linuxbridge mechanism driver"
 msgstr ""
 
-#: ./doc/common/tables/glance-filesystem.xml:26(td)
-msgid "filesystem_store_datadirs = None"
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml:45(td)
+msgid "(BoolOpt) Extension to use alongside ml2 plugin's l2population mechanism driver. It enables the plugin to populate VXLAN forwarding table."
 msgstr ""
 
-#: ./doc/common/tables/glance-filesystem.xml:27(td)
-msgid "(MultiStrOpt) List of directories and its priorities to which the Filesystem backend store writes images."
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml:49(td)
+msgid "(StrOpt) Local IP address of the VXLAN endpoints."
 msgstr ""
 
-#: ./doc/common/tables/glance-filesystem.xml:30(td)
-msgid "filesystem_store_metadata_file = None"
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml:52(td)
+msgid "tos = None"
 msgstr ""
 
-#: ./doc/common/tables/glance-filesystem.xml:31(td)
-msgid "(StrOpt) The path to a file which contains the metadata to be returned with any location associated with this store. The file must contain a valid JSON dict."
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml:53(td)
+msgid "(IntOpt) TOS for vxlan interface protocol packets."
 msgstr ""
 
-#: ./doc/common/tables/heat-redis.xml:8(caption) ./doc/common/tables/trove-redis.xml:8(caption) ./doc/common/tables/ceilometer-redis.xml:8(caption) ./doc/common/tables/glance-redis.xml:8(caption) ./doc/common/tables/neutron-redis.xml:8(caption) ./doc/common/tables/keystone-redis.xml:8(caption) ./doc/common/tables/nova-redis.xml:8(caption)
-msgid "Description of configuration options for redis"
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml:56(td)
+msgid "ttl = None"
 msgstr ""
 
-#: ./doc/common/tables/heat-redis.xml:22(td) ./doc/common/tables/nova-common.xml:42(td) ./doc/common/tables/ceilometer-redis.xml:22(td) ./doc/common/tables/cinder-common.xml:58(td) ./doc/common/tables/neutron-redis.xml:22(td)
-msgid "host = oslo"
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml:57(td)
+msgid "(IntOpt) TTL for vxlan interface protocol packets."
 msgstr ""
 
-#: ./doc/common/tables/heat-redis.xml:23(td)
-msgid "(StrOpt) Name of the engine node. This can be an opaque identifier. It is not necessarily a hostname, FQDN, or IP address."
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml:60(td)
+msgid "vxlan_group = 224.0.0.1"
 msgstr ""
 
-#: ./doc/common/tables/heat-redis.xml:26(th) ./doc/common/tables/trove-redis.xml:19(th) ./doc/common/tables/ceilometer-redis.xml:34(th) ./doc/common/tables/neutron-redis.xml:26(th)
-msgid "[matchmaker_redis]"
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml:61(td)
+msgid "(StrOpt) Multicast group for vxlan interface."
 msgstr ""
 
-#: ./doc/common/tables/heat-redis.xml:29(td) ./doc/common/tables/trove-redis.xml:22(td) ./doc/common/tables/ceilometer-redis.xml:37(td) ./doc/common/tables/glance-redis.xml:22(td) ./doc/common/tables/neutron-redis.xml:29(td) ./doc/common/tables/keystone-redis.xml:22(td) ./doc/common/tables/neutron-nec.xml:38(td)
-msgid "host = 127.0.0.1"
+#: ./doc/common/tables/nova-redis.xml:23(td) ./doc/common/tables/glance-redis.xml:27(td) ./doc/common/tables/cinder-rpc.xml:83(td) ./doc/common/tables/keystone-redis.xml:35(td)
+msgid "(StrOpt) Password for Redis server (optional)."
 msgstr ""
 
-#: ./doc/common/tables/heat-redis.xml:30(td) ./doc/common/tables/trove-redis.xml:23(td) ./doc/common/tables/ceilometer-redis.xml:38(td) ./doc/common/tables/neutron-redis.xml:30(td)
-msgid "(StrOpt) Host to locate redis"
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml:21(td)
+msgid "bind_port = 6001"
 msgstr ""
 
-#: ./doc/common/tables/heat-redis.xml:33(td) ./doc/common/tables/trove-redis.xml:26(td) ./doc/common/tables/keystone-ldap.xml:90(td) ./doc/common/tables/ceilometer-redis.xml:41(td) ./doc/common/tables/cinder-rpc.xml:82(td) ./doc/common/tables/glance-redis.xml:26(td) ./doc/common/tables/neutron-redis.xml:33(td) ./doc/common/tables/keystone-redis.xml:34(td) ./doc/common/tables/neutron-ml2_odl.xml:22(td) ./doc/common/tables/neutron-ml2_ncs.xml:22(td) ./doc/common/tables/nova-redis.xml:22(td)
-msgid "password = None"
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml:36(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:36(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:36(td)
+msgid "devices = /srv/node"
 msgstr ""
 
-#: ./doc/common/tables/heat-redis.xml:34(td) ./doc/common/tables/trove-redis.xml:27(td) ./doc/common/tables/ceilometer-redis.xml:42(td) ./doc/common/tables/neutron-redis.xml:34(td)
-msgid "(StrOpt) Password for Redis server. (optional)"
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml:36(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:36(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:36(td)
+msgid "Parent directory of where devices are mounted"
 msgstr ""
 
-#: ./doc/common/tables/heat-redis.xml:37(td) ./doc/common/tables/trove-redis.xml:30(td) ./doc/common/tables/nova-common.xml:74(td) ./doc/common/tables/ceilometer-redis.xml:45(td) ./doc/common/tables/cinder-rpc.xml:86(td) ./doc/common/tables/glance-redis.xml:30(td) ./doc/common/tables/neutron-redis.xml:37(td) ./doc/common/tables/keystone-redis.xml:38(td)
-msgid "port = 6379"
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml:39(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:39(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:39(td)
+msgid "mount_check = true"
 msgstr ""
 
-#: ./doc/common/tables/heat-redis.xml:38(td) ./doc/common/tables/trove-redis.xml:31(td) ./doc/common/tables/nova-common.xml:75(td) ./doc/common/tables/ceilometer-redis.xml:46(td) ./doc/common/tables/cinder-rpc.xml:87(td) ./doc/common/tables/glance-redis.xml:31(td) ./doc/common/tables/neutron-redis.xml:38(td) ./doc/common/tables/keystone-redis.xml:39(td)
-msgid "(IntOpt) Use this port to connect to redis host."
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml:39(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:39(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:39(td)
+msgid "Whether or not check if the devices are mounted to prevent accidentally writing to the root device"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:8(caption) ./doc/common/tables/glance-logging.xml:8(caption) ./doc/common/tables/ceilometer-logging.xml:8(caption) ./doc/common/tables/neutron-logging.xml:8(caption) ./doc/common/tables/heat-logging.xml:8(caption) ./doc/common/tables/keystone-logging.xml:8(caption) ./doc/common/tables/nova-logging.xml:8(caption)
-msgid "Description of configuration options for logging"
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml:42(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:42(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:42(td)
+msgid "disable_fallocate = false"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:22(td)
-msgid "format_options = -m 5"
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml:42(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:42(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:42(td)
+msgid "Disable \"fast fail\" fallocate checks if the underlying filesystem does not support it."
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:23(td) ./doc/common/tables/trove-logging.xml:71(td) ./doc/common/tables/trove-compute.xml:23(td) ./doc/common/tables/trove-compute.xml:27(td) ./doc/common/tables/trove-api.xml:39(td) ./doc/common/tables/trove-api.xml:83(td) ./doc/common/tables/trove-api.xml:91(td) ./doc/common/tables/trove-api.xml:95(td) ./doc/common/tables/trove-debug.xml:55(td) ./doc/common/tables/trove-debug.xml:59(td) ./doc/common/tables/trove-debug.xml:63(td) ./doc/common/tables/trove-debug.xml:67(td) ./doc/common/tables/trove-debug.xml:71(td) ./doc/common/tables/trove-debug.xml:75(td) ./doc/common/tables/trove-backup.xml:39(td) ./doc/common/tables/trove-backup.xml:55(td) ./doc/common/tables/trove-swift.xml:23(td) ./doc/common/tables/trove-volume.xml:23(td) ./doc/common/tables/trove-volume.xml:27(td) ./doc/common/tables/trove-volume.xml:31(td) ./doc/common/tables/trove-volume.xml:43(td) ./doc/common/tables/trove-rpc.xml:27(td) ./doc/common/tables/trove-common.xml:71(td) ./doc/common/tables/trove-dns.xml:23(td) ./doc/common/tables/trove-dns.xml:27(td) ./doc/common/tables/trove-dns.xml:31(td) ./doc/common/tables/trove-dns.xml:35(td) ./doc/common/tables/trove-dns.xml:39(td) ./doc/common/tables/trove-dns.xml:43(td) ./doc/common/tables/trove-dns.xml:47(td) ./doc/common/tables/trove-dns.xml:51(td) ./doc/common/tables/trove-dns.xml:55(td) ./doc/common/tables/trove-dns.xml:59(td) ./doc/common/tables/trove-dns.xml:63(td) ./doc/common/tables/trove-dns.xml:67(td) ./doc/common/tables/trove-dns.xml:79(td) ./doc/common/tables/trove-heat.xml:27(td) ./doc/common/tables/trove-guestagent.xml:39(td) ./doc/common/tables/trove-guestagent.xml:51(td) ./doc/common/tables/trove-amqp.xml:31(td)
-msgid "(StrOpt) No help text available for this option."
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml:58(td)
+msgid "allowed_sync_hosts = 127.0.0.1"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:26(td) ./doc/common/tables/glance-logging.xml:34(td) ./doc/common/tables/cinder-images.xml:62(td) ./doc/common/tables/ceilometer-logging.xml:34(td) ./doc/common/tables/neutron-logging.xml:34(td) ./doc/common/tables/heat-logging.xml:26(td) ./doc/common/tables/keystone-logging.xml:26(td) ./doc/common/tables/nova-logging.xml:38(td)
-msgid "instance_format = \"[instance: %(uuid)s] \""
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml:100(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:97(td)
+msgid "db_preallocation = off"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:27(td) ./doc/common/tables/glance-logging.xml:35(td) ./doc/common/tables/cinder-images.xml:63(td) ./doc/common/tables/ceilometer-logging.xml:35(td) ./doc/common/tables/neutron-logging.xml:35(td) ./doc/common/tables/heat-logging.xml:27(td) ./doc/common/tables/keystone-logging.xml:27(td) ./doc/common/tables/nova-logging.xml:39(td)
-msgid "(StrOpt) If an instance is passed with the log message, format it like this"
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml:100(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:97(td)
+msgid "If you don't mind the extra disk space usage in overhead, you can turn this on to preallocate disk space with SQLite databases to decrease fragmentation. underlying filesystem does not support it. to setup custom log handlers. bytes you'd like fallocate to reserve, whether there is space for the given file size or not. This is useful for systems that behave badly when they completely run out of space; you can make the services pretend they're out of space early. server. For most cases, this should be `egg:swift#account`. replication passes account can be reclaimed"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:30(td) ./doc/common/tables/glance-logging.xml:38(td) ./doc/common/tables/cinder-images.xml:66(td) ./doc/common/tables/ceilometer-logging.xml:38(td) ./doc/common/tables/neutron-logging.xml:38(td) ./doc/common/tables/heat-logging.xml:30(td) ./doc/common/tables/keystone-logging.xml:30(td) ./doc/common/tables/nova-logging.xml:42(td)
-msgid "instance_uuid_format = \"[instance: %(uuid)s] \""
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml:106(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:106(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:103(td)
+msgid "fallocate_reserve = 0"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:31(td) ./doc/common/tables/glance-logging.xml:39(td) ./doc/common/tables/cinder-images.xml:67(td) ./doc/common/tables/ceilometer-logging.xml:39(td) ./doc/common/tables/neutron-logging.xml:39(td) ./doc/common/tables/heat-logging.xml:31(td) ./doc/common/tables/keystone-logging.xml:31(td) ./doc/common/tables/nova-logging.xml:43(td)
-msgid "(StrOpt) If an instance UUID is passed with the log message, format it like this"
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml:106(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:106(td) ./doc/common/tables/swift-account-server-DEFAULT.xml:103(td)
+msgid "You can set fallocate_reserve to the number of bytes you'd like fallocate to reserve, whether there is space for the given file size or not. This is useful for systems that behave badly when they completely run out of space; you can make the services pretend they're out of space early. server. For most cases, this should be `egg:swift#object`."
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:34(td) ./doc/common/tables/glance-logging.xml:42(td) ./doc/common/tables/ceilometer-logging.xml:42(td) ./doc/common/tables/neutron-logging.xml:42(td) ./doc/common/tables/heat-logging.xml:34(td) ./doc/common/tables/keystone-logging.xml:34(td) ./doc/common/tables/nova-logging.xml:46(td) ./doc/common/tables/cinder-common.xml:74(td)
-msgid "log_config_append = None"
+#: ./doc/common/tables/nova-db.xml:8(caption) ./doc/common/tables/glance-db.xml:8(caption) ./doc/common/tables/neutron-db.xml:8(caption)
+msgid "Description of configuration options for db"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:35(td) ./doc/common/tables/glance-logging.xml:43(td) ./doc/common/tables/ceilometer-logging.xml:43(td) ./doc/common/tables/neutron-logging.xml:43(td) ./doc/common/tables/heat-logging.xml:35(td) ./doc/common/tables/keystone-logging.xml:35(td) ./doc/common/tables/nova-logging.xml:47(td) ./doc/common/tables/cinder-common.xml:75(td)
-msgid "(StrOpt) The name of logging configuration file. It does not disable existing loggers, but just appends specified logging configuration to any other existing logging options. Please see the Python logging module documentation for details on logging configuration files."
+#: ./doc/common/tables/nova-db.xml:22(td)
+msgid "db_driver = nova.db"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:38(td) ./doc/common/tables/glance-logging.xml:46(td) ./doc/common/tables/ceilometer-logging.xml:46(td) ./doc/common/tables/neutron-logging.xml:46(td) ./doc/common/tables/heat-logging.xml:38(td) ./doc/common/tables/keystone-logging.xml:38(td) ./doc/common/tables/nova-logging.xml:50(td) ./doc/common/tables/cinder-common.xml:78(td)
-msgid "log_date_format = %Y-%m-%d %H:%M:%S"
+#: ./doc/common/tables/nova-db.xml:23(td)
+msgid "(StrOpt) The driver to use for database access"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:39(td) ./doc/common/tables/glance-logging.xml:47(td) ./doc/common/tables/ceilometer-logging.xml:47(td) ./doc/common/tables/neutron-logging.xml:47(td) ./doc/common/tables/heat-logging.xml:39(td) ./doc/common/tables/keystone-logging.xml:39(td) ./doc/common/tables/nova-logging.xml:51(td) ./doc/common/tables/cinder-common.xml:79(td)
-msgid "(StrOpt) Format string for %%(asctime)s in log records. Default: %(default)s"
+#: ./doc/common/tables/nova-db.xml:26(th) ./doc/common/tables/ceilometer-cells.xml:19(th) ./doc/common/tables/nova-upgrade_levels.xml:19(th) ./doc/common/tables/nova-cells.xml:19(th) ./doc/common/tables/nova-rpc_all.xml:198(th) ./doc/common/tables/nova-scheduling.xml:118(th) ./doc/common/tables/nova-quota.xml:82(th) ./doc/common/tables/nova-rpc.xml:62(th)
+msgid "[cells]"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:42(td) ./doc/common/tables/glance-logging.xml:50(td) ./doc/common/tables/ceilometer-logging.xml:50(td) ./doc/common/tables/neutron-logging.xml:50(td) ./doc/common/tables/heat-logging.xml:42(td) ./doc/common/tables/keystone-logging.xml:42(td) ./doc/common/tables/nova-logging.xml:54(td) ./doc/common/tables/cinder-common.xml:82(td)
-msgid "log_dir = None"
+#: ./doc/common/tables/nova-db.xml:29(td)
+msgid "db_check_interval = 60"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:43(td) ./doc/common/tables/glance-logging.xml:51(td) ./doc/common/tables/ceilometer-logging.xml:51(td) ./doc/common/tables/neutron-logging.xml:51(td) ./doc/common/tables/heat-logging.xml:43(td) ./doc/common/tables/keystone-logging.xml:43(td) ./doc/common/tables/nova-logging.xml:55(td) ./doc/common/tables/cinder-common.xml:83(td)
-msgid "(StrOpt) (Optional) The base directory used for relative --log-file paths"
+#: ./doc/common/tables/nova-db.xml:30(td)
+msgid "(IntOpt) Interval, in seconds, for getting fresh cell information from the database."
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:46(td) ./doc/common/tables/glance-logging.xml:54(td) ./doc/common/tables/ceilometer-logging.xml:54(td) ./doc/common/tables/neutron-logging.xml:54(td) ./doc/common/tables/heat-logging.xml:46(td) ./doc/common/tables/keystone-logging.xml:46(td) ./doc/common/tables/nova-logging.xml:58(td) ./doc/common/tables/cinder-common.xml:86(td)
-msgid "log_file = None"
+#: ./doc/common/tables/nova-db.xml:40(td) ./doc/common/tables/glance-db.xml:26(td) ./doc/common/tables/keystone-database.xml:26(td)
+msgid "connection = None"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:47(td) ./doc/common/tables/glance-logging.xml:55(td) ./doc/common/tables/ceilometer-logging.xml:55(td) ./doc/common/tables/neutron-logging.xml:55(td) ./doc/common/tables/heat-logging.xml:47(td) ./doc/common/tables/keystone-logging.xml:47(td) ./doc/common/tables/nova-logging.xml:59(td) ./doc/common/tables/cinder-common.xml:87(td)
-msgid "(StrOpt) (Optional) Name of log file to output to. If no default is set, logging will go to stdout."
+#: ./doc/common/tables/nova-db.xml:52(td) ./doc/common/tables/glance-db.xml:38(td) ./doc/common/tables/neutron-db.xml:49(td) ./doc/common/tables/keystone-database.xml:38(td)
+msgid "db_inc_retry_interval = True"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:50(td) ./doc/common/tables/glance-logging.xml:58(td) ./doc/common/tables/ceilometer-logging.xml:58(td) ./doc/common/tables/neutron-logging.xml:58(td) ./doc/common/tables/heat-logging.xml:50(td) ./doc/common/tables/keystone-logging.xml:50(td) ./doc/common/tables/nova-logging.xml:62(td) ./doc/common/tables/cinder-common.xml:90(td)
-msgid "log_format = None"
+#: ./doc/common/tables/nova-db.xml:53(td) ./doc/common/tables/glance-db.xml:39(td) ./doc/common/tables/neutron-db.xml:50(td) ./doc/common/tables/keystone-database.xml:39(td)
+msgid "(BoolOpt) Whether to increase interval between db connection retries, up to db_max_retry_interval"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:51(td) ./doc/common/tables/glance-logging.xml:59(td) ./doc/common/tables/ceilometer-logging.xml:59(td) ./doc/common/tables/neutron-logging.xml:59(td) ./doc/common/tables/heat-logging.xml:51(td) ./doc/common/tables/keystone-logging.xml:51(td) ./doc/common/tables/nova-logging.xml:63(td) ./doc/common/tables/cinder-common.xml:91(td)
-msgid "(StrOpt) DEPRECATED. A logging.Formatter log message format string which may use any of the available logging.LogRecord attributes. This option is deprecated. Please use logging_context_format_string and logging_default_format_string instead."
+#: ./doc/common/tables/nova-db.xml:56(td) ./doc/common/tables/glance-db.xml:42(td) ./doc/common/tables/neutron-db.xml:53(td) ./doc/common/tables/keystone-database.xml:42(td)
+msgid "db_max_retries = 20"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:54(td) ./doc/common/tables/glance-logging.xml:62(td) ./doc/common/tables/ceilometer-logging.xml:62(td) ./doc/common/tables/neutron-logging.xml:62(td) ./doc/common/tables/heat-logging.xml:54(td) ./doc/common/tables/keystone-logging.xml:54(td) ./doc/common/tables/cinder-common.xml:94(td)
-msgid "logging_context_format_string = %(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [%(request_id)s %(user_identity)s] %(instance)s%(message)s"
+#: ./doc/common/tables/nova-db.xml:57(td) ./doc/common/tables/glance-db.xml:43(td) ./doc/common/tables/neutron-db.xml:54(td) ./doc/common/tables/keystone-database.xml:43(td)
+msgid "(IntOpt) maximum db connection retries before error is raised. (setting -1 implies an infinite retry count)"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:55(td) ./doc/common/tables/neutron-logging.xml:63(td) ./doc/common/tables/heat-logging.xml:55(td) ./doc/common/tables/nova-logging.xml:67(td)
-msgid "(StrOpt) format string to use for log messages with context"
+#: ./doc/common/tables/nova-db.xml:60(td) ./doc/common/tables/glance-db.xml:46(td) ./doc/common/tables/neutron-db.xml:57(td) ./doc/common/tables/keystone-database.xml:46(td)
+msgid "db_max_retry_interval = 10"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:58(td) ./doc/common/tables/glance-logging.xml:66(td) ./doc/common/tables/ceilometer-logging.xml:66(td) ./doc/common/tables/neutron-logging.xml:66(td) ./doc/common/tables/heat-logging.xml:58(td) ./doc/common/tables/keystone-logging.xml:58(td) ./doc/common/tables/nova-logging.xml:70(td) ./doc/common/tables/cinder-common.xml:98(td)
-msgid "logging_debug_format_suffix = %(funcName)s %(pathname)s:%(lineno)d"
+#: ./doc/common/tables/nova-db.xml:61(td) ./doc/common/tables/glance-db.xml:47(td) ./doc/common/tables/neutron-db.xml:58(td) ./doc/common/tables/keystone-database.xml:47(td)
+msgid "(IntOpt) max seconds between db connection retries, if db_inc_retry_interval is enabled"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:59(td) ./doc/common/tables/neutron-logging.xml:67(td) ./doc/common/tables/heat-logging.xml:59(td) ./doc/common/tables/nova-logging.xml:71(td)
-msgid "(StrOpt) data to append to log format when level is DEBUG"
+#: ./doc/common/tables/nova-db.xml:64(td) ./doc/common/tables/glance-db.xml:50(td) ./doc/common/tables/neutron-db.xml:61(td) ./doc/common/tables/keystone-database.xml:50(td)
+msgid "db_retry_interval = 1"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:62(td) ./doc/common/tables/glance-logging.xml:70(td) ./doc/common/tables/ceilometer-logging.xml:70(td) ./doc/common/tables/neutron-logging.xml:70(td) ./doc/common/tables/heat-logging.xml:62(td) ./doc/common/tables/keystone-logging.xml:62(td) ./doc/common/tables/nova-logging.xml:74(td) ./doc/common/tables/cinder-common.xml:102(td)
-msgid "logging_default_format_string = %(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [-] %(instance)s%(message)s"
+#: ./doc/common/tables/nova-db.xml:65(td) ./doc/common/tables/glance-db.xml:51(td) ./doc/common/tables/neutron-db.xml:62(td) ./doc/common/tables/keystone-database.xml:51(td)
+msgid "(IntOpt) seconds between db connection retries"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:63(td) ./doc/common/tables/neutron-logging.xml:71(td) ./doc/common/tables/heat-logging.xml:63(td) ./doc/common/tables/nova-logging.xml:75(td)
-msgid "(StrOpt) format string to use for log messages without context"
+#: ./doc/common/tables/nova-db.xml:88(td)
+msgid "mysql_sql_mode = None"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:66(td) ./doc/common/tables/glance-logging.xml:74(td) ./doc/common/tables/ceilometer-logging.xml:74(td) ./doc/common/tables/neutron-logging.xml:74(td) ./doc/common/tables/heat-logging.xml:66(td) ./doc/common/tables/keystone-logging.xml:66(td) ./doc/common/tables/nova-logging.xml:78(td) ./doc/common/tables/cinder-common.xml:106(td)
-msgid "logging_exception_prefix = %(asctime)s.%(msecs)03d %(process)d TRACE %(name)s %(instance)s"
+#: ./doc/common/tables/nova-db.xml:89(td)
+msgid "(StrOpt) The SQL mode to be used for MySQL sessions (default is empty, meaning do not override any server-side SQL mode setting)"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:67(td) ./doc/common/tables/neutron-logging.xml:75(td) ./doc/common/tables/heat-logging.xml:67(td) ./doc/common/tables/nova-logging.xml:79(td)
-msgid "(StrOpt) prefix each line of exception output with this format"
+#: ./doc/common/tables/nova-db.xml:100(td)
+msgid "slave_connection = None"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:70(td)
-msgid "network_label_regex = ^private$"
+#: ./doc/common/tables/nova-db.xml:104(td)
+msgid "sqlite_db = nova.sqlite"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:75(td) ./doc/common/tables/heat-notification.xml:27(td) ./doc/common/tables/neutron-logging.xml:79(td) ./doc/common/tables/nova-logging.xml:83(td)
-msgid "(BoolOpt) publish error events"
+#: ./doc/common/tables/nova-db.xml:112(td) ./doc/common/tables/glance-db.xml:94(td) ./doc/common/tables/neutron-db.xml:97(td) ./doc/common/tables/keystone-database.xml:94(td)
+msgid "use_db_reconnect = False"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:78(td) ./doc/common/tables/glance-logging.xml:82(td) ./doc/common/tables/ceilometer-logging.xml:82(td) ./doc/common/tables/neutron-logging.xml:82(td) ./doc/common/tables/heat-logging.xml:70(td) ./doc/common/tables/keystone-logging.xml:70(td) ./doc/common/tables/nova-logging.xml:86(td) ./doc/common/tables/cinder-common.xml:194(td)
-msgid "syslog_log_facility = LOG_USER"
+#: ./doc/common/tables/nova-db.xml:113(td) ./doc/common/tables/glance-db.xml:95(td) ./doc/common/tables/neutron-db.xml:98(td) ./doc/common/tables/keystone-database.xml:95(td)
+msgid "(BoolOpt) Enable the experimental use of database reconnect on connection lost"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:79(td) ./doc/common/tables/neutron-logging.xml:83(td) ./doc/common/tables/heat-logging.xml:71(td) ./doc/common/tables/nova-logging.xml:87(td)
-msgid "(StrOpt) syslog facility to receive log lines"
+#: ./doc/common/tables/glance-rabbitmq.xml:23(td) ./doc/common/tables/keystone-amqp.xml:31(td) ./doc/common/tables/cinder-rpc.xml:35(td) ./doc/common/tables/nova-rpc_all.xml:31(td) ./doc/common/tables/nova-rpc.xml:31(td)
+msgid "(StrOpt) The default exchange under which topics are scoped. May be overridden by an exchange name specified in the transport_url option."
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:82(td) ./doc/common/tables/glance-logging.xml:86(td) ./doc/common/tables/ceilometer-logging.xml:86(td) ./doc/common/tables/neutron-logging.xml:90(td) ./doc/common/tables/heat-logging.xml:74(td) ./doc/common/tables/keystone-logging.xml:74(td) ./doc/common/tables/nova-logging.xml:90(td) ./doc/common/tables/cinder-common.xml:210(td)
-msgid "use_stderr = True"
+#: ./doc/common/tables/neutron-l3_agent.xml:8(caption)
+msgid "Description of configuration options for l3_agent"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:83(td) ./doc/common/tables/glance-logging.xml:87(td) ./doc/common/tables/ceilometer-logging.xml:87(td) ./doc/common/tables/neutron-logging.xml:91(td) ./doc/common/tables/heat-logging.xml:75(td) ./doc/common/tables/keystone-logging.xml:75(td) ./doc/common/tables/nova-logging.xml:91(td) ./doc/common/tables/cinder-common.xml:211(td)
-msgid "(BoolOpt) Log output to standard error"
+#: ./doc/common/tables/neutron-l3_agent.xml:22(td)
+msgid "enable_metadata_proxy = True"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:86(td) ./doc/common/tables/glance-logging.xml:90(td) ./doc/common/tables/ceilometer-logging.xml:90(td) ./doc/common/tables/cinder-rootwrap.xml:30(td) ./doc/common/tables/neutron-logging.xml:94(td) ./doc/common/tables/heat-logging.xml:78(td) ./doc/common/tables/keystone-logging.xml:78(td) ./doc/common/tables/nova-logging.xml:94(td) ./doc/common/tables/cinder-common.xml:214(td) ./doc/common/tables/neutron-rootwrap.xml:30(td) ./doc/common/tables/nova-rootwrap.xml:30(td)
-msgid "use_syslog = False"
+#: ./doc/common/tables/neutron-l3_agent.xml:23(td)
+msgid "(BoolOpt) Allow running metadata proxy."
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml:87(td) ./doc/common/tables/neutron-logging.xml:95(td) ./doc/common/tables/heat-logging.xml:79(td)
-msgid "(BoolOpt) Use syslog for logging."
+#: ./doc/common/tables/neutron-l3_agent.xml:26(td)
+msgid "external_network_bridge = br-ex"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-container-updater.xml:7(literal)
-msgid "[container-updater]"
+#: ./doc/common/tables/neutron-l3_agent.xml:27(td)
+msgid "(StrOpt) Name of bridge used for external network traffic."
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-container-updater.xml:18(td)
-msgid "log_name = container-updater"
+#: ./doc/common/tables/neutron-l3_agent.xml:30(td)
+msgid "gateway_external_network_id ="
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-container-updater.xml:30(td) ./doc/common/tables/swift-container-server-container-sync.xml:33(td) ./doc/common/tables/swift-object-server-object-updater.xml:30(td) ./doc/common/tables/swift-object-expirer-object-expirer.xml:18(td)
-msgid "interval = 300"
+#: ./doc/common/tables/neutron-l3_agent.xml:31(td)
+msgid "(StrOpt) UUID of external network for routers implemented by the agents."
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-container-updater.xml:30(td) ./doc/common/tables/swift-container-server-container-replicator.xml:42(td) ./doc/common/tables/swift-container-server-container-sync.xml:33(td) ./doc/common/tables/swift-object-server-object-updater.xml:30(td) ./doc/common/tables/swift-account-server-account-auditor.xml:30(td) ./doc/common/tables/swift-container-server-container-auditor.xml:30(td) ./doc/common/tables/swift-account-server-account-replicator.xml:42(td) ./doc/common/tables/swift-object-expirer-object-expirer.xml:18(td) ./doc/common/tables/swift-account-server-account-reaper.xml:33(td)
-msgid "Minimum time for a pass to take"
+#: ./doc/common/tables/neutron-l3_agent.xml:34(td)
+msgid "handle_internal_only_routers = True"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-container-updater.xml:33(td)
-msgid "concurrency = 4"
+#: ./doc/common/tables/neutron-l3_agent.xml:35(td)
+msgid "(BoolOpt) Agent should implement routers with no gateway"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-container-updater.xml:33(td) ./doc/common/tables/swift-container-server-container-replicator.xml:39(td) ./doc/common/tables/swift-object-server-object-updater.xml:33(td) ./doc/common/tables/swift-object-server-object-replicator.xml:39(td) ./doc/common/tables/swift-dispersion-dispersion.xml:54(td) ./doc/common/tables/swift-account-server-account-replicator.xml:39(td) ./doc/common/tables/swift-object-expirer-object-expirer.xml:30(td) ./doc/common/tables/swift-account-server-account-reaper.xml:30(td)
-msgid "Number of replication workers to spawn"
+#: ./doc/common/tables/neutron-l3_agent.xml:38(td)
+msgid "router_id ="
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-container-updater.xml:36(td) ./doc/common/tables/swift-container-server-app-container-server.xml:36(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:112(td)
-msgid "node_timeout = 3"
+#: ./doc/common/tables/neutron-l3_agent.xml:39(td)
+msgid "(StrOpt) If namespaces is disabled, the l3 agent can only configure a router that has the matching router ID."
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-container-updater.xml:36(td) ./doc/common/tables/swift-container-server-container-replicator.xml:45(td) ./doc/common/tables/swift-object-server-object-updater.xml:36(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:48(td) ./doc/common/tables/swift-container-server-app-container-server.xml:36(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:112(td) ./doc/common/tables/swift-object-server-object-replicator.xml:57(td) ./doc/common/tables/swift-account-server-account-replicator.xml:51(td) ./doc/common/tables/swift-account-server-account-reaper.xml:36(td)
-msgid "Request timeout to external services"
+#: ./doc/common/tables/neutron-l3_agent.xml:42(td)
+msgid "send_arp_for_ha = 0"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-container-updater.xml:39(td) ./doc/common/tables/swift-container-server-container-replicator.xml:48(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:54(td) ./doc/common/tables/swift-container-server-app-container-server.xml:39(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:109(td) ./doc/common/tables/swift-account-server-account-replicator.xml:54(td) ./doc/common/tables/swift-account-server-account-reaper.xml:39(td)
-msgid "conn_timeout = 0.5"
+#: ./doc/common/tables/neutron-l3_agent.xml:43(td)
+msgid "(IntOpt) Send this many gratuitous ARPs for HA setup, if less than or equal to 0, the feature is disabled"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-container-updater.xml:39(td) ./doc/common/tables/swift-container-server-container-replicator.xml:48(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:54(td) ./doc/common/tables/swift-container-server-app-container-server.xml:39(td) ./doc/common/tables/swift-object-server-DEFAULT.xml:109(td) ./doc/common/tables/swift-account-server-account-replicator.xml:54(td) ./doc/common/tables/swift-account-server-account-reaper.xml:39(td)
-msgid "Connection timeout to external services"
+#: ./doc/common/tables/swift-container-server-pipeline-main.xml:18(td)
+msgid "pipeline = healthcheck recon container-server"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-container-updater.xml:42(td) ./doc/common/tables/swift-object-server-object-updater.xml:39(td)
-msgid "slowdown = 0.01"
+#: ./doc/common/tables/glance-policy.xml:23(td)
+msgid "(StrOpt) The default policy to use."
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-container-updater.xml:42(td) ./doc/common/tables/swift-object-server-object-updater.xml:39(td)
-msgid "Time in seconds to wait between objects"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml:45(td)
-msgid "account_suppression_time = 60"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml:45(td)
-msgid "Seconds to suppress updating an account that has generated an error (timeout, not yet found, etc.)"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml:49(td) ./doc/common/tables/swift-account-server-filter-recon.xml:21(td) ./doc/common/tables/swift-container-server-container-replicator.xml:57(td) ./doc/common/tables/swift-object-server-object-auditor.xml:42(td) ./doc/common/tables/swift-object-server-object-updater.xml:42(td) ./doc/common/tables/swift-account-server-account-auditor.xml:42(td) ./doc/common/tables/swift-object-server-filter-recon.xml:21(td) ./doc/common/tables/swift-container-server-container-auditor.xml:36(td) ./doc/common/tables/swift-object-server-object-replicator.xml:72(td) ./doc/common/tables/swift-account-server-account-replicator.xml:63(td) ./doc/common/tables/swift-container-server-filter-recon.xml:21(td)
-msgid "recon_cache_path = /var/cache/swift"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml:49(td) ./doc/common/tables/swift-account-server-filter-recon.xml:21(td) ./doc/common/tables/swift-container-server-container-replicator.xml:57(td) ./doc/common/tables/swift-object-server-object-auditor.xml:42(td) ./doc/common/tables/swift-object-server-object-updater.xml:42(td) ./doc/common/tables/swift-account-server-account-auditor.xml:42(td) ./doc/common/tables/swift-object-server-filter-recon.xml:21(td) ./doc/common/tables/swift-container-server-container-auditor.xml:36(td) ./doc/common/tables/swift-object-server-object-replicator.xml:72(td) ./doc/common/tables/swift-account-server-account-replicator.xml:63(td) ./doc/common/tables/swift-container-server-filter-recon.xml:21(td)
-msgid "Directory where stats for a few items will be stored"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml:8(caption)
-msgid "Description of configuration options for storage_gpfs"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml:22(td)
-msgid "gpfs_images_dir = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml:23(td)
-msgid "(StrOpt) Specifies the path of the Image service repository in GPFS. Leave undefined if not storing images in GPFS."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml:26(td)
-msgid "gpfs_images_share_mode = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml:27(td)
-msgid "(StrOpt) Specifies the type of image copy to be used. Set this when the Image service repository also uses GPFS so that image files can be transferred efficiently from the Image service to the Block Storage service. There are two valid values: \"copy\" specifies that a full copy of the image is made; \"copy_on_write\" specifies that copy-on-write optimization strategy is used and unmodified blocks of the image file are shared efficiently."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml:30(td)
-msgid "gpfs_max_clone_depth = 0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml:31(td)
-msgid "(IntOpt) Specifies an upper limit on the number of indirections required to reach a specific block due to snapshots or clones. A lengthy chain of copy-on-write snapshots or clones can have a negative impact on performance, but improves space utilization. 0 indicates unlimited clone depth."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml:34(td)
-msgid "gpfs_mount_point_base = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml:35(td)
-msgid "(StrOpt) Specifies the path of the GPFS directory where Block Storage volume and snapshot files are stored."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml:38(td)
-msgid "gpfs_sparse_volumes = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml:39(td)
-msgid "(BoolOpt) Specifies that volumes are created as sparse files which initially consume no space. If set to False, the volume is created as a fully allocated file, in which case, creation may take a significantly longer time."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml:42(td)
-msgid "gpfs_storage_pool = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml:43(td)
-msgid "(StrOpt) Specifies the storage pool that volumes are assigned to. By default, the system storage pool is used."
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:8(caption)
-msgid "Description of configuration options for nexenta_iscsi"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:22(td)
-msgid "nexenta_blocksize ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:23(td)
-msgid "(StrOpt) block size for volumes (blank=default,8KB)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:26(td)
-msgid "nexenta_host ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:27(td)
-msgid "(StrOpt) IP address of Nexenta SA"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:30(td)
-msgid "nexenta_iscsi_target_portal_port = 3260"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:31(td)
-msgid "(IntOpt) Nexenta target portal port"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:34(td)
-msgid "nexenta_password = nexenta"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:35(td)
-msgid "(StrOpt) Password to connect to Nexenta SA"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:38(td)
-msgid "nexenta_rest_port = 2000"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:39(td)
-msgid "(IntOpt) HTTP port to connect to Nexenta REST API server"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:42(td)
-msgid "nexenta_rest_protocol = auto"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:43(td)
-msgid "(StrOpt) Use http or https for REST connection (default auto)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:46(td)
-msgid "nexenta_rrmgr_compression = 0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:47(td)
-msgid "(IntOpt) Enable stream compression, level 1..9. 1 - gives best speed; 9 - gives best compression."
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:50(td)
-msgid "nexenta_rrmgr_connections = 2"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:51(td)
-msgid "(IntOpt) Number of TCP connections."
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:54(td)
-msgid "nexenta_rrmgr_tcp_buf_size = 4096"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:55(td)
-msgid "(IntOpt) TCP Buffer size in KiloBytes."
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:58(td)
-msgid "nexenta_sparse = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:59(td)
-msgid "(BoolOpt) flag to create sparse volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:62(td)
-msgid "nexenta_sparsed_volumes = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:63(td) ./doc/common/tables/cinder-storage_nfs.xml:39(td) ./doc/common/tables/cinder-storage_glusterfs.xml:35(td)
-msgid "(BoolOpt) Create volumes as sparsed files which take no space.If set to False volume is created as regular file.In such case volume creation takes a lot of time."
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:66(td)
-msgid "nexenta_target_group_prefix = cinder/"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:67(td)
-msgid "(StrOpt) prefix for iSCSI target groups on SA"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:70(td)
-msgid "nexenta_target_prefix = iqn.1986-03.com.sun:02:cinder-"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:71(td)
-msgid "(StrOpt) IQN prefix for iSCSI targets"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:74(td)
-msgid "nexenta_user = admin"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:75(td)
-msgid "(StrOpt) User name to connect to Nexenta SA"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:78(td)
-msgid "nexenta_volume = cinder"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml:79(td)
-msgid "(StrOpt) pool on SA that will hold all volumes"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml:8(caption)
-msgid "Description of configuration options for tilera"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml:22(td)
-msgid "tile_pdu_ip = 10.0.100.1"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml:23(td)
-msgid "(StrOpt) IP address of tilera pdu"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml:26(td)
-msgid "tile_pdu_mgr = /tftpboot/pdu_mgr"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml:27(td)
-msgid "(StrOpt) Management script for tilera pdu"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml:30(td)
-msgid "tile_pdu_off = 2"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml:31(td)
-msgid "(IntOpt) Power status of tilera PDU is OFF"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml:34(td)
-msgid "tile_pdu_on = 1"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml:35(td)
-msgid "(IntOpt) Power status of tilera PDU is ON"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml:38(td)
-msgid "tile_pdu_status = 9"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml:39(td)
-msgid "(IntOpt) Power status of tilera PDU"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml:42(td)
-msgid "tile_power_wait = 9"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml:43(td)
-msgid "(IntOpt) Wait time in seconds until check the result after tilera power operations"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml:8(caption)
-msgid "Description of configuration options for ca"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml:22(td)
-msgid "ca_file = cacert.pem"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml:23(td)
-msgid "(StrOpt) Filename of root CA"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml:26(td)
-msgid "ca_path = $state_path/CA"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml:27(td)
-msgid "(StrOpt) Where we keep our root CA"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml:30(td)
-msgid "cert_manager = nova.cert.manager.CertManager"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml:31(td)
-msgid "(StrOpt) Full class name for the Manager for cert"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml:34(td)
-msgid "cert_topic = cert"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml:35(td)
-msgid "(StrOpt) The topic cert nodes listen on"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml:38(td)
-msgid "crl_file = crl.pem"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml:39(td)
-msgid "(StrOpt) Filename of root Certificate Revocation List"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml:42(td)
-msgid "key_file = private/cakey.pem"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml:43(td)
-msgid "(StrOpt) Filename of private key"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml:46(td)
-msgid "keys_path = $state_path/keys"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml:47(td)
-msgid "(StrOpt) Where we keep our keys"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml:50(td)
-msgid "project_cert_subject = /C=US/ST=California/O=OpenStack/OU=NovaDev/CN=project-ca-%.16s-%s"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml:51(td)
-msgid "(StrOpt) Subject for certificate for projects, %s for project, timestamp"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml:54(td)
-msgid "use_project_ca = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml:55(td)
-msgid "(BoolOpt) Should we use a CA for each project?"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml:58(td)
-msgid "user_cert_subject = /C=US/ST=California/O=OpenStack/OU=NovaDev/CN=%.16s-%.16s-%s"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml:59(td)
-msgid "(StrOpt) Subject for certificate for users, %s for project, user, timestamp"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml:62(th) ./doc/common/tables/heat-cfn_api.xml:61(th) ./doc/common/tables/heat-cloudwatch_api.xml:57(th) ./doc/common/tables/cinder-ssl.xml:19(th) ./doc/common/tables/heat-api.xml:142(th) ./doc/common/tables/neutron-ssl.xml:34(th) ./doc/common/tables/trove-ssl.xml:19(th) ./doc/common/tables/keystone-ssl.xml:54(th) ./doc/common/tables/ceilometer-ssl.xml:19(th)
-msgid "[ssl]"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml:65(td) ./doc/common/tables/heat-clients_nova.xml:22(td) ./doc/common/tables/heat-cfn_api.xml:64(td) ./doc/common/tables/heat-clients.xml:29(td) ./doc/common/tables/heat-clients_heat.xml:22(td) ./doc/common/tables/heat-clients_swift.xml:22(td) ./doc/common/tables/heat-cloudwatch_api.xml:60(td) ./doc/common/tables/heat-clients_ceilometer.xml:22(td) ./doc/common/tables/heat-clients_trove.xml:22(td) ./doc/common/tables/heat-clients_cinder.xml:22(td) ./doc/common/tables/cinder-ssl.xml:22(td) ./doc/common/tables/heat-api.xml:145(td) ./doc/common/tables/neutron-ssl.xml:37(td) ./doc/common/tables/heat-clients_neutron.xml:22(td) ./doc/common/tables/trove-ssl.xml:22(td) ./doc/common/tables/glance-ssl.xml:22(td) ./doc/common/tables/heat-clients_keystone.xml:22(td) ./doc/common/tables/ceilometer-ssl.xml:22(td)
-msgid "ca_file = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml:66(td) ./doc/common/tables/glance-ssl.xml:23(td)
-msgid "(StrOpt) CA certificate file to use to verify connecting clients."
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml:69(td) ./doc/common/tables/heat-clients_nova.xml:26(td) ./doc/common/tables/heat-cfn_api.xml:45(td) ./doc/common/tables/heat-cfn_api.xml:68(td) ./doc/common/tables/heat-clients.xml:33(td) ./doc/common/tables/heat-clients_heat.xml:26(td) ./doc/common/tables/heat-clients_swift.xml:26(td) ./doc/common/tables/heat-cloudwatch_api.xml:41(td) ./doc/common/tables/heat-cloudwatch_api.xml:64(td) ./doc/common/tables/heat-clients_ceilometer.xml:26(td) ./doc/common/tables/heat-clients_trove.xml:26(td) ./doc/common/tables/heat-clients_cinder.xml:26(td) ./doc/common/tables/cinder-ssl.xml:26(td) ./doc/common/tables/heat-api.xml:115(td) ./doc/common/tables/heat-api.xml:149(td) ./doc/common/tables/neutron-ssl.xml:41(td) ./doc/common/tables/heat-clients_neutron.xml:26(td) ./doc/common/tables/trove-ssl.xml:26(td) ./doc/common/tables/glance-ssl.xml:26(td) ./doc/common/tables/heat-clients_keystone.xml:26(td) ./doc/common/tables/neutron-nec.xml:26(td) ./doc/common/tables/ceilometer-ssl.xml:26(td)
-msgid "cert_file = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml:70(td)
-msgid "(StrOpt) Certificate file to use when starting the server securely."
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml:73(td) ./doc/common/tables/heat-clients_nova.xml:38(td) ./doc/common/tables/heat-cfn_api.xml:49(td) ./doc/common/tables/heat-cfn_api.xml:72(td) ./doc/common/tables/heat-clients.xml:45(td) ./doc/common/tables/heat-clients_heat.xml:38(td) ./doc/common/tables/heat-clients_swift.xml:38(td) ./doc/common/tables/heat-cloudwatch_api.xml:45(td) ./doc/common/tables/heat-cloudwatch_api.xml:68(td) ./doc/common/tables/heat-clients_ceilometer.xml:38(td) ./doc/common/tables/heat-clients_trove.xml:38(td) ./doc/common/tables/heat-clients_cinder.xml:38(td) ./doc/common/tables/cinder-ssl.xml:30(td) ./doc/common/tables/heat-api.xml:119(td) ./doc/common/tables/heat-api.xml:153(td) ./doc/common/tables/neutron-ssl.xml:45(td) ./doc/common/tables/heat-clients_neutron.xml:38(td) ./doc/common/tables/trove-ssl.xml:30(td) ./doc/common/tables/glance-ssl.xml:30(td) ./doc/common/tables/heat-clients_keystone.xml:38(td) ./doc/common/tables/neutron-nec.xml:46(td) ./doc/common/tables/ceilometer-ssl.xml:30(td)
-msgid "key_file = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml:74(td)
-msgid "(StrOpt) Private key file to use when starting the server securely."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_nova.xml:8(caption)
-msgid "Description of configuration options for clients_nova"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_nova.xml:19(th)
-msgid "[clients_nova]"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_nova.xml:23(td) ./doc/common/tables/heat-clients.xml:30(td) ./doc/common/tables/heat-clients_heat.xml:23(td) ./doc/common/tables/heat-clients_swift.xml:23(td) ./doc/common/tables/heat-clients_ceilometer.xml:23(td) ./doc/common/tables/heat-clients_trove.xml:23(td) ./doc/common/tables/heat-clients_cinder.xml:23(td) ./doc/common/tables/heat-clients_neutron.xml:23(td) ./doc/common/tables/heat-clients_keystone.xml:23(td)
-msgid "(StrOpt) Optional CA cert file to use in SSL connections."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_nova.xml:27(td) ./doc/common/tables/heat-clients.xml:34(td) ./doc/common/tables/heat-clients_heat.xml:27(td) ./doc/common/tables/heat-clients_swift.xml:27(td) ./doc/common/tables/heat-clients_ceilometer.xml:27(td) ./doc/common/tables/heat-clients_trove.xml:27(td) ./doc/common/tables/heat-clients_cinder.xml:27(td) ./doc/common/tables/heat-clients_neutron.xml:27(td) ./doc/common/tables/heat-clients_keystone.xml:27(td)
-msgid "(StrOpt) Optional PEM-formatted certificate chain file."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_nova.xml:30(td) ./doc/common/tables/heat-clients.xml:37(td) ./doc/common/tables/heat-clients_heat.xml:30(td) ./doc/common/tables/heat-clients_swift.xml:30(td) ./doc/common/tables/heat-clients_ceilometer.xml:30(td) ./doc/common/tables/heat-clients_trove.xml:30(td) ./doc/common/tables/heat-clients_cinder.xml:30(td) ./doc/common/tables/swift-dispersion-dispersion.xml:39(td) ./doc/common/tables/heat-clients_neutron.xml:30(td) ./doc/common/tables/heat-clients_keystone.xml:30(td)
-msgid "endpoint_type = publicURL"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_nova.xml:31(td) ./doc/common/tables/heat-clients.xml:38(td) ./doc/common/tables/heat-clients_heat.xml:31(td) ./doc/common/tables/heat-clients_swift.xml:31(td) ./doc/common/tables/heat-clients_ceilometer.xml:31(td) ./doc/common/tables/heat-clients_trove.xml:31(td) ./doc/common/tables/heat-clients_cinder.xml:31(td) ./doc/common/tables/heat-clients_neutron.xml:31(td) ./doc/common/tables/heat-clients_keystone.xml:31(td)
-msgid "(StrOpt) Type of endpoint in Identity service catalog to use for communication with the OpenStack service."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_nova.xml:34(td) ./doc/common/tables/glance-auth_token.xml:101(td) ./doc/common/tables/heat-clients.xml:41(td) ./doc/common/tables/nova-auth_token.xml:94(td) ./doc/common/tables/cinder-auth_token.xml:101(td) ./doc/common/tables/heat-clients_heat.xml:34(td) ./doc/common/tables/heat-clients_swift.xml:34(td) ./doc/common/tables/trove-auth_token.xml:101(td) ./doc/common/tables/heat-clients_ceilometer.xml:34(td) ./doc/common/tables/heat-clients_trove.xml:34(td) ./doc/common/tables/heat-clients_cinder.xml:34(td) ./doc/common/tables/keystone-auth_token.xml:101(td) ./doc/common/tables/ceilometer-auth.xml:101(td) ./doc/common/tables/ceilometer-auth.xml:136(td) ./doc/common/tables/heat-auth_token.xml:101(td) ./doc/common/tables/heat-clients_neutron.xml:34(td) ./doc/common/tables/neutron-auth_token.xml:101(td) ./doc/common/tables/heat-clients_keystone.xml:34(td)
-msgid "insecure = False"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_nova.xml:35(td) ./doc/common/tables/heat-clients.xml:42(td) ./doc/common/tables/heat-clients_heat.xml:35(td) ./doc/common/tables/heat-clients_swift.xml:35(td) ./doc/common/tables/heat-clients_ceilometer.xml:35(td) ./doc/common/tables/heat-clients_trove.xml:35(td) ./doc/common/tables/heat-clients_cinder.xml:35(td) ./doc/common/tables/heat-clients_neutron.xml:35(td) ./doc/common/tables/heat-clients_keystone.xml:35(td)
-msgid "(BoolOpt) If set, then the server's certificate will not be verified."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_nova.xml:39(td) ./doc/common/tables/heat-clients.xml:46(td) ./doc/common/tables/heat-clients_heat.xml:39(td) ./doc/common/tables/heat-clients_swift.xml:39(td) ./doc/common/tables/heat-clients_ceilometer.xml:39(td) ./doc/common/tables/heat-clients_trove.xml:39(td) ./doc/common/tables/heat-clients_cinder.xml:39(td) ./doc/common/tables/heat-clients_neutron.xml:39(td) ./doc/common/tables/heat-clients_keystone.xml:39(td)
-msgid "(StrOpt) Optional PEM-formatted file that contains the private key."
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-filter-recon.xml:7(literal) ./doc/common/tables/swift-object-server-filter-recon.xml:7(literal) ./doc/common/tables/swift-container-server-filter-recon.xml:7(literal)
-msgid "[filter:recon]"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-filter-recon.xml:7(literal) ./doc/common/tables/swift-account-server-app-account-server.xml:7(literal) ./doc/common/tables/swift-account-server-filter-healthcheck.xml:7(literal) ./doc/common/tables/swift-account-server-account-auditor.xml:7(literal) ./doc/common/tables/swift-account-server-DEFAULT.xml:7(literal) ./doc/common/tables/swift-account-server-account-replicator.xml:7(literal) ./doc/common/tables/swift-account-server-pipeline-main.xml:7(literal) ./doc/common/tables/swift-account-server-account-reaper.xml:7(literal)
-msgid "account-server.conf-sample"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-filter-recon.xml:18(td) ./doc/common/tables/swift-object-server-filter-recon.xml:18(td) ./doc/common/tables/swift-container-server-filter-recon.xml:18(td)
-msgid "use = egg:swift#recon"
-msgstr ""
-
-#: ./doc/common/tables/cinder-huawei.xml:8(caption)
-msgid "Description of configuration options for huawei"
-msgstr ""
-
-#: ./doc/common/tables/cinder-huawei.xml:22(td)
-msgid "cinder_huawei_conf_file = /etc/cinder/cinder_huawei_conf.xml"
-msgstr ""
-
-#: ./doc/common/tables/cinder-huawei.xml:23(td)
-msgid "(StrOpt) config data for cinder huawei plugin"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:8(caption)
-msgid "Description of configuration options for netapp_eseries_iscsi"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:22(td)
-msgid "netapp_controller_ips = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:23(td)
-msgid "(StrOpt) This option is only utilized when the storage family is configured to eseries. This option is used to restrict provisioning to the specified controllers. Specify the value of this option to be a comma separated list of controller hostnames or IP addresses to be used for provisioning."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:26(td) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:22(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:22(td) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:26(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:30(td)
-msgid "netapp_login = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:27(td) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:23(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:23(td) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:27(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:31(td)
-msgid "(StrOpt) Administrative user account name used to access the storage system or proxy server."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:30(td) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:26(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:26(td) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:30(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:34(td)
-msgid "netapp_password = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:31(td) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:27(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:27(td) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:31(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:35(td)
-msgid "(StrOpt) Password for the administrative user account specified in the netapp_login option."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:34(td)
-msgid "netapp_sa_password = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:35(td)
-msgid "(StrOpt) Password for the NetApp E-Series storage array."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:38(td) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:30(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:30(td) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:34(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:38(td)
-msgid "netapp_server_hostname = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:39(td) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:31(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:31(td) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:35(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:39(td)
-msgid "(StrOpt) The hostname (or IP address) for the storage system or proxy server."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:42(td) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:34(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:34(td) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:38(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:42(td)
-msgid "netapp_server_port = 80"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:43(td) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:35(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:35(td) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:39(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:43(td)
-msgid "(IntOpt) The TCP port to use for communication with the storage system or proxy server. Traditionally, port 80 is used for HTTP and port 443 is used for HTTPS; however, this value should be changed if an alternate port has been configured on the storage system or proxy server."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:46(td) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:42(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:42(td) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:42(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:46(td)
-msgid "netapp_storage_family = ontap_cluster"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:47(td) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:43(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:43(td) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:43(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:47(td)
-msgid "(StrOpt) The storage family type used on the storage system; valid values are ontap_7mode for using Data ONTAP operating in 7-Mode, ontap_cluster for using clustered Data ONTAP, or eseries for using E-Series."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:50(td)
-msgid "netapp_storage_pools = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:51(td)
-msgid "(StrOpt) This option is used to restrict provisioning to the specified storage pools. Only dynamic disk pools are currently supported. Specify the value of this option to be a comma separated list of disk pool names to be used for provisioning."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:54(td) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:50(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:50(td) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:50(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:54(td)
-msgid "netapp_transport_type = http"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:55(td) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:51(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:51(td) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:51(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:55(td)
-msgid "(StrOpt) The transport protocol used when communicating with the storage system or proxy server. Valid values are http or https."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:58(td)
-msgid "netapp_webservice_path = /devmgr/v2"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml:59(td)
-msgid "(StrOpt) This option is used to specify the path to the E-Series proxy application on a proxy server. The value is combined with the value of the netapp_transport_type, netapp_server_hostname, and netapp_server_port options to create the URL used by the driver to connect to the proxy application."
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml:7(literal)
-msgid "[container-replicator]"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml:18(td)
-msgid "log_name = container-replicator"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml:30(td) ./doc/common/tables/swift-object-server-object-replicator.xml:30(td) ./doc/common/tables/swift-account-server-account-replicator.xml:30(td)
-msgid "vm_test_mode = no"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml:30(td) ./doc/common/tables/swift-object-server-object-replicator.xml:30(td) ./doc/common/tables/swift-account-server-account-replicator.xml:30(td)
-msgid "Indicates that you are using a VM environment"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml:33(td) ./doc/common/tables/swift-account-server-account-replicator.xml:33(td)
-msgid "per_diff = 1000"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml:33(td) ./doc/common/tables/swift-account-server-account-replicator.xml:33(td)
-msgid "Limit number of items to get per diff"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml:36(td) ./doc/common/tables/swift-account-server-account-replicator.xml:36(td)
-msgid "max_diffs = 100"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml:36(td) ./doc/common/tables/swift-account-server-account-replicator.xml:36(td)
-msgid "Caps how long the replicator spends trying to sync a database per pass"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml:39(td) ./doc/common/tables/swift-account-server-account-replicator.xml:39(td)
-msgid "concurrency = 8"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml:42(td) ./doc/common/tables/swift-account-server-account-replicator.xml:42(td)
-msgid "interval = 30"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml:45(td) ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:48(td) ./doc/common/tables/swift-account-server-account-replicator.xml:51(td) ./doc/common/tables/swift-account-server-account-reaper.xml:36(td)
-msgid "node_timeout = 10"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml:51(td) ./doc/common/tables/swift-object-server-object-replicator.xml:66(td) ./doc/common/tables/swift-account-server-account-replicator.xml:57(td)
-msgid "reclaim_age = 604800"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml:51(td) ./doc/common/tables/swift-object-server-object-replicator.xml:66(td) ./doc/common/tables/swift-account-server-account-replicator.xml:57(td)
-msgid "Time elapsed in seconds before an object can be reclaimed"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml:54(td) ./doc/common/tables/swift-object-server-object-replicator.xml:36(td) ./doc/common/tables/swift-account-server-account-replicator.xml:60(td)
-msgid "run_pause = 30"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml:54(td) ./doc/common/tables/swift-object-server-object-replicator.xml:36(td) ./doc/common/tables/swift-account-server-account-replicator.xml:60(td)
-msgid "Time in seconds to wait between replication passes"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml:8(caption)
-msgid "Description of configuration options for glance"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml:22(td) ./doc/common/tables/cinder-images.xml:22(td)
-msgid "allowed_direct_url_schemes ="
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml:23(td)
-msgid "(ListOpt) A list of url scheme that can be downloaded directly via the direct_url. Currently supported schemes: [file]."
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml:26(td) ./doc/common/tables/cinder-images.xml:26(td)
-msgid "glance_api_insecure = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml:27(td) ./doc/common/tables/cinder-images.xml:27(td)
-msgid "(BoolOpt) Allow to perform insecure SSL (https) requests to glance"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml:30(td) ./doc/common/tables/cinder-images.xml:30(td)
-msgid "glance_api_servers = $glance_host:$glance_port"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml:31(td)
-msgid "(ListOpt) A list of the glance api servers available to nova. Prefix with https:// for ssl-based glance api servers. ([hostname|ip]:port)"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml:34(td) ./doc/common/tables/cinder-images.xml:42(td)
-msgid "glance_host = $my_ip"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml:35(td)
-msgid "(StrOpt) Default glance hostname or IP address"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml:38(td) ./doc/common/tables/cinder-images.xml:46(td)
-msgid "glance_num_retries = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml:39(td)
-msgid "(IntOpt) Number of retries when downloading an image from glance"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml:42(td) ./doc/common/tables/cinder-images.xml:50(td)
-msgid "glance_port = 9292"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml:43(td)
-msgid "(IntOpt) Default glance port"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml:46(td)
-msgid "glance_protocol = http"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml:47(td)
-msgid "(StrOpt) Default protocol to use when connecting to glance. Set to https for SSL."
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml:50(td)
-msgid "osapi_glance_link_prefix = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml:51(td)
-msgid "(StrOpt) Base URL that will be presented to users in links to glance resources"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml:54(th)
-msgid "[image_file_url]"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml:57(td)
-msgid "filesystems ="
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml:58(td)
-msgid "(ListOpt) List of file systems that are configured in this file in the image_file_url:&lt;list entry name&gt; sections"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml:8(caption)
-msgid "Description of configuration options for dhcp_agent"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml:22(td) ./doc/common/tables/nova-network.xml:74(td)
-msgid "dnsmasq_config_file ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml:23(td) ./doc/common/tables/nova-network.xml:75(td)
-msgid "(StrOpt) Override the default dnsmasq settings with this file"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml:26(td)
-msgid "dnsmasq_dns_servers = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml:27(td)
-msgid "(ListOpt) Comma-separated list of the DNS servers which will be used as forwarders."
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml:30(td)
-msgid "dnsmasq_lease_max = 16777216"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml:31(td)
-msgid "(IntOpt) Limit number of leases to prevent a denial-of-service."
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml:34(td)
-msgid "enable_isolated_metadata = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml:35(td)
-msgid "(BoolOpt) Support Metadata requests on isolated networks."
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml:38(td)
-msgid "enable_metadata_network = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml:39(td)
-msgid "(BoolOpt) Allows for serving metadata requests from a dedicated network. Requires enable_isolated_metadata = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml:42(td)
-msgid "num_sync_threads = 4"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml:43(td)
-msgid "(IntOpt) Number of threads to use during sync process."
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml:46(td)
-msgid "resync_interval = 5"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml:47(td)
-msgid "(IntOpt) Interval to resync."
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml:50(td)
-msgid "use_namespaces = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml:51(td)
-msgid "(BoolOpt) Allow overlapping IP."
+#: ./doc/common/tables/glance-policy.xml:27(td)
+msgid "(StrOpt) The location of the policy file."
 msgstr ""
 
 #: ./doc/common/tables/nova-neutron.xml:8(caption)
@@ -20875,10 +25095,6 @@ msgstr ""
 msgid "neutron_ovs_bridge = br-int"
 msgstr ""
 
-#: ./doc/common/tables/nova-neutron.xml:67(td) ./doc/common/tables/nova-xen.xml:157(td)
-msgid "(StrOpt) Name of Integration Bridge used by Open vSwitch"
-msgstr ""
-
 #: ./doc/common/tables/nova-neutron.xml:70(td)
 msgid "neutron_region_name = None"
 msgstr ""
@@ -20911,648 +25127,88 @@ msgstr ""
 msgid "(BoolOpt) Set flag to indicate Neutron will proxy metadata requests and resolve instance ids."
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml:8(caption)
-msgid "Description of configuration options for backups_ceph"
+#: ./doc/common/tables/cinder-backups.xml:8(caption)
+msgid "Description of configuration options for backups"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml:22(td)
-msgid "backup_ceph_chunk_size = 134217728"
+#: ./doc/common/tables/cinder-backups.xml:22(td)
+msgid "backup_api_class = cinder.backup.api.API"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml:23(td)
-msgid "(IntOpt) The chunk size, in bytes, that a backup is broken into before transfer to the Ceph object store."
+#: ./doc/common/tables/cinder-backups.xml:23(td)
+msgid "(StrOpt) The full class name of the volume backup API class"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml:26(td)
-msgid "backup_ceph_conf = /etc/ceph/ceph.conf"
+#: ./doc/common/tables/cinder-backups.xml:26(td)
+msgid "backup_compression_algorithm = zlib"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml:27(td)
-msgid "(StrOpt) Ceph configuration file to use."
+#: ./doc/common/tables/cinder-backups.xml:27(td)
+msgid "(StrOpt) Compression algorithm (None to disable)"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml:30(td)
-msgid "backup_ceph_pool = backups"
+#: ./doc/common/tables/cinder-backups.xml:30(td)
+msgid "backup_driver = cinder.backup.drivers.swift"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml:31(td)
-msgid "(StrOpt) The Ceph pool where volume backups are stored."
+#: ./doc/common/tables/cinder-backups.xml:31(td)
+msgid "(StrOpt) Driver to use for backups."
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml:34(td)
-msgid "backup_ceph_stripe_count = 0"
+#: ./doc/common/tables/cinder-backups.xml:34(td)
+msgid "backup_manager = cinder.backup.manager.BackupManager"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml:35(td)
-msgid "(IntOpt) RBD stripe count to use when creating a backup image."
+#: ./doc/common/tables/cinder-backups.xml:35(td)
+msgid "(StrOpt) full class name for the Manager for volume backup"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml:38(td)
-msgid "backup_ceph_stripe_unit = 0"
+#: ./doc/common/tables/cinder-backups.xml:38(td)
+msgid "backup_metadata_version = 1"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml:39(td)
-msgid "(IntOpt) RBD stripe unit to use when creating a backup image."
+#: ./doc/common/tables/cinder-backups.xml:39(td)
+msgid "(IntOpt) Backup metadata version to be used when backing up volume metadata. If this number is bumped, make sure the service doing the restore supports the new version."
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml:42(td)
-msgid "backup_ceph_user = cinder"
+#: ./doc/common/tables/cinder-backups.xml:42(td)
+msgid "backup_name_template = backup-%s"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml:43(td)
-msgid "(StrOpt) The Ceph user to connect with. Default here is to use the same user as for Cinder volumes. If not using cephx this should be set to None."
+#: ./doc/common/tables/cinder-backups.xml:43(td)
+msgid "(StrOpt) Template string to be used to generate backup names"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml:46(td)
-msgid "restore_discard_excess_bytes = True"
+#: ./doc/common/tables/cinder-backups.xml:46(td)
+msgid "backup_topic = cinder-backup"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml:47(td)
-msgid "(BoolOpt) If True, always discard excess bytes when restoring volumes i.e. pad with zeroes."
+#: ./doc/common/tables/cinder-backups.xml:47(td)
+msgid "(StrOpt) the topic volume backup nodes listen on"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml:7(literal)
-msgid "[filter:name_check]"
+#: ./doc/common/tables/cinder-backups.xml:50(td) ./doc/common/tables/nova-api.xml:90(td)
+msgid "snapshot_name_template = snapshot-%s"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml:18(td)
-msgid "use = egg:swift#name_check"
+#: ./doc/common/tables/cinder-backups.xml:51(td) ./doc/common/tables/nova-api.xml:91(td)
+msgid "(StrOpt) Template string to be used to generate snapshot names"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml:21(td)
-msgid "forbidden_chars = '\"`&lt;&gt;"
+#: ./doc/common/tables/cinder-backups.xml:54(td)
+msgid "snapshot_same_host = True"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml:21(td)
-msgid "Characters that are not allowed in a name"
+#: ./doc/common/tables/cinder-backups.xml:55(td)
+msgid "(BoolOpt) Create volume from snapshot at the host where snapshot resides"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml:24(td)
-msgid "maximum_length = 255"
+#: ./doc/common/tables/cinder-keymgr.xml:22(td)
+msgid "api_class = cinder.keymgr.conf_key_mgr.ConfKeyManager"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml:24(td)
-msgid "Maximum length of a name"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml:27(td)
-msgid "forbidden_regexp = /\\./|/\\.\\./|/\\.$|/\\.\\.$"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml:27(td)
-msgid "Substrings to forbid, using regular expression syntax"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml:8(caption) ./doc/common/tables/neutron-metadata.xml:8(caption)
-msgid "Description of configuration options for metadata"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml:22(td)
-msgid "metadata_host = $my_ip"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml:23(td)
-msgid "(StrOpt) The IP address for the metadata API server"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml:26(td)
-msgid "metadata_listen = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml:27(td)
-msgid "(StrOpt) The IP address on which the metadata API will listen."
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml:30(td)
-msgid "metadata_listen_port = 8775"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml:31(td)
-msgid "(IntOpt) The port on which the metadata API will listen."
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml:34(td)
-msgid "metadata_manager = nova.api.manager.MetadataManager"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml:35(td)
-msgid "(StrOpt) OpenStack metadata service manager"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml:38(td)
-msgid "metadata_port = 8775"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml:39(td)
-msgid "(IntOpt) The port for the metadata API port"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml:42(td)
-msgid "metadata_workers = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml:43(td)
-msgid "(IntOpt) Number of workers for metadata service. The default will be the number of CPUs available."
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml:46(td)
-msgid "vendordata_driver = nova.api.metadata.vendordata_json.JsonFileVendorData"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml:47(td)
-msgid "(StrOpt) Driver to use for vendor data"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml:50(td)
-msgid "vendordata_jsonfile_path = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml:51(td)
-msgid "(StrOpt) File to load json formatted vendor data from"
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml:8(caption) ./doc/common/tables/nova-s3.xml:8(caption)
-msgid "Description of configuration options for s3"
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml:22(td)
-msgid "s3_store_access_key = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml:23(td)
-msgid "(StrOpt) The S3 query token access key."
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml:26(td)
-msgid "s3_store_bucket = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml:27(td)
-msgid "(StrOpt) The S3 bucket to be used to store the Glance data."
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml:30(td)
-msgid "s3_store_bucket_url_format = subdomain"
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml:31(td)
-msgid "(StrOpt) The S3 calling format used to determine the bucket. Either subdomain or path can be used."
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml:34(td)
-msgid "s3_store_create_bucket_on_put = False"
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml:35(td)
-msgid "(BoolOpt) A boolean to determine if the S3 bucket should be created on upload if it does not exist or if an error should be returned to the user."
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml:38(td)
-msgid "s3_store_host = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml:39(td)
-msgid "(StrOpt) The host where the S3 server is listening."
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml:42(td)
-msgid "s3_store_object_buffer_dir = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml:43(td)
-msgid "(StrOpt) The local directory where uploads will be staged before they are transferred into S3."
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml:46(td)
-msgid "s3_store_secret_key = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml:47(td)
-msgid "(StrOpt) The S3 query token secret key."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:8(caption) ./doc/common/tables/nova-auth_token.xml:8(caption) ./doc/common/tables/cinder-auth_token.xml:8(caption) ./doc/common/tables/trove-auth_token.xml:8(caption) ./doc/common/tables/keystone-auth_token.xml:8(caption) ./doc/common/tables/heat-auth_token.xml:8(caption) ./doc/common/tables/neutron-auth_token.xml:8(caption)
-msgid "Description of configuration options for auth_token"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:22(td) ./doc/common/tables/glance-auth_token.xml:117(td) ./doc/common/tables/nova-common.xml:50(td) ./doc/common/tables/nova-auth_token.xml:110(td) ./doc/common/tables/cinder-auth_token.xml:22(td) ./doc/common/tables/cinder-auth_token.xml:117(td) ./doc/common/tables/trove-auth_token.xml:22(td) ./doc/common/tables/trove-auth_token.xml:117(td) ./doc/common/tables/keystone-auth_token.xml:22(td) ./doc/common/tables/keystone-auth_token.xml:117(td) ./doc/common/tables/ceilometer-common.xml:38(td) ./doc/common/tables/ceilometer-auth.xml:117(td) ./doc/common/tables/heat-auth_token.xml:22(td) ./doc/common/tables/heat-auth_token.xml:117(td) ./doc/common/tables/neutron-auth_token.xml:22(td) ./doc/common/tables/neutron-auth_token.xml:117(td)
-msgid "memcached_servers = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:23(td) ./doc/common/tables/nova-common.xml:51(td) ./doc/common/tables/cinder-auth_token.xml:23(td) ./doc/common/tables/trove-auth_token.xml:23(td) ./doc/common/tables/keystone-auth_token.xml:23(td) ./doc/common/tables/ceilometer-common.xml:39(td) ./doc/common/tables/heat-auth_token.xml:23(td) ./doc/common/tables/neutron-auth_token.xml:23(td)
-msgid "(ListOpt) Memcached servers or None for in process cache."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:26(th) ./doc/common/tables/nova-auth_token.xml:19(th) ./doc/common/tables/cinder-auth_token.xml:26(th) ./doc/common/tables/trove-auth_token.xml:26(th) ./doc/common/tables/keystone-auth_token.xml:26(th) ./doc/common/tables/ceilometer-auth.xml:26(th) ./doc/common/tables/heat-auth_token.xml:26(th) ./doc/common/tables/neutron-auth_token.xml:26(th)
-msgid "[keystone_authtoken]"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:29(td) ./doc/common/tables/neutron-common.xml:22(td) ./doc/common/tables/neutron-common.xml:192(td) ./doc/common/tables/neutron-common.xml:219(td) ./doc/common/tables/nova-auth_token.xml:22(td) ./doc/common/tables/cinder-auth_token.xml:29(td) ./doc/common/tables/trove-auth_token.xml:29(td) ./doc/common/tables/glance-registry.xml:22(td) ./doc/common/tables/keystone-auth_token.xml:29(td) ./doc/common/tables/ceilometer-auth.xml:29(td) ./doc/common/tables/heat-auth_token.xml:29(td) ./doc/common/tables/neutron-embrane_lb.xml:22(td) ./doc/common/tables/neutron-auth_token.xml:29(td)
-msgid "admin_password = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:30(td) ./doc/common/tables/nova-auth_token.xml:23(td) ./doc/common/tables/cinder-auth_token.xml:30(td) ./doc/common/tables/trove-auth_token.xml:30(td) ./doc/common/tables/keystone-auth_token.xml:30(td) ./doc/common/tables/ceilometer-auth.xml:30(td) ./doc/common/tables/heat-auth_token.xml:30(td) ./doc/common/tables/neutron-auth_token.xml:30(td)
-msgid "(StrOpt) Keystone account password"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:33(td) ./doc/common/tables/nova-auth_token.xml:26(td) ./doc/common/tables/cinder-auth_token.xml:33(td) ./doc/common/tables/trove-auth_token.xml:33(td) ./doc/common/tables/keystone-auth_token.xml:33(td) ./doc/common/tables/ceilometer-auth.xml:33(td) ./doc/common/tables/heat-auth_token.xml:33(td) ./doc/common/tables/neutron-auth_token.xml:33(td)
-msgid "admin_tenant_name = admin"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:34(td) ./doc/common/tables/nova-auth_token.xml:27(td) ./doc/common/tables/cinder-auth_token.xml:34(td) ./doc/common/tables/trove-auth_token.xml:34(td) ./doc/common/tables/keystone-auth_token.xml:34(td) ./doc/common/tables/ceilometer-auth.xml:34(td) ./doc/common/tables/heat-auth_token.xml:34(td) ./doc/common/tables/neutron-auth_token.xml:34(td)
-msgid "(StrOpt) Keystone service account tenant name to validate user tokens"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:37(td) ./doc/common/tables/nova-auth_token.xml:30(td) ./doc/common/tables/cinder-auth_token.xml:37(td) ./doc/common/tables/trove-auth_token.xml:37(td) ./doc/common/tables/keystone-auth_token.xml:37(td) ./doc/common/tables/ceilometer-auth.xml:37(td) ./doc/common/tables/heat-auth_token.xml:37(td) ./doc/common/tables/neutron-auth_token.xml:37(td)
-msgid "admin_token = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:38(td) ./doc/common/tables/nova-auth_token.xml:31(td) ./doc/common/tables/cinder-auth_token.xml:38(td) ./doc/common/tables/trove-auth_token.xml:38(td) ./doc/common/tables/keystone-auth_token.xml:38(td) ./doc/common/tables/ceilometer-auth.xml:38(td) ./doc/common/tables/heat-auth_token.xml:38(td) ./doc/common/tables/neutron-auth_token.xml:38(td)
-msgid "(StrOpt) Single shared secret with the Keystone configuration used for bootstrapping a Keystone installation, or otherwise bypassing the normal authentication process."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:41(td) ./doc/common/tables/neutron-common.xml:30(td) ./doc/common/tables/neutron-common.xml:200(td) ./doc/common/tables/nova-auth_token.xml:34(td) ./doc/common/tables/cinder-auth_token.xml:41(td) ./doc/common/tables/trove-auth_token.xml:41(td) ./doc/common/tables/glance-registry.xml:30(td) ./doc/common/tables/keystone-auth_token.xml:41(td) ./doc/common/tables/ceilometer-auth.xml:41(td) ./doc/common/tables/heat-auth_token.xml:41(td) ./doc/common/tables/neutron-auth_token.xml:41(td)
-msgid "admin_user = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:42(td) ./doc/common/tables/nova-auth_token.xml:35(td) ./doc/common/tables/cinder-auth_token.xml:42(td) ./doc/common/tables/trove-auth_token.xml:42(td) ./doc/common/tables/keystone-auth_token.xml:42(td) ./doc/common/tables/ceilometer-auth.xml:42(td) ./doc/common/tables/heat-auth_token.xml:42(td) ./doc/common/tables/neutron-auth_token.xml:42(td)
-msgid "(StrOpt) Keystone account username"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:45(td) ./doc/common/tables/nova-auth_token.xml:38(td) ./doc/common/tables/cinder-auth_token.xml:45(td) ./doc/common/tables/trove-auth_token.xml:45(td) ./doc/common/tables/keystone-auth_token.xml:45(td) ./doc/common/tables/ceilometer-auth.xml:45(td) ./doc/common/tables/heat-auth_token.xml:45(td) ./doc/common/tables/neutron-auth_token.xml:45(td)
-msgid "auth_admin_prefix ="
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:46(td) ./doc/common/tables/nova-auth_token.xml:39(td) ./doc/common/tables/cinder-auth_token.xml:46(td) ./doc/common/tables/trove-auth_token.xml:46(td) ./doc/common/tables/keystone-auth_token.xml:46(td) ./doc/common/tables/ceilometer-auth.xml:46(td) ./doc/common/tables/heat-auth_token.xml:46(td) ./doc/common/tables/neutron-auth_token.xml:46(td)
-msgid "(StrOpt) Prefix to prepend at the beginning of the path"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:49(td) ./doc/common/tables/nova-auth_token.xml:42(td) ./doc/common/tables/cinder-auth_token.xml:49(td) ./doc/common/tables/trove-auth_token.xml:49(td) ./doc/common/tables/keystone-auth_token.xml:49(td) ./doc/common/tables/ceilometer-auth.xml:49(td) ./doc/common/tables/heat-auth_token.xml:49(td) ./doc/common/tables/neutron-auth_token.xml:49(td)
-msgid "auth_host = 127.0.0.1"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:50(td) ./doc/common/tables/nova-auth_token.xml:43(td) ./doc/common/tables/cinder-auth_token.xml:50(td) ./doc/common/tables/trove-auth_token.xml:50(td) ./doc/common/tables/keystone-auth_token.xml:50(td) ./doc/common/tables/ceilometer-auth.xml:50(td) ./doc/common/tables/heat-auth_token.xml:50(td) ./doc/common/tables/neutron-auth_token.xml:50(td)
-msgid "(StrOpt) Host providing the admin Identity API endpoint"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:53(td) ./doc/common/tables/nova-auth_token.xml:46(td) ./doc/common/tables/cinder-auth_token.xml:53(td) ./doc/common/tables/trove-auth_token.xml:53(td) ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:21(td) ./doc/common/tables/keystone-auth_token.xml:53(td) ./doc/common/tables/ceilometer-auth.xml:53(td) ./doc/common/tables/heat-auth_token.xml:53(td) ./doc/common/tables/neutron-auth_token.xml:53(td)
-msgid "auth_port = 35357"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:54(td) ./doc/common/tables/nova-auth_token.xml:47(td) ./doc/common/tables/cinder-auth_token.xml:54(td) ./doc/common/tables/trove-auth_token.xml:54(td) ./doc/common/tables/keystone-auth_token.xml:54(td) ./doc/common/tables/ceilometer-auth.xml:54(td) ./doc/common/tables/heat-auth_token.xml:54(td) ./doc/common/tables/neutron-auth_token.xml:54(td)
-msgid "(IntOpt) Port of the admin Identity API endpoint"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:57(td) ./doc/common/tables/nova-auth_token.xml:50(td) ./doc/common/tables/cinder-auth_token.xml:57(td) ./doc/common/tables/trove-auth_token.xml:57(td) ./doc/common/tables/keystone-auth_token.xml:57(td) ./doc/common/tables/ceilometer-auth.xml:57(td) ./doc/common/tables/heat-auth_token.xml:57(td) ./doc/common/tables/neutron-auth_token.xml:57(td)
-msgid "auth_protocol = https"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:58(td) ./doc/common/tables/nova-auth_token.xml:51(td) ./doc/common/tables/cinder-auth_token.xml:58(td) ./doc/common/tables/trove-auth_token.xml:58(td) ./doc/common/tables/keystone-auth_token.xml:58(td) ./doc/common/tables/ceilometer-auth.xml:58(td) ./doc/common/tables/heat-auth_token.xml:58(td) ./doc/common/tables/neutron-auth_token.xml:58(td)
-msgid "(StrOpt) Protocol of the admin Identity API endpoint(http or https)"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:61(td) ./doc/common/tables/nova-auth_token.xml:54(td) ./doc/common/tables/cinder-auth_token.xml:61(td) ./doc/common/tables/trove-auth_token.xml:61(td) ./doc/common/tables/heat-api.xml:92(td) ./doc/common/tables/keystone-auth_token.xml:61(td) ./doc/common/tables/ceilometer-auth.xml:61(td) ./doc/common/tables/heat-auth_token.xml:61(td) ./doc/common/tables/neutron-auth_token.xml:61(td)
-msgid "auth_uri = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:62(td) ./doc/common/tables/nova-auth_token.xml:55(td) ./doc/common/tables/cinder-auth_token.xml:62(td) ./doc/common/tables/trove-auth_token.xml:62(td) ./doc/common/tables/keystone-auth_token.xml:62(td) ./doc/common/tables/ceilometer-auth.xml:62(td) ./doc/common/tables/heat-auth_token.xml:62(td) ./doc/common/tables/neutron-auth_token.xml:62(td)
-msgid "(StrOpt) Complete public Identity API endpoint"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:65(td) ./doc/common/tables/nova-auth_token.xml:58(td) ./doc/common/tables/cinder-auth_token.xml:65(td) ./doc/common/tables/trove-auth_token.xml:65(td) ./doc/common/tables/keystone-auth_token.xml:65(td) ./doc/common/tables/ceilometer-auth.xml:65(td) ./doc/common/tables/heat-auth_token.xml:65(td) ./doc/common/tables/neutron-auth_token.xml:65(td)
-msgid "auth_version = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:66(td) ./doc/common/tables/nova-auth_token.xml:59(td) ./doc/common/tables/cinder-auth_token.xml:66(td) ./doc/common/tables/trove-auth_token.xml:66(td) ./doc/common/tables/keystone-auth_token.xml:66(td) ./doc/common/tables/ceilometer-auth.xml:66(td) ./doc/common/tables/heat-auth_token.xml:66(td) ./doc/common/tables/neutron-auth_token.xml:66(td)
-msgid "(StrOpt) API version of the admin Identity API endpoint"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:69(td) ./doc/common/tables/nova-auth_token.xml:62(td) ./doc/common/tables/cinder-auth_token.xml:69(td) ./doc/common/tables/trove-auth_token.xml:69(td) ./doc/common/tables/keystone-auth_token.xml:69(td) ./doc/common/tables/ceilometer-auth.xml:69(td) ./doc/common/tables/heat-auth_token.xml:69(td) ./doc/common/tables/neutron-auth_token.xml:69(td)
-msgid "cache = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:70(td) ./doc/common/tables/nova-auth_token.xml:63(td) ./doc/common/tables/cinder-auth_token.xml:70(td) ./doc/common/tables/trove-auth_token.xml:70(td) ./doc/common/tables/keystone-auth_token.xml:70(td) ./doc/common/tables/ceilometer-auth.xml:70(td) ./doc/common/tables/heat-auth_token.xml:70(td) ./doc/common/tables/neutron-auth_token.xml:70(td)
-msgid "(StrOpt) Env key for the swift cache"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:73(td) ./doc/common/tables/nova-auth_token.xml:66(td) ./doc/common/tables/cinder-auth_token.xml:73(td) ./doc/common/tables/trove-auth_token.xml:73(td) ./doc/common/tables/keystone-auth_token.xml:73(td) ./doc/common/tables/ceilometer-auth.xml:73(td) ./doc/common/tables/heat-auth_token.xml:73(td) ./doc/common/tables/neutron-auth_token.xml:73(td)
-msgid "cafile = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:74(td) ./doc/common/tables/nova-auth_token.xml:67(td) ./doc/common/tables/cinder-auth_token.xml:74(td) ./doc/common/tables/trove-auth_token.xml:74(td) ./doc/common/tables/keystone-auth_token.xml:74(td) ./doc/common/tables/ceilometer-auth.xml:74(td) ./doc/common/tables/heat-auth_token.xml:74(td) ./doc/common/tables/neutron-auth_token.xml:74(td)
-msgid "(StrOpt) A PEM encoded Certificate Authority to use when verifying HTTPs connections. Defaults to system CAs."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:77(td) ./doc/common/tables/nova-auth_token.xml:70(td) ./doc/common/tables/cinder-auth_token.xml:77(td) ./doc/common/tables/trove-auth_token.xml:77(td) ./doc/common/tables/keystone-auth_token.xml:77(td) ./doc/common/tables/ceilometer-auth.xml:77(td) ./doc/common/tables/heat-auth_token.xml:77(td) ./doc/common/tables/neutron-auth_token.xml:77(td)
-msgid "certfile = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:78(td) ./doc/common/tables/glance-auth_token.xml:106(td) ./doc/common/tables/nova-auth_token.xml:71(td) ./doc/common/tables/nova-auth_token.xml:99(td) ./doc/common/tables/cinder-auth_token.xml:78(td) ./doc/common/tables/cinder-auth_token.xml:106(td) ./doc/common/tables/trove-auth_token.xml:78(td) ./doc/common/tables/trove-auth_token.xml:106(td) ./doc/common/tables/keystone-auth_token.xml:78(td) ./doc/common/tables/keystone-auth_token.xml:106(td) ./doc/common/tables/ceilometer-auth.xml:78(td) ./doc/common/tables/ceilometer-auth.xml:106(td) ./doc/common/tables/heat-auth_token.xml:78(td) ./doc/common/tables/heat-auth_token.xml:106(td) ./doc/common/tables/neutron-auth_token.xml:78(td) ./doc/common/tables/neutron-auth_token.xml:106(td)
-msgid "(StrOpt) Required if Keystone server requires client certificate"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:81(td) ./doc/common/tables/nova-auth_token.xml:74(td) ./doc/common/tables/cinder-auth_token.xml:81(td) ./doc/common/tables/trove-auth_token.xml:81(td) ./doc/common/tables/keystone-auth_token.xml:81(td) ./doc/common/tables/ceilometer-auth.xml:81(td) ./doc/common/tables/heat-auth_token.xml:81(td) ./doc/common/tables/neutron-auth_token.xml:81(td)
-msgid "delay_auth_decision = False"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:82(td) ./doc/common/tables/nova-auth_token.xml:75(td) ./doc/common/tables/cinder-auth_token.xml:82(td) ./doc/common/tables/trove-auth_token.xml:82(td) ./doc/common/tables/keystone-auth_token.xml:82(td) ./doc/common/tables/ceilometer-auth.xml:82(td) ./doc/common/tables/heat-auth_token.xml:82(td) ./doc/common/tables/neutron-auth_token.xml:82(td)
-msgid "(BoolOpt) Do not handle authorization requests within the middleware, but delegate the authorization decision to downstream WSGI components"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:85(td) ./doc/common/tables/nova-auth_token.xml:78(td) ./doc/common/tables/cinder-auth_token.xml:85(td) ./doc/common/tables/trove-auth_token.xml:85(td) ./doc/common/tables/keystone-token.xml:38(td) ./doc/common/tables/keystone-auth_token.xml:85(td) ./doc/common/tables/ceilometer-auth.xml:85(td) ./doc/common/tables/heat-auth_token.xml:85(td) ./doc/common/tables/neutron-auth_token.xml:85(td)
-msgid "enforce_token_bind = permissive"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:86(td) ./doc/common/tables/nova-auth_token.xml:79(td) ./doc/common/tables/cinder-auth_token.xml:86(td) ./doc/common/tables/trove-auth_token.xml:86(td) ./doc/common/tables/keystone-auth_token.xml:86(td) ./doc/common/tables/ceilometer-auth.xml:86(td) ./doc/common/tables/heat-auth_token.xml:86(td) ./doc/common/tables/neutron-auth_token.xml:86(td)
-msgid "(StrOpt) Used to control the use and type of token binding. Can be set to: \"disabled\" to not check token binding. \"permissive\" (default) to validate binding information if the bind type is of a form known to the server and ignore it if not. \"strict\" like \"permissive\" but if the bind type is unknown the token will be rejected. \"required\" any form of token binding is needed to be allowed. Finally the name of a binding method that must be present in tokens."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:89(td) ./doc/common/tables/nova-auth_token.xml:82(td) ./doc/common/tables/cinder-auth_token.xml:89(td) ./doc/common/tables/trove-auth_token.xml:89(td) ./doc/common/tables/keystone-auth_token.xml:89(td) ./doc/common/tables/ceilometer-auth.xml:89(td) ./doc/common/tables/heat-auth_token.xml:89(td) ./doc/common/tables/neutron-auth_token.xml:89(td)
-msgid "http_connect_timeout = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:90(td) ./doc/common/tables/nova-auth_token.xml:83(td) ./doc/common/tables/cinder-auth_token.xml:90(td) ./doc/common/tables/trove-auth_token.xml:90(td) ./doc/common/tables/keystone-auth_token.xml:90(td) ./doc/common/tables/ceilometer-auth.xml:90(td) ./doc/common/tables/heat-auth_token.xml:90(td) ./doc/common/tables/neutron-auth_token.xml:90(td)
-msgid "(BoolOpt) Request timeout value for communicating with Identity API server."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:93(td) ./doc/common/tables/nova-auth_token.xml:86(td) ./doc/common/tables/cinder-auth_token.xml:93(td) ./doc/common/tables/trove-auth_token.xml:93(td) ./doc/common/tables/keystone-auth_token.xml:93(td) ./doc/common/tables/ceilometer-auth.xml:93(td) ./doc/common/tables/heat-auth_token.xml:93(td) ./doc/common/tables/neutron-auth_token.xml:93(td)
-msgid "http_request_max_retries = 3"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:94(td) ./doc/common/tables/nova-auth_token.xml:87(td) ./doc/common/tables/cinder-auth_token.xml:94(td) ./doc/common/tables/trove-auth_token.xml:94(td) ./doc/common/tables/keystone-auth_token.xml:94(td) ./doc/common/tables/ceilometer-auth.xml:94(td) ./doc/common/tables/heat-auth_token.xml:94(td) ./doc/common/tables/neutron-auth_token.xml:94(td)
-msgid "(IntOpt) How many times are we trying to reconnect when communicating with Identity API Server."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:97(td) ./doc/common/tables/nova-auth_token.xml:90(td) ./doc/common/tables/cinder-auth_token.xml:97(td) ./doc/common/tables/trove-auth_token.xml:97(td) ./doc/common/tables/keystone-auth_token.xml:97(td) ./doc/common/tables/ceilometer-auth.xml:97(td) ./doc/common/tables/heat-auth_token.xml:97(td) ./doc/common/tables/neutron-auth_token.xml:97(td)
-msgid "include_service_catalog = True"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:98(td) ./doc/common/tables/nova-auth_token.xml:91(td) ./doc/common/tables/cinder-auth_token.xml:98(td) ./doc/common/tables/trove-auth_token.xml:98(td) ./doc/common/tables/keystone-auth_token.xml:98(td) ./doc/common/tables/ceilometer-auth.xml:98(td) ./doc/common/tables/heat-auth_token.xml:98(td) ./doc/common/tables/neutron-auth_token.xml:98(td)
-msgid "(BoolOpt) (optional) indicate whether to set the X-Service-Catalog header. If False, middleware will not ask for service catalog on token validation and will not set the X-Service-Catalog header."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:102(td) ./doc/common/tables/nova-auth_token.xml:95(td) ./doc/common/tables/cinder-auth_token.xml:102(td) ./doc/common/tables/trove-auth_token.xml:102(td) ./doc/common/tables/keystone-auth_token.xml:102(td) ./doc/common/tables/ceilometer-auth.xml:102(td) ./doc/common/tables/heat-auth_token.xml:102(td) ./doc/common/tables/neutron-auth_token.xml:102(td)
-msgid "(BoolOpt) Verify HTTPS connections."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:105(td) ./doc/common/tables/nova-auth_token.xml:98(td) ./doc/common/tables/cinder-auth_token.xml:105(td) ./doc/common/tables/trove-auth_token.xml:105(td) ./doc/common/tables/keystone-auth_token.xml:105(td) ./doc/common/tables/ceilometer-auth.xml:105(td) ./doc/common/tables/heat-auth_token.xml:105(td) ./doc/common/tables/neutron-auth_token.xml:105(td)
-msgid "keyfile = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:109(td) ./doc/common/tables/nova-auth_token.xml:102(td) ./doc/common/tables/cinder-auth_token.xml:109(td) ./doc/common/tables/trove-auth_token.xml:109(td) ./doc/common/tables/keystone-auth_token.xml:109(td) ./doc/common/tables/ceilometer-auth.xml:109(td) ./doc/common/tables/heat-auth_token.xml:109(td) ./doc/common/tables/neutron-auth_token.xml:109(td)
-msgid "memcache_secret_key = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:110(td) ./doc/common/tables/nova-auth_token.xml:103(td) ./doc/common/tables/cinder-auth_token.xml:110(td) ./doc/common/tables/trove-auth_token.xml:110(td) ./doc/common/tables/keystone-auth_token.xml:110(td) ./doc/common/tables/ceilometer-auth.xml:110(td) ./doc/common/tables/heat-auth_token.xml:110(td) ./doc/common/tables/neutron-auth_token.xml:110(td)
-msgid "(StrOpt) (optional, mandatory if memcache_security_strategy is defined) this string is used for key derivation."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:113(td) ./doc/common/tables/nova-auth_token.xml:106(td) ./doc/common/tables/cinder-auth_token.xml:113(td) ./doc/common/tables/trove-auth_token.xml:113(td) ./doc/common/tables/keystone-auth_token.xml:113(td) ./doc/common/tables/ceilometer-auth.xml:113(td) ./doc/common/tables/heat-auth_token.xml:113(td) ./doc/common/tables/neutron-auth_token.xml:113(td)
-msgid "memcache_security_strategy = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:114(td) ./doc/common/tables/nova-auth_token.xml:107(td) ./doc/common/tables/cinder-auth_token.xml:114(td) ./doc/common/tables/trove-auth_token.xml:114(td) ./doc/common/tables/keystone-auth_token.xml:114(td) ./doc/common/tables/ceilometer-auth.xml:114(td) ./doc/common/tables/heat-auth_token.xml:114(td) ./doc/common/tables/neutron-auth_token.xml:114(td)
-msgid "(StrOpt) (optional) if defined, indicate whether token data should be authenticated or authenticated and encrypted. Acceptable values are MAC or ENCRYPT. If MAC, token data is authenticated (with HMAC) in the cache. If ENCRYPT, token data is encrypted and authenticated in the cache. If the value is not one of these options or empty, auth_token will raise an exception on initialization."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:118(td) ./doc/common/tables/nova-auth_token.xml:111(td) ./doc/common/tables/cinder-auth_token.xml:118(td) ./doc/common/tables/trove-auth_token.xml:118(td) ./doc/common/tables/keystone-auth_token.xml:118(td) ./doc/common/tables/ceilometer-auth.xml:118(td) ./doc/common/tables/heat-auth_token.xml:118(td) ./doc/common/tables/neutron-auth_token.xml:118(td)
-msgid "(ListOpt) Optionally specify a list of memcached server(s) to use for caching. If left undefined, tokens will instead be cached in-process."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:121(td) ./doc/common/tables/nova-auth_token.xml:114(td) ./doc/common/tables/cinder-auth_token.xml:121(td) ./doc/common/tables/trove-auth_token.xml:121(td) ./doc/common/tables/keystone-auth_token.xml:121(td) ./doc/common/tables/ceilometer-auth.xml:121(td) ./doc/common/tables/heat-auth_token.xml:121(td) ./doc/common/tables/neutron-auth_token.xml:121(td)
-msgid "revocation_cache_time = 300"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:122(td) ./doc/common/tables/nova-auth_token.xml:115(td) ./doc/common/tables/cinder-auth_token.xml:122(td) ./doc/common/tables/trove-auth_token.xml:122(td) ./doc/common/tables/keystone-auth_token.xml:122(td) ./doc/common/tables/ceilometer-auth.xml:122(td) ./doc/common/tables/heat-auth_token.xml:122(td) ./doc/common/tables/neutron-auth_token.xml:122(td)
-msgid "(IntOpt) Determines the frequency at which the list of revoked tokens is retrieved from the Identity service (in seconds). A high number of revocation events combined with a low cache duration may significantly reduce performance."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:125(td) ./doc/common/tables/nova-auth_token.xml:118(td) ./doc/common/tables/cinder-auth_token.xml:125(td) ./doc/common/tables/trove-auth_token.xml:125(td) ./doc/common/tables/keystone-auth_token.xml:125(td) ./doc/common/tables/ceilometer-auth.xml:125(td) ./doc/common/tables/heat-auth_token.xml:125(td) ./doc/common/tables/neutron-auth_token.xml:125(td)
-msgid "signing_dir = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:126(td) ./doc/common/tables/nova-auth_token.xml:119(td) ./doc/common/tables/cinder-auth_token.xml:126(td) ./doc/common/tables/trove-auth_token.xml:126(td) ./doc/common/tables/keystone-auth_token.xml:126(td) ./doc/common/tables/ceilometer-auth.xml:126(td) ./doc/common/tables/heat-auth_token.xml:126(td) ./doc/common/tables/neutron-auth_token.xml:126(td)
-msgid "(StrOpt) Directory used to cache files related to PKI tokens"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:129(td) ./doc/common/tables/nova-auth_token.xml:122(td) ./doc/common/tables/cinder-auth_token.xml:129(td) ./doc/common/tables/trove-auth_token.xml:129(td) ./doc/common/tables/keystone-auth_token.xml:129(td) ./doc/common/tables/ceilometer-auth.xml:129(td) ./doc/common/tables/heat-auth_token.xml:129(td) ./doc/common/tables/neutron-auth_token.xml:129(td)
-msgid "token_cache_time = 300"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml:130(td) ./doc/common/tables/nova-auth_token.xml:123(td) ./doc/common/tables/cinder-auth_token.xml:130(td) ./doc/common/tables/trove-auth_token.xml:130(td) ./doc/common/tables/keystone-auth_token.xml:130(td) ./doc/common/tables/ceilometer-auth.xml:130(td) ./doc/common/tables/heat-auth_token.xml:130(td) ./doc/common/tables/neutron-auth_token.xml:130(td)
-msgid "(IntOpt) In order to prevent excessive effort spent validating tokens, the middleware caches previously-seen tokens for a configurable duration (in seconds). Set to -1 to disable caching completely."
-msgstr ""
-
-#: ./doc/common/tables/neutron-kombu.xml:8(caption) ./doc/common/tables/nova-kombu.xml:8(caption)
-msgid "Description of configuration options for kombu"
-msgstr ""
-
-#: ./doc/common/tables/neutron-kombu.xml:23(td) ./doc/common/tables/heat-rabbitmq.xml:23(td) ./doc/common/tables/ceilometer-rabbitmq.xml:27(td) ./doc/common/tables/trove-amqp.xml:43(td)
-msgid "(StrOpt) SSL certification authority file (valid only if SSL enabled)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-kombu.xml:27(td) ./doc/common/tables/heat-rabbitmq.xml:27(td) ./doc/common/tables/ceilometer-rabbitmq.xml:31(td) ./doc/common/tables/trove-amqp.xml:47(td)
-msgid "(StrOpt) SSL cert file (valid only if SSL enabled)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-kombu.xml:31(td) ./doc/common/tables/heat-rabbitmq.xml:31(td) ./doc/common/tables/ceilometer-rabbitmq.xml:35(td) ./doc/common/tables/trove-amqp.xml:51(td)
-msgid "(StrOpt) SSL key file (valid only if SSL enabled)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-kombu.xml:35(td) ./doc/common/tables/ceilometer-rabbitmq.xml:39(td)
-msgid "(StrOpt) If SSL is enabled, the SSL version to use. Valid values are TLSv1, SSLv23 and SSLv3. SSLv2 might be available on some distributions."
-msgstr ""
-
-#: ./doc/common/tables/trove-redis.xml:38(td) ./doc/common/tables/heat-rpc.xml:62(td) ./doc/common/tables/ceilometer-redis.xml:53(td) ./doc/common/tables/neutron-rpc.xml:77(td)
-msgid "(StrOpt) Matchmaker ring file (JSON)"
-msgstr ""
-
-#: ./doc/common/tables/trove-qpid.xml:23(td) ./doc/common/tables/heat-qpid.xml:23(td) ./doc/common/tables/neutron-qpid.xml:23(td) ./doc/common/tables/ceilometer-qpid.xml:23(td)
-msgid "(IntOpt) Seconds between connection keepalive heartbeats"
-msgstr ""
-
-#: ./doc/common/tables/trove-qpid.xml:27(td) ./doc/common/tables/heat-qpid.xml:27(td) ./doc/common/tables/neutron-qpid.xml:27(td) ./doc/common/tables/ceilometer-qpid.xml:27(td)
-msgid "(StrOpt) Qpid broker hostname"
-msgstr ""
-
-#: ./doc/common/tables/trove-qpid.xml:31(td) ./doc/common/tables/heat-qpid.xml:31(td) ./doc/common/tables/neutron-qpid.xml:31(td) ./doc/common/tables/ceilometer-qpid.xml:31(td)
-msgid "(ListOpt) Qpid HA cluster host:port pairs"
-msgstr ""
-
-#: ./doc/common/tables/trove-qpid.xml:35(td) ./doc/common/tables/heat-qpid.xml:35(td) ./doc/common/tables/neutron-qpid.xml:35(td) ./doc/common/tables/ceilometer-qpid.xml:35(td)
-msgid "(StrOpt) Password for qpid connection"
-msgstr ""
-
-#: ./doc/common/tables/trove-qpid.xml:39(td) ./doc/common/tables/heat-qpid.xml:39(td) ./doc/common/tables/neutron-qpid.xml:39(td) ./doc/common/tables/ceilometer-qpid.xml:39(td)
-msgid "(IntOpt) Qpid broker port"
-msgstr ""
-
-#: ./doc/common/tables/trove-qpid.xml:43(td) ./doc/common/tables/heat-qpid.xml:43(td) ./doc/common/tables/neutron-qpid.xml:43(td) ./doc/common/tables/ceilometer-qpid.xml:43(td)
-msgid "(StrOpt) Transport to use, either 'tcp' or 'ssl'"
-msgstr ""
-
-#: ./doc/common/tables/trove-qpid.xml:47(td) ./doc/common/tables/heat-qpid.xml:47(td) ./doc/common/tables/neutron-qpid.xml:47(td) ./doc/common/tables/ceilometer-qpid.xml:47(td)
-msgid "(StrOpt) Space separated list of SASL mechanisms to use for auth"
-msgstr ""
-
-#: ./doc/common/tables/trove-qpid.xml:51(td) ./doc/common/tables/heat-qpid.xml:51(td) ./doc/common/tables/neutron-qpid.xml:51(td) ./doc/common/tables/ceilometer-qpid.xml:51(td)
-msgid "(BoolOpt) Disable Nagle algorithm"
-msgstr ""
-
-#: ./doc/common/tables/trove-qpid.xml:55(td) ./doc/common/tables/heat-qpid.xml:59(td) ./doc/common/tables/neutron-qpid.xml:59(td) ./doc/common/tables/ceilometer-qpid.xml:59(td)
-msgid "(StrOpt) Username for qpid connection"
-msgstr ""
-
-#: ./doc/common/tables/trove-compute.xml:8(caption) ./doc/common/tables/neutron-compute.xml:8(caption) ./doc/common/tables/cinder-compute.xml:8(caption) ./doc/common/tables/nova-compute.xml:8(caption)
-msgid "Description of configuration options for compute"
-msgstr ""
-
-#: ./doc/common/tables/trove-compute.xml:22(td)
-msgid "ip_regex = None"
-msgstr ""
-
-#: ./doc/common/tables/trove-compute.xml:26(td)
-msgid "nova_compute_url = http://localhost:8774/v2"
-msgstr ""
-
-#: ./doc/common/tables/trove-compute.xml:30(td)
-msgid "root_grant = ALL"
-msgstr ""
-
-#: ./doc/common/tables/trove-compute.xml:31(td) ./doc/common/tables/trove-api.xml:23(td) ./doc/common/tables/trove-guestagent.xml:43(td) ./doc/common/tables/trove-guestagent.xml:47(td)
-msgid "(ListOpt) No help text available for this option."
-msgstr ""
-
-#: ./doc/common/tables/trove-compute.xml:34(td)
-msgid "root_grant_option = True"
-msgstr ""
-
-#: ./doc/common/tables/trove-compute.xml:35(td) ./doc/common/tables/trove-api.xml:99(td) ./doc/common/tables/trove-taskmanager.xml:71(td) ./doc/common/tables/trove-taskmanager.xml:75(td) ./doc/common/tables/trove-database.xml:31(td) ./doc/common/tables/trove-dns.xml:83(td)
-msgid "(BoolOpt) No help text available for this option."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:7(literal)
-msgid "[filter:ratelimit]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:18(td)
-msgid "use = egg:swift#ratelimit"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:21(td)
-msgid "set log_name = ratelimit"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:36(td)
-msgid "clock_accuracy = 1000"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:36(td)
-msgid "Represents how accurate the proxy servers' system clocks are with each other. 1000 means that all the proxies' clock are accurate to each other within 1 millisecond. No ratelimit should be higher than the clock accuracy."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:39(td)
-msgid "max_sleep_time_seconds = 60"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:39(td)
-msgid "App will immediately return a 498 response if the necessary sleep time ever exceeds the given max_sleep_time_seconds."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:42(td)
-msgid "log_sleep_time_seconds = 0"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:42(td)
-msgid "To allow visibility into rate limiting set this value &gt; 0 and all sleeps greater than the number will be logged."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:45(td)
-msgid "rate_buffer_seconds = 5"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:45(td)
-msgid "Number of seconds the rate counter can drop and be allowed to catch up (at a faster than listed rate). A larger number will result in larger spikes in rate but better average accuracy."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:48(td)
-msgid "account_ratelimit = 0"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:48(td)
-msgid "If set, will limit PUT and DELETE requests to /account_name/container_name. Number is in requests per second."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:51(td)
-msgid "account_whitelist = a,b"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:51(td)
-msgid "Comma separated lists of account names that will not be rate limited."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:54(td)
-msgid "account_blacklist = c,d"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:54(td)
-msgid "Comma separated lists of account names that will not be allowed. Returns a 497 response. r: for containers of size x, limit requests per second to r. Will limit PUT, DELETE, and POST requests to /a/c/o. container_listing_ratelimit_x = r: for containers of size x, limit listing requests per second to r. Will limit GET requests to /a/c."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:57(td)
-msgid "with container_limit_x = r"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:60(td)
-msgid "container_ratelimit_0 = 100"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:63(td)
-msgid "container_ratelimit_10 = 50"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:66(td)
-msgid "container_ratelimit_50 = 20"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:69(td)
-msgid "container_listing_ratelimit_0 = 100"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:72(td)
-msgid "container_listing_ratelimit_10 = 50"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:75(td)
-msgid "container_listing_ratelimit_50 = 20"
-msgstr ""
-
-#: ./doc/common/tables/trove-nova.xml:8(caption)
-msgid "Description of configuration options for nova"
-msgstr ""
-
-#: ./doc/common/tables/trove-nova.xml:22(td)
-msgid "nova_proxy_admin_pass ="
-msgstr ""
-
-#: ./doc/common/tables/trove-nova.xml:23(td)
-msgid "(StrOpt) Admin password used to connect to nova,"
-msgstr ""
-
-#: ./doc/common/tables/trove-nova.xml:26(td)
-msgid "nova_proxy_admin_tenant_name ="
-msgstr ""
-
-#: ./doc/common/tables/trove-nova.xml:27(td)
-msgid "(StrOpt) Admin tenant used to connect to nova."
-msgstr ""
-
-#: ./doc/common/tables/trove-nova.xml:30(td)
-msgid "nova_proxy_admin_user ="
-msgstr ""
-
-#: ./doc/common/tables/trove-nova.xml:31(td)
-msgid "(StrOpt) Admin username used to connect to nova."
+#: ./doc/common/tables/ceilometer-cells.xml:8(caption) ./doc/common/tables/nova-cells.xml:8(caption)
+msgid "Description of configuration options for cells"
 msgstr ""
 
 #: ./doc/common/tables/ceilometer-cells.xml:22(td) ./doc/common/tables/nova-quota.xml:85(td)
@@ -21563,572 +25219,76 @@ msgstr ""
 msgid "(IntOpt) Seconds between bandwidth updates for cells."
 msgstr ""
 
-#: ./doc/common/tables/keystone-oauth.xml:8(caption)
-msgid "Description of configuration options for oauth"
+#: ./doc/common/tables/ceilometer-cells.xml:26(td) ./doc/common/tables/nova-cells.xml:22(td)
+msgid "call_timeout = 60"
 msgstr ""
 
-#: ./doc/common/tables/keystone-oauth.xml:19(th)
-msgid "[oauth1]"
+#: ./doc/common/tables/ceilometer-cells.xml:27(td) ./doc/common/tables/nova-cells.xml:23(td)
+msgid "(IntOpt) Seconds to wait for response from a call to a cell."
 msgstr ""
 
-#: ./doc/common/tables/keystone-oauth.xml:22(td)
-msgid "access_token_duration = 86400"
+#: ./doc/common/tables/ceilometer-cells.xml:30(td) ./doc/common/tables/nova-cells.xml:26(td)
+msgid "capabilities = hypervisor=xenserver;kvm, os=linux;windows"
 msgstr ""
 
-#: ./doc/common/tables/keystone-oauth.xml:23(td)
-msgid "(IntOpt) Duration (in seconds) for the OAuth Access Token."
+#: ./doc/common/tables/ceilometer-cells.xml:31(td) ./doc/common/tables/nova-cells.xml:27(td)
+msgid "(ListOpt) Key/Multi-value list with the capabilities of the cell"
 msgstr ""
 
-#: ./doc/common/tables/keystone-oauth.xml:26(td)
-msgid "driver = keystone.contrib.oauth1.backends.sql.OAuth1"
+#: ./doc/common/tables/ceilometer-cells.xml:34(td) ./doc/common/tables/nova-cells.xml:30(td)
+msgid "cell_type = compute"
 msgstr ""
 
-#: ./doc/common/tables/keystone-oauth.xml:27(td) ./doc/common/tables/keystone-credential.xml:23(td)
-msgid "(StrOpt) Keystone Credential backend driver."
+#: ./doc/common/tables/ceilometer-cells.xml:35(td) ./doc/common/tables/nova-cells.xml:31(td)
+msgid "(StrOpt) Type of cell: api or compute"
 msgstr ""
 
-#: ./doc/common/tables/keystone-oauth.xml:30(td)
-msgid "request_token_duration = 28800"
+#: ./doc/common/tables/ceilometer-cells.xml:38(td) ./doc/common/tables/nova-cells.xml:42(td) ./doc/common/tables/keystone-ssl.xml:77(td)
+msgid "enable = False"
 msgstr ""
 
-#: ./doc/common/tables/keystone-oauth.xml:31(td)
-msgid "(IntOpt) Duration (in seconds) for the OAuth Request Token."
+#: ./doc/common/tables/ceilometer-cells.xml:39(td) ./doc/common/tables/nova-cells.xml:43(td)
+msgid "(BoolOpt) Enable cell functionality"
 msgstr ""
 
-#: ./doc/common/tables/cinder-block-device.xml:8(caption)
-msgid "Description of configuration options for block-device"
+#: ./doc/common/tables/ceilometer-cells.xml:42(td) ./doc/common/tables/nova-cells.xml:54(td)
+msgid "manager = nova.cells.manager.CellsManager"
 msgstr ""
 
-#: ./doc/common/tables/cinder-block-device.xml:22(td)
-msgid "available_devices ="
+#: ./doc/common/tables/ceilometer-cells.xml:43(td) ./doc/common/tables/nova-cells.xml:55(td)
+msgid "(StrOpt) Manager for cells"
 msgstr ""
 
-#: ./doc/common/tables/cinder-block-device.xml:23(td)
-msgid "(ListOpt) List of all available devices"
+#: ./doc/common/tables/ceilometer-cells.xml:46(td) ./doc/common/tables/nova-cells.xml:62(td)
+msgid "mute_child_interval = 300"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zones.xml:8(caption)
-msgid "Description of configuration options for zones"
+#: ./doc/common/tables/ceilometer-cells.xml:47(td) ./doc/common/tables/nova-cells.xml:63(td)
+msgid "(IntOpt) Number of seconds after which a lack of capability and capacity updates signals the child cell is to be treated as a mute."
 msgstr ""
 
-#: ./doc/common/tables/cinder-zones.xml:22(td)
-msgid "cloned_volume_same_az = True"
+#: ./doc/common/tables/ceilometer-cells.xml:50(td) ./doc/common/tables/nova-cells.xml:74(td)
+msgid "name = nova"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zones.xml:23(td)
-msgid "(BoolOpt) Ensure that the new volumes are the same AZ as snapshot or source volume"
+#: ./doc/common/tables/ceilometer-cells.xml:51(td) ./doc/common/tables/nova-cells.xml:75(td)
+msgid "(StrOpt) Name of this cell"
 msgstr ""
 
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:8(caption)
-msgid "Description of configuration options for netapp_7mode_iscsi"
+#: ./doc/common/tables/ceilometer-cells.xml:54(td) ./doc/common/tables/nova-cells.xml:82(td)
+msgid "reserve_percent = 10.0"
 msgstr ""
 
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:38(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:38(td)
-msgid "netapp_size_multiplier = 1.2"
+#: ./doc/common/tables/ceilometer-cells.xml:55(td) ./doc/common/tables/nova-cells.xml:83(td)
+msgid "(FloatOpt) Percentage of cell capacity to hold in reserve. Affects both memory and disk utilization"
 msgstr ""
 
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:39(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:39(td)
-msgid "(FloatOpt) The quantity to be multiplied by the requested volume size to ensure enough space is available on the virtual storage server (Vserver) to fulfill the volume creation request."
+#: ./doc/common/tables/ceilometer-cells.xml:58(td) ./doc/common/tables/nova-cells.xml:86(td)
+msgid "topic = cells"
 msgstr ""
 
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:46(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:46(td) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:46(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:50(td)
-msgid "netapp_storage_protocol = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:47(td) ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:47(td) ./doc/common/tables/cinder-netapp_7mode_nfs.xml:47(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:51(td)
-msgid "(StrOpt) The storage protocol to be used on the data path with the storage system; valid values are iscsi or nfs."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:54(td)
-msgid "netapp_vfiler = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:55(td)
-msgid "(StrOpt) The vFiler unit on which provisioning of block storage volumes will be done. This option is only used by the driver when connecting to an instance with a storage family of Data ONTAP operating in 7-Mode and the storage protocol selected is iSCSI. Only use this option when utilizing the MultiStore feature on the NetApp storage system."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:58(td)
-msgid "netapp_volume_list = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:59(td)
-msgid "(StrOpt) This option is only utilized when the storage protocol is configured to use iSCSI. This option is used to restrict provisioning to the specified controller volumes. Specify the value of this option to be a comma separated list of NetApp controller volume names to be used for provisioning."
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-sync.xml:7(literal)
-msgid "[container-sync]"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-sync.xml:18(td)
-msgid "log_name = container-sync"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-sync.xml:30(td)
-msgid "sync_proxy = http://10.1.1.1:8888,http://10.1.1.2:8888"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-sync.xml:30(td)
-msgid "If you need to use an HTTP proxy, set it here. Defaults to no proxy."
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-sync.xml:36(td)
-msgid "container_time = 60"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-sync.xml:36(td)
-msgid "Maximum amount of time to spend syncing each container"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:8(caption) ./doc/common/tables/nova-common.xml:8(caption) ./doc/common/tables/glance-common.xml:8(caption) ./doc/common/tables/cinder-common.xml:8(caption) ./doc/common/tables/trove-common.xml:8(caption) ./doc/common/tables/ceilometer-common.xml:8(caption) ./doc/common/tables/heat-common.xml:8(caption)
-msgid "Description of configuration options for common"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:23(td) ./doc/common/tables/neutron-common.xml:193(td)
-msgid "(StrOpt) Admin password"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:26(td) ./doc/common/tables/neutron-common.xml:196(td) ./doc/common/tables/glance-registry.xml:26(td)
-msgid "admin_tenant_name = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:27(td) ./doc/common/tables/neutron-common.xml:197(td)
-msgid "(StrOpt) Admin tenant name"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:31(td)
-msgid "(StrOpt) Admin username"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:34(td)
-msgid "agent_down_time = 75"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:35(td)
-msgid "(IntOpt) Seconds to regard the agent is down; should be at least twice report_interval, to be sure the agent is down for good."
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:38(td) ./doc/common/tables/heat-rpc.xml:22(td) ./doc/common/tables/ceilometer-rpc.xml:22(td) ./doc/common/tables/trove-rpc.xml:22(td)
-msgid "allowed_rpc_exception_modules = nova.exception, cinder.exception, exceptions"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:39(td) ./doc/common/tables/heat-rpc.xml:23(td) ./doc/common/tables/nova-testing.xml:23(td) ./doc/common/tables/cinder-rpc.xml:23(td) ./doc/common/tables/keystone-rpc.xml:23(td) ./doc/common/tables/ceilometer-rpc.xml:23(td)
-msgid "(ListOpt) Modules of exceptions that are permitted to be recreated upon receiving exception data from an rpc call."
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:42(td)
-msgid "api_workers = 0"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:43(td)
-msgid "(IntOpt) Number of separate worker processes for service"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:46(td)
-msgid "auth_ca_cert = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:47(td)
-msgid "(StrOpt) Certificate Authority public key (CA cert) file for ssl"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:50(td)
-msgid "auth_insecure = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:51(td)
-msgid "(BoolOpt) Turn off verification of the certificate for ssl"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:54(td) ./doc/common/tables/neutron-common.xml:204(td) ./doc/common/tables/glance-registry.xml:34(td)
-msgid "auth_region = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:55(td) ./doc/common/tables/neutron-common.xml:205(td)
-msgid "(StrOpt) Authentication region"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:58(td) ./doc/common/tables/neutron-common.xml:208(td) ./doc/common/tables/ceilometer-auth.xml:22(td)
-msgid "auth_strategy = keystone"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:59(td) ./doc/common/tables/neutron-common.xml:209(td)
-msgid "(StrOpt) The type of authentication to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:62(td) ./doc/common/tables/neutron-common.xml:212(td) ./doc/common/tables/glance-registry.xml:42(td)
-msgid "auth_url = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:63(td) ./doc/common/tables/neutron-common.xml:213(td)
-msgid "(StrOpt) Authentication URL"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:66(td)
-msgid "base_mac = fa:16:3e:00:00:00"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:67(td)
-msgid "(StrOpt) The base MAC address Neutron will use for VIFs"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:70(td) ./doc/common/tables/heat-cfn_api.xml:37(td) ./doc/common/tables/heat-cloudwatch_api.xml:33(td) ./doc/common/tables/glance-common.xml:34(td) ./doc/common/tables/heat-api.xml:107(td)
-msgid "bind_host = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:71(td)
-msgid "(StrOpt) The host IP to bind to"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:74(td)
-msgid "bind_port = 9696"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:75(td)
-msgid "(IntOpt) The port to bind to"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:78(td)
-msgid "ca_certs = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:79(td)
-msgid "(StrOpt) CA certificates"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:82(td)
-msgid "core_plugin = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:83(td)
-msgid "(StrOpt) The core plugin Neutron will use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:86(td)
-msgid "ctl_cert = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:87(td)
-msgid "(StrOpt) controller certificate"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:90(td)
-msgid "ctl_privkey = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:91(td)
-msgid "(StrOpt) controller private key"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:94(td)
-msgid "dhcp_agent_notification = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:95(td)
-msgid "(BoolOpt) Allow sending resource operation notification to DHCP agent"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:98(td)
-msgid "dhcp_agents_per_network = 1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:99(td)
-msgid "(IntOpt) Number of DHCP agents scheduled to host a network."
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:102(td)
-msgid "dhcp_confs = $state_path/dhcp"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:103(td)
-msgid "(StrOpt) Location to store DHCP server config files"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:106(td)
-msgid "dhcp_delete_namespaces = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:107(td)
-msgid "(BoolOpt) Delete namespace after removing a dhcp server."
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:110(td)
-msgid "dhcp_domain = openstacklocal"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:111(td) ./doc/common/tables/nova-network.xml:51(td) ./doc/common/tables/neutron-vmware.xml:120(td)
-msgid "(StrOpt) Domain to use for building the hostnames"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:114(td)
-msgid "dhcp_driver = neutron.agent.linux.dhcp.Dnsmasq"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:115(td)
-msgid "(StrOpt) The driver used to manage the DHCP server."
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:118(td)
-msgid "dhcp_lease_duration = 86400"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:119(td)
-msgid "(IntOpt) DHCP lease duration"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:126(td)
-msgid "endpoint_type = adminURL"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:127(td)
-msgid "(StrOpt) Network service endpoint type to pull from the keystone catalog"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:130(td)
-msgid "force_gateway_on_subnet = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:131(td)
-msgid "(BoolOpt) Ensure that configured gateway is on subnet"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:134(td)
-msgid "interface_driver = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:135(td)
-msgid "(StrOpt) The driver used to manage the virtual interface."
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:138(td)
-msgid "ip_lib_force_root = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:139(td)
-msgid "(BoolOpt) Force ip_lib calls to use the root helper"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:142(td) ./doc/common/tables/nova-common.xml:46(td) ./doc/common/tables/heat-debug.xml:38(td) ./doc/common/tables/glance-common.xml:70(td) ./doc/common/tables/cinder-common.xml:70(td) ./doc/common/tables/trove-common.xml:58(td) ./doc/common/tables/ceilometer-common.xml:34(td) ./doc/common/tables/keystone-misc.xml:22(td)
-msgid "lock_path = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:143(td) ./doc/common/tables/nova-common.xml:47(td) ./doc/common/tables/heat-debug.xml:39(td) ./doc/common/tables/glance-common.xml:71(td) ./doc/common/tables/trove-common.xml:59(td) ./doc/common/tables/ceilometer-common.xml:35(td) ./doc/common/tables/keystone-misc.xml:23(td)
-msgid "(StrOpt) Directory to use for lock files."
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:146(td)
-msgid "mac_generation_retries = 16"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:147(td)
-msgid "(IntOpt) How many times Neutron will retry MAC generation"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:150(td)
-msgid "max_dns_nameservers = 5"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:151(td)
-msgid "(IntOpt) Maximum number of DNS nameservers"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:154(td)
-msgid "max_fixed_ips_per_port = 5"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:155(td)
-msgid "(IntOpt) Maximum number of fixed ips per port"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:158(td)
-msgid "max_subnet_host_routes = 20"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:159(td)
-msgid "(IntOpt) Maximum number of host routes per subnet"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:162(td)
-msgid "periodic_fuzzy_delay = 5"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:163(td) ./doc/common/tables/nova-periodic.xml:27(td)
-msgid "(IntOpt) Range of seconds to randomly delay when starting the periodic task scheduler to reduce stampeding. (Disable by setting to 0)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:166(td)
-msgid "periodic_interval = 40"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:167(td)
-msgid "(IntOpt) Seconds between running periodic tasks"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:170(td) ./doc/common/tables/swift-object-expirer-object-expirer.xml:27(td)
-msgid "report_interval = 300"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:171(td)
-msgid "(IntOpt) Interval between two metering reports"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:174(td) ./doc/common/tables/neutron-common.xml:185(td) ./doc/common/tables/neutron-sdnve.xml:89(td)
-msgid "root_helper = sudo"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:175(td) ./doc/common/tables/neutron-common.xml:186(td)
-msgid "(StrOpt) Root helper application."
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:178(td)
-msgid "state_path = /var/lib/neutron"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:179(td)
-msgid "(StrOpt) Where to store Neutron state files. This directory must be writable by the agent."
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:182(th) ./doc/common/tables/neutron-openvswitch_agent.xml:34(th) ./doc/common/tables/neutron-metering_agent.xml:30(th) ./doc/common/tables/neutron-ml2_ofa.xml:34(th) ./doc/common/tables/neutron-hyperv_agent.xml:19(th) ./doc/common/tables/neutron-rpc.xml:66(th) ./doc/common/tables/neutron-nvsd.xml:19(th)
-msgid "[AGENT]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:189(th)
-msgid "[PROXY]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:201(td)
-msgid "(StrOpt) Admin user"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:216(th) ./doc/common/tables/neutron-embrane.xml:19(th)
-msgid "[heleos]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml:220(td) ./doc/common/tables/neutron-embrane_lb.xml:23(td)
-msgid "(StrOpt) ESM admin password."
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml:22(td)
-msgid "notify_nova_on_port_data_changes = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml:23(td)
-msgid "(BoolOpt) Send notification to nova when port data (fixed_ips/floatingip) changes so nova can update its cache."
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml:26(td)
-msgid "notify_nova_on_port_status_changes = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml:27(td)
-msgid "(BoolOpt) Send notification to nova when port status changes"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml:30(td)
-msgid "nova_admin_auth_url = http://localhost:5000/v2.0"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml:31(td)
-msgid "(StrOpt) Authorization URL for connecting to nova in admin context"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml:34(td)
-msgid "nova_admin_password = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml:35(td)
-msgid "(StrOpt) Password for connection to nova in admin context"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml:38(td)
-msgid "nova_admin_tenant_id = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml:39(td)
-msgid "(StrOpt) The uuid of the admin nova tenant"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml:42(td)
-msgid "nova_admin_username = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml:43(td)
-msgid "(StrOpt) Username for connecting to nova in admin context"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml:46(td)
-msgid "nova_region_name = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml:47(td)
-msgid "(StrOpt) Name of nova region to use. Useful if keystone manages more than one region."
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml:50(td)
-msgid "nova_url = http://127.0.0.1:8774"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml:51(td)
-msgid "(StrOpt) URL for connection to nova"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml:54(td)
-msgid "send_events_interval = 2"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml:55(td)
-msgid "(IntOpt) Number of seconds between sending events to nova if there are any events to send."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml:7(literal)
-msgid "[object-auditor]"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml:7(literal) ./doc/common/tables/swift-object-server-object-updater.xml:7(literal) ./doc/common/tables/swift-object-server-pipeline-main.xml:7(literal) ./doc/common/tables/swift-object-server-DEFAULT.xml:7(literal) ./doc/common/tables/swift-object-server-filter-recon.xml:7(literal) ./doc/common/tables/swift-object-server-object-replicator.xml:7(literal) ./doc/common/tables/swift-object-server-app-object-server.xml:7(literal) ./doc/common/tables/swift-object-server-filter-healthcheck.xml:7(literal)
-msgid "object-server.conf-sample"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml:18(td)
-msgid "log_name = object-auditor"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml:30(td)
-msgid "files_per_second = 20"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml:30(td)
-msgid "Maximum files audited per second. Should be tuned according to individual system specs. 0 is unlimited."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml:33(td)
-msgid "bytes_per_second = 10000000"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml:33(td)
-msgid "Maximum bytes audited per second. Should be tuned according to individual system specs. 0 is unlimited. mounted to prevent accidentally writing to the root device process simultaneously (it will actually accept(2) N + 1). Setting this to one (1) will only handle one request at a time, without accepting another request concurrently. By increasing the number of workers to a much higher value, one can reduce the impact of slow file system operations in one request from negatively impacting other requests. underlying filesystem does not support it. to setup custom log handlers. bytes you'd like fallocate to reserve, whether there is space for the given file size or not. This is useful for systems that behave badly when they completely run out of space; you can make the services pretend they're out of space early. container server. For most cases, this should be `egg:swift#container`."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml:36(td)
-msgid "log_time = 3600"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml:36(td)
-msgid "Frequency of status logs in seconds."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml:39(td)
-msgid "zero_byte_files_per_second = 50"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml:39(td)
-msgid "Maximum zero byte files audited per second."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml:45(td)
-msgid "object_size_stats ="
-msgstr ""
-
-#: ./doc/common/tables/keystone-ldap.xml:8(caption) ./doc/common/tables/nova-ldap.xml:8(caption)
-msgid "Description of configuration options for ldap"
+#: ./doc/common/tables/ceilometer-cells.xml:59(td) ./doc/common/tables/nova-cells.xml:87(td)
+msgid "(StrOpt) The topic cells nodes listen on"
 msgstr ""
 
 #: ./doc/common/tables/keystone-ldap.xml:19(th)
@@ -22707,2414 +25867,6 @@ msgstr ""
 msgid "(StrOpt) Search base for users."
 msgstr ""
 
-#: ./doc/common/tables/heat-rpc.xml:8(caption) ./doc/common/tables/cinder-rpc.xml:8(caption) ./doc/common/tables/keystone-rpc.xml:8(caption) ./doc/common/tables/glance-rpc.xml:8(caption) ./doc/common/tables/ceilometer-rpc.xml:8(caption) ./doc/common/tables/neutron-rpc.xml:8(caption) ./doc/common/tables/trove-rpc.xml:8(caption) ./doc/common/tables/nova-rpc.xml:8(caption)
-msgid "Description of configuration options for rpc"
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml:26(td)
-msgid "engine_life_check_timeout = 2"
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml:27(td)
-msgid "(IntOpt) RPC timeout for the engine liveness check that is used for stack locking."
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml:31(td) ./doc/common/tables/ceilometer-redis.xml:27(td) ./doc/common/tables/neutron-rpc.xml:35(td) ./doc/common/tables/trove-rpc.xml:31(td)
-msgid "(IntOpt) Heartbeat frequency"
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml:38(td)
-msgid "rpc_backend = heat.openstack.common.rpc.impl_kombu"
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml:39(td) ./doc/common/tables/ceilometer-rpc.xml:31(td) ./doc/common/tables/neutron-rpc.xml:43(td) ./doc/common/tables/trove-rpc.xml:51(td)
-msgid "(StrOpt) The messaging module to use, defaults to kombu."
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml:47(td) ./doc/common/tables/ceilometer-rpc.xml:39(td) ./doc/common/tables/neutron-rpc.xml:51(td) ./doc/common/tables/trove-rpc.xml:59(td)
-msgid "(IntOpt) Size of RPC connection pool"
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml:51(td) ./doc/common/tables/ceilometer-rpc.xml:43(td) ./doc/common/tables/neutron-rpc.xml:55(td) ./doc/common/tables/trove-rpc.xml:63(td)
-msgid "(IntOpt) Seconds to wait for a response from call or multicall"
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml:55(td) ./doc/common/tables/ceilometer-rpc.xml:47(td) ./doc/common/tables/neutron-rpc.xml:59(td) ./doc/common/tables/trove-rpc.xml:67(td)
-msgid "(IntOpt) Size of RPC thread pool"
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml:65(th) ./doc/common/tables/ceilometer-rpc.xml:92(th) ./doc/common/tables/neutron-rpc.xml:80(th) ./doc/common/tables/trove-rpc.xml:70(th)
-msgid "[rpc_notifier2]"
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml:68(td) ./doc/common/tables/ceilometer-rpc.xml:95(td) ./doc/common/tables/neutron-rpc.xml:83(td) ./doc/common/tables/trove-rpc.xml:73(td)
-msgid "topics = notifications"
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml:69(td) ./doc/common/tables/ceilometer-rpc.xml:96(td)
-msgid "(ListOpt) AMQP topic(s) used for OpenStack notifications"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:8(caption)
-msgid "Description of configuration options for openvswitch_agent"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:22(td)
-msgid "ovs_integration_bridge = br-int"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:23(td)
-msgid "(StrOpt) Name of Open vSwitch bridge to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:26(td)
-msgid "ovs_use_veth = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:27(td)
-msgid "(BoolOpt) Uses veth for an interface or not"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:30(td)
-msgid "ovs_vsctl_timeout = 10"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:31(td)
-msgid "(IntOpt) Timeout in seconds for ovs-vsctl commands"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:37(td) ./doc/common/tables/neutron-linuxbridge_agent.xml:44(td)
-msgid "l2_population = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:38(td)
-msgid "(BoolOpt) Use ml2 l2population mechanism driver to learn remote mac and IPs and improve tunnel scalability"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:41(td)
-msgid "minimize_polling = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:42(td)
-msgid "(BoolOpt) Minimize polling by monitoring ovsdb for interface changes."
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:45(td)
-msgid "ovsdb_monitor_respawn_interval = 30"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:46(td)
-msgid "(IntOpt) The number of seconds to wait before respawning the ovsdb monitor after losing communication with it"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:49(td)
-msgid "tunnel_types ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:50(td)
-msgid "(ListOpt) Network types supported by the agent (gre and/or vxlan)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:53(td)
-msgid "veth_mtu = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:54(td)
-msgid "(IntOpt) MTU size of veth interfaces"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:57(td)
-msgid "vxlan_udp_port = 4789"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:58(td)
-msgid "(IntOpt) The UDP port to use for VXLAN tunnels."
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:61(th) ./doc/common/tables/neutron-cisco.xml:54(th)
-msgid "[CISCO_N1K]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:64(td)
-msgid "local_ip = 10.0.0.3"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:65(td)
-msgid "(StrOpt) N1K Local IP"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:68(th) ./doc/common/tables/neutron-ryu.xml:19(th)
-msgid "[OVS]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:71(td) ./doc/common/tables/neutron-cisco.xml:57(td)
-msgid "bridge_mappings ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:72(td)
-msgid "(ListOpt) List of &lt;physical_network&gt;:&lt;bridge&gt;"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:75(td)
-msgid "enable_tunneling = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:76(td)
-msgid "(BoolOpt) Enable tunneling support"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:79(td)
-msgid "int_peer_patch_port = patch-tun"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:80(td)
-msgid "(StrOpt) Peer patch port in integration bridge for tunnel bridge"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:84(td) ./doc/common/tables/neutron-sdnve.xml:43(td)
-msgid "(StrOpt) Integration bridge to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:87(td) ./doc/common/tables/neutron-linuxbridge_agent.xml:48(td)
-msgid "local_ip ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:88(td)
-msgid "(StrOpt) Local IP address of GRE tunnel endpoints."
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:91(td) ./doc/common/tables/neutron-ml2_vlan.xml:22(td) ./doc/common/tables/neutron-hyperv_agent.xml:45(td) ./doc/common/tables/neutron-linuxbridge_agent.xml:29(td)
-msgid "network_vlan_ranges ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:95(td) ./doc/common/tables/neutron-hyperv_agent.xml:49(td) ./doc/common/tables/neutron-cisco.xml:89(td) ./doc/common/tables/neutron-linuxbridge_agent.xml:33(td)
-msgid "tenant_network_type = local"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:96(td)
-msgid "(StrOpt) Network type for tenant networks (local, vlan, gre, vxlan, or none)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:99(td)
-msgid "tun_peer_patch_port = patch-int"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:100(td)
-msgid "(StrOpt) Peer patch port in tunnel bridge for integration bridge"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:103(td) ./doc/common/tables/neutron-cisco.xml:93(td)
-msgid "tunnel_bridge = br-tun"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:104(td)
-msgid "(StrOpt) Tunnel bridge to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:108(td)
-msgid "(ListOpt) List of &lt;tun_min&gt;:&lt;tun_max&gt;"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:111(td)
-msgid "tunnel_type ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml:112(td)
-msgid "(StrOpt) The type of tunnels to use when utilizing tunnels, either 'gre' or 'vxlan'"
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml:22(td)
-msgid "nova_api_insecure = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml:23(td)
-msgid "(BoolOpt) Allow to perform insecure SSL requests to nova"
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml:26(td)
-msgid "nova_ca_certificates_file = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml:27(td)
-msgid "(StrOpt) Location of ca certificates file to use for nova client requests."
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml:30(td)
-msgid "nova_catalog_admin_info = compute:nova:adminURL"
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml:31(td)
-msgid "(StrOpt) Same as nova_catalog_info, but for admin endpoint."
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml:34(td)
-msgid "nova_catalog_info = compute:nova:publicURL"
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml:35(td)
-msgid "(StrOpt) Info to match when looking for nova in the service catalog. Format is : separated values of the form: &lt;service_type&gt;:&lt;service_name&gt;:&lt;endpoint_type&gt;"
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml:38(td)
-msgid "nova_endpoint_admin_template = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml:39(td)
-msgid "(StrOpt) Same as nova_endpoint_template, but for admin endpoint."
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml:42(td)
-msgid "nova_endpoint_template = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml:43(td)
-msgid "(StrOpt) Override service catalog lookup with template for nova endpoint e.g. http://localhost:8774/v2/%(project_id)s"
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml:47(td)
-msgid "(StrOpt) region name of this node"
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml:8(caption)
-msgid "Description of configuration options for identity"
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml:19(th)
-msgid "[identity]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml:22(td)
-msgid "default_domain_id = default"
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml:23(td)
-msgid "(StrOpt) This references the domain to use for all Identity API v2 requests (which are not aware of domains). A domain with this ID will be created for you by keystone-manage db_sync in migration 008. The domain referenced by this ID cannot be deleted on the v3 API, to prevent accidentally breaking the v2 API. There is nothing special about this domain, other than the fact that it must exist to order to maintain support for your v2 clients."
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml:26(td)
-msgid "domain_config_dir = /etc/keystone/domains"
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml:27(td)
-msgid "(StrOpt) Path for Keystone to locate the domain specificidentity configuration files if domain_specific_drivers_enabled is set to true."
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml:30(td)
-msgid "domain_specific_drivers_enabled = False"
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml:31(td)
-msgid "(BoolOpt) A subset (or all) of domains can have their own identity driver, each with their own partial configuration file in a domain configuration directory. Only values specific to the domain need to be placed in the domain specific configuration file. This feature is disabled by default; set to True to enable."
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml:34(td)
-msgid "driver = keystone.identity.backends.sql.Identity"
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml:35(td)
-msgid "(StrOpt) Keystone Identity backend driver."
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml:38(td) ./doc/common/tables/keystone-assignment.xml:34(td) ./doc/common/tables/keystone-catalog.xml:26(td) ./doc/common/tables/keystone-policy.xml:37(td) ./doc/common/tables/keystone-api.xml:46(td)
-msgid "list_limit = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml:39(td)
-msgid "(IntOpt) Maximum number of entities that will be returned in an identity collection."
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml:42(td)
-msgid "max_password_length = 4096"
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml:43(td)
-msgid "(IntOpt) Maximum supported length for user passwords; decrease to improve performance."
-msgstr ""
-
-#: ./doc/common/tables/cinder-lvm.xml:8(caption)
-msgid "Description of configuration options for lvm"
-msgstr ""
-
-#: ./doc/common/tables/cinder-lvm.xml:22(td)
-msgid "lvm_mirrors = 0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-lvm.xml:23(td)
-msgid "(IntOpt) If set, create lvms with multiple mirrors. Note that this requires lvm_mirrors + 2 pvs with available space"
-msgstr ""
-
-#: ./doc/common/tables/cinder-lvm.xml:26(td)
-msgid "lvm_type = default"
-msgstr ""
-
-#: ./doc/common/tables/cinder-lvm.xml:27(td)
-msgid "(StrOpt) Type of LVM volumes to deploy; (default or thin)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-lvm.xml:30(td)
-msgid "volume_group = cinder-volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-lvm.xml:31(td)
-msgid "(StrOpt) Name for the VG that will contain exported volumes"
-msgstr ""
-
-#: ./doc/common/tables/keystone-trust.xml:8(caption)
-msgid "Description of configuration options for trust"
-msgstr ""
-
-#: ./doc/common/tables/keystone-trust.xml:19(th)
-msgid "[trust]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-trust.xml:22(td)
-msgid "driver = keystone.trust.backends.sql.Trust"
-msgstr ""
-
-#: ./doc/common/tables/keystone-trust.xml:23(td)
-msgid "(StrOpt) Keystone Trust backend driver."
-msgstr ""
-
-#: ./doc/common/tables/keystone-trust.xml:26(td) ./doc/common/tables/trove-rpc.xml:80(td)
-msgid "enabled = True"
-msgstr ""
-
-#: ./doc/common/tables/keystone-trust.xml:27(td)
-msgid "(BoolOpt) delegation and impersonation features can be optionally disabled."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_nfs.xml:8(caption)
-msgid "Description of configuration options for storage_nfs"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_nfs.xml:23(td)
-msgid "(StrOpt) Mount options passed to the nfs client. See section of the nfs man page for details."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_nfs.xml:27(td)
-msgid "(StrOpt) Base dir containing mount points for nfs shares."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_nfs.xml:30(td)
-msgid "nfs_oversub_ratio = 1.0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_nfs.xml:31(td)
-msgid "(FloatOpt) This will compare the allocated to available space on the volume destination. If the ratio exceeds this number, the destination will no longer be valid."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_nfs.xml:34(td)
-msgid "nfs_shares_config = /etc/cinder/nfs_shares"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_nfs.xml:35(td) ./doc/common/tables/cinder-nexenta_nfs.xml:31(td)
-msgid "(StrOpt) File with the list of available nfs shares"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_nfs.xml:38(td)
-msgid "nfs_sparsed_volumes = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_nfs.xml:42(td)
-msgid "nfs_used_ratio = 0.95"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_nfs.xml:43(td)
-msgid "(FloatOpt) Percent of ACTUAL usage of the underlying volume before no new volumes can be allocated to the volume destination."
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml:8(caption)
-msgid "Description of configuration options for plumgrid"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml:19(th)
-msgid "[plumgriddirector]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml:22(td)
-msgid "director_server = localhost"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml:23(td)
-msgid "(StrOpt) PLUMgrid Director server to connect to"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml:26(td)
-msgid "director_server_port = 8080"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml:27(td)
-msgid "(StrOpt) PLUMgrid Director server port to connect to"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml:30(td) ./doc/common/tables/neutron-ml2_brocade.xml:30(td)
-msgid "password = password"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml:31(td)
-msgid "(StrOpt) PLUMgrid Director admin password"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml:34(td)
-msgid "servertimeout = 5"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml:35(td)
-msgid "(IntOpt) PLUMgrid Director server timeout"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml:38(td)
-msgid "username = username"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml:39(td)
-msgid "(StrOpt) PLUMgrid Director admin username"
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml:8(caption)
-msgid "Description of configuration options for cfn_api"
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml:22(td)
-msgid "instance_connection_https_validate_certificates = 1"
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml:23(td)
-msgid "(StrOpt) Instance connection to CFN/CW API validate certs if SSL is used."
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml:26(td)
-msgid "instance_connection_is_secure = 0"
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml:27(td)
-msgid "(StrOpt) Instance connection to CFN/CW API via https."
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml:30(th)
-msgid "[heat_api_cfn]"
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml:34(td) ./doc/common/tables/heat-cloudwatch_api.xml:30(td) ./doc/common/tables/heat-api.xml:104(td)
-msgid "(IntOpt) Number of backlog requests to configure the socket with."
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml:38(td) ./doc/common/tables/heat-cloudwatch_api.xml:34(td) ./doc/common/tables/glance-common.xml:35(td) ./doc/common/tables/heat-api.xml:108(td)
-msgid "(StrOpt) Address to bind the server. Useful when selecting a particular network interface."
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml:41(td)
-msgid "bind_port = 8000"
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml:42(td) ./doc/common/tables/heat-cloudwatch_api.xml:38(td) ./doc/common/tables/glance-common.xml:39(td) ./doc/common/tables/heat-api.xml:112(td)
-msgid "(IntOpt) The port on which the server will listen."
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml:46(td) ./doc/common/tables/heat-cloudwatch_api.xml:42(td) ./doc/common/tables/heat-api.xml:116(td)
-msgid "(StrOpt) Location of the SSL certificate file to use for SSL mode."
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml:50(td) ./doc/common/tables/heat-cloudwatch_api.xml:46(td) ./doc/common/tables/heat-api.xml:120(td)
-msgid "(StrOpt) Location of the SSL key file to use for enabling SSL mode."
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml:53(td) ./doc/common/tables/trove-api.xml:66(td) ./doc/common/tables/neutron-api.xml:42(td) ./doc/common/tables/cinder-api.xml:46(td) ./doc/common/tables/glance-wsgi.xml:30(td) ./doc/common/tables/heat-cloudwatch_api.xml:49(td) ./doc/common/tables/heat-api.xml:123(td) ./doc/common/tables/nova-api.xml:42(td)
-msgid "max_header_line = 16384"
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml:54(td) ./doc/common/tables/cinder-api.xml:47(td) ./doc/common/tables/heat-api.xml:124(td) ./doc/common/tables/nova-api.xml:43(td)
-msgid "(IntOpt) Maximum line size of message headers to be accepted. max_header_line may need to be increased when using large tokens (typically those generated by the Keystone v3 API with big service catalogs)."
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml:57(td) ./doc/common/tables/heat-cloudwatch_api.xml:53(td) ./doc/common/tables/heat-api.xml:127(td)
-msgid "workers = 0"
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml:58(td) ./doc/common/tables/heat-cloudwatch_api.xml:54(td) ./doc/common/tables/heat-api.xml:128(td)
-msgid "(IntOpt) Number of workers for Heat service."
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml:65(td) ./doc/common/tables/heat-cloudwatch_api.xml:61(td) ./doc/common/tables/nova-wsgi.xml:27(td) ./doc/common/tables/cinder-common.xml:175(td) ./doc/common/tables/cinder-ssl.xml:23(td) ./doc/common/tables/heat-api.xml:146(td) ./doc/common/tables/neutron-ssl.xml:23(td) ./doc/common/tables/neutron-ssl.xml:38(td) ./doc/common/tables/trove-ssl.xml:23(td) ./doc/common/tables/ceilometer-ssl.xml:23(td)
-msgid "(StrOpt) CA certificate file to use to verify connecting clients"
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml:69(td) ./doc/common/tables/heat-cloudwatch_api.xml:65(td) ./doc/common/tables/cinder-common.xml:179(td) ./doc/common/tables/cinder-ssl.xml:27(td) ./doc/common/tables/heat-api.xml:150(td) ./doc/common/tables/neutron-ssl.xml:27(td) ./doc/common/tables/neutron-ssl.xml:42(td) ./doc/common/tables/trove-ssl.xml:27(td) ./doc/common/tables/ceilometer-ssl.xml:27(td)
-msgid "(StrOpt) Certificate file to use when starting the server securely"
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml:73(td) ./doc/common/tables/heat-cloudwatch_api.xml:69(td) ./doc/common/tables/cinder-common.xml:183(td) ./doc/common/tables/cinder-ssl.xml:31(td) ./doc/common/tables/heat-api.xml:154(td) ./doc/common/tables/neutron-ssl.xml:31(td) ./doc/common/tables/neutron-ssl.xml:46(td) ./doc/common/tables/trove-ssl.xml:31(td) ./doc/common/tables/ceilometer-ssl.xml:31(td)
-msgid "(StrOpt) Private key file to use when starting the server securely"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:8(caption)
-msgid "Description of configuration options for hypervisor"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:22(td)
-msgid "default_ephemeral_format = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:23(td)
-msgid "(StrOpt) The default format an ephemeral_volume will be formatted with on creation."
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:26(td)
-msgid "force_raw_images = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:27(td)
-msgid "(BoolOpt) Force backing images to raw format"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:30(td)
-msgid "preallocate_images = none"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:31(td)
-msgid "(StrOpt) VM image preallocation mode: \"none\" =&gt; no storage provisioning is done up front, \"space\" =&gt; storage is fully allocated at instance start"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:34(td)
-msgid "rescue_timeout = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:35(td)
-msgid "(IntOpt) Automatically unrescue an instance after N seconds. Set to 0 to disable."
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:38(td)
-msgid "timeout_nbd = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:39(td)
-msgid "(IntOpt) Amount of time, in seconds, to wait for NBD device start up."
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:42(td)
-msgid "use_cow_images = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:43(td)
-msgid "(BoolOpt) Whether to use cow images"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:46(td)
-msgid "vcpu_pin_set = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:47(td)
-msgid "(StrOpt) Defines which pcpus that instance vcpus can use. For example, \"4-12,^8,15\""
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:50(td)
-msgid "virt_mkfs = []"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:51(td)
-msgid "(MultiStrOpt) Name of the mkfs commands for ephemeral device. The format is &lt;os_type&gt;=&lt;mkfs command&gt;"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:57(td)
-msgid "block_migration_flag = VIR_MIGRATE_UNDEFINE_SOURCE, VIR_MIGRATE_PEER2PEER, VIR_MIGRATE_NON_SHARED_INC"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:58(td)
-msgid "(StrOpt) Migration flags to be set for block migration"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:61(td)
-msgid "disk_cachemodes ="
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:62(td)
-msgid "(ListOpt) Specific cachemodes to use for different disk types e.g: file=directsync,block=none"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:65(td)
-msgid "images_rbd_ceph_conf ="
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:66(td)
-msgid "(StrOpt) Path to the ceph configuration file to use"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:69(td)
-msgid "images_rbd_pool = rbd"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:70(td)
-msgid "(StrOpt) The RADOS pool in which rbd volumes are stored"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:73(td)
-msgid "images_type = default"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:74(td)
-msgid "(StrOpt) VM Images format. Acceptable values are: raw, qcow2, lvm, rbd, default. If default is specified, then use_cow_images flag is used instead of this one."
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:77(td)
-msgid "images_volume_group = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:78(td)
-msgid "(StrOpt) LVM Volume Group that is used for VM images, when you specify images_type=lvm."
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:81(td)
-msgid "inject_key = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:82(td)
-msgid "(BoolOpt) Inject the ssh public key at boot time"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:85(td)
-msgid "inject_partition = -2"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:86(td)
-msgid "(IntOpt) The partition to inject to : -2 =&gt; disable, -1 =&gt; inspect (libguestfs only), 0 =&gt; not partitioned, &gt;0 =&gt; partition number"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:89(td)
-msgid "inject_password = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:90(td)
-msgid "(BoolOpt) Inject the admin password at boot time, without an agent."
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:93(td)
-msgid "iscsi_use_multipath = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:94(td)
-msgid "(BoolOpt) Use multipath connection of the iSCSI volume"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:97(td)
-msgid "iser_use_multipath = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:98(td)
-msgid "(BoolOpt) Use multipath connection of the iSER volume"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:101(td)
-msgid "rescue_image_id = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:102(td)
-msgid "(StrOpt) Rescue ami image"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:105(td)
-msgid "rescue_kernel_id = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:106(td)
-msgid "(StrOpt) Rescue aki image"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:109(td)
-msgid "rescue_ramdisk_id = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:110(td)
-msgid "(StrOpt) Rescue ari image"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:113(td)
-msgid "snapshot_compression = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:114(td)
-msgid "(BoolOpt) Compress snapshot images when possible. This currently applies exclusively to qcow2 images"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:117(td)
-msgid "snapshot_image_format = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:118(td)
-msgid "(StrOpt) Snapshot image format (valid options are : raw, qcow2, vmdk, vdi). Defaults to same as source image"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:121(td)
-msgid "sparse_logical_volumes = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:122(td)
-msgid "(BoolOpt) Create sparse logical volumes (with virtualsize) if this flag is set to True."
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:125(td)
-msgid "use_usb_tablet = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:126(td)
-msgid "(BoolOpt) Sync virtual and real mouse cursors in Windows VMs"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:129(td)
-msgid "use_virtio_for_bridges = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml:130(td)
-msgid "(BoolOpt) Use virtio for bridge interfaces with KVM/QEMU"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml:8(caption) ./doc/common/tables/heat-rabbitmq.xml:8(caption) ./doc/common/tables/glance-rabbitmq.xml:8(caption) ./doc/common/tables/neutron-rabbitmq.xml:8(caption) ./doc/common/tables/ceilometer-rabbitmq.xml:8(caption) ./doc/common/tables/nova-rabbitmq.xml:8(caption)
-msgid "Description of configuration options for rabbitmq"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml:23(td) ./doc/common/tables/heat-rabbitmq.xml:39(td)
-msgid "(BoolOpt) use H/A queues in RabbitMQ (x-ha-policy: all).You need to wipe RabbitMQ database when changing this option."
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml:27(td) ./doc/common/tables/heat-rabbitmq.xml:43(td) ./doc/common/tables/neutron-rabbitmq.xml:27(td) ./doc/common/tables/ceilometer-rabbitmq.xml:47(td)
-msgid "(StrOpt) The RabbitMQ broker address where a single node is used"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml:31(td) ./doc/common/tables/heat-rabbitmq.xml:47(td) ./doc/common/tables/neutron-rabbitmq.xml:31(td) ./doc/common/tables/ceilometer-rabbitmq.xml:51(td)
-msgid "(ListOpt) RabbitMQ HA cluster host:port pairs"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml:35(td) ./doc/common/tables/heat-rabbitmq.xml:51(td)
-msgid "(IntOpt) maximum retries with trying to connect to RabbitMQ (the default of 0 implies an infinite retry count)"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml:39(td) ./doc/common/tables/heat-rabbitmq.xml:55(td)
-msgid "(StrOpt) the RabbitMQ password"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml:43(td) ./doc/common/tables/heat-rabbitmq.xml:59(td) ./doc/common/tables/neutron-rabbitmq.xml:43(td) ./doc/common/tables/ceilometer-rabbitmq.xml:63(td)
-msgid "(IntOpt) The RabbitMQ broker port where a single node is used"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml:47(td) ./doc/common/tables/heat-rabbitmq.xml:63(td)
-msgid "(IntOpt) how long to backoff for between retries when connecting to RabbitMQ"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml:51(td) ./doc/common/tables/heat-rabbitmq.xml:67(td)
-msgid "(IntOpt) how frequently to retry connecting with RabbitMQ"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml:55(td) ./doc/common/tables/heat-rabbitmq.xml:71(td)
-msgid "(BoolOpt) connect over SSL for RabbitMQ"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml:59(td) ./doc/common/tables/heat-rabbitmq.xml:75(td)
-msgid "(StrOpt) the RabbitMQ userid"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml:63(td) ./doc/common/tables/heat-rabbitmq.xml:79(td)
-msgid "(StrOpt) the RabbitMQ virtual host"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:7(literal)
-msgid "[filter:tempurl]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:18(td)
-msgid "use = egg:swift#tempurl"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:21(td)
-msgid "methods = GET HEAD PUT"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:21(td)
-msgid "HTTP methods allowed with Temporary URLs"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:24(td)
-msgid "incoming_remove_headers = x-timestamp"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:24(td)
-msgid "Headers to remove from incoming requests. Simply a whitespace delimited list of header names and names can optionally end with '*' to indicate a prefix match."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:28(td)
-msgid "incoming_allow_headers ="
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:28(td)
-msgid "Headers allowed as exceptions to incoming_remove_headers. Simply a whitespace delimited list of header names and names can optionally end with '*' to indicate a prefix match."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:33(td)
-msgid "outgoing_remove_headers = x-object-meta-*"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:33(td)
-msgid "Headers to remove from outgoing responses. Simply a whitespace delimited list of header names and names can optionally end with '*' to indicate a prefix match."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:38(td)
-msgid "outgoing_allow_headers = x-object-meta-public-*"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:38(td)
-msgid "Headers allowed as exceptions to outgoing_allow_headers. Simply a whitespace delimited list of header names and names can optionally end with '*' to indicate a prefix match."
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml:8(caption) ./doc/common/tables/neutron-api.xml:8(caption) ./doc/common/tables/cinder-api.xml:8(caption) ./doc/common/tables/ceilometer-api.xml:8(caption) ./doc/common/tables/heat-api.xml:8(caption) ./doc/common/tables/nova-api.xml:8(caption) ./doc/common/tables/glance-api.xml:8(caption) ./doc/common/tables/keystone-api.xml:8(caption)
-msgid "Description of configuration options for api"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml:22(td)
-msgid "admin_roles = admin"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml:26(td)
-msgid "api_extensions_path = trove/extensions/routes"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml:27(td)
-msgid "(StrOpt) Path to extensions."
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml:30(td) ./doc/common/tables/neutron-api.xml:38(td) ./doc/common/tables/cinder-api.xml:22(td) ./doc/common/tables/nova-wsgi.xml:22(td) ./doc/common/tables/heat-api.xml:134(td)
-msgid "api_paste_config = api-paste.ini"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml:31(td)
-msgid "(StrOpt) File name for the paste.deploy config for trove-api."
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml:34(td)
-msgid "bind_port = 8779"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml:35(td) ./doc/common/tables/trove-api.xml:47(td) ./doc/common/tables/trove-api.xml:51(td) ./doc/common/tables/trove-api.xml:55(td) ./doc/common/tables/trove-api.xml:59(td) ./doc/common/tables/trove-api.xml:63(td) ./doc/common/tables/trove-api.xml:79(td) ./doc/common/tables/trove-api.xml:87(td) ./doc/common/tables/trove-api.xml:103(td) ./doc/common/tables/trove-taskmanager.xml:43(td) ./doc/common/tables/trove-taskmanager.xml:47(td) ./doc/common/tables/trove-taskmanager.xml:51(td) ./doc/common/tables/trove-taskmanager.xml:55(td) ./doc/common/tables/trove-taskmanager.xml:59(td) ./doc/common/tables/trove-backup.xml:71(td) ./doc/common/tables/trove-volume.xml:39(td) ./doc/common/tables/trove-volume.xml:47(td) ./doc/common/tables/trove-database.xml:27(td) ./doc/common/tables/trove-rpc.xml:39(td) ./doc/common/tables/trove-rpc.xml:43(td) ./doc/common/tables/trove-common.xml:23(td) ./doc/common/tables/trove-common.xml:27(td) ./doc/common/tables/trove-common.xml:47(td) ./doc/common/tables/trove-dns.xml:71(td) ./doc/common/tables/trove-dns.xml:75(td) ./doc/common/tables/trove-heat.xml:23(td) ./doc/common/tables/trove-guestagent.xml:23(td) ./doc/common/tables/trove-guestagent.xml:27(td) ./doc/common/tables/trove-guestagent.xml:31(td)
-msgid "(IntOpt) No help text available for this option."
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml:38(td)
-msgid "db_api_implementation = trove.db.sqlalchemy.api"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml:42(td)
-msgid "hostname_require_ipv4 = True"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml:43(td)
-msgid "(BoolOpt) Require user hostnames to be IPv4 addresses."
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml:46(td)
-msgid "http_delete_rate = 200"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml:50(td)
-msgid "http_get_rate = 200"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml:54(td)
-msgid "http_post_rate = 200"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml:58(td)
-msgid "http_put_rate = 200"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml:62(td)
-msgid "instances_page_size = 20"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml:67(td) ./doc/common/tables/glance-wsgi.xml:31(td)
-msgid "(IntOpt) Maximum line size of message headers to be accepted. max_header_line may need to be increased when using large tokens (typically those generated by the Keystone v3 API with big service catalogs"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml:70(td)
-msgid "region = LOCAL_DEV"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml:71(td)
-msgid "(StrOpt) The region this service is located."
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml:74(td) ./doc/common/tables/glance-wsgi.xml:34(td) ./doc/common/tables/neutron-wsgi.xml:30(td) ./doc/common/tables/nova-wsgi.xml:38(td) ./doc/common/tables/cinder-common.xml:198(td) ./doc/common/tables/keystone-api.xml:86(td)
-msgid "tcp_keepidle = 600"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml:75(td) ./doc/common/tables/neutron-wsgi.xml:31(td) ./doc/common/tables/nova-wsgi.xml:39(td) ./doc/common/tables/cinder-common.xml:199(td)
-msgid "(IntOpt) Sets the value of TCP_KEEPIDLE in seconds for each server socket. Not supported on OS X."
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml:78(td)
-msgid "trove_api_workers = None"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml:82(td)
-msgid "trove_auth_url = http://0.0.0.0:5000/v2.0"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml:86(td)
-msgid "trove_conductor_workers = 1"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml:90(td)
-msgid "trove_security_group_name_prefix = SecGroup"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml:94(td)
-msgid "trove_security_group_rule_cidr = 0.0.0.0/0"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml:98(td)
-msgid "trove_security_groups_support = True"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml:102(td)
-msgid "users_page_size = 20"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml:8(caption) ./doc/common/tables/trove-quota.xml:8(caption) ./doc/common/tables/heat-quota.xml:8(caption) ./doc/common/tables/nova-quota.xml:8(caption)
-msgid "Description of configuration options for quota"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml:22(td) ./doc/common/tables/nova-policy.xml:34(td)
-msgid "max_age = 0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml:23(td)
-msgid "(IntOpt) number of seconds between subsequent usage refreshes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml:26(td)
-msgid "quota_driver = cinder.quota.DbQuotaDriver"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml:27(td)
-msgid "(StrOpt) default driver to use for quota checks"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml:30(td)
-msgid "quota_gigabytes = 1000"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml:31(td)
-msgid "(IntOpt) number of volume gigabytes (snapshots are also included) allowed per project"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml:34(td)
-msgid "quota_snapshots = 10"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml:35(td)
-msgid "(IntOpt) number of volume snapshots allowed per project"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml:38(td)
-msgid "quota_volumes = 10"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml:39(td)
-msgid "(IntOpt) number of volumes allowed per project"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml:42(td) ./doc/common/tables/nova-policy.xml:66(td)
-msgid "reservation_expire = 86400"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml:43(td)
-msgid "(IntOpt) number of seconds until a reservation expires"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml:46(td)
-msgid "use_default_quota_class = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml:47(td)
-msgid "(BoolOpt) whether to use default quota class for default quota"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml:7(literal) ./doc/common/tables/swift-account-server-filter-healthcheck.xml:7(literal) ./doc/common/tables/swift-container-server-filter-healthcheck.xml:7(literal) ./doc/common/tables/swift-object-server-filter-healthcheck.xml:7(literal)
-msgid "[filter:healthcheck]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml:18(td) ./doc/common/tables/swift-account-server-filter-healthcheck.xml:18(td) ./doc/common/tables/swift-container-server-filter-healthcheck.xml:18(td) ./doc/common/tables/swift-object-server-filter-healthcheck.xml:18(td)
-msgid "use = egg:swift#healthcheck"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml:21(td) ./doc/common/tables/swift-account-server-filter-healthcheck.xml:21(td) ./doc/common/tables/swift-container-server-filter-healthcheck.xml:21(td) ./doc/common/tables/swift-object-server-filter-healthcheck.xml:21(td)
-msgid "disable_path ="
-msgstr ""
-
-#: ./doc/common/tables/nova-console.xml:8(caption)
-msgid "Description of configuration options for console"
-msgstr ""
-
-#: ./doc/common/tables/nova-console.xml:22(td)
-msgid "console_public_hostname = oslo"
-msgstr ""
-
-#: ./doc/common/tables/nova-console.xml:23(td)
-msgid "(StrOpt) Publicly visible name for this console host"
-msgstr ""
-
-#: ./doc/common/tables/nova-console.xml:26(td)
-msgid "console_token_ttl = 600"
-msgstr ""
-
-#: ./doc/common/tables/nova-console.xml:27(td)
-msgid "(IntOpt) How many seconds before deleting tokens"
-msgstr ""
-
-#: ./doc/common/tables/nova-console.xml:30(td)
-msgid "consoleauth_manager = nova.consoleauth.manager.ConsoleAuthManager"
-msgstr ""
-
-#: ./doc/common/tables/nova-console.xml:31(td)
-msgid "(StrOpt) Manager for console auth"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml:8(caption)
-msgid "Description of configuration options for events"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml:19(th)
-msgid "[event]"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml:22(td)
-msgid "definitions_cfg_file = event_definitions.yaml"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml:23(td)
-msgid "(StrOpt) Configuration file for event definitions."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml:26(td)
-msgid "drop_unmatched_notifications = False"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml:27(td)
-msgid "(BoolOpt) Drop notifications if no event definition matches. (Otherwise, we convert them with just the default traits)"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml:30(th)
-msgid "[notification]"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml:33(td)
-msgid "ack_on_event_error = True"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml:34(td)
-msgid "(BoolOpt) Acknowledge message when event persistence fails."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml:37(td)
-msgid "store_events = False"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml:38(td)
-msgid "(BoolOpt) Save event details."
-msgstr ""
-
-#: ./doc/common/tables/keystone-os_inherit.xml:8(caption)
-msgid "Description of configuration options for os_inherit"
-msgstr ""
-
-#: ./doc/common/tables/keystone-os_inherit.xml:19(th)
-msgid "[os_inherit]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-os_inherit.xml:22(td) ./doc/common/tables/keystone-cache.xml:38(td) ./doc/common/tables/neutron-fwaas.xml:22(td) ./doc/common/tables/nova-spice.xml:26(td) ./doc/common/tables/nova-apiv3.xml:22(td) ./doc/common/tables/nova-rdp.xml:22(td)
-msgid "enabled = False"
-msgstr ""
-
-#: ./doc/common/tables/keystone-os_inherit.xml:23(td)
-msgid "(BoolOpt) role-assignment inheritance to projects from owning domain can be optionally enabled."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients.xml:8(caption)
-msgid "Description of configuration options for clients"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients.xml:22(td)
-msgid "region_name_for_services = None"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients.xml:23(td)
-msgid "(StrOpt) Default region name used to get services endpoints."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients.xml:26(th)
-msgid "[clients]"
-msgstr ""
-
-#: ./doc/common/tables/heat-notification.xml:8(caption) ./doc/common/tables/keystone-notification.xml:8(caption)
-msgid "Description of configuration options for notification"
-msgstr ""
-
-#: ./doc/common/tables/heat-notification.xml:22(td) ./doc/common/tables/keystone-notification.xml:22(td)
-msgid "onready = None"
-msgstr ""
-
-#: ./doc/common/tables/heat-notification.xml:23(td)
-msgid "(StrOpt) onready allows you to send a notification when the heat processes are ready to serve. This is either a module with the notify() method or a shell command. To enable notifications with systemd, one may use the 'systemd-notify --ready' shell command or the 'heat.common.systemd' notification module."
-msgstr ""
-
-#: ./doc/common/tables/keystone-assignment.xml:8(caption)
-msgid "Description of configuration options for assignment"
-msgstr ""
-
-#: ./doc/common/tables/keystone-assignment.xml:19(th)
-msgid "[assignment]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-assignment.xml:22(td) ./doc/common/tables/keystone-token.xml:26(td)
-msgid "cache_time = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-assignment.xml:23(td)
-msgid "(IntOpt) TTL (in seconds) to cache assignment data. This has no effect unless global caching is enabled."
-msgstr ""
-
-#: ./doc/common/tables/keystone-assignment.xml:26(td) ./doc/common/tables/keystone-token.xml:30(td) ./doc/common/tables/keystone-revoke.xml:22(td)
-msgid "caching = True"
-msgstr ""
-
-#: ./doc/common/tables/keystone-assignment.xml:27(td)
-msgid "(BoolOpt) Toggle for assignment caching. This has no effect unless global caching is enabled."
-msgstr ""
-
-#: ./doc/common/tables/keystone-assignment.xml:30(td)
-msgid "driver = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-assignment.xml:31(td)
-msgid "(StrOpt) Keystone Assignment backend driver."
-msgstr ""
-
-#: ./doc/common/tables/keystone-assignment.xml:35(td)
-msgid "(IntOpt) Maximum number of entities that will be returned in an assignment collection."
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:22(td)
-msgid "bindir = /usr/local/bin"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:23(td)
-msgid "(StrOpt) Directory where nova binaries are installed"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:26(td)
-msgid "compute_topic = compute"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:27(td)
-msgid "(StrOpt) The topic compute nodes listen on"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:30(td)
-msgid "console_topic = console"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:31(td)
-msgid "(StrOpt) The topic console proxy nodes listen on"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:34(td)
-msgid "consoleauth_topic = consoleauth"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:35(td)
-msgid "(StrOpt) The topic console auth proxy nodes listen on"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:43(td)
-msgid "(StrOpt) Name of this node. This can be an opaque identifier. It is not necessarily a hostname, FQDN, or IP address. However, the node name must be valid within an AMQP key, and if using ZeroMQ, a valid hostname, FQDN, or IP address"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:54(td) ./doc/common/tables/cinder-common.xml:118(td)
-msgid "my_ip = 10.0.0.1"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:55(td)
-msgid "(StrOpt) IP address of this host"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:58(td) ./doc/common/tables/cinder-rpc.xml:74(td) ./doc/common/tables/keystone-amqp.xml:38(td) ./doc/common/tables/neutron-notifier.xml:30(td) ./doc/common/tables/glance-amqp.xml:30(td) ./doc/common/tables/heat-amqp.xml:50(td) ./doc/common/tables/ceilometer-amqp.xml:30(td) ./doc/common/tables/trove-amqp.xml:58(td)
-msgid "notification_driver = []"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:59(td) ./doc/common/tables/cinder-rpc.xml:75(td) ./doc/common/tables/keystone-amqp.xml:39(td) ./doc/common/tables/glance-amqp.xml:31(td)
-msgid "(MultiStrOpt) Driver or drivers to handle sending notifications."
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:62(td) ./doc/common/tables/cinder-rpc.xml:78(td) ./doc/common/tables/keystone-amqp.xml:42(td) ./doc/common/tables/neutron-notifier.xml:34(td) ./doc/common/tables/glance-amqp.xml:34(td) ./doc/common/tables/heat-amqp.xml:54(td) ./doc/common/tables/ceilometer-amqp.xml:34(td) ./doc/common/tables/trove-amqp.xml:66(td)
-msgid "notification_topics = notifications"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:63(td) ./doc/common/tables/cinder-rpc.xml:79(td) ./doc/common/tables/keystone-amqp.xml:43(td) ./doc/common/tables/glance-amqp.xml:35(td)
-msgid "(ListOpt) AMQP topic used for OpenStack notifications."
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:66(td)
-msgid "notify_api_faults = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:67(td)
-msgid "(BoolOpt) If set, send api.fault notifications on caught exceptions in the API service."
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:70(td)
-msgid "notify_on_state_change = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:71(td)
-msgid "(StrOpt) If set, send compute.instance.update notifications on instance state changes. Valid values are None for no notifications, \"vm_state\" for notifications on VM state changes, or \"vm_and_task_state\" for notifications on VM and task state changes."
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:78(td)
-msgid "pybasedir = /usr/lib/python/site-packages"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:79(td)
-msgid "(StrOpt) Directory where the nova python module is installed"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:82(td) ./doc/common/tables/cinder-common.xml:146(td) ./doc/common/tables/trove-rpc.xml:46(td)
-msgid "report_interval = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:83(td)
-msgid "(IntOpt) Seconds between nodes reporting state to datastore"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:86(td)
-msgid "rootwrap_config = /etc/nova/rootwrap.conf"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:87(td) ./doc/common/tables/cinder-common.xml:155(td)
-msgid "(StrOpt) Path to the rootwrap configuration file to use for running commands as root"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:90(td) ./doc/common/tables/cinder-common.xml:162(td)
-msgid "service_down_time = 60"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:91(td)
-msgid "(IntOpt) Maximum time since last check-in for up service"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:94(td)
-msgid "state_path = $pybasedir"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:95(td)
-msgid "(StrOpt) Top-level directory for maintaining nova's state"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:98(td)
-msgid "tempdir = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:99(td)
-msgid "(StrOpt) Explicitly specify the temporary working directory"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:102(td) ./doc/common/tables/cinder-rpc.xml:230(td) ./doc/common/tables/keystone-amqp.xml:66(td) ./doc/common/tables/glance-amqp.xml:54(td)
-msgid "transport_url = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml:103(td) ./doc/common/tables/cinder-rpc.xml:231(td) ./doc/common/tables/keystone-amqp.xml:67(td) ./doc/common/tables/glance-amqp.xml:55(td)
-msgid "(StrOpt) A URL representing the messaging driver to use and its full configuration. If not set, we fall back to the rpc_backend option and driver specific configuration."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-updater.xml:7(literal)
-msgid "[object-updater]"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-updater.xml:18(td)
-msgid "log_name = object-updater"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-updater.xml:33(td) ./doc/common/tables/swift-object-server-object-replicator.xml:39(td) ./doc/common/tables/swift-object-expirer-object-expirer.xml:30(td)
-msgid "concurrency = 1"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-updater.xml:36(td) ./doc/common/tables/swift-object-server-object-replicator.xml:57(td)
-msgid "node_timeout = &lt;whatever's in the DEFAULT section or 10&gt;"
-msgstr ""
-
-#: ./doc/common/tables/glance-zmq.xml:8(caption)
-msgid "Description of configuration options for zmq"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metering_agent.xml:8(caption)
-msgid "Description of configuration options for metering_agent"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metering_agent.xml:22(td)
-msgid "driver = neutron.services.metering.drivers.noop.noop_driver.NoopMeteringDriver"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metering_agent.xml:23(td)
-msgid "(StrOpt) Metering driver"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metering_agent.xml:26(td)
-msgid "measure_interval = 30"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metering_agent.xml:27(td)
-msgid "(IntOpt) Interval between two metering measures"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metering_agent.xml:33(td)
-msgid "report_interval = 30"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metering_agent.xml:34(td)
-msgid "(FloatOpt) Seconds between nodes reporting state to server; should be less than agent_down_time, best if it is half or less than agent_down_time."
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml:8(caption)
-msgid "Description of configuration options for taskmanager"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml:22(td)
-msgid "cloudinit_location = /etc/trove/cloudinit"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml:23(td)
-msgid "(StrOpt) Path to folder with cloudinit scripts."
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml:26(td)
-msgid "datastore_manager = None"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml:27(td)
-msgid "(StrOpt) Manager class in guestagent, setup by taskmanager on instance provision."
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml:30(td)
-msgid "datastore_registry_ext = {}"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml:31(td)
-msgid "(DictOpt) Extension for default datastore managers. Allows to use custom managers for each of datastore supported in trove."
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml:34(td)
-msgid "exists_notification_ticks = 360"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml:35(td)
-msgid "(IntOpt) Number of report_intervals to wait between pushing events (see report_interval)."
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml:38(td)
-msgid "exists_notification_transformer = None"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml:39(td)
-msgid "(StrOpt) Transformer for exists notifications."
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml:42(td)
-msgid "reboot_time_out = 120"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml:46(td)
-msgid "resize_time_out = 600"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml:50(td)
-msgid "revert_time_out = 600"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml:54(td)
-msgid "server_delete_time_out = 60"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml:58(td)
-msgid "state_change_wait_time = 180"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml:62(td)
-msgid "update_status_on_fail = False"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml:63(td)
-msgid "(BoolOpt) If instance fails to become active, taskmanager updates statuses, service status = FAILED_TIMEOUT_GUESTAGENT, instance task status = BUILDING_ERROR_TIMEOUT_GA."
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml:66(td) ./doc/common/tables/trove-guestagent.xml:66(td)
-msgid "usage_sleep_time = 5"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml:67(td) ./doc/common/tables/trove-guestagent.xml:67(td)
-msgid "(IntOpt) Time to sleep during the check active guest."
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml:70(td)
-msgid "use_heat = False"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml:74(td)
-msgid "use_nova_server_volume = False"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml:78(td)
-msgid "verify_swift_checksum_on_restore = True"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml:79(td)
-msgid "(BoolOpt) Enable verification of swift checksum before starting restore; makes sure the checksum of original backup matches checksum of the swift backup file."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml:7(literal)
-msgid "[filter:account-quotas]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml:18(td)
-msgid "use = egg:swift#account_quotas"
-msgstr ""
-
-#: ./doc/common/tables/keystone-zeromq.xml:8(caption) ./doc/common/tables/trove-zeromq.xml:8(caption) ./doc/common/tables/heat-zeromq.xml:8(caption) ./doc/common/tables/nova-zeromq.xml:8(caption) ./doc/common/tables/neutron-zeromq.xml:8(caption)
-msgid "Description of configuration options for zeromq"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:7(literal) ./doc/common/tables/swift-object-expirer-app-proxy-server.xml:7(literal)
-msgid "[app:proxy-server]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:18(td) ./doc/common/tables/swift-object-expirer-app-proxy-server.xml:18(td)
-msgid "use = egg:swift#proxy"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:21(td)
-msgid "set log_name = proxy-server"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:33(td)
-msgid "log_handoffs = true"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:36(td)
-msgid "recheck_account_existence = 60"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:36(td)
-msgid "Cache timeout in seconds to send memcached for account existence"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:39(td)
-msgid "recheck_container_existence = 60"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:39(td)
-msgid "Cache timeout in seconds to send memcached for container existence"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:42(td)
-msgid "object_chunk_size = 8192"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:42(td)
-msgid "Chunk size to read from object servers"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:45(td)
-msgid "client_chunk_size = 8192"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:45(td)
-msgid "Chunk size to read from clients"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:51(td)
-msgid "recoverable_node_timeout = node_timeout"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:51(td)
-msgid "Request timeout to external services for requests that, on failure, can be recovered from. For example, object GET. from a client external services"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:57(td)
-msgid "post_quorum_timeout = 0.5"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:60(td) ./doc/common/tables/swift-account-server-account-replicator.xml:45(td)
-msgid "error_suppression_interval = 60"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:60(td) ./doc/common/tables/swift-account-server-account-replicator.xml:45(td)
-msgid "Time in seconds that must elapse since the last error for a node to be considered no longer error limited"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:63(td) ./doc/common/tables/swift-account-server-account-replicator.xml:48(td)
-msgid "error_suppression_limit = 10"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:63(td) ./doc/common/tables/swift-account-server-account-replicator.xml:48(td)
-msgid "Error count to consider a node error limited"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:66(td)
-msgid "allow_account_management = false"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:66(td)
-msgid "Whether account PUTs and DELETEs are even callable"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:69(td)
-msgid "object_post_as_copy = true"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:69(td)
-msgid "Set object_post_as_copy = false to turn on fast posts where only the metadata changes are stored anew and the original data file is kept in place. This makes for quicker posts; but since the container metadata isn't updated in this mode, features like container sync won't be able to sync posts."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:72(td)
-msgid "account_autocreate = false"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:72(td)
-msgid "If set to 'true' authorized accounts that do not yet exist within the Swift cluster will be automatically created."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:75(td)
-msgid "max_containers_per_account = 0"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:75(td)
-msgid "If set to a positive value, trying to create a container when the account already has at least this maximum containers will result in a 403 Forbidden. Note: This is a soft limit, meaning a user might exceed the cap for recheck_account_existence before the 403s kick in."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:78(td)
-msgid "max_containers_whitelist ="
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:78(td)
-msgid "is a comma separated list of account names that ignore the max_containers_per_account cap."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:81(td)
-msgid "deny_host_headers ="
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:84(td) ./doc/common/tables/swift-account-server-app-account-server.xml:36(td) ./doc/common/tables/swift-container-server-app-container-server.xml:45(td) ./doc/common/tables/swift-object-server-app-object-server.xml:54(td) ./doc/common/tables/swift-object-expirer-object-expirer.xml:21(td)
-msgid "auto_create_account_prefix = ."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:84(td) ./doc/common/tables/swift-account-server-app-account-server.xml:36(td) ./doc/common/tables/swift-container-server-app-container-server.xml:45(td) ./doc/common/tables/swift-object-server-app-object-server.xml:54(td) ./doc/common/tables/swift-object-expirer-object-expirer.xml:21(td)
-msgid "Prefix to use when automatically creating accounts"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:87(td)
-msgid "put_queue_depth = 10"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:90(td)
-msgid "sorting_method = shuffle"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:93(td)
-msgid "timing_expiry = 300"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:96(td)
-msgid "max_large_object_get_time = 86400"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:99(td)
-msgid "request_node_count = 2 * replicas"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:99(td)
-msgid "* replicas Set to the number of nodes to contact for a normal request. You can use '* replicas' at the end to have it use the number given times the number of replicas for the ring being used for the request. conf file for values will only be shown to the list of swift_owners. The exact default definition of a swift_owner is headers&gt; up to the auth system in use, but usually indicates administrative responsibilities. paste.deploy to use for auth. To use tempauth set to: `egg:swift#tempauth` each request"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:102(td)
-msgid "read_affinity = r1z1=100, r1z2=200, r2=300"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:105(td)
-msgid "read_affinity ="
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:108(td)
-msgid "write_affinity = r1, r2"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:111(td)
-msgid "write_affinity ="
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:114(td)
-msgid "write_affinity_node_count = 2 * replicas"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:117(td)
-msgid "swift_owner_headers = x-container-read, x-container-write, x-container-sync-key, x-container-sync-to, x-account-meta-temp-url-key, x-account-meta-temp-url-key-2, x-account-access-control"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml:117(td)
-msgid "the sample These are the headers whose conf file for values will only be shown to the list of swift_owners. The exact default definition of a swift_owner is headers&gt; up to the auth system in use, but usually indicates administrative responsibilities. paste.deploy to use for auth. To use tempauth set to: `egg:swift#tempauth` each request"
-msgstr ""
-
-#: ./doc/common/tables/nova-keymgr.xml:8(caption) ./doc/common/tables/cinder-keymgr.xml:8(caption)
-msgid "Description of configuration options for keymgr"
-msgstr ""
-
-#: ./doc/common/tables/nova-keymgr.xml:19(th) ./doc/common/tables/cinder-keymgr.xml:19(th)
-msgid "[keymgr]"
-msgstr ""
-
-#: ./doc/common/tables/nova-keymgr.xml:22(td)
-msgid "api_class = nova.keymgr.conf_key_mgr.ConfKeyManager"
-msgstr ""
-
-#: ./doc/common/tables/nova-keymgr.xml:23(td) ./doc/common/tables/cinder-keymgr.xml:23(td)
-msgid "(StrOpt) The full class name of the key manager API class"
-msgstr ""
-
-#: ./doc/common/tables/nova-keymgr.xml:26(td) ./doc/common/tables/cinder-keymgr.xml:26(td)
-msgid "fixed_key = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-keymgr.xml:27(td) ./doc/common/tables/cinder-keymgr.xml:27(td)
-msgid "(StrOpt) Fixed key returned by key manager, specified in hex"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml:7(literal)
-msgid "[filter:dlo]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml:18(td)
-msgid "use = egg:swift#dlo"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-slo.xml:30(td)
-msgid "rate_limit_after_segment = 10"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml:21(td) ./doc/common/tables/swift-proxy-server-filter-slo.xml:30(td)
-msgid "Rate limit the download of large object segments after this segment is downloaded."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml:24(td)
-msgid "rate_limit_segments_per_sec = 1"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml:24(td) ./doc/common/tables/swift-proxy-server-filter-slo.xml:33(td)
-msgid "Rate limit large object downloads at this rate. contact for a normal request. You can use '* replicas' at the end to have it use the number given times the number of replicas for the ring being used for the request. paste.deploy to use for auth. To use tempauth set to: `egg:swift#tempauth` each request"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml:27(td) ./doc/common/tables/swift-proxy-server-filter-slo.xml:36(td)
-msgid "max_get_time = 86400"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml:22(td)
-msgid "allow_bulk = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml:23(td)
-msgid "(BoolOpt) Allow the usage of the bulk API"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml:26(td)
-msgid "allow_pagination = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml:27(td)
-msgid "(BoolOpt) Allow the usage of the pagination"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml:30(td)
-msgid "allow_sorting = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml:31(td)
-msgid "(BoolOpt) Allow the usage of the sorting"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml:34(td)
-msgid "api_extensions_path ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml:35(td)
-msgid "(StrOpt) The path for API extensions"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml:39(td)
-msgid "(StrOpt) The API paste config file to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml:43(td)
-msgid "(IntOpt) Max header line to accommodate large tokens"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml:46(td) ./doc/common/tables/ceilometer-api.xml:26(td) ./doc/common/tables/keystone-api.xml:54(td)
-msgid "max_request_body_size = 114688"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml:47(td)
-msgid "(IntOpt) the maximum body size per each request(bytes)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml:50(td)
-msgid "pagination_max_limit = -1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml:51(td)
-msgid "(StrOpt) The maximum number of items returned in a single response, value was 'infinite' or negative integer means no limit"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml:54(td) ./doc/common/tables/nova-periodic.xml:30(td) ./doc/common/tables/cinder-common.xml:158(td)
-msgid "run_external_periodic_tasks = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml:55(td) ./doc/common/tables/nova-periodic.xml:31(td) ./doc/common/tables/cinder-common.xml:159(td)
-msgid "(BoolOpt) Some periodic tasks can be run in a separate process. Should we run them here?"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml:58(td)
-msgid "service_plugins ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml:59(td)
-msgid "(ListOpt) The service plugins Neutron will use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml:62(th)
-msgid "[service_providers]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml:65(td)
-msgid "service_provider = []"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml:66(td)
-msgid "(MultiStrOpt) Defines providers for advanced services using the format: &lt;service_type&gt;:&lt;name&gt;:&lt;driver&gt;[:default]"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-redis.xml:23(td)
-msgid "(StrOpt) Name of this node, which must be valid in an AMQP key. Can be an opaque identifier. For ZeroMQ only, must be a valid host name, FQDN, or IP address."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-swift.xml:8(caption) ./doc/common/tables/trove-swift.xml:8(caption) ./doc/common/tables/glance-swift.xml:8(caption)
-msgid "Description of configuration options for swift"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-swift.xml:22(td)
-msgid "reseller_prefix = AUTH_"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-swift.xml:23(td)
-msgid "(StrOpt) Swift reseller prefix. Must be on par with reseller_prefix in proxy-server.conf."
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml:8(caption)
-msgid "Description of configuration options for hplefthand"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml:22(td)
-msgid "hplefthand_api_url = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml:23(td)
-msgid "(StrOpt) HP LeftHand WSAPI Server Url like https://&lt;LeftHand ip&gt;:8081/lhos"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml:26(td)
-msgid "hplefthand_clustername = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml:27(td)
-msgid "(StrOpt) HP LeftHand cluster name"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml:30(td)
-msgid "hplefthand_debug = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml:31(td)
-msgid "(BoolOpt) Enable HTTP debugging to LeftHand"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml:34(td)
-msgid "hplefthand_iscsi_chap_enabled = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml:35(td)
-msgid "(BoolOpt) Configure CHAP authentication for iSCSI connections (Default: Disabled)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml:38(td)
-msgid "hplefthand_password = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml:39(td)
-msgid "(StrOpt) HP LeftHand Super user password"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml:42(td)
-msgid "hplefthand_username = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml:43(td)
-msgid "(StrOpt) HP LeftHand Super user username"
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml:8(caption) ./doc/common/tables/glance-testing.xml:8(caption) ./doc/common/tables/neutron-testing.xml:8(caption)
-msgid "Description of configuration options for testing"
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml:22(td) ./doc/common/tables/cinder-rpc.xml:22(td) ./doc/common/tables/keystone-rpc.xml:22(td)
-msgid "allowed_rpc_exception_modules = oslo.messaging.exceptions, nova.exception, cinder.exception, exceptions"
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml:27(td)
-msgid "(StrOpt) Enable eventlet backdoor. Acceptable values are 0, &lt;port&gt; and &lt;start&gt;:&lt;end&gt;, where 0 results in listening on a random tcp port number, &lt;port&gt; results in listening on the specified port number and not enabling backdoorif it is in use and &lt;start&gt;:&lt;end&gt; results in listening on the smallest unused port number within the specified range of port numbers. The chosen port is displayed in the service's log file."
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml:30(td)
-msgid "fake_call = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml:31(td)
-msgid "(BoolOpt) If True, skip using the queue and make local calls"
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml:34(td)
-msgid "fake_network = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml:35(td)
-msgid "(BoolOpt) If passed, use fake network devices and addresses"
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml:38(td) ./doc/common/tables/cinder-rpc.xml:42(td) ./doc/common/tables/heat-amqp.xml:42(td) ./doc/common/tables/glance-rabbitmq.xml:26(td) ./doc/common/tables/keystone-rabbit.xml:22(td) ./doc/common/tables/ceilometer-rabbitmq.xml:22(td) ./doc/common/tables/neutron-testing.xml:26(td) ./doc/common/tables/trove-amqp.xml:38(td)
-msgid "fake_rabbit = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml:39(td) ./doc/common/tables/cinder-rpc.xml:43(td) ./doc/common/tables/glance-rabbitmq.xml:27(td) ./doc/common/tables/keystone-rabbit.xml:23(td)
-msgid "(BoolOpt) If passed, use a fake RabbitMQ provider."
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml:42(td) ./doc/common/tables/cinder-common.xml:110(td)
-msgid "monkey_patch = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml:43(td)
-msgid "(BoolOpt) Whether to log monkey patching"
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml:46(td)
-msgid "monkey_patch_modules = nova.api.ec2.cloud:nova.notifications.notify_decorator, nova.compute.api:nova.notifications.notify_decorator"
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml:47(td) ./doc/common/tables/cinder-common.xml:115(td)
-msgid "(ListOpt) List of modules/decorators to monkey patch"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml:8(caption)
-msgid "Description of configuration options for backups"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml:22(td)
-msgid "backup_api_class = cinder.backup.api.API"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml:23(td)
-msgid "(StrOpt) The full class name of the volume backup API class"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml:26(td)
-msgid "backup_compression_algorithm = zlib"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml:27(td)
-msgid "(StrOpt) Compression algorithm (None to disable)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml:30(td)
-msgid "backup_driver = cinder.backup.drivers.swift"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml:31(td)
-msgid "(StrOpt) Driver to use for backups."
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml:34(td)
-msgid "backup_manager = cinder.backup.manager.BackupManager"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml:35(td)
-msgid "(StrOpt) full class name for the Manager for volume backup"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml:38(td)
-msgid "backup_metadata_version = 1"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml:39(td)
-msgid "(IntOpt) Backup metadata version to be used when backing up volume metadata. If this number is bumped, make sure the service doing the restore supports the new version."
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml:42(td)
-msgid "backup_name_template = backup-%s"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml:43(td)
-msgid "(StrOpt) Template string to be used to generate backup names"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml:46(td)
-msgid "backup_topic = cinder-backup"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml:47(td)
-msgid "(StrOpt) the topic volume backup nodes listen on"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml:50(td) ./doc/common/tables/nova-api.xml:90(td)
-msgid "snapshot_name_template = snapshot-%s"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml:51(td) ./doc/common/tables/nova-api.xml:91(td)
-msgid "(StrOpt) Template string to be used to generate snapshot names"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml:54(td)
-msgid "snapshot_same_host = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml:55(td)
-msgid "(BoolOpt) Create volume from snapshot at the host where snapshot resides"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-pipeline-main.xml:7(literal) ./doc/common/tables/swift-object-server-pipeline-main.xml:7(literal) ./doc/common/tables/swift-object-expirer-pipeline-main.xml:7(literal) ./doc/common/tables/swift-account-server-pipeline-main.xml:7(literal) ./doc/common/tables/swift-proxy-server-pipeline-main.xml:7(literal)
-msgid "[pipeline:main]"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-pipeline-main.xml:18(td)
-msgid "pipeline = healthcheck recon container-server"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ofa.xml:8(caption)
-msgid "Description of configuration options for ml2_ofa"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ofa.xml:22(td)
-msgid "ofp_listen_host ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ofa.xml:23(td)
-msgid "(StrOpt) openflow listen host"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ofa.xml:26(td)
-msgid "ofp_ssl_listen_port = 6633"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ofa.xml:27(td)
-msgid "(IntOpt) openflow ssl listen port"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ofa.xml:30(td)
-msgid "ofp_tcp_listen_port = 6633"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ofa.xml:31(td)
-msgid "(IntOpt) openflow tcp listen port"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ofa.xml:37(td)
-msgid "get_datapath_retry_times = 60"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ofa.xml:38(td)
-msgid "(IntOpt) Number of seconds to retry acquiring an Open vSwitch datapath"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml:27(td) ./doc/common/tables/neutron-wsgi.xml:23(td)
-msgid "(IntOpt) Number of backlog requests to configure the socket with"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml:39(td) ./doc/common/tables/heat-debug.xml:35(td) ./doc/common/tables/neutron-logging.xml:31(td) ./doc/common/tables/nova-logging.xml:31(td)
-msgid "(BoolOpt) make deprecations fatal"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml:42(td)
-msgid "pydev_debug = disabled"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml:43(td)
-msgid "(StrOpt) Enable or disable pydev remote debugging. If value is 'auto' tries to connect to remote debugger server, but in case of error continues running with debugging disabled."
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml:47(td)
-msgid "(StrOpt) Pydev debug server host (localhost by default)."
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml:51(td)
-msgid "(IntOpt) Pydev debug server port (5678 by default)."
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml:54(td)
-msgid "remote_cinder_client = trove.common.remote.cinder_client"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml:58(td)
-msgid "remote_dns_client = trove.common.remote.dns_client"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml:62(td)
-msgid "remote_guest_client = trove.common.remote.guest_client"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml:66(td)
-msgid "remote_heat_client = trove.common.remote.heat_client"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml:70(td)
-msgid "remote_nova_client = trove.common.remote.nova_client"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml:74(td)
-msgid "remote_swift_client = trove.common.remote.swift_client"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml:78(td) ./doc/common/tables/glance-logging.xml:98(td) ./doc/common/tables/ceilometer-logging.xml:98(td) ./doc/common/tables/neutron-logging.xml:98(td) ./doc/common/tables/heat-logging.xml:82(td) ./doc/common/tables/keystone-logging.xml:86(td) ./doc/common/tables/nova-logging.xml:102(td) ./doc/common/tables/cinder-common.xml:222(td)
-msgid "verbose = False"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml:79(td) ./doc/common/tables/glance-logging.xml:99(td) ./doc/common/tables/ceilometer-logging.xml:99(td) ./doc/common/tables/neutron-logging.xml:99(td) ./doc/common/tables/heat-logging.xml:83(td) ./doc/common/tables/keystone-logging.xml:87(td) ./doc/common/tables/nova-logging.xml:103(td) ./doc/common/tables/cinder-common.xml:223(td)
-msgid "(BoolOpt) Print more verbose output (set logging level to INFO instead of default WARNING level)."
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-object.xml:7(literal)
-msgid "[object]"
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-object.xml:7(literal) ./doc/common/tables/swift-rsyncd-account.xml:7(literal) ./doc/common/tables/swift-rsyncd-container.xml:7(literal)
-msgid "rsyncd.conf-sample"
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-object.xml:18(td)
-msgid "max connections = 8"
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-object.xml:21(td) ./doc/common/tables/swift-rsyncd-account.xml:21(td) ./doc/common/tables/swift-rsyncd-container.xml:21(td)
-msgid "path = /srv/node"
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-object.xml:24(td) ./doc/common/tables/swift-rsyncd-account.xml:24(td) ./doc/common/tables/swift-rsyncd-container.xml:24(td)
-msgid "read only = false"
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-object.xml:27(td)
-msgid "lock file = /var/lock/object.lock"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml:22(td)
-msgid "buckets_path = $state_path/buckets"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml:23(td)
-msgid "(StrOpt) Path to S3 buckets"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml:26(td)
-msgid "image_decryption_dir = /tmp"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml:27(td)
-msgid "(StrOpt) Parent directory for tempdir used for image decryption"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml:30(td)
-msgid "s3_access_key = notchecked"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml:31(td)
-msgid "(StrOpt) Access key to use for S3 server for images"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml:34(td)
-msgid "s3_affix_tenant = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml:35(td)
-msgid "(BoolOpt) Whether to affix the tenant id to the access key when downloading from S3"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml:38(td)
-msgid "s3_host = $my_ip"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml:39(td)
-msgid "(StrOpt) Hostname or IP for OpenStack to use when accessing the S3 api"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml:42(td)
-msgid "s3_listen = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml:43(td)
-msgid "(StrOpt) IP address for S3 API to listen"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml:46(td)
-msgid "s3_listen_port = 3333"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml:47(td)
-msgid "(IntOpt) Port for S3 API to listen"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml:50(td)
-msgid "s3_port = 3333"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml:51(td)
-msgid "(IntOpt) Port used when accessing the S3 api"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml:54(td)
-msgid "s3_secret_key = notchecked"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml:55(td)
-msgid "(StrOpt) Secret key to use for S3 server for images"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml:58(td)
-msgid "s3_use_ssl = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml:59(td)
-msgid "(BoolOpt) Whether to use SSL when talking to S3"
-msgstr ""
-
-#: ./doc/common/tables/nova-zookeeper.xml:8(caption)
-msgid "Description of configuration options for zookeeper"
-msgstr ""
-
-#: ./doc/common/tables/nova-zookeeper.xml:19(th)
-msgid "[zookeeper]"
-msgstr ""
-
-#: ./doc/common/tables/nova-zookeeper.xml:22(td)
-msgid "address = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-zookeeper.xml:23(td)
-msgid "(StrOpt) The ZooKeeper addresses for servicegroup service in the format of host1:port,host2:port,host3:port"
-msgstr ""
-
-#: ./doc/common/tables/nova-zookeeper.xml:26(td)
-msgid "recv_timeout = 4000"
-msgstr ""
-
-#: ./doc/common/tables/nova-zookeeper.xml:27(td)
-msgid "(IntOpt) The recv_timeout parameter for the zk session"
-msgstr ""
-
-#: ./doc/common/tables/nova-zookeeper.xml:30(td)
-msgid "sg_prefix = /servicegroups"
-msgstr ""
-
-#: ./doc/common/tables/nova-zookeeper.xml:31(td)
-msgid "(StrOpt) The prefix used in ZooKeeper to store ephemeral nodes"
-msgstr ""
-
-#: ./doc/common/tables/nova-zookeeper.xml:34(td)
-msgid "sg_retry_interval = 5"
-msgstr ""
-
-#: ./doc/common/tables/nova-zookeeper.xml:35(td)
-msgid "(IntOpt) Number of seconds to wait until retrying to join the session"
-msgstr ""
-
-#: ./doc/common/tables/cinder-rpc.xml:38(td)
-msgid "default_timeout = 20"
-msgstr ""
-
-#: ./doc/common/tables/cinder-rpc.xml:39(td)
-msgid "(IntOpt) Default Time Out For CLI operations in minutes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-rpc.xml:83(td) ./doc/common/tables/glance-redis.xml:27(td) ./doc/common/tables/keystone-redis.xml:35(td) ./doc/common/tables/nova-redis.xml:23(td)
-msgid "(StrOpt) Password for Redis server (optional)."
-msgstr ""
-
-#: ./doc/common/tables/cinder-rpc.xml:234(td)
-msgid "volume_topic = cinder-volume"
-msgstr ""
-
-#: ./doc/common/tables/cinder-rpc.xml:235(td)
-msgid "(StrOpt) the topic volume nodes listen on"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:23(td)
-msgid "(StrOpt) File name for the paste.deploy config for cinder-api"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:26(td)
-msgid "api_rate_limit = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:27(td)
-msgid "(BoolOpt) whether to rate limit the api"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:34(td) ./doc/common/tables/ceilometer-api.xml:22(td) ./doc/common/tables/glance-api.xml:38(td)
-msgid "enable_v1_api = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:35(td)
-msgid "(BoolOpt) Deploy v1 of the Cinder API."
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:38(td) ./doc/common/tables/glance-api.xml:46(td)
-msgid "enable_v2_api = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:39(td)
-msgid "(BoolOpt) Deploy v2 of the Cinder API."
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:42(td)
-msgid "extra_capabilities = {}"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:43(td)
-msgid "(StrOpt) User defined capabilities, a JSON formatted string specifying key/value pairs."
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:50(td) ./doc/common/tables/nova-policy.xml:46(td)
-msgid "osapi_max_limit = 1000"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:51(td)
-msgid "(IntOpt) the maximum number of items returned in a single response from a collection resource"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:54(td) ./doc/common/tables/nova-policy.xml:50(td)
-msgid "osapi_max_request_body_size = 114688"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:55(td)
-msgid "(IntOpt) Max size for body of a request"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:58(td)
-msgid "osapi_volume_base_URL = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:59(td)
-msgid "(StrOpt) Base URL that will be presented to users in links to the OpenStack Volume API"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:62(td)
-msgid "osapi_volume_ext_list ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:63(td)
-msgid "(ListOpt) Specify list of extensions to load when using osapi_volume_extension option with cinder.api.contrib.select_extensions"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:66(td)
-msgid "osapi_volume_extension = ['cinder.api.contrib.standard_extensions']"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:67(td)
-msgid "(MultiStrOpt) osapi volume extension to load"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:70(td)
-msgid "osapi_volume_listen = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:71(td)
-msgid "(StrOpt) IP address for OpenStack Volume API to listen"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:74(td)
-msgid "osapi_volume_listen_port = 8776"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:75(td)
-msgid "(IntOpt) port for os volume api to listen"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:78(td)
-msgid "osapi_volume_workers = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:79(td)
-msgid "(IntOpt) Number of workers for OpenStack Volume API service"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:82(td)
-msgid "transfer_api_class = cinder.transfer.api.API"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:83(td)
-msgid "(StrOpt) The full class name of the volume transfer API class"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:86(td)
-msgid "volume_api_class = cinder.volume.api.API"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:90(td)
-msgid "volume_name_template = volume-%s"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:91(td)
-msgid "(StrOpt) Template string to be used to generate volume names"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:94(td)
-msgid "volume_transfer_key_length = 16"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:95(td)
-msgid "(IntOpt) The number of characters in the autogenerated auth key."
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:98(td)
-msgid "volume_transfer_salt_length = 8"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml:99(td)
-msgid "(IntOpt) The number of characters in the salt."
-msgstr ""
-
-#: ./doc/common/tables/cinder-windows.xml:8(caption)
-msgid "Description of configuration options for windows"
-msgstr ""
-
-#: ./doc/common/tables/cinder-windows.xml:22(td)
-msgid "windows_iscsi_lun_path = C:\\iSCSIVirtualDisks"
-msgstr ""
-
-#: ./doc/common/tables/cinder-windows.xml:23(td)
-msgid "(StrOpt) Path to store VHD backed volumes"
-msgstr ""
-
-#: ./doc/common/tables/glance-vmware.xml:8(caption) ./doc/common/tables/ceilometer-vmware.xml:8(caption) ./doc/common/tables/cinder-vmware.xml:8(caption) ./doc/common/tables/nova-vmware.xml:8(caption) ./doc/common/tables/neutron-vmware.xml:8(caption)
-msgid "Description of configuration options for vmware"
-msgstr ""
-
 #: ./doc/common/tables/glance-vmware.xml:22(td)
 msgid "vmware_api_insecure = False"
 msgstr ""
@@ -25187,468 +25939,12 @@ msgstr ""
 msgid "(IntOpt) The interval used for polling remote tasks invoked on VMware ESX/VC server."
 msgstr ""
 
-#: ./doc/common/tables/swift-object-server-pipeline-main.xml:18(td)
-msgid "pipeline = healthcheck recon object-server"
+#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml:7(literal)
+msgid "[filter:container-quotas]"
 msgstr ""
 
-#: ./doc/common/tables/trove-backup.xml:8(caption)
-msgid "Description of configuration options for backup"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml:22(td)
-msgid "backup_aes_cbc_key = default_aes_cbc_key"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml:23(td)
-msgid "(StrOpt) Default OpenSSL aes_cbc key."
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml:26(td)
-msgid "backup_chunk_size = 65536"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml:27(td)
-msgid "(IntOpt) Chunk size to stream to swift container. This should be in multiples of 128 bytes, since this is the size of an md5 digest block allowing the process to update the file checksum during streaming. See: http://stackoverflow.com/questions/1131220/"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml:30(td)
-msgid "backup_incremental_strategy = {'InnoBackupEx': 'InnoBackupExIncremental'}"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml:31(td)
-msgid "(DictOpt) Incremental Backup Runner Based off of the default strategy. For strategies that do not implement an incremental the runner will use the default full backup."
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml:34(td)
-msgid "backup_namespace = trove.guestagent.strategies.backup.mysql_impl"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml:35(td)
-msgid "(StrOpt) Namespace to load backup strategies from."
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml:38(td)
-msgid "backup_runner = trove.guestagent.backup.backup_types.InnoBackupEx"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml:42(td)
-msgid "backup_runner_options = {}"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml:43(td)
-msgid "(DictOpt) Additional options to be passed to the backup runner."
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml:46(td)
-msgid "backup_segment_max_size = 2147483648"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml:47(td)
-msgid "(IntOpt) Maximum size of each segment of the backup file."
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml:50(td) ./doc/common/tables/trove-db_mysql.xml:22(td) ./doc/common/tables/trove-db_percona.xml:22(td)
-msgid "backup_strategy = InnoBackupEx"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml:54(td)
-msgid "backup_swift_container = database_backups"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml:58(td)
-msgid "backup_use_gzip_compression = True"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml:59(td)
-msgid "(BoolOpt) Compress backups using gzip."
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml:62(td)
-msgid "backup_use_openssl_encryption = True"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml:63(td)
-msgid "(BoolOpt) Encrypt backups using OpenSSL."
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml:66(td)
-msgid "backup_use_snet = False"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml:67(td)
-msgid "(BoolOpt) Send backup files over snet."
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml:70(td)
-msgid "backups_page_size = 20"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml:8(caption)
-msgid "Description of configuration options for san"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml:22(td)
-msgid "san_clustername ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml:23(td)
-msgid "(StrOpt) Cluster name to use for creating volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml:26(td)
-msgid "san_ip ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml:27(td)
-msgid "(StrOpt) IP address of SAN controller"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml:30(td)
-msgid "san_is_local = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml:31(td)
-msgid "(BoolOpt) Execute commands locally instead of over SSH; use if the volume service is running on the SAN device"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml:34(td)
-msgid "san_login = admin"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml:35(td)
-msgid "(StrOpt) Username for SAN controller"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml:38(td)
-msgid "san_password ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml:39(td)
-msgid "(StrOpt) Password for SAN controller"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml:42(td)
-msgid "san_private_key ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml:43(td)
-msgid "(StrOpt) Filename of private key to use for SSH authentication"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml:46(td)
-msgid "san_ssh_port = 22"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml:47(td)
-msgid "(IntOpt) SSH port to use with SAN"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml:50(td)
-msgid "san_thin_provision = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml:51(td)
-msgid "(BoolOpt) Use thin provisioning for SAN volumes?"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml:54(td)
-msgid "ssh_conn_timeout = 30"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml:55(td)
-msgid "(IntOpt) SSH connection timeout in seconds"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml:58(td)
-msgid "ssh_max_pool_conn = 5"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml:59(td)
-msgid "(IntOpt) Maximum ssh connections in the pool"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml:62(td)
-msgid "ssh_min_pool_conn = 1"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml:63(td)
-msgid "(IntOpt) Minimum ssh connections in the pool"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-app-account-server.xml:7(literal)
-msgid "[app:account-server]"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-app-account-server.xml:18(td)
-msgid "use = egg:swift#account"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-app-account-server.xml:21(td)
-msgid "set log_name = account-server"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-app-account-server.xml:30(td) ./doc/common/tables/swift-container-server-app-container-server.xml:30(td) ./doc/common/tables/swift-object-server-app-object-server.xml:30(td)
-msgid "set log_requests = true"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-app-account-server.xml:30(td) ./doc/common/tables/swift-container-server-app-container-server.xml:30(td) ./doc/common/tables/swift-object-server-app-object-server.xml:30(td)
-msgid "Whether or not to log requests"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-app-account-server.xml:39(td) ./doc/common/tables/swift-container-server-app-container-server.xml:48(td) ./doc/common/tables/swift-object-server-app-object-server.xml:60(td)
-msgid "replication_server = false"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-app-account-server.xml:39(td) ./doc/common/tables/swift-container-server-app-container-server.xml:48(td) ./doc/common/tables/swift-object-server-app-object-server.xml:60(td)
-msgid "If defined, tells server how to handle replication verbs in requests. When set to True (or 1), only replication verbs will be accepted. When set to False, replication verbs will be rejected. When undefined, server will accept any verb in the request."
-msgstr ""
-
-#: ./doc/common/tables/cinder-keymgr.xml:22(td)
-msgid "api_class = cinder.keymgr.conf_key_mgr.ConfKeyManager"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:8(caption) ./doc/common/tables/neutron-db.xml:8(caption) ./doc/common/tables/glance-db.xml:8(caption)
-msgid "Description of configuration options for db"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:22(td)
-msgid "db_driver = nova.db"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:23(td)
-msgid "(StrOpt) The driver to use for database access"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:29(td)
-msgid "db_check_interval = 60"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:30(td)
-msgid "(IntOpt) Interval, in seconds, for getting fresh cell information from the database."
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:36(td) ./doc/common/tables/heat-database.xml:37(td) ./doc/common/tables/ceilometer-database.xml:41(td) ./doc/common/tables/cinder-storage.xml:137(td) ./doc/common/tables/neutron-db.xml:33(td) ./doc/common/tables/keystone-database.xml:22(td) ./doc/common/tables/glance-db.xml:22(td)
-msgid "backend = sqlalchemy"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:37(td) ./doc/common/tables/heat-database.xml:38(td) ./doc/common/tables/ceilometer-database.xml:42(td) ./doc/common/tables/cinder-storage.xml:138(td) ./doc/common/tables/cinder-database.xml:23(td) ./doc/common/tables/neutron-db.xml:34(td) ./doc/common/tables/keystone-database.xml:23(td) ./doc/common/tables/glance-db.xml:23(td)
-msgid "(StrOpt) The backend to use for db"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:40(td) ./doc/common/tables/keystone-database.xml:26(td) ./doc/common/tables/glance-db.xml:26(td)
-msgid "connection = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:41(td) ./doc/common/tables/heat-database.xml:42(td) ./doc/common/tables/ceilometer-database.xml:46(td) ./doc/common/tables/cinder-connection.xml:23(td) ./doc/common/tables/neutron-db.xml:38(td) ./doc/common/tables/keystone-database.xml:27(td) ./doc/common/tables/glance-db.xml:27(td)
-msgid "(StrOpt) The SQLAlchemy connection string used to connect to the database"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:44(td) ./doc/common/tables/heat-database.xml:45(td) ./doc/common/tables/ceilometer-database.xml:49(td) ./doc/common/tables/cinder-connection.xml:26(td) ./doc/common/tables/neutron-db.xml:41(td) ./doc/common/tables/keystone-database.xml:30(td) ./doc/common/tables/glance-db.xml:30(td)
-msgid "connection_debug = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:45(td) ./doc/common/tables/heat-database.xml:46(td) ./doc/common/tables/ceilometer-database.xml:50(td) ./doc/common/tables/cinder-connection.xml:27(td) ./doc/common/tables/neutron-db.xml:42(td) ./doc/common/tables/keystone-database.xml:31(td) ./doc/common/tables/glance-db.xml:31(td)
-msgid "(IntOpt) Verbosity of SQL debugging information. 0=None, 100=Everything"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:48(td) ./doc/common/tables/heat-database.xml:49(td) ./doc/common/tables/ceilometer-database.xml:53(td) ./doc/common/tables/cinder-connection.xml:30(td) ./doc/common/tables/neutron-db.xml:45(td) ./doc/common/tables/keystone-database.xml:34(td) ./doc/common/tables/glance-db.xml:34(td)
-msgid "connection_trace = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:49(td) ./doc/common/tables/heat-database.xml:50(td) ./doc/common/tables/ceilometer-database.xml:54(td) ./doc/common/tables/cinder-connection.xml:31(td) ./doc/common/tables/neutron-db.xml:46(td) ./doc/common/tables/keystone-database.xml:35(td) ./doc/common/tables/glance-db.xml:35(td)
-msgid "(BoolOpt) Add python stack traces to SQL as comment strings"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:52(td) ./doc/common/tables/neutron-db.xml:49(td) ./doc/common/tables/keystone-database.xml:38(td) ./doc/common/tables/glance-db.xml:38(td)
-msgid "db_inc_retry_interval = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:53(td) ./doc/common/tables/neutron-db.xml:50(td) ./doc/common/tables/keystone-database.xml:39(td) ./doc/common/tables/glance-db.xml:39(td)
-msgid "(BoolOpt) Whether to increase interval between db connection retries, up to db_max_retry_interval"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:56(td) ./doc/common/tables/neutron-db.xml:53(td) ./doc/common/tables/keystone-database.xml:42(td) ./doc/common/tables/glance-db.xml:42(td)
-msgid "db_max_retries = 20"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:57(td) ./doc/common/tables/neutron-db.xml:54(td) ./doc/common/tables/keystone-database.xml:43(td) ./doc/common/tables/glance-db.xml:43(td)
-msgid "(IntOpt) maximum db connection retries before error is raised. (setting -1 implies an infinite retry count)"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:60(td) ./doc/common/tables/neutron-db.xml:57(td) ./doc/common/tables/keystone-database.xml:46(td) ./doc/common/tables/glance-db.xml:46(td)
-msgid "db_max_retry_interval = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:61(td) ./doc/common/tables/neutron-db.xml:58(td) ./doc/common/tables/keystone-database.xml:47(td) ./doc/common/tables/glance-db.xml:47(td)
-msgid "(IntOpt) max seconds between db connection retries, if db_inc_retry_interval is enabled"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:64(td) ./doc/common/tables/neutron-db.xml:61(td) ./doc/common/tables/keystone-database.xml:50(td) ./doc/common/tables/glance-db.xml:50(td)
-msgid "db_retry_interval = 1"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:65(td) ./doc/common/tables/neutron-db.xml:62(td) ./doc/common/tables/keystone-database.xml:51(td) ./doc/common/tables/glance-db.xml:51(td)
-msgid "(IntOpt) seconds between db connection retries"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:68(td) ./doc/common/tables/heat-database.xml:53(td) ./doc/common/tables/ceilometer-database.xml:57(td) ./doc/common/tables/cinder-common.xml:229(td) ./doc/common/tables/neutron-db.xml:65(td) ./doc/common/tables/keystone-database.xml:54(td) ./doc/common/tables/glance-db.xml:54(td)
-msgid "idle_timeout = 3600"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:69(td) ./doc/common/tables/ceilometer-database.xml:58(td) ./doc/common/tables/neutron-db.xml:66(td) ./doc/common/tables/keystone-database.xml:55(td) ./doc/common/tables/glance-db.xml:55(td)
-msgid "(IntOpt) Timeout before idle sql connections are reaped"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:72(td) ./doc/common/tables/heat-database.xml:57(td) ./doc/common/tables/ceilometer-database.xml:61(td) ./doc/common/tables/cinder-storage.xml:141(td) ./doc/common/tables/keystone-database.xml:58(td) ./doc/common/tables/glance-db.xml:58(td)
-msgid "max_overflow = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:73(td) ./doc/common/tables/heat-database.xml:58(td) ./doc/common/tables/ceilometer-database.xml:62(td) ./doc/common/tables/cinder-storage.xml:142(td) ./doc/common/tables/neutron-db.xml:70(td) ./doc/common/tables/keystone-database.xml:59(td) ./doc/common/tables/glance-db.xml:59(td)
-msgid "(IntOpt) If set, use this value for max_overflow with sqlalchemy"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:76(td) ./doc/common/tables/heat-database.xml:61(td) ./doc/common/tables/ceilometer-database.xml:65(td) ./doc/common/tables/keystone-database.xml:62(td) ./doc/common/tables/glance-db.xml:62(td)
-msgid "max_pool_size = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:77(td) ./doc/common/tables/heat-database.xml:62(td) ./doc/common/tables/ceilometer-database.xml:66(td) ./doc/common/tables/cinder-storage.xml:146(td) ./doc/common/tables/neutron-db.xml:74(td) ./doc/common/tables/keystone-database.xml:63(td) ./doc/common/tables/glance-db.xml:63(td)
-msgid "(IntOpt) Maximum number of SQL connections to keep open in a pool"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:80(td) ./doc/common/tables/heat-database.xml:65(td) ./doc/common/tables/ceilometer-database.xml:69(td) ./doc/common/tables/cinder-storage.xml:149(td) ./doc/common/tables/neutron-db.xml:77(td) ./doc/common/tables/keystone-database.xml:66(td) ./doc/common/tables/glance-db.xml:66(td)
-msgid "max_retries = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:81(td) ./doc/common/tables/ceilometer-database.xml:70(td) ./doc/common/tables/neutron-db.xml:78(td) ./doc/common/tables/keystone-database.xml:67(td) ./doc/common/tables/glance-db.xml:67(td)
-msgid "(IntOpt) Maximum db connection retries during startup. (setting -1 implies an infinite retry count)"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:84(td) ./doc/common/tables/heat-database.xml:69(td) ./doc/common/tables/ceilometer-database.xml:73(td) ./doc/common/tables/cinder-storage.xml:153(td) ./doc/common/tables/neutron-db.xml:81(td) ./doc/common/tables/keystone-database.xml:70(td) ./doc/common/tables/glance-db.xml:70(td)
-msgid "min_pool_size = 1"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:85(td) ./doc/common/tables/heat-database.xml:70(td) ./doc/common/tables/ceilometer-database.xml:74(td) ./doc/common/tables/cinder-storage.xml:154(td) ./doc/common/tables/neutron-db.xml:82(td) ./doc/common/tables/keystone-database.xml:71(td) ./doc/common/tables/glance-db.xml:71(td)
-msgid "(IntOpt) Minimum number of SQL connections to keep open in a pool"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:88(td)
-msgid "mysql_sql_mode = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:89(td)
-msgid "(StrOpt) The SQL mode to be used for MySQL sessions (default is empty, meaning do not override any server-side SQL mode setting)"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:92(td) ./doc/common/tables/heat-database.xml:73(td) ./doc/common/tables/ceilometer-database.xml:77(td) ./doc/common/tables/keystone-database.xml:78(td) ./doc/common/tables/glance-db.xml:78(td)
-msgid "pool_timeout = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:93(td) ./doc/common/tables/heat-database.xml:74(td) ./doc/common/tables/ceilometer-database.xml:78(td) ./doc/common/tables/neutron-db.xml:86(td) ./doc/common/tables/keystone-database.xml:79(td) ./doc/common/tables/glance-db.xml:79(td)
-msgid "(IntOpt) If set, use this value for pool_timeout with sqlalchemy"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:96(td) ./doc/common/tables/heat-database.xml:77(td) ./doc/common/tables/ceilometer-database.xml:81(td) ./doc/common/tables/cinder-common.xml:233(td) ./doc/common/tables/neutron-db.xml:89(td) ./doc/common/tables/keystone-database.xml:82(td) ./doc/common/tables/glance-db.xml:82(td)
-msgid "retry_interval = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:97(td) ./doc/common/tables/ceilometer-database.xml:82(td) ./doc/common/tables/neutron-db.xml:90(td) ./doc/common/tables/keystone-database.xml:83(td) ./doc/common/tables/glance-db.xml:83(td)
-msgid "(IntOpt) Interval between retries of opening a sql connection"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:100(td)
-msgid "slave_connection = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:101(td) ./doc/common/tables/heat-database.xml:82(td) ./doc/common/tables/ceilometer-database.xml:86(td) ./doc/common/tables/neutron-db.xml:94(td)
-msgid "(StrOpt) The SQLAlchemy connection string used to connect to the slave database"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:104(td)
-msgid "sqlite_db = nova.sqlite"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:105(td) ./doc/common/tables/ceilometer-database.xml:31(td) ./doc/common/tables/neutron-db.xml:23(td) ./doc/common/tables/keystone-database.xml:87(td) ./doc/common/tables/glance-db.xml:87(td)
-msgid "(StrOpt) The file name to use with SQLite"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:108(td) ./doc/common/tables/heat-database.xml:30(td) ./doc/common/tables/ceilometer-database.xml:34(td) ./doc/common/tables/cinder-common.xml:170(td) ./doc/common/tables/neutron-db.xml:26(td) ./doc/common/tables/keystone-database.xml:90(td) ./doc/common/tables/glance-db.xml:90(td)
-msgid "sqlite_synchronous = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:109(td) ./doc/common/tables/ceilometer-database.xml:35(td) ./doc/common/tables/neutron-db.xml:27(td) ./doc/common/tables/keystone-database.xml:91(td) ./doc/common/tables/glance-db.xml:91(td)
-msgid "(BoolOpt) If True, SQLite uses synchronous mode"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:112(td) ./doc/common/tables/neutron-db.xml:97(td) ./doc/common/tables/keystone-database.xml:94(td) ./doc/common/tables/glance-db.xml:94(td)
-msgid "use_db_reconnect = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml:113(td) ./doc/common/tables/neutron-db.xml:98(td) ./doc/common/tables/keystone-database.xml:95(td) ./doc/common/tables/glance-db.xml:95(td)
-msgid "(BoolOpt) Enable the experimental use of database reconnect on connection lost"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_vxlan.xml:8(caption)
-msgid "Description of configuration options for ml2_vxlan"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_vxlan.xml:19(th)
-msgid "[ml2_type_vxlan]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_vxlan.xml:22(td)
-msgid "vni_ranges ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_vxlan.xml:23(td)
-msgid "(ListOpt) Comma-separated list of &lt;vni_min&gt;:&lt;vni_max&gt; tuples enumerating ranges of VXLAN VNI IDs that are available for tenant network allocation"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_vxlan.xml:26(td)
-msgid "vxlan_group = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_vxlan.xml:27(td)
-msgid "(StrOpt) Multicast group for VXLAN. If unset, disables VXLAN multicast mode."
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml:26(td) ./doc/common/tables/ceilometer-logging.xml:26(td) ./doc/common/tables/keystone-logging.xml:22(td)
-msgid "default_log_levels = amqp=WARN, amqplib=WARN, boto=WARN, qpid=WARN, sqlalchemy=WARN, suds=INFO, iso8601=WARN, requests.packages.urllib3.connectionpool=WARN"
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml:27(td) ./doc/common/tables/ceilometer-logging.xml:27(td) ./doc/common/tables/keystone-logging.xml:23(td) ./doc/common/tables/cinder-common.xml:35(td)
-msgid "(ListOpt) List of logger=LEVEL pairs"
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml:63(td) ./doc/common/tables/ceilometer-logging.xml:63(td) ./doc/common/tables/keystone-logging.xml:55(td) ./doc/common/tables/cinder-common.xml:95(td)
-msgid "(StrOpt) Format string to use for log messages with context"
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml:67(td) ./doc/common/tables/ceilometer-logging.xml:67(td) ./doc/common/tables/keystone-logging.xml:59(td) ./doc/common/tables/cinder-common.xml:99(td)
-msgid "(StrOpt) Data to append to log format when level is DEBUG"
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml:71(td) ./doc/common/tables/ceilometer-logging.xml:71(td) ./doc/common/tables/keystone-logging.xml:63(td) ./doc/common/tables/cinder-common.xml:103(td)
-msgid "(StrOpt) Format string to use for log messages without context"
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml:75(td) ./doc/common/tables/ceilometer-logging.xml:75(td) ./doc/common/tables/keystone-logging.xml:67(td) ./doc/common/tables/cinder-common.xml:107(td)
-msgid "(StrOpt) Prefix each line of exception output with this format"
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml:83(td) ./doc/common/tables/ceilometer-logging.xml:83(td) ./doc/common/tables/keystone-logging.xml:71(td) ./doc/common/tables/cinder-common.xml:195(td)
-msgid "(StrOpt) Syslog facility to receive log lines"
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml:91(td) ./doc/common/tables/ceilometer-logging.xml:91(td) ./doc/common/tables/keystone-logging.xml:79(td) ./doc/common/tables/nova-logging.xml:95(td) ./doc/common/tables/cinder-common.xml:215(td)
-msgid "(BoolOpt) Use syslog for logging. Existing syslog format is DEPRECATED during I, and then will be changed in J to honor RFC5424"
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml:94(td) ./doc/common/tables/ceilometer-logging.xml:94(td) ./doc/common/tables/keystone-logging.xml:82(td) ./doc/common/tables/nova-logging.xml:98(td) ./doc/common/tables/cinder-common.xml:218(td)
-msgid "use_syslog_rfc_format = False"
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml:95(td) ./doc/common/tables/ceilometer-logging.xml:95(td) ./doc/common/tables/keystone-logging.xml:83(td) ./doc/common/tables/nova-logging.xml:99(td) ./doc/common/tables/cinder-common.xml:219(td)
-msgid "(BoolOpt) (Optional) Use syslog rfc5424 format for logging. If enabled, will add APP-NAME (RFC5424) before the MSG part of the syslog message. The old format without APP-NAME is deprecated in I, and will be removed in J."
+#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml:18(td)
+msgid "use = egg:swift#container_quotas"
 msgstr ""
 
 #: ./doc/common/tables/cinder-zoning.xml:8(caption)
@@ -25675,564 +25971,628 @@ msgstr ""
 msgid "(StrOpt) Comma separated list of fibre channel fabric names. This list of names is used to retrieve other SAN credentials for connecting to each SAN fabric"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning.xml:33(td) ./doc/common/tables/cinder-zoning_fabric.xml:50(td)
-msgid "zoning_policy = initiator-target"
-msgstr ""
-
 #: ./doc/common/tables/cinder-zoning.xml:34(td)
 msgid "(StrOpt) Zoning policy configured by user"
 msgstr ""
 
-#: ./doc/common/tables/glance-wsgi.xml:8(caption) ./doc/common/tables/neutron-wsgi.xml:8(caption) ./doc/common/tables/nova-wsgi.xml:8(caption)
-msgid "Description of configuration options for wsgi"
+#: ./doc/common/tables/heat-notification.xml:8(caption) ./doc/common/tables/keystone-notification.xml:8(caption)
+msgid "Description of configuration options for notification"
 msgstr ""
 
-#: ./doc/common/tables/glance-wsgi.xml:23(td)
-msgid "(IntOpt) port for eventlet backdoor to listen"
+#: ./doc/common/tables/heat-notification.xml:22(td) ./doc/common/tables/keystone-notification.xml:22(td)
+msgid "onready = None"
 msgstr ""
 
-#: ./doc/common/tables/glance-wsgi.xml:26(td)
-msgid "eventlet_hub = poll"
+#: ./doc/common/tables/heat-notification.xml:23(td)
+msgid "(StrOpt) onready allows you to send a notification when the heat processes are ready to serve. This is either a module with the notify() method or a shell command. To enable notifications with systemd, one may use the 'systemd-notify --ready' shell command or the 'heat.common.systemd' notification module."
 msgstr ""
 
-#: ./doc/common/tables/glance-wsgi.xml:27(td)
-msgid "(StrOpt) Name of eventlet hub to use. Traditionally, we have only supported 'poll', however 'selects' may be appropriate for some platforms. See http://eventlet.net/doc/hubs.html for more details."
+#: ./doc/common/tables/nova-vpn.xml:8(caption) ./doc/common/tables/neutron-vpn.xml:8(caption)
+msgid "Description of configuration options for vpn"
 msgstr ""
 
-#: ./doc/common/tables/glance-wsgi.xml:35(td)
-msgid "(IntOpt) The value for the socket option TCP_KEEPIDLE. This is the time in seconds that the connection must be idle before TCP starts sending keepalive probes."
+#: ./doc/common/tables/nova-vpn.xml:22(td)
+msgid "boot_script_template = $pybasedir/nova/cloudpipe/bootscript.template"
 msgstr ""
 
-#: ./doc/common/tables/nova-periodic.xml:8(caption)
-msgid "Description of configuration options for periodic"
+#: ./doc/common/tables/nova-vpn.xml:23(td)
+msgid "(StrOpt) Template for cloudpipe instance boot script"
 msgstr ""
 
-#: ./doc/common/tables/nova-periodic.xml:22(td)
-msgid "periodic_enable = True"
+#: ./doc/common/tables/nova-vpn.xml:26(td)
+msgid "dmz_cidr ="
 msgstr ""
 
-#: ./doc/common/tables/nova-periodic.xml:23(td)
-msgid "(BoolOpt) Enable periodic tasks"
+#: ./doc/common/tables/nova-vpn.xml:27(td)
+msgid "(ListOpt) A list of dmz range that should be accepted"
 msgstr ""
 
-#: ./doc/common/tables/nova-periodic.xml:26(td) ./doc/common/tables/cinder-common.xml:130(td)
-msgid "periodic_fuzzy_delay = 60"
+#: ./doc/common/tables/nova-vpn.xml:30(td)
+msgid "dmz_mask = 255.255.255.0"
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml:8(caption)
-msgid "Description of configuration options for images"
+#: ./doc/common/tables/nova-vpn.xml:31(td)
+msgid "(StrOpt) Netmask to push into openvpn config"
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml:23(td)
-msgid "(ListOpt) A list of url schemes that can be downloaded directly via the direct_url. Currently supported schemes: [file]."
+#: ./doc/common/tables/nova-vpn.xml:34(td)
+msgid "dmz_net = 10.0.0.0"
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml:31(td)
-msgid "(ListOpt) A list of the glance api servers available to cinder ([hostname|ip]:port)"
+#: ./doc/common/tables/nova-vpn.xml:35(td)
+msgid "(StrOpt) Network to push into openvpn config"
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml:34(td)
-msgid "glance_api_ssl_compression = False"
+#: ./doc/common/tables/nova-vpn.xml:38(td)
+msgid "vpn_flavor = m1.tiny"
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml:35(td)
-msgid "(BoolOpt) Whether to attempt to negotiate SSL layer compression when using SSL (https) requests. Set to False to disable SSL layer compression. In some cases disabling this may improve data throughput, eg when high network bandwidth is available and you are using already compressed image formats such as qcow2 ."
+#: ./doc/common/tables/nova-vpn.xml:39(td)
+msgid "(StrOpt) Flavor for vpn instances"
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml:38(td)
-msgid "glance_api_version = 1"
+#: ./doc/common/tables/nova-vpn.xml:42(td)
+msgid "vpn_image_id = 0"
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml:39(td)
-msgid "(IntOpt) Version of the glance api to use"
+#: ./doc/common/tables/nova-vpn.xml:43(td)
+msgid "(StrOpt) Image ID used when starting up a cloudpipe vpn server"
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml:43(td)
-msgid "(StrOpt) default glance hostname or ip"
+#: ./doc/common/tables/nova-vpn.xml:46(td)
+msgid "vpn_ip = $my_ip"
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml:47(td)
-msgid "(IntOpt) Number retries when downloading an image from glance"
+#: ./doc/common/tables/nova-vpn.xml:47(td)
+msgid "(StrOpt) Public IP for the cloudpipe VPN servers"
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml:51(td)
-msgid "(IntOpt) default glance port"
+#: ./doc/common/tables/nova-vpn.xml:50(td)
+msgid "vpn_key_suffix = -vpn"
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml:54(td)
-msgid "glance_request_timeout = None"
+#: ./doc/common/tables/nova-vpn.xml:51(td)
+msgid "(StrOpt) Suffix to add to project name for vpn key and secgroups"
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml:55(td)
-msgid "(IntOpt) http/https timeout value for glance operations. If no value (None) is supplied here, the glanceclient default value is used."
+#: ./doc/common/tables/nova-vpn.xml:54(td)
+msgid "vpn_start = 1000"
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml:58(td)
-msgid "image_conversion_dir = $state_path/conversion"
+#: ./doc/common/tables/nova-vpn.xml:55(td)
+msgid "(IntOpt) First Vpn port for private networks"
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml:59(td)
-msgid "(StrOpt) Directory used for temporary storage during image conversion"
+#: ./doc/common/tables/neutron-vpn.xml:19(th)
+msgid "[ipsec]"
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml:70(td)
-msgid "use_multipath_for_image_xfer = False"
+#: ./doc/common/tables/neutron-vpn.xml:22(td)
+msgid "config_base_dir = $state_path/ipsec"
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml:71(td)
-msgid "(BoolOpt) Do we attach/detach volumes in cinder using multipath for volume to image and image to volume transfers?"
+#: ./doc/common/tables/neutron-vpn.xml:23(td)
+msgid "(StrOpt) Location to store ipsec server config files"
 msgstr ""
 
-#: ./doc/common/tables/trove-swift.xml:22(td)
-msgid "swift_url = http://localhost:8080/v1/AUTH_"
+#: ./doc/common/tables/neutron-vpn.xml:26(td)
+msgid "ipsec_status_check_interval = 60"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-app-container-server.xml:7(literal)
-msgid "[app:container-server]"
+#: ./doc/common/tables/neutron-vpn.xml:27(td)
+msgid "(IntOpt) Interval for checking ipsec status"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-app-container-server.xml:18(td)
-msgid "use = egg:swift#container"
+#: ./doc/common/tables/neutron-vpn.xml:30(th)
+msgid "[openswan]"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-app-container-server.xml:21(td)
-msgid "set log_name = container-server"
+#: ./doc/common/tables/neutron-vpn.xml:33(td)
+msgid "ipsec_config_template = /usr/lib/python/site-packages/neutron/services/vpn/device_drivers/template/openswan/ipsec.conf.template"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-app-container-server.xml:42(td)
-msgid "allow_versions = false"
+#: ./doc/common/tables/neutron-vpn.xml:34(td)
+msgid "(StrOpt) Template file for ipsec configuration"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-app-container-server.xml:42(td)
-msgid "Enable/Disable object versioning feature"
+#: ./doc/common/tables/neutron-vpn.xml:37(td)
+msgid "ipsec_secret_template = /usr/lib/python/site-packages/neutron/services/vpn/device_drivers/template/openswan/ipsec.secret.template"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml:7(literal)
-msgid "[filter:slo]"
+#: ./doc/common/tables/neutron-vpn.xml:38(td)
+msgid "(StrOpt) Template file for ipsec secret configuration"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml:18(td)
-msgid "use = egg:swift#slo"
+#: ./doc/common/tables/neutron-vpn.xml:41(th)
+msgid "[vpnagent]"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml:21(td)
-msgid "max_manifest_segments = 1000"
+#: ./doc/common/tables/neutron-vpn.xml:44(td)
+msgid "vpn_device_driver = ['neutron.services.vpn.device_drivers.ipsec.OpenSwanDriver']"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml:24(td)
-msgid "max_manifest_size = 2097152"
+#: ./doc/common/tables/neutron-vpn.xml:45(td)
+msgid "(MultiStrOpt) The vpn device drivers Neutron will use"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml:27(td)
-msgid "min_segment_size = 1048576"
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml:7(literal)
+msgid "[object-expirer]"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml:33(td)
-msgid "rate_limit_segments_per_sec = 0"
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml:27(td) ./doc/common/tables/neutron-common.xml:170(td)
+msgid "report_interval = 300"
 msgstr ""
 
-#: ./doc/common/tables/heat-crypt.xml:8(caption)
-msgid "Description of configuration options for crypt"
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml:30(td) ./doc/common/tables/swift-object-server-object-replicator.xml:39(td) ./doc/common/tables/swift-object-server-object-updater.xml:33(td)
+msgid "concurrency = 1"
 msgstr ""
 
-#: ./doc/common/tables/heat-crypt.xml:22(td)
-msgid "auth_encryption_key = notgood but just long enough i think"
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml:30(td) ./doc/common/tables/swift-account-server-account-replicator.xml:39(td) ./doc/common/tables/swift-container-server-container-updater.xml:33(td) ./doc/common/tables/swift-object-server-object-replicator.xml:39(td) ./doc/common/tables/swift-container-server-container-replicator.xml:39(td) ./doc/common/tables/swift-object-server-object-updater.xml:33(td) ./doc/common/tables/swift-dispersion-dispersion.xml:54(td) ./doc/common/tables/swift-account-server-account-reaper.xml:30(td)
+msgid "Number of replication workers to spawn"
 msgstr ""
 
-#: ./doc/common/tables/heat-crypt.xml:23(td)
-msgid "(StrOpt) Encryption key used for authentication info in database."
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml:33(td)
+msgid "processes = 0"
 msgstr ""
 
-#: ./doc/common/tables/neutron-wsgi.xml:26(td)
-msgid "retry_until_window = 30"
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml:36(td)
+msgid "process = 0"
 msgstr ""
 
-#: ./doc/common/tables/neutron-wsgi.xml:27(td)
-msgid "(IntOpt) Number of seconds to keep retrying to listen"
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml:36(td)
+msgid "(it will actually accept(2) N + 1). Setting this to one (1) will only handle one request at a time, without accepting another request concurrently."
 msgstr ""
 
-#: ./doc/common/tables/neutron-scheduler.xml:8(caption) ./doc/common/tables/cinder-scheduler.xml:8(caption)
-msgid "Description of configuration options for scheduler"
+#: ./doc/common/tables/trove-common.xml:22(td)
+msgid "configurations_page_size = 20"
 msgstr ""
 
-#: ./doc/common/tables/neutron-scheduler.xml:22(td)
-msgid "network_auto_schedule = True"
+#: ./doc/common/tables/trove-common.xml:23(td) ./doc/common/tables/trove-common.xml:27(td) ./doc/common/tables/trove-common.xml:47(td) ./doc/common/tables/trove-api.xml:35(td) ./doc/common/tables/trove-api.xml:47(td) ./doc/common/tables/trove-api.xml:51(td) ./doc/common/tables/trove-api.xml:55(td) ./doc/common/tables/trove-api.xml:59(td) ./doc/common/tables/trove-api.xml:63(td) ./doc/common/tables/trove-api.xml:79(td) ./doc/common/tables/trove-api.xml:87(td) ./doc/common/tables/trove-api.xml:103(td) ./doc/common/tables/trove-dns.xml:71(td) ./doc/common/tables/trove-dns.xml:75(td) ./doc/common/tables/trove-volume.xml:39(td) ./doc/common/tables/trove-volume.xml:47(td) ./doc/common/tables/trove-heat.xml:23(td) ./doc/common/tables/trove-rpc.xml:39(td) ./doc/common/tables/trove-rpc.xml:43(td) ./doc/common/tables/trove-backup.xml:71(td) ./doc/common/tables/trove-guestagent.xml:23(td) ./doc/common/tables/trove-guestagent.xml:27(td) ./doc/common/tables/trove-guestagent.xml:31(td) ./doc/common/tables/trove-database.xml:27(td) ./doc/common/tables/trove-taskmanager.xml:43(td) ./doc/common/tables/trove-taskmanager.xml:47(td) ./doc/common/tables/trove-taskmanager.xml:51(td) ./doc/common/tables/trove-taskmanager.xml:55(td) ./doc/common/tables/trove-taskmanager.xml:59(td)
+msgid "(IntOpt) No help text available for this option."
 msgstr ""
 
-#: ./doc/common/tables/neutron-scheduler.xml:23(td)
-msgid "(BoolOpt) Allow auto scheduling networks to DHCP agent."
+#: ./doc/common/tables/trove-common.xml:26(td)
+msgid "databases_page_size = 20"
 msgstr ""
 
-#: ./doc/common/tables/neutron-scheduler.xml:26(td)
-msgid "network_scheduler_driver = neutron.scheduler.dhcp_agent_scheduler.ChanceScheduler"
+#: ./doc/common/tables/trove-common.xml:30(td)
+msgid "default_datastore = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-scheduler.xml:27(td)
-msgid "(StrOpt) Driver to use for scheduling network to DHCP agent"
+#: ./doc/common/tables/trove-common.xml:31(td)
+msgid "(StrOpt) The default datastore id or name to use if one is not provided by the user. If the default value is None, the field becomes required in the instance-create request."
 msgstr ""
 
-#: ./doc/common/tables/neutron-scheduler.xml:30(td)
-msgid "router_auto_schedule = True"
+#: ./doc/common/tables/trove-common.xml:38(td)
+msgid "default_neutron_networks ="
 msgstr ""
 
-#: ./doc/common/tables/neutron-scheduler.xml:31(td)
-msgid "(BoolOpt) Allow auto scheduling of routers to L3 agent."
+#: ./doc/common/tables/trove-common.xml:39(td)
+msgid "(ListOpt) List of network IDs which should be attached to instance when networks are not specified in API call."
 msgstr ""
 
-#: ./doc/common/tables/neutron-scheduler.xml:34(td)
-msgid "router_delete_namespaces = False"
+#: ./doc/common/tables/trove-common.xml:46(td)
+msgid "default_password_length = 36"
 msgstr ""
 
-#: ./doc/common/tables/neutron-scheduler.xml:35(td)
-msgid "(BoolOpt) Delete namespace after removing a router."
+#: ./doc/common/tables/trove-common.xml:50(td) ./doc/common/tables/neutron-notifier.xml:26(td)
+msgid "default_publisher_id = $host"
 msgstr ""
 
-#: ./doc/common/tables/neutron-scheduler.xml:38(td)
-msgid "router_scheduler_driver = neutron.scheduler.l3_agent_scheduler.ChanceScheduler"
+#: ./doc/common/tables/trove-common.xml:54(td)
+msgid "expected_filetype_suffixes = json"
 msgstr ""
 
-#: ./doc/common/tables/neutron-scheduler.xml:39(td)
-msgid "(StrOpt) Driver to use for scheduling router to a default L3 agent"
+#: ./doc/common/tables/trove-common.xml:55(td)
+msgid "(ListOpt) Filetype endings not to be reattached to an id by the utils method correct_id_with_req."
 msgstr ""
 
-#: ./doc/common/tables/keystone-security.xml:8(caption)
-msgid "Description of configuration options for security"
+#: ./doc/common/tables/trove-common.xml:62(td)
+msgid "pybasedir = /usr/lib/python/site-packages/trove"
 msgstr ""
 
-#: ./doc/common/tables/keystone-security.xml:22(td)
-msgid "crypt_strength = 40000"
+#: ./doc/common/tables/trove-common.xml:63(td)
+msgid "(StrOpt) Directory where the trove python module is installed."
 msgstr ""
 
-#: ./doc/common/tables/keystone-security.xml:23(td)
-msgid "(IntOpt) The value passed as the keyword \"rounds\" to passlib encrypt method."
+#: ./doc/common/tables/trove-common.xml:66(td)
+msgid "pydev_path = None"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-vmware.xml:19(th) ./doc/common/tables/nova-vnc.xml:42(th) ./doc/common/tables/nova-vmware.xml:19(th) ./doc/common/tables/nova-network.xml:254(th)
-msgid "[vmware]"
+#: ./doc/common/tables/trove-common.xml:67(td)
+msgid "(StrOpt) Set path to pydevd library, used if pydevd is not found in python sys.path."
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-vmware.xml:22(td) ./doc/common/tables/nova-vmware.xml:22(td)
-msgid "api_retry_count = 10"
+#: ./doc/common/tables/trove-common.xml:70(td)
+msgid "taskmanager_queue = taskmanager"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-vmware.xml:23(td)
-msgid "(IntOpt) Number of times a VMware Vsphere API must be retried"
+#: ./doc/common/tables/trove-common.xml:74(td)
+msgid "template_path = /etc/trove/templates/"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-vmware.xml:26(td)
-msgid "host_ip ="
+#: ./doc/common/tables/trove-common.xml:75(td)
+msgid "(StrOpt) Path which leads to datastore templates."
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-vmware.xml:27(td)
-msgid "(StrOpt) IP address of the VMware Vsphere host"
+#: ./doc/common/tables/trove-api.xml:22(td)
+msgid "admin_roles = admin"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-vmware.xml:30(td)
-msgid "host_password ="
+#: ./doc/common/tables/trove-api.xml:23(td) ./doc/common/tables/trove-guestagent.xml:43(td) ./doc/common/tables/trove-guestagent.xml:47(td) ./doc/common/tables/trove-compute.xml:31(td)
+msgid "(ListOpt) No help text available for this option."
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-vmware.xml:31(td)
-msgid "(StrOpt) Password of VMware Vsphere"
+#: ./doc/common/tables/trove-api.xml:26(td)
+msgid "api_extensions_path = trove/extensions/routes"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-vmware.xml:34(td)
-msgid "host_username ="
+#: ./doc/common/tables/trove-api.xml:27(td)
+msgid "(StrOpt) Path to extensions."
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-vmware.xml:35(td)
-msgid "(StrOpt) Username of VMware Vsphere"
+#: ./doc/common/tables/trove-api.xml:30(td) ./doc/common/tables/heat-api.xml:134(td) ./doc/common/tables/cinder-api.xml:22(td) ./doc/common/tables/neutron-api.xml:38(td) ./doc/common/tables/nova-wsgi.xml:22(td)
+msgid "api_paste_config = api-paste.ini"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-vmware.xml:38(td) ./doc/common/tables/nova-vmware.xml:54(td)
-msgid "task_poll_interval = 0.5"
+#: ./doc/common/tables/trove-api.xml:31(td)
+msgid "(StrOpt) File name for the paste.deploy config for trove-api."
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-vmware.xml:39(td)
-msgid "(FloatOpt) Sleep time in seconds for polling an ongoing async task"
+#: ./doc/common/tables/trove-api.xml:34(td)
+msgid "bind_port = 8779"
 msgstr ""
 
-#: ./doc/common/tables/glance-rbd.xml:8(caption)
-msgid "Description of configuration options for rbd"
+#: ./doc/common/tables/trove-api.xml:38(td)
+msgid "db_api_implementation = trove.db.sqlalchemy.api"
 msgstr ""
 
-#: ./doc/common/tables/glance-rbd.xml:22(td)
-msgid "rbd_store_ceph_conf = /etc/ceph/ceph.conf"
+#: ./doc/common/tables/trove-api.xml:42(td)
+msgid "hostname_require_ipv4 = True"
 msgstr ""
 
-#: ./doc/common/tables/glance-rbd.xml:23(td)
-msgid "(StrOpt) Ceph configuration file path. If &lt;None&gt;, librados will locate the default config. If using cephx authentication, this file should include a reference to the right keyring in a client.&lt;USER&gt; section."
+#: ./doc/common/tables/trove-api.xml:43(td)
+msgid "(BoolOpt) Require user hostnames to be IPv4 addresses."
 msgstr ""
 
-#: ./doc/common/tables/glance-rbd.xml:26(td)
-msgid "rbd_store_chunk_size = 8"
+#: ./doc/common/tables/trove-api.xml:46(td)
+msgid "http_delete_rate = 200"
 msgstr ""
 
-#: ./doc/common/tables/glance-rbd.xml:27(td)
-msgid "(IntOpt) RADOS images will be chunked into objects of this size (in megabytes). For best performance, this should be a power of two."
+#: ./doc/common/tables/trove-api.xml:50(td)
+msgid "http_get_rate = 200"
 msgstr ""
 
-#: ./doc/common/tables/glance-rbd.xml:30(td)
-msgid "rbd_store_pool = images"
+#: ./doc/common/tables/trove-api.xml:54(td)
+msgid "http_post_rate = 200"
 msgstr ""
 
-#: ./doc/common/tables/glance-rbd.xml:31(td)
-msgid "(StrOpt) RADOS pool in which images are stored."
+#: ./doc/common/tables/trove-api.xml:58(td)
+msgid "http_put_rate = 200"
 msgstr ""
 
-#: ./doc/common/tables/glance-rbd.xml:34(td)
-msgid "rbd_store_user = None"
+#: ./doc/common/tables/trove-api.xml:62(td)
+msgid "instances_page_size = 20"
 msgstr ""
 
-#: ./doc/common/tables/glance-rbd.xml:35(td)
-msgid "(StrOpt) RADOS user to authenticate as (only applicable if using Cephx. If &lt;None&gt;, a default will be chosen based on the client. section in rbd_store_ceph_conf)."
+#: ./doc/common/tables/trove-api.xml:67(td) ./doc/common/tables/glance-wsgi.xml:31(td)
+msgid "(IntOpt) Maximum line size of message headers to be accepted. max_header_line may need to be increased when using large tokens (typically those generated by the Keystone v3 API with big service catalogs"
 msgstr ""
 
-#: ./doc/common/tables/heat-clients_heat.xml:8(caption)
-msgid "Description of configuration options for clients_heat"
+#: ./doc/common/tables/trove-api.xml:70(td)
+msgid "region = LOCAL_DEV"
 msgstr ""
 
-#: ./doc/common/tables/heat-clients_heat.xml:19(th)
-msgid "[clients_heat]"
+#: ./doc/common/tables/trove-api.xml:71(td)
+msgid "(StrOpt) The region this service is located."
 msgstr ""
 
-#: ./doc/common/tables/heat-clients_heat.xml:42(td) ./doc/common/tables/neutron-ml2_odl.xml:34(td) ./doc/common/tables/neutron-ml2_ncs.xml:30(td)
-msgid "url = None"
+#: ./doc/common/tables/trove-api.xml:75(td) ./doc/common/tables/cinder-common.xml:199(td) ./doc/common/tables/neutron-wsgi.xml:31(td) ./doc/common/tables/nova-wsgi.xml:39(td)
+msgid "(IntOpt) Sets the value of TCP_KEEPIDLE in seconds for each server socket. Not supported on OS X."
 msgstr ""
 
-#: ./doc/common/tables/heat-clients_heat.xml:43(td)
-msgid "(StrOpt) Optional heat url in format like http://0.0.0.0:8004/v1/%(tenant_id)s."
+#: ./doc/common/tables/trove-api.xml:78(td)
+msgid "trove_api_workers = None"
 msgstr ""
 
-#: ./doc/common/tables/heat-rabbitmq.xml:35(td) ./doc/common/tables/trove-amqp.xml:55(td)
-msgid "(StrOpt) SSL version to use (valid only if SSL enabled). valid values are TLSv1, SSLv23 and SSLv3. SSLv2 may be available on some distributions"
+#: ./doc/common/tables/trove-api.xml:82(td)
+msgid "trove_auth_url = http://0.0.0.0:5000/v2.0"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-logging.xml:30(td) ./doc/common/tables/neutron-notifier.xml:22(td) ./doc/common/tables/heat-amqp.xml:34(td) ./doc/common/tables/trove-common.xml:42(td) ./doc/common/tables/nova-compute.xml:54(td)
-msgid "default_notification_level = INFO"
+#: ./doc/common/tables/trove-api.xml:86(td)
+msgid "trove_conductor_workers = 1"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-logging.xml:31(td) ./doc/common/tables/neutron-notifier.xml:23(td) ./doc/common/tables/heat-amqp.xml:35(td) ./doc/common/tables/trove-common.xml:43(td) ./doc/common/tables/nova-compute.xml:55(td)
-msgid "(StrOpt) Default notification level for outgoing notifications"
+#: ./doc/common/tables/trove-api.xml:90(td)
+msgid "trove_security_group_name_prefix = SecGroup"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-logging.xml:105(td) ./doc/common/tables/neutron-cadf.xml:22(td)
-msgid "api_audit_map = api_audit_map.conf"
+#: ./doc/common/tables/trove-api.xml:94(td)
+msgid "trove_security_group_rule_cidr = 0.0.0.0/0"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-logging.xml:106(td) ./doc/common/tables/neutron-cadf.xml:23(td)
-msgid "(StrOpt) File containing mapping for api paths and service endpoints"
+#: ./doc/common/tables/trove-api.xml:98(td)
+msgid "trove_security_groups_support = True"
 msgstr ""
 
-#: ./doc/common/tables/neutron-metadata.xml:22(td)
-msgid "meta_flavor_driver_mappings = None"
+#: ./doc/common/tables/trove-api.xml:99(td) ./doc/common/tables/trove-dns.xml:83(td) ./doc/common/tables/trove-compute.xml:35(td) ./doc/common/tables/trove-database.xml:31(td) ./doc/common/tables/trove-taskmanager.xml:71(td) ./doc/common/tables/trove-taskmanager.xml:75(td)
+msgid "(BoolOpt) No help text available for this option."
 msgstr ""
 
-#: ./doc/common/tables/neutron-metadata.xml:23(td)
-msgid "(StrOpt) Mapping between flavor and LinuxInterfaceDriver"
+#: ./doc/common/tables/trove-api.xml:102(td)
+msgid "users_page_size = 20"
 msgstr ""
 
-#: ./doc/common/tables/neutron-metadata.xml:26(td)
-msgid "metadata_backlog = 128"
+#: ./doc/common/tables/cinder-zadara.xml:8(caption)
+msgid "Description of configuration options for zadara"
 msgstr ""
 
-#: ./doc/common/tables/neutron-metadata.xml:27(td)
-msgid "(IntOpt) Number of backlog requests to configure the metadata server socket with"
+#: ./doc/common/tables/cinder-zadara.xml:22(td)
+msgid "zadara_password = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-metadata.xml:30(td)
-msgid "metadata_port = 9697"
+#: ./doc/common/tables/cinder-zadara.xml:23(td)
+msgid "(StrOpt) Password for the VPSA"
 msgstr ""
 
-#: ./doc/common/tables/neutron-metadata.xml:31(td)
-msgid "(IntOpt) TCP Port used by Neutron metadata namespace proxy."
+#: ./doc/common/tables/cinder-zadara.xml:26(td)
+msgid "zadara_user = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-metadata.xml:34(td)
-msgid "metadata_proxy_shared_secret ="
+#: ./doc/common/tables/cinder-zadara.xml:27(td)
+msgid "(StrOpt) User name for the VPSA"
 msgstr ""
 
-#: ./doc/common/tables/neutron-metadata.xml:35(td) ./doc/common/tables/neutron-vmware.xml:146(td)
-msgid "(StrOpt) Shared secret to sign instance-id request"
+#: ./doc/common/tables/cinder-zadara.xml:30(td)
+msgid "zadara_vol_encrypt = False"
 msgstr ""
 
-#: ./doc/common/tables/neutron-metadata.xml:38(td)
-msgid "metadata_proxy_socket = $state_path/metadata_proxy"
+#: ./doc/common/tables/cinder-zadara.xml:31(td)
+msgid "(BoolOpt) Default encryption policy for volumes"
 msgstr ""
 
-#: ./doc/common/tables/neutron-metadata.xml:39(td)
-msgid "(StrOpt) Location of Metadata Proxy UNIX domain socket"
+#: ./doc/common/tables/cinder-zadara.xml:34(td)
+msgid "zadara_vol_name_template = OS_%s"
 msgstr ""
 
-#: ./doc/common/tables/neutron-metadata.xml:42(td)
-msgid "metadata_workers = 0"
+#: ./doc/common/tables/cinder-zadara.xml:35(td)
+msgid "(StrOpt) Default template for VPSA volume names"
 msgstr ""
 
-#: ./doc/common/tables/neutron-metadata.xml:43(td)
-msgid "(IntOpt) Number of separate worker processes for metadata server"
+#: ./doc/common/tables/cinder-zadara.xml:38(td)
+msgid "zadara_vol_thin = True"
 msgstr ""
 
-#: ./doc/common/tables/neutron-metadata.xml:46(td)
-msgid "nova_metadata_ip = 127.0.0.1"
+#: ./doc/common/tables/cinder-zadara.xml:39(td)
+msgid "(BoolOpt) Default thin provisioning policy for volumes"
 msgstr ""
 
-#: ./doc/common/tables/neutron-metadata.xml:47(td)
-msgid "(StrOpt) IP address used by Nova metadata server."
+#: ./doc/common/tables/cinder-zadara.xml:42(td)
+msgid "zadara_vpsa_allow_nonexistent_delete = True"
 msgstr ""
 
-#: ./doc/common/tables/neutron-metadata.xml:50(td)
-msgid "nova_metadata_port = 8775"
+#: ./doc/common/tables/cinder-zadara.xml:43(td)
+msgid "(BoolOpt) Don't halt on deletion of non-existing volumes"
 msgstr ""
 
-#: ./doc/common/tables/neutron-metadata.xml:51(td)
-msgid "(IntOpt) TCP Port used by Nova metadata server."
+#: ./doc/common/tables/cinder-zadara.xml:46(td)
+msgid "zadara_vpsa_auto_detach_on_delete = True"
 msgstr ""
 
-#: ./doc/common/tables/glance-redis.xml:23(td) ./doc/common/tables/keystone-redis.xml:23(td)
-msgid "(StrOpt) Host to locate redis."
+#: ./doc/common/tables/cinder-zadara.xml:47(td)
+msgid "(BoolOpt) Automatically detach from servers on volume delete"
 msgstr ""
 
-#: ./doc/common/tables/keystone-stats.xml:8(caption)
-msgid "Description of configuration options for stats"
+#: ./doc/common/tables/cinder-zadara.xml:50(td)
+msgid "zadara_vpsa_ip = None"
 msgstr ""
 
-#: ./doc/common/tables/keystone-stats.xml:19(th)
-msgid "[stats]"
+#: ./doc/common/tables/cinder-zadara.xml:51(td)
+msgid "(StrOpt) Management IP of Zadara VPSA"
 msgstr ""
 
-#: ./doc/common/tables/keystone-stats.xml:22(td)
-msgid "driver = keystone.contrib.stats.backends.kvs.Stats"
+#: ./doc/common/tables/cinder-zadara.xml:54(td)
+msgid "zadara_vpsa_poolname = None"
 msgstr ""
 
-#: ./doc/common/tables/keystone-stats.xml:23(td)
-msgid "(StrOpt) Keystone stats backend driver."
+#: ./doc/common/tables/cinder-zadara.xml:55(td)
+msgid "(StrOpt) Name of VPSA storage pool for volumes"
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml:8(caption)
-msgid "Description of configuration options for hp3par"
+#: ./doc/common/tables/cinder-zadara.xml:58(td)
+msgid "zadara_vpsa_port = None"
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml:22(td)
-msgid "hp3par_api_url ="
+#: ./doc/common/tables/cinder-zadara.xml:59(td)
+msgid "(StrOpt) Zadara VPSA port number"
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml:23(td)
-msgid "(StrOpt) 3PAR WSAPI Server Url like https://&lt;3par ip&gt;:8080/api/v1"
+#: ./doc/common/tables/cinder-zadara.xml:62(td)
+msgid "zadara_vpsa_use_ssl = False"
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml:26(td)
-msgid "hp3par_cpg = OpenStack"
+#: ./doc/common/tables/cinder-zadara.xml:63(td)
+msgid "(BoolOpt) Use SSL connection"
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml:27(td)
-msgid "(StrOpt) The CPG to use for volume creation"
+#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml:7(literal) ./doc/common/tables/swift-object-server-app-object-server.xml:7(literal) ./doc/common/tables/swift-object-server-DEFAULT.xml:7(literal) ./doc/common/tables/swift-object-server-object-replicator.xml:7(literal) ./doc/common/tables/swift-object-server-pipeline-main.xml:7(literal) ./doc/common/tables/swift-object-server-object-auditor.xml:7(literal) ./doc/common/tables/swift-object-server-filter-recon.xml:7(literal) ./doc/common/tables/swift-object-server-object-updater.xml:7(literal)
+msgid "object-server.conf-sample"
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml:30(td)
-msgid "hp3par_cpg_snap ="
+#: ./doc/common/tables/nova-conductor.xml:8(caption)
+msgid "Description of configuration options for conductor"
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml:31(td)
-msgid "(StrOpt) The CPG to use for Snapshots for volumes. If empty hp3par_cpg will be used"
+#: ./doc/common/tables/nova-conductor.xml:22(td)
+msgid "migrate_max_retries = -1"
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml:34(td)
-msgid "hp3par_debug = False"
+#: ./doc/common/tables/nova-conductor.xml:23(td)
+msgid "(IntOpt) Number of times to retry live-migration before failing. If == -1, try until out of hosts. If == 0, only try once, no retries."
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml:35(td)
-msgid "(BoolOpt) Enable HTTP debugging to 3PAR"
+#: ./doc/common/tables/nova-conductor.xml:26(th)
+msgid "[conductor]"
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml:38(td)
-msgid "hp3par_iscsi_ips ="
+#: ./doc/common/tables/nova-conductor.xml:29(td)
+msgid "manager = nova.conductor.manager.ConductorManager"
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml:39(td)
-msgid "(ListOpt) List of target iSCSI addresses to use."
+#: ./doc/common/tables/nova-conductor.xml:30(td)
+msgid "(StrOpt) Full class name for the Manager for conductor"
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml:42(td)
-msgid "hp3par_password ="
+#: ./doc/common/tables/nova-conductor.xml:33(td)
+msgid "topic = conductor"
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml:43(td)
-msgid "(StrOpt) 3PAR Super user password"
+#: ./doc/common/tables/nova-conductor.xml:34(td)
+msgid "(StrOpt) The topic on which conductor nodes listen"
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml:46(td)
-msgid "hp3par_snapshot_expiration ="
+#: ./doc/common/tables/nova-conductor.xml:37(td)
+msgid "use_local = False"
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml:47(td)
-msgid "(StrOpt) The time in hours when a snapshot expires and is deleted. This must be larger than expiration"
+#: ./doc/common/tables/nova-conductor.xml:38(td)
+msgid "(BoolOpt) Perform nova-conductor operations locally"
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml:50(td)
-msgid "hp3par_snapshot_retention ="
+#: ./doc/common/tables/nova-conductor.xml:41(td)
+msgid "workers = None"
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml:51(td)
-msgid "(StrOpt) The time in hours to retain a snapshot. You can't delete it before this expires."
+#: ./doc/common/tables/nova-conductor.xml:42(td)
+msgid "(IntOpt) Number of workers for OpenStack Conductor service. The default will be the number of CPUs available."
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml:54(td)
-msgid "hp3par_username ="
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:7(literal)
+msgid "[app:object-server]"
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml:55(td)
-msgid "(StrOpt) 3PAR Super user username"
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:18(td)
+msgid "use = egg:swift#object"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_ceph.xml:8(caption)
-msgid "Description of configuration options for storage_ceph"
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:21(td)
+msgid "set log_name = object-server"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_ceph.xml:22(td)
-msgid "rbd_ceph_conf ="
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:30(td) ./doc/common/tables/swift-account-server-app-account-server.xml:30(td) ./doc/common/tables/swift-container-server-app-container-server.xml:30(td)
+msgid "set log_requests = true"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_ceph.xml:23(td)
-msgid "(StrOpt) path to the ceph configuration file to use"
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:30(td) ./doc/common/tables/swift-account-server-app-account-server.xml:30(td) ./doc/common/tables/swift-container-server-app-container-server.xml:30(td)
+msgid "Whether or not to log requests"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_ceph.xml:26(td)
-msgid "rbd_flatten_volume_from_snapshot = False"
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:36(td)
+msgid "max_upload_time = 86400"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_ceph.xml:27(td)
-msgid "(BoolOpt) flatten volumes created from snapshots to remove dependency"
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:36(td)
+msgid "Maximum time allowed to upload an object"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_ceph.xml:30(td)
-msgid "rbd_max_clone_depth = 5"
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:39(td)
+msgid "slow = 0"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_ceph.xml:31(td)
-msgid "(IntOpt) maximum number of nested clones that can be taken of a volume before enforcing a flatten prior to next clone. A value of zero disables cloning"
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:39(td)
+msgid "If &gt; 0, Minimum time in seconds for a PUT or DELETE request to complete"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_ceph.xml:34(td)
-msgid "rbd_pool = rbd"
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:42(td)
+msgid "keep_cache_size = 5424880"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_ceph.xml:35(td)
-msgid "(StrOpt) the RADOS pool in which rbd volumes are stored"
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:42(td)
+msgid "Largest object size to keep in buffer cache"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_ceph.xml:39(td)
-msgid "(StrOpt) the libvirt uuid of the secret for the rbd_uservolumes"
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:45(td)
+msgid "keep_cache_private = false"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_ceph.xml:43(td)
-msgid "(StrOpt) the RADOS client name for accessing rbd volumes - only set when using cephx authentication"
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:45(td)
+msgid "Allow non-public objects to stay in kernel's buffer cache"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_ceph.xml:46(td)
-msgid "volume_tmp_dir = None"
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:48(td)
+msgid "mb_per_sync = 512"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_ceph.xml:47(td)
-msgid "(StrOpt) where to store temporary image files if the volume driver does not write them directly to the volume"
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:48(td)
+msgid "On PUT requests, sync file every n MB"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:51(td)
+msgid "allowed_headers = Content-Disposition, Content-Encoding, X-Delete-At, X-Object-Manifest, X-Static-Large-Object"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:51(td)
+msgid "Comma-separated list of headers that can be set in metadata of an object"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:57(td)
+msgid "threads_per_disk = 0"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:57(td)
+msgid "Size of the per-disk thread pool used for performing disk I/O. The default of 0 means to not use a per-disk thread pool. It is recommended to keep this value small, as large values can result in high read latencies due to large queue depths. A good starting point is 4 threads per disk."
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:60(td) ./doc/common/tables/swift-account-server-app-account-server.xml:39(td) ./doc/common/tables/swift-container-server-app-container-server.xml:48(td)
+msgid "replication_server = false"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:60(td) ./doc/common/tables/swift-account-server-app-account-server.xml:39(td) ./doc/common/tables/swift-container-server-app-container-server.xml:48(td)
+msgid "If defined, tells server how to handle replication verbs in requests. When set to True (or 1), only replication verbs will be accepted. When set to False, replication verbs will be rejected. When undefined, server will accept any verb in the request."
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:63(td)
+msgid "replication_concurrency = 4"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:63(td)
+msgid "Set to restrict the number of concurrent incoming REPLICATION requests; set to 0 for unlimited"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:66(td)
+msgid "replication_one_per_device = True"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:66(td)
+msgid "Restricts incoming REPLICATION requests to one per device, replication_currency above allowing. This can help control I/O to each device, but you may wish to set this to False to allow multiple REPLICATION requests (up to the above replication_concurrency setting) per device."
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:69(td)
+msgid "replication_lock_timeout = 15"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:69(td)
+msgid "Number of seconds to wait for an existing replication device lock before giving up."
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:72(td)
+msgid "replication_failure_threshold = 100"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:72(td)
+msgid "The number of subrequest failures before the replication_failure_ratio is checked"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:75(td)
+msgid "replication_failure_ratio = 1.0"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml:75(td)
+msgid "If the value of failures / successes of REPLICATION subrequests exceeds this ratio, the overall REPLICATION request will be aborted"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:21(td)
+msgid "set log_name = catch_errors"
 msgstr ""
 
 #: ./doc/common/tables/nova-livemigration.xml:8(caption)
@@ -26271,404 +26631,96 @@ msgstr ""
 msgid "(StrOpt) Migration target URI (any included \"%s\" is replaced with the migration target hostname)"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml:22(td)
-msgid "ldap_dns_base_dn = ou=hosts,dc=example,dc=org"
+#: ./doc/common/tables/heat-rabbitmq.xml:39(td) ./doc/common/tables/trove-rabbitmq.xml:23(td)
+msgid "(BoolOpt) use H/A queues in RabbitMQ (x-ha-policy: all).You need to wipe RabbitMQ database when changing this option."
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml:23(td)
-msgid "(StrOpt) Base DN for DNS entries in LDAP"
+#: ./doc/common/tables/heat-rabbitmq.xml:43(td) ./doc/common/tables/trove-rabbitmq.xml:27(td) ./doc/common/tables/neutron-rabbitmq.xml:27(td) ./doc/common/tables/ceilometer-rabbitmq.xml:47(td)
+msgid "(StrOpt) The RabbitMQ broker address where a single node is used"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml:26(td)
-msgid "ldap_dns_password = password"
+#: ./doc/common/tables/heat-rabbitmq.xml:47(td) ./doc/common/tables/trove-rabbitmq.xml:31(td) ./doc/common/tables/neutron-rabbitmq.xml:31(td) ./doc/common/tables/ceilometer-rabbitmq.xml:51(td)
+msgid "(ListOpt) RabbitMQ HA cluster host:port pairs"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml:27(td)
-msgid "(StrOpt) Password for LDAP DNS"
+#: ./doc/common/tables/heat-rabbitmq.xml:51(td) ./doc/common/tables/trove-rabbitmq.xml:35(td)
+msgid "(IntOpt) maximum retries with trying to connect to RabbitMQ (the default of 0 implies an infinite retry count)"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml:30(td)
-msgid "ldap_dns_servers = ['dns.example.org']"
+#: ./doc/common/tables/heat-rabbitmq.xml:55(td) ./doc/common/tables/trove-rabbitmq.xml:39(td)
+msgid "(StrOpt) the RabbitMQ password"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml:31(td)
-msgid "(MultiStrOpt) DNS Servers for LDAP DNS driver"
+#: ./doc/common/tables/heat-rabbitmq.xml:59(td) ./doc/common/tables/trove-rabbitmq.xml:43(td) ./doc/common/tables/neutron-rabbitmq.xml:43(td) ./doc/common/tables/ceilometer-rabbitmq.xml:63(td)
+msgid "(IntOpt) The RabbitMQ broker port where a single node is used"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml:34(td)
-msgid "ldap_dns_soa_expiry = 86400"
+#: ./doc/common/tables/heat-rabbitmq.xml:63(td) ./doc/common/tables/trove-rabbitmq.xml:47(td)
+msgid "(IntOpt) how long to backoff for between retries when connecting to RabbitMQ"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml:35(td)
-msgid "(StrOpt) Expiry interval (in seconds) for LDAP DNS driver Statement of Authority"
+#: ./doc/common/tables/heat-rabbitmq.xml:67(td) ./doc/common/tables/trove-rabbitmq.xml:51(td)
+msgid "(IntOpt) how frequently to retry connecting with RabbitMQ"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml:38(td)
-msgid "ldap_dns_soa_hostmaster = hostmaster@example.org"
+#: ./doc/common/tables/heat-rabbitmq.xml:71(td) ./doc/common/tables/trove-rabbitmq.xml:55(td)
+msgid "(BoolOpt) connect over SSL for RabbitMQ"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml:39(td)
-msgid "(StrOpt) Hostmaster for LDAP DNS driver Statement of Authority"
+#: ./doc/common/tables/heat-rabbitmq.xml:75(td) ./doc/common/tables/trove-rabbitmq.xml:59(td)
+msgid "(StrOpt) the RabbitMQ userid"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml:42(td)
-msgid "ldap_dns_soa_minimum = 7200"
+#: ./doc/common/tables/heat-rabbitmq.xml:79(td) ./doc/common/tables/trove-rabbitmq.xml:63(td)
+msgid "(StrOpt) the RabbitMQ virtual host"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml:43(td)
-msgid "(StrOpt) Minimum interval (in seconds) for LDAP DNS driver Statement of Authority"
+#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:7(literal)
+msgid "[filter:keystoneauth]"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml:46(td)
-msgid "ldap_dns_soa_refresh = 1800"
+#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:18(td)
+msgid "use = egg:swift#keystoneauth"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml:47(td)
-msgid "(StrOpt) Refresh interval (in seconds) for LDAP DNS driver Statement of Authority"
+#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:21(td)
+msgid "operator_roles = admin, swiftoperator"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml:50(td)
-msgid "ldap_dns_soa_retry = 3600"
+#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:24(td)
+msgid "reseller_admin_role = ResellerAdmin"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml:51(td)
-msgid "(StrOpt) Retry interval (in seconds) for LDAP DNS driver Statement of Authority"
+#: ./doc/common/tables/neutron-cadf.xml:8(caption)
+msgid "Description of configuration options for cadf"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml:54(td)
-msgid "ldap_dns_url = ldap://ldap.example.com:389"
+#: ./doc/common/tables/keystone-amqp.xml:46(td) ./doc/common/tables/glance-amqp.xml:38(td) ./doc/common/tables/cinder-rpc.xml:182(td) ./doc/common/tables/nova-rpc_all.xml:150(td) ./doc/common/tables/nova-rpc.xml:42(td)
+msgid "rpc_backend = rabbit"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml:55(td)
-msgid "(StrOpt) URL for LDAP server which will store DNS entries"
+#: ./doc/common/tables/keystone-amqp.xml:47(td) ./doc/common/tables/glance-amqp.xml:39(td) ./doc/common/tables/cinder-rpc.xml:183(td) ./doc/common/tables/nova-rpc_all.xml:151(td) ./doc/common/tables/nova-rpc.xml:43(td)
+msgid "(StrOpt) The messaging driver to use, defaults to rabbit. Other drivers include qpid and zmq."
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml:58(td)
-msgid "ldap_dns_user = uid=admin,ou=people,dc=example,dc=org"
+#: ./doc/common/tables/keystone-amqp.xml:55(td) ./doc/common/tables/glance-amqp.xml:43(td) ./doc/common/tables/cinder-rpc.xml:191(td) ./doc/common/tables/nova-rpc_all.xml:159(td) ./doc/common/tables/nova-rpc.xml:51(td)
+msgid "(IntOpt) Size of RPC connection pool."
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml:59(td)
-msgid "(StrOpt) User for LDAP DNS"
+#: ./doc/common/tables/keystone-amqp.xml:59(td) ./doc/common/tables/glance-amqp.xml:47(td) ./doc/common/tables/cinder-rpc.xml:195(td) ./doc/common/tables/nova-rpc_all.xml:163(td) ./doc/common/tables/nova-rpc.xml:55(td)
+msgid "(IntOpt) Seconds to wait for a response from a call."
 msgstr ""
 
-#: ./doc/common/tables/nova-fping.xml:8(caption)
-msgid "Description of configuration options for fping"
-msgstr ""
-
-#: ./doc/common/tables/nova-fping.xml:22(td)
-msgid "fping_path = /usr/sbin/fping"
-msgstr ""
-
-#: ./doc/common/tables/nova-fping.xml:23(td)
-msgid "(StrOpt) Full path to fping."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_swift.xml:8(caption)
-msgid "Description of configuration options for clients_swift"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_swift.xml:19(th)
-msgid "[clients_swift]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-securitygroups.xml:8(caption)
-msgid "Description of configuration options for securitygroups"
-msgstr ""
-
-#: ./doc/common/tables/neutron-securitygroups.xml:19(th)
-msgid "[SECURITYGROUP]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-securitygroups.xml:22(td)
-msgid "enable_security_group = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-securitygroups.xml:23(td)
-msgid "(BoolOpt) Controls whether the neutron security group API is enabled in the server. It should be false when using no security groups or using the nova security group API."
-msgstr ""
-
-#: ./doc/common/tables/neutron-securitygroups.xml:26(td) ./doc/common/tables/nova-network.xml:78(td)
-msgid "firewall_driver = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-securitygroups.xml:27(td)
-msgid "(StrOpt) Driver for security groups firewall in the L2 agent"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:8(caption)
-msgid "Description of configuration options for netapp_cdot_iscsi"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:54(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:58(td)
-msgid "netapp_vserver = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:55(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:59(td)
-msgid "(StrOpt) This option specifies the virtual storage server (Vserver) name on the storage cluster on which provisioning of block storage volumes should occur. If using the NFS storage protocol, this parameter is mandatory for storage service catalog support (utilized by Cinder volume type extra_specs support). If this option is specified, the exports belonging to the Vserver will only be used for provisioning in the future. Block storage volumes on exports not belonging to the Vserver specified by this option will continue to function normally."
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:8(caption) ./doc/common/tables/keystone-ec2.xml:8(caption)
-msgid "Description of configuration options for ec2"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:22(td)
-msgid "ec2_dmz_host = $my_ip"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:23(td)
-msgid "(StrOpt) The internal IP address of the EC2 API server"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:26(td)
-msgid "ec2_host = $my_ip"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:27(td)
-msgid "(StrOpt) The IP address of the EC2 API server"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:30(td)
-msgid "ec2_listen = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:31(td)
-msgid "(StrOpt) The IP address on which the EC2 API will listen."
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:34(td)
-msgid "ec2_listen_port = 8773"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:35(td)
-msgid "(IntOpt) The port on which the EC2 API will listen."
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:38(td)
-msgid "ec2_path = /services/Cloud"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:39(td)
-msgid "(StrOpt) The path prefix used to call the ec2 API server"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:42(td)
-msgid "ec2_port = 8773"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:43(td)
-msgid "(IntOpt) The port of the EC2 API server"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:46(td)
-msgid "ec2_private_dns_show_ip = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:47(td)
-msgid "(BoolOpt) Return the IP address as private dns hostname in describe instances"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:50(td)
-msgid "ec2_scheme = http"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:51(td)
-msgid "(StrOpt) The protocol to use when connecting to the EC2 API server (http, https)"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:54(td)
-msgid "ec2_strict_validation = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:55(td)
-msgid "(BoolOpt) Validate security group names according to EC2 specification"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:58(td)
-msgid "ec2_timestamp_expiry = 300"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:59(td)
-msgid "(IntOpt) Time in seconds before ec2 timestamp expires"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:62(td)
-msgid "ec2_workers = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:63(td)
-msgid "(IntOpt) Number of workers for EC2 API service. The default will be equal to the number of CPUs available."
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:66(td) ./doc/common/tables/keystone-ec2.xml:38(td)
-msgid "keystone_ec2_url = http://localhost:5000/v2.0/ec2tokens"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:67(td) ./doc/common/tables/keystone-ec2.xml:39(td)
-msgid "(StrOpt) URL to get token from ec2 request."
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:70(td)
-msgid "lockout_attempts = 5"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:71(td)
-msgid "(IntOpt) Number of failed auths before lockout."
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:74(td)
-msgid "lockout_minutes = 15"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:75(td)
-msgid "(IntOpt) Number of minutes to lockout if triggered."
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:78(td)
-msgid "lockout_window = 15"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:79(td)
-msgid "(IntOpt) Number of minutes for lockout window."
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:82(td)
-msgid "region_list ="
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml:83(td)
-msgid "(ListOpt) List of region=fqdn pairs separated by commas"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-account-auditor.xml:7(literal)
-msgid "[account-auditor]"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-account-auditor.xml:18(td)
-msgid "log_name = account-auditor"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-account-auditor.xml:30(td) ./doc/common/tables/swift-container-server-container-auditor.xml:30(td)
-msgid "interval = 1800"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-account-auditor.xml:39(td)
-msgid "accounts_per_second = 200"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-account-auditor.xml:39(td)
-msgid "Maximum accounts audited per second. Should be tuned according to individual system specs. 0 is unlimited."
-msgstr ""
-
-#: ./doc/common/tables/trove-zeromq.xml:27(td) ./doc/common/tables/ceilometer-rpc.xml:55(td) ./doc/common/tables/heat-zeromq.xml:27(td) ./doc/common/tables/neutron-zeromq.xml:27(td)
-msgid "(IntOpt) Number of ZeroMQ contexts, defaults to 1"
-msgstr ""
-
-#: ./doc/common/tables/trove-zeromq.xml:35(td) ./doc/common/tables/ceilometer-rpc.xml:63(td) ./doc/common/tables/heat-zeromq.xml:35(td) ./doc/common/tables/neutron-zeromq.xml:35(td)
-msgid "(StrOpt) Directory for holding IPC sockets"
-msgstr ""
-
-#: ./doc/common/tables/trove-zeromq.xml:38(td)
-msgid "rpc_zmq_matchmaker = trove.openstack.common.rpc.matchmaker.MatchMakerLocalhost"
-msgstr ""
-
-#: ./doc/common/tables/trove-zeromq.xml:39(td) ./doc/common/tables/ceilometer-rpc.xml:67(td) ./doc/common/tables/heat-zeromq.xml:39(td) ./doc/common/tables/neutron-zeromq.xml:39(td)
-msgid "(StrOpt) MatchMaker driver"
-msgstr ""
-
-#: ./doc/common/tables/trove-zeromq.xml:43(td) ./doc/common/tables/ceilometer-rpc.xml:71(td) ./doc/common/tables/heat-zeromq.xml:43(td) ./doc/common/tables/neutron-zeromq.xml:43(td)
-msgid "(IntOpt) ZeroMQ receiver listening port"
-msgstr ""
-
-#: ./doc/common/tables/heat-database.xml:8(caption) ./doc/common/tables/ceilometer-database.xml:8(caption) ./doc/common/tables/cinder-database.xml:8(caption) ./doc/common/tables/trove-database.xml:8(caption) ./doc/common/tables/keystone-database.xml:8(caption)
-msgid "Description of configuration options for database"
-msgstr ""
-
-#: ./doc/common/tables/heat-database.xml:22(td) ./doc/common/tables/cinder-database.xml:22(td) ./doc/common/tables/nova-baremetal.xml:22(td)
-msgid "db_backend = sqlalchemy"
-msgstr ""
-
-#: ./doc/common/tables/heat-database.xml:23(td)
-msgid "(StrOpt) The backend to use for db."
-msgstr ""
-
-#: ./doc/common/tables/heat-database.xml:26(td)
-msgid "sqlite_db = heat.sqlite"
-msgstr ""
-
-#: ./doc/common/tables/heat-database.xml:27(td) ./doc/common/tables/cinder-common.xml:167(td)
-msgid "(StrOpt) the filename to use with sqlite"
-msgstr ""
-
-#: ./doc/common/tables/heat-database.xml:31(td) ./doc/common/tables/cinder-common.xml:171(td)
-msgid "(BoolOpt) If true, use synchronous mode for sqlite"
-msgstr ""
-
-#: ./doc/common/tables/heat-database.xml:41(td)
-msgid "connection = sqlite:////usr/lib/python/site-packages/heat/openstack/common/db/$sqlite_db"
-msgstr ""
-
-#: ./doc/common/tables/heat-database.xml:54(td) ./doc/common/tables/cinder-common.xml:230(td)
-msgid "(IntOpt) timeout before idle sql connections are reaped"
-msgstr ""
-
-#: ./doc/common/tables/heat-database.xml:66(td) ./doc/common/tables/cinder-storage.xml:150(td)
-msgid "(IntOpt) maximum db connection retries during startup. (setting -1 implies an infinite retry count)"
-msgstr ""
-
-#: ./doc/common/tables/heat-database.xml:78(td) ./doc/common/tables/cinder-common.xml:234(td)
-msgid "(IntOpt) interval between retries of opening a sql connection"
-msgstr ""
-
-#: ./doc/common/tables/heat-database.xml:81(td) ./doc/common/tables/ceilometer-database.xml:85(td) ./doc/common/tables/neutron-db.xml:93(td)
-msgid "slave_connection ="
-msgstr ""
-
-#: ./doc/common/tables/keystone-catalog.xml:8(caption)
-msgid "Description of configuration options for catalog"
-msgstr ""
-
-#: ./doc/common/tables/keystone-catalog.xml:19(th)
-msgid "[catalog]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-catalog.xml:22(td)
-msgid "driver = keystone.catalog.backends.sql.Catalog"
-msgstr ""
-
-#: ./doc/common/tables/keystone-catalog.xml:23(td)
-msgid "(StrOpt) Keystone catalog backend driver."
-msgstr ""
-
-#: ./doc/common/tables/keystone-catalog.xml:27(td)
-msgid "(IntOpt) Maximum number of entities that will be returned in a catalog collection."
-msgstr ""
-
-#: ./doc/common/tables/keystone-catalog.xml:30(td)
-msgid "template_file = default_catalog.templates"
-msgstr ""
-
-#: ./doc/common/tables/keystone-catalog.xml:31(td)
-msgid "(StrOpt) Catalog template file name for use with the template catalog backend."
+#: ./doc/common/tables/keystone-amqp.xml:63(td) ./doc/common/tables/glance-amqp.xml:51(td) ./doc/common/tables/cinder-rpc.xml:199(td) ./doc/common/tables/nova-rpc_all.xml:167(td) ./doc/common/tables/nova-rpc.xml:59(td)
+msgid "(IntOpt) Size of RPC greenthread pool."
 msgstr ""
 
 #: ./doc/common/tables/swift-object-server-DEFAULT.xml:21(td)
 msgid "bind_port = 6000"
 msgstr ""
 
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml:45(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:64(td)
-msgid "expiring_objects_container_divisor = 86400"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml:48(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:67(td) ./doc/common/tables/swift-object-expirer-object-expirer.xml:24(td)
-msgid "expiring_objects_account_name = expiring_objects"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml:115(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:118(td)
-msgid "client_timeout = 60"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml:115(td) ./doc/common/tables/swift-proxy-server-DEFAULT.xml:118(td)
-msgid "Timeout to read one chunk from a client external services"
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml:112(td) ./doc/common/tables/swift-container-server-container-updater.xml:36(td) ./doc/common/tables/swift-container-server-app-container-server.xml:36(td)
+msgid "node_timeout = 3"
 msgstr ""
 
 #: ./doc/common/tables/swift-object-server-DEFAULT.xml:118(td)
@@ -26687,324 +26739,148 @@ msgstr ""
 msgid "Size of chunks to read/write to disk"
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml:8(caption) ./doc/common/tables/neutron-rootwrap.xml:8(caption) ./doc/common/tables/nova-rootwrap.xml:8(caption)
-msgid "Description of configuration options for rootwrap"
+#: ./doc/common/tables/cinder-zones.xml:8(caption)
+msgid "Description of configuration options for zones"
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml:22(td)
-msgid "filters_path = /etc/cinder/rootwrap.d,/usr/share/cinder/rootwrap"
+#: ./doc/common/tables/cinder-zones.xml:22(td)
+msgid "cloned_volume_same_az = True"
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml:23(td) ./doc/common/tables/neutron-rootwrap.xml:23(td) ./doc/common/tables/nova-rootwrap.xml:23(td)
-msgid "List of directories to load filter definitions from (separated by ','). These directories MUST all be only writeable by root !"
+#: ./doc/common/tables/cinder-zones.xml:23(td)
+msgid "(BoolOpt) Ensure that the new volumes are the same AZ as snapshot or source volume"
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml:26(td) ./doc/common/tables/neutron-rootwrap.xml:26(td) ./doc/common/tables/nova-rootwrap.xml:26(td)
-msgid "exec_dirs = /sbin,/usr/sbin,/bin,/usr/bin"
+#: ./doc/common/tables/cinder-scality.xml:8(caption)
+msgid "Description of configuration options for scality"
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml:27(td) ./doc/common/tables/neutron-rootwrap.xml:27(td) ./doc/common/tables/nova-rootwrap.xml:27(td)
-msgid "List of directories to search executables in, in case filters do not explicitely specify a full path (separated by ',') If not specified, defaults to system PATH environment variable. These directories MUST all be only writeable by root !"
+#: ./doc/common/tables/cinder-scality.xml:30(td)
+msgid "scality_sofs_volume_dir = cinder/volumes"
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml:31(td) ./doc/common/tables/neutron-rootwrap.xml:31(td) ./doc/common/tables/nova-rootwrap.xml:31(td)
-msgid "Enable logging to syslog Default value is False"
+#: ./doc/common/tables/cinder-scality.xml:31(td)
+msgid "(StrOpt) Path from Scality SOFS root to volume dir"
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml:34(td) ./doc/common/tables/neutron-rootwrap.xml:34(td) ./doc/common/tables/nova-rootwrap.xml:34(td)
-msgid "syslog_log_facility = syslog"
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:7(literal)
+msgid "[filter:tempauth]"
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml:35(td) ./doc/common/tables/neutron-rootwrap.xml:35(td)
-msgid "Which syslog facility to use. Valid values include auth, authpriv, syslog, local0, local1... Default value is 'syslog'"
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:18(td)
+msgid "use = egg:swift#tempauth"
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml:38(td) ./doc/common/tables/neutron-rootwrap.xml:38(td) ./doc/common/tables/nova-rootwrap.xml:38(td)
-msgid "syslog_log_level = ERROR"
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:21(td)
+msgid "set log_name = tempauth"
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml:39(td) ./doc/common/tables/neutron-rootwrap.xml:39(td) ./doc/common/tables/nova-rootwrap.xml:39(td)
-msgid "Which messages to log. INFO means log all usage ERROR means only log unsuccessful attempts"
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:36(td)
+msgid "reseller_prefix = AUTH"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-database.xml:22(td)
-msgid "database_connection = None"
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:36(td)
+msgid "The naming scope for the auth service. Swift"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-database.xml:23(td)
-msgid "(StrOpt) DEPRECATED - Database connection string."
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:39(td)
+msgid "auth_prefix = /auth/"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-database.xml:26(td)
-msgid "mysql_engine = InnoDB"
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:39(td)
+msgid "The HTTP request path prefix for the auth service. Swift itself reserves anything beginning with the letter `v`."
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-database.xml:27(td)
-msgid "(StrOpt) MySQL engine to use."
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:42(td)
+msgid "token_life = 86400"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-database.xml:30(td)
-msgid "sqlite_db = ceilometer.sqlite"
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:42(td)
+msgid "The number of seconds a token is valid."
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-database.xml:45(td)
-msgid "connection = sqlite:////usr/lib/python/site-packages/ceilometer/openstack/common/db/$sqlite_db"
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:45(td)
+msgid "allow_overrides = true"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-database.xml:89(td)
-msgid "time_to_live = -1"
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:48(td)
+msgid "storage_url_scheme = default"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-database.xml:90(td)
-msgid "(IntOpt) Number of seconds that samples are kept in the database for (&lt;= 0 means forever)."
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:48(td)
+msgid "Scheme to return with storage urls: http, https, or default (chooses based on what the server is running as) This can be useful with an SSL load balancer in front of a non-SSL server."
 msgstr ""
 
-#: ./doc/common/tables/cinder-nexenta_nfs.xml:8(caption)
-msgid "Description of configuration options for nexenta_nfs"
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:51(td)
+msgid "user_admin_admin = admin .admin .reseller_admin"
 msgstr ""
 
-#: ./doc/common/tables/cinder-nexenta_nfs.xml:22(td)
-msgid "nexenta_mount_point_base = $state_path/mnt"
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:54(td)
+msgid "user_test_tester = testing .admin"
 msgstr ""
 
-#: ./doc/common/tables/cinder-nexenta_nfs.xml:23(td)
-msgid "(StrOpt) Base dir containing mount points for nfs shares"
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:57(td)
+msgid "user_test2_tester2 = testing2 .admin"
 msgstr ""
 
-#: ./doc/common/tables/cinder-nexenta_nfs.xml:26(td)
-msgid "nexenta_nms_cache_volroot = True"
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:60(td)
+msgid "user_test_tester3 = testing3"
 msgstr ""
 
-#: ./doc/common/tables/cinder-nexenta_nfs.xml:27(td)
-msgid "(BoolOpt) If set True cache NexentaStor appliance volroot option value."
+#: ./doc/common/tables/neutron-agent.xml:8(caption)
+msgid "Description of configuration options for agent"
 msgstr ""
 
-#: ./doc/common/tables/cinder-nexenta_nfs.xml:30(td)
-msgid "nexenta_shares_config = /etc/cinder/nfs_shares"
+#: ./doc/common/tables/neutron-agent.xml:22(td)
+msgid "external_pids = $state_path/external/pids"
 msgstr ""
 
-#: ./doc/common/tables/cinder-nexenta_nfs.xml:34(td)
-msgid "nexenta_volume_compression = on"
+#: ./doc/common/tables/neutron-agent.xml:23(td)
+msgid "(StrOpt) Location to store child pid files"
 msgstr ""
 
-#: ./doc/common/tables/cinder-nexenta_nfs.xml:35(td)
-msgid "(StrOpt) Default compression value for new ZFS folders."
+#: ./doc/common/tables/neutron-agent.xml:26(td) ./doc/common/tables/nova-network.xml:170(td)
+msgid "network_device_mtu = None"
 msgstr ""
 
-#: ./doc/common/tables/heat-waitcondition_api.xml:8(caption)
-msgid "Description of configuration options for waitcondition_api"
+#: ./doc/common/tables/neutron-agent.xml:27(td)
+msgid "(IntOpt) MTU setting for device."
 msgstr ""
 
-#: ./doc/common/tables/heat-waitcondition_api.xml:22(td) ./doc/common/tables/heat-api.xml:30(td)
-msgid "heat_waitcondition_server_url ="
+#: ./doc/common/tables/cinder-emc.xml:8(caption)
+msgid "Description of configuration options for emc"
 msgstr ""
 
-#: ./doc/common/tables/heat-waitcondition_api.xml:23(td) ./doc/common/tables/heat-api.xml:31(td)
-msgid "(StrOpt) URL of the Heat waitcondition server."
+#: ./doc/common/tables/cinder-emc.xml:22(td)
+msgid "cinder_emc_config_file = /etc/cinder/cinder_emc_config.xml"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml:7(literal)
-msgid "[filter:bulk]"
+#: ./doc/common/tables/cinder-emc.xml:23(td)
+msgid "(StrOpt) use this file for cinder emc plugin config data"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml:18(td)
-msgid "use = egg:swift#bulk"
+#: ./doc/common/tables/cinder-emc.xml:26(td)
+msgid "max_luns_per_storage_group = 256"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml:21(td)
-msgid "max_containers_per_extraction = 10000"
+#: ./doc/common/tables/cinder-emc.xml:27(td)
+msgid "(IntOpt) Default max number of LUNs in a storage group"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml:24(td)
-msgid "max_failed_extractions = 1000"
+#: ./doc/common/tables/cinder-emc.xml:30(td)
+msgid "naviseccli_path ="
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml:27(td)
-msgid "max_deletes_per_request = 10000"
+#: ./doc/common/tables/cinder-emc.xml:31(td)
+msgid "(StrOpt) Naviseccli Path"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml:30(td)
-msgid "max_failed_deletes = 1000"
+#: ./doc/common/tables/cinder-emc.xml:34(td)
+msgid "storage_vnx_pool_name = None"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml:33(td)
-msgid "yield_frequency = 10"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml:36(td)
-msgid "delete_container_retry_count = 0"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_vlan.xml:8(caption)
-msgid "Description of configuration options for ml2_vlan"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_vlan.xml:19(th)
-msgid "[ml2_type_vlan]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_vlan.xml:23(td)
-msgid "(ListOpt) List of &lt;physical_network&gt;:&lt;vlan_min&gt;:&lt;vlan_max&gt; or &lt;physical_network&gt; specifying physical_network names usable for VLAN provider and tenant networks, as well as ranges of VLAN tags on each available for allocation to tenant networks."
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml:22(td)
-msgid "allow_instance_snapshots = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml:23(td)
-msgid "(BoolOpt) Permit instance snapshot operations."
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml:26(td)
-msgid "allow_migrate_to_same_host = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml:27(td)
-msgid "(BoolOpt) Allow migrate machine to the same host. Useful when testing in single-host environments."
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml:30(td)
-msgid "allow_resize_to_same_host = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml:31(td)
-msgid "(BoolOpt) Allow destination machine to match source for resize. Useful when testing in single-host environments."
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml:35(td)
-msgid "(IntOpt) Number of seconds between subsequent usage refreshes"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml:38(td)
-msgid "max_local_block_devices = 3"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml:39(td)
-msgid "(IntOpt) Maximum number of devices that will result in a local image being created on the hypervisor node. Setting this to 0 means nova will allow only boot from volume. A negative number means unlimited."
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml:42(td)
-msgid "osapi_compute_unique_server_name_scope ="
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml:43(td)
-msgid "(StrOpt) When set, compute API will consider duplicate hostnames invalid within the specified scope, regardless of case. Should be empty, \"project\" or \"global\"."
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml:47(td)
-msgid "(IntOpt) The maximum number of items returned in a single response from a collection resource"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml:51(td)
-msgid "(IntOpt) The maximum body size per each osapi request(bytes)"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml:54(td)
-msgid "password_length = 12"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml:55(td)
-msgid "(IntOpt) Length of generated instance admin passwords"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml:59(td) ./doc/common/tables/cinder-common.xml:139(td)
-msgid "(StrOpt) Rule checked when requested rule is not found"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml:63(td) ./doc/common/tables/cinder-common.xml:143(td)
-msgid "(StrOpt) JSON file representing policy"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml:67(td)
-msgid "(IntOpt) Number of seconds until a reservation expires"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml:70(td)
-msgid "resize_fs_using_block_device = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml:71(td)
-msgid "(BoolOpt) Attempt to resize the filesystem by accessing the image over a block device. This is done by the host and may not be necessary if the image contains a recent version of cloud-init. Possible mechanisms require the nbd driver (for qcow and raw), or loop (for raw)."
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml:74(td) ./doc/common/tables/cinder-common.xml:202(td)
-msgid "until_refresh = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml:75(td)
-msgid "(IntOpt) Count of reservations until usage is refreshed"
-msgstr ""
-
-#: ./doc/common/tables/keystone-amqp.xml:8(caption) ./doc/common/tables/glance-amqp.xml:8(caption) ./doc/common/tables/heat-amqp.xml:8(caption) ./doc/common/tables/ceilometer-amqp.xml:8(caption) ./doc/common/tables/trove-amqp.xml:8(caption)
-msgid "Description of configuration options for amqp"
-msgstr ""
-
-#: ./doc/common/tables/keystone-amqp.xml:34(td) ./doc/common/tables/heat-amqp.xml:38(td) ./doc/common/tables/ceilometer-exchange.xml:30(td) ./doc/common/tables/nova-compute.xml:58(td)
-msgid "default_publisher_id = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-amqp.xml:35(td) ./doc/common/tables/neutron-notifier.xml:27(td) ./doc/common/tables/heat-amqp.xml:39(td) ./doc/common/tables/trove-common.xml:51(td) ./doc/common/tables/ceilometer-exchange.xml:31(td) ./doc/common/tables/nova-compute.xml:59(td)
-msgid "(StrOpt) Default publisher_id for outgoing notifications"
-msgstr ""
-
-#: ./doc/common/tables/neutron-logging.xml:26(td) ./doc/common/tables/heat-logging.xml:22(td) ./doc/common/tables/trove-common.xml:34(td)
-msgid "default_log_levels = amqp=WARN, amqplib=WARN, boto=WARN, qpid=WARN, sqlalchemy=WARN, suds=INFO, iso8601=WARN"
-msgstr ""
-
-#: ./doc/common/tables/neutron-logging.xml:27(td) ./doc/common/tables/heat-logging.xml:23(td) ./doc/common/tables/nova-logging.xml:27(td) ./doc/common/tables/trove-common.xml:35(td)
-msgid "(ListOpt) list of logger=LEVEL pairs"
-msgstr ""
-
-#: ./doc/common/tables/neutron-logging.xml:86(td) ./doc/common/tables/neutron-nec.xml:58(td)
-msgid "use_ssl = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-logging.xml:87(td)
-msgid "(BoolOpt) Enable SSL on the API server"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_cassandra.xml:8(caption)
-msgid "Description of configuration options for db_cassandra"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_cassandra.xml:19(th)
-msgid "[cassandra]"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_cassandra.xml:26(td)
-msgid "mount_point = /var/lib/cassandra"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_cassandra.xml:30(td)
-msgid "tcp_ports = 7000, 7001, 9042, 9160"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_cassandra.xml:35(td) ./doc/common/tables/trove-db_mysql.xml:39(td) ./doc/common/tables/trove-db_redis.xml:35(td) ./doc/common/tables/trove-db_couchbase.xml:35(td) ./doc/common/tables/trove-db_percona.xml:39(td)
-msgid "(ListOpt) List of UDP ports and/or port ranges to open in the security group (only applicable if trove_security_groups_support is True)"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_cassandra.xml:38(td)
-msgid "usage_timeout = 600"
-msgstr ""
-
-#: ./doc/common/tables/glance-rpc.xml:22(td)
-msgid "allowed_rpc_exception_modules = openstack.common.exception, glance.common.exception, exceptions"
-msgstr ""
-
-#: ./doc/common/tables/glance-rpc.xml:23(td) ./doc/common/tables/trove-rpc.xml:23(td)
-msgid "(ListOpt) Modules of exceptions that are permitted to be recreatedupon receiving exception data from an rpc call."
-msgstr ""
-
-#: ./doc/common/tables/nova-authentication.xml:8(caption)
-msgid "Description of configuration options for authentication"
-msgstr ""
-
-#: ./doc/common/tables/nova-authentication.xml:22(td) ./doc/common/tables/glance-registry.xml:38(td) ./doc/common/tables/cinder-auth.xml:22(td)
-msgid "auth_strategy = noauth"
-msgstr ""
-
-#: ./doc/common/tables/nova-authentication.xml:23(td) ./doc/common/tables/ceilometer-auth.xml:23(td)
-msgid "(StrOpt) The strategy to use for auth: noauth or keystone."
+#: ./doc/common/tables/cinder-emc.xml:35(td)
+msgid "(StrOpt) ISCSI pool name"
 msgstr ""
 
 #: ./doc/common/tables/cinder-vmware.xml:26(td)
@@ -27067,96 +26943,1636 @@ msgstr ""
 msgid "(StrOpt) Optional VIM service WSDL Location e.g http://&lt;server&gt;/vimService.wsdl. Optional over-ride to default location for bug work-arounds."
 msgstr ""
 
-#: ./doc/common/tables/glance-sheepdog.xml:8(caption)
-msgid "Description of configuration options for sheepdog"
+#: ./doc/common/tables/neutron-ml2_flat.xml:8(caption)
+msgid "Description of configuration options for ml2_flat"
 msgstr ""
 
-#: ./doc/common/tables/glance-sheepdog.xml:22(td)
-msgid "sheepdog_store_address = 127.0.0.1"
+#: ./doc/common/tables/neutron-ml2_flat.xml:19(th)
+msgid "[ml2_type_flat]"
 msgstr ""
 
-#: ./doc/common/tables/glance-sheepdog.xml:23(td)
-msgid "(StrOpt) IP address of sheep daemon."
+#: ./doc/common/tables/neutron-ml2_flat.xml:22(td)
+msgid "flat_networks ="
 msgstr ""
 
-#: ./doc/common/tables/glance-sheepdog.xml:26(td)
-msgid "sheepdog_store_chunk_size = 64"
+#: ./doc/common/tables/neutron-ml2_flat.xml:23(td)
+msgid "(ListOpt) List of physical_network names with which flat networks can be created. Use * to allow flat networks with arbitrary physical_network names."
 msgstr ""
 
-#: ./doc/common/tables/glance-sheepdog.xml:27(td)
-msgid "(IntOpt) Images will be chunked into objects of this size (in megabytes). For best performance, this should be a power of two."
+#: ./doc/common/tables/heat-metadata_api.xml:8(caption)
+msgid "Description of configuration options for metadata_api"
 msgstr ""
 
-#: ./doc/common/tables/glance-sheepdog.xml:30(td)
-msgid "sheepdog_store_port = 7000"
+#: ./doc/common/tables/heat-metadata_api.xml:22(td) ./doc/common/tables/heat-api.xml:22(td)
+msgid "heat_metadata_server_url ="
 msgstr ""
 
-#: ./doc/common/tables/glance-sheepdog.xml:31(td)
-msgid "(IntOpt) Port of sheep daemon."
+#: ./doc/common/tables/heat-metadata_api.xml:23(td) ./doc/common/tables/heat-api.xml:23(td)
+msgid "(StrOpt) URL of the Heat metadata server."
 msgstr ""
 
-#: ./doc/common/tables/keystone-notification.xml:23(td)
-msgid "(StrOpt) onready allows you to send a notification when the process is ready to serve For example, to have it notify using systemd, one could set shell command: \"onready = systemd-notify --ready\" or a module with notify() method: \"onready = keystone.common.systemd\"."
+#: ./doc/common/tables/nova-upgrade_levels.xml:8(caption)
+msgid "Description of configuration options for upgrade_levels"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml:8(caption)
-msgid "Description of configuration options for hyperv_agent"
+#: ./doc/common/tables/nova-upgrade_levels.xml:22(td)
+msgid "scheduler = nova.cells.scheduler.CellsScheduler"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml:22(td)
-msgid "enable_metrics_collection = False"
+#: ./doc/common/tables/nova-upgrade_levels.xml:23(td)
+msgid "(StrOpt) Cells scheduler to use"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml:23(td)
-msgid "(BoolOpt) Enables metrics collections for switch ports by using Hyper-V's metric APIs. Collected data can by retrieved by other apps and services, e.g.: Ceilometer. Requires Hyper-V / Windows Server 2012 and above"
+#: ./doc/common/tables/nova-upgrade_levels.xml:26(th) ./doc/common/tables/nova-rpc_all.xml:212(th) ./doc/common/tables/nova-rpc.xml:76(th)
+msgid "[upgrade_levels]"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml:26(td)
-msgid "local_network_vswitch = private"
+#: ./doc/common/tables/nova-upgrade_levels.xml:29(td)
+msgid "cells = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml:27(td)
-msgid "(StrOpt) Private vswitch name used for local networks"
+#: ./doc/common/tables/nova-upgrade_levels.xml:30(td)
+msgid "(StrOpt) Set a version cap for messages sent to local cells services"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml:30(td)
-msgid "metrics_max_retries = 100"
+#: ./doc/common/tables/nova-upgrade_levels.xml:33(td)
+msgid "cert = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml:31(td)
-msgid "(IntOpt) Specifies the maximum number of retries to enable Hyper-V's port metrics collection. The agent will try to enable the feature once every polling_interval period for at most metrics_max_retries or until it succeedes."
+#: ./doc/common/tables/nova-upgrade_levels.xml:34(td)
+msgid "(StrOpt) Set a version cap for messages sent to cert services"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml:34(td)
-msgid "physical_network_vswitch_mappings ="
+#: ./doc/common/tables/nova-upgrade_levels.xml:37(td)
+msgid "compute = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml:35(td)
-msgid "(ListOpt) List of &lt;physical_network&gt;:&lt;vswitch&gt; where the physical networks can be expressed with wildcards, e.g.: .\"*:external\""
+#: ./doc/common/tables/nova-upgrade_levels.xml:38(td)
+msgid "(StrOpt) Set a version cap for messages sent to compute services. If you plan to do a live upgrade from havana to icehouse, you should set this option to \"icehouse-compat\" before beginning the live upgrade procedure."
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml:38(td) ./doc/common/tables/neutron-sdnve.xml:85(td)
-msgid "polling_interval = 2"
+#: ./doc/common/tables/nova-upgrade_levels.xml:41(td)
+msgid "conductor = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml:39(td)
-msgid "(IntOpt) The number of seconds the agent will wait between polling for local device changes."
+#: ./doc/common/tables/nova-upgrade_levels.xml:42(td)
+msgid "(StrOpt) Set a version cap for messages sent to conductor services"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml:42(th)
-msgid "[HYPERV]"
+#: ./doc/common/tables/nova-upgrade_levels.xml:45(td)
+msgid "console = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml:50(td)
-msgid "(StrOpt) Network type for tenant networks (local, flat, vlan or none)"
+#: ./doc/common/tables/nova-upgrade_levels.xml:46(td)
+msgid "(StrOpt) Set a version cap for messages sent to console services"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml:56(td) ./doc/common/tables/nova-hyperv.xml:30(td)
-msgid "force_hyperv_utils_v1 = False"
+#: ./doc/common/tables/nova-upgrade_levels.xml:49(td)
+msgid "consoleauth = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml:57(td) ./doc/common/tables/nova-hyperv.xml:31(td)
-msgid "(BoolOpt) Force V1 WMI utility classes"
+#: ./doc/common/tables/nova-upgrade_levels.xml:50(td)
+msgid "(StrOpt) Set a version cap for messages sent to consoleauth services"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml:53(td)
+msgid "intercell = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml:54(td)
+msgid "(StrOpt) Set a version cap for messages sent between cells services"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml:57(td)
+msgid "network = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml:58(td)
+msgid "(StrOpt) Set a version cap for messages sent to network services"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml:61(td)
+msgid "scheduler = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml:62(td)
+msgid "(StrOpt) Set a version cap for messages sent to scheduler services"
+msgstr ""
+
+#: ./doc/common/tables/neutron-kombu.xml:8(caption) ./doc/common/tables/nova-kombu.xml:8(caption)
+msgid "Description of configuration options for kombu"
+msgstr ""
+
+#: ./doc/common/tables/neutron-kombu.xml:35(td) ./doc/common/tables/ceilometer-rabbitmq.xml:39(td)
+msgid "(StrOpt) If SSL is enabled, the SSL version to use. Valid values are TLSv1, SSLv23 and SSLv3. SSLv2 might be available on some distributions."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:8(caption)
+msgid "Description of configuration options for netapp_cdot_iscsi"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:38(td) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:38(td)
+msgid "netapp_size_multiplier = 1.2"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:39(td) ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:39(td)
+msgid "(FloatOpt) The quantity to be multiplied by the requested volume size to ensure enough space is available on the virtual storage server (Vserver) to fulfill the volume creation request."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:54(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:58(td)
+msgid "netapp_vserver = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml:55(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:59(td)
+msgid "(StrOpt) This option specifies the virtual storage server (Vserver) name on the storage cluster on which provisioning of block storage volumes should occur. If using the NFS storage protocol, this parameter is mandatory for storage service catalog support (utilized by Cinder volume type extra_specs support). If this option is specified, the exports belonging to the Vserver will only be used for provisioning in the future. Block storage volumes on exports not belonging to the Vserver specified by this option will continue to function normally."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ofa.xml:8(caption)
+msgid "Description of configuration options for ml2_ofa"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ofa.xml:22(td)
+msgid "ofp_listen_host ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ofa.xml:23(td)
+msgid "(StrOpt) openflow listen host"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ofa.xml:26(td)
+msgid "ofp_ssl_listen_port = 6633"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ofa.xml:27(td)
+msgid "(IntOpt) openflow ssl listen port"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ofa.xml:30(td)
+msgid "ofp_tcp_listen_port = 6633"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ofa.xml:31(td)
+msgid "(IntOpt) openflow tcp listen port"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ofa.xml:37(td)
+msgid "get_datapath_retry_times = 60"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ofa.xml:38(td)
+msgid "(IntOpt) Number of seconds to retry acquiring an Open vSwitch datapath"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:22(td)
+msgid "admin_role = admin"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:23(td)
+msgid "(StrOpt) Role used to identify an authenticated user as administrator."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:26(td)
+msgid "allow_anonymous_access = False"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:27(td)
+msgid "(BoolOpt) Allow unauthenticated users to access the API with read-only privileges. This only applies when using ContextMiddleware."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:30(td)
+msgid "default_publisher_id = image.localhost"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:31(td)
+msgid "(StrOpt) Default publisher_id for outgoing notifications."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:34(td)
+msgid "default_store = file"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:35(td)
+msgid "(StrOpt) Default scheme to use to store image data. The scheme must be registered by one of the stores defined by the 'known_stores' config option."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:38(td) ./doc/common/tables/ceilometer-api.xml:22(td) ./doc/common/tables/cinder-api.xml:34(td)
+msgid "enable_v1_api = True"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:39(td)
+msgid "(BoolOpt) Deploy the v1 OpenStack Images API."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:42(td)
+msgid "enable_v1_registry = True"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:43(td)
+msgid "(BoolOpt) Deploy the v1 OpenStack Registry API."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:46(td) ./doc/common/tables/cinder-api.xml:38(td)
+msgid "enable_v2_api = True"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:47(td)
+msgid "(BoolOpt) Deploy the v2 OpenStack Images API."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:50(td)
+msgid "enable_v2_registry = True"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:51(td)
+msgid "(BoolOpt) Deploy the v2 OpenStack Registry API."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:54(td)
+msgid "image_size_cap = 1099511627776"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:55(td)
+msgid "(IntOpt) Maximum size of image a user can upload in bytes. Defaults to 1099511627776 bytes (1 TB)."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:58(td)
+msgid "known_stores = glance.store.filesystem.Store, glance.store.http.Store"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:59(td)
+msgid "(ListOpt) List of which store classes and store class locations are currently known to glance at startup."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:62(td)
+msgid "location_strategy = location_order"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:63(td)
+msgid "(StrOpt) This value sets what strategy will be used to determine the image location order. Currently two strategies are packaged with Glance 'location_order' and 'store_type'."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:66(td)
+msgid "owner_is_tenant = True"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:67(td)
+msgid "(BoolOpt) When true, this option sets the owner of an image to be the tenant. Otherwise, the owner of the image will be the authenticated user issuing the request."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:70(td)
+msgid "send_identity_headers = False"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:71(td)
+msgid "(BoolOpt) Whether to pass through headers containing user and tenant information when making requests to the registry. This allows the registry to use the context middleware without the keystoneclients' auth_token middleware, removing calls to the keystone auth service. It is recommended that when using this option, secure communication between glance api and glance registry is ensured by means other than auth_token middleware."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:74(td)
+msgid "show_multiple_locations = False"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:75(td)
+msgid "(BoolOpt) Whether to include the backend image locations in image properties. Revealing storage location can be a security risk, so use this setting with caution! The overrides show_image_direct_url."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:78(td)
+msgid "use_user_token = True"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:79(td)
+msgid "(BoolOpt) Whether to pass through the user token when making requests to the registry."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:82(th)
+msgid "[store_type_location_strategy]"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:85(td)
+msgid "store_type_preference ="
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml:86(td)
+msgid "(ListOpt) The store names to use to get store preference order. The name must be registered by one of the stores defined by the 'known_stores' config option. This option will be applied when you using 'store_type' option as image location strategy defined by the 'location_strategy' config option."
+msgstr ""
+
+#: ./doc/common/tables/heat-waitcondition_api.xml:8(caption)
+msgid "Description of configuration options for waitcondition_api"
+msgstr ""
+
+#: ./doc/common/tables/heat-waitcondition_api.xml:22(td) ./doc/common/tables/heat-api.xml:30(td)
+msgid "heat_waitcondition_server_url ="
+msgstr ""
+
+#: ./doc/common/tables/heat-waitcondition_api.xml:23(td) ./doc/common/tables/heat-api.xml:31(td)
+msgid "(StrOpt) URL of the Heat waitcondition server."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:7(literal)
+msgid "[filter:gatekeeper]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:18(td)
+msgid "use = egg:swift#gatekeeper"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:21(td)
+msgid "set log_name = gatekeeper"
+msgstr ""
+
+#: ./doc/common/tables/swift-rsyncd-container.xml:7(literal)
+msgid "[container]"
+msgstr ""
+
+#: ./doc/common/tables/swift-rsyncd-container.xml:7(literal) ./doc/common/tables/swift-rsyncd-account.xml:7(literal) ./doc/common/tables/swift-rsyncd-object.xml:7(literal)
+msgid "rsyncd.conf-sample"
+msgstr ""
+
+#: ./doc/common/tables/swift-rsyncd-container.xml:18(td)
+msgid "max connections = 4"
+msgstr ""
+
+#: ./doc/common/tables/swift-rsyncd-container.xml:21(td) ./doc/common/tables/swift-rsyncd-account.xml:21(td) ./doc/common/tables/swift-rsyncd-object.xml:21(td)
+msgid "path = /srv/node"
+msgstr ""
+
+#: ./doc/common/tables/swift-rsyncd-container.xml:24(td) ./doc/common/tables/swift-rsyncd-account.xml:24(td) ./doc/common/tables/swift-rsyncd-object.xml:24(td)
+msgid "read only = false"
+msgstr ""
+
+#: ./doc/common/tables/swift-rsyncd-container.xml:27(td)
+msgid "lock file = /var/lock/container.lock"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml:8(caption)
+msgid "Description of configuration options for storwize"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml:22(td)
+msgid "storwize_svc_connection_protocol = iSCSI"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml:23(td)
+msgid "(StrOpt) Connection protocol (iSCSI/FC)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml:26(td)
+msgid "storwize_svc_flashcopy_timeout = 120"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml:27(td)
+msgid "(IntOpt) Maximum number of seconds to wait for FlashCopy to be prepared. Maximum value is 600 seconds (10 minutes)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml:30(td)
+msgid "storwize_svc_iscsi_chap_enabled = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml:31(td)
+msgid "(BoolOpt) Configure CHAP authentication for iSCSI connections (Default: Enabled)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml:34(td)
+msgid "storwize_svc_multihostmap_enabled = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml:35(td)
+msgid "(BoolOpt) Allows vdisk to multi host mapping"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml:38(td)
+msgid "storwize_svc_multipath_enabled = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml:39(td)
+msgid "(BoolOpt) Connect with multipath (FC only; iSCSI multipath is controlled by Nova)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml:42(td)
+msgid "storwize_svc_vol_autoexpand = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml:43(td)
+msgid "(BoolOpt) Storage system autoexpand parameter for volumes (True/False)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml:46(td)
+msgid "storwize_svc_vol_compression = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml:47(td)
+msgid "(BoolOpt) Storage system compression option for volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml:50(td)
+msgid "storwize_svc_vol_easytier = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml:51(td)
+msgid "(BoolOpt) Enable Easy Tier for volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml:54(td)
+msgid "storwize_svc_vol_grainsize = 256"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml:55(td)
+msgid "(IntOpt) Storage system grain size parameter for volumes (32/64/128/256)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml:58(td)
+msgid "storwize_svc_vol_iogrp = 0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml:59(td)
+msgid "(IntOpt) The I/O group in which to allocate volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml:62(td)
+msgid "storwize_svc_vol_rsize = 2"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml:63(td)
+msgid "(IntOpt) Storage system space-efficiency parameter for volumes (percentage)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml:66(td)
+msgid "storwize_svc_vol_warning = 0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml:67(td)
+msgid "(IntOpt) Storage system threshold for volume capacity warnings (percentage)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml:70(td)
+msgid "storwize_svc_volpool_name = volpool"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml:71(td)
+msgid "(StrOpt) Storage system storage pool for volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml:8(caption)
+msgid "Description of configuration options for hplefthand"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml:22(td)
+msgid "hplefthand_api_url = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml:23(td)
+msgid "(StrOpt) HP LeftHand WSAPI Server Url like https://&lt;LeftHand ip&gt;:8081/lhos"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml:26(td)
+msgid "hplefthand_clustername = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml:27(td)
+msgid "(StrOpt) HP LeftHand cluster name"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml:30(td)
+msgid "hplefthand_debug = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml:31(td)
+msgid "(BoolOpt) Enable HTTP debugging to LeftHand"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml:34(td)
+msgid "hplefthand_iscsi_chap_enabled = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml:35(td)
+msgid "(BoolOpt) Configure CHAP authentication for iSCSI connections (Default: Disabled)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml:38(td)
+msgid "hplefthand_password = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml:39(td)
+msgid "(StrOpt) HP LeftHand Super user password"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml:42(td)
+msgid "hplefthand_username = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml:43(td)
+msgid "(StrOpt) HP LeftHand Super user username"
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml:8(caption) ./doc/common/tables/nova-s3.xml:8(caption)
+msgid "Description of configuration options for s3"
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml:22(td)
+msgid "s3_store_access_key = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml:23(td)
+msgid "(StrOpt) The S3 query token access key."
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml:26(td)
+msgid "s3_store_bucket = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml:27(td)
+msgid "(StrOpt) The S3 bucket to be used to store the Glance data."
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml:30(td)
+msgid "s3_store_bucket_url_format = subdomain"
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml:31(td)
+msgid "(StrOpt) The S3 calling format used to determine the bucket. Either subdomain or path can be used."
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml:34(td)
+msgid "s3_store_create_bucket_on_put = False"
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml:35(td)
+msgid "(BoolOpt) A boolean to determine if the S3 bucket should be created on upload if it does not exist or if an error should be returned to the user."
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml:38(td)
+msgid "s3_store_host = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml:39(td)
+msgid "(StrOpt) The host where the S3 server is listening."
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml:42(td)
+msgid "s3_store_object_buffer_dir = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml:43(td)
+msgid "(StrOpt) The local directory where uploads will be staged before they are transferred into S3."
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml:46(td)
+msgid "s3_store_secret_key = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml:47(td)
+msgid "(StrOpt) The S3 query token secret key."
+msgstr ""
+
+#: ./doc/common/tables/nova-rootwrap.xml:22(td)
+msgid "filters_path = /etc/nova/rootwrap.d,/usr/share/nova/rootwrap"
+msgstr ""
+
+#: ./doc/common/tables/nova-rootwrap.xml:35(td)
+msgid "Which syslog facility to use. Valid values include auth, authpriv, syslog, user0, user1... Default value is 'syslog'"
+msgstr ""
+
+#: ./doc/common/tables/heat-loadbalancer.xml:8(caption)
+msgid "Description of configuration options for loadbalancer"
+msgstr ""
+
+#: ./doc/common/tables/heat-loadbalancer.xml:22(td)
+msgid "loadbalancer_template = None"
+msgstr ""
+
+#: ./doc/common/tables/heat-loadbalancer.xml:23(td)
+msgid "(StrOpt) Custom template for the built-in loadbalancer nested stack."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml:23(td)
+msgid "(BoolOpt) Deploy the deprecated v1 API."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml:27(td)
+msgid "(IntOpt) The maximum body size per request, in bytes"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml:30(td)
+msgid "pipeline_cfg_file = pipeline.yaml"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml:31(td)
+msgid "(StrOpt) Configuration file for pipeline definition."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml:42(td)
+msgid "reserved_metadata_length = 256"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml:43(td)
+msgid "(IntOpt) Limit on length of reserved metadata values."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml:46(td)
+msgid "reserved_metadata_namespace = metering."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml:47(td)
+msgid "(ListOpt) List of metadata prefixes reserved for metering use."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml:50(th)
+msgid "[api]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml:53(td) ./doc/common/tables/trove-rpc.xml:26(td)
+msgid "host = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml:54(td)
+msgid "(StrOpt) The listen IP for the ceilometer API server."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml:57(td)
+msgid "port = 8777"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml:58(td)
+msgid "(IntOpt) The port for the ceilometer API server."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml:8(caption)
+msgid "Description of configuration options for exchange"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml:22(td)
+msgid "cinder_control_exchange = cinder"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml:23(td)
+msgid "(StrOpt) Exchange name for Cinder notifications."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml:34(td)
+msgid "glance_control_exchange = glance"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml:35(td)
+msgid "(StrOpt) Exchange name for Glance notifications."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml:38(td)
+msgid "heat_control_exchange = heat"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml:39(td)
+msgid "(StrOpt) Exchange name for Heat notifications"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml:42(td)
+msgid "http_control_exchanges = ['nova', 'glance', 'neutron', 'cinder']"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml:43(td)
+msgid "(MultiStrOpt) Exchanges name to listen for notifications."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml:46(td)
+msgid "neutron_control_exchange = neutron"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml:47(td)
+msgid "(StrOpt) Exchange name for Neutron notifications."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml:50(td)
+msgid "nova_control_exchange = nova"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml:51(td)
+msgid "(StrOpt) Exchange name for Nova notifications."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml:54(td)
+msgid "sample_source = openstack"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml:55(td)
+msgid "(StrOpt) Source for samples emitted on this instance."
+msgstr ""
+
+#: ./doc/common/tables/cinder-lvm.xml:8(caption)
+msgid "Description of configuration options for lvm"
+msgstr ""
+
+#: ./doc/common/tables/cinder-lvm.xml:22(td)
+msgid "lvm_mirrors = 0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-lvm.xml:23(td)
+msgid "(IntOpt) If set, create lvms with multiple mirrors. Note that this requires lvm_mirrors + 2 pvs with available space"
+msgstr ""
+
+#: ./doc/common/tables/cinder-lvm.xml:26(td)
+msgid "lvm_type = default"
+msgstr ""
+
+#: ./doc/common/tables/cinder-lvm.xml:27(td)
+msgid "(StrOpt) Type of LVM volumes to deploy; (default or thin)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-lvm.xml:30(td)
+msgid "volume_group = cinder-volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-lvm.xml:31(td)
+msgid "(StrOpt) Name for the VG that will contain exported volumes"
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml:8(caption)
+msgid "Description of configuration options for dns"
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml:22(td)
+msgid "dns_account_id ="
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml:26(td)
+msgid "dns_auth_url ="
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml:30(td)
+msgid "dns_domain_id ="
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml:34(td)
+msgid "dns_domain_name ="
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml:38(td)
+msgid "dns_driver = trove.dns.driver.DnsDriver"
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml:42(td)
+msgid "dns_endpoint_url = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml:46(td)
+msgid "dns_hostname ="
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml:50(td)
+msgid "dns_instance_entry_factory = trove.dns.driver.DnsInstanceEntryFactory"
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml:54(td)
+msgid "dns_management_base_url ="
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml:58(td)
+msgid "dns_passkey ="
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml:62(td)
+msgid "dns_region ="
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml:66(td)
+msgid "dns_service_type ="
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml:70(td)
+msgid "dns_time_out = 120"
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml:74(td)
+msgid "dns_ttl = 300"
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml:78(td)
+msgid "dns_username ="
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml:82(td)
+msgid "trove_dns_support = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml:34(td)
+msgid "cells_config = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml:35(td)
+msgid "(StrOpt) Configuration file from which to read cells configuration. If given, overrides reading cells from the database."
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml:38(td)
+msgid "driver = nova.cells.rpc_driver.CellsRPCDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml:39(td)
+msgid "(StrOpt) Cells communication driver to use"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml:46(td)
+msgid "instance_update_num_instances = 1"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml:47(td)
+msgid "(IntOpt) Number of instances to update per periodic task run"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml:50(td)
+msgid "instance_updated_at_threshold = 3600"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml:51(td)
+msgid "(IntOpt) Number of seconds after an instance was updated or deleted to continue to update cells"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml:58(td)
+msgid "max_hop_count = 10"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml:59(td)
+msgid "(IntOpt) Maximum number of hops for cells routing."
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml:66(td)
+msgid "mute_weight_multiplier = -10.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml:67(td)
+msgid "(FloatOpt) Multiplier used to weigh mute children. (The value should be negative.)"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml:70(td)
+msgid "mute_weight_value = 1000.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml:71(td)
+msgid "(FloatOpt) Weight value assigned to mute children. (The value should be positive.)"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml:78(td)
+msgid "offset_weight_multiplier = 1.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml:79(td)
+msgid "(FloatOpt) Multiplier used to weigh offset weigher."
+msgstr ""
+
+#: ./doc/common/tables/trove-volume.xml:8(caption)
+msgid "Description of configuration options for volume"
+msgstr ""
+
+#: ./doc/common/tables/trove-volume.xml:22(td)
+msgid "block_device_mapping = vdb"
+msgstr ""
+
+#: ./doc/common/tables/trove-volume.xml:26(td)
+msgid "cinder_url = http://localhost:8776/v2"
+msgstr ""
+
+#: ./doc/common/tables/trove-volume.xml:30(td)
+msgid "device_path = /dev/vdb"
+msgstr ""
+
+#: ./doc/common/tables/trove-volume.xml:34(td)
+msgid "trove_volume_support = True"
+msgstr ""
+
+#: ./doc/common/tables/trove-volume.xml:35(td)
+msgid "(BoolOpt) Whether to provision a cinder volume for datadir."
+msgstr ""
+
+#: ./doc/common/tables/trove-volume.xml:38(td)
+msgid "volume_format_timeout = 120"
+msgstr ""
+
+#: ./doc/common/tables/trove-volume.xml:42(td)
+msgid "volume_fstype = ext3"
+msgstr ""
+
+#: ./doc/common/tables/trove-volume.xml:46(td)
+msgid "volume_time_out = 60"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:8(caption)
+msgid "Description of configuration options for quotas"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:22(td)
+msgid "max_routes = 30"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:23(td)
+msgid "(IntOpt) Maximum number of routes"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:26(th)
+msgid "[QUOTAS]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:29(td)
+msgid "default_quota = -1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:30(td)
+msgid "(IntOpt) Default number of resource allowed per tenant. A negative value means unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:33(td)
+msgid "quota_driver = neutron.db.quota_db.DbQuotaDriver"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:34(td) ./doc/common/tables/nova-quota.xml:35(td)
+msgid "(StrOpt) Default driver to use for quota checks"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:37(td)
+msgid "quota_firewall = 1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:38(td)
+msgid "(IntOpt) Number of firewalls allowed per tenant. A negative value means unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:41(td)
+msgid "quota_firewall_policy = 1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:42(td)
+msgid "(IntOpt) Number of firewall policies allowed per tenant. A negative value means unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:45(td)
+msgid "quota_firewall_rule = -1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:46(td)
+msgid "(IntOpt) Number of firewall rules allowed per tenant. A negative value means unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:49(td)
+msgid "quota_floatingip = 50"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:50(td)
+msgid "(IntOpt) Number of floating IPs allowed per tenant. A negative value means unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:53(td)
+msgid "quota_health_monitor = -1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:54(td)
+msgid "(IntOpt) Number of health monitors allowed per tenant. A negative value means unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:57(td)
+msgid "quota_items = network, subnet, port"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:58(td)
+msgid "(ListOpt) Resource name(s) that are supported in quota features"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:61(td)
+msgid "quota_member = -1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:62(td)
+msgid "(IntOpt) Number of pool members allowed per tenant. A negative value means unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:65(td)
+msgid "quota_network = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:66(td)
+msgid "(IntOpt) Number of networks allowed per tenant.A negative value means unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:69(td)
+msgid "quota_network_gateway = 5"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:70(td)
+msgid "(IntOpt) Number of network gateways allowed per tenant, -1 for unlimited"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:73(td)
+msgid "quota_packet_filter = 100"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:74(td)
+msgid "(IntOpt) Number of packet_filters allowed per tenant, -1 for unlimited"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:77(td)
+msgid "quota_pool = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:78(td)
+msgid "(IntOpt) Number of pools allowed per tenant. A negative value means unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:81(td)
+msgid "quota_port = 50"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:82(td)
+msgid "(IntOpt) Number of ports allowed per tenant. A negative value means unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:85(td)
+msgid "quota_router = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:86(td)
+msgid "(IntOpt) Number of routers allowed per tenant. A negative value means unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:89(td)
+msgid "quota_security_group = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:90(td)
+msgid "(IntOpt) Number of security groups allowed per tenant. A negative value means unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:93(td)
+msgid "quota_security_group_rule = 100"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:94(td)
+msgid "(IntOpt) Number of security rules allowed per tenant. A negative value means unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:97(td)
+msgid "quota_subnet = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:98(td)
+msgid "(IntOpt) Number of subnets allowed per tenant, A negative value means unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:101(td)
+msgid "quota_vip = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml:102(td)
+msgid "(IntOpt) Number of vips allowed per tenant. A negative value means unlimited."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml:8(caption)
+msgid "Description of configuration options for storage_nfs"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml:23(td)
+msgid "(StrOpt) Mount options passed to the nfs client. See section of the nfs man page for details."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml:27(td)
+msgid "(StrOpt) Base dir containing mount points for nfs shares."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml:30(td)
+msgid "nfs_oversub_ratio = 1.0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml:31(td)
+msgid "(FloatOpt) This will compare the allocated to available space on the volume destination. If the ratio exceeds this number, the destination will no longer be valid."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml:34(td)
+msgid "nfs_shares_config = /etc/cinder/nfs_shares"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml:35(td) ./doc/common/tables/cinder-nexenta_nfs.xml:31(td)
+msgid "(StrOpt) File with the list of available nfs shares"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml:38(td)
+msgid "nfs_sparsed_volumes = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml:39(td) ./doc/common/tables/cinder-storage_glusterfs.xml:35(td) ./doc/common/tables/cinder-nexenta_iscsi.xml:63(td)
+msgid "(BoolOpt) Create volumes as sparsed files which take no space.If set to False volume is created as regular file.In such case volume creation takes a lot of time."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml:42(td)
+msgid "nfs_used_ratio = 0.95"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml:43(td)
+msgid "(FloatOpt) Percent of ACTUAL usage of the underlying volume before no new volumes can be allocated to the volume destination."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:26(td)
+msgid "heat_stack_user_role = heat_stack_user"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:27(td)
+msgid "(StrOpt) Keystone role for heat template-defined users."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:34(td) ./doc/common/tables/heat-cloudwatch_api.xml:22(td)
+msgid "heat_watch_server_url ="
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:35(td) ./doc/common/tables/heat-cloudwatch_api.xml:23(td)
+msgid "(StrOpt) URL of the Heat CloudWatch server."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:38(td)
+msgid "max_json_body_size = 1048576"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:39(td)
+msgid "(IntOpt) Maximum raw byte size of JSON request body. Should be larger than max_template_size."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:50(td)
+msgid "secure_proxy_ssl_header = X-Forwarded-Proto"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:51(td)
+msgid "(StrOpt) The HTTP Header that will be used to determine which the original request protocol scheme was, even if it was removed by an SSL terminator proxy."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:54(td)
+msgid "stack_action_timeout = 3600"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:55(td)
+msgid "(IntOpt) Timeout in seconds for stack action (ie. create or update)."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:58(td)
+msgid "stack_domain_admin = None"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:59(td)
+msgid "(StrOpt) Keystone username, a user with roles sufficient to manage users and projects in the stack_user_domain."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:62(td)
+msgid "stack_domain_admin_password = None"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:63(td)
+msgid "(StrOpt) Keystone password for stack_domain_admin user."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:66(td)
+msgid "stack_user_domain = None"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:67(td)
+msgid "(StrOpt) Keystone domain ID which contains heat template-defined users."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:70(td)
+msgid "trusts_delegated_roles = heat_stack_owner"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:71(td)
+msgid "(ListOpt) Subset of trustor roles to be delegated to heat."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:74(th)
+msgid "[auth_password]"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:77(td) ./doc/common/tables/heat-api.xml:88(td)
+msgid "allowed_auth_uris ="
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:78(td) ./doc/common/tables/heat-api.xml:89(td)
+msgid "(ListOpt) Allowed keystone endpoints for auth_uri when multi_cloud is enabled. At least one endpoint needs to be specified."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:81(td) ./doc/common/tables/heat-api.xml:96(td)
+msgid "multi_cloud = False"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:82(td) ./doc/common/tables/heat-api.xml:97(td)
+msgid "(BoolOpt) Allow orchestration of multiple clouds."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:85(th)
+msgid "[ec2authtoken]"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:93(td)
+msgid "(StrOpt) Authentication Endpoint URI."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:100(th)
+msgid "[heat_api]"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:111(td)
+msgid "bind_port = 8004"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:135(td)
+msgid "(StrOpt) The API paste config file to use."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:138(td) ./doc/common/tables/glance-paste.xml:26(td)
+msgid "flavor = None"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml:139(td)
+msgid "(StrOpt) The flavor to use."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:7(literal)
+msgid "[filter:tempurl]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:18(td)
+msgid "use = egg:swift#tempurl"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:21(td)
+msgid "methods = GET HEAD PUT"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:21(td)
+msgid "HTTP methods allowed with Temporary URLs"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:24(td)
+msgid "incoming_remove_headers = x-timestamp"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:24(td)
+msgid "Headers to remove from incoming requests. Simply a whitespace delimited list of header names and names can optionally end with '*' to indicate a prefix match."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:28(td)
+msgid "incoming_allow_headers ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:28(td)
+msgid "Headers allowed as exceptions to incoming_remove_headers. Simply a whitespace delimited list of header names and names can optionally end with '*' to indicate a prefix match."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:33(td)
+msgid "outgoing_remove_headers = x-object-meta-*"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:33(td)
+msgid "Headers to remove from outgoing responses. Simply a whitespace delimited list of header names and names can optionally end with '*' to indicate a prefix match."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:38(td)
+msgid "outgoing_allow_headers = x-object-meta-public-*"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml:38(td)
+msgid "Headers allowed as exceptions to outgoing_allow_headers. Simply a whitespace delimited list of header names and names can optionally end with '*' to indicate a prefix match."
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_ceilometer.xml:8(caption)
+msgid "Description of configuration options for clients_ceilometer"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_ceilometer.xml:19(th)
+msgid "[clients_ceilometer]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml:8(caption)
+msgid "Description of configuration options for ryu"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml:22(td)
+msgid "openflow_rest_api = 127.0.0.1:8080"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml:23(td)
+msgid "(StrOpt) OpenFlow REST API location"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml:26(td)
+msgid "ovsdb_interface = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml:27(td)
+msgid "(StrOpt) OVSDB interface to connect to"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml:30(td)
+msgid "ovsdb_ip = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml:31(td)
+msgid "(StrOpt) OVSDB IP to connect to"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml:34(td)
+msgid "ovsdb_port = 6634"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml:35(td)
+msgid "(IntOpt) OVSDB port to connect to"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml:38(td)
+msgid "tunnel_interface = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml:39(td)
+msgid "(StrOpt) Tunnel interface to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml:42(td)
+msgid "tunnel_ip = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml:43(td)
+msgid "(StrOpt) Tunnel IP to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml:46(td)
+msgid "tunnel_key_max = 16777215"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml:47(td)
+msgid "(IntOpt) Maximum tunnel ID to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml:50(td)
+msgid "tunnel_key_min = 1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml:51(td)
+msgid "(IntOpt) Minimum tunnel ID to use"
+msgstr ""
+
+#: ./doc/common/tables/swift-rsyncd-account.xml:7(literal)
+msgid "[account]"
+msgstr ""
+
+#: ./doc/common/tables/swift-rsyncd-account.xml:18(td)
+msgid "max connections = 2"
+msgstr ""
+
+#: ./doc/common/tables/swift-rsyncd-account.xml:27(td)
+msgid "lock file = /var/lock/account.lock"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metering_agent.xml:8(caption)
+msgid "Description of configuration options for metering_agent"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metering_agent.xml:22(td)
+msgid "driver = neutron.services.metering.drivers.noop.noop_driver.NoopMeteringDriver"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metering_agent.xml:23(td)
+msgid "(StrOpt) Metering driver"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metering_agent.xml:26(td)
+msgid "measure_interval = 30"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metering_agent.xml:27(td)
+msgid "(IntOpt) Interval between two metering measures"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metering_agent.xml:33(td)
+msgid "report_interval = 30"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metering_agent.xml:34(td)
+msgid "(FloatOpt) Seconds between nodes reporting state to server; should be less than agent_down_time, best if it is half or less than agent_down_time."
+msgstr ""
+
+#: ./doc/common/tables/neutron-zeromq.xml:38(td)
+msgid "rpc_zmq_matchmaker = neutron.openstack.common.rpc.matchmaker.MatchMakerLocalhost"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_glusterfs.xml:8(caption)
+msgid "Description of configuration options for storage_glusterfs"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_glusterfs.xml:23(td)
+msgid "(StrOpt) Base dir containing mount points for gluster shares."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_glusterfs.xml:26(td)
+msgid "glusterfs_qcow2_volumes = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_glusterfs.xml:27(td)
+msgid "(BoolOpt) Create volumes as QCOW2 files rather than raw files."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_glusterfs.xml:30(td)
+msgid "glusterfs_shares_config = /etc/cinder/glusterfs_shares"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_glusterfs.xml:31(td)
+msgid "(StrOpt) File with the list of available gluster shares"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_glusterfs.xml:34(td)
+msgid "glusterfs_sparsed_volumes = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:22(td)
+msgid "compute_api_class = cinder.compute.nova.API"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:23(td)
+msgid "(StrOpt) The full class name of the compute API class to use"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:30(td)
+msgid "default_availability_zone = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:31(td)
+msgid "(StrOpt) default availability zone to use when creating a new volume. If this is not set then we use the value from the storage_availability_zone option as the default availability_zone for new volumes."
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:34(td)
+msgid "default_log_levels = amqp=WARN, amqplib=WARN, boto=WARN, qpid=WARN, sqlalchemy=WARN, suds=INFO, oslo.messaging=INFO, iso8601=WARN, requests.packages.urllib3.connectionpool=WARN"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:38(td)
+msgid "default_volume_type = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:39(td)
+msgid "(StrOpt) default volume type to use"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:46(td) ./doc/common/tables/nova-api.xml:26(td)
+msgid "enable_new_services = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:47(td) ./doc/common/tables/nova-api.xml:27(td)
+msgid "(BoolOpt) Services to be added to the available pool on create"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:54(td) ./doc/common/tables/nova-logging.xml:34(td)
+msgid "fatal_exception_format_errors = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:55(td)
+msgid "(BoolOpt) make exception message format errors fatal"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:59(td)
+msgid "(StrOpt) Name of this node. This can be an opaque identifier. It is not necessarily a hostname, FQDN, or IP address."
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:62(td)
+msgid "iet_conf = /etc/iet/ietd.conf"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:63(td)
+msgid "(StrOpt) IET configuration file"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:66(td)
+msgid "lio_initiator_iqns ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:67(td)
+msgid "(StrOpt) Comma-separated list of initiator IQNs allowed to connect to the iSCSI target. (From Nova compute nodes.)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:71(td)
+msgid "(StrOpt) Directory to use for lock files. Default to a temp directory"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:111(td)
+msgid "(BoolOpt) Enable monkey patching"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:114(td)
+msgid "monkey_patch_modules ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:119(td)
+msgid "(StrOpt) ip address of this host"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:122(td)
+msgid "no_snapshot_gb_quota = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:123(td)
+msgid "(BoolOpt) Whether snapshots count against GigaByte quota"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:126(td)
+msgid "num_shell_tries = 3"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:127(td)
+msgid "(IntOpt) number of times to attempt to run flakey shell commands"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:131(td)
+msgid "(IntOpt) range of seconds to randomly delay when starting the periodic task scheduler to reduce stampeding. (Disable by setting to 0)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:135(td)
+msgid "(IntOpt) seconds between running periodic tasks"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:147(td)
+msgid "(IntOpt) seconds between nodes reporting state to datastore"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:150(td)
+msgid "reserved_percentage = 0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:151(td)
+msgid "(IntOpt) The percentage of backend capacity is reserved"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:154(td)
+msgid "rootwrap_config = /etc/cinder/rootwrap.conf"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:163(td)
+msgid "(IntOpt) maximum time since last check-in for up service"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:166(td)
+msgid "sqlite_db = cinder.sqlite"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:167(td) ./doc/common/tables/heat-database.xml:27(td)
+msgid "(StrOpt) the filename to use with sqlite"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:171(td) ./doc/common/tables/heat-database.xml:31(td)
+msgid "(BoolOpt) If true, use synchronous mode for sqlite"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:174(td) ./doc/common/tables/neutron-ssl.xml:22(td) ./doc/common/tables/nova-wsgi.xml:26(td)
+msgid "ssl_ca_file = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:178(td) ./doc/common/tables/neutron-ssl.xml:26(td) ./doc/common/tables/nova-wsgi.xml:30(td)
+msgid "ssl_cert_file = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:182(td) ./doc/common/tables/neutron-ssl.xml:30(td) ./doc/common/tables/nova-wsgi.xml:34(td)
+msgid "ssl_key_file = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:186(td)
+msgid "state_path = /var/lib/cinder"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:187(td)
+msgid "(StrOpt) Top-level directory for maintaining cinder's state"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:190(td)
+msgid "storage_availability_zone = nova"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:191(td)
+msgid "(StrOpt) availability zone of this node"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:203(td)
+msgid "(IntOpt) count of reservations until usage is refreshed"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:206(td) ./doc/common/tables/nova-api.xml:94(td)
+msgid "use_forwarded_for = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:207(td) ./doc/common/tables/nova-api.xml:95(td)
+msgid "(BoolOpt) Treat X-Forwarded-For as the canonical remote address. Only enable this if you have a sanitizing proxy."
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:230(td) ./doc/common/tables/heat-database.xml:54(td)
+msgid "(IntOpt) timeout before idle sql connections are reaped"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:234(td) ./doc/common/tables/heat-database.xml:78(td)
+msgid "(IntOpt) interval between retries of opening a sql connection"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:237(td)
+msgid "use_tpool = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml:238(td)
+msgid "(BoolOpt) Enable the experimental use of thread pooling for all DB API calls"
+msgstr ""
+
+#: ./doc/common/tables/glance-swift.xml:8(caption) ./doc/common/tables/ceilometer-swift.xml:8(caption) ./doc/common/tables/trove-swift.xml:8(caption)
+msgid "Description of configuration options for swift"
 msgstr ""
 
 #: ./doc/common/tables/glance-swift.xml:22(td)
@@ -27295,168 +28711,3112 @@ msgstr ""
 msgid "(StrOpt) The user to authenticate against the Swift authentication service."
 msgstr ""
 
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml:21(td)
-msgid "bind_port = 6002"
+#: ./doc/common/tables/trove-quota.xml:22(td)
+msgid "max_accepted_volume_size = 5"
+msgstr ""
+
+#: ./doc/common/tables/trove-quota.xml:23(td)
+msgid "(IntOpt) Default maximum volume size for an instance."
+msgstr ""
+
+#: ./doc/common/tables/trove-quota.xml:26(td)
+msgid "max_backups_per_user = 50"
+msgstr ""
+
+#: ./doc/common/tables/trove-quota.xml:27(td)
+msgid "(IntOpt) Default maximum number of backups created by a tenant."
+msgstr ""
+
+#: ./doc/common/tables/trove-quota.xml:30(td)
+msgid "max_instances_per_user = 5"
+msgstr ""
+
+#: ./doc/common/tables/trove-quota.xml:31(td)
+msgid "(IntOpt) Default maximum number of instances per tenant."
+msgstr ""
+
+#: ./doc/common/tables/trove-quota.xml:34(td)
+msgid "max_volumes_per_user = 20"
+msgstr ""
+
+#: ./doc/common/tables/trove-quota.xml:35(td)
+msgid "(IntOpt) Default maximum volume capacity (in GB) spanning across all trove volumes per tenant"
+msgstr ""
+
+#: ./doc/common/tables/trove-quota.xml:38(td)
+msgid "quota_driver = trove.quota.quota.DbQuotaDriver"
+msgstr ""
+
+#: ./doc/common/tables/trove-quota.xml:39(td)
+msgid "(StrOpt) Default driver to use for quota checks."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml:8(caption)
+msgid "Description of configuration options for alarm"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml:19(th)
+msgid "[alarm]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml:22(td)
+msgid "evaluation_interval = 60"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml:23(td)
+msgid "(IntOpt) Period of evaluation cycle, should be &gt;= than configured pipeline interval for collection of underlying metrics."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml:26(td)
+msgid "evaluation_service = ceilometer.alarm.service.SingletonAlarmService"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml:27(td)
+msgid "(StrOpt) Class to launch as alarm evaluation service."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml:30(td)
+msgid "notifier_rpc_topic = alarm_notifier"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml:31(td)
+msgid "(StrOpt) The topic that ceilometer uses for alarm notifier messages."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml:34(td)
+msgid "partition_rpc_topic = alarm_partition_coordination"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml:35(td)
+msgid "(StrOpt) The topic that ceilometer uses for alarm partition coordination messages."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml:38(td)
+msgid "record_history = True"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml:39(td)
+msgid "(BoolOpt) Record alarm change events."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml:42(td)
+msgid "rest_notifier_certificate_file ="
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml:43(td)
+msgid "(StrOpt) SSL Client certificate for REST notifier."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml:46(td)
+msgid "rest_notifier_certificate_key ="
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml:47(td)
+msgid "(StrOpt) SSL Client private key for REST notifier."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml:50(td)
+msgid "rest_notifier_ssl_verify = True"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml:51(td)
+msgid "(BoolOpt) Whether to verify the SSL Server certificate when calling alarm action."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml:8(caption)
+msgid "Description of configuration options for events"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml:19(th)
+msgid "[event]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml:22(td)
+msgid "definitions_cfg_file = event_definitions.yaml"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml:23(td)
+msgid "(StrOpt) Configuration file for event definitions."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml:26(td)
+msgid "drop_unmatched_notifications = False"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml:27(td)
+msgid "(BoolOpt) Drop notifications if no event definition matches. (Otherwise, we convert them with just the default traits)"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml:30(th)
+msgid "[notification]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml:33(td)
+msgid "ack_on_event_error = True"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml:34(td)
+msgid "(BoolOpt) Acknowledge message when event persistence fails."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml:37(td)
+msgid "store_events = False"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml:38(td)
+msgid "(BoolOpt) Save event details."
+msgstr ""
+
+#: ./doc/common/tables/cinder-xiv.xml:8(caption)
+msgid "Description of configuration options for xiv"
+msgstr ""
+
+#: ./doc/common/tables/cinder-xiv.xml:22(td)
+msgid "xiv_chap = disabled"
+msgstr ""
+
+#: ./doc/common/tables/cinder-xiv.xml:23(td)
+msgid "(StrOpt) CHAP authentication mode, effective only for iscsi (disabled|enabled)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-xiv.xml:26(td)
+msgid "xiv_ds8k_connection_type = iscsi"
+msgstr ""
+
+#: ./doc/common/tables/cinder-xiv.xml:27(td)
+msgid "(StrOpt) Connection type to the IBM Storage Array (fibre_channel|iscsi)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-xiv.xml:30(td)
+msgid "xiv_ds8k_proxy = xiv_ds8k_openstack.nova_proxy.XIVDS8KNovaProxy"
+msgstr ""
+
+#: ./doc/common/tables/cinder-xiv.xml:31(td)
+msgid "(StrOpt) Proxy driver that connects to the IBM Storage Array"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml:7(literal)
+msgid "[filter:name_check]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml:18(td)
+msgid "use = egg:swift#name_check"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml:21(td)
+msgid "forbidden_chars = '\"`&lt;&gt;"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml:21(td)
+msgid "Characters that are not allowed in a name"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml:24(td)
+msgid "maximum_length = 255"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml:24(td)
+msgid "Maximum length of a name"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml:27(td)
+msgid "forbidden_regexp = /\\./|/\\.\\./|/\\.$|/\\.\\.$"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml:27(td)
+msgid "Substrings to forbid, using regular expression syntax"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:8(caption)
+msgid "Description of configuration options for ml2_bigswitch"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:19(th) ./doc/common/tables/neutron-bigswitch.xml:19(th)
+msgid "[NOVA]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:22(td) ./doc/common/tables/neutron-bigswitch.xml:22(td)
+msgid "node_override_vif_802.1qbg ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:23(td) ./doc/common/tables/neutron-bigswitch.xml:23(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to 802.1qbg"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:26(td) ./doc/common/tables/neutron-bigswitch.xml:26(td)
+msgid "node_override_vif_802.1qbh ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:27(td) ./doc/common/tables/neutron-bigswitch.xml:27(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to 802.1qbh"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:30(td) ./doc/common/tables/neutron-bigswitch.xml:30(td)
+msgid "node_override_vif_binding_failed ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:31(td) ./doc/common/tables/neutron-bigswitch.xml:31(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to binding_failed"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:34(td) ./doc/common/tables/neutron-bigswitch.xml:34(td)
+msgid "node_override_vif_bridge ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:35(td) ./doc/common/tables/neutron-bigswitch.xml:35(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to bridge"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:38(td) ./doc/common/tables/neutron-bigswitch.xml:38(td)
+msgid "node_override_vif_hostdev ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:39(td) ./doc/common/tables/neutron-bigswitch.xml:39(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to hostdev"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:42(td) ./doc/common/tables/neutron-bigswitch.xml:42(td)
+msgid "node_override_vif_hyperv ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:43(td) ./doc/common/tables/neutron-bigswitch.xml:43(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to hyperv"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:46(td) ./doc/common/tables/neutron-bigswitch.xml:46(td)
+msgid "node_override_vif_ivs ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:47(td) ./doc/common/tables/neutron-bigswitch.xml:47(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to ivs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:50(td) ./doc/common/tables/neutron-bigswitch.xml:50(td)
+msgid "node_override_vif_midonet ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:51(td) ./doc/common/tables/neutron-bigswitch.xml:51(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to midonet"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:54(td) ./doc/common/tables/neutron-bigswitch.xml:54(td)
+msgid "node_override_vif_mlnx_direct ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:55(td) ./doc/common/tables/neutron-bigswitch.xml:55(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to mlnx_direct"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:58(td) ./doc/common/tables/neutron-bigswitch.xml:58(td)
+msgid "node_override_vif_other ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:59(td) ./doc/common/tables/neutron-bigswitch.xml:59(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to other"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:62(td) ./doc/common/tables/neutron-bigswitch.xml:62(td)
+msgid "node_override_vif_ovs ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:63(td) ./doc/common/tables/neutron-bigswitch.xml:63(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to ovs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:66(td) ./doc/common/tables/neutron-bigswitch.xml:66(td)
+msgid "node_override_vif_unbound ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:67(td) ./doc/common/tables/neutron-bigswitch.xml:67(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to unbound"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:70(td) ./doc/common/tables/neutron-bigswitch.xml:70(td)
+msgid "vif_type = ovs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:71(td) ./doc/common/tables/neutron-bigswitch.xml:71(td)
+msgid "(StrOpt) Virtual interface type to configure on Nova compute nodes"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:74(td) ./doc/common/tables/neutron-bigswitch.xml:74(td)
+msgid "vif_types = unbound, binding_failed, ovs, ivs, bridge, 802.1qbg, 802.1qbh, hyperv, midonet, mlnx_direct, hostdev, other"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:75(td) ./doc/common/tables/neutron-bigswitch.xml:75(td)
+msgid "(ListOpt) List of allowed vif_type values."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:78(th) ./doc/common/tables/neutron-nuage.xml:19(th) ./doc/common/tables/neutron-bigswitch.xml:78(th)
+msgid "[RESTPROXY]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:81(td) ./doc/common/tables/neutron-bigswitch.xml:81(td)
+msgid "add_meta_server_route = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:82(td) ./doc/common/tables/neutron-bigswitch.xml:82(td)
+msgid "(BoolOpt) Flag to decide if a route to the metadata server should be injected into the VM"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:85(td) ./doc/common/tables/neutron-bigswitch.xml:85(td)
+msgid "auto_sync_on_failure = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:86(td) ./doc/common/tables/neutron-bigswitch.xml:86(td)
+msgid "(BoolOpt) If neutron fails to create a resource because the backend controller doesn't know of a dependency, the plugin automatically triggers a full data synchronization to the controller."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:89(td) ./doc/common/tables/neutron-bigswitch.xml:89(td)
+msgid "cache_connections = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:90(td) ./doc/common/tables/neutron-bigswitch.xml:90(td)
+msgid "(BoolOpt) Re-use HTTP/HTTPS connections to the controller."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:93(td) ./doc/common/tables/neutron-bigswitch.xml:93(td)
+msgid "consistency_interval = 60"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:94(td) ./doc/common/tables/neutron-bigswitch.xml:94(td)
+msgid "(IntOpt) Time between verifications that the backend controller database is consistent with Neutron"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:97(td) ./doc/common/tables/neutron-bigswitch.xml:97(td)
+msgid "neutron_id = neutron-oslo"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:98(td) ./doc/common/tables/neutron-bigswitch.xml:98(td)
+msgid "(StrOpt) User defined identifier for this Neutron deployment"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:101(td) ./doc/common/tables/neutron-bigswitch.xml:101(td)
+msgid "no_ssl_validation = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:102(td) ./doc/common/tables/neutron-bigswitch.xml:102(td)
+msgid "(BoolOpt) Disables SSL certificate validation for controllers"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:105(td) ./doc/common/tables/neutron-bigswitch.xml:105(td)
+msgid "server_auth = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:106(td) ./doc/common/tables/neutron-bigswitch.xml:106(td)
+msgid "(StrOpt) The username and password for authenticating against the Big Switch or Floodlight controller."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:109(td) ./doc/common/tables/neutron-bigswitch.xml:109(td)
+msgid "server_ssl = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:110(td) ./doc/common/tables/neutron-bigswitch.xml:110(td)
+msgid "(BoolOpt) If True, Use SSL when connecting to the Big Switch or Floodlight controller."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:113(td) ./doc/common/tables/neutron-bigswitch.xml:113(td)
+msgid "server_timeout = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:114(td) ./doc/common/tables/neutron-bigswitch.xml:114(td)
+msgid "(IntOpt) Maximum number of seconds to wait for proxy request to connect and complete."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:117(td) ./doc/common/tables/neutron-bigswitch.xml:117(td)
+msgid "servers = localhost:8800"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:118(td) ./doc/common/tables/neutron-bigswitch.xml:118(td)
+msgid "(ListOpt) A comma separated list of Big Switch or Floodlight servers and port numbers. The plugin proxies the requests to the Big Switch/Floodlight server, which performs the networking configuration. Only oneserver is needed per deployment, but you may wish todeploy multiple servers to support failover."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:121(td) ./doc/common/tables/neutron-bigswitch.xml:121(td)
+msgid "ssl_cert_directory = /etc/neutron/plugins/bigswitch/ssl"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:122(td) ./doc/common/tables/neutron-bigswitch.xml:122(td)
+msgid "(StrOpt) Directory containing ca_certs and host_certs certificate directories."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:125(td) ./doc/common/tables/neutron-bigswitch.xml:125(td)
+msgid "ssl_sticky = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:126(td) ./doc/common/tables/neutron-bigswitch.xml:126(td)
+msgid "(BoolOpt) Trust and store the first certificate received for each controller address and use it to validate future connections to that address."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:129(td) ./doc/common/tables/neutron-bigswitch.xml:129(td)
+msgid "sync_data = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:130(td) ./doc/common/tables/neutron-bigswitch.xml:130(td)
+msgid "(BoolOpt) Sync data on connect"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:133(td) ./doc/common/tables/neutron-bigswitch.xml:133(td)
+msgid "thread_pool_size = 4"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:134(td) ./doc/common/tables/neutron-bigswitch.xml:134(td)
+msgid "(IntOpt) Maximum number of threads to spawn to handle large volumes of port creations."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:137(th) ./doc/common/tables/neutron-bigswitch.xml:137(th)
+msgid "[RESTPROXYAGENT]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:141(td) ./doc/common/tables/neutron-bigswitch.xml:141(td)
+msgid "(StrOpt) Name of integration bridge on compute nodes used for security group insertion."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:144(td) ./doc/common/tables/neutron-bigswitch.xml:144(td)
+msgid "polling_interval = 5"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:145(td) ./doc/common/tables/neutron-bigswitch.xml:145(td)
+msgid "(IntOpt) Seconds between agent checks for port changes"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:148(td) ./doc/common/tables/neutron-bigswitch.xml:148(td)
+msgid "virtual_switch_type = ovs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:149(td) ./doc/common/tables/neutron-bigswitch.xml:149(td)
+msgid "(StrOpt) Virtual switch type."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:152(th) ./doc/common/tables/neutron-bigswitch.xml:152(th)
+msgid "[ROUTER]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:155(td) ./doc/common/tables/neutron-bigswitch.xml:155(td)
+msgid "max_router_rules = 200"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:156(td) ./doc/common/tables/neutron-bigswitch.xml:156(td)
+msgid "(IntOpt) Maximum number of router rules"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:159(td) ./doc/common/tables/neutron-bigswitch.xml:159(td)
+msgid "tenant_default_router_rule = ['*:any:any:permit']"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml:160(td) ./doc/common/tables/neutron-bigswitch.xml:160(td)
+msgid "(MultiStrOpt) The default router rules installed in new tenant routers. Repeat the config option for each rule. Format is &lt;tenant&gt;:&lt;source&gt;:&lt;destination&gt;:&lt;action&gt; Use an * to specify default for all tenants."
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml:8(caption)
+msgid "Description of configuration options for glance"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml:22(td) ./doc/common/tables/cinder-images.xml:22(td)
+msgid "allowed_direct_url_schemes ="
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml:23(td)
+msgid "(ListOpt) A list of url scheme that can be downloaded directly via the direct_url. Currently supported schemes: [file]."
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml:26(td) ./doc/common/tables/cinder-images.xml:26(td)
+msgid "glance_api_insecure = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml:27(td) ./doc/common/tables/cinder-images.xml:27(td)
+msgid "(BoolOpt) Allow to perform insecure SSL (https) requests to glance"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml:30(td) ./doc/common/tables/cinder-images.xml:30(td)
+msgid "glance_api_servers = $glance_host:$glance_port"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml:31(td)
+msgid "(ListOpt) A list of the glance api servers available to nova. Prefix with https:// for ssl-based glance api servers. ([hostname|ip]:port)"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml:34(td) ./doc/common/tables/cinder-images.xml:42(td)
+msgid "glance_host = $my_ip"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml:35(td)
+msgid "(StrOpt) Default glance hostname or IP address"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml:38(td) ./doc/common/tables/cinder-images.xml:46(td)
+msgid "glance_num_retries = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml:39(td)
+msgid "(IntOpt) Number of retries when downloading an image from glance"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml:42(td) ./doc/common/tables/cinder-images.xml:50(td)
+msgid "glance_port = 9292"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml:43(td)
+msgid "(IntOpt) Default glance port"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml:46(td)
+msgid "glance_protocol = http"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml:47(td)
+msgid "(StrOpt) Default protocol to use when connecting to glance. Set to https for SSL."
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml:50(td)
+msgid "osapi_glance_link_prefix = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml:51(td)
+msgid "(StrOpt) Base URL that will be presented to users in links to glance resources"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml:54(th)
+msgid "[image_file_url]"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml:57(td)
+msgid "filesystems ="
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml:58(td)
+msgid "(ListOpt) List of file systems that are configured in this file in the image_file_url:&lt;list entry name&gt; sections"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml:22(td)
+msgid "buckets_path = $state_path/buckets"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml:23(td)
+msgid "(StrOpt) Path to S3 buckets"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml:26(td)
+msgid "image_decryption_dir = /tmp"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml:27(td)
+msgid "(StrOpt) Parent directory for tempdir used for image decryption"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml:30(td)
+msgid "s3_access_key = notchecked"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml:31(td)
+msgid "(StrOpt) Access key to use for S3 server for images"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml:34(td)
+msgid "s3_affix_tenant = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml:35(td)
+msgid "(BoolOpt) Whether to affix the tenant id to the access key when downloading from S3"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml:38(td)
+msgid "s3_host = $my_ip"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml:39(td)
+msgid "(StrOpt) Hostname or IP for OpenStack to use when accessing the S3 api"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml:42(td)
+msgid "s3_listen = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml:43(td)
+msgid "(StrOpt) IP address for S3 API to listen"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml:46(td)
+msgid "s3_listen_port = 3333"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml:47(td)
+msgid "(IntOpt) Port for S3 API to listen"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml:50(td)
+msgid "s3_port = 3333"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml:51(td)
+msgid "(IntOpt) Port used when accessing the S3 api"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml:54(td)
+msgid "s3_secret_key = notchecked"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml:55(td)
+msgid "(StrOpt) Secret key to use for S3 server for images"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml:58(td)
+msgid "s3_use_ssl = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml:59(td)
+msgid "(BoolOpt) Whether to use SSL when talking to S3"
+msgstr ""
+
+#: ./doc/common/tables/nova-pci.xml:8(caption)
+msgid "Description of configuration options for pci"
+msgstr ""
+
+#: ./doc/common/tables/nova-pci.xml:22(td)
+msgid "pci_alias = []"
+msgstr ""
+
+#: ./doc/common/tables/nova-pci.xml:23(td)
+msgid "(MultiStrOpt) An alias for a PCI passthrough device requirement. This allows users to specify the alias in the extra_spec for a flavor, without needing to repeat all the PCI property requirements. For example: pci_alias = { \"name\": \"QuicAssist\", \"product_id\": \"0443\", \"vendor_id\": \"8086\", \"device_type\": \"ACCEL\" } defines an alias for the Intel QuickAssist card. (multi valued)"
+msgstr ""
+
+#: ./doc/common/tables/nova-pci.xml:26(td)
+msgid "pci_passthrough_whitelist = []"
+msgstr ""
+
+#: ./doc/common/tables/nova-pci.xml:27(td)
+msgid "(MultiStrOpt) White list of PCI devices available to VMs. For example: pci_passthrough_whitelist = [{\"vendor_id\": \"8086\", \"product_id\": \"0443\"}]"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_cinder.xml:8(caption)
+msgid "Description of configuration options for clients_cinder"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_cinder.xml:19(th)
+msgid "[clients_cinder]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:7(literal)
+msgid "[filter:ratelimit]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:18(td)
+msgid "use = egg:swift#ratelimit"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:21(td)
+msgid "set log_name = ratelimit"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:36(td)
+msgid "clock_accuracy = 1000"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:36(td)
+msgid "Represents how accurate the proxy servers' system clocks are with each other. 1000 means that all the proxies' clock are accurate to each other within 1 millisecond. No ratelimit should be higher than the clock accuracy."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:39(td)
+msgid "max_sleep_time_seconds = 60"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:39(td)
+msgid "App will immediately return a 498 response if the necessary sleep time ever exceeds the given max_sleep_time_seconds."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:42(td)
+msgid "log_sleep_time_seconds = 0"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:42(td)
+msgid "To allow visibility into rate limiting set this value &gt; 0 and all sleeps greater than the number will be logged."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:45(td)
+msgid "rate_buffer_seconds = 5"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:45(td)
+msgid "Number of seconds the rate counter can drop and be allowed to catch up (at a faster than listed rate). A larger number will result in larger spikes in rate but better average accuracy."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:48(td)
+msgid "account_ratelimit = 0"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:48(td)
+msgid "If set, will limit PUT and DELETE requests to /account_name/container_name. Number is in requests per second."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:51(td)
+msgid "account_whitelist = a,b"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:51(td)
+msgid "Comma separated lists of account names that will not be rate limited."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:54(td)
+msgid "account_blacklist = c,d"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:54(td)
+msgid "Comma separated lists of account names that will not be allowed. Returns a 497 response. r: for containers of size x, limit requests per second to r. Will limit PUT, DELETE, and POST requests to /a/c/o. container_listing_ratelimit_x = r: for containers of size x, limit listing requests per second to r. Will limit GET requests to /a/c."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:57(td)
+msgid "with container_limit_x = r"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:60(td)
+msgid "container_ratelimit_0 = 100"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:63(td)
+msgid "container_ratelimit_10 = 50"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:66(td)
+msgid "container_ratelimit_50 = 20"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:69(td)
+msgid "container_listing_ratelimit_0 = 100"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:72(td)
+msgid "container_listing_ratelimit_10 = 50"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml:75(td)
+msgid "container_listing_ratelimit_50 = 20"
+msgstr ""
+
+#: ./doc/common/tables/keystone-revoke.xml:8(caption)
+msgid "Description of configuration options for revoke"
+msgstr ""
+
+#: ./doc/common/tables/keystone-revoke.xml:19(th)
+msgid "[revoke]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-revoke.xml:23(td)
+msgid "(BoolOpt) Toggle for revocation event cacheing. This has no effect unless global caching is enabled."
+msgstr ""
+
+#: ./doc/common/tables/keystone-revoke.xml:26(td)
+msgid "driver = keystone.contrib.revoke.backends.kvs.Revoke"
+msgstr ""
+
+#: ./doc/common/tables/keystone-revoke.xml:27(td)
+msgid "(StrOpt) An implementation of the backend for persisting revocation events."
+msgstr ""
+
+#: ./doc/common/tables/keystone-revoke.xml:30(td)
+msgid "expiration_buffer = 1800"
+msgstr ""
+
+#: ./doc/common/tables/keystone-revoke.xml:31(td)
+msgid "(IntOpt) This value (calculated in seconds) is added to token expiration before a revocation event may be removed from the backend."
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:23(td)
+msgid "(StrOpt) File name for the paste.deploy config for cinder-api"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:26(td)
+msgid "api_rate_limit = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:27(td)
+msgid "(BoolOpt) whether to rate limit the api"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:35(td)
+msgid "(BoolOpt) Deploy v1 of the Cinder API."
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:39(td)
+msgid "(BoolOpt) Deploy v2 of the Cinder API."
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:42(td)
+msgid "extra_capabilities = {}"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:43(td)
+msgid "(StrOpt) User defined capabilities, a JSON formatted string specifying key/value pairs."
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:51(td)
+msgid "(IntOpt) the maximum number of items returned in a single response from a collection resource"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:55(td)
+msgid "(IntOpt) Max size for body of a request"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:58(td)
+msgid "osapi_volume_base_URL = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:59(td)
+msgid "(StrOpt) Base URL that will be presented to users in links to the OpenStack Volume API"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:62(td)
+msgid "osapi_volume_ext_list ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:63(td)
+msgid "(ListOpt) Specify list of extensions to load when using osapi_volume_extension option with cinder.api.contrib.select_extensions"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:66(td)
+msgid "osapi_volume_extension = ['cinder.api.contrib.standard_extensions']"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:67(td)
+msgid "(MultiStrOpt) osapi volume extension to load"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:70(td)
+msgid "osapi_volume_listen = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:71(td)
+msgid "(StrOpt) IP address for OpenStack Volume API to listen"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:74(td)
+msgid "osapi_volume_listen_port = 8776"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:75(td)
+msgid "(IntOpt) port for os volume api to listen"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:78(td)
+msgid "osapi_volume_workers = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:79(td)
+msgid "(IntOpt) Number of workers for OpenStack Volume API service"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:82(td)
+msgid "transfer_api_class = cinder.transfer.api.API"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:83(td)
+msgid "(StrOpt) The full class name of the volume transfer API class"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:86(td)
+msgid "volume_api_class = cinder.volume.api.API"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:90(td)
+msgid "volume_name_template = volume-%s"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:91(td)
+msgid "(StrOpt) Template string to be used to generate volume names"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:94(td)
+msgid "volume_transfer_key_length = 16"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:95(td)
+msgid "(IntOpt) The number of characters in the autogenerated auth key."
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:98(td)
+msgid "volume_transfer_salt_length = 8"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml:99(td)
+msgid "(IntOpt) The number of characters in the salt."
+msgstr ""
+
+#: ./doc/common/tables/trove-db_couchbase.xml:8(caption)
+msgid "Description of configuration options for db_couchbase"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_couchbase.xml:19(th)
+msgid "[couchbase]"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_couchbase.xml:26(td)
+msgid "mount_point = /var/lib/couchbase"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_couchbase.xml:30(td)
+msgid "tcp_ports = 8091, 8092, 4369, 11209-11211, 21100-21199"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_trove.xml:8(caption)
+msgid "Description of configuration options for clients_trove"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_trove.xml:19(th)
+msgid "[clients_trove]"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml:7(literal)
+msgid "[account-replicator]"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml:18(td)
+msgid "log_name = account-replicator"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml:30(td) ./doc/common/tables/swift-object-server-object-replicator.xml:30(td) ./doc/common/tables/swift-container-server-container-replicator.xml:30(td)
+msgid "vm_test_mode = no"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml:30(td) ./doc/common/tables/swift-object-server-object-replicator.xml:30(td) ./doc/common/tables/swift-container-server-container-replicator.xml:30(td)
+msgid "Indicates that you are using a VM environment"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml:33(td) ./doc/common/tables/swift-container-server-container-replicator.xml:33(td)
+msgid "per_diff = 1000"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml:33(td) ./doc/common/tables/swift-container-server-container-replicator.xml:33(td)
+msgid "Limit number of items to get per diff"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml:36(td) ./doc/common/tables/swift-container-server-container-replicator.xml:36(td)
+msgid "max_diffs = 100"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml:36(td) ./doc/common/tables/swift-container-server-container-replicator.xml:36(td)
+msgid "Caps how long the replicator spends trying to sync a database per pass"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml:39(td) ./doc/common/tables/swift-container-server-container-replicator.xml:39(td)
+msgid "concurrency = 8"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml:42(td) ./doc/common/tables/swift-container-server-container-replicator.xml:42(td)
+msgid "interval = 30"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml:57(td) ./doc/common/tables/swift-object-server-object-replicator.xml:66(td) ./doc/common/tables/swift-container-server-container-replicator.xml:51(td)
+msgid "reclaim_age = 604800"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml:57(td) ./doc/common/tables/swift-object-server-object-replicator.xml:66(td) ./doc/common/tables/swift-container-server-container-replicator.xml:51(td)
+msgid "Time elapsed in seconds before an object can be reclaimed"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml:60(td) ./doc/common/tables/swift-object-server-object-replicator.xml:36(td) ./doc/common/tables/swift-container-server-container-replicator.xml:54(td)
+msgid "run_pause = 30"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml:60(td) ./doc/common/tables/swift-object-server-object-replicator.xml:36(td) ./doc/common/tables/swift-container-server-container-replicator.xml:54(td)
+msgid "Time in seconds to wait between replication passes"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml:8(caption)
+msgid "Description of configuration options for plumgrid"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml:19(th)
+msgid "[plumgriddirector]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml:22(td)
+msgid "director_server = localhost"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml:23(td)
+msgid "(StrOpt) PLUMgrid Director server to connect to"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml:26(td)
+msgid "director_server_port = 8080"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml:27(td)
+msgid "(StrOpt) PLUMgrid Director server port to connect to"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml:30(td) ./doc/common/tables/neutron-ml2_brocade.xml:30(td)
+msgid "password = password"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml:31(td)
+msgid "(StrOpt) PLUMgrid Director admin password"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml:34(td)
+msgid "servertimeout = 5"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml:35(td)
+msgid "(IntOpt) PLUMgrid Director server timeout"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml:38(td)
+msgid "username = username"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml:39(td)
+msgid "(StrOpt) PLUMgrid Director admin username"
+msgstr ""
+
+#: ./doc/common/tables/trove-heat.xml:8(caption)
+msgid "Description of configuration options for heat"
+msgstr ""
+
+#: ./doc/common/tables/trove-heat.xml:22(td)
+msgid "heat_time_out = 60"
+msgstr ""
+
+#: ./doc/common/tables/trove-heat.xml:26(td)
+msgid "heat_url = http://localhost:8004/v1"
+msgstr ""
+
+#: ./doc/common/tables/glance-sheepdog.xml:8(caption)
+msgid "Description of configuration options for sheepdog"
+msgstr ""
+
+#: ./doc/common/tables/glance-sheepdog.xml:22(td)
+msgid "sheepdog_store_address = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/glance-sheepdog.xml:23(td)
+msgid "(StrOpt) IP address of sheep daemon."
+msgstr ""
+
+#: ./doc/common/tables/glance-sheepdog.xml:26(td)
+msgid "sheepdog_store_chunk_size = 64"
+msgstr ""
+
+#: ./doc/common/tables/glance-sheepdog.xml:27(td)
+msgid "(IntOpt) Images will be chunked into objects of this size (in megabytes). For best performance, this should be a power of two."
+msgstr ""
+
+#: ./doc/common/tables/glance-sheepdog.xml:30(td)
+msgid "sheepdog_store_port = 7000"
+msgstr ""
+
+#: ./doc/common/tables/glance-sheepdog.xml:31(td)
+msgid "(IntOpt) Port of sheep daemon."
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml:7(literal) ./doc/common/tables/swift-container-sync-realms-realm2.xml:7(literal) ./doc/common/tables/swift-container-sync-realms-realm1.xml:7(literal)
+msgid "container-sync-realms.conf-sample"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml:18(td)
+msgid "mtime_check_interval = 300"
+msgstr ""
+
+#: ./doc/common/tables/cinder-windows.xml:8(caption)
+msgid "Description of configuration options for windows"
+msgstr ""
+
+#: ./doc/common/tables/cinder-windows.xml:22(td)
+msgid "windows_iscsi_lun_path = C:\\iSCSIVirtualDisks"
+msgstr ""
+
+#: ./doc/common/tables/cinder-windows.xml:23(td)
+msgid "(StrOpt) Path to store VHD backed volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san-solaris.xml:8(caption)
+msgid "Description of configuration options for san-solaris"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san-solaris.xml:22(td)
+msgid "san_zfs_volume_base = rpool/"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san-solaris.xml:23(td)
+msgid "(StrOpt) The ZFS path under which to create zvols for volumes."
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml:8(caption)
+msgid "Description of configuration options for nuage"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml:22(td)
+msgid "auth_resource ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml:23(td)
+msgid "(StrOpt) Nuage provided uri for initial authorization to access VSD"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml:26(td)
+msgid "base_uri = /"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml:27(td)
+msgid "(StrOpt) Nuage provided base uri to reach out to VSD"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml:30(td)
+msgid "default_floatingip_quota = 254"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml:31(td)
+msgid "(IntOpt) Per Net Partition quota of floating ips"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml:34(td)
+msgid "default_net_partition_name = OpenStackDefaultNetPartition"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml:35(td)
+msgid "(StrOpt) Default Network partition in which VSD will orchestrate network resources using openstack"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml:38(td)
+msgid "organization = system"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml:39(td)
+msgid "(StrOpt) Organization name in which VSD will orchestrate network resources using openstack"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml:42(td)
+msgid "server = localhost:8800"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml:43(td)
+msgid "(StrOpt) IP Address and Port of Nuage's VSD server"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml:46(td)
+msgid "serverauth = username:password"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml:47(td)
+msgid "(StrOpt) Username and password for authentication"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml:50(td)
+msgid "serverssl = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml:51(td)
+msgid "(BoolOpt) Boolean for SSL connection with VSD server"
 msgstr ""
 
 #: ./doc/common/tables/neutron-bigswitch.xml:8(caption)
 msgid "Description of configuration options for bigswitch"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:8(caption)
-msgid "Description of configuration options for libvirt"
+#: ./doc/common/tables/ceilometer-rpc.xml:22(td) ./doc/common/tables/trove-rpc.xml:22(td) ./doc/common/tables/heat-rpc.xml:22(td) ./doc/common/tables/neutron-common.xml:38(td)
+msgid "allowed_rpc_exception_modules = nova.exception, cinder.exception, exceptions"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:22(td)
-msgid "remove_unused_base_images = True"
+#: ./doc/common/tables/ceilometer-rpc.xml:26(td)
+msgid "dispatcher = ['database']"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:23(td)
-msgid "(BoolOpt) Should unused base images be removed?"
+#: ./doc/common/tables/ceilometer-rpc.xml:27(td)
+msgid "(MultiStrOpt) Dispatcher to process data."
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:26(td)
-msgid "remove_unused_original_minimum_age_seconds = 86400"
+#: ./doc/common/tables/ceilometer-rpc.xml:30(td)
+msgid "rpc_backend = ceilometer.openstack.common.rpc.impl_kombu"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:27(td)
-msgid "(IntOpt) Unused unresized base images younger than this will not be removed"
+#: ./doc/common/tables/ceilometer-rpc.xml:66(td)
+msgid "rpc_zmq_matchmaker = ceilometer.openstack.common.rpc.matchmaker.MatchMakerLocalhost"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:33(td)
-msgid "checksum_base_images = False"
+#: ./doc/common/tables/ceilometer-rpc.xml:78(th)
+msgid "[publisher]"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:34(td)
-msgid "(BoolOpt) Write a checksum for files in _base to disk"
+#: ./doc/common/tables/ceilometer-rpc.xml:81(td)
+msgid "metering_secret = change this or be hacked"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:37(td)
-msgid "checksum_interval_seconds = 3600"
+#: ./doc/common/tables/ceilometer-rpc.xml:82(td)
+msgid "(StrOpt) Secret value for signing metering messages."
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:38(td)
-msgid "(IntOpt) How frequently to checksum base images"
+#: ./doc/common/tables/ceilometer-rpc.xml:85(th)
+msgid "[publisher_rpc]"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:41(td)
-msgid "connection_uri ="
+#: ./doc/common/tables/ceilometer-rpc.xml:88(td)
+msgid "metering_topic = metering"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:42(td)
-msgid "(StrOpt) Override the default libvirt URI (which is dependent on virt_type)"
+#: ./doc/common/tables/ceilometer-rpc.xml:89(td)
+msgid "(StrOpt) The topic that ceilometer uses for metering messages."
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:45(td)
-msgid "cpu_mode = None"
+#: ./doc/common/tables/ceilometer-rpc.xml:96(td) ./doc/common/tables/heat-rpc.xml:69(td)
+msgid "(ListOpt) AMQP topic(s) used for OpenStack notifications"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:46(td)
-msgid "(StrOpt) Set to \"host-model\" to clone the host CPU feature flags; to \"host-passthrough\" to use the host CPU model exactly; to \"custom\" to use a named CPU model; to \"none\" to not set any CPU model. If virt_type=\"kvm|qemu\", it will default to \"host-model\", otherwise it will default to \"none\""
+#: ./doc/common/tables/swift-container-server-container-updater.xml:7(literal)
+msgid "[container-updater]"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:49(td)
-msgid "cpu_model = None"
+#: ./doc/common/tables/swift-container-server-container-updater.xml:18(td)
+msgid "log_name = container-updater"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:50(td)
-msgid "(StrOpt) Set to a named libvirt CPU model (see names listed in /usr/share/libvirt/cpu_map.xml). Only has effect if cpu_mode=\"custom\" and virt_type=\"kvm|qemu\""
+#: ./doc/common/tables/swift-container-server-container-updater.xml:33(td)
+msgid "concurrency = 4"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:53(td)
-msgid "disk_prefix = None"
+#: ./doc/common/tables/swift-container-server-container-updater.xml:42(td) ./doc/common/tables/swift-object-server-object-updater.xml:39(td)
+msgid "slowdown = 0.01"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:54(td)
-msgid "(StrOpt) Override the default disk prefix for the devices attached to a server, which is dependent on virt_type. (valid options are: sd, xvd, uvd, vd)"
+#: ./doc/common/tables/swift-container-server-container-updater.xml:42(td) ./doc/common/tables/swift-object-server-object-updater.xml:39(td)
+msgid "Time in seconds to wait between objects"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:57(td)
-msgid "image_info_filename_pattern = $instances_path/$image_cache_subdirectory_name/%(image)s.info"
+#: ./doc/common/tables/swift-container-server-container-updater.xml:45(td)
+msgid "account_suppression_time = 60"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:58(td)
-msgid "(StrOpt) Allows image information files to be stored in non-standard locations"
+#: ./doc/common/tables/swift-container-server-container-updater.xml:45(td)
+msgid "Seconds to suppress updating an account that has generated an error (timeout, not yet found, etc.)"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:61(td)
-msgid "remove_unused_kernels = False"
+#: ./doc/common/tables/trove-db_mongodb.xml:8(caption)
+msgid "Description of configuration options for db_mongodb"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:62(td)
-msgid "(BoolOpt) Should unused kernel images be removed? This is only safe to enable if all compute nodes have been updated to support this option. This will be enabled by default in future."
+#: ./doc/common/tables/trove-db_mongodb.xml:19(th)
+msgid "[mongodb]"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:65(td)
-msgid "remove_unused_resized_minimum_age_seconds = 3600"
+#: ./doc/common/tables/trove-db_mongodb.xml:26(td)
+msgid "mount_point = /var/lib/mongodb"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:66(td)
-msgid "(IntOpt) Unused resized base images younger than this will not be removed"
+#: ./doc/common/tables/trove-db_mongodb.xml:30(td)
+msgid "tcp_ports = 2500, 27017"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:69(td)
-msgid "rng_dev_path = None"
+#: ./doc/common/tables/trove-db_mongodb.xml:35(td)
+msgid "(ListOpt) List of UPD ports and/or port ranges to open in the security group (only applicable if trove_security_groups_support is True)"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:70(td)
-msgid "(StrOpt) A path to a device that will be used as source of entropy on the host. Permitted options are: /dev/random or /dev/hwrng"
+#: ./doc/common/tables/swift-object-server-object-replicator.xml:7(literal)
+msgid "[object-replicator]"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:73(td)
-msgid "snapshots_directory = $instances_path/snapshots"
+#: ./doc/common/tables/swift-object-server-object-replicator.xml:18(td)
+msgid "log_name = object-replicator"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:74(td)
-msgid "(StrOpt) Location where libvirt driver will store snapshots before uploading them to image service"
+#: ./doc/common/tables/swift-object-server-object-replicator.xml:33(td)
+msgid "daemonize = on"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:77(td)
-msgid "vif_driver = nova.virt.libvirt.vif.LibvirtGenericVIFDriver"
+#: ./doc/common/tables/swift-object-server-object-replicator.xml:33(td)
+msgid "Whether or not to run replication as a daemon"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:78(td)
-msgid "(StrOpt) DEPRECATED. The libvirt VIF driver to configure the VIFs.This option is deprecated and will be removed in the Juno release."
+#: ./doc/common/tables/swift-object-server-object-replicator.xml:42(td)
+msgid "stats_interval = 300"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:81(td)
-msgid "virt_type = kvm"
+#: ./doc/common/tables/swift-object-server-object-replicator.xml:42(td)
+msgid "Interval in seconds between logging replication statistics"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:82(td)
-msgid "(StrOpt) Libvirt domain type (valid options are: kvm, lxc, qemu, uml, xen)"
+#: ./doc/common/tables/swift-object-server-object-replicator.xml:45(td)
+msgid "sync_method = rsync"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:85(td) ./doc/common/tables/cinder-storage.xml:98(td)
-msgid "volume_clear = zero"
+#: ./doc/common/tables/swift-object-server-object-replicator.xml:48(td)
+msgid "rsync_timeout = 900"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:86(td)
-msgid "(StrOpt) Method used to wipe old volumes (valid options are: none, zero, shred)"
+#: ./doc/common/tables/swift-object-server-object-replicator.xml:48(td)
+msgid "Max duration (seconds) of a partition rsync"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:89(td) ./doc/common/tables/cinder-storage.xml:106(td)
-msgid "volume_clear_size = 0"
+#: ./doc/common/tables/swift-object-server-object-replicator.xml:51(td)
+msgid "rsync_bwlimit = 0"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:90(td) ./doc/common/tables/cinder-storage.xml:107(td)
-msgid "(IntOpt) Size in MiB to wipe at start of old volumes. 0 =&gt; all"
+#: ./doc/common/tables/swift-object-server-object-replicator.xml:54(td)
+msgid "rsync_io_timeout = 30"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:93(td)
-msgid "volume_drivers = iscsi=nova.virt.libvirt.volume.LibvirtISCSIVolumeDriver, iser=nova.virt.libvirt.volume.LibvirtISERVolumeDriver, local=nova.virt.libvirt.volume.LibvirtVolumeDriver, fake=nova.virt.libvirt.volume.LibvirtFakeVolumeDriver, rbd=nova.virt.libvirt.volume.LibvirtNetVolumeDriver, sheepdog=nova.virt.libvirt.volume.LibvirtNetVolumeDriver, nfs=nova.virt.libvirt.volume.LibvirtNFSVolumeDriver, aoe=nova.virt.libvirt.volume.LibvirtAOEVolumeDriver, glusterfs=nova.virt.libvirt.volume.LibvirtGlusterfsVolumeDriver, fibre_channel=nova.virt.libvirt.volume.LibvirtFibreChannelVolumeDriver, scality=nova.virt.libvirt.volume.LibvirtScalityVolumeDriver"
+#: ./doc/common/tables/swift-object-server-object-replicator.xml:54(td)
+msgid "Passed to rsync for a max duration (seconds) of an I/O op"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:94(td)
-msgid "(ListOpt) Libvirt handlers for remote volumes."
+#: ./doc/common/tables/swift-object-server-object-replicator.xml:57(td) ./doc/common/tables/swift-object-server-object-updater.xml:36(td)
+msgid "node_timeout = &lt;whatever's in the DEFAULT section or 10&gt;"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:97(td)
-msgid "wait_soft_reboot_seconds = 120"
+#: ./doc/common/tables/swift-object-server-object-replicator.xml:60(td)
+msgid "http_timeout = 60"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml:98(td)
-msgid "(IntOpt) Number of seconds to wait for instance to shut down after soft reboot request is made. We fall back to hard reboot if instance does not shutdown within this window."
+#: ./doc/common/tables/swift-object-server-object-replicator.xml:60(td)
+msgid "Maximum duration for an HTTP request"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml:63(td)
+msgid "lockup_timeout = 1800"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml:63(td)
+msgid "Attempts to kill all workers if nothing replications for lockup_timeout seconds"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml:69(td)
+msgid "ring_check_interval = 15"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml:69(td)
+msgid "How often (in seconds) to check the ring"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml:75(td)
+msgid "rsync_error_log_line_length = 0"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml:78(td)
+msgid "handoffs_first = False"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml:78(td)
+msgid "If set to True, partitions that are not supposed to be on the node will be replicated first. The default setting should not be changed, except for extreme situations."
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml:81(td)
+msgid "handoff_delete = auto"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml:81(td)
+msgid "By default handoff partitions will be removed when it has successfully replicated to all the canonical nodes. If set to an integer n, it will remove the partition if it is successfully replicated to n nodes. The default setting should not be changed, except for extremem situations. This uses what's set here, or what's set in the DEFAULT section, or 10 (though other sections use 3 as the final default)."
+msgstr ""
+
+#: ./doc/common/tables/glance-filesystem.xml:8(caption)
+msgid "Description of configuration options for filesystem"
+msgstr ""
+
+#: ./doc/common/tables/glance-filesystem.xml:22(td)
+msgid "filesystem_store_datadir = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-filesystem.xml:23(td)
+msgid "(StrOpt) Directory to which the Filesystem backend store writes images."
+msgstr ""
+
+#: ./doc/common/tables/glance-filesystem.xml:26(td)
+msgid "filesystem_store_datadirs = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-filesystem.xml:27(td)
+msgid "(MultiStrOpt) List of directories and its priorities to which the Filesystem backend store writes images."
+msgstr ""
+
+#: ./doc/common/tables/glance-filesystem.xml:30(td)
+msgid "filesystem_store_metadata_file = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-filesystem.xml:31(td)
+msgid "(StrOpt) The path to a file which contains the metadata to be returned with any location associated with this store. The file must contain a valid JSON dict."
+msgstr ""
+
+#: ./doc/common/tables/trove-rpc.xml:38(td)
+msgid "num_tries = 3"
+msgstr ""
+
+#: ./doc/common/tables/trove-rpc.xml:47(td)
+msgid "(IntOpt) The interval in seconds which periodic tasks are run."
+msgstr ""
+
+#: ./doc/common/tables/trove-rpc.xml:50(td)
+msgid "rpc_backend = trove.openstack.common.rpc.impl_kombu"
+msgstr ""
+
+#: ./doc/common/tables/trove-rpc.xml:77(th)
+msgid "[secure_messages]"
+msgstr ""
+
+#: ./doc/common/tables/trove-rpc.xml:80(td) ./doc/common/tables/keystone-trust.xml:26(td)
+msgid "enabled = True"
+msgstr ""
+
+#: ./doc/common/tables/trove-rpc.xml:81(td)
+msgid "(BoolOpt) Whether Secure Messaging (Signing) is enabled, defaults to enabled"
+msgstr ""
+
+#: ./doc/common/tables/trove-rpc.xml:84(td)
+msgid "encrypt = False"
+msgstr ""
+
+#: ./doc/common/tables/trove-rpc.xml:85(td)
+msgid "(BoolOpt) Whether Secure Messaging (Encryption) is enabled, defaults to not enabled"
+msgstr ""
+
+#: ./doc/common/tables/trove-rpc.xml:88(td)
+msgid "enforced = False"
+msgstr ""
+
+#: ./doc/common/tables/trove-rpc.xml:89(td)
+msgid "(BoolOpt) Whether Secure Messaging (Signing) is enforced, defaults to not enforced"
+msgstr ""
+
+#: ./doc/common/tables/trove-rpc.xml:92(td)
+msgid "kds_endpoint = None"
+msgstr ""
+
+#: ./doc/common/tables/trove-rpc.xml:93(td)
+msgid "(StrOpt) KDS endpoint (ex: http://kds.example.com:35357/v3)"
+msgstr ""
+
+#: ./doc/common/tables/trove-rpc.xml:96(td)
+msgid "secret_key = None"
+msgstr ""
+
+#: ./doc/common/tables/trove-rpc.xml:97(td)
+msgid "(MultiStrOpt) A list of keys: (ex: name:&lt;base64 encoded key&gt;), ignored if secret_keys_file is set"
+msgstr ""
+
+#: ./doc/common/tables/trove-rpc.xml:100(td)
+msgid "secret_keys_file = None"
+msgstr ""
+
+#: ./doc/common/tables/trove-rpc.xml:101(td)
+msgid "(StrOpt) Path to the file containing the keys, takes precedence over secret_key"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-swift.xml:22(td)
+msgid "reseller_prefix = AUTH_"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-swift.xml:23(td)
+msgid "(StrOpt) Swift reseller prefix. Must be on par with reseller_prefix in proxy-server.conf."
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml:8(caption)
+msgid "Description of configuration options for backup"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml:22(td)
+msgid "backup_aes_cbc_key = default_aes_cbc_key"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml:23(td)
+msgid "(StrOpt) Default OpenSSL aes_cbc key."
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml:26(td)
+msgid "backup_chunk_size = 65536"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml:27(td)
+msgid "(IntOpt) Chunk size to stream to swift container. This should be in multiples of 128 bytes, since this is the size of an md5 digest block allowing the process to update the file checksum during streaming. See: http://stackoverflow.com/questions/1131220/"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml:30(td)
+msgid "backup_incremental_strategy = {'InnoBackupEx': 'InnoBackupExIncremental'}"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml:31(td)
+msgid "(DictOpt) Incremental Backup Runner Based off of the default strategy. For strategies that do not implement an incremental the runner will use the default full backup."
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml:34(td)
+msgid "backup_namespace = trove.guestagent.strategies.backup.mysql_impl"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml:35(td)
+msgid "(StrOpt) Namespace to load backup strategies from."
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml:38(td)
+msgid "backup_runner = trove.guestagent.backup.backup_types.InnoBackupEx"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml:42(td)
+msgid "backup_runner_options = {}"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml:43(td)
+msgid "(DictOpt) Additional options to be passed to the backup runner."
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml:46(td)
+msgid "backup_segment_max_size = 2147483648"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml:47(td)
+msgid "(IntOpt) Maximum size of each segment of the backup file."
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml:54(td)
+msgid "backup_swift_container = database_backups"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml:58(td)
+msgid "backup_use_gzip_compression = True"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml:59(td)
+msgid "(BoolOpt) Compress backups using gzip."
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml:62(td)
+msgid "backup_use_openssl_encryption = True"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml:63(td)
+msgid "(BoolOpt) Encrypt backups using OpenSSL."
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml:66(td)
+msgid "backup_use_snet = False"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml:67(td)
+msgid "(BoolOpt) Send backup files over snet."
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml:70(td)
+msgid "backups_page_size = 20"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:8(caption)
+msgid "Description of configuration options for network"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:22(td)
+msgid "allow_same_net_traffic = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:23(td)
+msgid "(BoolOpt) Whether to allow network traffic from same network"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:26(td)
+msgid "auto_assign_floating_ip = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:27(td)
+msgid "(BoolOpt) Autoassigning floating IP to VM"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:30(td)
+msgid "cnt_vpn_clients = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:31(td)
+msgid "(IntOpt) Number of addresses reserved for vpn clients"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:34(td)
+msgid "create_unique_mac_address_attempts = 5"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:35(td)
+msgid "(IntOpt) Number of attempts to create unique mac address"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:38(td)
+msgid "default_access_ip_network_name = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:39(td)
+msgid "(StrOpt) Name of network to use to set access IPs for instances"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:42(td)
+msgid "default_floating_pool = nova"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:43(td)
+msgid "(StrOpt) Default pool for floating IPs"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:46(td)
+msgid "defer_iptables_apply = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:47(td)
+msgid "(BoolOpt) Whether to batch up the application of IPTables rules during a host restart and apply all at the end of the init phase"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:50(td)
+msgid "dhcp_domain = novalocal"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:54(td)
+msgid "dhcp_lease_time = 120"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:55(td)
+msgid "(IntOpt) Lifetime of a DHCP lease in seconds"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:58(td)
+msgid "dhcpbridge = $bindir/nova-dhcpbridge"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:59(td)
+msgid "(StrOpt) Location of nova-dhcpbridge"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:62(td)
+msgid "dhcpbridge_flagfile = ['/etc/nova/nova-dhcpbridge.conf']"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:63(td)
+msgid "(MultiStrOpt) Location of flagfiles for dhcpbridge"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:66(td)
+msgid "dns_server = []"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:67(td)
+msgid "(MultiStrOpt) If set, uses specific DNS server for dnsmasq. Can be specified multiple times."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:70(td)
+msgid "dns_update_periodic_interval = -1"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:71(td)
+msgid "(IntOpt) Number of seconds to wait between runs of updates to DNS entries."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:74(td) ./doc/common/tables/neutron-dhcp_agent.xml:22(td)
+msgid "dnsmasq_config_file ="
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:75(td) ./doc/common/tables/neutron-dhcp_agent.xml:23(td)
+msgid "(StrOpt) Override the default dnsmasq settings with this file"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:78(td) ./doc/common/tables/neutron-securitygroups.xml:26(td)
+msgid "firewall_driver = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:79(td)
+msgid "(StrOpt) Firewall driver (defaults to hypervisor specific iptables driver)"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:82(td)
+msgid "fixed_ip_disassociate_timeout = 600"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:83(td)
+msgid "(IntOpt) Seconds after which a deallocated IP is disassociated"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:86(td)
+msgid "flat_injected = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:87(td)
+msgid "(BoolOpt) Whether to attempt to inject network setup into guest"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:90(td)
+msgid "flat_interface = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:91(td)
+msgid "(StrOpt) FlatDhcp will bridge into this interface if set"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:94(td)
+msgid "flat_network_bridge = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:95(td)
+msgid "(StrOpt) Bridge for simple network instances"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:98(td)
+msgid "flat_network_dns = 8.8.4.4"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:99(td)
+msgid "(StrOpt) DNS server for simple network"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:102(td)
+msgid "floating_ip_dns_manager = nova.network.noop_dns_driver.NoopDNSDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:103(td)
+msgid "(StrOpt) Full class name for the DNS Manager for floating IPs"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:106(td)
+msgid "force_dhcp_release = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:107(td)
+msgid "(BoolOpt) If True, send a dhcp release on instance termination"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:110(td)
+msgid "force_snat_range = []"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:111(td)
+msgid "(MultiStrOpt) Traffic to this range will always be snatted to the fallback ip, even if it would normally be bridged out of the node. Can be specified multiple times."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:114(td)
+msgid "forward_bridge_interface = ['all']"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:115(td)
+msgid "(MultiStrOpt) An interface that bridges can forward to. If this is set to all then all traffic will be forwarded. Can be specified multiple times."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:118(td)
+msgid "gateway = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:119(td)
+msgid "(StrOpt) Default IPv4 gateway"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:122(td)
+msgid "injected_network_template = $pybasedir/nova/virt/interfaces.template"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:123(td)
+msgid "(StrOpt) Template file for injected network"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:126(td)
+msgid "instance_dns_domain ="
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:127(td)
+msgid "(StrOpt) Full class name for the DNS Zone for instance IPs"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:130(td)
+msgid "instance_dns_manager = nova.network.noop_dns_driver.NoopDNSDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:131(td)
+msgid "(StrOpt) Full class name for the DNS Manager for instance IPs"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:134(td)
+msgid "iptables_bottom_regex ="
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:135(td)
+msgid "(StrOpt) Regular expression to match iptables rule that should always be on the bottom."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:138(td)
+msgid "iptables_drop_action = DROP"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:139(td)
+msgid "(StrOpt) The table that iptables to jump to when a packet is to be dropped."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:142(td)
+msgid "iptables_top_regex ="
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:143(td)
+msgid "(StrOpt) Regular expression to match iptables rule that should always be on the top."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:146(td)
+msgid "l3_lib = nova.network.l3.LinuxNetL3"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:147(td)
+msgid "(StrOpt) Indicates underlying L3 management library"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:150(td)
+msgid "linuxnet_interface_driver = nova.network.linux_net.LinuxBridgeInterfaceDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:151(td)
+msgid "(StrOpt) Driver used to create ethernet devices."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:154(td)
+msgid "linuxnet_ovs_integration_bridge = br-int"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:155(td)
+msgid "(StrOpt) Name of Open vSwitch bridge used with linuxnet"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:158(td)
+msgid "multi_host = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:159(td)
+msgid "(BoolOpt) Default value for multi_host in networks. Also, if set, some rpc network calls will be sent directly to host."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:162(td)
+msgid "network_allocate_retries = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:163(td)
+msgid "(IntOpt) Number of times to retry network allocation on failures"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:166(td)
+msgid "network_api_class = nova.network.api.API"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:167(td)
+msgid "(StrOpt) The full class name of the network API class to use"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:171(td)
+msgid "(IntOpt) MTU setting for network interface"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:174(td)
+msgid "network_driver = nova.network.linux_net"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:175(td)
+msgid "(StrOpt) Driver to use for network creation"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:178(td)
+msgid "network_manager = nova.network.manager.VlanManager"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:179(td)
+msgid "(StrOpt) Full class name for the Manager for network"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:182(td)
+msgid "network_size = 256"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:183(td)
+msgid "(IntOpt) Number of addresses in each private subnet"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:186(td)
+msgid "network_topic = network"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:187(td)
+msgid "(StrOpt) The topic network nodes listen on"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:190(td)
+msgid "networks_path = $state_path/networks"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:191(td)
+msgid "(StrOpt) Location to keep network config files"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:194(td)
+msgid "num_networks = 1"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:195(td)
+msgid "(IntOpt) Number of networks to support"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:198(td)
+msgid "ovs_vsctl_timeout = 120"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:199(td)
+msgid "(IntOpt) Amount of time, in seconds, that ovs_vsctl should wait for a response from the database. 0 is to wait forever."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:202(td)
+msgid "public_interface = eth0"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:203(td)
+msgid "(StrOpt) Interface for public IP addresses"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:206(td)
+msgid "routing_source_ip = $my_ip"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:207(td)
+msgid "(StrOpt) Public IP of network host"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:210(td)
+msgid "security_group_api = nova"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:211(td)
+msgid "(StrOpt) The full class name of the security API class"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:214(td)
+msgid "send_arp_for_ha = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:215(td)
+msgid "(BoolOpt) Send gratuitous ARPs for HA setup"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:218(td)
+msgid "send_arp_for_ha_count = 3"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:219(td)
+msgid "(IntOpt) Send this many gratuitous ARPs for HA setup"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:222(td)
+msgid "share_dhcp_address = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:223(td)
+msgid "(BoolOpt) If True in multi_host mode, all compute hosts share the same dhcp address. The same IP address used for DHCP will be added on each nova-network node which is only visible to the vms on the same host."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:226(td)
+msgid "teardown_unused_network_gateway = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:227(td)
+msgid "(BoolOpt) If True, unused gateway devices (VLAN and bridge) are deleted in VLAN network mode with multi hosted networks"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:230(td)
+msgid "update_dns_entries = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:231(td)
+msgid "(BoolOpt) If True, when a DNS entry must be updated, it sends a fanout cast to all network hosts to update their DNS entries in multi host mode"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:234(td)
+msgid "use_network_dns_servers = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:235(td)
+msgid "(BoolOpt) If set, uses the dns1 and dns2 from the network ref. as dns servers."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:238(td)
+msgid "use_neutron_default_nets = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:239(td)
+msgid "(StrOpt) Control for checking for default networks"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:242(td)
+msgid "use_single_default_gateway = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:243(td)
+msgid "(BoolOpt) Use single default gateway. Only first nic of vm will get default gateway from dhcp server"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:246(td)
+msgid "vlan_interface = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:247(td)
+msgid "(StrOpt) VLANs will bridge into this interface if set"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:250(td)
+msgid "vlan_start = 100"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:251(td)
+msgid "(IntOpt) First VLAN for private networks"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:257(td)
+msgid "vlan_interface = vmnic0"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml:258(td)
+msgid "(StrOpt) Physical ethernet adapter name for vlan networking"
+msgstr ""
+
+#: ./doc/common/tables/glance-redis.xml:23(td) ./doc/common/tables/keystone-redis.xml:23(td)
+msgid "(StrOpt) Host to locate redis."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:8(caption) ./doc/common/tables/cinder-ssl.xml:8(caption) ./doc/common/tables/trove-ssl.xml:8(caption) ./doc/common/tables/neutron-ssl.xml:8(caption) ./doc/common/tables/ceilometer-ssl.xml:8(caption) ./doc/common/tables/glance-ssl.xml:8(caption)
+msgid "Description of configuration options for ssl"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:19(th)
+msgid "[signing]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:22(td) ./doc/common/tables/keystone-ssl.xml:57(td)
+msgid "ca_certs = /etc/keystone/ssl/certs/ca.pem"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:23(td)
+msgid "(StrOpt) Path of the CA for token signing."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:26(td) ./doc/common/tables/keystone-ssl.xml:61(td)
+msgid "ca_key = /etc/keystone/ssl/private/cakey.pem"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:27(td)
+msgid "(StrOpt) Path of the CA Key for token signing."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:30(td)
+msgid "cert_subject = /C=US/ST=Unset/L=Unset/O=Unset/CN=www.example.com"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:31(td)
+msgid "(StrOpt) Certificate Subject (auto generated certificate) for token signing."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:34(td)
+msgid "certfile = /etc/keystone/ssl/certs/signing_cert.pem"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:35(td)
+msgid "(StrOpt) Path of the certfile for token signing."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:38(td)
+msgid "key_size = 2048"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:39(td)
+msgid "(IntOpt) Key Size (in bits) for token signing cert (auto generated certificate)."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:42(td)
+msgid "keyfile = /etc/keystone/ssl/private/signing_key.pem"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:43(td)
+msgid "(StrOpt) Path of the keyfile for token signing."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:46(td)
+msgid "token_format = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:47(td)
+msgid "(StrOpt) Deprecated in favor of provider in the [token] section."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:50(td) ./doc/common/tables/keystone-ssl.xml:89(td)
+msgid "valid_days = 3650"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:51(td)
+msgid "(IntOpt) Day the token signing cert is valid for (auto generated certificate)."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:58(td)
+msgid "(StrOpt) Path of the ca cert file for SSL."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:62(td)
+msgid "(StrOpt) Path of the CA key file for SSL."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:65(td)
+msgid "cert_required = False"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:66(td)
+msgid "(BoolOpt) Require client certificate."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:69(td)
+msgid "cert_subject = /C=US/ST=Unset/L=Unset/O=Unset/CN=localhost"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:70(td)
+msgid "(StrOpt) SSL Certificate Subject (auto generated certificate)."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:73(td)
+msgid "certfile = /etc/keystone/ssl/certs/keystone.pem"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:74(td)
+msgid "(StrOpt) Path of the certfile for SSL."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:78(td)
+msgid "(BoolOpt) Toggle for SSL support on the keystone eventlet servers."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:81(td)
+msgid "key_size = 1024"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:82(td)
+msgid "(IntOpt) SSL Key Length (in bits) (auto generated certificate)."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:85(td)
+msgid "keyfile = /etc/keystone/ssl/private/keystonekey.pem"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:86(td)
+msgid "(StrOpt) Path of the keyfile for SSL."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml:90(td)
+msgid "(IntOpt) Days the certificate is valid for once signed (auto generated certificate)."
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml:8(caption)
+msgid "Description of configuration options for ca"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml:22(td)
+msgid "ca_file = cacert.pem"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml:23(td)
+msgid "(StrOpt) Filename of root CA"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml:26(td)
+msgid "ca_path = $state_path/CA"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml:27(td)
+msgid "(StrOpt) Where we keep our root CA"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml:30(td)
+msgid "cert_manager = nova.cert.manager.CertManager"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml:31(td)
+msgid "(StrOpt) Full class name for the Manager for cert"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml:34(td)
+msgid "cert_topic = cert"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml:35(td)
+msgid "(StrOpt) The topic cert nodes listen on"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml:38(td)
+msgid "crl_file = crl.pem"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml:39(td)
+msgid "(StrOpt) Filename of root Certificate Revocation List"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml:42(td)
+msgid "key_file = private/cakey.pem"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml:43(td)
+msgid "(StrOpt) Filename of private key"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml:46(td)
+msgid "keys_path = $state_path/keys"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml:47(td)
+msgid "(StrOpt) Where we keep our keys"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml:50(td)
+msgid "project_cert_subject = /C=US/ST=California/O=OpenStack/OU=NovaDev/CN=project-ca-%.16s-%s"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml:51(td)
+msgid "(StrOpt) Subject for certificate for projects, %s for project, timestamp"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml:54(td)
+msgid "use_project_ca = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml:55(td)
+msgid "(BoolOpt) Should we use a CA for each project?"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml:58(td)
+msgid "user_cert_subject = /C=US/ST=California/O=OpenStack/OU=NovaDev/CN=%.16s-%.16s-%s"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml:59(td)
+msgid "(StrOpt) Subject for certificate for users, %s for project, user, timestamp"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml:66(td) ./doc/common/tables/glance-ssl.xml:23(td)
+msgid "(StrOpt) CA certificate file to use to verify connecting clients."
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml:70(td)
+msgid "(StrOpt) Certificate file to use when starting the server securely."
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml:74(td)
+msgid "(StrOpt) Private key file to use when starting the server securely."
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml:8(caption)
+msgid "Description of configuration options for dhcp_agent"
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml:26(td)
+msgid "dnsmasq_dns_servers = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml:27(td)
+msgid "(ListOpt) Comma-separated list of the DNS servers which will be used as forwarders."
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml:30(td)
+msgid "dnsmasq_lease_max = 16777216"
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml:31(td)
+msgid "(IntOpt) Limit number of leases to prevent a denial-of-service."
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml:34(td)
+msgid "enable_isolated_metadata = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml:35(td)
+msgid "(BoolOpt) Support Metadata requests on isolated networks."
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml:38(td)
+msgid "enable_metadata_network = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml:39(td)
+msgid "(BoolOpt) Allows for serving metadata requests from a dedicated network. Requires enable_isolated_metadata = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml:42(td)
+msgid "num_sync_threads = 4"
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml:43(td)
+msgid "(IntOpt) Number of threads to use during sync process."
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml:46(td)
+msgid "resync_interval = 5"
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml:47(td)
+msgid "(IntOpt) Interval to resync."
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml:50(td)
+msgid "use_namespaces = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml:51(td)
+msgid "(BoolOpt) Allow overlapping IP."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml:8(caption)
+msgid "Description of configuration options for collector"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml:22(td)
+msgid "collector_workers = 1"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml:23(td)
+msgid "(IntOpt) Number of workers for collector service. A single collector is enabled by default."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml:26(th)
+msgid "[collector]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml:29(td)
+msgid "udp_address = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml:30(td)
+msgid "(StrOpt) Address to which the UDP socket is bound. Set to an empty string to disable."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml:33(td)
+msgid "udp_port = 4952"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml:34(td)
+msgid "(IntOpt) Port to which the UDP socket is bound."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml:37(th)
+msgid "[dispatcher_file]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml:40(td)
+msgid "backup_count = 0"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml:41(td)
+msgid "(IntOpt) The max number of the files to keep."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml:44(td)
+msgid "file_path = None"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml:45(td)
+msgid "(StrOpt) Name and the location of the file to record meters."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml:48(td)
+msgid "max_bytes = 0"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml:49(td)
+msgid "(IntOpt) The max size of the file."
+msgstr ""
+
+#: ./doc/common/tables/cinder-hds-hus.xml:8(caption)
+msgid "Description of configuration options for hds-hus"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hds-hus.xml:22(td)
+msgid "hds_cinder_config_file = /opt/hds/hus/cinder_hus_conf.xml"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hds-hus.xml:23(td)
+msgid "(StrOpt) configuration file for HDS cinder plugin for HUS"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:8(caption)
+msgid "Description of configuration options for netapp_7mode_iscsi"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:54(td)
+msgid "netapp_vfiler = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:55(td)
+msgid "(StrOpt) The vFiler unit on which provisioning of block storage volumes will be done. This option is only used by the driver when connecting to an instance with a storage family of Data ONTAP operating in 7-Mode and the storage protocol selected is iSCSI. Only use this option when utilizing the MultiStore feature on the NetApp storage system."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:58(td)
+msgid "netapp_volume_list = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml:59(td)
+msgid "(StrOpt) This option is only utilized when the storage protocol is configured to use iSCSI. This option is used to restrict provisioning to the specified controller volumes. Specify the value of this option to be a comma separated list of NetApp controller volume names to be used for provisioning."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-hash.xml:7(literal)
+msgid "[swift-hash]"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-hash.xml:18(td)
+msgid "swift_hash_path_suffix = changeme"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-hash.xml:18(td)
+msgid "A suffix used by hash_path to offer a bit more security when generating hashes for paths. It simply appends this value to all paths; if someone knows this suffix, it's easier for them to guess the hash a path will end up with. New installations are advised to set this parameter to a random secret, which would not be disclosed ouside the organization. The same secret needs to be used by all swift servers of the same cluster. Existing installations should set this parameter to an empty string."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-hash.xml:29(td)
+msgid "swift_hash_path_prefix = changeme"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-hash.xml:29(td)
+msgid "A prefix used by hash_path to offer a bit more security when generating hashes for paths. It simply appends this value to all paths; if someone knows this suffix, it's easier for them to guess the hash a path will end up with. New installations are advised to set this parameter to a random secret, which would not be disclosed ouside the organization. The same secret needs to be used by all swift servers of the same cluster. Existing installations should set this parameter to an empty string."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_gre.xml:8(caption)
+msgid "Description of configuration options for ml2_gre"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_gre.xml:19(th)
+msgid "[ml2_type_gre]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_gre.xml:23(td)
+msgid "(ListOpt) Comma-separated list of &lt;tun_min&gt;:&lt;tun_max&gt; tuples enumerating ranges of GRE tunnel IDs that are available for tenant network allocation"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml:8(caption)
+msgid "Description of configuration options for varmour"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml:19(th)
+msgid "[vArmour]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml:22(td)
+msgid "director = localhost"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml:23(td)
+msgid "(StrOpt) vArmour director ip"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml:26(td)
+msgid "director_port = 443"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml:27(td)
+msgid "(StrOpt) vArmour director port"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml:30(td)
+msgid "password = varmour"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml:31(td)
+msgid "(StrOpt) vArmour director password"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml:34(td)
+msgid "username = varmour"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml:35(td)
+msgid "(StrOpt) vArmour director username"
+msgstr ""
+
+#: ./doc/common/tables/heat-debug.xml:8(caption) ./doc/common/tables/trove-debug.xml:8(caption) ./doc/common/tables/keystone-debug.xml:8(caption)
+msgid "Description of configuration options for debug"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml:7(literal)
+msgid "[filter:dlo]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml:18(td)
+msgid "use = egg:swift#dlo"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml:24(td)
+msgid "rate_limit_segments_per_sec = 1"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml:8(caption)
+msgid "Description of configuration options for guestagent"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml:22(td)
+msgid "agent_call_high_timeout = 60"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml:26(td)
+msgid "agent_call_low_timeout = 5"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml:30(td)
+msgid "agent_heartbeat_time = 10"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml:34(td)
+msgid "guest_config = $pybasedir/etc/trove/trove-guestagent.conf.sample"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml:35(td)
+msgid "(StrOpt) Path to guestagent config file."
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml:38(td)
+msgid "guest_id = None"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml:42(td)
+msgid "ignore_dbs = lost+found, mysql, information_schema"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml:46(td)
+msgid "ignore_users = os_admin, root"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml:50(td)
+msgid "mount_options = defaults,noatime"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml:54(td)
+msgid "restore_namespace = trove.guestagent.strategies.restore.mysql_impl"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml:55(td)
+msgid "(StrOpt) Namespace to load restore strategies from."
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml:58(td)
+msgid "storage_namespace = trove.guestagent.strategies.storage.swift"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml:59(td)
+msgid "(StrOpt) Namespace to load the default storage strategy from."
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml:62(td)
+msgid "storage_strategy = SwiftStorage"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml:63(td)
+msgid "(StrOpt) Default strategy to store backups."
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml:66(td) ./doc/common/tables/trove-taskmanager.xml:66(td)
+msgid "usage_sleep_time = 5"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml:67(td) ./doc/common/tables/trove-taskmanager.xml:67(td)
+msgid "(IntOpt) Time to sleep during the check active guest."
+msgstr ""
+
+#: ./doc/common/tables/nova-qpid.xml:23(td) ./doc/common/tables/glance-qpid.xml:23(td) ./doc/common/tables/cinder-rpc.xml:95(td) ./doc/common/tables/nova-rpc_all.xml:63(td) ./doc/common/tables/keystone-qpid.xml:23(td)
+msgid "(IntOpt) Seconds between connection keepalive heartbeats."
+msgstr ""
+
+#: ./doc/common/tables/nova-qpid.xml:27(td) ./doc/common/tables/glance-qpid.xml:27(td) ./doc/common/tables/cinder-rpc.xml:99(td) ./doc/common/tables/nova-rpc_all.xml:67(td) ./doc/common/tables/keystone-qpid.xml:27(td)
+msgid "(StrOpt) Qpid broker hostname."
+msgstr ""
+
+#: ./doc/common/tables/nova-qpid.xml:31(td) ./doc/common/tables/glance-qpid.xml:31(td) ./doc/common/tables/cinder-rpc.xml:103(td) ./doc/common/tables/nova-rpc_all.xml:71(td) ./doc/common/tables/keystone-qpid.xml:31(td)
+msgid "(ListOpt) Qpid HA cluster host:port pairs."
+msgstr ""
+
+#: ./doc/common/tables/nova-qpid.xml:35(td) ./doc/common/tables/glance-qpid.xml:35(td) ./doc/common/tables/cinder-rpc.xml:107(td) ./doc/common/tables/nova-rpc_all.xml:75(td) ./doc/common/tables/keystone-qpid.xml:35(td)
+msgid "(StrOpt) Password for Qpid connection."
+msgstr ""
+
+#: ./doc/common/tables/nova-qpid.xml:39(td) ./doc/common/tables/glance-qpid.xml:39(td) ./doc/common/tables/cinder-rpc.xml:111(td) ./doc/common/tables/nova-rpc_all.xml:79(td) ./doc/common/tables/keystone-qpid.xml:39(td)
+msgid "(IntOpt) Qpid broker port."
+msgstr ""
+
+#: ./doc/common/tables/nova-qpid.xml:43(td) ./doc/common/tables/glance-qpid.xml:43(td) ./doc/common/tables/cinder-rpc.xml:115(td) ./doc/common/tables/nova-rpc_all.xml:83(td) ./doc/common/tables/keystone-qpid.xml:43(td)
+msgid "(StrOpt) Transport to use, either 'tcp' or 'ssl'."
+msgstr ""
+
+#: ./doc/common/tables/nova-qpid.xml:47(td) ./doc/common/tables/glance-qpid.xml:47(td) ./doc/common/tables/cinder-rpc.xml:119(td) ./doc/common/tables/nova-rpc_all.xml:87(td) ./doc/common/tables/keystone-qpid.xml:47(td)
+msgid "(StrOpt) Space separated list of SASL mechanisms to use for auth."
+msgstr ""
+
+#: ./doc/common/tables/nova-qpid.xml:51(td) ./doc/common/tables/glance-qpid.xml:51(td) ./doc/common/tables/cinder-rpc.xml:123(td) ./doc/common/tables/nova-rpc_all.xml:91(td) ./doc/common/tables/keystone-qpid.xml:51(td)
+msgid "(BoolOpt) Whether to disable the Nagle algorithm."
+msgstr ""
+
+#: ./doc/common/tables/nova-qpid.xml:59(td) ./doc/common/tables/glance-qpid.xml:59(td) ./doc/common/tables/cinder-rpc.xml:131(td) ./doc/common/tables/nova-rpc_all.xml:99(td) ./doc/common/tables/keystone-qpid.xml:59(td)
+msgid "(StrOpt) Username for Qpid connection."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_l2pop.xml:8(caption)
+msgid "Description of configuration options for ml2_l2pop"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_l2pop.xml:19(th)
+msgid "[l2pop]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_l2pop.xml:22(td)
+msgid "agent_boot_time = 180"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_l2pop.xml:23(td)
+msgid "(IntOpt) Delay within which agent is expected to update existing ports whent it restarts"
+msgstr ""
+
+#: ./doc/common/tables/glance-zmq.xml:8(caption)
+msgid "Description of configuration options for zmq"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml:8(caption)
+msgid "Description of configuration options for embrane_lb"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml:19(th)
+msgid "[heleoslb]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml:23(td) ./doc/common/tables/neutron-common.xml:220(td)
+msgid "(StrOpt) ESM admin password."
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml:26(td)
+msgid "admin_username = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml:30(td)
+msgid "async_requests = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml:35(td)
+msgid "(StrOpt) Dummy user traffic Security Zone id for LBs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml:43(td)
+msgid "(StrOpt) In band Security Zone id for LBs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml:46(td)
+msgid "lb_flavor = small"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml:47(td)
+msgid "(StrOpt) choose LB image flavor to use, accepted values: small, medium"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml:50(td)
+msgid "lb_image = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml:51(td)
+msgid "(StrOpt) Load Balancer image id (Embrane LB)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml:55(td)
+msgid "(StrOpt) Management Security Zone id for LBs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml:59(td)
+msgid "(StrOpt) Out of band Security Zone id for LBs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml:66(td)
+msgid "sync_interval = 60"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml:67(td)
+msgid "(IntOpt) resource synchronization interval in seconds"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:7(literal)
+msgid "[filter:authtoken]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:18(td)
+msgid "auth_host = keystonehost"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:24(td)
+msgid "auth_protocol = http"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:27(td)
+msgid "auth_uri = http://keystonehost:5000/"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:30(td)
+msgid "admin_tenant_name = service"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:33(td)
+msgid "admin_user = swift"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:36(td)
+msgid "admin_password = password"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:39(td)
+msgid "delay_auth_decision = 1"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:42(td)
+msgid "cache = swift.cache"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:45(td)
+msgid "include_service_catalog = False"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-pipeline-main.xml:18(td)
+msgid "pipeline = healthcheck recon object-server"
+msgstr ""
+
+#: ./doc/common/tables/swift-memcache-memcache.xml:7(literal) ./doc/common/tables/keystone-memcache.xml:19(th)
+msgid "[memcache]"
+msgstr ""
+
+#: ./doc/common/tables/swift-memcache-memcache.xml:7(literal)
+msgid "memcache.conf-sample"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-app-account-server.xml:7(literal)
+msgid "[app:account-server]"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-app-account-server.xml:18(td)
+msgid "use = egg:swift#account"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-app-account-server.xml:21(td)
+msgid "set log_name = account-server"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml:7(literal)
+msgid "[filter:formpost]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml:18(td)
+msgid "use = egg:swift#formpost"
+msgstr ""
+
+#: ./doc/common/tables/trove-compute.xml:22(td)
+msgid "ip_regex = None"
+msgstr ""
+
+#: ./doc/common/tables/trove-compute.xml:26(td)
+msgid "nova_compute_url = http://localhost:8774/v2"
+msgstr ""
+
+#: ./doc/common/tables/trove-compute.xml:30(td)
+msgid "root_grant = ALL"
+msgstr ""
+
+#: ./doc/common/tables/trove-compute.xml:34(td)
+msgid "root_grant_option = True"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:7(literal)
+msgid "[filter:proxy-logging]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:18(td)
+msgid "use = egg:swift#proxy_logging"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:21(td)
+msgid "access_log_name = swift"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:24(td)
+msgid "access_log_facility = LOG_LOCAL0"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:27(td)
+msgid "access_log_level = INFO"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:30(td)
+msgid "access_log_address = /dev/log"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:33(td)
+msgid "access_log_udp_host ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:36(td)
+msgid "access_log_udp_port = 514"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:39(td)
+msgid "access_log_statsd_host = localhost"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:42(td)
+msgid "access_log_statsd_port = 8125"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:45(td)
+msgid "access_log_statsd_default_sample_rate = 1.0"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:48(td)
+msgid "access_log_statsd_sample_rate_factor = 1.0"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:51(td)
+msgid "access_log_statsd_metric_prefix ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:54(td)
+msgid "access_log_headers = false"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:57(td)
+msgid "access_log_headers_only ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:60(td)
+msgid "logged with access_log_headers = True."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:63(td)
+msgid "reveal_sensitive_prefix = 8192"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:63(td)
+msgid "The X-Auth-Token is sensitive data. If revealed to an unauthorised person, they can now make requests against an account until the token expires. Set reveal_sensitive_prefix to the number of characters of the token that are logged. For example reveal_sensitive_prefix = 12 so only first 12 characters of the token are logged. Or, set to 0 to completely remove the token."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:72(td)
+msgid "log_statsd_valid_http_methods = GET,HEAD,POST,PUT,DELETE,COPY,OPTIONS"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_redis.xml:8(caption)
+msgid "Description of configuration options for db_redis"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_redis.xml:19(th)
+msgid "[redis]"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_redis.xml:26(td)
+msgid "mount_point = /var/lib/redis"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_redis.xml:30(td)
+msgid "tcp_ports = 6379"
+msgstr ""
+
+#: ./doc/common/tables/cinder-rpc.xml:38(td)
+msgid "default_timeout = 20"
+msgstr ""
+
+#: ./doc/common/tables/cinder-rpc.xml:39(td)
+msgid "(IntOpt) Default Time Out For CLI operations in minutes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-rpc.xml:234(td)
+msgid "volume_topic = cinder-volume"
+msgstr ""
+
+#: ./doc/common/tables/cinder-rpc.xml:235(td)
+msgid "(StrOpt) the topic volume nodes listen on"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml:7(literal)
+msgid "[realm2]"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml:18(td)
+msgid "key = realm2key"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml:21(td)
+msgid "key2 = realm2key2"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml:24(td)
+msgid "cluster_name3 = https://host3/v1/"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml:27(td)
+msgid "cluster_name4 = https://host4/v1/"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hpmsa.xml:8(caption)
+msgid "Description of configuration options for hpmsa"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hpmsa.xml:22(td)
+msgid "msa_vdisk = OpenStack"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hpmsa.xml:23(td)
+msgid "(StrOpt) The VDisk to use for volume creation."
+msgstr ""
+
+#: ./doc/common/tables/nova-apiv3.xml:8(caption)
+msgid "Description of configuration options for apiv3"
+msgstr ""
+
+#: ./doc/common/tables/nova-apiv3.xml:19(th)
+msgid "[osapi_v3]"
+msgstr ""
+
+#: ./doc/common/tables/nova-apiv3.xml:23(td)
+msgid "(BoolOpt) Whether the V3 API is enabled or not"
+msgstr ""
+
+#: ./doc/common/tables/nova-apiv3.xml:26(td)
+msgid "extensions_blacklist ="
+msgstr ""
+
+#: ./doc/common/tables/nova-apiv3.xml:27(td)
+msgid "(ListOpt) A list of v3 API extensions to never load. Specify the extension aliases here."
+msgstr ""
+
+#: ./doc/common/tables/nova-apiv3.xml:30(td)
+msgid "extensions_whitelist ="
+msgstr ""
+
+#: ./doc/common/tables/nova-apiv3.xml:31(td)
+msgid "(ListOpt) If the list is not empty then a v3 API extension will only be loaded if it exists in this list. Specify the extension aliases here."
+msgstr ""
+
+#: ./doc/common/tables/keystone-oauth.xml:8(caption)
+msgid "Description of configuration options for oauth"
+msgstr ""
+
+#: ./doc/common/tables/keystone-oauth.xml:19(th)
+msgid "[oauth1]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-oauth.xml:22(td)
+msgid "access_token_duration = 86400"
+msgstr ""
+
+#: ./doc/common/tables/keystone-oauth.xml:23(td)
+msgid "(IntOpt) Duration (in seconds) for the OAuth Access Token."
+msgstr ""
+
+#: ./doc/common/tables/keystone-oauth.xml:26(td)
+msgid "driver = keystone.contrib.oauth1.backends.sql.OAuth1"
+msgstr ""
+
+#: ./doc/common/tables/keystone-oauth.xml:27(td) ./doc/common/tables/keystone-credential.xml:23(td)
+msgid "(StrOpt) Keystone Credential backend driver."
+msgstr ""
+
+#: ./doc/common/tables/keystone-oauth.xml:30(td)
+msgid "request_token_duration = 28800"
+msgstr ""
+
+#: ./doc/common/tables/keystone-oauth.xml:31(td)
+msgid "(IntOpt) Duration (in seconds) for the OAuth Request Token."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml:8(caption)
+msgid "Description of configuration options for storage_gpfs"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml:22(td)
+msgid "gpfs_images_dir = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml:23(td)
+msgid "(StrOpt) Specifies the path of the Image service repository in GPFS. Leave undefined if not storing images in GPFS."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml:26(td)
+msgid "gpfs_images_share_mode = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml:27(td)
+msgid "(StrOpt) Specifies the type of image copy to be used. Set this when the Image service repository also uses GPFS so that image files can be transferred efficiently from the Image service to the Block Storage service. There are two valid values: \"copy\" specifies that a full copy of the image is made; \"copy_on_write\" specifies that copy-on-write optimization strategy is used and unmodified blocks of the image file are shared efficiently."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml:30(td)
+msgid "gpfs_max_clone_depth = 0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml:31(td)
+msgid "(IntOpt) Specifies an upper limit on the number of indirections required to reach a specific block due to snapshots or clones. A lengthy chain of copy-on-write snapshots or clones can have a negative impact on performance, but improves space utilization. 0 indicates unlimited clone depth."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml:34(td)
+msgid "gpfs_mount_point_base = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml:35(td)
+msgid "(StrOpt) Specifies the path of the GPFS directory where Block Storage volume and snapshot files are stored."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml:38(td)
+msgid "gpfs_sparse_volumes = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml:39(td)
+msgid "(BoolOpt) Specifies that volumes are created as sparse files which initially consume no space. If set to False, the volume is created as a fully allocated file, in which case, creation may take a significantly longer time."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml:42(td)
+msgid "gpfs_storage_pool = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml:43(td)
+msgid "(StrOpt) Specifies the storage pool that volumes are assigned to. By default, the system storage pool is used."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_vlan.xml:8(caption)
+msgid "Description of configuration options for ml2_vlan"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_vlan.xml:19(th)
+msgid "[ml2_type_vlan]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_vlan.xml:23(td)
+msgid "(ListOpt) List of &lt;physical_network&gt;:&lt;vlan_min&gt;:&lt;vlan_max&gt; or &lt;physical_network&gt; specifying physical_network names usable for VLAN provider and tenant networks, as well as ranges of VLAN tags on each available for allocation to tenant networks."
+msgstr ""
+
+#: ./doc/common/tables/keystone-notification.xml:23(td)
+msgid "(StrOpt) onready allows you to send a notification when the process is ready to serve For example, to have it notify using systemd, one could set shell command: \"onready = systemd-notify --ready\" or a module with notify() method: \"onready = keystone.common.systemd\"."
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml:7(literal)
+msgid "[object-auditor]"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml:18(td)
+msgid "log_name = object-auditor"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml:30(td)
+msgid "files_per_second = 20"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml:30(td)
+msgid "Maximum files audited per second. Should be tuned according to individual system specs. 0 is unlimited."
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml:33(td)
+msgid "bytes_per_second = 10000000"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml:33(td)
+msgid "Maximum bytes audited per second. Should be tuned according to individual system specs. 0 is unlimited. mounted to prevent accidentally writing to the root device process simultaneously (it will actually accept(2) N + 1). Setting this to one (1) will only handle one request at a time, without accepting another request concurrently. By increasing the number of workers to a much higher value, one can reduce the impact of slow file system operations in one request from negatively impacting other requests. underlying filesystem does not support it. to setup custom log handlers. bytes you'd like fallocate to reserve, whether there is space for the given file size or not. This is useful for systems that behave badly when they completely run out of space; you can make the services pretend they're out of space early. container server. For most cases, this should be `egg:swift#container`."
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml:36(td)
+msgid "log_time = 3600"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml:36(td)
+msgid "Frequency of status logs in seconds."
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml:39(td)
+msgid "zero_byte_files_per_second = 50"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml:39(td)
+msgid "Maximum zero byte files audited per second."
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml:45(td)
+msgid "object_size_stats ="
+msgstr ""
+
+#: ./doc/common/tables/trove-zeromq.xml:38(td)
+msgid "rpc_zmq_matchmaker = trove.openstack.common.rpc.matchmaker.MatchMakerLocalhost"
 msgstr ""
 
 #: ./doc/common/tables/neutron-lbaas.xml:8(caption)
@@ -27751,3622 +32111,6 @@ msgstr ""
 msgid "(StrOpt) Swift user name"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_cisco.xml:8(caption)
-msgid "Description of configuration options for ml2_cisco"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_cisco.xml:19(th) ./doc/common/tables/neutron-cisco.xml:119(th)
-msgid "[ml2_cisco]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_cisco.xml:22(td)
-msgid "managed_physical_network = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_cisco.xml:23(td)
-msgid "(StrOpt) The physical network managed by the switches."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml:26(td)
-msgid "dispatcher = ['database']"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml:27(td)
-msgid "(MultiStrOpt) Dispatcher to process data."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml:30(td)
-msgid "rpc_backend = ceilometer.openstack.common.rpc.impl_kombu"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml:66(td)
-msgid "rpc_zmq_matchmaker = ceilometer.openstack.common.rpc.matchmaker.MatchMakerLocalhost"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml:78(th)
-msgid "[publisher]"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml:81(td)
-msgid "metering_secret = change this or be hacked"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml:82(td)
-msgid "(StrOpt) Secret value for signing metering messages."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml:85(th)
-msgid "[publisher_rpc]"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml:88(td)
-msgid "metering_topic = metering"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml:89(td)
-msgid "(StrOpt) The topic that ceilometer uses for metering messages."
-msgstr ""
-
-#: ./doc/common/tables/heat-loadbalancer.xml:8(caption)
-msgid "Description of configuration options for loadbalancer"
-msgstr ""
-
-#: ./doc/common/tables/heat-loadbalancer.xml:22(td)
-msgid "loadbalancer_template = None"
-msgstr ""
-
-#: ./doc/common/tables/heat-loadbalancer.xml:23(td)
-msgid "(StrOpt) Custom template for the built-in loadbalancer nested stack."
-msgstr ""
-
-#: ./doc/common/tables/heat-cloudwatch_api.xml:8(caption)
-msgid "Description of configuration options for cloudwatch_api"
-msgstr ""
-
-#: ./doc/common/tables/heat-cloudwatch_api.xml:22(td) ./doc/common/tables/heat-api.xml:34(td)
-msgid "heat_watch_server_url ="
-msgstr ""
-
-#: ./doc/common/tables/heat-cloudwatch_api.xml:23(td) ./doc/common/tables/heat-api.xml:35(td)
-msgid "(StrOpt) URL of the Heat CloudWatch server."
-msgstr ""
-
-#: ./doc/common/tables/heat-cloudwatch_api.xml:26(th)
-msgid "[heat_api_cloudwatch]"
-msgstr ""
-
-#: ./doc/common/tables/heat-cloudwatch_api.xml:37(td)
-msgid "bind_port = 8003"
-msgstr ""
-
-#: ./doc/common/tables/heat-cloudwatch_api.xml:50(td)
-msgid "(IntOpt) Maximum line size of message headers to be accepted. max_header_line may need to be increased when using large tokens (typically those generated by the Keystone v3 API with big service catalogs.)"
-msgstr ""
-
-#: ./doc/common/tables/nova-pci.xml:8(caption)
-msgid "Description of configuration options for pci"
-msgstr ""
-
-#: ./doc/common/tables/nova-pci.xml:22(td)
-msgid "pci_alias = []"
-msgstr ""
-
-#: ./doc/common/tables/nova-pci.xml:23(td)
-msgid "(MultiStrOpt) An alias for a PCI passthrough device requirement. This allows users to specify the alias in the extra_spec for a flavor, without needing to repeat all the PCI property requirements. For example: pci_alias = { \"name\": \"QuicAssist\", \"product_id\": \"0443\", \"vendor_id\": \"8086\", \"device_type\": \"ACCEL\" } defines an alias for the Intel QuickAssist card. (multi valued)"
-msgstr ""
-
-#: ./doc/common/tables/nova-pci.xml:26(td)
-msgid "pci_passthrough_whitelist = []"
-msgstr ""
-
-#: ./doc/common/tables/nova-pci.xml:27(td)
-msgid "(MultiStrOpt) White list of PCI devices available to VMs. For example: pci_passthrough_whitelist = [{\"vendor_id\": \"8086\", \"product_id\": \"0443\"}]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:7(literal)
-msgid "[filter:proxy-logging]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:18(td)
-msgid "use = egg:swift#proxy_logging"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:21(td)
-msgid "access_log_name = swift"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:24(td)
-msgid "access_log_facility = LOG_LOCAL0"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:27(td)
-msgid "access_log_level = INFO"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:30(td)
-msgid "access_log_address = /dev/log"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:33(td)
-msgid "access_log_udp_host ="
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:36(td)
-msgid "access_log_udp_port = 514"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:39(td)
-msgid "access_log_statsd_host = localhost"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:42(td)
-msgid "access_log_statsd_port = 8125"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:45(td)
-msgid "access_log_statsd_default_sample_rate = 1.0"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:48(td)
-msgid "access_log_statsd_sample_rate_factor = 1.0"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:51(td)
-msgid "access_log_statsd_metric_prefix ="
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:54(td)
-msgid "access_log_headers = false"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:57(td)
-msgid "access_log_headers_only ="
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:60(td)
-msgid "logged with access_log_headers = True."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:63(td)
-msgid "reveal_sensitive_prefix = 8192"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:63(td)
-msgid "The X-Auth-Token is sensitive data. If revealed to an unauthorised person, they can now make requests against an account until the token expires. Set reveal_sensitive_prefix to the number of characters of the token that are logged. For example reveal_sensitive_prefix = 12 so only first 12 characters of the token are logged. Or, set to 0 to completely remove the token."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml:72(td)
-msgid "log_statsd_valid_http_methods = GET,HEAD,POST,PUT,DELETE,COPY,OPTIONS"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_ceilometer.xml:8(caption)
-msgid "Description of configuration options for clients_ceilometer"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_ceilometer.xml:19(th)
-msgid "[clients_ceilometer]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-varmour.xml:8(caption)
-msgid "Description of configuration options for varmour"
-msgstr ""
-
-#: ./doc/common/tables/neutron-varmour.xml:19(th)
-msgid "[vArmour]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-varmour.xml:22(td)
-msgid "director = localhost"
-msgstr ""
-
-#: ./doc/common/tables/neutron-varmour.xml:23(td)
-msgid "(StrOpt) vArmour director ip"
-msgstr ""
-
-#: ./doc/common/tables/neutron-varmour.xml:26(td)
-msgid "director_port = 443"
-msgstr ""
-
-#: ./doc/common/tables/neutron-varmour.xml:27(td)
-msgid "(StrOpt) vArmour director port"
-msgstr ""
-
-#: ./doc/common/tables/neutron-varmour.xml:30(td)
-msgid "password = varmour"
-msgstr ""
-
-#: ./doc/common/tables/neutron-varmour.xml:31(td)
-msgid "(StrOpt) vArmour director password"
-msgstr ""
-
-#: ./doc/common/tables/neutron-varmour.xml:34(td)
-msgid "username = varmour"
-msgstr ""
-
-#: ./doc/common/tables/neutron-varmour.xml:35(td)
-msgid "(StrOpt) vArmour director username"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml:8(caption)
-msgid "Description of configuration options for imagecache"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml:22(td)
-msgid "cleanup_scrubber = False"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml:23(td)
-msgid "(BoolOpt) A boolean that determines if the scrubber should clean up the files it uses for taking data. Only one server in your deployment should be designated the cleanup host."
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml:26(td)
-msgid "cleanup_scrubber_time = 86400"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml:27(td)
-msgid "(IntOpt) Items must have a modified time that is older than this value in order to be candidates for cleanup."
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml:30(td)
-msgid "delayed_delete = False"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml:31(td)
-msgid "(BoolOpt) Turn on/off delayed delete."
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml:34(td)
-msgid "image_cache_dir = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml:35(td)
-msgid "(StrOpt) Base directory that the Image Cache uses."
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml:38(td)
-msgid "image_cache_driver = sqlite"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml:39(td)
-msgid "(StrOpt) The driver to use for image cache management."
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml:42(td)
-msgid "image_cache_max_size = 10737418240"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml:43(td)
-msgid "(IntOpt) The maximum size in bytes that the cache can use."
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml:46(td)
-msgid "image_cache_sqlite_db = cache.db"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml:47(td)
-msgid "(StrOpt) The path to the sqlite file database that will be used for image cache management."
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml:50(td)
-msgid "image_cache_stall_time = 86400"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml:51(td)
-msgid "(IntOpt) The amount of time to let an image remain in the cache without being accessed."
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml:54(td)
-msgid "scrub_time = 0"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml:55(td)
-msgid "(IntOpt) The amount of time in seconds to delay before performing a delete."
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml:58(td)
-msgid "scrubber_datadir = /var/lib/glance/scrubber"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml:59(td)
-msgid "(StrOpt) Directory that the scrubber will use to track information about what to delete. Make sure this is set in glance-api.conf and glance-scrubber.conf."
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml:22(td)
-msgid "max_accepted_volume_size = 5"
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml:23(td)
-msgid "(IntOpt) Default maximum volume size for an instance."
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml:26(td)
-msgid "max_backups_per_user = 50"
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml:27(td)
-msgid "(IntOpt) Default maximum number of backups created by a tenant."
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml:30(td)
-msgid "max_instances_per_user = 5"
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml:31(td)
-msgid "(IntOpt) Default maximum number of instances per tenant."
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml:34(td)
-msgid "max_volumes_per_user = 20"
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml:35(td)
-msgid "(IntOpt) Default maximum volume capacity (in GB) spanning across all trove volumes per tenant"
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml:38(td)
-msgid "quota_driver = trove.quota.quota.DbQuotaDriver"
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml:39(td)
-msgid "(StrOpt) Default driver to use for quota checks."
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-account.xml:7(literal)
-msgid "[account]"
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-account.xml:18(td)
-msgid "max connections = 2"
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-account.xml:27(td)
-msgid "lock file = /var/lock/account.lock"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:8(caption)
-msgid "Description of configuration options for storage"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:22(td)
-msgid "allocated_capacity_weight_multiplier = -1.0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:23(td) ./doc/common/tables/cinder-storage.xml:27(td)
-msgid "(FloatOpt) Multiplier used for weighing volume capacity. Negative numbers mean to stack vs spread."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:26(td)
-msgid "capacity_weight_multiplier = 1.0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:30(td)
-msgid "enabled_backends = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:31(td)
-msgid "(ListOpt) A list of backend names to use. These backend names should be backed by a unique [CONFIG] group with its options"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:34(td)
-msgid "iscsi_helper = tgtadm"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:35(td)
-msgid "(StrOpt) iscsi target user-land tool to use"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:38(td)
-msgid "iscsi_iotype = fileio"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:39(td)
-msgid "(StrOpt) Sets the behavior of the iSCSI target to either perform blockio or fileio optionally, auto can be set and Cinder will autodetect type of backing device"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:42(td)
-msgid "iscsi_ip_address = $my_ip"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:43(td)
-msgid "(StrOpt) The IP address that the iSCSI daemon is listening on"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:46(td)
-msgid "iscsi_num_targets = 100"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:47(td)
-msgid "(IntOpt) The maximum number of iscsi target ids per host"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:50(td)
-msgid "iscsi_port = 3260"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:51(td)
-msgid "(IntOpt) The port that the iSCSI daemon is listening on"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:54(td)
-msgid "iscsi_target_prefix = iqn.2010-10.org.openstack:"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:55(td)
-msgid "(StrOpt) prefix for iscsi volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:58(td)
-msgid "iser_helper = tgtadm"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:59(td)
-msgid "(StrOpt) iser target user-land tool to use"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:62(td)
-msgid "iser_ip_address = $my_ip"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:63(td)
-msgid "(StrOpt) The IP address that the iSER daemon is listening on"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:66(td)
-msgid "iser_num_targets = 100"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:67(td)
-msgid "(IntOpt) The maximum number of iser target ids per host"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:70(td)
-msgid "iser_port = 3260"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:71(td)
-msgid "(IntOpt) The port that the iSER daemon is listening on"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:74(td)
-msgid "iser_target_prefix = iqn.2010-10.org.iser.openstack:"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:75(td)
-msgid "(StrOpt) prefix for iser volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:78(td)
-msgid "max_gigabytes = 10000"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:79(td)
-msgid "(IntOpt) This configure option has been deprecated along with the SimpleScheduler. New scheduler is able to gather capacity information for each host, thus setting the maximum number of volume gigabytes for host is no longer needed. It's safe to remove this configure from cinder.conf."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:82(td)
-msgid "migration_create_volume_timeout_secs = 300"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:83(td)
-msgid "(IntOpt) Timeout for creating the volume to migrate to when performing volume migration (seconds)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:86(td)
-msgid "num_iser_scan_tries = 3"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:87(td)
-msgid "(IntOpt) The maximum number of times to rescan iSER targetto find volume"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:90(td)
-msgid "num_volume_device_scan_tries = 3"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:91(td)
-msgid "(IntOpt) The maximum number of times to rescan targets to find volume"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:94(td)
-msgid "volume_backend_name = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:95(td)
-msgid "(StrOpt) The backend name for a given driver implementation"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:99(td)
-msgid "(StrOpt) Method used to wipe old voumes (valid options are: none, zero, shred)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:102(td)
-msgid "volume_clear_ionice = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:103(td)
-msgid "(StrOpt) The flag to pass to ionice to alter the i/o priority of the process used to zero a volume after deletion, for example \"-c3\" for idle only priority."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:110(td)
-msgid "volume_dd_blocksize = 1M"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:111(td)
-msgid "(StrOpt) The default block size used when copying/clearing volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:114(td)
-msgid "volume_driver = cinder.volume.drivers.lvm.LVMISCSIDriver"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:115(td)
-msgid "(StrOpt) Driver to use for volume creation"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:118(td)
-msgid "volume_manager = cinder.volume.manager.VolumeManager"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:119(td)
-msgid "(StrOpt) full class name for the Manager for volume"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:122(td)
-msgid "volume_service_inithost_offload = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:123(td)
-msgid "(BoolOpt) Offload pending volume delete during volume service startup"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:126(td)
-msgid "volume_usage_audit_period = month"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:127(td)
-msgid "(StrOpt) time period to generate volume usages for. Time period must be hour, day, month or year"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:130(td)
-msgid "volumes_dir = $state_path/volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:131(td)
-msgid "(StrOpt) Volume configuration file storage directory"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml:145(td)
-msgid "max_pool_size = 5"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nas.xml:8(caption)
-msgid "Description of configuration options for nas"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nas.xml:22(td)
-msgid "nas_ip ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-nas.xml:23(td)
-msgid "(StrOpt) IP address or Hostname of NAS system."
-msgstr ""
-
-#: ./doc/common/tables/cinder-nas.xml:26(td)
-msgid "nas_login = admin"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nas.xml:27(td)
-msgid "(StrOpt) User name to connect to NAS system."
-msgstr ""
-
-#: ./doc/common/tables/cinder-nas.xml:30(td)
-msgid "nas_password ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-nas.xml:31(td)
-msgid "(StrOpt) Password to connect to NAS system."
-msgstr ""
-
-#: ./doc/common/tables/cinder-nas.xml:34(td)
-msgid "nas_private_key ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-nas.xml:35(td)
-msgid "(StrOpt) Filename of private key to use for SSH authentication."
-msgstr ""
-
-#: ./doc/common/tables/cinder-nas.xml:38(td)
-msgid "nas_ssh_port = 22"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nas.xml:39(td)
-msgid "(IntOpt) SSH port to use to connect to NAS system."
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml:8(caption) ./doc/common/tables/neutron-vpn.xml:8(caption)
-msgid "Description of configuration options for vpn"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml:22(td)
-msgid "boot_script_template = $pybasedir/nova/cloudpipe/bootscript.template"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml:23(td)
-msgid "(StrOpt) Template for cloudpipe instance boot script"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml:26(td)
-msgid "dmz_cidr ="
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml:27(td)
-msgid "(ListOpt) A list of dmz range that should be accepted"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml:30(td)
-msgid "dmz_mask = 255.255.255.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml:31(td)
-msgid "(StrOpt) Netmask to push into openvpn config"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml:34(td)
-msgid "dmz_net = 10.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml:35(td)
-msgid "(StrOpt) Network to push into openvpn config"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml:38(td)
-msgid "vpn_flavor = m1.tiny"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml:39(td)
-msgid "(StrOpt) Flavor for vpn instances"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml:42(td)
-msgid "vpn_image_id = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml:43(td)
-msgid "(StrOpt) Image ID used when starting up a cloudpipe vpn server"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml:46(td)
-msgid "vpn_ip = $my_ip"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml:47(td)
-msgid "(StrOpt) Public IP for the cloudpipe VPN servers"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml:50(td)
-msgid "vpn_key_suffix = -vpn"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml:51(td)
-msgid "(StrOpt) Suffix to add to project name for vpn key and secgroups"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml:54(td)
-msgid "vpn_start = 1000"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml:55(td)
-msgid "(IntOpt) First Vpn port for private networks"
-msgstr ""
-
-#: ./doc/common/tables/nova-wsgi.xml:23(td)
-msgid "(StrOpt) File name for the paste.deploy config for nova-api"
-msgstr ""
-
-#: ./doc/common/tables/nova-wsgi.xml:26(td) ./doc/common/tables/cinder-common.xml:174(td) ./doc/common/tables/neutron-ssl.xml:22(td)
-msgid "ssl_ca_file = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-wsgi.xml:30(td) ./doc/common/tables/cinder-common.xml:178(td) ./doc/common/tables/neutron-ssl.xml:26(td)
-msgid "ssl_cert_file = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-wsgi.xml:31(td)
-msgid "(StrOpt) SSL certificate of API server"
-msgstr ""
-
-#: ./doc/common/tables/nova-wsgi.xml:34(td) ./doc/common/tables/cinder-common.xml:182(td) ./doc/common/tables/neutron-ssl.xml:30(td)
-msgid "ssl_key_file = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-wsgi.xml:35(td)
-msgid "(StrOpt) SSL private key of API server"
-msgstr ""
-
-#: ./doc/common/tables/nova-wsgi.xml:42(td)
-msgid "wsgi_default_pool_size = 1000"
-msgstr ""
-
-#: ./doc/common/tables/nova-wsgi.xml:43(td)
-msgid "(IntOpt) Size of the pool of greenthreads used by wsgi"
-msgstr ""
-
-#: ./doc/common/tables/nova-wsgi.xml:46(td)
-msgid "wsgi_log_format = %(client_ip)s \"%(request_line)s\" status: %(status_code)s len: %(body_length)s time: %(wall_seconds).7f"
-msgstr ""
-
-#: ./doc/common/tables/nova-wsgi.xml:47(td)
-msgid "(StrOpt) A python format string that is used as the template to generate log lines. The following values can be formatted into it: client_ip, date_time, request_line, status_code, body_length, wall_seconds."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_glusterfs.xml:8(caption)
-msgid "Description of configuration options for storage_glusterfs"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_glusterfs.xml:23(td)
-msgid "(StrOpt) Base dir containing mount points for gluster shares."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_glusterfs.xml:26(td)
-msgid "glusterfs_qcow2_volumes = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_glusterfs.xml:27(td)
-msgid "(BoolOpt) Create volumes as QCOW2 files rather than raw files."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_glusterfs.xml:30(td)
-msgid "glusterfs_shares_config = /etc/cinder/glusterfs_shares"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_glusterfs.xml:31(td)
-msgid "(StrOpt) File with the list of available gluster shares"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_glusterfs.xml:34(td)
-msgid "glusterfs_sparsed_volumes = True"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml:7(literal)
-msgid "[realm1]"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml:7(literal) ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml:7(literal) ./doc/common/tables/swift-container-sync-realms-realm2.xml:7(literal)
-msgid "container-sync-realms.conf-sample"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml:18(td)
-msgid "key = realm1key"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml:21(td)
-msgid "key2 = realm1key2"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml:24(td)
-msgid "cluster_name1 = https://host1/v1/"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml:27(td)
-msgid "cluster_name2 = https://host2/v1/"
-msgstr ""
-
-#: ./doc/common/tables/nova-availabilityzones.xml:8(caption)
-msgid "Description of configuration options for availabilityzones"
-msgstr ""
-
-#: ./doc/common/tables/nova-availabilityzones.xml:22(td)
-msgid "default_availability_zone = nova"
-msgstr ""
-
-#: ./doc/common/tables/nova-availabilityzones.xml:23(td)
-msgid "(StrOpt) Default compute node availability_zone"
-msgstr ""
-
-#: ./doc/common/tables/nova-availabilityzones.xml:26(td)
-msgid "default_schedule_zone = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-availabilityzones.xml:27(td)
-msgid "(StrOpt) Availability zone to use when user doesn't specify one"
-msgstr ""
-
-#: ./doc/common/tables/nova-availabilityzones.xml:30(td)
-msgid "internal_service_availability_zone = internal"
-msgstr ""
-
-#: ./doc/common/tables/nova-availabilityzones.xml:31(td)
-msgid "(StrOpt) The availability_zone to show internal services under"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml:7(literal)
-msgid "[filter:container_sync]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml:18(td)
-msgid "use = egg:swift#container_sync"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml:21(td)
-msgid "allow_full_urls = true"
-msgstr ""
-
-#: ./doc/common/tables/heat-zeromq.xml:38(td)
-msgid "rpc_zmq_matchmaker = heat.openstack.common.rpc.matchmaker.MatchMakerLocalhost"
-msgstr ""
-
-#: ./doc/common/tables/keystone-memcache.xml:8(caption)
-msgid "Description of configuration options for memcache"
-msgstr ""
-
-#: ./doc/common/tables/keystone-memcache.xml:19(th) ./doc/common/tables/swift-memcache-memcache.xml:7(literal)
-msgid "[memcache]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-memcache.xml:22(td)
-msgid "max_compare_and_set_retry = 16"
-msgstr ""
-
-#: ./doc/common/tables/keystone-memcache.xml:23(td)
-msgid "(IntOpt) Number of compare-and-set attempts to make when using compare-and-set in the token memcache back end."
-msgstr ""
-
-#: ./doc/common/tables/keystone-memcache.xml:26(td)
-msgid "servers = localhost:11211"
-msgstr ""
-
-#: ./doc/common/tables/keystone-memcache.xml:27(td)
-msgid "(ListOpt) Memcache servers in the format of \"host:port\""
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml:8(caption)
-msgid "Description of configuration options for vnc"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml:22(td)
-msgid "novncproxy_base_url = http://127.0.0.1:6080/vnc_auto.html"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml:23(td)
-msgid "(StrOpt) Location of VNC console proxy, in the form \"http://127.0.0.1:6080/vnc_auto.html\""
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml:26(td)
-msgid "vnc_enabled = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml:27(td)
-msgid "(BoolOpt) Enable VNC related features"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml:30(td)
-msgid "vnc_keymap = en-us"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml:31(td)
-msgid "(StrOpt) Keymap for VNC"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml:34(td)
-msgid "vncserver_listen = 127.0.0.1"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml:35(td)
-msgid "(StrOpt) IP address on which instance vncservers should listen"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml:38(td)
-msgid "vncserver_proxyclient_address = 127.0.0.1"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml:39(td)
-msgid "(StrOpt) The address to which proxy clients (like nova-xvpvncproxy) should connect"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml:45(td)
-msgid "vnc_port = 5900"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml:46(td)
-msgid "(IntOpt) VNC starting port"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml:49(td)
-msgid "vnc_port_total = 10000"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml:50(td)
-msgid "(IntOpt) Total number of VNC ports"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml:7(literal)
-msgid "[swift-constraints]"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml:7(literal) ./doc/common/tables/swift-swift-swift-hash.xml:7(literal)
-msgid "swift.conf-sample"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml:18(td)
-msgid "max_file_size = 5368709122"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml:18(td)
-msgid "The largest normal object that can be saved in the cluster. This is also the limit on the size of each segment of a large object when using the large object manifest support. This value is set in bytes. Setting it to lower than 1MiB will cause some tests to fail. It is STRONGLY recommended to leave this value at the default (5 * 2**30 + 2)."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml:29(td)
-msgid "max_meta_name_length = 128"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml:29(td)
-msgid "The maximum number of bytes in the utf8 encoding of the name portion of a metadata header."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml:34(td)
-msgid "max_meta_value_length = 256"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml:34(td)
-msgid "The max number of bytes in the utf8 encoding of a metadata value."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml:38(td)
-msgid "max_meta_count = 90"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml:38(td)
-msgid "The maximum number of metadata keys that can be stored on a single account, container, or object."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml:43(td)
-msgid "max_meta_overall_size = 4096"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml:43(td)
-msgid "The maximum number of bytes in the utf8 encoding of the metadata (keys + values)."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml:48(td)
-msgid "max_header_size = 8192"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml:48(td)
-msgid "The maximum number of bytes in the utf8 encoding of each header."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml:52(td)
-msgid "max_object_name_length = 1024"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml:52(td)
-msgid "The maximum number of bytes in the utf8 encoding of an object name."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml:56(td)
-msgid "container_listing_limit = 10000"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml:56(td)
-msgid "The default (and maximum) number of items returned for a container listing request."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml:61(td)
-msgid "account_listing_limit = 10000"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml:61(td)
-msgid "The default (and maximum) number of items returned for an account listing request."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml:65(td)
-msgid "max_account_name_length = 256"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml:65(td)
-msgid "The maximum number of bytes in the utf8 encoding of an account name."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml:69(td)
-msgid "max_container_name_length = 256"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml:69(td)
-msgid "The maximum number of bytes in the utf8 encoding of a container name."
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:8(caption)
-msgid "Description of configuration options for cisco"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:19(th)
-msgid "[CISCO]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:22(td)
-msgid "model_class = neutron.plugins.cisco.models.virt_phy_sw_v2.VirtualPhysicalSwitchModelV2"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:23(td)
-msgid "(StrOpt) Model Class"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:26(td)
-msgid "nexus_driver = neutron.plugins.cisco.test.nexus.fake_nexus_driver.CiscoNEXUSFakeDriver"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:27(td)
-msgid "(StrOpt) Nexus Driver Name"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:30(td)
-msgid "nexus_l3_enable = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:31(td)
-msgid "(BoolOpt) Enable L3 support on the Nexus switches"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:34(td)
-msgid "provider_vlan_auto_create = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:35(td)
-msgid "(BoolOpt) Provider VLANs are automatically created as needed on the Nexus switch"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:38(td)
-msgid "provider_vlan_auto_trunk = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:39(td)
-msgid "(BoolOpt) Provider VLANs are automatically trunked as needed on the ports of the Nexus switch"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:42(td)
-msgid "provider_vlan_name_prefix = p-"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:43(td)
-msgid "(StrOpt) VLAN Name prefix for provider vlans"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:46(td) ./doc/common/tables/neutron-cisco.xml:122(td)
-msgid "svi_round_robin = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:47(td) ./doc/common/tables/neutron-cisco.xml:123(td)
-msgid "(BoolOpt) Distribute SVI interfaces over all switches"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:50(td) ./doc/common/tables/neutron-cisco.xml:126(td)
-msgid "vlan_name_prefix = q-"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:51(td) ./doc/common/tables/neutron-cisco.xml:127(td)
-msgid "(StrOpt) VLAN Name prefix"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:58(td)
-msgid "(StrOpt) N1K Bridge Mappings"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:61(td)
-msgid "default_network_profile = default_network_profile"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:62(td)
-msgid "(StrOpt) N1K default network profile"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:65(td)
-msgid "default_policy_profile = service_profile"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:66(td)
-msgid "(StrOpt) N1K default policy profile"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:69(td)
-msgid "enable_tunneling = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:70(td)
-msgid "(BoolOpt) N1K Enable Tunneling"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:74(td)
-msgid "(StrOpt) N1K Integration Bridge"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:77(td)
-msgid "network_node_policy_profile = dhcp_pp"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:78(td)
-msgid "(StrOpt) N1K policy profile for network node"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:81(td)
-msgid "network_vlan_ranges = vlan:1:4095"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:82(td)
-msgid "(StrOpt) N1K Network VLAN Ranges"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:85(td)
-msgid "poll_duration = 10"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:86(td)
-msgid "(StrOpt) N1K Policy profile polling duration in seconds"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:90(td)
-msgid "(StrOpt) N1K Tenant Network Type"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:94(td)
-msgid "(StrOpt) N1K Tunnel Bridge"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:97(td)
-msgid "vxlan_id_ranges = 5000:10000"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:98(td)
-msgid "(StrOpt) N1K VXLAN ID Ranges"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:101(th)
-msgid "[CISCO_PLUGINS]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:104(td)
-msgid "nexus_plugin = neutron.plugins.cisco.nexus.cisco_nexus_plugin_v2.NexusPlugin"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:105(td)
-msgid "(StrOpt) Nexus Switch to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:108(td)
-msgid "vswitch_plugin = neutron.plugins.openvswitch.ovs_neutron_plugin.OVSNeutronPluginV2"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:109(td)
-msgid "(StrOpt) Virtual Switch to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:112(th)
-msgid "[cisco_csr_ipsec]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:115(td)
-msgid "status_check_interval = 60"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml:116(td)
-msgid "(IntOpt) Status check interval for Cisco CSR IPSec connections"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml:8(caption)
-msgid "Description of configuration options for hyperv"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml:22(td)
-msgid "dynamic_memory_ratio = 1.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml:23(td)
-msgid "(FloatOpt) Enables dynamic memory allocation (ballooning) when set to a value greater than 1. The value expresses the ratio between the total RAM assigned to an instance and its startup RAM amount. For example a ratio of 2.0 for an instance with 1024MB of RAM implies 512MB of RAM allocated at startup"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml:26(td)
-msgid "enable_instance_metrics_collection = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml:27(td)
-msgid "(BoolOpt) Enables metrics collections for an instance by using Hyper-V's metric APIs. Collected data can by retrieved by other apps and services, e.g.: Ceilometer. Requires Hyper-V / Windows Server 2012 and above"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml:34(td)
-msgid "instances_path_share ="
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml:35(td)
-msgid "(StrOpt) The name of a Windows share name mapped to the \"instances_path\" dir and used by the resize feature to copy files to the target host. If left blank, an administrative share will be used, looking for the same \"instances_path\" used locally"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml:38(td)
-msgid "limit_cpu_features = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml:39(td)
-msgid "(BoolOpt) Required for live migration among hosts with different CPU features"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml:42(td)
-msgid "mounted_disk_query_retry_count = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml:43(td)
-msgid "(IntOpt) The number of times to retry checking for a disk mounted via iSCSI."
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml:46(td)
-msgid "mounted_disk_query_retry_interval = 5"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml:47(td)
-msgid "(IntOpt) Interval between checks for a mounted iSCSI disk, in seconds."
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml:50(td)
-msgid "qemu_img_cmd = qemu-img.exe"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml:51(td)
-msgid "(StrOpt) Path of qemu-img command which is used to convert between different image types"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml:54(td)
-msgid "vswitch_name = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml:55(td)
-msgid "(StrOpt) External virtual switch Name, if not provided, the first external virtual switch is used"
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml:8(caption)
-msgid "Description of configuration options for l3_agent"
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml:22(td)
-msgid "enable_metadata_proxy = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml:23(td)
-msgid "(BoolOpt) Allow running metadata proxy."
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml:26(td)
-msgid "external_network_bridge = br-ex"
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml:27(td)
-msgid "(StrOpt) Name of bridge used for external network traffic."
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml:30(td)
-msgid "gateway_external_network_id ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml:31(td)
-msgid "(StrOpt) UUID of external network for routers implemented by the agents."
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml:34(td)
-msgid "handle_internal_only_routers = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml:35(td)
-msgid "(BoolOpt) Agent should implement routers with no gateway"
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml:38(td)
-msgid "router_id ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml:39(td)
-msgid "(StrOpt) If namespaces is disabled, the l3 agent can only configure a router that has the matching router ID."
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml:42(td)
-msgid "send_arp_for_ha = 0"
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml:43(td)
-msgid "(IntOpt) Send this many gratuitous ARPs for HA setup, if less than or equal to 0, the feature is disabled"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-filter-recon.xml:24(td)
-msgid "recon_lock_path = /var/lock"
-msgstr ""
-
-#: ./doc/common/tables/cinder-coraid.xml:8(caption)
-msgid "Description of configuration options for coraid"
-msgstr ""
-
-#: ./doc/common/tables/cinder-coraid.xml:22(td)
-msgid "coraid_esm_address ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-coraid.xml:23(td)
-msgid "(StrOpt) IP address of Coraid ESM"
-msgstr ""
-
-#: ./doc/common/tables/cinder-coraid.xml:26(td)
-msgid "coraid_group = admin"
-msgstr ""
-
-#: ./doc/common/tables/cinder-coraid.xml:27(td)
-msgid "(StrOpt) Name of group on Coraid ESM to which coraid_user belongs (must have admin privilege)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-coraid.xml:30(td)
-msgid "coraid_password = password"
-msgstr ""
-
-#: ./doc/common/tables/cinder-coraid.xml:31(td)
-msgid "(StrOpt) Password to connect to Coraid ESM"
-msgstr ""
-
-#: ./doc/common/tables/cinder-coraid.xml:34(td)
-msgid "coraid_repository_key = coraid_repository"
-msgstr ""
-
-#: ./doc/common/tables/cinder-coraid.xml:35(td)
-msgid "(StrOpt) Volume Type key name to store ESM Repository Name"
-msgstr ""
-
-#: ./doc/common/tables/cinder-coraid.xml:38(td)
-msgid "coraid_user = admin"
-msgstr ""
-
-#: ./doc/common/tables/cinder-coraid.xml:39(td)
-msgid "(StrOpt) User name to connect to Coraid ESM"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-auditor.xml:7(literal)
-msgid "[container-auditor]"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-auditor.xml:18(td)
-msgid "log_name = container-auditor"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-auditor.xml:33(td)
-msgid "containers_per_second = 200"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-auditor.xml:33(td)
-msgid "Maximum containers audited per second. Should be tuned according to individual system specs. 0 is unlimited. mounted to prevent accidentally writing to the root device process simultaneously (it will actually accept(2) N + 1). Setting this to one (1) will only handle one request at a time, without accepting another request concurrently. By increasing the number of workers to a much higher value, one can reduce the impact of slow file system operations in one request from negatively impacting other requests."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml:21(td)
-msgid "set log_name = catch_errors"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml:23(td)
-msgid "(IntOpt) The number of times we retry on failures, e.g., socket error, etc."
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml:26(td)
-msgid "cluster_name = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml:27(td)
-msgid "(MultiStrOpt) Name of a VMware Cluster ComputeResource. Used only if compute_driver is vmwareapi.VMwareVCDriver."
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml:30(td)
-msgid "datastore_regex = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml:31(td)
-msgid "(StrOpt) Regex to match the name of a datastore."
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml:34(td)
-msgid "host_ip = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml:35(td)
-msgid "(StrOpt) Hostname or IP address for connection to VMware ESX/VC host."
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml:38(td)
-msgid "host_password = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml:39(td)
-msgid "(StrOpt) Password for connection to VMware ESX/VC host."
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml:42(td)
-msgid "host_username = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml:43(td)
-msgid "(StrOpt) Username for connection to VMware ESX/VC host."
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml:47(td)
-msgid "(StrOpt) Name of Integration Bridge"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml:50(td)
-msgid "maximum_objects = 100"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml:51(td)
-msgid "(IntOpt) The maximum number of ObjectContent data objects that should be returned in a single result. A positive value will cause the operation to suspend the retrieval when the count of objects reaches the specified maximum. The server may still limit the count to something less than the configured value. Any remaining objects may be retrieved with additional requests."
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml:55(td)
-msgid "(FloatOpt) The interval used for polling of remote tasks."
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml:58(td)
-msgid "use_linked_clone = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml:59(td)
-msgid "(BoolOpt) Whether to use linked clone"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml:62(td)
-msgid "wsdl_location = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml:63(td)
-msgid "(StrOpt) Optional VIM Service WSDL Location e.g http://&lt;server&gt;/vimService.wsdl. Optional over-ride to default location for bug work-arounds"
-msgstr ""
-
-#: ./doc/common/tables/nova-logging.xml:26(td)
-msgid "default_log_levels = amqp=WARN, amqplib=WARN, boto=WARN, qpid=WARN, sqlalchemy=WARN, suds=INFO, oslo.messaging=INFO, iso8601=WARN"
-msgstr ""
-
-#: ./doc/common/tables/nova-logging.xml:34(td) ./doc/common/tables/cinder-common.xml:54(td)
-msgid "fatal_exception_format_errors = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-logging.xml:35(td)
-msgid "(BoolOpt) Make exception message format errors fatal"
-msgstr ""
-
-#: ./doc/common/tables/nova-logging.xml:66(td)
-msgid "logging_context_format_string = %(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [%(request_id)s %(user)s %(tenant)s] %(instance)s%(message)s"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:8(caption)
-msgid "Description of configuration options for xen"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:22(td)
-msgid "console_driver = nova.console.xvp.XVPConsoleProxy"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:23(td)
-msgid "(StrOpt) Driver to use for the console proxy"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:26(td)
-msgid "console_vmrc_error_retries = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:27(td)
-msgid "(IntOpt) Number of retries for retrieving VMRC information"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:30(td)
-msgid "console_vmrc_port = 443"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:31(td)
-msgid "(IntOpt) Port for VMware VMRC connections"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:34(td)
-msgid "console_xvp_conf = /etc/xvp.conf"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:35(td)
-msgid "(StrOpt) Generated XVP conf file"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:38(td)
-msgid "console_xvp_conf_template = $pybasedir/nova/console/xvp.conf.template"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:39(td)
-msgid "(StrOpt) XVP conf template"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:42(td)
-msgid "console_xvp_log = /var/log/xvp.log"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:43(td)
-msgid "(StrOpt) XVP log file"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:46(td)
-msgid "console_xvp_multiplex_port = 5900"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:47(td)
-msgid "(IntOpt) Port for XVP to multiplex VNC connections on"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:50(td)
-msgid "console_xvp_pid = /var/run/xvp.pid"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:51(td)
-msgid "(StrOpt) XVP master process pid file"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:54(td)
-msgid "stub_compute = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:55(td)
-msgid "(BoolOpt) Stub calls to compute worker for tests"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:61(td)
-msgid "xen_hvmloader_path = /usr/lib/xen/boot/hvmloader"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:62(td)
-msgid "(StrOpt) Location where the Xen hvmloader is kept"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:68(td)
-msgid "agent_path = usr/sbin/xe-update-networking"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:69(td)
-msgid "(StrOpt) Specifies the path in which the XenAPI guest agent should be located. If the agent is present, network configuration is not injected into the image. Used if compute_driver=xenapi.XenAPIDriver and flat_injected=True"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:72(td)
-msgid "agent_resetnetwork_timeout = 60"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:73(td)
-msgid "(IntOpt) Number of seconds to wait for agent reply to resetnetwork request"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:76(td)
-msgid "agent_timeout = 30"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:77(td)
-msgid "(IntOpt) Number of seconds to wait for agent reply"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:80(td)
-msgid "agent_version_timeout = 300"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:81(td)
-msgid "(IntOpt) Number of seconds to wait for agent to be fully operational"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:84(td)
-msgid "cache_images = all"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:85(td)
-msgid "(StrOpt) Cache glance images locally. `all` will cache all images, `some` will only cache images that have the image_property `cache_in_nova=True`, and `none` turns off caching entirely"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:88(td)
-msgid "check_host = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:89(td)
-msgid "(BoolOpt) Ensure compute service is running on host XenAPI connects to."
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:92(td)
-msgid "connection_concurrent = 5"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:93(td)
-msgid "(IntOpt) Maximum number of concurrent XenAPI connections. Used only if compute_driver=xenapi.XenAPIDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:96(td)
-msgid "connection_password = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:97(td)
-msgid "(StrOpt) Password for connection to XenServer/Xen Cloud Platform. Used only if compute_driver=xenapi.XenAPIDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:100(td)
-msgid "connection_url = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:101(td)
-msgid "(StrOpt) URL for connection to XenServer/Xen Cloud Platform. A special value of unix://local can be used to connect to the local unix socket. Required if compute_driver=xenapi.XenAPIDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:104(td)
-msgid "connection_username = root"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:105(td)
-msgid "(StrOpt) Username for connection to XenServer/Xen Cloud Platform. Used only if compute_driver=xenapi.XenAPIDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:108(td)
-msgid "default_os_type = linux"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:109(td)
-msgid "(StrOpt) Default OS type"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:112(td)
-msgid "disable_agent = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:113(td)
-msgid "(BoolOpt) Disables the use of the XenAPI agent in any image regardless of what image properties are present."
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:116(td)
-msgid "image_compression_level = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:117(td)
-msgid "(IntOpt) Compression level for images, e.g., 9 for gzip -9. Range is 1-9, 9 being most compressed but most CPU intensive on dom0."
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:120(td)
-msgid "image_upload_handler = nova.virt.xenapi.image.glance.GlanceStore"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:121(td)
-msgid "(StrOpt) Dom0 plugin driver used to handle image uploads."
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:124(td)
-msgid "introduce_vdi_retry_wait = 20"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:125(td)
-msgid "(IntOpt) Number of seconds to wait for an SR to settle if the VDI does not exist when first introduced"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:128(td)
-msgid "ipxe_boot_menu_url = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:129(td)
-msgid "(StrOpt) URL to the iPXE boot menu"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:132(td)
-msgid "ipxe_mkisofs_cmd = mkisofs"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:133(td) ./doc/common/tables/nova-configdrive.xml:39(td)
-msgid "(StrOpt) Name and optionally path of the tool used for ISO image creation"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:136(td)
-msgid "ipxe_network_name = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:137(td)
-msgid "(StrOpt) Name of network to use for booting iPXE ISOs"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:140(td)
-msgid "iqn_prefix = iqn.2010-10.org.openstack"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:141(td)
-msgid "(StrOpt) IQN Prefix"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:144(td)
-msgid "login_timeout = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:145(td)
-msgid "(IntOpt) Timeout in seconds for XenAPI login."
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:148(td)
-msgid "max_kernel_ramdisk_size = 16777216"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:149(td)
-msgid "(IntOpt) Maximum size in bytes of kernel or ramdisk images"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:152(td)
-msgid "num_vbd_unplug_retries = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:153(td)
-msgid "(IntOpt) Maximum number of retries to unplug VBD"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:156(td)
-msgid "ovs_integration_bridge = xapi1"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:160(td)
-msgid "remap_vbd_dev = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:161(td)
-msgid "(BoolOpt) Used to enable the remapping of VBD dev (Works around an issue in Ubuntu Maverick)"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:164(td)
-msgid "remap_vbd_dev_prefix = sd"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:165(td)
-msgid "(StrOpt) Specify prefix to remap VBD dev to (ex. /dev/xvdb -&gt; /dev/sdb)"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:168(td)
-msgid "running_timeout = 60"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:169(td)
-msgid "(IntOpt) Number of seconds to wait for instance to go to running state"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:172(td)
-msgid "sparse_copy = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:173(td)
-msgid "(BoolOpt) Whether to use sparse_copy for copying data on a resize down (False will use standard dd). This speeds up resizes down considerably since large runs of zeros won't have to be rsynced"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:176(td)
-msgid "sr_base_path = /var/run/sr-mount"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:177(td) ./doc/common/tables/cinder-storage_xen.xml:43(td)
-msgid "(StrOpt) Base path to the storage repository"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:180(td)
-msgid "sr_matching_filter = default-sr:true"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:181(td)
-msgid "(StrOpt) Filter for finding the SR to be used to install guest instances on. To use the Local Storage in default XenServer/XCP installations set this flag to other-config:i18n-key=local-storage. To select an SR with a different matching criteria, you could set it to other-config:my_favorite_sr=true. On the other hand, to fall back on the Default SR, as displayed by XenCenter, set this flag to: default-sr:true"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:184(td)
-msgid "target_host = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:185(td)
-msgid "(StrOpt) The iSCSI Target Host"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:188(td)
-msgid "target_port = 3260"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:189(td)
-msgid "(StrOpt) The iSCSI Target Port, default is port 3260"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:192(td)
-msgid "torrent_base_url = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:193(td)
-msgid "(StrOpt) Base URL for torrent files."
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:196(td)
-msgid "torrent_download_stall_cutoff = 600"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:197(td)
-msgid "(IntOpt) Number of seconds a download can remain at the same progress percentage w/o being considered a stall"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:200(td)
-msgid "torrent_images = none"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:201(td)
-msgid "(StrOpt) Whether or not to download images via Bit Torrent (all|some|none)."
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:204(td)
-msgid "torrent_listen_port_end = 6891"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:205(td)
-msgid "(IntOpt) End of port range to listen on"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:208(td)
-msgid "torrent_listen_port_start = 6881"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:209(td)
-msgid "(IntOpt) Beginning of port range to listen on"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:212(td)
-msgid "torrent_max_last_accessed = 86400"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:213(td)
-msgid "(IntOpt) Cached torrent files not accessed within this number of seconds can be reaped"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:216(td)
-msgid "torrent_max_seeder_processes_per_host = 1"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:217(td)
-msgid "(IntOpt) Maximum number of seeder processes to run concurrently within a given dom0. (-1 = no limit)"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:220(td)
-msgid "torrent_seed_chance = 1.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:221(td)
-msgid "(FloatOpt) Probability that peer will become a seeder. (1.0 = 100%)"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:224(td)
-msgid "torrent_seed_duration = 3600"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:225(td)
-msgid "(IntOpt) Number of seconds after downloading an image via BitTorrent that it should be seeded for other peers."
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:228(td)
-msgid "use_agent_default = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:229(td)
-msgid "(BoolOpt) Determines if the XenAPI agent should be used when the image used does not contain a hint to declare if the agent is present or not. The hint is a glance property \"xenapi_use_agent\" that has the value \"True\" or \"False\". Note that waiting for the agent when it is not present will significantly increase server boot times."
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:232(td)
-msgid "use_join_force = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:233(td)
-msgid "(BoolOpt) To use for hosts with different CPUs"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:236(td)
-msgid "vhd_coalesce_max_attempts = 20"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:237(td)
-msgid "(IntOpt) Max number of times to poll for VHD to coalesce. Used only if compute_driver=xenapi.XenAPIDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:240(td)
-msgid "vhd_coalesce_poll_interval = 5.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml:241(td)
-msgid "(FloatOpt) The interval used for polling of coalescing vhds. Used only if compute_driver=xenapi.XenAPIDriver"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml:8(caption)
-msgid "Description of configuration options for collector"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml:22(td)
-msgid "collector_workers = 1"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml:23(td)
-msgid "(IntOpt) Number of workers for collector service. A single collector is enabled by default."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml:26(th)
-msgid "[collector]"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml:29(td)
-msgid "udp_address = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml:30(td)
-msgid "(StrOpt) Address to which the UDP socket is bound. Set to an empty string to disable."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml:33(td)
-msgid "udp_port = 4952"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml:34(td)
-msgid "(IntOpt) Port to which the UDP socket is bound."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml:37(th)
-msgid "[dispatcher_file]"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml:40(td)
-msgid "backup_count = 0"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml:41(td)
-msgid "(IntOpt) The max number of the files to keep."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml:44(td)
-msgid "file_path = None"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml:45(td)
-msgid "(StrOpt) Name and the location of the file to record meters."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml:48(td)
-msgid "max_bytes = 0"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml:49(td)
-msgid "(IntOpt) The max size of the file."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml:7(literal)
-msgid "[filter:list-endpoints]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml:18(td)
-msgid "use = egg:swift#list_endpoints"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml:21(td)
-msgid "list_endpoints_path = /endpoints/"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml:22(td)
-msgid "keystone_ec2_cafile = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml:23(td)
-msgid "(StrOpt) A PEM encoded certificate authority to use when verifying HTTPS connections. Defaults to the system CAs."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml:26(td)
-msgid "keystone_ec2_certfile = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml:27(td)
-msgid "(StrOpt) Client certificate key filename. Required if EC2 server requires client certificate."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml:30(td)
-msgid "keystone_ec2_insecure = False"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml:31(td)
-msgid "(BoolOpt) Disable SSL certificate verification."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml:34(td)
-msgid "keystone_ec2_keyfile = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml:35(td)
-msgid "(StrOpt) Required if EC2 server requires client certificate."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml:42(th)
-msgid "[ec2]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml:45(td)
-msgid "driver = keystone.contrib.ec2.backends.kvs.Ec2"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml:46(td)
-msgid "(StrOpt) Keystone EC2Credential backend driver."
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml:8(caption) ./doc/common/tables/ceilometer-auth.xml:8(caption) ./doc/common/tables/cinder-auth.xml:8(caption)
-msgid "Description of configuration options for auth"
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml:19(th)
-msgid "[auth]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml:22(td)
-msgid "external = keystone.auth.plugins.external.DefaultDomain"
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml:23(td)
-msgid "(StrOpt) The external (REMOTE_USER) auth plugin module."
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml:26(td)
-msgid "methods = external, password, token"
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml:27(td)
-msgid "(ListOpt) Default auth methods."
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml:30(td)
-msgid "password = keystone.auth.plugins.password.Password"
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml:31(td)
-msgid "(StrOpt) The password auth plugin module."
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml:34(td)
-msgid "token = keystone.auth.plugins.token.Token"
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml:35(td)
-msgid "(StrOpt) The token auth plugin module."
-msgstr ""
-
-#: ./doc/common/tables/swift-memcache-memcache.xml:7(literal)
-msgid "memcache.conf-sample"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:7(literal)
-msgid "[filter:keystoneauth]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:18(td)
-msgid "use = egg:swift#keystoneauth"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:21(td)
-msgid "operator_roles = admin, swiftoperator"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml:24(td)
-msgid "reseller_admin_role = ResellerAdmin"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2.xml:8(caption)
-msgid "Description of configuration options for ml2"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2.xml:19(th)
-msgid "[ml2]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2.xml:22(td)
-msgid "mechanism_drivers ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2.xml:23(td)
-msgid "(ListOpt) An ordered list of networking mechanism driver entrypoints to be loaded from the neutron.ml2.mechanism_drivers namespace."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2.xml:26(td)
-msgid "tenant_network_types = local"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2.xml:27(td)
-msgid "(ListOpt) Ordered list of network_types to allocate as tenant networks."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2.xml:30(td)
-msgid "type_drivers = local, flat, vlan, gre, vxlan"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2.xml:31(td)
-msgid "(ListOpt) List of network type driver entrypoints to be loaded from the neutron.ml2.type_drivers namespace."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml:23(td)
-msgid "(BoolOpt) Deploy the deprecated v1 API."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml:27(td)
-msgid "(IntOpt) The maximum body size per request, in bytes"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml:30(td)
-msgid "pipeline_cfg_file = pipeline.yaml"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml:31(td)
-msgid "(StrOpt) Configuration file for pipeline definition."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml:35(td) ./doc/common/tables/heat-api.xml:43(td) ./doc/common/tables/keystone-policy.xml:23(td)
-msgid "(StrOpt) Rule enforced when requested rule is not found"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml:39(td) ./doc/common/tables/heat-api.xml:47(td) ./doc/common/tables/keystone-policy.xml:27(td)
-msgid "(StrOpt) JSON file containing policy"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml:42(td)
-msgid "reserved_metadata_length = 256"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml:43(td)
-msgid "(IntOpt) Limit on length of reserved metadata values."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml:46(td)
-msgid "reserved_metadata_namespace = metering."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml:47(td)
-msgid "(ListOpt) List of metadata prefixes reserved for metering use."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml:50(th)
-msgid "[api]"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml:53(td) ./doc/common/tables/trove-rpc.xml:26(td)
-msgid "host = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml:54(td)
-msgid "(StrOpt) The listen IP for the ceilometer API server."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml:57(td)
-msgid "port = 8777"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml:58(td)
-msgid "(IntOpt) The port for the ceilometer API server."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_trove.xml:8(caption)
-msgid "Description of configuration options for clients_trove"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_trove.xml:19(th)
-msgid "[clients_trove]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:7(literal)
-msgid "[filter:gatekeeper]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:18(td)
-msgid "use = egg:swift#gatekeeper"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml:21(td)
-msgid "set log_name = gatekeeper"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:8(caption)
-msgid "Description of configuration options for netapp_7mode_nfs"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:22(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:22(td)
-msgid "expiry_thres_minutes = 720"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:23(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:23(td)
-msgid "(IntOpt) This option specifies the threshold for last access time for images in the NFS image cache. When a cache cleaning cycle begins, images in the cache that have not been accessed in the last M minutes, where M is the value of this parameter, will be deleted from the cache to create free space on the NFS share."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:54(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:62(td)
-msgid "thres_avl_size_perc_start = 20"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:55(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:63(td)
-msgid "(IntOpt) If the percentage of available space for an NFS share has dropped below the value specified by this option, the NFS image cache will be cleaned."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:58(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:66(td)
-msgid "thres_avl_size_perc_stop = 60"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml:59(td) ./doc/common/tables/cinder-netapp_cdot_nfs.xml:67(td)
-msgid "(IntOpt) When the percentage of available space on an NFS share has reached the percentage specified by this option, the driver will stop clearing files from the NFS image cache that have not been accessed in the last M minutes, where M is the value of the expiry_thres_minutes configuration option."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:22(td)
-msgid "allow_additional_image_properties = True"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:23(td)
-msgid "(BoolOpt) Whether to allow users to specify image properties beyond what the image schema provides"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:26(td)
-msgid "api_limit_max = 1000"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:27(td)
-msgid "(IntOpt) Maximum permissible number of items that could be returned by a request"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:31(td)
-msgid "(IntOpt) The backlog value that will be used when creating the TCP listener socket."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:38(td)
-msgid "bind_port = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:42(td)
-msgid "data_api = glance.db.sqlalchemy.api"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:43(td)
-msgid "(StrOpt) Python module path of data access API"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:50(td)
-msgid "image_location_quota = 10"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:51(td)
-msgid "(IntOpt) Maximum number of locations allowed on an image. Negative values evaluate to unlimited."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:54(td)
-msgid "image_member_quota = 128"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:55(td)
-msgid "(IntOpt) Maximum number of image members per image. Negative values evaluate to unlimited."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:58(td)
-msgid "image_property_quota = 128"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:59(td)
-msgid "(IntOpt) Maximum number of properties allowed on an image. Negative values evaluate to unlimited."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:62(td)
-msgid "image_tag_quota = 128"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:63(td)
-msgid "(IntOpt) Maximum number of tags allowed on an image. Negative values evaluate to unlimited."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:66(td)
-msgid "limit_param_default = 25"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:67(td)
-msgid "(IntOpt) Default value for the number of items returned by a request if not specified explicitly in the request"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:74(td)
-msgid "metadata_encryption_key = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:75(td)
-msgid "(StrOpt) Key used for encrypting sensitive metadata while talking to the registry or database."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:78(td)
-msgid "notifier_strategy = default"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:79(td)
-msgid "(StrOpt) Notifications can be sent when images are create, updated or deleted. There are three methods of sending notifications, logging (via the log_file directive), rabbit (via a rabbitmq queue), qpid (via a Qpid message queue), or noop (no notifications sent, the default). (DEPRECATED)"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:83(td)
-msgid "(StrOpt) Region name of this node."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:86(td)
-msgid "property_protection_file = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:87(td)
-msgid "(StrOpt) The location of the property protection file."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:90(td)
-msgid "property_protection_rule_format = roles"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:91(td)
-msgid "(StrOpt) This config value indicates whether \"roles\" or \"policies\" are used in the property protection file."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:94(td)
-msgid "show_image_direct_url = False"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:95(td)
-msgid "(BoolOpt) Whether to include the backend image storage location in image properties. Revealing storage location can be a security risk, so use this setting with caution!"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:98(td)
-msgid "user_storage_quota = 0"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:99(td)
-msgid "(IntOpt) Set a system wide quota for every user. This value is the total number of bytes that a user can use across all storage systems. A value of 0 means unlimited."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:102(td)
-msgid "workers = 1"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:103(td)
-msgid "(IntOpt) The number of child process workers that will be created to service API requests."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:106(th)
-msgid "[image_format]"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:109(td)
-msgid "container_formats = ami, ari, aki, bare, ovf, ova"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:110(td)
-msgid "(ListOpt) Supported values for the 'container_format' image attribute"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:113(td)
-msgid "disk_formats = ami, ari, aki, vhd, vmdk, raw, qcow2, vdi, iso"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:114(td)
-msgid "(ListOpt) Supported values for the 'disk_format' image attribute"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:117(th)
-msgid "[task]"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:120(td)
-msgid "task_time_to_live = 48"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml:121(td)
-msgid "(IntOpt) Time in hours for which a task lives after, either succeeding or failing"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:8(caption)
-msgid "Description of configuration options for network"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:22(td)
-msgid "allow_same_net_traffic = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:23(td)
-msgid "(BoolOpt) Whether to allow network traffic from same network"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:26(td)
-msgid "auto_assign_floating_ip = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:27(td)
-msgid "(BoolOpt) Autoassigning floating IP to VM"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:30(td)
-msgid "cnt_vpn_clients = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:31(td)
-msgid "(IntOpt) Number of addresses reserved for vpn clients"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:34(td)
-msgid "create_unique_mac_address_attempts = 5"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:35(td)
-msgid "(IntOpt) Number of attempts to create unique mac address"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:38(td)
-msgid "default_access_ip_network_name = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:39(td)
-msgid "(StrOpt) Name of network to use to set access IPs for instances"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:42(td)
-msgid "default_floating_pool = nova"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:43(td)
-msgid "(StrOpt) Default pool for floating IPs"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:46(td)
-msgid "defer_iptables_apply = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:47(td)
-msgid "(BoolOpt) Whether to batch up the application of IPTables rules during a host restart and apply all at the end of the init phase"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:50(td)
-msgid "dhcp_domain = novalocal"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:54(td)
-msgid "dhcp_lease_time = 120"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:55(td)
-msgid "(IntOpt) Lifetime of a DHCP lease in seconds"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:58(td)
-msgid "dhcpbridge = $bindir/nova-dhcpbridge"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:59(td)
-msgid "(StrOpt) Location of nova-dhcpbridge"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:62(td)
-msgid "dhcpbridge_flagfile = ['/etc/nova/nova-dhcpbridge.conf']"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:63(td)
-msgid "(MultiStrOpt) Location of flagfiles for dhcpbridge"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:66(td)
-msgid "dns_server = []"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:67(td)
-msgid "(MultiStrOpt) If set, uses specific DNS server for dnsmasq. Can be specified multiple times."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:70(td)
-msgid "dns_update_periodic_interval = -1"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:71(td)
-msgid "(IntOpt) Number of seconds to wait between runs of updates to DNS entries."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:79(td)
-msgid "(StrOpt) Firewall driver (defaults to hypervisor specific iptables driver)"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:82(td)
-msgid "fixed_ip_disassociate_timeout = 600"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:83(td)
-msgid "(IntOpt) Seconds after which a deallocated IP is disassociated"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:86(td)
-msgid "flat_injected = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:87(td)
-msgid "(BoolOpt) Whether to attempt to inject network setup into guest"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:90(td)
-msgid "flat_interface = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:91(td)
-msgid "(StrOpt) FlatDhcp will bridge into this interface if set"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:94(td)
-msgid "flat_network_bridge = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:95(td)
-msgid "(StrOpt) Bridge for simple network instances"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:98(td)
-msgid "flat_network_dns = 8.8.4.4"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:99(td)
-msgid "(StrOpt) DNS server for simple network"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:102(td)
-msgid "floating_ip_dns_manager = nova.network.noop_dns_driver.NoopDNSDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:103(td)
-msgid "(StrOpt) Full class name for the DNS Manager for floating IPs"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:106(td)
-msgid "force_dhcp_release = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:107(td)
-msgid "(BoolOpt) If True, send a dhcp release on instance termination"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:110(td)
-msgid "force_snat_range = []"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:111(td)
-msgid "(MultiStrOpt) Traffic to this range will always be snatted to the fallback ip, even if it would normally be bridged out of the node. Can be specified multiple times."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:114(td)
-msgid "forward_bridge_interface = ['all']"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:115(td)
-msgid "(MultiStrOpt) An interface that bridges can forward to. If this is set to all then all traffic will be forwarded. Can be specified multiple times."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:118(td)
-msgid "gateway = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:119(td)
-msgid "(StrOpt) Default IPv4 gateway"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:122(td)
-msgid "injected_network_template = $pybasedir/nova/virt/interfaces.template"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:123(td)
-msgid "(StrOpt) Template file for injected network"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:126(td)
-msgid "instance_dns_domain ="
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:127(td)
-msgid "(StrOpt) Full class name for the DNS Zone for instance IPs"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:130(td)
-msgid "instance_dns_manager = nova.network.noop_dns_driver.NoopDNSDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:131(td)
-msgid "(StrOpt) Full class name for the DNS Manager for instance IPs"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:134(td)
-msgid "iptables_bottom_regex ="
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:135(td)
-msgid "(StrOpt) Regular expression to match iptables rule that should always be on the bottom."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:138(td)
-msgid "iptables_drop_action = DROP"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:139(td)
-msgid "(StrOpt) The table that iptables to jump to when a packet is to be dropped."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:142(td)
-msgid "iptables_top_regex ="
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:143(td)
-msgid "(StrOpt) Regular expression to match iptables rule that should always be on the top."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:146(td)
-msgid "l3_lib = nova.network.l3.LinuxNetL3"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:147(td)
-msgid "(StrOpt) Indicates underlying L3 management library"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:150(td)
-msgid "linuxnet_interface_driver = nova.network.linux_net.LinuxBridgeInterfaceDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:151(td)
-msgid "(StrOpt) Driver used to create ethernet devices."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:154(td)
-msgid "linuxnet_ovs_integration_bridge = br-int"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:155(td)
-msgid "(StrOpt) Name of Open vSwitch bridge used with linuxnet"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:158(td)
-msgid "multi_host = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:159(td)
-msgid "(BoolOpt) Default value for multi_host in networks. Also, if set, some rpc network calls will be sent directly to host."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:162(td)
-msgid "network_allocate_retries = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:163(td)
-msgid "(IntOpt) Number of times to retry network allocation on failures"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:166(td)
-msgid "network_api_class = nova.network.api.API"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:167(td)
-msgid "(StrOpt) The full class name of the network API class to use"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:170(td) ./doc/common/tables/neutron-agent.xml:26(td)
-msgid "network_device_mtu = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:171(td)
-msgid "(IntOpt) MTU setting for network interface"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:174(td)
-msgid "network_driver = nova.network.linux_net"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:175(td)
-msgid "(StrOpt) Driver to use for network creation"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:178(td)
-msgid "network_manager = nova.network.manager.VlanManager"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:179(td)
-msgid "(StrOpt) Full class name for the Manager for network"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:182(td)
-msgid "network_size = 256"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:183(td)
-msgid "(IntOpt) Number of addresses in each private subnet"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:186(td)
-msgid "network_topic = network"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:187(td)
-msgid "(StrOpt) The topic network nodes listen on"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:190(td)
-msgid "networks_path = $state_path/networks"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:191(td)
-msgid "(StrOpt) Location to keep network config files"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:194(td)
-msgid "num_networks = 1"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:195(td)
-msgid "(IntOpt) Number of networks to support"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:198(td)
-msgid "ovs_vsctl_timeout = 120"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:199(td)
-msgid "(IntOpt) Amount of time, in seconds, that ovs_vsctl should wait for a response from the database. 0 is to wait forever."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:202(td)
-msgid "public_interface = eth0"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:203(td)
-msgid "(StrOpt) Interface for public IP addresses"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:206(td)
-msgid "routing_source_ip = $my_ip"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:207(td)
-msgid "(StrOpt) Public IP of network host"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:210(td)
-msgid "security_group_api = nova"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:211(td)
-msgid "(StrOpt) The full class name of the security API class"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:214(td)
-msgid "send_arp_for_ha = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:215(td)
-msgid "(BoolOpt) Send gratuitous ARPs for HA setup"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:218(td)
-msgid "send_arp_for_ha_count = 3"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:219(td)
-msgid "(IntOpt) Send this many gratuitous ARPs for HA setup"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:222(td)
-msgid "share_dhcp_address = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:223(td)
-msgid "(BoolOpt) If True in multi_host mode, all compute hosts share the same dhcp address. The same IP address used for DHCP will be added on each nova-network node which is only visible to the vms on the same host."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:226(td)
-msgid "teardown_unused_network_gateway = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:227(td)
-msgid "(BoolOpt) If True, unused gateway devices (VLAN and bridge) are deleted in VLAN network mode with multi hosted networks"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:230(td)
-msgid "update_dns_entries = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:231(td)
-msgid "(BoolOpt) If True, when a DNS entry must be updated, it sends a fanout cast to all network hosts to update their DNS entries in multi host mode"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:234(td)
-msgid "use_network_dns_servers = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:235(td)
-msgid "(BoolOpt) If set, uses the dns1 and dns2 from the network ref. as dns servers."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:238(td)
-msgid "use_neutron_default_nets = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:239(td)
-msgid "(StrOpt) Control for checking for default networks"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:242(td)
-msgid "use_single_default_gateway = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:243(td)
-msgid "(BoolOpt) Use single default gateway. Only first nic of vm will get default gateway from dhcp server"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:246(td)
-msgid "vlan_interface = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:247(td)
-msgid "(StrOpt) VLANs will bridge into this interface if set"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:250(td)
-msgid "vlan_start = 100"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:251(td)
-msgid "(IntOpt) First VLAN for private networks"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:257(td)
-msgid "vlan_interface = vmnic0"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml:258(td)
-msgid "(StrOpt) Physical ethernet adapter name for vlan networking"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scality.xml:8(caption)
-msgid "Description of configuration options for scality"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scality.xml:30(td)
-msgid "scality_sofs_volume_dir = cinder/volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scality.xml:31(td)
-msgid "(StrOpt) Path from Scality SOFS root to volume dir"
-msgstr ""
-
-#: ./doc/common/tables/neutron-notifier.xml:8(caption)
-msgid "Description of configuration options for notifier"
-msgstr ""
-
-#: ./doc/common/tables/neutron-notifier.xml:26(td) ./doc/common/tables/trove-common.xml:50(td)
-msgid "default_publisher_id = $host"
-msgstr ""
-
-#: ./doc/common/tables/neutron-notifier.xml:31(td) ./doc/common/tables/heat-amqp.xml:51(td) ./doc/common/tables/ceilometer-amqp.xml:31(td) ./doc/common/tables/trove-amqp.xml:59(td)
-msgid "(MultiStrOpt) Driver or drivers to handle sending notifications"
-msgstr ""
-
-#: ./doc/common/tables/neutron-notifier.xml:35(td) ./doc/common/tables/trove-amqp.xml:67(td)
-msgid "(ListOpt) AMQP topic used for openstack notifications"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:22(td)
-msgid "compute_api_class = cinder.compute.nova.API"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:23(td)
-msgid "(StrOpt) The full class name of the compute API class to use"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:30(td)
-msgid "default_availability_zone = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:31(td)
-msgid "(StrOpt) default availability zone to use when creating a new volume. If this is not set then we use the value from the storage_availability_zone option as the default availability_zone for new volumes."
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:34(td)
-msgid "default_log_levels = amqp=WARN, amqplib=WARN, boto=WARN, qpid=WARN, sqlalchemy=WARN, suds=INFO, oslo.messaging=INFO, iso8601=WARN, requests.packages.urllib3.connectionpool=WARN"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:38(td)
-msgid "default_volume_type = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:39(td)
-msgid "(StrOpt) default volume type to use"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:46(td) ./doc/common/tables/nova-api.xml:26(td)
-msgid "enable_new_services = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:47(td) ./doc/common/tables/nova-api.xml:27(td)
-msgid "(BoolOpt) Services to be added to the available pool on create"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:55(td)
-msgid "(BoolOpt) make exception message format errors fatal"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:59(td)
-msgid "(StrOpt) Name of this node. This can be an opaque identifier. It is not necessarily a hostname, FQDN, or IP address."
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:62(td)
-msgid "iet_conf = /etc/iet/ietd.conf"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:63(td)
-msgid "(StrOpt) IET configuration file"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:66(td)
-msgid "lio_initiator_iqns ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:67(td)
-msgid "(StrOpt) Comma-separated list of initiator IQNs allowed to connect to the iSCSI target. (From Nova compute nodes.)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:71(td)
-msgid "(StrOpt) Directory to use for lock files. Default to a temp directory"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:111(td)
-msgid "(BoolOpt) Enable monkey patching"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:114(td)
-msgid "monkey_patch_modules ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:119(td)
-msgid "(StrOpt) ip address of this host"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:122(td)
-msgid "no_snapshot_gb_quota = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:123(td)
-msgid "(BoolOpt) Whether snapshots count against GigaByte quota"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:126(td)
-msgid "num_shell_tries = 3"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:127(td)
-msgid "(IntOpt) number of times to attempt to run flakey shell commands"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:131(td)
-msgid "(IntOpt) range of seconds to randomly delay when starting the periodic task scheduler to reduce stampeding. (Disable by setting to 0)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:134(td) ./doc/common/tables/trove-rpc.xml:42(td) ./doc/common/tables/heat-common.xml:46(td)
-msgid "periodic_interval = 60"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:135(td)
-msgid "(IntOpt) seconds between running periodic tasks"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:147(td)
-msgid "(IntOpt) seconds between nodes reporting state to datastore"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:150(td)
-msgid "reserved_percentage = 0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:151(td)
-msgid "(IntOpt) The percentage of backend capacity is reserved"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:154(td)
-msgid "rootwrap_config = /etc/cinder/rootwrap.conf"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:163(td)
-msgid "(IntOpt) maximum time since last check-in for up service"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:166(td)
-msgid "sqlite_db = cinder.sqlite"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:186(td)
-msgid "state_path = /var/lib/cinder"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:187(td)
-msgid "(StrOpt) Top-level directory for maintaining cinder's state"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:190(td)
-msgid "storage_availability_zone = nova"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:191(td)
-msgid "(StrOpt) availability zone of this node"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:203(td)
-msgid "(IntOpt) count of reservations until usage is refreshed"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:206(td) ./doc/common/tables/nova-api.xml:94(td)
-msgid "use_forwarded_for = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:207(td) ./doc/common/tables/nova-api.xml:95(td)
-msgid "(BoolOpt) Treat X-Forwarded-For as the canonical remote address. Only enable this if you have a sanitizing proxy."
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:237(td)
-msgid "use_tpool = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml:238(td)
-msgid "(BoolOpt) Enable the experimental use of thread pooling for all DB API calls"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml:8(caption)
-msgid "Description of configuration options for trustedcomputing"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml:19(th)
-msgid "[trusted_computing]"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml:22(td)
-msgid "attestation_api_url = /OpenAttestationWebServices/V1.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml:23(td)
-msgid "(StrOpt) Attestation web API URL"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml:26(td)
-msgid "attestation_auth_blob = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml:27(td)
-msgid "(StrOpt) Attestation authorization blob - must change"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml:30(td)
-msgid "attestation_auth_timeout = 60"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml:31(td)
-msgid "(IntOpt) Attestation status cache valid period length"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml:34(td)
-msgid "attestation_port = 8443"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml:35(td)
-msgid "(StrOpt) Attestation server port"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml:38(td)
-msgid "attestation_server = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml:39(td)
-msgid "(StrOpt) Attestation server HTTP"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml:42(td)
-msgid "attestation_server_ca_file = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml:43(td)
-msgid "(StrOpt) Attestation server Cert file for Identity verification"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_flat.xml:8(caption)
-msgid "Description of configuration options for ml2_flat"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_flat.xml:19(th)
-msgid "[ml2_type_flat]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_flat.xml:22(td)
-msgid "flat_networks ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_flat.xml:23(td)
-msgid "(ListOpt) List of physical_network names with which flat networks can be created. Use * to allow flat networks with arbitrary physical_network names."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_cinder.xml:8(caption)
-msgid "Description of configuration options for clients_cinder"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_cinder.xml:19(th)
-msgid "[clients_cinder]"
-msgstr ""
-
-#: ./doc/common/tables/nova-configdrive.xml:8(caption)
-msgid "Description of configuration options for configdrive"
-msgstr ""
-
-#: ./doc/common/tables/nova-configdrive.xml:22(td)
-msgid "config_drive_format = iso9660"
-msgstr ""
-
-#: ./doc/common/tables/nova-configdrive.xml:23(td)
-msgid "(StrOpt) Config drive format. One of iso9660 (default) or vfat"
-msgstr ""
-
-#: ./doc/common/tables/nova-configdrive.xml:26(td)
-msgid "config_drive_skip_versions = 1.0 2007-01-19 2007-03-01 2007-08-29 2007-10-10 2007-12-15 2008-02-01 2008-09-01"
-msgstr ""
-
-#: ./doc/common/tables/nova-configdrive.xml:27(td)
-msgid "(StrOpt) List of metadata versions to skip placing into the config drive"
-msgstr ""
-
-#: ./doc/common/tables/nova-configdrive.xml:30(td)
-msgid "config_drive_tempdir = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-configdrive.xml:31(td)
-msgid "(StrOpt) Where to put temporary files associated with config drive creation"
-msgstr ""
-
-#: ./doc/common/tables/nova-configdrive.xml:34(td)
-msgid "force_config_drive = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-configdrive.xml:35(td)
-msgid "(StrOpt) Set to force injection to take place on a config drive (if set, valid options are: always)"
-msgstr ""
-
-#: ./doc/common/tables/nova-configdrive.xml:38(td)
-msgid "mkisofs_cmd = genisoimage"
-msgstr ""
-
-#: ./doc/common/tables/nova-configdrive.xml:45(td)
-msgid "config_drive_cdrom = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-configdrive.xml:46(td)
-msgid "(BoolOpt) Attaches the Config Drive image as a cdrom drive instead of a disk drive"
-msgstr ""
-
-#: ./doc/common/tables/nova-configdrive.xml:49(td)
-msgid "config_drive_inject_password = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-configdrive.xml:50(td)
-msgid "(BoolOpt) Sets the admin password in the config drive image"
-msgstr ""
-
-#: ./doc/common/tables/cinder-database.xml:26(td)
-msgid "db_driver = cinder.db"
-msgstr ""
-
-#: ./doc/common/tables/cinder-database.xml:27(td)
-msgid "(StrOpt) driver to use for database access"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rpc.xml:30(td)
-msgid "control_exchange = neutron"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rpc.xml:31(td) ./doc/common/tables/heat-amqp.xml:31(td) ./doc/common/tables/ceilometer-exchange.xml:27(td) ./doc/common/tables/trove-amqp.xml:35(td)
-msgid "(StrOpt) AMQP exchange to connect to if using RabbitMQ or Qpid"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rpc.xml:42(td)
-msgid "rpc_backend = neutron.openstack.common.rpc.impl_kombu"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rpc.xml:62(td)
-msgid "rpc_workers = 0"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rpc.xml:63(td)
-msgid "(IntOpt) Number of RPC worker processes for service"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rpc.xml:69(td)
-msgid "rpc_support_old_agents = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rpc.xml:70(td)
-msgid "(BoolOpt) Enable server RPC compatibility with old agents"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rpc.xml:84(td) ./doc/common/tables/trove-rpc.xml:74(td)
-msgid "(ListOpt) AMQP topic(s) used for openstack notifications"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zoning_manager.xml:8(caption)
-msgid "Description of configuration options for zoning_manager"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zoning_manager.xml:22(td)
-msgid "brcd_sb_connector = cinder.zonemanager.drivers.brocade.brcd_fc_zone_client_cli.BrcdFCZoneClientCLI"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zoning_manager.xml:23(td)
-msgid "(StrOpt) Southbound connector for zoning operation"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zoning_manager.xml:26(td)
-msgid "fc_san_lookup_service = cinder.zonemanager.drivers.brocade.brcd_fc_san_lookup_service.BrcdFCSanLookupService"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zoning_manager.xml:27(td)
-msgid "(StrOpt) FC San Lookup Service"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zoning_manager.xml:30(td)
-msgid "zone_driver = cinder.zonemanager.drivers.brocade.brcd_fc_zone_driver.BrcdFCZoneDriver"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zoning_manager.xml:31(td)
-msgid "(StrOpt) FC Zone Driver responsible for zone management"
-msgstr ""
-
-#: ./doc/common/tables/trove-volume.xml:8(caption)
-msgid "Description of configuration options for volume"
-msgstr ""
-
-#: ./doc/common/tables/trove-volume.xml:22(td)
-msgid "block_device_mapping = vdb"
-msgstr ""
-
-#: ./doc/common/tables/trove-volume.xml:26(td)
-msgid "cinder_url = http://localhost:8776/v2"
-msgstr ""
-
-#: ./doc/common/tables/trove-volume.xml:30(td)
-msgid "device_path = /dev/vdb"
-msgstr ""
-
-#: ./doc/common/tables/trove-volume.xml:34(td)
-msgid "trove_volume_support = True"
-msgstr ""
-
-#: ./doc/common/tables/trove-volume.xml:35(td)
-msgid "(BoolOpt) Whether to provision a cinder volume for datadir."
-msgstr ""
-
-#: ./doc/common/tables/trove-volume.xml:38(td)
-msgid "volume_format_timeout = 120"
-msgstr ""
-
-#: ./doc/common/tables/trove-volume.xml:42(td)
-msgid "volume_fstype = ext3"
-msgstr ""
-
-#: ./doc/common/tables/trove-volume.xml:46(td)
-msgid "volume_time_out = 60"
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml:8(caption)
-msgid "Description of configuration options for cache"
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml:19(th)
-msgid "[cache]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml:22(td)
-msgid "backend = keystone.common.cache.noop"
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml:23(td)
-msgid "(StrOpt) Dogpile.cache backend module. It is recommended that Memcache (dogpile.cache.memcache) or Redis (dogpile.cache.redis) be used in production deployments. Small workloads (single process) like devstack can use the dogpile.cache.memory backend."
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml:26(td)
-msgid "backend_argument = []"
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml:27(td)
-msgid "(MultiStrOpt) Arguments supplied to the backend module. Specify this option once per argument to be passed to the dogpile.cache backend. Example format: \"&lt;argname&gt;:&lt;value&gt;\"."
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml:30(td)
-msgid "config_prefix = cache.keystone"
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml:31(td)
-msgid "(StrOpt) Prefix for building the configuration dictionary for the cache region. This should not need to be changed unless there is another dogpile.cache region with the same configuration name."
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml:34(td)
-msgid "debug_cache_backend = False"
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml:35(td)
-msgid "(BoolOpt) Extra debugging from the cache backend (cache keys, get/set/delete/etc calls) This is only really useful if you need to see the specific cache-backend get/set/delete calls with the keys/values. Typically this should be left set to False."
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml:39(td)
-msgid "(BoolOpt) Global toggle for all caching using the should_cache_fn mechanism."
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml:42(td)
-msgid "expiration_time = 600"
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml:43(td)
-msgid "(IntOpt) Default TTL, in seconds, for any cached item in the dogpile.cache region. This applies to any cached method that doesn't have an explicit cache expiration time defined for it."
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml:46(td)
-msgid "proxies ="
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml:47(td)
-msgid "(ListOpt) Proxy Classes to import that will affect the way the dogpile.cache backend functions. See the dogpile.cache documentation on changing-backend-behavior. Comma delimited list e.g. my.dogpile.proxy.Class, my.dogpile.proxyClass2."
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml:50(td)
-msgid "use_key_mangler = True"
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml:51(td)
-msgid "(BoolOpt) Use a key-mangling function (sha1) to ensure fixed length cache-keys. This is toggle-able for debugging purposes, it is highly recommended to always leave this set to True."
-msgstr ""
-
-#: ./doc/common/tables/glance-testing.xml:22(td)
-msgid "pydev_worker_debug_host = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-testing.xml:23(td)
-msgid "(StrOpt) The hostname/IP of the pydev process listening for debug connections"
-msgstr ""
-
-#: ./doc/common/tables/glance-testing.xml:26(td)
-msgid "pydev_worker_debug_port = 5678"
-msgstr ""
-
-#: ./doc/common/tables/glance-testing.xml:27(td)
-msgid "(IntOpt) The port on which a pydev process is listening for connections."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:7(literal)
-msgid "[filter:tempauth]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:18(td)
-msgid "use = egg:swift#tempauth"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:21(td)
-msgid "set log_name = tempauth"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:36(td)
-msgid "reseller_prefix = AUTH"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:36(td)
-msgid "The naming scope for the auth service. Swift"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:39(td)
-msgid "auth_prefix = /auth/"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:39(td)
-msgid "The HTTP request path prefix for the auth service. Swift itself reserves anything beginning with the letter `v`."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:42(td)
-msgid "token_life = 86400"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:42(td)
-msgid "The number of seconds a token is valid."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:45(td)
-msgid "allow_overrides = true"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:48(td)
-msgid "storage_url_scheme = default"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:48(td)
-msgid "Scheme to return with storage urls: http, https, or default (chooses based on what the server is running as) This can be useful with an SSL load balancer in front of a non-SSL server."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:51(td)
-msgid "user_admin_admin = admin .admin .reseller_admin"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:54(td)
-msgid "user_test_tester = testing .admin"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:57(td)
-msgid "user_test2_tester2 = testing2 .admin"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml:60(td)
-msgid "user_test_tester3 = testing3"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml:8(caption)
-msgid "Description of configuration options for registry"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml:23(td)
-msgid "(StrOpt) The administrators password."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml:27(td)
-msgid "(StrOpt) The tenant name of the administrative user."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml:31(td)
-msgid "(StrOpt) The administrators user name."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml:35(td)
-msgid "(StrOpt) The region for the authentication service."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml:39(td)
-msgid "(StrOpt) The strategy to use for authentication."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml:43(td)
-msgid "(StrOpt) The URL to the keystone service."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml:46(td)
-msgid "registry_client_ca_file = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml:47(td)
-msgid "(StrOpt) The path to the certifying authority cert file to use in SSL connections to the registry server."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml:50(td)
-msgid "registry_client_cert_file = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml:51(td)
-msgid "(StrOpt) The path to the cert file to use in SSL connections to the registry server."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml:54(td)
-msgid "registry_client_insecure = False"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml:55(td)
-msgid "(BoolOpt) When using SSL in connections to the registry server, do not require validation via a certifying authority."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml:58(td)
-msgid "registry_client_key_file = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml:59(td)
-msgid "(StrOpt) The path to the key file to use in SSL connections to the registry server."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml:62(td)
-msgid "registry_client_protocol = http"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml:63(td)
-msgid "(StrOpt) The protocol to use for communication with the registry server. Either http or https."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml:66(td)
-msgid "registry_client_timeout = 600"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml:67(td)
-msgid "(IntOpt) The period of time, in seconds, that the API server will wait for a registry request to complete. A value of 0 implies no timeout."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml:70(td)
-msgid "registry_host = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml:71(td)
-msgid "(StrOpt) Address to find the registry server."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml:74(td)
-msgid "registry_port = 9191"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml:75(td)
-msgid "(IntOpt) Port the registry server is listening on."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml:7(literal)
-msgid "[object-replicator]"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml:18(td)
-msgid "log_name = object-replicator"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml:33(td)
-msgid "daemonize = on"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml:33(td)
-msgid "Whether or not to run replication as a daemon"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml:42(td)
-msgid "stats_interval = 300"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml:42(td)
-msgid "Interval in seconds between logging replication statistics"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml:45(td)
-msgid "sync_method = rsync"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml:48(td)
-msgid "rsync_timeout = 900"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml:48(td)
-msgid "Max duration (seconds) of a partition rsync"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml:51(td)
-msgid "rsync_bwlimit = 0"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml:54(td)
-msgid "rsync_io_timeout = 30"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml:54(td)
-msgid "Passed to rsync for a max duration (seconds) of an I/O op"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml:60(td)
-msgid "http_timeout = 60"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml:60(td)
-msgid "Maximum duration for an HTTP request"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml:63(td)
-msgid "lockup_timeout = 1800"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml:63(td)
-msgid "Attempts to kill all workers if nothing replications for lockup_timeout seconds"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml:69(td)
-msgid "ring_check_interval = 15"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml:69(td)
-msgid "How often (in seconds) to check the ring"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml:75(td)
-msgid "rsync_error_log_line_length = 0"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml:78(td)
-msgid "handoffs_first = False"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml:78(td)
-msgid "If set to True, partitions that are not supposed to be on the node will be replicated first. The default setting should not be changed, except for extreme situations."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml:81(td)
-msgid "handoff_delete = auto"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml:81(td)
-msgid "By default handoff partitions will be removed when it has successfully replicated to all the canonical nodes. If set to an integer n, it will remove the partition if it is successfully replicated to n nodes. The default setting should not be changed, except for extremem situations. This uses what's set here, or what's set in the DEFAULT section, or 10 (though other sections use 3 as the final default)."
-msgstr ""
-
 #: ./doc/common/tables/trove-database.xml:22(td)
 msgid "sql_connection = sqlite:///trove_test.sqlite"
 msgstr ""
@@ -31391,1368 +32135,216 @@ msgstr ""
 msgid "(BoolOpt) Allow insecure logging while executing queries through SQLAlchemy."
 msgstr ""
 
-#: ./doc/common/tables/heat-clients_backends.xml:8(caption)
-msgid "Description of configuration options for clients_backends"
+#: ./doc/common/tables/swift-container-server-app-container-server.xml:7(literal)
+msgid "[app:container-server]"
 msgstr ""
 
-#: ./doc/common/tables/heat-clients_backends.xml:22(td)
-msgid "cloud_backend = heat.engine.clients.OpenStackClients"
+#: ./doc/common/tables/swift-container-server-app-container-server.xml:18(td)
+msgid "use = egg:swift#container"
 msgstr ""
 
-#: ./doc/common/tables/heat-clients_backends.xml:23(td)
-msgid "(StrOpt) Fully qualified class name to use as a client backend."
+#: ./doc/common/tables/swift-container-server-app-container-server.xml:21(td)
+msgid "set log_name = container-server"
 msgstr ""
 
-#: ./doc/common/tables/heat-amqp.xml:30(td)
-msgid "control_exchange = heat"
+#: ./doc/common/tables/swift-container-server-app-container-server.xml:42(td)
+msgid "allow_versions = false"
 msgstr ""
 
-#: ./doc/common/tables/heat-amqp.xml:43(td) ./doc/common/tables/ceilometer-rabbitmq.xml:23(td) ./doc/common/tables/neutron-testing.xml:27(td) ./doc/common/tables/trove-amqp.xml:39(td)
-msgid "(BoolOpt) If passed, use a fake RabbitMQ provider"
+#: ./doc/common/tables/swift-container-server-app-container-server.xml:42(td)
+msgid "Enable/Disable object versioning feature"
 msgstr ""
 
-#: ./doc/common/tables/heat-amqp.xml:46(td)
-msgid "list_notifier_drivers = ['heat.openstack.common.notifier.no_op_notifier']"
+#: ./doc/common/tables/nova-authentication.xml:8(caption)
+msgid "Description of configuration options for authentication"
 msgstr ""
 
-#: ./doc/common/tables/heat-amqp.xml:47(td)
-msgid "(MultiStrOpt) List of drivers to send notifications"
+#: ./doc/common/tables/neutron-nvsd.xml:8(caption)
+msgid "Description of configuration options for nvsd"
 msgstr ""
 
-#: ./doc/common/tables/heat-amqp.xml:55(td) ./doc/common/tables/ceilometer-amqp.xml:35(td)
-msgid "(ListOpt) AMQP topic used for OpenStack notifications"
+#: ./doc/common/tables/neutron-nvsd.xml:23(td)
+msgid "(StrOpt) integration bridge"
 msgstr ""
 
-#: ./doc/common/tables/swift-dispersion-dispersion.xml:7(literal)
-msgid "[dispersion]"
+#: ./doc/common/tables/neutron-nvsd.xml:26(th)
+msgid "[nvsd]"
 msgstr ""
 
-#: ./doc/common/tables/swift-dispersion-dispersion.xml:7(literal)
-msgid "dispersion.conf-sample"
+#: ./doc/common/tables/neutron-nvsd.xml:29(td)
+msgid "nvsd_ip = 127.0.0.1"
 msgstr ""
 
-#: ./doc/common/tables/swift-dispersion-dispersion.xml:18(td)
-msgid "auth_url = http://localhost:8080/auth/v1.0"
+#: ./doc/common/tables/neutron-nvsd.xml:30(td)
+msgid "(StrOpt) NVSD Controller IP address"
 msgstr ""
 
-#: ./doc/common/tables/swift-dispersion-dispersion.xml:18(td) ./doc/common/tables/swift-dispersion-dispersion.xml:27(td)
-msgid "Endpoint for auth server, such as keystone"
+#: ./doc/common/tables/neutron-nvsd.xml:33(td)
+msgid "nvsd_passwd = oc123"
 msgstr ""
 
-#: ./doc/common/tables/swift-dispersion-dispersion.xml:21(td)
-msgid "auth_user = test:tester"
+#: ./doc/common/tables/neutron-nvsd.xml:34(td)
+msgid "(StrOpt) NVSD Controller password"
 msgstr ""
 
-#: ./doc/common/tables/swift-dispersion-dispersion.xml:21(td) ./doc/common/tables/swift-dispersion-dispersion.xml:30(td)
-msgid "Default user for dispersion in this context"
+#: ./doc/common/tables/neutron-nvsd.xml:37(td)
+msgid "nvsd_port = 8082"
 msgstr ""
 
-#: ./doc/common/tables/swift-dispersion-dispersion.xml:24(td)
-msgid "auth_key = testing"
+#: ./doc/common/tables/neutron-nvsd.xml:38(td)
+msgid "(IntOpt) NVSD Controller Port number"
 msgstr ""
 
-#: ./doc/common/tables/swift-dispersion-dispersion.xml:27(td)
-msgid "auth_url = http://localhost:5000/v2.0/"
+#: ./doc/common/tables/neutron-nvsd.xml:41(td)
+msgid "nvsd_retries = 0"
 msgstr ""
 
-#: ./doc/common/tables/swift-dispersion-dispersion.xml:30(td)
-msgid "auth_user = tenant:user"
+#: ./doc/common/tables/neutron-nvsd.xml:42(td)
+msgid "(IntOpt) Number of login retries to NVSD controller"
 msgstr ""
 
-#: ./doc/common/tables/swift-dispersion-dispersion.xml:33(td)
-msgid "auth_key = password"
+#: ./doc/common/tables/neutron-nvsd.xml:45(td)
+msgid "nvsd_user = ocplugin"
 msgstr ""
 
-#: ./doc/common/tables/swift-dispersion-dispersion.xml:36(td)
-msgid "auth_version = 2.0"
+#: ./doc/common/tables/neutron-nvsd.xml:46(td)
+msgid "(StrOpt) NVSD Controller username"
 msgstr ""
 
-#: ./doc/common/tables/swift-dispersion-dispersion.xml:36(td)
-msgid "Indicates which version of auth"
+#: ./doc/common/tables/neutron-nvsd.xml:49(td)
+msgid "request_timeout = 30"
 msgstr ""
 
-#: ./doc/common/tables/swift-dispersion-dispersion.xml:39(td)
-msgid "Indicates whether endpoint for auth is public or internal"
+#: ./doc/common/tables/neutron-nvsd.xml:50(td)
+msgid "(IntOpt) NVSD controller REST API request timeout in seconds"
 msgstr ""
 
-#: ./doc/common/tables/swift-dispersion-dispersion.xml:42(td)
-msgid "keystone_api_insecure = no"
+#: ./doc/common/tables/swift-account-server-pipeline-main.xml:18(td)
+msgid "pipeline = healthcheck recon account-server"
 msgstr ""
 
-#: ./doc/common/tables/swift-dispersion-dispersion.xml:48(td)
-msgid "dispersion_coverage = 1.0"
+#: ./doc/common/tables/glance-gridfs.xml:8(caption)
+msgid "Description of configuration options for gridfs"
 msgstr ""
 
-#: ./doc/common/tables/swift-dispersion-dispersion.xml:51(td)
-msgid "retries = 5"
+#: ./doc/common/tables/glance-gridfs.xml:22(td)
+msgid "mongodb_store_db = None"
 msgstr ""
 
-#: ./doc/common/tables/swift-dispersion-dispersion.xml:54(td) ./doc/common/tables/swift-account-server-account-reaper.xml:30(td)
-msgid "concurrency = 25"
+#: ./doc/common/tables/glance-gridfs.xml:23(td)
+msgid "(StrOpt) Database to use."
 msgstr ""
 
-#: ./doc/common/tables/swift-dispersion-dispersion.xml:57(td)
-msgid "container_populate = yes"
+#: ./doc/common/tables/glance-gridfs.xml:26(td)
+msgid "mongodb_store_uri = None"
 msgstr ""
 
-#: ./doc/common/tables/swift-dispersion-dispersion.xml:60(td)
-msgid "object_populate = yes"
+#: ./doc/common/tables/glance-gridfs.xml:27(td)
+msgid "(StrOpt) Hostname or IP address of the instance to connect to, or a mongodb URI, or a list of hostnames / mongodb URIs. If host is an IPv6 literal it must be enclosed in '[' and ']' characters following the RFC2732 URL syntax (e.g. '[::1]' for localhost)."
 msgstr ""
 
-#: ./doc/common/tables/swift-dispersion-dispersion.xml:63(td)
-msgid "container_report = yes"
+#: ./doc/common/tables/neutron-notifier.xml:8(caption)
+msgid "Description of configuration options for notifier"
 msgstr ""
 
-#: ./doc/common/tables/swift-dispersion-dispersion.xml:66(td)
-msgid "object_report = yes"
+#: ./doc/common/tables/nova-rpc_all.xml:8(caption)
+msgid "Description of configuration options for rpc_all"
 msgstr ""
 
-#: ./doc/common/tables/swift-dispersion-dispersion.xml:69(td)
-msgid "dump_json = no"
+#: ./doc/common/tables/nova-rpc_all.xml:201(td) ./doc/common/tables/nova-rpc.xml:65(td)
+msgid "rpc_driver_queue_base = cells.intercell"
 msgstr ""
 
-#: ./doc/common/tables/cinder-hpmsa.xml:8(caption)
-msgid "Description of configuration options for hpmsa"
+#: ./doc/common/tables/nova-rpc_all.xml:202(td) ./doc/common/tables/nova-rpc.xml:66(td)
+msgid "(StrOpt) Base queue name to use when communicating between cells. Various topics by message type will be appended to this."
 msgstr ""
 
-#: ./doc/common/tables/cinder-hpmsa.xml:22(td)
-msgid "msa_vdisk = OpenStack"
+#: ./doc/common/tables/nova-rpc_all.xml:215(td) ./doc/common/tables/nova-rpc.xml:79(td)
+msgid "baseapi = None"
 msgstr ""
 
-#: ./doc/common/tables/cinder-hpmsa.xml:23(td)
-msgid "(StrOpt) The VDisk to use for volume creation."
+#: ./doc/common/tables/nova-rpc_all.xml:216(td) ./doc/common/tables/nova-rpc.xml:80(td)
+msgid "(StrOpt) Set a version cap for messages sent to the base api in any service"
 msgstr ""
 
-#: ./doc/common/tables/cinder-emc.xml:8(caption)
-msgid "Description of configuration options for emc"
+#: ./doc/common/tables/neutron-hyperv_agent.xml:8(caption)
+msgid "Description of configuration options for hyperv_agent"
 msgstr ""
 
-#: ./doc/common/tables/cinder-emc.xml:22(td)
-msgid "cinder_emc_config_file = /etc/cinder/cinder_emc_config.xml"
+#: ./doc/common/tables/neutron-hyperv_agent.xml:22(td)
+msgid "enable_metrics_collection = False"
 msgstr ""
 
-#: ./doc/common/tables/cinder-emc.xml:23(td)
-msgid "(StrOpt) use this file for cinder emc plugin config data"
+#: ./doc/common/tables/neutron-hyperv_agent.xml:23(td)
+msgid "(BoolOpt) Enables metrics collections for switch ports by using Hyper-V's metric APIs. Collected data can by retrieved by other apps and services, e.g.: Ceilometer. Requires Hyper-V / Windows Server 2012 and above"
 msgstr ""
 
-#: ./doc/common/tables/cinder-emc.xml:26(td)
-msgid "max_luns_per_storage_group = 256"
+#: ./doc/common/tables/neutron-hyperv_agent.xml:26(td)
+msgid "local_network_vswitch = private"
 msgstr ""
 
-#: ./doc/common/tables/cinder-emc.xml:27(td)
-msgid "(IntOpt) Default max number of LUNs in a storage group"
+#: ./doc/common/tables/neutron-hyperv_agent.xml:27(td)
+msgid "(StrOpt) Private vswitch name used for local networks"
 msgstr ""
 
-#: ./doc/common/tables/cinder-emc.xml:30(td)
-msgid "naviseccli_path ="
+#: ./doc/common/tables/neutron-hyperv_agent.xml:30(td)
+msgid "metrics_max_retries = 100"
 msgstr ""
 
-#: ./doc/common/tables/cinder-emc.xml:31(td)
-msgid "(StrOpt) Naviseccli Path"
+#: ./doc/common/tables/neutron-hyperv_agent.xml:31(td)
+msgid "(IntOpt) Specifies the maximum number of retries to enable Hyper-V's port metrics collection. The agent will try to enable the feature once every polling_interval period for at most metrics_max_retries or until it succeedes."
 msgstr ""
 
-#: ./doc/common/tables/cinder-emc.xml:34(td)
-msgid "storage_vnx_pool_name = None"
+#: ./doc/common/tables/neutron-hyperv_agent.xml:34(td)
+msgid "physical_network_vswitch_mappings ="
 msgstr ""
 
-#: ./doc/common/tables/cinder-emc.xml:35(td)
-msgid "(StrOpt) ISCSI pool name"
+#: ./doc/common/tables/neutron-hyperv_agent.xml:35(td)
+msgid "(ListOpt) List of &lt;physical_network&gt;:&lt;vswitch&gt; where the physical networks can be expressed with wildcards, e.g.: .\"*:external\""
 msgstr ""
 
-#: ./doc/common/tables/swift-account-server-account-replicator.xml:7(literal)
-msgid "[account-replicator]"
+#: ./doc/common/tables/neutron-hyperv_agent.xml:39(td)
+msgid "(IntOpt) The number of seconds the agent will wait between polling for local device changes."
 msgstr ""
 
-#: ./doc/common/tables/swift-account-server-account-replicator.xml:18(td)
-msgid "log_name = account-replicator"
+#: ./doc/common/tables/neutron-hyperv_agent.xml:42(th)
+msgid "[HYPERV]"
 msgstr ""
 
-#: ./doc/common/tables/neutron-fwaas.xml:8(caption)
-msgid "Description of configuration options for fwaas"
+#: ./doc/common/tables/neutron-hyperv_agent.xml:50(td)
+msgid "(StrOpt) Network type for tenant networks (local, flat, vlan or none)"
 msgstr ""
 
-#: ./doc/common/tables/neutron-fwaas.xml:19(th) ./doc/common/tables/neutron-nec.xml:73(th)
-msgid "[fwaas]"
+#: ./doc/common/tables/neutron-hyperv_agent.xml:56(td) ./doc/common/tables/nova-hyperv.xml:30(td)
+msgid "force_hyperv_utils_v1 = False"
 msgstr ""
 
-#: ./doc/common/tables/neutron-fwaas.xml:23(td)
-msgid "(BoolOpt) Enable FWaaS"
+#: ./doc/common/tables/neutron-hyperv_agent.xml:57(td) ./doc/common/tables/nova-hyperv.xml:31(td)
+msgid "(BoolOpt) Force V1 WMI utility classes"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_tsm.xml:8(caption)
-msgid "Description of configuration options for backups_tsm"
+#: ./doc/common/tables/keystone-federation.xml:8(caption)
+msgid "Description of configuration options for federation"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_tsm.xml:22(td)
-msgid "backup_tsm_compression = True"
+#: ./doc/common/tables/keystone-federation.xml:19(th)
+msgid "[federation]"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_tsm.xml:23(td)
-msgid "(BoolOpt) Enable or Disable compression for backups"
+#: ./doc/common/tables/keystone-federation.xml:22(td)
+msgid "assertion_prefix ="
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_tsm.xml:26(td)
-msgid "backup_tsm_password = password"
+#: ./doc/common/tables/keystone-federation.xml:23(td)
+msgid "(StrOpt) Value to be used when filtering assertion parameters from the environment."
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_tsm.xml:27(td)
-msgid "(StrOpt) TSM password for the running username"
+#: ./doc/common/tables/keystone-federation.xml:26(td)
+msgid "driver = keystone.contrib.federation.backends.sql.Federation"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_tsm.xml:30(td)
-msgid "backup_tsm_volume_prefix = backup"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups_tsm.xml:31(td)
-msgid "(StrOpt) Volume prefix for the backup id when backing up to TSM"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:8(caption)
-msgid "Description of configuration options for sdnve"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:19(th)
-msgid "[SDNVE]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:22(td)
-msgid "base_url = /one/nb/v2/"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:23(td)
-msgid "(StrOpt) Base URL for SDN-VE controller REST API"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:26(td)
-msgid "controller_ips = 127.0.0.1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:27(td)
-msgid "(ListOpt) List of IP addresses of SDN-VE controller(s)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:30(td)
-msgid "default_tenant_type = OF"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:31(td)
-msgid "(StrOpt) Tenant type: OF (default) and OVERLAY"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:34(td)
-msgid "format = json"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:35(td)
-msgid "(StrOpt) SDN-VE request/response format"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:38(td)
-msgid "info = sdnve_info_string"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:39(td)
-msgid "(StrOpt) SDN-VE RPC subject"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:42(td)
-msgid "integration_bridge = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:46(td)
-msgid "interface_mappings ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:47(td)
-msgid "(ListOpt) List of &lt;physical_network_name&gt;:&lt;interface_name&gt;"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:50(td)
-msgid "of_signature = SDNVE-OF"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:51(td)
-msgid "(StrOpt) The string in tenant description that indicates the tenant is a OF tenant"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:54(td)
-msgid "out_of_band = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:55(td)
-msgid "(BoolOpt) Indicating if controller is out of band or not"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:58(td)
-msgid "overlay_signature = SDNVE-OVERLAY"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:59(td)
-msgid "(StrOpt) The string in tenant description that indicates the tenant is a OVERLAY tenant"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:62(td)
-msgid "password = admin"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:63(td)
-msgid "(StrOpt) SDN-VE administrator password"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:66(td)
-msgid "port = 8443"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:67(td)
-msgid "(StrOpt) SDN-VE controller port number"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:70(td)
-msgid "reset_bridge = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:71(td)
-msgid "(BoolOpt) Reset the integration bridge before use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:74(td)
-msgid "use_fake_controller = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:75(td)
-msgid "(BoolOpt) If set to True uses a fake controller."
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:78(td)
-msgid "userid = admin"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:79(td)
-msgid "(StrOpt) SDN-VE administrator user id"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:82(th)
-msgid "[SDNVE_AGENT]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:86(td)
-msgid "(IntOpt) Agent polling interval if necessary"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:90(td)
-msgid "(StrOpt) Using root helper"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:93(td)
-msgid "rpc = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml:94(td)
-msgid "(BoolOpt) Whether using rpc"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_mysql.xml:8(caption)
-msgid "Description of configuration options for db_mysql"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_mysql.xml:19(th)
-msgid "[mysql]"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_mysql.xml:26(td) ./doc/common/tables/trove-db_percona.xml:26(td)
-msgid "mount_point = /var/lib/mysql"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_mysql.xml:30(td) ./doc/common/tables/trove-db_percona.xml:30(td)
-msgid "root_on_create = False"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_mysql.xml:31(td) ./doc/common/tables/trove-db_percona.xml:31(td)
-msgid "(BoolOpt) Enable the automatic creation of the root user for the service during instance-create. The generated password for the root user is immediately returned in the response of instance-create as the 'password' field."
-msgstr ""
-
-#: ./doc/common/tables/trove-db_mysql.xml:34(td) ./doc/common/tables/trove-db_percona.xml:34(td)
-msgid "tcp_ports = 3306"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_mysql.xml:42(td)
-msgid "usage_timeout = 400"
-msgstr ""
-
-#: ./doc/common/tables/trove-rpc.xml:38(td)
-msgid "num_tries = 3"
-msgstr ""
-
-#: ./doc/common/tables/trove-rpc.xml:47(td)
-msgid "(IntOpt) The interval in seconds which periodic tasks are run."
-msgstr ""
-
-#: ./doc/common/tables/trove-rpc.xml:50(td)
-msgid "rpc_backend = trove.openstack.common.rpc.impl_kombu"
-msgstr ""
-
-#: ./doc/common/tables/trove-rpc.xml:77(th)
-msgid "[secure_messages]"
-msgstr ""
-
-#: ./doc/common/tables/trove-rpc.xml:81(td)
-msgid "(BoolOpt) Whether Secure Messaging (Signing) is enabled, defaults to enabled"
-msgstr ""
-
-#: ./doc/common/tables/trove-rpc.xml:84(td)
-msgid "encrypt = False"
-msgstr ""
-
-#: ./doc/common/tables/trove-rpc.xml:85(td)
-msgid "(BoolOpt) Whether Secure Messaging (Encryption) is enabled, defaults to not enabled"
-msgstr ""
-
-#: ./doc/common/tables/trove-rpc.xml:88(td)
-msgid "enforced = False"
-msgstr ""
-
-#: ./doc/common/tables/trove-rpc.xml:89(td)
-msgid "(BoolOpt) Whether Secure Messaging (Signing) is enforced, defaults to not enforced"
-msgstr ""
-
-#: ./doc/common/tables/trove-rpc.xml:92(td)
-msgid "kds_endpoint = None"
-msgstr ""
-
-#: ./doc/common/tables/trove-rpc.xml:93(td)
-msgid "(StrOpt) KDS endpoint (ex: http://kds.example.com:35357/v3)"
-msgstr ""
-
-#: ./doc/common/tables/trove-rpc.xml:96(td)
-msgid "secret_key = None"
-msgstr ""
-
-#: ./doc/common/tables/trove-rpc.xml:97(td)
-msgid "(MultiStrOpt) A list of keys: (ex: name:&lt;base64 encoded key&gt;), ignored if secret_keys_file is set"
-msgstr ""
-
-#: ./doc/common/tables/trove-rpc.xml:100(td)
-msgid "secret_keys_file = None"
-msgstr ""
-
-#: ./doc/common/tables/trove-rpc.xml:101(td)
-msgid "(StrOpt) Path to the file containing the keys, takes precedence over secret_key"
-msgstr ""
-
-#: ./doc/common/tables/cinder-connection.xml:8(caption)
-msgid "Description of configuration options for connection"
-msgstr ""
-
-#: ./doc/common/tables/cinder-connection.xml:22(td)
-msgid "connection = sqlite:///$state_path/$sqlite_db"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml:18(td)
-msgid "mtime_check_interval = 300"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:7(literal)
-msgid "[filter:authtoken]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:18(td)
-msgid "auth_host = keystonehost"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:24(td)
-msgid "auth_protocol = http"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:27(td)
-msgid "auth_uri = http://keystonehost:5000/"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:30(td)
-msgid "admin_tenant_name = service"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:33(td)
-msgid "admin_user = swift"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:36(td)
-msgid "admin_password = password"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:39(td)
-msgid "delay_auth_decision = 1"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:42(td)
-msgid "cache = swift.cache"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml:45(td)
-msgid "include_service_catalog = False"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_redis.xml:8(caption)
-msgid "Description of configuration options for db_redis"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_redis.xml:19(th)
-msgid "[redis]"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_redis.xml:26(td)
-msgid "mount_point = /var/lib/redis"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_redis.xml:30(td)
-msgid "tcp_ports = 6379"
-msgstr ""
-
-#: ./doc/common/tables/neutron-zeromq.xml:38(td)
-msgid "rpc_zmq_matchmaker = neutron.openstack.common.rpc.matchmaker.MatchMakerLocalhost"
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml:8(caption)
-msgid "Description of configuration options for token"
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml:19(th)
-msgid "[token]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml:22(td)
-msgid "bind ="
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml:23(td)
-msgid "(ListOpt) External auth mechanisms that should add bind information to token e.g. kerberos, x509."
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml:27(td)
-msgid "(IntOpt) Time to cache tokens (in seconds). This has no effect unless global and token caching are enabled."
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml:31(td)
-msgid "(BoolOpt) Toggle for token system cacheing. This has no effect unless global caching is enabled."
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml:34(td)
-msgid "driver = keystone.token.backends.sql.Token"
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml:35(td)
-msgid "(StrOpt) Keystone Token persistence backend driver."
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml:39(td)
-msgid "(StrOpt) Enforcement policy on tokens presented to keystone with bind information. One of disabled, permissive, strict, required or a specifically required bind mode e.g. kerberos or x509 to require binding to that authentication."
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml:42(td)
-msgid "expiration = 3600"
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml:43(td)
-msgid "(IntOpt) Amount of time a token should remain valid (in seconds)."
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml:46(td)
-msgid "provider = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml:47(td)
-msgid "(StrOpt) Controls the token construction, validation, and revocation operations. Core providers are \"keystone.token.providers.[pki|uuid].Provider\"."
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml:50(td)
-msgid "revocation_cache_time = 3600"
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml:51(td)
-msgid "(IntOpt) Time to cache the revocation list and the revocation events if revoke extension is enabled (in seconds). This has no effect unless global and token caching are enabled."
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml:54(td)
-msgid "revoke_by_id = True"
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml:55(td)
-msgid "(BoolOpt) Revoke token by token identifier. Setting revoke_by_id to True enables various forms of enumerating tokens, e.g. `list tokens for user`. These enumerations are processed to determine the list of tokens to revoke. Only disable if you are switching to using the Revoke extension with a backend other than KVS, which stores events in memory."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml:19(th)
-msgid "[ipsec]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml:22(td)
-msgid "config_base_dir = $state_path/ipsec"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml:23(td)
-msgid "(StrOpt) Location to store ipsec server config files"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml:26(td)
-msgid "ipsec_status_check_interval = 60"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml:27(td)
-msgid "(IntOpt) Interval for checking ipsec status"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml:30(th)
-msgid "[openswan]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml:33(td)
-msgid "ipsec_config_template = /usr/lib/python/site-packages/neutron/services/vpn/device_drivers/template/openswan/ipsec.conf.template"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml:34(td)
-msgid "(StrOpt) Template file for ipsec configuration"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml:37(td)
-msgid "ipsec_secret_template = /usr/lib/python/site-packages/neutron/services/vpn/device_drivers/template/openswan/ipsec.secret.template"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml:38(td)
-msgid "(StrOpt) Template file for ipsec secret configuration"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml:41(th)
-msgid "[vpnagent]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml:44(td)
-msgid "vpn_device_driver = ['neutron.services.vpn.device_drivers.ipsec.OpenSwanDriver']"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml:45(td)
-msgid "(MultiStrOpt) The vpn device drivers Neutron will use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-agent.xml:8(caption)
-msgid "Description of configuration options for agent"
-msgstr ""
-
-#: ./doc/common/tables/neutron-agent.xml:22(td)
-msgid "external_pids = $state_path/external/pids"
-msgstr ""
-
-#: ./doc/common/tables/neutron-agent.xml:23(td)
-msgid "(StrOpt) Location to store child pid files"
-msgstr ""
-
-#: ./doc/common/tables/neutron-agent.xml:27(td)
-msgid "(IntOpt) MTU setting for device."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml:8(caption)
-msgid "Description of configuration options for ryu"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml:22(td)
-msgid "openflow_rest_api = 127.0.0.1:8080"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml:23(td)
-msgid "(StrOpt) OpenFlow REST API location"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml:26(td)
-msgid "ovsdb_interface = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml:27(td)
-msgid "(StrOpt) OVSDB interface to connect to"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml:30(td)
-msgid "ovsdb_ip = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml:31(td)
-msgid "(StrOpt) OVSDB IP to connect to"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml:34(td)
-msgid "ovsdb_port = 6634"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml:35(td)
-msgid "(IntOpt) OVSDB port to connect to"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml:38(td)
-msgid "tunnel_interface = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml:39(td)
-msgid "(StrOpt) Tunnel interface to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml:42(td)
-msgid "tunnel_ip = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml:43(td)
-msgid "(StrOpt) Tunnel IP to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml:46(td)
-msgid "tunnel_key_max = 16777215"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml:47(td)
-msgid "(IntOpt) Maximum tunnel ID to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml:50(td)
-msgid "tunnel_key_min = 1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml:51(td)
-msgid "(IntOpt) Minimum tunnel ID to use"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml:7(literal)
-msgid "[app:object-server]"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml:18(td)
-msgid "use = egg:swift#object"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml:21(td)
-msgid "set log_name = object-server"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml:36(td)
-msgid "max_upload_time = 86400"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml:36(td)
-msgid "Maximum time allowed to upload an object"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml:39(td)
-msgid "slow = 0"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml:39(td)
-msgid "If &gt; 0, Minimum time in seconds for a PUT or DELETE request to complete"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml:42(td)
-msgid "keep_cache_size = 5424880"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml:42(td)
-msgid "Largest object size to keep in buffer cache"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml:45(td)
-msgid "keep_cache_private = false"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml:45(td)
-msgid "Allow non-public objects to stay in kernel's buffer cache"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml:48(td)
-msgid "mb_per_sync = 512"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml:48(td)
-msgid "On PUT requests, sync file every n MB"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml:51(td)
-msgid "allowed_headers = Content-Disposition, Content-Encoding, X-Delete-At, X-Object-Manifest, X-Static-Large-Object"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml:51(td)
-msgid "Comma-separated list of headers that can be set in metadata of an object"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml:57(td)
-msgid "threads_per_disk = 0"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml:57(td)
-msgid "Size of the per-disk thread pool used for performing disk I/O. The default of 0 means to not use a per-disk thread pool. It is recommended to keep this value small, as large values can result in high read latencies due to large queue depths. A good starting point is 4 threads per disk."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml:63(td)
-msgid "replication_concurrency = 4"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml:63(td)
-msgid "Set to restrict the number of concurrent incoming REPLICATION requests; set to 0 for unlimited"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml:66(td)
-msgid "replication_one_per_device = True"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml:66(td)
-msgid "Restricts incoming REPLICATION requests to one per device, replication_currency above allowing. This can help control I/O to each device, but you may wish to set this to False to allow multiple REPLICATION requests (up to the above replication_concurrency setting) per device."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml:69(td)
-msgid "replication_lock_timeout = 15"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml:69(td)
-msgid "Number of seconds to wait for an existing replication device lock before giving up."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml:72(td)
-msgid "replication_failure_threshold = 100"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml:72(td)
-msgid "The number of subrequest failures before the replication_failure_ratio is checked"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml:75(td)
-msgid "replication_failure_ratio = 1.0"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml:75(td)
-msgid "If the value of failures / successes of REPLICATION subrequests exceeds this ratio, the overall REPLICATION request will be aborted"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_couchbase.xml:8(caption)
-msgid "Description of configuration options for db_couchbase"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_couchbase.xml:19(th)
-msgid "[couchbase]"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_couchbase.xml:26(td)
-msgid "mount_point = /var/lib/couchbase"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_couchbase.xml:30(td)
-msgid "tcp_ports = 8091, 8092, 4369, 11209-11211, 21100-21199"
-msgstr ""
-
-#: ./doc/common/tables/neutron-policy.xml:22(td)
-msgid "allow_overlapping_ips = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-policy.xml:23(td)
-msgid "(BoolOpt) Allow overlapping IP support in Neutron"
-msgstr ""
-
-#: ./doc/common/tables/neutron-policy.xml:27(td)
-msgid "(StrOpt) The policy file to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rootwrap.xml:22(td)
-msgid "filters_path = /etc/neutron/rootwrap.d,/usr/share/neutron/rootwrap,/etc/quantum/rootwrap.d,/usr/share/quantum/rootwrap"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rootwrap.xml:42(th)
-msgid "[xenapi]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rootwrap.xml:45(td)
-msgid "xenapi_connection_url = &lt;None&gt;"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rootwrap.xml:46(td)
-msgid "XenAPI configuration is only required by the L2 agent if it is to target a XenServer/XCP compute host's dom0."
-msgstr ""
-
-#: ./doc/common/tables/neutron-rootwrap.xml:49(td) ./doc/common/tables/cinder-storage_xen.xml:30(td)
-msgid "xenapi_connection_username = root"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rootwrap.xml:53(td)
-msgid "xenapi_connection_password = &lt;None&gt;"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:21(td)
-msgid "bind_port = 80"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:36(td)
-msgid "expose_info = true"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:36(td)
-msgid "Enables exposing configuration settings via HTTP GET /info."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:39(td)
-msgid "admin_key = secret_admin_key"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:39(td)
-msgid "to use for admin calls that are HMAC signed. Default is empty, which will disable admin calls to /info. the proxy server. For most cases, this should be `egg:swift#proxy`. request whenever it has to failover to a handoff node"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:42(td)
-msgid "disallowed_sections = container_quotas, tempurl"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:58(td)
-msgid "cert_file = /etc/swift/proxy.crt"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:58(td)
-msgid "to the ssl .crt. This should be enabled for testing purposes only."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:61(td)
-msgid "key_file = /etc/swift/proxy.key"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:61(td)
-msgid "to the ssl .key. This should be enabled for testing purposes only."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:79(td)
-msgid "log_headers = false"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:85(td)
-msgid "trans_id_suffix ="
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:115(td)
-msgid "cors_allow_origin ="
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml:115(td)
-msgid "is a list of hosts that are included with any CORS request by default and returned with the Access-Control-Allow-Origin header in addition to what the container has set. to call to setup custom log handlers. for eventlet the proxy server. For most cases, this should be `egg:swift#proxy`. request whenever it has to failover to a handoff node"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml:7(literal)
-msgid "[filter:staticweb]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml:18(td)
-msgid "use = egg:swift#staticweb"
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml:22(td)
-msgid "configurations_page_size = 20"
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml:26(td)
-msgid "databases_page_size = 20"
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml:30(td)
-msgid "default_datastore = None"
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml:31(td)
-msgid "(StrOpt) The default datastore id or name to use if one is not provided by the user. If the default value is None, the field becomes required in the instance-create request."
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml:38(td)
-msgid "default_neutron_networks ="
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml:39(td)
-msgid "(ListOpt) List of network IDs which should be attached to instance when networks are not specified in API call."
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml:46(td)
-msgid "default_password_length = 36"
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml:54(td)
-msgid "expected_filetype_suffixes = json"
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml:55(td)
-msgid "(ListOpt) Filetype endings not to be reattached to an id by the utils method correct_id_with_req."
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml:62(td)
-msgid "pybasedir = /usr/lib/python/site-packages/trove"
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml:63(td)
-msgid "(StrOpt) Directory where the trove python module is installed."
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml:66(td)
-msgid "pydev_path = None"
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml:67(td)
-msgid "(StrOpt) Set path to pydevd library, used if pydevd is not found in python sys.path."
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml:70(td)
-msgid "taskmanager_queue = taskmanager"
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml:74(td)
-msgid "template_path = /etc/trove/templates/"
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml:75(td)
-msgid "(StrOpt) Path which leads to datastore templates."
-msgstr ""
-
-#: ./doc/common/tables/cinder-ssl.xml:8(caption) ./doc/common/tables/neutron-ssl.xml:8(caption) ./doc/common/tables/trove-ssl.xml:8(caption) ./doc/common/tables/glance-ssl.xml:8(caption) ./doc/common/tables/keystone-ssl.xml:8(caption) ./doc/common/tables/ceilometer-ssl.xml:8(caption)
-msgid "Description of configuration options for ssl"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:22(td) ./doc/common/tables/heat-metadata_api.xml:22(td)
-msgid "heat_metadata_server_url ="
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:23(td) ./doc/common/tables/heat-metadata_api.xml:23(td)
-msgid "(StrOpt) URL of the Heat metadata server."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:26(td)
-msgid "heat_stack_user_role = heat_stack_user"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:27(td)
-msgid "(StrOpt) Keystone role for heat template-defined users."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:38(td)
-msgid "max_json_body_size = 1048576"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:39(td)
-msgid "(IntOpt) Maximum raw byte size of JSON request body. Should be larger than max_template_size."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:50(td)
-msgid "secure_proxy_ssl_header = X-Forwarded-Proto"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:51(td)
-msgid "(StrOpt) The HTTP Header that will be used to determine which the original request protocol scheme was, even if it was removed by an SSL terminator proxy."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:54(td)
-msgid "stack_action_timeout = 3600"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:55(td)
-msgid "(IntOpt) Timeout in seconds for stack action (ie. create or update)."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:58(td)
-msgid "stack_domain_admin = None"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:59(td)
-msgid "(StrOpt) Keystone username, a user with roles sufficient to manage users and projects in the stack_user_domain."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:62(td)
-msgid "stack_domain_admin_password = None"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:63(td)
-msgid "(StrOpt) Keystone password for stack_domain_admin user."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:66(td)
-msgid "stack_user_domain = None"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:67(td)
-msgid "(StrOpt) Keystone domain ID which contains heat template-defined users."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:70(td)
-msgid "trusts_delegated_roles = heat_stack_owner"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:71(td)
-msgid "(ListOpt) Subset of trustor roles to be delegated to heat."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:74(th)
-msgid "[auth_password]"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:77(td) ./doc/common/tables/heat-api.xml:88(td)
-msgid "allowed_auth_uris ="
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:78(td) ./doc/common/tables/heat-api.xml:89(td)
-msgid "(ListOpt) Allowed keystone endpoints for auth_uri when multi_cloud is enabled. At least one endpoint needs to be specified."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:81(td) ./doc/common/tables/heat-api.xml:96(td)
-msgid "multi_cloud = False"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:82(td) ./doc/common/tables/heat-api.xml:97(td)
-msgid "(BoolOpt) Allow orchestration of multiple clouds."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:85(th)
-msgid "[ec2authtoken]"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:93(td)
-msgid "(StrOpt) Authentication Endpoint URI."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:100(th)
-msgid "[heat_api]"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:111(td)
-msgid "bind_port = 8004"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:131(th) ./doc/common/tables/glance-paste.xml:19(th) ./doc/common/tables/keystone-api.xml:101(th)
-msgid "[paste_deploy]"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:135(td)
-msgid "(StrOpt) The API paste config file to use."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:138(td) ./doc/common/tables/glance-paste.xml:26(td)
-msgid "flavor = None"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml:139(td)
-msgid "(StrOpt) The flavor to use."
-msgstr ""
-
-#: ./doc/common/tables/trove-db_percona.xml:8(caption)
-msgid "Description of configuration options for db_percona"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_percona.xml:19(th)
-msgid "[percona]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml:8(caption)
-msgid "Description of configuration options for meta"
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml:19(th)
-msgid "[META]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml:22(td)
-msgid "default_flavor ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml:23(td)
-msgid "(StrOpt) Default flavor to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml:26(td)
-msgid "default_l3_flavor ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml:27(td)
-msgid "(StrOpt) Default L3 flavor to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml:30(td)
-msgid "extension_map ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml:31(td)
-msgid "(StrOpt) A list of extensions, per plugin, to load."
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml:34(td)
-msgid "l3_plugin_list ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml:35(td)
-msgid "(StrOpt) List of L3 plugins to load"
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml:38(td)
-msgid "plugin_list ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml:39(td)
-msgid "(StrOpt) List of plugins to load"
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml:42(td)
-msgid "rpc_flavor ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml:43(td)
-msgid "(StrOpt) Flavor of which plugin handles RPC"
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml:46(td)
-msgid "supported_extension_aliases ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml:47(td)
-msgid "(StrOpt) Supported extension aliases"
-msgstr ""
-
-#: ./doc/common/tables/neutron-redis.xml:23(td)
-msgid "(StrOpt) The hostname Neutron is running on"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml:8(caption)
-msgid "Description of configuration options for exchange"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml:22(td)
-msgid "cinder_control_exchange = cinder"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml:23(td)
-msgid "(StrOpt) Exchange name for Cinder notifications."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml:34(td)
-msgid "glance_control_exchange = glance"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml:35(td)
-msgid "(StrOpt) Exchange name for Glance notifications."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml:38(td)
-msgid "heat_control_exchange = heat"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml:39(td)
-msgid "(StrOpt) Exchange name for Heat notifications"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml:42(td)
-msgid "http_control_exchanges = ['nova', 'glance', 'neutron', 'cinder']"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml:43(td)
-msgid "(MultiStrOpt) Exchanges name to listen for notifications."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml:46(td)
-msgid "neutron_control_exchange = neutron"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml:47(td)
-msgid "(StrOpt) Exchange name for Neutron notifications."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml:50(td)
-msgid "nova_control_exchange = nova"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml:51(td)
-msgid "(StrOpt) Exchange name for Nova notifications."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml:54(td)
-msgid "sample_source = openstack"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml:55(td)
-msgid "(StrOpt) Source for samples emitted on this instance."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-common.xml:27(td)
-msgid "(BoolOpt) Whether to disable inter-process locks."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-common.xml:42(td)
-msgid "notification_workers = 1"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-common.xml:43(td)
-msgid "(IntOpt) Number of workers for notification service. A single notification agent is enabled by default."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml:8(caption)
-msgid "Description of configuration options for alarm"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml:19(th)
-msgid "[alarm]"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml:22(td)
-msgid "evaluation_interval = 60"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml:23(td)
-msgid "(IntOpt) Period of evaluation cycle, should be &gt;= than configured pipeline interval for collection of underlying metrics."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml:26(td)
-msgid "evaluation_service = ceilometer.alarm.service.SingletonAlarmService"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml:27(td)
-msgid "(StrOpt) Class to launch as alarm evaluation service."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml:30(td)
-msgid "notifier_rpc_topic = alarm_notifier"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml:31(td)
-msgid "(StrOpt) The topic that ceilometer uses for alarm notifier messages."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml:34(td)
-msgid "partition_rpc_topic = alarm_partition_coordination"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml:35(td)
-msgid "(StrOpt) The topic that ceilometer uses for alarm partition coordination messages."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml:38(td)
-msgid "record_history = True"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml:39(td)
-msgid "(BoolOpt) Record alarm change events."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml:42(td)
-msgid "rest_notifier_certificate_file ="
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml:43(td)
-msgid "(StrOpt) SSL Client certificate for REST notifier."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml:46(td)
-msgid "rest_notifier_certificate_key ="
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml:47(td)
-msgid "(StrOpt) SSL Client private key for REST notifier."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml:50(td)
-msgid "rest_notifier_ssl_verify = True"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml:51(td)
-msgid "(BoolOpt) Whether to verify the SSL Server certificate when calling alarm action."
-msgstr ""
-
-#: ./doc/common/tables/keystone-misc.xml:8(caption)
-msgid "Description of configuration options for misc"
+#: ./doc/common/tables/keystone-federation.xml:27(td)
+msgid "(StrOpt) Keystone Federation backend driver."
 msgstr ""
 
 #: ./doc/common/tables/nova-scheduling.xml:8(caption)
@@ -32875,10 +32467,6 @@ msgstr ""
 msgid "scheduler_default_filters = RetryFilter, AvailabilityZoneFilter, RamFilter, ComputeFilter, ComputeCapabilitiesFilter, ImagePropertiesFilter, ServerGroupAntiAffinityFilter, ServerGroupAffinityFilter"
 msgstr ""
 
-#: ./doc/common/tables/nova-scheduling.xml:79(td) ./doc/common/tables/cinder-scheduler.xml:23(td)
-msgid "(ListOpt) Which filter class names to use for filtering hosts when not specified in the request."
-msgstr ""
-
 #: ./doc/common/tables/nova-scheduling.xml:82(td)
 msgid "scheduler_driver = nova.scheduler.filter_scheduler.FilterScheduler"
 msgstr ""
@@ -32899,10 +32487,6 @@ msgstr ""
 msgid "scheduler_host_manager = nova.scheduler.host_manager.HostManager"
 msgstr ""
 
-#: ./doc/common/tables/nova-scheduling.xml:91(td) ./doc/common/tables/cinder-scheduler.xml:35(td)
-msgid "(StrOpt) The scheduler host manager class to use"
-msgstr ""
-
 #: ./doc/common/tables/nova-scheduling.xml:94(td)
 msgid "scheduler_host_subset_size = 1"
 msgstr ""
@@ -32911,14 +32495,6 @@ msgstr ""
 msgid "(IntOpt) New instances will be scheduled on a host chosen randomly from a subset of the N best hosts. This property defines the subset size that a host is chosen from. A value of 1 chooses the first host returned by the weighing functions. This value must be at least 1. Any value less than 1 will be ignored, and 1 will be used instead"
 msgstr ""
 
-#: ./doc/common/tables/nova-scheduling.xml:98(td) ./doc/common/tables/cinder-scheduler.xml:38(td)
-msgid "scheduler_json_config_location ="
-msgstr ""
-
-#: ./doc/common/tables/nova-scheduling.xml:99(td) ./doc/common/tables/cinder-scheduler.xml:39(td)
-msgid "(StrOpt) Absolute path to scheduler configuration JSON file."
-msgstr ""
-
 #: ./doc/common/tables/nova-scheduling.xml:102(td)
 msgid "scheduler_manager = nova.scheduler.manager.SchedulerManager"
 msgstr ""
@@ -32927,10 +32503,6 @@ msgstr ""
 msgid "(StrOpt) Full class name for the Manager for scheduler"
 msgstr ""
 
-#: ./doc/common/tables/nova-scheduling.xml:106(td) ./doc/common/tables/cinder-scheduler.xml:46(td)
-msgid "scheduler_max_attempts = 3"
-msgstr ""
-
 #: ./doc/common/tables/nova-scheduling.xml:107(td)
 msgid "(IntOpt) Maximum number of attempts to schedule an instance"
 msgstr ""
@@ -33023,224 +32595,644 @@ msgstr ""
 msgid "(ListOpt) How the metrics are going to be weighed. This should be in the form of \"&lt;name1&gt;=&lt;ratio1&gt;, &lt;name2&gt;=&lt;ratio2&gt;, ...\", where &lt;nameX&gt; is one of the metrics to be weighed, and &lt;ratioX&gt; is the corresponding ratio. So for \"name1=1.0, name2=-1.0\" The final weight would be name1.value * 1.0 + name2.value * -1.0."
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml:133(th)
-msgid "[service_credentials]"
+#: ./doc/common/tables/cinder-eqlx.xml:8(caption)
+msgid "Description of configuration options for eqlx"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml:137(td)
-msgid "(BoolOpt) Disables X.509 certificate validation when an SSL connection to Identity Service is established."
+#: ./doc/common/tables/cinder-eqlx.xml:22(td)
+msgid "eqlx_chap_login = admin"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml:140(td)
-msgid "os_auth_url = http://localhost:5000/v2.0"
+#: ./doc/common/tables/cinder-eqlx.xml:23(td)
+msgid "(StrOpt) Existing CHAP account name"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml:141(td)
-msgid "(StrOpt) Auth URL to use for OpenStack service access."
+#: ./doc/common/tables/cinder-eqlx.xml:26(td)
+msgid "eqlx_chap_password = password"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml:144(td)
-msgid "os_cacert = None"
+#: ./doc/common/tables/cinder-eqlx.xml:27(td)
+msgid "(StrOpt) Password for specified CHAP account name"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml:145(td)
-msgid "(StrOpt) Certificate chain for SSL validation."
+#: ./doc/common/tables/cinder-eqlx.xml:30(td)
+msgid "eqlx_cli_max_retries = 5"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml:148(td)
-msgid "os_endpoint_type = publicURL"
+#: ./doc/common/tables/cinder-eqlx.xml:31(td)
+msgid "(IntOpt) Maximum retry count for reconnection"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml:149(td)
-msgid "(StrOpt) Type of endpoint in Identity service catalog to use for communication with OpenStack services."
+#: ./doc/common/tables/cinder-eqlx.xml:34(td)
+msgid "eqlx_cli_timeout = 30"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml:152(td)
-msgid "os_password = admin"
+#: ./doc/common/tables/cinder-eqlx.xml:35(td)
+msgid "(IntOpt) Timeout for the Group Manager cli command execution"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml:153(td)
-msgid "(StrOpt) Password to use for OpenStack service access."
+#: ./doc/common/tables/cinder-eqlx.xml:38(td)
+msgid "eqlx_group_name = group-0"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml:157(td)
-msgid "(StrOpt) Region name to use for OpenStack service endpoints."
+#: ./doc/common/tables/cinder-eqlx.xml:39(td)
+msgid "(StrOpt) Group name to use for creating volumes"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml:160(td)
-msgid "os_tenant_id ="
+#: ./doc/common/tables/cinder-eqlx.xml:42(td)
+msgid "eqlx_pool = default"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml:161(td)
-msgid "(StrOpt) Tenant ID to use for OpenStack service access."
+#: ./doc/common/tables/cinder-eqlx.xml:43(td)
+msgid "(StrOpt) Pool in which volumes will be created"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml:164(td)
-msgid "os_tenant_name = admin"
+#: ./doc/common/tables/cinder-eqlx.xml:46(td)
+msgid "eqlx_use_chap = False"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml:165(td)
-msgid "(StrOpt) Tenant name to use for OpenStack service access."
+#: ./doc/common/tables/cinder-eqlx.xml:47(td)
+msgid "(BoolOpt) Use CHAP authentication for targets?"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml:168(td)
-msgid "os_username = ceilometer"
+#: ./doc/common/tables/heat-redis.xml:23(td)
+msgid "(StrOpt) Name of the engine node. This can be an opaque identifier. It is not necessarily a hostname, FQDN, or IP address."
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml:169(td)
-msgid "(StrOpt) User name to use for OpenStack service access."
+#: ./doc/common/tables/nova-ec2.xml:8(caption) ./doc/common/tables/keystone-ec2.xml:8(caption)
+msgid "Description of configuration options for ec2"
 msgstr ""
 
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:7(literal)
-msgid "[drive-audit]"
+#: ./doc/common/tables/nova-ec2.xml:22(td)
+msgid "ec2_dmz_host = $my_ip"
 msgstr ""
 
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:7(literal)
-msgid "drive-audit.conf-sample"
+#: ./doc/common/tables/nova-ec2.xml:23(td)
+msgid "(StrOpt) The internal IP address of the EC2 API server"
 msgstr ""
 
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:18(td)
-msgid "device_dir = /srv/node"
+#: ./doc/common/tables/nova-ec2.xml:26(td)
+msgid "ec2_host = $my_ip"
 msgstr ""
 
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:18(td)
-msgid "Directory devices are mounted under"
+#: ./doc/common/tables/nova-ec2.xml:27(td)
+msgid "(StrOpt) The IP address of the EC2 API server"
 msgstr ""
 
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:30(td)
-msgid "minutes = 60"
+#: ./doc/common/tables/nova-ec2.xml:30(td)
+msgid "ec2_listen = 0.0.0.0"
 msgstr ""
 
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:30(td)
-msgid "Number of minutes to look back in `/var/log/kern.log`"
+#: ./doc/common/tables/nova-ec2.xml:31(td)
+msgid "(StrOpt) The IP address on which the EC2 API will listen."
 msgstr ""
 
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:33(td)
-msgid "error_limit = 1"
+#: ./doc/common/tables/nova-ec2.xml:34(td)
+msgid "ec2_listen_port = 8773"
 msgstr ""
 
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:33(td)
-msgid "Number of errors to find before a device is unmounted"
+#: ./doc/common/tables/nova-ec2.xml:35(td)
+msgid "(IntOpt) The port on which the EC2 API will listen."
 msgstr ""
 
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:36(td)
-msgid "log_file_pattern = /var/log/kern*"
+#: ./doc/common/tables/nova-ec2.xml:38(td)
+msgid "ec2_path = /services/Cloud"
 msgstr ""
 
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:36(td)
-msgid "Location of the log file with globbing pattern to check against device errors locate device blocks with errors in the log file"
+#: ./doc/common/tables/nova-ec2.xml:39(td)
+msgid "(StrOpt) The path prefix used to call the ec2 API server"
 msgstr ""
 
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:39(td)
-msgid "regex_pattern_1 = \\berror\\b.*\\b(dm-[0-9]{1,2}\\d?)\\b"
+#: ./doc/common/tables/nova-ec2.xml:42(td)
+msgid "ec2_port = 8773"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_mlnx.xml:8(caption)
-msgid "Description of configuration options for ml2_mlnx"
+#: ./doc/common/tables/nova-ec2.xml:43(td)
+msgid "(IntOpt) The port of the EC2 API server"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_mlnx.xml:22(td)
-msgid "apply_profile_patch = False"
+#: ./doc/common/tables/nova-ec2.xml:46(td)
+msgid "ec2_private_dns_show_ip = False"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_mlnx.xml:23(td)
-msgid "(BoolOpt) Enable server compatibility with old nova"
+#: ./doc/common/tables/nova-ec2.xml:47(td)
+msgid "(BoolOpt) Return the IP address as private dns hostname in describe instances"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_mlnx.xml:26(td)
-msgid "vnic_type = mlnx_direct"
+#: ./doc/common/tables/nova-ec2.xml:50(td)
+msgid "ec2_scheme = http"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_mlnx.xml:27(td)
-msgid "(StrOpt) Type of VM network interface: mlnx_direct or hostdev"
+#: ./doc/common/tables/nova-ec2.xml:51(td)
+msgid "(StrOpt) The protocol to use when connecting to the EC2 API server (http, https)"
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml:8(caption)
-msgid "Description of configuration options for dns"
+#: ./doc/common/tables/nova-ec2.xml:54(td)
+msgid "ec2_strict_validation = True"
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml:22(td)
-msgid "dns_account_id ="
+#: ./doc/common/tables/nova-ec2.xml:55(td)
+msgid "(BoolOpt) Validate security group names according to EC2 specification"
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml:26(td)
-msgid "dns_auth_url ="
+#: ./doc/common/tables/nova-ec2.xml:58(td)
+msgid "ec2_timestamp_expiry = 300"
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml:30(td)
-msgid "dns_domain_id ="
+#: ./doc/common/tables/nova-ec2.xml:59(td)
+msgid "(IntOpt) Time in seconds before ec2 timestamp expires"
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml:34(td)
-msgid "dns_domain_name ="
+#: ./doc/common/tables/nova-ec2.xml:62(td)
+msgid "ec2_workers = None"
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml:38(td)
-msgid "dns_driver = trove.dns.driver.DnsDriver"
+#: ./doc/common/tables/nova-ec2.xml:63(td)
+msgid "(IntOpt) Number of workers for EC2 API service. The default will be equal to the number of CPUs available."
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml:42(td)
-msgid "dns_endpoint_url = 0.0.0.0"
+#: ./doc/common/tables/nova-ec2.xml:66(td) ./doc/common/tables/keystone-ec2.xml:38(td)
+msgid "keystone_ec2_url = http://localhost:5000/v2.0/ec2tokens"
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml:46(td)
-msgid "dns_hostname ="
+#: ./doc/common/tables/nova-ec2.xml:67(td) ./doc/common/tables/keystone-ec2.xml:39(td)
+msgid "(StrOpt) URL to get token from ec2 request."
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml:50(td)
-msgid "dns_instance_entry_factory = trove.dns.driver.DnsInstanceEntryFactory"
+#: ./doc/common/tables/nova-ec2.xml:70(td)
+msgid "lockout_attempts = 5"
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml:54(td)
-msgid "dns_management_base_url ="
+#: ./doc/common/tables/nova-ec2.xml:71(td)
+msgid "(IntOpt) Number of failed auths before lockout."
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml:58(td)
-msgid "dns_passkey ="
+#: ./doc/common/tables/nova-ec2.xml:74(td)
+msgid "lockout_minutes = 15"
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml:62(td)
-msgid "dns_region ="
+#: ./doc/common/tables/nova-ec2.xml:75(td)
+msgid "(IntOpt) Number of minutes to lockout if triggered."
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml:66(td)
-msgid "dns_service_type ="
+#: ./doc/common/tables/nova-ec2.xml:78(td)
+msgid "lockout_window = 15"
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml:70(td)
-msgid "dns_time_out = 120"
+#: ./doc/common/tables/nova-ec2.xml:79(td)
+msgid "(IntOpt) Number of minutes for lockout window."
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml:74(td)
-msgid "dns_ttl = 300"
+#: ./doc/common/tables/nova-ec2.xml:82(td)
+msgid "region_list ="
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml:78(td)
-msgid "dns_username ="
+#: ./doc/common/tables/nova-ec2.xml:83(td)
+msgid "(ListOpt) List of region=fqdn pairs separated by commas"
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml:82(td)
-msgid "trove_dns_support = False"
+#: ./doc/common/tables/keystone-credential.xml:8(caption)
+msgid "Description of configuration options for credential"
 msgstr ""
 
-#: ./doc/common/tables/neutron-db.xml:22(td)
-msgid "sqlite_db ="
+#: ./doc/common/tables/keystone-credential.xml:19(th)
+msgid "[credential]"
 msgstr ""
 
-#: ./doc/common/tables/neutron-db.xml:37(td)
-msgid "connection = sqlite://"
+#: ./doc/common/tables/keystone-credential.xml:22(td)
+msgid "driver = keystone.credential.backends.sql.Credential"
 msgstr ""
 
-#: ./doc/common/tables/neutron-db.xml:69(td)
-msgid "max_overflow = 20"
+#: ./doc/common/tables/cinder-block-device.xml:8(caption)
+msgid "Description of configuration options for block-device"
 msgstr ""
 
-#: ./doc/common/tables/neutron-db.xml:73(td)
-msgid "max_pool_size = 10"
+#: ./doc/common/tables/cinder-block-device.xml:22(td)
+msgid "available_devices ="
 msgstr ""
 
-#: ./doc/common/tables/neutron-db.xml:85(td)
-msgid "pool_timeout = 10"
+#: ./doc/common/tables/cinder-block-device.xml:23(td)
+msgid "(ListOpt) List of all available devices"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml:22(td)
+msgid "meta_flavor_driver_mappings = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml:23(td)
+msgid "(StrOpt) Mapping between flavor and LinuxInterfaceDriver"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml:26(td)
+msgid "metadata_backlog = 128"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml:27(td)
+msgid "(IntOpt) Number of backlog requests to configure the metadata server socket with"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml:30(td)
+msgid "metadata_port = 9697"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml:31(td)
+msgid "(IntOpt) TCP Port used by Neutron metadata namespace proxy."
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml:34(td)
+msgid "metadata_proxy_shared_secret ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml:38(td)
+msgid "metadata_proxy_socket = $state_path/metadata_proxy"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml:39(td)
+msgid "(StrOpt) Location of Metadata Proxy UNIX domain socket"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml:42(td)
+msgid "metadata_workers = 0"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml:43(td)
+msgid "(IntOpt) Number of separate worker processes for metadata server"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml:46(td)
+msgid "nova_metadata_ip = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml:47(td)
+msgid "(StrOpt) IP address used by Nova metadata server."
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml:50(td)
+msgid "nova_metadata_port = 8775"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml:51(td)
+msgid "(IntOpt) TCP Port used by Nova metadata server."
+msgstr ""
+
+#: ./doc/common/tables/nova-fping.xml:8(caption)
+msgid "Description of configuration options for fping"
+msgstr ""
+
+#: ./doc/common/tables/nova-fping.xml:22(td)
+msgid "fping_path = /usr/sbin/fping"
+msgstr ""
+
+#: ./doc/common/tables/nova-fping.xml:23(td)
+msgid "(StrOpt) Full path to fping."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml:7(literal)
+msgid "[filter:staticweb]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml:18(td)
+msgid "use = egg:swift#staticweb"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-replicator.xml:7(literal)
+msgid "[container-replicator]"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-replicator.xml:18(td)
+msgid "log_name = container-replicator"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ncs.xml:8(caption)
+msgid "Description of configuration options for ml2_ncs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ncs.xml:19(th)
+msgid "[ml2_ncs]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ncs.xml:23(td) ./doc/common/tables/neutron-ml2_odl.xml:23(td)
+msgid "(StrOpt) HTTP password for authentication"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ncs.xml:26(td) ./doc/common/tables/neutron-ml2_odl.xml:30(td)
+msgid "timeout = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ncs.xml:27(td) ./doc/common/tables/neutron-ml2_odl.xml:31(td)
+msgid "(IntOpt) HTTP timeout in seconds."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ncs.xml:31(td)
+msgid "(StrOpt) HTTP URL of Tail-f NCS REST interface."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ncs.xml:34(td) ./doc/common/tables/neutron-ml2_odl.xml:38(td)
+msgid "username = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ncs.xml:35(td) ./doc/common/tables/neutron-ml2_odl.xml:39(td)
+msgid "(StrOpt) HTTP username for authentication"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml:8(caption)
+msgid "Description of configuration options for ml2_arista"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml:19(th)
+msgid "[ml2_arista]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml:22(td)
+msgid "eapi_host ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml:23(td)
+msgid "(StrOpt) Arista EOS IP address. This is required field.If not set, all communications to Arista EOSwill fail"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml:26(td)
+msgid "eapi_password ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml:27(td)
+msgid "(StrOpt) Password for Arista EOS. This is required field.if not set, all communications to Arista EOSwill fail"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml:30(td)
+msgid "eapi_username ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml:31(td)
+msgid "(StrOpt) Username for Arista EOS. This is required field.if not set, all communications to Arista EOSwill fail"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml:34(td)
+msgid "region_name = RegionOne"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml:35(td)
+msgid "(StrOpt) Defines Region Name that is assigned to this OpenStackController. This is useful when multipleOpenStack/Neutron controllers are managing the sameArista HW clusters. Note that this name must match withthe region name registered (or known) to keystoneservice. Authentication with Keysotne is performed byEOS. This is optional. If not set, a value of\"RegionOne\" is assumed"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml:38(td)
+msgid "sync_interval = 180"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml:39(td)
+msgid "(IntOpt) Sync interval in seconds between Neutron plugin andEOS. This interval defines how often thesynchronization is performed. This is an optionalfield. If not set, a value of 180 seconds is assumed"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml:42(td)
+msgid "use_fqdn = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml:43(td)
+msgid "(BoolOpt) Defines if hostnames are sent to Arista EOS as FQDNs(\"node1.domain.com\") or as short names (\"node1\").This is optional. If not set, a value of \"True\"is assumed."
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml:8(caption)
+msgid "Description of configuration options for trustedcomputing"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml:19(th)
+msgid "[trusted_computing]"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml:22(td)
+msgid "attestation_api_url = /OpenAttestationWebServices/V1.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml:23(td)
+msgid "(StrOpt) Attestation web API URL"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml:26(td)
+msgid "attestation_auth_blob = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml:27(td)
+msgid "(StrOpt) Attestation authorization blob - must change"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml:30(td)
+msgid "attestation_auth_timeout = 60"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml:31(td)
+msgid "(IntOpt) Attestation status cache valid period length"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml:34(td)
+msgid "attestation_port = 8443"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml:35(td)
+msgid "(StrOpt) Attestation server port"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml:38(td)
+msgid "attestation_server = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml:39(td)
+msgid "(StrOpt) Attestation server HTTP"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml:42(td)
+msgid "attestation_server_ca_file = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml:43(td)
+msgid "(StrOpt) Attestation server Cert file for Identity verification"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml:7(literal)
+msgid "[filter:bulk]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml:18(td)
+msgid "use = egg:swift#bulk"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml:21(td)
+msgid "max_containers_per_extraction = 10000"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml:24(td)
+msgid "max_failed_extractions = 1000"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml:27(td)
+msgid "max_deletes_per_request = 10000"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml:30(td)
+msgid "max_failed_deletes = 1000"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml:33(td)
+msgid "yield_frequency = 10"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml:36(td)
+msgid "delete_container_retry_count = 0"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml:22(td)
+msgid "notify_nova_on_port_data_changes = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml:23(td)
+msgid "(BoolOpt) Send notification to nova when port data (fixed_ips/floatingip) changes so nova can update its cache."
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml:26(td)
+msgid "notify_nova_on_port_status_changes = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml:27(td)
+msgid "(BoolOpt) Send notification to nova when port status changes"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml:30(td)
+msgid "nova_admin_auth_url = http://localhost:5000/v2.0"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml:31(td)
+msgid "(StrOpt) Authorization URL for connecting to nova in admin context"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml:34(td)
+msgid "nova_admin_password = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml:35(td)
+msgid "(StrOpt) Password for connection to nova in admin context"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml:38(td)
+msgid "nova_admin_tenant_id = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml:39(td)
+msgid "(StrOpt) The uuid of the admin nova tenant"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml:42(td)
+msgid "nova_admin_username = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml:43(td)
+msgid "(StrOpt) Username for connecting to nova in admin context"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml:46(td)
+msgid "nova_region_name = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml:47(td)
+msgid "(StrOpt) Name of nova region to use. Useful if keystone manages more than one region."
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml:50(td)
+msgid "nova_url = http://127.0.0.1:8774"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml:51(td)
+msgid "(StrOpt) URL for connection to nova"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml:54(td)
+msgid "send_events_interval = 2"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml:55(td)
+msgid "(IntOpt) Number of seconds between sending events to nova if there are any events to send."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml:8(caption)
+msgid "Description of configuration options for imagecache"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml:22(td)
+msgid "cleanup_scrubber = False"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml:23(td)
+msgid "(BoolOpt) A boolean that determines if the scrubber should clean up the files it uses for taking data. Only one server in your deployment should be designated the cleanup host."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml:26(td)
+msgid "cleanup_scrubber_time = 86400"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml:27(td)
+msgid "(IntOpt) Items must have a modified time that is older than this value in order to be candidates for cleanup."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml:30(td)
+msgid "delayed_delete = False"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml:31(td)
+msgid "(BoolOpt) Turn on/off delayed delete."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml:34(td)
+msgid "image_cache_dir = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml:35(td)
+msgid "(StrOpt) Base directory that the Image Cache uses."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml:38(td)
+msgid "image_cache_driver = sqlite"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml:39(td)
+msgid "(StrOpt) The driver to use for image cache management."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml:42(td)
+msgid "image_cache_max_size = 10737418240"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml:43(td)
+msgid "(IntOpt) The maximum size in bytes that the cache can use."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml:46(td)
+msgid "image_cache_sqlite_db = cache.db"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml:47(td)
+msgid "(StrOpt) The path to the sqlite file database that will be used for image cache management."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml:50(td)
+msgid "image_cache_stall_time = 86400"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml:51(td)
+msgid "(IntOpt) The amount of time to let an image remain in the cache without being accessed."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml:54(td)
+msgid "scrub_time = 0"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml:55(td)
+msgid "(IntOpt) The amount of time in seconds to delay before performing a delete."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml:58(td)
+msgid "scrubber_datadir = /var/lib/glance/scrubber"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml:59(td)
+msgid "(StrOpt) Directory that the scrubber will use to track information about what to delete. Make sure this is set in glance-api.conf and glance-scrubber.conf."
 msgstr ""
 
 #: ./doc/common/tables/neutron-ml2_brocade.xml:8(caption)
@@ -33287,6 +33279,86 @@ msgstr ""
 msgid "(StrOpt) The SSH username to use"
 msgstr ""
 
+#: ./doc/common/tables/swift-account-server-account-auditor.xml:7(literal)
+msgid "[account-auditor]"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-auditor.xml:18(td)
+msgid "log_name = account-auditor"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-auditor.xml:39(td)
+msgid "accounts_per_second = 200"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-auditor.xml:39(td)
+msgid "Maximum accounts audited per second. Should be tuned according to individual system specs. 0 is unlimited."
+msgstr ""
+
+#: ./doc/common/tables/cinder-nas.xml:8(caption)
+msgid "Description of configuration options for nas"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nas.xml:22(td)
+msgid "nas_ip ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-nas.xml:23(td)
+msgid "(StrOpt) IP address or Hostname of NAS system."
+msgstr ""
+
+#: ./doc/common/tables/cinder-nas.xml:26(td)
+msgid "nas_login = admin"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nas.xml:27(td)
+msgid "(StrOpt) User name to connect to NAS system."
+msgstr ""
+
+#: ./doc/common/tables/cinder-nas.xml:30(td)
+msgid "nas_password ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-nas.xml:31(td)
+msgid "(StrOpt) Password to connect to NAS system."
+msgstr ""
+
+#: ./doc/common/tables/cinder-nas.xml:34(td)
+msgid "nas_private_key ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-nas.xml:35(td)
+msgid "(StrOpt) Filename of private key to use for SSH authentication."
+msgstr ""
+
+#: ./doc/common/tables/cinder-nas.xml:38(td)
+msgid "nas_ssh_port = 22"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nas.xml:39(td)
+msgid "(IntOpt) SSH port to use to connect to NAS system."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml:8(caption)
+msgid "Description of configuration options for netapp_cdot_nfs"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml:26(td)
+msgid "netapp_copyoffload_tool_path = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml:27(td)
+msgid "(StrOpt) This option specifies the path of the NetApp copy offload tool binary. Ensure that the binary has execute permissions set which allow the effective user of the cinder-volume process to execute the file."
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_swift.xml:8(caption)
+msgid "Description of configuration options for clients_swift"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_swift.xml:19(th)
+msgid "[clients_swift]"
+msgstr ""
+
 #: ./doc/common/tables/neutron-brocade.xml:8(caption)
 msgid "Description of configuration options for brocade"
 msgstr ""
@@ -33319,250 +33391,6 @@ msgstr ""
 msgid "username ="
 msgstr ""
 
-#: ./doc/common/tables/keystone-database.xml:74(td) ./doc/common/tables/glance-db.xml:74(td)
-msgid "mysql_sql_mode = TRADITIONAL"
-msgstr ""
-
-#: ./doc/common/tables/keystone-database.xml:75(td) ./doc/common/tables/glance-db.xml:75(td)
-msgid "(StrOpt) The SQL mode to be used for MySQL sessions. This option, including the default, overrides any server-set SQL mode. To use whatever SQL mode is set by the server configuration, set this to no value. Example: mysql_sql_mode="
-msgstr ""
-
-#: ./doc/common/tables/keystone-database.xml:86(td)
-msgid "sqlite_db = keystone.sqlite"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml:18(td)
-msgid "pipeline = catch_errors cache proxy-server"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_neutron.xml:8(caption)
-msgid "Description of configuration options for clients_neutron"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_neutron.xml:19(th)
-msgid "[clients_neutron]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml:8(caption)
-msgid "Description of configuration options for linuxbridge_agent"
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml:19(th)
-msgid "[LINUX_BRIDGE]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml:26(th)
-msgid "[VLANS]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml:37(th)
-msgid "[VXLAN]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml:40(td)
-msgid "enable_vxlan = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml:41(td)
-msgid "(BoolOpt) Enable VXLAN on the agent. Can be enabled when agent is managed by ml2 plugin using linuxbridge mechanism driver"
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml:45(td)
-msgid "(BoolOpt) Extension to use alongside ml2 plugin's l2population mechanism driver. It enables the plugin to populate VXLAN forwarding table."
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml:49(td)
-msgid "(StrOpt) Local IP address of the VXLAN endpoints."
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml:52(td)
-msgid "tos = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml:53(td)
-msgid "(IntOpt) TOS for vxlan interface protocol packets."
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml:56(td)
-msgid "ttl = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml:57(td)
-msgid "(IntOpt) TTL for vxlan interface protocol packets."
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml:60(td)
-msgid "vxlan_group = 224.0.0.1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml:61(td)
-msgid "(StrOpt) Multicast group for vxlan interface."
-msgstr ""
-
-#: ./doc/common/tables/cinder-xiv.xml:8(caption)
-msgid "Description of configuration options for xiv"
-msgstr ""
-
-#: ./doc/common/tables/cinder-xiv.xml:22(td)
-msgid "xiv_chap = disabled"
-msgstr ""
-
-#: ./doc/common/tables/cinder-xiv.xml:23(td)
-msgid "(StrOpt) CHAP authentication mode, effective only for iscsi (disabled|enabled)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-xiv.xml:26(td)
-msgid "xiv_ds8k_connection_type = iscsi"
-msgstr ""
-
-#: ./doc/common/tables/cinder-xiv.xml:27(td)
-msgid "(StrOpt) Connection type to the IBM Storage Array (fibre_channel|iscsi)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-xiv.xml:30(td)
-msgid "xiv_ds8k_proxy = xiv_ds8k_openstack.nova_proxy.XIVDS8KNovaProxy"
-msgstr ""
-
-#: ./doc/common/tables/cinder-xiv.xml:31(td)
-msgid "(StrOpt) Proxy driver that connects to the IBM Storage Array"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hds-hus.xml:8(caption)
-msgid "Description of configuration options for hds-hus"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hds-hus.xml:22(td)
-msgid "hds_cinder_config_file = /opt/hds/hus/cinder_hus_conf.xml"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hds-hus.xml:23(td)
-msgid "(StrOpt) configuration file for HDS cinder plugin for HUS"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rabbitmq.xml:35(td) ./doc/common/tables/ceilometer-rabbitmq.xml:55(td)
-msgid "(IntOpt) Maximum number of RabbitMQ connection retries. Default is 0 (infinite retry count)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rabbitmq.xml:39(td) ./doc/common/tables/ceilometer-rabbitmq.xml:59(td)
-msgid "(StrOpt) The RabbitMQ password"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rabbitmq.xml:47(td) ./doc/common/tables/ceilometer-rabbitmq.xml:67(td)
-msgid "(IntOpt) How long to backoff for between retries when connecting to RabbitMQ"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rabbitmq.xml:51(td) ./doc/common/tables/ceilometer-rabbitmq.xml:71(td)
-msgid "(IntOpt) How frequently to retry connecting with RabbitMQ"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rabbitmq.xml:55(td) ./doc/common/tables/ceilometer-rabbitmq.xml:75(td)
-msgid "(BoolOpt) Connect over SSL for RabbitMQ"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rabbitmq.xml:59(td) ./doc/common/tables/ceilometer-rabbitmq.xml:79(td)
-msgid "(StrOpt) The RabbitMQ userid"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rabbitmq.xml:63(td) ./doc/common/tables/ceilometer-rabbitmq.xml:83(td)
-msgid "(StrOpt) The RabbitMQ virtual host"
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml:8(caption)
-msgid "Description of configuration options for kvs"
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml:19(th)
-msgid "[kvs]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml:22(td)
-msgid "backends ="
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml:23(td)
-msgid "(ListOpt) Extra dogpile.cache backend modules to register with the dogpile.cache library."
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml:26(td)
-msgid "config_prefix = keystone.kvs"
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml:27(td)
-msgid "(StrOpt) Prefix for building the configuration dictionary for the KVS region. This should not need to be changed unless there is another dogpile.cache region with the same configuration name."
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml:30(td)
-msgid "default_lock_timeout = 5"
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml:31(td)
-msgid "(IntOpt) Default lock timeout for distributed locking."
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml:34(td)
-msgid "enable_key_mangler = True"
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml:35(td)
-msgid "(BoolOpt) Toggle to disable using a key-mangling function to ensure fixed length keys. This is toggle-able for debugging purposes, it is highly recommended to always leave this set to True."
-msgstr ""
-
-#: ./doc/common/tables/keystone-policy.xml:30(th)
-msgid "[policy]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-policy.xml:33(td)
-msgid "driver = keystone.policy.backends.sql.Policy"
-msgstr ""
-
-#: ./doc/common/tables/keystone-policy.xml:34(td)
-msgid "(StrOpt) Keystone Policy backend driver."
-msgstr ""
-
-#: ./doc/common/tables/keystone-policy.xml:38(td)
-msgid "(IntOpt) Maximum number of entities that will be returned in a policy collection."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml:7(literal)
-msgid "[filter:container-quotas]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml:18(td)
-msgid "use = egg:swift#container_quotas"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-hash.xml:7(literal)
-msgid "[swift-hash]"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-hash.xml:18(td)
-msgid "swift_hash_path_suffix = changeme"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-hash.xml:18(td)
-msgid "A suffix used by hash_path to offer a bit more security when generating hashes for paths. It simply appends this value to all paths; if someone knows this suffix, it's easier for them to guess the hash a path will end up with. New installations are advised to set this parameter to a random secret, which would not be disclosed ouside the organization. The same secret needs to be used by all swift servers of the same cluster. Existing installations should set this parameter to an empty string."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-hash.xml:29(td)
-msgid "swift_hash_path_prefix = changeme"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-hash.xml:29(td)
-msgid "A prefix used by hash_path to offer a bit more security when generating hashes for paths. It simply appends this value to all paths; if someone knows this suffix, it's easier for them to guess the hash a path will end up with. New installations are advised to set this parameter to a random secret, which would not be disclosed ouside the organization. The same secret needs to be used by all swift servers of the same cluster. Existing installations should set this parameter to an empty string."
-msgstr ""
-
-#: ./doc/common/tables/cinder-auth.xml:23(td)
-msgid "(StrOpt) The strategy to use for auth. Supports noauth, keystone, and deprecated."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml:7(literal)
-msgid "[filter:formpost]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml:18(td)
-msgid "use = egg:swift#formpost"
-msgstr ""
-
 #: ./doc/common/tables/neutron-ml2_odl.xml:8(caption)
 msgid "Description of configuration options for ml2_odl"
 msgstr ""
@@ -33571,10 +33399,6 @@ msgstr ""
 msgid "[ml2_odl]"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_odl.xml:23(td) ./doc/common/tables/neutron-ml2_ncs.xml:23(td)
-msgid "(StrOpt) HTTP password for authentication"
-msgstr ""
-
 #: ./doc/common/tables/neutron-ml2_odl.xml:26(td)
 msgid "session_timeout = 30"
 msgstr ""
@@ -33583,184 +33407,428 @@ msgstr ""
 msgid "(IntOpt) Tomcat session timeout in minutes."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_odl.xml:30(td) ./doc/common/tables/neutron-ml2_ncs.xml:26(td)
-msgid "timeout = 10"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_odl.xml:31(td) ./doc/common/tables/neutron-ml2_ncs.xml:27(td)
-msgid "(IntOpt) HTTP timeout in seconds."
-msgstr ""
-
 #: ./doc/common/tables/neutron-ml2_odl.xml:35(td)
 msgid "(StrOpt) HTTP URL of OpenDaylight REST interface."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_odl.xml:38(td) ./doc/common/tables/neutron-ml2_ncs.xml:34(td)
-msgid "username = None"
+#: ./doc/common/tables/swift-object-server-filter-recon.xml:24(td)
+msgid "recon_lock_path = /var/lock"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_odl.xml:39(td) ./doc/common/tables/neutron-ml2_ncs.xml:35(td)
-msgid "(StrOpt) HTTP username for authentication"
+#: ./doc/common/tables/cinder-connection.xml:8(caption)
+msgid "Description of configuration options for connection"
 msgstr ""
 
-#: ./doc/common/tables/heat-quota.xml:22(td)
-msgid "max_events_per_stack = 1000"
+#: ./doc/common/tables/cinder-connection.xml:22(td)
+msgid "connection = sqlite:///$state_path/$sqlite_db"
 msgstr ""
 
-#: ./doc/common/tables/heat-quota.xml:23(td)
-msgid "(IntOpt) Maximum events that will be available per stack. Older events will be deleted when this is reached. Set to 0 for unlimited events per stack."
+#: ./doc/common/tables/heat-rpc.xml:26(td)
+msgid "engine_life_check_timeout = 2"
 msgstr ""
 
-#: ./doc/common/tables/heat-quota.xml:26(td)
-msgid "max_nested_stack_depth = 3"
+#: ./doc/common/tables/heat-rpc.xml:27(td)
+msgid "(IntOpt) RPC timeout for the engine liveness check that is used for stack locking."
 msgstr ""
 
-#: ./doc/common/tables/heat-quota.xml:27(td)
-msgid "(IntOpt) Maximum depth allowed when using nested stacks."
+#: ./doc/common/tables/heat-rpc.xml:38(td)
+msgid "rpc_backend = heat.openstack.common.rpc.impl_kombu"
 msgstr ""
 
-#: ./doc/common/tables/heat-quota.xml:30(td)
-msgid "max_resources_per_stack = 1000"
+#: ./doc/common/tables/trove-taskmanager.xml:8(caption)
+msgid "Description of configuration options for taskmanager"
 msgstr ""
 
-#: ./doc/common/tables/heat-quota.xml:31(td)
-msgid "(IntOpt) Maximum resources allowed per top-level stack."
+#: ./doc/common/tables/trove-taskmanager.xml:22(td)
+msgid "cloudinit_location = /etc/trove/cloudinit"
 msgstr ""
 
-#: ./doc/common/tables/heat-quota.xml:34(td)
-msgid "max_stacks_per_tenant = 100"
+#: ./doc/common/tables/trove-taskmanager.xml:23(td)
+msgid "(StrOpt) Path to folder with cloudinit scripts."
 msgstr ""
 
-#: ./doc/common/tables/heat-quota.xml:35(td)
-msgid "(IntOpt) Maximum number of stacks any one tenant may have active at one time."
+#: ./doc/common/tables/trove-taskmanager.xml:26(td)
+msgid "datastore_manager = None"
 msgstr ""
 
-#: ./doc/common/tables/heat-quota.xml:38(td)
-msgid "max_template_size = 524288"
+#: ./doc/common/tables/trove-taskmanager.xml:27(td)
+msgid "(StrOpt) Manager class in guestagent, setup by taskmanager on instance provision."
 msgstr ""
 
-#: ./doc/common/tables/heat-quota.xml:39(td)
-msgid "(IntOpt) Maximum raw byte size of any template."
+#: ./doc/common/tables/trove-taskmanager.xml:30(td)
+msgid "datastore_registry_ext = {}"
 msgstr ""
 
-#: ./doc/common/tables/nova-spice.xml:8(caption)
-msgid "Description of configuration options for spice"
+#: ./doc/common/tables/trove-taskmanager.xml:31(td)
+msgid "(DictOpt) Extension for default datastore managers. Allows to use custom managers for each of datastore supported in trove."
 msgstr ""
 
-#: ./doc/common/tables/nova-spice.xml:19(th)
-msgid "[spice]"
+#: ./doc/common/tables/trove-taskmanager.xml:34(td)
+msgid "exists_notification_ticks = 360"
 msgstr ""
 
-#: ./doc/common/tables/nova-spice.xml:22(td)
-msgid "agent_enabled = True"
+#: ./doc/common/tables/trove-taskmanager.xml:35(td)
+msgid "(IntOpt) Number of report_intervals to wait between pushing events (see report_interval)."
 msgstr ""
 
-#: ./doc/common/tables/nova-spice.xml:23(td)
-msgid "(BoolOpt) Enable spice guest agent support"
+#: ./doc/common/tables/trove-taskmanager.xml:38(td)
+msgid "exists_notification_transformer = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-spice.xml:27(td)
-msgid "(BoolOpt) Enable spice related features"
+#: ./doc/common/tables/trove-taskmanager.xml:39(td)
+msgid "(StrOpt) Transformer for exists notifications."
 msgstr ""
 
-#: ./doc/common/tables/nova-spice.xml:30(td)
-msgid "html5proxy_base_url = http://127.0.0.1:6082/spice_auto.html"
+#: ./doc/common/tables/trove-taskmanager.xml:42(td)
+msgid "reboot_time_out = 120"
 msgstr ""
 
-#: ./doc/common/tables/nova-spice.xml:31(td)
-msgid "(StrOpt) Location of spice HTML5 console proxy, in the form \"http://127.0.0.1:6082/spice_auto.html\""
+#: ./doc/common/tables/trove-taskmanager.xml:46(td)
+msgid "resize_time_out = 600"
 msgstr ""
 
-#: ./doc/common/tables/nova-spice.xml:34(td)
-msgid "keymap = en-us"
+#: ./doc/common/tables/trove-taskmanager.xml:50(td)
+msgid "revert_time_out = 600"
 msgstr ""
 
-#: ./doc/common/tables/nova-spice.xml:35(td)
-msgid "(StrOpt) Keymap for spice"
+#: ./doc/common/tables/trove-taskmanager.xml:54(td)
+msgid "server_delete_time_out = 60"
 msgstr ""
 
-#: ./doc/common/tables/nova-spice.xml:38(td)
-msgid "server_listen = 127.0.0.1"
+#: ./doc/common/tables/trove-taskmanager.xml:58(td)
+msgid "state_change_wait_time = 180"
 msgstr ""
 
-#: ./doc/common/tables/nova-spice.xml:39(td)
-msgid "(StrOpt) IP address on which instance spice server should listen"
+#: ./doc/common/tables/trove-taskmanager.xml:62(td)
+msgid "update_status_on_fail = False"
 msgstr ""
 
-#: ./doc/common/tables/nova-spice.xml:42(td)
-msgid "server_proxyclient_address = 127.0.0.1"
+#: ./doc/common/tables/trove-taskmanager.xml:63(td)
+msgid "(BoolOpt) If instance fails to become active, taskmanager updates statuses, service status = FAILED_TIMEOUT_GUESTAGENT, instance task status = BUILDING_ERROR_TIMEOUT_GA."
 msgstr ""
 
-#: ./doc/common/tables/nova-spice.xml:43(td)
-msgid "(StrOpt) The address to which proxy clients (like nova-spicehtml5proxy) should connect"
+#: ./doc/common/tables/trove-taskmanager.xml:70(td)
+msgid "use_heat = False"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml:8(caption)
-msgid "Description of configuration options for zoning_fabric"
+#: ./doc/common/tables/trove-taskmanager.xml:74(td)
+msgid "use_nova_server_volume = False"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml:19(th)
-msgid "[BRCD_FABRIC_EXAMPLE]"
+#: ./doc/common/tables/trove-taskmanager.xml:78(td)
+msgid "verify_swift_checksum_on_restore = True"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml:22(td)
-msgid "fc_fabric_address ="
+#: ./doc/common/tables/trove-taskmanager.xml:79(td)
+msgid "(BoolOpt) Enable verification of swift checksum before starting restore; makes sure the checksum of original backup matches checksum of the swift backup file."
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml:23(td)
-msgid "(StrOpt) Management IP of fabric"
+#: ./doc/common/tables/heat-cloudwatch_api.xml:8(caption)
+msgid "Description of configuration options for cloudwatch_api"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml:26(td)
-msgid "fc_fabric_password ="
+#: ./doc/common/tables/heat-cloudwatch_api.xml:26(th)
+msgid "[heat_api_cloudwatch]"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml:27(td)
-msgid "(StrOpt) Password for user"
+#: ./doc/common/tables/heat-cloudwatch_api.xml:37(td)
+msgid "bind_port = 8003"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml:30(td)
-msgid "fc_fabric_port = 22"
+#: ./doc/common/tables/heat-cloudwatch_api.xml:50(td)
+msgid "(IntOpt) Maximum line size of message headers to be accepted. max_header_line may need to be increased when using large tokens (typically those generated by the Keystone v3 API with big service catalogs.)"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml:31(td)
-msgid "(IntOpt) Connecting port"
+#: ./doc/common/tables/cinder-images.xml:8(caption)
+msgid "Description of configuration options for images"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml:34(td)
-msgid "fc_fabric_user ="
+#: ./doc/common/tables/cinder-images.xml:23(td)
+msgid "(ListOpt) A list of url schemes that can be downloaded directly via the direct_url. Currently supported schemes: [file]."
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml:35(td)
-msgid "(StrOpt) Fabric user ID"
+#: ./doc/common/tables/cinder-images.xml:31(td)
+msgid "(ListOpt) A list of the glance api servers available to cinder ([hostname|ip]:port)"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml:38(td)
-msgid "principal_switch_wwn = None"
+#: ./doc/common/tables/cinder-images.xml:34(td)
+msgid "glance_api_ssl_compression = False"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml:39(td)
-msgid "(StrOpt) Principal switch WWN of the fabric"
+#: ./doc/common/tables/cinder-images.xml:35(td)
+msgid "(BoolOpt) Whether to attempt to negotiate SSL layer compression when using SSL (https) requests. Set to False to disable SSL layer compression. In some cases disabling this may improve data throughput, eg when high network bandwidth is available and you are using already compressed image formats such as qcow2 ."
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml:42(td)
-msgid "zone_activate = True"
+#: ./doc/common/tables/cinder-images.xml:38(td)
+msgid "glance_api_version = 1"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml:43(td)
-msgid "(BoolOpt) overridden zoning activation state"
+#: ./doc/common/tables/cinder-images.xml:39(td)
+msgid "(IntOpt) Version of the glance api to use"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml:46(td)
-msgid "zone_name_prefix = None"
+#: ./doc/common/tables/cinder-images.xml:43(td)
+msgid "(StrOpt) default glance hostname or ip"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml:47(td)
-msgid "(StrOpt) overridden zone name prefix"
+#: ./doc/common/tables/cinder-images.xml:47(td)
+msgid "(IntOpt) Number retries when downloading an image from glance"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml:51(td)
-msgid "(StrOpt) overridden zoning policy"
+#: ./doc/common/tables/cinder-images.xml:51(td)
+msgid "(IntOpt) default glance port"
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml:54(td)
+msgid "glance_request_timeout = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml:55(td)
+msgid "(IntOpt) http/https timeout value for glance operations. If no value (None) is supplied here, the glanceclient default value is used."
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml:58(td)
+msgid "image_conversion_dir = $state_path/conversion"
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml:59(td)
+msgid "(StrOpt) Directory used for temporary storage during image conversion"
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml:70(td)
+msgid "use_multipath_for_image_xfer = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml:71(td)
+msgid "(BoolOpt) Do we attach/detach volumes in cinder using multipath for volume to image and image to volume transfers?"
+msgstr ""
+
+#: ./doc/common/tables/cinder-huawei.xml:8(caption)
+msgid "Description of configuration options for huawei"
+msgstr ""
+
+#: ./doc/common/tables/cinder-huawei.xml:22(td)
+msgid "cinder_huawei_conf_file = /etc/cinder/cinder_huawei_conf.xml"
+msgstr ""
+
+#: ./doc/common/tables/cinder-huawei.xml:23(td)
+msgid "(StrOpt) config data for cinder huawei plugin"
+msgstr ""
+
+#: ./doc/common/tables/nova-console.xml:8(caption)
+msgid "Description of configuration options for console"
+msgstr ""
+
+#: ./doc/common/tables/nova-console.xml:22(td)
+msgid "console_public_hostname = oslo"
+msgstr ""
+
+#: ./doc/common/tables/nova-console.xml:23(td)
+msgid "(StrOpt) Publicly visible name for this console host"
+msgstr ""
+
+#: ./doc/common/tables/nova-console.xml:26(td)
+msgid "console_token_ttl = 600"
+msgstr ""
+
+#: ./doc/common/tables/nova-console.xml:27(td)
+msgid "(IntOpt) How many seconds before deleting tokens"
+msgstr ""
+
+#: ./doc/common/tables/nova-console.xml:30(td)
+msgid "consoleauth_manager = nova.consoleauth.manager.ConsoleAuthManager"
+msgstr ""
+
+#: ./doc/common/tables/nova-console.xml:31(td)
+msgid "(StrOpt) Manager for console auth"
+msgstr ""
+
+#: ./doc/common/tables/neutron-fwaas.xml:8(caption)
+msgid "Description of configuration options for fwaas"
+msgstr ""
+
+#: ./doc/common/tables/neutron-fwaas.xml:19(th) ./doc/common/tables/neutron-nec.xml:73(th)
+msgid "[fwaas]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-fwaas.xml:23(td)
+msgid "(BoolOpt) Enable FWaaS"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_nfs.xml:8(caption)
+msgid "Description of configuration options for nexenta_nfs"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_nfs.xml:22(td)
+msgid "nexenta_mount_point_base = $state_path/mnt"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_nfs.xml:23(td)
+msgid "(StrOpt) Base dir containing mount points for nfs shares"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_nfs.xml:26(td)
+msgid "nexenta_nms_cache_volroot = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_nfs.xml:27(td)
+msgid "(BoolOpt) If set True cache NexentaStor appliance volroot option value."
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_nfs.xml:30(td)
+msgid "nexenta_shares_config = /etc/cinder/nfs_shares"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_nfs.xml:34(td)
+msgid "nexenta_volume_compression = on"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_nfs.xml:35(td)
+msgid "(StrOpt) Default compression value for new ZFS folders."
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml:22(td)
+msgid "bandwidth_poll_interval = 600"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml:23(td)
+msgid "(IntOpt) Interval to pull network bandwidth usage info. Not supported on all hypervisors. Set to 0 to disable."
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml:26(td)
+msgid "enable_network_quota = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml:27(td)
+msgid "(BoolOpt) Enables or disables quota checking for tenant networks"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml:30(td)
+msgid "quota_cores = 20"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml:31(td)
+msgid "(IntOpt) Number of instance cores allowed per project"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml:34(td)
+msgid "quota_driver = nova.quota.DbQuotaDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml:38(td)
+msgid "quota_fixed_ips = -1"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml:39(td)
+msgid "(IntOpt) Number of fixed IPs allowed per project (this should be at least the number of instances allowed)"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml:42(td)
+msgid "quota_floating_ips = 10"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml:43(td)
+msgid "(IntOpt) Number of floating IPs allowed per project"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml:46(td)
+msgid "quota_injected_file_content_bytes = 10240"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml:47(td)
+msgid "(IntOpt) Number of bytes allowed per injected file"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml:50(td)
+msgid "quota_injected_file_path_bytes = 255"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml:51(td)
+msgid "(IntOpt) Number of bytes allowed per injected file path"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml:54(td)
+msgid "quota_injected_files = 5"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml:55(td)
+msgid "(IntOpt) Number of injected files allowed"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml:58(td)
+msgid "quota_instances = 10"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml:59(td)
+msgid "(IntOpt) Number of instances allowed per project"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml:62(td)
+msgid "quota_key_pairs = 100"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml:63(td)
+msgid "(IntOpt) Number of key pairs per user"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml:66(td)
+msgid "quota_metadata_items = 128"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml:67(td)
+msgid "(IntOpt) Number of metadata items allowed per instance"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml:70(td)
+msgid "quota_ram = 51200"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml:71(td)
+msgid "(IntOpt) Megabytes of instance RAM allowed per project"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml:74(td)
+msgid "quota_security_group_rules = 20"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml:75(td)
+msgid "(IntOpt) Number of security rules per security group"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml:78(td)
+msgid "quota_security_groups = 10"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml:79(td)
+msgid "(IntOpt) Number of security groups per project"
+msgstr ""
+
+#: ./doc/common/tables/keystone-stats.xml:8(caption)
+msgid "Description of configuration options for stats"
+msgstr ""
+
+#: ./doc/common/tables/keystone-stats.xml:19(th)
+msgid "[stats]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-stats.xml:22(td)
+msgid "driver = keystone.contrib.stats.backends.kvs.Stats"
+msgstr ""
+
+#: ./doc/common/tables/keystone-stats.xml:23(td)
+msgid "(StrOpt) Keystone stats backend driver."
+msgstr ""
+
+#: ./doc/common/tables/heat-crypt.xml:8(caption)
+msgid "Description of configuration options for crypt"
+msgstr ""
+
+#: ./doc/common/tables/heat-crypt.xml:22(td)
+msgid "auth_encryption_key = notgood but just long enough i think"
+msgstr ""
+
+#: ./doc/common/tables/heat-crypt.xml:23(td)
+msgid "(StrOpt) Encryption key used for authentication info in database."
 msgstr ""
 
 #: ./doc/common/tables/neutron-midonet.xml:8(caption)
@@ -33823,1312 +33891,188 @@ msgstr ""
 msgid "(StrOpt) MidoNet admin username."
 msgstr ""
 
-#: ./doc/common/tables/neutron-nvsd.xml:8(caption)
-msgid "Description of configuration options for nvsd"
+#: ./doc/common/tables/cinder-coraid.xml:8(caption)
+msgid "Description of configuration options for coraid"
 msgstr ""
 
-#: ./doc/common/tables/neutron-nvsd.xml:23(td)
-msgid "(StrOpt) integration bridge"
+#: ./doc/common/tables/cinder-coraid.xml:22(td)
+msgid "coraid_esm_address ="
 msgstr ""
 
-#: ./doc/common/tables/neutron-nvsd.xml:26(th)
-msgid "[nvsd]"
+#: ./doc/common/tables/cinder-coraid.xml:23(td)
+msgid "(StrOpt) IP address of Coraid ESM"
 msgstr ""
 
-#: ./doc/common/tables/neutron-nvsd.xml:29(td)
-msgid "nvsd_ip = 127.0.0.1"
+#: ./doc/common/tables/cinder-coraid.xml:26(td)
+msgid "coraid_group = admin"
 msgstr ""
 
-#: ./doc/common/tables/neutron-nvsd.xml:30(td)
-msgid "(StrOpt) NVSD Controller IP address"
+#: ./doc/common/tables/cinder-coraid.xml:27(td)
+msgid "(StrOpt) Name of group on Coraid ESM to which coraid_user belongs (must have admin privilege)"
 msgstr ""
 
-#: ./doc/common/tables/neutron-nvsd.xml:33(td)
-msgid "nvsd_passwd = oc123"
+#: ./doc/common/tables/cinder-coraid.xml:30(td)
+msgid "coraid_password = password"
 msgstr ""
 
-#: ./doc/common/tables/neutron-nvsd.xml:34(td)
-msgid "(StrOpt) NVSD Controller password"
+#: ./doc/common/tables/cinder-coraid.xml:31(td)
+msgid "(StrOpt) Password to connect to Coraid ESM"
 msgstr ""
 
-#: ./doc/common/tables/neutron-nvsd.xml:37(td)
-msgid "nvsd_port = 8082"
+#: ./doc/common/tables/cinder-coraid.xml:34(td)
+msgid "coraid_repository_key = coraid_repository"
 msgstr ""
 
-#: ./doc/common/tables/neutron-nvsd.xml:38(td)
-msgid "(IntOpt) NVSD Controller Port number"
+#: ./doc/common/tables/cinder-coraid.xml:35(td)
+msgid "(StrOpt) Volume Type key name to store ESM Repository Name"
 msgstr ""
 
-#: ./doc/common/tables/neutron-nvsd.xml:41(td)
-msgid "nvsd_retries = 0"
+#: ./doc/common/tables/cinder-coraid.xml:38(td)
+msgid "coraid_user = admin"
 msgstr ""
 
-#: ./doc/common/tables/neutron-nvsd.xml:42(td)
-msgid "(IntOpt) Number of login retries to NVSD controller"
+#: ./doc/common/tables/cinder-coraid.xml:39(td)
+msgid "(StrOpt) User name to connect to Coraid ESM"
 msgstr ""
 
-#: ./doc/common/tables/neutron-nvsd.xml:45(td)
-msgid "nvsd_user = ocplugin"
+#: ./doc/common/tables/neutron-wsgi.xml:8(caption) ./doc/common/tables/glance-wsgi.xml:8(caption) ./doc/common/tables/nova-wsgi.xml:8(caption)
+msgid "Description of configuration options for wsgi"
 msgstr ""
 
-#: ./doc/common/tables/neutron-nvsd.xml:46(td)
-msgid "(StrOpt) NVSD Controller username"
+#: ./doc/common/tables/neutron-wsgi.xml:23(td) ./doc/common/tables/trove-debug.xml:27(td)
+msgid "(IntOpt) Number of backlog requests to configure the socket with"
 msgstr ""
 
-#: ./doc/common/tables/neutron-nvsd.xml:49(td)
-msgid "request_timeout = 30"
+#: ./doc/common/tables/neutron-wsgi.xml:26(td)
+msgid "retry_until_window = 30"
 msgstr ""
 
-#: ./doc/common/tables/neutron-nvsd.xml:50(td)
-msgid "(IntOpt) NVSD controller REST API request timeout in seconds"
+#: ./doc/common/tables/neutron-wsgi.xml:27(td)
+msgid "(IntOpt) Number of seconds to keep retrying to listen"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane_lb.xml:8(caption)
-msgid "Description of configuration options for embrane_lb"
+#: ./doc/common/tables/cinder-compute.xml:22(td)
+msgid "nova_api_insecure = False"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane_lb.xml:19(th)
-msgid "[heleoslb]"
+#: ./doc/common/tables/cinder-compute.xml:23(td)
+msgid "(BoolOpt) Allow to perform insecure SSL requests to nova"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane_lb.xml:26(td)
-msgid "admin_username = None"
+#: ./doc/common/tables/cinder-compute.xml:26(td)
+msgid "nova_ca_certificates_file = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane_lb.xml:27(td) ./doc/common/tables/neutron-embrane.xml:23(td)
-msgid "(StrOpt) ESM admin username."
+#: ./doc/common/tables/cinder-compute.xml:27(td)
+msgid "(StrOpt) Location of ca certificates file to use for nova client requests."
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane_lb.xml:30(td)
-msgid "async_requests = None"
+#: ./doc/common/tables/cinder-compute.xml:30(td)
+msgid "nova_catalog_admin_info = compute:nova:adminURL"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane_lb.xml:31(td) ./doc/common/tables/neutron-embrane.xml:27(td)
-msgid "(BoolOpt) Define if the requests have run asynchronously or not"
+#: ./doc/common/tables/cinder-compute.xml:31(td)
+msgid "(StrOpt) Same as nova_catalog_info, but for admin endpoint."
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane_lb.xml:34(td) ./doc/common/tables/neutron-embrane.xml:30(td)
-msgid "dummy_utif_id = None"
+#: ./doc/common/tables/cinder-compute.xml:34(td)
+msgid "nova_catalog_info = compute:nova:publicURL"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane_lb.xml:35(td)
-msgid "(StrOpt) Dummy user traffic Security Zone id for LBs"
+#: ./doc/common/tables/cinder-compute.xml:35(td)
+msgid "(StrOpt) Info to match when looking for nova in the service catalog. Format is : separated values of the form: &lt;service_type&gt;:&lt;service_name&gt;:&lt;endpoint_type&gt;"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane_lb.xml:38(td) ./doc/common/tables/neutron-embrane.xml:34(td)
-msgid "esm_mgmt = None"
+#: ./doc/common/tables/cinder-compute.xml:38(td)
+msgid "nova_endpoint_admin_template = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane_lb.xml:39(td) ./doc/common/tables/neutron-embrane.xml:35(td)
-msgid "(StrOpt) ESM management root address"
+#: ./doc/common/tables/cinder-compute.xml:39(td)
+msgid "(StrOpt) Same as nova_endpoint_template, but for admin endpoint."
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane_lb.xml:42(td) ./doc/common/tables/neutron-embrane.xml:38(td)
-msgid "inband_id = None"
+#: ./doc/common/tables/cinder-compute.xml:42(td)
+msgid "nova_endpoint_template = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane_lb.xml:43(td)
-msgid "(StrOpt) In band Security Zone id for LBs"
+#: ./doc/common/tables/cinder-compute.xml:43(td)
+msgid "(StrOpt) Override service catalog lookup with template for nova endpoint e.g. http://localhost:8774/v2/%(project_id)s"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane_lb.xml:46(td)
-msgid "lb_flavor = small"
+#: ./doc/common/tables/cinder-compute.xml:47(td)
+msgid "(StrOpt) region name of this node"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane_lb.xml:47(td)
-msgid "(StrOpt) choose LB image flavor to use, accepted values: small, medium"
+#: ./doc/common/tables/swift-rsyncd-object.xml:7(literal)
+msgid "[object]"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane_lb.xml:50(td)
-msgid "lb_image = None"
+#: ./doc/common/tables/swift-rsyncd-object.xml:18(td)
+msgid "max connections = 8"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane_lb.xml:51(td)
-msgid "(StrOpt) Load Balancer image id (Embrane LB)"
+#: ./doc/common/tables/swift-rsyncd-object.xml:27(td)
+msgid "lock file = /var/lock/object.lock"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane_lb.xml:54(td) ./doc/common/tables/neutron-embrane.xml:42(td)
-msgid "mgmt_id = None"
+#: ./doc/common/tables/glance-wsgi.xml:23(td)
+msgid "(IntOpt) port for eventlet backdoor to listen"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane_lb.xml:55(td)
-msgid "(StrOpt) Management Security Zone id for LBs"
+#: ./doc/common/tables/glance-wsgi.xml:26(td)
+msgid "eventlet_hub = poll"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane_lb.xml:58(td) ./doc/common/tables/neutron-embrane.xml:46(td)
-msgid "oob_id = None"
+#: ./doc/common/tables/glance-wsgi.xml:27(td)
+msgid "(StrOpt) Name of eventlet hub to use. Traditionally, we have only supported 'poll', however 'selects' may be appropriate for some platforms. See http://eventlet.net/doc/hubs.html for more details."
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane_lb.xml:59(td)
-msgid "(StrOpt) Out of band Security Zone id for LBs"
+#: ./doc/common/tables/glance-wsgi.xml:35(td)
+msgid "(IntOpt) The value for the socket option TCP_KEEPIDLE. This is the time in seconds that the connection must be idle before TCP starts sending keepalive probes."
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane_lb.xml:62(td) ./doc/common/tables/neutron-vmware.xml:199(td)
-msgid "resource_pool_id = None"
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:7(literal)
+msgid "[drive-audit]"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane_lb.xml:63(td) ./doc/common/tables/neutron-embrane.xml:51(td)
-msgid "(StrOpt) Shared resource pool id"
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:7(literal)
+msgid "drive-audit.conf-sample"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane_lb.xml:66(td)
-msgid "sync_interval = 60"
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:18(td)
+msgid "device_dir = /srv/node"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane_lb.xml:67(td)
-msgid "(IntOpt) resource synchronization interval in seconds"
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:18(td)
+msgid "Directory devices are mounted under"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storwize.xml:8(caption)
-msgid "Description of configuration options for storwize"
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:30(td)
+msgid "minutes = 60"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storwize.xml:22(td)
-msgid "storwize_svc_connection_protocol = iSCSI"
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:30(td)
+msgid "Number of minutes to look back in `/var/log/kern.log`"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storwize.xml:23(td)
-msgid "(StrOpt) Connection protocol (iSCSI/FC)"
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:33(td)
+msgid "error_limit = 1"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storwize.xml:26(td)
-msgid "storwize_svc_flashcopy_timeout = 120"
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:33(td)
+msgid "Number of errors to find before a device is unmounted"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storwize.xml:27(td)
-msgid "(IntOpt) Maximum number of seconds to wait for FlashCopy to be prepared. Maximum value is 600 seconds (10 minutes)"
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:36(td)
+msgid "log_file_pattern = /var/log/kern*"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storwize.xml:30(td)
-msgid "storwize_svc_iscsi_chap_enabled = True"
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:36(td)
+msgid "Location of the log file with globbing pattern to check against device errors locate device blocks with errors in the log file"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storwize.xml:31(td)
-msgid "(BoolOpt) Configure CHAP authentication for iSCSI connections (Default: Enabled)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml:34(td)
-msgid "storwize_svc_multihostmap_enabled = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml:35(td)
-msgid "(BoolOpt) Allows vdisk to multi host mapping"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml:38(td)
-msgid "storwize_svc_multipath_enabled = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml:39(td)
-msgid "(BoolOpt) Connect with multipath (FC only; iSCSI multipath is controlled by Nova)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml:42(td)
-msgid "storwize_svc_vol_autoexpand = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml:43(td)
-msgid "(BoolOpt) Storage system autoexpand parameter for volumes (True/False)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml:46(td)
-msgid "storwize_svc_vol_compression = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml:47(td)
-msgid "(BoolOpt) Storage system compression option for volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml:50(td)
-msgid "storwize_svc_vol_easytier = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml:51(td)
-msgid "(BoolOpt) Enable Easy Tier for volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml:54(td)
-msgid "storwize_svc_vol_grainsize = 256"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml:55(td)
-msgid "(IntOpt) Storage system grain size parameter for volumes (32/64/128/256)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml:58(td)
-msgid "storwize_svc_vol_iogrp = 0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml:59(td)
-msgid "(IntOpt) The I/O group in which to allocate volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml:62(td)
-msgid "storwize_svc_vol_rsize = 2"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml:63(td)
-msgid "(IntOpt) Storage system space-efficiency parameter for volumes (percentage)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml:66(td)
-msgid "storwize_svc_vol_warning = 0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml:67(td)
-msgid "(IntOpt) Storage system threshold for volume capacity warnings (percentage)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml:70(td)
-msgid "storwize_svc_volpool_name = volpool"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml:71(td)
-msgid "(StrOpt) Storage system storage pool for volumes"
-msgstr ""
-
-#: ./doc/common/tables/nova-rootwrap.xml:22(td)
-msgid "filters_path = /etc/nova/rootwrap.d,/usr/share/nova/rootwrap"
-msgstr ""
-
-#: ./doc/common/tables/nova-rootwrap.xml:35(td)
-msgid "Which syslog facility to use. Valid values include auth, authpriv, syslog, user0, user1... Default value is 'syslog'"
-msgstr ""
-
-#: ./doc/common/tables/cinder-solidfire.xml:8(caption)
-msgid "Description of configuration options for solidfire"
-msgstr ""
-
-#: ./doc/common/tables/cinder-solidfire.xml:22(td)
-msgid "sf_account_prefix = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-solidfire.xml:23(td)
-msgid "(StrOpt) Create SolidFire accounts with this prefix. Any string can be used here, but the string \"hostname\" is special and will create a prefix using the cinder node hostsname (previous default behavior). The default is NO prefix."
-msgstr ""
-
-#: ./doc/common/tables/cinder-solidfire.xml:26(td)
-msgid "sf_allow_tenant_qos = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-solidfire.xml:27(td)
-msgid "(BoolOpt) Allow tenants to specify QOS on create"
-msgstr ""
-
-#: ./doc/common/tables/cinder-solidfire.xml:30(td)
-msgid "sf_api_port = 443"
-msgstr ""
-
-#: ./doc/common/tables/cinder-solidfire.xml:31(td)
-msgid "(IntOpt) SolidFire API port. Useful if the device api is behind a proxy on a different port."
-msgstr ""
-
-#: ./doc/common/tables/cinder-solidfire.xml:34(td)
-msgid "sf_emulate_512 = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-solidfire.xml:35(td)
-msgid "(BoolOpt) Set 512 byte emulation on volume creation;"
-msgstr ""
-
-#: ./doc/common/tables/keystone-revoke.xml:8(caption)
-msgid "Description of configuration options for revoke"
-msgstr ""
-
-#: ./doc/common/tables/keystone-revoke.xml:19(th)
-msgid "[revoke]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-revoke.xml:23(td)
-msgid "(BoolOpt) Toggle for revocation event cacheing. This has no effect unless global caching is enabled."
-msgstr ""
-
-#: ./doc/common/tables/keystone-revoke.xml:26(td)
-msgid "driver = keystone.contrib.revoke.backends.kvs.Revoke"
-msgstr ""
-
-#: ./doc/common/tables/keystone-revoke.xml:27(td)
-msgid "(StrOpt) An implementation of the backend for persisting revocation events."
-msgstr ""
-
-#: ./doc/common/tables/keystone-revoke.xml:30(td)
-msgid "expiration_buffer = 1800"
-msgstr ""
-
-#: ./doc/common/tables/keystone-revoke.xml:31(td)
-msgid "(IntOpt) This value (calculated in seconds) is added to token expiration before a revocation event may be removed from the backend."
-msgstr ""
-
-#: ./doc/common/tables/glance-ssl.xml:27(td)
-msgid "(StrOpt) Certificate file to use when starting API server securely."
-msgstr ""
-
-#: ./doc/common/tables/glance-ssl.xml:31(td)
-msgid "(StrOpt) Private key file to use when starting API server securely."
-msgstr ""
-
-#: ./doc/common/tables/heat-metadata_api.xml:8(caption)
-msgid "Description of configuration options for metadata_api"
-msgstr ""
-
-#: ./doc/common/tables/nova-apiv3.xml:8(caption)
-msgid "Description of configuration options for apiv3"
-msgstr ""
-
-#: ./doc/common/tables/nova-apiv3.xml:19(th)
-msgid "[osapi_v3]"
-msgstr ""
-
-#: ./doc/common/tables/nova-apiv3.xml:23(td)
-msgid "(BoolOpt) Whether the V3 API is enabled or not"
-msgstr ""
-
-#: ./doc/common/tables/nova-apiv3.xml:26(td)
-msgid "extensions_blacklist ="
-msgstr ""
-
-#: ./doc/common/tables/nova-apiv3.xml:27(td)
-msgid "(ListOpt) A list of v3 API extensions to never load. Specify the extension aliases here."
-msgstr ""
-
-#: ./doc/common/tables/nova-apiv3.xml:30(td)
-msgid "extensions_whitelist ="
-msgstr ""
-
-#: ./doc/common/tables/nova-apiv3.xml:31(td)
-msgid "(ListOpt) If the list is not empty then a v3 API extension will only be loaded if it exists in this list. Specify the extension aliases here."
-msgstr ""
-
-#: ./doc/common/tables/glance-db.xml:86(td)
-msgid "sqlite_db = glance.sqlite"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:22(td)
-msgid "default_interface_name = breth0"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:23(td)
-msgid "(StrOpt) Name of the interface on a L2 Gateway transport nodewhich should be used by default when setting up a network connection"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:26(td)
-msgid "default_l2_gw_service_uuid = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:27(td)
-msgid "(StrOpt) Unique identifier of the NSX L2 Gateway service which will be used by default for network gateways"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:30(td)
-msgid "default_l3_gw_service_uuid = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:31(td)
-msgid "(StrOpt) Unique identifier of the NSX L3 Gateway service which will be used for implementing routers and floating IPs"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:34(td)
-msgid "default_service_cluster_uuid = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:35(td)
-msgid "(StrOpt) Unique identifier of the Service Cluster which will be used by logical services like dhcp and metadata"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:38(td)
-msgid "default_tz_uuid = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:39(td)
-msgid "(StrOpt) This is uuid of the default NSX Transport zone that will be used for creating tunneled isolated \"Neutron\" networks. It needs to be created in NSX before starting Neutron with the nsx plugin."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:42(td)
-msgid "http_timeout = 10"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:43(td)
-msgid "(IntOpt) Time before aborting a request"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:46(td)
-msgid "nsx_controllers = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:47(td)
-msgid "(ListOpt) Lists the NSX controllers in this cluster"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:50(td)
-msgid "nsx_password = admin"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:51(td)
-msgid "(StrOpt) Password for NSX controllers in this cluster"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:54(td)
-msgid "nsx_user = admin"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:55(td)
-msgid "(StrOpt) User name for NSX controllers in this cluster"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:58(td)
-msgid "redirects = 2"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:59(td)
-msgid "(IntOpt) Number of times a redirect should be followed"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:62(td)
-msgid "req_timeout = 30"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:63(td)
-msgid "(IntOpt) Total time limit for a cluster request"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:66(td)
-msgid "retries = 2"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:67(td)
-msgid "(IntOpt) Number of time a request should be retried"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:73(td)
-msgid "retries = 3"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:74(td)
-msgid "(IntOpt) The number of retries the agent will send request to daemon before giving up"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:77(th)
-msgid "[NSX]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:80(td)
-msgid "agent_mode = agent"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:81(td)
-msgid "(StrOpt) The mode used to implement DHCP/metadata services."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:84(td)
-msgid "concurrent_connections = 10"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:85(td)
-msgid "(IntOpt) Maximum concurrent connections to each NSX controller."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:88(td)
-msgid "default_transport_type = stt"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:89(td)
-msgid "(StrOpt) The default network tranport type to use (stt, gre, bridge, ipsec_gre, or ipsec_stt)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:92(td)
-msgid "max_lp_per_bridged_ls = 5000"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:93(td)
-msgid "(IntOpt) Maximum number of ports of a logical switch on a bridged transport zone (default 5000)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:96(td)
-msgid "max_lp_per_overlay_ls = 256"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:97(td)
-msgid "(IntOpt) Maximum number of ports of a logical switch on an overlay transport zone (default 256)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:100(td)
-msgid "metadata_mode = access_network"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:101(td)
-msgid "(StrOpt) If set to access_network this enables a dedicated connection to the metadata proxy for metadata server access via Neutron router. If set to dhcp_host_route this enables host route injection via the dhcp agent. This option is only useful if running on a host that does not support namespaces otherwise access_network should be used."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:104(td)
-msgid "nsx_gen_timeout = -1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:105(td)
-msgid "(IntOpt) Number of seconds a generation id should be valid for (default -1 meaning do not time out)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:108(td)
-msgid "replication_mode = service"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:109(td)
-msgid "(StrOpt) The default option leverages service nodes to perform packet replication though one could set to this to 'source' to perform replication locally. This is useful if one does not want to deploy a service node(s)."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:112(th)
-msgid "[NSX_DHCP]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:115(td)
-msgid "default_lease_time = 43200"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:116(td)
-msgid "(IntOpt) Default DHCP lease time"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:119(td)
-msgid "domain_name = openstacklocal"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:123(td)
-msgid "extra_domain_name_servers ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:124(td)
-msgid "(ListOpt) Comma separated list of additional domain name servers"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:127(th)
-msgid "[NSX_LSN]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:130(td)
-msgid "sync_on_missing_data = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:131(td)
-msgid "(BoolOpt) Pull LSN information from NSX in case it is missing from the local data store. This is useful to rebuild the local store in case of server recovery."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:134(th)
-msgid "[NSX_METADATA]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:137(td)
-msgid "metadata_server_address = 127.0.0.1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:138(td)
-msgid "(StrOpt) IP address used by Metadata server."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:141(td)
-msgid "metadata_server_port = 8775"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:142(td)
-msgid "(IntOpt) TCP Port used by Metadata server."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:145(td)
-msgid "metadata_shared_secret ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:149(th)
-msgid "[NSX_SYNC]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:152(td)
-msgid "always_read_status = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:153(td)
-msgid "(BoolOpt) Always read operational status from backend on show operations. Enabling this option might slow down the system."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:156(td)
-msgid "max_random_sync_delay = 0"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:157(td)
-msgid "(IntOpt) Maximum value for the additional random delay in seconds between runs of the state synchronization task"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:160(td)
-msgid "min_chunk_size = 500"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:161(td)
-msgid "(IntOpt) Minimum number of resources to be retrieved from NSX during state synchronization"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:164(td)
-msgid "min_sync_req_delay = 1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:165(td)
-msgid "(IntOpt) Minimum delay, in seconds, between two state synchronization queries to NSX. It must not exceed state_sync_interval"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:168(td)
-msgid "state_sync_interval = 10"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:169(td)
-msgid "(IntOpt) Interval in seconds between runs of the state synchronization task. Set it to 0 to disable it"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:172(th)
-msgid "[vcns]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:175(td)
-msgid "datacenter_moid = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:176(td)
-msgid "(StrOpt) Optional parameter identifying the ID of datacenter to deploy NSX Edges"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:179(td)
-msgid "datastore_id = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:180(td) ./doc/common/tables/neutron-vmware.xml:184(td)
-msgid "(StrOpt) Optional parameter identifying the ID of datastore to deploy NSX Edges"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:183(td)
-msgid "deployment_container_id = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:187(td)
-msgid "external_network = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:188(td)
-msgid "(StrOpt) Network ID for physical network connectivity"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:191(td)
-msgid "manager_uri = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:192(td)
-msgid "(StrOpt) uri for vsm"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:195(td)
-msgid "password = default"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:196(td)
-msgid "(StrOpt) Password for vsm"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:200(td)
-msgid "(StrOpt) Optional parameter identifying the ID of resource to deploy NSX Edges"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:203(td)
-msgid "task_status_check_interval = 2000"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:204(td)
-msgid "(IntOpt) Task status check interval"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:207(td)
-msgid "user = admin"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml:208(td)
-msgid "(StrOpt) User name for vsm"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml:7(literal)
-msgid "[realm2]"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml:18(td)
-msgid "key = realm2key"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml:21(td)
-msgid "key2 = realm2key2"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml:24(td)
-msgid "cluster_name3 = https://host3/v1/"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml:27(td)
-msgid "cluster_name4 = https://host4/v1/"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:22(td)
-msgid "api_rate_limit = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:23(td)
-msgid "(BoolOpt) Whether to use per-user rate limiting for the api. This option is only used by v2 api. Rate limiting is removed from v3 api."
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:30(td)
-msgid "enabled_apis = ec2, osapi_compute, metadata"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:31(td)
-msgid "(ListOpt) A list of APIs to enable by default"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:34(td)
-msgid "enabled_ssl_apis ="
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:35(td)
-msgid "(ListOpt) A list of APIs with enabled SSL"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:38(td)
-msgid "instance_name_template = instance-%08x"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:39(td)
-msgid "(StrOpt) Template string to be used to generate instance names"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:46(td)
-msgid "multi_instance_display_name_template = %(name)s-%(uuid)s"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:47(td)
-msgid "(StrOpt) When creating multiple instances with a single request using the os-multiple-create API extension, this template will be used to build the display name for each instance. The benefit is that the instances end up with different hostnames. To restore legacy behavior of every instance having the same name, set this option to \"%(name)s\". Valid keys for the template are: name, uuid, count."
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:50(td)
-msgid "non_inheritable_image_properties = cache_in_nova, bittorrent"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:51(td)
-msgid "(ListOpt) These are image properties which a snapshot should not inherit from an instance"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:54(td)
-msgid "null_kernel = nokernel"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:55(td)
-msgid "(StrOpt) Kernel image that indicates not to use a kernel, but to use a raw disk image instead"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:58(td)
-msgid "osapi_compute_ext_list ="
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:59(td)
-msgid "(ListOpt) Specify list of extensions to load when using osapi_compute_extension option with nova.api.openstack.compute.contrib.select_extensions"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:62(td)
-msgid "osapi_compute_extension = ['nova.api.openstack.compute.contrib.standard_extensions']"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:63(td)
-msgid "(MultiStrOpt) osapi compute extension to load"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:66(td)
-msgid "osapi_compute_link_prefix = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:67(td)
-msgid "(StrOpt) Base URL that will be presented to users in links to the OpenStack Compute API"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:70(td)
-msgid "osapi_compute_listen = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:71(td)
-msgid "(StrOpt) The IP address on which the OpenStack API will listen."
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:74(td)
-msgid "osapi_compute_listen_port = 8774"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:75(td)
-msgid "(IntOpt) The port on which the OpenStack API will listen."
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:78(td)
-msgid "osapi_compute_workers = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:79(td)
-msgid "(IntOpt) Number of workers for OpenStack API service. The default will be the number of CPUs available."
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:82(td)
-msgid "osapi_hide_server_address_states = building"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:83(td)
-msgid "(ListOpt) List of instance states that should hide network info"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:86(td)
-msgid "servicegroup_driver = db"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml:87(td)
-msgid "(StrOpt) The driver for servicegroup service (valid options are: db, zk, mc)"
-msgstr ""
-
-#: ./doc/common/tables/glance-matchmaker.xml:8(caption)
-msgid "Description of configuration options for matchmaker"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:19(th)
-msgid "[signing]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:22(td) ./doc/common/tables/keystone-ssl.xml:57(td)
-msgid "ca_certs = /etc/keystone/ssl/certs/ca.pem"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:23(td)
-msgid "(StrOpt) Path of the CA for token signing."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:26(td) ./doc/common/tables/keystone-ssl.xml:61(td)
-msgid "ca_key = /etc/keystone/ssl/private/cakey.pem"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:27(td)
-msgid "(StrOpt) Path of the CA Key for token signing."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:30(td)
-msgid "cert_subject = /C=US/ST=Unset/L=Unset/O=Unset/CN=www.example.com"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:31(td)
-msgid "(StrOpt) Certificate Subject (auto generated certificate) for token signing."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:34(td)
-msgid "certfile = /etc/keystone/ssl/certs/signing_cert.pem"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:35(td)
-msgid "(StrOpt) Path of the certfile for token signing."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:38(td)
-msgid "key_size = 2048"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:39(td)
-msgid "(IntOpt) Key Size (in bits) for token signing cert (auto generated certificate)."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:42(td)
-msgid "keyfile = /etc/keystone/ssl/private/signing_key.pem"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:43(td)
-msgid "(StrOpt) Path of the keyfile for token signing."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:46(td)
-msgid "token_format = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:47(td)
-msgid "(StrOpt) Deprecated in favor of provider in the [token] section."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:50(td) ./doc/common/tables/keystone-ssl.xml:89(td)
-msgid "valid_days = 3650"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:51(td)
-msgid "(IntOpt) Day the token signing cert is valid for (auto generated certificate)."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:58(td)
-msgid "(StrOpt) Path of the ca cert file for SSL."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:62(td)
-msgid "(StrOpt) Path of the CA key file for SSL."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:65(td)
-msgid "cert_required = False"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:66(td)
-msgid "(BoolOpt) Require client certificate."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:69(td)
-msgid "cert_subject = /C=US/ST=Unset/L=Unset/O=Unset/CN=localhost"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:70(td)
-msgid "(StrOpt) SSL Certificate Subject (auto generated certificate)."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:73(td)
-msgid "certfile = /etc/keystone/ssl/certs/keystone.pem"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:74(td)
-msgid "(StrOpt) Path of the certfile for SSL."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:78(td)
-msgid "(BoolOpt) Toggle for SSL support on the keystone eventlet servers."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:81(td)
-msgid "key_size = 1024"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:82(td)
-msgid "(IntOpt) SSL Key Length (in bits) (auto generated certificate)."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:85(td)
-msgid "keyfile = /etc/keystone/ssl/private/keystonekey.pem"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:86(td)
-msgid "(StrOpt) Path of the keyfile for SSL."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml:90(td)
-msgid "(IntOpt) Days the certificate is valid for once signed (auto generated certificate)."
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-container.xml:7(literal)
-msgid "[container]"
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-container.xml:18(td)
-msgid "max connections = 4"
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-container.xml:27(td)
-msgid "lock file = /var/lock/container.lock"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san-solaris.xml:8(caption)
-msgid "Description of configuration options for san-solaris"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san-solaris.xml:22(td)
-msgid "san_zfs_volume_base = rpool/"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san-solaris.xml:23(td)
-msgid "(StrOpt) The ZFS path under which to create zvols for volumes."
-msgstr ""
-
-#: ./doc/common/tables/trove-heat.xml:8(caption)
-msgid "Description of configuration options for heat"
-msgstr ""
-
-#: ./doc/common/tables/trove-heat.xml:22(td)
-msgid "heat_time_out = 60"
-msgstr ""
-
-#: ./doc/common/tables/trove-heat.xml:26(td)
-msgid "heat_url = http://localhost:8004/v1"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml:8(caption)
-msgid "Description of configuration options for netapp_cdot_nfs"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml:26(td)
-msgid "netapp_copyoffload_tool_path = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml:27(td)
-msgid "(StrOpt) This option specifies the path of the NetApp copy offload tool binary. Ensure that the binary has execute permissions set which allow the effective user of the cinder-volume process to execute the file."
-msgstr ""
-
-#: ./doc/common/tables/glance-paste.xml:8(caption)
-msgid "Description of configuration options for paste"
-msgstr ""
-
-#: ./doc/common/tables/glance-paste.xml:22(td)
-msgid "config_file = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-paste.xml:23(td)
-msgid "(StrOpt) Name of the paste configuration file."
-msgstr ""
-
-#: ./doc/common/tables/glance-paste.xml:27(td)
-msgid "(StrOpt) Partial name of a pipeline in your paste configuration file with the service name removed. For example, if your paste section name is [pipeline:glance-api-keystone] use the value \"keystone\""
-msgstr ""
-
-#: ./doc/common/tables/nova-rdp.xml:8(caption)
-msgid "Description of configuration options for rdp"
-msgstr ""
-
-#: ./doc/common/tables/nova-rdp.xml:19(th)
-msgid "[rdp]"
-msgstr ""
-
-#: ./doc/common/tables/nova-rdp.xml:23(td)
-msgid "(BoolOpt) Enable RDP related features"
-msgstr ""
-
-#: ./doc/common/tables/nova-rdp.xml:26(td)
-msgid "html5_proxy_base_url = http://127.0.0.1:6083/"
-msgstr ""
-
-#: ./doc/common/tables/nova-rdp.xml:27(td)
-msgid "(StrOpt) Location of RDP html5 console proxy, in the form \"http://127.0.0.1:6083/\""
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:8(caption)
-msgid "Description of configuration options for quotas"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:22(td)
-msgid "max_routes = 30"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:23(td)
-msgid "(IntOpt) Maximum number of routes"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:26(th)
-msgid "[QUOTAS]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:29(td)
-msgid "default_quota = -1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:30(td)
-msgid "(IntOpt) Default number of resource allowed per tenant. A negative value means unlimited."
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:33(td)
-msgid "quota_driver = neutron.db.quota_db.DbQuotaDriver"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:34(td) ./doc/common/tables/nova-quota.xml:35(td)
-msgid "(StrOpt) Default driver to use for quota checks"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:37(td)
-msgid "quota_firewall = 1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:38(td)
-msgid "(IntOpt) Number of firewalls allowed per tenant. A negative value means unlimited."
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:41(td)
-msgid "quota_firewall_policy = 1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:42(td)
-msgid "(IntOpt) Number of firewall policies allowed per tenant. A negative value means unlimited."
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:45(td)
-msgid "quota_firewall_rule = -1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:46(td)
-msgid "(IntOpt) Number of firewall rules allowed per tenant. A negative value means unlimited."
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:49(td)
-msgid "quota_floatingip = 50"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:50(td)
-msgid "(IntOpt) Number of floating IPs allowed per tenant. A negative value means unlimited."
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:53(td)
-msgid "quota_health_monitor = -1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:54(td)
-msgid "(IntOpt) Number of health monitors allowed per tenant. A negative value means unlimited."
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:57(td)
-msgid "quota_items = network, subnet, port"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:58(td)
-msgid "(ListOpt) Resource name(s) that are supported in quota features"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:61(td)
-msgid "quota_member = -1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:62(td)
-msgid "(IntOpt) Number of pool members allowed per tenant. A negative value means unlimited."
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:65(td)
-msgid "quota_network = 10"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:66(td)
-msgid "(IntOpt) Number of networks allowed per tenant.A negative value means unlimited."
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:69(td)
-msgid "quota_network_gateway = 5"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:70(td)
-msgid "(IntOpt) Number of network gateways allowed per tenant, -1 for unlimited"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:73(td)
-msgid "quota_packet_filter = 100"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:74(td)
-msgid "(IntOpt) Number of packet_filters allowed per tenant, -1 for unlimited"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:77(td)
-msgid "quota_pool = 10"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:78(td)
-msgid "(IntOpt) Number of pools allowed per tenant. A negative value means unlimited."
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:81(td)
-msgid "quota_port = 50"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:82(td)
-msgid "(IntOpt) Number of ports allowed per tenant. A negative value means unlimited."
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:85(td)
-msgid "quota_router = 10"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:86(td)
-msgid "(IntOpt) Number of routers allowed per tenant. A negative value means unlimited."
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:89(td)
-msgid "quota_security_group = 10"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:90(td)
-msgid "(IntOpt) Number of security groups allowed per tenant. A negative value means unlimited."
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:93(td)
-msgid "quota_security_group_rule = 100"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:94(td)
-msgid "(IntOpt) Number of security rules allowed per tenant. A negative value means unlimited."
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:97(td)
-msgid "quota_subnet = 10"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:98(td)
-msgid "(IntOpt) Number of subnets allowed per tenant, A negative value means unlimited."
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:101(td)
-msgid "quota_vip = 10"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml:102(td)
-msgid "(IntOpt) Number of vips allowed per tenant. A negative value means unlimited."
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml:8(caption)
-msgid "Description of configuration options for guestagent"
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml:22(td)
-msgid "agent_call_high_timeout = 60"
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml:26(td)
-msgid "agent_call_low_timeout = 5"
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml:30(td)
-msgid "agent_heartbeat_time = 10"
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml:34(td)
-msgid "guest_config = $pybasedir/etc/trove/trove-guestagent.conf.sample"
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml:35(td)
-msgid "(StrOpt) Path to guestagent config file."
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml:38(td)
-msgid "guest_id = None"
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml:42(td)
-msgid "ignore_dbs = lost+found, mysql, information_schema"
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml:46(td)
-msgid "ignore_users = os_admin, root"
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml:50(td)
-msgid "mount_options = defaults,noatime"
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml:54(td)
-msgid "restore_namespace = trove.guestagent.strategies.restore.mysql_impl"
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml:55(td)
-msgid "(StrOpt) Namespace to load restore strategies from."
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml:58(td)
-msgid "storage_namespace = trove.guestagent.strategies.storage.swift"
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml:59(td)
-msgid "(StrOpt) Namespace to load the default storage strategy from."
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml:62(td)
-msgid "storage_strategy = SwiftStorage"
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml:63(td)
-msgid "(StrOpt) Default strategy to store backups."
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml:39(td)
+msgid "regex_pattern_1 = \\berror\\b.*\\b(dm-[0-9]{1,2}\\d?)\\b"
 msgstr ""
 
 #: ./doc/common/tables/nova-baremetal.xml:8(caption)
@@ -35355,352 +34299,136 @@ msgstr ""
 msgid "(StrOpt) The XenAPI VIF driver using XenServer Network APIs."
 msgstr ""
 
-#: ./doc/common/tables/heat-clients_keystone.xml:8(caption)
-msgid "Description of configuration options for clients_keystone"
+#: ./doc/common/tables/cinder-backups_tsm.xml:8(caption)
+msgid "Description of configuration options for backups_tsm"
 msgstr ""
 
-#: ./doc/common/tables/heat-clients_keystone.xml:19(th)
-msgid "[clients_keystone]"
+#: ./doc/common/tables/cinder-backups_tsm.xml:22(td)
+msgid "backup_tsm_compression = True"
 msgstr ""
 
-#: ./doc/common/tables/swift-account-server-pipeline-main.xml:18(td)
-msgid "pipeline = healthcheck recon account-server"
+#: ./doc/common/tables/cinder-backups_tsm.xml:23(td)
+msgid "(BoolOpt) Enable or Disable compression for backups"
 msgstr ""
 
-#: ./doc/common/tables/keystone-rabbit.xml:8(caption)
-msgid "Description of configuration options for rabbit"
+#: ./doc/common/tables/cinder-backups_tsm.xml:26(td)
+msgid "backup_tsm_password = password"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml:22(td)
-msgid "admin_role = admin"
+#: ./doc/common/tables/cinder-backups_tsm.xml:27(td)
+msgid "(StrOpt) TSM password for the running username"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml:23(td)
-msgid "(StrOpt) Role used to identify an authenticated user as administrator."
+#: ./doc/common/tables/cinder-backups_tsm.xml:30(td)
+msgid "backup_tsm_volume_prefix = backup"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml:26(td)
-msgid "allow_anonymous_access = False"
+#: ./doc/common/tables/cinder-backups_tsm.xml:31(td)
+msgid "(StrOpt) Volume prefix for the backup id when backing up to TSM"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml:27(td)
-msgid "(BoolOpt) Allow unauthenticated users to access the API with read-only privileges. This only applies when using ContextMiddleware."
+#: ./doc/common/tables/cinder-san.xml:8(caption)
+msgid "Description of configuration options for san"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml:30(td)
-msgid "default_publisher_id = image.localhost"
+#: ./doc/common/tables/cinder-san.xml:22(td)
+msgid "san_clustername ="
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml:31(td)
-msgid "(StrOpt) Default publisher_id for outgoing notifications."
+#: ./doc/common/tables/cinder-san.xml:23(td)
+msgid "(StrOpt) Cluster name to use for creating volumes"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml:34(td)
-msgid "default_store = file"
+#: ./doc/common/tables/cinder-san.xml:26(td)
+msgid "san_ip ="
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml:35(td)
-msgid "(StrOpt) Default scheme to use to store image data. The scheme must be registered by one of the stores defined by the 'known_stores' config option."
+#: ./doc/common/tables/cinder-san.xml:27(td)
+msgid "(StrOpt) IP address of SAN controller"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml:39(td)
-msgid "(BoolOpt) Deploy the v1 OpenStack Images API."
+#: ./doc/common/tables/cinder-san.xml:30(td)
+msgid "san_is_local = False"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml:42(td)
-msgid "enable_v1_registry = True"
+#: ./doc/common/tables/cinder-san.xml:31(td)
+msgid "(BoolOpt) Execute commands locally instead of over SSH; use if the volume service is running on the SAN device"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml:43(td)
-msgid "(BoolOpt) Deploy the v1 OpenStack Registry API."
+#: ./doc/common/tables/cinder-san.xml:34(td)
+msgid "san_login = admin"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml:47(td)
-msgid "(BoolOpt) Deploy the v2 OpenStack Images API."
+#: ./doc/common/tables/cinder-san.xml:35(td)
+msgid "(StrOpt) Username for SAN controller"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml:50(td)
-msgid "enable_v2_registry = True"
+#: ./doc/common/tables/cinder-san.xml:38(td)
+msgid "san_password ="
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml:51(td)
-msgid "(BoolOpt) Deploy the v2 OpenStack Registry API."
+#: ./doc/common/tables/cinder-san.xml:39(td)
+msgid "(StrOpt) Password for SAN controller"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml:54(td)
-msgid "image_size_cap = 1099511627776"
+#: ./doc/common/tables/cinder-san.xml:42(td)
+msgid "san_private_key ="
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml:55(td)
-msgid "(IntOpt) Maximum size of image a user can upload in bytes. Defaults to 1099511627776 bytes (1 TB)."
+#: ./doc/common/tables/cinder-san.xml:43(td)
+msgid "(StrOpt) Filename of private key to use for SSH authentication"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml:58(td)
-msgid "known_stores = glance.store.filesystem.Store, glance.store.http.Store"
+#: ./doc/common/tables/cinder-san.xml:46(td)
+msgid "san_ssh_port = 22"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml:59(td)
-msgid "(ListOpt) List of which store classes and store class locations are currently known to glance at startup."
+#: ./doc/common/tables/cinder-san.xml:47(td)
+msgid "(IntOpt) SSH port to use with SAN"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml:62(td)
-msgid "location_strategy = location_order"
+#: ./doc/common/tables/cinder-san.xml:50(td)
+msgid "san_thin_provision = True"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml:63(td)
-msgid "(StrOpt) This value sets what strategy will be used to determine the image location order. Currently two strategies are packaged with Glance 'location_order' and 'store_type'."
+#: ./doc/common/tables/cinder-san.xml:51(td)
+msgid "(BoolOpt) Use thin provisioning for SAN volumes?"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml:66(td)
-msgid "owner_is_tenant = True"
+#: ./doc/common/tables/cinder-san.xml:54(td)
+msgid "ssh_conn_timeout = 30"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml:67(td)
-msgid "(BoolOpt) When true, this option sets the owner of an image to be the tenant. Otherwise, the owner of the image will be the authenticated user issuing the request."
+#: ./doc/common/tables/cinder-san.xml:55(td)
+msgid "(IntOpt) SSH connection timeout in seconds"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml:70(td)
-msgid "send_identity_headers = False"
+#: ./doc/common/tables/cinder-san.xml:58(td)
+msgid "ssh_max_pool_conn = 5"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml:71(td)
-msgid "(BoolOpt) Whether to pass through headers containing user and tenant information when making requests to the registry. This allows the registry to use the context middleware without the keystoneclients' auth_token middleware, removing calls to the keystone auth service. It is recommended that when using this option, secure communication between glance api and glance registry is ensured by means other than auth_token middleware."
+#: ./doc/common/tables/cinder-san.xml:59(td)
+msgid "(IntOpt) Maximum ssh connections in the pool"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml:74(td)
-msgid "show_multiple_locations = False"
+#: ./doc/common/tables/cinder-san.xml:62(td)
+msgid "ssh_min_pool_conn = 1"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml:75(td)
-msgid "(BoolOpt) Whether to include the backend image locations in image properties. Revealing storage location can be a security risk, so use this setting with caution! The overrides show_image_direct_url."
+#: ./doc/common/tables/cinder-san.xml:63(td)
+msgid "(IntOpt) Minimum ssh connections in the pool"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml:78(td)
-msgid "use_user_token = True"
+#: ./doc/common/tables/nova-logging.xml:26(td)
+msgid "default_log_levels = amqp=WARN, amqplib=WARN, boto=WARN, qpid=WARN, sqlalchemy=WARN, suds=INFO, oslo.messaging=INFO, iso8601=WARN"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml:79(td)
-msgid "(BoolOpt) Whether to pass through the user token when making requests to the registry."
+#: ./doc/common/tables/nova-logging.xml:35(td)
+msgid "(BoolOpt) Make exception message format errors fatal"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml:82(th)
-msgid "[store_type_location_strategy]"
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml:85(td)
-msgid "store_type_preference ="
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml:86(td)
-msgid "(ListOpt) The store names to use to get store preference order. The name must be registered by one of the stores defined by the 'known_stores' config option. This option will be applied when you using 'store_type' option as image location strategy defined by the 'location_strategy' config option."
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml:22(td)
-msgid "scheduler_default_filters = AvailabilityZoneFilter, CapacityFilter, CapabilitiesFilter"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml:26(td)
-msgid "scheduler_default_weighers = CapacityWeigher"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml:27(td)
-msgid "(ListOpt) Which weigher class names to use for weighing hosts."
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml:30(td)
-msgid "scheduler_driver = cinder.scheduler.filter_scheduler.FilterScheduler"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml:31(td)
-msgid "(StrOpt) Default scheduler driver to use"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml:34(td)
-msgid "scheduler_host_manager = cinder.scheduler.host_manager.HostManager"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml:42(td)
-msgid "scheduler_manager = cinder.scheduler.manager.SchedulerManager"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml:43(td)
-msgid "(StrOpt) full class name for the Manager for scheduler"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml:47(td)
-msgid "(IntOpt) Maximum number of attempts to schedule an volume"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml:50(td)
-msgid "scheduler_topic = cinder-scheduler"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml:51(td)
-msgid "(StrOpt) the topic scheduler nodes listen on"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:22(td)
-msgid "admin_bind_host = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:23(td)
-msgid "(StrOpt) The IP Address of the network interface to for the admin service to listen on."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:26(td)
-msgid "admin_endpoint = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:27(td)
-msgid "(StrOpt) The base admin endpoint URL for keystone that are advertised to clients (NOTE: this does NOT affect how keystone listens for connections). Defaults to the base host URL of the request. Eg a request to http://server:35357/v2.0/users will default to http://server:35357. You should only need to set this value if the base URL contains a path (eg /prefix/v2.0) or the endpoint should be found on a different server."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:30(td)
-msgid "admin_port = 35357"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:31(td)
-msgid "(IntOpt) The port number which the admin service listens on."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:34(td)
-msgid "admin_token = ADMIN"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:35(td)
-msgid "(StrOpt) A \"shared secret\" that can be used to bootstrap Keystone. This \"token\" does not represent a user, and carries no explicit authorization. To disable in production (highly recommended), remove AdminTokenAuthMiddleware from your paste application pipelines (for example, in keystone-paste.ini)."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:38(td)
-msgid "compute_port = 8774"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:39(td)
-msgid "(IntOpt) The port which the OpenStack Compute service listens on."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:42(td)
-msgid "domain_id_immutable = True"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:43(td)
-msgid "(BoolOpt) Set this to false if you want to enable the ability for user, group and project entities to be moved between domains by updating their domain_id. Allowing such movement is not recommended if the scope of a domain admin is being restricted by use of an appropriate policy file (see policy.v3cloudsample as an example)."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:47(td)
-msgid "(IntOpt) The maximum number of entities that will be returned in a collection can be set with list_limit, with no limit set by default. This global limit may be then overridden for a specific driver, by specifying a list_limit in the appropriate section (e.g. [assignment])."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:50(td)
-msgid "max_param_size = 64"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:51(td)
-msgid "(IntOpt) limit the sizes of user &amp; tenant ID/names."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:55(td)
-msgid "(IntOpt) enforced by optional sizelimit middleware (keystone.middleware:RequestBodySizeLimiter)."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:58(td)
-msgid "max_token_size = 8192"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:59(td)
-msgid "(IntOpt) similar to max_param_size, but provides an exception for token values."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:62(td)
-msgid "member_role_id = 9fe2ff9ee4384b1894a90878d3e92bab"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:63(td)
-msgid "(StrOpt) During a SQL upgrade member_role_id will be used to create a new role that will replace records in the user_tenant_membership table with explicit role grants. After migration, the member_role_id will be used in the API add_user_to_project."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:66(td)
-msgid "member_role_name = _member_"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:67(td)
-msgid "(StrOpt) During a SQL upgrade member_role_id will be used to create a new role that will replace records in the user_tenant_membership table with explicit role grants. After migration, member_role_name will be ignored."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:70(td)
-msgid "public_bind_host = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:71(td)
-msgid "(StrOpt) The IP Address of the network interface to for the public service to listen on."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:74(td)
-msgid "public_endpoint = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:75(td)
-msgid "(StrOpt) The base public endpoint URL for keystone that are advertised to clients (NOTE: this does NOT affect how keystone listens for connections). Defaults to the base host URL of the request. Eg a request to http://server:5000/v2.0/users will default to http://server:5000. You should only need to set this value if the base URL contains a path (eg /prefix/v2.0) or the endpoint should be found on a different server."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:78(td)
-msgid "public_port = 5000"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:79(td)
-msgid "(IntOpt) The port number which the public service listens on."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:82(td)
-msgid "tcp_keepalive = False"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:83(td)
-msgid "(BoolOpt) Set this to True if you want to enable TCP_KEEPALIVE on server sockets i.e. sockets used by the keystone wsgi server for client connections."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:87(td)
-msgid "(IntOpt) Sets the value of TCP_KEEPIDLE in seconds for each server socket. Only applies if tcp_keepalive is True. Not supported on OS X."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:90(th)
-msgid "[endpoint_filter]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:93(td)
-msgid "driver = keystone.contrib.endpoint_filter.backends.sql.EndpointFilter"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:94(td)
-msgid "(StrOpt) Keystone Endpoint Filter backend driver"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:97(td)
-msgid "return_all_endpoints_if_no_filter = True"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:98(td)
-msgid "(BoolOpt) Toggle to return all active endpoints if no filter exists."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:104(td)
-msgid "config_file = keystone-paste.ini"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml:105(td)
-msgid "(StrOpt) Name of the paste configuration file that defines the available pipelines."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ncs.xml:8(caption)
-msgid "Description of configuration options for ml2_ncs"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ncs.xml:19(th)
-msgid "[ml2_ncs]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ncs.xml:31(td)
-msgid "(StrOpt) HTTP URL of Tail-f NCS REST interface."
+#: ./doc/common/tables/nova-logging.xml:66(td)
+msgid "logging_context_format_string = %(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [%(request_id)s %(user)s %(tenant)s] %(instance)s%(message)s"
 msgstr ""
 
 #: ./doc/common/tables/neutron-nec.xml:8(caption)
@@ -35803,24 +34531,184 @@ msgstr ""
 msgid "(StrOpt) Name of the FWaaS Driver"
 msgstr ""
 
-#: ./doc/common/tables/neutron-cadf.xml:8(caption)
-msgid "Description of configuration options for cadf"
+#: ./doc/common/tables/keystone-security.xml:8(caption)
+msgid "Description of configuration options for security"
 msgstr ""
 
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml:7(literal)
-msgid "[object-expirer]"
+#: ./doc/common/tables/keystone-security.xml:22(td)
+msgid "crypt_strength = 40000"
 msgstr ""
 
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml:33(td)
-msgid "processes = 0"
+#: ./doc/common/tables/keystone-security.xml:23(td)
+msgid "(IntOpt) The value passed as the keyword \"rounds\" to passlib encrypt method."
 msgstr ""
 
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml:36(td)
-msgid "process = 0"
+#: ./doc/common/tables/heat-clients_neutron.xml:8(caption)
+msgid "Description of configuration options for clients_neutron"
 msgstr ""
 
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml:36(td)
-msgid "(it will actually accept(2) N + 1). Setting this to one (1) will only handle one request at a time, without accepting another request concurrently."
+#: ./doc/common/tables/heat-clients_neutron.xml:19(th)
+msgid "[clients_neutron]"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:22(td)
+msgid "api_rate_limit = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:23(td)
+msgid "(BoolOpt) Whether to use per-user rate limiting for the api. This option is only used by v2 api. Rate limiting is removed from v3 api."
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:30(td)
+msgid "enabled_apis = ec2, osapi_compute, metadata"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:31(td)
+msgid "(ListOpt) A list of APIs to enable by default"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:34(td)
+msgid "enabled_ssl_apis ="
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:35(td)
+msgid "(ListOpt) A list of APIs with enabled SSL"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:38(td)
+msgid "instance_name_template = instance-%08x"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:39(td)
+msgid "(StrOpt) Template string to be used to generate instance names"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:46(td)
+msgid "multi_instance_display_name_template = %(name)s-%(uuid)s"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:47(td)
+msgid "(StrOpt) When creating multiple instances with a single request using the os-multiple-create API extension, this template will be used to build the display name for each instance. The benefit is that the instances end up with different hostnames. To restore legacy behavior of every instance having the same name, set this option to \"%(name)s\". Valid keys for the template are: name, uuid, count."
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:50(td)
+msgid "non_inheritable_image_properties = cache_in_nova, bittorrent"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:51(td)
+msgid "(ListOpt) These are image properties which a snapshot should not inherit from an instance"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:54(td)
+msgid "null_kernel = nokernel"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:55(td)
+msgid "(StrOpt) Kernel image that indicates not to use a kernel, but to use a raw disk image instead"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:58(td)
+msgid "osapi_compute_ext_list ="
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:59(td)
+msgid "(ListOpt) Specify list of extensions to load when using osapi_compute_extension option with nova.api.openstack.compute.contrib.select_extensions"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:62(td)
+msgid "osapi_compute_extension = ['nova.api.openstack.compute.contrib.standard_extensions']"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:63(td)
+msgid "(MultiStrOpt) osapi compute extension to load"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:66(td)
+msgid "osapi_compute_link_prefix = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:67(td)
+msgid "(StrOpt) Base URL that will be presented to users in links to the OpenStack Compute API"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:70(td)
+msgid "osapi_compute_listen = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:71(td)
+msgid "(StrOpt) The IP address on which the OpenStack API will listen."
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:74(td)
+msgid "osapi_compute_listen_port = 8774"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:75(td)
+msgid "(IntOpt) The port on which the OpenStack API will listen."
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:78(td)
+msgid "osapi_compute_workers = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:79(td)
+msgid "(IntOpt) Number of workers for OpenStack API service. The default will be the number of CPUs available."
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:82(td)
+msgid "osapi_hide_server_address_states = building"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:83(td)
+msgid "(ListOpt) List of instance states that should hide network info"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:86(td)
+msgid "servicegroup_driver = db"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml:87(td)
+msgid "(StrOpt) The driver for servicegroup service (valid options are: db, zk, mc)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_mlnx.xml:8(caption)
+msgid "Description of configuration options for ml2_mlnx"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_mlnx.xml:22(td)
+msgid "apply_profile_patch = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_mlnx.xml:23(td)
+msgid "(BoolOpt) Enable server compatibility with old nova"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_mlnx.xml:26(td)
+msgid "vnic_type = mlnx_direct"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_mlnx.xml:27(td)
+msgid "(StrOpt) Type of VM network interface: mlnx_direct or hostdev"
+msgstr ""
+
+#: ./doc/common/tables/keystone-trust.xml:8(caption)
+msgid "Description of configuration options for trust"
+msgstr ""
+
+#: ./doc/common/tables/keystone-trust.xml:19(th)
+msgid "[trust]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-trust.xml:22(td)
+msgid "driver = keystone.trust.backends.sql.Trust"
+msgstr ""
+
+#: ./doc/common/tables/keystone-trust.xml:23(td)
+msgid "(StrOpt) Keystone Trust backend driver."
+msgstr ""
+
+#: ./doc/common/tables/keystone-trust.xml:27(td)
+msgid "(BoolOpt) delegation and impersonation features can be optionally disabled."
 msgstr ""
 
 #: ./doc/common/tables/glance-cinder.xml:8(caption)
@@ -35847,880 +34735,292 @@ msgstr ""
 msgid "(IntOpt) Number of cinderclient retries on failed http calls."
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane.xml:8(caption)
-msgid "Description of configuration options for embrane"
+#: ./doc/common/tables/swift-object-server-object-updater.xml:7(literal)
+msgid "[object-updater]"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane.xml:22(td)
-msgid "admin_username = admin"
+#: ./doc/common/tables/swift-object-server-object-updater.xml:18(td)
+msgid "log_name = object-updater"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane.xml:26(td)
-msgid "async_requests = True"
+#: ./doc/common/tables/glance-common.xml:22(td)
+msgid "allow_additional_image_properties = True"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane.xml:31(td)
-msgid "(StrOpt) Dummy user traffic Security Zone id"
+#: ./doc/common/tables/glance-common.xml:23(td)
+msgid "(BoolOpt) Whether to allow users to specify image properties beyond what the image schema provides"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane.xml:39(td)
-msgid "(StrOpt) In band Security Zone id"
+#: ./doc/common/tables/glance-common.xml:26(td)
+msgid "api_limit_max = 1000"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane.xml:43(td)
-msgid "(StrOpt) Management Security Zone id"
+#: ./doc/common/tables/glance-common.xml:27(td)
+msgid "(IntOpt) Maximum permissible number of items that could be returned by a request"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane.xml:47(td)
-msgid "(StrOpt) Out of band Security Zone id"
+#: ./doc/common/tables/glance-common.xml:31(td)
+msgid "(IntOpt) The backlog value that will be used when creating the TCP listener socket."
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane.xml:50(td)
-msgid "resource_pool_id = default"
+#: ./doc/common/tables/glance-common.xml:38(td)
+msgid "bind_port = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane.xml:54(td)
-msgid "router_image = None"
+#: ./doc/common/tables/glance-common.xml:42(td)
+msgid "data_api = glance.db.sqlalchemy.api"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane.xml:55(td)
-msgid "(StrOpt) Router image id (Embrane FW/VPN)"
+#: ./doc/common/tables/glance-common.xml:43(td)
+msgid "(StrOpt) Python module path of data access API"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml:18(td)
-msgid "pipeline = catch_errors gatekeeper healthcheck proxy-logging cache container_sync bulk tempurl slo dlo ratelimit tempauth container-quotas account-quotas proxy-logging proxy-server"
+#: ./doc/common/tables/glance-common.xml:50(td)
+msgid "image_location_quota = 10"
 msgstr ""
 
-#: ./doc/common/tables/nova-upgrade_levels.xml:8(caption)
-msgid "Description of configuration options for upgrade_levels"
+#: ./doc/common/tables/glance-common.xml:51(td)
+msgid "(IntOpt) Maximum number of locations allowed on an image. Negative values evaluate to unlimited."
 msgstr ""
 
-#: ./doc/common/tables/nova-upgrade_levels.xml:22(td)
-msgid "scheduler = nova.cells.scheduler.CellsScheduler"
+#: ./doc/common/tables/glance-common.xml:54(td)
+msgid "image_member_quota = 128"
 msgstr ""
 
-#: ./doc/common/tables/nova-upgrade_levels.xml:23(td)
-msgid "(StrOpt) Cells scheduler to use"
+#: ./doc/common/tables/glance-common.xml:55(td)
+msgid "(IntOpt) Maximum number of image members per image. Negative values evaluate to unlimited."
 msgstr ""
 
-#: ./doc/common/tables/nova-upgrade_levels.xml:29(td)
-msgid "cells = None"
+#: ./doc/common/tables/glance-common.xml:58(td)
+msgid "image_property_quota = 128"
 msgstr ""
 
-#: ./doc/common/tables/nova-upgrade_levels.xml:30(td)
-msgid "(StrOpt) Set a version cap for messages sent to local cells services"
+#: ./doc/common/tables/glance-common.xml:59(td)
+msgid "(IntOpt) Maximum number of properties allowed on an image. Negative values evaluate to unlimited."
 msgstr ""
 
-#: ./doc/common/tables/nova-upgrade_levels.xml:33(td)
-msgid "cert = None"
+#: ./doc/common/tables/glance-common.xml:62(td)
+msgid "image_tag_quota = 128"
 msgstr ""
 
-#: ./doc/common/tables/nova-upgrade_levels.xml:34(td)
-msgid "(StrOpt) Set a version cap for messages sent to cert services"
+#: ./doc/common/tables/glance-common.xml:63(td)
+msgid "(IntOpt) Maximum number of tags allowed on an image. Negative values evaluate to unlimited."
 msgstr ""
 
-#: ./doc/common/tables/nova-upgrade_levels.xml:37(td)
-msgid "compute = None"
+#: ./doc/common/tables/glance-common.xml:66(td)
+msgid "limit_param_default = 25"
 msgstr ""
 
-#: ./doc/common/tables/nova-upgrade_levels.xml:38(td)
-msgid "(StrOpt) Set a version cap for messages sent to compute services. If you plan to do a live upgrade from havana to icehouse, you should set this option to \"icehouse-compat\" before beginning the live upgrade procedure."
+#: ./doc/common/tables/glance-common.xml:67(td)
+msgid "(IntOpt) Default value for the number of items returned by a request if not specified explicitly in the request"
 msgstr ""
 
-#: ./doc/common/tables/nova-upgrade_levels.xml:41(td)
-msgid "conductor = None"
+#: ./doc/common/tables/glance-common.xml:74(td)
+msgid "metadata_encryption_key = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-upgrade_levels.xml:42(td)
-msgid "(StrOpt) Set a version cap for messages sent to conductor services"
+#: ./doc/common/tables/glance-common.xml:75(td)
+msgid "(StrOpt) Key used for encrypting sensitive metadata while talking to the registry or database."
 msgstr ""
 
-#: ./doc/common/tables/nova-upgrade_levels.xml:45(td)
-msgid "console = None"
+#: ./doc/common/tables/glance-common.xml:78(td)
+msgid "notifier_strategy = default"
 msgstr ""
 
-#: ./doc/common/tables/nova-upgrade_levels.xml:46(td)
-msgid "(StrOpt) Set a version cap for messages sent to console services"
+#: ./doc/common/tables/glance-common.xml:79(td)
+msgid "(StrOpt) Notifications can be sent when images are create, updated or deleted. There are three methods of sending notifications, logging (via the log_file directive), rabbit (via a rabbitmq queue), qpid (via a Qpid message queue), or noop (no notifications sent, the default). (DEPRECATED)"
 msgstr ""
 
-#: ./doc/common/tables/nova-upgrade_levels.xml:49(td)
-msgid "consoleauth = None"
+#: ./doc/common/tables/glance-common.xml:83(td)
+msgid "(StrOpt) Region name of this node."
 msgstr ""
 
-#: ./doc/common/tables/nova-upgrade_levels.xml:50(td)
-msgid "(StrOpt) Set a version cap for messages sent to consoleauth services"
+#: ./doc/common/tables/glance-common.xml:86(td)
+msgid "property_protection_file = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-upgrade_levels.xml:53(td)
-msgid "intercell = None"
+#: ./doc/common/tables/glance-common.xml:87(td)
+msgid "(StrOpt) The location of the property protection file."
 msgstr ""
 
-#: ./doc/common/tables/nova-upgrade_levels.xml:54(td)
-msgid "(StrOpt) Set a version cap for messages sent between cells services"
+#: ./doc/common/tables/glance-common.xml:90(td)
+msgid "property_protection_rule_format = roles"
 msgstr ""
 
-#: ./doc/common/tables/nova-upgrade_levels.xml:57(td)
-msgid "network = None"
+#: ./doc/common/tables/glance-common.xml:91(td)
+msgid "(StrOpt) This config value indicates whether \"roles\" or \"policies\" are used in the property protection file."
 msgstr ""
 
-#: ./doc/common/tables/nova-upgrade_levels.xml:58(td)
-msgid "(StrOpt) Set a version cap for messages sent to network services"
+#: ./doc/common/tables/glance-common.xml:94(td)
+msgid "show_image_direct_url = False"
 msgstr ""
 
-#: ./doc/common/tables/nova-upgrade_levels.xml:61(td)
-msgid "scheduler = None"
+#: ./doc/common/tables/glance-common.xml:95(td)
+msgid "(BoolOpt) Whether to include the backend image storage location in image properties. Revealing storage location can be a security risk, so use this setting with caution!"
 msgstr ""
 
-#: ./doc/common/tables/nova-upgrade_levels.xml:62(td)
-msgid "(StrOpt) Set a version cap for messages sent to scheduler services"
+#: ./doc/common/tables/glance-common.xml:98(td)
+msgid "user_storage_quota = 0"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:7(literal)
-msgid "[filter:cname_lookup]"
+#: ./doc/common/tables/glance-common.xml:99(td)
+msgid "(IntOpt) Set a system wide quota for every user. This value is the total number of bytes that a user can use across all storage systems. A value of 0 means unlimited."
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:18(td)
-msgid "use = egg:swift#cname_lookup"
+#: ./doc/common/tables/glance-common.xml:102(td)
+msgid "workers = 1"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:21(td)
-msgid "set log_name = cname_lookup"
+#: ./doc/common/tables/glance-common.xml:103(td)
+msgid "(IntOpt) The number of child process workers that will be created to service API requests."
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:36(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:36(td)
-msgid "storage_domain = example.com"
+#: ./doc/common/tables/glance-common.xml:106(th)
+msgid "[image_format]"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:36(td) ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:36(td)
-msgid "Domain that matches your cloud. Multiple domains can be specified using a comma-separated list."
+#: ./doc/common/tables/glance-common.xml:109(td)
+msgid "container_formats = ami, ari, aki, bare, ovf, ova"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:40(td)
-msgid "lookup_depth = 1"
+#: ./doc/common/tables/glance-common.xml:110(td)
+msgid "(ListOpt) Supported values for the 'container_format' image attribute"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml:40(td)
-msgid "Because CNAMES can be recursive, specifies the number of levels through which to search."
+#: ./doc/common/tables/glance-common.xml:113(td)
+msgid "disk_formats = ami, ari, aki, vhd, vmdk, raw, qcow2, vdi, iso"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-inspector.xml:8(caption)
-msgid "Description of configuration options for inspector"
+#: ./doc/common/tables/glance-common.xml:114(td)
+msgid "(ListOpt) Supported values for the 'disk_format' image attribute"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-inspector.xml:22(td)
-msgid "hypervisor_inspector = libvirt"
+#: ./doc/common/tables/glance-common.xml:117(th)
+msgid "[task]"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-inspector.xml:23(td)
-msgid "(StrOpt) Inspector to use for inspecting the hypervisor layer."
+#: ./doc/common/tables/glance-common.xml:120(td)
+msgid "task_time_to_live = 48"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-inspector.xml:26(td)
-msgid "libvirt_type = kvm"
+#: ./doc/common/tables/glance-common.xml:121(td)
+msgid "(IntOpt) Time in hours for which a task lives after, either succeeding or failing"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-inspector.xml:27(td)
-msgid "(StrOpt) Libvirt domain type (valid options are: kvm, lxc, qemu, uml, xen)."
+#: ./doc/common/tables/neutron-ml2_vxlan.xml:8(caption)
+msgid "Description of configuration options for ml2_vxlan"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-inspector.xml:30(td)
-msgid "libvirt_uri ="
+#: ./doc/common/tables/neutron-ml2_vxlan.xml:19(th)
+msgid "[ml2_type_vxlan]"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-inspector.xml:31(td)
-msgid "(StrOpt) Override the default libvirt URI (which is dependent on libvirt_type)."
+#: ./doc/common/tables/neutron-ml2_vxlan.xml:22(td)
+msgid "vni_ranges ="
 msgstr ""
 
-#: ./doc/common/tables/heat-common.xml:22(td)
-msgid "deferred_auth_method = password"
+#: ./doc/common/tables/neutron-ml2_vxlan.xml:23(td)
+msgid "(ListOpt) Comma-separated list of &lt;vni_min&gt;:&lt;vni_max&gt; tuples enumerating ranges of VXLAN VNI IDs that are available for tenant network allocation"
 msgstr ""
 
-#: ./doc/common/tables/heat-common.xml:23(td)
-msgid "(StrOpt) Select deferred auth method, stored password or trusts."
+#: ./doc/common/tables/neutron-ml2_vxlan.xml:26(td)
+msgid "vxlan_group = None"
 msgstr ""
 
-#: ./doc/common/tables/heat-common.xml:26(td)
-msgid "environment_dir = /etc/heat/environment.d"
+#: ./doc/common/tables/neutron-ml2_vxlan.xml:27(td)
+msgid "(StrOpt) Multicast group for VXLAN. If unset, disables VXLAN multicast mode."
 msgstr ""
 
-#: ./doc/common/tables/heat-common.xml:27(td)
-msgid "(StrOpt) The directory to search for environment files."
+#: ./doc/common/tables/swift-dispersion-dispersion.xml:7(literal)
+msgid "[dispersion]"
 msgstr ""
 
-#: ./doc/common/tables/heat-common.xml:30(td)
-msgid "event_purge_batch_size = 10"
+#: ./doc/common/tables/swift-dispersion-dispersion.xml:7(literal)
+msgid "dispersion.conf-sample"
 msgstr ""
 
-#: ./doc/common/tables/heat-common.xml:31(td)
-msgid "(IntOpt) Controls how many events will be pruned whenever a stack's events exceed max_events_per_stack. Set this lower to keep more events at the expense of more frequent purges."
+#: ./doc/common/tables/swift-dispersion-dispersion.xml:18(td)
+msgid "auth_url = http://localhost:8080/auth/v1.0"
 msgstr ""
 
-#: ./doc/common/tables/heat-common.xml:34(td)
-msgid "instance_driver = heat.engine.nova"
+#: ./doc/common/tables/swift-dispersion-dispersion.xml:18(td) ./doc/common/tables/swift-dispersion-dispersion.xml:27(td)
+msgid "Endpoint for auth server, such as keystone"
 msgstr ""
 
-#: ./doc/common/tables/heat-common.xml:35(td)
-msgid "(StrOpt) Driver to use for controlling instances."
+#: ./doc/common/tables/swift-dispersion-dispersion.xml:21(td)
+msgid "auth_user = test:tester"
 msgstr ""
 
-#: ./doc/common/tables/heat-common.xml:38(td)
-msgid "instance_user = ec2-user"
+#: ./doc/common/tables/swift-dispersion-dispersion.xml:21(td) ./doc/common/tables/swift-dispersion-dispersion.xml:30(td)
+msgid "Default user for dispersion in this context"
 msgstr ""
 
-#: ./doc/common/tables/heat-common.xml:39(td)
-msgid "(StrOpt) The default user for new instances. This option is deprecated and will be removed in the Juno release. If it's empty, Heat will use the default user set up with your cloud image (for OS::Nova::Server) or 'ec2-user' (for AWS::EC2::Instance)."
+#: ./doc/common/tables/swift-dispersion-dispersion.xml:24(td)
+msgid "auth_key = testing"
 msgstr ""
 
-#: ./doc/common/tables/heat-common.xml:42(td)
-msgid "keystone_backend = heat.common.heat_keystoneclient.KeystoneClientV3"
+#: ./doc/common/tables/swift-dispersion-dispersion.xml:27(td)
+msgid "auth_url = http://localhost:5000/v2.0/"
 msgstr ""
 
-#: ./doc/common/tables/heat-common.xml:43(td)
-msgid "(StrOpt) Fully qualified class name to use as a keystone backend."
+#: ./doc/common/tables/swift-dispersion-dispersion.xml:30(td)
+msgid "auth_user = tenant:user"
 msgstr ""
 
-#: ./doc/common/tables/heat-common.xml:47(td)
-msgid "(IntOpt) Seconds between running periodic tasks."
+#: ./doc/common/tables/swift-dispersion-dispersion.xml:33(td)
+msgid "auth_key = password"
 msgstr ""
 
-#: ./doc/common/tables/heat-common.xml:50(td)
-msgid "plugin_dirs = /usr/lib64/heat, /usr/lib/heat"
+#: ./doc/common/tables/swift-dispersion-dispersion.xml:36(td)
+msgid "auth_version = 2.0"
 msgstr ""
 
-#: ./doc/common/tables/heat-common.xml:51(td)
-msgid "(ListOpt) List of directories to search for plug-ins."
+#: ./doc/common/tables/swift-dispersion-dispersion.xml:36(td)
+msgid "Indicates which version of auth"
 msgstr ""
 
-#: ./doc/common/tables/heat-common.xml:54(th)
-msgid "[revision]"
+#: ./doc/common/tables/swift-dispersion-dispersion.xml:39(td)
+msgid "Indicates whether endpoint for auth is public or internal"
 msgstr ""
 
-#: ./doc/common/tables/heat-common.xml:57(td)
-msgid "heat_revision = unknown"
+#: ./doc/common/tables/swift-dispersion-dispersion.xml:42(td)
+msgid "keystone_api_insecure = no"
 msgstr ""
 
-#: ./doc/common/tables/heat-common.xml:58(td)
-msgid "(StrOpt) Heat build revision. If you would prefer to manage your build revision separately, you can move this section to a different file and add it as another config option."
+#: ./doc/common/tables/swift-dispersion-dispersion.xml:48(td)
+msgid "dispersion_coverage = 1.0"
 msgstr ""
 
-#: ./doc/common/tables/keystone-federation.xml:8(caption)
-msgid "Description of configuration options for federation"
+#: ./doc/common/tables/swift-dispersion-dispersion.xml:51(td)
+msgid "retries = 5"
 msgstr ""
 
-#: ./doc/common/tables/keystone-federation.xml:19(th)
-msgid "[federation]"
+#: ./doc/common/tables/swift-dispersion-dispersion.xml:54(td) ./doc/common/tables/swift-account-server-account-reaper.xml:30(td)
+msgid "concurrency = 25"
 msgstr ""
 
-#: ./doc/common/tables/keystone-federation.xml:22(td)
-msgid "assertion_prefix ="
+#: ./doc/common/tables/swift-dispersion-dispersion.xml:57(td)
+msgid "container_populate = yes"
 msgstr ""
 
-#: ./doc/common/tables/keystone-federation.xml:23(td)
-msgid "(StrOpt) Value to be used when filtering assertion parameters from the environment."
+#: ./doc/common/tables/swift-dispersion-dispersion.xml:60(td)
+msgid "object_populate = yes"
 msgstr ""
 
-#: ./doc/common/tables/keystone-federation.xml:26(td)
-msgid "driver = keystone.contrib.federation.backends.sql.Federation"
+#: ./doc/common/tables/swift-dispersion-dispersion.xml:63(td)
+msgid "container_report = yes"
 msgstr ""
 
-#: ./doc/common/tables/keystone-federation.xml:27(td)
-msgid "(StrOpt) Keystone Federation backend driver."
+#: ./doc/common/tables/swift-dispersion-dispersion.xml:66(td)
+msgid "object_report = yes"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zadara.xml:8(caption)
-msgid "Description of configuration options for zadara"
+#: ./doc/common/tables/swift-dispersion-dispersion.xml:69(td)
+msgid "dump_json = no"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zadara.xml:22(td)
-msgid "zadara_password = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml:23(td)
-msgid "(StrOpt) Password for the VPSA"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml:26(td)
-msgid "zadara_user = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml:27(td)
-msgid "(StrOpt) User name for the VPSA"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml:30(td)
-msgid "zadara_vol_encrypt = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml:31(td)
-msgid "(BoolOpt) Default encryption policy for volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml:34(td)
-msgid "zadara_vol_name_template = OS_%s"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml:35(td)
-msgid "(StrOpt) Default template for VPSA volume names"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml:38(td)
-msgid "zadara_vol_thin = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml:39(td)
-msgid "(BoolOpt) Default thin provisioning policy for volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml:42(td)
-msgid "zadara_vpsa_allow_nonexistent_delete = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml:43(td)
-msgid "(BoolOpt) Don't halt on deletion of non-existing volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml:46(td)
-msgid "zadara_vpsa_auto_detach_on_delete = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml:47(td)
-msgid "(BoolOpt) Automatically detach from servers on volume delete"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml:50(td)
-msgid "zadara_vpsa_ip = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml:51(td)
-msgid "(StrOpt) Management IP of Zadara VPSA"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml:54(td)
-msgid "zadara_vpsa_poolname = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml:55(td)
-msgid "(StrOpt) Name of VPSA storage pool for volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml:58(td)
-msgid "zadara_vpsa_port = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml:59(td)
-msgid "(StrOpt) Zadara VPSA port number"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml:62(td)
-msgid "zadara_vpsa_use_ssl = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml:63(td)
-msgid "(BoolOpt) Use SSL connection"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml:8(caption)
-msgid "Description of configuration options for nuage"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml:22(td)
-msgid "auth_resource ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml:23(td)
-msgid "(StrOpt) Nuage provided uri for initial authorization to access VSD"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml:26(td)
-msgid "base_uri = /"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml:27(td)
-msgid "(StrOpt) Nuage provided base uri to reach out to VSD"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml:30(td)
-msgid "default_floatingip_quota = 254"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml:31(td)
-msgid "(IntOpt) Per Net Partition quota of floating ips"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml:34(td)
-msgid "default_net_partition_name = OpenStackDefaultNetPartition"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml:35(td)
-msgid "(StrOpt) Default Network partition in which VSD will orchestrate network resources using openstack"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml:38(td)
-msgid "organization = system"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml:39(td)
-msgid "(StrOpt) Organization name in which VSD will orchestrate network resources using openstack"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml:42(td)
-msgid "server = localhost:8800"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml:43(td)
-msgid "(StrOpt) IP Address and Port of Nuage's VSD server"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml:46(td)
-msgid "serverauth = username:password"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml:47(td)
-msgid "(StrOpt) Username and password for authentication"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml:50(td)
-msgid "serverssl = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml:51(td)
-msgid "(BoolOpt) Boolean for SSL connection with VSD server"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-account-reaper.xml:7(literal)
-msgid "[account-reaper]"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-account-reaper.xml:18(td)
-msgid "log_name = account-reaper"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-account-reaper.xml:33(td)
-msgid "interval = 3600"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-account-reaper.xml:42(td)
-msgid "delay_reaping = 0"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-account-reaper.xml:42(td)
-msgid "Normally, the reaper begins deleting account information for deleted accounts immediately; you can set this to delay its work however. The value is in seconds, 2592000 = 30 days, for example. bind to giving up worker can process simultaneously (it will actually accept(2) N + 1). Setting this to one (1) will only handle one request at a time, without accepting another request concurrently. By increasing the number of workers to a much higher value, one can reduce the impact of slow file system operations in one request from negatively impacting other requests."
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-account-reaper.xml:45(td)
-msgid "reap_warn_after = 2592000"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml:22(td)
-msgid "bandwidth_poll_interval = 600"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml:23(td)
-msgid "(IntOpt) Interval to pull network bandwidth usage info. Not supported on all hypervisors. Set to 0 to disable."
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml:26(td)
-msgid "enable_network_quota = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml:27(td)
-msgid "(BoolOpt) Enables or disables quota checking for tenant networks"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml:30(td)
-msgid "quota_cores = 20"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml:31(td)
-msgid "(IntOpt) Number of instance cores allowed per project"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml:34(td)
-msgid "quota_driver = nova.quota.DbQuotaDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml:38(td)
-msgid "quota_fixed_ips = -1"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml:39(td)
-msgid "(IntOpt) Number of fixed IPs allowed per project (this should be at least the number of instances allowed)"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml:42(td)
-msgid "quota_floating_ips = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml:43(td)
-msgid "(IntOpt) Number of floating IPs allowed per project"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml:46(td)
-msgid "quota_injected_file_content_bytes = 10240"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml:47(td)
-msgid "(IntOpt) Number of bytes allowed per injected file"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml:50(td)
-msgid "quota_injected_file_path_bytes = 255"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml:51(td)
-msgid "(IntOpt) Number of bytes allowed per injected file path"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml:54(td)
-msgid "quota_injected_files = 5"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml:55(td)
-msgid "(IntOpt) Number of injected files allowed"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml:58(td)
-msgid "quota_instances = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml:59(td)
-msgid "(IntOpt) Number of instances allowed per project"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml:62(td)
-msgid "quota_key_pairs = 100"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml:63(td)
-msgid "(IntOpt) Number of key pairs per user"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml:66(td)
-msgid "quota_metadata_items = 128"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml:67(td)
-msgid "(IntOpt) Number of metadata items allowed per instance"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml:70(td)
-msgid "quota_ram = 51200"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml:71(td)
-msgid "(IntOpt) Megabytes of instance RAM allowed per project"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml:74(td)
-msgid "quota_security_group_rules = 20"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml:75(td)
-msgid "(IntOpt) Number of security rules per security group"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml:78(td)
-msgid "quota_security_groups = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml:79(td)
-msgid "(IntOpt) Number of security groups per project"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml:8(caption)
-msgid "Description of configuration options for conductor"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml:22(td)
-msgid "migrate_max_retries = -1"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml:23(td)
-msgid "(IntOpt) Number of times to retry live-migration before failing. If == -1, try until out of hosts. If == 0, only try once, no retries."
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml:26(th)
-msgid "[conductor]"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml:29(td)
-msgid "manager = nova.conductor.manager.ConductorManager"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml:30(td)
-msgid "(StrOpt) Full class name for the Manager for conductor"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml:33(td)
-msgid "topic = conductor"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml:34(td)
-msgid "(StrOpt) The topic on which conductor nodes listen"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml:37(td)
-msgid "use_local = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml:38(td)
-msgid "(BoolOpt) Perform nova-conductor operations locally"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml:41(td)
-msgid "workers = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml:42(td)
-msgid "(IntOpt) Number of workers for OpenStack Conductor service. The default will be the number of CPUs available."
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:22(td)
-msgid "compute_available_monitors = ['nova.compute.monitors.all_monitors']"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:23(td)
-msgid "(MultiStrOpt) Monitor classes available to the compute which may be specified more than once."
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:26(td)
-msgid "compute_driver = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:27(td)
-msgid "(StrOpt) Driver to use for controlling virtualization. Options include: libvirt.LibvirtDriver, xenapi.XenAPIDriver, fake.FakeDriver, baremetal.BareMetalDriver, vmwareapi.VMwareESXDriver, vmwareapi.VMwareVCDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:30(td)
-msgid "compute_manager = nova.compute.manager.ComputeManager"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:31(td)
-msgid "(StrOpt) Full class name for the Manager for compute"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:34(td)
-msgid "compute_monitors ="
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:35(td)
-msgid "(ListOpt) A list of monitors that can be used for getting compute metrics."
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:38(td)
-msgid "compute_stats_class = nova.compute.stats.Stats"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:39(td)
-msgid "(StrOpt) Class that will manage stats for the local compute host"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:42(td)
-msgid "console_host = oslo"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:43(td)
-msgid "(StrOpt) Console proxy host to use to connect to instances on this host."
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:46(td)
-msgid "console_manager = nova.console.manager.ConsoleProxyManager"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:47(td)
-msgid "(StrOpt) Full class name for the Manager for console proxy"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:50(td)
-msgid "default_flavor = m1.small"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:51(td)
-msgid "(StrOpt) Default flavor to use for the EC2 API only. The Nova API does not support a default flavor."
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:62(td)
-msgid "enable_instance_password = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:63(td)
-msgid "(BoolOpt) Enables returning of the instance password by the relevant server API calls such as create, rebuild or rescue, If the hypervisor does not support password injection then the password returned will not be correct"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:66(td)
-msgid "heal_instance_info_cache_interval = 60"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:67(td)
-msgid "(IntOpt) Number of seconds between instance info_cache self healing updates"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:70(td)
-msgid "image_cache_manager_interval = 2400"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:71(td)
-msgid "(IntOpt) Number of seconds to wait between runs of the image cache manager"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:74(td)
-msgid "image_cache_subdirectory_name = _base"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:75(td)
-msgid "(StrOpt) Where cached images are stored under $instances_path. This is NOT the full path - just a folder name. For per-compute-host cached images, set to _base_$my_ip"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:78(td)
-msgid "image_handlers = download"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:79(td)
-msgid "(ListOpt) Specifies which image handler extension names to use for handling images. The first extension in the list which can handle the image with a suitable location will be used."
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:82(td)
-msgid "instance_build_timeout = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:83(td)
-msgid "(IntOpt) Amount of time in seconds an instance can be in BUILD before going into ERROR status.Set to 0 to disable."
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:86(td)
-msgid "instance_delete_interval = 300"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:87(td)
-msgid "(IntOpt) Interval in seconds for retrying failed instance file deletes"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:90(td)
-msgid "instance_usage_audit = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:91(td)
-msgid "(BoolOpt) Generate periodic compute.instance.exists notifications"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:94(td)
-msgid "instance_usage_audit_period = month"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:95(td)
-msgid "(StrOpt) Time period to generate instance usages for. Time period must be hour, day, month or year"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:98(td)
-msgid "instances_path = $state_path/instances"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:99(td)
-msgid "(StrOpt) Where instances are stored on disk"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:102(td)
-msgid "maximum_instance_delete_attempts = 5"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:103(td)
-msgid "(IntOpt) The number of times to attempt to reap an instance's files."
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:106(td)
-msgid "reboot_timeout = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:107(td)
-msgid "(IntOpt) Automatically hard reboot an instance if it has been stuck in a rebooting state longer than N seconds. Set to 0 to disable."
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:110(td)
-msgid "reclaim_instance_interval = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:111(td)
-msgid "(IntOpt) Interval in seconds for reclaiming deleted instances"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:114(td)
-msgid "resize_confirm_window = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:115(td)
-msgid "(IntOpt) Automatically confirm resizes after N seconds. Set to 0 to disable."
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:118(td)
-msgid "resume_guests_state_on_host_boot = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:119(td)
-msgid "(BoolOpt) Whether to start guests that were running before the host rebooted"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:122(td)
-msgid "running_deleted_instance_action = reap"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:123(td)
-msgid "(StrOpt) Action to take if a running deleted instance is detected.Valid options are 'noop', 'log', 'shutdown', or 'reap'. Set to 'noop' to take no action."
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:126(td)
-msgid "running_deleted_instance_poll_interval = 1800"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:127(td)
-msgid "(IntOpt) Number of seconds to wait between runs of the cleanup task."
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:130(td)
-msgid "running_deleted_instance_timeout = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:131(td)
-msgid "(IntOpt) Number of seconds after being deleted when a running instance should be considered eligible for cleanup."
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:134(td)
-msgid "shelved_offload_time = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:135(td)
-msgid "(IntOpt) Time in seconds before a shelved instance is eligible for removing from a host. -1 never offload, 0 offload when shelved"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:138(td)
-msgid "shelved_poll_interval = 3600"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:139(td)
-msgid "(IntOpt) Interval in seconds for polling shelved instances to offload"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:142(td)
-msgid "sync_power_state_interval = 600"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:143(td)
-msgid "(IntOpt) Interval to sync power states between the database and the hypervisor"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:146(td)
-msgid "vif_plugging_is_fatal = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:147(td)
-msgid "(BoolOpt) Fail instance boot if vif plugging fails"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:150(td)
-msgid "vif_plugging_timeout = 300"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml:151(td)
-msgid "(IntOpt) Number of seconds to wait for neutron vif plugging events to arrive before continuing or failing (see vif_plugging_is_fatal). If this is set to zero and vif_plugging_is_fatal is False, events should not be expected to arrive at all."
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml:21(td)
+msgid "bind_port = 6002"
 msgstr ""
 
 #: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml:7(literal)
@@ -36751,72 +35051,308 @@ msgstr ""
 msgid "Reseller prefix"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_xen.xml:8(caption)
-msgid "Description of configuration options for storage_xen"
+#: ./doc/common/tables/trove-nova.xml:8(caption)
+msgid "Description of configuration options for nova"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_xen.xml:22(td)
-msgid "xenapi_connection_password = None"
+#: ./doc/common/tables/trove-nova.xml:22(td)
+msgid "nova_proxy_admin_pass ="
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_xen.xml:23(td)
-msgid "(StrOpt) Password for XenAPI connection"
+#: ./doc/common/tables/trove-nova.xml:23(td)
+msgid "(StrOpt) Admin password used to connect to nova,"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_xen.xml:26(td)
-msgid "xenapi_connection_url = None"
+#: ./doc/common/tables/trove-nova.xml:26(td)
+msgid "nova_proxy_admin_tenant_name ="
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_xen.xml:27(td)
-msgid "(StrOpt) URL for XenAPI connection"
+#: ./doc/common/tables/trove-nova.xml:27(td)
+msgid "(StrOpt) Admin tenant used to connect to nova."
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_xen.xml:31(td)
-msgid "(StrOpt) Username for XenAPI connection"
+#: ./doc/common/tables/trove-nova.xml:30(td)
+msgid "nova_proxy_admin_user ="
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_xen.xml:34(td)
-msgid "xenapi_nfs_server = None"
+#: ./doc/common/tables/trove-nova.xml:31(td)
+msgid "(StrOpt) Admin username used to connect to nova."
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_xen.xml:35(td)
-msgid "(StrOpt) NFS server to be used by XenAPINFSDriver"
+#: ./doc/common/tables/neutron-meta.xml:8(caption)
+msgid "Description of configuration options for meta"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_xen.xml:38(td)
-msgid "xenapi_nfs_serverpath = None"
+#: ./doc/common/tables/neutron-meta.xml:19(th)
+msgid "[META]"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_xen.xml:39(td)
-msgid "(StrOpt) Path of exported NFS, used by XenAPINFSDriver"
+#: ./doc/common/tables/neutron-meta.xml:22(td)
+msgid "default_flavor ="
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_xen.xml:42(td)
-msgid "xenapi_sr_base_path = /var/run/sr-mount"
+#: ./doc/common/tables/neutron-meta.xml:23(td)
+msgid "(StrOpt) Default flavor to use"
 msgstr ""
 
-#: ./doc/common/tables/keystone-credential.xml:8(caption)
-msgid "Description of configuration options for credential"
+#: ./doc/common/tables/neutron-meta.xml:26(td)
+msgid "default_l3_flavor ="
 msgstr ""
 
-#: ./doc/common/tables/keystone-credential.xml:19(th)
-msgid "[credential]"
+#: ./doc/common/tables/neutron-meta.xml:27(td)
+msgid "(StrOpt) Default L3 flavor to use"
 msgstr ""
 
-#: ./doc/common/tables/keystone-credential.xml:22(td)
-msgid "driver = keystone.credential.backends.sql.Credential"
+#: ./doc/common/tables/neutron-meta.xml:30(td)
+msgid "extension_map ="
 msgstr ""
 
-#: ./doc/common/tables/trove-amqp.xml:30(td)
-msgid "conductor_queue = trove-conductor"
+#: ./doc/common/tables/neutron-meta.xml:31(td)
+msgid "(StrOpt) A list of extensions, per plugin, to load."
 msgstr ""
 
-#: ./doc/common/tables/trove-amqp.xml:62(td)
-msgid "notification_service_id = {'couchbase': 'fa62fe68-74d9-4779-a24e-36f19602c415', 'mongodb': 'c8c907af-7375-456f-b929-b637ff9209ee', 'cassandra': '459a230d-4e97-4344-9067-2a54a310b0ed', 'redis': 'b216ffc5-1947-456c-a4cf-70f94c05f7d0', 'mysql': '2f3ff068-2bfb-4f70-9a9d-a6bb65bc084b'}"
+#: ./doc/common/tables/neutron-meta.xml:34(td)
+msgid "l3_plugin_list ="
 msgstr ""
 
-#: ./doc/common/tables/trove-amqp.xml:63(td)
-msgid "(DictOpt) Unique ID to tag notification events."
+#: ./doc/common/tables/neutron-meta.xml:35(td)
+msgid "(StrOpt) List of L3 plugins to load"
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml:38(td)
+msgid "plugin_list ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml:39(td)
+msgid "(StrOpt) List of plugins to load"
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml:42(td)
+msgid "rpc_flavor ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml:43(td)
+msgid "(StrOpt) Flavor of which plugin handles RPC"
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml:46(td)
+msgid "supported_extension_aliases ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml:47(td)
+msgid "(StrOpt) Supported extension aliases"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rabbitmq.xml:35(td) ./doc/common/tables/ceilometer-rabbitmq.xml:55(td)
+msgid "(IntOpt) Maximum number of RabbitMQ connection retries. Default is 0 (infinite retry count)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rabbitmq.xml:39(td) ./doc/common/tables/ceilometer-rabbitmq.xml:59(td)
+msgid "(StrOpt) The RabbitMQ password"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rabbitmq.xml:47(td) ./doc/common/tables/ceilometer-rabbitmq.xml:67(td)
+msgid "(IntOpt) How long to backoff for between retries when connecting to RabbitMQ"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rabbitmq.xml:51(td) ./doc/common/tables/ceilometer-rabbitmq.xml:71(td)
+msgid "(IntOpt) How frequently to retry connecting with RabbitMQ"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rabbitmq.xml:55(td) ./doc/common/tables/ceilometer-rabbitmq.xml:75(td)
+msgid "(BoolOpt) Connect over SSL for RabbitMQ"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rabbitmq.xml:59(td) ./doc/common/tables/ceilometer-rabbitmq.xml:79(td)
+msgid "(StrOpt) The RabbitMQ userid"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rabbitmq.xml:63(td) ./doc/common/tables/ceilometer-rabbitmq.xml:83(td)
+msgid "(StrOpt) The RabbitMQ virtual host"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml:22(td)
+msgid "keystone_ec2_cafile = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml:23(td)
+msgid "(StrOpt) A PEM encoded certificate authority to use when verifying HTTPS connections. Defaults to the system CAs."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml:26(td)
+msgid "keystone_ec2_certfile = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml:27(td)
+msgid "(StrOpt) Client certificate key filename. Required if EC2 server requires client certificate."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml:30(td)
+msgid "keystone_ec2_insecure = False"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml:31(td)
+msgid "(BoolOpt) Disable SSL certificate verification."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml:34(td)
+msgid "keystone_ec2_keyfile = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml:35(td)
+msgid "(StrOpt) Required if EC2 server requires client certificate."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml:42(th)
+msgid "[ec2]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml:45(td)
+msgid "driver = keystone.contrib.ec2.backends.kvs.Ec2"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml:46(td)
+msgid "(StrOpt) Keystone EC2Credential backend driver."
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_keystone.xml:8(caption)
+msgid "Description of configuration options for clients_keystone"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_keystone.xml:19(th)
+msgid "[clients_keystone]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml:22(td)
+msgid "allow_bulk = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml:23(td)
+msgid "(BoolOpt) Allow the usage of the bulk API"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml:26(td)
+msgid "allow_pagination = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml:27(td)
+msgid "(BoolOpt) Allow the usage of the pagination"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml:30(td)
+msgid "allow_sorting = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml:31(td)
+msgid "(BoolOpt) Allow the usage of the sorting"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml:34(td)
+msgid "api_extensions_path ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml:35(td)
+msgid "(StrOpt) The path for API extensions"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml:39(td)
+msgid "(StrOpt) The API paste config file to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml:43(td)
+msgid "(IntOpt) Max header line to accommodate large tokens"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml:47(td)
+msgid "(IntOpt) the maximum body size per each request(bytes)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml:50(td)
+msgid "pagination_max_limit = -1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml:51(td)
+msgid "(StrOpt) The maximum number of items returned in a single response, value was 'infinite' or negative integer means no limit"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml:58(td)
+msgid "service_plugins ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml:59(td)
+msgid "(ListOpt) The service plugins Neutron will use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml:62(th)
+msgid "[service_providers]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml:65(td)
+msgid "service_provider = []"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml:66(td)
+msgid "(MultiStrOpt) Defines providers for advanced services using the format: &lt;service_type&gt;:&lt;name&gt;:&lt;driver&gt;[:default]"
+msgstr ""
+
+#: ./doc/common/tables/trove-logging.xml:22(td)
+msgid "format_options = -m 5"
+msgstr ""
+
+#: ./doc/common/tables/trove-logging.xml:70(td)
+msgid "network_label_regex = ^private$"
+msgstr ""
+
+#: ./doc/common/tables/glance-db.xml:74(td) ./doc/common/tables/keystone-database.xml:74(td)
+msgid "mysql_sql_mode = TRADITIONAL"
+msgstr ""
+
+#: ./doc/common/tables/glance-db.xml:75(td) ./doc/common/tables/keystone-database.xml:75(td)
+msgid "(StrOpt) The SQL mode to be used for MySQL sessions. This option, including the default, overrides any server-set SQL mode. To use whatever SQL mode is set by the server configuration, set this to no value. Example: mysql_sql_mode="
+msgstr ""
+
+#: ./doc/common/tables/glance-db.xml:86(td)
+msgid "sqlite_db = glance.sqlite"
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml:8(caption)
+msgid "Description of configuration options for kvs"
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml:19(th)
+msgid "[kvs]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml:22(td)
+msgid "backends ="
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml:23(td)
+msgid "(ListOpt) Extra dogpile.cache backend modules to register with the dogpile.cache library."
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml:26(td)
+msgid "config_prefix = keystone.kvs"
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml:27(td)
+msgid "(StrOpt) Prefix for building the configuration dictionary for the KVS region. This should not need to be changed unless there is another dogpile.cache region with the same configuration name."
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml:30(td)
+msgid "default_lock_timeout = 5"
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml:31(td)
+msgid "(IntOpt) Default lock timeout for distributed locking."
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml:34(td)
+msgid "enable_key_mangler = True"
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml:35(td)
+msgid "(BoolOpt) Toggle to disable using a key-mangling function to ensure fixed length keys. This is toggle-able for debugging purposes, it is highly recommended to always leave this set to True."
 msgstr ""
 
 #: ./doc/common/tables/nova-xvpnvncproxy.xml:8(caption)
@@ -36847,8 +35383,1476 @@ msgstr ""
 msgid "(IntOpt) Port that the XCP VNC proxy should bind to"
 msgstr ""
 
+#: ./doc/common/tables/glance-paste.xml:8(caption)
+msgid "Description of configuration options for paste"
+msgstr ""
+
+#: ./doc/common/tables/glance-paste.xml:22(td)
+msgid "config_file = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-paste.xml:23(td)
+msgid "(StrOpt) Name of the paste configuration file."
+msgstr ""
+
+#: ./doc/common/tables/glance-paste.xml:27(td)
+msgid "(StrOpt) Partial name of a pipeline in your paste configuration file with the service name removed. For example, if your paste section name is [pipeline:glance-api-keystone] use the value \"keystone\""
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml:7(literal)
+msgid "[filter:list-endpoints]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml:18(td)
+msgid "use = egg:swift#list_endpoints"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml:21(td)
+msgid "list_endpoints_path = /endpoints/"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-reaper.xml:7(literal)
+msgid "[account-reaper]"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-reaper.xml:18(td)
+msgid "log_name = account-reaper"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-reaper.xml:33(td)
+msgid "interval = 3600"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-reaper.xml:42(td)
+msgid "delay_reaping = 0"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-reaper.xml:42(td)
+msgid "Normally, the reaper begins deleting account information for deleted accounts immediately; you can set this to delay its work however. The value is in seconds, 2592000 = 30 days, for example. bind to giving up worker can process simultaneously (it will actually accept(2) N + 1). Setting this to one (1) will only handle one request at a time, without accepting another request concurrently. By increasing the number of workers to a much higher value, one can reduce the impact of slow file system operations in one request from negatively impacting other requests."
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-reaper.xml:45(td)
+msgid "reap_warn_after = 2592000"
+msgstr ""
+
+#: ./doc/common/tables/nova-hyperv.xml:8(caption)
+msgid "Description of configuration options for hyperv"
+msgstr ""
+
+#: ./doc/common/tables/nova-hyperv.xml:22(td)
+msgid "dynamic_memory_ratio = 1.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-hyperv.xml:23(td)
+msgid "(FloatOpt) Enables dynamic memory allocation (ballooning) when set to a value greater than 1. The value expresses the ratio between the total RAM assigned to an instance and its startup RAM amount. For example a ratio of 2.0 for an instance with 1024MB of RAM implies 512MB of RAM allocated at startup"
+msgstr ""
+
+#: ./doc/common/tables/nova-hyperv.xml:26(td)
+msgid "enable_instance_metrics_collection = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-hyperv.xml:27(td)
+msgid "(BoolOpt) Enables metrics collections for an instance by using Hyper-V's metric APIs. Collected data can by retrieved by other apps and services, e.g.: Ceilometer. Requires Hyper-V / Windows Server 2012 and above"
+msgstr ""
+
+#: ./doc/common/tables/nova-hyperv.xml:34(td)
+msgid "instances_path_share ="
+msgstr ""
+
+#: ./doc/common/tables/nova-hyperv.xml:35(td)
+msgid "(StrOpt) The name of a Windows share name mapped to the \"instances_path\" dir and used by the resize feature to copy files to the target host. If left blank, an administrative share will be used, looking for the same \"instances_path\" used locally"
+msgstr ""
+
+#: ./doc/common/tables/nova-hyperv.xml:38(td)
+msgid "limit_cpu_features = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-hyperv.xml:39(td)
+msgid "(BoolOpt) Required for live migration among hosts with different CPU features"
+msgstr ""
+
+#: ./doc/common/tables/nova-hyperv.xml:42(td)
+msgid "mounted_disk_query_retry_count = 10"
+msgstr ""
+
+#: ./doc/common/tables/nova-hyperv.xml:43(td)
+msgid "(IntOpt) The number of times to retry checking for a disk mounted via iSCSI."
+msgstr ""
+
+#: ./doc/common/tables/nova-hyperv.xml:46(td)
+msgid "mounted_disk_query_retry_interval = 5"
+msgstr ""
+
+#: ./doc/common/tables/nova-hyperv.xml:47(td)
+msgid "(IntOpt) Interval between checks for a mounted iSCSI disk, in seconds."
+msgstr ""
+
+#: ./doc/common/tables/nova-hyperv.xml:50(td)
+msgid "qemu_img_cmd = qemu-img.exe"
+msgstr ""
+
+#: ./doc/common/tables/nova-hyperv.xml:51(td)
+msgid "(StrOpt) Path of qemu-img command which is used to convert between different image types"
+msgstr ""
+
+#: ./doc/common/tables/nova-hyperv.xml:54(td)
+msgid "vswitch_name = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-hyperv.xml:55(td)
+msgid "(StrOpt) External virtual switch Name, if not provided, the first external virtual switch is used"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml:7(literal)
+msgid "[filter:container_sync]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml:18(td)
+msgid "use = egg:swift#container_sync"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml:21(td)
+msgid "allow_full_urls = true"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_backends.xml:8(caption)
+msgid "Description of configuration options for clients_backends"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_backends.xml:22(td)
+msgid "cloud_backend = heat.engine.clients.OpenStackClients"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_backends.xml:23(td)
+msgid "(StrOpt) Fully qualified class name to use as a client backend."
+msgstr ""
+
+#: ./doc/common/tables/glance-testing.xml:22(td)
+msgid "pydev_worker_debug_host = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-testing.xml:23(td)
+msgid "(StrOpt) The hostname/IP of the pydev process listening for debug connections"
+msgstr ""
+
+#: ./doc/common/tables/glance-testing.xml:26(td)
+msgid "pydev_worker_debug_port = 5678"
+msgstr ""
+
+#: ./doc/common/tables/glance-testing.xml:27(td)
+msgid "(IntOpt) The port on which a pydev process is listening for connections."
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:23(td) ./doc/common/tables/neutron-common.xml:193(td)
+msgid "(StrOpt) Admin password"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:27(td) ./doc/common/tables/neutron-common.xml:197(td)
+msgid "(StrOpt) Admin tenant name"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:31(td)
+msgid "(StrOpt) Admin username"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:34(td)
+msgid "agent_down_time = 75"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:35(td)
+msgid "(IntOpt) Seconds to regard the agent is down; should be at least twice report_interval, to be sure the agent is down for good."
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:42(td)
+msgid "api_workers = 0"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:43(td)
+msgid "(IntOpt) Number of separate worker processes for service"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:46(td)
+msgid "auth_ca_cert = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:47(td)
+msgid "(StrOpt) Certificate Authority public key (CA cert) file for ssl"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:50(td)
+msgid "auth_insecure = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:51(td)
+msgid "(BoolOpt) Turn off verification of the certificate for ssl"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:55(td) ./doc/common/tables/neutron-common.xml:205(td)
+msgid "(StrOpt) Authentication region"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:59(td) ./doc/common/tables/neutron-common.xml:209(td)
+msgid "(StrOpt) The type of authentication to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:63(td) ./doc/common/tables/neutron-common.xml:213(td)
+msgid "(StrOpt) Authentication URL"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:66(td)
+msgid "base_mac = fa:16:3e:00:00:00"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:67(td)
+msgid "(StrOpt) The base MAC address Neutron will use for VIFs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:71(td)
+msgid "(StrOpt) The host IP to bind to"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:74(td)
+msgid "bind_port = 9696"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:75(td)
+msgid "(IntOpt) The port to bind to"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:78(td)
+msgid "ca_certs = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:79(td)
+msgid "(StrOpt) CA certificates"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:82(td)
+msgid "core_plugin = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:83(td)
+msgid "(StrOpt) The core plugin Neutron will use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:86(td)
+msgid "ctl_cert = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:87(td)
+msgid "(StrOpt) controller certificate"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:90(td)
+msgid "ctl_privkey = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:91(td)
+msgid "(StrOpt) controller private key"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:94(td)
+msgid "dhcp_agent_notification = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:95(td)
+msgid "(BoolOpt) Allow sending resource operation notification to DHCP agent"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:98(td)
+msgid "dhcp_agents_per_network = 1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:99(td)
+msgid "(IntOpt) Number of DHCP agents scheduled to host a network."
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:102(td)
+msgid "dhcp_confs = $state_path/dhcp"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:103(td)
+msgid "(StrOpt) Location to store DHCP server config files"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:106(td)
+msgid "dhcp_delete_namespaces = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:107(td)
+msgid "(BoolOpt) Delete namespace after removing a dhcp server."
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:110(td)
+msgid "dhcp_domain = openstacklocal"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:114(td)
+msgid "dhcp_driver = neutron.agent.linux.dhcp.Dnsmasq"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:115(td)
+msgid "(StrOpt) The driver used to manage the DHCP server."
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:118(td)
+msgid "dhcp_lease_duration = 86400"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:119(td)
+msgid "(IntOpt) DHCP lease duration"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:126(td)
+msgid "endpoint_type = adminURL"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:127(td)
+msgid "(StrOpt) Network service endpoint type to pull from the keystone catalog"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:130(td)
+msgid "force_gateway_on_subnet = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:131(td)
+msgid "(BoolOpt) Ensure that configured gateway is on subnet"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:134(td)
+msgid "interface_driver = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:135(td)
+msgid "(StrOpt) The driver used to manage the virtual interface."
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:138(td)
+msgid "ip_lib_force_root = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:139(td)
+msgid "(BoolOpt) Force ip_lib calls to use the root helper"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:146(td)
+msgid "mac_generation_retries = 16"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:147(td)
+msgid "(IntOpt) How many times Neutron will retry MAC generation"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:150(td)
+msgid "max_dns_nameservers = 5"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:151(td)
+msgid "(IntOpt) Maximum number of DNS nameservers"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:154(td)
+msgid "max_fixed_ips_per_port = 5"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:155(td)
+msgid "(IntOpt) Maximum number of fixed ips per port"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:158(td)
+msgid "max_subnet_host_routes = 20"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:159(td)
+msgid "(IntOpt) Maximum number of host routes per subnet"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:162(td)
+msgid "periodic_fuzzy_delay = 5"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:166(td)
+msgid "periodic_interval = 40"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:167(td)
+msgid "(IntOpt) Seconds between running periodic tasks"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:171(td)
+msgid "(IntOpt) Interval between two metering reports"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:175(td) ./doc/common/tables/neutron-common.xml:186(td)
+msgid "(StrOpt) Root helper application."
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:178(td)
+msgid "state_path = /var/lib/neutron"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:179(td)
+msgid "(StrOpt) Where to store Neutron state files. This directory must be writable by the agent."
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:189(th)
+msgid "[PROXY]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml:201(td)
+msgid "(StrOpt) Admin user"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:8(caption)
+msgid "Description of configuration options for hypervisor"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:22(td)
+msgid "default_ephemeral_format = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:23(td)
+msgid "(StrOpt) The default format an ephemeral_volume will be formatted with on creation."
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:26(td)
+msgid "force_raw_images = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:27(td)
+msgid "(BoolOpt) Force backing images to raw format"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:30(td)
+msgid "preallocate_images = none"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:31(td)
+msgid "(StrOpt) VM image preallocation mode: \"none\" =&gt; no storage provisioning is done up front, \"space\" =&gt; storage is fully allocated at instance start"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:34(td)
+msgid "rescue_timeout = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:35(td)
+msgid "(IntOpt) Automatically unrescue an instance after N seconds. Set to 0 to disable."
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:38(td)
+msgid "timeout_nbd = 10"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:39(td)
+msgid "(IntOpt) Amount of time, in seconds, to wait for NBD device start up."
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:42(td)
+msgid "use_cow_images = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:43(td)
+msgid "(BoolOpt) Whether to use cow images"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:46(td)
+msgid "vcpu_pin_set = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:47(td)
+msgid "(StrOpt) Defines which pcpus that instance vcpus can use. For example, \"4-12,^8,15\""
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:50(td)
+msgid "virt_mkfs = []"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:51(td)
+msgid "(MultiStrOpt) Name of the mkfs commands for ephemeral device. The format is &lt;os_type&gt;=&lt;mkfs command&gt;"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:57(td)
+msgid "block_migration_flag = VIR_MIGRATE_UNDEFINE_SOURCE, VIR_MIGRATE_PEER2PEER, VIR_MIGRATE_NON_SHARED_INC"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:58(td)
+msgid "(StrOpt) Migration flags to be set for block migration"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:61(td)
+msgid "disk_cachemodes ="
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:62(td)
+msgid "(ListOpt) Specific cachemodes to use for different disk types e.g: file=directsync,block=none"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:65(td)
+msgid "images_rbd_ceph_conf ="
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:66(td)
+msgid "(StrOpt) Path to the ceph configuration file to use"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:69(td)
+msgid "images_rbd_pool = rbd"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:70(td)
+msgid "(StrOpt) The RADOS pool in which rbd volumes are stored"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:73(td)
+msgid "images_type = default"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:74(td)
+msgid "(StrOpt) VM Images format. Acceptable values are: raw, qcow2, lvm, rbd, default. If default is specified, then use_cow_images flag is used instead of this one."
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:77(td)
+msgid "images_volume_group = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:78(td)
+msgid "(StrOpt) LVM Volume Group that is used for VM images, when you specify images_type=lvm."
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:81(td)
+msgid "inject_key = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:82(td)
+msgid "(BoolOpt) Inject the ssh public key at boot time"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:85(td)
+msgid "inject_partition = -2"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:86(td)
+msgid "(IntOpt) The partition to inject to : -2 =&gt; disable, -1 =&gt; inspect (libguestfs only), 0 =&gt; not partitioned, &gt;0 =&gt; partition number"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:89(td)
+msgid "inject_password = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:90(td)
+msgid "(BoolOpt) Inject the admin password at boot time, without an agent."
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:93(td)
+msgid "iscsi_use_multipath = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:94(td)
+msgid "(BoolOpt) Use multipath connection of the iSCSI volume"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:97(td)
+msgid "iser_use_multipath = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:98(td)
+msgid "(BoolOpt) Use multipath connection of the iSER volume"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:101(td)
+msgid "rescue_image_id = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:102(td)
+msgid "(StrOpt) Rescue ami image"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:105(td)
+msgid "rescue_kernel_id = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:106(td)
+msgid "(StrOpt) Rescue aki image"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:109(td)
+msgid "rescue_ramdisk_id = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:110(td)
+msgid "(StrOpt) Rescue ari image"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:113(td)
+msgid "snapshot_compression = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:114(td)
+msgid "(BoolOpt) Compress snapshot images when possible. This currently applies exclusively to qcow2 images"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:117(td)
+msgid "snapshot_image_format = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:118(td)
+msgid "(StrOpt) Snapshot image format (valid options are : raw, qcow2, vmdk, vdi). Defaults to same as source image"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:121(td)
+msgid "sparse_logical_volumes = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:122(td)
+msgid "(BoolOpt) Create sparse logical volumes (with virtualsize) if this flag is set to True."
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:125(td)
+msgid "use_usb_tablet = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:126(td)
+msgid "(BoolOpt) Sync virtual and real mouse cursors in Windows VMs"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:129(td)
+msgid "use_virtio_for_bridges = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml:130(td)
+msgid "(BoolOpt) Use virtio for bridge interfaces with KVM/QEMU"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml:7(literal)
+msgid "[realm1]"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml:18(td)
+msgid "key = realm1key"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml:21(td)
+msgid "key2 = realm1key2"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml:24(td)
+msgid "cluster_name1 = https://host1/v1/"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml:27(td)
+msgid "cluster_name2 = https://host2/v1/"
+msgstr ""
+
+#: ./doc/common/tables/nova-wsgi.xml:23(td)
+msgid "(StrOpt) File name for the paste.deploy config for nova-api"
+msgstr ""
+
+#: ./doc/common/tables/nova-wsgi.xml:31(td)
+msgid "(StrOpt) SSL certificate of API server"
+msgstr ""
+
+#: ./doc/common/tables/nova-wsgi.xml:35(td)
+msgid "(StrOpt) SSL private key of API server"
+msgstr ""
+
+#: ./doc/common/tables/nova-wsgi.xml:42(td)
+msgid "wsgi_default_pool_size = 1000"
+msgstr ""
+
+#: ./doc/common/tables/nova-wsgi.xml:43(td)
+msgid "(IntOpt) Size of the pool of greenthreads used by wsgi"
+msgstr ""
+
+#: ./doc/common/tables/nova-wsgi.xml:46(td)
+msgid "wsgi_log_format = %(client_ip)s \"%(request_line)s\" status: %(status_code)s len: %(body_length)s time: %(wall_seconds).7f"
+msgstr ""
+
+#: ./doc/common/tables/nova-wsgi.xml:47(td)
+msgid "(StrOpt) A python format string that is used as the template to generate log lines. The following values can be formatted into it: client_ip, date_time, request_line, status_code, body_length, wall_seconds."
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml:8(caption)
+msgid "Description of configuration options for cache"
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml:19(th)
+msgid "[cache]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml:22(td)
+msgid "backend = keystone.common.cache.noop"
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml:23(td)
+msgid "(StrOpt) Dogpile.cache backend module. It is recommended that Memcache (dogpile.cache.memcache) or Redis (dogpile.cache.redis) be used in production deployments. Small workloads (single process) like devstack can use the dogpile.cache.memory backend."
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml:26(td)
+msgid "backend_argument = []"
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml:27(td)
+msgid "(MultiStrOpt) Arguments supplied to the backend module. Specify this option once per argument to be passed to the dogpile.cache backend. Example format: \"&lt;argname&gt;:&lt;value&gt;\"."
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml:30(td)
+msgid "config_prefix = cache.keystone"
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml:31(td)
+msgid "(StrOpt) Prefix for building the configuration dictionary for the cache region. This should not need to be changed unless there is another dogpile.cache region with the same configuration name."
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml:34(td)
+msgid "debug_cache_backend = False"
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml:35(td)
+msgid "(BoolOpt) Extra debugging from the cache backend (cache keys, get/set/delete/etc calls) This is only really useful if you need to see the specific cache-backend get/set/delete calls with the keys/values. Typically this should be left set to False."
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml:39(td)
+msgid "(BoolOpt) Global toggle for all caching using the should_cache_fn mechanism."
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml:42(td)
+msgid "expiration_time = 600"
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml:43(td)
+msgid "(IntOpt) Default TTL, in seconds, for any cached item in the dogpile.cache region. This applies to any cached method that doesn't have an explicit cache expiration time defined for it."
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml:46(td)
+msgid "proxies ="
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml:47(td)
+msgid "(ListOpt) Proxy Classes to import that will affect the way the dogpile.cache backend functions. See the dogpile.cache documentation on changing-backend-behavior. Comma delimited list e.g. my.dogpile.proxy.Class, my.dogpile.proxyClass2."
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml:50(td)
+msgid "use_key_mangler = True"
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml:51(td)
+msgid "(BoolOpt) Use a key-mangling function (sha1) to ensure fixed length cache-keys. This is toggle-able for debugging purposes, it is highly recommended to always leave this set to True."
+msgstr ""
+
+#: ./doc/common/tables/nova-configdrive.xml:8(caption)
+msgid "Description of configuration options for configdrive"
+msgstr ""
+
+#: ./doc/common/tables/nova-configdrive.xml:22(td)
+msgid "config_drive_format = iso9660"
+msgstr ""
+
+#: ./doc/common/tables/nova-configdrive.xml:23(td)
+msgid "(StrOpt) Config drive format. One of iso9660 (default) or vfat"
+msgstr ""
+
+#: ./doc/common/tables/nova-configdrive.xml:26(td)
+msgid "config_drive_skip_versions = 1.0 2007-01-19 2007-03-01 2007-08-29 2007-10-10 2007-12-15 2008-02-01 2008-09-01"
+msgstr ""
+
+#: ./doc/common/tables/nova-configdrive.xml:27(td)
+msgid "(StrOpt) List of metadata versions to skip placing into the config drive"
+msgstr ""
+
+#: ./doc/common/tables/nova-configdrive.xml:30(td)
+msgid "config_drive_tempdir = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-configdrive.xml:31(td)
+msgid "(StrOpt) Where to put temporary files associated with config drive creation"
+msgstr ""
+
+#: ./doc/common/tables/nova-configdrive.xml:34(td)
+msgid "force_config_drive = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-configdrive.xml:35(td)
+msgid "(StrOpt) Set to force injection to take place on a config drive (if set, valid options are: always)"
+msgstr ""
+
+#: ./doc/common/tables/nova-configdrive.xml:38(td)
+msgid "mkisofs_cmd = genisoimage"
+msgstr ""
+
+#: ./doc/common/tables/nova-configdrive.xml:45(td)
+msgid "config_drive_cdrom = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-configdrive.xml:46(td)
+msgid "(BoolOpt) Attaches the Config Drive image as a cdrom drive instead of a disk drive"
+msgstr ""
+
+#: ./doc/common/tables/nova-configdrive.xml:49(td)
+msgid "config_drive_inject_password = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-configdrive.xml:50(td)
+msgid "(BoolOpt) Sets the admin password in the config drive image"
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml:8(caption)
+msgid "Description of configuration options for token"
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml:19(th)
+msgid "[token]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml:22(td)
+msgid "bind ="
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml:23(td)
+msgid "(ListOpt) External auth mechanisms that should add bind information to token e.g. kerberos, x509."
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml:27(td)
+msgid "(IntOpt) Time to cache tokens (in seconds). This has no effect unless global and token caching are enabled."
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml:31(td)
+msgid "(BoolOpt) Toggle for token system cacheing. This has no effect unless global caching is enabled."
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml:34(td)
+msgid "driver = keystone.token.backends.sql.Token"
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml:35(td)
+msgid "(StrOpt) Keystone Token persistence backend driver."
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml:39(td)
+msgid "(StrOpt) Enforcement policy on tokens presented to keystone with bind information. One of disabled, permissive, strict, required or a specifically required bind mode e.g. kerberos or x509 to require binding to that authentication."
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml:42(td)
+msgid "expiration = 3600"
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml:43(td)
+msgid "(IntOpt) Amount of time a token should remain valid (in seconds)."
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml:46(td)
+msgid "provider = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml:47(td)
+msgid "(StrOpt) Controls the token construction, validation, and revocation operations. Core providers are \"keystone.token.providers.[pki|uuid].Provider\"."
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml:50(td)
+msgid "revocation_cache_time = 3600"
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml:51(td)
+msgid "(IntOpt) Time to cache the revocation list and the revocation events if revoke extension is enabled (in seconds). This has no effect unless global and token caching are enabled."
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml:54(td)
+msgid "revoke_by_id = True"
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml:55(td)
+msgid "(BoolOpt) Revoke token by token identifier. Setting revoke_by_id to True enables various forms of enumerating tokens, e.g. `list tokens for user`. These enumerations are processed to determine the list of tokens to revoke. Only disable if you are switching to using the Revoke extension with a backend other than KVS, which stores events in memory."
+msgstr ""
+
+#: ./doc/common/tables/heat-database.xml:23(td)
+msgid "(StrOpt) The backend to use for db."
+msgstr ""
+
+#: ./doc/common/tables/heat-database.xml:26(td)
+msgid "sqlite_db = heat.sqlite"
+msgstr ""
+
+#: ./doc/common/tables/heat-database.xml:41(td)
+msgid "connection = sqlite:////usr/lib/python/site-packages/heat/openstack/common/db/$sqlite_db"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2.xml:8(caption)
+msgid "Description of configuration options for ml2"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2.xml:19(th)
+msgid "[ml2]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2.xml:22(td)
+msgid "mechanism_drivers ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2.xml:23(td)
+msgid "(ListOpt) An ordered list of networking mechanism driver entrypoints to be loaded from the neutron.ml2.mechanism_drivers namespace."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2.xml:26(td)
+msgid "tenant_network_types = local"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2.xml:27(td)
+msgid "(ListOpt) Ordered list of network_types to allocate as tenant networks."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2.xml:30(td)
+msgid "type_drivers = local, flat, vlan, gre, vxlan"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2.xml:31(td)
+msgid "(ListOpt) List of network type driver entrypoints to be loaded from the neutron.ml2.type_drivers namespace."
+msgstr ""
+
+#: ./doc/common/tables/neutron-db.xml:22(td)
+msgid "sqlite_db ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-db.xml:37(td)
+msgid "connection = sqlite://"
+msgstr ""
+
+#: ./doc/common/tables/neutron-db.xml:69(td)
+msgid "max_overflow = 20"
+msgstr ""
+
+#: ./doc/common/tables/neutron-db.xml:73(td)
+msgid "max_pool_size = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-db.xml:85(td)
+msgid "pool_timeout = 10"
+msgstr ""
+
+#: ./doc/common/tables/keystone-database.xml:86(td)
+msgid "sqlite_db = keystone.sqlite"
+msgstr ""
+
+#: ./doc/common/tables/keystone-memcache.xml:8(caption)
+msgid "Description of configuration options for memcache"
+msgstr ""
+
+#: ./doc/common/tables/keystone-memcache.xml:22(td)
+msgid "max_compare_and_set_retry = 16"
+msgstr ""
+
+#: ./doc/common/tables/keystone-memcache.xml:23(td)
+msgid "(IntOpt) Number of compare-and-set attempts to make when using compare-and-set in the token memcache back end."
+msgstr ""
+
+#: ./doc/common/tables/keystone-memcache.xml:26(td)
+msgid "servers = localhost:11211"
+msgstr ""
+
+#: ./doc/common/tables/keystone-memcache.xml:27(td)
+msgid "(ListOpt) Memcache servers in the format of \"host:port\""
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml:42(td)
+msgid "pydev_debug = disabled"
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml:43(td)
+msgid "(StrOpt) Enable or disable pydev remote debugging. If value is 'auto' tries to connect to remote debugger server, but in case of error continues running with debugging disabled."
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml:46(td) ./doc/common/tables/keystone-debug.xml:42(td)
+msgid "pydev_debug_host = None"
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml:47(td)
+msgid "(StrOpt) Pydev debug server host (localhost by default)."
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml:50(td) ./doc/common/tables/keystone-debug.xml:46(td)
+msgid "pydev_debug_port = None"
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml:51(td)
+msgid "(IntOpt) Pydev debug server port (5678 by default)."
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml:54(td)
+msgid "remote_cinder_client = trove.common.remote.cinder_client"
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml:58(td)
+msgid "remote_dns_client = trove.common.remote.dns_client"
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml:62(td)
+msgid "remote_guest_client = trove.common.remote.guest_client"
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml:66(td)
+msgid "remote_heat_client = trove.common.remote.heat_client"
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml:70(td)
+msgid "remote_nova_client = trove.common.remote.nova_client"
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml:74(td)
+msgid "remote_swift_client = trove.common.remote.swift_client"
+msgstr ""
+
+#: ./doc/common/tables/trove-swift.xml:22(td)
+msgid "swift_url = http://localhost:8080/v1/AUTH_"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml:8(caption)
+msgid "Description of configuration options for tilera"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml:22(td)
+msgid "tile_pdu_ip = 10.0.100.1"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml:23(td)
+msgid "(StrOpt) IP address of tilera pdu"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml:26(td)
+msgid "tile_pdu_mgr = /tftpboot/pdu_mgr"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml:27(td)
+msgid "(StrOpt) Management script for tilera pdu"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml:30(td)
+msgid "tile_pdu_off = 2"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml:31(td)
+msgid "(IntOpt) Power status of tilera PDU is OFF"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml:34(td)
+msgid "tile_pdu_on = 1"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml:35(td)
+msgid "(IntOpt) Power status of tilera PDU is ON"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml:38(td)
+msgid "tile_pdu_status = 9"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml:39(td)
+msgid "(IntOpt) Power status of tilera PDU"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml:42(td)
+msgid "tile_power_wait = 9"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml:43(td)
+msgid "(IntOpt) Wait time in seconds until check the result after tilera power operations"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:8(caption)
+msgid "Description of configuration options for libvirt"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:22(td)
+msgid "remove_unused_base_images = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:23(td)
+msgid "(BoolOpt) Should unused base images be removed?"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:26(td)
+msgid "remove_unused_original_minimum_age_seconds = 86400"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:27(td)
+msgid "(IntOpt) Unused unresized base images younger than this will not be removed"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:33(td)
+msgid "checksum_base_images = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:34(td)
+msgid "(BoolOpt) Write a checksum for files in _base to disk"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:37(td)
+msgid "checksum_interval_seconds = 3600"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:38(td)
+msgid "(IntOpt) How frequently to checksum base images"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:41(td)
+msgid "connection_uri ="
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:42(td)
+msgid "(StrOpt) Override the default libvirt URI (which is dependent on virt_type)"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:45(td)
+msgid "cpu_mode = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:46(td)
+msgid "(StrOpt) Set to \"host-model\" to clone the host CPU feature flags; to \"host-passthrough\" to use the host CPU model exactly; to \"custom\" to use a named CPU model; to \"none\" to not set any CPU model. If virt_type=\"kvm|qemu\", it will default to \"host-model\", otherwise it will default to \"none\""
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:49(td)
+msgid "cpu_model = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:50(td)
+msgid "(StrOpt) Set to a named libvirt CPU model (see names listed in /usr/share/libvirt/cpu_map.xml). Only has effect if cpu_mode=\"custom\" and virt_type=\"kvm|qemu\""
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:53(td)
+msgid "disk_prefix = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:54(td)
+msgid "(StrOpt) Override the default disk prefix for the devices attached to a server, which is dependent on virt_type. (valid options are: sd, xvd, uvd, vd)"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:57(td)
+msgid "image_info_filename_pattern = $instances_path/$image_cache_subdirectory_name/%(image)s.info"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:58(td)
+msgid "(StrOpt) Allows image information files to be stored in non-standard locations"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:61(td)
+msgid "remove_unused_kernels = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:62(td)
+msgid "(BoolOpt) Should unused kernel images be removed? This is only safe to enable if all compute nodes have been updated to support this option. This will be enabled by default in future."
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:65(td)
+msgid "remove_unused_resized_minimum_age_seconds = 3600"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:66(td)
+msgid "(IntOpt) Unused resized base images younger than this will not be removed"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:69(td)
+msgid "rng_dev_path = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:70(td)
+msgid "(StrOpt) A path to a device that will be used as source of entropy on the host. Permitted options are: /dev/random or /dev/hwrng"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:73(td)
+msgid "snapshots_directory = $instances_path/snapshots"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:74(td)
+msgid "(StrOpt) Location where libvirt driver will store snapshots before uploading them to image service"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:77(td)
+msgid "vif_driver = nova.virt.libvirt.vif.LibvirtGenericVIFDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:78(td)
+msgid "(StrOpt) DEPRECATED. The libvirt VIF driver to configure the VIFs.This option is deprecated and will be removed in the Juno release."
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:81(td)
+msgid "virt_type = kvm"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:82(td)
+msgid "(StrOpt) Libvirt domain type (valid options are: kvm, lxc, qemu, uml, xen)"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:86(td)
+msgid "(StrOpt) Method used to wipe old volumes (valid options are: none, zero, shred)"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:93(td)
+msgid "volume_drivers = iscsi=nova.virt.libvirt.volume.LibvirtISCSIVolumeDriver, iser=nova.virt.libvirt.volume.LibvirtISERVolumeDriver, local=nova.virt.libvirt.volume.LibvirtVolumeDriver, fake=nova.virt.libvirt.volume.LibvirtFakeVolumeDriver, rbd=nova.virt.libvirt.volume.LibvirtNetVolumeDriver, sheepdog=nova.virt.libvirt.volume.LibvirtNetVolumeDriver, nfs=nova.virt.libvirt.volume.LibvirtNFSVolumeDriver, aoe=nova.virt.libvirt.volume.LibvirtAOEVolumeDriver, glusterfs=nova.virt.libvirt.volume.LibvirtGlusterfsVolumeDriver, fibre_channel=nova.virt.libvirt.volume.LibvirtFibreChannelVolumeDriver, scality=nova.virt.libvirt.volume.LibvirtScalityVolumeDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:94(td)
+msgid "(ListOpt) Libvirt handlers for remote volumes."
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:97(td)
+msgid "wait_soft_reboot_seconds = 120"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml:98(td)
+msgid "(IntOpt) Number of seconds to wait for instance to shut down after soft reboot request is made. We fall back to hard reboot if instance does not shutdown within this window."
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml:8(caption)
+msgid "Description of configuration options for mlnx"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml:22(td)
+msgid "backoff_rate = 2"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml:23(td)
+msgid "(IntOpt) backoff rate multiplier for waiting period between retries for request to daemon, i.e. value of 2 will double the request timeout each retry"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml:26(td)
+msgid "daemon_endpoint = tcp://127.0.0.1:60001"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml:27(td)
+msgid "(StrOpt) eswitch daemon end point"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml:34(td)
+msgid "request_timeout = 3000"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml:35(td)
+msgid "(IntOpt) The number of milliseconds the agent will wait for response on request to daemon."
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml:38(th)
+msgid "[MLNX]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml:41(td)
+msgid "network_vlan_ranges = default:1:1000"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml:45(td)
+msgid "physical_network_type = eth"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml:46(td)
+msgid "(StrOpt) Physical network type for provider network (eth or ib)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml:49(td)
+msgid "physical_network_type_mappings ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml:50(td)
+msgid "(ListOpt) List of &lt;physical_network&gt;:&lt;physical_network_type&gt; with physical_network_type is either eth or ib"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml:53(td)
+msgid "tenant_network_type = vlan"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_manager.xml:8(caption)
+msgid "Description of configuration options for zoning_manager"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_manager.xml:22(td)
+msgid "brcd_sb_connector = cinder.zonemanager.drivers.brocade.brcd_fc_zone_client_cli.BrcdFCZoneClientCLI"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_manager.xml:23(td)
+msgid "(StrOpt) Southbound connector for zoning operation"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_manager.xml:26(td)
+msgid "fc_san_lookup_service = cinder.zonemanager.drivers.brocade.brcd_fc_san_lookup_service.BrcdFCSanLookupService"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_manager.xml:27(td)
+msgid "(StrOpt) FC San Lookup Service"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_manager.xml:30(td)
+msgid "zone_driver = cinder.zonemanager.drivers.brocade.brcd_fc_zone_driver.BrcdFCZoneDriver"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_manager.xml:31(td)
+msgid "(StrOpt) FC Zone Driver responsible for zone management"
+msgstr ""
+
+#: ./doc/common/tables/glance-ssl.xml:27(td)
+msgid "(StrOpt) Certificate file to use when starting API server securely."
+msgstr ""
+
+#: ./doc/common/tables/glance-ssl.xml:31(td)
+msgid "(StrOpt) Private key file to use when starting API server securely."
+msgstr ""
+
+#: ./doc/common/tables/neutron-securitygroups.xml:8(caption)
+msgid "Description of configuration options for securitygroups"
+msgstr ""
+
+#: ./doc/common/tables/neutron-securitygroups.xml:19(th)
+msgid "[SECURITYGROUP]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-securitygroups.xml:22(td)
+msgid "enable_security_group = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-securitygroups.xml:23(td)
+msgid "(BoolOpt) Controls whether the neutron security group API is enabled in the server. It should be false when using no security groups or using the nova security group API."
+msgstr ""
+
+#: ./doc/common/tables/neutron-securitygroups.xml:27(td)
+msgid "(StrOpt) Driver for security groups firewall in the L2 agent"
+msgstr ""
+
+#: ./doc/common/tables/keystone-debug.xml:43(td)
+msgid "(StrOpt) Host to connect to for remote debugger."
+msgstr ""
+
+#: ./doc/common/tables/keystone-debug.xml:47(td)
+msgid "(IntOpt) Port to connect to for remote debugger."
+msgstr ""
+
+#: ./doc/common/tables/keystone-debug.xml:50(td)
+msgid "standard_threads = False"
+msgstr ""
+
+#: ./doc/common/tables/keystone-debug.xml:51(td)
+msgid "(BoolOpt) Do not monkey-patch threading system modules."
+msgstr ""
+
+#: ./doc/common/tables/cinder-rootwrap.xml:22(td)
+msgid "filters_path = /etc/cinder/rootwrap.d,/usr/share/cinder/rootwrap"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:8(caption)
+msgid "Description of configuration options for nexenta_iscsi"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:22(td)
+msgid "nexenta_blocksize ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:23(td)
+msgid "(StrOpt) block size for volumes (blank=default,8KB)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:26(td)
+msgid "nexenta_host ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:27(td)
+msgid "(StrOpt) IP address of Nexenta SA"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:30(td)
+msgid "nexenta_iscsi_target_portal_port = 3260"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:31(td)
+msgid "(IntOpt) Nexenta target portal port"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:34(td)
+msgid "nexenta_password = nexenta"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:35(td)
+msgid "(StrOpt) Password to connect to Nexenta SA"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:38(td)
+msgid "nexenta_rest_port = 2000"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:39(td)
+msgid "(IntOpt) HTTP port to connect to Nexenta REST API server"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:42(td)
+msgid "nexenta_rest_protocol = auto"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:43(td)
+msgid "(StrOpt) Use http or https for REST connection (default auto)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:46(td)
+msgid "nexenta_rrmgr_compression = 0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:47(td)
+msgid "(IntOpt) Enable stream compression, level 1..9. 1 - gives best speed; 9 - gives best compression."
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:50(td)
+msgid "nexenta_rrmgr_connections = 2"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:51(td)
+msgid "(IntOpt) Number of TCP connections."
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:54(td)
+msgid "nexenta_rrmgr_tcp_buf_size = 4096"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:55(td)
+msgid "(IntOpt) TCP Buffer size in KiloBytes."
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:58(td)
+msgid "nexenta_sparse = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:59(td)
+msgid "(BoolOpt) flag to create sparse volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:62(td)
+msgid "nexenta_sparsed_volumes = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:66(td)
+msgid "nexenta_target_group_prefix = cinder/"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:67(td)
+msgid "(StrOpt) prefix for iSCSI target groups on SA"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:70(td)
+msgid "nexenta_target_prefix = iqn.1986-03.com.sun:02:cinder-"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:71(td)
+msgid "(StrOpt) IQN prefix for iSCSI targets"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:74(td)
+msgid "nexenta_user = admin"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:75(td)
+msgid "(StrOpt) User name to connect to Nexenta SA"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:78(td)
+msgid "nexenta_volume = cinder"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:79(td)
+msgid "(StrOpt) pool on SA that will hold all volumes"
+msgstr ""
+
 #. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
-#: ./doc/common/tables/nova-xvpnvncproxy.xml:0(None)
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml:0(None)
 msgid "translator-credits"
 msgstr ""
 
diff --git a/doc/common/locale/fr.po b/doc/common/locale/fr.po
index 8c278fd271..75fce0a0a7 100644
--- a/doc/common/locale/fr.po
+++ b/doc/common/locale/fr.po
@@ -18,8 +18,8 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: OpenStack Manuals\n"
-"POT-Creation-Date: 2014-06-02 05:41+0000\n"
-"PO-Revision-Date: 2014-06-02 04:30+0000\n"
+"POT-Creation-Date: 2014-06-03 02:30+0000\n"
+"PO-Revision-Date: 2014-06-03 02:40+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"
@@ -28,1266 +28,65 @@ msgstr ""
 "Language: fr\n"
 "Plural-Forms: nplurals=2; plural=(n > 1);\n"
 
-#: ./doc/common/app_support.xml7(title)
-msgid "Community support"
-msgstr "Soutien Communautaire"
-
-#: ./doc/common/app_support.xml8(para)
-msgid ""
-"The following resources are available to help you run and use OpenStack. The"
-" OpenStack community constantly improves and adds to the main features of "
-"OpenStack, but if you have any questions, do not hesitate to ask. Use the "
-"following resources to get OpenStack support, and troubleshoot your "
-"installations."
-msgstr ""
-
-#: ./doc/common/app_support.xml15(title)
-msgid "Documentation"
-msgstr "Documentation"
-
-#: ./doc/common/app_support.xml16(para)
-msgid ""
-"For the available OpenStack documentation, see <link "
-"href=\"http://docs.openstack.org\">docs.openstack.org</link>."
-msgstr ""
-
-#: ./doc/common/app_support.xml19(para) ./doc/common/app_support.xml393(para)
-#: ./doc/common/ch_getstart.xml208(para)
-msgid ""
-"To provide feedback on documentation, join and use the <email>openstack-"
-"docs@lists.openstack.org</email> mailing list at <link "
-"href=\"http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-"
-"docs\">OpenStack Documentation Mailing List</link>, or <link "
-"href=\"https://bugs.launchpad.net/openstack-manuals/+filebug\">report a "
-"bug</link>."
-msgstr ""
-
-#: ./doc/common/app_support.xml26(para)
-msgid ""
-"The following books explain how to install an OpenStack cloud and its "
-"associated components:"
-msgstr ""
-
-#: ./doc/common/app_support.xml33(citetitle)
-msgid "Installation Guide for Debian 7.0"
-msgstr "Installation sur Debian 7.0 "
-
-#: ./doc/common/app_support.xml41(citetitle)
-msgid "Installation Guide for openSUSE and SUSE Linux Enterprise Server"
-msgstr "Installation sur openSUSE ou SUSE Linux Enterprise Server"
-
-#: ./doc/common/app_support.xml49(citetitle)
-msgid "Installation Guide for Red Hat Enterprise Linux, CentOS, and Fedora"
-msgstr "Installation sur Red Hat Enterprise Linux, CentOS et Fedora"
-
-#: ./doc/common/app_support.xml58(citetitle)
-msgid "Installation Guide for Ubuntu 12.04/14.04 (LTS)"
-msgstr ""
-
-#: ./doc/common/app_support.xml63(para)
-msgid ""
-"The following books explain how to configure and run an OpenStack cloud:"
-msgstr ""
-
-#: ./doc/common/app_support.xml70(citetitle)
-msgid "Cloud Administrator Guide"
-msgstr ""
-
-#: ./doc/common/app_support.xml76(citetitle)
-msgid "Configuration Reference"
-msgstr "Référence de Configuration"
-
-#: ./doc/common/app_support.xml82(citetitle)
-msgid "Operations Guide"
-msgstr "Guide d'Opérations"
-
-#: ./doc/common/app_support.xml88(citetitle)
-msgid "High Availability Guide"
-msgstr ""
-
-#: ./doc/common/app_support.xml94(citetitle)
-msgid "Security Guide"
-msgstr "Guide de sécurité"
-
-#: ./doc/common/app_support.xml100(citetitle)
-msgid "Virtual Machine Image Guide"
-msgstr ""
-
-#: ./doc/common/app_support.xml104(para)
-msgid ""
-"The following books explain how to use the OpenStack dashboard and command-"
-"line clients:"
-msgstr ""
-
-#: ./doc/common/app_support.xml111(citetitle)
-msgid "API Quick Start"
-msgstr ""
-
-#: ./doc/common/app_support.xml118(citetitle)
-msgid "End User Guide"
-msgstr "fin du guide utilisateur"
-
-#: ./doc/common/app_support.xml125(citetitle)
-msgid "Admin User Guide"
-msgstr ""
-
-#: ./doc/common/app_support.xml132(citetitle)
-msgid "Command-Line Interface Reference"
-msgstr ""
-
-#: ./doc/common/app_support.xml136(para)
-msgid ""
-"The following documentation provides reference and guidance information for "
-"the OpenStack APIs:"
-msgstr ""
-
-#: ./doc/common/app_support.xml142(link)
-msgid "OpenStack API Complete Reference (HTML)"
-msgstr ""
-
-#: ./doc/common/app_support.xml148(link)
-msgid "API Complete Reference (PDF)"
-msgstr ""
-
-#: ./doc/common/app_support.xml153(citetitle)
-msgid "OpenStack Block Storage Service API v2 Reference"
-msgstr "Reference de l'API du service OpenStack Block Storage v2"
-
-#: ./doc/common/app_support.xml160(citetitle)
-msgid "OpenStack Compute API v2 and Extensions Reference"
-msgstr ""
-
-#: ./doc/common/app_support.xml167(citetitle)
-msgid "OpenStack Identity Service API v2.0 Reference"
-msgstr ""
-
-#: ./doc/common/app_support.xml173(citetitle)
-msgid "OpenStack Image Service API v2 Reference"
-msgstr ""
-
-#: ./doc/common/app_support.xml179(citetitle)
-msgid "OpenStack Networking API v2.0 Reference"
-msgstr ""
-
-#: ./doc/common/app_support.xml185(citetitle)
-msgid "OpenStack Object Storage API v1 Reference"
-msgstr ""
-
-#: ./doc/common/app_support.xml189(para)
-msgid ""
-"The <link href=\"http://docs.openstack.org/training-"
-"guides/content/\"><citetitle>Training Guides</citetitle></link> offer "
-"software training for cloud administration and management."
-msgstr ""
-
-#: ./doc/common/app_support.xml196(title)
-msgid "ask.openstack.org"
-msgstr "ask.openstack.org"
-
-#: ./doc/common/app_support.xml197(para)
-msgid ""
-"During the set up or testing of OpenStack, you might have questions about "
-"how a specific task is completed or be in a situation where a feature does "
-"not work correctly. Use the <link "
-"href=\"http://ask.openstack.org\">ask.openstack.org</link> site to ask "
-"questions and get answers. When you visit the <link "
-"href=\"http://ask.openstack.org\">http://ask.openstack.org</link> site, scan"
-" the recently asked questions to see whether your question has already been "
-"answered. If not, ask a new question. Be sure to give a clear, concise "
-"summary in the title and provide as much detail as possible in the "
-"description. Paste in your command output or stack traces, links to screen "
-"shots, and any other information which might be useful."
-msgstr ""
-
-#: ./doc/common/app_support.xml214(title)
-msgid "OpenStack mailing lists"
-msgstr "listes de diffusion OpenStack"
-
-#: ./doc/common/app_support.xml215(para)
-msgid ""
-"A great way to get answers and insights is to post your question or "
-"problematic scenario to the OpenStack mailing list. You can learn from and "
-"help others who might have similar issues. To subscribe or view the "
-"archives, go to <link href=\"http://lists.openstack.org/cgi-"
-"bin/mailman/listinfo/openstack\">http://lists.openstack.org/cgi-"
-"bin/mailman/listinfo/openstack</link>. You might be interested in the other "
-"mailing lists for specific projects or development, which you can find <link"
-" href=\"http://wiki.openstack.org/MailingLists\">on the wiki</link>. A "
-"description of all mailing lists is available at <link "
-"href=\"http://wiki.openstack.org/MailingLists\">http://wiki.openstack.org/MailingLists</link>."
-msgstr ""
-
-#: ./doc/common/app_support.xml231(title)
-msgid "The OpenStack wiki"
-msgstr "Le wiki OpenStack "
-
-#: ./doc/common/app_support.xml232(para)
-msgid ""
-"The <link href=\"http://wiki.openstack.org/\">OpenStack wiki</link> contains"
-" a broad range of topics but some of the information can be difficult to "
-"find or is a few pages deep. Fortunately, the wiki search feature enables "
-"you to search by title or content. If you search for specific information, "
-"such as about networking or nova, you can find a large amount of relevant "
-"material. More is being added all the time, so be sure to check back often. "
-"You can find the search box in the upper-right corner of any OpenStack wiki "
-"page."
-msgstr ""
-
-#: ./doc/common/app_support.xml243(title)
-msgid "The Launchpad Bugs area"
-msgstr "La zone Launchpad Bugs"
-
-#: ./doc/common/app_support.xml244(para)
-msgid ""
-"The OpenStack community values your set up and testing efforts and wants "
-"your feedback. To log a bug, you must sign up for a Launchpad account at "
-"<link "
-"href=\"https://launchpad.net/+login\">https://launchpad.net/+login</link>. "
-"You can view existing bugs and report bugs in the Launchpad Bugs area. Use "
-"the search feature to determine whether the bug has already been reported or"
-" already been fixed. If it still seems like your bug is unreported, fill out"
-" a bug report."
-msgstr ""
-
-#: ./doc/common/app_support.xml252(para)
-msgid "Some tips:"
-msgstr "Quelques conseils :"
-
-#: ./doc/common/app_support.xml255(para)
-msgid "Give a clear, concise summary."
-msgstr ""
-
-#: ./doc/common/app_support.xml258(para)
-msgid ""
-"Provide as much detail as possible in the description. Paste in your command"
-" output or stack traces, links to screen shots, and any other information "
-"which might be useful."
-msgstr ""
-
-#: ./doc/common/app_support.xml264(para)
-msgid ""
-"Be sure to include the software and package versions that you are using, "
-"especially if you are using a development branch, such as, <literal>\"Juno "
-"release\" vs git commit bc79c3ecc55929bac585d04a03475b72e06a3208</literal>."
-msgstr ""
-
-#: ./doc/common/app_support.xml271(para)
-msgid ""
-"Any deployment-specific information is helpful, such as whether you are "
-"using Ubuntu 14.04 or are performing a multi-node installation."
-msgstr ""
-
-#: ./doc/common/app_support.xml276(para)
-msgid "The following Launchpad Bugs areas are available:"
-msgstr ""
-
-#: ./doc/common/app_support.xml282(link)
-msgid "Bugs: OpenStack Block Storage (cinder)"
-msgstr ""
-
-#: ./doc/common/app_support.xml288(link)
-msgid "Bugs: OpenStack Compute (nova)"
-msgstr "Bugs: OpenStack Calcul (nova)"
-
-#: ./doc/common/app_support.xml293(link)
-msgid "Bugs: OpenStack Dashboard (horizon)"
-msgstr "Bugs: OpenStack Tableau de Bord (horizon)"
-
-#: ./doc/common/app_support.xml299(link)
-msgid "Bugs: OpenStack Identity (keystone)"
-msgstr "Bugs: OpenStack Identité (keystone)"
-
-#: ./doc/common/app_support.xml305(link)
-msgid "Bugs: OpenStack Image Service (glance)"
-msgstr "Bugs: OpenStack Service d'Image (glance)"
-
-#: ./doc/common/app_support.xml311(link)
-msgid "Bugs: OpenStack Networking (neutron)"
-msgstr "Bugs: OpenStack Réseau (neutron)"
-
-#: ./doc/common/app_support.xml317(link)
-msgid "Bugs: OpenStack Object Storage (swift)"
-msgstr "Bugs: OpenStack Stockage d'Objets (swift)"
-
-#: ./doc/common/app_support.xml324(link)
-msgid "Bugs: Bare Metal (ironic)"
-msgstr ""
-
-#: ./doc/common/app_support.xml329(link)
-msgid "Bugs: Data Processing Service (sahara)"
-msgstr ""
-
-#: ./doc/common/app_support.xml335(link)
-msgid "Bugs: Database Service (trove)"
-msgstr "Bugs: La Service Base de Données (trove)"
-
-#: ./doc/common/app_support.xml340(link)
-msgid "Bugs: Orchestration (heat)"
-msgstr "Bugs: l'Orchestration (heat)"
-
-#: ./doc/common/app_support.xml345(link)
-msgid "Bugs: Telemetry (ceilometer)"
-msgstr "Bugs: Métrologie (ceilometer)"
-
-#: ./doc/common/app_support.xml350(link)
-msgid "Bugs: Queue Service (marconi)"
-msgstr ""
-
-#: ./doc/common/app_support.xml356(link)
-msgid "Bugs: OpenStack API Documentation (developer.openstack.org)"
-msgstr ""
-
-#: ./doc/common/app_support.xml362(link)
-msgid "Bugs: OpenStack Documentation (docs.openstack.org)"
-msgstr ""
-
-#: ./doc/common/app_support.xml368(title)
-msgid "The OpenStack IRC channel"
-msgstr "Le canal OpenStack IRC"
-
-#: ./doc/common/app_support.xml369(para)
-msgid ""
-"The OpenStack community lives in the #openstack IRC channel on the Freenode "
-"network. You can hang out, ask questions, or get immediate feedback for "
-"urgent and pressing issues. To install an IRC client or use a browser-based "
-"client, go to <link "
-"href=\"http://webchat.freenode.net\">http://webchat.freenode.net/</link>. "
-"You can also use Colloquy (Mac OS X, <link "
-"href=\"http://colloquy.info/\">http://colloquy.info/</link>), mIRC (Windows,"
-" <link href=\"http://www.mirc.com/\">http://www.mirc.com/</link>), or XChat "
-"(Linux). When you are in the IRC channel and want to share code or command "
-"output, the generally accepted method is to use a Paste Bin. The OpenStack "
-"project has one at <link "
-"href=\"http://paste.openstack.org\">http://paste.openstack.org</link>. Just "
-"paste your longer amounts of text or logs in the web form and you get a URL "
-"that you can paste into the channel. The OpenStack IRC channel is "
-"<literal>#openstack</literal> on <literal>irc.freenode.net</literal>. You "
-"can find a list of all OpenStack IRC channels at <link "
-"href=\"https://wiki.openstack.org/wiki/IRC\">https://wiki.openstack.org/wiki/IRC</link>."
-msgstr ""
-
-#: ./doc/common/app_support.xml392(title)
-msgid "Documentation feedback"
-msgstr "commentaires sur la documentation"
-
-#: ./doc/common/app_support.xml399(title)
-msgid "OpenStack distribution packages"
-msgstr ""
-
-#: ./doc/common/app_support.xml400(para)
-msgid ""
-"The following Linux distributions provide community-supported packages for "
-"OpenStack:"
-msgstr ""
-
-#: ./doc/common/app_support.xml404(emphasis)
-msgid "Debian:"
-msgstr ""
-
-#: ./doc/common/app_support.xml407(link)
-msgid "http://wiki.debian.org/OpenStack"
-msgstr "http://wiki.debian.org/OpenStack"
-
-#: ./doc/common/app_support.xml410(emphasis)
-msgid "CentOS, Fedora, and Red Hat Enterprise Linux:"
-msgstr "CentOS, Fedora, et Red Hat Enterprise Linux:"
-
-#: ./doc/common/app_support.xml413(link)
-msgid "http://openstack.redhat.com/"
-msgstr "http://openstack.redhat.com/"
-
-#: ./doc/common/app_support.xml416(emphasis)
-msgid "openSUSE and SUSE Linux Enterprise Server:"
-msgstr ""
-
-#: ./doc/common/app_support.xml420(link)
-msgid "http://en.opensuse.org/Portal:OpenStack"
-msgstr "http://en.opensuse.org/Portal:OpenStack"
-
-#: ./doc/common/app_support.xml423(emphasis)
-msgid "Ubuntu:"
-msgstr "Ubuntu:"
-
-#: ./doc/common/app_support.xml426(link)
-msgid "https://wiki.ubuntu.com/ServerTeam/CloudArchive"
-msgstr "https://wiki.ubuntu.com/ServerTeam/CloudArchive"
-
-#: ./doc/common/section_cli_glance_manage_images.xml7(title)
-msgid "Manage images"
-msgstr "Gérez les images"
-
-#: ./doc/common/section_cli_glance_manage_images.xml8(para)
-msgid ""
-"The cloud operator assigns roles to users. Roles determine who can upload "
-"and manage images. The operator might restrict image upload and management "
-"to only cloud administrators or operators."
-msgstr "L'opérateur du cloud assigne des rôles aux utilisateurs. Les rôles déterminent qui peut télécharger et gérer des images. L'opérateur pourrait restreindre le téléchargement d'images et de gestion uniquement pour les administrateurs du cloud ou les opérateurs."
-
-#: ./doc/common/section_cli_glance_manage_images.xml12(para)
-msgid ""
-"You can upload images through the <placeholder-1/> client or the Image "
-"Service API. You can also use the <placeholder-2/> client to list images, "
-"set and delete image metadata, delete images, and take a snapshot of a "
-"running instance to create an image. After you upload an image, you cannot "
-"change it."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml16(para)
-msgid ""
-"For details about image creation, see the <link "
-"href=\"http://docs.openstack.org/image-guide/content/\"><citetitle>Virtual "
-"Machine Image Guide</citetitle></link>."
-msgstr "Pour plus de détails sur la création de l'image, voir le <link href=\"http://docs.openstack.org/image-guide/content/\"><citetitle>Virtual Machine Image Guide</citetitle></link>."
-
-#: ./doc/common/section_cli_glance_manage_images.xml21(title)
-msgid "List or get details for images (glance)"
-msgstr "Lister ou trouver les détails pour les images (glance)"
-
-#: ./doc/common/section_cli_glance_manage_images.xml22(para)
-msgid ""
-"To get a list of images and to then get further details about a single "
-"image, use <placeholder-1/> and <placeholder-2/>."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml74(para)
-msgid ""
-"When viewing a list of images, you can also use <placeholder-1/> to filter "
-"the list, as follows:"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml80(para)
-msgid ""
-"To store location metadata for images, which enables direct file access for "
-"a client, update the <filename>/etc/glance/glance.conf</filename> file with "
-"the following statements:"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml87(code)
-msgid "show_multiple_locations = True"
-msgstr "show_multiple_locations = True"
-
-#: ./doc/common/section_cli_glance_manage_images.xml90(para)
-msgid ""
-"<code>filesystem_store_metadata_file = "
-"<replaceable>filePath</replaceable></code>, where "
-"<replaceable>filePath</replaceable> points to a JSON file that defines the "
-"mount point for OpenStack images on your system and a unique ID. For "
-"example: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml102(para)
-msgid ""
-"After you restart the Image Service, you can use the following syntax to "
-"view the image's location information:"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml103(replaceable)
-msgid "imageID"
-msgstr "imageID"
-
-#: ./doc/common/section_cli_glance_manage_images.xml104(para)
-msgid ""
-"For example, using the image ID shown above, you would issue the command as "
-"follows:"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml109(title)
-msgid "Create or update an image (glance)"
-msgstr "Créer ou mettre à jour une image (glance)"
-
-#: ./doc/common/section_cli_glance_manage_images.xml110(para)
-msgid "To create an image, use <placeholder-1/>:"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml111(replaceable)
-#: ./doc/common/section_cli_glance_manage_images.xml114(replaceable)
-msgid "imageName"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml112(para)
-msgid "To update an image by name or ID, use <placeholder-1/>:"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml116(para)
-msgid ""
-"The following table lists the optional arguments that you can use with the "
-"<placeholder-1/> and <placeholder-2/> commands to modify image properties. "
-"For more information, refer to Image Service chapter in the <link "
-"href=\"http://docs.openstack.org/cli-"
-"reference/content/index.html\">OpenStack Command-Line Interface "
-"Reference</link>."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml126(parameter)
-msgid "--name NAME"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml129(para)
-msgid "The name of the image."
-msgstr "Le nom de l'image."
-
-#: ./doc/common/section_cli_glance_manage_images.xml134(parameter)
-msgid "--disk-format DISK_FORMAT"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml137(para)
-msgid ""
-"The disk format of the image. Acceptable formats are ami, ari, aki, vhd, "
-"vmdk, raw, qcow2, vdi, and iso."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml143(parameter)
-msgid "--container-format CONTAINER_FORMAT"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml146(para)
-msgid ""
-"The container format of the image. Acceptable formats are ami, ari, aki, "
-"bare, and ovf."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml152(parameter)
-msgid "--owner TENANT_ID"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml155(para)
-msgid "The tenant who should own the image."
-msgstr "Le locataire qui devrait posséder l'image."
-
-#: ./doc/common/section_cli_glance_manage_images.xml160(parameter)
-msgid "--size SIZE"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml163(para)
-msgid "The size of image data, in bytes."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml168(parameter)
-msgid "--min-disk DISK_GB"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml171(para)
-msgid "The minimum size of the disk needed to boot the image, in gigabytes."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml177(parameter)
-msgid "--min-ram DISK_RAM"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml180(para)
-msgid "The minimum amount of RAM needed to boot the image, in megabytes."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml185(parameter)
-msgid "--location IMAGE_URL"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml188(para)
-msgid ""
-"The URL where the data for this image resides. For example, if the image "
-"data is stored in swift, you could specify "
-"<literal>swift://account:key@example.com/container/obj</literal>."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml195(parameter)
-msgid "--file FILE"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml198(para)
-msgid ""
-"Local file that contains the disk image to be uploaded during the update. "
-"Alternatively, you can pass images to the client through stdin."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml204(parameter)
-msgid "--checksum CHECKSUM"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml207(para)
-msgid "Hash of image data to use for verification."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml212(parameter)
-msgid "--copy-from IMAGE_URL"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml215(para)
-msgid ""
-"Similar to <parameter>--location</parameter> in usage, but indicates that "
-"the image server should immediately copy the data and store it in its "
-"configured image store."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml222(parameter)
-msgid "--is-public [True|False]"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml225(para)
-msgid "Makes an image accessible for all the tenants."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml230(parameter)
-msgid "--is-protected [True|False]"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml233(para)
-msgid "Prevents an image from being deleted."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml238(parameter)
-msgid "--property KEY=VALUE"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml241(para)
-msgid ""
-"Arbitrary property to associate with image. This option can be used multiple"
-" times."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml247(parameter)
-msgid "--purge-props"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml250(para)
-msgid ""
-"Deletes all image properties that are not explicitly set in the update "
-"request. Otherwise, those properties not referenced are preserved."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml256(parameter)
-msgid "--human-readable"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml259(para)
-msgid "Prints the image size in a human-friendly format."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml263(para)
-msgid ""
-"The following example shows the command that you would use to upload a "
-"CentOS 6.3 image in qcow2 format and configure it for public access:"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml267(para)
-msgid ""
-"The following example shows how to update an existing image with a "
-"properties that describe the disk bus, the CD-ROM bus, and the VIF model:"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml274(para)
-msgid ""
-"Currently the libvirt virtualization tool determines the disk, CD-ROM, and "
-"VIF device models based on the configured hypervisor type "
-"(<literal>libvirt_type</literal> in "
-"<filename>/etc/nova/nova.conf</filename>). For the sake of optimal "
-"performance, libvirt defaults to using virtio for both disk and VIF (NIC) "
-"models. The disadvantage of this approach is that it is not possible to run "
-"operating systems that lack virtio drivers, for example, BSD, Solaris, and "
-"older versions of Linux and Windows."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml280(para)
-msgid ""
-"If you specify a disk or CD-ROM bus model that is not supported, see <xref "
-"linkend=\"bus_models\"/>. If you specify a VIF model that is not supported, "
-"the instance fails to launch. See <xref linkend=\"vif_models\"/>."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml284(para)
-msgid ""
-"The valid model values depend on the <literal>libvirt_type</literal> "
-"setting, as shown in the following tables."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml287(caption)
-msgid "Disk and CD-ROM bus model values"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml292(th)
-#: ./doc/common/section_cli_glance_manage_images.xml336(th)
-msgid "libvirt_type setting"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml293(th)
-#: ./doc/common/section_cli_glance_manage_images.xml337(th)
-msgid "Supported model values"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml298(td)
-#: ./doc/common/section_cli_glance_manage_images.xml342(td)
-msgid "qemu or kvm"
-msgstr "qemu ou kvm"
-
-#: ./doc/common/section_cli_glance_manage_images.xml303(para)
-#: ./doc/common/section_cli_glance_manage_images.xml320(para)
-msgid "ide"
-msgstr "ide"
-
-#: ./doc/common/section_cli_glance_manage_images.xml306(para)
-msgid "scsi"
-msgstr "scsi"
-
-#: ./doc/common/section_cli_glance_manage_images.xml309(para)
-#: ./doc/common/section_cli_glance_manage_images.xml359(para)
-msgid "virtio"
-msgstr "virtio"
-
-#: ./doc/common/section_cli_glance_manage_images.xml316(td)
-#: ./doc/common/section_cli_glance_manage_images.xml323(para)
-#: ./doc/common/section_cli_glance_manage_images.xml366(td)
-msgid "xen"
-msgstr "xen"
-
-#: ./doc/common/section_cli_glance_manage_images.xml331(caption)
-msgid "VIF model values"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml347(para)
-#: ./doc/common/section_cli_glance_manage_images.xml370(para)
-msgid "e1000"
-msgstr "e1000"
-
-#: ./doc/common/section_cli_glance_manage_images.xml350(para)
-#: ./doc/common/section_cli_glance_manage_images.xml376(para)
-msgid "ne2k_pci"
-msgstr "ne2k_pci"
-
-#: ./doc/common/section_cli_glance_manage_images.xml353(para)
-#: ./doc/common/section_cli_glance_manage_images.xml379(para)
-msgid "pcnet"
-msgstr "pcnet"
-
-#: ./doc/common/section_cli_glance_manage_images.xml356(para)
-#: ./doc/common/section_cli_glance_manage_images.xml382(para)
-msgid "rtl8139"
-msgstr "rtl8139"
-
-#: ./doc/common/section_cli_glance_manage_images.xml373(para)
-msgid "netfront"
-msgstr "netfront"
-
-#: ./doc/common/section_cli_glance_manage_images.xml388(td)
-msgid "vmware"
-msgstr "vmware"
-
-#: ./doc/common/section_cli_glance_manage_images.xml393(para)
-msgid "VirtualE1000"
-msgstr "VirtualE1000"
-
-#: ./doc/common/section_cli_glance_manage_images.xml396(para)
-msgid "VirtualPCNet32"
-msgstr "VirtualPCNet32"
-
-#: ./doc/common/section_cli_glance_manage_images.xml399(para)
-msgid "VirtualVmxnet"
-msgstr "VirtualVmxnet"
-
-#: ./doc/common/section_cli_glance_manage_images.xml410(title)
-#: ./doc/common/section_cli_nova_images.xml125(title)
-msgid "Troubleshoot image creation"
-msgstr "Résoudre les problèmes de la création des images"
-
-#: ./doc/common/section_cli_glance_manage_images.xml411(para)
-msgid ""
-"If you encounter problems in creating an image in Image Service or Compute, "
-"the following information may help you troubleshoot the creation process."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml415(para)
-msgid ""
-"Ensure that the version of qemu you are using is version 0.14 or later. "
-"Earlier versions of qemu result in an <literal>unknown option -s</literal> "
-"error message in the <filename>nova-compute.log</filename> file."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml420(para)
-#: ./doc/common/section_cli_nova_images.xml140(para)
-msgid ""
-"Examine the <filename>/var/log/nova-api.log</filename> and "
-"<filename>/var/log/nova-compute.log</filename> log files for error messages."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_manage_images.xml6(title)
-msgid "Create an image (nova)"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_manage_images.xml7(para)
-msgid ""
-"You can use the <placeholder-1/> client to take a snapshot of a running "
-"instance to create an image."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_manage_images.xml9(para)
-msgid ""
-"To minimize the potential for data loss and ensure that you create an "
-"accurate image, you should shut down the instance before you take a "
-"snapshot."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_manage_images.xml12(para)
-msgid ""
-"You cannot create a snapshot from an instance that has an attached volume. "
-"Detach the volume, create the image, and remount the volume."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_manage_images.xml17(para)
-#: ./doc/common/section_cli_nova_images.xml18(para)
-msgid "Write any buffered data to disk."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_manage_images.xml18(para)
-msgid ""
-"For more information, see <link href=\"http://docs.openstack.org/trunk"
-"/openstack-ops/content/snapshots.html\">Taking Snapshots</link> in the "
-"<citetitle>OpenStack Operations Guide</citetitle>."
-msgstr "Pour plus d'informations, voir  see <link href=\"http://docs.openstack.org/trunk/openstack-ops/content/snapshots.html\">Taking Snapshots</link> dans <citetitle>OpenStack Operations Guide</citetitle>."
-
-#: ./doc/common/section_cli_nova_manage_images.xml24(para)
-msgid "List instances to get the server name:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_manage_images.xml31(para)
-msgid ""
-"In this example, the server is named <literal>myCirrosServer</literal>."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_manage_images.xml33(para)
-msgid ""
-"Use this server to create a snapshot: <placeholder-1/>The command creates a "
-"qemu snapshot and automatically uploads the image to your repository. Only "
-"the tenant that creates the image has access to it."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_manage_images.xml40(para)
-#: ./doc/common/section_cli_nova_images.xml43(para)
-msgid "Get details for your image to check its status:"
-msgstr "Trouver les détails de votre image pour vérifier son état:"
-
-#: ./doc/common/section_cli_nova_manage_images.xml75(para)
-#: ./doc/common/section_cli_nova_images.xml79(para)
-msgid ""
-"The image status changes from <literal>SAVING</literal> to "
-"<literal>ACTIVE</literal>. Only the tenant who creates the image has access "
-"to it."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_manage_images.xml81(para)
-msgid ""
-"To launch an instance from your image, include the image ID and flavor ID, "
-"as in the following example:"
-msgstr ""
-
 #. When image changes, this message will be marked fuzzy or untranslated for
 #. you.
 #. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_compute-configure-vnc.xml63(None)
+#: ./doc/common/section_getstart_dashboard.xml14(None)
 msgid ""
-"@@image: '../common/figures/novnc/SCH_5009_V00_NUAC-VNC_OpenStack.png'; "
-"md5=182dc38019a220c851e1c94aa50f4565"
-msgstr "@@image: '../common/figures/novnc/SCH_5009_V00_NUAC-VNC_OpenStack.png'; md5=182dc38019a220c851e1c94aa50f4565"
+"@@image: 'figures/horizon-screenshot.jpg'; "
+"md5=9471047adf0d93713be7f54b9db2b53c"
+msgstr "@@image: 'figures/horizon-screenshot.jpg'; md5=9471047adf0d93713be7f54b9db2b53c"
 
-#: ./doc/common/section_compute-configure-vnc.xml6(title)
-msgid "VNC console proxy"
+#: ./doc/common/section_getstart_dashboard.xml5(title)
+msgid "OpenStack dashboard"
+msgstr "Tableau de bord OpenStack"
+
+#: ./doc/common/section_getstart_dashboard.xml6(para)
+msgid ""
+"The OpenStack dashboard is a modular <link "
+"href=\"https://www.djangoproject.com/\">Django web application</link> that "
+"provides a graphical interface to OpenStack services."
 msgstr ""
 
-#: ./doc/common/section_compute-configure-vnc.xml7(para)
+#: ./doc/common/section_getstart_dashboard.xml18(para)
 msgid ""
-"The VNC proxy is an OpenStack component that enables compute service users "
-"to access their instances through VNC clients."
-msgstr "Le proxy VNC est un composant OpenStack qui permet aux utilisateurs du service Compute d’accéder à leurs instances via des clients VNC."
+"The dashboard is usually deployed through <link "
+"href=\"http://code.google.com/p/modwsgi/\">mod_wsgi</link> in Apache. You "
+"can modify the dashboard code to make it suitable for different sites."
+msgstr "Le tableau de bord est généralement déployé par <link href=\"http://code.google.com/p/modwsgi/\">mod_wsgi</link> dans Apache. Vous pouvez modifier le code du tableau de bord pour qu'il convienne des autres sites web. "
 
-#: ./doc/common/section_compute-configure-vnc.xml10(para)
-msgid "The VNC console connection works as follows:"
-msgstr "La connexion à la console VNC fonctionne comme suit :"
-
-#: ./doc/common/section_compute-configure-vnc.xml13(para)
+#: ./doc/common/section_getstart_dashboard.xml22(para)
 msgid ""
-"A user connects to the API and gets an <literal>access_url</literal> such "
-"as, <literal>http://<replaceable>ip:port</replaceable>/?token=xyz</literal>."
-msgstr "Un utilisateur se connecte à l’API et obtient une <literal>access_url</literal> telle que <literal>http://<replaceable>ip:port</replaceable>/?token=xyz</literal>."
+"From a network architecture point of view, this service must be accessible "
+"to customers and the public API for each OpenStack service. To use the "
+"administrator functionality for other services, it must also connect to "
+"Admin API endpoints, which should not be accessible by customers."
+msgstr "Du point de vue de l'architecture réseau, ce service doit être accessible aux clients et à l'API publique pour chaque service d’OpenStack). Pour utiliser la fonctionnalité d'administrateur pour d'autres services, il faut aussi se connecter aux terminaisons de l'API d'administration, qui ne doivent pas être accessibles par les clients."
 
-#: ./doc/common/section_compute-configure-vnc.xml19(para)
-msgid "The user pastes the URL in a browser or uses it as a client parameter."
-msgstr "L'utilisateur colle l'URL dans le navigateur ou il l'utilise comme paramètre client."
+#: ./doc/common/section_cli_nova_reboot.xml5(title)
+msgid "Reboot an instance"
+msgstr "Redémarrer une instance"
 
-#: ./doc/common/section_compute-configure-vnc.xml23(para)
-msgid "The browser or client connects to the proxy."
-msgstr "Le navigateur ou le client se connecte au proxy."
-
-#: ./doc/common/section_compute-configure-vnc.xml26(para)
+#: ./doc/common/section_cli_nova_reboot.xml6(para)
 msgid ""
-"The proxy talks to <systemitem class=\"service\">nova-"
-"consoleauth</systemitem> to authorize the token for the user, and maps the "
-"token to the <emphasis>private</emphasis> host and port of the VNC server "
-"for an instance."
+"You can soft or hard reboot a running instance. A soft reboot attempts a "
+"graceful shut down and restart of the instance. A hard reboot power cycles "
+"the instance."
 msgstr ""
 
-#: ./doc/common/section_compute-configure-vnc.xml31(para)
-msgid ""
-"The compute host specifies the address that the proxy should use to connect "
-"through the <filename>nova.conf</filename> file option, "
-"<option>vncserver_proxyclient_address</option>. In this way, the VNC proxy "
-"works as a bridge between the public network and private host network."
-msgstr "L’hôte Compute spécifie l’adresse que le proxy doit utiliser pour se connecter dans l’option <option>vncserver_proxyclient_address</option> du fichier <filename>nova.conf</filename>. Ainsi, le proxy VNC fonctionne comme un pont entre le réseau public et le réseau hôte privé."
-
-#: ./doc/common/section_compute-configure-vnc.xml39(para)
-msgid ""
-"The proxy initiates the connection to VNC server and continues to proxy "
-"until the session ends."
+#: ./doc/common/section_cli_nova_reboot.xml9(para)
+msgid "By default, when you reboot a server, it is a soft reboot."
 msgstr ""
 
-#: ./doc/common/section_compute-configure-vnc.xml43(para)
-msgid ""
-"The proxy also tunnels the VNC protocol over WebSockets so that the "
-"<systemitem>noVNC</systemitem> client can talk to VNC servers. In general, "
-"the VNC proxy:"
+#: ./doc/common/section_cli_nova_reboot.xml10(replaceable)
+#: ./doc/common/section_cli_nova_reboot.xml12(replaceable)
+msgid "SERVER"
 msgstr ""
 
-#: ./doc/common/section_compute-configure-vnc.xml48(para)
+#: ./doc/common/section_cli_nova_reboot.xml11(para)
 msgid ""
-"Bridges between the public network where the clients live and the private "
-"network where VNC servers live."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml52(para)
-msgid "Mediates token authentication."
-msgstr "fournit les jetons d’authentification."
-
-#: ./doc/common/section_compute-configure-vnc.xml55(para)
-msgid ""
-"Transparently deals with hypervisor-specific connection details to provide a"
-" uniform client experience."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml58(title)
-msgid "noVNC process"
-msgstr "Processus noVNC"
-
-#: ./doc/common/section_compute-configure-vnc.xml71(title)
-msgid "About nova-consoleauth"
-msgstr "A propos de nova-consoleauth"
-
-#: ./doc/common/section_compute-configure-vnc.xml73(para)
-msgid ""
-"Both client proxies leverage a shared service to manage token authentication"
-" called <systemitem class=\"service\">nova-consoleauth</systemitem>. This "
-"service must be running for either proxy to work. Many proxies of either "
-"type can be run against a single <systemitem class=\"service\">nova-"
-"consoleauth</systemitem> service in a cluster configuration."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml80(para)
-msgid ""
-"Do not confuse the <systemitem class=\"service\">nova-"
-"consoleauth</systemitem> shared service with <literal>nova-"
-"console</literal>, which is a XenAPI-specific service that most recent VNC "
-"proxy architectures do not use."
-msgstr "Il ne faut pas confondre le service partagé  <systemitem class=\"service\">nova-consoleauth</systemitem> avec <literal>nova-console</literal>, qui est un service spécifique à XenAPI que la plupart des architectures proxy récentes n’utilisent pas."
-
-#: ./doc/common/section_compute-configure-vnc.xml87(title)
-msgid "Typical deployment"
-msgstr "Déploiement typique"
-
-#: ./doc/common/section_compute-configure-vnc.xml88(para)
-msgid "A typical deployment has the following components:"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml91(para)
-msgid ""
-"A <systemitem class=\"service\">nova-consoleauth</systemitem> process. "
-"Typically runs on the controller host."
-msgstr "Un processus <systemitem class=\"service\">nova-consoleauth</systemitem>. Tourne généralement sur le contrôleur hôte."
-
-#: ./doc/common/section_compute-configure-vnc.xml96(para)
-msgid ""
-"One or more <systemitem class=\"service\">nova-novncproxy</systemitem> "
-"services. Supports browser-based noVNC clients. For simple deployments, this"
-" service typically runs on the same machine as <systemitem class=\"service"
-"\">nova-api</systemitem> because it operates as a proxy between the public "
-"network and the private compute host network."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml105(para)
-msgid ""
-"One or more <literal>nova-xvpvncproxy</literal> services. Supports the "
-"special Java client discussed here. For simple deployments, this service "
-"typically runs on the same machine as <systemitem class=\"service\">nova-"
-"api</systemitem> because it acts as a proxy between the public network and "
-"the private compute host network."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml114(para)
-msgid ""
-"One or more compute hosts. These compute hosts must have correctly "
-"configured options, as follows."
-msgstr "Un ou plusieurs hôtes Compute. Ces hôtes Compute doivent avoir leurs options correctement configurées, comme suit :"
-
-#: ./doc/common/section_compute-configure-vnc.xml120(title)
-msgid "VNC configuration options"
-msgstr "Un ou plusieurs hôtes Compute. Ces hôtes Compute doivent avoir leurs options correctement configurées, comme suit :"
-
-#: ./doc/common/section_compute-configure-vnc.xml121(para)
-msgid "To customize the VNC console, use the following configuration options:"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml124(para)
-msgid ""
-"To support <link href=\"http://docs.openstack.org/trunk/config-"
-"reference/content/configuring-openstack-compute-basics.html"
-"#section_configuring-compute-migrations\">live migration</link>, you cannot "
-"specify a specific IP address for <literal>vncserver_listen</literal>, "
-"because that IP address does not exist on the destination host."
-msgstr "Pour supporter la <link href=\"http://docs.openstack.org/trunk/config-reference/content/configuring-openstack-compute-basics.html#section_configuring-compute-migrations\">live migration</link>, vous ne pouvez pas spécifier d’adresse IP en particulier pour <literal>vncserver_listen</literal>, car cette adresse IP n’existe pas sur l’hôte destinataire."
-
-#: ./doc/common/section_compute-configure-vnc.xml134(para)
-msgid ""
-"The <literal>vncserver_proxyclient_address</literal> defaults to "
-"<literal>127.0.0.1</literal>, which is the address of the compute host that "
-"Compute instructs proxies to use when connecting to instance servers."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml139(para)
-msgid "For all-in-one XenServer domU deployments, set this to 169.254.0.1."
-msgstr "Pour des déploiements domU XenServer tout-en-un, définissez-la sur 169.254.0.1."
-
-#: ./doc/common/section_compute-configure-vnc.xml140(para)
-msgid ""
-"For multi-host XenServer domU deployments, set to a dom0 management IP on "
-"the same network as the proxies."
-msgstr "Pour des déploiements domU XenServer multi-hôtes, définissez-la sur une IP de gestion dom0 sur le même réseau que les proxies."
-
-#: ./doc/common/section_compute-configure-vnc.xml142(para)
-msgid ""
-"For multi-host libvirt deployments, set to a host management IP on the same "
-"network as the proxies."
-msgstr "Pour des déploiements libvirt multi-hôtes, définissez-la sur une IP de gestion d’hôtes sur le même réseau que les proxies."
-
-#: ./doc/common/section_compute-configure-vnc.xml150(title)
-msgid "nova-novncproxy (noVNC)"
-msgstr "nova-novncproxy  (noVNC)"
-
-#: ./doc/common/section_compute-configure-vnc.xml152(para)
-msgid ""
-"You must install the <package>noVNC</package> package, which contains the "
-"<systemitem class=\"service\">nova-novncproxy</systemitem> service. As root,"
-" run the following command:"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml156(para)
-msgid "The service starts automatically on installation."
-msgstr "Le service démarre automatiquement lors de l’installation"
-
-#: ./doc/common/section_compute-configure-vnc.xml157(para)
-msgid "To restart the service, run:"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml159(para)
-msgid ""
-"The configuration option parameter should point to your "
-"<filename>nova.conf</filename> file, which includes the message queue server"
-" address and credentials."
-msgstr "Le paramètre d’option de configuration doit pointer vers votre fichier <filename>nova.conf</filename>, qui contient les informations d’identification et l’adresse du serveur de file d’attente de messagerie."
-
-#: ./doc/common/section_compute-configure-vnc.xml162(para)
-msgid ""
-"By default, <systemitem class=\"service\">nova-novncproxy</systemitem> binds"
-" on <literal>0.0.0.0:6080</literal>."
-msgstr "Par défaut, <systemitem class=\"service\">nova-novncproxy</systemitem> s’attache à <literal>0.0.0.0:6080</literal>."
-
-#: ./doc/common/section_compute-configure-vnc.xml165(para)
-msgid ""
-"To connect the service to your Compute deployment, add the following "
-"configuration options to your <filename>nova.conf</filename> file:"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml169(para)
-msgid "<literal>vncserver_listen</literal>=<replaceable>0.0.0.0</replaceable>"
-msgstr "<literal>vncserver_listen</literal>=<replaceable>0.0.0.0</replaceable>"
-
-#: ./doc/common/section_compute-configure-vnc.xml172(para)
-msgid ""
-"Specifies the address on which the VNC service should bind. Make sure it is "
-"assigned one of the compute node interfaces. This address is the one used by"
-" your domain file."
-msgstr "Spécifie l’adresse à laquelle le service VNC doit s’attacher. Assurez-vous que lui soit assignée une des interfaces de nœud Compute. Cette adresse est celle utilisée par votre fichier de domaine."
-
-#: ./doc/common/section_compute-configure-vnc.xml178(para)
-msgid ""
-"To use live migration, use the <replaceable>0.0.0.0</replaceable> address."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml183(para)
-msgid ""
-"<literal>vncserver_proxyclient_address</literal>=<replaceable>127.0.0.1</replaceable>"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml186(para)
-msgid ""
-"The address of the compute host that Compute instructs proxies to use when "
-"connecting to instance <literal>vncservers</literal>."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml193(title)
-msgid "Frequently asked questions about VNC access to virtual machines"
-msgstr "Foire Aux Questions à propos de l’accès VNC aux machines virtuelles"
-
-#: ./doc/common/section_compute-configure-vnc.xml199(literal)
-msgid "nova-xvpvncproxy"
-msgstr "nova-xvpvncproxy"
-
-#: ./doc/common/section_compute-configure-vnc.xml200(systemitem)
-msgid "nova-novncproxy"
-msgstr "nova-novncproxy"
-
-#: ./doc/common/section_compute-configure-vnc.xml198(emphasis)
-msgid ""
-"Q: What is the difference between <placeholder-1/> and <placeholder-2/>?"
-msgstr "Q: Quelle est la différence entre <placeholder-1/> et <placeholder-2/>?"
-
-#: ./doc/common/section_compute-configure-vnc.xml202(para)
-msgid ""
-"A: <literal>nova-xvpvncproxy</literal>, which ships with OpenStack Compute, "
-"is a proxy that supports a simple Java client. <systemitem class=\"service"
-"\">nova-novncproxy</systemitem> uses noVNC to provide VNC support through a "
-"web browser."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml208(emphasis)
-msgid ""
-"Q: I want VNC support in the OpenStack dashboard. What services do I need?"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml210(para)
-msgid ""
-"A: You need <systemitem class=\"service\">nova-novncproxy</systemitem>, "
-"<systemitem class=\"service\">nova-consoleauth</systemitem>, and correctly "
-"configured compute hosts."
-msgstr "R : Vous avez besoin de <systemitem class=\"service\">nova-novncproxy</systemitem>, <systemitem class=\"service\">nova-consoleauth</systemitem>, et d’hôtes Compute correctement configurés."
-
-#: ./doc/common/section_compute-configure-vnc.xml216(emphasis)
-msgid ""
-"Q: When I use <placeholder-1/> or click on the VNC tab of the OpenStack "
-"dashboard, it hangs. Why?"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml218(para)
-msgid ""
-"A: Make sure you are running <systemitem class=\"service\">nova-"
-"consoleauth</systemitem> (in addition to <systemitem class=\"service\">nova-"
-"novncproxy</systemitem>). The proxies rely on <systemitem class=\"service"
-"\">nova-consoleauth</systemitem> to validate tokens, and waits for a reply "
-"from them until a timeout is reached."
-msgstr "R : Assurez-vous d’exécuter <systemitem class=\"service\">nova-consoleauth</systemitem> (en plus de <systemitem class=\"service\">nova-novncproxy</systemitem>). Les proxies s’appuient sur <systemitem class=\"service\">nova-consoleauth</systemitem> pour valider les jetons, et attendent une réponse de leur part jusqu’à ce qu’un timeout soit atteint."
-
-#: ./doc/common/section_compute-configure-vnc.xml227(emphasis)
-msgid ""
-"Q: My VNC proxy worked fine during my all-in-one test, but now it doesn't "
-"work on multi host. Why?"
-msgstr "Q: Mon proxy VNC marchait bien lors de mon test tout-en-un, mais maintenant ça ne marche pas en multi-hôtes. Pourquoi ?"
-
-#: ./doc/common/section_compute-configure-vnc.xml230(para)
-msgid ""
-"A: The default options work for an all-in-one install, but changes must be "
-"made on your compute hosts once you start to build a cluster. As an example,"
-" suppose you have two servers:"
-msgstr "R : Les options par défaut marchent pour une installation tout-en-un, mais des changements doivent être faits sur vos hôtes Compute une fois que vous commencez à bâtir un cluster. Par exemple, supposons que vous ayez deux serveurs :"
-
-#: ./doc/common/section_compute-configure-vnc.xml236(para)
-msgid ""
-"Your <systemitem class=\"service\">nova-compute</systemitem> configuration "
-"file must set the following values:"
-msgstr "Votre fichier de configuration <systemitem class=\"service\">nova-compute</systemitem> doit être réglé avec les valeurs suivantes :"
-
-#: ./doc/common/section_compute-configure-vnc.xml248(para)
-msgid ""
-"<literal>novncproxy_base_url</literal> and "
-"<literal>xvpvncproxy_base_url</literal> use a public IP; this is the URL "
-"that is ultimately returned to clients, which generally do not have access "
-"to your private network. Your PROXYSERVER must be able to reach "
-"<literal>vncserver_proxyclient_address</literal>, because that is the "
-"address over which the VNC connection is proxied."
-msgstr "<literal>novncproxy_base_url</literal> et <literal>xvpvncproxy_base_url</literal> utilisent une IP publique ; il s’agit de l’URL qui est in fine renvoyée aux clients, qui généralement n’ont pas accès à votre réseau privé. Votre SERVEUR PROXY doit être capable d’atteindre <literal>vncserver_proxyclient_address</literal>, car c’est l’adresse par laquelle la connexion VNC passe."
-
-#: ./doc/common/section_compute-configure-vnc.xml260(emphasis)
-msgid "Q: My noVNC does not work with recent versions of web browsers. Why?"
-msgstr "Q: Mon noVNC ne marche pas avec les versions récentes des navigateurs web. Pourquoi ?"
-
-#: ./doc/common/section_compute-configure-vnc.xml263(para)
-msgid ""
-"A: Make sure you have installed <literal>python-numpy</literal>, which is "
-"required to support a newer version of the WebSocket protocol (HyBi-07+)."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml270(emphasis)
-msgid ""
-"Q: How do I adjust the dimensions of the VNC window image in the OpenStack "
-"dashboard?"
-msgstr "Q: Comment puis-je ajuster les dimensions de l’image de la fenêtre VNC dans le tableau de bord OpenStack ?"
-
-#: ./doc/common/section_compute-configure-vnc.xml273(para)
-msgid ""
-"A: These values are hard-coded in a Django HTML template. To alter them, "
-"edit the <filename>_detail_vnc.html</filename> template file. The location "
-"of this file varies based on Linux distribution. On Ubuntu 12.04, the file "
-"is at "
-"<filename>/usr/share/pyshared/horizon/dashboards/nova/instances/templates/instances/_detail_vnc.html</filename>."
-msgstr "R : Ces valeurs sont codées en dur dans le modèle HTML Django. Pour les modifier, éditez le fichier modèle  <filename>_detail_vnc.html</filename>. L’emplacement de ce fichier varie selon la distribution Linux. Sur Ubuntu 12.04, le fichier se trouve dans <filename>/usr/share/pyshared/horizon/ dashboards/nova/instances/templates/instances/_detail_vnc.html</filename>."
-
-#: ./doc/common/section_compute-configure-vnc.xml279(para)
-msgid ""
-"Modify the <option>width</option> and <option>height</option> options, as "
-"follows:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml6(title)
-msgid "Change the size of your server"
-msgstr "Changez la taille de votre serveur"
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml7(para)
-msgid "You change the size of a server by changing its flavor."
-msgstr "Vous changez la taille d'un serveur en changeant son type d'instance."
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml10(para)
-msgid ""
-"Show information about your server, including its size, which is shown as "
-"the value of the flavor property."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml43(para)
-msgid "The size (flavor) of the server is <literal>m1.small (2)</literal>."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml46(para)
-msgid "List the available flavors with the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml59(para)
-msgid ""
-"To resize the server, pass the server ID or name and the new flavor to the "
-"<placeholder-1/> command. Include the <literal>--poll</literal> parameter to"
-" report the resize progress."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml67(para)
-msgid "Show the status for your server:"
-msgstr "Montrer l'état de votre serveur:"
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml74(para)
-msgid "When the resize completes, the status becomes VERIFY_RESIZE."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml77(para)
-msgid "Confirm the resize:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml79(para)
-#: ./doc/common/section_cli_nova_resizerebuild.xml85(para)
-msgid "The server status becomes ACTIVE."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml82(para)
-msgid ""
-"If the resize fails or does not work as expected, you can revert the resize:"
+"To perform a hard reboot, pass the <parameter>--hard</parameter> parameter, "
+"as follows:"
 msgstr ""
 
 #: ./doc/common/ch_cli_nova_commands.xml11(title)
@@ -1302,38 +101,38 @@ msgid ""
 msgstr ""
 
 #: ./doc/common/ch_cli_nova_commands.xml16(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml16(para)
 #: ./doc/common/ch_cli_neutron_commands.xml16(para)
-#: ./doc/common/ch_cli_keystone_commands.xml16(para)
-#: ./doc/common/ch_cli_swift_commands.xml16(para)
-#: ./doc/common/ch_cli_cinder_commands.xml16(para)
-#: ./doc/common/ch_cli_glance_commands.xml16(para)
 #: ./doc/common/ch_cli_heat_commands.xml16(para)
+#: ./doc/common/ch_cli_swift_commands.xml16(para)
+#: ./doc/common/ch_cli_glance_commands.xml16(para)
+#: ./doc/common/ch_cli_keystone_commands.xml16(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml16(para)
+#: ./doc/common/ch_cli_cinder_commands.xml16(para)
 #: ./doc/common/ch_cli_trove_commands.xml16(para)
 msgid "For help on a specific <placeholder-1/> command, enter:"
 msgstr ""
 
 #: ./doc/common/ch_cli_nova_commands.xml19(option)
-#: ./doc/common/ch_cli_ceilometer_commands.xml19(option)
 #: ./doc/common/ch_cli_neutron_commands.xml19(option)
-#: ./doc/common/ch_cli_keystone_commands.xml19(option)
-#: ./doc/common/ch_cli_swift_commands.xml19(option)
-#: ./doc/common/ch_cli_cinder_commands.xml19(option)
-#: ./doc/common/ch_cli_glance_commands.xml19(option)
 #: ./doc/common/ch_cli_heat_commands.xml19(option)
+#: ./doc/common/ch_cli_swift_commands.xml19(option)
+#: ./doc/common/ch_cli_glance_commands.xml19(option)
+#: ./doc/common/ch_cli_keystone_commands.xml19(option)
+#: ./doc/common/ch_cli_ceilometer_commands.xml19(option)
+#: ./doc/common/ch_cli_cinder_commands.xml19(option)
 #: ./doc/common/ch_cli_trove_commands.xml19(option)
 msgid "help"
 msgstr "aide"
 
 #: ./doc/common/ch_cli_nova_commands.xml19(replaceable)
-#: ./doc/common/ch_cli_ceilometer_commands.xml19(replaceable)
 #: ./doc/common/ch_cli_neutron_commands.xml19(replaceable)
-#: ./doc/common/ch_cli_keystone_commands.xml19(replaceable)
+#: ./doc/common/ch_cli_heat_commands.xml19(replaceable)
 #: ./doc/common/ch_cli_swift_commands.xml19(replaceable)
 #: ./doc/common/section_cli_keystone_example_usage.xml12(replaceable)
-#: ./doc/common/ch_cli_cinder_commands.xml19(replaceable)
 #: ./doc/common/ch_cli_glance_commands.xml19(replaceable)
-#: ./doc/common/ch_cli_heat_commands.xml19(replaceable)
+#: ./doc/common/ch_cli_keystone_commands.xml19(replaceable)
+#: ./doc/common/ch_cli_ceilometer_commands.xml19(replaceable)
+#: ./doc/common/ch_cli_cinder_commands.xml19(replaceable)
 #: ./doc/common/ch_cli_trove_commands.xml19(replaceable)
 msgid "COMMAND"
 msgstr "COMMAND"
@@ -1343,12 +142,12 @@ msgid "nova usage"
 msgstr ""
 
 #: ./doc/common/ch_cli_nova_commands.xml37(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml38(title)
-#: ./doc/common/ch_cli_keystone_commands.xml37(title)
-#: ./doc/common/ch_cli_swift_commands.xml37(title)
-#: ./doc/common/ch_cli_cinder_commands.xml35(title)
-#: ./doc/common/ch_cli_glance_commands.xml39(title)
 #: ./doc/common/ch_cli_heat_commands.xml35(title)
+#: ./doc/common/ch_cli_swift_commands.xml37(title)
+#: ./doc/common/ch_cli_glance_commands.xml39(title)
+#: ./doc/common/ch_cli_keystone_commands.xml37(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml38(title)
+#: ./doc/common/ch_cli_cinder_commands.xml35(title)
 #: ./doc/common/ch_cli_trove_commands.xml35(title)
 msgid "Subcommands"
 msgstr ""
@@ -2189,11 +988,11 @@ msgid ""
 msgstr ""
 
 #: ./doc/common/ch_cli_nova_commands.xml1326(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml261(para)
-#: ./doc/common/ch_cli_keystone_commands.xml332(para)
-#: ./doc/common/ch_cli_cinder_commands.xml575(para)
-#: ./doc/common/ch_cli_glance_commands.xml203(para)
 #: ./doc/common/ch_cli_heat_commands.xml311(para)
+#: ./doc/common/ch_cli_glance_commands.xml203(para)
+#: ./doc/common/ch_cli_keystone_commands.xml332(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml261(para)
+#: ./doc/common/ch_cli_cinder_commands.xml575(para)
 msgid "Display help about this program or one of its subcommands."
 msgstr ""
 
@@ -2314,11 +1113,11 @@ msgid "nova optional arguments"
 msgstr ""
 
 #: ./doc/common/ch_cli_nova_commands.xml1519(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml275(para)
 #: ./doc/common/ch_cli_neutron_commands.xml38(para)
 #: ./doc/common/ch_cli_swift_commands.xml115(para)
-#: ./doc/common/ch_cli_cinder_commands.xml597(para)
 #: ./doc/common/ch_cli_glance_commands.xml217(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml275(para)
+#: ./doc/common/ch_cli_cinder_commands.xml597(para)
 #: ./doc/common/ch_cli_trove_commands.xml446(para)
 msgid "show program's version number and exit"
 msgstr ""
@@ -2348,49 +1147,49 @@ msgid "Defaults to <code>env[OS_AUTH_TOKEN]</code>"
 msgstr ""
 
 #: ./doc/common/ch_cli_nova_commands.xml1568(para)
+#: ./doc/common/ch_cli_heat_commands.xml399(para)
 #: ./doc/common/ch_cli_ceilometer_commands.xml357(para)
 #: ./doc/common/ch_cli_cinder_commands.xml613(para)
-#: ./doc/common/ch_cli_heat_commands.xml399(para)
 #: ./doc/common/ch_cli_trove_commands.xml462(para)
 msgid "Defaults to <code>env[OS_USERNAME]</code>."
 msgstr ""
 
 #: ./doc/common/ch_cli_nova_commands.xml1576(para)
+#: ./doc/common/ch_cli_heat_commands.xml407(para)
 #: ./doc/common/ch_cli_ceilometer_commands.xml365(para)
 #: ./doc/common/ch_cli_cinder_commands.xml621(para)
-#: ./doc/common/ch_cli_heat_commands.xml407(para)
 #: ./doc/common/ch_cli_trove_commands.xml470(para)
 msgid "Defaults to <code>env[OS_PASSWORD]</code>."
 msgstr ""
 
 #: ./doc/common/ch_cli_nova_commands.xml1584(para)
+#: ./doc/common/ch_cli_heat_commands.xml423(para)
 #: ./doc/common/ch_cli_ceilometer_commands.xml381(para)
 #: ./doc/common/ch_cli_cinder_commands.xml629(para)
-#: ./doc/common/ch_cli_heat_commands.xml423(para)
 #: ./doc/common/ch_cli_trove_commands.xml478(para)
 msgid "Defaults to <code>env[OS_TENANT_NAME]</code>."
 msgstr ""
 
 #: ./doc/common/ch_cli_nova_commands.xml1592(para)
+#: ./doc/common/ch_cli_heat_commands.xml415(para)
 #: ./doc/common/ch_cli_ceilometer_commands.xml373(para)
 #: ./doc/common/ch_cli_cinder_commands.xml637(para)
-#: ./doc/common/ch_cli_heat_commands.xml415(para)
 #: ./doc/common/ch_cli_trove_commands.xml486(para)
 msgid "Defaults to <code>env[OS_TENANT_ID]</code>."
 msgstr ""
 
 #: ./doc/common/ch_cli_nova_commands.xml1600(para)
+#: ./doc/common/ch_cli_heat_commands.xml431(para)
 #: ./doc/common/ch_cli_ceilometer_commands.xml389(para)
 #: ./doc/common/ch_cli_cinder_commands.xml645(para)
-#: ./doc/common/ch_cli_heat_commands.xml431(para)
 #: ./doc/common/ch_cli_trove_commands.xml494(para)
 msgid "Defaults to <code>env[OS_AUTH_URL]</code>."
 msgstr ""
 
 #: ./doc/common/ch_cli_nova_commands.xml1608(para)
+#: ./doc/common/ch_cli_heat_commands.xml439(para)
 #: ./doc/common/ch_cli_ceilometer_commands.xml397(para)
 #: ./doc/common/ch_cli_cinder_commands.xml653(para)
-#: ./doc/common/ch_cli_heat_commands.xml439(para)
 #: ./doc/common/ch_cli_trove_commands.xml502(para)
 msgid "Defaults to <code>env[OS_REGION_NAME]</code>."
 msgstr ""
@@ -2496,30 +1295,6 @@ msgstr ""
 #: ./doc/common/ch_cli_nova_commands.xml6347(title)
 #: ./doc/common/ch_cli_nova_commands.xml6448(title)
 #: ./doc/common/ch_cli_nova_commands.xml6496(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml462(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml604(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml749(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml766(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml793(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml812(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml829(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml846(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml887(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1077(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1282(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1471(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1490(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1514(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1534(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1570(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1606(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1642(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1661(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1684(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1767(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1803(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1856(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1874(title)
 #: ./doc/common/ch_cli_neutron_commands.xml1434(title)
 #: ./doc/common/ch_cli_neutron_commands.xml1461(title)
 #: ./doc/common/ch_cli_neutron_commands.xml1517(title)
@@ -2673,12 +1448,51 @@ msgstr ""
 #: ./doc/common/ch_cli_neutron_commands.xml10279(title)
 #: ./doc/common/ch_cli_neutron_commands.xml10365(title)
 #: ./doc/common/ch_cli_neutron_commands.xml10419(title)
+#: ./doc/common/ch_cli_heat_commands.xml561(title)
+#: ./doc/common/ch_cli_heat_commands.xml739(title)
+#: ./doc/common/ch_cli_heat_commands.xml776(title)
+#: ./doc/common/ch_cli_heat_commands.xml848(title)
+#: ./doc/common/ch_cli_heat_commands.xml946(title)
+#: ./doc/common/ch_cli_heat_commands.xml1040(title)
+#: ./doc/common/ch_cli_heat_commands.xml1090(title)
+#: ./doc/common/ch_cli_heat_commands.xml1187(title)
+#: ./doc/common/ch_cli_heat_commands.xml1264(title)
 #: ./doc/common/ch_cli_swift_commands.xml358(title)
 #: ./doc/common/ch_cli_swift_commands.xml424(title)
 #: ./doc/common/ch_cli_swift_commands.xml527(title)
 #: ./doc/common/ch_cli_swift_commands.xml601(title)
 #: ./doc/common/ch_cli_swift_commands.xml684(title)
 #: ./doc/common/ch_cli_swift_commands.xml723(title)
+#: ./doc/common/ch_cli_glance_commands.xml527(title)
+#: ./doc/common/ch_cli_glance_commands.xml718(title)
+#: ./doc/common/ch_cli_glance_commands.xml862(title)
+#: ./doc/common/ch_cli_glance_commands.xml900(title)
+#: ./doc/common/ch_cli_glance_commands.xml1079(title)
+#: ./doc/common/ch_cli_glance_commands.xml1121(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml462(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml604(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml749(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml766(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml793(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml812(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml829(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml846(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml887(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1077(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1282(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1471(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1490(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1514(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1534(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1570(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1606(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1642(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1661(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1684(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1767(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1803(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1856(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1874(title)
 #: ./doc/common/ch_cli_cinder_commands.xml751(title)
 #: ./doc/common/ch_cli_cinder_commands.xml819(title)
 #: ./doc/common/ch_cli_cinder_commands.xml871(title)
@@ -2697,21 +1511,6 @@ msgstr ""
 #: ./doc/common/ch_cli_cinder_commands.xml2089(title)
 #: ./doc/common/ch_cli_cinder_commands.xml2162(title)
 #: ./doc/common/ch_cli_cinder_commands.xml2316(title)
-#: ./doc/common/ch_cli_glance_commands.xml527(title)
-#: ./doc/common/ch_cli_glance_commands.xml718(title)
-#: ./doc/common/ch_cli_glance_commands.xml862(title)
-#: ./doc/common/ch_cli_glance_commands.xml900(title)
-#: ./doc/common/ch_cli_glance_commands.xml1079(title)
-#: ./doc/common/ch_cli_glance_commands.xml1121(title)
-#: ./doc/common/ch_cli_heat_commands.xml561(title)
-#: ./doc/common/ch_cli_heat_commands.xml739(title)
-#: ./doc/common/ch_cli_heat_commands.xml776(title)
-#: ./doc/common/ch_cli_heat_commands.xml848(title)
-#: ./doc/common/ch_cli_heat_commands.xml946(title)
-#: ./doc/common/ch_cli_heat_commands.xml1040(title)
-#: ./doc/common/ch_cli_heat_commands.xml1090(title)
-#: ./doc/common/ch_cli_heat_commands.xml1187(title)
-#: ./doc/common/ch_cli_heat_commands.xml1264(title)
 #: ./doc/common/ch_cli_trove_commands.xml610(title)
 #: ./doc/common/ch_cli_trove_commands.xml653(title)
 #: ./doc/common/ch_cli_trove_commands.xml681(title)
@@ -3003,12 +1802,37 @@ msgstr ""
 #: ./doc/common/ch_cli_neutron_commands.xml10239(title)
 #: ./doc/common/ch_cli_neutron_commands.xml10354(title)
 #: ./doc/common/ch_cli_neutron_commands.xml10408(title)
+#: ./doc/common/ch_cli_heat_commands.xml509(title)
+#: ./doc/common/ch_cli_heat_commands.xml526(title)
+#: ./doc/common/ch_cli_heat_commands.xml550(title)
+#: ./doc/common/ch_cli_heat_commands.xml578(title)
+#: ./doc/common/ch_cli_heat_commands.xml611(title)
+#: ./doc/common/ch_cli_heat_commands.xml628(title)
+#: ./doc/common/ch_cli_heat_commands.xml653(title)
+#: ./doc/common/ch_cli_heat_commands.xml670(title)
+#: ./doc/common/ch_cli_heat_commands.xml695(title)
+#: ./doc/common/ch_cli_heat_commands.xml720(title)
+#: ./doc/common/ch_cli_heat_commands.xml765(title)
+#: ./doc/common/ch_cli_heat_commands.xml800(title)
+#: ./doc/common/ch_cli_heat_commands.xml817(title)
+#: ./doc/common/ch_cli_heat_commands.xml837(title)
+#: ./doc/common/ch_cli_heat_commands.xml935(title)
+#: ./doc/common/ch_cli_heat_commands.xml1022(title)
+#: ./doc/common/ch_cli_heat_commands.xml1079(title)
+#: ./doc/common/ch_cli_heat_commands.xml1157(title)
+#: ./doc/common/ch_cli_heat_commands.xml1176(title)
+#: ./doc/common/ch_cli_heat_commands.xml1246(title)
 #: ./doc/common/ch_cli_swift_commands.xml338(title)
 #: ./doc/common/ch_cli_swift_commands.xml402(title)
 #: ./doc/common/ch_cli_swift_commands.xml516(title)
 #: ./doc/common/ch_cli_swift_commands.xml581(title)
 #: ./doc/common/ch_cli_swift_commands.xml664(title)
 #: ./doc/common/ch_cli_swift_commands.xml703(title)
+#: ./doc/common/ch_cli_glance_commands.xml694(title)
+#: ./doc/common/ch_cli_glance_commands.xml851(title)
+#: ./doc/common/ch_cli_glance_commands.xml889(title)
+#: ./doc/common/ch_cli_glance_commands.xml1060(title)
+#: ./doc/common/ch_cli_glance_commands.xml1096(title)
 #: ./doc/common/ch_cli_cinder_commands.xml740(title)
 #: ./doc/common/ch_cli_cinder_commands.xml784(title)
 #: ./doc/common/ch_cli_cinder_commands.xml808(title)
@@ -3060,31 +1884,6 @@ msgstr ""
 #: ./doc/common/ch_cli_cinder_commands.xml2237(title)
 #: ./doc/common/ch_cli_cinder_commands.xml2254(title)
 #: ./doc/common/ch_cli_cinder_commands.xml2297(title)
-#: ./doc/common/ch_cli_glance_commands.xml694(title)
-#: ./doc/common/ch_cli_glance_commands.xml851(title)
-#: ./doc/common/ch_cli_glance_commands.xml889(title)
-#: ./doc/common/ch_cli_glance_commands.xml1060(title)
-#: ./doc/common/ch_cli_glance_commands.xml1096(title)
-#: ./doc/common/ch_cli_heat_commands.xml509(title)
-#: ./doc/common/ch_cli_heat_commands.xml526(title)
-#: ./doc/common/ch_cli_heat_commands.xml550(title)
-#: ./doc/common/ch_cli_heat_commands.xml578(title)
-#: ./doc/common/ch_cli_heat_commands.xml611(title)
-#: ./doc/common/ch_cli_heat_commands.xml628(title)
-#: ./doc/common/ch_cli_heat_commands.xml653(title)
-#: ./doc/common/ch_cli_heat_commands.xml670(title)
-#: ./doc/common/ch_cli_heat_commands.xml695(title)
-#: ./doc/common/ch_cli_heat_commands.xml720(title)
-#: ./doc/common/ch_cli_heat_commands.xml765(title)
-#: ./doc/common/ch_cli_heat_commands.xml800(title)
-#: ./doc/common/ch_cli_heat_commands.xml817(title)
-#: ./doc/common/ch_cli_heat_commands.xml837(title)
-#: ./doc/common/ch_cli_heat_commands.xml935(title)
-#: ./doc/common/ch_cli_heat_commands.xml1022(title)
-#: ./doc/common/ch_cli_heat_commands.xml1079(title)
-#: ./doc/common/ch_cli_heat_commands.xml1157(title)
-#: ./doc/common/ch_cli_heat_commands.xml1176(title)
-#: ./doc/common/ch_cli_heat_commands.xml1246(title)
 #: ./doc/common/ch_cli_trove_commands.xml591(title)
 #: ./doc/common/ch_cli_trove_commands.xml636(title)
 #: ./doc/common/ch_cli_trove_commands.xml670(title)
@@ -5091,40 +3890,311 @@ msgstr ""
 msgid "Filename to write the x509 root cert."
 msgstr ""
 
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_getstart_dashboard.xml14(None)
-msgid ""
-"@@image: 'figures/horizon-screenshot.jpg'; "
-"md5=9471047adf0d93713be7f54b9db2b53c"
-msgstr "@@image: 'figures/horizon-screenshot.jpg'; md5=9471047adf0d93713be7f54b9db2b53c"
+#: ./doc/common/section_xapi-ami-setup.xml7(title)
+msgid "Prepare for AMI type images"
+msgstr "Préparation pour les images de type AMI"
 
-#: ./doc/common/section_getstart_dashboard.xml5(title)
-msgid "OpenStack dashboard"
-msgstr "Tableau de bord OpenStack"
-
-#: ./doc/common/section_getstart_dashboard.xml6(para)
+#: ./doc/common/section_xapi-ami-setup.xml8(para)
 msgid ""
-"The OpenStack dashboard is a modular <link "
-"href=\"https://www.djangoproject.com/\">Django web application</link> that "
-"provides a graphical interface to OpenStack services."
+"To support AMI type images in your OpenStack installation, you must create a"
+" <filename>/boot/guest</filename> directory inside Dom0. The OpenStack VM "
+"extracts the kernel and ramdisk from the AKI and ARI images puts them in "
+"this location."
+msgstr "Dans le but de supporter les images de type AMI dans l'installation d'OpenStack, un répertoire <filename>/boot/guest</filename> doit être créer dans Dom0. Le VM OpenStack va placer le noyau et le ramdisk extraits des images AKI et ARI dans cet emplacement."
+
+#: ./doc/common/section_xapi-ami-setup.xml12(para)
+msgid ""
+"OpenStack maintains the contents of this directory and its size should not "
+"increase during normal operation. However, in case of power failures or "
+"accidental shutdowns, some files might be left over. To prevent these files "
+"from filling the Dom0 disk, set up this directory as a symlink that points "
+"to a subdirectory of the local SR."
+msgstr "Le contenu de ce répertoire sera maintenu par OpenStack, et sa taille ne devra pas augmenter pendant une opération normal. Cependant, en cas de défaillance électrique ou coupure de courant accidentelle, certains fichiers pourront être conservés. Dans le but d'empêcher ces fichiers d'encombrer le disque Dom0, il est recommandé de configurer ce répertoire en tant que liaison symbolique joint à un sous-répertoire du SR local."
+
+#: ./doc/common/section_xapi-ami-setup.xml18(para)
+msgid "Run these commands in Dom0 to achieve this setup:"
+msgstr "Exécutez les commandes suivantes dans Dom0 afin d'achever l'installation mentionnée ci-dessus:"
+
+#: ./doc/common/section_dashboard-configure-http.xml6(title)
+msgid "Configure the dashboard for HTTP"
 msgstr ""
 
-#: ./doc/common/section_getstart_dashboard.xml18(para)
+#: ./doc/common/section_dashboard-configure-http.xml8(para)
 msgid ""
-"The dashboard is usually deployed through <link "
-"href=\"http://code.google.com/p/modwsgi/\">mod_wsgi</link> in Apache. You "
-"can modify the dashboard code to make it suitable for different sites."
-msgstr "Le tableau de bord est généralement déployé par <link href=\"http://code.google.com/p/modwsgi/\">mod_wsgi</link> dans Apache. Vous pouvez modifier le code du tableau de bord pour qu'il convienne des autres sites web. "
+"You can configure the dashboard for a simple HTTP deployment. The standard "
+"installation uses a non-encrypted HTTP channel."
+msgstr ""
 
-#: ./doc/common/section_getstart_dashboard.xml22(para)
+#: ./doc/common/section_dashboard-configure-http.xml12(para)
 msgid ""
-"From a network architecture point of view, this service must be accessible "
-"to customers and the public API for each OpenStack service. To use the "
-"administrator functionality for other services, it must also connect to "
-"Admin API endpoints, which should not be accessible by customers."
-msgstr "Du point de vue de l'architecture réseau, ce service doit être accessible aux clients et à l'API publique pour chaque service d’OpenStack). Pour utiliser la fonctionnalité d'administrateur pour d'autres services, il faut aussi se connecter aux terminaisons de l'API d'administration, qui ne doivent pas être accessibles par les clients."
+"Specify the host for your OpenStack Identity Service endpoint in the "
+"<filename>/etc/openstack-dashboard/local_settings.py</filename> file with "
+"the <literal>OPENSTACK_HOST</literal> setting."
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-http.xml17(para)
+msgid "The following example shows this setting:"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-http.xml19(para)
+msgid ""
+"The service catalog configuration in the Identity Service determines whether"
+" a service appears in the dashboard. For the full listing, see <link "
+"href=\"http://docs.openstack.org/developer/horizon/topics/settings.html\">Horizon"
+" Settings and Configuration</link>."
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-http.xml28(para)
+msgid "Restart Apache http server. For Ubuntu/Debian/SUSE:"
+msgstr "Redémarrer la serveur Apache http. Pour Ubuntu/Debian/SUSE:"
+
+#: ./doc/common/section_dashboard-configure-http.xml30(para)
+msgid "or for Fedora/RHEL/CentOS:"
+msgstr "ou pour Fedora/RHEL/CentOS:"
+
+#: ./doc/common/section_dashboard-configure-http.xml32(para)
+#: ./doc/common/section_dashboard-configure-https.xml98(para)
+msgid "Next, restart memcached:"
+msgstr ""
+
+#: ./doc/common/section_rpc.xml7(title)
+#: ./doc/common/section_rpc-for-networking.xml7(title)
+msgid "Configure the Oslo RPC messaging system"
+msgstr ""
+
+#: ./doc/common/section_rpc.xml8(para)
+msgid ""
+"OpenStack projects use AMQP, an open standard for messaging middleware. "
+"OpenStack services that run on multiple servers to talk to each other. "
+"OpenStack Oslo RPC supports three implementations of AMQP: "
+"<application>RabbitMQ</application>, <application>Qpid</application>, and "
+"<application>ZeroMQ</application>."
+msgstr ""
+
+#: ./doc/common/section_rpc.xml15(title)
+#: ./doc/common/section_rpc-for-networking.xml18(title)
+msgid "Configure RabbitMQ"
+msgstr "Configuration pour RabbitMQ"
+
+#: ./doc/common/section_rpc.xml16(para)
+msgid ""
+"OpenStack Oslo RPC uses <application>RabbitMQ</application> by default. Use "
+"these options to configure the <application>RabbitMQ</application> message "
+"system. The <literal>rpc_backend</literal> option is not required as long as"
+" <application>RabbitMQ</application> is the default messaging system. "
+"However, if it is included the configuration, you must set it to "
+"<literal>nova.openstack.common.rpc.impl_kombu</literal>."
+msgstr ""
+
+#: ./doc/common/section_rpc.xml25(para)
+msgid ""
+"You can use these additional options to configure the "
+"<application>RabbitMQ</application> messaging system. You can configure "
+"messaging communication for different installation scenarios, tune retries "
+"for RabbitMQ, and define the size of the RPC thread pool. To monitor "
+"notifications through RabbitMQ, you must set the "
+"<option>notification_driver</option> option to "
+"<literal>nova.notifier.rabbit_notifier</literal> in the "
+"<filename>nova.conf</filename> file. The default for sending usage data is "
+"sixty seconds plus a random number of seconds from zero to sixty."
+msgstr ""
+
+#: ./doc/common/section_rpc.xml39(title)
+#: ./doc/common/section_rpc-for-networking.xml46(title)
+msgid "Configure Qpid"
+msgstr "Configuration pour Qpid"
+
+#: ./doc/common/section_rpc.xml40(para)
+msgid ""
+"Use these options to configure the <application>Qpid</application> messaging"
+" system for OpenStack Oslo RPC. <application>Qpid</application> is not the "
+"default messaging system, so you must enable it by setting the "
+"<option>rpc_backend</option> option in the <filename>nova.conf</filename> "
+"file."
+msgstr ""
+
+#: ./doc/common/section_rpc.xml47(para)
+msgid ""
+"This critical option points the compute nodes to the "
+"<application>Qpid</application> broker (server). Set "
+"<option>qpid_hostname</option> to the host name where the broker runs in the"
+" <filename>nova.conf</filename> file."
+msgstr ""
+
+#: ./doc/common/section_rpc.xml52(para)
+#: ./doc/common/section_rpc-for-networking.xml62(para)
+msgid ""
+"The <option>--qpid_hostname</option> option accepts a host name or IP "
+"address value."
+msgstr ""
+
+#: ./doc/common/section_rpc.xml56(para)
+#: ./doc/common/section_rpc-for-networking.xml69(para)
+msgid ""
+"If the <application>Qpid</application> broker listens on a port other than "
+"the AMQP default of <literal>5672</literal>, you must set the "
+"<option>qpid_port</option> option to that value:"
+msgstr ""
+
+#: ./doc/common/section_rpc.xml61(para)
+#: ./doc/common/section_rpc-for-networking.xml78(para)
+msgid ""
+"If you configure the <application>Qpid</application> broker to require "
+"authentication, you must add a user name and password to the configuration:"
+msgstr ""
+
+#: ./doc/common/section_rpc.xml66(para)
+#: ./doc/common/section_rpc-for-networking.xml87(para)
+msgid ""
+"By default, TCP is used as the transport. To enable SSL, set the "
+"<option>qpid_protocol</option> option:"
+msgstr ""
+
+#: ./doc/common/section_rpc.xml69(para)
+msgid ""
+"This table lists additional options that you use to configure the Qpid "
+"messaging driver for OpenStack Oslo RPC. These options are used "
+"infrequently."
+msgstr ""
+
+#: ./doc/common/section_rpc.xml75(title)
+#: ./doc/common/section_rpc-for-networking.xml102(title)
+msgid "Configure ZeroMQ"
+msgstr "Configurez ZeroMQ"
+
+#: ./doc/common/section_rpc.xml76(para)
+msgid ""
+"Use these options to configure the <application>ZeroMQ</application> "
+"messaging system for OpenStack Oslo RPC. <application>ZeroMQ</application> "
+"is not the default messaging system, so you must enable it by setting the "
+"<option>rpc_backend</option> option in the <filename>nova.conf</filename> "
+"file."
+msgstr ""
+
+#: ./doc/common/section_rpc.xml85(title)
+#: ./doc/common/section_rpc-for-networking.xml112(title)
+msgid "Configure messaging"
+msgstr ""
+
+#: ./doc/common/section_rpc.xml86(para)
+msgid ""
+"Use these options to configure the <application>RabbitMQ</application> and "
+"<application>Qpid</application> messaging drivers."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml6(title)
+msgid "User management"
+msgstr "Gestion des utilisateurs"
+
+#: ./doc/common/section_keystone-concepts-user-management.xml7(para)
+msgid "The main components of Identity user management are:"
+msgstr "Les trois concepts majeurs de la gestion des utilisateurs sont :"
+
+#: ./doc/common/section_keystone-concepts-user-management.xml10(para)
+msgid ""
+"<emphasis role=\"bold\">User</emphasis>. Represents a human user. Has "
+"associated information such as user name, password, and email. This example "
+"creates a user named <literal>alice</literal>:"
+msgstr "Un <emphasis role=\"bold\">User</emphasis> représente un utilisateur humain, et possède des informations associées telles que le nom d'utilisateur, un mot de passe, et un email. Par exemple, la création de l'utilisateur nommé <literal>alice</literal> :"
+
+#: ./doc/common/section_keystone-concepts-user-management.xml17(para)
+msgid ""
+"<emphasis role=\"bold\">Tenant</emphasis>. A project, group, or "
+"organization. When you make requests to OpenStack services, you must specify"
+" a tenant. For example, if you query the Compute service for a list of "
+"running instances, you get a list of all running instances in the tenant "
+"that you specified in your query. This example creates a tenant named "
+"<literal>acme</literal>:"
+msgstr "Un <emphasis role=\"bold\">Tenant</emphasis> peut être vu comme un projet, groupe, ou une organisation . Chaque fois que vous envoyez une requête aux services OpenStack, vous devez spécifier un ensemble. Par exemple, si vous vous enquérez auprès du service Calcul de la liste des instances en cours, vous recevrez la liste de toutes les instances en cours de l'ensemble spécifié dans votre requête. Cet exemple montre la création de l'ensemble nommé  <literal>acme</literal>: "
+
+#: ./doc/common/section_keystone-concepts-user-management.xml27(para)
+msgid ""
+"Because the term <emphasis>project</emphasis> was used instead of "
+"<emphasis>tenant</emphasis> in earlier versions of OpenStack Compute, some "
+"command-line tools use <literal>--project_id</literal> instead of <literal"
+">--tenant-id</literal> or <literal>--os-tenant-id</literal> to refer to a "
+"tenant ID."
+msgstr "Comme le terme <emphasis>project</emphasis> été utilisé au lieu de <emphasis>tenant</emphasis> dans les versions précédentes de OpenStack Compute, certains outils d'entrée de commande utilisent <literal>--project_id</literal> au lieu de <literal>--tenant-id</literal>]ou<literal>--os-tenant-id</literal>pour faire référence à l'ID d'un ensemble."
+
+#: ./doc/common/section_keystone-concepts-user-management.xml38(para)
+msgid ""
+"<emphasis role=\"bold\">Role</emphasis>. Captures the operations that a user"
+" can perform in a given tenant."
+msgstr "Un  <emphasis role=\"bold\">Role</emphasis> récapitule quelles opérations un utilisateur est en droit d'effectuer dans un ensemble donné. Cet exemple est la création d'un rôle nommé « compute-user » :"
+
+#: ./doc/common/section_keystone-concepts-user-management.xml40(para)
+msgid "This example creates a role named <literal>compute-user</literal>:"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml44(para)
+msgid ""
+"Individual services, such as Compute and the Image Service, assign meaning "
+"to roles. In the Identity Service, a role is simply a name."
+msgstr "C'est aux services individuels tels que le service Calcul et le service Image d'attribuer à ces rôles un sens. Pour le service Identité, un rôle n'est qu'un simple nom."
+
+#: ./doc/common/section_keystone-concepts-user-management.xml51(para)
+msgid ""
+"The Identity Service assigns a tenant and a role to a user. You might assign"
+" the <literal>compute-user</literal> role to the <literal>alice</literal> "
+"user in the <literal>acme</literal> tenant:"
+msgstr "Le service Identité associe un utilisateur à un ensemble et un rôle. Pour continuer nos exemples précédents, nous allons vouloir associer à l'utilisateur <literal>alice</literal> le rôle <literal>compute-user</literal> dans l'ensemble <literal>acme</literal> : "
+
+#: ./doc/common/section_keystone-concepts-user-management.xml74(para)
+msgid ""
+"A user can have different roles in different tenants. For example, Alice "
+"might also have the <literal>admin</literal> role in the "
+"<literal>Cyberdyne</literal> tenant. A user can also have multiple roles in "
+"the same tenant."
+msgstr "Un utilisateur peut se voir attribuer des rôles différents dans des ensembles différents : Par exemple, Alice peut aussi avoir le rôle <literal>admin</literal> dans l'ensemble <literal>Cyberdyne</literal>. On peut aussi attribuer à un individu plusieurs rôles dans le même ensemble. "
+
+#: ./doc/common/section_keystone-concepts-user-management.xml78(para)
+msgid ""
+"The "
+"<filename>/etc/<replaceable>[SERVICE_CODENAME]</replaceable>/policy.json</filename>"
+" file controls the tasks that users can perform for a given service. For "
+"example, <filename>/etc/nova/policy.json</filename> specifies the access "
+"policy for the Compute service, <filename>/etc/glance/policy.json</filename>"
+" specifies the access policy for the Image Service, and "
+"<filename>/etc/keystone/policy.json</filename> specifies the access policy "
+"for the Identity Service."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml88(para)
+msgid ""
+"The default <filename>policy.json</filename> files in the Compute, Identity,"
+" and Image Service recognize only the <literal>admin</literal> role: all "
+"operations that do not require the <literal>admin</literal> role are "
+"accessible by any user that has any role in a tenant."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml93(para)
+msgid ""
+"If you wish to restrict users from performing operations in, say, the "
+"Compute service, you need to create a role in the Identity Service and then "
+"modify <filename>/etc/nova/policy.json</filename> so that this role is "
+"required for Compute operations."
+msgstr "Si vous voulez restreindre les permissions des utilisateurs d'effectuer des opérations dans par exemple le service Calcul, vous devez créer un rôle dans le service Identité, et modifier <filename>/etc/nova/policy.json</filename> pour que ce rôle soit nécessaire afin d'effectuer des opérations de Calcul. "
+
+#: ./doc/common/section_keystone-concepts-user-management.xml99(para)
+msgid ""
+"For example, this line in <filename>/etc/nova/policy.json</filename> "
+"specifies that there are no restrictions on which users can create volumes: "
+"if the user has any role in a tenant, they can create volumes in that "
+"tenant."
+msgstr "Par exemple, cette ligne dans <filename>/etc/nova/policy.json</filename> spécifies qu'il n'y a aucune restriction concernant la création de volumes par les utilisateurs : si l'utilisateur a un rôle quelconque dans un ensemble, il sera capable de créer des volumes dans cet ensemble."
+
+#: ./doc/common/section_keystone-concepts-user-management.xml105(para)
+msgid ""
+"To restrict creation of volumes to users who had the <literal>compute-"
+"user</literal> role in a particular tenant, you would add <literal>\"role"
+":compute-user\"</literal>, like so:"
+msgstr "Si on souhaite restreindre la création de volume aux utilisateurs qui ont le rôle <literal>compute-user</literal> dans un ensemble particulier, il faudrait ajouter <literal>\"role:compute-user\"</literal>, ainsi : "
+
+#: ./doc/common/section_keystone-concepts-user-management.xml110(para)
+msgid ""
+"To restrict all Compute service requests to require this role, the resulting"
+" file would look like:"
+msgstr "Si on souhaite que toutes les requêtes de Calcul soient soumise à la possession de ce rôle, le fichier qu'il en résulterait ressemblerait à ceci : "
 
 #: ./doc/common/section_cli_nova_quotas.xml6(title)
 msgid "Manage Compute service quotas"
@@ -5147,390 +4217,390 @@ msgid "Quota name"
 msgstr ""
 
 #: ./doc/common/section_cli_nova_quotas.xml20(th)
-#: ./doc/common/ch_getstart.xml31(th)
 #: ./doc/common/section_cli_nova_customize_flavors.xml40(td)
-#: ./doc/common/section_cli_overview.xml36(th)
-#: ./doc/common/section_cli_install.xml22(th)
-#: ./doc/common/tables/nova-cells.xml14(th)
-#: ./doc/common/tables/trove-db_mongodb.xml14(th)
-#: ./doc/common/tables/keystone-debug.xml14(th)
-#: ./doc/common/tables/glance-policy.xml14(th)
-#: ./doc/common/tables/neutron-mlnx.xml14(th)
-#: ./doc/common/tables/nova-ipv6.xml14(th)
-#: ./doc/common/tables/cinder-eqlx.xml14(th)
-#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml13(th)
-#: ./doc/common/tables/swift-object-expirer-filter-cache.xml13(th)
-#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml13(th)
-#: ./doc/common/tables/nova-rpc_all.xml14(th)
-#: ./doc/common/tables/neutron-ml2_l2pop.xml14(th)
-#: ./doc/common/tables/glance-qpid.xml14(th)
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml13(th)
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml14(th)
-#: ./doc/common/tables/neutron-ml2_gre.xml14(th)
-#: ./doc/common/tables/nova-volumes.xml14(th)
-#: ./doc/common/tables/glance-gridfs.xml14(th)
-#: ./doc/common/tables/neutron-ml2_arista.xml14(th)
-#: ./doc/common/tables/glance-filesystem.xml14(th)
-#: ./doc/common/tables/heat-redis.xml14(th)
-#: ./doc/common/tables/trove-logging.xml14(th)
-#: ./doc/common/tables/swift-container-server-container-updater.xml13(th)
-#: ./doc/common/tables/cinder-storage_gpfs.xml14(th)
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml14(th)
-#: ./doc/common/tables/nova-tilera.xml14(th)
-#: ./doc/common/tables/nova-ca.xml14(th)
-#: ./doc/common/tables/heat-clients_nova.xml14(th)
-#: ./doc/common/tables/swift-account-server-filter-recon.xml13(th)
-#: ./doc/common/tables/cinder-huawei.xml14(th)
-#: ./doc/common/tables/keystone-qpid.xml14(th)
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml14(th)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml13(th)
-#: ./doc/common/tables/nova-glance.xml14(th)
-#: ./doc/common/tables/neutron-dhcp_agent.xml14(th)
-#: ./doc/common/tables/nova-neutron.xml14(th)
-#: ./doc/common/tables/cinder-backups_ceph.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml13(th)
-#: ./doc/common/tables/nova-metadata.xml14(th)
-#: ./doc/common/tables/glance-s3.xml14(th)
-#: ./doc/common/tables/glance-auth_token.xml14(th)
-#: ./doc/common/tables/neutron-kombu.xml14(th)
-#: ./doc/common/tables/trove-redis.xml14(th)
-#: ./doc/common/tables/trove-qpid.xml14(th)
-#: ./doc/common/tables/trove-compute.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml13(th)
-#: ./doc/common/tables/trove-nova.xml14(th)
-#: ./doc/common/tables/ceilometer-cells.xml14(th)
-#: ./doc/common/tables/keystone-oauth.xml14(th)
-#: ./doc/common/tables/cinder-block-device.xml14(th)
-#: ./doc/common/tables/cinder-zones.xml14(th)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml14(th)
-#: ./doc/common/tables/swift-container-server-container-sync.xml13(th)
-#: ./doc/common/tables/neutron-common.xml14(th)
-#: ./doc/common/tables/neutron-compute.xml14(th)
-#: ./doc/common/tables/swift-object-server-object-auditor.xml13(th)
-#: ./doc/common/tables/keystone-ldap.xml14(th)
-#: ./doc/common/tables/heat-rpc.xml14(th)
-#: ./doc/common/tables/neutron-openvswitch_agent.xml14(th)
-#: ./doc/common/tables/cinder-compute.xml14(th)
-#: ./doc/common/tables/keystone-identity.xml14(th)
-#: ./doc/common/tables/cinder-lvm.xml14(th)
-#: ./doc/common/tables/keystone-trust.xml14(th)
-#: ./doc/common/tables/cinder-storage_nfs.xml14(th)
-#: ./doc/common/tables/neutron-plumgrid.xml14(th)
-#: ./doc/common/tables/heat-cfn_api.xml14(th)
-#: ./doc/common/tables/nova-hypervisor.xml14(th)
-#: ./doc/common/tables/trove-rabbitmq.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml13(th)
-#: ./doc/common/tables/trove-api.xml14(th)
-#: ./doc/common/tables/cinder-quota.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml13(th)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml13(th)
-#: ./doc/common/tables/nova-console.xml14(th)
-#: ./doc/common/tables/ceilometer-events.xml14(th)
-#: ./doc/common/tables/keystone-os_inherit.xml14(th)
-#: ./doc/common/tables/heat-clients.xml14(th)
-#: ./doc/common/tables/heat-notification.xml14(th)
-#: ./doc/common/tables/keystone-assignment.xml14(th)
-#: ./doc/common/tables/nova-common.xml14(th)
-#: ./doc/common/tables/swift-object-server-object-updater.xml13(th)
-#: ./doc/common/tables/glance-zmq.xml14(th)
-#: ./doc/common/tables/neutron-metering_agent.xml14(th)
-#: ./doc/common/tables/trove-taskmanager.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml13(th)
-#: ./doc/common/tables/keystone-zeromq.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml13(th)
-#: ./doc/common/tables/nova-keymgr.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml13(th)
-#: ./doc/common/tables/neutron-api.xml14(th)
-#: ./doc/common/tables/ceilometer-redis.xml14(th)
-#: ./doc/common/tables/ceilometer-swift.xml14(th)
-#: ./doc/common/tables/cinder-hplefthand.xml14(th)
-#: ./doc/common/tables/heat-qpid.xml14(th)
-#: ./doc/common/tables/nova-testing.xml14(th)
-#: ./doc/common/tables/cinder-backups.xml14(th)
-#: ./doc/common/tables/swift-container-server-pipeline-main.xml13(th)
-#: ./doc/common/tables/neutron-ml2_ofa.xml14(th)
-#: ./doc/common/tables/trove-debug.xml14(th)
-#: ./doc/common/tables/swift-rsyncd-object.xml13(th)
-#: ./doc/common/tables/nova-s3.xml14(th)
-#: ./doc/common/tables/nova-zookeeper.xml14(th)
-#: ./doc/common/tables/cinder-rpc.xml14(th)
-#: ./doc/common/tables/cinder-api.xml14(th)
-#: ./doc/common/tables/cinder-windows.xml14(th)
-#: ./doc/common/tables/glance-vmware.xml14(th)
-#: ./doc/common/tables/swift-object-server-pipeline-main.xml13(th)
-#: ./doc/common/tables/trove-backup.xml14(th)
-#: ./doc/common/tables/nova-auth_token.xml14(th)
-#: ./doc/common/tables/cinder-san.xml14(th)
-#: ./doc/common/tables/swift-account-server-app-account-server.xml13(th)
-#: ./doc/common/tables/keystone-rpc.xml14(th)
-#: ./doc/common/tables/cinder-keymgr.xml14(th)
-#: ./doc/common/tables/nova-db.xml14(th)
-#: ./doc/common/tables/neutron-ml2_vxlan.xml14(th)
-#: ./doc/common/tables/glance-logging.xml14(th)
-#: ./doc/common/tables/cinder-zoning.xml14(th)
-#: ./doc/common/tables/glance-wsgi.xml14(th)
-#: ./doc/common/tables/nova-periodic.xml14(th)
-#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml13(th)
-#: ./doc/common/tables/cinder-images.xml14(th)
-#: ./doc/common/tables/trove-swift.xml14(th)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml13(th)
-#: ./doc/common/tables/cinder-auth_token.xml14(th)
-#: ./doc/common/tables/heat-crypt.xml14(th)
-#: ./doc/common/tables/neutron-wsgi.xml14(th)
-#: ./doc/common/tables/neutron-scheduler.xml14(th)
-#: ./doc/common/tables/keystone-security.xml14(th)
-#: ./doc/common/tables/ceilometer-vmware.xml14(th)
-#: ./doc/common/tables/glance-rbd.xml14(th)
-#: ./doc/common/tables/heat-clients_heat.xml14(th)
-#: ./doc/common/tables/heat-rabbitmq.xml14(th)
-#: ./doc/common/tables/ceilometer-logging.xml14(th)
-#: ./doc/common/tables/neutron-metadata.xml14(th)
-#: ./doc/common/tables/glance-redis.xml14(th)
-#: ./doc/common/tables/keystone-stats.xml14(th)
-#: ./doc/common/tables/cinder-hp3par.xml14(th)
-#: ./doc/common/tables/cinder-storage_ceph.xml14(th)
-#: ./doc/common/tables/nova-livemigration.xml14(th)
-#: ./doc/common/tables/nova-ldap.xml14(th)
-#: ./doc/common/tables/nova-fping.xml14(th)
-#: ./doc/common/tables/heat-clients_swift.xml14(th)
-#: ./doc/common/tables/neutron-securitygroups.xml14(th)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml14(th)
-#: ./doc/common/tables/nova-ec2.xml14(th)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml13(th)
-#: ./doc/common/tables/trove-zeromq.xml14(th)
-#: ./doc/common/tables/heat-database.xml14(th)
-#: ./doc/common/tables/keystone-catalog.xml14(th)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml13(th)
-#: ./doc/common/tables/cinder-rootwrap.xml14(th)
+#: ./doc/common/section_cli_overview.xml43(th)
+#: ./doc/common/section_cli_install.xml30(th)
+#: ./doc/common/ch_getstart.xml31(th)
 #: ./doc/common/tables/ceilometer-database.xml14(th)
-#: ./doc/common/tables/heat-debug.xml14(th)
-#: ./doc/common/tables/cinder-nexenta_nfs.xml14(th)
-#: ./doc/common/tables/trove-auth_token.xml14(th)
-#: ./doc/common/tables/heat-waitcondition_api.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml13(th)
-#: ./doc/common/tables/neutron-ml2_vlan.xml14(th)
-#: ./doc/common/tables/nova-policy.xml14(th)
-#: ./doc/common/tables/keystone-amqp.xml14(th)
-#: ./doc/common/tables/neutron-logging.xml14(th)
-#: ./doc/common/tables/trove-db_cassandra.xml14(th)
+#: ./doc/common/tables/neutron-openvswitch_agent.xml14(th)
+#: ./doc/common/tables/heat-clients.xml14(th)
+#: ./doc/common/tables/cinder-solidfire.xml14(th)
+#: ./doc/common/tables/neutron-rpc.xml14(th)
+#: ./doc/common/tables/trove-db_percona.xml14(th)
+#: ./doc/common/tables/nova-periodic.xml14(th)
+#: ./doc/common/tables/keystone-auth.xml14(th)
+#: ./doc/common/tables/keystone-policy.xml14(th)
+#: ./doc/common/tables/glance-auth_token.xml14(th)
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml14(th)
+#: ./doc/common/tables/swift-container-server-container-sync.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml13(th)
+#: ./doc/common/tables/cinder-zoning_fabric.xml14(th)
+#: ./doc/common/tables/ceilometer-redis.xml14(th)
+#: ./doc/common/tables/cinder-storage_ceph.xml14(th)
+#: ./doc/common/tables/ceilometer-vmware.xml14(th)
+#: ./doc/common/tables/neutron-cisco.xml14(th)
+#: ./doc/common/tables/nova-testing.xml14(th)
+#: ./doc/common/tables/nova-metadata.xml14(th)
+#: ./doc/common/tables/heat-clients_nova.xml14(th)
+#: ./doc/common/tables/cinder-hp3par.xml14(th)
+#: ./doc/common/tables/keystone-misc.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml13(th)
+#: ./doc/common/tables/neutron-scheduler.xml14(th)
+#: ./doc/common/tables/glance-rbd.xml14(th)
+#: ./doc/common/tables/cinder-storage_xen.xml14(th)
+#: ./doc/common/tables/ceilometer-common.xml14(th)
+#: ./doc/common/tables/cinder-database.xml14(th)
+#: ./doc/common/tables/ceilometer-logging.xml14(th)
+#: ./doc/common/tables/heat-common.xml14(th)
+#: ./doc/common/tables/nova-ipv6.xml14(th)
+#: ./doc/common/tables/nova-vnc.xml14(th)
+#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml13(th)
+#: ./doc/common/tables/trove-qpid.xml14(th)
+#: ./doc/common/tables/keystone-api.xml14(th)
+#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml13(th)
+#: ./doc/common/tables/swift-container-server-container-auditor.xml13(th)
 #: ./doc/common/tables/glance-rpc.xml14(th)
-#: ./doc/common/tables/nova-authentication.xml14(th)
+#: ./doc/common/tables/neutron-policy.xml14(th)
+#: ./doc/common/tables/nova-spice.xml14(th)
+#: ./doc/common/tables/heat-clients_heat.xml14(th)
+#: ./doc/common/tables/nova-xen.xml14(th)
+#: ./doc/common/tables/trove-amqp.xml14(th)
+#: ./doc/common/tables/glance-matchmaker.xml14(th)
+#: ./doc/common/tables/nova-rabbitmq.xml14(th)
+#: ./doc/common/tables/neutron-ml2_cisco.xml14(th)
+#: ./doc/common/tables/nova-policy.xml14(th)
+#: ./doc/common/tables/keystone-identity.xml14(th)
+#: ./doc/common/tables/ceilometer-inspector.xml14(th)
+#: ./doc/common/tables/cinder-scheduler.xml14(th)
+#: ./doc/common/tables/trove-db_cassandra.xml14(th)
+#: ./doc/common/tables/neutron-logging.xml14(th)
+#: ./doc/common/tables/nova-availabilityzones.xml14(th)
+#: ./doc/common/tables/keystone-catalog.xml14(th)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml14(th)
+#: ./doc/common/tables/neutron-rootwrap.xml14(th)
+#: ./doc/common/tables/cinder-auth.xml14(th)
+#: ./doc/common/tables/swift-swift-swift-constraints.xml13(th)
+#: ./doc/common/tables/heat-qpid.xml14(th)
+#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml13(th)
+#: ./doc/common/tables/nova-zookeeper.xml14(th)
+#: ./doc/common/tables/nova-keymgr.xml14(th)
+#: ./doc/common/tables/neutron-auth_token.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml13(th)
+#: ./doc/common/tables/nova-ldap.xml14(th)
+#: ./doc/common/tables/swift-container-server-filter-recon.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml13(th)
+#: ./doc/common/tables/ceilometer-auth.xml14(th)
+#: ./doc/common/tables/cinder-quota.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml13(th)
+#: ./doc/common/tables/keystone-os_inherit.xml14(th)
+#: ./doc/common/tables/neutron-sdnve.xml14(th)
+#: ./doc/common/tables/nova-compute.xml14(th)
+#: ./doc/common/tables/keystone-rabbit.xml14(th)
+#: ./doc/common/tables/cinder-backups_ceph.xml14(th)
+#: ./doc/common/tables/nova-vmware.xml14(th)
+#: ./doc/common/tables/heat-cfn_api.xml14(th)
+#: ./doc/common/tables/neutron-vmware.xml14(th)
+#: ./doc/common/tables/nova-rdp.xml14(th)
+#: ./doc/common/tables/keystone-assignment.xml14(th)
+#: ./doc/common/tables/nova-zeromq.xml14(th)
+#: ./doc/common/tables/cinder-storage.xml14(th)
+#: ./doc/common/tables/glance-registry.xml14(th)
+#: ./doc/common/tables/neutron-embrane.xml14(th)
+#: ./doc/common/tables/heat-quota.xml14(th)
+#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml13(th)
+#: ./doc/common/tables/nova-common.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml13(th)
+#: ./doc/common/tables/nova-volumes.xml14(th)
+#: ./doc/common/tables/neutron-redis.xml14(th)
+#: ./doc/common/tables/trove-db_mysql.xml14(th)
+#: ./doc/common/tables/heat-zeromq.xml14(th)
+#: ./doc/common/tables/heat-amqp.xml14(th)
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml14(th)
+#: ./doc/common/tables/nova-redis.xml14(th)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml13(th)
+#: ./doc/common/tables/nova-db.xml14(th)
+#: ./doc/common/tables/glance-rabbitmq.xml14(th)
+#: ./doc/common/tables/neutron-l3_agent.xml14(th)
+#: ./doc/common/tables/swift-container-server-pipeline-main.xml13(th)
+#: ./doc/common/tables/glance-policy.xml14(th)
+#: ./doc/common/tables/nova-neutron.xml14(th)
+#: ./doc/common/tables/cinder-backups.xml14(th)
+#: ./doc/common/tables/cinder-keymgr.xml14(th)
+#: ./doc/common/tables/ceilometer-cells.xml14(th)
+#: ./doc/common/tables/keystone-ldap.xml14(th)
+#: ./doc/common/tables/glance-vmware.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml13(th)
+#: ./doc/common/tables/cinder-zoning.xml14(th)
+#: ./doc/common/tables/heat-notification.xml14(th)
+#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml13(th)
+#: ./doc/common/tables/nova-vpn.xml14(th)
+#: ./doc/common/tables/neutron-vpn.xml14(th)
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml13(th)
+#: ./doc/common/tables/trove-common.xml14(th)
+#: ./doc/common/tables/trove-api.xml14(th)
+#: ./doc/common/tables/cinder-zadara.xml14(th)
+#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml13(th)
+#: ./doc/common/tables/nova-conductor.xml14(th)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml13(th)
+#: ./doc/common/tables/nova-livemigration.xml14(th)
+#: ./doc/common/tables/heat-rabbitmq.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml13(th)
+#: ./doc/common/tables/neutron-cadf.xml14(th)
+#: ./doc/common/tables/keystone-amqp.xml14(th)
+#: ./doc/common/tables/keystone-rpc.xml14(th)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml13(th)
+#: ./doc/common/tables/cinder-zones.xml14(th)
+#: ./doc/common/tables/cinder-scality.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml13(th)
+#: ./doc/common/tables/neutron-agent.xml14(th)
+#: ./doc/common/tables/cinder-emc.xml14(th)
 #: ./doc/common/tables/cinder-vmware.xml14(th)
-#: ./doc/common/tables/glance-sheepdog.xml14(th)
-#: ./doc/common/tables/heat-logging.xml14(th)
-#: ./doc/common/tables/keystone-notification.xml14(th)
-#: ./doc/common/tables/neutron-qpid.xml14(th)
-#: ./doc/common/tables/neutron-hyperv_agent.xml14(th)
+#: ./doc/common/tables/neutron-ml2_flat.xml14(th)
+#: ./doc/common/tables/heat-metadata_api.xml14(th)
+#: ./doc/common/tables/trove-rabbitmq.xml14(th)
+#: ./doc/common/tables/nova-upgrade_levels.xml14(th)
+#: ./doc/common/tables/neutron-kombu.xml14(th)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml14(th)
+#: ./doc/common/tables/neutron-ml2_ofa.xml14(th)
+#: ./doc/common/tables/glance-api.xml14(th)
+#: ./doc/common/tables/heat-waitcondition_api.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml13(th)
+#: ./doc/common/tables/swift-rsyncd-container.xml13(th)
+#: ./doc/common/tables/cinder-storwize.xml14(th)
+#: ./doc/common/tables/cinder-hplefthand.xml14(th)
+#: ./doc/common/tables/glance-s3.xml14(th)
+#: ./doc/common/tables/nova-rootwrap.xml14(th)
+#: ./doc/common/tables/heat-loadbalancer.xml14(th)
+#: ./doc/common/tables/ceilometer-api.xml14(th)
+#: ./doc/common/tables/ceilometer-exchange.xml14(th)
+#: ./doc/common/tables/cinder-lvm.xml14(th)
+#: ./doc/common/tables/trove-dns.xml14(th)
+#: ./doc/common/tables/nova-cells.xml14(th)
+#: ./doc/common/tables/trove-volume.xml14(th)
+#: ./doc/common/tables/heat-auth_token.xml14(th)
+#: ./doc/common/tables/neutron-quotas.xml14(th)
+#: ./doc/common/tables/nova-auth_token.xml14(th)
+#: ./doc/common/tables/cinder-storage_nfs.xml14(th)
+#: ./doc/common/tables/heat-api.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml13(th)
+#: ./doc/common/tables/heat-clients_ceilometer.xml14(th)
+#: ./doc/common/tables/neutron-ryu.xml14(th)
+#: ./doc/common/tables/glance-logging.xml14(th)
+#: ./doc/common/tables/swift-rsyncd-account.xml13(th)
+#: ./doc/common/tables/neutron-metering_agent.xml14(th)
+#: ./doc/common/tables/neutron-zeromq.xml14(th)
+#: ./doc/common/tables/cinder-storage_glusterfs.xml14(th)
+#: ./doc/common/tables/cinder-common.xml14(th)
 #: ./doc/common/tables/glance-swift.xml14(th)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml13(th)
+#: ./doc/common/tables/trove-quota.xml14(th)
+#: ./doc/common/tables/cinder-auth_token.xml14(th)
+#: ./doc/common/tables/ceilometer-alarm.xml14(th)
+#: ./doc/common/tables/ceilometer-events.xml14(th)
+#: ./doc/common/tables/cinder-xiv.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml13(th)
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml14(th)
+#: ./doc/common/tables/nova-glance.xml14(th)
+#: ./doc/common/tables/keystone-auth_token.xml14(th)
+#: ./doc/common/tables/nova-s3.xml14(th)
+#: ./doc/common/tables/nova-pci.xml14(th)
+#: ./doc/common/tables/swift-account-server-filter-recon.xml13(th)
+#: ./doc/common/tables/heat-clients_cinder.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml13(th)
+#: ./doc/common/tables/keystone-revoke.xml14(th)
+#: ./doc/common/tables/cinder-api.xml14(th)
+#: ./doc/common/tables/trove-db_couchbase.xml14(th)
+#: ./doc/common/tables/heat-clients_trove.xml14(th)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml13(th)
+#: ./doc/common/tables/neutron-plumgrid.xml14(th)
+#: ./doc/common/tables/trove-heat.xml14(th)
+#: ./doc/common/tables/glance-sheepdog.xml14(th)
+#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml13(th)
+#: ./doc/common/tables/cinder-windows.xml14(th)
+#: ./doc/common/tables/cinder-san-solaris.xml14(th)
+#: ./doc/common/tables/neutron-nuage.xml14(th)
+#: ./doc/common/tables/keystone-zeromq.xml14(th)
 #: ./doc/common/tables/neutron-bigswitch.xml14(th)
-#: ./doc/common/tables/nova-libvirt.xml14(th)
+#: ./doc/common/tables/ceilometer-rpc.xml14(th)
+#: ./doc/common/tables/swift-container-server-container-updater.xml13(th)
+#: ./doc/common/tables/trove-db_mongodb.xml14(th)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml13(th)
+#: ./doc/common/tables/glance-filesystem.xml14(th)
+#: ./doc/common/tables/trove-rpc.xml14(th)
+#: ./doc/common/tables/ceilometer-swift.xml14(th)
+#: ./doc/common/tables/trove-backup.xml14(th)
+#: ./doc/common/tables/nova-network.xml14(th)
+#: ./doc/common/tables/glance-redis.xml14(th)
+#: ./doc/common/tables/keystone-ssl.xml14(th)
+#: ./doc/common/tables/nova-ca.xml14(th)
+#: ./doc/common/tables/neutron-dhcp_agent.xml14(th)
+#: ./doc/common/tables/ceilometer-collector.xml14(th)
+#: ./doc/common/tables/cinder-hds-hus.xml14(th)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml14(th)
+#: ./doc/common/tables/swift-swift-swift-hash.xml13(th)
+#: ./doc/common/tables/neutron-ml2_gre.xml14(th)
+#: ./doc/common/tables/neutron-varmour.xml14(th)
+#: ./doc/common/tables/heat-debug.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml13(th)
+#: ./doc/common/tables/nova-kombu.xml14(th)
+#: ./doc/common/tables/trove-guestagent.xml14(th)
+#: ./doc/common/tables/nova-qpid.xml14(th)
+#: ./doc/common/tables/glance-qpid.xml14(th)
+#: ./doc/common/tables/neutron-ml2_l2pop.xml14(th)
+#: ./doc/common/tables/glance-amqp.xml14(th)
+#: ./doc/common/tables/glance-zmq.xml14(th)
+#: ./doc/common/tables/neutron-embrane_lb.xml14(th)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml13(th)
+#: ./doc/common/tables/neutron-testing.xml14(th)
+#: ./doc/common/tables/swift-object-server-pipeline-main.xml13(th)
+#: ./doc/common/tables/swift-memcache-memcache.xml13(th)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml13(th)
+#: ./doc/common/tables/trove-compute.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml13(th)
+#: ./doc/common/tables/swift-object-expirer-filter-cache.xml13(th)
+#: ./doc/common/tables/trove-db_redis.xml14(th)
+#: ./doc/common/tables/cinder-rpc.xml14(th)
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml13(th)
+#: ./doc/common/tables/cinder-hpmsa.xml14(th)
+#: ./doc/common/tables/nova-apiv3.xml14(th)
+#: ./doc/common/tables/keystone-oauth.xml14(th)
+#: ./doc/common/tables/cinder-storage_gpfs.xml14(th)
+#: ./doc/common/tables/neutron-ml2_vlan.xml14(th)
+#: ./doc/common/tables/keystone-notification.xml14(th)
+#: ./doc/common/tables/swift-object-server-object-auditor.xml13(th)
+#: ./doc/common/tables/trove-zeromq.xml14(th)
 #: ./doc/common/tables/neutron-lbaas.xml14(th)
 #: ./doc/common/tables/cinder-backups_swift.xml14(th)
-#: ./doc/common/tables/neutron-ml2_cisco.xml14(th)
-#: ./doc/common/tables/ceilometer-rpc.xml14(th)
-#: ./doc/common/tables/heat-loadbalancer.xml14(th)
-#: ./doc/common/tables/heat-cloudwatch_api.xml14(th)
-#: ./doc/common/tables/nova-pci.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml13(th)
-#: ./doc/common/tables/heat-clients_ceilometer.xml14(th)
-#: ./doc/common/tables/neutron-varmour.xml14(th)
-#: ./doc/common/tables/glance-imagecache.xml14(th)
-#: ./doc/common/tables/trove-quota.xml14(th)
-#: ./doc/common/tables/swift-rsyncd-account.xml13(th)
-#: ./doc/common/tables/cinder-storage.xml14(th)
-#: ./doc/common/tables/cinder-nas.xml14(th)
-#: ./doc/common/tables/nova-vpn.xml14(th)
-#: ./doc/common/tables/nova-wsgi.xml14(th)
-#: ./doc/common/tables/cinder-storage_glusterfs.xml14(th)
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml13(th)
-#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml13(th)
-#: ./doc/common/tables/nova-availabilityzones.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml13(th)
-#: ./doc/common/tables/heat-zeromq.xml14(th)
-#: ./doc/common/tables/keystone-memcache.xml14(th)
-#: ./doc/common/tables/nova-vnc.xml14(th)
-#: ./doc/common/tables/swift-swift-swift-constraints.xml13(th)
-#: ./doc/common/tables/neutron-cisco.xml14(th)
-#: ./doc/common/tables/keystone-logging.xml14(th)
-#: ./doc/common/tables/nova-hyperv.xml14(th)
-#: ./doc/common/tables/neutron-l3_agent.xml14(th)
-#: ./doc/common/tables/swift-object-server-filter-recon.xml13(th)
-#: ./doc/common/tables/cinder-coraid.xml14(th)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml13(th)
-#: ./doc/common/tables/nova-vmware.xml14(th)
-#: ./doc/common/tables/nova-logging.xml14(th)
-#: ./doc/common/tables/nova-xen.xml14(th)
-#: ./doc/common/tables/ceilometer-collector.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml13(th)
-#: ./doc/common/tables/keystone-ec2.xml14(th)
-#: ./doc/common/tables/keystone-auth.xml14(th)
-#: ./doc/common/tables/swift-memcache-memcache.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml13(th)
-#: ./doc/common/tables/neutron-ml2.xml14(th)
-#: ./doc/common/tables/ceilometer-api.xml14(th)
-#: ./doc/common/tables/heat-clients_trove.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml13(th)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml14(th)
-#: ./doc/common/tables/glance-common.xml14(th)
-#: ./doc/common/tables/nova-network.xml14(th)
-#: ./doc/common/tables/cinder-scality.xml14(th)
-#: ./doc/common/tables/neutron-notifier.xml14(th)
-#: ./doc/common/tables/cinder-common.xml14(th)
-#: ./doc/common/tables/nova-trustedcomputing.xml14(th)
-#: ./doc/common/tables/neutron-ml2_flat.xml14(th)
-#: ./doc/common/tables/heat-clients_cinder.xml14(th)
-#: ./doc/common/tables/nova-configdrive.xml14(th)
-#: ./doc/common/tables/cinder-database.xml14(th)
-#: ./doc/common/tables/neutron-rpc.xml14(th)
-#: ./doc/common/tables/cinder-zoning_manager.xml14(th)
-#: ./doc/common/tables/trove-volume.xml14(th)
-#: ./doc/common/tables/keystone-cache.xml14(th)
-#: ./doc/common/tables/nova-zeromq.xml14(th)
-#: ./doc/common/tables/glance-testing.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml13(th)
-#: ./doc/common/tables/glance-registry.xml14(th)
-#: ./doc/common/tables/glance-amqp.xml14(th)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml13(th)
 #: ./doc/common/tables/trove-database.xml14(th)
-#: ./doc/common/tables/heat-clients_backends.xml14(th)
-#: ./doc/common/tables/heat-amqp.xml14(th)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml13(th)
-#: ./doc/common/tables/cinder-hpmsa.xml14(th)
-#: ./doc/common/tables/cinder-emc.xml14(th)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml13(th)
-#: ./doc/common/tables/neutron-fwaas.xml14(th)
-#: ./doc/common/tables/glance-rabbitmq.xml14(th)
-#: ./doc/common/tables/cinder-backups_tsm.xml14(th)
-#: ./doc/common/tables/neutron-sdnve.xml14(th)
-#: ./doc/common/tables/trove-db_mysql.xml14(th)
-#: ./doc/common/tables/nova-qpid.xml14(th)
-#: ./doc/common/tables/trove-rpc.xml14(th)
-#: ./doc/common/tables/cinder-connection.xml14(th)
-#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml13(th)
-#: ./doc/common/tables/trove-db_redis.xml14(th)
-#: ./doc/common/tables/ceilometer-qpid.xml14(th)
-#: ./doc/common/tables/neutron-zeromq.xml14(th)
-#: ./doc/common/tables/keystone-token.xml14(th)
-#: ./doc/common/tables/neutron-vpn.xml14(th)
-#: ./doc/common/tables/neutron-agent.xml14(th)
-#: ./doc/common/tables/neutron-ryu.xml14(th)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml13(th)
-#: ./doc/common/tables/trove-db_couchbase.xml14(th)
-#: ./doc/common/tables/neutron-policy.xml14(th)
-#: ./doc/common/tables/neutron-rootwrap.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml13(th)
-#: ./doc/common/tables/trove-common.xml14(th)
-#: ./doc/common/tables/cinder-ssl.xml14(th)
-#: ./doc/common/tables/heat-api.xml14(th)
-#: ./doc/common/tables/trove-db_percona.xml14(th)
-#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml13(th)
-#: ./doc/common/tables/ceilometer-amqp.xml14(th)
-#: ./doc/common/tables/keystone-auth_token.xml14(th)
-#: ./doc/common/tables/neutron-meta.xml14(th)
-#: ./doc/common/tables/neutron-redis.xml14(th)
-#: ./doc/common/tables/neutron-ssl.xml14(th)
-#: ./doc/common/tables/ceilometer-exchange.xml14(th)
-#: ./doc/common/tables/ceilometer-common.xml14(th)
-#: ./doc/common/tables/ceilometer-alarm.xml14(th)
-#: ./doc/common/tables/keystone-misc.xml14(th)
-#: ./doc/common/tables/nova-scheduling.xml14(th)
-#: ./doc/common/tables/ceilometer-auth.xml14(th)
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml13(th)
-#: ./doc/common/tables/neutron-ml2_mlnx.xml14(th)
-#: ./doc/common/tables/swift-container-server-filter-recon.xml13(th)
-#: ./doc/common/tables/trove-dns.xml14(th)
-#: ./doc/common/tables/neutron-db.xml14(th)
-#: ./doc/common/tables/neutron-ml2_brocade.xml14(th)
-#: ./doc/common/tables/neutron-brocade.xml14(th)
-#: ./doc/common/tables/keystone-redis.xml14(th)
-#: ./doc/common/tables/heat-auth_token.xml14(th)
-#: ./doc/common/tables/keystone-database.xml14(th)
-#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml13(th)
-#: ./doc/common/tables/heat-clients_neutron.xml14(th)
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml14(th)
-#: ./doc/common/tables/cinder-xiv.xml14(th)
-#: ./doc/common/tables/cinder-hds-hus.xml14(th)
-#: ./doc/common/tables/neutron-rabbitmq.xml14(th)
-#: ./doc/common/tables/keystone-kvs.xml14(th)
-#: ./doc/common/tables/trove-ssl.xml14(th)
-#: ./doc/common/tables/keystone-policy.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml13(th)
-#: ./doc/common/tables/swift-swift-swift-hash.xml13(th)
-#: ./doc/common/tables/cinder-auth.xml14(th)
-#: ./doc/common/tables/nova-kombu.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml13(th)
-#: ./doc/common/tables/neutron-ml2_odl.xml14(th)
-#: ./doc/common/tables/heat-quota.xml14(th)
-#: ./doc/common/tables/nova-spice.xml14(th)
-#: ./doc/common/tables/cinder-zoning_fabric.xml14(th)
-#: ./doc/common/tables/neutron-midonet.xml14(th)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml13(th)
+#: ./doc/common/tables/nova-authentication.xml14(th)
 #: ./doc/common/tables/neutron-nvsd.xml14(th)
-#: ./doc/common/tables/neutron-embrane_lb.xml14(th)
-#: ./doc/common/tables/neutron-auth_token.xml14(th)
-#: ./doc/common/tables/cinder-storwize.xml14(th)
-#: ./doc/common/tables/nova-rootwrap.xml14(th)
-#: ./doc/common/tables/cinder-solidfire.xml14(th)
-#: ./doc/common/tables/keystone-revoke.xml14(th)
-#: ./doc/common/tables/glance-ssl.xml14(th)
-#: ./doc/common/tables/heat-metadata_api.xml14(th)
-#: ./doc/common/tables/nova-apiv3.xml14(th)
-#: ./doc/common/tables/glance-db.xml14(th)
-#: ./doc/common/tables/neutron-vmware.xml14(th)
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml13(th)
-#: ./doc/common/tables/nova-api.xml14(th)
-#: ./doc/common/tables/glance-matchmaker.xml14(th)
-#: ./doc/common/tables/keystone-ssl.xml14(th)
-#: ./doc/common/tables/swift-rsyncd-container.xml13(th)
-#: ./doc/common/tables/cinder-san-solaris.xml14(th)
-#: ./doc/common/tables/trove-heat.xml14(th)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml14(th)
-#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml13(th)
-#: ./doc/common/tables/glance-paste.xml14(th)
-#: ./doc/common/tables/nova-rdp.xml14(th)
-#: ./doc/common/tables/neutron-quotas.xml14(th)
-#: ./doc/common/tables/nova-rpc.xml14(th)
-#: ./doc/common/tables/trove-guestagent.xml14(th)
-#: ./doc/common/tables/nova-baremetal.xml14(th)
-#: ./doc/common/tables/heat-clients_keystone.xml14(th)
 #: ./doc/common/tables/swift-account-server-pipeline-main.xml13(th)
-#: ./doc/common/tables/keystone-rabbit.xml14(th)
-#: ./doc/common/tables/glance-api.xml14(th)
-#: ./doc/common/tables/cinder-scheduler.xml14(th)
-#: ./doc/common/tables/keystone-api.xml14(th)
-#: ./doc/common/tables/neutron-ml2_ncs.xml14(th)
-#: ./doc/common/tables/neutron-nec.xml14(th)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml14(th)
-#: ./doc/common/tables/neutron-cadf.xml14(th)
-#: ./doc/common/tables/neutron-testing.xml14(th)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml13(th)
-#: ./doc/common/tables/glance-cinder.xml14(th)
-#: ./doc/common/tables/nova-redis.xml14(th)
-#: ./doc/common/tables/neutron-embrane.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml13(th)
-#: ./doc/common/tables/nova-upgrade_levels.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml13(th)
-#: ./doc/common/tables/ceilometer-inspector.xml14(th)
-#: ./doc/common/tables/nova-rabbitmq.xml14(th)
-#: ./doc/common/tables/heat-common.xml14(th)
+#: ./doc/common/tables/glance-gridfs.xml14(th)
+#: ./doc/common/tables/neutron-notifier.xml14(th)
+#: ./doc/common/tables/nova-rpc_all.xml14(th)
+#: ./doc/common/tables/neutron-hyperv_agent.xml14(th)
 #: ./doc/common/tables/keystone-federation.xml14(th)
-#: ./doc/common/tables/cinder-zadara.xml14(th)
-#: ./doc/common/tables/neutron-nuage.xml14(th)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml13(th)
-#: ./doc/common/tables/ceilometer-ssl.xml14(th)
-#: ./doc/common/tables/nova-quota.xml14(th)
-#: ./doc/common/tables/nova-conductor.xml14(th)
-#: ./doc/common/tables/nova-compute.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml13(th)
-#: ./doc/common/tables/cinder-storage_xen.xml14(th)
+#: ./doc/common/tables/nova-scheduling.xml14(th)
+#: ./doc/common/tables/cinder-ssl.xml14(th)
+#: ./doc/common/tables/trove-ssl.xml14(th)
+#: ./doc/common/tables/cinder-eqlx.xml14(th)
+#: ./doc/common/tables/heat-redis.xml14(th)
+#: ./doc/common/tables/nova-ec2.xml14(th)
 #: ./doc/common/tables/keystone-credential.xml14(th)
-#: ./doc/common/tables/trove-amqp.xml14(th)
+#: ./doc/common/tables/cinder-block-device.xml14(th)
+#: ./doc/common/tables/neutron-metadata.xml14(th)
+#: ./doc/common/tables/nova-fping.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml13(th)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml13(th)
+#: ./doc/common/tables/neutron-ml2_ncs.xml14(th)
+#: ./doc/common/tables/neutron-ml2_arista.xml14(th)
+#: ./doc/common/tables/nova-trustedcomputing.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml13(th)
+#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml13(th)
+#: ./doc/common/tables/neutron-compute.xml14(th)
+#: ./doc/common/tables/glance-imagecache.xml14(th)
+#: ./doc/common/tables/neutron-ml2_brocade.xml14(th)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml13(th)
+#: ./doc/common/tables/cinder-nas.xml14(th)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml14(th)
+#: ./doc/common/tables/heat-clients_swift.xml14(th)
+#: ./doc/common/tables/keystone-logging.xml14(th)
+#: ./doc/common/tables/neutron-brocade.xml14(th)
+#: ./doc/common/tables/neutron-ml2_odl.xml14(th)
+#: ./doc/common/tables/swift-object-server-filter-recon.xml13(th)
+#: ./doc/common/tables/cinder-connection.xml14(th)
+#: ./doc/common/tables/heat-rpc.xml14(th)
+#: ./doc/common/tables/trove-taskmanager.xml14(th)
+#: ./doc/common/tables/heat-cloudwatch_api.xml14(th)
+#: ./doc/common/tables/cinder-images.xml14(th)
+#: ./doc/common/tables/cinder-huawei.xml14(th)
+#: ./doc/common/tables/nova-console.xml14(th)
+#: ./doc/common/tables/neutron-fwaas.xml14(th)
+#: ./doc/common/tables/cinder-nexenta_nfs.xml14(th)
+#: ./doc/common/tables/nova-quota.xml14(th)
+#: ./doc/common/tables/heat-logging.xml14(th)
+#: ./doc/common/tables/trove-redis.xml14(th)
+#: ./doc/common/tables/keystone-stats.xml14(th)
+#: ./doc/common/tables/heat-crypt.xml14(th)
+#: ./doc/common/tables/neutron-ssl.xml14(th)
+#: ./doc/common/tables/neutron-midonet.xml14(th)
+#: ./doc/common/tables/cinder-coraid.xml14(th)
+#: ./doc/common/tables/neutron-wsgi.xml14(th)
+#: ./doc/common/tables/cinder-compute.xml14(th)
+#: ./doc/common/tables/swift-rsyncd-object.xml13(th)
+#: ./doc/common/tables/glance-wsgi.xml14(th)
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml13(th)
+#: ./doc/common/tables/nova-baremetal.xml14(th)
+#: ./doc/common/tables/neutron-qpid.xml14(th)
+#: ./doc/common/tables/nova-rpc.xml14(th)
+#: ./doc/common/tables/cinder-backups_tsm.xml14(th)
+#: ./doc/common/tables/cinder-san.xml14(th)
+#: ./doc/common/tables/nova-logging.xml14(th)
+#: ./doc/common/tables/neutron-nec.xml14(th)
+#: ./doc/common/tables/keystone-security.xml14(th)
+#: ./doc/common/tables/heat-clients_neutron.xml14(th)
+#: ./doc/common/tables/nova-api.xml14(th)
+#: ./doc/common/tables/neutron-ml2_mlnx.xml14(th)
+#: ./doc/common/tables/trove-auth_token.xml14(th)
+#: ./doc/common/tables/keystone-trust.xml14(th)
+#: ./doc/common/tables/glance-cinder.xml14(th)
+#: ./doc/common/tables/swift-object-server-object-updater.xml13(th)
+#: ./doc/common/tables/glance-common.xml14(th)
+#: ./doc/common/tables/neutron-ml2_vxlan.xml14(th)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml13(th)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml13(th)
+#: ./doc/common/tables/trove-nova.xml14(th)
+#: ./doc/common/tables/neutron-meta.xml14(th)
+#: ./doc/common/tables/neutron-rabbitmq.xml14(th)
+#: ./doc/common/tables/keystone-ec2.xml14(th)
+#: ./doc/common/tables/heat-clients_keystone.xml14(th)
+#: ./doc/common/tables/neutron-api.xml14(th)
+#: ./doc/common/tables/trove-logging.xml14(th)
+#: ./doc/common/tables/glance-db.xml14(th)
+#: ./doc/common/tables/keystone-kvs.xml14(th)
+#: ./doc/common/tables/keystone-redis.xml14(th)
 #: ./doc/common/tables/nova-xvpnvncproxy.xml14(th)
+#: ./doc/common/tables/glance-paste.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml13(th)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml13(th)
+#: ./doc/common/tables/nova-hyperv.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml13(th)
+#: ./doc/common/tables/heat-clients_backends.xml14(th)
+#: ./doc/common/tables/glance-testing.xml14(th)
+#: ./doc/common/tables/neutron-common.xml14(th)
+#: ./doc/common/tables/nova-hypervisor.xml14(th)
+#: ./doc/common/tables/keystone-qpid.xml14(th)
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml13(th)
+#: ./doc/common/tables/nova-wsgi.xml14(th)
+#: ./doc/common/tables/keystone-cache.xml14(th)
+#: ./doc/common/tables/nova-configdrive.xml14(th)
+#: ./doc/common/tables/keystone-token.xml14(th)
+#: ./doc/common/tables/ceilometer-ssl.xml14(th)
+#: ./doc/common/tables/ceilometer-qpid.xml14(th)
+#: ./doc/common/tables/heat-database.xml14(th)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml14(th)
+#: ./doc/common/tables/neutron-ml2.xml14(th)
+#: ./doc/common/tables/neutron-db.xml14(th)
+#: ./doc/common/tables/keystone-database.xml14(th)
+#: ./doc/common/tables/keystone-memcache.xml14(th)
+#: ./doc/common/tables/trove-debug.xml14(th)
+#: ./doc/common/tables/trove-swift.xml14(th)
+#: ./doc/common/tables/nova-tilera.xml14(th)
+#: ./doc/common/tables/nova-libvirt.xml14(th)
+#: ./doc/common/tables/neutron-mlnx.xml14(th)
+#: ./doc/common/tables/cinder-zoning_manager.xml14(th)
+#: ./doc/common/tables/ceilometer-amqp.xml14(th)
+#: ./doc/common/tables/glance-ssl.xml14(th)
+#: ./doc/common/tables/neutron-securitygroups.xml14(th)
+#: ./doc/common/tables/keystone-debug.xml14(th)
+#: ./doc/common/tables/cinder-rootwrap.xml14(th)
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml14(th)
 msgid "Description"
 msgstr "Description"
 
@@ -5650,13 +4720,13 @@ msgstr ""
 #: ./doc/common/section_cli_nova_quotas.xml249(para)
 #: ./doc/common/section_cli_nova_quotas.xml292(para)
 #: ./doc/common/section_cli_nova_quotas.xml324(para)
-#: ./doc/common/section_cli_keystone_services.xml100(para)
-#: ./doc/common/section_cli_nova_boot_from_volume.xml190(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml82(para)
 #: ./doc/common/section_keystone_certificates-for-pki.xml180(para)
+#: ./doc/common/section_cli_nova_boot_from_volume.xml190(para)
 #: ./doc/common/section_cli_cinder_manage_volumes.xml335(para)
 #: ./doc/common/section_cli_cinder_manage_volumes.xml349(para)
 #: ./doc/common/section_cli_cinder_manage_volumes.xml393(para)
-#: ./doc/common/section_objectstorage-ringbuilder.xml82(para)
+#: ./doc/common/section_cli_keystone_services.xml100(para)
 msgid "For example:"
 msgstr "Par exemple :"
 
@@ -5754,1036 +4824,530 @@ msgstr ""
 msgid "To update quota values for a tenant user"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-intro.xml7(title)
-#: ./doc/common/section_about-object-storage.xml7(title)
-msgid "Introduction to Object Storage"
-msgstr "Introduction au Stockage d'Objets"
+#: ./doc/common/section_cli_nova_boot.xml6(title)
+msgid "Launch instances"
+msgstr "Lancer les instances"
 
-#: ./doc/common/section_objectstorage-intro.xml8(para)
+#: ./doc/common/section_cli_nova_boot.xml7(para)
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml8(para)
+msgid "Instances are virtual machines that run inside the cloud."
+msgstr "Les instances sont des machines virtuelles individuelles qui tournent dans le cloud."
+
+#: ./doc/common/section_cli_nova_boot.xml9(para)
+msgid "Before you can launch an instance, gather the following parameters:"
+msgstr "Avant de lancer une instance, ramassez les paramètres suivants:"
+
+#: ./doc/common/section_cli_nova_boot.xml13(para)
 msgid ""
-"OpenStack Object Storage (code-named swift) is open source software for "
-"creating redundant, scalable data storage using clusters of standardized "
-"servers to store petabytes of accessible data. It is a long-term storage "
-"system for large amounts of static data that can be retrieved, leveraged, "
-"and updated. Object Storage uses a distributed architecture with no central "
-"point of control, providing greater scalability, redundancy, and permanence."
-" Objects are written to multiple hardware devices, with the OpenStack "
-"software responsible for ensuring data replication and integrity across the "
-"cluster. Storage clusters scale horizontally by adding new nodes. Should a "
-"node fail, OpenStack works to replicate its content from other active nodes."
-" Because OpenStack uses software logic to ensure data replication and "
-"distribution across different devices, inexpensive commodity hard drives and"
-" servers can be used in lieu of more expensive equipment."
+"The <emphasis role=\"bold\">instance source</emphasis> can be an image, "
+"snapshot, or block storage volume that contains an image or snapshot."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-intro.xml19(para)
+#: ./doc/common/section_cli_nova_boot.xml18(para)
+msgid "A <emphasis role=\"bold\">name</emphasis> for your instance."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot.xml21(para)
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml37(para)
 msgid ""
-"Object Storage is ideal for cost effective, scale-out storage. It provides a"
-" fully distributed, API-accessible storage platform that can be integrated "
-"directly into applications or used for backup, archiving, and data "
-"retention."
+"The <emphasis role=\"bold\">flavor</emphasis> for your instance, which "
+"defines the compute, memory, and storage capacity of nova computing "
+"instances. A flavor is an available hardware configuration for a server. It "
+"defines the size of a virtual server that can be launched."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml6(title)
-msgid "Set up credentials for the keystone client"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_credentials.xml7(para)
+#: ./doc/common/section_cli_nova_boot.xml29(para)
 msgid ""
-"You can configure the <package>python-keystoneclient</package> with admin "
-"credentials with either an authentication token or a user name and password."
+"Any <emphasis role=\"bold\">user data</emphasis> files. A user data file is "
+"a special key in the metadata service that holds a file that cloud-aware "
+"applications in the guest instance can access. For example, one application "
+"that uses user data is the <link "
+"href=\"https://help.ubuntu.com/community/CloudInit\">cloud-init</link> "
+"system, which is an open-source package from Ubuntu that is available on "
+"various Linux distributions and that handles early initialization of a cloud"
+" instance."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml12(title)
-msgid "To configure the keystone client with an authentication token"
-msgstr "Pour configurer le client keystone avec un jeton d'authentification"
-
-#: ./doc/common/section_cli_keystone_credentials.xml15(para)
+#: ./doc/common/section_cli_nova_boot.xml42(para)
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml45(para)
 msgid ""
-"Export your keystone endpoint to the <varname>OS_SERVICE_ENDPOINT</varname> "
-"environment variable:"
+"Access and security credentials, which include one or both of the following "
+"credentials:"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml21(para)
+#: ./doc/common/section_cli_nova_boot.xml46(para)
 msgid ""
-"Export the administrator service token to the "
-"<varname>OS_SERVICE_TOKEN</varname> environment variable:"
+"A <emphasis role=\"bold\">key pair</emphasis> for your instance, which are "
+"SSH credentials that are injected into images when they are launched. For "
+"the key pair to be successfully injected, the image must contain the "
+"<literal>cloud-init</literal> package. Create at least one key pair for each"
+" project. If you already have generated a key pair with an external tool, "
+"you can import it into OpenStack. You can use the key pair for multiple "
+"instances that belong to that project."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml26(para)
-#: ./doc/common/section_cli_keystone_credentials.xml80(para)
+#: ./doc/common/section_cli_nova_boot.xml60(para)
 msgid ""
-"Alternatively, you can specify these parameters on any keystone client "
-"command:"
-msgstr "Alternativement, vous pouvez spécifier ces paramètres sur un client de commande keystone:"
+"A <emphasis role=\"bold\">security group</emphasis> that defines which "
+"incoming network traffic is forwarded to instances. Security groups hold a "
+"set of firewall policies, known as <emphasis role=\"italic\">security group "
+"rules</emphasis>."
+msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml30(para)
+#: ./doc/common/section_cli_nova_boot.xml71(para)
 msgid ""
-"<parameter>--os-endpoint "
-"<replaceable>SERVICE_ENDPOINT</replaceable></parameter>. An endpoint to use "
-"instead of the one in the service catalog. Defaults to "
-"<code>env[OS_SERVICE_ENDPOINT]</code>."
+"If needed, you can assign a <emphasis role=\"bold\">floating (public) IP "
+"address</emphasis> to a running instance."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml39(para)
+#: ./doc/common/section_cli_nova_boot.xml76(para)
 msgid ""
-"<parameter>--os-token <replaceable>SERVICE_TOKEN</replaceable></parameter>. "
-"An existing token to use instead of the one generated by authentication. "
-"Defaults to <code>env[OS_SERVICE_TOKEN]</code>."
+"You can also attach a block storage device, or <emphasis "
+"role=\"bold\">volume</emphasis>, for persistent storage."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml52(title)
-msgid "To configure the keystone client with a user name and password"
-msgstr "Pour configurer le client keystone avec un nom d'utilisateur et un mot de passe"
-
-#: ./doc/common/section_cli_keystone_credentials.xml55(para)
+#: ./doc/common/section_cli_nova_boot.xml82(para)
 msgid ""
-"Export the administrator user name to the <varname>OS_USERNAME</varname> "
-"environment variable:"
+"Instances that use the default security group cannot, by default, be "
+"accessed from any IP address outside of the cloud. If you want those IP "
+"addresses to access the instances, you must modify the rules for the default"
+" security group."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml61(para)
+#: ./doc/common/section_cli_nova_boot.xml87(para)
 msgid ""
-"Export the administrator password to the <varname>OS_PASSWORD</varname> "
-"environment variable:"
+"You can also assign a floating IP address to a running instance to make it "
+"accessible from outside the cloud. See <xref "
+"linkend=\"manage_ip_addresses\"/>."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml67(para)
+#: ./doc/common/section_cli_nova_boot.xml91(para)
 msgid ""
-"Export the tenant name to the <varname>OS_TENANT_NAME</varname> environment "
-"variable:"
+"After you gather the parameters that you need to launch an instance, you can"
+" launch it from an <link linkend=\"launch_from_image\">image</link> or a "
+"<link linkend=\"boot_from_volume\">volume</link>. You can launch an instance"
+" directly from one of the available OpenStack images or from an image that "
+"you have copied to a persistent volume. The OpenStack Image Service provides"
+" a pool of images that are accessible to members of different projects."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml73(para)
+#: ./doc/common/section_cli_nova_boot.xml101(title)
+msgid "Gather parameters to launch an instance"
+msgstr "Pour lancer une instance, ramassez les paramètres"
+
+#: ./doc/common/section_cli_nova_boot.xml103(para)
+msgid "Before you begin, source the OpenStack RC file."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot.xml106(para)
+#: ./doc/common/section_cli_nova_boot_from_volume.xml169(para)
+msgid "List the available flavors:"
+msgstr "Listez les types d'instances disponibles:"
+
+#: ./doc/common/section_cli_nova_boot.xml108(para)
+msgid "Note the ID of the flavor that you want to use for your instance:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot.xml121(para)
+#: ./doc/common/section_cli_nova_boot_from_volume.xml155(para)
+msgid "List the available images:"
+msgstr "Lister les images disponibles:"
+
+#: ./doc/common/section_cli_nova_boot.xml123(para)
+msgid "Note the ID of the image from which you want to boot your instance:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot.xml131(para)
 msgid ""
-"Export the URL of the keystone auth server, for example <link "
-"href=\"http://localhost:5000/v2.0'\">http://localhost:5000/v2.0'</link>, to "
-"the <varname>OS_AUTH_URL</varname> environment variable:"
+"You can also filter the image list by using <placeholder-1/> to find a "
+"specific image, as follows:"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml84(para)
+#: ./doc/common/section_cli_nova_boot.xml138(para)
+msgid "List the available security groups:"
+msgstr "Listez les groupes de sécurité disponibles:"
+
+#: ./doc/common/section_cli_nova_boot.xml140(para)
 msgid ""
-"<literal>--os-username <replaceable>OS_USERNAME</replaceable></literal>. "
-"Name used for authentication with the Identity Service. Defaults to "
-"<code>env[OS_USERNAME]</code>."
+"If you are an admin user, specify the <option>--all-tenants</option> "
+"parameter to list groups for all tenants."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml92(para)
+#: ./doc/common/section_cli_nova_boot.xml145(para)
 msgid ""
-"<literal>--os-password <replaceable>OS_PASSWORD</replaceable></literal>. "
-"Password used for authentication with the Identity Service. Defaults to "
-"<code>env[OS_PASSWORD]</code>."
+"Note the ID of the security group that you want to use for your instance:"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml100(para)
+#: ./doc/common/section_cli_nova_boot.xml151(para)
 msgid ""
-"<literal>--os-tenant_name "
-"<replaceable>OS_TENANT_NAME</replaceable></literal>. Tenant for which to "
-"request authentication. Defaults to <code>env[OS_TENANT_NAME]</code>."
+"If you have not created any security groups, you can assign the instance to "
+"only the default security group."
+msgstr "Si vous n'avez pas créer de groupe de sécurité, vous ne pourrez qu'assigner l'instance au groupe de sécurité par défaut."
+
+#: ./doc/common/section_cli_nova_boot.xml154(para)
+msgid "You can view rules for a specified security group:"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml108(para)
+#: ./doc/common/section_cli_nova_boot.xml159(para)
 msgid ""
-"<literal>--os-auth_url <replaceable>OS_AUTH_URL</replaceable></literal>. The"
-" Identity Service endpoint to use for authentication. Defaults to "
-"<code>env[OS_AUTH_URL]</code>."
+"List the available key pairs and note the name of the key pair that you use "
+"for SSH access."
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml6(title)
-msgid "Use the VNC console"
-msgstr ""
+#: ./doc/common/section_cli_nova_boot.xml168(title)
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml6(title)
+msgid "Launch an instance from an image"
+msgstr "Lancer une instance depuis une image"
 
-#: ./doc/common/section_using-vnc-console.xml7(para)
+#: ./doc/common/section_cli_nova_boot.xml171(para)
 msgid ""
-"To interact through the VNC console, you can use a VNC client directly, a "
-"special Java client, or a web browser. For information about how to "
-"configure the console, see <xref linkend=\"installing-openstack-"
-"dashboard\"/>."
+"After you gather required parameters, run the following command to launch an"
+" instance. Specify the server name, flavor ID, and image ID."
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml15(title)
-msgid "Get an access URL"
-msgstr "obtenez une URL d’accès :"
-
-#: ./doc/common/section_using-vnc-console.xml16(para)
+#: ./doc/common/section_cli_nova_boot.xml174(para)
 msgid ""
-"The Compute service enables you to create access_urls through the os-"
-"consoles extension. Support for accessing this URL is provided by the nova "
-"client:"
+"Optionally, you can provide a key name for access control and a security "
+"group for security. You can also include metadata key and value pairs. For "
+"example, you can add a description for your server by providing the "
+"<parameter>--meta description=\"My Server\"</parameter> parameter."
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml19(replaceable)
-#: ./doc/common/section_using-vnc-console.xml25(replaceable)
-#: ./doc/common/section_using-vnc-console.xml52(replaceable)
-#: ./doc/common/section_using-vnc-console.xml65(replaceable)
-msgid "[server_id]"
-msgstr "[server_id]"
-
-#: ./doc/common/section_using-vnc-console.xml19(replaceable)
-msgid "[novnc|xvpvnc]"
-msgstr "[novnc|xvpvnc]"
-
-#: ./doc/common/section_using-vnc-console.xml20(para)
+#: ./doc/common/section_cli_nova_boot.xml181(para)
 msgid ""
-"Specify '<literal>novnc</literal>' to get a URL suitable for pasting into a "
-"web browser."
+"You can pass user data in a local file at instance launch by using the "
+"<parameter>--user-data <replaceable>USER-DATA-FILE</replaceable></parameter>"
+" parameter."
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml22(para)
+#: ./doc/common/section_cli_nova_boot.xml186(replaceable)
+msgid "FLAVOR_ID"
+msgstr "FLAVOR_ID"
+
+#: ./doc/common/section_cli_nova_boot.xml186(replaceable)
+#: ./doc/common/section_cli_nova_boot_from_volume.xml329(replaceable)
+msgid "IMAGE_ID"
+msgstr "IMAGE_ID"
+
+#: ./doc/common/section_cli_nova_boot.xml186(replaceable)
+msgid "KEY_NAME"
+msgstr "KEY_NAME"
+
+#: ./doc/common/section_cli_nova_boot.xml187(replaceable)
+msgid "USER_DATA_FILE"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot.xml187(replaceable)
+msgid "SEC_GROUP"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot.xml187(replaceable)
+msgid "KEY=VALUE"
+msgstr "KEY=VALUE"
+
+#: ./doc/common/section_cli_nova_boot.xml188(replaceable)
+#: ./doc/common/section_cli_nova_startstop.xml14(replaceable)
+#: ./doc/common/section_cli_nova_startstop.xml18(replaceable)
+#: ./doc/common/section_cli_nova_startstop.xml35(replaceable)
+#: ./doc/common/section_cli_nova_startstop.xml40(replaceable)
+#: ./doc/common/section_cli_nova_get_console.xml8(replaceable)
+msgid "INSTANCE_NAME"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot.xml189(para)
 msgid ""
-"Specify '<literal>xvpvnc</literal>' for a URL suitable for pasting into the "
-"Java client."
+"The following command launches the <literal>MyCirrosServer</literal> "
+"instance with the <literal>m1.small</literal> flavor (ID of "
+"<literal>1</literal>), <literal>cirros-0.3.2-x86_64-uec</literal> image (ID "
+"of <literal>397e713c-b95b-4186-ad46-6126863ea0a9</literal>), "
+"<literal>default</literal> security group, <literal>KeyPair01</literal> key,"
+" and a user data file called <filename>cloudinit.file</filename>:"
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml24(para)
-msgid "To request a web browser URL:"
-msgstr "Pour demander une URL de navigateur web:"
-
-#: ./doc/common/section_using-vnc-console.xml28(title)
-msgid "Access a VNC console with a Java client"
+#: ./doc/common/section_cli_nova_boot.xml202(replaceable)
+msgid "myCirrosServer"
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml29(para)
+#: ./doc/common/section_cli_nova_boot.xml203(para)
 msgid ""
-"To enable support for the OpenStack Java VNC client in compute, run the "
-"<literal>nova-xvpvncproxy</literal> service."
+"Depending on the parameters that you provide, the command returns a list of "
+"server properties."
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml34(para)
+#: ./doc/common/section_cli_nova_boot.xml206(para)
 msgid ""
-"<literal>xvpvncproxy_port</literal>=<replaceable>[port]</replaceable> - port"
-" to bind (defaults to 6081)"
-msgstr "<literal>xvpvncproxy_port</literal>=<replaceable>[port]</replaceable> - port  à attacher (par défaut à 6081)"
+"A status of <literal>BUILD</literal> indicates that the instance has "
+"started, but is not yet online."
+msgstr "L'état <literal>BUILD</literal> indique que l'instance a demarré, mais qu'elle n'est pas en ligne."
 
-#: ./doc/common/section_using-vnc-console.xml38(para)
+#: ./doc/common/section_cli_nova_boot.xml209(para)
 msgid ""
-"<literal>xvpvncproxy_host</literal>=<replaceable>[host]</replaceable> - host"
-" to bind (defaults to 0.0.0.0)"
-msgstr "<literal>xvpvncproxy_host</literal>=<replaceable>[host]</replaceable> - hôte à attacher (par défaut à 0.0.0.0)"
+"A status of <literal>ACTIVE</literal> indicates that the instance is active."
+msgstr "L'état <literal>ACTIVE</literal> indique que l'instance est active."
 
-#: ./doc/common/section_using-vnc-console.xml42(para)
+#: ./doc/common/section_cli_nova_boot.xml241(para)
 msgid ""
-"As a client, you need a special Java client, which is a slightly modified "
-"version of TightVNC that supports our token auth:"
+"Copy the server ID value from the <literal>id</literal> field in the output."
+" You use this ID to get details for or delete your server."
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml48(para)
+#: ./doc/common/section_cli_nova_boot.xml245(para)
 msgid ""
-"To create a session, request an access URL by using <placeholder-1/>. Then, "
-"run the client as follows."
-msgstr "Pour créer une session, demander une URL d'accès en utilisant <placeholder-1/>. Puis exécutez le client comme suit."
-
-#: ./doc/common/section_using-vnc-console.xml51(para)
-msgid "To get an access URL:"
-msgstr "Pour obtenir une URL d'accès:"
-
-#: ./doc/common/section_using-vnc-console.xml53(para)
-msgid "To run the client:"
-msgstr "Accéder aux consoles VNC avec un client Java"
-
-#: ./doc/common/section_using-vnc-console.xml54(replaceable)
-msgid "[access_url]"
-msgstr "[access_url]"
-
-#: ./doc/common/section_using-vnc-console.xml59(title)
-msgid "Access a VNC console with a web browser"
+"Copy the administrative password value from the <literal>adminPass</literal>"
+" field. You use this value to log in to your server."
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml61(para)
+#: ./doc/common/section_cli_nova_boot.xml249(para)
 msgid ""
-"Retrieving an access_url for a web browser is similar to the flow for the "
-"Java client."
-msgstr "Récupérer une URL d’accès pour un navigateur web est similaire à la procédure pour le client Java."
+"You can also place arbitrary local files into the instance file system at "
+"creation time by using the <option>--file &lt;dst-path=src-path&gt;</option>"
+" option. You can store up to five files. For example, if you have a special "
+"authorized keys file named <filename>special_authorized_keysfile</filename> "
+"that you want to put on the instance rather than using the regular SSH key "
+"injection, you can use the <option>--file</option> option as shown in the "
+"following example:"
+msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml63(para)
-msgid "To get the access URL, run the following command:"
-msgstr "Pour obtenir l'URL d'accès, exécutez la commande :"
+#: ./doc/common/section_cli_nova_boot.xml266(para)
+msgid "Check if the instance is online:"
+msgstr "Vérifier que l'instance est en ligne:"
 
-#: ./doc/common/section_using-vnc-console.xml66(para)
-msgid "Paste the URL into your web browser."
-msgstr "Collez l'URL dans votre navigateur web."
-
-#: ./doc/common/section_using-vnc-console.xml68(para)
+#: ./doc/common/section_cli_nova_boot.xml268(para)
 msgid ""
-"Additionally, you can use the OpenStack dashboard, known as horizon, to "
-"access browser-based VNC consoles for instances."
-msgstr "Collez l'URL dans votre navigateur web."
-
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml6(title)
-msgid "Configure tenant-specific image locations with Object Storage"
+"The list shows the ID, name, status, and private (and if assigned, public) "
+"IP addresses for all instances in the project to which you belong:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml14(para)
-msgid "The tenant who owns the image"
-msgstr "Le locataire qui possède l'image"
+#: ./doc/common/section_cli_nova_boot.xml278(para)
+msgid "If the status for the instance is ACTIVE, the instance is online."
+msgstr "Si l'état de l'instance est actif, l'instance est en ligne."
 
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml17(para)
+#: ./doc/common/section_cli_nova_boot.xml280(para)
 msgid ""
-"Tenants that are defined in <option>swift_store_admin_tenants</option> and "
-"that have admin-level accounts"
-msgstr ""
+"To view the available options for the <placeholder-1/> command, run the "
+"following command:"
+msgstr "Pour voir les options disponibles pour la <placeholder-1/> commande, exécutez la commande suivante: "
 
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml8(para)
+#: ./doc/common/section_cli_nova_boot.xml287(para)
 msgid ""
-"For some deployers, it is not ideal to store all images in one place to "
-"enable all tenants and users to access them. You can configure the Image "
-"Service to store image data in tenant-specific image locations. Then, only "
-"the following tenants can use the Image Service to access the created "
-"image:<placeholder-1/>"
+"If you did not provide a key pair, security groups, or rules, you can access"
+" the instance only from inside the cloud through VNC. Even pinging the "
+"instance is not possible."
 msgstr ""
 
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml23(title)
-msgid "To configure tenant-specific image locations"
+#: ./doc/common/section_user-data.xml6(title)
+msgid "Configure instances at boot"
 msgstr ""
 
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml25(para)
+#: ./doc/common/section_user-data.xml7(para)
 msgid ""
-"Configure swift as your <option>default_store</option> in the <filename"
-">glance-api.conf</filename> file."
+"When you boot instances in an OpenStack cloud, you can use user data or "
+"<package>cloud-init</package> to automatically configure instances at boot "
+"time. You might want to install some packages, start services, or manage "
+"your instance by using a Puppet or Chef server."
 msgstr ""
 
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml33(para)
+#: ./doc/common/section_user-data.xml13(title)
+msgid "User data"
+msgstr "Données utilisateur"
+
+#: ./doc/common/section_user-data.xml14(para)
 msgid ""
-"<option>swift_store_multi_tenant</option>. Set to <literal>True</literal> to"
-" enable tenant-specific storage locations. Default is "
-"<literal>False</literal>."
-msgstr ""
+"User data is the mechanism by which a user can pass information contained in"
+" a local file to an instance at launch time. The typical use case is to pass"
+" something like a shell script or a configuration file as user data."
+msgstr "User data est le mécanisme par lequel un utilisateur peut faire passer des informations contenues dans un fichier local à une instance au lancement de celle-ci. Le cas d'utilisation typique est de faire passer quelque chose comme un script shell ou un fichier de configuration en tant que user data."
 
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml39(para)
+#: ./doc/common/section_user-data.xml19(para)
 msgid ""
-"<option>swift_store_admin_tenants</option>. Specify a list of tenant IDs "
-"that can grant read and write access to all Object Storage containers that "
-"are created by the Image Service."
-msgstr ""
+"User data is sent using the <literal>--user-data "
+"<replaceable>/path/to/filename</replaceable></literal> option when calling "
+"<placeholder-1/>. This example creates a text file and sends its contents as"
+" user data to the instance:"
+msgstr "User data est envoyé en utilisant l'option <literal>--user-data <replaceable>/path/to/filename</replaceable></literal> à l'appel de <placeholder-1/>. L'exemple suivant créé un fichier texte et ensuite envoie le contenu de ce fichier en tant que user data à l'instance."
 
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml30(para)
+#: ./doc/common/section_user-data.xml26(para)
 msgid ""
-"Set these configuration options in the <filename>glance-api.conf</filename> "
-"file: <placeholder-1/>"
-msgstr ""
+"The instance can get user data by querying the metadata service through "
+"either the OpenStack metadata API or the EC2 compatibility API:"
+msgstr "L'instance peut retrouver user data en interrogeant le service de métadonnées à utiliser soit l'API de métadonnées OpenStack soit l'API de compatibilité EC2:"
 
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml48(para)
+#: ./doc/common/section_user-data.xml34(para)
 msgid ""
-"With this configuration, images are stored in an Object Storage service "
-"(swift) endpoint that is pulled from the service catalog for the "
-"authenticated user."
+"The Compute service treats user data as a blob. While the previous example "
+"uses a text file, user data can be in any format."
+msgstr "Notez que le service Compute traite user data tel un blob. Tandis que l'exemple ci dessus utilise un fichier texte, user data peut être dans n'importe quel format."
+
+#: ./doc/common/section_user-data.xml38(para)
+msgid "For more information, see <xref linkend=\"config-drive\"/>."
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml11(title)
-msgid "Telemetry command-line client"
-msgstr ""
+#: ./doc/common/section_user-data.xml42(package)
+msgid "cloud-init"
+msgstr "Cloud-init"
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml12(para)
+#: ./doc/common/section_user-data.xml43(para)
 msgid ""
-"The <placeholder-1/> client is the command-line interface (CLI) for the "
-"Telemetry API and its extensions. This chapter documents <placeholder-2/> "
-"version 1.0.10."
-msgstr ""
+"To do something useful with the user data, you must configure the virtual "
+"machine image to run a service on boot that gets user data from the metadata"
+" service and takes some action based on the contents of the data. The "
+"<package>cloud-init</package> package does exactly this. This package is "
+"compatible with the Compute metadata service and the Compute configuration "
+"drive."
+msgstr "Pour faire quelque chose d'utile avec les données utilisateur , l'image de la machine virtuelle doit être configurée pour exécuter un service au lancement qui retrouve les données utilisateur  depuis le service métadonnées et faire quelque actions basées sur le contenu des données. Le paquet <package>cloud-init</package> a été inventé pour faire exactement cela. En particulier, cloud-init est compatible avec le service de métadonnées Compute ainsi que le Compute config drive.."
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml22(title)
-msgid "ceilometer usage"
-msgstr "utilisation de ceilometer"
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml42(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml459(para)
-msgid "Create a new alarm based on state of other alarms."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml50(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml601(para)
-msgid "Update an existing alarm based on state of other alarms."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml59(para)
-msgid "Create a new alarm (Deprecated). Use alarm-threshold- create instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml68(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml746(para)
-msgid "Delete an alarm."
-msgstr "Supprimer une alarme."
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml76(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml763(para)
-msgid "Display the change history of an alarm."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml84(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml790(para)
-msgid "List the user's alarms."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml92(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml809(para)
-msgid "Show an alarm."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml100(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml826(para)
-msgid "Get the state of an alarm."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml108(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml843(para)
-msgid "Set the state of an alarm."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml116(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml884(para)
-msgid "Create a new alarm based on computed statistics."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml124(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1074(para)
-msgid "Update an existing alarm based on computed statistics."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml132(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1279(para)
-msgid "Update an existing alarm (Deprecated)."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml140(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1468(para)
-msgid "List events."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml148(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1487(para)
-msgid "Show a particular event."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml156(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1504(para)
-msgid "List event types."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml164(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1511(para)
-msgid "List the user's meters."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml172(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1531(para)
-msgid "Query Alarm History."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml180(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1567(para)
-msgid "Query Alarms."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml188(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1603(para)
-msgid "Query samples."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml196(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1639(para)
-msgid "List the resources."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml204(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1658(para)
-msgid "Show the resource."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml212(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1681(para)
-msgid "Create a sample."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml220(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1764(para)
-msgid "List the samples for a meter."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml228(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1800(para)
-msgid "List the statistics for a meter."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml236(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1853(para)
-msgid "List trait info for an event type."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml244(para)
-msgid "List trait all traits with name &lt;trait_name&gt; for Event Type"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml253(para)
-#: ./doc/common/ch_cli_keystone_commands.xml324(para)
-#: ./doc/common/ch_cli_heat_commands.xml303(para)
-msgid "Prints all of the commands and options to stdout."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml270(title)
-msgid "ceilometer optional arguments"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml283(para)
-msgid "Defaults to <code>env[CEILOMETERCLIENT_DEBUG]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml291(para)
-#: ./doc/common/ch_cli_heat_commands.xml341(para)
-msgid "Print more verbose output."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml299(para)
+#: ./doc/common/section_user-data.xml51(para)
 msgid ""
-"Explicitly allow ceilometerclient to perform \"insecure\" SSL (https) "
-"requests. The server's certificate will not be verified against any "
-"certificate authorities. This option should be used with caution."
-msgstr ""
+"The <package>cloud-init</package> package supports multiple cloud providers."
+" You can use the same virtual machine image in different clouds without "
+"modification. The <package>cloud-init</package> package is an open source "
+"project and the source code is available on <link "
+"href=\"http://launchpad.net/cloud-init\">Launchpad</link>. It is maintained "
+"by Canonical, the company that runs the Ubuntu project. All Ubuntu cloud "
+"images come pre-installed with <package>cloud-init</package>. However, "
+"<package>cloud-init</package> is not designed to be Ubuntu-specific and has "
+"been successfully ported to several other platforms including Fedora."
+msgstr "Notez que <package>cloud-init</package> n'est pas une technologie OpenStack. Plutôt, il s'agit d'un paquet qui est fait pour supporter plusieurs fournisseurs de cloud, de sorte que la même image de machine virtuelle peut être utilisée dans différents clouds sans modification. <package>cloud-init</package> est un projet open source, et le code source est disponible sur <link href=\"http://launchpad.net/cloud-init\">Launchpad</link>. Il est maintenu par Canonical, L'entreprise qui travaille sur le projet Ubuntu. Toutes les images Ubuntu sont distribuées avec <package>cloud-init</package> pré-installé. Cependant, <package>cloud-init</package> n'est pas fait pour être spécifique à Ubuntu, et a été porté avec succès sur Fedora."
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml311(para)
-#: ./doc/common/ch_cli_glance_commands.xml262(para)
-#: ./doc/common/ch_cli_heat_commands.xml360(para)
+#: ./doc/common/section_user-data.xml66(para)
 msgid ""
-"Path of certificate file to use in SSL connection. This file can optionally "
-"be prepended with the private key."
-msgstr ""
+"Even if you do not use user data to configure instance behavior at boot "
+"time, install <package>cloud-init</package> on images that you create "
+"because this package provides useful functionality. For example, the "
+"<package>cloud-init</package> package enables you to copy the public key to "
+"an account (the <literal>ubuntu</literal> account by default on Ubuntu "
+"instances, the <literal>ec2-user</literal> by default in Fedora instances)."
+msgstr "Nous recommandons d'installer <package>cloud-init</package> sur les images que vous créez pour simplifier la tâche de configuration de vos instances au lancement. Même si vous ne voulez pas utiliser de données utilisateur pour configurer le comportement de l'instance au lancement, <package>cloud-init</package> fournit des fonctionnalités utiles tels que copier la clé public dans un compte (le compte <literal>ubuntu</literal> par défaut sur les instances Ubuntu,le <literal>ec2-user</literal> par défaut dans les instances Fedora)."
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml321(para)
-#: ./doc/common/ch_cli_glance_commands.xml272(para)
+#: ./doc/common/section_user-data.xml75(para)
 msgid ""
-"Path of client key to use in SSL connection. This option is not necessary if"
-" your key is prepended to your cert file."
-msgstr ""
+"If you do not have <package>cloud-init</package> installed, you must "
+"manually configure your image to get the public key from the metadata "
+"service on boot and copy it to the appropriate account."
+msgstr "Si vous n'avez pas installé <package>cloud-init</package>, vous devrez configurer votre image manuellement pour retrouver la clé publique depuis le service métadonnées au lancement et le copier dans le compte approprié."
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml331(para)
+#: ./doc/common/section_user-data.xml81(title)
+msgid "<package>cloud-init</package> supported formats and documentation"
+msgstr "Documentation et formats supportés par <package>cloud-init</package>"
+
+#: ./doc/common/section_user-data.xml83(para)
 msgid ""
-"Path of CA TLS certificate(s) used to verifythe remote server's certificate."
-" Without this option ceilometer looks for the default system CA "
-"certificates."
-msgstr ""
+"Look at the <package>cloud-init</package><link "
+"href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-"
+"init/trunk/view/head:/doc/userdata.txt\">doc/userdata.txt</link> file the "
+"<link href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-"
+"init/trunk/files/head:/doc/examples/\">examples</link> directory and the "
+"<link href=\"https://help.ubuntu.com/community/CloudInit\">Ubuntu community "
+"documentation</link> for details about how to use <package>cloud-"
+"init</package>. Some basic examples are provided here."
+msgstr "Nous recommandons d'aller jeter un œil au fichier <package>cloud-init</package> <link href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/userdata.txt\">doc/userdata.txt</link>, des<link href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/files/head:/doc/examples/\">examples</link> ainsi que la <link href=\"https://help.ubuntu.com/community/CloudInit\">Ubuntu community documentation</link> pour des détails concernant comment utiliser <package>cloud-init</package>. Nous proposons quelques exemples basiques ici."
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml341(para)
-#: ./doc/common/ch_cli_glance_commands.xml292(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use --os-cacert."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml349(para)
-msgid "Number of seconds to wait for a response."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml405(para)
-#: ./doc/common/ch_cli_heat_commands.xml447(para)
-msgid "Defaults to <code>env[OS_AUTH_TOKEN]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml413(para)
-msgid "Defaults to <code>env[CEILOMETER_URL]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml421(para)
-msgid "Defaults to <code>env[CEILOMETER_API_VERSION]</code> or 2."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml429(para)
-#: ./doc/common/ch_cli_heat_commands.xml480(para)
-msgid "Defaults to <code>env[OS_SERVICE_TYPE]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml437(para)
-#: ./doc/common/ch_cli_heat_commands.xml488(para)
-msgid "Defaults to <code>env[OS_ENDPOINT_TYPE]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml445(title)
-msgid "ceilometer alarm-combination-create command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml466(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml891(para)
-msgid "Name of the alarm (must be unique per tenant). Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml475(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml624(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml900(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1097(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1302(para)
-msgid "Tenant to associate with alarm (only settable by admin users)."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml484(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml633(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml909(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1106(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1311(para)
-msgid "User to associate with alarm (only settable by admin users)."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml493(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml642(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml918(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1115(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1320(para)
-msgid "Free text description of the alarm."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml501(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml650(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml926(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1123(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1328(para)
-msgid "State of the alarm, one of: ['ok', 'alarm', 'insufficient_data']"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml510(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml659(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml935(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1132(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1337(para)
-msgid "True if alarm evaluation/actioning is enabled."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml518(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml667(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml943(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1140(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1345(para)
+#: ./doc/common/section_user-data.xml93(para)
 msgid ""
-"URL to invoke when state transitions to alarm. May be used multiple times. "
-"Defaults to None."
+"<package>cloud-init</package> supports several input formats for user data. "
+"Two commonly used formats are:"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml527(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml676(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml952(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1149(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1354(para)
+#: ./doc/common/section_user-data.xml98(para)
+msgid "Shell scripts (starts with <literal>#!</literal>)"
+msgstr "Scripts Shell (<literal>#!</literal>)"
+
+#: ./doc/common/section_user-data.xml102(para)
+msgid "Cloud config files (starts with <literal>#cloud-config</literal>)"
+msgstr "Fichiers de configuration de cloud(commence par <literal>#cloud-config</literal>)"
+
+#: ./doc/common/section_user-data.xml108(title)
+msgid "Run a shell script on boot"
+msgstr "Exécuter un script shell au boot"
+
+#: ./doc/common/section_user-data.xml109(para)
 msgid ""
-"URL to invoke when state transitions to OK. May be used multiple times. "
-"Defaults to None."
-msgstr ""
+"Assuming you have <package>cloud-init</package> installed, the simplest way "
+"to configure an instance on boot is to pass a shell script as user data. The"
+" shell file must begin with <literal>#!</literal> in order for <package"
+">cloud-init</package> to recognize it as a shell script. This example shows "
+"a script that creates a <literal>clouduser</literal> account:"
+msgstr "En supposant que vous avez installé <package>cloud-init</package>, le moyen le plus simple pour configurer une instance durant le boot est de faire passer un script shell en tant que données utilisateur. Le fichier shell doit commencer par <literal>#!</literal> pour que <package>cloud-init</package> le reconnaisse comme script shell. Voici un exemple de script qui créée un compte nommé <literal>clouduser</literal>."
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml536(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml685(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml961(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1158(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1363(para)
+#: ./doc/common/section_user-data.xml118(para)
 msgid ""
-"URL to invoke when state transitions to insufficient_data. May be used "
-"multiple times. Defaults to None."
-msgstr ""
+"Sending a shell script as user data has a similar effect to writing an "
+"<filename>/etc/rc.local</filename> script: it executes very late in the boot"
+" sequence as root."
+msgstr "Envoyer un script shell en tant que données utilisateur a un effet similaire à écrire un script <filename>/etc/rc.local</filename>:il sera exécuté très tard dans la séquence de boot en tant que root."
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml546(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml695(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml971(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1168(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1373(para)
+#: ./doc/common/section_user-data.xml123(title)
+msgid "Cloud-config format"
+msgstr "Format Cloud-config "
+
+#: ./doc/common/section_user-data.xml124(para)
 msgid ""
-"Only evaluate the alarm if the time at evaluation is within this time "
-"constraint. Start point(s) of the constraint are specified with a cron "
-"expression , whereas its duration is given in seconds. Can be specified "
-"multiple times for multiple time constraints, format is: "
-"name=&lt;CONSTRAINT_NAME&gt;;start=&lt; "
-"CRON&gt;;duration=&lt;SECONDS&gt;;[description=&lt;DESCRIPTION&gt;;[t "
-"imezone=&lt;IANA Timezone&gt;]] Defaults to None."
-msgstr ""
+"<package>cloud-init</package> supports a YAML-based config format that "
+"allows the user to configure a large number of options on a system. User "
+"data that begins with <literal>#cloud-config</literal> will be interpreted "
+"by <package>cloud-init</package> as cloud-config format."
+msgstr "<package>cloud-init</package> supporte un format de configuration basé sur YAML qui permet à l'utilisateur de configurer un grand nombre d'options sur un système. Les données utilisateur commençant par <literal>#cloud-config</literal> seront interprétées par <package>cloud-init</package> en tant que format de configuration de cloud."
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml561(para)
-msgid "List of alarm ids. Required."
-msgstr ""
+#: ./doc/common/section_user-data.xml132(title)
+msgid "Example: Set the host name"
+msgstr "<package>cloud-init</package>"
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml569(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml727(para)
-msgid "Operator to compare with, one of: ['and', 'or']."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml577(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1046(para)
+#: ./doc/common/section_user-data.xml133(para)
 msgid ""
-"True if actions should be repeatedly notified while alarm remains in target "
-"state. Defaults to False."
-msgstr ""
+"This <package>cloud-init</package> user data example sets the hostname and "
+"the FQDN, as well as updating <filename>/etc/hosts</filename> on the "
+"instance:"
+msgstr "Cet exemple de données utilisateur <package>cloud-init</package> fixe un nom d'hôte et le FQDN, et met à jour <filename>/etc/hosts</filename> dans l'instance:"
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml586(title)
-msgid "ceilometer alarm-combination-update command"
-msgstr ""
+#: ./doc/common/section_user-data.xml145(title)
+msgid "Example: Configure instances with Puppet"
+msgstr "Exemple: Configurer des instances avec Puppet"
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml608(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1081(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1286(para)
-msgid "ID of the alarm to update. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml616(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1089(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1294(para)
-msgid "Name of the alarm (must be unique per tenant)."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml710(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1183(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1388(para)
-msgid "Name or list of names of the time constraints to remove."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml719(para)
-msgid "List of alarm id."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml735(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1252(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1457(para)
+#: ./doc/common/section_user-data.xml146(para)
 msgid ""
-"True if actions should be repeatedly notified while alarm remains in target "
-"state."
+"This <package>cloud-init</package> user data example, based on <link "
+"href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-"
+"init/trunk/view/head:/doc/examples/cloud-config-puppet.txt\">doc/examples"
+"/cloud-config-puppet.txt</link>, would configure the instance to contact a "
+"Puppet server at puppetmaster.example.org and verify its identity by using a"
+" certificate."
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml744(title)
-msgid "ceilometer alarm-delete command"
-msgstr ""
+#: ./doc/common/section_user-data.xml174(title)
+msgid "Example: Configure instances with Chef"
+msgstr "Exemple : Configurer les instances avec Chef"
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml753(para)
-msgid "ID of the alarm to delete. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml761(title)
-msgid "ceilometer alarm-history command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml770(para)
-msgid "ID of the alarm for which history is shown. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml778(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml797(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1036(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1242(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1518(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1646(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1771(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1807(para)
+#: ./doc/common/section_user-data.xml175(para)
 msgid ""
-"key[op]data_type::value; list. data_type is optional, but if supplied must "
-"be string, integer, float, or boolean."
+"This <package>cloud-init</package> user data example, based on <link "
+"href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-"
+"init/trunk/view/head:/doc/examples/cloud-config-chef.txt\">doc/examples"
+"/cloud-config/chef.txt</link> and intended for use in an Ubuntu image, adds "
+"the Chef apt repository, installs Chef, connects to a Chef server at "
+"<literal>https://chefserver.example.com:4000</literal>, and installs Apache:"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml788(title)
-msgid "ceilometer alarm-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml807(title)
-msgid "ceilometer alarm-show command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml816(para)
-msgid "ID of the alarm to show. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml824(title)
-msgid "ceilometer alarm-state-get command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml833(para)
-msgid "ID of the alarm state to show. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml841(title)
-msgid "ceilometer alarm-state-set command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml850(para)
-msgid "ID of the alarm state to set. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml858(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_getstart_conceptual_arch.xml16(None)
 msgid ""
-"State of the alarm, one of: ['ok', 'alarm', 'insufficient_data']. Required."
+"@@image: 'figures/openstack_havana_conceptual_arch.png'; "
+"md5=96e1d5492d4c865fc9145710bb294a91"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml867(title)
-msgid "ceilometer alarm-threshold-create command"
-msgstr ""
+#: ./doc/common/section_getstart_conceptual_arch.xml6(title)
+msgid "Conceptual architecture"
+msgstr "Principe de l’architecture"
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml986(para)
-msgid "Metric to evaluate against. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml994(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1200(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1397(para)
-msgid "Length of each period (seconds) to evaluate over."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1002(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1208(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1405(para)
-msgid "Number of periods to evaluate over."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1010(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1216(para)
-msgid "Statistic to evaluate, one of: ['max', 'min', 'avg', 'sum', 'count']."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1019(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1225(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1430(para)
+#: ./doc/common/section_getstart_conceptual_arch.xml7(para)
 msgid ""
-"Operator to compare with, one of: ['lt', 'le', 'eq', 'ne', 'ge', 'gt']."
-msgstr ""
+"The following diagram shows the relationships among the OpenStack services:"
+msgstr "Le diagramme suivant montre une vue schématisée et simplifiée de l’architecture d’OpenStack du point de vue de l’utilisateur. "
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml1028(para)
-msgid "Threshold to evaluate against. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1055(title)
-msgid "ceilometer alarm-threshold-update command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1192(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1413(para)
-msgid "Metric to evaluate against."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1234(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1439(para)
-msgid "Threshold to evaluate against."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1261(title)
-msgid "ceilometer alarm-update command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1421(para)
-msgid "Statistic to evaluate, one of: ['max', 'min', 'avg', 'sum', 'count']"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1447(para)
-msgid ""
-"A meter should match this resource metadata (key=value) additionally to the "
-"meter_name. Defaults to None."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1466(title)
-msgid "ceilometer event-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1475(para)
-msgid ""
-"key[op]data_type::value; list. data_type is optional, but if supplied must "
-"be string, integer, floator datetime."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1485(title)
-msgid "ceilometer event-show command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1494(para)
-msgid "The id of the event. Should be a UUID Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1502(title)
-msgid "ceilometer event-type-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1509(title)
-msgid "ceilometer meter-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1528(title)
-msgid "ceilometer query-alarm-history command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1538(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1574(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1610(para)
-msgid ""
-"{complex_op: [{simple_op: {field_name: value}}]} The complex_op is one of: "
-"['and', 'or'], simple_op is one of: ['=', '!=', '&lt;', '&lt;=', '&gt;', "
-"'&gt;=']."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1548(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1584(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1620(para)
-msgid ""
-"[{field_name: direction}, {field_name: direction}] The direction is one of: "
-"['asc', 'desc']."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1557(para)
-msgid "Maximum number of alarm history items to return."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1565(title)
-msgid "ceilometer query-alarms command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1593(para)
-msgid "Maximum number of alarms to return."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1601(title)
-msgid "ceilometer query-samples command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1629(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1789(para)
-msgid "Maximum number of samples to return."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1637(title)
-msgid "ceilometer resource-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1656(title)
-msgid "ceilometer resource-show command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1665(para)
-msgid "ID of the resource to show. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1673(title)
-msgid "ceilometer sample-create command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1688(para)
-msgid "Tenant to associate with sample (only settable by admin users)."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1697(para)
-msgid "User to associate with sample (only settable by admin users)."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1706(para)
-msgid "ID of the resource. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1714(para)
-msgid "The meter name. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1722(para)
-msgid "The meter type. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1730(para)
-msgid "The meter unit. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1738(para)
-msgid "The sample volume. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1746(para)
-msgid "Resource metadata."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1754(para)
-msgid "The sample timestamp."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1762(title)
-msgid "ceilometer sample-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1781(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1817(para)
-msgid "Name of meter to show samples for. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1797(title)
-msgid "ceilometer statistics command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1825(para)
-msgid "Period in seconds over which to group samples."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1833(para)
-msgid "Field for group by."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1841(para)
-msgid ""
-"Function for data aggregation. Available aggregates are: count, cardinality,"
-" min, max, sum, stddev, avg. Defaults to []."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1851(title)
-msgid "ceilometer trait-description-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1860(para)
-msgid "Type of the event for which traits will be shown. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1869(title)
-msgid "ceilometer trait-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1871(para)
-msgid ""
-"List trait all traits with name &lt;trait_name&gt; for Event Type "
-"&lt;event_type&gt;."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1878(para)
-msgid "Type of the event for which traits will listed. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1887(para)
-msgid "The name of the trait to list. Required."
-msgstr ""
-
-#: ./doc/common/section_conventions.xml8(title)
-msgid "Conventions"
-msgstr ""
-
-#: ./doc/common/section_conventions.xml9(para)
-msgid "The OpenStack documentation uses several typesetting conventions."
-msgstr ""
-
-#: ./doc/common/section_conventions.xml13(title)
-msgid "Notices"
-msgstr ""
-
-#: ./doc/common/section_conventions.xml14(para)
-msgid "Notices take three forms:"
-msgstr ""
-
-#: ./doc/common/section_conventions.xml16(para)
-msgid ""
-"The information in a note is usually in the form of a handy tip or reminder."
-msgstr ""
-
-#: ./doc/common/section_conventions.xml20(para)
-msgid ""
-"The information in an important notice is something you must be aware of "
-"before proceeding."
-msgstr ""
-
-#: ./doc/common/section_conventions.xml24(para)
-msgid ""
-"The information in warnings is critical. Warnings provide additional "
-"information about risk of data loss or security issues."
-msgstr ""
-
-#: ./doc/common/section_conventions.xml31(title)
-msgid "Command prompts"
-msgstr ""
-
-#: ./doc/common/section_conventions.xml32(para)
-msgid ""
-"Commands prefixed with the <literal>#</literal> prompt are to be executed by"
-" the <literal>root</literal> user. These examples can also be executed by "
-"using the <placeholder-1/> command, if available."
-msgstr ""
-
-#: ./doc/common/section_conventions.xml36(para)
-msgid ""
-"Commands prefixed with the <literal>$</literal> prompt can be executed by "
-"any user, including <literal>root</literal>."
-msgstr ""
+#: ./doc/common/section_getstart_conceptual_arch.xml11(title)
+msgid "OpenStack conceptual architecture"
+msgstr "Principe de l’architecture de l'OpenStack"
 
 #: ./doc/common/ch_cli_neutron_commands.xml11(title)
 msgid "Networking command-line client"
@@ -9863,457 +8427,800 @@ msgstr ""
 msgid "ID or name of vpnservice to update"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml7(title)
-msgid "Create and manage services and service users"
-msgstr "Créer et gérer des services et des utilisateurs des services"
+#: ./doc/common/section_keystone-concepts-service-management.xml5(title)
+msgid "Service management"
+msgstr "Gestion des services"
 
-#: ./doc/common/section_cli_keystone_services.xml8(para)
-msgid "The Identity Service enables you to define services, as follows:"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_services.xml12(para)
+#: ./doc/common/section_keystone-concepts-service-management.xml6(para)
 msgid ""
-"Service catalog template. The Identity Service acts as a service catalog of "
-"endpoints for other OpenStack services. The "
-"<literal>etc/default_catalog.templates</literal> template file defines the "
-"endpoints for services. When the Identity Service uses a template file back "
-"end, any changes that are made to the endpoints are cached. These changes do"
-" not persist when you restart the service or reboot the machine."
-msgstr ""
+"The Identity Service provides identity, token, catalog, and policy services."
+" It consists of:"
+msgstr "Le service d'identité met à disposition des services d'identité, jeton, catalogue, et politique. Il s'agit de:"
 
-#: ./doc/common/section_cli_keystone_services.xml23(para)
+#: ./doc/common/section_keystone-concepts-service-management.xml11(para)
 msgid ""
-"A SQL back end for the catalog service. When the Identity Service is online,"
-" you must add the services to the catalog. When you deploy a system for "
-"production, use the SQL back end."
-msgstr ""
+"<systemitem class=\"service\">keystone-all</systemitem>. Starts both the "
+"service and administrative APIs in a single process to provide Catalog, "
+"Authorization, and Authentication services for OpenStack."
+msgstr "<systemitem class=\"service\">keystone-all</systemitem>.  Démarre à la fois les APIs administrative et de service dans un processus unique, afin de fournir des services d'annuaire, d'autorisation et d'authentification au sein d'OpenStack."
 
-#: ./doc/common/section_cli_keystone_services.xml29(para)
+#: ./doc/common/section_keystone-concepts-service-management.xml17(para)
 msgid ""
-"The <literal>auth_token</literal> middleware supports the use of either a "
-"shared secret or users for each service."
+"Identity Service functions. Each has a pluggable back end that allows "
+"different ways to use the particular service. Most support standard back "
+"ends like LDAP or SQL."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml32(para)
+#: ./doc/common/section_keystone-concepts-service-management.xml23(para)
 msgid ""
-"To authenticate users against the Identity Service, you must create a "
-"service user for each OpenStack service. For example, create a service user "
-"for the Compute, Block Storage, and Networking services."
-msgstr ""
+"The Identity Service also maintains a user that corresponds to each service,"
+" such as, a user named <emphasis>nova</emphasis> for the Compute service, "
+"and a special service tenant called <emphasis>service</emphasis>."
+msgstr "Le service d'identité conserve également un utilisateur qui correspond à chaque service, par exemple, un utilisateur qui s'appelle <emphasis>nova</emphasis> qui correspond avec le service Calcul, et un locataire de service en particulier qui s'appelle <emphasis>service</emphasis>."
 
-#: ./doc/common/section_cli_keystone_services.xml36(para)
+#: ./doc/common/section_keystone-concepts-service-management.xml28(para)
 msgid ""
-"To configure the OpenStack services with service users, create a project for"
-" all services and create users for each service. Assign the admin role to "
-"each service user and project pair. This role enables users to validate "
-"tokens and authenticate and authorize other user requests."
+"For information about how to create services and endpoints, see the <link "
+"href=\"http://docs.openstack.org/user-guide-"
+"admin/content/index.html\"><citetitle>OpenStack Admin User "
+"Guide</citetitle></link>."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml42(title)
-msgid "Create a service"
-msgstr "Créez un service"
-
-#: ./doc/common/section_cli_keystone_services.xml45(para)
-msgid "List the available services:"
-msgstr "Listez les services disponibles:"
-
-#: ./doc/common/section_cli_keystone_services.xml59(para)
-msgid "To create a service, run this command:"
-msgstr "Pour créer un service, exécutez cette instruction:"
-
-#: ./doc/common/section_cli_keystone_services.xml60(replaceable)
-msgid "service_name"
-msgstr "service_name"
-
-#: ./doc/common/section_cli_keystone_services.xml60(replaceable)
-msgid "service_type"
-msgstr "service_type"
-
-#: ./doc/common/section_cli_keystone_services.xml60(replaceable)
-msgid "service_description"
-msgstr "service_description"
-
-#: ./doc/common/section_cli_keystone_services.xml61(para)
-msgid "The arguments are:"
-msgstr "Les arguments sont:"
-
-#: ./doc/common/section_cli_keystone_services.xml64(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_trusted-compute-pools.xml45(None)
+#: ./doc/common/section_trusted-compute-pools.xml50(None)
 msgid ""
-"<code><replaceable>service_name</replaceable></code>. The unique name of the"
-" new service."
-msgstr "<code><replaceable>service_name</replaceable></code>. Le nom unique de ce nouveau service."
+"@@image: 'figures/OpenStackTrustedComputePool1.png'; "
+"md5=858fbd6148b927723cea5ad2c88d54bd"
+msgstr "@@image: 'figures/OpenStackTrustedComputePool1.png'; md5=858fbd6148b927723cea5ad2c88d54bd"
 
-#: ./doc/common/section_cli_keystone_services.xml68(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_trusted-compute-pools.xml150(None)
+#: ./doc/common/section_trusted-compute-pools.xml155(None)
 msgid ""
-"<code><replaceable>service_type</replaceable></code>. The service type, such"
-" as <code>identity</code>, <code>compute</code>, <code>network</code>, "
-"<code>image</code>, <code>object-store</code> or any other service "
-"identifier string."
+"@@image: 'figures/OpenStackTrustedComputePool2.png'; "
+"md5=077261c595464638c4b3fcc92b6afb9a"
+msgstr "@@image: 'figures/OpenStackTrustedComputePool2.png'; md5=077261c595464638c4b3fcc92b6afb9a"
+
+#: ./doc/common/section_trusted-compute-pools.xml6(title)
+msgid "Trusted compute pools"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml78(para)
+#: ./doc/common/section_trusted-compute-pools.xml7(para)
 msgid ""
-"<code><replaceable>service_description</replaceable></code>. The description"
-" of the service."
+"Trusted compute pools enable administrators to designate a group of compute "
+"hosts as trusted. These hosts use hardware-based security features, such as "
+"the Intel Trusted Execution Technology (TXT), to provide an additional level"
+" of security. Combined with an external stand-alone, web-based remote "
+"attestation server, cloud providers can ensure that the compute node runs "
+"only software with verified measurements and can ensure a secure cloud "
+"stack."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml82(para)
+#: ./doc/common/section_trusted-compute-pools.xml13(para)
 msgid ""
-"For example, to create a <literal>swift</literal> service of type <literal"
-">object-store</literal>, run this command:"
+"Using the trusted compute pools, cloud subscribers can request services to "
+"run on verified compute nodes."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml97(para)
-msgid "To get details for a service, run this command:"
+#: ./doc/common/section_trusted-compute-pools.xml15(para)
+msgid "The remote attestation server performs node verification as follows:"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml99(replaceable)
-msgid "service_ID"
-msgstr "service_ID"
+#: ./doc/common/section_trusted-compute-pools.xml19(para)
+msgid "Compute nodes boot with Intel TXT technology enabled."
+msgstr "Les nœuds de calcul sont amorcés avec la technologie Intel TXT activée."
 
-#: ./doc/common/section_cli_keystone_services.xml114(title)
-msgid "Create service users"
-msgstr "Créer des utilisateurs des services"
+#: ./doc/common/section_trusted-compute-pools.xml23(para)
+msgid "The compute node BIOS, hypervisor, and OS are measured."
+msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml117(para)
+#: ./doc/common/section_trusted-compute-pools.xml27(para)
 msgid ""
-"Create a project for the service users. Typically, this project is named "
-"<literal>service</literal>, but choose any name you like:"
+"Measured data is sent to the attestation server when challenged by the "
+"attestation server."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml122(para)
-msgid "The output shows the ID for the project."
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_services.xml123(para)
+#: ./doc/common/section_trusted-compute-pools.xml31(para)
 msgid ""
-"Make a note of this ID. You need it to create service users and assign "
-"roles."
+"The attestation server verifies those measurements against a good and known "
+"database to determine node trustworthiness."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml135(para)
-msgid "Create service users for the relevant services for your deployment."
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_services.xml139(para)
+#: ./doc/common/section_trusted-compute-pools.xml35(para)
 msgid ""
-"To assign the admin role to the service user-project pairs, run this command"
-" to get the ID of the admin role:"
+"A description of how to set up an attestation service is beyond the scope of"
+" this document. For an open source project that you can use to implement an "
+"attestation service, see the <link "
+"href=\"https://github.com/OpenAttestation/OpenAttestation\">Open "
+"Attestation</link> project."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml155(para)
-msgid "Assign the admin role to the user-project pair:"
+#: ./doc/common/section_trusted-compute-pools.xml54(title)
+msgid "Configure Compute to use trusted compute pools"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml157(replaceable)
-msgid "SERVICE_USER_ID"
-msgstr "SERVICE_USER_ID"
-
-#: ./doc/common/section_cli_keystone_services.xml157(replaceable)
-msgid "ADMIN_ROLE_ID"
-msgstr "ADMIN_ROLE_ID"
-
-#: ./doc/common/section_cli_keystone_services.xml157(replaceable)
-msgid "SERVICE_PROJECT_ID"
-msgstr "SERVICE_PROJECT_ID"
-
-#: ./doc/common/section_cli_keystone_services.xml162(title)
-msgid "Delete a service"
-msgstr "Supprimez un service"
-
-#: ./doc/common/section_cli_keystone_services.xml163(para)
-msgid "To delete a specified service, specify its ID:"
-msgstr "Pour supprimer un service spécifique, préciser son ID:"
-
-#: ./doc/common/section_cli_keystone_services.xml164(replaceable)
-msgid "SERVICE_ID"
-msgstr "SERVICE_ID"
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml10(title)
-msgid "Launch an instance from a volume"
-msgstr "Lancer une instance d'un volume"
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml11(para)
-msgid "You can boot instances from a volume instead of an image."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml12(para)
+#: ./doc/common/section_trusted-compute-pools.xml57(para)
 msgid ""
-"To complete these tasks, use these parameters on the nova <placeholder-1/> "
-"command:"
+"Enable scheduling support for trusted compute pools by adding the following "
+"lines in the <literal>DEFAULT</literal> section in the "
+"<filename>/etc/nova/nova.conf</filename> file:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml20(th)
-msgid "Task"
-msgstr "Tâche"
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml21(th)
-msgid "nova boot parameter"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml22(th)
-msgid "See"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml27(td)
-msgid "Boot an instance from an image and attach a non-bootable volume."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml29(parameter)
-#: ./doc/common/section_cli_nova_boot_from_volume.xml35(parameter)
-#: ./doc/common/section_cli_nova_boot_from_volume.xml41(parameter)
-msgid "--block-device"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml33(td)
-msgid "Create a volume from an image and boot an instance from that volume."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml39(td)
-msgid "Boot from an existing source image, volume, or snapshot."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml45(td)
-msgid "Attach a swap disk to an instance."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml47(parameter)
-msgid "--swap"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml51(td)
-msgid "Attach an ephemeral disk to an instance."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml52(parameter)
-msgid "--ephemeral"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml58(para)
+#: ./doc/common/section_trusted-compute-pools.xml66(para)
 msgid ""
-"To attach a volume to a running instance, see <xref "
-"linkend=\"cli_attach_volume\"/>."
+"Specify the connection information for your attestation service by adding "
+"the following lines to the <literal>trusted_computing</literal> section in "
+"the <filename>/etc/nova/nova.conf</filename> file:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml62(title)
-msgid "Boot instance from image and attach non-bootable volume"
+#: ./doc/common/section_trusted-compute-pools.xml78(para)
+#: ./doc/common/section_cli_nova_customize_flavors.xml260(para)
+#: ./doc/common/section_keystone_config_ldap-hardening.xml83(para)
+msgid "Where:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml64(para)
+#: ./doc/common/section_trusted-compute-pools.xml81(term)
+msgid "server"
+msgstr "server"
+
+#: ./doc/common/section_trusted-compute-pools.xml83(para)
+msgid "Host name or IP address of the host that runs the attestation service."
+msgstr ""
+
+#: ./doc/common/section_trusted-compute-pools.xml88(term)
+msgid "port"
+msgstr "port"
+
+#: ./doc/common/section_trusted-compute-pools.xml90(para)
+msgid "HTTPS port for the attestation service."
+msgstr ""
+
+#: ./doc/common/section_trusted-compute-pools.xml94(term)
+msgid "server_ca_file"
+msgstr "server_ca_file "
+
+#: ./doc/common/section_trusted-compute-pools.xml96(para)
+msgid "Certificate file used to verify the attestation server's identity."
+msgstr "Certificat utilisé pour vérifier l'identité du serveur d'attestation. "
+
+#: ./doc/common/section_trusted-compute-pools.xml101(term)
+msgid "api_url"
+msgstr "api_url"
+
+#: ./doc/common/section_trusted-compute-pools.xml103(para)
+msgid "The attestation service's URL path."
+msgstr ""
+
+#: ./doc/common/section_trusted-compute-pools.xml107(term)
+msgid "auth_blob"
+msgstr "auth_blob"
+
+#: ./doc/common/section_trusted-compute-pools.xml109(para)
+msgid "An authentication blob, which is required by the attestation service."
+msgstr "Blob d'authentification, nécessaire au service."
+
+#: ./doc/common/section_trusted-compute-pools.xml117(para)
 msgid ""
-"Create a non-bootable volume and attach that volume to an instance that you "
-"boot from an image."
+"Restart the <systemitem class=\"service\">nova-compute</systemitem> and "
+"<systemitem class=\"service\">nova-scheduler</systemitem> services."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml66(para)
+#: ./doc/common/section_trusted-compute-pools.xml124(title)
+#: ./doc/common/section_compute_config-api.xml183(title)
+msgid "Configuration reference"
+msgstr ""
+
+#: ./doc/common/section_trusted-compute-pools.xml125(para)
 msgid ""
-"To create a non-bootable volume, do not create it from an image. The volume "
-"must be entirely empty with no partition table and no file system."
+"To customize the trusted compute pools, use the following configuration "
+"option settings:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml71(para)
-msgid "Create a non-bootable volume:"
+#: ./doc/common/section_trusted-compute-pools.xml132(title)
+msgid "Specify trusted flavors"
+msgstr "Spécification de variétés [ORIGINAL: flavors] fiables"
+
+#: ./doc/common/section_trusted-compute-pools.xml133(para)
+msgid "To designate hosts as trusted:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml98(para)
-#: ./doc/common/section_cli_cinder_manage_volumes.xml176(para)
-msgid "List volumes:"
-msgstr "Listez les volumes:"
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml107(para)
+#: ./doc/common/section_trusted-compute-pools.xml136(para)
 msgid ""
-"Boot an instance from an image and attach the empty volume to the instance:"
+"Configure one or more flavors as trusted by using the <placeholder-1/> "
+"command. For example, to set the <literal>m1.tiny</literal> flavor as "
+"trusted:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml149(title)
-msgid "Create volume from image and boot instance"
-msgstr "Créez un volume depuis une image et démarrer une instance."
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml150(para)
+#: ./doc/common/section_trusted-compute-pools.xml141(para)
 msgid ""
-"You can create a volume from an existing image, volume, or snapshot. This "
-"procedure shows you how to create a volume from an image, and use the volume"
-" to boot an instance."
+"Request that your instance be run on a trusted host, by specifying a trusted"
+" flavor when booting the instance. For example:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml155(para)
-#: ./doc/common/section_cli_nova_boot.xml121(para)
-msgid "List the available images:"
-msgstr "Lister les images disponibles:"
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml165(para)
-msgid "Note the ID of the image that you want to use to create a volume."
+#: ./doc/common/section_trusted-compute-pools.xml145(title)
+msgid "Trusted compute pool"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml169(para)
-#: ./doc/common/section_cli_nova_boot.xml106(para)
-msgid "List the available flavors:"
-msgstr "Listez les types d'instances disponibles:"
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml183(para)
-msgid "Note the ID of the flavor that you want to use to create a volume."
+#: ./doc/common/ch_cli_heat_commands.xml11(title)
+msgid "Orchestration command-line client"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml187(para)
+#: ./doc/common/ch_cli_heat_commands.xml12(para)
 msgid ""
-"To create a bootable volume from an image and launch an instance from this "
-"volume, use the <parameter>--block-device</parameter> parameter."
-msgstr "Pour créer un volume démarrable depuis une image et pour lancer une instance depuis ce volume, utilisez le paramètre <parameter>--block-device</parameter>."
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
-#: ./doc/common/section_cli_nova_boot_from_volume.xml329(replaceable)
-msgid "FLAVOR"
+"The <placeholder-1/> client is the command-line interface (CLI) for the "
+"Orchestration API and its extensions. This chapter documents "
+"<placeholder-2/> version 0.2.9."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
-#: ./doc/common/section_cli_nova_boot_from_volume.xml205(replaceable)
-msgid "SOURCE"
-msgstr "SOURCE"
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
-#: ./doc/common/section_cli_nova_boot_from_volume.xml217(replaceable)
-msgid "ID"
-msgstr "ID"
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
-#: ./doc/common/section_cli_nova_boot_from_volume.xml224(replaceable)
-msgid "DEST"
+#: ./doc/common/ch_cli_heat_commands.xml22(title)
+msgid "heat usage"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
-#: ./doc/common/section_cli_nova_boot_from_volume.xml233(replaceable)
-msgid "SIZE"
+#: ./doc/common/ch_cli_heat_commands.xml39(para)
+#: ./doc/common/ch_cli_heat_commands.xml506(para)
+msgid "Resume the stack."
+msgstr "Reprendre la pile."
+
+#: ./doc/common/ch_cli_heat_commands.xml47(para)
+#: ./doc/common/ch_cli_heat_commands.xml523(para)
+msgid "Suspend the stack."
+msgstr "suspendre la pile."
+
+#: ./doc/common/ch_cli_heat_commands.xml55(para)
+#: ./doc/common/ch_cli_heat_commands.xml540(para)
+msgid "Retrieve build information."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
-msgid "PRESERVE"
+#: ./doc/common/ch_cli_heat_commands.xml63(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use stack-create instead."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
-#: ./doc/common/section_cli_nova_boot_from_volume.xml250(replaceable)
-msgid "INDEX"
+#: ./doc/common/ch_cli_heat_commands.xml71(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use stack-delete instead."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
-#: ./doc/common/section_cli_nova_boot_from_volume.xml329(replaceable)
-msgid "NAME"
+#: ./doc/common/ch_cli_heat_commands.xml79(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use stack-show instead."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml192(para)
-msgid "The parameters are:"
-msgstr "Les paramètres sont:"
+#: ./doc/common/ch_cli_heat_commands.xml87(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use event-show instead."
+msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml195(para)
+#: ./doc/common/ch_cli_heat_commands.xml95(para)
+#: ./doc/common/ch_cli_heat_commands.xml547(para)
+msgid "List events for a stack."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml103(para)
+#: ./doc/common/ch_cli_heat_commands.xml575(para)
+msgid "Describe the event."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml111(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use template-show instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml119(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use stack-list instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml127(para)
+#: ./doc/common/ch_cli_heat_commands.xml608(para)
+msgid "Show available outputs."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml135(para)
+#: ./doc/common/ch_cli_heat_commands.xml625(para)
+msgid "Show a specific stack output."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml143(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use resource-show instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml151(para)
+#: ./doc/common/ch_cli_heat_commands.xml650(para)
+msgid "Show list of resources belonging to a stack."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml159(para)
+#: ./doc/common/ch_cli_heat_commands.xml667(para)
+msgid "List resource metadata."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml167(para)
+#: ./doc/common/ch_cli_heat_commands.xml692(para)
+msgid "Describe the resource."
+msgstr "Décrire la ressource."
+
+#: ./doc/common/ch_cli_heat_commands.xml175(para)
+#: ./doc/common/ch_cli_heat_commands.xml717(para)
+msgid "Send a signal to a resource."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml183(para)
+#: ./doc/common/ch_cli_heat_commands.xml762(para)
+msgid "Generate a template based on a resource."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml191(para)
+#: ./doc/common/ch_cli_heat_commands.xml790(para)
+msgid "List the available resource types."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml199(para)
+#: ./doc/common/ch_cli_heat_commands.xml797(para)
+msgid "Show the resource type."
+msgstr "Montrer le type de ressource."
+
+#: ./doc/common/ch_cli_heat_commands.xml207(para)
+#: ./doc/common/ch_cli_heat_commands.xml814(para)
+msgid "Abandon the stack."
+msgstr "Abandonner la pile."
+
+#: ./doc/common/ch_cli_heat_commands.xml215(para)
+#: ./doc/common/ch_cli_heat_commands.xml834(para)
+msgid "Adopt a stack."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml223(para)
+#: ./doc/common/ch_cli_heat_commands.xml932(para)
+msgid "Create the stack."
+msgstr "Créer la pile"
+
+#: ./doc/common/ch_cli_heat_commands.xml231(para)
+#: ./doc/common/ch_cli_heat_commands.xml1019(para)
+msgid "Delete the stack(s)."
+msgstr "Supprimer la pile (les piles)."
+
+#: ./doc/common/ch_cli_heat_commands.xml239(para)
+#: ./doc/common/ch_cli_heat_commands.xml1037(para)
+msgid "List the user's stacks."
+msgstr "Lister les piles de l'utilisateur."
+
+#: ./doc/common/ch_cli_heat_commands.xml247(para)
+#: ./doc/common/ch_cli_heat_commands.xml1076(para)
+msgid "Preview the stack."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml255(para)
+#: ./doc/common/ch_cli_heat_commands.xml1154(para)
+msgid "Describe the stack."
+msgstr "Décrire la pile"
+
+#: ./doc/common/ch_cli_heat_commands.xml263(para)
+#: ./doc/common/ch_cli_heat_commands.xml1173(para)
+msgid "Update the stack."
+msgstr "Mettre à jour la pile"
+
+#: ./doc/common/ch_cli_heat_commands.xml271(para)
+#: ./doc/common/ch_cli_heat_commands.xml1243(para)
+msgid "Get the template for the specified stack."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml279(para)
+#: ./doc/common/ch_cli_heat_commands.xml1261(para)
+msgid "Validate a template with parameters."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml287(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use stack-update instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml295(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use template-validate instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml303(para)
+#: ./doc/common/ch_cli_keystone_commands.xml324(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml253(para)
+msgid "Prints all of the commands and options to stdout."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml320(title)
+msgid "heat optional arguments"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml325(para)
+#: ./doc/common/ch_cli_keystone_commands.xml346(para)
+msgid "Shows the client version and exits."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml333(para)
+msgid "Defaults to <code>env[HEATCLIENT_DEBUG]</code>."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml341(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml291(para)
+msgid "Print more verbose output."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml349(para)
 msgid ""
-"<parameter>--flavor</parameter><replaceable>FLAVOR</replaceable>. The flavor"
-" ID or name."
+"Explicitly allow the client to perform \"insecure\" SSL (https) requests. "
+"The server's certificate will not be verified against any certificate "
+"authorities. This option should be used with caution."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml200(para)
+#: ./doc/common/ch_cli_heat_commands.xml360(para)
+#: ./doc/common/ch_cli_glance_commands.xml262(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml311(para)
 msgid ""
-"<parameter>--block-device</parameter> "
-"source=<replaceable>SOURCE</replaceable>,id=<replaceable>ID</replaceable>,dest=<replaceable>DEST</replaceable>,size=<replaceable>SIZE</replaceable>,shutdown=<replaceable>PRESERVE</replaceable>,bootindex=<replaceable>INDEX</replaceable>"
-msgstr "<parameter>--block-device</parameter> source=<replaceable>SOURCE</replaceable>,id=<replaceable>ID</replaceable>,dest=<replaceable>DEST</replaceable>,size=<replaceable>SIZE</replaceable>,shutdown=<replaceable>PRESERVE</replaceable>,bootindex=<replaceable>INDEX</replaceable>"
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml205(emphasis)
-msgid "source=<placeholder-1/>"
+"Path of certificate file to use in SSL connection. This file can optionally "
+"be prepended with the private key."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml207(para)
+#: ./doc/common/ch_cli_heat_commands.xml370(para)
 msgid ""
-"The type of object used to create the block device. Valid values are "
-"<literal>volume</literal>, <literal>snapshot</literal>, "
-"<literal>image</literal>, and <literal>blank</literal>."
+"Path of client key to use in SSL connection.This option is not necessary if "
+"your key is prepended to your cert file."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml217(emphasis)
-msgid "id=<placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml219(para)
-msgid "The ID of the source object."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml224(emphasis)
-msgid "dest=<placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml226(para)
+#: ./doc/common/ch_cli_heat_commands.xml380(para)
 msgid ""
-"The type of the target virtual device. Valid values are "
-"<literal>volume</literal> and <literal>local</literal>."
+"Path of CA SSL certificate(s) used to verify the remote server's "
+"certificate. Without this option the client looks for the default system CA "
+"certificates."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml233(emphasis)
-msgid "size=<placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml235(para)
-msgid "The size of the volume that is created."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml240(emphasis)
-msgid "shutdown={preserve|remove}"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml242(para)
+#: ./doc/common/ch_cli_heat_commands.xml390(para)
 msgid ""
-"What to do with the volume when the instance is deleted. "
-"<literal>preserve</literal> does not delete the volume. "
-"<literal>remove</literal> deletes the volume."
+"Number of seconds to wait for an API response, defaults to system socket "
+"timeout"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml250(emphasis)
-msgid "bootindex=<placeholder-1/>"
+#: ./doc/common/ch_cli_heat_commands.xml447(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml405(para)
+msgid "Defaults to <code>env[OS_AUTH_TOKEN]</code>."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml252(para)
+#: ./doc/common/ch_cli_heat_commands.xml455(para)
 msgid ""
-"Orders the boot disks. Use <literal>0</literal> to boot from this volume."
+"Do not contact keystone for a token. Defaults to "
+"<code>env[OS_NO_CLIENT_AUTH]</code>."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml260(para)
-msgid "<replaceable>NAME</replaceable>. The name for the server."
+#: ./doc/common/ch_cli_heat_commands.xml464(para)
+msgid "Defaults to <code>env[HEAT_URL]</code>."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml266(para)
+#: ./doc/common/ch_cli_heat_commands.xml472(para)
+msgid "Defaults to <code>env[HEAT_API_VERSION]</code> or 1."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml480(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml429(para)
+msgid "Defaults to <code>env[OS_SERVICE_TYPE]</code>."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml488(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml437(para)
+msgid "Defaults to <code>env[OS_ENDPOINT_TYPE]</code>."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml496(para)
+msgid "Send os-username and os-password to heat."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml504(title)
+msgid "heat action-resume command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml513(para)
+msgid "Name or ID of stack to resume."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml521(title)
+msgid "heat action-suspend command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml530(para)
+msgid "Name or ID of stack to suspend."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml538(title)
+msgid "heat build-info command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml545(title)
+msgid "heat event-list command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml554(para)
+#: ./doc/common/ch_cli_heat_commands.xml582(para)
+msgid "Name or ID of stack to show the events for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml565(para)
+msgid "Name of the resource to filter events by."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml573(title)
+msgid "heat event-show command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml590(para)
+msgid "Name of the resource the event belongs to."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml598(para)
+msgid "ID of event to display details for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml606(title)
+msgid "heat output-list command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml615(para)
+#: ./doc/common/ch_cli_heat_commands.xml632(para)
+msgid "Name or ID of stack to query."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml623(title)
+msgid "heat output-show command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml640(para)
+msgid "Name of an output to display."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml648(title)
+msgid "heat resource-list command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml657(para)
+msgid "Name or ID of stack to show the resources for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml665(title)
+msgid "heat resource-metadata command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml674(para)
+msgid "Name or ID of stack to show the resource metadata for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml682(para)
+msgid "Name of the resource to show the metadata for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml690(title)
+msgid "heat resource-show command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml699(para)
+msgid "Name or ID of stack to show the resource for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml707(para)
+msgid "Name of the resource to show the details for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml715(title)
+msgid "heat resource-signal command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml724(para)
+msgid "Name or ID of stack the resource belongs to."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml732(para)
+msgid "Name of the resource to signal."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml743(para)
+msgid "JSON Data to send to the signal handler."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml751(para)
+msgid "File containing JSON data to send to the signal handler."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml760(title)
+msgid "heat resource-template command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml769(para)
+msgid "Name of the resource to generate a template for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml780(para)
+msgid "The template output format, one of: yaml, json."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml788(title)
+msgid "heat resource-type-list command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml795(title)
+msgid "heat resource-type-show command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml804(para)
+msgid "Resource type to get the details for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml812(title)
+msgid "heat stack-abandon command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml821(para)
+msgid "Name or ID of stack to abandon."
+msgstr "Nom ou ID de la pile à abandonner."
+
+#: ./doc/common/ch_cli_heat_commands.xml829(title)
+msgid "heat stack-adopt command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml841(para)
+msgid "Name of the stack to adopt."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml852(para)
+#: ./doc/common/ch_cli_heat_commands.xml950(para)
+#: ./doc/common/ch_cli_heat_commands.xml1094(para)
+#: ./doc/common/ch_cli_heat_commands.xml1191(para)
+#: ./doc/common/ch_cli_heat_commands.xml1276(para)
+msgid "Path to the template."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml860(para)
+#: ./doc/common/ch_cli_heat_commands.xml958(para)
+#: ./doc/common/ch_cli_heat_commands.xml1102(para)
+#: ./doc/common/ch_cli_heat_commands.xml1199(para)
+#: ./doc/common/ch_cli_heat_commands.xml1284(para)
+msgid "Path to the environment."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml868(para)
+#: ./doc/common/ch_cli_heat_commands.xml966(para)
+#: ./doc/common/ch_cli_heat_commands.xml1110(para)
+#: ./doc/common/ch_cli_heat_commands.xml1207(para)
+#: ./doc/common/ch_cli_heat_commands.xml1268(para)
+msgid "URL of template."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml876(para)
+msgid "URL to retrieve template object (e.g from swift)."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml884(para)
+#: ./doc/common/ch_cli_heat_commands.xml982(para)
 msgid ""
-"Create a bootable volume from an image, before the instance boots. The "
-"volume is not deleted when the instance is terminated:"
-msgstr "Créez un volume démarrable depuis une image avant le lancement de l'instance. Le volume n'est pas supprimé quand l'instance est terminée:"
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml307(para)
-msgid ""
-"List volumes to see the bootable volume and its attached "
-"<literal>myInstanceFromVolume</literal> instance:"
-msgstr "Listez les volumes pour voir l'instance démarrable et son instance <literal>myInstanceFromVolume</literal> jointe:"
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml320(title)
-msgid "Attach swap or ephemeral disk to an instance"
+"Stack creation timeout in minutes. <emphasis>DEPRECATED</emphasis> use "
+"--timeout instead."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml321(para)
-msgid ""
-"Use the nova <placeholder-1/><parameter>--swap</parameter> parameter to "
-"attach a swap disk on boot or the nova "
-"<placeholder-2/><parameter>--ephemeral</parameter> parameter to attach an "
-"ephemeral disk on boot. When you terminate the instance, both disks are "
-"deleted."
+#: ./doc/common/ch_cli_heat_commands.xml893(para)
+#: ./doc/common/ch_cli_heat_commands.xml991(para)
+msgid "Stack creation timeout in minutes."
+msgstr "Délai d'expiration (en minutes) pour la création de stack "
+
+#: ./doc/common/ch_cli_heat_commands.xml901(para)
+msgid "Path to adopt stack data file."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml327(para)
-msgid "Boot an instance with a 512MB swap disk and 2GB ephemeral disk:"
+#: ./doc/common/ch_cli_heat_commands.xml909(para)
+#: ./doc/common/ch_cli_heat_commands.xml999(para)
+msgid "Enable rollback on create/update failure."
+msgstr "Permettre le retour arrière en cas d'échec de la création / mise à jour."
+
+#: ./doc/common/ch_cli_heat_commands.xml917(para)
+#: ./doc/common/ch_cli_heat_commands.xml1007(para)
+#: ./doc/common/ch_cli_heat_commands.xml1231(para)
+msgid ""
+"Parameter values used to create the stack. This can be specified multiple "
+"times, or once with parameters separated by a semicolon."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml329(replaceable)
-#: ./doc/common/section_cli_nova_boot.xml186(replaceable)
-msgid "IMAGE_ID"
-msgstr "IMAGE_ID"
+#: ./doc/common/ch_cli_heat_commands.xml927(title)
+msgid "heat stack-create command"
+msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml331(para)
+#: ./doc/common/ch_cli_heat_commands.xml939(para)
+msgid "Name of the stack to create."
+msgstr "Nom de la pile à créer."
+
+#: ./doc/common/ch_cli_heat_commands.xml974(para)
+#: ./doc/common/ch_cli_heat_commands.xml1215(para)
+#: ./doc/common/ch_cli_heat_commands.xml1292(para)
+msgid "URL to retrieve template object (e.g. from swift)."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1017(title)
+msgid "heat stack-delete command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1026(para)
+msgid "Name or ID of stack(s) to delete."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1034(title)
+msgid "heat stack-list command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1044(para)
 msgid ""
-"The flavor defines the maximum swap and ephemeral disk size. You cannot "
-"exceed these maximum values."
+"Filter parameters to apply on returned stacks. This can be specified "
+"multiple times, or once with parameters separated by a semicolon."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1054(para)
+msgid "Limit the number of stacks returned."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1062(para)
+msgid "Only return stacks that appear after the given stack ID."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1071(title)
+msgid "heat stack-preview command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1083(para)
+msgid "Name of the stack to preview."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1118(para)
+msgid "URL to retrieve template object (e.g from swift)"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1126(para)
+msgid "Stack timeout in minutes. Default: 60"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1134(para)
+msgid "Enable rollback on failure"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1142(para)
+msgid ""
+"Parameter values used to preview the stack. This can be specified multiple "
+"times, or once with parameters separated by semicolon."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1152(title)
+msgid "heat stack-show command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1161(para)
+msgid "Name or ID of stack to describe."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1169(title)
+msgid "heat stack-update command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1180(para)
+msgid "Name or ID of stack to update."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1223(para)
+msgid "Stack update timeout in minutes."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1241(title)
+msgid "heat template-show command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1250(para)
+msgid "Name or ID of stack to get the template for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1258(title)
+msgid "heat template-validate command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1300(para)
+msgid ""
+"Parameter values to validate. This can be specified multiple times, or once "
+"with parameters separated by a semicolon."
 msgstr ""
 
 #: ./doc/common/section_cli_nova_images.xml6(title)
@@ -10342,6 +9249,11 @@ msgstr "Vous ne pouvez pas créer un instantané d'une unstance qui a un volume
 msgid "To create an image"
 msgstr "Pour créer un image"
 
+#: ./doc/common/section_cli_nova_images.xml18(para)
+#: ./doc/common/section_cli_nova_manage_images.xml17(para)
+msgid "Write any buffered data to disk."
+msgstr ""
+
 #: ./doc/common/section_cli_nova_images.xml19(para)
 msgid ""
 "For more information, see the <link href=\"http://docs.openstack.org/trunk"
@@ -10361,10 +9273,23 @@ msgid ""
 "repository. Only the tenant that creates the image has access to it."
 msgstr ""
 
+#: ./doc/common/section_cli_nova_images.xml43(para)
+#: ./doc/common/section_cli_nova_manage_images.xml40(para)
+msgid "Get details for your image to check its status:"
+msgstr "Trouver les détails de votre image pour vérifier son état:"
+
 #: ./doc/common/section_cli_nova_images.xml45(replaceable)
 msgid "IMAGE"
 msgstr "IMAGE"
 
+#: ./doc/common/section_cli_nova_images.xml79(para)
+#: ./doc/common/section_cli_nova_manage_images.xml75(para)
+msgid ""
+"The image status changes from <literal>SAVING</literal> to "
+"<literal>ACTIVE</literal>. Only the tenant who creates the image has access "
+"to it."
+msgstr ""
+
 #: ./doc/common/section_cli_nova_images.xml86(title)
 msgid "To launch an instance from your image"
 msgstr "Pour lancer une instance depuis votre image"
@@ -10375,6 +9300,11 @@ msgid ""
 "as follows:"
 msgstr "Pour lancer une instance depuis votre image, inclure l'ID de l'image et l'ID du type d'instance, comme suite:"
 
+#: ./doc/common/section_cli_nova_images.xml125(title)
+#: ./doc/common/section_cli_glance_manage_images.xml410(title)
+msgid "Troubleshoot image creation"
+msgstr "Résoudre les problèmes de la création des images"
+
 #: ./doc/common/section_cli_nova_images.xml133(para)
 msgid ""
 "Make sure the version of qemu you are using is version 0.14 or greater. "
@@ -10382,601 +9312,1658 @@ msgid ""
 " error message in the <filename>nova-compute.log</filename>."
 msgstr ""
 
-#: ./doc/common/section_keystone-external-auth.xml7(title)
-msgid "External authentication with Identity"
-msgstr ""
-
-#: ./doc/common/section_keystone-external-auth.xml8(para)
+#: ./doc/common/section_cli_nova_images.xml140(para)
+#: ./doc/common/section_cli_glance_manage_images.xml420(para)
 msgid ""
-"When Identity runs in <literal>apache-httpd</literal>, you can use external "
-"authentication methods that differ from the authentication provided by the "
-"identity store back end. For example, you can use an SQL identity back end "
-"together with X.509 authentication, Kerberos, and so on instead of using the"
-" user name and password combination."
+"Examine the <filename>/var/log/nova-api.log</filename> and "
+"<filename>/var/log/nova-compute.log</filename> log files for error messages."
 msgstr ""
 
-#: ./doc/common/section_keystone-external-auth.xml15(title)
-msgid "Use HTTPD authentication"
+#: ./doc/common/section_dochistory.xml6(title)
+msgid "Document change history"
 msgstr ""
 
-#: ./doc/common/section_keystone-external-auth.xml16(para)
+#: ./doc/common/section_dochistory.xml8(para)
 msgid ""
-"Web servers, like Apache HTTP, support many methods of authentication. "
-"Identity can allow the web server to perform the authentication. The web "
-"server then passes the authenticated user to Identity by using the "
-"<literal>REMOTE_USER</literal> environment variable. This user must already "
-"exist in the Identity back end to get a token from the controller. To use "
-"this method, Identity should run on <literal>apache-httpd</literal>."
+"This version of the guide replaces and obsoletes all previous versions. The "
+"following table describes the most recent changes:"
 msgstr ""
 
-#: ./doc/common/section_keystone-external-auth.xml27(title)
-msgid "Use X.509"
+#: ./doc/common/ch_cli_swift_commands.xml11(title)
+msgid "Object Storage command-line client"
 msgstr ""
 
-#: ./doc/common/section_keystone-external-auth.xml28(para)
+#: ./doc/common/ch_cli_swift_commands.xml12(para)
 msgid ""
-"The following Apache configuration snippet authenticates the user based on a"
-" valid X.509 certificate from a known CA:"
+"The <placeholder-1/> client is the command-line interface (CLI) for the "
+"OpenStack Object Storage API and its extensions. This chapter documents "
+"<placeholder-2/> version 2.1.0."
 msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml5(title)
-msgid "Orchestration module"
+#: ./doc/common/ch_cli_swift_commands.xml22(title)
+msgid "swift usage"
 msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml6(para)
+#: ./doc/common/ch_cli_swift_commands.xml41(para)
+#: ./doc/common/ch_cli_swift_commands.xml335(para)
+msgid "Delete a container or objects within a container."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml49(para)
+#: ./doc/common/ch_cli_swift_commands.xml399(para)
+msgid "Download objects from containers."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml57(para)
+#: ./doc/common/ch_cli_swift_commands.xml513(para)
+msgid "Lists the containers for the account or the objects for a container."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml66(para)
 msgid ""
-"The Orchestration module provides a template-based orchestration for "
-"describing a cloud application, by running OpenStack API calls to generate "
-"running cloud applications. The software integrates other core components of"
-" OpenStack into a one-file template system. The templates allow you to "
-"create most OpenStack resource types, such as instances, floating IPs, "
-"volumes, security groups and users. It also provides advanced functionality,"
-" such as instance high availability, instance auto-scaling, and nested "
-"stacks. This enables OpenStack core projects to receive a larger user base."
+"Updates meta information for the account, container, or object; creates "
+"containers if not present."
 msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml16(para)
+#: ./doc/common/ch_cli_swift_commands.xml75(para)
+#: ./doc/common/ch_cli_swift_commands.xml661(para)
+msgid "Displays information for the account, container, or object."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml84(para)
+msgid "Uploads files or directories to the given container."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml92(para)
+msgid "List cluster capabilities."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml100(title)
+msgid "swift examples"
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml110(title)
+msgid "swift optional arguments"
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml131(para)
+msgid "Use SERVICENET internal network."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml139(para)
+msgid "Print more info."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml147(para)
 msgid ""
-"The service enables deployers to integrate with the Orchestration module "
-"directly or through custom plug-ins."
+"Show the curl commands and results of all http queries regardless of result "
+"status."
 msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml18(para)
-msgid "The Orchestration module consists of the following components:"
-msgstr ""
-
-#: ./doc/common/section_getstart_orchestration.xml22(term)
-msgid "<code>heat</code> command-line client"
-msgstr ""
-
-#: ./doc/common/section_getstart_orchestration.xml23(para)
+#: ./doc/common/ch_cli_swift_commands.xml156(para)
 msgid ""
-"A CLI that communicates with the heat-api to run AWS CloudFormation APIs. "
-"End developers can directly use the Orchestration REST API."
+"Show the curl commands and results of all http queries which return an "
+"error."
 msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml28(term)
-msgid "<code>heat-api</code> component"
+#: ./doc/common/ch_cli_swift_commands.xml165(para)
+msgid "Suppress status output."
 msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml28(para)
+#: ./doc/common/ch_cli_swift_commands.xml173(para)
+msgid "for obtaining an auth token."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml181(para)
+msgid "Specify a version for authentication. Defaults to 1.0."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml189(para)
+msgid "User name for obtaining an auth token."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml197(para)
+msgid "Key for obtaining an auth token."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml205(para)
+msgid "The number of times to retry a failed connection."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml213(para)
+msgid "OpenStack username. Defaults to <code>env[OS_USERNAME]</code>."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml221(para)
+msgid "OpenStack password. Defaults to <code>env[OS_PASSWORD]</code>."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml229(para)
+msgid "OpenStack tenant ID. Defaults to <code>env[OS_TENANT_ID]</code>."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml237(para)
+msgid "OpenStack tenant name. Defaults to <code>env[OS_TENANT_NAME]</code>."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml246(para)
+msgid "OpenStack auth URL. Defaults to <code>env[OS_AUTH_URL]</code>."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml254(para)
 msgid ""
-"An OpenStack-native REST API that processes API requests by sending them to "
-"the heat-engine over Remote Procedure Call (RPC)."
+"OpenStack token. Defaults to <code>env[OS_AUTH_TOKEN]</code>. Used with "
+"--os-storage-url to bypass the usual username/password authentication."
 msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml34(term)
-msgid "<code>heat-api-cfn</code> component"
-msgstr ""
-
-#: ./doc/common/section_getstart_orchestration.xml34(para)
+#: ./doc/common/ch_cli_swift_commands.xml264(para)
 msgid ""
-"An AWS Query API that is compatible with AWS CloudFormation. It processes "
-"API requests by sending them to the heat-engine over RPC."
+"OpenStack storage URL. Defaults to <code>env[OS_STORAGE_URL]</code>. "
+"Overrides the storage url returned during auth. Will bypass authentication "
+"when used with --os-auth-token."
 msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml40(code)
-msgid "heat-engine"
+#: ./doc/common/ch_cli_swift_commands.xml275(para)
+msgid "OpenStack region name. Defaults to <code>env[OS_REGION_NAME]</code>."
 msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml41(para)
+#: ./doc/common/ch_cli_swift_commands.xml284(para)
+msgid "OpenStack Service type. Defaults to <code>env[OS_SERVICE_TYPE]</code>."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml293(para)
 msgid ""
-"Orchestrates the launching of templates and provides events back to the API "
-"consumer."
+"OpenStack Endpoint type. Defaults to <code>env[OS_ENDPOINT_TYPE]</code>."
 msgstr ""
 
-#: ./doc/common/section_getstart_networking.xml5(title)
-msgid "OpenStack Networking"
-msgstr ""
-
-#: ./doc/common/section_getstart_networking.xml6(para)
+#: ./doc/common/ch_cli_swift_commands.xml302(para)
+#: ./doc/common/ch_cli_keystone_commands.xml445(para)
+#: ./doc/common/ch_cli_trove_commands.xml558(para)
 msgid ""
-"OpenStack Networking allows you to create and attach interface devices "
-"managed by other OpenStack services to networks. Plug-ins can be implemented"
-" to accomodate different networking equipment and software, providing "
-"flexibility to OpenStack architecture and deployment."
+"Specify a CA bundle file to use in verifying a TLS (https) server "
+"certificate. Defaults to <code>env[OS_CACERT]</code>."
 msgstr ""
 
-#: ./doc/common/section_getstart_networking.xml11(para)
-#: ./doc/common/section_getstart_object-storage.xml9(para)
-msgid "It includes the following components:"
-msgstr "Elle comprend les éléments suivants "
-
-#: ./doc/common/section_getstart_networking.xml14(systemitem)
-msgid "neutron-server"
-msgstr ""
-
-#: ./doc/common/section_getstart_networking.xml15(para)
+#: ./doc/common/ch_cli_swift_commands.xml312(para)
 msgid ""
-"Accepts and routes API requests to the appropriate OpenStack Networking "
-"plug-in for action."
+"Allow swiftclient to access servers without having to verify the SSL "
+"certificate. Defaults to <code>env[SWIFTCLIENT_INSECURE]</code> (set to "
+"'true' to enable)."
 msgstr ""
 
-#: ./doc/common/section_getstart_networking.xml19(term)
-msgid "OpenStack Networking plug-ins and agents"
-msgstr ""
-
-#: ./doc/common/section_getstart_networking.xml20(para)
+#: ./doc/common/ch_cli_swift_commands.xml322(para)
 msgid ""
-"Plugs and unplugs ports, creates networks or subnets, and provides IP "
-"addressing. These plug-ins and agents differ depending on the vendor and "
-"technologies used in the particular cloud. OpenStack Networking ships with "
-"plug-ins and agents for Cisco virtual and physical switches, NEC OpenFlow "
-"products, Open vSwitch, Linux bridging, Ryu Network Operating System, and "
-"the VMware NSX product."
+"This option is deprecated and not used anymore. SSL compression should be "
+"disabled by default by the system SSL library."
 msgstr ""
 
-#: ./doc/common/section_getstart_networking.xml27(para)
+#: ./doc/common/ch_cli_swift_commands.xml332(title)
+msgid "swift delete command"
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml342(para)
+msgid "Name of container to delete from."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml350(para)
+msgid "Name of object to delete. Specify multiple times for multiple objects."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml362(para)
+msgid "Delete all containers and objects."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml370(para)
+msgid "Do not delete segments of manifest objects."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml378(para)
+msgid "Number of threads to use for deleting objects. Default is 10."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml387(para)
+msgid "Number of threads to use for deleting containers. Default is 10."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml396(title)
+msgid "swift download command"
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml406(para)
 msgid ""
-"The common agents are L3 (layer 3), DHCP (dynamic host IP addressing), and a"
-" plug-in agent."
+"Name of container to download from. To download a whole account, omit this "
+"and specify --all."
 msgstr ""
 
-#: ./doc/common/section_getstart_networking.xml31(term)
-#: ./doc/common/section_getstart_block-storage.xml35(term)
-msgid "Messaging queue"
-msgstr ""
-
-#: ./doc/common/section_getstart_networking.xml32(para)
+#: ./doc/common/ch_cli_swift_commands.xml415(para)
 msgid ""
-"Used by most OpenStack Networking installations to route information between"
-" the neutron-server and various agents, as well as a database to store "
-"networking state for particular plug-ins."
+"Name of object to download. Specify multiple times for multiple objects. "
+"Omit this to download all objects from the container."
 msgstr ""
 
-#: ./doc/common/section_getstart_networking.xml38(para)
+#: ./doc/common/ch_cli_swift_commands.xml428(para)
+msgid "Indicates that you really want to download everything in the account."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml437(para)
+msgid "Marker to use when starting a container or account download."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml446(para)
+msgid "Only download items beginning with &lt;prefix&gt;."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml454(para)
 msgid ""
-"OpenStack Networking mainly interacts with OpenStack Compute to provide "
-"networks and connectivity for its instances."
+"For a single file download, stream the output to &lt;out_file&gt;. "
+"Specifying \"-\" as &lt;out_file&gt; will redirect to stdout."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml6(title)
-msgid "Configure instances at boot"
+#: ./doc/common/ch_cli_swift_commands.xml464(para)
+msgid "Number of threads to use for downloading objects. Default is 10"
 msgstr ""
 
-#: ./doc/common/section_user-data.xml7(para)
+#: ./doc/common/ch_cli_swift_commands.xml473(para)
+msgid "Number of threads to use for downloading containers. Default is 10"
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml482(para)
+msgid "Perform download(s), but don't actually write anything to disk."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml491(para)
 msgid ""
-"When you boot instances in an OpenStack cloud, you can use user data or "
-"<package>cloud-init</package> to automatically configure instances at boot "
-"time. You might want to install some packages, start services, or manage "
-"your instance by using a Puppet or Chef server."
+"Adds a customized request header to the query, like \"Range\" or \"If-"
+"Match\". This argument is repeatable. Example --header \"content-"
+"type:text/plain\""
 msgstr ""
 
-#: ./doc/common/section_user-data.xml13(title)
-msgid "User data"
-msgstr "Données utilisateur"
+#: ./doc/common/ch_cli_swift_commands.xml501(para)
+msgid "Skip downloading files that are identical on both sides."
+msgstr ""
 
-#: ./doc/common/section_user-data.xml14(para)
+#: ./doc/common/ch_cli_swift_commands.xml510(title)
+msgid "swift list command"
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml520(para)
+msgid "Name of container to list object in."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml531(para)
+msgid "Long listing format, similar to ls -l."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml539(para)
+#: ./doc/common/ch_cli_swift_commands.xml688(para)
+msgid "Report sizes in human readable format similar to ls -lh."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml548(para)
+msgid "Used with -l or --lh, only report totals."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml556(para)
+msgid "Only list items beginning with the prefix."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml564(para)
 msgid ""
-"User data is the mechanism by which a user can pass information contained in"
-" a local file to an instance at launch time. The typical use case is to pass"
-" something like a shell script or a configuration file as user data."
-msgstr "User data est le mécanisme par lequel un utilisateur peut faire passer des informations contenues dans un fichier local à une instance au lancement de celle-ci. Le cas d'utilisation typique est de faire passer quelque chose comme un script shell ou un fichier de configuration en tant que user data."
+"Roll up items with the given delimiter. For containers only. See OpenStack "
+"Swift API documentation for what this means."
+msgstr ""
 
-#: ./doc/common/section_user-data.xml19(para)
+#: ./doc/common/ch_cli_swift_commands.xml574(title)
+msgid "swift post command"
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml577(para)
 msgid ""
-"User data is sent using the <literal>--user-data "
-"<replaceable>/path/to/filename</replaceable></literal> option when calling "
-"<placeholder-1/>. This example creates a text file and sends its contents as"
-" user data to the instance:"
-msgstr "User data est envoyé en utilisant l'option <literal>--user-data <replaceable>/path/to/filename</replaceable></literal> à l'appel de <placeholder-1/>. L'exemple suivant créé un fichier texte et ensuite envoie le contenu de ce fichier en tant que user data à l'instance."
+"Updates meta information for the account, container, or object. If the "
+"container is not found, it will be created automatically."
+msgstr ""
 
-#: ./doc/common/section_user-data.xml26(para)
+#: ./doc/common/ch_cli_swift_commands.xml585(para)
+msgid "Name of container to post to."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml593(para)
+msgid "Name of object to post. Specify multiple times for multiple objects."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml605(para)
 msgid ""
-"The instance can get user data by querying the metadata service through "
-"either the OpenStack metadata API or the EC2 compatibility API:"
-msgstr "L'instance peut retrouver user data en interrogeant le service de métadonnées à utiliser soit l'API de métadonnées OpenStack soit l'API de compatibilité EC2:"
+"Read ACL for containers. Quick summary of ACL syntax: .r:*, "
+".r:-.example.com, .r:www.example.com, account1, account2:user2"
+msgstr ""
 
-#: ./doc/common/section_user-data.xml34(para)
+#: ./doc/common/ch_cli_swift_commands.xml615(para)
 msgid ""
-"The Compute service treats user data as a blob. While the previous example "
-"uses a text file, user data can be in any format."
-msgstr "Notez que le service Compute traite user data tel un blob. Tandis que l'exemple ci dessus utilise un fichier texte, user data peut être dans n'importe quel format."
-
-#: ./doc/common/section_user-data.xml38(para)
-msgid "For more information, see <xref linkend=\"config-drive\"/>."
+"Write ACL for containers. Quick summary of ACL syntax: account1 "
+"account2:user2"
 msgstr ""
 
-#: ./doc/common/section_user-data.xml42(package)
-msgid "cloud-init"
-msgstr "Cloud-init"
+#: ./doc/common/ch_cli_swift_commands.xml624(para)
+msgid "Sync To for containers, for multi-cluster replication."
+msgstr ""
 
-#: ./doc/common/section_user-data.xml43(para)
+#: ./doc/common/ch_cli_swift_commands.xml632(para)
+msgid "Sync Key for containers, for multi-cluster replication."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml640(para)
 msgid ""
-"To do something useful with the user data, you must configure the virtual "
-"machine image to run a service on boot that gets user data from the metadata"
-" service and takes some action based on the contents of the data. The "
-"<package>cloud-init</package> package does exactly this. This package is "
-"compatible with the Compute metadata service and the Compute configuration "
-"drive."
-msgstr "Pour faire quelque chose d'utile avec les données utilisateur , l'image de la machine virtuelle doit être configurée pour exécuter un service au lancement qui retrouve les données utilisateur  depuis le service métadonnées et faire quelque actions basées sur le contenu des données. Le paquet <package>cloud-init</package> a été inventé pour faire exactement cela. En particulier, cloud-init est compatible avec le service de métadonnées Compute ainsi que le Compute config drive.."
+"Sets a meta data item. This option may be repeated. Example: -m Color:Blue "
+"-m Size:Large"
+msgstr ""
 
-#: ./doc/common/section_user-data.xml51(para)
+#: ./doc/common/ch_cli_swift_commands.xml649(para)
 msgid ""
-"The <package>cloud-init</package> package supports multiple cloud providers."
-" You can use the same virtual machine image in different clouds without "
-"modification. The <package>cloud-init</package> package is an open source "
-"project and the source code is available on <link "
-"href=\"http://launchpad.net/cloud-init\">Launchpad</link>. It is maintained "
-"by Canonical, the company that runs the Ubuntu project. All Ubuntu cloud "
-"images come pre-installed with <package>cloud-init</package>. However, "
-"<package>cloud-init</package> is not designed to be Ubuntu-specific and has "
-"been successfully ported to several other platforms including Fedora."
-msgstr "Notez que <package>cloud-init</package> n'est pas une technologie OpenStack. Plutôt, il s'agit d'un paquet qui est fait pour supporter plusieurs fournisseurs de cloud, de sorte que la même image de machine virtuelle peut être utilisée dans différents clouds sans modification. <package>cloud-init</package> est un projet open source, et le code source est disponible sur <link href=\"http://launchpad.net/cloud-init\">Launchpad</link>. Il est maintenu par Canonical, L'entreprise qui travaille sur le projet Ubuntu. Toutes les images Ubuntu sont distribuées avec <package>cloud-init</package> pré-installé. Cependant, <package>cloud-init</package> n'est pas fait pour être spécifique à Ubuntu, et a été porté avec succès sur Fedora."
+"Set request headers. This option may be repeated. Example -H \"content-"
+"type:text/plain\""
+msgstr ""
 
-#: ./doc/common/section_user-data.xml66(para)
+#: ./doc/common/ch_cli_swift_commands.xml658(title)
+msgid "swift stat command"
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml668(para)
+msgid "Name of container to stat from."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml676(para)
+msgid "Name of object to stat. Specify multiple times for multiple objects."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml697(title)
+msgid "swift upload command"
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml700(para)
+msgid "Uploads specified files and directories to the given container."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml707(para)
+msgid "Name of container to upload to."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml715(para)
 msgid ""
-"Even if you do not use user data to configure instance behavior at boot "
-"time, install <package>cloud-init</package> on images that you create "
-"because this package provides useful functionality. For example, the "
-"<package>cloud-init</package> package enables you to copy the public key to "
-"an account (the <literal>ubuntu</literal> account by default on Ubuntu "
-"instances, the <literal>ec2-user</literal> by default in Fedora instances)."
-msgstr "Nous recommandons d'installer <package>cloud-init</package> sur les images que vous créez pour simplifier la tâche de configuration de vos instances au lancement. Même si vous ne voulez pas utiliser de données utilisateur pour configurer le comportement de l'instance au lancement, <package>cloud-init</package> fournit des fonctionnalités utiles tels que copier la clé public dans un compte (le compte <literal>ubuntu</literal> par défaut sur les instances Ubuntu,le <literal>ec2-user</literal> par défaut dans les instances Fedora)."
+"Name of file or directory to upload. Specify multiple times for multiple "
+"uploads."
+msgstr ""
 
-#: ./doc/common/section_user-data.xml75(para)
+#: ./doc/common/ch_cli_swift_commands.xml727(para)
+msgid "Only upload files that have changed since the last upload."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml736(para)
+msgid "Skip uploading files that are identical on both sides."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml744(para)
 msgid ""
-"If you do not have <package>cloud-init</package> installed, you must "
-"manually configure your image to get the public key from the metadata "
-"service on boot and copy it to the appropriate account."
-msgstr "Si vous n'avez pas installé <package>cloud-init</package>, vous devrez configurer votre image manuellement pour retrouver la clé publique depuis le service métadonnées au lancement et le copier dans le compte approprié."
+"Upload files in segments no larger than &lt;size&gt; (in Bytes) and then "
+"create a \"manifest\" file that will download all the segments as if it were"
+" the original file."
+msgstr ""
 
-#: ./doc/common/section_user-data.xml81(title)
-msgid "<package>cloud-init</package> supported formats and documentation"
-msgstr "Documentation et formats supportés par <package>cloud-init</package>"
-
-#: ./doc/common/section_user-data.xml83(para)
+#: ./doc/common/ch_cli_swift_commands.xml755(para)
 msgid ""
-"Look at the <package>cloud-init</package><link "
-"href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-"
-"init/trunk/view/head:/doc/userdata.txt\">doc/userdata.txt</link> file the "
-"<link href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-"
-"init/trunk/files/head:/doc/examples/\">examples</link> directory and the "
-"<link href=\"https://help.ubuntu.com/community/CloudInit\">Ubuntu community "
-"documentation</link> for details about how to use <package>cloud-"
-"init</package>. Some basic examples are provided here."
-msgstr "Nous recommandons d'aller jeter un œil au fichier <package>cloud-init</package> <link href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/userdata.txt\">doc/userdata.txt</link>, des<link href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/files/head:/doc/examples/\">examples</link> ainsi que la <link href=\"https://help.ubuntu.com/community/CloudInit\">Ubuntu community documentation</link> pour des détails concernant comment utiliser <package>cloud-init</package>. Nous proposons quelques exemples basiques ici."
+"Upload the segments into the specified container. If not specified, the "
+"segments will be uploaded to a &lt;container&gt;_segments container to not "
+"pollute the main &lt;container&gt; listings."
+msgstr ""
 
-#: ./doc/common/section_user-data.xml93(para)
+#: ./doc/common/ch_cli_swift_commands.xml766(para)
 msgid ""
-"<package>cloud-init</package> supports several input formats for user data. "
-"Two commonly used formats are:"
+"Indicates that you want the older segments of manifest objects left alone "
+"(in the case of overwrites)."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml98(para)
-msgid "Shell scripts (starts with <literal>#!</literal>)"
-msgstr "Scripts Shell (<literal>#!</literal>)"
+#: ./doc/common/ch_cli_swift_commands.xml775(para)
+msgid "Number of threads to use for uploading full objects. Default is 10."
+msgstr ""
 
-#: ./doc/common/section_user-data.xml102(para)
-msgid "Cloud config files (starts with <literal>#cloud-config</literal>)"
-msgstr "Fichiers de configuration de cloud(commence par <literal>#cloud-config</literal>)"
+#: ./doc/common/ch_cli_swift_commands.xml784(para)
+msgid "Number of threads to use for uploading object segments. Default is 10."
+msgstr ""
 
-#: ./doc/common/section_user-data.xml108(title)
-msgid "Run a shell script on boot"
-msgstr "Exécuter un script shell au boot"
-
-#: ./doc/common/section_user-data.xml109(para)
+#: ./doc/common/ch_cli_swift_commands.xml793(para)
 msgid ""
-"Assuming you have <package>cloud-init</package> installed, the simplest way "
-"to configure an instance on boot is to pass a shell script as user data. The"
-" shell file must begin with <literal>#!</literal> in order for <package"
-">cloud-init</package> to recognize it as a shell script. This example shows "
-"a script that creates a <literal>clouduser</literal> account:"
-msgstr "En supposant que vous avez installé <package>cloud-init</package>, le moyen le plus simple pour configurer une instance durant le boot est de faire passer un script shell en tant que données utilisateur. Le fichier shell doit commencer par <literal>#!</literal> pour que <package>cloud-init</package> le reconnaisse comme script shell. Voici un exemple de script qui créée un compte nommé <literal>clouduser</literal>."
+"Set request headers with the syntax header:value. This option may be "
+"repeated. Example -H \"content-type:text/plain\"."
+msgstr ""
 
-#: ./doc/common/section_user-data.xml118(para)
+#: ./doc/common/ch_cli_swift_commands.xml803(para)
 msgid ""
-"Sending a shell script as user data has a similar effect to writing an "
-"<filename>/etc/rc.local</filename> script: it executes very late in the boot"
-" sequence as root."
-msgstr "Envoyer un script shell en tant que données utilisateur a un effet similaire à écrire un script <filename>/etc/rc.local</filename>:il sera exécuté très tard dans la séquence de boot en tant que root."
+"When used in conjunction with --segment-size it will create a Static Large "
+"Object instead of the default Dynamic Large Object."
+msgstr ""
 
-#: ./doc/common/section_user-data.xml123(title)
-msgid "Cloud-config format"
-msgstr "Format Cloud-config "
-
-#: ./doc/common/section_user-data.xml124(para)
+#: ./doc/common/ch_cli_swift_commands.xml813(para)
 msgid ""
-"<package>cloud-init</package> supports a YAML-based config format that "
-"allows the user to configure a large number of options on a system. User "
-"data that begins with <literal>#cloud-config</literal> will be interpreted "
-"by <package>cloud-init</package> as cloud-config format."
-msgstr "<package>cloud-init</package> supporte un format de configuration basé sur YAML qui permet à l'utilisateur de configurer un grand nombre d'options sur un système. Les données utilisateur commençant par <literal>#cloud-config</literal> seront interprétées par <package>cloud-init</package> en tant que format de configuration de cloud."
+"Upload file and name object to &lt;object-name&gt; or upload dir and use &lt"
+";object-name&gt; as object prefix instead of folder name."
+msgstr ""
 
-#: ./doc/common/section_user-data.xml132(title)
-msgid "Example: Set the host name"
-msgstr "<package>cloud-init</package>"
+#: ./doc/common/section_cli_neutron_manage_networks.xml7(title)
+msgid "Create and manage networks"
+msgstr "Créez et gérez des réseaux"
 
-#: ./doc/common/section_user-data.xml133(para)
+#: ./doc/common/section_cli_neutron_manage_networks.xml8(para)
+msgid "Before you run commands, set the following environment variables:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml15(title)
+msgid "Create networks"
+msgstr "Créez des réseaux"
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml18(para)
+msgid "List the extensions of the system:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml34(para)
+msgid "Create a network:"
+msgstr "Créez un réseau"
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml53(para)
+msgid "Some fields of the created network are invisible to non-admin users."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml58(para)
+msgid "Create a network with specified provider network type:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml77(para)
 msgid ""
-"This <package>cloud-init</package> user data example sets the hostname and "
-"the FQDN, as well as updating <filename>/etc/hosts</filename> on the "
-"instance:"
-msgstr "Cet exemple de données utilisateur <package>cloud-init</package> fixe un nom d'hôte et le FQDN, et met à jour <filename>/etc/hosts</filename> dans l'instance:"
+"Just as shown previously, the unknown option <literal>--provider:network-"
+"type</literal> is used to create a <literal>local</literal> provider "
+"network."
+msgstr ""
 
-#: ./doc/common/section_user-data.xml145(title)
-msgid "Example: Configure instances with Puppet"
-msgstr "Exemple: Configurer des instances avec Puppet"
+#: ./doc/common/section_cli_neutron_manage_networks.xml85(title)
+msgid "Create subnets"
+msgstr "Créez des sous-réseaux"
 
-#: ./doc/common/section_user-data.xml146(para)
+#: ./doc/common/section_cli_neutron_manage_networks.xml88(para)
+msgid "Create a subnet:"
+msgstr "Créez un sous-réseau"
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml106(para)
 msgid ""
-"This <package>cloud-init</package> user data example, based on <link "
-"href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-"
-"init/trunk/view/head:/doc/examples/cloud-config-puppet.txt\">doc/examples"
-"/cloud-config-puppet.txt</link>, would configure the instance to contact a "
-"Puppet server at puppetmaster.example.org and verify its identity by using a"
-" certificate."
+"The <placeholder-1/> command has the following positional and optional "
+"parameters:"
 msgstr ""
 
-#: ./doc/common/section_user-data.xml174(title)
-msgid "Example: Configure instances with Chef"
-msgstr "Exemple : Configurer les instances avec Chef"
+#: ./doc/common/section_cli_neutron_manage_networks.xml111(para)
+msgid "The name or ID of the network to which the subnet belongs."
+msgstr ""
 
-#: ./doc/common/section_user-data.xml175(para)
+#: ./doc/common/section_cli_neutron_manage_networks.xml113(para)
 msgid ""
-"This <package>cloud-init</package> user data example, based on <link "
-"href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-"
-"init/trunk/view/head:/doc/examples/cloud-config-chef.txt\">doc/examples"
-"/cloud-config/chef.txt</link> and intended for use in an Ubuntu image, adds "
-"the Chef apt repository, installs Chef, connects to a Chef server at "
-"<literal>https://chefserver.example.com:4000</literal>, and installs Apache:"
+"In this example, <literal>net1</literal> is a positional argument that "
+"specifies the network name."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml6(title)
-msgid "Add security group and rules"
-msgstr "Ajouter un groupe de sécurité et des règles"
+#: ./doc/common/section_cli_neutron_manage_networks.xml118(para)
+msgid "The CIDR of the subnet."
+msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml7(para)
+#: ./doc/common/section_cli_neutron_manage_networks.xml119(para)
 msgid ""
-"The following procedure shows you how to add security groups and add rules "
-"to the default security group."
-msgstr "Le procédure suivant vous montre comment ajouter les groupes de sécurité et ajouter des règles au groupe de sécurité par défaut."
-
-#: ./doc/common/section_cli_nova_secgroups.xml10(title)
-msgid "Add or delete a security group"
-msgstr "Ajouter ou supprimer un groupe de sécurité"
-
-#: ./doc/common/section_cli_nova_secgroups.xml11(para)
-msgid "Use the <placeholder-1/> command to add security groups."
+"In this example, <literal>192.168.2.0/24</literal> is a positional argument "
+"that specifies the CIDR."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml13(para)
+#: ./doc/common/section_cli_neutron_manage_networks.xml125(para)
+msgid "The subnet name, which is optional."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml127(para)
 msgid ""
-"The following example shows how to create the <literal>secure1</literal> "
-"security group:"
+"In this example, <literal>--name subnet1</literal> specifies the name of the"
+" subnet."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml21(para)
+#: ./doc/common/section_cli_neutron_manage_networks.xml136(title)
+msgid "Create routers"
+msgstr "Créer des routeurs"
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml139(para)
+msgid "Create a router:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml140(replaceable)
+msgid "router1"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml152(para)
 msgid ""
-"After you create the security group, you can view it in the security group "
-"list:"
+"Take note of the unique router identifier returned, this will be required in"
+" subsequent steps."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml30(para)
+#: ./doc/common/section_cli_neutron_manage_networks.xml156(para)
+msgid "Link the router to the external provider network:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml157(replaceable)
+#: ./doc/common/section_cli_neutron_manage_networks.xml164(replaceable)
+msgid "ROUTER"
+msgstr "ROUTEUR"
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml157(replaceable)
+msgid "NETWORK"
+msgstr "RESEAU"
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml158(para)
 msgid ""
-"Use the <placeholder-1/> command to delete security groups. You cannot "
-"delete the default security group. The default security group has these "
-"initial settings:"
+"Replace <replaceable>ROUTER</replaceable> with the unique identifier of the "
+"router, replace <replaceable>NETWORK</replaceable> with the unique "
+"identifier of the external provider network."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml36(para)
+#: ./doc/common/section_cli_neutron_manage_networks.xml163(para)
+msgid "Link the router to the subnet:"
+msgstr "Liez le routeur au sous-réseau:"
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml164(replaceable)
+msgid "SUBNET"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml165(para)
 msgid ""
-"All the traffic originated by the instances (outbound traffic) is allowed"
-msgstr "Tout trafic créé par des instances (trafic sortant) est autorisé."
+"Replace <replaceable>ROUTER</replaceable> with the unique identifier of the "
+"router, replace <replaceable>SUBNET</replaceable> with the unique identifier"
+" of the subnet."
+msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml40(para)
-msgid "All the traffic destined to instances (inbound traffic) is denied"
-msgstr "Tout trafic à destination des instances (trafic entrant) est refusé."
+#: ./doc/common/section_cli_neutron_manage_networks.xml172(title)
+msgid "Create ports"
+msgstr "Créer des ports"
 
-#: ./doc/common/section_cli_nova_secgroups.xml44(para)
-msgid "All the instances inside the group are allowed to talk to each other"
-msgstr "Tous les instances dans le groupe peuvent communiquer entre elles. "
+#: ./doc/common/section_cli_neutron_manage_networks.xml175(para)
+msgid "Create a port with specified IP address:"
+msgstr "Créer un port avec une adresse IP précisée:"
 
-#: ./doc/common/section_cli_nova_secgroups.xml49(para)
+#: ./doc/common/section_cli_neutron_manage_networks.xml194(para)
 msgid ""
-"You can add extra rules into the default security group for handling the "
-"egress traffic. Rules are ingress only at this time."
-msgstr "Vous pouvez ajouter des règles supplémentaires dans le groupe de sécurité par défaut afin de gérer le trafic de sortie. Les règles concerne le trafic d'entrée uniquement à ce stade-là."
+"In the previous command, <literal>net1</literal> is the network name, which "
+"is a positional argument. <literal>--fixed-ip "
+"ip_address=192.168.2.40</literal> is an option, which specifies the port's "
+"fixed IP address we wanted."
+msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml53(para)
+#: ./doc/common/section_cli_neutron_manage_networks.xml201(para)
 msgid ""
-"The following example deletes the <literal>secure1</literal> group. When you"
-" view the security group list, it no longer appears:"
+"When creating a port, you can specify any unallocated IP in the subnet even "
+"if the address is not in a pre-defined pool of allocated IP addresses (set "
+"by your cloud provider)."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml65(title)
-msgid "Modify security group rules"
-msgstr "Modifier les règles du groupe de sécurité"
+#: ./doc/common/section_cli_neutron_manage_networks.xml208(para)
+msgid "Create a port without specified IP address:"
+msgstr "Créer un port sans une adresse IP précisée:"
 
-#: ./doc/common/section_cli_nova_secgroups.xml69(para)
-msgid "You cannot change the default outbound behavior."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_secgroups.xml66(para)
+#: ./doc/common/section_cli_neutron_manage_networks.xml229(para)
 msgid ""
-"The security group rules control the incoming traffic that can access the "
-"instances in the group, while all outbound traffic is automatically allowed."
-" <placeholder-1/>Every security group rule is a policy that allows you to "
-"specify inbound connections that can access the instance by source address, "
-"destination port, and IP protocol (TCP, UDP or ICMP). Currently, you cannot "
-"manage ipv6 and other protocols through the security rules, making them "
-"permitted by default. To manage such protocols, you can deploy a firewall in"
-" front of your OpenStack cloud to control other types of traffic. The "
-"command requires the following arguments for both TCP and UDP rules:"
+"Note that the system allocates one IP address if you do not specify an IP "
+"address in the <placeholder-1/> command."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml84(emphasis)
-#: ./doc/common/section_cli_nova_secgroups.xml124(emphasis)
-#: ./doc/common/section_cli_nova_secgroups.xml209(emphasis)
-msgid "&lt;secgroup&gt;"
+#: ./doc/common/section_cli_neutron_manage_networks.xml234(para)
+msgid "Query ports with specified fixed IP addresses:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml86(para)
-#: ./doc/common/section_cli_nova_secgroups.xml126(para)
-#: ./doc/common/section_cli_nova_secgroups.xml211(para)
-msgid "ID of security group."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_secgroups.xml91(emphasis)
-#: ./doc/common/section_cli_nova_secgroups.xml131(emphasis)
-#: ./doc/common/section_cli_nova_secgroups.xml216(emphasis)
-msgid "&lt;ip_proto&gt;"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_secgroups.xml98(emphasis)
-#: ./doc/common/section_cli_nova_secgroups.xml223(emphasis)
-msgid "&lt;from_port&gt;"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_secgroups.xml105(emphasis)
-#: ./doc/common/section_cli_nova_secgroups.xml230(emphasis)
-msgid "&lt;to_port&gt;"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_secgroups.xml112(emphasis)
-#: ./doc/common/section_cli_nova_secgroups.xml152(emphasis)
-#: ./doc/common/section_cli_nova_secgroups.xml237(emphasis)
-msgid "&lt;cidr&gt;"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_secgroups.xml118(para)
+#: ./doc/common/section_cli_neutron_manage_networks.xml243(para)
 msgid ""
-"For ICMP rules, instead of specifying a begin and end port, you specify the "
-"allowed ICMP code and ICMP type:"
+"<literal>--fixed-ips ip_address=192.168.2.2 "
+"ip_address=192.168.2.40</literal> is one unknown option."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml133(para)
-msgid "IP protocol (with icmp specified)."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_secgroups.xml138(emphasis)
-msgid "&lt;ICMP_code&gt;"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_secgroups.xml140(para)
-msgid "The ICMP code."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_secgroups.xml145(emphasis)
-msgid "&lt;ICMP_type&gt;"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_secgroups.xml147(para)
-msgid "The ICMP type."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_secgroups.xml154(para)
-msgid "CIDR for the source address range."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_secgroups.xml159(para)
+#: ./doc/common/section_cli_neutron_manage_networks.xml246(para)
 msgid ""
-"Entering <literal>-1</literal> for both code and type indicates that all "
-"ICMP codes and types are allowed."
+"<emphasis role=\"bold\">How to find unknown options?</emphasis> The unknown "
+"options can be easily found by watching the output of "
+"<literal>create_xxx</literal> or <literal>show_xxx</literal> command. For "
+"example, in the port creation command, we see the fixed_ips fields, which "
+"can be used as an unknown option."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml164(title)
-msgid "The CIDR notation"
-msgstr "La notation CIDR"
-
-#: ./doc/common/section_cli_nova_secgroups.xml165(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-arch.xml23(None)
 msgid ""
-"That notation allows you to specify a base IP address and a suffix that "
-"designates the number of significant bits in the IP address used to identify"
-" the network. For example, by specifying a "
-"<literal>88.170.60.32/27</literal>, you specify "
-"<literal>88.170.60.32</literal> as the <emphasis role=\"bold\">base "
-"IP</emphasis> and <literal>27</literal> as the <emphasis "
-"role=\"bold\">suffix</emphasis>. Because you use an IPV4 format, only 5 bits"
-" are available for the host part (32 minus 27). The "
-"<literal>0.0.0.0/0</literal> notation means you allow the entire IPV4 range,"
-" which allows all addresses."
+"@@image: '../common/figures/objectstorage-arch.png'; "
+"md5=90f6c7cf3947d7987eeb55d657cdc927"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml179(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-arch.xml60(None)
 msgid ""
-"For example, to allow any IP address to access a web server running on one "
-"of your instances inside the default security group:"
+"@@image: '../common/figures/objectstorage-nodes.png'; "
+"md5=2aa7eb3bddcf6826f33469920dc2a9c3"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml188(para)
+#: ./doc/common/section_objectstorage-arch.xml11(title)
+msgid "Cluster architecture"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-arch.xml13(title)
+msgid "Access tier"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-arch.xml14(para)
 msgid ""
-"To allow any IP address to ping an instance inside the default security "
-"group (Code 0, Type 8 for the ECHO request):"
+"Large-scale deployments segment off an access tier, which is considered the "
+"Object Storage system's central hub. The access tier fields the incoming API"
+" requests from clients and moves data in and out of the system. This tier "
+"consists of front-end load balancers, ssl-terminators, and authentication "
+"services. It runs the (distributed) brain of the Object Storage system: the "
+"proxy server processes."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml204(para)
+#: ./doc/common/section_objectstorage-arch.xml20(title)
+msgid "Object Storage architecture"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-arch.xml27(para)
 msgid ""
-"To delete a rule, you must specify exactly the same arguments that you used "
-"to create it:"
+"Because access servers are collocated in their own tier, you can scale out "
+"read/write access regardless of the storage capacity. For example, if a "
+"cluster is on the public Internet, requires SSL termination, and has a high "
+"demand for data access, you can provision many access servers. However, if "
+"the cluster is on a private network and used primarily for archival "
+"purposes, you need fewer access servers."
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts-domain-management.xml6(title)
-msgid "Domains"
-msgstr "Domaines"
-
-#: ./doc/common/section_keystone-concepts-domain-management.xml7(para)
+#: ./doc/common/section_objectstorage-arch.xml32(para)
 msgid ""
-"A domain defines administrative boundaries for the management of Identity "
-"entities. A domain may represent an individual, company, or operator-owned "
-"space. It is used for exposing administrative activities directly to the "
-"system users."
+"Since this is an HTTP addressable storage service, you may incorporate a "
+"load balancer into the access tier."
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts-domain-management.xml10(para)
+#: ./doc/common/section_objectstorage-arch.xml34(para)
 msgid ""
-"A domain is a collection of tenants, users, and roles. Users may be given a "
-"domain's administrator role. A domain administrator may create tenants, "
-"users, and groups within a domain and assign roles to users and groups."
+"Typically, the tier consists of a collection of 1U servers. These machines "
+"use a moderate amount of RAM and are network I/O intensive. Since these "
+"systems field each incoming API request, you should provision them with two "
+"high-throughput (10GbE) interfaces - one for the incoming \"front-end\" "
+"requests and the other for the \"back-end\" access to the object storage "
+"nodes to put and fetch data."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_get_console.xml6(title)
-msgid "Access an instance through a console"
+#: ./doc/common/section_objectstorage-arch.xml40(title)
+#: ./doc/common/section_objectstorage-arch.xml69(title)
+msgid "Factors to consider"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_get_console.xml7(para)
+#: ./doc/common/section_objectstorage-arch.xml41(para)
 msgid ""
-"To access an instance through a VNC console, run the following command:"
+"For most publicly facing deployments as well as private deployments "
+"available across a wide-reaching corporate network, you use SSL to encrypt "
+"traffic to the client. SSL adds significant processing load to establish "
+"sessions between clients, which is why you have to provision more capacity "
+"in the access layer. SSL may not be required for private deployments on "
+"trusted networks."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_get_console.xml8(replaceable)
-#: ./doc/common/section_cli_nova_startstop.xml14(replaceable)
-#: ./doc/common/section_cli_nova_startstop.xml18(replaceable)
-#: ./doc/common/section_cli_nova_startstop.xml35(replaceable)
-#: ./doc/common/section_cli_nova_startstop.xml40(replaceable)
-#: ./doc/common/section_cli_nova_boot.xml188(replaceable)
-msgid "INSTANCE_NAME"
-msgstr ""
+#: ./doc/common/section_objectstorage-arch.xml49(title)
+msgid "Storage nodes"
+msgstr "Noeuds de stockage"
 
-#: ./doc/common/section_cli_nova_get_console.xml9(para)
-msgid "The command returns a URL from which you can access your instance:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_get_console.xml15(para)
+#: ./doc/common/section_objectstorage-arch.xml50(para)
 msgid ""
-"To access an instance through a non-VNC console, specify the "
-"<parameter>novnc</parameter> parameter instead of the "
-"<parameter>xvpvnc</parameter> parameter."
+"In most configurations, each of the five zones should have an equal amount "
+"of storage capacity. Storage nodes use a reasonable amount of memory and "
+"CPU. Metadata needs to be readily available to return objects quickly. The "
+"object stores run services not only to field incoming requests from the "
+"access tier, but to also run replicators, auditors, and reapers. You can "
+"provision object stores provisioned with single gigabit or 10 gigabit "
+"network interface depending on the expected workload and desired "
+"performance."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-arch.xml57(title)
+#: ./doc/common/section_objectstorage-characteristics.xml46(title)
+#: ./doc/common/section_storage-concepts.xml21(td)
+msgid "Object Storage (swift)"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-arch.xml64(para)
+msgid ""
+"Currently, a 2TB or 3TB SATA disk delivers good performance for the price. "
+"You can use desktop-grade drives if you have responsive remote hands in the "
+"datacenter and enterprise-grade drives if you don't."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-arch.xml70(para)
+msgid ""
+"You should keep in mind the desired I/O performance for single-threaded "
+"requests . This system does not use RAID, so a single disk handles each "
+"request for an object. Disk performance impacts single-threaded response "
+"rates."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-arch.xml73(para)
+msgid ""
+"To achieve apparent higher throughput, the object storage system is designed"
+" to handle concurrent uploads/downloads. The network I/O capacity (1GbE, "
+"bonded 1GbE pair, or 10GbE) should match your desired concurrent throughput "
+"needs for reads and writes."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_example_usage.xml6(title)
+msgid "keystone command-line client example usage"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_example_usage.xml7(para)
+msgid ""
+"Before you can use keystone client commands, you must download and source an"
+" OpenStack RC file. For information, see the <citetitle>OpenStack Admin User"
+" Guide</citetitle>."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_example_usage.xml10(para)
+msgid "The keystone command-line client uses the following syntax:"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_example_usage.xml12(replaceable)
+msgid "PARAMETER"
+msgstr "PARAMETER"
+
+#: ./doc/common/section_cli_keystone_example_usage.xml12(replaceable)
+msgid "ARGUMENT"
+msgstr "ARGUMENT"
+
+#: ./doc/common/section_cli_keystone_example_usage.xml13(para)
+msgid ""
+"For example, you can run the <placeholder-1/> and <placeholder-2/> commands,"
+" as follows:"
+msgstr "Par exemple, vous pouvez exécuter les commandes <placeholder-1/> et <placeholder-2/>, comme suit:"
+
+#: ./doc/common/section_cli_keystone_example_usage.xml22(replaceable)
+#: ./doc/common/section_cli_keystone_example_usage.xml23(replaceable)
+msgid "token"
+msgstr "jeton"
+
+#: ./doc/common/section_cli_keystone_example_usage.xml22(replaceable)
+#: ./doc/common/section_cli_keystone_example_usage.xml23(replaceable)
+msgid "endpoint"
+msgstr "Point de terminaison"
+
+#: ./doc/common/section_cli_keystone_example_usage.xml31(replaceable)
+msgid "id"
+msgstr "id"
+
+#: ./doc/common/section_cli_keystone_example_usage.xml34(para)
+msgid ""
+"For information about using the keystone client commands to create and "
+"manage users, roles, and projects, see the <citetitle>OpenStack Admin User "
+"Guide</citetitle>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml5(title)
+msgid "Manage bare-metal nodes"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml6(para)
+msgid ""
+"The bare-metal driver for OpenStack Compute manages provisioning of physical"
+" hardware by using common cloud APIs and tools such as Orchestration (Heat)."
+" The use case for this driver is for single tenant clouds such as a high-"
+"performance computing cluster or for deploying OpenStack itself."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml10(para)
+msgid ""
+"If you use the bare-metal driver, you must create a network interface and "
+"add it to a bare-metal node. Then, you can launch an instance from a bare-"
+"metal image."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml13(para)
+msgid ""
+"Development efforts are focused on moving the driver out of the Compute code"
+" base in the Icehouse release."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml15(para)
+msgid ""
+"You can list and delete bare-metal nodes. When you delete a node, any "
+"associated network interfaces are removed. You can list and remove network "
+"interfaces that are associated with a bare-metal node."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml19(title)
+msgid "Commands"
+msgstr "Commandes"
+
+#: ./doc/common/section_cli_nova_baremetal.xml20(para)
+msgid "The following commands can be used to manage bare-metal nodes."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml22(para)
+msgid "<placeholder-1/>. Adds a network interface to a bare-metal node."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml26(para)
+msgid ""
+"<placeholder-1/>. Lists network interfaces associated with a bare-metal "
+"node."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml30(para)
+msgid "<placeholder-1/>. Removes a network interface from a bare-metal node."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml34(para)
+msgid "<placeholder-1/>. Creates a bare-metal node."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml38(para)
+msgid ""
+"<placeholder-1/>. Removes a bare-metal node and any associated interfaces."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml42(para)
+msgid "<placeholder-1/>. Lists available bare-metal nodes."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml46(para)
+msgid "<placeholder-1/>. Shows information about a bare-metal node."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml51(title)
+msgid "Create a bare-metal node"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml52(para)
+msgid ""
+"When you create a bare-metal node, your PM address, username, and password "
+"should match those that are configured in your hardware's BIOS/IPMI "
+"configuration."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml57(para)
+msgid ""
+"The following example shows the command and results from creating a node "
+"with the PM address <filename>1.2.3.4</filename>, the PM username "
+"<literal>ipmi</literal>, and password <literal>ipmi</literal>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml79(title)
+msgid "Add a network interface to the node:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml80(para)
+msgid ""
+"For each NIC on the node, you must create an interface, specifying the "
+"interface's MAC address."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml92(title)
+msgid "Launch an instance from a bare-metal image:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml94(para)
+msgid ""
+"A bare-metal instance is an instance created directly on a physical machine "
+"without any virtualization layer running underneath it. Nova retains power "
+"control via IPMI. In some situations, Nova may retain network control via "
+"Neutron and OpenFlow."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml107(para)
+msgid ""
+"Set the <parameter>--availability_zone</parameter> parameter to specify "
+"which zone or node to use to start the server. Separate the zone from the "
+"host name with a comma. For example:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml110(replaceable)
+msgid "HOST"
+msgstr "HOST"
+
+#: ./doc/common/section_cli_nova_baremetal.xml110(replaceable)
+msgid "NODE"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml111(para)
+msgid ""
+"<literal>host</literal> is optional for the "
+"<literal>--availability_zone</literal> parameter. You can specify simply "
+"<literal>zone:,node</literal>. You must still use the comma."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml118(title)
+msgid "List bare-metal nodes and interfaces:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml120(para)
+msgid ""
+"Use the <placeholder-1/> command to view all bare-metal nodes and "
+"interfaces. When a node is in use, its status includes the UUID of the "
+"instance that runs on it:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml130(title)
+msgid "Show details for a bare-metal node:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml131(para)
+msgid ""
+"Use the <placeholder-1/> command to view the details for a bare-metal node."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml6(title)
+msgid "Troubleshoot the Identity service"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml7(para)
+msgid ""
+"To troubleshoot the Identity service, review the logs in the "
+"<filename>/var/log/keystone/keystone.log</filename> file."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml10(para)
+msgid ""
+"Use the <filename>/etc/keystone/logging.conf</filename> file to configure "
+"the location of log files."
+msgstr "Utilisez le fichier <filename>/etc/keystone/logging.conf</filename> pour configurer la location des fichiers journaux. "
+
+#: ./doc/common/section_identity-troubleshooting.xml13(para)
+msgid ""
+"The logs show the components that have come in to the WSGI request, and "
+"ideally show an error that explains why an authorization request failed. If "
+"you do not see the request in the logs, run keystone with "
+"<parameter>--debug</parameter> parameter. Pass the "
+"<parameter>--debug</parameter> parameter before the command parameters."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml20(title)
+msgid "Debug PKI middleware"
+msgstr "Déboguer l'intergiciel PKI."
+
+#: ./doc/common/section_identity-troubleshooting.xml21(para)
+msgid ""
+"If you receive an <literal>Invalid OpenStack Identity Credentials</literal> "
+"message when you talk to an OpenStack service, it might be caused by the "
+"changeover from UUID tokens to PKI tokens in the Grizzly release. Learn how "
+"to troubleshoot this error."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml26(para)
+msgid ""
+"The PKI-based token validation scheme relies on certificates from Identity "
+"that are fetched through HTTP and stored in a local directory. The location "
+"for this directory is specified by the <literal>signing_dir</literal> "
+"configuration option. In your services configuration file, look for a "
+"section like this:"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml41(para)
+msgid ""
+"If your service lacks this stanza, the <link "
+"href=\"https://github.com/openstack/python-"
+"keystoneclient/blob/master/keystoneclient/middleware/auth_token.py#L198\">keystoneclient/middleware/auth_token.py</link>"
+" file specifies the defaults. If no value is specified for this directory, "
+"it <link href=\"https://github.com/openstack/python-"
+"keystoneclient/blob/master/keystoneclient/middleware/auth_token.py#L299\">defaults"
+" to a secure temporary directory.</link> Initialization code for the service"
+" checks that the directory exists and is writable. If it does not exist, the"
+" code tries to create it. If this fails, the service fails to start. "
+"However, it often succeeds but problems occur later."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml53(para)
+msgid ""
+"The first thing to check is that the <literal>signing_dir</literal> does, in"
+" fact, exist. If it does, check for the presence of the certificate files "
+"inside there:"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml64(para)
+msgid ""
+"This directory contains two certificates and the token revocation list. If "
+"these files are not present, your service cannot fetch them from Identity. "
+"To troubleshoot, try to talk to Identity to make sure it correctly serves "
+"files, as follows:"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml70(para)
+msgid "This command fetches the signing certificate:"
+msgstr "Cette commande récupère le certificat de signature:"
+
+#: ./doc/common/section_identity-troubleshooting.xml81(para)
+msgid "Note the expiration dates of the certificate:"
+msgstr "Notez les dates d'expiration du certificat:"
+
+#: ./doc/common/section_identity-troubleshooting.xml84(para)
+msgid ""
+"The token revocation list is updated once a minute, but the certificates are"
+" not. One possible problem is that the certificates are the wrong files or "
+"garbage. You can remove these files and run another command against your "
+"server: They are fetched on demand."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml89(para)
+msgid ""
+"The Identity service log should show the access of the certificate files. "
+"You might have to turn up your logging levels. Set <literal>debug = "
+"True</literal> and <literal>verbose = True</literal> in your Identity "
+"configuration file and restart the Identity server."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml98(para)
+msgid ""
+"If the files do not appear in your directory after this, it is likely one of"
+" the following issues:"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml102(para)
+msgid ""
+"Your service is configured incorrectly and cannot talk to Identity. Check "
+"the <literal>auth_port</literal> and <literal>auth_host</literal> values and"
+" make sure that you can talk to that service through cURL, as shown "
+"previously."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml110(para)
+msgid ""
+"Your signing directory is not writable. Use the <placeholder-1/> command to "
+"change its permissions so that the service (POSIX) user can write to it. "
+"Verify the change through <placeholder-2/> and <placeholder-3/> commands."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml118(para)
+msgid "The SELinux policy is denying access to the directory."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml122(para)
+msgid ""
+"SELinux troubles often occur when you use Fedora/RHEL-based packages and you"
+" choose configuration options that do not match the standard policy. Run the"
+" <placeholder-1/> command. If that makes a difference, you should relabel "
+"the directory. If you are using a sub-directory of the "
+"<filename>/var/cache/</filename> directory, run the following command:"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml131(para)
+msgid ""
+"If you are not using a <filename>/var/cache</filename> sub-directory, you "
+"should. Modify the <literal>signing_dir</literal> configuration option for "
+"your service and restart."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml135(para)
+msgid ""
+"Set back to <literal>setenforce enforcing</literal> to confirm that your "
+"changes solve the problem."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml137(para)
+msgid ""
+"If your certificates are fetched on demand, the PKI validation is working "
+"properly. Most likely, the token from Identity is not valid for the "
+"operation you are attempting to perform, and your user needs a different "
+"role for the operation."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml144(title)
+msgid "Debug signing key file errors"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml145(para)
+msgid ""
+"If an error occurs when the signing key file opens, it is possible that the "
+"person who ran the <placeholder-1/> command to generate certificates and "
+"keys did not use the correct user. When you run the <placeholder-2/> "
+"command, Identity generates a set of certificates and keys in "
+"<filename>/etc/keystone/ssl*</filename>, which is owned by root:root."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml154(para)
+msgid ""
+"This can present a problem when you run the Identity daemon under the "
+"keystone user account (nologin) when you try to run PKI. Unless you run the "
+"<placeholder-1/> command against the files keystone:keystone or run the "
+"<placeholder-2/> command with the <parameter>--keystone-user</parameter> and"
+" <parameter>--keystone-group</parameter> parameters, you get an error, as "
+"follows:"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml172(title)
+msgid "Flush expired tokens from the token database table"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml174(para)
+msgid ""
+"As you generate tokens, the token database table on the Identity server "
+"grows. To clear the token table, an administrative user must run the "
+"<placeholder-1/> command to flush the tokens. When you flush tokens, expired"
+" tokens are deleted and traceability is eliminated."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml180(para)
+msgid ""
+"Use <placeholder-1/> to schedule this command to run frequently based on "
+"your workload. For large workloads, running it every minute is recommended."
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml5(title)
+msgid "Database service overview"
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml6(para)
+msgid ""
+"The Database service provides scalable and reliable cloud provisioning "
+"functionality for both relational and non-relational database engines. Users"
+" can quickly and easily utilize database features without the burden of "
+"handling complex administrative tasks. Cloud users and database "
+"administrators can provision and manage multiple database instances as "
+"needed."
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml7(para)
+msgid ""
+"The Database service provides resource isolation at high performance levels,"
+" and automates complex administrative tasks such as deployment, "
+"configuration, patching, backups, restores, and monitoring."
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml9(title)
+msgid "Process flow example."
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml9(para)
+msgid "Here is a high-level process flow example for using Database services:"
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml12(para)
+msgid "Administrator sets up infrastructure:"
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml15(para)
+msgid "OpenStack administrator installs the Database service."
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml18(para)
+msgid ""
+"She creates one image for each type of database the administrator wants to "
+"have (one for MySQL, one for MongoDB, and so on)."
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml23(para)
+msgid ""
+"OpenStack administrator updates the datastore to use the new images, using "
+"the <placeholder-1/> command."
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml30(para)
+msgid "End user uses database service:"
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml33(para)
+msgid ""
+"Now that the basic infrastructure is set up, an end user can create a Trove "
+"instance (database) whenever the user wants, using the <placeholder-1/> "
+"command."
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml41(replaceable)
+msgid "instanceID"
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml39(para)
+msgid ""
+"The end user gets the IP address of the Trove instance by using the "
+"<placeholder-1/> command to get the ID of the instance, and then using the "
+"<placeholder-2/> command to get the IP address."
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml44(para)
+msgid ""
+"The end user can now access the Trove instance using typical database access"
+" commands. MySQL example:"
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml45(replaceable)
+msgid "trove_ip_address"
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml51(title)
+msgid "Components:"
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml51(para)
+msgid "The Database service includes the following components:"
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml55(para)
+msgid ""
+"<code>python-troveclient</code> command-line client. A CLI that communicates"
+" with the <code>trove-api</code> component."
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml58(para)
+msgid ""
+"<code>trove-api</code> component. Provides an OpenStack-native RESTful API "
+"that supports JSON to provision and manage Trove instances."
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml62(para)
+msgid ""
+"<code>trove-conductor</code> service. Runs on the host, and receives "
+"messages from guest instances that want to update information on the host."
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml65(para)
+msgid ""
+"<code>trove-taskmanager</code> service. Instruments the complex system flows"
+" that support provisioning instances, managing the lifecycle of instances, "
+"and performing operations on instances."
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml68(para)
+msgid ""
+"<code>trove-guestagent</code> service. Runs within the guest instance. "
+"Manages and performs operations on the database itself."
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml6(title)
+msgid "Migrate the Identity Service database"
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml7(para)
+msgid ""
+"Between revisions of the Identity Service project, you might need to "
+"complete SQL migrations. The Identity Service project uses SQLAlchemy-"
+"migrate (see <link href=\"http://code.google.com/p/sqlalchemy-"
+"migrate/\">http://code.google.com/p/sqlalchemy-migrate/</link>) to migrate "
+"the SQL database between revisions. For core components, the source code "
+"stores migrations in a central repository under a "
+"<filename>keystone/common/sql/migrate_repo</filename> directory."
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml17(para)
+msgid ""
+"Extensions to the Identity Service might also require SQL migrations. The "
+"directory <filename>keystone/contrib/example</filename> in the keystone "
+"repository contains a sample extension migration."
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml23(title)
+msgid "To set up a migration for an extension"
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml25(para)
+msgid ""
+"Create a directory structure where <literal>my_extension</literal> is the "
+"name of the extension, as follows: "
+"<filename>keystone/contrib/my_extension/migrate_repo/versions/</filename>."
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml31(para)
+msgid ""
+"Create empty <filename>__init__.py</filename> files in the "
+"<filename>migrate_repo</filename> and <filename>versions</filename> "
+"subdirectories."
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml37(para)
+msgid ""
+"Create a <filename>migrate.cfg</filename> configuration file in the "
+"<filename>migrate_repo</filename> subdirectory, which conforms to a "
+"key/value <filename>.ini</filename> file format."
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml41(para)
+msgid "An example configuration file:"
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml49(title)
+msgid "To test a migration for a specific extension"
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml50(para)
+msgid ""
+"You can use the <placeholder-1/> command with the "
+"<parameter>--extension</parameter> parameter for both the <placeholder-2/> "
+"and <placeholder-3/> commands. Ensure that the required configuration files "
+"exist before completing these steps."
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml57(para)
+msgid "Test your migrations with an <literal>example</literal> extension:"
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml62(para)
+msgid "Migrate to version 1:"
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml66(para)
+msgid "Migrate back to version 0:"
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml70(para)
+msgid "Check the version:"
+msgstr "Vérifiez la version:"
+
+#: ./doc/common/section_support-compute.xml9(title)
+msgid "Troubleshoot Compute"
+msgstr "Résoudre les problèmes Calcul"
+
+#: ./doc/common/section_support-compute.xml10(para)
+msgid ""
+"Common problems for Compute typically involve misconfigured networking or "
+"credentials that are not sourced properly in the environment. Also, most "
+"flat networking configurations do not enable <placeholder-1/> or "
+"<placeholder-2/> from a compute node to the instances that run on that node."
+" Another common problem is trying to run 32-bit images on a 64-bit compute "
+"node. This section shows you how to troubleshoot Compute."
+msgstr "Les erreurs fréquentes avec Calcul impliquent généralement un réseau mal configuré ou des identifiants qui ne sont pas correctement sourcés dans l'environnement. De plus, la plupart des configurations de réseaux plats ne permettent pas de <placeholder-1/> or <placeholder-2/> à partir d'un nœud de calcul pour les instances en cours d'exécution sur ce nœud. Un autre problème fréquent est d'essayer d'exécuter des images 32 bits sur un nœud de calcul 64-bit. Cette section propose plus d'informations sur la façon de résoudre les problèmes de Calcul."
+
+#: ./doc/common/section_support-compute.xml19(title)
+msgid "Compute service logging"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml20(para)
+msgid ""
+"Compute stores a log file for each service in "
+"<filename>/var/log/nova</filename>. For example, <filename>nova-"
+"compute.log</filename> is the log for the <systemitem class=\"service"
+"\">nova-compute</systemitem> service. You can set the following options to "
+"format log strings for the nova.log module in the "
+"<filename>nova.conf</filename> file:"
+msgstr "Les fichiers Log sont stockés dans <filename>/var/log/nova</filename> et il y a un fichier log pour chaque service, par exemple <filename>nova-compute.log</filename>. Vous pouvez formater les chaines log en utilisant les options pour le nova.log module. Les options utilisées pour définir les chaînes de format sont : "
+
+#: ./doc/common/section_support-compute.xml29(literal)
+msgid "logging_context_format_string"
+msgstr "logging_context_format_string"
+
+#: ./doc/common/section_support-compute.xml32(literal)
+msgid "logging_default_format_string"
+msgstr "logging_default_format_string"
+
+#: ./doc/common/section_support-compute.xml35(para)
+msgid ""
+"If the log level is set to <literal>debug</literal>, you can also specify "
+"<literal>logging_debug_format_suffix</literal> to append extra formatting. "
+"For information about what variables are available for the formatter see: "
+"<link "
+"href=\"http://docs.python.org/library/logging.html#formatter\">http://docs.python.org/library/logging.html#formatter</link>."
+msgstr "Si le niveau de journalisation est défini sur <literal>debug</literal>, vous pouvez également spécifier <literal>logging_debug_format_suffix</literal> pour ajouter du formatage supplémentaire. Pour des informations à propos de quelles variables sont disponibles pour le formatteur : <link href=\"http://docs.python.org/library/logging.html#formatter\">http://docs.python.org/library/logging.html#formatter</link>."
+
+#: ./doc/common/section_support-compute.xml42(para)
+msgid ""
+"You have two options for logging for OpenStack Compute based on "
+"configuration settings. In <filename>nova.conf</filename>, include the "
+"<literal>logfile</literal> option to enable logging. Alternatively you can "
+"set <literal>use_syslog = 1</literal> so that the nova daemon logs to "
+"syslog."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml50(title)
+msgid "Guru Meditation reports"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml51(para)
+msgid ""
+"A Guru Meditation report is sent by the Compute Service upon receipt of the "
+"<systemitem>SIGUSR1</systemitem> signal. This report is a general-purpose "
+"error report, including a complete report of the service's current state, "
+"and is sent to <systemitem>stderr</systemitem>."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml55(para)
+msgid ""
+"For example, if you redirect error output to <filename>nova-api-"
+"err.log</filename> using <placeholder-1/>, resulting in the process ID 8675,"
+" you can then run:"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml59(para)
+msgid ""
+"This command triggers the Guru Meditation report to be printed to "
+"<filename>/var/log/nova/nova-api-err.log</filename>."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml63(para)
+msgid ""
+"Package Displays information about the package to which the process belongs,"
+" including version information."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml65(para)
+msgid ""
+"Threads Displays stack traces and thread IDs for each of the threads within "
+"the process."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml67(para)
+msgid ""
+"Green Threads Displays stack traces for each of the green threads within the"
+" process (green threads do not have thread IDs)."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml69(para)
+msgid ""
+"Configuration Lists all configuration options currently accessible through "
+"the CONF object for the current process."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml61(para)
+msgid "The report has the following sections: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml72(para)
+msgid ""
+"For more information, see <link "
+"href=\"http://docs.openstack.org/developer/nova/devref/gmr.html\">Guru "
+"Meditation Reports</link>."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml77(title)
+msgid "Common errors and fixes for Compute"
+msgstr "Erreurs Fréquentes et Solutions pour Calcul"
+
+#: ./doc/common/section_support-compute.xml78(para)
+msgid ""
+"The <link href=\"ask.openstack.org\">ask.openstack.org</link> site offers a "
+"place to ask and answer questions, and you can also mark questions as "
+"frequently asked questions. This section describes some errors people have "
+"posted previously. Bugs are constantly being fixed, so online resources are "
+"a great way to get the most up-to-date errors and fixes."
+msgstr "Le site <link href=\"ask.openstack.org\">ask.openstack.org</link> offre un endroit où poser et répondre aux questions, et vous pouvez également annoter des questions comme fréquemment posées. Cette section décrit certaines erreurs que des personnes ont postées précédemment. Comme nous corrigeons constamment les bugs, les ressources en ligne sont un excellent moyen pour obtenir le plus de mises à jour sur les erreurs et solutions."
+
+#: ./doc/common/section_support-compute.xml86(title)
+msgid "Credential errors, 401, and 403 forbidden errors"
+msgstr "Erreurs références, 401, 403 [original] forbidden erreurs "
+
+#: ./doc/common/section_support-compute.xml93(para)
+msgid ""
+"<emphasis role=\"bold\">Manual method</emphasis>. Get get the "
+"<filename>novarc</filename> file from the project ZIP file, save existing "
+"credentials in case of override. and manually source the "
+"<filename>novarc</filename> file."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml103(para)
+msgid ""
+"<emphasis role=\"bold\">Script method</emphasis>. Generates "
+"<filename>novarc</filename> from the project ZIP file and sources it for "
+"you."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml88(para)
+msgid ""
+"Missing credentials cause a "
+"<errorcode>403</errorcode><errortext>forbidden</errortext> error. To resolve"
+" this issue, use one of these methods:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml110(para)
+msgid ""
+"When you run <systemitem class=\"service\">nova-api</systemitem> the first "
+"time, it generates the certificate authority information, including "
+"<filename>openssl.cnf</filename>. If you start the CA services before this, "
+"you might not be able to create your ZIP file. Restart the services. When "
+"your CA information is available, create your ZIP file."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml118(para)
+msgid ""
+"Also, check your HTTP proxy settings to see whether they cause problems with"
+" <filename>novarc</filename> creation."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml123(title)
+msgid "Instance errors"
+msgstr "Erreurs Instance"
+
+#: ./doc/common/section_support-compute.xml124(para)
+msgid ""
+"Sometimes a particular instance shows <literal>pending</literal> or you "
+"cannot SSH to it. Sometimes the image itself is the problem. For example, "
+"when you use flat manager networking, you do not have a DHCP server and "
+"certain images do not support interface injection; you cannot connect to "
+"them. The fix for this problem is to use an image that does support this "
+"method, such as Ubuntu, which obtains an IP address correctly with "
+"FlatManager network settings."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml134(para)
+msgid ""
+"To troubleshoot other possible problems with an instance, such as an "
+"instance that stays in a spawning state, check the directory for the "
+"particular instance under <filename>/var/lib/nova/instances</filename> on "
+"the <systemitem class=\"service\">nova-compute</systemitem> host and make "
+"sure that these files are present:"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml143(filename)
+msgid "libvirt.xml"
+msgstr "libvirt.xml"
+
+#: ./doc/common/section_support-compute.xml146(filename)
+msgid "disk"
+msgstr "disque"
+
+#: ./doc/common/section_support-compute.xml149(filename)
+msgid "disk-raw"
+msgstr "disk en format brut"
+
+#: ./doc/common/section_support-compute.xml152(filename)
+msgid "kernel"
+msgstr "noyau"
+
+#: ./doc/common/section_support-compute.xml155(filename)
+msgid "ramdisk"
+msgstr "ramdisk"
+
+#: ./doc/common/section_support-compute.xml158(para)
+msgid "After the instance starts, <filename>console.log</filename>"
+msgstr "Après le démarrage de l'instance, <filename>console.log</filename>"
+
+#: ./doc/common/section_support-compute.xml162(para)
+msgid ""
+"If any files are missing, empty, or very small, the <systemitem "
+"class=\"service\">nova-compute</systemitem> service did not successfully "
+"download the images from the Image Service."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml167(para)
+msgid ""
+"Also check <filename>nova-compute.log</filename> for exceptions. Sometimes "
+"they do not appear in the console output."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml170(para)
+msgid ""
+"Next, check the log file for the instance in the "
+"<filename>/var/log/libvirt/qemu</filename> directory to see if it exists and"
+" has any useful error messages in it."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml174(para)
+msgid ""
+"Finally, from the <filename>/var/lib/nova/instances</filename> directory for"
+" the instance, see if this command returns an error:"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml181(title)
+msgid "Empty log output for Linux instances"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml182(para)
+msgid ""
+"You can view the log output of running instances from either the "
+"<guilabel>Log</guilabel> tab of the dashboard or the output of "
+"<placeholder-1/>. In some cases, the log output of a running Linux instance "
+"will be empty or only display a single character (for example, the "
+"<keycap>?</keycap> character)."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml189(para)
+msgid ""
+"This occurs when the Compute service attempts to retrieve the log output of "
+"the instance via a serial console while the instance itself is not "
+"configured to send output to the console. To rectify this, append the "
+"following parameters to kernel arguments specified in the instance's boot "
+"loader:"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml196(para)
+msgid ""
+"Upon rebooting, the instance will be configured to send output to the "
+"Compute service."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml201(title)
+msgid "Reset the state of an instance"
+msgstr "Réinitialiser manuellement l'état d'une instance"
+
+#: ./doc/common/section_support-compute.xml202(para)
+msgid ""
+"If an instance remains in an intermediate state, such as "
+"<literal>deleting</literal>, you can use the <placeholder-1/> command to "
+"manually reset the state of an instance to an error state. You can then "
+"delete the instance. For example:"
+msgstr "Si une instance est bloquée dans un état intermédiaire <literal>deleting</literal>, vous prouver réinitialiser manuellement l'état d'une instance en utilisant la commande <placeholder-1/> . Cela va le réinitialiser à l'état d'erreur, que vous pouvez ensuite supprimer. Par example :"
+
+#: ./doc/common/section_support-compute.xml209(para)
+msgid ""
+"You can also use the <parameter>--active</parameter> parameter to force the "
+"instance back to an active state instead of an error state. For example:"
+msgstr "Vous pouvez également utiliser le --active  pour forcer l'instance à retourner à un état actif au lieu d'un état d'erreur, par exemple :"
+
+#: ./doc/common/section_support-compute.xml215(title)
+msgid "Injection problems"
+msgstr "Problèmes avec Injection"
+
+#: ./doc/common/section_support-compute.xml216(para)
+msgid ""
+"If instances do not boot or boot slowly, investigate file injection as a "
+"cause."
+msgstr "Si vous diagnostiquez un problème avec des instances qui ne démarrent pas, ou lentement, considérez le fichier injection la cause et vérifiez le. "
+
+#: ./doc/common/section_support-compute.xml218(para)
+msgid ""
+"To disable injection in libvirt, set the following in "
+"<filename>nova.conf</filename>:"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml223(para)
+msgid ""
+"If you have not enabled the configuration drive and you want to make user-"
+"specified files available from the metadata server for to improve "
+"performance and avoid boot failure if injection fails, you must disable "
+"injection."
 msgstr ""
 
 #: ./doc/common/section_getstart_telemetry.xml5(title)
@@ -11095,188 +11082,2362 @@ msgid ""
 "collector and API server have access to the data store."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml6(title)
-msgid "Install XenServer and XCP"
+#: ./doc/common/section_cli_cinder_read-only-volumes.xml6(title)
+msgid "Set a volume to read-only access"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml8(para)
+#: ./doc/common/section_cli_cinder_read-only-volumes.xml7(para)
 msgid ""
-"Before you can run OpenStack with XCP or XenServer, you must install the "
-"software on <link "
-"href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/installation.html#sys_requirements\">an"
-" appropriate server</link>."
+"To give multiple users shared, secure access to the same data, you can set a"
+" volume to read-only access."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml13(para)
-msgid ""
-"Xen is a type 1 hypervisor: When your server starts, Xen is the first "
-"software that runs. Consequently, you must install XenServer or XCP before "
-"you install the operating system where you want to run OpenStack code. The "
-"OpenStack services then run in a virtual machine that you install on top of "
-"XenServer."
+#: ./doc/common/section_cli_cinder_read-only-volumes.xml9(para)
+msgid "Run the following command to set a volume to read-only access:"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml20(para)
-msgid ""
-"Before you can install your system, decide whether to install a free or paid"
-" edition of Citrix XenServer or Xen Cloud Platform from Xen.org. Download "
-"the software from these locations:"
+#: ./doc/common/section_cli_cinder_read-only-volumes.xml11(replaceable)
+msgid "VOLUME"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml28(link)
-msgid "http://www.citrix.com/XenServer/download"
-msgstr "http://www.citrix.com/XenServer/download"
-
-#: ./doc/common/section_xen-install.xml33(link)
-msgid "http://www.xen.org/download/xcp/index.html"
-msgstr "http://www.xen.org/download/xcp/index.html"
-
-#: ./doc/common/section_xen-install.xml36(para)
-msgid ""
-"When you install many servers, you might find it easier to perform <link "
-"href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/installation.html#pxe_boot_install\">PXE"
-" boot installations of XenServer or XCP</link>. You can also package any "
-"post-installation changes that you want to make to your XenServer by <link "
-"href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/supplemental_pack_ddk.html\">creating"
-" your own XenServer supplemental pack</link>."
+#: ./doc/common/section_cli_cinder_read-only-volumes.xml11(replaceable)
+msgid "BOOLEAN"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml46(para)
+#: ./doc/common/section_cli_cinder_read-only-volumes.xml12(para)
 msgid ""
-"You can also install the <package>xcp-xenapi</package> package on Debian-"
-"based distributions to get XCP. However, this is not as mature or feature "
-"complete as above distributions. This modifies your boot loader to first "
-"boot Xen and boot your existing OS on top of Xen as Dom0. The xapi daemon "
-"runs in Dom0. Find more details at <link "
-"href=\"http://wiki.xen.org/wiki/Project_Kronos\">http://wiki.xen.org/wiki/Project_Kronos</link>."
+"<replaceable>VOLUME</replaceable> is the ID of the target volume and "
+"<replaceable>BOOLEAN</replaceable> is a flag that enables read-only or "
+"read/write access to the volume."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml55(para)
-msgid ""
-"Make sure you use the EXT type of storage repository (SR). Features that "
-"require access to VHD files (such as copy on write, snapshot and migration) "
-"do not work when you use the LVM SR. Storage repository (SR) is a XenAPI-"
-"specific term relating to the physical storage where virtual disks are "
-"stored."
-msgstr "Assurez-vous que vous utilisez le type EXT de référentiel de stockage (SR). Les fonctions qui nécessitent l'accès à des fichiers VHD (telles que la copie sur écriture, instantané et migration) ne fonctionnent pas lorsque vous utilisez LVM SR. Le référentiel de stockage (SR) est un terme spécifique XenAPI relatives au stockage physique où les disques virtuels sont stockés."
-
-#: ./doc/common/section_xen-install.xml61(para)
-msgid ""
-"On the XenServer/XCP installation screen, choose the <guilabel>XenDesktop "
-"Optimized</guilabel> option. If you use an answer file, make sure you use "
-"<literal>srtype=\"ext\"</literal> in the <option>installation</option> tag "
-"of the answer file."
+#: ./doc/common/section_cli_cinder_read-only-volumes.xml15(para)
+msgid "The following values for <replaceable>BOOLEAN</replaceable> are valid:"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml69(title)
-msgid "Post-installation steps"
+#: ./doc/common/section_cli_cinder_read-only-volumes.xml19(para)
+msgid ""
+"<literal>true</literal>. Sets the read-only flag in the volume. When you "
+"attach the volume to an instance, the instance checks for this flag to "
+"determine whether to restrict volume access to read-only."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml70(para)
-msgid "Complete these steps to install OpenStack in your XenServer system:"
+#: ./doc/common/section_cli_cinder_read-only-volumes.xml25(para)
+msgid "<literal>false</literal>. Sets the volume to read/write access."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml74(para)
+#: ./doc/common/section_compute-configure-ec2.xml6(title)
+msgid "Configure the EC2 API"
+msgstr "Configurer l’API EC2"
+
+#: ./doc/common/section_compute-configure-ec2.xml7(para)
 msgid ""
-"For resize and migrate functionality, complete the changes described in the "
-"<citetitle>Configure resize</citetitle> section in the <link href"
-"=\"../config-reference/content/index.html\"><citetitle>OpenStack "
-"Configuration Reference</citetitle></link>."
+"You can set options in the <filename>nova.conf</filename> configuration file"
+" to control which network address and port the EC2 API listens on, the "
+"formatting of some API responses, and authentication related options."
+msgstr "Vous pouvez utiliser les options de configuration de <filename>nova.conf</filename> pour contrôler à quelle adresse réseau et sur quel port l’API EC2 écoutera, le formatage de certaines réponses API et des options ayant trait à l’authentification."
+
+#: ./doc/common/section_compute-configure-ec2.xml11(para)
+msgid ""
+"To customize these options for OpenStack EC2 API, use the configuration "
+"option settings documented in <xref linkend=\"config_table_nova_ec2\"/>."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml82(para)
-msgid ""
-"Install the VIF isolation rules to help prevent mac and IP address spoofing."
+#: ./doc/common/section_cli_keystone_credentials.xml6(title)
+msgid "Set up credentials for the keystone client"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml86(para)
-msgid "Install the XenAPI plug-ins. See the following section."
+#: ./doc/common/section_cli_keystone_credentials.xml7(para)
+msgid ""
+"You can configure the <package>python-keystoneclient</package> with admin "
+"credentials with either an authentication token or a user name and password."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml90(para)
-msgid ""
-"To support AMI type images, you must set up <literal>/boot/guest</literal> "
-"symlink/directory in Dom0. For detailed instructions, see next section."
-msgstr "Afin de supporter les images de types AMI, il est nécessaire de régler <literal>/boot/guest</literal> symlink/directory dans Dom0. Pour des instructions plus détaillées, voir la prochaine section."
+#: ./doc/common/section_cli_keystone_credentials.xml12(title)
+msgid "To configure the keystone client with an authentication token"
+msgstr "Pour configurer le client keystone avec un jeton d'authentification"
 
-#: ./doc/common/section_xen-install.xml96(para)
+#: ./doc/common/section_cli_keystone_credentials.xml15(para)
 msgid ""
-"To support resize/migration, set up an ssh trust relation between your "
-"XenServer hosts, and ensure <literal>/images</literal> is properly set up. "
-"See next section for more details."
-msgstr "Afin de supportef la redimension/migration, établissez une relation de confiance ssh avec les hôtes XenServer, et assurez-vous que <literal>/images</literal> est correctement réglé. Voir la prochaine section pour plus de détails."
-
-#: ./doc/common/section_xen-install.xml102(para)
-msgid ""
-"Create a Paravirtualized virtual machine that can run the OpenStack compute "
-"code."
-msgstr "Créez une machine virtuelle Paravirtualisée qui puissant lancer le code de calcul OpenStack."
-
-#: ./doc/common/section_xen-install.xml106(para)
-msgid ""
-"Install and configure the <systemitem class=\"service\">nova-"
-"compute</systemitem> in the above virtual machine."
-msgstr "Installez et configurer le <systemitem class=\"service\">nova-compute</systemitem> dans la machine précitée."
-
-#: ./doc/common/section_xen-install.xml111(para)
-msgid ""
-"For more information, see how DevStack performs the last three steps for "
-"developer deployments. For more information about DevStack, see "
-"<citetitle>Getting Started With XenServer and Devstack</citetitle> (<link "
-"href=\"https://github.com/openstack-"
-"dev/devstack/blob/master/tools/xen/README.md\">https://github.com/openstack-"
-"dev/devstack/blob/master/tools/xen/README.md</link>). Find more information "
-"about the first step, see <citetitle>Multi Tenancy Networking Protections in"
-" XenServer</citetitle> (<link "
-"href=\"https://github.com/openstack/nova/blob/master/plugins/xenserver/doc/networking.rst\">https://github.com/openstack/nova/blob/master/plugins/xenserver/doc/networking.rst</link>)."
-" For information about how to install the XenAPI plug-ins, see "
-"<citetitle>XenAPI README</citetitle> (<link "
-"href=\"https://github.com/openstack/nova/blob/master/plugins/xenserver/xenapi/README\">https://github.com/openstack/nova/blob/master/plugins/xenserver/xenapi/README</link>)."
+"Export your keystone endpoint to the <varname>OS_SERVICE_ENDPOINT</varname> "
+"environment variable:"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml131(title)
-msgid "Xen boot from ISO"
-msgstr "Charger Xen à partir d'un ISO"
-
-#: ./doc/common/section_xen-install.xml132(para)
+#: ./doc/common/section_cli_keystone_credentials.xml21(para)
 msgid ""
-"XenServer, through the XenAPI integration with OpenStack, provides a feature"
-" to boot instances from an ISO file. To activate the Boot From ISO feature, "
-"you must configure the SR elements on XenServer host, as follows:"
-msgstr "XenServer, par l'intégration de XenAPI avec OpenStack, fourni une fonction permettant le chargement d'instances à partir d'un fichier ISO. Pour activer la fonction “Chargement à partir de l'ISO”, il vous faut configurer les éléments SR sur l'hôte XenServer de la manière suivante:"
+"Export the administrator service token to the "
+"<varname>OS_SERVICE_TOKEN</varname> environment variable:"
+msgstr ""
 
-#: ./doc/common/section_xen-install.xml139(para)
+#: ./doc/common/section_cli_keystone_credentials.xml26(para)
+#: ./doc/common/section_cli_keystone_credentials.xml80(para)
 msgid ""
-"Create an ISO-typed SR, such as an NFS ISO library, for instance. For this, "
-"using XenCenter is a simple method. You must export an NFS volume from a "
-"remote NFS server. Make sure it is exported in read-write mode."
-msgstr "Créez un SR de type ISO, comme une bibliothèque NFS ISO par exemple. Pour se faire, la manière la plus simple sera d'utiliser XenCenter. Vous devez exporter un volume NFS   d'un serveur distant NFS. Vérifiez  que celui-ci est exporté en mode lecture/écriture."
+"Alternatively, you can specify these parameters on any keystone client "
+"command:"
+msgstr "Alternativement, vous pouvez spécifier ces paramètres sur un client de commande keystone:"
 
-#: ./doc/common/section_xen-install.xml146(para)
-msgid "On the compute host, find and record the uuid of this ISO SR:"
-msgstr "2.\tSur l'ordinateur hôte, trouver l'uuid de cette ISO SR et notez-le."
-
-#: ./doc/common/section_xen-install.xml151(para)
-msgid "Locate the uuid of the NFS ISO library:"
-msgstr "Localisez l'uuid de la bibliothèque NFS ISO:"
-
-#: ./doc/common/section_xen-install.xml155(para)
+#: ./doc/common/section_cli_keystone_credentials.xml30(para)
 msgid ""
-"Set the uuid and configuration. Even if an NFS mount point is not local, you"
-" must specify <literal>local-storage-iso</literal>."
-msgstr "Définissez l'uuid et la configuration. Même si un point de montage NFS n'est pas un stockage local, il faudra spécifier <literal>local-storage-iso</literal>."
+"<parameter>--os-endpoint "
+"<replaceable>SERVICE_ENDPOINT</replaceable></parameter>. An endpoint to use "
+"instead of the one in the service catalog. Defaults to "
+"<code>env[OS_SERVICE_ENDPOINT]</code>."
+msgstr ""
 
-#: ./doc/common/section_xen-install.xml161(para)
+#: ./doc/common/section_cli_keystone_credentials.xml39(para)
 msgid ""
-"Make sure the host-uuid from <literal>xe pbd-list</literal> equals the uuid "
-"of the host you found previously:"
-msgstr "Vérifiez que l'hôte uuid de <literal>xe pbd-list</literal> est équivalent à l'uuid de l'hôte que vous avez trouvé précédemment:"
+"<parameter>--os-token <replaceable>SERVICE_TOKEN</replaceable></parameter>. "
+"An existing token to use instead of the one generated by authentication. "
+"Defaults to <code>env[OS_SERVICE_TOKEN]</code>."
+msgstr ""
 
-#: ./doc/common/section_xen-install.xml167(para)
+#: ./doc/common/section_cli_keystone_credentials.xml52(title)
+msgid "To configure the keystone client with a user name and password"
+msgstr "Pour configurer le client keystone avec un nom d'utilisateur et un mot de passe"
+
+#: ./doc/common/section_cli_keystone_credentials.xml55(para)
 msgid ""
-"You can now add images through the OpenStack Image Service with <literal"
-">disk-format=iso</literal>, and boot them in OpenStack Compute:"
-msgstr "Vous pouvez maintenant ajouter des images via le Répertoire d'Image OpenStack, avec <literal>disk-format=iso</literal> et les lancer dans OpenStack Compute."
+"Export the administrator user name to the <varname>OS_USERNAME</varname> "
+"environment variable:"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_credentials.xml61(para)
+msgid ""
+"Export the administrator password to the <varname>OS_PASSWORD</varname> "
+"environment variable:"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_credentials.xml67(para)
+msgid ""
+"Export the tenant name to the <varname>OS_TENANT_NAME</varname> environment "
+"variable:"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_credentials.xml73(para)
+msgid ""
+"Export the URL of the keystone auth server, for example <link "
+"href=\"http://localhost:5000/v2.0'\">http://localhost:5000/v2.0'</link>, to "
+"the <varname>OS_AUTH_URL</varname> environment variable:"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_credentials.xml84(para)
+msgid ""
+"<literal>--os-username <replaceable>OS_USERNAME</replaceable></literal>. "
+"Name used for authentication with the Identity Service. Defaults to "
+"<code>env[OS_USERNAME]</code>."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_credentials.xml92(para)
+msgid ""
+"<literal>--os-password <replaceable>OS_PASSWORD</replaceable></literal>. "
+"Password used for authentication with the Identity Service. Defaults to "
+"<code>env[OS_PASSWORD]</code>."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_credentials.xml100(para)
+msgid ""
+"<literal>--os-tenant_name "
+"<replaceable>OS_TENANT_NAME</replaceable></literal>. Tenant for which to "
+"request authentication. Defaults to <code>env[OS_TENANT_NAME]</code>."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_credentials.xml108(para)
+msgid ""
+"<literal>--os-auth_url <replaceable>OS_AUTH_URL</replaceable></literal>. The"
+" Identity Service endpoint to use for authentication. Defaults to "
+"<code>env[OS_AUTH_URL]</code>."
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_compute-configure-vnc.xml63(None)
+msgid ""
+"@@image: '../common/figures/novnc/SCH_5009_V00_NUAC-VNC_OpenStack.png'; "
+"md5=182dc38019a220c851e1c94aa50f4565"
+msgstr "@@image: '../common/figures/novnc/SCH_5009_V00_NUAC-VNC_OpenStack.png'; md5=182dc38019a220c851e1c94aa50f4565"
+
+#: ./doc/common/section_compute-configure-vnc.xml6(title)
+msgid "VNC console proxy"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml7(para)
+msgid ""
+"The VNC proxy is an OpenStack component that enables compute service users "
+"to access their instances through VNC clients."
+msgstr "Le proxy VNC est un composant OpenStack qui permet aux utilisateurs du service Compute d’accéder à leurs instances via des clients VNC."
+
+#: ./doc/common/section_compute-configure-vnc.xml10(para)
+msgid "The VNC console connection works as follows:"
+msgstr "La connexion à la console VNC fonctionne comme suit :"
+
+#: ./doc/common/section_compute-configure-vnc.xml13(para)
+msgid ""
+"A user connects to the API and gets an <literal>access_url</literal> such "
+"as, <literal>http://<replaceable>ip:port</replaceable>/?token=xyz</literal>."
+msgstr "Un utilisateur se connecte à l’API et obtient une <literal>access_url</literal> telle que <literal>http://<replaceable>ip:port</replaceable>/?token=xyz</literal>."
+
+#: ./doc/common/section_compute-configure-vnc.xml19(para)
+msgid "The user pastes the URL in a browser or uses it as a client parameter."
+msgstr "L'utilisateur colle l'URL dans le navigateur ou il l'utilise comme paramètre client."
+
+#: ./doc/common/section_compute-configure-vnc.xml23(para)
+msgid "The browser or client connects to the proxy."
+msgstr "Le navigateur ou le client se connecte au proxy."
+
+#: ./doc/common/section_compute-configure-vnc.xml26(para)
+msgid ""
+"The proxy talks to <systemitem class=\"service\">nova-"
+"consoleauth</systemitem> to authorize the token for the user, and maps the "
+"token to the <emphasis>private</emphasis> host and port of the VNC server "
+"for an instance."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml31(para)
+msgid ""
+"The compute host specifies the address that the proxy should use to connect "
+"through the <filename>nova.conf</filename> file option, "
+"<option>vncserver_proxyclient_address</option>. In this way, the VNC proxy "
+"works as a bridge between the public network and private host network."
+msgstr "L’hôte Compute spécifie l’adresse que le proxy doit utiliser pour se connecter dans l’option <option>vncserver_proxyclient_address</option> du fichier <filename>nova.conf</filename>. Ainsi, le proxy VNC fonctionne comme un pont entre le réseau public et le réseau hôte privé."
+
+#: ./doc/common/section_compute-configure-vnc.xml39(para)
+msgid ""
+"The proxy initiates the connection to VNC server and continues to proxy "
+"until the session ends."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml43(para)
+msgid ""
+"The proxy also tunnels the VNC protocol over WebSockets so that the "
+"<systemitem>noVNC</systemitem> client can talk to VNC servers. In general, "
+"the VNC proxy:"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml48(para)
+msgid ""
+"Bridges between the public network where the clients live and the private "
+"network where VNC servers live."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml52(para)
+msgid "Mediates token authentication."
+msgstr "fournit les jetons d’authentification."
+
+#: ./doc/common/section_compute-configure-vnc.xml55(para)
+msgid ""
+"Transparently deals with hypervisor-specific connection details to provide a"
+" uniform client experience."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml58(title)
+msgid "noVNC process"
+msgstr "Processus noVNC"
+
+#: ./doc/common/section_compute-configure-vnc.xml71(title)
+msgid "About nova-consoleauth"
+msgstr "A propos de nova-consoleauth"
+
+#: ./doc/common/section_compute-configure-vnc.xml73(para)
+msgid ""
+"Both client proxies leverage a shared service to manage token authentication"
+" called <systemitem class=\"service\">nova-consoleauth</systemitem>. This "
+"service must be running for either proxy to work. Many proxies of either "
+"type can be run against a single <systemitem class=\"service\">nova-"
+"consoleauth</systemitem> service in a cluster configuration."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml80(para)
+msgid ""
+"Do not confuse the <systemitem class=\"service\">nova-"
+"consoleauth</systemitem> shared service with <literal>nova-"
+"console</literal>, which is a XenAPI-specific service that most recent VNC "
+"proxy architectures do not use."
+msgstr "Il ne faut pas confondre le service partagé  <systemitem class=\"service\">nova-consoleauth</systemitem> avec <literal>nova-console</literal>, qui est un service spécifique à XenAPI que la plupart des architectures proxy récentes n’utilisent pas."
+
+#: ./doc/common/section_compute-configure-vnc.xml87(title)
+msgid "Typical deployment"
+msgstr "Déploiement typique"
+
+#: ./doc/common/section_compute-configure-vnc.xml88(para)
+msgid "A typical deployment has the following components:"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml91(para)
+msgid ""
+"A <systemitem class=\"service\">nova-consoleauth</systemitem> process. "
+"Typically runs on the controller host."
+msgstr "Un processus <systemitem class=\"service\">nova-consoleauth</systemitem>. Tourne généralement sur le contrôleur hôte."
+
+#: ./doc/common/section_compute-configure-vnc.xml96(para)
+msgid ""
+"One or more <systemitem class=\"service\">nova-novncproxy</systemitem> "
+"services. Supports browser-based noVNC clients. For simple deployments, this"
+" service typically runs on the same machine as <systemitem class=\"service"
+"\">nova-api</systemitem> because it operates as a proxy between the public "
+"network and the private compute host network."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml105(para)
+msgid ""
+"One or more <literal>nova-xvpvncproxy</literal> services. Supports the "
+"special Java client discussed here. For simple deployments, this service "
+"typically runs on the same machine as <systemitem class=\"service\">nova-"
+"api</systemitem> because it acts as a proxy between the public network and "
+"the private compute host network."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml114(para)
+msgid ""
+"One or more compute hosts. These compute hosts must have correctly "
+"configured options, as follows."
+msgstr "Un ou plusieurs hôtes Compute. Ces hôtes Compute doivent avoir leurs options correctement configurées, comme suit :"
+
+#: ./doc/common/section_compute-configure-vnc.xml120(title)
+msgid "VNC configuration options"
+msgstr "Un ou plusieurs hôtes Compute. Ces hôtes Compute doivent avoir leurs options correctement configurées, comme suit :"
+
+#: ./doc/common/section_compute-configure-vnc.xml121(para)
+msgid "To customize the VNC console, use the following configuration options:"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml124(para)
+msgid ""
+"To support <link href=\"http://docs.openstack.org/trunk/config-"
+"reference/content/configuring-openstack-compute-basics.html"
+"#section_configuring-compute-migrations\">live migration</link>, you cannot "
+"specify a specific IP address for <literal>vncserver_listen</literal>, "
+"because that IP address does not exist on the destination host."
+msgstr "Pour supporter la <link href=\"http://docs.openstack.org/trunk/config-reference/content/configuring-openstack-compute-basics.html#section_configuring-compute-migrations\">live migration</link>, vous ne pouvez pas spécifier d’adresse IP en particulier pour <literal>vncserver_listen</literal>, car cette adresse IP n’existe pas sur l’hôte destinataire."
+
+#: ./doc/common/section_compute-configure-vnc.xml134(para)
+msgid ""
+"The <literal>vncserver_proxyclient_address</literal> defaults to "
+"<literal>127.0.0.1</literal>, which is the address of the compute host that "
+"Compute instructs proxies to use when connecting to instance servers."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml139(para)
+msgid "For all-in-one XenServer domU deployments, set this to 169.254.0.1."
+msgstr "Pour des déploiements domU XenServer tout-en-un, définissez-la sur 169.254.0.1."
+
+#: ./doc/common/section_compute-configure-vnc.xml140(para)
+msgid ""
+"For multi-host XenServer domU deployments, set to a dom0 management IP on "
+"the same network as the proxies."
+msgstr "Pour des déploiements domU XenServer multi-hôtes, définissez-la sur une IP de gestion dom0 sur le même réseau que les proxies."
+
+#: ./doc/common/section_compute-configure-vnc.xml142(para)
+msgid ""
+"For multi-host libvirt deployments, set to a host management IP on the same "
+"network as the proxies."
+msgstr "Pour des déploiements libvirt multi-hôtes, définissez-la sur une IP de gestion d’hôtes sur le même réseau que les proxies."
+
+#: ./doc/common/section_compute-configure-vnc.xml150(title)
+msgid "nova-novncproxy (noVNC)"
+msgstr "nova-novncproxy  (noVNC)"
+
+#: ./doc/common/section_compute-configure-vnc.xml152(para)
+msgid ""
+"You must install the <package>noVNC</package> package, which contains the "
+"<systemitem class=\"service\">nova-novncproxy</systemitem> service. As root,"
+" run the following command:"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml156(para)
+msgid "The service starts automatically on installation."
+msgstr "Le service démarre automatiquement lors de l’installation"
+
+#: ./doc/common/section_compute-configure-vnc.xml157(para)
+msgid "To restart the service, run:"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml159(para)
+msgid ""
+"The configuration option parameter should point to your "
+"<filename>nova.conf</filename> file, which includes the message queue server"
+" address and credentials."
+msgstr "Le paramètre d’option de configuration doit pointer vers votre fichier <filename>nova.conf</filename>, qui contient les informations d’identification et l’adresse du serveur de file d’attente de messagerie."
+
+#: ./doc/common/section_compute-configure-vnc.xml162(para)
+msgid ""
+"By default, <systemitem class=\"service\">nova-novncproxy</systemitem> binds"
+" on <literal>0.0.0.0:6080</literal>."
+msgstr "Par défaut, <systemitem class=\"service\">nova-novncproxy</systemitem> s’attache à <literal>0.0.0.0:6080</literal>."
+
+#: ./doc/common/section_compute-configure-vnc.xml165(para)
+msgid ""
+"To connect the service to your Compute deployment, add the following "
+"configuration options to your <filename>nova.conf</filename> file:"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml169(para)
+msgid "<literal>vncserver_listen</literal>=<replaceable>0.0.0.0</replaceable>"
+msgstr "<literal>vncserver_listen</literal>=<replaceable>0.0.0.0</replaceable>"
+
+#: ./doc/common/section_compute-configure-vnc.xml172(para)
+msgid ""
+"Specifies the address on which the VNC service should bind. Make sure it is "
+"assigned one of the compute node interfaces. This address is the one used by"
+" your domain file."
+msgstr "Spécifie l’adresse à laquelle le service VNC doit s’attacher. Assurez-vous que lui soit assignée une des interfaces de nœud Compute. Cette adresse est celle utilisée par votre fichier de domaine."
+
+#: ./doc/common/section_compute-configure-vnc.xml178(para)
+msgid ""
+"To use live migration, use the <replaceable>0.0.0.0</replaceable> address."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml183(para)
+msgid ""
+"<literal>vncserver_proxyclient_address</literal>=<replaceable>127.0.0.1</replaceable>"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml186(para)
+msgid ""
+"The address of the compute host that Compute instructs proxies to use when "
+"connecting to instance <literal>vncservers</literal>."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml193(title)
+msgid "Frequently asked questions about VNC access to virtual machines"
+msgstr "Foire Aux Questions à propos de l’accès VNC aux machines virtuelles"
+
+#: ./doc/common/section_compute-configure-vnc.xml199(literal)
+msgid "nova-xvpvncproxy"
+msgstr "nova-xvpvncproxy"
+
+#: ./doc/common/section_compute-configure-vnc.xml200(systemitem)
+msgid "nova-novncproxy"
+msgstr "nova-novncproxy"
+
+#: ./doc/common/section_compute-configure-vnc.xml198(emphasis)
+msgid ""
+"Q: What is the difference between <placeholder-1/> and <placeholder-2/>?"
+msgstr "Q: Quelle est la différence entre <placeholder-1/> et <placeholder-2/>?"
+
+#: ./doc/common/section_compute-configure-vnc.xml202(para)
+msgid ""
+"A: <literal>nova-xvpvncproxy</literal>, which ships with OpenStack Compute, "
+"is a proxy that supports a simple Java client. <systemitem class=\"service"
+"\">nova-novncproxy</systemitem> uses noVNC to provide VNC support through a "
+"web browser."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml208(emphasis)
+msgid ""
+"Q: I want VNC support in the OpenStack dashboard. What services do I need?"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml210(para)
+msgid ""
+"A: You need <systemitem class=\"service\">nova-novncproxy</systemitem>, "
+"<systemitem class=\"service\">nova-consoleauth</systemitem>, and correctly "
+"configured compute hosts."
+msgstr "R : Vous avez besoin de <systemitem class=\"service\">nova-novncproxy</systemitem>, <systemitem class=\"service\">nova-consoleauth</systemitem>, et d’hôtes Compute correctement configurés."
+
+#: ./doc/common/section_compute-configure-vnc.xml216(emphasis)
+msgid ""
+"Q: When I use <placeholder-1/> or click on the VNC tab of the OpenStack "
+"dashboard, it hangs. Why?"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml218(para)
+msgid ""
+"A: Make sure you are running <systemitem class=\"service\">nova-"
+"consoleauth</systemitem> (in addition to <systemitem class=\"service\">nova-"
+"novncproxy</systemitem>). The proxies rely on <systemitem class=\"service"
+"\">nova-consoleauth</systemitem> to validate tokens, and waits for a reply "
+"from them until a timeout is reached."
+msgstr "R : Assurez-vous d’exécuter <systemitem class=\"service\">nova-consoleauth</systemitem> (en plus de <systemitem class=\"service\">nova-novncproxy</systemitem>). Les proxies s’appuient sur <systemitem class=\"service\">nova-consoleauth</systemitem> pour valider les jetons, et attendent une réponse de leur part jusqu’à ce qu’un timeout soit atteint."
+
+#: ./doc/common/section_compute-configure-vnc.xml227(emphasis)
+msgid ""
+"Q: My VNC proxy worked fine during my all-in-one test, but now it doesn't "
+"work on multi host. Why?"
+msgstr "Q: Mon proxy VNC marchait bien lors de mon test tout-en-un, mais maintenant ça ne marche pas en multi-hôtes. Pourquoi ?"
+
+#: ./doc/common/section_compute-configure-vnc.xml230(para)
+msgid ""
+"A: The default options work for an all-in-one install, but changes must be "
+"made on your compute hosts once you start to build a cluster. As an example,"
+" suppose you have two servers:"
+msgstr "R : Les options par défaut marchent pour une installation tout-en-un, mais des changements doivent être faits sur vos hôtes Compute une fois que vous commencez à bâtir un cluster. Par exemple, supposons que vous ayez deux serveurs :"
+
+#: ./doc/common/section_compute-configure-vnc.xml236(para)
+msgid ""
+"Your <systemitem class=\"service\">nova-compute</systemitem> configuration "
+"file must set the following values:"
+msgstr "Votre fichier de configuration <systemitem class=\"service\">nova-compute</systemitem> doit être réglé avec les valeurs suivantes :"
+
+#: ./doc/common/section_compute-configure-vnc.xml248(para)
+msgid ""
+"<literal>novncproxy_base_url</literal> and "
+"<literal>xvpvncproxy_base_url</literal> use a public IP; this is the URL "
+"that is ultimately returned to clients, which generally do not have access "
+"to your private network. Your PROXYSERVER must be able to reach "
+"<literal>vncserver_proxyclient_address</literal>, because that is the "
+"address over which the VNC connection is proxied."
+msgstr "<literal>novncproxy_base_url</literal> et <literal>xvpvncproxy_base_url</literal> utilisent une IP publique ; il s’agit de l’URL qui est in fine renvoyée aux clients, qui généralement n’ont pas accès à votre réseau privé. Votre SERVEUR PROXY doit être capable d’atteindre <literal>vncserver_proxyclient_address</literal>, car c’est l’adresse par laquelle la connexion VNC passe."
+
+#: ./doc/common/section_compute-configure-vnc.xml260(emphasis)
+msgid "Q: My noVNC does not work with recent versions of web browsers. Why?"
+msgstr "Q: Mon noVNC ne marche pas avec les versions récentes des navigateurs web. Pourquoi ?"
+
+#: ./doc/common/section_compute-configure-vnc.xml263(para)
+msgid ""
+"A: Make sure you have installed <literal>python-numpy</literal>, which is "
+"required to support a newer version of the WebSocket protocol (HyBi-07+)."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml270(emphasis)
+msgid ""
+"Q: How do I adjust the dimensions of the VNC window image in the OpenStack "
+"dashboard?"
+msgstr "Q: Comment puis-je ajuster les dimensions de l’image de la fenêtre VNC dans le tableau de bord OpenStack ?"
+
+#: ./doc/common/section_compute-configure-vnc.xml273(para)
+msgid ""
+"A: These values are hard-coded in a Django HTML template. To alter them, "
+"edit the <filename>_detail_vnc.html</filename> template file. The location "
+"of this file varies based on Linux distribution. On Ubuntu 12.04, the file "
+"is at "
+"<filename>/usr/share/pyshared/horizon/dashboards/nova/instances/templates/instances/_detail_vnc.html</filename>."
+msgstr "R : Ces valeurs sont codées en dur dans le modèle HTML Django. Pour les modifier, éditez le fichier modèle  <filename>_detail_vnc.html</filename>. L’emplacement de ce fichier varie selon la distribution Linux. Sur Ubuntu 12.04, le fichier se trouve dans <filename>/usr/share/pyshared/horizon/ dashboards/nova/instances/templates/instances/_detail_vnc.html</filename>."
+
+#: ./doc/common/section_compute-configure-vnc.xml279(para)
+msgid ""
+"Modify the <option>width</option> and <option>height</option> options, as "
+"follows:"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml11(title)
+msgid "Image Service command-line client"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml12(para)
+msgid ""
+"The <placeholder-1/> client is the command-line interface (CLI) for the "
+"OpenStack Image Service API and its extensions. This chapter documents "
+"<placeholder-2/> version 0.12.0."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml22(title)
+msgid "glance usage"
+msgstr "l'utilisation de glance"
+
+#: ./doc/common/ch_cli_glance_commands.xml43(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use image-create instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml52(emphasis)
+#: ./doc/common/ch_cli_glance_commands.xml180(emphasis)
+msgid "DEPRECATED!"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml59(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use image-delete instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml67(para)
+#: ./doc/common/ch_cli_glance_commands.xml131(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use image-list instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml75(para)
+#: ./doc/common/ch_cli_glance_commands.xml524(para)
+msgid "Create a new image."
+msgstr "Créer une nouvelle image."
+
+#: ./doc/common/ch_cli_glance_commands.xml91(para)
+msgid "Download a specific image."
+msgstr "Télécharger une image spécifique."
+
+#: ./doc/common/ch_cli_glance_commands.xml99(para)
+#: ./doc/common/ch_cli_glance_commands.xml715(para)
+msgid "List images you can access."
+msgstr "Listez les images auxquelles vous pouvez accéder."
+
+#: ./doc/common/ch_cli_glance_commands.xml107(para)
+#: ./doc/common/ch_cli_glance_commands.xml163(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use member-list instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml115(para)
+#: ./doc/common/ch_cli_glance_commands.xml848(para)
+msgid "Describe a specific image."
+msgstr "Décrire une image spécifique."
+
+#: ./doc/common/ch_cli_glance_commands.xml123(para)
+#: ./doc/common/ch_cli_glance_commands.xml886(para)
+msgid "Update a specific image."
+msgstr "Mettre à jour une image spécifique."
+
+#: ./doc/common/ch_cli_glance_commands.xml139(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use member-create instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml147(para)
+#: ./doc/common/ch_cli_glance_commands.xml1057(para)
+msgid "Share a specific image with a tenant."
+msgstr "Partager une image spécifique avec un locataire."
+
+#: ./doc/common/ch_cli_glance_commands.xml155(para)
+#: ./doc/common/ch_cli_glance_commands.xml1093(para)
+msgid "Remove a shared image from a tenant."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml171(para)
+#: ./doc/common/ch_cli_glance_commands.xml1118(para)
+msgid "Describe sharing permissions by image or tenant."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml187(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use image-show instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml195(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use image-update instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml212(title)
+msgid "glance optional arguments"
+msgstr "arguments facultatifs de glance"
+
+#: ./doc/common/ch_cli_glance_commands.xml225(para)
+msgid "Defaults to <code>env[GLANCECLIENT_DEBUG]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml233(para)
+msgid "Print more verbose output"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml241(para)
+msgid ""
+"Force retrieving the schema used to generate portions of the help text "
+"rather than using a cached copy. Ignored with api version 1"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml251(para)
+msgid ""
+"Explicitly allow glanceclient to perform \"insecure SSL\" (https) requests. "
+"The server's certificate will not be verified against any certificate "
+"authorities. This option should be used with caution."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml272(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml321(para)
+msgid ""
+"Path of client key to use in SSL connection. This option is not necessary if"
+" your key is prepended to your cert file."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml282(para)
+msgid ""
+"Path of CA TLS certificate(s) used to verify the remote server's "
+"certificate. Without this option glance looks for the default system CA "
+"certificates."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml292(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml341(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use --os-cacert."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml300(para)
+msgid "Number of seconds to wait for a response"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml308(para)
+msgid "Disable SSL compression when using https."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml316(para)
+msgid "Prevent select actions from requesting user confirmation."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml325(para)
+msgid ""
+"<emphasis>DEPRECATED!</emphasis> Only used for deprecated legacy commands."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml333(para)
+#: ./doc/common/ch_cli_glance_commands.xml342(para)
+#: ./doc/common/ch_cli_glance_commands.xml351(para)
+msgid ""
+"<emphasis>DEPRECATED!</emphasis> Send a fully-formed endpoint using --os- "
+"image-url instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml360(para)
+msgid "Defaults to <code>env[OS_USERNAME]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml368(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use --os-username."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml376(para)
+msgid "Defaults to <code>env[OS_PASSWORD]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml384(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use --os-password."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml392(para)
+msgid "Defaults to <code>env[OS_TENANT_ID]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml400(para)
+msgid "Defaults to <code>env[OS_TENANT_NAME]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml408(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use --os-tenant-name."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml416(para)
+msgid "Defaults to <code>env[OS_AUTH_URL]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml424(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use --os-auth-url."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml432(para)
+msgid "Defaults to <code>env[OS_REGION_NAME]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml440(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use --os-region-name."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml456(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use --os-auth-token."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml464(para)
+msgid "Defaults to <code>env[OS_IMAGE_URL]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml472(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use --os-image-url."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml480(para)
+msgid "Defaults to <code>env[OS_IMAGE_API_VERSION]</code> or 1"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml488(para)
+msgid "Defaults to <code>env[OS_SERVICE_TYPE]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml496(para)
+msgid "Defaults to <code>env[OS_ENDPOINT_TYPE]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml504(para)
+msgid "<emphasis>DEPRECATED!</emphasis> This option is completely ignored."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml512(title)
+msgid "glance image-create command"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml531(para)
+msgid "of image to reserve."
+msgstr "d'une image à réserver."
+
+#: ./doc/common/ch_cli_glance_commands.xml539(para)
+#: ./doc/common/ch_cli_glance_commands.xml904(para)
+msgid "Name of image."
+msgstr "Nom de l'image."
+
+#: ./doc/common/ch_cli_glance_commands.xml547(para)
+msgid "Store to upload image to."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml555(para)
+#: ./doc/common/ch_cli_glance_commands.xml912(para)
+msgid ""
+"Disk format of image. Acceptable formats: ami, ari, aki, vhd, vmdk, raw, "
+"qcow2, vdi, and iso."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml564(para)
+#: ./doc/common/ch_cli_glance_commands.xml921(para)
+msgid ""
+"Container format of image. Acceptable formats: ami, ari, aki, bare, and ovf."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml573(para)
+#: ./doc/common/ch_cli_glance_commands.xml930(para)
+msgid "Tenant who should own image."
+msgstr "Le locataire que devrait posséder l'image."
+
+#: ./doc/common/ch_cli_glance_commands.xml581(para)
+msgid ""
+"Size of image data (in bytes). Only used with '-- location' and '--"
+"copy_from'."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml590(para)
+#: ./doc/common/ch_cli_glance_commands.xml946(para)
+msgid "Minimum size of disk needed to boot image (in gigabytes)."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml599(para)
+#: ./doc/common/ch_cli_glance_commands.xml955(para)
+msgid "Minimum amount of ram needed to boot image (in megabytes)."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml608(para)
+#: ./doc/common/ch_cli_glance_commands.xml964(para)
+msgid ""
+"URL where the data for this image already resides. For example, if the image"
+" data is stored in swift, you could specify "
+"'swift://account:key@example.com/container/obj'."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml619(para)
+msgid ""
+"Local file that contains disk image to be uploaded during creation. "
+"Alternatively, images can be passed to the client via stdin."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml629(para)
+msgid ""
+"Hash of image data used Glance can use for verification. Provide a md5 "
+"checksum here."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml638(para)
+#: ./doc/common/ch_cli_glance_commands.xml994(para)
+msgid ""
+"Similar to '--location' in usage, but this indicates that the Glance server "
+"should immediately copy the data and store it in its configured image store."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml648(para)
+#: ./doc/common/ch_cli_glance_commands.xml1004(para)
+msgid "Make image accessible to the public."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml656(para)
+#: ./doc/common/ch_cli_glance_commands.xml1012(para)
+msgid "Prevent image from being deleted."
+msgstr "Empêcher la suppression de l'image"
+
+#: ./doc/common/ch_cli_glance_commands.xml664(para)
+#: ./doc/common/ch_cli_glance_commands.xml1020(para)
+msgid ""
+"Arbitrary property to associate with image. May be used multiple times."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml673(para)
+#: ./doc/common/ch_cli_glance_commands.xml790(para)
+#: ./doc/common/ch_cli_glance_commands.xml866(para)
+#: ./doc/common/ch_cli_glance_commands.xml1039(para)
+msgid "Print image size in a human-friendly format."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml681(para)
+#: ./doc/common/ch_cli_glance_commands.xml1047(para)
+msgid "Show upload progress bar."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml689(title)
+msgid "glance image-delete command"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml698(para)
+msgid "Name or ID of image(s) to delete."
+msgstr "Nom ou ID des image(s) à supprimer."
+
+#: ./doc/common/ch_cli_glance_commands.xml706(title)
+msgid "glance image-list command"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml722(para)
+msgid "Filter images to those that have this name."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml730(para)
+msgid "Filter images to those that have this status."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml738(para)
+msgid ""
+"Filter images to those that have this container format. Acceptable formats: "
+"ami, ari, aki, bare, and ovf."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml748(para)
+msgid ""
+"Filter images to those that have this disk format. Acceptable formats: ami, "
+"ari, aki, vhd, vmdk, raw, qcow2, vdi, and iso."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml758(para)
+msgid "Filter images to those with a size greater than this."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml766(para)
+msgid "Filter images to those with a size less than this."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml774(para)
+msgid "Filter images by a user-defined image property."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml782(para)
+msgid "Number of images to request in each paginated request."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml798(para)
+msgid "Sort image list by specified field."
+msgstr "Trier la liste des images par champ spécifique."
+
+#: ./doc/common/ch_cli_glance_commands.xml806(para)
+msgid "Sort image list in specified direction."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml814(para)
+msgid "Allows the user to select a listing of public or non public images."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml823(para)
+msgid ""
+"Display only images owned by this tenant id. Filtering occurs on the client "
+"side so may be inefficient. This option is mainly intended for admin use. "
+"Use an empty string ('') to list images with no owner. Note: This option "
+"overrides the --is-public argument if present. Note: the v2 API supports "
+"more efficient server-side owner based filtering."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml837(para)
+msgid ""
+"Allows the admin user to list all images irrespective of the image's owner "
+"or is_public value."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml846(title)
+msgid "glance image-show command"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml855(para)
+msgid "Name or ID of image to describe."
+msgstr "Nom ou ID de l'image à décrire."
+
+#: ./doc/common/ch_cli_glance_commands.xml874(title)
+msgid "glance image-update command"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml893(para)
+msgid "Name or ID of image to modify."
+msgstr "Nom ou ID de l'image à modifier."
+
+#: ./doc/common/ch_cli_glance_commands.xml938(para)
+msgid "Size of image data (in bytes)."
+msgstr "Taille de l'image (en octets)."
+
+#: ./doc/common/ch_cli_glance_commands.xml975(para)
+msgid ""
+"Local file that contains disk image to be uploaded during update. "
+"Alternatively, images can be passed to the client via stdin."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml985(para)
+msgid "Hash of image data used Glance can use for verification."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml1029(para)
+msgid ""
+"If this flag is present, delete all image properties not explicitly set in "
+"the update request. Otherwise, those properties not referenced are "
+"preserved."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml1055(title)
+msgid "glance member-create command"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml1064(para)
+msgid "Image to add member to."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml1072(para)
+msgid "Tenant to add as member"
+msgstr "Le locataire à ajouter comme membre"
+
+#: ./doc/common/ch_cli_glance_commands.xml1083(para)
+msgid "Allow the specified tenant to share this image."
+msgstr "Permetter le locataire specifié de partager cette image."
+
+#: ./doc/common/ch_cli_glance_commands.xml1091(title)
+msgid "glance member-delete command"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml1100(para)
+msgid "Image from which to remove member"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml1108(para)
+msgid "Tenant to remove as member"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml1116(title)
+msgid "glance member-list command"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml1125(para)
+msgid "Filter results by an image ID."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml1133(para)
+msgid "Filter results by a tenant ID."
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml106(None)
+msgid ""
+"@@image: 'figures/launch_instances.png'; "
+"md5=8a7e6864bce97f6478db572daf3ef5de"
+msgstr "@@image: 'figures/launch_instances.png'; md5=8a7e6864bce97f6478db572daf3ef5de"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml164(None)
+msgid "@@image: 'figures/instances.png'; md5=6b0f5cb3009d447334ff8b5c5b2cd121"
+msgstr "@@image: 'figures/instances.png'; md5=6b0f5cb3009d447334ff8b5c5b2cd121"
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml10(para)
+msgid ""
+"You can launch an instance directly from one of the available OpenStack "
+"images. The OpenStack Image Service provides a pool of images that are "
+"accessible to members of different projects. When you launch an instance "
+"from an image, OpenStack creates a local copy of the image on the respective"
+" compute node where the instance is started."
+msgstr "Vous pouvez lancer une instance directement depuis l'une des images OpenStack qui sont disponibles. Le service d'Images OpenStack met à disposition un pool d'images qui sont accessible aux membres des différents projets. Quand vous lancez une instance depuis une image, OpenStack crée une copie locale de l'image sur le nœud de calcul respectif où l'instance est démarrée.  "
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml16(para)
+msgid ""
+"Alternatively, you can launch an instance from an image that you have copied"
+" to a persistent volume."
+msgstr "Autrement, vous pouvez lancer une instance à partird'une image qui a été copiée sur un volume persistent."
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml18(para)
+msgid "To launch an instance, specify the following parameters:"
+msgstr "Pour lancer une instance, spécifiez les paramètres suivants:"
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml22(para)
+msgid ""
+"The <guilabel>instance source</guilabel>, which is an image or snapshot. "
+"Alternatively, you can boot from a volume, which is block storage, to which "
+"you've copied an image or snapshot."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml28(para)
+msgid ""
+"The <guilabel>image</guilabel> or <guilabel>snapshot</guilabel>, which "
+"represents the operating system."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml33(para)
+msgid "A <guilabel>name</guilabel> for your instance."
+msgstr "Un <guilabel>name</guilabel> pour votre instance."
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml49(para)
+msgid ""
+"A <emphasis role=\"bold\">keypair</emphasis> for your instance, which are "
+"SSH credentials that are injected into images when they are launched. For "
+"this to work, the image must contain the <literal>cloud-init</literal> "
+"package. Create at least one keypair for each project. If you already have "
+"generated a keypair with an external tool, you can import it into OpenStack."
+" You can use the keypair for multiple instances that belong to that project."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml62(para)
+msgid ""
+"A <emphasis role=\"bold\">security group</emphasis>, which defines which "
+"incoming network traffic is forwarded to instances. Security groups hold a "
+"set of firewall policies, known as <emphasis role=\"italic\">security group "
+"rules</emphasis>."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml73(para)
+msgid ""
+"If needed, you can assign a <emphasis role=\"bold\">floating (public) IP "
+"address</emphasis> to a running instance and attach a block storage device, "
+"or volume, for persistent storage."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml80(title)
+msgid "To launch an instance:"
+msgstr "Pour lancer une instance"
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml82(para)
+msgid "Log in to the OpenStack dashboard."
+msgstr "Connectez-vous au tableau de bord OpenStack"
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml85(para)
+msgid ""
+"If you are a member of multiple projects, select a project from the drop-"
+"down list at the top of the <guilabel>Project</guilabel> tab."
+msgstr "Si vous êtes membre de multiple projets, selectionnez un projet de la liste déroulante en tête de l'onglet <guilabel>Project</guilabel>."
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml90(para)
+msgid "Click the <guilabel>Images &amp; Snapshot</guilabel> category."
+msgstr "Cliquez sur la catégorie <guilabel>Images &amp; Snapshot</guilabel>."
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml92(para)
+msgid ""
+"The dashboard shows the images that have been uploaded to OpenStack Image "
+"Service and are available for this project."
+msgstr "Le tableau de bord affiche les images qui ont été téléchargé  sur le Service d'Image OpenStack et qui sont disponibles pour ce projet."
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml100(title)
+msgid "OpenStack dashboard - Launch Instances window"
+msgstr "Tableau de bord OpenStack - Fenêtre du lancement des instances"
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml97(para)
+msgid ""
+"Select an image and click <guibutton>Launch</guibutton>. The "
+"<guilabel>Launch Image</guilabel> window appears: <placeholder-1/>"
+msgstr "Sélectionnez une image et cliquez sur <guibutton>Launch</guibutton>. La fenêtre  <guilabel>Launch Image</guilabel> s'affiche: <placeholder-1/>"
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml112(para)
+msgid "Specify the following parameters:"
+msgstr "Spécifiez les paramètres suivants:"
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml116(para)
+msgid "Enter an instance name to assign to the virtual machine."
+msgstr "Entrer le nom d'une instance pour l'assigner à la machine virtuel."
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml120(para)
+msgid ""
+"From the <guilabel>Flavor</guilabel> drop-down list, select the size of the "
+"virtual machine to launch."
+msgstr "A partir de la liste déroulante <guilabel>Flavor</guilabel>, sélectionnez la taille de la machine virtuelle à lancer."
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml125(para)
+msgid "Optionally, select a keypair."
+msgstr "Facultativement, choisissez une paire de clés."
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml126(para)
+msgid ""
+"In case an image uses a static root password or a static key set (neither is"
+" recommended), you do not need to provide a keypair on starting the "
+"instance."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml132(para)
+msgid ""
+"In <guilabel>Instance Count</guilabel>, enter the number of virtual machines"
+" to launch from this image."
+msgstr "Dans <guilabel>Instance Count</guilabel>, entrez le nombre de machines virtuelles à lancer depuis cette instance."
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml137(para)
+msgid ""
+"Assign the instance to the default security group. If you added rules to "
+"this group, the instance implements these rules."
+msgstr "Assignez l'instance au groupe de sécurité par défaut. Si vous ajoutez des règles à ce groupe, l'instance met en oeuvre ces règles."
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml150(para)
+msgid ""
+"Click <guibutton>Launch Instance</guibutton>. The instance is launched on "
+"any of the compute nodes in the cloud."
+msgstr "Cliquez sur <guibutton>Launch Instance</guibutton>. L'instance est lancé sur n'importe quel nœud de calcul dans le cloud. "
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml155(para)
+msgid ""
+"After you have launched an instance, switch to the <guilabel>Instances &amp;"
+" Volumes</guilabel> category to view the instance name, its (private or "
+"public) IP address, size, status, task, and power state."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml160(title)
+msgid "OpenStack dashboard - Instances"
+msgstr "Tableau de bord OpenStack - Instances"
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml168(para)
+msgid ""
+"If you did not provide a keypair on starting and have not touched security "
+"groups or rules so far, by default the instance can only be accessed from "
+"inside the cloud through VNC at this point. Even pinging the instance is not"
+" possible."
+msgstr "Si vous ne fournissez pas de paire de clés, de groupes de sécurités, ou de règles jusqu'ici, les utilisateurs ne peuvent accéder à l'instance qu'à partir du cloud par VNC. Même pinger l'instance n'est pas possible."
+
+#: ./doc/common/section_keystone_config_ldap.xml6(title)
+msgid "Integrate Identity with LDAP"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml7(para)
+msgid ""
+"Identity Service supports integration with an existing LDAP directory for "
+"authentication and authorization services."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml11(para)
+msgid ""
+"For OpenStack Identity to access an LDAP back end, you must enable the "
+"<option>authlogin_nsswitch_use_ldap</option> boolean value for SELinux on "
+"the Identity server. To enable and make the option persistent across "
+"reboots:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml18(para)
+msgid "You can integrate Identity with a single LDAP server."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml21(para)
+msgid ""
+"To configure Identity, set options in the "
+"<filename>/etc/keystone/keystone.conf</filename> file. Modify these examples"
+" as needed."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml25(title)
+msgid "To integrate Identity with LDAP"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml27(para)
+msgid "Enable the LDAP driver in the <filename>keystone.conf</filename> file:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml34(para)
+msgid ""
+"Define the destination LDAP server in the <filename>keystone.conf</filename>"
+" file:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml45(para)
+msgid ""
+"Create the organizational units (OU) in the LDAP directory, and define their"
+" corresponding location in the <filename>keystone.conf</filename> file:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml58(para)
+msgid ""
+"These schema attributes are extensible for compatibility with various "
+"schemas. For example, this entry maps to the <systemitem>person</systemitem>"
+" attribute in Active Directory:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml67(para)
+msgid ""
+"A read-only implementation is recommended for LDAP integration. These "
+"permissions are applied to object types in the "
+"<filename>keystone.conf</filename> file:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml85(para)
+msgid "Restart the Identity service:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml87(para)
+msgid ""
+"During service restart, authentication and authorization are unavailable."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml92(title)
+msgid "Additional LDAP integration settings"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml93(para)
+msgid "Set these options in the <filename>keystone.conf</filename> file."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml98(term)
+msgid "Filters"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml100(para)
+msgid "Use filters to control the scope of data presented through LDAP."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml109(term)
+msgid "LDAP Account Status"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml111(para)
+msgid ""
+"Mask account status values for compatibility with various directory "
+"services. Superfluous accounts are filtered with "
+"<systemitem>user_filter</systemitem>."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml115(para)
+msgid ""
+"For example, you can mask Active Directory account status attributes in the "
+"<filename>keystone.conf</filename> file:"
+msgstr ""
+
+#: ./doc/common/app_support.xml7(title)
+msgid "Community support"
+msgstr "Soutien Communautaire"
+
+#: ./doc/common/app_support.xml8(para)
+msgid ""
+"The following resources are available to help you run and use OpenStack. The"
+" OpenStack community constantly improves and adds to the main features of "
+"OpenStack, but if you have any questions, do not hesitate to ask. Use the "
+"following resources to get OpenStack support, and troubleshoot your "
+"installations."
+msgstr ""
+
+#: ./doc/common/app_support.xml15(title)
+msgid "Documentation"
+msgstr "Documentation"
+
+#: ./doc/common/app_support.xml16(para)
+msgid ""
+"For the available OpenStack documentation, see <link "
+"href=\"http://docs.openstack.org\">docs.openstack.org</link>."
+msgstr ""
+
+#: ./doc/common/app_support.xml19(para) ./doc/common/app_support.xml393(para)
+#: ./doc/common/ch_getstart.xml208(para)
+msgid ""
+"To provide feedback on documentation, join and use the <email>openstack-"
+"docs@lists.openstack.org</email> mailing list at <link "
+"href=\"http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-"
+"docs\">OpenStack Documentation Mailing List</link>, or <link "
+"href=\"https://bugs.launchpad.net/openstack-manuals/+filebug\">report a "
+"bug</link>."
+msgstr ""
+
+#: ./doc/common/app_support.xml26(para)
+msgid ""
+"The following books explain how to install an OpenStack cloud and its "
+"associated components:"
+msgstr ""
+
+#: ./doc/common/app_support.xml33(citetitle)
+msgid "Installation Guide for Debian 7.0"
+msgstr "Installation sur Debian 7.0 "
+
+#: ./doc/common/app_support.xml41(citetitle)
+msgid "Installation Guide for openSUSE and SUSE Linux Enterprise Server"
+msgstr "Installation sur openSUSE ou SUSE Linux Enterprise Server"
+
+#: ./doc/common/app_support.xml49(citetitle)
+msgid "Installation Guide for Red Hat Enterprise Linux, CentOS, and Fedora"
+msgstr "Installation sur Red Hat Enterprise Linux, CentOS et Fedora"
+
+#: ./doc/common/app_support.xml58(citetitle)
+msgid "Installation Guide for Ubuntu 12.04/14.04 (LTS)"
+msgstr ""
+
+#: ./doc/common/app_support.xml63(para)
+msgid ""
+"The following books explain how to configure and run an OpenStack cloud:"
+msgstr ""
+
+#: ./doc/common/app_support.xml70(citetitle)
+msgid "Cloud Administrator Guide"
+msgstr ""
+
+#: ./doc/common/app_support.xml76(citetitle)
+msgid "Configuration Reference"
+msgstr "Référence de Configuration"
+
+#: ./doc/common/app_support.xml82(citetitle)
+msgid "Operations Guide"
+msgstr "Guide d'Opérations"
+
+#: ./doc/common/app_support.xml88(citetitle)
+msgid "High Availability Guide"
+msgstr ""
+
+#: ./doc/common/app_support.xml94(citetitle)
+msgid "Security Guide"
+msgstr "Guide de sécurité"
+
+#: ./doc/common/app_support.xml100(citetitle)
+msgid "Virtual Machine Image Guide"
+msgstr ""
+
+#: ./doc/common/app_support.xml104(para)
+msgid ""
+"The following books explain how to use the OpenStack dashboard and command-"
+"line clients:"
+msgstr ""
+
+#: ./doc/common/app_support.xml111(citetitle)
+msgid "API Quick Start"
+msgstr ""
+
+#: ./doc/common/app_support.xml118(citetitle)
+msgid "End User Guide"
+msgstr "fin du guide utilisateur"
+
+#: ./doc/common/app_support.xml125(citetitle)
+msgid "Admin User Guide"
+msgstr ""
+
+#: ./doc/common/app_support.xml132(citetitle)
+msgid "Command-Line Interface Reference"
+msgstr ""
+
+#: ./doc/common/app_support.xml136(para)
+msgid ""
+"The following documentation provides reference and guidance information for "
+"the OpenStack APIs:"
+msgstr ""
+
+#: ./doc/common/app_support.xml142(link)
+msgid "OpenStack API Complete Reference (HTML)"
+msgstr ""
+
+#: ./doc/common/app_support.xml148(link)
+msgid "API Complete Reference (PDF)"
+msgstr ""
+
+#: ./doc/common/app_support.xml153(citetitle)
+msgid "OpenStack Block Storage Service API v2 Reference"
+msgstr "Reference de l'API du service OpenStack Block Storage v2"
+
+#: ./doc/common/app_support.xml160(citetitle)
+msgid "OpenStack Compute API v2 and Extensions Reference"
+msgstr ""
+
+#: ./doc/common/app_support.xml167(citetitle)
+msgid "OpenStack Identity Service API v2.0 Reference"
+msgstr ""
+
+#: ./doc/common/app_support.xml173(citetitle)
+msgid "OpenStack Image Service API v2 Reference"
+msgstr ""
+
+#: ./doc/common/app_support.xml179(citetitle)
+msgid "OpenStack Networking API v2.0 Reference"
+msgstr ""
+
+#: ./doc/common/app_support.xml185(citetitle)
+msgid "OpenStack Object Storage API v1 Reference"
+msgstr ""
+
+#: ./doc/common/app_support.xml189(para)
+msgid ""
+"The <link href=\"http://docs.openstack.org/training-"
+"guides/content/\"><citetitle>Training Guides</citetitle></link> offer "
+"software training for cloud administration and management."
+msgstr ""
+
+#: ./doc/common/app_support.xml196(title)
+msgid "ask.openstack.org"
+msgstr "ask.openstack.org"
+
+#: ./doc/common/app_support.xml197(para)
+msgid ""
+"During the set up or testing of OpenStack, you might have questions about "
+"how a specific task is completed or be in a situation where a feature does "
+"not work correctly. Use the <link "
+"href=\"http://ask.openstack.org\">ask.openstack.org</link> site to ask "
+"questions and get answers. When you visit the <link "
+"href=\"http://ask.openstack.org\">http://ask.openstack.org</link> site, scan"
+" the recently asked questions to see whether your question has already been "
+"answered. If not, ask a new question. Be sure to give a clear, concise "
+"summary in the title and provide as much detail as possible in the "
+"description. Paste in your command output or stack traces, links to screen "
+"shots, and any other information which might be useful."
+msgstr ""
+
+#: ./doc/common/app_support.xml214(title)
+msgid "OpenStack mailing lists"
+msgstr "listes de diffusion OpenStack"
+
+#: ./doc/common/app_support.xml215(para)
+msgid ""
+"A great way to get answers and insights is to post your question or "
+"problematic scenario to the OpenStack mailing list. You can learn from and "
+"help others who might have similar issues. To subscribe or view the "
+"archives, go to <link href=\"http://lists.openstack.org/cgi-"
+"bin/mailman/listinfo/openstack\">http://lists.openstack.org/cgi-"
+"bin/mailman/listinfo/openstack</link>. You might be interested in the other "
+"mailing lists for specific projects or development, which you can find <link"
+" href=\"http://wiki.openstack.org/MailingLists\">on the wiki</link>. A "
+"description of all mailing lists is available at <link "
+"href=\"http://wiki.openstack.org/MailingLists\">http://wiki.openstack.org/MailingLists</link>."
+msgstr ""
+
+#: ./doc/common/app_support.xml231(title)
+msgid "The OpenStack wiki"
+msgstr "Le wiki OpenStack "
+
+#: ./doc/common/app_support.xml232(para)
+msgid ""
+"The <link href=\"http://wiki.openstack.org/\">OpenStack wiki</link> contains"
+" a broad range of topics but some of the information can be difficult to "
+"find or is a few pages deep. Fortunately, the wiki search feature enables "
+"you to search by title or content. If you search for specific information, "
+"such as about networking or nova, you can find a large amount of relevant "
+"material. More is being added all the time, so be sure to check back often. "
+"You can find the search box in the upper-right corner of any OpenStack wiki "
+"page."
+msgstr ""
+
+#: ./doc/common/app_support.xml243(title)
+msgid "The Launchpad Bugs area"
+msgstr "La zone Launchpad Bugs"
+
+#: ./doc/common/app_support.xml244(para)
+msgid ""
+"The OpenStack community values your set up and testing efforts and wants "
+"your feedback. To log a bug, you must sign up for a Launchpad account at "
+"<link "
+"href=\"https://launchpad.net/+login\">https://launchpad.net/+login</link>. "
+"You can view existing bugs and report bugs in the Launchpad Bugs area. Use "
+"the search feature to determine whether the bug has already been reported or"
+" already been fixed. If it still seems like your bug is unreported, fill out"
+" a bug report."
+msgstr ""
+
+#: ./doc/common/app_support.xml252(para)
+msgid "Some tips:"
+msgstr "Quelques conseils :"
+
+#: ./doc/common/app_support.xml255(para)
+msgid "Give a clear, concise summary."
+msgstr ""
+
+#: ./doc/common/app_support.xml258(para)
+msgid ""
+"Provide as much detail as possible in the description. Paste in your command"
+" output or stack traces, links to screen shots, and any other information "
+"which might be useful."
+msgstr ""
+
+#: ./doc/common/app_support.xml264(para)
+msgid ""
+"Be sure to include the software and package versions that you are using, "
+"especially if you are using a development branch, such as, <literal>\"Juno "
+"release\" vs git commit bc79c3ecc55929bac585d04a03475b72e06a3208</literal>."
+msgstr ""
+
+#: ./doc/common/app_support.xml271(para)
+msgid ""
+"Any deployment-specific information is helpful, such as whether you are "
+"using Ubuntu 14.04 or are performing a multi-node installation."
+msgstr ""
+
+#: ./doc/common/app_support.xml276(para)
+msgid "The following Launchpad Bugs areas are available:"
+msgstr ""
+
+#: ./doc/common/app_support.xml282(link)
+msgid "Bugs: OpenStack Block Storage (cinder)"
+msgstr ""
+
+#: ./doc/common/app_support.xml288(link)
+msgid "Bugs: OpenStack Compute (nova)"
+msgstr "Bugs: OpenStack Calcul (nova)"
+
+#: ./doc/common/app_support.xml293(link)
+msgid "Bugs: OpenStack Dashboard (horizon)"
+msgstr "Bugs: OpenStack Tableau de Bord (horizon)"
+
+#: ./doc/common/app_support.xml299(link)
+msgid "Bugs: OpenStack Identity (keystone)"
+msgstr "Bugs: OpenStack Identité (keystone)"
+
+#: ./doc/common/app_support.xml305(link)
+msgid "Bugs: OpenStack Image Service (glance)"
+msgstr "Bugs: OpenStack Service d'Image (glance)"
+
+#: ./doc/common/app_support.xml311(link)
+msgid "Bugs: OpenStack Networking (neutron)"
+msgstr "Bugs: OpenStack Réseau (neutron)"
+
+#: ./doc/common/app_support.xml317(link)
+msgid "Bugs: OpenStack Object Storage (swift)"
+msgstr "Bugs: OpenStack Stockage d'Objets (swift)"
+
+#: ./doc/common/app_support.xml324(link)
+msgid "Bugs: Bare Metal (ironic)"
+msgstr ""
+
+#: ./doc/common/app_support.xml329(link)
+msgid "Bugs: Data Processing Service (sahara)"
+msgstr ""
+
+#: ./doc/common/app_support.xml335(link)
+msgid "Bugs: Database Service (trove)"
+msgstr "Bugs: La Service Base de Données (trove)"
+
+#: ./doc/common/app_support.xml340(link)
+msgid "Bugs: Orchestration (heat)"
+msgstr "Bugs: l'Orchestration (heat)"
+
+#: ./doc/common/app_support.xml345(link)
+msgid "Bugs: Telemetry (ceilometer)"
+msgstr "Bugs: Métrologie (ceilometer)"
+
+#: ./doc/common/app_support.xml350(link)
+msgid "Bugs: Queue Service (marconi)"
+msgstr ""
+
+#: ./doc/common/app_support.xml356(link)
+msgid "Bugs: OpenStack API Documentation (developer.openstack.org)"
+msgstr ""
+
+#: ./doc/common/app_support.xml362(link)
+msgid "Bugs: OpenStack Documentation (docs.openstack.org)"
+msgstr ""
+
+#: ./doc/common/app_support.xml368(title)
+msgid "The OpenStack IRC channel"
+msgstr "Le canal OpenStack IRC"
+
+#: ./doc/common/app_support.xml369(para)
+msgid ""
+"The OpenStack community lives in the #openstack IRC channel on the Freenode "
+"network. You can hang out, ask questions, or get immediate feedback for "
+"urgent and pressing issues. To install an IRC client or use a browser-based "
+"client, go to <link "
+"href=\"http://webchat.freenode.net\">http://webchat.freenode.net/</link>. "
+"You can also use Colloquy (Mac OS X, <link "
+"href=\"http://colloquy.info/\">http://colloquy.info/</link>), mIRC (Windows,"
+" <link href=\"http://www.mirc.com/\">http://www.mirc.com/</link>), or XChat "
+"(Linux). When you are in the IRC channel and want to share code or command "
+"output, the generally accepted method is to use a Paste Bin. The OpenStack "
+"project has one at <link "
+"href=\"http://paste.openstack.org\">http://paste.openstack.org</link>. Just "
+"paste your longer amounts of text or logs in the web form and you get a URL "
+"that you can paste into the channel. The OpenStack IRC channel is "
+"<literal>#openstack</literal> on <literal>irc.freenode.net</literal>. You "
+"can find a list of all OpenStack IRC channels at <link "
+"href=\"https://wiki.openstack.org/wiki/IRC\">https://wiki.openstack.org/wiki/IRC</link>."
+msgstr ""
+
+#: ./doc/common/app_support.xml392(title)
+msgid "Documentation feedback"
+msgstr "commentaires sur la documentation"
+
+#: ./doc/common/app_support.xml399(title)
+msgid "OpenStack distribution packages"
+msgstr ""
+
+#: ./doc/common/app_support.xml400(para)
+msgid ""
+"The following Linux distributions provide community-supported packages for "
+"OpenStack:"
+msgstr ""
+
+#: ./doc/common/app_support.xml404(emphasis)
+msgid "Debian:"
+msgstr ""
+
+#: ./doc/common/app_support.xml407(link)
+msgid "http://wiki.debian.org/OpenStack"
+msgstr "http://wiki.debian.org/OpenStack"
+
+#: ./doc/common/app_support.xml410(emphasis)
+msgid "CentOS, Fedora, and Red Hat Enterprise Linux:"
+msgstr "CentOS, Fedora, et Red Hat Enterprise Linux:"
+
+#: ./doc/common/app_support.xml413(link)
+msgid "http://openstack.redhat.com/"
+msgstr "http://openstack.redhat.com/"
+
+#: ./doc/common/app_support.xml416(emphasis)
+msgid "openSUSE and SUSE Linux Enterprise Server:"
+msgstr ""
+
+#: ./doc/common/app_support.xml420(link)
+msgid "http://en.opensuse.org/Portal:OpenStack"
+msgstr "http://en.opensuse.org/Portal:OpenStack"
+
+#: ./doc/common/app_support.xml423(emphasis)
+msgid "Ubuntu:"
+msgstr "Ubuntu:"
+
+#: ./doc/common/app_support.xml426(link)
+msgid "https://wiki.ubuntu.com/ServerTeam/CloudArchive"
+msgstr "https://wiki.ubuntu.com/ServerTeam/CloudArchive"
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml6(title)
+msgid "Troubleshoot Object Storage"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml7(para)
+msgid ""
+"For Object Storage, everything is logged in "
+"<filename>/var/log/syslog</filename> (or messages on some distros). Several "
+"settings enable further customization of logging, such as "
+"<literal>log_name</literal>, <literal>log_facility</literal>, and "
+"<literal>log_level</literal>, within the object server configuration files."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml11(title)
+msgid "Drive failure"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml12(para)
+msgid ""
+"In the event that a drive has failed, the first step is to make sure the "
+"drive is unmounted. This will make it easier for Object Storage to work "
+"around the failure until it has been resolved. If the drive is going to be "
+"replaced immediately, then it is just best to replace the drive, format it, "
+"remount it, and let replication fill it up."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml16(para)
+msgid ""
+"If the drive can’t be replaced immediately, then it is best to leave it "
+"unmounted, and remove the drive from the ring. This will allow all the "
+"replicas that were on that drive to be replicated elsewhere until the drive "
+"is replaced. Once the drive is replaced, it can be re-added to the ring."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml20(para)
+msgid ""
+"You can look at error messages in <filename>/var/log/kern.log</filename> for"
+" hints of drive failure."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml23(title)
+msgid "Server failure"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml24(para)
+msgid ""
+"If a server is having hardware issues, it is a good idea to make sure the "
+"Object Storage services are not running. This will allow Object Storage to "
+"work around the failure while you troubleshoot."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml27(para)
+msgid ""
+"If the server just needs a reboot, or a small amount of work that should "
+"only last a couple of hours, then it is probably best to let Object Storage "
+"work around the failure and get the machine fixed and back online. When the "
+"machine comes back online, replication will make sure that anything that is "
+"missing during the downtime will get updated."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml32(para)
+msgid ""
+"If the server has more serious issues, then it is probably best to remove "
+"all of the server’s devices from the ring. Once the server has been repaired"
+" and is back online, the server’s devices can be added back into the ring. "
+"It is important that the devices are reformatted before putting them back "
+"into the ring as it is likely to be responsible for a different set of "
+"partitions than before."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml40(title)
+msgid "Detect failed drives"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml41(para)
+msgid ""
+"It has been our experience that when a drive is about to fail, error "
+"messages will spew into /var/log/kern.log. There is a script called swift-"
+"drive-audit that can be run via cron to watch for bad drives. If errors are "
+"detected, it will unmount the bad drive, so that Object Storage can work "
+"around it. The script takes a configuration file with the following "
+"settings:"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml47(para)
+msgid ""
+"This script has only been tested on Ubuntu 10.04, so if you are using a "
+"different distro or OS, some care should be taken before using in "
+"production."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml52(title)
+msgid "Emergency recovery of ring builder files"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml53(para)
+msgid ""
+"You should always keep a backup of swift ring builder files. However, if an "
+"emergency occurs, this procedure may assist in returning your cluster to an "
+"operational state."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml56(para)
+msgid ""
+"Using existing swift tools, there is no way to recover a builder file from a"
+" <filename>ring.gz</filename> file. However, if you have a knowledge of "
+"Python, it is possible to construct a builder file that is pretty close to "
+"the one you have lost. The following is what you will need to do."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml61(para)
+msgid ""
+"This procedure is a last-resort for emergency circumstances. It requires "
+"knowledge of the swift python code and may not succeed."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml64(para)
+msgid "First, load the ring and a new ringbuilder object in a Python REPL:"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml67(para)
+msgid "Now, start copying the data we have in the ring into the builder."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml84(para)
+msgid ""
+"This is the extent of the recoverable fields. For "
+"<literal>min_part_hours</literal> you'll either have to remember what the "
+"value you used was, or just make up a new one."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml89(para)
+msgid ""
+"Try some validation: if this doesn't raise an exception, you may feel some "
+"hope. Not too much, though."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml92(para)
+msgid "Save the builder."
+msgstr "Enregistrer le générateur."
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml96(para)
+msgid ""
+"You should now have a file called 'account.builder' in the current working "
+"directory. Next, run <literal>swift-ring-builder account.builder "
+"write_ring</literal> and compare the new account.ring.gz to the "
+"account.ring.gz that you started from. They probably won't be byte-for-byte "
+"identical, but if you load them up in a REPL and their "
+"<literal>_replica2part2dev_id</literal> and <literal>devs</literal> "
+"attributes are the same (or nearly so), then you're in good shape."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml103(para)
+msgid ""
+"Next, repeat the procedure for <filename>container.ring.gz</filename> and "
+"<filename>object.ring.gz</filename>, and you might get usable builder files."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-account-reaper.xml7(title)
+msgid "Account reaper"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-account-reaper.xml8(para)
+msgid ""
+"In the background, the account reaper removes data from the deleted "
+"accounts."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-account-reaper.xml9(para)
+msgid ""
+"A reseller marks an account for deletion by issuing a <code>DELETE</code> "
+"request on the account’s storage URL. This action sets the "
+"<code>status</code> column of the account_stat table in the account database"
+" and replicas to <code>DELETED</code>, marking the account's data for "
+"deletion."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-account-reaper.xml17(para)
+msgid ""
+"It's on the developers' to-do list to write a utility that performs this "
+"task, preferably through a ReST call."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-account-reaper.xml12(para)
+msgid ""
+"Typically, a specific retention time or undelete are not provided. However, "
+"you can set a <code>delay_reaping</code> value in the <code>[account-"
+"reaper]</code> section of the account-server.conf to delay the actual "
+"deletion of data. At this time, to undelete you have to update the account "
+"database replicas directly, setting the status column to an empty string and"
+" updating the put_timestamp to be greater than the delete_timestamp. "
+"<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-account-reaper.xml20(para)
+msgid ""
+"The account reaper runs on each account server and scans the server "
+"occasionally for account databases marked for deletion. It only fires up on "
+"the accounts for which the server is the primary node, so that multiple "
+"account servers aren’t trying to do it simultaneously. Using multiple "
+"servers to delete one account might improve the deletion speed but requires "
+"coordination to avoid duplication. Speed really is not a big concern with "
+"data deletion, and large accounts aren’t deleted often."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-account-reaper.xml26(para)
+msgid ""
+"Deleting an account is simple. For each account container, all objects are "
+"deleted and then the container is deleted. Deletion requests that fail will "
+"not stop the overall process but will cause the overall process to fail "
+"eventually (for example, if an object delete times out, you will not be able"
+" to delete the container or the account). The account reaper keeps trying to"
+" delete an account until it is empty, at which point the database reclaim "
+"process within the db_replicator will remove the database files."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-account-reaper.xml32(para)
+msgid ""
+"A persistent error state may prevent the deletion of an object or container."
+" If this happens, you will see a message such as <code>“Account &lt;name&gt;"
+" has not been reaped since &lt;date&gt;”</code> in the log. You can control "
+"when this is logged with the <code>reap_warn_after</code> value in the <code"
+">[account-reaper]</code> section of the account-server.conf file. The "
+"default value is 30 days."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml7(title)
+#: ./doc/common/section_dashboard_access.xml304(guilabel)
+msgid "Flavors"
+msgstr "Types d'instance"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml8(para)
+msgid ""
+"Admin users can use the <placeholder-1/> commands to customize and manage "
+"flavors. To see the available flavor-related commands, run:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml22(para)
+msgid ""
+"Configuration rights can be delegated to additional users by redefining the "
+"access controls for <option>compute_extension:flavormanage</option> in "
+"<filename>/etc/nova/policy.json</filename> on the <systemitem class=\"server"
+"\">nova-api</systemitem> server."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml26(para)
+msgid ""
+"To modify an existing flavor in the dashboard, you must delete the flavor "
+"and create a modified one with the same name."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml31(para)
+msgid "Flavors define these elements:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml33(caption)
+msgid "Identity Service configuration file sections"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml39(td)
+msgid "Element"
+msgstr "élément"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml45(literal)
+msgid "Name"
+msgstr "Nom"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml47(replaceable)
+msgid "XX"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml47(replaceable)
+msgid "SIZE_NAME"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml46(td)
+msgid ""
+"A descriptive name. <placeholder-1/>.<placeholder-2/> is typically not "
+"required, though some third party tools may rely on it."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml52(literal)
+msgid "Memory_MB"
+msgstr "Memory_MB"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml53(td)
+msgid "Virtual machine memory in megabytes."
+msgstr "Mémoire de la machine virtuel en mégaoctets."
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml56(literal)
+msgid "Disk"
+msgstr "Disque"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml57(td)
+msgid ""
+"Virtual root disk size in gigabytes. This is an ephemeral disk that the base"
+" image is copied into. When booting from a persistent volume it is not used."
+" The \"0\" size is a special case which uses the native base image size as "
+"the size of the ephemeral root volume."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml65(literal)
+msgid "Ephemeral"
+msgstr "Éphémère"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml66(td)
+msgid ""
+"Specifies the size of a secondary ephemeral data disk. This is an empty, "
+"unformatted disk and exists only for the life of the instance."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml71(literal)
+msgid "Swap"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml72(td)
+msgid "Optional swap space allocation for the instance."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml76(literal)
+msgid "VCPUs"
+msgstr "VCPUs"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml77(td)
+msgid "Number of virtual CPUs presented to the instance."
+msgstr "Nombre de UC virtuelles présentées à l'instance. "
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml81(literal)
+msgid "RXTX_Factor"
+msgstr "RXTX_Factor"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml82(td)
+msgid ""
+"Optional property allows created servers to have a different bandwidth cap "
+"than that defined in the network they are attached to. This factor is "
+"multiplied by the rxtx_base property of the network. Default value is 1.0. "
+"That is, the same as attached network."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml90(literal)
+msgid "Is_Public"
+msgstr "Is_Public"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml91(td)
+msgid ""
+"Boolean value, whether flavor is available to all users or private to the "
+"tenant it was created in. Defaults to True."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml96(literal)
+msgid "extra_specs"
+msgstr "extra_specs"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml97(para)
+msgid ""
+"Key and value pairs that define on which compute nodes a flavor can run. "
+"These pairs must match corresponding pairs on the compute nodes. Use to "
+"implement special resources, such as flavors that run on only compute nodes "
+"with GPU hardware."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml105(para)
+msgid ""
+"Flavor customization can be limited by the hypervisor in use. For example "
+"the <systemitem>libvirt</systemitem> driver enables quotas on CPUs available"
+" to a VM, disk tuning, bandwidth I/O, watchdog behavior, random number "
+"generator device control, and instance VIF traffic control."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml110(term)
+msgid "CPU limits"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml111(para)
+msgid ""
+"You can configure the CPU limits with control parameters with the "
+"<placeholder-1/> client. For example, to configure the I/O limit, use:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml115(para)
+msgid ""
+"There are optional CPU control parameters for weight shares, enforcement "
+"intervals for runtime quotas, and a quota for maximum allowed bandwidth:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml121(para)
+msgid ""
+"<literal>cpu_shares</literal> specifies the proportional weighted share for "
+"the domain. If this element is omitted, the service defaults to the OS "
+"provided defaults. There is no unit for the value; it is a relative measure "
+"based on the setting of other VMs. For example, a VM configured with value "
+"2048 gets twice as much CPU time as a VM configured with value 1024."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml130(para)
+msgid ""
+"<literal>cpu_period</literal> specifies the enforcement interval (unit: "
+"microseconds) for QEMU and LXC hypervisors. Within a period, each VCPU of "
+"the domain is not allowed to consume more than the quota worth of runtime. "
+"The value should be in range <literal>[1000, 1000000]</literal>. A period "
+"with value 0 means no value."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml138(para)
+msgid ""
+"<literal>cpu_quota</literal> specifies the maximum allowed bandwidth (unit: "
+"microseconds). A domain with a negative-value quota indicates that the "
+"domain has infinite bandwidth, which means that it is not bandwidth "
+"controlled. The value should be in range <literal>[1000, "
+"18446744073709551]</literal> or less than 0. A quota with value 0 means no "
+"value. You can use this feature to ensure that all vCPUs run at the same "
+"speed. For example:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml147(para)
+msgid ""
+"In this example, the instance of <literal>m1.low_cpu</literal> can only "
+"consume a maximum of 50% CPU of a physical CPU computing capability."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml155(term)
+msgid "Disk tuning"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml156(para)
+msgid ""
+"Using disk I/O quotas, you can set maximum disk write to 10 MB per second "
+"for a VM user. For example:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml159(para)
+msgid "The disk I/O options are:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml162(para)
+msgid "disk_read_bytes_sec"
+msgstr "disk_read_bytes_sec"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml165(para)
+msgid "disk_read_iops_sec"
+msgstr "disk_read_iops_sec"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml168(para)
+msgid "disk_write_bytes_sec"
+msgstr "disk_write_bytes_sec"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml171(para)
+msgid "disk_write_iops_sec"
+msgstr "disk_write_iops_sec"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml174(para)
+msgid "disk_total_bytes_sec"
+msgstr "disk_total_bytes_sec"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml177(para)
+msgid "disk_total_iops_sec"
+msgstr "disk_total_iops_sec"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml180(para)
+msgid "The vif I/O options are:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml183(para)
+msgid "vif_inbound_ average"
+msgstr "vif_inbound_ average"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml186(para)
+msgid "vif_inbound_burst"
+msgstr "vif_inbound_burst"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml189(para)
+msgid "vif_inbound_peak"
+msgstr "vif_inbound_peak"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml192(para)
+msgid "vif_outbound_ average"
+msgstr "vif_outbound_ average"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml195(para)
+msgid "vif_outbound_burst"
+msgstr "vif_outbound_burst"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml198(para)
+msgid "vif_outbound_peak"
+msgstr "vif_outbound_peak"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml202(term)
+msgid "Bandwidth I/O"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml203(para)
+msgid ""
+"Incoming and outgoing traffic can be shaped independently. The bandwidth "
+"element can have at most one inbound and at most one outbound child element."
+" If you leave any of these children element out, no quality of service (QoS)"
+" is applied on that traffic direction. So, if you want to shape only the "
+"network's incoming traffic, use inbound only (and vice versa). Each element "
+"has one mandatory attribute average, which specifies the average bit rate on"
+" the interface being shaped."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml209(para)
+msgid ""
+"There are also two optional attributes (integer): <option>peak</option>, "
+"which specifies maximum rate at which bridge can send data "
+"(kilobytes/second), and <option>burst</option>, the amount of bytes that can"
+" be burst at peak speed (kilobytes). The rate is shared equally within "
+"domains connected to the network."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml214(para)
+msgid ""
+"The following example configures a bandwidth limit for instance network "
+"traffic:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml219(term)
+msgid "Watchdog behavior"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml220(para)
+msgid ""
+"For the <systemitem>libvirt</systemitem> driver, you can enable and set the "
+"behavior of a virtual hardware watchdog device for each flavor. Watchdog "
+"devices keep an eye on the guest server, and carry out the configured action"
+" if the server hangs. The watchdog uses the i6300esb device (emulating a PCI"
+" Intel 6300ESB). If <literal>hw_watchdog_action</literal> is not specified, "
+"the watchdog is disabled."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml226(para)
+msgid "To set the behavior, use:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml227(replaceable)
+#: ./doc/common/section_cli_nova_customize_flavors.xml257(replaceable)
+#: ./doc/common/section_cli_nova_customize_flavors.xml258(replaceable)
+#: ./doc/common/section_cli_nova_customize_flavors.xml259(replaceable)
+msgid "FLAVOR-NAME"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml227(replaceable)
+msgid "ACTION"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml228(para)
+msgid "Valid <replaceable>ACTION</replaceable> values are:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml231(para)
+msgid "<literal>disabled</literal>(default) The device is not attached."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml234(para)
+msgid "<literal>reset</literal>Forcefully reset the guest."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml238(para)
+msgid "<literal>poweroff</literal>Forcefully power off the guest."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml242(para)
+msgid "<literal>pause</literal>Pause the guest."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml245(para)
+msgid ""
+"<literal>none</literal>Only enable the watchdog; do nothing if the server "
+"hangs."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml249(para)
+msgid ""
+"Watchdog behavior set using a specific image's properties will override "
+"behavior set using flavors."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml254(term)
+msgid "Random-number generator"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml255(para)
+msgid ""
+"If a random-number generator device has been added to the instance through "
+"its image properties, the device can be enabled and configured using:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml258(replaceable)
+msgid "RATE-BYTES"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml259(replaceable)
+msgid "RATE-PERIOD"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml263(para)
+msgid ""
+"<replaceable>RATE-BYTES</replaceable>(Integer) Allowed amount of bytes that "
+"the guest can read from the host's entropy per period."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml267(para)
+msgid ""
+"<replaceable>RATE-PERIOD</replaceable>(Integer) Duration of the read period "
+"in seconds."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml273(term)
+msgid "Instance VIF traffic control"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml274(para)
+msgid ""
+"Flavors can also be assigned to particular projects. By default, a flavor is"
+" public and available to all projects. Private flavors are only accessible "
+"to those on the access list and are invisible to other projects. To create "
+"and assign a private flavor to a project, run these commands:"
+msgstr ""
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml6(title)
+msgid "Configure tenant-specific image locations with Object Storage"
+msgstr ""
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml14(para)
+msgid "The tenant who owns the image"
+msgstr "Le locataire qui possède l'image"
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml17(para)
+msgid ""
+"Tenants that are defined in <option>swift_store_admin_tenants</option> and "
+"that have admin-level accounts"
+msgstr ""
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml8(para)
+msgid ""
+"For some deployers, it is not ideal to store all images in one place to "
+"enable all tenants and users to access them. You can configure the Image "
+"Service to store image data in tenant-specific image locations. Then, only "
+"the following tenants can use the Image Service to access the created "
+"image:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml23(title)
+msgid "To configure tenant-specific image locations"
+msgstr ""
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml25(para)
+msgid ""
+"Configure swift as your <option>default_store</option> in the <filename"
+">glance-api.conf</filename> file."
+msgstr ""
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml33(para)
+msgid ""
+"<option>swift_store_multi_tenant</option>. Set to <literal>True</literal> to"
+" enable tenant-specific storage locations. Default is "
+"<literal>False</literal>."
+msgstr ""
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml39(para)
+msgid ""
+"<option>swift_store_admin_tenants</option>. Specify a list of tenant IDs "
+"that can grant read and write access to all Object Storage containers that "
+"are created by the Image Service."
+msgstr ""
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml30(para)
+msgid ""
+"Set these configuration options in the <filename>glance-api.conf</filename> "
+"file: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml48(para)
+msgid ""
+"With this configuration, images are stored in an Object Storage service "
+"(swift) endpoint that is pulled from the service catalog for the "
+"authenticated user."
+msgstr ""
 
 #: ./doc/common/ch_cli_keystone_commands.xml11(title)
 msgid "Identity service command-line client"
@@ -11472,11 +13633,6 @@ msgstr ""
 msgid "keystone optional arguments"
 msgstr ""
 
-#: ./doc/common/ch_cli_keystone_commands.xml346(para)
-#: ./doc/common/ch_cli_heat_commands.xml325(para)
-msgid "Shows the client version and exits."
-msgstr ""
-
 #: ./doc/common/ch_cli_keystone_commands.xml354(para)
 msgid "Set request timeout (in seconds)."
 msgstr ""
@@ -11536,14 +13692,6 @@ msgid ""
 "<code>env[OS_SERVICE_ENDPOINT]</code>."
 msgstr ""
 
-#: ./doc/common/ch_cli_keystone_commands.xml445(para)
-#: ./doc/common/ch_cli_swift_commands.xml302(para)
-#: ./doc/common/ch_cli_trove_commands.xml558(para)
-msgid ""
-"Specify a CA bundle file to use in verifying a TLS (https) server "
-"certificate. Defaults to <code>env[OS_CACERT]</code>."
-msgstr ""
-
 #: ./doc/common/ch_cli_keystone_commands.xml455(para)
 msgid ""
 "Explicitly allow keystoneclient to perform \"insecure\" TLS (https) "
@@ -11995,3130 +14143,1099 @@ msgstr ""
 msgid "Name or ID of user to update."
 msgstr ""
 
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_getstart_conceptual_arch.xml16(None)
+#: ./doc/common/section_objectstorage-ringbuilder.xml6(title)
+msgid "Ring-builder"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-ringbuilder.xml7(para)
 msgid ""
-"@@image: 'figures/openstack_havana_conceptual_arch.png'; "
-"md5=96e1d5492d4c865fc9145710bb294a91"
+"Use the swift-ring-builder utility to build and manage rings. This utility "
+"assigns partitions to devices and writes an optimized Python structure to a "
+"gzipped, serialized file on disk for transmission to the servers. The server"
+" processes occasionally check the modification time of the file and reload "
+"in-memory copies of the ring structure as needed. If you use a slightly "
+"older version of the ring, one of the three replicas for a partition subset "
+"will be incorrect because of the way the ring-builder manages changes to the"
+" ring. You can work around this issue."
 msgstr ""
 
-#: ./doc/common/section_getstart_conceptual_arch.xml6(title)
-msgid "Conceptual architecture"
-msgstr "Principe de l’architecture"
-
-#: ./doc/common/section_getstart_conceptual_arch.xml7(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml17(para)
 msgid ""
-"The following diagram shows the relationships among the OpenStack services:"
-msgstr "Le diagramme suivant montre une vue schématisée et simplifiée de l’architecture d’OpenStack du point de vue de l’utilisateur. "
+"The ring-builder also keeps its own builder file with the ring information "
+"and additional data required to build future rings. It is very important to "
+"keep multiple backup copies of these builder files. One option is to copy "
+"the builder files out to every server while copying the ring files "
+"themselves. Another is to upload the builder files into the cluster itself. "
+"If you lose the builder file, you have to create a new ring from scratch. "
+"Nearly all partitions would be assigned to different devices and, therefore,"
+" nearly all of the stored data would have to be replicated to new locations."
+" So, recovery from a builder file loss is possible, but data would be "
+"unreachable for an extended time."
+msgstr ""
 
-#: ./doc/common/section_getstart_conceptual_arch.xml11(title)
-msgid "OpenStack conceptual architecture"
-msgstr "Principe de l’architecture de l'OpenStack"
+#: ./doc/common/section_objectstorage-ringbuilder.xml30(title)
+msgid "Ring data structure"
+msgstr ""
 
-#: ./doc/common/section_cli_nova_metadata.xml9(title)
-msgid "Insert metadata during launch"
-msgstr "<placeholder-2/>"
-
-#: ./doc/common/section_cli_nova_metadata.xml10(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml31(para)
 msgid ""
-"When booting a server, you can also add metadata, so that you can more "
-"easily identify it amongst your ever-growing elastic cloud. Use the "
-"<literal>--meta</literal> option with a key=value pair, where you can make "
-"up the string for both the key and the value. For example, you could add a "
-"description and also the creator of the server. <placeholder-1/>"
-msgstr "Lorsque vous bootez un serveur, vous pouvez aussi ajouter des métadonnées, pour pouvoir l'identifier plus facilement au sein de votre toujours grandissant cloud élastique. Utilisez l'option <literal>--meta</literal> avec une paire key=value, où vous pouvez faire le lien entre la clé et la valeur. Par exemple, vous pouvez ajouter une description et aussi un créateur du serveur.<placeholder-1/>"
+"The ring data structure consists of three top level fields: a list of "
+"devices in the cluster, a list of lists of device ids indicating partition "
+"to device assignments, and an integer indicating the number of bits to shift"
+" an MD5 hash to calculate the partition for the hash."
+msgstr ""
 
-#: ./doc/common/section_cli_nova_metadata.xml18(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml38(title)
+msgid "Partition assignment list"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-ringbuilder.xml39(para)
 msgid ""
-"When viewing the server information, you can see the metadata included on "
-"the <literal>metadata</literal> line: <placeholder-1/>"
-msgstr "Lorsque vous voyez les informations du serveur, vous pouvez voir les métadonnées inclues sur la ligne <literal>metadata</literal>: <placeholder-1/>"
+"This is a list of <literal>array(‘H’)</literal> of devices ids. The "
+"outermost list contains an <literal>array(‘H’)</literal> for each replica. "
+"Each <literal>array(‘H’)</literal> has a length equal to the partition count"
+" for the ring. Each integer in the <literal>array(‘H’)</literal> is an index"
+" into the above list of devices. The partition list is known internally to "
+"the Ring class as <literal>_replica2part2dev_id</literal>."
+msgstr ""
 
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-arch.xml23(None)
+#: ./doc/common/section_objectstorage-ringbuilder.xml48(para)
 msgid ""
-"@@image: '../common/figures/objectstorage-arch.png'; "
-"md5=90f6c7cf3947d7987eeb55d657cdc927"
+"So, to create a list of device dictionaries assigned to a partition, the "
+"Python code would look like: <placeholder-1/>"
 msgstr ""
 
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-arch.xml60(None)
+#: ./doc/common/section_objectstorage-ringbuilder.xml52(para)
 msgid ""
-"@@image: '../common/figures/objectstorage-nodes.png'; "
-"md5=2aa7eb3bddcf6826f33469920dc2a9c3"
+"That code is a little simplistic because it does not account for the removal"
+" of duplicate devices. If a ring has more replicas than devices, a partition"
+" will have more than one replica on a device."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml11(title)
-msgid "Cluster architecture"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-arch.xml13(title)
-msgid "Access tier"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-arch.xml14(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml56(para)
 msgid ""
-"Large-scale deployments segment off an access tier, which is considered the "
-"Object Storage system's central hub. The access tier fields the incoming API"
-" requests from clients and moves data in and out of the system. This tier "
-"consists of front-end load balancers, ssl-terminators, and authentication "
-"services. It runs the (distributed) brain of the Object Storage system: the "
-"proxy server processes."
+"<literal>array(‘H’)</literal> is used for memory conservation as there may "
+"be millions of partitions."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml20(title)
-msgid "Object Storage architecture"
+#: ./doc/common/section_objectstorage-ringbuilder.xml61(title)
+msgid "Replica counts"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml27(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml62(para)
 msgid ""
-"Because access servers are collocated in their own tier, you can scale out "
-"read/write access regardless of the storage capacity. For example, if a "
-"cluster is on the public Internet, requires SSL termination, and has a high "
-"demand for data access, you can provision many access servers. However, if "
-"the cluster is on a private network and used primarily for archival "
-"purposes, you need fewer access servers."
+"To support the gradual change in replica counts, a ring can have a real "
+"number of replicas and is not restricted to an integer number of replicas."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml32(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml65(para)
 msgid ""
-"Since this is an HTTP addressable storage service, you may incorporate a "
-"load balancer into the access tier."
+"A fractional replica count is for the whole ring and not for individual "
+"partitions. It indicates the average number of replicas for each partition. "
+"For example, a replica count of 3.2 means that 20 percent of partitions have"
+" four replicas and 80 percent have three replicas."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml34(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml70(para)
+msgid "The replica count is adjustable."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-ringbuilder.xml71(para)
+msgid "Example:"
+msgstr "Exemple:"
+
+#: ./doc/common/section_objectstorage-ringbuilder.xml74(para)
 msgid ""
-"Typically, the tier consists of a collection of 1U servers. These machines "
-"use a moderate amount of RAM and are network I/O intensive. Since these "
-"systems field each incoming API request, you should provision them with two "
-"high-throughput (10GbE) interfaces - one for the incoming \"front-end\" "
-"requests and the other for the \"back-end\" access to the object storage "
-"nodes to put and fetch data."
+"You must rebalance the replica ring in globally distributed clusters. "
+"Operators of these clusters generally want an equal number of replicas and "
+"regions. Therefore, when an operator adds or removes a region, the operator "
+"adds or removes a replica. Removing unneeded replicas saves on the cost of "
+"disks."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml40(title)
-#: ./doc/common/section_objectstorage-arch.xml69(title)
-msgid "Factors to consider"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-arch.xml41(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml80(para)
 msgid ""
-"For most publicly facing deployments as well as private deployments "
-"available across a wide-reaching corporate network, you use SSL to encrypt "
-"traffic to the client. SSL adds significant processing load to establish "
-"sessions between clients, which is why you have to provision more capacity "
-"in the access layer. SSL may not be required for private deployments on "
-"trusted networks."
+"You can gradually increase the replica count at a rate that does not "
+"adversely affect cluster performance."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml49(title)
-msgid "Storage nodes"
-msgstr "Noeuds de stockage"
-
-#: ./doc/common/section_objectstorage-arch.xml50(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml90(para)
 msgid ""
-"In most configurations, each of the five zones should have an equal amount "
-"of storage capacity. Storage nodes use a reasonable amount of memory and "
-"CPU. Metadata needs to be readily available to return objects quickly. The "
-"object stores run services not only to field incoming requests from the "
-"access tier, but to also run replicators, auditors, and reapers. You can "
-"provision object stores provisioned with single gigabit or 10 gigabit "
-"network interface depending on the expected workload and desired "
-"performance."
+"Changes take effect after the ring is rebalanced. Therefore, if you intend "
+"to change from 3 replicas to 3.01 but you accidentally type "
+"<literal>2.01</literal>, no data is lost."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml57(title)
-#: ./doc/common/section_storage-concepts.xml21(td)
-#: ./doc/common/section_objectstorage-characteristics.xml46(title)
-msgid "Object Storage (swift)"
+#: ./doc/common/section_objectstorage-ringbuilder.xml95(replaceable)
+msgid "X.builder"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml64(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml94(para)
 msgid ""
-"Currently, a 2TB or 3TB SATA disk delivers good performance for the price. "
-"You can use desktop-grade drives if you have responsive remote hands in the "
-"datacenter and enterprise-grade drives if you don't."
+"Additionally, <placeholder-1/> can now take a decimal argument for the "
+"number of replicas."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml70(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml100(title)
+msgid "Partition shift value"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-ringbuilder.xml101(para)
 msgid ""
-"You should keep in mind the desired I/O performance for single-threaded "
-"requests . This system does not use RAID, so a single disk handles each "
-"request for an object. Disk performance impacts single-threaded response "
-"rates."
+"The partition shift value is known internally to the Ring class as "
+"<literal>_part_shift</literal>. This value is used to shift an MD5 hash to "
+"calculate the partition where the data for that hash should reside. Only the"
+" top four bytes of the hash is used in this process. For example, to compute"
+" the partition for the <literal>/account/container/object</literal> path, "
+"the Python code might look like the following code: <placeholder-1/>"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml73(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml112(para)
 msgid ""
-"To achieve apparent higher throughput, the object storage system is designed"
-" to handle concurrent uploads/downloads. The network I/O capacity (1GbE, "
-"bonded 1GbE pair, or 10GbE) should match your desired concurrent throughput "
-"needs for reads and writes."
+"For a ring generated with part_power P, the partition shift value is "
+"<literal>32 - P</literal>."
 msgstr ""
 
-#: ./doc/common/section_dochistory.xml6(title)
-msgid "Document change history"
+#: ./doc/common/section_objectstorage-ringbuilder.xml116(title)
+msgid "Build the ring"
 msgstr ""
 
-#: ./doc/common/section_dochistory.xml8(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml117(para)
+msgid "The ring builder process includes these high-level steps:"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-ringbuilder.xml121(para)
 msgid ""
-"This version of the guide replaces and obsoletes all previous versions. The "
-"following table describes the most recent changes:"
+"The utility calculates the number of partitions to assign to each device "
+"based on the weight of the device. For example, for a partition at the power"
+" of 20, the ring has 1,048,576 partitions. One thousand devices of equal "
+"weight will each want 1,048.576 partitions. The devices are sorted by the "
+"number of partitions they desire and kept in order throughout the "
+"initialization process."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml10(title)
-msgid "Host aggregates"
-msgstr "Agrégats d'hôtes"
-
-#: ./doc/common/section_cli_nova_host_aggregates.xml11(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml131(para)
 msgid ""
-"Host aggregates are a mechanism to further partition an availability zone; "
-"while availability zones are visible to users, host aggregates are only "
-"visible to administrators. Host Aggregates provide a mechanism to allow "
-"administrators to assign key-value pairs to groups of machines. Each node "
-"can have multiple aggregates, each aggregate can have multiple key-value "
-"pairs, and the same key-value pair can be assigned to multiple aggregates. "
-"This information can be used in the scheduler to enable advanced scheduling,"
-" to set up hypervisor resource pools or to define logical groups for "
-"migration."
+"Each device is also assigned a random tiebreaker value that is used when two"
+" devices desire the same number of partitions. This tiebreaker is not stored"
+" on disk anywhere, and so two different rings created with the same "
+"parameters will have different partition assignments. For repeatable "
+"partition assignments, <literal>RingBuilder.rebalance()</literal> takes an "
+"optional seed value that seeds the Python pseudo-random number generator."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml23(title)
-msgid "Command-line interface"
-msgstr "Interface de ligne de commande"
-
-#: ./doc/common/section_cli_nova_host_aggregates.xml35(replaceable)
-#: ./doc/common/section_cli_nova_host_aggregates.xml111(replaceable)
-msgid "&lt;name&gt;"
-msgstr "&lt;name&gt;"
-
-#: ./doc/common/section_cli_nova_host_aggregates.xml36(replaceable)
-msgid "&lt;availability-zone&gt;"
-msgstr "&lt;availability-zone&gt;"
-
-#: ./doc/common/section_cli_nova_host_aggregates.xml38(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml145(para)
 msgid ""
-"Create a new aggregate named <replaceable>&lt;name&gt;</replaceable> in "
-"availability zone <replaceable>&lt;availability-zone&gt;</replaceable>. "
-"Returns the ID of the newly created aggregate. Hosts can be made available "
-"to multiple availability zones, but administrators should be careful when "
-"adding the host to a different host aggregate within the same availability "
-"zone and pay attention when using the <placeholder-1/> and <placeholder-2/> "
-"commands to avoid user confusion when they boot instances in different "
-"availability zones. An error occurs if you cannot add a particular host to "
-"an aggregate zone for which it is not intended."
+"The ring builder assigns each partition replica to the device that requires "
+"most partitions at that point while keeping it as far away as possible from "
+"other replicas. The ring builder prefers to assign a replica to a device in "
+"a region that does not already have a replica. If no such region is "
+"available, the ring builder searches for a device in a different zone, or on"
+" a different server. If it does not find one, it looks for a device with no "
+"replicas. Finally, if all options are exhausted, the ring builder assigns "
+"the replica to the device that has the fewest replicas already assigned."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml60(replaceable)
-#: ./doc/common/section_cli_nova_host_aggregates.xml68(replaceable)
-#: ./doc/common/section_cli_nova_host_aggregates.xml76(replaceable)
-#: ./doc/common/section_cli_nova_host_aggregates.xml87(replaceable)
-#: ./doc/common/section_cli_nova_host_aggregates.xml98(replaceable)
-#: ./doc/common/section_cli_nova_host_aggregates.xml110(replaceable)
-msgid "&lt;id&gt;"
-msgstr "&lt;id&gt;"
-
-#: ./doc/common/section_cli_nova_host_aggregates.xml62(para)
-msgid "Delete an aggregate with id <replaceable>&lt;id&gt;</replaceable>."
-msgstr "Supprimer un agrégat ayant l'id <replaceable>&lt;id&gt;</replaceable>."
-
-#: ./doc/common/section_cli_nova_host_aggregates.xml70(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml159(para)
 msgid ""
-"Show details of the aggregate with id <replaceable>&lt;id&gt;</replaceable>."
-msgstr "Montrer les détails de l'agrégat ayant l'id <replaceable>&lt;id&gt;</replaceable>.."
+"The ring builder assigns multiple replicas to one device only if the ring "
+"has fewer devices than it has replicas."
+msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml77(replaceable)
-#: ./doc/common/section_cli_nova_host_aggregates.xml88(replaceable)
-msgid "&lt;host&gt;"
-msgstr "&lt;host&gt;"
-
-#: ./doc/common/section_cli_nova_host_aggregates.xml79(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml165(para)
 msgid ""
-"Add host with name <replaceable>&lt;host&gt;</replaceable> to aggregate with"
-" id <replaceable>&lt;id&gt;</replaceable>."
-msgstr "Ajouter l'hôte nommé <replaceable>&lt;host&gt;</replaceable> à l'agrégat ayant l'id <replaceable>&lt;id&gt;</replaceable>."
+"When building a new ring from an old ring, the ring builder recalculates the"
+" desired number of partitions that each device wants."
+msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml90(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml174(para)
 msgid ""
-"Remove the host with name <replaceable>&lt;host&gt;</replaceable> from the "
-"aggregate with id <replaceable>&lt;id&gt;</replaceable>."
-msgstr "Supprimer l'hôte nommé <replaceable>&lt;host&gt;</replaceable> de l'agrégat ayant l'id <replaceable>&lt;id&gt;</replaceable>."
+"The ring builder unassigns any assigned partitions from any removed devices "
+"and adds these partitions to the gathered list."
+msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml99(replaceable)
-#: ./doc/common/section_cli_nova_host_aggregates.xml100(replaceable)
-msgid "&lt;key=value&gt;"
-msgstr "&lt;key=value&gt;"
-
-#: ./doc/common/section_cli_nova_host_aggregates.xml103(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml180(para)
 msgid ""
-"Add or update metadata (key-value pairs) associated with the aggregate with "
-"id <replaceable>&lt;id&gt;</replaceable>."
-msgstr "Ajouter ou modifier des méta données (paires de valeurs-clés) associées à l'agrégat ayant l'id <replaceable>&lt;id&gt;</replaceable>."
-
-#: ./doc/common/section_cli_nova_host_aggregates.xml112(replaceable)
-msgid "&lt;availability_zone&gt;"
-msgstr "&lt;availability_zone&gt;"
-
-#: ./doc/common/section_cli_nova_host_aggregates.xml114(para)
-msgid "Update the name and availability zone (optional) for the aggregate."
+"The ring builder unassigns any partition replicas that can be spread out for"
+" better durability and adds these partitions to the gathered list."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml128(para)
-msgid "Put/resume host into/from maintenance."
-msgstr "Mettre/retirer les hôtes en/de la maintenance."
-
-#: ./doc/common/section_cli_nova_host_aggregates.xml24(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml187(para)
 msgid ""
-"The <placeholder-1/> command-line tool supports the following aggregate-"
-"related commands. <placeholder-2/>"
-msgstr "L'outil de ligne de commande <placeholder-1/> supporte les commandes relatives aux agrégats suivantes. <placeholder-2/>"
+"The ring builder unassigns random partitions from any devices that have more"
+" partitions than they need and adds these partitions to the gathered list."
+msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml134(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml170(para)
 msgid ""
-"Only administrators can access these commands. If you try to use these "
-"commands and the user name and tenant that you use to access the Compute "
-"service do not have the <literal>admin</literal> role or the appropriate "
-"privileges, these errors occur:"
+"The ring builder unassigns partitions and gathers these partitions for "
+"reassignment, as follows: <placeholder-1/>"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml146(title)
-msgid "Configure scheduler to support host aggregates"
-msgstr "Configurer le planificateur pour qu'il supporte les agrégats d'hôtes"
-
-#: ./doc/common/section_cli_nova_host_aggregates.xml147(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml197(para)
 msgid ""
-"One common use case for host aggregates is when you want to support "
-"scheduling instances to a subset of compute hosts because they have a "
-"specific capability. For example, you may want to allow users to request "
-"compute hosts that have SSD drives if they need access to faster disk I/O, "
-"or access to compute hosts that have GPU cards to take advantage of GPU-"
-"accelerated code."
-msgstr "Généralement, les agrégats d'hôtes sont utilisés lorsque vous souhaitez supporter les instances de planifications pour un sous-ensemble d'ordinateurs hôtes du fait de leur capacité spécifique. Par exemple, vous pourrez vouloir autoriser les utilisateurs à demander aux ordinateurs hôtes ayant des disques SSD  s'ils nécessitent un accès à un disque I/O plus rapide ou un accès à des ordinateurs hôtes qui ont des cartes GPU tirant partie des codes GPU avancés."
+"The ring builder reassigns the gathered partitions to devices by using a "
+"similar method to the one described previously."
+msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml154(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml202(para)
 msgid ""
-"To configure the scheduler to support host aggregates, the "
-"<literal>scheduler_default_filters</literal> configuration option must "
-"contain the <literal>AggregateInstanceExtraSpecsFilter</literal> in addition"
-" to the other filters used by the scheduler. Add the following line to "
-"<filename>/etc/nova/nova.conf</filename> on the host that runs the "
-"<systemitem class=\"service\">nova-scheduler</systemitem> service to enable "
-"host aggregates filtering, as well as the other filters that are typically "
-"enabled:<placeholder-1/>"
+"When the ring builder reassigns a replica to a partition, the ring builder "
+"records the time of the reassignment. The ring builder uses this value when "
+"it gathers partitions for reassignment so that no partition is moved twice "
+"in a configurable amount of time. The RingBuilder class knows this "
+"configurable amount of time as <literal>min_part_hours</literal>. The ring "
+"builder ignores this restriction for replicas of partitions on removed "
+"devices because removal of a device happens on device failure only, and "
+"reassignment is the only choice."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml168(title)
-msgid "Example: Specify compute hosts with SSDs"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_host_aggregates.xml169(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml216(para)
 msgid ""
-"This example configures the Compute service to enable users to request nodes"
-" that have solid-state drives (SSDs). You create a <literal>fast-"
-"io</literal> host aggregate in the <literal>nova</literal> availability zone"
-" and you add the <literal>ssd=true</literal> key-value pair to the "
-"aggregate. Then, you add the <literal>node1</literal>, and "
-"<literal>node2</literal> compute nodes to it."
+"Theses steps do not always perfectly rebalance a ring due to the random "
+"nature of gathering partitions for reassignment. To help reach a more "
+"balanced ring, the rebalance process is repeated until near perfect (less "
+"than 1 percent off) or when the balance does not improve by at least 1 "
+"percent (indicating we probably cannot get perfect balance due to wildly "
+"imbalanced zones or too many partitions recently moved)."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml204(para)
+#: ./doc/common/section_keystone-ssl-config.xml7(title)
+msgid "Configure the Identity Service with SSL"
+msgstr "Configurer le service d'identité avec SSL"
+
+#: ./doc/common/section_keystone-ssl-config.xml8(para)
+msgid "You can configure the Identity Service to support two-way SSL."
+msgstr ""
+
+#: ./doc/common/section_keystone-ssl-config.xml10(para)
+msgid "You must obtain the x509 certificates externally and configure them."
+msgstr ""
+
+#: ./doc/common/section_keystone-ssl-config.xml12(para)
 msgid ""
-"Use the <placeholder-1/> command to create the "
-"<replaceable>ssd.large</replaceable> flavor called with an ID of 6, 8GB of "
-"RAM, 80GB root disk, and four vCPUs."
+"The Identity Service provides a set of sample certificates in the <filename "
+"class=\"directory\">examples/pki/certs</filename> and <filename "
+"class=\"directory\">examples/pki/private</filename> directories:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml207(replaceable)
-#: ./doc/common/section_cli_nova_host_aggregates.xml219(replaceable)
-msgid "ssd.large"
-msgstr ""
+#: ./doc/common/section_keystone-ssl-config.xml18(title)
+msgid "Certificate types"
+msgstr "Types de certificats"
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml207(replaceable)
-msgid "6"
-msgstr ""
+#: ./doc/common/section_keystone-ssl-config.xml20(term)
+msgid "cacert.pem"
+msgstr "cacert.pem"
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml207(replaceable)
-msgid "8192"
-msgstr ""
+#: ./doc/common/section_keystone-ssl-config.xml22(para)
+msgid "Certificate Authority chain to validate against."
+msgstr "Certifie la chaîne d'Autorité comme support de validation. "
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml207(replaceable)
-msgid "80"
-msgstr ""
+#: ./doc/common/section_keystone-ssl-config.xml27(term)
+msgid "ssl_cert.pem"
+msgstr "ssl_cert.pem"
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml207(replaceable)
-msgid "4"
-msgstr ""
+#: ./doc/common/section_keystone-ssl-config.xml29(para)
+msgid "Public certificate for Identity Service server."
+msgstr "Certificat public pour le serveur Keystone."
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml213(para)
+#: ./doc/common/section_keystone-ssl-config.xml34(term)
+msgid "middleware.pem"
+msgstr "middleware.pem"
+
+#: ./doc/common/section_keystone-ssl-config.xml36(para)
+msgid "Public and private certificate for Identity Service middleware/client."
+msgstr "Certificat public et prive pour le client de middleware de Keystone"
+
+#: ./doc/common/section_keystone-ssl-config.xml41(term)
+msgid "cakey.pem"
+msgstr "cakey.pem"
+
+#: ./doc/common/section_keystone-ssl-config.xml43(para)
+msgid "Private key for the CA."
+msgstr "Clé privée pour le CA"
+
+#: ./doc/common/section_keystone-ssl-config.xml47(term)
+msgid "ssl_key.pem"
+msgstr "ssl_key.pem"
+
+#: ./doc/common/section_keystone-ssl-config.xml49(para)
+msgid "Private key for the Identity Service server."
+msgstr "Clé privée pour le serveur Keystone "
+
+#: ./doc/common/section_keystone-ssl-config.xml55(para)
 msgid ""
-"Once the flavor is created, specify one or more key-value pairs that match "
-"the key-value pairs on the host aggregates. In this case, that is the "
-"<replaceable>ssd=true</replaceable> key-value pair. Setting a key-value pair"
-" on a flavor is done using the <placeholder-1/> command."
-msgstr ""
+"You can choose names for these certificates. You can also combine the "
+"public/private keys in the same file, if you wish. These certificates are "
+"provided as an example."
+msgstr "Il faut noter qu'il est possible de choisir les noms que vous voulez pour ces certificats, ou de combiner les clés publiques/privées dans le même fichier si vous le souhaitez. Ces certificats sont juste fournis à titre d'exemple. "
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml219(replaceable)
-msgid "ssd=true"
-msgstr ""
+#: ./doc/common/section_keystone-ssl-config.xml61(title)
+msgid "SSL configuration"
+msgstr "Configuration SSL"
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml220(para)
+#: ./doc/common/section_keystone-ssl-config.xml62(para)
 msgid ""
-"Once it is set, you should see the <literal>extra_specs</literal> property "
-"of the <literal>ssd.large</literal> flavor populated with a key of "
-"<literal>ssd</literal> and a corresponding value of <literal>true</literal>."
-msgstr ""
+"To enable SSL with client authentication, modify the "
+"<literal>[ssl]</literal> section in the "
+"<filename>etc/keystone.conf</filename> file. The following SSL configuration"
+" example uses the included sample certificates:"
+msgstr "Pour permettre le SSL avec l'authentification par client, il faut modifier le fichier <filename>etc/keystone.conf</filename> dans la section <literal>[ssl]</literal>. Exemple de configuration SSL  en utilisant les certificats témoins inclus :  "
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml241(para)
+#: ./doc/common/section_keystone-ssl-config.xml74(title)
+msgid "Options"
+msgstr "Options"
+
+#: ./doc/common/section_keystone-ssl-config.xml76(para)
+msgid "<literal>enable</literal>. True enables SSL. Default is False."
+msgstr "\t•\t<literal>enable</literal>: True active le SSL. Par défaut False "
+
+#: ./doc/common/section_keystone-ssl-config.xml80(para)
 msgid ""
-"Now, when a user requests an instance with the <literal>ssd.large</literal> "
-"flavor, the scheduler only considers hosts with the "
-"<literal>ssd=true</literal> key-value pair. In this example, these are "
-"<literal>node1</literal> and <literal>node2</literal>."
-msgstr ""
+"<literal>certfile</literal>. Path to the Identity Service public certificate"
+" file."
+msgstr "<literal>certfile</literal>: Chemin vers les fichiers des certificat Keystone publics."
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml249(title)
-msgid "XenServer hypervisor pools to support live migration"
-msgstr "Pools de l'hyperviseur XenServeur pour supporter la live migration"
-
-#: ./doc/common/section_cli_nova_host_aggregates.xml251(para)
+#: ./doc/common/section_keystone-ssl-config.xml84(para)
 msgid ""
-"When using the XenAPI-based hypervisor, the Compute service uses host "
-"aggregates to manage XenServer Resource pools, which are used in supporting "
-"live migration."
-msgstr ""
+"<literal>keyfile</literal>. Path to the Identity Service private certificate"
+" file. If you include the private key in the certfile, you can omit the "
+"keyfile."
+msgstr "• <literal>keyfile</literal>: Chemin vers les fichiers des certificats Keystone privés. Si la clé privé est incluse dans le certfile, le keyfile peut être omis."
 
-#: ./doc/common/section_keystone_db_sync.xml6(title)
-msgid "Migrate the Identity Service database"
-msgstr ""
+#: ./doc/common/section_keystone-ssl-config.xml90(para)
+msgid "<literal>ca_certs</literal>. Path to the CA trust chain."
+msgstr "<literal>ca_certs</literal>: Chemin vers la chaîne de confiance du CA."
 
-#: ./doc/common/section_keystone_db_sync.xml7(para)
+#: ./doc/common/section_keystone-ssl-config.xml94(para)
 msgid ""
-"Between revisions of the Identity Service project, you might need to "
-"complete SQL migrations. The Identity Service project uses SQLAlchemy-"
-"migrate (see <link href=\"http://code.google.com/p/sqlalchemy-"
-"migrate/\">http://code.google.com/p/sqlalchemy-migrate/</link>) to migrate "
-"the SQL database between revisions. For core components, the source code "
-"stores migrations in a central repository under a "
-"<filename>keystone/common/sql/migrate_repo</filename> directory."
-msgstr ""
+"<literal>cert_required</literal>. Requires client certificate. Default is "
+"False."
+msgstr "<literal>cert_required</literal>: Requiert le certificat du client. Par défaut False "
 
-#: ./doc/common/section_keystone_db_sync.xml17(para)
+#: ./doc/common/section_cli_keystone_apiv3.xml5(title)
+msgid "Use Identity Service API v3 instead of API v2.0"
+msgstr "Utilise Service d'Identité API v3 au lieu de API v2.0"
+
+#: ./doc/common/section_cli_keystone_apiv3.xml6(para)
 msgid ""
-"Extensions to the Identity Service might also require SQL migrations. The "
-"directory <filename>keystone/contrib/example</filename> in the keystone "
-"repository contains a sample extension migration."
+"Use the following parameters in combination on any keystone command to "
+"specify which version of the API to use:"
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml23(title)
-msgid "To set up a migration for an extension"
-msgstr ""
-
-#: ./doc/common/section_keystone_db_sync.xml25(para)
+#: ./doc/common/section_cli_keystone_apiv3.xml11(para)
 msgid ""
-"Create a directory structure where <literal>my_extension</literal> is the "
-"name of the extension, as follows: "
-"<filename>keystone/contrib/my_extension/migrate_repo/versions/</filename>."
+"<parameter>--os-endpoint</parameter>. The endpoint to use instead of the one"
+" in the service catalog. Defaults to <code>env[OS_SERVICE_ENDPOINT]</code>."
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml31(para)
+#: ./doc/common/section_cli_keystone_apiv3.xml15(para)
 msgid ""
-"Create empty <filename>__init__.py</filename> files in the "
-"<filename>migrate_repo</filename> and <filename>versions</filename> "
-"subdirectories."
+"The <literal>keystone</literal> client detects the version of the API from "
+"this parameter."
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml37(para)
+#: ./doc/common/section_cli_keystone_apiv3.xml19(para)
 msgid ""
-"Create a <filename>migrate.cfg</filename> configuration file in the "
-"<filename>migrate_repo</filename> subdirectory, which conforms to a "
-"key/value <filename>.ini</filename> file format."
+"<parameter>--os-auth_url</parameter>. The Identity Service endpoint to use "
+"for authentication. Defaults to <code>env[OS_AUTH_URL]</code>."
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml41(para)
-msgid "An example configuration file:"
-msgstr ""
-
-#: ./doc/common/section_keystone_db_sync.xml49(title)
-msgid "To test a migration for a specific extension"
-msgstr ""
-
-#: ./doc/common/section_keystone_db_sync.xml50(para)
+#: ./doc/common/section_cli_keystone_apiv3.xml25(para)
 msgid ""
-"You can use the <placeholder-1/> command with the "
-"<parameter>--extension</parameter> parameter for both the <placeholder-2/> "
-"and <placeholder-3/> commands. Ensure that the required configuration files "
-"exist before completing these steps."
+"<parameter>--os-identity-api-version</parameter>. The Identity Service API "
+"version. Defaults to <code>env[OS_IDENTITY_API_VERSION]</code> or "
+"<literal>2.0</literal>."
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml57(para)
-msgid "Test your migrations with an <literal>example</literal> extension:"
+#: ./doc/common/section_cli_keystone_apiv3.xml31(para)
+msgid "For example, use the following parameters to use API v3:"
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml62(para)
-msgid "Migrate to version 1:"
+#: ./doc/common/section_cli_keystone_apiv3.xml33(parameter)
+#: ./doc/common/section_cli_keystone_apiv3.xml35(parameter)
+msgid "--os-auth_url"
+msgstr "--os-auth_url"
+
+#: ./doc/common/section_cli_keystone_apiv3.xml33(parameter)
+#: ./doc/common/section_cli_keystone_apiv3.xml35(parameter)
+msgid "--os-identity-api-version"
+msgstr "--os-identity-api-version"
+
+#: ./doc/common/section_cli_keystone_apiv3.xml34(para)
+msgid "Use the following parameters to use API v2.0:"
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml66(para)
-msgid "Migrate back to version 0:"
+#: ./doc/common/section_conventions.xml8(title)
+msgid "Conventions"
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml70(para)
-msgid "Check the version:"
-msgstr "Vérifiez la version:"
-
-#: ./doc/common/section_getstart_trove.xml5(title)
-msgid "Database service overview"
+#: ./doc/common/section_conventions.xml9(para)
+msgid "The OpenStack documentation uses several typesetting conventions."
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml6(para)
+#: ./doc/common/section_conventions.xml13(title)
+msgid "Notices"
+msgstr ""
+
+#: ./doc/common/section_conventions.xml14(para)
+msgid "Notices take three forms:"
+msgstr ""
+
+#: ./doc/common/section_conventions.xml16(para)
 msgid ""
-"The Database service provides scalable and reliable cloud provisioning "
-"functionality for both relational and non-relational database engines. Users"
-" can quickly and easily utilize database features without the burden of "
-"handling complex administrative tasks. Cloud users and database "
-"administrators can provision and manage multiple database instances as "
-"needed."
+"The information in a note is usually in the form of a handy tip or reminder."
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml7(para)
+#: ./doc/common/section_conventions.xml20(para)
 msgid ""
-"The Database service provides resource isolation at high performance levels,"
-" and automates complex administrative tasks such as deployment, "
-"configuration, patching, backups, restores, and monitoring."
+"The information in an important notice is something you must be aware of "
+"before proceeding."
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml9(title)
-msgid "Process flow example."
-msgstr ""
-
-#: ./doc/common/section_getstart_trove.xml9(para)
-msgid "Here is a high-level process flow example for using Database services:"
-msgstr ""
-
-#: ./doc/common/section_getstart_trove.xml12(para)
-msgid "Administrator sets up infrastructure:"
-msgstr ""
-
-#: ./doc/common/section_getstart_trove.xml15(para)
-msgid "OpenStack administrator installs the Database service."
-msgstr ""
-
-#: ./doc/common/section_getstart_trove.xml18(para)
+#: ./doc/common/section_conventions.xml24(para)
 msgid ""
-"She creates one image for each type of database the administrator wants to "
-"have (one for MySQL, one for MongoDB, and so on)."
+"The information in warnings is critical. Warnings provide additional "
+"information about risk of data loss or security issues."
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml23(para)
+#: ./doc/common/section_conventions.xml31(title)
+msgid "Command prompts"
+msgstr ""
+
+#: ./doc/common/section_conventions.xml32(para)
 msgid ""
-"OpenStack administrator updates the datastore to use the new images, using "
-"the <placeholder-1/> command."
+"Commands prefixed with the <literal>#</literal> prompt are to be executed by"
+" the <literal>root</literal> user. These examples can also be executed by "
+"using the <placeholder-1/> command, if available."
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml30(para)
-msgid "End user uses database service:"
-msgstr ""
-
-#: ./doc/common/section_getstart_trove.xml33(para)
+#: ./doc/common/section_conventions.xml36(para)
 msgid ""
-"Now that the basic infrastructure is set up, an end user can create a Trove "
-"instance (database) whenever the user wants, using the <placeholder-1/> "
-"command."
+"Commands prefixed with the <literal>$</literal> prompt can be executed by "
+"any user, including <literal>root</literal>."
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml41(replaceable)
-msgid "instanceID"
+#: ./doc/common/ch_cli_ceilometer_commands.xml11(title)
+msgid "Telemetry command-line client"
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml39(para)
-msgid ""
-"The end user gets the IP address of the Trove instance by using the "
-"<placeholder-1/> command to get the ID of the instance, and then using the "
-"<placeholder-2/> command to get the IP address."
-msgstr ""
-
-#: ./doc/common/section_getstart_trove.xml44(para)
-msgid ""
-"The end user can now access the Trove instance using typical database access"
-" commands. MySQL example:"
-msgstr ""
-
-#: ./doc/common/section_getstart_trove.xml45(replaceable)
-msgid "trove_ip_address"
-msgstr ""
-
-#: ./doc/common/section_getstart_trove.xml51(title)
-msgid "Components:"
-msgstr ""
-
-#: ./doc/common/section_getstart_trove.xml51(para)
-msgid "The Database service includes the following components:"
-msgstr ""
-
-#: ./doc/common/section_getstart_trove.xml55(para)
-msgid ""
-"<code>python-troveclient</code> command-line client. A CLI that communicates"
-" with the <code>trove-api</code> component."
-msgstr ""
-
-#: ./doc/common/section_getstart_trove.xml58(para)
-msgid ""
-"<code>trove-api</code> component. Provides an OpenStack-native RESTful API "
-"that supports JSON to provision and manage Trove instances."
-msgstr ""
-
-#: ./doc/common/section_getstart_trove.xml62(para)
-msgid ""
-"<code>trove-conductor</code> service. Runs on the host, and receives "
-"messages from guest instances that want to update information on the host."
-msgstr ""
-
-#: ./doc/common/section_getstart_trove.xml65(para)
-msgid ""
-"<code>trove-taskmanager</code> service. Instruments the complex system flows"
-" that support provisioning instances, managing the lifecycle of instances, "
-"and performing operations on instances."
-msgstr ""
-
-#: ./doc/common/section_getstart_trove.xml68(para)
-msgid ""
-"<code>trove-guestagent</code> service. Runs within the guest instance. "
-"Manages and performs operations on the database itself."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml11(title)
-msgid "Object Storage command-line client"
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml12(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml12(para)
 msgid ""
 "The <placeholder-1/> client is the command-line interface (CLI) for the "
-"OpenStack Object Storage API and its extensions. This chapter documents "
-"<placeholder-2/> version 2.1.0."
+"Telemetry API and its extensions. This chapter documents <placeholder-2/> "
+"version 1.0.10."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml22(title)
-msgid "swift usage"
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml41(para)
-#: ./doc/common/ch_cli_swift_commands.xml335(para)
-msgid "Delete a container or objects within a container."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml49(para)
-#: ./doc/common/ch_cli_swift_commands.xml399(para)
-msgid "Download objects from containers."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml57(para)
-#: ./doc/common/ch_cli_swift_commands.xml513(para)
-msgid "Lists the containers for the account or the objects for a container."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml66(para)
-msgid ""
-"Updates meta information for the account, container, or object; creates "
-"containers if not present."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml75(para)
-#: ./doc/common/ch_cli_swift_commands.xml661(para)
-msgid "Displays information for the account, container, or object."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml84(para)
-msgid "Uploads files or directories to the given container."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml92(para)
-msgid "List cluster capabilities."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml100(title)
-msgid "swift examples"
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml110(title)
-msgid "swift optional arguments"
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml131(para)
-msgid "Use SERVICENET internal network."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml139(para)
-msgid "Print more info."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml147(para)
-msgid ""
-"Show the curl commands and results of all http queries regardless of result "
-"status."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml156(para)
-msgid ""
-"Show the curl commands and results of all http queries which return an "
-"error."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml165(para)
-msgid "Suppress status output."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml173(para)
-msgid "for obtaining an auth token."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml181(para)
-msgid "Specify a version for authentication. Defaults to 1.0."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml189(para)
-msgid "User name for obtaining an auth token."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml197(para)
-msgid "Key for obtaining an auth token."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml205(para)
-msgid "The number of times to retry a failed connection."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml213(para)
-msgid "OpenStack username. Defaults to <code>env[OS_USERNAME]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml221(para)
-msgid "OpenStack password. Defaults to <code>env[OS_PASSWORD]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml229(para)
-msgid "OpenStack tenant ID. Defaults to <code>env[OS_TENANT_ID]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml237(para)
-msgid "OpenStack tenant name. Defaults to <code>env[OS_TENANT_NAME]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml246(para)
-msgid "OpenStack auth URL. Defaults to <code>env[OS_AUTH_URL]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml254(para)
-msgid ""
-"OpenStack token. Defaults to <code>env[OS_AUTH_TOKEN]</code>. Used with "
-"--os-storage-url to bypass the usual username/password authentication."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml264(para)
-msgid ""
-"OpenStack storage URL. Defaults to <code>env[OS_STORAGE_URL]</code>. "
-"Overrides the storage url returned during auth. Will bypass authentication "
-"when used with --os-auth-token."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml275(para)
-msgid "OpenStack region name. Defaults to <code>env[OS_REGION_NAME]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml284(para)
-msgid "OpenStack Service type. Defaults to <code>env[OS_SERVICE_TYPE]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml293(para)
-msgid ""
-"OpenStack Endpoint type. Defaults to <code>env[OS_ENDPOINT_TYPE]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml312(para)
-msgid ""
-"Allow swiftclient to access servers without having to verify the SSL "
-"certificate. Defaults to <code>env[SWIFTCLIENT_INSECURE]</code> (set to "
-"'true' to enable)."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml322(para)
-msgid ""
-"This option is deprecated and not used anymore. SSL compression should be "
-"disabled by default by the system SSL library."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml332(title)
-msgid "swift delete command"
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml342(para)
-msgid "Name of container to delete from."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml350(para)
-msgid "Name of object to delete. Specify multiple times for multiple objects."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml362(para)
-msgid "Delete all containers and objects."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml370(para)
-msgid "Do not delete segments of manifest objects."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml378(para)
-msgid "Number of threads to use for deleting objects. Default is 10."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml387(para)
-msgid "Number of threads to use for deleting containers. Default is 10."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml396(title)
-msgid "swift download command"
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml406(para)
-msgid ""
-"Name of container to download from. To download a whole account, omit this "
-"and specify --all."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml415(para)
-msgid ""
-"Name of object to download. Specify multiple times for multiple objects. "
-"Omit this to download all objects from the container."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml428(para)
-msgid "Indicates that you really want to download everything in the account."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml437(para)
-msgid "Marker to use when starting a container or account download."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml446(para)
-msgid "Only download items beginning with &lt;prefix&gt;."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml454(para)
-msgid ""
-"For a single file download, stream the output to &lt;out_file&gt;. "
-"Specifying \"-\" as &lt;out_file&gt; will redirect to stdout."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml464(para)
-msgid "Number of threads to use for downloading objects. Default is 10"
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml473(para)
-msgid "Number of threads to use for downloading containers. Default is 10"
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml482(para)
-msgid "Perform download(s), but don't actually write anything to disk."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml491(para)
-msgid ""
-"Adds a customized request header to the query, like \"Range\" or \"If-"
-"Match\". This argument is repeatable. Example --header \"content-"
-"type:text/plain\""
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml501(para)
-msgid "Skip downloading files that are identical on both sides."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml510(title)
-msgid "swift list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml520(para)
-msgid "Name of container to list object in."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml531(para)
-msgid "Long listing format, similar to ls -l."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml539(para)
-#: ./doc/common/ch_cli_swift_commands.xml688(para)
-msgid "Report sizes in human readable format similar to ls -lh."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml548(para)
-msgid "Used with -l or --lh, only report totals."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml556(para)
-msgid "Only list items beginning with the prefix."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml564(para)
-msgid ""
-"Roll up items with the given delimiter. For containers only. See OpenStack "
-"Swift API documentation for what this means."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml574(title)
-msgid "swift post command"
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml577(para)
-msgid ""
-"Updates meta information for the account, container, or object. If the "
-"container is not found, it will be created automatically."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml585(para)
-msgid "Name of container to post to."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml593(para)
-msgid "Name of object to post. Specify multiple times for multiple objects."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml605(para)
-msgid ""
-"Read ACL for containers. Quick summary of ACL syntax: .r:*, "
-".r:-.example.com, .r:www.example.com, account1, account2:user2"
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml615(para)
-msgid ""
-"Write ACL for containers. Quick summary of ACL syntax: account1 "
-"account2:user2"
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml624(para)
-msgid "Sync To for containers, for multi-cluster replication."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml632(para)
-msgid "Sync Key for containers, for multi-cluster replication."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml640(para)
-msgid ""
-"Sets a meta data item. This option may be repeated. Example: -m Color:Blue "
-"-m Size:Large"
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml649(para)
-msgid ""
-"Set request headers. This option may be repeated. Example -H \"content-"
-"type:text/plain\""
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml658(title)
-msgid "swift stat command"
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml668(para)
-msgid "Name of container to stat from."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml676(para)
-msgid "Name of object to stat. Specify multiple times for multiple objects."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml697(title)
-msgid "swift upload command"
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml700(para)
-msgid "Uploads specified files and directories to the given container."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml707(para)
-msgid "Name of container to upload to."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml715(para)
-msgid ""
-"Name of file or directory to upload. Specify multiple times for multiple "
-"uploads."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml727(para)
-msgid "Only upload files that have changed since the last upload."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml736(para)
-msgid "Skip uploading files that are identical on both sides."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml744(para)
-msgid ""
-"Upload files in segments no larger than &lt;size&gt; (in Bytes) and then "
-"create a \"manifest\" file that will download all the segments as if it were"
-" the original file."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml755(para)
-msgid ""
-"Upload the segments into the specified container. If not specified, the "
-"segments will be uploaded to a &lt;container&gt;_segments container to not "
-"pollute the main &lt;container&gt; listings."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml766(para)
-msgid ""
-"Indicates that you want the older segments of manifest objects left alone "
-"(in the case of overwrites)."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml775(para)
-msgid "Number of threads to use for uploading full objects. Default is 10."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml784(para)
-msgid "Number of threads to use for uploading object segments. Default is 10."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml793(para)
-msgid ""
-"Set request headers with the syntax header:value. This option may be "
-"repeated. Example -H \"content-type:text/plain\"."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml803(para)
-msgid ""
-"When used in conjunction with --segment-size it will create a Static Large "
-"Object instead of the default Dynamic Large Object."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml813(para)
-msgid ""
-"Upload file and name object to &lt;object-name&gt; or upload dir and use &lt"
-";object-name&gt; as object prefix instead of folder name."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml6(title)
-msgid "Manage Networking service quotas"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml7(para)
-msgid ""
-"A quota limits the number of available resources. A default quota might be "
-"enforced for all tenants. When you try to create more resources than the "
-"quota allows, an error occurs:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml12(para)
-msgid ""
-"Per-tenant quota configuration is also supported by the quota extension API."
-" See <link linkend=\"cfg_quotas_per_tenant\"> Per-tenant quota "
-"configuration</link> for details."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml16(title)
-msgid "Basic quota configuration"
-msgstr "Configurations basic des quotas "
-
-#: ./doc/common/section_cli_neutron-quotas.xml17(para)
-msgid ""
-"In the Networking default quota mechanism, all tenants have the same quota "
-"values, such as the number of resources that a tenant can create."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml20(para)
-msgid ""
-"The quota value is defined in the OpenStack Networking "
-"<filename>neutron.conf</filename> configuration file. To disable quotas for "
-"a specific resource, such as network, subnet, or port, remove a "
-"corresponding item from <option>quota_items</option>. This example shows the"
-" default quota values:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml41(para)
-msgid ""
-"OpenStack Networking also supports quotas for L3 resources: router and "
-"floating IP. Add these lines to the <literal>quotas</literal> section in the"
-" <filename>neutron.conf</filename> file."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml52(para)
-#: ./doc/common/section_cli_neutron-quotas.xml67(para)
-msgid "The <option>quota_items</option> option does not affect these quotas."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml55(para)
-msgid ""
-"OpenStack Networking also supports quotas for security group resources: "
-"number of security groups and the number of rules for each security group. "
-"Add these lines to the <literal>quotas</literal> section in the "
-"<filename>neutron.conf</filename> file:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml72(title)
-msgid "Configure per-tenant quotas"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml73(para)
-msgid ""
-"OpenStack Networking also supports per-tenant quota limit by quota extension"
-" API."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml77(para)
-msgid "<placeholder-1/>. Deletes defined quotas for a specified tenant."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml81(para)
-msgid "<placeholder-1/>. Lists defined quotas for all tenants."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml85(para)
-msgid "<placeholder-1/>. Shows quotas for a specified tenant."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml89(para)
-msgid "<placeholder-1/>. Updates quotas for a specified tenant."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml75(para)
-msgid ""
-"Use these commands to manage per-tenant quotas:<placeholder-1/>Only users "
-"with the <literal>admin</literal> role can change a quota value. By default,"
-" the default set of quotas are enforced for all tenants, so no "
-"<placeholder-2/> command exists."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml98(title)
-msgid "Configure Networking to show per-tenant quotas"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml99(para)
-msgid ""
-"Set the <literal>quota_driver</literal> option in the "
-"<literal>neutron.conf</literal> file:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml102(para)
-msgid ""
-"When you set this option, the output for Networking commands shows "
-"<literal>quotas</literal>."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml106(title)
-msgid "List Networking extensions"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml107(para)
-msgid "To list the Networking extensions, run this command:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml110(para)
-msgid ""
-"The command shows the <literal>quotas</literal> extension, which provides "
-"per-tenant quota management support:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml128(title)
-msgid "Show information for the quotas extension"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml129(para)
-msgid ""
-"To show information for the <literal>quotas</literal> extension, run this "
-"command:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml143(para)
-msgid ""
-"Only some plug-ins support per-tenant quotas. Specifically, Open vSwitch, "
-"Linux Bridge, and VMware NSX support them, but new versions of other plug-"
-"ins might bring additional functionality. See the documentation for each "
-"plug-in."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml151(title)
-msgid "List tenants who have per-tenant quota support"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml152(para)
-msgid ""
-"The <placeholder-1/> command lists tenants for which the per-tenant quota is"
-" enabled. The command does not list tenants with default quota support. You "
-"must be an administrative user to run this command:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml165(title)
-msgid "Show per-tenant quota values"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml166(para)
-msgid ""
-"The <placeholder-1/> reports the current set of quota limits for the "
-"specified tenant. Non-administrative users can run this command without the "
-"<parameter>--tenant_id</parameter> parameter. If per-tenant quota limits are"
-" not enabled for the tenant, the command shows the default set of quotas:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml182(para)
-msgid ""
-"The following command shows the command output for a non-administrative "
-"user:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml196(title)
-msgid "Update quota values for a specified tenant"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml197(para)
-msgid ""
-"Use the <placeholder-1/> command to update a quota for a specified tenant:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml209(para)
-msgid "You can update quotas for multiple resources through one command:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml221(para)
-msgid ""
-"To update the limits for an L3 resource such as, router or floating IP, you "
-"must define new values for the quotas after the <parameter>--</parameter> "
-"directive."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml224(para)
-msgid ""
-"This example updates the limit of the number of floating IPs for the "
-"specified tenant:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml236(para)
-msgid ""
-"You can update the limits of multiple resources by including L2 resources "
-"and L3 resource through one command."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml251(title)
-msgid "Delete per-tenant quota values"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml252(para)
-msgid "To clear per-tenant quota limits, use the <placeholder-1/> command:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml256(para)
-msgid ""
-"After you run this command, you can see that quota values for the tenant are"
-" reset to the default values:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_terminate.xml8(title)
-msgid "Delete an instance"
-msgstr "Supprimer une instance "
-
-#: ./doc/common/section_cli_nova_terminate.xml9(para)
-msgid "When you no longer need an instance, you can delete it."
-msgstr "Lorsque vous n'avez plus besoin d'une instance, vous pouvez la supprimer."
-
-#: ./doc/common/section_cli_nova_terminate.xml11(para)
-msgid "List all instances:"
-msgstr "Listez tous les instances:"
-
-#: ./doc/common/section_cli_nova_terminate.xml21(para)
-msgid ""
-"Run the <placeholder-1/> command to delete the instance. The following "
-"example shows deletion of the <filename>newServer</filename> instance, which"
-" is in <literal>ERROR</literal> state:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_terminate.xml24(para)
-msgid "The command does not notify that your server was deleted."
-msgstr "Vous ne recevrez aucune notification indiquant la suppression du server."
-
-#: ./doc/common/section_cli_nova_terminate.xml25(para)
-msgid ""
-"To verify that the server was deleted, run the <placeholder-1/> command:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_terminate.xml33(para)
-msgid "The deleted instance does not appear in the list."
-msgstr "L'instance qui a été supprimée ne s'affiche pas dans la liste."
-
-#: ./doc/common/section_cli_keystone_example_usage.xml6(title)
-msgid "keystone command-line client example usage"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_example_usage.xml7(para)
-msgid ""
-"Before you can use keystone client commands, you must download and source an"
-" OpenStack RC file. For information, see the <citetitle>OpenStack Admin User"
-" Guide</citetitle>."
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_example_usage.xml10(para)
-msgid "The keystone command-line client uses the following syntax:"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_example_usage.xml12(replaceable)
-msgid "PARAMETER"
-msgstr "PARAMETER"
-
-#: ./doc/common/section_cli_keystone_example_usage.xml12(replaceable)
-msgid "ARGUMENT"
-msgstr "ARGUMENT"
-
-#: ./doc/common/section_cli_keystone_example_usage.xml13(para)
-msgid ""
-"For example, you can run the <placeholder-1/> and <placeholder-2/> commands,"
-" as follows:"
-msgstr "Par exemple, vous pouvez exécuter les commandes <placeholder-1/> et <placeholder-2/>, comme suit:"
-
-#: ./doc/common/section_cli_keystone_example_usage.xml22(replaceable)
-#: ./doc/common/section_cli_keystone_example_usage.xml23(replaceable)
-msgid "token"
-msgstr "jeton"
-
-#: ./doc/common/section_cli_keystone_example_usage.xml22(replaceable)
-#: ./doc/common/section_cli_keystone_example_usage.xml23(replaceable)
-msgid "endpoint"
-msgstr "Point de terminaison"
-
-#: ./doc/common/section_cli_keystone_example_usage.xml31(replaceable)
-msgid "id"
-msgstr "id"
-
-#: ./doc/common/section_cli_keystone_example_usage.xml34(para)
-msgid ""
-"For information about using the keystone client commands to create and "
-"manage users, roles, and projects, see the <citetitle>OpenStack Admin User "
-"Guide</citetitle>."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_volumes.xml8(title)
-msgid "Manage Volumes"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_volumes.xml9(para)
-msgid ""
-"Depending on the setup of your cloud provider, they may give you an endpoint"
-" to use to manage volumes, or there may be an extension under the covers. In"
-" either case, you can use the <placeholder-1/> CLI to manage volumes:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_volumes.xml26(para)
-msgid "For example, to list IDs and names of Compute volumes, run:"
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml5(title)
-msgid "OpenStack Object Storage"
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml6(para)
-msgid ""
-"The OpenStack Object Storage is a multi-tenant object storage system. It is "
-"highly scalable and can manage large amounts of unstructured data at low "
-"cost through a RESTful HTTP API."
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml11(term)
-msgid ""
-"Proxy servers (<systemitem class=\"service\">swift-proxy-"
-"server</systemitem>)"
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml13(para)
-msgid ""
-"Accepts OpenStack Object Storage API and raw HTTP requests to upload files, "
-"modify metadata, and create containers. It also serves file or container "
-"listings to web browsers. To improve performance, the proxy server can use "
-"an optional cache usually deployed with memcache."
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml20(term)
-msgid ""
-"Account servers (<systemitem class=\"service\">swift-account-"
-"server</systemitem>)"
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml22(para)
-msgid "Manages accounts defined with Object Storage."
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml26(term)
-msgid ""
-"Container servers (<systemitem class=\"service\">swift-container-"
-"server</systemitem>)"
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml28(para)
-msgid "Manages the mapping of containers or folders, within Object Storage."
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml32(term)
-msgid ""
-"Object servers (<systemitem class=\"service\">swift-object-"
-"server</systemitem>)"
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml34(para)
-msgid "Manages actual objects,such as files, on the storage nodes."
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml38(term)
-msgid "Various periodic processes"
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml39(para)
-msgid ""
-"Performs housekeeping tasks on the large data store. The replication "
-"services ensure consistency and availability through the cluster. Other "
-"periodic processes include auditors, updaters, and reapers."
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml45(term)
-msgid "WSGI middleware"
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml46(para)
-msgid "Handles authentication and is usually OpenStack Identity."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml6(title)
-msgid "Secure the OpenStack Identity service connection to an LDAP back end"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml8(para)
-msgid ""
-"The Identity service supports the use of TLS to encrypt LDAP traffic. Before"
-" configuring this, you must first verify where your certificate authority "
-"file is located. For more information, see <xref linkend=\"certificates-for-"
-"pki\"/>."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml12(para)
-msgid "Once you verify the location of your certificate authority file:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml15(title)
-msgid "Configuring TLS encryption on LDAP traffic"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml17(para)
-msgid ""
-"Open the <filename>/etc/keystone/keystone.conf</filename> configuration "
-"file."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml23(para)
-msgid "Find the <literal>[ldap]</literal> section."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml26(para)
-msgid ""
-"In the <literal>[ldap]</literal> section, set the <literal>use_tls</literal>"
-" configuration key to <literal>True</literal>. Doing so will enable TLS."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml31(para)
-msgid ""
-"Configure the Identity service to use your certificate authorities file. To "
-"do so, set the <literal>tls_cacertfile</literal> configuration key in the "
-"<literal>ldap</literal> section to the certificate authorities file's path."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml37(para)
-msgid ""
-"You can also set the <literal>tls_cacertdir</literal> (also in the "
-"<literal>ldap</literal> section) to the directory where all certificate "
-"authorities files are kept. If both <literal>tls_cacertfile</literal> and "
-"<literal>tls_cacertdir</literal> are set, then the latter will be ignored."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml46(para)
-msgid ""
-"Specify what client certificate checks to perform on incoming TLS sessions "
-"from the LDAP server. To do so, set the <literal>tls_req_cert</literal> "
-"configuration key in the <literal>[ldap]</literal> section to "
-"<literal>demand</literal>, <literal>allow</literal>, or "
-"<literal>never</literal>:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml53(para)
-msgid ""
-"<parameter>demand</parameter>: a certificate will always be requested from "
-"the LDAP server. The session will be terminated if no certificate is "
-"provided, or if the certificate provided cannot be verified against the "
-"existing certificate authorities file."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml60(para)
-msgid ""
-"<parameter>allow</parameter>: a certificate will always be requested from "
-"the LDAP server. The session will proceed as normal even if a certificate is"
-" not provided. If a certificate is provided but it cannot be verified "
-"against the existing certificate authorities file, the certificate will be "
-"ignored and the session will proceed as normal."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml67(para)
-msgid "<parameter>never</parameter>: a certificate will never be requested."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml72(para)
-msgid ""
-"On distributions that include <application>openstack-config</application>, "
-"you can configure TLS encryption on LDAP traffic by running the following "
-"commands instead:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml80(replaceable)
-msgid "CA_FILE"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml82(replaceable)
-msgid "CERT_BEHAVIOR"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml83(para)
-#: ./doc/common/section_cli_nova_customize_flavors.xml260(para)
-#: ./doc/common/section_trusted-compute-pools.xml78(para)
-msgid "Where:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml85(para)
-msgid ""
-"<replaceable>CA_FILE</replaceable> is the absolute path to the certificate "
-"authorities file that should be used to encrypt LDAP traffic."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml88(para)
-msgid ""
-"<replaceable>CERT_BEHAVIOR</replaceable>: specifies what client certificate "
-"checks to perform on an incoming TLS session from the LDAP server "
-"(<literal>demand</literal>, <literal>allow</literal>, or "
-"<literal>never</literal>)."
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml7(title)
-#: ./doc/common/section_rpc.xml7(title)
-msgid "Configure the Oslo RPC messaging system"
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml9(para)
-msgid ""
-"OpenStack projects use an open standard for messaging middleware known as "
-"AMQP. This messaging middleware enables the OpenStack services that run on "
-"multiple servers to talk to each other. OpenStack Oslo RPC supports three "
-"implementations of AMQP: <application>RabbitMQ</application>, "
-"<application>Qpid</application>, and <application>ZeroMQ</application>."
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml18(title)
-#: ./doc/common/section_rpc.xml15(title)
-msgid "Configure RabbitMQ"
-msgstr "Configuration pour RabbitMQ"
-
-#: ./doc/common/section_rpc-for-networking.xml20(para)
-msgid ""
-"OpenStack Oslo RPC uses <application>RabbitMQ</application> by default. Use "
-"these options to configure the <application>RabbitMQ</application> message "
-"system. The <option>rpc_backend</option> option is optional as long as "
-"<application>RabbitMQ</application> is the default messaging system. "
-"However, if it is included the configuration, you must set it to "
-"<literal>neutron.openstack.common.rpc.impl_kombu</literal>."
-msgstr "OpenStack Oslo RPC utilise <application>RabbitMQ</application> par défaut. Cette section traite des options de configuration qui sont pertinentes quand <application>RabbitMQ</application> est utilisé. L’option <option>rpc_backend</option> n’est pas nécessaire du moment que <application>RabbitMQ</application> est le système de messagerie par défaut. Toutefois, s’il est inclus, la configuration sur laquelle il doit être défini est <literal>neutron.openstack.common.rpc.impl_kombu</literal>."
-
-#: ./doc/common/section_rpc-for-networking.xml34(para)
-msgid ""
-"Use these options to configure the <application>RabbitMQ</application> "
-"messaging system. You can configure messaging communication for different "
-"installation scenarios, tune retries for RabbitMQ, and define the size of "
-"the RPC thread pool. To monitor notifications through RabbitMQ, you must set"
-" the <option>notification_driver</option> option to "
-"<literal>neutron.notifier.rabbit_notifier</literal> in the "
-"<filename>neutron.conf</filename> file:"
-msgstr "Les tableaux suivants décrivent le reste des options qui peuvent être utilisées quand <application>RabbitMQ</application> est utilisé en tant que système de messagerie. Vous pouvez configurer la communication pas messages pour différents scénarios d’installation et également régler le nombre de nouvelles tentatives de RabbitMQ et la taille du pool de thread RPC. Si vous souhaitez surveiller les notifications par RabbitMQ, vous devez définir l’option <option>notification_driver</option> dans <filename>neutron.conf</filename> à <literal>neutron.notifier.rabbit_notifier</literal>. "
-
-#: ./doc/common/section_rpc-for-networking.xml46(title)
-#: ./doc/common/section_rpc.xml39(title)
-msgid "Configure Qpid"
-msgstr "Configuration pour Qpid"
-
-#: ./doc/common/section_rpc-for-networking.xml47(para)
-msgid ""
-"Use these options to configure the <application>Qpid</application> messaging"
-" system for OpenStack Oslo RPC. <application>Qpid</application> is not the "
-"default messaging system, so you must enable it by setting the "
-"<option>rpc_backend</option> option in the <filename>neutron.conf</filename>"
-" file:"
-msgstr "Cette section traite des options de configuration pertinentes si <application>Qpid</application> est utilisé en tant que système de messagerie pour OpenStack Oslo RPC. <application>Qpid</application> n’est pas le système de messagerie par défaut, il doit donc être activé en définissant l’option <option>rpc_backend</option> dans <filename>neutron.conf</filename>."
-
-#: ./doc/common/section_rpc-for-networking.xml56(para)
-msgid ""
-"This critical option points the compute nodes to the "
-"<application>Qpid</application> broker (server). Set the "
-"<option>qpid_hostname</option> option to the host name where the broker runs"
-" in the <filename>neutron.conf</filename> file."
-msgstr "L’option critique qui suit fait pointer les nœuds Compute vers l’intermédiaire (serveur) <application>Qpid</application>. Définissez <option>qpid_hostname</option> dans <filename>neutron.conf</filename> comme nom d’hôte là où l’intermédiaire tourne."
-
-#: ./doc/common/section_rpc-for-networking.xml62(para)
-#: ./doc/common/section_rpc.xml52(para)
-msgid ""
-"The <option>--qpid_hostname</option> option accepts a host name or IP "
-"address value."
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml69(para)
-#: ./doc/common/section_rpc.xml56(para)
-msgid ""
-"If the <application>Qpid</application> broker listens on a port other than "
-"the AMQP default of <literal>5672</literal>, you must set the "
-"<option>qpid_port</option> option to that value:"
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml78(para)
-#: ./doc/common/section_rpc.xml61(para)
-msgid ""
-"If you configure the <application>Qpid</application> broker to require "
-"authentication, you must add a user name and password to the configuration:"
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml87(para)
-#: ./doc/common/section_rpc.xml66(para)
-msgid ""
-"By default, TCP is used as the transport. To enable SSL, set the "
-"<option>qpid_protocol</option> option:"
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml94(para)
-msgid ""
-"Use these additional options to configure the Qpid messaging driver for "
-"OpenStack Oslo RPC. These options are used infrequently."
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml102(title)
-#: ./doc/common/section_rpc.xml75(title)
-msgid "Configure ZeroMQ"
-msgstr "Configurez ZeroMQ"
-
-#: ./doc/common/section_rpc-for-networking.xml103(para)
-msgid ""
-"Use these options to configure the <application>ZeroMQ</application> "
-"messaging system for OpenStack Oslo RPC. <application>ZeroMQ</application> "
-"is not the default messaging system, so you must enable it by setting the "
-"<option>rpc_backend</option> option in the <filename>neutron.conf</filename>"
-" file:"
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml112(title)
-#: ./doc/common/section_rpc.xml85(title)
-msgid "Configure messaging"
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml114(para)
-msgid ""
-"Use these common options to configure the "
-"<application>RabbitMQ</application>, <application>Qpid</application>, and "
-"<application>ZeroMq</application> messaging drivers:"
-msgstr ""
-
-#: ./doc/common/section_fibrechannel.xml5(title)
-msgid "Fibre Channel support in Compute"
-msgstr "Support de Fibre Channel en Calcul"
-
-#: ./doc/common/section_fibrechannel.xml6(para)
-msgid ""
-"Fibre Channel support in OpenStack Compute is remote block storage attached "
-"to compute nodes for VMs."
-msgstr ""
-
-#. TODO: This below statement needs to be verified for current release
-#: ./doc/common/section_fibrechannel.xml9(para)
-msgid ""
-"In the Grizzly release, Fibre Channel supported only the KVM hypervisor."
-msgstr "Fibre Channel supporte l'hyperviseur KVM uniquement dans l'édition grizzly."
-
-#: ./doc/common/section_fibrechannel.xml11(para)
-msgid ""
-"Compute and Block Storage for Fibre Channel do not support automatic zoning."
-" Fibre Channel arrays must be pre-zoned or directly attached to the KVM "
-"hosts."
-msgstr "Il n'y a pas de support de zonage automatique dans Nova ou Cinder pour Fibre Channel. Les matrices Fibre Channel doivent être pré-zonées ou directement rattachées aux hôtes KVM. "
-
-#: ./doc/common/section_fibrechannel.xml15(title)
-msgid "KVM host requirements"
-msgstr "Il n'y a pas de support de zonage automatique dans Nova ou Cinder pour Fibre Channel. Les matrices Fibre Channel doivent être pré-zonées ou directement rattachées aux hôtes KVM. "
-
-#: ./doc/common/section_fibrechannel.xml16(para)
-msgid "You must install these packages on the KVM host:"
-msgstr "L'hôte KVM doit contenir les packs suivants: "
-
-#: ./doc/common/section_fibrechannel.xml19(para)
-msgid ""
-"<package>sysfsutils</package> - Nova uses the <package>systool</package> "
-"application in this package."
-msgstr ""
-
-#: ./doc/common/section_fibrechannel.xml25(para)
-msgid ""
-"<package>sg3-utils</package> - Nova uses the <package>sg_scan</package> and "
-"<package>sginfo</package> applications."
-msgstr "<package>sg3-utils</package>  – Utilise les applications <package>sg_scan</package>. "
-
-#: ./doc/common/section_fibrechannel.xml31(para)
-msgid "Installing the <package>multipath-tools</package> package is optional."
-msgstr "L'installation du pack <package>sginfo</package> est optionnel."
-
-#: ./doc/common/section_fibrechannel.xml35(title)
-msgid "Install required packages"
-msgstr "Installations des Packs Nécessaires"
-
-#: ./doc/common/section_fibrechannel.xml36(para)
-msgid "Use these commands to install the system packages:"
-msgstr "Utilisez les commandes suivantes pour installer les packs système. "
-
-#: ./doc/common/section_fibrechannel.xml40(para)
-msgid "For systems running openSUSE or SUSE Linux Enterprise Server:"
-msgstr ""
-
-#: ./doc/common/section_fibrechannel.xml45(para)
-msgid "For systems running Red Hat:"
-msgstr "Pour les systèmes fonctionnant sous Red Hat:"
-
-#: ./doc/common/section_fibrechannel.xml49(para)
-msgid "For systems running Ubuntu:"
-msgstr "Pour les systèmes fonctionnants sous Ubuntu:"
-
-#: ./doc/common/section_cli_help.xml6(title)
-msgid "Get help for client commands"
-msgstr ""
-
-#: ./doc/common/section_cli_help.xml7(para)
-msgid ""
-"To get usage information, including a list of commands with descriptions, "
-"for a client, run the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_help.xml9(replaceable)
-#: ./doc/common/section_cli_help.xml59(replaceable)
-msgid "CLIENT_NAME"
-msgstr "CLIENT_NAME"
-
-#: ./doc/common/section_cli_help.xml10(para)
-msgid ""
-"For example, to get help information for the swift client, run the following"
-" command:"
-msgstr ""
-
-#: ./doc/common/section_cli_help.xml54(para)
-msgid ""
-"Depending on your credentials, you might not have permission to use every "
-"command."
-msgstr ""
-
-#: ./doc/common/section_cli_help.xml57(para)
-msgid ""
-"After the <option>help</option> command, you can enter a command name to get"
-" help for that command, as follows:"
-msgstr ""
-
-#: ./doc/common/section_cli_help.xml59(replaceable)
-msgid "COMMAND_NAME"
-msgstr "COMMAND_NAME"
-
-#: ./doc/common/section_cli_help.xml60(para)
-msgid ""
-"For example, to get help for the glance <placeholder-1/> command, enter the "
-"following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_help.xml64(para)
-msgid ""
-"The command returns a description of the command and its positional and "
-"optional arguments:"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml6(title)
-msgid "Get started with OpenStack"
-msgstr "Débuter avec OpenStack "
-
-#: ./doc/common/ch_getstart.xml7(para)
-msgid ""
-"The OpenStack project is an open source cloud computing platform for all "
-"types of clouds, which aims to be simple to implement, massively scalable, "
-"and feature rich. Developers and cloud computing technologists from around "
-"the world create the OpenStack project."
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml12(para)
-msgid ""
-"OpenStack provides an Infrastructure-as-a-Service "
-"(<glossterm>IaaS</glossterm>) solution through a set of interrelated "
-"services. Each service offers an application programming interface "
-"(<glossterm>API</glossterm>) that facilitates this integration. Depending on"
-" your needs, you can install some or all services."
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml20(para)
-msgid ""
-"The following table describes the OpenStack services that make up the "
-"OpenStack architecture:"
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml23(caption)
-#: ./doc/common/ch_getstart.xml188(title)
-msgid "OpenStack services"
-msgstr "Les services d'OpenStack"
-
-#: ./doc/common/ch_getstart.xml29(th)
-#: ./doc/common/section_keystone-concepts.xml83(term)
-#: ./doc/common/section_cli_overview.xml33(th)
-msgid "Service"
-msgstr "Service"
-
-#: ./doc/common/ch_getstart.xml30(th)
-msgid "Project name"
-msgstr "Nom du projet"
-
-#: ./doc/common/ch_getstart.xml38(glossterm)
-msgid "Dashboard"
-msgstr "Tableau de Bord"
-
-#: ./doc/common/ch_getstart.xml42(glossterm)
-msgid "Horizon"
-msgstr "Horizon"
-
-#: ./doc/common/ch_getstart.xml44(td)
-msgid ""
-"Provides a web-based self-service portal to interact with underlying "
-"OpenStack services, such as launching an instance, assigning IP addresses "
-"and configuring access controls."
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml52(glossterm)
-#: ./doc/common/section_dashboard_access.xml100(guilabel)
-#: ./doc/common/section_cli_overview.xml47(td)
-msgid "Compute"
-msgstr "Compute"
-
-#: ./doc/common/ch_getstart.xml56(glossterm)
-msgid "Nova"
-msgstr "Nova"
+#: ./doc/common/ch_cli_ceilometer_commands.xml22(title)
+msgid "ceilometer usage"
+msgstr "utilisation de ceilometer"
 
-#: ./doc/common/ch_getstart.xml58(td)
-msgid ""
-"Manages the lifecycle of compute instances in an OpenStack environment. "
-"Responsibilities include spawning, scheduling and decommissioning of virtual"
-" machines on demand."
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml66(glossterm)
-#: ./doc/common/section_cli_overview.xml71(td)
-msgid "Networking"
-msgstr "Réseaux"
-
-#: ./doc/common/ch_getstart.xml70(glossterm)
-msgid "Neutron"
-msgstr "Neutron"
-
-#: ./doc/common/ch_getstart.xml72(td)
-msgid ""
-"Enables network connectivity as a service for other OpenStack services, such"
-" as OpenStack Compute. Provides an API for users to define networks and the "
-"attachments into them. Has a pluggable architecture that supports many "
-"popular networking vendors and technologies."
-msgstr ""
-
-#: ./doc/common/ch_getstart.xml79(th)
-msgid "Storage"
-msgstr "Stockage"
-
-#: ./doc/common/ch_getstart.xml83(glossterm)
-#: ./doc/common/section_cli_overview.xml78(td)
-msgid "Object Storage"
-msgstr "Object Storage"
-
-#: ./doc/common/ch_getstart.xml87(glossterm)
-msgid "Swift"
-msgstr "Swift"
-
-#: ./doc/common/ch_getstart.xml90(glossterm)
-msgid "RESTful"
-msgstr "RESTful"
-
-#: ./doc/common/ch_getstart.xml89(td)
-msgid ""
-"Stores and retrieves arbitrary unstructured data objects via a "
-"<placeholder-1/>, HTTP based API. It is highly fault tolerant with its data "
-"replication and scale out architecture. Its implementation is not like a "
-"file server with mountable directories."
+#: ./doc/common/ch_cli_ceilometer_commands.xml42(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml459(para)
+msgid "Create a new alarm based on state of other alarms."
 msgstr ""
 
-#: ./doc/common/ch_getstart.xml99(glossterm)
-#: ./doc/common/section_cli_overview.xml41(td)
-msgid "Block Storage"
+#: ./doc/common/ch_cli_ceilometer_commands.xml50(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml601(para)
+msgid "Update an existing alarm based on state of other alarms."
 msgstr ""
 
-#: ./doc/common/ch_getstart.xml103(glossterm)
-msgid "Cinder"
-msgstr "Cinder"
-
-#: ./doc/common/ch_getstart.xml105(td)
-msgid ""
-"Provides persistent block storage to running instances. Its pluggable driver"
-" architecture facilitates the creation and management of block storage "
-"devices."
+#: ./doc/common/ch_cli_ceilometer_commands.xml59(para)
+msgid "Create a new alarm (Deprecated). Use alarm-threshold- create instead."
 msgstr ""
 
-#: ./doc/common/ch_getstart.xml110(th)
-msgid "Shared services"
-msgstr "Les Services partagés"
+#: ./doc/common/ch_cli_ceilometer_commands.xml68(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml746(para)
+msgid "Delete an alarm."
+msgstr "Supprimer une alarme."
 
-#: ./doc/common/ch_getstart.xml114(glossterm)
-msgid "Identity service"
+#: ./doc/common/ch_cli_ceilometer_commands.xml76(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml763(para)
+msgid "Display the change history of an alarm."
 msgstr ""
 
-#: ./doc/common/ch_getstart.xml118(glossterm)
-msgid "Keystone"
-msgstr "Keystone"
-
-#: ./doc/common/ch_getstart.xml120(td)
-msgid ""
-"Provides an authentication and authorization service for other OpenStack "
-"services. Provides a catalog of endpoints for all OpenStack services."
+#: ./doc/common/ch_cli_ceilometer_commands.xml84(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml790(para)
+msgid "List the user's alarms."
 msgstr ""
 
-#: ./doc/common/ch_getstart.xml127(glossterm)
-#: ./doc/common/section_cli_overview.xml65(td)
-msgid "Image Service"
-msgstr "le Service d'Image"
-
-#: ./doc/common/ch_getstart.xml131(glossterm)
-msgid "Glance"
-msgstr "Glance"
-
-#: ./doc/common/ch_getstart.xml133(td)
-msgid ""
-"Stores and retrieves virtual machine disk images. OpenStack Compute makes "
-"use of this during instance provisioning."
+#: ./doc/common/ch_cli_ceilometer_commands.xml92(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml809(para)
+msgid "Show an alarm."
 msgstr ""
 
-#: ./doc/common/ch_getstart.xml142(glossterm)
-#: ./doc/common/section_cli_overview.xml93(td)
-msgid "Telemetry"
-msgstr "Métrologie"
-
-#: ./doc/common/ch_getstart.xml146(glossterm)
-msgid "Ceilometer"
-msgstr "Ceilometer"
-
-#: ./doc/common/ch_getstart.xml148(td)
-msgid ""
-"Monitors and meters the OpenStack cloud for billing, benchmarking, "
-"scalability, and statistical purposes."
+#: ./doc/common/ch_cli_ceilometer_commands.xml100(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml826(para)
+msgid "Get the state of an alarm."
 msgstr ""
 
-#: ./doc/common/ch_getstart.xml153(th)
-msgid "Higher-level services"
+#: ./doc/common/ch_cli_ceilometer_commands.xml108(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml843(para)
+msgid "Set the state of an alarm."
 msgstr ""
 
-#: ./doc/common/ch_getstart.xml157(glossterm)
-#: ./doc/common/section_dashboard_access.xml192(guilabel)
-#: ./doc/common/section_cli_overview.xml86(td)
-msgid "Orchestration"
-msgstr "Orchestration"
-
-#: ./doc/common/ch_getstart.xml160(glossterm)
-msgid "Heat"
-msgstr "Heat"
-
-#: ./doc/common/ch_getstart.xml164(glossterm)
-msgid "HOT"
+#: ./doc/common/ch_cli_ceilometer_commands.xml116(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml884(para)
+msgid "Create a new alarm based on computed statistics."
 msgstr ""
 
-#: ./doc/common/ch_getstart.xml162(td)
-msgid ""
-"Orchestrates multiple composite cloud applications by using either the "
-"native <placeholder-1/> template format or the AWS CloudFormation template "
-"format, through both an OpenStack-native REST API and a CloudFormation-"
-"compatible Query API."
+#: ./doc/common/ch_cli_ceilometer_commands.xml124(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1074(para)
+msgid "Update an existing alarm based on computed statistics."
 msgstr ""
 
-#: ./doc/common/ch_getstart.xml172(glossterm)
-#: ./doc/common/section_cli_overview.xml53(td)
-msgid "Database Service"
-msgstr "Base de données"
-
-#: ./doc/common/ch_getstart.xml176(glossterm)
-msgid "Trove"
+#: ./doc/common/ch_cli_ceilometer_commands.xml132(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1279(para)
+msgid "Update an existing alarm (Deprecated)."
 msgstr ""
 
-#: ./doc/common/ch_getstart.xml178(td)
-msgid ""
-"Provides scalable and reliable Cloud Database-as-a-Service functionality for"
-" both relational and non-relational database engines."
+#: ./doc/common/ch_cli_ceilometer_commands.xml140(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1468(para)
+msgid "List events."
 msgstr ""
 
-#: ./doc/common/ch_getstart.xml189(para)
-msgid "This section describes OpenStack services in detail."
+#: ./doc/common/ch_cli_ceilometer_commands.xml148(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1487(para)
+msgid "Show a particular event."
 msgstr ""
 
-#: ./doc/common/ch_getstart.xml207(title)
-msgid "Feedback"
-msgstr "remarques"
-
-#: ./doc/common/section_getstart_compute.xml5(title)
-msgid "OpenStack Compute"
-msgstr "OpenStack Compute"
-
-#: ./doc/common/section_getstart_compute.xml6(para)
-msgid ""
-"OpenStack Compute is used to host and manage cloud computing systems and is "
-"a major part of an infrastructure-as-a-service (IaaS) system. The main "
-"modules are implemented in Python."
+#: ./doc/common/ch_cli_ceilometer_commands.xml156(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1504(para)
+msgid "List event types."
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml9(para)
-msgid ""
-"OpenStack Compute interacts with OpenStack Identity for authentication, "
-"OpenStack Image Service for images, and OpenStack dashboard for the user and"
-" administrative interface. Access to images is limited by project and by "
-"user; quotas are limited per project (for example, the number of instances)."
-" OpenStack Compute can scale horizontally on standard hardware, and download"
-" images to launch instances."
+#: ./doc/common/ch_cli_ceilometer_commands.xml164(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1511(para)
+msgid "List the user's meters."
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml15(para)
-msgid ""
-"OpenStack Compute consists of the following areas and their components:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml172(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1531(para)
+msgid "Query Alarm History."
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml17(title)
-msgid "API"
-msgstr "API"
-
-#: ./doc/common/section_getstart_compute.xml19(systemitem)
-msgid "nova-api service"
+#: ./doc/common/ch_cli_ceilometer_commands.xml180(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1567(para)
+msgid "Query Alarms."
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml20(para)
-msgid ""
-"Accepts and responds to end user compute API calls. Supports the OpenStack "
-"Compute API, the Amazon EC2 API, and a special Admin API for privileged "
-"users to perform administrative actions. It enforces some policies and "
-"initiates most orchestration activities, such as running an instance."
+#: ./doc/common/ch_cli_ceilometer_commands.xml188(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1603(para)
+msgid "Query samples."
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml28(term)
-msgid "<systemitem class=\"service\">nova-api-metadata</systemitem> service"
+#: ./doc/common/ch_cli_ceilometer_commands.xml196(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1639(para)
+msgid "List the resources."
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml30(para)
-msgid ""
-"Accepts metadata requests from instances. The <systemitem class=\"service"
-"\">nova-api-metadata</systemitem> service is generally used when you run in "
-"multi-host mode with <systemitem class=\"service\">nova-network</systemitem>"
-" installations. For details, see <link href=\"http://docs.openstack.org"
-"/admin-guide-cloud/content/section_metadata-service.html\">Metadata "
-"service</link> in the <citetitle>Cloud Administrator Guide</citetitle>."
+#: ./doc/common/ch_cli_ceilometer_commands.xml204(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1658(para)
+msgid "Show the resource."
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml38(para)
-msgid ""
-"On Debian systems, it is included in the <systemitem class=\"service\">nova-"
-"api</systemitem> package, and can be selected through "
-"<package>debconf</package>."
+#: ./doc/common/ch_cli_ceilometer_commands.xml212(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1681(para)
+msgid "Create a sample."
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml44(title)
-msgid "Compute core"
+#: ./doc/common/ch_cli_ceilometer_commands.xml220(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1764(para)
+msgid "List the samples for a meter."
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml46(term)
-msgid "<systemitem class=\"service\">nova-compute</systemitem> process"
+#: ./doc/common/ch_cli_ceilometer_commands.xml228(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1800(para)
+msgid "List the statistics for a meter."
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml47(para)
-msgid ""
-"A worker daemon that creates and terminates virtual machine instances "
-"through hypervisor APIs. For example, XenAPI for XenServer/XCP, libvirt for "
-"KVM or QEMU and VMwareAPI for VMware. Processing is fairly complex but "
-"fundamentally it accepts actions from the queue and performs a series of "
-"system commands, like launching a KVM instance, whilst updating its state in"
-" the database."
+#: ./doc/common/ch_cli_ceilometer_commands.xml236(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1853(para)
+msgid "List trait info for an event type."
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml56(term)
-msgid "<systemitem class=\"service\">nova-scheduler</systemitem> process"
+#: ./doc/common/ch_cli_ceilometer_commands.xml244(para)
+msgid "List trait all traits with name &lt;trait_name&gt; for Event Type"
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml58(para)
-msgid ""
-"Conceptually the simplest piece of code in OpenStack Compute. It takes a "
-"virtual machine instance request from the queue and determines on which "
-"compute server host it will run."
+#: ./doc/common/ch_cli_ceilometer_commands.xml270(title)
+msgid "ceilometer optional arguments"
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml64(term)
-msgid "<systemitem class=\"service\">nova-conductor</systemitem> module"
+#: ./doc/common/ch_cli_ceilometer_commands.xml283(para)
+msgid "Defaults to <code>env[CEILOMETERCLIENT_DEBUG]</code>."
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml65(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml299(para)
 msgid ""
-"Mediates interactions between <systemitem class=\"service\">nova-"
-"compute</systemitem> and the database. It eliminates direct accesses to the "
-"cloud database made by <systemitem class=\"service\">nova-"
-"compute</systemitem>. The <systemitem class=\"service\">nova-"
-"conductor</systemitem> module scales horizontally. However, do not deploy it"
-" on any nodes where <systemitem class=\"service\">nova-compute</systemitem> "
-"runs. For more information, see <link "
-"href=\"http://russellbryantnet.wordpress.com/2012/11/19/a-new-nova-service-"
-"nova-conductor/\">A new Nova service: nova-conductor</link>."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml79(title)
-msgid "Networking for VMs"
-msgstr "Réseaux pour les machines virtuelles"
-
-#: ./doc/common/section_getstart_compute.xml80(term)
-msgid "<systemitem class=\"service\">nova-network</systemitem> worker daemon"
+"Explicitly allow ceilometerclient to perform \"insecure\" SSL (https) "
+"requests. The server's certificate will not be verified against any "
+"certificate authorities. This option should be used with caution."
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml82(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml331(para)
 msgid ""
-"Similar to <systemitem class=\"service\">nova-compute</systemitem>, it "
-"accepts networking tasks from the queue and performs tasks to manipulate the"
-" network, such as setting up bridging interfaces or changing iptables rules."
-" This functionality is being migrated to OpenStack Networking."
+"Path of CA TLS certificate(s) used to verifythe remote server's certificate."
+" Without this option ceilometer looks for the default system CA "
+"certificates."
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml90(term)
-msgid "<systemitem class=\"service\">nova-dhcpbridge</systemitem> script"
+#: ./doc/common/ch_cli_ceilometer_commands.xml349(para)
+msgid "Number of seconds to wait for a response."
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml92(para)
-msgid ""
-"The IP address leases and is recorded in the database using the dnsmasq "
-"<literal>dhcp-script</literal> facility. This functionality is being "
-"migrated to OpenStack Networkin which provides a different script."
+#: ./doc/common/ch_cli_ceilometer_commands.xml413(para)
+msgid "Defaults to <code>env[CEILOMETER_URL]</code>."
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml99(title)
-msgid "Console interface"
-msgstr "Interface Console"
-
-#: ./doc/common/section_getstart_compute.xml101(term)
-msgid "<systemitem class=\"service\">nova-consoleauth</systemitem> daemon"
+#: ./doc/common/ch_cli_ceilometer_commands.xml421(para)
+msgid "Defaults to <code>env[CEILOMETER_API_VERSION]</code> or 2."
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml102(para)
-msgid ""
-"Authorizes tokens for users that console proxies provide. See <systemitem "
-"class=\"service\">nova-novncproxy</systemitem> and <systemitem "
-"class=\"service\">nova-xvpnvcproxy</systemitem>. This service must be "
-"running for console proxies to work. Many proxies of either type can be run "
-"against a single <systemitem class=\"service\">nova-consoleauth</systemitem>"
-" service in a cluster configuration. For information, see <link "
-"href=\"http://docs.openstack.org/trunk/config-reference/content/about-nova-"
-"consoleauth.html\">About nova-consoleauth</link>."
+#: ./doc/common/ch_cli_ceilometer_commands.xml445(title)
+msgid "ceilometer alarm-combination-create command"
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml114(term)
-msgid "<systemitem class=\"service\">nova-novncproxy</systemitem> daemon"
+#: ./doc/common/ch_cli_ceilometer_commands.xml466(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml891(para)
+msgid "Name of the alarm (must be unique per tenant). Required."
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml116(para)
-msgid ""
-"Provides a proxy for accessing running instances through a VNC connection. "
-"Supports browser-based novnc clients."
+#: ./doc/common/ch_cli_ceilometer_commands.xml475(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml624(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml900(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1097(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1302(para)
+msgid "Tenant to associate with alarm (only settable by admin users)."
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml121(term)
-msgid "<systemitem class=\"service\">nova-xvpnvncproxy</systemitem> daemon"
+#: ./doc/common/ch_cli_ceilometer_commands.xml484(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml633(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml909(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1106(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1311(para)
+msgid "User to associate with alarm (only settable by admin users)."
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml123(para)
-msgid ""
-"A proxy for accessing running instances through a VNC connection. It "
-"supports a Java client specifically designed for OpenStack."
+#: ./doc/common/ch_cli_ceilometer_commands.xml493(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml642(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml918(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1115(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1320(para)
+msgid "Free text description of the alarm."
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml128(term)
-msgid "<systemitem class=\"service\">nova-cert</systemitem> daemon"
+#: ./doc/common/ch_cli_ceilometer_commands.xml501(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml650(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml926(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1123(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1328(para)
+msgid "State of the alarm, one of: ['ok', 'alarm', 'insufficient_data']"
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml129(para)
-msgid "x509 certificates."
+#: ./doc/common/ch_cli_ceilometer_commands.xml510(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml659(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml935(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1132(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1337(para)
+msgid "True if alarm evaluation/actioning is enabled."
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml132(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml518(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml667(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml943(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1140(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1345(para)
 msgid ""
-"In Debian, a unique <package>nova-consoleproxy</package> package provides "
-"the <package>nova-novncproxy</package>, <package>nova-"
-"spicehtml5proxy</package>, and <package>nova-xvpvncproxy</package> packages."
-" To select packages, edit the <filename>/etc/default/nova-"
-"consoleproxy</filename> file or use the <package>debconf</package> "
-"interface. You can also manually edit the <filename>/etc/default/nova-"
-"consoleproxy</filename> file, and stop and start the console daemons."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml142(title)
-msgid "Image management (EC2 scenario)"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml144(term)
-msgid "<systemitem class=\"service\">nova-objectstore</systemitem> daemon"
+"URL to invoke when state transitions to alarm. May be used multiple times. "
+"Defaults to None."
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml145(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml527(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml676(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml952(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1149(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1354(para)
 msgid ""
-"A S3 interface for registering images with the OpenStack Image Service. It "
-"is mainly used for installations that must support euca2ools. The euca2ools "
-"tools talk to <systemitem class=\"service\">nova-objectstore</systemitem> in"
-" <emphasis role=\"italic\">S3 language</emphasis>, and <systemitem "
-"class=\"service\">nova-objectstore</systemitem> translates S3 requests into "
-"Image service requests."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml154(term)
-msgid "euca2ools client"
+"URL to invoke when state transitions to OK. May be used multiple times. "
+"Defaults to None."
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml155(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml536(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml685(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml961(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1158(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1363(para)
 msgid ""
-"A set of command-line interpreter commands for managing cloud resources. "
-"Although it is not an OpenStack module, you can configure <systemitem "
-"class=\"service\">nova-api</systemitem> to support this EC2 interface. For "
-"more information, see the <link "
-"href=\"https://www.eucalyptus.com/docs/eucalyptus/3.4/index.html\">Eucalyptus"
-" 3.4 Documentation</link>."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml163(title)
-msgid "Command-line clients and other interfaces"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml164(term)
-msgid "nova client"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml165(para)
-msgid "Allows users to submit commands as a tenant administrator or end user."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml169(term)
-msgid "nova-manage client"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml170(para)
-msgid "Enables cloud administrators to submit commands."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml174(title)
-msgid "Other components"
-msgstr "Autres Composants"
-
-#: ./doc/common/section_getstart_compute.xml175(term)
-msgid "The queue"
+"URL to invoke when state transitions to insufficient_data. May be used "
+"multiple times. Defaults to None."
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml175(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml546(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml695(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml971(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1168(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1373(para)
 msgid ""
-"A central hub for passing messages between daemons. It is usually "
-"implemented with <link href=\"http://www.rabbitmq.com/\">RabbitMQ</link>, "
-"but could be any AMQP message queue, such as <link "
-"href=\"http://qpid.apache.org/\">Apache Qpid</link> or <link "
-"href=\"http://www.zeromq.org/\">Zero MQ</link>."
+"Only evaluate the alarm if the time at evaluation is within this time "
+"constraint. Start point(s) of the constraint are specified with a cron "
+"expression , whereas its duration is given in seconds. Can be specified "
+"multiple times for multiple time constraints, format is: "
+"name=&lt;CONSTRAINT_NAME&gt;;start=&lt; "
+"CRON&gt;;duration=&lt;SECONDS&gt;;[description=&lt;DESCRIPTION&gt;;[t "
+"imezone=&lt;IANA Timezone&gt;]] Defaults to None."
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml183(term)
-msgid "SQL database"
+#: ./doc/common/ch_cli_ceilometer_commands.xml561(para)
+msgid "List of alarm ids. Required."
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml184(para)
-msgid ""
-"Stores most build-time and runtime states for a cloud infrastructure. It "
-"includes instance types that are available for use, instances in use, "
-"available networks, and projects. Theoretically, OpenStack Compute can "
-"support any database that is supported by SQL-Alchemy. Note the databases "
-"which are widely used are SQLite3 databases (for test and development work),"
-" MySQL, and PostgreSQL."
+#: ./doc/common/ch_cli_ceilometer_commands.xml569(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml727(para)
+msgid "Operator to compare with, one of: ['and', 'or']."
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml192(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml577(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1046(para)
 msgid ""
-"OpenStack Compute interacts with OpenStack Identity for authentication; "
-"OpenStack Image Service for images; and the OpenStack dashboard for a web "
-"interface."
+"True if actions should be repeatedly notified while alarm remains in target "
+"state. Defaults to False."
 msgstr ""
 
-#: ./doc/common/section_compute-configure-console.xml5(title)
-msgid "Configure remote console access"
-msgstr "Configurer l’accès console à distance"
-
-#. <?dbhtml stop-chunking?>
-#: ./doc/common/section_compute-configure-console.xml7(para)
-msgid ""
-"To provide a remote console or remote desktop access to guest virtual "
-"machines, use VNC or SPICE HTML5 through either the OpenStack dashboard or "
-"the command line. Best practice is to select one or the other to run."
-msgstr "OpenStack dispose de deux méthodes principales pour fournir l’accès à une console à distance ou un bureau à distance sur des machines virtuelles hébergées. Ce sont VNC, et SPICE HTML5 et ils peuvent être utilisés soit via le tableau de bord OpenStack, soit en ligne de commande. La meilleure pratique consiste à sélectionner l'un ou l'autre pour fonctionner."
-
-#: ./doc/common/section_xapi-resize-setup.xml7(title)
-msgid "Modify Dom0 for resize/migration support"
+#: ./doc/common/ch_cli_ceilometer_commands.xml586(title)
+msgid "ceilometer alarm-combination-update command"
 msgstr ""
 
-#: ./doc/common/section_xapi-resize-setup.xml8(para)
-msgid "To resize servers with XenServer and XCP, you must:"
-msgstr "Afin d'obtenir la redimmension dans le but de travailler avec XenServer (et XCP), il faut:"
-
-#: ./doc/common/section_xapi-resize-setup.xml11(para)
-msgid ""
-"Establish a root trust between all hypervisor nodes of your deployment:"
-msgstr "Etablir une sécurité entre tous les noeuds de l''hyperviseur de votre développement:"
-
-#: ./doc/common/section_xapi-resize-setup.xml13(para)
-msgid ""
-"To do so, generate an ssh key-pair with the <placeholder-1/> command. Ensure"
-" that each of your dom0's <filename>authorized_keys</filename> file (located"
-" in <filename>/root/.ssh/authorized_keys</filename>) contains the public key"
-" fingerprint (located in <filename>/root/.ssh/id_rsa.pub</filename>)."
-msgstr "Pour se faire, il vous faut générer une paire de clés ssh (avec <placeholder-1/>), et vérifier ensuite que que chaque dossier dom0 <filename>authorized_keys</filename> file (located in <filename>/root/.ssh/authorized_keys</filename> (se trouvant dans /root/.ssh/ authorized_keys) contient l'empreinte de la clé publique (se trouvant dans <filename>/root/.ssh/id_rsa.pub</filename>)"
-
-#: ./doc/common/section_xapi-resize-setup.xml22(para)
-msgid ""
-"Provide an <filename>/images</filename> mount point to the dom0 for your "
-"hypervisor:"
-msgstr "Fournir un point de montage <filename>/images</filename> à l'hyperviseur de dom0:"
-
-#: ./doc/common/section_xapi-resize-setup.xml24(para)
-msgid ""
-"Dom0 space is at a premium so creating a directory in dom0 is potentially "
-"dangerous and likely to fail especially when you resize large servers. The "
-"least you can do is to symlink <filename>/images</filename> to your local "
-"storage SR. The following instructions work for an English-based "
-"installation of XenServer (and XCP) and in the case of ext3-based SR (with "
-"which the resize functionality is known to work correctly)."
-msgstr "L'espace Dom0 est un espace premium, il est donc risqué de créer un répertoire dans dom0. Cette entreprise échouera, en particulier au moment de redimensionner les gros serveurs. Il est néanmoins possible de lier symboliquement les <filename>/images</filename> dans vos stockages locaux SR.  Les instructions ci-dessous s'appliquent à une installation basée sur l'anglais de XenServer (et XCP), ainsi que dans le cas d'un SR basé sur ext3 (avec lequel la fonctionnalité de redimensionnement est connu pour fonctionner correctement)"
-
-#: ./doc/common/section_cli_nova_sshkeys.xml6(title)
-msgid "Add keypair"
-msgstr "Ajouter une paire de clés"
-
-#: ./doc/common/section_cli_nova_sshkeys.xml7(para)
-msgid ""
-"Create at least one keypair for each project. If you have generated a "
-"keypair with an external tool, you can import it into OpenStack. The keypair"
-" can be used for multiple instances that belong to a project."
+#: ./doc/common/ch_cli_ceilometer_commands.xml608(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1081(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1286(para)
+msgid "ID of the alarm to update. Required."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_sshkeys.xml13(para)
-msgid "Create a key."
-msgstr "Créez une clé."
-
-#: ./doc/common/section_cli_nova_sshkeys.xml14(para)
-msgid ""
-"To create a <literal>mykey</literal> key that you can associate with "
-"instances, run the following command:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml616(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1089(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1294(para)
+msgid "Name of the alarm (must be unique per tenant)."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_sshkeys.xml17(para)
-msgid ""
-"Save the <filename>mykey.pem</filename> file to a secure location. It "
-"enables root access to any instances with which the <literal>mykey</literal>"
-" key is associated."
+#: ./doc/common/ch_cli_ceilometer_commands.xml710(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1183(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1388(para)
+msgid "Name or list of names of the time constraints to remove."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_sshkeys.xml22(para)
-msgid "Alternatively, you can import a keypair."
+#: ./doc/common/ch_cli_ceilometer_commands.xml719(para)
+msgid "List of alarm id."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_sshkeys.xml23(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml735(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1252(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1457(para)
 msgid ""
-"To import an existing public key, <literal>mykey.pub</literal>, and "
-"associate it with the <literal>mykey</literal> key, run the following "
-"command:"
+"True if actions should be repeatedly notified while alarm remains in target "
+"state."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_sshkeys.xml28(para)
-msgid ""
-"You must have the matching private key to access instances that are "
-"associated with this key."
+#: ./doc/common/ch_cli_ceilometer_commands.xml744(title)
+msgid "ceilometer alarm-delete command"
 msgstr ""
 
-#: ./doc/common/section_dashboard-configure-https.xml4(title)
-msgid "Configure the dashboard for HTTPS"
-msgstr "Pour configurer le tableau de bord pour HTTPS"
-
-#: ./doc/common/section_dashboard-configure-https.xml5(para)
-#: ./doc/common/section_dashboard-configure.xml10(para)
-msgid ""
-"You can configure the dashboard for a secured HTTPS deployment. While the "
-"standard installation uses a non-encrypted HTTP channel, you can enable SSL "
-"support for the dashboard."
+#: ./doc/common/ch_cli_ceilometer_commands.xml753(para)
+msgid "ID of the alarm to delete. Required."
 msgstr ""
 
-#: ./doc/common/section_dashboard-configure-https.xml9(para)
-msgid ""
-"The following example uses the domain, \"http://openstack.example.com.\" Use"
-" a domain that fits your current setup."
-msgstr "L’exemple suivant utilise le domaine http://openstack.example.com. Utilisez un domaine qui corresponde à votre installation courante."
-
-#: ./doc/common/section_dashboard-configure-https.xml13(para)
-msgid ""
-"In<filename>/etc/openstack-dashboard/local_settings.py</filename> update the"
-" following directives:"
-msgstr "Dans <filename>/etc/openstack-dashboard/local_settings.py</filename>, mettez à jour le paramètre suivant :"
-
-#: ./doc/common/section_dashboard-configure-https.xml19(para)
-msgid ""
-"The first option is required to enable HTTPS. The other recommended settings"
-" defend against cross-site scripting and require HTTPS."
+#: ./doc/common/ch_cli_ceilometer_commands.xml761(title)
+msgid "ceilometer alarm-history command"
 msgstr ""
 
-#: ./doc/common/section_dashboard-configure-https.xml24(para)
-msgid ""
-"Edit <filename>/etc/apache2/ports.conf</filename> and add the following "
-"line:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml770(para)
+msgid "ID of the alarm for which history is shown. Required."
 msgstr ""
 
-#: ./doc/common/section_dashboard-configure-https.xml30(para)
-msgid ""
-"Edit <filename>/etc/apache2/conf.d/openstack-dashboard.conf:</filename>"
-msgstr "Editez le fichier <filename>/etc/apache2/conf.d/openstack-dashboard.conf:</filename>"
-
-#: ./doc/common/section_dashboard-configure-https.xml33(para)
-msgid "Before:"
-msgstr "Avant:"
-
-#: ./doc/common/section_dashboard-configure-https.xml46(para)
-msgid "After:"
-msgstr "Après:"
-
-#: ./doc/common/section_dashboard-configure-https.xml87(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml778(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml797(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1036(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1242(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1518(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1646(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1771(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1807(para)
 msgid ""
-"In this configuration, Apache http server listens on the port 443 and "
-"redirects all the hits to the HTTPS protocol for all the non-secured "
-"requests. The secured section defines the private key, public key, and "
-"certificate to use."
+"key[op]data_type::value; list. data_type is optional, but if supplied must "
+"be string, integer, float, or boolean."
 msgstr ""
 
-#: ./doc/common/section_dashboard-configure-https.xml94(para)
-msgid "Restart Apache http server. For Debian/Ubuntu/SUSE:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml788(title)
+msgid "ceilometer alarm-list command"
 msgstr ""
 
-#: ./doc/common/section_dashboard-configure-https.xml96(para)
-msgid "Or for Fedora/RHEL/CentOS:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml807(title)
+msgid "ceilometer alarm-show command"
 msgstr ""
 
-#: ./doc/common/section_dashboard-configure-https.xml98(para)
-#: ./doc/common/section_dashboard-configure-http.xml32(para)
-msgid "Next, restart memcached:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml816(para)
+msgid "ID of the alarm to show. Required."
 msgstr ""
 
-#: ./doc/common/section_dashboard-configure-https.xml100(para)
-msgid ""
-"If you try to access the dashboard through HTTP, the browser redirects you "
-"to the HTTPS page."
+#: ./doc/common/ch_cli_ceilometer_commands.xml824(title)
+msgid "ceilometer alarm-state-get command"
 msgstr ""
 
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_getstart_logical_arch.xml38(None)
-msgid ""
-"@@image: 'figures/openstack-arch-havana-logical-v1.jpg'; "
-"md5=e7acaaee72722626b045eda3fae81841"
+#: ./doc/common/ch_cli_ceilometer_commands.xml833(para)
+msgid "ID of the alarm state to show. Required."
 msgstr ""
 
-#: ./doc/common/section_getstart_logical_arch.xml5(title)
-#: ./doc/common/section_getstart_logical_arch.xml33(title)
-msgid "Logical architecture"
-msgstr "Architecture du logiciel"
-
-#: ./doc/common/section_getstart_logical_arch.xml6(para)
-msgid ""
-"To design, deploy, and configure OpenStack, administrators must understand "
-"the logical architecture."
+#: ./doc/common/ch_cli_ceilometer_commands.xml841(title)
+msgid "ceilometer alarm-state-set command"
 msgstr ""
 
-#: ./doc/common/section_getstart_logical_arch.xml7(para)
-msgid "OpenStack modules are one of the following types:"
-msgstr "Les modules sont classés selon l'un des types suivants :"
-
-#: ./doc/common/section_getstart_logical_arch.xml9(term)
-msgid "Daemon"
+#: ./doc/common/ch_cli_ceilometer_commands.xml850(para)
+msgid "ID of the alarm state to set. Required."
 msgstr ""
 
-#: ./doc/common/section_getstart_logical_arch.xml11(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml858(para)
 msgid ""
-"Runs as a background process. On Linux platforms, a daemon is usually "
-"installed as a service."
+"State of the alarm, one of: ['ok', 'alarm', 'insufficient_data']. Required."
 msgstr ""
 
-#: ./doc/common/section_getstart_logical_arch.xml15(term)
-msgid "Script"
+#: ./doc/common/ch_cli_ceilometer_commands.xml867(title)
+msgid "ceilometer alarm-threshold-create command"
 msgstr ""
 
-#: ./doc/common/section_getstart_logical_arch.xml17(para)
-msgid ""
-"Installs a virtual environment and runs tests. For example, the "
-"<code>run_tests.sh</code> script installs a virtual environment and runs "
-"unit tests on a service."
-msgstr ""
-
-#: ./doc/common/section_getstart_logical_arch.xml21(term)
-msgid "Command-line interface (CLI)"
+#: ./doc/common/ch_cli_ceilometer_commands.xml986(para)
+msgid "Metric to evaluate against. Required."
 msgstr ""
 
-#: ./doc/common/section_getstart_logical_arch.xml23(para)
-msgid ""
-"Enables users to submit API calls to OpenStack services through easy-to-use "
-"commands."
+#: ./doc/common/ch_cli_ceilometer_commands.xml994(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1200(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1397(para)
+msgid "Length of each period (seconds) to evaluate over."
 msgstr ""
 
-#: ./doc/common/section_getstart_logical_arch.xml29(para)
-msgid ""
-"The following diagram shows the most common, but not the only, architecture "
-"for an OpenStack cloud:"
-msgstr "le schéma ci-dessous illustre l'architecture la plus courante pour un cloud basé sur OpenStack, mais ne représente pas la seule architecture possible :"
-
-#: ./doc/common/section_getstart_logical_arch.xml42(para)
-msgid ""
-"As in <xref linkend=\"concept_arch\"/>, end users can interact through the "
-"dashboard, CLIs, and APIs. All services authenticate through a common "
-"Identity Service and individual services interact with each other through "
-"public APIs, except where privileged administrator commands are necessary."
-msgstr "Comme dans <xref linkend=\"concept_arch\"/>, les utilisateurs finaux peuvent interagir à travers le tableau de bord, les CLI, ou directement via les API, tous les services s'authentifient via un service d'identité commune, et les services individuels interagissent les uns avec les autres via des API publiques, sauf là où des privilèges d’administrateur sont nécessaires pour une commande."
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_keystone-concepts.xml120(None)
-#: ./doc/common/section_keystone-concepts.xml125(None)
-msgid ""
-"@@image: 'figures/SCH_5002_V00_NUAC-Keystone.png'; "
-"md5=734714c50c99fc1d74bdfd9f9cd049a6"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1002(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1208(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1405(para)
+msgid "Number of periods to evaluate over."
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts.xml7(title)
-msgid "OpenStack Identity concepts"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1010(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1216(para)
+msgid "Statistic to evaluate, one of: ['max', 'min', 'avg', 'sum', 'count']."
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts.xml8(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1019(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1225(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1430(para)
 msgid ""
-"The OpenStack<glossterm>Identity Service</glossterm> performs the following "
-"functions:"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts.xml12(para)
-msgid "Tracking users and their permissions."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts.xml15(para)
-msgid "Providing a catalog of available services with their API endpoints."
+"Operator to compare with, one of: ['lt', 'le', 'eq', 'ne', 'ge', 'gt']."
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts.xml19(para)
-msgid ""
-"To understand OpenStack Identity, you must understand the following "
-"concepts:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1028(para)
+msgid "Threshold to evaluate against. Required."
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts.xml23(term)
-msgid "User"
-msgstr "Utilisateur"
-
-#: ./doc/common/section_keystone-concepts.xml25(para)
-msgid ""
-"Digital representation of a person, system, or service who uses OpenStack "
-"cloud services. The Identity service validates that incoming requests are "
-"made by the user who claims to be making the call. Users have a login and "
-"may be assigned tokens to access resources. Users can be directly assigned "
-"to a particular tenant and behave as if they are contained in that tenant."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1055(title)
+msgid "ceilometer alarm-threshold-update command"
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts.xml36(term)
-msgid "Credentials"
-msgstr "Information  d'Authentification          "
-
-#: ./doc/common/section_keystone-concepts.xml38(para)
-msgid ""
-"Data that confirms the user's identity. For example, user name and password;"
-" user name and API key; or an authentication token provided by the Identity "
-"Service."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1192(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1413(para)
+msgid "Metric to evaluate against."
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts.xml45(term)
-msgid "Authentication"
-msgstr "Authentication"
-
-#: ./doc/common/section_keystone-concepts.xml47(para)
-msgid ""
-"The process of confirming the identity of a user. OpenStack Identity "
-"confirms an incoming request by validating a set of credentials supplied by "
-"the user."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1234(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1439(para)
+msgid "Threshold to evaluate against."
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts.xml51(para)
-msgid ""
-"These credentials are initially a user name and password; or a user name and"
-" API key. When user credentials are validated, OpenStack Identity issues an "
-"authentication token which the user provides in subsequent requests."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1261(title)
+msgid "ceilometer alarm-update command"
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts.xml59(term)
-msgid "Token"
-msgstr "Jeton/Token "
-
-#: ./doc/common/section_keystone-concepts.xml61(para)
-msgid ""
-"An arbitrary bit of text that is used to access resources. Each token has "
-"information which defines access to resources. A token may be revoked at any"
-" time and is valid for a finite duration."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1421(para)
+msgid "Statistic to evaluate, one of: ['max', 'min', 'avg', 'sum', 'count']"
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts.xml65(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1447(para)
 msgid ""
-"While OpenStack Identity supports token-based authentication in this "
-"release, the intention is to support additional protocols in the future. Its"
-" main purpose is to be an integration service, and not aspire to be a full-"
-"fledged identity store and management solution."
+"A meter should match this resource metadata (key=value) additionally to the "
+"meter_name. Defaults to None."
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts.xml74(term)
-msgid "Tenant"
-msgstr "Ensemble/Tenant"
-
-#: ./doc/common/section_keystone-concepts.xml76(para)
-msgid ""
-"A container used to group or isolate resources and/or identity objects. "
-"Depending on the service operator, a tenant may map to a customer, account, "
-"organization, or project."
-msgstr "Contenant utilisé pour regrouper ou isoler des ressources et/ou  des identités-objets. Selon l'opérateur de service, un ensemble peut être lié à des clients, comptes, organisations, ou projets."
-
-#: ./doc/common/section_keystone-concepts.xml85(para)
-msgid ""
-"An OpenStack service, such as Compute (nova), Object Storage (swift), or "
-"Image Service (glance). It provides one or more endpoints through which "
-"users can access resources and perform operations."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1466(title)
+msgid "ceilometer event-list command"
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts.xml92(term)
-msgid "Endpoint"
-msgstr "Destination"
-
-#: ./doc/common/section_keystone-concepts.xml94(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1475(para)
 msgid ""
-"A network-accessible address where you access a service, usually a URL "
-"address. If you are using an extension for templates, an endpoint template "
-"can be created, which represents the templates of all the consumable "
-"services that are available across the regions."
+"key[op]data_type::value; list. data_type is optional, but if supplied must "
+"be string, integer, floator datetime."
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts.xml102(term)
-msgid "Role"
-msgstr "Rôle"
-
-#: ./doc/common/section_keystone-concepts.xml104(para)
-msgid ""
-"A personality with a defined set of user rights and privileges to perform a "
-"specific set of operations."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1485(title)
+msgid "ceilometer event-show command"
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts.xml106(para)
-msgid ""
-"In the Identity service, a token that is issued to a user includes the list "
-"of roles. Services that are being called by that user determine how they "
-"interpret the set of roles a user has and to which operations or resources "
-"each role grants access."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1494(para)
+msgid "The id of the event. Should be a UUID Required."
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts.xml114(para)
-msgid "The following diagram shows the OpenStack Identity process flow:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1502(title)
+msgid "ceilometer event-type-list command"
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml6(title)
-msgid "Enable KVM"
-msgstr "Activer KVM"
-
-#: ./doc/common/section_kvm_enable.xml7(para)
-msgid ""
-"To perform these steps, you must be logged in as the "
-"<systemitem>root</systemitem> user."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1509(title)
+msgid "ceilometer meter-list command"
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml11(para)
-msgid ""
-"To determine whether the <literal>svm</literal> or <literal>vmx</literal> "
-"CPU extensions are present, run this command:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1528(title)
+msgid "ceilometer query-alarm-history command"
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml15(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1538(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1574(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1610(para)
 msgid ""
-"This command generates output if the CPU is hardware-virtualization capable."
-" Even if output is shown, you might still need to enable virtualization in "
-"the system BIOS for full support."
+"{complex_op: [{simple_op: {field_name: value}}]} The complex_op is one of: "
+"['and', 'or'], simple_op is one of: ['=', '!=', '&lt;', '&lt;=', '&gt;', "
+"'&gt;=']."
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml19(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1548(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1584(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1620(para)
 msgid ""
-"If no output appears, consult your system documentation to ensure that your "
-"CPU and motherboard support hardware virtualization. Verify that any "
-"relevant hardware virtualization options are enabled in the system BIOS."
+"[{field_name: direction}, {field_name: direction}] The direction is one of: "
+"['asc', 'desc']."
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml24(para)
-msgid ""
-"The BIOS for each manufacturer is different. If you must enable "
-"virtualization in the BIOS, look for an option containing the words "
-"<literal>virtualization</literal>, <literal>VT</literal>, "
-"<literal>VMX</literal>, or <literal>SVM</literal>."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1557(para)
+msgid "Maximum number of alarm history items to return."
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml32(para)
-msgid ""
-"To list the loaded kernel modules and verify that the <literal>kvm</literal>"
-" modules are loaded, run this command:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1565(title)
+msgid "ceilometer query-alarms command"
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml36(para)
-msgid ""
-"If the output includes <systemitem>kvm_intel</systemitem> or "
-"<systemitem>kvm_amd</systemitem>, the <systemitem>kvm</systemitem> hardware "
-"virtualization modules are loaded and your kernel meets the module "
-"requirements for OpenStack Compute."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1593(para)
+msgid "Maximum number of alarms to return."
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml43(para)
-msgid ""
-"If the output does not show that the <literal>kvm</literal> module is "
-"loaded, run this command to load it:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1601(title)
+msgid "ceilometer query-samples command"
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml47(para)
-msgid "Run the command for your CPU. For Intel, run this command:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1629(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1789(para)
+msgid "Maximum number of samples to return."
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml50(para)
-msgid "For AMD, run this command:"
-msgstr "Pour AMD, exécutez cette commande:"
-
-#: ./doc/common/section_kvm_enable.xml52(para)
-msgid ""
-"Because a KVM installation can change user group membership, you might need "
-"to log in again for changes to take effect."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1637(title)
+msgid "ceilometer resource-list command"
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml55(para)
-msgid ""
-"If the kernel modules do not load automatically, use the procedures listed "
-"in these subsections."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1656(title)
+msgid "ceilometer resource-show command"
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml59(para)
-msgid ""
-"If the checks indicate that required hardware virtualization support or "
-"kernel modules are disabled or unavailable, you must either enable this "
-"support on the system or find a system with this support."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1665(para)
+msgid "ID of the resource to show. Required."
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml64(para)
-msgid ""
-"Some systems require that you enable VT support in the system BIOS. If you "
-"believe your processor supports hardware acceleration but the previous "
-"command did not produce output, reboot your machine, enter the system BIOS, "
-"and enable the VT option."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1673(title)
+msgid "ceilometer sample-create command"
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml70(para)
-msgid ""
-"If KVM acceleration is not supported, configure Compute to use a different "
-"hypervisor, such as <link href=\"http://docs.openstack.org/trunk/config-"
-"reference/content/qemu.html\">QEMU</link> or <link "
-"href=\"http://docs.openstack.org/trunk/config-reference/content"
-"/introduction-to-xen.html\">Xen</link>."
-msgstr "Dans le cas où l'accélération KVM n'est pas supportée, Compute devra être configuré pour utiliser un autre hyperviseur comme <link href=\"http://docs.openstack.org/trunk/config-reference/content/qemu.html\">QEMU</link> ou <link href=\"http://docs.openstack.org/trunk/config-reference/content/introduction-to-xen.html\">Xen</link>."
-
-#: ./doc/common/section_kvm_enable.xml76(para)
-msgid ""
-"These procedures help you load the kernel modules for Intel-based and AMD-"
-"based processors if they do not load automatically during KVM installation."
-msgstr "Ces procédures décrit comment charger les modules de noyau pour les processeurs Intel et AMD, s'ils n'ont pas été chargés automatiquement par le processus d'installation de KVM de votre distribution."
-
-#: ./doc/common/section_kvm_enable.xml80(title)
-msgid "Intel-based processors"
-msgstr "Processeurs Intel"
-
-#: ./doc/common/section_kvm_enable.xml81(para)
-msgid ""
-"If your compute host is Intel-based, run these commands as root to load the "
-"kernel modules:"
-msgstr "Si votre ordinateur hôte est basé sur Intel, lancez en tant qu'utilisateur root les modules de noyau : "
-
-#: ./doc/common/section_kvm_enable.xml85(para)
-msgid ""
-"Add these lines to the <filename>/etc/modules</filename> file so that these "
-"modules load on reboot:"
-msgstr "Ajoutez les lignes suivantes à <filename>/etc/modules</filename> pour que ces modules soient chargés au redémarrage :"
-
-#: ./doc/common/section_kvm_enable.xml91(title)
-msgid "AMD-based processors"
-msgstr "Processeurs AMD"
-
-#: ./doc/common/section_kvm_enable.xml92(para)
-msgid ""
-"If your compute host is AMD-based, run these commands as root to load the "
-"kernel modules:"
-msgstr "Si votre ordinateur hôte est basé sur AMD, lancez en tant qu'utilisateur root les modules de noyau : "
-
-#: ./doc/common/section_kvm_enable.xml96(para)
-msgid ""
-"Add these lines to <filename>/etc/modules</filename> file so that these "
-"modules load on reboot:"
-msgstr "Ajoutez les lignes suivantes à <filename>/etc/modules</filename> pour que ces modules soient chargés au redémarrage : "
-
-#: ./doc/common/section_xapi-install-plugins.xml7(title)
-msgid "Install the XenAPI plug-ins"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1688(para)
+msgid "Tenant to associate with sample (only settable by admin users)."
 msgstr ""
 
-#: ./doc/common/section_xapi-install-plugins.xml8(para)
-msgid ""
-"When you use Xen as the hypervisor for OpenStack Compute, you can install a "
-"Python script (or any executable) on the host side, and call that through "
-"the XenAPI. These scripts are called plug-ins. The XenAPI plug-ins live in "
-"the nova code repository. These plug-ins have to be copied to the Dom0 for "
-"the hypervisor, to the appropriate directory, where xapi can find them. "
-"There are several options for the installation. The important thing is to "
-"ensure that the version of the plug-ins are in line with the nova "
-"installation by only installing plug-ins from a matching nova repository."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1697(para)
+msgid "User to associate with sample (only settable by admin users)."
 msgstr ""
 
-#: ./doc/common/section_xapi-install-plugins.xml19(title)
-msgid "Manually install the plug-in"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1706(para)
+msgid "ID of the resource. Required."
 msgstr ""
 
-#: ./doc/common/section_xapi-install-plugins.xml22(para)
-msgid "Create temporary files/directories:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1714(para)
+msgid "The meter name. Required."
 msgstr ""
 
-#: ./doc/common/section_xapi-install-plugins.xml27(para)
-msgid ""
-"Get the source from github. The example assumes the master branch is used. "
-"Amend the URL to match the version being used:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1722(para)
+msgid "The meter type. Required."
 msgstr ""
 
-#: ./doc/common/section_xapi-install-plugins.xml32(para)
-msgid ""
-"(Alternatively) To use the official Ubuntu packages, use the following "
-"commands to get the nova code base:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1730(para)
+msgid "The meter unit. Required."
 msgstr ""
 
-#: ./doc/common/section_xapi-install-plugins.xml39(para)
-msgid "Copy the plug-ins to the hypervisor:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1738(para)
+msgid "The sample volume. Required."
 msgstr ""
 
-#: ./doc/common/section_xapi-install-plugins.xml44(para)
-msgid "Remove the temporary files/directories:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1746(para)
+msgid "Resource metadata."
 msgstr ""
 
-#: ./doc/common/section_xapi-install-plugins.xml51(title)
-msgid "Package a XenServer supplemental pack"
-msgstr "Pour combiner un pack supplémentaire XenServer"
-
-#: ./doc/common/section_xapi-install-plugins.xml52(para)
-msgid ""
-"Follow these steps to produce a supplemental pack from the nova sources, and"
-" package it as a XenServer supplemental pack."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1754(para)
+msgid "The sample timestamp."
 msgstr ""
 
-#: ./doc/common/section_xapi-install-plugins.xml57(para)
-msgid ""
-"Create RPM packages. Given you have the nova sources. Use one of the methods"
-" in <xref linkend=\"manual_install\"/>:"
-msgstr "\t1.\tCréez les packs RPM. Il est entendu que vous possédez les sources nova (utilisez une des méthodes mentionnées dans le <xref linkend=\"manual_install\"/>)"
-
-#: ./doc/common/section_xapi-install-plugins.xml62(para)
-msgid ""
-"These commands leave an <filename>.rpm</filename> file in the "
-"<filename>rpmbuild/RPMS/noarch/</filename> directory."
-msgstr "Ces commandes laisseront un <filename>.rpm</filename> dans le répertoire <filename>rpmbuild/RPMS/noarch/</filename>."
-
-#: ./doc/common/section_xapi-install-plugins.xml68(para)
-msgid ""
-"Pack the RPM packages to a Supplemental Pack, using the XenServer DDK (the "
-"following command should be issued on the XenServer DDK virtual appliance, "
-"after the produced rpm file has been copied over):"
-msgstr "Combiner les packs RPM à un Pack Supplémentaire, en utilisant le XenServer DDK (la commande suivante sera utilisée pour l'appliance virtuelle XenServer DDK, après que le fichier rpm généré ait été copié):"
-
-#: ./doc/common/section_xapi-install-plugins.xml81(para)
-msgid ""
-"This command produces an <filename>.iso</filename> file in the output "
-"directory specified. Copy that file to the hypervisor."
-msgstr "Cette commande génère un fichier <filename>.iso</filename> dans le répertoire de sortie précisé. Copiez ce fichier dans l'hyperviseur."
-
-#: ./doc/common/section_xapi-install-plugins.xml87(para)
-msgid "Install the Supplemental Pack. Log in to the hypervisor, and issue:"
-msgstr "Installez le Pack Supplémentaire. Connectez-le à l'hyperviseur, et lancer:"
-
-#: ./doc/common/section_dashboard-configure-vnc-window.xml6(title)
-msgid "Change the size of the dashboard VNC window"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1762(title)
+msgid "ceilometer sample-list command"
 msgstr ""
 
-#: ./doc/common/section_dashboard-configure-vnc-window.xml7(para)
-msgid ""
-"The <filename>_detail_vnc.html</filename> file defines the size of the VNC "
-"window. To change the window size, edit this file."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1781(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1817(para)
+msgid "Name of meter to show samples for. Required."
 msgstr ""
 
-#: ./doc/common/section_dashboard-configure-vnc-window.xml12(para)
-msgid ""
-"Edit "
-"<filename>/usr/share/pyshared/horizon/dashboards/nova/instances/templates/instances/_detail_vnc.html.</filename>"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1797(title)
+msgid "ceilometer statistics command"
 msgstr ""
 
-#: ./doc/common/section_dashboard-configure-vnc-window.xml16(para)
-msgid ""
-"Modify the <literal>width</literal> and <literal>height</literal> "
-"parameters, as follows:"
-msgstr "Modifiez les paramètres width (largeur) et height (hauteur), comme suit :"
-
-#: ./doc/common/section_cli_nova_fileinjection.xml10(title)
-msgid "Inject files into instances"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1825(para)
+msgid "Period in seconds over which to group samples."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_fileinjection.xml11(para)
-msgid ""
-"You can inject local files into the instance file system when you launch an "
-"instance."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1833(para)
+msgid "Field for group by."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_fileinjection.xml13(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1841(para)
 msgid ""
-"Use the <parameter>--file dst-path=src-path</parameter> parameter on the "
-"nova <placeholder-1/> command."
+"Function for data aggregation. Available aggregates are: count, cardinality,"
+" min, max, sum, stddev, avg. Defaults to []."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_fileinjection.xml15(para)
-msgid "You can inject up to five files."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1851(title)
+msgid "ceilometer trait-description-list command"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_fileinjection.xml16(para)
-msgid ""
-"For example, you might inject the "
-"<filename>special_authorized_keysfile</filename> file into the instance "
-"rather than using the regular ssh key injection."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1860(para)
+msgid "Type of the event for which traits will be shown. Required."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_fileinjection.xml19(para)
-msgid "Run the following command:<placeholder-1/>"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1869(title)
+msgid "ceilometer trait-list command"
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml7(title)
-msgid "Certificates for PKI"
-msgstr "Certificats pour PKI"
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml8(para)
-msgid ""
-"PKI stands for Public Key Infrastructure. Tokens are documents, "
-"cryptographically signed using the X509 standard. In order to work correctly"
-" token generation requires a public/private key pair. The public key must be"
-" signed in an X509 certificate, and the certificate used to sign it must be "
-"available as Certificate Authority (CA) certificate. These files can be "
-"generated either using the <placeholder-1/> utility, or externally "
-"generated. The files need to be in the locations specified by the top level "
-"Identity Service configuration file <filename>keystone.conf</filename> as "
-"specified in the above section. Additionally, the private key should only be"
-" readable by the system user that will run the Identity Service."
-msgstr "PKI signifie Public Key Infrastructure (Infrastructure de Clé Publique). Les jetons sont des document , signés de façon cryptographique via les standards X509. Afin de fonctionner correctement, l'émission de jetons nécessite une paire de clés publique/privée. La clé publique doit être signée dans un certificat X509, et le certificat utilisé pour la signer doit être disponible comme certificat d’Autorité de Certification (CA). Ces fichiers peuvent être générés soit en utilisant l'utilitaire keystone-manage, ou être générés de façon extérieure. Les fichiers doivent être dans les emplacements spécifiés par le fichier de configuration Keystone de plus haut niveau, comme spécifié dans la section précédente. De plus, la clé privée ne devrait être lisible que par l'utilisateur système qui mettra Keystone en marche."
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml23(para)
-msgid ""
-"The certificates can be world readable, but the private key cannot be. The "
-"private key should only be readable by the account that is going to sign "
-"tokens. When generating files with the <placeholder-1/> command, your best "
-"option is to run as the pki user. If you run nova-manage as root, you can "
-"append --keystone-user and --keystone-group parameters to set the username "
-"and group keystone is going to run under."
-msgstr "Les certificats peuvent être lus mondialement, mais non la clé privée. La clé privée ne devrait être lisible que par le compte qui va signer les jetons.  Lorsque l'on génère des fichiers avec la commande <placeholder-1/>, la meilleure option est de la lancer en tant qu'utilisateur pki. Si vous lancez nova-manage en tant qu’administrateur vous pouvez ajouter des paramètres keystone-user et --keystone-group pour définir le nom d'utilisateur et le groupe sous lesquels keystone va fonctionner."
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml33(para)
-msgid ""
-"The values that specify where to read the certificates are under the "
-"<literal>[signing]</literal> section of the configuration file. The "
-"configuration values are:"
-msgstr "Les valeurs qui spécifient où lire les certificats sont dans la section  <literal>[signing]</literal> du fichier de  configuration. Les valeurs de configuration sont :"
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml38(para)
-msgid ""
-"<literal>token_format</literal> - Determines the algorithm used to generate "
-"tokens. Can be either <literal>UUID</literal> or <literal>PKI</literal>. "
-"Defaults to <literal>PKI</literal>."
-msgstr "<literal>token_format</literal> – Détermine l'algorithme utilisé pour générer les jetons. Peut être soit <literal>UUID</literal> ou <literal>PKI</literal>. Par défaut <literal>PKI</literal>."
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml45(para)
-msgid ""
-"<literal>certfile</literal> - Location of certificate used to verify tokens."
-" Default is <literal>/etc/keystone/ssl/certs/signing_cert.pem</literal>."
-msgstr "<literal>certfile</literal> – Emplacement du certificat utilisé pour vérifier les jetons. Par défaut <literal>/etc/keystone/ssl/certs/signing_cert.pem</literal>."
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml51(para)
-msgid ""
-"<literal>keyfile</literal> - Location of private key used to sign tokens. "
-"Default is <literal>/etc/keystone/ssl/private/signing_key.pem</literal>."
-msgstr "<literal>keyfile</literal> – Emplacement de la clé privée utilisée pour signer les jetons. Par défaut  <literal>/etc/keystone/ssl/private/signing_key.pem</literal>"
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml57(para)
-msgid ""
-"<literal>ca_certs</literal> - Location of certificate for the authority that"
-" issued the above certificate. Default is "
-"<literal>/etc/keystone/ssl/certs/ca.pem</literal>."
-msgstr "<literal>ca_certs</literal> – Emplacement du certificat pour l'autorité ayant émis le certificat précédent. Par défaut <literal>/etc/keystone/ssl/certs/ca.pem</literal>."
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml64(para)
-msgid "<literal>key_size</literal> - Default is <literal>1024</literal>."
-msgstr "<literal>key_size</literal> – Par défaut <literal>1024</literal>."
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml69(para)
-msgid "<literal>valid_days</literal> - Default is <literal>3650</literal>."
-msgstr "<literal>valid_days</literal>  - Par défaut <literal>3650</literal>."
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml74(para)
-msgid ""
-"<literal>ca_password</literal> - Password required to read the "
-"<literal>ca_file</literal>. Default is <literal>None</literal>."
-msgstr "<literal>ca_password</literal> – Mot de passe requis pour lire le <literal>ca_file</literal>. Par défaut <literal>None</literal>."
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml80(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1871(para)
 msgid ""
-"If <literal>token_format=UUID</literal>, a typical token looks like "
-"<literal>53f7f6ef0cc344b5be706bcc8b1479e1</literal>. If "
-"<literal>token_format=PKI</literal>, a typical token is a much longer "
-"string, such as:"
-msgstr " Si <literal>token_format=UUID</literal>, un jeton typique ressemblera à <literal>53f7f6ef0cc344b5be706bcc8b1479e1</literal>. Si <literal>token_format=PKI</literal>, un jeton typique sera beaucoup plus long, comme ceci :"
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml113(title)
-msgid "Sign certificate issued by external CA"
-msgstr "Signer un Certificat émis par une CA externe"
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml114(para)
-msgid ""
-"You can use a signing certificate issued by an external CA instead of "
-"generated by <placeholder-1/>. However, a certificate issued by an external "
-"CA must satisfy the following conditions:"
+"List trait all traits with name &lt;trait_name&gt; for Event Type "
+"&lt;event_type&gt;."
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml121(para)
-msgid ""
-"all certificate and key files must be in Privacy Enhanced Mail (PEM) format"
-msgstr "Tous les fichiers certificats et clés doivent êtres en format PEM [original](Privacy Enhanced Mail)[/original]"
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml125(para)
-msgid "private key files must not be protected by a password"
-msgstr "Les fichiers de clés privées ne doivent pas être protégés par un mot de passe"
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml129(para)
-msgid ""
-"When using signing certificate issued by an external CA, you do not need to "
-"specify <literal>key_size</literal>, <literal>valid_days</literal>, and "
-"<literal>ca_password</literal> as they will be ignored."
-msgstr "Lorsque l'on utilise un certificat de signature émis pas une CA externe, il n'y a pas besoin de spécifier <literal>key_size</literal>, <literal>valid_days</literal>, et <literal>ca_password</literal>, puisqu'il seront ignorés."
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml134(para)
-msgid ""
-"The basic workflow for using a signing certificate issued by an external CA "
-"involves:"
-msgstr "Le flux de travail basique lorsqu'on utilise un certificat de signature émis par une CA externe implique :"
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml138(para)
-msgid "Request Signing Certificate from External CA"
-msgstr "Demander un Certificat de Signature à une CA externe"
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml142(para)
-msgid "Convert certificate and private key to PEM if needed"
-msgstr "Convertir le Certificat et la clé privée en PEM si nécessaire"
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml146(para)
-msgid "Install External Signing Certificate"
-msgstr "Installer le Certificat de Signature Externe"
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml151(title)
-msgid "Request a signing certificate from an external CA"
-msgstr "Demander un Certificat de Signature à une CA externe"
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml153(para)
-msgid ""
-"One way to request a signing certificate from an external CA is to first "
-"generate a PKCS #10 Certificate Request Syntax (CRS) using OpenSSL CLI."
-msgstr "Un façon de demander un certificat de signature à une CA externe est de d'abord générer une Syntaxe pou Requête de Certification (CRS-Certificate  Request  Syntax) en PKCS #10 via OpenSSL CLI. "
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml156(para)
-msgid ""
-"Create a certificate request configuration file. For example, create the "
-"<filename>cert_req.conf</filename> file, as follows:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1878(para)
+msgid "Type of the event for which traits will listed. Required."
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml176(para)
-msgid ""
-"Then generate a CRS with OpenSSL CLI. <emphasis role=\"strong\">Do not "
-"encrypt the generated private key. Must use the -nodes option.</emphasis>"
-msgstr "Puis générez une CRS avec OpenSSL CLI. <emphasis role=\"strong\">N'encryptez pas la clé privée générée. Vous devez utiliser l'option -nodes.</emphasis>"
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml183(para)
-msgid ""
-"If everything is successful, you should end up with "
-"<filename>signing_cert_req.pem</filename> and "
-"<filename>signing_key.pem</filename>. Send "
-"<filename>signing_cert_req.pem</filename> to your CA to request a token "
-"signing certificate and make sure to ask the certificate to be in PEM "
-"format. Also, make sure your trusted CA certificate chain is also in PEM "
-"format."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1887(para)
+msgid "The name of the trait to list. Required."
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml193(title)
-msgid "Install an external signing certificate"
-msgstr "Installer un Certificat de Signature Externe"
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml194(para)
-msgid "Assuming you have the following already:"
-msgstr "En supposant que vous possédez déjà les suivants :"
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml197(para)
-msgid ""
-"<filename>signing_cert.pem</filename> - (Keystone token) signing certificate"
-" in PEM format"
-msgstr "<filename>signing_cert.pem</filename> – (jeton Keystone) certificat de signature au format PEM "
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml202(para)
-msgid ""
-"<filename>signing_key.pem</filename> - corresponding (non-encrypted) private"
-" key in PEM format"
-msgstr "<filename>signing_key.pem</filename> – Clé privée (non-cryptée) correspondante au format PEM"
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml208(para)
-msgid ""
-"<filename>cacert.pem</filename> - trust CA certificate chain in PEM format"
-msgstr "• <filename>cacert.pem</filename> – Chaîne de certificat de CA de confiance au format PEM"
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml213(para)
-msgid "Copy the above to your certificate directory. For example:"
-msgstr "Copiez ce qui précède dans votre dossier de certificats. Par exemple :"
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml221(para)
-msgid "Make sure the certificate directory is only accessible by root."
-msgstr "Assurez-vous que le dossier de certificats n’est accessible que par root (racine)."
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml224(para)
-msgid ""
-"If your certificate directory path is different from the default "
-"<filename>/etc/keystone/ssl/certs</filename>, make sure it is reflected in "
-"the <literal>[signing]</literal> section of the configuration file."
-msgstr "Si le chemin de votre dossier de certificats diffère du chemin par défaut <filename>/etc/keystone/ssl/certs</filename>, assurez-vous que ce changement soit reflété dans la section <literal>[signing]</literal> du fichier de configuration."
-
 #: ./doc/common/ch_cli_cinder_commands.xml11(title)
 msgid "Block Storage command-line client"
 msgstr ""
@@ -16005,6962 +16122,503 @@ msgstr ""
 msgid "Optional type for disk format (Default=raw)"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml7(title)
-#: ./doc/common/section_dashboard_access.xml304(guilabel)
-msgid "Flavors"
-msgstr "Types d'instance"
+#: ./doc/common/section_cli_glance_manage_images.xml7(title)
+msgid "Manage images"
+msgstr "Gérez les images"
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml8(para)
+#: ./doc/common/section_cli_glance_manage_images.xml8(para)
 msgid ""
-"Admin users can use the <placeholder-1/> commands to customize and manage "
-"flavors. To see the available flavor-related commands, run:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml22(para)
-msgid ""
-"Configuration rights can be delegated to additional users by redefining the "
-"access controls for <option>compute_extension:flavormanage</option> in "
-"<filename>/etc/nova/policy.json</filename> on the <systemitem class=\"server"
-"\">nova-api</systemitem> server."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml26(para)
-msgid ""
-"To modify an existing flavor in the dashboard, you must delete the flavor "
-"and create a modified one with the same name."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml31(para)
-msgid "Flavors define these elements:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml33(caption)
-msgid "Identity Service configuration file sections"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml39(td)
-msgid "Element"
-msgstr "élément"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml45(literal)
-msgid "Name"
-msgstr "Nom"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml47(replaceable)
-msgid "XX"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml47(replaceable)
-msgid "SIZE_NAME"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml46(td)
-msgid ""
-"A descriptive name. <placeholder-1/>.<placeholder-2/> is typically not "
-"required, though some third party tools may rely on it."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml52(literal)
-msgid "Memory_MB"
-msgstr "Memory_MB"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml53(td)
-msgid "Virtual machine memory in megabytes."
-msgstr "Mémoire de la machine virtuel en mégaoctets."
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml56(literal)
-msgid "Disk"
-msgstr "Disque"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml57(td)
-msgid ""
-"Virtual root disk size in gigabytes. This is an ephemeral disk that the base"
-" image is copied into. When booting from a persistent volume it is not used."
-" The \"0\" size is a special case which uses the native base image size as "
-"the size of the ephemeral root volume."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml65(literal)
-msgid "Ephemeral"
-msgstr "Éphémère"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml66(td)
-msgid ""
-"Specifies the size of a secondary ephemeral data disk. This is an empty, "
-"unformatted disk and exists only for the life of the instance."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml71(literal)
-msgid "Swap"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml72(td)
-msgid "Optional swap space allocation for the instance."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml76(literal)
-msgid "VCPUs"
-msgstr "VCPUs"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml77(td)
-msgid "Number of virtual CPUs presented to the instance."
-msgstr "Nombre de UC virtuelles présentées à l'instance. "
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml81(literal)
-msgid "RXTX_Factor"
-msgstr "RXTX_Factor"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml82(td)
-msgid ""
-"Optional property allows created servers to have a different bandwidth cap "
-"than that defined in the network they are attached to. This factor is "
-"multiplied by the rxtx_base property of the network. Default value is 1.0. "
-"That is, the same as attached network."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml90(literal)
-msgid "Is_Public"
-msgstr "Is_Public"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml91(td)
-msgid ""
-"Boolean value, whether flavor is available to all users or private to the "
-"tenant it was created in. Defaults to True."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml96(literal)
-msgid "extra_specs"
-msgstr "extra_specs"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml97(para)
-msgid ""
-"Key and value pairs that define on which compute nodes a flavor can run. "
-"These pairs must match corresponding pairs on the compute nodes. Use to "
-"implement special resources, such as flavors that run on only compute nodes "
-"with GPU hardware."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml105(para)
-msgid ""
-"Flavor customization can be limited by the hypervisor in use. For example "
-"the <systemitem>libvirt</systemitem> driver enables quotas on CPUs available"
-" to a VM, disk tuning, bandwidth I/O, watchdog behavior, random number "
-"generator device control, and instance VIF traffic control."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml110(term)
-msgid "CPU limits"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml111(para)
-msgid ""
-"You can configure the CPU limits with control parameters with the "
-"<placeholder-1/> client. For example, to configure the I/O limit, use:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml115(para)
-msgid ""
-"There are optional CPU control parameters for weight shares, enforcement "
-"intervals for runtime quotas, and a quota for maximum allowed bandwidth:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml121(para)
-msgid ""
-"<literal>cpu_shares</literal> specifies the proportional weighted share for "
-"the domain. If this element is omitted, the service defaults to the OS "
-"provided defaults. There is no unit for the value; it is a relative measure "
-"based on the setting of other VMs. For example, a VM configured with value "
-"2048 gets twice as much CPU time as a VM configured with value 1024."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml130(para)
-msgid ""
-"<literal>cpu_period</literal> specifies the enforcement interval (unit: "
-"microseconds) for QEMU and LXC hypervisors. Within a period, each VCPU of "
-"the domain is not allowed to consume more than the quota worth of runtime. "
-"The value should be in range <literal>[1000, 1000000]</literal>. A period "
-"with value 0 means no value."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml138(para)
-msgid ""
-"<literal>cpu_quota</literal> specifies the maximum allowed bandwidth (unit: "
-"microseconds). A domain with a negative-value quota indicates that the "
-"domain has infinite bandwidth, which means that it is not bandwidth "
-"controlled. The value should be in range <literal>[1000, "
-"18446744073709551]</literal> or less than 0. A quota with value 0 means no "
-"value. You can use this feature to ensure that all vCPUs run at the same "
-"speed. For example:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml147(para)
-msgid ""
-"In this example, the instance of <literal>m1.low_cpu</literal> can only "
-"consume a maximum of 50% CPU of a physical CPU computing capability."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml155(term)
-msgid "Disk tuning"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml156(para)
-msgid ""
-"Using disk I/O quotas, you can set maximum disk write to 10 MB per second "
-"for a VM user. For example:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml159(para)
-msgid "The disk I/O options are:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml162(para)
-msgid "disk_read_bytes_sec"
-msgstr "disk_read_bytes_sec"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml165(para)
-msgid "disk_read_iops_sec"
-msgstr "disk_read_iops_sec"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml168(para)
-msgid "disk_write_bytes_sec"
-msgstr "disk_write_bytes_sec"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml171(para)
-msgid "disk_write_iops_sec"
-msgstr "disk_write_iops_sec"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml174(para)
-msgid "disk_total_bytes_sec"
-msgstr "disk_total_bytes_sec"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml177(para)
-msgid "disk_total_iops_sec"
-msgstr "disk_total_iops_sec"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml180(para)
-msgid "The vif I/O options are:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml183(para)
-msgid "vif_inbound_ average"
-msgstr "vif_inbound_ average"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml186(para)
-msgid "vif_inbound_burst"
-msgstr "vif_inbound_burst"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml189(para)
-msgid "vif_inbound_peak"
-msgstr "vif_inbound_peak"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml192(para)
-msgid "vif_outbound_ average"
-msgstr "vif_outbound_ average"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml195(para)
-msgid "vif_outbound_burst"
-msgstr "vif_outbound_burst"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml198(para)
-msgid "vif_outbound_peak"
-msgstr "vif_outbound_peak"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml202(term)
-msgid "Bandwidth I/O"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml203(para)
-msgid ""
-"Incoming and outgoing traffic can be shaped independently. The bandwidth "
-"element can have at most one inbound and at most one outbound child element."
-" If you leave any of these children element out, no quality of service (QoS)"
-" is applied on that traffic direction. So, if you want to shape only the "
-"network's incoming traffic, use inbound only (and vice versa). Each element "
-"has one mandatory attribute average, which specifies the average bit rate on"
-" the interface being shaped."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml209(para)
-msgid ""
-"There are also two optional attributes (integer): <option>peak</option>, "
-"which specifies maximum rate at which bridge can send data "
-"(kilobytes/second), and <option>burst</option>, the amount of bytes that can"
-" be burst at peak speed (kilobytes). The rate is shared equally within "
-"domains connected to the network."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml214(para)
-msgid ""
-"The following example configures a bandwidth limit for instance network "
-"traffic:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml219(term)
-msgid "Watchdog behavior"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml220(para)
-msgid ""
-"For the <systemitem>libvirt</systemitem> driver, you can enable and set the "
-"behavior of a virtual hardware watchdog device for each flavor. Watchdog "
-"devices keep an eye on the guest server, and carry out the configured action"
-" if the server hangs. The watchdog uses the i6300esb device (emulating a PCI"
-" Intel 6300ESB). If <literal>hw_watchdog_action</literal> is not specified, "
-"the watchdog is disabled."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml226(para)
-msgid "To set the behavior, use:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml227(replaceable)
-#: ./doc/common/section_cli_nova_customize_flavors.xml257(replaceable)
-#: ./doc/common/section_cli_nova_customize_flavors.xml258(replaceable)
-#: ./doc/common/section_cli_nova_customize_flavors.xml259(replaceable)
-msgid "FLAVOR-NAME"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml227(replaceable)
-msgid "ACTION"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml228(para)
-msgid "Valid <replaceable>ACTION</replaceable> values are:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml231(para)
-msgid "<literal>disabled</literal>(default) The device is not attached."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml234(para)
-msgid "<literal>reset</literal>Forcefully reset the guest."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml238(para)
-msgid "<literal>poweroff</literal>Forcefully power off the guest."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml242(para)
-msgid "<literal>pause</literal>Pause the guest."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml245(para)
-msgid ""
-"<literal>none</literal>Only enable the watchdog; do nothing if the server "
-"hangs."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml249(para)
-msgid ""
-"Watchdog behavior set using a specific image's properties will override "
-"behavior set using flavors."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml254(term)
-msgid "Random-number generator"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml255(para)
-msgid ""
-"If a random-number generator device has been added to the instance through "
-"its image properties, the device can be enabled and configured using:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml258(replaceable)
-msgid "RATE-BYTES"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml259(replaceable)
-msgid "RATE-PERIOD"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml263(para)
-msgid ""
-"<replaceable>RATE-BYTES</replaceable>(Integer) Allowed amount of bytes that "
-"the guest can read from the host's entropy per period."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml267(para)
-msgid ""
-"<replaceable>RATE-PERIOD</replaceable>(Integer) Duration of the read period "
-"in seconds."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml273(term)
-msgid "Instance VIF traffic control"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml274(para)
-msgid ""
-"Flavors can also be assigned to particular projects. By default, a flavor is"
-" public and available to all projects. Private flavors are only accessible "
-"to those on the access list and are invisible to other projects. To create "
-"and assign a private flavor to a project, run these commands:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_evacuate.xml6(title)
-msgid "Evacuate instances"
-msgstr "Evacuation d'une instance"
-
-#: ./doc/common/section_cli_nova_evacuate.xml7(para)
-msgid ""
-"If a cloud compute node fails due to a hardware malfunction or another "
-"reason, you can evacuate instances to make them available again. You can "
-"choose evacuation parameters for your use case."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_evacuate.xml10(para)
-msgid ""
-"To preserve user data on server disk, you must configure shared storage on "
-"the target host. Also, you must validate that the current VM host is down; "
-"otherwise, the evacuation fails with an error."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_evacuate.xml15(para)
-msgid ""
-"To list hosts and find a different host for the evacuated instance, run:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_evacuate.xml19(para)
-msgid ""
-"Evacuate the instance. You can pass the instance password to the command by "
-"using the <literal>--password &lt;pwd&gt;</literal> option. If you do not "
-"specify a password, one is generated and printed after the command finishes "
-"successfully. The following command evacuates a server without shared "
-"storage from a host that is down to the specified "
-"<replaceable>host_b</replaceable>:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_evacuate.xml24(replaceable)
-#: ./doc/common/section_cli_nova_evacuate.xml40(replaceable)
-msgid "evacuated_server_name"
-msgstr "evacuated_server_name"
-
-#: ./doc/common/section_cli_nova_evacuate.xml24(replaceable)
-#: ./doc/common/section_cli_nova_evacuate.xml40(replaceable)
-msgid "host_b"
-msgstr "host_b"
-
-#: ./doc/common/section_cli_nova_evacuate.xml25(para)
-msgid ""
-"The instance is booted from a new disk, but preserves its configuration "
-"including its ID, name, uid, IP address, and so on. The command returns a "
-"password:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_evacuate.xml34(para)
-msgid ""
-"To preserve the user disk data on the evacuated server, deploy OpenStack "
-"Compute with a shared file system. To configure your system, see <link "
-"href=\"http://docs.openstack.org/icehouse/config-reference/content"
-"/configuring-openstack-compute-basics.html#section_configuring-compute-"
-"migrations\">Configure migrations</link> in <citetitle>OpenStack "
-"Configuration Reference</citetitle>. In the following example, the password "
-"remains unchanged:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_read-only-volumes.xml6(title)
-msgid "Set a volume to read-only access"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_read-only-volumes.xml7(para)
-msgid ""
-"To give multiple users shared, secure access to the same data, you can set a"
-" volume to read-only access."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_read-only-volumes.xml9(para)
-msgid "Run the following command to set a volume to read-only access:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_read-only-volumes.xml11(replaceable)
-msgid "VOLUME"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_read-only-volumes.xml11(replaceable)
-msgid "BOOLEAN"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_read-only-volumes.xml12(para)
-msgid ""
-"<replaceable>VOLUME</replaceable> is the ID of the target volume and "
-"<replaceable>BOOLEAN</replaceable> is a flag that enables read-only or "
-"read/write access to the volume."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_read-only-volumes.xml15(para)
-msgid "The following values for <replaceable>BOOLEAN</replaceable> are valid:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_read-only-volumes.xml19(para)
-msgid ""
-"<literal>true</literal>. Sets the read-only flag in the volume. When you "
-"attach the volume to an instance, the instance checks for this flag to "
-"determine whether to restrict volume access to read-only."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_read-only-volumes.xml25(para)
-msgid "<literal>false</literal>. Sets the volume to read/write access."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml7(title)
-msgid "Create and manage networks"
-msgstr "Créez et gérez des réseaux"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml8(para)
-msgid "Before you run commands, set the following environment variables:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml15(title)
-msgid "Create networks"
-msgstr "Créez des réseaux"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml18(para)
-msgid "List the extensions of the system:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml34(para)
-msgid "Create a network:"
-msgstr "Créez un réseau"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml53(para)
-msgid "Some fields of the created network are invisible to non-admin users."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml58(para)
-msgid "Create a network with specified provider network type:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml77(para)
-msgid ""
-"Just as shown previously, the unknown option <literal>--provider:network-"
-"type</literal> is used to create a <literal>local</literal> provider "
-"network."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml85(title)
-msgid "Create subnets"
-msgstr "Créez des sous-réseaux"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml88(para)
-msgid "Create a subnet:"
-msgstr "Créez un sous-réseau"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml106(para)
-msgid ""
-"The <placeholder-1/> command has the following positional and optional "
-"parameters:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml111(para)
-msgid "The name or ID of the network to which the subnet belongs."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml113(para)
-msgid ""
-"In this example, <literal>net1</literal> is a positional argument that "
-"specifies the network name."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml118(para)
-msgid "The CIDR of the subnet."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml119(para)
-msgid ""
-"In this example, <literal>192.168.2.0/24</literal> is a positional argument "
-"that specifies the CIDR."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml125(para)
-msgid "The subnet name, which is optional."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml127(para)
-msgid ""
-"In this example, <literal>--name subnet1</literal> specifies the name of the"
-" subnet."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml136(title)
-msgid "Create routers"
-msgstr "Créer des routeurs"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml139(para)
-msgid "Create a router:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml140(replaceable)
-msgid "router1"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml152(para)
-msgid ""
-"Take note of the unique router identifier returned, this will be required in"
-" subsequent steps."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml156(para)
-msgid "Link the router to the external provider network:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml157(replaceable)
-#: ./doc/common/section_cli_neutron_manage_networks.xml164(replaceable)
-msgid "ROUTER"
-msgstr "ROUTEUR"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml157(replaceable)
-msgid "NETWORK"
-msgstr "RESEAU"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml158(para)
-msgid ""
-"Replace <replaceable>ROUTER</replaceable> with the unique identifier of the "
-"router, replace <replaceable>NETWORK</replaceable> with the unique "
-"identifier of the external provider network."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml163(para)
-msgid "Link the router to the subnet:"
-msgstr "Liez le routeur au sous-réseau:"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml164(replaceable)
-msgid "SUBNET"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml165(para)
-msgid ""
-"Replace <replaceable>ROUTER</replaceable> with the unique identifier of the "
-"router, replace <replaceable>SUBNET</replaceable> with the unique identifier"
-" of the subnet."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml172(title)
-msgid "Create ports"
-msgstr "Créer des ports"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml175(para)
-msgid "Create a port with specified IP address:"
-msgstr "Créer un port avec une adresse IP précisée:"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml194(para)
-msgid ""
-"In the previous command, <literal>net1</literal> is the network name, which "
-"is a positional argument. <literal>--fixed-ip "
-"ip_address=192.168.2.40</literal> is an option, which specifies the port's "
-"fixed IP address we wanted."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml201(para)
-msgid ""
-"When creating a port, you can specify any unallocated IP in the subnet even "
-"if the address is not in a pre-defined pool of allocated IP addresses (set "
-"by your cloud provider)."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml208(para)
-msgid "Create a port without specified IP address:"
-msgstr "Créer un port sans une adresse IP précisée:"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml229(para)
-msgid ""
-"Note that the system allocates one IP address if you do not specify an IP "
-"address in the <placeholder-1/> command."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml234(para)
-msgid "Query ports with specified fixed IP addresses:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml243(para)
-msgid ""
-"<literal>--fixed-ips ip_address=192.168.2.2 "
-"ip_address=192.168.2.40</literal> is one unknown option."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml246(para)
-msgid ""
-"<emphasis role=\"bold\">How to find unknown options?</emphasis> The unknown "
-"options can be easily found by watching the output of "
-"<literal>create_xxx</literal> or <literal>show_xxx</literal> command. For "
-"example, in the port creation command, we see the fixed_ips fields, which "
-"can be used as an unknown option."
-msgstr ""
-
-#: ./doc/common/ch_preface.xml7(title)
-msgid "Preface"
-msgstr "Preface"
-
-#: ./doc/common/section_cli_keystone_apiv3.xml5(title)
-msgid "Use Identity Service API v3 instead of API v2.0"
-msgstr "Utilise Service d'Identité API v3 au lieu de API v2.0"
-
-#: ./doc/common/section_cli_keystone_apiv3.xml6(para)
-msgid ""
-"Use the following parameters in combination on any keystone command to "
-"specify which version of the API to use:"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_apiv3.xml11(para)
-msgid ""
-"<parameter>--os-endpoint</parameter>. The endpoint to use instead of the one"
-" in the service catalog. Defaults to <code>env[OS_SERVICE_ENDPOINT]</code>."
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_apiv3.xml15(para)
-msgid ""
-"The <literal>keystone</literal> client detects the version of the API from "
-"this parameter."
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_apiv3.xml19(para)
-msgid ""
-"<parameter>--os-auth_url</parameter>. The Identity Service endpoint to use "
-"for authentication. Defaults to <code>env[OS_AUTH_URL]</code>."
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_apiv3.xml25(para)
-msgid ""
-"<parameter>--os-identity-api-version</parameter>. The Identity Service API "
-"version. Defaults to <code>env[OS_IDENTITY_API_VERSION]</code> or "
-"<literal>2.0</literal>."
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_apiv3.xml31(para)
-msgid "For example, use the following parameters to use API v3:"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_apiv3.xml33(parameter)
-#: ./doc/common/section_cli_keystone_apiv3.xml35(parameter)
-msgid "--os-auth_url"
-msgstr "--os-auth_url"
-
-#: ./doc/common/section_cli_keystone_apiv3.xml33(parameter)
-#: ./doc/common/section_cli_keystone_apiv3.xml35(parameter)
-msgid "--os-identity-api-version"
-msgstr "--os-identity-api-version"
-
-#: ./doc/common/section_cli_keystone_apiv3.xml34(para)
-msgid "Use the following parameters to use API v2.0:"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_trusted-compute-pools.xml45(None)
-#: ./doc/common/section_trusted-compute-pools.xml50(None)
-msgid ""
-"@@image: 'figures/OpenStackTrustedComputePool1.png'; "
-"md5=858fbd6148b927723cea5ad2c88d54bd"
-msgstr "@@image: 'figures/OpenStackTrustedComputePool1.png'; md5=858fbd6148b927723cea5ad2c88d54bd"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_trusted-compute-pools.xml150(None)
-#: ./doc/common/section_trusted-compute-pools.xml155(None)
-msgid ""
-"@@image: 'figures/OpenStackTrustedComputePool2.png'; "
-"md5=077261c595464638c4b3fcc92b6afb9a"
-msgstr "@@image: 'figures/OpenStackTrustedComputePool2.png'; md5=077261c595464638c4b3fcc92b6afb9a"
-
-#: ./doc/common/section_trusted-compute-pools.xml6(title)
-msgid "Trusted compute pools"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml7(para)
-msgid ""
-"Trusted compute pools enable administrators to designate a group of compute "
-"hosts as trusted. These hosts use hardware-based security features, such as "
-"the Intel Trusted Execution Technology (TXT), to provide an additional level"
-" of security. Combined with an external stand-alone, web-based remote "
-"attestation server, cloud providers can ensure that the compute node runs "
-"only software with verified measurements and can ensure a secure cloud "
-"stack."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml13(para)
-msgid ""
-"Using the trusted compute pools, cloud subscribers can request services to "
-"run on verified compute nodes."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml15(para)
-msgid "The remote attestation server performs node verification as follows:"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml19(para)
-msgid "Compute nodes boot with Intel TXT technology enabled."
-msgstr "Les nœuds de calcul sont amorcés avec la technologie Intel TXT activée."
-
-#: ./doc/common/section_trusted-compute-pools.xml23(para)
-msgid "The compute node BIOS, hypervisor, and OS are measured."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml27(para)
-msgid ""
-"Measured data is sent to the attestation server when challenged by the "
-"attestation server."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml31(para)
-msgid ""
-"The attestation server verifies those measurements against a good and known "
-"database to determine node trustworthiness."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml35(para)
-msgid ""
-"A description of how to set up an attestation service is beyond the scope of"
-" this document. For an open source project that you can use to implement an "
-"attestation service, see the <link "
-"href=\"https://github.com/OpenAttestation/OpenAttestation\">Open "
-"Attestation</link> project."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml54(title)
-msgid "Configure Compute to use trusted compute pools"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml57(para)
-msgid ""
-"Enable scheduling support for trusted compute pools by adding the following "
-"lines in the <literal>DEFAULT</literal> section in the "
-"<filename>/etc/nova/nova.conf</filename> file:"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml66(para)
-msgid ""
-"Specify the connection information for your attestation service by adding "
-"the following lines to the <literal>trusted_computing</literal> section in "
-"the <filename>/etc/nova/nova.conf</filename> file:"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml81(term)
-msgid "server"
-msgstr "server"
-
-#: ./doc/common/section_trusted-compute-pools.xml83(para)
-msgid "Host name or IP address of the host that runs the attestation service."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml88(term)
-msgid "port"
-msgstr "port"
-
-#: ./doc/common/section_trusted-compute-pools.xml90(para)
-msgid "HTTPS port for the attestation service."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml94(term)
-msgid "server_ca_file"
-msgstr "server_ca_file "
-
-#: ./doc/common/section_trusted-compute-pools.xml96(para)
-msgid "Certificate file used to verify the attestation server's identity."
-msgstr "Certificat utilisé pour vérifier l'identité du serveur d'attestation. "
-
-#: ./doc/common/section_trusted-compute-pools.xml101(term)
-msgid "api_url"
-msgstr "api_url"
-
-#: ./doc/common/section_trusted-compute-pools.xml103(para)
-msgid "The attestation service's URL path."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml107(term)
-msgid "auth_blob"
-msgstr "auth_blob"
-
-#: ./doc/common/section_trusted-compute-pools.xml109(para)
-msgid "An authentication blob, which is required by the attestation service."
-msgstr "Blob d'authentification, nécessaire au service."
-
-#: ./doc/common/section_trusted-compute-pools.xml117(para)
-msgid ""
-"Restart the <systemitem class=\"service\">nova-compute</systemitem> and "
-"<systemitem class=\"service\">nova-scheduler</systemitem> services."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml124(title)
-#: ./doc/common/section_compute_config-api.xml183(title)
-msgid "Configuration reference"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml125(para)
-msgid ""
-"To customize the trusted compute pools, use the following configuration "
-"option settings:"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml132(title)
-msgid "Specify trusted flavors"
-msgstr "Spécification de variétés [ORIGINAL: flavors] fiables"
-
-#: ./doc/common/section_trusted-compute-pools.xml133(para)
-msgid "To designate hosts as trusted:"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml136(para)
-msgid ""
-"Configure one or more flavors as trusted by using the <placeholder-1/> "
-"command. For example, to set the <literal>m1.tiny</literal> flavor as "
-"trusted:"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml141(para)
-msgid ""
-"Request that your instance be run on a trusted host, by specifying a trusted"
-" flavor when booting the instance. For example:"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml145(title)
-msgid "Trusted compute pool"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-ec2.xml6(title)
-msgid "Configure the EC2 API"
-msgstr "Configurer l’API EC2"
-
-#: ./doc/common/section_compute-configure-ec2.xml7(para)
-msgid ""
-"You can set options in the <filename>nova.conf</filename> configuration file"
-" to control which network address and port the EC2 API listens on, the "
-"formatting of some API responses, and authentication related options."
-msgstr "Vous pouvez utiliser les options de configuration de <filename>nova.conf</filename> pour contrôler à quelle adresse réseau et sur quel port l’API EC2 écoutera, le formatage de certaines réponses API et des options ayant trait à l’authentification."
-
-#: ./doc/common/section_compute-configure-ec2.xml11(para)
-msgid ""
-"To customize these options for OpenStack EC2 API, use the configuration "
-"option settings documented in <xref linkend=\"config_table_nova_ec2\"/>."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml7(title)
-msgid "Features and benefits"
-msgstr "Traits et avantages"
-
-#: ./doc/common/section_objectstorage-features.xml12(th)
-msgid "Features"
-msgstr "Traits"
-
-#: ./doc/common/section_objectstorage-features.xml13(th)
-msgid "Benefits"
-msgstr "Avantages"
-
-#: ./doc/common/section_objectstorage-features.xml18(emphasis)
-msgid "Leverages commodity hardware"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml19(td)
-msgid "No lock-in, lower price/GB."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml22(emphasis)
-msgid "HDD/node failure agnostic"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml23(td)
-msgid "Self-healing, reliable, data redundancy protects from failures."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml27(emphasis)
-msgid "Unlimited storage"
-msgstr "Stockage illimité"
-
-#: ./doc/common/section_objectstorage-features.xml28(td)
-msgid ""
-"Large and flat namespace, highly scalable read/write access, able to serve "
-"content directly from storage system."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml32(emphasis)
-msgid "Multi-dimensional scalability"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml34(td)
-msgid ""
-"Scale-out architecture: Scale vertically and horizontally-distributed "
-"storage. Backs up and archives large amounts of data with linear "
-"performance."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml39(emphasis)
-msgid "Account/container/object structure"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml40(td)
-msgid ""
-"No nesting, not a traditional file system: Optimized for scale, it scales to"
-" multiple petabytes and billions of objects."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml45(emphasis)
-msgid "Built-in replication 3✕ + data redundancy (compared with 2✕ on RAID)"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml48(td)
-msgid ""
-"A configurable number of accounts, containers and object copies for high "
-"availability."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml52(emphasis)
-msgid "Easily add capacity (unlike RAID resize)"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml54(td)
-msgid "Elastic data scaling with ease"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml57(emphasis)
-msgid "No central database"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml58(td)
-msgid "Higher performance, no bottlenecks"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml61(emphasis)
-msgid "RAID not required"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml62(td)
-msgid "Handle many small, random reads and writes efficiently"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml65(emphasis)
-msgid "Built-in management utilities"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml66(td)
-msgid ""
-"Account management: Create, add, verify, and delete users; Container "
-"management: Upload, download, and verify; Monitoring: Capacity, host, "
-"network, log trawling, and cluster health."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml72(emphasis)
-msgid "Drive auditing"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml73(td)
-msgid "Detect drive failures preempting data corruption"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml76(emphasis)
-msgid "Expiring objects"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml77(td)
-msgid ""
-"Users can set an expiration time or a TTL on an object to control access"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml81(emphasis)
-msgid "Direct object access"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml82(td)
-msgid "Enable direct browser access to content, such as for a control panel"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml86(emphasis)
-msgid "Realtime visibility into client requests"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml88(td)
-msgid "Know what users are requesting."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml91(emphasis)
-msgid "Supports S3 API"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml92(td)
-msgid "Utilize tools that were designed for the popular S3 API."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml96(emphasis)
-msgid "Restrict containers per account"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml98(td)
-msgid "Limit access to control usage by user."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml101(emphasis)
-msgid "Support for NetApp, Nexenta, SolidFire"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml103(td)
-msgid "Unified support for block volumes using a variety of storage systems."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml107(emphasis)
-msgid "Snapshot and backup API for block volumes"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml109(td)
-msgid "Data protection and recovery for VM data."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml112(emphasis)
-msgid "Standalone volume API available"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml114(td)
-msgid "Separate endpoint and API for integration with other compute systems."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml118(emphasis)
-msgid "Integration with Compute"
-msgstr "Intégration avec calcul"
-
-#: ./doc/common/section_objectstorage-features.xml120(td)
-msgid ""
-"Fully integrated with Compute for attaching block volumes and reporting on "
-"usage."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml6(title)
-msgid "User management"
-msgstr "Gestion des utilisateurs"
-
-#: ./doc/common/section_keystone-concepts-user-management.xml7(para)
-msgid "The main components of Identity user management are:"
-msgstr "Les trois concepts majeurs de la gestion des utilisateurs sont :"
-
-#: ./doc/common/section_keystone-concepts-user-management.xml10(para)
-msgid ""
-"<emphasis role=\"bold\">User</emphasis>. Represents a human user. Has "
-"associated information such as user name, password, and email. This example "
-"creates a user named <literal>alice</literal>:"
-msgstr "Un <emphasis role=\"bold\">User</emphasis> représente un utilisateur humain, et possède des informations associées telles que le nom d'utilisateur, un mot de passe, et un email. Par exemple, la création de l'utilisateur nommé <literal>alice</literal> :"
-
-#: ./doc/common/section_keystone-concepts-user-management.xml17(para)
-msgid ""
-"<emphasis role=\"bold\">Tenant</emphasis>. A project, group, or "
-"organization. When you make requests to OpenStack services, you must specify"
-" a tenant. For example, if you query the Compute service for a list of "
-"running instances, you get a list of all running instances in the tenant "
-"that you specified in your query. This example creates a tenant named "
-"<literal>acme</literal>:"
-msgstr "Un <emphasis role=\"bold\">Tenant</emphasis> peut être vu comme un projet, groupe, ou une organisation . Chaque fois que vous envoyez une requête aux services OpenStack, vous devez spécifier un ensemble. Par exemple, si vous vous enquérez auprès du service Calcul de la liste des instances en cours, vous recevrez la liste de toutes les instances en cours de l'ensemble spécifié dans votre requête. Cet exemple montre la création de l'ensemble nommé  <literal>acme</literal>: "
-
-#: ./doc/common/section_keystone-concepts-user-management.xml27(para)
-msgid ""
-"Because the term <emphasis>project</emphasis> was used instead of "
-"<emphasis>tenant</emphasis> in earlier versions of OpenStack Compute, some "
-"command-line tools use <literal>--project_id</literal> instead of <literal"
-">--tenant-id</literal> or <literal>--os-tenant-id</literal> to refer to a "
-"tenant ID."
-msgstr "Comme le terme <emphasis>project</emphasis> été utilisé au lieu de <emphasis>tenant</emphasis> dans les versions précédentes de OpenStack Compute, certains outils d'entrée de commande utilisent <literal>--project_id</literal> au lieu de <literal>--tenant-id</literal>]ou<literal>--os-tenant-id</literal>pour faire référence à l'ID d'un ensemble."
-
-#: ./doc/common/section_keystone-concepts-user-management.xml38(para)
-msgid ""
-"<emphasis role=\"bold\">Role</emphasis>. Captures the operations that a user"
-" can perform in a given tenant."
-msgstr "Un  <emphasis role=\"bold\">Role</emphasis> récapitule quelles opérations un utilisateur est en droit d'effectuer dans un ensemble donné. Cet exemple est la création d'un rôle nommé « compute-user » :"
-
-#: ./doc/common/section_keystone-concepts-user-management.xml40(para)
-msgid "This example creates a role named <literal>compute-user</literal>:"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml44(para)
-msgid ""
-"Individual services, such as Compute and the Image Service, assign meaning "
-"to roles. In the Identity Service, a role is simply a name."
-msgstr "C'est aux services individuels tels que le service Calcul et le service Image d'attribuer à ces rôles un sens. Pour le service Identité, un rôle n'est qu'un simple nom."
-
-#: ./doc/common/section_keystone-concepts-user-management.xml51(para)
-msgid ""
-"The Identity Service assigns a tenant and a role to a user. You might assign"
-" the <literal>compute-user</literal> role to the <literal>alice</literal> "
-"user in the <literal>acme</literal> tenant:"
-msgstr "Le service Identité associe un utilisateur à un ensemble et un rôle. Pour continuer nos exemples précédents, nous allons vouloir associer à l'utilisateur <literal>alice</literal> le rôle <literal>compute-user</literal> dans l'ensemble <literal>acme</literal> : "
-
-#: ./doc/common/section_keystone-concepts-user-management.xml74(para)
-msgid ""
-"A user can have different roles in different tenants. For example, Alice "
-"might also have the <literal>admin</literal> role in the "
-"<literal>Cyberdyne</literal> tenant. A user can also have multiple roles in "
-"the same tenant."
-msgstr "Un utilisateur peut se voir attribuer des rôles différents dans des ensembles différents : Par exemple, Alice peut aussi avoir le rôle <literal>admin</literal> dans l'ensemble <literal>Cyberdyne</literal>. On peut aussi attribuer à un individu plusieurs rôles dans le même ensemble. "
-
-#: ./doc/common/section_keystone-concepts-user-management.xml78(para)
-msgid ""
-"The "
-"<filename>/etc/<replaceable>[SERVICE_CODENAME]</replaceable>/policy.json</filename>"
-" file controls the tasks that users can perform for a given service. For "
-"example, <filename>/etc/nova/policy.json</filename> specifies the access "
-"policy for the Compute service, <filename>/etc/glance/policy.json</filename>"
-" specifies the access policy for the Image Service, and "
-"<filename>/etc/keystone/policy.json</filename> specifies the access policy "
-"for the Identity Service."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml88(para)
-msgid ""
-"The default <filename>policy.json</filename> files in the Compute, Identity,"
-" and Image Service recognize only the <literal>admin</literal> role: all "
-"operations that do not require the <literal>admin</literal> role are "
-"accessible by any user that has any role in a tenant."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml93(para)
-msgid ""
-"If you wish to restrict users from performing operations in, say, the "
-"Compute service, you need to create a role in the Identity Service and then "
-"modify <filename>/etc/nova/policy.json</filename> so that this role is "
-"required for Compute operations."
-msgstr "Si vous voulez restreindre les permissions des utilisateurs d'effectuer des opérations dans par exemple le service Calcul, vous devez créer un rôle dans le service Identité, et modifier <filename>/etc/nova/policy.json</filename> pour que ce rôle soit nécessaire afin d'effectuer des opérations de Calcul. "
-
-#: ./doc/common/section_keystone-concepts-user-management.xml99(para)
-msgid ""
-"For example, this line in <filename>/etc/nova/policy.json</filename> "
-"specifies that there are no restrictions on which users can create volumes: "
-"if the user has any role in a tenant, they can create volumes in that "
-"tenant."
-msgstr "Par exemple, cette ligne dans <filename>/etc/nova/policy.json</filename> spécifies qu'il n'y a aucune restriction concernant la création de volumes par les utilisateurs : si l'utilisateur a un rôle quelconque dans un ensemble, il sera capable de créer des volumes dans cet ensemble."
-
-#: ./doc/common/section_keystone-concepts-user-management.xml105(para)
-msgid ""
-"To restrict creation of volumes to users who had the <literal>compute-"
-"user</literal> role in a particular tenant, you would add <literal>\"role"
-":compute-user\"</literal>, like so:"
-msgstr "Si on souhaite restreindre la création de volume aux utilisateurs qui ont le rôle <literal>compute-user</literal> dans un ensemble particulier, il faudrait ajouter <literal>\"role:compute-user\"</literal>, ainsi : "
-
-#: ./doc/common/section_keystone-concepts-user-management.xml110(para)
-msgid ""
-"To restrict all Compute service requests to require this role, the resulting"
-" file would look like:"
-msgstr "Si on souhaite que toutes les requêtes de Calcul soient soumise à la possession de ce rôle, le fichier qu'il en résulterait ressemblerait à ceci : "
-
-#: ./doc/common/section_compute-configure-spice.xml6(title)
-msgid "SPICE console"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-spice.xml7(para)
-msgid ""
-"OpenStack Compute supports VNC consoles to guests. The VNC protocol is "
-"fairly limited, lacking support for multiple monitors, bi-directional audio,"
-" reliable cut-and-paste, video streaming and more. SPICE is a new protocol "
-"that aims to address the limitations in VNC and provide good remote desktop "
-"support."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-spice.xml12(para)
-msgid ""
-"SPICE support in OpenStack Compute shares a similar architecture to the VNC "
-"implementation. The OpenStack dashboard uses a SPICE-HTML5 widget in its "
-"console tab that communicates to the <systemitem class=\"service\">nova-"
-"spicehtml5proxy</systemitem> service by using SPICE-over-websockets. The "
-"<systemitem class=\"service\">nova-spicehtml5proxy</systemitem> service "
-"communicates directly with the hypervisor process by using SPICE."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-spice.xml19(para)
-msgid ""
-"VNC must be explicitly disabled to get access to the SPICE console. Set the "
-"<option>vnc_enabled</option> option to <literal>False</literal> in the "
-"<literal>[DEFAULT]</literal> section to disable the VNC console."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-spice.xml22(para)
-msgid ""
-"Use the following options to configure SPICE as the console for OpenStack "
-"Compute:"
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure.xml6(title)
-msgid "Configure the dashboard"
-msgstr "Configurer le tableau de bord"
-
-#: ./doc/common/section_dashboard-configure.xml8(para)
-msgid "You can configure the dashboard for a simple HTTP deployment."
-msgstr "Vous pouvez configurer le tableau de bord pour un  déploiement HTTP simple."
-
-#: ./doc/common/section_dashboard-configure.xml14(para)
-msgid "Also, you can configure the size of the VNC window in the dashboard."
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-http.xml6(title)
-msgid "Configure the dashboard for HTTP"
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-http.xml8(para)
-msgid ""
-"You can configure the dashboard for a simple HTTP deployment. The standard "
-"installation uses a non-encrypted HTTP channel."
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-http.xml12(para)
-msgid ""
-"Specify the host for your OpenStack Identity Service endpoint in the "
-"<filename>/etc/openstack-dashboard/local_settings.py</filename> file with "
-"the <literal>OPENSTACK_HOST</literal> setting."
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-http.xml17(para)
-msgid "The following example shows this setting:"
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-http.xml19(para)
-msgid ""
-"The service catalog configuration in the Identity Service determines whether"
-" a service appears in the dashboard. For the full listing, see <link "
-"href=\"http://docs.openstack.org/developer/horizon/topics/settings.html\">Horizon"
-" Settings and Configuration</link>."
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-http.xml28(para)
-msgid "Restart Apache http server. For Ubuntu/Debian/SUSE:"
-msgstr "Redémarrer la serveur Apache http. Pour Ubuntu/Debian/SUSE:"
-
-#: ./doc/common/section_dashboard-configure-http.xml30(para)
-msgid "or for Fedora/RHEL/CentOS:"
-msgstr "ou pour Fedora/RHEL/CentOS:"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_dashboard_access.xml89(None)
-msgid ""
-"@@image: 'figures/dashboard-project-tab.png'; "
-"md5=5b192a3d34c9285dbacd875395b8e4cc"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_dashboard_access.xml214(None)
-msgid ""
-"@@image: 'figures/dashboard-admin-tab.png'; "
-"md5=039358c76c549d7d423da5b8aa826435"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml12(title)
-msgid "Log in to the dashboard"
-msgstr "Connectez-vous au tableau de bord"
-
-#: ./doc/common/section_dashboard_access.xml13(para)
-msgid ""
-"The dashboard is available on the node with the <literal>nova-"
-"dashboard</literal> server role."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml17(para)
-msgid ""
-"Ask the cloud operator for the host name or public IP address from which you"
-" can access the dashboard, and for your user name and password."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml22(para)
-msgid "Open a web browser that has JavaScript and cookies enabled."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml25(para)
-msgid ""
-"To use the Virtual Network Computing (VNC) client for the dashboard, your "
-"browser must support HTML5 Canvas and HTML5 WebSockets. The VNC client is "
-"based on noVNC. For details, see <link "
-"href=\"https://github.com/kanaka/noVNC/blob/master/README.md\">noVNC: HTML5 "
-"VNC Client</link>. For a list of supported browsers, see <link "
-"href=\"https://github.com/kanaka/noVNC/wiki/Browser-support\">Browser "
-"support</link>."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml38(para)
-msgid ""
-"In the address bar, enter the host name or IP address for the dashboard."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml40(replaceable)
-msgid "ipAddressOrHostName"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml42(para)
-msgid ""
-"If a certificate warning appears when you try to access the URL for the "
-"first time, a self-signed certificate is in use, which is not considered "
-"trustworthy by default. Verify the certificate or add an exception in the "
-"browser to bypass the warning."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml51(para)
-msgid ""
-"On the <guilabel>Log In</guilabel> page, enter your user name and password, "
-"and click <guibutton>Sign In</guibutton>."
-msgstr "Au page <guilabel>Log In</guilabel>, entrez votre nom d'utilisateur et mot de passe, et cliquez sur <guibutton>Sign In</guibutton>."
-
-#: ./doc/common/section_dashboard_access.xml54(para)
-msgid ""
-"The top of the window displays your user name. You can also access "
-"<guilabel>Settings</guilabel> or sign out of the dashboard."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml61(para)
-msgid ""
-"If you are logged in as an end user, the <link "
-"linkend=\"dashboard_project_tab\">Project</link> tab is displayed."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml65(para)
-msgid ""
-"If you are logged in as an administrator, the <link "
-"linkend=\"dashboard_project_tab\">Project</link> tab and <link "
-"linkend=\"dashboard_admin_tab\">Admin</link> tab are displayed."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml57(para)
-msgid ""
-"The visible tabs and functions in the dashboard depend on the access "
-"permissions, or <emphasis role=\"italic\">roles</emphasis>, of the user you "
-"are logged in as.<placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml75(title)
-msgid "OpenStack dashboardProject tab"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml76(para)
-msgid ""
-"Projects are organizational units in the cloud, and are also known as "
-"tenants or accounts. Each user is a member of one or more projects. Within a"
-" project, a user creates and manages instances."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml80(para)
-msgid ""
-"From the <guilabel>Project</guilabel> tab, you can view and manage the "
-"resources in a selected project, including instances and images. You select "
-"the project from the <guilabel>CURRENT PROJECT</guilabel> list at the top of"
-" the tab."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml85(title)
-msgid "Project tab"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml93(para)
-msgid ""
-"From the <guilabel>Project</guilabel> tab, you can access the following "
-"tabs:"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml100(th)
-#: ./doc/common/section_dashboard_access.xml170(th)
-#: ./doc/common/section_dashboard_access.xml185(th)
-#: ./doc/common/section_dashboard_access.xml192(th)
-#: ./doc/common/section_dashboard_access.xml224(th)
-#: ./doc/common/section_dashboard_access.xml350(th)
-msgid "<placeholder-1/> tab"
-msgstr "<placeholder-1/> tab"
-
-#: ./doc/common/section_dashboard_access.xml105(guilabel)
-#: ./doc/common/section_dashboard_access.xml229(guilabel)
-#: ./doc/common/section_cli_overview.xml7(title)
-msgid "Overview"
-msgstr "Vue d'ensemble"
-
-#: ./doc/common/section_dashboard_access.xml106(para)
-msgid "View reports for the project."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml109(guilabel)
-#: ./doc/common/section_dashboard_access.xml292(guilabel)
-msgid "Instances"
-msgstr "Instances"
-
-#: ./doc/common/section_dashboard_access.xml110(para)
-msgid ""
-"View, launch, create a snapshot from, stop, pause, or reboot instances, or "
-"connect to them through VNC."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml114(guilabel)
-#: ./doc/common/section_dashboard_access.xml119(guilabel)
-#: ./doc/common/section_dashboard_access.xml299(guilabel)
-msgid "Volumes"
-msgstr "Volumes"
-
-#: ./doc/common/section_dashboard_access.xml115(para)
-#: ./doc/common/section_dashboard_access.xml141(para)
-msgid "Use the following tabs to complete these tasks:"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml121(para)
-msgid "View, create, edit, and delete volumes."
-msgstr "Voir, créer, éditer et supprimer des columes."
-
-#: ./doc/common/section_dashboard_access.xml125(guilabel)
-msgid "Volume Snapshots"
-msgstr "Instantanés du volume"
-
-#: ./doc/common/section_dashboard_access.xml127(para)
-msgid "View, create, edit, and delete volume snapshots."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml133(guilabel)
-#: ./doc/common/section_dashboard_access.xml309(guilabel)
-msgid "Images"
-msgstr "Images"
-
-#: ./doc/common/section_dashboard_access.xml134(para)
-msgid ""
-"View images and instance snapshots created by project users, plus any images"
-" that are publicly available. Create, edit, and delete images, and launch "
-"instances from images and snapshots."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml140(guilabel)
-msgid "Access &amp; Security"
-msgstr "Accès et Sécurité"
-
-#: ./doc/common/section_dashboard_access.xml144(guilabel)
-msgid "Security Groups"
-msgstr "Groupes de sécurité"
-
-#: ./doc/common/section_dashboard_access.xml145(para)
-msgid ""
-"View, create, edit, and delete security groups and security group rules."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml150(guilabel)
-msgid "Key Pairs"
-msgstr "Paires de Clefs"
-
-#: ./doc/common/section_dashboard_access.xml151(para)
-msgid "View, create, edit, import, and delete key pairs."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml156(guilabel)
-msgid "Floating IPs"
-msgstr "IP flottantes"
-
-#: ./doc/common/section_dashboard_access.xml158(para)
-msgid "Allocate an IP address to or release it from a project."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml163(guilabel)
-msgid "API Access"
-msgstr "Accès API"
-
-#: ./doc/common/section_dashboard_access.xml164(para)
-msgid "View API endpoints."
-msgstr "Voir des points de terminaison d'API."
-
-#: ./doc/common/section_dashboard_access.xml170(guilabel)
-msgid "Network"
-msgstr "Réseau"
-
-#: ./doc/common/section_dashboard_access.xml173(guilabel)
-msgid "Network Topology"
-msgstr "Topologie du Réseau"
-
-#: ./doc/common/section_dashboard_access.xml174(para)
-msgid "View the network topology."
-msgstr "Voir la topologie du réseau"
-
-#: ./doc/common/section_dashboard_access.xml177(guilabel)
-#: ./doc/common/section_dashboard_access.xml314(guilabel)
-msgid "Networks"
-msgstr "Réseaux"
-
-#: ./doc/common/section_dashboard_access.xml178(para)
-msgid "Create and manage public and private networks."
-msgstr "Créer et gérer les réseaux publics et privés."
-
-#: ./doc/common/section_dashboard_access.xml181(guilabel)
-#: ./doc/common/section_dashboard_access.xml318(guilabel)
-msgid "Routers"
-msgstr "Routeurs"
-
-#: ./doc/common/section_dashboard_access.xml182(para)
-msgid "Create and manage subnets."
-msgstr "Créez et gérez des sous-réseaux."
-
-#: ./doc/common/section_dashboard_access.xml185(guilabel)
-msgid "Object Store"
-msgstr "Stockage d'objet"
-
-#: ./doc/common/section_dashboard_access.xml188(guilabel)
-#: ./doc/common/section_dashboard_access.xml195(guilabel)
-msgid "Containers"
-msgstr "Conteneurs"
-
-#: ./doc/common/section_dashboard_access.xml189(para)
-msgid "Create and manage containers and objects."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml196(para)
-msgid "Use the REST API to orchestrate multiple composite cloud applications."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml203(title)
-msgid "OpenStack dashboardAdmin tab"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml204(para)
-msgid ""
-"Administrative users can use the <guilabel>Admin</guilabel> tab to view "
-"usage and to manage instances, volumes, flavors, images, projects, users, "
-"services, and quotas."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml209(title)
-msgid "Admin tab"
-msgstr "Onglet d'administration"
-
-#: ./doc/common/section_dashboard_access.xml218(para)
-msgid "Access the following categories to complete these tasks:"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml224(guilabel)
-msgid "System Panel"
-msgstr "Gestion Système"
-
-#: ./doc/common/section_dashboard_access.xml230(para)
-msgid "View basic reports."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml233(guilabel)
-msgid "Resource Usage"
-msgstr "Usage de ressource"
-
-#: ./doc/common/section_dashboard_access.xml234(para)
-msgid "Use the following tabs to view the following usages:"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml269(guilabel)
-msgid "Daily Report"
-msgstr "Rapport journalier"
-
-#: ./doc/common/section_dashboard_access.xml271(para)
-msgid "View the daily report."
-msgstr "Voir la rapport journalier."
-
-#: ./doc/common/section_dashboard_access.xml275(guilabel)
-msgid "Stats"
-msgstr "Stats"
-
-#: ./doc/common/section_dashboard_access.xml277(para)
-msgid "View the statistics of all resources."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml283(guilabel)
-msgid "Hypervisors"
-msgstr "Hyperviseurs"
-
-#: ./doc/common/section_dashboard_access.xml284(para)
-msgid "View the hypervisor summary."
-msgstr "Voir le résumé d'hyperviseur."
-
-#: ./doc/common/section_dashboard_access.xml287(guilabel)
-msgid "Host Aggregates"
-msgstr "Agrégations d'hôte."
-
-#: ./doc/common/section_dashboard_access.xml288(para)
-msgid ""
-"View, create, and edit host aggregates. View the list of availability zones."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml293(para)
-msgid ""
-"View, pause, resume, suspend, migrate, soft or hard reboot, and delete "
-"running instances that belong to users of some, but not all, projects. Also,"
-" view the log for an instance or access an instance through VNC."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml300(para)
-msgid "View, create, edit, and delete volumes and volume types."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml305(para)
-msgid ""
-"View, create, edit, view extra specifications for, and delete flavors. A "
-"flavor is size of an instance."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml310(para)
-msgid "View, create, edit properties for, and delete custom images."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml315(para)
-msgid "View, create, edit properties for, and delete networks."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml319(para)
-msgid "View, create, edit properties for, and delete routers."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml322(guilabel)
-msgid "System Info"
-msgstr "Informations Système"
-
-#: ./doc/common/section_dashboard_access.xml323(para)
-msgid "Use the following tabs to view the service information:"
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml326(guilabel)
-msgid "Services"
-msgstr "Services"
-
-#: ./doc/common/section_dashboard_access.xml327(para)
-msgid "View a list of the services."
-msgstr "Voir une liste de toutes les services."
-
-#: ./doc/common/section_dashboard_access.xml331(guilabel)
-msgid "Compute Services"
-msgstr "Services de calcul"
-
-#: ./doc/common/section_dashboard_access.xml332(para)
-msgid "View a list of all Compute services."
-msgstr "Voir une liste de toutes les services calcul."
-
-#: ./doc/common/section_dashboard_access.xml336(guilabel)
-msgid "Network Agents"
-msgstr "Agents réseau."
-
-#: ./doc/common/section_dashboard_access.xml337(para)
-msgid "View the network agents."
-msgstr "Voir les agents réseau."
-
-#: ./doc/common/section_dashboard_access.xml341(guilabel)
-msgid "Default Quotas"
-msgstr "Quotas par défaut"
-
-#: ./doc/common/section_dashboard_access.xml342(para)
-msgid ""
-"View default quota values. Quotas are hard-coded in OpenStack Compute and "
-"define the maximum allowable size and number of resources."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml350(guilabel)
-msgid "Identity Panel"
-msgstr "Gestion des Identités"
-
-#: ./doc/common/section_dashboard_access.xml358(guilabel)
-msgid "Projects"
-msgstr "Projets"
-
-#: ./doc/common/section_dashboard_access.xml359(para)
-msgid "View, create, assign users to, remove users from, and delete projects."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml363(guilabel)
-msgid "Users"
-msgstr "Utilisateurs"
-
-#: ./doc/common/section_dashboard_access.xml364(para)
-msgid "View, create, enable, disable, and delete users."
-msgstr ""
-
-#: ./doc/common/ch_using_openstack_overview.xml7(title)
-msgid ""
-"How can I <phrase audience=\"enduser\">use</phrase><phrase "
-"audience=\"adminuser\">administer</phrase> an OpenStack cloud?"
-msgstr ""
-
-#: ./doc/common/ch_using_openstack_overview.xml11(para)
-msgid ""
-"As an OpenStack cloud end user, you can provision your own resources within "
-"the limits set by administrators."
-msgstr ""
-
-#: ./doc/common/ch_using_openstack_overview.xml14(para)
-msgid ""
-"As an OpenStack cloud administrative user, you can manage tenants, known as "
-"<glossterm baseform=\"project\">projects</glossterm>, users, services, "
-"images, flavors, and quotas."
-msgstr ""
-
-#: ./doc/common/ch_using_openstack_overview.xml18(para)
-msgid ""
-"The examples in this guide show you how to perform tasks by using the "
-"following methods:"
-msgstr ""
-
-#: ./doc/common/ch_using_openstack_overview.xml22(para)
-msgid ""
-"OpenStack dashboard. Use this web-based graphical interface, code named "
-"<link href=\"https://github.com/openstack/horizon/\">horizon</link>, to "
-"view, create, and manage resources<phrase audience=\"adminuser\"> and "
-"services</phrase>."
-msgstr ""
-
-#: ./doc/common/ch_using_openstack_overview.xml30(para)
-msgid ""
-"OpenStack command-line clients. Each core OpenStack project has a command-"
-"line client that you can use to run simple commands to view, create, and "
-"manage resources<phrase audience=\"adminuser\"> and services</phrase> in a "
-"cloud and automate tasks by using scripts."
-msgstr ""
-
-#: ./doc/common/ch_using_openstack_overview.xml38(para)
-msgid "You can modify these examples for your specific use cases."
-msgstr ""
-
-#: ./doc/common/ch_using_openstack_overview.xml40(para)
-msgid ""
-"In addition to these ways of interacting with a cloud, you can access the "
-"OpenStack APIs directly or indirectly through <link "
-"href=\"http://curl.haxx.se/\">cURL</link> commands or open SDKs. You can "
-"automate access or build tools to manage resources and services by using the"
-" native OpenStack APIs or the EC2 compatibility API."
-msgstr ""
-
-#: ./doc/common/ch_using_openstack_overview.xml46(para)
-msgid ""
-"To use the OpenStack APIs, it helps to be familiar with HTTP/1.1, RESTful "
-"web services, the OpenStack services, and JSON or XML data serialization "
-"formats."
-msgstr ""
-
-#: ./doc/common/section_xapi-ami-setup.xml7(title)
-msgid "Prepare for AMI type images"
-msgstr "Préparation pour les images de type AMI"
-
-#: ./doc/common/section_xapi-ami-setup.xml8(para)
-msgid ""
-"To support AMI type images in your OpenStack installation, you must create a"
-" <filename>/boot/guest</filename> directory inside Dom0. The OpenStack VM "
-"extracts the kernel and ramdisk from the AKI and ARI images puts them in "
-"this location."
-msgstr "Dans le but de supporter les images de type AMI dans l'installation d'OpenStack, un répertoire <filename>/boot/guest</filename> doit être créer dans Dom0. Le VM OpenStack va placer le noyau et le ramdisk extraits des images AKI et ARI dans cet emplacement."
-
-#: ./doc/common/section_xapi-ami-setup.xml12(para)
-msgid ""
-"OpenStack maintains the contents of this directory and its size should not "
-"increase during normal operation. However, in case of power failures or "
-"accidental shutdowns, some files might be left over. To prevent these files "
-"from filling the Dom0 disk, set up this directory as a symlink that points "
-"to a subdirectory of the local SR."
-msgstr "Le contenu de ce répertoire sera maintenu par OpenStack, et sa taille ne devra pas augmenter pendant une opération normal. Cependant, en cas de défaillance électrique ou coupure de courant accidentelle, certains fichiers pourront être conservés. Dans le but d'empêcher ces fichiers d'encombrer le disque Dom0, il est recommandé de configurer ce répertoire en tant que liaison symbolique joint à un sous-répertoire du SR local."
-
-#: ./doc/common/section_xapi-ami-setup.xml18(para)
-msgid "Run these commands in Dom0 to achieve this setup:"
-msgstr "Exécutez les commandes suivantes dans Dom0 afin d'achever l'installation mentionnée ci-dessus:"
-
-#: ./doc/common/section_config_format.xml8(title)
-msgid "Configuration file format"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml10(para)
-msgid ""
-"OpenStack uses the <glossterm>INI</glossterm> file format for configuration "
-"files. An INI file is a simple text file that specifies options as "
-"<literal>key=value</literal> pairs, grouped into sections. The "
-"<literal>DEFAULT</literal> section contains most of the configuration "
-"options. Lines starting with a hash sign (<literal>#</literal>) are comment "
-"lines. For example:"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml29(replaceable)
-msgid "KEYSTONE_DBPASS"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml29(replaceable)
-msgid "controller"
-msgstr "controller"
-
-#: ./doc/common/section_config_format.xml32(para)
-msgid ""
-"Options can have different type for values. The comments in the sample "
-"config files always mention these. The following types are used by "
-"OpenStack:"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml39(term)
-msgid "boolean value"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml41(para)
-msgid ""
-"Enables or disables an option. The allowed values are "
-"<literal>true</literal> and <literal>false</literal>."
-msgstr ""
-
-#: ./doc/common/section_config_format.xml51(term)
-msgid "floating point value"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml53(para)
-msgid ""
-"A floating point number like <literal>0.25</literal> or "
-"<literal>1000</literal>."
-msgstr ""
-
-#: ./doc/common/section_config_format.xml62(term)
-msgid "integer value"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml64(para)
-msgid ""
-"An integer number is a number without fractional components, like "
-"<literal>0</literal> or <literal>42</literal>."
-msgstr ""
-
-#: ./doc/common/section_config_format.xml74(term)
-msgid "list value"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml76(para)
-msgid ""
-"Represents values of other types, separated by commas. As an example, the "
-"following sets <option>allowed_rpc_exception_modules</option> to a list "
-"containing the four elements <literal>oslo.messaging.exceptions</literal>, "
-"<literal>nova.exception</literal>, <literal>cinder.exception</literal>, and "
-"<literal>exceptions</literal>:"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml92(term)
-msgid "multi valued"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml94(para)
-msgid ""
-"A multi-valued option is a string value and can be given more than once, all"
-" values will be used."
-msgstr ""
-
-#: ./doc/common/section_config_format.xml105(term)
-msgid "string value"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml107(para)
-msgid "Strings can be optionally enclosed with single or double quotes."
-msgstr ""
-
-#: ./doc/common/section_config_format.xml127(title)
-msgid "Sections"
-msgstr "Sections"
-
-#: ./doc/common/section_config_format.xml134(literal)
-#: ./doc/common/tables/keystone-debug.xml19(th)
-#: ./doc/common/tables/glance-policy.xml19(th)
-#: ./doc/common/tables/nova-ipv6.xml19(th)
-#: ./doc/common/tables/cinder-eqlx.xml19(th)
-#: ./doc/common/tables/nova-rpc_all.xml19(th)
-#: ./doc/common/tables/glance-qpid.xml19(th)
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml7(literal)
-#: ./doc/common/tables/nova-volumes.xml19(th)
-#: ./doc/common/tables/glance-gridfs.xml19(th)
-#: ./doc/common/tables/glance-filesystem.xml19(th)
-#: ./doc/common/tables/heat-redis.xml19(th)
-#: ./doc/common/tables/trove-logging.xml19(th)
-#: ./doc/common/tables/cinder-storage_gpfs.xml19(th)
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml19(th)
-#: ./doc/common/tables/nova-ca.xml19(th)
-#: ./doc/common/tables/cinder-huawei.xml19(th)
-#: ./doc/common/tables/keystone-qpid.xml19(th)
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml19(th)
-#: ./doc/common/tables/nova-glance.xml19(th)
-#: ./doc/common/tables/neutron-dhcp_agent.xml19(th)
-#: ./doc/common/tables/nova-neutron.xml19(th)
-#: ./doc/common/tables/cinder-backups_ceph.xml19(th)
-#: ./doc/common/tables/nova-metadata.xml19(th)
-#: ./doc/common/tables/glance-s3.xml19(th)
-#: ./doc/common/tables/glance-auth_token.xml19(th)
-#: ./doc/common/tables/neutron-kombu.xml19(th)
-#: ./doc/common/tables/trove-qpid.xml19(th)
-#: ./doc/common/tables/trove-compute.xml19(th)
-#: ./doc/common/tables/trove-nova.xml19(th)
-#: ./doc/common/tables/cinder-block-device.xml19(th)
-#: ./doc/common/tables/cinder-zones.xml19(th)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml19(th)
-#: ./doc/common/tables/neutron-common.xml19(th)
-#: ./doc/common/tables/neutron-compute.xml19(th)
-#: ./doc/common/tables/heat-rpc.xml19(th)
-#: ./doc/common/tables/neutron-openvswitch_agent.xml19(th)
-#: ./doc/common/tables/cinder-compute.xml19(th)
-#: ./doc/common/tables/cinder-lvm.xml19(th)
-#: ./doc/common/tables/cinder-storage_nfs.xml19(th)
-#: ./doc/common/tables/heat-cfn_api.xml19(th)
-#: ./doc/common/tables/nova-hypervisor.xml19(th)
-#: ./doc/common/tables/trove-rabbitmq.xml19(th)
-#: ./doc/common/tables/trove-api.xml19(th)
-#: ./doc/common/tables/cinder-quota.xml19(th)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml7(literal)
-#: ./doc/common/tables/nova-console.xml19(th)
-#: ./doc/common/tables/heat-clients.xml19(th)
-#: ./doc/common/tables/heat-notification.xml19(th)
-#: ./doc/common/tables/nova-common.xml19(th)
-#: ./doc/common/tables/glance-zmq.xml19(th)
-#: ./doc/common/tables/neutron-metering_agent.xml19(th)
-#: ./doc/common/tables/trove-taskmanager.xml19(th)
-#: ./doc/common/tables/keystone-zeromq.xml19(th)
-#: ./doc/common/tables/neutron-api.xml19(th)
-#: ./doc/common/tables/ceilometer-redis.xml19(th)
-#: ./doc/common/tables/ceilometer-swift.xml19(th)
-#: ./doc/common/tables/cinder-hplefthand.xml19(th)
-#: ./doc/common/tables/heat-qpid.xml19(th)
-#: ./doc/common/tables/nova-testing.xml19(th)
-#: ./doc/common/tables/cinder-backups.xml19(th)
-#: ./doc/common/tables/neutron-ml2_ofa.xml19(th)
-#: ./doc/common/tables/trove-debug.xml19(th)
-#: ./doc/common/tables/nova-s3.xml19(th)
-#: ./doc/common/tables/cinder-rpc.xml19(th)
-#: ./doc/common/tables/cinder-api.xml19(th)
-#: ./doc/common/tables/cinder-windows.xml19(th)
-#: ./doc/common/tables/glance-vmware.xml19(th)
-#: ./doc/common/tables/trove-backup.xml19(th)
-#: ./doc/common/tables/cinder-san.xml19(th)
-#: ./doc/common/tables/keystone-rpc.xml19(th)
-#: ./doc/common/tables/nova-db.xml19(th)
-#: ./doc/common/tables/glance-logging.xml19(th)
-#: ./doc/common/tables/cinder-zoning.xml19(th)
-#: ./doc/common/tables/glance-wsgi.xml19(th)
-#: ./doc/common/tables/nova-periodic.xml19(th)
-#: ./doc/common/tables/cinder-images.xml19(th)
-#: ./doc/common/tables/trove-swift.xml19(th)
-#: ./doc/common/tables/cinder-auth_token.xml19(th)
-#: ./doc/common/tables/heat-crypt.xml19(th)
-#: ./doc/common/tables/neutron-wsgi.xml19(th)
-#: ./doc/common/tables/neutron-scheduler.xml19(th)
-#: ./doc/common/tables/keystone-security.xml19(th)
-#: ./doc/common/tables/glance-rbd.xml19(th)
-#: ./doc/common/tables/heat-rabbitmq.xml19(th)
-#: ./doc/common/tables/ceilometer-logging.xml19(th)
-#: ./doc/common/tables/neutron-metadata.xml19(th)
-#: ./doc/common/tables/glance-redis.xml19(th)
-#: ./doc/common/tables/cinder-hp3par.xml19(th)
-#: ./doc/common/tables/cinder-storage_ceph.xml19(th)
-#: ./doc/common/tables/nova-livemigration.xml19(th)
-#: ./doc/common/tables/nova-ldap.xml19(th)
-#: ./doc/common/tables/nova-fping.xml19(th)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml19(th)
-#: ./doc/common/tables/nova-ec2.xml19(th)
-#: ./doc/common/tables/trove-zeromq.xml19(th)
-#: ./doc/common/tables/heat-database.xml19(th)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml7(literal)
-#: ./doc/common/tables/cinder-rootwrap.xml19(th)
-#: ./doc/common/tables/ceilometer-database.xml19(th)
-#: ./doc/common/tables/heat-debug.xml19(th)
-#: ./doc/common/tables/cinder-nexenta_nfs.xml19(th)
-#: ./doc/common/tables/trove-auth_token.xml19(th)
-#: ./doc/common/tables/heat-waitcondition_api.xml19(th)
-#: ./doc/common/tables/nova-policy.xml19(th)
-#: ./doc/common/tables/keystone-amqp.xml19(th)
-#: ./doc/common/tables/neutron-logging.xml19(th)
-#: ./doc/common/tables/glance-rpc.xml19(th)
-#: ./doc/common/tables/nova-authentication.xml19(th)
-#: ./doc/common/tables/cinder-vmware.xml19(th)
-#: ./doc/common/tables/glance-sheepdog.xml19(th)
-#: ./doc/common/tables/heat-logging.xml19(th)
-#: ./doc/common/tables/keystone-notification.xml19(th)
-#: ./doc/common/tables/neutron-qpid.xml19(th)
-#: ./doc/common/tables/glance-swift.xml19(th)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml7(literal)
-#: ./doc/common/tables/nova-libvirt.xml19(th)
-#: ./doc/common/tables/neutron-lbaas.xml19(th)
-#: ./doc/common/tables/cinder-backups_swift.xml19(th)
-#: ./doc/common/tables/ceilometer-rpc.xml19(th)
-#: ./doc/common/tables/heat-loadbalancer.xml19(th)
-#: ./doc/common/tables/heat-cloudwatch_api.xml19(th)
-#: ./doc/common/tables/nova-pci.xml19(th)
-#: ./doc/common/tables/glance-imagecache.xml19(th)
-#: ./doc/common/tables/trove-quota.xml19(th)
-#: ./doc/common/tables/cinder-storage.xml19(th)
-#: ./doc/common/tables/cinder-nas.xml19(th)
-#: ./doc/common/tables/nova-vpn.xml19(th)
-#: ./doc/common/tables/nova-wsgi.xml19(th)
-#: ./doc/common/tables/cinder-storage_glusterfs.xml19(th)
-#: ./doc/common/tables/nova-availabilityzones.xml19(th)
-#: ./doc/common/tables/heat-zeromq.xml19(th)
-#: ./doc/common/tables/nova-vnc.xml19(th)
-#: ./doc/common/tables/keystone-logging.xml19(th)
-#: ./doc/common/tables/neutron-l3_agent.xml19(th)
-#: ./doc/common/tables/cinder-coraid.xml19(th)
-#: ./doc/common/tables/nova-logging.xml19(th)
-#: ./doc/common/tables/nova-xen.xml19(th)
-#: ./doc/common/tables/ceilometer-collector.xml19(th)
-#: ./doc/common/tables/keystone-ec2.xml19(th)
-#: ./doc/common/tables/ceilometer-api.xml19(th)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml19(th)
-#: ./doc/common/tables/glance-common.xml19(th)
-#: ./doc/common/tables/nova-network.xml19(th)
-#: ./doc/common/tables/cinder-scality.xml19(th)
-#: ./doc/common/tables/neutron-notifier.xml19(th)
-#: ./doc/common/tables/cinder-common.xml19(th)
-#: ./doc/common/tables/nova-configdrive.xml19(th)
-#: ./doc/common/tables/cinder-database.xml19(th)
-#: ./doc/common/tables/neutron-rpc.xml19(th)
-#: ./doc/common/tables/trove-volume.xml19(th)
-#: ./doc/common/tables/nova-zeromq.xml19(th)
-#: ./doc/common/tables/glance-testing.xml19(th)
-#: ./doc/common/tables/glance-registry.xml19(th)
-#: ./doc/common/tables/glance-amqp.xml19(th)
-#: ./doc/common/tables/trove-database.xml19(th)
-#: ./doc/common/tables/heat-clients_backends.xml19(th)
-#: ./doc/common/tables/heat-amqp.xml19(th)
-#: ./doc/common/tables/cinder-hpmsa.xml19(th)
-#: ./doc/common/tables/cinder-emc.xml19(th)
-#: ./doc/common/tables/glance-rabbitmq.xml19(th)
-#: ./doc/common/tables/cinder-backups_tsm.xml19(th)
-#: ./doc/common/tables/nova-qpid.xml19(th)
-#: ./doc/common/tables/trove-rpc.xml19(th)
-#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml7(literal)
-#: ./doc/common/tables/ceilometer-qpid.xml19(th)
-#: ./doc/common/tables/neutron-zeromq.xml19(th)
-#: ./doc/common/tables/neutron-agent.xml19(th)
-#: ./doc/common/tables/neutron-policy.xml19(th)
-#: ./doc/common/tables/neutron-rootwrap.xml19(th)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml7(literal)
-#: ./doc/common/tables/trove-common.xml19(th)
-#: ./doc/common/tables/heat-api.xml19(th)
-#: ./doc/common/tables/ceilometer-amqp.xml19(th)
-#: ./doc/common/tables/keystone-auth_token.xml19(th)
-#: ./doc/common/tables/neutron-redis.xml19(th)
-#: ./doc/common/tables/neutron-ssl.xml19(th)
-#: ./doc/common/tables/ceilometer-exchange.xml19(th)
-#: ./doc/common/tables/ceilometer-common.xml19(th)
-#: ./doc/common/tables/keystone-misc.xml19(th)
-#: ./doc/common/tables/nova-scheduling.xml19(th)
-#: ./doc/common/tables/ceilometer-auth.xml19(th)
-#: ./doc/common/tables/trove-dns.xml19(th)
-#: ./doc/common/tables/neutron-db.xml19(th)
-#: ./doc/common/tables/keystone-redis.xml19(th)
-#: ./doc/common/tables/heat-auth_token.xml19(th)
-#: ./doc/common/tables/cinder-xiv.xml19(th)
-#: ./doc/common/tables/cinder-hds-hus.xml19(th)
-#: ./doc/common/tables/neutron-rabbitmq.xml19(th)
-#: ./doc/common/tables/keystone-policy.xml19(th)
-#: ./doc/common/tables/cinder-auth.xml19(th)
-#: ./doc/common/tables/nova-kombu.xml19(th)
-#: ./doc/common/tables/heat-quota.xml19(th)
-#: ./doc/common/tables/neutron-auth_token.xml19(th)
-#: ./doc/common/tables/cinder-storwize.xml19(th)
-#: ./doc/common/tables/nova-rootwrap.xml19(th)
-#: ./doc/common/tables/cinder-solidfire.xml19(th)
-#: ./doc/common/tables/glance-ssl.xml19(th)
-#: ./doc/common/tables/heat-metadata_api.xml19(th)
-#: ./doc/common/tables/neutron-vmware.xml19(th)
-#: ./doc/common/tables/nova-api.xml19(th)
-#: ./doc/common/tables/glance-matchmaker.xml19(th)
-#: ./doc/common/tables/cinder-san-solaris.xml19(th)
-#: ./doc/common/tables/trove-heat.xml19(th)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml19(th)
-#: ./doc/common/tables/neutron-quotas.xml19(th)
-#: ./doc/common/tables/nova-rpc.xml19(th)
-#: ./doc/common/tables/trove-guestagent.xml19(th)
-#: ./doc/common/tables/keystone-rabbit.xml19(th)
-#: ./doc/common/tables/glance-api.xml19(th)
-#: ./doc/common/tables/cinder-scheduler.xml19(th)
-#: ./doc/common/tables/keystone-api.xml19(th)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml19(th)
-#: ./doc/common/tables/neutron-testing.xml19(th)
-#: ./doc/common/tables/glance-cinder.xml19(th)
-#: ./doc/common/tables/nova-redis.xml19(th)
-#: ./doc/common/tables/ceilometer-inspector.xml19(th)
-#: ./doc/common/tables/nova-rabbitmq.xml19(th)
-#: ./doc/common/tables/heat-common.xml19(th)
-#: ./doc/common/tables/cinder-zadara.xml19(th)
-#: ./doc/common/tables/nova-quota.xml19(th)
-#: ./doc/common/tables/nova-conductor.xml19(th)
-#: ./doc/common/tables/nova-compute.xml19(th)
-#: ./doc/common/tables/cinder-storage_xen.xml19(th)
-#: ./doc/common/tables/trove-amqp.xml19(th)
-#: ./doc/common/tables/nova-xvpnvncproxy.xml19(th)
-msgid "[DEFAULT]"
-msgstr "[DEFAULT]"
-
-#: ./doc/common/section_config_format.xml136(para)
-msgid ""
-"Contains most configuration options. If the documentation for a "
-"configuration option does not specify its section, assume that it appears in"
-" this section."
-msgstr "Presque toutes les options de configuration sont organisées dans cette section. Si la documentation concernant une option de configuration ne stipule pas cette section, il faudra supposer qu'elle concernera celle-ci. "
-
-#: ./doc/common/section_config_format.xml145(literal)
-#: ./doc/common/tables/nova-db.xml33(th)
-#: ./doc/common/tables/heat-database.xml34(th)
-#: ./doc/common/tables/ceilometer-database.xml38(th)
-#: ./doc/common/tables/cinder-storage.xml134(th)
-#: ./doc/common/tables/cinder-common.xml226(th)
-#: ./doc/common/tables/cinder-connection.xml19(th)
-#: ./doc/common/tables/neutron-db.xml30(th)
-#: ./doc/common/tables/keystone-database.xml19(th)
-#: ./doc/common/tables/glance-db.xml19(th)
-msgid "[database]"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml147(para)
-msgid ""
-"Configuration options for the database that stores the state of the "
-"OpenStack service."
-msgstr ""
-
-#: ./doc/common/section_config_format.xml128(para)
-msgid ""
-"Configuration options are grouped by section. Most configuration file "
-"supports at least the following sections: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml158(title)
-msgid "Substitution"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml160(para)
-msgid ""
-"The configuration file supports variable substitution. After you set a "
-"configuration option, it can be referenced in later configuration values "
-"when you precede it with a <literal>$</literal>, like "
-"<literal>$OPTION</literal>."
-msgstr ""
-
-#: ./doc/common/section_config_format.xml167(para)
-msgid ""
-"The following example uses the values of <literal>rabbit_host</literal> and "
-"<literal>rabbit_port</literal> to define the value of the "
-"<literal>rabbit_hosts</literal> option, in this case as "
-"<literal>controller:5672</literal>."
-msgstr ""
-
-#: ./doc/common/section_config_format.xml185(para)
-msgid ""
-"To avoid substitution, use <literal>$$</literal>, it is replaced by a single"
-" <literal>$</literal>. For example, if your LDAP DNS password is "
-"<literal>$xkj432</literal>, specify it, as follows: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml191(para)
-msgid ""
-"The code uses the Python "
-"<literal>string.Template.safe_substitute()</literal> method to implement "
-"variable substitution. For more details on how variable substitution is "
-"resolved, see <link href=\"http://docs.python.org/2/library/string.html"
-"#template-strings\">http://docs.python.org/2/library/string.html#template-"
-"strings</link> and <link "
-"href=\"http://www.python.org/dev/peps/pep-0292/\">PEP 292</link>."
-msgstr ""
-
-#: ./doc/common/section_config_format.xml204(title)
-msgid "Whitespace"
-msgstr "Whitespace"
-
-#: ./doc/common/section_config_format.xml205(para)
-msgid ""
-"To include whitespace in a configuration value, use a quoted string. For "
-"example:"
-msgstr "Pour insérer un espace dans une valeur de configuration, utiliser une chaîne entre guillement. Par exemple"
-
-#: ./doc/common/section_config_format.xml211(title)
-msgid "Define an alternate location for a config file"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml212(para)
-msgid ""
-"Most services and the and the <placeholder-1/> command-line clients load the"
-" configuration file. To define an alternate location for the configuration "
-"file, pass the <parameter>--config-file "
-"<replaceable>CONFIG_FILE</replaceable></parameter> parameter when you start "
-"a service or call a <placeholder-2/> command."
-msgstr ""
-
-#: ./doc/common/section_about-object-storage.xml8(para)
-msgid ""
-"Object Storage is a robust, highly scalable and fault tolerant storage "
-"platform for unstructured data such as objects. Objects are stored bits, "
-"accessed through a RESTful, HTTP-based interface. You cannot access data at "
-"the block or file level. Object Storage is commonly used to archive and back"
-" up data, with use cases in virtual machine image, photo, video and music "
-"storage."
-msgstr ""
-
-#: ./doc/common/section_about-object-storage.xml15(para)
-msgid ""
-"Object Storage provides a high degree of availability, throughput, and "
-"performance with its scale out architecture. Each object is replicated "
-"across multiple servers, residing within the same data center or across data"
-" centers, which mitigates the risk of network and hardware failure. In the "
-"event of hardware failure, Object Storage will automatically copy objects to"
-" a new location to ensure that there are always three copies available. "
-"Object Storage is an eventually consistent distributed storage platform; it "
-"sacrifices consistency for maximum availability and partition tolerance. "
-"Object Storage enables you to create a reliable platform by using commodity "
-"hardware and inexpensive storage."
-msgstr ""
-
-#: ./doc/common/section_about-object-storage.xml27(para)
-msgid ""
-"For more information, review the key concepts in the developer documentation"
-" at <link "
-"href=\"http://docs.openstack.org/developer/swift/\">docs.openstack.org/developer/swift/</link>."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-assignments.xml6(title)
-msgid "Separate role authorization and user authentication"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-assignments.xml7(para)
-msgid ""
-"When you configure the Identity service to use an LDAP back end, you can "
-"split authentication and authorization using the "
-"<emphasis>Assignments</emphasis> feature."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-assignments.xml10(para)
-msgid ""
-"The Assignments feature enables administrators to manage project role "
-"authorization using the Identity service's own SQL database, while still "
-"providing user authentication through the LDAP directory."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-assignments.xml14(para)
-msgid "To configure this:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-assignments.xml16(title)
-msgid ""
-"Separating role authorization and user authentication through Assignments"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-assignments.xml19(para)
-msgid ""
-"Configure the Identity service to authenticate users through the LDAP "
-"driver. To do so, first find the <literal>[identity]</literal> section in "
-"the <filename>/etc/keystone/keystone.conf</filename> configuration file. "
-"Then, set the <literal>driver</literal> configuration key in that section to"
-" <literal>keystone.identity.backends.ldap.Identity</literal>:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-assignments.xml30(para)
-msgid ""
-"Next, enable the Assignment driver. To do so, find the "
-"<literal>[assignment]</literal> section in the "
-"<filename>/etc/keystone/keystone.conf</filename> configuration file. Then, "
-"set the <literal>driver</literal> configuration key in that section to "
-"<literal>keystone.assignment.backends.sql.Assignment</literal>:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-assignments.xml41(para)
-msgid ""
-"On distributions that include <application>openstack-config</application>, "
-"you can configure both drivers by running the following commands instead:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml11(title)
-msgid "Manage volumes"
-msgstr "Gérer les volumes"
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml12(para)
-msgid ""
-"A volume is a detachable block storage device, similar to a USB hard drive. "
-"You can attach a volume to only one instance. To create and manage volumes, "
-"you use a combination of <placeholder-1/> and <placeholder-2/> client "
-"commands."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml16(title)
-msgid "Migrate a volume"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml17(para)
-msgid ""
-"As an administrator, you can migrate a volume with its data from one "
-"location to another in a manner that is transparent to users and workloads. "
-"You can migrate only detached volumes with no snapshots."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml21(para)
-msgid "Possible use cases for data migration include:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml24(para)
-msgid ""
-"Bring down a physical storage device for maintenance without disrupting "
-"workloads."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml28(para)
-msgid "Modify the properties of a volume."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml31(para)
-msgid "Free up space in a thinly-provisioned back end."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml35(para)
-msgid ""
-"Migrate a volume with the <placeholder-1/> command, as shown in the "
-"following example:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml36(replaceable)
-#: ./doc/common/section_cli_cinder_manage_volumes.xml274(replaceable)
-msgid "volumeID"
-msgstr "volumeID"
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml36(replaceable)
-msgid "destinationHost"
-msgstr "destinationHost"
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml36(replaceable)
-msgid "True|False"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml37(para)
-msgid ""
-"In this example, <literal>--force-host-copy=True</literal> forces the "
-"generic host-based migration mechanism and bypasses any driver "
-"optimizations."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml40(para)
-msgid ""
-"If the volume is in use or has snapshots, the specified host destination "
-"cannot accept the volume. If the user is not an administrator, the migration"
-" fails."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml45(title)
-msgid "Create a volume"
-msgstr "Créer un volume"
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml46(para)
-msgid "This example creates a my-new-volume volume based on an image."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml49(para)
-msgid ""
-"List images, and note the ID of the image that you want to use for your "
-"volume:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml62(para)
-msgid ""
-"List the availability zones, and note the ID of the availability zone in "
-"which you want to create your volume:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml81(para)
-msgid ""
-"Create a volume with 8GB of space, and specify the availability zone and "
-"image:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml103(para)
-msgid ""
-"To verify that your volume was created successfully, list the available "
-"volumes:"
-msgstr "Pour vérifier que votre volume a été bien créé, listez les volumes disponibles:"
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml112(para)
-msgid ""
-"If your volume was created successfully, its status is "
-"<literal>available</literal>. If its status is <literal>error</literal>, you"
-" might have exceeded your quota."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml120(title)
-msgid "Attach a volume to an instance"
-msgstr "Joindre un volume à l'instance"
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml123(para)
-msgid ""
-"Attach your volume to a server, specifying the server ID and the volume ID:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml133(para)
-msgid "Note the ID of your volume."
-msgstr "Notez l'identité de votre volume."
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml136(para)
-msgid "Show information for your volume:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml138(para)
-msgid ""
-"The output shows that the volume is attached to the server with ID <literal"
-">84c6e57d-a6b1-44b6-81eb-fcb36afd31b5</literal>, is in the nova availability"
-" zone, and is bootable."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml165(title)
-msgid "Resize a volume"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml168(para)
-msgid "To resize your volume, you must first detach it from the server."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml170(para)
-msgid ""
-"To detach the volume from your server, pass the server ID and volume ID to "
-"the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml172(para)
-#: ./doc/common/section_cli_cinder_manage_volumes.xml191(para)
-msgid "The <placeholder-1/> command does not return any output."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml184(para)
-msgid "Note that the volume is now available."
-msgstr "Notez que le volume est maintenant disponible."
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml187(para)
-msgid ""
-"Resize the volume by passing the volume ID and the new size (a value greater"
-" than the old one) as parameters:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml197(title)
-msgid "Delete a volume"
-msgstr "Supprimez un volume"
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml200(para)
-msgid "To delete your volume, you must first detach it from the server."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml202(para)
-msgid ""
-"To detach the volume from your server and check for the list of existing "
-"volumes, see steps 1 and 2 in <xref linkend=\"cli_extend_volumes\"/>."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml206(para)
-msgid "Delete the volume using either the volume name or ID:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml208(para)
-msgid "The delete command does not return any output."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml212(para)
-msgid ""
-"List the volumes again, and note that the status of your volume is "
-"<literal>deleting</literal>:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml222(para)
-msgid ""
-"When the volume is fully deleted, it disappears from the list of volumes:"
-msgstr "Quand le volume a été complètement supprimé, il ne s'affiche plus dans la liste des volumes: "
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml234(title)
-msgid "Transfer a volume"
-msgstr "Transférer un volume"
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml235(para)
-msgid ""
-"You can transfer a volume from one owner to another by using the "
-"<placeholder-1/> commands. The volume donor, or original owner, creates a "
-"transfer request and sends the created transfer ID and authorization key to "
-"the volume recipient. The volume recipient, or new owner, accepts the "
-"transfer by using the ID and key."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml243(para)
-msgid ""
-"The procedure for volume transfer is intended for tenants (both the volume "
-"donor and recipient) within the same cloud."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml245(para)
-msgid "Use cases include:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml248(para)
-msgid ""
-"Create a custom bootable volume or a volume with a large data set and "
-"transfer it to a customer."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml251(para)
-msgid ""
-"For bulk import of data to the cloud, the data ingress system creates a new "
-"Block Storage volume, copies data from the physical device, and transfers "
-"device ownership to the end user."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml258(title)
-msgid "Create a volume transfer request"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml261(para)
-msgid "While logged in as the volume donor, list the available volumes:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml271(para)
-msgid ""
-"As the volume donor, request a volume transfer authorization code for a "
-"specific volume:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml275(para)
-msgid ""
-"The volume must be in an <literal>available</literal> state or the request "
-"will be denied. If the transfer request is valid in the database (that is, "
-"it has not expired or been deleted), the volume is placed in an "
-"<literal>awaiting transfer</literal> state. For example:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml279(para)
-msgid ""
-"The output shows the volume transfer ID in the <literal>id</literal> row and"
-" the authorization key."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml291(para)
-msgid ""
-"Optionally, you can specify a name for the transfer by using the <code"
-">--display-name <replaceable>displayName</replaceable></code> parameter."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml299(para)
-msgid ""
-"Send the volume transfer ID and authorization key to the new owner (for "
-"example, by email)."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml304(para)
-msgid "View pending transfers:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml313(para)
-msgid ""
-"After the volume recipient, or new owner, accepts the transfer, you can see "
-"that the transfer is no longer available:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml325(title)
-msgid "Accept a volume transfer request"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml328(para)
-msgid ""
-"As the volume recipient, you must first obtain the transfer ID and "
-"authorization key from the original owner."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml333(para)
-msgid "Display the transfer request details by using the ID:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml334(replaceable)
-#: ./doc/common/section_cli_cinder_manage_volumes.xml348(replaceable)
-#: ./doc/common/section_cli_cinder_manage_volumes.xml392(replaceable)
-msgid "transferID"
-msgstr "transferID"
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml347(para)
-msgid "Accept the request:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml348(replaceable)
-msgid "authKey"
-msgstr "authKey"
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml359(para)
-msgid ""
-"If you do not have a sufficient quota for the transfer, the transfer is "
-"refused."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml367(title)
-msgid "Delete a volume transfer"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml371(para)
-msgid "List available volumes and their statuses:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml382(para)
-msgid "Find the matching transfer ID:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml391(para)
-msgid "Delete the volume:"
-msgstr "Supprimez le volume:"
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml397(para)
-msgid ""
-"Verify that transfer list is now empty and that the volume is again "
-"available for transfer:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml6(title)
-msgid "Show usage statistics for hosts and instances"
-msgstr "Afficher les statistiques d'utilisation des hôtes et des instances"
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml7(para)
-msgid ""
-"You can show basic statistics on resource usage for hosts and instances."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml10(para)
-msgid ""
-"For more sophisticated monitoring, see the <link "
-"href=\"https://launchpad.net/ceilometer\">ceilometer</link> project. You can"
-" also use tools, such as <link href=\"http://ganglia.info/\">Ganglia</link> "
-"or <link href=\"http://graphite.wikidot.com/\">Graphite</link>, to gather "
-"more detailed data."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml20(title)
-msgid "Show host usage statistics"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml21(para)
-msgid ""
-"The following examples show the host usage statistics for a host called "
-"<filename>devstack</filename>."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml25(para)
-msgid "List the hosts and the nova-related services that run on them:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml37(para)
-msgid ""
-"Get a summary of resource usage of all of the instances running on the host:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml49(para)
-msgid ""
-"The <literal>cpu</literal> column shows the sum of the virtual CPUs for "
-"instances running on the host."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml51(para)
-msgid ""
-"The <literal>memory_mb</literal> column shows the sum of the memory (in MB) "
-"allocated to the instances that run on the host."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml54(para)
-msgid ""
-"The <literal>disk_gb</literal> column shows the sum of the root and "
-"ephemeral disk sizes (in GB) of the instances that run on the host."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml57(para)
-msgid ""
-"The row that has the value <literal>used_now</literal> in the "
-"<literal>PROJECT</literal> column shows the sum of the resources allocated "
-"to the instances that run on the host, plus the resources allocated to the "
-"virtual machine of the host itself."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml62(para)
-msgid ""
-"The row that has the value <literal>used_max</literal> row in the "
-"<literal>PROJECT</literal> column shows the sum of the resources allocated "
-"to the instances that run on the host."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml68(para)
-msgid ""
-"These values are computed by using information about the flavors of the "
-"instances that run on the hosts. This command does not query the CPU usage, "
-"memory usage, or hard disk usage of the physical host."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml75(title)
-msgid "Show instance usage statistics"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml77(para)
-msgid "Get CPU, memory, I/O, and network statistics for an instance."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml79(para)
-msgid "List instances:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml87(para)
-msgid "Get diagnostic statistics:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml108(para)
-msgid "Get summary statistics for each tenant:"
-msgstr "obtenir des statistiques sommaires pour chaque [original]tenant[/original] :"
-
-#: ./doc/common/ch_cli_glance_commands.xml11(title)
-msgid "Image Service command-line client"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml12(para)
-msgid ""
-"The <placeholder-1/> client is the command-line interface (CLI) for the "
-"OpenStack Image Service API and its extensions. This chapter documents "
-"<placeholder-2/> version 0.12.0."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml22(title)
-msgid "glance usage"
-msgstr "l'utilisation de glance"
-
-#: ./doc/common/ch_cli_glance_commands.xml43(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use image-create instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml52(emphasis)
-#: ./doc/common/ch_cli_glance_commands.xml180(emphasis)
-msgid "DEPRECATED!"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml59(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use image-delete instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml67(para)
-#: ./doc/common/ch_cli_glance_commands.xml131(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use image-list instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml75(para)
-#: ./doc/common/ch_cli_glance_commands.xml524(para)
-msgid "Create a new image."
-msgstr "Créer une nouvelle image."
-
-#: ./doc/common/ch_cli_glance_commands.xml91(para)
-msgid "Download a specific image."
-msgstr "Télécharger une image spécifique."
-
-#: ./doc/common/ch_cli_glance_commands.xml99(para)
-#: ./doc/common/ch_cli_glance_commands.xml715(para)
-msgid "List images you can access."
-msgstr "Listez les images auxquelles vous pouvez accéder."
-
-#: ./doc/common/ch_cli_glance_commands.xml107(para)
-#: ./doc/common/ch_cli_glance_commands.xml163(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use member-list instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml115(para)
-#: ./doc/common/ch_cli_glance_commands.xml848(para)
-msgid "Describe a specific image."
-msgstr "Décrire une image spécifique."
-
-#: ./doc/common/ch_cli_glance_commands.xml123(para)
-#: ./doc/common/ch_cli_glance_commands.xml886(para)
-msgid "Update a specific image."
-msgstr "Mettre à jour une image spécifique."
-
-#: ./doc/common/ch_cli_glance_commands.xml139(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use member-create instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml147(para)
-#: ./doc/common/ch_cli_glance_commands.xml1057(para)
-msgid "Share a specific image with a tenant."
-msgstr "Partager une image spécifique avec un locataire."
-
-#: ./doc/common/ch_cli_glance_commands.xml155(para)
-#: ./doc/common/ch_cli_glance_commands.xml1093(para)
-msgid "Remove a shared image from a tenant."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml171(para)
-#: ./doc/common/ch_cli_glance_commands.xml1118(para)
-msgid "Describe sharing permissions by image or tenant."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml187(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use image-show instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml195(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use image-update instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml212(title)
-msgid "glance optional arguments"
-msgstr "arguments facultatifs de glance"
-
-#: ./doc/common/ch_cli_glance_commands.xml225(para)
-msgid "Defaults to <code>env[GLANCECLIENT_DEBUG]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml233(para)
-msgid "Print more verbose output"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml241(para)
-msgid ""
-"Force retrieving the schema used to generate portions of the help text "
-"rather than using a cached copy. Ignored with api version 1"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml251(para)
-msgid ""
-"Explicitly allow glanceclient to perform \"insecure SSL\" (https) requests. "
-"The server's certificate will not be verified against any certificate "
-"authorities. This option should be used with caution."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml282(para)
-msgid ""
-"Path of CA TLS certificate(s) used to verify the remote server's "
-"certificate. Without this option glance looks for the default system CA "
-"certificates."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml300(para)
-msgid "Number of seconds to wait for a response"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml308(para)
-msgid "Disable SSL compression when using https."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml316(para)
-msgid "Prevent select actions from requesting user confirmation."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml325(para)
-msgid ""
-"<emphasis>DEPRECATED!</emphasis> Only used for deprecated legacy commands."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml333(para)
-#: ./doc/common/ch_cli_glance_commands.xml342(para)
-#: ./doc/common/ch_cli_glance_commands.xml351(para)
-msgid ""
-"<emphasis>DEPRECATED!</emphasis> Send a fully-formed endpoint using --os- "
-"image-url instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml360(para)
-msgid "Defaults to <code>env[OS_USERNAME]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml368(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use --os-username."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml376(para)
-msgid "Defaults to <code>env[OS_PASSWORD]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml384(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use --os-password."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml392(para)
-msgid "Defaults to <code>env[OS_TENANT_ID]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml400(para)
-msgid "Defaults to <code>env[OS_TENANT_NAME]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml408(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use --os-tenant-name."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml416(para)
-msgid "Defaults to <code>env[OS_AUTH_URL]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml424(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use --os-auth-url."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml432(para)
-msgid "Defaults to <code>env[OS_REGION_NAME]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml440(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use --os-region-name."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml456(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use --os-auth-token."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml464(para)
-msgid "Defaults to <code>env[OS_IMAGE_URL]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml472(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use --os-image-url."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml480(para)
-msgid "Defaults to <code>env[OS_IMAGE_API_VERSION]</code> or 1"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml488(para)
-msgid "Defaults to <code>env[OS_SERVICE_TYPE]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml496(para)
-msgid "Defaults to <code>env[OS_ENDPOINT_TYPE]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml504(para)
-msgid "<emphasis>DEPRECATED!</emphasis> This option is completely ignored."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml512(title)
-msgid "glance image-create command"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml531(para)
-msgid "of image to reserve."
-msgstr "d'une image à réserver."
-
-#: ./doc/common/ch_cli_glance_commands.xml539(para)
-#: ./doc/common/ch_cli_glance_commands.xml904(para)
-msgid "Name of image."
-msgstr "Nom de l'image."
-
-#: ./doc/common/ch_cli_glance_commands.xml547(para)
-msgid "Store to upload image to."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml555(para)
-#: ./doc/common/ch_cli_glance_commands.xml912(para)
-msgid ""
-"Disk format of image. Acceptable formats: ami, ari, aki, vhd, vmdk, raw, "
-"qcow2, vdi, and iso."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml564(para)
-#: ./doc/common/ch_cli_glance_commands.xml921(para)
-msgid ""
-"Container format of image. Acceptable formats: ami, ari, aki, bare, and ovf."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml573(para)
-#: ./doc/common/ch_cli_glance_commands.xml930(para)
-msgid "Tenant who should own image."
-msgstr "Le locataire que devrait posséder l'image."
-
-#: ./doc/common/ch_cli_glance_commands.xml581(para)
-msgid ""
-"Size of image data (in bytes). Only used with '-- location' and '--"
-"copy_from'."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml590(para)
-#: ./doc/common/ch_cli_glance_commands.xml946(para)
-msgid "Minimum size of disk needed to boot image (in gigabytes)."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml599(para)
-#: ./doc/common/ch_cli_glance_commands.xml955(para)
-msgid "Minimum amount of ram needed to boot image (in megabytes)."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml608(para)
-#: ./doc/common/ch_cli_glance_commands.xml964(para)
-msgid ""
-"URL where the data for this image already resides. For example, if the image"
-" data is stored in swift, you could specify "
-"'swift://account:key@example.com/container/obj'."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml619(para)
-msgid ""
-"Local file that contains disk image to be uploaded during creation. "
-"Alternatively, images can be passed to the client via stdin."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml629(para)
-msgid ""
-"Hash of image data used Glance can use for verification. Provide a md5 "
-"checksum here."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml638(para)
-#: ./doc/common/ch_cli_glance_commands.xml994(para)
-msgid ""
-"Similar to '--location' in usage, but this indicates that the Glance server "
-"should immediately copy the data and store it in its configured image store."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml648(para)
-#: ./doc/common/ch_cli_glance_commands.xml1004(para)
-msgid "Make image accessible to the public."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml656(para)
-#: ./doc/common/ch_cli_glance_commands.xml1012(para)
-msgid "Prevent image from being deleted."
-msgstr "Empêcher la suppression de l'image"
-
-#: ./doc/common/ch_cli_glance_commands.xml664(para)
-#: ./doc/common/ch_cli_glance_commands.xml1020(para)
-msgid ""
-"Arbitrary property to associate with image. May be used multiple times."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml673(para)
-#: ./doc/common/ch_cli_glance_commands.xml790(para)
-#: ./doc/common/ch_cli_glance_commands.xml866(para)
-#: ./doc/common/ch_cli_glance_commands.xml1039(para)
-msgid "Print image size in a human-friendly format."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml681(para)
-#: ./doc/common/ch_cli_glance_commands.xml1047(para)
-msgid "Show upload progress bar."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml689(title)
-msgid "glance image-delete command"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml698(para)
-msgid "Name or ID of image(s) to delete."
-msgstr "Nom ou ID des image(s) à supprimer."
-
-#: ./doc/common/ch_cli_glance_commands.xml706(title)
-msgid "glance image-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml722(para)
-msgid "Filter images to those that have this name."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml730(para)
-msgid "Filter images to those that have this status."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml738(para)
-msgid ""
-"Filter images to those that have this container format. Acceptable formats: "
-"ami, ari, aki, bare, and ovf."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml748(para)
-msgid ""
-"Filter images to those that have this disk format. Acceptable formats: ami, "
-"ari, aki, vhd, vmdk, raw, qcow2, vdi, and iso."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml758(para)
-msgid "Filter images to those with a size greater than this."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml766(para)
-msgid "Filter images to those with a size less than this."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml774(para)
-msgid "Filter images by a user-defined image property."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml782(para)
-msgid "Number of images to request in each paginated request."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml798(para)
-msgid "Sort image list by specified field."
-msgstr "Trier la liste des images par champ spécifique."
-
-#: ./doc/common/ch_cli_glance_commands.xml806(para)
-msgid "Sort image list in specified direction."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml814(para)
-msgid "Allows the user to select a listing of public or non public images."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml823(para)
-msgid ""
-"Display only images owned by this tenant id. Filtering occurs on the client "
-"side so may be inefficient. This option is mainly intended for admin use. "
-"Use an empty string ('') to list images with no owner. Note: This option "
-"overrides the --is-public argument if present. Note: the v2 API supports "
-"more efficient server-side owner based filtering."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml837(para)
-msgid ""
-"Allows the admin user to list all images irrespective of the image's owner "
-"or is_public value."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml846(title)
-msgid "glance image-show command"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml855(para)
-msgid "Name or ID of image to describe."
-msgstr "Nom ou ID de l'image à décrire."
-
-#: ./doc/common/ch_cli_glance_commands.xml874(title)
-msgid "glance image-update command"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml893(para)
-msgid "Name or ID of image to modify."
-msgstr "Nom ou ID de l'image à modifier."
-
-#: ./doc/common/ch_cli_glance_commands.xml938(para)
-msgid "Size of image data (in bytes)."
-msgstr "Taille de l'image (en octets)."
-
-#: ./doc/common/ch_cli_glance_commands.xml975(para)
-msgid ""
-"Local file that contains disk image to be uploaded during update. "
-"Alternatively, images can be passed to the client via stdin."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml985(para)
-msgid "Hash of image data used Glance can use for verification."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml1029(para)
-msgid ""
-"If this flag is present, delete all image properties not explicitly set in "
-"the update request. Otherwise, those properties not referenced are "
-"preserved."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml1055(title)
-msgid "glance member-create command"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml1064(para)
-msgid "Image to add member to."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml1072(para)
-msgid "Tenant to add as member"
-msgstr "Le locataire à ajouter comme membre"
-
-#: ./doc/common/ch_cli_glance_commands.xml1083(para)
-msgid "Allow the specified tenant to share this image."
-msgstr "Permetter le locataire specifié de partager cette image."
-
-#: ./doc/common/ch_cli_glance_commands.xml1091(title)
-msgid "glance member-delete command"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml1100(para)
-msgid "Image from which to remove member"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml1108(para)
-msgid "Tenant to remove as member"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml1116(title)
-msgid "glance member-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml1125(para)
-msgid "Filter results by an image ID."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml1133(para)
-msgid "Filter results by a tenant ID."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_userdata.xml6(title)
-msgid "Provide user data to instances"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_userdata.xml7(para)
-msgid ""
-"A <glossterm baseform=\"user data\">user data</glossterm> file is a special "
-"key in the metadata service that holds a file that cloud-aware applications "
-"in the guest instance can access. For example, one application that uses "
-"user data is the <link href=\"https://help.ubuntu.com/community/CloudInit"
-"\">cloud-init</link> system, which is an open-source package from Ubuntu "
-"that is available on various Linux distributions and which handles early "
-"initialization of a cloud instance."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_userdata.xml14(para)
-msgid ""
-"You can place user data in a local file and pass it through the <parameter"
-">--user-data &lt;user-data-file&gt;</parameter> parameter at instance "
-"creation:"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml6(title)
-#: ./doc/common/section_objectstorage-components.xml192(title)
-msgid "Replication"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml7(para)
-msgid ""
-"Because each replica in Object Storage functions independently and clients "
-"generally require only a simple majority of nodes to respond to consider an "
-"operation successful, transient failures like network partitions can quickly"
-" cause replicas to diverge. These differences are eventually reconciled by "
-"asynchronous, peer-to-peer replicator processes. The replicator processes "
-"traverse their local file systems and concurrently perform operations in a "
-"manner that balances load across physical disks."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml16(para)
-msgid ""
-"Replication uses a push model, with records and files generally only being "
-"copied from local to remote replicas. This is important because data on the "
-"node might not belong there (as in the case of hand offs and ring changes), "
-"and a replicator cannot know which data it should pull in from elsewhere in "
-"the cluster. Any node that contains data must ensure that data gets to where"
-" it belongs. The ring handles replica placement."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml24(para)
-msgid ""
-"To replicate deletions in addition to creations, every deleted record or "
-"file in the system is marked by a tombstone. The replication process cleans "
-"up tombstones after a time period known as the <emphasis "
-"role=\"italic\">consistency window</emphasis>. This window defines the "
-"duration of the replication and how long transient failure can remove a node"
-" from the cluster. Tombstone cleanup must be tied to replication to reach "
-"replica convergence."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml32(para)
-msgid ""
-"If a replicator detects that a remote drive has failed, the replicator uses "
-"the <literal>get_more_nodes</literal> interface for the ring to choose an "
-"alternate node with which to synchronize. The replicator can maintain "
-"desired levels of replication during disk failures, though some replicas "
-"might not be in an immediately usable location."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml39(para)
-msgid ""
-"The replicator does not maintain desired levels of replication when failures"
-" such as entire node failures occur; most failures are transient."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml43(para)
-msgid "The main replication types are:"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml46(para)
-msgid ""
-"<emphasis role=\"bold\">Database replication</emphasis>. Replicates "
-"containers and objects."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml51(para)
-msgid ""
-"<emphasis role=\"bold\">Object replication</emphasis>. Replicates object "
-"data."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml56(title)
-msgid "Database replication"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml57(para)
-msgid ""
-"Database replication completes a low-cost hash comparison to determine "
-"whether two replicas already match. Normally, this check can quickly verify "
-"that most databases in the system are already synchronized. If the hashes "
-"differ, the replicator synchronizes the databases by sharing records added "
-"since the last synchronization point."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml64(para)
-msgid ""
-"This synchronization point is a high water mark that notes the last record "
-"at which two databases were known to be synchronized, and is stored in each "
-"database as a tuple of the remote database ID and record ID. Database IDs "
-"are unique across all replicas of the database, and record IDs are "
-"monotonically increasing integers. After all new records are pushed to the "
-"remote database, the entire synchronization table of the local database is "
-"pushed, so the remote database can guarantee that it is synchronized with "
-"everything with which the local database was previously synchronized."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml75(para)
-msgid ""
-"If a replica is missing, the whole local database file is transmitted to the"
-" peer by using rsync(1) and is assigned a new unique ID."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml78(para)
-msgid ""
-"In practice, database replication can process hundreds of databases per "
-"concurrency setting per second (up to the number of available CPUs or disks)"
-" and is bound by the number of database transactions that must be performed."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml85(title)
-msgid "Object replication"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml86(para)
-msgid ""
-"The initial implementation of object replication performed an rsync to push "
-"data from a local partition to all remote servers where it was expected to "
-"reside. While this worked at small scale, replication times skyrocketed once"
-" directory structures could no longer be held in RAM. This scheme was "
-"modified to save a hash of the contents for each suffix directory to a per-"
-"partition hashes file. The hash for a suffix directory is no longer valid "
-"when the contents of that suffix directory is modified."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml95(para)
-msgid ""
-"The object replication process reads in hash files and calculates any "
-"invalidated hashes. Then, it transmits the hashes to each remote server that"
-" should hold the partition, and only suffix directories with differing "
-"hashes on the remote server are rsynced. After pushing files to the remote "
-"server, the replication process notifies it to recalculate hashes for the "
-"rsynced suffix directories."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml103(para)
-msgid ""
-"The number of uncached directories that object replication must traverse, "
-"usually as a result of invalidated suffix directory hashes, impedes "
-"performance. To provide acceptable replication speeds, object replication is"
-" designed to invalidate around 2 percent of the hash space on a normal node "
-"each day."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_reboot.xml5(title)
-msgid "Reboot an instance"
-msgstr "Redémarrer une instance"
-
-#: ./doc/common/section_cli_nova_reboot.xml6(para)
-msgid ""
-"You can soft or hard reboot a running instance. A soft reboot attempts a "
-"graceful shut down and restart of the instance. A hard reboot power cycles "
-"the instance."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_reboot.xml9(para)
-msgid "By default, when you reboot a server, it is a soft reboot."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_reboot.xml10(replaceable)
-#: ./doc/common/section_cli_nova_reboot.xml12(replaceable)
-msgid "SERVER"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_reboot.xml11(para)
-msgid ""
-"To perform a hard reboot, pass the <parameter>--hard</parameter> parameter, "
-"as follows:"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml6(title)
-msgid "Ring-builder"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml7(para)
-msgid ""
-"Use the swift-ring-builder utility to build and manage rings. This utility "
-"assigns partitions to devices and writes an optimized Python structure to a "
-"gzipped, serialized file on disk for transmission to the servers. The server"
-" processes occasionally check the modification time of the file and reload "
-"in-memory copies of the ring structure as needed. If you use a slightly "
-"older version of the ring, one of the three replicas for a partition subset "
-"will be incorrect because of the way the ring-builder manages changes to the"
-" ring. You can work around this issue."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml17(para)
-msgid ""
-"The ring-builder also keeps its own builder file with the ring information "
-"and additional data required to build future rings. It is very important to "
-"keep multiple backup copies of these builder files. One option is to copy "
-"the builder files out to every server while copying the ring files "
-"themselves. Another is to upload the builder files into the cluster itself. "
-"If you lose the builder file, you have to create a new ring from scratch. "
-"Nearly all partitions would be assigned to different devices and, therefore,"
-" nearly all of the stored data would have to be replicated to new locations."
-" So, recovery from a builder file loss is possible, but data would be "
-"unreachable for an extended time."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml30(title)
-msgid "Ring data structure"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml31(para)
-msgid ""
-"The ring data structure consists of three top level fields: a list of "
-"devices in the cluster, a list of lists of device ids indicating partition "
-"to device assignments, and an integer indicating the number of bits to shift"
-" an MD5 hash to calculate the partition for the hash."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml38(title)
-msgid "Partition assignment list"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml39(para)
-msgid ""
-"This is a list of <literal>array(‘H’)</literal> of devices ids. The "
-"outermost list contains an <literal>array(‘H’)</literal> for each replica. "
-"Each <literal>array(‘H’)</literal> has a length equal to the partition count"
-" for the ring. Each integer in the <literal>array(‘H’)</literal> is an index"
-" into the above list of devices. The partition list is known internally to "
-"the Ring class as <literal>_replica2part2dev_id</literal>."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml48(para)
-msgid ""
-"So, to create a list of device dictionaries assigned to a partition, the "
-"Python code would look like: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml52(para)
-msgid ""
-"That code is a little simplistic because it does not account for the removal"
-" of duplicate devices. If a ring has more replicas than devices, a partition"
-" will have more than one replica on a device."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml56(para)
-msgid ""
-"<literal>array(‘H’)</literal> is used for memory conservation as there may "
-"be millions of partitions."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml61(title)
-msgid "Replica counts"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml62(para)
-msgid ""
-"To support the gradual change in replica counts, a ring can have a real "
-"number of replicas and is not restricted to an integer number of replicas."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml65(para)
-msgid ""
-"A fractional replica count is for the whole ring and not for individual "
-"partitions. It indicates the average number of replicas for each partition. "
-"For example, a replica count of 3.2 means that 20 percent of partitions have"
-" four replicas and 80 percent have three replicas."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml70(para)
-msgid "The replica count is adjustable."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml71(para)
-msgid "Example:"
-msgstr "Exemple:"
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml74(para)
-msgid ""
-"You must rebalance the replica ring in globally distributed clusters. "
-"Operators of these clusters generally want an equal number of replicas and "
-"regions. Therefore, when an operator adds or removes a region, the operator "
-"adds or removes a replica. Removing unneeded replicas saves on the cost of "
-"disks."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml80(para)
-msgid ""
-"You can gradually increase the replica count at a rate that does not "
-"adversely affect cluster performance."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml90(para)
-msgid ""
-"Changes take effect after the ring is rebalanced. Therefore, if you intend "
-"to change from 3 replicas to 3.01 but you accidentally type "
-"<literal>2.01</literal>, no data is lost."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml95(replaceable)
-msgid "X.builder"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml94(para)
-msgid ""
-"Additionally, <placeholder-1/> can now take a decimal argument for the "
-"number of replicas."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml100(title)
-msgid "Partition shift value"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml101(para)
-msgid ""
-"The partition shift value is known internally to the Ring class as "
-"<literal>_part_shift</literal>. This value is used to shift an MD5 hash to "
-"calculate the partition where the data for that hash should reside. Only the"
-" top four bytes of the hash is used in this process. For example, to compute"
-" the partition for the <literal>/account/container/object</literal> path, "
-"the Python code might look like the following code: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml112(para)
-msgid ""
-"For a ring generated with part_power P, the partition shift value is "
-"<literal>32 - P</literal>."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml116(title)
-msgid "Build the ring"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml117(para)
-msgid "The ring builder process includes these high-level steps:"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml121(para)
-msgid ""
-"The utility calculates the number of partitions to assign to each device "
-"based on the weight of the device. For example, for a partition at the power"
-" of 20, the ring has 1,048,576 partitions. One thousand devices of equal "
-"weight will each want 1,048.576 partitions. The devices are sorted by the "
-"number of partitions they desire and kept in order throughout the "
-"initialization process."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml131(para)
-msgid ""
-"Each device is also assigned a random tiebreaker value that is used when two"
-" devices desire the same number of partitions. This tiebreaker is not stored"
-" on disk anywhere, and so two different rings created with the same "
-"parameters will have different partition assignments. For repeatable "
-"partition assignments, <literal>RingBuilder.rebalance()</literal> takes an "
-"optional seed value that seeds the Python pseudo-random number generator."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml145(para)
-msgid ""
-"The ring builder assigns each partition replica to the device that requires "
-"most partitions at that point while keeping it as far away as possible from "
-"other replicas. The ring builder prefers to assign a replica to a device in "
-"a region that does not already have a replica. If no such region is "
-"available, the ring builder searches for a device in a different zone, or on"
-" a different server. If it does not find one, it looks for a device with no "
-"replicas. Finally, if all options are exhausted, the ring builder assigns "
-"the replica to the device that has the fewest replicas already assigned."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml159(para)
-msgid ""
-"The ring builder assigns multiple replicas to one device only if the ring "
-"has fewer devices than it has replicas."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml165(para)
-msgid ""
-"When building a new ring from an old ring, the ring builder recalculates the"
-" desired number of partitions that each device wants."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml174(para)
-msgid ""
-"The ring builder unassigns any assigned partitions from any removed devices "
-"and adds these partitions to the gathered list."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml180(para)
-msgid ""
-"The ring builder unassigns any partition replicas that can be spread out for"
-" better durability and adds these partitions to the gathered list."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml187(para)
-msgid ""
-"The ring builder unassigns random partitions from any devices that have more"
-" partitions than they need and adds these partitions to the gathered list."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml170(para)
-msgid ""
-"The ring builder unassigns partitions and gathers these partitions for "
-"reassignment, as follows: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml197(para)
-msgid ""
-"The ring builder reassigns the gathered partitions to devices by using a "
-"similar method to the one described previously."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml202(para)
-msgid ""
-"When the ring builder reassigns a replica to a partition, the ring builder "
-"records the time of the reassignment. The ring builder uses this value when "
-"it gathers partitions for reassignment so that no partition is moved twice "
-"in a configurable amount of time. The RingBuilder class knows this "
-"configurable amount of time as <literal>min_part_hours</literal>. The ring "
-"builder ignores this restriction for replicas of partitions on removed "
-"devices because removal of a device happens on device failure only, and "
-"reassignment is the only choice."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml216(para)
-msgid ""
-"Theses steps do not always perfectly rebalance a ring due to the random "
-"nature of gathering partitions for reassignment. To help reach a more "
-"balanced ring, the rebalance process is repeated until near perfect (less "
-"than 1 percent off) or when the balance does not improve by at least 1 "
-"percent (indicating we probably cannot get perfect balance due to wildly "
-"imbalanced zones or too many partitions recently moved)."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-account-reaper.xml7(title)
-msgid "Account reaper"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-account-reaper.xml8(para)
-msgid ""
-"In the background, the account reaper removes data from the deleted "
-"accounts."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-account-reaper.xml9(para)
-msgid ""
-"A reseller marks an account for deletion by issuing a <code>DELETE</code> "
-"request on the account’s storage URL. This action sets the "
-"<code>status</code> column of the account_stat table in the account database"
-" and replicas to <code>DELETED</code>, marking the account's data for "
-"deletion."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-account-reaper.xml17(para)
-msgid ""
-"It's on the developers' to-do list to write a utility that performs this "
-"task, preferably through a ReST call."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-account-reaper.xml12(para)
-msgid ""
-"Typically, a specific retention time or undelete are not provided. However, "
-"you can set a <code>delay_reaping</code> value in the <code>[account-"
-"reaper]</code> section of the account-server.conf to delay the actual "
-"deletion of data. At this time, to undelete you have to update the account "
-"database replicas directly, setting the status column to an empty string and"
-" updating the put_timestamp to be greater than the delete_timestamp. "
-"<placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-account-reaper.xml20(para)
-msgid ""
-"The account reaper runs on each account server and scans the server "
-"occasionally for account databases marked for deletion. It only fires up on "
-"the accounts for which the server is the primary node, so that multiple "
-"account servers aren’t trying to do it simultaneously. Using multiple "
-"servers to delete one account might improve the deletion speed but requires "
-"coordination to avoid duplication. Speed really is not a big concern with "
-"data deletion, and large accounts aren’t deleted often."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-account-reaper.xml26(para)
-msgid ""
-"Deleting an account is simple. For each account container, all objects are "
-"deleted and then the container is deleted. Deletion requests that fail will "
-"not stop the overall process but will cause the overall process to fail "
-"eventually (for example, if an object delete times out, you will not be able"
-" to delete the container or the account). The account reaper keeps trying to"
-" delete an account until it is empty, at which point the database reclaim "
-"process within the db_replicator will remove the database files."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-account-reaper.xml32(para)
-msgid ""
-"A persistent error state may prevent the deletion of an object or container."
-" If this happens, you will see a message such as <code>“Account &lt;name&gt;"
-" has not been reaped since &lt;date&gt;”</code> in the log. You can control "
-"when this is logged with the <code>reap_warn_after</code> value in the <code"
-">[account-reaper]</code> section of the account-server.conf file. The "
-"default value is 30 days."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml9(title)
-msgid "Troubleshoot Compute"
-msgstr "Résoudre les problèmes Calcul"
-
-#: ./doc/common/section_support-compute.xml10(para)
-msgid ""
-"Common problems for Compute typically involve misconfigured networking or "
-"credentials that are not sourced properly in the environment. Also, most "
-"flat networking configurations do not enable <placeholder-1/> or "
-"<placeholder-2/> from a compute node to the instances that run on that node."
-" Another common problem is trying to run 32-bit images on a 64-bit compute "
-"node. This section shows you how to troubleshoot Compute."
-msgstr "Les erreurs fréquentes avec Calcul impliquent généralement un réseau mal configuré ou des identifiants qui ne sont pas correctement sourcés dans l'environnement. De plus, la plupart des configurations de réseaux plats ne permettent pas de <placeholder-1/> or <placeholder-2/> à partir d'un nœud de calcul pour les instances en cours d'exécution sur ce nœud. Un autre problème fréquent est d'essayer d'exécuter des images 32 bits sur un nœud de calcul 64-bit. Cette section propose plus d'informations sur la façon de résoudre les problèmes de Calcul."
-
-#: ./doc/common/section_support-compute.xml19(title)
-msgid "Compute service logging"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml20(para)
-msgid ""
-"Compute stores a log file for each service in "
-"<filename>/var/log/nova</filename>. For example, <filename>nova-"
-"compute.log</filename> is the log for the <systemitem class=\"service"
-"\">nova-compute</systemitem> service. You can set the following options to "
-"format log strings for the nova.log module in the "
-"<filename>nova.conf</filename> file:"
-msgstr "Les fichiers Log sont stockés dans <filename>/var/log/nova</filename> et il y a un fichier log pour chaque service, par exemple <filename>nova-compute.log</filename>. Vous pouvez formater les chaines log en utilisant les options pour le nova.log module. Les options utilisées pour définir les chaînes de format sont : "
-
-#: ./doc/common/section_support-compute.xml29(literal)
-msgid "logging_context_format_string"
-msgstr "logging_context_format_string"
-
-#: ./doc/common/section_support-compute.xml32(literal)
-msgid "logging_default_format_string"
-msgstr "logging_default_format_string"
-
-#: ./doc/common/section_support-compute.xml35(para)
-msgid ""
-"If the log level is set to <literal>debug</literal>, you can also specify "
-"<literal>logging_debug_format_suffix</literal> to append extra formatting. "
-"For information about what variables are available for the formatter see: "
-"<link "
-"href=\"http://docs.python.org/library/logging.html#formatter\">http://docs.python.org/library/logging.html#formatter</link>."
-msgstr "Si le niveau de journalisation est défini sur <literal>debug</literal>, vous pouvez également spécifier <literal>logging_debug_format_suffix</literal> pour ajouter du formatage supplémentaire. Pour des informations à propos de quelles variables sont disponibles pour le formatteur : <link href=\"http://docs.python.org/library/logging.html#formatter\">http://docs.python.org/library/logging.html#formatter</link>."
-
-#: ./doc/common/section_support-compute.xml42(para)
-msgid ""
-"You have two options for logging for OpenStack Compute based on "
-"configuration settings. In <filename>nova.conf</filename>, include the "
-"<literal>logfile</literal> option to enable logging. Alternatively you can "
-"set <literal>use_syslog = 1</literal> so that the nova daemon logs to "
-"syslog."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml50(title)
-msgid "Guru Meditation reports"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml51(para)
-msgid ""
-"A Guru Meditation report is sent by the Compute Service upon receipt of the "
-"<systemitem>SIGUSR1</systemitem> signal. This report is a general-purpose "
-"error report, including a complete report of the service's current state, "
-"and is sent to <systemitem>stderr</systemitem>."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml55(para)
-msgid ""
-"For example, if you redirect error output to <filename>nova-api-"
-"err.log</filename> using <placeholder-1/>, resulting in the process ID 8675,"
-" you can then run:"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml59(para)
-msgid ""
-"This command triggers the Guru Meditation report to be printed to "
-"<filename>/var/log/nova/nova-api-err.log</filename>."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml63(para)
-msgid ""
-"Package Displays information about the package to which the process belongs,"
-" including version information."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml65(para)
-msgid ""
-"Threads Displays stack traces and thread IDs for each of the threads within "
-"the process."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml67(para)
-msgid ""
-"Green Threads Displays stack traces for each of the green threads within the"
-" process (green threads do not have thread IDs)."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml69(para)
-msgid ""
-"Configuration Lists all configuration options currently accessible through "
-"the CONF object for the current process."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml61(para)
-msgid "The report has the following sections: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml72(para)
-msgid ""
-"For more information, see <link "
-"href=\"http://docs.openstack.org/developer/nova/devref/gmr.html\">Guru "
-"Meditation Reports</link>."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml77(title)
-msgid "Common errors and fixes for Compute"
-msgstr "Erreurs Fréquentes et Solutions pour Calcul"
-
-#: ./doc/common/section_support-compute.xml78(para)
-msgid ""
-"The <link href=\"ask.openstack.org\">ask.openstack.org</link> site offers a "
-"place to ask and answer questions, and you can also mark questions as "
-"frequently asked questions. This section describes some errors people have "
-"posted previously. Bugs are constantly being fixed, so online resources are "
-"a great way to get the most up-to-date errors and fixes."
-msgstr "Le site <link href=\"ask.openstack.org\">ask.openstack.org</link> offre un endroit où poser et répondre aux questions, et vous pouvez également annoter des questions comme fréquemment posées. Cette section décrit certaines erreurs que des personnes ont postées précédemment. Comme nous corrigeons constamment les bugs, les ressources en ligne sont un excellent moyen pour obtenir le plus de mises à jour sur les erreurs et solutions."
-
-#: ./doc/common/section_support-compute.xml86(title)
-msgid "Credential errors, 401, and 403 forbidden errors"
-msgstr "Erreurs références, 401, 403 [original] forbidden erreurs "
-
-#: ./doc/common/section_support-compute.xml93(para)
-msgid ""
-"<emphasis role=\"bold\">Manual method</emphasis>. Get get the "
-"<filename>novarc</filename> file from the project ZIP file, save existing "
-"credentials in case of override. and manually source the "
-"<filename>novarc</filename> file."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml103(para)
-msgid ""
-"<emphasis role=\"bold\">Script method</emphasis>. Generates "
-"<filename>novarc</filename> from the project ZIP file and sources it for "
-"you."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml88(para)
-msgid ""
-"Missing credentials cause a "
-"<errorcode>403</errorcode><errortext>forbidden</errortext> error. To resolve"
-" this issue, use one of these methods:<placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml110(para)
-msgid ""
-"When you run <systemitem class=\"service\">nova-api</systemitem> the first "
-"time, it generates the certificate authority information, including "
-"<filename>openssl.cnf</filename>. If you start the CA services before this, "
-"you might not be able to create your ZIP file. Restart the services. When "
-"your CA information is available, create your ZIP file."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml118(para)
-msgid ""
-"Also, check your HTTP proxy settings to see whether they cause problems with"
-" <filename>novarc</filename> creation."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml123(title)
-msgid "Instance errors"
-msgstr "Erreurs Instance"
-
-#: ./doc/common/section_support-compute.xml124(para)
-msgid ""
-"Sometimes a particular instance shows <literal>pending</literal> or you "
-"cannot SSH to it. Sometimes the image itself is the problem. For example, "
-"when you use flat manager networking, you do not have a DHCP server and "
-"certain images do not support interface injection; you cannot connect to "
-"them. The fix for this problem is to use an image that does support this "
-"method, such as Ubuntu, which obtains an IP address correctly with "
-"FlatManager network settings."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml134(para)
-msgid ""
-"To troubleshoot other possible problems with an instance, such as an "
-"instance that stays in a spawning state, check the directory for the "
-"particular instance under <filename>/var/lib/nova/instances</filename> on "
-"the <systemitem class=\"service\">nova-compute</systemitem> host and make "
-"sure that these files are present:"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml143(filename)
-msgid "libvirt.xml"
-msgstr "libvirt.xml"
-
-#: ./doc/common/section_support-compute.xml146(filename)
-msgid "disk"
-msgstr "disque"
-
-#: ./doc/common/section_support-compute.xml149(filename)
-msgid "disk-raw"
-msgstr "disk en format brut"
-
-#: ./doc/common/section_support-compute.xml152(filename)
-msgid "kernel"
-msgstr "noyau"
-
-#: ./doc/common/section_support-compute.xml155(filename)
-msgid "ramdisk"
-msgstr "ramdisk"
-
-#: ./doc/common/section_support-compute.xml158(para)
-msgid "After the instance starts, <filename>console.log</filename>"
-msgstr "Après le démarrage de l'instance, <filename>console.log</filename>"
-
-#: ./doc/common/section_support-compute.xml162(para)
-msgid ""
-"If any files are missing, empty, or very small, the <systemitem "
-"class=\"service\">nova-compute</systemitem> service did not successfully "
-"download the images from the Image Service."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml167(para)
-msgid ""
-"Also check <filename>nova-compute.log</filename> for exceptions. Sometimes "
-"they do not appear in the console output."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml170(para)
-msgid ""
-"Next, check the log file for the instance in the "
-"<filename>/var/log/libvirt/qemu</filename> directory to see if it exists and"
-" has any useful error messages in it."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml174(para)
-msgid ""
-"Finally, from the <filename>/var/lib/nova/instances</filename> directory for"
-" the instance, see if this command returns an error:"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml181(title)
-msgid "Empty log output for Linux instances"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml182(para)
-msgid ""
-"You can view the log output of running instances from either the "
-"<guilabel>Log</guilabel> tab of the dashboard or the output of "
-"<placeholder-1/>. In some cases, the log output of a running Linux instance "
-"will be empty or only display a single character (for example, the "
-"<keycap>?</keycap> character)."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml189(para)
-msgid ""
-"This occurs when the Compute service attempts to retrieve the log output of "
-"the instance via a serial console while the instance itself is not "
-"configured to send output to the console. To rectify this, append the "
-"following parameters to kernel arguments specified in the instance's boot "
-"loader:"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml196(para)
-msgid ""
-"Upon rebooting, the instance will be configured to send output to the "
-"Compute service."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml201(title)
-msgid "Reset the state of an instance"
-msgstr "Réinitialiser manuellement l'état d'une instance"
-
-#: ./doc/common/section_support-compute.xml202(para)
-msgid ""
-"If an instance remains in an intermediate state, such as "
-"<literal>deleting</literal>, you can use the <placeholder-1/> command to "
-"manually reset the state of an instance to an error state. You can then "
-"delete the instance. For example:"
-msgstr "Si une instance est bloquée dans un état intermédiaire <literal>deleting</literal>, vous prouver réinitialiser manuellement l'état d'une instance en utilisant la commande <placeholder-1/> . Cela va le réinitialiser à l'état d'erreur, que vous pouvez ensuite supprimer. Par example :"
-
-#: ./doc/common/section_support-compute.xml209(para)
-msgid ""
-"You can also use the <parameter>--active</parameter> parameter to force the "
-"instance back to an active state instead of an error state. For example:"
-msgstr "Vous pouvez également utiliser le --active  pour forcer l'instance à retourner à un état actif au lieu d'un état d'erreur, par exemple :"
-
-#: ./doc/common/section_support-compute.xml215(title)
-msgid "Injection problems"
-msgstr "Problèmes avec Injection"
-
-#: ./doc/common/section_support-compute.xml216(para)
-msgid ""
-"If instances do not boot or boot slowly, investigate file injection as a "
-"cause."
-msgstr "Si vous diagnostiquez un problème avec des instances qui ne démarrent pas, ou lentement, considérez le fichier injection la cause et vérifiez le. "
-
-#: ./doc/common/section_support-compute.xml218(para)
-msgid ""
-"To disable injection in libvirt, set the following in "
-"<filename>nova.conf</filename>:"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml223(para)
-msgid ""
-"If you have not enabled the configuration drive and you want to make user-"
-"specified files available from the metadata server for to improve "
-"performance and avoid boot failure if injection fails, you must disable "
-"injection."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_search_ip.xml7(title)
-msgid "Search for an instance using IP address"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_search_ip.xml8(para)
-msgid ""
-"You can search for an instance using the IP address parameter, "
-"<literal>--ip</literal>, with the <placeholder-1/> command."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_search_ip.xml11(parameter)
-#: ./doc/common/section_cli_nova_search_ip.xml14(parameter)
-msgid "ip"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_search_ip.xml11(replaceable)
-msgid "IP_ADDRESS"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_search_ip.xml12(para)
-msgid ""
-"The following example shows the results of a search on "
-"<filename>10.0.0.4</filename>."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_search_ip.xml14(replaceable)
-msgid "10.0.0.4"
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml7(title)
-msgid "Configure the Identity Service with SSL"
-msgstr "Configurer le service d'identité avec SSL"
-
-#: ./doc/common/section_keystone-ssl-config.xml8(para)
-msgid "You can configure the Identity Service to support two-way SSL."
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml10(para)
-msgid "You must obtain the x509 certificates externally and configure them."
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml12(para)
-msgid ""
-"The Identity Service provides a set of sample certificates in the <filename "
-"class=\"directory\">examples/pki/certs</filename> and <filename "
-"class=\"directory\">examples/pki/private</filename> directories:"
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml18(title)
-msgid "Certificate types"
-msgstr "Types de certificats"
-
-#: ./doc/common/section_keystone-ssl-config.xml20(term)
-msgid "cacert.pem"
-msgstr "cacert.pem"
-
-#: ./doc/common/section_keystone-ssl-config.xml22(para)
-msgid "Certificate Authority chain to validate against."
-msgstr "Certifie la chaîne d'Autorité comme support de validation. "
-
-#: ./doc/common/section_keystone-ssl-config.xml27(term)
-msgid "ssl_cert.pem"
-msgstr "ssl_cert.pem"
-
-#: ./doc/common/section_keystone-ssl-config.xml29(para)
-msgid "Public certificate for Identity Service server."
-msgstr "Certificat public pour le serveur Keystone."
-
-#: ./doc/common/section_keystone-ssl-config.xml34(term)
-msgid "middleware.pem"
-msgstr "middleware.pem"
-
-#: ./doc/common/section_keystone-ssl-config.xml36(para)
-msgid "Public and private certificate for Identity Service middleware/client."
-msgstr "Certificat public et prive pour le client de middleware de Keystone"
-
-#: ./doc/common/section_keystone-ssl-config.xml41(term)
-msgid "cakey.pem"
-msgstr "cakey.pem"
-
-#: ./doc/common/section_keystone-ssl-config.xml43(para)
-msgid "Private key for the CA."
-msgstr "Clé privée pour le CA"
-
-#: ./doc/common/section_keystone-ssl-config.xml47(term)
-msgid "ssl_key.pem"
-msgstr "ssl_key.pem"
-
-#: ./doc/common/section_keystone-ssl-config.xml49(para)
-msgid "Private key for the Identity Service server."
-msgstr "Clé privée pour le serveur Keystone "
-
-#: ./doc/common/section_keystone-ssl-config.xml55(para)
-msgid ""
-"You can choose names for these certificates. You can also combine the "
-"public/private keys in the same file, if you wish. These certificates are "
-"provided as an example."
-msgstr "Il faut noter qu'il est possible de choisir les noms que vous voulez pour ces certificats, ou de combiner les clés publiques/privées dans le même fichier si vous le souhaitez. Ces certificats sont juste fournis à titre d'exemple. "
-
-#: ./doc/common/section_keystone-ssl-config.xml61(title)
-msgid "SSL configuration"
-msgstr "Configuration SSL"
-
-#: ./doc/common/section_keystone-ssl-config.xml62(para)
-msgid ""
-"To enable SSL with client authentication, modify the "
-"<literal>[ssl]</literal> section in the "
-"<filename>etc/keystone.conf</filename> file. The following SSL configuration"
-" example uses the included sample certificates:"
-msgstr "Pour permettre le SSL avec l'authentification par client, il faut modifier le fichier <filename>etc/keystone.conf</filename> dans la section <literal>[ssl]</literal>. Exemple de configuration SSL  en utilisant les certificats témoins inclus :  "
-
-#: ./doc/common/section_keystone-ssl-config.xml74(title)
-msgid "Options"
-msgstr "Options"
-
-#: ./doc/common/section_keystone-ssl-config.xml76(para)
-msgid "<literal>enable</literal>. True enables SSL. Default is False."
-msgstr "\t•\t<literal>enable</literal>: True active le SSL. Par défaut False "
-
-#: ./doc/common/section_keystone-ssl-config.xml80(para)
-msgid ""
-"<literal>certfile</literal>. Path to the Identity Service public certificate"
-" file."
-msgstr "<literal>certfile</literal>: Chemin vers les fichiers des certificat Keystone publics."
-
-#: ./doc/common/section_keystone-ssl-config.xml84(para)
-msgid ""
-"<literal>keyfile</literal>. Path to the Identity Service private certificate"
-" file. If you include the private key in the certfile, you can omit the "
-"keyfile."
-msgstr "• <literal>keyfile</literal>: Chemin vers les fichiers des certificats Keystone privés. Si la clé privé est incluse dans le certfile, le keyfile peut être omis."
-
-#: ./doc/common/section_keystone-ssl-config.xml90(para)
-msgid "<literal>ca_certs</literal>. Path to the CA trust chain."
-msgstr "<literal>ca_certs</literal>: Chemin vers la chaîne de confiance du CA."
-
-#: ./doc/common/section_keystone-ssl-config.xml94(para)
-msgid ""
-"<literal>cert_required</literal>. Requires client certificate. Default is "
-"False."
-msgstr "<literal>cert_required</literal>: Requiert le certificat du client. Par défaut False "
-
-#: ./doc/common/section_cli_nova_startstop.xml6(title)
-msgid "Stop and start an instance"
-msgstr "Démarrer et arrêter une instance"
-
-#: ./doc/common/section_cli_nova_startstop.xml7(para)
-msgid "Use one of the following methods to stop and start an instance."
-msgstr "Utilisez une des méthodes suivantes pour arrêter et démarrer une instance :"
-
-#: ./doc/common/section_cli_nova_startstop.xml10(title)
-msgid "Pause and unpause an instance"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml13(para)
-msgid "To pause an instance, run the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml15(para)
-msgid ""
-"This command stores the state of the VM in RAM. A paused instance continues "
-"to run in a frozen state."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml17(para)
-msgid "To unpause the instance, run the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml23(title)
-msgid "Suspend and resume an instance"
-msgstr "Suspend  and Resume (suspendre et reprendre)"
-
-#: ./doc/common/section_cli_nova_startstop.xml25(para)
-msgid ""
-"Administrative users might want to suspend an instance if it is infrequently"
-" used or to perform system maintenance. When you suspend an instance, its VM"
-" state is stored on disk, all memory is written to disk, and the virtual "
-"machine is stopped. Suspending an instance is similar to placing a device in"
-" hibernation; memory and vCPUs become available to create other instances."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml33(para)
-msgid ""
-"To initiate a hypervisor-level suspend operation, run the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml38(para)
-msgid "To resume a suspended instance, run the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml45(title)
-msgid "Shelve and unshelve an instance"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml46(para)
-msgid ""
-"Shelving is useful if you have an instance that you are not using, but would"
-" like retain in your list of servers. For example, you can stop an instance "
-"at the end of a work week, and resume work again at the start of the next "
-"week. All associated data and resources are kept; however, anything still in"
-" memory is not retained. If a shelved instance is no longer needed, it can "
-"also be entirely removed."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml51(para)
-msgid "You can complete the following shelving tasks:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml53(term)
-msgid "Shelve an instance"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml54(para)
-msgid ""
-"Shuts down the instance, and stores it together with associated data and "
-"resources (a snapshot is taken if not volume backed). Anything in memory is "
-"lost. Use the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml57(replaceable)
-#: ./doc/common/section_cli_nova_startstop.xml62(replaceable)
-#: ./doc/common/section_cli_nova_startstop.xml69(replaceable)
-msgid "SERVERNAME"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml60(term)
-msgid "Unshelve an instance"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml61(para)
-msgid "Restores the instance:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml65(term)
-msgid "Remove a shelved instance"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml66(para)
-msgid ""
-"Removes the instance from the server; data and resource associations are "
-"deleted. If an instance is no longer needed, you can move that instance off "
-"the hypervisor in order to minimize resource usage:"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-components.xml43(None)
-msgid ""
-"@@image: '../common/figures/objectstorage-buildingblocks.png'; "
-"md5=ed79466c8464513dbeaf1e0954280e5e"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-components.xml86(None)
-msgid ""
-"@@image: '../common/figures/objectstorage-ring.png'; "
-"md5=a94e26734cec6980c3684d9e824eac2d"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-components.xml126(None)
-msgid ""
-"@@image: '../common/figures/objectstorage-zones.png'; "
-"md5=1b1dc0abe6ea0c516f22ce399deb75ed"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-components.xml144(None)
-msgid ""
-"@@image: '../common/figures/objectstorage-accountscontainers.png'; "
-"md5=4b15e5a202db5bde53c9b369058aeab8"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-components.xml169(None)
-msgid ""
-"@@image: '../common/figures/objectstorage-partitions.png'; "
-"md5=2c161c2e92d6fefc8140ec86e79e9492"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-components.xml195(None)
-msgid ""
-"@@image: '../common/figures/objectstorage-replication.png'; "
-"md5=9d55594d7f445764569ab04d8d4373b2"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-components.xml222(None)
-msgid ""
-"@@image: '../common/figures/objectstorage-usecase.png'; "
-"md5=07480e7175b383171173775fb96d70d7"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml7(title)
-msgid "Components"
-msgstr "Composants "
-
-#: ./doc/common/section_objectstorage-components.xml8(para)
-msgid ""
-"The components that enable Object Storage to deliver high availability, high"
-" durability, and high concurrency are:"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml12(para)
-msgid ""
-"<emphasis role=\"bold\">Proxy servers.</emphasis> Handle all of the incoming"
-" API requests."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml16(para)
-msgid ""
-"<emphasis role=\"bold\">Rings.</emphasis> Map logical names of data to "
-"locations on particular disks."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml20(para)
-msgid ""
-"<emphasis role=\"bold\">Zones.</emphasis> Isolate data from other zones. A "
-"failure in one zone doesn’t impact the rest of the cluster because data is "
-"replicated across zones."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml25(para)
-msgid ""
-"<emphasis role=\"bold\">Accounts and containers.</emphasis> Each account and"
-" container are individual databases that are distributed across the cluster."
-" An account database contains the list of containers in that account. A "
-"container database contains the list of objects in that container."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml31(para)
-msgid "<emphasis role=\"bold\">Objects.</emphasis> The data itself."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml34(para)
-msgid ""
-"<emphasis role=\"bold\">Partitions.</emphasis> A partition stores objects, "
-"account databases, and container databases and helps manage locations where "
-"data lives in the cluster."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml40(title)
-msgid "Object Storage building blocks"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml48(title)
-msgid "Proxy servers"
-msgstr "Serveurs proxy"
-
-#: ./doc/common/section_objectstorage-components.xml49(para)
-msgid ""
-"Proxy servers are the public face of Object Storage and handle all of the "
-"incoming API requests. Once a proxy server receives a request, it determines"
-" the storage node based on the object's URL, for example, "
-"https://swift.example.com/v1/account/container/object. Proxy servers also "
-"coordinate responses, handle failures, and coordinate timestamps."
-msgstr "Les serveurs proxy sont la face publique de l'Object Storage et gèrent toutes les requêtes de l'API entrantes. Une fois qu'un serveur proxy reçoit une requête, il détermine le nœud de stockage basée sur l'URL de l'objet, par exemple, https://swift.example.com/v1/account/container/object. Les serveurs proxy coordonnent également les réponses, gèrent les échecs, et coordonnent les horodateurs."
-
-#: ./doc/common/section_objectstorage-components.xml54(para)
-msgid ""
-"Proxy servers use a shared-nothing architecture and can be scaled as needed "
-"based on projected workloads. A minimum of two proxy servers should be "
-"deployed for redundancy. If one proxy server fails, the others take over."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml59(title)
-msgid "Rings"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml60(para)
-msgid ""
-"A ring represents a mapping between the names of entities stored on disk and"
-" their physical locations. There are separate rings for accounts, "
-"containers, and objects. When other components need to perform any operation"
-" on an object, container, or account, they need to interact with the "
-"appropriate ring to determine their location in the cluster."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml65(para)
-msgid ""
-"The ring maintains this mapping using zones, devices, partitions, and "
-"replicas. Each partition in the ring is replicated, by default, three times "
-"across the cluster, and partition locations are stored in the mapping "
-"maintained by the ring. The ring is also responsible for determining which "
-"devices are used for handoff in failure scenarios."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml70(para)
-msgid ""
-"Data can be isolated into zones in the ring. Each partition replica is "
-"guaranteed to reside in a different zone. A zone could represent a drive, a "
-"server, a cabinet, a switch, or even a data center."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml73(para)
-msgid ""
-"The partitions of the ring are equally divided among all of the devices in "
-"the Object Storage installation. When partitions need to be moved around "
-"(for example, if a device is added to the cluster), the ring ensures that a "
-"minimum number of partitions are moved at a time, and only one replica of a "
-"partition is moved at a time."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml77(para)
-msgid ""
-"Weights can be used to balance the distribution of partitions on drives "
-"across the cluster. This can be useful, for example, when differently sized "
-"drives are used in a cluster."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml80(para)
-msgid ""
-"The ring is used by the proxy server and several background processes (like "
-"replication)."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml83(title)
-msgid "The <emphasis role=\"bold\">ring</emphasis>"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml90(para)
-msgid ""
-"These rings are externally managed, in that the server processes themselves "
-"do not modify the rings, they are instead given new rings modified by other "
-"tools."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml92(para)
-msgid ""
-"The ring uses a configurable number of bits from a path’s MD5 hash as a "
-"partition index that designates a device. The number of bits kept from the "
-"hash is known as the partition power, and 2 to the partition power indicates"
-" the partition count. Partitioning the full MD5 hash ring allows other parts"
-" of the cluster to work in batches of items at once which ends up either "
-"more efficient or at least less complex than working with each item "
-"separately or the entire cluster all at once."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml101(para)
-msgid ""
-"Another configurable value is the replica count, which indicates how many of"
-" the partition-device assignments make up a single ring. For a given "
-"partition number, each replica’s device will not be in the same zone as any "
-"other replica's device. Zones can be used to group devices based on physical"
-" locations, power separations, network separations, or any other attribute "
-"that would improve the availability of multiple replicas at the same time."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml109(title)
-#: ./doc/common/section_objectstorage-components.xml123(title)
-msgid "Zones"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml110(para)
-msgid ""
-"Object Storage allows configuring zones in order to isolate failure "
-"boundaries. Each data replica resides in a separate zone, if possible. At "
-"the smallest level, a zone could be a single drive or a grouping of a few "
-"drives. If there were five object storage servers, then each server would "
-"represent its own zone. Larger deployments would have an entire rack (or "
-"multiple racks) of object servers, each representing a zone. The goal of "
-"zones is to allow the cluster to tolerate significant outages of storage "
-"servers without losing all replicas of the data."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml117(para)
-msgid ""
-"As mentioned earlier, everything in Object Storage is stored, by default, "
-"three times. Swift will place each replica \"as-uniquely-as-possible\" to "
-"ensure both high availability and high durability. This means that when "
-"chosing a replica location, Object Storage chooses a server in an unused "
-"zone before an unused server in a zone that already has a replica of the "
-"data."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml130(para)
-msgid ""
-"When a disk fails, replica data is automatically distributed to the other "
-"zones to ensure there are three copies of the data."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml134(title)
-#: ./doc/common/section_objectstorage-components.xml141(title)
-msgid "Accounts and containers"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml135(para)
-msgid ""
-"Each account and container is an individual SQLite database that is "
-"distributed across the cluster. An account database contains the list of "
-"containers in that account. A container database contains the list of "
-"objects in that container."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml148(para)
-msgid ""
-"To keep track of object data locations, each account in the system has a "
-"database that references all of its containers, and each container database "
-"references each object."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml153(title)
-#: ./doc/common/section_objectstorage-components.xml166(title)
-msgid "Partitions"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml154(para)
-msgid ""
-"A partition is a collection of stored data, including account databases, "
-"container databases, and objects. Partitions are core to the replication "
-"system."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml156(para)
-msgid ""
-"Think of a partition as a bin moving throughout a fulfillment center "
-"warehouse. Individual orders get thrown into the bin. The system treats that"
-" bin as a cohesive entity as it moves throughout the system. A bin is easier"
-" to deal with than many little things. It makes for fewer moving parts "
-"throughout the system."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml160(para)
-msgid ""
-"System replicators and object uploads/downloads operate on partitions. As "
-"the system scales up, its behavior continues to be predictable because the "
-"number of partitions is a fixed number."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml163(para)
-msgid ""
-"Implementing a partition is conceptually simple, a partition is just a "
-"directory sitting on a disk with a corresponding hash table of what it "
-"contains."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml175(title)
-msgid "Replicators"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml176(para)
-msgid ""
-"In order to ensure that there are three copies of the data everywhere, "
-"replicators continuously examine each partition. For each local partition, "
-"the replicator compares it against the replicated copies in the other zones "
-"to see if there are any differences."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml180(para)
-msgid ""
-"The replicator knows if replication needs to take place by examining hashes."
-" A hash file is created for each partition, which contains hashes of each "
-"directory in the partition. Each of the three hash files is compared. For a "
-"given partition, the hash files for each of the partition's copies are "
-"compared. If the hashes are different, then it is time to replicate, and the"
-" directory that needs to be replicated is copied over."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml186(para)
-msgid ""
-"This is where partitions come in handy. With fewer things in the system, "
-"larger chunks of data are transferred around (rather than lots of little TCP"
-" connections, which is inefficient) and there is a consistent number of "
-"hashes to compare."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml189(para)
-msgid ""
-"The cluster eventually has a consistent behavior where the newest data has a"
-" priority."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml199(para)
-msgid ""
-"If a zone goes down, one of the nodes containing a replica notices and "
-"proactively copies data to a handoff location."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml203(title)
-msgid "Use cases"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml204(para)
-msgid ""
-"The following sections show use cases for object uploads and downloads and "
-"introduce the components."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml206(title)
-msgid "Upload"
-msgstr "Mettre en ligne"
-
-#: ./doc/common/section_objectstorage-components.xml207(para)
-msgid ""
-"A client uses the REST API to make a HTTP request to PUT an object into an "
-"existing container. The cluster receives the request. First, the system must"
-" figure out where the data is going to go. To do this, the account name, "
-"container name, and object name are all used to determine the partition "
-"where this object should live."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml211(para)
-msgid ""
-"Then a lookup in the ring figures out which storage nodes contain the "
-"partitions in question."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml213(para)
-msgid ""
-"The data is then sent to each storage node where it is placed in the "
-"appropriate partition. At least two of the three writes must be successful "
-"before the client is notified that the upload was successful."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml216(para)
-msgid ""
-"Next, the container database is updated asynchronously to reflect that there"
-" is a new object in it."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml219(title)
-msgid "Object Storage in use"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml228(title)
-msgid "Download"
-msgstr "Télécharger"
-
-#: ./doc/common/section_objectstorage-components.xml229(para)
-msgid ""
-"A request comes in for an account/container/object. Using the same "
-"consistent hashing, the partition name is generated. A lookup in the ring "
-"reveals which storage nodes contain that partition. A request is made to one"
-" of the storage nodes to fetch the object and, if that fails, requests are "
-"made to the other nodes."
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml10(title)
-msgid "Storage concepts"
-msgstr "Concepts de stockage"
-
-#: ./doc/common/section_storage-concepts.xml11(para)
-msgid "The OpenStack stack uses the following storage types:"
-msgstr "La pile OpenStack utilise diverses formes de stockage, ce qui peut troubler même les ingénieurs cloud expérimentés. Le tableau suivant décrit les types de stockage :"
-
-#: ./doc/common/section_storage-concepts.xml13(caption)
-msgid "Storage types"
-msgstr "La pile OpenStack utilise diverses formes de stockage, ce qui peut troubler même les ingénieurs cloud expérimentés. Le tableau suivant décrit les types de stockage :"
-
-#: ./doc/common/section_storage-concepts.xml19(td)
-msgid "On-instance / ephemeral"
-msgstr "Sur-instance / éphémère"
-
-#: ./doc/common/section_storage-concepts.xml20(td)
-msgid "Block storage (cinder)"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml26(td)
-msgid "Runs operating systems and provides scratch space"
-msgstr "Exécute les systèmes d’exploitation et fournit de l’espace scratch"
-
-#: ./doc/common/section_storage-concepts.xml27(td)
-msgid ""
-"Used for adding additional persistent storage to a virtual machine (VM)"
-msgstr "Utilisé pour ajouter du stockage persistant additionnel à une machine virtuelle (VM)"
-
-#: ./doc/common/section_storage-concepts.xml29(td)
-msgid "Used for storing virtual machine images and data"
-msgstr "Utilisé pour stocker des images de machines virtuelles et des données"
-
-#: ./doc/common/section_storage-concepts.xml32(td)
-msgid "Persists until VM is terminated"
-msgstr "Persiste jusqu’à ce que la VM soit éteinte"
-
-#: ./doc/common/section_storage-concepts.xml33(td)
-#: ./doc/common/section_storage-concepts.xml34(td)
-msgid "Persists until deleted"
-msgstr "Persiste jusqu’à l’effacement"
-
-#: ./doc/common/section_storage-concepts.xml37(td)
-#: ./doc/common/section_storage-concepts.xml38(td)
-msgid "Access associated with a VM"
-msgstr "Accès associé à une VM"
-
-#: ./doc/common/section_storage-concepts.xml39(td)
-msgid "Available from anywhere"
-msgstr "Disponible depuis partout"
-
-#: ./doc/common/section_storage-concepts.xml42(td)
-msgid "Implemented as a filesystem underlying OpenStack Compute"
-msgstr "Implémenté en tant que système de fichiers sous-jacent à OpenStack Compute"
-
-#: ./doc/common/section_storage-concepts.xml44(td)
-msgid ""
-"Mounted via OpenStack Block Storage controlled protocol (for example, iSCSI)"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml46(td)
-msgid "REST API"
-msgstr "REST API"
-
-#: ./doc/common/section_storage-concepts.xml49(td)
-msgid "Administrator configures size setting, based on flavors"
-msgstr "Administrateur configure le paramètre de taille, en se basant sur les types d'instances"
-
-#: ./doc/common/section_storage-concepts.xml51(td)
-msgid "Sizings based on need"
-msgstr "Dimensionnements basés sur le besoin"
-
-#: ./doc/common/section_storage-concepts.xml52(td)
-msgid "Easily scalable for future growth"
-msgstr "Facilement redimensionnable en vue d’une croissance future"
-
-#: ./doc/common/section_storage-concepts.xml55(td)
-msgid "Example: 10GB first disk, 30GB/core second disk"
-msgstr "Exemple: 10GB premier disque, 30GB/core second disque"
-
-#: ./doc/common/section_storage-concepts.xml56(td)
-msgid "Example: 1TB \"extra hard drive\""
-msgstr "Exemple: 1TB \"disque dur supplémentaire\""
-
-#: ./doc/common/section_storage-concepts.xml57(td)
-msgid "Example: 10s of TBs of data set storage"
-msgstr "Exemple: Des dizaines de TB de stockage destiné aux données"
-
-#: ./doc/common/section_storage-concepts.xml64(para)
-msgid ""
-"<emphasis>You cannot use OpenStack Object Storage like a traditional hard "
-"drive.</emphasis> The Object Storage relaxes some of the constraints of a "
-"POSIX-style file system to get other gains. You can access the objects "
-"through an API which uses HTTP. Subsequently you don't have to provide "
-"atomic operations (that is, relying on eventual consistency), you can scale "
-"a storage system easily and avoid a central point of failure."
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml73(para)
-msgid ""
-"<emphasis>The OpenStack Image Service is used to manage the virtual machine "
-"images in an OpenStack cluster, not store them.</emphasis> It provides an "
-"abstraction to different methods for storage - a bridge to the storage, not "
-"the storage itself."
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml80(para)
-msgid ""
-"<emphasis>The OpenStack Object Storage can function on its own.</emphasis> "
-"The Object Storage (swift) product can be used independently of the Compute "
-"(nova) product."
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml62(para)
-msgid "You should note that:<placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml6(title)
-msgid "Launch instances"
-msgstr "Lancer les instances"
-
-#: ./doc/common/section_cli_nova_boot.xml7(para)
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml8(para)
-msgid "Instances are virtual machines that run inside the cloud."
-msgstr "Les instances sont des machines virtuelles individuelles qui tournent dans le cloud."
-
-#: ./doc/common/section_cli_nova_boot.xml9(para)
-msgid "Before you can launch an instance, gather the following parameters:"
-msgstr "Avant de lancer une instance, ramassez les paramètres suivants:"
-
-#: ./doc/common/section_cli_nova_boot.xml13(para)
-msgid ""
-"The <emphasis role=\"bold\">instance source</emphasis> can be an image, "
-"snapshot, or block storage volume that contains an image or snapshot."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml18(para)
-msgid "A <emphasis role=\"bold\">name</emphasis> for your instance."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml21(para)
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml37(para)
-msgid ""
-"The <emphasis role=\"bold\">flavor</emphasis> for your instance, which "
-"defines the compute, memory, and storage capacity of nova computing "
-"instances. A flavor is an available hardware configuration for a server. It "
-"defines the size of a virtual server that can be launched."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml29(para)
-msgid ""
-"Any <emphasis role=\"bold\">user data</emphasis> files. A user data file is "
-"a special key in the metadata service that holds a file that cloud-aware "
-"applications in the guest instance can access. For example, one application "
-"that uses user data is the <link "
-"href=\"https://help.ubuntu.com/community/CloudInit\">cloud-init</link> "
-"system, which is an open-source package from Ubuntu that is available on "
-"various Linux distributions and that handles early initialization of a cloud"
-" instance."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml42(para)
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml45(para)
-msgid ""
-"Access and security credentials, which include one or both of the following "
-"credentials:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml46(para)
-msgid ""
-"A <emphasis role=\"bold\">key pair</emphasis> for your instance, which are "
-"SSH credentials that are injected into images when they are launched. For "
-"the key pair to be successfully injected, the image must contain the "
-"<literal>cloud-init</literal> package. Create at least one key pair for each"
-" project. If you already have generated a key pair with an external tool, "
-"you can import it into OpenStack. You can use the key pair for multiple "
-"instances that belong to that project."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml60(para)
-msgid ""
-"A <emphasis role=\"bold\">security group</emphasis> that defines which "
-"incoming network traffic is forwarded to instances. Security groups hold a "
-"set of firewall policies, known as <emphasis role=\"italic\">security group "
-"rules</emphasis>."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml71(para)
-msgid ""
-"If needed, you can assign a <emphasis role=\"bold\">floating (public) IP "
-"address</emphasis> to a running instance."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml76(para)
-msgid ""
-"You can also attach a block storage device, or <emphasis "
-"role=\"bold\">volume</emphasis>, for persistent storage."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml82(para)
-msgid ""
-"Instances that use the default security group cannot, by default, be "
-"accessed from any IP address outside of the cloud. If you want those IP "
-"addresses to access the instances, you must modify the rules for the default"
-" security group."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml87(para)
-msgid ""
-"You can also assign a floating IP address to a running instance to make it "
-"accessible from outside the cloud. See <xref "
-"linkend=\"manage_ip_addresses\"/>."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml91(para)
-msgid ""
-"After you gather the parameters that you need to launch an instance, you can"
-" launch it from an <link linkend=\"launch_from_image\">image</link> or a "
-"<link linkend=\"boot_from_volume\">volume</link>. You can launch an instance"
-" directly from one of the available OpenStack images or from an image that "
-"you have copied to a persistent volume. The OpenStack Image Service provides"
-" a pool of images that are accessible to members of different projects."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml101(title)
-msgid "Gather parameters to launch an instance"
-msgstr "Pour lancer une instance, ramassez les paramètres"
-
-#: ./doc/common/section_cli_nova_boot.xml103(para)
-msgid "Before you begin, source the OpenStack RC file."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml108(para)
-msgid "Note the ID of the flavor that you want to use for your instance:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml123(para)
-msgid "Note the ID of the image from which you want to boot your instance:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml131(para)
-msgid ""
-"You can also filter the image list by using <placeholder-1/> to find a "
-"specific image, as follows:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml138(para)
-msgid "List the available security groups:"
-msgstr "Listez les groupes de sécurité disponibles:"
-
-#: ./doc/common/section_cli_nova_boot.xml140(para)
-msgid ""
-"If you are an admin user, specify the <option>--all-tenants</option> "
-"parameter to list groups for all tenants."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml145(para)
-msgid ""
-"Note the ID of the security group that you want to use for your instance:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml151(para)
-msgid ""
-"If you have not created any security groups, you can assign the instance to "
-"only the default security group."
-msgstr "Si vous n'avez pas créer de groupe de sécurité, vous ne pourrez qu'assigner l'instance au groupe de sécurité par défaut."
-
-#: ./doc/common/section_cli_nova_boot.xml154(para)
-msgid "You can view rules for a specified security group:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml159(para)
-msgid ""
-"List the available key pairs and note the name of the key pair that you use "
-"for SSH access."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml168(title)
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml6(title)
-msgid "Launch an instance from an image"
-msgstr "Lancer une instance depuis une image"
-
-#: ./doc/common/section_cli_nova_boot.xml171(para)
-msgid ""
-"After you gather required parameters, run the following command to launch an"
-" instance. Specify the server name, flavor ID, and image ID."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml174(para)
-msgid ""
-"Optionally, you can provide a key name for access control and a security "
-"group for security. You can also include metadata key and value pairs. For "
-"example, you can add a description for your server by providing the "
-"<parameter>--meta description=\"My Server\"</parameter> parameter."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml181(para)
-msgid ""
-"You can pass user data in a local file at instance launch by using the "
-"<parameter>--user-data <replaceable>USER-DATA-FILE</replaceable></parameter>"
-" parameter."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml186(replaceable)
-msgid "FLAVOR_ID"
-msgstr "FLAVOR_ID"
-
-#: ./doc/common/section_cli_nova_boot.xml186(replaceable)
-msgid "KEY_NAME"
-msgstr "KEY_NAME"
-
-#: ./doc/common/section_cli_nova_boot.xml187(replaceable)
-msgid "USER_DATA_FILE"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml187(replaceable)
-msgid "SEC_GROUP"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml187(replaceable)
-msgid "KEY=VALUE"
-msgstr "KEY=VALUE"
-
-#: ./doc/common/section_cli_nova_boot.xml189(para)
-msgid ""
-"The following command launches the <literal>MyCirrosServer</literal> "
-"instance with the <literal>m1.small</literal> flavor (ID of "
-"<literal>1</literal>), <literal>cirros-0.3.2-x86_64-uec</literal> image (ID "
-"of <literal>397e713c-b95b-4186-ad46-6126863ea0a9</literal>), "
-"<literal>default</literal> security group, <literal>KeyPair01</literal> key,"
-" and a user data file called <filename>cloudinit.file</filename>:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml202(replaceable)
-msgid "myCirrosServer"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml203(para)
-msgid ""
-"Depending on the parameters that you provide, the command returns a list of "
-"server properties."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml206(para)
-msgid ""
-"A status of <literal>BUILD</literal> indicates that the instance has "
-"started, but is not yet online."
-msgstr "L'état <literal>BUILD</literal> indique que l'instance a demarré, mais qu'elle n'est pas en ligne."
-
-#: ./doc/common/section_cli_nova_boot.xml209(para)
-msgid ""
-"A status of <literal>ACTIVE</literal> indicates that the instance is active."
-msgstr "L'état <literal>ACTIVE</literal> indique que l'instance est active."
-
-#: ./doc/common/section_cli_nova_boot.xml241(para)
-msgid ""
-"Copy the server ID value from the <literal>id</literal> field in the output."
-" You use this ID to get details for or delete your server."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml245(para)
-msgid ""
-"Copy the administrative password value from the <literal>adminPass</literal>"
-" field. You use this value to log in to your server."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml249(para)
-msgid ""
-"You can also place arbitrary local files into the instance file system at "
-"creation time by using the <option>--file &lt;dst-path=src-path&gt;</option>"
-" option. You can store up to five files. For example, if you have a special "
-"authorized keys file named <filename>special_authorized_keysfile</filename> "
-"that you want to put on the instance rather than using the regular SSH key "
-"injection, you can use the <option>--file</option> option as shown in the "
-"following example:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml266(para)
-msgid "Check if the instance is online:"
-msgstr "Vérifier que l'instance est en ligne:"
-
-#: ./doc/common/section_cli_nova_boot.xml268(para)
-msgid ""
-"The list shows the ID, name, status, and private (and if assigned, public) "
-"IP addresses for all instances in the project to which you belong:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml278(para)
-msgid "If the status for the instance is ACTIVE, the instance is online."
-msgstr "Si l'état de l'instance est actif, l'instance est en ligne."
-
-#: ./doc/common/section_cli_nova_boot.xml280(para)
-msgid ""
-"To view the available options for the <placeholder-1/> command, run the "
-"following command:"
-msgstr "Pour voir les options disponibles pour la <placeholder-1/> commande, exécutez la commande suivante: "
-
-#: ./doc/common/section_cli_nova_boot.xml287(para)
-msgid ""
-"If you did not provide a key pair, security groups, or rules, you can access"
-" the instance only from inside the cloud through VNC. Even pinging the "
-"instance is not possible."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml6(title)
-msgid "Integrate Identity with LDAP"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml7(para)
-msgid ""
-"Identity Service supports integration with an existing LDAP directory for "
-"authentication and authorization services."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml11(para)
-msgid ""
-"For OpenStack Identity to access an LDAP back end, you must enable the "
-"<option>authlogin_nsswitch_use_ldap</option> boolean value for SELinux on "
-"the Identity server. To enable and make the option persistent across "
-"reboots:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml18(para)
-msgid "You can integrate Identity with a single LDAP server."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml21(para)
-msgid ""
-"To configure Identity, set options in the "
-"<filename>/etc/keystone/keystone.conf</filename> file. Modify these examples"
-" as needed."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml25(title)
-msgid "To integrate Identity with LDAP"
-msgstr ""
+"The cloud operator assigns roles to users. Roles determine who can upload "
+"and manage images. The operator might restrict image upload and management "
+"to only cloud administrators or operators."
+msgstr "L'opérateur du cloud assigne des rôles aux utilisateurs. Les rôles déterminent qui peut télécharger et gérer des images. L'opérateur pourrait restreindre le téléchargement d'images et de gestion uniquement pour les administrateurs du cloud ou les opérateurs."
 
-#: ./doc/common/section_keystone_config_ldap.xml27(para)
-msgid "Enable the LDAP driver in the <filename>keystone.conf</filename> file:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml34(para)
-msgid ""
-"Define the destination LDAP server in the <filename>keystone.conf</filename>"
-" file:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml45(para)
-msgid ""
-"Create the organizational units (OU) in the LDAP directory, and define their"
-" corresponding location in the <filename>keystone.conf</filename> file:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml58(para)
-msgid ""
-"These schema attributes are extensible for compatibility with various "
-"schemas. For example, this entry maps to the <systemitem>person</systemitem>"
-" attribute in Active Directory:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml67(para)
-msgid ""
-"A read-only implementation is recommended for LDAP integration. These "
-"permissions are applied to object types in the "
-"<filename>keystone.conf</filename> file:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml85(para)
-msgid "Restart the Identity service:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml87(para)
-msgid ""
-"During service restart, authentication and authorization are unavailable."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml92(title)
-msgid "Additional LDAP integration settings"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml93(para)
-msgid "Set these options in the <filename>keystone.conf</filename> file."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml98(term)
-msgid "Filters"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml100(para)
-msgid "Use filters to control the scope of data presented through LDAP."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml109(term)
-msgid "LDAP Account Status"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml111(para)
-msgid ""
-"Mask account status values for compatibility with various directory "
-"services. Superfluous accounts are filtered with "
-"<systemitem>user_filter</systemitem>."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml115(para)
-msgid ""
-"For example, you can mask Active Directory account status attributes in the "
-"<filename>keystone.conf</filename> file:"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml106(None)
-msgid ""
-"@@image: 'figures/launch_instances.png'; "
-"md5=8a7e6864bce97f6478db572daf3ef5de"
-msgstr "@@image: 'figures/launch_instances.png'; md5=8a7e6864bce97f6478db572daf3ef5de"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml164(None)
-msgid "@@image: 'figures/instances.png'; md5=6b0f5cb3009d447334ff8b5c5b2cd121"
-msgstr "@@image: 'figures/instances.png'; md5=6b0f5cb3009d447334ff8b5c5b2cd121"
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml10(para)
-msgid ""
-"You can launch an instance directly from one of the available OpenStack "
-"images. The OpenStack Image Service provides a pool of images that are "
-"accessible to members of different projects. When you launch an instance "
-"from an image, OpenStack creates a local copy of the image on the respective"
-" compute node where the instance is started."
-msgstr "Vous pouvez lancer une instance directement depuis l'une des images OpenStack qui sont disponibles. Le service d'Images OpenStack met à disposition un pool d'images qui sont accessible aux membres des différents projets. Quand vous lancez une instance depuis une image, OpenStack crée une copie locale de l'image sur le nœud de calcul respectif où l'instance est démarrée.  "
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml16(para)
-msgid ""
-"Alternatively, you can launch an instance from an image that you have copied"
-" to a persistent volume."
-msgstr "Autrement, vous pouvez lancer une instance à partird'une image qui a été copiée sur un volume persistent."
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml18(para)
-msgid "To launch an instance, specify the following parameters:"
-msgstr "Pour lancer une instance, spécifiez les paramètres suivants:"
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml22(para)
-msgid ""
-"The <guilabel>instance source</guilabel>, which is an image or snapshot. "
-"Alternatively, you can boot from a volume, which is block storage, to which "
-"you've copied an image or snapshot."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml28(para)
-msgid ""
-"The <guilabel>image</guilabel> or <guilabel>snapshot</guilabel>, which "
-"represents the operating system."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml33(para)
-msgid "A <guilabel>name</guilabel> for your instance."
-msgstr "Un <guilabel>name</guilabel> pour votre instance."
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml49(para)
-msgid ""
-"A <emphasis role=\"bold\">keypair</emphasis> for your instance, which are "
-"SSH credentials that are injected into images when they are launched. For "
-"this to work, the image must contain the <literal>cloud-init</literal> "
-"package. Create at least one keypair for each project. If you already have "
-"generated a keypair with an external tool, you can import it into OpenStack."
-" You can use the keypair for multiple instances that belong to that project."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml62(para)
-msgid ""
-"A <emphasis role=\"bold\">security group</emphasis>, which defines which "
-"incoming network traffic is forwarded to instances. Security groups hold a "
-"set of firewall policies, known as <emphasis role=\"italic\">security group "
-"rules</emphasis>."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml73(para)
-msgid ""
-"If needed, you can assign a <emphasis role=\"bold\">floating (public) IP "
-"address</emphasis> to a running instance and attach a block storage device, "
-"or volume, for persistent storage."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml80(title)
-msgid "To launch an instance:"
-msgstr "Pour lancer une instance"
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml82(para)
-msgid "Log in to the OpenStack dashboard."
-msgstr "Connectez-vous au tableau de bord OpenStack"
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml85(para)
-msgid ""
-"If you are a member of multiple projects, select a project from the drop-"
-"down list at the top of the <guilabel>Project</guilabel> tab."
-msgstr "Si vous êtes membre de multiple projets, selectionnez un projet de la liste déroulante en tête de l'onglet <guilabel>Project</guilabel>."
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml90(para)
-msgid "Click the <guilabel>Images &amp; Snapshot</guilabel> category."
-msgstr "Cliquez sur la catégorie <guilabel>Images &amp; Snapshot</guilabel>."
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml92(para)
+#: ./doc/common/section_cli_glance_manage_images.xml12(para)
 msgid ""
-"The dashboard shows the images that have been uploaded to OpenStack Image "
-"Service and are available for this project."
-msgstr "Le tableau de bord affiche les images qui ont été téléchargé  sur le Service d'Image OpenStack et qui sont disponibles pour ce projet."
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml100(title)
-msgid "OpenStack dashboard - Launch Instances window"
-msgstr "Tableau de bord OpenStack - Fenêtre du lancement des instances"
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml97(para)
-msgid ""
-"Select an image and click <guibutton>Launch</guibutton>. The "
-"<guilabel>Launch Image</guilabel> window appears: <placeholder-1/>"
-msgstr "Sélectionnez une image et cliquez sur <guibutton>Launch</guibutton>. La fenêtre  <guilabel>Launch Image</guilabel> s'affiche: <placeholder-1/>"
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml112(para)
-msgid "Specify the following parameters:"
-msgstr "Spécifiez les paramètres suivants:"
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml116(para)
-msgid "Enter an instance name to assign to the virtual machine."
-msgstr "Entrer le nom d'une instance pour l'assigner à la machine virtuel."
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml120(para)
-msgid ""
-"From the <guilabel>Flavor</guilabel> drop-down list, select the size of the "
-"virtual machine to launch."
-msgstr "A partir de la liste déroulante <guilabel>Flavor</guilabel>, sélectionnez la taille de la machine virtuelle à lancer."
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml125(para)
-msgid "Optionally, select a keypair."
-msgstr "Facultativement, choisissez une paire de clés."
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml126(para)
-msgid ""
-"In case an image uses a static root password or a static key set (neither is"
-" recommended), you do not need to provide a keypair on starting the "
-"instance."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml132(para)
-msgid ""
-"In <guilabel>Instance Count</guilabel>, enter the number of virtual machines"
-" to launch from this image."
-msgstr "Dans <guilabel>Instance Count</guilabel>, entrez le nombre de machines virtuelles à lancer depuis cette instance."
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml137(para)
-msgid ""
-"Assign the instance to the default security group. If you added rules to "
-"this group, the instance implements these rules."
-msgstr "Assignez l'instance au groupe de sécurité par défaut. Si vous ajoutez des règles à ce groupe, l'instance met en oeuvre ces règles."
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml150(para)
-msgid ""
-"Click <guibutton>Launch Instance</guibutton>. The instance is launched on "
-"any of the compute nodes in the cloud."
-msgstr "Cliquez sur <guibutton>Launch Instance</guibutton>. L'instance est lancé sur n'importe quel nœud de calcul dans le cloud. "
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml155(para)
-msgid ""
-"After you have launched an instance, switch to the <guilabel>Instances &amp;"
-" Volumes</guilabel> category to view the instance name, its (private or "
-"public) IP address, size, status, task, and power state."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml160(title)
-msgid "OpenStack dashboard - Instances"
-msgstr "Tableau de bord OpenStack - Instances"
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml168(para)
-msgid ""
-"If you did not provide a keypair on starting and have not touched security "
-"groups or rules so far, by default the instance can only be accessed from "
-"inside the cloud through VNC at this point. Even pinging the instance is not"
-" possible."
-msgstr "Si vous ne fournissez pas de paire de clés, de groupes de sécurités, ou de règles jusqu'ici, les utilisateurs ne peuvent accéder à l'instance qu'à partir du cloud par VNC. Même pinger l'instance n'est pas possible."
-
-#: ./doc/common/section_identity-troubleshooting.xml6(title)
-msgid "Troubleshoot the Identity service"
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml7(para)
-msgid ""
-"To troubleshoot the Identity service, review the logs in the "
-"<filename>/var/log/keystone/keystone.log</filename> file."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml10(para)
-msgid ""
-"Use the <filename>/etc/keystone/logging.conf</filename> file to configure "
-"the location of log files."
-msgstr "Utilisez le fichier <filename>/etc/keystone/logging.conf</filename> pour configurer la location des fichiers journaux. "
-
-#: ./doc/common/section_identity-troubleshooting.xml13(para)
-msgid ""
-"The logs show the components that have come in to the WSGI request, and "
-"ideally show an error that explains why an authorization request failed. If "
-"you do not see the request in the logs, run keystone with "
-"<parameter>--debug</parameter> parameter. Pass the "
-"<parameter>--debug</parameter> parameter before the command parameters."
+"You can upload images through the <placeholder-1/> client or the Image "
+"Service API. You can also use the <placeholder-2/> client to list images, "
+"set and delete image metadata, delete images, and take a snapshot of a "
+"running instance to create an image. After you upload an image, you cannot "
+"change it."
 msgstr ""
 
-#: ./doc/common/section_identity-troubleshooting.xml20(title)
-msgid "Debug PKI middleware"
-msgstr "Déboguer l'intergiciel PKI."
-
-#: ./doc/common/section_identity-troubleshooting.xml21(para)
-msgid ""
-"If you receive an <literal>Invalid OpenStack Identity Credentials</literal> "
-"message when you talk to an OpenStack service, it might be caused by the "
-"changeover from UUID tokens to PKI tokens in the Grizzly release. Learn how "
-"to troubleshoot this error."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml26(para)
-msgid ""
-"The PKI-based token validation scheme relies on certificates from Identity "
-"that are fetched through HTTP and stored in a local directory. The location "
-"for this directory is specified by the <literal>signing_dir</literal> "
-"configuration option. In your services configuration file, look for a "
-"section like this:"
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml41(para)
-msgid ""
-"If your service lacks this stanza, the <link "
-"href=\"https://github.com/openstack/python-"
-"keystoneclient/blob/master/keystoneclient/middleware/auth_token.py#L198\">keystoneclient/middleware/auth_token.py</link>"
-" file specifies the defaults. If no value is specified for this directory, "
-"it <link href=\"https://github.com/openstack/python-"
-"keystoneclient/blob/master/keystoneclient/middleware/auth_token.py#L299\">defaults"
-" to a secure temporary directory.</link> Initialization code for the service"
-" checks that the directory exists and is writable. If it does not exist, the"
-" code tries to create it. If this fails, the service fails to start. "
-"However, it often succeeds but problems occur later."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml53(para)
-msgid ""
-"The first thing to check is that the <literal>signing_dir</literal> does, in"
-" fact, exist. If it does, check for the presence of the certificate files "
-"inside there:"
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml64(para)
-msgid ""
-"This directory contains two certificates and the token revocation list. If "
-"these files are not present, your service cannot fetch them from Identity. "
-"To troubleshoot, try to talk to Identity to make sure it correctly serves "
-"files, as follows:"
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml70(para)
-msgid "This command fetches the signing certificate:"
-msgstr "Cette commande récupère le certificat de signature:"
-
-#: ./doc/common/section_identity-troubleshooting.xml81(para)
-msgid "Note the expiration dates of the certificate:"
-msgstr "Notez les dates d'expiration du certificat:"
-
-#: ./doc/common/section_identity-troubleshooting.xml84(para)
-msgid ""
-"The token revocation list is updated once a minute, but the certificates are"
-" not. One possible problem is that the certificates are the wrong files or "
-"garbage. You can remove these files and run another command against your "
-"server: They are fetched on demand."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml89(para)
+#: ./doc/common/section_cli_glance_manage_images.xml16(para)
 msgid ""
-"The Identity service log should show the access of the certificate files. "
-"You might have to turn up your logging levels. Set <literal>debug = "
-"True</literal> and <literal>verbose = True</literal> in your Identity "
-"configuration file and restart the Identity server."
-msgstr ""
+"For details about image creation, see the <link "
+"href=\"http://docs.openstack.org/image-guide/content/\"><citetitle>Virtual "
+"Machine Image Guide</citetitle></link>."
+msgstr "Pour plus de détails sur la création de l'image, voir le <link href=\"http://docs.openstack.org/image-guide/content/\"><citetitle>Virtual Machine Image Guide</citetitle></link>."
 
-#: ./doc/common/section_identity-troubleshooting.xml98(para)
-msgid ""
-"If the files do not appear in your directory after this, it is likely one of"
-" the following issues:"
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml21(title)
+msgid "List or get details for images (glance)"
+msgstr "Lister ou trouver les détails pour les images (glance)"
 
-#: ./doc/common/section_identity-troubleshooting.xml102(para)
+#: ./doc/common/section_cli_glance_manage_images.xml22(para)
 msgid ""
-"Your service is configured incorrectly and cannot talk to Identity. Check "
-"the <literal>auth_port</literal> and <literal>auth_host</literal> values and"
-" make sure that you can talk to that service through cURL, as shown "
-"previously."
+"To get a list of images and to then get further details about a single "
+"image, use <placeholder-1/> and <placeholder-2/>."
 msgstr ""
 
-#: ./doc/common/section_identity-troubleshooting.xml110(para)
+#: ./doc/common/section_cli_glance_manage_images.xml74(para)
 msgid ""
-"Your signing directory is not writable. Use the <placeholder-1/> command to "
-"change its permissions so that the service (POSIX) user can write to it. "
-"Verify the change through <placeholder-2/> and <placeholder-3/> commands."
+"When viewing a list of images, you can also use <placeholder-1/> to filter "
+"the list, as follows:"
 msgstr ""
 
-#: ./doc/common/section_identity-troubleshooting.xml118(para)
-msgid "The SELinux policy is denying access to the directory."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml122(para)
+#: ./doc/common/section_cli_glance_manage_images.xml80(para)
 msgid ""
-"SELinux troubles often occur when you use Fedora/RHEL-based packages and you"
-" choose configuration options that do not match the standard policy. Run the"
-" <placeholder-1/> command. If that makes a difference, you should relabel "
-"the directory. If you are using a sub-directory of the "
-"<filename>/var/cache/</filename> directory, run the following command:"
+"To store location metadata for images, which enables direct file access for "
+"a client, update the <filename>/etc/glance/glance.conf</filename> file with "
+"the following statements:"
 msgstr ""
 
-#: ./doc/common/section_identity-troubleshooting.xml131(para)
-msgid ""
-"If you are not using a <filename>/var/cache</filename> sub-directory, you "
-"should. Modify the <literal>signing_dir</literal> configuration option for "
-"your service and restart."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml87(code)
+msgid "show_multiple_locations = True"
+msgstr "show_multiple_locations = True"
 
-#: ./doc/common/section_identity-troubleshooting.xml135(para)
+#: ./doc/common/section_cli_glance_manage_images.xml90(para)
 msgid ""
-"Set back to <literal>setenforce enforcing</literal> to confirm that your "
-"changes solve the problem."
+"<code>filesystem_store_metadata_file = "
+"<replaceable>filePath</replaceable></code>, where "
+"<replaceable>filePath</replaceable> points to a JSON file that defines the "
+"mount point for OpenStack images on your system and a unique ID. For "
+"example: <placeholder-1/>"
 msgstr ""
 
-#: ./doc/common/section_identity-troubleshooting.xml137(para)
+#: ./doc/common/section_cli_glance_manage_images.xml102(para)
 msgid ""
-"If your certificates are fetched on demand, the PKI validation is working "
-"properly. Most likely, the token from Identity is not valid for the "
-"operation you are attempting to perform, and your user needs a different "
-"role for the operation."
+"After you restart the Image Service, you can use the following syntax to "
+"view the image's location information:"
 msgstr ""
 
-#: ./doc/common/section_identity-troubleshooting.xml144(title)
-msgid "Debug signing key file errors"
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml145(para)
-msgid ""
-"If an error occurs when the signing key file opens, it is possible that the "
-"person who ran the <placeholder-1/> command to generate certificates and "
-"keys did not use the correct user. When you run the <placeholder-2/> "
-"command, Identity generates a set of certificates and keys in "
-"<filename>/etc/keystone/ssl*</filename>, which is owned by root:root."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml103(replaceable)
+msgid "imageID"
+msgstr "imageID"
 
-#: ./doc/common/section_identity-troubleshooting.xml154(para)
+#: ./doc/common/section_cli_glance_manage_images.xml104(para)
 msgid ""
-"This can present a problem when you run the Identity daemon under the "
-"keystone user account (nologin) when you try to run PKI. Unless you run the "
-"<placeholder-1/> command against the files keystone:keystone or run the "
-"<placeholder-2/> command with the <parameter>--keystone-user</parameter> and"
-" <parameter>--keystone-group</parameter> parameters, you get an error, as "
+"For example, using the image ID shown above, you would issue the command as "
 "follows:"
 msgstr ""
 
-#: ./doc/common/section_identity-troubleshooting.xml172(title)
-msgid "Flush expired tokens from the token database table"
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml174(para)
-msgid ""
-"As you generate tokens, the token database table on the Identity server "
-"grows. To clear the token table, an administrative user must run the "
-"<placeholder-1/> command to flush the tokens. When you flush tokens, expired"
-" tokens are deleted and traceability is eliminated."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml180(para)
-msgid ""
-"Use <placeholder-1/> to schedule this command to run frequently based on "
-"your workload. For large workloads, running it every minute is recommended."
-msgstr ""
-
-#: ./doc/common/section_compute_config-firewalls.xml6(title)
-msgid "Compute service node firewall requirements"
-msgstr ""
-
-#: ./doc/common/section_compute_config-firewalls.xml7(para)
-msgid ""
-"Console connections for virtual machines, whether direct or through a proxy,"
-" are received on ports <literal>5900</literal> to <literal>5999</literal>. "
-"You must configure the firewall on each Compute service node to enable "
-"network traffic on these ports."
-msgstr ""
-
-#: ./doc/common/section_compute_config-firewalls.xml11(title)
-msgid "Configure the service-node firewall"
-msgstr ""
-
-#: ./doc/common/section_compute_config-firewalls.xml12(para)
-msgid ""
-"On the server that hosts the Compute service, log in as "
-"<systemitem>root</systemitem>."
-msgstr ""
-
-#: ./doc/common/section_compute_config-firewalls.xml14(para)
-msgid "Edit the <filename>/etc/sysconfig/iptables</filename> file."
-msgstr "Editer le fichier <filename>/etc/sysconfig/iptables</filename>."
-
-#: ./doc/common/section_compute_config-firewalls.xml20(para)
-msgid ""
-"Add an INPUT rule that allows TCP traffic on ports that range from "
-"<literal>5900</literal> to <literal>5999</literal>:"
-msgstr ""
-
-#: ./doc/common/section_compute_config-firewalls.xml26(para)
-msgid "The new rule must appear before any INPUT rules that REJECT traffic."
-msgstr ""
-
-#: ./doc/common/section_compute_config-firewalls.xml32(para)
-msgid ""
-"Save the changes to the <filename>/etc/sysconfig/iptables</filename> file."
-msgstr "Enregistrez les changements au fichier <filename>/etc/sysconfig/iptables</filename>."
-
-#: ./doc/common/section_compute_config-firewalls.xml38(para)
-msgid ""
-"Restart the <systemitem>iptables</systemitem> service to ensure that the "
-"change takes effect."
-msgstr "Redémarrer le service <systemitem>iptables</systemitem> pour être sûr que le changement fasse effet."
-
-#: ./doc/common/section_compute_config-firewalls.xml45(para)
-msgid ""
-"The <systemitem>iptables</systemitem> firewall now enables incoming "
-"connections to the Compute services. Repeat this process for each Compute "
-"service node."
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml6(title)
-msgid "Customize the dashboard"
-msgstr "Personalisez le tableau de bord"
-
-#: ./doc/common/section_dashboard_customizing.xml7(para)
-msgid ""
-"Adapted from <link href=\"http://www.prestonlee.com/2012/05/09/how-to-"
-"custom-brand-the-openstack-horizon-dashboard/\">How To Custom Brand The "
-"OpenStack “Horizon” Dashboard</link>."
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml11(para)
-msgid ""
-"You install the OpenStack dashboard through the <literal>openstack-"
-"dashboard</literal> package. You can customize the dashboard with your own "
-"colors, logo, and site title through a CSS file."
-msgstr "Vous installez le tableau de bord OpenStack à partir du paquetage <literal>openstack-dashboard</literal>. Vous pouvez personnaliser le tableau de bord avec vos propres couleurs, logo ou titre de site grâce à un fichier CSS."
-
-#: ./doc/common/section_dashboard_customizing.xml15(para)
-msgid ""
-"Canonical also provides an <literal>openstack-dashboard-ubuntu-"
-"theme</literal> package that brands the Python-based Django interface."
-msgstr "Canonical fournit aussi un paquetage <literal>openstack-dashboard-ubuntu-theme</literal> caractéristique de l'interface Django à base de Python."
-
-#: ./doc/common/section_dashboard_customizing.xml47(para)
-msgid ""
-"Create a graphical logo with a transparent background. The text "
-"<literal>TGen Cloud</literal> in this example is rendered through "
-"<filename>.png</filename> files of multiple sizes created with a graphics "
-"program."
-msgstr "Créez un logo graphique avec un fond transparent. Le texte <literal>TGen Cloud</literal>, dans cet exemple, est mis en valeur grâce à des fichiers <filename>.png</filename> de tailles diverses créés à l'aide d'un programme de création graphique."
-
-#: ./doc/common/section_dashboard_customizing.xml52(para)
-msgid ""
-"Use a 200×27 for the logged-in banner graphic, and 365×50 for the login "
-"screen graphic."
-msgstr "Utilisez une taille de 200x27 pour le graphique de la bannière une fois connecté, et 365x50 pour le graphique de l'encart d'ouverture de session."
-
-#: ./doc/common/section_dashboard_customizing.xml56(para)
-msgid ""
-"Set the HTML title, which appears at the top of the browser window, by "
-"adding the following line to <filename>/etc/openstack-"
-"dashboard/local_settings.py</filename>:"
-msgstr "Assignez à la fenêtre du navigateur le titre HTML apparaissant en haut en ajoutant la ligne suivante au fichier <filename>/etc/openstack-dashboard/local_settings.py</filename>: "
-
-#: ./doc/common/section_dashboard_customizing.xml59(code)
-msgid "SITE_BRANDING = \"Example, Inc. Cloud\""
-msgstr "SITE_BRANDING = \"Exemple, Inc. Cloud\""
-
-#: ./doc/common/section_dashboard_customizing.xml63(para)
-msgid ""
-"Upload your new graphic files to the following location: "
-"<filename>/usr/share/openstack-"
-"dashboard/openstack_dashboard/static/dashboard/img/</filename>"
-msgstr "Chargez sur le serveur vos nouveaux fichiers graphiques dans la zone : <filename>/usr/share/openstack-dashboard/openstack_dashboard/static/dashboard/img/</filename>"
-
-#: ./doc/common/section_dashboard_customizing.xml68(para)
-msgid ""
-"Create a CSS style sheet in the following directory: <filename>/usr/share"
-"/openstack-dashboard/openstack_dashboard/static/dashboard/css/</filename>"
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml72(para)
-msgid ""
-"Edit your CSS file to override the Ubuntu customizations in the "
-"<filename>ubuntu.css</filename> file."
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml75(para)
-msgid ""
-"Change the colors and image file names as appropriate, though the relative "
-"directory paths should be the same. The following example file shows you how"
-" to customize your CSS file:"
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml114(para)
-msgid ""
-"Open the following HTML template in an editor: <filename>/usr/share"
-"/openstack-"
-"dashboard/openstack_dashboard/templates/_stylesheets.html</filename>"
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml118(para)
-msgid "Add a line to include your <filename>custom.css</filename> file:"
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml123(emphasis)
-msgid ""
-"&lt;link href='{{ STATIC_URL }}dashboard/css/custom.css' media='screen' "
-"rel='stylesheet' /&gt;"
-msgstr "&lt;link href='{{ STATIC_URL }}dashboard/css/custom.css' media='screen' rel='stylesheet' /&gt;"
-
-#: ./doc/common/section_dashboard_customizing.xml127(title)
-msgid "Restart Apache:"
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml128(para)
-#: ./doc/common/section_dashboard_sessions.xml180(para)
-msgid "On Ubuntu: <placeholder-1/>"
-msgstr "Sur Ubuntu: <placeholder-1/>"
-
-#: ./doc/common/section_dashboard_customizing.xml131(para)
-msgid "On Fedora, RHEL, CentOS: <placeholder-1/>"
-msgstr "Sur Fedora, RHEL, CentOS: <placeholder-1/>"
-
-#: ./doc/common/section_dashboard_customizing.xml134(para)
-#: ./doc/common/section_dashboard_sessions.xml187(para)
-msgid "On openSUSE: <placeholder-1/>"
-msgstr "Sur openSUSE: <placeholder-1/>"
-
-#: ./doc/common/section_dashboard_customizing.xml139(para)
-msgid "Reload the dashboard in your browser to view your changes."
-msgstr "Relancer le tableau de bord dans votre navigateur pour voir vos changements."
-
-#: ./doc/common/section_dashboard_customizing.xml141(para)
-msgid "Modify your CSS file as appropriate."
-msgstr "Modifier votre dossier CSS comme il convient."
-
-#: ./doc/common/section_cli_version.xml6(title)
-msgid "Discover the version number for a client"
-msgstr ""
-
-#: ./doc/common/section_cli_version.xml7(para)
-msgid "Run the following command to discover the version number for a client:"
-msgstr ""
-
-#: ./doc/common/section_cli_version.xml9(replaceable)
-#: ./doc/common/section_cli_install.xml208(replaceable)
-#: ./doc/common/section_cli_install.xml210(replaceable)
-#: ./doc/common/section_cli_install.xml222(replaceable)
-#: ./doc/common/section_cli_install.xml228(replaceable)
-#: ./doc/common/section_cli_install.xml236(replaceable)
-#: ./doc/common/section_cli_install.xml239(replaceable)
-msgid "PROJECT"
-msgstr "PROJECT"
-
-#: ./doc/common/section_cli_version.xml10(para)
-msgid ""
-"For example, to see the version number for the <placeholder-1/> client, run "
-"the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_version.xml14(para)
-msgid "The version number (2.15.0 in the example) is returned."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml6(title)
-msgid "Groups"
-msgstr "Groupes"
-
-#: ./doc/common/section_keystone-concepts-group-management.xml7(para)
-msgid ""
-"A group is a collection of users. Administrators can create groups and add "
-"users to them. Then, rather than assign a role to each user individually, "
-"assign a role to the group. Every group is in a domain. Groups were "
-"introduced with the Identity API v3."
-msgstr ""
-
-#. TODO: eventually remove the last sentence, when v3 is
-#.              commonplace
-#: ./doc/common/section_keystone-concepts-group-management.xml14(para)
-msgid "Identity API V3 provides the following group-related operations:"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml18(para)
-msgid "Create a group"
-msgstr "Créez un groupe"
-
-#: ./doc/common/section_keystone-concepts-group-management.xml21(para)
-msgid "Delete a group"
-msgstr "Supprimez un groupe"
-
-#: ./doc/common/section_keystone-concepts-group-management.xml24(para)
-msgid "Update a group (change its name or description)"
-msgstr "Mettre à jour (changer le nom ou la description)"
-
-#: ./doc/common/section_keystone-concepts-group-management.xml28(para)
-msgid "Add a user to a group"
-msgstr "Ajoutez un utilisateur à un groupe"
-
-#: ./doc/common/section_keystone-concepts-group-management.xml31(para)
-msgid "Remove a user from a group"
-msgstr "Supprimez un utilisateur d'un groupe"
-
-#: ./doc/common/section_keystone-concepts-group-management.xml34(para)
-msgid "List group members"
-msgstr "Listez les membres d'un groupe."
-
-#: ./doc/common/section_keystone-concepts-group-management.xml37(para)
-msgid "List groups for a user"
-msgstr "Lister des groupes pour un utilisateur"
-
-#: ./doc/common/section_keystone-concepts-group-management.xml40(para)
-msgid "Assign a role on a tenant to a group"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml43(para)
-msgid "Assign a role on a domain to a group"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml46(para)
-msgid "Query role assignments to groups"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml50(para)
-msgid ""
-"The Identity service server might not allow all operations. For example, if "
-"using the Identity server with the LDAP Identity back end and group updates "
-"are disabled, then a request to create, delete, or update a group fails."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml56(para)
-msgid "Here are a couple of examples:"
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml109(title)
+msgid "Create or update an image (glance)"
+msgstr "Créer ou mettre à jour une image (glance)"
 
-#: ./doc/common/section_keystone-concepts-group-management.xml59(para)
-msgid ""
-"Group A is granted Role A on Tenant A. If User A is a member of Group A, "
-"when User A gets a token scoped to Tenant A, the token also includes Role A."
+#: ./doc/common/section_cli_glance_manage_images.xml110(para)
+msgid "To create an image, use <placeholder-1/>:"
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts-group-management.xml65(para)
-msgid ""
-"Group B is granted Role B on Domain B. If User B is a member of Domain B, if"
-" User B gets a token scoped to Domain B, the token also includes Role B."
+#: ./doc/common/section_cli_glance_manage_images.xml111(replaceable)
+#: ./doc/common/section_cli_glance_manage_images.xml114(replaceable)
+msgid "imageName"
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml11(title)
-msgid "Orchestration command-line client"
+#: ./doc/common/section_cli_glance_manage_images.xml112(para)
+msgid "To update an image by name or ID, use <placeholder-1/>:"
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml12(para)
+#: ./doc/common/section_cli_glance_manage_images.xml116(para)
 msgid ""
-"The <placeholder-1/> client is the command-line interface (CLI) for the "
-"Orchestration API and its extensions. This chapter documents "
-"<placeholder-2/> version 0.2.9."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml22(title)
-msgid "heat usage"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml39(para)
-#: ./doc/common/ch_cli_heat_commands.xml506(para)
-msgid "Resume the stack."
-msgstr "Reprendre la pile."
-
-#: ./doc/common/ch_cli_heat_commands.xml47(para)
-#: ./doc/common/ch_cli_heat_commands.xml523(para)
-msgid "Suspend the stack."
-msgstr "suspendre la pile."
-
-#: ./doc/common/ch_cli_heat_commands.xml55(para)
-#: ./doc/common/ch_cli_heat_commands.xml540(para)
-msgid "Retrieve build information."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml63(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use stack-create instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml71(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use stack-delete instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml79(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use stack-show instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml87(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use event-show instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml95(para)
-#: ./doc/common/ch_cli_heat_commands.xml547(para)
-msgid "List events for a stack."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml103(para)
-#: ./doc/common/ch_cli_heat_commands.xml575(para)
-msgid "Describe the event."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml111(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use template-show instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml119(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use stack-list instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml127(para)
-#: ./doc/common/ch_cli_heat_commands.xml608(para)
-msgid "Show available outputs."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml135(para)
-#: ./doc/common/ch_cli_heat_commands.xml625(para)
-msgid "Show a specific stack output."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml143(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use resource-show instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml151(para)
-#: ./doc/common/ch_cli_heat_commands.xml650(para)
-msgid "Show list of resources belonging to a stack."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml159(para)
-#: ./doc/common/ch_cli_heat_commands.xml667(para)
-msgid "List resource metadata."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml167(para)
-#: ./doc/common/ch_cli_heat_commands.xml692(para)
-msgid "Describe the resource."
-msgstr "Décrire la ressource."
-
-#: ./doc/common/ch_cli_heat_commands.xml175(para)
-#: ./doc/common/ch_cli_heat_commands.xml717(para)
-msgid "Send a signal to a resource."
+"The following table lists the optional arguments that you can use with the "
+"<placeholder-1/> and <placeholder-2/> commands to modify image properties. "
+"For more information, refer to Image Service chapter in the <link "
+"href=\"http://docs.openstack.org/cli-"
+"reference/content/index.html\">OpenStack Command-Line Interface "
+"Reference</link>."
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml183(para)
-#: ./doc/common/ch_cli_heat_commands.xml762(para)
-msgid "Generate a template based on a resource."
+#: ./doc/common/section_cli_glance_manage_images.xml126(parameter)
+msgid "--name NAME"
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml191(para)
-#: ./doc/common/ch_cli_heat_commands.xml790(para)
-msgid "List the available resource types."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml199(para)
-#: ./doc/common/ch_cli_heat_commands.xml797(para)
-msgid "Show the resource type."
-msgstr "Montrer le type de ressource."
-
-#: ./doc/common/ch_cli_heat_commands.xml207(para)
-#: ./doc/common/ch_cli_heat_commands.xml814(para)
-msgid "Abandon the stack."
-msgstr "Abandonner la pile."
-
-#: ./doc/common/ch_cli_heat_commands.xml215(para)
-#: ./doc/common/ch_cli_heat_commands.xml834(para)
-msgid "Adopt a stack."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml223(para)
-#: ./doc/common/ch_cli_heat_commands.xml932(para)
-msgid "Create the stack."
-msgstr "Créer la pile"
-
-#: ./doc/common/ch_cli_heat_commands.xml231(para)
-#: ./doc/common/ch_cli_heat_commands.xml1019(para)
-msgid "Delete the stack(s)."
-msgstr "Supprimer la pile (les piles)."
-
-#: ./doc/common/ch_cli_heat_commands.xml239(para)
-#: ./doc/common/ch_cli_heat_commands.xml1037(para)
-msgid "List the user's stacks."
-msgstr "Lister les piles de l'utilisateur."
-
-#: ./doc/common/ch_cli_heat_commands.xml247(para)
-#: ./doc/common/ch_cli_heat_commands.xml1076(para)
-msgid "Preview the stack."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml255(para)
-#: ./doc/common/ch_cli_heat_commands.xml1154(para)
-msgid "Describe the stack."
-msgstr "Décrire la pile"
-
-#: ./doc/common/ch_cli_heat_commands.xml263(para)
-#: ./doc/common/ch_cli_heat_commands.xml1173(para)
-msgid "Update the stack."
-msgstr "Mettre à jour la pile"
+#: ./doc/common/section_cli_glance_manage_images.xml129(para)
+msgid "The name of the image."
+msgstr "Le nom de l'image."
 
-#: ./doc/common/ch_cli_heat_commands.xml271(para)
-#: ./doc/common/ch_cli_heat_commands.xml1243(para)
-msgid "Get the template for the specified stack."
+#: ./doc/common/section_cli_glance_manage_images.xml134(parameter)
+msgid "--disk-format DISK_FORMAT"
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml279(para)
-#: ./doc/common/ch_cli_heat_commands.xml1261(para)
-msgid "Validate a template with parameters."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml287(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use stack-update instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml295(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use template-validate instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml320(title)
-msgid "heat optional arguments"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml333(para)
-msgid "Defaults to <code>env[HEATCLIENT_DEBUG]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml349(para)
+#: ./doc/common/section_cli_glance_manage_images.xml137(para)
 msgid ""
-"Explicitly allow the client to perform \"insecure\" SSL (https) requests. "
-"The server's certificate will not be verified against any certificate "
-"authorities. This option should be used with caution."
+"The disk format of the image. Acceptable formats are ami, ari, aki, vhd, "
+"vmdk, raw, qcow2, vdi, and iso."
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml370(para)
-msgid ""
-"Path of client key to use in SSL connection.This option is not necessary if "
-"your key is prepended to your cert file."
+#: ./doc/common/section_cli_glance_manage_images.xml143(parameter)
+msgid "--container-format CONTAINER_FORMAT"
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml380(para)
+#: ./doc/common/section_cli_glance_manage_images.xml146(para)
 msgid ""
-"Path of CA SSL certificate(s) used to verify the remote server's "
-"certificate. Without this option the client looks for the default system CA "
-"certificates."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml390(para)
-msgid ""
-"Number of seconds to wait for an API response, defaults to system socket "
-"timeout"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml455(para)
-msgid ""
-"Do not contact keystone for a token. Defaults to "
-"<code>env[OS_NO_CLIENT_AUTH]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml464(para)
-msgid "Defaults to <code>env[HEAT_URL]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml472(para)
-msgid "Defaults to <code>env[HEAT_API_VERSION]</code> or 1."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml496(para)
-msgid "Send os-username and os-password to heat."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml504(title)
-msgid "heat action-resume command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml513(para)
-msgid "Name or ID of stack to resume."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml521(title)
-msgid "heat action-suspend command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml530(para)
-msgid "Name or ID of stack to suspend."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml538(title)
-msgid "heat build-info command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml545(title)
-msgid "heat event-list command"
+"The container format of the image. Acceptable formats are ami, ari, aki, "
+"bare, and ovf."
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml554(para)
-#: ./doc/common/ch_cli_heat_commands.xml582(para)
-msgid "Name or ID of stack to show the events for."
+#: ./doc/common/section_cli_glance_manage_images.xml152(parameter)
+msgid "--owner TENANT_ID"
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml565(para)
-msgid "Name of the resource to filter events by."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml573(title)
-msgid "heat event-show command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml590(para)
-msgid "Name of the resource the event belongs to."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml598(para)
-msgid "ID of event to display details for."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml606(title)
-msgid "heat output-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml615(para)
-#: ./doc/common/ch_cli_heat_commands.xml632(para)
-msgid "Name or ID of stack to query."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml623(title)
-msgid "heat output-show command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml640(para)
-msgid "Name of an output to display."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml648(title)
-msgid "heat resource-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml657(para)
-msgid "Name or ID of stack to show the resources for."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml665(title)
-msgid "heat resource-metadata command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml674(para)
-msgid "Name or ID of stack to show the resource metadata for."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml682(para)
-msgid "Name of the resource to show the metadata for."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml690(title)
-msgid "heat resource-show command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml699(para)
-msgid "Name or ID of stack to show the resource for."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml707(para)
-msgid "Name of the resource to show the details for."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml715(title)
-msgid "heat resource-signal command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml724(para)
-msgid "Name or ID of stack the resource belongs to."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml732(para)
-msgid "Name of the resource to signal."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml743(para)
-msgid "JSON Data to send to the signal handler."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml751(para)
-msgid "File containing JSON data to send to the signal handler."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml760(title)
-msgid "heat resource-template command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml769(para)
-msgid "Name of the resource to generate a template for."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml780(para)
-msgid "The template output format, one of: yaml, json."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml155(para)
+msgid "The tenant who should own the image."
+msgstr "Le locataire qui devrait posséder l'image."
 
-#: ./doc/common/ch_cli_heat_commands.xml788(title)
-msgid "heat resource-type-list command"
+#: ./doc/common/section_cli_glance_manage_images.xml160(parameter)
+msgid "--size SIZE"
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml795(title)
-msgid "heat resource-type-show command"
+#: ./doc/common/section_cli_glance_manage_images.xml163(para)
+msgid "The size of image data, in bytes."
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml804(para)
-msgid "Resource type to get the details for."
+#: ./doc/common/section_cli_glance_manage_images.xml168(parameter)
+msgid "--min-disk DISK_GB"
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml812(title)
-msgid "heat stack-abandon command"
+#: ./doc/common/section_cli_glance_manage_images.xml171(para)
+msgid "The minimum size of the disk needed to boot the image, in gigabytes."
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml821(para)
-msgid "Name or ID of stack to abandon."
-msgstr "Nom ou ID de la pile à abandonner."
-
-#: ./doc/common/ch_cli_heat_commands.xml829(title)
-msgid "heat stack-adopt command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml841(para)
-msgid "Name of the stack to adopt."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml852(para)
-#: ./doc/common/ch_cli_heat_commands.xml950(para)
-#: ./doc/common/ch_cli_heat_commands.xml1094(para)
-#: ./doc/common/ch_cli_heat_commands.xml1191(para)
-#: ./doc/common/ch_cli_heat_commands.xml1276(para)
-msgid "Path to the template."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml860(para)
-#: ./doc/common/ch_cli_heat_commands.xml958(para)
-#: ./doc/common/ch_cli_heat_commands.xml1102(para)
-#: ./doc/common/ch_cli_heat_commands.xml1199(para)
-#: ./doc/common/ch_cli_heat_commands.xml1284(para)
-msgid "Path to the environment."
+#: ./doc/common/section_cli_glance_manage_images.xml177(parameter)
+msgid "--min-ram DISK_RAM"
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml868(para)
-#: ./doc/common/ch_cli_heat_commands.xml966(para)
-#: ./doc/common/ch_cli_heat_commands.xml1110(para)
-#: ./doc/common/ch_cli_heat_commands.xml1207(para)
-#: ./doc/common/ch_cli_heat_commands.xml1268(para)
-msgid "URL of template."
+#: ./doc/common/section_cli_glance_manage_images.xml180(para)
+msgid "The minimum amount of RAM needed to boot the image, in megabytes."
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml876(para)
-msgid "URL to retrieve template object (e.g from swift)."
+#: ./doc/common/section_cli_glance_manage_images.xml185(parameter)
+msgid "--location IMAGE_URL"
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml884(para)
-#: ./doc/common/ch_cli_heat_commands.xml982(para)
+#: ./doc/common/section_cli_glance_manage_images.xml188(para)
 msgid ""
-"Stack creation timeout in minutes. <emphasis>DEPRECATED</emphasis> use "
-"--timeout instead."
+"The URL where the data for this image resides. For example, if the image "
+"data is stored in swift, you could specify "
+"<literal>swift://account:key@example.com/container/obj</literal>."
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml893(para)
-#: ./doc/common/ch_cli_heat_commands.xml991(para)
-msgid "Stack creation timeout in minutes."
-msgstr "Délai d'expiration (en minutes) pour la création de stack "
-
-#: ./doc/common/ch_cli_heat_commands.xml901(para)
-msgid "Path to adopt stack data file."
+#: ./doc/common/section_cli_glance_manage_images.xml195(parameter)
+msgid "--file FILE"
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml909(para)
-#: ./doc/common/ch_cli_heat_commands.xml999(para)
-msgid "Enable rollback on create/update failure."
-msgstr "Permettre le retour arrière en cas d'échec de la création / mise à jour."
-
-#: ./doc/common/ch_cli_heat_commands.xml917(para)
-#: ./doc/common/ch_cli_heat_commands.xml1007(para)
-#: ./doc/common/ch_cli_heat_commands.xml1231(para)
+#: ./doc/common/section_cli_glance_manage_images.xml198(para)
 msgid ""
-"Parameter values used to create the stack. This can be specified multiple "
-"times, or once with parameters separated by a semicolon."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml927(title)
-msgid "heat stack-create command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml939(para)
-msgid "Name of the stack to create."
-msgstr "Nom de la pile à créer."
-
-#: ./doc/common/ch_cli_heat_commands.xml974(para)
-#: ./doc/common/ch_cli_heat_commands.xml1215(para)
-#: ./doc/common/ch_cli_heat_commands.xml1292(para)
-msgid "URL to retrieve template object (e.g. from swift)."
+"Local file that contains the disk image to be uploaded during the update. "
+"Alternatively, you can pass images to the client through stdin."
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml1017(title)
-msgid "heat stack-delete command"
+#: ./doc/common/section_cli_glance_manage_images.xml204(parameter)
+msgid "--checksum CHECKSUM"
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml1026(para)
-msgid "Name or ID of stack(s) to delete."
+#: ./doc/common/section_cli_glance_manage_images.xml207(para)
+msgid "Hash of image data to use for verification."
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml1034(title)
-msgid "heat stack-list command"
+#: ./doc/common/section_cli_glance_manage_images.xml212(parameter)
+msgid "--copy-from IMAGE_URL"
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml1044(para)
+#: ./doc/common/section_cli_glance_manage_images.xml215(para)
 msgid ""
-"Filter parameters to apply on returned stacks. This can be specified "
-"multiple times, or once with parameters separated by a semicolon."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml1054(para)
-msgid "Limit the number of stacks returned."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml1062(para)
-msgid "Only return stacks that appear after the given stack ID."
+"Similar to <parameter>--location</parameter> in usage, but indicates that "
+"the image server should immediately copy the data and store it in its "
+"configured image store."
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml1071(title)
-msgid "heat stack-preview command"
+#: ./doc/common/section_cli_glance_manage_images.xml222(parameter)
+msgid "--is-public [True|False]"
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml1083(para)
-msgid "Name of the stack to preview."
+#: ./doc/common/section_cli_glance_manage_images.xml225(para)
+msgid "Makes an image accessible for all the tenants."
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml1118(para)
-msgid "URL to retrieve template object (e.g from swift)"
+#: ./doc/common/section_cli_glance_manage_images.xml230(parameter)
+msgid "--is-protected [True|False]"
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml1126(para)
-msgid "Stack timeout in minutes. Default: 60"
+#: ./doc/common/section_cli_glance_manage_images.xml233(para)
+msgid "Prevents an image from being deleted."
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml1134(para)
-msgid "Enable rollback on failure"
+#: ./doc/common/section_cli_glance_manage_images.xml238(parameter)
+msgid "--property KEY=VALUE"
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml1142(para)
+#: ./doc/common/section_cli_glance_manage_images.xml241(para)
 msgid ""
-"Parameter values used to preview the stack. This can be specified multiple "
-"times, or once with parameters separated by semicolon."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml1152(title)
-msgid "heat stack-show command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml1161(para)
-msgid "Name or ID of stack to describe."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml1169(title)
-msgid "heat stack-update command"
+"Arbitrary property to associate with image. This option can be used multiple"
+" times."
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml1180(para)
-msgid "Name or ID of stack to update."
+#: ./doc/common/section_cli_glance_manage_images.xml247(parameter)
+msgid "--purge-props"
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml1223(para)
-msgid "Stack update timeout in minutes."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml1241(title)
-msgid "heat template-show command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml1250(para)
-msgid "Name or ID of stack to get the template for."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml1258(title)
-msgid "heat template-validate command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml1300(para)
-msgid ""
-"Parameter values to validate. This can be specified multiple times, or once "
-"with parameters separated by a semicolon."
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml8(para)
+#: ./doc/common/section_cli_glance_manage_images.xml250(para)
 msgid ""
-"You can use the OpenStack command-line clients to run simple commands that "
-"make API calls. You can run these commands from the command line or in "
-"scripts to automate tasks. If you provide OpenStack credentials, you can run"
-" these commands on any computer."
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml12(para)
-msgid ""
-"Internally, each client command runs cURL commands that embed API requests. "
-"The OpenStack APIs are RESTful APIs that use the HTTP protocol, including "
-"methods, URIs, media types, and response codes."
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml16(para)
-msgid ""
-"These open-source Python clients run on Linux or Mac OS X systems and are "
-"easy to learn and use. Each OpenStack service has its own command-line "
-"client. On some client commands, you can specify a <placeholder-1/> "
-"parameter to show the underlying API request for the command. This is a good"
-" way to become familiar with the OpenStack API calls."
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml23(para)
-msgid ""
-"The following table lists the command-line client for each OpenStack service"
-" with its package name and description."
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml26(caption)
-msgid "OpenStack services and clients"
-msgstr "Les services et les clients d'OpenStack"
-
-#: ./doc/common/section_cli_overview.xml34(th)
-msgid "Client"
-msgstr "Client"
-
-#: ./doc/common/section_cli_overview.xml35(th)
-msgid "Package"
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml43(package)
-msgid "python-cinderclient"
-msgstr "python-cinderclient"
-
-#: ./doc/common/section_cli_overview.xml44(td)
-msgid "Create and manage volumes."
-msgstr "Créer et Gérer les volumes."
-
-#: ./doc/common/section_cli_overview.xml49(package)
-msgid "python-novaclient"
-msgstr "python-novaclient"
-
-#: ./doc/common/section_cli_overview.xml50(td)
-msgid "Create and manage images, instances, and flavors."
-msgstr "Créer et gérer les images, instances et types d'instance."
-
-#: ./doc/common/section_cli_overview.xml55(package)
-msgid "python-troveclient"
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml56(td)
-msgid "Create and manage databases."
+"Deletes all image properties that are not explicitly set in the update "
+"request. Otherwise, those properties not referenced are preserved."
 msgstr ""
 
-#: ./doc/common/section_cli_overview.xml59(td)
-msgid "Identity"
-msgstr "Identité"
-
-#: ./doc/common/section_cli_overview.xml61(package)
-msgid "python-keystoneclient"
-msgstr "python-keystoneclient"
-
-#: ./doc/common/section_cli_overview.xml62(td)
-msgid "Create and manage users, tenants, roles, endpoints, and credentials."
-msgstr "Créez et gérez des utilisateurs, des locataires, des rôles, des points de terminaison et des informations d'identification."
-
-#: ./doc/common/section_cli_overview.xml67(package)
-msgid "python-glanceclient"
+#: ./doc/common/section_cli_glance_manage_images.xml256(parameter)
+msgid "--human-readable"
 msgstr ""
 
-#: ./doc/common/section_cli_overview.xml68(td)
-msgid "Create and manage images."
-msgstr "Créer et gérer les images."
-
-#: ./doc/common/section_cli_overview.xml73(package)
-msgid "python-neutronclient"
+#: ./doc/common/section_cli_glance_manage_images.xml259(para)
+msgid "Prints the image size in a human-friendly format."
 msgstr ""
 
-#: ./doc/common/section_cli_overview.xml74(td)
+#: ./doc/common/section_cli_glance_manage_images.xml263(para)
 msgid ""
-"Configure networks for guest servers. This client was previously called "
-"<placeholder-1/>."
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml80(package)
-msgid "python-swiftclient"
+"The following example shows the command that you would use to upload a "
+"CentOS 6.3 image in qcow2 format and configure it for public access:"
 msgstr ""
 
-#: ./doc/common/section_cli_overview.xml81(td)
+#: ./doc/common/section_cli_glance_manage_images.xml267(para)
 msgid ""
-"Gather statistics, list items, update metadata, and upload, download, and "
-"delete files stored by the Object Storage service. Gain access to an Object "
-"Storage installation for ad hoc processing."
+"The following example shows how to update an existing image with a "
+"properties that describe the disk bus, the CD-ROM bus, and the VIF model:"
 msgstr ""
 
-#: ./doc/common/section_cli_overview.xml88(package)
-msgid "python-heatclient"
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml89(td)
+#: ./doc/common/section_cli_glance_manage_images.xml274(para)
 msgid ""
-"Launch stacks from templates, view details of running stacks including "
-"events and resources, and update and delete stacks."
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml95(package)
-msgid "python-ceilometerclient"
-msgstr ""
-
-#: ./doc/common/section_cli_overview.xml96(td)
-msgid "Create and collect measurements across OpenStack."
+"Currently the libvirt virtualization tool determines the disk, CD-ROM, and "
+"VIF device models based on the configured hypervisor type "
+"(<literal>libvirt_type</literal> in "
+"<filename>/etc/nova/nova.conf</filename>). For the sake of optimal "
+"performance, libvirt defaults to using virtio for both disk and VIF (NIC) "
+"models. The disadvantage of this approach is that it is not possible to run "
+"operating systems that lack virtio drivers, for example, BSD, Solaris, and "
+"older versions of Linux and Windows."
 msgstr ""
 
-#: ./doc/common/section_cli_overview.xml100(para)
-msgid "An OpenStack <placeholder-1/> client is in development."
-msgstr "Un client d'OpenStack <placeholder-1/> est en train d'être développer "
-
-#: ./doc/common/section_cli_overview.xml102(para)
+#: ./doc/common/section_cli_glance_manage_images.xml280(para)
 msgid ""
-"For client installation instructions, see <link "
-"href=\"http://docs.openstack.org/user-"
-"guide/content/install_clients.html\">Install the OpenStack command-line "
-"clients</link>. For information about the OpenStack RC file, see <link "
-"href=\"http://docs.openstack.org/user-"
-"guide/content/cli_openrc.html\">Download and source the OpenStack RC "
-"file</link>."
+"If you specify a disk or CD-ROM bus model that is not supported, see <xref "
+"linkend=\"bus_models\"/>. If you specify a VIF model that is not supported, "
+"the instance fails to launch. See <xref linkend=\"vif_models\"/>."
 msgstr ""
 
-#: ./doc/common/section_rpc.xml8(para)
+#: ./doc/common/section_cli_glance_manage_images.xml284(para)
 msgid ""
-"OpenStack projects use AMQP, an open standard for messaging middleware. "
-"OpenStack services that run on multiple servers to talk to each other. "
-"OpenStack Oslo RPC supports three implementations of AMQP: "
-"<application>RabbitMQ</application>, <application>Qpid</application>, and "
-"<application>ZeroMQ</application>."
+"The valid model values depend on the <literal>libvirt_type</literal> "
+"setting, as shown in the following tables."
 msgstr ""
 
-#: ./doc/common/section_rpc.xml16(para)
-msgid ""
-"OpenStack Oslo RPC uses <application>RabbitMQ</application> by default. Use "
-"these options to configure the <application>RabbitMQ</application> message "
-"system. The <literal>rpc_backend</literal> option is not required as long as"
-" <application>RabbitMQ</application> is the default messaging system. "
-"However, if it is included the configuration, you must set it to "
-"<literal>nova.openstack.common.rpc.impl_kombu</literal>."
+#: ./doc/common/section_cli_glance_manage_images.xml287(caption)
+msgid "Disk and CD-ROM bus model values"
 msgstr ""
 
-#: ./doc/common/section_rpc.xml25(para)
-msgid ""
-"You can use these additional options to configure the "
-"<application>RabbitMQ</application> messaging system. You can configure "
-"messaging communication for different installation scenarios, tune retries "
-"for RabbitMQ, and define the size of the RPC thread pool. To monitor "
-"notifications through RabbitMQ, you must set the "
-"<option>notification_driver</option> option to "
-"<literal>nova.notifier.rabbit_notifier</literal> in the "
-"<filename>nova.conf</filename> file. The default for sending usage data is "
-"sixty seconds plus a random number of seconds from zero to sixty."
-msgstr ""
-
-#: ./doc/common/section_rpc.xml40(para)
-msgid ""
-"Use these options to configure the <application>Qpid</application> messaging"
-" system for OpenStack Oslo RPC. <application>Qpid</application> is not the "
-"default messaging system, so you must enable it by setting the "
-"<option>rpc_backend</option> option in the <filename>nova.conf</filename> "
-"file."
+#: ./doc/common/section_cli_glance_manage_images.xml292(th)
+#: ./doc/common/section_cli_glance_manage_images.xml336(th)
+msgid "libvirt_type setting"
 msgstr ""
 
-#: ./doc/common/section_rpc.xml47(para)
-msgid ""
-"This critical option points the compute nodes to the "
-"<application>Qpid</application> broker (server). Set "
-"<option>qpid_hostname</option> to the host name where the broker runs in the"
-" <filename>nova.conf</filename> file."
+#: ./doc/common/section_cli_glance_manage_images.xml293(th)
+#: ./doc/common/section_cli_glance_manage_images.xml337(th)
+msgid "Supported model values"
 msgstr ""
 
-#: ./doc/common/section_rpc.xml69(para)
-msgid ""
-"This table lists additional options that you use to configure the Qpid "
-"messaging driver for OpenStack Oslo RPC. These options are used "
-"infrequently."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml298(td)
+#: ./doc/common/section_cli_glance_manage_images.xml342(td)
+msgid "qemu or kvm"
+msgstr "qemu ou kvm"
 
-#: ./doc/common/section_rpc.xml76(para)
-msgid ""
-"Use these options to configure the <application>ZeroMQ</application> "
-"messaging system for OpenStack Oslo RPC. <application>ZeroMQ</application> "
-"is not the default messaging system, so you must enable it by setting the "
-"<option>rpc_backend</option> option in the <filename>nova.conf</filename> "
-"file."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml303(para)
+#: ./doc/common/section_cli_glance_manage_images.xml320(para)
+msgid "ide"
+msgstr "ide"
 
-#: ./doc/common/section_rpc.xml86(para)
-msgid ""
-"Use these options to configure the <application>RabbitMQ</application> and "
-"<application>Qpid</application> messaging drivers."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml306(para)
+msgid "scsi"
+msgstr "scsi"
 
-#: ./doc/common/section_cli_install.xml7(title)
-msgid "Install the OpenStack command-line clients"
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml309(para)
+#: ./doc/common/section_cli_glance_manage_images.xml359(para)
+msgid "virtio"
+msgstr "virtio"
 
-#: ./doc/common/section_cli_install.xml8(para)
-msgid ""
-"Install the prerequisite software and the Python package for each OpenStack "
-"client."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml316(td)
+#: ./doc/common/section_cli_glance_manage_images.xml323(para)
+#: ./doc/common/section_cli_glance_manage_images.xml366(td)
+msgid "xen"
+msgstr "xen"
 
-#: ./doc/common/section_cli_install.xml11(title)
-msgid "Install the prerequisite software"
+#: ./doc/common/section_cli_glance_manage_images.xml331(caption)
+msgid "VIF model values"
 msgstr ""
 
-#: ./doc/common/section_cli_install.xml12(para)
-msgid ""
-"The following table lists the software that you need to have to run the "
-"command-line clients, and provides installation instructions as needed."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml347(para)
+#: ./doc/common/section_cli_glance_manage_images.xml370(para)
+msgid "e1000"
+msgstr "e1000"
 
-#: ./doc/common/section_cli_install.xml16(caption)
-msgid "Prerequisite software"
-msgstr "Logiciels Prérequis"
+#: ./doc/common/section_cli_glance_manage_images.xml350(para)
+#: ./doc/common/section_cli_glance_manage_images.xml376(para)
+msgid "ne2k_pci"
+msgstr "ne2k_pci"
 
-#: ./doc/common/section_cli_install.xml21(th)
-msgid "Prerequisite"
-msgstr "Prérequis"
+#: ./doc/common/section_cli_glance_manage_images.xml353(para)
+#: ./doc/common/section_cli_glance_manage_images.xml379(para)
+msgid "pcnet"
+msgstr "pcnet"
 
-#: ./doc/common/section_cli_install.xml28(para)
-msgid "Python 2.6 or later"
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml356(para)
+#: ./doc/common/section_cli_glance_manage_images.xml382(para)
+msgid "rtl8139"
+msgstr "rtl8139"
 
-#: ./doc/common/section_cli_install.xml31(para)
-msgid "Currently, the clients do not support Python 3."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml373(para)
+msgid "netfront"
+msgstr "netfront"
 
-#: ./doc/common/section_cli_install.xml37(para)
-msgid "<package>setuptools</package> package"
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml388(td)
+msgid "vmware"
+msgstr "vmware"
 
-#: ./doc/common/section_cli_install.xml40(para)
-msgid "Installed by default on Mac OS X."
-msgstr "Installé par défaut sur Mac OS X."
+#: ./doc/common/section_cli_glance_manage_images.xml393(para)
+msgid "VirtualE1000"
+msgstr "VirtualE1000"
 
-#: ./doc/common/section_cli_install.xml41(para)
-msgid ""
-"Many Linux distributions provide packages to make "
-"<package>setuptools</package> easy to install. Search your package manager "
-"for <package>setuptools</package> to find an installation package. If you "
-"cannot find one, download the <package>setuptools</package> package directly"
-" from <link "
-"href=\"http://pypi.python.org/pypi/setuptools\">http://pypi.python.org/pypi/setuptools</link>."
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml49(para)
-msgid ""
-"The recommended way to install <package>setuptools</package> on Microsoft "
-"Windows is to follow the documentation provided <link "
-"href=\"https://pypi.python.org/pypi/setuptools#windows\">on the setuptools "
-"website</link>. Another option is to use the unofficial binary installer "
-"maintained by Christoph Gohlke (<link "
-"href=\"http://www.lfd.uci.edu/~gohlke/pythonlibs/#setuptools\">http://www.lfd.uci.edu/~gohlke/pythonlibs/#setuptools</link>)."
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml62(package)
-msgid "pip"
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml396(para)
+msgid "VirtualPCNet32"
+msgstr "VirtualPCNet32"
 
-#: ./doc/common/section_cli_install.xml62(td)
-msgid "<placeholder-1/> package"
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml399(para)
+msgid "VirtualVmxnet"
+msgstr "VirtualVmxnet"
 
-#: ./doc/common/section_cli_install.xml64(para)
+#: ./doc/common/section_cli_glance_manage_images.xml411(para)
 msgid ""
-"To install the clients on a Linux, Mac OS X, or Microsoft Windows system, "
-"use <package>pip</package>. It is easy to use, ensures that you get the "
-"latest version of the clients from the <link "
-"href=\"http://pypi.python.org/pypi/python-novaclient/\">Python Package "
-"Index</link>, and lets you update or remove the packages later on."
+"If you encounter problems in creating an image in Image Service or Compute, "
+"the following information may help you troubleshoot the creation process."
 msgstr ""
 
-#: ./doc/common/section_cli_install.xml73(para)
+#: ./doc/common/section_cli_glance_manage_images.xml415(para)
 msgid ""
-"Install <package>pip</package> through the package manager for your system:"
+"Ensure that the version of qemu you are using is version 0.14 or later. "
+"Earlier versions of qemu result in an <literal>unknown option -s</literal> "
+"error message in the <filename>nova-compute.log</filename> file."
 msgstr ""
 
-#: ./doc/common/section_cli_install.xml76(title)
-msgid "MacOS"
+#: ./doc/common/section_keystone-external-auth.xml7(title)
+msgid "External authentication with Identity"
 msgstr ""
 
-#: ./doc/common/section_cli_install.xml80(title)
-msgid "Microsoft Windows"
-msgstr "Microsoft Windows"
-
-#: ./doc/common/section_cli_install.xml81(para)
+#: ./doc/common/section_keystone-external-auth.xml8(para)
 msgid ""
-"Ensure that the <filename>C:\\Python27\\Scripts</filename> directory is "
-"defined in the <literal>PATH</literal> environment variable, and use the "
-"<placeholder-1/> command from the <package>setuptools</package> package: "
-"<placeholder-2/>Another option is to use the unofficial binary installer "
-"provided by Christoph Gohlke (<link "
-"href=\"http://www.lfd.uci.edu/~gohlke/pythonlibs/#pip\">http://www.lfd.uci.edu/~gohlke/pythonlibs/#pip</link>)."
+"When Identity runs in <literal>apache-httpd</literal>, you can use external "
+"authentication methods that differ from the authentication provided by the "
+"identity store back end. For example, you can use an SQL identity back end "
+"together with X.509 authentication, Kerberos, and so on instead of using the"
+" user name and password combination."
 msgstr ""
 
-#: ./doc/common/section_cli_install.xml98(title)
-msgid "Ubuntu 12.04/14.04"
+#: ./doc/common/section_keystone-external-auth.xml15(title)
+msgid "Use HTTPD authentication"
 msgstr ""
 
-#: ./doc/common/section_cli_install.xml99(para)
+#: ./doc/common/section_keystone-external-auth.xml16(para)
 msgid ""
-"A packaged version enables you to use <package>dpkg</package> or <package"
-">apt-get</package> to install the <package>python-novaclient</package>: "
-"<placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml108(title)
-msgid "Ubuntu and Debian"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml114(title)
-msgid "Red Hat Enterprise Linux, CentOS, or Fedora"
+"Web servers, like Apache HTTP, support many methods of authentication. "
+"Identity can allow the web server to perform the authentication. The web "
+"server then passes the authenticated user to Identity by using the "
+"<literal>REMOTE_USER</literal> environment variable. This user must already "
+"exist in the Identity back end to get a token from the controller. To use "
+"this method, Identity should run on <literal>apache-httpd</literal>."
 msgstr ""
 
-#: ./doc/common/section_cli_install.xml115(para)
-msgid ""
-"A packaged version available in <link "
-"href=\"http://openstack.redhat.com/\">RDO</link> enables you to use "
-"<package>yum</package> to install the clients, or you can install "
-"<package>pip</package> and use it to manage client installation: "
-"<placeholder-1/>"
+#: ./doc/common/section_keystone-external-auth.xml27(title)
+msgid "Use X.509"
 msgstr ""
 
-#: ./doc/common/section_cli_install.xml123(title)
-msgid "openSUSE 12.2 and earlier"
-msgstr "openSUSE 12.2 et précédent"
-
-#: ./doc/common/section_cli_install.xml124(para)
+#: ./doc/common/section_keystone-external-auth.xml28(para)
 msgid ""
-"A <link href=\"https://build.opensuse.org/package/show?package=python-"
-"novaclient&amp;project=Cloud:OpenStack:Master\">packaged version available "
-"in the Open Build Service</link> enables you to use <package>rpm</package> "
-"or <package>zypper</package> to install the clients, or you can install "
-"<package>pip</package> and use it to manage client installation: "
-"<placeholder-1/>"
+"The following Apache configuration snippet authenticates the user based on a"
+" valid X.509 certificate from a known CA:"
 msgstr ""
 
-#: ./doc/common/section_cli_install.xml135(title)
-msgid "openSUSE 12.3 and later"
+#: ./doc/common/section_getstart_object-storage.xml5(title)
+msgid "OpenStack Object Storage"
 msgstr ""
 
-#: ./doc/common/section_cli_install.xml136(para)
+#: ./doc/common/section_getstart_object-storage.xml6(para)
 msgid ""
-"A packaged version enables you to use <package>rpm</package> or "
-"<package>zypper</package> to install the clients. See <xref "
-"linkend=\"cli_clients_install\"/>"
+"The OpenStack Object Storage is a multi-tenant object storage system. It is "
+"highly scalable and can manage large amounts of unstructured data at low "
+"cost through a RESTful HTTP API."
 msgstr ""
 
-#: ./doc/common/section_cli_install.xml147(title)
-msgid "Install the clients"
-msgstr "Installez les clients"
+#: ./doc/common/section_getstart_object-storage.xml9(para)
+#: ./doc/common/section_getstart_networking.xml11(para)
+msgid "It includes the following components:"
+msgstr "Elle comprend les éléments suivants "
 
-#: ./doc/common/section_cli_install.xml148(para)
+#: ./doc/common/section_getstart_object-storage.xml11(term)
 msgid ""
-"When following the instructions in this section, replace "
-"<replaceable>PROJECT</replaceable> with the lowercase name of the client to "
-"install, such as <placeholder-1/>. Repeat for each client. The following "
-"values are valid:"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml155(para)
-msgid "<literal>ceilometer</literal> - Telemetry API"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml159(para)
-msgid "<literal>cinder</literal> - Block Storage API and extensions"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml163(para)
-msgid "<literal>glance</literal> - Image Service API"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml167(para)
-msgid "<literal>heat</literal> - Orchestration API"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml171(para)
-msgid "<literal>keystone</literal> - Identity service API and extensions"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml175(para)
-msgid "<literal>neutron</literal> - Networking API"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml179(para)
-msgid "<literal>nova</literal> - Compute API and extensions"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml183(para)
-msgid "<literal>swift</literal> - Object Storage API"
+"Proxy servers (<systemitem class=\"service\">swift-proxy-"
+"server</systemitem>)"
 msgstr ""
 
-#: ./doc/common/section_cli_install.xml187(para)
-msgid "<literal>trove</literal> - Database Service API"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml191(para)
+#: ./doc/common/section_getstart_object-storage.xml13(para)
 msgid ""
-"The following example shows the command for installing the nova client with "
-"<replaceable>pip</replaceable>."
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml196(title)
-msgid "Installing with pip"
+"Accepts OpenStack Object Storage API and raw HTTP requests to upload files, "
+"modify metadata, and create containers. It also serves file or container "
+"listings to web browsers. To improve performance, the proxy server can use "
+"an optional cache usually deployed with memcache."
 msgstr ""
 
-#: ./doc/common/section_cli_install.xml197(para)
+#: ./doc/common/section_getstart_object-storage.xml20(term)
 msgid ""
-"Use <package>pip</package> to install the OpenStack clients on a Linux, Mac "
-"OS X, or Microsoft Windows system. It is easy to use and ensures that you "
-"get the latest version of the client from the <link "
-"href=\"http://pypi.python.org/pypi\">Python Package Index</link>. Also, "
-"<package>pip</package> enables you to update or remove a package."
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml204(para)
-msgid "Install each client separately by using the following command:"
+"Account servers (<systemitem class=\"service\">swift-account-"
+"server</systemitem>)"
 msgstr ""
 
-#: ./doc/common/section_cli_install.xml207(para)
-msgid "For Mac OS X or Linux:"
-msgstr "Pour Mac OS X ou Linux:"
-
-#: ./doc/common/section_cli_install.xml209(para)
-msgid "For Microsoft Windows:"
-msgstr "Pour Microsoft Windows:"
-
-#: ./doc/common/section_cli_install.xml214(title)
-msgid "Installing from packages"
+#: ./doc/common/section_getstart_object-storage.xml22(para)
+msgid "Manages accounts defined with Object Storage."
 msgstr ""
 
-#: ./doc/common/section_cli_install.xml215(para)
+#: ./doc/common/section_getstart_object-storage.xml26(term)
 msgid ""
-"RDO and openSUSE have client packages that can be installed without "
-"<filename>pip</filename>."
+"Container servers (<systemitem class=\"service\">swift-container-"
+"server</systemitem>)"
 msgstr ""
 
-#: ./doc/common/section_cli_install.xml217(para)
-msgid ""
-"On Red Hat Enterprise Linux, CentOS, or Fedora, use <placeholder-1/> to "
-"install the clients from the packaged versions available in <link "
-"href=\"http://openstack.redhat.com/\">RDO</link>: <placeholder-2/>"
+#: ./doc/common/section_getstart_object-storage.xml28(para)
+msgid "Manages the mapping of containers or folders, within Object Storage."
 msgstr ""
 
-#: ./doc/common/section_cli_install.xml223(para)
+#: ./doc/common/section_getstart_object-storage.xml32(term)
 msgid ""
-"For openSUSE, use <package>rpm</package> or <package>zypper</package> to "
-"install the clients from the packaged versions available in <link "
-"href=\"https://build.opensuse.org/package/show?package=python-"
-"novaclient&amp;project=Cloud:OpenStack:Master\">the Open Build "
-"Service</link>:<placeholder-1/>"
+"Object servers (<systemitem class=\"service\">swift-object-"
+"server</systemitem>)"
 msgstr ""
 
-#: ./doc/common/section_cli_install.xml232(title)
-msgid "Upgrade or remove clients"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml233(para)
-msgid ""
-"To upgrade a client, add the <literal>--upgrade</literal> option to the "
-"<placeholder-1/> command:"
+#: ./doc/common/section_getstart_object-storage.xml34(para)
+msgid "Manages actual objects,such as files, on the storage nodes."
 msgstr ""
 
-#: ./doc/common/section_cli_install.xml237(para)
-msgid "To remove the a client, run the <placeholder-1/> command:"
+#: ./doc/common/section_getstart_object-storage.xml38(term)
+msgid "Various periodic processes"
 msgstr ""
 
-#: ./doc/common/section_cli_install.xml242(title)
-msgid "What's next"
-msgstr ""
-
-#: ./doc/common/section_cli_install.xml243(para)
+#: ./doc/common/section_getstart_object-storage.xml39(para)
 msgid ""
-"Before you can run client commands, you must create and source the "
-"<filename><replaceable>PROJECT</replaceable>-openrc.sh</filename> file to "
-"set environment variables. See <xref linkend=\"cli_openrc\"/>."
+"Performs housekeeping tasks on the large data store. The replication "
+"services ensure consistency and availability through the cluster. Other "
+"periodic processes include auditors, updaters, and reapers."
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts-service-management.xml5(title)
-msgid "Service management"
-msgstr "Gestion des services"
-
-#: ./doc/common/section_keystone-concepts-service-management.xml6(para)
-msgid ""
-"The Identity Service provides identity, token, catalog, and policy services."
-" It consists of:"
-msgstr "Le service d'identité met à disposition des services d'identité, jeton, catalogue, et politique. Il s'agit de:"
-
-#: ./doc/common/section_keystone-concepts-service-management.xml11(para)
-msgid ""
-"<systemitem class=\"service\">keystone-all</systemitem>. Starts both the "
-"service and administrative APIs in a single process to provide Catalog, "
-"Authorization, and Authentication services for OpenStack."
-msgstr "<systemitem class=\"service\">keystone-all</systemitem>.  Démarre à la fois les APIs administrative et de service dans un processus unique, afin de fournir des services d'annuaire, d'autorisation et d'authentification au sein d'OpenStack."
-
-#: ./doc/common/section_keystone-concepts-service-management.xml17(para)
-msgid ""
-"Identity Service functions. Each has a pluggable back end that allows "
-"different ways to use the particular service. Most support standard back "
-"ends like LDAP or SQL."
+#: ./doc/common/section_getstart_object-storage.xml45(term)
+msgid "WSGI middleware"
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts-service-management.xml23(para)
-msgid ""
-"The Identity Service also maintains a user that corresponds to each service,"
-" such as, a user named <emphasis>nova</emphasis> for the Compute service, "
-"and a special service tenant called <emphasis>service</emphasis>."
-msgstr "Le service d'identité conserve également un utilisateur qui correspond à chaque service, par exemple, un utilisateur qui s'appelle <emphasis>nova</emphasis> qui correspond avec le service Calcul, et un locataire de service en particulier qui s'appelle <emphasis>service</emphasis>."
-
-#: ./doc/common/section_keystone-concepts-service-management.xml28(para)
-msgid ""
-"For information about how to create services and endpoints, see the <link "
-"href=\"http://docs.openstack.org/user-guide-"
-"admin/content/index.html\"><citetitle>OpenStack Admin User "
-"Guide</citetitle></link>."
+#: ./doc/common/section_getstart_object-storage.xml46(para)
+msgid "Handles authentication and is usually OpenStack Identity."
 msgstr ""
 
 #: ./doc/common/ch_cli_trove_commands.xml11(title)
@@ -23696,6 +17354,2851 @@ msgstr ""
 msgid "Optional new host of user."
 msgstr ""
 
+#: ./doc/common/section_dashboard-configure-https.xml4(title)
+msgid "Configure the dashboard for HTTPS"
+msgstr "Pour configurer le tableau de bord pour HTTPS"
+
+#: ./doc/common/section_dashboard-configure-https.xml5(para)
+#: ./doc/common/section_dashboard-configure.xml10(para)
+msgid ""
+"You can configure the dashboard for a secured HTTPS deployment. While the "
+"standard installation uses a non-encrypted HTTP channel, you can enable SSL "
+"support for the dashboard."
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml9(para)
+msgid ""
+"The following example uses the domain, \"http://openstack.example.com.\" Use"
+" a domain that fits your current setup."
+msgstr "L’exemple suivant utilise le domaine http://openstack.example.com. Utilisez un domaine qui corresponde à votre installation courante."
+
+#: ./doc/common/section_dashboard-configure-https.xml13(para)
+msgid ""
+"In<filename>/etc/openstack-dashboard/local_settings.py</filename> update the"
+" following directives:"
+msgstr "Dans <filename>/etc/openstack-dashboard/local_settings.py</filename>, mettez à jour le paramètre suivant :"
+
+#: ./doc/common/section_dashboard-configure-https.xml19(para)
+msgid ""
+"The first option is required to enable HTTPS. The other recommended settings"
+" defend against cross-site scripting and require HTTPS."
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml24(para)
+msgid ""
+"Edit <filename>/etc/apache2/ports.conf</filename> and add the following "
+"line:"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml30(para)
+msgid ""
+"Edit <filename>/etc/apache2/conf.d/openstack-dashboard.conf:</filename>"
+msgstr "Editez le fichier <filename>/etc/apache2/conf.d/openstack-dashboard.conf:</filename>"
+
+#: ./doc/common/section_dashboard-configure-https.xml33(para)
+msgid "Before:"
+msgstr "Avant:"
+
+#: ./doc/common/section_dashboard-configure-https.xml46(para)
+msgid "After:"
+msgstr "Après:"
+
+#: ./doc/common/section_dashboard-configure-https.xml87(para)
+msgid ""
+"In this configuration, Apache http server listens on the port 443 and "
+"redirects all the hits to the HTTPS protocol for all the non-secured "
+"requests. The secured section defines the private key, public key, and "
+"certificate to use."
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml94(para)
+msgid "Restart Apache http server. For Debian/Ubuntu/SUSE:"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml96(para)
+msgid "Or for Fedora/RHEL/CentOS:"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml100(para)
+msgid ""
+"If you try to access the dashboard through HTTP, the browser redirects you "
+"to the HTTPS page."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_volumes.xml8(title)
+msgid "Manage Volumes"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_volumes.xml9(para)
+msgid ""
+"Depending on the setup of your cloud provider, they may give you an endpoint"
+" to use to manage volumes, or there may be an extension under the covers. In"
+" either case, you can use the <placeholder-1/> CLI to manage volumes:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_volumes.xml26(para)
+msgid "For example, to list IDs and names of Compute volumes, run:"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-console.xml5(title)
+msgid "Configure remote console access"
+msgstr "Configurer l’accès console à distance"
+
+#. <?dbhtml stop-chunking?>
+#: ./doc/common/section_compute-configure-console.xml7(para)
+msgid ""
+"To provide a remote console or remote desktop access to guest virtual "
+"machines, use VNC or SPICE HTML5 through either the OpenStack dashboard or "
+"the command line. Best practice is to select one or the other to run."
+msgstr "OpenStack dispose de deux méthodes principales pour fournir l’accès à une console à distance ou un bureau à distance sur des machines virtuelles hébergées. Ce sont VNC, et SPICE HTML5 et ils peuvent être utilisés soit via le tableau de bord OpenStack, soit en ligne de commande. La meilleure pratique consiste à sélectionner l'un ou l'autre pour fonctionner."
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-characteristics.xml49(None)
+msgid ""
+"@@image: '../common/figures/objectstorage.png'; "
+"md5=e26e374ace84070f5fed24e73adcd562"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml7(title)
+msgid "Object Storage characteristics"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml8(para)
+msgid "The key characteristics of Object Storage are that:"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml11(para)
+msgid "All objects stored in Object Storage have a URL."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml14(para)
+msgid ""
+"All objects stored are replicated 3✕ in as-unique-as-possible zones, which "
+"can be defined as a group of drives, a node, a rack, and so on."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml18(para)
+msgid "All objects have their own metadata."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml21(para)
+msgid ""
+"Developers interact with the object storage system through a RESTful HTTP "
+"API."
+msgstr "Les développeurs interagissent avec le système de stockage d'objets à travers une API HTTP RESTful."
+
+#: ./doc/common/section_objectstorage-characteristics.xml25(para)
+msgid "Object data can be located anywhere in the cluster."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml28(para)
+msgid ""
+"The cluster scales by adding additional nodes without sacrificing "
+"performance, which allows a more cost-effective linear storage expansion "
+"than fork-lift upgrades."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml33(para)
+msgid "Data doesn't have to be migrate to an entirely new storage system."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml36(para)
+msgid "New nodes can be added to the cluster without downtime."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml39(para)
+msgid "Failed nodes and disks can be swapped out without downtime."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml42(para)
+msgid ""
+"It runs on industry-standard hardware, such as Dell, HP, and Supermicro."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml53(para)
+msgid ""
+"Developers can either write directly to the Swift API or use one of the many"
+" client libraries that exist for all of the popular programming languages, "
+"such as Java, Python, Ruby, and C#. Amazon S3 and RackSpace Cloud Files "
+"users should be very familiar with Object Storage. Users new to object "
+"storage systems will have to adjust to a different approach and mindset than"
+" those required for a traditional filesystem."
+msgstr "Les développeurs peuvent soit écrire directement à l'API Swift ou utiliser l'une des nombreuses bibliothèques clientes qui existent pour tous les langages de programmation, tels que Java, Python, Ruby et C #. Les utilisateurs Amazon S3 et Rackspace Cloud Files devrait être très familier avec l'Object Storage. Les nouveaux utilisateurs du système Object Storage devront s'adapter à une approche et une mentalité différente que ceux requis pour un système de fichiers traditionnel."
+
+#: ./doc/common/section_cli_nova_startstop.xml6(title)
+msgid "Stop and start an instance"
+msgstr "Démarrer et arrêter une instance"
+
+#: ./doc/common/section_cli_nova_startstop.xml7(para)
+msgid "Use one of the following methods to stop and start an instance."
+msgstr "Utilisez une des méthodes suivantes pour arrêter et démarrer une instance :"
+
+#: ./doc/common/section_cli_nova_startstop.xml10(title)
+msgid "Pause and unpause an instance"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml13(para)
+msgid "To pause an instance, run the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml15(para)
+msgid ""
+"This command stores the state of the VM in RAM. A paused instance continues "
+"to run in a frozen state."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml17(para)
+msgid "To unpause the instance, run the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml23(title)
+msgid "Suspend and resume an instance"
+msgstr "Suspend  and Resume (suspendre et reprendre)"
+
+#: ./doc/common/section_cli_nova_startstop.xml25(para)
+msgid ""
+"Administrative users might want to suspend an instance if it is infrequently"
+" used or to perform system maintenance. When you suspend an instance, its VM"
+" state is stored on disk, all memory is written to disk, and the virtual "
+"machine is stopped. Suspending an instance is similar to placing a device in"
+" hibernation; memory and vCPUs become available to create other instances."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml33(para)
+msgid ""
+"To initiate a hypervisor-level suspend operation, run the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml38(para)
+msgid "To resume a suspended instance, run the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml45(title)
+msgid "Shelve and unshelve an instance"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml46(para)
+msgid ""
+"Shelving is useful if you have an instance that you are not using, but would"
+" like retain in your list of servers. For example, you can stop an instance "
+"at the end of a work week, and resume work again at the start of the next "
+"week. All associated data and resources are kept; however, anything still in"
+" memory is not retained. If a shelved instance is no longer needed, it can "
+"also be entirely removed."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml51(para)
+msgid "You can complete the following shelving tasks:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml53(term)
+msgid "Shelve an instance"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml54(para)
+msgid ""
+"Shuts down the instance, and stores it together with associated data and "
+"resources (a snapshot is taken if not volume backed). Anything in memory is "
+"lost. Use the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml57(replaceable)
+#: ./doc/common/section_cli_nova_startstop.xml62(replaceable)
+#: ./doc/common/section_cli_nova_startstop.xml69(replaceable)
+msgid "SERVERNAME"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml60(term)
+msgid "Unshelve an instance"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml61(para)
+msgid "Restores the instance:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml65(term)
+msgid "Remove a shelved instance"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml66(para)
+msgid ""
+"Removes the instance from the server; data and resource associations are "
+"deleted. If an instance is no longer needed, you can move that instance off "
+"the hypervisor in order to minimize resource usage:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_metadata.xml9(title)
+msgid "Insert metadata during launch"
+msgstr "<placeholder-2/>"
+
+#: ./doc/common/section_cli_nova_metadata.xml10(para)
+msgid ""
+"When booting a server, you can also add metadata, so that you can more "
+"easily identify it amongst your ever-growing elastic cloud. Use the "
+"<literal>--meta</literal> option with a key=value pair, where you can make "
+"up the string for both the key and the value. For example, you could add a "
+"description and also the creator of the server. <placeholder-1/>"
+msgstr "Lorsque vous bootez un serveur, vous pouvez aussi ajouter des métadonnées, pour pouvoir l'identifier plus facilement au sein de votre toujours grandissant cloud élastique. Utilisez l'option <literal>--meta</literal> avec une paire key=value, où vous pouvez faire le lien entre la clé et la valeur. Par exemple, vous pouvez ajouter une description et aussi un créateur du serveur.<placeholder-1/>"
+
+#: ./doc/common/section_cli_nova_metadata.xml18(para)
+msgid ""
+"When viewing the server information, you can see the metadata included on "
+"the <literal>metadata</literal> line: <placeholder-1/>"
+msgstr "Lorsque vous voyez les informations du serveur, vous pouvez voir les métadonnées inclues sur la ligne <literal>metadata</literal>: <placeholder-1/>"
+
+#: ./doc/common/section_cli_overview.xml7(title)
+#: ./doc/common/section_dashboard_access.xml105(guilabel)
+#: ./doc/common/section_dashboard_access.xml229(guilabel)
+msgid "Overview"
+msgstr "Vue d'ensemble"
+
+#: ./doc/common/section_cli_overview.xml8(para)
+msgid ""
+"Each OpenStack project provides a command-line client, which enables you to "
+"access the project API through easy-to-use commands. For example, the "
+"Compute service provides a nova command-line client."
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml13(para)
+msgid ""
+"You can run the commands from the command line, or include the commands "
+"within scripts to automate tasks. If you provide OpenStack credentials, such"
+" as your user name and password, you can run these commands on any computer."
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml19(para)
+msgid ""
+"Internally, each command uses cURL command-line tools, which embed API "
+"requests. OpenStack APIs are RESTful APIs, and use the HTTP protocol. They "
+"include methods, URIs, media types, and response codes."
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml24(para)
+msgid ""
+"OpenStack APIs are open-source Python clients, and can run on Linux or Mac "
+"OS X systems. On some client commands, you can specify a <placeholder-1/> "
+"parameter to show the underlying API request for the command. This is a good"
+" way to become familiar with the OpenStack API calls."
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml30(para)
+msgid ""
+"The following table lists the command-line client for each OpenStack service"
+" with its package name and description."
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml33(caption)
+msgid "OpenStack services and clients"
+msgstr "Les services et les clients d'OpenStack"
+
+#: ./doc/common/section_cli_overview.xml40(th)
+#: ./doc/common/ch_getstart.xml29(th)
+#: ./doc/common/section_keystone-concepts.xml83(term)
+msgid "Service"
+msgstr "Service"
+
+#: ./doc/common/section_cli_overview.xml41(th)
+msgid "Client"
+msgstr "Client"
+
+#: ./doc/common/section_cli_overview.xml42(th)
+msgid "Package"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml48(td)
+#: ./doc/common/ch_getstart.xml99(glossterm)
+msgid "Block Storage"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml50(package)
+msgid "python-cinderclient"
+msgstr "python-cinderclient"
+
+#: ./doc/common/section_cli_overview.xml51(td)
+msgid "Create and manage volumes."
+msgstr "Créer et Gérer les volumes."
+
+#: ./doc/common/section_cli_overview.xml54(td)
+#: ./doc/common/section_dashboard_access.xml100(guilabel)
+#: ./doc/common/ch_getstart.xml52(glossterm)
+msgid "Compute"
+msgstr "Compute"
+
+#: ./doc/common/section_cli_overview.xml56(package)
+msgid "python-novaclient"
+msgstr "python-novaclient"
+
+#: ./doc/common/section_cli_overview.xml57(td)
+msgid "Create and manage images, instances, and flavors."
+msgstr "Créer et gérer les images, instances et types d'instance."
+
+#: ./doc/common/section_cli_overview.xml60(td)
+#: ./doc/common/ch_getstart.xml172(glossterm)
+msgid "Database Service"
+msgstr "Base de données"
+
+#: ./doc/common/section_cli_overview.xml62(package)
+msgid "python-troveclient"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml63(td)
+msgid "Create and manage databases."
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml66(td)
+msgid "Identity"
+msgstr "Identité"
+
+#: ./doc/common/section_cli_overview.xml68(package)
+msgid "python-keystoneclient"
+msgstr "python-keystoneclient"
+
+#: ./doc/common/section_cli_overview.xml69(td)
+msgid "Create and manage users, tenants, roles, endpoints, and credentials."
+msgstr "Créez et gérez des utilisateurs, des locataires, des rôles, des points de terminaison et des informations d'identification."
+
+#: ./doc/common/section_cli_overview.xml72(td)
+#: ./doc/common/ch_getstart.xml127(glossterm)
+msgid "Image Service"
+msgstr "le Service d'Image"
+
+#: ./doc/common/section_cli_overview.xml74(package)
+msgid "python-glanceclient"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml75(td)
+msgid "Create and manage images."
+msgstr "Créer et gérer les images."
+
+#: ./doc/common/section_cli_overview.xml78(td)
+#: ./doc/common/ch_getstart.xml66(glossterm)
+msgid "Networking"
+msgstr "Réseaux"
+
+#: ./doc/common/section_cli_overview.xml80(package)
+msgid "python-neutronclient"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml81(td)
+msgid ""
+"Configure networks for guest servers. This client was previously called "
+"<placeholder-1/>."
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml85(td)
+#: ./doc/common/ch_getstart.xml83(glossterm)
+msgid "Object Storage"
+msgstr "Object Storage"
+
+#: ./doc/common/section_cli_overview.xml87(package)
+msgid "python-swiftclient"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml88(td)
+msgid ""
+"Gather statistics, list items, update metadata, and upload, download, and "
+"delete files stored by the Object Storage service. Gain access to an Object "
+"Storage installation for ad hoc processing."
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml93(td)
+#: ./doc/common/section_dashboard_access.xml192(guilabel)
+#: ./doc/common/ch_getstart.xml157(glossterm)
+msgid "Orchestration"
+msgstr "Orchestration"
+
+#: ./doc/common/section_cli_overview.xml95(package)
+msgid "python-heatclient"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml96(td)
+msgid ""
+"Launch stacks from templates, view details of running stacks including "
+"events and resources, and update and delete stacks."
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml100(td)
+#: ./doc/common/ch_getstart.xml142(glossterm)
+msgid "Telemetry"
+msgstr "Métrologie"
+
+#: ./doc/common/section_cli_overview.xml102(package)
+msgid "python-ceilometerclient"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml103(td)
+msgid "Create and collect measurements across OpenStack."
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml107(para)
+msgid "An OpenStack <placeholder-1/> client is in development."
+msgstr "Un client d'OpenStack <placeholder-1/> est en train d'être développer "
+
+#: ./doc/common/section_cli_overview.xml109(para)
+msgid ""
+"For client installation instructions, see <link "
+"href=\"http://docs.openstack.org/user-"
+"guide/content/install_clients.html\">Install the OpenStack command-line "
+"clients</link>. For information about the OpenStack RC file, see <link "
+"href=\"http://docs.openstack.org/user-"
+"guide/content/cli_openrc.html\">Download and source the OpenStack RC "
+"file</link>."
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_getstart_logical_arch.xml38(None)
+msgid ""
+"@@image: 'figures/openstack-arch-havana-logical-v1.jpg'; "
+"md5=e7acaaee72722626b045eda3fae81841"
+msgstr ""
+
+#: ./doc/common/section_getstart_logical_arch.xml5(title)
+#: ./doc/common/section_getstart_logical_arch.xml33(title)
+msgid "Logical architecture"
+msgstr "Architecture du logiciel"
+
+#: ./doc/common/section_getstart_logical_arch.xml6(para)
+msgid ""
+"To design, deploy, and configure OpenStack, administrators must understand "
+"the logical architecture."
+msgstr ""
+
+#: ./doc/common/section_getstart_logical_arch.xml7(para)
+msgid "OpenStack modules are one of the following types:"
+msgstr "Les modules sont classés selon l'un des types suivants :"
+
+#: ./doc/common/section_getstart_logical_arch.xml9(term)
+msgid "Daemon"
+msgstr ""
+
+#: ./doc/common/section_getstart_logical_arch.xml11(para)
+msgid ""
+"Runs as a background process. On Linux platforms, a daemon is usually "
+"installed as a service."
+msgstr ""
+
+#: ./doc/common/section_getstart_logical_arch.xml15(term)
+msgid "Script"
+msgstr ""
+
+#: ./doc/common/section_getstart_logical_arch.xml17(para)
+msgid ""
+"Installs a virtual environment and runs tests. For example, the "
+"<code>run_tests.sh</code> script installs a virtual environment and runs "
+"unit tests on a service."
+msgstr ""
+
+#: ./doc/common/section_getstart_logical_arch.xml21(term)
+msgid "Command-line interface (CLI)"
+msgstr ""
+
+#: ./doc/common/section_getstart_logical_arch.xml23(para)
+msgid ""
+"Enables users to submit API calls to OpenStack services through easy-to-use "
+"commands."
+msgstr ""
+
+#: ./doc/common/section_getstart_logical_arch.xml29(para)
+msgid ""
+"The following diagram shows the most common, but not the only, architecture "
+"for an OpenStack cloud:"
+msgstr "le schéma ci-dessous illustre l'architecture la plus courante pour un cloud basé sur OpenStack, mais ne représente pas la seule architecture possible :"
+
+#: ./doc/common/section_getstart_logical_arch.xml42(para)
+msgid ""
+"As in <xref linkend=\"concept_arch\"/>, end users can interact through the "
+"dashboard, CLIs, and APIs. All services authenticate through a common "
+"Identity Service and individual services interact with each other through "
+"public APIs, except where privileged administrator commands are necessary."
+msgstr "Comme dans <xref linkend=\"concept_arch\"/>, les utilisateurs finaux peuvent interagir à travers le tableau de bord, les CLI, ou directement via les API, tous les services s'authentifient via un service d'identité commune, et les services individuels interagissent les uns avec les autres via des API publiques, sauf là où des privilèges d’administrateur sont nécessaires pour une commande."
+
+#: ./doc/common/section_cli_neutron-quotas.xml6(title)
+msgid "Manage Networking service quotas"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml7(para)
+msgid ""
+"A quota limits the number of available resources. A default quota might be "
+"enforced for all tenants. When you try to create more resources than the "
+"quota allows, an error occurs:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml12(para)
+msgid ""
+"Per-tenant quota configuration is also supported by the quota extension API."
+" See <link linkend=\"cfg_quotas_per_tenant\"> Per-tenant quota "
+"configuration</link> for details."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml16(title)
+msgid "Basic quota configuration"
+msgstr "Configurations basic des quotas "
+
+#: ./doc/common/section_cli_neutron-quotas.xml17(para)
+msgid ""
+"In the Networking default quota mechanism, all tenants have the same quota "
+"values, such as the number of resources that a tenant can create."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml20(para)
+msgid ""
+"The quota value is defined in the OpenStack Networking "
+"<filename>neutron.conf</filename> configuration file. To disable quotas for "
+"a specific resource, such as network, subnet, or port, remove a "
+"corresponding item from <option>quota_items</option>. This example shows the"
+" default quota values:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml41(para)
+msgid ""
+"OpenStack Networking also supports quotas for L3 resources: router and "
+"floating IP. Add these lines to the <literal>quotas</literal> section in the"
+" <filename>neutron.conf</filename> file."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml52(para)
+#: ./doc/common/section_cli_neutron-quotas.xml67(para)
+msgid "The <option>quota_items</option> option does not affect these quotas."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml55(para)
+msgid ""
+"OpenStack Networking also supports quotas for security group resources: "
+"number of security groups and the number of rules for each security group. "
+"Add these lines to the <literal>quotas</literal> section in the "
+"<filename>neutron.conf</filename> file:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml72(title)
+msgid "Configure per-tenant quotas"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml73(para)
+msgid ""
+"OpenStack Networking also supports per-tenant quota limit by quota extension"
+" API."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml77(para)
+msgid "<placeholder-1/>. Deletes defined quotas for a specified tenant."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml81(para)
+msgid "<placeholder-1/>. Lists defined quotas for all tenants."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml85(para)
+msgid "<placeholder-1/>. Shows quotas for a specified tenant."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml89(para)
+msgid "<placeholder-1/>. Updates quotas for a specified tenant."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml75(para)
+msgid ""
+"Use these commands to manage per-tenant quotas:<placeholder-1/>Only users "
+"with the <literal>admin</literal> role can change a quota value. By default,"
+" the default set of quotas are enforced for all tenants, so no "
+"<placeholder-2/> command exists."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml98(title)
+msgid "Configure Networking to show per-tenant quotas"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml99(para)
+msgid ""
+"Set the <literal>quota_driver</literal> option in the "
+"<literal>neutron.conf</literal> file:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml102(para)
+msgid ""
+"When you set this option, the output for Networking commands shows "
+"<literal>quotas</literal>."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml106(title)
+msgid "List Networking extensions"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml107(para)
+msgid "To list the Networking extensions, run this command:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml110(para)
+msgid ""
+"The command shows the <literal>quotas</literal> extension, which provides "
+"per-tenant quota management support:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml128(title)
+msgid "Show information for the quotas extension"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml129(para)
+msgid ""
+"To show information for the <literal>quotas</literal> extension, run this "
+"command:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml143(para)
+msgid ""
+"Only some plug-ins support per-tenant quotas. Specifically, Open vSwitch, "
+"Linux Bridge, and VMware NSX support them, but new versions of other plug-"
+"ins might bring additional functionality. See the documentation for each "
+"plug-in."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml151(title)
+msgid "List tenants who have per-tenant quota support"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml152(para)
+msgid ""
+"The <placeholder-1/> command lists tenants for which the per-tenant quota is"
+" enabled. The command does not list tenants with default quota support. You "
+"must be an administrative user to run this command:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml165(title)
+msgid "Show per-tenant quota values"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml166(para)
+msgid ""
+"The <placeholder-1/> reports the current set of quota limits for the "
+"specified tenant. Non-administrative users can run this command without the "
+"<parameter>--tenant_id</parameter> parameter. If per-tenant quota limits are"
+" not enabled for the tenant, the command shows the default set of quotas:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml182(para)
+msgid ""
+"The following command shows the command output for a non-administrative "
+"user:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml196(title)
+msgid "Update quota values for a specified tenant"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml197(para)
+msgid ""
+"Use the <placeholder-1/> command to update a quota for a specified tenant:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml209(para)
+msgid "You can update quotas for multiple resources through one command:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml221(para)
+msgid ""
+"To update the limits for an L3 resource such as, router or floating IP, you "
+"must define new values for the quotas after the <parameter>--</parameter> "
+"directive."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml224(para)
+msgid ""
+"This example updates the limit of the number of floating IPs for the "
+"specified tenant:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml236(para)
+msgid ""
+"You can update the limits of multiple resources by including L2 resources "
+"and L3 resource through one command."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml251(title)
+msgid "Delete per-tenant quota values"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml252(para)
+msgid "To clear per-tenant quota limits, use the <placeholder-1/> command:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml256(para)
+msgid ""
+"After you run this command, you can see that quota values for the tenant are"
+" reset to the default values:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml10(title)
+msgid "Host aggregates"
+msgstr "Agrégats d'hôtes"
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml11(para)
+msgid ""
+"Host aggregates are a mechanism to further partition an availability zone; "
+"while availability zones are visible to users, host aggregates are only "
+"visible to administrators. Host Aggregates provide a mechanism to allow "
+"administrators to assign key-value pairs to groups of machines. Each node "
+"can have multiple aggregates, each aggregate can have multiple key-value "
+"pairs, and the same key-value pair can be assigned to multiple aggregates. "
+"This information can be used in the scheduler to enable advanced scheduling,"
+" to set up hypervisor resource pools or to define logical groups for "
+"migration."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml23(title)
+msgid "Command-line interface"
+msgstr "Interface de ligne de commande"
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml35(replaceable)
+#: ./doc/common/section_cli_nova_host_aggregates.xml111(replaceable)
+msgid "&lt;name&gt;"
+msgstr "&lt;name&gt;"
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml36(replaceable)
+msgid "&lt;availability-zone&gt;"
+msgstr "&lt;availability-zone&gt;"
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml38(para)
+msgid ""
+"Create a new aggregate named <replaceable>&lt;name&gt;</replaceable> in "
+"availability zone <replaceable>&lt;availability-zone&gt;</replaceable>. "
+"Returns the ID of the newly created aggregate. Hosts can be made available "
+"to multiple availability zones, but administrators should be careful when "
+"adding the host to a different host aggregate within the same availability "
+"zone and pay attention when using the <placeholder-1/> and <placeholder-2/> "
+"commands to avoid user confusion when they boot instances in different "
+"availability zones. An error occurs if you cannot add a particular host to "
+"an aggregate zone for which it is not intended."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml60(replaceable)
+#: ./doc/common/section_cli_nova_host_aggregates.xml68(replaceable)
+#: ./doc/common/section_cli_nova_host_aggregates.xml76(replaceable)
+#: ./doc/common/section_cli_nova_host_aggregates.xml87(replaceable)
+#: ./doc/common/section_cli_nova_host_aggregates.xml98(replaceable)
+#: ./doc/common/section_cli_nova_host_aggregates.xml110(replaceable)
+msgid "&lt;id&gt;"
+msgstr "&lt;id&gt;"
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml62(para)
+msgid "Delete an aggregate with id <replaceable>&lt;id&gt;</replaceable>."
+msgstr "Supprimer un agrégat ayant l'id <replaceable>&lt;id&gt;</replaceable>."
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml70(para)
+msgid ""
+"Show details of the aggregate with id <replaceable>&lt;id&gt;</replaceable>."
+msgstr "Montrer les détails de l'agrégat ayant l'id <replaceable>&lt;id&gt;</replaceable>.."
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml77(replaceable)
+#: ./doc/common/section_cli_nova_host_aggregates.xml88(replaceable)
+msgid "&lt;host&gt;"
+msgstr "&lt;host&gt;"
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml79(para)
+msgid ""
+"Add host with name <replaceable>&lt;host&gt;</replaceable> to aggregate with"
+" id <replaceable>&lt;id&gt;</replaceable>."
+msgstr "Ajouter l'hôte nommé <replaceable>&lt;host&gt;</replaceable> à l'agrégat ayant l'id <replaceable>&lt;id&gt;</replaceable>."
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml90(para)
+msgid ""
+"Remove the host with name <replaceable>&lt;host&gt;</replaceable> from the "
+"aggregate with id <replaceable>&lt;id&gt;</replaceable>."
+msgstr "Supprimer l'hôte nommé <replaceable>&lt;host&gt;</replaceable> de l'agrégat ayant l'id <replaceable>&lt;id&gt;</replaceable>."
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml99(replaceable)
+#: ./doc/common/section_cli_nova_host_aggregates.xml100(replaceable)
+msgid "&lt;key=value&gt;"
+msgstr "&lt;key=value&gt;"
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml103(para)
+msgid ""
+"Add or update metadata (key-value pairs) associated with the aggregate with "
+"id <replaceable>&lt;id&gt;</replaceable>."
+msgstr "Ajouter ou modifier des méta données (paires de valeurs-clés) associées à l'agrégat ayant l'id <replaceable>&lt;id&gt;</replaceable>."
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml112(replaceable)
+msgid "&lt;availability_zone&gt;"
+msgstr "&lt;availability_zone&gt;"
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml114(para)
+msgid "Update the name and availability zone (optional) for the aggregate."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml128(para)
+msgid "Put/resume host into/from maintenance."
+msgstr "Mettre/retirer les hôtes en/de la maintenance."
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml24(para)
+msgid ""
+"The <placeholder-1/> command-line tool supports the following aggregate-"
+"related commands. <placeholder-2/>"
+msgstr "L'outil de ligne de commande <placeholder-1/> supporte les commandes relatives aux agrégats suivantes. <placeholder-2/>"
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml134(para)
+msgid ""
+"Only administrators can access these commands. If you try to use these "
+"commands and the user name and tenant that you use to access the Compute "
+"service do not have the <literal>admin</literal> role or the appropriate "
+"privileges, these errors occur:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml146(title)
+msgid "Configure scheduler to support host aggregates"
+msgstr "Configurer le planificateur pour qu'il supporte les agrégats d'hôtes"
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml147(para)
+msgid ""
+"One common use case for host aggregates is when you want to support "
+"scheduling instances to a subset of compute hosts because they have a "
+"specific capability. For example, you may want to allow users to request "
+"compute hosts that have SSD drives if they need access to faster disk I/O, "
+"or access to compute hosts that have GPU cards to take advantage of GPU-"
+"accelerated code."
+msgstr "Généralement, les agrégats d'hôtes sont utilisés lorsque vous souhaitez supporter les instances de planifications pour un sous-ensemble d'ordinateurs hôtes du fait de leur capacité spécifique. Par exemple, vous pourrez vouloir autoriser les utilisateurs à demander aux ordinateurs hôtes ayant des disques SSD  s'ils nécessitent un accès à un disque I/O plus rapide ou un accès à des ordinateurs hôtes qui ont des cartes GPU tirant partie des codes GPU avancés."
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml154(para)
+msgid ""
+"To configure the scheduler to support host aggregates, the "
+"<literal>scheduler_default_filters</literal> configuration option must "
+"contain the <literal>AggregateInstanceExtraSpecsFilter</literal> in addition"
+" to the other filters used by the scheduler. Add the following line to "
+"<filename>/etc/nova/nova.conf</filename> on the host that runs the "
+"<systemitem class=\"service\">nova-scheduler</systemitem> service to enable "
+"host aggregates filtering, as well as the other filters that are typically "
+"enabled:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml168(title)
+msgid "Example: Specify compute hosts with SSDs"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml169(para)
+msgid ""
+"This example configures the Compute service to enable users to request nodes"
+" that have solid-state drives (SSDs). You create a <literal>fast-"
+"io</literal> host aggregate in the <literal>nova</literal> availability zone"
+" and you add the <literal>ssd=true</literal> key-value pair to the "
+"aggregate. Then, you add the <literal>node1</literal>, and "
+"<literal>node2</literal> compute nodes to it."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml204(para)
+msgid ""
+"Use the <placeholder-1/> command to create the "
+"<replaceable>ssd.large</replaceable> flavor called with an ID of 6, 8GB of "
+"RAM, 80GB root disk, and four vCPUs."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml207(replaceable)
+#: ./doc/common/section_cli_nova_host_aggregates.xml219(replaceable)
+msgid "ssd.large"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml207(replaceable)
+msgid "6"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml207(replaceable)
+msgid "8192"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml207(replaceable)
+msgid "80"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml207(replaceable)
+msgid "4"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml213(para)
+msgid ""
+"Once the flavor is created, specify one or more key-value pairs that match "
+"the key-value pairs on the host aggregates. In this case, that is the "
+"<replaceable>ssd=true</replaceable> key-value pair. Setting a key-value pair"
+" on a flavor is done using the <placeholder-1/> command."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml219(replaceable)
+msgid "ssd=true"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml220(para)
+msgid ""
+"Once it is set, you should see the <literal>extra_specs</literal> property "
+"of the <literal>ssd.large</literal> flavor populated with a key of "
+"<literal>ssd</literal> and a corresponding value of <literal>true</literal>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml241(para)
+msgid ""
+"Now, when a user requests an instance with the <literal>ssd.large</literal> "
+"flavor, the scheduler only considers hosts with the "
+"<literal>ssd=true</literal> key-value pair. In this example, these are "
+"<literal>node1</literal> and <literal>node2</literal>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml249(title)
+msgid "XenServer hypervisor pools to support live migration"
+msgstr "Pools de l'hyperviseur XenServeur pour supporter la live migration"
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml251(para)
+msgid ""
+"When using the XenAPI-based hypervisor, the Compute service uses host "
+"aggregates to manage XenServer Resource pools, which are used in supporting "
+"live migration."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml6(title)
+#: ./doc/common/section_objectstorage-components.xml192(title)
+msgid "Replication"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml7(para)
+msgid ""
+"Because each replica in Object Storage functions independently and clients "
+"generally require only a simple majority of nodes to respond to consider an "
+"operation successful, transient failures like network partitions can quickly"
+" cause replicas to diverge. These differences are eventually reconciled by "
+"asynchronous, peer-to-peer replicator processes. The replicator processes "
+"traverse their local file systems and concurrently perform operations in a "
+"manner that balances load across physical disks."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml16(para)
+msgid ""
+"Replication uses a push model, with records and files generally only being "
+"copied from local to remote replicas. This is important because data on the "
+"node might not belong there (as in the case of hand offs and ring changes), "
+"and a replicator cannot know which data it should pull in from elsewhere in "
+"the cluster. Any node that contains data must ensure that data gets to where"
+" it belongs. The ring handles replica placement."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml24(para)
+msgid ""
+"To replicate deletions in addition to creations, every deleted record or "
+"file in the system is marked by a tombstone. The replication process cleans "
+"up tombstones after a time period known as the <emphasis "
+"role=\"italic\">consistency window</emphasis>. This window defines the "
+"duration of the replication and how long transient failure can remove a node"
+" from the cluster. Tombstone cleanup must be tied to replication to reach "
+"replica convergence."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml32(para)
+msgid ""
+"If a replicator detects that a remote drive has failed, the replicator uses "
+"the <literal>get_more_nodes</literal> interface for the ring to choose an "
+"alternate node with which to synchronize. The replicator can maintain "
+"desired levels of replication during disk failures, though some replicas "
+"might not be in an immediately usable location."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml39(para)
+msgid ""
+"The replicator does not maintain desired levels of replication when failures"
+" such as entire node failures occur; most failures are transient."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml43(para)
+msgid "The main replication types are:"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml46(para)
+msgid ""
+"<emphasis role=\"bold\">Database replication</emphasis>. Replicates "
+"containers and objects."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml51(para)
+msgid ""
+"<emphasis role=\"bold\">Object replication</emphasis>. Replicates object "
+"data."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml56(title)
+msgid "Database replication"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml57(para)
+msgid ""
+"Database replication completes a low-cost hash comparison to determine "
+"whether two replicas already match. Normally, this check can quickly verify "
+"that most databases in the system are already synchronized. If the hashes "
+"differ, the replicator synchronizes the databases by sharing records added "
+"since the last synchronization point."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml64(para)
+msgid ""
+"This synchronization point is a high water mark that notes the last record "
+"at which two databases were known to be synchronized, and is stored in each "
+"database as a tuple of the remote database ID and record ID. Database IDs "
+"are unique across all replicas of the database, and record IDs are "
+"monotonically increasing integers. After all new records are pushed to the "
+"remote database, the entire synchronization table of the local database is "
+"pushed, so the remote database can guarantee that it is synchronized with "
+"everything with which the local database was previously synchronized."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml75(para)
+msgid ""
+"If a replica is missing, the whole local database file is transmitted to the"
+" peer by using rsync(1) and is assigned a new unique ID."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml78(para)
+msgid ""
+"In practice, database replication can process hundreds of databases per "
+"concurrency setting per second (up to the number of available CPUs or disks)"
+" and is bound by the number of database transactions that must be performed."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml85(title)
+msgid "Object replication"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml86(para)
+msgid ""
+"The initial implementation of object replication performed an rsync to push "
+"data from a local partition to all remote servers where it was expected to "
+"reside. While this worked at small scale, replication times skyrocketed once"
+" directory structures could no longer be held in RAM. This scheme was "
+"modified to save a hash of the contents for each suffix directory to a per-"
+"partition hashes file. The hash for a suffix directory is no longer valid "
+"when the contents of that suffix directory is modified."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml95(para)
+msgid ""
+"The object replication process reads in hash files and calculates any "
+"invalidated hashes. Then, it transmits the hashes to each remote server that"
+" should hold the partition, and only suffix directories with differing "
+"hashes on the remote server are rsynced. After pushing files to the remote "
+"server, the replication process notifies it to recalculate hashes for the "
+"rsynced suffix directories."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml103(para)
+msgid ""
+"The number of uncached directories that object replication must traverse, "
+"usually as a result of invalidated suffix directory hashes, impedes "
+"performance. To provide acceptable replication speeds, object replication is"
+" designed to invalidate around 2 percent of the hash space on a normal node "
+"each day."
+msgstr ""
+
+#: ./doc/common/section_getstart_networking.xml5(title)
+msgid "OpenStack Networking"
+msgstr ""
+
+#: ./doc/common/section_getstart_networking.xml6(para)
+msgid ""
+"OpenStack Networking allows you to create and attach interface devices "
+"managed by other OpenStack services to networks. Plug-ins can be implemented"
+" to accomodate different networking equipment and software, providing "
+"flexibility to OpenStack architecture and deployment."
+msgstr ""
+
+#: ./doc/common/section_getstart_networking.xml14(systemitem)
+msgid "neutron-server"
+msgstr ""
+
+#: ./doc/common/section_getstart_networking.xml15(para)
+msgid ""
+"Accepts and routes API requests to the appropriate OpenStack Networking "
+"plug-in for action."
+msgstr ""
+
+#: ./doc/common/section_getstart_networking.xml19(term)
+msgid "OpenStack Networking plug-ins and agents"
+msgstr ""
+
+#: ./doc/common/section_getstart_networking.xml20(para)
+msgid ""
+"Plugs and unplugs ports, creates networks or subnets, and provides IP "
+"addressing. These plug-ins and agents differ depending on the vendor and "
+"technologies used in the particular cloud. OpenStack Networking ships with "
+"plug-ins and agents for Cisco virtual and physical switches, NEC OpenFlow "
+"products, Open vSwitch, Linux bridging, Ryu Network Operating System, and "
+"the VMware NSX product."
+msgstr ""
+
+#: ./doc/common/section_getstart_networking.xml27(para)
+msgid ""
+"The common agents are L3 (layer 3), DHCP (dynamic host IP addressing), and a"
+" plug-in agent."
+msgstr ""
+
+#: ./doc/common/section_getstart_networking.xml31(term)
+#: ./doc/common/section_getstart_block-storage.xml35(term)
+msgid "Messaging queue"
+msgstr ""
+
+#: ./doc/common/section_getstart_networking.xml32(para)
+msgid ""
+"Used by most OpenStack Networking installations to route information between"
+" the neutron-server and various agents, as well as a database to store "
+"networking state for particular plug-ins."
+msgstr ""
+
+#: ./doc/common/section_getstart_networking.xml38(para)
+msgid ""
+"OpenStack Networking mainly interacts with OpenStack Compute to provide "
+"networks and connectivity for its instances."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_evacuate.xml6(title)
+msgid "Evacuate instances"
+msgstr "Evacuation d'une instance"
+
+#: ./doc/common/section_cli_nova_evacuate.xml7(para)
+msgid ""
+"If a cloud compute node fails due to a hardware malfunction or another "
+"reason, you can evacuate instances to make them available again. You can "
+"choose evacuation parameters for your use case."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_evacuate.xml10(para)
+msgid ""
+"To preserve user data on server disk, you must configure shared storage on "
+"the target host. Also, you must validate that the current VM host is down; "
+"otherwise, the evacuation fails with an error."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_evacuate.xml15(para)
+msgid ""
+"To list hosts and find a different host for the evacuated instance, run:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_evacuate.xml19(para)
+msgid ""
+"Evacuate the instance. You can pass the instance password to the command by "
+"using the <literal>--password &lt;pwd&gt;</literal> option. If you do not "
+"specify a password, one is generated and printed after the command finishes "
+"successfully. The following command evacuates a server without shared "
+"storage from a host that is down to the specified "
+"<replaceable>host_b</replaceable>:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_evacuate.xml24(replaceable)
+#: ./doc/common/section_cli_nova_evacuate.xml40(replaceable)
+msgid "evacuated_server_name"
+msgstr "evacuated_server_name"
+
+#: ./doc/common/section_cli_nova_evacuate.xml24(replaceable)
+#: ./doc/common/section_cli_nova_evacuate.xml40(replaceable)
+msgid "host_b"
+msgstr "host_b"
+
+#: ./doc/common/section_cli_nova_evacuate.xml25(para)
+msgid ""
+"The instance is booted from a new disk, but preserves its configuration "
+"including its ID, name, uid, IP address, and so on. The command returns a "
+"password:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_evacuate.xml34(para)
+msgid ""
+"To preserve the user disk data on the evacuated server, deploy OpenStack "
+"Compute with a shared file system. To configure your system, see <link "
+"href=\"http://docs.openstack.org/icehouse/config-reference/content"
+"/configuring-openstack-compute-basics.html#section_configuring-compute-"
+"migrations\">Configure migrations</link> in <citetitle>OpenStack "
+"Configuration Reference</citetitle>. In the following example, the password "
+"remains unchanged:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_terminate.xml8(title)
+msgid "Delete an instance"
+msgstr "Supprimer une instance "
+
+#: ./doc/common/section_cli_nova_terminate.xml9(para)
+msgid "When you no longer need an instance, you can delete it."
+msgstr "Lorsque vous n'avez plus besoin d'une instance, vous pouvez la supprimer."
+
+#: ./doc/common/section_cli_nova_terminate.xml11(para)
+msgid "List all instances:"
+msgstr "Listez tous les instances:"
+
+#: ./doc/common/section_cli_nova_terminate.xml21(para)
+msgid ""
+"Run the <placeholder-1/> command to delete the instance. The following "
+"example shows deletion of the <filename>newServer</filename> instance, which"
+" is in <literal>ERROR</literal> state:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_terminate.xml24(para)
+msgid "The command does not notify that your server was deleted."
+msgstr "Vous ne recevrez aucune notification indiquant la suppression du server."
+
+#: ./doc/common/section_cli_nova_terminate.xml25(para)
+msgid ""
+"To verify that the server was deleted, run the <placeholder-1/> command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_terminate.xml33(para)
+msgid "The deleted instance does not appear in the list."
+msgstr "L'instance qui a été supprimée ne s'affiche pas dans la liste."
+
+#: ./doc/common/section_compute-configure-spice.xml6(title)
+msgid "SPICE console"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-spice.xml7(para)
+msgid ""
+"OpenStack Compute supports VNC consoles to guests. The VNC protocol is "
+"fairly limited, lacking support for multiple monitors, bi-directional audio,"
+" reliable cut-and-paste, video streaming and more. SPICE is a new protocol "
+"that aims to address the limitations in VNC and provide good remote desktop "
+"support."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-spice.xml12(para)
+msgid ""
+"SPICE support in OpenStack Compute shares a similar architecture to the VNC "
+"implementation. The OpenStack dashboard uses a SPICE-HTML5 widget in its "
+"console tab that communicates to the <systemitem class=\"service\">nova-"
+"spicehtml5proxy</systemitem> service by using SPICE-over-websockets. The "
+"<systemitem class=\"service\">nova-spicehtml5proxy</systemitem> service "
+"communicates directly with the hypervisor process by using SPICE."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-spice.xml19(para)
+msgid ""
+"VNC must be explicitly disabled to get access to the SPICE console. Set the "
+"<option>vnc_enabled</option> option to <literal>False</literal> in the "
+"<literal>[DEFAULT]</literal> section to disable the VNC console."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-spice.xml22(para)
+msgid ""
+"Use the following options to configure SPICE as the console for OpenStack "
+"Compute:"
+msgstr ""
+
+#: ./doc/common/section_getstart_block-storage.xml5(title)
+msgid "OpenStack Block Storage"
+msgstr ""
+
+#: ./doc/common/section_getstart_block-storage.xml6(para)
+msgid ""
+"OpenStack Block Storage enables management of volumes, volume snapshots, and"
+" volume types. It consists of the following components:"
+msgstr ""
+
+#: ./doc/common/section_getstart_block-storage.xml11(systemitem)
+msgid "cinder-api"
+msgstr ""
+
+#: ./doc/common/section_getstart_block-storage.xml12(para)
+msgid ""
+"Accepts API requests and routes them to <systemitem class=\"service"
+"\">cinder-volume</systemitem> for action."
+msgstr ""
+
+#: ./doc/common/section_getstart_block-storage.xml17(systemitem)
+msgid "cinder-volume"
+msgstr ""
+
+#: ./doc/common/section_getstart_block-storage.xml18(para)
+msgid ""
+"Responds to requests to read from and write to the OpenStack Block Storage "
+"database to maintain state, interacting with other processes (like "
+"<systemitem class=\"service\">cinder-scheduler</systemitem>) through a "
+"message queue and directly upon block storage providing hardware or "
+"software. It can interact with a variety of storage providers through a "
+"driver architecture."
+msgstr ""
+
+#: ./doc/common/section_getstart_block-storage.xml28(term)
+msgid "<systemitem class=\"service\">cinder-scheduler</systemitem> daemon"
+msgstr ""
+
+#: ./doc/common/section_getstart_block-storage.xml30(para)
+msgid ""
+"Like the <systemitem class=\"service\">nova-scheduler</systemitem>, picks "
+"the optimal block storage provider node on which to create the volume."
+msgstr ""
+
+#: ./doc/common/section_getstart_block-storage.xml36(para)
+msgid "Routes information between the Block Storage processes."
+msgstr ""
+
+#: ./doc/common/section_getstart_block-storage.xml40(para)
+msgid ""
+"OpenStack Block Storage interacts with OpenStack Compute to provide volumes "
+"for instances."
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-vnc-window.xml6(title)
+msgid "Change the size of the dashboard VNC window"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-vnc-window.xml7(para)
+msgid ""
+"The <filename>_detail_vnc.html</filename> file defines the size of the VNC "
+"window. To change the window size, edit this file."
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-vnc-window.xml12(para)
+msgid ""
+"Edit "
+"<filename>/usr/share/pyshared/horizon/dashboards/nova/instances/templates/instances/_detail_vnc.html.</filename>"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-vnc-window.xml16(para)
+msgid ""
+"Modify the <literal>width</literal> and <literal>height</literal> "
+"parameters, as follows:"
+msgstr "Modifiez les paramètres width (largeur) et height (hauteur), comme suit :"
+
+#: ./doc/common/section_using-vnc-console.xml6(title)
+msgid "Use the VNC console"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml7(para)
+msgid ""
+"To interact through the VNC console, you can use a VNC client directly, a "
+"special Java client, or a web browser. For information about how to "
+"configure the console, see <xref linkend=\"installing-openstack-"
+"dashboard\"/>."
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml15(title)
+msgid "Get an access URL"
+msgstr "obtenez une URL d’accès :"
+
+#: ./doc/common/section_using-vnc-console.xml16(para)
+msgid ""
+"The Compute service enables you to create access_urls through the os-"
+"consoles extension. Support for accessing this URL is provided by the nova "
+"client:"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml19(replaceable)
+#: ./doc/common/section_using-vnc-console.xml25(replaceable)
+#: ./doc/common/section_using-vnc-console.xml52(replaceable)
+#: ./doc/common/section_using-vnc-console.xml65(replaceable)
+msgid "[server_id]"
+msgstr "[server_id]"
+
+#: ./doc/common/section_using-vnc-console.xml19(replaceable)
+msgid "[novnc|xvpvnc]"
+msgstr "[novnc|xvpvnc]"
+
+#: ./doc/common/section_using-vnc-console.xml20(para)
+msgid ""
+"Specify '<literal>novnc</literal>' to get a URL suitable for pasting into a "
+"web browser."
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml22(para)
+msgid ""
+"Specify '<literal>xvpvnc</literal>' for a URL suitable for pasting into the "
+"Java client."
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml24(para)
+msgid "To request a web browser URL:"
+msgstr "Pour demander une URL de navigateur web:"
+
+#: ./doc/common/section_using-vnc-console.xml28(title)
+msgid "Access a VNC console with a Java client"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml29(para)
+msgid ""
+"To enable support for the OpenStack Java VNC client in compute, run the "
+"<literal>nova-xvpvncproxy</literal> service."
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml34(para)
+msgid ""
+"<literal>xvpvncproxy_port</literal>=<replaceable>[port]</replaceable> - port"
+" to bind (defaults to 6081)"
+msgstr "<literal>xvpvncproxy_port</literal>=<replaceable>[port]</replaceable> - port  à attacher (par défaut à 6081)"
+
+#: ./doc/common/section_using-vnc-console.xml38(para)
+msgid ""
+"<literal>xvpvncproxy_host</literal>=<replaceable>[host]</replaceable> - host"
+" to bind (defaults to 0.0.0.0)"
+msgstr "<literal>xvpvncproxy_host</literal>=<replaceable>[host]</replaceable> - hôte à attacher (par défaut à 0.0.0.0)"
+
+#: ./doc/common/section_using-vnc-console.xml42(para)
+msgid ""
+"As a client, you need a special Java client, which is a slightly modified "
+"version of TightVNC that supports our token auth:"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml48(para)
+msgid ""
+"To create a session, request an access URL by using <placeholder-1/>. Then, "
+"run the client as follows."
+msgstr "Pour créer une session, demander une URL d'accès en utilisant <placeholder-1/>. Puis exécutez le client comme suit."
+
+#: ./doc/common/section_using-vnc-console.xml51(para)
+msgid "To get an access URL:"
+msgstr "Pour obtenir une URL d'accès:"
+
+#: ./doc/common/section_using-vnc-console.xml53(para)
+msgid "To run the client:"
+msgstr "Accéder aux consoles VNC avec un client Java"
+
+#: ./doc/common/section_using-vnc-console.xml54(replaceable)
+msgid "[access_url]"
+msgstr "[access_url]"
+
+#: ./doc/common/section_using-vnc-console.xml59(title)
+msgid "Access a VNC console with a web browser"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml61(para)
+msgid ""
+"Retrieving an access_url for a web browser is similar to the flow for the "
+"Java client."
+msgstr "Récupérer une URL d’accès pour un navigateur web est similaire à la procédure pour le client Java."
+
+#: ./doc/common/section_using-vnc-console.xml63(para)
+msgid "To get the access URL, run the following command:"
+msgstr "Pour obtenir l'URL d'accès, exécutez la commande :"
+
+#: ./doc/common/section_using-vnc-console.xml66(para)
+msgid "Paste the URL into your web browser."
+msgstr "Collez l'URL dans votre navigateur web."
+
+#: ./doc/common/section_using-vnc-console.xml68(para)
+msgid ""
+"Additionally, you can use the OpenStack dashboard, known as horizon, to "
+"access browser-based VNC consoles for instances."
+msgstr "Collez l'URL dans votre navigateur web."
+
+#: ./doc/common/section_cli_nova_userdata.xml6(title)
+msgid "Provide user data to instances"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_userdata.xml7(para)
+msgid ""
+"A <glossterm baseform=\"user data\">user data</glossterm> file is a special "
+"key in the metadata service that holds a file that cloud-aware applications "
+"in the guest instance can access. For example, one application that uses "
+"user data is the <link href=\"https://help.ubuntu.com/community/CloudInit"
+"\">cloud-init</link> system, which is an open-source package from Ubuntu "
+"that is available on various Linux distributions and which handles early "
+"initialization of a cloud instance."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_userdata.xml14(para)
+msgid ""
+"You can place user data in a local file and pass it through the <parameter"
+">--user-data &lt;user-data-file&gt;</parameter> parameter at instance "
+"creation:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_sshkeys.xml6(title)
+msgid "Add keypair"
+msgstr "Ajouter une paire de clés"
+
+#: ./doc/common/section_cli_nova_sshkeys.xml7(para)
+msgid ""
+"Create at least one keypair for each project. If you have generated a "
+"keypair with an external tool, you can import it into OpenStack. The keypair"
+" can be used for multiple instances that belong to a project."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_sshkeys.xml13(para)
+msgid "Create a key."
+msgstr "Créez une clé."
+
+#: ./doc/common/section_cli_nova_sshkeys.xml14(para)
+msgid ""
+"To create a <literal>mykey</literal> key that you can associate with "
+"instances, run the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_sshkeys.xml17(para)
+msgid ""
+"Save the <filename>mykey.pem</filename> file to a secure location. It "
+"enables root access to any instances with which the <literal>mykey</literal>"
+" key is associated."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_sshkeys.xml22(para)
+msgid "Alternatively, you can import a keypair."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_sshkeys.xml23(para)
+msgid ""
+"To import an existing public key, <literal>mykey.pub</literal>, and "
+"associate it with the <literal>mykey</literal> key, run the following "
+"command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_sshkeys.xml28(para)
+msgid ""
+"You must have the matching private key to access instances that are "
+"associated with this key."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml6(title)
+msgid "Secure the OpenStack Identity service connection to an LDAP back end"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml8(para)
+msgid ""
+"The Identity service supports the use of TLS to encrypt LDAP traffic. Before"
+" configuring this, you must first verify where your certificate authority "
+"file is located. For more information, see <xref linkend=\"certificates-for-"
+"pki\"/>."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml12(para)
+msgid "Once you verify the location of your certificate authority file:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml15(title)
+msgid "Configuring TLS encryption on LDAP traffic"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml17(para)
+msgid ""
+"Open the <filename>/etc/keystone/keystone.conf</filename> configuration "
+"file."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml23(para)
+msgid "Find the <literal>[ldap]</literal> section."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml26(para)
+msgid ""
+"In the <literal>[ldap]</literal> section, set the <literal>use_tls</literal>"
+" configuration key to <literal>True</literal>. Doing so will enable TLS."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml31(para)
+msgid ""
+"Configure the Identity service to use your certificate authorities file. To "
+"do so, set the <literal>tls_cacertfile</literal> configuration key in the "
+"<literal>ldap</literal> section to the certificate authorities file's path."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml37(para)
+msgid ""
+"You can also set the <literal>tls_cacertdir</literal> (also in the "
+"<literal>ldap</literal> section) to the directory where all certificate "
+"authorities files are kept. If both <literal>tls_cacertfile</literal> and "
+"<literal>tls_cacertdir</literal> are set, then the latter will be ignored."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml46(para)
+msgid ""
+"Specify what client certificate checks to perform on incoming TLS sessions "
+"from the LDAP server. To do so, set the <literal>tls_req_cert</literal> "
+"configuration key in the <literal>[ldap]</literal> section to "
+"<literal>demand</literal>, <literal>allow</literal>, or "
+"<literal>never</literal>:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml53(para)
+msgid ""
+"<parameter>demand</parameter>: a certificate will always be requested from "
+"the LDAP server. The session will be terminated if no certificate is "
+"provided, or if the certificate provided cannot be verified against the "
+"existing certificate authorities file."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml60(para)
+msgid ""
+"<parameter>allow</parameter>: a certificate will always be requested from "
+"the LDAP server. The session will proceed as normal even if a certificate is"
+" not provided. If a certificate is provided but it cannot be verified "
+"against the existing certificate authorities file, the certificate will be "
+"ignored and the session will proceed as normal."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml67(para)
+msgid "<parameter>never</parameter>: a certificate will never be requested."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml72(para)
+msgid ""
+"On distributions that include <application>openstack-config</application>, "
+"you can configure TLS encryption on LDAP traffic by running the following "
+"commands instead:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml80(replaceable)
+msgid "CA_FILE"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml82(replaceable)
+msgid "CERT_BEHAVIOR"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml85(para)
+msgid ""
+"<replaceable>CA_FILE</replaceable> is the absolute path to the certificate "
+"authorities file that should be used to encrypt LDAP traffic."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml88(para)
+msgid ""
+"<replaceable>CERT_BEHAVIOR</replaceable>: specifies what client certificate "
+"checks to perform on an incoming TLS session from the LDAP server "
+"(<literal>demand</literal>, <literal>allow</literal>, or "
+"<literal>never</literal>)."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml7(title)
+msgid "Certificates for PKI"
+msgstr "Certificats pour PKI"
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml8(para)
+msgid ""
+"PKI stands for Public Key Infrastructure. Tokens are documents, "
+"cryptographically signed using the X509 standard. In order to work correctly"
+" token generation requires a public/private key pair. The public key must be"
+" signed in an X509 certificate, and the certificate used to sign it must be "
+"available as Certificate Authority (CA) certificate. These files can be "
+"generated either using the <placeholder-1/> utility, or externally "
+"generated. The files need to be in the locations specified by the top level "
+"Identity Service configuration file <filename>keystone.conf</filename> as "
+"specified in the above section. Additionally, the private key should only be"
+" readable by the system user that will run the Identity Service."
+msgstr "PKI signifie Public Key Infrastructure (Infrastructure de Clé Publique). Les jetons sont des document , signés de façon cryptographique via les standards X509. Afin de fonctionner correctement, l'émission de jetons nécessite une paire de clés publique/privée. La clé publique doit être signée dans un certificat X509, et le certificat utilisé pour la signer doit être disponible comme certificat d’Autorité de Certification (CA). Ces fichiers peuvent être générés soit en utilisant l'utilitaire keystone-manage, ou être générés de façon extérieure. Les fichiers doivent être dans les emplacements spécifiés par le fichier de configuration Keystone de plus haut niveau, comme spécifié dans la section précédente. De plus, la clé privée ne devrait être lisible que par l'utilisateur système qui mettra Keystone en marche."
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml23(para)
+msgid ""
+"The certificates can be world readable, but the private key cannot be. The "
+"private key should only be readable by the account that is going to sign "
+"tokens. When generating files with the <placeholder-1/> command, your best "
+"option is to run as the pki user. If you run nova-manage as root, you can "
+"append --keystone-user and --keystone-group parameters to set the username "
+"and group keystone is going to run under."
+msgstr "Les certificats peuvent être lus mondialement, mais non la clé privée. La clé privée ne devrait être lisible que par le compte qui va signer les jetons.  Lorsque l'on génère des fichiers avec la commande <placeholder-1/>, la meilleure option est de la lancer en tant qu'utilisateur pki. Si vous lancez nova-manage en tant qu’administrateur vous pouvez ajouter des paramètres keystone-user et --keystone-group pour définir le nom d'utilisateur et le groupe sous lesquels keystone va fonctionner."
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml33(para)
+msgid ""
+"The values that specify where to read the certificates are under the "
+"<literal>[signing]</literal> section of the configuration file. The "
+"configuration values are:"
+msgstr "Les valeurs qui spécifient où lire les certificats sont dans la section  <literal>[signing]</literal> du fichier de  configuration. Les valeurs de configuration sont :"
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml38(para)
+msgid ""
+"<literal>token_format</literal> - Determines the algorithm used to generate "
+"tokens. Can be either <literal>UUID</literal> or <literal>PKI</literal>. "
+"Defaults to <literal>PKI</literal>."
+msgstr "<literal>token_format</literal> – Détermine l'algorithme utilisé pour générer les jetons. Peut être soit <literal>UUID</literal> ou <literal>PKI</literal>. Par défaut <literal>PKI</literal>."
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml45(para)
+msgid ""
+"<literal>certfile</literal> - Location of certificate used to verify tokens."
+" Default is <literal>/etc/keystone/ssl/certs/signing_cert.pem</literal>."
+msgstr "<literal>certfile</literal> – Emplacement du certificat utilisé pour vérifier les jetons. Par défaut <literal>/etc/keystone/ssl/certs/signing_cert.pem</literal>."
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml51(para)
+msgid ""
+"<literal>keyfile</literal> - Location of private key used to sign tokens. "
+"Default is <literal>/etc/keystone/ssl/private/signing_key.pem</literal>."
+msgstr "<literal>keyfile</literal> – Emplacement de la clé privée utilisée pour signer les jetons. Par défaut  <literal>/etc/keystone/ssl/private/signing_key.pem</literal>"
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml57(para)
+msgid ""
+"<literal>ca_certs</literal> - Location of certificate for the authority that"
+" issued the above certificate. Default is "
+"<literal>/etc/keystone/ssl/certs/ca.pem</literal>."
+msgstr "<literal>ca_certs</literal> – Emplacement du certificat pour l'autorité ayant émis le certificat précédent. Par défaut <literal>/etc/keystone/ssl/certs/ca.pem</literal>."
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml64(para)
+msgid "<literal>key_size</literal> - Default is <literal>1024</literal>."
+msgstr "<literal>key_size</literal> – Par défaut <literal>1024</literal>."
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml69(para)
+msgid "<literal>valid_days</literal> - Default is <literal>3650</literal>."
+msgstr "<literal>valid_days</literal>  - Par défaut <literal>3650</literal>."
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml74(para)
+msgid ""
+"<literal>ca_password</literal> - Password required to read the "
+"<literal>ca_file</literal>. Default is <literal>None</literal>."
+msgstr "<literal>ca_password</literal> – Mot de passe requis pour lire le <literal>ca_file</literal>. Par défaut <literal>None</literal>."
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml80(para)
+msgid ""
+"If <literal>token_format=UUID</literal>, a typical token looks like "
+"<literal>53f7f6ef0cc344b5be706bcc8b1479e1</literal>. If "
+"<literal>token_format=PKI</literal>, a typical token is a much longer "
+"string, such as:"
+msgstr " Si <literal>token_format=UUID</literal>, un jeton typique ressemblera à <literal>53f7f6ef0cc344b5be706bcc8b1479e1</literal>. Si <literal>token_format=PKI</literal>, un jeton typique sera beaucoup plus long, comme ceci :"
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml113(title)
+msgid "Sign certificate issued by external CA"
+msgstr "Signer un Certificat émis par une CA externe"
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml114(para)
+msgid ""
+"You can use a signing certificate issued by an external CA instead of "
+"generated by <placeholder-1/>. However, a certificate issued by an external "
+"CA must satisfy the following conditions:"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml121(para)
+msgid ""
+"all certificate and key files must be in Privacy Enhanced Mail (PEM) format"
+msgstr "Tous les fichiers certificats et clés doivent êtres en format PEM [original](Privacy Enhanced Mail)[/original]"
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml125(para)
+msgid "private key files must not be protected by a password"
+msgstr "Les fichiers de clés privées ne doivent pas être protégés par un mot de passe"
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml129(para)
+msgid ""
+"When using signing certificate issued by an external CA, you do not need to "
+"specify <literal>key_size</literal>, <literal>valid_days</literal>, and "
+"<literal>ca_password</literal> as they will be ignored."
+msgstr "Lorsque l'on utilise un certificat de signature émis pas une CA externe, il n'y a pas besoin de spécifier <literal>key_size</literal>, <literal>valid_days</literal>, et <literal>ca_password</literal>, puisqu'il seront ignorés."
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml134(para)
+msgid ""
+"The basic workflow for using a signing certificate issued by an external CA "
+"involves:"
+msgstr "Le flux de travail basique lorsqu'on utilise un certificat de signature émis par une CA externe implique :"
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml138(para)
+msgid "Request Signing Certificate from External CA"
+msgstr "Demander un Certificat de Signature à une CA externe"
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml142(para)
+msgid "Convert certificate and private key to PEM if needed"
+msgstr "Convertir le Certificat et la clé privée en PEM si nécessaire"
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml146(para)
+msgid "Install External Signing Certificate"
+msgstr "Installer le Certificat de Signature Externe"
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml151(title)
+msgid "Request a signing certificate from an external CA"
+msgstr "Demander un Certificat de Signature à une CA externe"
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml153(para)
+msgid ""
+"One way to request a signing certificate from an external CA is to first "
+"generate a PKCS #10 Certificate Request Syntax (CRS) using OpenSSL CLI."
+msgstr "Un façon de demander un certificat de signature à une CA externe est de d'abord générer une Syntaxe pou Requête de Certification (CRS-Certificate  Request  Syntax) en PKCS #10 via OpenSSL CLI. "
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml156(para)
+msgid ""
+"Create a certificate request configuration file. For example, create the "
+"<filename>cert_req.conf</filename> file, as follows:"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml176(para)
+msgid ""
+"Then generate a CRS with OpenSSL CLI. <emphasis role=\"strong\">Do not "
+"encrypt the generated private key. Must use the -nodes option.</emphasis>"
+msgstr "Puis générez une CRS avec OpenSSL CLI. <emphasis role=\"strong\">N'encryptez pas la clé privée générée. Vous devez utiliser l'option -nodes.</emphasis>"
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml183(para)
+msgid ""
+"If everything is successful, you should end up with "
+"<filename>signing_cert_req.pem</filename> and "
+"<filename>signing_key.pem</filename>. Send "
+"<filename>signing_cert_req.pem</filename> to your CA to request a token "
+"signing certificate and make sure to ask the certificate to be in PEM "
+"format. Also, make sure your trusted CA certificate chain is also in PEM "
+"format."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml193(title)
+msgid "Install an external signing certificate"
+msgstr "Installer un Certificat de Signature Externe"
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml194(para)
+msgid "Assuming you have the following already:"
+msgstr "En supposant que vous possédez déjà les suivants :"
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml197(para)
+msgid ""
+"<filename>signing_cert.pem</filename> - (Keystone token) signing certificate"
+" in PEM format"
+msgstr "<filename>signing_cert.pem</filename> – (jeton Keystone) certificat de signature au format PEM "
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml202(para)
+msgid ""
+"<filename>signing_key.pem</filename> - corresponding (non-encrypted) private"
+" key in PEM format"
+msgstr "<filename>signing_key.pem</filename> – Clé privée (non-cryptée) correspondante au format PEM"
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml208(para)
+msgid ""
+"<filename>cacert.pem</filename> - trust CA certificate chain in PEM format"
+msgstr "• <filename>cacert.pem</filename> – Chaîne de certificat de CA de confiance au format PEM"
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml213(para)
+msgid "Copy the above to your certificate directory. For example:"
+msgstr "Copiez ce qui précède dans votre dossier de certificats. Par exemple :"
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml221(para)
+msgid "Make sure the certificate directory is only accessible by root."
+msgstr "Assurez-vous que le dossier de certificats n’est accessible que par root (racine)."
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml224(para)
+msgid ""
+"If your certificate directory path is different from the default "
+"<filename>/etc/keystone/ssl/certs</filename>, make sure it is reflected in "
+"the <literal>[signing]</literal> section of the configuration file."
+msgstr "Si le chemin de votre dossier de certificats diffère du chemin par défaut <filename>/etc/keystone/ssl/certs</filename>, assurez-vous que ce changement soit reflété dans la section <literal>[signing]</literal> du fichier de configuration."
+
+#: ./doc/common/section_cli_nova_get_console.xml6(title)
+msgid "Access an instance through a console"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_get_console.xml7(para)
+msgid ""
+"To access an instance through a VNC console, run the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_get_console.xml9(para)
+msgid "The command returns a URL from which you can access your instance:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_get_console.xml15(para)
+msgid ""
+"To access an instance through a non-VNC console, specify the "
+"<parameter>novnc</parameter> parameter instead of the "
+"<parameter>xvpvnc</parameter> parameter."
+msgstr ""
+
+#: ./doc/common/section_compute_config-firewalls.xml6(title)
+msgid "Compute service node firewall requirements"
+msgstr ""
+
+#: ./doc/common/section_compute_config-firewalls.xml7(para)
+msgid ""
+"Console connections for virtual machines, whether direct or through a proxy,"
+" are received on ports <literal>5900</literal> to <literal>5999</literal>. "
+"You must configure the firewall on each Compute service node to enable "
+"network traffic on these ports."
+msgstr ""
+
+#: ./doc/common/section_compute_config-firewalls.xml11(title)
+msgid "Configure the service-node firewall"
+msgstr ""
+
+#: ./doc/common/section_compute_config-firewalls.xml12(para)
+msgid ""
+"On the server that hosts the Compute service, log in as "
+"<systemitem>root</systemitem>."
+msgstr ""
+
+#: ./doc/common/section_compute_config-firewalls.xml14(para)
+msgid "Edit the <filename>/etc/sysconfig/iptables</filename> file."
+msgstr "Editer le fichier <filename>/etc/sysconfig/iptables</filename>."
+
+#: ./doc/common/section_compute_config-firewalls.xml20(para)
+msgid ""
+"Add an INPUT rule that allows TCP traffic on ports that range from "
+"<literal>5900</literal> to <literal>5999</literal>:"
+msgstr ""
+
+#: ./doc/common/section_compute_config-firewalls.xml26(para)
+msgid "The new rule must appear before any INPUT rules that REJECT traffic."
+msgstr ""
+
+#: ./doc/common/section_compute_config-firewalls.xml32(para)
+msgid ""
+"Save the changes to the <filename>/etc/sysconfig/iptables</filename> file."
+msgstr "Enregistrez les changements au fichier <filename>/etc/sysconfig/iptables</filename>."
+
+#: ./doc/common/section_compute_config-firewalls.xml38(para)
+msgid ""
+"Restart the <systemitem>iptables</systemitem> service to ensure that the "
+"change takes effect."
+msgstr "Redémarrer le service <systemitem>iptables</systemitem> pour être sûr que le changement fasse effet."
+
+#: ./doc/common/section_compute_config-firewalls.xml45(para)
+msgid ""
+"The <systemitem>iptables</systemitem> firewall now enables incoming "
+"connections to the Compute services. Repeat this process for each Compute "
+"service node."
+msgstr ""
+
+#: ./doc/common/section_about-object-storage.xml7(title)
+#: ./doc/common/section_objectstorage-intro.xml7(title)
+msgid "Introduction to Object Storage"
+msgstr "Introduction au Stockage d'Objets"
+
+#: ./doc/common/section_about-object-storage.xml8(para)
+msgid ""
+"Object Storage is a robust, highly scalable and fault tolerant storage "
+"platform for unstructured data such as objects. Objects are stored bits, "
+"accessed through a RESTful, HTTP-based interface. You cannot access data at "
+"the block or file level. Object Storage is commonly used to archive and back"
+" up data, with use cases in virtual machine image, photo, video and music "
+"storage."
+msgstr ""
+
+#: ./doc/common/section_about-object-storage.xml15(para)
+msgid ""
+"Object Storage provides a high degree of availability, throughput, and "
+"performance with its scale out architecture. Each object is replicated "
+"across multiple servers, residing within the same data center or across data"
+" centers, which mitigates the risk of network and hardware failure. In the "
+"event of hardware failure, Object Storage will automatically copy objects to"
+" a new location to ensure that there are always three copies available. "
+"Object Storage is an eventually consistent distributed storage platform; it "
+"sacrifices consistency for maximum availability and partition tolerance. "
+"Object Storage enables you to create a reliable platform by using commodity "
+"hardware and inexpensive storage."
+msgstr ""
+
+#: ./doc/common/section_about-object-storage.xml27(para)
+msgid ""
+"For more information, review the key concepts in the developer documentation"
+" at <link "
+"href=\"http://docs.openstack.org/developer/swift/\">docs.openstack.org/developer/swift/</link>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml10(title)
+msgid "Launch an instance from a volume"
+msgstr "Lancer une instance d'un volume"
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml11(para)
+msgid "You can boot instances from a volume instead of an image."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml12(para)
+msgid ""
+"To complete these tasks, use these parameters on the nova <placeholder-1/> "
+"command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml20(th)
+msgid "Task"
+msgstr "Tâche"
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml21(th)
+msgid "nova boot parameter"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml22(th)
+msgid "See"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml27(td)
+msgid "Boot an instance from an image and attach a non-bootable volume."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml29(parameter)
+#: ./doc/common/section_cli_nova_boot_from_volume.xml35(parameter)
+#: ./doc/common/section_cli_nova_boot_from_volume.xml41(parameter)
+msgid "--block-device"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml33(td)
+msgid "Create a volume from an image and boot an instance from that volume."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml39(td)
+msgid "Boot from an existing source image, volume, or snapshot."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml45(td)
+msgid "Attach a swap disk to an instance."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml47(parameter)
+msgid "--swap"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml51(td)
+msgid "Attach an ephemeral disk to an instance."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml52(parameter)
+msgid "--ephemeral"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml58(para)
+msgid ""
+"To attach a volume to a running instance, see <xref "
+"linkend=\"cli_attach_volume\"/>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml62(title)
+msgid "Boot instance from image and attach non-bootable volume"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml64(para)
+msgid ""
+"Create a non-bootable volume and attach that volume to an instance that you "
+"boot from an image."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml66(para)
+msgid ""
+"To create a non-bootable volume, do not create it from an image. The volume "
+"must be entirely empty with no partition table and no file system."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml71(para)
+msgid "Create a non-bootable volume:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml98(para)
+#: ./doc/common/section_cli_cinder_manage_volumes.xml176(para)
+msgid "List volumes:"
+msgstr "Listez les volumes:"
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml107(para)
+msgid ""
+"Boot an instance from an image and attach the empty volume to the instance:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml149(title)
+msgid "Create volume from image and boot instance"
+msgstr "Créez un volume depuis une image et démarrer une instance."
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml150(para)
+msgid ""
+"You can create a volume from an existing image, volume, or snapshot. This "
+"procedure shows you how to create a volume from an image, and use the volume"
+" to boot an instance."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml165(para)
+msgid "Note the ID of the image that you want to use to create a volume."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml183(para)
+msgid "Note the ID of the flavor that you want to use to create a volume."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml187(para)
+msgid ""
+"To create a bootable volume from an image and launch an instance from this "
+"volume, use the <parameter>--block-device</parameter> parameter."
+msgstr "Pour créer un volume démarrable depuis une image et pour lancer une instance depuis ce volume, utilisez le paramètre <parameter>--block-device</parameter>."
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
+#: ./doc/common/section_cli_nova_boot_from_volume.xml329(replaceable)
+msgid "FLAVOR"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
+#: ./doc/common/section_cli_nova_boot_from_volume.xml205(replaceable)
+msgid "SOURCE"
+msgstr "SOURCE"
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
+#: ./doc/common/section_cli_nova_boot_from_volume.xml217(replaceable)
+msgid "ID"
+msgstr "ID"
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
+#: ./doc/common/section_cli_nova_boot_from_volume.xml224(replaceable)
+msgid "DEST"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
+#: ./doc/common/section_cli_nova_boot_from_volume.xml233(replaceable)
+msgid "SIZE"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
+msgid "PRESERVE"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
+#: ./doc/common/section_cli_nova_boot_from_volume.xml250(replaceable)
+msgid "INDEX"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
+#: ./doc/common/section_cli_nova_boot_from_volume.xml329(replaceable)
+msgid "NAME"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml192(para)
+msgid "The parameters are:"
+msgstr "Les paramètres sont:"
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml195(para)
+msgid ""
+"<parameter>--flavor</parameter><replaceable>FLAVOR</replaceable>. The flavor"
+" ID or name."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml200(para)
+msgid ""
+"<parameter>--block-device</parameter> "
+"source=<replaceable>SOURCE</replaceable>,id=<replaceable>ID</replaceable>,dest=<replaceable>DEST</replaceable>,size=<replaceable>SIZE</replaceable>,shutdown=<replaceable>PRESERVE</replaceable>,bootindex=<replaceable>INDEX</replaceable>"
+msgstr "<parameter>--block-device</parameter> source=<replaceable>SOURCE</replaceable>,id=<replaceable>ID</replaceable>,dest=<replaceable>DEST</replaceable>,size=<replaceable>SIZE</replaceable>,shutdown=<replaceable>PRESERVE</replaceable>,bootindex=<replaceable>INDEX</replaceable>"
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml205(emphasis)
+msgid "source=<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml207(para)
+msgid ""
+"The type of object used to create the block device. Valid values are "
+"<literal>volume</literal>, <literal>snapshot</literal>, "
+"<literal>image</literal>, and <literal>blank</literal>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml217(emphasis)
+msgid "id=<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml219(para)
+msgid "The ID of the source object."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml224(emphasis)
+msgid "dest=<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml226(para)
+msgid ""
+"The type of the target virtual device. Valid values are "
+"<literal>volume</literal> and <literal>local</literal>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml233(emphasis)
+msgid "size=<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml235(para)
+msgid "The size of the volume that is created."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml240(emphasis)
+msgid "shutdown={preserve|remove}"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml242(para)
+msgid ""
+"What to do with the volume when the instance is deleted. "
+"<literal>preserve</literal> does not delete the volume. "
+"<literal>remove</literal> deletes the volume."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml250(emphasis)
+msgid "bootindex=<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml252(para)
+msgid ""
+"Orders the boot disks. Use <literal>0</literal> to boot from this volume."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml260(para)
+msgid "<replaceable>NAME</replaceable>. The name for the server."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml266(para)
+msgid ""
+"Create a bootable volume from an image, before the instance boots. The "
+"volume is not deleted when the instance is terminated:"
+msgstr "Créez un volume démarrable depuis une image avant le lancement de l'instance. Le volume n'est pas supprimé quand l'instance est terminée:"
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml307(para)
+msgid ""
+"List volumes to see the bootable volume and its attached "
+"<literal>myInstanceFromVolume</literal> instance:"
+msgstr "Listez les volumes pour voir l'instance démarrable et son instance <literal>myInstanceFromVolume</literal> jointe:"
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml320(title)
+msgid "Attach swap or ephemeral disk to an instance"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml321(para)
+msgid ""
+"Use the nova <placeholder-1/><parameter>--swap</parameter> parameter to "
+"attach a swap disk on boot or the nova "
+"<placeholder-2/><parameter>--ephemeral</parameter> parameter to attach an "
+"ephemeral disk on boot. When you terminate the instance, both disks are "
+"deleted."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml327(para)
+msgid "Boot an instance with a 512MB swap disk and 2GB ephemeral disk:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml331(para)
+msgid ""
+"The flavor defines the maximum swap and ephemeral disk size. You cannot "
+"exceed these maximum values."
+msgstr ""
+
+#: ./doc/common/section_xapi-resize-setup.xml7(title)
+msgid "Modify Dom0 for resize/migration support"
+msgstr ""
+
+#: ./doc/common/section_xapi-resize-setup.xml8(para)
+msgid "To resize servers with XenServer and XCP, you must:"
+msgstr "Afin d'obtenir la redimmension dans le but de travailler avec XenServer (et XCP), il faut:"
+
+#: ./doc/common/section_xapi-resize-setup.xml11(para)
+msgid ""
+"Establish a root trust between all hypervisor nodes of your deployment:"
+msgstr "Etablir une sécurité entre tous les noeuds de l''hyperviseur de votre développement:"
+
+#: ./doc/common/section_xapi-resize-setup.xml13(para)
+msgid ""
+"To do so, generate an ssh key-pair with the <placeholder-1/> command. Ensure"
+" that each of your dom0's <filename>authorized_keys</filename> file (located"
+" in <filename>/root/.ssh/authorized_keys</filename>) contains the public key"
+" fingerprint (located in <filename>/root/.ssh/id_rsa.pub</filename>)."
+msgstr "Pour se faire, il vous faut générer une paire de clés ssh (avec <placeholder-1/>), et vérifier ensuite que que chaque dossier dom0 <filename>authorized_keys</filename> file (located in <filename>/root/.ssh/authorized_keys</filename> (se trouvant dans /root/.ssh/ authorized_keys) contient l'empreinte de la clé publique (se trouvant dans <filename>/root/.ssh/id_rsa.pub</filename>)"
+
+#: ./doc/common/section_xapi-resize-setup.xml22(para)
+msgid ""
+"Provide an <filename>/images</filename> mount point to the dom0 for your "
+"hypervisor:"
+msgstr "Fournir un point de montage <filename>/images</filename> à l'hyperviseur de dom0:"
+
+#: ./doc/common/section_xapi-resize-setup.xml24(para)
+msgid ""
+"Dom0 space is at a premium so creating a directory in dom0 is potentially "
+"dangerous and likely to fail especially when you resize large servers. The "
+"least you can do is to symlink <filename>/images</filename> to your local "
+"storage SR. The following instructions work for an English-based "
+"installation of XenServer (and XCP) and in the case of ext3-based SR (with "
+"which the resize functionality is known to work correctly)."
+msgstr "L'espace Dom0 est un espace premium, il est donc risqué de créer un répertoire dans dom0. Cette entreprise échouera, en particulier au moment de redimensionner les gros serveurs. Il est néanmoins possible de lier symboliquement les <filename>/images</filename> dans vos stockages locaux SR.  Les instructions ci-dessous s'appliquent à une installation basée sur l'anglais de XenServer (et XCP), ainsi que dans le cas d'un SR basé sur ext3 (avec lequel la fonctionnalité de redimensionnement est connu pour fonctionner correctement)"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_dashboard_access.xml89(None)
+msgid ""
+"@@image: 'figures/dashboard-project-tab.png'; "
+"md5=5b192a3d34c9285dbacd875395b8e4cc"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_dashboard_access.xml214(None)
+msgid ""
+"@@image: 'figures/dashboard-admin-tab.png'; "
+"md5=039358c76c549d7d423da5b8aa826435"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml12(title)
+msgid "Log in to the dashboard"
+msgstr "Connectez-vous au tableau de bord"
+
+#: ./doc/common/section_dashboard_access.xml13(para)
+msgid ""
+"The dashboard is available on the node with the <literal>nova-"
+"dashboard</literal> server role."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml17(para)
+msgid ""
+"Ask the cloud operator for the host name or public IP address from which you"
+" can access the dashboard, and for your user name and password."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml22(para)
+msgid "Open a web browser that has JavaScript and cookies enabled."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml25(para)
+msgid ""
+"To use the Virtual Network Computing (VNC) client for the dashboard, your "
+"browser must support HTML5 Canvas and HTML5 WebSockets. The VNC client is "
+"based on noVNC. For details, see <link "
+"href=\"https://github.com/kanaka/noVNC/blob/master/README.md\">noVNC: HTML5 "
+"VNC Client</link>. For a list of supported browsers, see <link "
+"href=\"https://github.com/kanaka/noVNC/wiki/Browser-support\">Browser "
+"support</link>."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml38(para)
+msgid ""
+"In the address bar, enter the host name or IP address for the dashboard."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml40(replaceable)
+msgid "ipAddressOrHostName"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml42(para)
+msgid ""
+"If a certificate warning appears when you try to access the URL for the "
+"first time, a self-signed certificate is in use, which is not considered "
+"trustworthy by default. Verify the certificate or add an exception in the "
+"browser to bypass the warning."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml51(para)
+msgid ""
+"On the <guilabel>Log In</guilabel> page, enter your user name and password, "
+"and click <guibutton>Sign In</guibutton>."
+msgstr "Au page <guilabel>Log In</guilabel>, entrez votre nom d'utilisateur et mot de passe, et cliquez sur <guibutton>Sign In</guibutton>."
+
+#: ./doc/common/section_dashboard_access.xml54(para)
+msgid ""
+"The top of the window displays your user name. You can also access "
+"<guilabel>Settings</guilabel> or sign out of the dashboard."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml61(para)
+msgid ""
+"If you are logged in as an end user, the <link "
+"linkend=\"dashboard_project_tab\">Project</link> tab is displayed."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml65(para)
+msgid ""
+"If you are logged in as an administrator, the <link "
+"linkend=\"dashboard_project_tab\">Project</link> tab and <link "
+"linkend=\"dashboard_admin_tab\">Admin</link> tab are displayed."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml57(para)
+msgid ""
+"The visible tabs and functions in the dashboard depend on the access "
+"permissions, or <emphasis role=\"italic\">roles</emphasis>, of the user you "
+"are logged in as.<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml75(title)
+msgid "OpenStack dashboardProject tab"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml76(para)
+msgid ""
+"Projects are organizational units in the cloud, and are also known as "
+"tenants or accounts. Each user is a member of one or more projects. Within a"
+" project, a user creates and manages instances."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml80(para)
+msgid ""
+"From the <guilabel>Project</guilabel> tab, you can view and manage the "
+"resources in a selected project, including instances and images. You select "
+"the project from the <guilabel>CURRENT PROJECT</guilabel> list at the top of"
+" the tab."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml85(title)
+msgid "Project tab"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml93(para)
+msgid ""
+"From the <guilabel>Project</guilabel> tab, you can access the following "
+"tabs:"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml100(th)
+#: ./doc/common/section_dashboard_access.xml170(th)
+#: ./doc/common/section_dashboard_access.xml185(th)
+#: ./doc/common/section_dashboard_access.xml192(th)
+#: ./doc/common/section_dashboard_access.xml224(th)
+#: ./doc/common/section_dashboard_access.xml350(th)
+msgid "<placeholder-1/> tab"
+msgstr "<placeholder-1/> tab"
+
+#: ./doc/common/section_dashboard_access.xml106(para)
+msgid "View reports for the project."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml109(guilabel)
+#: ./doc/common/section_dashboard_access.xml292(guilabel)
+msgid "Instances"
+msgstr "Instances"
+
+#: ./doc/common/section_dashboard_access.xml110(para)
+msgid ""
+"View, launch, create a snapshot from, stop, pause, or reboot instances, or "
+"connect to them through VNC."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml114(guilabel)
+#: ./doc/common/section_dashboard_access.xml119(guilabel)
+#: ./doc/common/section_dashboard_access.xml299(guilabel)
+msgid "Volumes"
+msgstr "Volumes"
+
+#: ./doc/common/section_dashboard_access.xml115(para)
+#: ./doc/common/section_dashboard_access.xml141(para)
+msgid "Use the following tabs to complete these tasks:"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml121(para)
+msgid "View, create, edit, and delete volumes."
+msgstr "Voir, créer, éditer et supprimer des columes."
+
+#: ./doc/common/section_dashboard_access.xml125(guilabel)
+msgid "Volume Snapshots"
+msgstr "Instantanés du volume"
+
+#: ./doc/common/section_dashboard_access.xml127(para)
+msgid "View, create, edit, and delete volume snapshots."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml133(guilabel)
+#: ./doc/common/section_dashboard_access.xml309(guilabel)
+msgid "Images"
+msgstr "Images"
+
+#: ./doc/common/section_dashboard_access.xml134(para)
+msgid ""
+"View images and instance snapshots created by project users, plus any images"
+" that are publicly available. Create, edit, and delete images, and launch "
+"instances from images and snapshots."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml140(guilabel)
+msgid "Access &amp; Security"
+msgstr "Accès et Sécurité"
+
+#: ./doc/common/section_dashboard_access.xml144(guilabel)
+msgid "Security Groups"
+msgstr "Groupes de sécurité"
+
+#: ./doc/common/section_dashboard_access.xml145(para)
+msgid ""
+"View, create, edit, and delete security groups and security group rules."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml150(guilabel)
+msgid "Key Pairs"
+msgstr "Paires de Clefs"
+
+#: ./doc/common/section_dashboard_access.xml151(para)
+msgid "View, create, edit, import, and delete key pairs."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml156(guilabel)
+msgid "Floating IPs"
+msgstr "IP flottantes"
+
+#: ./doc/common/section_dashboard_access.xml158(para)
+msgid "Allocate an IP address to or release it from a project."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml163(guilabel)
+msgid "API Access"
+msgstr "Accès API"
+
+#: ./doc/common/section_dashboard_access.xml164(para)
+msgid "View API endpoints."
+msgstr "Voir des points de terminaison d'API."
+
+#: ./doc/common/section_dashboard_access.xml170(guilabel)
+msgid "Network"
+msgstr "Réseau"
+
+#: ./doc/common/section_dashboard_access.xml173(guilabel)
+msgid "Network Topology"
+msgstr "Topologie du Réseau"
+
+#: ./doc/common/section_dashboard_access.xml174(para)
+msgid "View the network topology."
+msgstr "Voir la topologie du réseau"
+
+#: ./doc/common/section_dashboard_access.xml177(guilabel)
+#: ./doc/common/section_dashboard_access.xml314(guilabel)
+msgid "Networks"
+msgstr "Réseaux"
+
+#: ./doc/common/section_dashboard_access.xml178(para)
+msgid "Create and manage public and private networks."
+msgstr "Créer et gérer les réseaux publics et privés."
+
+#: ./doc/common/section_dashboard_access.xml181(guilabel)
+#: ./doc/common/section_dashboard_access.xml318(guilabel)
+msgid "Routers"
+msgstr "Routeurs"
+
+#: ./doc/common/section_dashboard_access.xml182(para)
+msgid "Create and manage subnets."
+msgstr "Créez et gérez des sous-réseaux."
+
+#: ./doc/common/section_dashboard_access.xml185(guilabel)
+msgid "Object Store"
+msgstr "Stockage d'objet"
+
+#: ./doc/common/section_dashboard_access.xml188(guilabel)
+#: ./doc/common/section_dashboard_access.xml195(guilabel)
+msgid "Containers"
+msgstr "Conteneurs"
+
+#: ./doc/common/section_dashboard_access.xml189(para)
+msgid "Create and manage containers and objects."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml196(para)
+msgid "Use the REST API to orchestrate multiple composite cloud applications."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml203(title)
+msgid "OpenStack dashboardAdmin tab"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml204(para)
+msgid ""
+"Administrative users can use the <guilabel>Admin</guilabel> tab to view "
+"usage and to manage instances, volumes, flavors, images, projects, users, "
+"services, and quotas."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml209(title)
+msgid "Admin tab"
+msgstr "Onglet d'administration"
+
+#: ./doc/common/section_dashboard_access.xml218(para)
+msgid "Access the following categories to complete these tasks:"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml224(guilabel)
+msgid "System Panel"
+msgstr "Gestion Système"
+
+#: ./doc/common/section_dashboard_access.xml230(para)
+msgid "View basic reports."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml233(guilabel)
+msgid "Resource Usage"
+msgstr "Usage de ressource"
+
+#: ./doc/common/section_dashboard_access.xml234(para)
+msgid "Use the following tabs to view the following usages:"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml269(guilabel)
+msgid "Daily Report"
+msgstr "Rapport journalier"
+
+#: ./doc/common/section_dashboard_access.xml271(para)
+msgid "View the daily report."
+msgstr "Voir la rapport journalier."
+
+#: ./doc/common/section_dashboard_access.xml275(guilabel)
+msgid "Stats"
+msgstr "Stats"
+
+#: ./doc/common/section_dashboard_access.xml277(para)
+msgid "View the statistics of all resources."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml283(guilabel)
+msgid "Hypervisors"
+msgstr "Hyperviseurs"
+
+#: ./doc/common/section_dashboard_access.xml284(para)
+msgid "View the hypervisor summary."
+msgstr "Voir le résumé d'hyperviseur."
+
+#: ./doc/common/section_dashboard_access.xml287(guilabel)
+msgid "Host Aggregates"
+msgstr "Agrégations d'hôte."
+
+#: ./doc/common/section_dashboard_access.xml288(para)
+msgid ""
+"View, create, and edit host aggregates. View the list of availability zones."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml293(para)
+msgid ""
+"View, pause, resume, suspend, migrate, soft or hard reboot, and delete "
+"running instances that belong to users of some, but not all, projects. Also,"
+" view the log for an instance or access an instance through VNC."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml300(para)
+msgid "View, create, edit, and delete volumes and volume types."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml305(para)
+msgid ""
+"View, create, edit, view extra specifications for, and delete flavors. A "
+"flavor is size of an instance."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml310(para)
+msgid "View, create, edit properties for, and delete custom images."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml315(para)
+msgid "View, create, edit properties for, and delete networks."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml319(para)
+msgid "View, create, edit properties for, and delete routers."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml322(guilabel)
+msgid "System Info"
+msgstr "Informations Système"
+
+#: ./doc/common/section_dashboard_access.xml323(para)
+msgid "Use the following tabs to view the service information:"
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml326(guilabel)
+msgid "Services"
+msgstr "Services"
+
+#: ./doc/common/section_dashboard_access.xml327(para)
+msgid "View a list of the services."
+msgstr "Voir une liste de toutes les services."
+
+#: ./doc/common/section_dashboard_access.xml331(guilabel)
+msgid "Compute Services"
+msgstr "Services de calcul"
+
+#: ./doc/common/section_dashboard_access.xml332(para)
+msgid "View a list of all Compute services."
+msgstr "Voir une liste de toutes les services calcul."
+
+#: ./doc/common/section_dashboard_access.xml336(guilabel)
+msgid "Network Agents"
+msgstr "Agents réseau."
+
+#: ./doc/common/section_dashboard_access.xml337(para)
+msgid "View the network agents."
+msgstr "Voir les agents réseau."
+
+#: ./doc/common/section_dashboard_access.xml341(guilabel)
+msgid "Default Quotas"
+msgstr "Quotas par défaut"
+
+#: ./doc/common/section_dashboard_access.xml342(para)
+msgid ""
+"View default quota values. Quotas are hard-coded in OpenStack Compute and "
+"define the maximum allowable size and number of resources."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml350(guilabel)
+msgid "Identity Panel"
+msgstr "Gestion des Identités"
+
+#: ./doc/common/section_dashboard_access.xml358(guilabel)
+msgid "Projects"
+msgstr "Projets"
+
+#: ./doc/common/section_dashboard_access.xml359(para)
+msgid "View, create, assign users to, remove users from, and delete projects."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml363(guilabel)
+msgid "Users"
+msgstr "Utilisateurs"
+
+#: ./doc/common/section_dashboard_access.xml364(para)
+msgid "View, create, enable, disable, and delete users."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml6(title)
+msgid "Show usage statistics for hosts and instances"
+msgstr "Afficher les statistiques d'utilisation des hôtes et des instances"
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml7(para)
+msgid ""
+"You can show basic statistics on resource usage for hosts and instances."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml10(para)
+msgid ""
+"For more sophisticated monitoring, see the <link "
+"href=\"https://launchpad.net/ceilometer\">ceilometer</link> project. You can"
+" also use tools, such as <link href=\"http://ganglia.info/\">Ganglia</link> "
+"or <link href=\"http://graphite.wikidot.com/\">Graphite</link>, to gather "
+"more detailed data."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml20(title)
+msgid "Show host usage statistics"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml21(para)
+msgid ""
+"The following examples show the host usage statistics for a host called "
+"<filename>devstack</filename>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml25(para)
+msgid "List the hosts and the nova-related services that run on them:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml37(para)
+msgid ""
+"Get a summary of resource usage of all of the instances running on the host:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml49(para)
+msgid ""
+"The <literal>cpu</literal> column shows the sum of the virtual CPUs for "
+"instances running on the host."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml51(para)
+msgid ""
+"The <literal>memory_mb</literal> column shows the sum of the memory (in MB) "
+"allocated to the instances that run on the host."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml54(para)
+msgid ""
+"The <literal>disk_gb</literal> column shows the sum of the root and "
+"ephemeral disk sizes (in GB) of the instances that run on the host."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml57(para)
+msgid ""
+"The row that has the value <literal>used_now</literal> in the "
+"<literal>PROJECT</literal> column shows the sum of the resources allocated "
+"to the instances that run on the host, plus the resources allocated to the "
+"virtual machine of the host itself."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml62(para)
+msgid ""
+"The row that has the value <literal>used_max</literal> row in the "
+"<literal>PROJECT</literal> column shows the sum of the resources allocated "
+"to the instances that run on the host."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml68(para)
+msgid ""
+"These values are computed by using information about the flavors of the "
+"instances that run on the hosts. This command does not query the CPU usage, "
+"memory usage, or hard disk usage of the physical host."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml75(title)
+msgid "Show instance usage statistics"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml77(para)
+msgid "Get CPU, memory, I/O, and network statistics for an instance."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml79(para)
+msgid "List instances:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml87(para)
+msgid "Get diagnostic statistics:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml108(para)
+msgid "Get summary statistics for each tenant:"
+msgstr "obtenir des statistiques sommaires pour chaque [original]tenant[/original] :"
+
 #: ./doc/common/section_cli_openrc.xml7(title)
 msgid "Set environment variables using the OpenStack RC file"
 msgstr ""
@@ -23872,159 +20375,2670 @@ msgstr "MOT DE PASSE"
 msgid "Where <replaceable>PASSWORD</replaceable> is your password."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml5(title)
-msgid "Manage bare-metal nodes"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_baremetal.xml6(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-components.xml43(None)
 msgid ""
-"The bare-metal driver for OpenStack Compute manages provisioning of physical"
-" hardware by using common cloud APIs and tools such as Orchestration (Heat)."
-" The use case for this driver is for single tenant clouds such as a high-"
-"performance computing cluster or for deploying OpenStack itself."
+"@@image: '../common/figures/objectstorage-buildingblocks.png'; "
+"md5=ed79466c8464513dbeaf1e0954280e5e"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml10(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-components.xml86(None)
 msgid ""
-"If you use the bare-metal driver, you must create a network interface and "
-"add it to a bare-metal node. Then, you can launch an instance from a bare-"
-"metal image."
+"@@image: '../common/figures/objectstorage-ring.png'; "
+"md5=a94e26734cec6980c3684d9e824eac2d"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml13(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-components.xml126(None)
 msgid ""
-"Development efforts are focused on moving the driver out of the Compute code"
-" base in the Icehouse release."
+"@@image: '../common/figures/objectstorage-zones.png'; "
+"md5=1b1dc0abe6ea0c516f22ce399deb75ed"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml15(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-components.xml144(None)
 msgid ""
-"You can list and delete bare-metal nodes. When you delete a node, any "
-"associated network interfaces are removed. You can list and remove network "
-"interfaces that are associated with a bare-metal node."
+"@@image: '../common/figures/objectstorage-accountscontainers.png'; "
+"md5=4b15e5a202db5bde53c9b369058aeab8"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml19(title)
-msgid "Commands"
-msgstr "Commandes"
-
-#: ./doc/common/section_cli_nova_baremetal.xml20(para)
-msgid "The following commands can be used to manage bare-metal nodes."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_baremetal.xml22(para)
-msgid "<placeholder-1/>. Adds a network interface to a bare-metal node."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_baremetal.xml26(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-components.xml169(None)
 msgid ""
-"<placeholder-1/>. Lists network interfaces associated with a bare-metal "
-"node."
+"@@image: '../common/figures/objectstorage-partitions.png'; "
+"md5=2c161c2e92d6fefc8140ec86e79e9492"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml30(para)
-msgid "<placeholder-1/>. Removes a network interface from a bare-metal node."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_baremetal.xml34(para)
-msgid "<placeholder-1/>. Creates a bare-metal node."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_baremetal.xml38(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-components.xml195(None)
 msgid ""
-"<placeholder-1/>. Removes a bare-metal node and any associated interfaces."
+"@@image: '../common/figures/objectstorage-replication.png'; "
+"md5=9d55594d7f445764569ab04d8d4373b2"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml42(para)
-msgid "<placeholder-1/>. Lists available bare-metal nodes."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_baremetal.xml46(para)
-msgid "<placeholder-1/>. Shows information about a bare-metal node."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_baremetal.xml51(title)
-msgid "Create a bare-metal node"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_baremetal.xml52(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-components.xml222(None)
 msgid ""
-"When you create a bare-metal node, your PM address, username, and password "
-"should match those that are configured in your hardware's BIOS/IPMI "
-"configuration."
+"@@image: '../common/figures/objectstorage-usecase.png'; "
+"md5=07480e7175b383171173775fb96d70d7"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml57(para)
+#: ./doc/common/section_objectstorage-components.xml7(title)
+msgid "Components"
+msgstr "Composants "
+
+#: ./doc/common/section_objectstorage-components.xml8(para)
 msgid ""
-"The following example shows the command and results from creating a node "
-"with the PM address <filename>1.2.3.4</filename>, the PM username "
-"<literal>ipmi</literal>, and password <literal>ipmi</literal>."
+"The components that enable Object Storage to deliver high availability, high"
+" durability, and high concurrency are:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml79(title)
-msgid "Add a network interface to the node:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_baremetal.xml80(para)
+#: ./doc/common/section_objectstorage-components.xml12(para)
 msgid ""
-"For each NIC on the node, you must create an interface, specifying the "
-"interface's MAC address."
+"<emphasis role=\"bold\">Proxy servers.</emphasis> Handle all of the incoming"
+" API requests."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml92(title)
-msgid "Launch an instance from a bare-metal image:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_baremetal.xml94(para)
+#: ./doc/common/section_objectstorage-components.xml16(para)
 msgid ""
-"A bare-metal instance is an instance created directly on a physical machine "
-"without any virtualization layer running underneath it. Nova retains power "
-"control via IPMI. In some situations, Nova may retain network control via "
-"Neutron and OpenFlow."
+"<emphasis role=\"bold\">Rings.</emphasis> Map logical names of data to "
+"locations on particular disks."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml107(para)
+#: ./doc/common/section_objectstorage-components.xml20(para)
 msgid ""
-"Set the <parameter>--availability_zone</parameter> parameter to specify "
-"which zone or node to use to start the server. Separate the zone from the "
-"host name with a comma. For example:"
+"<emphasis role=\"bold\">Zones.</emphasis> Isolate data from other zones. A "
+"failure in one zone doesn’t impact the rest of the cluster because data is "
+"replicated across zones."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml110(replaceable)
-msgid "HOST"
-msgstr "HOST"
-
-#: ./doc/common/section_cli_nova_baremetal.xml110(replaceable)
-msgid "NODE"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_baremetal.xml111(para)
+#: ./doc/common/section_objectstorage-components.xml25(para)
 msgid ""
-"<literal>host</literal> is optional for the "
-"<literal>--availability_zone</literal> parameter. You can specify simply "
-"<literal>zone:,node</literal>. You must still use the comma."
+"<emphasis role=\"bold\">Accounts and containers.</emphasis> Each account and"
+" container are individual databases that are distributed across the cluster."
+" An account database contains the list of containers in that account. A "
+"container database contains the list of objects in that container."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml118(title)
-msgid "List bare-metal nodes and interfaces:"
+#: ./doc/common/section_objectstorage-components.xml31(para)
+msgid "<emphasis role=\"bold\">Objects.</emphasis> The data itself."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml120(para)
+#: ./doc/common/section_objectstorage-components.xml34(para)
 msgid ""
-"Use the <placeholder-1/> command to view all bare-metal nodes and "
-"interfaces. When a node is in use, its status includes the UUID of the "
-"instance that runs on it:"
+"<emphasis role=\"bold\">Partitions.</emphasis> A partition stores objects, "
+"account databases, and container databases and helps manage locations where "
+"data lives in the cluster."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml130(title)
-msgid "Show details for a bare-metal node:"
+#: ./doc/common/section_objectstorage-components.xml40(title)
+msgid "Object Storage building blocks"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml131(para)
+#: ./doc/common/section_objectstorage-components.xml48(title)
+msgid "Proxy servers"
+msgstr "Serveurs proxy"
+
+#: ./doc/common/section_objectstorage-components.xml49(para)
 msgid ""
-"Use the <placeholder-1/> command to view the details for a bare-metal node."
+"Proxy servers are the public face of Object Storage and handle all of the "
+"incoming API requests. Once a proxy server receives a request, it determines"
+" the storage node based on the object's URL, for example, "
+"https://swift.example.com/v1/account/container/object. Proxy servers also "
+"coordinate responses, handle failures, and coordinate timestamps."
+msgstr "Les serveurs proxy sont la face publique de l'Object Storage et gèrent toutes les requêtes de l'API entrantes. Une fois qu'un serveur proxy reçoit une requête, il détermine le nœud de stockage basée sur l'URL de l'objet, par exemple, https://swift.example.com/v1/account/container/object. Les serveurs proxy coordonnent également les réponses, gèrent les échecs, et coordonnent les horodateurs."
+
+#: ./doc/common/section_objectstorage-components.xml54(para)
+msgid ""
+"Proxy servers use a shared-nothing architecture and can be scaled as needed "
+"based on projected workloads. A minimum of two proxy servers should be "
+"deployed for redundancy. If one proxy server fails, the others take over."
 msgstr ""
 
+#: ./doc/common/section_objectstorage-components.xml59(title)
+msgid "Rings"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml60(para)
+msgid ""
+"A ring represents a mapping between the names of entities stored on disk and"
+" their physical locations. There are separate rings for accounts, "
+"containers, and objects. When other components need to perform any operation"
+" on an object, container, or account, they need to interact with the "
+"appropriate ring to determine their location in the cluster."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml65(para)
+msgid ""
+"The ring maintains this mapping using zones, devices, partitions, and "
+"replicas. Each partition in the ring is replicated, by default, three times "
+"across the cluster, and partition locations are stored in the mapping "
+"maintained by the ring. The ring is also responsible for determining which "
+"devices are used for handoff in failure scenarios."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml70(para)
+msgid ""
+"Data can be isolated into zones in the ring. Each partition replica is "
+"guaranteed to reside in a different zone. A zone could represent a drive, a "
+"server, a cabinet, a switch, or even a data center."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml73(para)
+msgid ""
+"The partitions of the ring are equally divided among all of the devices in "
+"the Object Storage installation. When partitions need to be moved around "
+"(for example, if a device is added to the cluster), the ring ensures that a "
+"minimum number of partitions are moved at a time, and only one replica of a "
+"partition is moved at a time."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml77(para)
+msgid ""
+"Weights can be used to balance the distribution of partitions on drives "
+"across the cluster. This can be useful, for example, when differently sized "
+"drives are used in a cluster."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml80(para)
+msgid ""
+"The ring is used by the proxy server and several background processes (like "
+"replication)."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml83(title)
+msgid "The <emphasis role=\"bold\">ring</emphasis>"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml90(para)
+msgid ""
+"These rings are externally managed, in that the server processes themselves "
+"do not modify the rings, they are instead given new rings modified by other "
+"tools."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml92(para)
+msgid ""
+"The ring uses a configurable number of bits from a path’s MD5 hash as a "
+"partition index that designates a device. The number of bits kept from the "
+"hash is known as the partition power, and 2 to the partition power indicates"
+" the partition count. Partitioning the full MD5 hash ring allows other parts"
+" of the cluster to work in batches of items at once which ends up either "
+"more efficient or at least less complex than working with each item "
+"separately or the entire cluster all at once."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml101(para)
+msgid ""
+"Another configurable value is the replica count, which indicates how many of"
+" the partition-device assignments make up a single ring. For a given "
+"partition number, each replica’s device will not be in the same zone as any "
+"other replica's device. Zones can be used to group devices based on physical"
+" locations, power separations, network separations, or any other attribute "
+"that would improve the availability of multiple replicas at the same time."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml109(title)
+#: ./doc/common/section_objectstorage-components.xml123(title)
+msgid "Zones"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml110(para)
+msgid ""
+"Object Storage allows configuring zones in order to isolate failure "
+"boundaries. Each data replica resides in a separate zone, if possible. At "
+"the smallest level, a zone could be a single drive or a grouping of a few "
+"drives. If there were five object storage servers, then each server would "
+"represent its own zone. Larger deployments would have an entire rack (or "
+"multiple racks) of object servers, each representing a zone. The goal of "
+"zones is to allow the cluster to tolerate significant outages of storage "
+"servers without losing all replicas of the data."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml117(para)
+msgid ""
+"As mentioned earlier, everything in Object Storage is stored, by default, "
+"three times. Swift will place each replica \"as-uniquely-as-possible\" to "
+"ensure both high availability and high durability. This means that when "
+"chosing a replica location, Object Storage chooses a server in an unused "
+"zone before an unused server in a zone that already has a replica of the "
+"data."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml130(para)
+msgid ""
+"When a disk fails, replica data is automatically distributed to the other "
+"zones to ensure there are three copies of the data."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml134(title)
+#: ./doc/common/section_objectstorage-components.xml141(title)
+msgid "Accounts and containers"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml135(para)
+msgid ""
+"Each account and container is an individual SQLite database that is "
+"distributed across the cluster. An account database contains the list of "
+"containers in that account. A container database contains the list of "
+"objects in that container."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml148(para)
+msgid ""
+"To keep track of object data locations, each account in the system has a "
+"database that references all of its containers, and each container database "
+"references each object."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml153(title)
+#: ./doc/common/section_objectstorage-components.xml166(title)
+msgid "Partitions"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml154(para)
+msgid ""
+"A partition is a collection of stored data, including account databases, "
+"container databases, and objects. Partitions are core to the replication "
+"system."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml156(para)
+msgid ""
+"Think of a partition as a bin moving throughout a fulfillment center "
+"warehouse. Individual orders get thrown into the bin. The system treats that"
+" bin as a cohesive entity as it moves throughout the system. A bin is easier"
+" to deal with than many little things. It makes for fewer moving parts "
+"throughout the system."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml160(para)
+msgid ""
+"System replicators and object uploads/downloads operate on partitions. As "
+"the system scales up, its behavior continues to be predictable because the "
+"number of partitions is a fixed number."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml163(para)
+msgid ""
+"Implementing a partition is conceptually simple, a partition is just a "
+"directory sitting on a disk with a corresponding hash table of what it "
+"contains."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml175(title)
+msgid "Replicators"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml176(para)
+msgid ""
+"In order to ensure that there are three copies of the data everywhere, "
+"replicators continuously examine each partition. For each local partition, "
+"the replicator compares it against the replicated copies in the other zones "
+"to see if there are any differences."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml180(para)
+msgid ""
+"The replicator knows if replication needs to take place by examining hashes."
+" A hash file is created for each partition, which contains hashes of each "
+"directory in the partition. Each of the three hash files is compared. For a "
+"given partition, the hash files for each of the partition's copies are "
+"compared. If the hashes are different, then it is time to replicate, and the"
+" directory that needs to be replicated is copied over."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml186(para)
+msgid ""
+"This is where partitions come in handy. With fewer things in the system, "
+"larger chunks of data are transferred around (rather than lots of little TCP"
+" connections, which is inefficient) and there is a consistent number of "
+"hashes to compare."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml189(para)
+msgid ""
+"The cluster eventually has a consistent behavior where the newest data has a"
+" priority."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml199(para)
+msgid ""
+"If a zone goes down, one of the nodes containing a replica notices and "
+"proactively copies data to a handoff location."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml203(title)
+msgid "Use cases"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml204(para)
+msgid ""
+"The following sections show use cases for object uploads and downloads and "
+"introduce the components."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml206(title)
+msgid "Upload"
+msgstr "Mettre en ligne"
+
+#: ./doc/common/section_objectstorage-components.xml207(para)
+msgid ""
+"A client uses the REST API to make a HTTP request to PUT an object into an "
+"existing container. The cluster receives the request. First, the system must"
+" figure out where the data is going to go. To do this, the account name, "
+"container name, and object name are all used to determine the partition "
+"where this object should live."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml211(para)
+msgid ""
+"Then a lookup in the ring figures out which storage nodes contain the "
+"partitions in question."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml213(para)
+msgid ""
+"The data is then sent to each storage node where it is placed in the "
+"appropriate partition. At least two of the three writes must be successful "
+"before the client is notified that the upload was successful."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml216(para)
+msgid ""
+"Next, the container database is updated asynchronously to reflect that there"
+" is a new object in it."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml219(title)
+msgid "Object Storage in use"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml228(title)
+msgid "Download"
+msgstr "Télécharger"
+
+#: ./doc/common/section_objectstorage-components.xml229(para)
+msgid ""
+"A request comes in for an account/container/object. Using the same "
+"consistent hashing, the partition name is generated. A lookup in the ring "
+"reveals which storage nodes contain that partition. A request is made to one"
+" of the storage nodes to fetch the object and, if that fails, requests are "
+"made to the other nodes."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml11(title)
+msgid "Manage volumes"
+msgstr "Gérer les volumes"
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml12(para)
+msgid ""
+"A volume is a detachable block storage device, similar to a USB hard drive. "
+"You can attach a volume to only one instance. To create and manage volumes, "
+"you use a combination of <placeholder-1/> and <placeholder-2/> client "
+"commands."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml16(title)
+msgid "Migrate a volume"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml17(para)
+msgid ""
+"As an administrator, you can migrate a volume with its data from one "
+"location to another in a manner that is transparent to users and workloads. "
+"You can migrate only detached volumes with no snapshots."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml21(para)
+msgid "Possible use cases for data migration include:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml24(para)
+msgid ""
+"Bring down a physical storage device for maintenance without disrupting "
+"workloads."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml28(para)
+msgid "Modify the properties of a volume."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml31(para)
+msgid "Free up space in a thinly-provisioned back end."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml35(para)
+msgid ""
+"Migrate a volume with the <placeholder-1/> command, as shown in the "
+"following example:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml36(replaceable)
+#: ./doc/common/section_cli_cinder_manage_volumes.xml274(replaceable)
+msgid "volumeID"
+msgstr "volumeID"
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml36(replaceable)
+msgid "destinationHost"
+msgstr "destinationHost"
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml36(replaceable)
+msgid "True|False"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml37(para)
+msgid ""
+"In this example, <literal>--force-host-copy=True</literal> forces the "
+"generic host-based migration mechanism and bypasses any driver "
+"optimizations."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml40(para)
+msgid ""
+"If the volume is in use or has snapshots, the specified host destination "
+"cannot accept the volume. If the user is not an administrator, the migration"
+" fails."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml45(title)
+msgid "Create a volume"
+msgstr "Créer un volume"
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml46(para)
+msgid "This example creates a my-new-volume volume based on an image."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml49(para)
+msgid ""
+"List images, and note the ID of the image that you want to use for your "
+"volume:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml62(para)
+msgid ""
+"List the availability zones, and note the ID of the availability zone in "
+"which you want to create your volume:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml81(para)
+msgid ""
+"Create a volume with 8GB of space, and specify the availability zone and "
+"image:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml103(para)
+msgid ""
+"To verify that your volume was created successfully, list the available "
+"volumes:"
+msgstr "Pour vérifier que votre volume a été bien créé, listez les volumes disponibles:"
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml112(para)
+msgid ""
+"If your volume was created successfully, its status is "
+"<literal>available</literal>. If its status is <literal>error</literal>, you"
+" might have exceeded your quota."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml120(title)
+msgid "Attach a volume to an instance"
+msgstr "Joindre un volume à l'instance"
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml123(para)
+msgid ""
+"Attach your volume to a server, specifying the server ID and the volume ID:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml133(para)
+msgid "Note the ID of your volume."
+msgstr "Notez l'identité de votre volume."
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml136(para)
+msgid "Show information for your volume:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml138(para)
+msgid ""
+"The output shows that the volume is attached to the server with ID <literal"
+">84c6e57d-a6b1-44b6-81eb-fcb36afd31b5</literal>, is in the nova availability"
+" zone, and is bootable."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml165(title)
+msgid "Resize a volume"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml168(para)
+msgid "To resize your volume, you must first detach it from the server."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml170(para)
+msgid ""
+"To detach the volume from your server, pass the server ID and volume ID to "
+"the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml172(para)
+#: ./doc/common/section_cli_cinder_manage_volumes.xml191(para)
+msgid "The <placeholder-1/> command does not return any output."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml184(para)
+msgid "Note that the volume is now available."
+msgstr "Notez que le volume est maintenant disponible."
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml187(para)
+msgid ""
+"Resize the volume by passing the volume ID and the new size (a value greater"
+" than the old one) as parameters:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml197(title)
+msgid "Delete a volume"
+msgstr "Supprimez un volume"
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml200(para)
+msgid "To delete your volume, you must first detach it from the server."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml202(para)
+msgid ""
+"To detach the volume from your server and check for the list of existing "
+"volumes, see steps 1 and 2 in <xref linkend=\"cli_extend_volumes\"/>."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml206(para)
+msgid "Delete the volume using either the volume name or ID:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml208(para)
+msgid "The delete command does not return any output."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml212(para)
+msgid ""
+"List the volumes again, and note that the status of your volume is "
+"<literal>deleting</literal>:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml222(para)
+msgid ""
+"When the volume is fully deleted, it disappears from the list of volumes:"
+msgstr "Quand le volume a été complètement supprimé, il ne s'affiche plus dans la liste des volumes: "
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml234(title)
+msgid "Transfer a volume"
+msgstr "Transférer un volume"
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml235(para)
+msgid ""
+"You can transfer a volume from one owner to another by using the "
+"<placeholder-1/> commands. The volume donor, or original owner, creates a "
+"transfer request and sends the created transfer ID and authorization key to "
+"the volume recipient. The volume recipient, or new owner, accepts the "
+"transfer by using the ID and key."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml243(para)
+msgid ""
+"The procedure for volume transfer is intended for tenants (both the volume "
+"donor and recipient) within the same cloud."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml245(para)
+msgid "Use cases include:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml248(para)
+msgid ""
+"Create a custom bootable volume or a volume with a large data set and "
+"transfer it to a customer."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml251(para)
+msgid ""
+"For bulk import of data to the cloud, the data ingress system creates a new "
+"Block Storage volume, copies data from the physical device, and transfers "
+"device ownership to the end user."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml258(title)
+msgid "Create a volume transfer request"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml261(para)
+msgid "While logged in as the volume donor, list the available volumes:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml271(para)
+msgid ""
+"As the volume donor, request a volume transfer authorization code for a "
+"specific volume:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml275(para)
+msgid ""
+"The volume must be in an <literal>available</literal> state or the request "
+"will be denied. If the transfer request is valid in the database (that is, "
+"it has not expired or been deleted), the volume is placed in an "
+"<literal>awaiting transfer</literal> state. For example:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml279(para)
+msgid ""
+"The output shows the volume transfer ID in the <literal>id</literal> row and"
+" the authorization key."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml291(para)
+msgid ""
+"Optionally, you can specify a name for the transfer by using the <code"
+">--display-name <replaceable>displayName</replaceable></code> parameter."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml299(para)
+msgid ""
+"Send the volume transfer ID and authorization key to the new owner (for "
+"example, by email)."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml304(para)
+msgid "View pending transfers:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml313(para)
+msgid ""
+"After the volume recipient, or new owner, accepts the transfer, you can see "
+"that the transfer is no longer available:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml325(title)
+msgid "Accept a volume transfer request"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml328(para)
+msgid ""
+"As the volume recipient, you must first obtain the transfer ID and "
+"authorization key from the original owner."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml333(para)
+msgid "Display the transfer request details by using the ID:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml334(replaceable)
+#: ./doc/common/section_cli_cinder_manage_volumes.xml348(replaceable)
+#: ./doc/common/section_cli_cinder_manage_volumes.xml392(replaceable)
+msgid "transferID"
+msgstr "transferID"
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml347(para)
+msgid "Accept the request:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml348(replaceable)
+msgid "authKey"
+msgstr "authKey"
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml359(para)
+msgid ""
+"If you do not have a sufficient quota for the transfer, the transfer is "
+"refused."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml367(title)
+msgid "Delete a volume transfer"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml371(para)
+msgid "List available volumes and their statuses:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml382(para)
+msgid "Find the matching transfer ID:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml391(para)
+msgid "Delete the volume:"
+msgstr "Supprimez le volume:"
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml397(para)
+msgid ""
+"Verify that transfer list is now empty and that the volume is again "
+"available for transfer:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_search_ip.xml7(title)
+msgid "Search for an instance using IP address"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_search_ip.xml8(para)
+msgid ""
+"You can search for an instance using the IP address parameter, "
+"<literal>--ip</literal>, with the <placeholder-1/> command."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_search_ip.xml11(parameter)
+#: ./doc/common/section_cli_nova_search_ip.xml14(parameter)
+msgid "ip"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_search_ip.xml11(replaceable)
+msgid "IP_ADDRESS"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_search_ip.xml12(para)
+msgid ""
+"The following example shows the results of a search on "
+"<filename>10.0.0.4</filename>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_search_ip.xml14(replaceable)
+msgid "10.0.0.4"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml5(title)
+msgid "OpenStack Compute"
+msgstr "OpenStack Compute"
+
+#: ./doc/common/section_getstart_compute.xml6(para)
+msgid ""
+"OpenStack Compute is used to host and manage cloud computing systems and is "
+"a major part of an infrastructure-as-a-service (IaaS) system. The main "
+"modules are implemented in Python."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml9(para)
+msgid ""
+"OpenStack Compute interacts with OpenStack Identity for authentication, "
+"OpenStack Image Service for images, and OpenStack dashboard for the user and"
+" administrative interface. Access to images is limited by project and by "
+"user; quotas are limited per project (for example, the number of instances)."
+" OpenStack Compute can scale horizontally on standard hardware, and download"
+" images to launch instances."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml15(para)
+msgid ""
+"OpenStack Compute consists of the following areas and their components:"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml17(title)
+msgid "API"
+msgstr "API"
+
+#: ./doc/common/section_getstart_compute.xml19(systemitem)
+msgid "nova-api service"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml20(para)
+msgid ""
+"Accepts and responds to end user compute API calls. Supports the OpenStack "
+"Compute API, the Amazon EC2 API, and a special Admin API for privileged "
+"users to perform administrative actions. It enforces some policies and "
+"initiates most orchestration activities, such as running an instance."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml28(term)
+msgid "<systemitem class=\"service\">nova-api-metadata</systemitem> service"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml30(para)
+msgid ""
+"Accepts metadata requests from instances. The <systemitem class=\"service"
+"\">nova-api-metadata</systemitem> service is generally used when you run in "
+"multi-host mode with <systemitem class=\"service\">nova-network</systemitem>"
+" installations. For details, see <link href=\"http://docs.openstack.org"
+"/admin-guide-cloud/content/section_metadata-service.html\">Metadata "
+"service</link> in the <citetitle>Cloud Administrator Guide</citetitle>."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml38(para)
+msgid ""
+"On Debian systems, it is included in the <systemitem class=\"service\">nova-"
+"api</systemitem> package, and can be selected through "
+"<package>debconf</package>."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml44(title)
+msgid "Compute core"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml46(term)
+msgid "<systemitem class=\"service\">nova-compute</systemitem> process"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml47(para)
+msgid ""
+"A worker daemon that creates and terminates virtual machine instances "
+"through hypervisor APIs. For example, XenAPI for XenServer/XCP, libvirt for "
+"KVM or QEMU and VMwareAPI for VMware. Processing is fairly complex but "
+"fundamentally it accepts actions from the queue and performs a series of "
+"system commands, like launching a KVM instance, whilst updating its state in"
+" the database."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml56(term)
+msgid "<systemitem class=\"service\">nova-scheduler</systemitem> process"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml58(para)
+msgid ""
+"Conceptually the simplest piece of code in OpenStack Compute. It takes a "
+"virtual machine instance request from the queue and determines on which "
+"compute server host it will run."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml64(term)
+msgid "<systemitem class=\"service\">nova-conductor</systemitem> module"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml65(para)
+msgid ""
+"Mediates interactions between <systemitem class=\"service\">nova-"
+"compute</systemitem> and the database. It eliminates direct accesses to the "
+"cloud database made by <systemitem class=\"service\">nova-"
+"compute</systemitem>. The <systemitem class=\"service\">nova-"
+"conductor</systemitem> module scales horizontally. However, do not deploy it"
+" on any nodes where <systemitem class=\"service\">nova-compute</systemitem> "
+"runs. For more information, see <link "
+"href=\"http://russellbryantnet.wordpress.com/2012/11/19/a-new-nova-service-"
+"nova-conductor/\">A new Nova service: nova-conductor</link>."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml79(title)
+msgid "Networking for VMs"
+msgstr "Réseaux pour les machines virtuelles"
+
+#: ./doc/common/section_getstart_compute.xml80(term)
+msgid "<systemitem class=\"service\">nova-network</systemitem> worker daemon"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml82(para)
+msgid ""
+"Similar to <systemitem class=\"service\">nova-compute</systemitem>, it "
+"accepts networking tasks from the queue and performs tasks to manipulate the"
+" network, such as setting up bridging interfaces or changing iptables rules."
+" This functionality is being migrated to OpenStack Networking."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml90(term)
+msgid "<systemitem class=\"service\">nova-dhcpbridge</systemitem> script"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml92(para)
+msgid ""
+"The IP address leases and is recorded in the database using the dnsmasq "
+"<literal>dhcp-script</literal> facility. This functionality is being "
+"migrated to OpenStack Networkin which provides a different script."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml99(title)
+msgid "Console interface"
+msgstr "Interface Console"
+
+#: ./doc/common/section_getstart_compute.xml101(term)
+msgid "<systemitem class=\"service\">nova-consoleauth</systemitem> daemon"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml102(para)
+msgid ""
+"Authorizes tokens for users that console proxies provide. See <systemitem "
+"class=\"service\">nova-novncproxy</systemitem> and <systemitem "
+"class=\"service\">nova-xvpnvcproxy</systemitem>. This service must be "
+"running for console proxies to work. Many proxies of either type can be run "
+"against a single <systemitem class=\"service\">nova-consoleauth</systemitem>"
+" service in a cluster configuration. For information, see <link "
+"href=\"http://docs.openstack.org/trunk/config-reference/content/about-nova-"
+"consoleauth.html\">About nova-consoleauth</link>."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml114(term)
+msgid "<systemitem class=\"service\">nova-novncproxy</systemitem> daemon"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml116(para)
+msgid ""
+"Provides a proxy for accessing running instances through a VNC connection. "
+"Supports browser-based novnc clients."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml121(term)
+msgid "<systemitem class=\"service\">nova-xvpnvncproxy</systemitem> daemon"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml123(para)
+msgid ""
+"A proxy for accessing running instances through a VNC connection. It "
+"supports a Java client specifically designed for OpenStack."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml128(term)
+msgid "<systemitem class=\"service\">nova-cert</systemitem> daemon"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml129(para)
+msgid "x509 certificates."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml132(para)
+msgid ""
+"In Debian, a unique <package>nova-consoleproxy</package> package provides "
+"the <package>nova-novncproxy</package>, <package>nova-"
+"spicehtml5proxy</package>, and <package>nova-xvpvncproxy</package> packages."
+" To select packages, edit the <filename>/etc/default/nova-"
+"consoleproxy</filename> file or use the <package>debconf</package> "
+"interface. You can also manually edit the <filename>/etc/default/nova-"
+"consoleproxy</filename> file, and stop and start the console daemons."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml142(title)
+msgid "Image management (EC2 scenario)"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml144(term)
+msgid "<systemitem class=\"service\">nova-objectstore</systemitem> daemon"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml145(para)
+msgid ""
+"A S3 interface for registering images with the OpenStack Image Service. It "
+"is mainly used for installations that must support euca2ools. The euca2ools "
+"tools talk to <systemitem class=\"service\">nova-objectstore</systemitem> in"
+" <emphasis role=\"italic\">S3 language</emphasis>, and <systemitem "
+"class=\"service\">nova-objectstore</systemitem> translates S3 requests into "
+"Image service requests."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml154(term)
+msgid "euca2ools client"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml155(para)
+msgid ""
+"A set of command-line interpreter commands for managing cloud resources. "
+"Although it is not an OpenStack module, you can configure <systemitem "
+"class=\"service\">nova-api</systemitem> to support this EC2 interface. For "
+"more information, see the <link "
+"href=\"https://www.eucalyptus.com/docs/eucalyptus/3.4/index.html\">Eucalyptus"
+" 3.4 Documentation</link>."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml163(title)
+msgid "Command-line clients and other interfaces"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml164(term)
+msgid "nova client"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml165(para)
+msgid "Allows users to submit commands as a tenant administrator or end user."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml169(term)
+msgid "nova-manage client"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml170(para)
+msgid "Enables cloud administrators to submit commands."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml174(title)
+msgid "Other components"
+msgstr "Autres Composants"
+
+#: ./doc/common/section_getstart_compute.xml175(term)
+msgid "The queue"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml175(para)
+msgid ""
+"A central hub for passing messages between daemons. It is usually "
+"implemented with <link href=\"http://www.rabbitmq.com/\">RabbitMQ</link>, "
+"but could be any AMQP message queue, such as <link "
+"href=\"http://qpid.apache.org/\">Apache Qpid</link> or <link "
+"href=\"http://www.zeromq.org/\">Zero MQ</link>."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml183(term)
+msgid "SQL database"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml184(para)
+msgid ""
+"Stores most build-time and runtime states for a cloud infrastructure. It "
+"includes instance types that are available for use, instances in use, "
+"available networks, and projects. Theoretically, OpenStack Compute can "
+"support any database that is supported by SQL-Alchemy. Note the databases "
+"which are widely used are SQLite3 databases (for test and development work),"
+" MySQL, and PostgreSQL."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml192(para)
+msgid ""
+"OpenStack Compute interacts with OpenStack Identity for authentication; "
+"OpenStack Image Service for images; and the OpenStack dashboard for a web "
+"interface."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_manage_images.xml6(title)
+msgid "Create an image (nova)"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_manage_images.xml7(para)
+msgid ""
+"You can use the <placeholder-1/> client to take a snapshot of a running "
+"instance to create an image."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_manage_images.xml9(para)
+msgid ""
+"To minimize the potential for data loss and ensure that you create an "
+"accurate image, you should shut down the instance before you take a "
+"snapshot."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_manage_images.xml12(para)
+msgid ""
+"You cannot create a snapshot from an instance that has an attached volume. "
+"Detach the volume, create the image, and remount the volume."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_manage_images.xml18(para)
+msgid ""
+"For more information, see <link href=\"http://docs.openstack.org/trunk"
+"/openstack-ops/content/snapshots.html\">Taking Snapshots</link> in the "
+"<citetitle>OpenStack Operations Guide</citetitle>."
+msgstr "Pour plus d'informations, voir  see <link href=\"http://docs.openstack.org/trunk/openstack-ops/content/snapshots.html\">Taking Snapshots</link> dans <citetitle>OpenStack Operations Guide</citetitle>."
+
+#: ./doc/common/section_cli_nova_manage_images.xml24(para)
+msgid "List instances to get the server name:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_manage_images.xml31(para)
+msgid ""
+"In this example, the server is named <literal>myCirrosServer</literal>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_manage_images.xml33(para)
+msgid ""
+"Use this server to create a snapshot: <placeholder-1/>The command creates a "
+"qemu snapshot and automatically uploads the image to your repository. Only "
+"the tenant that creates the image has access to it."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_manage_images.xml81(para)
+msgid ""
+"To launch an instance from your image, include the image ID and flavor ID, "
+"as in the following example:"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml6(title)
+msgid "Groups"
+msgstr "Groupes"
+
+#: ./doc/common/section_keystone-concepts-group-management.xml7(para)
+msgid ""
+"A group is a collection of users. Administrators can create groups and add "
+"users to them. Then, rather than assign a role to each user individually, "
+"assign a role to the group. Every group is in a domain. Groups were "
+"introduced with the Identity API v3."
+msgstr ""
+
+#. TODO: eventually remove the last sentence, when v3 is
+#.              commonplace
+#: ./doc/common/section_keystone-concepts-group-management.xml14(para)
+msgid "Identity API V3 provides the following group-related operations:"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml18(para)
+msgid "Create a group"
+msgstr "Créez un groupe"
+
+#: ./doc/common/section_keystone-concepts-group-management.xml21(para)
+msgid "Delete a group"
+msgstr "Supprimez un groupe"
+
+#: ./doc/common/section_keystone-concepts-group-management.xml24(para)
+msgid "Update a group (change its name or description)"
+msgstr "Mettre à jour (changer le nom ou la description)"
+
+#: ./doc/common/section_keystone-concepts-group-management.xml28(para)
+msgid "Add a user to a group"
+msgstr "Ajoutez un utilisateur à un groupe"
+
+#: ./doc/common/section_keystone-concepts-group-management.xml31(para)
+msgid "Remove a user from a group"
+msgstr "Supprimez un utilisateur d'un groupe"
+
+#: ./doc/common/section_keystone-concepts-group-management.xml34(para)
+msgid "List group members"
+msgstr "Listez les membres d'un groupe."
+
+#: ./doc/common/section_keystone-concepts-group-management.xml37(para)
+msgid "List groups for a user"
+msgstr "Lister des groupes pour un utilisateur"
+
+#: ./doc/common/section_keystone-concepts-group-management.xml40(para)
+msgid "Assign a role on a tenant to a group"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml43(para)
+msgid "Assign a role on a domain to a group"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml46(para)
+msgid "Query role assignments to groups"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml50(para)
+msgid ""
+"The Identity service server might not allow all operations. For example, if "
+"using the Identity server with the LDAP Identity back end and group updates "
+"are disabled, then a request to create, delete, or update a group fails."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml56(para)
+msgid "Here are a couple of examples:"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml59(para)
+msgid ""
+"Group A is granted Role A on Tenant A. If User A is a member of Group A, "
+"when User A gets a token scoped to Tenant A, the token also includes Role A."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml65(para)
+msgid ""
+"Group B is granted Role B on Domain B. If User B is a member of Domain B, if"
+" User B gets a token scoped to Domain B, the token also includes Role B."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-assignments.xml6(title)
+msgid "Separate role authorization and user authentication"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-assignments.xml7(para)
+msgid ""
+"When you configure the Identity service to use an LDAP back end, you can "
+"split authentication and authorization using the "
+"<emphasis>Assignments</emphasis> feature."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-assignments.xml10(para)
+msgid ""
+"The Assignments feature enables administrators to manage project role "
+"authorization using the Identity service's own SQL database, while still "
+"providing user authentication through the LDAP directory."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-assignments.xml14(para)
+msgid "To configure this:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-assignments.xml16(title)
+msgid ""
+"Separating role authorization and user authentication through Assignments"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-assignments.xml19(para)
+msgid ""
+"Configure the Identity service to authenticate users through the LDAP "
+"driver. To do so, first find the <literal>[identity]</literal> section in "
+"the <filename>/etc/keystone/keystone.conf</filename> configuration file. "
+"Then, set the <literal>driver</literal> configuration key in that section to"
+" <literal>keystone.identity.backends.ldap.Identity</literal>:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-assignments.xml30(para)
+msgid ""
+"Next, enable the Assignment driver. To do so, find the "
+"<literal>[assignment]</literal> section in the "
+"<filename>/etc/keystone/keystone.conf</filename> configuration file. Then, "
+"set the <literal>driver</literal> configuration key in that section to "
+"<literal>keystone.assignment.backends.sql.Assignment</literal>:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-assignments.xml41(para)
+msgid ""
+"On distributions that include <application>openstack-config</application>, "
+"you can configure both drivers by running the following commands instead:"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml7(title)
+msgid "Install the OpenStack command-line clients"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml8(para)
+msgid ""
+"Install the prerequisite software and the Python package for each OpenStack "
+"client."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml11(title)
+msgid "Install the prerequisite software"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml13(para)
+msgid ""
+"Most Linux distributions include packaged versions of the command-line "
+"clients that you can install directly, see <xref "
+"linkend=\"cli_clients_install_packages\"/>."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml17(para)
+msgid ""
+"If you need to install the command-line packages source packages, the "
+"following table lists the software that you need to have to run the command-"
+"line clients, and provides installation instructions as needed."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml24(caption)
+msgid "Prerequisite software"
+msgstr "Logiciels Prérequis"
+
+#: ./doc/common/section_cli_install.xml29(th)
+msgid "Prerequisite"
+msgstr "Prérequis"
+
+#: ./doc/common/section_cli_install.xml36(para)
+msgid "Python 2.6 or later"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml39(para)
+msgid "Currently, the clients do not support Python 3."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml45(para)
+msgid "<package>setuptools</package> package"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml48(para)
+msgid "Installed by default on Mac OS X."
+msgstr "Installé par défaut sur Mac OS X."
+
+#: ./doc/common/section_cli_install.xml49(para)
+msgid ""
+"Many Linux distributions provide packages to make "
+"<package>setuptools</package> easy to install. Search your package manager "
+"for <package>setuptools</package> to find an installation package. If you "
+"cannot find one, download the <package>setuptools</package> package directly"
+" from <link "
+"href=\"http://pypi.python.org/pypi/setuptools\">http://pypi.python.org/pypi/setuptools</link>."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml57(para)
+msgid ""
+"The recommended way to install <package>setuptools</package> on Microsoft "
+"Windows is to follow the documentation provided <link "
+"href=\"https://pypi.python.org/pypi/setuptools#windows\">on the setuptools "
+"website</link>. Another option is to use the unofficial binary installer "
+"maintained by Christoph Gohlke (<link "
+"href=\"http://www.lfd.uci.edu/~gohlke/pythonlibs/#setuptools\">http://www.lfd.uci.edu/~gohlke/pythonlibs/#setuptools</link>)."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml70(package)
+msgid "pip"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml70(td)
+msgid "<placeholder-1/> package"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml72(para)
+msgid ""
+"To install the clients on a Linux, Mac OS X, or Microsoft Windows system, "
+"use <package>pip</package>. It is easy to use, ensures that you get the "
+"latest version of the clients from the <link "
+"href=\"http://pypi.python.org/\">Python Package Index</link>, and lets you "
+"update or remove the packages later on."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml81(para)
+msgid ""
+"Install <package>pip</package> through the package manager for your system:"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml84(title)
+msgid "MacOS"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml88(title)
+msgid "Microsoft Windows"
+msgstr "Microsoft Windows"
+
+#: ./doc/common/section_cli_install.xml89(para)
+msgid ""
+"Ensure that the <filename>C:\\Python27\\Scripts</filename> directory is "
+"defined in the <literal>PATH</literal> environment variable, and use the "
+"<placeholder-1/> command from the <package>setuptools</package> package: "
+"<placeholder-2/>Another option is to use the unofficial binary installer "
+"provided by Christoph Gohlke (<link "
+"href=\"http://www.lfd.uci.edu/~gohlke/pythonlibs/#pip\">http://www.lfd.uci.edu/~gohlke/pythonlibs/#pip</link>)."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml106(title)
+msgid "Ubuntu and Debian"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml112(title)
+msgid "Red Hat Enterprise Linux, CentOS, or Fedora"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml113(para)
+msgid ""
+"A packaged version enables you to use <package>yum</package> to install the "
+"package: <placeholder-1/> There are also packaged versions of the clients "
+"available in <link href=\"http://openstack.redhat.com/\">RDO</link> that "
+"enable <package>yum</package> to install the clients as described in <xref "
+"linkend=\"cli_clients_install_packages\"/>."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml125(title)
+msgid "SUSE Linux Enterprise Linux 11"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml126(para)
+msgid ""
+"A <link href=\"https://build.opensuse.org/package/show?package=python-"
+"pip&amp;project=Cloud:OpenStack:Master\">packaged version available in the "
+"Open Build Service</link> enables you to use or <package>zypper</package> to"
+" install the package. First, add the Open Build Service repository: "
+"<placeholder-1/> Then install <package>pip</package> and use it to manage "
+"client installation: <placeholder-2/> There are also packaged versions of "
+"the clients available that enable <package>zypper</package> to install the "
+"clients as described in <xref linkend=\"cli_clients_install_packages\"/>."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml141(title)
+msgid "openSUSE"
+msgstr "openSUSE"
+
+#: ./doc/common/section_cli_install.xml142(para)
+msgid ""
+"You can install <package>pip</package> and use it to manage client "
+"installation: <placeholder-1/> There are also packaged versions of the "
+"clients available that enable <package>zypper</package> to install the "
+"clients as described in <xref linkend=\"cli_clients_install_packages\"/>"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml157(title)
+msgid "Install the clients"
+msgstr "Installez les clients"
+
+#: ./doc/common/section_cli_install.xml158(para)
+msgid ""
+"When following the instructions in this section, replace "
+"<replaceable>PROJECT</replaceable> with the lowercase name of the client to "
+"install, such as <placeholder-1/>. Repeat for each client. The following "
+"values are valid:"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml165(para)
+msgid "<literal>ceilometer</literal> - Telemetry API"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml169(para)
+msgid "<literal>cinder</literal> - Block Storage API and extensions"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml173(para)
+msgid "<literal>glance</literal> - Image Service API"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml177(para)
+msgid "<literal>heat</literal> - Orchestration API"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml181(para)
+msgid "<literal>keystone</literal> - Identity service API and extensions"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml185(para)
+msgid "<literal>neutron</literal> - Networking API"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml189(para)
+msgid "<literal>nova</literal> - Compute API and extensions"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml193(para)
+msgid "<literal>swift</literal> - Object Storage API"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml197(para)
+msgid "<literal>trove</literal> - Database Service API"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml201(para)
+msgid ""
+"The following example shows the command for installing the nova client with "
+"<replaceable>pip</replaceable>."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml206(title)
+msgid "Installing with pip"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml207(para)
+msgid ""
+"Use <package>pip</package> to install the OpenStack clients on a Linux, Mac "
+"OS X, or Microsoft Windows system. It is easy to use and ensures that you "
+"get the latest version of the client from the <link "
+"href=\"http://pypi.python.org/pypi\">Python Package Index</link>. Also, "
+"<package>pip</package> enables you to update or remove a package."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml214(para)
+msgid "Install each client separately by using the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml217(para)
+msgid "For Mac OS X or Linux:"
+msgstr "Pour Mac OS X ou Linux:"
+
+#: ./doc/common/section_cli_install.xml218(replaceable)
+#: ./doc/common/section_cli_install.xml220(replaceable)
+#: ./doc/common/section_cli_install.xml232(replaceable)
+#: ./doc/common/section_cli_install.xml236(replaceable)
+#: ./doc/common/section_cli_install.xml243(replaceable)
+#: ./doc/common/section_cli_install.xml252(replaceable)
+#: ./doc/common/section_cli_install.xml255(replaceable)
+#: ./doc/common/section_cli_version.xml9(replaceable)
+msgid "PROJECT"
+msgstr "PROJECT"
+
+#: ./doc/common/section_cli_install.xml219(para)
+msgid "For Microsoft Windows:"
+msgstr "Pour Microsoft Windows:"
+
+#: ./doc/common/section_cli_install.xml224(title)
+msgid "Installing from packages"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml225(para)
+msgid ""
+"RDO, openSUSE and SUSE Linux Enterprise have client packages that can be "
+"installed without <filename>pip</filename>."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml227(para)
+msgid ""
+"On Red Hat Enterprise Linux, CentOS, or Fedora, use <placeholder-1/> to "
+"install the clients from the packaged versions available in <link "
+"href=\"http://openstack.redhat.com/\">RDO</link>: <placeholder-2/>"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml233(para)
+msgid ""
+"For openSUSE, use <package>zypper</package> to install the clients from the "
+"distribution packages Service: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml237(para)
+msgid ""
+"For SUSE Linux Enterprise Server, use <package>zypper</package> to install "
+"the clients from the distribution packages in the Open Build Service. First,"
+" add the Open Build Service repository: <placeholder-1/> Then you can "
+"install the packages: <placeholder-2/>"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml248(title)
+msgid "Upgrade or remove clients"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml249(para)
+msgid ""
+"To upgrade a client, add the <literal>--upgrade</literal> option to the "
+"<placeholder-1/> command:"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml253(para)
+msgid "To remove the a client, run the <placeholder-1/> command:"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml258(title)
+msgid "What's next"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml259(para)
+msgid ""
+"Before you can run client commands, you must create and source the "
+"<filename><replaceable>PROJECT</replaceable>-openrc.sh</filename> file to "
+"set environment variables. See <xref linkend=\"cli_openrc\"/>."
+msgstr ""
+
+#: ./doc/common/section_cli_help.xml6(title)
+msgid "Get help for client commands"
+msgstr ""
+
+#: ./doc/common/section_cli_help.xml7(para)
+msgid ""
+"To get usage information, including a list of commands with descriptions, "
+"for a client, run the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_help.xml9(replaceable)
+#: ./doc/common/section_cli_help.xml59(replaceable)
+msgid "CLIENT_NAME"
+msgstr "CLIENT_NAME"
+
+#: ./doc/common/section_cli_help.xml10(para)
+msgid ""
+"For example, to get help information for the swift client, run the following"
+" command:"
+msgstr ""
+
+#: ./doc/common/section_cli_help.xml54(para)
+msgid ""
+"Depending on your credentials, you might not have permission to use every "
+"command."
+msgstr ""
+
+#: ./doc/common/section_cli_help.xml57(para)
+msgid ""
+"After the <option>help</option> command, you can enter a command name to get"
+" help for that command, as follows:"
+msgstr ""
+
+#: ./doc/common/section_cli_help.xml59(replaceable)
+msgid "COMMAND_NAME"
+msgstr "COMMAND_NAME"
+
+#: ./doc/common/section_cli_help.xml60(para)
+msgid ""
+"For example, to get help for the glance <placeholder-1/> command, enter the "
+"following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_help.xml64(para)
+msgid ""
+"The command returns a description of the command and its positional and "
+"optional arguments:"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-intro.xml8(para)
+msgid ""
+"OpenStack Object Storage (code-named swift) is open source software for "
+"creating redundant, scalable data storage using clusters of standardized "
+"servers to store petabytes of accessible data. It is a long-term storage "
+"system for large amounts of static data that can be retrieved, leveraged, "
+"and updated. Object Storage uses a distributed architecture with no central "
+"point of control, providing greater scalability, redundancy, and permanence."
+" Objects are written to multiple hardware devices, with the OpenStack "
+"software responsible for ensuring data replication and integrity across the "
+"cluster. Storage clusters scale horizontally by adding new nodes. Should a "
+"node fail, OpenStack works to replicate its content from other active nodes."
+" Because OpenStack uses software logic to ensure data replication and "
+"distribution across different devices, inexpensive commodity hard drives and"
+" servers can be used in lieu of more expensive equipment."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-intro.xml19(para)
+msgid ""
+"Object Storage is ideal for cost effective, scale-out storage. It provides a"
+" fully distributed, API-accessible storage platform that can be integrated "
+"directly into applications or used for backup, archiving, and data "
+"retention."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml8(title)
+msgid "Configuration file format"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml10(para)
+msgid ""
+"OpenStack uses the <glossterm>INI</glossterm> file format for configuration "
+"files. An INI file is a simple text file that specifies options as "
+"<literal>key=value</literal> pairs, grouped into sections. The "
+"<literal>DEFAULT</literal> section contains most of the configuration "
+"options. Lines starting with a hash sign (<literal>#</literal>) are comment "
+"lines. For example:"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml29(replaceable)
+msgid "KEYSTONE_DBPASS"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml29(replaceable)
+msgid "controller"
+msgstr "controller"
+
+#: ./doc/common/section_config_format.xml32(para)
+msgid ""
+"Options can have different type for values. The comments in the sample "
+"config files always mention these. The following types are used by "
+"OpenStack:"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml39(term)
+msgid "boolean value"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml41(para)
+msgid ""
+"Enables or disables an option. The allowed values are "
+"<literal>true</literal> and <literal>false</literal>."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml51(term)
+msgid "floating point value"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml53(para)
+msgid ""
+"A floating point number like <literal>0.25</literal> or "
+"<literal>1000</literal>."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml62(term)
+msgid "integer value"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml64(para)
+msgid ""
+"An integer number is a number without fractional components, like "
+"<literal>0</literal> or <literal>42</literal>."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml74(term)
+msgid "list value"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml76(para)
+msgid ""
+"Represents values of other types, separated by commas. As an example, the "
+"following sets <option>allowed_rpc_exception_modules</option> to a list "
+"containing the four elements <literal>oslo.messaging.exceptions</literal>, "
+"<literal>nova.exception</literal>, <literal>cinder.exception</literal>, and "
+"<literal>exceptions</literal>:"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml92(term)
+msgid "multi valued"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml94(para)
+msgid ""
+"A multi-valued option is a string value and can be given more than once, all"
+" values will be used."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml105(term)
+msgid "string value"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml107(para)
+msgid "Strings can be optionally enclosed with single or double quotes."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml127(title)
+msgid "Sections"
+msgstr "Sections"
+
+#: ./doc/common/section_config_format.xml134(literal)
+#: ./doc/common/tables/ceilometer-database.xml19(th)
+#: ./doc/common/tables/neutron-openvswitch_agent.xml19(th)
+#: ./doc/common/tables/heat-clients.xml19(th)
+#: ./doc/common/tables/cinder-solidfire.xml19(th)
+#: ./doc/common/tables/neutron-rpc.xml19(th)
+#: ./doc/common/tables/nova-periodic.xml19(th)
+#: ./doc/common/tables/keystone-policy.xml19(th)
+#: ./doc/common/tables/glance-auth_token.xml19(th)
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml19(th)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml7(literal)
+#: ./doc/common/tables/ceilometer-redis.xml19(th)
+#: ./doc/common/tables/cinder-storage_ceph.xml19(th)
+#: ./doc/common/tables/nova-testing.xml19(th)
+#: ./doc/common/tables/nova-metadata.xml19(th)
+#: ./doc/common/tables/cinder-hp3par.xml19(th)
+#: ./doc/common/tables/keystone-misc.xml19(th)
+#: ./doc/common/tables/neutron-scheduler.xml19(th)
+#: ./doc/common/tables/glance-rbd.xml19(th)
+#: ./doc/common/tables/cinder-storage_xen.xml19(th)
+#: ./doc/common/tables/ceilometer-common.xml19(th)
+#: ./doc/common/tables/cinder-database.xml19(th)
+#: ./doc/common/tables/ceilometer-logging.xml19(th)
+#: ./doc/common/tables/heat-common.xml19(th)
+#: ./doc/common/tables/nova-ipv6.xml19(th)
+#: ./doc/common/tables/nova-vnc.xml19(th)
+#: ./doc/common/tables/trove-qpid.xml19(th)
+#: ./doc/common/tables/keystone-api.xml19(th)
+#: ./doc/common/tables/glance-rpc.xml19(th)
+#: ./doc/common/tables/neutron-policy.xml19(th)
+#: ./doc/common/tables/nova-xen.xml19(th)
+#: ./doc/common/tables/trove-amqp.xml19(th)
+#: ./doc/common/tables/glance-matchmaker.xml19(th)
+#: ./doc/common/tables/nova-rabbitmq.xml19(th)
+#: ./doc/common/tables/nova-policy.xml19(th)
+#: ./doc/common/tables/ceilometer-inspector.xml19(th)
+#: ./doc/common/tables/cinder-scheduler.xml19(th)
+#: ./doc/common/tables/neutron-logging.xml19(th)
+#: ./doc/common/tables/nova-availabilityzones.xml19(th)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml19(th)
+#: ./doc/common/tables/neutron-rootwrap.xml19(th)
+#: ./doc/common/tables/cinder-auth.xml19(th)
+#: ./doc/common/tables/heat-qpid.xml19(th)
+#: ./doc/common/tables/neutron-auth_token.xml19(th)
+#: ./doc/common/tables/nova-ldap.xml19(th)
+#: ./doc/common/tables/ceilometer-auth.xml19(th)
+#: ./doc/common/tables/cinder-quota.xml19(th)
+#: ./doc/common/tables/nova-compute.xml19(th)
+#: ./doc/common/tables/keystone-rabbit.xml19(th)
+#: ./doc/common/tables/cinder-backups_ceph.xml19(th)
+#: ./doc/common/tables/heat-cfn_api.xml19(th)
+#: ./doc/common/tables/neutron-vmware.xml19(th)
+#: ./doc/common/tables/nova-zeromq.xml19(th)
+#: ./doc/common/tables/cinder-storage.xml19(th)
+#: ./doc/common/tables/glance-registry.xml19(th)
+#: ./doc/common/tables/heat-quota.xml19(th)
+#: ./doc/common/tables/nova-common.xml19(th)
+#: ./doc/common/tables/nova-volumes.xml19(th)
+#: ./doc/common/tables/neutron-redis.xml19(th)
+#: ./doc/common/tables/heat-zeromq.xml19(th)
+#: ./doc/common/tables/heat-amqp.xml19(th)
+#: ./doc/common/tables/nova-redis.xml19(th)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml7(literal)
+#: ./doc/common/tables/nova-db.xml19(th)
+#: ./doc/common/tables/glance-rabbitmq.xml19(th)
+#: ./doc/common/tables/neutron-l3_agent.xml19(th)
+#: ./doc/common/tables/glance-policy.xml19(th)
+#: ./doc/common/tables/nova-neutron.xml19(th)
+#: ./doc/common/tables/cinder-backups.xml19(th)
+#: ./doc/common/tables/glance-vmware.xml19(th)
+#: ./doc/common/tables/cinder-zoning.xml19(th)
+#: ./doc/common/tables/heat-notification.xml19(th)
+#: ./doc/common/tables/nova-vpn.xml19(th)
+#: ./doc/common/tables/trove-common.xml19(th)
+#: ./doc/common/tables/trove-api.xml19(th)
+#: ./doc/common/tables/cinder-zadara.xml19(th)
+#: ./doc/common/tables/nova-conductor.xml19(th)
+#: ./doc/common/tables/nova-livemigration.xml19(th)
+#: ./doc/common/tables/heat-rabbitmq.xml19(th)
+#: ./doc/common/tables/keystone-amqp.xml19(th)
+#: ./doc/common/tables/keystone-rpc.xml19(th)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml7(literal)
+#: ./doc/common/tables/cinder-zones.xml19(th)
+#: ./doc/common/tables/cinder-scality.xml19(th)
+#: ./doc/common/tables/neutron-agent.xml19(th)
+#: ./doc/common/tables/cinder-emc.xml19(th)
+#: ./doc/common/tables/cinder-vmware.xml19(th)
+#: ./doc/common/tables/heat-metadata_api.xml19(th)
+#: ./doc/common/tables/trove-rabbitmq.xml19(th)
+#: ./doc/common/tables/neutron-kombu.xml19(th)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml19(th)
+#: ./doc/common/tables/neutron-ml2_ofa.xml19(th)
+#: ./doc/common/tables/glance-api.xml19(th)
+#: ./doc/common/tables/heat-waitcondition_api.xml19(th)
+#: ./doc/common/tables/cinder-storwize.xml19(th)
+#: ./doc/common/tables/cinder-hplefthand.xml19(th)
+#: ./doc/common/tables/glance-s3.xml19(th)
+#: ./doc/common/tables/nova-rootwrap.xml19(th)
+#: ./doc/common/tables/heat-loadbalancer.xml19(th)
+#: ./doc/common/tables/ceilometer-api.xml19(th)
+#: ./doc/common/tables/ceilometer-exchange.xml19(th)
+#: ./doc/common/tables/cinder-lvm.xml19(th)
+#: ./doc/common/tables/trove-dns.xml19(th)
+#: ./doc/common/tables/trove-volume.xml19(th)
+#: ./doc/common/tables/heat-auth_token.xml19(th)
+#: ./doc/common/tables/neutron-quotas.xml19(th)
+#: ./doc/common/tables/cinder-storage_nfs.xml19(th)
+#: ./doc/common/tables/heat-api.xml19(th)
+#: ./doc/common/tables/glance-logging.xml19(th)
+#: ./doc/common/tables/neutron-metering_agent.xml19(th)
+#: ./doc/common/tables/neutron-zeromq.xml19(th)
+#: ./doc/common/tables/cinder-storage_glusterfs.xml19(th)
+#: ./doc/common/tables/cinder-common.xml19(th)
+#: ./doc/common/tables/glance-swift.xml19(th)
+#: ./doc/common/tables/trove-quota.xml19(th)
+#: ./doc/common/tables/cinder-auth_token.xml19(th)
+#: ./doc/common/tables/cinder-xiv.xml19(th)
+#: ./doc/common/tables/nova-glance.xml19(th)
+#: ./doc/common/tables/keystone-auth_token.xml19(th)
+#: ./doc/common/tables/nova-s3.xml19(th)
+#: ./doc/common/tables/nova-pci.xml19(th)
+#: ./doc/common/tables/cinder-api.xml19(th)
+#: ./doc/common/tables/trove-heat.xml19(th)
+#: ./doc/common/tables/glance-sheepdog.xml19(th)
+#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml7(literal)
+#: ./doc/common/tables/cinder-windows.xml19(th)
+#: ./doc/common/tables/cinder-san-solaris.xml19(th)
+#: ./doc/common/tables/keystone-zeromq.xml19(th)
+#: ./doc/common/tables/ceilometer-rpc.xml19(th)
+#: ./doc/common/tables/glance-filesystem.xml19(th)
+#: ./doc/common/tables/trove-rpc.xml19(th)
+#: ./doc/common/tables/ceilometer-swift.xml19(th)
+#: ./doc/common/tables/trove-backup.xml19(th)
+#: ./doc/common/tables/nova-network.xml19(th)
+#: ./doc/common/tables/glance-redis.xml19(th)
+#: ./doc/common/tables/nova-ca.xml19(th)
+#: ./doc/common/tables/neutron-dhcp_agent.xml19(th)
+#: ./doc/common/tables/ceilometer-collector.xml19(th)
+#: ./doc/common/tables/cinder-hds-hus.xml19(th)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml19(th)
+#: ./doc/common/tables/heat-debug.xml19(th)
+#: ./doc/common/tables/nova-kombu.xml19(th)
+#: ./doc/common/tables/trove-guestagent.xml19(th)
+#: ./doc/common/tables/nova-qpid.xml19(th)
+#: ./doc/common/tables/glance-qpid.xml19(th)
+#: ./doc/common/tables/glance-amqp.xml19(th)
+#: ./doc/common/tables/glance-zmq.xml19(th)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml7(literal)
+#: ./doc/common/tables/neutron-testing.xml19(th)
+#: ./doc/common/tables/trove-compute.xml19(th)
+#: ./doc/common/tables/cinder-rpc.xml19(th)
+#: ./doc/common/tables/cinder-hpmsa.xml19(th)
+#: ./doc/common/tables/cinder-storage_gpfs.xml19(th)
+#: ./doc/common/tables/keystone-notification.xml19(th)
+#: ./doc/common/tables/trove-zeromq.xml19(th)
+#: ./doc/common/tables/neutron-lbaas.xml19(th)
+#: ./doc/common/tables/cinder-backups_swift.xml19(th)
+#: ./doc/common/tables/trove-database.xml19(th)
+#: ./doc/common/tables/nova-authentication.xml19(th)
+#: ./doc/common/tables/glance-gridfs.xml19(th)
+#: ./doc/common/tables/neutron-notifier.xml19(th)
+#: ./doc/common/tables/nova-rpc_all.xml19(th)
+#: ./doc/common/tables/nova-scheduling.xml19(th)
+#: ./doc/common/tables/cinder-eqlx.xml19(th)
+#: ./doc/common/tables/heat-redis.xml19(th)
+#: ./doc/common/tables/nova-ec2.xml19(th)
+#: ./doc/common/tables/cinder-block-device.xml19(th)
+#: ./doc/common/tables/neutron-metadata.xml19(th)
+#: ./doc/common/tables/nova-fping.xml19(th)
+#: ./doc/common/tables/neutron-compute.xml19(th)
+#: ./doc/common/tables/glance-imagecache.xml19(th)
+#: ./doc/common/tables/cinder-nas.xml19(th)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml19(th)
+#: ./doc/common/tables/keystone-logging.xml19(th)
+#: ./doc/common/tables/heat-rpc.xml19(th)
+#: ./doc/common/tables/trove-taskmanager.xml19(th)
+#: ./doc/common/tables/heat-cloudwatch_api.xml19(th)
+#: ./doc/common/tables/cinder-images.xml19(th)
+#: ./doc/common/tables/cinder-huawei.xml19(th)
+#: ./doc/common/tables/nova-console.xml19(th)
+#: ./doc/common/tables/cinder-nexenta_nfs.xml19(th)
+#: ./doc/common/tables/nova-quota.xml19(th)
+#: ./doc/common/tables/heat-logging.xml19(th)
+#: ./doc/common/tables/heat-crypt.xml19(th)
+#: ./doc/common/tables/neutron-ssl.xml19(th)
+#: ./doc/common/tables/cinder-coraid.xml19(th)
+#: ./doc/common/tables/neutron-wsgi.xml19(th)
+#: ./doc/common/tables/cinder-compute.xml19(th)
+#: ./doc/common/tables/glance-wsgi.xml19(th)
+#: ./doc/common/tables/neutron-qpid.xml19(th)
+#: ./doc/common/tables/nova-rpc.xml19(th)
+#: ./doc/common/tables/cinder-backups_tsm.xml19(th)
+#: ./doc/common/tables/cinder-san.xml19(th)
+#: ./doc/common/tables/nova-logging.xml19(th)
+#: ./doc/common/tables/keystone-security.xml19(th)
+#: ./doc/common/tables/nova-api.xml19(th)
+#: ./doc/common/tables/trove-auth_token.xml19(th)
+#: ./doc/common/tables/glance-cinder.xml19(th)
+#: ./doc/common/tables/glance-common.xml19(th)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml7(literal)
+#: ./doc/common/tables/trove-nova.xml19(th)
+#: ./doc/common/tables/neutron-rabbitmq.xml19(th)
+#: ./doc/common/tables/keystone-ec2.xml19(th)
+#: ./doc/common/tables/neutron-api.xml19(th)
+#: ./doc/common/tables/trove-logging.xml19(th)
+#: ./doc/common/tables/keystone-redis.xml19(th)
+#: ./doc/common/tables/nova-xvpnvncproxy.xml19(th)
+#: ./doc/common/tables/heat-clients_backends.xml19(th)
+#: ./doc/common/tables/glance-testing.xml19(th)
+#: ./doc/common/tables/neutron-common.xml19(th)
+#: ./doc/common/tables/nova-hypervisor.xml19(th)
+#: ./doc/common/tables/keystone-qpid.xml19(th)
+#: ./doc/common/tables/nova-wsgi.xml19(th)
+#: ./doc/common/tables/nova-configdrive.xml19(th)
+#: ./doc/common/tables/ceilometer-qpid.xml19(th)
+#: ./doc/common/tables/heat-database.xml19(th)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml19(th)
+#: ./doc/common/tables/neutron-db.xml19(th)
+#: ./doc/common/tables/trove-debug.xml19(th)
+#: ./doc/common/tables/trove-swift.xml19(th)
+#: ./doc/common/tables/nova-libvirt.xml19(th)
+#: ./doc/common/tables/ceilometer-amqp.xml19(th)
+#: ./doc/common/tables/glance-ssl.xml19(th)
+#: ./doc/common/tables/keystone-debug.xml19(th)
+#: ./doc/common/tables/cinder-rootwrap.xml19(th)
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml19(th)
+msgid "[DEFAULT]"
+msgstr "[DEFAULT]"
+
+#: ./doc/common/section_config_format.xml136(para)
+msgid ""
+"Contains most configuration options. If the documentation for a "
+"configuration option does not specify its section, assume that it appears in"
+" this section."
+msgstr "Presque toutes les options de configuration sont organisées dans cette section. Si la documentation concernant une option de configuration ne stipule pas cette section, il faudra supposer qu'elle concernera celle-ci. "
+
+#: ./doc/common/section_config_format.xml145(literal)
+#: ./doc/common/tables/ceilometer-database.xml38(th)
+#: ./doc/common/tables/cinder-storage.xml134(th)
+#: ./doc/common/tables/nova-db.xml33(th)
+#: ./doc/common/tables/cinder-common.xml226(th)
+#: ./doc/common/tables/cinder-connection.xml19(th)
+#: ./doc/common/tables/glance-db.xml19(th)
+#: ./doc/common/tables/heat-database.xml34(th)
+#: ./doc/common/tables/neutron-db.xml30(th)
+#: ./doc/common/tables/keystone-database.xml19(th)
+msgid "[database]"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml147(para)
+msgid ""
+"Configuration options for the database that stores the state of the "
+"OpenStack service."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml128(para)
+msgid ""
+"Configuration options are grouped by section. Most configuration file "
+"supports at least the following sections: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml158(title)
+msgid "Substitution"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml160(para)
+msgid ""
+"The configuration file supports variable substitution. After you set a "
+"configuration option, it can be referenced in later configuration values "
+"when you precede it with a <literal>$</literal>, like "
+"<literal>$OPTION</literal>."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml167(para)
+msgid ""
+"The following example uses the values of <literal>rabbit_host</literal> and "
+"<literal>rabbit_port</literal> to define the value of the "
+"<literal>rabbit_hosts</literal> option, in this case as "
+"<literal>controller:5672</literal>."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml185(para)
+msgid ""
+"To avoid substitution, use <literal>$$</literal>, it is replaced by a single"
+" <literal>$</literal>. For example, if your LDAP DNS password is "
+"<literal>$xkj432</literal>, specify it, as follows: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml191(para)
+msgid ""
+"The code uses the Python "
+"<literal>string.Template.safe_substitute()</literal> method to implement "
+"variable substitution. For more details on how variable substitution is "
+"resolved, see <link href=\"http://docs.python.org/2/library/string.html"
+"#template-strings\">http://docs.python.org/2/library/string.html#template-"
+"strings</link> and <link "
+"href=\"http://www.python.org/dev/peps/pep-0292/\">PEP 292</link>."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml204(title)
+msgid "Whitespace"
+msgstr "Whitespace"
+
+#: ./doc/common/section_config_format.xml205(para)
+msgid ""
+"To include whitespace in a configuration value, use a quoted string. For "
+"example:"
+msgstr "Pour insérer un espace dans une valeur de configuration, utiliser une chaîne entre guillement. Par exemple"
+
+#: ./doc/common/section_config_format.xml211(title)
+msgid "Define an alternate location for a config file"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml212(para)
+msgid ""
+"Most services and the and the <placeholder-1/> command-line clients load the"
+" configuration file. To define an alternate location for the configuration "
+"file, pass the <parameter>--config-file "
+"<replaceable>CONFIG_FILE</replaceable></parameter> parameter when you start "
+"a service or call a <placeholder-2/> command."
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml5(title)
+msgid "OpenStack Image Service"
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml6(para)
+msgid ""
+"The OpenStack Image Service is central to infrastructure-as-a-service (IaaS)"
+" as shown in <xref linkend=\"conceptual-architecture\"/>. It accepts API "
+"requests for disk or server images, and image metadata from end users or "
+"OpenStack Compute components. It also supports the storage of disk or server"
+" images on various repository types, including OpenStack Object Storage."
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml12(para)
+msgid ""
+"A number of periodic processes run on the OpenStack Image Service to support"
+" caching. Replication services ensures consistency and availability through "
+"the cluster. Other periodic processes include auditors, updaters, and "
+"reapers."
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml16(para)
+msgid "The OpenStack Image Service includes the following components:"
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml20(systemitem)
+msgid "glance-api"
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml21(para)
+msgid "Accepts Image API calls for image discovery, retrieval, and storage."
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml25(systemitem)
+msgid "glance-registry"
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml26(para)
+msgid ""
+"Stores, processes, and retrieves metadata about images. Metadata includes "
+"items such as size and type."
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml28(title)
+msgid "Security note"
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml29(para)
+msgid ""
+"The registry is a private internal service meant for use by OpenStack Image "
+"Service. Do not disclose it to users."
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml35(term)
+msgid "Database"
+msgstr "Base de données"
+
+#: ./doc/common/section_getstart_image.xml36(para)
+msgid ""
+"Stores image metadata and you can choose your database depending on your "
+"preference. Most deployments use MySQL or SQlite."
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml41(term)
+msgid "Storage repository for image files"
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml42(para)
+msgid ""
+"Various repository types are supported including normal file systems, Object"
+" Storage, RADOS block devices, HTTP, and Amazon S3. Note that some "
+"repositories will only support read-only usage."
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml6(title)
+msgid "Get started with OpenStack"
+msgstr "Débuter avec OpenStack "
+
+#: ./doc/common/ch_getstart.xml7(para)
+msgid ""
+"The OpenStack project is an open source cloud computing platform for all "
+"types of clouds, which aims to be simple to implement, massively scalable, "
+"and feature rich. Developers and cloud computing technologists from around "
+"the world create the OpenStack project."
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml12(para)
+msgid ""
+"OpenStack provides an Infrastructure-as-a-Service "
+"(<glossterm>IaaS</glossterm>) solution through a set of interrelated "
+"services. Each service offers an application programming interface "
+"(<glossterm>API</glossterm>) that facilitates this integration. Depending on"
+" your needs, you can install some or all services."
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml20(para)
+msgid ""
+"The following table describes the OpenStack services that make up the "
+"OpenStack architecture:"
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml23(caption)
+#: ./doc/common/ch_getstart.xml188(title)
+msgid "OpenStack services"
+msgstr "Les services d'OpenStack"
+
+#: ./doc/common/ch_getstart.xml30(th)
+msgid "Project name"
+msgstr "Nom du projet"
+
+#: ./doc/common/ch_getstart.xml38(glossterm)
+msgid "Dashboard"
+msgstr "Tableau de Bord"
+
+#: ./doc/common/ch_getstart.xml42(glossterm)
+msgid "Horizon"
+msgstr "Horizon"
+
+#: ./doc/common/ch_getstart.xml44(td)
+msgid ""
+"Provides a web-based self-service portal to interact with underlying "
+"OpenStack services, such as launching an instance, assigning IP addresses "
+"and configuring access controls."
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml56(glossterm)
+msgid "Nova"
+msgstr "Nova"
+
+#: ./doc/common/ch_getstart.xml58(td)
+msgid ""
+"Manages the lifecycle of compute instances in an OpenStack environment. "
+"Responsibilities include spawning, scheduling and decommissioning of virtual"
+" machines on demand."
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml70(glossterm)
+msgid "Neutron"
+msgstr "Neutron"
+
+#: ./doc/common/ch_getstart.xml72(td)
+msgid ""
+"Enables network connectivity as a service for other OpenStack services, such"
+" as OpenStack Compute. Provides an API for users to define networks and the "
+"attachments into them. Has a pluggable architecture that supports many "
+"popular networking vendors and technologies."
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml79(th)
+msgid "Storage"
+msgstr "Stockage"
+
+#: ./doc/common/ch_getstart.xml87(glossterm)
+msgid "Swift"
+msgstr "Swift"
+
+#: ./doc/common/ch_getstart.xml90(glossterm)
+msgid "RESTful"
+msgstr "RESTful"
+
+#: ./doc/common/ch_getstart.xml89(td)
+msgid ""
+"Stores and retrieves arbitrary unstructured data objects via a "
+"<placeholder-1/>, HTTP based API. It is highly fault tolerant with its data "
+"replication and scale out architecture. Its implementation is not like a "
+"file server with mountable directories."
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml103(glossterm)
+msgid "Cinder"
+msgstr "Cinder"
+
+#: ./doc/common/ch_getstart.xml105(td)
+msgid ""
+"Provides persistent block storage to running instances. Its pluggable driver"
+" architecture facilitates the creation and management of block storage "
+"devices."
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml110(th)
+msgid "Shared services"
+msgstr "Les Services partagés"
+
+#: ./doc/common/ch_getstart.xml114(glossterm)
+msgid "Identity service"
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml118(glossterm)
+msgid "Keystone"
+msgstr "Keystone"
+
+#: ./doc/common/ch_getstart.xml120(td)
+msgid ""
+"Provides an authentication and authorization service for other OpenStack "
+"services. Provides a catalog of endpoints for all OpenStack services."
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml131(glossterm)
+msgid "Glance"
+msgstr "Glance"
+
+#: ./doc/common/ch_getstart.xml133(td)
+msgid ""
+"Stores and retrieves virtual machine disk images. OpenStack Compute makes "
+"use of this during instance provisioning."
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml146(glossterm)
+msgid "Ceilometer"
+msgstr "Ceilometer"
+
+#: ./doc/common/ch_getstart.xml148(td)
+msgid ""
+"Monitors and meters the OpenStack cloud for billing, benchmarking, "
+"scalability, and statistical purposes."
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml153(th)
+msgid "Higher-level services"
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml160(glossterm)
+msgid "Heat"
+msgstr "Heat"
+
+#: ./doc/common/ch_getstart.xml164(glossterm)
+msgid "HOT"
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml162(td)
+msgid ""
+"Orchestrates multiple composite cloud applications by using either the "
+"native <placeholder-1/> template format or the AWS CloudFormation template "
+"format, through both an OpenStack-native REST API and a CloudFormation-"
+"compatible Query API."
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml176(glossterm)
+msgid "Trove"
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml178(td)
+msgid ""
+"Provides scalable and reliable Cloud Database-as-a-Service functionality for"
+" both relational and non-relational database engines."
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml189(para)
+msgid "This section describes OpenStack services in detail."
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml207(title)
+msgid "Feedback"
+msgstr "remarques"
+
+#: ./doc/common/section_fibrechannel.xml5(title)
+msgid "Fibre Channel support in Compute"
+msgstr "Support de Fibre Channel en Calcul"
+
+#: ./doc/common/section_fibrechannel.xml6(para)
+msgid ""
+"Fibre Channel support in OpenStack Compute is remote block storage attached "
+"to compute nodes for VMs."
+msgstr ""
+
+#. TODO: This below statement needs to be verified for current release
+#: ./doc/common/section_fibrechannel.xml9(para)
+msgid ""
+"In the Grizzly release, Fibre Channel supported only the KVM hypervisor."
+msgstr "Fibre Channel supporte l'hyperviseur KVM uniquement dans l'édition grizzly."
+
+#: ./doc/common/section_fibrechannel.xml11(para)
+msgid ""
+"Compute and Block Storage for Fibre Channel do not support automatic zoning."
+" Fibre Channel arrays must be pre-zoned or directly attached to the KVM "
+"hosts."
+msgstr "Il n'y a pas de support de zonage automatique dans Nova ou Cinder pour Fibre Channel. Les matrices Fibre Channel doivent être pré-zonées ou directement rattachées aux hôtes KVM. "
+
+#: ./doc/common/section_fibrechannel.xml15(title)
+msgid "KVM host requirements"
+msgstr "Il n'y a pas de support de zonage automatique dans Nova ou Cinder pour Fibre Channel. Les matrices Fibre Channel doivent être pré-zonées ou directement rattachées aux hôtes KVM. "
+
+#: ./doc/common/section_fibrechannel.xml16(para)
+msgid "You must install these packages on the KVM host:"
+msgstr "L'hôte KVM doit contenir les packs suivants: "
+
+#: ./doc/common/section_fibrechannel.xml19(para)
+msgid ""
+"<package>sysfsutils</package> - Nova uses the <package>systool</package> "
+"application in this package."
+msgstr ""
+
+#: ./doc/common/section_fibrechannel.xml25(para)
+msgid ""
+"<package>sg3-utils</package> - Nova uses the <package>sg_scan</package> and "
+"<package>sginfo</package> applications."
+msgstr "<package>sg3-utils</package>  – Utilise les applications <package>sg_scan</package>. "
+
+#: ./doc/common/section_fibrechannel.xml31(para)
+msgid "Installing the <package>multipath-tools</package> package is optional."
+msgstr "L'installation du pack <package>sginfo</package> est optionnel."
+
+#: ./doc/common/section_fibrechannel.xml35(title)
+msgid "Install required packages"
+msgstr "Installations des Packs Nécessaires"
+
+#: ./doc/common/section_fibrechannel.xml36(para)
+msgid "Use these commands to install the system packages:"
+msgstr "Utilisez les commandes suivantes pour installer les packs système. "
+
+#: ./doc/common/section_fibrechannel.xml40(para)
+msgid "For systems running openSUSE or SUSE Linux Enterprise Server:"
+msgstr ""
+
+#: ./doc/common/section_fibrechannel.xml45(para)
+msgid "For systems running Red Hat:"
+msgstr "Pour les systèmes fonctionnant sous Red Hat:"
+
+#: ./doc/common/section_fibrechannel.xml49(para)
+msgid "For systems running Ubuntu:"
+msgstr "Pour les systèmes fonctionnants sous Ubuntu:"
+
+#: ./doc/common/section_cli_keystone_services.xml7(title)
+msgid "Create and manage services and service users"
+msgstr "Créer et gérer des services et des utilisateurs des services"
+
+#: ./doc/common/section_cli_keystone_services.xml8(para)
+msgid "The Identity Service enables you to define services, as follows:"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml12(para)
+msgid ""
+"Service catalog template. The Identity Service acts as a service catalog of "
+"endpoints for other OpenStack services. The "
+"<literal>etc/default_catalog.templates</literal> template file defines the "
+"endpoints for services. When the Identity Service uses a template file back "
+"end, any changes that are made to the endpoints are cached. These changes do"
+" not persist when you restart the service or reboot the machine."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml23(para)
+msgid ""
+"A SQL back end for the catalog service. When the Identity Service is online,"
+" you must add the services to the catalog. When you deploy a system for "
+"production, use the SQL back end."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml29(para)
+msgid ""
+"The <literal>auth_token</literal> middleware supports the use of either a "
+"shared secret or users for each service."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml32(para)
+msgid ""
+"To authenticate users against the Identity Service, you must create a "
+"service user for each OpenStack service. For example, create a service user "
+"for the Compute, Block Storage, and Networking services."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml36(para)
+msgid ""
+"To configure the OpenStack services with service users, create a project for"
+" all services and create users for each service. Assign the admin role to "
+"each service user and project pair. This role enables users to validate "
+"tokens and authenticate and authorize other user requests."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml42(title)
+msgid "Create a service"
+msgstr "Créez un service"
+
+#: ./doc/common/section_cli_keystone_services.xml45(para)
+msgid "List the available services:"
+msgstr "Listez les services disponibles:"
+
+#: ./doc/common/section_cli_keystone_services.xml59(para)
+msgid "To create a service, run this command:"
+msgstr "Pour créer un service, exécutez cette instruction:"
+
+#: ./doc/common/section_cli_keystone_services.xml60(replaceable)
+msgid "service_name"
+msgstr "service_name"
+
+#: ./doc/common/section_cli_keystone_services.xml60(replaceable)
+msgid "service_type"
+msgstr "service_type"
+
+#: ./doc/common/section_cli_keystone_services.xml60(replaceable)
+msgid "service_description"
+msgstr "service_description"
+
+#: ./doc/common/section_cli_keystone_services.xml61(para)
+msgid "The arguments are:"
+msgstr "Les arguments sont:"
+
+#: ./doc/common/section_cli_keystone_services.xml64(para)
+msgid ""
+"<code><replaceable>service_name</replaceable></code>. The unique name of the"
+" new service."
+msgstr "<code><replaceable>service_name</replaceable></code>. Le nom unique de ce nouveau service."
+
+#: ./doc/common/section_cli_keystone_services.xml68(para)
+msgid ""
+"<code><replaceable>service_type</replaceable></code>. The service type, such"
+" as <code>identity</code>, <code>compute</code>, <code>network</code>, "
+"<code>image</code>, <code>object-store</code> or any other service "
+"identifier string."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml78(para)
+msgid ""
+"<code><replaceable>service_description</replaceable></code>. The description"
+" of the service."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml82(para)
+msgid ""
+"For example, to create a <literal>swift</literal> service of type <literal"
+">object-store</literal>, run this command:"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml97(para)
+msgid "To get details for a service, run this command:"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml99(replaceable)
+msgid "service_ID"
+msgstr "service_ID"
+
+#: ./doc/common/section_cli_keystone_services.xml114(title)
+msgid "Create service users"
+msgstr "Créer des utilisateurs des services"
+
+#: ./doc/common/section_cli_keystone_services.xml117(para)
+msgid ""
+"Create a project for the service users. Typically, this project is named "
+"<literal>service</literal>, but choose any name you like:"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml122(para)
+msgid "The output shows the ID for the project."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml123(para)
+msgid ""
+"Make a note of this ID. You need it to create service users and assign "
+"roles."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml135(para)
+msgid "Create service users for the relevant services for your deployment."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml139(para)
+msgid ""
+"To assign the admin role to the service user-project pairs, run this command"
+" to get the ID of the admin role:"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml155(para)
+msgid "Assign the admin role to the user-project pair:"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml157(replaceable)
+msgid "SERVICE_USER_ID"
+msgstr "SERVICE_USER_ID"
+
+#: ./doc/common/section_cli_keystone_services.xml157(replaceable)
+msgid "ADMIN_ROLE_ID"
+msgstr "ADMIN_ROLE_ID"
+
+#: ./doc/common/section_cli_keystone_services.xml157(replaceable)
+msgid "SERVICE_PROJECT_ID"
+msgstr "SERVICE_PROJECT_ID"
+
+#: ./doc/common/section_cli_keystone_services.xml162(title)
+msgid "Delete a service"
+msgstr "Supprimez un service"
+
+#: ./doc/common/section_cli_keystone_services.xml163(para)
+msgid "To delete a specified service, specify its ID:"
+msgstr "Pour supprimer un service spécifique, préciser son ID:"
+
+#: ./doc/common/section_cli_keystone_services.xml164(replaceable)
+msgid "SERVICE_ID"
+msgstr "SERVICE_ID"
+
+#: ./doc/common/section_keystone-concepts-domain-management.xml6(title)
+msgid "Domains"
+msgstr "Domaines"
+
+#: ./doc/common/section_keystone-concepts-domain-management.xml7(para)
+msgid ""
+"A domain defines administrative boundaries for the management of Identity "
+"entities. A domain may represent an individual, company, or operator-owned "
+"space. It is used for exposing administrative activities directly to the "
+"system users."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-domain-management.xml10(para)
+msgid ""
+"A domain is a collection of tenants, users, and roles. Users may be given a "
+"domain's administrator role. A domain administrator may create tenants, "
+"users, and groups within a domain and assign roles to users and groups."
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml6(title)
+msgid "Customize the dashboard"
+msgstr "Personalisez le tableau de bord"
+
+#: ./doc/common/section_dashboard_customizing.xml7(para)
+msgid ""
+"Adapted from <link href=\"http://www.prestonlee.com/2012/05/09/how-to-"
+"custom-brand-the-openstack-horizon-dashboard/\">How To Custom Brand The "
+"OpenStack “Horizon” Dashboard</link>."
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml11(para)
+msgid ""
+"You install the OpenStack dashboard through the <literal>openstack-"
+"dashboard</literal> package. You can customize the dashboard with your own "
+"colors, logo, and site title through a CSS file."
+msgstr "Vous installez le tableau de bord OpenStack à partir du paquetage <literal>openstack-dashboard</literal>. Vous pouvez personnaliser le tableau de bord avec vos propres couleurs, logo ou titre de site grâce à un fichier CSS."
+
+#: ./doc/common/section_dashboard_customizing.xml15(para)
+msgid ""
+"Canonical also provides an <literal>openstack-dashboard-ubuntu-"
+"theme</literal> package that brands the Python-based Django interface."
+msgstr "Canonical fournit aussi un paquetage <literal>openstack-dashboard-ubuntu-theme</literal> caractéristique de l'interface Django à base de Python."
+
+#: ./doc/common/section_dashboard_customizing.xml47(para)
+msgid ""
+"Create a graphical logo with a transparent background. The text "
+"<literal>TGen Cloud</literal> in this example is rendered through "
+"<filename>.png</filename> files of multiple sizes created with a graphics "
+"program."
+msgstr "Créez un logo graphique avec un fond transparent. Le texte <literal>TGen Cloud</literal>, dans cet exemple, est mis en valeur grâce à des fichiers <filename>.png</filename> de tailles diverses créés à l'aide d'un programme de création graphique."
+
+#: ./doc/common/section_dashboard_customizing.xml52(para)
+msgid ""
+"Use a 200×27 for the logged-in banner graphic, and 365×50 for the login "
+"screen graphic."
+msgstr "Utilisez une taille de 200x27 pour le graphique de la bannière une fois connecté, et 365x50 pour le graphique de l'encart d'ouverture de session."
+
+#: ./doc/common/section_dashboard_customizing.xml56(para)
+msgid ""
+"Set the HTML title, which appears at the top of the browser window, by "
+"adding the following line to <filename>/etc/openstack-"
+"dashboard/local_settings.py</filename>:"
+msgstr "Assignez à la fenêtre du navigateur le titre HTML apparaissant en haut en ajoutant la ligne suivante au fichier <filename>/etc/openstack-dashboard/local_settings.py</filename>: "
+
+#: ./doc/common/section_dashboard_customizing.xml59(code)
+msgid "SITE_BRANDING = \"Example, Inc. Cloud\""
+msgstr "SITE_BRANDING = \"Exemple, Inc. Cloud\""
+
+#: ./doc/common/section_dashboard_customizing.xml63(para)
+msgid ""
+"Upload your new graphic files to the following location: "
+"<filename>/usr/share/openstack-"
+"dashboard/openstack_dashboard/static/dashboard/img/</filename>"
+msgstr "Chargez sur le serveur vos nouveaux fichiers graphiques dans la zone : <filename>/usr/share/openstack-dashboard/openstack_dashboard/static/dashboard/img/</filename>"
+
+#: ./doc/common/section_dashboard_customizing.xml68(para)
+msgid ""
+"Create a CSS style sheet in the following directory: <filename>/usr/share"
+"/openstack-dashboard/openstack_dashboard/static/dashboard/css/</filename>"
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml72(para)
+msgid ""
+"Edit your CSS file to override the Ubuntu customizations in the "
+"<filename>ubuntu.css</filename> file."
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml75(para)
+msgid ""
+"Change the colors and image file names as appropriate, though the relative "
+"directory paths should be the same. The following example file shows you how"
+" to customize your CSS file:"
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml114(para)
+msgid ""
+"Open the following HTML template in an editor: <filename>/usr/share"
+"/openstack-"
+"dashboard/openstack_dashboard/templates/_stylesheets.html</filename>"
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml118(para)
+msgid "Add a line to include your <filename>custom.css</filename> file:"
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml123(emphasis)
+msgid ""
+"&lt;link href='{{ STATIC_URL }}dashboard/css/custom.css' media='screen' "
+"rel='stylesheet' /&gt;"
+msgstr "&lt;link href='{{ STATIC_URL }}dashboard/css/custom.css' media='screen' rel='stylesheet' /&gt;"
+
+#: ./doc/common/section_dashboard_customizing.xml127(title)
+msgid "Restart Apache:"
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml128(para)
+#: ./doc/common/section_dashboard_sessions.xml180(para)
+msgid "On Ubuntu: <placeholder-1/>"
+msgstr "Sur Ubuntu: <placeholder-1/>"
+
+#: ./doc/common/section_dashboard_customizing.xml131(para)
+msgid "On Fedora, RHEL, CentOS: <placeholder-1/>"
+msgstr "Sur Fedora, RHEL, CentOS: <placeholder-1/>"
+
+#: ./doc/common/section_dashboard_customizing.xml134(para)
+#: ./doc/common/section_dashboard_sessions.xml187(para)
+msgid "On openSUSE: <placeholder-1/>"
+msgstr "Sur openSUSE: <placeholder-1/>"
+
+#: ./doc/common/section_dashboard_customizing.xml139(para)
+msgid "Reload the dashboard in your browser to view your changes."
+msgstr "Relancer le tableau de bord dans votre navigateur pour voir vos changements."
+
+#: ./doc/common/section_dashboard_customizing.xml141(para)
+msgid "Modify your CSS file as appropriate."
+msgstr "Modifier votre dossier CSS comme il convient."
+
 #: ./doc/common/section_compute_config-api.xml6(title)
 msgid "Configure the Compute API"
 msgstr ""
@@ -24282,208 +23296,1223 @@ msgid ""
 "linkend=\"config_table_nova_api\"/>."
 msgstr ""
 
-#: ./doc/common/section_getstart_block-storage.xml5(title)
-msgid "OpenStack Block Storage"
+#: ./doc/common/section_cli_nova_fileinjection.xml10(title)
+msgid "Inject files into instances"
 msgstr ""
 
-#: ./doc/common/section_getstart_block-storage.xml6(para)
+#: ./doc/common/section_cli_nova_fileinjection.xml11(para)
 msgid ""
-"OpenStack Block Storage enables management of volumes, volume snapshots, and"
-" volume types. It consists of the following components:"
+"You can inject local files into the instance file system when you launch an "
+"instance."
 msgstr ""
 
-#: ./doc/common/section_getstart_block-storage.xml11(systemitem)
-msgid "cinder-api"
-msgstr ""
-
-#: ./doc/common/section_getstart_block-storage.xml12(para)
+#: ./doc/common/section_cli_nova_fileinjection.xml13(para)
 msgid ""
-"Accepts API requests and routes them to <systemitem class=\"service"
-"\">cinder-volume</systemitem> for action."
+"Use the <parameter>--file dst-path=src-path</parameter> parameter on the "
+"nova <placeholder-1/> command."
 msgstr ""
 
-#: ./doc/common/section_getstart_block-storage.xml17(systemitem)
-msgid "cinder-volume"
+#: ./doc/common/section_cli_nova_fileinjection.xml15(para)
+msgid "You can inject up to five files."
 msgstr ""
 
-#: ./doc/common/section_getstart_block-storage.xml18(para)
+#: ./doc/common/section_cli_nova_fileinjection.xml16(para)
 msgid ""
-"Responds to requests to read from and write to the OpenStack Block Storage "
-"database to maintain state, interacting with other processes (like "
-"<systemitem class=\"service\">cinder-scheduler</systemitem>) through a "
-"message queue and directly upon block storage providing hardware or "
-"software. It can interact with a variety of storage providers through a "
-"driver architecture."
+"For example, you might inject the "
+"<filename>special_authorized_keysfile</filename> file into the instance "
+"rather than using the regular ssh key injection."
 msgstr ""
 
-#: ./doc/common/section_getstart_block-storage.xml28(term)
-msgid "<systemitem class=\"service\">cinder-scheduler</systemitem> daemon"
+#: ./doc/common/section_cli_nova_fileinjection.xml19(para)
+msgid "Run the following command:<placeholder-1/>"
 msgstr ""
 
-#: ./doc/common/section_getstart_block-storage.xml30(para)
+#: ./doc/common/ch_preface.xml7(title)
+msgid "Preface"
+msgstr "Preface"
+
+#: ./doc/common/section_cli_nova_resizerebuild.xml6(title)
+msgid "Change the size of your server"
+msgstr "Changez la taille de votre serveur"
+
+#: ./doc/common/section_cli_nova_resizerebuild.xml7(para)
+msgid "You change the size of a server by changing its flavor."
+msgstr "Vous changez la taille d'un serveur en changeant son type d'instance."
+
+#: ./doc/common/section_cli_nova_resizerebuild.xml10(para)
 msgid ""
-"Like the <systemitem class=\"service\">nova-scheduler</systemitem>, picks "
-"the optimal block storage provider node on which to create the volume."
+"Show information about your server, including its size, which is shown as "
+"the value of the flavor property."
 msgstr ""
 
-#: ./doc/common/section_getstart_block-storage.xml36(para)
-msgid "Routes information between the Block Storage processes."
+#: ./doc/common/section_cli_nova_resizerebuild.xml43(para)
+msgid "The size (flavor) of the server is <literal>m1.small (2)</literal>."
 msgstr ""
 
-#: ./doc/common/section_getstart_block-storage.xml40(para)
+#: ./doc/common/section_cli_nova_resizerebuild.xml46(para)
+msgid "List the available flavors with the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_resizerebuild.xml59(para)
 msgid ""
-"OpenStack Block Storage interacts with OpenStack Compute to provide volumes "
-"for instances."
+"To resize the server, pass the server ID or name and the new flavor to the "
+"<placeholder-1/> command. Include the <literal>--poll</literal> parameter to"
+" report the resize progress."
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml5(title)
-msgid "OpenStack Image Service"
+#: ./doc/common/section_cli_nova_resizerebuild.xml67(para)
+msgid "Show the status for your server:"
+msgstr "Montrer l'état de votre serveur:"
+
+#: ./doc/common/section_cli_nova_resizerebuild.xml74(para)
+msgid "When the resize completes, the status becomes VERIFY_RESIZE."
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml6(para)
+#: ./doc/common/section_cli_nova_resizerebuild.xml77(para)
+msgid "Confirm the resize:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_resizerebuild.xml79(para)
+#: ./doc/common/section_cli_nova_resizerebuild.xml85(para)
+msgid "The server status becomes ACTIVE."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_resizerebuild.xml82(para)
 msgid ""
-"The OpenStack Image Service is central to infrastructure-as-a-service (IaaS)"
-" as shown in <xref linkend=\"conceptual-architecture\"/>. It accepts API "
-"requests for disk or server images, and image metadata from end users or "
-"OpenStack Compute components. It also supports the storage of disk or server"
-" images on various repository types, including OpenStack Object Storage."
+"If the resize fails or does not work as expected, you can revert the resize:"
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml12(para)
+#: ./doc/common/section_dashboard-configure.xml6(title)
+msgid "Configure the dashboard"
+msgstr "Configurer le tableau de bord"
+
+#: ./doc/common/section_dashboard-configure.xml8(para)
+msgid "You can configure the dashboard for a simple HTTP deployment."
+msgstr "Vous pouvez configurer le tableau de bord pour un  déploiement HTTP simple."
+
+#: ./doc/common/section_dashboard-configure.xml14(para)
+msgid "Also, you can configure the size of the VNC window in the dashboard."
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml10(title)
+msgid "Storage concepts"
+msgstr "Concepts de stockage"
+
+#: ./doc/common/section_storage-concepts.xml11(para)
+msgid "The OpenStack stack uses the following storage types:"
+msgstr "La pile OpenStack utilise diverses formes de stockage, ce qui peut troubler même les ingénieurs cloud expérimentés. Le tableau suivant décrit les types de stockage :"
+
+#: ./doc/common/section_storage-concepts.xml13(caption)
+msgid "Storage types"
+msgstr "La pile OpenStack utilise diverses formes de stockage, ce qui peut troubler même les ingénieurs cloud expérimentés. Le tableau suivant décrit les types de stockage :"
+
+#: ./doc/common/section_storage-concepts.xml19(td)
+msgid "On-instance / ephemeral"
+msgstr "Sur-instance / éphémère"
+
+#: ./doc/common/section_storage-concepts.xml20(td)
+msgid "Block storage (cinder)"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml26(td)
+msgid "Runs operating systems and provides scratch space"
+msgstr "Exécute les systèmes d’exploitation et fournit de l’espace scratch"
+
+#: ./doc/common/section_storage-concepts.xml27(td)
 msgid ""
-"A number of periodic processes run on the OpenStack Image Service to support"
-" caching. Replication services ensures consistency and availability through "
-"the cluster. Other periodic processes include auditors, updaters, and "
-"reapers."
-msgstr ""
+"Used for adding additional persistent storage to a virtual machine (VM)"
+msgstr "Utilisé pour ajouter du stockage persistant additionnel à une machine virtuelle (VM)"
 
-#: ./doc/common/section_getstart_image.xml16(para)
-msgid "The OpenStack Image Service includes the following components:"
-msgstr ""
+#: ./doc/common/section_storage-concepts.xml29(td)
+msgid "Used for storing virtual machine images and data"
+msgstr "Utilisé pour stocker des images de machines virtuelles et des données"
 
-#: ./doc/common/section_getstart_image.xml20(systemitem)
-msgid "glance-api"
-msgstr ""
+#: ./doc/common/section_storage-concepts.xml32(td)
+msgid "Persists until VM is terminated"
+msgstr "Persiste jusqu’à ce que la VM soit éteinte"
 
-#: ./doc/common/section_getstart_image.xml21(para)
-msgid "Accepts Image API calls for image discovery, retrieval, and storage."
-msgstr ""
+#: ./doc/common/section_storage-concepts.xml33(td)
+#: ./doc/common/section_storage-concepts.xml34(td)
+msgid "Persists until deleted"
+msgstr "Persiste jusqu’à l’effacement"
 
-#: ./doc/common/section_getstart_image.xml25(systemitem)
-msgid "glance-registry"
-msgstr ""
+#: ./doc/common/section_storage-concepts.xml37(td)
+#: ./doc/common/section_storage-concepts.xml38(td)
+msgid "Access associated with a VM"
+msgstr "Accès associé à une VM"
 
-#: ./doc/common/section_getstart_image.xml26(para)
+#: ./doc/common/section_storage-concepts.xml39(td)
+msgid "Available from anywhere"
+msgstr "Disponible depuis partout"
+
+#: ./doc/common/section_storage-concepts.xml42(td)
+msgid "Implemented as a filesystem underlying OpenStack Compute"
+msgstr "Implémenté en tant que système de fichiers sous-jacent à OpenStack Compute"
+
+#: ./doc/common/section_storage-concepts.xml44(td)
 msgid ""
-"Stores, processes, and retrieves metadata about images. Metadata includes "
-"items such as size and type."
+"Mounted via OpenStack Block Storage controlled protocol (for example, iSCSI)"
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml28(title)
-msgid "Security note"
-msgstr ""
+#: ./doc/common/section_storage-concepts.xml46(td)
+msgid "REST API"
+msgstr "REST API"
 
-#: ./doc/common/section_getstart_image.xml29(para)
+#: ./doc/common/section_storage-concepts.xml49(td)
+msgid "Administrator configures size setting, based on flavors"
+msgstr "Administrateur configure le paramètre de taille, en se basant sur les types d'instances"
+
+#: ./doc/common/section_storage-concepts.xml51(td)
+msgid "Sizings based on need"
+msgstr "Dimensionnements basés sur le besoin"
+
+#: ./doc/common/section_storage-concepts.xml52(td)
+msgid "Easily scalable for future growth"
+msgstr "Facilement redimensionnable en vue d’une croissance future"
+
+#: ./doc/common/section_storage-concepts.xml55(td)
+msgid "Example: 10GB first disk, 30GB/core second disk"
+msgstr "Exemple: 10GB premier disque, 30GB/core second disque"
+
+#: ./doc/common/section_storage-concepts.xml56(td)
+msgid "Example: 1TB \"extra hard drive\""
+msgstr "Exemple: 1TB \"disque dur supplémentaire\""
+
+#: ./doc/common/section_storage-concepts.xml57(td)
+msgid "Example: 10s of TBs of data set storage"
+msgstr "Exemple: Des dizaines de TB de stockage destiné aux données"
+
+#: ./doc/common/section_storage-concepts.xml64(para)
 msgid ""
-"The registry is a private internal service meant for use by OpenStack Image "
-"Service. Do not disclose it to users."
+"<emphasis>You cannot use OpenStack Object Storage like a traditional hard "
+"drive.</emphasis> The Object Storage relaxes some of the constraints of a "
+"POSIX-style file system to get other gains. You can access the objects "
+"through an API which uses HTTP. Subsequently you don't have to provide "
+"atomic operations (that is, relying on eventual consistency), you can scale "
+"a storage system easily and avoid a central point of failure."
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml35(term)
-msgid "Database"
-msgstr "Base de données"
-
-#: ./doc/common/section_getstart_image.xml36(para)
+#: ./doc/common/section_storage-concepts.xml73(para)
 msgid ""
-"Stores image metadata and you can choose your database depending on your "
-"preference. Most deployments use MySQL or SQlite."
+"<emphasis>The OpenStack Image Service is used to manage the virtual machine "
+"images in an OpenStack cluster, not store them.</emphasis> It provides an "
+"abstraction to different methods for storage - a bridge to the storage, not "
+"the storage itself."
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml41(term)
-msgid "Storage repository for image files"
-msgstr ""
-
-#: ./doc/common/section_getstart_image.xml42(para)
+#: ./doc/common/section_storage-concepts.xml80(para)
 msgid ""
-"Various repository types are supported including normal file systems, Object"
-" Storage, RADOS block devices, HTTP, and Amazon S3. Note that some "
-"repositories will only support read-only usage."
+"<emphasis>The OpenStack Object Storage can function on its own.</emphasis> "
+"The Object Storage (swift) product can be used independently of the Compute "
+"(nova) product."
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml62(para)
+msgid "You should note that:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_rpc-for-networking.xml9(para)
+msgid ""
+"OpenStack projects use an open standard for messaging middleware known as "
+"AMQP. This messaging middleware enables the OpenStack services that run on "
+"multiple servers to talk to each other. OpenStack Oslo RPC supports three "
+"implementations of AMQP: <application>RabbitMQ</application>, "
+"<application>Qpid</application>, and <application>ZeroMQ</application>."
+msgstr ""
+
+#: ./doc/common/section_rpc-for-networking.xml20(para)
+msgid ""
+"OpenStack Oslo RPC uses <application>RabbitMQ</application> by default. Use "
+"these options to configure the <application>RabbitMQ</application> message "
+"system. The <option>rpc_backend</option> option is optional as long as "
+"<application>RabbitMQ</application> is the default messaging system. "
+"However, if it is included the configuration, you must set it to "
+"<literal>neutron.openstack.common.rpc.impl_kombu</literal>."
+msgstr "OpenStack Oslo RPC utilise <application>RabbitMQ</application> par défaut. Cette section traite des options de configuration qui sont pertinentes quand <application>RabbitMQ</application> est utilisé. L’option <option>rpc_backend</option> n’est pas nécessaire du moment que <application>RabbitMQ</application> est le système de messagerie par défaut. Toutefois, s’il est inclus, la configuration sur laquelle il doit être défini est <literal>neutron.openstack.common.rpc.impl_kombu</literal>."
+
+#: ./doc/common/section_rpc-for-networking.xml34(para)
+msgid ""
+"Use these options to configure the <application>RabbitMQ</application> "
+"messaging system. You can configure messaging communication for different "
+"installation scenarios, tune retries for RabbitMQ, and define the size of "
+"the RPC thread pool. To monitor notifications through RabbitMQ, you must set"
+" the <option>notification_driver</option> option to "
+"<literal>neutron.notifier.rabbit_notifier</literal> in the "
+"<filename>neutron.conf</filename> file:"
+msgstr "Les tableaux suivants décrivent le reste des options qui peuvent être utilisées quand <application>RabbitMQ</application> est utilisé en tant que système de messagerie. Vous pouvez configurer la communication pas messages pour différents scénarios d’installation et également régler le nombre de nouvelles tentatives de RabbitMQ et la taille du pool de thread RPC. Si vous souhaitez surveiller les notifications par RabbitMQ, vous devez définir l’option <option>notification_driver</option> dans <filename>neutron.conf</filename> à <literal>neutron.notifier.rabbit_notifier</literal>. "
+
+#: ./doc/common/section_rpc-for-networking.xml47(para)
+msgid ""
+"Use these options to configure the <application>Qpid</application> messaging"
+" system for OpenStack Oslo RPC. <application>Qpid</application> is not the "
+"default messaging system, so you must enable it by setting the "
+"<option>rpc_backend</option> option in the <filename>neutron.conf</filename>"
+" file:"
+msgstr "Cette section traite des options de configuration pertinentes si <application>Qpid</application> est utilisé en tant que système de messagerie pour OpenStack Oslo RPC. <application>Qpid</application> n’est pas le système de messagerie par défaut, il doit donc être activé en définissant l’option <option>rpc_backend</option> dans <filename>neutron.conf</filename>."
+
+#: ./doc/common/section_rpc-for-networking.xml56(para)
+msgid ""
+"This critical option points the compute nodes to the "
+"<application>Qpid</application> broker (server). Set the "
+"<option>qpid_hostname</option> option to the host name where the broker runs"
+" in the <filename>neutron.conf</filename> file."
+msgstr "L’option critique qui suit fait pointer les nœuds Compute vers l’intermédiaire (serveur) <application>Qpid</application>. Définissez <option>qpid_hostname</option> dans <filename>neutron.conf</filename> comme nom d’hôte là où l’intermédiaire tourne."
+
+#: ./doc/common/section_rpc-for-networking.xml94(para)
+msgid ""
+"Use these additional options to configure the Qpid messaging driver for "
+"OpenStack Oslo RPC. These options are used infrequently."
+msgstr ""
+
+#: ./doc/common/section_rpc-for-networking.xml103(para)
+msgid ""
+"Use these options to configure the <application>ZeroMQ</application> "
+"messaging system for OpenStack Oslo RPC. <application>ZeroMQ</application> "
+"is not the default messaging system, so you must enable it by setting the "
+"<option>rpc_backend</option> option in the <filename>neutron.conf</filename>"
+" file:"
+msgstr ""
+
+#: ./doc/common/section_rpc-for-networking.xml114(para)
+msgid ""
+"Use these common options to configure the "
+"<application>RabbitMQ</application>, <application>Qpid</application>, and "
+"<application>ZeroMq</application> messaging drivers:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml6(title)
+msgid "Add security group and rules"
+msgstr "Ajouter un groupe de sécurité et des règles"
+
+#: ./doc/common/section_cli_nova_secgroups.xml7(para)
+msgid ""
+"The following procedure shows you how to add security groups and add rules "
+"to the default security group."
+msgstr "Le procédure suivant vous montre comment ajouter les groupes de sécurité et ajouter des règles au groupe de sécurité par défaut."
+
+#: ./doc/common/section_cli_nova_secgroups.xml10(title)
+msgid "Add or delete a security group"
+msgstr "Ajouter ou supprimer un groupe de sécurité"
+
+#: ./doc/common/section_cli_nova_secgroups.xml11(para)
+msgid "Use the <placeholder-1/> command to add security groups."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml13(para)
+msgid ""
+"The following example shows how to create the <literal>secure1</literal> "
+"security group:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml21(para)
+msgid ""
+"After you create the security group, you can view it in the security group "
+"list:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml30(para)
+msgid ""
+"Use the <placeholder-1/> command to delete security groups. You cannot "
+"delete the default security group. The default security group has these "
+"initial settings:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml36(para)
+msgid ""
+"All the traffic originated by the instances (outbound traffic) is allowed"
+msgstr "Tout trafic créé par des instances (trafic sortant) est autorisé."
+
+#: ./doc/common/section_cli_nova_secgroups.xml40(para)
+msgid "All the traffic destined to instances (inbound traffic) is denied"
+msgstr "Tout trafic à destination des instances (trafic entrant) est refusé."
+
+#: ./doc/common/section_cli_nova_secgroups.xml44(para)
+msgid "All the instances inside the group are allowed to talk to each other"
+msgstr "Tous les instances dans le groupe peuvent communiquer entre elles. "
+
+#: ./doc/common/section_cli_nova_secgroups.xml49(para)
+msgid ""
+"You can add extra rules into the default security group for handling the "
+"egress traffic. Rules are ingress only at this time."
+msgstr "Vous pouvez ajouter des règles supplémentaires dans le groupe de sécurité par défaut afin de gérer le trafic de sortie. Les règles concerne le trafic d'entrée uniquement à ce stade-là."
+
+#: ./doc/common/section_cli_nova_secgroups.xml53(para)
+msgid ""
+"The following example deletes the <literal>secure1</literal> group. When you"
+" view the security group list, it no longer appears:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml65(title)
+msgid "Modify security group rules"
+msgstr "Modifier les règles du groupe de sécurité"
+
+#: ./doc/common/section_cli_nova_secgroups.xml69(para)
+msgid "You cannot change the default outbound behavior."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml66(para)
+msgid ""
+"The security group rules control the incoming traffic that can access the "
+"instances in the group, while all outbound traffic is automatically allowed."
+" <placeholder-1/>Every security group rule is a policy that allows you to "
+"specify inbound connections that can access the instance by source address, "
+"destination port, and IP protocol (TCP, UDP or ICMP). Currently, you cannot "
+"manage ipv6 and other protocols through the security rules, making them "
+"permitted by default. To manage such protocols, you can deploy a firewall in"
+" front of your OpenStack cloud to control other types of traffic. The "
+"command requires the following arguments for both TCP and UDP rules:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml84(emphasis)
+#: ./doc/common/section_cli_nova_secgroups.xml124(emphasis)
+#: ./doc/common/section_cli_nova_secgroups.xml209(emphasis)
+msgid "&lt;secgroup&gt;"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml86(para)
+#: ./doc/common/section_cli_nova_secgroups.xml126(para)
+#: ./doc/common/section_cli_nova_secgroups.xml211(para)
+msgid "ID of security group."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml91(emphasis)
+#: ./doc/common/section_cli_nova_secgroups.xml131(emphasis)
+#: ./doc/common/section_cli_nova_secgroups.xml216(emphasis)
+msgid "&lt;ip_proto&gt;"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml98(emphasis)
+#: ./doc/common/section_cli_nova_secgroups.xml223(emphasis)
+msgid "&lt;from_port&gt;"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml105(emphasis)
+#: ./doc/common/section_cli_nova_secgroups.xml230(emphasis)
+msgid "&lt;to_port&gt;"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml112(emphasis)
+#: ./doc/common/section_cli_nova_secgroups.xml152(emphasis)
+#: ./doc/common/section_cli_nova_secgroups.xml237(emphasis)
+msgid "&lt;cidr&gt;"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml118(para)
+msgid ""
+"For ICMP rules, instead of specifying a begin and end port, you specify the "
+"allowed ICMP code and ICMP type:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml133(para)
+msgid "IP protocol (with icmp specified)."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml138(emphasis)
+msgid "&lt;ICMP_code&gt;"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml140(para)
+msgid "The ICMP code."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml145(emphasis)
+msgid "&lt;ICMP_type&gt;"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml147(para)
+msgid "The ICMP type."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml154(para)
+msgid "CIDR for the source address range."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml159(para)
+msgid ""
+"Entering <literal>-1</literal> for both code and type indicates that all "
+"ICMP codes and types are allowed."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml164(title)
+msgid "The CIDR notation"
+msgstr "La notation CIDR"
+
+#: ./doc/common/section_cli_nova_secgroups.xml165(para)
+msgid ""
+"That notation allows you to specify a base IP address and a suffix that "
+"designates the number of significant bits in the IP address used to identify"
+" the network. For example, by specifying a "
+"<literal>88.170.60.32/27</literal>, you specify "
+"<literal>88.170.60.32</literal> as the <emphasis role=\"bold\">base "
+"IP</emphasis> and <literal>27</literal> as the <emphasis "
+"role=\"bold\">suffix</emphasis>. Because you use an IPV4 format, only 5 bits"
+" are available for the host part (32 minus 27). The "
+"<literal>0.0.0.0/0</literal> notation means you allow the entire IPV4 range,"
+" which allows all addresses."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml179(para)
+msgid ""
+"For example, to allow any IP address to access a web server running on one "
+"of your instances inside the default security group:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml188(para)
+msgid ""
+"To allow any IP address to ping an instance inside the default security "
+"group (Code 0, Type 8 for the ECHO request):"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml204(para)
+msgid ""
+"To delete a rule, you must specify exactly the same arguments that you used "
+"to create it:"
+msgstr ""
+
+#: ./doc/common/section_cli_version.xml6(title)
+msgid "Discover the version number for a client"
+msgstr ""
+
+#: ./doc/common/section_cli_version.xml7(para)
+msgid "Run the following command to discover the version number for a client:"
+msgstr ""
+
+#: ./doc/common/section_cli_version.xml10(para)
+msgid ""
+"For example, to see the version number for the <placeholder-1/> client, run "
+"the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_version.xml14(para)
+msgid "The version number (2.15.0 in the example) is returned."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml6(title)
+msgid "Install XenServer and XCP"
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml8(para)
+msgid ""
+"Before you can run OpenStack with XCP or XenServer, you must install the "
+"software on <link "
+"href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/installation.html#sys_requirements\">an"
+" appropriate server</link>."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml13(para)
+msgid ""
+"Xen is a type 1 hypervisor: When your server starts, Xen is the first "
+"software that runs. Consequently, you must install XenServer or XCP before "
+"you install the operating system where you want to run OpenStack code. The "
+"OpenStack services then run in a virtual machine that you install on top of "
+"XenServer."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml20(para)
+msgid ""
+"Before you can install your system, decide whether to install a free or paid"
+" edition of Citrix XenServer or Xen Cloud Platform from Xen.org. Download "
+"the software from these locations:"
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml28(link)
+msgid "http://www.citrix.com/XenServer/download"
+msgstr "http://www.citrix.com/XenServer/download"
+
+#: ./doc/common/section_xen-install.xml33(link)
+msgid "http://www.xen.org/download/xcp/index.html"
+msgstr "http://www.xen.org/download/xcp/index.html"
+
+#: ./doc/common/section_xen-install.xml36(para)
+msgid ""
+"When you install many servers, you might find it easier to perform <link "
+"href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/installation.html#pxe_boot_install\">PXE"
+" boot installations of XenServer or XCP</link>. You can also package any "
+"post-installation changes that you want to make to your XenServer by <link "
+"href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/supplemental_pack_ddk.html\">creating"
+" your own XenServer supplemental pack</link>."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml46(para)
+msgid ""
+"You can also install the <package>xcp-xenapi</package> package on Debian-"
+"based distributions to get XCP. However, this is not as mature or feature "
+"complete as above distributions. This modifies your boot loader to first "
+"boot Xen and boot your existing OS on top of Xen as Dom0. The xapi daemon "
+"runs in Dom0. Find more details at <link "
+"href=\"http://wiki.xen.org/wiki/Project_Kronos\">http://wiki.xen.org/wiki/Project_Kronos</link>."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml55(para)
+msgid ""
+"Make sure you use the EXT type of storage repository (SR). Features that "
+"require access to VHD files (such as copy on write, snapshot and migration) "
+"do not work when you use the LVM SR. Storage repository (SR) is a XenAPI-"
+"specific term relating to the physical storage where virtual disks are "
+"stored."
+msgstr "Assurez-vous que vous utilisez le type EXT de référentiel de stockage (SR). Les fonctions qui nécessitent l'accès à des fichiers VHD (telles que la copie sur écriture, instantané et migration) ne fonctionnent pas lorsque vous utilisez LVM SR. Le référentiel de stockage (SR) est un terme spécifique XenAPI relatives au stockage physique où les disques virtuels sont stockés."
+
+#: ./doc/common/section_xen-install.xml61(para)
+msgid ""
+"On the XenServer/XCP installation screen, choose the <guilabel>XenDesktop "
+"Optimized</guilabel> option. If you use an answer file, make sure you use "
+"<literal>srtype=\"ext\"</literal> in the <option>installation</option> tag "
+"of the answer file."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml69(title)
+msgid "Post-installation steps"
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml70(para)
+msgid "Complete these steps to install OpenStack in your XenServer system:"
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml74(para)
+msgid ""
+"For resize and migrate functionality, complete the changes described in the "
+"<citetitle>Configure resize</citetitle> section in the <link href"
+"=\"../config-reference/content/index.html\"><citetitle>OpenStack "
+"Configuration Reference</citetitle></link>."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml82(para)
+msgid ""
+"Install the VIF isolation rules to help prevent mac and IP address spoofing."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml86(para)
+msgid "Install the XenAPI plug-ins. See the following section."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml90(para)
+msgid ""
+"To support AMI type images, you must set up <literal>/boot/guest</literal> "
+"symlink/directory in Dom0. For detailed instructions, see next section."
+msgstr "Afin de supporter les images de types AMI, il est nécessaire de régler <literal>/boot/guest</literal> symlink/directory dans Dom0. Pour des instructions plus détaillées, voir la prochaine section."
+
+#: ./doc/common/section_xen-install.xml96(para)
+msgid ""
+"To support resize/migration, set up an ssh trust relation between your "
+"XenServer hosts, and ensure <literal>/images</literal> is properly set up. "
+"See next section for more details."
+msgstr "Afin de supportef la redimension/migration, établissez une relation de confiance ssh avec les hôtes XenServer, et assurez-vous que <literal>/images</literal> est correctement réglé. Voir la prochaine section pour plus de détails."
+
+#: ./doc/common/section_xen-install.xml102(para)
+msgid ""
+"Create a Paravirtualized virtual machine that can run the OpenStack compute "
+"code."
+msgstr "Créez une machine virtuelle Paravirtualisée qui puissant lancer le code de calcul OpenStack."
+
+#: ./doc/common/section_xen-install.xml106(para)
+msgid ""
+"Install and configure the <systemitem class=\"service\">nova-"
+"compute</systemitem> in the above virtual machine."
+msgstr "Installez et configurer le <systemitem class=\"service\">nova-compute</systemitem> dans la machine précitée."
+
+#: ./doc/common/section_xen-install.xml111(para)
+msgid ""
+"For more information, see how DevStack performs the last three steps for "
+"developer deployments. For more information about DevStack, see "
+"<citetitle>Getting Started With XenServer and Devstack</citetitle> (<link "
+"href=\"https://github.com/openstack-"
+"dev/devstack/blob/master/tools/xen/README.md\">https://github.com/openstack-"
+"dev/devstack/blob/master/tools/xen/README.md</link>). Find more information "
+"about the first step, see <citetitle>Multi Tenancy Networking Protections in"
+" XenServer</citetitle> (<link "
+"href=\"https://github.com/openstack/nova/blob/master/plugins/xenserver/doc/networking.rst\">https://github.com/openstack/nova/blob/master/plugins/xenserver/doc/networking.rst</link>)."
+" For information about how to install the XenAPI plug-ins, see "
+"<citetitle>XenAPI README</citetitle> (<link "
+"href=\"https://github.com/openstack/nova/blob/master/plugins/xenserver/xenapi/README\">https://github.com/openstack/nova/blob/master/plugins/xenserver/xenapi/README</link>)."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml131(title)
+msgid "Xen boot from ISO"
+msgstr "Charger Xen à partir d'un ISO"
+
+#: ./doc/common/section_xen-install.xml132(para)
+msgid ""
+"XenServer, through the XenAPI integration with OpenStack, provides a feature"
+" to boot instances from an ISO file. To activate the Boot From ISO feature, "
+"you must configure the SR elements on XenServer host, as follows:"
+msgstr "XenServer, par l'intégration de XenAPI avec OpenStack, fourni une fonction permettant le chargement d'instances à partir d'un fichier ISO. Pour activer la fonction “Chargement à partir de l'ISO”, il vous faut configurer les éléments SR sur l'hôte XenServer de la manière suivante:"
+
+#: ./doc/common/section_xen-install.xml139(para)
+msgid ""
+"Create an ISO-typed SR, such as an NFS ISO library, for instance. For this, "
+"using XenCenter is a simple method. You must export an NFS volume from a "
+"remote NFS server. Make sure it is exported in read-write mode."
+msgstr "Créez un SR de type ISO, comme une bibliothèque NFS ISO par exemple. Pour se faire, la manière la plus simple sera d'utiliser XenCenter. Vous devez exporter un volume NFS   d'un serveur distant NFS. Vérifiez  que celui-ci est exporté en mode lecture/écriture."
+
+#: ./doc/common/section_xen-install.xml146(para)
+msgid "On the compute host, find and record the uuid of this ISO SR:"
+msgstr "2.\tSur l'ordinateur hôte, trouver l'uuid de cette ISO SR et notez-le."
+
+#: ./doc/common/section_xen-install.xml151(para)
+msgid "Locate the uuid of the NFS ISO library:"
+msgstr "Localisez l'uuid de la bibliothèque NFS ISO:"
+
+#: ./doc/common/section_xen-install.xml155(para)
+msgid ""
+"Set the uuid and configuration. Even if an NFS mount point is not local, you"
+" must specify <literal>local-storage-iso</literal>."
+msgstr "Définissez l'uuid et la configuration. Même si un point de montage NFS n'est pas un stockage local, il faudra spécifier <literal>local-storage-iso</literal>."
+
+#: ./doc/common/section_xen-install.xml161(para)
+msgid ""
+"Make sure the host-uuid from <literal>xe pbd-list</literal> equals the uuid "
+"of the host you found previously:"
+msgstr "Vérifiez que l'hôte uuid de <literal>xe pbd-list</literal> est équivalent à l'uuid de l'hôte que vous avez trouvé précédemment:"
+
+#: ./doc/common/section_xen-install.xml167(para)
+msgid ""
+"You can now add images through the OpenStack Image Service with <literal"
+">disk-format=iso</literal>, and boot them in OpenStack Compute:"
+msgstr "Vous pouvez maintenant ajouter des images via le Répertoire d'Image OpenStack, avec <literal>disk-format=iso</literal> et les lancer dans OpenStack Compute."
+
+#: ./doc/common/section_xapi-install-plugins.xml7(title)
+msgid "Install the XenAPI plug-ins"
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml8(para)
+msgid ""
+"When you use Xen as the hypervisor for OpenStack Compute, you can install a "
+"Python script (or any executable) on the host side, and call that through "
+"the XenAPI. These scripts are called plug-ins. The XenAPI plug-ins live in "
+"the nova code repository. These plug-ins have to be copied to the Dom0 for "
+"the hypervisor, to the appropriate directory, where xapi can find them. "
+"There are several options for the installation. The important thing is to "
+"ensure that the version of the plug-ins are in line with the nova "
+"installation by only installing plug-ins from a matching nova repository."
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml19(title)
+msgid "Manually install the plug-in"
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml22(para)
+msgid "Create temporary files/directories:"
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml27(para)
+msgid ""
+"Get the source from github. The example assumes the master branch is used. "
+"Amend the URL to match the version being used:"
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml32(para)
+msgid ""
+"(Alternatively) To use the official Ubuntu packages, use the following "
+"commands to get the nova code base:"
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml39(para)
+msgid "Copy the plug-ins to the hypervisor:"
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml44(para)
+msgid "Remove the temporary files/directories:"
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml51(title)
+msgid "Package a XenServer supplemental pack"
+msgstr "Pour combiner un pack supplémentaire XenServer"
+
+#: ./doc/common/section_xapi-install-plugins.xml52(para)
+msgid ""
+"Follow these steps to produce a supplemental pack from the nova sources, and"
+" package it as a XenServer supplemental pack."
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml57(para)
+msgid ""
+"Create RPM packages. Given you have the nova sources. Use one of the methods"
+" in <xref linkend=\"manual_install\"/>:"
+msgstr "\t1.\tCréez les packs RPM. Il est entendu que vous possédez les sources nova (utilisez une des méthodes mentionnées dans le <xref linkend=\"manual_install\"/>)"
+
+#: ./doc/common/section_xapi-install-plugins.xml62(para)
+msgid ""
+"These commands leave an <filename>.rpm</filename> file in the "
+"<filename>rpmbuild/RPMS/noarch/</filename> directory."
+msgstr "Ces commandes laisseront un <filename>.rpm</filename> dans le répertoire <filename>rpmbuild/RPMS/noarch/</filename>."
+
+#: ./doc/common/section_xapi-install-plugins.xml68(para)
+msgid ""
+"Pack the RPM packages to a Supplemental Pack, using the XenServer DDK (the "
+"following command should be issued on the XenServer DDK virtual appliance, "
+"after the produced rpm file has been copied over):"
+msgstr "Combiner les packs RPM à un Pack Supplémentaire, en utilisant le XenServer DDK (la commande suivante sera utilisée pour l'appliance virtuelle XenServer DDK, après que le fichier rpm généré ait été copié):"
+
+#: ./doc/common/section_xapi-install-plugins.xml81(para)
+msgid ""
+"This command produces an <filename>.iso</filename> file in the output "
+"directory specified. Copy that file to the hypervisor."
+msgstr "Cette commande génère un fichier <filename>.iso</filename> dans le répertoire de sortie précisé. Copiez ce fichier dans l'hyperviseur."
+
+#: ./doc/common/section_xapi-install-plugins.xml87(para)
+msgid "Install the Supplemental Pack. Log in to the hypervisor, and issue:"
+msgstr "Installez le Pack Supplémentaire. Connectez-le à l'hyperviseur, et lancer:"
+
+#: ./doc/common/section_getstart_orchestration.xml5(title)
+msgid "Orchestration module"
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml6(para)
+msgid ""
+"The Orchestration module provides a template-based orchestration for "
+"describing a cloud application, by running OpenStack API calls to generate "
+"running cloud applications. The software integrates other core components of"
+" OpenStack into a one-file template system. The templates allow you to "
+"create most OpenStack resource types, such as instances, floating IPs, "
+"volumes, security groups and users. It also provides advanced functionality,"
+" such as instance high availability, instance auto-scaling, and nested "
+"stacks. This enables OpenStack core projects to receive a larger user base."
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml16(para)
+msgid ""
+"The service enables deployers to integrate with the Orchestration module "
+"directly or through custom plug-ins."
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml18(para)
+msgid "The Orchestration module consists of the following components:"
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml22(term)
+msgid "<code>heat</code> command-line client"
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml23(para)
+msgid ""
+"A CLI that communicates with the heat-api to run AWS CloudFormation APIs. "
+"End developers can directly use the Orchestration REST API."
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml28(term)
+msgid "<code>heat-api</code> component"
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml28(para)
+msgid ""
+"An OpenStack-native REST API that processes API requests by sending them to "
+"the heat-engine over Remote Procedure Call (RPC)."
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml34(term)
+msgid "<code>heat-api-cfn</code> component"
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml34(para)
+msgid ""
+"An AWS Query API that is compatible with AWS CloudFormation. It processes "
+"API requests by sending them to the heat-engine over RPC."
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml40(code)
+msgid "heat-engine"
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml41(para)
+msgid ""
+"Orchestrates the launching of templates and provides events back to the API "
+"consumer."
+msgstr ""
+
+#: ./doc/common/ch_using_openstack_overview.xml7(title)
+msgid ""
+"How can I <phrase audience=\"enduser\">use</phrase><phrase "
+"audience=\"adminuser\">administer</phrase> an OpenStack cloud?"
+msgstr ""
+
+#: ./doc/common/ch_using_openstack_overview.xml11(para)
+msgid ""
+"As an OpenStack cloud end user, you can provision your own resources within "
+"the limits set by administrators."
+msgstr ""
+
+#: ./doc/common/ch_using_openstack_overview.xml14(para)
+msgid ""
+"As an OpenStack cloud administrative user, you can manage tenants, known as "
+"<glossterm baseform=\"project\">projects</glossterm>, users, services, "
+"images, flavors, and quotas."
+msgstr ""
+
+#: ./doc/common/ch_using_openstack_overview.xml18(para)
+msgid ""
+"The examples in this guide show you how to perform tasks by using the "
+"following methods:"
+msgstr ""
+
+#: ./doc/common/ch_using_openstack_overview.xml22(para)
+msgid ""
+"OpenStack dashboard. Use this web-based graphical interface, code named "
+"<link href=\"https://github.com/openstack/horizon/\">horizon</link>, to "
+"view, create, and manage resources<phrase audience=\"adminuser\"> and "
+"services</phrase>."
+msgstr ""
+
+#: ./doc/common/ch_using_openstack_overview.xml30(para)
+msgid ""
+"OpenStack command-line clients. Each core OpenStack project has a command-"
+"line client that you can use to run simple commands to view, create, and "
+"manage resources<phrase audience=\"adminuser\"> and services</phrase> in a "
+"cloud and automate tasks by using scripts."
+msgstr ""
+
+#: ./doc/common/ch_using_openstack_overview.xml38(para)
+msgid "You can modify these examples for your specific use cases."
+msgstr ""
+
+#: ./doc/common/ch_using_openstack_overview.xml40(para)
+msgid ""
+"In addition to these ways of interacting with a cloud, you can access the "
+"OpenStack APIs directly or indirectly through <link "
+"href=\"http://curl.haxx.se/\">cURL</link> commands or open SDKs. You can "
+"automate access or build tools to manage resources and services by using the"
+" native OpenStack APIs or the EC2 compatibility API."
+msgstr ""
+
+#: ./doc/common/ch_using_openstack_overview.xml46(para)
+msgid ""
+"To use the OpenStack APIs, it helps to be familiar with HTTP/1.1, RESTful "
+"web services, the OpenStack services, and JSON or XML data serialization "
+"formats."
 msgstr ""
 
 #. When image changes, this message will be marked fuzzy or untranslated for
 #. you.
 #. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-characteristics.xml49(None)
+#: ./doc/common/section_keystone-concepts.xml120(None)
+#: ./doc/common/section_keystone-concepts.xml125(None)
 msgid ""
-"@@image: '../common/figures/objectstorage.png'; "
-"md5=e26e374ace84070f5fed24e73adcd562"
+"@@image: 'figures/SCH_5002_V00_NUAC-Keystone.png'; "
+"md5=734714c50c99fc1d74bdfd9f9cd049a6"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-characteristics.xml7(title)
-msgid "Object Storage characteristics"
+#: ./doc/common/section_keystone-concepts.xml7(title)
+msgid "OpenStack Identity concepts"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-characteristics.xml8(para)
-msgid "The key characteristics of Object Storage are that:"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-characteristics.xml11(para)
-msgid "All objects stored in Object Storage have a URL."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-characteristics.xml14(para)
+#: ./doc/common/section_keystone-concepts.xml8(para)
 msgid ""
-"All objects stored are replicated 3✕ in as-unique-as-possible zones, which "
-"can be defined as a group of drives, a node, a rack, and so on."
+"The OpenStack<glossterm>Identity Service</glossterm> performs the following "
+"functions:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-characteristics.xml18(para)
-msgid "All objects have their own metadata."
+#: ./doc/common/section_keystone-concepts.xml12(para)
+msgid "Tracking users and their permissions."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-characteristics.xml21(para)
+#: ./doc/common/section_keystone-concepts.xml15(para)
+msgid "Providing a catalog of available services with their API endpoints."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts.xml19(para)
 msgid ""
-"Developers interact with the object storage system through a RESTful HTTP "
-"API."
-msgstr "Les développeurs interagissent avec le système de stockage d'objets à travers une API HTTP RESTful."
-
-#: ./doc/common/section_objectstorage-characteristics.xml25(para)
-msgid "Object data can be located anywhere in the cluster."
+"To understand OpenStack Identity, you must understand the following "
+"concepts:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-characteristics.xml28(para)
+#: ./doc/common/section_keystone-concepts.xml23(term)
+msgid "User"
+msgstr "Utilisateur"
+
+#: ./doc/common/section_keystone-concepts.xml25(para)
 msgid ""
-"The cluster scales by adding additional nodes without sacrificing "
-"performance, which allows a more cost-effective linear storage expansion "
-"than fork-lift upgrades."
+"Digital representation of a person, system, or service who uses OpenStack "
+"cloud services. The Identity service validates that incoming requests are "
+"made by the user who claims to be making the call. Users have a login and "
+"may be assigned tokens to access resources. Users can be directly assigned "
+"to a particular tenant and behave as if they are contained in that tenant."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-characteristics.xml33(para)
-msgid "Data doesn't have to be migrate to an entirely new storage system."
-msgstr ""
+#: ./doc/common/section_keystone-concepts.xml36(term)
+msgid "Credentials"
+msgstr "Information  d'Authentification          "
 
-#: ./doc/common/section_objectstorage-characteristics.xml36(para)
-msgid "New nodes can be added to the cluster without downtime."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-characteristics.xml39(para)
-msgid "Failed nodes and disks can be swapped out without downtime."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-characteristics.xml42(para)
+#: ./doc/common/section_keystone-concepts.xml38(para)
 msgid ""
-"It runs on industry-standard hardware, such as Dell, HP, and Supermicro."
+"Data that confirms the user's identity. For example, user name and password;"
+" user name and API key; or an authentication token provided by the Identity "
+"Service."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-characteristics.xml53(para)
+#: ./doc/common/section_keystone-concepts.xml45(term)
+msgid "Authentication"
+msgstr "Authentication"
+
+#: ./doc/common/section_keystone-concepts.xml47(para)
 msgid ""
-"Developers can either write directly to the Swift API or use one of the many"
-" client libraries that exist for all of the popular programming languages, "
-"such as Java, Python, Ruby, and C#. Amazon S3 and RackSpace Cloud Files "
-"users should be very familiar with Object Storage. Users new to object "
-"storage systems will have to adjust to a different approach and mindset than"
-" those required for a traditional filesystem."
-msgstr "Les développeurs peuvent soit écrire directement à l'API Swift ou utiliser l'une des nombreuses bibliothèques clientes qui existent pour tous les langages de programmation, tels que Java, Python, Ruby et C #. Les utilisateurs Amazon S3 et Rackspace Cloud Files devrait être très familier avec l'Object Storage. Les nouveaux utilisateurs du système Object Storage devront s'adapter à une approche et une mentalité différente que ceux requis pour un système de fichiers traditionnel."
+"The process of confirming the identity of a user. OpenStack Identity "
+"confirms an incoming request by validating a set of credentials supplied by "
+"the user."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts.xml51(para)
+msgid ""
+"These credentials are initially a user name and password; or a user name and"
+" API key. When user credentials are validated, OpenStack Identity issues an "
+"authentication token which the user provides in subsequent requests."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts.xml59(term)
+msgid "Token"
+msgstr "Jeton/Token "
+
+#: ./doc/common/section_keystone-concepts.xml61(para)
+msgid ""
+"An arbitrary bit of text that is used to access resources. Each token has "
+"information which defines access to resources. A token may be revoked at any"
+" time and is valid for a finite duration."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts.xml65(para)
+msgid ""
+"While OpenStack Identity supports token-based authentication in this "
+"release, the intention is to support additional protocols in the future. Its"
+" main purpose is to be an integration service, and not aspire to be a full-"
+"fledged identity store and management solution."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts.xml74(term)
+msgid "Tenant"
+msgstr "Ensemble/Tenant"
+
+#: ./doc/common/section_keystone-concepts.xml76(para)
+msgid ""
+"A container used to group or isolate resources and/or identity objects. "
+"Depending on the service operator, a tenant may map to a customer, account, "
+"organization, or project."
+msgstr "Contenant utilisé pour regrouper ou isoler des ressources et/ou  des identités-objets. Selon l'opérateur de service, un ensemble peut être lié à des clients, comptes, organisations, ou projets."
+
+#: ./doc/common/section_keystone-concepts.xml85(para)
+msgid ""
+"An OpenStack service, such as Compute (nova), Object Storage (swift), or "
+"Image Service (glance). It provides one or more endpoints through which "
+"users can access resources and perform operations."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts.xml92(term)
+msgid "Endpoint"
+msgstr "Destination"
+
+#: ./doc/common/section_keystone-concepts.xml94(para)
+msgid ""
+"A network-accessible address where you access a service, usually a URL "
+"address. If you are using an extension for templates, an endpoint template "
+"can be created, which represents the templates of all the consumable "
+"services that are available across the regions."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts.xml102(term)
+msgid "Role"
+msgstr "Rôle"
+
+#: ./doc/common/section_keystone-concepts.xml104(para)
+msgid ""
+"A personality with a defined set of user rights and privileges to perform a "
+"specific set of operations."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts.xml106(para)
+msgid ""
+"In the Identity service, a token that is issued to a user includes the list "
+"of roles. Services that are being called by that user determine how they "
+"interpret the set of roles a user has and to which operations or resources "
+"each role grants access."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts.xml114(para)
+msgid "The following diagram shows the OpenStack Identity process flow:"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml7(title)
+msgid "Features and benefits"
+msgstr "Traits et avantages"
+
+#: ./doc/common/section_objectstorage-features.xml12(th)
+msgid "Features"
+msgstr "Traits"
+
+#: ./doc/common/section_objectstorage-features.xml13(th)
+msgid "Benefits"
+msgstr "Avantages"
+
+#: ./doc/common/section_objectstorage-features.xml18(emphasis)
+msgid "Leverages commodity hardware"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml19(td)
+msgid "No lock-in, lower price/GB."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml22(emphasis)
+msgid "HDD/node failure agnostic"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml23(td)
+msgid "Self-healing, reliable, data redundancy protects from failures."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml27(emphasis)
+msgid "Unlimited storage"
+msgstr "Stockage illimité"
+
+#: ./doc/common/section_objectstorage-features.xml28(td)
+msgid ""
+"Large and flat namespace, highly scalable read/write access, able to serve "
+"content directly from storage system."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml32(emphasis)
+msgid "Multi-dimensional scalability"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml34(td)
+msgid ""
+"Scale-out architecture: Scale vertically and horizontally-distributed "
+"storage. Backs up and archives large amounts of data with linear "
+"performance."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml39(emphasis)
+msgid "Account/container/object structure"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml40(td)
+msgid ""
+"No nesting, not a traditional file system: Optimized for scale, it scales to"
+" multiple petabytes and billions of objects."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml45(emphasis)
+msgid "Built-in replication 3✕ + data redundancy (compared with 2✕ on RAID)"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml48(td)
+msgid ""
+"A configurable number of accounts, containers and object copies for high "
+"availability."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml52(emphasis)
+msgid "Easily add capacity (unlike RAID resize)"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml54(td)
+msgid "Elastic data scaling with ease"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml57(emphasis)
+msgid "No central database"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml58(td)
+msgid "Higher performance, no bottlenecks"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml61(emphasis)
+msgid "RAID not required"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml62(td)
+msgid "Handle many small, random reads and writes efficiently"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml65(emphasis)
+msgid "Built-in management utilities"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml66(td)
+msgid ""
+"Account management: Create, add, verify, and delete users; Container "
+"management: Upload, download, and verify; Monitoring: Capacity, host, "
+"network, log trawling, and cluster health."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml72(emphasis)
+msgid "Drive auditing"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml73(td)
+msgid "Detect drive failures preempting data corruption"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml76(emphasis)
+msgid "Expiring objects"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml77(td)
+msgid ""
+"Users can set an expiration time or a TTL on an object to control access"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml81(emphasis)
+msgid "Direct object access"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml82(td)
+msgid "Enable direct browser access to content, such as for a control panel"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml86(emphasis)
+msgid "Realtime visibility into client requests"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml88(td)
+msgid "Know what users are requesting."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml91(emphasis)
+msgid "Supports S3 API"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml92(td)
+msgid "Utilize tools that were designed for the popular S3 API."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml96(emphasis)
+msgid "Restrict containers per account"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml98(td)
+msgid "Limit access to control usage by user."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml101(emphasis)
+msgid "Support for NetApp, Nexenta, SolidFire"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml103(td)
+msgid "Unified support for block volumes using a variety of storage systems."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml107(emphasis)
+msgid "Snapshot and backup API for block volumes"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml109(td)
+msgid "Data protection and recovery for VM data."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml112(emphasis)
+msgid "Standalone volume API available"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml114(td)
+msgid "Separate endpoint and API for integration with other compute systems."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml118(emphasis)
+msgid "Integration with Compute"
+msgstr "Intégration avec calcul"
+
+#: ./doc/common/section_objectstorage-features.xml120(td)
+msgid ""
+"Fully integrated with Compute for attaching block volumes and reporting on "
+"usage."
+msgstr ""
 
 #: ./doc/common/section_dashboard_sessions.xml6(title)
 msgid "Set up session storage for the dashboard"
@@ -24747,837 +24776,4510 @@ msgid ""
 "cookie-based-sessions\">cookie-based sessions</link> documentation."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml6(title)
-msgid "Troubleshoot Object Storage"
-msgstr ""
+#: ./doc/common/section_kvm_enable.xml6(title)
+msgid "Enable KVM"
+msgstr "Activer KVM"
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml7(para)
+#: ./doc/common/section_kvm_enable.xml7(para)
 msgid ""
-"For Object Storage, everything is logged in "
-"<filename>/var/log/syslog</filename> (or messages on some distros). Several "
-"settings enable further customization of logging, such as "
-"<literal>log_name</literal>, <literal>log_facility</literal>, and "
-"<literal>log_level</literal>, within the object server configuration files."
+"To perform these steps, you must be logged in as the "
+"<systemitem>root</systemitem> user."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml11(title)
-msgid "Drive failure"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-troubleshoot.xml12(para)
+#: ./doc/common/section_kvm_enable.xml11(para)
 msgid ""
-"In the event that a drive has failed, the first step is to make sure the "
-"drive is unmounted. This will make it easier for Object Storage to work "
-"around the failure until it has been resolved. If the drive is going to be "
-"replaced immediately, then it is just best to replace the drive, format it, "
-"remount it, and let replication fill it up."
+"To determine whether the <literal>svm</literal> or <literal>vmx</literal> "
+"CPU extensions are present, run this command:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml16(para)
+#: ./doc/common/section_kvm_enable.xml15(para)
 msgid ""
-"If the drive can’t be replaced immediately, then it is best to leave it "
-"unmounted, and remove the drive from the ring. This will allow all the "
-"replicas that were on that drive to be replicated elsewhere until the drive "
-"is replaced. Once the drive is replaced, it can be re-added to the ring."
+"This command generates output if the CPU is hardware-virtualization capable."
+" Even if output is shown, you might still need to enable virtualization in "
+"the system BIOS for full support."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml20(para)
+#: ./doc/common/section_kvm_enable.xml19(para)
 msgid ""
-"You can look at error messages in <filename>/var/log/kern.log</filename> for"
-" hints of drive failure."
+"If no output appears, consult your system documentation to ensure that your "
+"CPU and motherboard support hardware virtualization. Verify that any "
+"relevant hardware virtualization options are enabled in the system BIOS."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml23(title)
-msgid "Server failure"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-troubleshoot.xml24(para)
+#: ./doc/common/section_kvm_enable.xml24(para)
 msgid ""
-"If a server is having hardware issues, it is a good idea to make sure the "
-"Object Storage services are not running. This will allow Object Storage to "
-"work around the failure while you troubleshoot."
+"The BIOS for each manufacturer is different. If you must enable "
+"virtualization in the BIOS, look for an option containing the words "
+"<literal>virtualization</literal>, <literal>VT</literal>, "
+"<literal>VMX</literal>, or <literal>SVM</literal>."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml27(para)
+#: ./doc/common/section_kvm_enable.xml32(para)
 msgid ""
-"If the server just needs a reboot, or a small amount of work that should "
-"only last a couple of hours, then it is probably best to let Object Storage "
-"work around the failure and get the machine fixed and back online. When the "
-"machine comes back online, replication will make sure that anything that is "
-"missing during the downtime will get updated."
+"To list the loaded kernel modules and verify that the <literal>kvm</literal>"
+" modules are loaded, run this command:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml32(para)
+#: ./doc/common/section_kvm_enable.xml36(para)
 msgid ""
-"If the server has more serious issues, then it is probably best to remove "
-"all of the server’s devices from the ring. Once the server has been repaired"
-" and is back online, the server’s devices can be added back into the ring. "
-"It is important that the devices are reformatted before putting them back "
-"into the ring as it is likely to be responsible for a different set of "
-"partitions than before."
+"If the output includes <systemitem>kvm_intel</systemitem> or "
+"<systemitem>kvm_amd</systemitem>, the <systemitem>kvm</systemitem> hardware "
+"virtualization modules are loaded and your kernel meets the module "
+"requirements for OpenStack Compute."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml40(title)
-msgid "Detect failed drives"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-troubleshoot.xml41(para)
+#: ./doc/common/section_kvm_enable.xml43(para)
 msgid ""
-"It has been our experience that when a drive is about to fail, error "
-"messages will spew into /var/log/kern.log. There is a script called swift-"
-"drive-audit that can be run via cron to watch for bad drives. If errors are "
-"detected, it will unmount the bad drive, so that Object Storage can work "
-"around it. The script takes a configuration file with the following "
-"settings:"
+"If the output does not show that the <literal>kvm</literal> module is "
+"loaded, run this command to load it:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml47(para)
+#: ./doc/common/section_kvm_enable.xml47(para)
+msgid "Run the command for your CPU. For Intel, run this command:"
+msgstr ""
+
+#: ./doc/common/section_kvm_enable.xml50(para)
+msgid "For AMD, run this command:"
+msgstr "Pour AMD, exécutez cette commande:"
+
+#: ./doc/common/section_kvm_enable.xml52(para)
 msgid ""
-"This script has only been tested on Ubuntu 10.04, so if you are using a "
-"different distro or OS, some care should be taken before using in "
-"production."
+"Because a KVM installation can change user group membership, you might need "
+"to log in again for changes to take effect."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml52(title)
-msgid "Emergency recovery of ring builder files"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-troubleshoot.xml53(para)
+#: ./doc/common/section_kvm_enable.xml55(para)
 msgid ""
-"You should always keep a backup of swift ring builder files. However, if an "
-"emergency occurs, this procedure may assist in returning your cluster to an "
-"operational state."
+"If the kernel modules do not load automatically, use the procedures listed "
+"in these subsections."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml56(para)
+#: ./doc/common/section_kvm_enable.xml59(para)
 msgid ""
-"Using existing swift tools, there is no way to recover a builder file from a"
-" <filename>ring.gz</filename> file. However, if you have a knowledge of "
-"Python, it is possible to construct a builder file that is pretty close to "
-"the one you have lost. The following is what you will need to do."
+"If the checks indicate that required hardware virtualization support or "
+"kernel modules are disabled or unavailable, you must either enable this "
+"support on the system or find a system with this support."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml61(para)
+#: ./doc/common/section_kvm_enable.xml64(para)
 msgid ""
-"This procedure is a last-resort for emergency circumstances. It requires "
-"knowledge of the swift python code and may not succeed."
+"Some systems require that you enable VT support in the system BIOS. If you "
+"believe your processor supports hardware acceleration but the previous "
+"command did not produce output, reboot your machine, enter the system BIOS, "
+"and enable the VT option."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml64(para)
-msgid "First, load the ring and a new ringbuilder object in a Python REPL:"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-troubleshoot.xml67(para)
-msgid "Now, start copying the data we have in the ring into the builder."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-troubleshoot.xml84(para)
+#: ./doc/common/section_kvm_enable.xml70(para)
 msgid ""
-"This is the extent of the recoverable fields. For "
-"<literal>min_part_hours</literal> you'll either have to remember what the "
-"value you used was, or just make up a new one."
-msgstr ""
+"If KVM acceleration is not supported, configure Compute to use a different "
+"hypervisor, such as <link href=\"http://docs.openstack.org/trunk/config-"
+"reference/content/qemu.html\">QEMU</link> or <link "
+"href=\"http://docs.openstack.org/trunk/config-reference/content"
+"/introduction-to-xen.html\">Xen</link>."
+msgstr "Dans le cas où l'accélération KVM n'est pas supportée, Compute devra être configuré pour utiliser un autre hyperviseur comme <link href=\"http://docs.openstack.org/trunk/config-reference/content/qemu.html\">QEMU</link> ou <link href=\"http://docs.openstack.org/trunk/config-reference/content/introduction-to-xen.html\">Xen</link>."
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml89(para)
+#: ./doc/common/section_kvm_enable.xml76(para)
 msgid ""
-"Try some validation: if this doesn't raise an exception, you may feel some "
-"hope. Not too much, though."
-msgstr ""
+"These procedures help you load the kernel modules for Intel-based and AMD-"
+"based processors if they do not load automatically during KVM installation."
+msgstr "Ces procédures décrit comment charger les modules de noyau pour les processeurs Intel et AMD, s'ils n'ont pas été chargés automatiquement par le processus d'installation de KVM de votre distribution."
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml92(para)
-msgid "Save the builder."
-msgstr "Enregistrer le générateur."
+#: ./doc/common/section_kvm_enable.xml80(title)
+msgid "Intel-based processors"
+msgstr "Processeurs Intel"
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml96(para)
+#: ./doc/common/section_kvm_enable.xml81(para)
 msgid ""
-"You should now have a file called 'account.builder' in the current working "
-"directory. Next, run <literal>swift-ring-builder account.builder "
-"write_ring</literal> and compare the new account.ring.gz to the "
-"account.ring.gz that you started from. They probably won't be byte-for-byte "
-"identical, but if you load them up in a REPL and their "
-"<literal>_replica2part2dev_id</literal> and <literal>devs</literal> "
-"attributes are the same (or nearly so), then you're in good shape."
-msgstr ""
+"If your compute host is Intel-based, run these commands as root to load the "
+"kernel modules:"
+msgstr "Si votre ordinateur hôte est basé sur Intel, lancez en tant qu'utilisateur root les modules de noyau : "
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml103(para)
+#: ./doc/common/section_kvm_enable.xml85(para)
 msgid ""
-"Next, repeat the procedure for <filename>container.ring.gz</filename> and "
-"<filename>object.ring.gz</filename>, and you might get usable builder files."
+"Add these lines to the <filename>/etc/modules</filename> file so that these "
+"modules load on reboot:"
+msgstr "Ajoutez les lignes suivantes à <filename>/etc/modules</filename> pour que ces modules soient chargés au redémarrage :"
+
+#: ./doc/common/section_kvm_enable.xml91(title)
+msgid "AMD-based processors"
+msgstr "Processeurs AMD"
+
+#: ./doc/common/section_kvm_enable.xml92(para)
+msgid ""
+"If your compute host is AMD-based, run these commands as root to load the "
+"kernel modules:"
+msgstr "Si votre ordinateur hôte est basé sur AMD, lancez en tant qu'utilisateur root les modules de noyau : "
+
+#: ./doc/common/section_kvm_enable.xml96(para)
+msgid ""
+"Add these lines to <filename>/etc/modules</filename> file so that these "
+"modules load on reboot:"
+msgstr "Ajoutez les lignes suivantes à <filename>/etc/modules</filename> pour que ces modules soient chargés au redémarrage : "
+
+#: ./doc/common/tables/ceilometer-database.xml8(caption)
+#: ./doc/common/tables/cinder-database.xml8(caption)
+#: ./doc/common/tables/trove-database.xml8(caption)
+#: ./doc/common/tables/heat-database.xml8(caption)
+#: ./doc/common/tables/keystone-database.xml8(caption)
+msgid "Description of configuration options for database"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml8(caption)
-#: ./doc/common/tables/ceilometer-cells.xml8(caption)
-msgid "Description of configuration options for cells"
-msgstr "Description des options de configuration pour les cellules"
-
-#: ./doc/common/tables/nova-cells.xml13(th)
-#: ./doc/common/tables/trove-db_mongodb.xml13(th)
-#: ./doc/common/tables/keystone-debug.xml13(th)
-#: ./doc/common/tables/glance-policy.xml13(th)
-#: ./doc/common/tables/neutron-mlnx.xml13(th)
-#: ./doc/common/tables/nova-ipv6.xml13(th)
-#: ./doc/common/tables/cinder-eqlx.xml13(th)
-#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml12(th)
-#: ./doc/common/tables/swift-object-expirer-filter-cache.xml12(th)
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml12(th)
-#: ./doc/common/tables/nova-rpc_all.xml13(th)
-#: ./doc/common/tables/neutron-ml2_l2pop.xml13(th)
-#: ./doc/common/tables/glance-qpid.xml13(th)
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml12(th)
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml13(th)
-#: ./doc/common/tables/neutron-ml2_gre.xml13(th)
-#: ./doc/common/tables/nova-volumes.xml13(th)
-#: ./doc/common/tables/glance-gridfs.xml13(th)
-#: ./doc/common/tables/neutron-ml2_arista.xml13(th)
-#: ./doc/common/tables/glance-filesystem.xml13(th)
-#: ./doc/common/tables/heat-redis.xml13(th)
-#: ./doc/common/tables/trove-logging.xml13(th)
-#: ./doc/common/tables/swift-container-server-container-updater.xml12(th)
-#: ./doc/common/tables/cinder-storage_gpfs.xml13(th)
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml13(th)
-#: ./doc/common/tables/nova-tilera.xml13(th)
-#: ./doc/common/tables/nova-ca.xml13(th)
-#: ./doc/common/tables/heat-clients_nova.xml13(th)
-#: ./doc/common/tables/swift-account-server-filter-recon.xml12(th)
-#: ./doc/common/tables/cinder-huawei.xml13(th)
-#: ./doc/common/tables/keystone-qpid.xml13(th)
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml13(th)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml12(th)
-#: ./doc/common/tables/nova-glance.xml13(th)
-#: ./doc/common/tables/neutron-dhcp_agent.xml13(th)
-#: ./doc/common/tables/nova-neutron.xml13(th)
-#: ./doc/common/tables/cinder-backups_ceph.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml12(th)
-#: ./doc/common/tables/nova-metadata.xml13(th)
-#: ./doc/common/tables/glance-s3.xml13(th)
-#: ./doc/common/tables/glance-auth_token.xml13(th)
-#: ./doc/common/tables/neutron-kombu.xml13(th)
-#: ./doc/common/tables/trove-redis.xml13(th)
-#: ./doc/common/tables/trove-qpid.xml13(th)
-#: ./doc/common/tables/trove-compute.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml12(th)
-#: ./doc/common/tables/trove-nova.xml13(th)
-#: ./doc/common/tables/ceilometer-cells.xml13(th)
-#: ./doc/common/tables/keystone-oauth.xml13(th)
-#: ./doc/common/tables/cinder-block-device.xml13(th)
-#: ./doc/common/tables/cinder-zones.xml13(th)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml13(th)
-#: ./doc/common/tables/swift-container-server-container-sync.xml12(th)
-#: ./doc/common/tables/neutron-common.xml13(th)
-#: ./doc/common/tables/neutron-compute.xml13(th)
-#: ./doc/common/tables/swift-object-server-object-auditor.xml12(th)
-#: ./doc/common/tables/keystone-ldap.xml13(th)
-#: ./doc/common/tables/heat-rpc.xml13(th)
-#: ./doc/common/tables/neutron-openvswitch_agent.xml13(th)
-#: ./doc/common/tables/cinder-compute.xml13(th)
-#: ./doc/common/tables/keystone-identity.xml13(th)
-#: ./doc/common/tables/cinder-lvm.xml13(th)
-#: ./doc/common/tables/keystone-trust.xml13(th)
-#: ./doc/common/tables/cinder-storage_nfs.xml13(th)
-#: ./doc/common/tables/neutron-plumgrid.xml13(th)
-#: ./doc/common/tables/heat-cfn_api.xml13(th)
-#: ./doc/common/tables/nova-hypervisor.xml13(th)
-#: ./doc/common/tables/trove-rabbitmq.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml12(th)
-#: ./doc/common/tables/trove-api.xml13(th)
-#: ./doc/common/tables/cinder-quota.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml12(th)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml12(th)
-#: ./doc/common/tables/nova-console.xml13(th)
-#: ./doc/common/tables/ceilometer-events.xml13(th)
-#: ./doc/common/tables/keystone-os_inherit.xml13(th)
-#: ./doc/common/tables/heat-clients.xml13(th)
-#: ./doc/common/tables/heat-notification.xml13(th)
-#: ./doc/common/tables/keystone-assignment.xml13(th)
-#: ./doc/common/tables/nova-common.xml13(th)
-#: ./doc/common/tables/swift-object-server-object-updater.xml12(th)
-#: ./doc/common/tables/glance-zmq.xml13(th)
-#: ./doc/common/tables/neutron-metering_agent.xml13(th)
-#: ./doc/common/tables/trove-taskmanager.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml12(th)
-#: ./doc/common/tables/keystone-zeromq.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml12(th)
-#: ./doc/common/tables/nova-keymgr.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml12(th)
-#: ./doc/common/tables/neutron-api.xml13(th)
-#: ./doc/common/tables/ceilometer-redis.xml13(th)
-#: ./doc/common/tables/ceilometer-swift.xml13(th)
-#: ./doc/common/tables/cinder-hplefthand.xml13(th)
-#: ./doc/common/tables/heat-qpid.xml13(th)
-#: ./doc/common/tables/nova-testing.xml13(th)
-#: ./doc/common/tables/cinder-backups.xml13(th)
-#: ./doc/common/tables/swift-container-server-pipeline-main.xml12(th)
-#: ./doc/common/tables/neutron-ml2_ofa.xml13(th)
-#: ./doc/common/tables/trove-debug.xml13(th)
-#: ./doc/common/tables/swift-rsyncd-object.xml12(th)
-#: ./doc/common/tables/nova-s3.xml13(th)
-#: ./doc/common/tables/nova-zookeeper.xml13(th)
-#: ./doc/common/tables/cinder-rpc.xml13(th)
-#: ./doc/common/tables/cinder-api.xml13(th)
-#: ./doc/common/tables/cinder-windows.xml13(th)
-#: ./doc/common/tables/glance-vmware.xml13(th)
-#: ./doc/common/tables/swift-object-server-pipeline-main.xml12(th)
-#: ./doc/common/tables/trove-backup.xml13(th)
-#: ./doc/common/tables/nova-auth_token.xml13(th)
-#: ./doc/common/tables/cinder-san.xml13(th)
-#: ./doc/common/tables/swift-account-server-app-account-server.xml12(th)
-#: ./doc/common/tables/keystone-rpc.xml13(th)
-#: ./doc/common/tables/cinder-keymgr.xml13(th)
-#: ./doc/common/tables/nova-db.xml13(th)
-#: ./doc/common/tables/neutron-ml2_vxlan.xml13(th)
-#: ./doc/common/tables/glance-logging.xml13(th)
-#: ./doc/common/tables/cinder-zoning.xml13(th)
-#: ./doc/common/tables/glance-wsgi.xml13(th)
-#: ./doc/common/tables/nova-periodic.xml13(th)
-#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml12(th)
-#: ./doc/common/tables/cinder-images.xml13(th)
-#: ./doc/common/tables/trove-swift.xml13(th)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml12(th)
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml12(th)
-#: ./doc/common/tables/cinder-auth_token.xml13(th)
-#: ./doc/common/tables/heat-crypt.xml13(th)
-#: ./doc/common/tables/neutron-wsgi.xml13(th)
-#: ./doc/common/tables/neutron-scheduler.xml13(th)
-#: ./doc/common/tables/keystone-security.xml13(th)
-#: ./doc/common/tables/ceilometer-vmware.xml13(th)
-#: ./doc/common/tables/glance-rbd.xml13(th)
-#: ./doc/common/tables/heat-clients_heat.xml13(th)
-#: ./doc/common/tables/heat-rabbitmq.xml13(th)
-#: ./doc/common/tables/ceilometer-logging.xml13(th)
-#: ./doc/common/tables/neutron-metadata.xml13(th)
-#: ./doc/common/tables/glance-redis.xml13(th)
-#: ./doc/common/tables/keystone-stats.xml13(th)
-#: ./doc/common/tables/cinder-hp3par.xml13(th)
-#: ./doc/common/tables/cinder-storage_ceph.xml13(th)
-#: ./doc/common/tables/nova-livemigration.xml13(th)
-#: ./doc/common/tables/nova-ldap.xml13(th)
-#: ./doc/common/tables/nova-fping.xml13(th)
-#: ./doc/common/tables/heat-clients_swift.xml13(th)
-#: ./doc/common/tables/neutron-securitygroups.xml13(th)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml13(th)
-#: ./doc/common/tables/nova-ec2.xml13(th)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml12(th)
-#: ./doc/common/tables/trove-zeromq.xml13(th)
-#: ./doc/common/tables/heat-database.xml13(th)
-#: ./doc/common/tables/keystone-catalog.xml13(th)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml12(th)
-#: ./doc/common/tables/cinder-rootwrap.xml13(th)
 #: ./doc/common/tables/ceilometer-database.xml13(th)
-#: ./doc/common/tables/heat-debug.xml13(th)
-#: ./doc/common/tables/cinder-nexenta_nfs.xml13(th)
-#: ./doc/common/tables/trove-auth_token.xml13(th)
-#: ./doc/common/tables/heat-waitcondition_api.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml12(th)
-#: ./doc/common/tables/neutron-ml2_vlan.xml13(th)
-#: ./doc/common/tables/nova-policy.xml13(th)
-#: ./doc/common/tables/keystone-amqp.xml13(th)
-#: ./doc/common/tables/neutron-logging.xml13(th)
-#: ./doc/common/tables/trove-db_cassandra.xml13(th)
+#: ./doc/common/tables/neutron-openvswitch_agent.xml13(th)
+#: ./doc/common/tables/heat-clients.xml13(th)
+#: ./doc/common/tables/cinder-solidfire.xml13(th)
+#: ./doc/common/tables/neutron-rpc.xml13(th)
+#: ./doc/common/tables/trove-db_percona.xml13(th)
+#: ./doc/common/tables/nova-periodic.xml13(th)
+#: ./doc/common/tables/keystone-auth.xml13(th)
+#: ./doc/common/tables/keystone-policy.xml13(th)
+#: ./doc/common/tables/glance-auth_token.xml13(th)
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml13(th)
+#: ./doc/common/tables/swift-container-server-container-sync.xml12(th)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml12(th)
+#: ./doc/common/tables/cinder-zoning_fabric.xml13(th)
+#: ./doc/common/tables/ceilometer-redis.xml13(th)
+#: ./doc/common/tables/cinder-storage_ceph.xml13(th)
+#: ./doc/common/tables/ceilometer-vmware.xml13(th)
+#: ./doc/common/tables/neutron-cisco.xml13(th)
+#: ./doc/common/tables/nova-testing.xml13(th)
+#: ./doc/common/tables/nova-metadata.xml13(th)
+#: ./doc/common/tables/heat-clients_nova.xml13(th)
+#: ./doc/common/tables/cinder-hp3par.xml13(th)
+#: ./doc/common/tables/keystone-misc.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml12(th)
+#: ./doc/common/tables/neutron-scheduler.xml13(th)
+#: ./doc/common/tables/glance-rbd.xml13(th)
+#: ./doc/common/tables/cinder-storage_xen.xml13(th)
+#: ./doc/common/tables/ceilometer-common.xml13(th)
+#: ./doc/common/tables/cinder-database.xml13(th)
+#: ./doc/common/tables/ceilometer-logging.xml13(th)
+#: ./doc/common/tables/heat-common.xml13(th)
+#: ./doc/common/tables/nova-ipv6.xml13(th)
+#: ./doc/common/tables/nova-vnc.xml13(th)
+#: ./doc/common/tables/trove-qpid.xml13(th)
+#: ./doc/common/tables/keystone-api.xml13(th)
+#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml12(th)
+#: ./doc/common/tables/swift-container-server-container-auditor.xml12(th)
 #: ./doc/common/tables/glance-rpc.xml13(th)
-#: ./doc/common/tables/nova-authentication.xml13(th)
+#: ./doc/common/tables/neutron-policy.xml13(th)
+#: ./doc/common/tables/nova-spice.xml13(th)
+#: ./doc/common/tables/heat-clients_heat.xml13(th)
+#: ./doc/common/tables/nova-xen.xml13(th)
+#: ./doc/common/tables/trove-amqp.xml13(th)
+#: ./doc/common/tables/glance-matchmaker.xml13(th)
+#: ./doc/common/tables/nova-rabbitmq.xml13(th)
+#: ./doc/common/tables/neutron-ml2_cisco.xml13(th)
+#: ./doc/common/tables/nova-policy.xml13(th)
+#: ./doc/common/tables/keystone-identity.xml13(th)
+#: ./doc/common/tables/ceilometer-inspector.xml13(th)
+#: ./doc/common/tables/cinder-scheduler.xml13(th)
+#: ./doc/common/tables/trove-db_cassandra.xml13(th)
+#: ./doc/common/tables/neutron-logging.xml13(th)
+#: ./doc/common/tables/nova-availabilityzones.xml13(th)
+#: ./doc/common/tables/keystone-catalog.xml13(th)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml13(th)
+#: ./doc/common/tables/neutron-rootwrap.xml13(th)
+#: ./doc/common/tables/cinder-auth.xml13(th)
+#: ./doc/common/tables/swift-swift-swift-constraints.xml12(th)
+#: ./doc/common/tables/heat-qpid.xml13(th)
+#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml12(th)
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml12(th)
+#: ./doc/common/tables/nova-zookeeper.xml13(th)
+#: ./doc/common/tables/nova-keymgr.xml13(th)
+#: ./doc/common/tables/neutron-auth_token.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml12(th)
+#: ./doc/common/tables/nova-ldap.xml13(th)
+#: ./doc/common/tables/swift-container-server-filter-recon.xml12(th)
+#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml12(th)
+#: ./doc/common/tables/ceilometer-auth.xml13(th)
+#: ./doc/common/tables/cinder-quota.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml12(th)
+#: ./doc/common/tables/keystone-os_inherit.xml13(th)
+#: ./doc/common/tables/neutron-sdnve.xml13(th)
+#: ./doc/common/tables/nova-compute.xml13(th)
+#: ./doc/common/tables/keystone-rabbit.xml13(th)
+#: ./doc/common/tables/cinder-backups_ceph.xml13(th)
+#: ./doc/common/tables/nova-vmware.xml13(th)
+#: ./doc/common/tables/heat-cfn_api.xml13(th)
+#: ./doc/common/tables/neutron-vmware.xml13(th)
+#: ./doc/common/tables/nova-rdp.xml13(th)
+#: ./doc/common/tables/keystone-assignment.xml13(th)
+#: ./doc/common/tables/nova-zeromq.xml13(th)
+#: ./doc/common/tables/cinder-storage.xml13(th)
+#: ./doc/common/tables/glance-registry.xml13(th)
+#: ./doc/common/tables/neutron-embrane.xml13(th)
+#: ./doc/common/tables/heat-quota.xml13(th)
+#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml12(th)
+#: ./doc/common/tables/nova-common.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml12(th)
+#: ./doc/common/tables/nova-volumes.xml13(th)
+#: ./doc/common/tables/neutron-redis.xml13(th)
+#: ./doc/common/tables/trove-db_mysql.xml13(th)
+#: ./doc/common/tables/heat-zeromq.xml13(th)
+#: ./doc/common/tables/heat-amqp.xml13(th)
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml13(th)
+#: ./doc/common/tables/nova-redis.xml13(th)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml12(th)
+#: ./doc/common/tables/nova-db.xml13(th)
+#: ./doc/common/tables/glance-rabbitmq.xml13(th)
+#: ./doc/common/tables/neutron-l3_agent.xml13(th)
+#: ./doc/common/tables/swift-container-server-pipeline-main.xml12(th)
+#: ./doc/common/tables/glance-policy.xml13(th)
+#: ./doc/common/tables/nova-neutron.xml13(th)
+#: ./doc/common/tables/cinder-backups.xml13(th)
+#: ./doc/common/tables/cinder-keymgr.xml13(th)
+#: ./doc/common/tables/ceilometer-cells.xml13(th)
+#: ./doc/common/tables/keystone-ldap.xml13(th)
+#: ./doc/common/tables/glance-vmware.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml12(th)
+#: ./doc/common/tables/cinder-zoning.xml13(th)
+#: ./doc/common/tables/heat-notification.xml13(th)
+#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml12(th)
+#: ./doc/common/tables/nova-vpn.xml13(th)
+#: ./doc/common/tables/neutron-vpn.xml13(th)
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml12(th)
+#: ./doc/common/tables/trove-common.xml13(th)
+#: ./doc/common/tables/trove-api.xml13(th)
+#: ./doc/common/tables/cinder-zadara.xml13(th)
+#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml12(th)
+#: ./doc/common/tables/nova-conductor.xml13(th)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml12(th)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml12(th)
+#: ./doc/common/tables/nova-livemigration.xml13(th)
+#: ./doc/common/tables/heat-rabbitmq.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml12(th)
+#: ./doc/common/tables/neutron-cadf.xml13(th)
+#: ./doc/common/tables/keystone-amqp.xml13(th)
+#: ./doc/common/tables/keystone-rpc.xml13(th)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml12(th)
+#: ./doc/common/tables/cinder-zones.xml13(th)
+#: ./doc/common/tables/cinder-scality.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml12(th)
+#: ./doc/common/tables/neutron-agent.xml13(th)
+#: ./doc/common/tables/cinder-emc.xml13(th)
 #: ./doc/common/tables/cinder-vmware.xml13(th)
-#: ./doc/common/tables/glance-sheepdog.xml13(th)
-#: ./doc/common/tables/heat-logging.xml13(th)
-#: ./doc/common/tables/keystone-notification.xml13(th)
-#: ./doc/common/tables/neutron-qpid.xml13(th)
-#: ./doc/common/tables/neutron-hyperv_agent.xml13(th)
+#: ./doc/common/tables/neutron-ml2_flat.xml13(th)
+#: ./doc/common/tables/heat-metadata_api.xml13(th)
+#: ./doc/common/tables/trove-rabbitmq.xml13(th)
+#: ./doc/common/tables/nova-upgrade_levels.xml13(th)
+#: ./doc/common/tables/neutron-kombu.xml13(th)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml13(th)
+#: ./doc/common/tables/neutron-ml2_ofa.xml13(th)
+#: ./doc/common/tables/glance-api.xml13(th)
+#: ./doc/common/tables/heat-waitcondition_api.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml12(th)
+#: ./doc/common/tables/swift-rsyncd-container.xml12(th)
+#: ./doc/common/tables/cinder-storwize.xml13(th)
+#: ./doc/common/tables/cinder-hplefthand.xml13(th)
+#: ./doc/common/tables/glance-s3.xml13(th)
+#: ./doc/common/tables/nova-rootwrap.xml13(th)
+#: ./doc/common/tables/heat-loadbalancer.xml13(th)
+#: ./doc/common/tables/ceilometer-api.xml13(th)
+#: ./doc/common/tables/ceilometer-exchange.xml13(th)
+#: ./doc/common/tables/cinder-lvm.xml13(th)
+#: ./doc/common/tables/trove-dns.xml13(th)
+#: ./doc/common/tables/nova-cells.xml13(th)
+#: ./doc/common/tables/trove-volume.xml13(th)
+#: ./doc/common/tables/heat-auth_token.xml13(th)
+#: ./doc/common/tables/neutron-quotas.xml13(th)
+#: ./doc/common/tables/nova-auth_token.xml13(th)
+#: ./doc/common/tables/cinder-storage_nfs.xml13(th)
+#: ./doc/common/tables/heat-api.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml12(th)
+#: ./doc/common/tables/heat-clients_ceilometer.xml13(th)
+#: ./doc/common/tables/neutron-ryu.xml13(th)
+#: ./doc/common/tables/glance-logging.xml13(th)
+#: ./doc/common/tables/swift-rsyncd-account.xml12(th)
+#: ./doc/common/tables/neutron-metering_agent.xml13(th)
+#: ./doc/common/tables/neutron-zeromq.xml13(th)
+#: ./doc/common/tables/cinder-storage_glusterfs.xml13(th)
+#: ./doc/common/tables/cinder-common.xml13(th)
 #: ./doc/common/tables/glance-swift.xml13(th)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml12(th)
+#: ./doc/common/tables/trove-quota.xml13(th)
+#: ./doc/common/tables/cinder-auth_token.xml13(th)
+#: ./doc/common/tables/ceilometer-alarm.xml13(th)
+#: ./doc/common/tables/ceilometer-events.xml13(th)
+#: ./doc/common/tables/cinder-xiv.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml12(th)
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml13(th)
+#: ./doc/common/tables/nova-glance.xml13(th)
+#: ./doc/common/tables/keystone-auth_token.xml13(th)
+#: ./doc/common/tables/nova-s3.xml13(th)
+#: ./doc/common/tables/nova-pci.xml13(th)
+#: ./doc/common/tables/swift-account-server-filter-recon.xml12(th)
+#: ./doc/common/tables/heat-clients_cinder.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml12(th)
+#: ./doc/common/tables/keystone-revoke.xml13(th)
+#: ./doc/common/tables/cinder-api.xml13(th)
+#: ./doc/common/tables/trove-db_couchbase.xml13(th)
+#: ./doc/common/tables/heat-clients_trove.xml13(th)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml12(th)
+#: ./doc/common/tables/neutron-plumgrid.xml13(th)
+#: ./doc/common/tables/trove-heat.xml13(th)
+#: ./doc/common/tables/glance-sheepdog.xml13(th)
+#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml12(th)
+#: ./doc/common/tables/cinder-windows.xml13(th)
+#: ./doc/common/tables/cinder-san-solaris.xml13(th)
+#: ./doc/common/tables/neutron-nuage.xml13(th)
+#: ./doc/common/tables/keystone-zeromq.xml13(th)
 #: ./doc/common/tables/neutron-bigswitch.xml13(th)
-#: ./doc/common/tables/nova-libvirt.xml13(th)
+#: ./doc/common/tables/ceilometer-rpc.xml13(th)
+#: ./doc/common/tables/swift-container-server-container-updater.xml12(th)
+#: ./doc/common/tables/trove-db_mongodb.xml13(th)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml12(th)
+#: ./doc/common/tables/glance-filesystem.xml13(th)
+#: ./doc/common/tables/trove-rpc.xml13(th)
+#: ./doc/common/tables/ceilometer-swift.xml13(th)
+#: ./doc/common/tables/trove-backup.xml13(th)
+#: ./doc/common/tables/nova-network.xml13(th)
+#: ./doc/common/tables/glance-redis.xml13(th)
+#: ./doc/common/tables/keystone-ssl.xml13(th)
+#: ./doc/common/tables/nova-ca.xml13(th)
+#: ./doc/common/tables/neutron-dhcp_agent.xml13(th)
+#: ./doc/common/tables/ceilometer-collector.xml13(th)
+#: ./doc/common/tables/cinder-hds-hus.xml13(th)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml13(th)
+#: ./doc/common/tables/swift-swift-swift-hash.xml12(th)
+#: ./doc/common/tables/neutron-ml2_gre.xml13(th)
+#: ./doc/common/tables/neutron-varmour.xml13(th)
+#: ./doc/common/tables/heat-debug.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml12(th)
+#: ./doc/common/tables/nova-kombu.xml13(th)
+#: ./doc/common/tables/trove-guestagent.xml13(th)
+#: ./doc/common/tables/nova-qpid.xml13(th)
+#: ./doc/common/tables/glance-qpid.xml13(th)
+#: ./doc/common/tables/neutron-ml2_l2pop.xml13(th)
+#: ./doc/common/tables/glance-amqp.xml13(th)
+#: ./doc/common/tables/glance-zmq.xml13(th)
+#: ./doc/common/tables/neutron-embrane_lb.xml13(th)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml12(th)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml12(th)
+#: ./doc/common/tables/neutron-testing.xml13(th)
+#: ./doc/common/tables/swift-object-server-pipeline-main.xml12(th)
+#: ./doc/common/tables/swift-memcache-memcache.xml12(th)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml12(th)
+#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml12(th)
+#: ./doc/common/tables/trove-compute.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml12(th)
+#: ./doc/common/tables/swift-object-expirer-filter-cache.xml12(th)
+#: ./doc/common/tables/trove-db_redis.xml13(th)
+#: ./doc/common/tables/cinder-rpc.xml13(th)
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml12(th)
+#: ./doc/common/tables/cinder-hpmsa.xml13(th)
+#: ./doc/common/tables/nova-apiv3.xml13(th)
+#: ./doc/common/tables/keystone-oauth.xml13(th)
+#: ./doc/common/tables/cinder-storage_gpfs.xml13(th)
+#: ./doc/common/tables/neutron-ml2_vlan.xml13(th)
+#: ./doc/common/tables/keystone-notification.xml13(th)
+#: ./doc/common/tables/swift-object-server-object-auditor.xml12(th)
+#: ./doc/common/tables/trove-zeromq.xml13(th)
 #: ./doc/common/tables/neutron-lbaas.xml13(th)
 #: ./doc/common/tables/cinder-backups_swift.xml13(th)
-#: ./doc/common/tables/neutron-ml2_cisco.xml13(th)
-#: ./doc/common/tables/ceilometer-rpc.xml13(th)
-#: ./doc/common/tables/heat-loadbalancer.xml13(th)
-#: ./doc/common/tables/heat-cloudwatch_api.xml13(th)
-#: ./doc/common/tables/nova-pci.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml12(th)
-#: ./doc/common/tables/heat-clients_ceilometer.xml13(th)
-#: ./doc/common/tables/neutron-varmour.xml13(th)
-#: ./doc/common/tables/glance-imagecache.xml13(th)
-#: ./doc/common/tables/trove-quota.xml13(th)
-#: ./doc/common/tables/swift-rsyncd-account.xml12(th)
-#: ./doc/common/tables/cinder-storage.xml13(th)
-#: ./doc/common/tables/cinder-nas.xml13(th)
-#: ./doc/common/tables/nova-vpn.xml13(th)
-#: ./doc/common/tables/nova-wsgi.xml13(th)
-#: ./doc/common/tables/cinder-storage_glusterfs.xml13(th)
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml12(th)
-#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml12(th)
-#: ./doc/common/tables/nova-availabilityzones.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml12(th)
-#: ./doc/common/tables/heat-zeromq.xml13(th)
-#: ./doc/common/tables/keystone-memcache.xml13(th)
-#: ./doc/common/tables/nova-vnc.xml13(th)
-#: ./doc/common/tables/swift-swift-swift-constraints.xml12(th)
-#: ./doc/common/tables/neutron-cisco.xml13(th)
-#: ./doc/common/tables/keystone-logging.xml13(th)
-#: ./doc/common/tables/nova-hyperv.xml13(th)
-#: ./doc/common/tables/neutron-l3_agent.xml13(th)
-#: ./doc/common/tables/swift-object-server-filter-recon.xml12(th)
-#: ./doc/common/tables/cinder-coraid.xml13(th)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml12(th)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml12(th)
-#: ./doc/common/tables/nova-vmware.xml13(th)
-#: ./doc/common/tables/nova-logging.xml13(th)
-#: ./doc/common/tables/nova-xen.xml13(th)
-#: ./doc/common/tables/ceilometer-collector.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml12(th)
-#: ./doc/common/tables/keystone-ec2.xml13(th)
-#: ./doc/common/tables/keystone-auth.xml13(th)
-#: ./doc/common/tables/swift-memcache-memcache.xml12(th)
-#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml12(th)
-#: ./doc/common/tables/neutron-ml2.xml13(th)
-#: ./doc/common/tables/ceilometer-api.xml13(th)
-#: ./doc/common/tables/heat-clients_trove.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml12(th)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml13(th)
-#: ./doc/common/tables/glance-common.xml13(th)
-#: ./doc/common/tables/nova-network.xml13(th)
-#: ./doc/common/tables/cinder-scality.xml13(th)
-#: ./doc/common/tables/neutron-notifier.xml13(th)
-#: ./doc/common/tables/cinder-common.xml13(th)
-#: ./doc/common/tables/nova-trustedcomputing.xml13(th)
-#: ./doc/common/tables/neutron-ml2_flat.xml13(th)
-#: ./doc/common/tables/heat-clients_cinder.xml13(th)
-#: ./doc/common/tables/nova-configdrive.xml13(th)
-#: ./doc/common/tables/cinder-database.xml13(th)
-#: ./doc/common/tables/neutron-rpc.xml13(th)
-#: ./doc/common/tables/cinder-zoning_manager.xml13(th)
-#: ./doc/common/tables/trove-volume.xml13(th)
-#: ./doc/common/tables/keystone-cache.xml13(th)
-#: ./doc/common/tables/nova-zeromq.xml13(th)
-#: ./doc/common/tables/glance-testing.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml12(th)
-#: ./doc/common/tables/glance-registry.xml13(th)
-#: ./doc/common/tables/glance-amqp.xml13(th)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml12(th)
 #: ./doc/common/tables/trove-database.xml13(th)
-#: ./doc/common/tables/heat-clients_backends.xml13(th)
-#: ./doc/common/tables/heat-amqp.xml13(th)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml12(th)
-#: ./doc/common/tables/cinder-hpmsa.xml13(th)
-#: ./doc/common/tables/cinder-emc.xml13(th)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml12(th)
-#: ./doc/common/tables/neutron-fwaas.xml13(th)
-#: ./doc/common/tables/glance-rabbitmq.xml13(th)
-#: ./doc/common/tables/cinder-backups_tsm.xml13(th)
-#: ./doc/common/tables/neutron-sdnve.xml13(th)
-#: ./doc/common/tables/trove-db_mysql.xml13(th)
-#: ./doc/common/tables/nova-qpid.xml13(th)
-#: ./doc/common/tables/trove-rpc.xml13(th)
-#: ./doc/common/tables/cinder-connection.xml13(th)
-#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml12(th)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml12(th)
-#: ./doc/common/tables/trove-db_redis.xml13(th)
-#: ./doc/common/tables/ceilometer-qpid.xml13(th)
-#: ./doc/common/tables/neutron-zeromq.xml13(th)
-#: ./doc/common/tables/keystone-token.xml13(th)
-#: ./doc/common/tables/neutron-vpn.xml13(th)
-#: ./doc/common/tables/neutron-agent.xml13(th)
-#: ./doc/common/tables/neutron-ryu.xml13(th)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml12(th)
-#: ./doc/common/tables/trove-db_couchbase.xml13(th)
-#: ./doc/common/tables/neutron-policy.xml13(th)
-#: ./doc/common/tables/neutron-rootwrap.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml12(th)
-#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml12(th)
-#: ./doc/common/tables/trove-common.xml13(th)
-#: ./doc/common/tables/cinder-ssl.xml13(th)
-#: ./doc/common/tables/heat-api.xml13(th)
-#: ./doc/common/tables/trove-db_percona.xml13(th)
-#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml12(th)
-#: ./doc/common/tables/ceilometer-amqp.xml13(th)
-#: ./doc/common/tables/keystone-auth_token.xml13(th)
-#: ./doc/common/tables/neutron-meta.xml13(th)
-#: ./doc/common/tables/neutron-redis.xml13(th)
-#: ./doc/common/tables/neutron-ssl.xml13(th)
-#: ./doc/common/tables/ceilometer-exchange.xml13(th)
-#: ./doc/common/tables/ceilometer-common.xml13(th)
-#: ./doc/common/tables/ceilometer-alarm.xml13(th)
-#: ./doc/common/tables/keystone-misc.xml13(th)
-#: ./doc/common/tables/nova-scheduling.xml13(th)
-#: ./doc/common/tables/ceilometer-auth.xml13(th)
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml12(th)
-#: ./doc/common/tables/neutron-ml2_mlnx.xml13(th)
-#: ./doc/common/tables/swift-container-server-filter-recon.xml12(th)
-#: ./doc/common/tables/trove-dns.xml13(th)
-#: ./doc/common/tables/neutron-db.xml13(th)
-#: ./doc/common/tables/neutron-ml2_brocade.xml13(th)
-#: ./doc/common/tables/neutron-brocade.xml13(th)
-#: ./doc/common/tables/keystone-redis.xml13(th)
-#: ./doc/common/tables/heat-auth_token.xml13(th)
-#: ./doc/common/tables/keystone-database.xml13(th)
-#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml12(th)
-#: ./doc/common/tables/heat-clients_neutron.xml13(th)
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml13(th)
-#: ./doc/common/tables/cinder-xiv.xml13(th)
-#: ./doc/common/tables/cinder-hds-hus.xml13(th)
-#: ./doc/common/tables/neutron-rabbitmq.xml13(th)
-#: ./doc/common/tables/keystone-kvs.xml13(th)
-#: ./doc/common/tables/trove-ssl.xml13(th)
-#: ./doc/common/tables/keystone-policy.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml12(th)
-#: ./doc/common/tables/swift-swift-swift-hash.xml12(th)
-#: ./doc/common/tables/cinder-auth.xml13(th)
-#: ./doc/common/tables/nova-kombu.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml12(th)
-#: ./doc/common/tables/neutron-ml2_odl.xml13(th)
-#: ./doc/common/tables/heat-quota.xml13(th)
-#: ./doc/common/tables/nova-spice.xml13(th)
-#: ./doc/common/tables/cinder-zoning_fabric.xml13(th)
-#: ./doc/common/tables/neutron-midonet.xml13(th)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml12(th)
+#: ./doc/common/tables/nova-authentication.xml13(th)
 #: ./doc/common/tables/neutron-nvsd.xml13(th)
-#: ./doc/common/tables/neutron-embrane_lb.xml13(th)
-#: ./doc/common/tables/neutron-auth_token.xml13(th)
-#: ./doc/common/tables/cinder-storwize.xml13(th)
-#: ./doc/common/tables/nova-rootwrap.xml13(th)
-#: ./doc/common/tables/cinder-solidfire.xml13(th)
-#: ./doc/common/tables/keystone-revoke.xml13(th)
-#: ./doc/common/tables/glance-ssl.xml13(th)
-#: ./doc/common/tables/heat-metadata_api.xml13(th)
-#: ./doc/common/tables/nova-apiv3.xml13(th)
-#: ./doc/common/tables/glance-db.xml13(th)
-#: ./doc/common/tables/neutron-vmware.xml13(th)
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml12(th)
-#: ./doc/common/tables/nova-api.xml13(th)
-#: ./doc/common/tables/glance-matchmaker.xml13(th)
-#: ./doc/common/tables/keystone-ssl.xml13(th)
-#: ./doc/common/tables/swift-rsyncd-container.xml12(th)
-#: ./doc/common/tables/cinder-san-solaris.xml13(th)
-#: ./doc/common/tables/trove-heat.xml13(th)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml13(th)
-#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml12(th)
-#: ./doc/common/tables/glance-paste.xml13(th)
-#: ./doc/common/tables/nova-rdp.xml13(th)
-#: ./doc/common/tables/neutron-quotas.xml13(th)
-#: ./doc/common/tables/nova-rpc.xml13(th)
-#: ./doc/common/tables/trove-guestagent.xml13(th)
-#: ./doc/common/tables/nova-baremetal.xml13(th)
-#: ./doc/common/tables/heat-clients_keystone.xml13(th)
 #: ./doc/common/tables/swift-account-server-pipeline-main.xml12(th)
-#: ./doc/common/tables/keystone-rabbit.xml13(th)
-#: ./doc/common/tables/glance-api.xml13(th)
-#: ./doc/common/tables/cinder-scheduler.xml13(th)
-#: ./doc/common/tables/keystone-api.xml13(th)
-#: ./doc/common/tables/neutron-ml2_ncs.xml13(th)
-#: ./doc/common/tables/neutron-nec.xml13(th)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml13(th)
-#: ./doc/common/tables/neutron-cadf.xml13(th)
-#: ./doc/common/tables/neutron-testing.xml13(th)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml12(th)
-#: ./doc/common/tables/glance-cinder.xml13(th)
-#: ./doc/common/tables/nova-redis.xml13(th)
-#: ./doc/common/tables/neutron-embrane.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml12(th)
-#: ./doc/common/tables/nova-upgrade_levels.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml12(th)
-#: ./doc/common/tables/ceilometer-inspector.xml13(th)
-#: ./doc/common/tables/nova-rabbitmq.xml13(th)
-#: ./doc/common/tables/heat-common.xml13(th)
+#: ./doc/common/tables/glance-gridfs.xml13(th)
+#: ./doc/common/tables/neutron-notifier.xml13(th)
+#: ./doc/common/tables/nova-rpc_all.xml13(th)
+#: ./doc/common/tables/neutron-hyperv_agent.xml13(th)
 #: ./doc/common/tables/keystone-federation.xml13(th)
-#: ./doc/common/tables/cinder-zadara.xml13(th)
-#: ./doc/common/tables/neutron-nuage.xml13(th)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml12(th)
-#: ./doc/common/tables/ceilometer-ssl.xml13(th)
-#: ./doc/common/tables/nova-quota.xml13(th)
-#: ./doc/common/tables/nova-conductor.xml13(th)
-#: ./doc/common/tables/nova-compute.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml12(th)
-#: ./doc/common/tables/cinder-storage_xen.xml13(th)
+#: ./doc/common/tables/nova-scheduling.xml13(th)
+#: ./doc/common/tables/cinder-ssl.xml13(th)
+#: ./doc/common/tables/trove-ssl.xml13(th)
+#: ./doc/common/tables/cinder-eqlx.xml13(th)
+#: ./doc/common/tables/heat-redis.xml13(th)
+#: ./doc/common/tables/nova-ec2.xml13(th)
 #: ./doc/common/tables/keystone-credential.xml13(th)
-#: ./doc/common/tables/trove-amqp.xml13(th)
+#: ./doc/common/tables/cinder-block-device.xml13(th)
+#: ./doc/common/tables/neutron-metadata.xml13(th)
+#: ./doc/common/tables/nova-fping.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml12(th)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml12(th)
+#: ./doc/common/tables/neutron-ml2_ncs.xml13(th)
+#: ./doc/common/tables/neutron-ml2_arista.xml13(th)
+#: ./doc/common/tables/nova-trustedcomputing.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml12(th)
+#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml12(th)
+#: ./doc/common/tables/neutron-compute.xml13(th)
+#: ./doc/common/tables/glance-imagecache.xml13(th)
+#: ./doc/common/tables/neutron-ml2_brocade.xml13(th)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml12(th)
+#: ./doc/common/tables/cinder-nas.xml13(th)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml13(th)
+#: ./doc/common/tables/heat-clients_swift.xml13(th)
+#: ./doc/common/tables/keystone-logging.xml13(th)
+#: ./doc/common/tables/neutron-brocade.xml13(th)
+#: ./doc/common/tables/neutron-ml2_odl.xml13(th)
+#: ./doc/common/tables/swift-object-server-filter-recon.xml12(th)
+#: ./doc/common/tables/cinder-connection.xml13(th)
+#: ./doc/common/tables/heat-rpc.xml13(th)
+#: ./doc/common/tables/trove-taskmanager.xml13(th)
+#: ./doc/common/tables/heat-cloudwatch_api.xml13(th)
+#: ./doc/common/tables/cinder-images.xml13(th)
+#: ./doc/common/tables/cinder-huawei.xml13(th)
+#: ./doc/common/tables/nova-console.xml13(th)
+#: ./doc/common/tables/neutron-fwaas.xml13(th)
+#: ./doc/common/tables/cinder-nexenta_nfs.xml13(th)
+#: ./doc/common/tables/nova-quota.xml13(th)
+#: ./doc/common/tables/heat-logging.xml13(th)
+#: ./doc/common/tables/trove-redis.xml13(th)
+#: ./doc/common/tables/keystone-stats.xml13(th)
+#: ./doc/common/tables/heat-crypt.xml13(th)
+#: ./doc/common/tables/neutron-ssl.xml13(th)
+#: ./doc/common/tables/neutron-midonet.xml13(th)
+#: ./doc/common/tables/cinder-coraid.xml13(th)
+#: ./doc/common/tables/neutron-wsgi.xml13(th)
+#: ./doc/common/tables/cinder-compute.xml13(th)
+#: ./doc/common/tables/swift-rsyncd-object.xml12(th)
+#: ./doc/common/tables/glance-wsgi.xml13(th)
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml12(th)
+#: ./doc/common/tables/nova-baremetal.xml13(th)
+#: ./doc/common/tables/neutron-qpid.xml13(th)
+#: ./doc/common/tables/nova-rpc.xml13(th)
+#: ./doc/common/tables/cinder-backups_tsm.xml13(th)
+#: ./doc/common/tables/cinder-san.xml13(th)
+#: ./doc/common/tables/nova-logging.xml13(th)
+#: ./doc/common/tables/neutron-nec.xml13(th)
+#: ./doc/common/tables/keystone-security.xml13(th)
+#: ./doc/common/tables/heat-clients_neutron.xml13(th)
+#: ./doc/common/tables/nova-api.xml13(th)
+#: ./doc/common/tables/neutron-ml2_mlnx.xml13(th)
+#: ./doc/common/tables/trove-auth_token.xml13(th)
+#: ./doc/common/tables/keystone-trust.xml13(th)
+#: ./doc/common/tables/glance-cinder.xml13(th)
+#: ./doc/common/tables/swift-object-server-object-updater.xml12(th)
+#: ./doc/common/tables/glance-common.xml13(th)
+#: ./doc/common/tables/neutron-ml2_vxlan.xml13(th)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml12(th)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml12(th)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml12(th)
+#: ./doc/common/tables/trove-nova.xml13(th)
+#: ./doc/common/tables/neutron-meta.xml13(th)
+#: ./doc/common/tables/neutron-rabbitmq.xml13(th)
+#: ./doc/common/tables/keystone-ec2.xml13(th)
+#: ./doc/common/tables/heat-clients_keystone.xml13(th)
+#: ./doc/common/tables/neutron-api.xml13(th)
+#: ./doc/common/tables/trove-logging.xml13(th)
+#: ./doc/common/tables/glance-db.xml13(th)
+#: ./doc/common/tables/keystone-kvs.xml13(th)
+#: ./doc/common/tables/keystone-redis.xml13(th)
 #: ./doc/common/tables/nova-xvpnvncproxy.xml13(th)
+#: ./doc/common/tables/glance-paste.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml12(th)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml12(th)
+#: ./doc/common/tables/nova-hyperv.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml12(th)
+#: ./doc/common/tables/heat-clients_backends.xml13(th)
+#: ./doc/common/tables/glance-testing.xml13(th)
+#: ./doc/common/tables/neutron-common.xml13(th)
+#: ./doc/common/tables/nova-hypervisor.xml13(th)
+#: ./doc/common/tables/keystone-qpid.xml13(th)
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml12(th)
+#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml12(th)
+#: ./doc/common/tables/nova-wsgi.xml13(th)
+#: ./doc/common/tables/keystone-cache.xml13(th)
+#: ./doc/common/tables/nova-configdrive.xml13(th)
+#: ./doc/common/tables/keystone-token.xml13(th)
+#: ./doc/common/tables/ceilometer-ssl.xml13(th)
+#: ./doc/common/tables/ceilometer-qpid.xml13(th)
+#: ./doc/common/tables/heat-database.xml13(th)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml13(th)
+#: ./doc/common/tables/neutron-ml2.xml13(th)
+#: ./doc/common/tables/neutron-db.xml13(th)
+#: ./doc/common/tables/keystone-database.xml13(th)
+#: ./doc/common/tables/keystone-memcache.xml13(th)
+#: ./doc/common/tables/trove-debug.xml13(th)
+#: ./doc/common/tables/trove-swift.xml13(th)
+#: ./doc/common/tables/nova-tilera.xml13(th)
+#: ./doc/common/tables/nova-libvirt.xml13(th)
+#: ./doc/common/tables/neutron-mlnx.xml13(th)
+#: ./doc/common/tables/cinder-zoning_manager.xml13(th)
+#: ./doc/common/tables/ceilometer-amqp.xml13(th)
+#: ./doc/common/tables/glance-ssl.xml13(th)
+#: ./doc/common/tables/neutron-securitygroups.xml13(th)
+#: ./doc/common/tables/keystone-debug.xml13(th)
+#: ./doc/common/tables/cinder-rootwrap.xml13(th)
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml13(th)
 msgid "Configuration option = Default value"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml19(th)
-#: ./doc/common/tables/nova-rpc_all.xml198(th)
-#: ./doc/common/tables/ceilometer-cells.xml19(th)
-#: ./doc/common/tables/nova-db.xml26(th)
-#: ./doc/common/tables/nova-scheduling.xml118(th)
-#: ./doc/common/tables/nova-rpc.xml62(th)
-#: ./doc/common/tables/nova-upgrade_levels.xml19(th)
-#: ./doc/common/tables/nova-quota.xml82(th)
-msgid "[cells]"
-msgstr "[cells]"
-
-#: ./doc/common/tables/nova-cells.xml22(td)
-#: ./doc/common/tables/ceilometer-cells.xml26(td)
-msgid "call_timeout = 60"
+#: ./doc/common/tables/ceilometer-database.xml22(td)
+msgid "database_connection = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml23(td)
-#: ./doc/common/tables/ceilometer-cells.xml27(td)
-msgid "(IntOpt) Seconds to wait for response from a call to a cell."
+#: ./doc/common/tables/ceilometer-database.xml23(td)
+msgid "(StrOpt) DEPRECATED - Database connection string."
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml26(td)
-#: ./doc/common/tables/ceilometer-cells.xml30(td)
-msgid "capabilities = hypervisor=xenserver;kvm, os=linux;windows"
-msgstr "capabilities = hypervisor=xenserver;kvm, os=linux;windows"
-
-#: ./doc/common/tables/nova-cells.xml27(td)
-#: ./doc/common/tables/ceilometer-cells.xml31(td)
-msgid "(ListOpt) Key/Multi-value list with the capabilities of the cell"
+#: ./doc/common/tables/ceilometer-database.xml26(td)
+msgid "mysql_engine = InnoDB"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml30(td)
-#: ./doc/common/tables/ceilometer-cells.xml34(td)
-msgid "cell_type = compute"
-msgstr "cell_type = compute"
-
-#: ./doc/common/tables/nova-cells.xml31(td)
-#: ./doc/common/tables/ceilometer-cells.xml35(td)
-msgid "(StrOpt) Type of cell: api or compute"
+#: ./doc/common/tables/ceilometer-database.xml27(td)
+msgid "(StrOpt) MySQL engine to use."
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml34(td)
-msgid "cells_config = None"
-msgstr "cells_config = None"
+#: ./doc/common/tables/ceilometer-database.xml30(td)
+msgid "sqlite_db = ceilometer.sqlite"
+msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml35(td)
+#: ./doc/common/tables/ceilometer-database.xml31(td)
+#: ./doc/common/tables/nova-db.xml105(td)
+#: ./doc/common/tables/glance-db.xml87(td)
+#: ./doc/common/tables/neutron-db.xml23(td)
+#: ./doc/common/tables/keystone-database.xml87(td)
+msgid "(StrOpt) The file name to use with SQLite"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-database.xml34(td)
+#: ./doc/common/tables/nova-db.xml108(td)
+#: ./doc/common/tables/cinder-common.xml170(td)
+#: ./doc/common/tables/glance-db.xml90(td)
+#: ./doc/common/tables/heat-database.xml30(td)
+#: ./doc/common/tables/neutron-db.xml26(td)
+#: ./doc/common/tables/keystone-database.xml90(td)
+msgid "sqlite_synchronous = True"
+msgstr "sqlite_synchronous = True"
+
+#: ./doc/common/tables/ceilometer-database.xml35(td)
+#: ./doc/common/tables/nova-db.xml109(td)
+#: ./doc/common/tables/glance-db.xml91(td)
+#: ./doc/common/tables/neutron-db.xml27(td)
+#: ./doc/common/tables/keystone-database.xml91(td)
+msgid "(BoolOpt) If True, SQLite uses synchronous mode"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-database.xml41(td)
+#: ./doc/common/tables/cinder-storage.xml137(td)
+#: ./doc/common/tables/nova-db.xml36(td)
+#: ./doc/common/tables/glance-db.xml22(td)
+#: ./doc/common/tables/heat-database.xml37(td)
+#: ./doc/common/tables/neutron-db.xml33(td)
+#: ./doc/common/tables/keystone-database.xml22(td)
+msgid "backend = sqlalchemy"
+msgstr "backend = sqlalchemy"
+
+#: ./doc/common/tables/ceilometer-database.xml42(td)
+#: ./doc/common/tables/cinder-database.xml23(td)
+#: ./doc/common/tables/cinder-storage.xml138(td)
+#: ./doc/common/tables/nova-db.xml37(td)
+#: ./doc/common/tables/glance-db.xml23(td)
+#: ./doc/common/tables/heat-database.xml38(td)
+#: ./doc/common/tables/neutron-db.xml34(td)
+#: ./doc/common/tables/keystone-database.xml23(td)
+msgid "(StrOpt) The backend to use for db"
+msgstr "StrOpt)  Le backend à utiliser pour la base de données"
+
+#: ./doc/common/tables/ceilometer-database.xml45(td)
 msgid ""
-"(StrOpt) Configuration file from which to read cells configuration. If "
-"given, overrides reading cells from the database."
+"connection = sqlite:////usr/lib/python/site-"
+"packages/ceilometer/openstack/common/db/$sqlite_db"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml38(td)
-msgid "driver = nova.cells.rpc_driver.CellsRPCDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-cells.xml39(td)
-msgid "(StrOpt) Cells communication driver to use"
-msgstr ""
-
-#: ./doc/common/tables/nova-cells.xml42(td)
-#: ./doc/common/tables/ceilometer-cells.xml38(td)
-#: ./doc/common/tables/keystone-ssl.xml77(td)
-msgid "enable = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-cells.xml43(td)
-#: ./doc/common/tables/ceilometer-cells.xml39(td)
-msgid "(BoolOpt) Enable cell functionality"
-msgstr ""
-
-#: ./doc/common/tables/nova-cells.xml46(td)
-msgid "instance_update_num_instances = 1"
-msgstr "instance_update_num_instances = 1"
-
-#: ./doc/common/tables/nova-cells.xml47(td)
-msgid "(IntOpt) Number of instances to update per periodic task run"
-msgstr ""
-
-#: ./doc/common/tables/nova-cells.xml50(td)
-msgid "instance_updated_at_threshold = 3600"
-msgstr "instance_updated_at_threshold = 3600"
-
-#: ./doc/common/tables/nova-cells.xml51(td)
+#: ./doc/common/tables/ceilometer-database.xml46(td)
+#: ./doc/common/tables/nova-db.xml41(td)
+#: ./doc/common/tables/cinder-connection.xml23(td)
+#: ./doc/common/tables/glance-db.xml27(td)
+#: ./doc/common/tables/heat-database.xml42(td)
+#: ./doc/common/tables/neutron-db.xml38(td)
+#: ./doc/common/tables/keystone-database.xml27(td)
 msgid ""
-"(IntOpt) Number of seconds after an instance was updated or deleted to "
-"continue to update cells"
-msgstr ""
+"(StrOpt) The SQLAlchemy connection string used to connect to the database"
+msgstr "(StrOpt)  La chaîne de connexion SQLAlchemy utilisée pour se connecter à la base de données bare-metal"
 
-#: ./doc/common/tables/nova-cells.xml54(td)
-#: ./doc/common/tables/ceilometer-cells.xml42(td)
-msgid "manager = nova.cells.manager.CellsManager"
-msgstr "manager = nova.cells.manager.CellsManager"
+#: ./doc/common/tables/ceilometer-database.xml49(td)
+#: ./doc/common/tables/nova-db.xml44(td)
+#: ./doc/common/tables/cinder-connection.xml26(td)
+#: ./doc/common/tables/glance-db.xml30(td)
+#: ./doc/common/tables/heat-database.xml45(td)
+#: ./doc/common/tables/neutron-db.xml41(td)
+#: ./doc/common/tables/keystone-database.xml30(td)
+msgid "connection_debug = 0"
+msgstr "connection_debug = 0"
 
-#: ./doc/common/tables/nova-cells.xml55(td)
-#: ./doc/common/tables/ceilometer-cells.xml43(td)
-msgid "(StrOpt) Manager for cells"
-msgstr ""
-
-#: ./doc/common/tables/nova-cells.xml58(td)
-msgid "max_hop_count = 10"
-msgstr "max_hop_count = 10"
-
-#: ./doc/common/tables/nova-cells.xml59(td)
-msgid "(IntOpt) Maximum number of hops for cells routing."
-msgstr ""
-
-#: ./doc/common/tables/nova-cells.xml62(td)
-#: ./doc/common/tables/ceilometer-cells.xml46(td)
-msgid "mute_child_interval = 300"
-msgstr "mute_child_interval = 300"
-
-#: ./doc/common/tables/nova-cells.xml63(td)
-#: ./doc/common/tables/ceilometer-cells.xml47(td)
+#: ./doc/common/tables/ceilometer-database.xml50(td)
+#: ./doc/common/tables/nova-db.xml45(td)
+#: ./doc/common/tables/cinder-connection.xml27(td)
+#: ./doc/common/tables/glance-db.xml31(td)
+#: ./doc/common/tables/heat-database.xml46(td)
+#: ./doc/common/tables/neutron-db.xml42(td)
+#: ./doc/common/tables/keystone-database.xml31(td)
 msgid ""
-"(IntOpt) Number of seconds after which a lack of capability and capacity "
-"updates signals the child cell is to be treated as a mute."
+"(IntOpt) Verbosity of SQL debugging information. 0=None, 100=Everything"
+msgstr "(IntOpt) Verbosité de l’information de débogage SQL.0=Aucune, 100=Tout"
+
+#: ./doc/common/tables/ceilometer-database.xml53(td)
+#: ./doc/common/tables/nova-db.xml48(td)
+#: ./doc/common/tables/cinder-connection.xml30(td)
+#: ./doc/common/tables/glance-db.xml34(td)
+#: ./doc/common/tables/heat-database.xml49(td)
+#: ./doc/common/tables/neutron-db.xml45(td)
+#: ./doc/common/tables/keystone-database.xml34(td)
+msgid "connection_trace = False"
+msgstr "connection_trace = False"
+
+#: ./doc/common/tables/ceilometer-database.xml54(td)
+#: ./doc/common/tables/nova-db.xml49(td)
+#: ./doc/common/tables/cinder-connection.xml31(td)
+#: ./doc/common/tables/glance-db.xml35(td)
+#: ./doc/common/tables/heat-database.xml50(td)
+#: ./doc/common/tables/neutron-db.xml46(td)
+#: ./doc/common/tables/keystone-database.xml35(td)
+msgid "(BoolOpt) Add python stack traces to SQL as comment strings"
+msgstr "(BoolOpt) Ajouter des traces de pile Python à SQL en tant que chaînes de commentaires"
+
+#: ./doc/common/tables/ceilometer-database.xml57(td)
+#: ./doc/common/tables/nova-db.xml68(td)
+#: ./doc/common/tables/cinder-common.xml229(td)
+#: ./doc/common/tables/glance-db.xml54(td)
+#: ./doc/common/tables/heat-database.xml53(td)
+#: ./doc/common/tables/neutron-db.xml65(td)
+#: ./doc/common/tables/keystone-database.xml54(td)
+msgid "idle_timeout = 3600"
+msgstr "idle_timeout = 3600"
+
+#: ./doc/common/tables/ceilometer-database.xml58(td)
+#: ./doc/common/tables/nova-db.xml69(td)
+#: ./doc/common/tables/glance-db.xml55(td)
+#: ./doc/common/tables/neutron-db.xml66(td)
+#: ./doc/common/tables/keystone-database.xml55(td)
+msgid "(IntOpt) Timeout before idle sql connections are reaped"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml66(td)
-msgid "mute_weight_multiplier = -10.0"
-msgstr "mute_weight_multiplier = -10.0"
+#: ./doc/common/tables/ceilometer-database.xml61(td)
+#: ./doc/common/tables/cinder-storage.xml141(td)
+#: ./doc/common/tables/nova-db.xml72(td)
+#: ./doc/common/tables/glance-db.xml58(td)
+#: ./doc/common/tables/heat-database.xml57(td)
+#: ./doc/common/tables/keystone-database.xml58(td)
+msgid "max_overflow = None"
+msgstr "max_overflow = None"
 
-#: ./doc/common/tables/nova-cells.xml67(td)
+#: ./doc/common/tables/ceilometer-database.xml62(td)
+#: ./doc/common/tables/cinder-storage.xml142(td)
+#: ./doc/common/tables/nova-db.xml73(td)
+#: ./doc/common/tables/glance-db.xml59(td)
+#: ./doc/common/tables/heat-database.xml58(td)
+#: ./doc/common/tables/neutron-db.xml70(td)
+#: ./doc/common/tables/keystone-database.xml59(td)
+msgid "(IntOpt) If set, use this value for max_overflow with sqlalchemy"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-database.xml65(td)
+#: ./doc/common/tables/nova-db.xml76(td)
+#: ./doc/common/tables/glance-db.xml62(td)
+#: ./doc/common/tables/heat-database.xml61(td)
+#: ./doc/common/tables/keystone-database.xml62(td)
+msgid "max_pool_size = None"
+msgstr "max_pool_size = None"
+
+#: ./doc/common/tables/ceilometer-database.xml66(td)
+#: ./doc/common/tables/cinder-storage.xml146(td)
+#: ./doc/common/tables/nova-db.xml77(td)
+#: ./doc/common/tables/glance-db.xml63(td)
+#: ./doc/common/tables/heat-database.xml62(td)
+#: ./doc/common/tables/neutron-db.xml74(td)
+#: ./doc/common/tables/keystone-database.xml63(td)
+msgid "(IntOpt) Maximum number of SQL connections to keep open in a pool"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-database.xml69(td)
+#: ./doc/common/tables/cinder-storage.xml149(td)
+#: ./doc/common/tables/nova-db.xml80(td)
+#: ./doc/common/tables/glance-db.xml66(td)
+#: ./doc/common/tables/heat-database.xml65(td)
+#: ./doc/common/tables/neutron-db.xml77(td)
+#: ./doc/common/tables/keystone-database.xml66(td)
+msgid "max_retries = 10"
+msgstr "max_retries = 10"
+
+#: ./doc/common/tables/ceilometer-database.xml70(td)
+#: ./doc/common/tables/nova-db.xml81(td)
+#: ./doc/common/tables/glance-db.xml67(td)
+#: ./doc/common/tables/neutron-db.xml78(td)
+#: ./doc/common/tables/keystone-database.xml67(td)
 msgid ""
-"(FloatOpt) Multiplier used to weigh mute children. (The value should be "
-"negative.)"
+"(IntOpt) Maximum db connection retries during startup. (setting -1 implies "
+"an infinite retry count)"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml70(td)
-msgid "mute_weight_value = 1000.0"
-msgstr "mute_weight_value = 1000.0"
+#: ./doc/common/tables/ceilometer-database.xml73(td)
+#: ./doc/common/tables/cinder-storage.xml153(td)
+#: ./doc/common/tables/nova-db.xml84(td)
+#: ./doc/common/tables/glance-db.xml70(td)
+#: ./doc/common/tables/heat-database.xml69(td)
+#: ./doc/common/tables/neutron-db.xml81(td)
+#: ./doc/common/tables/keystone-database.xml70(td)
+msgid "min_pool_size = 1"
+msgstr "min_pool_size = 1"
 
-#: ./doc/common/tables/nova-cells.xml71(td)
+#: ./doc/common/tables/ceilometer-database.xml74(td)
+#: ./doc/common/tables/cinder-storage.xml154(td)
+#: ./doc/common/tables/nova-db.xml85(td)
+#: ./doc/common/tables/glance-db.xml71(td)
+#: ./doc/common/tables/heat-database.xml70(td)
+#: ./doc/common/tables/neutron-db.xml82(td)
+#: ./doc/common/tables/keystone-database.xml71(td)
+msgid "(IntOpt) Minimum number of SQL connections to keep open in a pool"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-database.xml77(td)
+#: ./doc/common/tables/nova-db.xml92(td)
+#: ./doc/common/tables/glance-db.xml78(td)
+#: ./doc/common/tables/heat-database.xml73(td)
+#: ./doc/common/tables/keystone-database.xml78(td)
+msgid "pool_timeout = None"
+msgstr "pool_timeout = None"
+
+#: ./doc/common/tables/ceilometer-database.xml78(td)
+#: ./doc/common/tables/nova-db.xml93(td)
+#: ./doc/common/tables/glance-db.xml79(td)
+#: ./doc/common/tables/heat-database.xml74(td)
+#: ./doc/common/tables/neutron-db.xml86(td)
+#: ./doc/common/tables/keystone-database.xml79(td)
+msgid "(IntOpt) If set, use this value for pool_timeout with sqlalchemy"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-database.xml81(td)
+#: ./doc/common/tables/nova-db.xml96(td)
+#: ./doc/common/tables/cinder-common.xml233(td)
+#: ./doc/common/tables/glance-db.xml82(td)
+#: ./doc/common/tables/heat-database.xml77(td)
+#: ./doc/common/tables/neutron-db.xml89(td)
+#: ./doc/common/tables/keystone-database.xml82(td)
+msgid "retry_interval = 10"
+msgstr "retry_interval = 10"
+
+#: ./doc/common/tables/ceilometer-database.xml82(td)
+#: ./doc/common/tables/nova-db.xml97(td)
+#: ./doc/common/tables/glance-db.xml83(td)
+#: ./doc/common/tables/neutron-db.xml90(td)
+#: ./doc/common/tables/keystone-database.xml83(td)
+msgid "(IntOpt) Interval between retries of opening a sql connection"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-database.xml85(td)
+#: ./doc/common/tables/heat-database.xml81(td)
+#: ./doc/common/tables/neutron-db.xml93(td)
+msgid "slave_connection ="
+msgstr "slave_connection ="
+
+#: ./doc/common/tables/ceilometer-database.xml86(td)
+#: ./doc/common/tables/nova-db.xml101(td)
+#: ./doc/common/tables/heat-database.xml82(td)
+#: ./doc/common/tables/neutron-db.xml94(td)
 msgid ""
-"(FloatOpt) Weight value assigned to mute children. (The value should be "
-"positive.)"
+"(StrOpt) The SQLAlchemy connection string used to connect to the slave "
+"database"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml74(td)
-#: ./doc/common/tables/ceilometer-cells.xml50(td)
-msgid "name = nova"
+#: ./doc/common/tables/ceilometer-database.xml89(td)
+msgid "time_to_live = -1"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml75(td)
-#: ./doc/common/tables/ceilometer-cells.xml51(td)
-msgid "(StrOpt) Name of this cell"
-msgstr "(StrOpt) Nom de cette cellule"
-
-#: ./doc/common/tables/nova-cells.xml78(td)
-msgid "offset_weight_multiplier = 1.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-cells.xml79(td)
-msgid "(FloatOpt) Multiplier used to weigh offset weigher."
-msgstr ""
-
-#: ./doc/common/tables/nova-cells.xml82(td)
-#: ./doc/common/tables/ceilometer-cells.xml54(td)
-msgid "reserve_percent = 10.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-cells.xml83(td)
-#: ./doc/common/tables/ceilometer-cells.xml55(td)
+#: ./doc/common/tables/ceilometer-database.xml90(td)
 msgid ""
-"(FloatOpt) Percentage of cell capacity to hold in reserve. Affects both "
-"memory and disk utilization"
+"(IntOpt) Number of seconds that samples are kept in the database for (&lt;= "
+"0 means forever)."
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml86(td)
-#: ./doc/common/tables/ceilometer-cells.xml58(td)
-msgid "topic = cells"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml8(caption)
+msgid "Description of configuration options for openvswitch_agent"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml87(td)
-#: ./doc/common/tables/ceilometer-cells.xml59(td)
-msgid "(StrOpt) The topic cells nodes listen on"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml22(td)
+msgid "ovs_integration_bridge = br-int"
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml8(caption)
-msgid "Description of configuration options for db_mongodb"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml23(td)
+msgid "(StrOpt) Name of Open vSwitch bridge to use"
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml19(th)
-msgid "[mongodb]"
-msgstr "[mongodb]"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml26(td)
+msgid "ovs_use_veth = False"
+msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml22(td)
-#: ./doc/common/tables/trove-db_cassandra.xml22(td)
-#: ./doc/common/tables/trove-db_redis.xml22(td)
-#: ./doc/common/tables/trove-db_couchbase.xml22(td)
-msgid "backup_strategy = None"
-msgstr "backup_strategy = None"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml27(td)
+msgid "(BoolOpt) Uses veth for an interface or not"
+msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml23(td)
-#: ./doc/common/tables/trove-backup.xml51(td)
+#: ./doc/common/tables/neutron-openvswitch_agent.xml30(td)
+msgid "ovs_vsctl_timeout = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml31(td)
+msgid "(IntOpt) Timeout in seconds for ovs-vsctl commands"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml34(th)
+#: ./doc/common/tables/neutron-rpc.xml66(th)
+#: ./doc/common/tables/neutron-ml2_ofa.xml34(th)
+#: ./doc/common/tables/neutron-metering_agent.xml30(th)
+#: ./doc/common/tables/neutron-nvsd.xml19(th)
+#: ./doc/common/tables/neutron-hyperv_agent.xml19(th)
+#: ./doc/common/tables/neutron-common.xml182(th)
+msgid "[AGENT]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml37(td)
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml44(td)
+msgid "l2_population = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml38(td)
+msgid ""
+"(BoolOpt) Use ml2 l2population mechanism driver to learn remote mac and IPs "
+"and improve tunnel scalability"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml41(td)
+msgid "minimize_polling = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml42(td)
+msgid "(BoolOpt) Minimize polling by monitoring ovsdb for interface changes."
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml45(td)
+msgid "ovsdb_monitor_respawn_interval = 30"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml46(td)
+msgid ""
+"(IntOpt) The number of seconds to wait before respawning the ovsdb monitor "
+"after losing communication with it"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml49(td)
+msgid "tunnel_types ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml50(td)
+msgid "(ListOpt) Network types supported by the agent (gre and/or vxlan)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml53(td)
+msgid "veth_mtu = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml54(td)
+msgid "(IntOpt) MTU size of veth interfaces"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml57(td)
+msgid "vxlan_udp_port = 4789"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml58(td)
+msgid "(IntOpt) The UDP port to use for VXLAN tunnels."
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml61(th)
+#: ./doc/common/tables/neutron-cisco.xml54(th)
+msgid "[CISCO_N1K]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml64(td)
+msgid "local_ip = 10.0.0.3"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml65(td)
+msgid "(StrOpt) N1K Local IP"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml68(th)
+#: ./doc/common/tables/neutron-ryu.xml19(th)
+msgid "[OVS]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml71(td)
+#: ./doc/common/tables/neutron-cisco.xml57(td)
+msgid "bridge_mappings ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml72(td)
+msgid "(ListOpt) List of &lt;physical_network&gt;:&lt;bridge&gt;"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml75(td)
+msgid "enable_tunneling = False"
+msgstr "enable_tunneling = False"
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml76(td)
+msgid "(BoolOpt) Enable tunneling support"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml79(td)
+msgid "int_peer_patch_port = patch-tun"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml80(td)
+msgid "(StrOpt) Peer patch port in integration bridge for tunnel bridge"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml83(td)
+#: ./doc/common/tables/neutron-cisco.xml73(td)
+#: ./doc/common/tables/nova-vmware.xml46(td)
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml140(td)
+#: ./doc/common/tables/neutron-bigswitch.xml140(td)
+#: ./doc/common/tables/neutron-nvsd.xml22(td)
+msgid "integration_bridge = br-int"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml84(td)
+#: ./doc/common/tables/neutron-sdnve.xml43(td)
+msgid "(StrOpt) Integration bridge to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml87(td)
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml48(td)
+msgid "local_ip ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml88(td)
+msgid "(StrOpt) Local IP address of GRE tunnel endpoints."
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml91(td)
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml29(td)
+#: ./doc/common/tables/neutron-ml2_vlan.xml22(td)
+#: ./doc/common/tables/neutron-hyperv_agent.xml45(td)
+msgid "network_vlan_ranges ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml92(td)
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml30(td)
+#: ./doc/common/tables/neutron-hyperv_agent.xml46(td)
+#: ./doc/common/tables/neutron-mlnx.xml42(td)
+msgid ""
+"(ListOpt) List of &lt;physical_network&gt;:&lt;vlan_min&gt;:&lt;vlan_max&gt;"
+" or &lt;physical_network&gt;"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml95(td)
+#: ./doc/common/tables/neutron-cisco.xml89(td)
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml33(td)
+#: ./doc/common/tables/neutron-hyperv_agent.xml49(td)
+msgid "tenant_network_type = local"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml96(td)
+msgid ""
+"(StrOpt) Network type for tenant networks (local, vlan, gre, vxlan, or none)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml99(td)
+msgid "tun_peer_patch_port = patch-int"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml100(td)
+msgid "(StrOpt) Peer patch port in tunnel bridge for integration bridge"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml103(td)
+#: ./doc/common/tables/neutron-cisco.xml93(td)
+msgid "tunnel_bridge = br-tun"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml104(td)
+msgid "(StrOpt) Tunnel bridge to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml107(td)
+#: ./doc/common/tables/neutron-ml2_gre.xml22(td)
+msgid "tunnel_id_ranges ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml108(td)
+msgid "(ListOpt) List of &lt;tun_min&gt;:&lt;tun_max&gt;"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml111(td)
+msgid "tunnel_type ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml112(td)
+msgid ""
+"(StrOpt) The type of tunnels to use when utilizing tunnels, either 'gre' or "
+"'vxlan'"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml8(caption)
+msgid "Description of configuration options for clients"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml22(td)
+msgid "region_name_for_services = None"
+msgstr "region_name_for_services = None"
+
+#: ./doc/common/tables/heat-clients.xml23(td)
+msgid "(StrOpt) Default region name used to get services endpoints."
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml26(th)
+msgid "[clients]"
+msgstr "[clients]"
+
+#: ./doc/common/tables/heat-clients.xml29(td)
+#: ./doc/common/tables/heat-clients_nova.xml22(td)
+#: ./doc/common/tables/heat-clients_heat.xml22(td)
+#: ./doc/common/tables/heat-cfn_api.xml64(td)
+#: ./doc/common/tables/heat-api.xml145(td)
+#: ./doc/common/tables/heat-clients_ceilometer.xml22(td)
+#: ./doc/common/tables/heat-clients_cinder.xml22(td)
+#: ./doc/common/tables/heat-clients_trove.xml22(td)
+#: ./doc/common/tables/nova-ca.xml65(td)
+#: ./doc/common/tables/cinder-ssl.xml22(td)
+#: ./doc/common/tables/trove-ssl.xml22(td)
+#: ./doc/common/tables/heat-clients_swift.xml22(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml60(td)
+#: ./doc/common/tables/neutron-ssl.xml37(td)
+#: ./doc/common/tables/heat-clients_neutron.xml22(td)
+#: ./doc/common/tables/heat-clients_keystone.xml22(td)
+#: ./doc/common/tables/ceilometer-ssl.xml22(td)
+#: ./doc/common/tables/glance-ssl.xml22(td)
+msgid "ca_file = None"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml30(td)
+#: ./doc/common/tables/heat-clients_nova.xml23(td)
+#: ./doc/common/tables/heat-clients_heat.xml23(td)
+#: ./doc/common/tables/heat-clients_ceilometer.xml23(td)
+#: ./doc/common/tables/heat-clients_cinder.xml23(td)
+#: ./doc/common/tables/heat-clients_trove.xml23(td)
+#: ./doc/common/tables/heat-clients_swift.xml23(td)
+#: ./doc/common/tables/heat-clients_neutron.xml23(td)
+#: ./doc/common/tables/heat-clients_keystone.xml23(td)
+msgid "(StrOpt) Optional CA cert file to use in SSL connections."
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml33(td)
+#: ./doc/common/tables/heat-clients_nova.xml26(td)
+#: ./doc/common/tables/heat-clients_heat.xml26(td)
+#: ./doc/common/tables/heat-cfn_api.xml45(td)
+#: ./doc/common/tables/heat-cfn_api.xml68(td)
+#: ./doc/common/tables/heat-api.xml115(td)
+#: ./doc/common/tables/heat-api.xml149(td)
+#: ./doc/common/tables/heat-clients_ceilometer.xml26(td)
+#: ./doc/common/tables/heat-clients_cinder.xml26(td)
+#: ./doc/common/tables/heat-clients_trove.xml26(td)
+#: ./doc/common/tables/nova-ca.xml69(td)
+#: ./doc/common/tables/cinder-ssl.xml26(td)
+#: ./doc/common/tables/trove-ssl.xml26(td)
+#: ./doc/common/tables/heat-clients_swift.xml26(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml41(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml64(td)
+#: ./doc/common/tables/neutron-ssl.xml41(td)
+#: ./doc/common/tables/neutron-nec.xml26(td)
+#: ./doc/common/tables/heat-clients_neutron.xml26(td)
+#: ./doc/common/tables/heat-clients_keystone.xml26(td)
+#: ./doc/common/tables/ceilometer-ssl.xml26(td)
+#: ./doc/common/tables/glance-ssl.xml26(td)
+msgid "cert_file = None"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml34(td)
+#: ./doc/common/tables/heat-clients_nova.xml27(td)
+#: ./doc/common/tables/heat-clients_heat.xml27(td)
+#: ./doc/common/tables/heat-clients_ceilometer.xml27(td)
+#: ./doc/common/tables/heat-clients_cinder.xml27(td)
+#: ./doc/common/tables/heat-clients_trove.xml27(td)
+#: ./doc/common/tables/heat-clients_swift.xml27(td)
+#: ./doc/common/tables/heat-clients_neutron.xml27(td)
+#: ./doc/common/tables/heat-clients_keystone.xml27(td)
+msgid "(StrOpt) Optional PEM-formatted certificate chain file."
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml37(td)
+#: ./doc/common/tables/heat-clients_nova.xml30(td)
+#: ./doc/common/tables/heat-clients_heat.xml30(td)
+#: ./doc/common/tables/heat-clients_ceilometer.xml30(td)
+#: ./doc/common/tables/heat-clients_cinder.xml30(td)
+#: ./doc/common/tables/heat-clients_trove.xml30(td)
+#: ./doc/common/tables/heat-clients_swift.xml30(td)
+#: ./doc/common/tables/heat-clients_neutron.xml30(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml39(td)
+#: ./doc/common/tables/heat-clients_keystone.xml30(td)
+msgid "endpoint_type = publicURL"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml38(td)
+#: ./doc/common/tables/heat-clients_nova.xml31(td)
+#: ./doc/common/tables/heat-clients_heat.xml31(td)
+#: ./doc/common/tables/heat-clients_ceilometer.xml31(td)
+#: ./doc/common/tables/heat-clients_cinder.xml31(td)
+#: ./doc/common/tables/heat-clients_trove.xml31(td)
+#: ./doc/common/tables/heat-clients_swift.xml31(td)
+#: ./doc/common/tables/heat-clients_neutron.xml31(td)
+#: ./doc/common/tables/heat-clients_keystone.xml31(td)
+msgid ""
+"(StrOpt) Type of endpoint in Identity service catalog to use for "
+"communication with the OpenStack service."
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml41(td)
+#: ./doc/common/tables/glance-auth_token.xml101(td)
+#: ./doc/common/tables/heat-clients_nova.xml34(td)
+#: ./doc/common/tables/heat-clients_heat.xml34(td)
+#: ./doc/common/tables/neutron-auth_token.xml101(td)
+#: ./doc/common/tables/ceilometer-auth.xml101(td)
+#: ./doc/common/tables/ceilometer-auth.xml136(td)
+#: ./doc/common/tables/heat-auth_token.xml101(td)
+#: ./doc/common/tables/nova-auth_token.xml94(td)
+#: ./doc/common/tables/heat-clients_ceilometer.xml34(td)
+#: ./doc/common/tables/cinder-auth_token.xml101(td)
+#: ./doc/common/tables/keystone-auth_token.xml101(td)
+#: ./doc/common/tables/heat-clients_cinder.xml34(td)
+#: ./doc/common/tables/heat-clients_trove.xml34(td)
+#: ./doc/common/tables/heat-clients_swift.xml34(td)
+#: ./doc/common/tables/heat-clients_neutron.xml34(td)
+#: ./doc/common/tables/trove-auth_token.xml101(td)
+#: ./doc/common/tables/heat-clients_keystone.xml34(td)
+msgid "insecure = False"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml42(td)
+#: ./doc/common/tables/heat-clients_nova.xml35(td)
+#: ./doc/common/tables/heat-clients_heat.xml35(td)
+#: ./doc/common/tables/heat-clients_ceilometer.xml35(td)
+#: ./doc/common/tables/heat-clients_cinder.xml35(td)
+#: ./doc/common/tables/heat-clients_trove.xml35(td)
+#: ./doc/common/tables/heat-clients_swift.xml35(td)
+#: ./doc/common/tables/heat-clients_neutron.xml35(td)
+#: ./doc/common/tables/heat-clients_keystone.xml35(td)
+msgid "(BoolOpt) If set, then the server's certificate will not be verified."
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml45(td)
+#: ./doc/common/tables/heat-clients_nova.xml38(td)
+#: ./doc/common/tables/heat-clients_heat.xml38(td)
+#: ./doc/common/tables/heat-cfn_api.xml49(td)
+#: ./doc/common/tables/heat-cfn_api.xml72(td)
+#: ./doc/common/tables/heat-api.xml119(td)
+#: ./doc/common/tables/heat-api.xml153(td)
+#: ./doc/common/tables/heat-clients_ceilometer.xml38(td)
+#: ./doc/common/tables/heat-clients_cinder.xml38(td)
+#: ./doc/common/tables/heat-clients_trove.xml38(td)
+#: ./doc/common/tables/nova-ca.xml73(td)
+#: ./doc/common/tables/cinder-ssl.xml30(td)
+#: ./doc/common/tables/trove-ssl.xml30(td)
+#: ./doc/common/tables/heat-clients_swift.xml38(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml45(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml68(td)
+#: ./doc/common/tables/neutron-ssl.xml45(td)
+#: ./doc/common/tables/neutron-nec.xml46(td)
+#: ./doc/common/tables/heat-clients_neutron.xml38(td)
+#: ./doc/common/tables/heat-clients_keystone.xml38(td)
+#: ./doc/common/tables/ceilometer-ssl.xml30(td)
+#: ./doc/common/tables/glance-ssl.xml30(td)
+msgid "key_file = None"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml46(td)
+#: ./doc/common/tables/heat-clients_nova.xml39(td)
+#: ./doc/common/tables/heat-clients_heat.xml39(td)
+#: ./doc/common/tables/heat-clients_ceilometer.xml39(td)
+#: ./doc/common/tables/heat-clients_cinder.xml39(td)
+#: ./doc/common/tables/heat-clients_trove.xml39(td)
+#: ./doc/common/tables/heat-clients_swift.xml39(td)
+#: ./doc/common/tables/heat-clients_neutron.xml39(td)
+#: ./doc/common/tables/heat-clients_keystone.xml39(td)
+msgid "(StrOpt) Optional PEM-formatted file that contains the private key."
+msgstr ""
+
+#: ./doc/common/tables/cinder-solidfire.xml8(caption)
+msgid "Description of configuration options for solidfire"
+msgstr ""
+
+#: ./doc/common/tables/cinder-solidfire.xml22(td)
+msgid "sf_account_prefix = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-solidfire.xml23(td)
+msgid ""
+"(StrOpt) Create SolidFire accounts with this prefix. Any string can be used "
+"here, but the string \"hostname\" is special and will create a prefix using "
+"the cinder node hostsname (previous default behavior). The default is NO "
+"prefix."
+msgstr ""
+
+#: ./doc/common/tables/cinder-solidfire.xml26(td)
+msgid "sf_allow_tenant_qos = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-solidfire.xml27(td)
+msgid "(BoolOpt) Allow tenants to specify QOS on create"
+msgstr ""
+
+#: ./doc/common/tables/cinder-solidfire.xml30(td)
+msgid "sf_api_port = 443"
+msgstr ""
+
+#: ./doc/common/tables/cinder-solidfire.xml31(td)
+msgid ""
+"(IntOpt) SolidFire API port. Useful if the device api is behind a proxy on a"
+" different port."
+msgstr ""
+
+#: ./doc/common/tables/cinder-solidfire.xml34(td)
+msgid "sf_emulate_512 = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-solidfire.xml35(td)
+msgid "(BoolOpt) Set 512 byte emulation on volume creation;"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml8(caption)
+#: ./doc/common/tables/glance-rpc.xml8(caption)
+#: ./doc/common/tables/keystone-rpc.xml8(caption)
+#: ./doc/common/tables/ceilometer-rpc.xml8(caption)
+#: ./doc/common/tables/trove-rpc.xml8(caption)
+#: ./doc/common/tables/cinder-rpc.xml8(caption)
+#: ./doc/common/tables/heat-rpc.xml8(caption)
+#: ./doc/common/tables/nova-rpc.xml8(caption)
+msgid "Description of configuration options for rpc"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml22(td)
+#: ./doc/common/tables/trove-amqp.xml22(td)
+#: ./doc/common/tables/heat-amqp.xml22(td)
+#: ./doc/common/tables/keystone-amqp.xml22(td)
+#: ./doc/common/tables/glance-amqp.xml22(td)
+#: ./doc/common/tables/cinder-rpc.xml26(td)
+#: ./doc/common/tables/nova-rpc_all.xml22(td)
+#: ./doc/common/tables/nova-rpc.xml22(td)
+#: ./doc/common/tables/ceilometer-amqp.xml22(td)
+msgid "amqp_auto_delete = False"
+msgstr "amqp_auto_delete = False"
+
+#: ./doc/common/tables/neutron-rpc.xml23(td)
+#: ./doc/common/tables/trove-amqp.xml23(td)
+#: ./doc/common/tables/heat-amqp.xml23(td)
+#: ./doc/common/tables/keystone-amqp.xml23(td)
+#: ./doc/common/tables/glance-amqp.xml23(td)
+#: ./doc/common/tables/cinder-rpc.xml27(td)
+#: ./doc/common/tables/nova-rpc_all.xml23(td)
+#: ./doc/common/tables/nova-rpc.xml23(td)
+#: ./doc/common/tables/ceilometer-amqp.xml23(td)
+msgid "(BoolOpt) Auto-delete queues in amqp."
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml26(td)
+#: ./doc/common/tables/trove-amqp.xml26(td)
+#: ./doc/common/tables/heat-amqp.xml26(td)
+#: ./doc/common/tables/keystone-amqp.xml26(td)
+#: ./doc/common/tables/glance-amqp.xml26(td)
+#: ./doc/common/tables/cinder-rpc.xml30(td)
+#: ./doc/common/tables/nova-rpc_all.xml26(td)
+#: ./doc/common/tables/nova-rpc.xml26(td)
+#: ./doc/common/tables/ceilometer-amqp.xml26(td)
+msgid "amqp_durable_queues = False"
+msgstr "amqp_durable_queues = False"
+
+#: ./doc/common/tables/neutron-rpc.xml27(td)
+#: ./doc/common/tables/trove-amqp.xml27(td)
+#: ./doc/common/tables/heat-amqp.xml27(td)
+#: ./doc/common/tables/keystone-amqp.xml27(td)
+#: ./doc/common/tables/glance-amqp.xml27(td)
+#: ./doc/common/tables/cinder-rpc.xml31(td)
+#: ./doc/common/tables/nova-rpc_all.xml27(td)
+#: ./doc/common/tables/nova-rpc.xml27(td)
+#: ./doc/common/tables/ceilometer-amqp.xml27(td)
+msgid "(BoolOpt) Use durable queues in amqp."
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml30(td)
+msgid "control_exchange = neutron"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml31(td)
+#: ./doc/common/tables/trove-amqp.xml35(td)
+#: ./doc/common/tables/heat-amqp.xml31(td)
+#: ./doc/common/tables/ceilometer-exchange.xml27(td)
+msgid "(StrOpt) AMQP exchange to connect to if using RabbitMQ or Qpid"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml34(td)
+#: ./doc/common/tables/ceilometer-redis.xml26(td)
+#: ./doc/common/tables/glance-matchmaker.xml22(td)
+#: ./doc/common/tables/trove-rpc.xml30(td)
+#: ./doc/common/tables/cinder-rpc.xml66(td)
+#: ./doc/common/tables/nova-rpc_all.xml54(td)
+#: ./doc/common/tables/heat-rpc.xml30(td)
+#: ./doc/common/tables/nova-rpc.xml34(td)
+#: ./doc/common/tables/keystone-redis.xml26(td)
+msgid "matchmaker_heartbeat_freq = 300"
+msgstr "matchmaker_heartbeat_freq = 300"
+
+#: ./doc/common/tables/neutron-rpc.xml35(td)
+#: ./doc/common/tables/ceilometer-redis.xml27(td)
+#: ./doc/common/tables/trove-rpc.xml31(td)
+#: ./doc/common/tables/heat-rpc.xml31(td)
+msgid "(IntOpt) Heartbeat frequency"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml38(td)
+#: ./doc/common/tables/ceilometer-redis.xml30(td)
+#: ./doc/common/tables/glance-matchmaker.xml26(td)
+#: ./doc/common/tables/trove-rpc.xml34(td)
+#: ./doc/common/tables/cinder-rpc.xml70(td)
+#: ./doc/common/tables/nova-rpc_all.xml58(td)
+#: ./doc/common/tables/heat-rpc.xml34(td)
+#: ./doc/common/tables/nova-rpc.xml38(td)
+#: ./doc/common/tables/keystone-redis.xml30(td)
+msgid "matchmaker_heartbeat_ttl = 600"
+msgstr "matchmaker_heartbeat_ttl = 600"
+
+#: ./doc/common/tables/neutron-rpc.xml39(td)
+#: ./doc/common/tables/ceilometer-redis.xml31(td)
+#: ./doc/common/tables/glance-matchmaker.xml27(td)
+#: ./doc/common/tables/trove-rpc.xml35(td)
+#: ./doc/common/tables/cinder-rpc.xml71(td)
+#: ./doc/common/tables/nova-rpc_all.xml59(td)
+#: ./doc/common/tables/heat-rpc.xml35(td)
+#: ./doc/common/tables/nova-rpc.xml39(td)
+#: ./doc/common/tables/keystone-redis.xml31(td)
+msgid "(IntOpt) Heartbeat time-to-live."
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml42(td)
+msgid "rpc_backend = neutron.openstack.common.rpc.impl_kombu"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml43(td)
+#: ./doc/common/tables/ceilometer-rpc.xml31(td)
+#: ./doc/common/tables/trove-rpc.xml51(td)
+#: ./doc/common/tables/heat-rpc.xml39(td)
+msgid "(StrOpt) The messaging module to use, defaults to kombu."
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml46(td)
+#: ./doc/common/tables/keystone-amqp.xml50(td)
+#: ./doc/common/tables/ceilometer-rpc.xml34(td)
+#: ./doc/common/tables/trove-rpc.xml54(td)
+#: ./doc/common/tables/glance-zmq.xml22(td)
+#: ./doc/common/tables/cinder-rpc.xml186(td)
+#: ./doc/common/tables/nova-rpc_all.xml154(td)
+#: ./doc/common/tables/heat-rpc.xml42(td)
+#: ./doc/common/tables/nova-rpc.xml46(td)
+msgid "rpc_cast_timeout = 30"
+msgstr "rpc_cast_timeout = 30"
+
+#: ./doc/common/tables/neutron-rpc.xml47(td)
+#: ./doc/common/tables/keystone-amqp.xml51(td)
+#: ./doc/common/tables/ceilometer-rpc.xml35(td)
+#: ./doc/common/tables/trove-rpc.xml55(td)
+#: ./doc/common/tables/glance-zmq.xml23(td)
+#: ./doc/common/tables/cinder-rpc.xml187(td)
+#: ./doc/common/tables/nova-rpc_all.xml155(td)
+#: ./doc/common/tables/heat-rpc.xml43(td)
+#: ./doc/common/tables/nova-rpc.xml47(td)
+msgid ""
+"(IntOpt) Seconds to wait before a cast expires (TTL). Only supported by "
+"impl_zmq."
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml50(td)
+#: ./doc/common/tables/keystone-amqp.xml54(td)
+#: ./doc/common/tables/ceilometer-rpc.xml38(td)
+#: ./doc/common/tables/trove-rpc.xml58(td)
+#: ./doc/common/tables/glance-amqp.xml42(td)
+#: ./doc/common/tables/cinder-rpc.xml190(td)
+#: ./doc/common/tables/nova-rpc_all.xml158(td)
+#: ./doc/common/tables/heat-rpc.xml46(td)
+#: ./doc/common/tables/nova-rpc.xml50(td)
+msgid "rpc_conn_pool_size = 30"
+msgstr "rpc_conn_pool_size = 30"
+
+#: ./doc/common/tables/neutron-rpc.xml51(td)
+#: ./doc/common/tables/ceilometer-rpc.xml39(td)
+#: ./doc/common/tables/trove-rpc.xml59(td)
+#: ./doc/common/tables/heat-rpc.xml47(td)
+msgid "(IntOpt) Size of RPC connection pool"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml54(td)
+#: ./doc/common/tables/keystone-amqp.xml58(td)
+#: ./doc/common/tables/ceilometer-rpc.xml42(td)
+#: ./doc/common/tables/trove-rpc.xml62(td)
+#: ./doc/common/tables/glance-amqp.xml46(td)
+#: ./doc/common/tables/cinder-rpc.xml194(td)
+#: ./doc/common/tables/nova-rpc_all.xml162(td)
+#: ./doc/common/tables/heat-rpc.xml50(td)
+#: ./doc/common/tables/nova-rpc.xml54(td)
+msgid "rpc_response_timeout = 60"
+msgstr "rpc_response_timeout = 60"
+
+#: ./doc/common/tables/neutron-rpc.xml55(td)
+#: ./doc/common/tables/ceilometer-rpc.xml43(td)
+#: ./doc/common/tables/trove-rpc.xml63(td)
+#: ./doc/common/tables/heat-rpc.xml51(td)
+msgid "(IntOpt) Seconds to wait for a response from call or multicall"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml58(td)
+#: ./doc/common/tables/keystone-amqp.xml62(td)
+#: ./doc/common/tables/ceilometer-rpc.xml46(td)
+#: ./doc/common/tables/trove-rpc.xml66(td)
+#: ./doc/common/tables/glance-amqp.xml50(td)
+#: ./doc/common/tables/cinder-rpc.xml198(td)
+#: ./doc/common/tables/nova-rpc_all.xml166(td)
+#: ./doc/common/tables/heat-rpc.xml54(td)
+#: ./doc/common/tables/nova-rpc.xml58(td)
+msgid "rpc_thread_pool_size = 64"
+msgstr "rpc_thread_pool_size = 64"
+
+#: ./doc/common/tables/neutron-rpc.xml59(td)
+#: ./doc/common/tables/ceilometer-rpc.xml47(td)
+#: ./doc/common/tables/trove-rpc.xml67(td)
+#: ./doc/common/tables/heat-rpc.xml55(td)
+msgid "(IntOpt) Size of RPC thread pool"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml62(td)
+msgid "rpc_workers = 0"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml63(td)
+msgid "(IntOpt) Number of RPC worker processes for service"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml69(td)
+msgid "rpc_support_old_agents = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml70(td)
+msgid "(BoolOpt) Enable server RPC compatibility with old agents"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml73(th)
+#: ./doc/common/tables/ceilometer-redis.xml49(th)
+#: ./doc/common/tables/glance-matchmaker.xml30(th)
+#: ./doc/common/tables/cinder-rpc.xml238(th)
+#: ./doc/common/tables/nova-rpc_all.xml205(th)
+#: ./doc/common/tables/heat-rpc.xml58(th)
+#: ./doc/common/tables/trove-redis.xml34(th)
+#: ./doc/common/tables/nova-rpc.xml69(th)
+#: ./doc/common/tables/keystone-redis.xml42(th)
+msgid "[matchmaker_ring]"
+msgstr "[matchmaker_ring]"
+
+#: ./doc/common/tables/neutron-rpc.xml76(td)
+#: ./doc/common/tables/ceilometer-redis.xml52(td)
+#: ./doc/common/tables/glance-matchmaker.xml33(td)
+#: ./doc/common/tables/cinder-rpc.xml241(td)
+#: ./doc/common/tables/nova-rpc_all.xml208(td)
+#: ./doc/common/tables/heat-rpc.xml61(td)
+#: ./doc/common/tables/trove-redis.xml37(td)
+#: ./doc/common/tables/nova-rpc.xml72(td)
+#: ./doc/common/tables/keystone-redis.xml45(td)
+msgid "ringfile = /etc/oslo/matchmaker_ring.json"
+msgstr "ringfile = /etc/oslo/matchmaker_ring.json"
+
+#: ./doc/common/tables/neutron-rpc.xml77(td)
+#: ./doc/common/tables/ceilometer-redis.xml53(td)
+#: ./doc/common/tables/heat-rpc.xml62(td)
+#: ./doc/common/tables/trove-redis.xml38(td)
+msgid "(StrOpt) Matchmaker ring file (JSON)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml80(th)
+#: ./doc/common/tables/ceilometer-rpc.xml92(th)
+#: ./doc/common/tables/trove-rpc.xml70(th)
+#: ./doc/common/tables/heat-rpc.xml65(th)
+msgid "[rpc_notifier2]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml83(td)
+#: ./doc/common/tables/ceilometer-rpc.xml95(td)
+#: ./doc/common/tables/trove-rpc.xml73(td)
+#: ./doc/common/tables/heat-rpc.xml68(td)
+msgid "topics = notifications"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml84(td)
+#: ./doc/common/tables/trove-rpc.xml74(td)
+msgid "(ListOpt) AMQP topic(s) used for openstack notifications"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_percona.xml8(caption)
+msgid "Description of configuration options for db_percona"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_percona.xml19(th)
+msgid "[percona]"
+msgstr "[percona]"
+
+#: ./doc/common/tables/trove-db_percona.xml22(td)
+#: ./doc/common/tables/trove-db_mysql.xml22(td)
+#: ./doc/common/tables/trove-backup.xml50(td)
+msgid "backup_strategy = InnoBackupEx"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_percona.xml23(td)
 #: ./doc/common/tables/trove-db_cassandra.xml23(td)
 #: ./doc/common/tables/trove-db_mysql.xml23(td)
-#: ./doc/common/tables/trove-db_redis.xml23(td)
 #: ./doc/common/tables/trove-db_couchbase.xml23(td)
-#: ./doc/common/tables/trove-db_percona.xml23(td)
+#: ./doc/common/tables/trove-db_mongodb.xml23(td)
+#: ./doc/common/tables/trove-backup.xml51(td)
+#: ./doc/common/tables/trove-db_redis.xml23(td)
 msgid "(StrOpt) Default strategy to perform backups."
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml26(td)
-msgid "mount_point = /var/lib/mongodb"
-msgstr "mount_point = /var/lib/mongodb"
+#: ./doc/common/tables/trove-db_percona.xml26(td)
+#: ./doc/common/tables/trove-db_mysql.xml26(td)
+msgid "mount_point = /var/lib/mysql"
+msgstr "mount_point = /var/lib/mysql"
 
-#: ./doc/common/tables/trove-db_mongodb.xml27(td)
+#: ./doc/common/tables/trove-db_percona.xml27(td)
 #: ./doc/common/tables/trove-db_cassandra.xml27(td)
 #: ./doc/common/tables/trove-db_mysql.xml27(td)
-#: ./doc/common/tables/trove-db_redis.xml27(td)
 #: ./doc/common/tables/trove-db_couchbase.xml27(td)
-#: ./doc/common/tables/trove-db_percona.xml27(td)
+#: ./doc/common/tables/trove-db_mongodb.xml27(td)
+#: ./doc/common/tables/trove-db_redis.xml27(td)
 msgid ""
 "(StrOpt) Filesystem path for mounting volumes if volume support is enabled"
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml30(td)
-msgid "tcp_ports = 2500, 27017"
-msgstr "tcp_ports = 2500, 27017"
+#: ./doc/common/tables/trove-db_percona.xml30(td)
+#: ./doc/common/tables/trove-db_mysql.xml30(td)
+msgid "root_on_create = False"
+msgstr "root_on_create = False"
 
-#: ./doc/common/tables/trove-db_mongodb.xml31(td)
+#: ./doc/common/tables/trove-db_percona.xml31(td)
+#: ./doc/common/tables/trove-db_mysql.xml31(td)
+msgid ""
+"(BoolOpt) Enable the automatic creation of the root user for the service "
+"during instance-create. The generated password for the root user is "
+"immediately returned in the response of instance-create as the 'password' "
+"field."
+msgstr ""
+
+#: ./doc/common/tables/trove-db_percona.xml34(td)
+#: ./doc/common/tables/trove-db_mysql.xml34(td)
+msgid "tcp_ports = 3306"
+msgstr "tcp_ports = 3306"
+
+#: ./doc/common/tables/trove-db_percona.xml35(td)
 #: ./doc/common/tables/trove-db_cassandra.xml31(td)
 #: ./doc/common/tables/trove-db_mysql.xml35(td)
-#: ./doc/common/tables/trove-db_redis.xml31(td)
 #: ./doc/common/tables/trove-db_couchbase.xml31(td)
-#: ./doc/common/tables/trove-db_percona.xml35(td)
+#: ./doc/common/tables/trove-db_mongodb.xml31(td)
+#: ./doc/common/tables/trove-db_redis.xml31(td)
 msgid ""
 "(ListOpt) List of TCP ports and/or port ranges to open in the security group"
 " (only applicable if trove_security_groups_support is True)"
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml34(td)
+#: ./doc/common/tables/trove-db_percona.xml38(td)
 #: ./doc/common/tables/trove-db_cassandra.xml34(td)
 #: ./doc/common/tables/trove-db_mysql.xml38(td)
-#: ./doc/common/tables/trove-db_redis.xml34(td)
 #: ./doc/common/tables/trove-db_couchbase.xml34(td)
-#: ./doc/common/tables/trove-db_percona.xml38(td)
+#: ./doc/common/tables/trove-db_mongodb.xml34(td)
+#: ./doc/common/tables/trove-db_redis.xml34(td)
 msgid "udp_ports ="
 msgstr "udp_ports ="
 
-#: ./doc/common/tables/trove-db_mongodb.xml35(td)
+#: ./doc/common/tables/trove-db_percona.xml39(td)
+#: ./doc/common/tables/trove-db_cassandra.xml35(td)
+#: ./doc/common/tables/trove-db_mysql.xml39(td)
+#: ./doc/common/tables/trove-db_couchbase.xml35(td)
+#: ./doc/common/tables/trove-db_redis.xml35(td)
 msgid ""
-"(ListOpt) List of UPD ports and/or port ranges to open in the security group"
+"(ListOpt) List of UDP ports and/or port ranges to open in the security group"
 " (only applicable if trove_security_groups_support is True)"
 msgstr ""
 
+#: ./doc/common/tables/trove-db_percona.xml42(td)
+#: ./doc/common/tables/trove-db_couchbase.xml38(td)
 #: ./doc/common/tables/trove-db_mongodb.xml38(td)
 #: ./doc/common/tables/trove-db_redis.xml38(td)
-#: ./doc/common/tables/trove-db_couchbase.xml38(td)
-#: ./doc/common/tables/trove-db_percona.xml42(td)
 msgid "usage_timeout = 450"
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml39(td)
+#: ./doc/common/tables/trove-db_percona.xml43(td)
 #: ./doc/common/tables/trove-db_cassandra.xml39(td)
 #: ./doc/common/tables/trove-db_mysql.xml43(td)
-#: ./doc/common/tables/trove-db_redis.xml39(td)
 #: ./doc/common/tables/trove-db_couchbase.xml39(td)
-#: ./doc/common/tables/trove-db_percona.xml43(td)
+#: ./doc/common/tables/trove-db_mongodb.xml39(td)
+#: ./doc/common/tables/trove-db_redis.xml39(td)
 msgid "(IntOpt) Timeout to wait for a guest to become active."
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml8(caption)
-#: ./doc/common/tables/trove-debug.xml8(caption)
-#: ./doc/common/tables/heat-debug.xml8(caption)
-msgid "Description of configuration options for debug"
+#: ./doc/common/tables/nova-periodic.xml8(caption)
+msgid "Description of configuration options for periodic"
+msgstr ""
+
+#: ./doc/common/tables/nova-periodic.xml22(td)
+msgid "periodic_enable = True"
+msgstr "periodic_enable = True"
+
+#: ./doc/common/tables/nova-periodic.xml23(td)
+msgid "(BoolOpt) Enable periodic tasks"
+msgstr ""
+
+#: ./doc/common/tables/nova-periodic.xml26(td)
+#: ./doc/common/tables/cinder-common.xml130(td)
+msgid "periodic_fuzzy_delay = 60"
+msgstr ""
+
+#: ./doc/common/tables/nova-periodic.xml27(td)
+#: ./doc/common/tables/neutron-common.xml163(td)
+msgid ""
+"(IntOpt) Range of seconds to randomly delay when starting the periodic task "
+"scheduler to reduce stampeding. (Disable by setting to 0)"
+msgstr ""
+
+#: ./doc/common/tables/nova-periodic.xml30(td)
+#: ./doc/common/tables/cinder-common.xml158(td)
+#: ./doc/common/tables/neutron-api.xml54(td)
+msgid "run_external_periodic_tasks = True"
+msgstr "run_external_periodic_tasks = True"
+
+#: ./doc/common/tables/nova-periodic.xml31(td)
+#: ./doc/common/tables/cinder-common.xml159(td)
+#: ./doc/common/tables/neutron-api.xml55(td)
+msgid ""
+"(BoolOpt) Some periodic tasks can be run in a separate process. Should we "
+"run them here?"
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml8(caption)
+#: ./doc/common/tables/cinder-auth.xml8(caption)
+#: ./doc/common/tables/ceilometer-auth.xml8(caption)
+msgid "Description of configuration options for auth"
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml19(th)
+msgid "[auth]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml22(td)
+msgid "external = keystone.auth.plugins.external.DefaultDomain"
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml23(td)
+msgid "(StrOpt) The external (REMOTE_USER) auth plugin module."
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml26(td)
+msgid "methods = external, password, token"
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml27(td)
+msgid "(ListOpt) Default auth methods."
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml30(td)
+msgid "password = keystone.auth.plugins.password.Password"
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml31(td)
+msgid "(StrOpt) The password auth plugin module."
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml34(td)
+msgid "token = keystone.auth.plugins.token.Token"
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml35(td)
+msgid "(StrOpt) The token auth plugin module."
+msgstr ""
+
+#: ./doc/common/tables/keystone-policy.xml8(caption)
+#: ./doc/common/tables/neutron-policy.xml8(caption)
+#: ./doc/common/tables/nova-policy.xml8(caption)
+#: ./doc/common/tables/glance-policy.xml8(caption)
+msgid "Description of configuration options for policy"
+msgstr ""
+
+#: ./doc/common/tables/keystone-policy.xml22(td)
+#: ./doc/common/tables/nova-policy.xml58(td)
+#: ./doc/common/tables/glance-policy.xml22(td)
+#: ./doc/common/tables/ceilometer-api.xml34(td)
+#: ./doc/common/tables/heat-api.xml42(td)
+#: ./doc/common/tables/cinder-common.xml138(td)
+msgid "policy_default_rule = default"
+msgstr "policy_default_rule = default"
+
+#: ./doc/common/tables/keystone-policy.xml23(td)
+#: ./doc/common/tables/ceilometer-api.xml35(td)
+#: ./doc/common/tables/heat-api.xml43(td)
+msgid "(StrOpt) Rule enforced when requested rule is not found"
+msgstr ""
+
+#: ./doc/common/tables/keystone-policy.xml26(td)
+#: ./doc/common/tables/neutron-policy.xml26(td)
+#: ./doc/common/tables/nova-policy.xml62(td)
+#: ./doc/common/tables/glance-policy.xml26(td)
+#: ./doc/common/tables/ceilometer-api.xml38(td)
+#: ./doc/common/tables/heat-api.xml46(td)
+#: ./doc/common/tables/cinder-common.xml142(td)
+msgid "policy_file = policy.json"
+msgstr "policy_file = policy.json"
+
+#: ./doc/common/tables/keystone-policy.xml27(td)
+#: ./doc/common/tables/ceilometer-api.xml39(td)
+#: ./doc/common/tables/heat-api.xml47(td)
+msgid "(StrOpt) JSON file containing policy"
+msgstr ""
+
+#: ./doc/common/tables/keystone-policy.xml30(th)
+msgid "[policy]"
+msgstr "[policy]"
+
+#: ./doc/common/tables/keystone-policy.xml33(td)
+msgid "driver = keystone.policy.backends.sql.Policy"
+msgstr ""
+
+#: ./doc/common/tables/keystone-policy.xml34(td)
+msgid "(StrOpt) Keystone Policy backend driver."
+msgstr ""
+
+#: ./doc/common/tables/keystone-policy.xml37(td)
+#: ./doc/common/tables/keystone-api.xml46(td)
+#: ./doc/common/tables/keystone-identity.xml38(td)
+#: ./doc/common/tables/keystone-catalog.xml26(td)
+#: ./doc/common/tables/keystone-assignment.xml34(td)
+msgid "list_limit = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-policy.xml38(td)
+msgid ""
+"(IntOpt) Maximum number of entities that will be returned in a policy "
+"collection."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml8(caption)
+#: ./doc/common/tables/neutron-auth_token.xml8(caption)
+#: ./doc/common/tables/heat-auth_token.xml8(caption)
+#: ./doc/common/tables/nova-auth_token.xml8(caption)
+#: ./doc/common/tables/cinder-auth_token.xml8(caption)
+#: ./doc/common/tables/keystone-auth_token.xml8(caption)
+#: ./doc/common/tables/trove-auth_token.xml8(caption)
+msgid "Description of configuration options for auth_token"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml22(td)
+#: ./doc/common/tables/glance-auth_token.xml117(td)
+#: ./doc/common/tables/ceilometer-common.xml38(td)
+#: ./doc/common/tables/neutron-auth_token.xml22(td)
+#: ./doc/common/tables/neutron-auth_token.xml117(td)
+#: ./doc/common/tables/ceilometer-auth.xml117(td)
+#: ./doc/common/tables/nova-common.xml50(td)
+#: ./doc/common/tables/heat-auth_token.xml22(td)
+#: ./doc/common/tables/heat-auth_token.xml117(td)
+#: ./doc/common/tables/nova-auth_token.xml110(td)
+#: ./doc/common/tables/cinder-auth_token.xml22(td)
+#: ./doc/common/tables/cinder-auth_token.xml117(td)
+#: ./doc/common/tables/keystone-auth_token.xml22(td)
+#: ./doc/common/tables/keystone-auth_token.xml117(td)
+#: ./doc/common/tables/trove-auth_token.xml22(td)
+#: ./doc/common/tables/trove-auth_token.xml117(td)
+msgid "memcached_servers = None"
+msgstr "memcached_servers = None"
+
+#: ./doc/common/tables/glance-auth_token.xml23(td)
+#: ./doc/common/tables/ceilometer-common.xml39(td)
+#: ./doc/common/tables/neutron-auth_token.xml23(td)
+#: ./doc/common/tables/nova-common.xml51(td)
+#: ./doc/common/tables/heat-auth_token.xml23(td)
+#: ./doc/common/tables/cinder-auth_token.xml23(td)
+#: ./doc/common/tables/keystone-auth_token.xml23(td)
+#: ./doc/common/tables/trove-auth_token.xml23(td)
+msgid "(ListOpt) Memcached servers or None for in process cache."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml26(th)
+#: ./doc/common/tables/neutron-auth_token.xml26(th)
+#: ./doc/common/tables/ceilometer-auth.xml26(th)
+#: ./doc/common/tables/heat-auth_token.xml26(th)
+#: ./doc/common/tables/nova-auth_token.xml19(th)
+#: ./doc/common/tables/cinder-auth_token.xml26(th)
+#: ./doc/common/tables/keystone-auth_token.xml26(th)
+#: ./doc/common/tables/trove-auth_token.xml26(th)
+msgid "[keystone_authtoken]"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml29(td)
+#: ./doc/common/tables/neutron-auth_token.xml29(td)
+#: ./doc/common/tables/ceilometer-auth.xml29(td)
+#: ./doc/common/tables/glance-registry.xml22(td)
+#: ./doc/common/tables/heat-auth_token.xml29(td)
+#: ./doc/common/tables/nova-auth_token.xml22(td)
+#: ./doc/common/tables/cinder-auth_token.xml29(td)
+#: ./doc/common/tables/keystone-auth_token.xml29(td)
+#: ./doc/common/tables/neutron-embrane_lb.xml22(td)
+#: ./doc/common/tables/trove-auth_token.xml29(td)
+#: ./doc/common/tables/neutron-common.xml22(td)
+#: ./doc/common/tables/neutron-common.xml192(td)
+#: ./doc/common/tables/neutron-common.xml219(td)
+msgid "admin_password = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml30(td)
+#: ./doc/common/tables/neutron-auth_token.xml30(td)
+#: ./doc/common/tables/ceilometer-auth.xml30(td)
+#: ./doc/common/tables/heat-auth_token.xml30(td)
+#: ./doc/common/tables/nova-auth_token.xml23(td)
+#: ./doc/common/tables/cinder-auth_token.xml30(td)
+#: ./doc/common/tables/keystone-auth_token.xml30(td)
+#: ./doc/common/tables/trove-auth_token.xml30(td)
+msgid "(StrOpt) Keystone account password"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml33(td)
+#: ./doc/common/tables/neutron-auth_token.xml33(td)
+#: ./doc/common/tables/ceilometer-auth.xml33(td)
+#: ./doc/common/tables/heat-auth_token.xml33(td)
+#: ./doc/common/tables/nova-auth_token.xml26(td)
+#: ./doc/common/tables/cinder-auth_token.xml33(td)
+#: ./doc/common/tables/keystone-auth_token.xml33(td)
+#: ./doc/common/tables/trove-auth_token.xml33(td)
+msgid "admin_tenant_name = admin"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml34(td)
+#: ./doc/common/tables/neutron-auth_token.xml34(td)
+#: ./doc/common/tables/ceilometer-auth.xml34(td)
+#: ./doc/common/tables/heat-auth_token.xml34(td)
+#: ./doc/common/tables/nova-auth_token.xml27(td)
+#: ./doc/common/tables/cinder-auth_token.xml34(td)
+#: ./doc/common/tables/keystone-auth_token.xml34(td)
+#: ./doc/common/tables/trove-auth_token.xml34(td)
+msgid "(StrOpt) Keystone service account tenant name to validate user tokens"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml37(td)
+#: ./doc/common/tables/neutron-auth_token.xml37(td)
+#: ./doc/common/tables/ceilometer-auth.xml37(td)
+#: ./doc/common/tables/heat-auth_token.xml37(td)
+#: ./doc/common/tables/nova-auth_token.xml30(td)
+#: ./doc/common/tables/cinder-auth_token.xml37(td)
+#: ./doc/common/tables/keystone-auth_token.xml37(td)
+#: ./doc/common/tables/trove-auth_token.xml37(td)
+msgid "admin_token = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml38(td)
+#: ./doc/common/tables/neutron-auth_token.xml38(td)
+#: ./doc/common/tables/ceilometer-auth.xml38(td)
+#: ./doc/common/tables/heat-auth_token.xml38(td)
+#: ./doc/common/tables/nova-auth_token.xml31(td)
+#: ./doc/common/tables/cinder-auth_token.xml38(td)
+#: ./doc/common/tables/keystone-auth_token.xml38(td)
+#: ./doc/common/tables/trove-auth_token.xml38(td)
+msgid ""
+"(StrOpt) Single shared secret with the Keystone configuration used for "
+"bootstrapping a Keystone installation, or otherwise bypassing the normal "
+"authentication process."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml41(td)
+#: ./doc/common/tables/neutron-auth_token.xml41(td)
+#: ./doc/common/tables/ceilometer-auth.xml41(td)
+#: ./doc/common/tables/glance-registry.xml30(td)
+#: ./doc/common/tables/heat-auth_token.xml41(td)
+#: ./doc/common/tables/nova-auth_token.xml34(td)
+#: ./doc/common/tables/cinder-auth_token.xml41(td)
+#: ./doc/common/tables/keystone-auth_token.xml41(td)
+#: ./doc/common/tables/trove-auth_token.xml41(td)
+#: ./doc/common/tables/neutron-common.xml30(td)
+#: ./doc/common/tables/neutron-common.xml200(td)
+msgid "admin_user = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml42(td)
+#: ./doc/common/tables/neutron-auth_token.xml42(td)
+#: ./doc/common/tables/ceilometer-auth.xml42(td)
+#: ./doc/common/tables/heat-auth_token.xml42(td)
+#: ./doc/common/tables/nova-auth_token.xml35(td)
+#: ./doc/common/tables/cinder-auth_token.xml42(td)
+#: ./doc/common/tables/keystone-auth_token.xml42(td)
+#: ./doc/common/tables/trove-auth_token.xml42(td)
+msgid "(StrOpt) Keystone account username"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml45(td)
+#: ./doc/common/tables/neutron-auth_token.xml45(td)
+#: ./doc/common/tables/ceilometer-auth.xml45(td)
+#: ./doc/common/tables/heat-auth_token.xml45(td)
+#: ./doc/common/tables/nova-auth_token.xml38(td)
+#: ./doc/common/tables/cinder-auth_token.xml45(td)
+#: ./doc/common/tables/keystone-auth_token.xml45(td)
+#: ./doc/common/tables/trove-auth_token.xml45(td)
+msgid "auth_admin_prefix ="
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml46(td)
+#: ./doc/common/tables/neutron-auth_token.xml46(td)
+#: ./doc/common/tables/ceilometer-auth.xml46(td)
+#: ./doc/common/tables/heat-auth_token.xml46(td)
+#: ./doc/common/tables/nova-auth_token.xml39(td)
+#: ./doc/common/tables/cinder-auth_token.xml46(td)
+#: ./doc/common/tables/keystone-auth_token.xml46(td)
+#: ./doc/common/tables/trove-auth_token.xml46(td)
+msgid "(StrOpt) Prefix to prepend at the beginning of the path"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml49(td)
+#: ./doc/common/tables/neutron-auth_token.xml49(td)
+#: ./doc/common/tables/ceilometer-auth.xml49(td)
+#: ./doc/common/tables/heat-auth_token.xml49(td)
+#: ./doc/common/tables/nova-auth_token.xml42(td)
+#: ./doc/common/tables/cinder-auth_token.xml49(td)
+#: ./doc/common/tables/keystone-auth_token.xml49(td)
+#: ./doc/common/tables/trove-auth_token.xml49(td)
+msgid "auth_host = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml50(td)
+#: ./doc/common/tables/neutron-auth_token.xml50(td)
+#: ./doc/common/tables/ceilometer-auth.xml50(td)
+#: ./doc/common/tables/heat-auth_token.xml50(td)
+#: ./doc/common/tables/nova-auth_token.xml43(td)
+#: ./doc/common/tables/cinder-auth_token.xml50(td)
+#: ./doc/common/tables/keystone-auth_token.xml50(td)
+#: ./doc/common/tables/trove-auth_token.xml50(td)
+msgid "(StrOpt) Host providing the admin Identity API endpoint"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml53(td)
+#: ./doc/common/tables/neutron-auth_token.xml53(td)
+#: ./doc/common/tables/ceilometer-auth.xml53(td)
+#: ./doc/common/tables/heat-auth_token.xml53(td)
+#: ./doc/common/tables/nova-auth_token.xml46(td)
+#: ./doc/common/tables/cinder-auth_token.xml53(td)
+#: ./doc/common/tables/keystone-auth_token.xml53(td)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml21(td)
+#: ./doc/common/tables/trove-auth_token.xml53(td)
+msgid "auth_port = 35357"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml54(td)
+#: ./doc/common/tables/neutron-auth_token.xml54(td)
+#: ./doc/common/tables/ceilometer-auth.xml54(td)
+#: ./doc/common/tables/heat-auth_token.xml54(td)
+#: ./doc/common/tables/nova-auth_token.xml47(td)
+#: ./doc/common/tables/cinder-auth_token.xml54(td)
+#: ./doc/common/tables/keystone-auth_token.xml54(td)
+#: ./doc/common/tables/trove-auth_token.xml54(td)
+msgid "(IntOpt) Port of the admin Identity API endpoint"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml57(td)
+#: ./doc/common/tables/neutron-auth_token.xml57(td)
+#: ./doc/common/tables/ceilometer-auth.xml57(td)
+#: ./doc/common/tables/heat-auth_token.xml57(td)
+#: ./doc/common/tables/nova-auth_token.xml50(td)
+#: ./doc/common/tables/cinder-auth_token.xml57(td)
+#: ./doc/common/tables/keystone-auth_token.xml57(td)
+#: ./doc/common/tables/trove-auth_token.xml57(td)
+msgid "auth_protocol = https"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml58(td)
+#: ./doc/common/tables/neutron-auth_token.xml58(td)
+#: ./doc/common/tables/ceilometer-auth.xml58(td)
+#: ./doc/common/tables/heat-auth_token.xml58(td)
+#: ./doc/common/tables/nova-auth_token.xml51(td)
+#: ./doc/common/tables/cinder-auth_token.xml58(td)
+#: ./doc/common/tables/keystone-auth_token.xml58(td)
+#: ./doc/common/tables/trove-auth_token.xml58(td)
+msgid "(StrOpt) Protocol of the admin Identity API endpoint(http or https)"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml61(td)
+#: ./doc/common/tables/neutron-auth_token.xml61(td)
+#: ./doc/common/tables/ceilometer-auth.xml61(td)
+#: ./doc/common/tables/heat-auth_token.xml61(td)
+#: ./doc/common/tables/nova-auth_token.xml54(td)
+#: ./doc/common/tables/heat-api.xml92(td)
+#: ./doc/common/tables/cinder-auth_token.xml61(td)
+#: ./doc/common/tables/keystone-auth_token.xml61(td)
+#: ./doc/common/tables/trove-auth_token.xml61(td)
+msgid "auth_uri = None"
+msgstr "auth_uri = None"
+
+#: ./doc/common/tables/glance-auth_token.xml62(td)
+#: ./doc/common/tables/neutron-auth_token.xml62(td)
+#: ./doc/common/tables/ceilometer-auth.xml62(td)
+#: ./doc/common/tables/heat-auth_token.xml62(td)
+#: ./doc/common/tables/nova-auth_token.xml55(td)
+#: ./doc/common/tables/cinder-auth_token.xml62(td)
+#: ./doc/common/tables/keystone-auth_token.xml62(td)
+#: ./doc/common/tables/trove-auth_token.xml62(td)
+msgid "(StrOpt) Complete public Identity API endpoint"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml65(td)
+#: ./doc/common/tables/neutron-auth_token.xml65(td)
+#: ./doc/common/tables/ceilometer-auth.xml65(td)
+#: ./doc/common/tables/heat-auth_token.xml65(td)
+#: ./doc/common/tables/nova-auth_token.xml58(td)
+#: ./doc/common/tables/cinder-auth_token.xml65(td)
+#: ./doc/common/tables/keystone-auth_token.xml65(td)
+#: ./doc/common/tables/trove-auth_token.xml65(td)
+msgid "auth_version = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml66(td)
+#: ./doc/common/tables/neutron-auth_token.xml66(td)
+#: ./doc/common/tables/ceilometer-auth.xml66(td)
+#: ./doc/common/tables/heat-auth_token.xml66(td)
+#: ./doc/common/tables/nova-auth_token.xml59(td)
+#: ./doc/common/tables/cinder-auth_token.xml66(td)
+#: ./doc/common/tables/keystone-auth_token.xml66(td)
+#: ./doc/common/tables/trove-auth_token.xml66(td)
+msgid "(StrOpt) API version of the admin Identity API endpoint"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml69(td)
+#: ./doc/common/tables/neutron-auth_token.xml69(td)
+#: ./doc/common/tables/ceilometer-auth.xml69(td)
+#: ./doc/common/tables/heat-auth_token.xml69(td)
+#: ./doc/common/tables/nova-auth_token.xml62(td)
+#: ./doc/common/tables/cinder-auth_token.xml69(td)
+#: ./doc/common/tables/keystone-auth_token.xml69(td)
+#: ./doc/common/tables/trove-auth_token.xml69(td)
+msgid "cache = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml70(td)
+#: ./doc/common/tables/neutron-auth_token.xml70(td)
+#: ./doc/common/tables/ceilometer-auth.xml70(td)
+#: ./doc/common/tables/heat-auth_token.xml70(td)
+#: ./doc/common/tables/nova-auth_token.xml63(td)
+#: ./doc/common/tables/cinder-auth_token.xml70(td)
+#: ./doc/common/tables/keystone-auth_token.xml70(td)
+#: ./doc/common/tables/trove-auth_token.xml70(td)
+msgid "(StrOpt) Env key for the swift cache"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml73(td)
+#: ./doc/common/tables/neutron-auth_token.xml73(td)
+#: ./doc/common/tables/ceilometer-auth.xml73(td)
+#: ./doc/common/tables/heat-auth_token.xml73(td)
+#: ./doc/common/tables/nova-auth_token.xml66(td)
+#: ./doc/common/tables/cinder-auth_token.xml73(td)
+#: ./doc/common/tables/keystone-auth_token.xml73(td)
+#: ./doc/common/tables/trove-auth_token.xml73(td)
+msgid "cafile = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml74(td)
+#: ./doc/common/tables/neutron-auth_token.xml74(td)
+#: ./doc/common/tables/ceilometer-auth.xml74(td)
+#: ./doc/common/tables/heat-auth_token.xml74(td)
+#: ./doc/common/tables/nova-auth_token.xml67(td)
+#: ./doc/common/tables/cinder-auth_token.xml74(td)
+#: ./doc/common/tables/keystone-auth_token.xml74(td)
+#: ./doc/common/tables/trove-auth_token.xml74(td)
+msgid ""
+"(StrOpt) A PEM encoded Certificate Authority to use when verifying HTTPs "
+"connections. Defaults to system CAs."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml77(td)
+#: ./doc/common/tables/neutron-auth_token.xml77(td)
+#: ./doc/common/tables/ceilometer-auth.xml77(td)
+#: ./doc/common/tables/heat-auth_token.xml77(td)
+#: ./doc/common/tables/nova-auth_token.xml70(td)
+#: ./doc/common/tables/cinder-auth_token.xml77(td)
+#: ./doc/common/tables/keystone-auth_token.xml77(td)
+#: ./doc/common/tables/trove-auth_token.xml77(td)
+msgid "certfile = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml78(td)
+#: ./doc/common/tables/glance-auth_token.xml106(td)
+#: ./doc/common/tables/neutron-auth_token.xml78(td)
+#: ./doc/common/tables/neutron-auth_token.xml106(td)
+#: ./doc/common/tables/ceilometer-auth.xml78(td)
+#: ./doc/common/tables/ceilometer-auth.xml106(td)
+#: ./doc/common/tables/heat-auth_token.xml78(td)
+#: ./doc/common/tables/heat-auth_token.xml106(td)
+#: ./doc/common/tables/nova-auth_token.xml71(td)
+#: ./doc/common/tables/nova-auth_token.xml99(td)
+#: ./doc/common/tables/cinder-auth_token.xml78(td)
+#: ./doc/common/tables/cinder-auth_token.xml106(td)
+#: ./doc/common/tables/keystone-auth_token.xml78(td)
+#: ./doc/common/tables/keystone-auth_token.xml106(td)
+#: ./doc/common/tables/trove-auth_token.xml78(td)
+#: ./doc/common/tables/trove-auth_token.xml106(td)
+msgid "(StrOpt) Required if Keystone server requires client certificate"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml81(td)
+#: ./doc/common/tables/neutron-auth_token.xml81(td)
+#: ./doc/common/tables/ceilometer-auth.xml81(td)
+#: ./doc/common/tables/heat-auth_token.xml81(td)
+#: ./doc/common/tables/nova-auth_token.xml74(td)
+#: ./doc/common/tables/cinder-auth_token.xml81(td)
+#: ./doc/common/tables/keystone-auth_token.xml81(td)
+#: ./doc/common/tables/trove-auth_token.xml81(td)
+msgid "delay_auth_decision = False"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml82(td)
+#: ./doc/common/tables/neutron-auth_token.xml82(td)
+#: ./doc/common/tables/ceilometer-auth.xml82(td)
+#: ./doc/common/tables/heat-auth_token.xml82(td)
+#: ./doc/common/tables/nova-auth_token.xml75(td)
+#: ./doc/common/tables/cinder-auth_token.xml82(td)
+#: ./doc/common/tables/keystone-auth_token.xml82(td)
+#: ./doc/common/tables/trove-auth_token.xml82(td)
+msgid ""
+"(BoolOpt) Do not handle authorization requests within the middleware, but "
+"delegate the authorization decision to downstream WSGI components"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml85(td)
+#: ./doc/common/tables/neutron-auth_token.xml85(td)
+#: ./doc/common/tables/ceilometer-auth.xml85(td)
+#: ./doc/common/tables/heat-auth_token.xml85(td)
+#: ./doc/common/tables/nova-auth_token.xml78(td)
+#: ./doc/common/tables/cinder-auth_token.xml85(td)
+#: ./doc/common/tables/keystone-auth_token.xml85(td)
+#: ./doc/common/tables/trove-auth_token.xml85(td)
+#: ./doc/common/tables/keystone-token.xml38(td)
+msgid "enforce_token_bind = permissive"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml86(td)
+#: ./doc/common/tables/neutron-auth_token.xml86(td)
+#: ./doc/common/tables/ceilometer-auth.xml86(td)
+#: ./doc/common/tables/heat-auth_token.xml86(td)
+#: ./doc/common/tables/nova-auth_token.xml79(td)
+#: ./doc/common/tables/cinder-auth_token.xml86(td)
+#: ./doc/common/tables/keystone-auth_token.xml86(td)
+#: ./doc/common/tables/trove-auth_token.xml86(td)
+msgid ""
+"(StrOpt) Used to control the use and type of token binding. Can be set to: "
+"\"disabled\" to not check token binding. \"permissive\" (default) to "
+"validate binding information if the bind type is of a form known to the "
+"server and ignore it if not. \"strict\" like \"permissive\" but if the bind "
+"type is unknown the token will be rejected. \"required\" any form of token "
+"binding is needed to be allowed. Finally the name of a binding method that "
+"must be present in tokens."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml89(td)
+#: ./doc/common/tables/neutron-auth_token.xml89(td)
+#: ./doc/common/tables/ceilometer-auth.xml89(td)
+#: ./doc/common/tables/heat-auth_token.xml89(td)
+#: ./doc/common/tables/nova-auth_token.xml82(td)
+#: ./doc/common/tables/cinder-auth_token.xml89(td)
+#: ./doc/common/tables/keystone-auth_token.xml89(td)
+#: ./doc/common/tables/trove-auth_token.xml89(td)
+msgid "http_connect_timeout = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml90(td)
+#: ./doc/common/tables/neutron-auth_token.xml90(td)
+#: ./doc/common/tables/ceilometer-auth.xml90(td)
+#: ./doc/common/tables/heat-auth_token.xml90(td)
+#: ./doc/common/tables/nova-auth_token.xml83(td)
+#: ./doc/common/tables/cinder-auth_token.xml90(td)
+#: ./doc/common/tables/keystone-auth_token.xml90(td)
+#: ./doc/common/tables/trove-auth_token.xml90(td)
+msgid ""
+"(BoolOpt) Request timeout value for communicating with Identity API server."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml93(td)
+#: ./doc/common/tables/neutron-auth_token.xml93(td)
+#: ./doc/common/tables/ceilometer-auth.xml93(td)
+#: ./doc/common/tables/heat-auth_token.xml93(td)
+#: ./doc/common/tables/nova-auth_token.xml86(td)
+#: ./doc/common/tables/cinder-auth_token.xml93(td)
+#: ./doc/common/tables/keystone-auth_token.xml93(td)
+#: ./doc/common/tables/trove-auth_token.xml93(td)
+msgid "http_request_max_retries = 3"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml94(td)
+#: ./doc/common/tables/neutron-auth_token.xml94(td)
+#: ./doc/common/tables/ceilometer-auth.xml94(td)
+#: ./doc/common/tables/heat-auth_token.xml94(td)
+#: ./doc/common/tables/nova-auth_token.xml87(td)
+#: ./doc/common/tables/cinder-auth_token.xml94(td)
+#: ./doc/common/tables/keystone-auth_token.xml94(td)
+#: ./doc/common/tables/trove-auth_token.xml94(td)
+msgid ""
+"(IntOpt) How many times are we trying to reconnect when communicating with "
+"Identity API Server."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml97(td)
+#: ./doc/common/tables/neutron-auth_token.xml97(td)
+#: ./doc/common/tables/ceilometer-auth.xml97(td)
+#: ./doc/common/tables/heat-auth_token.xml97(td)
+#: ./doc/common/tables/nova-auth_token.xml90(td)
+#: ./doc/common/tables/cinder-auth_token.xml97(td)
+#: ./doc/common/tables/keystone-auth_token.xml97(td)
+#: ./doc/common/tables/trove-auth_token.xml97(td)
+msgid "include_service_catalog = True"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml98(td)
+#: ./doc/common/tables/neutron-auth_token.xml98(td)
+#: ./doc/common/tables/ceilometer-auth.xml98(td)
+#: ./doc/common/tables/heat-auth_token.xml98(td)
+#: ./doc/common/tables/nova-auth_token.xml91(td)
+#: ./doc/common/tables/cinder-auth_token.xml98(td)
+#: ./doc/common/tables/keystone-auth_token.xml98(td)
+#: ./doc/common/tables/trove-auth_token.xml98(td)
+msgid ""
+"(BoolOpt) (optional) indicate whether to set the X-Service-Catalog header. "
+"If False, middleware will not ask for service catalog on token validation "
+"and will not set the X-Service-Catalog header."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml102(td)
+#: ./doc/common/tables/neutron-auth_token.xml102(td)
+#: ./doc/common/tables/ceilometer-auth.xml102(td)
+#: ./doc/common/tables/heat-auth_token.xml102(td)
+#: ./doc/common/tables/nova-auth_token.xml95(td)
+#: ./doc/common/tables/cinder-auth_token.xml102(td)
+#: ./doc/common/tables/keystone-auth_token.xml102(td)
+#: ./doc/common/tables/trove-auth_token.xml102(td)
+msgid "(BoolOpt) Verify HTTPS connections."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml105(td)
+#: ./doc/common/tables/neutron-auth_token.xml105(td)
+#: ./doc/common/tables/ceilometer-auth.xml105(td)
+#: ./doc/common/tables/heat-auth_token.xml105(td)
+#: ./doc/common/tables/nova-auth_token.xml98(td)
+#: ./doc/common/tables/cinder-auth_token.xml105(td)
+#: ./doc/common/tables/keystone-auth_token.xml105(td)
+#: ./doc/common/tables/trove-auth_token.xml105(td)
+msgid "keyfile = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml109(td)
+#: ./doc/common/tables/neutron-auth_token.xml109(td)
+#: ./doc/common/tables/ceilometer-auth.xml109(td)
+#: ./doc/common/tables/heat-auth_token.xml109(td)
+#: ./doc/common/tables/nova-auth_token.xml102(td)
+#: ./doc/common/tables/cinder-auth_token.xml109(td)
+#: ./doc/common/tables/keystone-auth_token.xml109(td)
+#: ./doc/common/tables/trove-auth_token.xml109(td)
+msgid "memcache_secret_key = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml110(td)
+#: ./doc/common/tables/neutron-auth_token.xml110(td)
+#: ./doc/common/tables/ceilometer-auth.xml110(td)
+#: ./doc/common/tables/heat-auth_token.xml110(td)
+#: ./doc/common/tables/nova-auth_token.xml103(td)
+#: ./doc/common/tables/cinder-auth_token.xml110(td)
+#: ./doc/common/tables/keystone-auth_token.xml110(td)
+#: ./doc/common/tables/trove-auth_token.xml110(td)
+msgid ""
+"(StrOpt) (optional, mandatory if memcache_security_strategy is defined) this"
+" string is used for key derivation."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml113(td)
+#: ./doc/common/tables/neutron-auth_token.xml113(td)
+#: ./doc/common/tables/ceilometer-auth.xml113(td)
+#: ./doc/common/tables/heat-auth_token.xml113(td)
+#: ./doc/common/tables/nova-auth_token.xml106(td)
+#: ./doc/common/tables/cinder-auth_token.xml113(td)
+#: ./doc/common/tables/keystone-auth_token.xml113(td)
+#: ./doc/common/tables/trove-auth_token.xml113(td)
+msgid "memcache_security_strategy = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml114(td)
+#: ./doc/common/tables/neutron-auth_token.xml114(td)
+#: ./doc/common/tables/ceilometer-auth.xml114(td)
+#: ./doc/common/tables/heat-auth_token.xml114(td)
+#: ./doc/common/tables/nova-auth_token.xml107(td)
+#: ./doc/common/tables/cinder-auth_token.xml114(td)
+#: ./doc/common/tables/keystone-auth_token.xml114(td)
+#: ./doc/common/tables/trove-auth_token.xml114(td)
+msgid ""
+"(StrOpt) (optional) if defined, indicate whether token data should be "
+"authenticated or authenticated and encrypted. Acceptable values are MAC or "
+"ENCRYPT. If MAC, token data is authenticated (with HMAC) in the cache. If "
+"ENCRYPT, token data is encrypted and authenticated in the cache. If the "
+"value is not one of these options or empty, auth_token will raise an "
+"exception on initialization."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml118(td)
+#: ./doc/common/tables/neutron-auth_token.xml118(td)
+#: ./doc/common/tables/ceilometer-auth.xml118(td)
+#: ./doc/common/tables/heat-auth_token.xml118(td)
+#: ./doc/common/tables/nova-auth_token.xml111(td)
+#: ./doc/common/tables/cinder-auth_token.xml118(td)
+#: ./doc/common/tables/keystone-auth_token.xml118(td)
+#: ./doc/common/tables/trove-auth_token.xml118(td)
+msgid ""
+"(ListOpt) Optionally specify a list of memcached server(s) to use for "
+"caching. If left undefined, tokens will instead be cached in-process."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml121(td)
+#: ./doc/common/tables/neutron-auth_token.xml121(td)
+#: ./doc/common/tables/ceilometer-auth.xml121(td)
+#: ./doc/common/tables/heat-auth_token.xml121(td)
+#: ./doc/common/tables/nova-auth_token.xml114(td)
+#: ./doc/common/tables/cinder-auth_token.xml121(td)
+#: ./doc/common/tables/keystone-auth_token.xml121(td)
+#: ./doc/common/tables/trove-auth_token.xml121(td)
+msgid "revocation_cache_time = 300"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml122(td)
+#: ./doc/common/tables/neutron-auth_token.xml122(td)
+#: ./doc/common/tables/ceilometer-auth.xml122(td)
+#: ./doc/common/tables/heat-auth_token.xml122(td)
+#: ./doc/common/tables/nova-auth_token.xml115(td)
+#: ./doc/common/tables/cinder-auth_token.xml122(td)
+#: ./doc/common/tables/keystone-auth_token.xml122(td)
+#: ./doc/common/tables/trove-auth_token.xml122(td)
+msgid ""
+"(IntOpt) Determines the frequency at which the list of revoked tokens is "
+"retrieved from the Identity service (in seconds). A high number of "
+"revocation events combined with a low cache duration may significantly "
+"reduce performance."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml125(td)
+#: ./doc/common/tables/neutron-auth_token.xml125(td)
+#: ./doc/common/tables/ceilometer-auth.xml125(td)
+#: ./doc/common/tables/heat-auth_token.xml125(td)
+#: ./doc/common/tables/nova-auth_token.xml118(td)
+#: ./doc/common/tables/cinder-auth_token.xml125(td)
+#: ./doc/common/tables/keystone-auth_token.xml125(td)
+#: ./doc/common/tables/trove-auth_token.xml125(td)
+msgid "signing_dir = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml126(td)
+#: ./doc/common/tables/neutron-auth_token.xml126(td)
+#: ./doc/common/tables/ceilometer-auth.xml126(td)
+#: ./doc/common/tables/heat-auth_token.xml126(td)
+#: ./doc/common/tables/nova-auth_token.xml119(td)
+#: ./doc/common/tables/cinder-auth_token.xml126(td)
+#: ./doc/common/tables/keystone-auth_token.xml126(td)
+#: ./doc/common/tables/trove-auth_token.xml126(td)
+msgid "(StrOpt) Directory used to cache files related to PKI tokens"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml129(td)
+#: ./doc/common/tables/neutron-auth_token.xml129(td)
+#: ./doc/common/tables/ceilometer-auth.xml129(td)
+#: ./doc/common/tables/heat-auth_token.xml129(td)
+#: ./doc/common/tables/nova-auth_token.xml122(td)
+#: ./doc/common/tables/cinder-auth_token.xml129(td)
+#: ./doc/common/tables/keystone-auth_token.xml129(td)
+#: ./doc/common/tables/trove-auth_token.xml129(td)
+msgid "token_cache_time = 300"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml130(td)
+#: ./doc/common/tables/neutron-auth_token.xml130(td)
+#: ./doc/common/tables/ceilometer-auth.xml130(td)
+#: ./doc/common/tables/heat-auth_token.xml130(td)
+#: ./doc/common/tables/nova-auth_token.xml123(td)
+#: ./doc/common/tables/cinder-auth_token.xml130(td)
+#: ./doc/common/tables/keystone-auth_token.xml130(td)
+#: ./doc/common/tables/trove-auth_token.xml130(td)
+msgid ""
+"(IntOpt) In order to prevent excessive effort spent validating tokens, the "
+"middleware caches previously-seen tokens for a configurable duration (in "
+"seconds). Set to -1 to disable caching completely."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml8(caption)
+msgid "Description of configuration options for netapp_7mode_nfs"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml22(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml22(td)
+msgid "expiry_thres_minutes = 720"
+msgstr "expiry_thres_minutes = 720"
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml23(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml23(td)
+msgid ""
+"(IntOpt) This option specifies the threshold for last access time for images"
+" in the NFS image cache. When a cache cleaning cycle begins, images in the "
+"cache that have not been accessed in the last M minutes, where M is the "
+"value of this parameter, will be deleted from the cache to create free space"
+" on the NFS share."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml26(td)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml26(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml22(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml22(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml30(td)
+msgid "netapp_login = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml27(td)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml27(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml23(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml23(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml31(td)
+msgid ""
+"(StrOpt) Administrative user account name used to access the storage system "
+"or proxy server."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml30(td)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml30(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml26(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml26(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml34(td)
+msgid "netapp_password = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml31(td)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml31(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml27(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml27(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml35(td)
+msgid ""
+"(StrOpt) Password for the administrative user account specified in the "
+"netapp_login option."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml34(td)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml38(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml30(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml30(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml38(td)
+msgid "netapp_server_hostname = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml35(td)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml39(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml31(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml31(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml39(td)
+msgid ""
+"(StrOpt) The hostname (or IP address) for the storage system or proxy "
+"server."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml38(td)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml42(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml34(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml34(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml42(td)
+msgid "netapp_server_port = 80"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml39(td)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml43(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml35(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml35(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml43(td)
+msgid ""
+"(IntOpt) The TCP port to use for communication with the storage system or "
+"proxy server. Traditionally, port 80 is used for HTTP and port 443 is used "
+"for HTTPS; however, this value should be changed if an alternate port has "
+"been configured on the storage system or proxy server."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml42(td)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml46(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml42(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml42(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml46(td)
+msgid "netapp_storage_family = ontap_cluster"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml43(td)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml47(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml43(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml43(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml47(td)
+msgid ""
+"(StrOpt) The storage family type used on the storage system; valid values "
+"are ontap_7mode for using Data ONTAP operating in 7-Mode, ontap_cluster for "
+"using clustered Data ONTAP, or eseries for using E-Series."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml46(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml46(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml46(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml50(td)
+msgid "netapp_storage_protocol = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml47(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml47(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml47(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml51(td)
+msgid ""
+"(StrOpt) The storage protocol to be used on the data path with the storage "
+"system; valid values are iscsi or nfs."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml50(td)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml54(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml50(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml50(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml54(td)
+msgid "netapp_transport_type = http"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml51(td)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml55(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml51(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml51(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml55(td)
+msgid ""
+"(StrOpt) The transport protocol used when communicating with the storage "
+"system or proxy server. Valid values are http or https."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml54(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml62(td)
+msgid "thres_avl_size_perc_start = 20"
+msgstr "thres_avl_size_perc_start = 20"
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml55(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml63(td)
+msgid ""
+"(IntOpt) If the percentage of available space for an NFS share has dropped "
+"below the value specified by this option, the NFS image cache will be "
+"cleaned."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml58(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml66(td)
+msgid "thres_avl_size_perc_stop = 60"
+msgstr "thres_avl_size_perc_stop = 60"
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml59(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml67(td)
+msgid ""
+"(IntOpt) When the percentage of available space on an NFS share has reached "
+"the percentage specified by this option, the driver will stop clearing files"
+" from the NFS image cache that have not been accessed in the last M minutes,"
+" where M is the value of the expiry_thres_minutes configuration option."
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml7(literal)
+msgid "[container-sync]"
+msgstr "[container-sync]"
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml7(literal)
+#: ./doc/common/tables/swift-container-server-container-auditor.xml7(literal)
+#: ./doc/common/tables/swift-container-server-filter-recon.xml7(literal)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml7(literal)
+#: ./doc/common/tables/swift-container-server-pipeline-main.xml7(literal)
+#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml7(literal)
+#: ./doc/common/tables/swift-container-server-container-updater.xml7(literal)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml7(literal)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml7(literal)
+msgid "container-server.conf-sample"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml7(caption)
+#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml7(caption)
+#: ./doc/common/tables/swift-container-server-container-auditor.xml7(caption)
+#: ./doc/common/tables/swift-swift-swift-constraints.xml7(caption)
+#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml7(caption)
+#: ./doc/common/tables/swift-container-server-filter-recon.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml7(caption)
+#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml7(caption)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml7(caption)
+#: ./doc/common/tables/swift-container-server-pipeline-main.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml7(caption)
+#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml7(caption)
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml7(caption)
+#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml7(caption)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml7(caption)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml7(caption)
+#: ./doc/common/tables/swift-rsyncd-container.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml7(caption)
+#: ./doc/common/tables/swift-rsyncd-account.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml7(caption)
+#: ./doc/common/tables/swift-account-server-filter-recon.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml7(caption)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml7(caption)
+#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml7(caption)
+#: ./doc/common/tables/swift-container-server-container-updater.xml7(caption)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml7(caption)
+#: ./doc/common/tables/swift-swift-swift-hash.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml7(caption)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml7(caption)
+#: ./doc/common/tables/swift-object-server-pipeline-main.xml7(caption)
+#: ./doc/common/tables/swift-memcache-memcache.xml7(caption)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml7(caption)
+#: ./doc/common/tables/swift-object-expirer-filter-cache.xml7(caption)
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml7(caption)
+#: ./doc/common/tables/swift-object-server-object-auditor.xml7(caption)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml7(caption)
+#: ./doc/common/tables/swift-account-server-pipeline-main.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml7(caption)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml7(caption)
+#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml7(caption)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml7(caption)
+#: ./doc/common/tables/swift-object-server-filter-recon.xml7(caption)
+#: ./doc/common/tables/swift-rsyncd-object.xml7(caption)
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml7(caption)
+#: ./doc/common/tables/swift-object-server-object-updater.xml7(caption)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml7(caption)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml7(caption)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml7(caption)
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml7(caption)
+msgid ""
+"Description of configuration options for <placeholder-1/> in "
+"<placeholder-2/>"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml18(td)
+msgid "log_name = container-sync"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml70(td)
+#: ./doc/common/tables/swift-container-server-container-auditor.xml18(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml61(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml64(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml18(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml18(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml18(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml24(td)
+#: ./doc/common/tables/swift-object-server-object-auditor.xml18(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml18(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml18(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml18(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml58(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml18(td)
+msgid "Label used when logging"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml73(td)
+#: ./doc/common/tables/swift-container-server-container-auditor.xml21(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml64(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml67(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml21(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml21(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml21(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml27(td)
+#: ./doc/common/tables/swift-object-server-object-auditor.xml21(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml21(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml21(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml33(td)
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml21(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml21(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml61(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml21(td)
+msgid "log_facility = LOG_LOCAL0"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml73(td)
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml24(td)
+#: ./doc/common/tables/swift-container-server-container-auditor.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml24(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml64(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml24(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml67(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml24(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml21(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml21(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml21(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml27(td)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml24(td)
+#: ./doc/common/tables/swift-object-server-object-auditor.xml21(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml24(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml21(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml21(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml33(td)
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml21(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml21(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml61(td)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml24(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml21(td)
+msgid "Syslog log facility"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml76(td)
+#: ./doc/common/tables/swift-container-server-container-auditor.xml24(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml67(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml70(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml24(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml24(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml24(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml30(td)
+#: ./doc/common/tables/swift-object-server-object-auditor.xml24(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml24(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml24(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml36(td)
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml24(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml24(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml64(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml24(td)
+msgid "log_level = INFO"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml76(td)
+#: ./doc/common/tables/swift-container-server-container-auditor.xml24(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml67(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml70(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml24(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml24(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml24(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml30(td)
+#: ./doc/common/tables/swift-object-server-object-auditor.xml24(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml24(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml24(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml36(td)
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml24(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml24(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml64(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml24(td)
+msgid "Logging level"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml82(td)
+#: ./doc/common/tables/swift-container-server-container-auditor.xml27(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml70(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml73(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml27(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml27(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml27(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml33(td)
+#: ./doc/common/tables/swift-object-server-object-auditor.xml27(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml27(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml27(td)
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml27(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml27(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml67(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml27(td)
+msgid "log_address = /dev/log"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml82(td)
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml33(td)
+#: ./doc/common/tables/swift-container-server-container-auditor.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml30(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml70(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml33(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml73(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml33(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml27(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml27(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml27(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml33(td)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml33(td)
+#: ./doc/common/tables/swift-object-server-object-auditor.xml27(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml33(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml27(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml27(td)
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml27(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml27(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml67(td)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml33(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml27(td)
+msgid "Location where syslog sends the logs to"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml30(td)
+msgid "sync_proxy = http://10.1.1.1:8888,http://10.1.1.2:8888"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml30(td)
+msgid "If you need to use an HTTP proxy, set it here. Defaults to no proxy."
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml33(td)
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml18(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml30(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml30(td)
+msgid "interval = 300"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml33(td)
+#: ./doc/common/tables/swift-container-server-container-auditor.xml30(td)
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml18(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml42(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml30(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml42(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml30(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml30(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml33(td)
+msgid "Minimum time for a pass to take"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml36(td)
+msgid "container_time = 60"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml36(td)
+msgid "Maximum amount of time to spend syncing each container"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml7(literal)
+msgid "proxy-server.conf-sample"
+msgstr "proxy-server.conf-sample"
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml18(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml18(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml18(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml18(td)
+msgid "bind_ip = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml18(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml18(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml18(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml18(td)
+msgid "IP Address for server to bind to"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml21(td)
+msgid "bind_port = 80"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml21(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml21(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml21(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml21(td)
+msgid "Port for server to bind to"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml24(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml24(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml24(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml24(td)
+msgid "bind_timeout = 30"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml24(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml24(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml24(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml24(td)
+msgid "Seconds to attempt bind before giving up"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml27(td)
+#: ./doc/common/tables/heat-cfn_api.xml33(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml27(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml27(td)
+#: ./doc/common/tables/heat-api.xml103(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml29(td)
+#: ./doc/common/tables/neutron-wsgi.xml22(td)
+#: ./doc/common/tables/glance-common.xml30(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml27(td)
+#: ./doc/common/tables/trove-debug.xml26(td)
+msgid "backlog = 4096"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml27(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml27(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml27(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml27(td)
+msgid "Maximum number of allowed pending TCP connections"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml30(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml33(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml33(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml18(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml45(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml33(td)
+msgid "swift_dir = /etc/swift"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml30(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml33(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml33(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml18(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml45(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml33(td)
+msgid "Swift configuration directory"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml33(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml30(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml30(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml21(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml30(td)
+msgid "user = swift"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml33(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml30(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml30(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml21(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml30(td)
+msgid "User to run as"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml36(td)
+msgid "expose_info = true"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml36(td)
+msgid "Enables exposing configuration settings via HTTP GET /info."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml39(td)
+msgid "admin_key = secret_admin_key"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml39(td)
+msgid ""
+"to use for admin calls that are HMAC signed. Default is empty, which will "
+"disable admin calls to /info. the proxy server. For most cases, this should "
+"be `egg:swift#proxy`. request whenever it has to failover to a handoff node"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml42(td)
+msgid "disallowed_sections = container_quotas, tempurl"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml42(td)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml64(td)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml67(td)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml79(td)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml85(td)
+#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml18(td)
+#: ./doc/common/tables/neutron-rootwrap.xml50(td)
+#: ./doc/common/tables/neutron-rootwrap.xml54(td)
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml36(td)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml39(td)
+#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml18(td)
+#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml57(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml81(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml87(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml90(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml93(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml96(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml102(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml105(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml108(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml111(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml114(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml58(td)
+#: ./doc/common/tables/swift-container-server-pipeline-main.xml18(td)
+#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml21(td)
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml24(td)
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml27(td)
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml33(td)
+#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml24(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml45(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml48(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml45(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml51(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml54(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml57(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml60(td)
+#: ./doc/common/tables/swift-rsyncd-container.xml18(td)
+#: ./doc/common/tables/swift-rsyncd-container.xml21(td)
+#: ./doc/common/tables/swift-rsyncd-container.xml24(td)
+#: ./doc/common/tables/swift-rsyncd-container.xml27(td)
+#: ./doc/common/tables/swift-rsyncd-account.xml18(td)
+#: ./doc/common/tables/swift-rsyncd-account.xml21(td)
+#: ./doc/common/tables/swift-rsyncd-account.xml24(td)
+#: ./doc/common/tables/swift-rsyncd-account.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml57(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml60(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml63(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml66(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml69(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml72(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml75(td)
+#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml18(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml45(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml51(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml75(td)
+#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml36(td)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml39(td)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml42(td)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml45(td)
+#: ./doc/common/tables/swift-object-server-pipeline-main.xml18(td)
+#: ./doc/common/tables/swift-memcache-memcache.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml36(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml39(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml42(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml45(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml48(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml51(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml54(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml57(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml60(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml72(td)
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml18(td)
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml21(td)
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml24(td)
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml27(td)
+#: ./doc/common/tables/swift-object-server-object-auditor.xml45(td)
+#: ./doc/common/tables/swift-account-server-pipeline-main.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml36(td)
+#: ./doc/common/tables/swift-object-server-filter-recon.xml24(td)
+#: ./doc/common/tables/swift-rsyncd-object.xml18(td)
+#: ./doc/common/tables/swift-rsyncd-object.xml21(td)
+#: ./doc/common/tables/swift-rsyncd-object.xml24(td)
+#: ./doc/common/tables/swift-rsyncd-object.xml27(td)
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml39(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml24(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml33(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml42(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml48(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml51(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml57(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml60(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml63(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml66(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml69(td)
+#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml21(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml45(td)
+#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml21(td)
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml18(td)
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml21(td)
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml24(td)
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml21(td)
+msgid "No help text available for this option."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml45(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml45(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml51(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml45(td)
+msgid "workers = auto"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml45(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml45(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml51(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml45(td)
+msgid ""
+"a much higher value, one can reduce the impact of slow file system "
+"operations in one request from negatively impacting other requests."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml48(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml48(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml54(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml48(td)
+msgid "max_clients = 1024"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml48(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml48(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml54(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml48(td)
+msgid ""
+"Maximum number of clients one worker can process simultaneously Lowering the"
+" number of clients handled per worker, and raising the number of workers can"
+" lessen the impact that a CPU intensive, or blocking, request can have on "
+"other requests served by the same worker. If the maximum number of clients "
+"is set to one, then a given worker will not perform another call while "
+"processing, allowing other workers a chance to process it."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml58(td)
+msgid "cert_file = /etc/swift/proxy.crt"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml58(td)
+msgid "to the ssl .crt. This should be enabled for testing purposes only."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml61(td)
+msgid "key_file = /etc/swift/proxy.key"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml61(td)
+msgid "to the ssl .key. This should be enabled for testing purposes only."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml64(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml45(td)
+msgid "expiring_objects_container_divisor = 86400"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml67(td)
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml24(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml48(td)
+msgid "expiring_objects_account_name = expiring_objects"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml70(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml61(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml64(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml24(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml58(td)
+msgid "log_name = swift"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml79(td)
+msgid "log_headers = false"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml85(td)
+msgid "trans_id_suffix ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml88(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml73(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml76(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml36(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml70(td)
+msgid "log_custom_handlers ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml88(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml73(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml76(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml36(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml70(td)
+msgid ""
+"Comma-separated list of functions to call to setup custom log handlers."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml91(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml76(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml79(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml39(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml73(td)
+msgid "log_udp_host ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml91(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml76(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml79(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml39(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml73(td)
+msgid "If not set, the UDB receiver for syslog is disabled."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml94(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml79(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml82(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml42(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml76(td)
+msgid "log_udp_port = 514"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml94(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml79(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml82(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml42(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml76(td)
+msgid "Port value for UDB receiver, if enabled."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml97(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml82(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml85(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml45(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml79(td)
+msgid "log_statsd_host = localhost"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml97(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml82(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml85(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml45(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml79(td)
+msgid "If not set, the StatsD feature is disabled."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml100(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml85(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml88(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml48(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml82(td)
+msgid "log_statsd_port = 8125"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml100(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml85(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml88(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml48(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml82(td)
+msgid "Port value for the StatsD server."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml103(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml88(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml91(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml51(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml85(td)
+msgid "log_statsd_default_sample_rate = 1.0"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml103(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml88(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml91(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml51(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml85(td)
+msgid ""
+"Defines the probability of sending a sample for any given event or timing "
+"measurement."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml107(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml92(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml95(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml55(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml89(td)
+msgid "log_statsd_sample_rate_factor = 1.0"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml107(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml92(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml95(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml55(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml89(td)
+msgid ""
+"Not recommended to set this to a value less than 1.0, if frequency of "
+"logging is too high, tune the log_statsd_default_sample_rate instead."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml112(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml97(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml100(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml60(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml94(td)
+msgid "log_statsd_metric_prefix ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml112(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml97(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml100(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml60(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml94(td)
+msgid "Value will be prepended to every metric sent to the StatsD server."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml115(td)
+msgid "cors_allow_origin ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml115(td)
+msgid ""
+"is a list of hosts that are included with any CORS request by default and "
+"returned with the Access-Control-Allow-Origin header in addition to what the"
+" container has set. to call to setup custom log handlers. for eventlet the "
+"proxy server. For most cases, this should be `egg:swift#proxy`. request "
+"whenever it has to failover to a handoff node"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml118(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml115(td)
+msgid "client_timeout = 60"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml118(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml115(td)
+msgid "Timeout to read one chunk from a client external services"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml121(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml103(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml103(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml100(td)
+msgid "eventlet_debug = false"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml121(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml103(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml103(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml100(td)
+msgid "If true, turn on debug logging for eventlet"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml8(caption)
+msgid "Description of configuration options for zoning_fabric"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml19(th)
+msgid "[BRCD_FABRIC_EXAMPLE]"
+msgstr "[BRCD_FABRIC_EXAMPLE]"
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml22(td)
+msgid "fc_fabric_address ="
+msgstr "fc_fabric_address ="
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml23(td)
+msgid "(StrOpt) Management IP of fabric"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml26(td)
+msgid "fc_fabric_password ="
+msgstr "fc_fabric_password ="
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml27(td)
+msgid "(StrOpt) Password for user"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml30(td)
+msgid "fc_fabric_port = 22"
+msgstr "fc_fabric_port = 22"
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml31(td)
+msgid "(IntOpt) Connecting port"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml34(td)
+msgid "fc_fabric_user ="
+msgstr "fc_fabric_user ="
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml35(td)
+msgid "(StrOpt) Fabric user ID"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml38(td)
+msgid "principal_switch_wwn = None"
+msgstr "principal_switch_wwn = None"
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml39(td)
+msgid "(StrOpt) Principal switch WWN of the fabric"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml42(td)
+msgid "zone_activate = True"
+msgstr "zone_activate = True"
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml43(td)
+msgid "(BoolOpt) overridden zoning activation state"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml46(td)
+msgid "zone_name_prefix = None"
+msgstr "zone_name_prefix = None"
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml47(td)
+msgid "(StrOpt) overridden zone name prefix"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml50(td)
+#: ./doc/common/tables/cinder-zoning.xml33(td)
+msgid "zoning_policy = initiator-target"
+msgstr "zoning_policy = initiator-target"
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml51(td)
+msgid "(StrOpt) overridden zoning policy"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-redis.xml8(caption)
+#: ./doc/common/tables/neutron-redis.xml8(caption)
+#: ./doc/common/tables/nova-redis.xml8(caption)
+#: ./doc/common/tables/glance-redis.xml8(caption)
+#: ./doc/common/tables/heat-redis.xml8(caption)
+#: ./doc/common/tables/trove-redis.xml8(caption)
+#: ./doc/common/tables/keystone-redis.xml8(caption)
+msgid "Description of configuration options for redis"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-redis.xml22(td)
+#: ./doc/common/tables/nova-common.xml42(td)
+#: ./doc/common/tables/neutron-redis.xml22(td)
+#: ./doc/common/tables/cinder-common.xml58(td)
+#: ./doc/common/tables/heat-redis.xml22(td)
+msgid "host = oslo"
+msgstr "host = oslo"
+
+#: ./doc/common/tables/ceilometer-redis.xml23(td)
+msgid ""
+"(StrOpt) Name of this node, which must be valid in an AMQP key. Can be an "
+"opaque identifier. For ZeroMQ only, must be a valid host name, FQDN, or IP "
+"address."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-redis.xml34(th)
+#: ./doc/common/tables/neutron-redis.xml26(th)
+#: ./doc/common/tables/heat-redis.xml26(th)
+#: ./doc/common/tables/trove-redis.xml19(th)
+msgid "[matchmaker_redis]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-redis.xml37(td)
+#: ./doc/common/tables/neutron-redis.xml29(td)
+#: ./doc/common/tables/glance-redis.xml22(td)
+#: ./doc/common/tables/heat-redis.xml29(td)
+#: ./doc/common/tables/trove-redis.xml22(td)
+#: ./doc/common/tables/neutron-nec.xml38(td)
+#: ./doc/common/tables/keystone-redis.xml22(td)
+msgid "host = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-redis.xml38(td)
+#: ./doc/common/tables/neutron-redis.xml30(td)
+#: ./doc/common/tables/heat-redis.xml30(td)
+#: ./doc/common/tables/trove-redis.xml23(td)
+msgid "(StrOpt) Host to locate redis"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-redis.xml41(td)
+#: ./doc/common/tables/neutron-redis.xml33(td)
+#: ./doc/common/tables/nova-redis.xml22(td)
+#: ./doc/common/tables/keystone-ldap.xml90(td)
+#: ./doc/common/tables/glance-redis.xml26(td)
+#: ./doc/common/tables/cinder-rpc.xml82(td)
+#: ./doc/common/tables/heat-redis.xml33(td)
+#: ./doc/common/tables/neutron-ml2_ncs.xml22(td)
+#: ./doc/common/tables/neutron-ml2_odl.xml22(td)
+#: ./doc/common/tables/trove-redis.xml26(td)
+#: ./doc/common/tables/keystone-redis.xml34(td)
+msgid "password = None"
+msgstr "password = None"
+
+#: ./doc/common/tables/ceilometer-redis.xml42(td)
+#: ./doc/common/tables/neutron-redis.xml34(td)
+#: ./doc/common/tables/heat-redis.xml34(td)
+#: ./doc/common/tables/trove-redis.xml27(td)
+msgid "(StrOpt) Password for Redis server. (optional)"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-redis.xml45(td)
+#: ./doc/common/tables/nova-common.xml74(td)
+#: ./doc/common/tables/neutron-redis.xml37(td)
+#: ./doc/common/tables/glance-redis.xml30(td)
+#: ./doc/common/tables/cinder-rpc.xml86(td)
+#: ./doc/common/tables/heat-redis.xml37(td)
+#: ./doc/common/tables/trove-redis.xml30(td)
+#: ./doc/common/tables/keystone-redis.xml38(td)
+msgid "port = 6379"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-redis.xml46(td)
+#: ./doc/common/tables/nova-common.xml75(td)
+#: ./doc/common/tables/neutron-redis.xml38(td)
+#: ./doc/common/tables/glance-redis.xml31(td)
+#: ./doc/common/tables/cinder-rpc.xml87(td)
+#: ./doc/common/tables/heat-redis.xml38(td)
+#: ./doc/common/tables/trove-redis.xml31(td)
+#: ./doc/common/tables/keystone-redis.xml39(td)
+msgid "(IntOpt) Use this port to connect to redis host."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml8(caption)
+msgid "Description of configuration options for storage_ceph"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml22(td)
+msgid "rbd_ceph_conf ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml23(td)
+msgid "(StrOpt) path to the ceph configuration file to use"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml26(td)
+msgid "rbd_flatten_volume_from_snapshot = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml27(td)
+msgid "(BoolOpt) flatten volumes created from snapshots to remove dependency"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml30(td)
+msgid "rbd_max_clone_depth = 5"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml31(td)
+msgid ""
+"(IntOpt) maximum number of nested clones that can be taken of a volume "
+"before enforcing a flatten prior to next clone. A value of zero disables "
+"cloning"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml34(td)
+msgid "rbd_pool = rbd"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml35(td)
+msgid "(StrOpt) the RADOS pool in which rbd volumes are stored"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml38(td)
+#: ./doc/common/tables/nova-volumes.xml115(td)
+msgid "rbd_secret_uuid = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml39(td)
+msgid "(StrOpt) the libvirt uuid of the secret for the rbd_uservolumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml42(td)
+#: ./doc/common/tables/nova-volumes.xml119(td)
+msgid "rbd_user = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml43(td)
+msgid ""
+"(StrOpt) the RADOS client name for accessing rbd volumes - only set when "
+"using cephx authentication"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml46(td)
+msgid "volume_tmp_dir = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml47(td)
+msgid ""
+"(StrOpt) where to store temporary image files if the volume driver does not "
+"write them directly to the volume"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml8(caption)
+#: ./doc/common/tables/nova-vmware.xml8(caption)
+#: ./doc/common/tables/neutron-vmware.xml8(caption)
+#: ./doc/common/tables/glance-vmware.xml8(caption)
+#: ./doc/common/tables/cinder-vmware.xml8(caption)
+msgid "Description of configuration options for vmware"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml19(th)
+#: ./doc/common/tables/nova-vnc.xml42(th)
+#: ./doc/common/tables/nova-vmware.xml19(th)
+#: ./doc/common/tables/nova-network.xml254(th)
+msgid "[vmware]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml22(td)
+#: ./doc/common/tables/nova-vmware.xml22(td)
+msgid "api_retry_count = 10"
+msgstr "api_retry_count = 10"
+
+#: ./doc/common/tables/ceilometer-vmware.xml23(td)
+msgid "(IntOpt) Number of times a VMware Vsphere API must be retried"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml26(td)
+msgid "host_ip ="
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml27(td)
+msgid "(StrOpt) IP address of the VMware Vsphere host"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml30(td)
+msgid "host_password ="
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml31(td)
+msgid "(StrOpt) Password of VMware Vsphere"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml34(td)
+msgid "host_username ="
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml35(td)
+msgid "(StrOpt) Username of VMware Vsphere"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml38(td)
+#: ./doc/common/tables/nova-vmware.xml54(td)
+msgid "task_poll_interval = 0.5"
+msgstr "task_poll_interval = 0.5"
+
+#: ./doc/common/tables/ceilometer-vmware.xml39(td)
+msgid "(FloatOpt) Sleep time in seconds for polling an ongoing async task"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml8(caption)
+msgid "Description of configuration options for cisco"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml19(th)
+msgid "[CISCO]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml22(td)
+msgid ""
+"model_class = "
+"neutron.plugins.cisco.models.virt_phy_sw_v2.VirtualPhysicalSwitchModelV2"
+msgstr "model_class = neutron.plugins.cisco.models.virt_phy_sw_v2.VirtualPhysicalSwitchModelV2 "
+
+#: ./doc/common/tables/neutron-cisco.xml23(td)
+msgid "(StrOpt) Model Class"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml26(td)
+msgid ""
+"nexus_driver = "
+"neutron.plugins.cisco.test.nexus.fake_nexus_driver.CiscoNEXUSFakeDriver"
+msgstr "nexus_driver = neutron.plugins.cisco.test.nexus.fake_nexus_driver.CiscoNEXUSFakeDriver"
+
+#: ./doc/common/tables/neutron-cisco.xml27(td)
+msgid "(StrOpt) Nexus Driver Name"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml30(td)
+msgid "nexus_l3_enable = False"
+msgstr "nexus_l3_enable = False"
+
+#: ./doc/common/tables/neutron-cisco.xml31(td)
+msgid "(BoolOpt) Enable L3 support on the Nexus switches"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml34(td)
+msgid "provider_vlan_auto_create = True"
+msgstr "provider_vlan_auto_create = True"
+
+#: ./doc/common/tables/neutron-cisco.xml35(td)
+msgid ""
+"(BoolOpt) Provider VLANs are automatically created as needed on the Nexus "
+"switch"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml38(td)
+msgid "provider_vlan_auto_trunk = True"
+msgstr "provider_vlan_auto_trunk = True"
+
+#: ./doc/common/tables/neutron-cisco.xml39(td)
+msgid ""
+"(BoolOpt) Provider VLANs are automatically trunked as needed on the ports of"
+" the Nexus switch"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml42(td)
+msgid "provider_vlan_name_prefix = p-"
+msgstr "provider_vlan_name_prefix = p-"
+
+#: ./doc/common/tables/neutron-cisco.xml43(td)
+msgid "(StrOpt) VLAN Name prefix for provider vlans"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml46(td)
+#: ./doc/common/tables/neutron-cisco.xml122(td)
+msgid "svi_round_robin = False"
+msgstr "svi_round_robin = False"
+
+#: ./doc/common/tables/neutron-cisco.xml47(td)
+#: ./doc/common/tables/neutron-cisco.xml123(td)
+msgid "(BoolOpt) Distribute SVI interfaces over all switches"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml50(td)
+#: ./doc/common/tables/neutron-cisco.xml126(td)
+msgid "vlan_name_prefix = q-"
+msgstr "vlan_name_prefix = q-"
+
+#: ./doc/common/tables/neutron-cisco.xml51(td)
+#: ./doc/common/tables/neutron-cisco.xml127(td)
+msgid "(StrOpt) VLAN Name prefix"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml58(td)
+msgid "(StrOpt) N1K Bridge Mappings"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml61(td)
+msgid "default_network_profile = default_network_profile"
+msgstr "default_network_profile = default_network_profile"
+
+#: ./doc/common/tables/neutron-cisco.xml62(td)
+msgid "(StrOpt) N1K default network profile"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml65(td)
+msgid "default_policy_profile = service_profile"
+msgstr "default_policy_profile = service_profile"
+
+#: ./doc/common/tables/neutron-cisco.xml66(td)
+msgid "(StrOpt) N1K default policy profile"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml69(td)
+msgid "enable_tunneling = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml70(td)
+msgid "(BoolOpt) N1K Enable Tunneling"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml74(td)
+msgid "(StrOpt) N1K Integration Bridge"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml77(td)
+msgid "network_node_policy_profile = dhcp_pp"
+msgstr "network_node_policy_profile = dhcp_pp"
+
+#: ./doc/common/tables/neutron-cisco.xml78(td)
+msgid "(StrOpt) N1K policy profile for network node"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml81(td)
+msgid "network_vlan_ranges = vlan:1:4095"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml82(td)
+msgid "(StrOpt) N1K Network VLAN Ranges"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml85(td)
+msgid "poll_duration = 10"
+msgstr "poll_duration = 10"
+
+#: ./doc/common/tables/neutron-cisco.xml86(td)
+msgid "(StrOpt) N1K Policy profile polling duration in seconds"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml90(td)
+msgid "(StrOpt) N1K Tenant Network Type"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml94(td)
+msgid "(StrOpt) N1K Tunnel Bridge"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml97(td)
+msgid "vxlan_id_ranges = 5000:10000"
+msgstr "vxlan_id_ranges = 5000:10000"
+
+#: ./doc/common/tables/neutron-cisco.xml98(td)
+msgid "(StrOpt) N1K VXLAN ID Ranges"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml101(th)
+msgid "[CISCO_PLUGINS]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml104(td)
+msgid ""
+"nexus_plugin = neutron.plugins.cisco.nexus.cisco_nexus_plugin_v2.NexusPlugin"
+msgstr "nexus_plugin = neutron.plugins.cisco.nexus.cisco_nexus_plugin_v2.NexusPlugin"
+
+#: ./doc/common/tables/neutron-cisco.xml105(td)
+msgid "(StrOpt) Nexus Switch to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml108(td)
+msgid ""
+"vswitch_plugin = "
+"neutron.plugins.openvswitch.ovs_neutron_plugin.OVSNeutronPluginV2"
+msgstr "vswitch_plugin = neutron.plugins.openvswitch.ovs_neutron_plugin.OVSNeutronPluginV2"
+
+#: ./doc/common/tables/neutron-cisco.xml109(td)
+msgid "(StrOpt) Virtual Switch to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml112(th)
+msgid "[cisco_csr_ipsec]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml115(td)
+msgid "status_check_interval = 60"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml116(td)
+msgid "(IntOpt) Status check interval for Cisco CSR IPSec connections"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml119(th)
+#: ./doc/common/tables/neutron-ml2_cisco.xml19(th)
+msgid "[ml2_cisco]"
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml8(caption)
+#: ./doc/common/tables/neutron-testing.xml8(caption)
+#: ./doc/common/tables/glance-testing.xml8(caption)
+msgid "Description of configuration options for testing"
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml22(td)
+#: ./doc/common/tables/keystone-rpc.xml22(td)
+#: ./doc/common/tables/cinder-rpc.xml22(td)
+msgid ""
+"allowed_rpc_exception_modules = oslo.messaging.exceptions, nova.exception, "
+"cinder.exception, exceptions"
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml23(td)
+#: ./doc/common/tables/keystone-rpc.xml23(td)
+#: ./doc/common/tables/ceilometer-rpc.xml23(td)
+#: ./doc/common/tables/cinder-rpc.xml23(td)
+#: ./doc/common/tables/heat-rpc.xml23(td)
+#: ./doc/common/tables/neutron-common.xml39(td)
+msgid ""
+"(ListOpt) Modules of exceptions that are permitted to be recreated upon "
+"receiving exception data from an rpc call."
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml22(td)
 #: ./doc/common/tables/nova-testing.xml26(td)
-#: ./doc/common/tables/trove-debug.xml22(td)
-#: ./doc/common/tables/cinder-api.xml30(td)
-#: ./doc/common/tables/glance-wsgi.xml22(td)
-#: ./doc/common/tables/heat-debug.xml22(td)
 #: ./doc/common/tables/ceilometer-common.xml22(td)
+#: ./doc/common/tables/cinder-api.xml30(td)
+#: ./doc/common/tables/heat-debug.xml22(td)
 #: ./doc/common/tables/neutron-testing.xml22(td)
+#: ./doc/common/tables/glance-wsgi.xml22(td)
+#: ./doc/common/tables/trove-debug.xml22(td)
+#: ./doc/common/tables/keystone-debug.xml22(td)
 msgid "backdoor_port = None"
 msgstr "backdoor_port = None"
 
-#: ./doc/common/tables/keystone-debug.xml23(td)
-#: ./doc/common/tables/trove-debug.xml23(td)
+#: ./doc/common/tables/nova-testing.xml27(td)
+msgid ""
+"(StrOpt) Enable eventlet backdoor. Acceptable values are 0, &lt;port&gt; and"
+" &lt;start&gt;:&lt;end&gt;, where 0 results in listening on a random tcp "
+"port number, &lt;port&gt; results in listening on the specified port number "
+"and not enabling backdoorif it is in use and &lt;start&gt;:&lt;end&gt; "
+"results in listening on the smallest unused port number within the specified"
+" range of port numbers. The chosen port is displayed in the service's log "
+"file."
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml30(td)
+msgid "fake_call = False"
+msgstr "fake_call = False"
+
+#: ./doc/common/tables/nova-testing.xml31(td)
+msgid "(BoolOpt) If True, skip using the queue and make local calls"
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml34(td)
+msgid "fake_network = False"
+msgstr "fake_network = False"
+
+#: ./doc/common/tables/nova-testing.xml35(td)
+msgid "(BoolOpt) If passed, use fake network devices and addresses"
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml38(td)
+#: ./doc/common/tables/trove-amqp.xml38(td)
+#: ./doc/common/tables/keystone-rabbit.xml22(td)
+#: ./doc/common/tables/heat-amqp.xml42(td)
+#: ./doc/common/tables/glance-rabbitmq.xml26(td)
+#: ./doc/common/tables/neutron-testing.xml26(td)
+#: ./doc/common/tables/cinder-rpc.xml42(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml22(td)
+msgid "fake_rabbit = False"
+msgstr "fake_rabbit = False"
+
+#: ./doc/common/tables/nova-testing.xml39(td)
+#: ./doc/common/tables/keystone-rabbit.xml23(td)
+#: ./doc/common/tables/glance-rabbitmq.xml27(td)
+#: ./doc/common/tables/cinder-rpc.xml43(td)
+msgid "(BoolOpt) If passed, use a fake RabbitMQ provider."
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml42(td)
+#: ./doc/common/tables/cinder-common.xml110(td)
+msgid "monkey_patch = False"
+msgstr "monkey_patch = False"
+
+#: ./doc/common/tables/nova-testing.xml43(td)
+msgid "(BoolOpt) Whether to log monkey patching"
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml46(td)
+msgid ""
+"monkey_patch_modules = "
+"nova.api.ec2.cloud:nova.notifications.notify_decorator, "
+"nova.compute.api:nova.notifications.notify_decorator"
+msgstr "monkey_patch_modules = nova.api.ec2.cloud:nova.notifications.notify_decorator, nova.compute.api:nova.notifications.notify_decorator"
+
+#: ./doc/common/tables/nova-testing.xml47(td)
+#: ./doc/common/tables/cinder-common.xml115(td)
+msgid "(ListOpt) List of modules/decorators to monkey patch"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml8(caption)
+#: ./doc/common/tables/neutron-metadata.xml8(caption)
+msgid "Description of configuration options for metadata"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml22(td)
+msgid "metadata_host = $my_ip"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml23(td)
+msgid "(StrOpt) The IP address for the metadata API server"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml26(td)
+msgid "metadata_listen = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml27(td)
+msgid "(StrOpt) The IP address on which the metadata API will listen."
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml30(td)
+msgid "metadata_listen_port = 8775"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml31(td)
+msgid "(IntOpt) The port on which the metadata API will listen."
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml34(td)
+msgid "metadata_manager = nova.api.manager.MetadataManager"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml35(td)
+msgid "(StrOpt) OpenStack metadata service manager"
+msgstr "(StrOpt)  Gestionnaire du service des métadonnées d’OpenStack"
+
+#: ./doc/common/tables/nova-metadata.xml38(td)
+msgid "metadata_port = 8775"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml39(td)
+msgid "(IntOpt) The port for the metadata API port"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml42(td)
+msgid "metadata_workers = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml43(td)
+msgid ""
+"(IntOpt) Number of workers for metadata service. The default will be the "
+"number of CPUs available."
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml46(td)
+msgid ""
+"vendordata_driver = nova.api.metadata.vendordata_json.JsonFileVendorData"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml47(td)
+msgid "(StrOpt) Driver to use for vendor data"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml50(td)
+msgid "vendordata_jsonfile_path = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml51(td)
+msgid "(StrOpt) File to load json formatted vendor data from"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_nova.xml8(caption)
+msgid "Description of configuration options for clients_nova"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_nova.xml19(th)
+msgid "[clients_nova]"
+msgstr "[clients_nova]"
+
+#: ./doc/common/tables/cinder-hp3par.xml8(caption)
+msgid "Description of configuration options for hp3par"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml22(td)
+msgid "hp3par_api_url ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml23(td)
+msgid ""
+"(StrOpt) 3PAR WSAPI Server Url like https://&lt;3par ip&gt;:8080/api/v1"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml26(td)
+msgid "hp3par_cpg = OpenStack"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml27(td)
+msgid "(StrOpt) The CPG to use for volume creation"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml30(td)
+msgid "hp3par_cpg_snap ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml31(td)
+msgid ""
+"(StrOpt) The CPG to use for Snapshots for volumes. If empty hp3par_cpg will "
+"be used"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml34(td)
+msgid "hp3par_debug = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml35(td)
+msgid "(BoolOpt) Enable HTTP debugging to 3PAR"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml38(td)
+msgid "hp3par_iscsi_ips ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml39(td)
+msgid "(ListOpt) List of target iSCSI addresses to use."
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml42(td)
+msgid "hp3par_password ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml43(td)
+msgid "(StrOpt) 3PAR Super user password"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml46(td)
+msgid "hp3par_snapshot_expiration ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml47(td)
+msgid ""
+"(StrOpt) The time in hours when a snapshot expires and is deleted. This must"
+" be larger than expiration"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml50(td)
+msgid "hp3par_snapshot_retention ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml51(td)
+msgid ""
+"(StrOpt) The time in hours to retain a snapshot. You can't delete it before "
+"this expires."
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml54(td)
+msgid "hp3par_username ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml55(td)
+msgid "(StrOpt) 3PAR Super user username"
+msgstr ""
+
+#: ./doc/common/tables/keystone-misc.xml8(caption)
+msgid "Description of configuration options for misc"
+msgstr ""
+
+#: ./doc/common/tables/keystone-misc.xml22(td)
+#: ./doc/common/tables/ceilometer-common.xml34(td)
+#: ./doc/common/tables/nova-common.xml46(td)
+#: ./doc/common/tables/trove-common.xml58(td)
+#: ./doc/common/tables/cinder-common.xml70(td)
+#: ./doc/common/tables/heat-debug.xml38(td)
+#: ./doc/common/tables/glance-common.xml70(td)
+#: ./doc/common/tables/neutron-common.xml142(td)
+msgid "lock_path = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-misc.xml23(td)
+#: ./doc/common/tables/ceilometer-common.xml35(td)
+#: ./doc/common/tables/nova-common.xml47(td)
+#: ./doc/common/tables/trove-common.xml59(td)
+#: ./doc/common/tables/heat-debug.xml39(td)
+#: ./doc/common/tables/glance-common.xml71(td)
+#: ./doc/common/tables/neutron-common.xml143(td)
+msgid "(StrOpt) Directory to use for lock files."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml7(literal)
+msgid "[filter:cname_lookup]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml18(td)
+msgid "use = egg:swift#cname_lookup"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml18(td)
+#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml18(td)
+#: ./doc/common/tables/swift-container-server-filter-recon.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml18(td)
+#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml18(td)
+#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml18(td)
+#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml18(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml18(td)
+#: ./doc/common/tables/swift-account-server-filter-recon.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml18(td)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml18(td)
+#: ./doc/common/tables/swift-object-expirer-filter-cache.xml18(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml18(td)
+#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml18(td)
+#: ./doc/common/tables/swift-object-server-filter-recon.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml18(td)
+msgid "Entry point of paste.deploy in the server"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml21(td)
+msgid "set log_name = cname_lookup"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml21(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml21(td)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml21(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml21(td)
+msgid "Label to use when logging"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml24(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml24(td)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml24(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml24(td)
+msgid "set log_facility = LOG_LOCAL0"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml27(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml27(td)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml27(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml27(td)
+msgid "set log_level = INFO"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml27(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml27(td)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml27(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml27(td)
+msgid "Log level"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml30(td)
+msgid "set log_headers = false"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml30(td)
+msgid "If True, log headers in each request"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml30(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml33(td)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml33(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml33(td)
+msgid "set log_address = /dev/log"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml36(td)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml36(td)
+msgid "storage_domain = example.com"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml36(td)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml36(td)
+msgid ""
+"Domain that matches your cloud. Multiple domains can be specified using a "
+"comma-separated list."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml40(td)
+msgid "lookup_depth = 1"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml40(td)
+msgid ""
+"Because CNAMES can be recursive, specifies the number of levels through "
+"which to search."
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml8(caption)
+#: ./doc/common/tables/cinder-scheduler.xml8(caption)
+msgid "Description of configuration options for scheduler"
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml22(td)
+msgid "network_auto_schedule = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml23(td)
+msgid "(BoolOpt) Allow auto scheduling networks to DHCP agent."
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml26(td)
+msgid ""
+"network_scheduler_driver = "
+"neutron.scheduler.dhcp_agent_scheduler.ChanceScheduler"
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml27(td)
+msgid "(StrOpt) Driver to use for scheduling network to DHCP agent"
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml30(td)
+msgid "router_auto_schedule = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml31(td)
+msgid "(BoolOpt) Allow auto scheduling of routers to L3 agent."
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml34(td)
+msgid "router_delete_namespaces = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml35(td)
+msgid "(BoolOpt) Delete namespace after removing a router."
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml38(td)
+msgid ""
+"router_scheduler_driver = "
+"neutron.scheduler.l3_agent_scheduler.ChanceScheduler"
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml39(td)
+msgid "(StrOpt) Driver to use for scheduling router to a default L3 agent"
+msgstr ""
+
+#: ./doc/common/tables/glance-rbd.xml8(caption)
+msgid "Description of configuration options for rbd"
+msgstr ""
+
+#: ./doc/common/tables/glance-rbd.xml22(td)
+msgid "rbd_store_ceph_conf = /etc/ceph/ceph.conf"
+msgstr ""
+
+#: ./doc/common/tables/glance-rbd.xml23(td)
+msgid ""
+"(StrOpt) Ceph configuration file path. If &lt;None&gt;, librados will locate"
+" the default config. If using cephx authentication, this file should include"
+" a reference to the right keyring in a client.&lt;USER&gt; section."
+msgstr ""
+
+#: ./doc/common/tables/glance-rbd.xml26(td)
+msgid "rbd_store_chunk_size = 8"
+msgstr ""
+
+#: ./doc/common/tables/glance-rbd.xml27(td)
+msgid ""
+"(IntOpt) RADOS images will be chunked into objects of this size (in "
+"megabytes). For best performance, this should be a power of two."
+msgstr ""
+
+#: ./doc/common/tables/glance-rbd.xml30(td)
+msgid "rbd_store_pool = images"
+msgstr ""
+
+#: ./doc/common/tables/glance-rbd.xml31(td)
+msgid "(StrOpt) RADOS pool in which images are stored."
+msgstr ""
+
+#: ./doc/common/tables/glance-rbd.xml34(td)
+msgid "rbd_store_user = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-rbd.xml35(td)
+msgid ""
+"(StrOpt) RADOS user to authenticate as (only applicable if using Cephx. If "
+"&lt;None&gt;, a default will be chosen based on the client. section in "
+"rbd_store_ceph_conf)."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml8(caption)
+msgid "Description of configuration options for storage_xen"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml22(td)
+msgid "xenapi_connection_password = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml23(td)
+msgid "(StrOpt) Password for XenAPI connection"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml26(td)
+msgid "xenapi_connection_url = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml27(td)
+msgid "(StrOpt) URL for XenAPI connection"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml30(td)
+#: ./doc/common/tables/neutron-rootwrap.xml49(td)
+msgid "xenapi_connection_username = root"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml31(td)
+msgid "(StrOpt) Username for XenAPI connection"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml34(td)
+msgid "xenapi_nfs_server = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml35(td)
+msgid "(StrOpt) NFS server to be used by XenAPINFSDriver"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml38(td)
+msgid "xenapi_nfs_serverpath = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml39(td)
+msgid "(StrOpt) Path of exported NFS, used by XenAPINFSDriver"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml42(td)
+msgid "xenapi_sr_base_path = /var/run/sr-mount"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml43(td)
+#: ./doc/common/tables/nova-xen.xml177(td)
+msgid "(StrOpt) Base path to the storage repository"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-common.xml8(caption)
+#: ./doc/common/tables/heat-common.xml8(caption)
+#: ./doc/common/tables/nova-common.xml8(caption)
+#: ./doc/common/tables/trove-common.xml8(caption)
+#: ./doc/common/tables/cinder-common.xml8(caption)
+#: ./doc/common/tables/glance-common.xml8(caption)
+#: ./doc/common/tables/neutron-common.xml8(caption)
+msgid "Description of configuration options for common"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-common.xml23(td)
 #: ./doc/common/tables/cinder-api.xml31(td)
 #: ./doc/common/tables/heat-debug.xml23(td)
-#: ./doc/common/tables/ceilometer-common.xml23(td)
 #: ./doc/common/tables/neutron-testing.xml23(td)
+#: ./doc/common/tables/trove-debug.xml23(td)
+#: ./doc/common/tables/keystone-debug.xml23(td)
 msgid ""
 "(StrOpt) Enable eventlet backdoor. Acceptable values are 0, &lt;port&gt;, "
 "and &lt;start&gt;:&lt;end&gt;, where 0 results in listening on a random tcp "
@@ -25588,256 +29290,615 @@ msgid ""
 "displayed in the service's log file."
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml26(td)
-#: ./doc/common/tables/trove-debug.xml30(td)
-#: ./doc/common/tables/glance-logging.xml22(td)
+#: ./doc/common/tables/ceilometer-common.xml26(td)
+#: ./doc/common/tables/nova-common.xml38(td)
+#: ./doc/common/tables/cinder-common.xml42(td)
+#: ./doc/common/tables/heat-debug.xml30(td)
+#: ./doc/common/tables/glance-common.xml46(td)
+#: ./doc/common/tables/neutron-common.xml122(td)
+#: ./doc/common/tables/trove-debug.xml34(td)
+#: ./doc/common/tables/keystone-debug.xml30(td)
+msgid "disable_process_locking = False"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-common.xml27(td)
+msgid "(BoolOpt) Whether to disable inter-process locks."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-common.xml30(td)
+#: ./doc/common/tables/neutron-logging.xml30(td)
+#: ./doc/common/tables/glance-logging.xml30(td)
+#: ./doc/common/tables/cinder-common.xml50(td)
+#: ./doc/common/tables/heat-debug.xml34(td)
+#: ./doc/common/tables/nova-logging.xml30(td)
+#: ./doc/common/tables/trove-debug.xml38(td)
+#: ./doc/common/tables/keystone-debug.xml34(td)
+msgid "fatal_deprecations = False"
+msgstr "fatal_deprecations = False"
+
+#: ./doc/common/tables/ceilometer-common.xml31(td)
+#: ./doc/common/tables/glance-logging.xml31(td)
+#: ./doc/common/tables/cinder-common.xml51(td)
+#: ./doc/common/tables/keystone-debug.xml35(td)
+msgid "(BoolOpt) Make deprecations fatal"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-common.xml42(td)
+msgid "notification_workers = 1"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-common.xml43(td)
+msgid ""
+"(IntOpt) Number of workers for notification service. A single notification "
+"agent is enabled by default."
+msgstr ""
+
+#: ./doc/common/tables/cinder-database.xml22(td)
+#: ./doc/common/tables/nova-baremetal.xml22(td)
+#: ./doc/common/tables/heat-database.xml22(td)
+msgid "db_backend = sqlalchemy"
+msgstr ""
+
+#: ./doc/common/tables/cinder-database.xml26(td)
+msgid "db_driver = cinder.db"
+msgstr ""
+
+#: ./doc/common/tables/cinder-database.xml27(td)
+msgid "(StrOpt) driver to use for database access"
+msgstr "(StrOpt)  pilote à utiliser pour l’accès à la base de données"
+
+#: ./doc/common/tables/ceilometer-logging.xml8(caption)
+#: ./doc/common/tables/neutron-logging.xml8(caption)
+#: ./doc/common/tables/glance-logging.xml8(caption)
+#: ./doc/common/tables/keystone-logging.xml8(caption)
+#: ./doc/common/tables/heat-logging.xml8(caption)
+#: ./doc/common/tables/nova-logging.xml8(caption)
+#: ./doc/common/tables/trove-logging.xml8(caption)
+msgid "Description of configuration options for logging"
+msgstr ""
+
 #: ./doc/common/tables/ceilometer-logging.xml22(td)
-#: ./doc/common/tables/heat-debug.xml26(td)
 #: ./doc/common/tables/neutron-logging.xml22(td)
-#: ./doc/common/tables/nova-logging.xml22(td)
+#: ./doc/common/tables/glance-logging.xml22(td)
 #: ./doc/common/tables/cinder-common.xml26(td)
+#: ./doc/common/tables/heat-debug.xml26(td)
+#: ./doc/common/tables/nova-logging.xml22(td)
+#: ./doc/common/tables/trove-debug.xml30(td)
+#: ./doc/common/tables/keystone-debug.xml26(td)
 msgid "debug = False"
 msgstr "debug = False"
 
-#: ./doc/common/tables/keystone-debug.xml27(td)
-#: ./doc/common/tables/trove-debug.xml31(td)
-#: ./doc/common/tables/glance-logging.xml23(td)
 #: ./doc/common/tables/ceilometer-logging.xml23(td)
-#: ./doc/common/tables/heat-debug.xml27(td)
 #: ./doc/common/tables/neutron-logging.xml23(td)
-#: ./doc/common/tables/nova-logging.xml23(td)
+#: ./doc/common/tables/glance-logging.xml23(td)
 #: ./doc/common/tables/cinder-common.xml27(td)
+#: ./doc/common/tables/heat-debug.xml27(td)
+#: ./doc/common/tables/nova-logging.xml23(td)
+#: ./doc/common/tables/trove-debug.xml31(td)
+#: ./doc/common/tables/keystone-debug.xml27(td)
 msgid ""
 "(BoolOpt) Print debugging output (set logging level to DEBUG instead of "
 "default WARNING level)."
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml30(td)
-#: ./doc/common/tables/neutron-common.xml122(td)
-#: ./doc/common/tables/nova-common.xml38(td)
-#: ./doc/common/tables/trove-debug.xml34(td)
-#: ./doc/common/tables/heat-debug.xml30(td)
-#: ./doc/common/tables/glance-common.xml46(td)
-#: ./doc/common/tables/cinder-common.xml42(td)
-#: ./doc/common/tables/ceilometer-common.xml26(td)
-msgid "disable_process_locking = False"
+#: ./doc/common/tables/ceilometer-logging.xml26(td)
+#: ./doc/common/tables/glance-logging.xml26(td)
+#: ./doc/common/tables/keystone-logging.xml22(td)
+msgid ""
+"default_log_levels = amqp=WARN, amqplib=WARN, boto=WARN, qpid=WARN, "
+"sqlalchemy=WARN, suds=INFO, iso8601=WARN, "
+"requests.packages.urllib3.connectionpool=WARN"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml31(td)
-#: ./doc/common/tables/neutron-common.xml123(td)
-#: ./doc/common/tables/nova-common.xml39(td)
-#: ./doc/common/tables/trove-debug.xml35(td)
-#: ./doc/common/tables/heat-debug.xml31(td)
-#: ./doc/common/tables/glance-common.xml47(td)
-#: ./doc/common/tables/cinder-common.xml43(td)
-msgid "(BoolOpt) Whether to disable inter-process locks"
-msgstr "(BoolOpt) Faut-il désactiver les verrouillages inter-processus"
-
-#: ./doc/common/tables/keystone-debug.xml34(td)
-#: ./doc/common/tables/trove-debug.xml38(td)
-#: ./doc/common/tables/glance-logging.xml30(td)
-#: ./doc/common/tables/heat-debug.xml34(td)
-#: ./doc/common/tables/neutron-logging.xml30(td)
-#: ./doc/common/tables/nova-logging.xml30(td)
-#: ./doc/common/tables/cinder-common.xml50(td)
-#: ./doc/common/tables/ceilometer-common.xml30(td)
-msgid "fatal_deprecations = False"
-msgstr "fatal_deprecations = False"
-
-#: ./doc/common/tables/keystone-debug.xml35(td)
-#: ./doc/common/tables/glance-logging.xml31(td)
-#: ./doc/common/tables/cinder-common.xml51(td)
-#: ./doc/common/tables/ceilometer-common.xml31(td)
-msgid "(BoolOpt) Make deprecations fatal"
+#: ./doc/common/tables/ceilometer-logging.xml27(td)
+#: ./doc/common/tables/glance-logging.xml27(td)
+#: ./doc/common/tables/cinder-common.xml35(td)
+#: ./doc/common/tables/keystone-logging.xml23(td)
+msgid "(ListOpt) List of logger=LEVEL pairs"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml30(td)
+#: ./doc/common/tables/nova-compute.xml54(td)
+#: ./doc/common/tables/heat-amqp.xml34(td)
+#: ./doc/common/tables/trove-common.xml42(td)
+#: ./doc/common/tables/neutron-notifier.xml22(td)
+msgid "default_notification_level = INFO"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml31(td)
+#: ./doc/common/tables/nova-compute.xml55(td)
+#: ./doc/common/tables/heat-amqp.xml35(td)
+#: ./doc/common/tables/trove-common.xml43(td)
+#: ./doc/common/tables/neutron-notifier.xml23(td)
+msgid "(StrOpt) Default notification level for outgoing notifications"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml34(td)
+#: ./doc/common/tables/neutron-logging.xml34(td)
+#: ./doc/common/tables/glance-logging.xml34(td)
+#: ./doc/common/tables/keystone-logging.xml26(td)
+#: ./doc/common/tables/cinder-images.xml62(td)
+#: ./doc/common/tables/heat-logging.xml26(td)
+#: ./doc/common/tables/nova-logging.xml38(td)
+#: ./doc/common/tables/trove-logging.xml26(td)
+msgid "instance_format = \"[instance: %(uuid)s] \""
+msgstr "instance_format = \"[instance: %(uuid)s] \""
+
+#: ./doc/common/tables/ceilometer-logging.xml35(td)
+#: ./doc/common/tables/neutron-logging.xml35(td)
+#: ./doc/common/tables/glance-logging.xml35(td)
+#: ./doc/common/tables/keystone-logging.xml27(td)
+#: ./doc/common/tables/cinder-images.xml63(td)
+#: ./doc/common/tables/heat-logging.xml27(td)
+#: ./doc/common/tables/nova-logging.xml39(td)
+#: ./doc/common/tables/trove-logging.xml27(td)
+msgid ""
+"(StrOpt) If an instance is passed with the log message, format it like this"
+msgstr "(StrOpt)  Si une instance est passée dans le message de log, la formater ainsi"
+
+#: ./doc/common/tables/ceilometer-logging.xml38(td)
+#: ./doc/common/tables/neutron-logging.xml38(td)
+#: ./doc/common/tables/glance-logging.xml38(td)
+#: ./doc/common/tables/keystone-logging.xml30(td)
+#: ./doc/common/tables/cinder-images.xml66(td)
+#: ./doc/common/tables/heat-logging.xml30(td)
+#: ./doc/common/tables/nova-logging.xml42(td)
+#: ./doc/common/tables/trove-logging.xml30(td)
+msgid "instance_uuid_format = \"[instance: %(uuid)s] \""
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml39(td)
+#: ./doc/common/tables/neutron-logging.xml39(td)
+#: ./doc/common/tables/glance-logging.xml39(td)
+#: ./doc/common/tables/keystone-logging.xml31(td)
+#: ./doc/common/tables/cinder-images.xml67(td)
+#: ./doc/common/tables/heat-logging.xml31(td)
+#: ./doc/common/tables/nova-logging.xml43(td)
+#: ./doc/common/tables/trove-logging.xml31(td)
+msgid ""
+"(StrOpt) If an instance UUID is passed with the log message, format it like "
+"this"
+msgstr "(StrOpt)  Si l’UUID d’une instance est passé dans le message de log, le formater ainsi"
+
+#: ./doc/common/tables/ceilometer-logging.xml42(td)
+#: ./doc/common/tables/neutron-logging.xml42(td)
+#: ./doc/common/tables/glance-logging.xml42(td)
+#: ./doc/common/tables/cinder-common.xml74(td)
+#: ./doc/common/tables/keystone-logging.xml34(td)
+#: ./doc/common/tables/heat-logging.xml34(td)
+#: ./doc/common/tables/nova-logging.xml46(td)
+#: ./doc/common/tables/trove-logging.xml34(td)
+msgid "log_config_append = None"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml43(td)
+#: ./doc/common/tables/neutron-logging.xml43(td)
+#: ./doc/common/tables/glance-logging.xml43(td)
+#: ./doc/common/tables/cinder-common.xml75(td)
+#: ./doc/common/tables/keystone-logging.xml35(td)
+#: ./doc/common/tables/heat-logging.xml35(td)
+#: ./doc/common/tables/nova-logging.xml47(td)
+#: ./doc/common/tables/trove-logging.xml35(td)
+msgid ""
+"(StrOpt) The name of logging configuration file. It does not disable "
+"existing loggers, but just appends specified logging configuration to any "
+"other existing logging options. Please see the Python logging module "
+"documentation for details on logging configuration files."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml46(td)
+#: ./doc/common/tables/neutron-logging.xml46(td)
+#: ./doc/common/tables/glance-logging.xml46(td)
+#: ./doc/common/tables/cinder-common.xml78(td)
+#: ./doc/common/tables/keystone-logging.xml38(td)
+#: ./doc/common/tables/heat-logging.xml38(td)
+#: ./doc/common/tables/nova-logging.xml50(td)
+#: ./doc/common/tables/trove-logging.xml38(td)
+msgid "log_date_format = %Y-%m-%d %H:%M:%S"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml47(td)
+#: ./doc/common/tables/neutron-logging.xml47(td)
+#: ./doc/common/tables/glance-logging.xml47(td)
+#: ./doc/common/tables/cinder-common.xml79(td)
+#: ./doc/common/tables/keystone-logging.xml39(td)
+#: ./doc/common/tables/heat-logging.xml39(td)
+#: ./doc/common/tables/nova-logging.xml51(td)
+#: ./doc/common/tables/trove-logging.xml39(td)
+msgid ""
+"(StrOpt) Format string for %%(asctime)s in log records. Default: %(default)s"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml50(td)
+#: ./doc/common/tables/neutron-logging.xml50(td)
+#: ./doc/common/tables/glance-logging.xml50(td)
+#: ./doc/common/tables/cinder-common.xml82(td)
+#: ./doc/common/tables/keystone-logging.xml42(td)
+#: ./doc/common/tables/heat-logging.xml42(td)
+#: ./doc/common/tables/nova-logging.xml54(td)
+#: ./doc/common/tables/trove-logging.xml42(td)
+msgid "log_dir = None"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml51(td)
+#: ./doc/common/tables/neutron-logging.xml51(td)
+#: ./doc/common/tables/glance-logging.xml51(td)
+#: ./doc/common/tables/cinder-common.xml83(td)
+#: ./doc/common/tables/keystone-logging.xml43(td)
+#: ./doc/common/tables/heat-logging.xml43(td)
+#: ./doc/common/tables/nova-logging.xml55(td)
+#: ./doc/common/tables/trove-logging.xml43(td)
+msgid ""
+"(StrOpt) (Optional) The base directory used for relative --log-file paths"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml54(td)
+#: ./doc/common/tables/neutron-logging.xml54(td)
+#: ./doc/common/tables/glance-logging.xml54(td)
+#: ./doc/common/tables/cinder-common.xml86(td)
+#: ./doc/common/tables/keystone-logging.xml46(td)
+#: ./doc/common/tables/heat-logging.xml46(td)
+#: ./doc/common/tables/nova-logging.xml58(td)
+#: ./doc/common/tables/trove-logging.xml46(td)
+msgid "log_file = None"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml55(td)
+#: ./doc/common/tables/neutron-logging.xml55(td)
+#: ./doc/common/tables/glance-logging.xml55(td)
+#: ./doc/common/tables/cinder-common.xml87(td)
+#: ./doc/common/tables/keystone-logging.xml47(td)
+#: ./doc/common/tables/heat-logging.xml47(td)
+#: ./doc/common/tables/nova-logging.xml59(td)
+#: ./doc/common/tables/trove-logging.xml47(td)
+msgid ""
+"(StrOpt) (Optional) Name of log file to output to. If no default is set, "
+"logging will go to stdout."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml58(td)
+#: ./doc/common/tables/neutron-logging.xml58(td)
+#: ./doc/common/tables/glance-logging.xml58(td)
+#: ./doc/common/tables/cinder-common.xml90(td)
+#: ./doc/common/tables/keystone-logging.xml50(td)
+#: ./doc/common/tables/heat-logging.xml50(td)
+#: ./doc/common/tables/nova-logging.xml62(td)
+#: ./doc/common/tables/trove-logging.xml50(td)
+msgid "log_format = None"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml59(td)
+#: ./doc/common/tables/neutron-logging.xml59(td)
+#: ./doc/common/tables/glance-logging.xml59(td)
+#: ./doc/common/tables/cinder-common.xml91(td)
+#: ./doc/common/tables/keystone-logging.xml51(td)
+#: ./doc/common/tables/heat-logging.xml51(td)
+#: ./doc/common/tables/nova-logging.xml63(td)
+#: ./doc/common/tables/trove-logging.xml51(td)
+msgid ""
+"(StrOpt) DEPRECATED. A logging.Formatter log message format string which may"
+" use any of the available logging.LogRecord attributes. This option is "
+"deprecated. Please use logging_context_format_string and "
+"logging_default_format_string instead."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml62(td)
+#: ./doc/common/tables/neutron-logging.xml62(td)
+#: ./doc/common/tables/glance-logging.xml62(td)
+#: ./doc/common/tables/cinder-common.xml94(td)
+#: ./doc/common/tables/keystone-logging.xml54(td)
+#: ./doc/common/tables/heat-logging.xml54(td)
+#: ./doc/common/tables/trove-logging.xml54(td)
+msgid ""
+"logging_context_format_string = %(asctime)s.%(msecs)03d %(process)d "
+"%(levelname)s %(name)s [%(request_id)s %(user_identity)s] "
+"%(instance)s%(message)s"
+msgstr "logging_context_format_string = %(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [%(request_id)s %(user_identity)s] %(instance)s%(message)s"
+
+#: ./doc/common/tables/ceilometer-logging.xml63(td)
+#: ./doc/common/tables/glance-logging.xml63(td)
+#: ./doc/common/tables/cinder-common.xml95(td)
+#: ./doc/common/tables/keystone-logging.xml55(td)
+msgid "(StrOpt) Format string to use for log messages with context"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml66(td)
+#: ./doc/common/tables/neutron-logging.xml66(td)
+#: ./doc/common/tables/glance-logging.xml66(td)
+#: ./doc/common/tables/cinder-common.xml98(td)
+#: ./doc/common/tables/keystone-logging.xml58(td)
+#: ./doc/common/tables/heat-logging.xml58(td)
+#: ./doc/common/tables/nova-logging.xml70(td)
+#: ./doc/common/tables/trove-logging.xml58(td)
+msgid "logging_debug_format_suffix = %(funcName)s %(pathname)s:%(lineno)d"
+msgstr "logging_debug_format_suffix = %(funcName)s %(pathname)s:%(lineno)d"
+
+#: ./doc/common/tables/ceilometer-logging.xml67(td)
+#: ./doc/common/tables/glance-logging.xml67(td)
+#: ./doc/common/tables/cinder-common.xml99(td)
+#: ./doc/common/tables/keystone-logging.xml59(td)
+msgid "(StrOpt) Data to append to log format when level is DEBUG"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml70(td)
+#: ./doc/common/tables/neutron-logging.xml70(td)
+#: ./doc/common/tables/glance-logging.xml70(td)
+#: ./doc/common/tables/cinder-common.xml102(td)
+#: ./doc/common/tables/keystone-logging.xml62(td)
+#: ./doc/common/tables/heat-logging.xml62(td)
+#: ./doc/common/tables/nova-logging.xml74(td)
+#: ./doc/common/tables/trove-logging.xml62(td)
+msgid ""
+"logging_default_format_string = %(asctime)s.%(msecs)03d %(process)d "
+"%(levelname)s %(name)s [-] %(instance)s%(message)s"
+msgstr "logging_default_format_string = %(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [-] %(instance)s%(message)s"
+
+#: ./doc/common/tables/ceilometer-logging.xml71(td)
+#: ./doc/common/tables/glance-logging.xml71(td)
+#: ./doc/common/tables/cinder-common.xml103(td)
+#: ./doc/common/tables/keystone-logging.xml63(td)
+msgid "(StrOpt) Format string to use for log messages without context"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml74(td)
+#: ./doc/common/tables/neutron-logging.xml74(td)
+#: ./doc/common/tables/glance-logging.xml74(td)
+#: ./doc/common/tables/cinder-common.xml106(td)
+#: ./doc/common/tables/keystone-logging.xml66(td)
+#: ./doc/common/tables/heat-logging.xml66(td)
+#: ./doc/common/tables/nova-logging.xml78(td)
+#: ./doc/common/tables/trove-logging.xml66(td)
+msgid ""
+"logging_exception_prefix = %(asctime)s.%(msecs)03d %(process)d TRACE "
+"%(name)s %(instance)s"
+msgstr "logging_exception_prefix = %(asctime)s.%(msecs)03d %(process)d TRACE %(name)s %(instance)s"
+
+#: ./doc/common/tables/ceilometer-logging.xml75(td)
+#: ./doc/common/tables/glance-logging.xml75(td)
+#: ./doc/common/tables/cinder-common.xml107(td)
+#: ./doc/common/tables/keystone-logging.xml67(td)
+msgid "(StrOpt) Prefix each line of exception output with this format"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml38(td)
-#: ./doc/common/tables/trove-logging.xml74(td)
-#: ./doc/common/tables/heat-notification.xml26(td)
-#: ./doc/common/tables/cinder-rpc.xml90(td)
-#: ./doc/common/tables/glance-logging.xml78(td)
 #: ./doc/common/tables/ceilometer-logging.xml78(td)
 #: ./doc/common/tables/neutron-logging.xml78(td)
+#: ./doc/common/tables/heat-notification.xml26(td)
+#: ./doc/common/tables/glance-logging.xml78(td)
+#: ./doc/common/tables/cinder-rpc.xml90(td)
 #: ./doc/common/tables/nova-logging.xml82(td)
+#: ./doc/common/tables/trove-logging.xml74(td)
+#: ./doc/common/tables/keystone-debug.xml38(td)
 msgid "publish_errors = False"
 msgstr "publish_errors = False"
 
-#: ./doc/common/tables/keystone-debug.xml39(td)
-#: ./doc/common/tables/cinder-rpc.xml91(td)
-#: ./doc/common/tables/glance-logging.xml79(td)
 #: ./doc/common/tables/ceilometer-logging.xml79(td)
+#: ./doc/common/tables/glance-logging.xml79(td)
+#: ./doc/common/tables/cinder-rpc.xml91(td)
+#: ./doc/common/tables/keystone-debug.xml39(td)
 msgid "(BoolOpt) Publish error events"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml42(td)
-#: ./doc/common/tables/trove-debug.xml46(td)
-msgid "pydev_debug_host = None"
+#: ./doc/common/tables/ceilometer-logging.xml82(td)
+#: ./doc/common/tables/neutron-logging.xml82(td)
+#: ./doc/common/tables/glance-logging.xml82(td)
+#: ./doc/common/tables/cinder-common.xml194(td)
+#: ./doc/common/tables/keystone-logging.xml70(td)
+#: ./doc/common/tables/heat-logging.xml70(td)
+#: ./doc/common/tables/nova-logging.xml86(td)
+#: ./doc/common/tables/trove-logging.xml78(td)
+msgid "syslog_log_facility = LOG_USER"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml43(td)
-msgid "(StrOpt) Host to connect to for remote debugger."
+#: ./doc/common/tables/ceilometer-logging.xml83(td)
+#: ./doc/common/tables/glance-logging.xml83(td)
+#: ./doc/common/tables/cinder-common.xml195(td)
+#: ./doc/common/tables/keystone-logging.xml71(td)
+msgid "(StrOpt) Syslog facility to receive log lines"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml46(td)
-#: ./doc/common/tables/trove-debug.xml50(td)
-msgid "pydev_debug_port = None"
+#: ./doc/common/tables/ceilometer-logging.xml86(td)
+#: ./doc/common/tables/neutron-logging.xml90(td)
+#: ./doc/common/tables/glance-logging.xml86(td)
+#: ./doc/common/tables/cinder-common.xml210(td)
+#: ./doc/common/tables/keystone-logging.xml74(td)
+#: ./doc/common/tables/heat-logging.xml74(td)
+#: ./doc/common/tables/nova-logging.xml90(td)
+#: ./doc/common/tables/trove-logging.xml82(td)
+msgid "use_stderr = True"
+msgstr "use_stderr = True"
+
+#: ./doc/common/tables/ceilometer-logging.xml87(td)
+#: ./doc/common/tables/neutron-logging.xml91(td)
+#: ./doc/common/tables/glance-logging.xml87(td)
+#: ./doc/common/tables/cinder-common.xml211(td)
+#: ./doc/common/tables/keystone-logging.xml75(td)
+#: ./doc/common/tables/heat-logging.xml75(td)
+#: ./doc/common/tables/nova-logging.xml91(td)
+#: ./doc/common/tables/trove-logging.xml83(td)
+msgid "(BoolOpt) Log output to standard error"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml47(td)
-msgid "(IntOpt) Port to connect to for remote debugger."
+#: ./doc/common/tables/ceilometer-logging.xml90(td)
+#: ./doc/common/tables/neutron-logging.xml94(td)
+#: ./doc/common/tables/neutron-rootwrap.xml30(td)
+#: ./doc/common/tables/nova-rootwrap.xml30(td)
+#: ./doc/common/tables/glance-logging.xml90(td)
+#: ./doc/common/tables/cinder-common.xml214(td)
+#: ./doc/common/tables/keystone-logging.xml78(td)
+#: ./doc/common/tables/heat-logging.xml78(td)
+#: ./doc/common/tables/nova-logging.xml94(td)
+#: ./doc/common/tables/trove-logging.xml86(td)
+#: ./doc/common/tables/cinder-rootwrap.xml30(td)
+msgid "use_syslog = False"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml50(td)
-msgid "standard_threads = False"
+#: ./doc/common/tables/ceilometer-logging.xml91(td)
+#: ./doc/common/tables/glance-logging.xml91(td)
+#: ./doc/common/tables/cinder-common.xml215(td)
+#: ./doc/common/tables/keystone-logging.xml79(td)
+#: ./doc/common/tables/nova-logging.xml95(td)
+msgid ""
+"(BoolOpt) Use syslog for logging. Existing syslog format is DEPRECATED "
+"during I, and then will be changed in J to honor RFC5424"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml51(td)
-msgid "(BoolOpt) Do not monkey-patch threading system modules."
+#: ./doc/common/tables/ceilometer-logging.xml94(td)
+#: ./doc/common/tables/glance-logging.xml94(td)
+#: ./doc/common/tables/cinder-common.xml218(td)
+#: ./doc/common/tables/keystone-logging.xml82(td)
+#: ./doc/common/tables/nova-logging.xml98(td)
+msgid "use_syslog_rfc_format = False"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml95(td)
+#: ./doc/common/tables/glance-logging.xml95(td)
+#: ./doc/common/tables/cinder-common.xml219(td)
+#: ./doc/common/tables/keystone-logging.xml83(td)
+#: ./doc/common/tables/nova-logging.xml99(td)
+msgid ""
+"(BoolOpt) (Optional) Use syslog rfc5424 format for logging. If enabled, will"
+" add APP-NAME (RFC5424) before the MSG part of the syslog message. The old "
+"format without APP-NAME is deprecated in I, and will be removed in J."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml98(td)
+#: ./doc/common/tables/neutron-logging.xml98(td)
+#: ./doc/common/tables/glance-logging.xml98(td)
+#: ./doc/common/tables/cinder-common.xml222(td)
+#: ./doc/common/tables/keystone-logging.xml86(td)
+#: ./doc/common/tables/heat-logging.xml82(td)
+#: ./doc/common/tables/nova-logging.xml102(td)
+#: ./doc/common/tables/trove-debug.xml78(td)
+msgid "verbose = False"
+msgstr "verbose = False"
+
+#: ./doc/common/tables/ceilometer-logging.xml99(td)
+#: ./doc/common/tables/neutron-logging.xml99(td)
+#: ./doc/common/tables/glance-logging.xml99(td)
+#: ./doc/common/tables/cinder-common.xml223(td)
+#: ./doc/common/tables/keystone-logging.xml87(td)
+#: ./doc/common/tables/heat-logging.xml83(td)
+#: ./doc/common/tables/nova-logging.xml103(td)
+#: ./doc/common/tables/trove-debug.xml79(td)
+msgid ""
+"(BoolOpt) Print more verbose output (set logging level to INFO instead of "
+"default WARNING level)."
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml54(th)
 #: ./doc/common/tables/ceilometer-logging.xml102(th)
 #: ./doc/common/tables/neutron-cadf.xml19(th)
+#: ./doc/common/tables/keystone-debug.xml54(th)
 msgid "[audit]"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml57(td)
+#: ./doc/common/tables/ceilometer-logging.xml105(td)
+#: ./doc/common/tables/neutron-cadf.xml22(td)
+msgid "api_audit_map = api_audit_map.conf"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml106(td)
+#: ./doc/common/tables/neutron-cadf.xml23(td)
+msgid "(StrOpt) File containing mapping for api paths and service endpoints"
+msgstr ""
+
 #: ./doc/common/tables/ceilometer-logging.xml109(td)
 #: ./doc/common/tables/neutron-cadf.xml26(td)
+#: ./doc/common/tables/keystone-debug.xml57(td)
 msgid "namespace = openstack"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml58(td)
 #: ./doc/common/tables/ceilometer-logging.xml110(td)
 #: ./doc/common/tables/neutron-cadf.xml27(td)
+#: ./doc/common/tables/keystone-debug.xml58(td)
 msgid "(StrOpt) namespace prefix for generated id"
 msgstr ""
 
-#: ./doc/common/tables/glance-policy.xml8(caption)
-#: ./doc/common/tables/nova-policy.xml8(caption)
-#: ./doc/common/tables/neutron-policy.xml8(caption)
-#: ./doc/common/tables/keystone-policy.xml8(caption)
-msgid "Description of configuration options for policy"
+#: ./doc/common/tables/heat-common.xml22(td)
+msgid "deferred_auth_method = password"
+msgstr "deferred_auth_method = password"
+
+#: ./doc/common/tables/heat-common.xml23(td)
+msgid "(StrOpt) Select deferred auth method, stored password or trusts."
 msgstr ""
 
-#: ./doc/common/tables/glance-policy.xml22(td)
-#: ./doc/common/tables/nova-policy.xml58(td)
-#: ./doc/common/tables/ceilometer-api.xml34(td)
-#: ./doc/common/tables/cinder-common.xml138(td)
-#: ./doc/common/tables/heat-api.xml42(td)
-#: ./doc/common/tables/keystone-policy.xml22(td)
-msgid "policy_default_rule = default"
-msgstr "policy_default_rule = default"
+#: ./doc/common/tables/heat-common.xml26(td)
+msgid "environment_dir = /etc/heat/environment.d"
+msgstr "environment_dir = /etc/heat/environment.d"
 
-#: ./doc/common/tables/glance-policy.xml23(td)
-msgid "(StrOpt) The default policy to use."
+#: ./doc/common/tables/heat-common.xml27(td)
+msgid "(StrOpt) The directory to search for environment files."
 msgstr ""
 
-#: ./doc/common/tables/glance-policy.xml26(td)
-#: ./doc/common/tables/nova-policy.xml62(td)
-#: ./doc/common/tables/ceilometer-api.xml38(td)
-#: ./doc/common/tables/cinder-common.xml142(td)
-#: ./doc/common/tables/neutron-policy.xml26(td)
-#: ./doc/common/tables/heat-api.xml46(td)
-#: ./doc/common/tables/keystone-policy.xml26(td)
-msgid "policy_file = policy.json"
-msgstr "policy_file = policy.json"
+#: ./doc/common/tables/heat-common.xml30(td)
+msgid "event_purge_batch_size = 10"
+msgstr "event_purge_batch_size = 10"
 
-#: ./doc/common/tables/glance-policy.xml27(td)
-msgid "(StrOpt) The location of the policy file."
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml8(caption)
-msgid "Description of configuration options for mlnx"
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml19(th)
-#: ./doc/common/tables/neutron-ml2_mlnx.xml19(th)
-#: ./doc/common/tables/neutron-vmware.xml70(th)
-msgid "[ESWITCH]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml22(td)
-msgid "backoff_rate = 2"
-msgstr "backoff_rate = 2"
-
-#: ./doc/common/tables/neutron-mlnx.xml23(td)
+#: ./doc/common/tables/heat-common.xml31(td)
 msgid ""
-"(IntOpt) backoff rate multiplier for waiting period between retries for "
-"request to daemon, i.e. value of 2 will double the request timeout each "
-"retry"
+"(IntOpt) Controls how many events will be pruned whenever a stack's events "
+"exceed max_events_per_stack. Set this lower to keep more events at the "
+"expense of more frequent purges."
 msgstr ""
 
-#: ./doc/common/tables/neutron-mlnx.xml26(td)
-msgid "daemon_endpoint = tcp://127.0.0.1:60001"
-msgstr "daemon_endpoint = tcp://127.0.0.1:60001"
+#: ./doc/common/tables/heat-common.xml34(td)
+msgid "instance_driver = heat.engine.nova"
+msgstr "instance_driver = heat.engine.nova"
 
-#: ./doc/common/tables/neutron-mlnx.xml27(td)
-msgid "(StrOpt) eswitch daemon end point"
+#: ./doc/common/tables/heat-common.xml35(td)
+msgid "(StrOpt) Driver to use for controlling instances."
 msgstr ""
 
-#: ./doc/common/tables/neutron-mlnx.xml30(td)
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml22(td)
-msgid "physical_interface_mappings ="
-msgstr ""
+#: ./doc/common/tables/heat-common.xml38(td)
+msgid "instance_user = ec2-user"
+msgstr "instance_user = ec2-user"
 
-#: ./doc/common/tables/neutron-mlnx.xml31(td)
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml23(td)
-msgid "(ListOpt) List of &lt;physical_network&gt;:&lt;physical_interface&gt;"
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml34(td)
-msgid "request_timeout = 3000"
-msgstr "request_timeout = 3000"
-
-#: ./doc/common/tables/neutron-mlnx.xml35(td)
+#: ./doc/common/tables/heat-common.xml39(td)
 msgid ""
-"(IntOpt) The number of milliseconds the agent will wait for response on "
-"request to daemon."
+"(StrOpt) The default user for new instances. This option is deprecated and "
+"will be removed in the Juno release. If it's empty, Heat will use the "
+"default user set up with your cloud image (for OS::Nova::Server) or "
+"'ec2-user' (for AWS::EC2::Instance)."
 msgstr ""
 
-#: ./doc/common/tables/neutron-mlnx.xml38(th)
-msgid "[MLNX]"
+#: ./doc/common/tables/heat-common.xml42(td)
+msgid "keystone_backend = heat.common.heat_keystoneclient.KeystoneClientV3"
+msgstr "keystone_backend = heat.common.heat_keystoneclient.KeystoneClientV3"
+
+#: ./doc/common/tables/heat-common.xml43(td)
+msgid "(StrOpt) Fully qualified class name to use as a keystone backend."
 msgstr ""
 
-#: ./doc/common/tables/neutron-mlnx.xml41(td)
-msgid "network_vlan_ranges = default:1:1000"
+#: ./doc/common/tables/heat-common.xml46(td)
+#: ./doc/common/tables/cinder-common.xml134(td)
+#: ./doc/common/tables/trove-rpc.xml42(td)
+msgid "periodic_interval = 60"
 msgstr ""
 
-#: ./doc/common/tables/neutron-mlnx.xml42(td)
-#: ./doc/common/tables/neutron-openvswitch_agent.xml92(td)
-#: ./doc/common/tables/neutron-hyperv_agent.xml46(td)
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml30(td)
+#: ./doc/common/tables/heat-common.xml47(td)
+msgid "(IntOpt) Seconds between running periodic tasks."
+msgstr ""
+
+#: ./doc/common/tables/heat-common.xml50(td)
+msgid "plugin_dirs = /usr/lib64/heat, /usr/lib/heat"
+msgstr "plugin_dirs = /usr/lib64/heat, /usr/lib/heat"
+
+#: ./doc/common/tables/heat-common.xml51(td)
+msgid "(ListOpt) List of directories to search for plug-ins."
+msgstr ""
+
+#: ./doc/common/tables/heat-common.xml54(th)
+msgid "[revision]"
+msgstr "[revision]"
+
+#: ./doc/common/tables/heat-common.xml57(td)
+msgid "heat_revision = unknown"
+msgstr "heat_revision = unknown"
+
+#: ./doc/common/tables/heat-common.xml58(td)
 msgid ""
-"(ListOpt) List of &lt;physical_network&gt;:&lt;vlan_min&gt;:&lt;vlan_max&gt;"
-" or &lt;physical_network&gt;"
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml45(td)
-msgid "physical_network_type = eth"
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml46(td)
-msgid "(StrOpt) Physical network type for provider network (eth or ib)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml49(td)
-msgid "physical_network_type_mappings ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml50(td)
-msgid ""
-"(ListOpt) List of &lt;physical_network&gt;:&lt;physical_network_type&gt; "
-"with physical_network_type is either eth or ib"
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml53(td)
-msgid "tenant_network_type = vlan"
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml54(td)
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml34(td)
-msgid "(StrOpt) Network type for tenant networks (local, vlan, or none)"
+"(StrOpt) Heat build revision. If you would prefer to manage your build "
+"revision separately, you can move this section to a different file and add "
+"it as another config option."
 msgstr ""
 
 #: ./doc/common/tables/nova-ipv6.xml8(caption)
@@ -25876,202 +29937,68 @@ msgstr "use_ipv6 = False"
 msgid "(BoolOpt) Use IPv6"
 msgstr ""
 
-#: ./doc/common/tables/cinder-eqlx.xml8(caption)
-msgid "Description of configuration options for eqlx"
+#: ./doc/common/tables/nova-vnc.xml8(caption)
+msgid "Description of configuration options for vnc"
 msgstr ""
 
-#: ./doc/common/tables/cinder-eqlx.xml22(td)
-msgid "eqlx_chap_login = admin"
-msgstr "eqlx_chap_login = admin"
-
-#: ./doc/common/tables/cinder-eqlx.xml23(td)
-msgid "(StrOpt) Existing CHAP account name"
+#: ./doc/common/tables/nova-vnc.xml22(td)
+msgid "novncproxy_base_url = http://127.0.0.1:6080/vnc_auto.html"
 msgstr ""
 
-#: ./doc/common/tables/cinder-eqlx.xml26(td)
-msgid "eqlx_chap_password = password"
-msgstr "eqlx_chap_password = password"
-
-#: ./doc/common/tables/cinder-eqlx.xml27(td)
-msgid "(StrOpt) Password for specified CHAP account name"
-msgstr ""
-
-#: ./doc/common/tables/cinder-eqlx.xml30(td)
-msgid "eqlx_cli_max_retries = 5"
-msgstr "eqlx_cli_max_retries = 5"
-
-#: ./doc/common/tables/cinder-eqlx.xml31(td)
-msgid "(IntOpt) Maximum retry count for reconnection"
-msgstr ""
-
-#: ./doc/common/tables/cinder-eqlx.xml34(td)
-msgid "eqlx_cli_timeout = 30"
-msgstr "eqlx_cli_timeout = 30"
-
-#: ./doc/common/tables/cinder-eqlx.xml35(td)
-msgid "(IntOpt) Timeout for the Group Manager cli command execution"
-msgstr ""
-
-#: ./doc/common/tables/cinder-eqlx.xml38(td)
-msgid "eqlx_group_name = group-0"
-msgstr "eqlx_group_name = group-0"
-
-#: ./doc/common/tables/cinder-eqlx.xml39(td)
-msgid "(StrOpt) Group name to use for creating volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-eqlx.xml42(td)
-msgid "eqlx_pool = default"
-msgstr "eqlx_pool = default"
-
-#: ./doc/common/tables/cinder-eqlx.xml43(td)
-msgid "(StrOpt) Pool in which volumes will be created"
-msgstr ""
-
-#: ./doc/common/tables/cinder-eqlx.xml46(td)
-msgid "eqlx_use_chap = False"
-msgstr "eqlx_use_chap = False"
-
-#: ./doc/common/tables/cinder-eqlx.xml47(td)
-msgid "(BoolOpt) Use CHAP authentication for targets?"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml7(literal)
-msgid "[filter:catch_errors]"
-msgstr "[filter:catch_errors]"
-
-#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml7(literal)
-#: ./doc/common/tables/swift-object-expirer-filter-cache.xml7(literal)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml7(literal)
-#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml7(literal)
-#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml7(literal)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml7(literal)
-msgid "object-expirer.conf-sample"
-msgstr "object-expirer.conf-sample"
-
-#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml7(caption)
-#: ./doc/common/tables/swift-object-expirer-filter-cache.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml7(caption)
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml7(caption)
-#: ./doc/common/tables/swift-container-server-container-updater.xml7(caption)
-#: ./doc/common/tables/swift-account-server-filter-recon.xml7(caption)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml7(caption)
-#: ./doc/common/tables/swift-container-server-container-sync.xml7(caption)
-#: ./doc/common/tables/swift-object-server-object-auditor.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml7(caption)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml7(caption)
-#: ./doc/common/tables/swift-object-server-object-updater.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml7(caption)
-#: ./doc/common/tables/swift-container-server-pipeline-main.xml7(caption)
-#: ./doc/common/tables/swift-rsyncd-object.xml7(caption)
-#: ./doc/common/tables/swift-object-server-pipeline-main.xml7(caption)
-#: ./doc/common/tables/swift-account-server-app-account-server.xml7(caption)
-#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml7(caption)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml7(caption)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml7(caption)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml7(caption)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml7(caption)
-#: ./doc/common/tables/swift-rsyncd-account.xml7(caption)
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml7(caption)
-#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml7(caption)
-#: ./doc/common/tables/swift-swift-swift-constraints.xml7(caption)
-#: ./doc/common/tables/swift-object-server-filter-recon.xml7(caption)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml7(caption)
-#: ./doc/common/tables/swift-memcache-memcache.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml7(caption)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml7(caption)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml7(caption)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml7(caption)
-#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml7(caption)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml7(caption)
-#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml7(caption)
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml7(caption)
-#: ./doc/common/tables/swift-container-server-filter-recon.xml7(caption)
-#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml7(caption)
-#: ./doc/common/tables/swift-swift-swift-hash.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml7(caption)
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml7(caption)
-#: ./doc/common/tables/swift-rsyncd-container.xml7(caption)
-#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml7(caption)
-#: ./doc/common/tables/swift-account-server-pipeline-main.xml7(caption)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml7(caption)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml7(caption)
+#: ./doc/common/tables/nova-vnc.xml23(td)
 msgid ""
-"Description of configuration options for <placeholder-1/> in "
-"<placeholder-2/>"
+"(StrOpt) Location of VNC console proxy, in the form "
+"\"http://127.0.0.1:6080/vnc_auto.html\""
 msgstr ""
 
-#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml18(td)
-msgid "use = egg:swift#catch_errors"
-msgstr "use = egg:swift#catch_errors"
-
-#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml18(td)
-#: ./doc/common/tables/swift-object-expirer-filter-cache.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml18(td)
-#: ./doc/common/tables/swift-account-server-filter-recon.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml18(td)
-#: ./doc/common/tables/swift-account-server-app-account-server.xml18(td)
-#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml18(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml18(td)
-#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml18(td)
-#: ./doc/common/tables/swift-object-server-filter-recon.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml18(td)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml18(td)
-#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml18(td)
-#: ./doc/common/tables/swift-container-server-filter-recon.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml18(td)
-#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml18(td)
-msgid "Entry point of paste.deploy in the server"
+#: ./doc/common/tables/nova-vnc.xml26(td)
+msgid "vnc_enabled = True"
 msgstr ""
 
-#: ./doc/common/tables/swift-object-expirer-filter-cache.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml7(literal)
-msgid "[filter:cache]"
+#: ./doc/common/tables/nova-vnc.xml27(td)
+msgid "(BoolOpt) Enable VNC related features"
 msgstr ""
 
-#: ./doc/common/tables/swift-object-expirer-filter-cache.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml18(td)
-msgid "use = egg:swift#memcache"
+#: ./doc/common/tables/nova-vnc.xml30(td)
+msgid "vnc_keymap = en-us"
+msgstr ""
+
+#: ./doc/common/tables/nova-vnc.xml31(td)
+msgid "(StrOpt) Keymap for VNC"
+msgstr ""
+
+#: ./doc/common/tables/nova-vnc.xml34(td)
+msgid "vncserver_listen = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/nova-vnc.xml35(td)
+msgid "(StrOpt) IP address on which instance vncservers should listen"
+msgstr ""
+
+#: ./doc/common/tables/nova-vnc.xml38(td)
+msgid "vncserver_proxyclient_address = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/nova-vnc.xml39(td)
+msgid ""
+"(StrOpt) The address to which proxy clients (like nova-xvpvncproxy) should "
+"connect"
+msgstr ""
+
+#: ./doc/common/tables/nova-vnc.xml45(td)
+msgid "vnc_port = 5900"
+msgstr "vnc_port = 5900"
+
+#: ./doc/common/tables/nova-vnc.xml46(td)
+msgid "(IntOpt) VNC starting port"
+msgstr ""
+
+#: ./doc/common/tables/nova-vnc.xml49(td)
+msgid "vnc_port_total = 10000"
+msgstr "vnc_port_total = 10000"
+
+#: ./doc/common/tables/nova-vnc.xml50(td)
+msgid "(IntOpt) Total number of VNC ports"
 msgstr ""
 
 #: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml5(caption)
@@ -26235,189 +30162,2487 @@ msgid ""
 "provisioning on the storage controller."
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml7(literal)
+#: ./doc/common/tables/trove-qpid.xml8(caption)
+#: ./doc/common/tables/heat-qpid.xml8(caption)
+#: ./doc/common/tables/nova-qpid.xml8(caption)
+#: ./doc/common/tables/glance-qpid.xml8(caption)
+#: ./doc/common/tables/neutron-qpid.xml8(caption)
+#: ./doc/common/tables/keystone-qpid.xml8(caption)
+#: ./doc/common/tables/ceilometer-qpid.xml8(caption)
+msgid "Description of configuration options for qpid"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml22(td)
+#: ./doc/common/tables/heat-qpid.xml22(td)
+#: ./doc/common/tables/nova-qpid.xml22(td)
+#: ./doc/common/tables/glance-qpid.xml22(td)
+#: ./doc/common/tables/cinder-rpc.xml94(td)
+#: ./doc/common/tables/nova-rpc_all.xml62(td)
+#: ./doc/common/tables/neutron-qpid.xml22(td)
+#: ./doc/common/tables/keystone-qpid.xml22(td)
+#: ./doc/common/tables/ceilometer-qpid.xml22(td)
+msgid "qpid_heartbeat = 60"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml23(td)
+#: ./doc/common/tables/heat-qpid.xml23(td)
+#: ./doc/common/tables/neutron-qpid.xml23(td)
+#: ./doc/common/tables/ceilometer-qpid.xml23(td)
+msgid "(IntOpt) Seconds between connection keepalive heartbeats"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml26(td)
+#: ./doc/common/tables/heat-qpid.xml26(td)
+#: ./doc/common/tables/nova-qpid.xml26(td)
+#: ./doc/common/tables/glance-qpid.xml26(td)
+#: ./doc/common/tables/cinder-rpc.xml98(td)
+#: ./doc/common/tables/nova-rpc_all.xml66(td)
+#: ./doc/common/tables/neutron-qpid.xml26(td)
+#: ./doc/common/tables/keystone-qpid.xml26(td)
+#: ./doc/common/tables/ceilometer-qpid.xml26(td)
+msgid "qpid_hostname = localhost"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml27(td)
+#: ./doc/common/tables/heat-qpid.xml27(td)
+#: ./doc/common/tables/neutron-qpid.xml27(td)
+#: ./doc/common/tables/ceilometer-qpid.xml27(td)
+msgid "(StrOpt) Qpid broker hostname"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml30(td)
+#: ./doc/common/tables/heat-qpid.xml30(td)
+#: ./doc/common/tables/nova-qpid.xml30(td)
+#: ./doc/common/tables/glance-qpid.xml30(td)
+#: ./doc/common/tables/cinder-rpc.xml102(td)
+#: ./doc/common/tables/nova-rpc_all.xml70(td)
+#: ./doc/common/tables/neutron-qpid.xml30(td)
+#: ./doc/common/tables/keystone-qpid.xml30(td)
+#: ./doc/common/tables/ceilometer-qpid.xml30(td)
+msgid "qpid_hosts = $qpid_hostname:$qpid_port"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml31(td)
+#: ./doc/common/tables/heat-qpid.xml31(td)
+#: ./doc/common/tables/neutron-qpid.xml31(td)
+#: ./doc/common/tables/ceilometer-qpid.xml31(td)
+msgid "(ListOpt) Qpid HA cluster host:port pairs"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml34(td)
+#: ./doc/common/tables/heat-qpid.xml34(td)
+#: ./doc/common/tables/nova-qpid.xml34(td)
+#: ./doc/common/tables/glance-qpid.xml34(td)
+#: ./doc/common/tables/cinder-rpc.xml106(td)
+#: ./doc/common/tables/nova-rpc_all.xml74(td)
+#: ./doc/common/tables/neutron-qpid.xml34(td)
+#: ./doc/common/tables/keystone-qpid.xml34(td)
+#: ./doc/common/tables/ceilometer-qpid.xml34(td)
+msgid "qpid_password ="
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml35(td)
+#: ./doc/common/tables/heat-qpid.xml35(td)
+#: ./doc/common/tables/neutron-qpid.xml35(td)
+#: ./doc/common/tables/ceilometer-qpid.xml35(td)
+msgid "(StrOpt) Password for qpid connection"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml38(td)
+#: ./doc/common/tables/heat-qpid.xml38(td)
+#: ./doc/common/tables/nova-qpid.xml38(td)
+#: ./doc/common/tables/glance-qpid.xml38(td)
+#: ./doc/common/tables/cinder-rpc.xml110(td)
+#: ./doc/common/tables/nova-rpc_all.xml78(td)
+#: ./doc/common/tables/neutron-qpid.xml38(td)
+#: ./doc/common/tables/keystone-qpid.xml38(td)
+#: ./doc/common/tables/ceilometer-qpid.xml38(td)
+msgid "qpid_port = 5672"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml39(td)
+#: ./doc/common/tables/heat-qpid.xml39(td)
+#: ./doc/common/tables/neutron-qpid.xml39(td)
+#: ./doc/common/tables/ceilometer-qpid.xml39(td)
+msgid "(IntOpt) Qpid broker port"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml42(td)
+#: ./doc/common/tables/heat-qpid.xml42(td)
+#: ./doc/common/tables/nova-qpid.xml42(td)
+#: ./doc/common/tables/glance-qpid.xml42(td)
+#: ./doc/common/tables/cinder-rpc.xml114(td)
+#: ./doc/common/tables/nova-rpc_all.xml82(td)
+#: ./doc/common/tables/neutron-qpid.xml42(td)
+#: ./doc/common/tables/keystone-qpid.xml42(td)
+#: ./doc/common/tables/ceilometer-qpid.xml42(td)
+msgid "qpid_protocol = tcp"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml43(td)
+#: ./doc/common/tables/heat-qpid.xml43(td)
+#: ./doc/common/tables/neutron-qpid.xml43(td)
+#: ./doc/common/tables/ceilometer-qpid.xml43(td)
+msgid "(StrOpt) Transport to use, either 'tcp' or 'ssl'"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml46(td)
+#: ./doc/common/tables/heat-qpid.xml46(td)
+#: ./doc/common/tables/nova-qpid.xml46(td)
+#: ./doc/common/tables/glance-qpid.xml46(td)
+#: ./doc/common/tables/cinder-rpc.xml118(td)
+#: ./doc/common/tables/nova-rpc_all.xml86(td)
+#: ./doc/common/tables/neutron-qpid.xml46(td)
+#: ./doc/common/tables/keystone-qpid.xml46(td)
+#: ./doc/common/tables/ceilometer-qpid.xml46(td)
+msgid "qpid_sasl_mechanisms ="
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml47(td)
+#: ./doc/common/tables/heat-qpid.xml47(td)
+#: ./doc/common/tables/neutron-qpid.xml47(td)
+#: ./doc/common/tables/ceilometer-qpid.xml47(td)
+msgid "(StrOpt) Space separated list of SASL mechanisms to use for auth"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml50(td)
+#: ./doc/common/tables/heat-qpid.xml50(td)
+#: ./doc/common/tables/nova-qpid.xml50(td)
+#: ./doc/common/tables/glance-qpid.xml50(td)
+#: ./doc/common/tables/cinder-rpc.xml122(td)
+#: ./doc/common/tables/nova-rpc_all.xml90(td)
+#: ./doc/common/tables/neutron-qpid.xml50(td)
+#: ./doc/common/tables/keystone-qpid.xml50(td)
+#: ./doc/common/tables/ceilometer-qpid.xml50(td)
+msgid "qpid_tcp_nodelay = True"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml51(td)
+#: ./doc/common/tables/heat-qpid.xml51(td)
+#: ./doc/common/tables/neutron-qpid.xml51(td)
+#: ./doc/common/tables/ceilometer-qpid.xml51(td)
+msgid "(BoolOpt) Disable Nagle algorithm"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml54(td)
+#: ./doc/common/tables/heat-qpid.xml58(td)
+#: ./doc/common/tables/nova-qpid.xml58(td)
+#: ./doc/common/tables/glance-qpid.xml58(td)
+#: ./doc/common/tables/cinder-rpc.xml130(td)
+#: ./doc/common/tables/nova-rpc_all.xml98(td)
+#: ./doc/common/tables/neutron-qpid.xml58(td)
+#: ./doc/common/tables/keystone-qpid.xml58(td)
+#: ./doc/common/tables/ceilometer-qpid.xml58(td)
+msgid "qpid_username ="
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml55(td)
+#: ./doc/common/tables/heat-qpid.xml59(td)
+#: ./doc/common/tables/neutron-qpid.xml59(td)
+#: ./doc/common/tables/ceilometer-qpid.xml59(td)
+msgid "(StrOpt) Username for qpid connection"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml8(caption)
+#: ./doc/common/tables/trove-api.xml8(caption)
+#: ./doc/common/tables/glance-api.xml8(caption)
+#: ./doc/common/tables/ceilometer-api.xml8(caption)
+#: ./doc/common/tables/heat-api.xml8(caption)
+#: ./doc/common/tables/cinder-api.xml8(caption)
+#: ./doc/common/tables/nova-api.xml8(caption)
+#: ./doc/common/tables/neutron-api.xml8(caption)
+msgid "Description of configuration options for api"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml22(td)
+msgid "admin_bind_host = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml23(td)
+msgid ""
+"(StrOpt) The IP Address of the network interface to for the admin service to"
+" listen on."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml26(td)
+msgid "admin_endpoint = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml27(td)
+msgid ""
+"(StrOpt) The base admin endpoint URL for keystone that are advertised to "
+"clients (NOTE: this does NOT affect how keystone listens for connections). "
+"Defaults to the base host URL of the request. Eg a request to "
+"http://server:35357/v2.0/users will default to http://server:35357. You "
+"should only need to set this value if the base URL contains a path (eg "
+"/prefix/v2.0) or the endpoint should be found on a different server."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml30(td)
+msgid "admin_port = 35357"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml31(td)
+msgid "(IntOpt) The port number which the admin service listens on."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml34(td)
+msgid "admin_token = ADMIN"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml35(td)
+msgid ""
+"(StrOpt) A \"shared secret\" that can be used to bootstrap Keystone. This "
+"\"token\" does not represent a user, and carries no explicit authorization. "
+"To disable in production (highly recommended), remove "
+"AdminTokenAuthMiddleware from your paste application pipelines (for example,"
+" in keystone-paste.ini)."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml38(td)
+msgid "compute_port = 8774"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml39(td)
+msgid "(IntOpt) The port which the OpenStack Compute service listens on."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml42(td)
+msgid "domain_id_immutable = True"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml43(td)
+msgid ""
+"(BoolOpt) Set this to false if you want to enable the ability for user, "
+"group and project entities to be moved between domains by updating their "
+"domain_id. Allowing such movement is not recommended if the scope of a "
+"domain admin is being restricted by use of an appropriate policy file (see "
+"policy.v3cloudsample as an example)."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml47(td)
+msgid ""
+"(IntOpt) The maximum number of entities that will be returned in a "
+"collection can be set with list_limit, with no limit set by default. This "
+"global limit may be then overridden for a specific driver, by specifying a "
+"list_limit in the appropriate section (e.g. [assignment])."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml50(td)
+msgid "max_param_size = 64"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml51(td)
+msgid "(IntOpt) limit the sizes of user &amp; tenant ID/names."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml54(td)
+#: ./doc/common/tables/ceilometer-api.xml26(td)
+#: ./doc/common/tables/neutron-api.xml46(td)
+msgid "max_request_body_size = 114688"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml55(td)
+msgid ""
+"(IntOpt) enforced by optional sizelimit middleware "
+"(keystone.middleware:RequestBodySizeLimiter)."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml58(td)
+msgid "max_token_size = 8192"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml59(td)
+msgid ""
+"(IntOpt) similar to max_param_size, but provides an exception for token "
+"values."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml62(td)
+msgid "member_role_id = 9fe2ff9ee4384b1894a90878d3e92bab"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml63(td)
+msgid ""
+"(StrOpt) During a SQL upgrade member_role_id will be used to create a new "
+"role that will replace records in the user_tenant_membership table with "
+"explicit role grants. After migration, the member_role_id will be used in "
+"the API add_user_to_project."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml66(td)
+msgid "member_role_name = _member_"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml67(td)
+msgid ""
+"(StrOpt) During a SQL upgrade member_role_id will be used to create a new "
+"role that will replace records in the user_tenant_membership table with "
+"explicit role grants. After migration, member_role_name will be ignored."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml70(td)
+msgid "public_bind_host = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml71(td)
+msgid ""
+"(StrOpt) The IP Address of the network interface to for the public service "
+"to listen on."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml74(td)
+msgid "public_endpoint = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml75(td)
+msgid ""
+"(StrOpt) The base public endpoint URL for keystone that are advertised to "
+"clients (NOTE: this does NOT affect how keystone listens for connections). "
+"Defaults to the base host URL of the request. Eg a request to "
+"http://server:5000/v2.0/users will default to http://server:5000. You should"
+" only need to set this value if the base URL contains a path (eg "
+"/prefix/v2.0) or the endpoint should be found on a different server."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml78(td)
+msgid "public_port = 5000"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml79(td)
+msgid "(IntOpt) The port number which the public service listens on."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml82(td)
+msgid "tcp_keepalive = False"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml83(td)
+msgid ""
+"(BoolOpt) Set this to True if you want to enable TCP_KEEPALIVE on server "
+"sockets i.e. sockets used by the keystone wsgi server for client "
+"connections."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml86(td)
+#: ./doc/common/tables/trove-api.xml74(td)
+#: ./doc/common/tables/cinder-common.xml198(td)
+#: ./doc/common/tables/neutron-wsgi.xml30(td)
+#: ./doc/common/tables/glance-wsgi.xml34(td)
+#: ./doc/common/tables/nova-wsgi.xml38(td)
+msgid "tcp_keepidle = 600"
+msgstr "tcp_keepidle = 600"
+
+#: ./doc/common/tables/keystone-api.xml87(td)
+msgid ""
+"(IntOpt) Sets the value of TCP_KEEPIDLE in seconds for each server socket. "
+"Only applies if tcp_keepalive is True. Not supported on OS X."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml90(th)
+msgid "[endpoint_filter]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml93(td)
+msgid "driver = keystone.contrib.endpoint_filter.backends.sql.EndpointFilter"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml94(td)
+msgid "(StrOpt) Keystone Endpoint Filter backend driver"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml97(td)
+msgid "return_all_endpoints_if_no_filter = True"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml98(td)
+msgid "(BoolOpt) Toggle to return all active endpoints if no filter exists."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml101(th)
+#: ./doc/common/tables/heat-api.xml131(th)
+#: ./doc/common/tables/glance-paste.xml19(th)
+msgid "[paste_deploy]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml104(td)
+msgid "config_file = keystone-paste.ini"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml105(td)
+msgid ""
+"(StrOpt) Name of the paste configuration file that defines the available "
+"pipelines."
+msgstr ""
+
+#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml7(literal)
 #: ./doc/common/tables/swift-proxy-server-pipeline-main.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml7(literal)
-msgid "proxy-server.conf-sample"
-msgstr "proxy-server.conf-sample"
+#: ./doc/common/tables/swift-container-server-pipeline-main.xml7(literal)
+#: ./doc/common/tables/swift-object-server-pipeline-main.xml7(literal)
+#: ./doc/common/tables/swift-account-server-pipeline-main.xml7(literal)
+msgid "[pipeline:main]"
+msgstr "[pipeline:main]"
+
+#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml7(literal)
+#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml7(literal)
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml7(literal)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml7(literal)
+#: ./doc/common/tables/swift-object-expirer-filter-cache.xml7(literal)
+#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml7(literal)
+msgid "object-expirer.conf-sample"
+msgstr "object-expirer.conf-sample"
+
+#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml18(td)
+msgid "pipeline = catch_errors cache proxy-server"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-auditor.xml7(literal)
+msgid "[container-auditor]"
+msgstr "[container-auditor]"
+
+#: ./doc/common/tables/swift-container-server-container-auditor.xml18(td)
+msgid "log_name = container-auditor"
+msgstr "log_name = container-auditor"
+
+#: ./doc/common/tables/swift-container-server-container-auditor.xml30(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml30(td)
+msgid "interval = 1800"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-auditor.xml33(td)
+msgid "containers_per_second = 200"
+msgstr "containers_per_second = 200"
+
+#: ./doc/common/tables/swift-container-server-container-auditor.xml33(td)
+msgid ""
+"Maximum containers audited per second. Should be tuned according to "
+"individual system specs. 0 is unlimited. mounted to prevent accidentally "
+"writing to the root device process simultaneously (it will actually "
+"accept(2) N + 1). Setting this to one (1) will only handle one request at a "
+"time, without accepting another request concurrently. By increasing the "
+"number of workers to a much higher value, one can reduce the impact of slow "
+"file system operations in one request from negatively impacting other "
+"requests."
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-auditor.xml36(td)
+#: ./doc/common/tables/swift-container-server-filter-recon.xml21(td)
+#: ./doc/common/tables/swift-account-server-filter-recon.xml21(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml63(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml49(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml72(td)
+#: ./doc/common/tables/swift-object-server-object-auditor.xml42(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml57(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml42(td)
+#: ./doc/common/tables/swift-object-server-filter-recon.xml21(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml42(td)
+msgid "recon_cache_path = /var/cache/swift"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-auditor.xml36(td)
+#: ./doc/common/tables/swift-container-server-filter-recon.xml21(td)
+#: ./doc/common/tables/swift-account-server-filter-recon.xml21(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml63(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml49(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml72(td)
+#: ./doc/common/tables/swift-object-server-object-auditor.xml42(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml57(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml42(td)
+#: ./doc/common/tables/swift-object-server-filter-recon.xml21(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml42(td)
+msgid "Directory where stats for a few items will be stored"
+msgstr ""
+
+#: ./doc/common/tables/glance-rpc.xml22(td)
+msgid ""
+"allowed_rpc_exception_modules = openstack.common.exception, "
+"glance.common.exception, exceptions"
+msgstr ""
+
+#: ./doc/common/tables/glance-rpc.xml23(td)
+#: ./doc/common/tables/trove-rpc.xml23(td)
+msgid ""
+"(ListOpt) Modules of exceptions that are permitted to be recreatedupon "
+"receiving exception data from an rpc call."
+msgstr ""
+
+#: ./doc/common/tables/neutron-policy.xml22(td)
+msgid "allow_overlapping_ips = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-policy.xml23(td)
+msgid "(BoolOpt) Allow overlapping IP support in Neutron"
+msgstr ""
+
+#: ./doc/common/tables/neutron-policy.xml27(td)
+msgid "(StrOpt) The policy file to use"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml8(caption)
+msgid "Description of configuration options for spice"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml19(th)
+msgid "[spice]"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml22(td)
+msgid "agent_enabled = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml23(td)
+msgid "(BoolOpt) Enable spice guest agent support"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml26(td)
+#: ./doc/common/tables/keystone-os_inherit.xml22(td)
+#: ./doc/common/tables/nova-rdp.xml22(td)
+#: ./doc/common/tables/nova-apiv3.xml22(td)
+#: ./doc/common/tables/neutron-fwaas.xml22(td)
+#: ./doc/common/tables/keystone-cache.xml38(td)
+msgid "enabled = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml27(td)
+msgid "(BoolOpt) Enable spice related features"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml30(td)
+msgid "html5proxy_base_url = http://127.0.0.1:6082/spice_auto.html"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml31(td)
+msgid ""
+"(StrOpt) Location of spice HTML5 console proxy, in the form "
+"\"http://127.0.0.1:6082/spice_auto.html\""
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml34(td)
+msgid "keymap = en-us"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml35(td)
+msgid "(StrOpt) Keymap for spice"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml38(td)
+msgid "server_listen = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml39(td)
+msgid "(StrOpt) IP address on which instance spice server should listen"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml42(td)
+msgid "server_proxyclient_address = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml43(td)
+msgid ""
+"(StrOpt) The address to which proxy clients (like nova-spicehtml5proxy) "
+"should connect"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_heat.xml8(caption)
+msgid "Description of configuration options for clients_heat"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_heat.xml19(th)
+msgid "[clients_heat]"
+msgstr "[clients_heat]"
+
+#: ./doc/common/tables/heat-clients_heat.xml42(td)
+#: ./doc/common/tables/neutron-ml2_ncs.xml30(td)
+#: ./doc/common/tables/neutron-ml2_odl.xml34(td)
+msgid "url = None"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_heat.xml43(td)
+msgid ""
+"(StrOpt) Optional heat url in format like "
+"http://0.0.0.0:8004/v1/%(tenant_id)s."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml8(caption)
+msgid "Description of configuration options for xen"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml22(td)
+msgid "console_driver = nova.console.xvp.XVPConsoleProxy"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml23(td)
+msgid "(StrOpt) Driver to use for the console proxy"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml26(td)
+msgid "console_vmrc_error_retries = 10"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml27(td)
+msgid "(IntOpt) Number of retries for retrieving VMRC information"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml30(td)
+msgid "console_vmrc_port = 443"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml31(td)
+msgid "(IntOpt) Port for VMware VMRC connections"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml34(td)
+msgid "console_xvp_conf = /etc/xvp.conf"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml35(td)
+msgid "(StrOpt) Generated XVP conf file"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml38(td)
+msgid "console_xvp_conf_template = $pybasedir/nova/console/xvp.conf.template"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml39(td)
+msgid "(StrOpt) XVP conf template"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml42(td)
+msgid "console_xvp_log = /var/log/xvp.log"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml43(td)
+msgid "(StrOpt) XVP log file"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml46(td)
+msgid "console_xvp_multiplex_port = 5900"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml47(td)
+msgid "(IntOpt) Port for XVP to multiplex VNC connections on"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml50(td)
+msgid "console_xvp_pid = /var/run/xvp.pid"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml51(td)
+msgid "(StrOpt) XVP master process pid file"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml54(td)
+msgid "stub_compute = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml55(td)
+msgid "(BoolOpt) Stub calls to compute worker for tests"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml58(th)
+#: ./doc/common/tables/nova-volumes.xml84(th)
+#: ./doc/common/tables/nova-livemigration.xml26(th)
+#: ./doc/common/tables/nova-hypervisor.xml54(th)
+#: ./doc/common/tables/nova-libvirt.xml30(th)
+msgid "[libvirt]"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml61(td)
+msgid "xen_hvmloader_path = /usr/lib/xen/boot/hvmloader"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml62(td)
+msgid "(StrOpt) Location where the Xen hvmloader is kept"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml65(th)
+#: ./doc/common/tables/nova-volumes.xml131(th)
+#: ./doc/common/tables/nova-baremetal.xml130(th)
+msgid "[xenserver]"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml68(td)
+msgid "agent_path = usr/sbin/xe-update-networking"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml69(td)
+msgid ""
+"(StrOpt) Specifies the path in which the XenAPI guest agent should be "
+"located. If the agent is present, network configuration is not injected into"
+" the image. Used if compute_driver=xenapi.XenAPIDriver and "
+"flat_injected=True"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml72(td)
+msgid "agent_resetnetwork_timeout = 60"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml73(td)
+msgid ""
+"(IntOpt) Number of seconds to wait for agent reply to resetnetwork request"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml76(td)
+msgid "agent_timeout = 30"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml77(td)
+msgid "(IntOpt) Number of seconds to wait for agent reply"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml80(td)
+msgid "agent_version_timeout = 300"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml81(td)
+msgid "(IntOpt) Number of seconds to wait for agent to be fully operational"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml84(td)
+msgid "cache_images = all"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml85(td)
+msgid ""
+"(StrOpt) Cache glance images locally. `all` will cache all images, `some` "
+"will only cache images that have the image_property `cache_in_nova=True`, "
+"and `none` turns off caching entirely"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml88(td)
+msgid "check_host = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml89(td)
+msgid ""
+"(BoolOpt) Ensure compute service is running on host XenAPI connects to."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml92(td)
+msgid "connection_concurrent = 5"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml93(td)
+msgid ""
+"(IntOpt) Maximum number of concurrent XenAPI connections. Used only if "
+"compute_driver=xenapi.XenAPIDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml96(td)
+msgid "connection_password = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml97(td)
+msgid ""
+"(StrOpt) Password for connection to XenServer/Xen Cloud Platform. Used only "
+"if compute_driver=xenapi.XenAPIDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml100(td)
+msgid "connection_url = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml101(td)
+msgid ""
+"(StrOpt) URL for connection to XenServer/Xen Cloud Platform. A special value"
+" of unix://local can be used to connect to the local unix socket. Required "
+"if compute_driver=xenapi.XenAPIDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml104(td)
+msgid "connection_username = root"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml105(td)
+msgid ""
+"(StrOpt) Username for connection to XenServer/Xen Cloud Platform. Used only "
+"if compute_driver=xenapi.XenAPIDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml108(td)
+msgid "default_os_type = linux"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml109(td)
+msgid "(StrOpt) Default OS type"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml112(td)
+msgid "disable_agent = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml113(td)
+msgid ""
+"(BoolOpt) Disables the use of the XenAPI agent in any image regardless of "
+"what image properties are present."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml116(td)
+msgid "image_compression_level = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml117(td)
+msgid ""
+"(IntOpt) Compression level for images, e.g., 9 for gzip -9. Range is 1-9, 9 "
+"being most compressed but most CPU intensive on dom0."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml120(td)
+msgid "image_upload_handler = nova.virt.xenapi.image.glance.GlanceStore"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml121(td)
+msgid "(StrOpt) Dom0 plugin driver used to handle image uploads."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml124(td)
+msgid "introduce_vdi_retry_wait = 20"
+msgstr "introduce_vdi_retry_wait = 20"
+
+#: ./doc/common/tables/nova-xen.xml125(td)
+msgid ""
+"(IntOpt) Number of seconds to wait for an SR to settle if the VDI does not "
+"exist when first introduced"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml128(td)
+msgid "ipxe_boot_menu_url = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml129(td)
+msgid "(StrOpt) URL to the iPXE boot menu"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml132(td)
+msgid "ipxe_mkisofs_cmd = mkisofs"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml133(td)
+#: ./doc/common/tables/nova-configdrive.xml39(td)
+msgid ""
+"(StrOpt) Name and optionally path of the tool used for ISO image creation"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml136(td)
+msgid "ipxe_network_name = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml137(td)
+msgid "(StrOpt) Name of network to use for booting iPXE ISOs"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml140(td)
+msgid "iqn_prefix = iqn.2010-10.org.openstack"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml141(td)
+msgid "(StrOpt) IQN Prefix"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml144(td)
+msgid "login_timeout = 10"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml145(td)
+msgid "(IntOpt) Timeout in seconds for XenAPI login."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml148(td)
+msgid "max_kernel_ramdisk_size = 16777216"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml149(td)
+msgid "(IntOpt) Maximum size in bytes of kernel or ramdisk images"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml152(td)
+msgid "num_vbd_unplug_retries = 10"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml153(td)
+msgid "(IntOpt) Maximum number of retries to unplug VBD"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml156(td)
+msgid "ovs_integration_bridge = xapi1"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml157(td)
+#: ./doc/common/tables/nova-neutron.xml67(td)
+msgid "(StrOpt) Name of Integration Bridge used by Open vSwitch"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml160(td)
+msgid "remap_vbd_dev = False"
+msgstr "remap_vbd_dev = False"
+
+#: ./doc/common/tables/nova-xen.xml161(td)
+msgid ""
+"(BoolOpt) Used to enable the remapping of VBD dev (Works around an issue in "
+"Ubuntu Maverick)"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml164(td)
+msgid "remap_vbd_dev_prefix = sd"
+msgstr "remap_vbd_dev_prefix = sd"
+
+#: ./doc/common/tables/nova-xen.xml165(td)
+msgid ""
+"(StrOpt) Specify prefix to remap VBD dev to (ex. /dev/xvdb -&gt; /dev/sdb)"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml168(td)
+msgid "running_timeout = 60"
+msgstr "running_timeout = 60"
+
+#: ./doc/common/tables/nova-xen.xml169(td)
+msgid "(IntOpt) Number of seconds to wait for instance to go to running state"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml172(td)
+msgid "sparse_copy = True"
+msgstr "sparse_copy = True"
+
+#: ./doc/common/tables/nova-xen.xml173(td)
+msgid ""
+"(BoolOpt) Whether to use sparse_copy for copying data on a resize down "
+"(False will use standard dd). This speeds up resizes down considerably since"
+" large runs of zeros won't have to be rsynced"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml176(td)
+msgid "sr_base_path = /var/run/sr-mount"
+msgstr "sr_base_path = /var/run/sr-mount"
+
+#: ./doc/common/tables/nova-xen.xml180(td)
+msgid "sr_matching_filter = default-sr:true"
+msgstr "sr_matching_filter = default-sr:true"
+
+#: ./doc/common/tables/nova-xen.xml181(td)
+msgid ""
+"(StrOpt) Filter for finding the SR to be used to install guest instances on."
+" To use the Local Storage in default XenServer/XCP installations set this "
+"flag to other-config:i18n-key=local-storage. To select an SR with a "
+"different matching criteria, you could set it to other-"
+"config:my_favorite_sr=true. On the other hand, to fall back on the Default "
+"SR, as displayed by XenCenter, set this flag to: default-sr:true"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml184(td)
+msgid "target_host = None"
+msgstr "target_host = None"
+
+#: ./doc/common/tables/nova-xen.xml185(td)
+msgid "(StrOpt) The iSCSI Target Host"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml188(td)
+msgid "target_port = 3260"
+msgstr "target_port = 3260"
+
+#: ./doc/common/tables/nova-xen.xml189(td)
+msgid "(StrOpt) The iSCSI Target Port, default is port 3260"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml192(td)
+msgid "torrent_base_url = None"
+msgstr "torrent_base_url = None"
+
+#: ./doc/common/tables/nova-xen.xml193(td)
+msgid "(StrOpt) Base URL for torrent files."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml196(td)
+msgid "torrent_download_stall_cutoff = 600"
+msgstr "torrent_download_stall_cutoff = 600"
+
+#: ./doc/common/tables/nova-xen.xml197(td)
+msgid ""
+"(IntOpt) Number of seconds a download can remain at the same progress "
+"percentage w/o being considered a stall"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml200(td)
+msgid "torrent_images = none"
+msgstr "torrent_images = none"
+
+#: ./doc/common/tables/nova-xen.xml201(td)
+msgid ""
+"(StrOpt) Whether or not to download images via Bit Torrent (all|some|none)."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml204(td)
+msgid "torrent_listen_port_end = 6891"
+msgstr "torrent_listen_port_end = 6891"
+
+#: ./doc/common/tables/nova-xen.xml205(td)
+msgid "(IntOpt) End of port range to listen on"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml208(td)
+msgid "torrent_listen_port_start = 6881"
+msgstr "torrent_listen_port_start = 6881"
+
+#: ./doc/common/tables/nova-xen.xml209(td)
+msgid "(IntOpt) Beginning of port range to listen on"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml212(td)
+msgid "torrent_max_last_accessed = 86400"
+msgstr "torrent_max_last_accessed = 86400"
+
+#: ./doc/common/tables/nova-xen.xml213(td)
+msgid ""
+"(IntOpt) Cached torrent files not accessed within this number of seconds can"
+" be reaped"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml216(td)
+msgid "torrent_max_seeder_processes_per_host = 1"
+msgstr "torrent_max_seeder_processes_per_host = 1"
+
+#: ./doc/common/tables/nova-xen.xml217(td)
+msgid ""
+"(IntOpt) Maximum number of seeder processes to run concurrently within a "
+"given dom0. (-1 = no limit)"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml220(td)
+msgid "torrent_seed_chance = 1.0"
+msgstr "torrent_seed_chance = 1.0"
+
+#: ./doc/common/tables/nova-xen.xml221(td)
+msgid "(FloatOpt) Probability that peer will become a seeder. (1.0 = 100%)"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml224(td)
+msgid "torrent_seed_duration = 3600"
+msgstr "torrent_seed_duration = 3600"
+
+#: ./doc/common/tables/nova-xen.xml225(td)
+msgid ""
+"(IntOpt) Number of seconds after downloading an image via BitTorrent that it"
+" should be seeded for other peers."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml228(td)
+msgid "use_agent_default = False"
+msgstr "use_agent_default = False"
+
+#: ./doc/common/tables/nova-xen.xml229(td)
+msgid ""
+"(BoolOpt) Determines if the XenAPI agent should be used when the image used "
+"does not contain a hint to declare if the agent is present or not. The hint "
+"is a glance property \"xenapi_use_agent\" that has the value \"True\" or "
+"\"False\". Note that waiting for the agent when it is not present will "
+"significantly increase server boot times."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml232(td)
+msgid "use_join_force = True"
+msgstr "use_join_force = True"
+
+#: ./doc/common/tables/nova-xen.xml233(td)
+msgid "(BoolOpt) To use for hosts with different CPUs"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml236(td)
+msgid "vhd_coalesce_max_attempts = 20"
+msgstr "vhd_coalesce_max_attempts = 20"
+
+#: ./doc/common/tables/nova-xen.xml237(td)
+msgid ""
+"(IntOpt) Max number of times to poll for VHD to coalesce. Used only if "
+"compute_driver=xenapi.XenAPIDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml240(td)
+msgid "vhd_coalesce_poll_interval = 5.0"
+msgstr "vhd_coalesce_poll_interval = 5.0"
+
+#: ./doc/common/tables/nova-xen.xml241(td)
+msgid ""
+"(FloatOpt) The interval used for polling of coalescing vhds. Used only if "
+"compute_driver=xenapi.XenAPIDriver"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml8(caption)
+#: ./doc/common/tables/heat-amqp.xml8(caption)
+#: ./doc/common/tables/keystone-amqp.xml8(caption)
+#: ./doc/common/tables/glance-amqp.xml8(caption)
+#: ./doc/common/tables/ceilometer-amqp.xml8(caption)
+msgid "Description of configuration options for amqp"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml30(td)
+msgid "conductor_queue = trove-conductor"
+msgstr "conductor_queue = trove-conductor"
+
+#: ./doc/common/tables/trove-amqp.xml31(td)
+#: ./doc/common/tables/trove-common.xml71(td)
+#: ./doc/common/tables/trove-api.xml39(td)
+#: ./doc/common/tables/trove-api.xml83(td)
+#: ./doc/common/tables/trove-api.xml91(td)
+#: ./doc/common/tables/trove-api.xml95(td)
+#: ./doc/common/tables/trove-dns.xml23(td)
+#: ./doc/common/tables/trove-dns.xml27(td)
+#: ./doc/common/tables/trove-dns.xml31(td)
+#: ./doc/common/tables/trove-dns.xml35(td)
+#: ./doc/common/tables/trove-dns.xml39(td)
+#: ./doc/common/tables/trove-dns.xml43(td)
+#: ./doc/common/tables/trove-dns.xml47(td)
+#: ./doc/common/tables/trove-dns.xml51(td)
+#: ./doc/common/tables/trove-dns.xml55(td)
+#: ./doc/common/tables/trove-dns.xml59(td)
+#: ./doc/common/tables/trove-dns.xml63(td)
+#: ./doc/common/tables/trove-dns.xml67(td)
+#: ./doc/common/tables/trove-dns.xml79(td)
+#: ./doc/common/tables/trove-volume.xml23(td)
+#: ./doc/common/tables/trove-volume.xml27(td)
+#: ./doc/common/tables/trove-volume.xml31(td)
+#: ./doc/common/tables/trove-volume.xml43(td)
+#: ./doc/common/tables/trove-heat.xml27(td)
+#: ./doc/common/tables/trove-rpc.xml27(td)
+#: ./doc/common/tables/trove-backup.xml39(td)
+#: ./doc/common/tables/trove-backup.xml55(td)
+#: ./doc/common/tables/trove-guestagent.xml39(td)
+#: ./doc/common/tables/trove-guestagent.xml51(td)
+#: ./doc/common/tables/trove-compute.xml23(td)
+#: ./doc/common/tables/trove-compute.xml27(td)
+#: ./doc/common/tables/trove-logging.xml23(td)
+#: ./doc/common/tables/trove-logging.xml71(td)
+#: ./doc/common/tables/trove-debug.xml55(td)
+#: ./doc/common/tables/trove-debug.xml59(td)
+#: ./doc/common/tables/trove-debug.xml63(td)
+#: ./doc/common/tables/trove-debug.xml67(td)
+#: ./doc/common/tables/trove-debug.xml71(td)
+#: ./doc/common/tables/trove-debug.xml75(td)
+#: ./doc/common/tables/trove-swift.xml23(td)
+msgid "(StrOpt) No help text available for this option."
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml34(td)
+#: ./doc/common/tables/glance-rabbitmq.xml22(td)
+#: ./doc/common/tables/keystone-amqp.xml30(td)
+#: ./doc/common/tables/ceilometer-exchange.xml26(td)
+#: ./doc/common/tables/cinder-rpc.xml34(td)
+#: ./doc/common/tables/nova-rpc_all.xml30(td)
+#: ./doc/common/tables/nova-rpc.xml30(td)
+msgid "control_exchange = openstack"
+msgstr "control_exchange = openstack"
+
+#: ./doc/common/tables/trove-amqp.xml39(td)
+#: ./doc/common/tables/heat-amqp.xml43(td)
+#: ./doc/common/tables/neutron-testing.xml27(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml23(td)
+msgid "(BoolOpt) If passed, use a fake RabbitMQ provider"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml42(td)
+#: ./doc/common/tables/keystone-rabbit.xml30(td)
+#: ./doc/common/tables/glance-rabbitmq.xml34(td)
+#: ./doc/common/tables/heat-rabbitmq.xml22(td)
+#: ./doc/common/tables/neutron-kombu.xml22(td)
+#: ./doc/common/tables/nova-kombu.xml26(td)
+#: ./doc/common/tables/cinder-rpc.xml50(td)
+#: ./doc/common/tables/nova-rpc_all.xml38(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml26(td)
+msgid "kombu_ssl_ca_certs ="
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml43(td)
+#: ./doc/common/tables/heat-rabbitmq.xml23(td)
+#: ./doc/common/tables/neutron-kombu.xml23(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml27(td)
+msgid "(StrOpt) SSL certification authority file (valid only if SSL enabled)"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml46(td)
+#: ./doc/common/tables/keystone-rabbit.xml34(td)
+#: ./doc/common/tables/glance-rabbitmq.xml38(td)
+#: ./doc/common/tables/heat-rabbitmq.xml26(td)
+#: ./doc/common/tables/neutron-kombu.xml26(td)
+#: ./doc/common/tables/nova-kombu.xml30(td)
+#: ./doc/common/tables/cinder-rpc.xml54(td)
+#: ./doc/common/tables/nova-rpc_all.xml42(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml30(td)
+msgid "kombu_ssl_certfile ="
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml47(td)
+#: ./doc/common/tables/heat-rabbitmq.xml27(td)
+#: ./doc/common/tables/neutron-kombu.xml27(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml31(td)
+msgid "(StrOpt) SSL cert file (valid only if SSL enabled)"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml50(td)
+#: ./doc/common/tables/keystone-rabbit.xml38(td)
+#: ./doc/common/tables/glance-rabbitmq.xml42(td)
+#: ./doc/common/tables/heat-rabbitmq.xml30(td)
+#: ./doc/common/tables/neutron-kombu.xml30(td)
+#: ./doc/common/tables/nova-kombu.xml34(td)
+#: ./doc/common/tables/cinder-rpc.xml58(td)
+#: ./doc/common/tables/nova-rpc_all.xml46(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml34(td)
+msgid "kombu_ssl_keyfile ="
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml51(td)
+#: ./doc/common/tables/heat-rabbitmq.xml31(td)
+#: ./doc/common/tables/neutron-kombu.xml31(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml35(td)
+msgid "(StrOpt) SSL key file (valid only if SSL enabled)"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml54(td)
+#: ./doc/common/tables/keystone-rabbit.xml42(td)
+#: ./doc/common/tables/glance-rabbitmq.xml46(td)
+#: ./doc/common/tables/heat-rabbitmq.xml34(td)
+#: ./doc/common/tables/neutron-kombu.xml34(td)
+#: ./doc/common/tables/nova-kombu.xml38(td)
+#: ./doc/common/tables/cinder-rpc.xml62(td)
+#: ./doc/common/tables/nova-rpc_all.xml50(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml38(td)
+msgid "kombu_ssl_version ="
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml55(td)
+#: ./doc/common/tables/heat-rabbitmq.xml35(td)
+msgid ""
+"(StrOpt) SSL version to use (valid only if SSL enabled). valid values are "
+"TLSv1, SSLv23 and SSLv3. SSLv2 may be available on some distributions"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml58(td)
+#: ./doc/common/tables/nova-common.xml58(td)
+#: ./doc/common/tables/heat-amqp.xml50(td)
+#: ./doc/common/tables/keystone-amqp.xml38(td)
+#: ./doc/common/tables/glance-amqp.xml30(td)
+#: ./doc/common/tables/cinder-rpc.xml74(td)
+#: ./doc/common/tables/neutron-notifier.xml30(td)
+#: ./doc/common/tables/ceilometer-amqp.xml30(td)
+msgid "notification_driver = []"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml59(td)
+#: ./doc/common/tables/heat-amqp.xml51(td)
+#: ./doc/common/tables/neutron-notifier.xml31(td)
+#: ./doc/common/tables/ceilometer-amqp.xml31(td)
+msgid "(MultiStrOpt) Driver or drivers to handle sending notifications"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml62(td)
+msgid ""
+"notification_service_id = {'couchbase': 'fa62fe68-74d9-4779-a24e-"
+"36f19602c415', 'mongodb': 'c8c907af-7375-456f-b929-b637ff9209ee', "
+"'cassandra': '459a230d-4e97-4344-9067-2a54a310b0ed', 'redis': 'b216ffc5-1947"
+"-456c-a4cf-70f94c05f7d0', 'mysql': '2f3ff068-2bfb-4f70-9a9d-a6bb65bc084b'}"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml63(td)
+msgid "(DictOpt) Unique ID to tag notification events."
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml66(td)
+#: ./doc/common/tables/nova-common.xml62(td)
+#: ./doc/common/tables/heat-amqp.xml54(td)
+#: ./doc/common/tables/keystone-amqp.xml42(td)
+#: ./doc/common/tables/glance-amqp.xml34(td)
+#: ./doc/common/tables/cinder-rpc.xml78(td)
+#: ./doc/common/tables/neutron-notifier.xml34(td)
+#: ./doc/common/tables/ceilometer-amqp.xml34(td)
+msgid "notification_topics = notifications"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml67(td)
+#: ./doc/common/tables/neutron-notifier.xml35(td)
+msgid "(ListOpt) AMQP topic used for openstack notifications"
+msgstr ""
+
+#: ./doc/common/tables/glance-matchmaker.xml8(caption)
+msgid "Description of configuration options for matchmaker"
+msgstr ""
+
+#: ./doc/common/tables/glance-matchmaker.xml23(td)
+#: ./doc/common/tables/cinder-rpc.xml67(td)
+#: ./doc/common/tables/nova-rpc_all.xml55(td)
+#: ./doc/common/tables/nova-rpc.xml35(td)
+#: ./doc/common/tables/keystone-redis.xml27(td)
+msgid "(IntOpt) Heartbeat frequency."
+msgstr ""
+
+#: ./doc/common/tables/glance-matchmaker.xml34(td)
+#: ./doc/common/tables/cinder-rpc.xml242(td)
+#: ./doc/common/tables/nova-rpc_all.xml209(td)
+#: ./doc/common/tables/nova-rpc.xml73(td)
+#: ./doc/common/tables/keystone-redis.xml46(td)
+msgid "(StrOpt) Matchmaker ring file (JSON)."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml8(caption)
+#: ./doc/common/tables/glance-rabbitmq.xml8(caption)
+#: ./doc/common/tables/heat-rabbitmq.xml8(caption)
+#: ./doc/common/tables/trove-rabbitmq.xml8(caption)
+#: ./doc/common/tables/neutron-rabbitmq.xml8(caption)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml8(caption)
+msgid "Description of configuration options for rabbitmq"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml22(td)
+#: ./doc/common/tables/keystone-rabbit.xml46(td)
+#: ./doc/common/tables/glance-rabbitmq.xml50(td)
+#: ./doc/common/tables/heat-rabbitmq.xml38(td)
+#: ./doc/common/tables/trove-rabbitmq.xml22(td)
+#: ./doc/common/tables/cinder-rpc.xml134(td)
+#: ./doc/common/tables/nova-rpc_all.xml102(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml22(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml42(td)
+msgid "rabbit_ha_queues = False"
+msgstr "rabbit_ha_queues = False"
+
+#: ./doc/common/tables/nova-rabbitmq.xml23(td)
+#: ./doc/common/tables/keystone-rabbit.xml47(td)
+#: ./doc/common/tables/glance-rabbitmq.xml51(td)
+#: ./doc/common/tables/cinder-rpc.xml135(td)
+#: ./doc/common/tables/nova-rpc_all.xml103(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml23(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml43(td)
+msgid ""
+"(BoolOpt) Use HA queues in RabbitMQ (x-ha-policy: all). If you change this "
+"option, you must wipe the RabbitMQ database."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml26(td)
+#: ./doc/common/tables/keystone-rabbit.xml50(td)
+#: ./doc/common/tables/glance-rabbitmq.xml54(td)
+#: ./doc/common/tables/heat-rabbitmq.xml42(td)
+#: ./doc/common/tables/trove-rabbitmq.xml26(td)
+#: ./doc/common/tables/cinder-rpc.xml138(td)
+#: ./doc/common/tables/nova-rpc_all.xml106(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml26(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml46(td)
+msgid "rabbit_host = localhost"
+msgstr "rabbit_host = localhost"
+
+#: ./doc/common/tables/nova-rabbitmq.xml27(td)
+#: ./doc/common/tables/keystone-rabbit.xml51(td)
+#: ./doc/common/tables/glance-rabbitmq.xml55(td)
+#: ./doc/common/tables/cinder-rpc.xml139(td)
+#: ./doc/common/tables/nova-rpc_all.xml107(td)
+msgid "(StrOpt) The RabbitMQ broker address where a single node is used."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml30(td)
+#: ./doc/common/tables/keystone-rabbit.xml54(td)
+#: ./doc/common/tables/glance-rabbitmq.xml58(td)
+#: ./doc/common/tables/heat-rabbitmq.xml46(td)
+#: ./doc/common/tables/trove-rabbitmq.xml30(td)
+#: ./doc/common/tables/cinder-rpc.xml142(td)
+#: ./doc/common/tables/nova-rpc_all.xml110(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml30(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml50(td)
+msgid "rabbit_hosts = $rabbit_host:$rabbit_port"
+msgstr "rabbit_hosts = $rabbit_host:$rabbit_port"
+
+#: ./doc/common/tables/nova-rabbitmq.xml31(td)
+#: ./doc/common/tables/keystone-rabbit.xml55(td)
+#: ./doc/common/tables/glance-rabbitmq.xml59(td)
+#: ./doc/common/tables/cinder-rpc.xml143(td)
+#: ./doc/common/tables/nova-rpc_all.xml111(td)
+msgid "(ListOpt) RabbitMQ HA cluster host:port pairs."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml34(td)
+#: ./doc/common/tables/keystone-rabbit.xml58(td)
+#: ./doc/common/tables/glance-rabbitmq.xml62(td)
+#: ./doc/common/tables/cinder-rpc.xml146(td)
+#: ./doc/common/tables/nova-rpc_all.xml114(td)
+msgid "rabbit_login_method = AMQPLAIN"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml35(td)
+#: ./doc/common/tables/keystone-rabbit.xml59(td)
+#: ./doc/common/tables/glance-rabbitmq.xml63(td)
+#: ./doc/common/tables/cinder-rpc.xml147(td)
+#: ./doc/common/tables/nova-rpc_all.xml115(td)
+msgid "(StrOpt) the RabbitMQ login method"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml38(td)
+#: ./doc/common/tables/keystone-rabbit.xml62(td)
+#: ./doc/common/tables/glance-rabbitmq.xml66(td)
+#: ./doc/common/tables/heat-rabbitmq.xml50(td)
+#: ./doc/common/tables/trove-rabbitmq.xml34(td)
+#: ./doc/common/tables/cinder-rpc.xml150(td)
+#: ./doc/common/tables/nova-rpc_all.xml118(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml34(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml54(td)
+msgid "rabbit_max_retries = 0"
+msgstr "rabbit_max_retries = 0"
+
+#: ./doc/common/tables/nova-rabbitmq.xml39(td)
+#: ./doc/common/tables/keystone-rabbit.xml63(td)
+#: ./doc/common/tables/glance-rabbitmq.xml67(td)
+#: ./doc/common/tables/cinder-rpc.xml151(td)
+#: ./doc/common/tables/nova-rpc_all.xml119(td)
+msgid ""
+"(IntOpt) Maximum number of RabbitMQ connection retries. Default is 0 "
+"(infinite retry count)."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml42(td)
+#: ./doc/common/tables/keystone-rabbit.xml66(td)
+#: ./doc/common/tables/glance-rabbitmq.xml70(td)
+#: ./doc/common/tables/heat-rabbitmq.xml54(td)
+#: ./doc/common/tables/trove-rabbitmq.xml38(td)
+#: ./doc/common/tables/cinder-rpc.xml154(td)
+#: ./doc/common/tables/nova-rpc_all.xml122(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml38(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml58(td)
+msgid "rabbit_password = guest"
+msgstr "rabbit_password = guest"
+
+#: ./doc/common/tables/nova-rabbitmq.xml43(td)
+#: ./doc/common/tables/keystone-rabbit.xml67(td)
+#: ./doc/common/tables/glance-rabbitmq.xml71(td)
+#: ./doc/common/tables/cinder-rpc.xml155(td)
+#: ./doc/common/tables/nova-rpc_all.xml123(td)
+msgid "(StrOpt) The RabbitMQ password."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml46(td)
+#: ./doc/common/tables/keystone-rabbit.xml70(td)
+#: ./doc/common/tables/glance-rabbitmq.xml74(td)
+#: ./doc/common/tables/heat-rabbitmq.xml58(td)
+#: ./doc/common/tables/trove-rabbitmq.xml42(td)
+#: ./doc/common/tables/cinder-rpc.xml158(td)
+#: ./doc/common/tables/nova-rpc_all.xml126(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml42(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml62(td)
+msgid "rabbit_port = 5672"
+msgstr "rabbit_port = 5672"
+
+#: ./doc/common/tables/nova-rabbitmq.xml47(td)
+#: ./doc/common/tables/keystone-rabbit.xml71(td)
+#: ./doc/common/tables/glance-rabbitmq.xml75(td)
+#: ./doc/common/tables/cinder-rpc.xml159(td)
+#: ./doc/common/tables/nova-rpc_all.xml127(td)
+msgid "(IntOpt) The RabbitMQ broker port where a single node is used."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml50(td)
+#: ./doc/common/tables/keystone-rabbit.xml74(td)
+#: ./doc/common/tables/glance-rabbitmq.xml78(td)
+#: ./doc/common/tables/heat-rabbitmq.xml62(td)
+#: ./doc/common/tables/trove-rabbitmq.xml46(td)
+#: ./doc/common/tables/cinder-rpc.xml162(td)
+#: ./doc/common/tables/nova-rpc_all.xml130(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml46(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml66(td)
+msgid "rabbit_retry_backoff = 2"
+msgstr "rabbit_retry_backoff = 2"
+
+#: ./doc/common/tables/nova-rabbitmq.xml51(td)
+#: ./doc/common/tables/keystone-rabbit.xml75(td)
+#: ./doc/common/tables/glance-rabbitmq.xml79(td)
+#: ./doc/common/tables/cinder-rpc.xml163(td)
+#: ./doc/common/tables/nova-rpc_all.xml131(td)
+msgid ""
+"(IntOpt) How long to backoff for between retries when connecting to "
+"RabbitMQ."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml54(td)
+#: ./doc/common/tables/keystone-rabbit.xml78(td)
+#: ./doc/common/tables/glance-rabbitmq.xml82(td)
+#: ./doc/common/tables/heat-rabbitmq.xml66(td)
+#: ./doc/common/tables/trove-rabbitmq.xml50(td)
+#: ./doc/common/tables/cinder-rpc.xml166(td)
+#: ./doc/common/tables/nova-rpc_all.xml134(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml50(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml70(td)
+msgid "rabbit_retry_interval = 1"
+msgstr "rabbit_retry_interval = 1"
+
+#: ./doc/common/tables/nova-rabbitmq.xml55(td)
+#: ./doc/common/tables/keystone-rabbit.xml79(td)
+#: ./doc/common/tables/glance-rabbitmq.xml83(td)
+#: ./doc/common/tables/cinder-rpc.xml167(td)
+#: ./doc/common/tables/nova-rpc_all.xml135(td)
+msgid "(IntOpt) How frequently to retry connecting with RabbitMQ."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml58(td)
+#: ./doc/common/tables/keystone-rabbit.xml82(td)
+#: ./doc/common/tables/glance-rabbitmq.xml86(td)
+#: ./doc/common/tables/heat-rabbitmq.xml70(td)
+#: ./doc/common/tables/trove-rabbitmq.xml54(td)
+#: ./doc/common/tables/cinder-rpc.xml170(td)
+#: ./doc/common/tables/nova-rpc_all.xml138(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml54(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml74(td)
+msgid "rabbit_use_ssl = False"
+msgstr "rabbit_use_ssl = False"
+
+#: ./doc/common/tables/nova-rabbitmq.xml59(td)
+#: ./doc/common/tables/keystone-rabbit.xml83(td)
+#: ./doc/common/tables/glance-rabbitmq.xml87(td)
+#: ./doc/common/tables/cinder-rpc.xml171(td)
+#: ./doc/common/tables/nova-rpc_all.xml139(td)
+msgid "(BoolOpt) Connect over SSL for RabbitMQ."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml62(td)
+#: ./doc/common/tables/keystone-rabbit.xml86(td)
+#: ./doc/common/tables/glance-rabbitmq.xml90(td)
+#: ./doc/common/tables/heat-rabbitmq.xml74(td)
+#: ./doc/common/tables/trove-rabbitmq.xml58(td)
+#: ./doc/common/tables/cinder-rpc.xml174(td)
+#: ./doc/common/tables/nova-rpc_all.xml142(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml58(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml78(td)
+msgid "rabbit_userid = guest"
+msgstr "rabbit_userid = guest"
+
+#: ./doc/common/tables/nova-rabbitmq.xml63(td)
+#: ./doc/common/tables/keystone-rabbit.xml87(td)
+#: ./doc/common/tables/glance-rabbitmq.xml91(td)
+#: ./doc/common/tables/cinder-rpc.xml175(td)
+#: ./doc/common/tables/nova-rpc_all.xml143(td)
+msgid "(StrOpt) The RabbitMQ userid."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml66(td)
+#: ./doc/common/tables/keystone-rabbit.xml90(td)
+#: ./doc/common/tables/glance-rabbitmq.xml94(td)
+#: ./doc/common/tables/heat-rabbitmq.xml78(td)
+#: ./doc/common/tables/trove-rabbitmq.xml62(td)
+#: ./doc/common/tables/cinder-rpc.xml178(td)
+#: ./doc/common/tables/nova-rpc_all.xml146(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml62(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml82(td)
+msgid "rabbit_virtual_host = /"
+msgstr "rabbit_virtual_host = /"
+
+#: ./doc/common/tables/nova-rabbitmq.xml67(td)
+#: ./doc/common/tables/keystone-rabbit.xml91(td)
+#: ./doc/common/tables/glance-rabbitmq.xml95(td)
+#: ./doc/common/tables/cinder-rpc.xml179(td)
+#: ./doc/common/tables/nova-rpc_all.xml147(td)
+msgid "(StrOpt) The RabbitMQ virtual host."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_cisco.xml8(caption)
+msgid "Description of configuration options for ml2_cisco"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_cisco.xml22(td)
+msgid "managed_physical_network = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_cisco.xml23(td)
+msgid "(StrOpt) The physical network managed by the switches."
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml22(td)
+msgid "allow_instance_snapshots = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml23(td)
+msgid "(BoolOpt) Permit instance snapshot operations."
+msgstr "(BoolOpt) Autorise les opérations de snapshots des instances"
+
+#: ./doc/common/tables/nova-policy.xml26(td)
+msgid "allow_migrate_to_same_host = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml27(td)
+msgid ""
+"(BoolOpt) Allow migrate machine to the same host. Useful when testing in "
+"single-host environments."
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml30(td)
+msgid "allow_resize_to_same_host = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml31(td)
+msgid ""
+"(BoolOpt) Allow destination machine to match source for resize. Useful when "
+"testing in single-host environments."
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml34(td)
+#: ./doc/common/tables/cinder-quota.xml22(td)
+msgid "max_age = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml35(td)
+msgid "(IntOpt) Number of seconds between subsequent usage refreshes"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml38(td)
+msgid "max_local_block_devices = 3"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml39(td)
+msgid ""
+"(IntOpt) Maximum number of devices that will result in a local image being "
+"created on the hypervisor node. Setting this to 0 means nova will allow only"
+" boot from volume. A negative number means unlimited."
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml42(td)
+msgid "osapi_compute_unique_server_name_scope ="
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml43(td)
+msgid ""
+"(StrOpt) When set, compute API will consider duplicate hostnames invalid "
+"within the specified scope, regardless of case. Should be empty, \"project\""
+" or \"global\"."
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml46(td)
+#: ./doc/common/tables/cinder-api.xml50(td)
+msgid "osapi_max_limit = 1000"
+msgstr "osapi_max_limit = 1000"
+
+#: ./doc/common/tables/nova-policy.xml47(td)
+msgid ""
+"(IntOpt) The maximum number of items returned in a single response from a "
+"collection resource"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml50(td)
+#: ./doc/common/tables/cinder-api.xml54(td)
+msgid "osapi_max_request_body_size = 114688"
+msgstr "osapi_max_request_body_size = 114688"
+
+#: ./doc/common/tables/nova-policy.xml51(td)
+msgid "(IntOpt) The maximum body size per each osapi request(bytes)"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml54(td)
+msgid "password_length = 12"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml55(td)
+msgid "(IntOpt) Length of generated instance admin passwords"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml59(td)
+#: ./doc/common/tables/cinder-common.xml139(td)
+msgid "(StrOpt) Rule checked when requested rule is not found"
+msgstr "(StrOpt)  Règle vérifiée lorsque la règle recherchée n'existe pas"
+
+#: ./doc/common/tables/nova-policy.xml63(td)
+#: ./doc/common/tables/cinder-common.xml143(td)
+msgid "(StrOpt) JSON file representing policy"
+msgstr "(StrOpt)  Fichier JSON correspondant aux polices"
+
+#: ./doc/common/tables/nova-policy.xml66(td)
+#: ./doc/common/tables/cinder-quota.xml42(td)
+msgid "reservation_expire = 86400"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml67(td)
+msgid "(IntOpt) Number of seconds until a reservation expires"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml70(td)
+msgid "resize_fs_using_block_device = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml71(td)
+msgid ""
+"(BoolOpt) Attempt to resize the filesystem by accessing the image over a "
+"block device. This is done by the host and may not be necessary if the image"
+" contains a recent version of cloud-init. Possible mechanisms require the "
+"nbd driver (for qcow and raw), or loop (for raw)."
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml74(td)
+#: ./doc/common/tables/cinder-common.xml202(td)
+msgid "until_refresh = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml75(td)
+msgid "(IntOpt) Count of reservations until usage is refreshed"
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml8(caption)
+msgid "Description of configuration options for identity"
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml19(th)
+msgid "[identity]"
+msgstr "[identity]"
+
+#: ./doc/common/tables/keystone-identity.xml22(td)
+msgid "default_domain_id = default"
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml23(td)
+msgid ""
+"(StrOpt) This references the domain to use for all Identity API v2 requests "
+"(which are not aware of domains). A domain with this ID will be created for "
+"you by keystone-manage db_sync in migration 008. The domain referenced by "
+"this ID cannot be deleted on the v3 API, to prevent accidentally breaking "
+"the v2 API. There is nothing special about this domain, other than the fact "
+"that it must exist to order to maintain support for your v2 clients."
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml26(td)
+msgid "domain_config_dir = /etc/keystone/domains"
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml27(td)
+msgid ""
+"(StrOpt) Path for Keystone to locate the domain specificidentity "
+"configuration files if domain_specific_drivers_enabled is set to true."
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml30(td)
+msgid "domain_specific_drivers_enabled = False"
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml31(td)
+msgid ""
+"(BoolOpt) A subset (or all) of domains can have their own identity driver, "
+"each with their own partial configuration file in a domain configuration "
+"directory. Only values specific to the domain need to be placed in the "
+"domain specific configuration file. This feature is disabled by default; set"
+" to True to enable."
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml34(td)
+msgid "driver = keystone.identity.backends.sql.Identity"
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml35(td)
+msgid "(StrOpt) Keystone Identity backend driver."
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml39(td)
+msgid ""
+"(IntOpt) Maximum number of entities that will be returned in an identity "
+"collection."
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml42(td)
+msgid "max_password_length = 4096"
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml43(td)
+msgid ""
+"(IntOpt) Maximum supported length for user passwords; decrease to improve "
+"performance."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-inspector.xml8(caption)
+msgid "Description of configuration options for inspector"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-inspector.xml22(td)
+msgid "hypervisor_inspector = libvirt"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-inspector.xml23(td)
+msgid "(StrOpt) Inspector to use for inspecting the hypervisor layer."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-inspector.xml26(td)
+msgid "libvirt_type = kvm"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-inspector.xml27(td)
+msgid ""
+"(StrOpt) Libvirt domain type (valid options are: kvm, lxc, qemu, uml, xen)."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-inspector.xml30(td)
+msgid "libvirt_uri ="
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-inspector.xml31(td)
+msgid ""
+"(StrOpt) Override the default libvirt URI (which is dependent on "
+"libvirt_type)."
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml22(td)
+msgid ""
+"scheduler_default_filters = AvailabilityZoneFilter, CapacityFilter, "
+"CapabilitiesFilter"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml23(td)
+#: ./doc/common/tables/nova-scheduling.xml79(td)
+msgid ""
+"(ListOpt) Which filter class names to use for filtering hosts when not "
+"specified in the request."
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml26(td)
+msgid "scheduler_default_weighers = CapacityWeigher"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml27(td)
+msgid "(ListOpt) Which weigher class names to use for weighing hosts."
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml30(td)
+msgid "scheduler_driver = cinder.scheduler.filter_scheduler.FilterScheduler"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml31(td)
+msgid "(StrOpt) Default scheduler driver to use"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml34(td)
+msgid "scheduler_host_manager = cinder.scheduler.host_manager.HostManager"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml35(td)
+#: ./doc/common/tables/nova-scheduling.xml91(td)
+msgid "(StrOpt) The scheduler host manager class to use"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml38(td)
+#: ./doc/common/tables/nova-scheduling.xml98(td)
+msgid "scheduler_json_config_location ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml39(td)
+#: ./doc/common/tables/nova-scheduling.xml99(td)
+msgid "(StrOpt) Absolute path to scheduler configuration JSON file."
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml42(td)
+msgid "scheduler_manager = cinder.scheduler.manager.SchedulerManager"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml43(td)
+msgid "(StrOpt) full class name for the Manager for scheduler"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml46(td)
+#: ./doc/common/tables/nova-scheduling.xml106(td)
+msgid "scheduler_max_attempts = 3"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml47(td)
+msgid "(IntOpt) Maximum number of attempts to schedule an volume"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml50(td)
+msgid "scheduler_topic = cinder-scheduler"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml51(td)
+msgid "(StrOpt) the topic scheduler nodes listen on"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_cassandra.xml8(caption)
+msgid "Description of configuration options for db_cassandra"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_cassandra.xml19(th)
+msgid "[cassandra]"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_cassandra.xml22(td)
+#: ./doc/common/tables/trove-db_couchbase.xml22(td)
+#: ./doc/common/tables/trove-db_mongodb.xml22(td)
+#: ./doc/common/tables/trove-db_redis.xml22(td)
+msgid "backup_strategy = None"
+msgstr "backup_strategy = None"
+
+#: ./doc/common/tables/trove-db_cassandra.xml26(td)
+msgid "mount_point = /var/lib/cassandra"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_cassandra.xml30(td)
+msgid "tcp_ports = 7000, 7001, 9042, 9160"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_cassandra.xml38(td)
+msgid "usage_timeout = 600"
+msgstr ""
+
+#: ./doc/common/tables/neutron-logging.xml26(td)
+#: ./doc/common/tables/trove-common.xml34(td)
+#: ./doc/common/tables/heat-logging.xml22(td)
+msgid ""
+"default_log_levels = amqp=WARN, amqplib=WARN, boto=WARN, qpid=WARN, "
+"sqlalchemy=WARN, suds=INFO, iso8601=WARN"
+msgstr "default_log_levels = amqp=WARN, amqplib=WARN, boto=WARN, qpid=WARN, sqlalchemy=WARN, suds=INFO, iso8601=WARN"
+
+#: ./doc/common/tables/neutron-logging.xml27(td)
+#: ./doc/common/tables/trove-common.xml35(td)
+#: ./doc/common/tables/heat-logging.xml23(td)
+#: ./doc/common/tables/nova-logging.xml27(td)
+msgid "(ListOpt) list of logger=LEVEL pairs"
+msgstr "(ListOpt) liste de loggers=paires LEVEL"
+
+#: ./doc/common/tables/neutron-logging.xml31(td)
+#: ./doc/common/tables/heat-debug.xml35(td)
+#: ./doc/common/tables/nova-logging.xml31(td)
+#: ./doc/common/tables/trove-debug.xml39(td)
+msgid "(BoolOpt) make deprecations fatal"
+msgstr ""
+
+#: ./doc/common/tables/neutron-logging.xml63(td)
+#: ./doc/common/tables/heat-logging.xml55(td)
+#: ./doc/common/tables/nova-logging.xml67(td)
+#: ./doc/common/tables/trove-logging.xml55(td)
+msgid "(StrOpt) format string to use for log messages with context"
+msgstr "(StrOpt)  chaîne de format à utiliser pour les messages de log avec contexte"
+
+#: ./doc/common/tables/neutron-logging.xml67(td)
+#: ./doc/common/tables/heat-logging.xml59(td)
+#: ./doc/common/tables/nova-logging.xml71(td)
+#: ./doc/common/tables/trove-logging.xml59(td)
+msgid "(StrOpt) data to append to log format when level is DEBUG"
+msgstr "(StrOpt)  données à ajouter au format de journal lorsque le niveau est DEBUG"
+
+#: ./doc/common/tables/neutron-logging.xml71(td)
+#: ./doc/common/tables/heat-logging.xml63(td)
+#: ./doc/common/tables/nova-logging.xml75(td)
+#: ./doc/common/tables/trove-logging.xml63(td)
+msgid "(StrOpt) format string to use for log messages without context"
+msgstr "(StrOpt)  chaîne de format à utiliser pour les messages de log sans contexte"
+
+#: ./doc/common/tables/neutron-logging.xml75(td)
+#: ./doc/common/tables/heat-logging.xml67(td)
+#: ./doc/common/tables/nova-logging.xml79(td)
+#: ./doc/common/tables/trove-logging.xml67(td)
+msgid "(StrOpt) prefix each line of exception output with this format"
+msgstr "(StrOpt)  préfixer chaque ligne de sortie d'exception avec ce format"
+
+#: ./doc/common/tables/neutron-logging.xml79(td)
+#: ./doc/common/tables/heat-notification.xml27(td)
+#: ./doc/common/tables/nova-logging.xml83(td)
+#: ./doc/common/tables/trove-logging.xml75(td)
+msgid "(BoolOpt) publish error events"
+msgstr "(BoolOpt) publier les événements de type erreur"
+
+#: ./doc/common/tables/neutron-logging.xml83(td)
+#: ./doc/common/tables/heat-logging.xml71(td)
+#: ./doc/common/tables/nova-logging.xml87(td)
+#: ./doc/common/tables/trove-logging.xml79(td)
+msgid "(StrOpt) syslog facility to receive log lines"
+msgstr "(StrOpt)  syslog destiné à recevoir les lignes de log"
+
+#: ./doc/common/tables/neutron-logging.xml86(td)
+#: ./doc/common/tables/neutron-nec.xml58(td)
+msgid "use_ssl = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-logging.xml87(td)
+msgid "(BoolOpt) Enable SSL on the API server"
+msgstr ""
+
+#: ./doc/common/tables/neutron-logging.xml95(td)
+#: ./doc/common/tables/heat-logging.xml79(td)
+#: ./doc/common/tables/trove-logging.xml87(td)
+msgid "(BoolOpt) Use syslog for logging."
+msgstr ""
+
+#: ./doc/common/tables/nova-availabilityzones.xml8(caption)
+msgid "Description of configuration options for availabilityzones"
+msgstr ""
+
+#: ./doc/common/tables/nova-availabilityzones.xml22(td)
+msgid "default_availability_zone = nova"
+msgstr ""
+
+#: ./doc/common/tables/nova-availabilityzones.xml23(td)
+msgid "(StrOpt) Default compute node availability_zone"
+msgstr ""
+
+#: ./doc/common/tables/nova-availabilityzones.xml26(td)
+msgid "default_schedule_zone = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-availabilityzones.xml27(td)
+msgid "(StrOpt) Availability zone to use when user doesn't specify one"
+msgstr ""
+
+#: ./doc/common/tables/nova-availabilityzones.xml30(td)
+msgid "internal_service_availability_zone = internal"
+msgstr ""
+
+#: ./doc/common/tables/nova-availabilityzones.xml31(td)
+msgid "(StrOpt) The availability_zone to show internal services under"
+msgstr ""
+
+#: ./doc/common/tables/keystone-catalog.xml8(caption)
+msgid "Description of configuration options for catalog"
+msgstr ""
+
+#: ./doc/common/tables/keystone-catalog.xml19(th)
+msgid "[catalog]"
+msgstr "[catalog]"
+
+#: ./doc/common/tables/keystone-catalog.xml22(td)
+msgid "driver = keystone.catalog.backends.sql.Catalog"
+msgstr ""
+
+#: ./doc/common/tables/keystone-catalog.xml23(td)
+msgid "(StrOpt) Keystone catalog backend driver."
+msgstr ""
+
+#: ./doc/common/tables/keystone-catalog.xml27(td)
+msgid ""
+"(IntOpt) Maximum number of entities that will be returned in a catalog "
+"collection."
+msgstr ""
+
+#: ./doc/common/tables/keystone-catalog.xml30(td)
+msgid "template_file = default_catalog.templates"
+msgstr ""
+
+#: ./doc/common/tables/keystone-catalog.xml31(td)
+msgid ""
+"(StrOpt) Catalog template file name for use with the template catalog "
+"backend."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml8(caption)
+msgid "Description of configuration options for netapp_eseries_iscsi"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml22(td)
+msgid "netapp_controller_ips = None"
+msgstr "netapp_controller_ips = None"
+
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml23(td)
+msgid ""
+"(StrOpt) This option is only utilized when the storage family is configured "
+"to eseries. This option is used to restrict provisioning to the specified "
+"controllers. Specify the value of this option to be a comma separated list "
+"of controller hostnames or IP addresses to be used for provisioning."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml34(td)
+msgid "netapp_sa_password = None"
+msgstr "netapp_sa_password = None"
+
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml35(td)
+msgid "(StrOpt) Password for the NetApp E-Series storage array."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml50(td)
+msgid "netapp_storage_pools = None"
+msgstr "netapp_storage_pools = None"
+
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml51(td)
+msgid ""
+"(StrOpt) This option is used to restrict provisioning to the specified "
+"storage pools. Only dynamic disk pools are currently supported. Specify the "
+"value of this option to be a comma separated list of disk pool names to be "
+"used for provisioning."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml58(td)
+msgid "netapp_webservice_path = /devmgr/v2"
+msgstr "netapp_webservice_path = /devmgr/v2"
+
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml59(td)
+msgid ""
+"(StrOpt) This option is used to specify the path to the E-Series proxy "
+"application on a proxy server. The value is combined with the value of the "
+"netapp_transport_type, netapp_server_hostname, and netapp_server_port "
+"options to create the URL used by the driver to connect to the proxy "
+"application."
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml8(caption)
+#: ./doc/common/tables/nova-rootwrap.xml8(caption)
+#: ./doc/common/tables/cinder-rootwrap.xml8(caption)
+msgid "Description of configuration options for rootwrap"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml22(td)
+msgid ""
+"filters_path = "
+"/etc/neutron/rootwrap.d,/usr/share/neutron/rootwrap,/etc/quantum/rootwrap.d,/usr/share/quantum/rootwrap"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml23(td)
+#: ./doc/common/tables/nova-rootwrap.xml23(td)
+#: ./doc/common/tables/cinder-rootwrap.xml23(td)
+msgid ""
+"List of directories to load filter definitions from (separated by ','). "
+"These directories MUST all be only writeable by root !"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml26(td)
+#: ./doc/common/tables/nova-rootwrap.xml26(td)
+#: ./doc/common/tables/cinder-rootwrap.xml26(td)
+msgid "exec_dirs = /sbin,/usr/sbin,/bin,/usr/bin"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml27(td)
+#: ./doc/common/tables/nova-rootwrap.xml27(td)
+#: ./doc/common/tables/cinder-rootwrap.xml27(td)
+msgid ""
+"List of directories to search executables in, in case filters do not "
+"explicitely specify a full path (separated by ',') If not specified, "
+"defaults to system PATH environment variable. These directories MUST all be "
+"only writeable by root !"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml31(td)
+#: ./doc/common/tables/nova-rootwrap.xml31(td)
+#: ./doc/common/tables/cinder-rootwrap.xml31(td)
+msgid "Enable logging to syslog Default value is False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml34(td)
+#: ./doc/common/tables/nova-rootwrap.xml34(td)
+#: ./doc/common/tables/cinder-rootwrap.xml34(td)
+msgid "syslog_log_facility = syslog"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml35(td)
+#: ./doc/common/tables/cinder-rootwrap.xml35(td)
+msgid ""
+"Which syslog facility to use. Valid values include auth, authpriv, syslog, "
+"local0, local1... Default value is 'syslog'"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml38(td)
+#: ./doc/common/tables/nova-rootwrap.xml38(td)
+#: ./doc/common/tables/cinder-rootwrap.xml38(td)
+msgid "syslog_log_level = ERROR"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml39(td)
+#: ./doc/common/tables/nova-rootwrap.xml39(td)
+#: ./doc/common/tables/cinder-rootwrap.xml39(td)
+msgid ""
+"Which messages to log. INFO means log all usage ERROR means only log "
+"unsuccessful attempts"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml42(th)
+msgid "[xenapi]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml45(td)
+msgid "xenapi_connection_url = &lt;None&gt;"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml46(td)
+msgid ""
+"XenAPI configuration is only required by the L2 agent if it is to target a "
+"XenServer/XCP compute host's dom0."
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml53(td)
+msgid "xenapi_connection_password = &lt;None&gt;"
+msgstr ""
+
+#: ./doc/common/tables/cinder-auth.xml22(td)
+#: ./doc/common/tables/glance-registry.xml38(td)
+#: ./doc/common/tables/nova-authentication.xml22(td)
+msgid "auth_strategy = noauth"
+msgstr ""
+
+#: ./doc/common/tables/cinder-auth.xml23(td)
+msgid ""
+"(StrOpt) The strategy to use for auth. Supports noauth, keystone, and "
+"deprecated."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml7(literal)
+msgid "[swift-constraints]"
+msgstr "[swift-constraints]"
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml7(literal)
+#: ./doc/common/tables/swift-swift-swift-hash.xml7(literal)
+msgid "swift.conf-sample"
+msgstr "swift.conf-sample"
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml18(td)
+msgid "max_file_size = 5368709122"
+msgstr "max_file_size = 5368709122"
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml18(td)
+msgid ""
+"The largest normal object that can be saved in the cluster. This is also the"
+" limit on the size of each segment of a large object when using the large "
+"object manifest support. This value is set in bytes. Setting it to lower "
+"than 1MiB will cause some tests to fail. It is STRONGLY recommended to leave"
+" this value at the default (5 * 2**30 + 2)."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml29(td)
+msgid "max_meta_name_length = 128"
+msgstr "max_meta_name_length = 128"
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml29(td)
+msgid ""
+"The maximum number of bytes in the utf8 encoding of the name portion of a "
+"metadata header."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml34(td)
+msgid "max_meta_value_length = 256"
+msgstr "max_meta_value_length = 256"
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml34(td)
+msgid "The max number of bytes in the utf8 encoding of a metadata value."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml38(td)
+msgid "max_meta_count = 90"
+msgstr "max_meta_count = 90"
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml38(td)
+msgid ""
+"The maximum number of metadata keys that can be stored on a single account, "
+"container, or object."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml43(td)
+msgid "max_meta_overall_size = 4096"
+msgstr "max_meta_overall_size = 4096"
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml43(td)
+msgid ""
+"The maximum number of bytes in the utf8 encoding of the metadata (keys + "
+"values)."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml48(td)
+msgid "max_header_size = 8192"
+msgstr "max_header_size = 8192"
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml48(td)
+msgid "The maximum number of bytes in the utf8 encoding of each header."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml52(td)
+msgid "max_object_name_length = 1024"
+msgstr "max_object_name_length = 1024"
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml52(td)
+msgid "The maximum number of bytes in the utf8 encoding of an object name."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml56(td)
+msgid "container_listing_limit = 10000"
+msgstr "container_listing_limit = 10000"
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml56(td)
+msgid ""
+"The default (and maximum) number of items returned for a container listing "
+"request."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml61(td)
+msgid "account_listing_limit = 10000"
+msgstr "account_listing_limit = 10000"
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml61(td)
+msgid ""
+"The default (and maximum) number of items returned for an account listing "
+"request."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml65(td)
+msgid "max_account_name_length = 256"
+msgstr "max_account_name_length = 256"
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml65(td)
+msgid "The maximum number of bytes in the utf8 encoding of an account name."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml69(td)
+msgid "max_container_name_length = 256"
+msgstr "max_container_name_length = 256"
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml69(td)
+msgid "The maximum number of bytes in the utf8 encoding of a container name."
+msgstr ""
+
+#: ./doc/common/tables/heat-qpid.xml54(td)
+#: ./doc/common/tables/nova-qpid.xml54(td)
+#: ./doc/common/tables/glance-qpid.xml54(td)
+#: ./doc/common/tables/cinder-rpc.xml126(td)
+#: ./doc/common/tables/nova-rpc_all.xml94(td)
+#: ./doc/common/tables/neutron-qpid.xml54(td)
+#: ./doc/common/tables/keystone-qpid.xml54(td)
+#: ./doc/common/tables/ceilometer-qpid.xml54(td)
+msgid "qpid_topology_version = 1"
+msgstr ""
+
+#: ./doc/common/tables/heat-qpid.xml55(td)
+#: ./doc/common/tables/nova-qpid.xml55(td)
+#: ./doc/common/tables/glance-qpid.xml55(td)
+#: ./doc/common/tables/cinder-rpc.xml127(td)
+#: ./doc/common/tables/nova-rpc_all.xml95(td)
+#: ./doc/common/tables/neutron-qpid.xml55(td)
+#: ./doc/common/tables/keystone-qpid.xml55(td)
+#: ./doc/common/tables/ceilometer-qpid.xml55(td)
+msgid ""
+"(IntOpt) The qpid topology version to use. Version 1 is what was originally "
+"used by impl_qpid. Version 2 includes some backwards-incompatible changes "
+"that allow broker federation to work. Users should update to version 2 when "
+"they are able to take everything down, as it requires a clean break."
+msgstr ""
+
+#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml7(literal)
+msgid "[filter:catch_errors]"
+msgstr "[filter:catch_errors]"
+
+#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml18(td)
+msgid "use = egg:swift#catch_errors"
+msgstr "use = egg:swift#catch_errors"
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml7(literal)
+msgid "[filter:slo]"
+msgstr "[filter:slo]"
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml18(td)
+msgid "use = egg:swift#slo"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml21(td)
+msgid "max_manifest_segments = 1000"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml24(td)
+msgid "max_manifest_size = 2097152"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml27(td)
+msgid "min_segment_size = 1048576"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml21(td)
+msgid "rate_limit_after_segment = 10"
+msgstr "rate_limit_after_segment = 10"
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml21(td)
+msgid ""
+"Rate limit the download of large object segments after this segment is "
+"downloaded."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml33(td)
+msgid "rate_limit_segments_per_sec = 0"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml24(td)
+msgid ""
+"Rate limit large object downloads at this rate. contact for a normal "
+"request. You can use '* replicas' at the end to have it use the number given"
+" times the number of replicas for the ring being used for the request. "
+"paste.deploy to use for auth. To use tempauth set to: `egg:swift#tempauth` "
+"each request"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml36(td)
+#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml27(td)
+msgid "max_get_time = 86400"
+msgstr ""
+
+#: ./doc/common/tables/nova-zookeeper.xml8(caption)
+msgid "Description of configuration options for zookeeper"
+msgstr "Description des options de configuration pour zookeeper"
+
+#: ./doc/common/tables/nova-zookeeper.xml19(th)
+msgid "[zookeeper]"
+msgstr ""
+
+#: ./doc/common/tables/nova-zookeeper.xml22(td)
+msgid "address = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-zookeeper.xml23(td)
+msgid ""
+"(StrOpt) The ZooKeeper addresses for servicegroup service in the format of "
+"host1:port,host2:port,host3:port"
+msgstr ""
+
+#: ./doc/common/tables/nova-zookeeper.xml26(td)
+msgid "recv_timeout = 4000"
+msgstr "recv_timeout = 4000"
+
+#: ./doc/common/tables/nova-zookeeper.xml27(td)
+msgid "(IntOpt) The recv_timeout parameter for the zk session"
+msgstr ""
+
+#: ./doc/common/tables/nova-zookeeper.xml30(td)
+msgid "sg_prefix = /servicegroups"
+msgstr "sg_prefix = /servicegroups"
+
+#: ./doc/common/tables/nova-zookeeper.xml31(td)
+msgid "(StrOpt) The prefix used in ZooKeeper to store ephemeral nodes"
+msgstr ""
+
+#: ./doc/common/tables/nova-zookeeper.xml34(td)
+msgid "sg_retry_interval = 5"
+msgstr "sg_retry_interval = 5"
+
+#: ./doc/common/tables/nova-zookeeper.xml35(td)
+msgid "(IntOpt) Number of seconds to wait until retrying to join the session"
+msgstr ""
+
+#: ./doc/common/tables/nova-keymgr.xml8(caption)
+#: ./doc/common/tables/cinder-keymgr.xml8(caption)
+msgid "Description of configuration options for keymgr"
+msgstr ""
+
+#: ./doc/common/tables/nova-keymgr.xml19(th)
+#: ./doc/common/tables/cinder-keymgr.xml19(th)
+msgid "[keymgr]"
+msgstr ""
+
+#: ./doc/common/tables/nova-keymgr.xml22(td)
+msgid "api_class = nova.keymgr.conf_key_mgr.ConfKeyManager"
+msgstr "api_class = nova.keymgr.conf_key_mgr.ConfKeyManager"
+
+#: ./doc/common/tables/nova-keymgr.xml23(td)
+#: ./doc/common/tables/cinder-keymgr.xml23(td)
+msgid "(StrOpt) The full class name of the key manager API class"
+msgstr ""
+
+#: ./doc/common/tables/nova-keymgr.xml26(td)
+#: ./doc/common/tables/cinder-keymgr.xml26(td)
+msgid "fixed_key = None"
+msgstr "fixed_key = None"
+
+#: ./doc/common/tables/nova-keymgr.xml27(td)
+#: ./doc/common/tables/cinder-keymgr.xml27(td)
+msgid "(StrOpt) Fixed key returned by key manager, specified in hex"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml7(literal)
+#: ./doc/common/tables/swift-object-expirer-filter-cache.xml7(literal)
+msgid "[filter:cache]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml18(td)
+#: ./doc/common/tables/swift-object-expirer-filter-cache.xml18(td)
+msgid "use = egg:swift#memcache"
+msgstr ""
 
 #: ./doc/common/tables/swift-proxy-server-filter-cache.xml21(td)
 msgid "set log_name = cache"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml21(td)
-#: ./doc/common/tables/swift-account-server-app-account-server.xml21(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml21(td)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml21(td)
-msgid "Label to use when logging"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml24(td)
-#: ./doc/common/tables/swift-account-server-app-account-server.xml24(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml24(td)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml24(td)
-msgid "set log_facility = LOG_LOCAL0"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml24(td)
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml64(td)
-#: ./doc/common/tables/swift-container-server-container-updater.xml21(td)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml24(td)
-#: ./doc/common/tables/swift-container-server-container-sync.xml21(td)
-#: ./doc/common/tables/swift-object-server-object-auditor.xml21(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml27(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml24(td)
-#: ./doc/common/tables/swift-account-server-app-account-server.xml24(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml24(td)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml21(td)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml33(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml67(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml61(td)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml24(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml21(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml21(td)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml73(td)
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml24(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml24(td)
-msgid "Syslog log facility"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml27(td)
-#: ./doc/common/tables/swift-account-server-app-account-server.xml27(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml27(td)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml27(td)
-msgid "set log_level = INFO"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml27(td)
-#: ./doc/common/tables/swift-account-server-app-account-server.xml27(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml27(td)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml27(td)
-msgid "Log level"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml30(td)
-msgid "set log_headers = false"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml30(td)
-msgid "If True, log headers in each request"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml30(td)
-#: ./doc/common/tables/swift-account-server-app-account-server.xml33(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml33(td)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml33(td)
-msgid "set log_address = /dev/log"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml33(td)
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml70(td)
-#: ./doc/common/tables/swift-container-server-container-updater.xml27(td)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml33(td)
-#: ./doc/common/tables/swift-container-server-container-sync.xml27(td)
-#: ./doc/common/tables/swift-object-server-object-auditor.xml27(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml33(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml30(td)
-#: ./doc/common/tables/swift-account-server-app-account-server.xml33(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml33(td)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml27(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml73(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml67(td)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml33(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml27(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml27(td)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml82(td)
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml33(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml33(td)
-msgid "Location where syslog sends the logs to"
-msgstr ""
-
 #: ./doc/common/tables/swift-proxy-server-filter-cache.xml36(td)
 #: ./doc/common/tables/swift-memcache-memcache.xml18(td)
 msgid "memcache_servers = 127.0.0.1:11211"
@@ -26433,135 +32658,6 @@ msgstr ""
 msgid "memcache_serialization_support = 2"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml39(td)
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml58(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml57(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml60(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml63(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml66(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml69(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml72(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml75(td)
-#: ./doc/common/tables/swift-object-server-object-auditor.xml45(td)
-#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml57(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml81(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml87(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml90(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml93(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml96(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml102(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml105(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml108(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml111(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml114(td)
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml27(td)
-#: ./doc/common/tables/swift-container-server-pipeline-main.xml18(td)
-#: ./doc/common/tables/swift-rsyncd-object.xml18(td)
-#: ./doc/common/tables/swift-rsyncd-object.xml21(td)
-#: ./doc/common/tables/swift-rsyncd-object.xml24(td)
-#: ./doc/common/tables/swift-rsyncd-object.xml27(td)
-#: ./doc/common/tables/swift-object-server-pipeline-main.xml18(td)
-#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml36(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml45(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml48(td)
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml36(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml36(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml39(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml42(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml45(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml48(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml51(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml54(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml57(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml60(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml72(td)
-#: ./doc/common/tables/swift-rsyncd-account.xml18(td)
-#: ./doc/common/tables/swift-rsyncd-account.xml21(td)
-#: ./doc/common/tables/swift-rsyncd-account.xml24(td)
-#: ./doc/common/tables/swift-rsyncd-account.xml27(td)
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml18(td)
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml21(td)
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml24(td)
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml27(td)
-#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml21(td)
-#: ./doc/common/tables/swift-object-server-filter-recon.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml21(td)
-#: ./doc/common/tables/swift-memcache-memcache.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml45(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml51(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml54(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml57(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml60(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml45(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml51(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml75(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml24(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml33(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml42(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml48(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml51(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml57(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml60(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml63(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml66(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml69(td)
-#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml36(td)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml39(td)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml42(td)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml45(td)
-#: ./doc/common/tables/neutron-rootwrap.xml50(td)
-#: ./doc/common/tables/neutron-rootwrap.xml54(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml42(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml64(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml67(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml79(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml85(td)
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml39(td)
-#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml18(td)
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml18(td)
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml21(td)
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml24(td)
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml27(td)
-#: ./doc/common/tables/swift-rsyncd-container.xml18(td)
-#: ./doc/common/tables/swift-rsyncd-container.xml21(td)
-#: ./doc/common/tables/swift-rsyncd-container.xml24(td)
-#: ./doc/common/tables/swift-rsyncd-container.xml27(td)
-#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml21(td)
-#: ./doc/common/tables/swift-account-server-pipeline-main.xml18(td)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml24(td)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml27(td)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml18(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml45(td)
-msgid "No help text available for this option."
-msgstr ""
-
 #: ./doc/common/tables/swift-proxy-server-filter-cache.xml42(td)
 #: ./doc/common/tables/swift-memcache-memcache.xml24(td)
 msgid "memcache_max_connections = 2"
@@ -26572,1903 +32668,2745 @@ msgstr ""
 msgid "Max number of connections to each memcached server per worker services"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml8(caption)
-msgid "Description of configuration options for rpc_all"
+#: ./doc/common/tables/nova-ldap.xml8(caption)
+#: ./doc/common/tables/keystone-ldap.xml8(caption)
+msgid "Description of configuration options for ldap"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml22(td)
-#: ./doc/common/tables/cinder-rpc.xml26(td)
-#: ./doc/common/tables/keystone-amqp.xml22(td)
-#: ./doc/common/tables/neutron-rpc.xml22(td)
-#: ./doc/common/tables/glance-amqp.xml22(td)
-#: ./doc/common/tables/heat-amqp.xml22(td)
-#: ./doc/common/tables/ceilometer-amqp.xml22(td)
-#: ./doc/common/tables/nova-rpc.xml22(td)
-#: ./doc/common/tables/trove-amqp.xml22(td)
-msgid "amqp_auto_delete = False"
-msgstr "amqp_auto_delete = False"
-
-#: ./doc/common/tables/nova-rpc_all.xml23(td)
-#: ./doc/common/tables/cinder-rpc.xml27(td)
-#: ./doc/common/tables/keystone-amqp.xml23(td)
-#: ./doc/common/tables/neutron-rpc.xml23(td)
-#: ./doc/common/tables/glance-amqp.xml23(td)
-#: ./doc/common/tables/heat-amqp.xml23(td)
-#: ./doc/common/tables/ceilometer-amqp.xml23(td)
-#: ./doc/common/tables/nova-rpc.xml23(td)
-#: ./doc/common/tables/trove-amqp.xml23(td)
-msgid "(BoolOpt) Auto-delete queues in amqp."
+#: ./doc/common/tables/nova-ldap.xml22(td)
+msgid "ldap_dns_base_dn = ou=hosts,dc=example,dc=org"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml26(td)
-#: ./doc/common/tables/cinder-rpc.xml30(td)
-#: ./doc/common/tables/keystone-amqp.xml26(td)
-#: ./doc/common/tables/neutron-rpc.xml26(td)
-#: ./doc/common/tables/glance-amqp.xml26(td)
-#: ./doc/common/tables/heat-amqp.xml26(td)
-#: ./doc/common/tables/ceilometer-amqp.xml26(td)
-#: ./doc/common/tables/nova-rpc.xml26(td)
-#: ./doc/common/tables/trove-amqp.xml26(td)
-msgid "amqp_durable_queues = False"
-msgstr "amqp_durable_queues = False"
-
-#: ./doc/common/tables/nova-rpc_all.xml27(td)
-#: ./doc/common/tables/cinder-rpc.xml31(td)
-#: ./doc/common/tables/keystone-amqp.xml27(td)
-#: ./doc/common/tables/neutron-rpc.xml27(td)
-#: ./doc/common/tables/glance-amqp.xml27(td)
-#: ./doc/common/tables/heat-amqp.xml27(td)
-#: ./doc/common/tables/ceilometer-amqp.xml27(td)
-#: ./doc/common/tables/nova-rpc.xml27(td)
-#: ./doc/common/tables/trove-amqp.xml27(td)
-msgid "(BoolOpt) Use durable queues in amqp."
+#: ./doc/common/tables/nova-ldap.xml23(td)
+msgid "(StrOpt) Base DN for DNS entries in LDAP"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml30(td)
-#: ./doc/common/tables/cinder-rpc.xml34(td)
-#: ./doc/common/tables/keystone-amqp.xml30(td)
-#: ./doc/common/tables/glance-rabbitmq.xml22(td)
-#: ./doc/common/tables/ceilometer-exchange.xml26(td)
-#: ./doc/common/tables/nova-rpc.xml30(td)
-#: ./doc/common/tables/trove-amqp.xml34(td)
-msgid "control_exchange = openstack"
-msgstr "control_exchange = openstack"
+#: ./doc/common/tables/nova-ldap.xml26(td)
+msgid "ldap_dns_password = password"
+msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml31(td)
-#: ./doc/common/tables/cinder-rpc.xml35(td)
-#: ./doc/common/tables/keystone-amqp.xml31(td)
-#: ./doc/common/tables/glance-rabbitmq.xml23(td)
-#: ./doc/common/tables/nova-rpc.xml31(td)
+#: ./doc/common/tables/nova-ldap.xml27(td)
+msgid "(StrOpt) Password for LDAP DNS"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml30(td)
+msgid "ldap_dns_servers = ['dns.example.org']"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml31(td)
+msgid "(MultiStrOpt) DNS Servers for LDAP DNS driver"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml34(td)
+msgid "ldap_dns_soa_expiry = 86400"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml35(td)
 msgid ""
-"(StrOpt) The default exchange under which topics are scoped. May be "
-"overridden by an exchange name specified in the transport_url option."
+"(StrOpt) Expiry interval (in seconds) for LDAP DNS driver Statement of "
+"Authority"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml34(td)
-#: ./doc/common/tables/cinder-rpc.xml46(td)
+#: ./doc/common/tables/nova-ldap.xml38(td)
+msgid "ldap_dns_soa_hostmaster = hostmaster@example.org"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml39(td)
+msgid "(StrOpt) Hostmaster for LDAP DNS driver Statement of Authority"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml42(td)
+msgid "ldap_dns_soa_minimum = 7200"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml43(td)
+msgid ""
+"(StrOpt) Minimum interval (in seconds) for LDAP DNS driver Statement of "
+"Authority"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml46(td)
+msgid "ldap_dns_soa_refresh = 1800"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml47(td)
+msgid ""
+"(StrOpt) Refresh interval (in seconds) for LDAP DNS driver Statement of "
+"Authority"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml50(td)
+msgid "ldap_dns_soa_retry = 3600"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml51(td)
+msgid ""
+"(StrOpt) Retry interval (in seconds) for LDAP DNS driver Statement of "
+"Authority"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml54(td)
+msgid "ldap_dns_url = ldap://ldap.example.com:389"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml55(td)
+msgid "(StrOpt) URL for LDAP server which will store DNS entries"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml58(td)
+msgid "ldap_dns_user = uid=admin,ou=people,dc=example,dc=org"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml59(td)
+msgid "(StrOpt) User for LDAP DNS"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-filter-recon.xml7(literal)
+#: ./doc/common/tables/swift-account-server-filter-recon.xml7(literal)
+#: ./doc/common/tables/swift-object-server-filter-recon.xml7(literal)
+msgid "[filter:recon]"
+msgstr "[filter:recon]"
+
+#: ./doc/common/tables/swift-container-server-filter-recon.xml18(td)
+#: ./doc/common/tables/swift-account-server-filter-recon.xml18(td)
+#: ./doc/common/tables/swift-object-server-filter-recon.xml18(td)
+msgid "use = egg:swift#recon"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml18(td)
+msgid ""
+"pipeline = catch_errors gatekeeper healthcheck proxy-logging cache "
+"container_sync bulk tempurl slo dlo ratelimit tempauth container-quotas "
+"account-quotas proxy-logging proxy-server"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml22(td)
+#: ./doc/common/tables/neutron-common.xml58(td)
+#: ./doc/common/tables/neutron-common.xml208(td)
+msgid "auth_strategy = keystone"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml23(td)
+#: ./doc/common/tables/nova-authentication.xml23(td)
+msgid "(StrOpt) The strategy to use for auth: noauth or keystone."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml133(th)
+msgid "[service_credentials]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml137(td)
+msgid ""
+"(BoolOpt) Disables X.509 certificate validation when an SSL connection to "
+"Identity Service is established."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml140(td)
+msgid "os_auth_url = http://localhost:5000/v2.0"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml141(td)
+msgid "(StrOpt) Auth URL to use for OpenStack service access."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml144(td)
+msgid "os_cacert = None"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml145(td)
+msgid "(StrOpt) Certificate chain for SSL validation."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml148(td)
+msgid "os_endpoint_type = publicURL"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml149(td)
+msgid ""
+"(StrOpt) Type of endpoint in Identity service catalog to use for "
+"communication with OpenStack services."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml152(td)
+msgid "os_password = admin"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml153(td)
+msgid "(StrOpt) Password to use for OpenStack service access."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml156(td)
+#: ./doc/common/tables/nova-volumes.xml46(td)
+#: ./doc/common/tables/cinder-compute.xml46(td)
+#: ./doc/common/tables/glance-common.xml82(td)
+msgid "os_region_name = None"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml157(td)
+msgid "(StrOpt) Region name to use for OpenStack service endpoints."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml160(td)
+msgid "os_tenant_id ="
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml161(td)
+msgid "(StrOpt) Tenant ID to use for OpenStack service access."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml164(td)
+msgid "os_tenant_name = admin"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml165(td)
+msgid "(StrOpt) Tenant name to use for OpenStack service access."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml168(td)
+msgid "os_username = ceilometer"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml169(td)
+msgid "(StrOpt) User name to use for OpenStack service access."
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml8(caption)
+#: ./doc/common/tables/heat-quota.xml8(caption)
+#: ./doc/common/tables/trove-quota.xml8(caption)
+#: ./doc/common/tables/nova-quota.xml8(caption)
+msgid "Description of configuration options for quota"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml23(td)
+msgid "(IntOpt) number of seconds between subsequent usage refreshes"
+msgstr "(IntOpt) nombre de secondes entre les rafraîchissements d'usage"
+
+#: ./doc/common/tables/cinder-quota.xml26(td)
+msgid "quota_driver = cinder.quota.DbQuotaDriver"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml27(td)
+msgid "(StrOpt) default driver to use for quota checks"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml30(td)
+msgid "quota_gigabytes = 1000"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml31(td)
+msgid ""
+"(IntOpt) number of volume gigabytes (snapshots are also included) allowed "
+"per project"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml34(td)
+msgid "quota_snapshots = 10"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml35(td)
+msgid "(IntOpt) number of volume snapshots allowed per project"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml38(td)
+msgid "quota_volumes = 10"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml39(td)
+msgid "(IntOpt) number of volumes allowed per project"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml43(td)
+msgid "(IntOpt) number of seconds until a reservation expires"
+msgstr "(IntOpt) nombre de secondes jusqu'à ce qu'une réservation expire"
+
+#: ./doc/common/tables/cinder-quota.xml46(td)
+msgid "use_default_quota_class = True"
+msgstr "use_default_quota_class = True"
+
+#: ./doc/common/tables/cinder-quota.xml47(td)
+msgid "(BoolOpt) whether to use default quota class for default quota"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml7(literal)
+msgid "[filter:account-quotas]"
+msgstr "[filter:account-quotas]"
+
+#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml18(td)
+msgid "use = egg:swift#account_quotas"
+msgstr "use = egg:swift#account_quotas"
+
+#: ./doc/common/tables/keystone-os_inherit.xml8(caption)
+msgid "Description of configuration options for os_inherit"
+msgstr ""
+
+#: ./doc/common/tables/keystone-os_inherit.xml19(th)
+msgid "[os_inherit]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-os_inherit.xml23(td)
+msgid ""
+"(BoolOpt) role-assignment inheritance to projects from owning domain can be "
+"optionally enabled."
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml8(caption)
+msgid "Description of configuration options for sdnve"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml19(th)
+msgid "[SDNVE]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml22(td)
+msgid "base_url = /one/nb/v2/"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml23(td)
+msgid "(StrOpt) Base URL for SDN-VE controller REST API"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml26(td)
+msgid "controller_ips = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml27(td)
+msgid "(ListOpt) List of IP addresses of SDN-VE controller(s)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml30(td)
+msgid "default_tenant_type = OF"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml31(td)
+msgid "(StrOpt) Tenant type: OF (default) and OVERLAY"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml34(td)
+msgid "format = json"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml35(td)
+msgid "(StrOpt) SDN-VE request/response format"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml38(td)
+msgid "info = sdnve_info_string"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml39(td)
+msgid "(StrOpt) SDN-VE RPC subject"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml42(td)
+msgid "integration_bridge = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml46(td)
+msgid "interface_mappings ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml47(td)
+msgid "(ListOpt) List of &lt;physical_network_name&gt;:&lt;interface_name&gt;"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml50(td)
+msgid "of_signature = SDNVE-OF"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml51(td)
+msgid ""
+"(StrOpt) The string in tenant description that indicates the tenant is a OF "
+"tenant"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml54(td)
+msgid "out_of_band = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml55(td)
+msgid "(BoolOpt) Indicating if controller is out of band or not"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml58(td)
+msgid "overlay_signature = SDNVE-OVERLAY"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml59(td)
+msgid ""
+"(StrOpt) The string in tenant description that indicates the tenant is a "
+"OVERLAY tenant"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml62(td)
+msgid "password = admin"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml63(td)
+msgid "(StrOpt) SDN-VE administrator password"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml66(td)
+msgid "port = 8443"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml67(td)
+msgid "(StrOpt) SDN-VE controller port number"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml70(td)
+msgid "reset_bridge = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml71(td)
+msgid "(BoolOpt) Reset the integration bridge before use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml74(td)
+msgid "use_fake_controller = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml75(td)
+msgid "(BoolOpt) If set to True uses a fake controller."
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml78(td)
+msgid "userid = admin"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml79(td)
+msgid "(StrOpt) SDN-VE administrator user id"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml82(th)
+msgid "[SDNVE_AGENT]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml85(td)
+#: ./doc/common/tables/neutron-hyperv_agent.xml38(td)
+msgid "polling_interval = 2"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml86(td)
+msgid "(IntOpt) Agent polling interval if necessary"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml89(td)
+#: ./doc/common/tables/neutron-common.xml174(td)
+#: ./doc/common/tables/neutron-common.xml185(td)
+msgid "root_helper = sudo"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml90(td)
+msgid "(StrOpt) Using root helper"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml93(td)
+msgid "rpc = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml94(td)
+msgid "(BoolOpt) Whether using rpc"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml8(caption)
+#: ./doc/common/tables/trove-compute.xml8(caption)
+#: ./doc/common/tables/neutron-compute.xml8(caption)
+#: ./doc/common/tables/cinder-compute.xml8(caption)
+msgid "Description of configuration options for compute"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml22(td)
+msgid "compute_available_monitors = ['nova.compute.monitors.all_monitors']"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml23(td)
+msgid ""
+"(MultiStrOpt) Monitor classes available to the compute which may be "
+"specified more than once."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml26(td)
+msgid "compute_driver = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml27(td)
+msgid ""
+"(StrOpt) Driver to use for controlling virtualization. Options include: "
+"libvirt.LibvirtDriver, xenapi.XenAPIDriver, fake.FakeDriver, "
+"baremetal.BareMetalDriver, vmwareapi.VMwareESXDriver, "
+"vmwareapi.VMwareVCDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml30(td)
+msgid "compute_manager = nova.compute.manager.ComputeManager"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml31(td)
+msgid "(StrOpt) Full class name for the Manager for compute"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml34(td)
+msgid "compute_monitors ="
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml35(td)
+msgid ""
+"(ListOpt) A list of monitors that can be used for getting compute metrics."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml38(td)
+msgid "compute_stats_class = nova.compute.stats.Stats"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml39(td)
+msgid "(StrOpt) Class that will manage stats for the local compute host"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml42(td)
+msgid "console_host = oslo"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml43(td)
+msgid ""
+"(StrOpt) Console proxy host to use to connect to instances on this host."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml46(td)
+msgid "console_manager = nova.console.manager.ConsoleProxyManager"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml47(td)
+msgid "(StrOpt) Full class name for the Manager for console proxy"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml50(td)
+msgid "default_flavor = m1.small"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml51(td)
+msgid ""
+"(StrOpt) Default flavor to use for the EC2 API only. The Nova API does not "
+"support a default flavor."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml58(td)
+#: ./doc/common/tables/heat-amqp.xml38(td)
+#: ./doc/common/tables/keystone-amqp.xml34(td)
+#: ./doc/common/tables/ceilometer-exchange.xml30(td)
+msgid "default_publisher_id = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml59(td)
+#: ./doc/common/tables/heat-amqp.xml39(td)
+#: ./doc/common/tables/trove-common.xml51(td)
+#: ./doc/common/tables/keystone-amqp.xml35(td)
+#: ./doc/common/tables/ceilometer-exchange.xml31(td)
+#: ./doc/common/tables/neutron-notifier.xml27(td)
+msgid "(StrOpt) Default publisher_id for outgoing notifications"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml62(td)
+msgid "enable_instance_password = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml63(td)
+msgid ""
+"(BoolOpt) Enables returning of the instance password by the relevant server "
+"API calls such as create, rebuild or rescue, If the hypervisor does not "
+"support password injection then the password returned will not be correct"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml66(td)
+msgid "heal_instance_info_cache_interval = 60"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml67(td)
+msgid ""
+"(IntOpt) Number of seconds between instance info_cache self healing updates"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml70(td)
+msgid "image_cache_manager_interval = 2400"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml71(td)
+msgid ""
+"(IntOpt) Number of seconds to wait between runs of the image cache manager"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml74(td)
+msgid "image_cache_subdirectory_name = _base"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml75(td)
+msgid ""
+"(StrOpt) Where cached images are stored under $instances_path. This is NOT "
+"the full path - just a folder name. For per-compute-host cached images, set "
+"to _base_$my_ip"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml78(td)
+msgid "image_handlers = download"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml79(td)
+msgid ""
+"(ListOpt) Specifies which image handler extension names to use for handling "
+"images. The first extension in the list which can handle the image with a "
+"suitable location will be used."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml82(td)
+msgid "instance_build_timeout = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml83(td)
+msgid ""
+"(IntOpt) Amount of time in seconds an instance can be in BUILD before going "
+"into ERROR status.Set to 0 to disable."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml86(td)
+msgid "instance_delete_interval = 300"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml87(td)
+msgid "(IntOpt) Interval in seconds for retrying failed instance file deletes"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml90(td)
+msgid "instance_usage_audit = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml91(td)
+msgid "(BoolOpt) Generate periodic compute.instance.exists notifications"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml94(td)
+msgid "instance_usage_audit_period = month"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml95(td)
+msgid ""
+"(StrOpt) Time period to generate instance usages for. Time period must be "
+"hour, day, month or year"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml98(td)
+msgid "instances_path = $state_path/instances"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml99(td)
+msgid "(StrOpt) Where instances are stored on disk"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml102(td)
+msgid "maximum_instance_delete_attempts = 5"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml103(td)
+msgid "(IntOpt) The number of times to attempt to reap an instance's files."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml106(td)
+msgid "reboot_timeout = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml107(td)
+msgid ""
+"(IntOpt) Automatically hard reboot an instance if it has been stuck in a "
+"rebooting state longer than N seconds. Set to 0 to disable."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml110(td)
+msgid "reclaim_instance_interval = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml111(td)
+msgid "(IntOpt) Interval in seconds for reclaiming deleted instances"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml114(td)
+msgid "resize_confirm_window = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml115(td)
+msgid ""
+"(IntOpt) Automatically confirm resizes after N seconds. Set to 0 to disable."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml118(td)
+msgid "resume_guests_state_on_host_boot = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml119(td)
+msgid ""
+"(BoolOpt) Whether to start guests that were running before the host rebooted"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml122(td)
+msgid "running_deleted_instance_action = reap"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml123(td)
+msgid ""
+"(StrOpt) Action to take if a running deleted instance is detected.Valid "
+"options are 'noop', 'log', 'shutdown', or 'reap'. Set to 'noop' to take no "
+"action."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml126(td)
+msgid "running_deleted_instance_poll_interval = 1800"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml127(td)
+msgid "(IntOpt) Number of seconds to wait between runs of the cleanup task."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml130(td)
+msgid "running_deleted_instance_timeout = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml131(td)
+msgid ""
+"(IntOpt) Number of seconds after being deleted when a running instance "
+"should be considered eligible for cleanup."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml134(td)
+msgid "shelved_offload_time = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml135(td)
+msgid ""
+"(IntOpt) Time in seconds before a shelved instance is eligible for removing "
+"from a host. -1 never offload, 0 offload when shelved"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml138(td)
+msgid "shelved_poll_interval = 3600"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml139(td)
+msgid "(IntOpt) Interval in seconds for polling shelved instances to offload"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml142(td)
+msgid "sync_power_state_interval = 600"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml143(td)
+msgid ""
+"(IntOpt) Interval to sync power states between the database and the "
+"hypervisor"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml146(td)
+msgid "vif_plugging_is_fatal = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml147(td)
+msgid "(BoolOpt) Fail instance boot if vif plugging fails"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml150(td)
+msgid "vif_plugging_timeout = 300"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml151(td)
+msgid ""
+"(IntOpt) Number of seconds to wait for neutron vif plugging events to arrive"
+" before continuing or failing (see vif_plugging_is_fatal). If this is set to"
+" zero and vif_plugging_is_fatal is False, events should not be expected to "
+"arrive at all."
+msgstr ""
+
+#: ./doc/common/tables/keystone-rabbit.xml8(caption)
+msgid "Description of configuration options for rabbit"
+msgstr ""
+
+#: ./doc/common/tables/keystone-rabbit.xml26(td)
 #: ./doc/common/tables/glance-rabbitmq.xml30(td)
 #: ./doc/common/tables/nova-kombu.xml22(td)
-#: ./doc/common/tables/keystone-rabbit.xml26(td)
+#: ./doc/common/tables/cinder-rpc.xml46(td)
+#: ./doc/common/tables/nova-rpc_all.xml34(td)
 msgid "kombu_reconnect_delay = 1.0"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml35(td)
-#: ./doc/common/tables/cinder-rpc.xml47(td)
+#: ./doc/common/tables/keystone-rabbit.xml27(td)
 #: ./doc/common/tables/glance-rabbitmq.xml31(td)
 #: ./doc/common/tables/nova-kombu.xml23(td)
-#: ./doc/common/tables/keystone-rabbit.xml27(td)
+#: ./doc/common/tables/cinder-rpc.xml47(td)
+#: ./doc/common/tables/nova-rpc_all.xml35(td)
 msgid ""
 "(FloatOpt) How long to wait before reconnecting in response to an AMQP "
 "consumer cancel notification."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml38(td)
-#: ./doc/common/tables/neutron-kombu.xml22(td)
-#: ./doc/common/tables/cinder-rpc.xml50(td)
-#: ./doc/common/tables/heat-rabbitmq.xml22(td)
-#: ./doc/common/tables/glance-rabbitmq.xml34(td)
-#: ./doc/common/tables/nova-kombu.xml26(td)
-#: ./doc/common/tables/keystone-rabbit.xml30(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml26(td)
-#: ./doc/common/tables/trove-amqp.xml42(td)
-msgid "kombu_ssl_ca_certs ="
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml39(td)
-#: ./doc/common/tables/cinder-rpc.xml51(td)
+#: ./doc/common/tables/keystone-rabbit.xml31(td)
 #: ./doc/common/tables/glance-rabbitmq.xml35(td)
 #: ./doc/common/tables/nova-kombu.xml27(td)
-#: ./doc/common/tables/keystone-rabbit.xml31(td)
+#: ./doc/common/tables/cinder-rpc.xml51(td)
+#: ./doc/common/tables/nova-rpc_all.xml39(td)
 msgid "(StrOpt) SSL certification authority file (valid only if SSL enabled)."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml42(td)
-#: ./doc/common/tables/neutron-kombu.xml26(td)
-#: ./doc/common/tables/cinder-rpc.xml54(td)
-#: ./doc/common/tables/heat-rabbitmq.xml26(td)
-#: ./doc/common/tables/glance-rabbitmq.xml38(td)
-#: ./doc/common/tables/nova-kombu.xml30(td)
-#: ./doc/common/tables/keystone-rabbit.xml34(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml30(td)
-#: ./doc/common/tables/trove-amqp.xml46(td)
-msgid "kombu_ssl_certfile ="
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml43(td)
-#: ./doc/common/tables/cinder-rpc.xml55(td)
+#: ./doc/common/tables/keystone-rabbit.xml35(td)
 #: ./doc/common/tables/glance-rabbitmq.xml39(td)
 #: ./doc/common/tables/nova-kombu.xml31(td)
-#: ./doc/common/tables/keystone-rabbit.xml35(td)
+#: ./doc/common/tables/cinder-rpc.xml55(td)
+#: ./doc/common/tables/nova-rpc_all.xml43(td)
 msgid "(StrOpt) SSL cert file (valid only if SSL enabled)."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml46(td)
-#: ./doc/common/tables/neutron-kombu.xml30(td)
-#: ./doc/common/tables/cinder-rpc.xml58(td)
-#: ./doc/common/tables/heat-rabbitmq.xml30(td)
-#: ./doc/common/tables/glance-rabbitmq.xml42(td)
-#: ./doc/common/tables/nova-kombu.xml34(td)
-#: ./doc/common/tables/keystone-rabbit.xml38(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml34(td)
-#: ./doc/common/tables/trove-amqp.xml50(td)
-msgid "kombu_ssl_keyfile ="
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml47(td)
-#: ./doc/common/tables/cinder-rpc.xml59(td)
+#: ./doc/common/tables/keystone-rabbit.xml39(td)
 #: ./doc/common/tables/glance-rabbitmq.xml43(td)
 #: ./doc/common/tables/nova-kombu.xml35(td)
-#: ./doc/common/tables/keystone-rabbit.xml39(td)
+#: ./doc/common/tables/cinder-rpc.xml59(td)
+#: ./doc/common/tables/nova-rpc_all.xml47(td)
 msgid "(StrOpt) SSL key file (valid only if SSL enabled)."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml50(td)
-#: ./doc/common/tables/neutron-kombu.xml34(td)
-#: ./doc/common/tables/cinder-rpc.xml62(td)
-#: ./doc/common/tables/heat-rabbitmq.xml34(td)
-#: ./doc/common/tables/glance-rabbitmq.xml46(td)
-#: ./doc/common/tables/nova-kombu.xml38(td)
-#: ./doc/common/tables/keystone-rabbit.xml42(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml38(td)
-#: ./doc/common/tables/trove-amqp.xml54(td)
-msgid "kombu_ssl_version ="
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml51(td)
-#: ./doc/common/tables/cinder-rpc.xml63(td)
+#: ./doc/common/tables/keystone-rabbit.xml43(td)
 #: ./doc/common/tables/glance-rabbitmq.xml47(td)
 #: ./doc/common/tables/nova-kombu.xml39(td)
-#: ./doc/common/tables/keystone-rabbit.xml43(td)
+#: ./doc/common/tables/cinder-rpc.xml63(td)
+#: ./doc/common/tables/nova-rpc_all.xml51(td)
 msgid ""
 "(StrOpt) SSL version to use (valid only if SSL enabled). valid values are "
 "TLSv1, SSLv23 and SSLv3. SSLv2 may be available on some distributions."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml54(td)
-#: ./doc/common/tables/heat-rpc.xml30(td)
-#: ./doc/common/tables/ceilometer-redis.xml26(td)
-#: ./doc/common/tables/cinder-rpc.xml66(td)
-#: ./doc/common/tables/neutron-rpc.xml34(td)
-#: ./doc/common/tables/trove-rpc.xml30(td)
-#: ./doc/common/tables/keystone-redis.xml26(td)
-#: ./doc/common/tables/glance-matchmaker.xml22(td)
-#: ./doc/common/tables/nova-rpc.xml34(td)
-msgid "matchmaker_heartbeat_freq = 300"
-msgstr "matchmaker_heartbeat_freq = 300"
-
-#: ./doc/common/tables/nova-rpc_all.xml55(td)
-#: ./doc/common/tables/cinder-rpc.xml67(td)
-#: ./doc/common/tables/keystone-redis.xml27(td)
-#: ./doc/common/tables/glance-matchmaker.xml23(td)
-#: ./doc/common/tables/nova-rpc.xml35(td)
-msgid "(IntOpt) Heartbeat frequency."
+#: ./doc/common/tables/cinder-backups_ceph.xml8(caption)
+msgid "Description of configuration options for backups_ceph"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml58(td)
-#: ./doc/common/tables/heat-rpc.xml34(td)
-#: ./doc/common/tables/ceilometer-redis.xml30(td)
-#: ./doc/common/tables/cinder-rpc.xml70(td)
-#: ./doc/common/tables/neutron-rpc.xml38(td)
-#: ./doc/common/tables/trove-rpc.xml34(td)
-#: ./doc/common/tables/keystone-redis.xml30(td)
-#: ./doc/common/tables/glance-matchmaker.xml26(td)
-#: ./doc/common/tables/nova-rpc.xml38(td)
-msgid "matchmaker_heartbeat_ttl = 600"
-msgstr "matchmaker_heartbeat_ttl = 600"
-
-#: ./doc/common/tables/nova-rpc_all.xml59(td)
-#: ./doc/common/tables/heat-rpc.xml35(td)
-#: ./doc/common/tables/ceilometer-redis.xml31(td)
-#: ./doc/common/tables/cinder-rpc.xml71(td)
-#: ./doc/common/tables/neutron-rpc.xml39(td)
-#: ./doc/common/tables/trove-rpc.xml35(td)
-#: ./doc/common/tables/keystone-redis.xml31(td)
-#: ./doc/common/tables/glance-matchmaker.xml27(td)
-#: ./doc/common/tables/nova-rpc.xml39(td)
-msgid "(IntOpt) Heartbeat time-to-live."
+#: ./doc/common/tables/cinder-backups_ceph.xml22(td)
+msgid "backup_ceph_chunk_size = 134217728"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml62(td)
-#: ./doc/common/tables/glance-qpid.xml22(td)
-#: ./doc/common/tables/keystone-qpid.xml22(td)
-#: ./doc/common/tables/trove-qpid.xml22(td)
-#: ./doc/common/tables/heat-qpid.xml22(td)
-#: ./doc/common/tables/cinder-rpc.xml94(td)
-#: ./doc/common/tables/neutron-qpid.xml22(td)
-#: ./doc/common/tables/nova-qpid.xml22(td)
-#: ./doc/common/tables/ceilometer-qpid.xml22(td)
-msgid "qpid_heartbeat = 60"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml63(td)
-#: ./doc/common/tables/glance-qpid.xml23(td)
-#: ./doc/common/tables/keystone-qpid.xml23(td)
-#: ./doc/common/tables/cinder-rpc.xml95(td)
-#: ./doc/common/tables/nova-qpid.xml23(td)
-msgid "(IntOpt) Seconds between connection keepalive heartbeats."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml66(td)
-#: ./doc/common/tables/glance-qpid.xml26(td)
-#: ./doc/common/tables/keystone-qpid.xml26(td)
-#: ./doc/common/tables/trove-qpid.xml26(td)
-#: ./doc/common/tables/heat-qpid.xml26(td)
-#: ./doc/common/tables/cinder-rpc.xml98(td)
-#: ./doc/common/tables/neutron-qpid.xml26(td)
-#: ./doc/common/tables/nova-qpid.xml26(td)
-#: ./doc/common/tables/ceilometer-qpid.xml26(td)
-msgid "qpid_hostname = localhost"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml67(td)
-#: ./doc/common/tables/glance-qpid.xml27(td)
-#: ./doc/common/tables/keystone-qpid.xml27(td)
-#: ./doc/common/tables/cinder-rpc.xml99(td)
-#: ./doc/common/tables/nova-qpid.xml27(td)
-msgid "(StrOpt) Qpid broker hostname."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml70(td)
-#: ./doc/common/tables/glance-qpid.xml30(td)
-#: ./doc/common/tables/keystone-qpid.xml30(td)
-#: ./doc/common/tables/trove-qpid.xml30(td)
-#: ./doc/common/tables/heat-qpid.xml30(td)
-#: ./doc/common/tables/cinder-rpc.xml102(td)
-#: ./doc/common/tables/neutron-qpid.xml30(td)
-#: ./doc/common/tables/nova-qpid.xml30(td)
-#: ./doc/common/tables/ceilometer-qpid.xml30(td)
-msgid "qpid_hosts = $qpid_hostname:$qpid_port"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml71(td)
-#: ./doc/common/tables/glance-qpid.xml31(td)
-#: ./doc/common/tables/keystone-qpid.xml31(td)
-#: ./doc/common/tables/cinder-rpc.xml103(td)
-#: ./doc/common/tables/nova-qpid.xml31(td)
-msgid "(ListOpt) Qpid HA cluster host:port pairs."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml74(td)
-#: ./doc/common/tables/glance-qpid.xml34(td)
-#: ./doc/common/tables/keystone-qpid.xml34(td)
-#: ./doc/common/tables/trove-qpid.xml34(td)
-#: ./doc/common/tables/heat-qpid.xml34(td)
-#: ./doc/common/tables/cinder-rpc.xml106(td)
-#: ./doc/common/tables/neutron-qpid.xml34(td)
-#: ./doc/common/tables/nova-qpid.xml34(td)
-#: ./doc/common/tables/ceilometer-qpid.xml34(td)
-msgid "qpid_password ="
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml75(td)
-#: ./doc/common/tables/glance-qpid.xml35(td)
-#: ./doc/common/tables/keystone-qpid.xml35(td)
-#: ./doc/common/tables/cinder-rpc.xml107(td)
-#: ./doc/common/tables/nova-qpid.xml35(td)
-msgid "(StrOpt) Password for Qpid connection."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml78(td)
-#: ./doc/common/tables/glance-qpid.xml38(td)
-#: ./doc/common/tables/keystone-qpid.xml38(td)
-#: ./doc/common/tables/trove-qpid.xml38(td)
-#: ./doc/common/tables/heat-qpid.xml38(td)
-#: ./doc/common/tables/cinder-rpc.xml110(td)
-#: ./doc/common/tables/neutron-qpid.xml38(td)
-#: ./doc/common/tables/nova-qpid.xml38(td)
-#: ./doc/common/tables/ceilometer-qpid.xml38(td)
-msgid "qpid_port = 5672"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml79(td)
-#: ./doc/common/tables/glance-qpid.xml39(td)
-#: ./doc/common/tables/keystone-qpid.xml39(td)
-#: ./doc/common/tables/cinder-rpc.xml111(td)
-#: ./doc/common/tables/nova-qpid.xml39(td)
-msgid "(IntOpt) Qpid broker port."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml82(td)
-#: ./doc/common/tables/glance-qpid.xml42(td)
-#: ./doc/common/tables/keystone-qpid.xml42(td)
-#: ./doc/common/tables/trove-qpid.xml42(td)
-#: ./doc/common/tables/heat-qpid.xml42(td)
-#: ./doc/common/tables/cinder-rpc.xml114(td)
-#: ./doc/common/tables/neutron-qpid.xml42(td)
-#: ./doc/common/tables/nova-qpid.xml42(td)
-#: ./doc/common/tables/ceilometer-qpid.xml42(td)
-msgid "qpid_protocol = tcp"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml83(td)
-#: ./doc/common/tables/glance-qpid.xml43(td)
-#: ./doc/common/tables/keystone-qpid.xml43(td)
-#: ./doc/common/tables/cinder-rpc.xml115(td)
-#: ./doc/common/tables/nova-qpid.xml43(td)
-msgid "(StrOpt) Transport to use, either 'tcp' or 'ssl'."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml86(td)
-#: ./doc/common/tables/glance-qpid.xml46(td)
-#: ./doc/common/tables/keystone-qpid.xml46(td)
-#: ./doc/common/tables/trove-qpid.xml46(td)
-#: ./doc/common/tables/heat-qpid.xml46(td)
-#: ./doc/common/tables/cinder-rpc.xml118(td)
-#: ./doc/common/tables/neutron-qpid.xml46(td)
-#: ./doc/common/tables/nova-qpid.xml46(td)
-#: ./doc/common/tables/ceilometer-qpid.xml46(td)
-msgid "qpid_sasl_mechanisms ="
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml87(td)
-#: ./doc/common/tables/glance-qpid.xml47(td)
-#: ./doc/common/tables/keystone-qpid.xml47(td)
-#: ./doc/common/tables/cinder-rpc.xml119(td)
-#: ./doc/common/tables/nova-qpid.xml47(td)
-msgid "(StrOpt) Space separated list of SASL mechanisms to use for auth."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml90(td)
-#: ./doc/common/tables/glance-qpid.xml50(td)
-#: ./doc/common/tables/keystone-qpid.xml50(td)
-#: ./doc/common/tables/trove-qpid.xml50(td)
-#: ./doc/common/tables/heat-qpid.xml50(td)
-#: ./doc/common/tables/cinder-rpc.xml122(td)
-#: ./doc/common/tables/neutron-qpid.xml50(td)
-#: ./doc/common/tables/nova-qpid.xml50(td)
-#: ./doc/common/tables/ceilometer-qpid.xml50(td)
-msgid "qpid_tcp_nodelay = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml91(td)
-#: ./doc/common/tables/glance-qpid.xml51(td)
-#: ./doc/common/tables/keystone-qpid.xml51(td)
-#: ./doc/common/tables/cinder-rpc.xml123(td)
-#: ./doc/common/tables/nova-qpid.xml51(td)
-msgid "(BoolOpt) Whether to disable the Nagle algorithm."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml94(td)
-#: ./doc/common/tables/glance-qpid.xml54(td)
-#: ./doc/common/tables/keystone-qpid.xml54(td)
-#: ./doc/common/tables/heat-qpid.xml54(td)
-#: ./doc/common/tables/cinder-rpc.xml126(td)
-#: ./doc/common/tables/neutron-qpid.xml54(td)
-#: ./doc/common/tables/nova-qpid.xml54(td)
-#: ./doc/common/tables/ceilometer-qpid.xml54(td)
-msgid "qpid_topology_version = 1"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml95(td)
-#: ./doc/common/tables/glance-qpid.xml55(td)
-#: ./doc/common/tables/keystone-qpid.xml55(td)
-#: ./doc/common/tables/heat-qpid.xml55(td)
-#: ./doc/common/tables/cinder-rpc.xml127(td)
-#: ./doc/common/tables/neutron-qpid.xml55(td)
-#: ./doc/common/tables/nova-qpid.xml55(td)
-#: ./doc/common/tables/ceilometer-qpid.xml55(td)
+#: ./doc/common/tables/cinder-backups_ceph.xml23(td)
 msgid ""
-"(IntOpt) The qpid topology version to use. Version 1 is what was originally "
-"used by impl_qpid. Version 2 includes some backwards-incompatible changes "
-"that allow broker federation to work. Users should update to version 2 when "
-"they are able to take everything down, as it requires a clean break."
+"(IntOpt) The chunk size, in bytes, that a backup is broken into before "
+"transfer to the Ceph object store."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml98(td)
-#: ./doc/common/tables/glance-qpid.xml58(td)
-#: ./doc/common/tables/keystone-qpid.xml58(td)
-#: ./doc/common/tables/trove-qpid.xml54(td)
-#: ./doc/common/tables/heat-qpid.xml58(td)
-#: ./doc/common/tables/cinder-rpc.xml130(td)
-#: ./doc/common/tables/neutron-qpid.xml58(td)
-#: ./doc/common/tables/nova-qpid.xml58(td)
-#: ./doc/common/tables/ceilometer-qpid.xml58(td)
-msgid "qpid_username ="
+#: ./doc/common/tables/cinder-backups_ceph.xml26(td)
+msgid "backup_ceph_conf = /etc/ceph/ceph.conf"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml99(td)
-#: ./doc/common/tables/glance-qpid.xml59(td)
-#: ./doc/common/tables/keystone-qpid.xml59(td)
-#: ./doc/common/tables/cinder-rpc.xml131(td)
-#: ./doc/common/tables/nova-qpid.xml59(td)
-msgid "(StrOpt) Username for Qpid connection."
+#: ./doc/common/tables/cinder-backups_ceph.xml27(td)
+msgid "(StrOpt) Ceph configuration file to use."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml102(td)
-#: ./doc/common/tables/trove-rabbitmq.xml22(td)
-#: ./doc/common/tables/cinder-rpc.xml134(td)
-#: ./doc/common/tables/heat-rabbitmq.xml38(td)
-#: ./doc/common/tables/glance-rabbitmq.xml50(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml22(td)
-#: ./doc/common/tables/keystone-rabbit.xml46(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml42(td)
-#: ./doc/common/tables/nova-rabbitmq.xml22(td)
-msgid "rabbit_ha_queues = False"
-msgstr "rabbit_ha_queues = False"
+#: ./doc/common/tables/cinder-backups_ceph.xml30(td)
+msgid "backup_ceph_pool = backups"
+msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml103(td)
-#: ./doc/common/tables/cinder-rpc.xml135(td)
-#: ./doc/common/tables/glance-rabbitmq.xml51(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml23(td)
-#: ./doc/common/tables/keystone-rabbit.xml47(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml43(td)
-#: ./doc/common/tables/nova-rabbitmq.xml23(td)
+#: ./doc/common/tables/cinder-backups_ceph.xml31(td)
+msgid "(StrOpt) The Ceph pool where volume backups are stored."
+msgstr ""
+
+#: ./doc/common/tables/cinder-backups_ceph.xml34(td)
+msgid "backup_ceph_stripe_count = 0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-backups_ceph.xml35(td)
+msgid "(IntOpt) RBD stripe count to use when creating a backup image."
+msgstr ""
+
+#: ./doc/common/tables/cinder-backups_ceph.xml38(td)
+msgid "backup_ceph_stripe_unit = 0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-backups_ceph.xml39(td)
+msgid "(IntOpt) RBD stripe unit to use when creating a backup image."
+msgstr ""
+
+#: ./doc/common/tables/cinder-backups_ceph.xml42(td)
+msgid "backup_ceph_user = cinder"
+msgstr ""
+
+#: ./doc/common/tables/cinder-backups_ceph.xml43(td)
 msgid ""
-"(BoolOpt) Use HA queues in RabbitMQ (x-ha-policy: all). If you change this "
-"option, you must wipe the RabbitMQ database."
+"(StrOpt) The Ceph user to connect with. Default here is to use the same user"
+" as for Cinder volumes. If not using cephx this should be set to None."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml106(td)
-#: ./doc/common/tables/trove-rabbitmq.xml26(td)
-#: ./doc/common/tables/cinder-rpc.xml138(td)
-#: ./doc/common/tables/heat-rabbitmq.xml42(td)
-#: ./doc/common/tables/glance-rabbitmq.xml54(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml26(td)
-#: ./doc/common/tables/keystone-rabbit.xml50(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml46(td)
-#: ./doc/common/tables/nova-rabbitmq.xml26(td)
-msgid "rabbit_host = localhost"
-msgstr "rabbit_host = localhost"
-
-#: ./doc/common/tables/nova-rpc_all.xml107(td)
-#: ./doc/common/tables/cinder-rpc.xml139(td)
-#: ./doc/common/tables/glance-rabbitmq.xml55(td)
-#: ./doc/common/tables/keystone-rabbit.xml51(td)
-#: ./doc/common/tables/nova-rabbitmq.xml27(td)
-msgid "(StrOpt) The RabbitMQ broker address where a single node is used."
+#: ./doc/common/tables/cinder-backups_ceph.xml46(td)
+msgid "restore_discard_excess_bytes = True"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml110(td)
-#: ./doc/common/tables/trove-rabbitmq.xml30(td)
-#: ./doc/common/tables/cinder-rpc.xml142(td)
-#: ./doc/common/tables/heat-rabbitmq.xml46(td)
-#: ./doc/common/tables/glance-rabbitmq.xml58(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml30(td)
-#: ./doc/common/tables/keystone-rabbit.xml54(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml50(td)
-#: ./doc/common/tables/nova-rabbitmq.xml30(td)
-msgid "rabbit_hosts = $rabbit_host:$rabbit_port"
-msgstr "rabbit_hosts = $rabbit_host:$rabbit_port"
-
-#: ./doc/common/tables/nova-rpc_all.xml111(td)
-#: ./doc/common/tables/cinder-rpc.xml143(td)
-#: ./doc/common/tables/glance-rabbitmq.xml59(td)
-#: ./doc/common/tables/keystone-rabbit.xml55(td)
-#: ./doc/common/tables/nova-rabbitmq.xml31(td)
-msgid "(ListOpt) RabbitMQ HA cluster host:port pairs."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml114(td)
-#: ./doc/common/tables/cinder-rpc.xml146(td)
-#: ./doc/common/tables/glance-rabbitmq.xml62(td)
-#: ./doc/common/tables/keystone-rabbit.xml58(td)
-#: ./doc/common/tables/nova-rabbitmq.xml34(td)
-msgid "rabbit_login_method = AMQPLAIN"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml115(td)
-#: ./doc/common/tables/cinder-rpc.xml147(td)
-#: ./doc/common/tables/glance-rabbitmq.xml63(td)
-#: ./doc/common/tables/keystone-rabbit.xml59(td)
-#: ./doc/common/tables/nova-rabbitmq.xml35(td)
-msgid "(StrOpt) the RabbitMQ login method"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml118(td)
-#: ./doc/common/tables/trove-rabbitmq.xml34(td)
-#: ./doc/common/tables/cinder-rpc.xml150(td)
-#: ./doc/common/tables/heat-rabbitmq.xml50(td)
-#: ./doc/common/tables/glance-rabbitmq.xml66(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml34(td)
-#: ./doc/common/tables/keystone-rabbit.xml62(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml54(td)
-#: ./doc/common/tables/nova-rabbitmq.xml38(td)
-msgid "rabbit_max_retries = 0"
-msgstr "rabbit_max_retries = 0"
-
-#: ./doc/common/tables/nova-rpc_all.xml119(td)
-#: ./doc/common/tables/cinder-rpc.xml151(td)
-#: ./doc/common/tables/glance-rabbitmq.xml67(td)
-#: ./doc/common/tables/keystone-rabbit.xml63(td)
-#: ./doc/common/tables/nova-rabbitmq.xml39(td)
+#: ./doc/common/tables/cinder-backups_ceph.xml47(td)
 msgid ""
-"(IntOpt) Maximum number of RabbitMQ connection retries. Default is 0 "
-"(infinite retry count)."
+"(BoolOpt) If True, always discard excess bytes when restoring volumes i.e. "
+"pad with zeroes."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml122(td)
-#: ./doc/common/tables/trove-rabbitmq.xml38(td)
-#: ./doc/common/tables/cinder-rpc.xml154(td)
-#: ./doc/common/tables/heat-rabbitmq.xml54(td)
-#: ./doc/common/tables/glance-rabbitmq.xml70(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml38(td)
-#: ./doc/common/tables/keystone-rabbit.xml66(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml58(td)
-#: ./doc/common/tables/nova-rabbitmq.xml42(td)
-msgid "rabbit_password = guest"
-msgstr "rabbit_password = guest"
-
-#: ./doc/common/tables/nova-rpc_all.xml123(td)
-#: ./doc/common/tables/cinder-rpc.xml155(td)
-#: ./doc/common/tables/glance-rabbitmq.xml71(td)
-#: ./doc/common/tables/keystone-rabbit.xml67(td)
-#: ./doc/common/tables/nova-rabbitmq.xml43(td)
-msgid "(StrOpt) The RabbitMQ password."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml126(td)
-#: ./doc/common/tables/trove-rabbitmq.xml42(td)
-#: ./doc/common/tables/cinder-rpc.xml158(td)
-#: ./doc/common/tables/heat-rabbitmq.xml58(td)
-#: ./doc/common/tables/glance-rabbitmq.xml74(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml42(td)
-#: ./doc/common/tables/keystone-rabbit.xml70(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml62(td)
-#: ./doc/common/tables/nova-rabbitmq.xml46(td)
-msgid "rabbit_port = 5672"
-msgstr "rabbit_port = 5672"
-
-#: ./doc/common/tables/nova-rpc_all.xml127(td)
-#: ./doc/common/tables/cinder-rpc.xml159(td)
-#: ./doc/common/tables/glance-rabbitmq.xml75(td)
-#: ./doc/common/tables/keystone-rabbit.xml71(td)
-#: ./doc/common/tables/nova-rabbitmq.xml47(td)
-msgid "(IntOpt) The RabbitMQ broker port where a single node is used."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml130(td)
-#: ./doc/common/tables/trove-rabbitmq.xml46(td)
-#: ./doc/common/tables/cinder-rpc.xml162(td)
-#: ./doc/common/tables/heat-rabbitmq.xml62(td)
-#: ./doc/common/tables/glance-rabbitmq.xml78(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml46(td)
-#: ./doc/common/tables/keystone-rabbit.xml74(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml66(td)
-#: ./doc/common/tables/nova-rabbitmq.xml50(td)
-msgid "rabbit_retry_backoff = 2"
-msgstr "rabbit_retry_backoff = 2"
-
-#: ./doc/common/tables/nova-rpc_all.xml131(td)
-#: ./doc/common/tables/cinder-rpc.xml163(td)
-#: ./doc/common/tables/glance-rabbitmq.xml79(td)
-#: ./doc/common/tables/keystone-rabbit.xml75(td)
-#: ./doc/common/tables/nova-rabbitmq.xml51(td)
+#: ./doc/common/tables/nova-vmware.xml23(td)
 msgid ""
-"(IntOpt) How long to backoff for between retries when connecting to "
-"RabbitMQ."
+"(IntOpt) The number of times we retry on failures, e.g., socket error, etc."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml134(td)
-#: ./doc/common/tables/trove-rabbitmq.xml50(td)
-#: ./doc/common/tables/cinder-rpc.xml166(td)
-#: ./doc/common/tables/heat-rabbitmq.xml66(td)
-#: ./doc/common/tables/glance-rabbitmq.xml82(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml50(td)
-#: ./doc/common/tables/keystone-rabbit.xml78(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml70(td)
-#: ./doc/common/tables/nova-rabbitmq.xml54(td)
-msgid "rabbit_retry_interval = 1"
-msgstr "rabbit_retry_interval = 1"
-
-#: ./doc/common/tables/nova-rpc_all.xml135(td)
-#: ./doc/common/tables/cinder-rpc.xml167(td)
-#: ./doc/common/tables/glance-rabbitmq.xml83(td)
-#: ./doc/common/tables/keystone-rabbit.xml79(td)
-#: ./doc/common/tables/nova-rabbitmq.xml55(td)
-msgid "(IntOpt) How frequently to retry connecting with RabbitMQ."
+#: ./doc/common/tables/nova-vmware.xml26(td)
+msgid "cluster_name = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml138(td)
-#: ./doc/common/tables/trove-rabbitmq.xml54(td)
-#: ./doc/common/tables/cinder-rpc.xml170(td)
-#: ./doc/common/tables/heat-rabbitmq.xml70(td)
-#: ./doc/common/tables/glance-rabbitmq.xml86(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml54(td)
-#: ./doc/common/tables/keystone-rabbit.xml82(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml74(td)
-#: ./doc/common/tables/nova-rabbitmq.xml58(td)
-msgid "rabbit_use_ssl = False"
-msgstr "rabbit_use_ssl = False"
-
-#: ./doc/common/tables/nova-rpc_all.xml139(td)
-#: ./doc/common/tables/cinder-rpc.xml171(td)
-#: ./doc/common/tables/glance-rabbitmq.xml87(td)
-#: ./doc/common/tables/keystone-rabbit.xml83(td)
-#: ./doc/common/tables/nova-rabbitmq.xml59(td)
-msgid "(BoolOpt) Connect over SSL for RabbitMQ."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml142(td)
-#: ./doc/common/tables/trove-rabbitmq.xml58(td)
-#: ./doc/common/tables/cinder-rpc.xml174(td)
-#: ./doc/common/tables/heat-rabbitmq.xml74(td)
-#: ./doc/common/tables/glance-rabbitmq.xml90(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml58(td)
-#: ./doc/common/tables/keystone-rabbit.xml86(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml78(td)
-#: ./doc/common/tables/nova-rabbitmq.xml62(td)
-msgid "rabbit_userid = guest"
-msgstr "rabbit_userid = guest"
-
-#: ./doc/common/tables/nova-rpc_all.xml143(td)
-#: ./doc/common/tables/cinder-rpc.xml175(td)
-#: ./doc/common/tables/glance-rabbitmq.xml91(td)
-#: ./doc/common/tables/keystone-rabbit.xml87(td)
-#: ./doc/common/tables/nova-rabbitmq.xml63(td)
-msgid "(StrOpt) The RabbitMQ userid."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml146(td)
-#: ./doc/common/tables/trove-rabbitmq.xml62(td)
-#: ./doc/common/tables/cinder-rpc.xml178(td)
-#: ./doc/common/tables/heat-rabbitmq.xml78(td)
-#: ./doc/common/tables/glance-rabbitmq.xml94(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml62(td)
-#: ./doc/common/tables/keystone-rabbit.xml90(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml82(td)
-#: ./doc/common/tables/nova-rabbitmq.xml66(td)
-msgid "rabbit_virtual_host = /"
-msgstr "rabbit_virtual_host = /"
-
-#: ./doc/common/tables/nova-rpc_all.xml147(td)
-#: ./doc/common/tables/cinder-rpc.xml179(td)
-#: ./doc/common/tables/glance-rabbitmq.xml95(td)
-#: ./doc/common/tables/keystone-rabbit.xml91(td)
-#: ./doc/common/tables/nova-rabbitmq.xml67(td)
-msgid "(StrOpt) The RabbitMQ virtual host."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml150(td)
-#: ./doc/common/tables/cinder-rpc.xml182(td)
-#: ./doc/common/tables/keystone-amqp.xml46(td)
-#: ./doc/common/tables/glance-amqp.xml38(td)
-#: ./doc/common/tables/nova-rpc.xml42(td)
-msgid "rpc_backend = rabbit"
-msgstr "rpc_backend = rabbit"
-
-#: ./doc/common/tables/nova-rpc_all.xml151(td)
-#: ./doc/common/tables/cinder-rpc.xml183(td)
-#: ./doc/common/tables/keystone-amqp.xml47(td)
-#: ./doc/common/tables/glance-amqp.xml39(td)
-#: ./doc/common/tables/nova-rpc.xml43(td)
+#: ./doc/common/tables/nova-vmware.xml27(td)
 msgid ""
-"(StrOpt) The messaging driver to use, defaults to rabbit. Other drivers "
-"include qpid and zmq."
+"(MultiStrOpt) Name of a VMware Cluster ComputeResource. Used only if "
+"compute_driver is vmwareapi.VMwareVCDriver."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml154(td)
-#: ./doc/common/tables/heat-rpc.xml42(td)
-#: ./doc/common/tables/glance-zmq.xml22(td)
-#: ./doc/common/tables/cinder-rpc.xml186(td)
-#: ./doc/common/tables/keystone-amqp.xml50(td)
-#: ./doc/common/tables/ceilometer-rpc.xml34(td)
-#: ./doc/common/tables/neutron-rpc.xml46(td)
-#: ./doc/common/tables/trove-rpc.xml54(td)
-#: ./doc/common/tables/nova-rpc.xml46(td)
-msgid "rpc_cast_timeout = 30"
-msgstr "rpc_cast_timeout = 30"
+#: ./doc/common/tables/nova-vmware.xml30(td)
+msgid "datastore_regex = None"
+msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml155(td)
-#: ./doc/common/tables/heat-rpc.xml43(td)
-#: ./doc/common/tables/glance-zmq.xml23(td)
-#: ./doc/common/tables/cinder-rpc.xml187(td)
-#: ./doc/common/tables/keystone-amqp.xml51(td)
-#: ./doc/common/tables/ceilometer-rpc.xml35(td)
-#: ./doc/common/tables/neutron-rpc.xml47(td)
-#: ./doc/common/tables/trove-rpc.xml55(td)
-#: ./doc/common/tables/nova-rpc.xml47(td)
+#: ./doc/common/tables/nova-vmware.xml31(td)
+msgid "(StrOpt) Regex to match the name of a datastore."
+msgstr ""
+
+#: ./doc/common/tables/nova-vmware.xml34(td)
+msgid "host_ip = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-vmware.xml35(td)
+msgid "(StrOpt) Hostname or IP address for connection to VMware ESX/VC host."
+msgstr ""
+
+#: ./doc/common/tables/nova-vmware.xml38(td)
+msgid "host_password = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-vmware.xml39(td)
+msgid "(StrOpt) Password for connection to VMware ESX/VC host."
+msgstr ""
+
+#: ./doc/common/tables/nova-vmware.xml42(td)
+msgid "host_username = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-vmware.xml43(td)
+msgid "(StrOpt) Username for connection to VMware ESX/VC host."
+msgstr ""
+
+#: ./doc/common/tables/nova-vmware.xml47(td)
+msgid "(StrOpt) Name of Integration Bridge"
+msgstr ""
+
+#: ./doc/common/tables/nova-vmware.xml50(td)
+msgid "maximum_objects = 100"
+msgstr ""
+
+#: ./doc/common/tables/nova-vmware.xml51(td)
 msgid ""
-"(IntOpt) Seconds to wait before a cast expires (TTL). Only supported by "
-"impl_zmq."
+"(IntOpt) The maximum number of ObjectContent data objects that should be "
+"returned in a single result. A positive value will cause the operation to "
+"suspend the retrieval when the count of objects reaches the specified "
+"maximum. The server may still limit the count to something less than the "
+"configured value. Any remaining objects may be retrieved with additional "
+"requests."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml158(td)
-#: ./doc/common/tables/heat-rpc.xml46(td)
-#: ./doc/common/tables/cinder-rpc.xml190(td)
-#: ./doc/common/tables/keystone-amqp.xml54(td)
-#: ./doc/common/tables/ceilometer-rpc.xml38(td)
-#: ./doc/common/tables/neutron-rpc.xml50(td)
-#: ./doc/common/tables/glance-amqp.xml42(td)
-#: ./doc/common/tables/trove-rpc.xml58(td)
-#: ./doc/common/tables/nova-rpc.xml50(td)
-msgid "rpc_conn_pool_size = 30"
-msgstr "rpc_conn_pool_size = 30"
-
-#: ./doc/common/tables/nova-rpc_all.xml159(td)
-#: ./doc/common/tables/cinder-rpc.xml191(td)
-#: ./doc/common/tables/keystone-amqp.xml55(td)
-#: ./doc/common/tables/glance-amqp.xml43(td)
-#: ./doc/common/tables/nova-rpc.xml51(td)
-msgid "(IntOpt) Size of RPC connection pool."
+#: ./doc/common/tables/nova-vmware.xml55(td)
+msgid "(FloatOpt) The interval used for polling of remote tasks."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml162(td)
-#: ./doc/common/tables/heat-rpc.xml50(td)
-#: ./doc/common/tables/cinder-rpc.xml194(td)
-#: ./doc/common/tables/keystone-amqp.xml58(td)
-#: ./doc/common/tables/ceilometer-rpc.xml42(td)
-#: ./doc/common/tables/neutron-rpc.xml54(td)
-#: ./doc/common/tables/glance-amqp.xml46(td)
-#: ./doc/common/tables/trove-rpc.xml62(td)
-#: ./doc/common/tables/nova-rpc.xml54(td)
-msgid "rpc_response_timeout = 60"
-msgstr "rpc_response_timeout = 60"
-
-#: ./doc/common/tables/nova-rpc_all.xml163(td)
-#: ./doc/common/tables/cinder-rpc.xml195(td)
-#: ./doc/common/tables/keystone-amqp.xml59(td)
-#: ./doc/common/tables/glance-amqp.xml47(td)
-#: ./doc/common/tables/nova-rpc.xml55(td)
-msgid "(IntOpt) Seconds to wait for a response from a call."
+#: ./doc/common/tables/nova-vmware.xml58(td)
+msgid "use_linked_clone = True"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml166(td)
-#: ./doc/common/tables/heat-rpc.xml54(td)
-#: ./doc/common/tables/cinder-rpc.xml198(td)
-#: ./doc/common/tables/keystone-amqp.xml62(td)
-#: ./doc/common/tables/ceilometer-rpc.xml46(td)
-#: ./doc/common/tables/neutron-rpc.xml58(td)
-#: ./doc/common/tables/glance-amqp.xml50(td)
-#: ./doc/common/tables/trove-rpc.xml66(td)
-#: ./doc/common/tables/nova-rpc.xml58(td)
-msgid "rpc_thread_pool_size = 64"
-msgstr "rpc_thread_pool_size = 64"
-
-#: ./doc/common/tables/nova-rpc_all.xml167(td)
-#: ./doc/common/tables/cinder-rpc.xml199(td)
-#: ./doc/common/tables/keystone-amqp.xml63(td)
-#: ./doc/common/tables/glance-amqp.xml51(td)
-#: ./doc/common/tables/nova-rpc.xml59(td)
-msgid "(IntOpt) Size of RPC greenthread pool."
+#: ./doc/common/tables/nova-vmware.xml59(td)
+msgid "(BoolOpt) Whether to use linked clone"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml170(td)
-#: ./doc/common/tables/glance-zmq.xml26(td)
+#: ./doc/common/tables/nova-vmware.xml62(td)
+msgid "wsdl_location = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-vmware.xml63(td)
+msgid ""
+"(StrOpt) Optional VIM Service WSDL Location e.g "
+"http://&lt;server&gt;/vimService.wsdl. Optional over-ride to default "
+"location for bug work-arounds"
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml8(caption)
+msgid "Description of configuration options for cfn_api"
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml22(td)
+msgid "instance_connection_https_validate_certificates = 1"
+msgstr "instance_connection_https_validate_certificates = 1"
+
+#: ./doc/common/tables/heat-cfn_api.xml23(td)
+msgid ""
+"(StrOpt) Instance connection to CFN/CW API validate certs if SSL is used."
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml26(td)
+msgid "instance_connection_is_secure = 0"
+msgstr "instance_connection_is_secure = 0"
+
+#: ./doc/common/tables/heat-cfn_api.xml27(td)
+msgid "(StrOpt) Instance connection to CFN/CW API via https."
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml30(th)
+msgid "[heat_api_cfn]"
+msgstr "[heat_api_cfn]"
+
+#: ./doc/common/tables/heat-cfn_api.xml34(td)
+#: ./doc/common/tables/heat-api.xml104(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml30(td)
+msgid "(IntOpt) Number of backlog requests to configure the socket with."
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml37(td)
+#: ./doc/common/tables/heat-api.xml107(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml33(td)
+#: ./doc/common/tables/glance-common.xml34(td)
+#: ./doc/common/tables/neutron-common.xml70(td)
+msgid "bind_host = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml38(td)
+#: ./doc/common/tables/heat-api.xml108(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml34(td)
+#: ./doc/common/tables/glance-common.xml35(td)
+msgid ""
+"(StrOpt) Address to bind the server. Useful when selecting a particular "
+"network interface."
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml41(td)
+msgid "bind_port = 8000"
+msgstr "bind_port = 8000"
+
+#: ./doc/common/tables/heat-cfn_api.xml42(td)
+#: ./doc/common/tables/heat-api.xml112(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml38(td)
+#: ./doc/common/tables/glance-common.xml39(td)
+msgid "(IntOpt) The port on which the server will listen."
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml46(td)
+#: ./doc/common/tables/heat-api.xml116(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml42(td)
+msgid "(StrOpt) Location of the SSL certificate file to use for SSL mode."
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml50(td)
+#: ./doc/common/tables/heat-api.xml120(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml46(td)
+msgid "(StrOpt) Location of the SSL key file to use for enabling SSL mode."
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml53(td)
+#: ./doc/common/tables/trove-api.xml66(td)
+#: ./doc/common/tables/heat-api.xml123(td)
+#: ./doc/common/tables/cinder-api.xml46(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml49(td)
+#: ./doc/common/tables/glance-wsgi.xml30(td)
+#: ./doc/common/tables/nova-api.xml42(td)
+#: ./doc/common/tables/neutron-api.xml42(td)
+msgid "max_header_line = 16384"
+msgstr "max_header_line = 16384"
+
+#: ./doc/common/tables/heat-cfn_api.xml54(td)
+#: ./doc/common/tables/heat-api.xml124(td)
+#: ./doc/common/tables/cinder-api.xml47(td)
+#: ./doc/common/tables/nova-api.xml43(td)
+msgid ""
+"(IntOpt) Maximum line size of message headers to be accepted. "
+"max_header_line may need to be increased when using large tokens (typically "
+"those generated by the Keystone v3 API with big service catalogs)."
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml57(td)
+#: ./doc/common/tables/heat-api.xml127(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml53(td)
+msgid "workers = 0"
+msgstr "workers = 0"
+
+#: ./doc/common/tables/heat-cfn_api.xml58(td)
+#: ./doc/common/tables/heat-api.xml128(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml54(td)
+msgid "(IntOpt) Number of workers for Heat service."
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml61(th)
+#: ./doc/common/tables/heat-api.xml142(th)
+#: ./doc/common/tables/keystone-ssl.xml54(th)
+#: ./doc/common/tables/nova-ca.xml62(th)
+#: ./doc/common/tables/cinder-ssl.xml19(th)
+#: ./doc/common/tables/trove-ssl.xml19(th)
+#: ./doc/common/tables/heat-cloudwatch_api.xml57(th)
+#: ./doc/common/tables/neutron-ssl.xml34(th)
+#: ./doc/common/tables/ceilometer-ssl.xml19(th)
+msgid "[ssl]"
+msgstr "[ssl]"
+
+#: ./doc/common/tables/heat-cfn_api.xml65(td)
+#: ./doc/common/tables/heat-api.xml146(td)
+#: ./doc/common/tables/cinder-common.xml175(td)
+#: ./doc/common/tables/cinder-ssl.xml23(td)
+#: ./doc/common/tables/trove-ssl.xml23(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml61(td)
+#: ./doc/common/tables/neutron-ssl.xml23(td)
+#: ./doc/common/tables/neutron-ssl.xml38(td)
+#: ./doc/common/tables/nova-wsgi.xml27(td)
+#: ./doc/common/tables/ceilometer-ssl.xml23(td)
+msgid "(StrOpt) CA certificate file to use to verify connecting clients"
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml69(td)
+#: ./doc/common/tables/heat-api.xml150(td)
+#: ./doc/common/tables/cinder-common.xml179(td)
+#: ./doc/common/tables/cinder-ssl.xml27(td)
+#: ./doc/common/tables/trove-ssl.xml27(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml65(td)
+#: ./doc/common/tables/neutron-ssl.xml27(td)
+#: ./doc/common/tables/neutron-ssl.xml42(td)
+#: ./doc/common/tables/ceilometer-ssl.xml27(td)
+msgid "(StrOpt) Certificate file to use when starting the server securely"
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml73(td)
+#: ./doc/common/tables/heat-api.xml154(td)
+#: ./doc/common/tables/cinder-common.xml183(td)
+#: ./doc/common/tables/cinder-ssl.xml31(td)
+#: ./doc/common/tables/trove-ssl.xml31(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml69(td)
+#: ./doc/common/tables/neutron-ssl.xml31(td)
+#: ./doc/common/tables/neutron-ssl.xml46(td)
+#: ./doc/common/tables/ceilometer-ssl.xml31(td)
+msgid "(StrOpt) Private key file to use when starting the server securely"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml22(td)
+msgid "default_interface_name = breth0"
+msgstr "default_interface_name = breth0"
+
+#: ./doc/common/tables/neutron-vmware.xml23(td)
+msgid ""
+"(StrOpt) Name of the interface on a L2 Gateway transport nodewhich should be"
+" used by default when setting up a network connection"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml26(td)
+msgid "default_l2_gw_service_uuid = None"
+msgstr "default_l2_gw_service_uuid = None"
+
+#: ./doc/common/tables/neutron-vmware.xml27(td)
+msgid ""
+"(StrOpt) Unique identifier of the NSX L2 Gateway service which will be used "
+"by default for network gateways"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml30(td)
+msgid "default_l3_gw_service_uuid = None"
+msgstr "default_l3_gw_service_uuid = None"
+
+#: ./doc/common/tables/neutron-vmware.xml31(td)
+msgid ""
+"(StrOpt) Unique identifier of the NSX L3 Gateway service which will be used "
+"for implementing routers and floating IPs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml34(td)
+msgid "default_service_cluster_uuid = None"
+msgstr "default_service_cluster_uuid = None"
+
+#: ./doc/common/tables/neutron-vmware.xml35(td)
+msgid ""
+"(StrOpt) Unique identifier of the Service Cluster which will be used by "
+"logical services like dhcp and metadata"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml38(td)
+msgid "default_tz_uuid = None"
+msgstr "default_tz_uuid = None"
+
+#: ./doc/common/tables/neutron-vmware.xml39(td)
+msgid ""
+"(StrOpt) This is uuid of the default NSX Transport zone that will be used "
+"for creating tunneled isolated \"Neutron\" networks. It needs to be created "
+"in NSX before starting Neutron with the nsx plugin."
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml42(td)
+msgid "http_timeout = 10"
+msgstr "http_timeout = 10"
+
+#: ./doc/common/tables/neutron-vmware.xml43(td)
+msgid "(IntOpt) Time before aborting a request"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml46(td)
+msgid "nsx_controllers = None"
+msgstr "nsx_controllers = None"
+
+#: ./doc/common/tables/neutron-vmware.xml47(td)
+msgid "(ListOpt) Lists the NSX controllers in this cluster"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml50(td)
+msgid "nsx_password = admin"
+msgstr "nsx_password = admin"
+
+#: ./doc/common/tables/neutron-vmware.xml51(td)
+msgid "(StrOpt) Password for NSX controllers in this cluster"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml54(td)
+msgid "nsx_user = admin"
+msgstr "nsx_user = admin"
+
+#: ./doc/common/tables/neutron-vmware.xml55(td)
+msgid "(StrOpt) User name for NSX controllers in this cluster"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml58(td)
+msgid "redirects = 2"
+msgstr "redirects = 2"
+
+#: ./doc/common/tables/neutron-vmware.xml59(td)
+msgid "(IntOpt) Number of times a redirect should be followed"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml62(td)
+msgid "req_timeout = 30"
+msgstr "req_timeout = 30"
+
+#: ./doc/common/tables/neutron-vmware.xml63(td)
+msgid "(IntOpt) Total time limit for a cluster request"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml66(td)
+msgid "retries = 2"
+msgstr "retries = 2"
+
+#: ./doc/common/tables/neutron-vmware.xml67(td)
+msgid "(IntOpt) Number of time a request should be retried"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml70(th)
+#: ./doc/common/tables/neutron-ml2_mlnx.xml19(th)
+#: ./doc/common/tables/neutron-mlnx.xml19(th)
+msgid "[ESWITCH]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml73(td)
+msgid "retries = 3"
+msgstr "retries = 3"
+
+#: ./doc/common/tables/neutron-vmware.xml74(td)
+msgid ""
+"(IntOpt) The number of retries the agent will send request to daemon before "
+"giving up"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml77(th)
+msgid "[NSX]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml80(td)
+msgid "agent_mode = agent"
+msgstr "agent_mode = agent"
+
+#: ./doc/common/tables/neutron-vmware.xml81(td)
+msgid "(StrOpt) The mode used to implement DHCP/metadata services."
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml84(td)
+msgid "concurrent_connections = 10"
+msgstr "concurrent_connections = 10"
+
+#: ./doc/common/tables/neutron-vmware.xml85(td)
+msgid "(IntOpt) Maximum concurrent connections to each NSX controller."
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml88(td)
+msgid "default_transport_type = stt"
+msgstr "default_transport_type = stt"
+
+#: ./doc/common/tables/neutron-vmware.xml89(td)
+msgid ""
+"(StrOpt) The default network tranport type to use (stt, gre, bridge, "
+"ipsec_gre, or ipsec_stt)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml92(td)
+msgid "max_lp_per_bridged_ls = 5000"
+msgstr "max_lp_per_bridged_ls = 5000"
+
+#: ./doc/common/tables/neutron-vmware.xml93(td)
+msgid ""
+"(IntOpt) Maximum number of ports of a logical switch on a bridged transport "
+"zone (default 5000)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml96(td)
+msgid "max_lp_per_overlay_ls = 256"
+msgstr "max_lp_per_overlay_ls = 256"
+
+#: ./doc/common/tables/neutron-vmware.xml97(td)
+msgid ""
+"(IntOpt) Maximum number of ports of a logical switch on an overlay transport"
+" zone (default 256)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml100(td)
+msgid "metadata_mode = access_network"
+msgstr "metadata_mode = access_network"
+
+#: ./doc/common/tables/neutron-vmware.xml101(td)
+msgid ""
+"(StrOpt) If set to access_network this enables a dedicated connection to the"
+" metadata proxy for metadata server access via Neutron router. If set to "
+"dhcp_host_route this enables host route injection via the dhcp agent. This "
+"option is only useful if running on a host that does not support namespaces "
+"otherwise access_network should be used."
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml104(td)
+msgid "nsx_gen_timeout = -1"
+msgstr "nsx_gen_timeout = -1"
+
+#: ./doc/common/tables/neutron-vmware.xml105(td)
+msgid ""
+"(IntOpt) Number of seconds a generation id should be valid for (default -1 "
+"meaning do not time out)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml108(td)
+msgid "replication_mode = service"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml109(td)
+msgid ""
+"(StrOpt) The default option leverages service nodes to perform packet "
+"replication though one could set to this to 'source' to perform replication "
+"locally. This is useful if one does not want to deploy a service node(s)."
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml112(th)
+msgid "[NSX_DHCP]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml115(td)
+msgid "default_lease_time = 43200"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml116(td)
+msgid "(IntOpt) Default DHCP lease time"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml119(td)
+msgid "domain_name = openstacklocal"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml120(td)
+#: ./doc/common/tables/nova-network.xml51(td)
+#: ./doc/common/tables/neutron-common.xml111(td)
+msgid "(StrOpt) Domain to use for building the hostnames"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml123(td)
+msgid "extra_domain_name_servers ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml124(td)
+msgid "(ListOpt) Comma separated list of additional domain name servers"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml127(th)
+msgid "[NSX_LSN]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml130(td)
+msgid "sync_on_missing_data = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml131(td)
+msgid ""
+"(BoolOpt) Pull LSN information from NSX in case it is missing from the local"
+" data store. This is useful to rebuild the local store in case of server "
+"recovery."
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml134(th)
+msgid "[NSX_METADATA]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml137(td)
+msgid "metadata_server_address = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml138(td)
+msgid "(StrOpt) IP address used by Metadata server."
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml141(td)
+msgid "metadata_server_port = 8775"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml142(td)
+msgid "(IntOpt) TCP Port used by Metadata server."
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml145(td)
+msgid "metadata_shared_secret ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml146(td)
+#: ./doc/common/tables/neutron-metadata.xml35(td)
+msgid "(StrOpt) Shared secret to sign instance-id request"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml149(th)
+msgid "[NSX_SYNC]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml152(td)
+msgid "always_read_status = False"
+msgstr "always_read_status = False"
+
+#: ./doc/common/tables/neutron-vmware.xml153(td)
+msgid ""
+"(BoolOpt) Always read operational status from backend on show operations. "
+"Enabling this option might slow down the system."
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml156(td)
+msgid "max_random_sync_delay = 0"
+msgstr "max_random_sync_delay = 0"
+
+#: ./doc/common/tables/neutron-vmware.xml157(td)
+msgid ""
+"(IntOpt) Maximum value for the additional random delay in seconds between "
+"runs of the state synchronization task"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml160(td)
+msgid "min_chunk_size = 500"
+msgstr "min_chunk_size = 500"
+
+#: ./doc/common/tables/neutron-vmware.xml161(td)
+msgid ""
+"(IntOpt) Minimum number of resources to be retrieved from NSX during state "
+"synchronization"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml164(td)
+msgid "min_sync_req_delay = 1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml165(td)
+msgid ""
+"(IntOpt) Minimum delay, in seconds, between two state synchronization "
+"queries to NSX. It must not exceed state_sync_interval"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml168(td)
+msgid "state_sync_interval = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml169(td)
+msgid ""
+"(IntOpt) Interval in seconds between runs of the state synchronization task."
+" Set it to 0 to disable it"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml172(th)
+msgid "[vcns]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml175(td)
+msgid "datacenter_moid = None"
+msgstr "datacenter_moid = None"
+
+#: ./doc/common/tables/neutron-vmware.xml176(td)
+msgid ""
+"(StrOpt) Optional parameter identifying the ID of datacenter to deploy NSX "
+"Edges"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml179(td)
+msgid "datastore_id = None"
+msgstr "datastore_id = None"
+
+#: ./doc/common/tables/neutron-vmware.xml180(td)
+#: ./doc/common/tables/neutron-vmware.xml184(td)
+msgid ""
+"(StrOpt) Optional parameter identifying the ID of datastore to deploy NSX "
+"Edges"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml183(td)
+msgid "deployment_container_id = None"
+msgstr "deployment_container_id = None"
+
+#: ./doc/common/tables/neutron-vmware.xml187(td)
+msgid "external_network = None"
+msgstr "external_network = None"
+
+#: ./doc/common/tables/neutron-vmware.xml188(td)
+msgid "(StrOpt) Network ID for physical network connectivity"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml191(td)
+msgid "manager_uri = None"
+msgstr "manager_uri = None"
+
+#: ./doc/common/tables/neutron-vmware.xml192(td)
+msgid "(StrOpt) uri for vsm"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml195(td)
+msgid "password = default"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml196(td)
+msgid "(StrOpt) Password for vsm"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml199(td)
+#: ./doc/common/tables/neutron-embrane_lb.xml62(td)
+msgid "resource_pool_id = None"
+msgstr "resource_pool_id = None"
+
+#: ./doc/common/tables/neutron-vmware.xml200(td)
+msgid ""
+"(StrOpt) Optional parameter identifying the ID of resource to deploy NSX "
+"Edges"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml203(td)
+msgid "task_status_check_interval = 2000"
+msgstr "task_status_check_interval = 2000"
+
+#: ./doc/common/tables/neutron-vmware.xml204(td)
+msgid "(IntOpt) Task status check interval"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml207(td)
+msgid "user = admin"
+msgstr "user = admin"
+
+#: ./doc/common/tables/neutron-vmware.xml208(td)
+msgid "(StrOpt) User name for vsm"
+msgstr ""
+
+#: ./doc/common/tables/nova-rdp.xml8(caption)
+msgid "Description of configuration options for rdp"
+msgstr ""
+
+#: ./doc/common/tables/nova-rdp.xml19(th)
+msgid "[rdp]"
+msgstr ""
+
+#: ./doc/common/tables/nova-rdp.xml23(td)
+msgid "(BoolOpt) Enable RDP related features"
+msgstr ""
+
+#: ./doc/common/tables/nova-rdp.xml26(td)
+msgid "html5_proxy_base_url = http://127.0.0.1:6083/"
+msgstr ""
+
+#: ./doc/common/tables/nova-rdp.xml27(td)
+msgid ""
+"(StrOpt) Location of RDP html5 console proxy, in the form "
+"\"http://127.0.0.1:6083/\""
+msgstr ""
+
+#: ./doc/common/tables/keystone-assignment.xml8(caption)
+msgid "Description of configuration options for assignment"
+msgstr ""
+
+#: ./doc/common/tables/keystone-assignment.xml19(th)
+msgid "[assignment]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-assignment.xml22(td)
+#: ./doc/common/tables/keystone-token.xml26(td)
+msgid "cache_time = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-assignment.xml23(td)
+msgid ""
+"(IntOpt) TTL (in seconds) to cache assignment data. This has no effect "
+"unless global caching is enabled."
+msgstr ""
+
+#: ./doc/common/tables/keystone-assignment.xml26(td)
+#: ./doc/common/tables/keystone-revoke.xml22(td)
+#: ./doc/common/tables/keystone-token.xml30(td)
+msgid "caching = True"
+msgstr ""
+
+#: ./doc/common/tables/keystone-assignment.xml27(td)
+msgid ""
+"(BoolOpt) Toggle for assignment caching. This has no effect unless global "
+"caching is enabled."
+msgstr ""
+
+#: ./doc/common/tables/keystone-assignment.xml30(td)
+msgid "driver = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-assignment.xml31(td)
+msgid "(StrOpt) Keystone Assignment backend driver."
+msgstr ""
+
+#: ./doc/common/tables/keystone-assignment.xml35(td)
+msgid ""
+"(IntOpt) Maximum number of entities that will be returned in an assignment "
+"collection."
+msgstr ""
+
+#: ./doc/common/tables/nova-zeromq.xml8(caption)
+#: ./doc/common/tables/heat-zeromq.xml8(caption)
+#: ./doc/common/tables/neutron-zeromq.xml8(caption)
+#: ./doc/common/tables/keystone-zeromq.xml8(caption)
+#: ./doc/common/tables/trove-zeromq.xml8(caption)
+msgid "Description of configuration options for zeromq"
+msgstr ""
+
+#: ./doc/common/tables/nova-zeromq.xml22(td)
+#: ./doc/common/tables/heat-zeromq.xml22(td)
+#: ./doc/common/tables/neutron-zeromq.xml22(td)
 #: ./doc/common/tables/keystone-zeromq.xml22(td)
+#: ./doc/common/tables/ceilometer-rpc.xml50(td)
+#: ./doc/common/tables/glance-zmq.xml26(td)
 #: ./doc/common/tables/cinder-rpc.xml202(td)
 #: ./doc/common/tables/trove-zeromq.xml22(td)
-#: ./doc/common/tables/ceilometer-rpc.xml50(td)
-#: ./doc/common/tables/heat-zeromq.xml22(td)
-#: ./doc/common/tables/nova-zeromq.xml22(td)
-#: ./doc/common/tables/neutron-zeromq.xml22(td)
+#: ./doc/common/tables/nova-rpc_all.xml170(td)
 msgid "rpc_zmq_bind_address = *"
 msgstr "rpc_zmq_bind_address = *"
 
-#: ./doc/common/tables/nova-rpc_all.xml171(td)
-#: ./doc/common/tables/glance-zmq.xml27(td)
+#: ./doc/common/tables/nova-zeromq.xml23(td)
+#: ./doc/common/tables/heat-zeromq.xml23(td)
+#: ./doc/common/tables/neutron-zeromq.xml23(td)
 #: ./doc/common/tables/keystone-zeromq.xml23(td)
+#: ./doc/common/tables/ceilometer-rpc.xml51(td)
+#: ./doc/common/tables/glance-zmq.xml27(td)
 #: ./doc/common/tables/cinder-rpc.xml203(td)
 #: ./doc/common/tables/trove-zeromq.xml23(td)
-#: ./doc/common/tables/ceilometer-rpc.xml51(td)
-#: ./doc/common/tables/heat-zeromq.xml23(td)
-#: ./doc/common/tables/nova-zeromq.xml23(td)
-#: ./doc/common/tables/neutron-zeromq.xml23(td)
+#: ./doc/common/tables/nova-rpc_all.xml171(td)
 msgid ""
 "(StrOpt) ZeroMQ bind address. Should be a wildcard (*), an ethernet "
 "interface, or IP. The \"host\" option should point or resolve to this "
 "address."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml174(td)
-#: ./doc/common/tables/glance-zmq.xml30(td)
+#: ./doc/common/tables/nova-zeromq.xml26(td)
+#: ./doc/common/tables/heat-zeromq.xml26(td)
+#: ./doc/common/tables/neutron-zeromq.xml26(td)
 #: ./doc/common/tables/keystone-zeromq.xml26(td)
+#: ./doc/common/tables/ceilometer-rpc.xml54(td)
+#: ./doc/common/tables/glance-zmq.xml30(td)
 #: ./doc/common/tables/cinder-rpc.xml206(td)
 #: ./doc/common/tables/trove-zeromq.xml26(td)
-#: ./doc/common/tables/ceilometer-rpc.xml54(td)
-#: ./doc/common/tables/heat-zeromq.xml26(td)
-#: ./doc/common/tables/nova-zeromq.xml26(td)
-#: ./doc/common/tables/neutron-zeromq.xml26(td)
+#: ./doc/common/tables/nova-rpc_all.xml174(td)
 msgid "rpc_zmq_contexts = 1"
 msgstr "rpc_zmq_contexts = 1"
 
-#: ./doc/common/tables/nova-rpc_all.xml175(td)
-#: ./doc/common/tables/glance-zmq.xml31(td)
-#: ./doc/common/tables/keystone-zeromq.xml27(td)
-#: ./doc/common/tables/cinder-rpc.xml207(td)
 #: ./doc/common/tables/nova-zeromq.xml27(td)
+#: ./doc/common/tables/keystone-zeromq.xml27(td)
+#: ./doc/common/tables/glance-zmq.xml31(td)
+#: ./doc/common/tables/cinder-rpc.xml207(td)
+#: ./doc/common/tables/nova-rpc_all.xml175(td)
 msgid "(IntOpt) Number of ZeroMQ contexts, defaults to 1."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml178(td)
-#: ./doc/common/tables/glance-zmq.xml34(td)
+#: ./doc/common/tables/nova-zeromq.xml30(td)
+#: ./doc/common/tables/heat-zeromq.xml30(td)
+#: ./doc/common/tables/neutron-zeromq.xml30(td)
 #: ./doc/common/tables/keystone-zeromq.xml30(td)
+#: ./doc/common/tables/ceilometer-rpc.xml58(td)
+#: ./doc/common/tables/glance-zmq.xml34(td)
 #: ./doc/common/tables/cinder-rpc.xml210(td)
 #: ./doc/common/tables/trove-zeromq.xml30(td)
-#: ./doc/common/tables/ceilometer-rpc.xml58(td)
-#: ./doc/common/tables/heat-zeromq.xml30(td)
-#: ./doc/common/tables/nova-zeromq.xml30(td)
-#: ./doc/common/tables/neutron-zeromq.xml30(td)
+#: ./doc/common/tables/nova-rpc_all.xml178(td)
 msgid "rpc_zmq_host = oslo"
 msgstr "rpc_zmq_host = oslo"
 
-#: ./doc/common/tables/nova-rpc_all.xml179(td)
-#: ./doc/common/tables/glance-zmq.xml35(td)
+#: ./doc/common/tables/nova-zeromq.xml31(td)
+#: ./doc/common/tables/heat-zeromq.xml31(td)
+#: ./doc/common/tables/neutron-zeromq.xml31(td)
 #: ./doc/common/tables/keystone-zeromq.xml31(td)
+#: ./doc/common/tables/ceilometer-rpc.xml59(td)
+#: ./doc/common/tables/glance-zmq.xml35(td)
 #: ./doc/common/tables/cinder-rpc.xml211(td)
 #: ./doc/common/tables/trove-zeromq.xml31(td)
-#: ./doc/common/tables/ceilometer-rpc.xml59(td)
-#: ./doc/common/tables/heat-zeromq.xml31(td)
-#: ./doc/common/tables/nova-zeromq.xml31(td)
-#: ./doc/common/tables/neutron-zeromq.xml31(td)
+#: ./doc/common/tables/nova-rpc_all.xml179(td)
 msgid ""
 "(StrOpt) Name of this node. Must be a valid hostname, FQDN, or IP address. "
 "Must match \"host\" option, if running Nova."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml182(td)
-#: ./doc/common/tables/glance-zmq.xml38(td)
+#: ./doc/common/tables/nova-zeromq.xml34(td)
+#: ./doc/common/tables/heat-zeromq.xml34(td)
+#: ./doc/common/tables/neutron-zeromq.xml34(td)
 #: ./doc/common/tables/keystone-zeromq.xml34(td)
+#: ./doc/common/tables/ceilometer-rpc.xml62(td)
+#: ./doc/common/tables/glance-zmq.xml38(td)
 #: ./doc/common/tables/cinder-rpc.xml214(td)
 #: ./doc/common/tables/trove-zeromq.xml34(td)
-#: ./doc/common/tables/ceilometer-rpc.xml62(td)
-#: ./doc/common/tables/heat-zeromq.xml34(td)
-#: ./doc/common/tables/nova-zeromq.xml34(td)
-#: ./doc/common/tables/neutron-zeromq.xml34(td)
+#: ./doc/common/tables/nova-rpc_all.xml182(td)
 msgid "rpc_zmq_ipc_dir = /var/run/openstack"
 msgstr "rpc_zmq_ipc_dir = /var/run/openstack"
 
-#: ./doc/common/tables/nova-rpc_all.xml183(td)
-#: ./doc/common/tables/glance-zmq.xml39(td)
-#: ./doc/common/tables/keystone-zeromq.xml35(td)
-#: ./doc/common/tables/cinder-rpc.xml215(td)
 #: ./doc/common/tables/nova-zeromq.xml35(td)
+#: ./doc/common/tables/keystone-zeromq.xml35(td)
+#: ./doc/common/tables/glance-zmq.xml39(td)
+#: ./doc/common/tables/cinder-rpc.xml215(td)
+#: ./doc/common/tables/nova-rpc_all.xml183(td)
 msgid "(StrOpt) Directory for holding IPC sockets."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml186(td)
-#: ./doc/common/tables/glance-zmq.xml42(td)
-#: ./doc/common/tables/keystone-zeromq.xml38(td)
-#: ./doc/common/tables/cinder-rpc.xml218(td)
 #: ./doc/common/tables/nova-zeromq.xml38(td)
+#: ./doc/common/tables/keystone-zeromq.xml38(td)
+#: ./doc/common/tables/glance-zmq.xml42(td)
+#: ./doc/common/tables/cinder-rpc.xml218(td)
+#: ./doc/common/tables/nova-rpc_all.xml186(td)
 msgid ""
 "rpc_zmq_matchmaker = oslo.messaging._drivers.matchmaker.MatchMakerLocalhost"
 msgstr "rpc_zmq_matchmaker = oslo.messaging._drivers.matchmaker.MatchMakerLocalhost"
 
-#: ./doc/common/tables/nova-rpc_all.xml187(td)
-#: ./doc/common/tables/glance-zmq.xml43(td)
-#: ./doc/common/tables/keystone-zeromq.xml39(td)
-#: ./doc/common/tables/cinder-rpc.xml219(td)
 #: ./doc/common/tables/nova-zeromq.xml39(td)
+#: ./doc/common/tables/keystone-zeromq.xml39(td)
+#: ./doc/common/tables/glance-zmq.xml43(td)
+#: ./doc/common/tables/cinder-rpc.xml219(td)
+#: ./doc/common/tables/nova-rpc_all.xml187(td)
 msgid "(StrOpt) MatchMaker driver."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml190(td)
-#: ./doc/common/tables/glance-zmq.xml46(td)
+#: ./doc/common/tables/nova-zeromq.xml42(td)
+#: ./doc/common/tables/heat-zeromq.xml42(td)
+#: ./doc/common/tables/neutron-zeromq.xml42(td)
 #: ./doc/common/tables/keystone-zeromq.xml42(td)
+#: ./doc/common/tables/ceilometer-rpc.xml70(td)
+#: ./doc/common/tables/glance-zmq.xml46(td)
 #: ./doc/common/tables/cinder-rpc.xml222(td)
 #: ./doc/common/tables/trove-zeromq.xml42(td)
-#: ./doc/common/tables/ceilometer-rpc.xml70(td)
-#: ./doc/common/tables/heat-zeromq.xml42(td)
-#: ./doc/common/tables/nova-zeromq.xml42(td)
-#: ./doc/common/tables/neutron-zeromq.xml42(td)
+#: ./doc/common/tables/nova-rpc_all.xml190(td)
 msgid "rpc_zmq_port = 9501"
 msgstr "rpc_zmq_port = 9501"
 
-#: ./doc/common/tables/nova-rpc_all.xml191(td)
-#: ./doc/common/tables/glance-zmq.xml47(td)
-#: ./doc/common/tables/keystone-zeromq.xml43(td)
-#: ./doc/common/tables/cinder-rpc.xml223(td)
 #: ./doc/common/tables/nova-zeromq.xml43(td)
+#: ./doc/common/tables/keystone-zeromq.xml43(td)
+#: ./doc/common/tables/glance-zmq.xml47(td)
+#: ./doc/common/tables/cinder-rpc.xml223(td)
+#: ./doc/common/tables/nova-rpc_all.xml191(td)
 msgid "(IntOpt) ZeroMQ receiver listening port."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml194(td)
-#: ./doc/common/tables/glance-zmq.xml50(td)
+#: ./doc/common/tables/nova-zeromq.xml46(td)
+#: ./doc/common/tables/heat-zeromq.xml46(td)
+#: ./doc/common/tables/neutron-zeromq.xml46(td)
 #: ./doc/common/tables/keystone-zeromq.xml46(td)
+#: ./doc/common/tables/ceilometer-rpc.xml74(td)
+#: ./doc/common/tables/glance-zmq.xml50(td)
 #: ./doc/common/tables/cinder-rpc.xml226(td)
 #: ./doc/common/tables/trove-zeromq.xml46(td)
-#: ./doc/common/tables/ceilometer-rpc.xml74(td)
-#: ./doc/common/tables/heat-zeromq.xml46(td)
-#: ./doc/common/tables/nova-zeromq.xml46(td)
-#: ./doc/common/tables/neutron-zeromq.xml46(td)
+#: ./doc/common/tables/nova-rpc_all.xml194(td)
 msgid "rpc_zmq_topic_backlog = None"
 msgstr "rpc_zmq_topic_backlog = None"
 
-#: ./doc/common/tables/nova-rpc_all.xml195(td)
-#: ./doc/common/tables/glance-zmq.xml51(td)
+#: ./doc/common/tables/nova-zeromq.xml47(td)
+#: ./doc/common/tables/heat-zeromq.xml47(td)
+#: ./doc/common/tables/neutron-zeromq.xml47(td)
 #: ./doc/common/tables/keystone-zeromq.xml47(td)
+#: ./doc/common/tables/ceilometer-rpc.xml75(td)
+#: ./doc/common/tables/glance-zmq.xml51(td)
 #: ./doc/common/tables/cinder-rpc.xml227(td)
 #: ./doc/common/tables/trove-zeromq.xml47(td)
-#: ./doc/common/tables/ceilometer-rpc.xml75(td)
-#: ./doc/common/tables/heat-zeromq.xml47(td)
-#: ./doc/common/tables/nova-zeromq.xml47(td)
-#: ./doc/common/tables/neutron-zeromq.xml47(td)
+#: ./doc/common/tables/nova-rpc_all.xml195(td)
 msgid ""
 "(IntOpt) Maximum number of ingress messages to locally buffer per topic. "
 "Default is unlimited."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml201(td)
-#: ./doc/common/tables/nova-rpc.xml65(td)
-msgid "rpc_driver_queue_base = cells.intercell"
+#: ./doc/common/tables/cinder-storage.xml8(caption)
+msgid "Description of configuration options for storage"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml202(td)
-#: ./doc/common/tables/nova-rpc.xml66(td)
+#: ./doc/common/tables/cinder-storage.xml22(td)
+msgid "allocated_capacity_weight_multiplier = -1.0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml23(td)
+#: ./doc/common/tables/cinder-storage.xml27(td)
 msgid ""
-"(StrOpt) Base queue name to use when communicating between cells. Various "
-"topics by message type will be appended to this."
+"(FloatOpt) Multiplier used for weighing volume capacity. Negative numbers "
+"mean to stack vs spread."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml205(th)
-#: ./doc/common/tables/trove-redis.xml34(th)
-#: ./doc/common/tables/heat-rpc.xml58(th)
-#: ./doc/common/tables/ceilometer-redis.xml49(th)
-#: ./doc/common/tables/cinder-rpc.xml238(th)
-#: ./doc/common/tables/neutron-rpc.xml73(th)
-#: ./doc/common/tables/keystone-redis.xml42(th)
-#: ./doc/common/tables/glance-matchmaker.xml30(th)
-#: ./doc/common/tables/nova-rpc.xml69(th)
-msgid "[matchmaker_ring]"
-msgstr "[matchmaker_ring]"
-
-#: ./doc/common/tables/nova-rpc_all.xml208(td)
-#: ./doc/common/tables/trove-redis.xml37(td)
-#: ./doc/common/tables/heat-rpc.xml61(td)
-#: ./doc/common/tables/ceilometer-redis.xml52(td)
-#: ./doc/common/tables/cinder-rpc.xml241(td)
-#: ./doc/common/tables/neutron-rpc.xml76(td)
-#: ./doc/common/tables/keystone-redis.xml45(td)
-#: ./doc/common/tables/glance-matchmaker.xml33(td)
-#: ./doc/common/tables/nova-rpc.xml72(td)
-msgid "ringfile = /etc/oslo/matchmaker_ring.json"
-msgstr "ringfile = /etc/oslo/matchmaker_ring.json"
-
-#: ./doc/common/tables/nova-rpc_all.xml209(td)
-#: ./doc/common/tables/cinder-rpc.xml242(td)
-#: ./doc/common/tables/keystone-redis.xml46(td)
-#: ./doc/common/tables/glance-matchmaker.xml34(td)
-#: ./doc/common/tables/nova-rpc.xml73(td)
-msgid "(StrOpt) Matchmaker ring file (JSON)."
+#: ./doc/common/tables/cinder-storage.xml26(td)
+msgid "capacity_weight_multiplier = 1.0"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml212(th)
-#: ./doc/common/tables/nova-rpc.xml76(th)
-#: ./doc/common/tables/nova-upgrade_levels.xml26(th)
-msgid "[upgrade_levels]"
+#: ./doc/common/tables/cinder-storage.xml30(td)
+msgid "enabled_backends = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml215(td)
-#: ./doc/common/tables/nova-rpc.xml79(td)
-msgid "baseapi = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml216(td)
-#: ./doc/common/tables/nova-rpc.xml80(td)
+#: ./doc/common/tables/cinder-storage.xml31(td)
 msgid ""
-"(StrOpt) Set a version cap for messages sent to the base api in any service"
+"(ListOpt) A list of backend names to use. These backend names should be "
+"backed by a unique [CONFIG] group with its options"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_l2pop.xml8(caption)
-msgid "Description of configuration options for ml2_l2pop"
+#: ./doc/common/tables/cinder-storage.xml34(td)
+msgid "iscsi_helper = tgtadm"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_l2pop.xml19(th)
-msgid "[l2pop]"
+#: ./doc/common/tables/cinder-storage.xml35(td)
+msgid "(StrOpt) iscsi target user-land tool to use"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_l2pop.xml22(td)
-msgid "agent_boot_time = 180"
+#: ./doc/common/tables/cinder-storage.xml38(td)
+msgid "iscsi_iotype = fileio"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_l2pop.xml23(td)
+#: ./doc/common/tables/cinder-storage.xml39(td)
 msgid ""
-"(IntOpt) Delay within which agent is expected to update existing ports whent"
-" it restarts"
+"(StrOpt) Sets the behavior of the iSCSI target to either perform blockio or "
+"fileio optionally, auto can be set and Cinder will autodetect type of "
+"backing device"
 msgstr ""
 
-#: ./doc/common/tables/glance-qpid.xml8(caption)
-#: ./doc/common/tables/keystone-qpid.xml8(caption)
-#: ./doc/common/tables/trove-qpid.xml8(caption)
-#: ./doc/common/tables/heat-qpid.xml8(caption)
-#: ./doc/common/tables/neutron-qpid.xml8(caption)
-#: ./doc/common/tables/nova-qpid.xml8(caption)
-#: ./doc/common/tables/ceilometer-qpid.xml8(caption)
-msgid "Description of configuration options for qpid"
+#: ./doc/common/tables/cinder-storage.xml42(td)
+msgid "iscsi_ip_address = $my_ip"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml7(literal)
-#: ./doc/common/tables/swift-container-server-container-updater.xml7(literal)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml7(literal)
-#: ./doc/common/tables/swift-container-server-container-sync.xml7(literal)
-#: ./doc/common/tables/swift-container-server-pipeline-main.xml7(literal)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml7(literal)
+#: ./doc/common/tables/cinder-storage.xml43(td)
+msgid "(StrOpt) The IP address that the iSCSI daemon is listening on"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml46(td)
+msgid "iscsi_num_targets = 100"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml47(td)
+msgid "(IntOpt) The maximum number of iscsi target ids per host"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml50(td)
+msgid "iscsi_port = 3260"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml51(td)
+msgid "(IntOpt) The port that the iSCSI daemon is listening on"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml54(td)
+msgid "iscsi_target_prefix = iqn.2010-10.org.openstack:"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml55(td)
+msgid "(StrOpt) prefix for iscsi volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml58(td)
+msgid "iser_helper = tgtadm"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml59(td)
+msgid "(StrOpt) iser target user-land tool to use"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml62(td)
+msgid "iser_ip_address = $my_ip"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml63(td)
+msgid "(StrOpt) The IP address that the iSER daemon is listening on"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml66(td)
+msgid "iser_num_targets = 100"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml67(td)
+msgid "(IntOpt) The maximum number of iser target ids per host"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml70(td)
+msgid "iser_port = 3260"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml71(td)
+msgid "(IntOpt) The port that the iSER daemon is listening on"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml74(td)
+msgid "iser_target_prefix = iqn.2010-10.org.iser.openstack:"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml75(td)
+msgid "(StrOpt) prefix for iser volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml78(td)
+msgid "max_gigabytes = 10000"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml79(td)
+msgid ""
+"(IntOpt) This configure option has been deprecated along with the "
+"SimpleScheduler. New scheduler is able to gather capacity information for "
+"each host, thus setting the maximum number of volume gigabytes for host is "
+"no longer needed. It's safe to remove this configure from cinder.conf."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml82(td)
+msgid "migration_create_volume_timeout_secs = 300"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml83(td)
+msgid ""
+"(IntOpt) Timeout for creating the volume to migrate to when performing "
+"volume migration (seconds)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml86(td)
+msgid "num_iser_scan_tries = 3"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml87(td)
+msgid ""
+"(IntOpt) The maximum number of times to rescan iSER targetto find volume"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml90(td)
+msgid "num_volume_device_scan_tries = 3"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml91(td)
+msgid "(IntOpt) The maximum number of times to rescan targets to find volume"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml94(td)
+msgid "volume_backend_name = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml95(td)
+msgid "(StrOpt) The backend name for a given driver implementation"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml98(td)
+#: ./doc/common/tables/nova-libvirt.xml85(td)
+msgid "volume_clear = zero"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml99(td)
+msgid ""
+"(StrOpt) Method used to wipe old voumes (valid options are: none, zero, "
+"shred)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml102(td)
+msgid "volume_clear_ionice = None"
+msgstr "volume_clear_ionice = None"
+
+#: ./doc/common/tables/cinder-storage.xml103(td)
+msgid ""
+"(StrOpt) The flag to pass to ionice to alter the i/o priority of the process"
+" used to zero a volume after deletion, for example \"-c3\" for idle only "
+"priority."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml106(td)
+#: ./doc/common/tables/nova-libvirt.xml89(td)
+msgid "volume_clear_size = 0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml107(td)
+#: ./doc/common/tables/nova-libvirt.xml90(td)
+msgid "(IntOpt) Size in MiB to wipe at start of old volumes. 0 =&gt; all"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml110(td)
+msgid "volume_dd_blocksize = 1M"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml111(td)
+msgid "(StrOpt) The default block size used when copying/clearing volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml114(td)
+msgid "volume_driver = cinder.volume.drivers.lvm.LVMISCSIDriver"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml115(td)
+msgid "(StrOpt) Driver to use for volume creation"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml118(td)
+msgid "volume_manager = cinder.volume.manager.VolumeManager"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml119(td)
+msgid "(StrOpt) full class name for the Manager for volume"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml122(td)
+msgid "volume_service_inithost_offload = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml123(td)
+msgid "(BoolOpt) Offload pending volume delete during volume service startup"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml126(td)
+msgid "volume_usage_audit_period = month"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml127(td)
+msgid ""
+"(StrOpt) time period to generate volume usages for. Time period must be "
+"hour, day, month or year"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml130(td)
+msgid "volumes_dir = $state_path/volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml131(td)
+msgid "(StrOpt) Volume configuration file storage directory"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml145(td)
+msgid "max_pool_size = 5"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml150(td)
+#: ./doc/common/tables/heat-database.xml66(td)
+msgid ""
+"(IntOpt) maximum db connection retries during startup. (setting -1 implies "
+"an infinite retry count)"
+msgstr "(IntOpt) Nombre maximum de nouvelles tentatives de connexion db pendant le démarrage. (paramètre -1 implique un nombre indéfini de nouvelles tentatives)"
+
+#: ./doc/common/tables/glance-registry.xml8(caption)
+msgid "Description of configuration options for registry"
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml23(td)
+msgid "(StrOpt) The administrators password."
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml26(td)
+#: ./doc/common/tables/neutron-common.xml26(td)
+#: ./doc/common/tables/neutron-common.xml196(td)
+msgid "admin_tenant_name = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml27(td)
+msgid "(StrOpt) The tenant name of the administrative user."
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml31(td)
+msgid "(StrOpt) The administrators user name."
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml34(td)
+#: ./doc/common/tables/neutron-common.xml54(td)
+#: ./doc/common/tables/neutron-common.xml204(td)
+msgid "auth_region = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml35(td)
+msgid "(StrOpt) The region for the authentication service."
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml39(td)
+msgid "(StrOpt) The strategy to use for authentication."
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml42(td)
+#: ./doc/common/tables/neutron-common.xml62(td)
+#: ./doc/common/tables/neutron-common.xml212(td)
+msgid "auth_url = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml43(td)
+msgid "(StrOpt) The URL to the keystone service."
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml46(td)
+msgid "registry_client_ca_file = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml47(td)
+msgid ""
+"(StrOpt) The path to the certifying authority cert file to use in SSL "
+"connections to the registry server."
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml50(td)
+msgid "registry_client_cert_file = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml51(td)
+msgid ""
+"(StrOpt) The path to the cert file to use in SSL connections to the registry"
+" server."
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml54(td)
+msgid "registry_client_insecure = False"
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml55(td)
+msgid ""
+"(BoolOpt) When using SSL in connections to the registry server, do not "
+"require validation via a certifying authority."
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml58(td)
+msgid "registry_client_key_file = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml59(td)
+msgid ""
+"(StrOpt) The path to the key file to use in SSL connections to the registry "
+"server."
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml62(td)
+msgid "registry_client_protocol = http"
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml63(td)
+msgid ""
+"(StrOpt) The protocol to use for communication with the registry server. "
+"Either http or https."
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml66(td)
+msgid "registry_client_timeout = 600"
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml67(td)
+msgid ""
+"(IntOpt) The period of time, in seconds, that the API server will wait for a"
+" registry request to complete. A value of 0 implies no timeout."
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml70(td)
+msgid "registry_host = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml71(td)
+msgid "(StrOpt) Address to find the registry server."
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml74(td)
+msgid "registry_port = 9191"
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml75(td)
+msgid "(IntOpt) Port the registry server is listening on."
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml8(caption)
+msgid "Description of configuration options for embrane"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml19(th)
+#: ./doc/common/tables/neutron-common.xml216(th)
+msgid "[heleos]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml22(td)
+msgid "admin_username = admin"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml23(td)
+#: ./doc/common/tables/neutron-embrane_lb.xml27(td)
+msgid "(StrOpt) ESM admin username."
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml26(td)
+msgid "async_requests = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml27(td)
+#: ./doc/common/tables/neutron-embrane_lb.xml31(td)
+msgid "(BoolOpt) Define if the requests have run asynchronously or not"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml30(td)
+#: ./doc/common/tables/neutron-embrane_lb.xml34(td)
+msgid "dummy_utif_id = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml31(td)
+msgid "(StrOpt) Dummy user traffic Security Zone id"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml34(td)
+#: ./doc/common/tables/neutron-embrane_lb.xml38(td)
+msgid "esm_mgmt = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml35(td)
+#: ./doc/common/tables/neutron-embrane_lb.xml39(td)
+msgid "(StrOpt) ESM management root address"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml38(td)
+#: ./doc/common/tables/neutron-embrane_lb.xml42(td)
+msgid "inband_id = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml39(td)
+msgid "(StrOpt) In band Security Zone id"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml42(td)
+#: ./doc/common/tables/neutron-embrane_lb.xml54(td)
+msgid "mgmt_id = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml43(td)
+msgid "(StrOpt) Management Security Zone id"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml46(td)
+#: ./doc/common/tables/neutron-embrane_lb.xml58(td)
+msgid "oob_id = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml47(td)
+msgid "(StrOpt) Out of band Security Zone id"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml50(td)
+msgid "resource_pool_id = default"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml51(td)
+#: ./doc/common/tables/neutron-embrane_lb.xml63(td)
+msgid "(StrOpt) Shared resource pool id"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml54(td)
+msgid "router_image = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml55(td)
+msgid "(StrOpt) Router image id (Embrane FW/VPN)"
+msgstr ""
+
+#: ./doc/common/tables/heat-quota.xml22(td)
+msgid "max_events_per_stack = 1000"
+msgstr "max_events_per_stack = 1000"
+
+#: ./doc/common/tables/heat-quota.xml23(td)
+msgid ""
+"(IntOpt) Maximum events that will be available per stack. Older events will "
+"be deleted when this is reached. Set to 0 for unlimited events per stack."
+msgstr ""
+
+#: ./doc/common/tables/heat-quota.xml26(td)
+msgid "max_nested_stack_depth = 3"
+msgstr "max_nested_stack_depth = 3"
+
+#: ./doc/common/tables/heat-quota.xml27(td)
+msgid "(IntOpt) Maximum depth allowed when using nested stacks."
+msgstr ""
+
+#: ./doc/common/tables/heat-quota.xml30(td)
+msgid "max_resources_per_stack = 1000"
+msgstr "max_resources_per_stack = 1000"
+
+#: ./doc/common/tables/heat-quota.xml31(td)
+msgid "(IntOpt) Maximum resources allowed per top-level stack."
+msgstr ""
+
+#: ./doc/common/tables/heat-quota.xml34(td)
+msgid "max_stacks_per_tenant = 100"
+msgstr "max_stacks_per_tenant = 100"
+
+#: ./doc/common/tables/heat-quota.xml35(td)
+msgid ""
+"(IntOpt) Maximum number of stacks any one tenant may have active at one "
+"time."
+msgstr ""
+
+#: ./doc/common/tables/heat-quota.xml38(td)
+msgid "max_template_size = 524288"
+msgstr "max_template_size = 524288"
+
+#: ./doc/common/tables/heat-quota.xml39(td)
+msgid "(IntOpt) Maximum raw byte size of any template."
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml7(literal)
 #: ./doc/common/tables/swift-container-server-filter-healthcheck.xml7(literal)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml7(literal)
-#: ./doc/common/tables/swift-container-server-filter-recon.xml7(literal)
-msgid "container-server.conf-sample"
+#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml7(literal)
+msgid "[filter:healthcheck]"
+msgstr "[filter:healthcheck]"
+
+#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml7(literal)
+#: ./doc/common/tables/swift-account-server-filter-recon.xml7(literal)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml7(literal)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml7(literal)
+#: ./doc/common/tables/swift-account-server-pipeline-main.xml7(literal)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml7(literal)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml7(literal)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml7(literal)
+msgid "account-server.conf-sample"
+msgstr "account-server.conf-sample"
+
+#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml18(td)
+#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml18(td)
+#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml18(td)
+msgid "use = egg:swift#healthcheck"
+msgstr "use = egg:swift#healthcheck"
+
+#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml21(td)
+#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml21(td)
+#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml21(td)
+msgid "disable_path ="
+msgstr "disable_path ="
+
+#: ./doc/common/tables/nova-common.xml22(td)
+msgid "bindir = /usr/local/bin"
+msgstr "bindir = /usr/local/bin"
+
+#: ./doc/common/tables/nova-common.xml23(td)
+msgid "(StrOpt) Directory where nova binaries are installed"
+msgstr "(StrOpt)  Répertoire où les binaires nova sont installées"
+
+#: ./doc/common/tables/nova-common.xml26(td)
+msgid "compute_topic = compute"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml18(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml18(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml18(td)
-msgid "bind_ip = 0.0.0.0"
+#: ./doc/common/tables/nova-common.xml27(td)
+msgid "(StrOpt) The topic compute nodes listen on"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml18(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml18(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml18(td)
-msgid "IP Address for server to bind to"
+#: ./doc/common/tables/nova-common.xml30(td)
+msgid "console_topic = console"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml21(td)
-msgid "bind_port = 6001"
+#: ./doc/common/tables/nova-common.xml31(td)
+msgid "(StrOpt) The topic console proxy nodes listen on"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml21(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml21(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml21(td)
-msgid "Port for server to bind to"
+#: ./doc/common/tables/nova-common.xml34(td)
+msgid "consoleauth_topic = consoleauth"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml24(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml24(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml24(td)
-msgid "bind_timeout = 30"
+#: ./doc/common/tables/nova-common.xml35(td)
+msgid "(StrOpt) The topic console auth proxy nodes listen on"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml24(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml24(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml24(td)
-msgid "Seconds to attempt bind before giving up"
-msgstr ""
+#: ./doc/common/tables/nova-common.xml39(td)
+#: ./doc/common/tables/cinder-common.xml43(td)
+#: ./doc/common/tables/heat-debug.xml31(td)
+#: ./doc/common/tables/glance-common.xml47(td)
+#: ./doc/common/tables/neutron-common.xml123(td)
+#: ./doc/common/tables/trove-debug.xml35(td)
+#: ./doc/common/tables/keystone-debug.xml31(td)
+msgid "(BoolOpt) Whether to disable inter-process locks"
+msgstr "(BoolOpt) Faut-il désactiver les verrouillages inter-processus"
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml27(td)
-#: ./doc/common/tables/heat-cfn_api.xml33(td)
-#: ./doc/common/tables/trove-debug.xml26(td)
-#: ./doc/common/tables/neutron-wsgi.xml22(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml27(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml27(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml29(td)
-#: ./doc/common/tables/glance-common.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml27(td)
-#: ./doc/common/tables/heat-api.xml103(td)
-msgid "backlog = 4096"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml27(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml27(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml27(td)
-msgid "Maximum number of allowed pending TCP connections"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml30(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml21(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml30(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml33(td)
-msgid "user = swift"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml30(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml21(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml30(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml33(td)
-msgid "User to run as"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml33(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml18(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml33(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml33(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml45(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml30(td)
-msgid "swift_dir = /etc/swift"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml33(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml18(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml33(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml33(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml45(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml30(td)
-msgid "Swift configuration directory"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml36(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml36(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml36(td)
-msgid "devices = /srv/node"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml36(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml36(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml36(td)
-msgid "Parent directory of where devices are mounted"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml39(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml39(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml39(td)
-msgid "mount_check = true"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml39(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml39(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml39(td)
+#: ./doc/common/tables/nova-common.xml43(td)
 msgid ""
-"Whether or not check if the devices are mounted to prevent accidentally "
-"writing to the root device"
+"(StrOpt) Name of this node. This can be an opaque identifier. It is not "
+"necessarily a hostname, FQDN, or IP address. However, the node name must be "
+"valid within an AMQP key, and if using ZeroMQ, a valid hostname, FQDN, or IP"
+" address"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml42(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml42(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml42(td)
-msgid "disable_fallocate = false"
+#: ./doc/common/tables/nova-common.xml54(td)
+#: ./doc/common/tables/cinder-common.xml118(td)
+msgid "my_ip = 10.0.0.1"
+msgstr "my_ip = 10.0.0.1"
+
+#: ./doc/common/tables/nova-common.xml55(td)
+msgid "(StrOpt) IP address of this host"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml42(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml42(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml42(td)
+#: ./doc/common/tables/nova-common.xml59(td)
+#: ./doc/common/tables/keystone-amqp.xml39(td)
+#: ./doc/common/tables/glance-amqp.xml31(td)
+#: ./doc/common/tables/cinder-rpc.xml75(td)
+msgid "(MultiStrOpt) Driver or drivers to handle sending notifications."
+msgstr ""
+
+#: ./doc/common/tables/nova-common.xml63(td)
+#: ./doc/common/tables/keystone-amqp.xml43(td)
+#: ./doc/common/tables/glance-amqp.xml35(td)
+#: ./doc/common/tables/cinder-rpc.xml79(td)
+msgid "(ListOpt) AMQP topic used for OpenStack notifications."
+msgstr ""
+
+#: ./doc/common/tables/nova-common.xml66(td)
+msgid "notify_api_faults = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-common.xml67(td)
 msgid ""
-"Disable \"fast fail\" fallocate checks if the underlying filesystem does not"
-" support it."
+"(BoolOpt) If set, send api.fault notifications on caught exceptions in the "
+"API service."
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml45(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml51(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml45(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml45(td)
-msgid "workers = auto"
+#: ./doc/common/tables/nova-common.xml70(td)
+msgid "notify_on_state_change = None"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml45(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml51(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml45(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml45(td)
+#: ./doc/common/tables/nova-common.xml71(td)
 msgid ""
-"a much higher value, one can reduce the impact of slow file system "
-"operations in one request from negatively impacting other requests."
+"(StrOpt) If set, send compute.instance.update notifications on instance "
+"state changes. Valid values are None for no notifications, \"vm_state\" for "
+"notifications on VM state changes, or \"vm_and_task_state\" for "
+"notifications on VM and task state changes."
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml48(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml54(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml48(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml48(td)
-msgid "max_clients = 1024"
+#: ./doc/common/tables/nova-common.xml78(td)
+msgid "pybasedir = /usr/lib/python/site-packages"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml48(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml54(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml48(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml48(td)
+#: ./doc/common/tables/nova-common.xml79(td)
+msgid "(StrOpt) Directory where the nova python module is installed"
+msgstr ""
+
+#: ./doc/common/tables/nova-common.xml82(td)
+#: ./doc/common/tables/cinder-common.xml146(td)
+#: ./doc/common/tables/trove-rpc.xml46(td)
+msgid "report_interval = 10"
+msgstr "report_interval = 10"
+
+#: ./doc/common/tables/nova-common.xml83(td)
+msgid "(IntOpt) Seconds between nodes reporting state to datastore"
+msgstr ""
+
+#: ./doc/common/tables/nova-common.xml86(td)
+msgid "rootwrap_config = /etc/nova/rootwrap.conf"
+msgstr "rootwrap_config = /etc/nova/rootwrap.conf"
+
+#: ./doc/common/tables/nova-common.xml87(td)
+#: ./doc/common/tables/cinder-common.xml155(td)
 msgid ""
-"Maximum number of clients one worker can process simultaneously Lowering the"
-" number of clients handled per worker, and raising the number of workers can"
-" lessen the impact that a CPU intensive, or blocking, request can have on "
-"other requests served by the same worker. If the maximum number of clients "
-"is set to one, then a given worker will not perform another call while "
-"processing, allowing other workers a chance to process it."
+"(StrOpt) Path to the rootwrap configuration file to use for running commands"
+" as root"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml58(td)
-msgid "allowed_sync_hosts = 127.0.0.1"
+#: ./doc/common/tables/nova-common.xml90(td)
+#: ./doc/common/tables/cinder-common.xml162(td)
+msgid "service_down_time = 60"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml61(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml24(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml64(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml58(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml70(td)
-msgid "log_name = swift"
+#: ./doc/common/tables/nova-common.xml91(td)
+msgid "(IntOpt) Maximum time since last check-in for up service"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml61(td)
-#: ./doc/common/tables/swift-container-server-container-updater.xml18(td)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml18(td)
-#: ./doc/common/tables/swift-container-server-container-sync.xml18(td)
-#: ./doc/common/tables/swift-object-server-object-auditor.xml18(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml24(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml18(td)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml18(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml64(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml58(td)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml18(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml18(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml70(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml18(td)
-msgid "Label used when logging"
+#: ./doc/common/tables/nova-common.xml94(td)
+msgid "state_path = $pybasedir"
+msgstr "state_path = $pybasedir"
+
+#: ./doc/common/tables/nova-common.xml95(td)
+msgid "(StrOpt) Top-level directory for maintaining nova's state"
+msgstr "(StrOpt)  Répertoire de haut niveau pour maintenir l'état de nova"
+
+#: ./doc/common/tables/nova-common.xml98(td)
+msgid "tempdir = None"
+msgstr "tempdir = None"
+
+#: ./doc/common/tables/nova-common.xml99(td)
+msgid "(StrOpt) Explicitly specify the temporary working directory"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml64(td)
-#: ./doc/common/tables/swift-container-server-container-updater.xml21(td)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml21(td)
-#: ./doc/common/tables/swift-container-server-container-sync.xml21(td)
-#: ./doc/common/tables/swift-object-server-object-auditor.xml21(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml27(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml21(td)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml21(td)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml33(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml67(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml61(td)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml21(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml21(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml73(td)
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml21(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml21(td)
-msgid "log_facility = LOG_LOCAL0"
-msgstr ""
+#: ./doc/common/tables/nova-common.xml102(td)
+#: ./doc/common/tables/keystone-amqp.xml66(td)
+#: ./doc/common/tables/glance-amqp.xml54(td)
+#: ./doc/common/tables/cinder-rpc.xml230(td)
+msgid "transport_url = None"
+msgstr "transport_url = None"
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml67(td)
-#: ./doc/common/tables/swift-container-server-container-updater.xml24(td)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml24(td)
-#: ./doc/common/tables/swift-container-server-container-sync.xml24(td)
-#: ./doc/common/tables/swift-object-server-object-auditor.xml24(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml30(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml24(td)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml24(td)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml36(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml70(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml64(td)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml24(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml24(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml76(td)
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml24(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml24(td)
-msgid "log_level = INFO"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml67(td)
-#: ./doc/common/tables/swift-container-server-container-updater.xml24(td)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml24(td)
-#: ./doc/common/tables/swift-container-server-container-sync.xml24(td)
-#: ./doc/common/tables/swift-object-server-object-auditor.xml24(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml30(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml24(td)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml24(td)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml36(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml70(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml64(td)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml24(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml24(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml76(td)
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml24(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml24(td)
-msgid "Logging level"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml70(td)
-#: ./doc/common/tables/swift-container-server-container-updater.xml27(td)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml27(td)
-#: ./doc/common/tables/swift-container-server-container-sync.xml27(td)
-#: ./doc/common/tables/swift-object-server-object-auditor.xml27(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml33(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml27(td)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml27(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml73(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml67(td)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml27(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml27(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml82(td)
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml27(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml27(td)
-msgid "log_address = /dev/log"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml73(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml36(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml76(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml70(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml88(td)
-msgid "log_custom_handlers ="
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml73(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml36(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml76(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml70(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml88(td)
+#: ./doc/common/tables/nova-common.xml103(td)
+#: ./doc/common/tables/keystone-amqp.xml67(td)
+#: ./doc/common/tables/glance-amqp.xml55(td)
+#: ./doc/common/tables/cinder-rpc.xml231(td)
 msgid ""
-"Comma-separated list of functions to call to setup custom log handlers."
+"(StrOpt) A URL representing the messaging driver to use and its full "
+"configuration. If not set, we fall back to the rpc_backend option and driver"
+" specific configuration."
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml76(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml39(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml79(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml73(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml91(td)
-msgid "log_udp_host ="
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml7(literal)
+#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml7(literal)
+msgid "[app:proxy-server]"
+msgstr "[app:proxy-server]"
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml18(td)
+#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml18(td)
+msgid "use = egg:swift#proxy"
+msgstr "use = egg:swift#proxy"
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml21(td)
+msgid "set log_name = proxy-server"
+msgstr "set log_name = proxy-server"
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml33(td)
+msgid "log_handoffs = true"
+msgstr "log_handoffs = true"
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml36(td)
+msgid "recheck_account_existence = 60"
+msgstr "recheck_account_existence = 60"
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml36(td)
+msgid "Cache timeout in seconds to send memcached for account existence"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml76(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml39(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml79(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml73(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml91(td)
-msgid "If not set, the UDB receiver for syslog is disabled."
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml39(td)
+msgid "recheck_container_existence = 60"
+msgstr "recheck_container_existence = 60"
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml39(td)
+msgid "Cache timeout in seconds to send memcached for container existence"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml79(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml42(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml82(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml76(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml94(td)
-msgid "log_udp_port = 514"
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml42(td)
+msgid "object_chunk_size = 8192"
+msgstr "object_chunk_size = 8192"
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml42(td)
+msgid "Chunk size to read from object servers"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml79(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml42(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml82(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml76(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml94(td)
-msgid "Port value for UDB receiver, if enabled."
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml45(td)
+msgid "client_chunk_size = 8192"
+msgstr "client_chunk_size = 8192"
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml45(td)
+msgid "Chunk size to read from clients"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml82(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml45(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml85(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml79(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml97(td)
-msgid "log_statsd_host = localhost"
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml48(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml51(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml45(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml36(td)
+msgid "node_timeout = 10"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml82(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml45(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml85(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml79(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml97(td)
-msgid "If not set, the StatsD feature is disabled."
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml48(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml112(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml51(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml36(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml57(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml36(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml45(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml36(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml36(td)
+msgid "Request timeout to external services"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml85(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml48(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml88(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml82(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml100(td)
-msgid "log_statsd_port = 8125"
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml51(td)
+msgid "recoverable_node_timeout = node_timeout"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml85(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml48(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml88(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml82(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml100(td)
-msgid "Port value for the StatsD server."
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml88(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml51(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml91(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml85(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml103(td)
-msgid "log_statsd_default_sample_rate = 1.0"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml88(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml51(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml91(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml85(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml103(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml51(td)
 msgid ""
-"Defines the probability of sending a sample for any given event or timing "
-"measurement."
+"Request timeout to external services for requests that, on failure, can be "
+"recovered from. For example, object GET. from a client external services"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml92(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml55(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml95(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml89(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml107(td)
-msgid "log_statsd_sample_rate_factor = 1.0"
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml54(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml109(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml54(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml39(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml39(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml48(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml39(td)
+msgid "conn_timeout = 0.5"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml92(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml55(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml95(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml89(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml107(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml54(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml109(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml54(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml39(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml39(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml48(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml39(td)
+msgid "Connection timeout to external services"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml57(td)
+msgid "post_quorum_timeout = 0.5"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml60(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml45(td)
+msgid "error_suppression_interval = 60"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml60(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml45(td)
 msgid ""
-"Not recommended to set this to a value less than 1.0, if frequency of "
-"logging is too high, tune the log_statsd_default_sample_rate instead."
+"Time in seconds that must elapse since the last error for a node to be "
+"considered no longer error limited"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml97(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml60(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml100(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml94(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml112(td)
-msgid "log_statsd_metric_prefix ="
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml63(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml48(td)
+msgid "error_suppression_limit = 10"
+msgstr "error_suppression_limit = 10"
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml63(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml48(td)
+msgid "Error count to consider a node error limited"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml97(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml60(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml100(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml94(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml112(td)
-msgid "Value will be prepended to every metric sent to the StatsD server."
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml66(td)
+msgid "allow_account_management = false"
+msgstr "allow_account_management = false"
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml66(td)
+msgid "Whether account PUTs and DELETEs are even callable"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml100(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml97(td)
-msgid "db_preallocation = off"
-msgstr ""
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml69(td)
+msgid "object_post_as_copy = true"
+msgstr "object_post_as_copy = true"
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml100(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml97(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml69(td)
 msgid ""
-"If you don't mind the extra disk space usage in overhead, you can turn this "
-"on to preallocate disk space with SQLite databases to decrease "
-"fragmentation. underlying filesystem does not support it. to setup custom "
-"log handlers. bytes you'd like fallocate to reserve, whether there is space "
-"for the given file size or not. This is useful for systems that behave badly"
-" when they completely run out of space; you can make the services pretend "
-"they're out of space early. server. For most cases, this should be "
-"`egg:swift#account`. replication passes account can be reclaimed"
+"Set object_post_as_copy = false to turn on fast posts where only the "
+"metadata changes are stored anew and the original data file is kept in "
+"place. This makes for quicker posts; but since the container metadata isn't "
+"updated in this mode, features like container sync won't be able to sync "
+"posts."
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml103(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml103(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml100(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml121(td)
-msgid "eventlet_debug = false"
-msgstr ""
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml72(td)
+msgid "account_autocreate = false"
+msgstr "account_autocreate = false"
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml103(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml103(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml100(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml121(td)
-msgid "If true, turn on debug logging for eventlet"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml106(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml106(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml103(td)
-msgid "fallocate_reserve = 0"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml106(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml106(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml103(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml72(td)
 msgid ""
-"You can set fallocate_reserve to the number of bytes you'd like fallocate to"
-" reserve, whether there is space for the given file size or not. This is "
-"useful for systems that behave badly when they completely run out of space; "
-"you can make the services pretend they're out of space early. server. For "
-"most cases, this should be `egg:swift#object`."
+"If set to 'true' authorized accounts that do not yet exist within the Swift "
+"cluster will be automatically created."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml8(caption)
-msgid "Description of configuration options for ml2_bigswitch"
-msgstr ""
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml75(td)
+msgid "max_containers_per_account = 0"
+msgstr "max_containers_per_account = 0"
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml19(th)
-#: ./doc/common/tables/neutron-bigswitch.xml19(th)
-msgid "[NOVA]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml22(td)
-#: ./doc/common/tables/neutron-bigswitch.xml22(td)
-msgid "node_override_vif_802.1qbg ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml23(td)
-#: ./doc/common/tables/neutron-bigswitch.xml23(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to 802.1qbg"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml26(td)
-#: ./doc/common/tables/neutron-bigswitch.xml26(td)
-msgid "node_override_vif_802.1qbh ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml27(td)
-#: ./doc/common/tables/neutron-bigswitch.xml27(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to 802.1qbh"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml30(td)
-#: ./doc/common/tables/neutron-bigswitch.xml30(td)
-msgid "node_override_vif_binding_failed ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml31(td)
-#: ./doc/common/tables/neutron-bigswitch.xml31(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml75(td)
 msgid ""
-"(ListOpt) Nova compute nodes to manually set VIF type to binding_failed"
+"If set to a positive value, trying to create a container when the account "
+"already has at least this maximum containers will result in a 403 Forbidden."
+" Note: This is a soft limit, meaning a user might exceed the cap for "
+"recheck_account_existence before the 403s kick in."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml34(td)
-#: ./doc/common/tables/neutron-bigswitch.xml34(td)
-msgid "node_override_vif_bridge ="
-msgstr ""
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml78(td)
+msgid "max_containers_whitelist ="
+msgstr "max_containers_whitelist ="
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml35(td)
-#: ./doc/common/tables/neutron-bigswitch.xml35(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to bridge"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml38(td)
-#: ./doc/common/tables/neutron-bigswitch.xml38(td)
-msgid "node_override_vif_hostdev ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml39(td)
-#: ./doc/common/tables/neutron-bigswitch.xml39(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to hostdev"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml42(td)
-#: ./doc/common/tables/neutron-bigswitch.xml42(td)
-msgid "node_override_vif_hyperv ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml43(td)
-#: ./doc/common/tables/neutron-bigswitch.xml43(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to hyperv"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml46(td)
-#: ./doc/common/tables/neutron-bigswitch.xml46(td)
-msgid "node_override_vif_ivs ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml47(td)
-#: ./doc/common/tables/neutron-bigswitch.xml47(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to ivs"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml50(td)
-#: ./doc/common/tables/neutron-bigswitch.xml50(td)
-msgid "node_override_vif_midonet ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml51(td)
-#: ./doc/common/tables/neutron-bigswitch.xml51(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to midonet"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml54(td)
-#: ./doc/common/tables/neutron-bigswitch.xml54(td)
-msgid "node_override_vif_mlnx_direct ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml55(td)
-#: ./doc/common/tables/neutron-bigswitch.xml55(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to mlnx_direct"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml58(td)
-#: ./doc/common/tables/neutron-bigswitch.xml58(td)
-msgid "node_override_vif_other ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml59(td)
-#: ./doc/common/tables/neutron-bigswitch.xml59(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to other"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml62(td)
-#: ./doc/common/tables/neutron-bigswitch.xml62(td)
-msgid "node_override_vif_ovs ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml63(td)
-#: ./doc/common/tables/neutron-bigswitch.xml63(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to ovs"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml66(td)
-#: ./doc/common/tables/neutron-bigswitch.xml66(td)
-msgid "node_override_vif_unbound ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml67(td)
-#: ./doc/common/tables/neutron-bigswitch.xml67(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to unbound"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml70(td)
-#: ./doc/common/tables/neutron-bigswitch.xml70(td)
-msgid "vif_type = ovs"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml71(td)
-#: ./doc/common/tables/neutron-bigswitch.xml71(td)
-msgid "(StrOpt) Virtual interface type to configure on Nova compute nodes"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml74(td)
-#: ./doc/common/tables/neutron-bigswitch.xml74(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml78(td)
 msgid ""
-"vif_types = unbound, binding_failed, ovs, ivs, bridge, 802.1qbg, 802.1qbh, "
-"hyperv, midonet, mlnx_direct, hostdev, other"
+"is a comma separated list of account names that ignore the "
+"max_containers_per_account cap."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml75(td)
-#: ./doc/common/tables/neutron-bigswitch.xml75(td)
-msgid "(ListOpt) List of allowed vif_type values."
-msgstr ""
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml81(td)
+msgid "deny_host_headers ="
+msgstr "deny_host_headers ="
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml78(th)
-#: ./doc/common/tables/neutron-bigswitch.xml78(th)
-#: ./doc/common/tables/neutron-nuage.xml19(th)
-msgid "[RESTPROXY]"
-msgstr ""
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml84(td)
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml21(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml54(td)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml36(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml45(td)
+msgid "auto_create_account_prefix = ."
+msgstr "auto_create_account_prefix = ."
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml81(td)
-#: ./doc/common/tables/neutron-bigswitch.xml81(td)
-msgid "add_meta_server_route = True"
-msgstr ""
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml84(td)
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml21(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml54(td)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml36(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml45(td)
+msgid "Prefix to use when automatically creating accounts"
+msgstr "Préfixe à utiliser avec la création automatique des comptes"
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml82(td)
-#: ./doc/common/tables/neutron-bigswitch.xml82(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml87(td)
+msgid "put_queue_depth = 10"
+msgstr "put_queue_depth = 10"
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml90(td)
+msgid "sorting_method = shuffle"
+msgstr "sorting_method = shuffle"
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml93(td)
+msgid "timing_expiry = 300"
+msgstr "timing_expiry = 300"
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml96(td)
+msgid "max_large_object_get_time = 86400"
+msgstr "max_large_object_get_time = 86400"
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml99(td)
+msgid "request_node_count = 2 * replicas"
+msgstr "request_node_count = 2 * replicas"
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml99(td)
 msgid ""
-"(BoolOpt) Flag to decide if a route to the metadata server should be "
-"injected into the VM"
+"* replicas Set to the number of nodes to contact for a normal request. You "
+"can use '* replicas' at the end to have it use the number given times the "
+"number of replicas for the ring being used for the request. conf file for "
+"values will only be shown to the list of swift_owners. The exact default "
+"definition of a swift_owner is headers&gt; up to the auth system in use, but"
+" usually indicates administrative responsibilities. paste.deploy to use for "
+"auth. To use tempauth set to: `egg:swift#tempauth` each request"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml85(td)
-#: ./doc/common/tables/neutron-bigswitch.xml85(td)
-msgid "auto_sync_on_failure = True"
-msgstr ""
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml102(td)
+msgid "read_affinity = r1z1=100, r1z2=200, r2=300"
+msgstr "read_affinity = r1z1=100, r1z2=200, r2=300"
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml86(td)
-#: ./doc/common/tables/neutron-bigswitch.xml86(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml105(td)
+msgid "read_affinity ="
+msgstr "read_affinity ="
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml108(td)
+msgid "write_affinity = r1, r2"
+msgstr "write_affinity = r1, r2"
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml111(td)
+msgid "write_affinity ="
+msgstr "write_affinity ="
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml114(td)
+msgid "write_affinity_node_count = 2 * replicas"
+msgstr "write_affinity_node_count = 2 * replicas"
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml117(td)
 msgid ""
-"(BoolOpt) If neutron fails to create a resource because the backend "
-"controller doesn't know of a dependency, the plugin automatically triggers a"
-" full data synchronization to the controller."
+"swift_owner_headers = x-container-read, x-container-write, x-container-sync-"
+"key, x-container-sync-to, x-account-meta-temp-url-key, x-account-meta-temp-"
+"url-key-2, x-account-access-control"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml89(td)
-#: ./doc/common/tables/neutron-bigswitch.xml89(td)
-msgid "cache_connections = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml90(td)
-#: ./doc/common/tables/neutron-bigswitch.xml90(td)
-msgid "(BoolOpt) Re-use HTTP/HTTPS connections to the controller."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml93(td)
-#: ./doc/common/tables/neutron-bigswitch.xml93(td)
-msgid "consistency_interval = 60"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml94(td)
-#: ./doc/common/tables/neutron-bigswitch.xml94(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml117(td)
 msgid ""
-"(IntOpt) Time between verifications that the backend controller database is "
-"consistent with Neutron"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml97(td)
-#: ./doc/common/tables/neutron-bigswitch.xml97(td)
-msgid "neutron_id = neutron-oslo"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml98(td)
-#: ./doc/common/tables/neutron-bigswitch.xml98(td)
-msgid "(StrOpt) User defined identifier for this Neutron deployment"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml101(td)
-#: ./doc/common/tables/neutron-bigswitch.xml101(td)
-msgid "no_ssl_validation = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml102(td)
-#: ./doc/common/tables/neutron-bigswitch.xml102(td)
-msgid "(BoolOpt) Disables SSL certificate validation for controllers"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml105(td)
-#: ./doc/common/tables/neutron-bigswitch.xml105(td)
-msgid "server_auth = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml106(td)
-#: ./doc/common/tables/neutron-bigswitch.xml106(td)
-msgid ""
-"(StrOpt) The username and password for authenticating against the Big Switch"
-" or Floodlight controller."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml109(td)
-#: ./doc/common/tables/neutron-bigswitch.xml109(td)
-msgid "server_ssl = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml110(td)
-#: ./doc/common/tables/neutron-bigswitch.xml110(td)
-msgid ""
-"(BoolOpt) If True, Use SSL when connecting to the Big Switch or Floodlight "
-"controller."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml113(td)
-#: ./doc/common/tables/neutron-bigswitch.xml113(td)
-msgid "server_timeout = 10"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml114(td)
-#: ./doc/common/tables/neutron-bigswitch.xml114(td)
-msgid ""
-"(IntOpt) Maximum number of seconds to wait for proxy request to connect and "
-"complete."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml117(td)
-#: ./doc/common/tables/neutron-bigswitch.xml117(td)
-msgid "servers = localhost:8800"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml118(td)
-#: ./doc/common/tables/neutron-bigswitch.xml118(td)
-msgid ""
-"(ListOpt) A comma separated list of Big Switch or Floodlight servers and "
-"port numbers. The plugin proxies the requests to the Big Switch/Floodlight "
-"server, which performs the networking configuration. Only oneserver is "
-"needed per deployment, but you may wish todeploy multiple servers to support"
-" failover."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml121(td)
-#: ./doc/common/tables/neutron-bigswitch.xml121(td)
-msgid "ssl_cert_directory = /etc/neutron/plugins/bigswitch/ssl"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml122(td)
-#: ./doc/common/tables/neutron-bigswitch.xml122(td)
-msgid ""
-"(StrOpt) Directory containing ca_certs and host_certs certificate "
-"directories."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml125(td)
-#: ./doc/common/tables/neutron-bigswitch.xml125(td)
-msgid "ssl_sticky = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml126(td)
-#: ./doc/common/tables/neutron-bigswitch.xml126(td)
-msgid ""
-"(BoolOpt) Trust and store the first certificate received for each controller"
-" address and use it to validate future connections to that address."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml129(td)
-#: ./doc/common/tables/neutron-bigswitch.xml129(td)
-msgid "sync_data = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml130(td)
-#: ./doc/common/tables/neutron-bigswitch.xml130(td)
-msgid "(BoolOpt) Sync data on connect"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml133(td)
-#: ./doc/common/tables/neutron-bigswitch.xml133(td)
-msgid "thread_pool_size = 4"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml134(td)
-#: ./doc/common/tables/neutron-bigswitch.xml134(td)
-msgid ""
-"(IntOpt) Maximum number of threads to spawn to handle large volumes of port "
-"creations."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml137(th)
-#: ./doc/common/tables/neutron-bigswitch.xml137(th)
-msgid "[RESTPROXYAGENT]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml140(td)
-#: ./doc/common/tables/neutron-openvswitch_agent.xml83(td)
-#: ./doc/common/tables/neutron-bigswitch.xml140(td)
-#: ./doc/common/tables/neutron-cisco.xml73(td)
-#: ./doc/common/tables/nova-vmware.xml46(td)
-#: ./doc/common/tables/neutron-nvsd.xml22(td)
-msgid "integration_bridge = br-int"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml141(td)
-#: ./doc/common/tables/neutron-bigswitch.xml141(td)
-msgid ""
-"(StrOpt) Name of integration bridge on compute nodes used for security group"
-" insertion."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml144(td)
-#: ./doc/common/tables/neutron-bigswitch.xml144(td)
-msgid "polling_interval = 5"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml145(td)
-#: ./doc/common/tables/neutron-bigswitch.xml145(td)
-msgid "(IntOpt) Seconds between agent checks for port changes"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml148(td)
-#: ./doc/common/tables/neutron-bigswitch.xml148(td)
-msgid "virtual_switch_type = ovs"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml149(td)
-#: ./doc/common/tables/neutron-bigswitch.xml149(td)
-msgid "(StrOpt) Virtual switch type."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml152(th)
-#: ./doc/common/tables/neutron-bigswitch.xml152(th)
-msgid "[ROUTER]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml155(td)
-#: ./doc/common/tables/neutron-bigswitch.xml155(td)
-msgid "max_router_rules = 200"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml156(td)
-#: ./doc/common/tables/neutron-bigswitch.xml156(td)
-msgid "(IntOpt) Maximum number of router rules"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml159(td)
-#: ./doc/common/tables/neutron-bigswitch.xml159(td)
-msgid "tenant_default_router_rule = ['*:any:any:permit']"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml160(td)
-#: ./doc/common/tables/neutron-bigswitch.xml160(td)
-msgid ""
-"(MultiStrOpt) The default router rules installed in new tenant routers. "
-"Repeat the config option for each rule. Format is "
-"&lt;tenant&gt;:&lt;source&gt;:&lt;destination&gt;:&lt;action&gt; Use an * to"
-" specify default for all tenants."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_gre.xml8(caption)
-msgid "Description of configuration options for ml2_gre"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_gre.xml19(th)
-msgid "[ml2_type_gre]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_gre.xml22(td)
-#: ./doc/common/tables/neutron-openvswitch_agent.xml107(td)
-msgid "tunnel_id_ranges ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_gre.xml23(td)
-msgid ""
-"(ListOpt) Comma-separated list of &lt;tun_min&gt;:&lt;tun_max&gt; tuples "
-"enumerating ranges of GRE tunnel IDs that are available for tenant network "
-"allocation"
+"the sample These are the headers whose conf file for values will only be "
+"shown to the list of swift_owners. The exact default definition of a "
+"swift_owner is headers&gt; up to the auth system in use, but usually "
+"indicates administrative responsibilities. paste.deploy to use for auth. To "
+"use tempauth set to: `egg:swift#tempauth` each request"
 msgstr ""
 
 #: ./doc/common/tables/nova-volumes.xml8(caption)
@@ -28536,13 +35474,6 @@ msgstr ""
 msgid "(IntOpt) Number of cinderclient retries on failed http calls"
 msgstr ""
 
-#: ./doc/common/tables/nova-volumes.xml46(td)
-#: ./doc/common/tables/cinder-compute.xml46(td)
-#: ./doc/common/tables/glance-common.xml82(td)
-#: ./doc/common/tables/ceilometer-auth.xml156(td)
-msgid "os_region_name = None"
-msgstr ""
-
 #: ./doc/common/tables/nova-volumes.xml47(td)
 msgid "(StrOpt) Region name of this node"
 msgstr ""
@@ -28565,8 +35496,8 @@ msgid "(IntOpt) Interval in seconds for gathering volume usages"
 msgstr ""
 
 #: ./doc/common/tables/nova-volumes.xml58(th)
-#: ./doc/common/tables/nova-tilera.xml19(th)
 #: ./doc/common/tables/nova-baremetal.xml19(th)
+#: ./doc/common/tables/nova-tilera.xml19(th)
 msgid "[baremetal]"
 msgstr "[baremetal]"
 
@@ -28617,14 +35548,6 @@ msgstr ""
 msgid "(IntOpt) Interval between volume attachment attempts, in seconds"
 msgstr ""
 
-#: ./doc/common/tables/nova-volumes.xml84(th)
-#: ./doc/common/tables/nova-hypervisor.xml54(th)
-#: ./doc/common/tables/nova-livemigration.xml26(th)
-#: ./doc/common/tables/nova-libvirt.xml30(th)
-#: ./doc/common/tables/nova-xen.xml58(th)
-msgid "[libvirt]"
-msgstr ""
-
 #: ./doc/common/tables/nova-volumes.xml87(td)
 #: ./doc/common/tables/cinder-storage_glusterfs.xml22(td)
 msgid "glusterfs_mount_point_base = $state_path/mnt"
@@ -28689,20 +35612,10 @@ msgid ""
 "Currently supported protocols: [gluster]"
 msgstr ""
 
-#: ./doc/common/tables/nova-volumes.xml115(td)
-#: ./doc/common/tables/cinder-storage_ceph.xml38(td)
-msgid "rbd_secret_uuid = None"
-msgstr ""
-
 #: ./doc/common/tables/nova-volumes.xml116(td)
 msgid "(StrOpt) The libvirt UUID of the secret for the rbd_uservolumes"
 msgstr ""
 
-#: ./doc/common/tables/nova-volumes.xml119(td)
-#: ./doc/common/tables/cinder-storage_ceph.xml42(td)
-msgid "rbd_user = None"
-msgstr ""
-
 #: ./doc/common/tables/nova-volumes.xml120(td)
 msgid "(StrOpt) The RADOS client name for accessing rbd volumes"
 msgstr ""
@@ -28727,12 +35640,6 @@ msgstr ""
 msgid "(StrOpt) Base dir where Scality SOFS shall be mounted"
 msgstr ""
 
-#: ./doc/common/tables/nova-volumes.xml131(th)
-#: ./doc/common/tables/nova-xen.xml65(th)
-#: ./doc/common/tables/nova-baremetal.xml130(th)
-msgid "[xenserver]"
-msgstr ""
-
 #: ./doc/common/tables/nova-volumes.xml134(td)
 msgid "block_device_creation_timeout = 10"
 msgstr ""
@@ -28741,1725 +35648,453 @@ msgstr ""
 msgid "(IntOpt) Time to wait for a block device to be created"
 msgstr ""
 
-#: ./doc/common/tables/glance-gridfs.xml8(caption)
-msgid "Description of configuration options for gridfs"
+#: ./doc/common/tables/neutron-redis.xml23(td)
+msgid "(StrOpt) The hostname Neutron is running on"
 msgstr ""
 
-#: ./doc/common/tables/glance-gridfs.xml22(td)
-msgid "mongodb_store_db = None"
+#: ./doc/common/tables/trove-db_mysql.xml8(caption)
+msgid "Description of configuration options for db_mysql"
 msgstr ""
 
-#: ./doc/common/tables/glance-gridfs.xml23(td)
-msgid "(StrOpt) Database to use."
+#: ./doc/common/tables/trove-db_mysql.xml19(th)
+msgid "[mysql]"
+msgstr "[mysql]"
+
+#: ./doc/common/tables/trove-db_mysql.xml42(td)
+msgid "usage_timeout = 400"
 msgstr ""
 
-#: ./doc/common/tables/glance-gridfs.xml26(td)
-msgid "mongodb_store_uri = None"
+#: ./doc/common/tables/heat-zeromq.xml27(td)
+#: ./doc/common/tables/neutron-zeromq.xml27(td)
+#: ./doc/common/tables/ceilometer-rpc.xml55(td)
+#: ./doc/common/tables/trove-zeromq.xml27(td)
+msgid "(IntOpt) Number of ZeroMQ contexts, defaults to 1"
 msgstr ""
 
-#: ./doc/common/tables/glance-gridfs.xml27(td)
+#: ./doc/common/tables/heat-zeromq.xml35(td)
+#: ./doc/common/tables/neutron-zeromq.xml35(td)
+#: ./doc/common/tables/ceilometer-rpc.xml63(td)
+#: ./doc/common/tables/trove-zeromq.xml35(td)
+msgid "(StrOpt) Directory for holding IPC sockets"
+msgstr ""
+
+#: ./doc/common/tables/heat-zeromq.xml38(td)
 msgid ""
-"(StrOpt) Hostname or IP address of the instance to connect to, or a mongodb "
-"URI, or a list of hostnames / mongodb URIs. If host is an IPv6 literal it "
-"must be enclosed in '[' and ']' characters following the RFC2732 URL syntax "
-"(e.g. '[::1]' for localhost)."
+"rpc_zmq_matchmaker = "
+"heat.openstack.common.rpc.matchmaker.MatchMakerLocalhost"
+msgstr "rpc_zmq_matchmaker = heat.openstack.common.rpc.matchmaker.MatchMakerLocalhost"
+
+#: ./doc/common/tables/heat-zeromq.xml39(td)
+#: ./doc/common/tables/neutron-zeromq.xml39(td)
+#: ./doc/common/tables/ceilometer-rpc.xml67(td)
+#: ./doc/common/tables/trove-zeromq.xml39(td)
+msgid "(StrOpt) MatchMaker driver"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml8(caption)
-msgid "Description of configuration options for ml2_arista"
+#: ./doc/common/tables/heat-zeromq.xml43(td)
+#: ./doc/common/tables/neutron-zeromq.xml43(td)
+#: ./doc/common/tables/ceilometer-rpc.xml71(td)
+#: ./doc/common/tables/trove-zeromq.xml43(td)
+msgid "(IntOpt) ZeroMQ receiver listening port"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml19(th)
-msgid "[ml2_arista]"
-msgstr ""
+#: ./doc/common/tables/heat-amqp.xml30(td)
+msgid "control_exchange = heat"
+msgstr "control_exchange = heat"
 
-#: ./doc/common/tables/neutron-ml2_arista.xml22(td)
-msgid "eapi_host ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_arista.xml23(td)
+#: ./doc/common/tables/heat-amqp.xml46(td)
 msgid ""
-"(StrOpt) Arista EOS IP address. This is required field.If not set, all "
-"communications to Arista EOSwill fail"
+"list_notifier_drivers = ['heat.openstack.common.notifier.no_op_notifier']"
+msgstr "list_notifier_drivers = ['heat.openstack.common.notifier.no_op_notifier']"
+
+#: ./doc/common/tables/heat-amqp.xml47(td)
+msgid "(MultiStrOpt) List of drivers to send notifications"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml26(td)
-msgid "eapi_password ="
+#: ./doc/common/tables/heat-amqp.xml55(td)
+#: ./doc/common/tables/ceilometer-amqp.xml35(td)
+msgid "(ListOpt) AMQP topic used for OpenStack notifications"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml27(td)
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml8(caption)
+msgid "Description of configuration options for linuxbridge_agent"
+msgstr ""
+
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml19(th)
+msgid "[LINUX_BRIDGE]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml22(td)
+#: ./doc/common/tables/neutron-mlnx.xml30(td)
+msgid "physical_interface_mappings ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml23(td)
+#: ./doc/common/tables/neutron-mlnx.xml31(td)
+msgid "(ListOpt) List of &lt;physical_network&gt;:&lt;physical_interface&gt;"
+msgstr ""
+
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml26(th)
+msgid "[VLANS]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml34(td)
+#: ./doc/common/tables/neutron-mlnx.xml54(td)
+msgid "(StrOpt) Network type for tenant networks (local, vlan, or none)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml37(th)
+msgid "[VXLAN]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml40(td)
+msgid "enable_vxlan = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml41(td)
 msgid ""
-"(StrOpt) Password for Arista EOS. This is required field.if not set, all "
-"communications to Arista EOSwill fail"
+"(BoolOpt) Enable VXLAN on the agent. Can be enabled when agent is managed by"
+" ml2 plugin using linuxbridge mechanism driver"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml30(td)
-msgid "eapi_username ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_arista.xml31(td)
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml45(td)
 msgid ""
-"(StrOpt) Username for Arista EOS. This is required field.if not set, all "
-"communications to Arista EOSwill fail"
+"(BoolOpt) Extension to use alongside ml2 plugin's l2population mechanism "
+"driver. It enables the plugin to populate VXLAN forwarding table."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml34(td)
-msgid "region_name = RegionOne"
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml49(td)
+msgid "(StrOpt) Local IP address of the VXLAN endpoints."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml35(td)
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml52(td)
+msgid "tos = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml53(td)
+msgid "(IntOpt) TOS for vxlan interface protocol packets."
+msgstr ""
+
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml56(td)
+msgid "ttl = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml57(td)
+msgid "(IntOpt) TTL for vxlan interface protocol packets."
+msgstr ""
+
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml60(td)
+msgid "vxlan_group = 224.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml61(td)
+msgid "(StrOpt) Multicast group for vxlan interface."
+msgstr ""
+
+#: ./doc/common/tables/nova-redis.xml23(td)
+#: ./doc/common/tables/glance-redis.xml27(td)
+#: ./doc/common/tables/cinder-rpc.xml83(td)
+#: ./doc/common/tables/keystone-redis.xml35(td)
+msgid "(StrOpt) Password for Redis server (optional)."
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml21(td)
+msgid "bind_port = 6001"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml36(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml36(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml36(td)
+msgid "devices = /srv/node"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml36(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml36(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml36(td)
+msgid "Parent directory of where devices are mounted"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml39(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml39(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml39(td)
+msgid "mount_check = true"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml39(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml39(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml39(td)
 msgid ""
-"(StrOpt) Defines Region Name that is assigned to this OpenStackController. "
-"This is useful when multipleOpenStack/Neutron controllers are managing the "
-"sameArista HW clusters. Note that this name must match withthe region name "
-"registered (or known) to keystoneservice. Authentication with Keysotne is "
-"performed byEOS. This is optional. If not set, a value of\"RegionOne\" is "
-"assumed"
+"Whether or not check if the devices are mounted to prevent accidentally "
+"writing to the root device"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml38(td)
-msgid "sync_interval = 180"
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml42(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml42(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml42(td)
+msgid "disable_fallocate = false"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml39(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml42(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml42(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml42(td)
 msgid ""
-"(IntOpt) Sync interval in seconds between Neutron plugin andEOS. This "
-"interval defines how often thesynchronization is performed. This is an "
-"optionalfield. If not set, a value of 180 seconds is assumed"
+"Disable \"fast fail\" fallocate checks if the underlying filesystem does not"
+" support it."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml42(td)
-msgid "use_fqdn = True"
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml58(td)
+msgid "allowed_sync_hosts = 127.0.0.1"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml43(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml100(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml97(td)
+msgid "db_preallocation = off"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml100(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml97(td)
 msgid ""
-"(BoolOpt) Defines if hostnames are sent to Arista EOS as "
-"FQDNs(\"node1.domain.com\") or as short names (\"node1\").This is optional. "
-"If not set, a value of \"True\"is assumed."
+"If you don't mind the extra disk space usage in overhead, you can turn this "
+"on to preallocate disk space with SQLite databases to decrease "
+"fragmentation. underlying filesystem does not support it. to setup custom "
+"log handlers. bytes you'd like fallocate to reserve, whether there is space "
+"for the given file size or not. This is useful for systems that behave badly"
+" when they completely run out of space; you can make the services pretend "
+"they're out of space early. server. For most cases, this should be "
+"`egg:swift#account`. replication passes account can be reclaimed"
 msgstr ""
 
-#: ./doc/common/tables/glance-filesystem.xml8(caption)
-msgid "Description of configuration options for filesystem"
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml106(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml106(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml103(td)
+msgid "fallocate_reserve = 0"
 msgstr ""
 
-#: ./doc/common/tables/glance-filesystem.xml22(td)
-msgid "filesystem_store_datadir = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-filesystem.xml23(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml106(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml106(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml103(td)
 msgid ""
-"(StrOpt) Directory to which the Filesystem backend store writes images."
+"You can set fallocate_reserve to the number of bytes you'd like fallocate to"
+" reserve, whether there is space for the given file size or not. This is "
+"useful for systems that behave badly when they completely run out of space; "
+"you can make the services pretend they're out of space early. server. For "
+"most cases, this should be `egg:swift#object`."
 msgstr ""
 
-#: ./doc/common/tables/glance-filesystem.xml26(td)
-msgid "filesystem_store_datadirs = None"
+#: ./doc/common/tables/nova-db.xml8(caption)
+#: ./doc/common/tables/glance-db.xml8(caption)
+#: ./doc/common/tables/neutron-db.xml8(caption)
+msgid "Description of configuration options for db"
 msgstr ""
 
-#: ./doc/common/tables/glance-filesystem.xml27(td)
+#: ./doc/common/tables/nova-db.xml22(td)
+msgid "db_driver = nova.db"
+msgstr "db_driver = nova.db"
+
+#: ./doc/common/tables/nova-db.xml23(td)
+msgid "(StrOpt) The driver to use for database access"
+msgstr ""
+
+#: ./doc/common/tables/nova-db.xml26(th)
+#: ./doc/common/tables/ceilometer-cells.xml19(th)
+#: ./doc/common/tables/nova-upgrade_levels.xml19(th)
+#: ./doc/common/tables/nova-cells.xml19(th)
+#: ./doc/common/tables/nova-rpc_all.xml198(th)
+#: ./doc/common/tables/nova-scheduling.xml118(th)
+#: ./doc/common/tables/nova-quota.xml82(th)
+#: ./doc/common/tables/nova-rpc.xml62(th)
+msgid "[cells]"
+msgstr "[cells]"
+
+#: ./doc/common/tables/nova-db.xml29(td)
+msgid "db_check_interval = 60"
+msgstr "db_check_interval = 60"
+
+#: ./doc/common/tables/nova-db.xml30(td)
 msgid ""
-"(MultiStrOpt) List of directories and its priorities to which the Filesystem"
-" backend store writes images."
+"(IntOpt) Interval, in seconds, for getting fresh cell information from the "
+"database."
 msgstr ""
 
-#: ./doc/common/tables/glance-filesystem.xml30(td)
-msgid "filesystem_store_metadata_file = None"
+#: ./doc/common/tables/nova-db.xml40(td)
+#: ./doc/common/tables/glance-db.xml26(td)
+#: ./doc/common/tables/keystone-database.xml26(td)
+msgid "connection = None"
 msgstr ""
 
-#: ./doc/common/tables/glance-filesystem.xml31(td)
+#: ./doc/common/tables/nova-db.xml52(td)
+#: ./doc/common/tables/glance-db.xml38(td)
+#: ./doc/common/tables/neutron-db.xml49(td)
+#: ./doc/common/tables/keystone-database.xml38(td)
+msgid "db_inc_retry_interval = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-db.xml53(td)
+#: ./doc/common/tables/glance-db.xml39(td)
+#: ./doc/common/tables/neutron-db.xml50(td)
+#: ./doc/common/tables/keystone-database.xml39(td)
 msgid ""
-"(StrOpt) The path to a file which contains the metadata to be returned with "
-"any location associated with this store. The file must contain a valid JSON "
-"dict."
+"(BoolOpt) Whether to increase interval between db connection retries, up to "
+"db_max_retry_interval"
 msgstr ""
 
-#: ./doc/common/tables/heat-redis.xml8(caption)
-#: ./doc/common/tables/trove-redis.xml8(caption)
-#: ./doc/common/tables/ceilometer-redis.xml8(caption)
-#: ./doc/common/tables/glance-redis.xml8(caption)
-#: ./doc/common/tables/neutron-redis.xml8(caption)
-#: ./doc/common/tables/keystone-redis.xml8(caption)
-#: ./doc/common/tables/nova-redis.xml8(caption)
-msgid "Description of configuration options for redis"
+#: ./doc/common/tables/nova-db.xml56(td)
+#: ./doc/common/tables/glance-db.xml42(td)
+#: ./doc/common/tables/neutron-db.xml53(td)
+#: ./doc/common/tables/keystone-database.xml42(td)
+msgid "db_max_retries = 20"
 msgstr ""
 
-#: ./doc/common/tables/heat-redis.xml22(td)
-#: ./doc/common/tables/nova-common.xml42(td)
-#: ./doc/common/tables/ceilometer-redis.xml22(td)
-#: ./doc/common/tables/cinder-common.xml58(td)
-#: ./doc/common/tables/neutron-redis.xml22(td)
-msgid "host = oslo"
-msgstr "host = oslo"
-
-#: ./doc/common/tables/heat-redis.xml23(td)
+#: ./doc/common/tables/nova-db.xml57(td)
+#: ./doc/common/tables/glance-db.xml43(td)
+#: ./doc/common/tables/neutron-db.xml54(td)
+#: ./doc/common/tables/keystone-database.xml43(td)
 msgid ""
-"(StrOpt) Name of the engine node. This can be an opaque identifier. It is "
-"not necessarily a hostname, FQDN, or IP address."
+"(IntOpt) maximum db connection retries before error is raised. (setting -1 "
+"implies an infinite retry count)"
 msgstr ""
 
-#: ./doc/common/tables/heat-redis.xml26(th)
-#: ./doc/common/tables/trove-redis.xml19(th)
-#: ./doc/common/tables/ceilometer-redis.xml34(th)
-#: ./doc/common/tables/neutron-redis.xml26(th)
-msgid "[matchmaker_redis]"
+#: ./doc/common/tables/nova-db.xml60(td)
+#: ./doc/common/tables/glance-db.xml46(td)
+#: ./doc/common/tables/neutron-db.xml57(td)
+#: ./doc/common/tables/keystone-database.xml46(td)
+msgid "db_max_retry_interval = 10"
 msgstr ""
 
-#: ./doc/common/tables/heat-redis.xml29(td)
-#: ./doc/common/tables/trove-redis.xml22(td)
-#: ./doc/common/tables/ceilometer-redis.xml37(td)
-#: ./doc/common/tables/glance-redis.xml22(td)
-#: ./doc/common/tables/neutron-redis.xml29(td)
-#: ./doc/common/tables/keystone-redis.xml22(td)
-#: ./doc/common/tables/neutron-nec.xml38(td)
-msgid "host = 127.0.0.1"
-msgstr ""
-
-#: ./doc/common/tables/heat-redis.xml30(td)
-#: ./doc/common/tables/trove-redis.xml23(td)
-#: ./doc/common/tables/ceilometer-redis.xml38(td)
-#: ./doc/common/tables/neutron-redis.xml30(td)
-msgid "(StrOpt) Host to locate redis"
-msgstr ""
-
-#: ./doc/common/tables/heat-redis.xml33(td)
-#: ./doc/common/tables/trove-redis.xml26(td)
-#: ./doc/common/tables/keystone-ldap.xml90(td)
-#: ./doc/common/tables/ceilometer-redis.xml41(td)
-#: ./doc/common/tables/cinder-rpc.xml82(td)
-#: ./doc/common/tables/glance-redis.xml26(td)
-#: ./doc/common/tables/neutron-redis.xml33(td)
-#: ./doc/common/tables/keystone-redis.xml34(td)
-#: ./doc/common/tables/neutron-ml2_odl.xml22(td)
-#: ./doc/common/tables/neutron-ml2_ncs.xml22(td)
-#: ./doc/common/tables/nova-redis.xml22(td)
-msgid "password = None"
-msgstr "password = None"
-
-#: ./doc/common/tables/heat-redis.xml34(td)
-#: ./doc/common/tables/trove-redis.xml27(td)
-#: ./doc/common/tables/ceilometer-redis.xml42(td)
-#: ./doc/common/tables/neutron-redis.xml34(td)
-msgid "(StrOpt) Password for Redis server. (optional)"
-msgstr ""
-
-#: ./doc/common/tables/heat-redis.xml37(td)
-#: ./doc/common/tables/trove-redis.xml30(td)
-#: ./doc/common/tables/nova-common.xml74(td)
-#: ./doc/common/tables/ceilometer-redis.xml45(td)
-#: ./doc/common/tables/cinder-rpc.xml86(td)
-#: ./doc/common/tables/glance-redis.xml30(td)
-#: ./doc/common/tables/neutron-redis.xml37(td)
-#: ./doc/common/tables/keystone-redis.xml38(td)
-msgid "port = 6379"
-msgstr ""
-
-#: ./doc/common/tables/heat-redis.xml38(td)
-#: ./doc/common/tables/trove-redis.xml31(td)
-#: ./doc/common/tables/nova-common.xml75(td)
-#: ./doc/common/tables/ceilometer-redis.xml46(td)
-#: ./doc/common/tables/cinder-rpc.xml87(td)
-#: ./doc/common/tables/glance-redis.xml31(td)
-#: ./doc/common/tables/neutron-redis.xml38(td)
-#: ./doc/common/tables/keystone-redis.xml39(td)
-msgid "(IntOpt) Use this port to connect to redis host."
-msgstr ""
-
-#: ./doc/common/tables/trove-logging.xml8(caption)
-#: ./doc/common/tables/glance-logging.xml8(caption)
-#: ./doc/common/tables/ceilometer-logging.xml8(caption)
-#: ./doc/common/tables/neutron-logging.xml8(caption)
-#: ./doc/common/tables/heat-logging.xml8(caption)
-#: ./doc/common/tables/keystone-logging.xml8(caption)
-#: ./doc/common/tables/nova-logging.xml8(caption)
-msgid "Description of configuration options for logging"
-msgstr ""
-
-#: ./doc/common/tables/trove-logging.xml22(td)
-msgid "format_options = -m 5"
-msgstr "format_options = -m 5"
-
-#: ./doc/common/tables/trove-logging.xml23(td)
-#: ./doc/common/tables/trove-logging.xml71(td)
-#: ./doc/common/tables/trove-compute.xml23(td)
-#: ./doc/common/tables/trove-compute.xml27(td)
-#: ./doc/common/tables/trove-api.xml39(td)
-#: ./doc/common/tables/trove-api.xml83(td)
-#: ./doc/common/tables/trove-api.xml91(td)
-#: ./doc/common/tables/trove-api.xml95(td)
-#: ./doc/common/tables/trove-debug.xml55(td)
-#: ./doc/common/tables/trove-debug.xml59(td)
-#: ./doc/common/tables/trove-debug.xml63(td)
-#: ./doc/common/tables/trove-debug.xml67(td)
-#: ./doc/common/tables/trove-debug.xml71(td)
-#: ./doc/common/tables/trove-debug.xml75(td)
-#: ./doc/common/tables/trove-backup.xml39(td)
-#: ./doc/common/tables/trove-backup.xml55(td)
-#: ./doc/common/tables/trove-swift.xml23(td)
-#: ./doc/common/tables/trove-volume.xml23(td)
-#: ./doc/common/tables/trove-volume.xml27(td)
-#: ./doc/common/tables/trove-volume.xml31(td)
-#: ./doc/common/tables/trove-volume.xml43(td)
-#: ./doc/common/tables/trove-rpc.xml27(td)
-#: ./doc/common/tables/trove-common.xml71(td)
-#: ./doc/common/tables/trove-dns.xml23(td)
-#: ./doc/common/tables/trove-dns.xml27(td)
-#: ./doc/common/tables/trove-dns.xml31(td)
-#: ./doc/common/tables/trove-dns.xml35(td)
-#: ./doc/common/tables/trove-dns.xml39(td)
-#: ./doc/common/tables/trove-dns.xml43(td)
-#: ./doc/common/tables/trove-dns.xml47(td)
-#: ./doc/common/tables/trove-dns.xml51(td)
-#: ./doc/common/tables/trove-dns.xml55(td)
-#: ./doc/common/tables/trove-dns.xml59(td)
-#: ./doc/common/tables/trove-dns.xml63(td)
-#: ./doc/common/tables/trove-dns.xml67(td)
-#: ./doc/common/tables/trove-dns.xml79(td)
-#: ./doc/common/tables/trove-heat.xml27(td)
-#: ./doc/common/tables/trove-guestagent.xml39(td)
-#: ./doc/common/tables/trove-guestagent.xml51(td)
-#: ./doc/common/tables/trove-amqp.xml31(td)
-msgid "(StrOpt) No help text available for this option."
-msgstr ""
-
-#: ./doc/common/tables/trove-logging.xml26(td)
-#: ./doc/common/tables/glance-logging.xml34(td)
-#: ./doc/common/tables/cinder-images.xml62(td)
-#: ./doc/common/tables/ceilometer-logging.xml34(td)
-#: ./doc/common/tables/neutron-logging.xml34(td)
-#: ./doc/common/tables/heat-logging.xml26(td)
-#: ./doc/common/tables/keystone-logging.xml26(td)
-#: ./doc/common/tables/nova-logging.xml38(td)
-msgid "instance_format = \"[instance: %(uuid)s] \""
-msgstr "instance_format = \"[instance: %(uuid)s] \""
-
-#: ./doc/common/tables/trove-logging.xml27(td)
-#: ./doc/common/tables/glance-logging.xml35(td)
-#: ./doc/common/tables/cinder-images.xml63(td)
-#: ./doc/common/tables/ceilometer-logging.xml35(td)
-#: ./doc/common/tables/neutron-logging.xml35(td)
-#: ./doc/common/tables/heat-logging.xml27(td)
-#: ./doc/common/tables/keystone-logging.xml27(td)
-#: ./doc/common/tables/nova-logging.xml39(td)
+#: ./doc/common/tables/nova-db.xml61(td)
+#: ./doc/common/tables/glance-db.xml47(td)
+#: ./doc/common/tables/neutron-db.xml58(td)
+#: ./doc/common/tables/keystone-database.xml47(td)
 msgid ""
-"(StrOpt) If an instance is passed with the log message, format it like this"
-msgstr "(StrOpt)  Si une instance est passée dans le message de log, la formater ainsi"
-
-#: ./doc/common/tables/trove-logging.xml30(td)
-#: ./doc/common/tables/glance-logging.xml38(td)
-#: ./doc/common/tables/cinder-images.xml66(td)
-#: ./doc/common/tables/ceilometer-logging.xml38(td)
-#: ./doc/common/tables/neutron-logging.xml38(td)
-#: ./doc/common/tables/heat-logging.xml30(td)
-#: ./doc/common/tables/keystone-logging.xml30(td)
-#: ./doc/common/tables/nova-logging.xml42(td)
-msgid "instance_uuid_format = \"[instance: %(uuid)s] \""
+"(IntOpt) max seconds between db connection retries, if db_inc_retry_interval"
+" is enabled"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml31(td)
-#: ./doc/common/tables/glance-logging.xml39(td)
-#: ./doc/common/tables/cinder-images.xml67(td)
-#: ./doc/common/tables/ceilometer-logging.xml39(td)
-#: ./doc/common/tables/neutron-logging.xml39(td)
-#: ./doc/common/tables/heat-logging.xml31(td)
-#: ./doc/common/tables/keystone-logging.xml31(td)
-#: ./doc/common/tables/nova-logging.xml43(td)
+#: ./doc/common/tables/nova-db.xml64(td)
+#: ./doc/common/tables/glance-db.xml50(td)
+#: ./doc/common/tables/neutron-db.xml61(td)
+#: ./doc/common/tables/keystone-database.xml50(td)
+msgid "db_retry_interval = 1"
+msgstr ""
+
+#: ./doc/common/tables/nova-db.xml65(td)
+#: ./doc/common/tables/glance-db.xml51(td)
+#: ./doc/common/tables/neutron-db.xml62(td)
+#: ./doc/common/tables/keystone-database.xml51(td)
+msgid "(IntOpt) seconds between db connection retries"
+msgstr ""
+
+#: ./doc/common/tables/nova-db.xml88(td)
+msgid "mysql_sql_mode = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-db.xml89(td)
 msgid ""
-"(StrOpt) If an instance UUID is passed with the log message, format it like "
-"this"
-msgstr "(StrOpt)  Si l’UUID d’une instance est passé dans le message de log, le formater ainsi"
-
-#: ./doc/common/tables/trove-logging.xml34(td)
-#: ./doc/common/tables/glance-logging.xml42(td)
-#: ./doc/common/tables/ceilometer-logging.xml42(td)
-#: ./doc/common/tables/neutron-logging.xml42(td)
-#: ./doc/common/tables/heat-logging.xml34(td)
-#: ./doc/common/tables/keystone-logging.xml34(td)
-#: ./doc/common/tables/nova-logging.xml46(td)
-#: ./doc/common/tables/cinder-common.xml74(td)
-msgid "log_config_append = None"
+"(StrOpt) The SQL mode to be used for MySQL sessions (default is empty, "
+"meaning do not override any server-side SQL mode setting)"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml35(td)
-#: ./doc/common/tables/glance-logging.xml43(td)
-#: ./doc/common/tables/ceilometer-logging.xml43(td)
-#: ./doc/common/tables/neutron-logging.xml43(td)
-#: ./doc/common/tables/heat-logging.xml35(td)
-#: ./doc/common/tables/keystone-logging.xml35(td)
-#: ./doc/common/tables/nova-logging.xml47(td)
-#: ./doc/common/tables/cinder-common.xml75(td)
+#: ./doc/common/tables/nova-db.xml100(td)
+msgid "slave_connection = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-db.xml104(td)
+msgid "sqlite_db = nova.sqlite"
+msgstr "sqlite_db = nova.sqlite"
+
+#: ./doc/common/tables/nova-db.xml112(td)
+#: ./doc/common/tables/glance-db.xml94(td)
+#: ./doc/common/tables/neutron-db.xml97(td)
+#: ./doc/common/tables/keystone-database.xml94(td)
+msgid "use_db_reconnect = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-db.xml113(td)
+#: ./doc/common/tables/glance-db.xml95(td)
+#: ./doc/common/tables/neutron-db.xml98(td)
+#: ./doc/common/tables/keystone-database.xml95(td)
 msgid ""
-"(StrOpt) The name of logging configuration file. It does not disable "
-"existing loggers, but just appends specified logging configuration to any "
-"other existing logging options. Please see the Python logging module "
-"documentation for details on logging configuration files."
+"(BoolOpt) Enable the experimental use of database reconnect on connection "
+"lost"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml38(td)
-#: ./doc/common/tables/glance-logging.xml46(td)
-#: ./doc/common/tables/ceilometer-logging.xml46(td)
-#: ./doc/common/tables/neutron-logging.xml46(td)
-#: ./doc/common/tables/heat-logging.xml38(td)
-#: ./doc/common/tables/keystone-logging.xml38(td)
-#: ./doc/common/tables/nova-logging.xml50(td)
-#: ./doc/common/tables/cinder-common.xml78(td)
-msgid "log_date_format = %Y-%m-%d %H:%M:%S"
-msgstr ""
-
-#: ./doc/common/tables/trove-logging.xml39(td)
-#: ./doc/common/tables/glance-logging.xml47(td)
-#: ./doc/common/tables/ceilometer-logging.xml47(td)
-#: ./doc/common/tables/neutron-logging.xml47(td)
-#: ./doc/common/tables/heat-logging.xml39(td)
-#: ./doc/common/tables/keystone-logging.xml39(td)
-#: ./doc/common/tables/nova-logging.xml51(td)
-#: ./doc/common/tables/cinder-common.xml79(td)
+#: ./doc/common/tables/glance-rabbitmq.xml23(td)
+#: ./doc/common/tables/keystone-amqp.xml31(td)
+#: ./doc/common/tables/cinder-rpc.xml35(td)
+#: ./doc/common/tables/nova-rpc_all.xml31(td)
+#: ./doc/common/tables/nova-rpc.xml31(td)
 msgid ""
-"(StrOpt) Format string for %%(asctime)s in log records. Default: %(default)s"
+"(StrOpt) The default exchange under which topics are scoped. May be "
+"overridden by an exchange name specified in the transport_url option."
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml42(td)
-#: ./doc/common/tables/glance-logging.xml50(td)
-#: ./doc/common/tables/ceilometer-logging.xml50(td)
-#: ./doc/common/tables/neutron-logging.xml50(td)
-#: ./doc/common/tables/heat-logging.xml42(td)
-#: ./doc/common/tables/keystone-logging.xml42(td)
-#: ./doc/common/tables/nova-logging.xml54(td)
-#: ./doc/common/tables/cinder-common.xml82(td)
-msgid "log_dir = None"
+#: ./doc/common/tables/neutron-l3_agent.xml8(caption)
+msgid "Description of configuration options for l3_agent"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml43(td)
-#: ./doc/common/tables/glance-logging.xml51(td)
-#: ./doc/common/tables/ceilometer-logging.xml51(td)
-#: ./doc/common/tables/neutron-logging.xml51(td)
-#: ./doc/common/tables/heat-logging.xml43(td)
-#: ./doc/common/tables/keystone-logging.xml43(td)
-#: ./doc/common/tables/nova-logging.xml55(td)
-#: ./doc/common/tables/cinder-common.xml83(td)
+#: ./doc/common/tables/neutron-l3_agent.xml22(td)
+msgid "enable_metadata_proxy = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-l3_agent.xml23(td)
+msgid "(BoolOpt) Allow running metadata proxy."
+msgstr ""
+
+#: ./doc/common/tables/neutron-l3_agent.xml26(td)
+msgid "external_network_bridge = br-ex"
+msgstr ""
+
+#: ./doc/common/tables/neutron-l3_agent.xml27(td)
+msgid "(StrOpt) Name of bridge used for external network traffic."
+msgstr ""
+
+#: ./doc/common/tables/neutron-l3_agent.xml30(td)
+msgid "gateway_external_network_id ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-l3_agent.xml31(td)
 msgid ""
-"(StrOpt) (Optional) The base directory used for relative --log-file paths"
+"(StrOpt) UUID of external network for routers implemented by the agents."
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml46(td)
-#: ./doc/common/tables/glance-logging.xml54(td)
-#: ./doc/common/tables/ceilometer-logging.xml54(td)
-#: ./doc/common/tables/neutron-logging.xml54(td)
-#: ./doc/common/tables/heat-logging.xml46(td)
-#: ./doc/common/tables/keystone-logging.xml46(td)
-#: ./doc/common/tables/nova-logging.xml58(td)
-#: ./doc/common/tables/cinder-common.xml86(td)
-msgid "log_file = None"
+#: ./doc/common/tables/neutron-l3_agent.xml34(td)
+msgid "handle_internal_only_routers = True"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml47(td)
-#: ./doc/common/tables/glance-logging.xml55(td)
-#: ./doc/common/tables/ceilometer-logging.xml55(td)
-#: ./doc/common/tables/neutron-logging.xml55(td)
-#: ./doc/common/tables/heat-logging.xml47(td)
-#: ./doc/common/tables/keystone-logging.xml47(td)
-#: ./doc/common/tables/nova-logging.xml59(td)
-#: ./doc/common/tables/cinder-common.xml87(td)
+#: ./doc/common/tables/neutron-l3_agent.xml35(td)
+msgid "(BoolOpt) Agent should implement routers with no gateway"
+msgstr ""
+
+#: ./doc/common/tables/neutron-l3_agent.xml38(td)
+msgid "router_id ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-l3_agent.xml39(td)
 msgid ""
-"(StrOpt) (Optional) Name of log file to output to. If no default is set, "
-"logging will go to stdout."
+"(StrOpt) If namespaces is disabled, the l3 agent can only configure a router"
+" that has the matching router ID."
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml50(td)
-#: ./doc/common/tables/glance-logging.xml58(td)
-#: ./doc/common/tables/ceilometer-logging.xml58(td)
-#: ./doc/common/tables/neutron-logging.xml58(td)
-#: ./doc/common/tables/heat-logging.xml50(td)
-#: ./doc/common/tables/keystone-logging.xml50(td)
-#: ./doc/common/tables/nova-logging.xml62(td)
-#: ./doc/common/tables/cinder-common.xml90(td)
-msgid "log_format = None"
+#: ./doc/common/tables/neutron-l3_agent.xml42(td)
+msgid "send_arp_for_ha = 0"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml51(td)
-#: ./doc/common/tables/glance-logging.xml59(td)
-#: ./doc/common/tables/ceilometer-logging.xml59(td)
-#: ./doc/common/tables/neutron-logging.xml59(td)
-#: ./doc/common/tables/heat-logging.xml51(td)
-#: ./doc/common/tables/keystone-logging.xml51(td)
-#: ./doc/common/tables/nova-logging.xml63(td)
-#: ./doc/common/tables/cinder-common.xml91(td)
+#: ./doc/common/tables/neutron-l3_agent.xml43(td)
 msgid ""
-"(StrOpt) DEPRECATED. A logging.Formatter log message format string which may"
-" use any of the available logging.LogRecord attributes. This option is "
-"deprecated. Please use logging_context_format_string and "
-"logging_default_format_string instead."
+"(IntOpt) Send this many gratuitous ARPs for HA setup, if less than or equal "
+"to 0, the feature is disabled"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml54(td)
-#: ./doc/common/tables/glance-logging.xml62(td)
-#: ./doc/common/tables/ceilometer-logging.xml62(td)
-#: ./doc/common/tables/neutron-logging.xml62(td)
-#: ./doc/common/tables/heat-logging.xml54(td)
-#: ./doc/common/tables/keystone-logging.xml54(td)
-#: ./doc/common/tables/cinder-common.xml94(td)
-msgid ""
-"logging_context_format_string = %(asctime)s.%(msecs)03d %(process)d "
-"%(levelname)s %(name)s [%(request_id)s %(user_identity)s] "
-"%(instance)s%(message)s"
-msgstr "logging_context_format_string = %(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [%(request_id)s %(user_identity)s] %(instance)s%(message)s"
-
-#: ./doc/common/tables/trove-logging.xml55(td)
-#: ./doc/common/tables/neutron-logging.xml63(td)
-#: ./doc/common/tables/heat-logging.xml55(td)
-#: ./doc/common/tables/nova-logging.xml67(td)
-msgid "(StrOpt) format string to use for log messages with context"
-msgstr "(StrOpt)  chaîne de format à utiliser pour les messages de log avec contexte"
-
-#: ./doc/common/tables/trove-logging.xml58(td)
-#: ./doc/common/tables/glance-logging.xml66(td)
-#: ./doc/common/tables/ceilometer-logging.xml66(td)
-#: ./doc/common/tables/neutron-logging.xml66(td)
-#: ./doc/common/tables/heat-logging.xml58(td)
-#: ./doc/common/tables/keystone-logging.xml58(td)
-#: ./doc/common/tables/nova-logging.xml70(td)
-#: ./doc/common/tables/cinder-common.xml98(td)
-msgid "logging_debug_format_suffix = %(funcName)s %(pathname)s:%(lineno)d"
-msgstr "logging_debug_format_suffix = %(funcName)s %(pathname)s:%(lineno)d"
-
-#: ./doc/common/tables/trove-logging.xml59(td)
-#: ./doc/common/tables/neutron-logging.xml67(td)
-#: ./doc/common/tables/heat-logging.xml59(td)
-#: ./doc/common/tables/nova-logging.xml71(td)
-msgid "(StrOpt) data to append to log format when level is DEBUG"
-msgstr "(StrOpt)  données à ajouter au format de journal lorsque le niveau est DEBUG"
-
-#: ./doc/common/tables/trove-logging.xml62(td)
-#: ./doc/common/tables/glance-logging.xml70(td)
-#: ./doc/common/tables/ceilometer-logging.xml70(td)
-#: ./doc/common/tables/neutron-logging.xml70(td)
-#: ./doc/common/tables/heat-logging.xml62(td)
-#: ./doc/common/tables/keystone-logging.xml62(td)
-#: ./doc/common/tables/nova-logging.xml74(td)
-#: ./doc/common/tables/cinder-common.xml102(td)
-msgid ""
-"logging_default_format_string = %(asctime)s.%(msecs)03d %(process)d "
-"%(levelname)s %(name)s [-] %(instance)s%(message)s"
-msgstr "logging_default_format_string = %(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [-] %(instance)s%(message)s"
-
-#: ./doc/common/tables/trove-logging.xml63(td)
-#: ./doc/common/tables/neutron-logging.xml71(td)
-#: ./doc/common/tables/heat-logging.xml63(td)
-#: ./doc/common/tables/nova-logging.xml75(td)
-msgid "(StrOpt) format string to use for log messages without context"
-msgstr "(StrOpt)  chaîne de format à utiliser pour les messages de log sans contexte"
-
-#: ./doc/common/tables/trove-logging.xml66(td)
-#: ./doc/common/tables/glance-logging.xml74(td)
-#: ./doc/common/tables/ceilometer-logging.xml74(td)
-#: ./doc/common/tables/neutron-logging.xml74(td)
-#: ./doc/common/tables/heat-logging.xml66(td)
-#: ./doc/common/tables/keystone-logging.xml66(td)
-#: ./doc/common/tables/nova-logging.xml78(td)
-#: ./doc/common/tables/cinder-common.xml106(td)
-msgid ""
-"logging_exception_prefix = %(asctime)s.%(msecs)03d %(process)d TRACE "
-"%(name)s %(instance)s"
-msgstr "logging_exception_prefix = %(asctime)s.%(msecs)03d %(process)d TRACE %(name)s %(instance)s"
-
-#: ./doc/common/tables/trove-logging.xml67(td)
-#: ./doc/common/tables/neutron-logging.xml75(td)
-#: ./doc/common/tables/heat-logging.xml67(td)
-#: ./doc/common/tables/nova-logging.xml79(td)
-msgid "(StrOpt) prefix each line of exception output with this format"
-msgstr "(StrOpt)  préfixer chaque ligne de sortie d'exception avec ce format"
-
-#: ./doc/common/tables/trove-logging.xml70(td)
-msgid "network_label_regex = ^private$"
-msgstr "network_label_regex = ^private$"
-
-#: ./doc/common/tables/trove-logging.xml75(td)
-#: ./doc/common/tables/heat-notification.xml27(td)
-#: ./doc/common/tables/neutron-logging.xml79(td)
-#: ./doc/common/tables/nova-logging.xml83(td)
-msgid "(BoolOpt) publish error events"
-msgstr "(BoolOpt) publier les événements de type erreur"
-
-#: ./doc/common/tables/trove-logging.xml78(td)
-#: ./doc/common/tables/glance-logging.xml82(td)
-#: ./doc/common/tables/ceilometer-logging.xml82(td)
-#: ./doc/common/tables/neutron-logging.xml82(td)
-#: ./doc/common/tables/heat-logging.xml70(td)
-#: ./doc/common/tables/keystone-logging.xml70(td)
-#: ./doc/common/tables/nova-logging.xml86(td)
-#: ./doc/common/tables/cinder-common.xml194(td)
-msgid "syslog_log_facility = LOG_USER"
-msgstr ""
-
-#: ./doc/common/tables/trove-logging.xml79(td)
-#: ./doc/common/tables/neutron-logging.xml83(td)
-#: ./doc/common/tables/heat-logging.xml71(td)
-#: ./doc/common/tables/nova-logging.xml87(td)
-msgid "(StrOpt) syslog facility to receive log lines"
-msgstr "(StrOpt)  syslog destiné à recevoir les lignes de log"
-
-#: ./doc/common/tables/trove-logging.xml82(td)
-#: ./doc/common/tables/glance-logging.xml86(td)
-#: ./doc/common/tables/ceilometer-logging.xml86(td)
-#: ./doc/common/tables/neutron-logging.xml90(td)
-#: ./doc/common/tables/heat-logging.xml74(td)
-#: ./doc/common/tables/keystone-logging.xml74(td)
-#: ./doc/common/tables/nova-logging.xml90(td)
-#: ./doc/common/tables/cinder-common.xml210(td)
-msgid "use_stderr = True"
-msgstr "use_stderr = True"
-
-#: ./doc/common/tables/trove-logging.xml83(td)
-#: ./doc/common/tables/glance-logging.xml87(td)
-#: ./doc/common/tables/ceilometer-logging.xml87(td)
-#: ./doc/common/tables/neutron-logging.xml91(td)
-#: ./doc/common/tables/heat-logging.xml75(td)
-#: ./doc/common/tables/keystone-logging.xml75(td)
-#: ./doc/common/tables/nova-logging.xml91(td)
-#: ./doc/common/tables/cinder-common.xml211(td)
-msgid "(BoolOpt) Log output to standard error"
-msgstr ""
-
-#: ./doc/common/tables/trove-logging.xml86(td)
-#: ./doc/common/tables/glance-logging.xml90(td)
-#: ./doc/common/tables/ceilometer-logging.xml90(td)
-#: ./doc/common/tables/cinder-rootwrap.xml30(td)
-#: ./doc/common/tables/neutron-logging.xml94(td)
-#: ./doc/common/tables/heat-logging.xml78(td)
-#: ./doc/common/tables/keystone-logging.xml78(td)
-#: ./doc/common/tables/nova-logging.xml94(td)
-#: ./doc/common/tables/cinder-common.xml214(td)
-#: ./doc/common/tables/neutron-rootwrap.xml30(td)
-#: ./doc/common/tables/nova-rootwrap.xml30(td)
-msgid "use_syslog = False"
-msgstr ""
-
-#: ./doc/common/tables/trove-logging.xml87(td)
-#: ./doc/common/tables/neutron-logging.xml95(td)
-#: ./doc/common/tables/heat-logging.xml79(td)
-msgid "(BoolOpt) Use syslog for logging."
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml7(literal)
-msgid "[container-updater]"
-msgstr "[container-updater]"
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml18(td)
-msgid "log_name = container-updater"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml30(td)
-#: ./doc/common/tables/swift-container-server-container-sync.xml33(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml30(td)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml18(td)
-msgid "interval = 300"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml30(td)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml42(td)
-#: ./doc/common/tables/swift-container-server-container-sync.xml33(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml30(td)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml30(td)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml30(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml42(td)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml18(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml33(td)
-msgid "Minimum time for a pass to take"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml33(td)
-msgid "concurrency = 4"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml33(td)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml39(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml33(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml39(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml54(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml39(td)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml30(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml30(td)
-msgid "Number of replication workers to spawn"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml36(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml36(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml112(td)
-msgid "node_timeout = 3"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml36(td)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml45(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml36(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml48(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml36(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml112(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml57(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml51(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml36(td)
-msgid "Request timeout to external services"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml39(td)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml48(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml54(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml39(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml109(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml54(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml39(td)
-msgid "conn_timeout = 0.5"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml39(td)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml48(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml54(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml39(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml109(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml54(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml39(td)
-msgid "Connection timeout to external services"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml42(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml39(td)
-msgid "slowdown = 0.01"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml42(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml39(td)
-msgid "Time in seconds to wait between objects"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml45(td)
-msgid "account_suppression_time = 60"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml45(td)
-msgid ""
-"Seconds to suppress updating an account that has generated an error "
-"(timeout, not yet found, etc.)"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml49(td)
-#: ./doc/common/tables/swift-account-server-filter-recon.xml21(td)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml57(td)
-#: ./doc/common/tables/swift-object-server-object-auditor.xml42(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml42(td)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml42(td)
-#: ./doc/common/tables/swift-object-server-filter-recon.xml21(td)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml36(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml72(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml63(td)
-#: ./doc/common/tables/swift-container-server-filter-recon.xml21(td)
-msgid "recon_cache_path = /var/cache/swift"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml49(td)
-#: ./doc/common/tables/swift-account-server-filter-recon.xml21(td)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml57(td)
-#: ./doc/common/tables/swift-object-server-object-auditor.xml42(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml42(td)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml42(td)
-#: ./doc/common/tables/swift-object-server-filter-recon.xml21(td)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml36(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml72(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml63(td)
-#: ./doc/common/tables/swift-container-server-filter-recon.xml21(td)
-msgid "Directory where stats for a few items will be stored"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml8(caption)
-msgid "Description of configuration options for storage_gpfs"
-msgstr "Description des options de configuration pour storage_gpfs"
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml22(td)
-msgid "gpfs_images_dir = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml23(td)
-msgid ""
-"(StrOpt) Specifies the path of the Image service repository in GPFS. Leave "
-"undefined if not storing images in GPFS."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml26(td)
-msgid "gpfs_images_share_mode = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml27(td)
-msgid ""
-"(StrOpt) Specifies the type of image copy to be used. Set this when the "
-"Image service repository also uses GPFS so that image files can be "
-"transferred efficiently from the Image service to the Block Storage service."
-" There are two valid values: \"copy\" specifies that a full copy of the "
-"image is made; \"copy_on_write\" specifies that copy-on-write optimization "
-"strategy is used and unmodified blocks of the image file are shared "
-"efficiently."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml30(td)
-msgid "gpfs_max_clone_depth = 0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml31(td)
-msgid ""
-"(IntOpt) Specifies an upper limit on the number of indirections required to "
-"reach a specific block due to snapshots or clones. A lengthy chain of copy-"
-"on-write snapshots or clones can have a negative impact on performance, but "
-"improves space utilization. 0 indicates unlimited clone depth."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml34(td)
-msgid "gpfs_mount_point_base = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml35(td)
-msgid ""
-"(StrOpt) Specifies the path of the GPFS directory where Block Storage volume"
-" and snapshot files are stored."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml38(td)
-msgid "gpfs_sparse_volumes = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml39(td)
-msgid ""
-"(BoolOpt) Specifies that volumes are created as sparse files which initially"
-" consume no space. If set to False, the volume is created as a fully "
-"allocated file, in which case, creation may take a significantly longer "
-"time."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml42(td)
-msgid "gpfs_storage_pool = None"
-msgstr "gpfs_storage_pool = None"
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml43(td)
-msgid ""
-"(StrOpt) Specifies the storage pool that volumes are assigned to. By "
-"default, the system storage pool is used."
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml8(caption)
-msgid "Description of configuration options for nexenta_iscsi"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml22(td)
-msgid "nexenta_blocksize ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml23(td)
-msgid "(StrOpt) block size for volumes (blank=default,8KB)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml26(td)
-msgid "nexenta_host ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml27(td)
-msgid "(StrOpt) IP address of Nexenta SA"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml30(td)
-msgid "nexenta_iscsi_target_portal_port = 3260"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml31(td)
-msgid "(IntOpt) Nexenta target portal port"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml34(td)
-msgid "nexenta_password = nexenta"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml35(td)
-msgid "(StrOpt) Password to connect to Nexenta SA"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml38(td)
-msgid "nexenta_rest_port = 2000"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml39(td)
-msgid "(IntOpt) HTTP port to connect to Nexenta REST API server"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml42(td)
-msgid "nexenta_rest_protocol = auto"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml43(td)
-msgid "(StrOpt) Use http or https for REST connection (default auto)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml46(td)
-msgid "nexenta_rrmgr_compression = 0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml47(td)
-msgid ""
-"(IntOpt) Enable stream compression, level 1..9. 1 - gives best speed; 9 - "
-"gives best compression."
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml50(td)
-msgid "nexenta_rrmgr_connections = 2"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml51(td)
-msgid "(IntOpt) Number of TCP connections."
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml54(td)
-msgid "nexenta_rrmgr_tcp_buf_size = 4096"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml55(td)
-msgid "(IntOpt) TCP Buffer size in KiloBytes."
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml58(td)
-msgid "nexenta_sparse = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml59(td)
-msgid "(BoolOpt) flag to create sparse volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml62(td)
-msgid "nexenta_sparsed_volumes = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml63(td)
-#: ./doc/common/tables/cinder-storage_nfs.xml39(td)
-#: ./doc/common/tables/cinder-storage_glusterfs.xml35(td)
-msgid ""
-"(BoolOpt) Create volumes as sparsed files which take no space.If set to "
-"False volume is created as regular file.In such case volume creation takes a"
-" lot of time."
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml66(td)
-msgid "nexenta_target_group_prefix = cinder/"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml67(td)
-msgid "(StrOpt) prefix for iSCSI target groups on SA"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml70(td)
-msgid "nexenta_target_prefix = iqn.1986-03.com.sun:02:cinder-"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml71(td)
-msgid "(StrOpt) IQN prefix for iSCSI targets"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml74(td)
-msgid "nexenta_user = admin"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml75(td)
-msgid "(StrOpt) User name to connect to Nexenta SA"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml78(td)
-msgid "nexenta_volume = cinder"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml79(td)
-msgid "(StrOpt) pool on SA that will hold all volumes"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml8(caption)
-msgid "Description of configuration options for tilera"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml22(td)
-msgid "tile_pdu_ip = 10.0.100.1"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml23(td)
-msgid "(StrOpt) IP address of tilera pdu"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml26(td)
-msgid "tile_pdu_mgr = /tftpboot/pdu_mgr"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml27(td)
-msgid "(StrOpt) Management script for tilera pdu"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml30(td)
-msgid "tile_pdu_off = 2"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml31(td)
-msgid "(IntOpt) Power status of tilera PDU is OFF"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml34(td)
-msgid "tile_pdu_on = 1"
-msgstr "tile_pdu_on = 1"
-
-#: ./doc/common/tables/nova-tilera.xml35(td)
-msgid "(IntOpt) Power status of tilera PDU is ON"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml38(td)
-msgid "tile_pdu_status = 9"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml39(td)
-msgid "(IntOpt) Power status of tilera PDU"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml42(td)
-msgid "tile_power_wait = 9"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml43(td)
-msgid ""
-"(IntOpt) Wait time in seconds until check the result after tilera power "
-"operations"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml8(caption)
-msgid "Description of configuration options for ca"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml22(td)
-msgid "ca_file = cacert.pem"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml23(td)
-msgid "(StrOpt) Filename of root CA"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml26(td)
-msgid "ca_path = $state_path/CA"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml27(td)
-msgid "(StrOpt) Where we keep our root CA"
-msgstr "(StrOpt)  Où nous conservons notre CA racine"
-
-#: ./doc/common/tables/nova-ca.xml30(td)
-msgid "cert_manager = nova.cert.manager.CertManager"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml31(td)
-msgid "(StrOpt) Full class name for the Manager for cert"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml34(td)
-msgid "cert_topic = cert"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml35(td)
-msgid "(StrOpt) The topic cert nodes listen on"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml38(td)
-msgid "crl_file = crl.pem"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml39(td)
-msgid "(StrOpt) Filename of root Certificate Revocation List"
-msgstr "(StrOpt)  Nom de fichier de la liste de révocation de certificat racine"
-
-#: ./doc/common/tables/nova-ca.xml42(td)
-msgid "key_file = private/cakey.pem"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml43(td)
-msgid "(StrOpt) Filename of private key"
-msgstr "(StrOpt)  Nom de fichier de la clé privée"
-
-#: ./doc/common/tables/nova-ca.xml46(td)
-msgid "keys_path = $state_path/keys"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml47(td)
-msgid "(StrOpt) Where we keep our keys"
-msgstr "(StrOpt)  Où nous conservons nos clés"
-
-#: ./doc/common/tables/nova-ca.xml50(td)
-msgid ""
-"project_cert_subject = /C=US/ST=California/O=OpenStack/OU=NovaDev/CN"
-"=project-ca-%.16s-%s"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml51(td)
-msgid ""
-"(StrOpt) Subject for certificate for projects, %s for project, timestamp"
-msgstr "(StrOpt)  Objet de certificat pour les projets,% s pour le projet, timestamp"
-
-#: ./doc/common/tables/nova-ca.xml54(td)
-msgid "use_project_ca = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml55(td)
-msgid "(BoolOpt) Should we use a CA for each project?"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml58(td)
-msgid ""
-"user_cert_subject = "
-"/C=US/ST=California/O=OpenStack/OU=NovaDev/CN=%.16s-%.16s-%s"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml59(td)
-msgid ""
-"(StrOpt) Subject for certificate for users, %s for project, user, timestamp"
-msgstr "(StrOpt)  Objet de certificat pour les utilisateurs, % s pour le projet, utilisateur, timestamp"
-
-#: ./doc/common/tables/nova-ca.xml62(th)
-#: ./doc/common/tables/heat-cfn_api.xml61(th)
-#: ./doc/common/tables/heat-cloudwatch_api.xml57(th)
-#: ./doc/common/tables/cinder-ssl.xml19(th)
-#: ./doc/common/tables/heat-api.xml142(th)
-#: ./doc/common/tables/neutron-ssl.xml34(th)
-#: ./doc/common/tables/trove-ssl.xml19(th)
-#: ./doc/common/tables/keystone-ssl.xml54(th)
-#: ./doc/common/tables/ceilometer-ssl.xml19(th)
-msgid "[ssl]"
-msgstr "[ssl]"
-
-#: ./doc/common/tables/nova-ca.xml65(td)
-#: ./doc/common/tables/heat-clients_nova.xml22(td)
-#: ./doc/common/tables/heat-cfn_api.xml64(td)
-#: ./doc/common/tables/heat-clients.xml29(td)
-#: ./doc/common/tables/heat-clients_heat.xml22(td)
-#: ./doc/common/tables/heat-clients_swift.xml22(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml60(td)
-#: ./doc/common/tables/heat-clients_ceilometer.xml22(td)
-#: ./doc/common/tables/heat-clients_trove.xml22(td)
-#: ./doc/common/tables/heat-clients_cinder.xml22(td)
-#: ./doc/common/tables/cinder-ssl.xml22(td)
-#: ./doc/common/tables/heat-api.xml145(td)
-#: ./doc/common/tables/neutron-ssl.xml37(td)
-#: ./doc/common/tables/heat-clients_neutron.xml22(td)
-#: ./doc/common/tables/trove-ssl.xml22(td)
-#: ./doc/common/tables/glance-ssl.xml22(td)
-#: ./doc/common/tables/heat-clients_keystone.xml22(td)
-#: ./doc/common/tables/ceilometer-ssl.xml22(td)
-msgid "ca_file = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml66(td)
-#: ./doc/common/tables/glance-ssl.xml23(td)
-msgid "(StrOpt) CA certificate file to use to verify connecting clients."
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml69(td)
-#: ./doc/common/tables/heat-clients_nova.xml26(td)
-#: ./doc/common/tables/heat-cfn_api.xml45(td)
-#: ./doc/common/tables/heat-cfn_api.xml68(td)
-#: ./doc/common/tables/heat-clients.xml33(td)
-#: ./doc/common/tables/heat-clients_heat.xml26(td)
-#: ./doc/common/tables/heat-clients_swift.xml26(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml41(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml64(td)
-#: ./doc/common/tables/heat-clients_ceilometer.xml26(td)
-#: ./doc/common/tables/heat-clients_trove.xml26(td)
-#: ./doc/common/tables/heat-clients_cinder.xml26(td)
-#: ./doc/common/tables/cinder-ssl.xml26(td)
-#: ./doc/common/tables/heat-api.xml115(td)
-#: ./doc/common/tables/heat-api.xml149(td)
-#: ./doc/common/tables/neutron-ssl.xml41(td)
-#: ./doc/common/tables/heat-clients_neutron.xml26(td)
-#: ./doc/common/tables/trove-ssl.xml26(td)
-#: ./doc/common/tables/glance-ssl.xml26(td)
-#: ./doc/common/tables/heat-clients_keystone.xml26(td)
-#: ./doc/common/tables/neutron-nec.xml26(td)
-#: ./doc/common/tables/ceilometer-ssl.xml26(td)
-msgid "cert_file = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml70(td)
-msgid "(StrOpt) Certificate file to use when starting the server securely."
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml73(td)
-#: ./doc/common/tables/heat-clients_nova.xml38(td)
-#: ./doc/common/tables/heat-cfn_api.xml49(td)
-#: ./doc/common/tables/heat-cfn_api.xml72(td)
-#: ./doc/common/tables/heat-clients.xml45(td)
-#: ./doc/common/tables/heat-clients_heat.xml38(td)
-#: ./doc/common/tables/heat-clients_swift.xml38(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml45(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml68(td)
-#: ./doc/common/tables/heat-clients_ceilometer.xml38(td)
-#: ./doc/common/tables/heat-clients_trove.xml38(td)
-#: ./doc/common/tables/heat-clients_cinder.xml38(td)
-#: ./doc/common/tables/cinder-ssl.xml30(td)
-#: ./doc/common/tables/heat-api.xml119(td)
-#: ./doc/common/tables/heat-api.xml153(td)
-#: ./doc/common/tables/neutron-ssl.xml45(td)
-#: ./doc/common/tables/heat-clients_neutron.xml38(td)
-#: ./doc/common/tables/trove-ssl.xml30(td)
-#: ./doc/common/tables/glance-ssl.xml30(td)
-#: ./doc/common/tables/heat-clients_keystone.xml38(td)
-#: ./doc/common/tables/neutron-nec.xml46(td)
-#: ./doc/common/tables/ceilometer-ssl.xml30(td)
-msgid "key_file = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml74(td)
-msgid "(StrOpt) Private key file to use when starting the server securely."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_nova.xml8(caption)
-msgid "Description of configuration options for clients_nova"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_nova.xml19(th)
-msgid "[clients_nova]"
-msgstr "[clients_nova]"
-
-#: ./doc/common/tables/heat-clients_nova.xml23(td)
-#: ./doc/common/tables/heat-clients.xml30(td)
-#: ./doc/common/tables/heat-clients_heat.xml23(td)
-#: ./doc/common/tables/heat-clients_swift.xml23(td)
-#: ./doc/common/tables/heat-clients_ceilometer.xml23(td)
-#: ./doc/common/tables/heat-clients_trove.xml23(td)
-#: ./doc/common/tables/heat-clients_cinder.xml23(td)
-#: ./doc/common/tables/heat-clients_neutron.xml23(td)
-#: ./doc/common/tables/heat-clients_keystone.xml23(td)
-msgid "(StrOpt) Optional CA cert file to use in SSL connections."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_nova.xml27(td)
-#: ./doc/common/tables/heat-clients.xml34(td)
-#: ./doc/common/tables/heat-clients_heat.xml27(td)
-#: ./doc/common/tables/heat-clients_swift.xml27(td)
-#: ./doc/common/tables/heat-clients_ceilometer.xml27(td)
-#: ./doc/common/tables/heat-clients_trove.xml27(td)
-#: ./doc/common/tables/heat-clients_cinder.xml27(td)
-#: ./doc/common/tables/heat-clients_neutron.xml27(td)
-#: ./doc/common/tables/heat-clients_keystone.xml27(td)
-msgid "(StrOpt) Optional PEM-formatted certificate chain file."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_nova.xml30(td)
-#: ./doc/common/tables/heat-clients.xml37(td)
-#: ./doc/common/tables/heat-clients_heat.xml30(td)
-#: ./doc/common/tables/heat-clients_swift.xml30(td)
-#: ./doc/common/tables/heat-clients_ceilometer.xml30(td)
-#: ./doc/common/tables/heat-clients_trove.xml30(td)
-#: ./doc/common/tables/heat-clients_cinder.xml30(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml39(td)
-#: ./doc/common/tables/heat-clients_neutron.xml30(td)
-#: ./doc/common/tables/heat-clients_keystone.xml30(td)
-msgid "endpoint_type = publicURL"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_nova.xml31(td)
-#: ./doc/common/tables/heat-clients.xml38(td)
-#: ./doc/common/tables/heat-clients_heat.xml31(td)
-#: ./doc/common/tables/heat-clients_swift.xml31(td)
-#: ./doc/common/tables/heat-clients_ceilometer.xml31(td)
-#: ./doc/common/tables/heat-clients_trove.xml31(td)
-#: ./doc/common/tables/heat-clients_cinder.xml31(td)
-#: ./doc/common/tables/heat-clients_neutron.xml31(td)
-#: ./doc/common/tables/heat-clients_keystone.xml31(td)
-msgid ""
-"(StrOpt) Type of endpoint in Identity service catalog to use for "
-"communication with the OpenStack service."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_nova.xml34(td)
-#: ./doc/common/tables/glance-auth_token.xml101(td)
-#: ./doc/common/tables/heat-clients.xml41(td)
-#: ./doc/common/tables/nova-auth_token.xml94(td)
-#: ./doc/common/tables/cinder-auth_token.xml101(td)
-#: ./doc/common/tables/heat-clients_heat.xml34(td)
-#: ./doc/common/tables/heat-clients_swift.xml34(td)
-#: ./doc/common/tables/trove-auth_token.xml101(td)
-#: ./doc/common/tables/heat-clients_ceilometer.xml34(td)
-#: ./doc/common/tables/heat-clients_trove.xml34(td)
-#: ./doc/common/tables/heat-clients_cinder.xml34(td)
-#: ./doc/common/tables/keystone-auth_token.xml101(td)
-#: ./doc/common/tables/ceilometer-auth.xml101(td)
-#: ./doc/common/tables/ceilometer-auth.xml136(td)
-#: ./doc/common/tables/heat-auth_token.xml101(td)
-#: ./doc/common/tables/heat-clients_neutron.xml34(td)
-#: ./doc/common/tables/neutron-auth_token.xml101(td)
-#: ./doc/common/tables/heat-clients_keystone.xml34(td)
-msgid "insecure = False"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_nova.xml35(td)
-#: ./doc/common/tables/heat-clients.xml42(td)
-#: ./doc/common/tables/heat-clients_heat.xml35(td)
-#: ./doc/common/tables/heat-clients_swift.xml35(td)
-#: ./doc/common/tables/heat-clients_ceilometer.xml35(td)
-#: ./doc/common/tables/heat-clients_trove.xml35(td)
-#: ./doc/common/tables/heat-clients_cinder.xml35(td)
-#: ./doc/common/tables/heat-clients_neutron.xml35(td)
-#: ./doc/common/tables/heat-clients_keystone.xml35(td)
-msgid "(BoolOpt) If set, then the server's certificate will not be verified."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_nova.xml39(td)
-#: ./doc/common/tables/heat-clients.xml46(td)
-#: ./doc/common/tables/heat-clients_heat.xml39(td)
-#: ./doc/common/tables/heat-clients_swift.xml39(td)
-#: ./doc/common/tables/heat-clients_ceilometer.xml39(td)
-#: ./doc/common/tables/heat-clients_trove.xml39(td)
-#: ./doc/common/tables/heat-clients_cinder.xml39(td)
-#: ./doc/common/tables/heat-clients_neutron.xml39(td)
-#: ./doc/common/tables/heat-clients_keystone.xml39(td)
-msgid "(StrOpt) Optional PEM-formatted file that contains the private key."
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-filter-recon.xml7(literal)
-#: ./doc/common/tables/swift-object-server-filter-recon.xml7(literal)
-#: ./doc/common/tables/swift-container-server-filter-recon.xml7(literal)
-msgid "[filter:recon]"
-msgstr "[filter:recon]"
-
-#: ./doc/common/tables/swift-account-server-filter-recon.xml7(literal)
-#: ./doc/common/tables/swift-account-server-app-account-server.xml7(literal)
-#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml7(literal)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml7(literal)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml7(literal)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml7(literal)
-#: ./doc/common/tables/swift-account-server-pipeline-main.xml7(literal)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml7(literal)
-msgid "account-server.conf-sample"
-msgstr "account-server.conf-sample"
-
-#: ./doc/common/tables/swift-account-server-filter-recon.xml18(td)
-#: ./doc/common/tables/swift-object-server-filter-recon.xml18(td)
-#: ./doc/common/tables/swift-container-server-filter-recon.xml18(td)
-msgid "use = egg:swift#recon"
-msgstr ""
-
-#: ./doc/common/tables/cinder-huawei.xml8(caption)
-msgid "Description of configuration options for huawei"
-msgstr ""
-
-#: ./doc/common/tables/cinder-huawei.xml22(td)
-msgid "cinder_huawei_conf_file = /etc/cinder/cinder_huawei_conf.xml"
-msgstr ""
-
-#: ./doc/common/tables/cinder-huawei.xml23(td)
-msgid "(StrOpt) config data for cinder huawei plugin"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml8(caption)
-msgid "Description of configuration options for netapp_eseries_iscsi"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml22(td)
-msgid "netapp_controller_ips = None"
-msgstr "netapp_controller_ips = None"
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml23(td)
-msgid ""
-"(StrOpt) This option is only utilized when the storage family is configured "
-"to eseries. This option is used to restrict provisioning to the specified "
-"controllers. Specify the value of this option to be a comma separated list "
-"of controller hostnames or IP addresses to be used for provisioning."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml26(td)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml22(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml22(td)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml26(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml30(td)
-msgid "netapp_login = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml27(td)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml23(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml23(td)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml27(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml31(td)
-msgid ""
-"(StrOpt) Administrative user account name used to access the storage system "
-"or proxy server."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml30(td)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml26(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml26(td)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml30(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml34(td)
-msgid "netapp_password = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml31(td)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml27(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml27(td)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml31(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml35(td)
-msgid ""
-"(StrOpt) Password for the administrative user account specified in the "
-"netapp_login option."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml34(td)
-msgid "netapp_sa_password = None"
-msgstr "netapp_sa_password = None"
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml35(td)
-msgid "(StrOpt) Password for the NetApp E-Series storage array."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml38(td)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml30(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml30(td)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml34(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml38(td)
-msgid "netapp_server_hostname = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml39(td)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml31(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml31(td)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml35(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml39(td)
-msgid ""
-"(StrOpt) The hostname (or IP address) for the storage system or proxy "
-"server."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml42(td)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml34(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml34(td)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml38(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml42(td)
-msgid "netapp_server_port = 80"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml43(td)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml35(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml35(td)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml39(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml43(td)
-msgid ""
-"(IntOpt) The TCP port to use for communication with the storage system or "
-"proxy server. Traditionally, port 80 is used for HTTP and port 443 is used "
-"for HTTPS; however, this value should be changed if an alternate port has "
-"been configured on the storage system or proxy server."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml46(td)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml42(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml42(td)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml42(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml46(td)
-msgid "netapp_storage_family = ontap_cluster"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml47(td)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml43(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml43(td)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml43(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml47(td)
-msgid ""
-"(StrOpt) The storage family type used on the storage system; valid values "
-"are ontap_7mode for using Data ONTAP operating in 7-Mode, ontap_cluster for "
-"using clustered Data ONTAP, or eseries for using E-Series."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml50(td)
-msgid "netapp_storage_pools = None"
-msgstr "netapp_storage_pools = None"
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml51(td)
-msgid ""
-"(StrOpt) This option is used to restrict provisioning to the specified "
-"storage pools. Only dynamic disk pools are currently supported. Specify the "
-"value of this option to be a comma separated list of disk pool names to be "
-"used for provisioning."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml54(td)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml50(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml50(td)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml50(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml54(td)
-msgid "netapp_transport_type = http"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml55(td)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml51(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml51(td)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml51(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml55(td)
-msgid ""
-"(StrOpt) The transport protocol used when communicating with the storage "
-"system or proxy server. Valid values are http or https."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml58(td)
-msgid "netapp_webservice_path = /devmgr/v2"
-msgstr "netapp_webservice_path = /devmgr/v2"
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml59(td)
-msgid ""
-"(StrOpt) This option is used to specify the path to the E-Series proxy "
-"application on a proxy server. The value is combined with the value of the "
-"netapp_transport_type, netapp_server_hostname, and netapp_server_port "
-"options to create the URL used by the driver to connect to the proxy "
-"application."
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml7(literal)
-msgid "[container-replicator]"
-msgstr "[container-replicator]"
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml18(td)
-msgid "log_name = container-replicator"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml30(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml30(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml30(td)
-msgid "vm_test_mode = no"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml30(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml30(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml30(td)
-msgid "Indicates that you are using a VM environment"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml33(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml33(td)
-msgid "per_diff = 1000"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml33(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml33(td)
-msgid "Limit number of items to get per diff"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml36(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml36(td)
-msgid "max_diffs = 100"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml36(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml36(td)
-msgid "Caps how long the replicator spends trying to sync a database per pass"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml39(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml39(td)
-msgid "concurrency = 8"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml42(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml42(td)
-msgid "interval = 30"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml45(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml48(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml51(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml36(td)
-msgid "node_timeout = 10"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml51(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml66(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml57(td)
-msgid "reclaim_age = 604800"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml51(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml66(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml57(td)
-msgid "Time elapsed in seconds before an object can be reclaimed"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml54(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml36(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml60(td)
-msgid "run_pause = 30"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml54(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml36(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml60(td)
-msgid "Time in seconds to wait between replication passes"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml8(caption)
-msgid "Description of configuration options for glance"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml22(td)
-#: ./doc/common/tables/cinder-images.xml22(td)
-msgid "allowed_direct_url_schemes ="
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml23(td)
-msgid ""
-"(ListOpt) A list of url scheme that can be downloaded directly via the "
-"direct_url. Currently supported schemes: [file]."
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml26(td)
-#: ./doc/common/tables/cinder-images.xml26(td)
-msgid "glance_api_insecure = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml27(td)
-#: ./doc/common/tables/cinder-images.xml27(td)
-msgid "(BoolOpt) Allow to perform insecure SSL (https) requests to glance"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml30(td)
-#: ./doc/common/tables/cinder-images.xml30(td)
-msgid "glance_api_servers = $glance_host:$glance_port"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml31(td)
-msgid ""
-"(ListOpt) A list of the glance api servers available to nova. Prefix with "
-"https:// for ssl-based glance api servers. ([hostname|ip]:port)"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml34(td)
-#: ./doc/common/tables/cinder-images.xml42(td)
-msgid "glance_host = $my_ip"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml35(td)
-msgid "(StrOpt) Default glance hostname or IP address"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml38(td)
-#: ./doc/common/tables/cinder-images.xml46(td)
-msgid "glance_num_retries = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml39(td)
-msgid "(IntOpt) Number of retries when downloading an image from glance"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml42(td)
-#: ./doc/common/tables/cinder-images.xml50(td)
-msgid "glance_port = 9292"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml43(td)
-msgid "(IntOpt) Default glance port"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml46(td)
-msgid "glance_protocol = http"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml47(td)
-msgid ""
-"(StrOpt) Default protocol to use when connecting to glance. Set to https for"
-" SSL."
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml50(td)
-msgid "osapi_glance_link_prefix = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml51(td)
-msgid ""
-"(StrOpt) Base URL that will be presented to users in links to glance "
-"resources"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml54(th)
-msgid "[image_file_url]"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml57(td)
-msgid "filesystems ="
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml58(td)
-msgid ""
-"(ListOpt) List of file systems that are configured in this file in the "
-"image_file_url:&lt;list entry name&gt; sections"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml8(caption)
-msgid "Description of configuration options for dhcp_agent"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml22(td)
-#: ./doc/common/tables/nova-network.xml74(td)
-msgid "dnsmasq_config_file ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml23(td)
-#: ./doc/common/tables/nova-network.xml75(td)
-msgid "(StrOpt) Override the default dnsmasq settings with this file"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml26(td)
-msgid "dnsmasq_dns_servers = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml27(td)
-msgid ""
-"(ListOpt) Comma-separated list of the DNS servers which will be used as "
-"forwarders."
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml30(td)
-msgid "dnsmasq_lease_max = 16777216"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml31(td)
-msgid "(IntOpt) Limit number of leases to prevent a denial-of-service."
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml34(td)
-msgid "enable_isolated_metadata = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml35(td)
-msgid "(BoolOpt) Support Metadata requests on isolated networks."
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml38(td)
-msgid "enable_metadata_network = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml39(td)
-msgid ""
-"(BoolOpt) Allows for serving metadata requests from a dedicated network. "
-"Requires enable_isolated_metadata = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml42(td)
-msgid "num_sync_threads = 4"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml43(td)
-msgid "(IntOpt) Number of threads to use during sync process."
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml46(td)
-msgid "resync_interval = 5"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml47(td)
-msgid "(IntOpt) Interval to resync."
+#: ./doc/common/tables/swift-container-server-pipeline-main.xml18(td)
+msgid "pipeline = healthcheck recon container-server"
 msgstr ""
 
-#: ./doc/common/tables/neutron-dhcp_agent.xml50(td)
-msgid "use_namespaces = True"
+#: ./doc/common/tables/glance-policy.xml23(td)
+msgid "(StrOpt) The default policy to use."
 msgstr ""
 
-#: ./doc/common/tables/neutron-dhcp_agent.xml51(td)
-msgid "(BoolOpt) Allow overlapping IP."
+#: ./doc/common/tables/glance-policy.xml27(td)
+msgid "(StrOpt) The location of the policy file."
 msgstr ""
 
 #: ./doc/common/tables/nova-neutron.xml8(caption)
@@ -30564,11 +36199,6 @@ msgstr ""
 msgid "neutron_ovs_bridge = br-int"
 msgstr ""
 
-#: ./doc/common/tables/nova-neutron.xml67(td)
-#: ./doc/common/tables/nova-xen.xml157(td)
-msgid "(StrOpt) Name of Integration Bridge used by Open vSwitch"
-msgstr ""
-
 #: ./doc/common/tables/nova-neutron.xml70(td)
 msgid "neutron_region_name = None"
 msgstr ""
@@ -30603,1171 +36233,96 @@ msgid ""
 "resolve instance ids."
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml8(caption)
-msgid "Description of configuration options for backups_ceph"
+#: ./doc/common/tables/cinder-backups.xml8(caption)
+msgid "Description of configuration options for backups"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml22(td)
-msgid "backup_ceph_chunk_size = 134217728"
+#: ./doc/common/tables/cinder-backups.xml22(td)
+msgid "backup_api_class = cinder.backup.api.API"
+msgstr "backup_api_class = cinder.backup.api.API"
+
+#: ./doc/common/tables/cinder-backups.xml23(td)
+msgid "(StrOpt) The full class name of the volume backup API class"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml23(td)
+#: ./doc/common/tables/cinder-backups.xml26(td)
+msgid "backup_compression_algorithm = zlib"
+msgstr "backup_compression_algorithm = zlib"
+
+#: ./doc/common/tables/cinder-backups.xml27(td)
+msgid "(StrOpt) Compression algorithm (None to disable)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-backups.xml30(td)
+msgid "backup_driver = cinder.backup.drivers.swift"
+msgstr "backup_driver = cinder.backup.drivers.swift"
+
+#: ./doc/common/tables/cinder-backups.xml31(td)
+msgid "(StrOpt) Driver to use for backups."
+msgstr ""
+
+#: ./doc/common/tables/cinder-backups.xml34(td)
+msgid "backup_manager = cinder.backup.manager.BackupManager"
+msgstr "backup_manager = cinder.backup.manager.BackupManager"
+
+#: ./doc/common/tables/cinder-backups.xml35(td)
+msgid "(StrOpt) full class name for the Manager for volume backup"
+msgstr ""
+
+#: ./doc/common/tables/cinder-backups.xml38(td)
+msgid "backup_metadata_version = 1"
+msgstr "backup_metadata_version = 1"
+
+#: ./doc/common/tables/cinder-backups.xml39(td)
 msgid ""
-"(IntOpt) The chunk size, in bytes, that a backup is broken into before "
-"transfer to the Ceph object store."
+"(IntOpt) Backup metadata version to be used when backing up volume metadata."
+" If this number is bumped, make sure the service doing the restore supports "
+"the new version."
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml26(td)
-msgid "backup_ceph_conf = /etc/ceph/ceph.conf"
+#: ./doc/common/tables/cinder-backups.xml42(td)
+msgid "backup_name_template = backup-%s"
+msgstr "backup_name_template = backup-%s"
+
+#: ./doc/common/tables/cinder-backups.xml43(td)
+msgid "(StrOpt) Template string to be used to generate backup names"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml27(td)
-msgid "(StrOpt) Ceph configuration file to use."
+#: ./doc/common/tables/cinder-backups.xml46(td)
+msgid "backup_topic = cinder-backup"
+msgstr "backup_topic = cinder-backup"
+
+#: ./doc/common/tables/cinder-backups.xml47(td)
+msgid "(StrOpt) the topic volume backup nodes listen on"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml30(td)
-msgid "backup_ceph_pool = backups"
+#: ./doc/common/tables/cinder-backups.xml50(td)
+#: ./doc/common/tables/nova-api.xml90(td)
+msgid "snapshot_name_template = snapshot-%s"
+msgstr "snapshot_name_template = snapshot-%s"
+
+#: ./doc/common/tables/cinder-backups.xml51(td)
+#: ./doc/common/tables/nova-api.xml91(td)
+msgid "(StrOpt) Template string to be used to generate snapshot names"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml31(td)
-msgid "(StrOpt) The Ceph pool where volume backups are stored."
-msgstr ""
+#: ./doc/common/tables/cinder-backups.xml54(td)
+msgid "snapshot_same_host = True"
+msgstr "snapshot_same_host = True"
 
-#: ./doc/common/tables/cinder-backups_ceph.xml34(td)
-msgid "backup_ceph_stripe_count = 0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups_ceph.xml35(td)
-msgid "(IntOpt) RBD stripe count to use when creating a backup image."
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups_ceph.xml38(td)
-msgid "backup_ceph_stripe_unit = 0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups_ceph.xml39(td)
-msgid "(IntOpt) RBD stripe unit to use when creating a backup image."
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups_ceph.xml42(td)
-msgid "backup_ceph_user = cinder"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups_ceph.xml43(td)
+#: ./doc/common/tables/cinder-backups.xml55(td)
 msgid ""
-"(StrOpt) The Ceph user to connect with. Default here is to use the same user"
-" as for Cinder volumes. If not using cephx this should be set to None."
+"(BoolOpt) Create volume from snapshot at the host where snapshot resides"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml46(td)
-msgid "restore_discard_excess_bytes = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups_ceph.xml47(td)
-msgid ""
-"(BoolOpt) If True, always discard excess bytes when restoring volumes i.e. "
-"pad with zeroes."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml7(literal)
-msgid "[filter:name_check]"
-msgstr "[filter:name_check]"
-
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml18(td)
-msgid "use = egg:swift#name_check"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml21(td)
-msgid "forbidden_chars = '\"`&lt;&gt;"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml21(td)
-msgid "Characters that are not allowed in a name"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml24(td)
-msgid "maximum_length = 255"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml24(td)
-msgid "Maximum length of a name"
-msgstr "Longueur maximum d'un nom"
-
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml27(td)
-msgid "forbidden_regexp = /\\./|/\\.\\./|/\\.$|/\\.\\.$"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml27(td)
-msgid "Substrings to forbid, using regular expression syntax"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml8(caption)
-#: ./doc/common/tables/neutron-metadata.xml8(caption)
-msgid "Description of configuration options for metadata"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml22(td)
-msgid "metadata_host = $my_ip"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml23(td)
-msgid "(StrOpt) The IP address for the metadata API server"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml26(td)
-msgid "metadata_listen = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml27(td)
-msgid "(StrOpt) The IP address on which the metadata API will listen."
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml30(td)
-msgid "metadata_listen_port = 8775"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml31(td)
-msgid "(IntOpt) The port on which the metadata API will listen."
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml34(td)
-msgid "metadata_manager = nova.api.manager.MetadataManager"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml35(td)
-msgid "(StrOpt) OpenStack metadata service manager"
-msgstr "(StrOpt)  Gestionnaire du service des métadonnées d’OpenStack"
-
-#: ./doc/common/tables/nova-metadata.xml38(td)
-msgid "metadata_port = 8775"
-msgstr ""
+#: ./doc/common/tables/cinder-keymgr.xml22(td)
+msgid "api_class = cinder.keymgr.conf_key_mgr.ConfKeyManager"
+msgstr "api_class = cinder.keymgr.conf_key_mgr.ConfKeyManager"
 
-#: ./doc/common/tables/nova-metadata.xml39(td)
-msgid "(IntOpt) The port for the metadata API port"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml42(td)
-msgid "metadata_workers = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml43(td)
-msgid ""
-"(IntOpt) Number of workers for metadata service. The default will be the "
-"number of CPUs available."
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml46(td)
-msgid ""
-"vendordata_driver = nova.api.metadata.vendordata_json.JsonFileVendorData"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml47(td)
-msgid "(StrOpt) Driver to use for vendor data"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml50(td)
-msgid "vendordata_jsonfile_path = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml51(td)
-msgid "(StrOpt) File to load json formatted vendor data from"
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml8(caption)
-#: ./doc/common/tables/nova-s3.xml8(caption)
-msgid "Description of configuration options for s3"
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml22(td)
-msgid "s3_store_access_key = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml23(td)
-msgid "(StrOpt) The S3 query token access key."
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml26(td)
-msgid "s3_store_bucket = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml27(td)
-msgid "(StrOpt) The S3 bucket to be used to store the Glance data."
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml30(td)
-msgid "s3_store_bucket_url_format = subdomain"
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml31(td)
-msgid ""
-"(StrOpt) The S3 calling format used to determine the bucket. Either "
-"subdomain or path can be used."
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml34(td)
-msgid "s3_store_create_bucket_on_put = False"
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml35(td)
-msgid ""
-"(BoolOpt) A boolean to determine if the S3 bucket should be created on "
-"upload if it does not exist or if an error should be returned to the user."
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml38(td)
-msgid "s3_store_host = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml39(td)
-msgid "(StrOpt) The host where the S3 server is listening."
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml42(td)
-msgid "s3_store_object_buffer_dir = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml43(td)
-msgid ""
-"(StrOpt) The local directory where uploads will be staged before they are "
-"transferred into S3."
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml46(td)
-msgid "s3_store_secret_key = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml47(td)
-msgid "(StrOpt) The S3 query token secret key."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml8(caption)
-#: ./doc/common/tables/nova-auth_token.xml8(caption)
-#: ./doc/common/tables/cinder-auth_token.xml8(caption)
-#: ./doc/common/tables/trove-auth_token.xml8(caption)
-#: ./doc/common/tables/keystone-auth_token.xml8(caption)
-#: ./doc/common/tables/heat-auth_token.xml8(caption)
-#: ./doc/common/tables/neutron-auth_token.xml8(caption)
-msgid "Description of configuration options for auth_token"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml22(td)
-#: ./doc/common/tables/glance-auth_token.xml117(td)
-#: ./doc/common/tables/nova-common.xml50(td)
-#: ./doc/common/tables/nova-auth_token.xml110(td)
-#: ./doc/common/tables/cinder-auth_token.xml22(td)
-#: ./doc/common/tables/cinder-auth_token.xml117(td)
-#: ./doc/common/tables/trove-auth_token.xml22(td)
-#: ./doc/common/tables/trove-auth_token.xml117(td)
-#: ./doc/common/tables/keystone-auth_token.xml22(td)
-#: ./doc/common/tables/keystone-auth_token.xml117(td)
-#: ./doc/common/tables/ceilometer-common.xml38(td)
-#: ./doc/common/tables/ceilometer-auth.xml117(td)
-#: ./doc/common/tables/heat-auth_token.xml22(td)
-#: ./doc/common/tables/heat-auth_token.xml117(td)
-#: ./doc/common/tables/neutron-auth_token.xml22(td)
-#: ./doc/common/tables/neutron-auth_token.xml117(td)
-msgid "memcached_servers = None"
-msgstr "memcached_servers = None"
-
-#: ./doc/common/tables/glance-auth_token.xml23(td)
-#: ./doc/common/tables/nova-common.xml51(td)
-#: ./doc/common/tables/cinder-auth_token.xml23(td)
-#: ./doc/common/tables/trove-auth_token.xml23(td)
-#: ./doc/common/tables/keystone-auth_token.xml23(td)
-#: ./doc/common/tables/ceilometer-common.xml39(td)
-#: ./doc/common/tables/heat-auth_token.xml23(td)
-#: ./doc/common/tables/neutron-auth_token.xml23(td)
-msgid "(ListOpt) Memcached servers or None for in process cache."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml26(th)
-#: ./doc/common/tables/nova-auth_token.xml19(th)
-#: ./doc/common/tables/cinder-auth_token.xml26(th)
-#: ./doc/common/tables/trove-auth_token.xml26(th)
-#: ./doc/common/tables/keystone-auth_token.xml26(th)
-#: ./doc/common/tables/ceilometer-auth.xml26(th)
-#: ./doc/common/tables/heat-auth_token.xml26(th)
-#: ./doc/common/tables/neutron-auth_token.xml26(th)
-msgid "[keystone_authtoken]"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml29(td)
-#: ./doc/common/tables/neutron-common.xml22(td)
-#: ./doc/common/tables/neutron-common.xml192(td)
-#: ./doc/common/tables/neutron-common.xml219(td)
-#: ./doc/common/tables/nova-auth_token.xml22(td)
-#: ./doc/common/tables/cinder-auth_token.xml29(td)
-#: ./doc/common/tables/trove-auth_token.xml29(td)
-#: ./doc/common/tables/glance-registry.xml22(td)
-#: ./doc/common/tables/keystone-auth_token.xml29(td)
-#: ./doc/common/tables/ceilometer-auth.xml29(td)
-#: ./doc/common/tables/heat-auth_token.xml29(td)
-#: ./doc/common/tables/neutron-embrane_lb.xml22(td)
-#: ./doc/common/tables/neutron-auth_token.xml29(td)
-msgid "admin_password = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml30(td)
-#: ./doc/common/tables/nova-auth_token.xml23(td)
-#: ./doc/common/tables/cinder-auth_token.xml30(td)
-#: ./doc/common/tables/trove-auth_token.xml30(td)
-#: ./doc/common/tables/keystone-auth_token.xml30(td)
-#: ./doc/common/tables/ceilometer-auth.xml30(td)
-#: ./doc/common/tables/heat-auth_token.xml30(td)
-#: ./doc/common/tables/neutron-auth_token.xml30(td)
-msgid "(StrOpt) Keystone account password"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml33(td)
-#: ./doc/common/tables/nova-auth_token.xml26(td)
-#: ./doc/common/tables/cinder-auth_token.xml33(td)
-#: ./doc/common/tables/trove-auth_token.xml33(td)
-#: ./doc/common/tables/keystone-auth_token.xml33(td)
-#: ./doc/common/tables/ceilometer-auth.xml33(td)
-#: ./doc/common/tables/heat-auth_token.xml33(td)
-#: ./doc/common/tables/neutron-auth_token.xml33(td)
-msgid "admin_tenant_name = admin"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml34(td)
-#: ./doc/common/tables/nova-auth_token.xml27(td)
-#: ./doc/common/tables/cinder-auth_token.xml34(td)
-#: ./doc/common/tables/trove-auth_token.xml34(td)
-#: ./doc/common/tables/keystone-auth_token.xml34(td)
-#: ./doc/common/tables/ceilometer-auth.xml34(td)
-#: ./doc/common/tables/heat-auth_token.xml34(td)
-#: ./doc/common/tables/neutron-auth_token.xml34(td)
-msgid "(StrOpt) Keystone service account tenant name to validate user tokens"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml37(td)
-#: ./doc/common/tables/nova-auth_token.xml30(td)
-#: ./doc/common/tables/cinder-auth_token.xml37(td)
-#: ./doc/common/tables/trove-auth_token.xml37(td)
-#: ./doc/common/tables/keystone-auth_token.xml37(td)
-#: ./doc/common/tables/ceilometer-auth.xml37(td)
-#: ./doc/common/tables/heat-auth_token.xml37(td)
-#: ./doc/common/tables/neutron-auth_token.xml37(td)
-msgid "admin_token = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml38(td)
-#: ./doc/common/tables/nova-auth_token.xml31(td)
-#: ./doc/common/tables/cinder-auth_token.xml38(td)
-#: ./doc/common/tables/trove-auth_token.xml38(td)
-#: ./doc/common/tables/keystone-auth_token.xml38(td)
-#: ./doc/common/tables/ceilometer-auth.xml38(td)
-#: ./doc/common/tables/heat-auth_token.xml38(td)
-#: ./doc/common/tables/neutron-auth_token.xml38(td)
-msgid ""
-"(StrOpt) Single shared secret with the Keystone configuration used for "
-"bootstrapping a Keystone installation, or otherwise bypassing the normal "
-"authentication process."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml41(td)
-#: ./doc/common/tables/neutron-common.xml30(td)
-#: ./doc/common/tables/neutron-common.xml200(td)
-#: ./doc/common/tables/nova-auth_token.xml34(td)
-#: ./doc/common/tables/cinder-auth_token.xml41(td)
-#: ./doc/common/tables/trove-auth_token.xml41(td)
-#: ./doc/common/tables/glance-registry.xml30(td)
-#: ./doc/common/tables/keystone-auth_token.xml41(td)
-#: ./doc/common/tables/ceilometer-auth.xml41(td)
-#: ./doc/common/tables/heat-auth_token.xml41(td)
-#: ./doc/common/tables/neutron-auth_token.xml41(td)
-msgid "admin_user = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml42(td)
-#: ./doc/common/tables/nova-auth_token.xml35(td)
-#: ./doc/common/tables/cinder-auth_token.xml42(td)
-#: ./doc/common/tables/trove-auth_token.xml42(td)
-#: ./doc/common/tables/keystone-auth_token.xml42(td)
-#: ./doc/common/tables/ceilometer-auth.xml42(td)
-#: ./doc/common/tables/heat-auth_token.xml42(td)
-#: ./doc/common/tables/neutron-auth_token.xml42(td)
-msgid "(StrOpt) Keystone account username"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml45(td)
-#: ./doc/common/tables/nova-auth_token.xml38(td)
-#: ./doc/common/tables/cinder-auth_token.xml45(td)
-#: ./doc/common/tables/trove-auth_token.xml45(td)
-#: ./doc/common/tables/keystone-auth_token.xml45(td)
-#: ./doc/common/tables/ceilometer-auth.xml45(td)
-#: ./doc/common/tables/heat-auth_token.xml45(td)
-#: ./doc/common/tables/neutron-auth_token.xml45(td)
-msgid "auth_admin_prefix ="
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml46(td)
-#: ./doc/common/tables/nova-auth_token.xml39(td)
-#: ./doc/common/tables/cinder-auth_token.xml46(td)
-#: ./doc/common/tables/trove-auth_token.xml46(td)
-#: ./doc/common/tables/keystone-auth_token.xml46(td)
-#: ./doc/common/tables/ceilometer-auth.xml46(td)
-#: ./doc/common/tables/heat-auth_token.xml46(td)
-#: ./doc/common/tables/neutron-auth_token.xml46(td)
-msgid "(StrOpt) Prefix to prepend at the beginning of the path"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml49(td)
-#: ./doc/common/tables/nova-auth_token.xml42(td)
-#: ./doc/common/tables/cinder-auth_token.xml49(td)
-#: ./doc/common/tables/trove-auth_token.xml49(td)
-#: ./doc/common/tables/keystone-auth_token.xml49(td)
-#: ./doc/common/tables/ceilometer-auth.xml49(td)
-#: ./doc/common/tables/heat-auth_token.xml49(td)
-#: ./doc/common/tables/neutron-auth_token.xml49(td)
-msgid "auth_host = 127.0.0.1"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml50(td)
-#: ./doc/common/tables/nova-auth_token.xml43(td)
-#: ./doc/common/tables/cinder-auth_token.xml50(td)
-#: ./doc/common/tables/trove-auth_token.xml50(td)
-#: ./doc/common/tables/keystone-auth_token.xml50(td)
-#: ./doc/common/tables/ceilometer-auth.xml50(td)
-#: ./doc/common/tables/heat-auth_token.xml50(td)
-#: ./doc/common/tables/neutron-auth_token.xml50(td)
-msgid "(StrOpt) Host providing the admin Identity API endpoint"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml53(td)
-#: ./doc/common/tables/nova-auth_token.xml46(td)
-#: ./doc/common/tables/cinder-auth_token.xml53(td)
-#: ./doc/common/tables/trove-auth_token.xml53(td)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml21(td)
-#: ./doc/common/tables/keystone-auth_token.xml53(td)
-#: ./doc/common/tables/ceilometer-auth.xml53(td)
-#: ./doc/common/tables/heat-auth_token.xml53(td)
-#: ./doc/common/tables/neutron-auth_token.xml53(td)
-msgid "auth_port = 35357"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml54(td)
-#: ./doc/common/tables/nova-auth_token.xml47(td)
-#: ./doc/common/tables/cinder-auth_token.xml54(td)
-#: ./doc/common/tables/trove-auth_token.xml54(td)
-#: ./doc/common/tables/keystone-auth_token.xml54(td)
-#: ./doc/common/tables/ceilometer-auth.xml54(td)
-#: ./doc/common/tables/heat-auth_token.xml54(td)
-#: ./doc/common/tables/neutron-auth_token.xml54(td)
-msgid "(IntOpt) Port of the admin Identity API endpoint"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml57(td)
-#: ./doc/common/tables/nova-auth_token.xml50(td)
-#: ./doc/common/tables/cinder-auth_token.xml57(td)
-#: ./doc/common/tables/trove-auth_token.xml57(td)
-#: ./doc/common/tables/keystone-auth_token.xml57(td)
-#: ./doc/common/tables/ceilometer-auth.xml57(td)
-#: ./doc/common/tables/heat-auth_token.xml57(td)
-#: ./doc/common/tables/neutron-auth_token.xml57(td)
-msgid "auth_protocol = https"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml58(td)
-#: ./doc/common/tables/nova-auth_token.xml51(td)
-#: ./doc/common/tables/cinder-auth_token.xml58(td)
-#: ./doc/common/tables/trove-auth_token.xml58(td)
-#: ./doc/common/tables/keystone-auth_token.xml58(td)
-#: ./doc/common/tables/ceilometer-auth.xml58(td)
-#: ./doc/common/tables/heat-auth_token.xml58(td)
-#: ./doc/common/tables/neutron-auth_token.xml58(td)
-msgid "(StrOpt) Protocol of the admin Identity API endpoint(http or https)"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml61(td)
-#: ./doc/common/tables/nova-auth_token.xml54(td)
-#: ./doc/common/tables/cinder-auth_token.xml61(td)
-#: ./doc/common/tables/trove-auth_token.xml61(td)
-#: ./doc/common/tables/heat-api.xml92(td)
-#: ./doc/common/tables/keystone-auth_token.xml61(td)
-#: ./doc/common/tables/ceilometer-auth.xml61(td)
-#: ./doc/common/tables/heat-auth_token.xml61(td)
-#: ./doc/common/tables/neutron-auth_token.xml61(td)
-msgid "auth_uri = None"
-msgstr "auth_uri = None"
-
-#: ./doc/common/tables/glance-auth_token.xml62(td)
-#: ./doc/common/tables/nova-auth_token.xml55(td)
-#: ./doc/common/tables/cinder-auth_token.xml62(td)
-#: ./doc/common/tables/trove-auth_token.xml62(td)
-#: ./doc/common/tables/keystone-auth_token.xml62(td)
-#: ./doc/common/tables/ceilometer-auth.xml62(td)
-#: ./doc/common/tables/heat-auth_token.xml62(td)
-#: ./doc/common/tables/neutron-auth_token.xml62(td)
-msgid "(StrOpt) Complete public Identity API endpoint"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml65(td)
-#: ./doc/common/tables/nova-auth_token.xml58(td)
-#: ./doc/common/tables/cinder-auth_token.xml65(td)
-#: ./doc/common/tables/trove-auth_token.xml65(td)
-#: ./doc/common/tables/keystone-auth_token.xml65(td)
-#: ./doc/common/tables/ceilometer-auth.xml65(td)
-#: ./doc/common/tables/heat-auth_token.xml65(td)
-#: ./doc/common/tables/neutron-auth_token.xml65(td)
-msgid "auth_version = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml66(td)
-#: ./doc/common/tables/nova-auth_token.xml59(td)
-#: ./doc/common/tables/cinder-auth_token.xml66(td)
-#: ./doc/common/tables/trove-auth_token.xml66(td)
-#: ./doc/common/tables/keystone-auth_token.xml66(td)
-#: ./doc/common/tables/ceilometer-auth.xml66(td)
-#: ./doc/common/tables/heat-auth_token.xml66(td)
-#: ./doc/common/tables/neutron-auth_token.xml66(td)
-msgid "(StrOpt) API version of the admin Identity API endpoint"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml69(td)
-#: ./doc/common/tables/nova-auth_token.xml62(td)
-#: ./doc/common/tables/cinder-auth_token.xml69(td)
-#: ./doc/common/tables/trove-auth_token.xml69(td)
-#: ./doc/common/tables/keystone-auth_token.xml69(td)
-#: ./doc/common/tables/ceilometer-auth.xml69(td)
-#: ./doc/common/tables/heat-auth_token.xml69(td)
-#: ./doc/common/tables/neutron-auth_token.xml69(td)
-msgid "cache = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml70(td)
-#: ./doc/common/tables/nova-auth_token.xml63(td)
-#: ./doc/common/tables/cinder-auth_token.xml70(td)
-#: ./doc/common/tables/trove-auth_token.xml70(td)
-#: ./doc/common/tables/keystone-auth_token.xml70(td)
-#: ./doc/common/tables/ceilometer-auth.xml70(td)
-#: ./doc/common/tables/heat-auth_token.xml70(td)
-#: ./doc/common/tables/neutron-auth_token.xml70(td)
-msgid "(StrOpt) Env key for the swift cache"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml73(td)
-#: ./doc/common/tables/nova-auth_token.xml66(td)
-#: ./doc/common/tables/cinder-auth_token.xml73(td)
-#: ./doc/common/tables/trove-auth_token.xml73(td)
-#: ./doc/common/tables/keystone-auth_token.xml73(td)
-#: ./doc/common/tables/ceilometer-auth.xml73(td)
-#: ./doc/common/tables/heat-auth_token.xml73(td)
-#: ./doc/common/tables/neutron-auth_token.xml73(td)
-msgid "cafile = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml74(td)
-#: ./doc/common/tables/nova-auth_token.xml67(td)
-#: ./doc/common/tables/cinder-auth_token.xml74(td)
-#: ./doc/common/tables/trove-auth_token.xml74(td)
-#: ./doc/common/tables/keystone-auth_token.xml74(td)
-#: ./doc/common/tables/ceilometer-auth.xml74(td)
-#: ./doc/common/tables/heat-auth_token.xml74(td)
-#: ./doc/common/tables/neutron-auth_token.xml74(td)
-msgid ""
-"(StrOpt) A PEM encoded Certificate Authority to use when verifying HTTPs "
-"connections. Defaults to system CAs."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml77(td)
-#: ./doc/common/tables/nova-auth_token.xml70(td)
-#: ./doc/common/tables/cinder-auth_token.xml77(td)
-#: ./doc/common/tables/trove-auth_token.xml77(td)
-#: ./doc/common/tables/keystone-auth_token.xml77(td)
-#: ./doc/common/tables/ceilometer-auth.xml77(td)
-#: ./doc/common/tables/heat-auth_token.xml77(td)
-#: ./doc/common/tables/neutron-auth_token.xml77(td)
-msgid "certfile = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml78(td)
-#: ./doc/common/tables/glance-auth_token.xml106(td)
-#: ./doc/common/tables/nova-auth_token.xml71(td)
-#: ./doc/common/tables/nova-auth_token.xml99(td)
-#: ./doc/common/tables/cinder-auth_token.xml78(td)
-#: ./doc/common/tables/cinder-auth_token.xml106(td)
-#: ./doc/common/tables/trove-auth_token.xml78(td)
-#: ./doc/common/tables/trove-auth_token.xml106(td)
-#: ./doc/common/tables/keystone-auth_token.xml78(td)
-#: ./doc/common/tables/keystone-auth_token.xml106(td)
-#: ./doc/common/tables/ceilometer-auth.xml78(td)
-#: ./doc/common/tables/ceilometer-auth.xml106(td)
-#: ./doc/common/tables/heat-auth_token.xml78(td)
-#: ./doc/common/tables/heat-auth_token.xml106(td)
-#: ./doc/common/tables/neutron-auth_token.xml78(td)
-#: ./doc/common/tables/neutron-auth_token.xml106(td)
-msgid "(StrOpt) Required if Keystone server requires client certificate"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml81(td)
-#: ./doc/common/tables/nova-auth_token.xml74(td)
-#: ./doc/common/tables/cinder-auth_token.xml81(td)
-#: ./doc/common/tables/trove-auth_token.xml81(td)
-#: ./doc/common/tables/keystone-auth_token.xml81(td)
-#: ./doc/common/tables/ceilometer-auth.xml81(td)
-#: ./doc/common/tables/heat-auth_token.xml81(td)
-#: ./doc/common/tables/neutron-auth_token.xml81(td)
-msgid "delay_auth_decision = False"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml82(td)
-#: ./doc/common/tables/nova-auth_token.xml75(td)
-#: ./doc/common/tables/cinder-auth_token.xml82(td)
-#: ./doc/common/tables/trove-auth_token.xml82(td)
-#: ./doc/common/tables/keystone-auth_token.xml82(td)
-#: ./doc/common/tables/ceilometer-auth.xml82(td)
-#: ./doc/common/tables/heat-auth_token.xml82(td)
-#: ./doc/common/tables/neutron-auth_token.xml82(td)
-msgid ""
-"(BoolOpt) Do not handle authorization requests within the middleware, but "
-"delegate the authorization decision to downstream WSGI components"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml85(td)
-#: ./doc/common/tables/nova-auth_token.xml78(td)
-#: ./doc/common/tables/cinder-auth_token.xml85(td)
-#: ./doc/common/tables/trove-auth_token.xml85(td)
-#: ./doc/common/tables/keystone-token.xml38(td)
-#: ./doc/common/tables/keystone-auth_token.xml85(td)
-#: ./doc/common/tables/ceilometer-auth.xml85(td)
-#: ./doc/common/tables/heat-auth_token.xml85(td)
-#: ./doc/common/tables/neutron-auth_token.xml85(td)
-msgid "enforce_token_bind = permissive"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml86(td)
-#: ./doc/common/tables/nova-auth_token.xml79(td)
-#: ./doc/common/tables/cinder-auth_token.xml86(td)
-#: ./doc/common/tables/trove-auth_token.xml86(td)
-#: ./doc/common/tables/keystone-auth_token.xml86(td)
-#: ./doc/common/tables/ceilometer-auth.xml86(td)
-#: ./doc/common/tables/heat-auth_token.xml86(td)
-#: ./doc/common/tables/neutron-auth_token.xml86(td)
-msgid ""
-"(StrOpt) Used to control the use and type of token binding. Can be set to: "
-"\"disabled\" to not check token binding. \"permissive\" (default) to "
-"validate binding information if the bind type is of a form known to the "
-"server and ignore it if not. \"strict\" like \"permissive\" but if the bind "
-"type is unknown the token will be rejected. \"required\" any form of token "
-"binding is needed to be allowed. Finally the name of a binding method that "
-"must be present in tokens."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml89(td)
-#: ./doc/common/tables/nova-auth_token.xml82(td)
-#: ./doc/common/tables/cinder-auth_token.xml89(td)
-#: ./doc/common/tables/trove-auth_token.xml89(td)
-#: ./doc/common/tables/keystone-auth_token.xml89(td)
-#: ./doc/common/tables/ceilometer-auth.xml89(td)
-#: ./doc/common/tables/heat-auth_token.xml89(td)
-#: ./doc/common/tables/neutron-auth_token.xml89(td)
-msgid "http_connect_timeout = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml90(td)
-#: ./doc/common/tables/nova-auth_token.xml83(td)
-#: ./doc/common/tables/cinder-auth_token.xml90(td)
-#: ./doc/common/tables/trove-auth_token.xml90(td)
-#: ./doc/common/tables/keystone-auth_token.xml90(td)
-#: ./doc/common/tables/ceilometer-auth.xml90(td)
-#: ./doc/common/tables/heat-auth_token.xml90(td)
-#: ./doc/common/tables/neutron-auth_token.xml90(td)
-msgid ""
-"(BoolOpt) Request timeout value for communicating with Identity API server."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml93(td)
-#: ./doc/common/tables/nova-auth_token.xml86(td)
-#: ./doc/common/tables/cinder-auth_token.xml93(td)
-#: ./doc/common/tables/trove-auth_token.xml93(td)
-#: ./doc/common/tables/keystone-auth_token.xml93(td)
-#: ./doc/common/tables/ceilometer-auth.xml93(td)
-#: ./doc/common/tables/heat-auth_token.xml93(td)
-#: ./doc/common/tables/neutron-auth_token.xml93(td)
-msgid "http_request_max_retries = 3"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml94(td)
-#: ./doc/common/tables/nova-auth_token.xml87(td)
-#: ./doc/common/tables/cinder-auth_token.xml94(td)
-#: ./doc/common/tables/trove-auth_token.xml94(td)
-#: ./doc/common/tables/keystone-auth_token.xml94(td)
-#: ./doc/common/tables/ceilometer-auth.xml94(td)
-#: ./doc/common/tables/heat-auth_token.xml94(td)
-#: ./doc/common/tables/neutron-auth_token.xml94(td)
-msgid ""
-"(IntOpt) How many times are we trying to reconnect when communicating with "
-"Identity API Server."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml97(td)
-#: ./doc/common/tables/nova-auth_token.xml90(td)
-#: ./doc/common/tables/cinder-auth_token.xml97(td)
-#: ./doc/common/tables/trove-auth_token.xml97(td)
-#: ./doc/common/tables/keystone-auth_token.xml97(td)
-#: ./doc/common/tables/ceilometer-auth.xml97(td)
-#: ./doc/common/tables/heat-auth_token.xml97(td)
-#: ./doc/common/tables/neutron-auth_token.xml97(td)
-msgid "include_service_catalog = True"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml98(td)
-#: ./doc/common/tables/nova-auth_token.xml91(td)
-#: ./doc/common/tables/cinder-auth_token.xml98(td)
-#: ./doc/common/tables/trove-auth_token.xml98(td)
-#: ./doc/common/tables/keystone-auth_token.xml98(td)
-#: ./doc/common/tables/ceilometer-auth.xml98(td)
-#: ./doc/common/tables/heat-auth_token.xml98(td)
-#: ./doc/common/tables/neutron-auth_token.xml98(td)
-msgid ""
-"(BoolOpt) (optional) indicate whether to set the X-Service-Catalog header. "
-"If False, middleware will not ask for service catalog on token validation "
-"and will not set the X-Service-Catalog header."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml102(td)
-#: ./doc/common/tables/nova-auth_token.xml95(td)
-#: ./doc/common/tables/cinder-auth_token.xml102(td)
-#: ./doc/common/tables/trove-auth_token.xml102(td)
-#: ./doc/common/tables/keystone-auth_token.xml102(td)
-#: ./doc/common/tables/ceilometer-auth.xml102(td)
-#: ./doc/common/tables/heat-auth_token.xml102(td)
-#: ./doc/common/tables/neutron-auth_token.xml102(td)
-msgid "(BoolOpt) Verify HTTPS connections."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml105(td)
-#: ./doc/common/tables/nova-auth_token.xml98(td)
-#: ./doc/common/tables/cinder-auth_token.xml105(td)
-#: ./doc/common/tables/trove-auth_token.xml105(td)
-#: ./doc/common/tables/keystone-auth_token.xml105(td)
-#: ./doc/common/tables/ceilometer-auth.xml105(td)
-#: ./doc/common/tables/heat-auth_token.xml105(td)
-#: ./doc/common/tables/neutron-auth_token.xml105(td)
-msgid "keyfile = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml109(td)
-#: ./doc/common/tables/nova-auth_token.xml102(td)
-#: ./doc/common/tables/cinder-auth_token.xml109(td)
-#: ./doc/common/tables/trove-auth_token.xml109(td)
-#: ./doc/common/tables/keystone-auth_token.xml109(td)
-#: ./doc/common/tables/ceilometer-auth.xml109(td)
-#: ./doc/common/tables/heat-auth_token.xml109(td)
-#: ./doc/common/tables/neutron-auth_token.xml109(td)
-msgid "memcache_secret_key = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml110(td)
-#: ./doc/common/tables/nova-auth_token.xml103(td)
-#: ./doc/common/tables/cinder-auth_token.xml110(td)
-#: ./doc/common/tables/trove-auth_token.xml110(td)
-#: ./doc/common/tables/keystone-auth_token.xml110(td)
-#: ./doc/common/tables/ceilometer-auth.xml110(td)
-#: ./doc/common/tables/heat-auth_token.xml110(td)
-#: ./doc/common/tables/neutron-auth_token.xml110(td)
-msgid ""
-"(StrOpt) (optional, mandatory if memcache_security_strategy is defined) this"
-" string is used for key derivation."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml113(td)
-#: ./doc/common/tables/nova-auth_token.xml106(td)
-#: ./doc/common/tables/cinder-auth_token.xml113(td)
-#: ./doc/common/tables/trove-auth_token.xml113(td)
-#: ./doc/common/tables/keystone-auth_token.xml113(td)
-#: ./doc/common/tables/ceilometer-auth.xml113(td)
-#: ./doc/common/tables/heat-auth_token.xml113(td)
-#: ./doc/common/tables/neutron-auth_token.xml113(td)
-msgid "memcache_security_strategy = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml114(td)
-#: ./doc/common/tables/nova-auth_token.xml107(td)
-#: ./doc/common/tables/cinder-auth_token.xml114(td)
-#: ./doc/common/tables/trove-auth_token.xml114(td)
-#: ./doc/common/tables/keystone-auth_token.xml114(td)
-#: ./doc/common/tables/ceilometer-auth.xml114(td)
-#: ./doc/common/tables/heat-auth_token.xml114(td)
-#: ./doc/common/tables/neutron-auth_token.xml114(td)
-msgid ""
-"(StrOpt) (optional) if defined, indicate whether token data should be "
-"authenticated or authenticated and encrypted. Acceptable values are MAC or "
-"ENCRYPT. If MAC, token data is authenticated (with HMAC) in the cache. If "
-"ENCRYPT, token data is encrypted and authenticated in the cache. If the "
-"value is not one of these options or empty, auth_token will raise an "
-"exception on initialization."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml118(td)
-#: ./doc/common/tables/nova-auth_token.xml111(td)
-#: ./doc/common/tables/cinder-auth_token.xml118(td)
-#: ./doc/common/tables/trove-auth_token.xml118(td)
-#: ./doc/common/tables/keystone-auth_token.xml118(td)
-#: ./doc/common/tables/ceilometer-auth.xml118(td)
-#: ./doc/common/tables/heat-auth_token.xml118(td)
-#: ./doc/common/tables/neutron-auth_token.xml118(td)
-msgid ""
-"(ListOpt) Optionally specify a list of memcached server(s) to use for "
-"caching. If left undefined, tokens will instead be cached in-process."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml121(td)
-#: ./doc/common/tables/nova-auth_token.xml114(td)
-#: ./doc/common/tables/cinder-auth_token.xml121(td)
-#: ./doc/common/tables/trove-auth_token.xml121(td)
-#: ./doc/common/tables/keystone-auth_token.xml121(td)
-#: ./doc/common/tables/ceilometer-auth.xml121(td)
-#: ./doc/common/tables/heat-auth_token.xml121(td)
-#: ./doc/common/tables/neutron-auth_token.xml121(td)
-msgid "revocation_cache_time = 300"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml122(td)
-#: ./doc/common/tables/nova-auth_token.xml115(td)
-#: ./doc/common/tables/cinder-auth_token.xml122(td)
-#: ./doc/common/tables/trove-auth_token.xml122(td)
-#: ./doc/common/tables/keystone-auth_token.xml122(td)
-#: ./doc/common/tables/ceilometer-auth.xml122(td)
-#: ./doc/common/tables/heat-auth_token.xml122(td)
-#: ./doc/common/tables/neutron-auth_token.xml122(td)
-msgid ""
-"(IntOpt) Determines the frequency at which the list of revoked tokens is "
-"retrieved from the Identity service (in seconds). A high number of "
-"revocation events combined with a low cache duration may significantly "
-"reduce performance."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml125(td)
-#: ./doc/common/tables/nova-auth_token.xml118(td)
-#: ./doc/common/tables/cinder-auth_token.xml125(td)
-#: ./doc/common/tables/trove-auth_token.xml125(td)
-#: ./doc/common/tables/keystone-auth_token.xml125(td)
-#: ./doc/common/tables/ceilometer-auth.xml125(td)
-#: ./doc/common/tables/heat-auth_token.xml125(td)
-#: ./doc/common/tables/neutron-auth_token.xml125(td)
-msgid "signing_dir = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml126(td)
-#: ./doc/common/tables/nova-auth_token.xml119(td)
-#: ./doc/common/tables/cinder-auth_token.xml126(td)
-#: ./doc/common/tables/trove-auth_token.xml126(td)
-#: ./doc/common/tables/keystone-auth_token.xml126(td)
-#: ./doc/common/tables/ceilometer-auth.xml126(td)
-#: ./doc/common/tables/heat-auth_token.xml126(td)
-#: ./doc/common/tables/neutron-auth_token.xml126(td)
-msgid "(StrOpt) Directory used to cache files related to PKI tokens"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml129(td)
-#: ./doc/common/tables/nova-auth_token.xml122(td)
-#: ./doc/common/tables/cinder-auth_token.xml129(td)
-#: ./doc/common/tables/trove-auth_token.xml129(td)
-#: ./doc/common/tables/keystone-auth_token.xml129(td)
-#: ./doc/common/tables/ceilometer-auth.xml129(td)
-#: ./doc/common/tables/heat-auth_token.xml129(td)
-#: ./doc/common/tables/neutron-auth_token.xml129(td)
-msgid "token_cache_time = 300"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml130(td)
-#: ./doc/common/tables/nova-auth_token.xml123(td)
-#: ./doc/common/tables/cinder-auth_token.xml130(td)
-#: ./doc/common/tables/trove-auth_token.xml130(td)
-#: ./doc/common/tables/keystone-auth_token.xml130(td)
-#: ./doc/common/tables/ceilometer-auth.xml130(td)
-#: ./doc/common/tables/heat-auth_token.xml130(td)
-#: ./doc/common/tables/neutron-auth_token.xml130(td)
-msgid ""
-"(IntOpt) In order to prevent excessive effort spent validating tokens, the "
-"middleware caches previously-seen tokens for a configurable duration (in "
-"seconds). Set to -1 to disable caching completely."
-msgstr ""
-
-#: ./doc/common/tables/neutron-kombu.xml8(caption)
-#: ./doc/common/tables/nova-kombu.xml8(caption)
-msgid "Description of configuration options for kombu"
-msgstr ""
-
-#: ./doc/common/tables/neutron-kombu.xml23(td)
-#: ./doc/common/tables/heat-rabbitmq.xml23(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml27(td)
-#: ./doc/common/tables/trove-amqp.xml43(td)
-msgid "(StrOpt) SSL certification authority file (valid only if SSL enabled)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-kombu.xml27(td)
-#: ./doc/common/tables/heat-rabbitmq.xml27(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml31(td)
-#: ./doc/common/tables/trove-amqp.xml47(td)
-msgid "(StrOpt) SSL cert file (valid only if SSL enabled)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-kombu.xml31(td)
-#: ./doc/common/tables/heat-rabbitmq.xml31(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml35(td)
-#: ./doc/common/tables/trove-amqp.xml51(td)
-msgid "(StrOpt) SSL key file (valid only if SSL enabled)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-kombu.xml35(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml39(td)
-msgid ""
-"(StrOpt) If SSL is enabled, the SSL version to use. Valid values are TLSv1, "
-"SSLv23 and SSLv3. SSLv2 might be available on some distributions."
-msgstr ""
-
-#: ./doc/common/tables/trove-redis.xml38(td)
-#: ./doc/common/tables/heat-rpc.xml62(td)
-#: ./doc/common/tables/ceilometer-redis.xml53(td)
-#: ./doc/common/tables/neutron-rpc.xml77(td)
-msgid "(StrOpt) Matchmaker ring file (JSON)"
-msgstr ""
-
-#: ./doc/common/tables/trove-qpid.xml23(td)
-#: ./doc/common/tables/heat-qpid.xml23(td)
-#: ./doc/common/tables/neutron-qpid.xml23(td)
-#: ./doc/common/tables/ceilometer-qpid.xml23(td)
-msgid "(IntOpt) Seconds between connection keepalive heartbeats"
-msgstr ""
-
-#: ./doc/common/tables/trove-qpid.xml27(td)
-#: ./doc/common/tables/heat-qpid.xml27(td)
-#: ./doc/common/tables/neutron-qpid.xml27(td)
-#: ./doc/common/tables/ceilometer-qpid.xml27(td)
-msgid "(StrOpt) Qpid broker hostname"
-msgstr ""
-
-#: ./doc/common/tables/trove-qpid.xml31(td)
-#: ./doc/common/tables/heat-qpid.xml31(td)
-#: ./doc/common/tables/neutron-qpid.xml31(td)
-#: ./doc/common/tables/ceilometer-qpid.xml31(td)
-msgid "(ListOpt) Qpid HA cluster host:port pairs"
-msgstr ""
-
-#: ./doc/common/tables/trove-qpid.xml35(td)
-#: ./doc/common/tables/heat-qpid.xml35(td)
-#: ./doc/common/tables/neutron-qpid.xml35(td)
-#: ./doc/common/tables/ceilometer-qpid.xml35(td)
-msgid "(StrOpt) Password for qpid connection"
-msgstr ""
-
-#: ./doc/common/tables/trove-qpid.xml39(td)
-#: ./doc/common/tables/heat-qpid.xml39(td)
-#: ./doc/common/tables/neutron-qpid.xml39(td)
-#: ./doc/common/tables/ceilometer-qpid.xml39(td)
-msgid "(IntOpt) Qpid broker port"
-msgstr ""
-
-#: ./doc/common/tables/trove-qpid.xml43(td)
-#: ./doc/common/tables/heat-qpid.xml43(td)
-#: ./doc/common/tables/neutron-qpid.xml43(td)
-#: ./doc/common/tables/ceilometer-qpid.xml43(td)
-msgid "(StrOpt) Transport to use, either 'tcp' or 'ssl'"
-msgstr ""
-
-#: ./doc/common/tables/trove-qpid.xml47(td)
-#: ./doc/common/tables/heat-qpid.xml47(td)
-#: ./doc/common/tables/neutron-qpid.xml47(td)
-#: ./doc/common/tables/ceilometer-qpid.xml47(td)
-msgid "(StrOpt) Space separated list of SASL mechanisms to use for auth"
-msgstr ""
-
-#: ./doc/common/tables/trove-qpid.xml51(td)
-#: ./doc/common/tables/heat-qpid.xml51(td)
-#: ./doc/common/tables/neutron-qpid.xml51(td)
-#: ./doc/common/tables/ceilometer-qpid.xml51(td)
-msgid "(BoolOpt) Disable Nagle algorithm"
-msgstr ""
-
-#: ./doc/common/tables/trove-qpid.xml55(td)
-#: ./doc/common/tables/heat-qpid.xml59(td)
-#: ./doc/common/tables/neutron-qpid.xml59(td)
-#: ./doc/common/tables/ceilometer-qpid.xml59(td)
-msgid "(StrOpt) Username for qpid connection"
-msgstr ""
-
-#: ./doc/common/tables/trove-compute.xml8(caption)
-#: ./doc/common/tables/neutron-compute.xml8(caption)
-#: ./doc/common/tables/cinder-compute.xml8(caption)
-#: ./doc/common/tables/nova-compute.xml8(caption)
-msgid "Description of configuration options for compute"
-msgstr ""
-
-#: ./doc/common/tables/trove-compute.xml22(td)
-msgid "ip_regex = None"
-msgstr "ip_regex = None"
-
-#: ./doc/common/tables/trove-compute.xml26(td)
-msgid "nova_compute_url = http://localhost:8774/v2"
-msgstr "nova_compute_url = http://localhost:8774/v2"
-
-#: ./doc/common/tables/trove-compute.xml30(td)
-msgid "root_grant = ALL"
-msgstr "root_grant = ALL"
-
-#: ./doc/common/tables/trove-compute.xml31(td)
-#: ./doc/common/tables/trove-api.xml23(td)
-#: ./doc/common/tables/trove-guestagent.xml43(td)
-#: ./doc/common/tables/trove-guestagent.xml47(td)
-msgid "(ListOpt) No help text available for this option."
-msgstr ""
-
-#: ./doc/common/tables/trove-compute.xml34(td)
-msgid "root_grant_option = True"
-msgstr "root_grant_option = True"
-
-#: ./doc/common/tables/trove-compute.xml35(td)
-#: ./doc/common/tables/trove-api.xml99(td)
-#: ./doc/common/tables/trove-taskmanager.xml71(td)
-#: ./doc/common/tables/trove-taskmanager.xml75(td)
-#: ./doc/common/tables/trove-database.xml31(td)
-#: ./doc/common/tables/trove-dns.xml83(td)
-msgid "(BoolOpt) No help text available for this option."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml7(literal)
-msgid "[filter:ratelimit]"
-msgstr "[filter:ratelimit]"
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml18(td)
-msgid "use = egg:swift#ratelimit"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml21(td)
-msgid "set log_name = ratelimit"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml36(td)
-msgid "clock_accuracy = 1000"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml36(td)
-msgid ""
-"Represents how accurate the proxy servers' system clocks are with each "
-"other. 1000 means that all the proxies' clock are accurate to each other "
-"within 1 millisecond. No ratelimit should be higher than the clock accuracy."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml39(td)
-msgid "max_sleep_time_seconds = 60"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml39(td)
-msgid ""
-"App will immediately return a 498 response if the necessary sleep time ever "
-"exceeds the given max_sleep_time_seconds."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml42(td)
-msgid "log_sleep_time_seconds = 0"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml42(td)
-msgid ""
-"To allow visibility into rate limiting set this value &gt; 0 and all sleeps "
-"greater than the number will be logged."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml45(td)
-msgid "rate_buffer_seconds = 5"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml45(td)
-msgid ""
-"Number of seconds the rate counter can drop and be allowed to catch up (at a"
-" faster than listed rate). A larger number will result in larger spikes in "
-"rate but better average accuracy."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml48(td)
-msgid "account_ratelimit = 0"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml48(td)
-msgid ""
-"If set, will limit PUT and DELETE requests to /account_name/container_name. "
-"Number is in requests per second."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml51(td)
-msgid "account_whitelist = a,b"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml51(td)
-msgid "Comma separated lists of account names that will not be rate limited."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml54(td)
-msgid "account_blacklist = c,d"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml54(td)
-msgid ""
-"Comma separated lists of account names that will not be allowed. Returns a "
-"497 response. r: for containers of size x, limit requests per second to r. "
-"Will limit PUT, DELETE, and POST requests to /a/c/o. "
-"container_listing_ratelimit_x = r: for containers of size x, limit listing "
-"requests per second to r. Will limit GET requests to /a/c."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml57(td)
-msgid "with container_limit_x = r"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml60(td)
-msgid "container_ratelimit_0 = 100"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml63(td)
-msgid "container_ratelimit_10 = 50"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml66(td)
-msgid "container_ratelimit_50 = 20"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml69(td)
-msgid "container_listing_ratelimit_0 = 100"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml72(td)
-msgid "container_listing_ratelimit_10 = 50"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml75(td)
-msgid "container_listing_ratelimit_50 = 20"
-msgstr ""
-
-#: ./doc/common/tables/trove-nova.xml8(caption)
-msgid "Description of configuration options for nova"
-msgstr ""
-
-#: ./doc/common/tables/trove-nova.xml22(td)
-msgid "nova_proxy_admin_pass ="
-msgstr "nova_proxy_admin_pass ="
-
-#: ./doc/common/tables/trove-nova.xml23(td)
-msgid "(StrOpt) Admin password used to connect to nova,"
-msgstr ""
-
-#: ./doc/common/tables/trove-nova.xml26(td)
-msgid "nova_proxy_admin_tenant_name ="
-msgstr "nova_proxy_admin_tenant_name ="
-
-#: ./doc/common/tables/trove-nova.xml27(td)
-msgid "(StrOpt) Admin tenant used to connect to nova."
-msgstr ""
-
-#: ./doc/common/tables/trove-nova.xml30(td)
-msgid "nova_proxy_admin_user ="
-msgstr "nova_proxy_admin_user ="
-
-#: ./doc/common/tables/trove-nova.xml31(td)
-msgid "(StrOpt) Admin username used to connect to nova."
-msgstr ""
+#: ./doc/common/tables/ceilometer-cells.xml8(caption)
+#: ./doc/common/tables/nova-cells.xml8(caption)
+msgid "Description of configuration options for cells"
+msgstr "Description des options de configuration pour les cellules"
 
 #: ./doc/common/tables/ceilometer-cells.xml22(td)
 #: ./doc/common/tables/nova-quota.xml85(td)
@@ -31779,696 +36334,99 @@ msgstr ""
 msgid "(IntOpt) Seconds between bandwidth updates for cells."
 msgstr ""
 
-#: ./doc/common/tables/keystone-oauth.xml8(caption)
-msgid "Description of configuration options for oauth"
+#: ./doc/common/tables/ceilometer-cells.xml26(td)
+#: ./doc/common/tables/nova-cells.xml22(td)
+msgid "call_timeout = 60"
 msgstr ""
 
-#: ./doc/common/tables/keystone-oauth.xml19(th)
-msgid "[oauth1]"
+#: ./doc/common/tables/ceilometer-cells.xml27(td)
+#: ./doc/common/tables/nova-cells.xml23(td)
+msgid "(IntOpt) Seconds to wait for response from a call to a cell."
 msgstr ""
 
-#: ./doc/common/tables/keystone-oauth.xml22(td)
-msgid "access_token_duration = 86400"
+#: ./doc/common/tables/ceilometer-cells.xml30(td)
+#: ./doc/common/tables/nova-cells.xml26(td)
+msgid "capabilities = hypervisor=xenserver;kvm, os=linux;windows"
+msgstr "capabilities = hypervisor=xenserver;kvm, os=linux;windows"
+
+#: ./doc/common/tables/ceilometer-cells.xml31(td)
+#: ./doc/common/tables/nova-cells.xml27(td)
+msgid "(ListOpt) Key/Multi-value list with the capabilities of the cell"
 msgstr ""
 
-#: ./doc/common/tables/keystone-oauth.xml23(td)
-msgid "(IntOpt) Duration (in seconds) for the OAuth Access Token."
+#: ./doc/common/tables/ceilometer-cells.xml34(td)
+#: ./doc/common/tables/nova-cells.xml30(td)
+msgid "cell_type = compute"
+msgstr "cell_type = compute"
+
+#: ./doc/common/tables/ceilometer-cells.xml35(td)
+#: ./doc/common/tables/nova-cells.xml31(td)
+msgid "(StrOpt) Type of cell: api or compute"
 msgstr ""
 
-#: ./doc/common/tables/keystone-oauth.xml26(td)
-msgid "driver = keystone.contrib.oauth1.backends.sql.OAuth1"
+#: ./doc/common/tables/ceilometer-cells.xml38(td)
+#: ./doc/common/tables/nova-cells.xml42(td)
+#: ./doc/common/tables/keystone-ssl.xml77(td)
+msgid "enable = False"
 msgstr ""
 
-#: ./doc/common/tables/keystone-oauth.xml27(td)
-#: ./doc/common/tables/keystone-credential.xml23(td)
-msgid "(StrOpt) Keystone Credential backend driver."
+#: ./doc/common/tables/ceilometer-cells.xml39(td)
+#: ./doc/common/tables/nova-cells.xml43(td)
+msgid "(BoolOpt) Enable cell functionality"
 msgstr ""
 
-#: ./doc/common/tables/keystone-oauth.xml30(td)
-msgid "request_token_duration = 28800"
+#: ./doc/common/tables/ceilometer-cells.xml42(td)
+#: ./doc/common/tables/nova-cells.xml54(td)
+msgid "manager = nova.cells.manager.CellsManager"
+msgstr "manager = nova.cells.manager.CellsManager"
+
+#: ./doc/common/tables/ceilometer-cells.xml43(td)
+#: ./doc/common/tables/nova-cells.xml55(td)
+msgid "(StrOpt) Manager for cells"
 msgstr ""
 
-#: ./doc/common/tables/keystone-oauth.xml31(td)
-msgid "(IntOpt) Duration (in seconds) for the OAuth Request Token."
-msgstr ""
+#: ./doc/common/tables/ceilometer-cells.xml46(td)
+#: ./doc/common/tables/nova-cells.xml62(td)
+msgid "mute_child_interval = 300"
+msgstr "mute_child_interval = 300"
 
-#: ./doc/common/tables/cinder-block-device.xml8(caption)
-msgid "Description of configuration options for block-device"
-msgstr ""
-
-#: ./doc/common/tables/cinder-block-device.xml22(td)
-msgid "available_devices ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-block-device.xml23(td)
-msgid "(ListOpt) List of all available devices"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zones.xml8(caption)
-msgid "Description of configuration options for zones"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zones.xml22(td)
-msgid "cloned_volume_same_az = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zones.xml23(td)
+#: ./doc/common/tables/ceilometer-cells.xml47(td)
+#: ./doc/common/tables/nova-cells.xml63(td)
 msgid ""
-"(BoolOpt) Ensure that the new volumes are the same AZ as snapshot or source "
-"volume"
+"(IntOpt) Number of seconds after which a lack of capability and capacity "
+"updates signals the child cell is to be treated as a mute."
 msgstr ""
 
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml8(caption)
-msgid "Description of configuration options for netapp_7mode_iscsi"
+#: ./doc/common/tables/ceilometer-cells.xml50(td)
+#: ./doc/common/tables/nova-cells.xml74(td)
+msgid "name = nova"
 msgstr ""
 
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml38(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml38(td)
-msgid "netapp_size_multiplier = 1.2"
+#: ./doc/common/tables/ceilometer-cells.xml51(td)
+#: ./doc/common/tables/nova-cells.xml75(td)
+msgid "(StrOpt) Name of this cell"
+msgstr "(StrOpt) Nom de cette cellule"
+
+#: ./doc/common/tables/ceilometer-cells.xml54(td)
+#: ./doc/common/tables/nova-cells.xml82(td)
+msgid "reserve_percent = 10.0"
 msgstr ""
 
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml39(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml39(td)
+#: ./doc/common/tables/ceilometer-cells.xml55(td)
+#: ./doc/common/tables/nova-cells.xml83(td)
 msgid ""
-"(FloatOpt) The quantity to be multiplied by the requested volume size to "
-"ensure enough space is available on the virtual storage server (Vserver) to "
-"fulfill the volume creation request."
+"(FloatOpt) Percentage of cell capacity to hold in reserve. Affects both "
+"memory and disk utilization"
 msgstr ""
 
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml46(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml46(td)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml46(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml50(td)
-msgid "netapp_storage_protocol = None"
+#: ./doc/common/tables/ceilometer-cells.xml58(td)
+#: ./doc/common/tables/nova-cells.xml86(td)
+msgid "topic = cells"
 msgstr ""
 
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml47(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml47(td)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml47(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml51(td)
-msgid ""
-"(StrOpt) The storage protocol to be used on the data path with the storage "
-"system; valid values are iscsi or nfs."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml54(td)
-msgid "netapp_vfiler = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml55(td)
-msgid ""
-"(StrOpt) The vFiler unit on which provisioning of block storage volumes will"
-" be done. This option is only used by the driver when connecting to an "
-"instance with a storage family of Data ONTAP operating in 7-Mode and the "
-"storage protocol selected is iSCSI. Only use this option when utilizing the "
-"MultiStore feature on the NetApp storage system."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml58(td)
-msgid "netapp_volume_list = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml59(td)
-msgid ""
-"(StrOpt) This option is only utilized when the storage protocol is "
-"configured to use iSCSI. This option is used to restrict provisioning to the"
-" specified controller volumes. Specify the value of this option to be a "
-"comma separated list of NetApp controller volume names to be used for "
-"provisioning."
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-sync.xml7(literal)
-msgid "[container-sync]"
-msgstr "[container-sync]"
-
-#: ./doc/common/tables/swift-container-server-container-sync.xml18(td)
-msgid "log_name = container-sync"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-sync.xml30(td)
-msgid "sync_proxy = http://10.1.1.1:8888,http://10.1.1.2:8888"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-sync.xml30(td)
-msgid "If you need to use an HTTP proxy, set it here. Defaults to no proxy."
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-sync.xml36(td)
-msgid "container_time = 60"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-sync.xml36(td)
-msgid "Maximum amount of time to spend syncing each container"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml8(caption)
-#: ./doc/common/tables/nova-common.xml8(caption)
-#: ./doc/common/tables/glance-common.xml8(caption)
-#: ./doc/common/tables/cinder-common.xml8(caption)
-#: ./doc/common/tables/trove-common.xml8(caption)
-#: ./doc/common/tables/ceilometer-common.xml8(caption)
-#: ./doc/common/tables/heat-common.xml8(caption)
-msgid "Description of configuration options for common"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml23(td)
-#: ./doc/common/tables/neutron-common.xml193(td)
-msgid "(StrOpt) Admin password"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml26(td)
-#: ./doc/common/tables/neutron-common.xml196(td)
-#: ./doc/common/tables/glance-registry.xml26(td)
-msgid "admin_tenant_name = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml27(td)
-#: ./doc/common/tables/neutron-common.xml197(td)
-msgid "(StrOpt) Admin tenant name"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml31(td)
-msgid "(StrOpt) Admin username"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml34(td)
-msgid "agent_down_time = 75"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml35(td)
-msgid ""
-"(IntOpt) Seconds to regard the agent is down; should be at least twice "
-"report_interval, to be sure the agent is down for good."
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml38(td)
-#: ./doc/common/tables/heat-rpc.xml22(td)
-#: ./doc/common/tables/ceilometer-rpc.xml22(td)
-#: ./doc/common/tables/trove-rpc.xml22(td)
-msgid ""
-"allowed_rpc_exception_modules = nova.exception, cinder.exception, exceptions"
-msgstr "allowed_rpc_exception_modules = nova.exception, cinder.exception, exceptions"
-
-#: ./doc/common/tables/neutron-common.xml39(td)
-#: ./doc/common/tables/heat-rpc.xml23(td)
-#: ./doc/common/tables/nova-testing.xml23(td)
-#: ./doc/common/tables/cinder-rpc.xml23(td)
-#: ./doc/common/tables/keystone-rpc.xml23(td)
-#: ./doc/common/tables/ceilometer-rpc.xml23(td)
-msgid ""
-"(ListOpt) Modules of exceptions that are permitted to be recreated upon "
-"receiving exception data from an rpc call."
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml42(td)
-msgid "api_workers = 0"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml43(td)
-msgid "(IntOpt) Number of separate worker processes for service"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml46(td)
-msgid "auth_ca_cert = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml47(td)
-msgid "(StrOpt) Certificate Authority public key (CA cert) file for ssl"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml50(td)
-msgid "auth_insecure = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml51(td)
-msgid "(BoolOpt) Turn off verification of the certificate for ssl"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml54(td)
-#: ./doc/common/tables/neutron-common.xml204(td)
-#: ./doc/common/tables/glance-registry.xml34(td)
-msgid "auth_region = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml55(td)
-#: ./doc/common/tables/neutron-common.xml205(td)
-msgid "(StrOpt) Authentication region"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml58(td)
-#: ./doc/common/tables/neutron-common.xml208(td)
-#: ./doc/common/tables/ceilometer-auth.xml22(td)
-msgid "auth_strategy = keystone"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml59(td)
-#: ./doc/common/tables/neutron-common.xml209(td)
-msgid "(StrOpt) The type of authentication to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml62(td)
-#: ./doc/common/tables/neutron-common.xml212(td)
-#: ./doc/common/tables/glance-registry.xml42(td)
-msgid "auth_url = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml63(td)
-#: ./doc/common/tables/neutron-common.xml213(td)
-msgid "(StrOpt) Authentication URL"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml66(td)
-msgid "base_mac = fa:16:3e:00:00:00"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml67(td)
-msgid "(StrOpt) The base MAC address Neutron will use for VIFs"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml70(td)
-#: ./doc/common/tables/heat-cfn_api.xml37(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml33(td)
-#: ./doc/common/tables/glance-common.xml34(td)
-#: ./doc/common/tables/heat-api.xml107(td)
-msgid "bind_host = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml71(td)
-msgid "(StrOpt) The host IP to bind to"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml74(td)
-msgid "bind_port = 9696"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml75(td)
-msgid "(IntOpt) The port to bind to"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml78(td)
-msgid "ca_certs = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml79(td)
-msgid "(StrOpt) CA certificates"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml82(td)
-msgid "core_plugin = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml83(td)
-msgid "(StrOpt) The core plugin Neutron will use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml86(td)
-msgid "ctl_cert = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml87(td)
-msgid "(StrOpt) controller certificate"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml90(td)
-msgid "ctl_privkey = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml91(td)
-msgid "(StrOpt) controller private key"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml94(td)
-msgid "dhcp_agent_notification = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml95(td)
-msgid "(BoolOpt) Allow sending resource operation notification to DHCP agent"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml98(td)
-msgid "dhcp_agents_per_network = 1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml99(td)
-msgid "(IntOpt) Number of DHCP agents scheduled to host a network."
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml102(td)
-msgid "dhcp_confs = $state_path/dhcp"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml103(td)
-msgid "(StrOpt) Location to store DHCP server config files"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml106(td)
-msgid "dhcp_delete_namespaces = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml107(td)
-msgid "(BoolOpt) Delete namespace after removing a dhcp server."
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml110(td)
-msgid "dhcp_domain = openstacklocal"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml111(td)
-#: ./doc/common/tables/nova-network.xml51(td)
-#: ./doc/common/tables/neutron-vmware.xml120(td)
-msgid "(StrOpt) Domain to use for building the hostnames"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml114(td)
-msgid "dhcp_driver = neutron.agent.linux.dhcp.Dnsmasq"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml115(td)
-msgid "(StrOpt) The driver used to manage the DHCP server."
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml118(td)
-msgid "dhcp_lease_duration = 86400"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml119(td)
-msgid "(IntOpt) DHCP lease duration"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml126(td)
-msgid "endpoint_type = adminURL"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml127(td)
-msgid ""
-"(StrOpt) Network service endpoint type to pull from the keystone catalog"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml130(td)
-msgid "force_gateway_on_subnet = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml131(td)
-msgid "(BoolOpt) Ensure that configured gateway is on subnet"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml134(td)
-msgid "interface_driver = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml135(td)
-msgid "(StrOpt) The driver used to manage the virtual interface."
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml138(td)
-msgid "ip_lib_force_root = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml139(td)
-msgid "(BoolOpt) Force ip_lib calls to use the root helper"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml142(td)
-#: ./doc/common/tables/nova-common.xml46(td)
-#: ./doc/common/tables/heat-debug.xml38(td)
-#: ./doc/common/tables/glance-common.xml70(td)
-#: ./doc/common/tables/cinder-common.xml70(td)
-#: ./doc/common/tables/trove-common.xml58(td)
-#: ./doc/common/tables/ceilometer-common.xml34(td)
-#: ./doc/common/tables/keystone-misc.xml22(td)
-msgid "lock_path = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml143(td)
-#: ./doc/common/tables/nova-common.xml47(td)
-#: ./doc/common/tables/heat-debug.xml39(td)
-#: ./doc/common/tables/glance-common.xml71(td)
-#: ./doc/common/tables/trove-common.xml59(td)
-#: ./doc/common/tables/ceilometer-common.xml35(td)
-#: ./doc/common/tables/keystone-misc.xml23(td)
-msgid "(StrOpt) Directory to use for lock files."
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml146(td)
-msgid "mac_generation_retries = 16"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml147(td)
-msgid "(IntOpt) How many times Neutron will retry MAC generation"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml150(td)
-msgid "max_dns_nameservers = 5"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml151(td)
-msgid "(IntOpt) Maximum number of DNS nameservers"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml154(td)
-msgid "max_fixed_ips_per_port = 5"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml155(td)
-msgid "(IntOpt) Maximum number of fixed ips per port"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml158(td)
-msgid "max_subnet_host_routes = 20"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml159(td)
-msgid "(IntOpt) Maximum number of host routes per subnet"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml162(td)
-msgid "periodic_fuzzy_delay = 5"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml163(td)
-#: ./doc/common/tables/nova-periodic.xml27(td)
-msgid ""
-"(IntOpt) Range of seconds to randomly delay when starting the periodic task "
-"scheduler to reduce stampeding. (Disable by setting to 0)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml166(td)
-msgid "periodic_interval = 40"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml167(td)
-msgid "(IntOpt) Seconds between running periodic tasks"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml170(td)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml27(td)
-msgid "report_interval = 300"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml171(td)
-msgid "(IntOpt) Interval between two metering reports"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml174(td)
-#: ./doc/common/tables/neutron-common.xml185(td)
-#: ./doc/common/tables/neutron-sdnve.xml89(td)
-msgid "root_helper = sudo"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml175(td)
-#: ./doc/common/tables/neutron-common.xml186(td)
-msgid "(StrOpt) Root helper application."
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml178(td)
-msgid "state_path = /var/lib/neutron"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml179(td)
-msgid ""
-"(StrOpt) Where to store Neutron state files. This directory must be writable"
-" by the agent."
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml182(th)
-#: ./doc/common/tables/neutron-openvswitch_agent.xml34(th)
-#: ./doc/common/tables/neutron-metering_agent.xml30(th)
-#: ./doc/common/tables/neutron-ml2_ofa.xml34(th)
-#: ./doc/common/tables/neutron-hyperv_agent.xml19(th)
-#: ./doc/common/tables/neutron-rpc.xml66(th)
-#: ./doc/common/tables/neutron-nvsd.xml19(th)
-msgid "[AGENT]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml189(th)
-msgid "[PROXY]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml201(td)
-msgid "(StrOpt) Admin user"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml216(th)
-#: ./doc/common/tables/neutron-embrane.xml19(th)
-msgid "[heleos]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml220(td)
-#: ./doc/common/tables/neutron-embrane_lb.xml23(td)
-msgid "(StrOpt) ESM admin password."
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml22(td)
-msgid "notify_nova_on_port_data_changes = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml23(td)
-msgid ""
-"(BoolOpt) Send notification to nova when port data (fixed_ips/floatingip) "
-"changes so nova can update its cache."
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml26(td)
-msgid "notify_nova_on_port_status_changes = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml27(td)
-msgid "(BoolOpt) Send notification to nova when port status changes"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml30(td)
-msgid "nova_admin_auth_url = http://localhost:5000/v2.0"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml31(td)
-msgid "(StrOpt) Authorization URL for connecting to nova in admin context"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml34(td)
-msgid "nova_admin_password = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml35(td)
-msgid "(StrOpt) Password for connection to nova in admin context"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml38(td)
-msgid "nova_admin_tenant_id = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml39(td)
-msgid "(StrOpt) The uuid of the admin nova tenant"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml42(td)
-msgid "nova_admin_username = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml43(td)
-msgid "(StrOpt) Username for connecting to nova in admin context"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml46(td)
-msgid "nova_region_name = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml47(td)
-msgid ""
-"(StrOpt) Name of nova region to use. Useful if keystone manages more than "
-"one region."
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml50(td)
-msgid "nova_url = http://127.0.0.1:8774"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml51(td)
-msgid "(StrOpt) URL for connection to nova"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml54(td)
-msgid "send_events_interval = 2"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml55(td)
-msgid ""
-"(IntOpt) Number of seconds between sending events to nova if there are any "
-"events to send."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml7(literal)
-msgid "[object-auditor]"
-msgstr "[object-auditor]"
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml7(literal)
-#: ./doc/common/tables/swift-object-server-object-updater.xml7(literal)
-#: ./doc/common/tables/swift-object-server-pipeline-main.xml7(literal)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml7(literal)
-#: ./doc/common/tables/swift-object-server-filter-recon.xml7(literal)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml7(literal)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml7(literal)
-#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml7(literal)
-msgid "object-server.conf-sample"
-msgstr "object-server.conf-sample"
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml18(td)
-msgid "log_name = object-auditor"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml30(td)
-msgid "files_per_second = 20"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml30(td)
-msgid ""
-"Maximum files audited per second. Should be tuned according to individual "
-"system specs. 0 is unlimited."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml33(td)
-msgid "bytes_per_second = 10000000"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml33(td)
-msgid ""
-"Maximum bytes audited per second. Should be tuned according to individual "
-"system specs. 0 is unlimited. mounted to prevent accidentally writing to the"
-" root device process simultaneously (it will actually accept(2) N + 1). "
-"Setting this to one (1) will only handle one request at a time, without "
-"accepting another request concurrently. By increasing the number of workers "
-"to a much higher value, one can reduce the impact of slow file system "
-"operations in one request from negatively impacting other requests. "
-"underlying filesystem does not support it. to setup custom log handlers. "
-"bytes you'd like fallocate to reserve, whether there is space for the given "
-"file size or not. This is useful for systems that behave badly when they "
-"completely run out of space; you can make the services pretend they're out "
-"of space early. container server. For most cases, this should be "
-"`egg:swift#container`."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml36(td)
-msgid "log_time = 3600"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml36(td)
-msgid "Frequency of status logs in seconds."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml39(td)
-msgid "zero_byte_files_per_second = 50"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml39(td)
-msgid "Maximum zero byte files audited per second."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml45(td)
-msgid "object_size_stats ="
-msgstr ""
-
-#: ./doc/common/tables/keystone-ldap.xml8(caption)
-#: ./doc/common/tables/nova-ldap.xml8(caption)
-msgid "Description of configuration options for ldap"
+#: ./doc/common/tables/ceilometer-cells.xml59(td)
+#: ./doc/common/tables/nova-cells.xml87(td)
+msgid "(StrOpt) The topic cells nodes listen on"
 msgstr ""
 
 #: ./doc/common/tables/keystone-ldap.xml19(th)
@@ -33094,2970 +37052,6 @@ msgstr ""
 msgid "(StrOpt) Search base for users."
 msgstr ""
 
-#: ./doc/common/tables/heat-rpc.xml8(caption)
-#: ./doc/common/tables/cinder-rpc.xml8(caption)
-#: ./doc/common/tables/keystone-rpc.xml8(caption)
-#: ./doc/common/tables/glance-rpc.xml8(caption)
-#: ./doc/common/tables/ceilometer-rpc.xml8(caption)
-#: ./doc/common/tables/neutron-rpc.xml8(caption)
-#: ./doc/common/tables/trove-rpc.xml8(caption)
-#: ./doc/common/tables/nova-rpc.xml8(caption)
-msgid "Description of configuration options for rpc"
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml26(td)
-msgid "engine_life_check_timeout = 2"
-msgstr "engine_life_check_timeout = 2"
-
-#: ./doc/common/tables/heat-rpc.xml27(td)
-msgid ""
-"(IntOpt) RPC timeout for the engine liveness check that is used for stack "
-"locking."
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml31(td)
-#: ./doc/common/tables/ceilometer-redis.xml27(td)
-#: ./doc/common/tables/neutron-rpc.xml35(td)
-#: ./doc/common/tables/trove-rpc.xml31(td)
-msgid "(IntOpt) Heartbeat frequency"
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml38(td)
-msgid "rpc_backend = heat.openstack.common.rpc.impl_kombu"
-msgstr "rpc_backend = heat.openstack.common.rpc.impl_kombu"
-
-#: ./doc/common/tables/heat-rpc.xml39(td)
-#: ./doc/common/tables/ceilometer-rpc.xml31(td)
-#: ./doc/common/tables/neutron-rpc.xml43(td)
-#: ./doc/common/tables/trove-rpc.xml51(td)
-msgid "(StrOpt) The messaging module to use, defaults to kombu."
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml47(td)
-#: ./doc/common/tables/ceilometer-rpc.xml39(td)
-#: ./doc/common/tables/neutron-rpc.xml51(td)
-#: ./doc/common/tables/trove-rpc.xml59(td)
-msgid "(IntOpt) Size of RPC connection pool"
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml51(td)
-#: ./doc/common/tables/ceilometer-rpc.xml43(td)
-#: ./doc/common/tables/neutron-rpc.xml55(td)
-#: ./doc/common/tables/trove-rpc.xml63(td)
-msgid "(IntOpt) Seconds to wait for a response from call or multicall"
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml55(td)
-#: ./doc/common/tables/ceilometer-rpc.xml47(td)
-#: ./doc/common/tables/neutron-rpc.xml59(td)
-#: ./doc/common/tables/trove-rpc.xml67(td)
-msgid "(IntOpt) Size of RPC thread pool"
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml65(th)
-#: ./doc/common/tables/ceilometer-rpc.xml92(th)
-#: ./doc/common/tables/neutron-rpc.xml80(th)
-#: ./doc/common/tables/trove-rpc.xml70(th)
-msgid "[rpc_notifier2]"
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml68(td)
-#: ./doc/common/tables/ceilometer-rpc.xml95(td)
-#: ./doc/common/tables/neutron-rpc.xml83(td)
-#: ./doc/common/tables/trove-rpc.xml73(td)
-msgid "topics = notifications"
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml69(td)
-#: ./doc/common/tables/ceilometer-rpc.xml96(td)
-msgid "(ListOpt) AMQP topic(s) used for OpenStack notifications"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml8(caption)
-msgid "Description of configuration options for openvswitch_agent"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml22(td)
-msgid "ovs_integration_bridge = br-int"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml23(td)
-msgid "(StrOpt) Name of Open vSwitch bridge to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml26(td)
-msgid "ovs_use_veth = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml27(td)
-msgid "(BoolOpt) Uses veth for an interface or not"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml30(td)
-msgid "ovs_vsctl_timeout = 10"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml31(td)
-msgid "(IntOpt) Timeout in seconds for ovs-vsctl commands"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml37(td)
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml44(td)
-msgid "l2_population = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml38(td)
-msgid ""
-"(BoolOpt) Use ml2 l2population mechanism driver to learn remote mac and IPs "
-"and improve tunnel scalability"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml41(td)
-msgid "minimize_polling = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml42(td)
-msgid "(BoolOpt) Minimize polling by monitoring ovsdb for interface changes."
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml45(td)
-msgid "ovsdb_monitor_respawn_interval = 30"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml46(td)
-msgid ""
-"(IntOpt) The number of seconds to wait before respawning the ovsdb monitor "
-"after losing communication with it"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml49(td)
-msgid "tunnel_types ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml50(td)
-msgid "(ListOpt) Network types supported by the agent (gre and/or vxlan)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml53(td)
-msgid "veth_mtu = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml54(td)
-msgid "(IntOpt) MTU size of veth interfaces"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml57(td)
-msgid "vxlan_udp_port = 4789"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml58(td)
-msgid "(IntOpt) The UDP port to use for VXLAN tunnels."
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml61(th)
-#: ./doc/common/tables/neutron-cisco.xml54(th)
-msgid "[CISCO_N1K]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml64(td)
-msgid "local_ip = 10.0.0.3"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml65(td)
-msgid "(StrOpt) N1K Local IP"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml68(th)
-#: ./doc/common/tables/neutron-ryu.xml19(th)
-msgid "[OVS]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml71(td)
-#: ./doc/common/tables/neutron-cisco.xml57(td)
-msgid "bridge_mappings ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml72(td)
-msgid "(ListOpt) List of &lt;physical_network&gt;:&lt;bridge&gt;"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml75(td)
-msgid "enable_tunneling = False"
-msgstr "enable_tunneling = False"
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml76(td)
-msgid "(BoolOpt) Enable tunneling support"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml79(td)
-msgid "int_peer_patch_port = patch-tun"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml80(td)
-msgid "(StrOpt) Peer patch port in integration bridge for tunnel bridge"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml84(td)
-#: ./doc/common/tables/neutron-sdnve.xml43(td)
-msgid "(StrOpt) Integration bridge to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml87(td)
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml48(td)
-msgid "local_ip ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml88(td)
-msgid "(StrOpt) Local IP address of GRE tunnel endpoints."
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml91(td)
-#: ./doc/common/tables/neutron-ml2_vlan.xml22(td)
-#: ./doc/common/tables/neutron-hyperv_agent.xml45(td)
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml29(td)
-msgid "network_vlan_ranges ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml95(td)
-#: ./doc/common/tables/neutron-hyperv_agent.xml49(td)
-#: ./doc/common/tables/neutron-cisco.xml89(td)
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml33(td)
-msgid "tenant_network_type = local"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml96(td)
-msgid ""
-"(StrOpt) Network type for tenant networks (local, vlan, gre, vxlan, or none)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml99(td)
-msgid "tun_peer_patch_port = patch-int"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml100(td)
-msgid "(StrOpt) Peer patch port in tunnel bridge for integration bridge"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml103(td)
-#: ./doc/common/tables/neutron-cisco.xml93(td)
-msgid "tunnel_bridge = br-tun"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml104(td)
-msgid "(StrOpt) Tunnel bridge to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml108(td)
-msgid "(ListOpt) List of &lt;tun_min&gt;:&lt;tun_max&gt;"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml111(td)
-msgid "tunnel_type ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml112(td)
-msgid ""
-"(StrOpt) The type of tunnels to use when utilizing tunnels, either 'gre' or "
-"'vxlan'"
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml22(td)
-msgid "nova_api_insecure = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml23(td)
-msgid "(BoolOpt) Allow to perform insecure SSL requests to nova"
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml26(td)
-msgid "nova_ca_certificates_file = None"
-msgstr "nova_ca_certificates_file = None"
-
-#: ./doc/common/tables/cinder-compute.xml27(td)
-msgid ""
-"(StrOpt) Location of ca certificates file to use for nova client requests."
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml30(td)
-msgid "nova_catalog_admin_info = compute:nova:adminURL"
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml31(td)
-msgid "(StrOpt) Same as nova_catalog_info, but for admin endpoint."
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml34(td)
-msgid "nova_catalog_info = compute:nova:publicURL"
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml35(td)
-msgid ""
-"(StrOpt) Info to match when looking for nova in the service catalog. Format "
-"is : separated values of the form: "
-"&lt;service_type&gt;:&lt;service_name&gt;:&lt;endpoint_type&gt;"
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml38(td)
-msgid "nova_endpoint_admin_template = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml39(td)
-msgid "(StrOpt) Same as nova_endpoint_template, but for admin endpoint."
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml42(td)
-msgid "nova_endpoint_template = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml43(td)
-msgid ""
-"(StrOpt) Override service catalog lookup with template for nova endpoint "
-"e.g. http://localhost:8774/v2/%(project_id)s"
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml47(td)
-msgid "(StrOpt) region name of this node"
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml8(caption)
-msgid "Description of configuration options for identity"
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml19(th)
-msgid "[identity]"
-msgstr "[identity]"
-
-#: ./doc/common/tables/keystone-identity.xml22(td)
-msgid "default_domain_id = default"
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml23(td)
-msgid ""
-"(StrOpt) This references the domain to use for all Identity API v2 requests "
-"(which are not aware of domains). A domain with this ID will be created for "
-"you by keystone-manage db_sync in migration 008. The domain referenced by "
-"this ID cannot be deleted on the v3 API, to prevent accidentally breaking "
-"the v2 API. There is nothing special about this domain, other than the fact "
-"that it must exist to order to maintain support for your v2 clients."
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml26(td)
-msgid "domain_config_dir = /etc/keystone/domains"
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml27(td)
-msgid ""
-"(StrOpt) Path for Keystone to locate the domain specificidentity "
-"configuration files if domain_specific_drivers_enabled is set to true."
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml30(td)
-msgid "domain_specific_drivers_enabled = False"
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml31(td)
-msgid ""
-"(BoolOpt) A subset (or all) of domains can have their own identity driver, "
-"each with their own partial configuration file in a domain configuration "
-"directory. Only values specific to the domain need to be placed in the "
-"domain specific configuration file. This feature is disabled by default; set"
-" to True to enable."
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml34(td)
-msgid "driver = keystone.identity.backends.sql.Identity"
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml35(td)
-msgid "(StrOpt) Keystone Identity backend driver."
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml38(td)
-#: ./doc/common/tables/keystone-assignment.xml34(td)
-#: ./doc/common/tables/keystone-catalog.xml26(td)
-#: ./doc/common/tables/keystone-policy.xml37(td)
-#: ./doc/common/tables/keystone-api.xml46(td)
-msgid "list_limit = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml39(td)
-msgid ""
-"(IntOpt) Maximum number of entities that will be returned in an identity "
-"collection."
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml42(td)
-msgid "max_password_length = 4096"
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml43(td)
-msgid ""
-"(IntOpt) Maximum supported length for user passwords; decrease to improve "
-"performance."
-msgstr ""
-
-#: ./doc/common/tables/cinder-lvm.xml8(caption)
-msgid "Description of configuration options for lvm"
-msgstr ""
-
-#: ./doc/common/tables/cinder-lvm.xml22(td)
-msgid "lvm_mirrors = 0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-lvm.xml23(td)
-msgid ""
-"(IntOpt) If set, create lvms with multiple mirrors. Note that this requires "
-"lvm_mirrors + 2 pvs with available space"
-msgstr ""
-
-#: ./doc/common/tables/cinder-lvm.xml26(td)
-msgid "lvm_type = default"
-msgstr ""
-
-#: ./doc/common/tables/cinder-lvm.xml27(td)
-msgid "(StrOpt) Type of LVM volumes to deploy; (default or thin)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-lvm.xml30(td)
-msgid "volume_group = cinder-volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-lvm.xml31(td)
-msgid "(StrOpt) Name for the VG that will contain exported volumes"
-msgstr ""
-
-#: ./doc/common/tables/keystone-trust.xml8(caption)
-msgid "Description of configuration options for trust"
-msgstr ""
-
-#: ./doc/common/tables/keystone-trust.xml19(th)
-msgid "[trust]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-trust.xml22(td)
-msgid "driver = keystone.trust.backends.sql.Trust"
-msgstr ""
-
-#: ./doc/common/tables/keystone-trust.xml23(td)
-msgid "(StrOpt) Keystone Trust backend driver."
-msgstr ""
-
-#: ./doc/common/tables/keystone-trust.xml26(td)
-#: ./doc/common/tables/trove-rpc.xml80(td)
-msgid "enabled = True"
-msgstr "enabled = True"
-
-#: ./doc/common/tables/keystone-trust.xml27(td)
-msgid ""
-"(BoolOpt) delegation and impersonation features can be optionally disabled."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_nfs.xml8(caption)
-msgid "Description of configuration options for storage_nfs"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_nfs.xml23(td)
-msgid ""
-"(StrOpt) Mount options passed to the nfs client. See section of the nfs man "
-"page for details."
-msgstr "(StrOpt) Options de montage passées au client NFS. Voir la section sur le NFS, page principale pour les détails."
-
-#: ./doc/common/tables/cinder-storage_nfs.xml27(td)
-msgid "(StrOpt) Base dir containing mount points for nfs shares."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_nfs.xml30(td)
-msgid "nfs_oversub_ratio = 1.0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_nfs.xml31(td)
-msgid ""
-"(FloatOpt) This will compare the allocated to available space on the volume "
-"destination. If the ratio exceeds this number, the destination will no "
-"longer be valid."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_nfs.xml34(td)
-msgid "nfs_shares_config = /etc/cinder/nfs_shares"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_nfs.xml35(td)
-#: ./doc/common/tables/cinder-nexenta_nfs.xml31(td)
-msgid "(StrOpt) File with the list of available nfs shares"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_nfs.xml38(td)
-msgid "nfs_sparsed_volumes = True"
-msgstr "nfs_sparsed_volumes = True"
-
-#: ./doc/common/tables/cinder-storage_nfs.xml42(td)
-msgid "nfs_used_ratio = 0.95"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_nfs.xml43(td)
-msgid ""
-"(FloatOpt) Percent of ACTUAL usage of the underlying volume before no new "
-"volumes can be allocated to the volume destination."
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml8(caption)
-msgid "Description of configuration options for plumgrid"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml19(th)
-msgid "[plumgriddirector]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml22(td)
-msgid "director_server = localhost"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml23(td)
-msgid "(StrOpt) PLUMgrid Director server to connect to"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml26(td)
-msgid "director_server_port = 8080"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml27(td)
-msgid "(StrOpt) PLUMgrid Director server port to connect to"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml30(td)
-#: ./doc/common/tables/neutron-ml2_brocade.xml30(td)
-msgid "password = password"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml31(td)
-msgid "(StrOpt) PLUMgrid Director admin password"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml34(td)
-msgid "servertimeout = 5"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml35(td)
-msgid "(IntOpt) PLUMgrid Director server timeout"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml38(td)
-msgid "username = username"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml39(td)
-msgid "(StrOpt) PLUMgrid Director admin username"
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml8(caption)
-msgid "Description of configuration options for cfn_api"
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml22(td)
-msgid "instance_connection_https_validate_certificates = 1"
-msgstr "instance_connection_https_validate_certificates = 1"
-
-#: ./doc/common/tables/heat-cfn_api.xml23(td)
-msgid ""
-"(StrOpt) Instance connection to CFN/CW API validate certs if SSL is used."
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml26(td)
-msgid "instance_connection_is_secure = 0"
-msgstr "instance_connection_is_secure = 0"
-
-#: ./doc/common/tables/heat-cfn_api.xml27(td)
-msgid "(StrOpt) Instance connection to CFN/CW API via https."
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml30(th)
-msgid "[heat_api_cfn]"
-msgstr "[heat_api_cfn]"
-
-#: ./doc/common/tables/heat-cfn_api.xml34(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml30(td)
-#: ./doc/common/tables/heat-api.xml104(td)
-msgid "(IntOpt) Number of backlog requests to configure the socket with."
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml38(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml34(td)
-#: ./doc/common/tables/glance-common.xml35(td)
-#: ./doc/common/tables/heat-api.xml108(td)
-msgid ""
-"(StrOpt) Address to bind the server. Useful when selecting a particular "
-"network interface."
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml41(td)
-msgid "bind_port = 8000"
-msgstr "bind_port = 8000"
-
-#: ./doc/common/tables/heat-cfn_api.xml42(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml38(td)
-#: ./doc/common/tables/glance-common.xml39(td)
-#: ./doc/common/tables/heat-api.xml112(td)
-msgid "(IntOpt) The port on which the server will listen."
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml46(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml42(td)
-#: ./doc/common/tables/heat-api.xml116(td)
-msgid "(StrOpt) Location of the SSL certificate file to use for SSL mode."
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml50(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml46(td)
-#: ./doc/common/tables/heat-api.xml120(td)
-msgid "(StrOpt) Location of the SSL key file to use for enabling SSL mode."
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml53(td)
-#: ./doc/common/tables/trove-api.xml66(td)
-#: ./doc/common/tables/neutron-api.xml42(td)
-#: ./doc/common/tables/cinder-api.xml46(td)
-#: ./doc/common/tables/glance-wsgi.xml30(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml49(td)
-#: ./doc/common/tables/heat-api.xml123(td)
-#: ./doc/common/tables/nova-api.xml42(td)
-msgid "max_header_line = 16384"
-msgstr "max_header_line = 16384"
-
-#: ./doc/common/tables/heat-cfn_api.xml54(td)
-#: ./doc/common/tables/cinder-api.xml47(td)
-#: ./doc/common/tables/heat-api.xml124(td)
-#: ./doc/common/tables/nova-api.xml43(td)
-msgid ""
-"(IntOpt) Maximum line size of message headers to be accepted. "
-"max_header_line may need to be increased when using large tokens (typically "
-"those generated by the Keystone v3 API with big service catalogs)."
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml57(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml53(td)
-#: ./doc/common/tables/heat-api.xml127(td)
-msgid "workers = 0"
-msgstr "workers = 0"
-
-#: ./doc/common/tables/heat-cfn_api.xml58(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml54(td)
-#: ./doc/common/tables/heat-api.xml128(td)
-msgid "(IntOpt) Number of workers for Heat service."
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml65(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml61(td)
-#: ./doc/common/tables/nova-wsgi.xml27(td)
-#: ./doc/common/tables/cinder-common.xml175(td)
-#: ./doc/common/tables/cinder-ssl.xml23(td)
-#: ./doc/common/tables/heat-api.xml146(td)
-#: ./doc/common/tables/neutron-ssl.xml23(td)
-#: ./doc/common/tables/neutron-ssl.xml38(td)
-#: ./doc/common/tables/trove-ssl.xml23(td)
-#: ./doc/common/tables/ceilometer-ssl.xml23(td)
-msgid "(StrOpt) CA certificate file to use to verify connecting clients"
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml69(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml65(td)
-#: ./doc/common/tables/cinder-common.xml179(td)
-#: ./doc/common/tables/cinder-ssl.xml27(td)
-#: ./doc/common/tables/heat-api.xml150(td)
-#: ./doc/common/tables/neutron-ssl.xml27(td)
-#: ./doc/common/tables/neutron-ssl.xml42(td)
-#: ./doc/common/tables/trove-ssl.xml27(td)
-#: ./doc/common/tables/ceilometer-ssl.xml27(td)
-msgid "(StrOpt) Certificate file to use when starting the server securely"
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml73(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml69(td)
-#: ./doc/common/tables/cinder-common.xml183(td)
-#: ./doc/common/tables/cinder-ssl.xml31(td)
-#: ./doc/common/tables/heat-api.xml154(td)
-#: ./doc/common/tables/neutron-ssl.xml31(td)
-#: ./doc/common/tables/neutron-ssl.xml46(td)
-#: ./doc/common/tables/trove-ssl.xml31(td)
-#: ./doc/common/tables/ceilometer-ssl.xml31(td)
-msgid "(StrOpt) Private key file to use when starting the server securely"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml8(caption)
-msgid "Description of configuration options for hypervisor"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml22(td)
-msgid "default_ephemeral_format = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml23(td)
-msgid ""
-"(StrOpt) The default format an ephemeral_volume will be formatted with on "
-"creation."
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml26(td)
-msgid "force_raw_images = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml27(td)
-msgid "(BoolOpt) Force backing images to raw format"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml30(td)
-msgid "preallocate_images = none"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml31(td)
-msgid ""
-"(StrOpt) VM image preallocation mode: \"none\" =&gt; no storage provisioning"
-" is done up front, \"space\" =&gt; storage is fully allocated at instance "
-"start"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml34(td)
-msgid "rescue_timeout = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml35(td)
-msgid ""
-"(IntOpt) Automatically unrescue an instance after N seconds. Set to 0 to "
-"disable."
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml38(td)
-msgid "timeout_nbd = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml39(td)
-msgid "(IntOpt) Amount of time, in seconds, to wait for NBD device start up."
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml42(td)
-msgid "use_cow_images = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml43(td)
-msgid "(BoolOpt) Whether to use cow images"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml46(td)
-msgid "vcpu_pin_set = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml47(td)
-msgid ""
-"(StrOpt) Defines which pcpus that instance vcpus can use. For example, "
-"\"4-12,^8,15\""
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml50(td)
-msgid "virt_mkfs = []"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml51(td)
-msgid ""
-"(MultiStrOpt) Name of the mkfs commands for ephemeral device. The format is "
-"&lt;os_type&gt;=&lt;mkfs command&gt;"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml57(td)
-msgid ""
-"block_migration_flag = VIR_MIGRATE_UNDEFINE_SOURCE, VIR_MIGRATE_PEER2PEER, "
-"VIR_MIGRATE_NON_SHARED_INC"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml58(td)
-msgid "(StrOpt) Migration flags to be set for block migration"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml61(td)
-msgid "disk_cachemodes ="
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml62(td)
-msgid ""
-"(ListOpt) Specific cachemodes to use for different disk types e.g: "
-"file=directsync,block=none"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml65(td)
-msgid "images_rbd_ceph_conf ="
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml66(td)
-msgid "(StrOpt) Path to the ceph configuration file to use"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml69(td)
-msgid "images_rbd_pool = rbd"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml70(td)
-msgid "(StrOpt) The RADOS pool in which rbd volumes are stored"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml73(td)
-msgid "images_type = default"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml74(td)
-msgid ""
-"(StrOpt) VM Images format. Acceptable values are: raw, qcow2, lvm, rbd, "
-"default. If default is specified, then use_cow_images flag is used instead "
-"of this one."
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml77(td)
-msgid "images_volume_group = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml78(td)
-msgid ""
-"(StrOpt) LVM Volume Group that is used for VM images, when you specify "
-"images_type=lvm."
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml81(td)
-msgid "inject_key = False"
-msgstr "inject_key = False"
-
-#: ./doc/common/tables/nova-hypervisor.xml82(td)
-msgid "(BoolOpt) Inject the ssh public key at boot time"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml85(td)
-msgid "inject_partition = -2"
-msgstr "inject_partition = -2"
-
-#: ./doc/common/tables/nova-hypervisor.xml86(td)
-msgid ""
-"(IntOpt) The partition to inject to : -2 =&gt; disable, -1 =&gt; inspect "
-"(libguestfs only), 0 =&gt; not partitioned, &gt;0 =&gt; partition number"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml89(td)
-msgid "inject_password = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml90(td)
-msgid "(BoolOpt) Inject the admin password at boot time, without an agent."
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml93(td)
-msgid "iscsi_use_multipath = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml94(td)
-msgid "(BoolOpt) Use multipath connection of the iSCSI volume"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml97(td)
-msgid "iser_use_multipath = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml98(td)
-msgid "(BoolOpt) Use multipath connection of the iSER volume"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml101(td)
-msgid "rescue_image_id = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml102(td)
-msgid "(StrOpt) Rescue ami image"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml105(td)
-msgid "rescue_kernel_id = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml106(td)
-msgid "(StrOpt) Rescue aki image"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml109(td)
-msgid "rescue_ramdisk_id = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml110(td)
-msgid "(StrOpt) Rescue ari image"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml113(td)
-msgid "snapshot_compression = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml114(td)
-msgid ""
-"(BoolOpt) Compress snapshot images when possible. This currently applies "
-"exclusively to qcow2 images"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml117(td)
-msgid "snapshot_image_format = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml118(td)
-msgid ""
-"(StrOpt) Snapshot image format (valid options are : raw, qcow2, vmdk, vdi). "
-"Defaults to same as source image"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml121(td)
-msgid "sparse_logical_volumes = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml122(td)
-msgid ""
-"(BoolOpt) Create sparse logical volumes (with virtualsize) if this flag is "
-"set to True."
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml125(td)
-msgid "use_usb_tablet = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml126(td)
-msgid "(BoolOpt) Sync virtual and real mouse cursors in Windows VMs"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml129(td)
-msgid "use_virtio_for_bridges = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml130(td)
-msgid "(BoolOpt) Use virtio for bridge interfaces with KVM/QEMU"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml8(caption)
-#: ./doc/common/tables/heat-rabbitmq.xml8(caption)
-#: ./doc/common/tables/glance-rabbitmq.xml8(caption)
-#: ./doc/common/tables/neutron-rabbitmq.xml8(caption)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml8(caption)
-#: ./doc/common/tables/nova-rabbitmq.xml8(caption)
-msgid "Description of configuration options for rabbitmq"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml23(td)
-#: ./doc/common/tables/heat-rabbitmq.xml39(td)
-msgid ""
-"(BoolOpt) use H/A queues in RabbitMQ (x-ha-policy: all).You need to wipe "
-"RabbitMQ database when changing this option."
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml27(td)
-#: ./doc/common/tables/heat-rabbitmq.xml43(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml27(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml47(td)
-msgid "(StrOpt) The RabbitMQ broker address where a single node is used"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml31(td)
-#: ./doc/common/tables/heat-rabbitmq.xml47(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml31(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml51(td)
-msgid "(ListOpt) RabbitMQ HA cluster host:port pairs"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml35(td)
-#: ./doc/common/tables/heat-rabbitmq.xml51(td)
-msgid ""
-"(IntOpt) maximum retries with trying to connect to RabbitMQ (the default of "
-"0 implies an infinite retry count)"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml39(td)
-#: ./doc/common/tables/heat-rabbitmq.xml55(td)
-msgid "(StrOpt) the RabbitMQ password"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml43(td)
-#: ./doc/common/tables/heat-rabbitmq.xml59(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml43(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml63(td)
-msgid "(IntOpt) The RabbitMQ broker port where a single node is used"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml47(td)
-#: ./doc/common/tables/heat-rabbitmq.xml63(td)
-msgid ""
-"(IntOpt) how long to backoff for between retries when connecting to RabbitMQ"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml51(td)
-#: ./doc/common/tables/heat-rabbitmq.xml67(td)
-msgid "(IntOpt) how frequently to retry connecting with RabbitMQ"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml55(td)
-#: ./doc/common/tables/heat-rabbitmq.xml71(td)
-msgid "(BoolOpt) connect over SSL for RabbitMQ"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml59(td)
-#: ./doc/common/tables/heat-rabbitmq.xml75(td)
-msgid "(StrOpt) the RabbitMQ userid"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml63(td)
-#: ./doc/common/tables/heat-rabbitmq.xml79(td)
-msgid "(StrOpt) the RabbitMQ virtual host"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml7(literal)
-msgid "[filter:tempurl]"
-msgstr "[filter:tempurl]"
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml18(td)
-msgid "use = egg:swift#tempurl"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml21(td)
-msgid "methods = GET HEAD PUT"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml21(td)
-msgid "HTTP methods allowed with Temporary URLs"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml24(td)
-msgid "incoming_remove_headers = x-timestamp"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml24(td)
-msgid ""
-"Headers to remove from incoming requests. Simply a whitespace delimited list"
-" of header names and names can optionally end with '*' to indicate a prefix "
-"match."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml28(td)
-msgid "incoming_allow_headers ="
-msgstr "incoming_allow_headers ="
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml28(td)
-msgid ""
-"Headers allowed as exceptions to incoming_remove_headers. Simply a "
-"whitespace delimited list of header names and names can optionally end with "
-"'*' to indicate a prefix match."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml33(td)
-msgid "outgoing_remove_headers = x-object-meta-*"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml33(td)
-msgid ""
-"Headers to remove from outgoing responses. Simply a whitespace delimited "
-"list of header names and names can optionally end with '*' to indicate a "
-"prefix match."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml38(td)
-msgid "outgoing_allow_headers = x-object-meta-public-*"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml38(td)
-msgid ""
-"Headers allowed as exceptions to outgoing_allow_headers. Simply a whitespace"
-" delimited list of header names and names can optionally end with '*' to "
-"indicate a prefix match."
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml8(caption)
-#: ./doc/common/tables/neutron-api.xml8(caption)
-#: ./doc/common/tables/cinder-api.xml8(caption)
-#: ./doc/common/tables/ceilometer-api.xml8(caption)
-#: ./doc/common/tables/heat-api.xml8(caption)
-#: ./doc/common/tables/nova-api.xml8(caption)
-#: ./doc/common/tables/glance-api.xml8(caption)
-#: ./doc/common/tables/keystone-api.xml8(caption)
-msgid "Description of configuration options for api"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml22(td)
-msgid "admin_roles = admin"
-msgstr "admin_roles = admin"
-
-#: ./doc/common/tables/trove-api.xml26(td)
-msgid "api_extensions_path = trove/extensions/routes"
-msgstr "api_extensions_path = trove/extensions/routes"
-
-#: ./doc/common/tables/trove-api.xml27(td)
-msgid "(StrOpt) Path to extensions."
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml30(td)
-#: ./doc/common/tables/neutron-api.xml38(td)
-#: ./doc/common/tables/cinder-api.xml22(td)
-#: ./doc/common/tables/nova-wsgi.xml22(td)
-#: ./doc/common/tables/heat-api.xml134(td)
-msgid "api_paste_config = api-paste.ini"
-msgstr "api_paste_config = api-paste.ini"
-
-#: ./doc/common/tables/trove-api.xml31(td)
-msgid "(StrOpt) File name for the paste.deploy config for trove-api."
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml34(td)
-msgid "bind_port = 8779"
-msgstr "bind_port = 8779"
-
-#: ./doc/common/tables/trove-api.xml35(td)
-#: ./doc/common/tables/trove-api.xml47(td)
-#: ./doc/common/tables/trove-api.xml51(td)
-#: ./doc/common/tables/trove-api.xml55(td)
-#: ./doc/common/tables/trove-api.xml59(td)
-#: ./doc/common/tables/trove-api.xml63(td)
-#: ./doc/common/tables/trove-api.xml79(td)
-#: ./doc/common/tables/trove-api.xml87(td)
-#: ./doc/common/tables/trove-api.xml103(td)
-#: ./doc/common/tables/trove-taskmanager.xml43(td)
-#: ./doc/common/tables/trove-taskmanager.xml47(td)
-#: ./doc/common/tables/trove-taskmanager.xml51(td)
-#: ./doc/common/tables/trove-taskmanager.xml55(td)
-#: ./doc/common/tables/trove-taskmanager.xml59(td)
-#: ./doc/common/tables/trove-backup.xml71(td)
-#: ./doc/common/tables/trove-volume.xml39(td)
-#: ./doc/common/tables/trove-volume.xml47(td)
-#: ./doc/common/tables/trove-database.xml27(td)
-#: ./doc/common/tables/trove-rpc.xml39(td)
-#: ./doc/common/tables/trove-rpc.xml43(td)
-#: ./doc/common/tables/trove-common.xml23(td)
-#: ./doc/common/tables/trove-common.xml27(td)
-#: ./doc/common/tables/trove-common.xml47(td)
-#: ./doc/common/tables/trove-dns.xml71(td)
-#: ./doc/common/tables/trove-dns.xml75(td)
-#: ./doc/common/tables/trove-heat.xml23(td)
-#: ./doc/common/tables/trove-guestagent.xml23(td)
-#: ./doc/common/tables/trove-guestagent.xml27(td)
-#: ./doc/common/tables/trove-guestagent.xml31(td)
-msgid "(IntOpt) No help text available for this option."
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml38(td)
-msgid "db_api_implementation = trove.db.sqlalchemy.api"
-msgstr "db_api_implementation = trove.db.sqlalchemy.api"
-
-#: ./doc/common/tables/trove-api.xml42(td)
-msgid "hostname_require_ipv4 = True"
-msgstr "hostname_require_ipv4 = True"
-
-#: ./doc/common/tables/trove-api.xml43(td)
-msgid "(BoolOpt) Require user hostnames to be IPv4 addresses."
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml46(td)
-msgid "http_delete_rate = 200"
-msgstr "http_delete_rate = 200"
-
-#: ./doc/common/tables/trove-api.xml50(td)
-msgid "http_get_rate = 200"
-msgstr "http_get_rate = 200"
-
-#: ./doc/common/tables/trove-api.xml54(td)
-msgid "http_post_rate = 200"
-msgstr "http_post_rate = 200"
-
-#: ./doc/common/tables/trove-api.xml58(td)
-msgid "http_put_rate = 200"
-msgstr "http_put_rate = 200"
-
-#: ./doc/common/tables/trove-api.xml62(td)
-msgid "instances_page_size = 20"
-msgstr "instances_page_size = 20"
-
-#: ./doc/common/tables/trove-api.xml67(td)
-#: ./doc/common/tables/glance-wsgi.xml31(td)
-msgid ""
-"(IntOpt) Maximum line size of message headers to be accepted. "
-"max_header_line may need to be increased when using large tokens (typically "
-"those generated by the Keystone v3 API with big service catalogs"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml70(td)
-msgid "region = LOCAL_DEV"
-msgstr "region = LOCAL_DEV"
-
-#: ./doc/common/tables/trove-api.xml71(td)
-msgid "(StrOpt) The region this service is located."
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml74(td)
-#: ./doc/common/tables/glance-wsgi.xml34(td)
-#: ./doc/common/tables/neutron-wsgi.xml30(td)
-#: ./doc/common/tables/nova-wsgi.xml38(td)
-#: ./doc/common/tables/cinder-common.xml198(td)
-#: ./doc/common/tables/keystone-api.xml86(td)
-msgid "tcp_keepidle = 600"
-msgstr "tcp_keepidle = 600"
-
-#: ./doc/common/tables/trove-api.xml75(td)
-#: ./doc/common/tables/neutron-wsgi.xml31(td)
-#: ./doc/common/tables/nova-wsgi.xml39(td)
-#: ./doc/common/tables/cinder-common.xml199(td)
-msgid ""
-"(IntOpt) Sets the value of TCP_KEEPIDLE in seconds for each server socket. "
-"Not supported on OS X."
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml78(td)
-msgid "trove_api_workers = None"
-msgstr "trove_api_workers = None"
-
-#: ./doc/common/tables/trove-api.xml82(td)
-msgid "trove_auth_url = http://0.0.0.0:5000/v2.0"
-msgstr "trove_auth_url = http://0.0.0.0:5000/v2.0"
-
-#: ./doc/common/tables/trove-api.xml86(td)
-msgid "trove_conductor_workers = 1"
-msgstr "trove_conductor_workers = 1"
-
-#: ./doc/common/tables/trove-api.xml90(td)
-msgid "trove_security_group_name_prefix = SecGroup"
-msgstr "trove_security_group_name_prefix = SecGroup"
-
-#: ./doc/common/tables/trove-api.xml94(td)
-msgid "trove_security_group_rule_cidr = 0.0.0.0/0"
-msgstr "trove_security_group_rule_cidr = 0.0.0.0/0"
-
-#: ./doc/common/tables/trove-api.xml98(td)
-msgid "trove_security_groups_support = True"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml102(td)
-msgid "users_page_size = 20"
-msgstr "users_page_size = 20"
-
-#: ./doc/common/tables/cinder-quota.xml8(caption)
-#: ./doc/common/tables/trove-quota.xml8(caption)
-#: ./doc/common/tables/heat-quota.xml8(caption)
-#: ./doc/common/tables/nova-quota.xml8(caption)
-msgid "Description of configuration options for quota"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml22(td)
-#: ./doc/common/tables/nova-policy.xml34(td)
-msgid "max_age = 0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml23(td)
-msgid "(IntOpt) number of seconds between subsequent usage refreshes"
-msgstr "(IntOpt) nombre de secondes entre les rafraîchissements d'usage"
-
-#: ./doc/common/tables/cinder-quota.xml26(td)
-msgid "quota_driver = cinder.quota.DbQuotaDriver"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml27(td)
-msgid "(StrOpt) default driver to use for quota checks"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml30(td)
-msgid "quota_gigabytes = 1000"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml31(td)
-msgid ""
-"(IntOpt) number of volume gigabytes (snapshots are also included) allowed "
-"per project"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml34(td)
-msgid "quota_snapshots = 10"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml35(td)
-msgid "(IntOpt) number of volume snapshots allowed per project"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml38(td)
-msgid "quota_volumes = 10"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml39(td)
-msgid "(IntOpt) number of volumes allowed per project"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml42(td)
-#: ./doc/common/tables/nova-policy.xml66(td)
-msgid "reservation_expire = 86400"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml43(td)
-msgid "(IntOpt) number of seconds until a reservation expires"
-msgstr "(IntOpt) nombre de secondes jusqu'à ce qu'une réservation expire"
-
-#: ./doc/common/tables/cinder-quota.xml46(td)
-msgid "use_default_quota_class = True"
-msgstr "use_default_quota_class = True"
-
-#: ./doc/common/tables/cinder-quota.xml47(td)
-msgid "(BoolOpt) whether to use default quota class for default quota"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml7(literal)
-#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml7(literal)
-#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml7(literal)
-#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml7(literal)
-msgid "[filter:healthcheck]"
-msgstr "[filter:healthcheck]"
-
-#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml18(td)
-#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml18(td)
-#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml18(td)
-#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml18(td)
-msgid "use = egg:swift#healthcheck"
-msgstr "use = egg:swift#healthcheck"
-
-#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml21(td)
-#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml21(td)
-#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml21(td)
-#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml21(td)
-msgid "disable_path ="
-msgstr "disable_path ="
-
-#: ./doc/common/tables/nova-console.xml8(caption)
-msgid "Description of configuration options for console"
-msgstr "Description des options de configuration pour la console"
-
-#: ./doc/common/tables/nova-console.xml22(td)
-msgid "console_public_hostname = oslo"
-msgstr "console_public_hostname = oslo"
-
-#: ./doc/common/tables/nova-console.xml23(td)
-msgid "(StrOpt) Publicly visible name for this console host"
-msgstr ""
-
-#: ./doc/common/tables/nova-console.xml26(td)
-msgid "console_token_ttl = 600"
-msgstr "console_token_ttl = 600"
-
-#: ./doc/common/tables/nova-console.xml27(td)
-msgid "(IntOpt) How many seconds before deleting tokens"
-msgstr ""
-
-#: ./doc/common/tables/nova-console.xml30(td)
-msgid "consoleauth_manager = nova.consoleauth.manager.ConsoleAuthManager"
-msgstr "consoleauth_manager = nova.consoleauth.manager.ConsoleAuthManager"
-
-#: ./doc/common/tables/nova-console.xml31(td)
-msgid "(StrOpt) Manager for console auth"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml8(caption)
-msgid "Description of configuration options for events"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml19(th)
-msgid "[event]"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml22(td)
-msgid "definitions_cfg_file = event_definitions.yaml"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml23(td)
-msgid "(StrOpt) Configuration file for event definitions."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml26(td)
-msgid "drop_unmatched_notifications = False"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml27(td)
-msgid ""
-"(BoolOpt) Drop notifications if no event definition matches. (Otherwise, we "
-"convert them with just the default traits)"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml30(th)
-msgid "[notification]"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml33(td)
-msgid "ack_on_event_error = True"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml34(td)
-msgid "(BoolOpt) Acknowledge message when event persistence fails."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml37(td)
-msgid "store_events = False"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml38(td)
-msgid "(BoolOpt) Save event details."
-msgstr ""
-
-#: ./doc/common/tables/keystone-os_inherit.xml8(caption)
-msgid "Description of configuration options for os_inherit"
-msgstr ""
-
-#: ./doc/common/tables/keystone-os_inherit.xml19(th)
-msgid "[os_inherit]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-os_inherit.xml22(td)
-#: ./doc/common/tables/keystone-cache.xml38(td)
-#: ./doc/common/tables/neutron-fwaas.xml22(td)
-#: ./doc/common/tables/nova-spice.xml26(td)
-#: ./doc/common/tables/nova-apiv3.xml22(td)
-#: ./doc/common/tables/nova-rdp.xml22(td)
-msgid "enabled = False"
-msgstr ""
-
-#: ./doc/common/tables/keystone-os_inherit.xml23(td)
-msgid ""
-"(BoolOpt) role-assignment inheritance to projects from owning domain can be "
-"optionally enabled."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients.xml8(caption)
-msgid "Description of configuration options for clients"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients.xml22(td)
-msgid "region_name_for_services = None"
-msgstr "region_name_for_services = None"
-
-#: ./doc/common/tables/heat-clients.xml23(td)
-msgid "(StrOpt) Default region name used to get services endpoints."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients.xml26(th)
-msgid "[clients]"
-msgstr "[clients]"
-
-#: ./doc/common/tables/heat-notification.xml8(caption)
-#: ./doc/common/tables/keystone-notification.xml8(caption)
-msgid "Description of configuration options for notification"
-msgstr ""
-
-#: ./doc/common/tables/heat-notification.xml22(td)
-#: ./doc/common/tables/keystone-notification.xml22(td)
-msgid "onready = None"
-msgstr "onready = None"
-
-#: ./doc/common/tables/heat-notification.xml23(td)
-msgid ""
-"(StrOpt) onready allows you to send a notification when the heat processes "
-"are ready to serve. This is either a module with the notify() method or a "
-"shell command. To enable notifications with systemd, one may use the "
-"'systemd-notify --ready' shell command or the 'heat.common.systemd' "
-"notification module."
-msgstr ""
-
-#: ./doc/common/tables/keystone-assignment.xml8(caption)
-msgid "Description of configuration options for assignment"
-msgstr ""
-
-#: ./doc/common/tables/keystone-assignment.xml19(th)
-msgid "[assignment]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-assignment.xml22(td)
-#: ./doc/common/tables/keystone-token.xml26(td)
-msgid "cache_time = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-assignment.xml23(td)
-msgid ""
-"(IntOpt) TTL (in seconds) to cache assignment data. This has no effect "
-"unless global caching is enabled."
-msgstr ""
-
-#: ./doc/common/tables/keystone-assignment.xml26(td)
-#: ./doc/common/tables/keystone-token.xml30(td)
-#: ./doc/common/tables/keystone-revoke.xml22(td)
-msgid "caching = True"
-msgstr ""
-
-#: ./doc/common/tables/keystone-assignment.xml27(td)
-msgid ""
-"(BoolOpt) Toggle for assignment caching. This has no effect unless global "
-"caching is enabled."
-msgstr ""
-
-#: ./doc/common/tables/keystone-assignment.xml30(td)
-msgid "driver = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-assignment.xml31(td)
-msgid "(StrOpt) Keystone Assignment backend driver."
-msgstr ""
-
-#: ./doc/common/tables/keystone-assignment.xml35(td)
-msgid ""
-"(IntOpt) Maximum number of entities that will be returned in an assignment "
-"collection."
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml22(td)
-msgid "bindir = /usr/local/bin"
-msgstr "bindir = /usr/local/bin"
-
-#: ./doc/common/tables/nova-common.xml23(td)
-msgid "(StrOpt) Directory where nova binaries are installed"
-msgstr "(StrOpt)  Répertoire où les binaires nova sont installées"
-
-#: ./doc/common/tables/nova-common.xml26(td)
-msgid "compute_topic = compute"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml27(td)
-msgid "(StrOpt) The topic compute nodes listen on"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml30(td)
-msgid "console_topic = console"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml31(td)
-msgid "(StrOpt) The topic console proxy nodes listen on"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml34(td)
-msgid "consoleauth_topic = consoleauth"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml35(td)
-msgid "(StrOpt) The topic console auth proxy nodes listen on"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml43(td)
-msgid ""
-"(StrOpt) Name of this node. This can be an opaque identifier. It is not "
-"necessarily a hostname, FQDN, or IP address. However, the node name must be "
-"valid within an AMQP key, and if using ZeroMQ, a valid hostname, FQDN, or IP"
-" address"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml54(td)
-#: ./doc/common/tables/cinder-common.xml118(td)
-msgid "my_ip = 10.0.0.1"
-msgstr "my_ip = 10.0.0.1"
-
-#: ./doc/common/tables/nova-common.xml55(td)
-msgid "(StrOpt) IP address of this host"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml58(td)
-#: ./doc/common/tables/cinder-rpc.xml74(td)
-#: ./doc/common/tables/keystone-amqp.xml38(td)
-#: ./doc/common/tables/neutron-notifier.xml30(td)
-#: ./doc/common/tables/glance-amqp.xml30(td)
-#: ./doc/common/tables/heat-amqp.xml50(td)
-#: ./doc/common/tables/ceilometer-amqp.xml30(td)
-#: ./doc/common/tables/trove-amqp.xml58(td)
-msgid "notification_driver = []"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml59(td)
-#: ./doc/common/tables/cinder-rpc.xml75(td)
-#: ./doc/common/tables/keystone-amqp.xml39(td)
-#: ./doc/common/tables/glance-amqp.xml31(td)
-msgid "(MultiStrOpt) Driver or drivers to handle sending notifications."
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml62(td)
-#: ./doc/common/tables/cinder-rpc.xml78(td)
-#: ./doc/common/tables/keystone-amqp.xml42(td)
-#: ./doc/common/tables/neutron-notifier.xml34(td)
-#: ./doc/common/tables/glance-amqp.xml34(td)
-#: ./doc/common/tables/heat-amqp.xml54(td)
-#: ./doc/common/tables/ceilometer-amqp.xml34(td)
-#: ./doc/common/tables/trove-amqp.xml66(td)
-msgid "notification_topics = notifications"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml63(td)
-#: ./doc/common/tables/cinder-rpc.xml79(td)
-#: ./doc/common/tables/keystone-amqp.xml43(td)
-#: ./doc/common/tables/glance-amqp.xml35(td)
-msgid "(ListOpt) AMQP topic used for OpenStack notifications."
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml66(td)
-msgid "notify_api_faults = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml67(td)
-msgid ""
-"(BoolOpt) If set, send api.fault notifications on caught exceptions in the "
-"API service."
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml70(td)
-msgid "notify_on_state_change = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml71(td)
-msgid ""
-"(StrOpt) If set, send compute.instance.update notifications on instance "
-"state changes. Valid values are None for no notifications, \"vm_state\" for "
-"notifications on VM state changes, or \"vm_and_task_state\" for "
-"notifications on VM and task state changes."
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml78(td)
-msgid "pybasedir = /usr/lib/python/site-packages"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml79(td)
-msgid "(StrOpt) Directory where the nova python module is installed"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml82(td)
-#: ./doc/common/tables/cinder-common.xml146(td)
-#: ./doc/common/tables/trove-rpc.xml46(td)
-msgid "report_interval = 10"
-msgstr "report_interval = 10"
-
-#: ./doc/common/tables/nova-common.xml83(td)
-msgid "(IntOpt) Seconds between nodes reporting state to datastore"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml86(td)
-msgid "rootwrap_config = /etc/nova/rootwrap.conf"
-msgstr "rootwrap_config = /etc/nova/rootwrap.conf"
-
-#: ./doc/common/tables/nova-common.xml87(td)
-#: ./doc/common/tables/cinder-common.xml155(td)
-msgid ""
-"(StrOpt) Path to the rootwrap configuration file to use for running commands"
-" as root"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml90(td)
-#: ./doc/common/tables/cinder-common.xml162(td)
-msgid "service_down_time = 60"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml91(td)
-msgid "(IntOpt) Maximum time since last check-in for up service"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml94(td)
-msgid "state_path = $pybasedir"
-msgstr "state_path = $pybasedir"
-
-#: ./doc/common/tables/nova-common.xml95(td)
-msgid "(StrOpt) Top-level directory for maintaining nova's state"
-msgstr "(StrOpt)  Répertoire de haut niveau pour maintenir l'état de nova"
-
-#: ./doc/common/tables/nova-common.xml98(td)
-msgid "tempdir = None"
-msgstr "tempdir = None"
-
-#: ./doc/common/tables/nova-common.xml99(td)
-msgid "(StrOpt) Explicitly specify the temporary working directory"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml102(td)
-#: ./doc/common/tables/cinder-rpc.xml230(td)
-#: ./doc/common/tables/keystone-amqp.xml66(td)
-#: ./doc/common/tables/glance-amqp.xml54(td)
-msgid "transport_url = None"
-msgstr "transport_url = None"
-
-#: ./doc/common/tables/nova-common.xml103(td)
-#: ./doc/common/tables/cinder-rpc.xml231(td)
-#: ./doc/common/tables/keystone-amqp.xml67(td)
-#: ./doc/common/tables/glance-amqp.xml55(td)
-msgid ""
-"(StrOpt) A URL representing the messaging driver to use and its full "
-"configuration. If not set, we fall back to the rpc_backend option and driver"
-" specific configuration."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-updater.xml7(literal)
-msgid "[object-updater]"
-msgstr "[object-updater]"
-
-#: ./doc/common/tables/swift-object-server-object-updater.xml18(td)
-msgid "log_name = object-updater"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-updater.xml33(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml39(td)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml30(td)
-msgid "concurrency = 1"
-msgstr "concurrency = 1"
-
-#: ./doc/common/tables/swift-object-server-object-updater.xml36(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml57(td)
-msgid "node_timeout = &lt;whatever's in the DEFAULT section or 10&gt;"
-msgstr ""
-
-#: ./doc/common/tables/glance-zmq.xml8(caption)
-msgid "Description of configuration options for zmq"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metering_agent.xml8(caption)
-msgid "Description of configuration options for metering_agent"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metering_agent.xml22(td)
-msgid ""
-"driver = "
-"neutron.services.metering.drivers.noop.noop_driver.NoopMeteringDriver"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metering_agent.xml23(td)
-msgid "(StrOpt) Metering driver"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metering_agent.xml26(td)
-msgid "measure_interval = 30"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metering_agent.xml27(td)
-msgid "(IntOpt) Interval between two metering measures"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metering_agent.xml33(td)
-msgid "report_interval = 30"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metering_agent.xml34(td)
-msgid ""
-"(FloatOpt) Seconds between nodes reporting state to server; should be less "
-"than agent_down_time, best if it is half or less than agent_down_time."
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml8(caption)
-msgid "Description of configuration options for taskmanager"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml22(td)
-msgid "cloudinit_location = /etc/trove/cloudinit"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml23(td)
-msgid "(StrOpt) Path to folder with cloudinit scripts."
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml26(td)
-msgid "datastore_manager = None"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml27(td)
-msgid ""
-"(StrOpt) Manager class in guestagent, setup by taskmanager on instance "
-"provision."
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml30(td)
-msgid "datastore_registry_ext = {}"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml31(td)
-msgid ""
-"(DictOpt) Extension for default datastore managers. Allows to use custom "
-"managers for each of datastore supported in trove."
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml34(td)
-msgid "exists_notification_ticks = 360"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml35(td)
-msgid ""
-"(IntOpt) Number of report_intervals to wait between pushing events (see "
-"report_interval)."
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml38(td)
-msgid "exists_notification_transformer = None"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml39(td)
-msgid "(StrOpt) Transformer for exists notifications."
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml42(td)
-msgid "reboot_time_out = 120"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml46(td)
-msgid "resize_time_out = 600"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml50(td)
-msgid "revert_time_out = 600"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml54(td)
-msgid "server_delete_time_out = 60"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml58(td)
-msgid "state_change_wait_time = 180"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml62(td)
-msgid "update_status_on_fail = False"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml63(td)
-msgid ""
-"(BoolOpt) If instance fails to become active, taskmanager updates statuses, "
-"service status = FAILED_TIMEOUT_GUESTAGENT, instance task status = "
-"BUILDING_ERROR_TIMEOUT_GA."
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml66(td)
-#: ./doc/common/tables/trove-guestagent.xml66(td)
-msgid "usage_sleep_time = 5"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml67(td)
-#: ./doc/common/tables/trove-guestagent.xml67(td)
-msgid "(IntOpt) Time to sleep during the check active guest."
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml70(td)
-msgid "use_heat = False"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml74(td)
-msgid "use_nova_server_volume = False"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml78(td)
-msgid "verify_swift_checksum_on_restore = True"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml79(td)
-msgid ""
-"(BoolOpt) Enable verification of swift checksum before starting restore; "
-"makes sure the checksum of original backup matches checksum of the swift "
-"backup file."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml7(literal)
-msgid "[filter:account-quotas]"
-msgstr "[filter:account-quotas]"
-
-#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml18(td)
-msgid "use = egg:swift#account_quotas"
-msgstr "use = egg:swift#account_quotas"
-
-#: ./doc/common/tables/keystone-zeromq.xml8(caption)
-#: ./doc/common/tables/trove-zeromq.xml8(caption)
-#: ./doc/common/tables/heat-zeromq.xml8(caption)
-#: ./doc/common/tables/nova-zeromq.xml8(caption)
-#: ./doc/common/tables/neutron-zeromq.xml8(caption)
-msgid "Description of configuration options for zeromq"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml7(literal)
-#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml7(literal)
-msgid "[app:proxy-server]"
-msgstr "[app:proxy-server]"
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml18(td)
-#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml18(td)
-msgid "use = egg:swift#proxy"
-msgstr "use = egg:swift#proxy"
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml21(td)
-msgid "set log_name = proxy-server"
-msgstr "set log_name = proxy-server"
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml33(td)
-msgid "log_handoffs = true"
-msgstr "log_handoffs = true"
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml36(td)
-msgid "recheck_account_existence = 60"
-msgstr "recheck_account_existence = 60"
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml36(td)
-msgid "Cache timeout in seconds to send memcached for account existence"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml39(td)
-msgid "recheck_container_existence = 60"
-msgstr "recheck_container_existence = 60"
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml39(td)
-msgid "Cache timeout in seconds to send memcached for container existence"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml42(td)
-msgid "object_chunk_size = 8192"
-msgstr "object_chunk_size = 8192"
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml42(td)
-msgid "Chunk size to read from object servers"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml45(td)
-msgid "client_chunk_size = 8192"
-msgstr "client_chunk_size = 8192"
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml45(td)
-msgid "Chunk size to read from clients"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml51(td)
-msgid "recoverable_node_timeout = node_timeout"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml51(td)
-msgid ""
-"Request timeout to external services for requests that, on failure, can be "
-"recovered from. For example, object GET. from a client external services"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml57(td)
-msgid "post_quorum_timeout = 0.5"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml60(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml45(td)
-msgid "error_suppression_interval = 60"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml60(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml45(td)
-msgid ""
-"Time in seconds that must elapse since the last error for a node to be "
-"considered no longer error limited"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml63(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml48(td)
-msgid "error_suppression_limit = 10"
-msgstr "error_suppression_limit = 10"
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml63(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml48(td)
-msgid "Error count to consider a node error limited"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml66(td)
-msgid "allow_account_management = false"
-msgstr "allow_account_management = false"
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml66(td)
-msgid "Whether account PUTs and DELETEs are even callable"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml69(td)
-msgid "object_post_as_copy = true"
-msgstr "object_post_as_copy = true"
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml69(td)
-msgid ""
-"Set object_post_as_copy = false to turn on fast posts where only the "
-"metadata changes are stored anew and the original data file is kept in "
-"place. This makes for quicker posts; but since the container metadata isn't "
-"updated in this mode, features like container sync won't be able to sync "
-"posts."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml72(td)
-msgid "account_autocreate = false"
-msgstr "account_autocreate = false"
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml72(td)
-msgid ""
-"If set to 'true' authorized accounts that do not yet exist within the Swift "
-"cluster will be automatically created."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml75(td)
-msgid "max_containers_per_account = 0"
-msgstr "max_containers_per_account = 0"
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml75(td)
-msgid ""
-"If set to a positive value, trying to create a container when the account "
-"already has at least this maximum containers will result in a 403 Forbidden."
-" Note: This is a soft limit, meaning a user might exceed the cap for "
-"recheck_account_existence before the 403s kick in."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml78(td)
-msgid "max_containers_whitelist ="
-msgstr "max_containers_whitelist ="
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml78(td)
-msgid ""
-"is a comma separated list of account names that ignore the "
-"max_containers_per_account cap."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml81(td)
-msgid "deny_host_headers ="
-msgstr "deny_host_headers ="
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml84(td)
-#: ./doc/common/tables/swift-account-server-app-account-server.xml36(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml45(td)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml54(td)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml21(td)
-msgid "auto_create_account_prefix = ."
-msgstr "auto_create_account_prefix = ."
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml84(td)
-#: ./doc/common/tables/swift-account-server-app-account-server.xml36(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml45(td)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml54(td)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml21(td)
-msgid "Prefix to use when automatically creating accounts"
-msgstr "Préfixe à utiliser avec la création automatique des comptes"
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml87(td)
-msgid "put_queue_depth = 10"
-msgstr "put_queue_depth = 10"
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml90(td)
-msgid "sorting_method = shuffle"
-msgstr "sorting_method = shuffle"
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml93(td)
-msgid "timing_expiry = 300"
-msgstr "timing_expiry = 300"
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml96(td)
-msgid "max_large_object_get_time = 86400"
-msgstr "max_large_object_get_time = 86400"
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml99(td)
-msgid "request_node_count = 2 * replicas"
-msgstr "request_node_count = 2 * replicas"
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml99(td)
-msgid ""
-"* replicas Set to the number of nodes to contact for a normal request. You "
-"can use '* replicas' at the end to have it use the number given times the "
-"number of replicas for the ring being used for the request. conf file for "
-"values will only be shown to the list of swift_owners. The exact default "
-"definition of a swift_owner is headers&gt; up to the auth system in use, but"
-" usually indicates administrative responsibilities. paste.deploy to use for "
-"auth. To use tempauth set to: `egg:swift#tempauth` each request"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml102(td)
-msgid "read_affinity = r1z1=100, r1z2=200, r2=300"
-msgstr "read_affinity = r1z1=100, r1z2=200, r2=300"
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml105(td)
-msgid "read_affinity ="
-msgstr "read_affinity ="
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml108(td)
-msgid "write_affinity = r1, r2"
-msgstr "write_affinity = r1, r2"
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml111(td)
-msgid "write_affinity ="
-msgstr "write_affinity ="
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml114(td)
-msgid "write_affinity_node_count = 2 * replicas"
-msgstr "write_affinity_node_count = 2 * replicas"
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml117(td)
-msgid ""
-"swift_owner_headers = x-container-read, x-container-write, x-container-sync-"
-"key, x-container-sync-to, x-account-meta-temp-url-key, x-account-meta-temp-"
-"url-key-2, x-account-access-control"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml117(td)
-msgid ""
-"the sample These are the headers whose conf file for values will only be "
-"shown to the list of swift_owners. The exact default definition of a "
-"swift_owner is headers&gt; up to the auth system in use, but usually "
-"indicates administrative responsibilities. paste.deploy to use for auth. To "
-"use tempauth set to: `egg:swift#tempauth` each request"
-msgstr ""
-
-#: ./doc/common/tables/nova-keymgr.xml8(caption)
-#: ./doc/common/tables/cinder-keymgr.xml8(caption)
-msgid "Description of configuration options for keymgr"
-msgstr ""
-
-#: ./doc/common/tables/nova-keymgr.xml19(th)
-#: ./doc/common/tables/cinder-keymgr.xml19(th)
-msgid "[keymgr]"
-msgstr ""
-
-#: ./doc/common/tables/nova-keymgr.xml22(td)
-msgid "api_class = nova.keymgr.conf_key_mgr.ConfKeyManager"
-msgstr "api_class = nova.keymgr.conf_key_mgr.ConfKeyManager"
-
-#: ./doc/common/tables/nova-keymgr.xml23(td)
-#: ./doc/common/tables/cinder-keymgr.xml23(td)
-msgid "(StrOpt) The full class name of the key manager API class"
-msgstr ""
-
-#: ./doc/common/tables/nova-keymgr.xml26(td)
-#: ./doc/common/tables/cinder-keymgr.xml26(td)
-msgid "fixed_key = None"
-msgstr "fixed_key = None"
-
-#: ./doc/common/tables/nova-keymgr.xml27(td)
-#: ./doc/common/tables/cinder-keymgr.xml27(td)
-msgid "(StrOpt) Fixed key returned by key manager, specified in hex"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml7(literal)
-msgid "[filter:dlo]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml18(td)
-msgid "use = egg:swift#dlo"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml30(td)
-msgid "rate_limit_after_segment = 10"
-msgstr "rate_limit_after_segment = 10"
-
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml30(td)
-msgid ""
-"Rate limit the download of large object segments after this segment is "
-"downloaded."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml24(td)
-msgid "rate_limit_segments_per_sec = 1"
-msgstr "rate_limit_segments_per_sec = 1"
-
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml33(td)
-msgid ""
-"Rate limit large object downloads at this rate. contact for a normal "
-"request. You can use '* replicas' at the end to have it use the number given"
-" times the number of replicas for the ring being used for the request. "
-"paste.deploy to use for auth. To use tempauth set to: `egg:swift#tempauth` "
-"each request"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml36(td)
-msgid "max_get_time = 86400"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml22(td)
-msgid "allow_bulk = True"
-msgstr "allow_bulk = True"
-
-#: ./doc/common/tables/neutron-api.xml23(td)
-msgid "(BoolOpt) Allow the usage of the bulk API"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml26(td)
-msgid "allow_pagination = False"
-msgstr "allow_pagination = False"
-
-#: ./doc/common/tables/neutron-api.xml27(td)
-msgid "(BoolOpt) Allow the usage of the pagination"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml30(td)
-msgid "allow_sorting = False"
-msgstr "allow_sorting = False"
-
-#: ./doc/common/tables/neutron-api.xml31(td)
-msgid "(BoolOpt) Allow the usage of the sorting"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml34(td)
-msgid "api_extensions_path ="
-msgstr "api_extensions_path ="
-
-#: ./doc/common/tables/neutron-api.xml35(td)
-msgid "(StrOpt) The path for API extensions"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml39(td)
-msgid "(StrOpt) The API paste config file to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml43(td)
-msgid "(IntOpt) Max header line to accommodate large tokens"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml46(td)
-#: ./doc/common/tables/ceilometer-api.xml26(td)
-#: ./doc/common/tables/keystone-api.xml54(td)
-msgid "max_request_body_size = 114688"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml47(td)
-msgid "(IntOpt) the maximum body size per each request(bytes)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml50(td)
-msgid "pagination_max_limit = -1"
-msgstr "pagination_max_limit = -1"
-
-#: ./doc/common/tables/neutron-api.xml51(td)
-msgid ""
-"(StrOpt) The maximum number of items returned in a single response, value "
-"was 'infinite' or negative integer means no limit"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml54(td)
-#: ./doc/common/tables/nova-periodic.xml30(td)
-#: ./doc/common/tables/cinder-common.xml158(td)
-msgid "run_external_periodic_tasks = True"
-msgstr "run_external_periodic_tasks = True"
-
-#: ./doc/common/tables/neutron-api.xml55(td)
-#: ./doc/common/tables/nova-periodic.xml31(td)
-#: ./doc/common/tables/cinder-common.xml159(td)
-msgid ""
-"(BoolOpt) Some periodic tasks can be run in a separate process. Should we "
-"run them here?"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml58(td)
-msgid "service_plugins ="
-msgstr "service_plugins ="
-
-#: ./doc/common/tables/neutron-api.xml59(td)
-msgid "(ListOpt) The service plugins Neutron will use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml62(th)
-msgid "[service_providers]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml65(td)
-msgid "service_provider = []"
-msgstr "service_provider = []"
-
-#: ./doc/common/tables/neutron-api.xml66(td)
-msgid ""
-"(MultiStrOpt) Defines providers for advanced services using the format: "
-"&lt;service_type&gt;:&lt;name&gt;:&lt;driver&gt;[:default]"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-redis.xml23(td)
-msgid ""
-"(StrOpt) Name of this node, which must be valid in an AMQP key. Can be an "
-"opaque identifier. For ZeroMQ only, must be a valid host name, FQDN, or IP "
-"address."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-swift.xml8(caption)
-#: ./doc/common/tables/trove-swift.xml8(caption)
-#: ./doc/common/tables/glance-swift.xml8(caption)
-msgid "Description of configuration options for swift"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-swift.xml22(td)
-msgid "reseller_prefix = AUTH_"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-swift.xml23(td)
-msgid ""
-"(StrOpt) Swift reseller prefix. Must be on par with reseller_prefix in "
-"proxy-server.conf."
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml8(caption)
-msgid "Description of configuration options for hplefthand"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml22(td)
-msgid "hplefthand_api_url = None"
-msgstr "hplefthand_api_url = None"
-
-#: ./doc/common/tables/cinder-hplefthand.xml23(td)
-msgid ""
-"(StrOpt) HP LeftHand WSAPI Server Url like https://&lt;LeftHand "
-"ip&gt;:8081/lhos"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml26(td)
-msgid "hplefthand_clustername = None"
-msgstr "hplefthand_clustername = None"
-
-#: ./doc/common/tables/cinder-hplefthand.xml27(td)
-msgid "(StrOpt) HP LeftHand cluster name"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml30(td)
-msgid "hplefthand_debug = False"
-msgstr "hplefthand_debug = False"
-
-#: ./doc/common/tables/cinder-hplefthand.xml31(td)
-msgid "(BoolOpt) Enable HTTP debugging to LeftHand"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml34(td)
-msgid "hplefthand_iscsi_chap_enabled = False"
-msgstr "hplefthand_iscsi_chap_enabled = False"
-
-#: ./doc/common/tables/cinder-hplefthand.xml35(td)
-msgid ""
-"(BoolOpt) Configure CHAP authentication for iSCSI connections (Default: "
-"Disabled)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml38(td)
-msgid "hplefthand_password = None"
-msgstr "hplefthand_password = None"
-
-#: ./doc/common/tables/cinder-hplefthand.xml39(td)
-msgid "(StrOpt) HP LeftHand Super user password"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml42(td)
-msgid "hplefthand_username = None"
-msgstr "hplefthand_username = None"
-
-#: ./doc/common/tables/cinder-hplefthand.xml43(td)
-msgid "(StrOpt) HP LeftHand Super user username"
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml8(caption)
-#: ./doc/common/tables/glance-testing.xml8(caption)
-#: ./doc/common/tables/neutron-testing.xml8(caption)
-msgid "Description of configuration options for testing"
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml22(td)
-#: ./doc/common/tables/cinder-rpc.xml22(td)
-#: ./doc/common/tables/keystone-rpc.xml22(td)
-msgid ""
-"allowed_rpc_exception_modules = oslo.messaging.exceptions, nova.exception, "
-"cinder.exception, exceptions"
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml27(td)
-msgid ""
-"(StrOpt) Enable eventlet backdoor. Acceptable values are 0, &lt;port&gt; and"
-" &lt;start&gt;:&lt;end&gt;, where 0 results in listening on a random tcp "
-"port number, &lt;port&gt; results in listening on the specified port number "
-"and not enabling backdoorif it is in use and &lt;start&gt;:&lt;end&gt; "
-"results in listening on the smallest unused port number within the specified"
-" range of port numbers. The chosen port is displayed in the service's log "
-"file."
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml30(td)
-msgid "fake_call = False"
-msgstr "fake_call = False"
-
-#: ./doc/common/tables/nova-testing.xml31(td)
-msgid "(BoolOpt) If True, skip using the queue and make local calls"
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml34(td)
-msgid "fake_network = False"
-msgstr "fake_network = False"
-
-#: ./doc/common/tables/nova-testing.xml35(td)
-msgid "(BoolOpt) If passed, use fake network devices and addresses"
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml38(td)
-#: ./doc/common/tables/cinder-rpc.xml42(td)
-#: ./doc/common/tables/heat-amqp.xml42(td)
-#: ./doc/common/tables/glance-rabbitmq.xml26(td)
-#: ./doc/common/tables/keystone-rabbit.xml22(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml22(td)
-#: ./doc/common/tables/neutron-testing.xml26(td)
-#: ./doc/common/tables/trove-amqp.xml38(td)
-msgid "fake_rabbit = False"
-msgstr "fake_rabbit = False"
-
-#: ./doc/common/tables/nova-testing.xml39(td)
-#: ./doc/common/tables/cinder-rpc.xml43(td)
-#: ./doc/common/tables/glance-rabbitmq.xml27(td)
-#: ./doc/common/tables/keystone-rabbit.xml23(td)
-msgid "(BoolOpt) If passed, use a fake RabbitMQ provider."
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml42(td)
-#: ./doc/common/tables/cinder-common.xml110(td)
-msgid "monkey_patch = False"
-msgstr "monkey_patch = False"
-
-#: ./doc/common/tables/nova-testing.xml43(td)
-msgid "(BoolOpt) Whether to log monkey patching"
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml46(td)
-msgid ""
-"monkey_patch_modules = "
-"nova.api.ec2.cloud:nova.notifications.notify_decorator, "
-"nova.compute.api:nova.notifications.notify_decorator"
-msgstr "monkey_patch_modules = nova.api.ec2.cloud:nova.notifications.notify_decorator, nova.compute.api:nova.notifications.notify_decorator"
-
-#: ./doc/common/tables/nova-testing.xml47(td)
-#: ./doc/common/tables/cinder-common.xml115(td)
-msgid "(ListOpt) List of modules/decorators to monkey patch"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml8(caption)
-msgid "Description of configuration options for backups"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml22(td)
-msgid "backup_api_class = cinder.backup.api.API"
-msgstr "backup_api_class = cinder.backup.api.API"
-
-#: ./doc/common/tables/cinder-backups.xml23(td)
-msgid "(StrOpt) The full class name of the volume backup API class"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml26(td)
-msgid "backup_compression_algorithm = zlib"
-msgstr "backup_compression_algorithm = zlib"
-
-#: ./doc/common/tables/cinder-backups.xml27(td)
-msgid "(StrOpt) Compression algorithm (None to disable)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml30(td)
-msgid "backup_driver = cinder.backup.drivers.swift"
-msgstr "backup_driver = cinder.backup.drivers.swift"
-
-#: ./doc/common/tables/cinder-backups.xml31(td)
-msgid "(StrOpt) Driver to use for backups."
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml34(td)
-msgid "backup_manager = cinder.backup.manager.BackupManager"
-msgstr "backup_manager = cinder.backup.manager.BackupManager"
-
-#: ./doc/common/tables/cinder-backups.xml35(td)
-msgid "(StrOpt) full class name for the Manager for volume backup"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml38(td)
-msgid "backup_metadata_version = 1"
-msgstr "backup_metadata_version = 1"
-
-#: ./doc/common/tables/cinder-backups.xml39(td)
-msgid ""
-"(IntOpt) Backup metadata version to be used when backing up volume metadata."
-" If this number is bumped, make sure the service doing the restore supports "
-"the new version."
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml42(td)
-msgid "backup_name_template = backup-%s"
-msgstr "backup_name_template = backup-%s"
-
-#: ./doc/common/tables/cinder-backups.xml43(td)
-msgid "(StrOpt) Template string to be used to generate backup names"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml46(td)
-msgid "backup_topic = cinder-backup"
-msgstr "backup_topic = cinder-backup"
-
-#: ./doc/common/tables/cinder-backups.xml47(td)
-msgid "(StrOpt) the topic volume backup nodes listen on"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml50(td)
-#: ./doc/common/tables/nova-api.xml90(td)
-msgid "snapshot_name_template = snapshot-%s"
-msgstr "snapshot_name_template = snapshot-%s"
-
-#: ./doc/common/tables/cinder-backups.xml51(td)
-#: ./doc/common/tables/nova-api.xml91(td)
-msgid "(StrOpt) Template string to be used to generate snapshot names"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml54(td)
-msgid "snapshot_same_host = True"
-msgstr "snapshot_same_host = True"
-
-#: ./doc/common/tables/cinder-backups.xml55(td)
-msgid ""
-"(BoolOpt) Create volume from snapshot at the host where snapshot resides"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-pipeline-main.xml7(literal)
-#: ./doc/common/tables/swift-object-server-pipeline-main.xml7(literal)
-#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml7(literal)
-#: ./doc/common/tables/swift-account-server-pipeline-main.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml7(literal)
-msgid "[pipeline:main]"
-msgstr "[pipeline:main]"
-
-#: ./doc/common/tables/swift-container-server-pipeline-main.xml18(td)
-msgid "pipeline = healthcheck recon container-server"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ofa.xml8(caption)
-msgid "Description of configuration options for ml2_ofa"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ofa.xml22(td)
-msgid "ofp_listen_host ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ofa.xml23(td)
-msgid "(StrOpt) openflow listen host"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ofa.xml26(td)
-msgid "ofp_ssl_listen_port = 6633"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ofa.xml27(td)
-msgid "(IntOpt) openflow ssl listen port"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ofa.xml30(td)
-msgid "ofp_tcp_listen_port = 6633"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ofa.xml31(td)
-msgid "(IntOpt) openflow tcp listen port"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ofa.xml37(td)
-msgid "get_datapath_retry_times = 60"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ofa.xml38(td)
-msgid "(IntOpt) Number of seconds to retry acquiring an Open vSwitch datapath"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml27(td)
-#: ./doc/common/tables/neutron-wsgi.xml23(td)
-msgid "(IntOpt) Number of backlog requests to configure the socket with"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml39(td)
-#: ./doc/common/tables/heat-debug.xml35(td)
-#: ./doc/common/tables/neutron-logging.xml31(td)
-#: ./doc/common/tables/nova-logging.xml31(td)
-msgid "(BoolOpt) make deprecations fatal"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml42(td)
-msgid "pydev_debug = disabled"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml43(td)
-msgid ""
-"(StrOpt) Enable or disable pydev remote debugging. If value is 'auto' tries "
-"to connect to remote debugger server, but in case of error continues running"
-" with debugging disabled."
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml47(td)
-msgid "(StrOpt) Pydev debug server host (localhost by default)."
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml51(td)
-msgid "(IntOpt) Pydev debug server port (5678 by default)."
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml54(td)
-msgid "remote_cinder_client = trove.common.remote.cinder_client"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml58(td)
-msgid "remote_dns_client = trove.common.remote.dns_client"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml62(td)
-msgid "remote_guest_client = trove.common.remote.guest_client"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml66(td)
-msgid "remote_heat_client = trove.common.remote.heat_client"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml70(td)
-msgid "remote_nova_client = trove.common.remote.nova_client"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml74(td)
-msgid "remote_swift_client = trove.common.remote.swift_client"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml78(td)
-#: ./doc/common/tables/glance-logging.xml98(td)
-#: ./doc/common/tables/ceilometer-logging.xml98(td)
-#: ./doc/common/tables/neutron-logging.xml98(td)
-#: ./doc/common/tables/heat-logging.xml82(td)
-#: ./doc/common/tables/keystone-logging.xml86(td)
-#: ./doc/common/tables/nova-logging.xml102(td)
-#: ./doc/common/tables/cinder-common.xml222(td)
-msgid "verbose = False"
-msgstr "verbose = False"
-
-#: ./doc/common/tables/trove-debug.xml79(td)
-#: ./doc/common/tables/glance-logging.xml99(td)
-#: ./doc/common/tables/ceilometer-logging.xml99(td)
-#: ./doc/common/tables/neutron-logging.xml99(td)
-#: ./doc/common/tables/heat-logging.xml83(td)
-#: ./doc/common/tables/keystone-logging.xml87(td)
-#: ./doc/common/tables/nova-logging.xml103(td)
-#: ./doc/common/tables/cinder-common.xml223(td)
-msgid ""
-"(BoolOpt) Print more verbose output (set logging level to INFO instead of "
-"default WARNING level)."
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-object.xml7(literal)
-msgid "[object]"
-msgstr "[object]"
-
-#: ./doc/common/tables/swift-rsyncd-object.xml7(literal)
-#: ./doc/common/tables/swift-rsyncd-account.xml7(literal)
-#: ./doc/common/tables/swift-rsyncd-container.xml7(literal)
-msgid "rsyncd.conf-sample"
-msgstr "rsyncd.conf-sample"
-
-#: ./doc/common/tables/swift-rsyncd-object.xml18(td)
-msgid "max connections = 8"
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-object.xml21(td)
-#: ./doc/common/tables/swift-rsyncd-account.xml21(td)
-#: ./doc/common/tables/swift-rsyncd-container.xml21(td)
-msgid "path = /srv/node"
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-object.xml24(td)
-#: ./doc/common/tables/swift-rsyncd-account.xml24(td)
-#: ./doc/common/tables/swift-rsyncd-container.xml24(td)
-msgid "read only = false"
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-object.xml27(td)
-msgid "lock file = /var/lock/object.lock"
-msgstr "lock file = /var/lock/object.lock"
-
-#: ./doc/common/tables/nova-s3.xml22(td)
-msgid "buckets_path = $state_path/buckets"
-msgstr "buckets_path = $state_path/buckets"
-
-#: ./doc/common/tables/nova-s3.xml23(td)
-msgid "(StrOpt) Path to S3 buckets"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml26(td)
-msgid "image_decryption_dir = /tmp"
-msgstr "image_decryption_dir = /tmp"
-
-#: ./doc/common/tables/nova-s3.xml27(td)
-msgid "(StrOpt) Parent directory for tempdir used for image decryption"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml30(td)
-msgid "s3_access_key = notchecked"
-msgstr "s3_access_key = notchecked"
-
-#: ./doc/common/tables/nova-s3.xml31(td)
-msgid "(StrOpt) Access key to use for S3 server for images"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml34(td)
-msgid "s3_affix_tenant = False"
-msgstr "s3_affix_tenant = False"
-
-#: ./doc/common/tables/nova-s3.xml35(td)
-msgid ""
-"(BoolOpt) Whether to affix the tenant id to the access key when downloading "
-"from S3"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml38(td)
-msgid "s3_host = $my_ip"
-msgstr "s3_host = $my_ip"
-
-#: ./doc/common/tables/nova-s3.xml39(td)
-msgid "(StrOpt) Hostname or IP for OpenStack to use when accessing the S3 api"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml42(td)
-msgid "s3_listen = 0.0.0.0"
-msgstr "s3_listen = 0.0.0.0"
-
-#: ./doc/common/tables/nova-s3.xml43(td)
-msgid "(StrOpt) IP address for S3 API to listen"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml46(td)
-msgid "s3_listen_port = 3333"
-msgstr "s3_listen_port = 3333"
-
-#: ./doc/common/tables/nova-s3.xml47(td)
-msgid "(IntOpt) Port for S3 API to listen"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml50(td)
-msgid "s3_port = 3333"
-msgstr "s3_port = 3333"
-
-#: ./doc/common/tables/nova-s3.xml51(td)
-msgid "(IntOpt) Port used when accessing the S3 api"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml54(td)
-msgid "s3_secret_key = notchecked"
-msgstr "s3_secret_key = notchecked"
-
-#: ./doc/common/tables/nova-s3.xml55(td)
-msgid "(StrOpt) Secret key to use for S3 server for images"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml58(td)
-msgid "s3_use_ssl = False"
-msgstr "s3_use_ssl = False"
-
-#: ./doc/common/tables/nova-s3.xml59(td)
-msgid "(BoolOpt) Whether to use SSL when talking to S3"
-msgstr ""
-
-#: ./doc/common/tables/nova-zookeeper.xml8(caption)
-msgid "Description of configuration options for zookeeper"
-msgstr "Description des options de configuration pour zookeeper"
-
-#: ./doc/common/tables/nova-zookeeper.xml19(th)
-msgid "[zookeeper]"
-msgstr ""
-
-#: ./doc/common/tables/nova-zookeeper.xml22(td)
-msgid "address = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-zookeeper.xml23(td)
-msgid ""
-"(StrOpt) The ZooKeeper addresses for servicegroup service in the format of "
-"host1:port,host2:port,host3:port"
-msgstr ""
-
-#: ./doc/common/tables/nova-zookeeper.xml26(td)
-msgid "recv_timeout = 4000"
-msgstr "recv_timeout = 4000"
-
-#: ./doc/common/tables/nova-zookeeper.xml27(td)
-msgid "(IntOpt) The recv_timeout parameter for the zk session"
-msgstr ""
-
-#: ./doc/common/tables/nova-zookeeper.xml30(td)
-msgid "sg_prefix = /servicegroups"
-msgstr "sg_prefix = /servicegroups"
-
-#: ./doc/common/tables/nova-zookeeper.xml31(td)
-msgid "(StrOpt) The prefix used in ZooKeeper to store ephemeral nodes"
-msgstr ""
-
-#: ./doc/common/tables/nova-zookeeper.xml34(td)
-msgid "sg_retry_interval = 5"
-msgstr "sg_retry_interval = 5"
-
-#: ./doc/common/tables/nova-zookeeper.xml35(td)
-msgid "(IntOpt) Number of seconds to wait until retrying to join the session"
-msgstr ""
-
-#: ./doc/common/tables/cinder-rpc.xml38(td)
-msgid "default_timeout = 20"
-msgstr ""
-
-#: ./doc/common/tables/cinder-rpc.xml39(td)
-msgid "(IntOpt) Default Time Out For CLI operations in minutes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-rpc.xml83(td)
-#: ./doc/common/tables/glance-redis.xml27(td)
-#: ./doc/common/tables/keystone-redis.xml35(td)
-#: ./doc/common/tables/nova-redis.xml23(td)
-msgid "(StrOpt) Password for Redis server (optional)."
-msgstr ""
-
-#: ./doc/common/tables/cinder-rpc.xml234(td)
-msgid "volume_topic = cinder-volume"
-msgstr "volume_topic = cinder-volume"
-
-#: ./doc/common/tables/cinder-rpc.xml235(td)
-msgid "(StrOpt) the topic volume nodes listen on"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml23(td)
-msgid "(StrOpt) File name for the paste.deploy config for cinder-api"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml26(td)
-msgid "api_rate_limit = True"
-msgstr "api_rate_limit = True"
-
-#: ./doc/common/tables/cinder-api.xml27(td)
-msgid "(BoolOpt) whether to rate limit the api"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml34(td)
-#: ./doc/common/tables/ceilometer-api.xml22(td)
-#: ./doc/common/tables/glance-api.xml38(td)
-msgid "enable_v1_api = True"
-msgstr "enable_v1_api = True"
-
-#: ./doc/common/tables/cinder-api.xml35(td)
-msgid "(BoolOpt) Deploy v1 of the Cinder API."
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml38(td)
-#: ./doc/common/tables/glance-api.xml46(td)
-msgid "enable_v2_api = True"
-msgstr "enable_v2_api = True"
-
-#: ./doc/common/tables/cinder-api.xml39(td)
-msgid "(BoolOpt) Deploy v2 of the Cinder API."
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml42(td)
-msgid "extra_capabilities = {}"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml43(td)
-msgid ""
-"(StrOpt) User defined capabilities, a JSON formatted string specifying "
-"key/value pairs."
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml50(td)
-#: ./doc/common/tables/nova-policy.xml46(td)
-msgid "osapi_max_limit = 1000"
-msgstr "osapi_max_limit = 1000"
-
-#: ./doc/common/tables/cinder-api.xml51(td)
-msgid ""
-"(IntOpt) the maximum number of items returned in a single response from a "
-"collection resource"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml54(td)
-#: ./doc/common/tables/nova-policy.xml50(td)
-msgid "osapi_max_request_body_size = 114688"
-msgstr "osapi_max_request_body_size = 114688"
-
-#: ./doc/common/tables/cinder-api.xml55(td)
-msgid "(IntOpt) Max size for body of a request"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml58(td)
-msgid "osapi_volume_base_URL = None"
-msgstr "osapi_volume_base_URL = None"
-
-#: ./doc/common/tables/cinder-api.xml59(td)
-msgid ""
-"(StrOpt) Base URL that will be presented to users in links to the OpenStack "
-"Volume API"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml62(td)
-msgid "osapi_volume_ext_list ="
-msgstr "osapi_volume_ext_list ="
-
-#: ./doc/common/tables/cinder-api.xml63(td)
-msgid ""
-"(ListOpt) Specify list of extensions to load when using "
-"osapi_volume_extension option with cinder.api.contrib.select_extensions"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml66(td)
-msgid "osapi_volume_extension = ['cinder.api.contrib.standard_extensions']"
-msgstr "osapi_volume_extension = ['cinder.api.contrib.standard_extensions']"
-
-#: ./doc/common/tables/cinder-api.xml67(td)
-msgid "(MultiStrOpt) osapi volume extension to load"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml70(td)
-msgid "osapi_volume_listen = 0.0.0.0"
-msgstr "osapi_volume_listen = 0.0.0.0"
-
-#: ./doc/common/tables/cinder-api.xml71(td)
-msgid "(StrOpt) IP address for OpenStack Volume API to listen"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml74(td)
-msgid "osapi_volume_listen_port = 8776"
-msgstr "osapi_volume_listen_port = 8776"
-
-#: ./doc/common/tables/cinder-api.xml75(td)
-msgid "(IntOpt) port for os volume api to listen"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml78(td)
-msgid "osapi_volume_workers = None"
-msgstr "osapi_volume_workers = None"
-
-#: ./doc/common/tables/cinder-api.xml79(td)
-msgid "(IntOpt) Number of workers for OpenStack Volume API service"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml82(td)
-msgid "transfer_api_class = cinder.transfer.api.API"
-msgstr "transfer_api_class = cinder.transfer.api.API"
-
-#: ./doc/common/tables/cinder-api.xml83(td)
-msgid "(StrOpt) The full class name of the volume transfer API class"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml86(td)
-msgid "volume_api_class = cinder.volume.api.API"
-msgstr "volume_api_class = cinder.volume.api.API"
-
-#: ./doc/common/tables/cinder-api.xml90(td)
-msgid "volume_name_template = volume-%s"
-msgstr "volume_name_template = volume-%s"
-
-#: ./doc/common/tables/cinder-api.xml91(td)
-msgid "(StrOpt) Template string to be used to generate volume names"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml94(td)
-msgid "volume_transfer_key_length = 16"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml95(td)
-msgid "(IntOpt) The number of characters in the autogenerated auth key."
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml98(td)
-msgid "volume_transfer_salt_length = 8"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml99(td)
-msgid "(IntOpt) The number of characters in the salt."
-msgstr ""
-
-#: ./doc/common/tables/cinder-windows.xml8(caption)
-msgid "Description of configuration options for windows"
-msgstr ""
-
-#: ./doc/common/tables/cinder-windows.xml22(td)
-msgid "windows_iscsi_lun_path = C:\\iSCSIVirtualDisks"
-msgstr "windows_iscsi_lun_path = C:\\iSCSIVirtualDisks"
-
-#: ./doc/common/tables/cinder-windows.xml23(td)
-msgid "(StrOpt) Path to store VHD backed volumes"
-msgstr ""
-
-#: ./doc/common/tables/glance-vmware.xml8(caption)
-#: ./doc/common/tables/ceilometer-vmware.xml8(caption)
-#: ./doc/common/tables/cinder-vmware.xml8(caption)
-#: ./doc/common/tables/nova-vmware.xml8(caption)
-#: ./doc/common/tables/neutron-vmware.xml8(caption)
-msgid "Description of configuration options for vmware"
-msgstr ""
-
 #: ./doc/common/tables/glance-vmware.xml22(td)
 msgid "vmware_api_insecure = False"
 msgstr ""
@@ -36146,720 +37140,12 @@ msgid ""
 " server."
 msgstr ""
 
-#: ./doc/common/tables/swift-object-server-pipeline-main.xml18(td)
-msgid "pipeline = healthcheck recon object-server"
-msgstr "pipeline = healthcheck recon object-server"
+#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml7(literal)
+msgid "[filter:container-quotas]"
+msgstr "[filter:container-quotas]"
 
-#: ./doc/common/tables/trove-backup.xml8(caption)
-msgid "Description of configuration options for backup"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml22(td)
-msgid "backup_aes_cbc_key = default_aes_cbc_key"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml23(td)
-msgid "(StrOpt) Default OpenSSL aes_cbc key."
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml26(td)
-msgid "backup_chunk_size = 65536"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml27(td)
-msgid ""
-"(IntOpt) Chunk size to stream to swift container. This should be in "
-"multiples of 128 bytes, since this is the size of an md5 digest block "
-"allowing the process to update the file checksum during streaming. See: "
-"http://stackoverflow.com/questions/1131220/"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml30(td)
-msgid ""
-"backup_incremental_strategy = {'InnoBackupEx': 'InnoBackupExIncremental'}"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml31(td)
-msgid ""
-"(DictOpt) Incremental Backup Runner Based off of the default strategy. For "
-"strategies that do not implement an incremental the runner will use the "
-"default full backup."
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml34(td)
-msgid "backup_namespace = trove.guestagent.strategies.backup.mysql_impl"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml35(td)
-msgid "(StrOpt) Namespace to load backup strategies from."
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml38(td)
-msgid "backup_runner = trove.guestagent.backup.backup_types.InnoBackupEx"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml42(td)
-msgid "backup_runner_options = {}"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml43(td)
-msgid "(DictOpt) Additional options to be passed to the backup runner."
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml46(td)
-msgid "backup_segment_max_size = 2147483648"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml47(td)
-msgid "(IntOpt) Maximum size of each segment of the backup file."
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml50(td)
-#: ./doc/common/tables/trove-db_mysql.xml22(td)
-#: ./doc/common/tables/trove-db_percona.xml22(td)
-msgid "backup_strategy = InnoBackupEx"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml54(td)
-msgid "backup_swift_container = database_backups"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml58(td)
-msgid "backup_use_gzip_compression = True"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml59(td)
-msgid "(BoolOpt) Compress backups using gzip."
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml62(td)
-msgid "backup_use_openssl_encryption = True"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml63(td)
-msgid "(BoolOpt) Encrypt backups using OpenSSL."
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml66(td)
-msgid "backup_use_snet = False"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml67(td)
-msgid "(BoolOpt) Send backup files over snet."
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml70(td)
-msgid "backups_page_size = 20"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml8(caption)
-msgid "Description of configuration options for san"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml22(td)
-msgid "san_clustername ="
-msgstr "san_clustername ="
-
-#: ./doc/common/tables/cinder-san.xml23(td)
-msgid "(StrOpt) Cluster name to use for creating volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml26(td)
-msgid "san_ip ="
-msgstr "san_ip ="
-
-#: ./doc/common/tables/cinder-san.xml27(td)
-msgid "(StrOpt) IP address of SAN controller"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml30(td)
-msgid "san_is_local = False"
-msgstr "san_is_local = False"
-
-#: ./doc/common/tables/cinder-san.xml31(td)
-msgid ""
-"(BoolOpt) Execute commands locally instead of over SSH; use if the volume "
-"service is running on the SAN device"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml34(td)
-msgid "san_login = admin"
-msgstr "san_login = admin"
-
-#: ./doc/common/tables/cinder-san.xml35(td)
-msgid "(StrOpt) Username for SAN controller"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml38(td)
-msgid "san_password ="
-msgstr "san_password ="
-
-#: ./doc/common/tables/cinder-san.xml39(td)
-msgid "(StrOpt) Password for SAN controller"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml42(td)
-msgid "san_private_key ="
-msgstr "san_private_key ="
-
-#: ./doc/common/tables/cinder-san.xml43(td)
-msgid "(StrOpt) Filename of private key to use for SSH authentication"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml46(td)
-msgid "san_ssh_port = 22"
-msgstr "san_ssh_port = 22"
-
-#: ./doc/common/tables/cinder-san.xml47(td)
-msgid "(IntOpt) SSH port to use with SAN"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml50(td)
-msgid "san_thin_provision = True"
-msgstr "san_thin_provision = True"
-
-#: ./doc/common/tables/cinder-san.xml51(td)
-msgid "(BoolOpt) Use thin provisioning for SAN volumes?"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml54(td)
-msgid "ssh_conn_timeout = 30"
-msgstr "ssh_conn_timeout = 30"
-
-#: ./doc/common/tables/cinder-san.xml55(td)
-msgid "(IntOpt) SSH connection timeout in seconds"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml58(td)
-msgid "ssh_max_pool_conn = 5"
-msgstr "ssh_max_pool_conn = 5"
-
-#: ./doc/common/tables/cinder-san.xml59(td)
-msgid "(IntOpt) Maximum ssh connections in the pool"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml62(td)
-msgid "ssh_min_pool_conn = 1"
-msgstr "ssh_min_pool_conn = 1"
-
-#: ./doc/common/tables/cinder-san.xml63(td)
-msgid "(IntOpt) Minimum ssh connections in the pool"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-app-account-server.xml7(literal)
-msgid "[app:account-server]"
-msgstr "[app:account-server]"
-
-#: ./doc/common/tables/swift-account-server-app-account-server.xml18(td)
-msgid "use = egg:swift#account"
-msgstr "use = egg:swift#account"
-
-#: ./doc/common/tables/swift-account-server-app-account-server.xml21(td)
-msgid "set log_name = account-server"
-msgstr "set log_name = account-server"
-
-#: ./doc/common/tables/swift-account-server-app-account-server.xml30(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml30(td)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml30(td)
-msgid "set log_requests = true"
-msgstr "set log_requests = true"
-
-#: ./doc/common/tables/swift-account-server-app-account-server.xml30(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml30(td)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml30(td)
-msgid "Whether or not to log requests"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-app-account-server.xml39(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml48(td)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml60(td)
-msgid "replication_server = false"
-msgstr "replication_server = false"
-
-#: ./doc/common/tables/swift-account-server-app-account-server.xml39(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml48(td)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml60(td)
-msgid ""
-"If defined, tells server how to handle replication verbs in requests. When "
-"set to True (or 1), only replication verbs will be accepted. When set to "
-"False, replication verbs will be rejected. When undefined, server will "
-"accept any verb in the request."
-msgstr ""
-
-#: ./doc/common/tables/cinder-keymgr.xml22(td)
-msgid "api_class = cinder.keymgr.conf_key_mgr.ConfKeyManager"
-msgstr "api_class = cinder.keymgr.conf_key_mgr.ConfKeyManager"
-
-#: ./doc/common/tables/nova-db.xml8(caption)
-#: ./doc/common/tables/neutron-db.xml8(caption)
-#: ./doc/common/tables/glance-db.xml8(caption)
-msgid "Description of configuration options for db"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml22(td)
-msgid "db_driver = nova.db"
-msgstr "db_driver = nova.db"
-
-#: ./doc/common/tables/nova-db.xml23(td)
-msgid "(StrOpt) The driver to use for database access"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml29(td)
-msgid "db_check_interval = 60"
-msgstr "db_check_interval = 60"
-
-#: ./doc/common/tables/nova-db.xml30(td)
-msgid ""
-"(IntOpt) Interval, in seconds, for getting fresh cell information from the "
-"database."
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml36(td)
-#: ./doc/common/tables/heat-database.xml37(td)
-#: ./doc/common/tables/ceilometer-database.xml41(td)
-#: ./doc/common/tables/cinder-storage.xml137(td)
-#: ./doc/common/tables/neutron-db.xml33(td)
-#: ./doc/common/tables/keystone-database.xml22(td)
-#: ./doc/common/tables/glance-db.xml22(td)
-msgid "backend = sqlalchemy"
-msgstr "backend = sqlalchemy"
-
-#: ./doc/common/tables/nova-db.xml37(td)
-#: ./doc/common/tables/heat-database.xml38(td)
-#: ./doc/common/tables/ceilometer-database.xml42(td)
-#: ./doc/common/tables/cinder-storage.xml138(td)
-#: ./doc/common/tables/cinder-database.xml23(td)
-#: ./doc/common/tables/neutron-db.xml34(td)
-#: ./doc/common/tables/keystone-database.xml23(td)
-#: ./doc/common/tables/glance-db.xml23(td)
-msgid "(StrOpt) The backend to use for db"
-msgstr "StrOpt)  Le backend à utiliser pour la base de données"
-
-#: ./doc/common/tables/nova-db.xml40(td)
-#: ./doc/common/tables/keystone-database.xml26(td)
-#: ./doc/common/tables/glance-db.xml26(td)
-msgid "connection = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml41(td)
-#: ./doc/common/tables/heat-database.xml42(td)
-#: ./doc/common/tables/ceilometer-database.xml46(td)
-#: ./doc/common/tables/cinder-connection.xml23(td)
-#: ./doc/common/tables/neutron-db.xml38(td)
-#: ./doc/common/tables/keystone-database.xml27(td)
-#: ./doc/common/tables/glance-db.xml27(td)
-msgid ""
-"(StrOpt) The SQLAlchemy connection string used to connect to the database"
-msgstr "(StrOpt)  La chaîne de connexion SQLAlchemy utilisée pour se connecter à la base de données bare-metal"
-
-#: ./doc/common/tables/nova-db.xml44(td)
-#: ./doc/common/tables/heat-database.xml45(td)
-#: ./doc/common/tables/ceilometer-database.xml49(td)
-#: ./doc/common/tables/cinder-connection.xml26(td)
-#: ./doc/common/tables/neutron-db.xml41(td)
-#: ./doc/common/tables/keystone-database.xml30(td)
-#: ./doc/common/tables/glance-db.xml30(td)
-msgid "connection_debug = 0"
-msgstr "connection_debug = 0"
-
-#: ./doc/common/tables/nova-db.xml45(td)
-#: ./doc/common/tables/heat-database.xml46(td)
-#: ./doc/common/tables/ceilometer-database.xml50(td)
-#: ./doc/common/tables/cinder-connection.xml27(td)
-#: ./doc/common/tables/neutron-db.xml42(td)
-#: ./doc/common/tables/keystone-database.xml31(td)
-#: ./doc/common/tables/glance-db.xml31(td)
-msgid ""
-"(IntOpt) Verbosity of SQL debugging information. 0=None, 100=Everything"
-msgstr "(IntOpt) Verbosité de l’information de débogage SQL.0=Aucune, 100=Tout"
-
-#: ./doc/common/tables/nova-db.xml48(td)
-#: ./doc/common/tables/heat-database.xml49(td)
-#: ./doc/common/tables/ceilometer-database.xml53(td)
-#: ./doc/common/tables/cinder-connection.xml30(td)
-#: ./doc/common/tables/neutron-db.xml45(td)
-#: ./doc/common/tables/keystone-database.xml34(td)
-#: ./doc/common/tables/glance-db.xml34(td)
-msgid "connection_trace = False"
-msgstr "connection_trace = False"
-
-#: ./doc/common/tables/nova-db.xml49(td)
-#: ./doc/common/tables/heat-database.xml50(td)
-#: ./doc/common/tables/ceilometer-database.xml54(td)
-#: ./doc/common/tables/cinder-connection.xml31(td)
-#: ./doc/common/tables/neutron-db.xml46(td)
-#: ./doc/common/tables/keystone-database.xml35(td)
-#: ./doc/common/tables/glance-db.xml35(td)
-msgid "(BoolOpt) Add python stack traces to SQL as comment strings"
-msgstr "(BoolOpt) Ajouter des traces de pile Python à SQL en tant que chaînes de commentaires"
-
-#: ./doc/common/tables/nova-db.xml52(td)
-#: ./doc/common/tables/neutron-db.xml49(td)
-#: ./doc/common/tables/keystone-database.xml38(td)
-#: ./doc/common/tables/glance-db.xml38(td)
-msgid "db_inc_retry_interval = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml53(td)
-#: ./doc/common/tables/neutron-db.xml50(td)
-#: ./doc/common/tables/keystone-database.xml39(td)
-#: ./doc/common/tables/glance-db.xml39(td)
-msgid ""
-"(BoolOpt) Whether to increase interval between db connection retries, up to "
-"db_max_retry_interval"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml56(td)
-#: ./doc/common/tables/neutron-db.xml53(td)
-#: ./doc/common/tables/keystone-database.xml42(td)
-#: ./doc/common/tables/glance-db.xml42(td)
-msgid "db_max_retries = 20"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml57(td)
-#: ./doc/common/tables/neutron-db.xml54(td)
-#: ./doc/common/tables/keystone-database.xml43(td)
-#: ./doc/common/tables/glance-db.xml43(td)
-msgid ""
-"(IntOpt) maximum db connection retries before error is raised. (setting -1 "
-"implies an infinite retry count)"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml60(td)
-#: ./doc/common/tables/neutron-db.xml57(td)
-#: ./doc/common/tables/keystone-database.xml46(td)
-#: ./doc/common/tables/glance-db.xml46(td)
-msgid "db_max_retry_interval = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml61(td)
-#: ./doc/common/tables/neutron-db.xml58(td)
-#: ./doc/common/tables/keystone-database.xml47(td)
-#: ./doc/common/tables/glance-db.xml47(td)
-msgid ""
-"(IntOpt) max seconds between db connection retries, if db_inc_retry_interval"
-" is enabled"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml64(td)
-#: ./doc/common/tables/neutron-db.xml61(td)
-#: ./doc/common/tables/keystone-database.xml50(td)
-#: ./doc/common/tables/glance-db.xml50(td)
-msgid "db_retry_interval = 1"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml65(td)
-#: ./doc/common/tables/neutron-db.xml62(td)
-#: ./doc/common/tables/keystone-database.xml51(td)
-#: ./doc/common/tables/glance-db.xml51(td)
-msgid "(IntOpt) seconds between db connection retries"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml68(td)
-#: ./doc/common/tables/heat-database.xml53(td)
-#: ./doc/common/tables/ceilometer-database.xml57(td)
-#: ./doc/common/tables/cinder-common.xml229(td)
-#: ./doc/common/tables/neutron-db.xml65(td)
-#: ./doc/common/tables/keystone-database.xml54(td)
-#: ./doc/common/tables/glance-db.xml54(td)
-msgid "idle_timeout = 3600"
-msgstr "idle_timeout = 3600"
-
-#: ./doc/common/tables/nova-db.xml69(td)
-#: ./doc/common/tables/ceilometer-database.xml58(td)
-#: ./doc/common/tables/neutron-db.xml66(td)
-#: ./doc/common/tables/keystone-database.xml55(td)
-#: ./doc/common/tables/glance-db.xml55(td)
-msgid "(IntOpt) Timeout before idle sql connections are reaped"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml72(td)
-#: ./doc/common/tables/heat-database.xml57(td)
-#: ./doc/common/tables/ceilometer-database.xml61(td)
-#: ./doc/common/tables/cinder-storage.xml141(td)
-#: ./doc/common/tables/keystone-database.xml58(td)
-#: ./doc/common/tables/glance-db.xml58(td)
-msgid "max_overflow = None"
-msgstr "max_overflow = None"
-
-#: ./doc/common/tables/nova-db.xml73(td)
-#: ./doc/common/tables/heat-database.xml58(td)
-#: ./doc/common/tables/ceilometer-database.xml62(td)
-#: ./doc/common/tables/cinder-storage.xml142(td)
-#: ./doc/common/tables/neutron-db.xml70(td)
-#: ./doc/common/tables/keystone-database.xml59(td)
-#: ./doc/common/tables/glance-db.xml59(td)
-msgid "(IntOpt) If set, use this value for max_overflow with sqlalchemy"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml76(td)
-#: ./doc/common/tables/heat-database.xml61(td)
-#: ./doc/common/tables/ceilometer-database.xml65(td)
-#: ./doc/common/tables/keystone-database.xml62(td)
-#: ./doc/common/tables/glance-db.xml62(td)
-msgid "max_pool_size = None"
-msgstr "max_pool_size = None"
-
-#: ./doc/common/tables/nova-db.xml77(td)
-#: ./doc/common/tables/heat-database.xml62(td)
-#: ./doc/common/tables/ceilometer-database.xml66(td)
-#: ./doc/common/tables/cinder-storage.xml146(td)
-#: ./doc/common/tables/neutron-db.xml74(td)
-#: ./doc/common/tables/keystone-database.xml63(td)
-#: ./doc/common/tables/glance-db.xml63(td)
-msgid "(IntOpt) Maximum number of SQL connections to keep open in a pool"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml80(td)
-#: ./doc/common/tables/heat-database.xml65(td)
-#: ./doc/common/tables/ceilometer-database.xml69(td)
-#: ./doc/common/tables/cinder-storage.xml149(td)
-#: ./doc/common/tables/neutron-db.xml77(td)
-#: ./doc/common/tables/keystone-database.xml66(td)
-#: ./doc/common/tables/glance-db.xml66(td)
-msgid "max_retries = 10"
-msgstr "max_retries = 10"
-
-#: ./doc/common/tables/nova-db.xml81(td)
-#: ./doc/common/tables/ceilometer-database.xml70(td)
-#: ./doc/common/tables/neutron-db.xml78(td)
-#: ./doc/common/tables/keystone-database.xml67(td)
-#: ./doc/common/tables/glance-db.xml67(td)
-msgid ""
-"(IntOpt) Maximum db connection retries during startup. (setting -1 implies "
-"an infinite retry count)"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml84(td)
-#: ./doc/common/tables/heat-database.xml69(td)
-#: ./doc/common/tables/ceilometer-database.xml73(td)
-#: ./doc/common/tables/cinder-storage.xml153(td)
-#: ./doc/common/tables/neutron-db.xml81(td)
-#: ./doc/common/tables/keystone-database.xml70(td)
-#: ./doc/common/tables/glance-db.xml70(td)
-msgid "min_pool_size = 1"
-msgstr "min_pool_size = 1"
-
-#: ./doc/common/tables/nova-db.xml85(td)
-#: ./doc/common/tables/heat-database.xml70(td)
-#: ./doc/common/tables/ceilometer-database.xml74(td)
-#: ./doc/common/tables/cinder-storage.xml154(td)
-#: ./doc/common/tables/neutron-db.xml82(td)
-#: ./doc/common/tables/keystone-database.xml71(td)
-#: ./doc/common/tables/glance-db.xml71(td)
-msgid "(IntOpt) Minimum number of SQL connections to keep open in a pool"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml88(td)
-msgid "mysql_sql_mode = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml89(td)
-msgid ""
-"(StrOpt) The SQL mode to be used for MySQL sessions (default is empty, "
-"meaning do not override any server-side SQL mode setting)"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml92(td)
-#: ./doc/common/tables/heat-database.xml73(td)
-#: ./doc/common/tables/ceilometer-database.xml77(td)
-#: ./doc/common/tables/keystone-database.xml78(td)
-#: ./doc/common/tables/glance-db.xml78(td)
-msgid "pool_timeout = None"
-msgstr "pool_timeout = None"
-
-#: ./doc/common/tables/nova-db.xml93(td)
-#: ./doc/common/tables/heat-database.xml74(td)
-#: ./doc/common/tables/ceilometer-database.xml78(td)
-#: ./doc/common/tables/neutron-db.xml86(td)
-#: ./doc/common/tables/keystone-database.xml79(td)
-#: ./doc/common/tables/glance-db.xml79(td)
-msgid "(IntOpt) If set, use this value for pool_timeout with sqlalchemy"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml96(td)
-#: ./doc/common/tables/heat-database.xml77(td)
-#: ./doc/common/tables/ceilometer-database.xml81(td)
-#: ./doc/common/tables/cinder-common.xml233(td)
-#: ./doc/common/tables/neutron-db.xml89(td)
-#: ./doc/common/tables/keystone-database.xml82(td)
-#: ./doc/common/tables/glance-db.xml82(td)
-msgid "retry_interval = 10"
-msgstr "retry_interval = 10"
-
-#: ./doc/common/tables/nova-db.xml97(td)
-#: ./doc/common/tables/ceilometer-database.xml82(td)
-#: ./doc/common/tables/neutron-db.xml90(td)
-#: ./doc/common/tables/keystone-database.xml83(td)
-#: ./doc/common/tables/glance-db.xml83(td)
-msgid "(IntOpt) Interval between retries of opening a sql connection"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml100(td)
-msgid "slave_connection = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml101(td)
-#: ./doc/common/tables/heat-database.xml82(td)
-#: ./doc/common/tables/ceilometer-database.xml86(td)
-#: ./doc/common/tables/neutron-db.xml94(td)
-msgid ""
-"(StrOpt) The SQLAlchemy connection string used to connect to the slave "
-"database"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml104(td)
-msgid "sqlite_db = nova.sqlite"
-msgstr "sqlite_db = nova.sqlite"
-
-#: ./doc/common/tables/nova-db.xml105(td)
-#: ./doc/common/tables/ceilometer-database.xml31(td)
-#: ./doc/common/tables/neutron-db.xml23(td)
-#: ./doc/common/tables/keystone-database.xml87(td)
-#: ./doc/common/tables/glance-db.xml87(td)
-msgid "(StrOpt) The file name to use with SQLite"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml108(td)
-#: ./doc/common/tables/heat-database.xml30(td)
-#: ./doc/common/tables/ceilometer-database.xml34(td)
-#: ./doc/common/tables/cinder-common.xml170(td)
-#: ./doc/common/tables/neutron-db.xml26(td)
-#: ./doc/common/tables/keystone-database.xml90(td)
-#: ./doc/common/tables/glance-db.xml90(td)
-msgid "sqlite_synchronous = True"
-msgstr "sqlite_synchronous = True"
-
-#: ./doc/common/tables/nova-db.xml109(td)
-#: ./doc/common/tables/ceilometer-database.xml35(td)
-#: ./doc/common/tables/neutron-db.xml27(td)
-#: ./doc/common/tables/keystone-database.xml91(td)
-#: ./doc/common/tables/glance-db.xml91(td)
-msgid "(BoolOpt) If True, SQLite uses synchronous mode"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml112(td)
-#: ./doc/common/tables/neutron-db.xml97(td)
-#: ./doc/common/tables/keystone-database.xml94(td)
-#: ./doc/common/tables/glance-db.xml94(td)
-msgid "use_db_reconnect = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml113(td)
-#: ./doc/common/tables/neutron-db.xml98(td)
-#: ./doc/common/tables/keystone-database.xml95(td)
-#: ./doc/common/tables/glance-db.xml95(td)
-msgid ""
-"(BoolOpt) Enable the experimental use of database reconnect on connection "
-"lost"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_vxlan.xml8(caption)
-msgid "Description of configuration options for ml2_vxlan"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_vxlan.xml19(th)
-msgid "[ml2_type_vxlan]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_vxlan.xml22(td)
-msgid "vni_ranges ="
-msgstr "vni_ranges ="
-
-#: ./doc/common/tables/neutron-ml2_vxlan.xml23(td)
-msgid ""
-"(ListOpt) Comma-separated list of &lt;vni_min&gt;:&lt;vni_max&gt; tuples "
-"enumerating ranges of VXLAN VNI IDs that are available for tenant network "
-"allocation"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_vxlan.xml26(td)
-msgid "vxlan_group = None"
-msgstr "vxlan_group = None"
-
-#: ./doc/common/tables/neutron-ml2_vxlan.xml27(td)
-msgid ""
-"(StrOpt) Multicast group for VXLAN. If unset, disables VXLAN multicast mode."
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml26(td)
-#: ./doc/common/tables/ceilometer-logging.xml26(td)
-#: ./doc/common/tables/keystone-logging.xml22(td)
-msgid ""
-"default_log_levels = amqp=WARN, amqplib=WARN, boto=WARN, qpid=WARN, "
-"sqlalchemy=WARN, suds=INFO, iso8601=WARN, "
-"requests.packages.urllib3.connectionpool=WARN"
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml27(td)
-#: ./doc/common/tables/ceilometer-logging.xml27(td)
-#: ./doc/common/tables/keystone-logging.xml23(td)
-#: ./doc/common/tables/cinder-common.xml35(td)
-msgid "(ListOpt) List of logger=LEVEL pairs"
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml63(td)
-#: ./doc/common/tables/ceilometer-logging.xml63(td)
-#: ./doc/common/tables/keystone-logging.xml55(td)
-#: ./doc/common/tables/cinder-common.xml95(td)
-msgid "(StrOpt) Format string to use for log messages with context"
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml67(td)
-#: ./doc/common/tables/ceilometer-logging.xml67(td)
-#: ./doc/common/tables/keystone-logging.xml59(td)
-#: ./doc/common/tables/cinder-common.xml99(td)
-msgid "(StrOpt) Data to append to log format when level is DEBUG"
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml71(td)
-#: ./doc/common/tables/ceilometer-logging.xml71(td)
-#: ./doc/common/tables/keystone-logging.xml63(td)
-#: ./doc/common/tables/cinder-common.xml103(td)
-msgid "(StrOpt) Format string to use for log messages without context"
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml75(td)
-#: ./doc/common/tables/ceilometer-logging.xml75(td)
-#: ./doc/common/tables/keystone-logging.xml67(td)
-#: ./doc/common/tables/cinder-common.xml107(td)
-msgid "(StrOpt) Prefix each line of exception output with this format"
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml83(td)
-#: ./doc/common/tables/ceilometer-logging.xml83(td)
-#: ./doc/common/tables/keystone-logging.xml71(td)
-#: ./doc/common/tables/cinder-common.xml195(td)
-msgid "(StrOpt) Syslog facility to receive log lines"
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml91(td)
-#: ./doc/common/tables/ceilometer-logging.xml91(td)
-#: ./doc/common/tables/keystone-logging.xml79(td)
-#: ./doc/common/tables/nova-logging.xml95(td)
-#: ./doc/common/tables/cinder-common.xml215(td)
-msgid ""
-"(BoolOpt) Use syslog for logging. Existing syslog format is DEPRECATED "
-"during I, and then will be changed in J to honor RFC5424"
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml94(td)
-#: ./doc/common/tables/ceilometer-logging.xml94(td)
-#: ./doc/common/tables/keystone-logging.xml82(td)
-#: ./doc/common/tables/nova-logging.xml98(td)
-#: ./doc/common/tables/cinder-common.xml218(td)
-msgid "use_syslog_rfc_format = False"
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml95(td)
-#: ./doc/common/tables/ceilometer-logging.xml95(td)
-#: ./doc/common/tables/keystone-logging.xml83(td)
-#: ./doc/common/tables/nova-logging.xml99(td)
-#: ./doc/common/tables/cinder-common.xml219(td)
-msgid ""
-"(BoolOpt) (Optional) Use syslog rfc5424 format for logging. If enabled, will"
-" add APP-NAME (RFC5424) before the MSG part of the syslog message. The old "
-"format without APP-NAME is deprecated in I, and will be removed in J."
+#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml18(td)
+msgid "use = egg:swift#container_quotas"
 msgstr ""
 
 #: ./doc/common/tables/cinder-zoning.xml8(caption)
@@ -36890,644 +37176,758 @@ msgid ""
 "fabric"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning.xml33(td)
-#: ./doc/common/tables/cinder-zoning_fabric.xml50(td)
-msgid "zoning_policy = initiator-target"
-msgstr "zoning_policy = initiator-target"
-
 #: ./doc/common/tables/cinder-zoning.xml34(td)
 msgid "(StrOpt) Zoning policy configured by user"
 msgstr ""
 
-#: ./doc/common/tables/glance-wsgi.xml8(caption)
-#: ./doc/common/tables/neutron-wsgi.xml8(caption)
-#: ./doc/common/tables/nova-wsgi.xml8(caption)
-msgid "Description of configuration options for wsgi"
+#: ./doc/common/tables/heat-notification.xml8(caption)
+#: ./doc/common/tables/keystone-notification.xml8(caption)
+msgid "Description of configuration options for notification"
 msgstr ""
 
-#: ./doc/common/tables/glance-wsgi.xml23(td)
-msgid "(IntOpt) port for eventlet backdoor to listen"
-msgstr ""
+#: ./doc/common/tables/heat-notification.xml22(td)
+#: ./doc/common/tables/keystone-notification.xml22(td)
+msgid "onready = None"
+msgstr "onready = None"
 
-#: ./doc/common/tables/glance-wsgi.xml26(td)
-msgid "eventlet_hub = poll"
-msgstr "eventlet_hub = poll"
-
-#: ./doc/common/tables/glance-wsgi.xml27(td)
+#: ./doc/common/tables/heat-notification.xml23(td)
 msgid ""
-"(StrOpt) Name of eventlet hub to use. Traditionally, we have only supported "
-"'poll', however 'selects' may be appropriate for some platforms. See "
-"http://eventlet.net/doc/hubs.html for more details."
+"(StrOpt) onready allows you to send a notification when the heat processes "
+"are ready to serve. This is either a module with the notify() method or a "
+"shell command. To enable notifications with systemd, one may use the "
+"'systemd-notify --ready' shell command or the 'heat.common.systemd' "
+"notification module."
 msgstr ""
 
-#: ./doc/common/tables/glance-wsgi.xml35(td)
+#: ./doc/common/tables/nova-vpn.xml8(caption)
+#: ./doc/common/tables/neutron-vpn.xml8(caption)
+msgid "Description of configuration options for vpn"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml22(td)
+msgid "boot_script_template = $pybasedir/nova/cloudpipe/bootscript.template"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml23(td)
+msgid "(StrOpt) Template for cloudpipe instance boot script"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml26(td)
+msgid "dmz_cidr ="
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml27(td)
+msgid "(ListOpt) A list of dmz range that should be accepted"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml30(td)
+msgid "dmz_mask = 255.255.255.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml31(td)
+msgid "(StrOpt) Netmask to push into openvpn config"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml34(td)
+msgid "dmz_net = 10.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml35(td)
+msgid "(StrOpt) Network to push into openvpn config"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml38(td)
+msgid "vpn_flavor = m1.tiny"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml39(td)
+msgid "(StrOpt) Flavor for vpn instances"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml42(td)
+msgid "vpn_image_id = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml43(td)
+msgid "(StrOpt) Image ID used when starting up a cloudpipe vpn server"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml46(td)
+msgid "vpn_ip = $my_ip"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml47(td)
+msgid "(StrOpt) Public IP for the cloudpipe VPN servers"
+msgstr "Adresse IP publique des serveurs VPN cloudpipe"
+
+#: ./doc/common/tables/nova-vpn.xml50(td)
+msgid "vpn_key_suffix = -vpn"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml51(td)
+msgid "(StrOpt) Suffix to add to project name for vpn key and secgroups"
+msgstr "(StrOpt)  Suffixe à ajouter au nom du projet pour les clés et secgroups de VPN"
+
+#: ./doc/common/tables/nova-vpn.xml54(td)
+msgid "vpn_start = 1000"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml55(td)
+msgid "(IntOpt) First Vpn port for private networks"
+msgstr "(IntOpt) Premier port VPN des réseaux privés"
+
+#: ./doc/common/tables/neutron-vpn.xml19(th)
+msgid "[ipsec]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vpn.xml22(td)
+msgid "config_base_dir = $state_path/ipsec"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vpn.xml23(td)
+msgid "(StrOpt) Location to store ipsec server config files"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vpn.xml26(td)
+msgid "ipsec_status_check_interval = 60"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vpn.xml27(td)
+msgid "(IntOpt) Interval for checking ipsec status"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vpn.xml30(th)
+msgid "[openswan]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vpn.xml33(td)
 msgid ""
-"(IntOpt) The value for the socket option TCP_KEEPIDLE. This is the time in "
-"seconds that the connection must be idle before TCP starts sending keepalive"
-" probes."
+"ipsec_config_template = /usr/lib/python/site-"
+"packages/neutron/services/vpn/device_drivers/template/openswan/ipsec.conf.template"
 msgstr ""
 
-#: ./doc/common/tables/nova-periodic.xml8(caption)
-msgid "Description of configuration options for periodic"
+#: ./doc/common/tables/neutron-vpn.xml34(td)
+msgid "(StrOpt) Template file for ipsec configuration"
 msgstr ""
 
-#: ./doc/common/tables/nova-periodic.xml22(td)
-msgid "periodic_enable = True"
-msgstr "periodic_enable = True"
-
-#: ./doc/common/tables/nova-periodic.xml23(td)
-msgid "(BoolOpt) Enable periodic tasks"
-msgstr ""
-
-#: ./doc/common/tables/nova-periodic.xml26(td)
-#: ./doc/common/tables/cinder-common.xml130(td)
-msgid "periodic_fuzzy_delay = 60"
-msgstr ""
-
-#: ./doc/common/tables/cinder-images.xml8(caption)
-msgid "Description of configuration options for images"
-msgstr ""
-
-#: ./doc/common/tables/cinder-images.xml23(td)
+#: ./doc/common/tables/neutron-vpn.xml37(td)
 msgid ""
-"(ListOpt) A list of url schemes that can be downloaded directly via the "
-"direct_url. Currently supported schemes: [file]."
+"ipsec_secret_template = /usr/lib/python/site-"
+"packages/neutron/services/vpn/device_drivers/template/openswan/ipsec.secret.template"
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml31(td)
+#: ./doc/common/tables/neutron-vpn.xml38(td)
+msgid "(StrOpt) Template file for ipsec secret configuration"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vpn.xml41(th)
+msgid "[vpnagent]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vpn.xml44(td)
 msgid ""
-"(ListOpt) A list of the glance api servers available to cinder "
-"([hostname|ip]:port)"
+"vpn_device_driver = "
+"['neutron.services.vpn.device_drivers.ipsec.OpenSwanDriver']"
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml34(td)
-msgid "glance_api_ssl_compression = False"
-msgstr "glance_api_ssl_compression = False"
+#: ./doc/common/tables/neutron-vpn.xml45(td)
+msgid "(MultiStrOpt) The vpn device drivers Neutron will use"
+msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml35(td)
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml7(literal)
+msgid "[object-expirer]"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml27(td)
+#: ./doc/common/tables/neutron-common.xml170(td)
+msgid "report_interval = 300"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml30(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml39(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml33(td)
+msgid "concurrency = 1"
+msgstr "concurrency = 1"
+
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml30(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml39(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml33(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml39(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml39(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml33(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml54(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml30(td)
+msgid "Number of replication workers to spawn"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml33(td)
+msgid "processes = 0"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml36(td)
+msgid "process = 0"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml36(td)
 msgid ""
-"(BoolOpt) Whether to attempt to negotiate SSL layer compression when using "
-"SSL (https) requests. Set to False to disable SSL layer compression. In some"
-" cases disabling this may improve data throughput, eg when high network "
-"bandwidth is available and you are using already compressed image formats "
-"such as qcow2 ."
+"(it will actually accept(2) N + 1). Setting this to one (1) will only handle"
+" one request at a time, without accepting another request concurrently."
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml38(td)
-msgid "glance_api_version = 1"
-msgstr "glance_api_version = 1"
+#: ./doc/common/tables/trove-common.xml22(td)
+msgid "configurations_page_size = 20"
+msgstr "configurations_page_size = 20"
 
-#: ./doc/common/tables/cinder-images.xml39(td)
-msgid "(IntOpt) Version of the glance api to use"
+#: ./doc/common/tables/trove-common.xml23(td)
+#: ./doc/common/tables/trove-common.xml27(td)
+#: ./doc/common/tables/trove-common.xml47(td)
+#: ./doc/common/tables/trove-api.xml35(td)
+#: ./doc/common/tables/trove-api.xml47(td)
+#: ./doc/common/tables/trove-api.xml51(td)
+#: ./doc/common/tables/trove-api.xml55(td)
+#: ./doc/common/tables/trove-api.xml59(td)
+#: ./doc/common/tables/trove-api.xml63(td)
+#: ./doc/common/tables/trove-api.xml79(td)
+#: ./doc/common/tables/trove-api.xml87(td)
+#: ./doc/common/tables/trove-api.xml103(td)
+#: ./doc/common/tables/trove-dns.xml71(td)
+#: ./doc/common/tables/trove-dns.xml75(td)
+#: ./doc/common/tables/trove-volume.xml39(td)
+#: ./doc/common/tables/trove-volume.xml47(td)
+#: ./doc/common/tables/trove-heat.xml23(td)
+#: ./doc/common/tables/trove-rpc.xml39(td)
+#: ./doc/common/tables/trove-rpc.xml43(td)
+#: ./doc/common/tables/trove-backup.xml71(td)
+#: ./doc/common/tables/trove-guestagent.xml23(td)
+#: ./doc/common/tables/trove-guestagent.xml27(td)
+#: ./doc/common/tables/trove-guestagent.xml31(td)
+#: ./doc/common/tables/trove-database.xml27(td)
+#: ./doc/common/tables/trove-taskmanager.xml43(td)
+#: ./doc/common/tables/trove-taskmanager.xml47(td)
+#: ./doc/common/tables/trove-taskmanager.xml51(td)
+#: ./doc/common/tables/trove-taskmanager.xml55(td)
+#: ./doc/common/tables/trove-taskmanager.xml59(td)
+msgid "(IntOpt) No help text available for this option."
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml43(td)
-msgid "(StrOpt) default glance hostname or ip"
-msgstr ""
+#: ./doc/common/tables/trove-common.xml26(td)
+msgid "databases_page_size = 20"
+msgstr "databases_page_size = 20"
 
-#: ./doc/common/tables/cinder-images.xml47(td)
-msgid "(IntOpt) Number retries when downloading an image from glance"
-msgstr ""
+#: ./doc/common/tables/trove-common.xml30(td)
+msgid "default_datastore = None"
+msgstr "default_datastore = None"
 
-#: ./doc/common/tables/cinder-images.xml51(td)
-msgid "(IntOpt) default glance port"
-msgstr ""
-
-#: ./doc/common/tables/cinder-images.xml54(td)
-msgid "glance_request_timeout = None"
-msgstr "glance_request_timeout = None"
-
-#: ./doc/common/tables/cinder-images.xml55(td)
+#: ./doc/common/tables/trove-common.xml31(td)
 msgid ""
-"(IntOpt) http/https timeout value for glance operations. If no value (None) "
-"is supplied here, the glanceclient default value is used."
+"(StrOpt) The default datastore id or name to use if one is not provided by "
+"the user. If the default value is None, the field becomes required in the "
+"instance-create request."
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml58(td)
-msgid "image_conversion_dir = $state_path/conversion"
-msgstr "image_conversion_dir = $state_path/conversion"
+#: ./doc/common/tables/trove-common.xml38(td)
+msgid "default_neutron_networks ="
+msgstr "default_neutron_networks ="
 
-#: ./doc/common/tables/cinder-images.xml59(td)
-msgid "(StrOpt) Directory used for temporary storage during image conversion"
-msgstr ""
-
-#: ./doc/common/tables/cinder-images.xml70(td)
-msgid "use_multipath_for_image_xfer = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-images.xml71(td)
+#: ./doc/common/tables/trove-common.xml39(td)
 msgid ""
-"(BoolOpt) Do we attach/detach volumes in cinder using multipath for volume "
-"to image and image to volume transfers?"
+"(ListOpt) List of network IDs which should be attached to instance when "
+"networks are not specified in API call."
 msgstr ""
 
-#: ./doc/common/tables/trove-swift.xml22(td)
-msgid "swift_url = http://localhost:8080/v1/AUTH_"
+#: ./doc/common/tables/trove-common.xml46(td)
+msgid "default_password_length = 36"
+msgstr "default_password_length = 36"
+
+#: ./doc/common/tables/trove-common.xml50(td)
+#: ./doc/common/tables/neutron-notifier.xml26(td)
+msgid "default_publisher_id = $host"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-app-container-server.xml7(literal)
-msgid "[app:container-server]"
+#: ./doc/common/tables/trove-common.xml54(td)
+msgid "expected_filetype_suffixes = json"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-app-container-server.xml18(td)
-msgid "use = egg:swift#container"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-app-container-server.xml21(td)
-msgid "set log_name = container-server"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-app-container-server.xml42(td)
-msgid "allow_versions = false"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-app-container-server.xml42(td)
-msgid "Enable/Disable object versioning feature"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml7(literal)
-msgid "[filter:slo]"
-msgstr "[filter:slo]"
-
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml18(td)
-msgid "use = egg:swift#slo"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml21(td)
-msgid "max_manifest_segments = 1000"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml24(td)
-msgid "max_manifest_size = 2097152"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml27(td)
-msgid "min_segment_size = 1048576"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml33(td)
-msgid "rate_limit_segments_per_sec = 0"
-msgstr ""
-
-#: ./doc/common/tables/heat-crypt.xml8(caption)
-msgid "Description of configuration options for crypt"
-msgstr ""
-
-#: ./doc/common/tables/heat-crypt.xml22(td)
-msgid "auth_encryption_key = notgood but just long enough i think"
-msgstr "auth_encryption_key = notgood but just long enough i think"
-
-#: ./doc/common/tables/heat-crypt.xml23(td)
-msgid "(StrOpt) Encryption key used for authentication info in database."
-msgstr ""
-
-#: ./doc/common/tables/neutron-wsgi.xml26(td)
-msgid "retry_until_window = 30"
-msgstr ""
-
-#: ./doc/common/tables/neutron-wsgi.xml27(td)
-msgid "(IntOpt) Number of seconds to keep retrying to listen"
-msgstr ""
-
-#: ./doc/common/tables/neutron-scheduler.xml8(caption)
-#: ./doc/common/tables/cinder-scheduler.xml8(caption)
-msgid "Description of configuration options for scheduler"
-msgstr ""
-
-#: ./doc/common/tables/neutron-scheduler.xml22(td)
-msgid "network_auto_schedule = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-scheduler.xml23(td)
-msgid "(BoolOpt) Allow auto scheduling networks to DHCP agent."
-msgstr ""
-
-#: ./doc/common/tables/neutron-scheduler.xml26(td)
+#: ./doc/common/tables/trove-common.xml55(td)
 msgid ""
-"network_scheduler_driver = "
-"neutron.scheduler.dhcp_agent_scheduler.ChanceScheduler"
+"(ListOpt) Filetype endings not to be reattached to an id by the utils method"
+" correct_id_with_req."
 msgstr ""
 
-#: ./doc/common/tables/neutron-scheduler.xml27(td)
-msgid "(StrOpt) Driver to use for scheduling network to DHCP agent"
+#: ./doc/common/tables/trove-common.xml62(td)
+msgid "pybasedir = /usr/lib/python/site-packages/trove"
+msgstr "pybasedir = /usr/lib/python/site-packages/trove"
+
+#: ./doc/common/tables/trove-common.xml63(td)
+msgid "(StrOpt) Directory where the trove python module is installed."
 msgstr ""
 
-#: ./doc/common/tables/neutron-scheduler.xml30(td)
-msgid "router_auto_schedule = True"
-msgstr ""
+#: ./doc/common/tables/trove-common.xml66(td)
+msgid "pydev_path = None"
+msgstr "pydev_path = None"
 
-#: ./doc/common/tables/neutron-scheduler.xml31(td)
-msgid "(BoolOpt) Allow auto scheduling of routers to L3 agent."
-msgstr ""
-
-#: ./doc/common/tables/neutron-scheduler.xml34(td)
-msgid "router_delete_namespaces = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-scheduler.xml35(td)
-msgid "(BoolOpt) Delete namespace after removing a router."
-msgstr ""
-
-#: ./doc/common/tables/neutron-scheduler.xml38(td)
+#: ./doc/common/tables/trove-common.xml67(td)
 msgid ""
-"router_scheduler_driver = "
-"neutron.scheduler.l3_agent_scheduler.ChanceScheduler"
+"(StrOpt) Set path to pydevd library, used if pydevd is not found in python "
+"sys.path."
 msgstr ""
 
-#: ./doc/common/tables/neutron-scheduler.xml39(td)
-msgid "(StrOpt) Driver to use for scheduling router to a default L3 agent"
+#: ./doc/common/tables/trove-common.xml70(td)
+msgid "taskmanager_queue = taskmanager"
+msgstr "taskmanager_queue = taskmanager"
+
+#: ./doc/common/tables/trove-common.xml74(td)
+msgid "template_path = /etc/trove/templates/"
+msgstr "template_path = /etc/trove/templates/"
+
+#: ./doc/common/tables/trove-common.xml75(td)
+msgid "(StrOpt) Path which leads to datastore templates."
 msgstr ""
 
-#: ./doc/common/tables/keystone-security.xml8(caption)
-msgid "Description of configuration options for security"
+#: ./doc/common/tables/trove-api.xml22(td)
+msgid "admin_roles = admin"
+msgstr "admin_roles = admin"
+
+#: ./doc/common/tables/trove-api.xml23(td)
+#: ./doc/common/tables/trove-guestagent.xml43(td)
+#: ./doc/common/tables/trove-guestagent.xml47(td)
+#: ./doc/common/tables/trove-compute.xml31(td)
+msgid "(ListOpt) No help text available for this option."
 msgstr ""
 
-#: ./doc/common/tables/keystone-security.xml22(td)
-msgid "crypt_strength = 40000"
+#: ./doc/common/tables/trove-api.xml26(td)
+msgid "api_extensions_path = trove/extensions/routes"
+msgstr "api_extensions_path = trove/extensions/routes"
+
+#: ./doc/common/tables/trove-api.xml27(td)
+msgid "(StrOpt) Path to extensions."
 msgstr ""
 
-#: ./doc/common/tables/keystone-security.xml23(td)
+#: ./doc/common/tables/trove-api.xml30(td)
+#: ./doc/common/tables/heat-api.xml134(td)
+#: ./doc/common/tables/cinder-api.xml22(td)
+#: ./doc/common/tables/neutron-api.xml38(td)
+#: ./doc/common/tables/nova-wsgi.xml22(td)
+msgid "api_paste_config = api-paste.ini"
+msgstr "api_paste_config = api-paste.ini"
+
+#: ./doc/common/tables/trove-api.xml31(td)
+msgid "(StrOpt) File name for the paste.deploy config for trove-api."
+msgstr ""
+
+#: ./doc/common/tables/trove-api.xml34(td)
+msgid "bind_port = 8779"
+msgstr "bind_port = 8779"
+
+#: ./doc/common/tables/trove-api.xml38(td)
+msgid "db_api_implementation = trove.db.sqlalchemy.api"
+msgstr "db_api_implementation = trove.db.sqlalchemy.api"
+
+#: ./doc/common/tables/trove-api.xml42(td)
+msgid "hostname_require_ipv4 = True"
+msgstr "hostname_require_ipv4 = True"
+
+#: ./doc/common/tables/trove-api.xml43(td)
+msgid "(BoolOpt) Require user hostnames to be IPv4 addresses."
+msgstr ""
+
+#: ./doc/common/tables/trove-api.xml46(td)
+msgid "http_delete_rate = 200"
+msgstr "http_delete_rate = 200"
+
+#: ./doc/common/tables/trove-api.xml50(td)
+msgid "http_get_rate = 200"
+msgstr "http_get_rate = 200"
+
+#: ./doc/common/tables/trove-api.xml54(td)
+msgid "http_post_rate = 200"
+msgstr "http_post_rate = 200"
+
+#: ./doc/common/tables/trove-api.xml58(td)
+msgid "http_put_rate = 200"
+msgstr "http_put_rate = 200"
+
+#: ./doc/common/tables/trove-api.xml62(td)
+msgid "instances_page_size = 20"
+msgstr "instances_page_size = 20"
+
+#: ./doc/common/tables/trove-api.xml67(td)
+#: ./doc/common/tables/glance-wsgi.xml31(td)
 msgid ""
-"(IntOpt) The value passed as the keyword \"rounds\" to passlib encrypt "
-"method."
+"(IntOpt) Maximum line size of message headers to be accepted. "
+"max_header_line may need to be increased when using large tokens (typically "
+"those generated by the Keystone v3 API with big service catalogs"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-vmware.xml19(th)
-#: ./doc/common/tables/nova-vnc.xml42(th)
-#: ./doc/common/tables/nova-vmware.xml19(th)
-#: ./doc/common/tables/nova-network.xml254(th)
-msgid "[vmware]"
+#: ./doc/common/tables/trove-api.xml70(td)
+msgid "region = LOCAL_DEV"
+msgstr "region = LOCAL_DEV"
+
+#: ./doc/common/tables/trove-api.xml71(td)
+msgid "(StrOpt) The region this service is located."
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-vmware.xml22(td)
-#: ./doc/common/tables/nova-vmware.xml22(td)
-msgid "api_retry_count = 10"
-msgstr "api_retry_count = 10"
-
-#: ./doc/common/tables/ceilometer-vmware.xml23(td)
-msgid "(IntOpt) Number of times a VMware Vsphere API must be retried"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-vmware.xml26(td)
-msgid "host_ip ="
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-vmware.xml27(td)
-msgid "(StrOpt) IP address of the VMware Vsphere host"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-vmware.xml30(td)
-msgid "host_password ="
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-vmware.xml31(td)
-msgid "(StrOpt) Password of VMware Vsphere"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-vmware.xml34(td)
-msgid "host_username ="
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-vmware.xml35(td)
-msgid "(StrOpt) Username of VMware Vsphere"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-vmware.xml38(td)
-#: ./doc/common/tables/nova-vmware.xml54(td)
-msgid "task_poll_interval = 0.5"
-msgstr "task_poll_interval = 0.5"
-
-#: ./doc/common/tables/ceilometer-vmware.xml39(td)
-msgid "(FloatOpt) Sleep time in seconds for polling an ongoing async task"
-msgstr ""
-
-#: ./doc/common/tables/glance-rbd.xml8(caption)
-msgid "Description of configuration options for rbd"
-msgstr ""
-
-#: ./doc/common/tables/glance-rbd.xml22(td)
-msgid "rbd_store_ceph_conf = /etc/ceph/ceph.conf"
-msgstr ""
-
-#: ./doc/common/tables/glance-rbd.xml23(td)
+#: ./doc/common/tables/trove-api.xml75(td)
+#: ./doc/common/tables/cinder-common.xml199(td)
+#: ./doc/common/tables/neutron-wsgi.xml31(td)
+#: ./doc/common/tables/nova-wsgi.xml39(td)
 msgid ""
-"(StrOpt) Ceph configuration file path. If &lt;None&gt;, librados will locate"
-" the default config. If using cephx authentication, this file should include"
-" a reference to the right keyring in a client.&lt;USER&gt; section."
+"(IntOpt) Sets the value of TCP_KEEPIDLE in seconds for each server socket. "
+"Not supported on OS X."
 msgstr ""
 
-#: ./doc/common/tables/glance-rbd.xml26(td)
-msgid "rbd_store_chunk_size = 8"
+#: ./doc/common/tables/trove-api.xml78(td)
+msgid "trove_api_workers = None"
+msgstr "trove_api_workers = None"
+
+#: ./doc/common/tables/trove-api.xml82(td)
+msgid "trove_auth_url = http://0.0.0.0:5000/v2.0"
+msgstr "trove_auth_url = http://0.0.0.0:5000/v2.0"
+
+#: ./doc/common/tables/trove-api.xml86(td)
+msgid "trove_conductor_workers = 1"
+msgstr "trove_conductor_workers = 1"
+
+#: ./doc/common/tables/trove-api.xml90(td)
+msgid "trove_security_group_name_prefix = SecGroup"
+msgstr "trove_security_group_name_prefix = SecGroup"
+
+#: ./doc/common/tables/trove-api.xml94(td)
+msgid "trove_security_group_rule_cidr = 0.0.0.0/0"
+msgstr "trove_security_group_rule_cidr = 0.0.0.0/0"
+
+#: ./doc/common/tables/trove-api.xml98(td)
+msgid "trove_security_groups_support = True"
 msgstr ""
 
-#: ./doc/common/tables/glance-rbd.xml27(td)
+#: ./doc/common/tables/trove-api.xml99(td)
+#: ./doc/common/tables/trove-dns.xml83(td)
+#: ./doc/common/tables/trove-compute.xml35(td)
+#: ./doc/common/tables/trove-database.xml31(td)
+#: ./doc/common/tables/trove-taskmanager.xml71(td)
+#: ./doc/common/tables/trove-taskmanager.xml75(td)
+msgid "(BoolOpt) No help text available for this option."
+msgstr ""
+
+#: ./doc/common/tables/trove-api.xml102(td)
+msgid "users_page_size = 20"
+msgstr "users_page_size = 20"
+
+#: ./doc/common/tables/cinder-zadara.xml8(caption)
+msgid "Description of configuration options for zadara"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml22(td)
+msgid "zadara_password = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml23(td)
+msgid "(StrOpt) Password for the VPSA"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml26(td)
+msgid "zadara_user = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml27(td)
+msgid "(StrOpt) User name for the VPSA"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml30(td)
+msgid "zadara_vol_encrypt = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml31(td)
+msgid "(BoolOpt) Default encryption policy for volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml34(td)
+msgid "zadara_vol_name_template = OS_%s"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml35(td)
+msgid "(StrOpt) Default template for VPSA volume names"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml38(td)
+msgid "zadara_vol_thin = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml39(td)
+msgid "(BoolOpt) Default thin provisioning policy for volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml42(td)
+msgid "zadara_vpsa_allow_nonexistent_delete = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml43(td)
+msgid "(BoolOpt) Don't halt on deletion of non-existing volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml46(td)
+msgid "zadara_vpsa_auto_detach_on_delete = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml47(td)
+msgid "(BoolOpt) Automatically detach from servers on volume delete"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml50(td)
+msgid "zadara_vpsa_ip = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml51(td)
+msgid "(StrOpt) Management IP of Zadara VPSA"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml54(td)
+msgid "zadara_vpsa_poolname = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml55(td)
+msgid "(StrOpt) Name of VPSA storage pool for volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml58(td)
+msgid "zadara_vpsa_port = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml59(td)
+msgid "(StrOpt) Zadara VPSA port number"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml62(td)
+msgid "zadara_vpsa_use_ssl = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml63(td)
+msgid "(BoolOpt) Use SSL connection"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml7(literal)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml7(literal)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml7(literal)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml7(literal)
+#: ./doc/common/tables/swift-object-server-pipeline-main.xml7(literal)
+#: ./doc/common/tables/swift-object-server-object-auditor.xml7(literal)
+#: ./doc/common/tables/swift-object-server-filter-recon.xml7(literal)
+#: ./doc/common/tables/swift-object-server-object-updater.xml7(literal)
+msgid "object-server.conf-sample"
+msgstr "object-server.conf-sample"
+
+#: ./doc/common/tables/nova-conductor.xml8(caption)
+msgid "Description of configuration options for conductor"
+msgstr ""
+
+#: ./doc/common/tables/nova-conductor.xml22(td)
+msgid "migrate_max_retries = -1"
+msgstr ""
+
+#: ./doc/common/tables/nova-conductor.xml23(td)
 msgid ""
-"(IntOpt) RADOS images will be chunked into objects of this size (in "
-"megabytes). For best performance, this should be a power of two."
+"(IntOpt) Number of times to retry live-migration before failing. If == -1, "
+"try until out of hosts. If == 0, only try once, no retries."
 msgstr ""
 
-#: ./doc/common/tables/glance-rbd.xml30(td)
-msgid "rbd_store_pool = images"
+#: ./doc/common/tables/nova-conductor.xml26(th)
+msgid "[conductor]"
+msgstr "[conductor]"
+
+#: ./doc/common/tables/nova-conductor.xml29(td)
+msgid "manager = nova.conductor.manager.ConductorManager"
 msgstr ""
 
-#: ./doc/common/tables/glance-rbd.xml31(td)
-msgid "(StrOpt) RADOS pool in which images are stored."
+#: ./doc/common/tables/nova-conductor.xml30(td)
+msgid "(StrOpt) Full class name for the Manager for conductor"
 msgstr ""
 
-#: ./doc/common/tables/glance-rbd.xml34(td)
-msgid "rbd_store_user = None"
+#: ./doc/common/tables/nova-conductor.xml33(td)
+msgid "topic = conductor"
 msgstr ""
 
-#: ./doc/common/tables/glance-rbd.xml35(td)
+#: ./doc/common/tables/nova-conductor.xml34(td)
+msgid "(StrOpt) The topic on which conductor nodes listen"
+msgstr ""
+
+#: ./doc/common/tables/nova-conductor.xml37(td)
+msgid "use_local = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-conductor.xml38(td)
+msgid "(BoolOpt) Perform nova-conductor operations locally"
+msgstr ""
+
+#: ./doc/common/tables/nova-conductor.xml41(td)
+msgid "workers = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-conductor.xml42(td)
 msgid ""
-"(StrOpt) RADOS user to authenticate as (only applicable if using Cephx. If "
-"&lt;None&gt;, a default will be chosen based on the client. section in "
-"rbd_store_ceph_conf)."
+"(IntOpt) Number of workers for OpenStack Conductor service. The default will"
+" be the number of CPUs available."
 msgstr ""
 
-#: ./doc/common/tables/heat-clients_heat.xml8(caption)
-msgid "Description of configuration options for clients_heat"
+#: ./doc/common/tables/swift-object-server-app-object-server.xml7(literal)
+msgid "[app:object-server]"
+msgstr "[app:object-server]"
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml18(td)
+msgid "use = egg:swift#object"
 msgstr ""
 
-#: ./doc/common/tables/heat-clients_heat.xml19(th)
-msgid "[clients_heat]"
-msgstr "[clients_heat]"
-
-#: ./doc/common/tables/heat-clients_heat.xml42(td)
-#: ./doc/common/tables/neutron-ml2_odl.xml34(td)
-#: ./doc/common/tables/neutron-ml2_ncs.xml30(td)
-msgid "url = None"
+#: ./doc/common/tables/swift-object-server-app-object-server.xml21(td)
+msgid "set log_name = object-server"
 msgstr ""
 
-#: ./doc/common/tables/heat-clients_heat.xml43(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml30(td)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml30(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml30(td)
+msgid "set log_requests = true"
+msgstr "set log_requests = true"
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml30(td)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml30(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml30(td)
+msgid "Whether or not to log requests"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml36(td)
+msgid "max_upload_time = 86400"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml36(td)
+msgid "Maximum time allowed to upload an object"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml39(td)
+msgid "slow = 0"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml39(td)
 msgid ""
-"(StrOpt) Optional heat url in format like "
-"http://0.0.0.0:8004/v1/%(tenant_id)s."
+"If &gt; 0, Minimum time in seconds for a PUT or DELETE request to complete"
 msgstr ""
 
-#: ./doc/common/tables/heat-rabbitmq.xml35(td)
-#: ./doc/common/tables/trove-amqp.xml55(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml42(td)
+msgid "keep_cache_size = 5424880"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml42(td)
+msgid "Largest object size to keep in buffer cache"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml45(td)
+msgid "keep_cache_private = false"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml45(td)
+msgid "Allow non-public objects to stay in kernel's buffer cache"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml48(td)
+msgid "mb_per_sync = 512"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml48(td)
+msgid "On PUT requests, sync file every n MB"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml51(td)
 msgid ""
-"(StrOpt) SSL version to use (valid only if SSL enabled). valid values are "
-"TLSv1, SSLv23 and SSLv3. SSLv2 may be available on some distributions"
+"allowed_headers = Content-Disposition, Content-Encoding, X-Delete-At, X"
+"-Object-Manifest, X-Static-Large-Object"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-logging.xml30(td)
-#: ./doc/common/tables/neutron-notifier.xml22(td)
-#: ./doc/common/tables/heat-amqp.xml34(td)
-#: ./doc/common/tables/trove-common.xml42(td)
-#: ./doc/common/tables/nova-compute.xml54(td)
-msgid "default_notification_level = INFO"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-logging.xml31(td)
-#: ./doc/common/tables/neutron-notifier.xml23(td)
-#: ./doc/common/tables/heat-amqp.xml35(td)
-#: ./doc/common/tables/trove-common.xml43(td)
-#: ./doc/common/tables/nova-compute.xml55(td)
-msgid "(StrOpt) Default notification level for outgoing notifications"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-logging.xml105(td)
-#: ./doc/common/tables/neutron-cadf.xml22(td)
-msgid "api_audit_map = api_audit_map.conf"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-logging.xml106(td)
-#: ./doc/common/tables/neutron-cadf.xml23(td)
-msgid "(StrOpt) File containing mapping for api paths and service endpoints"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metadata.xml22(td)
-msgid "meta_flavor_driver_mappings = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metadata.xml23(td)
-msgid "(StrOpt) Mapping between flavor and LinuxInterfaceDriver"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metadata.xml26(td)
-msgid "metadata_backlog = 128"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metadata.xml27(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml51(td)
 msgid ""
-"(IntOpt) Number of backlog requests to configure the metadata server socket "
-"with"
+"Comma-separated list of headers that can be set in metadata of an object"
 msgstr ""
 
-#: ./doc/common/tables/neutron-metadata.xml30(td)
-msgid "metadata_port = 9697"
+#: ./doc/common/tables/swift-object-server-app-object-server.xml57(td)
+msgid "threads_per_disk = 0"
 msgstr ""
 
-#: ./doc/common/tables/neutron-metadata.xml31(td)
-msgid "(IntOpt) TCP Port used by Neutron metadata namespace proxy."
-msgstr ""
-
-#: ./doc/common/tables/neutron-metadata.xml34(td)
-msgid "metadata_proxy_shared_secret ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-metadata.xml35(td)
-#: ./doc/common/tables/neutron-vmware.xml146(td)
-msgid "(StrOpt) Shared secret to sign instance-id request"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metadata.xml38(td)
-msgid "metadata_proxy_socket = $state_path/metadata_proxy"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metadata.xml39(td)
-msgid "(StrOpt) Location of Metadata Proxy UNIX domain socket"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metadata.xml42(td)
-msgid "metadata_workers = 0"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metadata.xml43(td)
-msgid "(IntOpt) Number of separate worker processes for metadata server"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metadata.xml46(td)
-msgid "nova_metadata_ip = 127.0.0.1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metadata.xml47(td)
-msgid "(StrOpt) IP address used by Nova metadata server."
-msgstr ""
-
-#: ./doc/common/tables/neutron-metadata.xml50(td)
-msgid "nova_metadata_port = 8775"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metadata.xml51(td)
-msgid "(IntOpt) TCP Port used by Nova metadata server."
-msgstr ""
-
-#: ./doc/common/tables/glance-redis.xml23(td)
-#: ./doc/common/tables/keystone-redis.xml23(td)
-msgid "(StrOpt) Host to locate redis."
-msgstr ""
-
-#: ./doc/common/tables/keystone-stats.xml8(caption)
-msgid "Description of configuration options for stats"
-msgstr ""
-
-#: ./doc/common/tables/keystone-stats.xml19(th)
-msgid "[stats]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-stats.xml22(td)
-msgid "driver = keystone.contrib.stats.backends.kvs.Stats"
-msgstr ""
-
-#: ./doc/common/tables/keystone-stats.xml23(td)
-msgid "(StrOpt) Keystone stats backend driver."
-msgstr ""
-
-#: ./doc/common/tables/cinder-hp3par.xml8(caption)
-msgid "Description of configuration options for hp3par"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hp3par.xml22(td)
-msgid "hp3par_api_url ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-hp3par.xml23(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml57(td)
 msgid ""
-"(StrOpt) 3PAR WSAPI Server Url like https://&lt;3par ip&gt;:8080/api/v1"
+"Size of the per-disk thread pool used for performing disk I/O. The default "
+"of 0 means to not use a per-disk thread pool. It is recommended to keep this"
+" value small, as large values can result in high read latencies due to large"
+" queue depths. A good starting point is 4 threads per disk."
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml26(td)
-msgid "hp3par_cpg = OpenStack"
-msgstr ""
+#: ./doc/common/tables/swift-object-server-app-object-server.xml60(td)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml39(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml48(td)
+msgid "replication_server = false"
+msgstr "replication_server = false"
 
-#: ./doc/common/tables/cinder-hp3par.xml27(td)
-msgid "(StrOpt) The CPG to use for volume creation"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hp3par.xml30(td)
-msgid "hp3par_cpg_snap ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-hp3par.xml31(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml60(td)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml39(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml48(td)
 msgid ""
-"(StrOpt) The CPG to use for Snapshots for volumes. If empty hp3par_cpg will "
-"be used"
+"If defined, tells server how to handle replication verbs in requests. When "
+"set to True (or 1), only replication verbs will be accepted. When set to "
+"False, replication verbs will be rejected. When undefined, server will "
+"accept any verb in the request."
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml34(td)
-msgid "hp3par_debug = False"
+#: ./doc/common/tables/swift-object-server-app-object-server.xml63(td)
+msgid "replication_concurrency = 4"
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml35(td)
-msgid "(BoolOpt) Enable HTTP debugging to 3PAR"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hp3par.xml38(td)
-msgid "hp3par_iscsi_ips ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-hp3par.xml39(td)
-msgid "(ListOpt) List of target iSCSI addresses to use."
-msgstr ""
-
-#: ./doc/common/tables/cinder-hp3par.xml42(td)
-msgid "hp3par_password ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-hp3par.xml43(td)
-msgid "(StrOpt) 3PAR Super user password"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hp3par.xml46(td)
-msgid "hp3par_snapshot_expiration ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-hp3par.xml47(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml63(td)
 msgid ""
-"(StrOpt) The time in hours when a snapshot expires and is deleted. This must"
-" be larger than expiration"
+"Set to restrict the number of concurrent incoming REPLICATION requests; set "
+"to 0 for unlimited"
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml50(td)
-msgid "hp3par_snapshot_retention ="
+#: ./doc/common/tables/swift-object-server-app-object-server.xml66(td)
+msgid "replication_one_per_device = True"
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml51(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml66(td)
 msgid ""
-"(StrOpt) The time in hours to retain a snapshot. You can't delete it before "
-"this expires."
+"Restricts incoming REPLICATION requests to one per device, "
+"replication_currency above allowing. This can help control I/O to each "
+"device, but you may wish to set this to False to allow multiple REPLICATION "
+"requests (up to the above replication_concurrency setting) per device."
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml54(td)
-msgid "hp3par_username ="
+#: ./doc/common/tables/swift-object-server-app-object-server.xml69(td)
+msgid "replication_lock_timeout = 15"
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml55(td)
-msgid "(StrOpt) 3PAR Super user username"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_ceph.xml8(caption)
-msgid "Description of configuration options for storage_ceph"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_ceph.xml22(td)
-msgid "rbd_ceph_conf ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_ceph.xml23(td)
-msgid "(StrOpt) path to the ceph configuration file to use"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_ceph.xml26(td)
-msgid "rbd_flatten_volume_from_snapshot = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_ceph.xml27(td)
-msgid "(BoolOpt) flatten volumes created from snapshots to remove dependency"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_ceph.xml30(td)
-msgid "rbd_max_clone_depth = 5"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_ceph.xml31(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml69(td)
 msgid ""
-"(IntOpt) maximum number of nested clones that can be taken of a volume "
-"before enforcing a flatten prior to next clone. A value of zero disables "
-"cloning"
+"Number of seconds to wait for an existing replication device lock before "
+"giving up."
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_ceph.xml34(td)
-msgid "rbd_pool = rbd"
+#: ./doc/common/tables/swift-object-server-app-object-server.xml72(td)
+msgid "replication_failure_threshold = 100"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_ceph.xml35(td)
-msgid "(StrOpt) the RADOS pool in which rbd volumes are stored"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_ceph.xml39(td)
-msgid "(StrOpt) the libvirt uuid of the secret for the rbd_uservolumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_ceph.xml43(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml72(td)
 msgid ""
-"(StrOpt) the RADOS client name for accessing rbd volumes - only set when "
-"using cephx authentication"
+"The number of subrequest failures before the replication_failure_ratio is "
+"checked"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_ceph.xml46(td)
-msgid "volume_tmp_dir = None"
+#: ./doc/common/tables/swift-object-server-app-object-server.xml75(td)
+msgid "replication_failure_ratio = 1.0"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_ceph.xml47(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml75(td)
 msgid ""
-"(StrOpt) where to store temporary image files if the volume driver does not "
-"write them directly to the volume"
+"If the value of failures / successes of REPLICATION subrequests exceeds this"
+" ratio, the overall REPLICATION request will be aborted"
 msgstr ""
 
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml21(td)
+msgid "set log_name = catch_errors"
+msgstr "set log_name = catch_errors"
+
 #: ./doc/common/tables/nova-livemigration.xml8(caption)
 msgid "Description of configuration options for livemigration"
 msgstr ""
@@ -37567,478 +37967,142 @@ msgid ""
 "migration target hostname)"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml22(td)
-msgid "ldap_dns_base_dn = ou=hosts,dc=example,dc=org"
-msgstr ""
-
-#: ./doc/common/tables/nova-ldap.xml23(td)
-msgid "(StrOpt) Base DN for DNS entries in LDAP"
-msgstr ""
-
-#: ./doc/common/tables/nova-ldap.xml26(td)
-msgid "ldap_dns_password = password"
-msgstr ""
-
-#: ./doc/common/tables/nova-ldap.xml27(td)
-msgid "(StrOpt) Password for LDAP DNS"
-msgstr ""
-
-#: ./doc/common/tables/nova-ldap.xml30(td)
-msgid "ldap_dns_servers = ['dns.example.org']"
-msgstr ""
-
-#: ./doc/common/tables/nova-ldap.xml31(td)
-msgid "(MultiStrOpt) DNS Servers for LDAP DNS driver"
-msgstr ""
-
-#: ./doc/common/tables/nova-ldap.xml34(td)
-msgid "ldap_dns_soa_expiry = 86400"
-msgstr ""
-
-#: ./doc/common/tables/nova-ldap.xml35(td)
+#: ./doc/common/tables/heat-rabbitmq.xml39(td)
+#: ./doc/common/tables/trove-rabbitmq.xml23(td)
 msgid ""
-"(StrOpt) Expiry interval (in seconds) for LDAP DNS driver Statement of "
-"Authority"
+"(BoolOpt) use H/A queues in RabbitMQ (x-ha-policy: all).You need to wipe "
+"RabbitMQ database when changing this option."
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml38(td)
-msgid "ldap_dns_soa_hostmaster = hostmaster@example.org"
+#: ./doc/common/tables/heat-rabbitmq.xml43(td)
+#: ./doc/common/tables/trove-rabbitmq.xml27(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml27(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml47(td)
+msgid "(StrOpt) The RabbitMQ broker address where a single node is used"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml39(td)
-msgid "(StrOpt) Hostmaster for LDAP DNS driver Statement of Authority"
+#: ./doc/common/tables/heat-rabbitmq.xml47(td)
+#: ./doc/common/tables/trove-rabbitmq.xml31(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml31(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml51(td)
+msgid "(ListOpt) RabbitMQ HA cluster host:port pairs"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml42(td)
-msgid "ldap_dns_soa_minimum = 7200"
-msgstr ""
-
-#: ./doc/common/tables/nova-ldap.xml43(td)
+#: ./doc/common/tables/heat-rabbitmq.xml51(td)
+#: ./doc/common/tables/trove-rabbitmq.xml35(td)
 msgid ""
-"(StrOpt) Minimum interval (in seconds) for LDAP DNS driver Statement of "
-"Authority"
+"(IntOpt) maximum retries with trying to connect to RabbitMQ (the default of "
+"0 implies an infinite retry count)"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml46(td)
-msgid "ldap_dns_soa_refresh = 1800"
+#: ./doc/common/tables/heat-rabbitmq.xml55(td)
+#: ./doc/common/tables/trove-rabbitmq.xml39(td)
+msgid "(StrOpt) the RabbitMQ password"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml47(td)
+#: ./doc/common/tables/heat-rabbitmq.xml59(td)
+#: ./doc/common/tables/trove-rabbitmq.xml43(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml43(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml63(td)
+msgid "(IntOpt) The RabbitMQ broker port where a single node is used"
+msgstr ""
+
+#: ./doc/common/tables/heat-rabbitmq.xml63(td)
+#: ./doc/common/tables/trove-rabbitmq.xml47(td)
 msgid ""
-"(StrOpt) Refresh interval (in seconds) for LDAP DNS driver Statement of "
-"Authority"
+"(IntOpt) how long to backoff for between retries when connecting to RabbitMQ"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml50(td)
-msgid "ldap_dns_soa_retry = 3600"
+#: ./doc/common/tables/heat-rabbitmq.xml67(td)
+#: ./doc/common/tables/trove-rabbitmq.xml51(td)
+msgid "(IntOpt) how frequently to retry connecting with RabbitMQ"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml51(td)
+#: ./doc/common/tables/heat-rabbitmq.xml71(td)
+#: ./doc/common/tables/trove-rabbitmq.xml55(td)
+msgid "(BoolOpt) connect over SSL for RabbitMQ"
+msgstr ""
+
+#: ./doc/common/tables/heat-rabbitmq.xml75(td)
+#: ./doc/common/tables/trove-rabbitmq.xml59(td)
+msgid "(StrOpt) the RabbitMQ userid"
+msgstr ""
+
+#: ./doc/common/tables/heat-rabbitmq.xml79(td)
+#: ./doc/common/tables/trove-rabbitmq.xml63(td)
+msgid "(StrOpt) the RabbitMQ virtual host"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml7(literal)
+msgid "[filter:keystoneauth]"
+msgstr "[filter:keystoneauth]"
+
+#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml18(td)
+msgid "use = egg:swift#keystoneauth"
+msgstr "use = egg:swift#keystoneauth"
+
+#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml21(td)
+msgid "operator_roles = admin, swiftoperator"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml24(td)
+msgid "reseller_admin_role = ResellerAdmin"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cadf.xml8(caption)
+msgid "Description of configuration options for cadf"
+msgstr ""
+
+#: ./doc/common/tables/keystone-amqp.xml46(td)
+#: ./doc/common/tables/glance-amqp.xml38(td)
+#: ./doc/common/tables/cinder-rpc.xml182(td)
+#: ./doc/common/tables/nova-rpc_all.xml150(td)
+#: ./doc/common/tables/nova-rpc.xml42(td)
+msgid "rpc_backend = rabbit"
+msgstr "rpc_backend = rabbit"
+
+#: ./doc/common/tables/keystone-amqp.xml47(td)
+#: ./doc/common/tables/glance-amqp.xml39(td)
+#: ./doc/common/tables/cinder-rpc.xml183(td)
+#: ./doc/common/tables/nova-rpc_all.xml151(td)
+#: ./doc/common/tables/nova-rpc.xml43(td)
 msgid ""
-"(StrOpt) Retry interval (in seconds) for LDAP DNS driver Statement of "
-"Authority"
+"(StrOpt) The messaging driver to use, defaults to rabbit. Other drivers "
+"include qpid and zmq."
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml54(td)
-msgid "ldap_dns_url = ldap://ldap.example.com:389"
+#: ./doc/common/tables/keystone-amqp.xml55(td)
+#: ./doc/common/tables/glance-amqp.xml43(td)
+#: ./doc/common/tables/cinder-rpc.xml191(td)
+#: ./doc/common/tables/nova-rpc_all.xml159(td)
+#: ./doc/common/tables/nova-rpc.xml51(td)
+msgid "(IntOpt) Size of RPC connection pool."
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml55(td)
-msgid "(StrOpt) URL for LDAP server which will store DNS entries"
+#: ./doc/common/tables/keystone-amqp.xml59(td)
+#: ./doc/common/tables/glance-amqp.xml47(td)
+#: ./doc/common/tables/cinder-rpc.xml195(td)
+#: ./doc/common/tables/nova-rpc_all.xml163(td)
+#: ./doc/common/tables/nova-rpc.xml55(td)
+msgid "(IntOpt) Seconds to wait for a response from a call."
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml58(td)
-msgid "ldap_dns_user = uid=admin,ou=people,dc=example,dc=org"
-msgstr ""
-
-#: ./doc/common/tables/nova-ldap.xml59(td)
-msgid "(StrOpt) User for LDAP DNS"
-msgstr ""
-
-#: ./doc/common/tables/nova-fping.xml8(caption)
-msgid "Description of configuration options for fping"
-msgstr ""
-
-#: ./doc/common/tables/nova-fping.xml22(td)
-msgid "fping_path = /usr/sbin/fping"
-msgstr ""
-
-#: ./doc/common/tables/nova-fping.xml23(td)
-msgid "(StrOpt) Full path to fping."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_swift.xml8(caption)
-msgid "Description of configuration options for clients_swift"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_swift.xml19(th)
-msgid "[clients_swift]"
-msgstr "[clients_swift]"
-
-#: ./doc/common/tables/neutron-securitygroups.xml8(caption)
-msgid "Description of configuration options for securitygroups"
-msgstr ""
-
-#: ./doc/common/tables/neutron-securitygroups.xml19(th)
-msgid "[SECURITYGROUP]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-securitygroups.xml22(td)
-msgid "enable_security_group = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-securitygroups.xml23(td)
-msgid ""
-"(BoolOpt) Controls whether the neutron security group API is enabled in the "
-"server. It should be false when using no security groups or using the nova "
-"security group API."
-msgstr ""
-
-#: ./doc/common/tables/neutron-securitygroups.xml26(td)
-#: ./doc/common/tables/nova-network.xml78(td)
-msgid "firewall_driver = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-securitygroups.xml27(td)
-msgid "(StrOpt) Driver for security groups firewall in the L2 agent"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml8(caption)
-msgid "Description of configuration options for netapp_cdot_iscsi"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml54(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml58(td)
-msgid "netapp_vserver = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml55(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml59(td)
-msgid ""
-"(StrOpt) This option specifies the virtual storage server (Vserver) name on "
-"the storage cluster on which provisioning of block storage volumes should "
-"occur. If using the NFS storage protocol, this parameter is mandatory for "
-"storage service catalog support (utilized by Cinder volume type extra_specs "
-"support). If this option is specified, the exports belonging to the Vserver "
-"will only be used for provisioning in the future. Block storage volumes on "
-"exports not belonging to the Vserver specified by this option will continue "
-"to function normally."
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml8(caption)
-#: ./doc/common/tables/keystone-ec2.xml8(caption)
-msgid "Description of configuration options for ec2"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml22(td)
-msgid "ec2_dmz_host = $my_ip"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml23(td)
-msgid "(StrOpt) The internal IP address of the EC2 API server"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml26(td)
-msgid "ec2_host = $my_ip"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml27(td)
-msgid "(StrOpt) The IP address of the EC2 API server"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml30(td)
-msgid "ec2_listen = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml31(td)
-msgid "(StrOpt) The IP address on which the EC2 API will listen."
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml34(td)
-msgid "ec2_listen_port = 8773"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml35(td)
-msgid "(IntOpt) The port on which the EC2 API will listen."
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml38(td)
-msgid "ec2_path = /services/Cloud"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml39(td)
-msgid "(StrOpt) The path prefix used to call the ec2 API server"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml42(td)
-msgid "ec2_port = 8773"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml43(td)
-msgid "(IntOpt) The port of the EC2 API server"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml46(td)
-msgid "ec2_private_dns_show_ip = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml47(td)
-msgid ""
-"(BoolOpt) Return the IP address as private dns hostname in describe "
-"instances"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml50(td)
-msgid "ec2_scheme = http"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml51(td)
-msgid ""
-"(StrOpt) The protocol to use when connecting to the EC2 API server (http, "
-"https)"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml54(td)
-msgid "ec2_strict_validation = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml55(td)
-msgid "(BoolOpt) Validate security group names according to EC2 specification"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml58(td)
-msgid "ec2_timestamp_expiry = 300"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml59(td)
-msgid "(IntOpt) Time in seconds before ec2 timestamp expires"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml62(td)
-msgid "ec2_workers = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml63(td)
-msgid ""
-"(IntOpt) Number of workers for EC2 API service. The default will be equal to"
-" the number of CPUs available."
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml66(td)
-#: ./doc/common/tables/keystone-ec2.xml38(td)
-msgid "keystone_ec2_url = http://localhost:5000/v2.0/ec2tokens"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml67(td)
-#: ./doc/common/tables/keystone-ec2.xml39(td)
-msgid "(StrOpt) URL to get token from ec2 request."
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml70(td)
-msgid "lockout_attempts = 5"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml71(td)
-msgid "(IntOpt) Number of failed auths before lockout."
-msgstr "(IntOpt) Nombre d’échecs d’authentification avant blocage."
-
-#: ./doc/common/tables/nova-ec2.xml74(td)
-msgid "lockout_minutes = 15"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml75(td)
-msgid "(IntOpt) Number of minutes to lockout if triggered."
-msgstr "(IntOpt) Nombre de minutes de blocage si déclenché."
-
-#: ./doc/common/tables/nova-ec2.xml78(td)
-msgid "lockout_window = 15"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml79(td)
-msgid "(IntOpt) Number of minutes for lockout window."
-msgstr "(IntOpt) Nombre de minutes pour fenêtre de blocage."
-
-#: ./doc/common/tables/nova-ec2.xml82(td)
-msgid "region_list ="
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml83(td)
-msgid "(ListOpt) List of region=fqdn pairs separated by commas"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-account-auditor.xml7(literal)
-msgid "[account-auditor]"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-account-auditor.xml18(td)
-msgid "log_name = account-auditor"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-account-auditor.xml30(td)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml30(td)
-msgid "interval = 1800"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-account-auditor.xml39(td)
-msgid "accounts_per_second = 200"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-account-auditor.xml39(td)
-msgid ""
-"Maximum accounts audited per second. Should be tuned according to individual"
-" system specs. 0 is unlimited."
-msgstr ""
-
-#: ./doc/common/tables/trove-zeromq.xml27(td)
-#: ./doc/common/tables/ceilometer-rpc.xml55(td)
-#: ./doc/common/tables/heat-zeromq.xml27(td)
-#: ./doc/common/tables/neutron-zeromq.xml27(td)
-msgid "(IntOpt) Number of ZeroMQ contexts, defaults to 1"
-msgstr ""
-
-#: ./doc/common/tables/trove-zeromq.xml35(td)
-#: ./doc/common/tables/ceilometer-rpc.xml63(td)
-#: ./doc/common/tables/heat-zeromq.xml35(td)
-#: ./doc/common/tables/neutron-zeromq.xml35(td)
-msgid "(StrOpt) Directory for holding IPC sockets"
-msgstr ""
-
-#: ./doc/common/tables/trove-zeromq.xml38(td)
-msgid ""
-"rpc_zmq_matchmaker = "
-"trove.openstack.common.rpc.matchmaker.MatchMakerLocalhost"
-msgstr ""
-
-#: ./doc/common/tables/trove-zeromq.xml39(td)
-#: ./doc/common/tables/ceilometer-rpc.xml67(td)
-#: ./doc/common/tables/heat-zeromq.xml39(td)
-#: ./doc/common/tables/neutron-zeromq.xml39(td)
-msgid "(StrOpt) MatchMaker driver"
-msgstr ""
-
-#: ./doc/common/tables/trove-zeromq.xml43(td)
-#: ./doc/common/tables/ceilometer-rpc.xml71(td)
-#: ./doc/common/tables/heat-zeromq.xml43(td)
-#: ./doc/common/tables/neutron-zeromq.xml43(td)
-msgid "(IntOpt) ZeroMQ receiver listening port"
-msgstr ""
-
-#: ./doc/common/tables/heat-database.xml8(caption)
-#: ./doc/common/tables/ceilometer-database.xml8(caption)
-#: ./doc/common/tables/cinder-database.xml8(caption)
-#: ./doc/common/tables/trove-database.xml8(caption)
-#: ./doc/common/tables/keystone-database.xml8(caption)
-msgid "Description of configuration options for database"
-msgstr ""
-
-#: ./doc/common/tables/heat-database.xml22(td)
-#: ./doc/common/tables/cinder-database.xml22(td)
-#: ./doc/common/tables/nova-baremetal.xml22(td)
-msgid "db_backend = sqlalchemy"
-msgstr ""
-
-#: ./doc/common/tables/heat-database.xml23(td)
-msgid "(StrOpt) The backend to use for db."
-msgstr ""
-
-#: ./doc/common/tables/heat-database.xml26(td)
-msgid "sqlite_db = heat.sqlite"
-msgstr "sqlite_db = heat.sqlite"
-
-#: ./doc/common/tables/heat-database.xml27(td)
-#: ./doc/common/tables/cinder-common.xml167(td)
-msgid "(StrOpt) the filename to use with sqlite"
-msgstr "(StrOpt)  Le nom de fichier à utiliser avec sqlite"
-
-#: ./doc/common/tables/heat-database.xml31(td)
-#: ./doc/common/tables/cinder-common.xml171(td)
-msgid "(BoolOpt) If true, use synchronous mode for sqlite"
-msgstr ""
-
-#: ./doc/common/tables/heat-database.xml41(td)
-msgid ""
-"connection = sqlite:////usr/lib/python/site-"
-"packages/heat/openstack/common/db/$sqlite_db"
-msgstr "connection = sqlite:////usr/lib/python/site-packages/heat/openstack/common/db/$sqlite_db"
-
-#: ./doc/common/tables/heat-database.xml54(td)
-#: ./doc/common/tables/cinder-common.xml230(td)
-msgid "(IntOpt) timeout before idle sql connections are reaped"
-msgstr "(IntOpt) délai d'attente avant que les connexions SQL inactives ne soient réclamées"
-
-#: ./doc/common/tables/heat-database.xml66(td)
-#: ./doc/common/tables/cinder-storage.xml150(td)
-msgid ""
-"(IntOpt) maximum db connection retries during startup. (setting -1 implies "
-"an infinite retry count)"
-msgstr "(IntOpt) Nombre maximum de nouvelles tentatives de connexion db pendant le démarrage. (paramètre -1 implique un nombre indéfini de nouvelles tentatives)"
-
-#: ./doc/common/tables/heat-database.xml78(td)
-#: ./doc/common/tables/cinder-common.xml234(td)
-msgid "(IntOpt) interval between retries of opening a sql connection"
-msgstr "(IntOpt) Intervalle entre les nouvelles tentatives d’ouverture d’une connexion  sql"
-
-#: ./doc/common/tables/heat-database.xml81(td)
-#: ./doc/common/tables/ceilometer-database.xml85(td)
-#: ./doc/common/tables/neutron-db.xml93(td)
-msgid "slave_connection ="
-msgstr "slave_connection ="
-
-#: ./doc/common/tables/keystone-catalog.xml8(caption)
-msgid "Description of configuration options for catalog"
-msgstr ""
-
-#: ./doc/common/tables/keystone-catalog.xml19(th)
-msgid "[catalog]"
-msgstr "[catalog]"
-
-#: ./doc/common/tables/keystone-catalog.xml22(td)
-msgid "driver = keystone.catalog.backends.sql.Catalog"
-msgstr ""
-
-#: ./doc/common/tables/keystone-catalog.xml23(td)
-msgid "(StrOpt) Keystone catalog backend driver."
-msgstr ""
-
-#: ./doc/common/tables/keystone-catalog.xml27(td)
-msgid ""
-"(IntOpt) Maximum number of entities that will be returned in a catalog "
-"collection."
-msgstr ""
-
-#: ./doc/common/tables/keystone-catalog.xml30(td)
-msgid "template_file = default_catalog.templates"
-msgstr ""
-
-#: ./doc/common/tables/keystone-catalog.xml31(td)
-msgid ""
-"(StrOpt) Catalog template file name for use with the template catalog "
-"backend."
+#: ./doc/common/tables/keystone-amqp.xml63(td)
+#: ./doc/common/tables/glance-amqp.xml51(td)
+#: ./doc/common/tables/cinder-rpc.xml199(td)
+#: ./doc/common/tables/nova-rpc_all.xml167(td)
+#: ./doc/common/tables/nova-rpc.xml59(td)
+msgid "(IntOpt) Size of RPC greenthread pool."
 msgstr ""
 
 #: ./doc/common/tables/swift-object-server-DEFAULT.xml21(td)
 msgid "bind_port = 6000"
 msgstr ""
 
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml45(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml64(td)
-msgid "expiring_objects_container_divisor = 86400"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml48(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml67(td)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml24(td)
-msgid "expiring_objects_account_name = expiring_objects"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml115(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml118(td)
-msgid "client_timeout = 60"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml115(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml118(td)
-msgid "Timeout to read one chunk from a client external services"
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml112(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml36(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml36(td)
+msgid "node_timeout = 3"
 msgstr ""
 
 #: ./doc/common/tables/swift-object-server-DEFAULT.xml118(td)
@@ -38057,415 +38121,156 @@ msgstr ""
 msgid "Size of chunks to read/write to disk"
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml8(caption)
-#: ./doc/common/tables/neutron-rootwrap.xml8(caption)
-#: ./doc/common/tables/nova-rootwrap.xml8(caption)
-msgid "Description of configuration options for rootwrap"
+#: ./doc/common/tables/cinder-zones.xml8(caption)
+msgid "Description of configuration options for zones"
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml22(td)
-msgid "filters_path = /etc/cinder/rootwrap.d,/usr/share/cinder/rootwrap"
+#: ./doc/common/tables/cinder-zones.xml22(td)
+msgid "cloned_volume_same_az = True"
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml23(td)
-#: ./doc/common/tables/neutron-rootwrap.xml23(td)
-#: ./doc/common/tables/nova-rootwrap.xml23(td)
+#: ./doc/common/tables/cinder-zones.xml23(td)
 msgid ""
-"List of directories to load filter definitions from (separated by ','). "
-"These directories MUST all be only writeable by root !"
+"(BoolOpt) Ensure that the new volumes are the same AZ as snapshot or source "
+"volume"
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml26(td)
-#: ./doc/common/tables/neutron-rootwrap.xml26(td)
-#: ./doc/common/tables/nova-rootwrap.xml26(td)
-msgid "exec_dirs = /sbin,/usr/sbin,/bin,/usr/bin"
+#: ./doc/common/tables/cinder-scality.xml8(caption)
+msgid "Description of configuration options for scality"
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml27(td)
-#: ./doc/common/tables/neutron-rootwrap.xml27(td)
-#: ./doc/common/tables/nova-rootwrap.xml27(td)
+#: ./doc/common/tables/cinder-scality.xml30(td)
+msgid "scality_sofs_volume_dir = cinder/volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scality.xml31(td)
+msgid "(StrOpt) Path from Scality SOFS root to volume dir"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml7(literal)
+msgid "[filter:tempauth]"
+msgstr "[filter:tempauth]"
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml18(td)
+msgid "use = egg:swift#tempauth"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml21(td)
+msgid "set log_name = tempauth"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml36(td)
+msgid "reseller_prefix = AUTH"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml36(td)
+msgid "The naming scope for the auth service. Swift"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml39(td)
+msgid "auth_prefix = /auth/"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml39(td)
 msgid ""
-"List of directories to search executables in, in case filters do not "
-"explicitely specify a full path (separated by ',') If not specified, "
-"defaults to system PATH environment variable. These directories MUST all be "
-"only writeable by root !"
+"The HTTP request path prefix for the auth service. Swift itself reserves "
+"anything beginning with the letter `v`."
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml31(td)
-#: ./doc/common/tables/neutron-rootwrap.xml31(td)
-#: ./doc/common/tables/nova-rootwrap.xml31(td)
-msgid "Enable logging to syslog Default value is False"
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml42(td)
+msgid "token_life = 86400"
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml34(td)
-#: ./doc/common/tables/neutron-rootwrap.xml34(td)
-#: ./doc/common/tables/nova-rootwrap.xml34(td)
-msgid "syslog_log_facility = syslog"
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml42(td)
+msgid "The number of seconds a token is valid."
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml35(td)
-#: ./doc/common/tables/neutron-rootwrap.xml35(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml45(td)
+msgid "allow_overrides = true"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml48(td)
+msgid "storage_url_scheme = default"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml48(td)
 msgid ""
-"Which syslog facility to use. Valid values include auth, authpriv, syslog, "
-"local0, local1... Default value is 'syslog'"
+"Scheme to return with storage urls: http, https, or default (chooses based "
+"on what the server is running as) This can be useful with an SSL load "
+"balancer in front of a non-SSL server."
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml38(td)
-#: ./doc/common/tables/neutron-rootwrap.xml38(td)
-#: ./doc/common/tables/nova-rootwrap.xml38(td)
-msgid "syslog_log_level = ERROR"
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml51(td)
+msgid "user_admin_admin = admin .admin .reseller_admin"
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml39(td)
-#: ./doc/common/tables/neutron-rootwrap.xml39(td)
-#: ./doc/common/tables/nova-rootwrap.xml39(td)
-msgid ""
-"Which messages to log. INFO means log all usage ERROR means only log "
-"unsuccessful attempts"
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml54(td)
+msgid "user_test_tester = testing .admin"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-database.xml22(td)
-msgid "database_connection = None"
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml57(td)
+msgid "user_test2_tester2 = testing2 .admin"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-database.xml23(td)
-msgid "(StrOpt) DEPRECATED - Database connection string."
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml60(td)
+msgid "user_test_tester3 = testing3"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-database.xml26(td)
-msgid "mysql_engine = InnoDB"
+#: ./doc/common/tables/neutron-agent.xml8(caption)
+msgid "Description of configuration options for agent"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-database.xml27(td)
-msgid "(StrOpt) MySQL engine to use."
+#: ./doc/common/tables/neutron-agent.xml22(td)
+msgid "external_pids = $state_path/external/pids"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-database.xml30(td)
-msgid "sqlite_db = ceilometer.sqlite"
+#: ./doc/common/tables/neutron-agent.xml23(td)
+msgid "(StrOpt) Location to store child pid files"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-database.xml45(td)
-msgid ""
-"connection = sqlite:////usr/lib/python/site-"
-"packages/ceilometer/openstack/common/db/$sqlite_db"
+#: ./doc/common/tables/neutron-agent.xml26(td)
+#: ./doc/common/tables/nova-network.xml170(td)
+msgid "network_device_mtu = None"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-database.xml89(td)
-msgid "time_to_live = -1"
+#: ./doc/common/tables/neutron-agent.xml27(td)
+msgid "(IntOpt) MTU setting for device."
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-database.xml90(td)
-msgid ""
-"(IntOpt) Number of seconds that samples are kept in the database for (&lt;= "
-"0 means forever)."
+#: ./doc/common/tables/cinder-emc.xml8(caption)
+msgid "Description of configuration options for emc"
 msgstr ""
 
-#: ./doc/common/tables/cinder-nexenta_nfs.xml8(caption)
-msgid "Description of configuration options for nexenta_nfs"
+#: ./doc/common/tables/cinder-emc.xml22(td)
+msgid "cinder_emc_config_file = /etc/cinder/cinder_emc_config.xml"
 msgstr ""
 
-#: ./doc/common/tables/cinder-nexenta_nfs.xml22(td)
-msgid "nexenta_mount_point_base = $state_path/mnt"
+#: ./doc/common/tables/cinder-emc.xml23(td)
+msgid "(StrOpt) use this file for cinder emc plugin config data"
 msgstr ""
 
-#: ./doc/common/tables/cinder-nexenta_nfs.xml23(td)
-msgid "(StrOpt) Base dir containing mount points for nfs shares"
+#: ./doc/common/tables/cinder-emc.xml26(td)
+msgid "max_luns_per_storage_group = 256"
 msgstr ""
 
-#: ./doc/common/tables/cinder-nexenta_nfs.xml26(td)
-msgid "nexenta_nms_cache_volroot = True"
+#: ./doc/common/tables/cinder-emc.xml27(td)
+msgid "(IntOpt) Default max number of LUNs in a storage group"
 msgstr ""
 
-#: ./doc/common/tables/cinder-nexenta_nfs.xml27(td)
-msgid ""
-"(BoolOpt) If set True cache NexentaStor appliance volroot option value."
+#: ./doc/common/tables/cinder-emc.xml30(td)
+msgid "naviseccli_path ="
 msgstr ""
 
-#: ./doc/common/tables/cinder-nexenta_nfs.xml30(td)
-msgid "nexenta_shares_config = /etc/cinder/nfs_shares"
+#: ./doc/common/tables/cinder-emc.xml31(td)
+msgid "(StrOpt) Naviseccli Path"
 msgstr ""
 
-#: ./doc/common/tables/cinder-nexenta_nfs.xml34(td)
-msgid "nexenta_volume_compression = on"
+#: ./doc/common/tables/cinder-emc.xml34(td)
+msgid "storage_vnx_pool_name = None"
 msgstr ""
 
-#: ./doc/common/tables/cinder-nexenta_nfs.xml35(td)
-msgid "(StrOpt) Default compression value for new ZFS folders."
-msgstr ""
-
-#: ./doc/common/tables/heat-waitcondition_api.xml8(caption)
-msgid "Description of configuration options for waitcondition_api"
-msgstr ""
-
-#: ./doc/common/tables/heat-waitcondition_api.xml22(td)
-#: ./doc/common/tables/heat-api.xml30(td)
-msgid "heat_waitcondition_server_url ="
-msgstr "heat_waitcondition_server_url ="
-
-#: ./doc/common/tables/heat-waitcondition_api.xml23(td)
-#: ./doc/common/tables/heat-api.xml31(td)
-msgid "(StrOpt) URL of the Heat waitcondition server."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml7(literal)
-msgid "[filter:bulk]"
-msgstr "[filter:bulk]"
-
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml18(td)
-msgid "use = egg:swift#bulk"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml21(td)
-msgid "max_containers_per_extraction = 10000"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml24(td)
-msgid "max_failed_extractions = 1000"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml27(td)
-msgid "max_deletes_per_request = 10000"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml30(td)
-msgid "max_failed_deletes = 1000"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml33(td)
-msgid "yield_frequency = 10"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml36(td)
-msgid "delete_container_retry_count = 0"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_vlan.xml8(caption)
-msgid "Description of configuration options for ml2_vlan"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_vlan.xml19(th)
-msgid "[ml2_type_vlan]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_vlan.xml23(td)
-msgid ""
-"(ListOpt) List of &lt;physical_network&gt;:&lt;vlan_min&gt;:&lt;vlan_max&gt;"
-" or &lt;physical_network&gt; specifying physical_network names usable for "
-"VLAN provider and tenant networks, as well as ranges of VLAN tags on each "
-"available for allocation to tenant networks."
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml22(td)
-msgid "allow_instance_snapshots = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml23(td)
-msgid "(BoolOpt) Permit instance snapshot operations."
-msgstr "(BoolOpt) Autorise les opérations de snapshots des instances"
-
-#: ./doc/common/tables/nova-policy.xml26(td)
-msgid "allow_migrate_to_same_host = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml27(td)
-msgid ""
-"(BoolOpt) Allow migrate machine to the same host. Useful when testing in "
-"single-host environments."
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml30(td)
-msgid "allow_resize_to_same_host = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml31(td)
-msgid ""
-"(BoolOpt) Allow destination machine to match source for resize. Useful when "
-"testing in single-host environments."
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml35(td)
-msgid "(IntOpt) Number of seconds between subsequent usage refreshes"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml38(td)
-msgid "max_local_block_devices = 3"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml39(td)
-msgid ""
-"(IntOpt) Maximum number of devices that will result in a local image being "
-"created on the hypervisor node. Setting this to 0 means nova will allow only"
-" boot from volume. A negative number means unlimited."
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml42(td)
-msgid "osapi_compute_unique_server_name_scope ="
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml43(td)
-msgid ""
-"(StrOpt) When set, compute API will consider duplicate hostnames invalid "
-"within the specified scope, regardless of case. Should be empty, \"project\""
-" or \"global\"."
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml47(td)
-msgid ""
-"(IntOpt) The maximum number of items returned in a single response from a "
-"collection resource"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml51(td)
-msgid "(IntOpt) The maximum body size per each osapi request(bytes)"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml54(td)
-msgid "password_length = 12"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml55(td)
-msgid "(IntOpt) Length of generated instance admin passwords"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml59(td)
-#: ./doc/common/tables/cinder-common.xml139(td)
-msgid "(StrOpt) Rule checked when requested rule is not found"
-msgstr "(StrOpt)  Règle vérifiée lorsque la règle recherchée n'existe pas"
-
-#: ./doc/common/tables/nova-policy.xml63(td)
-#: ./doc/common/tables/cinder-common.xml143(td)
-msgid "(StrOpt) JSON file representing policy"
-msgstr "(StrOpt)  Fichier JSON correspondant aux polices"
-
-#: ./doc/common/tables/nova-policy.xml67(td)
-msgid "(IntOpt) Number of seconds until a reservation expires"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml70(td)
-msgid "resize_fs_using_block_device = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml71(td)
-msgid ""
-"(BoolOpt) Attempt to resize the filesystem by accessing the image over a "
-"block device. This is done by the host and may not be necessary if the image"
-" contains a recent version of cloud-init. Possible mechanisms require the "
-"nbd driver (for qcow and raw), or loop (for raw)."
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml74(td)
-#: ./doc/common/tables/cinder-common.xml202(td)
-msgid "until_refresh = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml75(td)
-msgid "(IntOpt) Count of reservations until usage is refreshed"
-msgstr ""
-
-#: ./doc/common/tables/keystone-amqp.xml8(caption)
-#: ./doc/common/tables/glance-amqp.xml8(caption)
-#: ./doc/common/tables/heat-amqp.xml8(caption)
-#: ./doc/common/tables/ceilometer-amqp.xml8(caption)
-#: ./doc/common/tables/trove-amqp.xml8(caption)
-msgid "Description of configuration options for amqp"
-msgstr ""
-
-#: ./doc/common/tables/keystone-amqp.xml34(td)
-#: ./doc/common/tables/heat-amqp.xml38(td)
-#: ./doc/common/tables/ceilometer-exchange.xml30(td)
-#: ./doc/common/tables/nova-compute.xml58(td)
-msgid "default_publisher_id = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-amqp.xml35(td)
-#: ./doc/common/tables/neutron-notifier.xml27(td)
-#: ./doc/common/tables/heat-amqp.xml39(td)
-#: ./doc/common/tables/trove-common.xml51(td)
-#: ./doc/common/tables/ceilometer-exchange.xml31(td)
-#: ./doc/common/tables/nova-compute.xml59(td)
-msgid "(StrOpt) Default publisher_id for outgoing notifications"
-msgstr ""
-
-#: ./doc/common/tables/neutron-logging.xml26(td)
-#: ./doc/common/tables/heat-logging.xml22(td)
-#: ./doc/common/tables/trove-common.xml34(td)
-msgid ""
-"default_log_levels = amqp=WARN, amqplib=WARN, boto=WARN, qpid=WARN, "
-"sqlalchemy=WARN, suds=INFO, iso8601=WARN"
-msgstr "default_log_levels = amqp=WARN, amqplib=WARN, boto=WARN, qpid=WARN, sqlalchemy=WARN, suds=INFO, iso8601=WARN"
-
-#: ./doc/common/tables/neutron-logging.xml27(td)
-#: ./doc/common/tables/heat-logging.xml23(td)
-#: ./doc/common/tables/nova-logging.xml27(td)
-#: ./doc/common/tables/trove-common.xml35(td)
-msgid "(ListOpt) list of logger=LEVEL pairs"
-msgstr "(ListOpt) liste de loggers=paires LEVEL"
-
-#: ./doc/common/tables/neutron-logging.xml86(td)
-#: ./doc/common/tables/neutron-nec.xml58(td)
-msgid "use_ssl = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-logging.xml87(td)
-msgid "(BoolOpt) Enable SSL on the API server"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_cassandra.xml8(caption)
-msgid "Description of configuration options for db_cassandra"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_cassandra.xml19(th)
-msgid "[cassandra]"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_cassandra.xml26(td)
-msgid "mount_point = /var/lib/cassandra"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_cassandra.xml30(td)
-msgid "tcp_ports = 7000, 7001, 9042, 9160"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_cassandra.xml35(td)
-#: ./doc/common/tables/trove-db_mysql.xml39(td)
-#: ./doc/common/tables/trove-db_redis.xml35(td)
-#: ./doc/common/tables/trove-db_couchbase.xml35(td)
-#: ./doc/common/tables/trove-db_percona.xml39(td)
-msgid ""
-"(ListOpt) List of UDP ports and/or port ranges to open in the security group"
-" (only applicable if trove_security_groups_support is True)"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_cassandra.xml38(td)
-msgid "usage_timeout = 600"
-msgstr ""
-
-#: ./doc/common/tables/glance-rpc.xml22(td)
-msgid ""
-"allowed_rpc_exception_modules = openstack.common.exception, "
-"glance.common.exception, exceptions"
-msgstr ""
-
-#: ./doc/common/tables/glance-rpc.xml23(td)
-#: ./doc/common/tables/trove-rpc.xml23(td)
-msgid ""
-"(ListOpt) Modules of exceptions that are permitted to be recreatedupon "
-"receiving exception data from an rpc call."
-msgstr ""
-
-#: ./doc/common/tables/nova-authentication.xml8(caption)
-msgid "Description of configuration options for authentication"
-msgstr ""
-
-#: ./doc/common/tables/nova-authentication.xml22(td)
-#: ./doc/common/tables/glance-registry.xml38(td)
-#: ./doc/common/tables/cinder-auth.xml22(td)
-msgid "auth_strategy = noauth"
-msgstr ""
-
-#: ./doc/common/tables/nova-authentication.xml23(td)
-#: ./doc/common/tables/ceilometer-auth.xml23(td)
-msgid "(StrOpt) The strategy to use for auth: noauth or keystone."
+#: ./doc/common/tables/cinder-emc.xml35(td)
+msgid "(StrOpt) ISCSI pool name"
 msgstr ""
 
 #: ./doc/common/tables/cinder-vmware.xml26(td)
@@ -38543,116 +38348,1849 @@ msgid ""
 "location for bug work-arounds."
 msgstr ""
 
-#: ./doc/common/tables/glance-sheepdog.xml8(caption)
-msgid "Description of configuration options for sheepdog"
+#: ./doc/common/tables/neutron-ml2_flat.xml8(caption)
+msgid "Description of configuration options for ml2_flat"
 msgstr ""
 
-#: ./doc/common/tables/glance-sheepdog.xml22(td)
-msgid "sheepdog_store_address = 127.0.0.1"
+#: ./doc/common/tables/neutron-ml2_flat.xml19(th)
+msgid "[ml2_type_flat]"
 msgstr ""
 
-#: ./doc/common/tables/glance-sheepdog.xml23(td)
-msgid "(StrOpt) IP address of sheep daemon."
+#: ./doc/common/tables/neutron-ml2_flat.xml22(td)
+msgid "flat_networks ="
 msgstr ""
 
-#: ./doc/common/tables/glance-sheepdog.xml26(td)
-msgid "sheepdog_store_chunk_size = 64"
-msgstr ""
-
-#: ./doc/common/tables/glance-sheepdog.xml27(td)
+#: ./doc/common/tables/neutron-ml2_flat.xml23(td)
 msgid ""
-"(IntOpt) Images will be chunked into objects of this size (in megabytes). "
-"For best performance, this should be a power of two."
+"(ListOpt) List of physical_network names with which flat networks can be "
+"created. Use * to allow flat networks with arbitrary physical_network names."
 msgstr ""
 
-#: ./doc/common/tables/glance-sheepdog.xml30(td)
-msgid "sheepdog_store_port = 7000"
+#: ./doc/common/tables/heat-metadata_api.xml8(caption)
+msgid "Description of configuration options for metadata_api"
 msgstr ""
 
-#: ./doc/common/tables/glance-sheepdog.xml31(td)
-msgid "(IntOpt) Port of sheep daemon."
+#: ./doc/common/tables/heat-metadata_api.xml22(td)
+#: ./doc/common/tables/heat-api.xml22(td)
+msgid "heat_metadata_server_url ="
+msgstr "heat_metadata_server_url ="
+
+#: ./doc/common/tables/heat-metadata_api.xml23(td)
+#: ./doc/common/tables/heat-api.xml23(td)
+msgid "(StrOpt) URL of the Heat metadata server."
 msgstr ""
 
-#: ./doc/common/tables/keystone-notification.xml23(td)
+#: ./doc/common/tables/nova-upgrade_levels.xml8(caption)
+msgid "Description of configuration options for upgrade_levels"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml22(td)
+msgid "scheduler = nova.cells.scheduler.CellsScheduler"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml23(td)
+msgid "(StrOpt) Cells scheduler to use"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml26(th)
+#: ./doc/common/tables/nova-rpc_all.xml212(th)
+#: ./doc/common/tables/nova-rpc.xml76(th)
+msgid "[upgrade_levels]"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml29(td)
+msgid "cells = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml30(td)
+msgid "(StrOpt) Set a version cap for messages sent to local cells services"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml33(td)
+msgid "cert = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml34(td)
+msgid "(StrOpt) Set a version cap for messages sent to cert services"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml37(td)
+msgid "compute = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml38(td)
 msgid ""
-"(StrOpt) onready allows you to send a notification when the process is ready"
-" to serve For example, to have it notify using systemd, one could set shell "
-"command: \"onready = systemd-notify --ready\" or a module with notify() "
-"method: \"onready = keystone.common.systemd\"."
+"(StrOpt) Set a version cap for messages sent to compute services. If you "
+"plan to do a live upgrade from havana to icehouse, you should set this "
+"option to \"icehouse-compat\" before beginning the live upgrade procedure."
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml8(caption)
-msgid "Description of configuration options for hyperv_agent"
+#: ./doc/common/tables/nova-upgrade_levels.xml41(td)
+msgid "conductor = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml22(td)
-msgid "enable_metrics_collection = False"
+#: ./doc/common/tables/nova-upgrade_levels.xml42(td)
+msgid "(StrOpt) Set a version cap for messages sent to conductor services"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml23(td)
+#: ./doc/common/tables/nova-upgrade_levels.xml45(td)
+msgid "console = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml46(td)
+msgid "(StrOpt) Set a version cap for messages sent to console services"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml49(td)
+msgid "consoleauth = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml50(td)
+msgid "(StrOpt) Set a version cap for messages sent to consoleauth services"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml53(td)
+msgid "intercell = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml54(td)
+msgid "(StrOpt) Set a version cap for messages sent between cells services"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml57(td)
+msgid "network = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml58(td)
+msgid "(StrOpt) Set a version cap for messages sent to network services"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml61(td)
+msgid "scheduler = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml62(td)
+msgid "(StrOpt) Set a version cap for messages sent to scheduler services"
+msgstr ""
+
+#: ./doc/common/tables/neutron-kombu.xml8(caption)
+#: ./doc/common/tables/nova-kombu.xml8(caption)
+msgid "Description of configuration options for kombu"
+msgstr ""
+
+#: ./doc/common/tables/neutron-kombu.xml35(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml39(td)
 msgid ""
-"(BoolOpt) Enables metrics collections for switch ports by using Hyper-V's "
-"metric APIs. Collected data can by retrieved by other apps and services, "
-"e.g.: Ceilometer. Requires Hyper-V / Windows Server 2012 and above"
+"(StrOpt) If SSL is enabled, the SSL version to use. Valid values are TLSv1, "
+"SSLv23 and SSLv3. SSLv2 might be available on some distributions."
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml26(td)
-msgid "local_network_vswitch = private"
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml8(caption)
+msgid "Description of configuration options for netapp_cdot_iscsi"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml27(td)
-msgid "(StrOpt) Private vswitch name used for local networks"
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml38(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml38(td)
+msgid "netapp_size_multiplier = 1.2"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml30(td)
-msgid "metrics_max_retries = 100"
-msgstr ""
-
-#: ./doc/common/tables/neutron-hyperv_agent.xml31(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml39(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml39(td)
 msgid ""
-"(IntOpt) Specifies the maximum number of retries to enable Hyper-V's port "
-"metrics collection. The agent will try to enable the feature once every "
-"polling_interval period for at most metrics_max_retries or until it "
-"succeedes."
+"(FloatOpt) The quantity to be multiplied by the requested volume size to "
+"ensure enough space is available on the virtual storage server (Vserver) to "
+"fulfill the volume creation request."
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml34(td)
-msgid "physical_network_vswitch_mappings ="
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml54(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml58(td)
+msgid "netapp_vserver = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml35(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml55(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml59(td)
 msgid ""
-"(ListOpt) List of &lt;physical_network&gt;:&lt;vswitch&gt; where the "
-"physical networks can be expressed with wildcards, e.g.: .\"*:external\""
+"(StrOpt) This option specifies the virtual storage server (Vserver) name on "
+"the storage cluster on which provisioning of block storage volumes should "
+"occur. If using the NFS storage protocol, this parameter is mandatory for "
+"storage service catalog support (utilized by Cinder volume type extra_specs "
+"support). If this option is specified, the exports belonging to the Vserver "
+"will only be used for provisioning in the future. Block storage volumes on "
+"exports not belonging to the Vserver specified by this option will continue "
+"to function normally."
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml38(td)
-#: ./doc/common/tables/neutron-sdnve.xml85(td)
-msgid "polling_interval = 2"
+#: ./doc/common/tables/neutron-ml2_ofa.xml8(caption)
+msgid "Description of configuration options for ml2_ofa"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml39(td)
+#: ./doc/common/tables/neutron-ml2_ofa.xml22(td)
+msgid "ofp_listen_host ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ofa.xml23(td)
+msgid "(StrOpt) openflow listen host"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ofa.xml26(td)
+msgid "ofp_ssl_listen_port = 6633"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ofa.xml27(td)
+msgid "(IntOpt) openflow ssl listen port"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ofa.xml30(td)
+msgid "ofp_tcp_listen_port = 6633"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ofa.xml31(td)
+msgid "(IntOpt) openflow tcp listen port"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ofa.xml37(td)
+msgid "get_datapath_retry_times = 60"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ofa.xml38(td)
+msgid "(IntOpt) Number of seconds to retry acquiring an Open vSwitch datapath"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml22(td)
+msgid "admin_role = admin"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml23(td)
+msgid "(StrOpt) Role used to identify an authenticated user as administrator."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml26(td)
+msgid "allow_anonymous_access = False"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml27(td)
 msgid ""
-"(IntOpt) The number of seconds the agent will wait between polling for local"
-" device changes."
+"(BoolOpt) Allow unauthenticated users to access the API with read-only "
+"privileges. This only applies when using ContextMiddleware."
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml42(th)
-msgid "[HYPERV]"
+#: ./doc/common/tables/glance-api.xml30(td)
+msgid "default_publisher_id = image.localhost"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml50(td)
-msgid "(StrOpt) Network type for tenant networks (local, flat, vlan or none)"
+#: ./doc/common/tables/glance-api.xml31(td)
+msgid "(StrOpt) Default publisher_id for outgoing notifications."
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml56(td)
-#: ./doc/common/tables/nova-hyperv.xml30(td)
-msgid "force_hyperv_utils_v1 = False"
+#: ./doc/common/tables/glance-api.xml34(td)
+msgid "default_store = file"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml57(td)
-#: ./doc/common/tables/nova-hyperv.xml31(td)
-msgid "(BoolOpt) Force V1 WMI utility classes"
+#: ./doc/common/tables/glance-api.xml35(td)
+msgid ""
+"(StrOpt) Default scheme to use to store image data. The scheme must be "
+"registered by one of the stores defined by the 'known_stores' config option."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml38(td)
+#: ./doc/common/tables/ceilometer-api.xml22(td)
+#: ./doc/common/tables/cinder-api.xml34(td)
+msgid "enable_v1_api = True"
+msgstr "enable_v1_api = True"
+
+#: ./doc/common/tables/glance-api.xml39(td)
+msgid "(BoolOpt) Deploy the v1 OpenStack Images API."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml42(td)
+msgid "enable_v1_registry = True"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml43(td)
+msgid "(BoolOpt) Deploy the v1 OpenStack Registry API."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml46(td)
+#: ./doc/common/tables/cinder-api.xml38(td)
+msgid "enable_v2_api = True"
+msgstr "enable_v2_api = True"
+
+#: ./doc/common/tables/glance-api.xml47(td)
+msgid "(BoolOpt) Deploy the v2 OpenStack Images API."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml50(td)
+msgid "enable_v2_registry = True"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml51(td)
+msgid "(BoolOpt) Deploy the v2 OpenStack Registry API."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml54(td)
+msgid "image_size_cap = 1099511627776"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml55(td)
+msgid ""
+"(IntOpt) Maximum size of image a user can upload in bytes. Defaults to "
+"1099511627776 bytes (1 TB)."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml58(td)
+msgid "known_stores = glance.store.filesystem.Store, glance.store.http.Store"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml59(td)
+msgid ""
+"(ListOpt) List of which store classes and store class locations are "
+"currently known to glance at startup."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml62(td)
+msgid "location_strategy = location_order"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml63(td)
+msgid ""
+"(StrOpt) This value sets what strategy will be used to determine the image "
+"location order. Currently two strategies are packaged with Glance "
+"'location_order' and 'store_type'."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml66(td)
+msgid "owner_is_tenant = True"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml67(td)
+msgid ""
+"(BoolOpt) When true, this option sets the owner of an image to be the "
+"tenant. Otherwise, the owner of the image will be the authenticated user "
+"issuing the request."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml70(td)
+msgid "send_identity_headers = False"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml71(td)
+msgid ""
+"(BoolOpt) Whether to pass through headers containing user and tenant "
+"information when making requests to the registry. This allows the registry "
+"to use the context middleware without the keystoneclients' auth_token "
+"middleware, removing calls to the keystone auth service. It is recommended "
+"that when using this option, secure communication between glance api and "
+"glance registry is ensured by means other than auth_token middleware."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml74(td)
+msgid "show_multiple_locations = False"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml75(td)
+msgid ""
+"(BoolOpt) Whether to include the backend image locations in image "
+"properties. Revealing storage location can be a security risk, so use this "
+"setting with caution! The overrides show_image_direct_url."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml78(td)
+msgid "use_user_token = True"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml79(td)
+msgid ""
+"(BoolOpt) Whether to pass through the user token when making requests to the"
+" registry."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml82(th)
+msgid "[store_type_location_strategy]"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml85(td)
+msgid "store_type_preference ="
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml86(td)
+msgid ""
+"(ListOpt) The store names to use to get store preference order. The name "
+"must be registered by one of the stores defined by the 'known_stores' config"
+" option. This option will be applied when you using 'store_type' option as "
+"image location strategy defined by the 'location_strategy' config option."
+msgstr ""
+
+#: ./doc/common/tables/heat-waitcondition_api.xml8(caption)
+msgid "Description of configuration options for waitcondition_api"
+msgstr ""
+
+#: ./doc/common/tables/heat-waitcondition_api.xml22(td)
+#: ./doc/common/tables/heat-api.xml30(td)
+msgid "heat_waitcondition_server_url ="
+msgstr "heat_waitcondition_server_url ="
+
+#: ./doc/common/tables/heat-waitcondition_api.xml23(td)
+#: ./doc/common/tables/heat-api.xml31(td)
+msgid "(StrOpt) URL of the Heat waitcondition server."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml7(literal)
+msgid "[filter:gatekeeper]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml18(td)
+msgid "use = egg:swift#gatekeeper"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml21(td)
+msgid "set log_name = gatekeeper"
+msgstr ""
+
+#: ./doc/common/tables/swift-rsyncd-container.xml7(literal)
+msgid "[container]"
+msgstr "[container]"
+
+#: ./doc/common/tables/swift-rsyncd-container.xml7(literal)
+#: ./doc/common/tables/swift-rsyncd-account.xml7(literal)
+#: ./doc/common/tables/swift-rsyncd-object.xml7(literal)
+msgid "rsyncd.conf-sample"
+msgstr "rsyncd.conf-sample"
+
+#: ./doc/common/tables/swift-rsyncd-container.xml18(td)
+msgid "max connections = 4"
+msgstr ""
+
+#: ./doc/common/tables/swift-rsyncd-container.xml21(td)
+#: ./doc/common/tables/swift-rsyncd-account.xml21(td)
+#: ./doc/common/tables/swift-rsyncd-object.xml21(td)
+msgid "path = /srv/node"
+msgstr ""
+
+#: ./doc/common/tables/swift-rsyncd-container.xml24(td)
+#: ./doc/common/tables/swift-rsyncd-account.xml24(td)
+#: ./doc/common/tables/swift-rsyncd-object.xml24(td)
+msgid "read only = false"
+msgstr ""
+
+#: ./doc/common/tables/swift-rsyncd-container.xml27(td)
+msgid "lock file = /var/lock/container.lock"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml8(caption)
+msgid "Description of configuration options for storwize"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml22(td)
+msgid "storwize_svc_connection_protocol = iSCSI"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml23(td)
+msgid "(StrOpt) Connection protocol (iSCSI/FC)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml26(td)
+msgid "storwize_svc_flashcopy_timeout = 120"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml27(td)
+msgid ""
+"(IntOpt) Maximum number of seconds to wait for FlashCopy to be prepared. "
+"Maximum value is 600 seconds (10 minutes)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml30(td)
+msgid "storwize_svc_iscsi_chap_enabled = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml31(td)
+msgid ""
+"(BoolOpt) Configure CHAP authentication for iSCSI connections (Default: "
+"Enabled)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml34(td)
+msgid "storwize_svc_multihostmap_enabled = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml35(td)
+msgid "(BoolOpt) Allows vdisk to multi host mapping"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml38(td)
+msgid "storwize_svc_multipath_enabled = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml39(td)
+msgid ""
+"(BoolOpt) Connect with multipath (FC only; iSCSI multipath is controlled by "
+"Nova)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml42(td)
+msgid "storwize_svc_vol_autoexpand = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml43(td)
+msgid "(BoolOpt) Storage system autoexpand parameter for volumes (True/False)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml46(td)
+msgid "storwize_svc_vol_compression = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml47(td)
+msgid "(BoolOpt) Storage system compression option for volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml50(td)
+msgid "storwize_svc_vol_easytier = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml51(td)
+msgid "(BoolOpt) Enable Easy Tier for volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml54(td)
+msgid "storwize_svc_vol_grainsize = 256"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml55(td)
+msgid ""
+"(IntOpt) Storage system grain size parameter for volumes (32/64/128/256)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml58(td)
+msgid "storwize_svc_vol_iogrp = 0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml59(td)
+msgid "(IntOpt) The I/O group in which to allocate volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml62(td)
+msgid "storwize_svc_vol_rsize = 2"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml63(td)
+msgid ""
+"(IntOpt) Storage system space-efficiency parameter for volumes (percentage)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml66(td)
+msgid "storwize_svc_vol_warning = 0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml67(td)
+msgid ""
+"(IntOpt) Storage system threshold for volume capacity warnings (percentage)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml70(td)
+msgid "storwize_svc_volpool_name = volpool"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml71(td)
+msgid "(StrOpt) Storage system storage pool for volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml8(caption)
+msgid "Description of configuration options for hplefthand"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml22(td)
+msgid "hplefthand_api_url = None"
+msgstr "hplefthand_api_url = None"
+
+#: ./doc/common/tables/cinder-hplefthand.xml23(td)
+msgid ""
+"(StrOpt) HP LeftHand WSAPI Server Url like https://&lt;LeftHand "
+"ip&gt;:8081/lhos"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml26(td)
+msgid "hplefthand_clustername = None"
+msgstr "hplefthand_clustername = None"
+
+#: ./doc/common/tables/cinder-hplefthand.xml27(td)
+msgid "(StrOpt) HP LeftHand cluster name"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml30(td)
+msgid "hplefthand_debug = False"
+msgstr "hplefthand_debug = False"
+
+#: ./doc/common/tables/cinder-hplefthand.xml31(td)
+msgid "(BoolOpt) Enable HTTP debugging to LeftHand"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml34(td)
+msgid "hplefthand_iscsi_chap_enabled = False"
+msgstr "hplefthand_iscsi_chap_enabled = False"
+
+#: ./doc/common/tables/cinder-hplefthand.xml35(td)
+msgid ""
+"(BoolOpt) Configure CHAP authentication for iSCSI connections (Default: "
+"Disabled)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml38(td)
+msgid "hplefthand_password = None"
+msgstr "hplefthand_password = None"
+
+#: ./doc/common/tables/cinder-hplefthand.xml39(td)
+msgid "(StrOpt) HP LeftHand Super user password"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml42(td)
+msgid "hplefthand_username = None"
+msgstr "hplefthand_username = None"
+
+#: ./doc/common/tables/cinder-hplefthand.xml43(td)
+msgid "(StrOpt) HP LeftHand Super user username"
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml8(caption)
+#: ./doc/common/tables/nova-s3.xml8(caption)
+msgid "Description of configuration options for s3"
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml22(td)
+msgid "s3_store_access_key = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml23(td)
+msgid "(StrOpt) The S3 query token access key."
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml26(td)
+msgid "s3_store_bucket = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml27(td)
+msgid "(StrOpt) The S3 bucket to be used to store the Glance data."
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml30(td)
+msgid "s3_store_bucket_url_format = subdomain"
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml31(td)
+msgid ""
+"(StrOpt) The S3 calling format used to determine the bucket. Either "
+"subdomain or path can be used."
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml34(td)
+msgid "s3_store_create_bucket_on_put = False"
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml35(td)
+msgid ""
+"(BoolOpt) A boolean to determine if the S3 bucket should be created on "
+"upload if it does not exist or if an error should be returned to the user."
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml38(td)
+msgid "s3_store_host = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml39(td)
+msgid "(StrOpt) The host where the S3 server is listening."
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml42(td)
+msgid "s3_store_object_buffer_dir = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml43(td)
+msgid ""
+"(StrOpt) The local directory where uploads will be staged before they are "
+"transferred into S3."
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml46(td)
+msgid "s3_store_secret_key = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml47(td)
+msgid "(StrOpt) The S3 query token secret key."
+msgstr ""
+
+#: ./doc/common/tables/nova-rootwrap.xml22(td)
+msgid "filters_path = /etc/nova/rootwrap.d,/usr/share/nova/rootwrap"
+msgstr ""
+
+#: ./doc/common/tables/nova-rootwrap.xml35(td)
+msgid ""
+"Which syslog facility to use. Valid values include auth, authpriv, syslog, "
+"user0, user1... Default value is 'syslog'"
+msgstr ""
+
+#: ./doc/common/tables/heat-loadbalancer.xml8(caption)
+msgid "Description of configuration options for loadbalancer"
+msgstr ""
+
+#: ./doc/common/tables/heat-loadbalancer.xml22(td)
+msgid "loadbalancer_template = None"
+msgstr "loadbalancer_template = None"
+
+#: ./doc/common/tables/heat-loadbalancer.xml23(td)
+msgid "(StrOpt) Custom template for the built-in loadbalancer nested stack."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml23(td)
+msgid "(BoolOpt) Deploy the deprecated v1 API."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml27(td)
+msgid "(IntOpt) The maximum body size per request, in bytes"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml30(td)
+msgid "pipeline_cfg_file = pipeline.yaml"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml31(td)
+msgid "(StrOpt) Configuration file for pipeline definition."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml42(td)
+msgid "reserved_metadata_length = 256"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml43(td)
+msgid "(IntOpt) Limit on length of reserved metadata values."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml46(td)
+msgid "reserved_metadata_namespace = metering."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml47(td)
+msgid "(ListOpt) List of metadata prefixes reserved for metering use."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml50(th)
+msgid "[api]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml53(td)
+#: ./doc/common/tables/trove-rpc.xml26(td)
+msgid "host = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml54(td)
+msgid "(StrOpt) The listen IP for the ceilometer API server."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml57(td)
+msgid "port = 8777"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml58(td)
+msgid "(IntOpt) The port for the ceilometer API server."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml8(caption)
+msgid "Description of configuration options for exchange"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml22(td)
+msgid "cinder_control_exchange = cinder"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml23(td)
+msgid "(StrOpt) Exchange name for Cinder notifications."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml34(td)
+msgid "glance_control_exchange = glance"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml35(td)
+msgid "(StrOpt) Exchange name for Glance notifications."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml38(td)
+msgid "heat_control_exchange = heat"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml39(td)
+msgid "(StrOpt) Exchange name for Heat notifications"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml42(td)
+msgid "http_control_exchanges = ['nova', 'glance', 'neutron', 'cinder']"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml43(td)
+msgid "(MultiStrOpt) Exchanges name to listen for notifications."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml46(td)
+msgid "neutron_control_exchange = neutron"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml47(td)
+msgid "(StrOpt) Exchange name for Neutron notifications."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml50(td)
+msgid "nova_control_exchange = nova"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml51(td)
+msgid "(StrOpt) Exchange name for Nova notifications."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml54(td)
+msgid "sample_source = openstack"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml55(td)
+msgid "(StrOpt) Source for samples emitted on this instance."
+msgstr ""
+
+#: ./doc/common/tables/cinder-lvm.xml8(caption)
+msgid "Description of configuration options for lvm"
+msgstr ""
+
+#: ./doc/common/tables/cinder-lvm.xml22(td)
+msgid "lvm_mirrors = 0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-lvm.xml23(td)
+msgid ""
+"(IntOpt) If set, create lvms with multiple mirrors. Note that this requires "
+"lvm_mirrors + 2 pvs with available space"
+msgstr ""
+
+#: ./doc/common/tables/cinder-lvm.xml26(td)
+msgid "lvm_type = default"
+msgstr ""
+
+#: ./doc/common/tables/cinder-lvm.xml27(td)
+msgid "(StrOpt) Type of LVM volumes to deploy; (default or thin)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-lvm.xml30(td)
+msgid "volume_group = cinder-volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-lvm.xml31(td)
+msgid "(StrOpt) Name for the VG that will contain exported volumes"
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml8(caption)
+msgid "Description of configuration options for dns"
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml22(td)
+msgid "dns_account_id ="
+msgstr "dns_account_id ="
+
+#: ./doc/common/tables/trove-dns.xml26(td)
+msgid "dns_auth_url ="
+msgstr "dns_auth_url ="
+
+#: ./doc/common/tables/trove-dns.xml30(td)
+msgid "dns_domain_id ="
+msgstr "dns_domain_id ="
+
+#: ./doc/common/tables/trove-dns.xml34(td)
+msgid "dns_domain_name ="
+msgstr "dns_domain_name ="
+
+#: ./doc/common/tables/trove-dns.xml38(td)
+msgid "dns_driver = trove.dns.driver.DnsDriver"
+msgstr "dns_driver = trove.dns.driver.DnsDriver"
+
+#: ./doc/common/tables/trove-dns.xml42(td)
+msgid "dns_endpoint_url = 0.0.0.0"
+msgstr "dns_endpoint_url = 0.0.0.0"
+
+#: ./doc/common/tables/trove-dns.xml46(td)
+msgid "dns_hostname ="
+msgstr "dns_hostname ="
+
+#: ./doc/common/tables/trove-dns.xml50(td)
+msgid "dns_instance_entry_factory = trove.dns.driver.DnsInstanceEntryFactory"
+msgstr "dns_instance_entry_factory = trove.dns.driver.DnsInstanceEntryFactory"
+
+#: ./doc/common/tables/trove-dns.xml54(td)
+msgid "dns_management_base_url ="
+msgstr "dns_management_base_url ="
+
+#: ./doc/common/tables/trove-dns.xml58(td)
+msgid "dns_passkey ="
+msgstr "dns_passkey ="
+
+#: ./doc/common/tables/trove-dns.xml62(td)
+msgid "dns_region ="
+msgstr "dns_region ="
+
+#: ./doc/common/tables/trove-dns.xml66(td)
+msgid "dns_service_type ="
+msgstr "dns_service_type ="
+
+#: ./doc/common/tables/trove-dns.xml70(td)
+msgid "dns_time_out = 120"
+msgstr "dns_time_out = 120"
+
+#: ./doc/common/tables/trove-dns.xml74(td)
+msgid "dns_ttl = 300"
+msgstr "dns_ttl = 300"
+
+#: ./doc/common/tables/trove-dns.xml78(td)
+msgid "dns_username ="
+msgstr "dns_username ="
+
+#: ./doc/common/tables/trove-dns.xml82(td)
+msgid "trove_dns_support = False"
+msgstr "trove_dns_support = False"
+
+#: ./doc/common/tables/nova-cells.xml34(td)
+msgid "cells_config = None"
+msgstr "cells_config = None"
+
+#: ./doc/common/tables/nova-cells.xml35(td)
+msgid ""
+"(StrOpt) Configuration file from which to read cells configuration. If "
+"given, overrides reading cells from the database."
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml38(td)
+msgid "driver = nova.cells.rpc_driver.CellsRPCDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml39(td)
+msgid "(StrOpt) Cells communication driver to use"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml46(td)
+msgid "instance_update_num_instances = 1"
+msgstr "instance_update_num_instances = 1"
+
+#: ./doc/common/tables/nova-cells.xml47(td)
+msgid "(IntOpt) Number of instances to update per periodic task run"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml50(td)
+msgid "instance_updated_at_threshold = 3600"
+msgstr "instance_updated_at_threshold = 3600"
+
+#: ./doc/common/tables/nova-cells.xml51(td)
+msgid ""
+"(IntOpt) Number of seconds after an instance was updated or deleted to "
+"continue to update cells"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml58(td)
+msgid "max_hop_count = 10"
+msgstr "max_hop_count = 10"
+
+#: ./doc/common/tables/nova-cells.xml59(td)
+msgid "(IntOpt) Maximum number of hops for cells routing."
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml66(td)
+msgid "mute_weight_multiplier = -10.0"
+msgstr "mute_weight_multiplier = -10.0"
+
+#: ./doc/common/tables/nova-cells.xml67(td)
+msgid ""
+"(FloatOpt) Multiplier used to weigh mute children. (The value should be "
+"negative.)"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml70(td)
+msgid "mute_weight_value = 1000.0"
+msgstr "mute_weight_value = 1000.0"
+
+#: ./doc/common/tables/nova-cells.xml71(td)
+msgid ""
+"(FloatOpt) Weight value assigned to mute children. (The value should be "
+"positive.)"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml78(td)
+msgid "offset_weight_multiplier = 1.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml79(td)
+msgid "(FloatOpt) Multiplier used to weigh offset weigher."
+msgstr ""
+
+#: ./doc/common/tables/trove-volume.xml8(caption)
+msgid "Description of configuration options for volume"
+msgstr ""
+
+#: ./doc/common/tables/trove-volume.xml22(td)
+msgid "block_device_mapping = vdb"
+msgstr ""
+
+#: ./doc/common/tables/trove-volume.xml26(td)
+msgid "cinder_url = http://localhost:8776/v2"
+msgstr "cinder_url = http://localhost:8776/v2"
+
+#: ./doc/common/tables/trove-volume.xml30(td)
+msgid "device_path = /dev/vdb"
+msgstr "device_path = /dev/vdb"
+
+#: ./doc/common/tables/trove-volume.xml34(td)
+msgid "trove_volume_support = True"
+msgstr "trove_volume_support = True"
+
+#: ./doc/common/tables/trove-volume.xml35(td)
+msgid "(BoolOpt) Whether to provision a cinder volume for datadir."
+msgstr ""
+
+#: ./doc/common/tables/trove-volume.xml38(td)
+msgid "volume_format_timeout = 120"
+msgstr "volume_format_timeout = 120"
+
+#: ./doc/common/tables/trove-volume.xml42(td)
+msgid "volume_fstype = ext3"
+msgstr "volume_fstype = ext3"
+
+#: ./doc/common/tables/trove-volume.xml46(td)
+msgid "volume_time_out = 60"
+msgstr "volume_time_out = 60"
+
+#: ./doc/common/tables/neutron-quotas.xml8(caption)
+msgid "Description of configuration options for quotas"
+msgstr "Description des options de configuration pour les quotas"
+
+#: ./doc/common/tables/neutron-quotas.xml22(td)
+msgid "max_routes = 30"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml23(td)
+msgid "(IntOpt) Maximum number of routes"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml26(th)
+msgid "[QUOTAS]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml29(td)
+msgid "default_quota = -1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml30(td)
+msgid ""
+"(IntOpt) Default number of resource allowed per tenant. A negative value "
+"means unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml33(td)
+msgid "quota_driver = neutron.db.quota_db.DbQuotaDriver"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml34(td)
+#: ./doc/common/tables/nova-quota.xml35(td)
+msgid "(StrOpt) Default driver to use for quota checks"
+msgstr "(StrOpt)  pilote par défaut à utiliser pour vérifications de quota"
+
+#: ./doc/common/tables/neutron-quotas.xml37(td)
+msgid "quota_firewall = 1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml38(td)
+msgid ""
+"(IntOpt) Number of firewalls allowed per tenant. A negative value means "
+"unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml41(td)
+msgid "quota_firewall_policy = 1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml42(td)
+msgid ""
+"(IntOpt) Number of firewall policies allowed per tenant. A negative value "
+"means unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml45(td)
+msgid "quota_firewall_rule = -1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml46(td)
+msgid ""
+"(IntOpt) Number of firewall rules allowed per tenant. A negative value means"
+" unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml49(td)
+msgid "quota_floatingip = 50"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml50(td)
+msgid ""
+"(IntOpt) Number of floating IPs allowed per tenant. A negative value means "
+"unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml53(td)
+msgid "quota_health_monitor = -1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml54(td)
+msgid ""
+"(IntOpt) Number of health monitors allowed per tenant. A negative value "
+"means unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml57(td)
+msgid "quota_items = network, subnet, port"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml58(td)
+msgid "(ListOpt) Resource name(s) that are supported in quota features"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml61(td)
+msgid "quota_member = -1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml62(td)
+msgid ""
+"(IntOpt) Number of pool members allowed per tenant. A negative value means "
+"unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml65(td)
+msgid "quota_network = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml66(td)
+msgid ""
+"(IntOpt) Number of networks allowed per tenant.A negative value means "
+"unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml69(td)
+msgid "quota_network_gateway = 5"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml70(td)
+msgid ""
+"(IntOpt) Number of network gateways allowed per tenant, -1 for unlimited"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml73(td)
+msgid "quota_packet_filter = 100"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml74(td)
+msgid "(IntOpt) Number of packet_filters allowed per tenant, -1 for unlimited"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml77(td)
+msgid "quota_pool = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml78(td)
+msgid ""
+"(IntOpt) Number of pools allowed per tenant. A negative value means "
+"unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml81(td)
+msgid "quota_port = 50"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml82(td)
+msgid ""
+"(IntOpt) Number of ports allowed per tenant. A negative value means "
+"unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml85(td)
+msgid "quota_router = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml86(td)
+msgid ""
+"(IntOpt) Number of routers allowed per tenant. A negative value means "
+"unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml89(td)
+msgid "quota_security_group = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml90(td)
+msgid ""
+"(IntOpt) Number of security groups allowed per tenant. A negative value "
+"means unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml93(td)
+msgid "quota_security_group_rule = 100"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml94(td)
+msgid ""
+"(IntOpt) Number of security rules allowed per tenant. A negative value means"
+" unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml97(td)
+msgid "quota_subnet = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml98(td)
+msgid ""
+"(IntOpt) Number of subnets allowed per tenant, A negative value means "
+"unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml101(td)
+msgid "quota_vip = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml102(td)
+msgid ""
+"(IntOpt) Number of vips allowed per tenant. A negative value means "
+"unlimited."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml8(caption)
+msgid "Description of configuration options for storage_nfs"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml23(td)
+msgid ""
+"(StrOpt) Mount options passed to the nfs client. See section of the nfs man "
+"page for details."
+msgstr "(StrOpt) Options de montage passées au client NFS. Voir la section sur le NFS, page principale pour les détails."
+
+#: ./doc/common/tables/cinder-storage_nfs.xml27(td)
+msgid "(StrOpt) Base dir containing mount points for nfs shares."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml30(td)
+msgid "nfs_oversub_ratio = 1.0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml31(td)
+msgid ""
+"(FloatOpt) This will compare the allocated to available space on the volume "
+"destination. If the ratio exceeds this number, the destination will no "
+"longer be valid."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml34(td)
+msgid "nfs_shares_config = /etc/cinder/nfs_shares"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml35(td)
+#: ./doc/common/tables/cinder-nexenta_nfs.xml31(td)
+msgid "(StrOpt) File with the list of available nfs shares"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml38(td)
+msgid "nfs_sparsed_volumes = True"
+msgstr "nfs_sparsed_volumes = True"
+
+#: ./doc/common/tables/cinder-storage_nfs.xml39(td)
+#: ./doc/common/tables/cinder-storage_glusterfs.xml35(td)
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml63(td)
+msgid ""
+"(BoolOpt) Create volumes as sparsed files which take no space.If set to "
+"False volume is created as regular file.In such case volume creation takes a"
+" lot of time."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml42(td)
+msgid "nfs_used_ratio = 0.95"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml43(td)
+msgid ""
+"(FloatOpt) Percent of ACTUAL usage of the underlying volume before no new "
+"volumes can be allocated to the volume destination."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml26(td)
+msgid "heat_stack_user_role = heat_stack_user"
+msgstr "heat_stack_user_role = heat_stack_user"
+
+#: ./doc/common/tables/heat-api.xml27(td)
+msgid "(StrOpt) Keystone role for heat template-defined users."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml34(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml22(td)
+msgid "heat_watch_server_url ="
+msgstr "heat_watch_server_url ="
+
+#: ./doc/common/tables/heat-api.xml35(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml23(td)
+msgid "(StrOpt) URL of the Heat CloudWatch server."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml38(td)
+msgid "max_json_body_size = 1048576"
+msgstr "max_json_body_size = 1048576"
+
+#: ./doc/common/tables/heat-api.xml39(td)
+msgid ""
+"(IntOpt) Maximum raw byte size of JSON request body. Should be larger than "
+"max_template_size."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml50(td)
+msgid "secure_proxy_ssl_header = X-Forwarded-Proto"
+msgstr "secure_proxy_ssl_header = X-Forwarded-Proto"
+
+#: ./doc/common/tables/heat-api.xml51(td)
+msgid ""
+"(StrOpt) The HTTP Header that will be used to determine which the original "
+"request protocol scheme was, even if it was removed by an SSL terminator "
+"proxy."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml54(td)
+msgid "stack_action_timeout = 3600"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml55(td)
+msgid "(IntOpt) Timeout in seconds for stack action (ie. create or update)."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml58(td)
+msgid "stack_domain_admin = None"
+msgstr "stack_domain_admin = None"
+
+#: ./doc/common/tables/heat-api.xml59(td)
+msgid ""
+"(StrOpt) Keystone username, a user with roles sufficient to manage users and"
+" projects in the stack_user_domain."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml62(td)
+msgid "stack_domain_admin_password = None"
+msgstr "stack_domain_admin_password = None"
+
+#: ./doc/common/tables/heat-api.xml63(td)
+msgid "(StrOpt) Keystone password for stack_domain_admin user."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml66(td)
+msgid "stack_user_domain = None"
+msgstr "stack_user_domain = None"
+
+#: ./doc/common/tables/heat-api.xml67(td)
+msgid ""
+"(StrOpt) Keystone domain ID which contains heat template-defined users."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml70(td)
+msgid "trusts_delegated_roles = heat_stack_owner"
+msgstr "trusts_delegated_roles = heat_stack_owner"
+
+#: ./doc/common/tables/heat-api.xml71(td)
+msgid "(ListOpt) Subset of trustor roles to be delegated to heat."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml74(th)
+msgid "[auth_password]"
+msgstr "[auth_password]"
+
+#: ./doc/common/tables/heat-api.xml77(td)
+#: ./doc/common/tables/heat-api.xml88(td)
+msgid "allowed_auth_uris ="
+msgstr "allowed_auth_uris ="
+
+#: ./doc/common/tables/heat-api.xml78(td)
+#: ./doc/common/tables/heat-api.xml89(td)
+msgid ""
+"(ListOpt) Allowed keystone endpoints for auth_uri when multi_cloud is "
+"enabled. At least one endpoint needs to be specified."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml81(td)
+#: ./doc/common/tables/heat-api.xml96(td)
+msgid "multi_cloud = False"
+msgstr "multi_cloud = False"
+
+#: ./doc/common/tables/heat-api.xml82(td)
+#: ./doc/common/tables/heat-api.xml97(td)
+msgid "(BoolOpt) Allow orchestration of multiple clouds."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml85(th)
+msgid "[ec2authtoken]"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml93(td)
+msgid "(StrOpt) Authentication Endpoint URI."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml100(th)
+msgid "[heat_api]"
+msgstr "[heat_api]"
+
+#: ./doc/common/tables/heat-api.xml111(td)
+msgid "bind_port = 8004"
+msgstr "bind_port = 8004"
+
+#: ./doc/common/tables/heat-api.xml135(td)
+msgid "(StrOpt) The API paste config file to use."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml138(td)
+#: ./doc/common/tables/glance-paste.xml26(td)
+msgid "flavor = None"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml139(td)
+msgid "(StrOpt) The flavor to use."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml7(literal)
+msgid "[filter:tempurl]"
+msgstr "[filter:tempurl]"
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml18(td)
+msgid "use = egg:swift#tempurl"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml21(td)
+msgid "methods = GET HEAD PUT"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml21(td)
+msgid "HTTP methods allowed with Temporary URLs"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml24(td)
+msgid "incoming_remove_headers = x-timestamp"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml24(td)
+msgid ""
+"Headers to remove from incoming requests. Simply a whitespace delimited list"
+" of header names and names can optionally end with '*' to indicate a prefix "
+"match."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml28(td)
+msgid "incoming_allow_headers ="
+msgstr "incoming_allow_headers ="
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml28(td)
+msgid ""
+"Headers allowed as exceptions to incoming_remove_headers. Simply a "
+"whitespace delimited list of header names and names can optionally end with "
+"'*' to indicate a prefix match."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml33(td)
+msgid "outgoing_remove_headers = x-object-meta-*"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml33(td)
+msgid ""
+"Headers to remove from outgoing responses. Simply a whitespace delimited "
+"list of header names and names can optionally end with '*' to indicate a "
+"prefix match."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml38(td)
+msgid "outgoing_allow_headers = x-object-meta-public-*"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml38(td)
+msgid ""
+"Headers allowed as exceptions to outgoing_allow_headers. Simply a whitespace"
+" delimited list of header names and names can optionally end with '*' to "
+"indicate a prefix match."
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_ceilometer.xml8(caption)
+msgid "Description of configuration options for clients_ceilometer"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_ceilometer.xml19(th)
+msgid "[clients_ceilometer]"
+msgstr "[clients_ceilometer]"
+
+#: ./doc/common/tables/neutron-ryu.xml8(caption)
+msgid "Description of configuration options for ryu"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml22(td)
+msgid "openflow_rest_api = 127.0.0.1:8080"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml23(td)
+msgid "(StrOpt) OpenFlow REST API location"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml26(td)
+msgid "ovsdb_interface = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml27(td)
+msgid "(StrOpt) OVSDB interface to connect to"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml30(td)
+msgid "ovsdb_ip = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml31(td)
+msgid "(StrOpt) OVSDB IP to connect to"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml34(td)
+msgid "ovsdb_port = 6634"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml35(td)
+msgid "(IntOpt) OVSDB port to connect to"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml38(td)
+msgid "tunnel_interface = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml39(td)
+msgid "(StrOpt) Tunnel interface to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml42(td)
+msgid "tunnel_ip = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml43(td)
+msgid "(StrOpt) Tunnel IP to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml46(td)
+msgid "tunnel_key_max = 16777215"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml47(td)
+msgid "(IntOpt) Maximum tunnel ID to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml50(td)
+msgid "tunnel_key_min = 1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml51(td)
+msgid "(IntOpt) Minimum tunnel ID to use"
+msgstr ""
+
+#: ./doc/common/tables/swift-rsyncd-account.xml7(literal)
+msgid "[account]"
+msgstr ""
+
+#: ./doc/common/tables/swift-rsyncd-account.xml18(td)
+msgid "max connections = 2"
+msgstr ""
+
+#: ./doc/common/tables/swift-rsyncd-account.xml27(td)
+msgid "lock file = /var/lock/account.lock"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metering_agent.xml8(caption)
+msgid "Description of configuration options for metering_agent"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metering_agent.xml22(td)
+msgid ""
+"driver = "
+"neutron.services.metering.drivers.noop.noop_driver.NoopMeteringDriver"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metering_agent.xml23(td)
+msgid "(StrOpt) Metering driver"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metering_agent.xml26(td)
+msgid "measure_interval = 30"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metering_agent.xml27(td)
+msgid "(IntOpt) Interval between two metering measures"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metering_agent.xml33(td)
+msgid "report_interval = 30"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metering_agent.xml34(td)
+msgid ""
+"(FloatOpt) Seconds between nodes reporting state to server; should be less "
+"than agent_down_time, best if it is half or less than agent_down_time."
+msgstr ""
+
+#: ./doc/common/tables/neutron-zeromq.xml38(td)
+msgid ""
+"rpc_zmq_matchmaker = "
+"neutron.openstack.common.rpc.matchmaker.MatchMakerLocalhost"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_glusterfs.xml8(caption)
+msgid "Description of configuration options for storage_glusterfs"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_glusterfs.xml23(td)
+msgid "(StrOpt) Base dir containing mount points for gluster shares."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_glusterfs.xml26(td)
+msgid "glusterfs_qcow2_volumes = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_glusterfs.xml27(td)
+msgid "(BoolOpt) Create volumes as QCOW2 files rather than raw files."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_glusterfs.xml30(td)
+msgid "glusterfs_shares_config = /etc/cinder/glusterfs_shares"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_glusterfs.xml31(td)
+msgid "(StrOpt) File with the list of available gluster shares"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_glusterfs.xml34(td)
+msgid "glusterfs_sparsed_volumes = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml22(td)
+msgid "compute_api_class = cinder.compute.nova.API"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml23(td)
+msgid "(StrOpt) The full class name of the compute API class to use"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml30(td)
+msgid "default_availability_zone = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml31(td)
+msgid ""
+"(StrOpt) default availability zone to use when creating a new volume. If "
+"this is not set then we use the value from the storage_availability_zone "
+"option as the default availability_zone for new volumes."
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml34(td)
+msgid ""
+"default_log_levels = amqp=WARN, amqplib=WARN, boto=WARN, qpid=WARN, "
+"sqlalchemy=WARN, suds=INFO, oslo.messaging=INFO, iso8601=WARN, "
+"requests.packages.urllib3.connectionpool=WARN"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml38(td)
+msgid "default_volume_type = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml39(td)
+msgid "(StrOpt) default volume type to use"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml46(td)
+#: ./doc/common/tables/nova-api.xml26(td)
+msgid "enable_new_services = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml47(td)
+#: ./doc/common/tables/nova-api.xml27(td)
+msgid "(BoolOpt) Services to be added to the available pool on create"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml54(td)
+#: ./doc/common/tables/nova-logging.xml34(td)
+msgid "fatal_exception_format_errors = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml55(td)
+msgid "(BoolOpt) make exception message format errors fatal"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml59(td)
+msgid ""
+"(StrOpt) Name of this node. This can be an opaque identifier. It is not "
+"necessarily a hostname, FQDN, or IP address."
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml62(td)
+msgid "iet_conf = /etc/iet/ietd.conf"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml63(td)
+msgid "(StrOpt) IET configuration file"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml66(td)
+msgid "lio_initiator_iqns ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml67(td)
+msgid ""
+"(StrOpt) Comma-separated list of initiator IQNs allowed to connect to the "
+"iSCSI target. (From Nova compute nodes.)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml71(td)
+msgid "(StrOpt) Directory to use for lock files. Default to a temp directory"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml111(td)
+msgid "(BoolOpt) Enable monkey patching"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml114(td)
+msgid "monkey_patch_modules ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml119(td)
+msgid "(StrOpt) ip address of this host"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml122(td)
+msgid "no_snapshot_gb_quota = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml123(td)
+msgid "(BoolOpt) Whether snapshots count against GigaByte quota"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml126(td)
+msgid "num_shell_tries = 3"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml127(td)
+msgid "(IntOpt) number of times to attempt to run flakey shell commands"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml131(td)
+msgid ""
+"(IntOpt) range of seconds to randomly delay when starting the periodic task "
+"scheduler to reduce stampeding. (Disable by setting to 0)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml135(td)
+msgid "(IntOpt) seconds between running periodic tasks"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml147(td)
+msgid "(IntOpt) seconds between nodes reporting state to datastore"
+msgstr "(IntOpt) secondes entre les nœuds rapportant sur l'état au datastore"
+
+#: ./doc/common/tables/cinder-common.xml150(td)
+msgid "reserved_percentage = 0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml151(td)
+msgid "(IntOpt) The percentage of backend capacity is reserved"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml154(td)
+msgid "rootwrap_config = /etc/cinder/rootwrap.conf"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml163(td)
+msgid "(IntOpt) maximum time since last check-in for up service"
+msgstr "(IntOpt) durée maximale depuis le dernier enregistrement pour le service en place"
+
+#: ./doc/common/tables/cinder-common.xml166(td)
+msgid "sqlite_db = cinder.sqlite"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml167(td)
+#: ./doc/common/tables/heat-database.xml27(td)
+msgid "(StrOpt) the filename to use with sqlite"
+msgstr "(StrOpt)  Le nom de fichier à utiliser avec sqlite"
+
+#: ./doc/common/tables/cinder-common.xml171(td)
+#: ./doc/common/tables/heat-database.xml31(td)
+msgid "(BoolOpt) If true, use synchronous mode for sqlite"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml174(td)
+#: ./doc/common/tables/neutron-ssl.xml22(td)
+#: ./doc/common/tables/nova-wsgi.xml26(td)
+msgid "ssl_ca_file = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml178(td)
+#: ./doc/common/tables/neutron-ssl.xml26(td)
+#: ./doc/common/tables/nova-wsgi.xml30(td)
+msgid "ssl_cert_file = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml182(td)
+#: ./doc/common/tables/neutron-ssl.xml30(td)
+#: ./doc/common/tables/nova-wsgi.xml34(td)
+msgid "ssl_key_file = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml186(td)
+msgid "state_path = /var/lib/cinder"
+msgstr "state_path = /var/lib/cinder"
+
+#: ./doc/common/tables/cinder-common.xml187(td)
+msgid "(StrOpt) Top-level directory for maintaining cinder's state"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml190(td)
+msgid "storage_availability_zone = nova"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml191(td)
+msgid "(StrOpt) availability zone of this node"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml203(td)
+msgid "(IntOpt) count of reservations until usage is refreshed"
+msgstr "(IntOpt) compter les réservations jusqu'à ce que l'utilisation soit rafraîchie"
+
+#: ./doc/common/tables/cinder-common.xml206(td)
+#: ./doc/common/tables/nova-api.xml94(td)
+msgid "use_forwarded_for = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml207(td)
+#: ./doc/common/tables/nova-api.xml95(td)
+msgid ""
+"(BoolOpt) Treat X-Forwarded-For as the canonical remote address. Only enable"
+" this if you have a sanitizing proxy."
+msgstr "(BoolOpt) Traiter X-Forwarded-For comme l'adresse distante canonique. Seulement activer cette option si vous avez un proxy de désinfection."
+
+#: ./doc/common/tables/cinder-common.xml230(td)
+#: ./doc/common/tables/heat-database.xml54(td)
+msgid "(IntOpt) timeout before idle sql connections are reaped"
+msgstr "(IntOpt) délai d'attente avant que les connexions SQL inactives ne soient réclamées"
+
+#: ./doc/common/tables/cinder-common.xml234(td)
+#: ./doc/common/tables/heat-database.xml78(td)
+msgid "(IntOpt) interval between retries of opening a sql connection"
+msgstr "(IntOpt) Intervalle entre les nouvelles tentatives d’ouverture d’une connexion  sql"
+
+#: ./doc/common/tables/cinder-common.xml237(td)
+msgid "use_tpool = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml238(td)
+msgid ""
+"(BoolOpt) Enable the experimental use of thread pooling for all DB API calls"
+msgstr ""
+
+#: ./doc/common/tables/glance-swift.xml8(caption)
+#: ./doc/common/tables/ceilometer-swift.xml8(caption)
+#: ./doc/common/tables/trove-swift.xml8(caption)
+msgid "Description of configuration options for swift"
 msgstr ""
 
 #: ./doc/common/tables/glance-swift.xml22(td)
@@ -38825,215 +40363,3558 @@ msgid ""
 "(StrOpt) The user to authenticate against the Swift authentication service."
 msgstr ""
 
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml21(td)
-msgid "bind_port = 6002"
+#: ./doc/common/tables/trove-quota.xml22(td)
+msgid "max_accepted_volume_size = 5"
+msgstr ""
+
+#: ./doc/common/tables/trove-quota.xml23(td)
+msgid "(IntOpt) Default maximum volume size for an instance."
+msgstr ""
+
+#: ./doc/common/tables/trove-quota.xml26(td)
+msgid "max_backups_per_user = 50"
+msgstr ""
+
+#: ./doc/common/tables/trove-quota.xml27(td)
+msgid "(IntOpt) Default maximum number of backups created by a tenant."
+msgstr ""
+
+#: ./doc/common/tables/trove-quota.xml30(td)
+msgid "max_instances_per_user = 5"
+msgstr ""
+
+#: ./doc/common/tables/trove-quota.xml31(td)
+msgid "(IntOpt) Default maximum number of instances per tenant."
+msgstr ""
+
+#: ./doc/common/tables/trove-quota.xml34(td)
+msgid "max_volumes_per_user = 20"
+msgstr ""
+
+#: ./doc/common/tables/trove-quota.xml35(td)
+msgid ""
+"(IntOpt) Default maximum volume capacity (in GB) spanning across all trove "
+"volumes per tenant"
+msgstr ""
+
+#: ./doc/common/tables/trove-quota.xml38(td)
+msgid "quota_driver = trove.quota.quota.DbQuotaDriver"
+msgstr ""
+
+#: ./doc/common/tables/trove-quota.xml39(td)
+msgid "(StrOpt) Default driver to use for quota checks."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml8(caption)
+msgid "Description of configuration options for alarm"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml19(th)
+msgid "[alarm]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml22(td)
+msgid "evaluation_interval = 60"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml23(td)
+msgid ""
+"(IntOpt) Period of evaluation cycle, should be &gt;= than configured "
+"pipeline interval for collection of underlying metrics."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml26(td)
+msgid "evaluation_service = ceilometer.alarm.service.SingletonAlarmService"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml27(td)
+msgid "(StrOpt) Class to launch as alarm evaluation service."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml30(td)
+msgid "notifier_rpc_topic = alarm_notifier"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml31(td)
+msgid "(StrOpt) The topic that ceilometer uses for alarm notifier messages."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml34(td)
+msgid "partition_rpc_topic = alarm_partition_coordination"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml35(td)
+msgid ""
+"(StrOpt) The topic that ceilometer uses for alarm partition coordination "
+"messages."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml38(td)
+msgid "record_history = True"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml39(td)
+msgid "(BoolOpt) Record alarm change events."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml42(td)
+msgid "rest_notifier_certificate_file ="
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml43(td)
+msgid "(StrOpt) SSL Client certificate for REST notifier."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml46(td)
+msgid "rest_notifier_certificate_key ="
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml47(td)
+msgid "(StrOpt) SSL Client private key for REST notifier."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml50(td)
+msgid "rest_notifier_ssl_verify = True"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml51(td)
+msgid ""
+"(BoolOpt) Whether to verify the SSL Server certificate when calling alarm "
+"action."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml8(caption)
+msgid "Description of configuration options for events"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml19(th)
+msgid "[event]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml22(td)
+msgid "definitions_cfg_file = event_definitions.yaml"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml23(td)
+msgid "(StrOpt) Configuration file for event definitions."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml26(td)
+msgid "drop_unmatched_notifications = False"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml27(td)
+msgid ""
+"(BoolOpt) Drop notifications if no event definition matches. (Otherwise, we "
+"convert them with just the default traits)"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml30(th)
+msgid "[notification]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml33(td)
+msgid "ack_on_event_error = True"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml34(td)
+msgid "(BoolOpt) Acknowledge message when event persistence fails."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml37(td)
+msgid "store_events = False"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml38(td)
+msgid "(BoolOpt) Save event details."
+msgstr ""
+
+#: ./doc/common/tables/cinder-xiv.xml8(caption)
+msgid "Description of configuration options for xiv"
+msgstr ""
+
+#: ./doc/common/tables/cinder-xiv.xml22(td)
+msgid "xiv_chap = disabled"
+msgstr ""
+
+#: ./doc/common/tables/cinder-xiv.xml23(td)
+msgid ""
+"(StrOpt) CHAP authentication mode, effective only for iscsi "
+"(disabled|enabled)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-xiv.xml26(td)
+msgid "xiv_ds8k_connection_type = iscsi"
+msgstr ""
+
+#: ./doc/common/tables/cinder-xiv.xml27(td)
+msgid ""
+"(StrOpt) Connection type to the IBM Storage Array (fibre_channel|iscsi)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-xiv.xml30(td)
+msgid "xiv_ds8k_proxy = xiv_ds8k_openstack.nova_proxy.XIVDS8KNovaProxy"
+msgstr ""
+
+#: ./doc/common/tables/cinder-xiv.xml31(td)
+msgid "(StrOpt) Proxy driver that connects to the IBM Storage Array"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml7(literal)
+msgid "[filter:name_check]"
+msgstr "[filter:name_check]"
+
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml18(td)
+msgid "use = egg:swift#name_check"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml21(td)
+msgid "forbidden_chars = '\"`&lt;&gt;"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml21(td)
+msgid "Characters that are not allowed in a name"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml24(td)
+msgid "maximum_length = 255"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml24(td)
+msgid "Maximum length of a name"
+msgstr "Longueur maximum d'un nom"
+
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml27(td)
+msgid "forbidden_regexp = /\\./|/\\.\\./|/\\.$|/\\.\\.$"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml27(td)
+msgid "Substrings to forbid, using regular expression syntax"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml8(caption)
+msgid "Description of configuration options for ml2_bigswitch"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml19(th)
+#: ./doc/common/tables/neutron-bigswitch.xml19(th)
+msgid "[NOVA]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml22(td)
+#: ./doc/common/tables/neutron-bigswitch.xml22(td)
+msgid "node_override_vif_802.1qbg ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml23(td)
+#: ./doc/common/tables/neutron-bigswitch.xml23(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to 802.1qbg"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml26(td)
+#: ./doc/common/tables/neutron-bigswitch.xml26(td)
+msgid "node_override_vif_802.1qbh ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml27(td)
+#: ./doc/common/tables/neutron-bigswitch.xml27(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to 802.1qbh"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml30(td)
+#: ./doc/common/tables/neutron-bigswitch.xml30(td)
+msgid "node_override_vif_binding_failed ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml31(td)
+#: ./doc/common/tables/neutron-bigswitch.xml31(td)
+msgid ""
+"(ListOpt) Nova compute nodes to manually set VIF type to binding_failed"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml34(td)
+#: ./doc/common/tables/neutron-bigswitch.xml34(td)
+msgid "node_override_vif_bridge ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml35(td)
+#: ./doc/common/tables/neutron-bigswitch.xml35(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to bridge"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml38(td)
+#: ./doc/common/tables/neutron-bigswitch.xml38(td)
+msgid "node_override_vif_hostdev ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml39(td)
+#: ./doc/common/tables/neutron-bigswitch.xml39(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to hostdev"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml42(td)
+#: ./doc/common/tables/neutron-bigswitch.xml42(td)
+msgid "node_override_vif_hyperv ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml43(td)
+#: ./doc/common/tables/neutron-bigswitch.xml43(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to hyperv"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml46(td)
+#: ./doc/common/tables/neutron-bigswitch.xml46(td)
+msgid "node_override_vif_ivs ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml47(td)
+#: ./doc/common/tables/neutron-bigswitch.xml47(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to ivs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml50(td)
+#: ./doc/common/tables/neutron-bigswitch.xml50(td)
+msgid "node_override_vif_midonet ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml51(td)
+#: ./doc/common/tables/neutron-bigswitch.xml51(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to midonet"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml54(td)
+#: ./doc/common/tables/neutron-bigswitch.xml54(td)
+msgid "node_override_vif_mlnx_direct ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml55(td)
+#: ./doc/common/tables/neutron-bigswitch.xml55(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to mlnx_direct"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml58(td)
+#: ./doc/common/tables/neutron-bigswitch.xml58(td)
+msgid "node_override_vif_other ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml59(td)
+#: ./doc/common/tables/neutron-bigswitch.xml59(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to other"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml62(td)
+#: ./doc/common/tables/neutron-bigswitch.xml62(td)
+msgid "node_override_vif_ovs ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml63(td)
+#: ./doc/common/tables/neutron-bigswitch.xml63(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to ovs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml66(td)
+#: ./doc/common/tables/neutron-bigswitch.xml66(td)
+msgid "node_override_vif_unbound ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml67(td)
+#: ./doc/common/tables/neutron-bigswitch.xml67(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to unbound"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml70(td)
+#: ./doc/common/tables/neutron-bigswitch.xml70(td)
+msgid "vif_type = ovs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml71(td)
+#: ./doc/common/tables/neutron-bigswitch.xml71(td)
+msgid "(StrOpt) Virtual interface type to configure on Nova compute nodes"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml74(td)
+#: ./doc/common/tables/neutron-bigswitch.xml74(td)
+msgid ""
+"vif_types = unbound, binding_failed, ovs, ivs, bridge, 802.1qbg, 802.1qbh, "
+"hyperv, midonet, mlnx_direct, hostdev, other"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml75(td)
+#: ./doc/common/tables/neutron-bigswitch.xml75(td)
+msgid "(ListOpt) List of allowed vif_type values."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml78(th)
+#: ./doc/common/tables/neutron-nuage.xml19(th)
+#: ./doc/common/tables/neutron-bigswitch.xml78(th)
+msgid "[RESTPROXY]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml81(td)
+#: ./doc/common/tables/neutron-bigswitch.xml81(td)
+msgid "add_meta_server_route = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml82(td)
+#: ./doc/common/tables/neutron-bigswitch.xml82(td)
+msgid ""
+"(BoolOpt) Flag to decide if a route to the metadata server should be "
+"injected into the VM"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml85(td)
+#: ./doc/common/tables/neutron-bigswitch.xml85(td)
+msgid "auto_sync_on_failure = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml86(td)
+#: ./doc/common/tables/neutron-bigswitch.xml86(td)
+msgid ""
+"(BoolOpt) If neutron fails to create a resource because the backend "
+"controller doesn't know of a dependency, the plugin automatically triggers a"
+" full data synchronization to the controller."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml89(td)
+#: ./doc/common/tables/neutron-bigswitch.xml89(td)
+msgid "cache_connections = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml90(td)
+#: ./doc/common/tables/neutron-bigswitch.xml90(td)
+msgid "(BoolOpt) Re-use HTTP/HTTPS connections to the controller."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml93(td)
+#: ./doc/common/tables/neutron-bigswitch.xml93(td)
+msgid "consistency_interval = 60"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml94(td)
+#: ./doc/common/tables/neutron-bigswitch.xml94(td)
+msgid ""
+"(IntOpt) Time between verifications that the backend controller database is "
+"consistent with Neutron"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml97(td)
+#: ./doc/common/tables/neutron-bigswitch.xml97(td)
+msgid "neutron_id = neutron-oslo"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml98(td)
+#: ./doc/common/tables/neutron-bigswitch.xml98(td)
+msgid "(StrOpt) User defined identifier for this Neutron deployment"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml101(td)
+#: ./doc/common/tables/neutron-bigswitch.xml101(td)
+msgid "no_ssl_validation = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml102(td)
+#: ./doc/common/tables/neutron-bigswitch.xml102(td)
+msgid "(BoolOpt) Disables SSL certificate validation for controllers"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml105(td)
+#: ./doc/common/tables/neutron-bigswitch.xml105(td)
+msgid "server_auth = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml106(td)
+#: ./doc/common/tables/neutron-bigswitch.xml106(td)
+msgid ""
+"(StrOpt) The username and password for authenticating against the Big Switch"
+" or Floodlight controller."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml109(td)
+#: ./doc/common/tables/neutron-bigswitch.xml109(td)
+msgid "server_ssl = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml110(td)
+#: ./doc/common/tables/neutron-bigswitch.xml110(td)
+msgid ""
+"(BoolOpt) If True, Use SSL when connecting to the Big Switch or Floodlight "
+"controller."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml113(td)
+#: ./doc/common/tables/neutron-bigswitch.xml113(td)
+msgid "server_timeout = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml114(td)
+#: ./doc/common/tables/neutron-bigswitch.xml114(td)
+msgid ""
+"(IntOpt) Maximum number of seconds to wait for proxy request to connect and "
+"complete."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml117(td)
+#: ./doc/common/tables/neutron-bigswitch.xml117(td)
+msgid "servers = localhost:8800"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml118(td)
+#: ./doc/common/tables/neutron-bigswitch.xml118(td)
+msgid ""
+"(ListOpt) A comma separated list of Big Switch or Floodlight servers and "
+"port numbers. The plugin proxies the requests to the Big Switch/Floodlight "
+"server, which performs the networking configuration. Only oneserver is "
+"needed per deployment, but you may wish todeploy multiple servers to support"
+" failover."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml121(td)
+#: ./doc/common/tables/neutron-bigswitch.xml121(td)
+msgid "ssl_cert_directory = /etc/neutron/plugins/bigswitch/ssl"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml122(td)
+#: ./doc/common/tables/neutron-bigswitch.xml122(td)
+msgid ""
+"(StrOpt) Directory containing ca_certs and host_certs certificate "
+"directories."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml125(td)
+#: ./doc/common/tables/neutron-bigswitch.xml125(td)
+msgid "ssl_sticky = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml126(td)
+#: ./doc/common/tables/neutron-bigswitch.xml126(td)
+msgid ""
+"(BoolOpt) Trust and store the first certificate received for each controller"
+" address and use it to validate future connections to that address."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml129(td)
+#: ./doc/common/tables/neutron-bigswitch.xml129(td)
+msgid "sync_data = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml130(td)
+#: ./doc/common/tables/neutron-bigswitch.xml130(td)
+msgid "(BoolOpt) Sync data on connect"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml133(td)
+#: ./doc/common/tables/neutron-bigswitch.xml133(td)
+msgid "thread_pool_size = 4"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml134(td)
+#: ./doc/common/tables/neutron-bigswitch.xml134(td)
+msgid ""
+"(IntOpt) Maximum number of threads to spawn to handle large volumes of port "
+"creations."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml137(th)
+#: ./doc/common/tables/neutron-bigswitch.xml137(th)
+msgid "[RESTPROXYAGENT]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml141(td)
+#: ./doc/common/tables/neutron-bigswitch.xml141(td)
+msgid ""
+"(StrOpt) Name of integration bridge on compute nodes used for security group"
+" insertion."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml144(td)
+#: ./doc/common/tables/neutron-bigswitch.xml144(td)
+msgid "polling_interval = 5"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml145(td)
+#: ./doc/common/tables/neutron-bigswitch.xml145(td)
+msgid "(IntOpt) Seconds between agent checks for port changes"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml148(td)
+#: ./doc/common/tables/neutron-bigswitch.xml148(td)
+msgid "virtual_switch_type = ovs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml149(td)
+#: ./doc/common/tables/neutron-bigswitch.xml149(td)
+msgid "(StrOpt) Virtual switch type."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml152(th)
+#: ./doc/common/tables/neutron-bigswitch.xml152(th)
+msgid "[ROUTER]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml155(td)
+#: ./doc/common/tables/neutron-bigswitch.xml155(td)
+msgid "max_router_rules = 200"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml156(td)
+#: ./doc/common/tables/neutron-bigswitch.xml156(td)
+msgid "(IntOpt) Maximum number of router rules"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml159(td)
+#: ./doc/common/tables/neutron-bigswitch.xml159(td)
+msgid "tenant_default_router_rule = ['*:any:any:permit']"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml160(td)
+#: ./doc/common/tables/neutron-bigswitch.xml160(td)
+msgid ""
+"(MultiStrOpt) The default router rules installed in new tenant routers. "
+"Repeat the config option for each rule. Format is "
+"&lt;tenant&gt;:&lt;source&gt;:&lt;destination&gt;:&lt;action&gt; Use an * to"
+" specify default for all tenants."
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml8(caption)
+msgid "Description of configuration options for glance"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml22(td)
+#: ./doc/common/tables/cinder-images.xml22(td)
+msgid "allowed_direct_url_schemes ="
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml23(td)
+msgid ""
+"(ListOpt) A list of url scheme that can be downloaded directly via the "
+"direct_url. Currently supported schemes: [file]."
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml26(td)
+#: ./doc/common/tables/cinder-images.xml26(td)
+msgid "glance_api_insecure = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml27(td)
+#: ./doc/common/tables/cinder-images.xml27(td)
+msgid "(BoolOpt) Allow to perform insecure SSL (https) requests to glance"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml30(td)
+#: ./doc/common/tables/cinder-images.xml30(td)
+msgid "glance_api_servers = $glance_host:$glance_port"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml31(td)
+msgid ""
+"(ListOpt) A list of the glance api servers available to nova. Prefix with "
+"https:// for ssl-based glance api servers. ([hostname|ip]:port)"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml34(td)
+#: ./doc/common/tables/cinder-images.xml42(td)
+msgid "glance_host = $my_ip"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml35(td)
+msgid "(StrOpt) Default glance hostname or IP address"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml38(td)
+#: ./doc/common/tables/cinder-images.xml46(td)
+msgid "glance_num_retries = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml39(td)
+msgid "(IntOpt) Number of retries when downloading an image from glance"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml42(td)
+#: ./doc/common/tables/cinder-images.xml50(td)
+msgid "glance_port = 9292"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml43(td)
+msgid "(IntOpt) Default glance port"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml46(td)
+msgid "glance_protocol = http"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml47(td)
+msgid ""
+"(StrOpt) Default protocol to use when connecting to glance. Set to https for"
+" SSL."
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml50(td)
+msgid "osapi_glance_link_prefix = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml51(td)
+msgid ""
+"(StrOpt) Base URL that will be presented to users in links to glance "
+"resources"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml54(th)
+msgid "[image_file_url]"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml57(td)
+msgid "filesystems ="
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml58(td)
+msgid ""
+"(ListOpt) List of file systems that are configured in this file in the "
+"image_file_url:&lt;list entry name&gt; sections"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml22(td)
+msgid "buckets_path = $state_path/buckets"
+msgstr "buckets_path = $state_path/buckets"
+
+#: ./doc/common/tables/nova-s3.xml23(td)
+msgid "(StrOpt) Path to S3 buckets"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml26(td)
+msgid "image_decryption_dir = /tmp"
+msgstr "image_decryption_dir = /tmp"
+
+#: ./doc/common/tables/nova-s3.xml27(td)
+msgid "(StrOpt) Parent directory for tempdir used for image decryption"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml30(td)
+msgid "s3_access_key = notchecked"
+msgstr "s3_access_key = notchecked"
+
+#: ./doc/common/tables/nova-s3.xml31(td)
+msgid "(StrOpt) Access key to use for S3 server for images"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml34(td)
+msgid "s3_affix_tenant = False"
+msgstr "s3_affix_tenant = False"
+
+#: ./doc/common/tables/nova-s3.xml35(td)
+msgid ""
+"(BoolOpt) Whether to affix the tenant id to the access key when downloading "
+"from S3"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml38(td)
+msgid "s3_host = $my_ip"
+msgstr "s3_host = $my_ip"
+
+#: ./doc/common/tables/nova-s3.xml39(td)
+msgid "(StrOpt) Hostname or IP for OpenStack to use when accessing the S3 api"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml42(td)
+msgid "s3_listen = 0.0.0.0"
+msgstr "s3_listen = 0.0.0.0"
+
+#: ./doc/common/tables/nova-s3.xml43(td)
+msgid "(StrOpt) IP address for S3 API to listen"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml46(td)
+msgid "s3_listen_port = 3333"
+msgstr "s3_listen_port = 3333"
+
+#: ./doc/common/tables/nova-s3.xml47(td)
+msgid "(IntOpt) Port for S3 API to listen"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml50(td)
+msgid "s3_port = 3333"
+msgstr "s3_port = 3333"
+
+#: ./doc/common/tables/nova-s3.xml51(td)
+msgid "(IntOpt) Port used when accessing the S3 api"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml54(td)
+msgid "s3_secret_key = notchecked"
+msgstr "s3_secret_key = notchecked"
+
+#: ./doc/common/tables/nova-s3.xml55(td)
+msgid "(StrOpt) Secret key to use for S3 server for images"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml58(td)
+msgid "s3_use_ssl = False"
+msgstr "s3_use_ssl = False"
+
+#: ./doc/common/tables/nova-s3.xml59(td)
+msgid "(BoolOpt) Whether to use SSL when talking to S3"
+msgstr ""
+
+#: ./doc/common/tables/nova-pci.xml8(caption)
+msgid "Description of configuration options for pci"
+msgstr ""
+
+#: ./doc/common/tables/nova-pci.xml22(td)
+msgid "pci_alias = []"
+msgstr ""
+
+#: ./doc/common/tables/nova-pci.xml23(td)
+msgid ""
+"(MultiStrOpt) An alias for a PCI passthrough device requirement. This allows"
+" users to specify the alias in the extra_spec for a flavor, without needing "
+"to repeat all the PCI property requirements. For example: pci_alias = { "
+"\"name\": \"QuicAssist\", \"product_id\": \"0443\", \"vendor_id\": \"8086\","
+" \"device_type\": \"ACCEL\" } defines an alias for the Intel QuickAssist "
+"card. (multi valued)"
+msgstr ""
+
+#: ./doc/common/tables/nova-pci.xml26(td)
+msgid "pci_passthrough_whitelist = []"
+msgstr ""
+
+#: ./doc/common/tables/nova-pci.xml27(td)
+msgid ""
+"(MultiStrOpt) White list of PCI devices available to VMs. For example: "
+"pci_passthrough_whitelist = [{\"vendor_id\": \"8086\", \"product_id\": "
+"\"0443\"}]"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_cinder.xml8(caption)
+msgid "Description of configuration options for clients_cinder"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_cinder.xml19(th)
+msgid "[clients_cinder]"
+msgstr "[clients_cinder]"
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml7(literal)
+msgid "[filter:ratelimit]"
+msgstr "[filter:ratelimit]"
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml18(td)
+msgid "use = egg:swift#ratelimit"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml21(td)
+msgid "set log_name = ratelimit"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml36(td)
+msgid "clock_accuracy = 1000"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml36(td)
+msgid ""
+"Represents how accurate the proxy servers' system clocks are with each "
+"other. 1000 means that all the proxies' clock are accurate to each other "
+"within 1 millisecond. No ratelimit should be higher than the clock accuracy."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml39(td)
+msgid "max_sleep_time_seconds = 60"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml39(td)
+msgid ""
+"App will immediately return a 498 response if the necessary sleep time ever "
+"exceeds the given max_sleep_time_seconds."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml42(td)
+msgid "log_sleep_time_seconds = 0"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml42(td)
+msgid ""
+"To allow visibility into rate limiting set this value &gt; 0 and all sleeps "
+"greater than the number will be logged."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml45(td)
+msgid "rate_buffer_seconds = 5"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml45(td)
+msgid ""
+"Number of seconds the rate counter can drop and be allowed to catch up (at a"
+" faster than listed rate). A larger number will result in larger spikes in "
+"rate but better average accuracy."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml48(td)
+msgid "account_ratelimit = 0"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml48(td)
+msgid ""
+"If set, will limit PUT and DELETE requests to /account_name/container_name. "
+"Number is in requests per second."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml51(td)
+msgid "account_whitelist = a,b"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml51(td)
+msgid "Comma separated lists of account names that will not be rate limited."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml54(td)
+msgid "account_blacklist = c,d"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml54(td)
+msgid ""
+"Comma separated lists of account names that will not be allowed. Returns a "
+"497 response. r: for containers of size x, limit requests per second to r. "
+"Will limit PUT, DELETE, and POST requests to /a/c/o. "
+"container_listing_ratelimit_x = r: for containers of size x, limit listing "
+"requests per second to r. Will limit GET requests to /a/c."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml57(td)
+msgid "with container_limit_x = r"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml60(td)
+msgid "container_ratelimit_0 = 100"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml63(td)
+msgid "container_ratelimit_10 = 50"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml66(td)
+msgid "container_ratelimit_50 = 20"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml69(td)
+msgid "container_listing_ratelimit_0 = 100"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml72(td)
+msgid "container_listing_ratelimit_10 = 50"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml75(td)
+msgid "container_listing_ratelimit_50 = 20"
+msgstr ""
+
+#: ./doc/common/tables/keystone-revoke.xml8(caption)
+msgid "Description of configuration options for revoke"
+msgstr ""
+
+#: ./doc/common/tables/keystone-revoke.xml19(th)
+msgid "[revoke]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-revoke.xml23(td)
+msgid ""
+"(BoolOpt) Toggle for revocation event cacheing. This has no effect unless "
+"global caching is enabled."
+msgstr ""
+
+#: ./doc/common/tables/keystone-revoke.xml26(td)
+msgid "driver = keystone.contrib.revoke.backends.kvs.Revoke"
+msgstr ""
+
+#: ./doc/common/tables/keystone-revoke.xml27(td)
+msgid ""
+"(StrOpt) An implementation of the backend for persisting revocation events."
+msgstr ""
+
+#: ./doc/common/tables/keystone-revoke.xml30(td)
+msgid "expiration_buffer = 1800"
+msgstr ""
+
+#: ./doc/common/tables/keystone-revoke.xml31(td)
+msgid ""
+"(IntOpt) This value (calculated in seconds) is added to token expiration "
+"before a revocation event may be removed from the backend."
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml23(td)
+msgid "(StrOpt) File name for the paste.deploy config for cinder-api"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml26(td)
+msgid "api_rate_limit = True"
+msgstr "api_rate_limit = True"
+
+#: ./doc/common/tables/cinder-api.xml27(td)
+msgid "(BoolOpt) whether to rate limit the api"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml35(td)
+msgid "(BoolOpt) Deploy v1 of the Cinder API."
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml39(td)
+msgid "(BoolOpt) Deploy v2 of the Cinder API."
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml42(td)
+msgid "extra_capabilities = {}"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml43(td)
+msgid ""
+"(StrOpt) User defined capabilities, a JSON formatted string specifying "
+"key/value pairs."
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml51(td)
+msgid ""
+"(IntOpt) the maximum number of items returned in a single response from a "
+"collection resource"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml55(td)
+msgid "(IntOpt) Max size for body of a request"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml58(td)
+msgid "osapi_volume_base_URL = None"
+msgstr "osapi_volume_base_URL = None"
+
+#: ./doc/common/tables/cinder-api.xml59(td)
+msgid ""
+"(StrOpt) Base URL that will be presented to users in links to the OpenStack "
+"Volume API"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml62(td)
+msgid "osapi_volume_ext_list ="
+msgstr "osapi_volume_ext_list ="
+
+#: ./doc/common/tables/cinder-api.xml63(td)
+msgid ""
+"(ListOpt) Specify list of extensions to load when using "
+"osapi_volume_extension option with cinder.api.contrib.select_extensions"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml66(td)
+msgid "osapi_volume_extension = ['cinder.api.contrib.standard_extensions']"
+msgstr "osapi_volume_extension = ['cinder.api.contrib.standard_extensions']"
+
+#: ./doc/common/tables/cinder-api.xml67(td)
+msgid "(MultiStrOpt) osapi volume extension to load"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml70(td)
+msgid "osapi_volume_listen = 0.0.0.0"
+msgstr "osapi_volume_listen = 0.0.0.0"
+
+#: ./doc/common/tables/cinder-api.xml71(td)
+msgid "(StrOpt) IP address for OpenStack Volume API to listen"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml74(td)
+msgid "osapi_volume_listen_port = 8776"
+msgstr "osapi_volume_listen_port = 8776"
+
+#: ./doc/common/tables/cinder-api.xml75(td)
+msgid "(IntOpt) port for os volume api to listen"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml78(td)
+msgid "osapi_volume_workers = None"
+msgstr "osapi_volume_workers = None"
+
+#: ./doc/common/tables/cinder-api.xml79(td)
+msgid "(IntOpt) Number of workers for OpenStack Volume API service"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml82(td)
+msgid "transfer_api_class = cinder.transfer.api.API"
+msgstr "transfer_api_class = cinder.transfer.api.API"
+
+#: ./doc/common/tables/cinder-api.xml83(td)
+msgid "(StrOpt) The full class name of the volume transfer API class"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml86(td)
+msgid "volume_api_class = cinder.volume.api.API"
+msgstr "volume_api_class = cinder.volume.api.API"
+
+#: ./doc/common/tables/cinder-api.xml90(td)
+msgid "volume_name_template = volume-%s"
+msgstr "volume_name_template = volume-%s"
+
+#: ./doc/common/tables/cinder-api.xml91(td)
+msgid "(StrOpt) Template string to be used to generate volume names"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml94(td)
+msgid "volume_transfer_key_length = 16"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml95(td)
+msgid "(IntOpt) The number of characters in the autogenerated auth key."
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml98(td)
+msgid "volume_transfer_salt_length = 8"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml99(td)
+msgid "(IntOpt) The number of characters in the salt."
+msgstr ""
+
+#: ./doc/common/tables/trove-db_couchbase.xml8(caption)
+msgid "Description of configuration options for db_couchbase"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_couchbase.xml19(th)
+msgid "[couchbase]"
+msgstr "[couchbase]"
+
+#: ./doc/common/tables/trove-db_couchbase.xml26(td)
+msgid "mount_point = /var/lib/couchbase"
+msgstr "mount_point = /var/lib/couchbase"
+
+#: ./doc/common/tables/trove-db_couchbase.xml30(td)
+msgid "tcp_ports = 8091, 8092, 4369, 11209-11211, 21100-21199"
+msgstr "tcp_ports = 8091, 8092, 4369, 11209-11211, 21100-21199"
+
+#: ./doc/common/tables/heat-clients_trove.xml8(caption)
+msgid "Description of configuration options for clients_trove"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_trove.xml19(th)
+msgid "[clients_trove]"
+msgstr "[clients_trove]"
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml7(literal)
+msgid "[account-replicator]"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml18(td)
+msgid "log_name = account-replicator"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml30(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml30(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml30(td)
+msgid "vm_test_mode = no"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml30(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml30(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml30(td)
+msgid "Indicates that you are using a VM environment"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml33(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml33(td)
+msgid "per_diff = 1000"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml33(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml33(td)
+msgid "Limit number of items to get per diff"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml36(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml36(td)
+msgid "max_diffs = 100"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml36(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml36(td)
+msgid "Caps how long the replicator spends trying to sync a database per pass"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml39(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml39(td)
+msgid "concurrency = 8"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml42(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml42(td)
+msgid "interval = 30"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml57(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml66(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml51(td)
+msgid "reclaim_age = 604800"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml57(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml66(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml51(td)
+msgid "Time elapsed in seconds before an object can be reclaimed"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml60(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml36(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml54(td)
+msgid "run_pause = 30"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml60(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml36(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml54(td)
+msgid "Time in seconds to wait between replication passes"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml8(caption)
+msgid "Description of configuration options for plumgrid"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml19(th)
+msgid "[plumgriddirector]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml22(td)
+msgid "director_server = localhost"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml23(td)
+msgid "(StrOpt) PLUMgrid Director server to connect to"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml26(td)
+msgid "director_server_port = 8080"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml27(td)
+msgid "(StrOpt) PLUMgrid Director server port to connect to"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml30(td)
+#: ./doc/common/tables/neutron-ml2_brocade.xml30(td)
+msgid "password = password"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml31(td)
+msgid "(StrOpt) PLUMgrid Director admin password"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml34(td)
+msgid "servertimeout = 5"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml35(td)
+msgid "(IntOpt) PLUMgrid Director server timeout"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml38(td)
+msgid "username = username"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml39(td)
+msgid "(StrOpt) PLUMgrid Director admin username"
+msgstr ""
+
+#: ./doc/common/tables/trove-heat.xml8(caption)
+msgid "Description of configuration options for heat"
+msgstr ""
+
+#: ./doc/common/tables/trove-heat.xml22(td)
+msgid "heat_time_out = 60"
+msgstr "heat_time_out = 60"
+
+#: ./doc/common/tables/trove-heat.xml26(td)
+msgid "heat_url = http://localhost:8004/v1"
+msgstr "heat_url = http://localhost:8004/v1"
+
+#: ./doc/common/tables/glance-sheepdog.xml8(caption)
+msgid "Description of configuration options for sheepdog"
+msgstr ""
+
+#: ./doc/common/tables/glance-sheepdog.xml22(td)
+msgid "sheepdog_store_address = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/glance-sheepdog.xml23(td)
+msgid "(StrOpt) IP address of sheep daemon."
+msgstr ""
+
+#: ./doc/common/tables/glance-sheepdog.xml26(td)
+msgid "sheepdog_store_chunk_size = 64"
+msgstr ""
+
+#: ./doc/common/tables/glance-sheepdog.xml27(td)
+msgid ""
+"(IntOpt) Images will be chunked into objects of this size (in megabytes). "
+"For best performance, this should be a power of two."
+msgstr ""
+
+#: ./doc/common/tables/glance-sheepdog.xml30(td)
+msgid "sheepdog_store_port = 7000"
+msgstr ""
+
+#: ./doc/common/tables/glance-sheepdog.xml31(td)
+msgid "(IntOpt) Port of sheep daemon."
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml7(literal)
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml7(literal)
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml7(literal)
+msgid "container-sync-realms.conf-sample"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml18(td)
+msgid "mtime_check_interval = 300"
+msgstr ""
+
+#: ./doc/common/tables/cinder-windows.xml8(caption)
+msgid "Description of configuration options for windows"
+msgstr ""
+
+#: ./doc/common/tables/cinder-windows.xml22(td)
+msgid "windows_iscsi_lun_path = C:\\iSCSIVirtualDisks"
+msgstr "windows_iscsi_lun_path = C:\\iSCSIVirtualDisks"
+
+#: ./doc/common/tables/cinder-windows.xml23(td)
+msgid "(StrOpt) Path to store VHD backed volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san-solaris.xml8(caption)
+msgid "Description of configuration options for san-solaris"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san-solaris.xml22(td)
+msgid "san_zfs_volume_base = rpool/"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san-solaris.xml23(td)
+msgid "(StrOpt) The ZFS path under which to create zvols for volumes."
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml8(caption)
+msgid "Description of configuration options for nuage"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml22(td)
+msgid "auth_resource ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml23(td)
+msgid "(StrOpt) Nuage provided uri for initial authorization to access VSD"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml26(td)
+msgid "base_uri = /"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml27(td)
+msgid "(StrOpt) Nuage provided base uri to reach out to VSD"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml30(td)
+msgid "default_floatingip_quota = 254"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml31(td)
+msgid "(IntOpt) Per Net Partition quota of floating ips"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml34(td)
+msgid "default_net_partition_name = OpenStackDefaultNetPartition"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml35(td)
+msgid ""
+"(StrOpt) Default Network partition in which VSD will orchestrate network "
+"resources using openstack"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml38(td)
+msgid "organization = system"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml39(td)
+msgid ""
+"(StrOpt) Organization name in which VSD will orchestrate network resources "
+"using openstack"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml42(td)
+msgid "server = localhost:8800"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml43(td)
+msgid "(StrOpt) IP Address and Port of Nuage's VSD server"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml46(td)
+msgid "serverauth = username:password"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml47(td)
+msgid "(StrOpt) Username and password for authentication"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml50(td)
+msgid "serverssl = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml51(td)
+msgid "(BoolOpt) Boolean for SSL connection with VSD server"
 msgstr ""
 
 #: ./doc/common/tables/neutron-bigswitch.xml8(caption)
 msgid "Description of configuration options for bigswitch"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml8(caption)
-msgid "Description of configuration options for libvirt"
-msgstr ""
-
-#: ./doc/common/tables/nova-libvirt.xml22(td)
-msgid "remove_unused_base_images = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-libvirt.xml23(td)
-msgid "(BoolOpt) Should unused base images be removed?"
-msgstr ""
-
-#: ./doc/common/tables/nova-libvirt.xml26(td)
-msgid "remove_unused_original_minimum_age_seconds = 86400"
-msgstr ""
-
-#: ./doc/common/tables/nova-libvirt.xml27(td)
+#: ./doc/common/tables/ceilometer-rpc.xml22(td)
+#: ./doc/common/tables/trove-rpc.xml22(td)
+#: ./doc/common/tables/heat-rpc.xml22(td)
+#: ./doc/common/tables/neutron-common.xml38(td)
 msgid ""
-"(IntOpt) Unused unresized base images younger than this will not be removed"
+"allowed_rpc_exception_modules = nova.exception, cinder.exception, exceptions"
+msgstr "allowed_rpc_exception_modules = nova.exception, cinder.exception, exceptions"
+
+#: ./doc/common/tables/ceilometer-rpc.xml26(td)
+msgid "dispatcher = ['database']"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml33(td)
-msgid "checksum_base_images = False"
+#: ./doc/common/tables/ceilometer-rpc.xml27(td)
+msgid "(MultiStrOpt) Dispatcher to process data."
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml34(td)
-msgid "(BoolOpt) Write a checksum for files in _base to disk"
+#: ./doc/common/tables/ceilometer-rpc.xml30(td)
+msgid "rpc_backend = ceilometer.openstack.common.rpc.impl_kombu"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml37(td)
-msgid "checksum_interval_seconds = 3600"
-msgstr ""
-
-#: ./doc/common/tables/nova-libvirt.xml38(td)
-msgid "(IntOpt) How frequently to checksum base images"
-msgstr ""
-
-#: ./doc/common/tables/nova-libvirt.xml41(td)
-msgid "connection_uri ="
-msgstr ""
-
-#: ./doc/common/tables/nova-libvirt.xml42(td)
+#: ./doc/common/tables/ceilometer-rpc.xml66(td)
 msgid ""
-"(StrOpt) Override the default libvirt URI (which is dependent on virt_type)"
+"rpc_zmq_matchmaker = "
+"ceilometer.openstack.common.rpc.matchmaker.MatchMakerLocalhost"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml45(td)
-msgid "cpu_mode = None"
+#: ./doc/common/tables/ceilometer-rpc.xml78(th)
+msgid "[publisher]"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml46(td)
+#: ./doc/common/tables/ceilometer-rpc.xml81(td)
+msgid "metering_secret = change this or be hacked"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-rpc.xml82(td)
+msgid "(StrOpt) Secret value for signing metering messages."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-rpc.xml85(th)
+msgid "[publisher_rpc]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-rpc.xml88(td)
+msgid "metering_topic = metering"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-rpc.xml89(td)
+msgid "(StrOpt) The topic that ceilometer uses for metering messages."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-rpc.xml96(td)
+#: ./doc/common/tables/heat-rpc.xml69(td)
+msgid "(ListOpt) AMQP topic(s) used for OpenStack notifications"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-updater.xml7(literal)
+msgid "[container-updater]"
+msgstr "[container-updater]"
+
+#: ./doc/common/tables/swift-container-server-container-updater.xml18(td)
+msgid "log_name = container-updater"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-updater.xml33(td)
+msgid "concurrency = 4"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-updater.xml42(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml39(td)
+msgid "slowdown = 0.01"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-updater.xml42(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml39(td)
+msgid "Time in seconds to wait between objects"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-updater.xml45(td)
+msgid "account_suppression_time = 60"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-updater.xml45(td)
 msgid ""
-"(StrOpt) Set to \"host-model\" to clone the host CPU feature flags; to "
-"\"host-passthrough\" to use the host CPU model exactly; to \"custom\" to use"
-" a named CPU model; to \"none\" to not set any CPU model. If "
-"virt_type=\"kvm|qemu\", it will default to \"host-model\", otherwise it will"
-" default to \"none\""
+"Seconds to suppress updating an account that has generated an error "
+"(timeout, not yet found, etc.)"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml49(td)
-msgid "cpu_model = None"
+#: ./doc/common/tables/trove-db_mongodb.xml8(caption)
+msgid "Description of configuration options for db_mongodb"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml50(td)
+#: ./doc/common/tables/trove-db_mongodb.xml19(th)
+msgid "[mongodb]"
+msgstr "[mongodb]"
+
+#: ./doc/common/tables/trove-db_mongodb.xml26(td)
+msgid "mount_point = /var/lib/mongodb"
+msgstr "mount_point = /var/lib/mongodb"
+
+#: ./doc/common/tables/trove-db_mongodb.xml30(td)
+msgid "tcp_ports = 2500, 27017"
+msgstr "tcp_ports = 2500, 27017"
+
+#: ./doc/common/tables/trove-db_mongodb.xml35(td)
 msgid ""
-"(StrOpt) Set to a named libvirt CPU model (see names listed in "
-"/usr/share/libvirt/cpu_map.xml). Only has effect if cpu_mode=\"custom\" and "
-"virt_type=\"kvm|qemu\""
+"(ListOpt) List of UPD ports and/or port ranges to open in the security group"
+" (only applicable if trove_security_groups_support is True)"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml53(td)
-msgid "disk_prefix = None"
+#: ./doc/common/tables/swift-object-server-object-replicator.xml7(literal)
+msgid "[object-replicator]"
+msgstr "[object-replicator]"
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml18(td)
+msgid "log_name = object-replicator"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml54(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml33(td)
+msgid "daemonize = on"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml33(td)
+msgid "Whether or not to run replication as a daemon"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml42(td)
+msgid "stats_interval = 300"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml42(td)
+msgid "Interval in seconds between logging replication statistics"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml45(td)
+msgid "sync_method = rsync"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml48(td)
+msgid "rsync_timeout = 900"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml48(td)
+msgid "Max duration (seconds) of a partition rsync"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml51(td)
+msgid "rsync_bwlimit = 0"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml54(td)
+msgid "rsync_io_timeout = 30"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml54(td)
+msgid "Passed to rsync for a max duration (seconds) of an I/O op"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml57(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml36(td)
+msgid "node_timeout = &lt;whatever's in the DEFAULT section or 10&gt;"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml60(td)
+msgid "http_timeout = 60"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml60(td)
+msgid "Maximum duration for an HTTP request"
+msgstr "Durée maximum d'une requête HTTP"
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml63(td)
+msgid "lockup_timeout = 1800"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml63(td)
 msgid ""
-"(StrOpt) Override the default disk prefix for the devices attached to a "
-"server, which is dependent on virt_type. (valid options are: sd, xvd, uvd, "
-"vd)"
+"Attempts to kill all workers if nothing replications for lockup_timeout "
+"seconds"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml57(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml69(td)
+msgid "ring_check_interval = 15"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml69(td)
+msgid "How often (in seconds) to check the ring"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml75(td)
+msgid "rsync_error_log_line_length = 0"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml78(td)
+msgid "handoffs_first = False"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml78(td)
 msgid ""
-"image_info_filename_pattern = "
-"$instances_path/$image_cache_subdirectory_name/%(image)s.info"
+"If set to True, partitions that are not supposed to be on the node will be "
+"replicated first. The default setting should not be changed, except for "
+"extreme situations."
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml58(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml81(td)
+msgid "handoff_delete = auto"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml81(td)
 msgid ""
-"(StrOpt) Allows image information files to be stored in non-standard "
-"locations"
+"By default handoff partitions will be removed when it has successfully "
+"replicated to all the canonical nodes. If set to an integer n, it will "
+"remove the partition if it is successfully replicated to n nodes. The "
+"default setting should not be changed, except for extremem situations. This "
+"uses what's set here, or what's set in the DEFAULT section, or 10 (though "
+"other sections use 3 as the final default)."
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml61(td)
-msgid "remove_unused_kernels = False"
+#: ./doc/common/tables/glance-filesystem.xml8(caption)
+msgid "Description of configuration options for filesystem"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml62(td)
+#: ./doc/common/tables/glance-filesystem.xml22(td)
+msgid "filesystem_store_datadir = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-filesystem.xml23(td)
 msgid ""
-"(BoolOpt) Should unused kernel images be removed? This is only safe to "
-"enable if all compute nodes have been updated to support this option. This "
-"will be enabled by default in future."
+"(StrOpt) Directory to which the Filesystem backend store writes images."
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml65(td)
-msgid "remove_unused_resized_minimum_age_seconds = 3600"
+#: ./doc/common/tables/glance-filesystem.xml26(td)
+msgid "filesystem_store_datadirs = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml66(td)
+#: ./doc/common/tables/glance-filesystem.xml27(td)
 msgid ""
-"(IntOpt) Unused resized base images younger than this will not be removed"
+"(MultiStrOpt) List of directories and its priorities to which the Filesystem"
+" backend store writes images."
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml69(td)
-msgid "rng_dev_path = None"
+#: ./doc/common/tables/glance-filesystem.xml30(td)
+msgid "filesystem_store_metadata_file = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml70(td)
+#: ./doc/common/tables/glance-filesystem.xml31(td)
 msgid ""
-"(StrOpt) A path to a device that will be used as source of entropy on the "
-"host. Permitted options are: /dev/random or /dev/hwrng"
+"(StrOpt) The path to a file which contains the metadata to be returned with "
+"any location associated with this store. The file must contain a valid JSON "
+"dict."
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml73(td)
-msgid "snapshots_directory = $instances_path/snapshots"
+#: ./doc/common/tables/trove-rpc.xml38(td)
+msgid "num_tries = 3"
+msgstr "num_tries = 3"
+
+#: ./doc/common/tables/trove-rpc.xml47(td)
+msgid "(IntOpt) The interval in seconds which periodic tasks are run."
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml74(td)
+#: ./doc/common/tables/trove-rpc.xml50(td)
+msgid "rpc_backend = trove.openstack.common.rpc.impl_kombu"
+msgstr "rpc_backend = trove.openstack.common.rpc.impl_kombu"
+
+#: ./doc/common/tables/trove-rpc.xml77(th)
+msgid "[secure_messages]"
+msgstr "[secure_messages]"
+
+#: ./doc/common/tables/trove-rpc.xml80(td)
+#: ./doc/common/tables/keystone-trust.xml26(td)
+msgid "enabled = True"
+msgstr "enabled = True"
+
+#: ./doc/common/tables/trove-rpc.xml81(td)
 msgid ""
-"(StrOpt) Location where libvirt driver will store snapshots before uploading"
-" them to image service"
+"(BoolOpt) Whether Secure Messaging (Signing) is enabled, defaults to enabled"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml77(td)
-msgid "vif_driver = nova.virt.libvirt.vif.LibvirtGenericVIFDriver"
-msgstr ""
+#: ./doc/common/tables/trove-rpc.xml84(td)
+msgid "encrypt = False"
+msgstr "encrypt = False"
 
-#: ./doc/common/tables/nova-libvirt.xml78(td)
+#: ./doc/common/tables/trove-rpc.xml85(td)
 msgid ""
-"(StrOpt) DEPRECATED. The libvirt VIF driver to configure the VIFs.This "
-"option is deprecated and will be removed in the Juno release."
+"(BoolOpt) Whether Secure Messaging (Encryption) is enabled, defaults to not "
+"enabled"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml81(td)
-msgid "virt_type = kvm"
-msgstr ""
+#: ./doc/common/tables/trove-rpc.xml88(td)
+msgid "enforced = False"
+msgstr "enforced = False"
 
-#: ./doc/common/tables/nova-libvirt.xml82(td)
+#: ./doc/common/tables/trove-rpc.xml89(td)
 msgid ""
-"(StrOpt) Libvirt domain type (valid options are: kvm, lxc, qemu, uml, xen)"
+"(BoolOpt) Whether Secure Messaging (Signing) is enforced, defaults to not "
+"enforced"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml85(td)
-#: ./doc/common/tables/cinder-storage.xml98(td)
-msgid "volume_clear = zero"
+#: ./doc/common/tables/trove-rpc.xml92(td)
+msgid "kds_endpoint = None"
+msgstr "kds_endpoint = None"
+
+#: ./doc/common/tables/trove-rpc.xml93(td)
+msgid "(StrOpt) KDS endpoint (ex: http://kds.example.com:35357/v3)"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml86(td)
+#: ./doc/common/tables/trove-rpc.xml96(td)
+msgid "secret_key = None"
+msgstr "secret_key = None"
+
+#: ./doc/common/tables/trove-rpc.xml97(td)
 msgid ""
-"(StrOpt) Method used to wipe old volumes (valid options are: none, zero, "
-"shred)"
+"(MultiStrOpt) A list of keys: (ex: name:&lt;base64 encoded key&gt;), ignored"
+" if secret_keys_file is set"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml89(td)
-#: ./doc/common/tables/cinder-storage.xml106(td)
-msgid "volume_clear_size = 0"
-msgstr ""
+#: ./doc/common/tables/trove-rpc.xml100(td)
+msgid "secret_keys_file = None"
+msgstr "secret_keys_file = None"
 
-#: ./doc/common/tables/nova-libvirt.xml90(td)
-#: ./doc/common/tables/cinder-storage.xml107(td)
-msgid "(IntOpt) Size in MiB to wipe at start of old volumes. 0 =&gt; all"
-msgstr ""
-
-#: ./doc/common/tables/nova-libvirt.xml93(td)
+#: ./doc/common/tables/trove-rpc.xml101(td)
 msgid ""
-"volume_drivers = iscsi=nova.virt.libvirt.volume.LibvirtISCSIVolumeDriver, "
-"iser=nova.virt.libvirt.volume.LibvirtISERVolumeDriver, "
-"local=nova.virt.libvirt.volume.LibvirtVolumeDriver, "
-"fake=nova.virt.libvirt.volume.LibvirtFakeVolumeDriver, "
-"rbd=nova.virt.libvirt.volume.LibvirtNetVolumeDriver, "
-"sheepdog=nova.virt.libvirt.volume.LibvirtNetVolumeDriver, "
-"nfs=nova.virt.libvirt.volume.LibvirtNFSVolumeDriver, "
-"aoe=nova.virt.libvirt.volume.LibvirtAOEVolumeDriver, "
-"glusterfs=nova.virt.libvirt.volume.LibvirtGlusterfsVolumeDriver, "
-"fibre_channel=nova.virt.libvirt.volume.LibvirtFibreChannelVolumeDriver, "
-"scality=nova.virt.libvirt.volume.LibvirtScalityVolumeDriver"
+"(StrOpt) Path to the file containing the keys, takes precedence over "
+"secret_key"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml94(td)
-msgid "(ListOpt) Libvirt handlers for remote volumes."
+#: ./doc/common/tables/ceilometer-swift.xml22(td)
+msgid "reseller_prefix = AUTH_"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml97(td)
-msgid "wait_soft_reboot_seconds = 120"
-msgstr ""
-
-#: ./doc/common/tables/nova-libvirt.xml98(td)
+#: ./doc/common/tables/ceilometer-swift.xml23(td)
 msgid ""
-"(IntOpt) Number of seconds to wait for instance to shut down after soft "
-"reboot request is made. We fall back to hard reboot if instance does not "
-"shutdown within this window."
+"(StrOpt) Swift reseller prefix. Must be on par with reseller_prefix in "
+"proxy-server.conf."
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml8(caption)
+msgid "Description of configuration options for backup"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml22(td)
+msgid "backup_aes_cbc_key = default_aes_cbc_key"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml23(td)
+msgid "(StrOpt) Default OpenSSL aes_cbc key."
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml26(td)
+msgid "backup_chunk_size = 65536"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml27(td)
+msgid ""
+"(IntOpt) Chunk size to stream to swift container. This should be in "
+"multiples of 128 bytes, since this is the size of an md5 digest block "
+"allowing the process to update the file checksum during streaming. See: "
+"http://stackoverflow.com/questions/1131220/"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml30(td)
+msgid ""
+"backup_incremental_strategy = {'InnoBackupEx': 'InnoBackupExIncremental'}"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml31(td)
+msgid ""
+"(DictOpt) Incremental Backup Runner Based off of the default strategy. For "
+"strategies that do not implement an incremental the runner will use the "
+"default full backup."
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml34(td)
+msgid "backup_namespace = trove.guestagent.strategies.backup.mysql_impl"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml35(td)
+msgid "(StrOpt) Namespace to load backup strategies from."
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml38(td)
+msgid "backup_runner = trove.guestagent.backup.backup_types.InnoBackupEx"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml42(td)
+msgid "backup_runner_options = {}"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml43(td)
+msgid "(DictOpt) Additional options to be passed to the backup runner."
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml46(td)
+msgid "backup_segment_max_size = 2147483648"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml47(td)
+msgid "(IntOpt) Maximum size of each segment of the backup file."
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml54(td)
+msgid "backup_swift_container = database_backups"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml58(td)
+msgid "backup_use_gzip_compression = True"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml59(td)
+msgid "(BoolOpt) Compress backups using gzip."
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml62(td)
+msgid "backup_use_openssl_encryption = True"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml63(td)
+msgid "(BoolOpt) Encrypt backups using OpenSSL."
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml66(td)
+msgid "backup_use_snet = False"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml67(td)
+msgid "(BoolOpt) Send backup files over snet."
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml70(td)
+msgid "backups_page_size = 20"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml8(caption)
+msgid "Description of configuration options for network"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml22(td)
+msgid "allow_same_net_traffic = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml23(td)
+msgid "(BoolOpt) Whether to allow network traffic from same network"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml26(td)
+msgid "auto_assign_floating_ip = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml27(td)
+msgid "(BoolOpt) Autoassigning floating IP to VM"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml30(td)
+msgid "cnt_vpn_clients = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml31(td)
+msgid "(IntOpt) Number of addresses reserved for vpn clients"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml34(td)
+msgid "create_unique_mac_address_attempts = 5"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml35(td)
+msgid "(IntOpt) Number of attempts to create unique mac address"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml38(td)
+msgid "default_access_ip_network_name = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml39(td)
+msgid "(StrOpt) Name of network to use to set access IPs for instances"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml42(td)
+msgid "default_floating_pool = nova"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml43(td)
+msgid "(StrOpt) Default pool for floating IPs"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml46(td)
+msgid "defer_iptables_apply = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml47(td)
+msgid ""
+"(BoolOpt) Whether to batch up the application of IPTables rules during a "
+"host restart and apply all at the end of the init phase"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml50(td)
+msgid "dhcp_domain = novalocal"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml54(td)
+msgid "dhcp_lease_time = 120"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml55(td)
+msgid "(IntOpt) Lifetime of a DHCP lease in seconds"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml58(td)
+msgid "dhcpbridge = $bindir/nova-dhcpbridge"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml59(td)
+msgid "(StrOpt) Location of nova-dhcpbridge"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml62(td)
+msgid "dhcpbridge_flagfile = ['/etc/nova/nova-dhcpbridge.conf']"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml63(td)
+msgid "(MultiStrOpt) Location of flagfiles for dhcpbridge"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml66(td)
+msgid "dns_server = []"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml67(td)
+msgid ""
+"(MultiStrOpt) If set, uses specific DNS server for dnsmasq. Can be specified"
+" multiple times."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml70(td)
+msgid "dns_update_periodic_interval = -1"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml71(td)
+msgid ""
+"(IntOpt) Number of seconds to wait between runs of updates to DNS entries."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml74(td)
+#: ./doc/common/tables/neutron-dhcp_agent.xml22(td)
+msgid "dnsmasq_config_file ="
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml75(td)
+#: ./doc/common/tables/neutron-dhcp_agent.xml23(td)
+msgid "(StrOpt) Override the default dnsmasq settings with this file"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml78(td)
+#: ./doc/common/tables/neutron-securitygroups.xml26(td)
+msgid "firewall_driver = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml79(td)
+msgid ""
+"(StrOpt) Firewall driver (defaults to hypervisor specific iptables driver)"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml82(td)
+msgid "fixed_ip_disassociate_timeout = 600"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml83(td)
+msgid "(IntOpt) Seconds after which a deallocated IP is disassociated"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml86(td)
+msgid "flat_injected = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml87(td)
+msgid "(BoolOpt) Whether to attempt to inject network setup into guest"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml90(td)
+msgid "flat_interface = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml91(td)
+msgid "(StrOpt) FlatDhcp will bridge into this interface if set"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml94(td)
+msgid "flat_network_bridge = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml95(td)
+msgid "(StrOpt) Bridge for simple network instances"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml98(td)
+msgid "flat_network_dns = 8.8.4.4"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml99(td)
+msgid "(StrOpt) DNS server for simple network"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml102(td)
+msgid "floating_ip_dns_manager = nova.network.noop_dns_driver.NoopDNSDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml103(td)
+msgid "(StrOpt) Full class name for the DNS Manager for floating IPs"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml106(td)
+msgid "force_dhcp_release = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml107(td)
+msgid "(BoolOpt) If True, send a dhcp release on instance termination"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml110(td)
+msgid "force_snat_range = []"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml111(td)
+msgid ""
+"(MultiStrOpt) Traffic to this range will always be snatted to the fallback "
+"ip, even if it would normally be bridged out of the node. Can be specified "
+"multiple times."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml114(td)
+msgid "forward_bridge_interface = ['all']"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml115(td)
+msgid ""
+"(MultiStrOpt) An interface that bridges can forward to. If this is set to "
+"all then all traffic will be forwarded. Can be specified multiple times."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml118(td)
+msgid "gateway = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml119(td)
+msgid "(StrOpt) Default IPv4 gateway"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml122(td)
+msgid "injected_network_template = $pybasedir/nova/virt/interfaces.template"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml123(td)
+msgid "(StrOpt) Template file for injected network"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml126(td)
+msgid "instance_dns_domain ="
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml127(td)
+msgid "(StrOpt) Full class name for the DNS Zone for instance IPs"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml130(td)
+msgid "instance_dns_manager = nova.network.noop_dns_driver.NoopDNSDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml131(td)
+msgid "(StrOpt) Full class name for the DNS Manager for instance IPs"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml134(td)
+msgid "iptables_bottom_regex ="
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml135(td)
+msgid ""
+"(StrOpt) Regular expression to match iptables rule that should always be on "
+"the bottom."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml138(td)
+msgid "iptables_drop_action = DROP"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml139(td)
+msgid ""
+"(StrOpt) The table that iptables to jump to when a packet is to be dropped."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml142(td)
+msgid "iptables_top_regex ="
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml143(td)
+msgid ""
+"(StrOpt) Regular expression to match iptables rule that should always be on "
+"the top."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml146(td)
+msgid "l3_lib = nova.network.l3.LinuxNetL3"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml147(td)
+msgid "(StrOpt) Indicates underlying L3 management library"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml150(td)
+msgid ""
+"linuxnet_interface_driver = "
+"nova.network.linux_net.LinuxBridgeInterfaceDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml151(td)
+msgid "(StrOpt) Driver used to create ethernet devices."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml154(td)
+msgid "linuxnet_ovs_integration_bridge = br-int"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml155(td)
+msgid "(StrOpt) Name of Open vSwitch bridge used with linuxnet"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml158(td)
+msgid "multi_host = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml159(td)
+msgid ""
+"(BoolOpt) Default value for multi_host in networks. Also, if set, some rpc "
+"network calls will be sent directly to host."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml162(td)
+msgid "network_allocate_retries = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml163(td)
+msgid "(IntOpt) Number of times to retry network allocation on failures"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml166(td)
+msgid "network_api_class = nova.network.api.API"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml167(td)
+msgid "(StrOpt) The full class name of the network API class to use"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml171(td)
+msgid "(IntOpt) MTU setting for network interface"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml174(td)
+msgid "network_driver = nova.network.linux_net"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml175(td)
+msgid "(StrOpt) Driver to use for network creation"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml178(td)
+msgid "network_manager = nova.network.manager.VlanManager"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml179(td)
+msgid "(StrOpt) Full class name for the Manager for network"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml182(td)
+msgid "network_size = 256"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml183(td)
+msgid "(IntOpt) Number of addresses in each private subnet"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml186(td)
+msgid "network_topic = network"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml187(td)
+msgid "(StrOpt) The topic network nodes listen on"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml190(td)
+msgid "networks_path = $state_path/networks"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml191(td)
+msgid "(StrOpt) Location to keep network config files"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml194(td)
+msgid "num_networks = 1"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml195(td)
+msgid "(IntOpt) Number of networks to support"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml198(td)
+msgid "ovs_vsctl_timeout = 120"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml199(td)
+msgid ""
+"(IntOpt) Amount of time, in seconds, that ovs_vsctl should wait for a "
+"response from the database. 0 is to wait forever."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml202(td)
+msgid "public_interface = eth0"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml203(td)
+msgid "(StrOpt) Interface for public IP addresses"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml206(td)
+msgid "routing_source_ip = $my_ip"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml207(td)
+msgid "(StrOpt) Public IP of network host"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml210(td)
+msgid "security_group_api = nova"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml211(td)
+msgid "(StrOpt) The full class name of the security API class"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml214(td)
+msgid "send_arp_for_ha = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml215(td)
+msgid "(BoolOpt) Send gratuitous ARPs for HA setup"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml218(td)
+msgid "send_arp_for_ha_count = 3"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml219(td)
+msgid "(IntOpt) Send this many gratuitous ARPs for HA setup"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml222(td)
+msgid "share_dhcp_address = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml223(td)
+msgid ""
+"(BoolOpt) If True in multi_host mode, all compute hosts share the same dhcp "
+"address. The same IP address used for DHCP will be added on each nova-"
+"network node which is only visible to the vms on the same host."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml226(td)
+msgid "teardown_unused_network_gateway = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml227(td)
+msgid ""
+"(BoolOpt) If True, unused gateway devices (VLAN and bridge) are deleted in "
+"VLAN network mode with multi hosted networks"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml230(td)
+msgid "update_dns_entries = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml231(td)
+msgid ""
+"(BoolOpt) If True, when a DNS entry must be updated, it sends a fanout cast "
+"to all network hosts to update their DNS entries in multi host mode"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml234(td)
+msgid "use_network_dns_servers = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml235(td)
+msgid ""
+"(BoolOpt) If set, uses the dns1 and dns2 from the network ref. as dns "
+"servers."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml238(td)
+msgid "use_neutron_default_nets = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml239(td)
+msgid "(StrOpt) Control for checking for default networks"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml242(td)
+msgid "use_single_default_gateway = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml243(td)
+msgid ""
+"(BoolOpt) Use single default gateway. Only first nic of vm will get default "
+"gateway from dhcp server"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml246(td)
+msgid "vlan_interface = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml247(td)
+msgid "(StrOpt) VLANs will bridge into this interface if set"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml250(td)
+msgid "vlan_start = 100"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml251(td)
+msgid "(IntOpt) First VLAN for private networks"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml257(td)
+msgid "vlan_interface = vmnic0"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml258(td)
+msgid "(StrOpt) Physical ethernet adapter name for vlan networking"
+msgstr ""
+
+#: ./doc/common/tables/glance-redis.xml23(td)
+#: ./doc/common/tables/keystone-redis.xml23(td)
+msgid "(StrOpt) Host to locate redis."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml8(caption)
+#: ./doc/common/tables/cinder-ssl.xml8(caption)
+#: ./doc/common/tables/trove-ssl.xml8(caption)
+#: ./doc/common/tables/neutron-ssl.xml8(caption)
+#: ./doc/common/tables/ceilometer-ssl.xml8(caption)
+#: ./doc/common/tables/glance-ssl.xml8(caption)
+msgid "Description of configuration options for ssl"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml19(th)
+msgid "[signing]"
+msgstr "[signing]"
+
+#: ./doc/common/tables/keystone-ssl.xml22(td)
+#: ./doc/common/tables/keystone-ssl.xml57(td)
+msgid "ca_certs = /etc/keystone/ssl/certs/ca.pem"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml23(td)
+msgid "(StrOpt) Path of the CA for token signing."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml26(td)
+#: ./doc/common/tables/keystone-ssl.xml61(td)
+msgid "ca_key = /etc/keystone/ssl/private/cakey.pem"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml27(td)
+msgid "(StrOpt) Path of the CA Key for token signing."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml30(td)
+msgid "cert_subject = /C=US/ST=Unset/L=Unset/O=Unset/CN=www.example.com"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml31(td)
+msgid ""
+"(StrOpt) Certificate Subject (auto generated certificate) for token signing."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml34(td)
+msgid "certfile = /etc/keystone/ssl/certs/signing_cert.pem"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml35(td)
+msgid "(StrOpt) Path of the certfile for token signing."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml38(td)
+msgid "key_size = 2048"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml39(td)
+msgid ""
+"(IntOpt) Key Size (in bits) for token signing cert (auto generated "
+"certificate)."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml42(td)
+msgid "keyfile = /etc/keystone/ssl/private/signing_key.pem"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml43(td)
+msgid "(StrOpt) Path of the keyfile for token signing."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml46(td)
+msgid "token_format = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml47(td)
+msgid "(StrOpt) Deprecated in favor of provider in the [token] section."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml50(td)
+#: ./doc/common/tables/keystone-ssl.xml89(td)
+msgid "valid_days = 3650"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml51(td)
+msgid ""
+"(IntOpt) Day the token signing cert is valid for (auto generated "
+"certificate)."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml58(td)
+msgid "(StrOpt) Path of the ca cert file for SSL."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml62(td)
+msgid "(StrOpt) Path of the CA key file for SSL."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml65(td)
+msgid "cert_required = False"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml66(td)
+msgid "(BoolOpt) Require client certificate."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml69(td)
+msgid "cert_subject = /C=US/ST=Unset/L=Unset/O=Unset/CN=localhost"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml70(td)
+msgid "(StrOpt) SSL Certificate Subject (auto generated certificate)."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml73(td)
+msgid "certfile = /etc/keystone/ssl/certs/keystone.pem"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml74(td)
+msgid "(StrOpt) Path of the certfile for SSL."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml78(td)
+msgid "(BoolOpt) Toggle for SSL support on the keystone eventlet servers."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml81(td)
+msgid "key_size = 1024"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml82(td)
+msgid "(IntOpt) SSL Key Length (in bits) (auto generated certificate)."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml85(td)
+msgid "keyfile = /etc/keystone/ssl/private/keystonekey.pem"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml86(td)
+msgid "(StrOpt) Path of the keyfile for SSL."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml90(td)
+msgid ""
+"(IntOpt) Days the certificate is valid for once signed (auto generated "
+"certificate)."
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml8(caption)
+msgid "Description of configuration options for ca"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml22(td)
+msgid "ca_file = cacert.pem"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml23(td)
+msgid "(StrOpt) Filename of root CA"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml26(td)
+msgid "ca_path = $state_path/CA"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml27(td)
+msgid "(StrOpt) Where we keep our root CA"
+msgstr "(StrOpt)  Où nous conservons notre CA racine"
+
+#: ./doc/common/tables/nova-ca.xml30(td)
+msgid "cert_manager = nova.cert.manager.CertManager"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml31(td)
+msgid "(StrOpt) Full class name for the Manager for cert"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml34(td)
+msgid "cert_topic = cert"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml35(td)
+msgid "(StrOpt) The topic cert nodes listen on"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml38(td)
+msgid "crl_file = crl.pem"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml39(td)
+msgid "(StrOpt) Filename of root Certificate Revocation List"
+msgstr "(StrOpt)  Nom de fichier de la liste de révocation de certificat racine"
+
+#: ./doc/common/tables/nova-ca.xml42(td)
+msgid "key_file = private/cakey.pem"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml43(td)
+msgid "(StrOpt) Filename of private key"
+msgstr "(StrOpt)  Nom de fichier de la clé privée"
+
+#: ./doc/common/tables/nova-ca.xml46(td)
+msgid "keys_path = $state_path/keys"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml47(td)
+msgid "(StrOpt) Where we keep our keys"
+msgstr "(StrOpt)  Où nous conservons nos clés"
+
+#: ./doc/common/tables/nova-ca.xml50(td)
+msgid ""
+"project_cert_subject = /C=US/ST=California/O=OpenStack/OU=NovaDev/CN"
+"=project-ca-%.16s-%s"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml51(td)
+msgid ""
+"(StrOpt) Subject for certificate for projects, %s for project, timestamp"
+msgstr "(StrOpt)  Objet de certificat pour les projets,% s pour le projet, timestamp"
+
+#: ./doc/common/tables/nova-ca.xml54(td)
+msgid "use_project_ca = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml55(td)
+msgid "(BoolOpt) Should we use a CA for each project?"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml58(td)
+msgid ""
+"user_cert_subject = "
+"/C=US/ST=California/O=OpenStack/OU=NovaDev/CN=%.16s-%.16s-%s"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml59(td)
+msgid ""
+"(StrOpt) Subject for certificate for users, %s for project, user, timestamp"
+msgstr "(StrOpt)  Objet de certificat pour les utilisateurs, % s pour le projet, utilisateur, timestamp"
+
+#: ./doc/common/tables/nova-ca.xml66(td)
+#: ./doc/common/tables/glance-ssl.xml23(td)
+msgid "(StrOpt) CA certificate file to use to verify connecting clients."
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml70(td)
+msgid "(StrOpt) Certificate file to use when starting the server securely."
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml74(td)
+msgid "(StrOpt) Private key file to use when starting the server securely."
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml8(caption)
+msgid "Description of configuration options for dhcp_agent"
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml26(td)
+msgid "dnsmasq_dns_servers = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml27(td)
+msgid ""
+"(ListOpt) Comma-separated list of the DNS servers which will be used as "
+"forwarders."
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml30(td)
+msgid "dnsmasq_lease_max = 16777216"
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml31(td)
+msgid "(IntOpt) Limit number of leases to prevent a denial-of-service."
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml34(td)
+msgid "enable_isolated_metadata = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml35(td)
+msgid "(BoolOpt) Support Metadata requests on isolated networks."
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml38(td)
+msgid "enable_metadata_network = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml39(td)
+msgid ""
+"(BoolOpt) Allows for serving metadata requests from a dedicated network. "
+"Requires enable_isolated_metadata = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml42(td)
+msgid "num_sync_threads = 4"
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml43(td)
+msgid "(IntOpt) Number of threads to use during sync process."
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml46(td)
+msgid "resync_interval = 5"
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml47(td)
+msgid "(IntOpt) Interval to resync."
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml50(td)
+msgid "use_namespaces = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml51(td)
+msgid "(BoolOpt) Allow overlapping IP."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml8(caption)
+msgid "Description of configuration options for collector"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml22(td)
+msgid "collector_workers = 1"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml23(td)
+msgid ""
+"(IntOpt) Number of workers for collector service. A single collector is "
+"enabled by default."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml26(th)
+msgid "[collector]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml29(td)
+msgid "udp_address = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml30(td)
+msgid ""
+"(StrOpt) Address to which the UDP socket is bound. Set to an empty string to"
+" disable."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml33(td)
+msgid "udp_port = 4952"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml34(td)
+msgid "(IntOpt) Port to which the UDP socket is bound."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml37(th)
+msgid "[dispatcher_file]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml40(td)
+msgid "backup_count = 0"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml41(td)
+msgid "(IntOpt) The max number of the files to keep."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml44(td)
+msgid "file_path = None"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml45(td)
+msgid "(StrOpt) Name and the location of the file to record meters."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml48(td)
+msgid "max_bytes = 0"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml49(td)
+msgid "(IntOpt) The max size of the file."
+msgstr ""
+
+#: ./doc/common/tables/cinder-hds-hus.xml8(caption)
+msgid "Description of configuration options for hds-hus"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hds-hus.xml22(td)
+msgid "hds_cinder_config_file = /opt/hds/hus/cinder_hus_conf.xml"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hds-hus.xml23(td)
+msgid "(StrOpt) configuration file for HDS cinder plugin for HUS"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml8(caption)
+msgid "Description of configuration options for netapp_7mode_iscsi"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml54(td)
+msgid "netapp_vfiler = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml55(td)
+msgid ""
+"(StrOpt) The vFiler unit on which provisioning of block storage volumes will"
+" be done. This option is only used by the driver when connecting to an "
+"instance with a storage family of Data ONTAP operating in 7-Mode and the "
+"storage protocol selected is iSCSI. Only use this option when utilizing the "
+"MultiStore feature on the NetApp storage system."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml58(td)
+msgid "netapp_volume_list = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml59(td)
+msgid ""
+"(StrOpt) This option is only utilized when the storage protocol is "
+"configured to use iSCSI. This option is used to restrict provisioning to the"
+" specified controller volumes. Specify the value of this option to be a "
+"comma separated list of NetApp controller volume names to be used for "
+"provisioning."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-hash.xml7(literal)
+msgid "[swift-hash]"
+msgstr "[swift-hash]"
+
+#: ./doc/common/tables/swift-swift-swift-hash.xml18(td)
+msgid "swift_hash_path_suffix = changeme"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-hash.xml18(td)
+msgid ""
+"A suffix used by hash_path to offer a bit more security when generating "
+"hashes for paths. It simply appends this value to all paths; if someone "
+"knows this suffix, it's easier for them to guess the hash a path will end up"
+" with. New installations are advised to set this parameter to a random "
+"secret, which would not be disclosed ouside the organization. The same "
+"secret needs to be used by all swift servers of the same cluster. Existing "
+"installations should set this parameter to an empty string."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-hash.xml29(td)
+msgid "swift_hash_path_prefix = changeme"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-hash.xml29(td)
+msgid ""
+"A prefix used by hash_path to offer a bit more security when generating "
+"hashes for paths. It simply appends this value to all paths; if someone "
+"knows this suffix, it's easier for them to guess the hash a path will end up"
+" with. New installations are advised to set this parameter to a random "
+"secret, which would not be disclosed ouside the organization. The same "
+"secret needs to be used by all swift servers of the same cluster. Existing "
+"installations should set this parameter to an empty string."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_gre.xml8(caption)
+msgid "Description of configuration options for ml2_gre"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_gre.xml19(th)
+msgid "[ml2_type_gre]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_gre.xml23(td)
+msgid ""
+"(ListOpt) Comma-separated list of &lt;tun_min&gt;:&lt;tun_max&gt; tuples "
+"enumerating ranges of GRE tunnel IDs that are available for tenant network "
+"allocation"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml8(caption)
+msgid "Description of configuration options for varmour"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml19(th)
+msgid "[vArmour]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml22(td)
+msgid "director = localhost"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml23(td)
+msgid "(StrOpt) vArmour director ip"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml26(td)
+msgid "director_port = 443"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml27(td)
+msgid "(StrOpt) vArmour director port"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml30(td)
+msgid "password = varmour"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml31(td)
+msgid "(StrOpt) vArmour director password"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml34(td)
+msgid "username = varmour"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml35(td)
+msgid "(StrOpt) vArmour director username"
+msgstr ""
+
+#: ./doc/common/tables/heat-debug.xml8(caption)
+#: ./doc/common/tables/trove-debug.xml8(caption)
+#: ./doc/common/tables/keystone-debug.xml8(caption)
+msgid "Description of configuration options for debug"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml7(literal)
+msgid "[filter:dlo]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml18(td)
+msgid "use = egg:swift#dlo"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml24(td)
+msgid "rate_limit_segments_per_sec = 1"
+msgstr "rate_limit_segments_per_sec = 1"
+
+#: ./doc/common/tables/trove-guestagent.xml8(caption)
+msgid "Description of configuration options for guestagent"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml22(td)
+msgid "agent_call_high_timeout = 60"
+msgstr "agent_call_high_timeout = 60"
+
+#: ./doc/common/tables/trove-guestagent.xml26(td)
+msgid "agent_call_low_timeout = 5"
+msgstr "agent_call_low_timeout = 5"
+
+#: ./doc/common/tables/trove-guestagent.xml30(td)
+msgid "agent_heartbeat_time = 10"
+msgstr "agent_heartbeat_time = 10"
+
+#: ./doc/common/tables/trove-guestagent.xml34(td)
+msgid "guest_config = $pybasedir/etc/trove/trove-guestagent.conf.sample"
+msgstr "guest_config = $pybasedir/etc/trove/trove-guestagent.conf.sample"
+
+#: ./doc/common/tables/trove-guestagent.xml35(td)
+msgid "(StrOpt) Path to guestagent config file."
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml38(td)
+msgid "guest_id = None"
+msgstr "guest_id = None"
+
+#: ./doc/common/tables/trove-guestagent.xml42(td)
+msgid "ignore_dbs = lost+found, mysql, information_schema"
+msgstr "ignore_dbs = lost+found, mysql, information_schema"
+
+#: ./doc/common/tables/trove-guestagent.xml46(td)
+msgid "ignore_users = os_admin, root"
+msgstr "ignore_users = os_admin, root"
+
+#: ./doc/common/tables/trove-guestagent.xml50(td)
+msgid "mount_options = defaults,noatime"
+msgstr "mount_options = defaults,noatime"
+
+#: ./doc/common/tables/trove-guestagent.xml54(td)
+msgid "restore_namespace = trove.guestagent.strategies.restore.mysql_impl"
+msgstr "restore_namespace = trove.guestagent.strategies.restore.mysql_impl"
+
+#: ./doc/common/tables/trove-guestagent.xml55(td)
+msgid "(StrOpt) Namespace to load restore strategies from."
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml58(td)
+msgid "storage_namespace = trove.guestagent.strategies.storage.swift"
+msgstr "storage_namespace = trove.guestagent.strategies.storage.swift"
+
+#: ./doc/common/tables/trove-guestagent.xml59(td)
+msgid "(StrOpt) Namespace to load the default storage strategy from."
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml62(td)
+msgid "storage_strategy = SwiftStorage"
+msgstr "storage_strategy = SwiftStorage"
+
+#: ./doc/common/tables/trove-guestagent.xml63(td)
+msgid "(StrOpt) Default strategy to store backups."
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml66(td)
+#: ./doc/common/tables/trove-taskmanager.xml66(td)
+msgid "usage_sleep_time = 5"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml67(td)
+#: ./doc/common/tables/trove-taskmanager.xml67(td)
+msgid "(IntOpt) Time to sleep during the check active guest."
+msgstr ""
+
+#: ./doc/common/tables/nova-qpid.xml23(td)
+#: ./doc/common/tables/glance-qpid.xml23(td)
+#: ./doc/common/tables/cinder-rpc.xml95(td)
+#: ./doc/common/tables/nova-rpc_all.xml63(td)
+#: ./doc/common/tables/keystone-qpid.xml23(td)
+msgid "(IntOpt) Seconds between connection keepalive heartbeats."
+msgstr ""
+
+#: ./doc/common/tables/nova-qpid.xml27(td)
+#: ./doc/common/tables/glance-qpid.xml27(td)
+#: ./doc/common/tables/cinder-rpc.xml99(td)
+#: ./doc/common/tables/nova-rpc_all.xml67(td)
+#: ./doc/common/tables/keystone-qpid.xml27(td)
+msgid "(StrOpt) Qpid broker hostname."
+msgstr ""
+
+#: ./doc/common/tables/nova-qpid.xml31(td)
+#: ./doc/common/tables/glance-qpid.xml31(td)
+#: ./doc/common/tables/cinder-rpc.xml103(td)
+#: ./doc/common/tables/nova-rpc_all.xml71(td)
+#: ./doc/common/tables/keystone-qpid.xml31(td)
+msgid "(ListOpt) Qpid HA cluster host:port pairs."
+msgstr ""
+
+#: ./doc/common/tables/nova-qpid.xml35(td)
+#: ./doc/common/tables/glance-qpid.xml35(td)
+#: ./doc/common/tables/cinder-rpc.xml107(td)
+#: ./doc/common/tables/nova-rpc_all.xml75(td)
+#: ./doc/common/tables/keystone-qpid.xml35(td)
+msgid "(StrOpt) Password for Qpid connection."
+msgstr ""
+
+#: ./doc/common/tables/nova-qpid.xml39(td)
+#: ./doc/common/tables/glance-qpid.xml39(td)
+#: ./doc/common/tables/cinder-rpc.xml111(td)
+#: ./doc/common/tables/nova-rpc_all.xml79(td)
+#: ./doc/common/tables/keystone-qpid.xml39(td)
+msgid "(IntOpt) Qpid broker port."
+msgstr ""
+
+#: ./doc/common/tables/nova-qpid.xml43(td)
+#: ./doc/common/tables/glance-qpid.xml43(td)
+#: ./doc/common/tables/cinder-rpc.xml115(td)
+#: ./doc/common/tables/nova-rpc_all.xml83(td)
+#: ./doc/common/tables/keystone-qpid.xml43(td)
+msgid "(StrOpt) Transport to use, either 'tcp' or 'ssl'."
+msgstr ""
+
+#: ./doc/common/tables/nova-qpid.xml47(td)
+#: ./doc/common/tables/glance-qpid.xml47(td)
+#: ./doc/common/tables/cinder-rpc.xml119(td)
+#: ./doc/common/tables/nova-rpc_all.xml87(td)
+#: ./doc/common/tables/keystone-qpid.xml47(td)
+msgid "(StrOpt) Space separated list of SASL mechanisms to use for auth."
+msgstr ""
+
+#: ./doc/common/tables/nova-qpid.xml51(td)
+#: ./doc/common/tables/glance-qpid.xml51(td)
+#: ./doc/common/tables/cinder-rpc.xml123(td)
+#: ./doc/common/tables/nova-rpc_all.xml91(td)
+#: ./doc/common/tables/keystone-qpid.xml51(td)
+msgid "(BoolOpt) Whether to disable the Nagle algorithm."
+msgstr ""
+
+#: ./doc/common/tables/nova-qpid.xml59(td)
+#: ./doc/common/tables/glance-qpid.xml59(td)
+#: ./doc/common/tables/cinder-rpc.xml131(td)
+#: ./doc/common/tables/nova-rpc_all.xml99(td)
+#: ./doc/common/tables/keystone-qpid.xml59(td)
+msgid "(StrOpt) Username for Qpid connection."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_l2pop.xml8(caption)
+msgid "Description of configuration options for ml2_l2pop"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_l2pop.xml19(th)
+msgid "[l2pop]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_l2pop.xml22(td)
+msgid "agent_boot_time = 180"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_l2pop.xml23(td)
+msgid ""
+"(IntOpt) Delay within which agent is expected to update existing ports whent"
+" it restarts"
+msgstr ""
+
+#: ./doc/common/tables/glance-zmq.xml8(caption)
+msgid "Description of configuration options for zmq"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml8(caption)
+msgid "Description of configuration options for embrane_lb"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml19(th)
+msgid "[heleoslb]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml23(td)
+#: ./doc/common/tables/neutron-common.xml220(td)
+msgid "(StrOpt) ESM admin password."
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml26(td)
+msgid "admin_username = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml30(td)
+msgid "async_requests = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml35(td)
+msgid "(StrOpt) Dummy user traffic Security Zone id for LBs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml43(td)
+msgid "(StrOpt) In band Security Zone id for LBs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml46(td)
+msgid "lb_flavor = small"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml47(td)
+msgid "(StrOpt) choose LB image flavor to use, accepted values: small, medium"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml50(td)
+msgid "lb_image = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml51(td)
+msgid "(StrOpt) Load Balancer image id (Embrane LB)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml55(td)
+msgid "(StrOpt) Management Security Zone id for LBs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml59(td)
+msgid "(StrOpt) Out of band Security Zone id for LBs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml66(td)
+msgid "sync_interval = 60"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml67(td)
+msgid "(IntOpt) resource synchronization interval in seconds"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml7(literal)
+msgid "[filter:authtoken]"
+msgstr "[filter:authtoken]"
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml18(td)
+msgid "auth_host = keystonehost"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml24(td)
+msgid "auth_protocol = http"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml27(td)
+msgid "auth_uri = http://keystonehost:5000/"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml30(td)
+msgid "admin_tenant_name = service"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml33(td)
+msgid "admin_user = swift"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml36(td)
+msgid "admin_password = password"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml39(td)
+msgid "delay_auth_decision = 1"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml42(td)
+msgid "cache = swift.cache"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml45(td)
+msgid "include_service_catalog = False"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-pipeline-main.xml18(td)
+msgid "pipeline = healthcheck recon object-server"
+msgstr "pipeline = healthcheck recon object-server"
+
+#: ./doc/common/tables/swift-memcache-memcache.xml7(literal)
+#: ./doc/common/tables/keystone-memcache.xml19(th)
+msgid "[memcache]"
+msgstr "[memcache]"
+
+#: ./doc/common/tables/swift-memcache-memcache.xml7(literal)
+msgid "memcache.conf-sample"
+msgstr "memcache.conf-sample"
+
+#: ./doc/common/tables/swift-account-server-app-account-server.xml7(literal)
+msgid "[app:account-server]"
+msgstr "[app:account-server]"
+
+#: ./doc/common/tables/swift-account-server-app-account-server.xml18(td)
+msgid "use = egg:swift#account"
+msgstr "use = egg:swift#account"
+
+#: ./doc/common/tables/swift-account-server-app-account-server.xml21(td)
+msgid "set log_name = account-server"
+msgstr "set log_name = account-server"
+
+#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml7(literal)
+msgid "[filter:formpost]"
+msgstr "[filter:formpost]"
+
+#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml18(td)
+msgid "use = egg:swift#formpost"
+msgstr ""
+
+#: ./doc/common/tables/trove-compute.xml22(td)
+msgid "ip_regex = None"
+msgstr "ip_regex = None"
+
+#: ./doc/common/tables/trove-compute.xml26(td)
+msgid "nova_compute_url = http://localhost:8774/v2"
+msgstr "nova_compute_url = http://localhost:8774/v2"
+
+#: ./doc/common/tables/trove-compute.xml30(td)
+msgid "root_grant = ALL"
+msgstr "root_grant = ALL"
+
+#: ./doc/common/tables/trove-compute.xml34(td)
+msgid "root_grant_option = True"
+msgstr "root_grant_option = True"
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml7(literal)
+msgid "[filter:proxy-logging]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml18(td)
+msgid "use = egg:swift#proxy_logging"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml21(td)
+msgid "access_log_name = swift"
+msgstr "access_log_name = swift"
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml24(td)
+msgid "access_log_facility = LOG_LOCAL0"
+msgstr "access_log_facility = LOG_LOCAL0"
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml27(td)
+msgid "access_log_level = INFO"
+msgstr "access_log_level = INFO"
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml30(td)
+msgid "access_log_address = /dev/log"
+msgstr "access_log_address = /dev/log"
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml33(td)
+msgid "access_log_udp_host ="
+msgstr "access_log_udp_host ="
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml36(td)
+msgid "access_log_udp_port = 514"
+msgstr "access_log_udp_port = 514"
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml39(td)
+msgid "access_log_statsd_host = localhost"
+msgstr "access_log_statsd_host = localhost"
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml42(td)
+msgid "access_log_statsd_port = 8125"
+msgstr "access_log_statsd_port = 8125"
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml45(td)
+msgid "access_log_statsd_default_sample_rate = 1.0"
+msgstr "access_log_statsd_default_sample_rate = 1.0"
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml48(td)
+msgid "access_log_statsd_sample_rate_factor = 1.0"
+msgstr "access_log_statsd_sample_rate_factor = 1.0"
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml51(td)
+msgid "access_log_statsd_metric_prefix ="
+msgstr "access_log_statsd_metric_prefix ="
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml54(td)
+msgid "access_log_headers = false"
+msgstr "access_log_headers = false"
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml57(td)
+msgid "access_log_headers_only ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml60(td)
+msgid "logged with access_log_headers = True."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml63(td)
+msgid "reveal_sensitive_prefix = 8192"
+msgstr "reveal_sensitive_prefix = 8192"
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml63(td)
+msgid ""
+"The X-Auth-Token is sensitive data. If revealed to an unauthorised person, "
+"they can now make requests against an account until the token expires. Set "
+"reveal_sensitive_prefix to the number of characters of the token that are "
+"logged. For example reveal_sensitive_prefix = 12 so only first 12 characters"
+" of the token are logged. Or, set to 0 to completely remove the token."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml72(td)
+msgid "log_statsd_valid_http_methods = GET,HEAD,POST,PUT,DELETE,COPY,OPTIONS"
+msgstr "log_statsd_valid_http_methods = GET,HEAD,POST,PUT,DELETE,COPY,OPTIONS"
+
+#: ./doc/common/tables/trove-db_redis.xml8(caption)
+msgid "Description of configuration options for db_redis"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_redis.xml19(th)
+msgid "[redis]"
+msgstr "[redis]"
+
+#: ./doc/common/tables/trove-db_redis.xml26(td)
+msgid "mount_point = /var/lib/redis"
+msgstr "mount_point = /var/lib/redis"
+
+#: ./doc/common/tables/trove-db_redis.xml30(td)
+msgid "tcp_ports = 6379"
+msgstr "tcp_ports = 6379"
+
+#: ./doc/common/tables/cinder-rpc.xml38(td)
+msgid "default_timeout = 20"
+msgstr ""
+
+#: ./doc/common/tables/cinder-rpc.xml39(td)
+msgid "(IntOpt) Default Time Out For CLI operations in minutes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-rpc.xml234(td)
+msgid "volume_topic = cinder-volume"
+msgstr "volume_topic = cinder-volume"
+
+#: ./doc/common/tables/cinder-rpc.xml235(td)
+msgid "(StrOpt) the topic volume nodes listen on"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml7(literal)
+msgid "[realm2]"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml18(td)
+msgid "key = realm2key"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml21(td)
+msgid "key2 = realm2key2"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml24(td)
+msgid "cluster_name3 = https://host3/v1/"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml27(td)
+msgid "cluster_name4 = https://host4/v1/"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hpmsa.xml8(caption)
+msgid "Description of configuration options for hpmsa"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hpmsa.xml22(td)
+msgid "msa_vdisk = OpenStack"
+msgstr "msa_vdisk = OpenStack"
+
+#: ./doc/common/tables/cinder-hpmsa.xml23(td)
+msgid "(StrOpt) The VDisk to use for volume creation."
+msgstr ""
+
+#: ./doc/common/tables/nova-apiv3.xml8(caption)
+msgid "Description of configuration options for apiv3"
+msgstr ""
+
+#: ./doc/common/tables/nova-apiv3.xml19(th)
+msgid "[osapi_v3]"
+msgstr ""
+
+#: ./doc/common/tables/nova-apiv3.xml23(td)
+msgid "(BoolOpt) Whether the V3 API is enabled or not"
+msgstr ""
+
+#: ./doc/common/tables/nova-apiv3.xml26(td)
+msgid "extensions_blacklist ="
+msgstr ""
+
+#: ./doc/common/tables/nova-apiv3.xml27(td)
+msgid ""
+"(ListOpt) A list of v3 API extensions to never load. Specify the extension "
+"aliases here."
+msgstr ""
+
+#: ./doc/common/tables/nova-apiv3.xml30(td)
+msgid "extensions_whitelist ="
+msgstr ""
+
+#: ./doc/common/tables/nova-apiv3.xml31(td)
+msgid ""
+"(ListOpt) If the list is not empty then a v3 API extension will only be "
+"loaded if it exists in this list. Specify the extension aliases here."
+msgstr ""
+
+#: ./doc/common/tables/keystone-oauth.xml8(caption)
+msgid "Description of configuration options for oauth"
+msgstr ""
+
+#: ./doc/common/tables/keystone-oauth.xml19(th)
+msgid "[oauth1]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-oauth.xml22(td)
+msgid "access_token_duration = 86400"
+msgstr ""
+
+#: ./doc/common/tables/keystone-oauth.xml23(td)
+msgid "(IntOpt) Duration (in seconds) for the OAuth Access Token."
+msgstr ""
+
+#: ./doc/common/tables/keystone-oauth.xml26(td)
+msgid "driver = keystone.contrib.oauth1.backends.sql.OAuth1"
+msgstr ""
+
+#: ./doc/common/tables/keystone-oauth.xml27(td)
+#: ./doc/common/tables/keystone-credential.xml23(td)
+msgid "(StrOpt) Keystone Credential backend driver."
+msgstr ""
+
+#: ./doc/common/tables/keystone-oauth.xml30(td)
+msgid "request_token_duration = 28800"
+msgstr ""
+
+#: ./doc/common/tables/keystone-oauth.xml31(td)
+msgid "(IntOpt) Duration (in seconds) for the OAuth Request Token."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml8(caption)
+msgid "Description of configuration options for storage_gpfs"
+msgstr "Description des options de configuration pour storage_gpfs"
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml22(td)
+msgid "gpfs_images_dir = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml23(td)
+msgid ""
+"(StrOpt) Specifies the path of the Image service repository in GPFS. Leave "
+"undefined if not storing images in GPFS."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml26(td)
+msgid "gpfs_images_share_mode = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml27(td)
+msgid ""
+"(StrOpt) Specifies the type of image copy to be used. Set this when the "
+"Image service repository also uses GPFS so that image files can be "
+"transferred efficiently from the Image service to the Block Storage service."
+" There are two valid values: \"copy\" specifies that a full copy of the "
+"image is made; \"copy_on_write\" specifies that copy-on-write optimization "
+"strategy is used and unmodified blocks of the image file are shared "
+"efficiently."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml30(td)
+msgid "gpfs_max_clone_depth = 0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml31(td)
+msgid ""
+"(IntOpt) Specifies an upper limit on the number of indirections required to "
+"reach a specific block due to snapshots or clones. A lengthy chain of copy-"
+"on-write snapshots or clones can have a negative impact on performance, but "
+"improves space utilization. 0 indicates unlimited clone depth."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml34(td)
+msgid "gpfs_mount_point_base = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml35(td)
+msgid ""
+"(StrOpt) Specifies the path of the GPFS directory where Block Storage volume"
+" and snapshot files are stored."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml38(td)
+msgid "gpfs_sparse_volumes = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml39(td)
+msgid ""
+"(BoolOpt) Specifies that volumes are created as sparse files which initially"
+" consume no space. If set to False, the volume is created as a fully "
+"allocated file, in which case, creation may take a significantly longer "
+"time."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml42(td)
+msgid "gpfs_storage_pool = None"
+msgstr "gpfs_storage_pool = None"
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml43(td)
+msgid ""
+"(StrOpt) Specifies the storage pool that volumes are assigned to. By "
+"default, the system storage pool is used."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_vlan.xml8(caption)
+msgid "Description of configuration options for ml2_vlan"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_vlan.xml19(th)
+msgid "[ml2_type_vlan]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_vlan.xml23(td)
+msgid ""
+"(ListOpt) List of &lt;physical_network&gt;:&lt;vlan_min&gt;:&lt;vlan_max&gt;"
+" or &lt;physical_network&gt; specifying physical_network names usable for "
+"VLAN provider and tenant networks, as well as ranges of VLAN tags on each "
+"available for allocation to tenant networks."
+msgstr ""
+
+#: ./doc/common/tables/keystone-notification.xml23(td)
+msgid ""
+"(StrOpt) onready allows you to send a notification when the process is ready"
+" to serve For example, to have it notify using systemd, one could set shell "
+"command: \"onready = systemd-notify --ready\" or a module with notify() "
+"method: \"onready = keystone.common.systemd\"."
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml7(literal)
+msgid "[object-auditor]"
+msgstr "[object-auditor]"
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml18(td)
+msgid "log_name = object-auditor"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml30(td)
+msgid "files_per_second = 20"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml30(td)
+msgid ""
+"Maximum files audited per second. Should be tuned according to individual "
+"system specs. 0 is unlimited."
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml33(td)
+msgid "bytes_per_second = 10000000"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml33(td)
+msgid ""
+"Maximum bytes audited per second. Should be tuned according to individual "
+"system specs. 0 is unlimited. mounted to prevent accidentally writing to the"
+" root device process simultaneously (it will actually accept(2) N + 1). "
+"Setting this to one (1) will only handle one request at a time, without "
+"accepting another request concurrently. By increasing the number of workers "
+"to a much higher value, one can reduce the impact of slow file system "
+"operations in one request from negatively impacting other requests. "
+"underlying filesystem does not support it. to setup custom log handlers. "
+"bytes you'd like fallocate to reserve, whether there is space for the given "
+"file size or not. This is useful for systems that behave badly when they "
+"completely run out of space; you can make the services pretend they're out "
+"of space early. container server. For most cases, this should be "
+"`egg:swift#container`."
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml36(td)
+msgid "log_time = 3600"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml36(td)
+msgid "Frequency of status logs in seconds."
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml39(td)
+msgid "zero_byte_files_per_second = 50"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml39(td)
+msgid "Maximum zero byte files audited per second."
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml45(td)
+msgid "object_size_stats ="
+msgstr ""
+
+#: ./doc/common/tables/trove-zeromq.xml38(td)
+msgid ""
+"rpc_zmq_matchmaker = "
+"trove.openstack.common.rpc.matchmaker.MatchMakerLocalhost"
 msgstr ""
 
 #: ./doc/common/tables/neutron-lbaas.xml8(caption)
@@ -39340,4052 +44221,6 @@ msgstr ""
 msgid "(StrOpt) Swift user name"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_cisco.xml8(caption)
-msgid "Description of configuration options for ml2_cisco"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_cisco.xml19(th)
-#: ./doc/common/tables/neutron-cisco.xml119(th)
-msgid "[ml2_cisco]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_cisco.xml22(td)
-msgid "managed_physical_network = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_cisco.xml23(td)
-msgid "(StrOpt) The physical network managed by the switches."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml26(td)
-msgid "dispatcher = ['database']"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml27(td)
-msgid "(MultiStrOpt) Dispatcher to process data."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml30(td)
-msgid "rpc_backend = ceilometer.openstack.common.rpc.impl_kombu"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml66(td)
-msgid ""
-"rpc_zmq_matchmaker = "
-"ceilometer.openstack.common.rpc.matchmaker.MatchMakerLocalhost"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml78(th)
-msgid "[publisher]"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml81(td)
-msgid "metering_secret = change this or be hacked"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml82(td)
-msgid "(StrOpt) Secret value for signing metering messages."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml85(th)
-msgid "[publisher_rpc]"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml88(td)
-msgid "metering_topic = metering"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml89(td)
-msgid "(StrOpt) The topic that ceilometer uses for metering messages."
-msgstr ""
-
-#: ./doc/common/tables/heat-loadbalancer.xml8(caption)
-msgid "Description of configuration options for loadbalancer"
-msgstr ""
-
-#: ./doc/common/tables/heat-loadbalancer.xml22(td)
-msgid "loadbalancer_template = None"
-msgstr "loadbalancer_template = None"
-
-#: ./doc/common/tables/heat-loadbalancer.xml23(td)
-msgid "(StrOpt) Custom template for the built-in loadbalancer nested stack."
-msgstr ""
-
-#: ./doc/common/tables/heat-cloudwatch_api.xml8(caption)
-msgid "Description of configuration options for cloudwatch_api"
-msgstr ""
-
-#: ./doc/common/tables/heat-cloudwatch_api.xml22(td)
-#: ./doc/common/tables/heat-api.xml34(td)
-msgid "heat_watch_server_url ="
-msgstr "heat_watch_server_url ="
-
-#: ./doc/common/tables/heat-cloudwatch_api.xml23(td)
-#: ./doc/common/tables/heat-api.xml35(td)
-msgid "(StrOpt) URL of the Heat CloudWatch server."
-msgstr ""
-
-#: ./doc/common/tables/heat-cloudwatch_api.xml26(th)
-msgid "[heat_api_cloudwatch]"
-msgstr "[heat_api_cloudwatch]"
-
-#: ./doc/common/tables/heat-cloudwatch_api.xml37(td)
-msgid "bind_port = 8003"
-msgstr "bind_port = 8003"
-
-#: ./doc/common/tables/heat-cloudwatch_api.xml50(td)
-msgid ""
-"(IntOpt) Maximum line size of message headers to be accepted. "
-"max_header_line may need to be increased when using large tokens (typically "
-"those generated by the Keystone v3 API with big service catalogs.)"
-msgstr ""
-
-#: ./doc/common/tables/nova-pci.xml8(caption)
-msgid "Description of configuration options for pci"
-msgstr ""
-
-#: ./doc/common/tables/nova-pci.xml22(td)
-msgid "pci_alias = []"
-msgstr ""
-
-#: ./doc/common/tables/nova-pci.xml23(td)
-msgid ""
-"(MultiStrOpt) An alias for a PCI passthrough device requirement. This allows"
-" users to specify the alias in the extra_spec for a flavor, without needing "
-"to repeat all the PCI property requirements. For example: pci_alias = { "
-"\"name\": \"QuicAssist\", \"product_id\": \"0443\", \"vendor_id\": \"8086\","
-" \"device_type\": \"ACCEL\" } defines an alias for the Intel QuickAssist "
-"card. (multi valued)"
-msgstr ""
-
-#: ./doc/common/tables/nova-pci.xml26(td)
-msgid "pci_passthrough_whitelist = []"
-msgstr ""
-
-#: ./doc/common/tables/nova-pci.xml27(td)
-msgid ""
-"(MultiStrOpt) White list of PCI devices available to VMs. For example: "
-"pci_passthrough_whitelist = [{\"vendor_id\": \"8086\", \"product_id\": "
-"\"0443\"}]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml7(literal)
-msgid "[filter:proxy-logging]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml18(td)
-msgid "use = egg:swift#proxy_logging"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml21(td)
-msgid "access_log_name = swift"
-msgstr "access_log_name = swift"
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml24(td)
-msgid "access_log_facility = LOG_LOCAL0"
-msgstr "access_log_facility = LOG_LOCAL0"
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml27(td)
-msgid "access_log_level = INFO"
-msgstr "access_log_level = INFO"
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml30(td)
-msgid "access_log_address = /dev/log"
-msgstr "access_log_address = /dev/log"
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml33(td)
-msgid "access_log_udp_host ="
-msgstr "access_log_udp_host ="
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml36(td)
-msgid "access_log_udp_port = 514"
-msgstr "access_log_udp_port = 514"
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml39(td)
-msgid "access_log_statsd_host = localhost"
-msgstr "access_log_statsd_host = localhost"
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml42(td)
-msgid "access_log_statsd_port = 8125"
-msgstr "access_log_statsd_port = 8125"
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml45(td)
-msgid "access_log_statsd_default_sample_rate = 1.0"
-msgstr "access_log_statsd_default_sample_rate = 1.0"
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml48(td)
-msgid "access_log_statsd_sample_rate_factor = 1.0"
-msgstr "access_log_statsd_sample_rate_factor = 1.0"
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml51(td)
-msgid "access_log_statsd_metric_prefix ="
-msgstr "access_log_statsd_metric_prefix ="
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml54(td)
-msgid "access_log_headers = false"
-msgstr "access_log_headers = false"
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml57(td)
-msgid "access_log_headers_only ="
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml60(td)
-msgid "logged with access_log_headers = True."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml63(td)
-msgid "reveal_sensitive_prefix = 8192"
-msgstr "reveal_sensitive_prefix = 8192"
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml63(td)
-msgid ""
-"The X-Auth-Token is sensitive data. If revealed to an unauthorised person, "
-"they can now make requests against an account until the token expires. Set "
-"reveal_sensitive_prefix to the number of characters of the token that are "
-"logged. For example reveal_sensitive_prefix = 12 so only first 12 characters"
-" of the token are logged. Or, set to 0 to completely remove the token."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml72(td)
-msgid "log_statsd_valid_http_methods = GET,HEAD,POST,PUT,DELETE,COPY,OPTIONS"
-msgstr "log_statsd_valid_http_methods = GET,HEAD,POST,PUT,DELETE,COPY,OPTIONS"
-
-#: ./doc/common/tables/heat-clients_ceilometer.xml8(caption)
-msgid "Description of configuration options for clients_ceilometer"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_ceilometer.xml19(th)
-msgid "[clients_ceilometer]"
-msgstr "[clients_ceilometer]"
-
-#: ./doc/common/tables/neutron-varmour.xml8(caption)
-msgid "Description of configuration options for varmour"
-msgstr ""
-
-#: ./doc/common/tables/neutron-varmour.xml19(th)
-msgid "[vArmour]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-varmour.xml22(td)
-msgid "director = localhost"
-msgstr ""
-
-#: ./doc/common/tables/neutron-varmour.xml23(td)
-msgid "(StrOpt) vArmour director ip"
-msgstr ""
-
-#: ./doc/common/tables/neutron-varmour.xml26(td)
-msgid "director_port = 443"
-msgstr ""
-
-#: ./doc/common/tables/neutron-varmour.xml27(td)
-msgid "(StrOpt) vArmour director port"
-msgstr ""
-
-#: ./doc/common/tables/neutron-varmour.xml30(td)
-msgid "password = varmour"
-msgstr ""
-
-#: ./doc/common/tables/neutron-varmour.xml31(td)
-msgid "(StrOpt) vArmour director password"
-msgstr ""
-
-#: ./doc/common/tables/neutron-varmour.xml34(td)
-msgid "username = varmour"
-msgstr ""
-
-#: ./doc/common/tables/neutron-varmour.xml35(td)
-msgid "(StrOpt) vArmour director username"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml8(caption)
-msgid "Description of configuration options for imagecache"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml22(td)
-msgid "cleanup_scrubber = False"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml23(td)
-msgid ""
-"(BoolOpt) A boolean that determines if the scrubber should clean up the "
-"files it uses for taking data. Only one server in your deployment should be "
-"designated the cleanup host."
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml26(td)
-msgid "cleanup_scrubber_time = 86400"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml27(td)
-msgid ""
-"(IntOpt) Items must have a modified time that is older than this value in "
-"order to be candidates for cleanup."
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml30(td)
-msgid "delayed_delete = False"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml31(td)
-msgid "(BoolOpt) Turn on/off delayed delete."
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml34(td)
-msgid "image_cache_dir = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml35(td)
-msgid "(StrOpt) Base directory that the Image Cache uses."
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml38(td)
-msgid "image_cache_driver = sqlite"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml39(td)
-msgid "(StrOpt) The driver to use for image cache management."
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml42(td)
-msgid "image_cache_max_size = 10737418240"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml43(td)
-msgid "(IntOpt) The maximum size in bytes that the cache can use."
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml46(td)
-msgid "image_cache_sqlite_db = cache.db"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml47(td)
-msgid ""
-"(StrOpt) The path to the sqlite file database that will be used for image "
-"cache management."
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml50(td)
-msgid "image_cache_stall_time = 86400"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml51(td)
-msgid ""
-"(IntOpt) The amount of time to let an image remain in the cache without "
-"being accessed."
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml54(td)
-msgid "scrub_time = 0"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml55(td)
-msgid ""
-"(IntOpt) The amount of time in seconds to delay before performing a delete."
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml58(td)
-msgid "scrubber_datadir = /var/lib/glance/scrubber"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml59(td)
-msgid ""
-"(StrOpt) Directory that the scrubber will use to track information about "
-"what to delete. Make sure this is set in glance-api.conf and glance-"
-"scrubber.conf."
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml22(td)
-msgid "max_accepted_volume_size = 5"
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml23(td)
-msgid "(IntOpt) Default maximum volume size for an instance."
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml26(td)
-msgid "max_backups_per_user = 50"
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml27(td)
-msgid "(IntOpt) Default maximum number of backups created by a tenant."
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml30(td)
-msgid "max_instances_per_user = 5"
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml31(td)
-msgid "(IntOpt) Default maximum number of instances per tenant."
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml34(td)
-msgid "max_volumes_per_user = 20"
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml35(td)
-msgid ""
-"(IntOpt) Default maximum volume capacity (in GB) spanning across all trove "
-"volumes per tenant"
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml38(td)
-msgid "quota_driver = trove.quota.quota.DbQuotaDriver"
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml39(td)
-msgid "(StrOpt) Default driver to use for quota checks."
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-account.xml7(literal)
-msgid "[account]"
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-account.xml18(td)
-msgid "max connections = 2"
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-account.xml27(td)
-msgid "lock file = /var/lock/account.lock"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml8(caption)
-msgid "Description of configuration options for storage"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml22(td)
-msgid "allocated_capacity_weight_multiplier = -1.0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml23(td)
-#: ./doc/common/tables/cinder-storage.xml27(td)
-msgid ""
-"(FloatOpt) Multiplier used for weighing volume capacity. Negative numbers "
-"mean to stack vs spread."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml26(td)
-msgid "capacity_weight_multiplier = 1.0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml30(td)
-msgid "enabled_backends = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml31(td)
-msgid ""
-"(ListOpt) A list of backend names to use. These backend names should be "
-"backed by a unique [CONFIG] group with its options"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml34(td)
-msgid "iscsi_helper = tgtadm"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml35(td)
-msgid "(StrOpt) iscsi target user-land tool to use"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml38(td)
-msgid "iscsi_iotype = fileio"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml39(td)
-msgid ""
-"(StrOpt) Sets the behavior of the iSCSI target to either perform blockio or "
-"fileio optionally, auto can be set and Cinder will autodetect type of "
-"backing device"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml42(td)
-msgid "iscsi_ip_address = $my_ip"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml43(td)
-msgid "(StrOpt) The IP address that the iSCSI daemon is listening on"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml46(td)
-msgid "iscsi_num_targets = 100"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml47(td)
-msgid "(IntOpt) The maximum number of iscsi target ids per host"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml50(td)
-msgid "iscsi_port = 3260"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml51(td)
-msgid "(IntOpt) The port that the iSCSI daemon is listening on"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml54(td)
-msgid "iscsi_target_prefix = iqn.2010-10.org.openstack:"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml55(td)
-msgid "(StrOpt) prefix for iscsi volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml58(td)
-msgid "iser_helper = tgtadm"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml59(td)
-msgid "(StrOpt) iser target user-land tool to use"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml62(td)
-msgid "iser_ip_address = $my_ip"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml63(td)
-msgid "(StrOpt) The IP address that the iSER daemon is listening on"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml66(td)
-msgid "iser_num_targets = 100"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml67(td)
-msgid "(IntOpt) The maximum number of iser target ids per host"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml70(td)
-msgid "iser_port = 3260"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml71(td)
-msgid "(IntOpt) The port that the iSER daemon is listening on"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml74(td)
-msgid "iser_target_prefix = iqn.2010-10.org.iser.openstack:"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml75(td)
-msgid "(StrOpt) prefix for iser volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml78(td)
-msgid "max_gigabytes = 10000"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml79(td)
-msgid ""
-"(IntOpt) This configure option has been deprecated along with the "
-"SimpleScheduler. New scheduler is able to gather capacity information for "
-"each host, thus setting the maximum number of volume gigabytes for host is "
-"no longer needed. It's safe to remove this configure from cinder.conf."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml82(td)
-msgid "migration_create_volume_timeout_secs = 300"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml83(td)
-msgid ""
-"(IntOpt) Timeout for creating the volume to migrate to when performing "
-"volume migration (seconds)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml86(td)
-msgid "num_iser_scan_tries = 3"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml87(td)
-msgid ""
-"(IntOpt) The maximum number of times to rescan iSER targetto find volume"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml90(td)
-msgid "num_volume_device_scan_tries = 3"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml91(td)
-msgid "(IntOpt) The maximum number of times to rescan targets to find volume"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml94(td)
-msgid "volume_backend_name = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml95(td)
-msgid "(StrOpt) The backend name for a given driver implementation"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml99(td)
-msgid ""
-"(StrOpt) Method used to wipe old voumes (valid options are: none, zero, "
-"shred)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml102(td)
-msgid "volume_clear_ionice = None"
-msgstr "volume_clear_ionice = None"
-
-#: ./doc/common/tables/cinder-storage.xml103(td)
-msgid ""
-"(StrOpt) The flag to pass to ionice to alter the i/o priority of the process"
-" used to zero a volume after deletion, for example \"-c3\" for idle only "
-"priority."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml110(td)
-msgid "volume_dd_blocksize = 1M"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml111(td)
-msgid "(StrOpt) The default block size used when copying/clearing volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml114(td)
-msgid "volume_driver = cinder.volume.drivers.lvm.LVMISCSIDriver"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml115(td)
-msgid "(StrOpt) Driver to use for volume creation"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml118(td)
-msgid "volume_manager = cinder.volume.manager.VolumeManager"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml119(td)
-msgid "(StrOpt) full class name for the Manager for volume"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml122(td)
-msgid "volume_service_inithost_offload = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml123(td)
-msgid "(BoolOpt) Offload pending volume delete during volume service startup"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml126(td)
-msgid "volume_usage_audit_period = month"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml127(td)
-msgid ""
-"(StrOpt) time period to generate volume usages for. Time period must be "
-"hour, day, month or year"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml130(td)
-msgid "volumes_dir = $state_path/volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml131(td)
-msgid "(StrOpt) Volume configuration file storage directory"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml145(td)
-msgid "max_pool_size = 5"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nas.xml8(caption)
-msgid "Description of configuration options for nas"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nas.xml22(td)
-msgid "nas_ip ="
-msgstr "nas_ip ="
-
-#: ./doc/common/tables/cinder-nas.xml23(td)
-msgid "(StrOpt) IP address or Hostname of NAS system."
-msgstr ""
-
-#: ./doc/common/tables/cinder-nas.xml26(td)
-msgid "nas_login = admin"
-msgstr "nas_login = admin"
-
-#: ./doc/common/tables/cinder-nas.xml27(td)
-msgid "(StrOpt) User name to connect to NAS system."
-msgstr ""
-
-#: ./doc/common/tables/cinder-nas.xml30(td)
-msgid "nas_password ="
-msgstr "nas_password ="
-
-#: ./doc/common/tables/cinder-nas.xml31(td)
-msgid "(StrOpt) Password to connect to NAS system."
-msgstr ""
-
-#: ./doc/common/tables/cinder-nas.xml34(td)
-msgid "nas_private_key ="
-msgstr "nas_private_key ="
-
-#: ./doc/common/tables/cinder-nas.xml35(td)
-msgid "(StrOpt) Filename of private key to use for SSH authentication."
-msgstr ""
-
-#: ./doc/common/tables/cinder-nas.xml38(td)
-msgid "nas_ssh_port = 22"
-msgstr "nas_ssh_port = 22"
-
-#: ./doc/common/tables/cinder-nas.xml39(td)
-msgid "(IntOpt) SSH port to use to connect to NAS system."
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml8(caption)
-#: ./doc/common/tables/neutron-vpn.xml8(caption)
-msgid "Description of configuration options for vpn"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml22(td)
-msgid "boot_script_template = $pybasedir/nova/cloudpipe/bootscript.template"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml23(td)
-msgid "(StrOpt) Template for cloudpipe instance boot script"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml26(td)
-msgid "dmz_cidr ="
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml27(td)
-msgid "(ListOpt) A list of dmz range that should be accepted"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml30(td)
-msgid "dmz_mask = 255.255.255.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml31(td)
-msgid "(StrOpt) Netmask to push into openvpn config"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml34(td)
-msgid "dmz_net = 10.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml35(td)
-msgid "(StrOpt) Network to push into openvpn config"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml38(td)
-msgid "vpn_flavor = m1.tiny"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml39(td)
-msgid "(StrOpt) Flavor for vpn instances"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml42(td)
-msgid "vpn_image_id = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml43(td)
-msgid "(StrOpt) Image ID used when starting up a cloudpipe vpn server"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml46(td)
-msgid "vpn_ip = $my_ip"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml47(td)
-msgid "(StrOpt) Public IP for the cloudpipe VPN servers"
-msgstr "Adresse IP publique des serveurs VPN cloudpipe"
-
-#: ./doc/common/tables/nova-vpn.xml50(td)
-msgid "vpn_key_suffix = -vpn"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml51(td)
-msgid "(StrOpt) Suffix to add to project name for vpn key and secgroups"
-msgstr "(StrOpt)  Suffixe à ajouter au nom du projet pour les clés et secgroups de VPN"
-
-#: ./doc/common/tables/nova-vpn.xml54(td)
-msgid "vpn_start = 1000"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml55(td)
-msgid "(IntOpt) First Vpn port for private networks"
-msgstr "(IntOpt) Premier port VPN des réseaux privés"
-
-#: ./doc/common/tables/nova-wsgi.xml23(td)
-msgid "(StrOpt) File name for the paste.deploy config for nova-api"
-msgstr "(StrOpt)  Nom du fichier pour la config paste.deploy de nova-api"
-
-#: ./doc/common/tables/nova-wsgi.xml26(td)
-#: ./doc/common/tables/cinder-common.xml174(td)
-#: ./doc/common/tables/neutron-ssl.xml22(td)
-msgid "ssl_ca_file = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-wsgi.xml30(td)
-#: ./doc/common/tables/cinder-common.xml178(td)
-#: ./doc/common/tables/neutron-ssl.xml26(td)
-msgid "ssl_cert_file = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-wsgi.xml31(td)
-msgid "(StrOpt) SSL certificate of API server"
-msgstr "(StrOpt)  Certificat SSL de l'API du serveur"
-
-#: ./doc/common/tables/nova-wsgi.xml34(td)
-#: ./doc/common/tables/cinder-common.xml182(td)
-#: ./doc/common/tables/neutron-ssl.xml30(td)
-msgid "ssl_key_file = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-wsgi.xml35(td)
-msgid "(StrOpt) SSL private key of API server"
-msgstr "(StrOpt)  Clé SSL privée de l'API du serveur"
-
-#: ./doc/common/tables/nova-wsgi.xml42(td)
-msgid "wsgi_default_pool_size = 1000"
-msgstr ""
-
-#: ./doc/common/tables/nova-wsgi.xml43(td)
-msgid "(IntOpt) Size of the pool of greenthreads used by wsgi"
-msgstr ""
-
-#: ./doc/common/tables/nova-wsgi.xml46(td)
-msgid ""
-"wsgi_log_format = %(client_ip)s \"%(request_line)s\" status: %(status_code)s"
-" len: %(body_length)s time: %(wall_seconds).7f"
-msgstr ""
-
-#: ./doc/common/tables/nova-wsgi.xml47(td)
-msgid ""
-"(StrOpt) A python format string that is used as the template to generate log"
-" lines. The following values can be formatted into it: client_ip, date_time,"
-" request_line, status_code, body_length, wall_seconds."
-msgstr "(StrOpt)  Une chaîne de formatage Python utilisée en tant que template pour générer les journaux. Les valeurs suivantes peuvent être utilisées : client_ip, date_time, request_line, status_code, body_length, wall_seconds."
-
-#: ./doc/common/tables/cinder-storage_glusterfs.xml8(caption)
-msgid "Description of configuration options for storage_glusterfs"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_glusterfs.xml23(td)
-msgid "(StrOpt) Base dir containing mount points for gluster shares."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_glusterfs.xml26(td)
-msgid "glusterfs_qcow2_volumes = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_glusterfs.xml27(td)
-msgid "(BoolOpt) Create volumes as QCOW2 files rather than raw files."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_glusterfs.xml30(td)
-msgid "glusterfs_shares_config = /etc/cinder/glusterfs_shares"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_glusterfs.xml31(td)
-msgid "(StrOpt) File with the list of available gluster shares"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_glusterfs.xml34(td)
-msgid "glusterfs_sparsed_volumes = True"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml7(literal)
-msgid "[realm1]"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml7(literal)
-#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml7(literal)
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml7(literal)
-msgid "container-sync-realms.conf-sample"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml18(td)
-msgid "key = realm1key"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml21(td)
-msgid "key2 = realm1key2"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml24(td)
-msgid "cluster_name1 = https://host1/v1/"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml27(td)
-msgid "cluster_name2 = https://host2/v1/"
-msgstr ""
-
-#: ./doc/common/tables/nova-availabilityzones.xml8(caption)
-msgid "Description of configuration options for availabilityzones"
-msgstr ""
-
-#: ./doc/common/tables/nova-availabilityzones.xml22(td)
-msgid "default_availability_zone = nova"
-msgstr ""
-
-#: ./doc/common/tables/nova-availabilityzones.xml23(td)
-msgid "(StrOpt) Default compute node availability_zone"
-msgstr ""
-
-#: ./doc/common/tables/nova-availabilityzones.xml26(td)
-msgid "default_schedule_zone = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-availabilityzones.xml27(td)
-msgid "(StrOpt) Availability zone to use when user doesn't specify one"
-msgstr ""
-
-#: ./doc/common/tables/nova-availabilityzones.xml30(td)
-msgid "internal_service_availability_zone = internal"
-msgstr ""
-
-#: ./doc/common/tables/nova-availabilityzones.xml31(td)
-msgid "(StrOpt) The availability_zone to show internal services under"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml7(literal)
-msgid "[filter:container_sync]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml18(td)
-msgid "use = egg:swift#container_sync"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml21(td)
-msgid "allow_full_urls = true"
-msgstr ""
-
-#: ./doc/common/tables/heat-zeromq.xml38(td)
-msgid ""
-"rpc_zmq_matchmaker = "
-"heat.openstack.common.rpc.matchmaker.MatchMakerLocalhost"
-msgstr "rpc_zmq_matchmaker = heat.openstack.common.rpc.matchmaker.MatchMakerLocalhost"
-
-#: ./doc/common/tables/keystone-memcache.xml8(caption)
-msgid "Description of configuration options for memcache"
-msgstr ""
-
-#: ./doc/common/tables/keystone-memcache.xml19(th)
-#: ./doc/common/tables/swift-memcache-memcache.xml7(literal)
-msgid "[memcache]"
-msgstr "[memcache]"
-
-#: ./doc/common/tables/keystone-memcache.xml22(td)
-msgid "max_compare_and_set_retry = 16"
-msgstr ""
-
-#: ./doc/common/tables/keystone-memcache.xml23(td)
-msgid ""
-"(IntOpt) Number of compare-and-set attempts to make when using compare-and-"
-"set in the token memcache back end."
-msgstr ""
-
-#: ./doc/common/tables/keystone-memcache.xml26(td)
-msgid "servers = localhost:11211"
-msgstr ""
-
-#: ./doc/common/tables/keystone-memcache.xml27(td)
-msgid "(ListOpt) Memcache servers in the format of \"host:port\""
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml8(caption)
-msgid "Description of configuration options for vnc"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml22(td)
-msgid "novncproxy_base_url = http://127.0.0.1:6080/vnc_auto.html"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml23(td)
-msgid ""
-"(StrOpt) Location of VNC console proxy, in the form "
-"\"http://127.0.0.1:6080/vnc_auto.html\""
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml26(td)
-msgid "vnc_enabled = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml27(td)
-msgid "(BoolOpt) Enable VNC related features"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml30(td)
-msgid "vnc_keymap = en-us"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml31(td)
-msgid "(StrOpt) Keymap for VNC"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml34(td)
-msgid "vncserver_listen = 127.0.0.1"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml35(td)
-msgid "(StrOpt) IP address on which instance vncservers should listen"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml38(td)
-msgid "vncserver_proxyclient_address = 127.0.0.1"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml39(td)
-msgid ""
-"(StrOpt) The address to which proxy clients (like nova-xvpvncproxy) should "
-"connect"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml45(td)
-msgid "vnc_port = 5900"
-msgstr "vnc_port = 5900"
-
-#: ./doc/common/tables/nova-vnc.xml46(td)
-msgid "(IntOpt) VNC starting port"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml49(td)
-msgid "vnc_port_total = 10000"
-msgstr "vnc_port_total = 10000"
-
-#: ./doc/common/tables/nova-vnc.xml50(td)
-msgid "(IntOpt) Total number of VNC ports"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml7(literal)
-msgid "[swift-constraints]"
-msgstr "[swift-constraints]"
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml7(literal)
-#: ./doc/common/tables/swift-swift-swift-hash.xml7(literal)
-msgid "swift.conf-sample"
-msgstr "swift.conf-sample"
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml18(td)
-msgid "max_file_size = 5368709122"
-msgstr "max_file_size = 5368709122"
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml18(td)
-msgid ""
-"The largest normal object that can be saved in the cluster. This is also the"
-" limit on the size of each segment of a large object when using the large "
-"object manifest support. This value is set in bytes. Setting it to lower "
-"than 1MiB will cause some tests to fail. It is STRONGLY recommended to leave"
-" this value at the default (5 * 2**30 + 2)."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml29(td)
-msgid "max_meta_name_length = 128"
-msgstr "max_meta_name_length = 128"
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml29(td)
-msgid ""
-"The maximum number of bytes in the utf8 encoding of the name portion of a "
-"metadata header."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml34(td)
-msgid "max_meta_value_length = 256"
-msgstr "max_meta_value_length = 256"
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml34(td)
-msgid "The max number of bytes in the utf8 encoding of a metadata value."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml38(td)
-msgid "max_meta_count = 90"
-msgstr "max_meta_count = 90"
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml38(td)
-msgid ""
-"The maximum number of metadata keys that can be stored on a single account, "
-"container, or object."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml43(td)
-msgid "max_meta_overall_size = 4096"
-msgstr "max_meta_overall_size = 4096"
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml43(td)
-msgid ""
-"The maximum number of bytes in the utf8 encoding of the metadata (keys + "
-"values)."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml48(td)
-msgid "max_header_size = 8192"
-msgstr "max_header_size = 8192"
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml48(td)
-msgid "The maximum number of bytes in the utf8 encoding of each header."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml52(td)
-msgid "max_object_name_length = 1024"
-msgstr "max_object_name_length = 1024"
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml52(td)
-msgid "The maximum number of bytes in the utf8 encoding of an object name."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml56(td)
-msgid "container_listing_limit = 10000"
-msgstr "container_listing_limit = 10000"
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml56(td)
-msgid ""
-"The default (and maximum) number of items returned for a container listing "
-"request."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml61(td)
-msgid "account_listing_limit = 10000"
-msgstr "account_listing_limit = 10000"
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml61(td)
-msgid ""
-"The default (and maximum) number of items returned for an account listing "
-"request."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml65(td)
-msgid "max_account_name_length = 256"
-msgstr "max_account_name_length = 256"
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml65(td)
-msgid "The maximum number of bytes in the utf8 encoding of an account name."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml69(td)
-msgid "max_container_name_length = 256"
-msgstr "max_container_name_length = 256"
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml69(td)
-msgid "The maximum number of bytes in the utf8 encoding of a container name."
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml8(caption)
-msgid "Description of configuration options for cisco"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml19(th)
-msgid "[CISCO]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml22(td)
-msgid ""
-"model_class = "
-"neutron.plugins.cisco.models.virt_phy_sw_v2.VirtualPhysicalSwitchModelV2"
-msgstr "model_class = neutron.plugins.cisco.models.virt_phy_sw_v2.VirtualPhysicalSwitchModelV2 "
-
-#: ./doc/common/tables/neutron-cisco.xml23(td)
-msgid "(StrOpt) Model Class"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml26(td)
-msgid ""
-"nexus_driver = "
-"neutron.plugins.cisco.test.nexus.fake_nexus_driver.CiscoNEXUSFakeDriver"
-msgstr "nexus_driver = neutron.plugins.cisco.test.nexus.fake_nexus_driver.CiscoNEXUSFakeDriver"
-
-#: ./doc/common/tables/neutron-cisco.xml27(td)
-msgid "(StrOpt) Nexus Driver Name"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml30(td)
-msgid "nexus_l3_enable = False"
-msgstr "nexus_l3_enable = False"
-
-#: ./doc/common/tables/neutron-cisco.xml31(td)
-msgid "(BoolOpt) Enable L3 support on the Nexus switches"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml34(td)
-msgid "provider_vlan_auto_create = True"
-msgstr "provider_vlan_auto_create = True"
-
-#: ./doc/common/tables/neutron-cisco.xml35(td)
-msgid ""
-"(BoolOpt) Provider VLANs are automatically created as needed on the Nexus "
-"switch"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml38(td)
-msgid "provider_vlan_auto_trunk = True"
-msgstr "provider_vlan_auto_trunk = True"
-
-#: ./doc/common/tables/neutron-cisco.xml39(td)
-msgid ""
-"(BoolOpt) Provider VLANs are automatically trunked as needed on the ports of"
-" the Nexus switch"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml42(td)
-msgid "provider_vlan_name_prefix = p-"
-msgstr "provider_vlan_name_prefix = p-"
-
-#: ./doc/common/tables/neutron-cisco.xml43(td)
-msgid "(StrOpt) VLAN Name prefix for provider vlans"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml46(td)
-#: ./doc/common/tables/neutron-cisco.xml122(td)
-msgid "svi_round_robin = False"
-msgstr "svi_round_robin = False"
-
-#: ./doc/common/tables/neutron-cisco.xml47(td)
-#: ./doc/common/tables/neutron-cisco.xml123(td)
-msgid "(BoolOpt) Distribute SVI interfaces over all switches"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml50(td)
-#: ./doc/common/tables/neutron-cisco.xml126(td)
-msgid "vlan_name_prefix = q-"
-msgstr "vlan_name_prefix = q-"
-
-#: ./doc/common/tables/neutron-cisco.xml51(td)
-#: ./doc/common/tables/neutron-cisco.xml127(td)
-msgid "(StrOpt) VLAN Name prefix"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml58(td)
-msgid "(StrOpt) N1K Bridge Mappings"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml61(td)
-msgid "default_network_profile = default_network_profile"
-msgstr "default_network_profile = default_network_profile"
-
-#: ./doc/common/tables/neutron-cisco.xml62(td)
-msgid "(StrOpt) N1K default network profile"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml65(td)
-msgid "default_policy_profile = service_profile"
-msgstr "default_policy_profile = service_profile"
-
-#: ./doc/common/tables/neutron-cisco.xml66(td)
-msgid "(StrOpt) N1K default policy profile"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml69(td)
-msgid "enable_tunneling = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml70(td)
-msgid "(BoolOpt) N1K Enable Tunneling"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml74(td)
-msgid "(StrOpt) N1K Integration Bridge"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml77(td)
-msgid "network_node_policy_profile = dhcp_pp"
-msgstr "network_node_policy_profile = dhcp_pp"
-
-#: ./doc/common/tables/neutron-cisco.xml78(td)
-msgid "(StrOpt) N1K policy profile for network node"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml81(td)
-msgid "network_vlan_ranges = vlan:1:4095"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml82(td)
-msgid "(StrOpt) N1K Network VLAN Ranges"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml85(td)
-msgid "poll_duration = 10"
-msgstr "poll_duration = 10"
-
-#: ./doc/common/tables/neutron-cisco.xml86(td)
-msgid "(StrOpt) N1K Policy profile polling duration in seconds"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml90(td)
-msgid "(StrOpt) N1K Tenant Network Type"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml94(td)
-msgid "(StrOpt) N1K Tunnel Bridge"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml97(td)
-msgid "vxlan_id_ranges = 5000:10000"
-msgstr "vxlan_id_ranges = 5000:10000"
-
-#: ./doc/common/tables/neutron-cisco.xml98(td)
-msgid "(StrOpt) N1K VXLAN ID Ranges"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml101(th)
-msgid "[CISCO_PLUGINS]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml104(td)
-msgid ""
-"nexus_plugin = neutron.plugins.cisco.nexus.cisco_nexus_plugin_v2.NexusPlugin"
-msgstr "nexus_plugin = neutron.plugins.cisco.nexus.cisco_nexus_plugin_v2.NexusPlugin"
-
-#: ./doc/common/tables/neutron-cisco.xml105(td)
-msgid "(StrOpt) Nexus Switch to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml108(td)
-msgid ""
-"vswitch_plugin = "
-"neutron.plugins.openvswitch.ovs_neutron_plugin.OVSNeutronPluginV2"
-msgstr "vswitch_plugin = neutron.plugins.openvswitch.ovs_neutron_plugin.OVSNeutronPluginV2"
-
-#: ./doc/common/tables/neutron-cisco.xml109(td)
-msgid "(StrOpt) Virtual Switch to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml112(th)
-msgid "[cisco_csr_ipsec]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml115(td)
-msgid "status_check_interval = 60"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml116(td)
-msgid "(IntOpt) Status check interval for Cisco CSR IPSec connections"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml8(caption)
-msgid "Description of configuration options for hyperv"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml22(td)
-msgid "dynamic_memory_ratio = 1.0"
-msgstr "dynamic_memory_ratio = 1.0"
-
-#: ./doc/common/tables/nova-hyperv.xml23(td)
-msgid ""
-"(FloatOpt) Enables dynamic memory allocation (ballooning) when set to a "
-"value greater than 1. The value expresses the ratio between the total RAM "
-"assigned to an instance and its startup RAM amount. For example a ratio of "
-"2.0 for an instance with 1024MB of RAM implies 512MB of RAM allocated at "
-"startup"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml26(td)
-msgid "enable_instance_metrics_collection = False"
-msgstr "enable_instance_metrics_collection = False"
-
-#: ./doc/common/tables/nova-hyperv.xml27(td)
-msgid ""
-"(BoolOpt) Enables metrics collections for an instance by using Hyper-V's "
-"metric APIs. Collected data can by retrieved by other apps and services, "
-"e.g.: Ceilometer. Requires Hyper-V / Windows Server 2012 and above"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml34(td)
-msgid "instances_path_share ="
-msgstr "instances_path_share ="
-
-#: ./doc/common/tables/nova-hyperv.xml35(td)
-msgid ""
-"(StrOpt) The name of a Windows share name mapped to the \"instances_path\" "
-"dir and used by the resize feature to copy files to the target host. If left"
-" blank, an administrative share will be used, looking for the same "
-"\"instances_path\" used locally"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml38(td)
-msgid "limit_cpu_features = False"
-msgstr "limit_cpu_features = False"
-
-#: ./doc/common/tables/nova-hyperv.xml39(td)
-msgid ""
-"(BoolOpt) Required for live migration among hosts with different CPU "
-"features"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml42(td)
-msgid "mounted_disk_query_retry_count = 10"
-msgstr "mounted_disk_query_retry_count = 10"
-
-#: ./doc/common/tables/nova-hyperv.xml43(td)
-msgid ""
-"(IntOpt) The number of times to retry checking for a disk mounted via iSCSI."
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml46(td)
-msgid "mounted_disk_query_retry_interval = 5"
-msgstr "mounted_disk_query_retry_interval = 5"
-
-#: ./doc/common/tables/nova-hyperv.xml47(td)
-msgid "(IntOpt) Interval between checks for a mounted iSCSI disk, in seconds."
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml50(td)
-msgid "qemu_img_cmd = qemu-img.exe"
-msgstr "qemu_img_cmd = qemu-img.exe"
-
-#: ./doc/common/tables/nova-hyperv.xml51(td)
-msgid ""
-"(StrOpt) Path of qemu-img command which is used to convert between different"
-" image types"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml54(td)
-msgid "vswitch_name = None"
-msgstr "vswitch_name = None"
-
-#: ./doc/common/tables/nova-hyperv.xml55(td)
-msgid ""
-"(StrOpt) External virtual switch Name, if not provided, the first external "
-"virtual switch is used"
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml8(caption)
-msgid "Description of configuration options for l3_agent"
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml22(td)
-msgid "enable_metadata_proxy = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml23(td)
-msgid "(BoolOpt) Allow running metadata proxy."
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml26(td)
-msgid "external_network_bridge = br-ex"
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml27(td)
-msgid "(StrOpt) Name of bridge used for external network traffic."
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml30(td)
-msgid "gateway_external_network_id ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml31(td)
-msgid ""
-"(StrOpt) UUID of external network for routers implemented by the agents."
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml34(td)
-msgid "handle_internal_only_routers = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml35(td)
-msgid "(BoolOpt) Agent should implement routers with no gateway"
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml38(td)
-msgid "router_id ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml39(td)
-msgid ""
-"(StrOpt) If namespaces is disabled, the l3 agent can only configure a router"
-" that has the matching router ID."
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml42(td)
-msgid "send_arp_for_ha = 0"
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml43(td)
-msgid ""
-"(IntOpt) Send this many gratuitous ARPs for HA setup, if less than or equal "
-"to 0, the feature is disabled"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-filter-recon.xml24(td)
-msgid "recon_lock_path = /var/lock"
-msgstr "recon_lock_path = /var/lock"
-
-#: ./doc/common/tables/cinder-coraid.xml8(caption)
-msgid "Description of configuration options for coraid"
-msgstr ""
-
-#: ./doc/common/tables/cinder-coraid.xml22(td)
-msgid "coraid_esm_address ="
-msgstr "coraid_esm_address ="
-
-#: ./doc/common/tables/cinder-coraid.xml23(td)
-msgid "(StrOpt) IP address of Coraid ESM"
-msgstr ""
-
-#: ./doc/common/tables/cinder-coraid.xml26(td)
-msgid "coraid_group = admin"
-msgstr "coraid_group = admin"
-
-#: ./doc/common/tables/cinder-coraid.xml27(td)
-msgid ""
-"(StrOpt) Name of group on Coraid ESM to which coraid_user belongs (must have"
-" admin privilege)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-coraid.xml30(td)
-msgid "coraid_password = password"
-msgstr "coraid_password = password"
-
-#: ./doc/common/tables/cinder-coraid.xml31(td)
-msgid "(StrOpt) Password to connect to Coraid ESM"
-msgstr ""
-
-#: ./doc/common/tables/cinder-coraid.xml34(td)
-msgid "coraid_repository_key = coraid_repository"
-msgstr "coraid_repository_key = coraid_repository"
-
-#: ./doc/common/tables/cinder-coraid.xml35(td)
-msgid "(StrOpt) Volume Type key name to store ESM Repository Name"
-msgstr ""
-
-#: ./doc/common/tables/cinder-coraid.xml38(td)
-msgid "coraid_user = admin"
-msgstr "coraid_user = admin"
-
-#: ./doc/common/tables/cinder-coraid.xml39(td)
-msgid "(StrOpt) User name to connect to Coraid ESM"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-auditor.xml7(literal)
-msgid "[container-auditor]"
-msgstr "[container-auditor]"
-
-#: ./doc/common/tables/swift-container-server-container-auditor.xml18(td)
-msgid "log_name = container-auditor"
-msgstr "log_name = container-auditor"
-
-#: ./doc/common/tables/swift-container-server-container-auditor.xml33(td)
-msgid "containers_per_second = 200"
-msgstr "containers_per_second = 200"
-
-#: ./doc/common/tables/swift-container-server-container-auditor.xml33(td)
-msgid ""
-"Maximum containers audited per second. Should be tuned according to "
-"individual system specs. 0 is unlimited. mounted to prevent accidentally "
-"writing to the root device process simultaneously (it will actually "
-"accept(2) N + 1). Setting this to one (1) will only handle one request at a "
-"time, without accepting another request concurrently. By increasing the "
-"number of workers to a much higher value, one can reduce the impact of slow "
-"file system operations in one request from negatively impacting other "
-"requests."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml21(td)
-msgid "set log_name = catch_errors"
-msgstr "set log_name = catch_errors"
-
-#: ./doc/common/tables/nova-vmware.xml23(td)
-msgid ""
-"(IntOpt) The number of times we retry on failures, e.g., socket error, etc."
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml26(td)
-msgid "cluster_name = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml27(td)
-msgid ""
-"(MultiStrOpt) Name of a VMware Cluster ComputeResource. Used only if "
-"compute_driver is vmwareapi.VMwareVCDriver."
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml30(td)
-msgid "datastore_regex = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml31(td)
-msgid "(StrOpt) Regex to match the name of a datastore."
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml34(td)
-msgid "host_ip = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml35(td)
-msgid "(StrOpt) Hostname or IP address for connection to VMware ESX/VC host."
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml38(td)
-msgid "host_password = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml39(td)
-msgid "(StrOpt) Password for connection to VMware ESX/VC host."
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml42(td)
-msgid "host_username = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml43(td)
-msgid "(StrOpt) Username for connection to VMware ESX/VC host."
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml47(td)
-msgid "(StrOpt) Name of Integration Bridge"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml50(td)
-msgid "maximum_objects = 100"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml51(td)
-msgid ""
-"(IntOpt) The maximum number of ObjectContent data objects that should be "
-"returned in a single result. A positive value will cause the operation to "
-"suspend the retrieval when the count of objects reaches the specified "
-"maximum. The server may still limit the count to something less than the "
-"configured value. Any remaining objects may be retrieved with additional "
-"requests."
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml55(td)
-msgid "(FloatOpt) The interval used for polling of remote tasks."
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml58(td)
-msgid "use_linked_clone = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml59(td)
-msgid "(BoolOpt) Whether to use linked clone"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml62(td)
-msgid "wsdl_location = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml63(td)
-msgid ""
-"(StrOpt) Optional VIM Service WSDL Location e.g "
-"http://&lt;server&gt;/vimService.wsdl. Optional over-ride to default "
-"location for bug work-arounds"
-msgstr ""
-
-#: ./doc/common/tables/nova-logging.xml26(td)
-msgid ""
-"default_log_levels = amqp=WARN, amqplib=WARN, boto=WARN, qpid=WARN, "
-"sqlalchemy=WARN, suds=INFO, oslo.messaging=INFO, iso8601=WARN"
-msgstr ""
-
-#: ./doc/common/tables/nova-logging.xml34(td)
-#: ./doc/common/tables/cinder-common.xml54(td)
-msgid "fatal_exception_format_errors = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-logging.xml35(td)
-msgid "(BoolOpt) Make exception message format errors fatal"
-msgstr ""
-
-#: ./doc/common/tables/nova-logging.xml66(td)
-msgid ""
-"logging_context_format_string = %(asctime)s.%(msecs)03d %(process)d "
-"%(levelname)s %(name)s [%(request_id)s %(user)s %(tenant)s] "
-"%(instance)s%(message)s"
-msgstr "logging_context_format_string = %(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [%(request_id)s %(user)s %(tenant)s] %(instance)s%(message)s"
-
-#: ./doc/common/tables/nova-xen.xml8(caption)
-msgid "Description of configuration options for xen"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml22(td)
-msgid "console_driver = nova.console.xvp.XVPConsoleProxy"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml23(td)
-msgid "(StrOpt) Driver to use for the console proxy"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml26(td)
-msgid "console_vmrc_error_retries = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml27(td)
-msgid "(IntOpt) Number of retries for retrieving VMRC information"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml30(td)
-msgid "console_vmrc_port = 443"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml31(td)
-msgid "(IntOpt) Port for VMware VMRC connections"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml34(td)
-msgid "console_xvp_conf = /etc/xvp.conf"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml35(td)
-msgid "(StrOpt) Generated XVP conf file"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml38(td)
-msgid "console_xvp_conf_template = $pybasedir/nova/console/xvp.conf.template"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml39(td)
-msgid "(StrOpt) XVP conf template"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml42(td)
-msgid "console_xvp_log = /var/log/xvp.log"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml43(td)
-msgid "(StrOpt) XVP log file"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml46(td)
-msgid "console_xvp_multiplex_port = 5900"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml47(td)
-msgid "(IntOpt) Port for XVP to multiplex VNC connections on"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml50(td)
-msgid "console_xvp_pid = /var/run/xvp.pid"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml51(td)
-msgid "(StrOpt) XVP master process pid file"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml54(td)
-msgid "stub_compute = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml55(td)
-msgid "(BoolOpt) Stub calls to compute worker for tests"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml61(td)
-msgid "xen_hvmloader_path = /usr/lib/xen/boot/hvmloader"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml62(td)
-msgid "(StrOpt) Location where the Xen hvmloader is kept"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml68(td)
-msgid "agent_path = usr/sbin/xe-update-networking"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml69(td)
-msgid ""
-"(StrOpt) Specifies the path in which the XenAPI guest agent should be "
-"located. If the agent is present, network configuration is not injected into"
-" the image. Used if compute_driver=xenapi.XenAPIDriver and "
-"flat_injected=True"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml72(td)
-msgid "agent_resetnetwork_timeout = 60"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml73(td)
-msgid ""
-"(IntOpt) Number of seconds to wait for agent reply to resetnetwork request"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml76(td)
-msgid "agent_timeout = 30"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml77(td)
-msgid "(IntOpt) Number of seconds to wait for agent reply"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml80(td)
-msgid "agent_version_timeout = 300"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml81(td)
-msgid "(IntOpt) Number of seconds to wait for agent to be fully operational"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml84(td)
-msgid "cache_images = all"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml85(td)
-msgid ""
-"(StrOpt) Cache glance images locally. `all` will cache all images, `some` "
-"will only cache images that have the image_property `cache_in_nova=True`, "
-"and `none` turns off caching entirely"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml88(td)
-msgid "check_host = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml89(td)
-msgid ""
-"(BoolOpt) Ensure compute service is running on host XenAPI connects to."
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml92(td)
-msgid "connection_concurrent = 5"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml93(td)
-msgid ""
-"(IntOpt) Maximum number of concurrent XenAPI connections. Used only if "
-"compute_driver=xenapi.XenAPIDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml96(td)
-msgid "connection_password = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml97(td)
-msgid ""
-"(StrOpt) Password for connection to XenServer/Xen Cloud Platform. Used only "
-"if compute_driver=xenapi.XenAPIDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml100(td)
-msgid "connection_url = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml101(td)
-msgid ""
-"(StrOpt) URL for connection to XenServer/Xen Cloud Platform. A special value"
-" of unix://local can be used to connect to the local unix socket. Required "
-"if compute_driver=xenapi.XenAPIDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml104(td)
-msgid "connection_username = root"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml105(td)
-msgid ""
-"(StrOpt) Username for connection to XenServer/Xen Cloud Platform. Used only "
-"if compute_driver=xenapi.XenAPIDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml108(td)
-msgid "default_os_type = linux"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml109(td)
-msgid "(StrOpt) Default OS type"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml112(td)
-msgid "disable_agent = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml113(td)
-msgid ""
-"(BoolOpt) Disables the use of the XenAPI agent in any image regardless of "
-"what image properties are present."
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml116(td)
-msgid "image_compression_level = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml117(td)
-msgid ""
-"(IntOpt) Compression level for images, e.g., 9 for gzip -9. Range is 1-9, 9 "
-"being most compressed but most CPU intensive on dom0."
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml120(td)
-msgid "image_upload_handler = nova.virt.xenapi.image.glance.GlanceStore"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml121(td)
-msgid "(StrOpt) Dom0 plugin driver used to handle image uploads."
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml124(td)
-msgid "introduce_vdi_retry_wait = 20"
-msgstr "introduce_vdi_retry_wait = 20"
-
-#: ./doc/common/tables/nova-xen.xml125(td)
-msgid ""
-"(IntOpt) Number of seconds to wait for an SR to settle if the VDI does not "
-"exist when first introduced"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml128(td)
-msgid "ipxe_boot_menu_url = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml129(td)
-msgid "(StrOpt) URL to the iPXE boot menu"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml132(td)
-msgid "ipxe_mkisofs_cmd = mkisofs"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml133(td)
-#: ./doc/common/tables/nova-configdrive.xml39(td)
-msgid ""
-"(StrOpt) Name and optionally path of the tool used for ISO image creation"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml136(td)
-msgid "ipxe_network_name = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml137(td)
-msgid "(StrOpt) Name of network to use for booting iPXE ISOs"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml140(td)
-msgid "iqn_prefix = iqn.2010-10.org.openstack"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml141(td)
-msgid "(StrOpt) IQN Prefix"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml144(td)
-msgid "login_timeout = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml145(td)
-msgid "(IntOpt) Timeout in seconds for XenAPI login."
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml148(td)
-msgid "max_kernel_ramdisk_size = 16777216"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml149(td)
-msgid "(IntOpt) Maximum size in bytes of kernel or ramdisk images"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml152(td)
-msgid "num_vbd_unplug_retries = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml153(td)
-msgid "(IntOpt) Maximum number of retries to unplug VBD"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml156(td)
-msgid "ovs_integration_bridge = xapi1"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml160(td)
-msgid "remap_vbd_dev = False"
-msgstr "remap_vbd_dev = False"
-
-#: ./doc/common/tables/nova-xen.xml161(td)
-msgid ""
-"(BoolOpt) Used to enable the remapping of VBD dev (Works around an issue in "
-"Ubuntu Maverick)"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml164(td)
-msgid "remap_vbd_dev_prefix = sd"
-msgstr "remap_vbd_dev_prefix = sd"
-
-#: ./doc/common/tables/nova-xen.xml165(td)
-msgid ""
-"(StrOpt) Specify prefix to remap VBD dev to (ex. /dev/xvdb -&gt; /dev/sdb)"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml168(td)
-msgid "running_timeout = 60"
-msgstr "running_timeout = 60"
-
-#: ./doc/common/tables/nova-xen.xml169(td)
-msgid "(IntOpt) Number of seconds to wait for instance to go to running state"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml172(td)
-msgid "sparse_copy = True"
-msgstr "sparse_copy = True"
-
-#: ./doc/common/tables/nova-xen.xml173(td)
-msgid ""
-"(BoolOpt) Whether to use sparse_copy for copying data on a resize down "
-"(False will use standard dd). This speeds up resizes down considerably since"
-" large runs of zeros won't have to be rsynced"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml176(td)
-msgid "sr_base_path = /var/run/sr-mount"
-msgstr "sr_base_path = /var/run/sr-mount"
-
-#: ./doc/common/tables/nova-xen.xml177(td)
-#: ./doc/common/tables/cinder-storage_xen.xml43(td)
-msgid "(StrOpt) Base path to the storage repository"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml180(td)
-msgid "sr_matching_filter = default-sr:true"
-msgstr "sr_matching_filter = default-sr:true"
-
-#: ./doc/common/tables/nova-xen.xml181(td)
-msgid ""
-"(StrOpt) Filter for finding the SR to be used to install guest instances on."
-" To use the Local Storage in default XenServer/XCP installations set this "
-"flag to other-config:i18n-key=local-storage. To select an SR with a "
-"different matching criteria, you could set it to other-"
-"config:my_favorite_sr=true. On the other hand, to fall back on the Default "
-"SR, as displayed by XenCenter, set this flag to: default-sr:true"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml184(td)
-msgid "target_host = None"
-msgstr "target_host = None"
-
-#: ./doc/common/tables/nova-xen.xml185(td)
-msgid "(StrOpt) The iSCSI Target Host"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml188(td)
-msgid "target_port = 3260"
-msgstr "target_port = 3260"
-
-#: ./doc/common/tables/nova-xen.xml189(td)
-msgid "(StrOpt) The iSCSI Target Port, default is port 3260"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml192(td)
-msgid "torrent_base_url = None"
-msgstr "torrent_base_url = None"
-
-#: ./doc/common/tables/nova-xen.xml193(td)
-msgid "(StrOpt) Base URL for torrent files."
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml196(td)
-msgid "torrent_download_stall_cutoff = 600"
-msgstr "torrent_download_stall_cutoff = 600"
-
-#: ./doc/common/tables/nova-xen.xml197(td)
-msgid ""
-"(IntOpt) Number of seconds a download can remain at the same progress "
-"percentage w/o being considered a stall"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml200(td)
-msgid "torrent_images = none"
-msgstr "torrent_images = none"
-
-#: ./doc/common/tables/nova-xen.xml201(td)
-msgid ""
-"(StrOpt) Whether or not to download images via Bit Torrent (all|some|none)."
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml204(td)
-msgid "torrent_listen_port_end = 6891"
-msgstr "torrent_listen_port_end = 6891"
-
-#: ./doc/common/tables/nova-xen.xml205(td)
-msgid "(IntOpt) End of port range to listen on"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml208(td)
-msgid "torrent_listen_port_start = 6881"
-msgstr "torrent_listen_port_start = 6881"
-
-#: ./doc/common/tables/nova-xen.xml209(td)
-msgid "(IntOpt) Beginning of port range to listen on"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml212(td)
-msgid "torrent_max_last_accessed = 86400"
-msgstr "torrent_max_last_accessed = 86400"
-
-#: ./doc/common/tables/nova-xen.xml213(td)
-msgid ""
-"(IntOpt) Cached torrent files not accessed within this number of seconds can"
-" be reaped"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml216(td)
-msgid "torrent_max_seeder_processes_per_host = 1"
-msgstr "torrent_max_seeder_processes_per_host = 1"
-
-#: ./doc/common/tables/nova-xen.xml217(td)
-msgid ""
-"(IntOpt) Maximum number of seeder processes to run concurrently within a "
-"given dom0. (-1 = no limit)"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml220(td)
-msgid "torrent_seed_chance = 1.0"
-msgstr "torrent_seed_chance = 1.0"
-
-#: ./doc/common/tables/nova-xen.xml221(td)
-msgid "(FloatOpt) Probability that peer will become a seeder. (1.0 = 100%)"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml224(td)
-msgid "torrent_seed_duration = 3600"
-msgstr "torrent_seed_duration = 3600"
-
-#: ./doc/common/tables/nova-xen.xml225(td)
-msgid ""
-"(IntOpt) Number of seconds after downloading an image via BitTorrent that it"
-" should be seeded for other peers."
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml228(td)
-msgid "use_agent_default = False"
-msgstr "use_agent_default = False"
-
-#: ./doc/common/tables/nova-xen.xml229(td)
-msgid ""
-"(BoolOpt) Determines if the XenAPI agent should be used when the image used "
-"does not contain a hint to declare if the agent is present or not. The hint "
-"is a glance property \"xenapi_use_agent\" that has the value \"True\" or "
-"\"False\". Note that waiting for the agent when it is not present will "
-"significantly increase server boot times."
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml232(td)
-msgid "use_join_force = True"
-msgstr "use_join_force = True"
-
-#: ./doc/common/tables/nova-xen.xml233(td)
-msgid "(BoolOpt) To use for hosts with different CPUs"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml236(td)
-msgid "vhd_coalesce_max_attempts = 20"
-msgstr "vhd_coalesce_max_attempts = 20"
-
-#: ./doc/common/tables/nova-xen.xml237(td)
-msgid ""
-"(IntOpt) Max number of times to poll for VHD to coalesce. Used only if "
-"compute_driver=xenapi.XenAPIDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml240(td)
-msgid "vhd_coalesce_poll_interval = 5.0"
-msgstr "vhd_coalesce_poll_interval = 5.0"
-
-#: ./doc/common/tables/nova-xen.xml241(td)
-msgid ""
-"(FloatOpt) The interval used for polling of coalescing vhds. Used only if "
-"compute_driver=xenapi.XenAPIDriver"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml8(caption)
-msgid "Description of configuration options for collector"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml22(td)
-msgid "collector_workers = 1"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml23(td)
-msgid ""
-"(IntOpt) Number of workers for collector service. A single collector is "
-"enabled by default."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml26(th)
-msgid "[collector]"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml29(td)
-msgid "udp_address = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml30(td)
-msgid ""
-"(StrOpt) Address to which the UDP socket is bound. Set to an empty string to"
-" disable."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml33(td)
-msgid "udp_port = 4952"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml34(td)
-msgid "(IntOpt) Port to which the UDP socket is bound."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml37(th)
-msgid "[dispatcher_file]"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml40(td)
-msgid "backup_count = 0"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml41(td)
-msgid "(IntOpt) The max number of the files to keep."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml44(td)
-msgid "file_path = None"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml45(td)
-msgid "(StrOpt) Name and the location of the file to record meters."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml48(td)
-msgid "max_bytes = 0"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml49(td)
-msgid "(IntOpt) The max size of the file."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml7(literal)
-msgid "[filter:list-endpoints]"
-msgstr "[filter:list-endpoints]"
-
-#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml18(td)
-msgid "use = egg:swift#list_endpoints"
-msgstr "use = egg:swift#list_endpoints"
-
-#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml21(td)
-msgid "list_endpoints_path = /endpoints/"
-msgstr "list_endpoints_path = /endpoints/"
-
-#: ./doc/common/tables/keystone-ec2.xml22(td)
-msgid "keystone_ec2_cafile = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml23(td)
-msgid ""
-"(StrOpt) A PEM encoded certificate authority to use when verifying HTTPS "
-"connections. Defaults to the system CAs."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml26(td)
-msgid "keystone_ec2_certfile = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml27(td)
-msgid ""
-"(StrOpt) Client certificate key filename. Required if EC2 server requires "
-"client certificate."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml30(td)
-msgid "keystone_ec2_insecure = False"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml31(td)
-msgid "(BoolOpt) Disable SSL certificate verification."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml34(td)
-msgid "keystone_ec2_keyfile = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml35(td)
-msgid "(StrOpt) Required if EC2 server requires client certificate."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml42(th)
-msgid "[ec2]"
-msgstr "[ec2]"
-
-#: ./doc/common/tables/keystone-ec2.xml45(td)
-msgid "driver = keystone.contrib.ec2.backends.kvs.Ec2"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml46(td)
-msgid "(StrOpt) Keystone EC2Credential backend driver."
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml8(caption)
-#: ./doc/common/tables/ceilometer-auth.xml8(caption)
-#: ./doc/common/tables/cinder-auth.xml8(caption)
-msgid "Description of configuration options for auth"
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml19(th)
-msgid "[auth]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml22(td)
-msgid "external = keystone.auth.plugins.external.DefaultDomain"
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml23(td)
-msgid "(StrOpt) The external (REMOTE_USER) auth plugin module."
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml26(td)
-msgid "methods = external, password, token"
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml27(td)
-msgid "(ListOpt) Default auth methods."
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml30(td)
-msgid "password = keystone.auth.plugins.password.Password"
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml31(td)
-msgid "(StrOpt) The password auth plugin module."
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml34(td)
-msgid "token = keystone.auth.plugins.token.Token"
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml35(td)
-msgid "(StrOpt) The token auth plugin module."
-msgstr ""
-
-#: ./doc/common/tables/swift-memcache-memcache.xml7(literal)
-msgid "memcache.conf-sample"
-msgstr "memcache.conf-sample"
-
-#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml7(literal)
-msgid "[filter:keystoneauth]"
-msgstr "[filter:keystoneauth]"
-
-#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml18(td)
-msgid "use = egg:swift#keystoneauth"
-msgstr "use = egg:swift#keystoneauth"
-
-#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml21(td)
-msgid "operator_roles = admin, swiftoperator"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml24(td)
-msgid "reseller_admin_role = ResellerAdmin"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2.xml8(caption)
-msgid "Description of configuration options for ml2"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2.xml19(th)
-msgid "[ml2]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2.xml22(td)
-msgid "mechanism_drivers ="
-msgstr "mechanism_drivers ="
-
-#: ./doc/common/tables/neutron-ml2.xml23(td)
-msgid ""
-"(ListOpt) An ordered list of networking mechanism driver entrypoints to be "
-"loaded from the neutron.ml2.mechanism_drivers namespace."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2.xml26(td)
-msgid "tenant_network_types = local"
-msgstr "tenant_network_types = local"
-
-#: ./doc/common/tables/neutron-ml2.xml27(td)
-msgid ""
-"(ListOpt) Ordered list of network_types to allocate as tenant networks."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2.xml30(td)
-msgid "type_drivers = local, flat, vlan, gre, vxlan"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2.xml31(td)
-msgid ""
-"(ListOpt) List of network type driver entrypoints to be loaded from the "
-"neutron.ml2.type_drivers namespace."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml23(td)
-msgid "(BoolOpt) Deploy the deprecated v1 API."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml27(td)
-msgid "(IntOpt) The maximum body size per request, in bytes"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml30(td)
-msgid "pipeline_cfg_file = pipeline.yaml"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml31(td)
-msgid "(StrOpt) Configuration file for pipeline definition."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml35(td)
-#: ./doc/common/tables/heat-api.xml43(td)
-#: ./doc/common/tables/keystone-policy.xml23(td)
-msgid "(StrOpt) Rule enforced when requested rule is not found"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml39(td)
-#: ./doc/common/tables/heat-api.xml47(td)
-#: ./doc/common/tables/keystone-policy.xml27(td)
-msgid "(StrOpt) JSON file containing policy"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml42(td)
-msgid "reserved_metadata_length = 256"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml43(td)
-msgid "(IntOpt) Limit on length of reserved metadata values."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml46(td)
-msgid "reserved_metadata_namespace = metering."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml47(td)
-msgid "(ListOpt) List of metadata prefixes reserved for metering use."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml50(th)
-msgid "[api]"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml53(td)
-#: ./doc/common/tables/trove-rpc.xml26(td)
-msgid "host = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml54(td)
-msgid "(StrOpt) The listen IP for the ceilometer API server."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml57(td)
-msgid "port = 8777"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml58(td)
-msgid "(IntOpt) The port for the ceilometer API server."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_trove.xml8(caption)
-msgid "Description of configuration options for clients_trove"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_trove.xml19(th)
-msgid "[clients_trove]"
-msgstr "[clients_trove]"
-
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml7(literal)
-msgid "[filter:gatekeeper]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml18(td)
-msgid "use = egg:swift#gatekeeper"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml21(td)
-msgid "set log_name = gatekeeper"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml8(caption)
-msgid "Description of configuration options for netapp_7mode_nfs"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml22(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml22(td)
-msgid "expiry_thres_minutes = 720"
-msgstr "expiry_thres_minutes = 720"
-
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml23(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml23(td)
-msgid ""
-"(IntOpt) This option specifies the threshold for last access time for images"
-" in the NFS image cache. When a cache cleaning cycle begins, images in the "
-"cache that have not been accessed in the last M minutes, where M is the "
-"value of this parameter, will be deleted from the cache to create free space"
-" on the NFS share."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml54(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml62(td)
-msgid "thres_avl_size_perc_start = 20"
-msgstr "thres_avl_size_perc_start = 20"
-
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml55(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml63(td)
-msgid ""
-"(IntOpt) If the percentage of available space for an NFS share has dropped "
-"below the value specified by this option, the NFS image cache will be "
-"cleaned."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml58(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml66(td)
-msgid "thres_avl_size_perc_stop = 60"
-msgstr "thres_avl_size_perc_stop = 60"
-
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml59(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml67(td)
-msgid ""
-"(IntOpt) When the percentage of available space on an NFS share has reached "
-"the percentage specified by this option, the driver will stop clearing files"
-" from the NFS image cache that have not been accessed in the last M minutes,"
-" where M is the value of the expiry_thres_minutes configuration option."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml22(td)
-msgid "allow_additional_image_properties = True"
-msgstr "allow_additional_image_properties = True"
-
-#: ./doc/common/tables/glance-common.xml23(td)
-msgid ""
-"(BoolOpt) Whether to allow users to specify image properties beyond what the"
-" image schema provides"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml26(td)
-msgid "api_limit_max = 1000"
-msgstr "api_limit_max = 1000"
-
-#: ./doc/common/tables/glance-common.xml27(td)
-msgid ""
-"(IntOpt) Maximum permissible number of items that could be returned by a "
-"request"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml31(td)
-msgid ""
-"(IntOpt) The backlog value that will be used when creating the TCP listener "
-"socket."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml38(td)
-msgid "bind_port = None"
-msgstr "bind_port = None"
-
-#: ./doc/common/tables/glance-common.xml42(td)
-msgid "data_api = glance.db.sqlalchemy.api"
-msgstr "data_api = glance.db.sqlalchemy.api"
-
-#: ./doc/common/tables/glance-common.xml43(td)
-msgid "(StrOpt) Python module path of data access API"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml50(td)
-msgid "image_location_quota = 10"
-msgstr "image_location_quota = 10"
-
-#: ./doc/common/tables/glance-common.xml51(td)
-msgid ""
-"(IntOpt) Maximum number of locations allowed on an image. Negative values "
-"evaluate to unlimited."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml54(td)
-msgid "image_member_quota = 128"
-msgstr "image_member_quota = 128"
-
-#: ./doc/common/tables/glance-common.xml55(td)
-msgid ""
-"(IntOpt) Maximum number of image members per image. Negative values evaluate"
-" to unlimited."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml58(td)
-msgid "image_property_quota = 128"
-msgstr "image_property_quota = 128"
-
-#: ./doc/common/tables/glance-common.xml59(td)
-msgid ""
-"(IntOpt) Maximum number of properties allowed on an image. Negative values "
-"evaluate to unlimited."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml62(td)
-msgid "image_tag_quota = 128"
-msgstr "image_tag_quota = 128"
-
-#: ./doc/common/tables/glance-common.xml63(td)
-msgid ""
-"(IntOpt) Maximum number of tags allowed on an image. Negative values "
-"evaluate to unlimited."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml66(td)
-msgid "limit_param_default = 25"
-msgstr "limit_param_default = 25"
-
-#: ./doc/common/tables/glance-common.xml67(td)
-msgid ""
-"(IntOpt) Default value for the number of items returned by a request if not "
-"specified explicitly in the request"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml74(td)
-msgid "metadata_encryption_key = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml75(td)
-msgid ""
-"(StrOpt) Key used for encrypting sensitive metadata while talking to the "
-"registry or database."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml78(td)
-msgid "notifier_strategy = default"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml79(td)
-msgid ""
-"(StrOpt) Notifications can be sent when images are create, updated or "
-"deleted. There are three methods of sending notifications, logging (via the "
-"log_file directive), rabbit (via a rabbitmq queue), qpid (via a Qpid message"
-" queue), or noop (no notifications sent, the default). (DEPRECATED)"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml83(td)
-msgid "(StrOpt) Region name of this node."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml86(td)
-msgid "property_protection_file = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml87(td)
-msgid "(StrOpt) The location of the property protection file."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml90(td)
-msgid "property_protection_rule_format = roles"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml91(td)
-msgid ""
-"(StrOpt) This config value indicates whether \"roles\" or \"policies\" are "
-"used in the property protection file."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml94(td)
-msgid "show_image_direct_url = False"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml95(td)
-msgid ""
-"(BoolOpt) Whether to include the backend image storage location in image "
-"properties. Revealing storage location can be a security risk, so use this "
-"setting with caution!"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml98(td)
-msgid "user_storage_quota = 0"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml99(td)
-msgid ""
-"(IntOpt) Set a system wide quota for every user. This value is the total "
-"number of bytes that a user can use across all storage systems. A value of 0"
-" means unlimited."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml102(td)
-msgid "workers = 1"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml103(td)
-msgid ""
-"(IntOpt) The number of child process workers that will be created to service"
-" API requests."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml106(th)
-msgid "[image_format]"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml109(td)
-msgid "container_formats = ami, ari, aki, bare, ovf, ova"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml110(td)
-msgid "(ListOpt) Supported values for the 'container_format' image attribute"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml113(td)
-msgid "disk_formats = ami, ari, aki, vhd, vmdk, raw, qcow2, vdi, iso"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml114(td)
-msgid "(ListOpt) Supported values for the 'disk_format' image attribute"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml117(th)
-msgid "[task]"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml120(td)
-msgid "task_time_to_live = 48"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml121(td)
-msgid ""
-"(IntOpt) Time in hours for which a task lives after, either succeeding or "
-"failing"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml8(caption)
-msgid "Description of configuration options for network"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml22(td)
-msgid "allow_same_net_traffic = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml23(td)
-msgid "(BoolOpt) Whether to allow network traffic from same network"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml26(td)
-msgid "auto_assign_floating_ip = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml27(td)
-msgid "(BoolOpt) Autoassigning floating IP to VM"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml30(td)
-msgid "cnt_vpn_clients = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml31(td)
-msgid "(IntOpt) Number of addresses reserved for vpn clients"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml34(td)
-msgid "create_unique_mac_address_attempts = 5"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml35(td)
-msgid "(IntOpt) Number of attempts to create unique mac address"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml38(td)
-msgid "default_access_ip_network_name = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml39(td)
-msgid "(StrOpt) Name of network to use to set access IPs for instances"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml42(td)
-msgid "default_floating_pool = nova"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml43(td)
-msgid "(StrOpt) Default pool for floating IPs"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml46(td)
-msgid "defer_iptables_apply = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml47(td)
-msgid ""
-"(BoolOpt) Whether to batch up the application of IPTables rules during a "
-"host restart and apply all at the end of the init phase"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml50(td)
-msgid "dhcp_domain = novalocal"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml54(td)
-msgid "dhcp_lease_time = 120"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml55(td)
-msgid "(IntOpt) Lifetime of a DHCP lease in seconds"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml58(td)
-msgid "dhcpbridge = $bindir/nova-dhcpbridge"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml59(td)
-msgid "(StrOpt) Location of nova-dhcpbridge"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml62(td)
-msgid "dhcpbridge_flagfile = ['/etc/nova/nova-dhcpbridge.conf']"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml63(td)
-msgid "(MultiStrOpt) Location of flagfiles for dhcpbridge"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml66(td)
-msgid "dns_server = []"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml67(td)
-msgid ""
-"(MultiStrOpt) If set, uses specific DNS server for dnsmasq. Can be specified"
-" multiple times."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml70(td)
-msgid "dns_update_periodic_interval = -1"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml71(td)
-msgid ""
-"(IntOpt) Number of seconds to wait between runs of updates to DNS entries."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml79(td)
-msgid ""
-"(StrOpt) Firewall driver (defaults to hypervisor specific iptables driver)"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml82(td)
-msgid "fixed_ip_disassociate_timeout = 600"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml83(td)
-msgid "(IntOpt) Seconds after which a deallocated IP is disassociated"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml86(td)
-msgid "flat_injected = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml87(td)
-msgid "(BoolOpt) Whether to attempt to inject network setup into guest"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml90(td)
-msgid "flat_interface = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml91(td)
-msgid "(StrOpt) FlatDhcp will bridge into this interface if set"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml94(td)
-msgid "flat_network_bridge = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml95(td)
-msgid "(StrOpt) Bridge for simple network instances"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml98(td)
-msgid "flat_network_dns = 8.8.4.4"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml99(td)
-msgid "(StrOpt) DNS server for simple network"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml102(td)
-msgid "floating_ip_dns_manager = nova.network.noop_dns_driver.NoopDNSDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml103(td)
-msgid "(StrOpt) Full class name for the DNS Manager for floating IPs"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml106(td)
-msgid "force_dhcp_release = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml107(td)
-msgid "(BoolOpt) If True, send a dhcp release on instance termination"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml110(td)
-msgid "force_snat_range = []"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml111(td)
-msgid ""
-"(MultiStrOpt) Traffic to this range will always be snatted to the fallback "
-"ip, even if it would normally be bridged out of the node. Can be specified "
-"multiple times."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml114(td)
-msgid "forward_bridge_interface = ['all']"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml115(td)
-msgid ""
-"(MultiStrOpt) An interface that bridges can forward to. If this is set to "
-"all then all traffic will be forwarded. Can be specified multiple times."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml118(td)
-msgid "gateway = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml119(td)
-msgid "(StrOpt) Default IPv4 gateway"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml122(td)
-msgid "injected_network_template = $pybasedir/nova/virt/interfaces.template"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml123(td)
-msgid "(StrOpt) Template file for injected network"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml126(td)
-msgid "instance_dns_domain ="
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml127(td)
-msgid "(StrOpt) Full class name for the DNS Zone for instance IPs"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml130(td)
-msgid "instance_dns_manager = nova.network.noop_dns_driver.NoopDNSDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml131(td)
-msgid "(StrOpt) Full class name for the DNS Manager for instance IPs"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml134(td)
-msgid "iptables_bottom_regex ="
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml135(td)
-msgid ""
-"(StrOpt) Regular expression to match iptables rule that should always be on "
-"the bottom."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml138(td)
-msgid "iptables_drop_action = DROP"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml139(td)
-msgid ""
-"(StrOpt) The table that iptables to jump to when a packet is to be dropped."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml142(td)
-msgid "iptables_top_regex ="
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml143(td)
-msgid ""
-"(StrOpt) Regular expression to match iptables rule that should always be on "
-"the top."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml146(td)
-msgid "l3_lib = nova.network.l3.LinuxNetL3"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml147(td)
-msgid "(StrOpt) Indicates underlying L3 management library"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml150(td)
-msgid ""
-"linuxnet_interface_driver = "
-"nova.network.linux_net.LinuxBridgeInterfaceDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml151(td)
-msgid "(StrOpt) Driver used to create ethernet devices."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml154(td)
-msgid "linuxnet_ovs_integration_bridge = br-int"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml155(td)
-msgid "(StrOpt) Name of Open vSwitch bridge used with linuxnet"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml158(td)
-msgid "multi_host = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml159(td)
-msgid ""
-"(BoolOpt) Default value for multi_host in networks. Also, if set, some rpc "
-"network calls will be sent directly to host."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml162(td)
-msgid "network_allocate_retries = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml163(td)
-msgid "(IntOpt) Number of times to retry network allocation on failures"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml166(td)
-msgid "network_api_class = nova.network.api.API"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml167(td)
-msgid "(StrOpt) The full class name of the network API class to use"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml170(td)
-#: ./doc/common/tables/neutron-agent.xml26(td)
-msgid "network_device_mtu = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml171(td)
-msgid "(IntOpt) MTU setting for network interface"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml174(td)
-msgid "network_driver = nova.network.linux_net"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml175(td)
-msgid "(StrOpt) Driver to use for network creation"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml178(td)
-msgid "network_manager = nova.network.manager.VlanManager"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml179(td)
-msgid "(StrOpt) Full class name for the Manager for network"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml182(td)
-msgid "network_size = 256"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml183(td)
-msgid "(IntOpt) Number of addresses in each private subnet"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml186(td)
-msgid "network_topic = network"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml187(td)
-msgid "(StrOpt) The topic network nodes listen on"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml190(td)
-msgid "networks_path = $state_path/networks"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml191(td)
-msgid "(StrOpt) Location to keep network config files"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml194(td)
-msgid "num_networks = 1"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml195(td)
-msgid "(IntOpt) Number of networks to support"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml198(td)
-msgid "ovs_vsctl_timeout = 120"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml199(td)
-msgid ""
-"(IntOpt) Amount of time, in seconds, that ovs_vsctl should wait for a "
-"response from the database. 0 is to wait forever."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml202(td)
-msgid "public_interface = eth0"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml203(td)
-msgid "(StrOpt) Interface for public IP addresses"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml206(td)
-msgid "routing_source_ip = $my_ip"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml207(td)
-msgid "(StrOpt) Public IP of network host"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml210(td)
-msgid "security_group_api = nova"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml211(td)
-msgid "(StrOpt) The full class name of the security API class"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml214(td)
-msgid "send_arp_for_ha = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml215(td)
-msgid "(BoolOpt) Send gratuitous ARPs for HA setup"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml218(td)
-msgid "send_arp_for_ha_count = 3"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml219(td)
-msgid "(IntOpt) Send this many gratuitous ARPs for HA setup"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml222(td)
-msgid "share_dhcp_address = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml223(td)
-msgid ""
-"(BoolOpt) If True in multi_host mode, all compute hosts share the same dhcp "
-"address. The same IP address used for DHCP will be added on each nova-"
-"network node which is only visible to the vms on the same host."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml226(td)
-msgid "teardown_unused_network_gateway = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml227(td)
-msgid ""
-"(BoolOpt) If True, unused gateway devices (VLAN and bridge) are deleted in "
-"VLAN network mode with multi hosted networks"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml230(td)
-msgid "update_dns_entries = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml231(td)
-msgid ""
-"(BoolOpt) If True, when a DNS entry must be updated, it sends a fanout cast "
-"to all network hosts to update their DNS entries in multi host mode"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml234(td)
-msgid "use_network_dns_servers = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml235(td)
-msgid ""
-"(BoolOpt) If set, uses the dns1 and dns2 from the network ref. as dns "
-"servers."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml238(td)
-msgid "use_neutron_default_nets = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml239(td)
-msgid "(StrOpt) Control for checking for default networks"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml242(td)
-msgid "use_single_default_gateway = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml243(td)
-msgid ""
-"(BoolOpt) Use single default gateway. Only first nic of vm will get default "
-"gateway from dhcp server"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml246(td)
-msgid "vlan_interface = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml247(td)
-msgid "(StrOpt) VLANs will bridge into this interface if set"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml250(td)
-msgid "vlan_start = 100"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml251(td)
-msgid "(IntOpt) First VLAN for private networks"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml257(td)
-msgid "vlan_interface = vmnic0"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml258(td)
-msgid "(StrOpt) Physical ethernet adapter name for vlan networking"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scality.xml8(caption)
-msgid "Description of configuration options for scality"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scality.xml30(td)
-msgid "scality_sofs_volume_dir = cinder/volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scality.xml31(td)
-msgid "(StrOpt) Path from Scality SOFS root to volume dir"
-msgstr ""
-
-#: ./doc/common/tables/neutron-notifier.xml8(caption)
-msgid "Description of configuration options for notifier"
-msgstr ""
-
-#: ./doc/common/tables/neutron-notifier.xml26(td)
-#: ./doc/common/tables/trove-common.xml50(td)
-msgid "default_publisher_id = $host"
-msgstr ""
-
-#: ./doc/common/tables/neutron-notifier.xml31(td)
-#: ./doc/common/tables/heat-amqp.xml51(td)
-#: ./doc/common/tables/ceilometer-amqp.xml31(td)
-#: ./doc/common/tables/trove-amqp.xml59(td)
-msgid "(MultiStrOpt) Driver or drivers to handle sending notifications"
-msgstr ""
-
-#: ./doc/common/tables/neutron-notifier.xml35(td)
-#: ./doc/common/tables/trove-amqp.xml67(td)
-msgid "(ListOpt) AMQP topic used for openstack notifications"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml22(td)
-msgid "compute_api_class = cinder.compute.nova.API"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml23(td)
-msgid "(StrOpt) The full class name of the compute API class to use"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml30(td)
-msgid "default_availability_zone = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml31(td)
-msgid ""
-"(StrOpt) default availability zone to use when creating a new volume. If "
-"this is not set then we use the value from the storage_availability_zone "
-"option as the default availability_zone for new volumes."
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml34(td)
-msgid ""
-"default_log_levels = amqp=WARN, amqplib=WARN, boto=WARN, qpid=WARN, "
-"sqlalchemy=WARN, suds=INFO, oslo.messaging=INFO, iso8601=WARN, "
-"requests.packages.urllib3.connectionpool=WARN"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml38(td)
-msgid "default_volume_type = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml39(td)
-msgid "(StrOpt) default volume type to use"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml46(td)
-#: ./doc/common/tables/nova-api.xml26(td)
-msgid "enable_new_services = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml47(td)
-#: ./doc/common/tables/nova-api.xml27(td)
-msgid "(BoolOpt) Services to be added to the available pool on create"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml55(td)
-msgid "(BoolOpt) make exception message format errors fatal"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml59(td)
-msgid ""
-"(StrOpt) Name of this node. This can be an opaque identifier. It is not "
-"necessarily a hostname, FQDN, or IP address."
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml62(td)
-msgid "iet_conf = /etc/iet/ietd.conf"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml63(td)
-msgid "(StrOpt) IET configuration file"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml66(td)
-msgid "lio_initiator_iqns ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml67(td)
-msgid ""
-"(StrOpt) Comma-separated list of initiator IQNs allowed to connect to the "
-"iSCSI target. (From Nova compute nodes.)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml71(td)
-msgid "(StrOpt) Directory to use for lock files. Default to a temp directory"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml111(td)
-msgid "(BoolOpt) Enable monkey patching"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml114(td)
-msgid "monkey_patch_modules ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml119(td)
-msgid "(StrOpt) ip address of this host"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml122(td)
-msgid "no_snapshot_gb_quota = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml123(td)
-msgid "(BoolOpt) Whether snapshots count against GigaByte quota"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml126(td)
-msgid "num_shell_tries = 3"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml127(td)
-msgid "(IntOpt) number of times to attempt to run flakey shell commands"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml131(td)
-msgid ""
-"(IntOpt) range of seconds to randomly delay when starting the periodic task "
-"scheduler to reduce stampeding. (Disable by setting to 0)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml134(td)
-#: ./doc/common/tables/trove-rpc.xml42(td)
-#: ./doc/common/tables/heat-common.xml46(td)
-msgid "periodic_interval = 60"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml135(td)
-msgid "(IntOpt) seconds between running periodic tasks"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml147(td)
-msgid "(IntOpt) seconds between nodes reporting state to datastore"
-msgstr "(IntOpt) secondes entre les nœuds rapportant sur l'état au datastore"
-
-#: ./doc/common/tables/cinder-common.xml150(td)
-msgid "reserved_percentage = 0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml151(td)
-msgid "(IntOpt) The percentage of backend capacity is reserved"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml154(td)
-msgid "rootwrap_config = /etc/cinder/rootwrap.conf"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml163(td)
-msgid "(IntOpt) maximum time since last check-in for up service"
-msgstr "(IntOpt) durée maximale depuis le dernier enregistrement pour le service en place"
-
-#: ./doc/common/tables/cinder-common.xml166(td)
-msgid "sqlite_db = cinder.sqlite"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml186(td)
-msgid "state_path = /var/lib/cinder"
-msgstr "state_path = /var/lib/cinder"
-
-#: ./doc/common/tables/cinder-common.xml187(td)
-msgid "(StrOpt) Top-level directory for maintaining cinder's state"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml190(td)
-msgid "storage_availability_zone = nova"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml191(td)
-msgid "(StrOpt) availability zone of this node"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml203(td)
-msgid "(IntOpt) count of reservations until usage is refreshed"
-msgstr "(IntOpt) compter les réservations jusqu'à ce que l'utilisation soit rafraîchie"
-
-#: ./doc/common/tables/cinder-common.xml206(td)
-#: ./doc/common/tables/nova-api.xml94(td)
-msgid "use_forwarded_for = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml207(td)
-#: ./doc/common/tables/nova-api.xml95(td)
-msgid ""
-"(BoolOpt) Treat X-Forwarded-For as the canonical remote address. Only enable"
-" this if you have a sanitizing proxy."
-msgstr "(BoolOpt) Traiter X-Forwarded-For comme l'adresse distante canonique. Seulement activer cette option si vous avez un proxy de désinfection."
-
-#: ./doc/common/tables/cinder-common.xml237(td)
-msgid "use_tpool = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml238(td)
-msgid ""
-"(BoolOpt) Enable the experimental use of thread pooling for all DB API calls"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml8(caption)
-msgid "Description of configuration options for trustedcomputing"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml19(th)
-msgid "[trusted_computing]"
-msgstr "[trusted_computing]"
-
-#: ./doc/common/tables/nova-trustedcomputing.xml22(td)
-msgid "attestation_api_url = /OpenAttestationWebServices/V1.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml23(td)
-msgid "(StrOpt) Attestation web API URL"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml26(td)
-msgid "attestation_auth_blob = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml27(td)
-msgid "(StrOpt) Attestation authorization blob - must change"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml30(td)
-msgid "attestation_auth_timeout = 60"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml31(td)
-msgid "(IntOpt) Attestation status cache valid period length"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml34(td)
-msgid "attestation_port = 8443"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml35(td)
-msgid "(StrOpt) Attestation server port"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml38(td)
-msgid "attestation_server = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml39(td)
-msgid "(StrOpt) Attestation server HTTP"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml42(td)
-msgid "attestation_server_ca_file = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml43(td)
-msgid "(StrOpt) Attestation server Cert file for Identity verification"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_flat.xml8(caption)
-msgid "Description of configuration options for ml2_flat"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_flat.xml19(th)
-msgid "[ml2_type_flat]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_flat.xml22(td)
-msgid "flat_networks ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_flat.xml23(td)
-msgid ""
-"(ListOpt) List of physical_network names with which flat networks can be "
-"created. Use * to allow flat networks with arbitrary physical_network names."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_cinder.xml8(caption)
-msgid "Description of configuration options for clients_cinder"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_cinder.xml19(th)
-msgid "[clients_cinder]"
-msgstr "[clients_cinder]"
-
-#: ./doc/common/tables/nova-configdrive.xml8(caption)
-msgid "Description of configuration options for configdrive"
-msgstr ""
-
-#: ./doc/common/tables/nova-configdrive.xml22(td)
-msgid "config_drive_format = iso9660"
-msgstr ""
-
-#: ./doc/common/tables/nova-configdrive.xml23(td)
-msgid "(StrOpt) Config drive format. One of iso9660 (default) or vfat"
-msgstr ""
-
-#: ./doc/common/tables/nova-configdrive.xml26(td)
-msgid ""
-"config_drive_skip_versions = 1.0 2007-01-19 2007-03-01 2007-08-29 2007-10-10"
-" 2007-12-15 2008-02-01 2008-09-01"
-msgstr ""
-
-#: ./doc/common/tables/nova-configdrive.xml27(td)
-msgid ""
-"(StrOpt) List of metadata versions to skip placing into the config drive"
-msgstr ""
-
-#: ./doc/common/tables/nova-configdrive.xml30(td)
-msgid "config_drive_tempdir = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-configdrive.xml31(td)
-msgid ""
-"(StrOpt) Where to put temporary files associated with config drive creation"
-msgstr ""
-
-#: ./doc/common/tables/nova-configdrive.xml34(td)
-msgid "force_config_drive = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-configdrive.xml35(td)
-msgid ""
-"(StrOpt) Set to force injection to take place on a config drive (if set, "
-"valid options are: always)"
-msgstr ""
-
-#: ./doc/common/tables/nova-configdrive.xml38(td)
-msgid "mkisofs_cmd = genisoimage"
-msgstr ""
-
-#: ./doc/common/tables/nova-configdrive.xml45(td)
-msgid "config_drive_cdrom = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-configdrive.xml46(td)
-msgid ""
-"(BoolOpt) Attaches the Config Drive image as a cdrom drive instead of a disk"
-" drive"
-msgstr ""
-
-#: ./doc/common/tables/nova-configdrive.xml49(td)
-msgid "config_drive_inject_password = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-configdrive.xml50(td)
-msgid "(BoolOpt) Sets the admin password in the config drive image"
-msgstr ""
-
-#: ./doc/common/tables/cinder-database.xml26(td)
-msgid "db_driver = cinder.db"
-msgstr ""
-
-#: ./doc/common/tables/cinder-database.xml27(td)
-msgid "(StrOpt) driver to use for database access"
-msgstr "(StrOpt)  pilote à utiliser pour l’accès à la base de données"
-
-#: ./doc/common/tables/neutron-rpc.xml30(td)
-msgid "control_exchange = neutron"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rpc.xml31(td)
-#: ./doc/common/tables/heat-amqp.xml31(td)
-#: ./doc/common/tables/ceilometer-exchange.xml27(td)
-#: ./doc/common/tables/trove-amqp.xml35(td)
-msgid "(StrOpt) AMQP exchange to connect to if using RabbitMQ or Qpid"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rpc.xml42(td)
-msgid "rpc_backend = neutron.openstack.common.rpc.impl_kombu"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rpc.xml62(td)
-msgid "rpc_workers = 0"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rpc.xml63(td)
-msgid "(IntOpt) Number of RPC worker processes for service"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rpc.xml69(td)
-msgid "rpc_support_old_agents = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rpc.xml70(td)
-msgid "(BoolOpt) Enable server RPC compatibility with old agents"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rpc.xml84(td)
-#: ./doc/common/tables/trove-rpc.xml74(td)
-msgid "(ListOpt) AMQP topic(s) used for openstack notifications"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zoning_manager.xml8(caption)
-msgid "Description of configuration options for zoning_manager"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zoning_manager.xml22(td)
-msgid ""
-"brcd_sb_connector = "
-"cinder.zonemanager.drivers.brocade.brcd_fc_zone_client_cli.BrcdFCZoneClientCLI"
-msgstr "brcd_sb_connector = cinder.zonemanager.drivers.brocade.brcd_fc_zone_client_cli.BrcdFCZoneClientCLI"
-
-#: ./doc/common/tables/cinder-zoning_manager.xml23(td)
-msgid "(StrOpt) Southbound connector for zoning operation"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zoning_manager.xml26(td)
-msgid ""
-"fc_san_lookup_service = "
-"cinder.zonemanager.drivers.brocade.brcd_fc_san_lookup_service.BrcdFCSanLookupService"
-msgstr "fc_san_lookup_service = cinder.zonemanager.drivers.brocade.brcd_fc_san_lookup_service.BrcdFCSanLookupService"
-
-#: ./doc/common/tables/cinder-zoning_manager.xml27(td)
-msgid "(StrOpt) FC San Lookup Service"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zoning_manager.xml30(td)
-msgid ""
-"zone_driver = "
-"cinder.zonemanager.drivers.brocade.brcd_fc_zone_driver.BrcdFCZoneDriver"
-msgstr "zone_driver = cinder.zonemanager.drivers.brocade.brcd_fc_zone_driver.BrcdFCZoneDriver"
-
-#: ./doc/common/tables/cinder-zoning_manager.xml31(td)
-msgid "(StrOpt) FC Zone Driver responsible for zone management"
-msgstr ""
-
-#: ./doc/common/tables/trove-volume.xml8(caption)
-msgid "Description of configuration options for volume"
-msgstr ""
-
-#: ./doc/common/tables/trove-volume.xml22(td)
-msgid "block_device_mapping = vdb"
-msgstr ""
-
-#: ./doc/common/tables/trove-volume.xml26(td)
-msgid "cinder_url = http://localhost:8776/v2"
-msgstr "cinder_url = http://localhost:8776/v2"
-
-#: ./doc/common/tables/trove-volume.xml30(td)
-msgid "device_path = /dev/vdb"
-msgstr "device_path = /dev/vdb"
-
-#: ./doc/common/tables/trove-volume.xml34(td)
-msgid "trove_volume_support = True"
-msgstr "trove_volume_support = True"
-
-#: ./doc/common/tables/trove-volume.xml35(td)
-msgid "(BoolOpt) Whether to provision a cinder volume for datadir."
-msgstr ""
-
-#: ./doc/common/tables/trove-volume.xml38(td)
-msgid "volume_format_timeout = 120"
-msgstr "volume_format_timeout = 120"
-
-#: ./doc/common/tables/trove-volume.xml42(td)
-msgid "volume_fstype = ext3"
-msgstr "volume_fstype = ext3"
-
-#: ./doc/common/tables/trove-volume.xml46(td)
-msgid "volume_time_out = 60"
-msgstr "volume_time_out = 60"
-
-#: ./doc/common/tables/keystone-cache.xml8(caption)
-msgid "Description of configuration options for cache"
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml19(th)
-msgid "[cache]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml22(td)
-msgid "backend = keystone.common.cache.noop"
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml23(td)
-msgid ""
-"(StrOpt) Dogpile.cache backend module. It is recommended that Memcache "
-"(dogpile.cache.memcache) or Redis (dogpile.cache.redis) be used in "
-"production deployments. Small workloads (single process) like devstack can "
-"use the dogpile.cache.memory backend."
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml26(td)
-msgid "backend_argument = []"
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml27(td)
-msgid ""
-"(MultiStrOpt) Arguments supplied to the backend module. Specify this option "
-"once per argument to be passed to the dogpile.cache backend. Example format:"
-" \"&lt;argname&gt;:&lt;value&gt;\"."
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml30(td)
-msgid "config_prefix = cache.keystone"
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml31(td)
-msgid ""
-"(StrOpt) Prefix for building the configuration dictionary for the cache "
-"region. This should not need to be changed unless there is another "
-"dogpile.cache region with the same configuration name."
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml34(td)
-msgid "debug_cache_backend = False"
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml35(td)
-msgid ""
-"(BoolOpt) Extra debugging from the cache backend (cache keys, "
-"get/set/delete/etc calls) This is only really useful if you need to see the "
-"specific cache-backend get/set/delete calls with the keys/values. Typically "
-"this should be left set to False."
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml39(td)
-msgid ""
-"(BoolOpt) Global toggle for all caching using the should_cache_fn mechanism."
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml42(td)
-msgid "expiration_time = 600"
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml43(td)
-msgid ""
-"(IntOpt) Default TTL, in seconds, for any cached item in the dogpile.cache "
-"region. This applies to any cached method that doesn't have an explicit "
-"cache expiration time defined for it."
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml46(td)
-msgid "proxies ="
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml47(td)
-msgid ""
-"(ListOpt) Proxy Classes to import that will affect the way the dogpile.cache"
-" backend functions. See the dogpile.cache documentation on changing-backend-"
-"behavior. Comma delimited list e.g. my.dogpile.proxy.Class, "
-"my.dogpile.proxyClass2."
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml50(td)
-msgid "use_key_mangler = True"
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml51(td)
-msgid ""
-"(BoolOpt) Use a key-mangling function (sha1) to ensure fixed length cache-"
-"keys. This is toggle-able for debugging purposes, it is highly recommended "
-"to always leave this set to True."
-msgstr ""
-
-#: ./doc/common/tables/glance-testing.xml22(td)
-msgid "pydev_worker_debug_host = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-testing.xml23(td)
-msgid ""
-"(StrOpt) The hostname/IP of the pydev process listening for debug "
-"connections"
-msgstr ""
-
-#: ./doc/common/tables/glance-testing.xml26(td)
-msgid "pydev_worker_debug_port = 5678"
-msgstr ""
-
-#: ./doc/common/tables/glance-testing.xml27(td)
-msgid ""
-"(IntOpt) The port on which a pydev process is listening for connections."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml7(literal)
-msgid "[filter:tempauth]"
-msgstr "[filter:tempauth]"
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml18(td)
-msgid "use = egg:swift#tempauth"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml21(td)
-msgid "set log_name = tempauth"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml36(td)
-msgid "reseller_prefix = AUTH"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml36(td)
-msgid "The naming scope for the auth service. Swift"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml39(td)
-msgid "auth_prefix = /auth/"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml39(td)
-msgid ""
-"The HTTP request path prefix for the auth service. Swift itself reserves "
-"anything beginning with the letter `v`."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml42(td)
-msgid "token_life = 86400"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml42(td)
-msgid "The number of seconds a token is valid."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml45(td)
-msgid "allow_overrides = true"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml48(td)
-msgid "storage_url_scheme = default"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml48(td)
-msgid ""
-"Scheme to return with storage urls: http, https, or default (chooses based "
-"on what the server is running as) This can be useful with an SSL load "
-"balancer in front of a non-SSL server."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml51(td)
-msgid "user_admin_admin = admin .admin .reseller_admin"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml54(td)
-msgid "user_test_tester = testing .admin"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml57(td)
-msgid "user_test2_tester2 = testing2 .admin"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml60(td)
-msgid "user_test_tester3 = testing3"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml8(caption)
-msgid "Description of configuration options for registry"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml23(td)
-msgid "(StrOpt) The administrators password."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml27(td)
-msgid "(StrOpt) The tenant name of the administrative user."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml31(td)
-msgid "(StrOpt) The administrators user name."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml35(td)
-msgid "(StrOpt) The region for the authentication service."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml39(td)
-msgid "(StrOpt) The strategy to use for authentication."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml43(td)
-msgid "(StrOpt) The URL to the keystone service."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml46(td)
-msgid "registry_client_ca_file = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml47(td)
-msgid ""
-"(StrOpt) The path to the certifying authority cert file to use in SSL "
-"connections to the registry server."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml50(td)
-msgid "registry_client_cert_file = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml51(td)
-msgid ""
-"(StrOpt) The path to the cert file to use in SSL connections to the registry"
-" server."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml54(td)
-msgid "registry_client_insecure = False"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml55(td)
-msgid ""
-"(BoolOpt) When using SSL in connections to the registry server, do not "
-"require validation via a certifying authority."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml58(td)
-msgid "registry_client_key_file = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml59(td)
-msgid ""
-"(StrOpt) The path to the key file to use in SSL connections to the registry "
-"server."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml62(td)
-msgid "registry_client_protocol = http"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml63(td)
-msgid ""
-"(StrOpt) The protocol to use for communication with the registry server. "
-"Either http or https."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml66(td)
-msgid "registry_client_timeout = 600"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml67(td)
-msgid ""
-"(IntOpt) The period of time, in seconds, that the API server will wait for a"
-" registry request to complete. A value of 0 implies no timeout."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml70(td)
-msgid "registry_host = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml71(td)
-msgid "(StrOpt) Address to find the registry server."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml74(td)
-msgid "registry_port = 9191"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml75(td)
-msgid "(IntOpt) Port the registry server is listening on."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml7(literal)
-msgid "[object-replicator]"
-msgstr "[object-replicator]"
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml18(td)
-msgid "log_name = object-replicator"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml33(td)
-msgid "daemonize = on"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml33(td)
-msgid "Whether or not to run replication as a daemon"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml42(td)
-msgid "stats_interval = 300"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml42(td)
-msgid "Interval in seconds between logging replication statistics"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml45(td)
-msgid "sync_method = rsync"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml48(td)
-msgid "rsync_timeout = 900"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml48(td)
-msgid "Max duration (seconds) of a partition rsync"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml51(td)
-msgid "rsync_bwlimit = 0"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml54(td)
-msgid "rsync_io_timeout = 30"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml54(td)
-msgid "Passed to rsync for a max duration (seconds) of an I/O op"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml60(td)
-msgid "http_timeout = 60"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml60(td)
-msgid "Maximum duration for an HTTP request"
-msgstr "Durée maximum d'une requête HTTP"
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml63(td)
-msgid "lockup_timeout = 1800"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml63(td)
-msgid ""
-"Attempts to kill all workers if nothing replications for lockup_timeout "
-"seconds"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml69(td)
-msgid "ring_check_interval = 15"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml69(td)
-msgid "How often (in seconds) to check the ring"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml75(td)
-msgid "rsync_error_log_line_length = 0"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml78(td)
-msgid "handoffs_first = False"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml78(td)
-msgid ""
-"If set to True, partitions that are not supposed to be on the node will be "
-"replicated first. The default setting should not be changed, except for "
-"extreme situations."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml81(td)
-msgid "handoff_delete = auto"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml81(td)
-msgid ""
-"By default handoff partitions will be removed when it has successfully "
-"replicated to all the canonical nodes. If set to an integer n, it will "
-"remove the partition if it is successfully replicated to n nodes. The "
-"default setting should not be changed, except for extremem situations. This "
-"uses what's set here, or what's set in the DEFAULT section, or 10 (though "
-"other sections use 3 as the final default)."
-msgstr ""
-
 #: ./doc/common/tables/trove-database.xml22(td)
 msgid "sql_connection = sqlite:///trove_test.sqlite"
 msgstr "sql_connection = sqlite:///trove_test.sqlite"
@@ -43411,1501 +44246,242 @@ msgid ""
 "(BoolOpt) Allow insecure logging while executing queries through SQLAlchemy."
 msgstr ""
 
-#: ./doc/common/tables/heat-clients_backends.xml8(caption)
-msgid "Description of configuration options for clients_backends"
+#: ./doc/common/tables/swift-container-server-app-container-server.xml7(literal)
+msgid "[app:container-server]"
 msgstr ""
 
-#: ./doc/common/tables/heat-clients_backends.xml22(td)
-msgid "cloud_backend = heat.engine.clients.OpenStackClients"
-msgstr "cloud_backend = heat.engine.clients.OpenStackClients"
-
-#: ./doc/common/tables/heat-clients_backends.xml23(td)
-msgid "(StrOpt) Fully qualified class name to use as a client backend."
+#: ./doc/common/tables/swift-container-server-app-container-server.xml18(td)
+msgid "use = egg:swift#container"
 msgstr ""
 
-#: ./doc/common/tables/heat-amqp.xml30(td)
-msgid "control_exchange = heat"
-msgstr "control_exchange = heat"
-
-#: ./doc/common/tables/heat-amqp.xml43(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml23(td)
-#: ./doc/common/tables/neutron-testing.xml27(td)
-#: ./doc/common/tables/trove-amqp.xml39(td)
-msgid "(BoolOpt) If passed, use a fake RabbitMQ provider"
+#: ./doc/common/tables/swift-container-server-app-container-server.xml21(td)
+msgid "set log_name = container-server"
 msgstr ""
 
-#: ./doc/common/tables/heat-amqp.xml46(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml42(td)
+msgid "allow_versions = false"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-app-container-server.xml42(td)
+msgid "Enable/Disable object versioning feature"
+msgstr ""
+
+#: ./doc/common/tables/nova-authentication.xml8(caption)
+msgid "Description of configuration options for authentication"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml8(caption)
+msgid "Description of configuration options for nvsd"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml23(td)
+msgid "(StrOpt) integration bridge"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml26(th)
+msgid "[nvsd]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml29(td)
+msgid "nvsd_ip = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml30(td)
+msgid "(StrOpt) NVSD Controller IP address"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml33(td)
+msgid "nvsd_passwd = oc123"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml34(td)
+msgid "(StrOpt) NVSD Controller password"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml37(td)
+msgid "nvsd_port = 8082"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml38(td)
+msgid "(IntOpt) NVSD Controller Port number"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml41(td)
+msgid "nvsd_retries = 0"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml42(td)
+msgid "(IntOpt) Number of login retries to NVSD controller"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml45(td)
+msgid "nvsd_user = ocplugin"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml46(td)
+msgid "(StrOpt) NVSD Controller username"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml49(td)
+msgid "request_timeout = 30"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml50(td)
+msgid "(IntOpt) NVSD controller REST API request timeout in seconds"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-pipeline-main.xml18(td)
+msgid "pipeline = healthcheck recon account-server"
+msgstr ""
+
+#: ./doc/common/tables/glance-gridfs.xml8(caption)
+msgid "Description of configuration options for gridfs"
+msgstr ""
+
+#: ./doc/common/tables/glance-gridfs.xml22(td)
+msgid "mongodb_store_db = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-gridfs.xml23(td)
+msgid "(StrOpt) Database to use."
+msgstr ""
+
+#: ./doc/common/tables/glance-gridfs.xml26(td)
+msgid "mongodb_store_uri = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-gridfs.xml27(td)
 msgid ""
-"list_notifier_drivers = ['heat.openstack.common.notifier.no_op_notifier']"
-msgstr "list_notifier_drivers = ['heat.openstack.common.notifier.no_op_notifier']"
-
-#: ./doc/common/tables/heat-amqp.xml47(td)
-msgid "(MultiStrOpt) List of drivers to send notifications"
+"(StrOpt) Hostname or IP address of the instance to connect to, or a mongodb "
+"URI, or a list of hostnames / mongodb URIs. If host is an IPv6 literal it "
+"must be enclosed in '[' and ']' characters following the RFC2732 URL syntax "
+"(e.g. '[::1]' for localhost)."
 msgstr ""
 
-#: ./doc/common/tables/heat-amqp.xml55(td)
-#: ./doc/common/tables/ceilometer-amqp.xml35(td)
-msgid "(ListOpt) AMQP topic used for OpenStack notifications"
+#: ./doc/common/tables/neutron-notifier.xml8(caption)
+msgid "Description of configuration options for notifier"
 msgstr ""
 
-#: ./doc/common/tables/swift-dispersion-dispersion.xml7(literal)
-msgid "[dispersion]"
-msgstr "[dispersion]"
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml7(literal)
-msgid "dispersion.conf-sample"
-msgstr "dispersion.conf-sample"
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml18(td)
-msgid "auth_url = http://localhost:8080/auth/v1.0"
+#: ./doc/common/tables/nova-rpc_all.xml8(caption)
+msgid "Description of configuration options for rpc_all"
 msgstr ""
 
-#: ./doc/common/tables/swift-dispersion-dispersion.xml18(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml27(td)
-msgid "Endpoint for auth server, such as keystone"
+#: ./doc/common/tables/nova-rpc_all.xml201(td)
+#: ./doc/common/tables/nova-rpc.xml65(td)
+msgid "rpc_driver_queue_base = cells.intercell"
 msgstr ""
 
-#: ./doc/common/tables/swift-dispersion-dispersion.xml21(td)
-msgid "auth_user = test:tester"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml21(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml30(td)
-msgid "Default user for dispersion in this context"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml24(td)
-msgid "auth_key = testing"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml27(td)
-msgid "auth_url = http://localhost:5000/v2.0/"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml30(td)
-msgid "auth_user = tenant:user"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml33(td)
-msgid "auth_key = password"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml36(td)
-msgid "auth_version = 2.0"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml36(td)
-msgid "Indicates which version of auth"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml39(td)
-msgid "Indicates whether endpoint for auth is public or internal"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml42(td)
-msgid "keystone_api_insecure = no"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml48(td)
-msgid "dispersion_coverage = 1.0"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml51(td)
-msgid "retries = 5"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml54(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml30(td)
-msgid "concurrency = 25"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml57(td)
-msgid "container_populate = yes"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml60(td)
-msgid "object_populate = yes"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml63(td)
-msgid "container_report = yes"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml66(td)
-msgid "object_report = yes"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml69(td)
-msgid "dump_json = no"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hpmsa.xml8(caption)
-msgid "Description of configuration options for hpmsa"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hpmsa.xml22(td)
-msgid "msa_vdisk = OpenStack"
-msgstr "msa_vdisk = OpenStack"
-
-#: ./doc/common/tables/cinder-hpmsa.xml23(td)
-msgid "(StrOpt) The VDisk to use for volume creation."
-msgstr ""
-
-#: ./doc/common/tables/cinder-emc.xml8(caption)
-msgid "Description of configuration options for emc"
-msgstr ""
-
-#: ./doc/common/tables/cinder-emc.xml22(td)
-msgid "cinder_emc_config_file = /etc/cinder/cinder_emc_config.xml"
-msgstr ""
-
-#: ./doc/common/tables/cinder-emc.xml23(td)
-msgid "(StrOpt) use this file for cinder emc plugin config data"
-msgstr ""
-
-#: ./doc/common/tables/cinder-emc.xml26(td)
-msgid "max_luns_per_storage_group = 256"
-msgstr ""
-
-#: ./doc/common/tables/cinder-emc.xml27(td)
-msgid "(IntOpt) Default max number of LUNs in a storage group"
-msgstr ""
-
-#: ./doc/common/tables/cinder-emc.xml30(td)
-msgid "naviseccli_path ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-emc.xml31(td)
-msgid "(StrOpt) Naviseccli Path"
-msgstr ""
-
-#: ./doc/common/tables/cinder-emc.xml34(td)
-msgid "storage_vnx_pool_name = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-emc.xml35(td)
-msgid "(StrOpt) ISCSI pool name"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-account-replicator.xml7(literal)
-msgid "[account-replicator]"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-account-replicator.xml18(td)
-msgid "log_name = account-replicator"
-msgstr ""
-
-#: ./doc/common/tables/neutron-fwaas.xml8(caption)
-msgid "Description of configuration options for fwaas"
-msgstr ""
-
-#: ./doc/common/tables/neutron-fwaas.xml19(th)
-#: ./doc/common/tables/neutron-nec.xml73(th)
-msgid "[fwaas]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-fwaas.xml23(td)
-msgid "(BoolOpt) Enable FWaaS"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups_tsm.xml8(caption)
-msgid "Description of configuration options for backups_tsm"
-msgstr "Description des options de configuration pour backups_tsm"
-
-#: ./doc/common/tables/cinder-backups_tsm.xml22(td)
-msgid "backup_tsm_compression = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups_tsm.xml23(td)
-msgid "(BoolOpt) Enable or Disable compression for backups"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups_tsm.xml26(td)
-msgid "backup_tsm_password = password"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups_tsm.xml27(td)
-msgid "(StrOpt) TSM password for the running username"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups_tsm.xml30(td)
-msgid "backup_tsm_volume_prefix = backup"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups_tsm.xml31(td)
-msgid "(StrOpt) Volume prefix for the backup id when backing up to TSM"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml8(caption)
-msgid "Description of configuration options for sdnve"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml19(th)
-msgid "[SDNVE]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml22(td)
-msgid "base_url = /one/nb/v2/"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml23(td)
-msgid "(StrOpt) Base URL for SDN-VE controller REST API"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml26(td)
-msgid "controller_ips = 127.0.0.1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml27(td)
-msgid "(ListOpt) List of IP addresses of SDN-VE controller(s)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml30(td)
-msgid "default_tenant_type = OF"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml31(td)
-msgid "(StrOpt) Tenant type: OF (default) and OVERLAY"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml34(td)
-msgid "format = json"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml35(td)
-msgid "(StrOpt) SDN-VE request/response format"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml38(td)
-msgid "info = sdnve_info_string"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml39(td)
-msgid "(StrOpt) SDN-VE RPC subject"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml42(td)
-msgid "integration_bridge = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml46(td)
-msgid "interface_mappings ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml47(td)
-msgid "(ListOpt) List of &lt;physical_network_name&gt;:&lt;interface_name&gt;"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml50(td)
-msgid "of_signature = SDNVE-OF"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml51(td)
+#: ./doc/common/tables/nova-rpc_all.xml202(td)
+#: ./doc/common/tables/nova-rpc.xml66(td)
 msgid ""
-"(StrOpt) The string in tenant description that indicates the tenant is a OF "
-"tenant"
+"(StrOpt) Base queue name to use when communicating between cells. Various "
+"topics by message type will be appended to this."
 msgstr ""
 
-#: ./doc/common/tables/neutron-sdnve.xml54(td)
-msgid "out_of_band = True"
+#: ./doc/common/tables/nova-rpc_all.xml215(td)
+#: ./doc/common/tables/nova-rpc.xml79(td)
+msgid "baseapi = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-sdnve.xml55(td)
-msgid "(BoolOpt) Indicating if controller is out of band or not"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml58(td)
-msgid "overlay_signature = SDNVE-OVERLAY"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml59(td)
+#: ./doc/common/tables/nova-rpc_all.xml216(td)
+#: ./doc/common/tables/nova-rpc.xml80(td)
 msgid ""
-"(StrOpt) The string in tenant description that indicates the tenant is a "
-"OVERLAY tenant"
+"(StrOpt) Set a version cap for messages sent to the base api in any service"
 msgstr ""
 
-#: ./doc/common/tables/neutron-sdnve.xml62(td)
-msgid "password = admin"
+#: ./doc/common/tables/neutron-hyperv_agent.xml8(caption)
+msgid "Description of configuration options for hyperv_agent"
 msgstr ""
 
-#: ./doc/common/tables/neutron-sdnve.xml63(td)
-msgid "(StrOpt) SDN-VE administrator password"
+#: ./doc/common/tables/neutron-hyperv_agent.xml22(td)
+msgid "enable_metrics_collection = False"
 msgstr ""
 
-#: ./doc/common/tables/neutron-sdnve.xml66(td)
-msgid "port = 8443"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml67(td)
-msgid "(StrOpt) SDN-VE controller port number"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml70(td)
-msgid "reset_bridge = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml71(td)
-msgid "(BoolOpt) Reset the integration bridge before use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml74(td)
-msgid "use_fake_controller = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml75(td)
-msgid "(BoolOpt) If set to True uses a fake controller."
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml78(td)
-msgid "userid = admin"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml79(td)
-msgid "(StrOpt) SDN-VE administrator user id"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml82(th)
-msgid "[SDNVE_AGENT]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml86(td)
-msgid "(IntOpt) Agent polling interval if necessary"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml90(td)
-msgid "(StrOpt) Using root helper"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml93(td)
-msgid "rpc = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml94(td)
-msgid "(BoolOpt) Whether using rpc"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_mysql.xml8(caption)
-msgid "Description of configuration options for db_mysql"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_mysql.xml19(th)
-msgid "[mysql]"
-msgstr "[mysql]"
-
-#: ./doc/common/tables/trove-db_mysql.xml26(td)
-#: ./doc/common/tables/trove-db_percona.xml26(td)
-msgid "mount_point = /var/lib/mysql"
-msgstr "mount_point = /var/lib/mysql"
-
-#: ./doc/common/tables/trove-db_mysql.xml30(td)
-#: ./doc/common/tables/trove-db_percona.xml30(td)
-msgid "root_on_create = False"
-msgstr "root_on_create = False"
-
-#: ./doc/common/tables/trove-db_mysql.xml31(td)
-#: ./doc/common/tables/trove-db_percona.xml31(td)
+#: ./doc/common/tables/neutron-hyperv_agent.xml23(td)
 msgid ""
-"(BoolOpt) Enable the automatic creation of the root user for the service "
-"during instance-create. The generated password for the root user is "
-"immediately returned in the response of instance-create as the 'password' "
-"field."
+"(BoolOpt) Enables metrics collections for switch ports by using Hyper-V's "
+"metric APIs. Collected data can by retrieved by other apps and services, "
+"e.g.: Ceilometer. Requires Hyper-V / Windows Server 2012 and above"
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mysql.xml34(td)
-#: ./doc/common/tables/trove-db_percona.xml34(td)
-msgid "tcp_ports = 3306"
-msgstr "tcp_ports = 3306"
-
-#: ./doc/common/tables/trove-db_mysql.xml42(td)
-msgid "usage_timeout = 400"
+#: ./doc/common/tables/neutron-hyperv_agent.xml26(td)
+msgid "local_network_vswitch = private"
 msgstr ""
 
-#: ./doc/common/tables/trove-rpc.xml38(td)
-msgid "num_tries = 3"
-msgstr "num_tries = 3"
-
-#: ./doc/common/tables/trove-rpc.xml47(td)
-msgid "(IntOpt) The interval in seconds which periodic tasks are run."
+#: ./doc/common/tables/neutron-hyperv_agent.xml27(td)
+msgid "(StrOpt) Private vswitch name used for local networks"
 msgstr ""
 
-#: ./doc/common/tables/trove-rpc.xml50(td)
-msgid "rpc_backend = trove.openstack.common.rpc.impl_kombu"
-msgstr "rpc_backend = trove.openstack.common.rpc.impl_kombu"
+#: ./doc/common/tables/neutron-hyperv_agent.xml30(td)
+msgid "metrics_max_retries = 100"
+msgstr ""
 
-#: ./doc/common/tables/trove-rpc.xml77(th)
-msgid "[secure_messages]"
-msgstr "[secure_messages]"
-
-#: ./doc/common/tables/trove-rpc.xml81(td)
+#: ./doc/common/tables/neutron-hyperv_agent.xml31(td)
 msgid ""
-"(BoolOpt) Whether Secure Messaging (Signing) is enabled, defaults to enabled"
+"(IntOpt) Specifies the maximum number of retries to enable Hyper-V's port "
+"metrics collection. The agent will try to enable the feature once every "
+"polling_interval period for at most metrics_max_retries or until it "
+"succeedes."
 msgstr ""
 
-#: ./doc/common/tables/trove-rpc.xml84(td)
-msgid "encrypt = False"
-msgstr "encrypt = False"
+#: ./doc/common/tables/neutron-hyperv_agent.xml34(td)
+msgid "physical_network_vswitch_mappings ="
+msgstr ""
 
-#: ./doc/common/tables/trove-rpc.xml85(td)
+#: ./doc/common/tables/neutron-hyperv_agent.xml35(td)
 msgid ""
-"(BoolOpt) Whether Secure Messaging (Encryption) is enabled, defaults to not "
-"enabled"
+"(ListOpt) List of &lt;physical_network&gt;:&lt;vswitch&gt; where the "
+"physical networks can be expressed with wildcards, e.g.: .\"*:external\""
 msgstr ""
 
-#: ./doc/common/tables/trove-rpc.xml88(td)
-msgid "enforced = False"
-msgstr "enforced = False"
-
-#: ./doc/common/tables/trove-rpc.xml89(td)
+#: ./doc/common/tables/neutron-hyperv_agent.xml39(td)
 msgid ""
-"(BoolOpt) Whether Secure Messaging (Signing) is enforced, defaults to not "
-"enforced"
+"(IntOpt) The number of seconds the agent will wait between polling for local"
+" device changes."
 msgstr ""
 
-#: ./doc/common/tables/trove-rpc.xml92(td)
-msgid "kds_endpoint = None"
-msgstr "kds_endpoint = None"
-
-#: ./doc/common/tables/trove-rpc.xml93(td)
-msgid "(StrOpt) KDS endpoint (ex: http://kds.example.com:35357/v3)"
+#: ./doc/common/tables/neutron-hyperv_agent.xml42(th)
+msgid "[HYPERV]"
 msgstr ""
 
-#: ./doc/common/tables/trove-rpc.xml96(td)
-msgid "secret_key = None"
-msgstr "secret_key = None"
+#: ./doc/common/tables/neutron-hyperv_agent.xml50(td)
+msgid "(StrOpt) Network type for tenant networks (local, flat, vlan or none)"
+msgstr ""
 
-#: ./doc/common/tables/trove-rpc.xml97(td)
+#: ./doc/common/tables/neutron-hyperv_agent.xml56(td)
+#: ./doc/common/tables/nova-hyperv.xml30(td)
+msgid "force_hyperv_utils_v1 = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-hyperv_agent.xml57(td)
+#: ./doc/common/tables/nova-hyperv.xml31(td)
+msgid "(BoolOpt) Force V1 WMI utility classes"
+msgstr ""
+
+#: ./doc/common/tables/keystone-federation.xml8(caption)
+msgid "Description of configuration options for federation"
+msgstr ""
+
+#: ./doc/common/tables/keystone-federation.xml19(th)
+msgid "[federation]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-federation.xml22(td)
+msgid "assertion_prefix ="
+msgstr ""
+
+#: ./doc/common/tables/keystone-federation.xml23(td)
 msgid ""
-"(MultiStrOpt) A list of keys: (ex: name:&lt;base64 encoded key&gt;), ignored"
-" if secret_keys_file is set"
+"(StrOpt) Value to be used when filtering assertion parameters from the "
+"environment."
 msgstr ""
 
-#: ./doc/common/tables/trove-rpc.xml100(td)
-msgid "secret_keys_file = None"
-msgstr "secret_keys_file = None"
-
-#: ./doc/common/tables/trove-rpc.xml101(td)
-msgid ""
-"(StrOpt) Path to the file containing the keys, takes precedence over "
-"secret_key"
-msgstr ""
-
-#: ./doc/common/tables/cinder-connection.xml8(caption)
-msgid "Description of configuration options for connection"
-msgstr ""
-
-#: ./doc/common/tables/cinder-connection.xml22(td)
-msgid "connection = sqlite:///$state_path/$sqlite_db"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml18(td)
-msgid "mtime_check_interval = 300"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml7(literal)
-msgid "[filter:authtoken]"
-msgstr "[filter:authtoken]"
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml18(td)
-msgid "auth_host = keystonehost"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml24(td)
-msgid "auth_protocol = http"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml27(td)
-msgid "auth_uri = http://keystonehost:5000/"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml30(td)
-msgid "admin_tenant_name = service"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml33(td)
-msgid "admin_user = swift"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml36(td)
-msgid "admin_password = password"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml39(td)
-msgid "delay_auth_decision = 1"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml42(td)
-msgid "cache = swift.cache"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml45(td)
-msgid "include_service_catalog = False"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_redis.xml8(caption)
-msgid "Description of configuration options for db_redis"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_redis.xml19(th)
-msgid "[redis]"
-msgstr "[redis]"
-
-#: ./doc/common/tables/trove-db_redis.xml26(td)
-msgid "mount_point = /var/lib/redis"
-msgstr "mount_point = /var/lib/redis"
-
-#: ./doc/common/tables/trove-db_redis.xml30(td)
-msgid "tcp_ports = 6379"
-msgstr "tcp_ports = 6379"
-
-#: ./doc/common/tables/neutron-zeromq.xml38(td)
-msgid ""
-"rpc_zmq_matchmaker = "
-"neutron.openstack.common.rpc.matchmaker.MatchMakerLocalhost"
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml8(caption)
-msgid "Description of configuration options for token"
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml19(th)
-msgid "[token]"
-msgstr "[token]"
-
-#: ./doc/common/tables/keystone-token.xml22(td)
-msgid "bind ="
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml23(td)
-msgid ""
-"(ListOpt) External auth mechanisms that should add bind information to token"
-" e.g. kerberos, x509."
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml27(td)
-msgid ""
-"(IntOpt) Time to cache tokens (in seconds). This has no effect unless global"
-" and token caching are enabled."
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml31(td)
-msgid ""
-"(BoolOpt) Toggle for token system cacheing. This has no effect unless global"
-" caching is enabled."
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml34(td)
-msgid "driver = keystone.token.backends.sql.Token"
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml35(td)
-msgid "(StrOpt) Keystone Token persistence backend driver."
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml39(td)
-msgid ""
-"(StrOpt) Enforcement policy on tokens presented to keystone with bind "
-"information. One of disabled, permissive, strict, required or a specifically"
-" required bind mode e.g. kerberos or x509 to require binding to that "
-"authentication."
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml42(td)
-msgid "expiration = 3600"
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml43(td)
-msgid "(IntOpt) Amount of time a token should remain valid (in seconds)."
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml46(td)
-msgid "provider = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml47(td)
-msgid ""
-"(StrOpt) Controls the token construction, validation, and revocation "
-"operations. Core providers are "
-"\"keystone.token.providers.[pki|uuid].Provider\"."
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml50(td)
-msgid "revocation_cache_time = 3600"
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml51(td)
-msgid ""
-"(IntOpt) Time to cache the revocation list and the revocation events if "
-"revoke extension is enabled (in seconds). This has no effect unless global "
-"and token caching are enabled."
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml54(td)
-msgid "revoke_by_id = True"
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml55(td)
-msgid ""
-"(BoolOpt) Revoke token by token identifier. Setting revoke_by_id to True "
-"enables various forms of enumerating tokens, e.g. `list tokens for user`. "
-"These enumerations are processed to determine the list of tokens to revoke. "
-"Only disable if you are switching to using the Revoke extension with a "
-"backend other than KVS, which stores events in memory."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml19(th)
-msgid "[ipsec]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml22(td)
-msgid "config_base_dir = $state_path/ipsec"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml23(td)
-msgid "(StrOpt) Location to store ipsec server config files"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml26(td)
-msgid "ipsec_status_check_interval = 60"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml27(td)
-msgid "(IntOpt) Interval for checking ipsec status"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml30(th)
-msgid "[openswan]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml33(td)
-msgid ""
-"ipsec_config_template = /usr/lib/python/site-"
-"packages/neutron/services/vpn/device_drivers/template/openswan/ipsec.conf.template"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml34(td)
-msgid "(StrOpt) Template file for ipsec configuration"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml37(td)
-msgid ""
-"ipsec_secret_template = /usr/lib/python/site-"
-"packages/neutron/services/vpn/device_drivers/template/openswan/ipsec.secret.template"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml38(td)
-msgid "(StrOpt) Template file for ipsec secret configuration"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml41(th)
-msgid "[vpnagent]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml44(td)
-msgid ""
-"vpn_device_driver = "
-"['neutron.services.vpn.device_drivers.ipsec.OpenSwanDriver']"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml45(td)
-msgid "(MultiStrOpt) The vpn device drivers Neutron will use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-agent.xml8(caption)
-msgid "Description of configuration options for agent"
-msgstr ""
-
-#: ./doc/common/tables/neutron-agent.xml22(td)
-msgid "external_pids = $state_path/external/pids"
-msgstr ""
-
-#: ./doc/common/tables/neutron-agent.xml23(td)
-msgid "(StrOpt) Location to store child pid files"
-msgstr ""
-
-#: ./doc/common/tables/neutron-agent.xml27(td)
-msgid "(IntOpt) MTU setting for device."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml8(caption)
-msgid "Description of configuration options for ryu"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml22(td)
-msgid "openflow_rest_api = 127.0.0.1:8080"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml23(td)
-msgid "(StrOpt) OpenFlow REST API location"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml26(td)
-msgid "ovsdb_interface = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml27(td)
-msgid "(StrOpt) OVSDB interface to connect to"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml30(td)
-msgid "ovsdb_ip = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml31(td)
-msgid "(StrOpt) OVSDB IP to connect to"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml34(td)
-msgid "ovsdb_port = 6634"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml35(td)
-msgid "(IntOpt) OVSDB port to connect to"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml38(td)
-msgid "tunnel_interface = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml39(td)
-msgid "(StrOpt) Tunnel interface to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml42(td)
-msgid "tunnel_ip = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml43(td)
-msgid "(StrOpt) Tunnel IP to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml46(td)
-msgid "tunnel_key_max = 16777215"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml47(td)
-msgid "(IntOpt) Maximum tunnel ID to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml50(td)
-msgid "tunnel_key_min = 1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml51(td)
-msgid "(IntOpt) Minimum tunnel ID to use"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml7(literal)
-msgid "[app:object-server]"
-msgstr "[app:object-server]"
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml18(td)
-msgid "use = egg:swift#object"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml21(td)
-msgid "set log_name = object-server"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml36(td)
-msgid "max_upload_time = 86400"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml36(td)
-msgid "Maximum time allowed to upload an object"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml39(td)
-msgid "slow = 0"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml39(td)
-msgid ""
-"If &gt; 0, Minimum time in seconds for a PUT or DELETE request to complete"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml42(td)
-msgid "keep_cache_size = 5424880"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml42(td)
-msgid "Largest object size to keep in buffer cache"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml45(td)
-msgid "keep_cache_private = false"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml45(td)
-msgid "Allow non-public objects to stay in kernel's buffer cache"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml48(td)
-msgid "mb_per_sync = 512"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml48(td)
-msgid "On PUT requests, sync file every n MB"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml51(td)
-msgid ""
-"allowed_headers = Content-Disposition, Content-Encoding, X-Delete-At, X"
-"-Object-Manifest, X-Static-Large-Object"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml51(td)
-msgid ""
-"Comma-separated list of headers that can be set in metadata of an object"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml57(td)
-msgid "threads_per_disk = 0"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml57(td)
-msgid ""
-"Size of the per-disk thread pool used for performing disk I/O. The default "
-"of 0 means to not use a per-disk thread pool. It is recommended to keep this"
-" value small, as large values can result in high read latencies due to large"
-" queue depths. A good starting point is 4 threads per disk."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml63(td)
-msgid "replication_concurrency = 4"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml63(td)
-msgid ""
-"Set to restrict the number of concurrent incoming REPLICATION requests; set "
-"to 0 for unlimited"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml66(td)
-msgid "replication_one_per_device = True"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml66(td)
-msgid ""
-"Restricts incoming REPLICATION requests to one per device, "
-"replication_currency above allowing. This can help control I/O to each "
-"device, but you may wish to set this to False to allow multiple REPLICATION "
-"requests (up to the above replication_concurrency setting) per device."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml69(td)
-msgid "replication_lock_timeout = 15"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml69(td)
-msgid ""
-"Number of seconds to wait for an existing replication device lock before "
-"giving up."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml72(td)
-msgid "replication_failure_threshold = 100"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml72(td)
-msgid ""
-"The number of subrequest failures before the replication_failure_ratio is "
-"checked"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml75(td)
-msgid "replication_failure_ratio = 1.0"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml75(td)
-msgid ""
-"If the value of failures / successes of REPLICATION subrequests exceeds this"
-" ratio, the overall REPLICATION request will be aborted"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_couchbase.xml8(caption)
-msgid "Description of configuration options for db_couchbase"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_couchbase.xml19(th)
-msgid "[couchbase]"
-msgstr "[couchbase]"
-
-#: ./doc/common/tables/trove-db_couchbase.xml26(td)
-msgid "mount_point = /var/lib/couchbase"
-msgstr "mount_point = /var/lib/couchbase"
-
-#: ./doc/common/tables/trove-db_couchbase.xml30(td)
-msgid "tcp_ports = 8091, 8092, 4369, 11209-11211, 21100-21199"
-msgstr "tcp_ports = 8091, 8092, 4369, 11209-11211, 21100-21199"
-
-#: ./doc/common/tables/neutron-policy.xml22(td)
-msgid "allow_overlapping_ips = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-policy.xml23(td)
-msgid "(BoolOpt) Allow overlapping IP support in Neutron"
-msgstr ""
-
-#: ./doc/common/tables/neutron-policy.xml27(td)
-msgid "(StrOpt) The policy file to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rootwrap.xml22(td)
-msgid ""
-"filters_path = "
-"/etc/neutron/rootwrap.d,/usr/share/neutron/rootwrap,/etc/quantum/rootwrap.d,/usr/share/quantum/rootwrap"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rootwrap.xml42(th)
-msgid "[xenapi]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rootwrap.xml45(td)
-msgid "xenapi_connection_url = &lt;None&gt;"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rootwrap.xml46(td)
-msgid ""
-"XenAPI configuration is only required by the L2 agent if it is to target a "
-"XenServer/XCP compute host's dom0."
-msgstr ""
-
-#: ./doc/common/tables/neutron-rootwrap.xml49(td)
-#: ./doc/common/tables/cinder-storage_xen.xml30(td)
-msgid "xenapi_connection_username = root"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rootwrap.xml53(td)
-msgid "xenapi_connection_password = &lt;None&gt;"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml21(td)
-msgid "bind_port = 80"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml36(td)
-msgid "expose_info = true"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml36(td)
-msgid "Enables exposing configuration settings via HTTP GET /info."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml39(td)
-msgid "admin_key = secret_admin_key"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml39(td)
-msgid ""
-"to use for admin calls that are HMAC signed. Default is empty, which will "
-"disable admin calls to /info. the proxy server. For most cases, this should "
-"be `egg:swift#proxy`. request whenever it has to failover to a handoff node"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml42(td)
-msgid "disallowed_sections = container_quotas, tempurl"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml58(td)
-msgid "cert_file = /etc/swift/proxy.crt"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml58(td)
-msgid "to the ssl .crt. This should be enabled for testing purposes only."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml61(td)
-msgid "key_file = /etc/swift/proxy.key"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml61(td)
-msgid "to the ssl .key. This should be enabled for testing purposes only."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml79(td)
-msgid "log_headers = false"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml85(td)
-msgid "trans_id_suffix ="
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml115(td)
-msgid "cors_allow_origin ="
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml115(td)
-msgid ""
-"is a list of hosts that are included with any CORS request by default and "
-"returned with the Access-Control-Allow-Origin header in addition to what the"
-" container has set. to call to setup custom log handlers. for eventlet the "
-"proxy server. For most cases, this should be `egg:swift#proxy`. request "
-"whenever it has to failover to a handoff node"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml7(literal)
-msgid "[filter:staticweb]"
-msgstr "[filter:staticweb]"
-
-#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml18(td)
-msgid "use = egg:swift#staticweb"
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml22(td)
-msgid "configurations_page_size = 20"
-msgstr "configurations_page_size = 20"
-
-#: ./doc/common/tables/trove-common.xml26(td)
-msgid "databases_page_size = 20"
-msgstr "databases_page_size = 20"
-
-#: ./doc/common/tables/trove-common.xml30(td)
-msgid "default_datastore = None"
-msgstr "default_datastore = None"
-
-#: ./doc/common/tables/trove-common.xml31(td)
-msgid ""
-"(StrOpt) The default datastore id or name to use if one is not provided by "
-"the user. If the default value is None, the field becomes required in the "
-"instance-create request."
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml38(td)
-msgid "default_neutron_networks ="
-msgstr "default_neutron_networks ="
-
-#: ./doc/common/tables/trove-common.xml39(td)
-msgid ""
-"(ListOpt) List of network IDs which should be attached to instance when "
-"networks are not specified in API call."
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml46(td)
-msgid "default_password_length = 36"
-msgstr "default_password_length = 36"
-
-#: ./doc/common/tables/trove-common.xml54(td)
-msgid "expected_filetype_suffixes = json"
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml55(td)
-msgid ""
-"(ListOpt) Filetype endings not to be reattached to an id by the utils method"
-" correct_id_with_req."
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml62(td)
-msgid "pybasedir = /usr/lib/python/site-packages/trove"
-msgstr "pybasedir = /usr/lib/python/site-packages/trove"
-
-#: ./doc/common/tables/trove-common.xml63(td)
-msgid "(StrOpt) Directory where the trove python module is installed."
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml66(td)
-msgid "pydev_path = None"
-msgstr "pydev_path = None"
-
-#: ./doc/common/tables/trove-common.xml67(td)
-msgid ""
-"(StrOpt) Set path to pydevd library, used if pydevd is not found in python "
-"sys.path."
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml70(td)
-msgid "taskmanager_queue = taskmanager"
-msgstr "taskmanager_queue = taskmanager"
-
-#: ./doc/common/tables/trove-common.xml74(td)
-msgid "template_path = /etc/trove/templates/"
-msgstr "template_path = /etc/trove/templates/"
-
-#: ./doc/common/tables/trove-common.xml75(td)
-msgid "(StrOpt) Path which leads to datastore templates."
-msgstr ""
-
-#: ./doc/common/tables/cinder-ssl.xml8(caption)
-#: ./doc/common/tables/neutron-ssl.xml8(caption)
-#: ./doc/common/tables/trove-ssl.xml8(caption)
-#: ./doc/common/tables/glance-ssl.xml8(caption)
-#: ./doc/common/tables/keystone-ssl.xml8(caption)
-#: ./doc/common/tables/ceilometer-ssl.xml8(caption)
-msgid "Description of configuration options for ssl"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml22(td)
-#: ./doc/common/tables/heat-metadata_api.xml22(td)
-msgid "heat_metadata_server_url ="
-msgstr "heat_metadata_server_url ="
-
-#: ./doc/common/tables/heat-api.xml23(td)
-#: ./doc/common/tables/heat-metadata_api.xml23(td)
-msgid "(StrOpt) URL of the Heat metadata server."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml26(td)
-msgid "heat_stack_user_role = heat_stack_user"
-msgstr "heat_stack_user_role = heat_stack_user"
-
-#: ./doc/common/tables/heat-api.xml27(td)
-msgid "(StrOpt) Keystone role for heat template-defined users."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml38(td)
-msgid "max_json_body_size = 1048576"
-msgstr "max_json_body_size = 1048576"
-
-#: ./doc/common/tables/heat-api.xml39(td)
-msgid ""
-"(IntOpt) Maximum raw byte size of JSON request body. Should be larger than "
-"max_template_size."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml50(td)
-msgid "secure_proxy_ssl_header = X-Forwarded-Proto"
-msgstr "secure_proxy_ssl_header = X-Forwarded-Proto"
-
-#: ./doc/common/tables/heat-api.xml51(td)
-msgid ""
-"(StrOpt) The HTTP Header that will be used to determine which the original "
-"request protocol scheme was, even if it was removed by an SSL terminator "
-"proxy."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml54(td)
-msgid "stack_action_timeout = 3600"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml55(td)
-msgid "(IntOpt) Timeout in seconds for stack action (ie. create or update)."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml58(td)
-msgid "stack_domain_admin = None"
-msgstr "stack_domain_admin = None"
-
-#: ./doc/common/tables/heat-api.xml59(td)
-msgid ""
-"(StrOpt) Keystone username, a user with roles sufficient to manage users and"
-" projects in the stack_user_domain."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml62(td)
-msgid "stack_domain_admin_password = None"
-msgstr "stack_domain_admin_password = None"
-
-#: ./doc/common/tables/heat-api.xml63(td)
-msgid "(StrOpt) Keystone password for stack_domain_admin user."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml66(td)
-msgid "stack_user_domain = None"
-msgstr "stack_user_domain = None"
-
-#: ./doc/common/tables/heat-api.xml67(td)
-msgid ""
-"(StrOpt) Keystone domain ID which contains heat template-defined users."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml70(td)
-msgid "trusts_delegated_roles = heat_stack_owner"
-msgstr "trusts_delegated_roles = heat_stack_owner"
-
-#: ./doc/common/tables/heat-api.xml71(td)
-msgid "(ListOpt) Subset of trustor roles to be delegated to heat."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml74(th)
-msgid "[auth_password]"
-msgstr "[auth_password]"
-
-#: ./doc/common/tables/heat-api.xml77(td)
-#: ./doc/common/tables/heat-api.xml88(td)
-msgid "allowed_auth_uris ="
-msgstr "allowed_auth_uris ="
-
-#: ./doc/common/tables/heat-api.xml78(td)
-#: ./doc/common/tables/heat-api.xml89(td)
-msgid ""
-"(ListOpt) Allowed keystone endpoints for auth_uri when multi_cloud is "
-"enabled. At least one endpoint needs to be specified."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml81(td)
-#: ./doc/common/tables/heat-api.xml96(td)
-msgid "multi_cloud = False"
-msgstr "multi_cloud = False"
-
-#: ./doc/common/tables/heat-api.xml82(td)
-#: ./doc/common/tables/heat-api.xml97(td)
-msgid "(BoolOpt) Allow orchestration of multiple clouds."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml85(th)
-msgid "[ec2authtoken]"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml93(td)
-msgid "(StrOpt) Authentication Endpoint URI."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml100(th)
-msgid "[heat_api]"
-msgstr "[heat_api]"
-
-#: ./doc/common/tables/heat-api.xml111(td)
-msgid "bind_port = 8004"
-msgstr "bind_port = 8004"
-
-#: ./doc/common/tables/heat-api.xml131(th)
-#: ./doc/common/tables/glance-paste.xml19(th)
-#: ./doc/common/tables/keystone-api.xml101(th)
-msgid "[paste_deploy]"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml135(td)
-msgid "(StrOpt) The API paste config file to use."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml138(td)
-#: ./doc/common/tables/glance-paste.xml26(td)
-msgid "flavor = None"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml139(td)
-msgid "(StrOpt) The flavor to use."
-msgstr ""
-
-#: ./doc/common/tables/trove-db_percona.xml8(caption)
-msgid "Description of configuration options for db_percona"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_percona.xml19(th)
-msgid "[percona]"
-msgstr "[percona]"
-
-#: ./doc/common/tables/neutron-meta.xml8(caption)
-msgid "Description of configuration options for meta"
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml19(th)
-msgid "[META]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml22(td)
-msgid "default_flavor ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml23(td)
-msgid "(StrOpt) Default flavor to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml26(td)
-msgid "default_l3_flavor ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml27(td)
-msgid "(StrOpt) Default L3 flavor to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml30(td)
-msgid "extension_map ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml31(td)
-msgid "(StrOpt) A list of extensions, per plugin, to load."
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml34(td)
-msgid "l3_plugin_list ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml35(td)
-msgid "(StrOpt) List of L3 plugins to load"
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml38(td)
-msgid "plugin_list ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml39(td)
-msgid "(StrOpt) List of plugins to load"
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml42(td)
-msgid "rpc_flavor ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml43(td)
-msgid "(StrOpt) Flavor of which plugin handles RPC"
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml46(td)
-msgid "supported_extension_aliases ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml47(td)
-msgid "(StrOpt) Supported extension aliases"
-msgstr ""
-
-#: ./doc/common/tables/neutron-redis.xml23(td)
-msgid "(StrOpt) The hostname Neutron is running on"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml8(caption)
-msgid "Description of configuration options for exchange"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml22(td)
-msgid "cinder_control_exchange = cinder"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml23(td)
-msgid "(StrOpt) Exchange name for Cinder notifications."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml34(td)
-msgid "glance_control_exchange = glance"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml35(td)
-msgid "(StrOpt) Exchange name for Glance notifications."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml38(td)
-msgid "heat_control_exchange = heat"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml39(td)
-msgid "(StrOpt) Exchange name for Heat notifications"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml42(td)
-msgid "http_control_exchanges = ['nova', 'glance', 'neutron', 'cinder']"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml43(td)
-msgid "(MultiStrOpt) Exchanges name to listen for notifications."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml46(td)
-msgid "neutron_control_exchange = neutron"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml47(td)
-msgid "(StrOpt) Exchange name for Neutron notifications."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml50(td)
-msgid "nova_control_exchange = nova"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml51(td)
-msgid "(StrOpt) Exchange name for Nova notifications."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml54(td)
-msgid "sample_source = openstack"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml55(td)
-msgid "(StrOpt) Source for samples emitted on this instance."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-common.xml27(td)
-msgid "(BoolOpt) Whether to disable inter-process locks."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-common.xml42(td)
-msgid "notification_workers = 1"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-common.xml43(td)
-msgid ""
-"(IntOpt) Number of workers for notification service. A single notification "
-"agent is enabled by default."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml8(caption)
-msgid "Description of configuration options for alarm"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml19(th)
-msgid "[alarm]"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml22(td)
-msgid "evaluation_interval = 60"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml23(td)
-msgid ""
-"(IntOpt) Period of evaluation cycle, should be &gt;= than configured "
-"pipeline interval for collection of underlying metrics."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml26(td)
-msgid "evaluation_service = ceilometer.alarm.service.SingletonAlarmService"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml27(td)
-msgid "(StrOpt) Class to launch as alarm evaluation service."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml30(td)
-msgid "notifier_rpc_topic = alarm_notifier"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml31(td)
-msgid "(StrOpt) The topic that ceilometer uses for alarm notifier messages."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml34(td)
-msgid "partition_rpc_topic = alarm_partition_coordination"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml35(td)
-msgid ""
-"(StrOpt) The topic that ceilometer uses for alarm partition coordination "
-"messages."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml38(td)
-msgid "record_history = True"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml39(td)
-msgid "(BoolOpt) Record alarm change events."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml42(td)
-msgid "rest_notifier_certificate_file ="
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml43(td)
-msgid "(StrOpt) SSL Client certificate for REST notifier."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml46(td)
-msgid "rest_notifier_certificate_key ="
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml47(td)
-msgid "(StrOpt) SSL Client private key for REST notifier."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml50(td)
-msgid "rest_notifier_ssl_verify = True"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml51(td)
-msgid ""
-"(BoolOpt) Whether to verify the SSL Server certificate when calling alarm "
-"action."
+#: ./doc/common/tables/keystone-federation.xml26(td)
+msgid "driver = keystone.contrib.federation.backends.sql.Federation"
 msgstr ""
 
-#: ./doc/common/tables/keystone-misc.xml8(caption)
-msgid "Description of configuration options for misc"
+#: ./doc/common/tables/keystone-federation.xml27(td)
+msgid "(StrOpt) Keystone Federation backend driver."
 msgstr ""
 
 #: ./doc/common/tables/nova-scheduling.xml8(caption)
@@ -45049,13 +44625,6 @@ msgid ""
 "ServerGroupAntiAffinityFilter, ServerGroupAffinityFilter"
 msgstr ""
 
-#: ./doc/common/tables/nova-scheduling.xml79(td)
-#: ./doc/common/tables/cinder-scheduler.xml23(td)
-msgid ""
-"(ListOpt) Which filter class names to use for filtering hosts when not "
-"specified in the request."
-msgstr ""
-
 #: ./doc/common/tables/nova-scheduling.xml82(td)
 msgid "scheduler_driver = nova.scheduler.filter_scheduler.FilterScheduler"
 msgstr ""
@@ -45080,11 +44649,6 @@ msgstr ""
 msgid "scheduler_host_manager = nova.scheduler.host_manager.HostManager"
 msgstr ""
 
-#: ./doc/common/tables/nova-scheduling.xml91(td)
-#: ./doc/common/tables/cinder-scheduler.xml35(td)
-msgid "(StrOpt) The scheduler host manager class to use"
-msgstr ""
-
 #: ./doc/common/tables/nova-scheduling.xml94(td)
 msgid "scheduler_host_subset_size = 1"
 msgstr ""
@@ -45098,16 +44662,6 @@ msgid ""
 "will be ignored, and 1 will be used instead"
 msgstr ""
 
-#: ./doc/common/tables/nova-scheduling.xml98(td)
-#: ./doc/common/tables/cinder-scheduler.xml38(td)
-msgid "scheduler_json_config_location ="
-msgstr ""
-
-#: ./doc/common/tables/nova-scheduling.xml99(td)
-#: ./doc/common/tables/cinder-scheduler.xml39(td)
-msgid "(StrOpt) Absolute path to scheduler configuration JSON file."
-msgstr ""
-
 #: ./doc/common/tables/nova-scheduling.xml102(td)
 msgid "scheduler_manager = nova.scheduler.manager.SchedulerManager"
 msgstr ""
@@ -45116,11 +44670,6 @@ msgstr ""
 msgid "(StrOpt) Full class name for the Manager for scheduler"
 msgstr ""
 
-#: ./doc/common/tables/nova-scheduling.xml106(td)
-#: ./doc/common/tables/cinder-scheduler.xml46(td)
-msgid "scheduler_max_attempts = 3"
-msgstr ""
-
 #: ./doc/common/tables/nova-scheduling.xml107(td)
 msgid "(IntOpt) Maximum number of attempts to schedule an instance"
 msgstr ""
@@ -45232,230 +44781,699 @@ msgid ""
 "weight would be name1.value * 1.0 + name2.value * -1.0."
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml133(th)
-msgid "[service_credentials]"
+#: ./doc/common/tables/cinder-eqlx.xml8(caption)
+msgid "Description of configuration options for eqlx"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml137(td)
+#: ./doc/common/tables/cinder-eqlx.xml22(td)
+msgid "eqlx_chap_login = admin"
+msgstr "eqlx_chap_login = admin"
+
+#: ./doc/common/tables/cinder-eqlx.xml23(td)
+msgid "(StrOpt) Existing CHAP account name"
+msgstr ""
+
+#: ./doc/common/tables/cinder-eqlx.xml26(td)
+msgid "eqlx_chap_password = password"
+msgstr "eqlx_chap_password = password"
+
+#: ./doc/common/tables/cinder-eqlx.xml27(td)
+msgid "(StrOpt) Password for specified CHAP account name"
+msgstr ""
+
+#: ./doc/common/tables/cinder-eqlx.xml30(td)
+msgid "eqlx_cli_max_retries = 5"
+msgstr "eqlx_cli_max_retries = 5"
+
+#: ./doc/common/tables/cinder-eqlx.xml31(td)
+msgid "(IntOpt) Maximum retry count for reconnection"
+msgstr ""
+
+#: ./doc/common/tables/cinder-eqlx.xml34(td)
+msgid "eqlx_cli_timeout = 30"
+msgstr "eqlx_cli_timeout = 30"
+
+#: ./doc/common/tables/cinder-eqlx.xml35(td)
+msgid "(IntOpt) Timeout for the Group Manager cli command execution"
+msgstr ""
+
+#: ./doc/common/tables/cinder-eqlx.xml38(td)
+msgid "eqlx_group_name = group-0"
+msgstr "eqlx_group_name = group-0"
+
+#: ./doc/common/tables/cinder-eqlx.xml39(td)
+msgid "(StrOpt) Group name to use for creating volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-eqlx.xml42(td)
+msgid "eqlx_pool = default"
+msgstr "eqlx_pool = default"
+
+#: ./doc/common/tables/cinder-eqlx.xml43(td)
+msgid "(StrOpt) Pool in which volumes will be created"
+msgstr ""
+
+#: ./doc/common/tables/cinder-eqlx.xml46(td)
+msgid "eqlx_use_chap = False"
+msgstr "eqlx_use_chap = False"
+
+#: ./doc/common/tables/cinder-eqlx.xml47(td)
+msgid "(BoolOpt) Use CHAP authentication for targets?"
+msgstr ""
+
+#: ./doc/common/tables/heat-redis.xml23(td)
 msgid ""
-"(BoolOpt) Disables X.509 certificate validation when an SSL connection to "
-"Identity Service is established."
+"(StrOpt) Name of the engine node. This can be an opaque identifier. It is "
+"not necessarily a hostname, FQDN, or IP address."
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml140(td)
-msgid "os_auth_url = http://localhost:5000/v2.0"
+#: ./doc/common/tables/nova-ec2.xml8(caption)
+#: ./doc/common/tables/keystone-ec2.xml8(caption)
+msgid "Description of configuration options for ec2"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml141(td)
-msgid "(StrOpt) Auth URL to use for OpenStack service access."
+#: ./doc/common/tables/nova-ec2.xml22(td)
+msgid "ec2_dmz_host = $my_ip"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml144(td)
-msgid "os_cacert = None"
+#: ./doc/common/tables/nova-ec2.xml23(td)
+msgid "(StrOpt) The internal IP address of the EC2 API server"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml145(td)
-msgid "(StrOpt) Certificate chain for SSL validation."
+#: ./doc/common/tables/nova-ec2.xml26(td)
+msgid "ec2_host = $my_ip"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml148(td)
-msgid "os_endpoint_type = publicURL"
+#: ./doc/common/tables/nova-ec2.xml27(td)
+msgid "(StrOpt) The IP address of the EC2 API server"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml149(td)
+#: ./doc/common/tables/nova-ec2.xml30(td)
+msgid "ec2_listen = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-ec2.xml31(td)
+msgid "(StrOpt) The IP address on which the EC2 API will listen."
+msgstr ""
+
+#: ./doc/common/tables/nova-ec2.xml34(td)
+msgid "ec2_listen_port = 8773"
+msgstr ""
+
+#: ./doc/common/tables/nova-ec2.xml35(td)
+msgid "(IntOpt) The port on which the EC2 API will listen."
+msgstr ""
+
+#: ./doc/common/tables/nova-ec2.xml38(td)
+msgid "ec2_path = /services/Cloud"
+msgstr ""
+
+#: ./doc/common/tables/nova-ec2.xml39(td)
+msgid "(StrOpt) The path prefix used to call the ec2 API server"
+msgstr ""
+
+#: ./doc/common/tables/nova-ec2.xml42(td)
+msgid "ec2_port = 8773"
+msgstr ""
+
+#: ./doc/common/tables/nova-ec2.xml43(td)
+msgid "(IntOpt) The port of the EC2 API server"
+msgstr ""
+
+#: ./doc/common/tables/nova-ec2.xml46(td)
+msgid "ec2_private_dns_show_ip = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-ec2.xml47(td)
 msgid ""
-"(StrOpt) Type of endpoint in Identity service catalog to use for "
-"communication with OpenStack services."
+"(BoolOpt) Return the IP address as private dns hostname in describe "
+"instances"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml152(td)
-msgid "os_password = admin"
+#: ./doc/common/tables/nova-ec2.xml50(td)
+msgid "ec2_scheme = http"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml153(td)
-msgid "(StrOpt) Password to use for OpenStack service access."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-auth.xml157(td)
-msgid "(StrOpt) Region name to use for OpenStack service endpoints."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-auth.xml160(td)
-msgid "os_tenant_id ="
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-auth.xml161(td)
-msgid "(StrOpt) Tenant ID to use for OpenStack service access."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-auth.xml164(td)
-msgid "os_tenant_name = admin"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-auth.xml165(td)
-msgid "(StrOpt) Tenant name to use for OpenStack service access."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-auth.xml168(td)
-msgid "os_username = ceilometer"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-auth.xml169(td)
-msgid "(StrOpt) User name to use for OpenStack service access."
-msgstr ""
-
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml7(literal)
-msgid "[drive-audit]"
-msgstr "[drive-audit]"
-
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml7(literal)
-msgid "drive-audit.conf-sample"
-msgstr "drive-audit.conf-sample"
-
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml18(td)
-msgid "device_dir = /srv/node"
-msgstr ""
-
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml18(td)
-msgid "Directory devices are mounted under"
-msgstr ""
-
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml30(td)
-msgid "minutes = 60"
-msgstr ""
-
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml30(td)
-msgid "Number of minutes to look back in `/var/log/kern.log`"
-msgstr ""
-
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml33(td)
-msgid "error_limit = 1"
-msgstr ""
-
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml33(td)
-msgid "Number of errors to find before a device is unmounted"
-msgstr ""
-
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml36(td)
-msgid "log_file_pattern = /var/log/kern*"
-msgstr ""
-
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml36(td)
+#: ./doc/common/tables/nova-ec2.xml51(td)
 msgid ""
-"Location of the log file with globbing pattern to check against device "
-"errors locate device blocks with errors in the log file"
+"(StrOpt) The protocol to use when connecting to the EC2 API server (http, "
+"https)"
 msgstr ""
 
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml39(td)
-msgid "regex_pattern_1 = \\berror\\b.*\\b(dm-[0-9]{1,2}\\d?)\\b"
+#: ./doc/common/tables/nova-ec2.xml54(td)
+msgid "ec2_strict_validation = True"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_mlnx.xml8(caption)
-msgid "Description of configuration options for ml2_mlnx"
+#: ./doc/common/tables/nova-ec2.xml55(td)
+msgid "(BoolOpt) Validate security group names according to EC2 specification"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_mlnx.xml22(td)
-msgid "apply_profile_patch = False"
+#: ./doc/common/tables/nova-ec2.xml58(td)
+msgid "ec2_timestamp_expiry = 300"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_mlnx.xml23(td)
-msgid "(BoolOpt) Enable server compatibility with old nova"
+#: ./doc/common/tables/nova-ec2.xml59(td)
+msgid "(IntOpt) Time in seconds before ec2 timestamp expires"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_mlnx.xml26(td)
-msgid "vnic_type = mlnx_direct"
+#: ./doc/common/tables/nova-ec2.xml62(td)
+msgid "ec2_workers = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_mlnx.xml27(td)
-msgid "(StrOpt) Type of VM network interface: mlnx_direct or hostdev"
+#: ./doc/common/tables/nova-ec2.xml63(td)
+msgid ""
+"(IntOpt) Number of workers for EC2 API service. The default will be equal to"
+" the number of CPUs available."
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml8(caption)
-msgid "Description of configuration options for dns"
+#: ./doc/common/tables/nova-ec2.xml66(td)
+#: ./doc/common/tables/keystone-ec2.xml38(td)
+msgid "keystone_ec2_url = http://localhost:5000/v2.0/ec2tokens"
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml22(td)
-msgid "dns_account_id ="
-msgstr "dns_account_id ="
-
-#: ./doc/common/tables/trove-dns.xml26(td)
-msgid "dns_auth_url ="
-msgstr "dns_auth_url ="
-
-#: ./doc/common/tables/trove-dns.xml30(td)
-msgid "dns_domain_id ="
-msgstr "dns_domain_id ="
-
-#: ./doc/common/tables/trove-dns.xml34(td)
-msgid "dns_domain_name ="
-msgstr "dns_domain_name ="
-
-#: ./doc/common/tables/trove-dns.xml38(td)
-msgid "dns_driver = trove.dns.driver.DnsDriver"
-msgstr "dns_driver = trove.dns.driver.DnsDriver"
-
-#: ./doc/common/tables/trove-dns.xml42(td)
-msgid "dns_endpoint_url = 0.0.0.0"
-msgstr "dns_endpoint_url = 0.0.0.0"
-
-#: ./doc/common/tables/trove-dns.xml46(td)
-msgid "dns_hostname ="
-msgstr "dns_hostname ="
-
-#: ./doc/common/tables/trove-dns.xml50(td)
-msgid "dns_instance_entry_factory = trove.dns.driver.DnsInstanceEntryFactory"
-msgstr "dns_instance_entry_factory = trove.dns.driver.DnsInstanceEntryFactory"
-
-#: ./doc/common/tables/trove-dns.xml54(td)
-msgid "dns_management_base_url ="
-msgstr "dns_management_base_url ="
-
-#: ./doc/common/tables/trove-dns.xml58(td)
-msgid "dns_passkey ="
-msgstr "dns_passkey ="
-
-#: ./doc/common/tables/trove-dns.xml62(td)
-msgid "dns_region ="
-msgstr "dns_region ="
-
-#: ./doc/common/tables/trove-dns.xml66(td)
-msgid "dns_service_type ="
-msgstr "dns_service_type ="
-
-#: ./doc/common/tables/trove-dns.xml70(td)
-msgid "dns_time_out = 120"
-msgstr "dns_time_out = 120"
-
-#: ./doc/common/tables/trove-dns.xml74(td)
-msgid "dns_ttl = 300"
-msgstr "dns_ttl = 300"
-
-#: ./doc/common/tables/trove-dns.xml78(td)
-msgid "dns_username ="
-msgstr "dns_username ="
-
-#: ./doc/common/tables/trove-dns.xml82(td)
-msgid "trove_dns_support = False"
-msgstr "trove_dns_support = False"
-
-#: ./doc/common/tables/neutron-db.xml22(td)
-msgid "sqlite_db ="
+#: ./doc/common/tables/nova-ec2.xml67(td)
+#: ./doc/common/tables/keystone-ec2.xml39(td)
+msgid "(StrOpt) URL to get token from ec2 request."
 msgstr ""
 
-#: ./doc/common/tables/neutron-db.xml37(td)
-msgid "connection = sqlite://"
+#: ./doc/common/tables/nova-ec2.xml70(td)
+msgid "lockout_attempts = 5"
 msgstr ""
 
-#: ./doc/common/tables/neutron-db.xml69(td)
-msgid "max_overflow = 20"
+#: ./doc/common/tables/nova-ec2.xml71(td)
+msgid "(IntOpt) Number of failed auths before lockout."
+msgstr "(IntOpt) Nombre d’échecs d’authentification avant blocage."
+
+#: ./doc/common/tables/nova-ec2.xml74(td)
+msgid "lockout_minutes = 15"
 msgstr ""
 
-#: ./doc/common/tables/neutron-db.xml73(td)
-msgid "max_pool_size = 10"
+#: ./doc/common/tables/nova-ec2.xml75(td)
+msgid "(IntOpt) Number of minutes to lockout if triggered."
+msgstr "(IntOpt) Nombre de minutes de blocage si déclenché."
+
+#: ./doc/common/tables/nova-ec2.xml78(td)
+msgid "lockout_window = 15"
 msgstr ""
 
-#: ./doc/common/tables/neutron-db.xml85(td)
-msgid "pool_timeout = 10"
+#: ./doc/common/tables/nova-ec2.xml79(td)
+msgid "(IntOpt) Number of minutes for lockout window."
+msgstr "(IntOpt) Nombre de minutes pour fenêtre de blocage."
+
+#: ./doc/common/tables/nova-ec2.xml82(td)
+msgid "region_list ="
+msgstr ""
+
+#: ./doc/common/tables/nova-ec2.xml83(td)
+msgid "(ListOpt) List of region=fqdn pairs separated by commas"
+msgstr ""
+
+#: ./doc/common/tables/keystone-credential.xml8(caption)
+msgid "Description of configuration options for credential"
+msgstr ""
+
+#: ./doc/common/tables/keystone-credential.xml19(th)
+msgid "[credential]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-credential.xml22(td)
+msgid "driver = keystone.credential.backends.sql.Credential"
+msgstr ""
+
+#: ./doc/common/tables/cinder-block-device.xml8(caption)
+msgid "Description of configuration options for block-device"
+msgstr ""
+
+#: ./doc/common/tables/cinder-block-device.xml22(td)
+msgid "available_devices ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-block-device.xml23(td)
+msgid "(ListOpt) List of all available devices"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml22(td)
+msgid "meta_flavor_driver_mappings = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml23(td)
+msgid "(StrOpt) Mapping between flavor and LinuxInterfaceDriver"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml26(td)
+msgid "metadata_backlog = 128"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml27(td)
+msgid ""
+"(IntOpt) Number of backlog requests to configure the metadata server socket "
+"with"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml30(td)
+msgid "metadata_port = 9697"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml31(td)
+msgid "(IntOpt) TCP Port used by Neutron metadata namespace proxy."
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml34(td)
+msgid "metadata_proxy_shared_secret ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml38(td)
+msgid "metadata_proxy_socket = $state_path/metadata_proxy"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml39(td)
+msgid "(StrOpt) Location of Metadata Proxy UNIX domain socket"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml42(td)
+msgid "metadata_workers = 0"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml43(td)
+msgid "(IntOpt) Number of separate worker processes for metadata server"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml46(td)
+msgid "nova_metadata_ip = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml47(td)
+msgid "(StrOpt) IP address used by Nova metadata server."
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml50(td)
+msgid "nova_metadata_port = 8775"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml51(td)
+msgid "(IntOpt) TCP Port used by Nova metadata server."
+msgstr ""
+
+#: ./doc/common/tables/nova-fping.xml8(caption)
+msgid "Description of configuration options for fping"
+msgstr ""
+
+#: ./doc/common/tables/nova-fping.xml22(td)
+msgid "fping_path = /usr/sbin/fping"
+msgstr ""
+
+#: ./doc/common/tables/nova-fping.xml23(td)
+msgid "(StrOpt) Full path to fping."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml7(literal)
+msgid "[filter:staticweb]"
+msgstr "[filter:staticweb]"
+
+#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml18(td)
+msgid "use = egg:swift#staticweb"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-replicator.xml7(literal)
+msgid "[container-replicator]"
+msgstr "[container-replicator]"
+
+#: ./doc/common/tables/swift-container-server-container-replicator.xml18(td)
+msgid "log_name = container-replicator"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ncs.xml8(caption)
+msgid "Description of configuration options for ml2_ncs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ncs.xml19(th)
+msgid "[ml2_ncs]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ncs.xml23(td)
+#: ./doc/common/tables/neutron-ml2_odl.xml23(td)
+msgid "(StrOpt) HTTP password for authentication"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ncs.xml26(td)
+#: ./doc/common/tables/neutron-ml2_odl.xml30(td)
+msgid "timeout = 10"
+msgstr "timeout = 10"
+
+#: ./doc/common/tables/neutron-ml2_ncs.xml27(td)
+#: ./doc/common/tables/neutron-ml2_odl.xml31(td)
+msgid "(IntOpt) HTTP timeout in seconds."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ncs.xml31(td)
+msgid "(StrOpt) HTTP URL of Tail-f NCS REST interface."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ncs.xml34(td)
+#: ./doc/common/tables/neutron-ml2_odl.xml38(td)
+msgid "username = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ncs.xml35(td)
+#: ./doc/common/tables/neutron-ml2_odl.xml39(td)
+msgid "(StrOpt) HTTP username for authentication"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml8(caption)
+msgid "Description of configuration options for ml2_arista"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml19(th)
+msgid "[ml2_arista]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml22(td)
+msgid "eapi_host ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml23(td)
+msgid ""
+"(StrOpt) Arista EOS IP address. This is required field.If not set, all "
+"communications to Arista EOSwill fail"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml26(td)
+msgid "eapi_password ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml27(td)
+msgid ""
+"(StrOpt) Password for Arista EOS. This is required field.if not set, all "
+"communications to Arista EOSwill fail"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml30(td)
+msgid "eapi_username ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml31(td)
+msgid ""
+"(StrOpt) Username for Arista EOS. This is required field.if not set, all "
+"communications to Arista EOSwill fail"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml34(td)
+msgid "region_name = RegionOne"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml35(td)
+msgid ""
+"(StrOpt) Defines Region Name that is assigned to this OpenStackController. "
+"This is useful when multipleOpenStack/Neutron controllers are managing the "
+"sameArista HW clusters. Note that this name must match withthe region name "
+"registered (or known) to keystoneservice. Authentication with Keysotne is "
+"performed byEOS. This is optional. If not set, a value of\"RegionOne\" is "
+"assumed"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml38(td)
+msgid "sync_interval = 180"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml39(td)
+msgid ""
+"(IntOpt) Sync interval in seconds between Neutron plugin andEOS. This "
+"interval defines how often thesynchronization is performed. This is an "
+"optionalfield. If not set, a value of 180 seconds is assumed"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml42(td)
+msgid "use_fqdn = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml43(td)
+msgid ""
+"(BoolOpt) Defines if hostnames are sent to Arista EOS as "
+"FQDNs(\"node1.domain.com\") or as short names (\"node1\").This is optional. "
+"If not set, a value of \"True\"is assumed."
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml8(caption)
+msgid "Description of configuration options for trustedcomputing"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml19(th)
+msgid "[trusted_computing]"
+msgstr "[trusted_computing]"
+
+#: ./doc/common/tables/nova-trustedcomputing.xml22(td)
+msgid "attestation_api_url = /OpenAttestationWebServices/V1.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml23(td)
+msgid "(StrOpt) Attestation web API URL"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml26(td)
+msgid "attestation_auth_blob = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml27(td)
+msgid "(StrOpt) Attestation authorization blob - must change"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml30(td)
+msgid "attestation_auth_timeout = 60"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml31(td)
+msgid "(IntOpt) Attestation status cache valid period length"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml34(td)
+msgid "attestation_port = 8443"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml35(td)
+msgid "(StrOpt) Attestation server port"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml38(td)
+msgid "attestation_server = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml39(td)
+msgid "(StrOpt) Attestation server HTTP"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml42(td)
+msgid "attestation_server_ca_file = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml43(td)
+msgid "(StrOpt) Attestation server Cert file for Identity verification"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml7(literal)
+msgid "[filter:bulk]"
+msgstr "[filter:bulk]"
+
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml18(td)
+msgid "use = egg:swift#bulk"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml21(td)
+msgid "max_containers_per_extraction = 10000"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml24(td)
+msgid "max_failed_extractions = 1000"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml27(td)
+msgid "max_deletes_per_request = 10000"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml30(td)
+msgid "max_failed_deletes = 1000"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml33(td)
+msgid "yield_frequency = 10"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml36(td)
+msgid "delete_container_retry_count = 0"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml22(td)
+msgid "notify_nova_on_port_data_changes = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml23(td)
+msgid ""
+"(BoolOpt) Send notification to nova when port data (fixed_ips/floatingip) "
+"changes so nova can update its cache."
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml26(td)
+msgid "notify_nova_on_port_status_changes = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml27(td)
+msgid "(BoolOpt) Send notification to nova when port status changes"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml30(td)
+msgid "nova_admin_auth_url = http://localhost:5000/v2.0"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml31(td)
+msgid "(StrOpt) Authorization URL for connecting to nova in admin context"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml34(td)
+msgid "nova_admin_password = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml35(td)
+msgid "(StrOpt) Password for connection to nova in admin context"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml38(td)
+msgid "nova_admin_tenant_id = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml39(td)
+msgid "(StrOpt) The uuid of the admin nova tenant"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml42(td)
+msgid "nova_admin_username = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml43(td)
+msgid "(StrOpt) Username for connecting to nova in admin context"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml46(td)
+msgid "nova_region_name = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml47(td)
+msgid ""
+"(StrOpt) Name of nova region to use. Useful if keystone manages more than "
+"one region."
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml50(td)
+msgid "nova_url = http://127.0.0.1:8774"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml51(td)
+msgid "(StrOpt) URL for connection to nova"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml54(td)
+msgid "send_events_interval = 2"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml55(td)
+msgid ""
+"(IntOpt) Number of seconds between sending events to nova if there are any "
+"events to send."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml8(caption)
+msgid "Description of configuration options for imagecache"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml22(td)
+msgid "cleanup_scrubber = False"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml23(td)
+msgid ""
+"(BoolOpt) A boolean that determines if the scrubber should clean up the "
+"files it uses for taking data. Only one server in your deployment should be "
+"designated the cleanup host."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml26(td)
+msgid "cleanup_scrubber_time = 86400"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml27(td)
+msgid ""
+"(IntOpt) Items must have a modified time that is older than this value in "
+"order to be candidates for cleanup."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml30(td)
+msgid "delayed_delete = False"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml31(td)
+msgid "(BoolOpt) Turn on/off delayed delete."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml34(td)
+msgid "image_cache_dir = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml35(td)
+msgid "(StrOpt) Base directory that the Image Cache uses."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml38(td)
+msgid "image_cache_driver = sqlite"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml39(td)
+msgid "(StrOpt) The driver to use for image cache management."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml42(td)
+msgid "image_cache_max_size = 10737418240"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml43(td)
+msgid "(IntOpt) The maximum size in bytes that the cache can use."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml46(td)
+msgid "image_cache_sqlite_db = cache.db"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml47(td)
+msgid ""
+"(StrOpt) The path to the sqlite file database that will be used for image "
+"cache management."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml50(td)
+msgid "image_cache_stall_time = 86400"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml51(td)
+msgid ""
+"(IntOpt) The amount of time to let an image remain in the cache without "
+"being accessed."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml54(td)
+msgid "scrub_time = 0"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml55(td)
+msgid ""
+"(IntOpt) The amount of time in seconds to delay before performing a delete."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml58(td)
+msgid "scrubber_datadir = /var/lib/glance/scrubber"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml59(td)
+msgid ""
+"(StrOpt) Directory that the scrubber will use to track information about "
+"what to delete. Make sure this is set in glance-api.conf and glance-"
+"scrubber.conf."
 msgstr ""
 
 #: ./doc/common/tables/neutron-ml2_brocade.xml8(caption)
@@ -45508,6 +45526,91 @@ msgstr ""
 msgid "(StrOpt) The SSH username to use"
 msgstr ""
 
+#: ./doc/common/tables/swift-account-server-account-auditor.xml7(literal)
+msgid "[account-auditor]"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-auditor.xml18(td)
+msgid "log_name = account-auditor"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-auditor.xml39(td)
+msgid "accounts_per_second = 200"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-auditor.xml39(td)
+msgid ""
+"Maximum accounts audited per second. Should be tuned according to individual"
+" system specs. 0 is unlimited."
+msgstr ""
+
+#: ./doc/common/tables/cinder-nas.xml8(caption)
+msgid "Description of configuration options for nas"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nas.xml22(td)
+msgid "nas_ip ="
+msgstr "nas_ip ="
+
+#: ./doc/common/tables/cinder-nas.xml23(td)
+msgid "(StrOpt) IP address or Hostname of NAS system."
+msgstr ""
+
+#: ./doc/common/tables/cinder-nas.xml26(td)
+msgid "nas_login = admin"
+msgstr "nas_login = admin"
+
+#: ./doc/common/tables/cinder-nas.xml27(td)
+msgid "(StrOpt) User name to connect to NAS system."
+msgstr ""
+
+#: ./doc/common/tables/cinder-nas.xml30(td)
+msgid "nas_password ="
+msgstr "nas_password ="
+
+#: ./doc/common/tables/cinder-nas.xml31(td)
+msgid "(StrOpt) Password to connect to NAS system."
+msgstr ""
+
+#: ./doc/common/tables/cinder-nas.xml34(td)
+msgid "nas_private_key ="
+msgstr "nas_private_key ="
+
+#: ./doc/common/tables/cinder-nas.xml35(td)
+msgid "(StrOpt) Filename of private key to use for SSH authentication."
+msgstr ""
+
+#: ./doc/common/tables/cinder-nas.xml38(td)
+msgid "nas_ssh_port = 22"
+msgstr "nas_ssh_port = 22"
+
+#: ./doc/common/tables/cinder-nas.xml39(td)
+msgid "(IntOpt) SSH port to use to connect to NAS system."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml8(caption)
+msgid "Description of configuration options for netapp_cdot_nfs"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml26(td)
+msgid "netapp_copyoffload_tool_path = None"
+msgstr "netapp_copyoffload_tool_path = None"
+
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml27(td)
+msgid ""
+"(StrOpt) This option specifies the path of the NetApp copy offload tool "
+"binary. Ensure that the binary has execute permissions set which allow the "
+"effective user of the cinder-volume process to execute the file."
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_swift.xml8(caption)
+msgid "Description of configuration options for clients_swift"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_swift.xml19(th)
+msgid "[clients_swift]"
+msgstr "[clients_swift]"
+
 #: ./doc/common/tables/neutron-brocade.xml8(caption)
 msgid "Description of configuration options for brocade"
 msgstr ""
@@ -45540,299 +45643,6 @@ msgstr ""
 msgid "username ="
 msgstr ""
 
-#: ./doc/common/tables/keystone-database.xml74(td)
-#: ./doc/common/tables/glance-db.xml74(td)
-msgid "mysql_sql_mode = TRADITIONAL"
-msgstr ""
-
-#: ./doc/common/tables/keystone-database.xml75(td)
-#: ./doc/common/tables/glance-db.xml75(td)
-msgid ""
-"(StrOpt) The SQL mode to be used for MySQL sessions. This option, including "
-"the default, overrides any server-set SQL mode. To use whatever SQL mode is "
-"set by the server configuration, set this to no value. Example: "
-"mysql_sql_mode="
-msgstr ""
-
-#: ./doc/common/tables/keystone-database.xml86(td)
-msgid "sqlite_db = keystone.sqlite"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml18(td)
-msgid "pipeline = catch_errors cache proxy-server"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_neutron.xml8(caption)
-msgid "Description of configuration options for clients_neutron"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_neutron.xml19(th)
-msgid "[clients_neutron]"
-msgstr "[clients_neutron]"
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml8(caption)
-msgid "Description of configuration options for linuxbridge_agent"
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml19(th)
-msgid "[LINUX_BRIDGE]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml26(th)
-msgid "[VLANS]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml37(th)
-msgid "[VXLAN]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml40(td)
-msgid "enable_vxlan = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml41(td)
-msgid ""
-"(BoolOpt) Enable VXLAN on the agent. Can be enabled when agent is managed by"
-" ml2 plugin using linuxbridge mechanism driver"
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml45(td)
-msgid ""
-"(BoolOpt) Extension to use alongside ml2 plugin's l2population mechanism "
-"driver. It enables the plugin to populate VXLAN forwarding table."
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml49(td)
-msgid "(StrOpt) Local IP address of the VXLAN endpoints."
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml52(td)
-msgid "tos = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml53(td)
-msgid "(IntOpt) TOS for vxlan interface protocol packets."
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml56(td)
-msgid "ttl = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml57(td)
-msgid "(IntOpt) TTL for vxlan interface protocol packets."
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml60(td)
-msgid "vxlan_group = 224.0.0.1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml61(td)
-msgid "(StrOpt) Multicast group for vxlan interface."
-msgstr ""
-
-#: ./doc/common/tables/cinder-xiv.xml8(caption)
-msgid "Description of configuration options for xiv"
-msgstr ""
-
-#: ./doc/common/tables/cinder-xiv.xml22(td)
-msgid "xiv_chap = disabled"
-msgstr ""
-
-#: ./doc/common/tables/cinder-xiv.xml23(td)
-msgid ""
-"(StrOpt) CHAP authentication mode, effective only for iscsi "
-"(disabled|enabled)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-xiv.xml26(td)
-msgid "xiv_ds8k_connection_type = iscsi"
-msgstr ""
-
-#: ./doc/common/tables/cinder-xiv.xml27(td)
-msgid ""
-"(StrOpt) Connection type to the IBM Storage Array (fibre_channel|iscsi)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-xiv.xml30(td)
-msgid "xiv_ds8k_proxy = xiv_ds8k_openstack.nova_proxy.XIVDS8KNovaProxy"
-msgstr ""
-
-#: ./doc/common/tables/cinder-xiv.xml31(td)
-msgid "(StrOpt) Proxy driver that connects to the IBM Storage Array"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hds-hus.xml8(caption)
-msgid "Description of configuration options for hds-hus"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hds-hus.xml22(td)
-msgid "hds_cinder_config_file = /opt/hds/hus/cinder_hus_conf.xml"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hds-hus.xml23(td)
-msgid "(StrOpt) configuration file for HDS cinder plugin for HUS"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rabbitmq.xml35(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml55(td)
-msgid ""
-"(IntOpt) Maximum number of RabbitMQ connection retries. Default is 0 "
-"(infinite retry count)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rabbitmq.xml39(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml59(td)
-msgid "(StrOpt) The RabbitMQ password"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rabbitmq.xml47(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml67(td)
-msgid ""
-"(IntOpt) How long to backoff for between retries when connecting to RabbitMQ"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rabbitmq.xml51(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml71(td)
-msgid "(IntOpt) How frequently to retry connecting with RabbitMQ"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rabbitmq.xml55(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml75(td)
-msgid "(BoolOpt) Connect over SSL for RabbitMQ"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rabbitmq.xml59(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml79(td)
-msgid "(StrOpt) The RabbitMQ userid"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rabbitmq.xml63(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml83(td)
-msgid "(StrOpt) The RabbitMQ virtual host"
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml8(caption)
-msgid "Description of configuration options for kvs"
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml19(th)
-msgid "[kvs]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml22(td)
-msgid "backends ="
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml23(td)
-msgid ""
-"(ListOpt) Extra dogpile.cache backend modules to register with the "
-"dogpile.cache library."
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml26(td)
-msgid "config_prefix = keystone.kvs"
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml27(td)
-msgid ""
-"(StrOpt) Prefix for building the configuration dictionary for the KVS "
-"region. This should not need to be changed unless there is another "
-"dogpile.cache region with the same configuration name."
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml30(td)
-msgid "default_lock_timeout = 5"
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml31(td)
-msgid "(IntOpt) Default lock timeout for distributed locking."
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml34(td)
-msgid "enable_key_mangler = True"
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml35(td)
-msgid ""
-"(BoolOpt) Toggle to disable using a key-mangling function to ensure fixed "
-"length keys. This is toggle-able for debugging purposes, it is highly "
-"recommended to always leave this set to True."
-msgstr ""
-
-#: ./doc/common/tables/keystone-policy.xml30(th)
-msgid "[policy]"
-msgstr "[policy]"
-
-#: ./doc/common/tables/keystone-policy.xml33(td)
-msgid "driver = keystone.policy.backends.sql.Policy"
-msgstr ""
-
-#: ./doc/common/tables/keystone-policy.xml34(td)
-msgid "(StrOpt) Keystone Policy backend driver."
-msgstr ""
-
-#: ./doc/common/tables/keystone-policy.xml38(td)
-msgid ""
-"(IntOpt) Maximum number of entities that will be returned in a policy "
-"collection."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml7(literal)
-msgid "[filter:container-quotas]"
-msgstr "[filter:container-quotas]"
-
-#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml18(td)
-msgid "use = egg:swift#container_quotas"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-hash.xml7(literal)
-msgid "[swift-hash]"
-msgstr "[swift-hash]"
-
-#: ./doc/common/tables/swift-swift-swift-hash.xml18(td)
-msgid "swift_hash_path_suffix = changeme"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-hash.xml18(td)
-msgid ""
-"A suffix used by hash_path to offer a bit more security when generating "
-"hashes for paths. It simply appends this value to all paths; if someone "
-"knows this suffix, it's easier for them to guess the hash a path will end up"
-" with. New installations are advised to set this parameter to a random "
-"secret, which would not be disclosed ouside the organization. The same "
-"secret needs to be used by all swift servers of the same cluster. Existing "
-"installations should set this parameter to an empty string."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-hash.xml29(td)
-msgid "swift_hash_path_prefix = changeme"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-hash.xml29(td)
-msgid ""
-"A prefix used by hash_path to offer a bit more security when generating "
-"hashes for paths. It simply appends this value to all paths; if someone "
-"knows this suffix, it's easier for them to guess the hash a path will end up"
-" with. New installations are advised to set this parameter to a random "
-"secret, which would not be disclosed ouside the organization. The same "
-"secret needs to be used by all swift servers of the same cluster. Existing "
-"installations should set this parameter to an empty string."
-msgstr ""
-
-#: ./doc/common/tables/cinder-auth.xml23(td)
-msgid ""
-"(StrOpt) The strategy to use for auth. Supports noauth, keystone, and "
-"deprecated."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml7(literal)
-msgid "[filter:formpost]"
-msgstr "[filter:formpost]"
-
-#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml18(td)
-msgid "use = egg:swift#formpost"
-msgstr ""
-
 #: ./doc/common/tables/neutron-ml2_odl.xml8(caption)
 msgid "Description of configuration options for ml2_odl"
 msgstr ""
@@ -45841,11 +45651,6 @@ msgstr ""
 msgid "[ml2_odl]"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_odl.xml23(td)
-#: ./doc/common/tables/neutron-ml2_ncs.xml23(td)
-msgid "(StrOpt) HTTP password for authentication"
-msgstr ""
-
 #: ./doc/common/tables/neutron-ml2_odl.xml26(td)
 msgid "session_timeout = 30"
 msgstr ""
@@ -45854,196 +45659,464 @@ msgstr ""
 msgid "(IntOpt) Tomcat session timeout in minutes."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_odl.xml30(td)
-#: ./doc/common/tables/neutron-ml2_ncs.xml26(td)
-msgid "timeout = 10"
-msgstr "timeout = 10"
-
-#: ./doc/common/tables/neutron-ml2_odl.xml31(td)
-#: ./doc/common/tables/neutron-ml2_ncs.xml27(td)
-msgid "(IntOpt) HTTP timeout in seconds."
-msgstr ""
-
 #: ./doc/common/tables/neutron-ml2_odl.xml35(td)
 msgid "(StrOpt) HTTP URL of OpenDaylight REST interface."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_odl.xml38(td)
-#: ./doc/common/tables/neutron-ml2_ncs.xml34(td)
-msgid "username = None"
+#: ./doc/common/tables/swift-object-server-filter-recon.xml24(td)
+msgid "recon_lock_path = /var/lock"
+msgstr "recon_lock_path = /var/lock"
+
+#: ./doc/common/tables/cinder-connection.xml8(caption)
+msgid "Description of configuration options for connection"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_odl.xml39(td)
-#: ./doc/common/tables/neutron-ml2_ncs.xml35(td)
-msgid "(StrOpt) HTTP username for authentication"
+#: ./doc/common/tables/cinder-connection.xml22(td)
+msgid "connection = sqlite:///$state_path/$sqlite_db"
 msgstr ""
 
-#: ./doc/common/tables/heat-quota.xml22(td)
-msgid "max_events_per_stack = 1000"
-msgstr "max_events_per_stack = 1000"
+#: ./doc/common/tables/heat-rpc.xml26(td)
+msgid "engine_life_check_timeout = 2"
+msgstr "engine_life_check_timeout = 2"
 
-#: ./doc/common/tables/heat-quota.xml23(td)
+#: ./doc/common/tables/heat-rpc.xml27(td)
 msgid ""
-"(IntOpt) Maximum events that will be available per stack. Older events will "
-"be deleted when this is reached. Set to 0 for unlimited events per stack."
+"(IntOpt) RPC timeout for the engine liveness check that is used for stack "
+"locking."
 msgstr ""
 
-#: ./doc/common/tables/heat-quota.xml26(td)
-msgid "max_nested_stack_depth = 3"
-msgstr "max_nested_stack_depth = 3"
+#: ./doc/common/tables/heat-rpc.xml38(td)
+msgid "rpc_backend = heat.openstack.common.rpc.impl_kombu"
+msgstr "rpc_backend = heat.openstack.common.rpc.impl_kombu"
 
-#: ./doc/common/tables/heat-quota.xml27(td)
-msgid "(IntOpt) Maximum depth allowed when using nested stacks."
+#: ./doc/common/tables/trove-taskmanager.xml8(caption)
+msgid "Description of configuration options for taskmanager"
 msgstr ""
 
-#: ./doc/common/tables/heat-quota.xml30(td)
-msgid "max_resources_per_stack = 1000"
-msgstr "max_resources_per_stack = 1000"
-
-#: ./doc/common/tables/heat-quota.xml31(td)
-msgid "(IntOpt) Maximum resources allowed per top-level stack."
+#: ./doc/common/tables/trove-taskmanager.xml22(td)
+msgid "cloudinit_location = /etc/trove/cloudinit"
 msgstr ""
 
-#: ./doc/common/tables/heat-quota.xml34(td)
-msgid "max_stacks_per_tenant = 100"
-msgstr "max_stacks_per_tenant = 100"
+#: ./doc/common/tables/trove-taskmanager.xml23(td)
+msgid "(StrOpt) Path to folder with cloudinit scripts."
+msgstr ""
 
-#: ./doc/common/tables/heat-quota.xml35(td)
+#: ./doc/common/tables/trove-taskmanager.xml26(td)
+msgid "datastore_manager = None"
+msgstr ""
+
+#: ./doc/common/tables/trove-taskmanager.xml27(td)
 msgid ""
-"(IntOpt) Maximum number of stacks any one tenant may have active at one "
-"time."
+"(StrOpt) Manager class in guestagent, setup by taskmanager on instance "
+"provision."
 msgstr ""
 
-#: ./doc/common/tables/heat-quota.xml38(td)
-msgid "max_template_size = 524288"
-msgstr "max_template_size = 524288"
-
-#: ./doc/common/tables/heat-quota.xml39(td)
-msgid "(IntOpt) Maximum raw byte size of any template."
+#: ./doc/common/tables/trove-taskmanager.xml30(td)
+msgid "datastore_registry_ext = {}"
 msgstr ""
 
-#: ./doc/common/tables/nova-spice.xml8(caption)
-msgid "Description of configuration options for spice"
-msgstr ""
-
-#: ./doc/common/tables/nova-spice.xml19(th)
-msgid "[spice]"
-msgstr ""
-
-#: ./doc/common/tables/nova-spice.xml22(td)
-msgid "agent_enabled = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-spice.xml23(td)
-msgid "(BoolOpt) Enable spice guest agent support"
-msgstr ""
-
-#: ./doc/common/tables/nova-spice.xml27(td)
-msgid "(BoolOpt) Enable spice related features"
-msgstr ""
-
-#: ./doc/common/tables/nova-spice.xml30(td)
-msgid "html5proxy_base_url = http://127.0.0.1:6082/spice_auto.html"
-msgstr ""
-
-#: ./doc/common/tables/nova-spice.xml31(td)
+#: ./doc/common/tables/trove-taskmanager.xml31(td)
 msgid ""
-"(StrOpt) Location of spice HTML5 console proxy, in the form "
-"\"http://127.0.0.1:6082/spice_auto.html\""
+"(DictOpt) Extension for default datastore managers. Allows to use custom "
+"managers for each of datastore supported in trove."
 msgstr ""
 
-#: ./doc/common/tables/nova-spice.xml34(td)
-msgid "keymap = en-us"
+#: ./doc/common/tables/trove-taskmanager.xml34(td)
+msgid "exists_notification_ticks = 360"
 msgstr ""
 
-#: ./doc/common/tables/nova-spice.xml35(td)
-msgid "(StrOpt) Keymap for spice"
-msgstr ""
-
-#: ./doc/common/tables/nova-spice.xml38(td)
-msgid "server_listen = 127.0.0.1"
-msgstr ""
-
-#: ./doc/common/tables/nova-spice.xml39(td)
-msgid "(StrOpt) IP address on which instance spice server should listen"
-msgstr ""
-
-#: ./doc/common/tables/nova-spice.xml42(td)
-msgid "server_proxyclient_address = 127.0.0.1"
-msgstr ""
-
-#: ./doc/common/tables/nova-spice.xml43(td)
+#: ./doc/common/tables/trove-taskmanager.xml35(td)
 msgid ""
-"(StrOpt) The address to which proxy clients (like nova-spicehtml5proxy) "
-"should connect"
+"(IntOpt) Number of report_intervals to wait between pushing events (see "
+"report_interval)."
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml8(caption)
-msgid "Description of configuration options for zoning_fabric"
+#: ./doc/common/tables/trove-taskmanager.xml38(td)
+msgid "exists_notification_transformer = None"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml19(th)
-msgid "[BRCD_FABRIC_EXAMPLE]"
-msgstr "[BRCD_FABRIC_EXAMPLE]"
-
-#: ./doc/common/tables/cinder-zoning_fabric.xml22(td)
-msgid "fc_fabric_address ="
-msgstr "fc_fabric_address ="
-
-#: ./doc/common/tables/cinder-zoning_fabric.xml23(td)
-msgid "(StrOpt) Management IP of fabric"
+#: ./doc/common/tables/trove-taskmanager.xml39(td)
+msgid "(StrOpt) Transformer for exists notifications."
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml26(td)
-msgid "fc_fabric_password ="
-msgstr "fc_fabric_password ="
-
-#: ./doc/common/tables/cinder-zoning_fabric.xml27(td)
-msgid "(StrOpt) Password for user"
+#: ./doc/common/tables/trove-taskmanager.xml42(td)
+msgid "reboot_time_out = 120"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml30(td)
-msgid "fc_fabric_port = 22"
-msgstr "fc_fabric_port = 22"
-
-#: ./doc/common/tables/cinder-zoning_fabric.xml31(td)
-msgid "(IntOpt) Connecting port"
+#: ./doc/common/tables/trove-taskmanager.xml46(td)
+msgid "resize_time_out = 600"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml34(td)
-msgid "fc_fabric_user ="
-msgstr "fc_fabric_user ="
-
-#: ./doc/common/tables/cinder-zoning_fabric.xml35(td)
-msgid "(StrOpt) Fabric user ID"
+#: ./doc/common/tables/trove-taskmanager.xml50(td)
+msgid "revert_time_out = 600"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml38(td)
-msgid "principal_switch_wwn = None"
-msgstr "principal_switch_wwn = None"
-
-#: ./doc/common/tables/cinder-zoning_fabric.xml39(td)
-msgid "(StrOpt) Principal switch WWN of the fabric"
+#: ./doc/common/tables/trove-taskmanager.xml54(td)
+msgid "server_delete_time_out = 60"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml42(td)
-msgid "zone_activate = True"
-msgstr "zone_activate = True"
-
-#: ./doc/common/tables/cinder-zoning_fabric.xml43(td)
-msgid "(BoolOpt) overridden zoning activation state"
+#: ./doc/common/tables/trove-taskmanager.xml58(td)
+msgid "state_change_wait_time = 180"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml46(td)
-msgid "zone_name_prefix = None"
-msgstr "zone_name_prefix = None"
-
-#: ./doc/common/tables/cinder-zoning_fabric.xml47(td)
-msgid "(StrOpt) overridden zone name prefix"
+#: ./doc/common/tables/trove-taskmanager.xml62(td)
+msgid "update_status_on_fail = False"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml51(td)
-msgid "(StrOpt) overridden zoning policy"
+#: ./doc/common/tables/trove-taskmanager.xml63(td)
+msgid ""
+"(BoolOpt) If instance fails to become active, taskmanager updates statuses, "
+"service status = FAILED_TIMEOUT_GUESTAGENT, instance task status = "
+"BUILDING_ERROR_TIMEOUT_GA."
+msgstr ""
+
+#: ./doc/common/tables/trove-taskmanager.xml70(td)
+msgid "use_heat = False"
+msgstr ""
+
+#: ./doc/common/tables/trove-taskmanager.xml74(td)
+msgid "use_nova_server_volume = False"
+msgstr ""
+
+#: ./doc/common/tables/trove-taskmanager.xml78(td)
+msgid "verify_swift_checksum_on_restore = True"
+msgstr ""
+
+#: ./doc/common/tables/trove-taskmanager.xml79(td)
+msgid ""
+"(BoolOpt) Enable verification of swift checksum before starting restore; "
+"makes sure the checksum of original backup matches checksum of the swift "
+"backup file."
+msgstr ""
+
+#: ./doc/common/tables/heat-cloudwatch_api.xml8(caption)
+msgid "Description of configuration options for cloudwatch_api"
+msgstr ""
+
+#: ./doc/common/tables/heat-cloudwatch_api.xml26(th)
+msgid "[heat_api_cloudwatch]"
+msgstr "[heat_api_cloudwatch]"
+
+#: ./doc/common/tables/heat-cloudwatch_api.xml37(td)
+msgid "bind_port = 8003"
+msgstr "bind_port = 8003"
+
+#: ./doc/common/tables/heat-cloudwatch_api.xml50(td)
+msgid ""
+"(IntOpt) Maximum line size of message headers to be accepted. "
+"max_header_line may need to be increased when using large tokens (typically "
+"those generated by the Keystone v3 API with big service catalogs.)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml8(caption)
+msgid "Description of configuration options for images"
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml23(td)
+msgid ""
+"(ListOpt) A list of url schemes that can be downloaded directly via the "
+"direct_url. Currently supported schemes: [file]."
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml31(td)
+msgid ""
+"(ListOpt) A list of the glance api servers available to cinder "
+"([hostname|ip]:port)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml34(td)
+msgid "glance_api_ssl_compression = False"
+msgstr "glance_api_ssl_compression = False"
+
+#: ./doc/common/tables/cinder-images.xml35(td)
+msgid ""
+"(BoolOpt) Whether to attempt to negotiate SSL layer compression when using "
+"SSL (https) requests. Set to False to disable SSL layer compression. In some"
+" cases disabling this may improve data throughput, eg when high network "
+"bandwidth is available and you are using already compressed image formats "
+"such as qcow2 ."
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml38(td)
+msgid "glance_api_version = 1"
+msgstr "glance_api_version = 1"
+
+#: ./doc/common/tables/cinder-images.xml39(td)
+msgid "(IntOpt) Version of the glance api to use"
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml43(td)
+msgid "(StrOpt) default glance hostname or ip"
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml47(td)
+msgid "(IntOpt) Number retries when downloading an image from glance"
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml51(td)
+msgid "(IntOpt) default glance port"
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml54(td)
+msgid "glance_request_timeout = None"
+msgstr "glance_request_timeout = None"
+
+#: ./doc/common/tables/cinder-images.xml55(td)
+msgid ""
+"(IntOpt) http/https timeout value for glance operations. If no value (None) "
+"is supplied here, the glanceclient default value is used."
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml58(td)
+msgid "image_conversion_dir = $state_path/conversion"
+msgstr "image_conversion_dir = $state_path/conversion"
+
+#: ./doc/common/tables/cinder-images.xml59(td)
+msgid "(StrOpt) Directory used for temporary storage during image conversion"
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml70(td)
+msgid "use_multipath_for_image_xfer = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml71(td)
+msgid ""
+"(BoolOpt) Do we attach/detach volumes in cinder using multipath for volume "
+"to image and image to volume transfers?"
+msgstr ""
+
+#: ./doc/common/tables/cinder-huawei.xml8(caption)
+msgid "Description of configuration options for huawei"
+msgstr ""
+
+#: ./doc/common/tables/cinder-huawei.xml22(td)
+msgid "cinder_huawei_conf_file = /etc/cinder/cinder_huawei_conf.xml"
+msgstr ""
+
+#: ./doc/common/tables/cinder-huawei.xml23(td)
+msgid "(StrOpt) config data for cinder huawei plugin"
+msgstr ""
+
+#: ./doc/common/tables/nova-console.xml8(caption)
+msgid "Description of configuration options for console"
+msgstr "Description des options de configuration pour la console"
+
+#: ./doc/common/tables/nova-console.xml22(td)
+msgid "console_public_hostname = oslo"
+msgstr "console_public_hostname = oslo"
+
+#: ./doc/common/tables/nova-console.xml23(td)
+msgid "(StrOpt) Publicly visible name for this console host"
+msgstr ""
+
+#: ./doc/common/tables/nova-console.xml26(td)
+msgid "console_token_ttl = 600"
+msgstr "console_token_ttl = 600"
+
+#: ./doc/common/tables/nova-console.xml27(td)
+msgid "(IntOpt) How many seconds before deleting tokens"
+msgstr ""
+
+#: ./doc/common/tables/nova-console.xml30(td)
+msgid "consoleauth_manager = nova.consoleauth.manager.ConsoleAuthManager"
+msgstr "consoleauth_manager = nova.consoleauth.manager.ConsoleAuthManager"
+
+#: ./doc/common/tables/nova-console.xml31(td)
+msgid "(StrOpt) Manager for console auth"
+msgstr ""
+
+#: ./doc/common/tables/neutron-fwaas.xml8(caption)
+msgid "Description of configuration options for fwaas"
+msgstr ""
+
+#: ./doc/common/tables/neutron-fwaas.xml19(th)
+#: ./doc/common/tables/neutron-nec.xml73(th)
+msgid "[fwaas]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-fwaas.xml23(td)
+msgid "(BoolOpt) Enable FWaaS"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_nfs.xml8(caption)
+msgid "Description of configuration options for nexenta_nfs"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_nfs.xml22(td)
+msgid "nexenta_mount_point_base = $state_path/mnt"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_nfs.xml23(td)
+msgid "(StrOpt) Base dir containing mount points for nfs shares"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_nfs.xml26(td)
+msgid "nexenta_nms_cache_volroot = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_nfs.xml27(td)
+msgid ""
+"(BoolOpt) If set True cache NexentaStor appliance volroot option value."
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_nfs.xml30(td)
+msgid "nexenta_shares_config = /etc/cinder/nfs_shares"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_nfs.xml34(td)
+msgid "nexenta_volume_compression = on"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_nfs.xml35(td)
+msgid "(StrOpt) Default compression value for new ZFS folders."
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml22(td)
+msgid "bandwidth_poll_interval = 600"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml23(td)
+msgid ""
+"(IntOpt) Interval to pull network bandwidth usage info. Not supported on all"
+" hypervisors. Set to 0 to disable."
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml26(td)
+msgid "enable_network_quota = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml27(td)
+msgid "(BoolOpt) Enables or disables quota checking for tenant networks"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml30(td)
+msgid "quota_cores = 20"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml31(td)
+msgid "(IntOpt) Number of instance cores allowed per project"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml34(td)
+msgid "quota_driver = nova.quota.DbQuotaDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml38(td)
+msgid "quota_fixed_ips = -1"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml39(td)
+msgid ""
+"(IntOpt) Number of fixed IPs allowed per project (this should be at least "
+"the number of instances allowed)"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml42(td)
+msgid "quota_floating_ips = 10"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml43(td)
+msgid "(IntOpt) Number of floating IPs allowed per project"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml46(td)
+msgid "quota_injected_file_content_bytes = 10240"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml47(td)
+msgid "(IntOpt) Number of bytes allowed per injected file"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml50(td)
+msgid "quota_injected_file_path_bytes = 255"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml51(td)
+msgid "(IntOpt) Number of bytes allowed per injected file path"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml54(td)
+msgid "quota_injected_files = 5"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml55(td)
+msgid "(IntOpt) Number of injected files allowed"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml58(td)
+msgid "quota_instances = 10"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml59(td)
+msgid "(IntOpt) Number of instances allowed per project"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml62(td)
+msgid "quota_key_pairs = 100"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml63(td)
+msgid "(IntOpt) Number of key pairs per user"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml66(td)
+msgid "quota_metadata_items = 128"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml67(td)
+msgid "(IntOpt) Number of metadata items allowed per instance"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml70(td)
+msgid "quota_ram = 51200"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml71(td)
+msgid "(IntOpt) Megabytes of instance RAM allowed per project"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml74(td)
+msgid "quota_security_group_rules = 20"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml75(td)
+msgid "(IntOpt) Number of security rules per security group"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml78(td)
+msgid "quota_security_groups = 10"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml79(td)
+msgid "(IntOpt) Number of security groups per project"
+msgstr ""
+
+#: ./doc/common/tables/keystone-stats.xml8(caption)
+msgid "Description of configuration options for stats"
+msgstr ""
+
+#: ./doc/common/tables/keystone-stats.xml19(th)
+msgid "[stats]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-stats.xml22(td)
+msgid "driver = keystone.contrib.stats.backends.kvs.Stats"
+msgstr ""
+
+#: ./doc/common/tables/keystone-stats.xml23(td)
+msgid "(StrOpt) Keystone stats backend driver."
+msgstr ""
+
+#: ./doc/common/tables/heat-crypt.xml8(caption)
+msgid "Description of configuration options for crypt"
+msgstr ""
+
+#: ./doc/common/tables/heat-crypt.xml22(td)
+msgid "auth_encryption_key = notgood but just long enough i think"
+msgstr "auth_encryption_key = notgood but just long enough i think"
+
+#: ./doc/common/tables/heat-crypt.xml23(td)
+msgid "(StrOpt) Encryption key used for authentication info in database."
 msgstr ""
 
 #: ./doc/common/tables/neutron-midonet.xml8(caption)
@@ -46106,1469 +46179,207 @@ msgstr ""
 msgid "(StrOpt) MidoNet admin username."
 msgstr ""
 
-#: ./doc/common/tables/neutron-nvsd.xml8(caption)
-msgid "Description of configuration options for nvsd"
+#: ./doc/common/tables/cinder-coraid.xml8(caption)
+msgid "Description of configuration options for coraid"
 msgstr ""
 
-#: ./doc/common/tables/neutron-nvsd.xml23(td)
-msgid "(StrOpt) integration bridge"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nvsd.xml26(th)
-msgid "[nvsd]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nvsd.xml29(td)
-msgid "nvsd_ip = 127.0.0.1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nvsd.xml30(td)
-msgid "(StrOpt) NVSD Controller IP address"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nvsd.xml33(td)
-msgid "nvsd_passwd = oc123"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nvsd.xml34(td)
-msgid "(StrOpt) NVSD Controller password"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nvsd.xml37(td)
-msgid "nvsd_port = 8082"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nvsd.xml38(td)
-msgid "(IntOpt) NVSD Controller Port number"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nvsd.xml41(td)
-msgid "nvsd_retries = 0"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nvsd.xml42(td)
-msgid "(IntOpt) Number of login retries to NVSD controller"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nvsd.xml45(td)
-msgid "nvsd_user = ocplugin"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nvsd.xml46(td)
-msgid "(StrOpt) NVSD Controller username"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nvsd.xml49(td)
-msgid "request_timeout = 30"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nvsd.xml50(td)
-msgid "(IntOpt) NVSD controller REST API request timeout in seconds"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml8(caption)
-msgid "Description of configuration options for embrane_lb"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml19(th)
-msgid "[heleoslb]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml26(td)
-msgid "admin_username = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml27(td)
-#: ./doc/common/tables/neutron-embrane.xml23(td)
-msgid "(StrOpt) ESM admin username."
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml30(td)
-msgid "async_requests = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml31(td)
-#: ./doc/common/tables/neutron-embrane.xml27(td)
-msgid "(BoolOpt) Define if the requests have run asynchronously or not"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml34(td)
-#: ./doc/common/tables/neutron-embrane.xml30(td)
-msgid "dummy_utif_id = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml35(td)
-msgid "(StrOpt) Dummy user traffic Security Zone id for LBs"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml38(td)
-#: ./doc/common/tables/neutron-embrane.xml34(td)
-msgid "esm_mgmt = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml39(td)
-#: ./doc/common/tables/neutron-embrane.xml35(td)
-msgid "(StrOpt) ESM management root address"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml42(td)
-#: ./doc/common/tables/neutron-embrane.xml38(td)
-msgid "inband_id = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml43(td)
-msgid "(StrOpt) In band Security Zone id for LBs"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml46(td)
-msgid "lb_flavor = small"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml47(td)
-msgid "(StrOpt) choose LB image flavor to use, accepted values: small, medium"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml50(td)
-msgid "lb_image = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml51(td)
-msgid "(StrOpt) Load Balancer image id (Embrane LB)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml54(td)
-#: ./doc/common/tables/neutron-embrane.xml42(td)
-msgid "mgmt_id = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml55(td)
-msgid "(StrOpt) Management Security Zone id for LBs"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml58(td)
-#: ./doc/common/tables/neutron-embrane.xml46(td)
-msgid "oob_id = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml59(td)
-msgid "(StrOpt) Out of band Security Zone id for LBs"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml62(td)
-#: ./doc/common/tables/neutron-vmware.xml199(td)
-msgid "resource_pool_id = None"
-msgstr "resource_pool_id = None"
-
-#: ./doc/common/tables/neutron-embrane_lb.xml63(td)
-#: ./doc/common/tables/neutron-embrane.xml51(td)
-msgid "(StrOpt) Shared resource pool id"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml66(td)
-msgid "sync_interval = 60"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml67(td)
-msgid "(IntOpt) resource synchronization interval in seconds"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml8(caption)
-msgid "Description of configuration options for storwize"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml22(td)
-msgid "storwize_svc_connection_protocol = iSCSI"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml23(td)
-msgid "(StrOpt) Connection protocol (iSCSI/FC)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml26(td)
-msgid "storwize_svc_flashcopy_timeout = 120"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml27(td)
-msgid ""
-"(IntOpt) Maximum number of seconds to wait for FlashCopy to be prepared. "
-"Maximum value is 600 seconds (10 minutes)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml30(td)
-msgid "storwize_svc_iscsi_chap_enabled = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml31(td)
-msgid ""
-"(BoolOpt) Configure CHAP authentication for iSCSI connections (Default: "
-"Enabled)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml34(td)
-msgid "storwize_svc_multihostmap_enabled = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml35(td)
-msgid "(BoolOpt) Allows vdisk to multi host mapping"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml38(td)
-msgid "storwize_svc_multipath_enabled = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml39(td)
-msgid ""
-"(BoolOpt) Connect with multipath (FC only; iSCSI multipath is controlled by "
-"Nova)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml42(td)
-msgid "storwize_svc_vol_autoexpand = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml43(td)
-msgid "(BoolOpt) Storage system autoexpand parameter for volumes (True/False)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml46(td)
-msgid "storwize_svc_vol_compression = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml47(td)
-msgid "(BoolOpt) Storage system compression option for volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml50(td)
-msgid "storwize_svc_vol_easytier = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml51(td)
-msgid "(BoolOpt) Enable Easy Tier for volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml54(td)
-msgid "storwize_svc_vol_grainsize = 256"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml55(td)
-msgid ""
-"(IntOpt) Storage system grain size parameter for volumes (32/64/128/256)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml58(td)
-msgid "storwize_svc_vol_iogrp = 0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml59(td)
-msgid "(IntOpt) The I/O group in which to allocate volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml62(td)
-msgid "storwize_svc_vol_rsize = 2"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml63(td)
-msgid ""
-"(IntOpt) Storage system space-efficiency parameter for volumes (percentage)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml66(td)
-msgid "storwize_svc_vol_warning = 0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml67(td)
-msgid ""
-"(IntOpt) Storage system threshold for volume capacity warnings (percentage)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml70(td)
-msgid "storwize_svc_volpool_name = volpool"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml71(td)
-msgid "(StrOpt) Storage system storage pool for volumes"
-msgstr ""
-
-#: ./doc/common/tables/nova-rootwrap.xml22(td)
-msgid "filters_path = /etc/nova/rootwrap.d,/usr/share/nova/rootwrap"
-msgstr ""
-
-#: ./doc/common/tables/nova-rootwrap.xml35(td)
-msgid ""
-"Which syslog facility to use. Valid values include auth, authpriv, syslog, "
-"user0, user1... Default value is 'syslog'"
-msgstr ""
-
-#: ./doc/common/tables/cinder-solidfire.xml8(caption)
-msgid "Description of configuration options for solidfire"
-msgstr ""
-
-#: ./doc/common/tables/cinder-solidfire.xml22(td)
-msgid "sf_account_prefix = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-solidfire.xml23(td)
-msgid ""
-"(StrOpt) Create SolidFire accounts with this prefix. Any string can be used "
-"here, but the string \"hostname\" is special and will create a prefix using "
-"the cinder node hostsname (previous default behavior). The default is NO "
-"prefix."
-msgstr ""
-
-#: ./doc/common/tables/cinder-solidfire.xml26(td)
-msgid "sf_allow_tenant_qos = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-solidfire.xml27(td)
-msgid "(BoolOpt) Allow tenants to specify QOS on create"
-msgstr ""
-
-#: ./doc/common/tables/cinder-solidfire.xml30(td)
-msgid "sf_api_port = 443"
-msgstr ""
-
-#: ./doc/common/tables/cinder-solidfire.xml31(td)
-msgid ""
-"(IntOpt) SolidFire API port. Useful if the device api is behind a proxy on a"
-" different port."
-msgstr ""
-
-#: ./doc/common/tables/cinder-solidfire.xml34(td)
-msgid "sf_emulate_512 = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-solidfire.xml35(td)
-msgid "(BoolOpt) Set 512 byte emulation on volume creation;"
-msgstr ""
-
-#: ./doc/common/tables/keystone-revoke.xml8(caption)
-msgid "Description of configuration options for revoke"
-msgstr ""
-
-#: ./doc/common/tables/keystone-revoke.xml19(th)
-msgid "[revoke]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-revoke.xml23(td)
-msgid ""
-"(BoolOpt) Toggle for revocation event cacheing. This has no effect unless "
-"global caching is enabled."
-msgstr ""
-
-#: ./doc/common/tables/keystone-revoke.xml26(td)
-msgid "driver = keystone.contrib.revoke.backends.kvs.Revoke"
-msgstr ""
-
-#: ./doc/common/tables/keystone-revoke.xml27(td)
-msgid ""
-"(StrOpt) An implementation of the backend for persisting revocation events."
-msgstr ""
-
-#: ./doc/common/tables/keystone-revoke.xml30(td)
-msgid "expiration_buffer = 1800"
-msgstr ""
-
-#: ./doc/common/tables/keystone-revoke.xml31(td)
-msgid ""
-"(IntOpt) This value (calculated in seconds) is added to token expiration "
-"before a revocation event may be removed from the backend."
-msgstr ""
-
-#: ./doc/common/tables/glance-ssl.xml27(td)
-msgid "(StrOpt) Certificate file to use when starting API server securely."
-msgstr ""
-
-#: ./doc/common/tables/glance-ssl.xml31(td)
-msgid "(StrOpt) Private key file to use when starting API server securely."
-msgstr ""
-
-#: ./doc/common/tables/heat-metadata_api.xml8(caption)
-msgid "Description of configuration options for metadata_api"
-msgstr ""
-
-#: ./doc/common/tables/nova-apiv3.xml8(caption)
-msgid "Description of configuration options for apiv3"
-msgstr ""
-
-#: ./doc/common/tables/nova-apiv3.xml19(th)
-msgid "[osapi_v3]"
-msgstr ""
-
-#: ./doc/common/tables/nova-apiv3.xml23(td)
-msgid "(BoolOpt) Whether the V3 API is enabled or not"
-msgstr ""
-
-#: ./doc/common/tables/nova-apiv3.xml26(td)
-msgid "extensions_blacklist ="
-msgstr ""
-
-#: ./doc/common/tables/nova-apiv3.xml27(td)
-msgid ""
-"(ListOpt) A list of v3 API extensions to never load. Specify the extension "
-"aliases here."
-msgstr ""
-
-#: ./doc/common/tables/nova-apiv3.xml30(td)
-msgid "extensions_whitelist ="
-msgstr ""
-
-#: ./doc/common/tables/nova-apiv3.xml31(td)
-msgid ""
-"(ListOpt) If the list is not empty then a v3 API extension will only be "
-"loaded if it exists in this list. Specify the extension aliases here."
-msgstr ""
-
-#: ./doc/common/tables/glance-db.xml86(td)
-msgid "sqlite_db = glance.sqlite"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml22(td)
-msgid "default_interface_name = breth0"
-msgstr "default_interface_name = breth0"
-
-#: ./doc/common/tables/neutron-vmware.xml23(td)
-msgid ""
-"(StrOpt) Name of the interface on a L2 Gateway transport nodewhich should be"
-" used by default when setting up a network connection"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml26(td)
-msgid "default_l2_gw_service_uuid = None"
-msgstr "default_l2_gw_service_uuid = None"
-
-#: ./doc/common/tables/neutron-vmware.xml27(td)
-msgid ""
-"(StrOpt) Unique identifier of the NSX L2 Gateway service which will be used "
-"by default for network gateways"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml30(td)
-msgid "default_l3_gw_service_uuid = None"
-msgstr "default_l3_gw_service_uuid = None"
-
-#: ./doc/common/tables/neutron-vmware.xml31(td)
-msgid ""
-"(StrOpt) Unique identifier of the NSX L3 Gateway service which will be used "
-"for implementing routers and floating IPs"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml34(td)
-msgid "default_service_cluster_uuid = None"
-msgstr "default_service_cluster_uuid = None"
-
-#: ./doc/common/tables/neutron-vmware.xml35(td)
-msgid ""
-"(StrOpt) Unique identifier of the Service Cluster which will be used by "
-"logical services like dhcp and metadata"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml38(td)
-msgid "default_tz_uuid = None"
-msgstr "default_tz_uuid = None"
-
-#: ./doc/common/tables/neutron-vmware.xml39(td)
-msgid ""
-"(StrOpt) This is uuid of the default NSX Transport zone that will be used "
-"for creating tunneled isolated \"Neutron\" networks. It needs to be created "
-"in NSX before starting Neutron with the nsx plugin."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml42(td)
-msgid "http_timeout = 10"
-msgstr "http_timeout = 10"
-
-#: ./doc/common/tables/neutron-vmware.xml43(td)
-msgid "(IntOpt) Time before aborting a request"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml46(td)
-msgid "nsx_controllers = None"
-msgstr "nsx_controllers = None"
-
-#: ./doc/common/tables/neutron-vmware.xml47(td)
-msgid "(ListOpt) Lists the NSX controllers in this cluster"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml50(td)
-msgid "nsx_password = admin"
-msgstr "nsx_password = admin"
-
-#: ./doc/common/tables/neutron-vmware.xml51(td)
-msgid "(StrOpt) Password for NSX controllers in this cluster"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml54(td)
-msgid "nsx_user = admin"
-msgstr "nsx_user = admin"
-
-#: ./doc/common/tables/neutron-vmware.xml55(td)
-msgid "(StrOpt) User name for NSX controllers in this cluster"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml58(td)
-msgid "redirects = 2"
-msgstr "redirects = 2"
-
-#: ./doc/common/tables/neutron-vmware.xml59(td)
-msgid "(IntOpt) Number of times a redirect should be followed"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml62(td)
-msgid "req_timeout = 30"
-msgstr "req_timeout = 30"
-
-#: ./doc/common/tables/neutron-vmware.xml63(td)
-msgid "(IntOpt) Total time limit for a cluster request"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml66(td)
-msgid "retries = 2"
-msgstr "retries = 2"
-
-#: ./doc/common/tables/neutron-vmware.xml67(td)
-msgid "(IntOpt) Number of time a request should be retried"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml73(td)
-msgid "retries = 3"
-msgstr "retries = 3"
-
-#: ./doc/common/tables/neutron-vmware.xml74(td)
-msgid ""
-"(IntOpt) The number of retries the agent will send request to daemon before "
-"giving up"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml77(th)
-msgid "[NSX]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml80(td)
-msgid "agent_mode = agent"
-msgstr "agent_mode = agent"
-
-#: ./doc/common/tables/neutron-vmware.xml81(td)
-msgid "(StrOpt) The mode used to implement DHCP/metadata services."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml84(td)
-msgid "concurrent_connections = 10"
-msgstr "concurrent_connections = 10"
-
-#: ./doc/common/tables/neutron-vmware.xml85(td)
-msgid "(IntOpt) Maximum concurrent connections to each NSX controller."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml88(td)
-msgid "default_transport_type = stt"
-msgstr "default_transport_type = stt"
-
-#: ./doc/common/tables/neutron-vmware.xml89(td)
-msgid ""
-"(StrOpt) The default network tranport type to use (stt, gre, bridge, "
-"ipsec_gre, or ipsec_stt)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml92(td)
-msgid "max_lp_per_bridged_ls = 5000"
-msgstr "max_lp_per_bridged_ls = 5000"
-
-#: ./doc/common/tables/neutron-vmware.xml93(td)
-msgid ""
-"(IntOpt) Maximum number of ports of a logical switch on a bridged transport "
-"zone (default 5000)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml96(td)
-msgid "max_lp_per_overlay_ls = 256"
-msgstr "max_lp_per_overlay_ls = 256"
-
-#: ./doc/common/tables/neutron-vmware.xml97(td)
-msgid ""
-"(IntOpt) Maximum number of ports of a logical switch on an overlay transport"
-" zone (default 256)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml100(td)
-msgid "metadata_mode = access_network"
-msgstr "metadata_mode = access_network"
-
-#: ./doc/common/tables/neutron-vmware.xml101(td)
-msgid ""
-"(StrOpt) If set to access_network this enables a dedicated connection to the"
-" metadata proxy for metadata server access via Neutron router. If set to "
-"dhcp_host_route this enables host route injection via the dhcp agent. This "
-"option is only useful if running on a host that does not support namespaces "
-"otherwise access_network should be used."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml104(td)
-msgid "nsx_gen_timeout = -1"
-msgstr "nsx_gen_timeout = -1"
-
-#: ./doc/common/tables/neutron-vmware.xml105(td)
-msgid ""
-"(IntOpt) Number of seconds a generation id should be valid for (default -1 "
-"meaning do not time out)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml108(td)
-msgid "replication_mode = service"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml109(td)
-msgid ""
-"(StrOpt) The default option leverages service nodes to perform packet "
-"replication though one could set to this to 'source' to perform replication "
-"locally. This is useful if one does not want to deploy a service node(s)."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml112(th)
-msgid "[NSX_DHCP]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml115(td)
-msgid "default_lease_time = 43200"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml116(td)
-msgid "(IntOpt) Default DHCP lease time"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml119(td)
-msgid "domain_name = openstacklocal"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml123(td)
-msgid "extra_domain_name_servers ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml124(td)
-msgid "(ListOpt) Comma separated list of additional domain name servers"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml127(th)
-msgid "[NSX_LSN]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml130(td)
-msgid "sync_on_missing_data = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml131(td)
-msgid ""
-"(BoolOpt) Pull LSN information from NSX in case it is missing from the local"
-" data store. This is useful to rebuild the local store in case of server "
-"recovery."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml134(th)
-msgid "[NSX_METADATA]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml137(td)
-msgid "metadata_server_address = 127.0.0.1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml138(td)
-msgid "(StrOpt) IP address used by Metadata server."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml141(td)
-msgid "metadata_server_port = 8775"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml142(td)
-msgid "(IntOpt) TCP Port used by Metadata server."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml145(td)
-msgid "metadata_shared_secret ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml149(th)
-msgid "[NSX_SYNC]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml152(td)
-msgid "always_read_status = False"
-msgstr "always_read_status = False"
-
-#: ./doc/common/tables/neutron-vmware.xml153(td)
-msgid ""
-"(BoolOpt) Always read operational status from backend on show operations. "
-"Enabling this option might slow down the system."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml156(td)
-msgid "max_random_sync_delay = 0"
-msgstr "max_random_sync_delay = 0"
-
-#: ./doc/common/tables/neutron-vmware.xml157(td)
-msgid ""
-"(IntOpt) Maximum value for the additional random delay in seconds between "
-"runs of the state synchronization task"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml160(td)
-msgid "min_chunk_size = 500"
-msgstr "min_chunk_size = 500"
-
-#: ./doc/common/tables/neutron-vmware.xml161(td)
-msgid ""
-"(IntOpt) Minimum number of resources to be retrieved from NSX during state "
-"synchronization"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml164(td)
-msgid "min_sync_req_delay = 1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml165(td)
-msgid ""
-"(IntOpt) Minimum delay, in seconds, between two state synchronization "
-"queries to NSX. It must not exceed state_sync_interval"
-msgstr ""
+#: ./doc/common/tables/cinder-coraid.xml22(td)
+msgid "coraid_esm_address ="
+msgstr "coraid_esm_address ="
 
-#: ./doc/common/tables/neutron-vmware.xml168(td)
-msgid "state_sync_interval = 10"
+#: ./doc/common/tables/cinder-coraid.xml23(td)
+msgid "(StrOpt) IP address of Coraid ESM"
 msgstr ""
 
-#: ./doc/common/tables/neutron-vmware.xml169(td)
-msgid ""
-"(IntOpt) Interval in seconds between runs of the state synchronization task."
-" Set it to 0 to disable it"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml172(th)
-msgid "[vcns]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml175(td)
-msgid "datacenter_moid = None"
-msgstr "datacenter_moid = None"
-
-#: ./doc/common/tables/neutron-vmware.xml176(td)
-msgid ""
-"(StrOpt) Optional parameter identifying the ID of datacenter to deploy NSX "
-"Edges"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml179(td)
-msgid "datastore_id = None"
-msgstr "datastore_id = None"
-
-#: ./doc/common/tables/neutron-vmware.xml180(td)
-#: ./doc/common/tables/neutron-vmware.xml184(td)
-msgid ""
-"(StrOpt) Optional parameter identifying the ID of datastore to deploy NSX "
-"Edges"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml183(td)
-msgid "deployment_container_id = None"
-msgstr "deployment_container_id = None"
-
-#: ./doc/common/tables/neutron-vmware.xml187(td)
-msgid "external_network = None"
-msgstr "external_network = None"
-
-#: ./doc/common/tables/neutron-vmware.xml188(td)
-msgid "(StrOpt) Network ID for physical network connectivity"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml191(td)
-msgid "manager_uri = None"
-msgstr "manager_uri = None"
-
-#: ./doc/common/tables/neutron-vmware.xml192(td)
-msgid "(StrOpt) uri for vsm"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml195(td)
-msgid "password = default"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml196(td)
-msgid "(StrOpt) Password for vsm"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml200(td)
-msgid ""
-"(StrOpt) Optional parameter identifying the ID of resource to deploy NSX "
-"Edges"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml203(td)
-msgid "task_status_check_interval = 2000"
-msgstr "task_status_check_interval = 2000"
-
-#: ./doc/common/tables/neutron-vmware.xml204(td)
-msgid "(IntOpt) Task status check interval"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml207(td)
-msgid "user = admin"
-msgstr "user = admin"
-
-#: ./doc/common/tables/neutron-vmware.xml208(td)
-msgid "(StrOpt) User name for vsm"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml7(literal)
-msgid "[realm2]"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml18(td)
-msgid "key = realm2key"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml21(td)
-msgid "key2 = realm2key2"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml24(td)
-msgid "cluster_name3 = https://host3/v1/"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml27(td)
-msgid "cluster_name4 = https://host4/v1/"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml22(td)
-msgid "api_rate_limit = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml23(td)
-msgid ""
-"(BoolOpt) Whether to use per-user rate limiting for the api. This option is "
-"only used by v2 api. Rate limiting is removed from v3 api."
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml30(td)
-msgid "enabled_apis = ec2, osapi_compute, metadata"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml31(td)
-msgid "(ListOpt) A list of APIs to enable by default"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml34(td)
-msgid "enabled_ssl_apis ="
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml35(td)
-msgid "(ListOpt) A list of APIs with enabled SSL"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml38(td)
-msgid "instance_name_template = instance-%08x"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml39(td)
-msgid "(StrOpt) Template string to be used to generate instance names"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml46(td)
-msgid "multi_instance_display_name_template = %(name)s-%(uuid)s"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml47(td)
-msgid ""
-"(StrOpt) When creating multiple instances with a single request using the "
-"os-multiple-create API extension, this template will be used to build the "
-"display name for each instance. The benefit is that the instances end up "
-"with different hostnames. To restore legacy behavior of every instance "
-"having the same name, set this option to \"%(name)s\". Valid keys for the "
-"template are: name, uuid, count."
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml50(td)
-msgid "non_inheritable_image_properties = cache_in_nova, bittorrent"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml51(td)
-msgid ""
-"(ListOpt) These are image properties which a snapshot should not inherit "
-"from an instance"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml54(td)
-msgid "null_kernel = nokernel"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml55(td)
-msgid ""
-"(StrOpt) Kernel image that indicates not to use a kernel, but to use a raw "
-"disk image instead"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml58(td)
-msgid "osapi_compute_ext_list ="
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml59(td)
-msgid ""
-"(ListOpt) Specify list of extensions to load when using "
-"osapi_compute_extension option with "
-"nova.api.openstack.compute.contrib.select_extensions"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml62(td)
-msgid ""
-"osapi_compute_extension = "
-"['nova.api.openstack.compute.contrib.standard_extensions']"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml63(td)
-msgid "(MultiStrOpt) osapi compute extension to load"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml66(td)
-msgid "osapi_compute_link_prefix = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml67(td)
-msgid ""
-"(StrOpt) Base URL that will be presented to users in links to the OpenStack "
-"Compute API"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml70(td)
-msgid "osapi_compute_listen = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml71(td)
-msgid "(StrOpt) The IP address on which the OpenStack API will listen."
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml74(td)
-msgid "osapi_compute_listen_port = 8774"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml75(td)
-msgid "(IntOpt) The port on which the OpenStack API will listen."
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml78(td)
-msgid "osapi_compute_workers = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml79(td)
-msgid ""
-"(IntOpt) Number of workers for OpenStack API service. The default will be "
-"the number of CPUs available."
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml82(td)
-msgid "osapi_hide_server_address_states = building"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml83(td)
-msgid "(ListOpt) List of instance states that should hide network info"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml86(td)
-msgid "servicegroup_driver = db"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml87(td)
-msgid ""
-"(StrOpt) The driver for servicegroup service (valid options are: db, zk, mc)"
-msgstr ""
-
-#: ./doc/common/tables/glance-matchmaker.xml8(caption)
-msgid "Description of configuration options for matchmaker"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml19(th)
-msgid "[signing]"
-msgstr "[signing]"
-
-#: ./doc/common/tables/keystone-ssl.xml22(td)
-#: ./doc/common/tables/keystone-ssl.xml57(td)
-msgid "ca_certs = /etc/keystone/ssl/certs/ca.pem"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml23(td)
-msgid "(StrOpt) Path of the CA for token signing."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml26(td)
-#: ./doc/common/tables/keystone-ssl.xml61(td)
-msgid "ca_key = /etc/keystone/ssl/private/cakey.pem"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml27(td)
-msgid "(StrOpt) Path of the CA Key for token signing."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml30(td)
-msgid "cert_subject = /C=US/ST=Unset/L=Unset/O=Unset/CN=www.example.com"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml31(td)
-msgid ""
-"(StrOpt) Certificate Subject (auto generated certificate) for token signing."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml34(td)
-msgid "certfile = /etc/keystone/ssl/certs/signing_cert.pem"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml35(td)
-msgid "(StrOpt) Path of the certfile for token signing."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml38(td)
-msgid "key_size = 2048"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml39(td)
-msgid ""
-"(IntOpt) Key Size (in bits) for token signing cert (auto generated "
-"certificate)."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml42(td)
-msgid "keyfile = /etc/keystone/ssl/private/signing_key.pem"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml43(td)
-msgid "(StrOpt) Path of the keyfile for token signing."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml46(td)
-msgid "token_format = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml47(td)
-msgid "(StrOpt) Deprecated in favor of provider in the [token] section."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml50(td)
-#: ./doc/common/tables/keystone-ssl.xml89(td)
-msgid "valid_days = 3650"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml51(td)
-msgid ""
-"(IntOpt) Day the token signing cert is valid for (auto generated "
-"certificate)."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml58(td)
-msgid "(StrOpt) Path of the ca cert file for SSL."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml62(td)
-msgid "(StrOpt) Path of the CA key file for SSL."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml65(td)
-msgid "cert_required = False"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml66(td)
-msgid "(BoolOpt) Require client certificate."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml69(td)
-msgid "cert_subject = /C=US/ST=Unset/L=Unset/O=Unset/CN=localhost"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml70(td)
-msgid "(StrOpt) SSL Certificate Subject (auto generated certificate)."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml73(td)
-msgid "certfile = /etc/keystone/ssl/certs/keystone.pem"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml74(td)
-msgid "(StrOpt) Path of the certfile for SSL."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml78(td)
-msgid "(BoolOpt) Toggle for SSL support on the keystone eventlet servers."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml81(td)
-msgid "key_size = 1024"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml82(td)
-msgid "(IntOpt) SSL Key Length (in bits) (auto generated certificate)."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml85(td)
-msgid "keyfile = /etc/keystone/ssl/private/keystonekey.pem"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml86(td)
-msgid "(StrOpt) Path of the keyfile for SSL."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml90(td)
-msgid ""
-"(IntOpt) Days the certificate is valid for once signed (auto generated "
-"certificate)."
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-container.xml7(literal)
-msgid "[container]"
-msgstr "[container]"
-
-#: ./doc/common/tables/swift-rsyncd-container.xml18(td)
-msgid "max connections = 4"
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-container.xml27(td)
-msgid "lock file = /var/lock/container.lock"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san-solaris.xml8(caption)
-msgid "Description of configuration options for san-solaris"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san-solaris.xml22(td)
-msgid "san_zfs_volume_base = rpool/"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san-solaris.xml23(td)
-msgid "(StrOpt) The ZFS path under which to create zvols for volumes."
-msgstr ""
-
-#: ./doc/common/tables/trove-heat.xml8(caption)
-msgid "Description of configuration options for heat"
-msgstr ""
-
-#: ./doc/common/tables/trove-heat.xml22(td)
-msgid "heat_time_out = 60"
-msgstr "heat_time_out = 60"
+#: ./doc/common/tables/cinder-coraid.xml26(td)
+msgid "coraid_group = admin"
+msgstr "coraid_group = admin"
 
-#: ./doc/common/tables/trove-heat.xml26(td)
-msgid "heat_url = http://localhost:8004/v1"
-msgstr "heat_url = http://localhost:8004/v1"
-
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml8(caption)
-msgid "Description of configuration options for netapp_cdot_nfs"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml26(td)
-msgid "netapp_copyoffload_tool_path = None"
-msgstr "netapp_copyoffload_tool_path = None"
-
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml27(td)
-msgid ""
-"(StrOpt) This option specifies the path of the NetApp copy offload tool "
-"binary. Ensure that the binary has execute permissions set which allow the "
-"effective user of the cinder-volume process to execute the file."
-msgstr ""
-
-#: ./doc/common/tables/glance-paste.xml8(caption)
-msgid "Description of configuration options for paste"
-msgstr ""
-
-#: ./doc/common/tables/glance-paste.xml22(td)
-msgid "config_file = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-paste.xml23(td)
-msgid "(StrOpt) Name of the paste configuration file."
-msgstr ""
-
-#: ./doc/common/tables/glance-paste.xml27(td)
+#: ./doc/common/tables/cinder-coraid.xml27(td)
 msgid ""
-"(StrOpt) Partial name of a pipeline in your paste configuration file with "
-"the service name removed. For example, if your paste section name is "
-"[pipeline:glance-api-keystone] use the value \"keystone\""
-msgstr ""
-
-#: ./doc/common/tables/nova-rdp.xml8(caption)
-msgid "Description of configuration options for rdp"
-msgstr ""
-
-#: ./doc/common/tables/nova-rdp.xml19(th)
-msgid "[rdp]"
-msgstr ""
-
-#: ./doc/common/tables/nova-rdp.xml23(td)
-msgid "(BoolOpt) Enable RDP related features"
+"(StrOpt) Name of group on Coraid ESM to which coraid_user belongs (must have"
+" admin privilege)"
 msgstr ""
 
-#: ./doc/common/tables/nova-rdp.xml26(td)
-msgid "html5_proxy_base_url = http://127.0.0.1:6083/"
-msgstr ""
+#: ./doc/common/tables/cinder-coraid.xml30(td)
+msgid "coraid_password = password"
+msgstr "coraid_password = password"
 
-#: ./doc/common/tables/nova-rdp.xml27(td)
-msgid ""
-"(StrOpt) Location of RDP html5 console proxy, in the form "
-"\"http://127.0.0.1:6083/\""
+#: ./doc/common/tables/cinder-coraid.xml31(td)
+msgid "(StrOpt) Password to connect to Coraid ESM"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml8(caption)
-msgid "Description of configuration options for quotas"
-msgstr "Description des options de configuration pour les quotas"
-
-#: ./doc/common/tables/neutron-quotas.xml22(td)
-msgid "max_routes = 30"
-msgstr ""
+#: ./doc/common/tables/cinder-coraid.xml34(td)
+msgid "coraid_repository_key = coraid_repository"
+msgstr "coraid_repository_key = coraid_repository"
 
-#: ./doc/common/tables/neutron-quotas.xml23(td)
-msgid "(IntOpt) Maximum number of routes"
+#: ./doc/common/tables/cinder-coraid.xml35(td)
+msgid "(StrOpt) Volume Type key name to store ESM Repository Name"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml26(th)
-msgid "[QUOTAS]"
-msgstr ""
+#: ./doc/common/tables/cinder-coraid.xml38(td)
+msgid "coraid_user = admin"
+msgstr "coraid_user = admin"
 
-#: ./doc/common/tables/neutron-quotas.xml29(td)
-msgid "default_quota = -1"
+#: ./doc/common/tables/cinder-coraid.xml39(td)
+msgid "(StrOpt) User name to connect to Coraid ESM"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml30(td)
-msgid ""
-"(IntOpt) Default number of resource allowed per tenant. A negative value "
-"means unlimited."
+#: ./doc/common/tables/neutron-wsgi.xml8(caption)
+#: ./doc/common/tables/glance-wsgi.xml8(caption)
+#: ./doc/common/tables/nova-wsgi.xml8(caption)
+msgid "Description of configuration options for wsgi"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml33(td)
-msgid "quota_driver = neutron.db.quota_db.DbQuotaDriver"
+#: ./doc/common/tables/neutron-wsgi.xml23(td)
+#: ./doc/common/tables/trove-debug.xml27(td)
+msgid "(IntOpt) Number of backlog requests to configure the socket with"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml34(td)
-#: ./doc/common/tables/nova-quota.xml35(td)
-msgid "(StrOpt) Default driver to use for quota checks"
-msgstr "(StrOpt)  pilote par défaut à utiliser pour vérifications de quota"
-
-#: ./doc/common/tables/neutron-quotas.xml37(td)
-msgid "quota_firewall = 1"
+#: ./doc/common/tables/neutron-wsgi.xml26(td)
+msgid "retry_until_window = 30"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml38(td)
-msgid ""
-"(IntOpt) Number of firewalls allowed per tenant. A negative value means "
-"unlimited."
+#: ./doc/common/tables/neutron-wsgi.xml27(td)
+msgid "(IntOpt) Number of seconds to keep retrying to listen"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml41(td)
-msgid "quota_firewall_policy = 1"
+#: ./doc/common/tables/cinder-compute.xml22(td)
+msgid "nova_api_insecure = False"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml42(td)
-msgid ""
-"(IntOpt) Number of firewall policies allowed per tenant. A negative value "
-"means unlimited."
+#: ./doc/common/tables/cinder-compute.xml23(td)
+msgid "(BoolOpt) Allow to perform insecure SSL requests to nova"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml45(td)
-msgid "quota_firewall_rule = -1"
-msgstr ""
+#: ./doc/common/tables/cinder-compute.xml26(td)
+msgid "nova_ca_certificates_file = None"
+msgstr "nova_ca_certificates_file = None"
 
-#: ./doc/common/tables/neutron-quotas.xml46(td)
+#: ./doc/common/tables/cinder-compute.xml27(td)
 msgid ""
-"(IntOpt) Number of firewall rules allowed per tenant. A negative value means"
-" unlimited."
+"(StrOpt) Location of ca certificates file to use for nova client requests."
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml49(td)
-msgid "quota_floatingip = 50"
+#: ./doc/common/tables/cinder-compute.xml30(td)
+msgid "nova_catalog_admin_info = compute:nova:adminURL"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml50(td)
-msgid ""
-"(IntOpt) Number of floating IPs allowed per tenant. A negative value means "
-"unlimited."
+#: ./doc/common/tables/cinder-compute.xml31(td)
+msgid "(StrOpt) Same as nova_catalog_info, but for admin endpoint."
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml53(td)
-msgid "quota_health_monitor = -1"
+#: ./doc/common/tables/cinder-compute.xml34(td)
+msgid "nova_catalog_info = compute:nova:publicURL"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml54(td)
+#: ./doc/common/tables/cinder-compute.xml35(td)
 msgid ""
-"(IntOpt) Number of health monitors allowed per tenant. A negative value "
-"means unlimited."
+"(StrOpt) Info to match when looking for nova in the service catalog. Format "
+"is : separated values of the form: "
+"&lt;service_type&gt;:&lt;service_name&gt;:&lt;endpoint_type&gt;"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml57(td)
-msgid "quota_items = network, subnet, port"
+#: ./doc/common/tables/cinder-compute.xml38(td)
+msgid "nova_endpoint_admin_template = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml58(td)
-msgid "(ListOpt) Resource name(s) that are supported in quota features"
+#: ./doc/common/tables/cinder-compute.xml39(td)
+msgid "(StrOpt) Same as nova_endpoint_template, but for admin endpoint."
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml61(td)
-msgid "quota_member = -1"
+#: ./doc/common/tables/cinder-compute.xml42(td)
+msgid "nova_endpoint_template = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml62(td)
+#: ./doc/common/tables/cinder-compute.xml43(td)
 msgid ""
-"(IntOpt) Number of pool members allowed per tenant. A negative value means "
-"unlimited."
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml65(td)
-msgid "quota_network = 10"
+"(StrOpt) Override service catalog lookup with template for nova endpoint "
+"e.g. http://localhost:8774/v2/%(project_id)s"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml66(td)
-msgid ""
-"(IntOpt) Number of networks allowed per tenant.A negative value means "
-"unlimited."
+#: ./doc/common/tables/cinder-compute.xml47(td)
+msgid "(StrOpt) region name of this node"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml69(td)
-msgid "quota_network_gateway = 5"
-msgstr ""
+#: ./doc/common/tables/swift-rsyncd-object.xml7(literal)
+msgid "[object]"
+msgstr "[object]"
 
-#: ./doc/common/tables/neutron-quotas.xml70(td)
-msgid ""
-"(IntOpt) Number of network gateways allowed per tenant, -1 for unlimited"
+#: ./doc/common/tables/swift-rsyncd-object.xml18(td)
+msgid "max connections = 8"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml73(td)
-msgid "quota_packet_filter = 100"
-msgstr ""
+#: ./doc/common/tables/swift-rsyncd-object.xml27(td)
+msgid "lock file = /var/lock/object.lock"
+msgstr "lock file = /var/lock/object.lock"
 
-#: ./doc/common/tables/neutron-quotas.xml74(td)
-msgid "(IntOpt) Number of packet_filters allowed per tenant, -1 for unlimited"
+#: ./doc/common/tables/glance-wsgi.xml23(td)
+msgid "(IntOpt) port for eventlet backdoor to listen"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml77(td)
-msgid "quota_pool = 10"
-msgstr ""
+#: ./doc/common/tables/glance-wsgi.xml26(td)
+msgid "eventlet_hub = poll"
+msgstr "eventlet_hub = poll"
 
-#: ./doc/common/tables/neutron-quotas.xml78(td)
+#: ./doc/common/tables/glance-wsgi.xml27(td)
 msgid ""
-"(IntOpt) Number of pools allowed per tenant. A negative value means "
-"unlimited."
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml81(td)
-msgid "quota_port = 50"
+"(StrOpt) Name of eventlet hub to use. Traditionally, we have only supported "
+"'poll', however 'selects' may be appropriate for some platforms. See "
+"http://eventlet.net/doc/hubs.html for more details."
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml82(td)
+#: ./doc/common/tables/glance-wsgi.xml35(td)
 msgid ""
-"(IntOpt) Number of ports allowed per tenant. A negative value means "
-"unlimited."
+"(IntOpt) The value for the socket option TCP_KEEPIDLE. This is the time in "
+"seconds that the connection must be idle before TCP starts sending keepalive"
+" probes."
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml85(td)
-msgid "quota_router = 10"
-msgstr ""
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml7(literal)
+msgid "[drive-audit]"
+msgstr "[drive-audit]"
 
-#: ./doc/common/tables/neutron-quotas.xml86(td)
-msgid ""
-"(IntOpt) Number of routers allowed per tenant. A negative value means "
-"unlimited."
-msgstr ""
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml7(literal)
+msgid "drive-audit.conf-sample"
+msgstr "drive-audit.conf-sample"
 
-#: ./doc/common/tables/neutron-quotas.xml89(td)
-msgid "quota_security_group = 10"
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml18(td)
+msgid "device_dir = /srv/node"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml90(td)
-msgid ""
-"(IntOpt) Number of security groups allowed per tenant. A negative value "
-"means unlimited."
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml18(td)
+msgid "Directory devices are mounted under"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml93(td)
-msgid "quota_security_group_rule = 100"
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml30(td)
+msgid "minutes = 60"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml94(td)
-msgid ""
-"(IntOpt) Number of security rules allowed per tenant. A negative value means"
-" unlimited."
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml30(td)
+msgid "Number of minutes to look back in `/var/log/kern.log`"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml97(td)
-msgid "quota_subnet = 10"
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml33(td)
+msgid "error_limit = 1"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml98(td)
-msgid ""
-"(IntOpt) Number of subnets allowed per tenant, A negative value means "
-"unlimited."
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml33(td)
+msgid "Number of errors to find before a device is unmounted"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml101(td)
-msgid "quota_vip = 10"
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml36(td)
+msgid "log_file_pattern = /var/log/kern*"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml102(td)
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml36(td)
 msgid ""
-"(IntOpt) Number of vips allowed per tenant. A negative value means "
-"unlimited."
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml8(caption)
-msgid "Description of configuration options for guestagent"
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml22(td)
-msgid "agent_call_high_timeout = 60"
-msgstr "agent_call_high_timeout = 60"
-
-#: ./doc/common/tables/trove-guestagent.xml26(td)
-msgid "agent_call_low_timeout = 5"
-msgstr "agent_call_low_timeout = 5"
-
-#: ./doc/common/tables/trove-guestagent.xml30(td)
-msgid "agent_heartbeat_time = 10"
-msgstr "agent_heartbeat_time = 10"
-
-#: ./doc/common/tables/trove-guestagent.xml34(td)
-msgid "guest_config = $pybasedir/etc/trove/trove-guestagent.conf.sample"
-msgstr "guest_config = $pybasedir/etc/trove/trove-guestagent.conf.sample"
-
-#: ./doc/common/tables/trove-guestagent.xml35(td)
-msgid "(StrOpt) Path to guestagent config file."
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml38(td)
-msgid "guest_id = None"
-msgstr "guest_id = None"
-
-#: ./doc/common/tables/trove-guestagent.xml42(td)
-msgid "ignore_dbs = lost+found, mysql, information_schema"
-msgstr "ignore_dbs = lost+found, mysql, information_schema"
-
-#: ./doc/common/tables/trove-guestagent.xml46(td)
-msgid "ignore_users = os_admin, root"
-msgstr "ignore_users = os_admin, root"
-
-#: ./doc/common/tables/trove-guestagent.xml50(td)
-msgid "mount_options = defaults,noatime"
-msgstr "mount_options = defaults,noatime"
-
-#: ./doc/common/tables/trove-guestagent.xml54(td)
-msgid "restore_namespace = trove.guestagent.strategies.restore.mysql_impl"
-msgstr "restore_namespace = trove.guestagent.strategies.restore.mysql_impl"
-
-#: ./doc/common/tables/trove-guestagent.xml55(td)
-msgid "(StrOpt) Namespace to load restore strategies from."
+"Location of the log file with globbing pattern to check against device "
+"errors locate device blocks with errors in the log file"
 msgstr ""
 
-#: ./doc/common/tables/trove-guestagent.xml58(td)
-msgid "storage_namespace = trove.guestagent.strategies.storage.swift"
-msgstr "storage_namespace = trove.guestagent.strategies.storage.swift"
-
-#: ./doc/common/tables/trove-guestagent.xml59(td)
-msgid "(StrOpt) Namespace to load the default storage strategy from."
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml62(td)
-msgid "storage_strategy = SwiftStorage"
-msgstr "storage_strategy = SwiftStorage"
-
-#: ./doc/common/tables/trove-guestagent.xml63(td)
-msgid "(StrOpt) Default strategy to store backups."
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml39(td)
+msgid "regex_pattern_1 = \\berror\\b.*\\b(dm-[0-9]{1,2}\\d?)\\b"
 msgstr ""
 
 #: ./doc/common/tables/nova-baremetal.xml8(caption)
@@ -47809,432 +46620,144 @@ msgstr ""
 msgid "(StrOpt) The XenAPI VIF driver using XenServer Network APIs."
 msgstr ""
 
-#: ./doc/common/tables/heat-clients_keystone.xml8(caption)
-msgid "Description of configuration options for clients_keystone"
+#: ./doc/common/tables/cinder-backups_tsm.xml8(caption)
+msgid "Description of configuration options for backups_tsm"
+msgstr "Description des options de configuration pour backups_tsm"
+
+#: ./doc/common/tables/cinder-backups_tsm.xml22(td)
+msgid "backup_tsm_compression = True"
 msgstr ""
 
-#: ./doc/common/tables/heat-clients_keystone.xml19(th)
-msgid "[clients_keystone]"
-msgstr "[clients_keystone]"
-
-#: ./doc/common/tables/swift-account-server-pipeline-main.xml18(td)
-msgid "pipeline = healthcheck recon account-server"
+#: ./doc/common/tables/cinder-backups_tsm.xml23(td)
+msgid "(BoolOpt) Enable or Disable compression for backups"
 msgstr ""
 
-#: ./doc/common/tables/keystone-rabbit.xml8(caption)
-msgid "Description of configuration options for rabbit"
+#: ./doc/common/tables/cinder-backups_tsm.xml26(td)
+msgid "backup_tsm_password = password"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml22(td)
-msgid "admin_role = admin"
+#: ./doc/common/tables/cinder-backups_tsm.xml27(td)
+msgid "(StrOpt) TSM password for the running username"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml23(td)
-msgid "(StrOpt) Role used to identify an authenticated user as administrator."
+#: ./doc/common/tables/cinder-backups_tsm.xml30(td)
+msgid "backup_tsm_volume_prefix = backup"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml26(td)
-msgid "allow_anonymous_access = False"
+#: ./doc/common/tables/cinder-backups_tsm.xml31(td)
+msgid "(StrOpt) Volume prefix for the backup id when backing up to TSM"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml27(td)
+#: ./doc/common/tables/cinder-san.xml8(caption)
+msgid "Description of configuration options for san"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san.xml22(td)
+msgid "san_clustername ="
+msgstr "san_clustername ="
+
+#: ./doc/common/tables/cinder-san.xml23(td)
+msgid "(StrOpt) Cluster name to use for creating volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san.xml26(td)
+msgid "san_ip ="
+msgstr "san_ip ="
+
+#: ./doc/common/tables/cinder-san.xml27(td)
+msgid "(StrOpt) IP address of SAN controller"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san.xml30(td)
+msgid "san_is_local = False"
+msgstr "san_is_local = False"
+
+#: ./doc/common/tables/cinder-san.xml31(td)
 msgid ""
-"(BoolOpt) Allow unauthenticated users to access the API with read-only "
-"privileges. This only applies when using ContextMiddleware."
+"(BoolOpt) Execute commands locally instead of over SSH; use if the volume "
+"service is running on the SAN device"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml30(td)
-msgid "default_publisher_id = image.localhost"
+#: ./doc/common/tables/cinder-san.xml34(td)
+msgid "san_login = admin"
+msgstr "san_login = admin"
+
+#: ./doc/common/tables/cinder-san.xml35(td)
+msgid "(StrOpt) Username for SAN controller"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml31(td)
-msgid "(StrOpt) Default publisher_id for outgoing notifications."
+#: ./doc/common/tables/cinder-san.xml38(td)
+msgid "san_password ="
+msgstr "san_password ="
+
+#: ./doc/common/tables/cinder-san.xml39(td)
+msgid "(StrOpt) Password for SAN controller"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml34(td)
-msgid "default_store = file"
+#: ./doc/common/tables/cinder-san.xml42(td)
+msgid "san_private_key ="
+msgstr "san_private_key ="
+
+#: ./doc/common/tables/cinder-san.xml43(td)
+msgid "(StrOpt) Filename of private key to use for SSH authentication"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml35(td)
+#: ./doc/common/tables/cinder-san.xml46(td)
+msgid "san_ssh_port = 22"
+msgstr "san_ssh_port = 22"
+
+#: ./doc/common/tables/cinder-san.xml47(td)
+msgid "(IntOpt) SSH port to use with SAN"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san.xml50(td)
+msgid "san_thin_provision = True"
+msgstr "san_thin_provision = True"
+
+#: ./doc/common/tables/cinder-san.xml51(td)
+msgid "(BoolOpt) Use thin provisioning for SAN volumes?"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san.xml54(td)
+msgid "ssh_conn_timeout = 30"
+msgstr "ssh_conn_timeout = 30"
+
+#: ./doc/common/tables/cinder-san.xml55(td)
+msgid "(IntOpt) SSH connection timeout in seconds"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san.xml58(td)
+msgid "ssh_max_pool_conn = 5"
+msgstr "ssh_max_pool_conn = 5"
+
+#: ./doc/common/tables/cinder-san.xml59(td)
+msgid "(IntOpt) Maximum ssh connections in the pool"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san.xml62(td)
+msgid "ssh_min_pool_conn = 1"
+msgstr "ssh_min_pool_conn = 1"
+
+#: ./doc/common/tables/cinder-san.xml63(td)
+msgid "(IntOpt) Minimum ssh connections in the pool"
+msgstr ""
+
+#: ./doc/common/tables/nova-logging.xml26(td)
 msgid ""
-"(StrOpt) Default scheme to use to store image data. The scheme must be "
-"registered by one of the stores defined by the 'known_stores' config option."
+"default_log_levels = amqp=WARN, amqplib=WARN, boto=WARN, qpid=WARN, "
+"sqlalchemy=WARN, suds=INFO, oslo.messaging=INFO, iso8601=WARN"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml39(td)
-msgid "(BoolOpt) Deploy the v1 OpenStack Images API."
+#: ./doc/common/tables/nova-logging.xml35(td)
+msgid "(BoolOpt) Make exception message format errors fatal"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml42(td)
-msgid "enable_v1_registry = True"
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml43(td)
-msgid "(BoolOpt) Deploy the v1 OpenStack Registry API."
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml47(td)
-msgid "(BoolOpt) Deploy the v2 OpenStack Images API."
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml50(td)
-msgid "enable_v2_registry = True"
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml51(td)
-msgid "(BoolOpt) Deploy the v2 OpenStack Registry API."
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml54(td)
-msgid "image_size_cap = 1099511627776"
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml55(td)
+#: ./doc/common/tables/nova-logging.xml66(td)
 msgid ""
-"(IntOpt) Maximum size of image a user can upload in bytes. Defaults to "
-"1099511627776 bytes (1 TB)."
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml58(td)
-msgid "known_stores = glance.store.filesystem.Store, glance.store.http.Store"
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml59(td)
-msgid ""
-"(ListOpt) List of which store classes and store class locations are "
-"currently known to glance at startup."
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml62(td)
-msgid "location_strategy = location_order"
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml63(td)
-msgid ""
-"(StrOpt) This value sets what strategy will be used to determine the image "
-"location order. Currently two strategies are packaged with Glance "
-"'location_order' and 'store_type'."
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml66(td)
-msgid "owner_is_tenant = True"
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml67(td)
-msgid ""
-"(BoolOpt) When true, this option sets the owner of an image to be the "
-"tenant. Otherwise, the owner of the image will be the authenticated user "
-"issuing the request."
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml70(td)
-msgid "send_identity_headers = False"
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml71(td)
-msgid ""
-"(BoolOpt) Whether to pass through headers containing user and tenant "
-"information when making requests to the registry. This allows the registry "
-"to use the context middleware without the keystoneclients' auth_token "
-"middleware, removing calls to the keystone auth service. It is recommended "
-"that when using this option, secure communication between glance api and "
-"glance registry is ensured by means other than auth_token middleware."
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml74(td)
-msgid "show_multiple_locations = False"
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml75(td)
-msgid ""
-"(BoolOpt) Whether to include the backend image locations in image "
-"properties. Revealing storage location can be a security risk, so use this "
-"setting with caution! The overrides show_image_direct_url."
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml78(td)
-msgid "use_user_token = True"
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml79(td)
-msgid ""
-"(BoolOpt) Whether to pass through the user token when making requests to the"
-" registry."
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml82(th)
-msgid "[store_type_location_strategy]"
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml85(td)
-msgid "store_type_preference ="
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml86(td)
-msgid ""
-"(ListOpt) The store names to use to get store preference order. The name "
-"must be registered by one of the stores defined by the 'known_stores' config"
-" option. This option will be applied when you using 'store_type' option as "
-"image location strategy defined by the 'location_strategy' config option."
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml22(td)
-msgid ""
-"scheduler_default_filters = AvailabilityZoneFilter, CapacityFilter, "
-"CapabilitiesFilter"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml26(td)
-msgid "scheduler_default_weighers = CapacityWeigher"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml27(td)
-msgid "(ListOpt) Which weigher class names to use for weighing hosts."
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml30(td)
-msgid "scheduler_driver = cinder.scheduler.filter_scheduler.FilterScheduler"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml31(td)
-msgid "(StrOpt) Default scheduler driver to use"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml34(td)
-msgid "scheduler_host_manager = cinder.scheduler.host_manager.HostManager"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml42(td)
-msgid "scheduler_manager = cinder.scheduler.manager.SchedulerManager"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml43(td)
-msgid "(StrOpt) full class name for the Manager for scheduler"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml47(td)
-msgid "(IntOpt) Maximum number of attempts to schedule an volume"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml50(td)
-msgid "scheduler_topic = cinder-scheduler"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml51(td)
-msgid "(StrOpt) the topic scheduler nodes listen on"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml22(td)
-msgid "admin_bind_host = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml23(td)
-msgid ""
-"(StrOpt) The IP Address of the network interface to for the admin service to"
-" listen on."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml26(td)
-msgid "admin_endpoint = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml27(td)
-msgid ""
-"(StrOpt) The base admin endpoint URL for keystone that are advertised to "
-"clients (NOTE: this does NOT affect how keystone listens for connections). "
-"Defaults to the base host URL of the request. Eg a request to "
-"http://server:35357/v2.0/users will default to http://server:35357. You "
-"should only need to set this value if the base URL contains a path (eg "
-"/prefix/v2.0) or the endpoint should be found on a different server."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml30(td)
-msgid "admin_port = 35357"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml31(td)
-msgid "(IntOpt) The port number which the admin service listens on."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml34(td)
-msgid "admin_token = ADMIN"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml35(td)
-msgid ""
-"(StrOpt) A \"shared secret\" that can be used to bootstrap Keystone. This "
-"\"token\" does not represent a user, and carries no explicit authorization. "
-"To disable in production (highly recommended), remove "
-"AdminTokenAuthMiddleware from your paste application pipelines (for example,"
-" in keystone-paste.ini)."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml38(td)
-msgid "compute_port = 8774"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml39(td)
-msgid "(IntOpt) The port which the OpenStack Compute service listens on."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml42(td)
-msgid "domain_id_immutable = True"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml43(td)
-msgid ""
-"(BoolOpt) Set this to false if you want to enable the ability for user, "
-"group and project entities to be moved between domains by updating their "
-"domain_id. Allowing such movement is not recommended if the scope of a "
-"domain admin is being restricted by use of an appropriate policy file (see "
-"policy.v3cloudsample as an example)."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml47(td)
-msgid ""
-"(IntOpt) The maximum number of entities that will be returned in a "
-"collection can be set with list_limit, with no limit set by default. This "
-"global limit may be then overridden for a specific driver, by specifying a "
-"list_limit in the appropriate section (e.g. [assignment])."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml50(td)
-msgid "max_param_size = 64"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml51(td)
-msgid "(IntOpt) limit the sizes of user &amp; tenant ID/names."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml55(td)
-msgid ""
-"(IntOpt) enforced by optional sizelimit middleware "
-"(keystone.middleware:RequestBodySizeLimiter)."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml58(td)
-msgid "max_token_size = 8192"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml59(td)
-msgid ""
-"(IntOpt) similar to max_param_size, but provides an exception for token "
-"values."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml62(td)
-msgid "member_role_id = 9fe2ff9ee4384b1894a90878d3e92bab"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml63(td)
-msgid ""
-"(StrOpt) During a SQL upgrade member_role_id will be used to create a new "
-"role that will replace records in the user_tenant_membership table with "
-"explicit role grants. After migration, the member_role_id will be used in "
-"the API add_user_to_project."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml66(td)
-msgid "member_role_name = _member_"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml67(td)
-msgid ""
-"(StrOpt) During a SQL upgrade member_role_id will be used to create a new "
-"role that will replace records in the user_tenant_membership table with "
-"explicit role grants. After migration, member_role_name will be ignored."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml70(td)
-msgid "public_bind_host = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml71(td)
-msgid ""
-"(StrOpt) The IP Address of the network interface to for the public service "
-"to listen on."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml74(td)
-msgid "public_endpoint = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml75(td)
-msgid ""
-"(StrOpt) The base public endpoint URL for keystone that are advertised to "
-"clients (NOTE: this does NOT affect how keystone listens for connections). "
-"Defaults to the base host URL of the request. Eg a request to "
-"http://server:5000/v2.0/users will default to http://server:5000. You should"
-" only need to set this value if the base URL contains a path (eg "
-"/prefix/v2.0) or the endpoint should be found on a different server."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml78(td)
-msgid "public_port = 5000"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml79(td)
-msgid "(IntOpt) The port number which the public service listens on."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml82(td)
-msgid "tcp_keepalive = False"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml83(td)
-msgid ""
-"(BoolOpt) Set this to True if you want to enable TCP_KEEPALIVE on server "
-"sockets i.e. sockets used by the keystone wsgi server for client "
-"connections."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml87(td)
-msgid ""
-"(IntOpt) Sets the value of TCP_KEEPIDLE in seconds for each server socket. "
-"Only applies if tcp_keepalive is True. Not supported on OS X."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml90(th)
-msgid "[endpoint_filter]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml93(td)
-msgid "driver = keystone.contrib.endpoint_filter.backends.sql.EndpointFilter"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml94(td)
-msgid "(StrOpt) Keystone Endpoint Filter backend driver"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml97(td)
-msgid "return_all_endpoints_if_no_filter = True"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml98(td)
-msgid "(BoolOpt) Toggle to return all active endpoints if no filter exists."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml104(td)
-msgid "config_file = keystone-paste.ini"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml105(td)
-msgid ""
-"(StrOpt) Name of the paste configuration file that defines the available "
-"pipelines."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ncs.xml8(caption)
-msgid "Description of configuration options for ml2_ncs"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ncs.xml19(th)
-msgid "[ml2_ncs]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ncs.xml31(td)
-msgid "(StrOpt) HTTP URL of Tail-f NCS REST interface."
-msgstr ""
+"logging_context_format_string = %(asctime)s.%(msecs)03d %(process)d "
+"%(levelname)s %(name)s [%(request_id)s %(user)s %(tenant)s] "
+"%(instance)s%(message)s"
+msgstr "logging_context_format_string = %(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [%(request_id)s %(user)s %(tenant)s] %(instance)s%(message)s"
 
 #: ./doc/common/tables/neutron-nec.xml8(caption)
 msgid "Description of configuration options for nec"
@@ -48340,26 +46863,209 @@ msgstr ""
 msgid "(StrOpt) Name of the FWaaS Driver"
 msgstr ""
 
-#: ./doc/common/tables/neutron-cadf.xml8(caption)
-msgid "Description of configuration options for cadf"
+#: ./doc/common/tables/keystone-security.xml8(caption)
+msgid "Description of configuration options for security"
 msgstr ""
 
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml7(literal)
-msgid "[object-expirer]"
+#: ./doc/common/tables/keystone-security.xml22(td)
+msgid "crypt_strength = 40000"
 msgstr ""
 
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml33(td)
-msgid "processes = 0"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml36(td)
-msgid "process = 0"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml36(td)
+#: ./doc/common/tables/keystone-security.xml23(td)
 msgid ""
-"(it will actually accept(2) N + 1). Setting this to one (1) will only handle"
-" one request at a time, without accepting another request concurrently."
+"(IntOpt) The value passed as the keyword \"rounds\" to passlib encrypt "
+"method."
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_neutron.xml8(caption)
+msgid "Description of configuration options for clients_neutron"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_neutron.xml19(th)
+msgid "[clients_neutron]"
+msgstr "[clients_neutron]"
+
+#: ./doc/common/tables/nova-api.xml22(td)
+msgid "api_rate_limit = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml23(td)
+msgid ""
+"(BoolOpt) Whether to use per-user rate limiting for the api. This option is "
+"only used by v2 api. Rate limiting is removed from v3 api."
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml30(td)
+msgid "enabled_apis = ec2, osapi_compute, metadata"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml31(td)
+msgid "(ListOpt) A list of APIs to enable by default"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml34(td)
+msgid "enabled_ssl_apis ="
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml35(td)
+msgid "(ListOpt) A list of APIs with enabled SSL"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml38(td)
+msgid "instance_name_template = instance-%08x"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml39(td)
+msgid "(StrOpt) Template string to be used to generate instance names"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml46(td)
+msgid "multi_instance_display_name_template = %(name)s-%(uuid)s"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml47(td)
+msgid ""
+"(StrOpt) When creating multiple instances with a single request using the "
+"os-multiple-create API extension, this template will be used to build the "
+"display name for each instance. The benefit is that the instances end up "
+"with different hostnames. To restore legacy behavior of every instance "
+"having the same name, set this option to \"%(name)s\". Valid keys for the "
+"template are: name, uuid, count."
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml50(td)
+msgid "non_inheritable_image_properties = cache_in_nova, bittorrent"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml51(td)
+msgid ""
+"(ListOpt) These are image properties which a snapshot should not inherit "
+"from an instance"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml54(td)
+msgid "null_kernel = nokernel"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml55(td)
+msgid ""
+"(StrOpt) Kernel image that indicates not to use a kernel, but to use a raw "
+"disk image instead"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml58(td)
+msgid "osapi_compute_ext_list ="
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml59(td)
+msgid ""
+"(ListOpt) Specify list of extensions to load when using "
+"osapi_compute_extension option with "
+"nova.api.openstack.compute.contrib.select_extensions"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml62(td)
+msgid ""
+"osapi_compute_extension = "
+"['nova.api.openstack.compute.contrib.standard_extensions']"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml63(td)
+msgid "(MultiStrOpt) osapi compute extension to load"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml66(td)
+msgid "osapi_compute_link_prefix = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml67(td)
+msgid ""
+"(StrOpt) Base URL that will be presented to users in links to the OpenStack "
+"Compute API"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml70(td)
+msgid "osapi_compute_listen = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml71(td)
+msgid "(StrOpt) The IP address on which the OpenStack API will listen."
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml74(td)
+msgid "osapi_compute_listen_port = 8774"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml75(td)
+msgid "(IntOpt) The port on which the OpenStack API will listen."
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml78(td)
+msgid "osapi_compute_workers = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml79(td)
+msgid ""
+"(IntOpt) Number of workers for OpenStack API service. The default will be "
+"the number of CPUs available."
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml82(td)
+msgid "osapi_hide_server_address_states = building"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml83(td)
+msgid "(ListOpt) List of instance states that should hide network info"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml86(td)
+msgid "servicegroup_driver = db"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml87(td)
+msgid ""
+"(StrOpt) The driver for servicegroup service (valid options are: db, zk, mc)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_mlnx.xml8(caption)
+msgid "Description of configuration options for ml2_mlnx"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_mlnx.xml22(td)
+msgid "apply_profile_patch = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_mlnx.xml23(td)
+msgid "(BoolOpt) Enable server compatibility with old nova"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_mlnx.xml26(td)
+msgid "vnic_type = mlnx_direct"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_mlnx.xml27(td)
+msgid "(StrOpt) Type of VM network interface: mlnx_direct or hostdev"
+msgstr ""
+
+#: ./doc/common/tables/keystone-trust.xml8(caption)
+msgid "Description of configuration options for trust"
+msgstr ""
+
+#: ./doc/common/tables/keystone-trust.xml19(th)
+msgid "[trust]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-trust.xml22(td)
+msgid "driver = keystone.trust.backends.sql.Trust"
+msgstr ""
+
+#: ./doc/common/tables/keystone-trust.xml23(td)
+msgid "(StrOpt) Keystone Trust backend driver."
+msgstr ""
+
+#: ./doc/common/tables/keystone-trust.xml27(td)
+msgid ""
+"(BoolOpt) delegation and impersonation features can be optionally disabled."
 msgstr ""
 
 #: ./doc/common/tables/glance-cinder.xml8(caption)
@@ -48392,477 +47098,760 @@ msgstr ""
 msgid "(IntOpt) Number of cinderclient retries on failed http calls."
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane.xml8(caption)
-msgid "Description of configuration options for embrane"
+#: ./doc/common/tables/swift-object-server-object-updater.xml7(literal)
+msgid "[object-updater]"
+msgstr "[object-updater]"
+
+#: ./doc/common/tables/swift-object-server-object-updater.xml18(td)
+msgid "log_name = object-updater"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane.xml22(td)
-msgid "admin_username = admin"
-msgstr ""
+#: ./doc/common/tables/glance-common.xml22(td)
+msgid "allow_additional_image_properties = True"
+msgstr "allow_additional_image_properties = True"
 
-#: ./doc/common/tables/neutron-embrane.xml26(td)
-msgid "async_requests = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane.xml31(td)
-msgid "(StrOpt) Dummy user traffic Security Zone id"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane.xml39(td)
-msgid "(StrOpt) In band Security Zone id"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane.xml43(td)
-msgid "(StrOpt) Management Security Zone id"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane.xml47(td)
-msgid "(StrOpt) Out of band Security Zone id"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane.xml50(td)
-msgid "resource_pool_id = default"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane.xml54(td)
-msgid "router_image = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane.xml55(td)
-msgid "(StrOpt) Router image id (Embrane FW/VPN)"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml18(td)
+#: ./doc/common/tables/glance-common.xml23(td)
 msgid ""
-"pipeline = catch_errors gatekeeper healthcheck proxy-logging cache "
-"container_sync bulk tempurl slo dlo ratelimit tempauth container-quotas "
-"account-quotas proxy-logging proxy-server"
+"(BoolOpt) Whether to allow users to specify image properties beyond what the"
+" image schema provides"
 msgstr ""
 
-#: ./doc/common/tables/nova-upgrade_levels.xml8(caption)
-msgid "Description of configuration options for upgrade_levels"
-msgstr ""
+#: ./doc/common/tables/glance-common.xml26(td)
+msgid "api_limit_max = 1000"
+msgstr "api_limit_max = 1000"
 
-#: ./doc/common/tables/nova-upgrade_levels.xml22(td)
-msgid "scheduler = nova.cells.scheduler.CellsScheduler"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml23(td)
-msgid "(StrOpt) Cells scheduler to use"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml29(td)
-msgid "cells = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml30(td)
-msgid "(StrOpt) Set a version cap for messages sent to local cells services"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml33(td)
-msgid "cert = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml34(td)
-msgid "(StrOpt) Set a version cap for messages sent to cert services"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml37(td)
-msgid "compute = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml38(td)
+#: ./doc/common/tables/glance-common.xml27(td)
 msgid ""
-"(StrOpt) Set a version cap for messages sent to compute services. If you "
-"plan to do a live upgrade from havana to icehouse, you should set this "
-"option to \"icehouse-compat\" before beginning the live upgrade procedure."
+"(IntOpt) Maximum permissible number of items that could be returned by a "
+"request"
 msgstr ""
 
-#: ./doc/common/tables/nova-upgrade_levels.xml41(td)
-msgid "conductor = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml42(td)
-msgid "(StrOpt) Set a version cap for messages sent to conductor services"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml45(td)
-msgid "console = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml46(td)
-msgid "(StrOpt) Set a version cap for messages sent to console services"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml49(td)
-msgid "consoleauth = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml50(td)
-msgid "(StrOpt) Set a version cap for messages sent to consoleauth services"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml53(td)
-msgid "intercell = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml54(td)
-msgid "(StrOpt) Set a version cap for messages sent between cells services"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml57(td)
-msgid "network = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml58(td)
-msgid "(StrOpt) Set a version cap for messages sent to network services"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml61(td)
-msgid "scheduler = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml62(td)
-msgid "(StrOpt) Set a version cap for messages sent to scheduler services"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml7(literal)
-msgid "[filter:cname_lookup]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml18(td)
-msgid "use = egg:swift#cname_lookup"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml21(td)
-msgid "set log_name = cname_lookup"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml36(td)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml36(td)
-msgid "storage_domain = example.com"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml36(td)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml36(td)
+#: ./doc/common/tables/glance-common.xml31(td)
 msgid ""
-"Domain that matches your cloud. Multiple domains can be specified using a "
-"comma-separated list."
+"(IntOpt) The backlog value that will be used when creating the TCP listener "
+"socket."
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml40(td)
-msgid "lookup_depth = 1"
+#: ./doc/common/tables/glance-common.xml38(td)
+msgid "bind_port = None"
+msgstr "bind_port = None"
+
+#: ./doc/common/tables/glance-common.xml42(td)
+msgid "data_api = glance.db.sqlalchemy.api"
+msgstr "data_api = glance.db.sqlalchemy.api"
+
+#: ./doc/common/tables/glance-common.xml43(td)
+msgid "(StrOpt) Python module path of data access API"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml40(td)
+#: ./doc/common/tables/glance-common.xml50(td)
+msgid "image_location_quota = 10"
+msgstr "image_location_quota = 10"
+
+#: ./doc/common/tables/glance-common.xml51(td)
 msgid ""
-"Because CNAMES can be recursive, specifies the number of levels through "
-"which to search."
+"(IntOpt) Maximum number of locations allowed on an image. Negative values "
+"evaluate to unlimited."
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-inspector.xml8(caption)
-msgid "Description of configuration options for inspector"
-msgstr ""
+#: ./doc/common/tables/glance-common.xml54(td)
+msgid "image_member_quota = 128"
+msgstr "image_member_quota = 128"
 
-#: ./doc/common/tables/ceilometer-inspector.xml22(td)
-msgid "hypervisor_inspector = libvirt"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-inspector.xml23(td)
-msgid "(StrOpt) Inspector to use for inspecting the hypervisor layer."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-inspector.xml26(td)
-msgid "libvirt_type = kvm"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-inspector.xml27(td)
+#: ./doc/common/tables/glance-common.xml55(td)
 msgid ""
-"(StrOpt) Libvirt domain type (valid options are: kvm, lxc, qemu, uml, xen)."
+"(IntOpt) Maximum number of image members per image. Negative values evaluate"
+" to unlimited."
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-inspector.xml30(td)
-msgid "libvirt_uri ="
-msgstr ""
+#: ./doc/common/tables/glance-common.xml58(td)
+msgid "image_property_quota = 128"
+msgstr "image_property_quota = 128"
 
-#: ./doc/common/tables/ceilometer-inspector.xml31(td)
+#: ./doc/common/tables/glance-common.xml59(td)
 msgid ""
-"(StrOpt) Override the default libvirt URI (which is dependent on "
-"libvirt_type)."
+"(IntOpt) Maximum number of properties allowed on an image. Negative values "
+"evaluate to unlimited."
 msgstr ""
 
-#: ./doc/common/tables/heat-common.xml22(td)
-msgid "deferred_auth_method = password"
-msgstr "deferred_auth_method = password"
+#: ./doc/common/tables/glance-common.xml62(td)
+msgid "image_tag_quota = 128"
+msgstr "image_tag_quota = 128"
 
-#: ./doc/common/tables/heat-common.xml23(td)
-msgid "(StrOpt) Select deferred auth method, stored password or trusts."
-msgstr ""
-
-#: ./doc/common/tables/heat-common.xml26(td)
-msgid "environment_dir = /etc/heat/environment.d"
-msgstr "environment_dir = /etc/heat/environment.d"
-
-#: ./doc/common/tables/heat-common.xml27(td)
-msgid "(StrOpt) The directory to search for environment files."
-msgstr ""
-
-#: ./doc/common/tables/heat-common.xml30(td)
-msgid "event_purge_batch_size = 10"
-msgstr "event_purge_batch_size = 10"
-
-#: ./doc/common/tables/heat-common.xml31(td)
+#: ./doc/common/tables/glance-common.xml63(td)
 msgid ""
-"(IntOpt) Controls how many events will be pruned whenever a stack's events "
-"exceed max_events_per_stack. Set this lower to keep more events at the "
-"expense of more frequent purges."
+"(IntOpt) Maximum number of tags allowed on an image. Negative values "
+"evaluate to unlimited."
 msgstr ""
 
-#: ./doc/common/tables/heat-common.xml34(td)
-msgid "instance_driver = heat.engine.nova"
-msgstr "instance_driver = heat.engine.nova"
+#: ./doc/common/tables/glance-common.xml66(td)
+msgid "limit_param_default = 25"
+msgstr "limit_param_default = 25"
 
-#: ./doc/common/tables/heat-common.xml35(td)
-msgid "(StrOpt) Driver to use for controlling instances."
-msgstr ""
-
-#: ./doc/common/tables/heat-common.xml38(td)
-msgid "instance_user = ec2-user"
-msgstr "instance_user = ec2-user"
-
-#: ./doc/common/tables/heat-common.xml39(td)
+#: ./doc/common/tables/glance-common.xml67(td)
 msgid ""
-"(StrOpt) The default user for new instances. This option is deprecated and "
-"will be removed in the Juno release. If it's empty, Heat will use the "
-"default user set up with your cloud image (for OS::Nova::Server) or "
-"'ec2-user' (for AWS::EC2::Instance)."
+"(IntOpt) Default value for the number of items returned by a request if not "
+"specified explicitly in the request"
 msgstr ""
 
-#: ./doc/common/tables/heat-common.xml42(td)
-msgid "keystone_backend = heat.common.heat_keystoneclient.KeystoneClientV3"
-msgstr "keystone_backend = heat.common.heat_keystoneclient.KeystoneClientV3"
-
-#: ./doc/common/tables/heat-common.xml43(td)
-msgid "(StrOpt) Fully qualified class name to use as a keystone backend."
+#: ./doc/common/tables/glance-common.xml74(td)
+msgid "metadata_encryption_key = None"
 msgstr ""
 
-#: ./doc/common/tables/heat-common.xml47(td)
-msgid "(IntOpt) Seconds between running periodic tasks."
-msgstr ""
-
-#: ./doc/common/tables/heat-common.xml50(td)
-msgid "plugin_dirs = /usr/lib64/heat, /usr/lib/heat"
-msgstr "plugin_dirs = /usr/lib64/heat, /usr/lib/heat"
-
-#: ./doc/common/tables/heat-common.xml51(td)
-msgid "(ListOpt) List of directories to search for plug-ins."
-msgstr ""
-
-#: ./doc/common/tables/heat-common.xml54(th)
-msgid "[revision]"
-msgstr "[revision]"
-
-#: ./doc/common/tables/heat-common.xml57(td)
-msgid "heat_revision = unknown"
-msgstr "heat_revision = unknown"
-
-#: ./doc/common/tables/heat-common.xml58(td)
+#: ./doc/common/tables/glance-common.xml75(td)
 msgid ""
-"(StrOpt) Heat build revision. If you would prefer to manage your build "
-"revision separately, you can move this section to a different file and add "
-"it as another config option."
+"(StrOpt) Key used for encrypting sensitive metadata while talking to the "
+"registry or database."
 msgstr ""
 
-#: ./doc/common/tables/keystone-federation.xml8(caption)
-msgid "Description of configuration options for federation"
+#: ./doc/common/tables/glance-common.xml78(td)
+msgid "notifier_strategy = default"
 msgstr ""
 
-#: ./doc/common/tables/keystone-federation.xml19(th)
-msgid "[federation]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-federation.xml22(td)
-msgid "assertion_prefix ="
-msgstr ""
-
-#: ./doc/common/tables/keystone-federation.xml23(td)
+#: ./doc/common/tables/glance-common.xml79(td)
 msgid ""
-"(StrOpt) Value to be used when filtering assertion parameters from the "
-"environment."
+"(StrOpt) Notifications can be sent when images are create, updated or "
+"deleted. There are three methods of sending notifications, logging (via the "
+"log_file directive), rabbit (via a rabbitmq queue), qpid (via a Qpid message"
+" queue), or noop (no notifications sent, the default). (DEPRECATED)"
 msgstr ""
 
-#: ./doc/common/tables/keystone-federation.xml26(td)
-msgid "driver = keystone.contrib.federation.backends.sql.Federation"
+#: ./doc/common/tables/glance-common.xml83(td)
+msgid "(StrOpt) Region name of this node."
 msgstr ""
 
-#: ./doc/common/tables/keystone-federation.xml27(td)
-msgid "(StrOpt) Keystone Federation backend driver."
+#: ./doc/common/tables/glance-common.xml86(td)
+msgid "property_protection_file = None"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zadara.xml8(caption)
-msgid "Description of configuration options for zadara"
+#: ./doc/common/tables/glance-common.xml87(td)
+msgid "(StrOpt) The location of the property protection file."
 msgstr ""
 
-#: ./doc/common/tables/cinder-zadara.xml22(td)
-msgid "zadara_password = None"
+#: ./doc/common/tables/glance-common.xml90(td)
+msgid "property_protection_rule_format = roles"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zadara.xml23(td)
-msgid "(StrOpt) Password for the VPSA"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml26(td)
-msgid "zadara_user = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml27(td)
-msgid "(StrOpt) User name for the VPSA"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml30(td)
-msgid "zadara_vol_encrypt = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml31(td)
-msgid "(BoolOpt) Default encryption policy for volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml34(td)
-msgid "zadara_vol_name_template = OS_%s"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml35(td)
-msgid "(StrOpt) Default template for VPSA volume names"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml38(td)
-msgid "zadara_vol_thin = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml39(td)
-msgid "(BoolOpt) Default thin provisioning policy for volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml42(td)
-msgid "zadara_vpsa_allow_nonexistent_delete = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml43(td)
-msgid "(BoolOpt) Don't halt on deletion of non-existing volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml46(td)
-msgid "zadara_vpsa_auto_detach_on_delete = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml47(td)
-msgid "(BoolOpt) Automatically detach from servers on volume delete"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml50(td)
-msgid "zadara_vpsa_ip = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml51(td)
-msgid "(StrOpt) Management IP of Zadara VPSA"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml54(td)
-msgid "zadara_vpsa_poolname = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml55(td)
-msgid "(StrOpt) Name of VPSA storage pool for volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml58(td)
-msgid "zadara_vpsa_port = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml59(td)
-msgid "(StrOpt) Zadara VPSA port number"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml62(td)
-msgid "zadara_vpsa_use_ssl = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml63(td)
-msgid "(BoolOpt) Use SSL connection"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml8(caption)
-msgid "Description of configuration options for nuage"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml22(td)
-msgid "auth_resource ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml23(td)
-msgid "(StrOpt) Nuage provided uri for initial authorization to access VSD"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml26(td)
-msgid "base_uri = /"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml27(td)
-msgid "(StrOpt) Nuage provided base uri to reach out to VSD"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml30(td)
-msgid "default_floatingip_quota = 254"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml31(td)
-msgid "(IntOpt) Per Net Partition quota of floating ips"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml34(td)
-msgid "default_net_partition_name = OpenStackDefaultNetPartition"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml35(td)
+#: ./doc/common/tables/glance-common.xml91(td)
 msgid ""
-"(StrOpt) Default Network partition in which VSD will orchestrate network "
-"resources using openstack"
+"(StrOpt) This config value indicates whether \"roles\" or \"policies\" are "
+"used in the property protection file."
 msgstr ""
 
-#: ./doc/common/tables/neutron-nuage.xml38(td)
-msgid "organization = system"
+#: ./doc/common/tables/glance-common.xml94(td)
+msgid "show_image_direct_url = False"
 msgstr ""
 
-#: ./doc/common/tables/neutron-nuage.xml39(td)
+#: ./doc/common/tables/glance-common.xml95(td)
 msgid ""
-"(StrOpt) Organization name in which VSD will orchestrate network resources "
-"using openstack"
+"(BoolOpt) Whether to include the backend image storage location in image "
+"properties. Revealing storage location can be a security risk, so use this "
+"setting with caution!"
 msgstr ""
 
-#: ./doc/common/tables/neutron-nuage.xml42(td)
-msgid "server = localhost:8800"
+#: ./doc/common/tables/glance-common.xml98(td)
+msgid "user_storage_quota = 0"
 msgstr ""
 
-#: ./doc/common/tables/neutron-nuage.xml43(td)
-msgid "(StrOpt) IP Address and Port of Nuage's VSD server"
+#: ./doc/common/tables/glance-common.xml99(td)
+msgid ""
+"(IntOpt) Set a system wide quota for every user. This value is the total "
+"number of bytes that a user can use across all storage systems. A value of 0"
+" means unlimited."
 msgstr ""
 
-#: ./doc/common/tables/neutron-nuage.xml46(td)
-msgid "serverauth = username:password"
+#: ./doc/common/tables/glance-common.xml102(td)
+msgid "workers = 1"
 msgstr ""
 
-#: ./doc/common/tables/neutron-nuage.xml47(td)
-msgid "(StrOpt) Username and password for authentication"
+#: ./doc/common/tables/glance-common.xml103(td)
+msgid ""
+"(IntOpt) The number of child process workers that will be created to service"
+" API requests."
 msgstr ""
 
-#: ./doc/common/tables/neutron-nuage.xml50(td)
-msgid "serverssl = False"
+#: ./doc/common/tables/glance-common.xml106(th)
+msgid "[image_format]"
 msgstr ""
 
-#: ./doc/common/tables/neutron-nuage.xml51(td)
-msgid "(BoolOpt) Boolean for SSL connection with VSD server"
+#: ./doc/common/tables/glance-common.xml109(td)
+msgid "container_formats = ami, ari, aki, bare, ovf, ova"
 msgstr ""
 
+#: ./doc/common/tables/glance-common.xml110(td)
+msgid "(ListOpt) Supported values for the 'container_format' image attribute"
+msgstr ""
+
+#: ./doc/common/tables/glance-common.xml113(td)
+msgid "disk_formats = ami, ari, aki, vhd, vmdk, raw, qcow2, vdi, iso"
+msgstr ""
+
+#: ./doc/common/tables/glance-common.xml114(td)
+msgid "(ListOpt) Supported values for the 'disk_format' image attribute"
+msgstr ""
+
+#: ./doc/common/tables/glance-common.xml117(th)
+msgid "[task]"
+msgstr ""
+
+#: ./doc/common/tables/glance-common.xml120(td)
+msgid "task_time_to_live = 48"
+msgstr ""
+
+#: ./doc/common/tables/glance-common.xml121(td)
+msgid ""
+"(IntOpt) Time in hours for which a task lives after, either succeeding or "
+"failing"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_vxlan.xml8(caption)
+msgid "Description of configuration options for ml2_vxlan"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_vxlan.xml19(th)
+msgid "[ml2_type_vxlan]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_vxlan.xml22(td)
+msgid "vni_ranges ="
+msgstr "vni_ranges ="
+
+#: ./doc/common/tables/neutron-ml2_vxlan.xml23(td)
+msgid ""
+"(ListOpt) Comma-separated list of &lt;vni_min&gt;:&lt;vni_max&gt; tuples "
+"enumerating ranges of VXLAN VNI IDs that are available for tenant network "
+"allocation"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_vxlan.xml26(td)
+msgid "vxlan_group = None"
+msgstr "vxlan_group = None"
+
+#: ./doc/common/tables/neutron-ml2_vxlan.xml27(td)
+msgid ""
+"(StrOpt) Multicast group for VXLAN. If unset, disables VXLAN multicast mode."
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml7(literal)
+msgid "[dispersion]"
+msgstr "[dispersion]"
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml7(literal)
+msgid "dispersion.conf-sample"
+msgstr "dispersion.conf-sample"
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml18(td)
+msgid "auth_url = http://localhost:8080/auth/v1.0"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml18(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml27(td)
+msgid "Endpoint for auth server, such as keystone"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml21(td)
+msgid "auth_user = test:tester"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml21(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml30(td)
+msgid "Default user for dispersion in this context"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml24(td)
+msgid "auth_key = testing"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml27(td)
+msgid "auth_url = http://localhost:5000/v2.0/"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml30(td)
+msgid "auth_user = tenant:user"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml33(td)
+msgid "auth_key = password"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml36(td)
+msgid "auth_version = 2.0"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml36(td)
+msgid "Indicates which version of auth"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml39(td)
+msgid "Indicates whether endpoint for auth is public or internal"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml42(td)
+msgid "keystone_api_insecure = no"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml48(td)
+msgid "dispersion_coverage = 1.0"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml51(td)
+msgid "retries = 5"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml54(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml30(td)
+msgid "concurrency = 25"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml57(td)
+msgid "container_populate = yes"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml60(td)
+msgid "object_populate = yes"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml63(td)
+msgid "container_report = yes"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml66(td)
+msgid "object_report = yes"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml69(td)
+msgid "dump_json = no"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml21(td)
+msgid "bind_port = 6002"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml7(literal)
+msgid "[filter:domain_remap]"
+msgstr "[filter:domain_remap]"
+
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml18(td)
+msgid "use = egg:swift#domain_remap"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml21(td)
+msgid "set log_name = domain_remap"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml40(td)
+msgid "path_root = v1"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml40(td)
+msgid "Root path"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml43(td)
+msgid "reseller_prefixes = AUTH"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml43(td)
+msgid "Reseller prefix"
+msgstr ""
+
+#: ./doc/common/tables/trove-nova.xml8(caption)
+msgid "Description of configuration options for nova"
+msgstr ""
+
+#: ./doc/common/tables/trove-nova.xml22(td)
+msgid "nova_proxy_admin_pass ="
+msgstr "nova_proxy_admin_pass ="
+
+#: ./doc/common/tables/trove-nova.xml23(td)
+msgid "(StrOpt) Admin password used to connect to nova,"
+msgstr ""
+
+#: ./doc/common/tables/trove-nova.xml26(td)
+msgid "nova_proxy_admin_tenant_name ="
+msgstr "nova_proxy_admin_tenant_name ="
+
+#: ./doc/common/tables/trove-nova.xml27(td)
+msgid "(StrOpt) Admin tenant used to connect to nova."
+msgstr ""
+
+#: ./doc/common/tables/trove-nova.xml30(td)
+msgid "nova_proxy_admin_user ="
+msgstr "nova_proxy_admin_user ="
+
+#: ./doc/common/tables/trove-nova.xml31(td)
+msgid "(StrOpt) Admin username used to connect to nova."
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml8(caption)
+msgid "Description of configuration options for meta"
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml19(th)
+msgid "[META]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml22(td)
+msgid "default_flavor ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml23(td)
+msgid "(StrOpt) Default flavor to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml26(td)
+msgid "default_l3_flavor ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml27(td)
+msgid "(StrOpt) Default L3 flavor to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml30(td)
+msgid "extension_map ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml31(td)
+msgid "(StrOpt) A list of extensions, per plugin, to load."
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml34(td)
+msgid "l3_plugin_list ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml35(td)
+msgid "(StrOpt) List of L3 plugins to load"
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml38(td)
+msgid "plugin_list ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml39(td)
+msgid "(StrOpt) List of plugins to load"
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml42(td)
+msgid "rpc_flavor ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml43(td)
+msgid "(StrOpt) Flavor of which plugin handles RPC"
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml46(td)
+msgid "supported_extension_aliases ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml47(td)
+msgid "(StrOpt) Supported extension aliases"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rabbitmq.xml35(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml55(td)
+msgid ""
+"(IntOpt) Maximum number of RabbitMQ connection retries. Default is 0 "
+"(infinite retry count)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rabbitmq.xml39(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml59(td)
+msgid "(StrOpt) The RabbitMQ password"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rabbitmq.xml47(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml67(td)
+msgid ""
+"(IntOpt) How long to backoff for between retries when connecting to RabbitMQ"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rabbitmq.xml51(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml71(td)
+msgid "(IntOpt) How frequently to retry connecting with RabbitMQ"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rabbitmq.xml55(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml75(td)
+msgid "(BoolOpt) Connect over SSL for RabbitMQ"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rabbitmq.xml59(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml79(td)
+msgid "(StrOpt) The RabbitMQ userid"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rabbitmq.xml63(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml83(td)
+msgid "(StrOpt) The RabbitMQ virtual host"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml22(td)
+msgid "keystone_ec2_cafile = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml23(td)
+msgid ""
+"(StrOpt) A PEM encoded certificate authority to use when verifying HTTPS "
+"connections. Defaults to the system CAs."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml26(td)
+msgid "keystone_ec2_certfile = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml27(td)
+msgid ""
+"(StrOpt) Client certificate key filename. Required if EC2 server requires "
+"client certificate."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml30(td)
+msgid "keystone_ec2_insecure = False"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml31(td)
+msgid "(BoolOpt) Disable SSL certificate verification."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml34(td)
+msgid "keystone_ec2_keyfile = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml35(td)
+msgid "(StrOpt) Required if EC2 server requires client certificate."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml42(th)
+msgid "[ec2]"
+msgstr "[ec2]"
+
+#: ./doc/common/tables/keystone-ec2.xml45(td)
+msgid "driver = keystone.contrib.ec2.backends.kvs.Ec2"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml46(td)
+msgid "(StrOpt) Keystone EC2Credential backend driver."
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_keystone.xml8(caption)
+msgid "Description of configuration options for clients_keystone"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_keystone.xml19(th)
+msgid "[clients_keystone]"
+msgstr "[clients_keystone]"
+
+#: ./doc/common/tables/neutron-api.xml22(td)
+msgid "allow_bulk = True"
+msgstr "allow_bulk = True"
+
+#: ./doc/common/tables/neutron-api.xml23(td)
+msgid "(BoolOpt) Allow the usage of the bulk API"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml26(td)
+msgid "allow_pagination = False"
+msgstr "allow_pagination = False"
+
+#: ./doc/common/tables/neutron-api.xml27(td)
+msgid "(BoolOpt) Allow the usage of the pagination"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml30(td)
+msgid "allow_sorting = False"
+msgstr "allow_sorting = False"
+
+#: ./doc/common/tables/neutron-api.xml31(td)
+msgid "(BoolOpt) Allow the usage of the sorting"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml34(td)
+msgid "api_extensions_path ="
+msgstr "api_extensions_path ="
+
+#: ./doc/common/tables/neutron-api.xml35(td)
+msgid "(StrOpt) The path for API extensions"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml39(td)
+msgid "(StrOpt) The API paste config file to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml43(td)
+msgid "(IntOpt) Max header line to accommodate large tokens"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml47(td)
+msgid "(IntOpt) the maximum body size per each request(bytes)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml50(td)
+msgid "pagination_max_limit = -1"
+msgstr "pagination_max_limit = -1"
+
+#: ./doc/common/tables/neutron-api.xml51(td)
+msgid ""
+"(StrOpt) The maximum number of items returned in a single response, value "
+"was 'infinite' or negative integer means no limit"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml58(td)
+msgid "service_plugins ="
+msgstr "service_plugins ="
+
+#: ./doc/common/tables/neutron-api.xml59(td)
+msgid "(ListOpt) The service plugins Neutron will use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml62(th)
+msgid "[service_providers]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml65(td)
+msgid "service_provider = []"
+msgstr "service_provider = []"
+
+#: ./doc/common/tables/neutron-api.xml66(td)
+msgid ""
+"(MultiStrOpt) Defines providers for advanced services using the format: "
+"&lt;service_type&gt;:&lt;name&gt;:&lt;driver&gt;[:default]"
+msgstr ""
+
+#: ./doc/common/tables/trove-logging.xml22(td)
+msgid "format_options = -m 5"
+msgstr "format_options = -m 5"
+
+#: ./doc/common/tables/trove-logging.xml70(td)
+msgid "network_label_regex = ^private$"
+msgstr "network_label_regex = ^private$"
+
+#: ./doc/common/tables/glance-db.xml74(td)
+#: ./doc/common/tables/keystone-database.xml74(td)
+msgid "mysql_sql_mode = TRADITIONAL"
+msgstr ""
+
+#: ./doc/common/tables/glance-db.xml75(td)
+#: ./doc/common/tables/keystone-database.xml75(td)
+msgid ""
+"(StrOpt) The SQL mode to be used for MySQL sessions. This option, including "
+"the default, overrides any server-set SQL mode. To use whatever SQL mode is "
+"set by the server configuration, set this to no value. Example: "
+"mysql_sql_mode="
+msgstr ""
+
+#: ./doc/common/tables/glance-db.xml86(td)
+msgid "sqlite_db = glance.sqlite"
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml8(caption)
+msgid "Description of configuration options for kvs"
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml19(th)
+msgid "[kvs]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml22(td)
+msgid "backends ="
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml23(td)
+msgid ""
+"(ListOpt) Extra dogpile.cache backend modules to register with the "
+"dogpile.cache library."
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml26(td)
+msgid "config_prefix = keystone.kvs"
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml27(td)
+msgid ""
+"(StrOpt) Prefix for building the configuration dictionary for the KVS "
+"region. This should not need to be changed unless there is another "
+"dogpile.cache region with the same configuration name."
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml30(td)
+msgid "default_lock_timeout = 5"
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml31(td)
+msgid "(IntOpt) Default lock timeout for distributed locking."
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml34(td)
+msgid "enable_key_mangler = True"
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml35(td)
+msgid ""
+"(BoolOpt) Toggle to disable using a key-mangling function to ensure fixed "
+"length keys. This is toggle-able for debugging purposes, it is highly "
+"recommended to always leave this set to True."
+msgstr ""
+
+#: ./doc/common/tables/nova-xvpnvncproxy.xml8(caption)
+msgid "Description of configuration options for xvpnvncproxy"
+msgstr ""
+
+#: ./doc/common/tables/nova-xvpnvncproxy.xml22(td)
+msgid "xvpvncproxy_base_url = http://127.0.0.1:6081/console"
+msgstr ""
+
+#: ./doc/common/tables/nova-xvpnvncproxy.xml23(td)
+msgid ""
+"(StrOpt) Location of nova xvp VNC console proxy, in the form "
+"\"http://127.0.0.1:6081/console\""
+msgstr ""
+
+#: ./doc/common/tables/nova-xvpnvncproxy.xml26(td)
+msgid "xvpvncproxy_host = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-xvpnvncproxy.xml27(td)
+msgid "(StrOpt) Address that the XCP VNC proxy should bind to"
+msgstr ""
+
+#: ./doc/common/tables/nova-xvpnvncproxy.xml30(td)
+msgid "xvpvncproxy_port = 6081"
+msgstr ""
+
+#: ./doc/common/tables/nova-xvpnvncproxy.xml31(td)
+msgid "(IntOpt) Port that the XCP VNC proxy should bind to"
+msgstr ""
+
+#: ./doc/common/tables/glance-paste.xml8(caption)
+msgid "Description of configuration options for paste"
+msgstr ""
+
+#: ./doc/common/tables/glance-paste.xml22(td)
+msgid "config_file = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-paste.xml23(td)
+msgid "(StrOpt) Name of the paste configuration file."
+msgstr ""
+
+#: ./doc/common/tables/glance-paste.xml27(td)
+msgid ""
+"(StrOpt) Partial name of a pipeline in your paste configuration file with "
+"the service name removed. For example, if your paste section name is "
+"[pipeline:glance-api-keystone] use the value \"keystone\""
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml7(literal)
+msgid "[filter:list-endpoints]"
+msgstr "[filter:list-endpoints]"
+
+#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml18(td)
+msgid "use = egg:swift#list_endpoints"
+msgstr "use = egg:swift#list_endpoints"
+
+#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml21(td)
+msgid "list_endpoints_path = /endpoints/"
+msgstr "list_endpoints_path = /endpoints/"
+
 #: ./doc/common/tables/swift-account-server-account-reaper.xml7(literal)
 msgid "[account-reaper]"
 msgstr "[account-reaper]"
@@ -48895,599 +47884,1621 @@ msgstr ""
 msgid "reap_warn_after = 2592000"
 msgstr ""
 
-#: ./doc/common/tables/nova-quota.xml22(td)
-msgid "bandwidth_poll_interval = 600"
+#: ./doc/common/tables/nova-hyperv.xml8(caption)
+msgid "Description of configuration options for hyperv"
 msgstr ""
 
-#: ./doc/common/tables/nova-quota.xml23(td)
+#: ./doc/common/tables/nova-hyperv.xml22(td)
+msgid "dynamic_memory_ratio = 1.0"
+msgstr "dynamic_memory_ratio = 1.0"
+
+#: ./doc/common/tables/nova-hyperv.xml23(td)
 msgid ""
-"(IntOpt) Interval to pull network bandwidth usage info. Not supported on all"
-" hypervisors. Set to 0 to disable."
+"(FloatOpt) Enables dynamic memory allocation (ballooning) when set to a "
+"value greater than 1. The value expresses the ratio between the total RAM "
+"assigned to an instance and its startup RAM amount. For example a ratio of "
+"2.0 for an instance with 1024MB of RAM implies 512MB of RAM allocated at "
+"startup"
 msgstr ""
 
-#: ./doc/common/tables/nova-quota.xml26(td)
-msgid "enable_network_quota = False"
-msgstr ""
+#: ./doc/common/tables/nova-hyperv.xml26(td)
+msgid "enable_instance_metrics_collection = False"
+msgstr "enable_instance_metrics_collection = False"
 
-#: ./doc/common/tables/nova-quota.xml27(td)
-msgid "(BoolOpt) Enables or disables quota checking for tenant networks"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml30(td)
-msgid "quota_cores = 20"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml31(td)
-msgid "(IntOpt) Number of instance cores allowed per project"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml34(td)
-msgid "quota_driver = nova.quota.DbQuotaDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml38(td)
-msgid "quota_fixed_ips = -1"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml39(td)
+#: ./doc/common/tables/nova-hyperv.xml27(td)
 msgid ""
-"(IntOpt) Number of fixed IPs allowed per project (this should be at least "
-"the number of instances allowed)"
+"(BoolOpt) Enables metrics collections for an instance by using Hyper-V's "
+"metric APIs. Collected data can by retrieved by other apps and services, "
+"e.g.: Ceilometer. Requires Hyper-V / Windows Server 2012 and above"
 msgstr ""
 
-#: ./doc/common/tables/nova-quota.xml42(td)
-msgid "quota_floating_ips = 10"
-msgstr ""
+#: ./doc/common/tables/nova-hyperv.xml34(td)
+msgid "instances_path_share ="
+msgstr "instances_path_share ="
 
-#: ./doc/common/tables/nova-quota.xml43(td)
-msgid "(IntOpt) Number of floating IPs allowed per project"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml46(td)
-msgid "quota_injected_file_content_bytes = 10240"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml47(td)
-msgid "(IntOpt) Number of bytes allowed per injected file"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml50(td)
-msgid "quota_injected_file_path_bytes = 255"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml51(td)
-msgid "(IntOpt) Number of bytes allowed per injected file path"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml54(td)
-msgid "quota_injected_files = 5"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml55(td)
-msgid "(IntOpt) Number of injected files allowed"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml58(td)
-msgid "quota_instances = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml59(td)
-msgid "(IntOpt) Number of instances allowed per project"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml62(td)
-msgid "quota_key_pairs = 100"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml63(td)
-msgid "(IntOpt) Number of key pairs per user"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml66(td)
-msgid "quota_metadata_items = 128"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml67(td)
-msgid "(IntOpt) Number of metadata items allowed per instance"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml70(td)
-msgid "quota_ram = 51200"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml71(td)
-msgid "(IntOpt) Megabytes of instance RAM allowed per project"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml74(td)
-msgid "quota_security_group_rules = 20"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml75(td)
-msgid "(IntOpt) Number of security rules per security group"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml78(td)
-msgid "quota_security_groups = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml79(td)
-msgid "(IntOpt) Number of security groups per project"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml8(caption)
-msgid "Description of configuration options for conductor"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml22(td)
-msgid "migrate_max_retries = -1"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml23(td)
+#: ./doc/common/tables/nova-hyperv.xml35(td)
 msgid ""
-"(IntOpt) Number of times to retry live-migration before failing. If == -1, "
-"try until out of hosts. If == 0, only try once, no retries."
+"(StrOpt) The name of a Windows share name mapped to the \"instances_path\" "
+"dir and used by the resize feature to copy files to the target host. If left"
+" blank, an administrative share will be used, looking for the same "
+"\"instances_path\" used locally"
 msgstr ""
 
-#: ./doc/common/tables/nova-conductor.xml26(th)
-msgid "[conductor]"
-msgstr "[conductor]"
+#: ./doc/common/tables/nova-hyperv.xml38(td)
+msgid "limit_cpu_features = False"
+msgstr "limit_cpu_features = False"
 
-#: ./doc/common/tables/nova-conductor.xml29(td)
-msgid "manager = nova.conductor.manager.ConductorManager"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml30(td)
-msgid "(StrOpt) Full class name for the Manager for conductor"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml33(td)
-msgid "topic = conductor"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml34(td)
-msgid "(StrOpt) The topic on which conductor nodes listen"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml37(td)
-msgid "use_local = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml38(td)
-msgid "(BoolOpt) Perform nova-conductor operations locally"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml41(td)
-msgid "workers = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml42(td)
+#: ./doc/common/tables/nova-hyperv.xml39(td)
 msgid ""
-"(IntOpt) Number of workers for OpenStack Conductor service. The default will"
-" be the number of CPUs available."
+"(BoolOpt) Required for live migration among hosts with different CPU "
+"features"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml22(td)
-msgid "compute_available_monitors = ['nova.compute.monitors.all_monitors']"
-msgstr ""
+#: ./doc/common/tables/nova-hyperv.xml42(td)
+msgid "mounted_disk_query_retry_count = 10"
+msgstr "mounted_disk_query_retry_count = 10"
 
-#: ./doc/common/tables/nova-compute.xml23(td)
+#: ./doc/common/tables/nova-hyperv.xml43(td)
 msgid ""
-"(MultiStrOpt) Monitor classes available to the compute which may be "
-"specified more than once."
+"(IntOpt) The number of times to retry checking for a disk mounted via iSCSI."
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml26(td)
-msgid "compute_driver = None"
+#: ./doc/common/tables/nova-hyperv.xml46(td)
+msgid "mounted_disk_query_retry_interval = 5"
+msgstr "mounted_disk_query_retry_interval = 5"
+
+#: ./doc/common/tables/nova-hyperv.xml47(td)
+msgid "(IntOpt) Interval between checks for a mounted iSCSI disk, in seconds."
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml27(td)
+#: ./doc/common/tables/nova-hyperv.xml50(td)
+msgid "qemu_img_cmd = qemu-img.exe"
+msgstr "qemu_img_cmd = qemu-img.exe"
+
+#: ./doc/common/tables/nova-hyperv.xml51(td)
 msgid ""
-"(StrOpt) Driver to use for controlling virtualization. Options include: "
-"libvirt.LibvirtDriver, xenapi.XenAPIDriver, fake.FakeDriver, "
-"baremetal.BareMetalDriver, vmwareapi.VMwareESXDriver, "
-"vmwareapi.VMwareVCDriver"
+"(StrOpt) Path of qemu-img command which is used to convert between different"
+" image types"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml30(td)
-msgid "compute_manager = nova.compute.manager.ComputeManager"
-msgstr ""
+#: ./doc/common/tables/nova-hyperv.xml54(td)
+msgid "vswitch_name = None"
+msgstr "vswitch_name = None"
 
-#: ./doc/common/tables/nova-compute.xml31(td)
-msgid "(StrOpt) Full class name for the Manager for compute"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml34(td)
-msgid "compute_monitors ="
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml35(td)
+#: ./doc/common/tables/nova-hyperv.xml55(td)
 msgid ""
-"(ListOpt) A list of monitors that can be used for getting compute metrics."
+"(StrOpt) External virtual switch Name, if not provided, the first external "
+"virtual switch is used"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml38(td)
-msgid "compute_stats_class = nova.compute.stats.Stats"
+#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml7(literal)
+msgid "[filter:container_sync]"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml39(td)
-msgid "(StrOpt) Class that will manage stats for the local compute host"
+#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml18(td)
+msgid "use = egg:swift#container_sync"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml42(td)
-msgid "console_host = oslo"
+#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml21(td)
+msgid "allow_full_urls = true"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml43(td)
+#: ./doc/common/tables/heat-clients_backends.xml8(caption)
+msgid "Description of configuration options for clients_backends"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_backends.xml22(td)
+msgid "cloud_backend = heat.engine.clients.OpenStackClients"
+msgstr "cloud_backend = heat.engine.clients.OpenStackClients"
+
+#: ./doc/common/tables/heat-clients_backends.xml23(td)
+msgid "(StrOpt) Fully qualified class name to use as a client backend."
+msgstr ""
+
+#: ./doc/common/tables/glance-testing.xml22(td)
+msgid "pydev_worker_debug_host = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-testing.xml23(td)
 msgid ""
-"(StrOpt) Console proxy host to use to connect to instances on this host."
+"(StrOpt) The hostname/IP of the pydev process listening for debug "
+"connections"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml46(td)
-msgid "console_manager = nova.console.manager.ConsoleProxyManager"
+#: ./doc/common/tables/glance-testing.xml26(td)
+msgid "pydev_worker_debug_port = 5678"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml47(td)
-msgid "(StrOpt) Full class name for the Manager for console proxy"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml50(td)
-msgid "default_flavor = m1.small"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml51(td)
+#: ./doc/common/tables/glance-testing.xml27(td)
 msgid ""
-"(StrOpt) Default flavor to use for the EC2 API only. The Nova API does not "
-"support a default flavor."
+"(IntOpt) The port on which a pydev process is listening for connections."
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml62(td)
-msgid "enable_instance_password = True"
+#: ./doc/common/tables/neutron-common.xml23(td)
+#: ./doc/common/tables/neutron-common.xml193(td)
+msgid "(StrOpt) Admin password"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml63(td)
+#: ./doc/common/tables/neutron-common.xml27(td)
+#: ./doc/common/tables/neutron-common.xml197(td)
+msgid "(StrOpt) Admin tenant name"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml31(td)
+msgid "(StrOpt) Admin username"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml34(td)
+msgid "agent_down_time = 75"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml35(td)
 msgid ""
-"(BoolOpt) Enables returning of the instance password by the relevant server "
-"API calls such as create, rebuild or rescue, If the hypervisor does not "
-"support password injection then the password returned will not be correct"
+"(IntOpt) Seconds to regard the agent is down; should be at least twice "
+"report_interval, to be sure the agent is down for good."
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml66(td)
-msgid "heal_instance_info_cache_interval = 60"
+#: ./doc/common/tables/neutron-common.xml42(td)
+msgid "api_workers = 0"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml67(td)
+#: ./doc/common/tables/neutron-common.xml43(td)
+msgid "(IntOpt) Number of separate worker processes for service"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml46(td)
+msgid "auth_ca_cert = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml47(td)
+msgid "(StrOpt) Certificate Authority public key (CA cert) file for ssl"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml50(td)
+msgid "auth_insecure = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml51(td)
+msgid "(BoolOpt) Turn off verification of the certificate for ssl"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml55(td)
+#: ./doc/common/tables/neutron-common.xml205(td)
+msgid "(StrOpt) Authentication region"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml59(td)
+#: ./doc/common/tables/neutron-common.xml209(td)
+msgid "(StrOpt) The type of authentication to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml63(td)
+#: ./doc/common/tables/neutron-common.xml213(td)
+msgid "(StrOpt) Authentication URL"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml66(td)
+msgid "base_mac = fa:16:3e:00:00:00"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml67(td)
+msgid "(StrOpt) The base MAC address Neutron will use for VIFs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml71(td)
+msgid "(StrOpt) The host IP to bind to"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml74(td)
+msgid "bind_port = 9696"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml75(td)
+msgid "(IntOpt) The port to bind to"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml78(td)
+msgid "ca_certs = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml79(td)
+msgid "(StrOpt) CA certificates"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml82(td)
+msgid "core_plugin = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml83(td)
+msgid "(StrOpt) The core plugin Neutron will use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml86(td)
+msgid "ctl_cert = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml87(td)
+msgid "(StrOpt) controller certificate"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml90(td)
+msgid "ctl_privkey = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml91(td)
+msgid "(StrOpt) controller private key"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml94(td)
+msgid "dhcp_agent_notification = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml95(td)
+msgid "(BoolOpt) Allow sending resource operation notification to DHCP agent"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml98(td)
+msgid "dhcp_agents_per_network = 1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml99(td)
+msgid "(IntOpt) Number of DHCP agents scheduled to host a network."
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml102(td)
+msgid "dhcp_confs = $state_path/dhcp"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml103(td)
+msgid "(StrOpt) Location to store DHCP server config files"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml106(td)
+msgid "dhcp_delete_namespaces = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml107(td)
+msgid "(BoolOpt) Delete namespace after removing a dhcp server."
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml110(td)
+msgid "dhcp_domain = openstacklocal"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml114(td)
+msgid "dhcp_driver = neutron.agent.linux.dhcp.Dnsmasq"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml115(td)
+msgid "(StrOpt) The driver used to manage the DHCP server."
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml118(td)
+msgid "dhcp_lease_duration = 86400"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml119(td)
+msgid "(IntOpt) DHCP lease duration"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml126(td)
+msgid "endpoint_type = adminURL"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml127(td)
 msgid ""
-"(IntOpt) Number of seconds between instance info_cache self healing updates"
+"(StrOpt) Network service endpoint type to pull from the keystone catalog"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml70(td)
-msgid "image_cache_manager_interval = 2400"
+#: ./doc/common/tables/neutron-common.xml130(td)
+msgid "force_gateway_on_subnet = False"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml71(td)
+#: ./doc/common/tables/neutron-common.xml131(td)
+msgid "(BoolOpt) Ensure that configured gateway is on subnet"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml134(td)
+msgid "interface_driver = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml135(td)
+msgid "(StrOpt) The driver used to manage the virtual interface."
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml138(td)
+msgid "ip_lib_force_root = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml139(td)
+msgid "(BoolOpt) Force ip_lib calls to use the root helper"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml146(td)
+msgid "mac_generation_retries = 16"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml147(td)
+msgid "(IntOpt) How many times Neutron will retry MAC generation"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml150(td)
+msgid "max_dns_nameservers = 5"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml151(td)
+msgid "(IntOpt) Maximum number of DNS nameservers"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml154(td)
+msgid "max_fixed_ips_per_port = 5"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml155(td)
+msgid "(IntOpt) Maximum number of fixed ips per port"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml158(td)
+msgid "max_subnet_host_routes = 20"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml159(td)
+msgid "(IntOpt) Maximum number of host routes per subnet"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml162(td)
+msgid "periodic_fuzzy_delay = 5"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml166(td)
+msgid "periodic_interval = 40"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml167(td)
+msgid "(IntOpt) Seconds between running periodic tasks"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml171(td)
+msgid "(IntOpt) Interval between two metering reports"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml175(td)
+#: ./doc/common/tables/neutron-common.xml186(td)
+msgid "(StrOpt) Root helper application."
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml178(td)
+msgid "state_path = /var/lib/neutron"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml179(td)
 msgid ""
-"(IntOpt) Number of seconds to wait between runs of the image cache manager"
+"(StrOpt) Where to store Neutron state files. This directory must be writable"
+" by the agent."
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml74(td)
-msgid "image_cache_subdirectory_name = _base"
+#: ./doc/common/tables/neutron-common.xml189(th)
+msgid "[PROXY]"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml75(td)
+#: ./doc/common/tables/neutron-common.xml201(td)
+msgid "(StrOpt) Admin user"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml8(caption)
+msgid "Description of configuration options for hypervisor"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml22(td)
+msgid "default_ephemeral_format = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml23(td)
 msgid ""
-"(StrOpt) Where cached images are stored under $instances_path. This is NOT "
-"the full path - just a folder name. For per-compute-host cached images, set "
-"to _base_$my_ip"
+"(StrOpt) The default format an ephemeral_volume will be formatted with on "
+"creation."
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml78(td)
-msgid "image_handlers = download"
+#: ./doc/common/tables/nova-hypervisor.xml26(td)
+msgid "force_raw_images = True"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml79(td)
+#: ./doc/common/tables/nova-hypervisor.xml27(td)
+msgid "(BoolOpt) Force backing images to raw format"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml30(td)
+msgid "preallocate_images = none"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml31(td)
 msgid ""
-"(ListOpt) Specifies which image handler extension names to use for handling "
-"images. The first extension in the list which can handle the image with a "
-"suitable location will be used."
+"(StrOpt) VM image preallocation mode: \"none\" =&gt; no storage provisioning"
+" is done up front, \"space\" =&gt; storage is fully allocated at instance "
+"start"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml82(td)
-msgid "instance_build_timeout = 0"
+#: ./doc/common/tables/nova-hypervisor.xml34(td)
+msgid "rescue_timeout = 0"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml83(td)
+#: ./doc/common/tables/nova-hypervisor.xml35(td)
 msgid ""
-"(IntOpt) Amount of time in seconds an instance can be in BUILD before going "
-"into ERROR status.Set to 0 to disable."
+"(IntOpt) Automatically unrescue an instance after N seconds. Set to 0 to "
+"disable."
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml86(td)
-msgid "instance_delete_interval = 300"
+#: ./doc/common/tables/nova-hypervisor.xml38(td)
+msgid "timeout_nbd = 10"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml87(td)
-msgid "(IntOpt) Interval in seconds for retrying failed instance file deletes"
+#: ./doc/common/tables/nova-hypervisor.xml39(td)
+msgid "(IntOpt) Amount of time, in seconds, to wait for NBD device start up."
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml90(td)
-msgid "instance_usage_audit = False"
+#: ./doc/common/tables/nova-hypervisor.xml42(td)
+msgid "use_cow_images = True"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml91(td)
-msgid "(BoolOpt) Generate periodic compute.instance.exists notifications"
+#: ./doc/common/tables/nova-hypervisor.xml43(td)
+msgid "(BoolOpt) Whether to use cow images"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml94(td)
-msgid "instance_usage_audit_period = month"
+#: ./doc/common/tables/nova-hypervisor.xml46(td)
+msgid "vcpu_pin_set = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml95(td)
+#: ./doc/common/tables/nova-hypervisor.xml47(td)
 msgid ""
-"(StrOpt) Time period to generate instance usages for. Time period must be "
-"hour, day, month or year"
+"(StrOpt) Defines which pcpus that instance vcpus can use. For example, "
+"\"4-12,^8,15\""
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml98(td)
-msgid "instances_path = $state_path/instances"
+#: ./doc/common/tables/nova-hypervisor.xml50(td)
+msgid "virt_mkfs = []"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml99(td)
-msgid "(StrOpt) Where instances are stored on disk"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml102(td)
-msgid "maximum_instance_delete_attempts = 5"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml103(td)
-msgid "(IntOpt) The number of times to attempt to reap an instance's files."
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml106(td)
-msgid "reboot_timeout = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml107(td)
+#: ./doc/common/tables/nova-hypervisor.xml51(td)
 msgid ""
-"(IntOpt) Automatically hard reboot an instance if it has been stuck in a "
-"rebooting state longer than N seconds. Set to 0 to disable."
+"(MultiStrOpt) Name of the mkfs commands for ephemeral device. The format is "
+"&lt;os_type&gt;=&lt;mkfs command&gt;"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml110(td)
-msgid "reclaim_instance_interval = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml111(td)
-msgid "(IntOpt) Interval in seconds for reclaiming deleted instances"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml114(td)
-msgid "resize_confirm_window = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml115(td)
+#: ./doc/common/tables/nova-hypervisor.xml57(td)
 msgid ""
-"(IntOpt) Automatically confirm resizes after N seconds. Set to 0 to disable."
+"block_migration_flag = VIR_MIGRATE_UNDEFINE_SOURCE, VIR_MIGRATE_PEER2PEER, "
+"VIR_MIGRATE_NON_SHARED_INC"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml118(td)
-msgid "resume_guests_state_on_host_boot = False"
+#: ./doc/common/tables/nova-hypervisor.xml58(td)
+msgid "(StrOpt) Migration flags to be set for block migration"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml119(td)
+#: ./doc/common/tables/nova-hypervisor.xml61(td)
+msgid "disk_cachemodes ="
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml62(td)
 msgid ""
-"(BoolOpt) Whether to start guests that were running before the host rebooted"
+"(ListOpt) Specific cachemodes to use for different disk types e.g: "
+"file=directsync,block=none"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml122(td)
-msgid "running_deleted_instance_action = reap"
+#: ./doc/common/tables/nova-hypervisor.xml65(td)
+msgid "images_rbd_ceph_conf ="
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml123(td)
+#: ./doc/common/tables/nova-hypervisor.xml66(td)
+msgid "(StrOpt) Path to the ceph configuration file to use"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml69(td)
+msgid "images_rbd_pool = rbd"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml70(td)
+msgid "(StrOpt) The RADOS pool in which rbd volumes are stored"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml73(td)
+msgid "images_type = default"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml74(td)
 msgid ""
-"(StrOpt) Action to take if a running deleted instance is detected.Valid "
-"options are 'noop', 'log', 'shutdown', or 'reap'. Set to 'noop' to take no "
-"action."
+"(StrOpt) VM Images format. Acceptable values are: raw, qcow2, lvm, rbd, "
+"default. If default is specified, then use_cow_images flag is used instead "
+"of this one."
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml126(td)
-msgid "running_deleted_instance_poll_interval = 1800"
+#: ./doc/common/tables/nova-hypervisor.xml77(td)
+msgid "images_volume_group = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml127(td)
-msgid "(IntOpt) Number of seconds to wait between runs of the cleanup task."
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml130(td)
-msgid "running_deleted_instance_timeout = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml131(td)
+#: ./doc/common/tables/nova-hypervisor.xml78(td)
 msgid ""
-"(IntOpt) Number of seconds after being deleted when a running instance "
-"should be considered eligible for cleanup."
+"(StrOpt) LVM Volume Group that is used for VM images, when you specify "
+"images_type=lvm."
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml134(td)
-msgid "shelved_offload_time = 0"
+#: ./doc/common/tables/nova-hypervisor.xml81(td)
+msgid "inject_key = False"
+msgstr "inject_key = False"
+
+#: ./doc/common/tables/nova-hypervisor.xml82(td)
+msgid "(BoolOpt) Inject the ssh public key at boot time"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml135(td)
+#: ./doc/common/tables/nova-hypervisor.xml85(td)
+msgid "inject_partition = -2"
+msgstr "inject_partition = -2"
+
+#: ./doc/common/tables/nova-hypervisor.xml86(td)
 msgid ""
-"(IntOpt) Time in seconds before a shelved instance is eligible for removing "
-"from a host. -1 never offload, 0 offload when shelved"
+"(IntOpt) The partition to inject to : -2 =&gt; disable, -1 =&gt; inspect "
+"(libguestfs only), 0 =&gt; not partitioned, &gt;0 =&gt; partition number"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml138(td)
-msgid "shelved_poll_interval = 3600"
+#: ./doc/common/tables/nova-hypervisor.xml89(td)
+msgid "inject_password = False"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml139(td)
-msgid "(IntOpt) Interval in seconds for polling shelved instances to offload"
+#: ./doc/common/tables/nova-hypervisor.xml90(td)
+msgid "(BoolOpt) Inject the admin password at boot time, without an agent."
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml142(td)
-msgid "sync_power_state_interval = 600"
+#: ./doc/common/tables/nova-hypervisor.xml93(td)
+msgid "iscsi_use_multipath = False"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml143(td)
+#: ./doc/common/tables/nova-hypervisor.xml94(td)
+msgid "(BoolOpt) Use multipath connection of the iSCSI volume"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml97(td)
+msgid "iser_use_multipath = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml98(td)
+msgid "(BoolOpt) Use multipath connection of the iSER volume"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml101(td)
+msgid "rescue_image_id = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml102(td)
+msgid "(StrOpt) Rescue ami image"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml105(td)
+msgid "rescue_kernel_id = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml106(td)
+msgid "(StrOpt) Rescue aki image"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml109(td)
+msgid "rescue_ramdisk_id = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml110(td)
+msgid "(StrOpt) Rescue ari image"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml113(td)
+msgid "snapshot_compression = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml114(td)
 msgid ""
-"(IntOpt) Interval to sync power states between the database and the "
-"hypervisor"
+"(BoolOpt) Compress snapshot images when possible. This currently applies "
+"exclusively to qcow2 images"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml146(td)
-msgid "vif_plugging_is_fatal = True"
+#: ./doc/common/tables/nova-hypervisor.xml117(td)
+msgid "snapshot_image_format = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml147(td)
-msgid "(BoolOpt) Fail instance boot if vif plugging fails"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml150(td)
-msgid "vif_plugging_timeout = 300"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml151(td)
+#: ./doc/common/tables/nova-hypervisor.xml118(td)
 msgid ""
-"(IntOpt) Number of seconds to wait for neutron vif plugging events to arrive"
-" before continuing or failing (see vif_plugging_is_fatal). If this is set to"
-" zero and vif_plugging_is_fatal is False, events should not be expected to "
-"arrive at all."
+"(StrOpt) Snapshot image format (valid options are : raw, qcow2, vmdk, vdi). "
+"Defaults to same as source image"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml7(literal)
-msgid "[filter:domain_remap]"
-msgstr "[filter:domain_remap]"
-
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml18(td)
-msgid "use = egg:swift#domain_remap"
+#: ./doc/common/tables/nova-hypervisor.xml121(td)
+msgid "sparse_logical_volumes = False"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml21(td)
-msgid "set log_name = domain_remap"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml40(td)
-msgid "path_root = v1"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml40(td)
-msgid "Root path"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml43(td)
-msgid "reseller_prefixes = AUTH"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml43(td)
-msgid "Reseller prefix"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_xen.xml8(caption)
-msgid "Description of configuration options for storage_xen"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_xen.xml22(td)
-msgid "xenapi_connection_password = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_xen.xml23(td)
-msgid "(StrOpt) Password for XenAPI connection"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_xen.xml26(td)
-msgid "xenapi_connection_url = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_xen.xml27(td)
-msgid "(StrOpt) URL for XenAPI connection"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_xen.xml31(td)
-msgid "(StrOpt) Username for XenAPI connection"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_xen.xml34(td)
-msgid "xenapi_nfs_server = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_xen.xml35(td)
-msgid "(StrOpt) NFS server to be used by XenAPINFSDriver"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_xen.xml38(td)
-msgid "xenapi_nfs_serverpath = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_xen.xml39(td)
-msgid "(StrOpt) Path of exported NFS, used by XenAPINFSDriver"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_xen.xml42(td)
-msgid "xenapi_sr_base_path = /var/run/sr-mount"
-msgstr ""
-
-#: ./doc/common/tables/keystone-credential.xml8(caption)
-msgid "Description of configuration options for credential"
-msgstr ""
-
-#: ./doc/common/tables/keystone-credential.xml19(th)
-msgid "[credential]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-credential.xml22(td)
-msgid "driver = keystone.credential.backends.sql.Credential"
-msgstr ""
-
-#: ./doc/common/tables/trove-amqp.xml30(td)
-msgid "conductor_queue = trove-conductor"
-msgstr "conductor_queue = trove-conductor"
-
-#: ./doc/common/tables/trove-amqp.xml62(td)
+#: ./doc/common/tables/nova-hypervisor.xml122(td)
 msgid ""
-"notification_service_id = {'couchbase': 'fa62fe68-74d9-4779-a24e-"
-"36f19602c415', 'mongodb': 'c8c907af-7375-456f-b929-b637ff9209ee', "
-"'cassandra': '459a230d-4e97-4344-9067-2a54a310b0ed', 'redis': 'b216ffc5-1947"
-"-456c-a4cf-70f94c05f7d0', 'mysql': '2f3ff068-2bfb-4f70-9a9d-a6bb65bc084b'}"
+"(BoolOpt) Create sparse logical volumes (with virtualsize) if this flag is "
+"set to True."
 msgstr ""
 
-#: ./doc/common/tables/trove-amqp.xml63(td)
-msgid "(DictOpt) Unique ID to tag notification events."
+#: ./doc/common/tables/nova-hypervisor.xml125(td)
+msgid "use_usb_tablet = True"
 msgstr ""
 
-#: ./doc/common/tables/nova-xvpnvncproxy.xml8(caption)
-msgid "Description of configuration options for xvpnvncproxy"
+#: ./doc/common/tables/nova-hypervisor.xml126(td)
+msgid "(BoolOpt) Sync virtual and real mouse cursors in Windows VMs"
 msgstr ""
 
-#: ./doc/common/tables/nova-xvpnvncproxy.xml22(td)
-msgid "xvpvncproxy_base_url = http://127.0.0.1:6081/console"
+#: ./doc/common/tables/nova-hypervisor.xml129(td)
+msgid "use_virtio_for_bridges = True"
 msgstr ""
 
-#: ./doc/common/tables/nova-xvpnvncproxy.xml23(td)
+#: ./doc/common/tables/nova-hypervisor.xml130(td)
+msgid "(BoolOpt) Use virtio for bridge interfaces with KVM/QEMU"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml7(literal)
+msgid "[realm1]"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml18(td)
+msgid "key = realm1key"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml21(td)
+msgid "key2 = realm1key2"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml24(td)
+msgid "cluster_name1 = https://host1/v1/"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml27(td)
+msgid "cluster_name2 = https://host2/v1/"
+msgstr ""
+
+#: ./doc/common/tables/nova-wsgi.xml23(td)
+msgid "(StrOpt) File name for the paste.deploy config for nova-api"
+msgstr "(StrOpt)  Nom du fichier pour la config paste.deploy de nova-api"
+
+#: ./doc/common/tables/nova-wsgi.xml31(td)
+msgid "(StrOpt) SSL certificate of API server"
+msgstr "(StrOpt)  Certificat SSL de l'API du serveur"
+
+#: ./doc/common/tables/nova-wsgi.xml35(td)
+msgid "(StrOpt) SSL private key of API server"
+msgstr "(StrOpt)  Clé SSL privée de l'API du serveur"
+
+#: ./doc/common/tables/nova-wsgi.xml42(td)
+msgid "wsgi_default_pool_size = 1000"
+msgstr ""
+
+#: ./doc/common/tables/nova-wsgi.xml43(td)
+msgid "(IntOpt) Size of the pool of greenthreads used by wsgi"
+msgstr ""
+
+#: ./doc/common/tables/nova-wsgi.xml46(td)
 msgid ""
-"(StrOpt) Location of nova xvp VNC console proxy, in the form "
-"\"http://127.0.0.1:6081/console\""
+"wsgi_log_format = %(client_ip)s \"%(request_line)s\" status: %(status_code)s"
+" len: %(body_length)s time: %(wall_seconds).7f"
 msgstr ""
 
-#: ./doc/common/tables/nova-xvpnvncproxy.xml26(td)
-msgid "xvpvncproxy_host = 0.0.0.0"
+#: ./doc/common/tables/nova-wsgi.xml47(td)
+msgid ""
+"(StrOpt) A python format string that is used as the template to generate log"
+" lines. The following values can be formatted into it: client_ip, date_time,"
+" request_line, status_code, body_length, wall_seconds."
+msgstr "(StrOpt)  Une chaîne de formatage Python utilisée en tant que template pour générer les journaux. Les valeurs suivantes peuvent être utilisées : client_ip, date_time, request_line, status_code, body_length, wall_seconds."
+
+#: ./doc/common/tables/keystone-cache.xml8(caption)
+msgid "Description of configuration options for cache"
 msgstr ""
 
-#: ./doc/common/tables/nova-xvpnvncproxy.xml27(td)
-msgid "(StrOpt) Address that the XCP VNC proxy should bind to"
+#: ./doc/common/tables/keystone-cache.xml19(th)
+msgid "[cache]"
 msgstr ""
 
-#: ./doc/common/tables/nova-xvpnvncproxy.xml30(td)
-msgid "xvpvncproxy_port = 6081"
+#: ./doc/common/tables/keystone-cache.xml22(td)
+msgid "backend = keystone.common.cache.noop"
 msgstr ""
 
-#: ./doc/common/tables/nova-xvpnvncproxy.xml31(td)
-msgid "(IntOpt) Port that the XCP VNC proxy should bind to"
+#: ./doc/common/tables/keystone-cache.xml23(td)
+msgid ""
+"(StrOpt) Dogpile.cache backend module. It is recommended that Memcache "
+"(dogpile.cache.memcache) or Redis (dogpile.cache.redis) be used in "
+"production deployments. Small workloads (single process) like devstack can "
+"use the dogpile.cache.memory backend."
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml26(td)
+msgid "backend_argument = []"
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml27(td)
+msgid ""
+"(MultiStrOpt) Arguments supplied to the backend module. Specify this option "
+"once per argument to be passed to the dogpile.cache backend. Example format:"
+" \"&lt;argname&gt;:&lt;value&gt;\"."
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml30(td)
+msgid "config_prefix = cache.keystone"
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml31(td)
+msgid ""
+"(StrOpt) Prefix for building the configuration dictionary for the cache "
+"region. This should not need to be changed unless there is another "
+"dogpile.cache region with the same configuration name."
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml34(td)
+msgid "debug_cache_backend = False"
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml35(td)
+msgid ""
+"(BoolOpt) Extra debugging from the cache backend (cache keys, "
+"get/set/delete/etc calls) This is only really useful if you need to see the "
+"specific cache-backend get/set/delete calls with the keys/values. Typically "
+"this should be left set to False."
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml39(td)
+msgid ""
+"(BoolOpt) Global toggle for all caching using the should_cache_fn mechanism."
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml42(td)
+msgid "expiration_time = 600"
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml43(td)
+msgid ""
+"(IntOpt) Default TTL, in seconds, for any cached item in the dogpile.cache "
+"region. This applies to any cached method that doesn't have an explicit "
+"cache expiration time defined for it."
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml46(td)
+msgid "proxies ="
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml47(td)
+msgid ""
+"(ListOpt) Proxy Classes to import that will affect the way the dogpile.cache"
+" backend functions. See the dogpile.cache documentation on changing-backend-"
+"behavior. Comma delimited list e.g. my.dogpile.proxy.Class, "
+"my.dogpile.proxyClass2."
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml50(td)
+msgid "use_key_mangler = True"
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml51(td)
+msgid ""
+"(BoolOpt) Use a key-mangling function (sha1) to ensure fixed length cache-"
+"keys. This is toggle-able for debugging purposes, it is highly recommended "
+"to always leave this set to True."
+msgstr ""
+
+#: ./doc/common/tables/nova-configdrive.xml8(caption)
+msgid "Description of configuration options for configdrive"
+msgstr ""
+
+#: ./doc/common/tables/nova-configdrive.xml22(td)
+msgid "config_drive_format = iso9660"
+msgstr ""
+
+#: ./doc/common/tables/nova-configdrive.xml23(td)
+msgid "(StrOpt) Config drive format. One of iso9660 (default) or vfat"
+msgstr ""
+
+#: ./doc/common/tables/nova-configdrive.xml26(td)
+msgid ""
+"config_drive_skip_versions = 1.0 2007-01-19 2007-03-01 2007-08-29 2007-10-10"
+" 2007-12-15 2008-02-01 2008-09-01"
+msgstr ""
+
+#: ./doc/common/tables/nova-configdrive.xml27(td)
+msgid ""
+"(StrOpt) List of metadata versions to skip placing into the config drive"
+msgstr ""
+
+#: ./doc/common/tables/nova-configdrive.xml30(td)
+msgid "config_drive_tempdir = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-configdrive.xml31(td)
+msgid ""
+"(StrOpt) Where to put temporary files associated with config drive creation"
+msgstr ""
+
+#: ./doc/common/tables/nova-configdrive.xml34(td)
+msgid "force_config_drive = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-configdrive.xml35(td)
+msgid ""
+"(StrOpt) Set to force injection to take place on a config drive (if set, "
+"valid options are: always)"
+msgstr ""
+
+#: ./doc/common/tables/nova-configdrive.xml38(td)
+msgid "mkisofs_cmd = genisoimage"
+msgstr ""
+
+#: ./doc/common/tables/nova-configdrive.xml45(td)
+msgid "config_drive_cdrom = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-configdrive.xml46(td)
+msgid ""
+"(BoolOpt) Attaches the Config Drive image as a cdrom drive instead of a disk"
+" drive"
+msgstr ""
+
+#: ./doc/common/tables/nova-configdrive.xml49(td)
+msgid "config_drive_inject_password = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-configdrive.xml50(td)
+msgid "(BoolOpt) Sets the admin password in the config drive image"
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml8(caption)
+msgid "Description of configuration options for token"
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml19(th)
+msgid "[token]"
+msgstr "[token]"
+
+#: ./doc/common/tables/keystone-token.xml22(td)
+msgid "bind ="
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml23(td)
+msgid ""
+"(ListOpt) External auth mechanisms that should add bind information to token"
+" e.g. kerberos, x509."
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml27(td)
+msgid ""
+"(IntOpt) Time to cache tokens (in seconds). This has no effect unless global"
+" and token caching are enabled."
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml31(td)
+msgid ""
+"(BoolOpt) Toggle for token system cacheing. This has no effect unless global"
+" caching is enabled."
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml34(td)
+msgid "driver = keystone.token.backends.sql.Token"
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml35(td)
+msgid "(StrOpt) Keystone Token persistence backend driver."
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml39(td)
+msgid ""
+"(StrOpt) Enforcement policy on tokens presented to keystone with bind "
+"information. One of disabled, permissive, strict, required or a specifically"
+" required bind mode e.g. kerberos or x509 to require binding to that "
+"authentication."
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml42(td)
+msgid "expiration = 3600"
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml43(td)
+msgid "(IntOpt) Amount of time a token should remain valid (in seconds)."
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml46(td)
+msgid "provider = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml47(td)
+msgid ""
+"(StrOpt) Controls the token construction, validation, and revocation "
+"operations. Core providers are "
+"\"keystone.token.providers.[pki|uuid].Provider\"."
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml50(td)
+msgid "revocation_cache_time = 3600"
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml51(td)
+msgid ""
+"(IntOpt) Time to cache the revocation list and the revocation events if "
+"revoke extension is enabled (in seconds). This has no effect unless global "
+"and token caching are enabled."
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml54(td)
+msgid "revoke_by_id = True"
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml55(td)
+msgid ""
+"(BoolOpt) Revoke token by token identifier. Setting revoke_by_id to True "
+"enables various forms of enumerating tokens, e.g. `list tokens for user`. "
+"These enumerations are processed to determine the list of tokens to revoke. "
+"Only disable if you are switching to using the Revoke extension with a "
+"backend other than KVS, which stores events in memory."
+msgstr ""
+
+#: ./doc/common/tables/heat-database.xml23(td)
+msgid "(StrOpt) The backend to use for db."
+msgstr ""
+
+#: ./doc/common/tables/heat-database.xml26(td)
+msgid "sqlite_db = heat.sqlite"
+msgstr "sqlite_db = heat.sqlite"
+
+#: ./doc/common/tables/heat-database.xml41(td)
+msgid ""
+"connection = sqlite:////usr/lib/python/site-"
+"packages/heat/openstack/common/db/$sqlite_db"
+msgstr "connection = sqlite:////usr/lib/python/site-packages/heat/openstack/common/db/$sqlite_db"
+
+#: ./doc/common/tables/neutron-ml2.xml8(caption)
+msgid "Description of configuration options for ml2"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2.xml19(th)
+msgid "[ml2]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2.xml22(td)
+msgid "mechanism_drivers ="
+msgstr "mechanism_drivers ="
+
+#: ./doc/common/tables/neutron-ml2.xml23(td)
+msgid ""
+"(ListOpt) An ordered list of networking mechanism driver entrypoints to be "
+"loaded from the neutron.ml2.mechanism_drivers namespace."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2.xml26(td)
+msgid "tenant_network_types = local"
+msgstr "tenant_network_types = local"
+
+#: ./doc/common/tables/neutron-ml2.xml27(td)
+msgid ""
+"(ListOpt) Ordered list of network_types to allocate as tenant networks."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2.xml30(td)
+msgid "type_drivers = local, flat, vlan, gre, vxlan"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2.xml31(td)
+msgid ""
+"(ListOpt) List of network type driver entrypoints to be loaded from the "
+"neutron.ml2.type_drivers namespace."
+msgstr ""
+
+#: ./doc/common/tables/neutron-db.xml22(td)
+msgid "sqlite_db ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-db.xml37(td)
+msgid "connection = sqlite://"
+msgstr ""
+
+#: ./doc/common/tables/neutron-db.xml69(td)
+msgid "max_overflow = 20"
+msgstr ""
+
+#: ./doc/common/tables/neutron-db.xml73(td)
+msgid "max_pool_size = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-db.xml85(td)
+msgid "pool_timeout = 10"
+msgstr ""
+
+#: ./doc/common/tables/keystone-database.xml86(td)
+msgid "sqlite_db = keystone.sqlite"
+msgstr ""
+
+#: ./doc/common/tables/keystone-memcache.xml8(caption)
+msgid "Description of configuration options for memcache"
+msgstr ""
+
+#: ./doc/common/tables/keystone-memcache.xml22(td)
+msgid "max_compare_and_set_retry = 16"
+msgstr ""
+
+#: ./doc/common/tables/keystone-memcache.xml23(td)
+msgid ""
+"(IntOpt) Number of compare-and-set attempts to make when using compare-and-"
+"set in the token memcache back end."
+msgstr ""
+
+#: ./doc/common/tables/keystone-memcache.xml26(td)
+msgid "servers = localhost:11211"
+msgstr ""
+
+#: ./doc/common/tables/keystone-memcache.xml27(td)
+msgid "(ListOpt) Memcache servers in the format of \"host:port\""
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml42(td)
+msgid "pydev_debug = disabled"
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml43(td)
+msgid ""
+"(StrOpt) Enable or disable pydev remote debugging. If value is 'auto' tries "
+"to connect to remote debugger server, but in case of error continues running"
+" with debugging disabled."
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml46(td)
+#: ./doc/common/tables/keystone-debug.xml42(td)
+msgid "pydev_debug_host = None"
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml47(td)
+msgid "(StrOpt) Pydev debug server host (localhost by default)."
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml50(td)
+#: ./doc/common/tables/keystone-debug.xml46(td)
+msgid "pydev_debug_port = None"
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml51(td)
+msgid "(IntOpt) Pydev debug server port (5678 by default)."
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml54(td)
+msgid "remote_cinder_client = trove.common.remote.cinder_client"
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml58(td)
+msgid "remote_dns_client = trove.common.remote.dns_client"
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml62(td)
+msgid "remote_guest_client = trove.common.remote.guest_client"
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml66(td)
+msgid "remote_heat_client = trove.common.remote.heat_client"
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml70(td)
+msgid "remote_nova_client = trove.common.remote.nova_client"
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml74(td)
+msgid "remote_swift_client = trove.common.remote.swift_client"
+msgstr ""
+
+#: ./doc/common/tables/trove-swift.xml22(td)
+msgid "swift_url = http://localhost:8080/v1/AUTH_"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml8(caption)
+msgid "Description of configuration options for tilera"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml22(td)
+msgid "tile_pdu_ip = 10.0.100.1"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml23(td)
+msgid "(StrOpt) IP address of tilera pdu"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml26(td)
+msgid "tile_pdu_mgr = /tftpboot/pdu_mgr"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml27(td)
+msgid "(StrOpt) Management script for tilera pdu"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml30(td)
+msgid "tile_pdu_off = 2"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml31(td)
+msgid "(IntOpt) Power status of tilera PDU is OFF"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml34(td)
+msgid "tile_pdu_on = 1"
+msgstr "tile_pdu_on = 1"
+
+#: ./doc/common/tables/nova-tilera.xml35(td)
+msgid "(IntOpt) Power status of tilera PDU is ON"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml38(td)
+msgid "tile_pdu_status = 9"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml39(td)
+msgid "(IntOpt) Power status of tilera PDU"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml42(td)
+msgid "tile_power_wait = 9"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml43(td)
+msgid ""
+"(IntOpt) Wait time in seconds until check the result after tilera power "
+"operations"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml8(caption)
+msgid "Description of configuration options for libvirt"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml22(td)
+msgid "remove_unused_base_images = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml23(td)
+msgid "(BoolOpt) Should unused base images be removed?"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml26(td)
+msgid "remove_unused_original_minimum_age_seconds = 86400"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml27(td)
+msgid ""
+"(IntOpt) Unused unresized base images younger than this will not be removed"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml33(td)
+msgid "checksum_base_images = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml34(td)
+msgid "(BoolOpt) Write a checksum for files in _base to disk"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml37(td)
+msgid "checksum_interval_seconds = 3600"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml38(td)
+msgid "(IntOpt) How frequently to checksum base images"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml41(td)
+msgid "connection_uri ="
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml42(td)
+msgid ""
+"(StrOpt) Override the default libvirt URI (which is dependent on virt_type)"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml45(td)
+msgid "cpu_mode = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml46(td)
+msgid ""
+"(StrOpt) Set to \"host-model\" to clone the host CPU feature flags; to "
+"\"host-passthrough\" to use the host CPU model exactly; to \"custom\" to use"
+" a named CPU model; to \"none\" to not set any CPU model. If "
+"virt_type=\"kvm|qemu\", it will default to \"host-model\", otherwise it will"
+" default to \"none\""
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml49(td)
+msgid "cpu_model = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml50(td)
+msgid ""
+"(StrOpt) Set to a named libvirt CPU model (see names listed in "
+"/usr/share/libvirt/cpu_map.xml). Only has effect if cpu_mode=\"custom\" and "
+"virt_type=\"kvm|qemu\""
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml53(td)
+msgid "disk_prefix = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml54(td)
+msgid ""
+"(StrOpt) Override the default disk prefix for the devices attached to a "
+"server, which is dependent on virt_type. (valid options are: sd, xvd, uvd, "
+"vd)"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml57(td)
+msgid ""
+"image_info_filename_pattern = "
+"$instances_path/$image_cache_subdirectory_name/%(image)s.info"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml58(td)
+msgid ""
+"(StrOpt) Allows image information files to be stored in non-standard "
+"locations"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml61(td)
+msgid "remove_unused_kernels = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml62(td)
+msgid ""
+"(BoolOpt) Should unused kernel images be removed? This is only safe to "
+"enable if all compute nodes have been updated to support this option. This "
+"will be enabled by default in future."
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml65(td)
+msgid "remove_unused_resized_minimum_age_seconds = 3600"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml66(td)
+msgid ""
+"(IntOpt) Unused resized base images younger than this will not be removed"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml69(td)
+msgid "rng_dev_path = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml70(td)
+msgid ""
+"(StrOpt) A path to a device that will be used as source of entropy on the "
+"host. Permitted options are: /dev/random or /dev/hwrng"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml73(td)
+msgid "snapshots_directory = $instances_path/snapshots"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml74(td)
+msgid ""
+"(StrOpt) Location where libvirt driver will store snapshots before uploading"
+" them to image service"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml77(td)
+msgid "vif_driver = nova.virt.libvirt.vif.LibvirtGenericVIFDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml78(td)
+msgid ""
+"(StrOpt) DEPRECATED. The libvirt VIF driver to configure the VIFs.This "
+"option is deprecated and will be removed in the Juno release."
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml81(td)
+msgid "virt_type = kvm"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml82(td)
+msgid ""
+"(StrOpt) Libvirt domain type (valid options are: kvm, lxc, qemu, uml, xen)"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml86(td)
+msgid ""
+"(StrOpt) Method used to wipe old volumes (valid options are: none, zero, "
+"shred)"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml93(td)
+msgid ""
+"volume_drivers = iscsi=nova.virt.libvirt.volume.LibvirtISCSIVolumeDriver, "
+"iser=nova.virt.libvirt.volume.LibvirtISERVolumeDriver, "
+"local=nova.virt.libvirt.volume.LibvirtVolumeDriver, "
+"fake=nova.virt.libvirt.volume.LibvirtFakeVolumeDriver, "
+"rbd=nova.virt.libvirt.volume.LibvirtNetVolumeDriver, "
+"sheepdog=nova.virt.libvirt.volume.LibvirtNetVolumeDriver, "
+"nfs=nova.virt.libvirt.volume.LibvirtNFSVolumeDriver, "
+"aoe=nova.virt.libvirt.volume.LibvirtAOEVolumeDriver, "
+"glusterfs=nova.virt.libvirt.volume.LibvirtGlusterfsVolumeDriver, "
+"fibre_channel=nova.virt.libvirt.volume.LibvirtFibreChannelVolumeDriver, "
+"scality=nova.virt.libvirt.volume.LibvirtScalityVolumeDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml94(td)
+msgid "(ListOpt) Libvirt handlers for remote volumes."
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml97(td)
+msgid "wait_soft_reboot_seconds = 120"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml98(td)
+msgid ""
+"(IntOpt) Number of seconds to wait for instance to shut down after soft "
+"reboot request is made. We fall back to hard reboot if instance does not "
+"shutdown within this window."
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml8(caption)
+msgid "Description of configuration options for mlnx"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml22(td)
+msgid "backoff_rate = 2"
+msgstr "backoff_rate = 2"
+
+#: ./doc/common/tables/neutron-mlnx.xml23(td)
+msgid ""
+"(IntOpt) backoff rate multiplier for waiting period between retries for "
+"request to daemon, i.e. value of 2 will double the request timeout each "
+"retry"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml26(td)
+msgid "daemon_endpoint = tcp://127.0.0.1:60001"
+msgstr "daemon_endpoint = tcp://127.0.0.1:60001"
+
+#: ./doc/common/tables/neutron-mlnx.xml27(td)
+msgid "(StrOpt) eswitch daemon end point"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml34(td)
+msgid "request_timeout = 3000"
+msgstr "request_timeout = 3000"
+
+#: ./doc/common/tables/neutron-mlnx.xml35(td)
+msgid ""
+"(IntOpt) The number of milliseconds the agent will wait for response on "
+"request to daemon."
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml38(th)
+msgid "[MLNX]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml41(td)
+msgid "network_vlan_ranges = default:1:1000"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml45(td)
+msgid "physical_network_type = eth"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml46(td)
+msgid "(StrOpt) Physical network type for provider network (eth or ib)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml49(td)
+msgid "physical_network_type_mappings ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml50(td)
+msgid ""
+"(ListOpt) List of &lt;physical_network&gt;:&lt;physical_network_type&gt; "
+"with physical_network_type is either eth or ib"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml53(td)
+msgid "tenant_network_type = vlan"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_manager.xml8(caption)
+msgid "Description of configuration options for zoning_manager"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_manager.xml22(td)
+msgid ""
+"brcd_sb_connector = "
+"cinder.zonemanager.drivers.brocade.brcd_fc_zone_client_cli.BrcdFCZoneClientCLI"
+msgstr "brcd_sb_connector = cinder.zonemanager.drivers.brocade.brcd_fc_zone_client_cli.BrcdFCZoneClientCLI"
+
+#: ./doc/common/tables/cinder-zoning_manager.xml23(td)
+msgid "(StrOpt) Southbound connector for zoning operation"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_manager.xml26(td)
+msgid ""
+"fc_san_lookup_service = "
+"cinder.zonemanager.drivers.brocade.brcd_fc_san_lookup_service.BrcdFCSanLookupService"
+msgstr "fc_san_lookup_service = cinder.zonemanager.drivers.brocade.brcd_fc_san_lookup_service.BrcdFCSanLookupService"
+
+#: ./doc/common/tables/cinder-zoning_manager.xml27(td)
+msgid "(StrOpt) FC San Lookup Service"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_manager.xml30(td)
+msgid ""
+"zone_driver = "
+"cinder.zonemanager.drivers.brocade.brcd_fc_zone_driver.BrcdFCZoneDriver"
+msgstr "zone_driver = cinder.zonemanager.drivers.brocade.brcd_fc_zone_driver.BrcdFCZoneDriver"
+
+#: ./doc/common/tables/cinder-zoning_manager.xml31(td)
+msgid "(StrOpt) FC Zone Driver responsible for zone management"
+msgstr ""
+
+#: ./doc/common/tables/glance-ssl.xml27(td)
+msgid "(StrOpt) Certificate file to use when starting API server securely."
+msgstr ""
+
+#: ./doc/common/tables/glance-ssl.xml31(td)
+msgid "(StrOpt) Private key file to use when starting API server securely."
+msgstr ""
+
+#: ./doc/common/tables/neutron-securitygroups.xml8(caption)
+msgid "Description of configuration options for securitygroups"
+msgstr ""
+
+#: ./doc/common/tables/neutron-securitygroups.xml19(th)
+msgid "[SECURITYGROUP]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-securitygroups.xml22(td)
+msgid "enable_security_group = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-securitygroups.xml23(td)
+msgid ""
+"(BoolOpt) Controls whether the neutron security group API is enabled in the "
+"server. It should be false when using no security groups or using the nova "
+"security group API."
+msgstr ""
+
+#: ./doc/common/tables/neutron-securitygroups.xml27(td)
+msgid "(StrOpt) Driver for security groups firewall in the L2 agent"
+msgstr ""
+
+#: ./doc/common/tables/keystone-debug.xml43(td)
+msgid "(StrOpt) Host to connect to for remote debugger."
+msgstr ""
+
+#: ./doc/common/tables/keystone-debug.xml47(td)
+msgid "(IntOpt) Port to connect to for remote debugger."
+msgstr ""
+
+#: ./doc/common/tables/keystone-debug.xml50(td)
+msgid "standard_threads = False"
+msgstr ""
+
+#: ./doc/common/tables/keystone-debug.xml51(td)
+msgid "(BoolOpt) Do not monkey-patch threading system modules."
+msgstr ""
+
+#: ./doc/common/tables/cinder-rootwrap.xml22(td)
+msgid "filters_path = /etc/cinder/rootwrap.d,/usr/share/cinder/rootwrap"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml8(caption)
+msgid "Description of configuration options for nexenta_iscsi"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml22(td)
+msgid "nexenta_blocksize ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml23(td)
+msgid "(StrOpt) block size for volumes (blank=default,8KB)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml26(td)
+msgid "nexenta_host ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml27(td)
+msgid "(StrOpt) IP address of Nexenta SA"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml30(td)
+msgid "nexenta_iscsi_target_portal_port = 3260"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml31(td)
+msgid "(IntOpt) Nexenta target portal port"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml34(td)
+msgid "nexenta_password = nexenta"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml35(td)
+msgid "(StrOpt) Password to connect to Nexenta SA"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml38(td)
+msgid "nexenta_rest_port = 2000"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml39(td)
+msgid "(IntOpt) HTTP port to connect to Nexenta REST API server"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml42(td)
+msgid "nexenta_rest_protocol = auto"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml43(td)
+msgid "(StrOpt) Use http or https for REST connection (default auto)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml46(td)
+msgid "nexenta_rrmgr_compression = 0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml47(td)
+msgid ""
+"(IntOpt) Enable stream compression, level 1..9. 1 - gives best speed; 9 - "
+"gives best compression."
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml50(td)
+msgid "nexenta_rrmgr_connections = 2"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml51(td)
+msgid "(IntOpt) Number of TCP connections."
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml54(td)
+msgid "nexenta_rrmgr_tcp_buf_size = 4096"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml55(td)
+msgid "(IntOpt) TCP Buffer size in KiloBytes."
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml58(td)
+msgid "nexenta_sparse = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml59(td)
+msgid "(BoolOpt) flag to create sparse volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml62(td)
+msgid "nexenta_sparsed_volumes = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml66(td)
+msgid "nexenta_target_group_prefix = cinder/"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml67(td)
+msgid "(StrOpt) prefix for iSCSI target groups on SA"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml70(td)
+msgid "nexenta_target_prefix = iqn.1986-03.com.sun:02:cinder-"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml71(td)
+msgid "(StrOpt) IQN prefix for iSCSI targets"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml74(td)
+msgid "nexenta_user = admin"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml75(td)
+msgid "(StrOpt) User name to connect to Nexenta SA"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml78(td)
+msgid "nexenta_volume = cinder"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml79(td)
+msgid "(StrOpt) pool on SA that will hold all volumes"
 msgstr ""
 
 #. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
-#: ./doc/common/tables/nova-xvpnvncproxy.xml0(None)
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml0(None)
 msgid "translator-credits"
 msgstr "Olivier Buisson <olivier@obn.me>, 2012"
diff --git a/doc/common/locale/ja.po b/doc/common/locale/ja.po
index c6f10266f7..fe8e2c337b 100644
--- a/doc/common/locale/ja.po
+++ b/doc/common/locale/ja.po
@@ -7,9 +7,9 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: OpenStack Manuals\n"
-"POT-Creation-Date: 2014-06-02 05:41+0000\n"
-"PO-Revision-Date: 2014-06-02 06:10+0000\n"
-"Last-Translator: Tomoyuki KATO <tomo@dream.daynight.jp>\n"
+"POT-Creation-Date: 2014-06-03 02:30+0000\n"
+"PO-Revision-Date: 2014-06-03 02:40+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"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -17,1267 +17,66 @@ msgstr ""
 "Language: ja\n"
 "Plural-Forms: nplurals=1; plural=0;\n"
 
-#: ./doc/common/app_support.xml7(title)
-msgid "Community support"
-msgstr "コミュニティのサポート"
-
-#: ./doc/common/app_support.xml8(para)
-msgid ""
-"The following resources are available to help you run and use OpenStack. The"
-" OpenStack community constantly improves and adds to the main features of "
-"OpenStack, but if you have any questions, do not hesitate to ask. Use the "
-"following resources to get OpenStack support, and troubleshoot your "
-"installations."
-msgstr "OpenStackの利用に役立つ、以下のリソースがあります。OpenStackコミュニティは、OpenStackを継続的に改善、機能追加していますが、もしあなたが何らかの疑問に直面したら、遠慮せずに相談してください。下記のリソースをOpenStackのサポートとトラブルシュートに活用してください。"
-
-#: ./doc/common/app_support.xml15(title)
-msgid "Documentation"
-msgstr "ドキュメント"
-
-#: ./doc/common/app_support.xml16(para)
-msgid ""
-"For the available OpenStack documentation, see <link "
-"href=\"http://docs.openstack.org\">docs.openstack.org</link>."
-msgstr "OpenStackのドキュメントは、 <link href=\"http://docs.openstack.org\">docs.openstack.org</link>を参照してください。"
-
-#: ./doc/common/app_support.xml19(para) ./doc/common/app_support.xml393(para)
-#: ./doc/common/ch_getstart.xml208(para)
-msgid ""
-"To provide feedback on documentation, join and use the <email>openstack-"
-"docs@lists.openstack.org</email> mailing list at <link "
-"href=\"http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-"
-"docs\">OpenStack Documentation Mailing List</link>, or <link "
-"href=\"https://bugs.launchpad.net/openstack-manuals/+filebug\">report a "
-"bug</link>."
-msgstr "ドキュメントにフィードバックするには、 <link href=\"http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs\">OpenStack Documentation Mailing List</link>の <email>openstack-docs@lists.openstack.org</email>か、Launchpadの<link href=\"https://bugs.launchpad.net/openstack-manuals/+filebug\">report a bug</link>を活用してください。"
-
-#: ./doc/common/app_support.xml26(para)
-msgid ""
-"The following books explain how to install an OpenStack cloud and its "
-"associated components:"
-msgstr "OpenStackクラウドと関連コンポーネントの導入ガイド:"
-
-#: ./doc/common/app_support.xml33(citetitle)
-msgid "Installation Guide for Debian 7.0"
-msgstr "Installation Guide for Debian 7.0"
-
-#: ./doc/common/app_support.xml41(citetitle)
-msgid "Installation Guide for openSUSE and SUSE Linux Enterprise Server"
-msgstr "Installation Guide for openSUSE and SUSE Linux Enterprise Server"
-
-#: ./doc/common/app_support.xml49(citetitle)
-msgid "Installation Guide for Red Hat Enterprise Linux, CentOS, and Fedora"
-msgstr "Red Hat Enterprise Linux, CentOS, and Fedora向けインストールガイド"
-
-#: ./doc/common/app_support.xml58(citetitle)
-msgid "Installation Guide for Ubuntu 12.04/14.04 (LTS)"
-msgstr "インストールガイド Ubuntu 12.04/14.04 (LTS) 版"
-
-#: ./doc/common/app_support.xml63(para)
-msgid ""
-"The following books explain how to configure and run an OpenStack cloud:"
-msgstr "OpenStackクラウドの構成と実行ガイド:"
-
-#: ./doc/common/app_support.xml70(citetitle)
-msgid "Cloud Administrator Guide"
-msgstr "Cloud Administrator Guide"
-
-#: ./doc/common/app_support.xml76(citetitle)
-msgid "Configuration Reference"
-msgstr "Configuration Reference"
-
-#: ./doc/common/app_support.xml82(citetitle)
-msgid "Operations Guide"
-msgstr "Operations Guide"
-
-#: ./doc/common/app_support.xml88(citetitle)
-msgid "High Availability Guide"
-msgstr "High Availability Guide"
-
-#: ./doc/common/app_support.xml94(citetitle)
-msgid "Security Guide"
-msgstr "Security Guide"
-
-#: ./doc/common/app_support.xml100(citetitle)
-msgid "Virtual Machine Image Guide"
-msgstr "Virtual Machine Image Guide"
-
-#: ./doc/common/app_support.xml104(para)
-msgid ""
-"The following books explain how to use the OpenStack dashboard and command-"
-"line clients:"
-msgstr "OpenStackダッシュボードとCLIクライアントガイド"
-
-#: ./doc/common/app_support.xml111(citetitle)
-msgid "API Quick Start"
-msgstr "API Quick Start"
-
-#: ./doc/common/app_support.xml118(citetitle)
-msgid "End User Guide"
-msgstr "End User Guide"
-
-#: ./doc/common/app_support.xml125(citetitle)
-msgid "Admin User Guide"
-msgstr "Admin User Guide"
-
-#: ./doc/common/app_support.xml132(citetitle)
-msgid "Command-Line Interface Reference"
-msgstr "コマンドラインインターフェースリファレンス"
-
-#: ./doc/common/app_support.xml136(para)
-msgid ""
-"The following documentation provides reference and guidance information for "
-"the OpenStack APIs:"
-msgstr "OpenStack APIのリファレンスガイド"
-
-#: ./doc/common/app_support.xml142(link)
-msgid "OpenStack API Complete Reference (HTML)"
-msgstr "OpenStack API Complete Reference (HTML)"
-
-#: ./doc/common/app_support.xml148(link)
-msgid "API Complete Reference (PDF)"
-msgstr "API Complete Reference (PDF)"
-
-#: ./doc/common/app_support.xml153(citetitle)
-msgid "OpenStack Block Storage Service API v2 Reference"
-msgstr "OpenStack Block Storage Service API v2 Reference"
-
-#: ./doc/common/app_support.xml160(citetitle)
-msgid "OpenStack Compute API v2 and Extensions Reference"
-msgstr "OpenStack Compute API v2 and Extensions Reference"
-
-#: ./doc/common/app_support.xml167(citetitle)
-msgid "OpenStack Identity Service API v2.0 Reference"
-msgstr "OpenStack Identity Service API v2.0 Reference"
-
-#: ./doc/common/app_support.xml173(citetitle)
-msgid "OpenStack Image Service API v2 Reference"
-msgstr "OpenStack Identity Service API v2.0 Reference"
-
-#: ./doc/common/app_support.xml179(citetitle)
-msgid "OpenStack Networking API v2.0 Reference"
-msgstr "OpenStack Networking API v2.0 Reference"
-
-#: ./doc/common/app_support.xml185(citetitle)
-msgid "OpenStack Object Storage API v1 Reference"
-msgstr "OpenStack Object Storage API v1 Reference"
-
-#: ./doc/common/app_support.xml189(para)
-msgid ""
-"The <link href=\"http://docs.openstack.org/training-"
-"guides/content/\"><citetitle>Training Guides</citetitle></link> offer "
-"software training for cloud administration and management."
-msgstr "<link href=\"http://docs.openstack.org/training-guides/content/\"><citetitle>トレーニングガイド</citetitle></link>はクラウド管理者向けのソフトウェアトレーニングを提供します。"
-
-#: ./doc/common/app_support.xml196(title)
-msgid "ask.openstack.org"
-msgstr "ask.openstack.org"
-
-#: ./doc/common/app_support.xml197(para)
-msgid ""
-"During the set up or testing of OpenStack, you might have questions about "
-"how a specific task is completed or be in a situation where a feature does "
-"not work correctly. Use the <link "
-"href=\"http://ask.openstack.org\">ask.openstack.org</link> site to ask "
-"questions and get answers. When you visit the <link "
-"href=\"http://ask.openstack.org\">http://ask.openstack.org</link> site, scan"
-" the recently asked questions to see whether your question has already been "
-"answered. If not, ask a new question. Be sure to give a clear, concise "
-"summary in the title and provide as much detail as possible in the "
-"description. Paste in your command output or stack traces, links to screen "
-"shots, and any other information which might be useful."
-msgstr "OpenStackの導入やテスト中、特定のタスクが完了したのか、うまく動いていないのかを質問したくなるかもしれません。その時は、<link href=\"http://ask.openstack.org\">ask.openstack.org</link>が役に立ちます。<link href=\"http://ask.openstack.org\">ask.openstack.org</link>で、すでに同様の質問に回答がないかを確かめてみてください。もしなければ、質問しましょう。簡潔で明瞭なサマリーをタイトルにし、できるだけ詳細な情報を記入してください。コマンドの出力結果やスタックトレース、スクリーンショットへのリンク、その他有用な情報などがいいでしょう。"
-
-#: ./doc/common/app_support.xml214(title)
-msgid "OpenStack mailing lists"
-msgstr "OpenStack メーリングリスト"
-
-#: ./doc/common/app_support.xml215(para)
-msgid ""
-"A great way to get answers and insights is to post your question or "
-"problematic scenario to the OpenStack mailing list. You can learn from and "
-"help others who might have similar issues. To subscribe or view the "
-"archives, go to <link href=\"http://lists.openstack.org/cgi-"
-"bin/mailman/listinfo/openstack\">http://lists.openstack.org/cgi-"
-"bin/mailman/listinfo/openstack</link>. You might be interested in the other "
-"mailing lists for specific projects or development, which you can find <link"
-" href=\"http://wiki.openstack.org/MailingLists\">on the wiki</link>. A "
-"description of all mailing lists is available at <link "
-"href=\"http://wiki.openstack.org/MailingLists\">http://wiki.openstack.org/MailingLists</link>."
-msgstr "回答やヒントを得るとっておきの方法は、OpenStackメーリングリストへ質問や問題の状況を投稿することです。同様の問題に対処したことのある仲間が助けてくれることでしょう。購読の手続き、アーカイブの参照は<link href=\"http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack\">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</link>で行ってください。特定プロジェクトや環境についてのメーリングリストは、<link href=\"http://wiki.openstack.org/MailingLists\">on the wiki</link>で探してみましょう。すべてのメーリングリストは、<link href=\"http://wiki.openstack.org/MailingLists\">http://wiki.openstack.org/MailingLists</link>で参照できます。"
-
-#: ./doc/common/app_support.xml231(title)
-msgid "The OpenStack wiki"
-msgstr "OpenStack wiki"
-
-#: ./doc/common/app_support.xml232(para)
-msgid ""
-"The <link href=\"http://wiki.openstack.org/\">OpenStack wiki</link> contains"
-" a broad range of topics but some of the information can be difficult to "
-"find or is a few pages deep. Fortunately, the wiki search feature enables "
-"you to search by title or content. If you search for specific information, "
-"such as about networking or nova, you can find a large amount of relevant "
-"material. More is being added all the time, so be sure to check back often. "
-"You can find the search box in the upper-right corner of any OpenStack wiki "
-"page."
-msgstr "<link href=\"http://wiki.openstack.org/\">OpenStack wiki</link>は広い範囲のトピックを扱っていますが、情報によっては、探すのが難しかったり、情報が少なかったりします。幸いなことに wiki の検索機能で、タイトルと内容で探せます。もし特定の情報、たとえばネットワークや nova について探すのであれば、多くの関連情報を見つけられます。日々追加されているため、こまめに確認してみてください。OpenStack wiki ページの右上に、その検索窓はあります。"
-
-#: ./doc/common/app_support.xml243(title)
-msgid "The Launchpad Bugs area"
-msgstr "Launchpad バグエリア"
-
-#: ./doc/common/app_support.xml244(para)
-msgid ""
-"The OpenStack community values your set up and testing efforts and wants "
-"your feedback. To log a bug, you must sign up for a Launchpad account at "
-"<link "
-"href=\"https://launchpad.net/+login\">https://launchpad.net/+login</link>. "
-"You can view existing bugs and report bugs in the Launchpad Bugs area. Use "
-"the search feature to determine whether the bug has already been reported or"
-" already been fixed. If it still seems like your bug is unreported, fill out"
-" a bug report."
-msgstr "OpenStackコミュニティはあなたのセットアップ、テストの取り組みに価値を感じており、フィードバックを求めています。バグを登録するには、<link href=\"https://launchpad.net/+login\">https://launchpad.net/+login</link>でLaunchpadのアカウントを作成してください。Launchpadバグエリアにて、既知のバグの確認と報告ができます。すでにそのバグが報告、解決されていないかを判断するため、検索機能を活用してください。もしそのバグが報告されていなければ、バグレポートを入力しましょう。"
-
-#: ./doc/common/app_support.xml252(para)
-msgid "Some tips:"
-msgstr "使いこなすヒント:"
-
-#: ./doc/common/app_support.xml255(para)
-msgid "Give a clear, concise summary."
-msgstr "明瞭で簡潔なまとめを。"
-
-#: ./doc/common/app_support.xml258(para)
-msgid ""
-"Provide as much detail as possible in the description. Paste in your command"
-" output or stack traces, links to screen shots, and any other information "
-"which might be useful."
-msgstr "できるだけ詳細な情報を記入してください。コマンドの出力結果やスタックトレース、スクリーンショットへのリンク、その他有用な情報などがいいでしょう。"
-
-#: ./doc/common/app_support.xml264(para)
-msgid ""
-"Be sure to include the software and package versions that you are using, "
-"especially if you are using a development branch, such as, <literal>\"Juno "
-"release\" vs git commit bc79c3ecc55929bac585d04a03475b72e06a3208</literal>."
-msgstr "ソフトウェアとパッケージのバージョンを含めることを忘れずに。特に開発ブランチは<literal>\"Juno release\" vs git commit bc79c3ecc55929bac585d04a03475b72e06a3208</literal>のように明記しましょう。"
-
-#: ./doc/common/app_support.xml271(para)
-msgid ""
-"Any deployment-specific information is helpful, such as whether you are "
-"using Ubuntu 14.04 or are performing a multi-node installation."
-msgstr "環境固有の情報が役に立ちます。例えば、Ubuntu 14.04 の利用有無、複数ノードのインストール有無です。"
-
-#: ./doc/common/app_support.xml276(para)
-msgid "The following Launchpad Bugs areas are available:"
-msgstr "以下の Launchpad バグエリアが利用できます。"
-
-#: ./doc/common/app_support.xml282(link)
-msgid "Bugs: OpenStack Block Storage (cinder)"
-msgstr "Bugs: OpenStack Block Storage (cinder)"
-
-#: ./doc/common/app_support.xml288(link)
-msgid "Bugs: OpenStack Compute (nova)"
-msgstr "Bugs: OpenStack Compute (nova)"
-
-#: ./doc/common/app_support.xml293(link)
-msgid "Bugs: OpenStack Dashboard (horizon)"
-msgstr "Bugs : OpenStack Dashboard (horizon)"
-
-#: ./doc/common/app_support.xml299(link)
-msgid "Bugs: OpenStack Identity (keystone)"
-msgstr "Bugs : OpenStack Identity (keystone)"
-
-#: ./doc/common/app_support.xml305(link)
-msgid "Bugs: OpenStack Image Service (glance)"
-msgstr "Bugs : OpenStack Image Service (glance)"
-
-#: ./doc/common/app_support.xml311(link)
-msgid "Bugs: OpenStack Networking (neutron)"
-msgstr "Bugs : OpenStack Networking (neutron)"
-
-#: ./doc/common/app_support.xml317(link)
-msgid "Bugs: OpenStack Object Storage (swift)"
-msgstr "Bugs : OpenStack Object Storage (swift)"
-
-#: ./doc/common/app_support.xml324(link)
-msgid "Bugs: Bare Metal (ironic)"
-msgstr "Bugs: Bare Metal (ironic)"
-
-#: ./doc/common/app_support.xml329(link)
-msgid "Bugs: Data Processing Service (sahara)"
-msgstr "Bugs: Data Processing Service (sahara)"
-
-#: ./doc/common/app_support.xml335(link)
-msgid "Bugs: Database Service (trove)"
-msgstr "Bugs: Database Service (trove)"
-
-#: ./doc/common/app_support.xml340(link)
-msgid "Bugs: Orchestration (heat)"
-msgstr "Bugs: Orchestration (heat)"
-
-#: ./doc/common/app_support.xml345(link)
-msgid "Bugs: Telemetry (ceilometer)"
-msgstr "Bugs: Telemetry (ceilometer)"
-
-#: ./doc/common/app_support.xml350(link)
-msgid "Bugs: Queue Service (marconi)"
-msgstr "Bugs: Queue Service (marconi)"
-
-#: ./doc/common/app_support.xml356(link)
-msgid "Bugs: OpenStack API Documentation (developer.openstack.org)"
-msgstr "Bugs: OpenStack API Documentation (developer.openstack.org)"
-
-#: ./doc/common/app_support.xml362(link)
-msgid "Bugs: OpenStack Documentation (docs.openstack.org)"
-msgstr "Bugs: OpenStack Documentation (docs.openstack.org)"
-
-#: ./doc/common/app_support.xml368(title)
-msgid "The OpenStack IRC channel"
-msgstr "OpenStack IRC チャネル"
-
-#: ./doc/common/app_support.xml369(para)
-msgid ""
-"The OpenStack community lives in the #openstack IRC channel on the Freenode "
-"network. You can hang out, ask questions, or get immediate feedback for "
-"urgent and pressing issues. To install an IRC client or use a browser-based "
-"client, go to <link "
-"href=\"http://webchat.freenode.net\">http://webchat.freenode.net/</link>. "
-"You can also use Colloquy (Mac OS X, <link "
-"href=\"http://colloquy.info/\">http://colloquy.info/</link>), mIRC (Windows,"
-" <link href=\"http://www.mirc.com/\">http://www.mirc.com/</link>), or XChat "
-"(Linux). When you are in the IRC channel and want to share code or command "
-"output, the generally accepted method is to use a Paste Bin. The OpenStack "
-"project has one at <link "
-"href=\"http://paste.openstack.org\">http://paste.openstack.org</link>. Just "
-"paste your longer amounts of text or logs in the web form and you get a URL "
-"that you can paste into the channel. The OpenStack IRC channel is "
-"<literal>#openstack</literal> on <literal>irc.freenode.net</literal>. You "
-"can find a list of all OpenStack IRC channels at <link "
-"href=\"https://wiki.openstack.org/wiki/IRC\">https://wiki.openstack.org/wiki/IRC</link>."
-msgstr "OpenStackコミュニティはFreenode上の#openstack IRCチャネルを活用しています。あなたはそこに訪れ、質問することで、差し迫った問題へのフィードバックを迅速に得られます。IRCクライアントをインストール、もしくはブラウザベースのクライアントを使うには、<link href=\"http://webchat.freenode.net\">http://webchat.freenode.net/</link>にアクセスしてください。また、Colloquy (Mac OS X, <link href=\"http://colloquy.info/\">http://colloquy.info/</link>), mIRC (Windows, <link href=\"http://www.mirc.com/\">http://www.mirc.com/</link>), or XChat (Linux)なども使えます。IRCチャネル上でコードやコマンド出力結果を共有したい時には、Paste Binが多く使われています。OpenStackプロジェクトのPaste Binは<link href=\"http://paste.openstack.org\">http://paste.openstack.org</link>です。長めのテキストやログであっても、webフォームに貼り付けてURLを得るだけです。OpenStack IRCチャネルは、<literal>#openstack</literal> on <literal>irc.freenode.net</literal>です。OpenStack IRC チャネルは、<link href=\"https://wiki.openstack.org/wiki/IRC\">https://wiki.openstack.org/wiki/IRC</link>にリストがあります。"
-
-#: ./doc/common/app_support.xml392(title)
-msgid "Documentation feedback"
-msgstr "ドキュメントへのフィードバック"
-
-#: ./doc/common/app_support.xml399(title)
-msgid "OpenStack distribution packages"
-msgstr "OpenStackディストリビューション"
-
-#: ./doc/common/app_support.xml400(para)
-msgid ""
-"The following Linux distributions provide community-supported packages for "
-"OpenStack:"
-msgstr "OpenStackのコミュニティサポート版を提供しているディストリビューション"
-
-#: ./doc/common/app_support.xml404(emphasis)
-msgid "Debian:"
-msgstr "Debian:"
-
-#: ./doc/common/app_support.xml407(link)
-msgid "http://wiki.debian.org/OpenStack"
-msgstr "http://wiki.debian.org/OpenStack"
-
-#: ./doc/common/app_support.xml410(emphasis)
-msgid "CentOS, Fedora, and Red Hat Enterprise Linux:"
-msgstr "CentOS、Fedora、およびRed Hat Enterprise Linux:"
-
-#: ./doc/common/app_support.xml413(link)
-msgid "http://openstack.redhat.com/"
-msgstr "http://openstack.redhat.com/"
-
-#: ./doc/common/app_support.xml416(emphasis)
-msgid "openSUSE and SUSE Linux Enterprise Server:"
-msgstr "openSUSEとSUSE Linux Enterprise Server:"
-
-#: ./doc/common/app_support.xml420(link)
-msgid "http://en.opensuse.org/Portal:OpenStack"
-msgstr "http://en.opensuse.org/Portal:OpenStack"
-
-#: ./doc/common/app_support.xml423(emphasis)
-msgid "Ubuntu:"
-msgstr "Ubuntu:"
-
-#: ./doc/common/app_support.xml426(link)
-msgid "https://wiki.ubuntu.com/ServerTeam/CloudArchive"
-msgstr "https://wiki.ubuntu.com/ServerTeam/CloudArchive"
-
-#: ./doc/common/section_cli_glance_manage_images.xml7(title)
-msgid "Manage images"
-msgstr "イメージの管理"
-
-#: ./doc/common/section_cli_glance_manage_images.xml8(para)
-msgid ""
-"The cloud operator assigns roles to users. Roles determine who can upload "
-"and manage images. The operator might restrict image upload and management "
-"to only cloud administrators or operators."
-msgstr "クラウド運用者はユーザーにロールを割り当てます。ロールはイメージをアップロードおよび管理できるユーザーを決定します。運用者はイメージのアップロードと管理をクラウド管理者や運用者のみに制限するかもしれません。"
-
-#: ./doc/common/section_cli_glance_manage_images.xml12(para)
-msgid ""
-"You can upload images through the <placeholder-1/> client or the Image "
-"Service API. You can also use the <placeholder-2/> client to list images, "
-"set and delete image metadata, delete images, and take a snapshot of a "
-"running instance to create an image. After you upload an image, you cannot "
-"change it."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml16(para)
-msgid ""
-"For details about image creation, see the <link "
-"href=\"http://docs.openstack.org/image-guide/content/\"><citetitle>Virtual "
-"Machine Image Guide</citetitle></link>."
-msgstr "イメージの作成に関する詳細は<link href=\"http://docs.openstack.org/image-guide/content/\"><citetitle>仮想マシンイメージガイド</citetitle></link>を参照してください。"
-
-#: ./doc/common/section_cli_glance_manage_images.xml21(title)
-msgid "List or get details for images (glance)"
-msgstr "イメージ (glance) の詳細の一覧表示と取得"
-
-#: ./doc/common/section_cli_glance_manage_images.xml22(para)
-msgid ""
-"To get a list of images and to then get further details about a single "
-"image, use <placeholder-1/> and <placeholder-2/>."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml74(para)
-msgid ""
-"When viewing a list of images, you can also use <placeholder-1/> to filter "
-"the list, as follows:"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml80(para)
-msgid ""
-"To store location metadata for images, which enables direct file access for "
-"a client, update the <filename>/etc/glance/glance.conf</filename> file with "
-"the following statements:"
-msgstr "イメージの場所のメタデータを保存してクライアントが直接ファイルにアクセスできるようにするには、<filename>/etc/glance/glance.conf</filename> ファイルで以下のステートメントを追加更新します。"
-
-#: ./doc/common/section_cli_glance_manage_images.xml87(code)
-msgid "show_multiple_locations = True"
-msgstr "show_multiple_locations = True"
-
-#: ./doc/common/section_cli_glance_manage_images.xml90(para)
-msgid ""
-"<code>filesystem_store_metadata_file = "
-"<replaceable>filePath</replaceable></code>, where "
-"<replaceable>filePath</replaceable> points to a JSON file that defines the "
-"mount point for OpenStack images on your system and a unique ID. For "
-"example: <placeholder-1/>"
-msgstr "<code>filesystem_store_metadata_file = <replaceable>filePath</replaceable></code>。<replaceable>filePath</replaceable> は、お使いのシステムの OpenStack イメージのマウントポイントを定義する JSON ファイルおよび一意な ID を参照するようにします。例: <placeholder-1/>"
-
-#: ./doc/common/section_cli_glance_manage_images.xml102(para)
-msgid ""
-"After you restart the Image Service, you can use the following syntax to "
-"view the image's location information:"
-msgstr "Image Service を再起動してから、以下の構文を使用してイメージの場所情報を確認します。"
-
-#: ./doc/common/section_cli_glance_manage_images.xml103(replaceable)
-msgid "imageID"
-msgstr "imageID"
-
-#: ./doc/common/section_cli_glance_manage_images.xml104(para)
-msgid ""
-"For example, using the image ID shown above, you would issue the command as "
-"follows:"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml109(title)
-msgid "Create or update an image (glance)"
-msgstr "イメージ (glance) の作成・更新"
-
-#: ./doc/common/section_cli_glance_manage_images.xml110(para)
-msgid "To create an image, use <placeholder-1/>:"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml111(replaceable)
-#: ./doc/common/section_cli_glance_manage_images.xml114(replaceable)
-msgid "imageName"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml112(para)
-msgid "To update an image by name or ID, use <placeholder-1/>:"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml116(para)
-msgid ""
-"The following table lists the optional arguments that you can use with the "
-"<placeholder-1/> and <placeholder-2/> commands to modify image properties. "
-"For more information, refer to Image Service chapter in the <link "
-"href=\"http://docs.openstack.org/cli-"
-"reference/content/index.html\">OpenStack Command-Line Interface "
-"Reference</link>."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml126(parameter)
-msgid "--name NAME"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml129(para)
-msgid "The name of the image."
-msgstr "イメージの名前。"
-
-#: ./doc/common/section_cli_glance_manage_images.xml134(parameter)
-msgid "--disk-format DISK_FORMAT"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml137(para)
-msgid ""
-"The disk format of the image. Acceptable formats are ami, ari, aki, vhd, "
-"vmdk, raw, qcow2, vdi, and iso."
-msgstr "イメージのディスク形式。利用可能な形式は ami、ari、aki、vhd、vmdk、raw、qcow2、vdi、iso です。"
-
-#: ./doc/common/section_cli_glance_manage_images.xml143(parameter)
-msgid "--container-format CONTAINER_FORMAT"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml146(para)
-msgid ""
-"The container format of the image. Acceptable formats are ami, ari, aki, "
-"bare, and ovf."
-msgstr "イメージのコンテナー形式。対応形式は ami、ari、aki、bare、ovf です。"
-
-#: ./doc/common/section_cli_glance_manage_images.xml152(parameter)
-msgid "--owner TENANT_ID"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml155(para)
-msgid "The tenant who should own the image."
-msgstr "イメージを所有するプロジェクト。"
-
-#: ./doc/common/section_cli_glance_manage_images.xml160(parameter)
-msgid "--size SIZE"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml163(para)
-msgid "The size of image data, in bytes."
-msgstr "イメージデータの容量。バイト単位。"
-
-#: ./doc/common/section_cli_glance_manage_images.xml168(parameter)
-msgid "--min-disk DISK_GB"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml171(para)
-msgid "The minimum size of the disk needed to boot the image, in gigabytes."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml177(parameter)
-msgid "--min-ram DISK_RAM"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml180(para)
-msgid "The minimum amount of RAM needed to boot the image, in megabytes."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml185(parameter)
-msgid "--location IMAGE_URL"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml188(para)
-msgid ""
-"The URL where the data for this image resides. For example, if the image "
-"data is stored in swift, you could specify "
-"<literal>swift://account:key@example.com/container/obj</literal>."
-msgstr "このイメージのデータが格納されている URL。例えば、イメージデータが swift に格納されている場合 <literal>swift://account:key@example.com/container/obj</literal> を指定します。"
-
-#: ./doc/common/section_cli_glance_manage_images.xml195(parameter)
-msgid "--file FILE"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml198(para)
-msgid ""
-"Local file that contains the disk image to be uploaded during the update. "
-"Alternatively, you can pass images to the client through stdin."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml204(parameter)
-msgid "--checksum CHECKSUM"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml207(para)
-msgid "Hash of image data to use for verification."
-msgstr "イメージデータの検証に使用するハッシュ。"
-
-#: ./doc/common/section_cli_glance_manage_images.xml212(parameter)
-msgid "--copy-from IMAGE_URL"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml215(para)
-msgid ""
-"Similar to <parameter>--location</parameter> in usage, but indicates that "
-"the image server should immediately copy the data and store it in its "
-"configured image store."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml222(parameter)
-msgid "--is-public [True|False]"
-msgstr "--is-public [True|False]"
-
-#: ./doc/common/section_cli_glance_manage_images.xml225(para)
-msgid "Makes an image accessible for all the tenants."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml230(parameter)
-msgid "--is-protected [True|False]"
-msgstr "--is-protected [True|False]"
-
-#: ./doc/common/section_cli_glance_manage_images.xml233(para)
-msgid "Prevents an image from being deleted."
-msgstr "イメージが削除されることを防ぎます。"
-
-#: ./doc/common/section_cli_glance_manage_images.xml238(parameter)
-msgid "--property KEY=VALUE"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml241(para)
-msgid ""
-"Arbitrary property to associate with image. This option can be used multiple"
-" times."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml247(parameter)
-msgid "--purge-props"
-msgstr "--purge-props"
-
-#: ./doc/common/section_cli_glance_manage_images.xml250(para)
-msgid ""
-"Deletes all image properties that are not explicitly set in the update "
-"request. Otherwise, those properties not referenced are preserved."
-msgstr "更新要求に明示的に設定されていないイメージのプロパティをすべて削除します。そうでない場合は、参照されていないプロパティは保存されます。"
-
-#: ./doc/common/section_cli_glance_manage_images.xml256(parameter)
-msgid "--human-readable"
-msgstr "--human-readable"
-
-#: ./doc/common/section_cli_glance_manage_images.xml259(para)
-msgid "Prints the image size in a human-friendly format."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml263(para)
-msgid ""
-"The following example shows the command that you would use to upload a "
-"CentOS 6.3 image in qcow2 format and configure it for public access:"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml267(para)
-msgid ""
-"The following example shows how to update an existing image with a "
-"properties that describe the disk bus, the CD-ROM bus, and the VIF model:"
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml274(para)
-msgid ""
-"Currently the libvirt virtualization tool determines the disk, CD-ROM, and "
-"VIF device models based on the configured hypervisor type "
-"(<literal>libvirt_type</literal> in "
-"<filename>/etc/nova/nova.conf</filename>). For the sake of optimal "
-"performance, libvirt defaults to using virtio for both disk and VIF (NIC) "
-"models. The disadvantage of this approach is that it is not possible to run "
-"operating systems that lack virtio drivers, for example, BSD, Solaris, and "
-"older versions of Linux and Windows."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml280(para)
-msgid ""
-"If you specify a disk or CD-ROM bus model that is not supported, see <xref "
-"linkend=\"bus_models\"/>. If you specify a VIF model that is not supported, "
-"the instance fails to launch. See <xref linkend=\"vif_models\"/>."
-msgstr "サポートされていないディスクや CD-ROM バスモデルを指定する場合、<xref linkend=\"bus_models\"/>を参照してください。サポートされていない VIF モデルを指定する場合、インスタンスは起動できません。<xref linkend=\"vif_models\"/>を参照してください。"
-
-#: ./doc/common/section_cli_glance_manage_images.xml284(para)
-msgid ""
-"The valid model values depend on the <literal>libvirt_type</literal> "
-"setting, as shown in the following tables."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml287(caption)
-msgid "Disk and CD-ROM bus model values"
-msgstr "ディスクと CD-ROM のバスモデルの値"
-
-#: ./doc/common/section_cli_glance_manage_images.xml292(th)
-#: ./doc/common/section_cli_glance_manage_images.xml336(th)
-msgid "libvirt_type setting"
-msgstr "libvirt_type 設定"
-
-#: ./doc/common/section_cli_glance_manage_images.xml293(th)
-#: ./doc/common/section_cli_glance_manage_images.xml337(th)
-msgid "Supported model values"
-msgstr "サポートされるモデルの値"
-
-#: ./doc/common/section_cli_glance_manage_images.xml298(td)
-#: ./doc/common/section_cli_glance_manage_images.xml342(td)
-msgid "qemu or kvm"
-msgstr "qemu または kvm"
-
-#: ./doc/common/section_cli_glance_manage_images.xml303(para)
-#: ./doc/common/section_cli_glance_manage_images.xml320(para)
-msgid "ide"
-msgstr "ide"
-
-#: ./doc/common/section_cli_glance_manage_images.xml306(para)
-msgid "scsi"
-msgstr "scsi"
-
-#: ./doc/common/section_cli_glance_manage_images.xml309(para)
-#: ./doc/common/section_cli_glance_manage_images.xml359(para)
-msgid "virtio"
-msgstr "virtio"
-
-#: ./doc/common/section_cli_glance_manage_images.xml316(td)
-#: ./doc/common/section_cli_glance_manage_images.xml323(para)
-#: ./doc/common/section_cli_glance_manage_images.xml366(td)
-msgid "xen"
-msgstr "xen"
-
-#: ./doc/common/section_cli_glance_manage_images.xml331(caption)
-msgid "VIF model values"
-msgstr "仮想インターフェースのモデルの値"
-
-#: ./doc/common/section_cli_glance_manage_images.xml347(para)
-#: ./doc/common/section_cli_glance_manage_images.xml370(para)
-msgid "e1000"
-msgstr "e1000"
-
-#: ./doc/common/section_cli_glance_manage_images.xml350(para)
-#: ./doc/common/section_cli_glance_manage_images.xml376(para)
-msgid "ne2k_pci"
-msgstr "ne2k_pci"
-
-#: ./doc/common/section_cli_glance_manage_images.xml353(para)
-#: ./doc/common/section_cli_glance_manage_images.xml379(para)
-msgid "pcnet"
-msgstr "pcnet"
-
-#: ./doc/common/section_cli_glance_manage_images.xml356(para)
-#: ./doc/common/section_cli_glance_manage_images.xml382(para)
-msgid "rtl8139"
-msgstr "rtl8139"
-
-#: ./doc/common/section_cli_glance_manage_images.xml373(para)
-msgid "netfront"
-msgstr "netfront"
-
-#: ./doc/common/section_cli_glance_manage_images.xml388(td)
-msgid "vmware"
-msgstr "vmware"
-
-#: ./doc/common/section_cli_glance_manage_images.xml393(para)
-msgid "VirtualE1000"
-msgstr "VirtualE1000"
-
-#: ./doc/common/section_cli_glance_manage_images.xml396(para)
-msgid "VirtualPCNet32"
-msgstr "VirtualPCNet32"
-
-#: ./doc/common/section_cli_glance_manage_images.xml399(para)
-msgid "VirtualVmxnet"
-msgstr "VirtualVmxnet"
-
-#: ./doc/common/section_cli_glance_manage_images.xml410(title)
-#: ./doc/common/section_cli_nova_images.xml125(title)
-msgid "Troubleshoot image creation"
-msgstr "イメージ作成のトラブルシューティング"
-
-#: ./doc/common/section_cli_glance_manage_images.xml411(para)
-msgid ""
-"If you encounter problems in creating an image in Image Service or Compute, "
-"the following information may help you troubleshoot the creation process."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml415(para)
-msgid ""
-"Ensure that the version of qemu you are using is version 0.14 or later. "
-"Earlier versions of qemu result in an <literal>unknown option -s</literal> "
-"error message in the <filename>nova-compute.log</filename> file."
-msgstr ""
-
-#: ./doc/common/section_cli_glance_manage_images.xml420(para)
-#: ./doc/common/section_cli_nova_images.xml140(para)
-msgid ""
-"Examine the <filename>/var/log/nova-api.log</filename> and "
-"<filename>/var/log/nova-compute.log</filename> log files for error messages."
-msgstr "エラーメッセージは <filename>/var/log/nova-api.log</filename> と <filename>/var/log/nova-compute.log</filename> ログファイルを確認します。"
-
-#: ./doc/common/section_cli_nova_manage_images.xml6(title)
-msgid "Create an image (nova)"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_manage_images.xml7(para)
-msgid ""
-"You can use the <placeholder-1/> client to take a snapshot of a running "
-"instance to create an image."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_manage_images.xml9(para)
-msgid ""
-"To minimize the potential for data loss and ensure that you create an "
-"accurate image, you should shut down the instance before you take a "
-"snapshot."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_manage_images.xml12(para)
-msgid ""
-"You cannot create a snapshot from an instance that has an attached volume. "
-"Detach the volume, create the image, and remount the volume."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_manage_images.xml17(para)
-#: ./doc/common/section_cli_nova_images.xml18(para)
-msgid "Write any buffered data to disk."
-msgstr "バッファーデータをディスクに書き込みます。"
-
-#: ./doc/common/section_cli_nova_manage_images.xml18(para)
-msgid ""
-"For more information, see <link href=\"http://docs.openstack.org/trunk"
-"/openstack-ops/content/snapshots.html\">Taking Snapshots</link> in the "
-"<citetitle>OpenStack Operations Guide</citetitle>."
-msgstr "詳細情報は、<citetitle>OpenStack 運用ガイド</citetitle> の<link href=\"http://docs.openstack.org/trunk/openstack-ops/content/snapshots.html\">スナップショットの作成方法</link>を参照してください。"
-
-#: ./doc/common/section_cli_nova_manage_images.xml24(para)
-msgid "List instances to get the server name:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_manage_images.xml31(para)
-msgid ""
-"In this example, the server is named <literal>myCirrosServer</literal>."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_manage_images.xml33(para)
-msgid ""
-"Use this server to create a snapshot: <placeholder-1/>The command creates a "
-"qemu snapshot and automatically uploads the image to your repository. Only "
-"the tenant that creates the image has access to it."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_manage_images.xml40(para)
-#: ./doc/common/section_cli_nova_images.xml43(para)
-msgid "Get details for your image to check its status:"
-msgstr "イメージの詳細を取得して状態を確認します。"
-
-#: ./doc/common/section_cli_nova_manage_images.xml75(para)
-#: ./doc/common/section_cli_nova_images.xml79(para)
-msgid ""
-"The image status changes from <literal>SAVING</literal> to "
-"<literal>ACTIVE</literal>. Only the tenant who creates the image has access "
-"to it."
-msgstr "イメージの状態は <literal>SAVING</literal> から <literal>ACTIVE</literal> に変わります。イメージを作成したテナントのみがこのイメージにアクセスできます。"
-
-#: ./doc/common/section_cli_nova_manage_images.xml81(para)
-msgid ""
-"To launch an instance from your image, include the image ID and flavor ID, "
-"as in the following example:"
-msgstr ""
-
 #. When image changes, this message will be marked fuzzy or untranslated for
 #. you.
 #. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_compute-configure-vnc.xml63(None)
+#: ./doc/common/section_getstart_dashboard.xml14(None)
 msgid ""
-"@@image: '../common/figures/novnc/SCH_5009_V00_NUAC-VNC_OpenStack.png'; "
-"md5=182dc38019a220c851e1c94aa50f4565"
-msgstr "@@image: '../common/figures/novnc/SCH_5009_V00_NUAC-VNC_OpenStack.png'; md5=182dc38019a220c851e1c94aa50f4565"
+"@@image: 'figures/horizon-screenshot.jpg'; "
+"md5=9471047adf0d93713be7f54b9db2b53c"
+msgstr "@@image: 'figures/horizon-screenshot.jpg'; md5=9471047adf0d93713be7f54b9db2b53c"
 
-#: ./doc/common/section_compute-configure-vnc.xml6(title)
-msgid "VNC console proxy"
-msgstr ""
+#: ./doc/common/section_getstart_dashboard.xml5(title)
+msgid "OpenStack dashboard"
+msgstr "OpenStack Dashboard"
 
-#: ./doc/common/section_compute-configure-vnc.xml7(para)
+#: ./doc/common/section_getstart_dashboard.xml6(para)
 msgid ""
-"The VNC proxy is an OpenStack component that enables compute service users "
-"to access their instances through VNC clients."
+"The OpenStack dashboard is a modular <link "
+"href=\"https://www.djangoproject.com/\">Django web application</link> that "
+"provides a graphical interface to OpenStack services."
 msgstr ""
 
-#: ./doc/common/section_compute-configure-vnc.xml10(para)
-msgid "The VNC console connection works as follows:"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml13(para)
+#: ./doc/common/section_getstart_dashboard.xml18(para)
 msgid ""
-"A user connects to the API and gets an <literal>access_url</literal> such "
-"as, <literal>http://<replaceable>ip:port</replaceable>/?token=xyz</literal>."
+"The dashboard is usually deployed through <link "
+"href=\"http://code.google.com/p/modwsgi/\">mod_wsgi</link> in Apache. You "
+"can modify the dashboard code to make it suitable for different sites."
 msgstr ""
 
-#: ./doc/common/section_compute-configure-vnc.xml19(para)
-msgid "The user pastes the URL in a browser or uses it as a client parameter."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml23(para)
-msgid "The browser or client connects to the proxy."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml26(para)
+#: ./doc/common/section_getstart_dashboard.xml22(para)
 msgid ""
-"The proxy talks to <systemitem class=\"service\">nova-"
-"consoleauth</systemitem> to authorize the token for the user, and maps the "
-"token to the <emphasis>private</emphasis> host and port of the VNC server "
-"for an instance."
+"From a network architecture point of view, this service must be accessible "
+"to customers and the public API for each OpenStack service. To use the "
+"administrator functionality for other services, it must also connect to "
+"Admin API endpoints, which should not be accessible by customers."
 msgstr ""
 
-#: ./doc/common/section_compute-configure-vnc.xml31(para)
+#: ./doc/common/section_cli_nova_reboot.xml5(title)
+msgid "Reboot an instance"
+msgstr "インスタンスの再起動"
+
+#: ./doc/common/section_cli_nova_reboot.xml6(para)
 msgid ""
-"The compute host specifies the address that the proxy should use to connect "
-"through the <filename>nova.conf</filename> file option, "
-"<option>vncserver_proxyclient_address</option>. In this way, the VNC proxy "
-"works as a bridge between the public network and private host network."
-msgstr ""
+"You can soft or hard reboot a running instance. A soft reboot attempts a "
+"graceful shut down and restart of the instance. A hard reboot power cycles "
+"the instance."
+msgstr "実行中のインスタンスのソフトリブートまたはハードリブートを行うことができます。ソフトリブートは、グレースフルシャットダウンの後インスタンスの再起動を試行します。ハードリブートは、インスタンスの電源を一旦切って再投入します。"
 
-#: ./doc/common/section_compute-configure-vnc.xml39(para)
+#: ./doc/common/section_cli_nova_reboot.xml9(para)
+msgid "By default, when you reboot a server, it is a soft reboot."
+msgstr "デフォルトでは、サーバーをリブートする場合ソフトリブートとなっています。"
+
+#: ./doc/common/section_cli_nova_reboot.xml10(replaceable)
+#: ./doc/common/section_cli_nova_reboot.xml12(replaceable)
+msgid "SERVER"
+msgstr "SERVER"
+
+#: ./doc/common/section_cli_nova_reboot.xml11(para)
 msgid ""
-"The proxy initiates the connection to VNC server and continues to proxy "
-"until the session ends."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml43(para)
-msgid ""
-"The proxy also tunnels the VNC protocol over WebSockets so that the "
-"<systemitem>noVNC</systemitem> client can talk to VNC servers. In general, "
-"the VNC proxy:"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml48(para)
-msgid ""
-"Bridges between the public network where the clients live and the private "
-"network where VNC servers live."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml52(para)
-msgid "Mediates token authentication."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml55(para)
-msgid ""
-"Transparently deals with hypervisor-specific connection details to provide a"
-" uniform client experience."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml58(title)
-msgid "noVNC process"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml71(title)
-msgid "About nova-consoleauth"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml73(para)
-msgid ""
-"Both client proxies leverage a shared service to manage token authentication"
-" called <systemitem class=\"service\">nova-consoleauth</systemitem>. This "
-"service must be running for either proxy to work. Many proxies of either "
-"type can be run against a single <systemitem class=\"service\">nova-"
-"consoleauth</systemitem> service in a cluster configuration."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml80(para)
-msgid ""
-"Do not confuse the <systemitem class=\"service\">nova-"
-"consoleauth</systemitem> shared service with <literal>nova-"
-"console</literal>, which is a XenAPI-specific service that most recent VNC "
-"proxy architectures do not use."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml87(title)
-msgid "Typical deployment"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml88(para)
-msgid "A typical deployment has the following components:"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml91(para)
-msgid ""
-"A <systemitem class=\"service\">nova-consoleauth</systemitem> process. "
-"Typically runs on the controller host."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml96(para)
-msgid ""
-"One or more <systemitem class=\"service\">nova-novncproxy</systemitem> "
-"services. Supports browser-based noVNC clients. For simple deployments, this"
-" service typically runs on the same machine as <systemitem class=\"service"
-"\">nova-api</systemitem> because it operates as a proxy between the public "
-"network and the private compute host network."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml105(para)
-msgid ""
-"One or more <literal>nova-xvpvncproxy</literal> services. Supports the "
-"special Java client discussed here. For simple deployments, this service "
-"typically runs on the same machine as <systemitem class=\"service\">nova-"
-"api</systemitem> because it acts as a proxy between the public network and "
-"the private compute host network."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml114(para)
-msgid ""
-"One or more compute hosts. These compute hosts must have correctly "
-"configured options, as follows."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml120(title)
-msgid "VNC configuration options"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml121(para)
-msgid "To customize the VNC console, use the following configuration options:"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml124(para)
-msgid ""
-"To support <link href=\"http://docs.openstack.org/trunk/config-"
-"reference/content/configuring-openstack-compute-basics.html"
-"#section_configuring-compute-migrations\">live migration</link>, you cannot "
-"specify a specific IP address for <literal>vncserver_listen</literal>, "
-"because that IP address does not exist on the destination host."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml134(para)
-msgid ""
-"The <literal>vncserver_proxyclient_address</literal> defaults to "
-"<literal>127.0.0.1</literal>, which is the address of the compute host that "
-"Compute instructs proxies to use when connecting to instance servers."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml139(para)
-msgid "For all-in-one XenServer domU deployments, set this to 169.254.0.1."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml140(para)
-msgid ""
-"For multi-host XenServer domU deployments, set to a dom0 management IP on "
-"the same network as the proxies."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml142(para)
-msgid ""
-"For multi-host libvirt deployments, set to a host management IP on the same "
-"network as the proxies."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml150(title)
-msgid "nova-novncproxy (noVNC)"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml152(para)
-msgid ""
-"You must install the <package>noVNC</package> package, which contains the "
-"<systemitem class=\"service\">nova-novncproxy</systemitem> service. As root,"
-" run the following command:"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml156(para)
-msgid "The service starts automatically on installation."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml157(para)
-msgid "To restart the service, run:"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml159(para)
-msgid ""
-"The configuration option parameter should point to your "
-"<filename>nova.conf</filename> file, which includes the message queue server"
-" address and credentials."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml162(para)
-msgid ""
-"By default, <systemitem class=\"service\">nova-novncproxy</systemitem> binds"
-" on <literal>0.0.0.0:6080</literal>."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml165(para)
-msgid ""
-"To connect the service to your Compute deployment, add the following "
-"configuration options to your <filename>nova.conf</filename> file:"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml169(para)
-msgid "<literal>vncserver_listen</literal>=<replaceable>0.0.0.0</replaceable>"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml172(para)
-msgid ""
-"Specifies the address on which the VNC service should bind. Make sure it is "
-"assigned one of the compute node interfaces. This address is the one used by"
-" your domain file."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml178(para)
-msgid ""
-"To use live migration, use the <replaceable>0.0.0.0</replaceable> address."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml183(para)
-msgid ""
-"<literal>vncserver_proxyclient_address</literal>=<replaceable>127.0.0.1</replaceable>"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml186(para)
-msgid ""
-"The address of the compute host that Compute instructs proxies to use when "
-"connecting to instance <literal>vncservers</literal>."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml193(title)
-msgid "Frequently asked questions about VNC access to virtual machines"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml199(literal)
-msgid "nova-xvpvncproxy"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml200(systemitem)
-msgid "nova-novncproxy"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml198(emphasis)
-msgid ""
-"Q: What is the difference between <placeholder-1/> and <placeholder-2/>?"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml202(para)
-msgid ""
-"A: <literal>nova-xvpvncproxy</literal>, which ships with OpenStack Compute, "
-"is a proxy that supports a simple Java client. <systemitem class=\"service"
-"\">nova-novncproxy</systemitem> uses noVNC to provide VNC support through a "
-"web browser."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml208(emphasis)
-msgid ""
-"Q: I want VNC support in the OpenStack dashboard. What services do I need?"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml210(para)
-msgid ""
-"A: You need <systemitem class=\"service\">nova-novncproxy</systemitem>, "
-"<systemitem class=\"service\">nova-consoleauth</systemitem>, and correctly "
-"configured compute hosts."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml216(emphasis)
-msgid ""
-"Q: When I use <placeholder-1/> or click on the VNC tab of the OpenStack "
-"dashboard, it hangs. Why?"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml218(para)
-msgid ""
-"A: Make sure you are running <systemitem class=\"service\">nova-"
-"consoleauth</systemitem> (in addition to <systemitem class=\"service\">nova-"
-"novncproxy</systemitem>). The proxies rely on <systemitem class=\"service"
-"\">nova-consoleauth</systemitem> to validate tokens, and waits for a reply "
-"from them until a timeout is reached."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml227(emphasis)
-msgid ""
-"Q: My VNC proxy worked fine during my all-in-one test, but now it doesn't "
-"work on multi host. Why?"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml230(para)
-msgid ""
-"A: The default options work for an all-in-one install, but changes must be "
-"made on your compute hosts once you start to build a cluster. As an example,"
-" suppose you have two servers:"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml236(para)
-msgid ""
-"Your <systemitem class=\"service\">nova-compute</systemitem> configuration "
-"file must set the following values:"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml248(para)
-msgid ""
-"<literal>novncproxy_base_url</literal> and "
-"<literal>xvpvncproxy_base_url</literal> use a public IP; this is the URL "
-"that is ultimately returned to clients, which generally do not have access "
-"to your private network. Your PROXYSERVER must be able to reach "
-"<literal>vncserver_proxyclient_address</literal>, because that is the "
-"address over which the VNC connection is proxied."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml260(emphasis)
-msgid "Q: My noVNC does not work with recent versions of web browsers. Why?"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml263(para)
-msgid ""
-"A: Make sure you have installed <literal>python-numpy</literal>, which is "
-"required to support a newer version of the WebSocket protocol (HyBi-07+)."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml270(emphasis)
-msgid ""
-"Q: How do I adjust the dimensions of the VNC window image in the OpenStack "
-"dashboard?"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml273(para)
-msgid ""
-"A: These values are hard-coded in a Django HTML template. To alter them, "
-"edit the <filename>_detail_vnc.html</filename> template file. The location "
-"of this file varies based on Linux distribution. On Ubuntu 12.04, the file "
-"is at "
-"<filename>/usr/share/pyshared/horizon/dashboards/nova/instances/templates/instances/_detail_vnc.html</filename>."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-vnc.xml279(para)
-msgid ""
-"Modify the <option>width</option> and <option>height</option> options, as "
-"follows:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml6(title)
-msgid "Change the size of your server"
-msgstr "サーバーの大きさの変更"
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml7(para)
-msgid "You change the size of a server by changing its flavor."
-msgstr "フレーバーを変更することでサーバーの大きさを変更します。"
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml10(para)
-msgid ""
-"Show information about your server, including its size, which is shown as "
-"the value of the flavor property."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml43(para)
-msgid "The size (flavor) of the server is <literal>m1.small (2)</literal>."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml46(para)
-msgid "List the available flavors with the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml59(para)
-msgid ""
-"To resize the server, pass the server ID or name and the new flavor to the "
-"<placeholder-1/> command. Include the <literal>--poll</literal> parameter to"
-" report the resize progress."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml67(para)
-msgid "Show the status for your server:"
-msgstr "サーバーの状態を表示します。"
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml74(para)
-msgid "When the resize completes, the status becomes VERIFY_RESIZE."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml77(para)
-msgid "Confirm the resize:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml79(para)
-#: ./doc/common/section_cli_nova_resizerebuild.xml85(para)
-msgid "The server status becomes ACTIVE."
-msgstr "サーバーの状態が ACTIVE に変わります。"
-
-#: ./doc/common/section_cli_nova_resizerebuild.xml82(para)
-msgid ""
-"If the resize fails or does not work as expected, you can revert the resize:"
-msgstr "リサイズに失敗した場合や予想通りにリサイズが行われなかった場合、リサイズを元に戻すことができます。"
+"To perform a hard reboot, pass the <parameter>--hard</parameter> parameter, "
+"as follows:"
+msgstr "ハードリブートを実行するには、以下のように <parameter>--hard</parameter> パラメーターを指定します。"
 
 #: ./doc/common/ch_cli_nova_commands.xml11(title)
 msgid "Compute command-line client"
@@ -1291,38 +90,38 @@ msgid ""
 msgstr ""
 
 #: ./doc/common/ch_cli_nova_commands.xml16(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml16(para)
 #: ./doc/common/ch_cli_neutron_commands.xml16(para)
-#: ./doc/common/ch_cli_keystone_commands.xml16(para)
-#: ./doc/common/ch_cli_swift_commands.xml16(para)
-#: ./doc/common/ch_cli_cinder_commands.xml16(para)
-#: ./doc/common/ch_cli_glance_commands.xml16(para)
 #: ./doc/common/ch_cli_heat_commands.xml16(para)
+#: ./doc/common/ch_cli_swift_commands.xml16(para)
+#: ./doc/common/ch_cli_glance_commands.xml16(para)
+#: ./doc/common/ch_cli_keystone_commands.xml16(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml16(para)
+#: ./doc/common/ch_cli_cinder_commands.xml16(para)
 #: ./doc/common/ch_cli_trove_commands.xml16(para)
 msgid "For help on a specific <placeholder-1/> command, enter:"
 msgstr ""
 
 #: ./doc/common/ch_cli_nova_commands.xml19(option)
-#: ./doc/common/ch_cli_ceilometer_commands.xml19(option)
 #: ./doc/common/ch_cli_neutron_commands.xml19(option)
-#: ./doc/common/ch_cli_keystone_commands.xml19(option)
-#: ./doc/common/ch_cli_swift_commands.xml19(option)
-#: ./doc/common/ch_cli_cinder_commands.xml19(option)
-#: ./doc/common/ch_cli_glance_commands.xml19(option)
 #: ./doc/common/ch_cli_heat_commands.xml19(option)
+#: ./doc/common/ch_cli_swift_commands.xml19(option)
+#: ./doc/common/ch_cli_glance_commands.xml19(option)
+#: ./doc/common/ch_cli_keystone_commands.xml19(option)
+#: ./doc/common/ch_cli_ceilometer_commands.xml19(option)
+#: ./doc/common/ch_cli_cinder_commands.xml19(option)
 #: ./doc/common/ch_cli_trove_commands.xml19(option)
 msgid "help"
 msgstr ""
 
 #: ./doc/common/ch_cli_nova_commands.xml19(replaceable)
-#: ./doc/common/ch_cli_ceilometer_commands.xml19(replaceable)
 #: ./doc/common/ch_cli_neutron_commands.xml19(replaceable)
-#: ./doc/common/ch_cli_keystone_commands.xml19(replaceable)
+#: ./doc/common/ch_cli_heat_commands.xml19(replaceable)
 #: ./doc/common/ch_cli_swift_commands.xml19(replaceable)
 #: ./doc/common/section_cli_keystone_example_usage.xml12(replaceable)
-#: ./doc/common/ch_cli_cinder_commands.xml19(replaceable)
 #: ./doc/common/ch_cli_glance_commands.xml19(replaceable)
-#: ./doc/common/ch_cli_heat_commands.xml19(replaceable)
+#: ./doc/common/ch_cli_keystone_commands.xml19(replaceable)
+#: ./doc/common/ch_cli_ceilometer_commands.xml19(replaceable)
+#: ./doc/common/ch_cli_cinder_commands.xml19(replaceable)
 #: ./doc/common/ch_cli_trove_commands.xml19(replaceable)
 msgid "COMMAND"
 msgstr ""
@@ -1332,12 +131,12 @@ msgid "nova usage"
 msgstr ""
 
 #: ./doc/common/ch_cli_nova_commands.xml37(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml38(title)
-#: ./doc/common/ch_cli_keystone_commands.xml37(title)
-#: ./doc/common/ch_cli_swift_commands.xml37(title)
-#: ./doc/common/ch_cli_cinder_commands.xml35(title)
-#: ./doc/common/ch_cli_glance_commands.xml39(title)
 #: ./doc/common/ch_cli_heat_commands.xml35(title)
+#: ./doc/common/ch_cli_swift_commands.xml37(title)
+#: ./doc/common/ch_cli_glance_commands.xml39(title)
+#: ./doc/common/ch_cli_keystone_commands.xml37(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml38(title)
+#: ./doc/common/ch_cli_cinder_commands.xml35(title)
 #: ./doc/common/ch_cli_trove_commands.xml35(title)
 msgid "Subcommands"
 msgstr ""
@@ -2178,11 +977,11 @@ msgid ""
 msgstr ""
 
 #: ./doc/common/ch_cli_nova_commands.xml1326(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml261(para)
-#: ./doc/common/ch_cli_keystone_commands.xml332(para)
-#: ./doc/common/ch_cli_cinder_commands.xml575(para)
-#: ./doc/common/ch_cli_glance_commands.xml203(para)
 #: ./doc/common/ch_cli_heat_commands.xml311(para)
+#: ./doc/common/ch_cli_glance_commands.xml203(para)
+#: ./doc/common/ch_cli_keystone_commands.xml332(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml261(para)
+#: ./doc/common/ch_cli_cinder_commands.xml575(para)
 msgid "Display help about this program or one of its subcommands."
 msgstr ""
 
@@ -2303,11 +1102,11 @@ msgid "nova optional arguments"
 msgstr ""
 
 #: ./doc/common/ch_cli_nova_commands.xml1519(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml275(para)
 #: ./doc/common/ch_cli_neutron_commands.xml38(para)
 #: ./doc/common/ch_cli_swift_commands.xml115(para)
-#: ./doc/common/ch_cli_cinder_commands.xml597(para)
 #: ./doc/common/ch_cli_glance_commands.xml217(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml275(para)
+#: ./doc/common/ch_cli_cinder_commands.xml597(para)
 #: ./doc/common/ch_cli_trove_commands.xml446(para)
 msgid "show program's version number and exit"
 msgstr ""
@@ -2337,49 +1136,49 @@ msgid "Defaults to <code>env[OS_AUTH_TOKEN]</code>"
 msgstr ""
 
 #: ./doc/common/ch_cli_nova_commands.xml1568(para)
+#: ./doc/common/ch_cli_heat_commands.xml399(para)
 #: ./doc/common/ch_cli_ceilometer_commands.xml357(para)
 #: ./doc/common/ch_cli_cinder_commands.xml613(para)
-#: ./doc/common/ch_cli_heat_commands.xml399(para)
 #: ./doc/common/ch_cli_trove_commands.xml462(para)
 msgid "Defaults to <code>env[OS_USERNAME]</code>."
 msgstr ""
 
 #: ./doc/common/ch_cli_nova_commands.xml1576(para)
+#: ./doc/common/ch_cli_heat_commands.xml407(para)
 #: ./doc/common/ch_cli_ceilometer_commands.xml365(para)
 #: ./doc/common/ch_cli_cinder_commands.xml621(para)
-#: ./doc/common/ch_cli_heat_commands.xml407(para)
 #: ./doc/common/ch_cli_trove_commands.xml470(para)
 msgid "Defaults to <code>env[OS_PASSWORD]</code>."
 msgstr ""
 
 #: ./doc/common/ch_cli_nova_commands.xml1584(para)
+#: ./doc/common/ch_cli_heat_commands.xml423(para)
 #: ./doc/common/ch_cli_ceilometer_commands.xml381(para)
 #: ./doc/common/ch_cli_cinder_commands.xml629(para)
-#: ./doc/common/ch_cli_heat_commands.xml423(para)
 #: ./doc/common/ch_cli_trove_commands.xml478(para)
 msgid "Defaults to <code>env[OS_TENANT_NAME]</code>."
 msgstr ""
 
 #: ./doc/common/ch_cli_nova_commands.xml1592(para)
+#: ./doc/common/ch_cli_heat_commands.xml415(para)
 #: ./doc/common/ch_cli_ceilometer_commands.xml373(para)
 #: ./doc/common/ch_cli_cinder_commands.xml637(para)
-#: ./doc/common/ch_cli_heat_commands.xml415(para)
 #: ./doc/common/ch_cli_trove_commands.xml486(para)
 msgid "Defaults to <code>env[OS_TENANT_ID]</code>."
 msgstr ""
 
 #: ./doc/common/ch_cli_nova_commands.xml1600(para)
+#: ./doc/common/ch_cli_heat_commands.xml431(para)
 #: ./doc/common/ch_cli_ceilometer_commands.xml389(para)
 #: ./doc/common/ch_cli_cinder_commands.xml645(para)
-#: ./doc/common/ch_cli_heat_commands.xml431(para)
 #: ./doc/common/ch_cli_trove_commands.xml494(para)
 msgid "Defaults to <code>env[OS_AUTH_URL]</code>."
 msgstr ""
 
 #: ./doc/common/ch_cli_nova_commands.xml1608(para)
+#: ./doc/common/ch_cli_heat_commands.xml439(para)
 #: ./doc/common/ch_cli_ceilometer_commands.xml397(para)
 #: ./doc/common/ch_cli_cinder_commands.xml653(para)
-#: ./doc/common/ch_cli_heat_commands.xml439(para)
 #: ./doc/common/ch_cli_trove_commands.xml502(para)
 msgid "Defaults to <code>env[OS_REGION_NAME]</code>."
 msgstr ""
@@ -2485,30 +1284,6 @@ msgstr ""
 #: ./doc/common/ch_cli_nova_commands.xml6347(title)
 #: ./doc/common/ch_cli_nova_commands.xml6448(title)
 #: ./doc/common/ch_cli_nova_commands.xml6496(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml462(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml604(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml749(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml766(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml793(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml812(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml829(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml846(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml887(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1077(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1282(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1471(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1490(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1514(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1534(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1570(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1606(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1642(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1661(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1684(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1767(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1803(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1856(title)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1874(title)
 #: ./doc/common/ch_cli_neutron_commands.xml1434(title)
 #: ./doc/common/ch_cli_neutron_commands.xml1461(title)
 #: ./doc/common/ch_cli_neutron_commands.xml1517(title)
@@ -2662,12 +1437,51 @@ msgstr ""
 #: ./doc/common/ch_cli_neutron_commands.xml10279(title)
 #: ./doc/common/ch_cli_neutron_commands.xml10365(title)
 #: ./doc/common/ch_cli_neutron_commands.xml10419(title)
+#: ./doc/common/ch_cli_heat_commands.xml561(title)
+#: ./doc/common/ch_cli_heat_commands.xml739(title)
+#: ./doc/common/ch_cli_heat_commands.xml776(title)
+#: ./doc/common/ch_cli_heat_commands.xml848(title)
+#: ./doc/common/ch_cli_heat_commands.xml946(title)
+#: ./doc/common/ch_cli_heat_commands.xml1040(title)
+#: ./doc/common/ch_cli_heat_commands.xml1090(title)
+#: ./doc/common/ch_cli_heat_commands.xml1187(title)
+#: ./doc/common/ch_cli_heat_commands.xml1264(title)
 #: ./doc/common/ch_cli_swift_commands.xml358(title)
 #: ./doc/common/ch_cli_swift_commands.xml424(title)
 #: ./doc/common/ch_cli_swift_commands.xml527(title)
 #: ./doc/common/ch_cli_swift_commands.xml601(title)
 #: ./doc/common/ch_cli_swift_commands.xml684(title)
 #: ./doc/common/ch_cli_swift_commands.xml723(title)
+#: ./doc/common/ch_cli_glance_commands.xml527(title)
+#: ./doc/common/ch_cli_glance_commands.xml718(title)
+#: ./doc/common/ch_cli_glance_commands.xml862(title)
+#: ./doc/common/ch_cli_glance_commands.xml900(title)
+#: ./doc/common/ch_cli_glance_commands.xml1079(title)
+#: ./doc/common/ch_cli_glance_commands.xml1121(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml462(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml604(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml749(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml766(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml793(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml812(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml829(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml846(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml887(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1077(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1282(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1471(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1490(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1514(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1534(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1570(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1606(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1642(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1661(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1684(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1767(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1803(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1856(title)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1874(title)
 #: ./doc/common/ch_cli_cinder_commands.xml751(title)
 #: ./doc/common/ch_cli_cinder_commands.xml819(title)
 #: ./doc/common/ch_cli_cinder_commands.xml871(title)
@@ -2686,21 +1500,6 @@ msgstr ""
 #: ./doc/common/ch_cli_cinder_commands.xml2089(title)
 #: ./doc/common/ch_cli_cinder_commands.xml2162(title)
 #: ./doc/common/ch_cli_cinder_commands.xml2316(title)
-#: ./doc/common/ch_cli_glance_commands.xml527(title)
-#: ./doc/common/ch_cli_glance_commands.xml718(title)
-#: ./doc/common/ch_cli_glance_commands.xml862(title)
-#: ./doc/common/ch_cli_glance_commands.xml900(title)
-#: ./doc/common/ch_cli_glance_commands.xml1079(title)
-#: ./doc/common/ch_cli_glance_commands.xml1121(title)
-#: ./doc/common/ch_cli_heat_commands.xml561(title)
-#: ./doc/common/ch_cli_heat_commands.xml739(title)
-#: ./doc/common/ch_cli_heat_commands.xml776(title)
-#: ./doc/common/ch_cli_heat_commands.xml848(title)
-#: ./doc/common/ch_cli_heat_commands.xml946(title)
-#: ./doc/common/ch_cli_heat_commands.xml1040(title)
-#: ./doc/common/ch_cli_heat_commands.xml1090(title)
-#: ./doc/common/ch_cli_heat_commands.xml1187(title)
-#: ./doc/common/ch_cli_heat_commands.xml1264(title)
 #: ./doc/common/ch_cli_trove_commands.xml610(title)
 #: ./doc/common/ch_cli_trove_commands.xml653(title)
 #: ./doc/common/ch_cli_trove_commands.xml681(title)
@@ -2992,12 +1791,37 @@ msgstr ""
 #: ./doc/common/ch_cli_neutron_commands.xml10239(title)
 #: ./doc/common/ch_cli_neutron_commands.xml10354(title)
 #: ./doc/common/ch_cli_neutron_commands.xml10408(title)
+#: ./doc/common/ch_cli_heat_commands.xml509(title)
+#: ./doc/common/ch_cli_heat_commands.xml526(title)
+#: ./doc/common/ch_cli_heat_commands.xml550(title)
+#: ./doc/common/ch_cli_heat_commands.xml578(title)
+#: ./doc/common/ch_cli_heat_commands.xml611(title)
+#: ./doc/common/ch_cli_heat_commands.xml628(title)
+#: ./doc/common/ch_cli_heat_commands.xml653(title)
+#: ./doc/common/ch_cli_heat_commands.xml670(title)
+#: ./doc/common/ch_cli_heat_commands.xml695(title)
+#: ./doc/common/ch_cli_heat_commands.xml720(title)
+#: ./doc/common/ch_cli_heat_commands.xml765(title)
+#: ./doc/common/ch_cli_heat_commands.xml800(title)
+#: ./doc/common/ch_cli_heat_commands.xml817(title)
+#: ./doc/common/ch_cli_heat_commands.xml837(title)
+#: ./doc/common/ch_cli_heat_commands.xml935(title)
+#: ./doc/common/ch_cli_heat_commands.xml1022(title)
+#: ./doc/common/ch_cli_heat_commands.xml1079(title)
+#: ./doc/common/ch_cli_heat_commands.xml1157(title)
+#: ./doc/common/ch_cli_heat_commands.xml1176(title)
+#: ./doc/common/ch_cli_heat_commands.xml1246(title)
 #: ./doc/common/ch_cli_swift_commands.xml338(title)
 #: ./doc/common/ch_cli_swift_commands.xml402(title)
 #: ./doc/common/ch_cli_swift_commands.xml516(title)
 #: ./doc/common/ch_cli_swift_commands.xml581(title)
 #: ./doc/common/ch_cli_swift_commands.xml664(title)
 #: ./doc/common/ch_cli_swift_commands.xml703(title)
+#: ./doc/common/ch_cli_glance_commands.xml694(title)
+#: ./doc/common/ch_cli_glance_commands.xml851(title)
+#: ./doc/common/ch_cli_glance_commands.xml889(title)
+#: ./doc/common/ch_cli_glance_commands.xml1060(title)
+#: ./doc/common/ch_cli_glance_commands.xml1096(title)
 #: ./doc/common/ch_cli_cinder_commands.xml740(title)
 #: ./doc/common/ch_cli_cinder_commands.xml784(title)
 #: ./doc/common/ch_cli_cinder_commands.xml808(title)
@@ -3049,31 +1873,6 @@ msgstr ""
 #: ./doc/common/ch_cli_cinder_commands.xml2237(title)
 #: ./doc/common/ch_cli_cinder_commands.xml2254(title)
 #: ./doc/common/ch_cli_cinder_commands.xml2297(title)
-#: ./doc/common/ch_cli_glance_commands.xml694(title)
-#: ./doc/common/ch_cli_glance_commands.xml851(title)
-#: ./doc/common/ch_cli_glance_commands.xml889(title)
-#: ./doc/common/ch_cli_glance_commands.xml1060(title)
-#: ./doc/common/ch_cli_glance_commands.xml1096(title)
-#: ./doc/common/ch_cli_heat_commands.xml509(title)
-#: ./doc/common/ch_cli_heat_commands.xml526(title)
-#: ./doc/common/ch_cli_heat_commands.xml550(title)
-#: ./doc/common/ch_cli_heat_commands.xml578(title)
-#: ./doc/common/ch_cli_heat_commands.xml611(title)
-#: ./doc/common/ch_cli_heat_commands.xml628(title)
-#: ./doc/common/ch_cli_heat_commands.xml653(title)
-#: ./doc/common/ch_cli_heat_commands.xml670(title)
-#: ./doc/common/ch_cli_heat_commands.xml695(title)
-#: ./doc/common/ch_cli_heat_commands.xml720(title)
-#: ./doc/common/ch_cli_heat_commands.xml765(title)
-#: ./doc/common/ch_cli_heat_commands.xml800(title)
-#: ./doc/common/ch_cli_heat_commands.xml817(title)
-#: ./doc/common/ch_cli_heat_commands.xml837(title)
-#: ./doc/common/ch_cli_heat_commands.xml935(title)
-#: ./doc/common/ch_cli_heat_commands.xml1022(title)
-#: ./doc/common/ch_cli_heat_commands.xml1079(title)
-#: ./doc/common/ch_cli_heat_commands.xml1157(title)
-#: ./doc/common/ch_cli_heat_commands.xml1176(title)
-#: ./doc/common/ch_cli_heat_commands.xml1246(title)
 #: ./doc/common/ch_cli_trove_commands.xml591(title)
 #: ./doc/common/ch_cli_trove_commands.xml636(title)
 #: ./doc/common/ch_cli_trove_commands.xml670(title)
@@ -5080,39 +3879,310 @@ msgstr ""
 msgid "Filename to write the x509 root cert."
 msgstr ""
 
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_getstart_dashboard.xml14(None)
-msgid ""
-"@@image: 'figures/horizon-screenshot.jpg'; "
-"md5=9471047adf0d93713be7f54b9db2b53c"
-msgstr "@@image: 'figures/horizon-screenshot.jpg'; md5=9471047adf0d93713be7f54b9db2b53c"
-
-#: ./doc/common/section_getstart_dashboard.xml5(title)
-msgid "OpenStack dashboard"
-msgstr "OpenStack Dashboard"
-
-#: ./doc/common/section_getstart_dashboard.xml6(para)
-msgid ""
-"The OpenStack dashboard is a modular <link "
-"href=\"https://www.djangoproject.com/\">Django web application</link> that "
-"provides a graphical interface to OpenStack services."
+#: ./doc/common/section_xapi-ami-setup.xml7(title)
+msgid "Prepare for AMI type images"
 msgstr ""
 
-#: ./doc/common/section_getstart_dashboard.xml18(para)
+#: ./doc/common/section_xapi-ami-setup.xml8(para)
 msgid ""
-"The dashboard is usually deployed through <link "
-"href=\"http://code.google.com/p/modwsgi/\">mod_wsgi</link> in Apache. You "
-"can modify the dashboard code to make it suitable for different sites."
+"To support AMI type images in your OpenStack installation, you must create a"
+" <filename>/boot/guest</filename> directory inside Dom0. The OpenStack VM "
+"extracts the kernel and ramdisk from the AKI and ARI images puts them in "
+"this location."
 msgstr ""
 
-#: ./doc/common/section_getstart_dashboard.xml22(para)
+#: ./doc/common/section_xapi-ami-setup.xml12(para)
 msgid ""
-"From a network architecture point of view, this service must be accessible "
-"to customers and the public API for each OpenStack service. To use the "
-"administrator functionality for other services, it must also connect to "
-"Admin API endpoints, which should not be accessible by customers."
+"OpenStack maintains the contents of this directory and its size should not "
+"increase during normal operation. However, in case of power failures or "
+"accidental shutdowns, some files might be left over. To prevent these files "
+"from filling the Dom0 disk, set up this directory as a symlink that points "
+"to a subdirectory of the local SR."
+msgstr ""
+
+#: ./doc/common/section_xapi-ami-setup.xml18(para)
+msgid "Run these commands in Dom0 to achieve this setup:"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-http.xml6(title)
+msgid "Configure the dashboard for HTTP"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-http.xml8(para)
+msgid ""
+"You can configure the dashboard for a simple HTTP deployment. The standard "
+"installation uses a non-encrypted HTTP channel."
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-http.xml12(para)
+msgid ""
+"Specify the host for your OpenStack Identity Service endpoint in the "
+"<filename>/etc/openstack-dashboard/local_settings.py</filename> file with "
+"the <literal>OPENSTACK_HOST</literal> setting."
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-http.xml17(para)
+msgid "The following example shows this setting:"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-http.xml19(para)
+msgid ""
+"The service catalog configuration in the Identity Service determines whether"
+" a service appears in the dashboard. For the full listing, see <link "
+"href=\"http://docs.openstack.org/developer/horizon/topics/settings.html\">Horizon"
+" Settings and Configuration</link>."
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-http.xml28(para)
+msgid "Restart Apache http server. For Ubuntu/Debian/SUSE:"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-http.xml30(para)
+msgid "or for Fedora/RHEL/CentOS:"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-http.xml32(para)
+#: ./doc/common/section_dashboard-configure-https.xml98(para)
+msgid "Next, restart memcached:"
+msgstr ""
+
+#: ./doc/common/section_rpc.xml7(title)
+#: ./doc/common/section_rpc-for-networking.xml7(title)
+msgid "Configure the Oslo RPC messaging system"
+msgstr ""
+
+#: ./doc/common/section_rpc.xml8(para)
+msgid ""
+"OpenStack projects use AMQP, an open standard for messaging middleware. "
+"OpenStack services that run on multiple servers to talk to each other. "
+"OpenStack Oslo RPC supports three implementations of AMQP: "
+"<application>RabbitMQ</application>, <application>Qpid</application>, and "
+"<application>ZeroMQ</application>."
+msgstr ""
+
+#: ./doc/common/section_rpc.xml15(title)
+#: ./doc/common/section_rpc-for-networking.xml18(title)
+msgid "Configure RabbitMQ"
+msgstr "RabbitMQ の設定"
+
+#: ./doc/common/section_rpc.xml16(para)
+msgid ""
+"OpenStack Oslo RPC uses <application>RabbitMQ</application> by default. Use "
+"these options to configure the <application>RabbitMQ</application> message "
+"system. The <literal>rpc_backend</literal> option is not required as long as"
+" <application>RabbitMQ</application> is the default messaging system. "
+"However, if it is included the configuration, you must set it to "
+"<literal>nova.openstack.common.rpc.impl_kombu</literal>."
+msgstr ""
+
+#: ./doc/common/section_rpc.xml25(para)
+msgid ""
+"You can use these additional options to configure the "
+"<application>RabbitMQ</application> messaging system. You can configure "
+"messaging communication for different installation scenarios, tune retries "
+"for RabbitMQ, and define the size of the RPC thread pool. To monitor "
+"notifications through RabbitMQ, you must set the "
+"<option>notification_driver</option> option to "
+"<literal>nova.notifier.rabbit_notifier</literal> in the "
+"<filename>nova.conf</filename> file. The default for sending usage data is "
+"sixty seconds plus a random number of seconds from zero to sixty."
+msgstr ""
+
+#: ./doc/common/section_rpc.xml39(title)
+#: ./doc/common/section_rpc-for-networking.xml46(title)
+msgid "Configure Qpid"
+msgstr ""
+
+#: ./doc/common/section_rpc.xml40(para)
+msgid ""
+"Use these options to configure the <application>Qpid</application> messaging"
+" system for OpenStack Oslo RPC. <application>Qpid</application> is not the "
+"default messaging system, so you must enable it by setting the "
+"<option>rpc_backend</option> option in the <filename>nova.conf</filename> "
+"file."
+msgstr ""
+
+#: ./doc/common/section_rpc.xml47(para)
+msgid ""
+"This critical option points the compute nodes to the "
+"<application>Qpid</application> broker (server). Set "
+"<option>qpid_hostname</option> to the host name where the broker runs in the"
+" <filename>nova.conf</filename> file."
+msgstr ""
+
+#: ./doc/common/section_rpc.xml52(para)
+#: ./doc/common/section_rpc-for-networking.xml62(para)
+msgid ""
+"The <option>--qpid_hostname</option> option accepts a host name or IP "
+"address value."
+msgstr ""
+
+#: ./doc/common/section_rpc.xml56(para)
+#: ./doc/common/section_rpc-for-networking.xml69(para)
+msgid ""
+"If the <application>Qpid</application> broker listens on a port other than "
+"the AMQP default of <literal>5672</literal>, you must set the "
+"<option>qpid_port</option> option to that value:"
+msgstr ""
+
+#: ./doc/common/section_rpc.xml61(para)
+#: ./doc/common/section_rpc-for-networking.xml78(para)
+msgid ""
+"If you configure the <application>Qpid</application> broker to require "
+"authentication, you must add a user name and password to the configuration:"
+msgstr ""
+
+#: ./doc/common/section_rpc.xml66(para)
+#: ./doc/common/section_rpc-for-networking.xml87(para)
+msgid ""
+"By default, TCP is used as the transport. To enable SSL, set the "
+"<option>qpid_protocol</option> option:"
+msgstr ""
+
+#: ./doc/common/section_rpc.xml69(para)
+msgid ""
+"This table lists additional options that you use to configure the Qpid "
+"messaging driver for OpenStack Oslo RPC. These options are used "
+"infrequently."
+msgstr ""
+
+#: ./doc/common/section_rpc.xml75(title)
+#: ./doc/common/section_rpc-for-networking.xml102(title)
+msgid "Configure ZeroMQ"
+msgstr ""
+
+#: ./doc/common/section_rpc.xml76(para)
+msgid ""
+"Use these options to configure the <application>ZeroMQ</application> "
+"messaging system for OpenStack Oslo RPC. <application>ZeroMQ</application> "
+"is not the default messaging system, so you must enable it by setting the "
+"<option>rpc_backend</option> option in the <filename>nova.conf</filename> "
+"file."
+msgstr ""
+
+#: ./doc/common/section_rpc.xml85(title)
+#: ./doc/common/section_rpc-for-networking.xml112(title)
+msgid "Configure messaging"
+msgstr ""
+
+#: ./doc/common/section_rpc.xml86(para)
+msgid ""
+"Use these options to configure the <application>RabbitMQ</application> and "
+"<application>Qpid</application> messaging drivers."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml6(title)
+msgid "User management"
+msgstr "ユーザー管理"
+
+#: ./doc/common/section_keystone-concepts-user-management.xml7(para)
+msgid "The main components of Identity user management are:"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml10(para)
+msgid ""
+"<emphasis role=\"bold\">User</emphasis>. Represents a human user. Has "
+"associated information such as user name, password, and email. This example "
+"creates a user named <literal>alice</literal>:"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml17(para)
+msgid ""
+"<emphasis role=\"bold\">Tenant</emphasis>. A project, group, or "
+"organization. When you make requests to OpenStack services, you must specify"
+" a tenant. For example, if you query the Compute service for a list of "
+"running instances, you get a list of all running instances in the tenant "
+"that you specified in your query. This example creates a tenant named "
+"<literal>acme</literal>:"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml27(para)
+msgid ""
+"Because the term <emphasis>project</emphasis> was used instead of "
+"<emphasis>tenant</emphasis> in earlier versions of OpenStack Compute, some "
+"command-line tools use <literal>--project_id</literal> instead of <literal"
+">--tenant-id</literal> or <literal>--os-tenant-id</literal> to refer to a "
+"tenant ID."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml38(para)
+msgid ""
+"<emphasis role=\"bold\">Role</emphasis>. Captures the operations that a user"
+" can perform in a given tenant."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml40(para)
+msgid "This example creates a role named <literal>compute-user</literal>:"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml44(para)
+msgid ""
+"Individual services, such as Compute and the Image Service, assign meaning "
+"to roles. In the Identity Service, a role is simply a name."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml51(para)
+msgid ""
+"The Identity Service assigns a tenant and a role to a user. You might assign"
+" the <literal>compute-user</literal> role to the <literal>alice</literal> "
+"user in the <literal>acme</literal> tenant:"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml74(para)
+msgid ""
+"A user can have different roles in different tenants. For example, Alice "
+"might also have the <literal>admin</literal> role in the "
+"<literal>Cyberdyne</literal> tenant. A user can also have multiple roles in "
+"the same tenant."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml78(para)
+msgid ""
+"The "
+"<filename>/etc/<replaceable>[SERVICE_CODENAME]</replaceable>/policy.json</filename>"
+" file controls the tasks that users can perform for a given service. For "
+"example, <filename>/etc/nova/policy.json</filename> specifies the access "
+"policy for the Compute service, <filename>/etc/glance/policy.json</filename>"
+" specifies the access policy for the Image Service, and "
+"<filename>/etc/keystone/policy.json</filename> specifies the access policy "
+"for the Identity Service."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml88(para)
+msgid ""
+"The default <filename>policy.json</filename> files in the Compute, Identity,"
+" and Image Service recognize only the <literal>admin</literal> role: all "
+"operations that do not require the <literal>admin</literal> role are "
+"accessible by any user that has any role in a tenant."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml93(para)
+msgid ""
+"If you wish to restrict users from performing operations in, say, the "
+"Compute service, you need to create a role in the Identity Service and then "
+"modify <filename>/etc/nova/policy.json</filename> so that this role is "
+"required for Compute operations."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml99(para)
+msgid ""
+"For example, this line in <filename>/etc/nova/policy.json</filename> "
+"specifies that there are no restrictions on which users can create volumes: "
+"if the user has any role in a tenant, they can create volumes in that "
+"tenant."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml105(para)
+msgid ""
+"To restrict creation of volumes to users who had the <literal>compute-"
+"user</literal> role in a particular tenant, you would add <literal>\"role"
+":compute-user\"</literal>, like so:"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-user-management.xml110(para)
+msgid ""
+"To restrict all Compute service requests to require this role, the resulting"
+" file would look like:"
 msgstr ""
 
 #: ./doc/common/section_cli_nova_quotas.xml6(title)
@@ -5136,390 +4206,390 @@ msgid "Quota name"
 msgstr ""
 
 #: ./doc/common/section_cli_nova_quotas.xml20(th)
-#: ./doc/common/ch_getstart.xml31(th)
 #: ./doc/common/section_cli_nova_customize_flavors.xml40(td)
-#: ./doc/common/section_cli_overview.xml36(th)
-#: ./doc/common/section_cli_install.xml22(th)
-#: ./doc/common/tables/nova-cells.xml14(th)
-#: ./doc/common/tables/trove-db_mongodb.xml14(th)
-#: ./doc/common/tables/keystone-debug.xml14(th)
-#: ./doc/common/tables/glance-policy.xml14(th)
-#: ./doc/common/tables/neutron-mlnx.xml14(th)
-#: ./doc/common/tables/nova-ipv6.xml14(th)
-#: ./doc/common/tables/cinder-eqlx.xml14(th)
-#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml13(th)
-#: ./doc/common/tables/swift-object-expirer-filter-cache.xml13(th)
-#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml13(th)
-#: ./doc/common/tables/nova-rpc_all.xml14(th)
-#: ./doc/common/tables/neutron-ml2_l2pop.xml14(th)
-#: ./doc/common/tables/glance-qpid.xml14(th)
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml13(th)
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml14(th)
-#: ./doc/common/tables/neutron-ml2_gre.xml14(th)
-#: ./doc/common/tables/nova-volumes.xml14(th)
-#: ./doc/common/tables/glance-gridfs.xml14(th)
-#: ./doc/common/tables/neutron-ml2_arista.xml14(th)
-#: ./doc/common/tables/glance-filesystem.xml14(th)
-#: ./doc/common/tables/heat-redis.xml14(th)
-#: ./doc/common/tables/trove-logging.xml14(th)
-#: ./doc/common/tables/swift-container-server-container-updater.xml13(th)
-#: ./doc/common/tables/cinder-storage_gpfs.xml14(th)
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml14(th)
-#: ./doc/common/tables/nova-tilera.xml14(th)
-#: ./doc/common/tables/nova-ca.xml14(th)
-#: ./doc/common/tables/heat-clients_nova.xml14(th)
-#: ./doc/common/tables/swift-account-server-filter-recon.xml13(th)
-#: ./doc/common/tables/cinder-huawei.xml14(th)
-#: ./doc/common/tables/keystone-qpid.xml14(th)
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml14(th)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml13(th)
-#: ./doc/common/tables/nova-glance.xml14(th)
-#: ./doc/common/tables/neutron-dhcp_agent.xml14(th)
-#: ./doc/common/tables/nova-neutron.xml14(th)
-#: ./doc/common/tables/cinder-backups_ceph.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml13(th)
-#: ./doc/common/tables/nova-metadata.xml14(th)
-#: ./doc/common/tables/glance-s3.xml14(th)
-#: ./doc/common/tables/glance-auth_token.xml14(th)
-#: ./doc/common/tables/neutron-kombu.xml14(th)
-#: ./doc/common/tables/trove-redis.xml14(th)
-#: ./doc/common/tables/trove-qpid.xml14(th)
-#: ./doc/common/tables/trove-compute.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml13(th)
-#: ./doc/common/tables/trove-nova.xml14(th)
-#: ./doc/common/tables/ceilometer-cells.xml14(th)
-#: ./doc/common/tables/keystone-oauth.xml14(th)
-#: ./doc/common/tables/cinder-block-device.xml14(th)
-#: ./doc/common/tables/cinder-zones.xml14(th)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml14(th)
-#: ./doc/common/tables/swift-container-server-container-sync.xml13(th)
-#: ./doc/common/tables/neutron-common.xml14(th)
-#: ./doc/common/tables/neutron-compute.xml14(th)
-#: ./doc/common/tables/swift-object-server-object-auditor.xml13(th)
-#: ./doc/common/tables/keystone-ldap.xml14(th)
-#: ./doc/common/tables/heat-rpc.xml14(th)
-#: ./doc/common/tables/neutron-openvswitch_agent.xml14(th)
-#: ./doc/common/tables/cinder-compute.xml14(th)
-#: ./doc/common/tables/keystone-identity.xml14(th)
-#: ./doc/common/tables/cinder-lvm.xml14(th)
-#: ./doc/common/tables/keystone-trust.xml14(th)
-#: ./doc/common/tables/cinder-storage_nfs.xml14(th)
-#: ./doc/common/tables/neutron-plumgrid.xml14(th)
-#: ./doc/common/tables/heat-cfn_api.xml14(th)
-#: ./doc/common/tables/nova-hypervisor.xml14(th)
-#: ./doc/common/tables/trove-rabbitmq.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml13(th)
-#: ./doc/common/tables/trove-api.xml14(th)
-#: ./doc/common/tables/cinder-quota.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml13(th)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml13(th)
-#: ./doc/common/tables/nova-console.xml14(th)
-#: ./doc/common/tables/ceilometer-events.xml14(th)
-#: ./doc/common/tables/keystone-os_inherit.xml14(th)
-#: ./doc/common/tables/heat-clients.xml14(th)
-#: ./doc/common/tables/heat-notification.xml14(th)
-#: ./doc/common/tables/keystone-assignment.xml14(th)
-#: ./doc/common/tables/nova-common.xml14(th)
-#: ./doc/common/tables/swift-object-server-object-updater.xml13(th)
-#: ./doc/common/tables/glance-zmq.xml14(th)
-#: ./doc/common/tables/neutron-metering_agent.xml14(th)
-#: ./doc/common/tables/trove-taskmanager.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml13(th)
-#: ./doc/common/tables/keystone-zeromq.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml13(th)
-#: ./doc/common/tables/nova-keymgr.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml13(th)
-#: ./doc/common/tables/neutron-api.xml14(th)
-#: ./doc/common/tables/ceilometer-redis.xml14(th)
-#: ./doc/common/tables/ceilometer-swift.xml14(th)
-#: ./doc/common/tables/cinder-hplefthand.xml14(th)
-#: ./doc/common/tables/heat-qpid.xml14(th)
-#: ./doc/common/tables/nova-testing.xml14(th)
-#: ./doc/common/tables/cinder-backups.xml14(th)
-#: ./doc/common/tables/swift-container-server-pipeline-main.xml13(th)
-#: ./doc/common/tables/neutron-ml2_ofa.xml14(th)
-#: ./doc/common/tables/trove-debug.xml14(th)
-#: ./doc/common/tables/swift-rsyncd-object.xml13(th)
-#: ./doc/common/tables/nova-s3.xml14(th)
-#: ./doc/common/tables/nova-zookeeper.xml14(th)
-#: ./doc/common/tables/cinder-rpc.xml14(th)
-#: ./doc/common/tables/cinder-api.xml14(th)
-#: ./doc/common/tables/cinder-windows.xml14(th)
-#: ./doc/common/tables/glance-vmware.xml14(th)
-#: ./doc/common/tables/swift-object-server-pipeline-main.xml13(th)
-#: ./doc/common/tables/trove-backup.xml14(th)
-#: ./doc/common/tables/nova-auth_token.xml14(th)
-#: ./doc/common/tables/cinder-san.xml14(th)
-#: ./doc/common/tables/swift-account-server-app-account-server.xml13(th)
-#: ./doc/common/tables/keystone-rpc.xml14(th)
-#: ./doc/common/tables/cinder-keymgr.xml14(th)
-#: ./doc/common/tables/nova-db.xml14(th)
-#: ./doc/common/tables/neutron-ml2_vxlan.xml14(th)
-#: ./doc/common/tables/glance-logging.xml14(th)
-#: ./doc/common/tables/cinder-zoning.xml14(th)
-#: ./doc/common/tables/glance-wsgi.xml14(th)
-#: ./doc/common/tables/nova-periodic.xml14(th)
-#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml13(th)
-#: ./doc/common/tables/cinder-images.xml14(th)
-#: ./doc/common/tables/trove-swift.xml14(th)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml13(th)
-#: ./doc/common/tables/cinder-auth_token.xml14(th)
-#: ./doc/common/tables/heat-crypt.xml14(th)
-#: ./doc/common/tables/neutron-wsgi.xml14(th)
-#: ./doc/common/tables/neutron-scheduler.xml14(th)
-#: ./doc/common/tables/keystone-security.xml14(th)
-#: ./doc/common/tables/ceilometer-vmware.xml14(th)
-#: ./doc/common/tables/glance-rbd.xml14(th)
-#: ./doc/common/tables/heat-clients_heat.xml14(th)
-#: ./doc/common/tables/heat-rabbitmq.xml14(th)
-#: ./doc/common/tables/ceilometer-logging.xml14(th)
-#: ./doc/common/tables/neutron-metadata.xml14(th)
-#: ./doc/common/tables/glance-redis.xml14(th)
-#: ./doc/common/tables/keystone-stats.xml14(th)
-#: ./doc/common/tables/cinder-hp3par.xml14(th)
-#: ./doc/common/tables/cinder-storage_ceph.xml14(th)
-#: ./doc/common/tables/nova-livemigration.xml14(th)
-#: ./doc/common/tables/nova-ldap.xml14(th)
-#: ./doc/common/tables/nova-fping.xml14(th)
-#: ./doc/common/tables/heat-clients_swift.xml14(th)
-#: ./doc/common/tables/neutron-securitygroups.xml14(th)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml14(th)
-#: ./doc/common/tables/nova-ec2.xml14(th)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml13(th)
-#: ./doc/common/tables/trove-zeromq.xml14(th)
-#: ./doc/common/tables/heat-database.xml14(th)
-#: ./doc/common/tables/keystone-catalog.xml14(th)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml13(th)
-#: ./doc/common/tables/cinder-rootwrap.xml14(th)
+#: ./doc/common/section_cli_overview.xml43(th)
+#: ./doc/common/section_cli_install.xml30(th)
+#: ./doc/common/ch_getstart.xml31(th)
 #: ./doc/common/tables/ceilometer-database.xml14(th)
-#: ./doc/common/tables/heat-debug.xml14(th)
-#: ./doc/common/tables/cinder-nexenta_nfs.xml14(th)
-#: ./doc/common/tables/trove-auth_token.xml14(th)
-#: ./doc/common/tables/heat-waitcondition_api.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml13(th)
-#: ./doc/common/tables/neutron-ml2_vlan.xml14(th)
-#: ./doc/common/tables/nova-policy.xml14(th)
-#: ./doc/common/tables/keystone-amqp.xml14(th)
-#: ./doc/common/tables/neutron-logging.xml14(th)
-#: ./doc/common/tables/trove-db_cassandra.xml14(th)
+#: ./doc/common/tables/neutron-openvswitch_agent.xml14(th)
+#: ./doc/common/tables/heat-clients.xml14(th)
+#: ./doc/common/tables/cinder-solidfire.xml14(th)
+#: ./doc/common/tables/neutron-rpc.xml14(th)
+#: ./doc/common/tables/trove-db_percona.xml14(th)
+#: ./doc/common/tables/nova-periodic.xml14(th)
+#: ./doc/common/tables/keystone-auth.xml14(th)
+#: ./doc/common/tables/keystone-policy.xml14(th)
+#: ./doc/common/tables/glance-auth_token.xml14(th)
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml14(th)
+#: ./doc/common/tables/swift-container-server-container-sync.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml13(th)
+#: ./doc/common/tables/cinder-zoning_fabric.xml14(th)
+#: ./doc/common/tables/ceilometer-redis.xml14(th)
+#: ./doc/common/tables/cinder-storage_ceph.xml14(th)
+#: ./doc/common/tables/ceilometer-vmware.xml14(th)
+#: ./doc/common/tables/neutron-cisco.xml14(th)
+#: ./doc/common/tables/nova-testing.xml14(th)
+#: ./doc/common/tables/nova-metadata.xml14(th)
+#: ./doc/common/tables/heat-clients_nova.xml14(th)
+#: ./doc/common/tables/cinder-hp3par.xml14(th)
+#: ./doc/common/tables/keystone-misc.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml13(th)
+#: ./doc/common/tables/neutron-scheduler.xml14(th)
+#: ./doc/common/tables/glance-rbd.xml14(th)
+#: ./doc/common/tables/cinder-storage_xen.xml14(th)
+#: ./doc/common/tables/ceilometer-common.xml14(th)
+#: ./doc/common/tables/cinder-database.xml14(th)
+#: ./doc/common/tables/ceilometer-logging.xml14(th)
+#: ./doc/common/tables/heat-common.xml14(th)
+#: ./doc/common/tables/nova-ipv6.xml14(th)
+#: ./doc/common/tables/nova-vnc.xml14(th)
+#: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml13(th)
+#: ./doc/common/tables/trove-qpid.xml14(th)
+#: ./doc/common/tables/keystone-api.xml14(th)
+#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml13(th)
+#: ./doc/common/tables/swift-container-server-container-auditor.xml13(th)
 #: ./doc/common/tables/glance-rpc.xml14(th)
-#: ./doc/common/tables/nova-authentication.xml14(th)
+#: ./doc/common/tables/neutron-policy.xml14(th)
+#: ./doc/common/tables/nova-spice.xml14(th)
+#: ./doc/common/tables/heat-clients_heat.xml14(th)
+#: ./doc/common/tables/nova-xen.xml14(th)
+#: ./doc/common/tables/trove-amqp.xml14(th)
+#: ./doc/common/tables/glance-matchmaker.xml14(th)
+#: ./doc/common/tables/nova-rabbitmq.xml14(th)
+#: ./doc/common/tables/neutron-ml2_cisco.xml14(th)
+#: ./doc/common/tables/nova-policy.xml14(th)
+#: ./doc/common/tables/keystone-identity.xml14(th)
+#: ./doc/common/tables/ceilometer-inspector.xml14(th)
+#: ./doc/common/tables/cinder-scheduler.xml14(th)
+#: ./doc/common/tables/trove-db_cassandra.xml14(th)
+#: ./doc/common/tables/neutron-logging.xml14(th)
+#: ./doc/common/tables/nova-availabilityzones.xml14(th)
+#: ./doc/common/tables/keystone-catalog.xml14(th)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml14(th)
+#: ./doc/common/tables/neutron-rootwrap.xml14(th)
+#: ./doc/common/tables/cinder-auth.xml14(th)
+#: ./doc/common/tables/swift-swift-swift-constraints.xml13(th)
+#: ./doc/common/tables/heat-qpid.xml14(th)
+#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml13(th)
+#: ./doc/common/tables/nova-zookeeper.xml14(th)
+#: ./doc/common/tables/nova-keymgr.xml14(th)
+#: ./doc/common/tables/neutron-auth_token.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml13(th)
+#: ./doc/common/tables/nova-ldap.xml14(th)
+#: ./doc/common/tables/swift-container-server-filter-recon.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml13(th)
+#: ./doc/common/tables/ceilometer-auth.xml14(th)
+#: ./doc/common/tables/cinder-quota.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml13(th)
+#: ./doc/common/tables/keystone-os_inherit.xml14(th)
+#: ./doc/common/tables/neutron-sdnve.xml14(th)
+#: ./doc/common/tables/nova-compute.xml14(th)
+#: ./doc/common/tables/keystone-rabbit.xml14(th)
+#: ./doc/common/tables/cinder-backups_ceph.xml14(th)
+#: ./doc/common/tables/nova-vmware.xml14(th)
+#: ./doc/common/tables/heat-cfn_api.xml14(th)
+#: ./doc/common/tables/neutron-vmware.xml14(th)
+#: ./doc/common/tables/nova-rdp.xml14(th)
+#: ./doc/common/tables/keystone-assignment.xml14(th)
+#: ./doc/common/tables/nova-zeromq.xml14(th)
+#: ./doc/common/tables/cinder-storage.xml14(th)
+#: ./doc/common/tables/glance-registry.xml14(th)
+#: ./doc/common/tables/neutron-embrane.xml14(th)
+#: ./doc/common/tables/heat-quota.xml14(th)
+#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml13(th)
+#: ./doc/common/tables/nova-common.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml13(th)
+#: ./doc/common/tables/nova-volumes.xml14(th)
+#: ./doc/common/tables/neutron-redis.xml14(th)
+#: ./doc/common/tables/trove-db_mysql.xml14(th)
+#: ./doc/common/tables/heat-zeromq.xml14(th)
+#: ./doc/common/tables/heat-amqp.xml14(th)
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml14(th)
+#: ./doc/common/tables/nova-redis.xml14(th)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml13(th)
+#: ./doc/common/tables/nova-db.xml14(th)
+#: ./doc/common/tables/glance-rabbitmq.xml14(th)
+#: ./doc/common/tables/neutron-l3_agent.xml14(th)
+#: ./doc/common/tables/swift-container-server-pipeline-main.xml13(th)
+#: ./doc/common/tables/glance-policy.xml14(th)
+#: ./doc/common/tables/nova-neutron.xml14(th)
+#: ./doc/common/tables/cinder-backups.xml14(th)
+#: ./doc/common/tables/cinder-keymgr.xml14(th)
+#: ./doc/common/tables/ceilometer-cells.xml14(th)
+#: ./doc/common/tables/keystone-ldap.xml14(th)
+#: ./doc/common/tables/glance-vmware.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml13(th)
+#: ./doc/common/tables/cinder-zoning.xml14(th)
+#: ./doc/common/tables/heat-notification.xml14(th)
+#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml13(th)
+#: ./doc/common/tables/nova-vpn.xml14(th)
+#: ./doc/common/tables/neutron-vpn.xml14(th)
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml13(th)
+#: ./doc/common/tables/trove-common.xml14(th)
+#: ./doc/common/tables/trove-api.xml14(th)
+#: ./doc/common/tables/cinder-zadara.xml14(th)
+#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml13(th)
+#: ./doc/common/tables/nova-conductor.xml14(th)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml13(th)
+#: ./doc/common/tables/nova-livemigration.xml14(th)
+#: ./doc/common/tables/heat-rabbitmq.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml13(th)
+#: ./doc/common/tables/neutron-cadf.xml14(th)
+#: ./doc/common/tables/keystone-amqp.xml14(th)
+#: ./doc/common/tables/keystone-rpc.xml14(th)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml13(th)
+#: ./doc/common/tables/cinder-zones.xml14(th)
+#: ./doc/common/tables/cinder-scality.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml13(th)
+#: ./doc/common/tables/neutron-agent.xml14(th)
+#: ./doc/common/tables/cinder-emc.xml14(th)
 #: ./doc/common/tables/cinder-vmware.xml14(th)
-#: ./doc/common/tables/glance-sheepdog.xml14(th)
-#: ./doc/common/tables/heat-logging.xml14(th)
-#: ./doc/common/tables/keystone-notification.xml14(th)
-#: ./doc/common/tables/neutron-qpid.xml14(th)
-#: ./doc/common/tables/neutron-hyperv_agent.xml14(th)
+#: ./doc/common/tables/neutron-ml2_flat.xml14(th)
+#: ./doc/common/tables/heat-metadata_api.xml14(th)
+#: ./doc/common/tables/trove-rabbitmq.xml14(th)
+#: ./doc/common/tables/nova-upgrade_levels.xml14(th)
+#: ./doc/common/tables/neutron-kombu.xml14(th)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml14(th)
+#: ./doc/common/tables/neutron-ml2_ofa.xml14(th)
+#: ./doc/common/tables/glance-api.xml14(th)
+#: ./doc/common/tables/heat-waitcondition_api.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml13(th)
+#: ./doc/common/tables/swift-rsyncd-container.xml13(th)
+#: ./doc/common/tables/cinder-storwize.xml14(th)
+#: ./doc/common/tables/cinder-hplefthand.xml14(th)
+#: ./doc/common/tables/glance-s3.xml14(th)
+#: ./doc/common/tables/nova-rootwrap.xml14(th)
+#: ./doc/common/tables/heat-loadbalancer.xml14(th)
+#: ./doc/common/tables/ceilometer-api.xml14(th)
+#: ./doc/common/tables/ceilometer-exchange.xml14(th)
+#: ./doc/common/tables/cinder-lvm.xml14(th)
+#: ./doc/common/tables/trove-dns.xml14(th)
+#: ./doc/common/tables/nova-cells.xml14(th)
+#: ./doc/common/tables/trove-volume.xml14(th)
+#: ./doc/common/tables/heat-auth_token.xml14(th)
+#: ./doc/common/tables/neutron-quotas.xml14(th)
+#: ./doc/common/tables/nova-auth_token.xml14(th)
+#: ./doc/common/tables/cinder-storage_nfs.xml14(th)
+#: ./doc/common/tables/heat-api.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml13(th)
+#: ./doc/common/tables/heat-clients_ceilometer.xml14(th)
+#: ./doc/common/tables/neutron-ryu.xml14(th)
+#: ./doc/common/tables/glance-logging.xml14(th)
+#: ./doc/common/tables/swift-rsyncd-account.xml13(th)
+#: ./doc/common/tables/neutron-metering_agent.xml14(th)
+#: ./doc/common/tables/neutron-zeromq.xml14(th)
+#: ./doc/common/tables/cinder-storage_glusterfs.xml14(th)
+#: ./doc/common/tables/cinder-common.xml14(th)
 #: ./doc/common/tables/glance-swift.xml14(th)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml13(th)
+#: ./doc/common/tables/trove-quota.xml14(th)
+#: ./doc/common/tables/cinder-auth_token.xml14(th)
+#: ./doc/common/tables/ceilometer-alarm.xml14(th)
+#: ./doc/common/tables/ceilometer-events.xml14(th)
+#: ./doc/common/tables/cinder-xiv.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml13(th)
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml14(th)
+#: ./doc/common/tables/nova-glance.xml14(th)
+#: ./doc/common/tables/keystone-auth_token.xml14(th)
+#: ./doc/common/tables/nova-s3.xml14(th)
+#: ./doc/common/tables/nova-pci.xml14(th)
+#: ./doc/common/tables/swift-account-server-filter-recon.xml13(th)
+#: ./doc/common/tables/heat-clients_cinder.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml13(th)
+#: ./doc/common/tables/keystone-revoke.xml14(th)
+#: ./doc/common/tables/cinder-api.xml14(th)
+#: ./doc/common/tables/trove-db_couchbase.xml14(th)
+#: ./doc/common/tables/heat-clients_trove.xml14(th)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml13(th)
+#: ./doc/common/tables/neutron-plumgrid.xml14(th)
+#: ./doc/common/tables/trove-heat.xml14(th)
+#: ./doc/common/tables/glance-sheepdog.xml14(th)
+#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml13(th)
+#: ./doc/common/tables/cinder-windows.xml14(th)
+#: ./doc/common/tables/cinder-san-solaris.xml14(th)
+#: ./doc/common/tables/neutron-nuage.xml14(th)
+#: ./doc/common/tables/keystone-zeromq.xml14(th)
 #: ./doc/common/tables/neutron-bigswitch.xml14(th)
-#: ./doc/common/tables/nova-libvirt.xml14(th)
+#: ./doc/common/tables/ceilometer-rpc.xml14(th)
+#: ./doc/common/tables/swift-container-server-container-updater.xml13(th)
+#: ./doc/common/tables/trove-db_mongodb.xml14(th)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml13(th)
+#: ./doc/common/tables/glance-filesystem.xml14(th)
+#: ./doc/common/tables/trove-rpc.xml14(th)
+#: ./doc/common/tables/ceilometer-swift.xml14(th)
+#: ./doc/common/tables/trove-backup.xml14(th)
+#: ./doc/common/tables/nova-network.xml14(th)
+#: ./doc/common/tables/glance-redis.xml14(th)
+#: ./doc/common/tables/keystone-ssl.xml14(th)
+#: ./doc/common/tables/nova-ca.xml14(th)
+#: ./doc/common/tables/neutron-dhcp_agent.xml14(th)
+#: ./doc/common/tables/ceilometer-collector.xml14(th)
+#: ./doc/common/tables/cinder-hds-hus.xml14(th)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml14(th)
+#: ./doc/common/tables/swift-swift-swift-hash.xml13(th)
+#: ./doc/common/tables/neutron-ml2_gre.xml14(th)
+#: ./doc/common/tables/neutron-varmour.xml14(th)
+#: ./doc/common/tables/heat-debug.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml13(th)
+#: ./doc/common/tables/nova-kombu.xml14(th)
+#: ./doc/common/tables/trove-guestagent.xml14(th)
+#: ./doc/common/tables/nova-qpid.xml14(th)
+#: ./doc/common/tables/glance-qpid.xml14(th)
+#: ./doc/common/tables/neutron-ml2_l2pop.xml14(th)
+#: ./doc/common/tables/glance-amqp.xml14(th)
+#: ./doc/common/tables/glance-zmq.xml14(th)
+#: ./doc/common/tables/neutron-embrane_lb.xml14(th)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml13(th)
+#: ./doc/common/tables/neutron-testing.xml14(th)
+#: ./doc/common/tables/swift-object-server-pipeline-main.xml13(th)
+#: ./doc/common/tables/swift-memcache-memcache.xml13(th)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml13(th)
+#: ./doc/common/tables/trove-compute.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml13(th)
+#: ./doc/common/tables/swift-object-expirer-filter-cache.xml13(th)
+#: ./doc/common/tables/trove-db_redis.xml14(th)
+#: ./doc/common/tables/cinder-rpc.xml14(th)
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml13(th)
+#: ./doc/common/tables/cinder-hpmsa.xml14(th)
+#: ./doc/common/tables/nova-apiv3.xml14(th)
+#: ./doc/common/tables/keystone-oauth.xml14(th)
+#: ./doc/common/tables/cinder-storage_gpfs.xml14(th)
+#: ./doc/common/tables/neutron-ml2_vlan.xml14(th)
+#: ./doc/common/tables/keystone-notification.xml14(th)
+#: ./doc/common/tables/swift-object-server-object-auditor.xml13(th)
+#: ./doc/common/tables/trove-zeromq.xml14(th)
 #: ./doc/common/tables/neutron-lbaas.xml14(th)
 #: ./doc/common/tables/cinder-backups_swift.xml14(th)
-#: ./doc/common/tables/neutron-ml2_cisco.xml14(th)
-#: ./doc/common/tables/ceilometer-rpc.xml14(th)
-#: ./doc/common/tables/heat-loadbalancer.xml14(th)
-#: ./doc/common/tables/heat-cloudwatch_api.xml14(th)
-#: ./doc/common/tables/nova-pci.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml13(th)
-#: ./doc/common/tables/heat-clients_ceilometer.xml14(th)
-#: ./doc/common/tables/neutron-varmour.xml14(th)
-#: ./doc/common/tables/glance-imagecache.xml14(th)
-#: ./doc/common/tables/trove-quota.xml14(th)
-#: ./doc/common/tables/swift-rsyncd-account.xml13(th)
-#: ./doc/common/tables/cinder-storage.xml14(th)
-#: ./doc/common/tables/cinder-nas.xml14(th)
-#: ./doc/common/tables/nova-vpn.xml14(th)
-#: ./doc/common/tables/nova-wsgi.xml14(th)
-#: ./doc/common/tables/cinder-storage_glusterfs.xml14(th)
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml13(th)
-#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml13(th)
-#: ./doc/common/tables/nova-availabilityzones.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml13(th)
-#: ./doc/common/tables/heat-zeromq.xml14(th)
-#: ./doc/common/tables/keystone-memcache.xml14(th)
-#: ./doc/common/tables/nova-vnc.xml14(th)
-#: ./doc/common/tables/swift-swift-swift-constraints.xml13(th)
-#: ./doc/common/tables/neutron-cisco.xml14(th)
-#: ./doc/common/tables/keystone-logging.xml14(th)
-#: ./doc/common/tables/nova-hyperv.xml14(th)
-#: ./doc/common/tables/neutron-l3_agent.xml14(th)
-#: ./doc/common/tables/swift-object-server-filter-recon.xml13(th)
-#: ./doc/common/tables/cinder-coraid.xml14(th)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml13(th)
-#: ./doc/common/tables/nova-vmware.xml14(th)
-#: ./doc/common/tables/nova-logging.xml14(th)
-#: ./doc/common/tables/nova-xen.xml14(th)
-#: ./doc/common/tables/ceilometer-collector.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml13(th)
-#: ./doc/common/tables/keystone-ec2.xml14(th)
-#: ./doc/common/tables/keystone-auth.xml14(th)
-#: ./doc/common/tables/swift-memcache-memcache.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml13(th)
-#: ./doc/common/tables/neutron-ml2.xml14(th)
-#: ./doc/common/tables/ceilometer-api.xml14(th)
-#: ./doc/common/tables/heat-clients_trove.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml13(th)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml14(th)
-#: ./doc/common/tables/glance-common.xml14(th)
-#: ./doc/common/tables/nova-network.xml14(th)
-#: ./doc/common/tables/cinder-scality.xml14(th)
-#: ./doc/common/tables/neutron-notifier.xml14(th)
-#: ./doc/common/tables/cinder-common.xml14(th)
-#: ./doc/common/tables/nova-trustedcomputing.xml14(th)
-#: ./doc/common/tables/neutron-ml2_flat.xml14(th)
-#: ./doc/common/tables/heat-clients_cinder.xml14(th)
-#: ./doc/common/tables/nova-configdrive.xml14(th)
-#: ./doc/common/tables/cinder-database.xml14(th)
-#: ./doc/common/tables/neutron-rpc.xml14(th)
-#: ./doc/common/tables/cinder-zoning_manager.xml14(th)
-#: ./doc/common/tables/trove-volume.xml14(th)
-#: ./doc/common/tables/keystone-cache.xml14(th)
-#: ./doc/common/tables/nova-zeromq.xml14(th)
-#: ./doc/common/tables/glance-testing.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml13(th)
-#: ./doc/common/tables/glance-registry.xml14(th)
-#: ./doc/common/tables/glance-amqp.xml14(th)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml13(th)
 #: ./doc/common/tables/trove-database.xml14(th)
-#: ./doc/common/tables/heat-clients_backends.xml14(th)
-#: ./doc/common/tables/heat-amqp.xml14(th)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml13(th)
-#: ./doc/common/tables/cinder-hpmsa.xml14(th)
-#: ./doc/common/tables/cinder-emc.xml14(th)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml13(th)
-#: ./doc/common/tables/neutron-fwaas.xml14(th)
-#: ./doc/common/tables/glance-rabbitmq.xml14(th)
-#: ./doc/common/tables/cinder-backups_tsm.xml14(th)
-#: ./doc/common/tables/neutron-sdnve.xml14(th)
-#: ./doc/common/tables/trove-db_mysql.xml14(th)
-#: ./doc/common/tables/nova-qpid.xml14(th)
-#: ./doc/common/tables/trove-rpc.xml14(th)
-#: ./doc/common/tables/cinder-connection.xml14(th)
-#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml13(th)
-#: ./doc/common/tables/trove-db_redis.xml14(th)
-#: ./doc/common/tables/ceilometer-qpid.xml14(th)
-#: ./doc/common/tables/neutron-zeromq.xml14(th)
-#: ./doc/common/tables/keystone-token.xml14(th)
-#: ./doc/common/tables/neutron-vpn.xml14(th)
-#: ./doc/common/tables/neutron-agent.xml14(th)
-#: ./doc/common/tables/neutron-ryu.xml14(th)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml13(th)
-#: ./doc/common/tables/trove-db_couchbase.xml14(th)
-#: ./doc/common/tables/neutron-policy.xml14(th)
-#: ./doc/common/tables/neutron-rootwrap.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml13(th)
-#: ./doc/common/tables/trove-common.xml14(th)
-#: ./doc/common/tables/cinder-ssl.xml14(th)
-#: ./doc/common/tables/heat-api.xml14(th)
-#: ./doc/common/tables/trove-db_percona.xml14(th)
-#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml13(th)
-#: ./doc/common/tables/ceilometer-amqp.xml14(th)
-#: ./doc/common/tables/keystone-auth_token.xml14(th)
-#: ./doc/common/tables/neutron-meta.xml14(th)
-#: ./doc/common/tables/neutron-redis.xml14(th)
-#: ./doc/common/tables/neutron-ssl.xml14(th)
-#: ./doc/common/tables/ceilometer-exchange.xml14(th)
-#: ./doc/common/tables/ceilometer-common.xml14(th)
-#: ./doc/common/tables/ceilometer-alarm.xml14(th)
-#: ./doc/common/tables/keystone-misc.xml14(th)
-#: ./doc/common/tables/nova-scheduling.xml14(th)
-#: ./doc/common/tables/ceilometer-auth.xml14(th)
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml13(th)
-#: ./doc/common/tables/neutron-ml2_mlnx.xml14(th)
-#: ./doc/common/tables/swift-container-server-filter-recon.xml13(th)
-#: ./doc/common/tables/trove-dns.xml14(th)
-#: ./doc/common/tables/neutron-db.xml14(th)
-#: ./doc/common/tables/neutron-ml2_brocade.xml14(th)
-#: ./doc/common/tables/neutron-brocade.xml14(th)
-#: ./doc/common/tables/keystone-redis.xml14(th)
-#: ./doc/common/tables/heat-auth_token.xml14(th)
-#: ./doc/common/tables/keystone-database.xml14(th)
-#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml13(th)
-#: ./doc/common/tables/heat-clients_neutron.xml14(th)
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml14(th)
-#: ./doc/common/tables/cinder-xiv.xml14(th)
-#: ./doc/common/tables/cinder-hds-hus.xml14(th)
-#: ./doc/common/tables/neutron-rabbitmq.xml14(th)
-#: ./doc/common/tables/keystone-kvs.xml14(th)
-#: ./doc/common/tables/trove-ssl.xml14(th)
-#: ./doc/common/tables/keystone-policy.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml13(th)
-#: ./doc/common/tables/swift-swift-swift-hash.xml13(th)
-#: ./doc/common/tables/cinder-auth.xml14(th)
-#: ./doc/common/tables/nova-kombu.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml13(th)
-#: ./doc/common/tables/neutron-ml2_odl.xml14(th)
-#: ./doc/common/tables/heat-quota.xml14(th)
-#: ./doc/common/tables/nova-spice.xml14(th)
-#: ./doc/common/tables/cinder-zoning_fabric.xml14(th)
-#: ./doc/common/tables/neutron-midonet.xml14(th)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml13(th)
+#: ./doc/common/tables/nova-authentication.xml14(th)
 #: ./doc/common/tables/neutron-nvsd.xml14(th)
-#: ./doc/common/tables/neutron-embrane_lb.xml14(th)
-#: ./doc/common/tables/neutron-auth_token.xml14(th)
-#: ./doc/common/tables/cinder-storwize.xml14(th)
-#: ./doc/common/tables/nova-rootwrap.xml14(th)
-#: ./doc/common/tables/cinder-solidfire.xml14(th)
-#: ./doc/common/tables/keystone-revoke.xml14(th)
-#: ./doc/common/tables/glance-ssl.xml14(th)
-#: ./doc/common/tables/heat-metadata_api.xml14(th)
-#: ./doc/common/tables/nova-apiv3.xml14(th)
-#: ./doc/common/tables/glance-db.xml14(th)
-#: ./doc/common/tables/neutron-vmware.xml14(th)
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml13(th)
-#: ./doc/common/tables/nova-api.xml14(th)
-#: ./doc/common/tables/glance-matchmaker.xml14(th)
-#: ./doc/common/tables/keystone-ssl.xml14(th)
-#: ./doc/common/tables/swift-rsyncd-container.xml13(th)
-#: ./doc/common/tables/cinder-san-solaris.xml14(th)
-#: ./doc/common/tables/trove-heat.xml14(th)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml14(th)
-#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml13(th)
-#: ./doc/common/tables/glance-paste.xml14(th)
-#: ./doc/common/tables/nova-rdp.xml14(th)
-#: ./doc/common/tables/neutron-quotas.xml14(th)
-#: ./doc/common/tables/nova-rpc.xml14(th)
-#: ./doc/common/tables/trove-guestagent.xml14(th)
-#: ./doc/common/tables/nova-baremetal.xml14(th)
-#: ./doc/common/tables/heat-clients_keystone.xml14(th)
 #: ./doc/common/tables/swift-account-server-pipeline-main.xml13(th)
-#: ./doc/common/tables/keystone-rabbit.xml14(th)
-#: ./doc/common/tables/glance-api.xml14(th)
-#: ./doc/common/tables/cinder-scheduler.xml14(th)
-#: ./doc/common/tables/keystone-api.xml14(th)
-#: ./doc/common/tables/neutron-ml2_ncs.xml14(th)
-#: ./doc/common/tables/neutron-nec.xml14(th)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml14(th)
-#: ./doc/common/tables/neutron-cadf.xml14(th)
-#: ./doc/common/tables/neutron-testing.xml14(th)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml13(th)
-#: ./doc/common/tables/glance-cinder.xml14(th)
-#: ./doc/common/tables/nova-redis.xml14(th)
-#: ./doc/common/tables/neutron-embrane.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml13(th)
-#: ./doc/common/tables/nova-upgrade_levels.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml13(th)
-#: ./doc/common/tables/ceilometer-inspector.xml14(th)
-#: ./doc/common/tables/nova-rabbitmq.xml14(th)
-#: ./doc/common/tables/heat-common.xml14(th)
+#: ./doc/common/tables/glance-gridfs.xml14(th)
+#: ./doc/common/tables/neutron-notifier.xml14(th)
+#: ./doc/common/tables/nova-rpc_all.xml14(th)
+#: ./doc/common/tables/neutron-hyperv_agent.xml14(th)
 #: ./doc/common/tables/keystone-federation.xml14(th)
-#: ./doc/common/tables/cinder-zadara.xml14(th)
-#: ./doc/common/tables/neutron-nuage.xml14(th)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml13(th)
-#: ./doc/common/tables/ceilometer-ssl.xml14(th)
-#: ./doc/common/tables/nova-quota.xml14(th)
-#: ./doc/common/tables/nova-conductor.xml14(th)
-#: ./doc/common/tables/nova-compute.xml14(th)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml13(th)
-#: ./doc/common/tables/cinder-storage_xen.xml14(th)
+#: ./doc/common/tables/nova-scheduling.xml14(th)
+#: ./doc/common/tables/cinder-ssl.xml14(th)
+#: ./doc/common/tables/trove-ssl.xml14(th)
+#: ./doc/common/tables/cinder-eqlx.xml14(th)
+#: ./doc/common/tables/heat-redis.xml14(th)
+#: ./doc/common/tables/nova-ec2.xml14(th)
 #: ./doc/common/tables/keystone-credential.xml14(th)
-#: ./doc/common/tables/trove-amqp.xml14(th)
+#: ./doc/common/tables/cinder-block-device.xml14(th)
+#: ./doc/common/tables/neutron-metadata.xml14(th)
+#: ./doc/common/tables/nova-fping.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml13(th)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml13(th)
+#: ./doc/common/tables/neutron-ml2_ncs.xml14(th)
+#: ./doc/common/tables/neutron-ml2_arista.xml14(th)
+#: ./doc/common/tables/nova-trustedcomputing.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml13(th)
+#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml13(th)
+#: ./doc/common/tables/neutron-compute.xml14(th)
+#: ./doc/common/tables/glance-imagecache.xml14(th)
+#: ./doc/common/tables/neutron-ml2_brocade.xml14(th)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml13(th)
+#: ./doc/common/tables/cinder-nas.xml14(th)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml14(th)
+#: ./doc/common/tables/heat-clients_swift.xml14(th)
+#: ./doc/common/tables/keystone-logging.xml14(th)
+#: ./doc/common/tables/neutron-brocade.xml14(th)
+#: ./doc/common/tables/neutron-ml2_odl.xml14(th)
+#: ./doc/common/tables/swift-object-server-filter-recon.xml13(th)
+#: ./doc/common/tables/cinder-connection.xml14(th)
+#: ./doc/common/tables/heat-rpc.xml14(th)
+#: ./doc/common/tables/trove-taskmanager.xml14(th)
+#: ./doc/common/tables/heat-cloudwatch_api.xml14(th)
+#: ./doc/common/tables/cinder-images.xml14(th)
+#: ./doc/common/tables/cinder-huawei.xml14(th)
+#: ./doc/common/tables/nova-console.xml14(th)
+#: ./doc/common/tables/neutron-fwaas.xml14(th)
+#: ./doc/common/tables/cinder-nexenta_nfs.xml14(th)
+#: ./doc/common/tables/nova-quota.xml14(th)
+#: ./doc/common/tables/heat-logging.xml14(th)
+#: ./doc/common/tables/trove-redis.xml14(th)
+#: ./doc/common/tables/keystone-stats.xml14(th)
+#: ./doc/common/tables/heat-crypt.xml14(th)
+#: ./doc/common/tables/neutron-ssl.xml14(th)
+#: ./doc/common/tables/neutron-midonet.xml14(th)
+#: ./doc/common/tables/cinder-coraid.xml14(th)
+#: ./doc/common/tables/neutron-wsgi.xml14(th)
+#: ./doc/common/tables/cinder-compute.xml14(th)
+#: ./doc/common/tables/swift-rsyncd-object.xml13(th)
+#: ./doc/common/tables/glance-wsgi.xml14(th)
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml13(th)
+#: ./doc/common/tables/nova-baremetal.xml14(th)
+#: ./doc/common/tables/neutron-qpid.xml14(th)
+#: ./doc/common/tables/nova-rpc.xml14(th)
+#: ./doc/common/tables/cinder-backups_tsm.xml14(th)
+#: ./doc/common/tables/cinder-san.xml14(th)
+#: ./doc/common/tables/nova-logging.xml14(th)
+#: ./doc/common/tables/neutron-nec.xml14(th)
+#: ./doc/common/tables/keystone-security.xml14(th)
+#: ./doc/common/tables/heat-clients_neutron.xml14(th)
+#: ./doc/common/tables/nova-api.xml14(th)
+#: ./doc/common/tables/neutron-ml2_mlnx.xml14(th)
+#: ./doc/common/tables/trove-auth_token.xml14(th)
+#: ./doc/common/tables/keystone-trust.xml14(th)
+#: ./doc/common/tables/glance-cinder.xml14(th)
+#: ./doc/common/tables/swift-object-server-object-updater.xml13(th)
+#: ./doc/common/tables/glance-common.xml14(th)
+#: ./doc/common/tables/neutron-ml2_vxlan.xml14(th)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml13(th)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml13(th)
+#: ./doc/common/tables/trove-nova.xml14(th)
+#: ./doc/common/tables/neutron-meta.xml14(th)
+#: ./doc/common/tables/neutron-rabbitmq.xml14(th)
+#: ./doc/common/tables/keystone-ec2.xml14(th)
+#: ./doc/common/tables/heat-clients_keystone.xml14(th)
+#: ./doc/common/tables/neutron-api.xml14(th)
+#: ./doc/common/tables/trove-logging.xml14(th)
+#: ./doc/common/tables/glance-db.xml14(th)
+#: ./doc/common/tables/keystone-kvs.xml14(th)
+#: ./doc/common/tables/keystone-redis.xml14(th)
 #: ./doc/common/tables/nova-xvpnvncproxy.xml14(th)
+#: ./doc/common/tables/glance-paste.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml13(th)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml13(th)
+#: ./doc/common/tables/nova-hyperv.xml14(th)
+#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml13(th)
+#: ./doc/common/tables/heat-clients_backends.xml14(th)
+#: ./doc/common/tables/glance-testing.xml14(th)
+#: ./doc/common/tables/neutron-common.xml14(th)
+#: ./doc/common/tables/nova-hypervisor.xml14(th)
+#: ./doc/common/tables/keystone-qpid.xml14(th)
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml13(th)
+#: ./doc/common/tables/nova-wsgi.xml14(th)
+#: ./doc/common/tables/keystone-cache.xml14(th)
+#: ./doc/common/tables/nova-configdrive.xml14(th)
+#: ./doc/common/tables/keystone-token.xml14(th)
+#: ./doc/common/tables/ceilometer-ssl.xml14(th)
+#: ./doc/common/tables/ceilometer-qpid.xml14(th)
+#: ./doc/common/tables/heat-database.xml14(th)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml14(th)
+#: ./doc/common/tables/neutron-ml2.xml14(th)
+#: ./doc/common/tables/neutron-db.xml14(th)
+#: ./doc/common/tables/keystone-database.xml14(th)
+#: ./doc/common/tables/keystone-memcache.xml14(th)
+#: ./doc/common/tables/trove-debug.xml14(th)
+#: ./doc/common/tables/trove-swift.xml14(th)
+#: ./doc/common/tables/nova-tilera.xml14(th)
+#: ./doc/common/tables/nova-libvirt.xml14(th)
+#: ./doc/common/tables/neutron-mlnx.xml14(th)
+#: ./doc/common/tables/cinder-zoning_manager.xml14(th)
+#: ./doc/common/tables/ceilometer-amqp.xml14(th)
+#: ./doc/common/tables/glance-ssl.xml14(th)
+#: ./doc/common/tables/neutron-securitygroups.xml14(th)
+#: ./doc/common/tables/keystone-debug.xml14(th)
+#: ./doc/common/tables/cinder-rootwrap.xml14(th)
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml14(th)
 msgid "Description"
 msgstr "説明"
 
@@ -5639,13 +4709,13 @@ msgstr "全テナントに対するクォータのデフォルト値を全て表
 #: ./doc/common/section_cli_nova_quotas.xml249(para)
 #: ./doc/common/section_cli_nova_quotas.xml292(para)
 #: ./doc/common/section_cli_nova_quotas.xml324(para)
-#: ./doc/common/section_cli_keystone_services.xml100(para)
-#: ./doc/common/section_cli_nova_boot_from_volume.xml190(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml82(para)
 #: ./doc/common/section_keystone_certificates-for-pki.xml180(para)
+#: ./doc/common/section_cli_nova_boot_from_volume.xml190(para)
 #: ./doc/common/section_cli_cinder_manage_volumes.xml335(para)
 #: ./doc/common/section_cli_cinder_manage_volumes.xml349(para)
 #: ./doc/common/section_cli_cinder_manage_volumes.xml393(para)
-#: ./doc/common/section_objectstorage-ringbuilder.xml82(para)
+#: ./doc/common/section_cli_keystone_services.xml100(para)
 msgid "For example:"
 msgstr "例:"
 
@@ -5743,1036 +4813,530 @@ msgstr ""
 msgid "To update quota values for a tenant user"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-intro.xml7(title)
-#: ./doc/common/section_about-object-storage.xml7(title)
-msgid "Introduction to Object Storage"
-msgstr ""
+#: ./doc/common/section_cli_nova_boot.xml6(title)
+msgid "Launch instances"
+msgstr "インスタンスの起動"
 
-#: ./doc/common/section_objectstorage-intro.xml8(para)
+#: ./doc/common/section_cli_nova_boot.xml7(para)
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml8(para)
+msgid "Instances are virtual machines that run inside the cloud."
+msgstr "インスタンスはクラウド内で動作する仮想マシンです。"
+
+#: ./doc/common/section_cli_nova_boot.xml9(para)
+msgid "Before you can launch an instance, gather the following parameters:"
+msgstr "インスタンスを起動する前に、以下のパラメーターの情報を集めます。"
+
+#: ./doc/common/section_cli_nova_boot.xml13(para)
 msgid ""
-"OpenStack Object Storage (code-named swift) is open source software for "
-"creating redundant, scalable data storage using clusters of standardized "
-"servers to store petabytes of accessible data. It is a long-term storage "
-"system for large amounts of static data that can be retrieved, leveraged, "
-"and updated. Object Storage uses a distributed architecture with no central "
-"point of control, providing greater scalability, redundancy, and permanence."
-" Objects are written to multiple hardware devices, with the OpenStack "
-"software responsible for ensuring data replication and integrity across the "
-"cluster. Storage clusters scale horizontally by adding new nodes. Should a "
-"node fail, OpenStack works to replicate its content from other active nodes."
-" Because OpenStack uses software logic to ensure data replication and "
-"distribution across different devices, inexpensive commodity hard drives and"
-" servers can be used in lieu of more expensive equipment."
+"The <emphasis role=\"bold\">instance source</emphasis> can be an image, "
+"snapshot, or block storage volume that contains an image or snapshot."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-intro.xml19(para)
+#: ./doc/common/section_cli_nova_boot.xml18(para)
+msgid "A <emphasis role=\"bold\">name</emphasis> for your instance."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot.xml21(para)
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml37(para)
 msgid ""
-"Object Storage is ideal for cost effective, scale-out storage. It provides a"
-" fully distributed, API-accessible storage platform that can be integrated "
-"directly into applications or used for backup, archiving, and data "
-"retention."
+"The <emphasis role=\"bold\">flavor</emphasis> for your instance, which "
+"defines the compute, memory, and storage capacity of nova computing "
+"instances. A flavor is an available hardware configuration for a server. It "
+"defines the size of a virtual server that can be launched."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml6(title)
-msgid "Set up credentials for the keystone client"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_credentials.xml7(para)
+#: ./doc/common/section_cli_nova_boot.xml29(para)
 msgid ""
-"You can configure the <package>python-keystoneclient</package> with admin "
-"credentials with either an authentication token or a user name and password."
+"Any <emphasis role=\"bold\">user data</emphasis> files. A user data file is "
+"a special key in the metadata service that holds a file that cloud-aware "
+"applications in the guest instance can access. For example, one application "
+"that uses user data is the <link "
+"href=\"https://help.ubuntu.com/community/CloudInit\">cloud-init</link> "
+"system, which is an open-source package from Ubuntu that is available on "
+"various Linux distributions and that handles early initialization of a cloud"
+" instance."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml12(title)
-msgid "To configure the keystone client with an authentication token"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_credentials.xml15(para)
+#: ./doc/common/section_cli_nova_boot.xml42(para)
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml45(para)
 msgid ""
-"Export your keystone endpoint to the <varname>OS_SERVICE_ENDPOINT</varname> "
-"environment variable:"
-msgstr ""
+"Access and security credentials, which include one or both of the following "
+"credentials:"
+msgstr "アクセス、セキュリティクレデンシャル。以下のクレデンシャルの 1 つまたは両方が含まれます。"
 
-#: ./doc/common/section_cli_keystone_credentials.xml21(para)
+#: ./doc/common/section_cli_nova_boot.xml46(para)
 msgid ""
-"Export the administrator service token to the "
-"<varname>OS_SERVICE_TOKEN</varname> environment variable:"
+"A <emphasis role=\"bold\">key pair</emphasis> for your instance, which are "
+"SSH credentials that are injected into images when they are launched. For "
+"the key pair to be successfully injected, the image must contain the "
+"<literal>cloud-init</literal> package. Create at least one key pair for each"
+" project. If you already have generated a key pair with an external tool, "
+"you can import it into OpenStack. You can use the key pair for multiple "
+"instances that belong to that project."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml26(para)
-#: ./doc/common/section_cli_keystone_credentials.xml80(para)
+#: ./doc/common/section_cli_nova_boot.xml60(para)
 msgid ""
-"Alternatively, you can specify these parameters on any keystone client "
-"command:"
+"A <emphasis role=\"bold\">security group</emphasis> that defines which "
+"incoming network traffic is forwarded to instances. Security groups hold a "
+"set of firewall policies, known as <emphasis role=\"italic\">security group "
+"rules</emphasis>."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml30(para)
+#: ./doc/common/section_cli_nova_boot.xml71(para)
 msgid ""
-"<parameter>--os-endpoint "
-"<replaceable>SERVICE_ENDPOINT</replaceable></parameter>. An endpoint to use "
-"instead of the one in the service catalog. Defaults to "
-"<code>env[OS_SERVICE_ENDPOINT]</code>."
+"If needed, you can assign a <emphasis role=\"bold\">floating (public) IP "
+"address</emphasis> to a running instance."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml39(para)
+#: ./doc/common/section_cli_nova_boot.xml76(para)
 msgid ""
-"<parameter>--os-token <replaceable>SERVICE_TOKEN</replaceable></parameter>. "
-"An existing token to use instead of the one generated by authentication. "
-"Defaults to <code>env[OS_SERVICE_TOKEN]</code>."
+"You can also attach a block storage device, or <emphasis "
+"role=\"bold\">volume</emphasis>, for persistent storage."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml52(title)
-msgid "To configure the keystone client with a user name and password"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_credentials.xml55(para)
+#: ./doc/common/section_cli_nova_boot.xml82(para)
 msgid ""
-"Export the administrator user name to the <varname>OS_USERNAME</varname> "
-"environment variable:"
+"Instances that use the default security group cannot, by default, be "
+"accessed from any IP address outside of the cloud. If you want those IP "
+"addresses to access the instances, you must modify the rules for the default"
+" security group."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml61(para)
+#: ./doc/common/section_cli_nova_boot.xml87(para)
 msgid ""
-"Export the administrator password to the <varname>OS_PASSWORD</varname> "
-"environment variable:"
+"You can also assign a floating IP address to a running instance to make it "
+"accessible from outside the cloud. See <xref "
+"linkend=\"manage_ip_addresses\"/>."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml67(para)
+#: ./doc/common/section_cli_nova_boot.xml91(para)
 msgid ""
-"Export the tenant name to the <varname>OS_TENANT_NAME</varname> environment "
-"variable:"
+"After you gather the parameters that you need to launch an instance, you can"
+" launch it from an <link linkend=\"launch_from_image\">image</link> or a "
+"<link linkend=\"boot_from_volume\">volume</link>. You can launch an instance"
+" directly from one of the available OpenStack images or from an image that "
+"you have copied to a persistent volume. The OpenStack Image Service provides"
+" a pool of images that are accessible to members of different projects."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml73(para)
+#: ./doc/common/section_cli_nova_boot.xml101(title)
+msgid "Gather parameters to launch an instance"
+msgstr "インスタンスを起動するためのパラメーター情報の収集"
+
+#: ./doc/common/section_cli_nova_boot.xml103(para)
+msgid "Before you begin, source the OpenStack RC file."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot.xml106(para)
+#: ./doc/common/section_cli_nova_boot_from_volume.xml169(para)
+msgid "List the available flavors:"
+msgstr "利用可能なフレーバーを表示します。"
+
+#: ./doc/common/section_cli_nova_boot.xml108(para)
+msgid "Note the ID of the flavor that you want to use for your instance:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot.xml121(para)
+#: ./doc/common/section_cli_nova_boot_from_volume.xml155(para)
+msgid "List the available images:"
+msgstr "利用可能なイメージを表示します。"
+
+#: ./doc/common/section_cli_nova_boot.xml123(para)
+msgid "Note the ID of the image from which you want to boot your instance:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot.xml131(para)
 msgid ""
-"Export the URL of the keystone auth server, for example <link "
-"href=\"http://localhost:5000/v2.0'\">http://localhost:5000/v2.0'</link>, to "
-"the <varname>OS_AUTH_URL</varname> environment variable:"
+"You can also filter the image list by using <placeholder-1/> to find a "
+"specific image, as follows:"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml84(para)
+#: ./doc/common/section_cli_nova_boot.xml138(para)
+msgid "List the available security groups:"
+msgstr "利用可能なセキュリティグループを表示します。"
+
+#: ./doc/common/section_cli_nova_boot.xml140(para)
 msgid ""
-"<literal>--os-username <replaceable>OS_USERNAME</replaceable></literal>. "
-"Name used for authentication with the Identity Service. Defaults to "
-"<code>env[OS_USERNAME]</code>."
+"If you are an admin user, specify the <option>--all-tenants</option> "
+"parameter to list groups for all tenants."
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml92(para)
+#: ./doc/common/section_cli_nova_boot.xml145(para)
 msgid ""
-"<literal>--os-password <replaceable>OS_PASSWORD</replaceable></literal>. "
-"Password used for authentication with the Identity Service. Defaults to "
-"<code>env[OS_PASSWORD]</code>."
+"Note the ID of the security group that you want to use for your instance:"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml100(para)
+#: ./doc/common/section_cli_nova_boot.xml151(para)
 msgid ""
-"<literal>--os-tenant_name "
-"<replaceable>OS_TENANT_NAME</replaceable></literal>. Tenant for which to "
-"request authentication. Defaults to <code>env[OS_TENANT_NAME]</code>."
+"If you have not created any security groups, you can assign the instance to "
+"only the default security group."
+msgstr "セキュリティグループを作成していない場合、Default のセキュリティグループのみにインスタンスを割り当てることができます。"
+
+#: ./doc/common/section_cli_nova_boot.xml154(para)
+msgid "You can view rules for a specified security group:"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_credentials.xml108(para)
+#: ./doc/common/section_cli_nova_boot.xml159(para)
 msgid ""
-"<literal>--os-auth_url <replaceable>OS_AUTH_URL</replaceable></literal>. The"
-" Identity Service endpoint to use for authentication. Defaults to "
-"<code>env[OS_AUTH_URL]</code>."
+"List the available key pairs and note the name of the key pair that you use "
+"for SSH access."
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml6(title)
-msgid "Use the VNC console"
-msgstr ""
+#: ./doc/common/section_cli_nova_boot.xml168(title)
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml6(title)
+msgid "Launch an instance from an image"
+msgstr "イメージからのインスタンスの起動"
 
-#: ./doc/common/section_using-vnc-console.xml7(para)
+#: ./doc/common/section_cli_nova_boot.xml171(para)
 msgid ""
-"To interact through the VNC console, you can use a VNC client directly, a "
-"special Java client, or a web browser. For information about how to "
-"configure the console, see <xref linkend=\"installing-openstack-"
-"dashboard\"/>."
+"After you gather required parameters, run the following command to launch an"
+" instance. Specify the server name, flavor ID, and image ID."
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml15(title)
-msgid "Get an access URL"
-msgstr ""
-
-#: ./doc/common/section_using-vnc-console.xml16(para)
+#: ./doc/common/section_cli_nova_boot.xml174(para)
 msgid ""
-"The Compute service enables you to create access_urls through the os-"
-"consoles extension. Support for accessing this URL is provided by the nova "
-"client:"
+"Optionally, you can provide a key name for access control and a security "
+"group for security. You can also include metadata key and value pairs. For "
+"example, you can add a description for your server by providing the "
+"<parameter>--meta description=\"My Server\"</parameter> parameter."
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml19(replaceable)
-#: ./doc/common/section_using-vnc-console.xml25(replaceable)
-#: ./doc/common/section_using-vnc-console.xml52(replaceable)
-#: ./doc/common/section_using-vnc-console.xml65(replaceable)
-msgid "[server_id]"
-msgstr "[server_id]"
-
-#: ./doc/common/section_using-vnc-console.xml19(replaceable)
-msgid "[novnc|xvpvnc]"
-msgstr "[novnc|xvpvnc]"
-
-#: ./doc/common/section_using-vnc-console.xml20(para)
+#: ./doc/common/section_cli_nova_boot.xml181(para)
 msgid ""
-"Specify '<literal>novnc</literal>' to get a URL suitable for pasting into a "
-"web browser."
+"You can pass user data in a local file at instance launch by using the "
+"<parameter>--user-data <replaceable>USER-DATA-FILE</replaceable></parameter>"
+" parameter."
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml22(para)
+#: ./doc/common/section_cli_nova_boot.xml186(replaceable)
+msgid "FLAVOR_ID"
+msgstr "FLAVOR_ID"
+
+#: ./doc/common/section_cli_nova_boot.xml186(replaceable)
+#: ./doc/common/section_cli_nova_boot_from_volume.xml329(replaceable)
+msgid "IMAGE_ID"
+msgstr "IMAGE_ID"
+
+#: ./doc/common/section_cli_nova_boot.xml186(replaceable)
+msgid "KEY_NAME"
+msgstr "KEY_NAME"
+
+#: ./doc/common/section_cli_nova_boot.xml187(replaceable)
+msgid "USER_DATA_FILE"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot.xml187(replaceable)
+msgid "SEC_GROUP"
+msgstr "SEC_GROUP"
+
+#: ./doc/common/section_cli_nova_boot.xml187(replaceable)
+msgid "KEY=VALUE"
+msgstr "KEY=VALUE"
+
+#: ./doc/common/section_cli_nova_boot.xml188(replaceable)
+#: ./doc/common/section_cli_nova_startstop.xml14(replaceable)
+#: ./doc/common/section_cli_nova_startstop.xml18(replaceable)
+#: ./doc/common/section_cli_nova_startstop.xml35(replaceable)
+#: ./doc/common/section_cli_nova_startstop.xml40(replaceable)
+#: ./doc/common/section_cli_nova_get_console.xml8(replaceable)
+msgid "INSTANCE_NAME"
+msgstr "INSTANCE_NAME"
+
+#: ./doc/common/section_cli_nova_boot.xml189(para)
 msgid ""
-"Specify '<literal>xvpvnc</literal>' for a URL suitable for pasting into the "
-"Java client."
+"The following command launches the <literal>MyCirrosServer</literal> "
+"instance with the <literal>m1.small</literal> flavor (ID of "
+"<literal>1</literal>), <literal>cirros-0.3.2-x86_64-uec</literal> image (ID "
+"of <literal>397e713c-b95b-4186-ad46-6126863ea0a9</literal>), "
+"<literal>default</literal> security group, <literal>KeyPair01</literal> key,"
+" and a user data file called <filename>cloudinit.file</filename>:"
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml24(para)
-msgid "To request a web browser URL:"
-msgstr ""
+#: ./doc/common/section_cli_nova_boot.xml202(replaceable)
+msgid "myCirrosServer"
+msgstr "myCirrosServer"
 
-#: ./doc/common/section_using-vnc-console.xml28(title)
-msgid "Access a VNC console with a Java client"
-msgstr ""
-
-#: ./doc/common/section_using-vnc-console.xml29(para)
+#: ./doc/common/section_cli_nova_boot.xml203(para)
 msgid ""
-"To enable support for the OpenStack Java VNC client in compute, run the "
-"<literal>nova-xvpvncproxy</literal> service."
-msgstr ""
+"Depending on the parameters that you provide, the command returns a list of "
+"server properties."
+msgstr "指定のパラメーターにより、コマンドはサーバーのプロパティ一覧を返します。"
 
-#: ./doc/common/section_using-vnc-console.xml34(para)
+#: ./doc/common/section_cli_nova_boot.xml206(para)
 msgid ""
-"<literal>xvpvncproxy_port</literal>=<replaceable>[port]</replaceable> - port"
-" to bind (defaults to 6081)"
-msgstr ""
+"A status of <literal>BUILD</literal> indicates that the instance has "
+"started, but is not yet online."
+msgstr "<literal>BUILD</literal> の状態は、インスタンスが起動しているがオンラインにはなっていないことを示しています。"
 
-#: ./doc/common/section_using-vnc-console.xml38(para)
+#: ./doc/common/section_cli_nova_boot.xml209(para)
 msgid ""
-"<literal>xvpvncproxy_host</literal>=<replaceable>[host]</replaceable> - host"
-" to bind (defaults to 0.0.0.0)"
-msgstr ""
+"A status of <literal>ACTIVE</literal> indicates that the instance is active."
+msgstr "<literal>ACTIVE</literal> の状態は、インスタンスがアクティブであることを示しています。"
 
-#: ./doc/common/section_using-vnc-console.xml42(para)
+#: ./doc/common/section_cli_nova_boot.xml241(para)
 msgid ""
-"As a client, you need a special Java client, which is a slightly modified "
-"version of TightVNC that supports our token auth:"
-msgstr ""
+"Copy the server ID value from the <literal>id</literal> field in the output."
+" You use this ID to get details for or delete your server."
+msgstr "出力の <literal>id</literal> フィールドからサーバー ID の値をコピーします。この ID を使用して詳細を取得するか、サーバーを削除します。"
 
-#: ./doc/common/section_using-vnc-console.xml48(para)
+#: ./doc/common/section_cli_nova_boot.xml245(para)
 msgid ""
-"To create a session, request an access URL by using <placeholder-1/>. Then, "
-"run the client as follows."
+"Copy the administrative password value from the <literal>adminPass</literal>"
+" field. You use this value to log in to your server."
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml51(para)
-msgid "To get an access URL:"
-msgstr ""
-
-#: ./doc/common/section_using-vnc-console.xml53(para)
-msgid "To run the client:"
-msgstr ""
-
-#: ./doc/common/section_using-vnc-console.xml54(replaceable)
-msgid "[access_url]"
-msgstr "[access_url]"
-
-#: ./doc/common/section_using-vnc-console.xml59(title)
-msgid "Access a VNC console with a web browser"
-msgstr ""
-
-#: ./doc/common/section_using-vnc-console.xml61(para)
+#: ./doc/common/section_cli_nova_boot.xml249(para)
 msgid ""
-"Retrieving an access_url for a web browser is similar to the flow for the "
-"Java client."
+"You can also place arbitrary local files into the instance file system at "
+"creation time by using the <option>--file &lt;dst-path=src-path&gt;</option>"
+" option. You can store up to five files. For example, if you have a special "
+"authorized keys file named <filename>special_authorized_keysfile</filename> "
+"that you want to put on the instance rather than using the regular SSH key "
+"injection, you can use the <option>--file</option> option as shown in the "
+"following example:"
 msgstr ""
 
-#: ./doc/common/section_using-vnc-console.xml63(para)
-msgid "To get the access URL, run the following command:"
-msgstr ""
+#: ./doc/common/section_cli_nova_boot.xml266(para)
+msgid "Check if the instance is online:"
+msgstr "インスタンスがオンラインになっているかどうかをチェックします。"
 
-#: ./doc/common/section_using-vnc-console.xml66(para)
-msgid "Paste the URL into your web browser."
-msgstr ""
-
-#: ./doc/common/section_using-vnc-console.xml68(para)
+#: ./doc/common/section_cli_nova_boot.xml268(para)
 msgid ""
-"Additionally, you can use the OpenStack dashboard, known as horizon, to "
-"access browser-based VNC consoles for instances."
+"The list shows the ID, name, status, and private (and if assigned, public) "
+"IP addresses for all instances in the project to which you belong:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml6(title)
-msgid "Configure tenant-specific image locations with Object Storage"
-msgstr ""
+#: ./doc/common/section_cli_nova_boot.xml278(para)
+msgid "If the status for the instance is ACTIVE, the instance is online."
+msgstr "インスタンスの状態が ACTIVE の場合、インスタンスはオンラインです。"
 
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml14(para)
-msgid "The tenant who owns the image"
-msgstr ""
-
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml17(para)
+#: ./doc/common/section_cli_nova_boot.xml280(para)
 msgid ""
-"Tenants that are defined in <option>swift_store_admin_tenants</option> and "
-"that have admin-level accounts"
-msgstr ""
+"To view the available options for the <placeholder-1/> command, run the "
+"following command:"
+msgstr "<placeholder-1/> コマンドで利用可能なオプションを確認するには、以下のコマンドを実行します。"
 
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml8(para)
+#: ./doc/common/section_cli_nova_boot.xml287(para)
 msgid ""
-"For some deployers, it is not ideal to store all images in one place to "
-"enable all tenants and users to access them. You can configure the Image "
-"Service to store image data in tenant-specific image locations. Then, only "
-"the following tenants can use the Image Service to access the created "
-"image:<placeholder-1/>"
+"If you did not provide a key pair, security groups, or rules, you can access"
+" the instance only from inside the cloud through VNC. Even pinging the "
+"instance is not possible."
 msgstr ""
 
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml23(title)
-msgid "To configure tenant-specific image locations"
+#: ./doc/common/section_user-data.xml6(title)
+msgid "Configure instances at boot"
 msgstr ""
 
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml25(para)
+#: ./doc/common/section_user-data.xml7(para)
 msgid ""
-"Configure swift as your <option>default_store</option> in the <filename"
-">glance-api.conf</filename> file."
+"When you boot instances in an OpenStack cloud, you can use user data or "
+"<package>cloud-init</package> to automatically configure instances at boot "
+"time. You might want to install some packages, start services, or manage "
+"your instance by using a Puppet or Chef server."
 msgstr ""
 
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml33(para)
+#: ./doc/common/section_user-data.xml13(title)
+msgid "User data"
+msgstr "ユーザーデータ"
+
+#: ./doc/common/section_user-data.xml14(para)
 msgid ""
-"<option>swift_store_multi_tenant</option>. Set to <literal>True</literal> to"
-" enable tenant-specific storage locations. Default is "
-"<literal>False</literal>."
+"User data is the mechanism by which a user can pass information contained in"
+" a local file to an instance at launch time. The typical use case is to pass"
+" something like a shell script or a configuration file as user data."
 msgstr ""
 
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml39(para)
+#: ./doc/common/section_user-data.xml19(para)
 msgid ""
-"<option>swift_store_admin_tenants</option>. Specify a list of tenant IDs "
-"that can grant read and write access to all Object Storage containers that "
-"are created by the Image Service."
+"User data is sent using the <literal>--user-data "
+"<replaceable>/path/to/filename</replaceable></literal> option when calling "
+"<placeholder-1/>. This example creates a text file and sends its contents as"
+" user data to the instance:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml30(para)
+#: ./doc/common/section_user-data.xml26(para)
 msgid ""
-"Set these configuration options in the <filename>glance-api.conf</filename> "
-"file: <placeholder-1/>"
+"The instance can get user data by querying the metadata service through "
+"either the OpenStack metadata API or the EC2 compatibility API:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml48(para)
+#: ./doc/common/section_user-data.xml34(para)
 msgid ""
-"With this configuration, images are stored in an Object Storage service "
-"(swift) endpoint that is pulled from the service catalog for the "
-"authenticated user."
+"The Compute service treats user data as a blob. While the previous example "
+"uses a text file, user data can be in any format."
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml11(title)
-msgid "Telemetry command-line client"
+#: ./doc/common/section_user-data.xml38(para)
+msgid "For more information, see <xref linkend=\"config-drive\"/>."
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml12(para)
+#: ./doc/common/section_user-data.xml42(package)
+msgid "cloud-init"
+msgstr "cloud-init"
+
+#: ./doc/common/section_user-data.xml43(para)
 msgid ""
-"The <placeholder-1/> client is the command-line interface (CLI) for the "
-"Telemetry API and its extensions. This chapter documents <placeholder-2/> "
-"version 1.0.10."
+"To do something useful with the user data, you must configure the virtual "
+"machine image to run a service on boot that gets user data from the metadata"
+" service and takes some action based on the contents of the data. The "
+"<package>cloud-init</package> package does exactly this. This package is "
+"compatible with the Compute metadata service and the Compute configuration "
+"drive."
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml22(title)
-msgid "ceilometer usage"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml42(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml459(para)
-msgid "Create a new alarm based on state of other alarms."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml50(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml601(para)
-msgid "Update an existing alarm based on state of other alarms."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml59(para)
-msgid "Create a new alarm (Deprecated). Use alarm-threshold- create instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml68(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml746(para)
-msgid "Delete an alarm."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml76(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml763(para)
-msgid "Display the change history of an alarm."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml84(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml790(para)
-msgid "List the user's alarms."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml92(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml809(para)
-msgid "Show an alarm."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml100(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml826(para)
-msgid "Get the state of an alarm."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml108(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml843(para)
-msgid "Set the state of an alarm."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml116(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml884(para)
-msgid "Create a new alarm based on computed statistics."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml124(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1074(para)
-msgid "Update an existing alarm based on computed statistics."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml132(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1279(para)
-msgid "Update an existing alarm (Deprecated)."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml140(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1468(para)
-msgid "List events."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml148(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1487(para)
-msgid "Show a particular event."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml156(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1504(para)
-msgid "List event types."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml164(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1511(para)
-msgid "List the user's meters."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml172(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1531(para)
-msgid "Query Alarm History."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml180(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1567(para)
-msgid "Query Alarms."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml188(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1603(para)
-msgid "Query samples."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml196(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1639(para)
-msgid "List the resources."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml204(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1658(para)
-msgid "Show the resource."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml212(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1681(para)
-msgid "Create a sample."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml220(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1764(para)
-msgid "List the samples for a meter."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml228(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1800(para)
-msgid "List the statistics for a meter."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml236(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1853(para)
-msgid "List trait info for an event type."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml244(para)
-msgid "List trait all traits with name &lt;trait_name&gt; for Event Type"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml253(para)
-#: ./doc/common/ch_cli_keystone_commands.xml324(para)
-#: ./doc/common/ch_cli_heat_commands.xml303(para)
-msgid "Prints all of the commands and options to stdout."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml270(title)
-msgid "ceilometer optional arguments"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml283(para)
-msgid "Defaults to <code>env[CEILOMETERCLIENT_DEBUG]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml291(para)
-#: ./doc/common/ch_cli_heat_commands.xml341(para)
-msgid "Print more verbose output."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml299(para)
+#: ./doc/common/section_user-data.xml51(para)
 msgid ""
-"Explicitly allow ceilometerclient to perform \"insecure\" SSL (https) "
-"requests. The server's certificate will not be verified against any "
-"certificate authorities. This option should be used with caution."
+"The <package>cloud-init</package> package supports multiple cloud providers."
+" You can use the same virtual machine image in different clouds without "
+"modification. The <package>cloud-init</package> package is an open source "
+"project and the source code is available on <link "
+"href=\"http://launchpad.net/cloud-init\">Launchpad</link>. It is maintained "
+"by Canonical, the company that runs the Ubuntu project. All Ubuntu cloud "
+"images come pre-installed with <package>cloud-init</package>. However, "
+"<package>cloud-init</package> is not designed to be Ubuntu-specific and has "
+"been successfully ported to several other platforms including Fedora."
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml311(para)
-#: ./doc/common/ch_cli_glance_commands.xml262(para)
-#: ./doc/common/ch_cli_heat_commands.xml360(para)
+#: ./doc/common/section_user-data.xml66(para)
 msgid ""
-"Path of certificate file to use in SSL connection. This file can optionally "
-"be prepended with the private key."
+"Even if you do not use user data to configure instance behavior at boot "
+"time, install <package>cloud-init</package> on images that you create "
+"because this package provides useful functionality. For example, the "
+"<package>cloud-init</package> package enables you to copy the public key to "
+"an account (the <literal>ubuntu</literal> account by default on Ubuntu "
+"instances, the <literal>ec2-user</literal> by default in Fedora instances)."
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml321(para)
-#: ./doc/common/ch_cli_glance_commands.xml272(para)
+#: ./doc/common/section_user-data.xml75(para)
 msgid ""
-"Path of client key to use in SSL connection. This option is not necessary if"
-" your key is prepended to your cert file."
+"If you do not have <package>cloud-init</package> installed, you must "
+"manually configure your image to get the public key from the metadata "
+"service on boot and copy it to the appropriate account."
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml331(para)
+#: ./doc/common/section_user-data.xml81(title)
+msgid "<package>cloud-init</package> supported formats and documentation"
+msgstr ""
+
+#: ./doc/common/section_user-data.xml83(para)
 msgid ""
-"Path of CA TLS certificate(s) used to verifythe remote server's certificate."
-" Without this option ceilometer looks for the default system CA "
-"certificates."
+"Look at the <package>cloud-init</package><link "
+"href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-"
+"init/trunk/view/head:/doc/userdata.txt\">doc/userdata.txt</link> file the "
+"<link href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-"
+"init/trunk/files/head:/doc/examples/\">examples</link> directory and the "
+"<link href=\"https://help.ubuntu.com/community/CloudInit\">Ubuntu community "
+"documentation</link> for details about how to use <package>cloud-"
+"init</package>. Some basic examples are provided here."
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml341(para)
-#: ./doc/common/ch_cli_glance_commands.xml292(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use --os-cacert."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml349(para)
-msgid "Number of seconds to wait for a response."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml405(para)
-#: ./doc/common/ch_cli_heat_commands.xml447(para)
-msgid "Defaults to <code>env[OS_AUTH_TOKEN]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml413(para)
-msgid "Defaults to <code>env[CEILOMETER_URL]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml421(para)
-msgid "Defaults to <code>env[CEILOMETER_API_VERSION]</code> or 2."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml429(para)
-#: ./doc/common/ch_cli_heat_commands.xml480(para)
-msgid "Defaults to <code>env[OS_SERVICE_TYPE]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml437(para)
-#: ./doc/common/ch_cli_heat_commands.xml488(para)
-msgid "Defaults to <code>env[OS_ENDPOINT_TYPE]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml445(title)
-msgid "ceilometer alarm-combination-create command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml466(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml891(para)
-msgid "Name of the alarm (must be unique per tenant). Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml475(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml624(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml900(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1097(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1302(para)
-msgid "Tenant to associate with alarm (only settable by admin users)."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml484(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml633(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml909(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1106(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1311(para)
-msgid "User to associate with alarm (only settable by admin users)."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml493(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml642(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml918(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1115(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1320(para)
-msgid "Free text description of the alarm."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml501(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml650(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml926(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1123(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1328(para)
-msgid "State of the alarm, one of: ['ok', 'alarm', 'insufficient_data']"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml510(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml659(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml935(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1132(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1337(para)
-msgid "True if alarm evaluation/actioning is enabled."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml518(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml667(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml943(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1140(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1345(para)
+#: ./doc/common/section_user-data.xml93(para)
 msgid ""
-"URL to invoke when state transitions to alarm. May be used multiple times. "
-"Defaults to None."
+"<package>cloud-init</package> supports several input formats for user data. "
+"Two commonly used formats are:"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml527(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml676(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml952(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1149(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1354(para)
+#: ./doc/common/section_user-data.xml98(para)
+msgid "Shell scripts (starts with <literal>#!</literal>)"
+msgstr ""
+
+#: ./doc/common/section_user-data.xml102(para)
+msgid "Cloud config files (starts with <literal>#cloud-config</literal>)"
+msgstr ""
+
+#: ./doc/common/section_user-data.xml108(title)
+msgid "Run a shell script on boot"
+msgstr ""
+
+#: ./doc/common/section_user-data.xml109(para)
 msgid ""
-"URL to invoke when state transitions to OK. May be used multiple times. "
-"Defaults to None."
+"Assuming you have <package>cloud-init</package> installed, the simplest way "
+"to configure an instance on boot is to pass a shell script as user data. The"
+" shell file must begin with <literal>#!</literal> in order for <package"
+">cloud-init</package> to recognize it as a shell script. This example shows "
+"a script that creates a <literal>clouduser</literal> account:"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml536(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml685(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml961(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1158(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1363(para)
+#: ./doc/common/section_user-data.xml118(para)
 msgid ""
-"URL to invoke when state transitions to insufficient_data. May be used "
-"multiple times. Defaults to None."
+"Sending a shell script as user data has a similar effect to writing an "
+"<filename>/etc/rc.local</filename> script: it executes very late in the boot"
+" sequence as root."
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml546(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml695(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml971(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1168(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1373(para)
+#: ./doc/common/section_user-data.xml123(title)
+msgid "Cloud-config format"
+msgstr ""
+
+#: ./doc/common/section_user-data.xml124(para)
 msgid ""
-"Only evaluate the alarm if the time at evaluation is within this time "
-"constraint. Start point(s) of the constraint are specified with a cron "
-"expression , whereas its duration is given in seconds. Can be specified "
-"multiple times for multiple time constraints, format is: "
-"name=&lt;CONSTRAINT_NAME&gt;;start=&lt; "
-"CRON&gt;;duration=&lt;SECONDS&gt;;[description=&lt;DESCRIPTION&gt;;[t "
-"imezone=&lt;IANA Timezone&gt;]] Defaults to None."
+"<package>cloud-init</package> supports a YAML-based config format that "
+"allows the user to configure a large number of options on a system. User "
+"data that begins with <literal>#cloud-config</literal> will be interpreted "
+"by <package>cloud-init</package> as cloud-config format."
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml561(para)
-msgid "List of alarm ids. Required."
+#: ./doc/common/section_user-data.xml132(title)
+msgid "Example: Set the host name"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml569(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml727(para)
-msgid "Operator to compare with, one of: ['and', 'or']."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml577(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1046(para)
+#: ./doc/common/section_user-data.xml133(para)
 msgid ""
-"True if actions should be repeatedly notified while alarm remains in target "
-"state. Defaults to False."
+"This <package>cloud-init</package> user data example sets the hostname and "
+"the FQDN, as well as updating <filename>/etc/hosts</filename> on the "
+"instance:"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml586(title)
-msgid "ceilometer alarm-combination-update command"
+#: ./doc/common/section_user-data.xml145(title)
+msgid "Example: Configure instances with Puppet"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml608(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1081(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1286(para)
-msgid "ID of the alarm to update. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml616(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1089(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1294(para)
-msgid "Name of the alarm (must be unique per tenant)."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml710(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1183(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1388(para)
-msgid "Name or list of names of the time constraints to remove."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml719(para)
-msgid "List of alarm id."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml735(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1252(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1457(para)
+#: ./doc/common/section_user-data.xml146(para)
 msgid ""
-"True if actions should be repeatedly notified while alarm remains in target "
-"state."
+"This <package>cloud-init</package> user data example, based on <link "
+"href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-"
+"init/trunk/view/head:/doc/examples/cloud-config-puppet.txt\">doc/examples"
+"/cloud-config-puppet.txt</link>, would configure the instance to contact a "
+"Puppet server at puppetmaster.example.org and verify its identity by using a"
+" certificate."
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml744(title)
-msgid "ceilometer alarm-delete command"
+#: ./doc/common/section_user-data.xml174(title)
+msgid "Example: Configure instances with Chef"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml753(para)
-msgid "ID of the alarm to delete. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml761(title)
-msgid "ceilometer alarm-history command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml770(para)
-msgid "ID of the alarm for which history is shown. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml778(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml797(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1036(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1242(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1518(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1646(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1771(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1807(para)
+#: ./doc/common/section_user-data.xml175(para)
 msgid ""
-"key[op]data_type::value; list. data_type is optional, but if supplied must "
-"be string, integer, float, or boolean."
+"This <package>cloud-init</package> user data example, based on <link "
+"href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-"
+"init/trunk/view/head:/doc/examples/cloud-config-chef.txt\">doc/examples"
+"/cloud-config/chef.txt</link> and intended for use in an Ubuntu image, adds "
+"the Chef apt repository, installs Chef, connects to a Chef server at "
+"<literal>https://chefserver.example.com:4000</literal>, and installs Apache:"
 msgstr ""
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml788(title)
-msgid "ceilometer alarm-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml807(title)
-msgid "ceilometer alarm-show command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml816(para)
-msgid "ID of the alarm to show. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml824(title)
-msgid "ceilometer alarm-state-get command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml833(para)
-msgid "ID of the alarm state to show. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml841(title)
-msgid "ceilometer alarm-state-set command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml850(para)
-msgid "ID of the alarm state to set. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml858(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_getstart_conceptual_arch.xml16(None)
 msgid ""
-"State of the alarm, one of: ['ok', 'alarm', 'insufficient_data']. Required."
-msgstr ""
+"@@image: 'figures/openstack_havana_conceptual_arch.png'; "
+"md5=96e1d5492d4c865fc9145710bb294a91"
+msgstr "@@image: 'figures/openstack_havana_conceptual_arch.png'; md5=96e1d5492d4c865fc9145710bb294a91"
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml867(title)
-msgid "ceilometer alarm-threshold-create command"
-msgstr ""
+#: ./doc/common/section_getstart_conceptual_arch.xml6(title)
+msgid "Conceptual architecture"
+msgstr "概念アーキテクチャー"
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml986(para)
-msgid "Metric to evaluate against. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml994(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1200(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1397(para)
-msgid "Length of each period (seconds) to evaluate over."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1002(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1208(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1405(para)
-msgid "Number of periods to evaluate over."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1010(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1216(para)
-msgid "Statistic to evaluate, one of: ['max', 'min', 'avg', 'sum', 'count']."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1019(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1225(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1430(para)
+#: ./doc/common/section_getstart_conceptual_arch.xml7(para)
 msgid ""
-"Operator to compare with, one of: ['lt', 'le', 'eq', 'ne', 'ge', 'gt']."
-msgstr ""
+"The following diagram shows the relationships among the OpenStack services:"
+msgstr "以下の図は OpenStack サービス間の関連性を示します。"
 
-#: ./doc/common/ch_cli_ceilometer_commands.xml1028(para)
-msgid "Threshold to evaluate against. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1055(title)
-msgid "ceilometer alarm-threshold-update command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1192(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1413(para)
-msgid "Metric to evaluate against."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1234(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1439(para)
-msgid "Threshold to evaluate against."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1261(title)
-msgid "ceilometer alarm-update command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1421(para)
-msgid "Statistic to evaluate, one of: ['max', 'min', 'avg', 'sum', 'count']"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1447(para)
-msgid ""
-"A meter should match this resource metadata (key=value) additionally to the "
-"meter_name. Defaults to None."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1466(title)
-msgid "ceilometer event-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1475(para)
-msgid ""
-"key[op]data_type::value; list. data_type is optional, but if supplied must "
-"be string, integer, floator datetime."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1485(title)
-msgid "ceilometer event-show command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1494(para)
-msgid "The id of the event. Should be a UUID Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1502(title)
-msgid "ceilometer event-type-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1509(title)
-msgid "ceilometer meter-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1528(title)
-msgid "ceilometer query-alarm-history command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1538(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1574(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1610(para)
-msgid ""
-"{complex_op: [{simple_op: {field_name: value}}]} The complex_op is one of: "
-"['and', 'or'], simple_op is one of: ['=', '!=', '&lt;', '&lt;=', '&gt;', "
-"'&gt;=']."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1548(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1584(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1620(para)
-msgid ""
-"[{field_name: direction}, {field_name: direction}] The direction is one of: "
-"['asc', 'desc']."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1557(para)
-msgid "Maximum number of alarm history items to return."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1565(title)
-msgid "ceilometer query-alarms command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1593(para)
-msgid "Maximum number of alarms to return."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1601(title)
-msgid "ceilometer query-samples command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1629(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1789(para)
-msgid "Maximum number of samples to return."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1637(title)
-msgid "ceilometer resource-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1656(title)
-msgid "ceilometer resource-show command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1665(para)
-msgid "ID of the resource to show. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1673(title)
-msgid "ceilometer sample-create command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1688(para)
-msgid "Tenant to associate with sample (only settable by admin users)."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1697(para)
-msgid "User to associate with sample (only settable by admin users)."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1706(para)
-msgid "ID of the resource. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1714(para)
-msgid "The meter name. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1722(para)
-msgid "The meter type. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1730(para)
-msgid "The meter unit. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1738(para)
-msgid "The sample volume. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1746(para)
-msgid "Resource metadata."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1754(para)
-msgid "The sample timestamp."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1762(title)
-msgid "ceilometer sample-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1781(para)
-#: ./doc/common/ch_cli_ceilometer_commands.xml1817(para)
-msgid "Name of meter to show samples for. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1797(title)
-msgid "ceilometer statistics command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1825(para)
-msgid "Period in seconds over which to group samples."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1833(para)
-msgid "Field for group by."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1841(para)
-msgid ""
-"Function for data aggregation. Available aggregates are: count, cardinality,"
-" min, max, sum, stddev, avg. Defaults to []."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1851(title)
-msgid "ceilometer trait-description-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1860(para)
-msgid "Type of the event for which traits will be shown. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1869(title)
-msgid "ceilometer trait-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1871(para)
-msgid ""
-"List trait all traits with name &lt;trait_name&gt; for Event Type "
-"&lt;event_type&gt;."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1878(para)
-msgid "Type of the event for which traits will listed. Required."
-msgstr ""
-
-#: ./doc/common/ch_cli_ceilometer_commands.xml1887(para)
-msgid "The name of the trait to list. Required."
-msgstr ""
-
-#: ./doc/common/section_conventions.xml8(title)
-msgid "Conventions"
-msgstr "表記規則"
-
-#: ./doc/common/section_conventions.xml9(para)
-msgid "The OpenStack documentation uses several typesetting conventions."
-msgstr "OpenStack のドキュメントは、いくつかの植字の表記方法を採用しています。"
-
-#: ./doc/common/section_conventions.xml13(title)
-msgid "Notices"
-msgstr "注意"
-
-#: ./doc/common/section_conventions.xml14(para)
-msgid "Notices take three forms:"
-msgstr "注意には以下の 3 種類があります。"
-
-#: ./doc/common/section_conventions.xml16(para)
-msgid ""
-"The information in a note is usually in the form of a handy tip or reminder."
-msgstr "注記にある情報は一般的にちょっとしたヒントや備忘録の形式をとります。"
-
-#: ./doc/common/section_conventions.xml20(para)
-msgid ""
-"The information in an important notice is something you must be aware of "
-"before proceeding."
-msgstr "重要にある情報は続行する前に注意する必要があります。"
-
-#: ./doc/common/section_conventions.xml24(para)
-msgid ""
-"The information in warnings is critical. Warnings provide additional "
-"information about risk of data loss or security issues."
-msgstr "警告にある情報は致命的なものです。データ損失やセキュリティ問題のリスクに関する追加情報が提供されます。"
-
-#: ./doc/common/section_conventions.xml31(title)
-msgid "Command prompts"
-msgstr "コマンドプロンプト"
-
-#: ./doc/common/section_conventions.xml32(para)
-msgid ""
-"Commands prefixed with the <literal>#</literal> prompt are to be executed by"
-" the <literal>root</literal> user. These examples can also be executed by "
-"using the <placeholder-1/> command, if available."
-msgstr "<literal>#</literal> プロンプトから始まるコマンドは、<literal>root</literal> ユーザーにより実行されます。これらの例は、利用可能ならば、<placeholder-1/> コマンドを用いて実行することもできます。"
-
-#: ./doc/common/section_conventions.xml36(para)
-msgid ""
-"Commands prefixed with the <literal>$</literal> prompt can be executed by "
-"any user, including <literal>root</literal>."
-msgstr "<literal>$</literal> プロンプトから始まるコマンドは、<literal>root</literal> を含む、すべてのユーザーにより実行できます。"
+#: ./doc/common/section_getstart_conceptual_arch.xml11(title)
+msgid "OpenStack conceptual architecture"
+msgstr "OpenStack の概念アーキテクチャー"
 
 #: ./doc/common/ch_cli_neutron_commands.xml11(title)
 msgid "Networking command-line client"
@@ -9852,458 +8416,801 @@ msgstr ""
 msgid "ID or name of vpnservice to update"
 msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml7(title)
-msgid "Create and manage services and service users"
-msgstr "サービスとサービスユーザーの作成と管理"
+#: ./doc/common/section_keystone-concepts-service-management.xml5(title)
+msgid "Service management"
+msgstr "サービス管理"
 
-#: ./doc/common/section_cli_keystone_services.xml8(para)
-msgid "The Identity Service enables you to define services, as follows:"
-msgstr "Identity  により、以下のようなサービスを定義できます。"
-
-#: ./doc/common/section_cli_keystone_services.xml12(para)
+#: ./doc/common/section_keystone-concepts-service-management.xml6(para)
 msgid ""
-"Service catalog template. The Identity Service acts as a service catalog of "
-"endpoints for other OpenStack services. The "
-"<literal>etc/default_catalog.templates</literal> template file defines the "
-"endpoints for services. When the Identity Service uses a template file back "
-"end, any changes that are made to the endpoints are cached. These changes do"
-" not persist when you restart the service or reboot the machine."
-msgstr "サービスカタログテンプレート。Identity は、他の OpenStack サービスのエンドポイントのサービスカタログとして動作します。<literal>etc/default_catalog.templates</literal> テンプレートファイルは、サービスのエンドポイントを定義します。Identity がテンプレートファイルバックエンドを使用するとき、エンドポイントに対して実行された変更はすべてキャッシュされます。サービスの再起動やマシンの再起動をしたとき、これらの変更は保持されません。"
+"The Identity Service provides identity, token, catalog, and policy services."
+" It consists of:"
+msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml23(para)
+#: ./doc/common/section_keystone-concepts-service-management.xml11(para)
 msgid ""
-"A SQL back end for the catalog service. When the Identity Service is online,"
-" you must add the services to the catalog. When you deploy a system for "
-"production, use the SQL back end."
-msgstr "カタログサービスの SQL バックエンド。Identity がオンラインのとき、サービスをカタログに追加する必要があります。システムを本番環境に導入するとき、SQL バックエンドを使用します。"
+"<systemitem class=\"service\">keystone-all</systemitem>. Starts both the "
+"service and administrative APIs in a single process to provide Catalog, "
+"Authorization, and Authentication services for OpenStack."
+msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml29(para)
+#: ./doc/common/section_keystone-concepts-service-management.xml17(para)
 msgid ""
-"The <literal>auth_token</literal> middleware supports the use of either a "
-"shared secret or users for each service."
-msgstr "<literal>auth_token</literal> ミドルウェアは、共有シークレットの使用、各サービス用のユーザーの使用をサポートします。"
+"Identity Service functions. Each has a pluggable back end that allows "
+"different ways to use the particular service. Most support standard back "
+"ends like LDAP or SQL."
+msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml32(para)
+#: ./doc/common/section_keystone-concepts-service-management.xml23(para)
 msgid ""
-"To authenticate users against the Identity Service, you must create a "
-"service user for each OpenStack service. For example, create a service user "
-"for the Compute, Block Storage, and Networking services."
-msgstr "Identity に対してユーザーを認証するために、各 OpenStack サービスのサービスユーザーを作成する必要があります。例えば、Compute、Block Storage、Networking のサービスのサービスユーザーを作成します。"
+"The Identity Service also maintains a user that corresponds to each service,"
+" such as, a user named <emphasis>nova</emphasis> for the Compute service, "
+"and a special service tenant called <emphasis>service</emphasis>."
+msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml36(para)
+#: ./doc/common/section_keystone-concepts-service-management.xml28(para)
 msgid ""
-"To configure the OpenStack services with service users, create a project for"
-" all services and create users for each service. Assign the admin role to "
-"each service user and project pair. This role enables users to validate "
-"tokens and authenticate and authorize other user requests."
-msgstr "サービスユーザーを持つ OpenStack サービスを設定するために、すべてのサービスのプロジェクトを作成し、各サービスのユーザーを作成します。各サービスユーザーとプロジェクトのペアに admin ロールを割り当てます。このロールにより、ユーザーがトークンを検証し、他のユーザーのリクエストを認証、認可できます。"
+"For information about how to create services and endpoints, see the <link "
+"href=\"http://docs.openstack.org/user-guide-"
+"admin/content/index.html\"><citetitle>OpenStack Admin User "
+"Guide</citetitle></link>."
+msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml42(title)
-msgid "Create a service"
-msgstr "サービスの作成"
-
-#: ./doc/common/section_cli_keystone_services.xml45(para)
-msgid "List the available services:"
-msgstr "利用可能なサービスを一覧表示します。"
-
-#: ./doc/common/section_cli_keystone_services.xml59(para)
-msgid "To create a service, run this command:"
-msgstr "サービスを作成するために、このコマンドを実行します。"
-
-#: ./doc/common/section_cli_keystone_services.xml60(replaceable)
-msgid "service_name"
-msgstr "service_name"
-
-#: ./doc/common/section_cli_keystone_services.xml60(replaceable)
-msgid "service_type"
-msgstr "service_type"
-
-#: ./doc/common/section_cli_keystone_services.xml60(replaceable)
-msgid "service_description"
-msgstr "service_description"
-
-#: ./doc/common/section_cli_keystone_services.xml61(para)
-msgid "The arguments are:"
-msgstr "引数は以下のとおりです。"
-
-#: ./doc/common/section_cli_keystone_services.xml64(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_trusted-compute-pools.xml45(None)
+#: ./doc/common/section_trusted-compute-pools.xml50(None)
 msgid ""
-"<code><replaceable>service_name</replaceable></code>. The unique name of the"
-" new service."
-msgstr "<code><replaceable>service_name</replaceable></code>。新しいサービスの一意な名前。"
+"@@image: 'figures/OpenStackTrustedComputePool1.png'; "
+"md5=858fbd6148b927723cea5ad2c88d54bd"
+msgstr "@@image: 'figures/OpenStackTrustedComputePool1.png'; md5=858fbd6148b927723cea5ad2c88d54bd"
 
-#: ./doc/common/section_cli_keystone_services.xml68(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_trusted-compute-pools.xml150(None)
+#: ./doc/common/section_trusted-compute-pools.xml155(None)
 msgid ""
-"<code><replaceable>service_type</replaceable></code>. The service type, such"
-" as <code>identity</code>, <code>compute</code>, <code>network</code>, "
-"<code>image</code>, <code>object-store</code> or any other service "
-"identifier string."
-msgstr "<code><replaceable>service_type</replaceable></code>。<code>identity</code>、<code>compute</code>、<code>network</code>、<code>image</code>、<code>object-store</code>、他のサービス識別文字列などのサービス種別。"
+"@@image: 'figures/OpenStackTrustedComputePool2.png'; "
+"md5=077261c595464638c4b3fcc92b6afb9a"
+msgstr "@@image: 'figures/OpenStackTrustedComputePool2.png'; md5=077261c595464638c4b3fcc92b6afb9a"
 
-#: ./doc/common/section_cli_keystone_services.xml78(para)
+#: ./doc/common/section_trusted-compute-pools.xml6(title)
+msgid "Trusted compute pools"
+msgstr "信頼済コンピュートプール"
+
+#: ./doc/common/section_trusted-compute-pools.xml7(para)
 msgid ""
-"<code><replaceable>service_description</replaceable></code>. The description"
-" of the service."
-msgstr "<code><replaceable>service_description</replaceable></code>。サービスの説明。"
+"Trusted compute pools enable administrators to designate a group of compute "
+"hosts as trusted. These hosts use hardware-based security features, such as "
+"the Intel Trusted Execution Technology (TXT), to provide an additional level"
+" of security. Combined with an external stand-alone, web-based remote "
+"attestation server, cloud providers can ensure that the compute node runs "
+"only software with verified measurements and can ensure a secure cloud "
+"stack."
+msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml82(para)
+#: ./doc/common/section_trusted-compute-pools.xml13(para)
 msgid ""
-"For example, to create a <literal>swift</literal> service of type <literal"
-">object-store</literal>, run this command:"
-msgstr "例えば、<literal>object-store</literal> 種別の <literal>swift</literal> サービスを作成するために、このコマンドを実行します。"
+"Using the trusted compute pools, cloud subscribers can request services to "
+"run on verified compute nodes."
+msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml97(para)
-msgid "To get details for a service, run this command:"
-msgstr "サービスの詳細を取得するために、このコマンドを実行します。"
+#: ./doc/common/section_trusted-compute-pools.xml15(para)
+msgid "The remote attestation server performs node verification as follows:"
+msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml99(replaceable)
-msgid "service_ID"
-msgstr "service_ID"
+#: ./doc/common/section_trusted-compute-pools.xml19(para)
+msgid "Compute nodes boot with Intel TXT technology enabled."
+msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml114(title)
-msgid "Create service users"
-msgstr "サービスユーザーの作成"
+#: ./doc/common/section_trusted-compute-pools.xml23(para)
+msgid "The compute node BIOS, hypervisor, and OS are measured."
+msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml117(para)
+#: ./doc/common/section_trusted-compute-pools.xml27(para)
 msgid ""
-"Create a project for the service users. Typically, this project is named "
-"<literal>service</literal>, but choose any name you like:"
-msgstr "サービスユーザーのプロジェクトを作成します。このプロジェクトは一般的に、<literal>service</literal> という名前ですが、お好きなものを利用できます。"
+"Measured data is sent to the attestation server when challenged by the "
+"attestation server."
+msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml122(para)
-msgid "The output shows the ID for the project."
-msgstr "この出力はプロジェクトの ID を表示します。"
-
-#: ./doc/common/section_cli_keystone_services.xml123(para)
+#: ./doc/common/section_trusted-compute-pools.xml31(para)
 msgid ""
-"Make a note of this ID. You need it to create service users and assign "
-"roles."
-msgstr "この ID を記録します。サービスユーザーの作成とロールの割り当てに必要になります。"
+"The attestation server verifies those measurements against a good and known "
+"database to determine node trustworthiness."
+msgstr ""
 
-#: ./doc/common/section_cli_keystone_services.xml135(para)
-msgid "Create service users for the relevant services for your deployment."
-msgstr "お使いの環境に関連するサービス用のサービスユーザーを作成します。"
-
-#: ./doc/common/section_cli_keystone_services.xml139(para)
+#: ./doc/common/section_trusted-compute-pools.xml35(para)
 msgid ""
-"To assign the admin role to the service user-project pairs, run this command"
-" to get the ID of the admin role:"
-msgstr "サービスユーザーとプロジェクトのペアに admin ロールを割り当てるために、admin ロールの ID を取得するために、このコマンドを実行します。"
-
-#: ./doc/common/section_cli_keystone_services.xml155(para)
-msgid "Assign the admin role to the user-project pair:"
-msgstr "ユーザーとプロジェクトのペアに admin ロールを割り当てます。"
-
-#: ./doc/common/section_cli_keystone_services.xml157(replaceable)
-msgid "SERVICE_USER_ID"
-msgstr "SERVICE_USER_ID"
-
-#: ./doc/common/section_cli_keystone_services.xml157(replaceable)
-msgid "ADMIN_ROLE_ID"
-msgstr "ADMIN_ROLE_ID"
-
-#: ./doc/common/section_cli_keystone_services.xml157(replaceable)
-msgid "SERVICE_PROJECT_ID"
-msgstr "SERVICE_PROJECT_ID"
-
-#: ./doc/common/section_cli_keystone_services.xml162(title)
-msgid "Delete a service"
-msgstr "サービスの削除"
-
-#: ./doc/common/section_cli_keystone_services.xml163(para)
-msgid "To delete a specified service, specify its ID:"
-msgstr "指定したサービスを削除するために、その ID を指定します。"
-
-#: ./doc/common/section_cli_keystone_services.xml164(replaceable)
-msgid "SERVICE_ID"
-msgstr "SERVICE_ID"
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml10(title)
-msgid "Launch an instance from a volume"
-msgstr "ボリュームからのインスタンスの起動"
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml11(para)
-msgid "You can boot instances from a volume instead of an image."
+"A description of how to set up an attestation service is beyond the scope of"
+" this document. For an open source project that you can use to implement an "
+"attestation service, see the <link "
+"href=\"https://github.com/OpenAttestation/OpenAttestation\">Open "
+"Attestation</link> project."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml12(para)
+#: ./doc/common/section_trusted-compute-pools.xml54(title)
+msgid "Configure Compute to use trusted compute pools"
+msgstr ""
+
+#: ./doc/common/section_trusted-compute-pools.xml57(para)
 msgid ""
-"To complete these tasks, use these parameters on the nova <placeholder-1/> "
-"command:"
+"Enable scheduling support for trusted compute pools by adding the following "
+"lines in the <literal>DEFAULT</literal> section in the "
+"<filename>/etc/nova/nova.conf</filename> file:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml20(th)
-msgid "Task"
-msgstr "タスク"
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml21(th)
-msgid "nova boot parameter"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml22(th)
-msgid "See"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml27(td)
-msgid "Boot an instance from an image and attach a non-bootable volume."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml29(parameter)
-#: ./doc/common/section_cli_nova_boot_from_volume.xml35(parameter)
-#: ./doc/common/section_cli_nova_boot_from_volume.xml41(parameter)
-msgid "--block-device"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml33(td)
-msgid "Create a volume from an image and boot an instance from that volume."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml39(td)
-msgid "Boot from an existing source image, volume, or snapshot."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml45(td)
-msgid "Attach a swap disk to an instance."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml47(parameter)
-msgid "--swap"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml51(td)
-msgid "Attach an ephemeral disk to an instance."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml52(parameter)
-msgid "--ephemeral"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml58(para)
+#: ./doc/common/section_trusted-compute-pools.xml66(para)
 msgid ""
-"To attach a volume to a running instance, see <xref "
-"linkend=\"cli_attach_volume\"/>."
+"Specify the connection information for your attestation service by adding "
+"the following lines to the <literal>trusted_computing</literal> section in "
+"the <filename>/etc/nova/nova.conf</filename> file:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml62(title)
-msgid "Boot instance from image and attach non-bootable volume"
+#: ./doc/common/section_trusted-compute-pools.xml78(para)
+#: ./doc/common/section_cli_nova_customize_flavors.xml260(para)
+#: ./doc/common/section_keystone_config_ldap-hardening.xml83(para)
+msgid "Where:"
+msgstr "各項目:"
+
+#: ./doc/common/section_trusted-compute-pools.xml81(term)
+msgid "server"
+msgstr "サーバー"
+
+#: ./doc/common/section_trusted-compute-pools.xml83(para)
+msgid "Host name or IP address of the host that runs the attestation service."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml64(para)
+#: ./doc/common/section_trusted-compute-pools.xml88(term)
+msgid "port"
+msgstr "port"
+
+#: ./doc/common/section_trusted-compute-pools.xml90(para)
+msgid "HTTPS port for the attestation service."
+msgstr ""
+
+#: ./doc/common/section_trusted-compute-pools.xml94(term)
+msgid "server_ca_file"
+msgstr ""
+
+#: ./doc/common/section_trusted-compute-pools.xml96(para)
+msgid "Certificate file used to verify the attestation server's identity."
+msgstr ""
+
+#: ./doc/common/section_trusted-compute-pools.xml101(term)
+msgid "api_url"
+msgstr ""
+
+#: ./doc/common/section_trusted-compute-pools.xml103(para)
+msgid "The attestation service's URL path."
+msgstr ""
+
+#: ./doc/common/section_trusted-compute-pools.xml107(term)
+msgid "auth_blob"
+msgstr ""
+
+#: ./doc/common/section_trusted-compute-pools.xml109(para)
+msgid "An authentication blob, which is required by the attestation service."
+msgstr ""
+
+#: ./doc/common/section_trusted-compute-pools.xml117(para)
 msgid ""
-"Create a non-bootable volume and attach that volume to an instance that you "
-"boot from an image."
+"Restart the <systemitem class=\"service\">nova-compute</systemitem> and "
+"<systemitem class=\"service\">nova-scheduler</systemitem> services."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml66(para)
+#: ./doc/common/section_trusted-compute-pools.xml124(title)
+#: ./doc/common/section_compute_config-api.xml183(title)
+msgid "Configuration reference"
+msgstr ""
+
+#: ./doc/common/section_trusted-compute-pools.xml125(para)
 msgid ""
-"To create a non-bootable volume, do not create it from an image. The volume "
-"must be entirely empty with no partition table and no file system."
+"To customize the trusted compute pools, use the following configuration "
+"option settings:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml71(para)
-msgid "Create a non-bootable volume:"
+#: ./doc/common/section_trusted-compute-pools.xml132(title)
+msgid "Specify trusted flavors"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml98(para)
-#: ./doc/common/section_cli_cinder_manage_volumes.xml176(para)
-msgid "List volumes:"
-msgstr "ボリュームを一覧表示します。"
+#: ./doc/common/section_trusted-compute-pools.xml133(para)
+msgid "To designate hosts as trusted:"
+msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml107(para)
+#: ./doc/common/section_trusted-compute-pools.xml136(para)
 msgid ""
-"Boot an instance from an image and attach the empty volume to the instance:"
+"Configure one or more flavors as trusted by using the <placeholder-1/> "
+"command. For example, to set the <literal>m1.tiny</literal> flavor as "
+"trusted:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml149(title)
-msgid "Create volume from image and boot instance"
-msgstr "イメージからのボリュームの作成とインスタンスの起動"
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml150(para)
+#: ./doc/common/section_trusted-compute-pools.xml141(para)
 msgid ""
-"You can create a volume from an existing image, volume, or snapshot. This "
-"procedure shows you how to create a volume from an image, and use the volume"
-" to boot an instance."
+"Request that your instance be run on a trusted host, by specifying a trusted"
+" flavor when booting the instance. For example:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml155(para)
-#: ./doc/common/section_cli_nova_boot.xml121(para)
-msgid "List the available images:"
-msgstr "利用可能なイメージを表示します。"
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml165(para)
-msgid "Note the ID of the image that you want to use to create a volume."
+#: ./doc/common/section_trusted-compute-pools.xml145(title)
+msgid "Trusted compute pool"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml169(para)
-#: ./doc/common/section_cli_nova_boot.xml106(para)
-msgid "List the available flavors:"
-msgstr "利用可能なフレーバーを表示します。"
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml183(para)
-msgid "Note the ID of the flavor that you want to use to create a volume."
+#: ./doc/common/ch_cli_heat_commands.xml11(title)
+msgid "Orchestration command-line client"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml187(para)
+#: ./doc/common/ch_cli_heat_commands.xml12(para)
 msgid ""
-"To create a bootable volume from an image and launch an instance from this "
-"volume, use the <parameter>--block-device</parameter> parameter."
-msgstr "イメージから起動可能なボリュームを作成し、このボリュームからインスタンスを起動するために、<parameter>--block-device</parameter> パラメーターを使用します。"
+"The <placeholder-1/> client is the command-line interface (CLI) for the "
+"Orchestration API and its extensions. This chapter documents "
+"<placeholder-2/> version 0.2.9."
+msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
-#: ./doc/common/section_cli_nova_boot_from_volume.xml329(replaceable)
-msgid "FLAVOR"
-msgstr "FLAVOR"
+#: ./doc/common/ch_cli_heat_commands.xml22(title)
+msgid "heat usage"
+msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
-#: ./doc/common/section_cli_nova_boot_from_volume.xml205(replaceable)
-msgid "SOURCE"
-msgstr "SOURCE"
+#: ./doc/common/ch_cli_heat_commands.xml39(para)
+#: ./doc/common/ch_cli_heat_commands.xml506(para)
+msgid "Resume the stack."
+msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
-#: ./doc/common/section_cli_nova_boot_from_volume.xml217(replaceable)
-msgid "ID"
-msgstr "ID"
+#: ./doc/common/ch_cli_heat_commands.xml47(para)
+#: ./doc/common/ch_cli_heat_commands.xml523(para)
+msgid "Suspend the stack."
+msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
-#: ./doc/common/section_cli_nova_boot_from_volume.xml224(replaceable)
-msgid "DEST"
-msgstr "DEST"
+#: ./doc/common/ch_cli_heat_commands.xml55(para)
+#: ./doc/common/ch_cli_heat_commands.xml540(para)
+msgid "Retrieve build information."
+msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
-#: ./doc/common/section_cli_nova_boot_from_volume.xml233(replaceable)
-msgid "SIZE"
-msgstr "SIZE"
+#: ./doc/common/ch_cli_heat_commands.xml63(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use stack-create instead."
+msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
-msgid "PRESERVE"
-msgstr "PRESERVE"
+#: ./doc/common/ch_cli_heat_commands.xml71(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use stack-delete instead."
+msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
-#: ./doc/common/section_cli_nova_boot_from_volume.xml250(replaceable)
-msgid "INDEX"
-msgstr "INDEX"
+#: ./doc/common/ch_cli_heat_commands.xml79(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use stack-show instead."
+msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
-#: ./doc/common/section_cli_nova_boot_from_volume.xml329(replaceable)
-msgid "NAME"
-msgstr "NAME"
+#: ./doc/common/ch_cli_heat_commands.xml87(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use event-show instead."
+msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml192(para)
-msgid "The parameters are:"
-msgstr "パラメーターは以下のとおりです。"
+#: ./doc/common/ch_cli_heat_commands.xml95(para)
+#: ./doc/common/ch_cli_heat_commands.xml547(para)
+msgid "List events for a stack."
+msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml195(para)
+#: ./doc/common/ch_cli_heat_commands.xml103(para)
+#: ./doc/common/ch_cli_heat_commands.xml575(para)
+msgid "Describe the event."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml111(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use template-show instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml119(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use stack-list instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml127(para)
+#: ./doc/common/ch_cli_heat_commands.xml608(para)
+msgid "Show available outputs."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml135(para)
+#: ./doc/common/ch_cli_heat_commands.xml625(para)
+msgid "Show a specific stack output."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml143(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use resource-show instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml151(para)
+#: ./doc/common/ch_cli_heat_commands.xml650(para)
+msgid "Show list of resources belonging to a stack."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml159(para)
+#: ./doc/common/ch_cli_heat_commands.xml667(para)
+msgid "List resource metadata."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml167(para)
+#: ./doc/common/ch_cli_heat_commands.xml692(para)
+msgid "Describe the resource."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml175(para)
+#: ./doc/common/ch_cli_heat_commands.xml717(para)
+msgid "Send a signal to a resource."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml183(para)
+#: ./doc/common/ch_cli_heat_commands.xml762(para)
+msgid "Generate a template based on a resource."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml191(para)
+#: ./doc/common/ch_cli_heat_commands.xml790(para)
+msgid "List the available resource types."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml199(para)
+#: ./doc/common/ch_cli_heat_commands.xml797(para)
+msgid "Show the resource type."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml207(para)
+#: ./doc/common/ch_cli_heat_commands.xml814(para)
+msgid "Abandon the stack."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml215(para)
+#: ./doc/common/ch_cli_heat_commands.xml834(para)
+msgid "Adopt a stack."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml223(para)
+#: ./doc/common/ch_cli_heat_commands.xml932(para)
+msgid "Create the stack."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml231(para)
+#: ./doc/common/ch_cli_heat_commands.xml1019(para)
+msgid "Delete the stack(s)."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml239(para)
+#: ./doc/common/ch_cli_heat_commands.xml1037(para)
+msgid "List the user's stacks."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml247(para)
+#: ./doc/common/ch_cli_heat_commands.xml1076(para)
+msgid "Preview the stack."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml255(para)
+#: ./doc/common/ch_cli_heat_commands.xml1154(para)
+msgid "Describe the stack."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml263(para)
+#: ./doc/common/ch_cli_heat_commands.xml1173(para)
+msgid "Update the stack."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml271(para)
+#: ./doc/common/ch_cli_heat_commands.xml1243(para)
+msgid "Get the template for the specified stack."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml279(para)
+#: ./doc/common/ch_cli_heat_commands.xml1261(para)
+msgid "Validate a template with parameters."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml287(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use stack-update instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml295(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use template-validate instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml303(para)
+#: ./doc/common/ch_cli_keystone_commands.xml324(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml253(para)
+msgid "Prints all of the commands and options to stdout."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml320(title)
+msgid "heat optional arguments"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml325(para)
+#: ./doc/common/ch_cli_keystone_commands.xml346(para)
+msgid "Shows the client version and exits."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml333(para)
+msgid "Defaults to <code>env[HEATCLIENT_DEBUG]</code>."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml341(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml291(para)
+msgid "Print more verbose output."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml349(para)
 msgid ""
-"<parameter>--flavor</parameter><replaceable>FLAVOR</replaceable>. The flavor"
-" ID or name."
+"Explicitly allow the client to perform \"insecure\" SSL (https) requests. "
+"The server's certificate will not be verified against any certificate "
+"authorities. This option should be used with caution."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml200(para)
+#: ./doc/common/ch_cli_heat_commands.xml360(para)
+#: ./doc/common/ch_cli_glance_commands.xml262(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml311(para)
 msgid ""
-"<parameter>--block-device</parameter> "
-"source=<replaceable>SOURCE</replaceable>,id=<replaceable>ID</replaceable>,dest=<replaceable>DEST</replaceable>,size=<replaceable>SIZE</replaceable>,shutdown=<replaceable>PRESERVE</replaceable>,bootindex=<replaceable>INDEX</replaceable>"
-msgstr "<parameter>--block-device</parameter> source=<replaceable>SOURCE</replaceable>,id=<replaceable>ID</replaceable>,dest=<replaceable>DEST</replaceable>,size=<replaceable>SIZE</replaceable>,shutdown=<replaceable>PRESERVE</replaceable>,bootindex=<replaceable>INDEX</replaceable>"
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml205(emphasis)
-msgid "source=<placeholder-1/>"
+"Path of certificate file to use in SSL connection. This file can optionally "
+"be prepended with the private key."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml207(para)
+#: ./doc/common/ch_cli_heat_commands.xml370(para)
 msgid ""
-"The type of object used to create the block device. Valid values are "
-"<literal>volume</literal>, <literal>snapshot</literal>, "
-"<literal>image</literal>, and <literal>blank</literal>."
+"Path of client key to use in SSL connection.This option is not necessary if "
+"your key is prepended to your cert file."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml217(emphasis)
-msgid "id=<placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml219(para)
-msgid "The ID of the source object."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml224(emphasis)
-msgid "dest=<placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml226(para)
+#: ./doc/common/ch_cli_heat_commands.xml380(para)
 msgid ""
-"The type of the target virtual device. Valid values are "
-"<literal>volume</literal> and <literal>local</literal>."
+"Path of CA SSL certificate(s) used to verify the remote server's "
+"certificate. Without this option the client looks for the default system CA "
+"certificates."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml233(emphasis)
-msgid "size=<placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml235(para)
-msgid "The size of the volume that is created."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml240(emphasis)
-msgid "shutdown={preserve|remove}"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml242(para)
+#: ./doc/common/ch_cli_heat_commands.xml390(para)
 msgid ""
-"What to do with the volume when the instance is deleted. "
-"<literal>preserve</literal> does not delete the volume. "
-"<literal>remove</literal> deletes the volume."
+"Number of seconds to wait for an API response, defaults to system socket "
+"timeout"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml250(emphasis)
-msgid "bootindex=<placeholder-1/>"
+#: ./doc/common/ch_cli_heat_commands.xml447(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml405(para)
+msgid "Defaults to <code>env[OS_AUTH_TOKEN]</code>."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml252(para)
+#: ./doc/common/ch_cli_heat_commands.xml455(para)
 msgid ""
-"Orders the boot disks. Use <literal>0</literal> to boot from this volume."
+"Do not contact keystone for a token. Defaults to "
+"<code>env[OS_NO_CLIENT_AUTH]</code>."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml260(para)
-msgid "<replaceable>NAME</replaceable>. The name for the server."
+#: ./doc/common/ch_cli_heat_commands.xml464(para)
+msgid "Defaults to <code>env[HEAT_URL]</code>."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml266(para)
-msgid ""
-"Create a bootable volume from an image, before the instance boots. The "
-"volume is not deleted when the instance is terminated:"
-msgstr "インスタンスの起動前に、起動可能なボリュームをイメージから作成します。このボリュームはインスタンスの終了時に削除されません。"
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml307(para)
-msgid ""
-"List volumes to see the bootable volume and its attached "
-"<literal>myInstanceFromVolume</literal> instance:"
-msgstr "起動可能なボリュームと接続された <literal>myInstanceFromVolume</literal> インスタンスを参照するためにボリュームを一覧表示します。"
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml320(title)
-msgid "Attach swap or ephemeral disk to an instance"
-msgstr "インスタンスへのスワップや一時ディスクの接続"
-
-#: ./doc/common/section_cli_nova_boot_from_volume.xml321(para)
-msgid ""
-"Use the nova <placeholder-1/><parameter>--swap</parameter> parameter to "
-"attach a swap disk on boot or the nova "
-"<placeholder-2/><parameter>--ephemeral</parameter> parameter to attach an "
-"ephemeral disk on boot. When you terminate the instance, both disks are "
-"deleted."
+#: ./doc/common/ch_cli_heat_commands.xml472(para)
+msgid "Defaults to <code>env[HEAT_API_VERSION]</code> or 1."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml327(para)
-msgid "Boot an instance with a 512MB swap disk and 2GB ephemeral disk:"
+#: ./doc/common/ch_cli_heat_commands.xml480(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml429(para)
+msgid "Defaults to <code>env[OS_SERVICE_TYPE]</code>."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml329(replaceable)
-#: ./doc/common/section_cli_nova_boot.xml186(replaceable)
-msgid "IMAGE_ID"
-msgstr "IMAGE_ID"
+#: ./doc/common/ch_cli_heat_commands.xml488(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml437(para)
+msgid "Defaults to <code>env[OS_ENDPOINT_TYPE]</code>."
+msgstr ""
 
-#: ./doc/common/section_cli_nova_boot_from_volume.xml331(para)
+#: ./doc/common/ch_cli_heat_commands.xml496(para)
+msgid "Send os-username and os-password to heat."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml504(title)
+msgid "heat action-resume command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml513(para)
+msgid "Name or ID of stack to resume."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml521(title)
+msgid "heat action-suspend command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml530(para)
+msgid "Name or ID of stack to suspend."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml538(title)
+msgid "heat build-info command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml545(title)
+msgid "heat event-list command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml554(para)
+#: ./doc/common/ch_cli_heat_commands.xml582(para)
+msgid "Name or ID of stack to show the events for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml565(para)
+msgid "Name of the resource to filter events by."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml573(title)
+msgid "heat event-show command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml590(para)
+msgid "Name of the resource the event belongs to."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml598(para)
+msgid "ID of event to display details for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml606(title)
+msgid "heat output-list command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml615(para)
+#: ./doc/common/ch_cli_heat_commands.xml632(para)
+msgid "Name or ID of stack to query."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml623(title)
+msgid "heat output-show command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml640(para)
+msgid "Name of an output to display."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml648(title)
+msgid "heat resource-list command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml657(para)
+msgid "Name or ID of stack to show the resources for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml665(title)
+msgid "heat resource-metadata command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml674(para)
+msgid "Name or ID of stack to show the resource metadata for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml682(para)
+msgid "Name of the resource to show the metadata for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml690(title)
+msgid "heat resource-show command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml699(para)
+msgid "Name or ID of stack to show the resource for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml707(para)
+msgid "Name of the resource to show the details for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml715(title)
+msgid "heat resource-signal command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml724(para)
+msgid "Name or ID of stack the resource belongs to."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml732(para)
+msgid "Name of the resource to signal."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml743(para)
+msgid "JSON Data to send to the signal handler."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml751(para)
+msgid "File containing JSON data to send to the signal handler."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml760(title)
+msgid "heat resource-template command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml769(para)
+msgid "Name of the resource to generate a template for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml780(para)
+msgid "The template output format, one of: yaml, json."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml788(title)
+msgid "heat resource-type-list command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml795(title)
+msgid "heat resource-type-show command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml804(para)
+msgid "Resource type to get the details for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml812(title)
+msgid "heat stack-abandon command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml821(para)
+msgid "Name or ID of stack to abandon."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml829(title)
+msgid "heat stack-adopt command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml841(para)
+msgid "Name of the stack to adopt."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml852(para)
+#: ./doc/common/ch_cli_heat_commands.xml950(para)
+#: ./doc/common/ch_cli_heat_commands.xml1094(para)
+#: ./doc/common/ch_cli_heat_commands.xml1191(para)
+#: ./doc/common/ch_cli_heat_commands.xml1276(para)
+msgid "Path to the template."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml860(para)
+#: ./doc/common/ch_cli_heat_commands.xml958(para)
+#: ./doc/common/ch_cli_heat_commands.xml1102(para)
+#: ./doc/common/ch_cli_heat_commands.xml1199(para)
+#: ./doc/common/ch_cli_heat_commands.xml1284(para)
+msgid "Path to the environment."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml868(para)
+#: ./doc/common/ch_cli_heat_commands.xml966(para)
+#: ./doc/common/ch_cli_heat_commands.xml1110(para)
+#: ./doc/common/ch_cli_heat_commands.xml1207(para)
+#: ./doc/common/ch_cli_heat_commands.xml1268(para)
+msgid "URL of template."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml876(para)
+msgid "URL to retrieve template object (e.g from swift)."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml884(para)
+#: ./doc/common/ch_cli_heat_commands.xml982(para)
 msgid ""
-"The flavor defines the maximum swap and ephemeral disk size. You cannot "
-"exceed these maximum values."
-msgstr "フレーバーが最大スワップと一時ディスクの容量を定義します。これらの最大値を超過できません。"
+"Stack creation timeout in minutes. <emphasis>DEPRECATED</emphasis> use "
+"--timeout instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml893(para)
+#: ./doc/common/ch_cli_heat_commands.xml991(para)
+msgid "Stack creation timeout in minutes."
+msgstr "スタック作成のタイムアウト時間（分単位）。"
+
+#: ./doc/common/ch_cli_heat_commands.xml901(para)
+msgid "Path to adopt stack data file."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml909(para)
+#: ./doc/common/ch_cli_heat_commands.xml999(para)
+msgid "Enable rollback on create/update failure."
+msgstr "作成/更新失敗時のロールバックを有効にします。"
+
+#: ./doc/common/ch_cli_heat_commands.xml917(para)
+#: ./doc/common/ch_cli_heat_commands.xml1007(para)
+#: ./doc/common/ch_cli_heat_commands.xml1231(para)
+msgid ""
+"Parameter values used to create the stack. This can be specified multiple "
+"times, or once with parameters separated by a semicolon."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml927(title)
+msgid "heat stack-create command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml939(para)
+msgid "Name of the stack to create."
+msgstr "作成するスタックの名前。"
+
+#: ./doc/common/ch_cli_heat_commands.xml974(para)
+#: ./doc/common/ch_cli_heat_commands.xml1215(para)
+#: ./doc/common/ch_cli_heat_commands.xml1292(para)
+msgid "URL to retrieve template object (e.g. from swift)."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1017(title)
+msgid "heat stack-delete command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1026(para)
+msgid "Name or ID of stack(s) to delete."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1034(title)
+msgid "heat stack-list command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1044(para)
+msgid ""
+"Filter parameters to apply on returned stacks. This can be specified "
+"multiple times, or once with parameters separated by a semicolon."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1054(para)
+msgid "Limit the number of stacks returned."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1062(para)
+msgid "Only return stacks that appear after the given stack ID."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1071(title)
+msgid "heat stack-preview command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1083(para)
+msgid "Name of the stack to preview."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1118(para)
+msgid "URL to retrieve template object (e.g from swift)"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1126(para)
+msgid "Stack timeout in minutes. Default: 60"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1134(para)
+msgid "Enable rollback on failure"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1142(para)
+msgid ""
+"Parameter values used to preview the stack. This can be specified multiple "
+"times, or once with parameters separated by semicolon."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1152(title)
+msgid "heat stack-show command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1161(para)
+msgid "Name or ID of stack to describe."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1169(title)
+msgid "heat stack-update command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1180(para)
+msgid "Name or ID of stack to update."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1223(para)
+msgid "Stack update timeout in minutes."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1241(title)
+msgid "heat template-show command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1250(para)
+msgid "Name or ID of stack to get the template for."
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1258(title)
+msgid "heat template-validate command"
+msgstr ""
+
+#: ./doc/common/ch_cli_heat_commands.xml1300(para)
+msgid ""
+"Parameter values to validate. This can be specified multiple times, or once "
+"with parameters separated by a semicolon."
+msgstr ""
 
 #: ./doc/common/section_cli_nova_images.xml6(title)
 msgid "Manage images with the nova client"
@@ -10331,6 +9238,11 @@ msgstr "ボリュームを接続したインスタンスからスナップショ
 msgid "To create an image"
 msgstr ""
 
+#: ./doc/common/section_cli_nova_images.xml18(para)
+#: ./doc/common/section_cli_nova_manage_images.xml17(para)
+msgid "Write any buffered data to disk."
+msgstr "バッファーデータをディスクに書き込みます。"
+
 #: ./doc/common/section_cli_nova_images.xml19(para)
 msgid ""
 "For more information, see the <link href=\"http://docs.openstack.org/trunk"
@@ -10350,10 +9262,23 @@ msgid ""
 "repository. Only the tenant that creates the image has access to it."
 msgstr "この例では、サーバーの名前は <literal>myCirrosServer</literal> となっています。このサーバーを使用して、以下のようにスナップショットを作成します。<placeholder-1/> このコマンドは、qemu スナップショットを作成して、お使いのリポジトリにイメージを自動的にアップロードします。イメージを作成したテナントのみ、そのイメージにアクセスすることができます。"
 
+#: ./doc/common/section_cli_nova_images.xml43(para)
+#: ./doc/common/section_cli_nova_manage_images.xml40(para)
+msgid "Get details for your image to check its status:"
+msgstr "イメージの詳細を取得して状態を確認します。"
+
 #: ./doc/common/section_cli_nova_images.xml45(replaceable)
 msgid "IMAGE"
 msgstr "IMAGE"
 
+#: ./doc/common/section_cli_nova_images.xml79(para)
+#: ./doc/common/section_cli_nova_manage_images.xml75(para)
+msgid ""
+"The image status changes from <literal>SAVING</literal> to "
+"<literal>ACTIVE</literal>. Only the tenant who creates the image has access "
+"to it."
+msgstr "イメージの状態は <literal>SAVING</literal> から <literal>ACTIVE</literal> に変わります。イメージを作成したテナントのみがこのイメージにアクセスできます。"
+
 #: ./doc/common/section_cli_nova_images.xml86(title)
 msgid "To launch an instance from your image"
 msgstr ""
@@ -10364,6 +9289,11 @@ msgid ""
 "as follows:"
 msgstr "イメージからインスタンスを起動するには、以下のようにイメージ ID とフレーバー ID を含めます。"
 
+#: ./doc/common/section_cli_nova_images.xml125(title)
+#: ./doc/common/section_cli_glance_manage_images.xml410(title)
+msgid "Troubleshoot image creation"
+msgstr "イメージ作成のトラブルシューティング"
+
 #: ./doc/common/section_cli_nova_images.xml133(para)
 msgid ""
 "Make sure the version of qemu you are using is version 0.14 or greater. "
@@ -10371,601 +9301,1658 @@ msgid ""
 " error message in the <filename>nova-compute.log</filename>."
 msgstr "QEMU のバージョン 0.14 以降を使用していることを確認します。古いバージョンの QEMU を使用していると、<filename>nova-compute.log</filename> に \"<literal>unknown option -s</literal>\" エラーメッセージが記録されます。"
 
-#: ./doc/common/section_keystone-external-auth.xml7(title)
-msgid "External authentication with Identity"
-msgstr ""
-
-#: ./doc/common/section_keystone-external-auth.xml8(para)
+#: ./doc/common/section_cli_nova_images.xml140(para)
+#: ./doc/common/section_cli_glance_manage_images.xml420(para)
 msgid ""
-"When Identity runs in <literal>apache-httpd</literal>, you can use external "
-"authentication methods that differ from the authentication provided by the "
-"identity store back end. For example, you can use an SQL identity back end "
-"together with X.509 authentication, Kerberos, and so on instead of using the"
-" user name and password combination."
-msgstr ""
+"Examine the <filename>/var/log/nova-api.log</filename> and "
+"<filename>/var/log/nova-compute.log</filename> log files for error messages."
+msgstr "エラーメッセージは <filename>/var/log/nova-api.log</filename> と <filename>/var/log/nova-compute.log</filename> ログファイルを確認します。"
 
-#: ./doc/common/section_keystone-external-auth.xml15(title)
-msgid "Use HTTPD authentication"
-msgstr ""
+#: ./doc/common/section_dochistory.xml6(title)
+msgid "Document change history"
+msgstr "ドキュメント変更履歴"
 
-#: ./doc/common/section_keystone-external-auth.xml16(para)
+#: ./doc/common/section_dochistory.xml8(para)
 msgid ""
-"Web servers, like Apache HTTP, support many methods of authentication. "
-"Identity can allow the web server to perform the authentication. The web "
-"server then passes the authenticated user to Identity by using the "
-"<literal>REMOTE_USER</literal> environment variable. This user must already "
-"exist in the Identity back end to get a token from the controller. To use "
-"this method, Identity should run on <literal>apache-httpd</literal>."
+"This version of the guide replaces and obsoletes all previous versions. The "
+"following table describes the most recent changes:"
+msgstr "このバージョンのガイドはすべての旧バージョンを置き換え、廃止します。以下の表はもっとも最近の変更点を記載しています。"
+
+#: ./doc/common/ch_cli_swift_commands.xml11(title)
+msgid "Object Storage command-line client"
 msgstr ""
 
-#: ./doc/common/section_keystone-external-auth.xml27(title)
-msgid "Use X.509"
-msgstr ""
-
-#: ./doc/common/section_keystone-external-auth.xml28(para)
+#: ./doc/common/ch_cli_swift_commands.xml12(para)
 msgid ""
-"The following Apache configuration snippet authenticates the user based on a"
-" valid X.509 certificate from a known CA:"
+"The <placeholder-1/> client is the command-line interface (CLI) for the "
+"OpenStack Object Storage API and its extensions. This chapter documents "
+"<placeholder-2/> version 2.1.0."
 msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml5(title)
-msgid "Orchestration module"
+#: ./doc/common/ch_cli_swift_commands.xml22(title)
+msgid "swift usage"
 msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml6(para)
+#: ./doc/common/ch_cli_swift_commands.xml41(para)
+#: ./doc/common/ch_cli_swift_commands.xml335(para)
+msgid "Delete a container or objects within a container."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml49(para)
+#: ./doc/common/ch_cli_swift_commands.xml399(para)
+msgid "Download objects from containers."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml57(para)
+#: ./doc/common/ch_cli_swift_commands.xml513(para)
+msgid "Lists the containers for the account or the objects for a container."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml66(para)
 msgid ""
-"The Orchestration module provides a template-based orchestration for "
-"describing a cloud application, by running OpenStack API calls to generate "
-"running cloud applications. The software integrates other core components of"
-" OpenStack into a one-file template system. The templates allow you to "
-"create most OpenStack resource types, such as instances, floating IPs, "
-"volumes, security groups and users. It also provides advanced functionality,"
-" such as instance high availability, instance auto-scaling, and nested "
-"stacks. This enables OpenStack core projects to receive a larger user base."
+"Updates meta information for the account, container, or object; creates "
+"containers if not present."
 msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml16(para)
+#: ./doc/common/ch_cli_swift_commands.xml75(para)
+#: ./doc/common/ch_cli_swift_commands.xml661(para)
+msgid "Displays information for the account, container, or object."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml84(para)
+msgid "Uploads files or directories to the given container."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml92(para)
+msgid "List cluster capabilities."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml100(title)
+msgid "swift examples"
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml110(title)
+msgid "swift optional arguments"
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml131(para)
+msgid "Use SERVICENET internal network."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml139(para)
+msgid "Print more info."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml147(para)
 msgid ""
-"The service enables deployers to integrate with the Orchestration module "
-"directly or through custom plug-ins."
+"Show the curl commands and results of all http queries regardless of result "
+"status."
 msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml18(para)
-msgid "The Orchestration module consists of the following components:"
-msgstr ""
-
-#: ./doc/common/section_getstart_orchestration.xml22(term)
-msgid "<code>heat</code> command-line client"
-msgstr ""
-
-#: ./doc/common/section_getstart_orchestration.xml23(para)
+#: ./doc/common/ch_cli_swift_commands.xml156(para)
 msgid ""
-"A CLI that communicates with the heat-api to run AWS CloudFormation APIs. "
-"End developers can directly use the Orchestration REST API."
+"Show the curl commands and results of all http queries which return an "
+"error."
 msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml28(term)
-msgid "<code>heat-api</code> component"
+#: ./doc/common/ch_cli_swift_commands.xml165(para)
+msgid "Suppress status output."
 msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml28(para)
+#: ./doc/common/ch_cli_swift_commands.xml173(para)
+msgid "for obtaining an auth token."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml181(para)
+msgid "Specify a version for authentication. Defaults to 1.0."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml189(para)
+msgid "User name for obtaining an auth token."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml197(para)
+msgid "Key for obtaining an auth token."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml205(para)
+msgid "The number of times to retry a failed connection."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml213(para)
+msgid "OpenStack username. Defaults to <code>env[OS_USERNAME]</code>."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml221(para)
+msgid "OpenStack password. Defaults to <code>env[OS_PASSWORD]</code>."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml229(para)
+msgid "OpenStack tenant ID. Defaults to <code>env[OS_TENANT_ID]</code>."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml237(para)
+msgid "OpenStack tenant name. Defaults to <code>env[OS_TENANT_NAME]</code>."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml246(para)
+msgid "OpenStack auth URL. Defaults to <code>env[OS_AUTH_URL]</code>."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml254(para)
 msgid ""
-"An OpenStack-native REST API that processes API requests by sending them to "
-"the heat-engine over Remote Procedure Call (RPC)."
+"OpenStack token. Defaults to <code>env[OS_AUTH_TOKEN]</code>. Used with "
+"--os-storage-url to bypass the usual username/password authentication."
 msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml34(term)
-msgid "<code>heat-api-cfn</code> component"
-msgstr ""
-
-#: ./doc/common/section_getstart_orchestration.xml34(para)
+#: ./doc/common/ch_cli_swift_commands.xml264(para)
 msgid ""
-"An AWS Query API that is compatible with AWS CloudFormation. It processes "
-"API requests by sending them to the heat-engine over RPC."
+"OpenStack storage URL. Defaults to <code>env[OS_STORAGE_URL]</code>. "
+"Overrides the storage url returned during auth. Will bypass authentication "
+"when used with --os-auth-token."
 msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml40(code)
-msgid "heat-engine"
-msgstr "heat-engine"
+#: ./doc/common/ch_cli_swift_commands.xml275(para)
+msgid "OpenStack region name. Defaults to <code>env[OS_REGION_NAME]</code>."
+msgstr ""
 
-#: ./doc/common/section_getstart_orchestration.xml41(para)
+#: ./doc/common/ch_cli_swift_commands.xml284(para)
+msgid "OpenStack Service type. Defaults to <code>env[OS_SERVICE_TYPE]</code>."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml293(para)
 msgid ""
-"Orchestrates the launching of templates and provides events back to the API "
-"consumer."
+"OpenStack Endpoint type. Defaults to <code>env[OS_ENDPOINT_TYPE]</code>."
 msgstr ""
 
-#: ./doc/common/section_getstart_networking.xml5(title)
-msgid "OpenStack Networking"
-msgstr "OpenStack Networking"
-
-#: ./doc/common/section_getstart_networking.xml6(para)
+#: ./doc/common/ch_cli_swift_commands.xml302(para)
+#: ./doc/common/ch_cli_keystone_commands.xml445(para)
+#: ./doc/common/ch_cli_trove_commands.xml558(para)
 msgid ""
-"OpenStack Networking allows you to create and attach interface devices "
-"managed by other OpenStack services to networks. Plug-ins can be implemented"
-" to accomodate different networking equipment and software, providing "
-"flexibility to OpenStack architecture and deployment."
+"Specify a CA bundle file to use in verifying a TLS (https) server "
+"certificate. Defaults to <code>env[OS_CACERT]</code>."
 msgstr ""
 
-#: ./doc/common/section_getstart_networking.xml11(para)
-#: ./doc/common/section_getstart_object-storage.xml9(para)
-msgid "It includes the following components:"
-msgstr "以下のコンポーネントを含みます。"
-
-#: ./doc/common/section_getstart_networking.xml14(systemitem)
-msgid "neutron-server"
-msgstr "neutron-server"
-
-#: ./doc/common/section_getstart_networking.xml15(para)
+#: ./doc/common/ch_cli_swift_commands.xml312(para)
 msgid ""
-"Accepts and routes API requests to the appropriate OpenStack Networking "
-"plug-in for action."
+"Allow swiftclient to access servers without having to verify the SSL "
+"certificate. Defaults to <code>env[SWIFTCLIENT_INSECURE]</code> (set to "
+"'true' to enable)."
 msgstr ""
 
-#: ./doc/common/section_getstart_networking.xml19(term)
-msgid "OpenStack Networking plug-ins and agents"
-msgstr ""
-
-#: ./doc/common/section_getstart_networking.xml20(para)
+#: ./doc/common/ch_cli_swift_commands.xml322(para)
 msgid ""
-"Plugs and unplugs ports, creates networks or subnets, and provides IP "
-"addressing. These plug-ins and agents differ depending on the vendor and "
-"technologies used in the particular cloud. OpenStack Networking ships with "
-"plug-ins and agents for Cisco virtual and physical switches, NEC OpenFlow "
-"products, Open vSwitch, Linux bridging, Ryu Network Operating System, and "
-"the VMware NSX product."
+"This option is deprecated and not used anymore. SSL compression should be "
+"disabled by default by the system SSL library."
 msgstr ""
 
-#: ./doc/common/section_getstart_networking.xml27(para)
+#: ./doc/common/ch_cli_swift_commands.xml332(title)
+msgid "swift delete command"
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml342(para)
+msgid "Name of container to delete from."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml350(para)
+msgid "Name of object to delete. Specify multiple times for multiple objects."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml362(para)
+msgid "Delete all containers and objects."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml370(para)
+msgid "Do not delete segments of manifest objects."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml378(para)
+msgid "Number of threads to use for deleting objects. Default is 10."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml387(para)
+msgid "Number of threads to use for deleting containers. Default is 10."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml396(title)
+msgid "swift download command"
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml406(para)
 msgid ""
-"The common agents are L3 (layer 3), DHCP (dynamic host IP addressing), and a"
-" plug-in agent."
+"Name of container to download from. To download a whole account, omit this "
+"and specify --all."
 msgstr ""
 
-#: ./doc/common/section_getstart_networking.xml31(term)
-#: ./doc/common/section_getstart_block-storage.xml35(term)
-msgid "Messaging queue"
-msgstr ""
-
-#: ./doc/common/section_getstart_networking.xml32(para)
+#: ./doc/common/ch_cli_swift_commands.xml415(para)
 msgid ""
-"Used by most OpenStack Networking installations to route information between"
-" the neutron-server and various agents, as well as a database to store "
-"networking state for particular plug-ins."
+"Name of object to download. Specify multiple times for multiple objects. "
+"Omit this to download all objects from the container."
 msgstr ""
 
-#: ./doc/common/section_getstart_networking.xml38(para)
+#: ./doc/common/ch_cli_swift_commands.xml428(para)
+msgid "Indicates that you really want to download everything in the account."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml437(para)
+msgid "Marker to use when starting a container or account download."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml446(para)
+msgid "Only download items beginning with &lt;prefix&gt;."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml454(para)
 msgid ""
-"OpenStack Networking mainly interacts with OpenStack Compute to provide "
-"networks and connectivity for its instances."
+"For a single file download, stream the output to &lt;out_file&gt;. "
+"Specifying \"-\" as &lt;out_file&gt; will redirect to stdout."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml6(title)
-msgid "Configure instances at boot"
+#: ./doc/common/ch_cli_swift_commands.xml464(para)
+msgid "Number of threads to use for downloading objects. Default is 10"
 msgstr ""
 
-#: ./doc/common/section_user-data.xml7(para)
+#: ./doc/common/ch_cli_swift_commands.xml473(para)
+msgid "Number of threads to use for downloading containers. Default is 10"
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml482(para)
+msgid "Perform download(s), but don't actually write anything to disk."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml491(para)
 msgid ""
-"When you boot instances in an OpenStack cloud, you can use user data or "
-"<package>cloud-init</package> to automatically configure instances at boot "
-"time. You might want to install some packages, start services, or manage "
-"your instance by using a Puppet or Chef server."
+"Adds a customized request header to the query, like \"Range\" or \"If-"
+"Match\". This argument is repeatable. Example --header \"content-"
+"type:text/plain\""
 msgstr ""
 
-#: ./doc/common/section_user-data.xml13(title)
-msgid "User data"
-msgstr "ユーザーデータ"
+#: ./doc/common/ch_cli_swift_commands.xml501(para)
+msgid "Skip downloading files that are identical on both sides."
+msgstr ""
 
-#: ./doc/common/section_user-data.xml14(para)
+#: ./doc/common/ch_cli_swift_commands.xml510(title)
+msgid "swift list command"
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml520(para)
+msgid "Name of container to list object in."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml531(para)
+msgid "Long listing format, similar to ls -l."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml539(para)
+#: ./doc/common/ch_cli_swift_commands.xml688(para)
+msgid "Report sizes in human readable format similar to ls -lh."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml548(para)
+msgid "Used with -l or --lh, only report totals."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml556(para)
+msgid "Only list items beginning with the prefix."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml564(para)
 msgid ""
-"User data is the mechanism by which a user can pass information contained in"
-" a local file to an instance at launch time. The typical use case is to pass"
-" something like a shell script or a configuration file as user data."
+"Roll up items with the given delimiter. For containers only. See OpenStack "
+"Swift API documentation for what this means."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml19(para)
+#: ./doc/common/ch_cli_swift_commands.xml574(title)
+msgid "swift post command"
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml577(para)
 msgid ""
-"User data is sent using the <literal>--user-data "
-"<replaceable>/path/to/filename</replaceable></literal> option when calling "
-"<placeholder-1/>. This example creates a text file and sends its contents as"
-" user data to the instance:"
+"Updates meta information for the account, container, or object. If the "
+"container is not found, it will be created automatically."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml26(para)
+#: ./doc/common/ch_cli_swift_commands.xml585(para)
+msgid "Name of container to post to."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml593(para)
+msgid "Name of object to post. Specify multiple times for multiple objects."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml605(para)
 msgid ""
-"The instance can get user data by querying the metadata service through "
-"either the OpenStack metadata API or the EC2 compatibility API:"
+"Read ACL for containers. Quick summary of ACL syntax: .r:*, "
+".r:-.example.com, .r:www.example.com, account1, account2:user2"
 msgstr ""
 
-#: ./doc/common/section_user-data.xml34(para)
+#: ./doc/common/ch_cli_swift_commands.xml615(para)
 msgid ""
-"The Compute service treats user data as a blob. While the previous example "
-"uses a text file, user data can be in any format."
+"Write ACL for containers. Quick summary of ACL syntax: account1 "
+"account2:user2"
 msgstr ""
 
-#: ./doc/common/section_user-data.xml38(para)
-msgid "For more information, see <xref linkend=\"config-drive\"/>."
+#: ./doc/common/ch_cli_swift_commands.xml624(para)
+msgid "Sync To for containers, for multi-cluster replication."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml42(package)
-msgid "cloud-init"
-msgstr "cloud-init"
+#: ./doc/common/ch_cli_swift_commands.xml632(para)
+msgid "Sync Key for containers, for multi-cluster replication."
+msgstr ""
 
-#: ./doc/common/section_user-data.xml43(para)
+#: ./doc/common/ch_cli_swift_commands.xml640(para)
 msgid ""
-"To do something useful with the user data, you must configure the virtual "
-"machine image to run a service on boot that gets user data from the metadata"
-" service and takes some action based on the contents of the data. The "
-"<package>cloud-init</package> package does exactly this. This package is "
-"compatible with the Compute metadata service and the Compute configuration "
-"drive."
+"Sets a meta data item. This option may be repeated. Example: -m Color:Blue "
+"-m Size:Large"
 msgstr ""
 
-#: ./doc/common/section_user-data.xml51(para)
+#: ./doc/common/ch_cli_swift_commands.xml649(para)
 msgid ""
-"The <package>cloud-init</package> package supports multiple cloud providers."
-" You can use the same virtual machine image in different clouds without "
-"modification. The <package>cloud-init</package> package is an open source "
-"project and the source code is available on <link "
-"href=\"http://launchpad.net/cloud-init\">Launchpad</link>. It is maintained "
-"by Canonical, the company that runs the Ubuntu project. All Ubuntu cloud "
-"images come pre-installed with <package>cloud-init</package>. However, "
-"<package>cloud-init</package> is not designed to be Ubuntu-specific and has "
-"been successfully ported to several other platforms including Fedora."
+"Set request headers. This option may be repeated. Example -H \"content-"
+"type:text/plain\""
 msgstr ""
 
-#: ./doc/common/section_user-data.xml66(para)
+#: ./doc/common/ch_cli_swift_commands.xml658(title)
+msgid "swift stat command"
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml668(para)
+msgid "Name of container to stat from."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml676(para)
+msgid "Name of object to stat. Specify multiple times for multiple objects."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml697(title)
+msgid "swift upload command"
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml700(para)
+msgid "Uploads specified files and directories to the given container."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml707(para)
+msgid "Name of container to upload to."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml715(para)
 msgid ""
-"Even if you do not use user data to configure instance behavior at boot "
-"time, install <package>cloud-init</package> on images that you create "
-"because this package provides useful functionality. For example, the "
-"<package>cloud-init</package> package enables you to copy the public key to "
-"an account (the <literal>ubuntu</literal> account by default on Ubuntu "
-"instances, the <literal>ec2-user</literal> by default in Fedora instances)."
+"Name of file or directory to upload. Specify multiple times for multiple "
+"uploads."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml75(para)
+#: ./doc/common/ch_cli_swift_commands.xml727(para)
+msgid "Only upload files that have changed since the last upload."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml736(para)
+msgid "Skip uploading files that are identical on both sides."
+msgstr ""
+
+#: ./doc/common/ch_cli_swift_commands.xml744(para)
 msgid ""
-"If you do not have <package>cloud-init</package> installed, you must "
-"manually configure your image to get the public key from the metadata "
-"service on boot and copy it to the appropriate account."
+"Upload files in segments no larger than &lt;size&gt; (in Bytes) and then "
+"create a \"manifest\" file that will download all the segments as if it were"
+" the original file."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml81(title)
-msgid "<package>cloud-init</package> supported formats and documentation"
-msgstr ""
-
-#: ./doc/common/section_user-data.xml83(para)
+#: ./doc/common/ch_cli_swift_commands.xml755(para)
 msgid ""
-"Look at the <package>cloud-init</package><link "
-"href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-"
-"init/trunk/view/head:/doc/userdata.txt\">doc/userdata.txt</link> file the "
-"<link href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-"
-"init/trunk/files/head:/doc/examples/\">examples</link> directory and the "
-"<link href=\"https://help.ubuntu.com/community/CloudInit\">Ubuntu community "
-"documentation</link> for details about how to use <package>cloud-"
-"init</package>. Some basic examples are provided here."
+"Upload the segments into the specified container. If not specified, the "
+"segments will be uploaded to a &lt;container&gt;_segments container to not "
+"pollute the main &lt;container&gt; listings."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml93(para)
+#: ./doc/common/ch_cli_swift_commands.xml766(para)
 msgid ""
-"<package>cloud-init</package> supports several input formats for user data. "
-"Two commonly used formats are:"
+"Indicates that you want the older segments of manifest objects left alone "
+"(in the case of overwrites)."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml98(para)
-msgid "Shell scripts (starts with <literal>#!</literal>)"
+#: ./doc/common/ch_cli_swift_commands.xml775(para)
+msgid "Number of threads to use for uploading full objects. Default is 10."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml102(para)
-msgid "Cloud config files (starts with <literal>#cloud-config</literal>)"
+#: ./doc/common/ch_cli_swift_commands.xml784(para)
+msgid "Number of threads to use for uploading object segments. Default is 10."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml108(title)
-msgid "Run a shell script on boot"
-msgstr ""
-
-#: ./doc/common/section_user-data.xml109(para)
+#: ./doc/common/ch_cli_swift_commands.xml793(para)
 msgid ""
-"Assuming you have <package>cloud-init</package> installed, the simplest way "
-"to configure an instance on boot is to pass a shell script as user data. The"
-" shell file must begin with <literal>#!</literal> in order for <package"
-">cloud-init</package> to recognize it as a shell script. This example shows "
-"a script that creates a <literal>clouduser</literal> account:"
+"Set request headers with the syntax header:value. This option may be "
+"repeated. Example -H \"content-type:text/plain\"."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml118(para)
+#: ./doc/common/ch_cli_swift_commands.xml803(para)
 msgid ""
-"Sending a shell script as user data has a similar effect to writing an "
-"<filename>/etc/rc.local</filename> script: it executes very late in the boot"
-" sequence as root."
+"When used in conjunction with --segment-size it will create a Static Large "
+"Object instead of the default Dynamic Large Object."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml123(title)
-msgid "Cloud-config format"
-msgstr ""
-
-#: ./doc/common/section_user-data.xml124(para)
+#: ./doc/common/ch_cli_swift_commands.xml813(para)
 msgid ""
-"<package>cloud-init</package> supports a YAML-based config format that "
-"allows the user to configure a large number of options on a system. User "
-"data that begins with <literal>#cloud-config</literal> will be interpreted "
-"by <package>cloud-init</package> as cloud-config format."
+"Upload file and name object to &lt;object-name&gt; or upload dir and use &lt"
+";object-name&gt; as object prefix instead of folder name."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml132(title)
-msgid "Example: Set the host name"
-msgstr ""
+#: ./doc/common/section_cli_neutron_manage_networks.xml7(title)
+msgid "Create and manage networks"
+msgstr "ネットワークの作成と管理"
 
-#: ./doc/common/section_user-data.xml133(para)
+#: ./doc/common/section_cli_neutron_manage_networks.xml8(para)
+msgid "Before you run commands, set the following environment variables:"
+msgstr "コマンドを実行する前に、以下の環境変数を設定します。"
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml15(title)
+msgid "Create networks"
+msgstr "ネットワークの作成"
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml18(para)
+msgid "List the extensions of the system:"
+msgstr "システムの拡張を表示します。"
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml34(para)
+msgid "Create a network:"
+msgstr "ネットワークを作成します。"
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml53(para)
+msgid "Some fields of the created network are invisible to non-admin users."
+msgstr "作成したネットワークのフィールドで管理者ユーザー以外には表示されないものもあります。"
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml58(para)
+msgid "Create a network with specified provider network type:"
+msgstr "指定のプロバイダーネットワークタイプでネットワークを作成します。"
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml77(para)
 msgid ""
-"This <package>cloud-init</package> user data example sets the hostname and "
-"the FQDN, as well as updating <filename>/etc/hosts</filename> on the "
-"instance:"
-msgstr ""
+"Just as shown previously, the unknown option <literal>--provider:network-"
+"type</literal> is used to create a <literal>local</literal> provider "
+"network."
+msgstr "先ほど説明したように、不明オプション <literal>--provider:network-type</literal> を使用して、<literal>local</literal> プロバイダーネットワークを作成します。"
 
-#: ./doc/common/section_user-data.xml145(title)
-msgid "Example: Configure instances with Puppet"
-msgstr ""
+#: ./doc/common/section_cli_neutron_manage_networks.xml85(title)
+msgid "Create subnets"
+msgstr "サブネットの作成"
 
-#: ./doc/common/section_user-data.xml146(para)
+#: ./doc/common/section_cli_neutron_manage_networks.xml88(para)
+msgid "Create a subnet:"
+msgstr "サブネットを作成します。"
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml106(para)
 msgid ""
-"This <package>cloud-init</package> user data example, based on <link "
-"href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-"
-"init/trunk/view/head:/doc/examples/cloud-config-puppet.txt\">doc/examples"
-"/cloud-config-puppet.txt</link>, would configure the instance to contact a "
-"Puppet server at puppetmaster.example.org and verify its identity by using a"
-" certificate."
+"The <placeholder-1/> command has the following positional and optional "
+"parameters:"
 msgstr ""
 
-#: ./doc/common/section_user-data.xml174(title)
-msgid "Example: Configure instances with Chef"
+#: ./doc/common/section_cli_neutron_manage_networks.xml111(para)
+msgid "The name or ID of the network to which the subnet belongs."
 msgstr ""
 
-#: ./doc/common/section_user-data.xml175(para)
+#: ./doc/common/section_cli_neutron_manage_networks.xml113(para)
 msgid ""
-"This <package>cloud-init</package> user data example, based on <link "
-"href=\"http://bazaar.launchpad.net/~cloud-init-dev/cloud-"
-"init/trunk/view/head:/doc/examples/cloud-config-chef.txt\">doc/examples"
-"/cloud-config/chef.txt</link> and intended for use in an Ubuntu image, adds "
-"the Chef apt repository, installs Chef, connects to a Chef server at "
-"<literal>https://chefserver.example.com:4000</literal>, and installs Apache:"
+"In this example, <literal>net1</literal> is a positional argument that "
+"specifies the network name."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml6(title)
-msgid "Add security group and rules"
+#: ./doc/common/section_cli_neutron_manage_networks.xml118(para)
+msgid "The CIDR of the subnet."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml7(para)
+#: ./doc/common/section_cli_neutron_manage_networks.xml119(para)
 msgid ""
-"The following procedure shows you how to add security groups and add rules "
-"to the default security group."
+"In this example, <literal>192.168.2.0/24</literal> is a positional argument "
+"that specifies the CIDR."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml10(title)
-msgid "Add or delete a security group"
+#: ./doc/common/section_cli_neutron_manage_networks.xml125(para)
+msgid "The subnet name, which is optional."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml11(para)
-msgid "Use the <placeholder-1/> command to add security groups."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_secgroups.xml13(para)
+#: ./doc/common/section_cli_neutron_manage_networks.xml127(para)
 msgid ""
-"The following example shows how to create the <literal>secure1</literal> "
-"security group:"
+"In this example, <literal>--name subnet1</literal> specifies the name of the"
+" subnet."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml21(para)
+#: ./doc/common/section_cli_neutron_manage_networks.xml136(title)
+msgid "Create routers"
+msgstr "ルーターの作成"
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml139(para)
+msgid "Create a router:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml140(replaceable)
+msgid "router1"
+msgstr "router1"
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml152(para)
 msgid ""
-"After you create the security group, you can view it in the security group "
-"list:"
-msgstr ""
+"Take note of the unique router identifier returned, this will be required in"
+" subsequent steps."
+msgstr "返された一意なルーター ID を記録します。これは以降の手順に必要となります。"
 
-#: ./doc/common/section_cli_nova_secgroups.xml30(para)
+#: ./doc/common/section_cli_neutron_manage_networks.xml156(para)
+msgid "Link the router to the external provider network:"
+msgstr "ルーターを外部プロバイダーネットワークにリンクします。"
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml157(replaceable)
+#: ./doc/common/section_cli_neutron_manage_networks.xml164(replaceable)
+msgid "ROUTER"
+msgstr "ROUTER"
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml157(replaceable)
+msgid "NETWORK"
+msgstr "NETWORK"
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml158(para)
 msgid ""
-"Use the <placeholder-1/> command to delete security groups. You cannot "
-"delete the default security group. The default security group has these "
-"initial settings:"
-msgstr ""
+"Replace <replaceable>ROUTER</replaceable> with the unique identifier of the "
+"router, replace <replaceable>NETWORK</replaceable> with the unique "
+"identifier of the external provider network."
+msgstr "<replaceable>ROUTER</replaceable> をルーターの一意な ID で置き換え、<replaceable>NETWOKR</replaceable> を外部プロバイダールーターの一意な ID で置き換えます。"
 
-#: ./doc/common/section_cli_nova_secgroups.xml36(para)
+#: ./doc/common/section_cli_neutron_manage_networks.xml163(para)
+msgid "Link the router to the subnet:"
+msgstr "ルーターをサブネットにリンクします。"
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml164(replaceable)
+msgid "SUBNET"
+msgstr "SUBNET"
+
+#: ./doc/common/section_cli_neutron_manage_networks.xml165(para)
 msgid ""
-"All the traffic originated by the instances (outbound traffic) is allowed"
-msgstr ""
+"Replace <replaceable>ROUTER</replaceable> with the unique identifier of the "
+"router, replace <replaceable>SUBNET</replaceable> with the unique identifier"
+" of the subnet."
+msgstr "<replaceable>ROUTER</replaceable> をルーターの一意な ID で置き換え、<replaceable>SUBNET</replaceable> をサブネットの一意な ID で置き換えます。"
 
-#: ./doc/common/section_cli_nova_secgroups.xml40(para)
-msgid "All the traffic destined to instances (inbound traffic) is denied"
-msgstr ""
+#: ./doc/common/section_cli_neutron_manage_networks.xml172(title)
+msgid "Create ports"
+msgstr "ポートの作成"
 
-#: ./doc/common/section_cli_nova_secgroups.xml44(para)
-msgid "All the instances inside the group are allowed to talk to each other"
-msgstr ""
+#: ./doc/common/section_cli_neutron_manage_networks.xml175(para)
+msgid "Create a port with specified IP address:"
+msgstr "指定の IP アドレスでポートを作成します。"
 
-#: ./doc/common/section_cli_nova_secgroups.xml49(para)
+#: ./doc/common/section_cli_neutron_manage_networks.xml194(para)
 msgid ""
-"You can add extra rules into the default security group for handling the "
-"egress traffic. Rules are ingress only at this time."
-msgstr ""
+"In the previous command, <literal>net1</literal> is the network name, which "
+"is a positional argument. <literal>--fixed-ip "
+"ip_address=192.168.2.40</literal> is an option, which specifies the port's "
+"fixed IP address we wanted."
+msgstr "上記のコマンドでは、<literal>net1</literal> がネットワーク名で、位置引数となっています。 <literal>--fixed-ip ip_address=192.168.2.40</literal> はオプションで、希望のポートの Fixed IP アドレスを指定します。"
 
-#: ./doc/common/section_cli_nova_secgroups.xml53(para)
+#: ./doc/common/section_cli_neutron_manage_networks.xml201(para)
 msgid ""
-"The following example deletes the <literal>secure1</literal> group. When you"
-" view the security group list, it no longer appears:"
+"When creating a port, you can specify any unallocated IP in the subnet even "
+"if the address is not in a pre-defined pool of allocated IP addresses (set "
+"by your cloud provider)."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml65(title)
-msgid "Modify security group rules"
-msgstr ""
+#: ./doc/common/section_cli_neutron_manage_networks.xml208(para)
+msgid "Create a port without specified IP address:"
+msgstr "IP アドレス指定なしでポートを作成します。"
 
-#: ./doc/common/section_cli_nova_secgroups.xml69(para)
-msgid "You cannot change the default outbound behavior."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_secgroups.xml66(para)
+#: ./doc/common/section_cli_neutron_manage_networks.xml229(para)
 msgid ""
-"The security group rules control the incoming traffic that can access the "
-"instances in the group, while all outbound traffic is automatically allowed."
-" <placeholder-1/>Every security group rule is a policy that allows you to "
-"specify inbound connections that can access the instance by source address, "
-"destination port, and IP protocol (TCP, UDP or ICMP). Currently, you cannot "
-"manage ipv6 and other protocols through the security rules, making them "
-"permitted by default. To manage such protocols, you can deploy a firewall in"
-" front of your OpenStack cloud to control other types of traffic. The "
-"command requires the following arguments for both TCP and UDP rules:"
+"Note that the system allocates one IP address if you do not specify an IP "
+"address in the <placeholder-1/> command."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml84(emphasis)
-#: ./doc/common/section_cli_nova_secgroups.xml124(emphasis)
-#: ./doc/common/section_cli_nova_secgroups.xml209(emphasis)
-msgid "&lt;secgroup&gt;"
-msgstr ""
+#: ./doc/common/section_cli_neutron_manage_networks.xml234(para)
+msgid "Query ports with specified fixed IP addresses:"
+msgstr "指定の Fixed IP アドレスでポートを問い合わせします。"
 
-#: ./doc/common/section_cli_nova_secgroups.xml86(para)
-#: ./doc/common/section_cli_nova_secgroups.xml126(para)
-#: ./doc/common/section_cli_nova_secgroups.xml211(para)
-msgid "ID of security group."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_secgroups.xml91(emphasis)
-#: ./doc/common/section_cli_nova_secgroups.xml131(emphasis)
-#: ./doc/common/section_cli_nova_secgroups.xml216(emphasis)
-msgid "&lt;ip_proto&gt;"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_secgroups.xml98(emphasis)
-#: ./doc/common/section_cli_nova_secgroups.xml223(emphasis)
-msgid "&lt;from_port&gt;"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_secgroups.xml105(emphasis)
-#: ./doc/common/section_cli_nova_secgroups.xml230(emphasis)
-msgid "&lt;to_port&gt;"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_secgroups.xml112(emphasis)
-#: ./doc/common/section_cli_nova_secgroups.xml152(emphasis)
-#: ./doc/common/section_cli_nova_secgroups.xml237(emphasis)
-msgid "&lt;cidr&gt;"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_secgroups.xml118(para)
+#: ./doc/common/section_cli_neutron_manage_networks.xml243(para)
 msgid ""
-"For ICMP rules, instead of specifying a begin and end port, you specify the "
-"allowed ICMP code and ICMP type:"
-msgstr ""
+"<literal>--fixed-ips ip_address=192.168.2.2 "
+"ip_address=192.168.2.40</literal> is one unknown option."
+msgstr "<literal>--fixed-ips ip_address=192.168.2.2 ip_address=192.168.2.40</literal> は不明オプションです。"
 
-#: ./doc/common/section_cli_nova_secgroups.xml133(para)
-msgid "IP protocol (with icmp specified)."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_secgroups.xml138(emphasis)
-msgid "&lt;ICMP_code&gt;"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_secgroups.xml140(para)
-msgid "The ICMP code."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_secgroups.xml145(emphasis)
-msgid "&lt;ICMP_type&gt;"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_secgroups.xml147(para)
-msgid "The ICMP type."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_secgroups.xml154(para)
-msgid "CIDR for the source address range."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_secgroups.xml159(para)
+#: ./doc/common/section_cli_neutron_manage_networks.xml246(para)
 msgid ""
-"Entering <literal>-1</literal> for both code and type indicates that all "
-"ICMP codes and types are allowed."
-msgstr ""
+"<emphasis role=\"bold\">How to find unknown options?</emphasis> The unknown "
+"options can be easily found by watching the output of "
+"<literal>create_xxx</literal> or <literal>show_xxx</literal> command. For "
+"example, in the port creation command, we see the fixed_ips fields, which "
+"can be used as an unknown option."
+msgstr "<emphasis role=\"bold\">不明オプションの探し方</emphasis>: 不明オプションは、<literal>create_xxx</literal> または <literal>show_xxx</literal> コマンドの出力を見ているとすぐに見つけられます。例えば、ポート作成コマンドには fixed_ips フィールドがありますが、これは不明オプションとして使用することができます。"
 
-#: ./doc/common/section_cli_nova_secgroups.xml164(title)
-msgid "The CIDR notation"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_secgroups.xml165(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-arch.xml23(None)
 msgid ""
-"That notation allows you to specify a base IP address and a suffix that "
-"designates the number of significant bits in the IP address used to identify"
-" the network. For example, by specifying a "
-"<literal>88.170.60.32/27</literal>, you specify "
-"<literal>88.170.60.32</literal> as the <emphasis role=\"bold\">base "
-"IP</emphasis> and <literal>27</literal> as the <emphasis "
-"role=\"bold\">suffix</emphasis>. Because you use an IPV4 format, only 5 bits"
-" are available for the host part (32 minus 27). The "
-"<literal>0.0.0.0/0</literal> notation means you allow the entire IPV4 range,"
-" which allows all addresses."
-msgstr ""
+"@@image: '../common/figures/objectstorage-arch.png'; "
+"md5=90f6c7cf3947d7987eeb55d657cdc927"
+msgstr "@@image: '../common/figures/objectstorage-arch.png'; md5=90f6c7cf3947d7987eeb55d657cdc927"
 
-#: ./doc/common/section_cli_nova_secgroups.xml179(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-arch.xml60(None)
 msgid ""
-"For example, to allow any IP address to access a web server running on one "
-"of your instances inside the default security group:"
+"@@image: '../common/figures/objectstorage-nodes.png'; "
+"md5=2aa7eb3bddcf6826f33469920dc2a9c3"
+msgstr "@@image: '../common/figures/objectstorage-nodes.png'; md5=2aa7eb3bddcf6826f33469920dc2a9c3"
+
+#: ./doc/common/section_objectstorage-arch.xml11(title)
+msgid "Cluster architecture"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml188(para)
+#: ./doc/common/section_objectstorage-arch.xml13(title)
+msgid "Access tier"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-arch.xml14(para)
 msgid ""
-"To allow any IP address to ping an instance inside the default security "
-"group (Code 0, Type 8 for the ECHO request):"
+"Large-scale deployments segment off an access tier, which is considered the "
+"Object Storage system's central hub. The access tier fields the incoming API"
+" requests from clients and moves data in and out of the system. This tier "
+"consists of front-end load balancers, ssl-terminators, and authentication "
+"services. It runs the (distributed) brain of the Object Storage system: the "
+"proxy server processes."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_secgroups.xml204(para)
+#: ./doc/common/section_objectstorage-arch.xml20(title)
+msgid "Object Storage architecture"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-arch.xml27(para)
 msgid ""
-"To delete a rule, you must specify exactly the same arguments that you used "
-"to create it:"
+"Because access servers are collocated in their own tier, you can scale out "
+"read/write access regardless of the storage capacity. For example, if a "
+"cluster is on the public Internet, requires SSL termination, and has a high "
+"demand for data access, you can provision many access servers. However, if "
+"the cluster is on a private network and used primarily for archival "
+"purposes, you need fewer access servers."
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts-domain-management.xml6(title)
-msgid "Domains"
-msgstr "ドメイン"
-
-#: ./doc/common/section_keystone-concepts-domain-management.xml7(para)
+#: ./doc/common/section_objectstorage-arch.xml32(para)
 msgid ""
-"A domain defines administrative boundaries for the management of Identity "
-"entities. A domain may represent an individual, company, or operator-owned "
-"space. It is used for exposing administrative activities directly to the "
-"system users."
+"Since this is an HTTP addressable storage service, you may incorporate a "
+"load balancer into the access tier."
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts-domain-management.xml10(para)
+#: ./doc/common/section_objectstorage-arch.xml34(para)
 msgid ""
-"A domain is a collection of tenants, users, and roles. Users may be given a "
-"domain's administrator role. A domain administrator may create tenants, "
-"users, and groups within a domain and assign roles to users and groups."
+"Typically, the tier consists of a collection of 1U servers. These machines "
+"use a moderate amount of RAM and are network I/O intensive. Since these "
+"systems field each incoming API request, you should provision them with two "
+"high-throughput (10GbE) interfaces - one for the incoming \"front-end\" "
+"requests and the other for the \"back-end\" access to the object storage "
+"nodes to put and fetch data."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_get_console.xml6(title)
-msgid "Access an instance through a console"
+#: ./doc/common/section_objectstorage-arch.xml40(title)
+#: ./doc/common/section_objectstorage-arch.xml69(title)
+msgid "Factors to consider"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_get_console.xml7(para)
+#: ./doc/common/section_objectstorage-arch.xml41(para)
 msgid ""
-"To access an instance through a VNC console, run the following command:"
+"For most publicly facing deployments as well as private deployments "
+"available across a wide-reaching corporate network, you use SSL to encrypt "
+"traffic to the client. SSL adds significant processing load to establish "
+"sessions between clients, which is why you have to provision more capacity "
+"in the access layer. SSL may not be required for private deployments on "
+"trusted networks."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_get_console.xml8(replaceable)
-#: ./doc/common/section_cli_nova_startstop.xml14(replaceable)
-#: ./doc/common/section_cli_nova_startstop.xml18(replaceable)
-#: ./doc/common/section_cli_nova_startstop.xml35(replaceable)
-#: ./doc/common/section_cli_nova_startstop.xml40(replaceable)
-#: ./doc/common/section_cli_nova_boot.xml188(replaceable)
-msgid "INSTANCE_NAME"
-msgstr "INSTANCE_NAME"
+#: ./doc/common/section_objectstorage-arch.xml49(title)
+msgid "Storage nodes"
+msgstr ""
 
-#: ./doc/common/section_cli_nova_get_console.xml9(para)
-msgid "The command returns a URL from which you can access your instance:"
-msgstr "このコマンドは、インスタンスにアクセスするための URL を返します。"
-
-#: ./doc/common/section_cli_nova_get_console.xml15(para)
+#: ./doc/common/section_objectstorage-arch.xml50(para)
 msgid ""
-"To access an instance through a non-VNC console, specify the "
-"<parameter>novnc</parameter> parameter instead of the "
-"<parameter>xvpvnc</parameter> parameter."
+"In most configurations, each of the five zones should have an equal amount "
+"of storage capacity. Storage nodes use a reasonable amount of memory and "
+"CPU. Metadata needs to be readily available to return objects quickly. The "
+"object stores run services not only to field incoming requests from the "
+"access tier, but to also run replicators, auditors, and reapers. You can "
+"provision object stores provisioned with single gigabit or 10 gigabit "
+"network interface depending on the expected workload and desired "
+"performance."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-arch.xml57(title)
+#: ./doc/common/section_objectstorage-characteristics.xml46(title)
+#: ./doc/common/section_storage-concepts.xml21(td)
+msgid "Object Storage (swift)"
+msgstr "Object Storage (swift)"
+
+#: ./doc/common/section_objectstorage-arch.xml64(para)
+msgid ""
+"Currently, a 2TB or 3TB SATA disk delivers good performance for the price. "
+"You can use desktop-grade drives if you have responsive remote hands in the "
+"datacenter and enterprise-grade drives if you don't."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-arch.xml70(para)
+msgid ""
+"You should keep in mind the desired I/O performance for single-threaded "
+"requests . This system does not use RAID, so a single disk handles each "
+"request for an object. Disk performance impacts single-threaded response "
+"rates."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-arch.xml73(para)
+msgid ""
+"To achieve apparent higher throughput, the object storage system is designed"
+" to handle concurrent uploads/downloads. The network I/O capacity (1GbE, "
+"bonded 1GbE pair, or 10GbE) should match your desired concurrent throughput "
+"needs for reads and writes."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_example_usage.xml6(title)
+msgid "keystone command-line client example usage"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_example_usage.xml7(para)
+msgid ""
+"Before you can use keystone client commands, you must download and source an"
+" OpenStack RC file. For information, see the <citetitle>OpenStack Admin User"
+" Guide</citetitle>."
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_example_usage.xml10(para)
+msgid "The keystone command-line client uses the following syntax:"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_example_usage.xml12(replaceable)
+msgid "PARAMETER"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_example_usage.xml12(replaceable)
+msgid "ARGUMENT"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_example_usage.xml13(para)
+msgid ""
+"For example, you can run the <placeholder-1/> and <placeholder-2/> commands,"
+" as follows:"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_example_usage.xml22(replaceable)
+#: ./doc/common/section_cli_keystone_example_usage.xml23(replaceable)
+msgid "token"
+msgstr "トークン"
+
+#: ./doc/common/section_cli_keystone_example_usage.xml22(replaceable)
+#: ./doc/common/section_cli_keystone_example_usage.xml23(replaceable)
+msgid "endpoint"
+msgstr "エンドポイント"
+
+#: ./doc/common/section_cli_keystone_example_usage.xml31(replaceable)
+msgid "id"
+msgstr "id"
+
+#: ./doc/common/section_cli_keystone_example_usage.xml34(para)
+msgid ""
+"For information about using the keystone client commands to create and "
+"manage users, roles, and projects, see the <citetitle>OpenStack Admin User "
+"Guide</citetitle>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml5(title)
+msgid "Manage bare-metal nodes"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml6(para)
+msgid ""
+"The bare-metal driver for OpenStack Compute manages provisioning of physical"
+" hardware by using common cloud APIs and tools such as Orchestration (Heat)."
+" The use case for this driver is for single tenant clouds such as a high-"
+"performance computing cluster or for deploying OpenStack itself."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml10(para)
+msgid ""
+"If you use the bare-metal driver, you must create a network interface and "
+"add it to a bare-metal node. Then, you can launch an instance from a bare-"
+"metal image."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml13(para)
+msgid ""
+"Development efforts are focused on moving the driver out of the Compute code"
+" base in the Icehouse release."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml15(para)
+msgid ""
+"You can list and delete bare-metal nodes. When you delete a node, any "
+"associated network interfaces are removed. You can list and remove network "
+"interfaces that are associated with a bare-metal node."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml19(title)
+msgid "Commands"
+msgstr "コマンド"
+
+#: ./doc/common/section_cli_nova_baremetal.xml20(para)
+msgid "The following commands can be used to manage bare-metal nodes."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml22(para)
+msgid "<placeholder-1/>. Adds a network interface to a bare-metal node."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml26(para)
+msgid ""
+"<placeholder-1/>. Lists network interfaces associated with a bare-metal "
+"node."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml30(para)
+msgid "<placeholder-1/>. Removes a network interface from a bare-metal node."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml34(para)
+msgid "<placeholder-1/>. Creates a bare-metal node."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml38(para)
+msgid ""
+"<placeholder-1/>. Removes a bare-metal node and any associated interfaces."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml42(para)
+msgid "<placeholder-1/>. Lists available bare-metal nodes."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml46(para)
+msgid "<placeholder-1/>. Shows information about a bare-metal node."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml51(title)
+msgid "Create a bare-metal node"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml52(para)
+msgid ""
+"When you create a bare-metal node, your PM address, username, and password "
+"should match those that are configured in your hardware's BIOS/IPMI "
+"configuration."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml57(para)
+msgid ""
+"The following example shows the command and results from creating a node "
+"with the PM address <filename>1.2.3.4</filename>, the PM username "
+"<literal>ipmi</literal>, and password <literal>ipmi</literal>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml79(title)
+msgid "Add a network interface to the node:"
+msgstr "ベアメタルノードにネットワークインターフェースを追加します。"
+
+#: ./doc/common/section_cli_nova_baremetal.xml80(para)
+msgid ""
+"For each NIC on the node, you must create an interface, specifying the "
+"interface's MAC address."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml92(title)
+msgid "Launch an instance from a bare-metal image:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml94(para)
+msgid ""
+"A bare-metal instance is an instance created directly on a physical machine "
+"without any virtualization layer running underneath it. Nova retains power "
+"control via IPMI. In some situations, Nova may retain network control via "
+"Neutron and OpenFlow."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml107(para)
+msgid ""
+"Set the <parameter>--availability_zone</parameter> parameter to specify "
+"which zone or node to use to start the server. Separate the zone from the "
+"host name with a comma. For example:"
+msgstr "<parameter>--availability_zone</parameter> パラメーターを設定して、サーバーを起動するゾーンまたはノードを指定します。ホスト名とゾーンはコンマで区切ります。例えば以下のようになります。"
+
+#: ./doc/common/section_cli_nova_baremetal.xml110(replaceable)
+msgid "HOST"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml110(replaceable)
+msgid "NODE"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml111(para)
+msgid ""
+"<literal>host</literal> is optional for the "
+"<literal>--availability_zone</literal> parameter. You can specify simply "
+"<literal>zone:,node</literal>. You must still use the comma."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml118(title)
+msgid "List bare-metal nodes and interfaces:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml120(para)
+msgid ""
+"Use the <placeholder-1/> command to view all bare-metal nodes and "
+"interfaces. When a node is in use, its status includes the UUID of the "
+"instance that runs on it:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml130(title)
+msgid "Show details for a bare-metal node:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_baremetal.xml131(para)
+msgid ""
+"Use the <placeholder-1/> command to view the details for a bare-metal node."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml6(title)
+msgid "Troubleshoot the Identity service"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml7(para)
+msgid ""
+"To troubleshoot the Identity service, review the logs in the "
+"<filename>/var/log/keystone/keystone.log</filename> file."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml10(para)
+msgid ""
+"Use the <filename>/etc/keystone/logging.conf</filename> file to configure "
+"the location of log files."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml13(para)
+msgid ""
+"The logs show the components that have come in to the WSGI request, and "
+"ideally show an error that explains why an authorization request failed. If "
+"you do not see the request in the logs, run keystone with "
+"<parameter>--debug</parameter> parameter. Pass the "
+"<parameter>--debug</parameter> parameter before the command parameters."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml20(title)
+msgid "Debug PKI middleware"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml21(para)
+msgid ""
+"If you receive an <literal>Invalid OpenStack Identity Credentials</literal> "
+"message when you talk to an OpenStack service, it might be caused by the "
+"changeover from UUID tokens to PKI tokens in the Grizzly release. Learn how "
+"to troubleshoot this error."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml26(para)
+msgid ""
+"The PKI-based token validation scheme relies on certificates from Identity "
+"that are fetched through HTTP and stored in a local directory. The location "
+"for this directory is specified by the <literal>signing_dir</literal> "
+"configuration option. In your services configuration file, look for a "
+"section like this:"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml41(para)
+msgid ""
+"If your service lacks this stanza, the <link "
+"href=\"https://github.com/openstack/python-"
+"keystoneclient/blob/master/keystoneclient/middleware/auth_token.py#L198\">keystoneclient/middleware/auth_token.py</link>"
+" file specifies the defaults. If no value is specified for this directory, "
+"it <link href=\"https://github.com/openstack/python-"
+"keystoneclient/blob/master/keystoneclient/middleware/auth_token.py#L299\">defaults"
+" to a secure temporary directory.</link> Initialization code for the service"
+" checks that the directory exists and is writable. If it does not exist, the"
+" code tries to create it. If this fails, the service fails to start. "
+"However, it often succeeds but problems occur later."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml53(para)
+msgid ""
+"The first thing to check is that the <literal>signing_dir</literal> does, in"
+" fact, exist. If it does, check for the presence of the certificate files "
+"inside there:"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml64(para)
+msgid ""
+"This directory contains two certificates and the token revocation list. If "
+"these files are not present, your service cannot fetch them from Identity. "
+"To troubleshoot, try to talk to Identity to make sure it correctly serves "
+"files, as follows:"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml70(para)
+msgid "This command fetches the signing certificate:"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml81(para)
+msgid "Note the expiration dates of the certificate:"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml84(para)
+msgid ""
+"The token revocation list is updated once a minute, but the certificates are"
+" not. One possible problem is that the certificates are the wrong files or "
+"garbage. You can remove these files and run another command against your "
+"server: They are fetched on demand."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml89(para)
+msgid ""
+"The Identity service log should show the access of the certificate files. "
+"You might have to turn up your logging levels. Set <literal>debug = "
+"True</literal> and <literal>verbose = True</literal> in your Identity "
+"configuration file and restart the Identity server."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml98(para)
+msgid ""
+"If the files do not appear in your directory after this, it is likely one of"
+" the following issues:"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml102(para)
+msgid ""
+"Your service is configured incorrectly and cannot talk to Identity. Check "
+"the <literal>auth_port</literal> and <literal>auth_host</literal> values and"
+" make sure that you can talk to that service through cURL, as shown "
+"previously."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml110(para)
+msgid ""
+"Your signing directory is not writable. Use the <placeholder-1/> command to "
+"change its permissions so that the service (POSIX) user can write to it. "
+"Verify the change through <placeholder-2/> and <placeholder-3/> commands."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml118(para)
+msgid "The SELinux policy is denying access to the directory."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml122(para)
+msgid ""
+"SELinux troubles often occur when you use Fedora/RHEL-based packages and you"
+" choose configuration options that do not match the standard policy. Run the"
+" <placeholder-1/> command. If that makes a difference, you should relabel "
+"the directory. If you are using a sub-directory of the "
+"<filename>/var/cache/</filename> directory, run the following command:"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml131(para)
+msgid ""
+"If you are not using a <filename>/var/cache</filename> sub-directory, you "
+"should. Modify the <literal>signing_dir</literal> configuration option for "
+"your service and restart."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml135(para)
+msgid ""
+"Set back to <literal>setenforce enforcing</literal> to confirm that your "
+"changes solve the problem."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml137(para)
+msgid ""
+"If your certificates are fetched on demand, the PKI validation is working "
+"properly. Most likely, the token from Identity is not valid for the "
+"operation you are attempting to perform, and your user needs a different "
+"role for the operation."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml144(title)
+msgid "Debug signing key file errors"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml145(para)
+msgid ""
+"If an error occurs when the signing key file opens, it is possible that the "
+"person who ran the <placeholder-1/> command to generate certificates and "
+"keys did not use the correct user. When you run the <placeholder-2/> "
+"command, Identity generates a set of certificates and keys in "
+"<filename>/etc/keystone/ssl*</filename>, which is owned by root:root."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml154(para)
+msgid ""
+"This can present a problem when you run the Identity daemon under the "
+"keystone user account (nologin) when you try to run PKI. Unless you run the "
+"<placeholder-1/> command against the files keystone:keystone or run the "
+"<placeholder-2/> command with the <parameter>--keystone-user</parameter> and"
+" <parameter>--keystone-group</parameter> parameters, you get an error, as "
+"follows:"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml172(title)
+msgid "Flush expired tokens from the token database table"
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml174(para)
+msgid ""
+"As you generate tokens, the token database table on the Identity server "
+"grows. To clear the token table, an administrative user must run the "
+"<placeholder-1/> command to flush the tokens. When you flush tokens, expired"
+" tokens are deleted and traceability is eliminated."
+msgstr ""
+
+#: ./doc/common/section_identity-troubleshooting.xml180(para)
+msgid ""
+"Use <placeholder-1/> to schedule this command to run frequently based on "
+"your workload. For large workloads, running it every minute is recommended."
+msgstr ""
+
+#: ./doc/common/section_getstart_trove.xml5(title)
+msgid "Database service overview"
+msgstr "Database の概要"
+
+#: ./doc/common/section_getstart_trove.xml6(para)
+msgid ""
+"The Database service provides scalable and reliable cloud provisioning "
+"functionality for both relational and non-relational database engines. Users"
+" can quickly and easily utilize database features without the burden of "
+"handling complex administrative tasks. Cloud users and database "
+"administrators can provision and manage multiple database instances as "
+"needed."
+msgstr "Database は、リレーショナルデータベースと非リレーショナルデータベースの両方のエンジン向けにスケール可能な信頼できるクラウド展開機能を提供します。ユーザーは、複雑な管理作業を実行することなく、迅速かつ容易にデータベース機能を利用できます。クラウドのユーザーとデータベース管理者は、必要に応じて複数のデータベースインスタンスを展開、管理できます。"
+
+#: ./doc/common/section_getstart_trove.xml7(para)
+msgid ""
+"The Database service provides resource isolation at high performance levels,"
+" and automates complex administrative tasks such as deployment, "
+"configuration, patching, backups, restores, and monitoring."
+msgstr "Database は、高性能にリソースを分割でき、配備、設定、パッチ適用、バックアップ、リストア、監視などの複雑な管理作業を自動化します。"
+
+#: ./doc/common/section_getstart_trove.xml9(title)
+msgid "Process flow example."
+msgstr "プロセスフロー例。"
+
+#: ./doc/common/section_getstart_trove.xml9(para)
+msgid "Here is a high-level process flow example for using Database services:"
+msgstr "これは、Database のサービスを利用するための、高レベルなプロセスフローの例です。"
+
+#: ./doc/common/section_getstart_trove.xml12(para)
+msgid "Administrator sets up infrastructure:"
+msgstr "管理者がインフラストラクチャーをセットアップします。"
+
+#: ./doc/common/section_getstart_trove.xml15(para)
+msgid "OpenStack administrator installs the Database service."
+msgstr "OpenStack 管理者が Database をインストールします。"
+
+#: ./doc/common/section_getstart_trove.xml18(para)
+msgid ""
+"She creates one image for each type of database the administrator wants to "
+"have (one for MySQL, one for MongoDB, and so on)."
+msgstr "管理者が使用したいデータベース種別ごとのイメージを作成します。例えば、MySQL、MongoDB などです。"
+
+#: ./doc/common/section_getstart_trove.xml23(para)
+msgid ""
+"OpenStack administrator updates the datastore to use the new images, using "
+"the <placeholder-1/> command."
+msgstr "OpenStack 管理者は、新しいイメージを使用するために、<placeholder-1/> コマンドを使用して、データストアを更新します。"
+
+#: ./doc/common/section_getstart_trove.xml30(para)
+msgid "End user uses database service:"
+msgstr "エンドユーザーがデータベースのサービスを使用します。"
+
+#: ./doc/common/section_getstart_trove.xml33(para)
+msgid ""
+"Now that the basic infrastructure is set up, an end user can create a Trove "
+"instance (database) whenever the user wants, using the <placeholder-1/> "
+"command."
+msgstr "ここまでに基本的なインフラストラクチャーがセットアップされました。エンドユーザーが、使用したいときに <placeholder-1/> コマンドを使用して、Trove インスタンス (データベース) を作成できます。"
+
+#: ./doc/common/section_getstart_trove.xml41(replaceable)
+msgid "instanceID"
+msgstr "instanceID"
+
+#: ./doc/common/section_getstart_trove.xml39(para)
+msgid ""
+"The end user gets the IP address of the Trove instance by using the "
+"<placeholder-1/> command to get the ID of the instance, and then using the "
+"<placeholder-2/> command to get the IP address."
+msgstr "エンドユーザーは、インスタンスの ID を取得するために <placeholder-1/> コマンドを使用し、IP アドレスを取得するために <placeholder-2/> コマンドを使用することにより、Trove インスタンスの IP アドレスを取得します。"
+
+#: ./doc/common/section_getstart_trove.xml44(para)
+msgid ""
+"The end user can now access the Trove instance using typical database access"
+" commands. MySQL example:"
+msgstr "エンドユーザーは、一般的なデータベースアクセスコマンドを使用して、Trove インスタンスにアクセスできます。MySQL の例:"
+
+#: ./doc/common/section_getstart_trove.xml45(replaceable)
+msgid "trove_ip_address"
+msgstr "trove_ip_address"
+
+#: ./doc/common/section_getstart_trove.xml51(title)
+msgid "Components:"
+msgstr "コンポーネント:"
+
+#: ./doc/common/section_getstart_trove.xml51(para)
+msgid "The Database service includes the following components:"
+msgstr "Database は以下のコンポーネントを含みます。"
+
+#: ./doc/common/section_getstart_trove.xml55(para)
+msgid ""
+"<code>python-troveclient</code> command-line client. A CLI that communicates"
+" with the <code>trove-api</code> component."
+msgstr "<code>python-troveclient</code> コマンドラインクライアント。<code>trove-api</code> コンポーネントと通信する CLI。"
+
+#: ./doc/common/section_getstart_trove.xml58(para)
+msgid ""
+"<code>trove-api</code> component. Provides an OpenStack-native RESTful API "
+"that supports JSON to provision and manage Trove instances."
+msgstr "<code>trove-api</code> コンポーネント。Trove インスタンスを展開、管理するために JSON をサポートする、OpenStack ネイティブ RESTful API を提供します。"
+
+#: ./doc/common/section_getstart_trove.xml62(para)
+msgid ""
+"<code>trove-conductor</code> service. Runs on the host, and receives "
+"messages from guest instances that want to update information on the host."
+msgstr "<code>trove-conductor</code> サービス。ホストで実行し、ホストに情報をアップロードしたいゲストインスタンスからのメッセージを受け取ります。"
+
+#: ./doc/common/section_getstart_trove.xml65(para)
+msgid ""
+"<code>trove-taskmanager</code> service. Instruments the complex system flows"
+" that support provisioning instances, managing the lifecycle of instances, "
+"and performing operations on instances."
+msgstr "<code>trove-taskmanager</code> サービス。インスタンスの展開、インスタンスのライフサイクルの管理、インスタンス上の処理の実行をサポートする複雑なシステムフローを備えます。"
+
+#: ./doc/common/section_getstart_trove.xml68(para)
+msgid ""
+"<code>trove-guestagent</code> service. Runs within the guest instance. "
+"Manages and performs operations on the database itself."
+msgstr "<code>trove-guestagent</code> サービス。ゲストインスタンスの中で実行します。データベース自身の処理を管理、実行します。"
+
+#: ./doc/common/section_keystone_db_sync.xml6(title)
+msgid "Migrate the Identity Service database"
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml7(para)
+msgid ""
+"Between revisions of the Identity Service project, you might need to "
+"complete SQL migrations. The Identity Service project uses SQLAlchemy-"
+"migrate (see <link href=\"http://code.google.com/p/sqlalchemy-"
+"migrate/\">http://code.google.com/p/sqlalchemy-migrate/</link>) to migrate "
+"the SQL database between revisions. For core components, the source code "
+"stores migrations in a central repository under a "
+"<filename>keystone/common/sql/migrate_repo</filename> directory."
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml17(para)
+msgid ""
+"Extensions to the Identity Service might also require SQL migrations. The "
+"directory <filename>keystone/contrib/example</filename> in the keystone "
+"repository contains a sample extension migration."
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml23(title)
+msgid "To set up a migration for an extension"
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml25(para)
+msgid ""
+"Create a directory structure where <literal>my_extension</literal> is the "
+"name of the extension, as follows: "
+"<filename>keystone/contrib/my_extension/migrate_repo/versions/</filename>."
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml31(para)
+msgid ""
+"Create empty <filename>__init__.py</filename> files in the "
+"<filename>migrate_repo</filename> and <filename>versions</filename> "
+"subdirectories."
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml37(para)
+msgid ""
+"Create a <filename>migrate.cfg</filename> configuration file in the "
+"<filename>migrate_repo</filename> subdirectory, which conforms to a "
+"key/value <filename>.ini</filename> file format."
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml41(para)
+msgid "An example configuration file:"
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml49(title)
+msgid "To test a migration for a specific extension"
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml50(para)
+msgid ""
+"You can use the <placeholder-1/> command with the "
+"<parameter>--extension</parameter> parameter for both the <placeholder-2/> "
+"and <placeholder-3/> commands. Ensure that the required configuration files "
+"exist before completing these steps."
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml57(para)
+msgid "Test your migrations with an <literal>example</literal> extension:"
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml62(para)
+msgid "Migrate to version 1:"
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml66(para)
+msgid "Migrate back to version 0:"
+msgstr ""
+
+#: ./doc/common/section_keystone_db_sync.xml70(para)
+msgid "Check the version:"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml9(title)
+msgid "Troubleshoot Compute"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml10(para)
+msgid ""
+"Common problems for Compute typically involve misconfigured networking or "
+"credentials that are not sourced properly in the environment. Also, most "
+"flat networking configurations do not enable <placeholder-1/> or "
+"<placeholder-2/> from a compute node to the instances that run on that node."
+" Another common problem is trying to run 32-bit images on a 64-bit compute "
+"node. This section shows you how to troubleshoot Compute."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml19(title)
+msgid "Compute service logging"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml20(para)
+msgid ""
+"Compute stores a log file for each service in "
+"<filename>/var/log/nova</filename>. For example, <filename>nova-"
+"compute.log</filename> is the log for the <systemitem class=\"service"
+"\">nova-compute</systemitem> service. You can set the following options to "
+"format log strings for the nova.log module in the "
+"<filename>nova.conf</filename> file:"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml29(literal)
+msgid "logging_context_format_string"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml32(literal)
+msgid "logging_default_format_string"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml35(para)
+msgid ""
+"If the log level is set to <literal>debug</literal>, you can also specify "
+"<literal>logging_debug_format_suffix</literal> to append extra formatting. "
+"For information about what variables are available for the formatter see: "
+"<link "
+"href=\"http://docs.python.org/library/logging.html#formatter\">http://docs.python.org/library/logging.html#formatter</link>."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml42(para)
+msgid ""
+"You have two options for logging for OpenStack Compute based on "
+"configuration settings. In <filename>nova.conf</filename>, include the "
+"<literal>logfile</literal> option to enable logging. Alternatively you can "
+"set <literal>use_syslog = 1</literal> so that the nova daemon logs to "
+"syslog."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml50(title)
+msgid "Guru Meditation reports"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml51(para)
+msgid ""
+"A Guru Meditation report is sent by the Compute Service upon receipt of the "
+"<systemitem>SIGUSR1</systemitem> signal. This report is a general-purpose "
+"error report, including a complete report of the service's current state, "
+"and is sent to <systemitem>stderr</systemitem>."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml55(para)
+msgid ""
+"For example, if you redirect error output to <filename>nova-api-"
+"err.log</filename> using <placeholder-1/>, resulting in the process ID 8675,"
+" you can then run:"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml59(para)
+msgid ""
+"This command triggers the Guru Meditation report to be printed to "
+"<filename>/var/log/nova/nova-api-err.log</filename>."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml63(para)
+msgid ""
+"Package Displays information about the package to which the process belongs,"
+" including version information."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml65(para)
+msgid ""
+"Threads Displays stack traces and thread IDs for each of the threads within "
+"the process."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml67(para)
+msgid ""
+"Green Threads Displays stack traces for each of the green threads within the"
+" process (green threads do not have thread IDs)."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml69(para)
+msgid ""
+"Configuration Lists all configuration options currently accessible through "
+"the CONF object for the current process."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml61(para)
+msgid "The report has the following sections: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml72(para)
+msgid ""
+"For more information, see <link "
+"href=\"http://docs.openstack.org/developer/nova/devref/gmr.html\">Guru "
+"Meditation Reports</link>."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml77(title)
+msgid "Common errors and fixes for Compute"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml78(para)
+msgid ""
+"The <link href=\"ask.openstack.org\">ask.openstack.org</link> site offers a "
+"place to ask and answer questions, and you can also mark questions as "
+"frequently asked questions. This section describes some errors people have "
+"posted previously. Bugs are constantly being fixed, so online resources are "
+"a great way to get the most up-to-date errors and fixes."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml86(title)
+msgid "Credential errors, 401, and 403 forbidden errors"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml93(para)
+msgid ""
+"<emphasis role=\"bold\">Manual method</emphasis>. Get get the "
+"<filename>novarc</filename> file from the project ZIP file, save existing "
+"credentials in case of override. and manually source the "
+"<filename>novarc</filename> file."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml103(para)
+msgid ""
+"<emphasis role=\"bold\">Script method</emphasis>. Generates "
+"<filename>novarc</filename> from the project ZIP file and sources it for "
+"you."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml88(para)
+msgid ""
+"Missing credentials cause a "
+"<errorcode>403</errorcode><errortext>forbidden</errortext> error. To resolve"
+" this issue, use one of these methods:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml110(para)
+msgid ""
+"When you run <systemitem class=\"service\">nova-api</systemitem> the first "
+"time, it generates the certificate authority information, including "
+"<filename>openssl.cnf</filename>. If you start the CA services before this, "
+"you might not be able to create your ZIP file. Restart the services. When "
+"your CA information is available, create your ZIP file."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml118(para)
+msgid ""
+"Also, check your HTTP proxy settings to see whether they cause problems with"
+" <filename>novarc</filename> creation."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml123(title)
+msgid "Instance errors"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml124(para)
+msgid ""
+"Sometimes a particular instance shows <literal>pending</literal> or you "
+"cannot SSH to it. Sometimes the image itself is the problem. For example, "
+"when you use flat manager networking, you do not have a DHCP server and "
+"certain images do not support interface injection; you cannot connect to "
+"them. The fix for this problem is to use an image that does support this "
+"method, such as Ubuntu, which obtains an IP address correctly with "
+"FlatManager network settings."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml134(para)
+msgid ""
+"To troubleshoot other possible problems with an instance, such as an "
+"instance that stays in a spawning state, check the directory for the "
+"particular instance under <filename>/var/lib/nova/instances</filename> on "
+"the <systemitem class=\"service\">nova-compute</systemitem> host and make "
+"sure that these files are present:"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml143(filename)
+msgid "libvirt.xml"
+msgstr "libvirt.xml"
+
+#: ./doc/common/section_support-compute.xml146(filename)
+msgid "disk"
+msgstr "disk"
+
+#: ./doc/common/section_support-compute.xml149(filename)
+msgid "disk-raw"
+msgstr "disk-raw"
+
+#: ./doc/common/section_support-compute.xml152(filename)
+msgid "kernel"
+msgstr "kernel"
+
+#: ./doc/common/section_support-compute.xml155(filename)
+msgid "ramdisk"
+msgstr "ramdisk"
+
+#: ./doc/common/section_support-compute.xml158(para)
+msgid "After the instance starts, <filename>console.log</filename>"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml162(para)
+msgid ""
+"If any files are missing, empty, or very small, the <systemitem "
+"class=\"service\">nova-compute</systemitem> service did not successfully "
+"download the images from the Image Service."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml167(para)
+msgid ""
+"Also check <filename>nova-compute.log</filename> for exceptions. Sometimes "
+"they do not appear in the console output."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml170(para)
+msgid ""
+"Next, check the log file for the instance in the "
+"<filename>/var/log/libvirt/qemu</filename> directory to see if it exists and"
+" has any useful error messages in it."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml174(para)
+msgid ""
+"Finally, from the <filename>/var/lib/nova/instances</filename> directory for"
+" the instance, see if this command returns an error:"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml181(title)
+msgid "Empty log output for Linux instances"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml182(para)
+msgid ""
+"You can view the log output of running instances from either the "
+"<guilabel>Log</guilabel> tab of the dashboard or the output of "
+"<placeholder-1/>. In some cases, the log output of a running Linux instance "
+"will be empty or only display a single character (for example, the "
+"<keycap>?</keycap> character)."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml189(para)
+msgid ""
+"This occurs when the Compute service attempts to retrieve the log output of "
+"the instance via a serial console while the instance itself is not "
+"configured to send output to the console. To rectify this, append the "
+"following parameters to kernel arguments specified in the instance's boot "
+"loader:"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml196(para)
+msgid ""
+"Upon rebooting, the instance will be configured to send output to the "
+"Compute service."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml201(title)
+msgid "Reset the state of an instance"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml202(para)
+msgid ""
+"If an instance remains in an intermediate state, such as "
+"<literal>deleting</literal>, you can use the <placeholder-1/> command to "
+"manually reset the state of an instance to an error state. You can then "
+"delete the instance. For example:"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml209(para)
+msgid ""
+"You can also use the <parameter>--active</parameter> parameter to force the "
+"instance back to an active state instead of an error state. For example:"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml215(title)
+msgid "Injection problems"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml216(para)
+msgid ""
+"If instances do not boot or boot slowly, investigate file injection as a "
+"cause."
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml218(para)
+msgid ""
+"To disable injection in libvirt, set the following in "
+"<filename>nova.conf</filename>:"
+msgstr ""
+
+#: ./doc/common/section_support-compute.xml223(para)
+msgid ""
+"If you have not enabled the configuration drive and you want to make user-"
+"specified files available from the metadata server for to improve "
+"performance and avoid boot failure if injection fails, you must disable "
+"injection."
 msgstr ""
 
 #: ./doc/common/section_getstart_telemetry.xml5(title)
@@ -11084,187 +11071,2361 @@ msgid ""
 "collector and API server have access to the data store."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml6(title)
-msgid "Install XenServer and XCP"
+#: ./doc/common/section_cli_cinder_read-only-volumes.xml6(title)
+msgid "Set a volume to read-only access"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml8(para)
+#: ./doc/common/section_cli_cinder_read-only-volumes.xml7(para)
 msgid ""
-"Before you can run OpenStack with XCP or XenServer, you must install the "
-"software on <link "
-"href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/installation.html#sys_requirements\">an"
-" appropriate server</link>."
+"To give multiple users shared, secure access to the same data, you can set a"
+" volume to read-only access."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml13(para)
+#: ./doc/common/section_cli_cinder_read-only-volumes.xml9(para)
+msgid "Run the following command to set a volume to read-only access:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_read-only-volumes.xml11(replaceable)
+msgid "VOLUME"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_read-only-volumes.xml11(replaceable)
+msgid "BOOLEAN"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_read-only-volumes.xml12(para)
 msgid ""
-"Xen is a type 1 hypervisor: When your server starts, Xen is the first "
-"software that runs. Consequently, you must install XenServer or XCP before "
-"you install the operating system where you want to run OpenStack code. The "
-"OpenStack services then run in a virtual machine that you install on top of "
-"XenServer."
+"<replaceable>VOLUME</replaceable> is the ID of the target volume and "
+"<replaceable>BOOLEAN</replaceable> is a flag that enables read-only or "
+"read/write access to the volume."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml20(para)
+#: ./doc/common/section_cli_cinder_read-only-volumes.xml15(para)
+msgid "The following values for <replaceable>BOOLEAN</replaceable> are valid:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_read-only-volumes.xml19(para)
 msgid ""
-"Before you can install your system, decide whether to install a free or paid"
-" edition of Citrix XenServer or Xen Cloud Platform from Xen.org. Download "
-"the software from these locations:"
+"<literal>true</literal>. Sets the read-only flag in the volume. When you "
+"attach the volume to an instance, the instance checks for this flag to "
+"determine whether to restrict volume access to read-only."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml28(link)
-msgid "http://www.citrix.com/XenServer/download"
-msgstr "http://www.citrix.com/XenServer/download"
+#: ./doc/common/section_cli_cinder_read-only-volumes.xml25(para)
+msgid "<literal>false</literal>. Sets the volume to read/write access."
+msgstr ""
 
-#: ./doc/common/section_xen-install.xml33(link)
-msgid "http://www.xen.org/download/xcp/index.html"
-msgstr "http://www.xen.org/download/xcp/index.html"
+#: ./doc/common/section_compute-configure-ec2.xml6(title)
+msgid "Configure the EC2 API"
+msgstr ""
 
-#: ./doc/common/section_xen-install.xml36(para)
+#: ./doc/common/section_compute-configure-ec2.xml7(para)
 msgid ""
-"When you install many servers, you might find it easier to perform <link "
-"href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/installation.html#pxe_boot_install\">PXE"
-" boot installations of XenServer or XCP</link>. You can also package any "
-"post-installation changes that you want to make to your XenServer by <link "
-"href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/supplemental_pack_ddk.html\">creating"
-" your own XenServer supplemental pack</link>."
+"You can set options in the <filename>nova.conf</filename> configuration file"
+" to control which network address and port the EC2 API listens on, the "
+"formatting of some API responses, and authentication related options."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml46(para)
+#: ./doc/common/section_compute-configure-ec2.xml11(para)
 msgid ""
-"You can also install the <package>xcp-xenapi</package> package on Debian-"
-"based distributions to get XCP. However, this is not as mature or feature "
-"complete as above distributions. This modifies your boot loader to first "
-"boot Xen and boot your existing OS on top of Xen as Dom0. The xapi daemon "
-"runs in Dom0. Find more details at <link "
-"href=\"http://wiki.xen.org/wiki/Project_Kronos\">http://wiki.xen.org/wiki/Project_Kronos</link>."
+"To customize these options for OpenStack EC2 API, use the configuration "
+"option settings documented in <xref linkend=\"config_table_nova_ec2\"/>."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml55(para)
+#: ./doc/common/section_cli_keystone_credentials.xml6(title)
+msgid "Set up credentials for the keystone client"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_credentials.xml7(para)
 msgid ""
-"Make sure you use the EXT type of storage repository (SR). Features that "
-"require access to VHD files (such as copy on write, snapshot and migration) "
-"do not work when you use the LVM SR. Storage repository (SR) is a XenAPI-"
-"specific term relating to the physical storage where virtual disks are "
-"stored."
+"You can configure the <package>python-keystoneclient</package> with admin "
+"credentials with either an authentication token or a user name and password."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml61(para)
+#: ./doc/common/section_cli_keystone_credentials.xml12(title)
+msgid "To configure the keystone client with an authentication token"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_credentials.xml15(para)
 msgid ""
-"On the XenServer/XCP installation screen, choose the <guilabel>XenDesktop "
-"Optimized</guilabel> option. If you use an answer file, make sure you use "
-"<literal>srtype=\"ext\"</literal> in the <option>installation</option> tag "
-"of the answer file."
+"Export your keystone endpoint to the <varname>OS_SERVICE_ENDPOINT</varname> "
+"environment variable:"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml69(title)
-msgid "Post-installation steps"
-msgstr ""
-
-#: ./doc/common/section_xen-install.xml70(para)
-msgid "Complete these steps to install OpenStack in your XenServer system:"
-msgstr ""
-
-#: ./doc/common/section_xen-install.xml74(para)
+#: ./doc/common/section_cli_keystone_credentials.xml21(para)
 msgid ""
-"For resize and migrate functionality, complete the changes described in the "
-"<citetitle>Configure resize</citetitle> section in the <link href"
-"=\"../config-reference/content/index.html\"><citetitle>OpenStack "
-"Configuration Reference</citetitle></link>."
+"Export the administrator service token to the "
+"<varname>OS_SERVICE_TOKEN</varname> environment variable:"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml82(para)
+#: ./doc/common/section_cli_keystone_credentials.xml26(para)
+#: ./doc/common/section_cli_keystone_credentials.xml80(para)
 msgid ""
-"Install the VIF isolation rules to help prevent mac and IP address spoofing."
+"Alternatively, you can specify these parameters on any keystone client "
+"command:"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml86(para)
-msgid "Install the XenAPI plug-ins. See the following section."
-msgstr ""
-
-#: ./doc/common/section_xen-install.xml90(para)
+#: ./doc/common/section_cli_keystone_credentials.xml30(para)
 msgid ""
-"To support AMI type images, you must set up <literal>/boot/guest</literal> "
-"symlink/directory in Dom0. For detailed instructions, see next section."
+"<parameter>--os-endpoint "
+"<replaceable>SERVICE_ENDPOINT</replaceable></parameter>. An endpoint to use "
+"instead of the one in the service catalog. Defaults to "
+"<code>env[OS_SERVICE_ENDPOINT]</code>."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml96(para)
+#: ./doc/common/section_cli_keystone_credentials.xml39(para)
 msgid ""
-"To support resize/migration, set up an ssh trust relation between your "
-"XenServer hosts, and ensure <literal>/images</literal> is properly set up. "
-"See next section for more details."
+"<parameter>--os-token <replaceable>SERVICE_TOKEN</replaceable></parameter>. "
+"An existing token to use instead of the one generated by authentication. "
+"Defaults to <code>env[OS_SERVICE_TOKEN]</code>."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml102(para)
+#: ./doc/common/section_cli_keystone_credentials.xml52(title)
+msgid "To configure the keystone client with a user name and password"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_credentials.xml55(para)
 msgid ""
-"Create a Paravirtualized virtual machine that can run the OpenStack compute "
-"code."
+"Export the administrator user name to the <varname>OS_USERNAME</varname> "
+"environment variable:"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml106(para)
+#: ./doc/common/section_cli_keystone_credentials.xml61(para)
 msgid ""
-"Install and configure the <systemitem class=\"service\">nova-"
-"compute</systemitem> in the above virtual machine."
+"Export the administrator password to the <varname>OS_PASSWORD</varname> "
+"environment variable:"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml111(para)
+#: ./doc/common/section_cli_keystone_credentials.xml67(para)
 msgid ""
-"For more information, see how DevStack performs the last three steps for "
-"developer deployments. For more information about DevStack, see "
-"<citetitle>Getting Started With XenServer and Devstack</citetitle> (<link "
-"href=\"https://github.com/openstack-"
-"dev/devstack/blob/master/tools/xen/README.md\">https://github.com/openstack-"
-"dev/devstack/blob/master/tools/xen/README.md</link>). Find more information "
-"about the first step, see <citetitle>Multi Tenancy Networking Protections in"
-" XenServer</citetitle> (<link "
-"href=\"https://github.com/openstack/nova/blob/master/plugins/xenserver/doc/networking.rst\">https://github.com/openstack/nova/blob/master/plugins/xenserver/doc/networking.rst</link>)."
-" For information about how to install the XenAPI plug-ins, see "
-"<citetitle>XenAPI README</citetitle> (<link "
-"href=\"https://github.com/openstack/nova/blob/master/plugins/xenserver/xenapi/README\">https://github.com/openstack/nova/blob/master/plugins/xenserver/xenapi/README</link>)."
+"Export the tenant name to the <varname>OS_TENANT_NAME</varname> environment "
+"variable:"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml131(title)
-msgid "Xen boot from ISO"
-msgstr ""
-
-#: ./doc/common/section_xen-install.xml132(para)
+#: ./doc/common/section_cli_keystone_credentials.xml73(para)
 msgid ""
-"XenServer, through the XenAPI integration with OpenStack, provides a feature"
-" to boot instances from an ISO file. To activate the Boot From ISO feature, "
-"you must configure the SR elements on XenServer host, as follows:"
+"Export the URL of the keystone auth server, for example <link "
+"href=\"http://localhost:5000/v2.0'\">http://localhost:5000/v2.0'</link>, to "
+"the <varname>OS_AUTH_URL</varname> environment variable:"
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml139(para)
+#: ./doc/common/section_cli_keystone_credentials.xml84(para)
 msgid ""
-"Create an ISO-typed SR, such as an NFS ISO library, for instance. For this, "
-"using XenCenter is a simple method. You must export an NFS volume from a "
-"remote NFS server. Make sure it is exported in read-write mode."
+"<literal>--os-username <replaceable>OS_USERNAME</replaceable></literal>. "
+"Name used for authentication with the Identity Service. Defaults to "
+"<code>env[OS_USERNAME]</code>."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml146(para)
-msgid "On the compute host, find and record the uuid of this ISO SR:"
-msgstr ""
-
-#: ./doc/common/section_xen-install.xml151(para)
-msgid "Locate the uuid of the NFS ISO library:"
-msgstr ""
-
-#: ./doc/common/section_xen-install.xml155(para)
+#: ./doc/common/section_cli_keystone_credentials.xml92(para)
 msgid ""
-"Set the uuid and configuration. Even if an NFS mount point is not local, you"
-" must specify <literal>local-storage-iso</literal>."
+"<literal>--os-password <replaceable>OS_PASSWORD</replaceable></literal>. "
+"Password used for authentication with the Identity Service. Defaults to "
+"<code>env[OS_PASSWORD]</code>."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml161(para)
+#: ./doc/common/section_cli_keystone_credentials.xml100(para)
 msgid ""
-"Make sure the host-uuid from <literal>xe pbd-list</literal> equals the uuid "
-"of the host you found previously:"
+"<literal>--os-tenant_name "
+"<replaceable>OS_TENANT_NAME</replaceable></literal>. Tenant for which to "
+"request authentication. Defaults to <code>env[OS_TENANT_NAME]</code>."
 msgstr ""
 
-#: ./doc/common/section_xen-install.xml167(para)
+#: ./doc/common/section_cli_keystone_credentials.xml108(para)
 msgid ""
-"You can now add images through the OpenStack Image Service with <literal"
-">disk-format=iso</literal>, and boot them in OpenStack Compute:"
+"<literal>--os-auth_url <replaceable>OS_AUTH_URL</replaceable></literal>. The"
+" Identity Service endpoint to use for authentication. Defaults to "
+"<code>env[OS_AUTH_URL]</code>."
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_compute-configure-vnc.xml63(None)
+msgid ""
+"@@image: '../common/figures/novnc/SCH_5009_V00_NUAC-VNC_OpenStack.png'; "
+"md5=182dc38019a220c851e1c94aa50f4565"
+msgstr "@@image: '../common/figures/novnc/SCH_5009_V00_NUAC-VNC_OpenStack.png'; md5=182dc38019a220c851e1c94aa50f4565"
+
+#: ./doc/common/section_compute-configure-vnc.xml6(title)
+msgid "VNC console proxy"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml7(para)
+msgid ""
+"The VNC proxy is an OpenStack component that enables compute service users "
+"to access their instances through VNC clients."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml10(para)
+msgid "The VNC console connection works as follows:"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml13(para)
+msgid ""
+"A user connects to the API and gets an <literal>access_url</literal> such "
+"as, <literal>http://<replaceable>ip:port</replaceable>/?token=xyz</literal>."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml19(para)
+msgid "The user pastes the URL in a browser or uses it as a client parameter."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml23(para)
+msgid "The browser or client connects to the proxy."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml26(para)
+msgid ""
+"The proxy talks to <systemitem class=\"service\">nova-"
+"consoleauth</systemitem> to authorize the token for the user, and maps the "
+"token to the <emphasis>private</emphasis> host and port of the VNC server "
+"for an instance."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml31(para)
+msgid ""
+"The compute host specifies the address that the proxy should use to connect "
+"through the <filename>nova.conf</filename> file option, "
+"<option>vncserver_proxyclient_address</option>. In this way, the VNC proxy "
+"works as a bridge between the public network and private host network."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml39(para)
+msgid ""
+"The proxy initiates the connection to VNC server and continues to proxy "
+"until the session ends."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml43(para)
+msgid ""
+"The proxy also tunnels the VNC protocol over WebSockets so that the "
+"<systemitem>noVNC</systemitem> client can talk to VNC servers. In general, "
+"the VNC proxy:"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml48(para)
+msgid ""
+"Bridges between the public network where the clients live and the private "
+"network where VNC servers live."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml52(para)
+msgid "Mediates token authentication."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml55(para)
+msgid ""
+"Transparently deals with hypervisor-specific connection details to provide a"
+" uniform client experience."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml58(title)
+msgid "noVNC process"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml71(title)
+msgid "About nova-consoleauth"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml73(para)
+msgid ""
+"Both client proxies leverage a shared service to manage token authentication"
+" called <systemitem class=\"service\">nova-consoleauth</systemitem>. This "
+"service must be running for either proxy to work. Many proxies of either "
+"type can be run against a single <systemitem class=\"service\">nova-"
+"consoleauth</systemitem> service in a cluster configuration."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml80(para)
+msgid ""
+"Do not confuse the <systemitem class=\"service\">nova-"
+"consoleauth</systemitem> shared service with <literal>nova-"
+"console</literal>, which is a XenAPI-specific service that most recent VNC "
+"proxy architectures do not use."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml87(title)
+msgid "Typical deployment"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml88(para)
+msgid "A typical deployment has the following components:"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml91(para)
+msgid ""
+"A <systemitem class=\"service\">nova-consoleauth</systemitem> process. "
+"Typically runs on the controller host."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml96(para)
+msgid ""
+"One or more <systemitem class=\"service\">nova-novncproxy</systemitem> "
+"services. Supports browser-based noVNC clients. For simple deployments, this"
+" service typically runs on the same machine as <systemitem class=\"service"
+"\">nova-api</systemitem> because it operates as a proxy between the public "
+"network and the private compute host network."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml105(para)
+msgid ""
+"One or more <literal>nova-xvpvncproxy</literal> services. Supports the "
+"special Java client discussed here. For simple deployments, this service "
+"typically runs on the same machine as <systemitem class=\"service\">nova-"
+"api</systemitem> because it acts as a proxy between the public network and "
+"the private compute host network."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml114(para)
+msgid ""
+"One or more compute hosts. These compute hosts must have correctly "
+"configured options, as follows."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml120(title)
+msgid "VNC configuration options"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml121(para)
+msgid "To customize the VNC console, use the following configuration options:"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml124(para)
+msgid ""
+"To support <link href=\"http://docs.openstack.org/trunk/config-"
+"reference/content/configuring-openstack-compute-basics.html"
+"#section_configuring-compute-migrations\">live migration</link>, you cannot "
+"specify a specific IP address for <literal>vncserver_listen</literal>, "
+"because that IP address does not exist on the destination host."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml134(para)
+msgid ""
+"The <literal>vncserver_proxyclient_address</literal> defaults to "
+"<literal>127.0.0.1</literal>, which is the address of the compute host that "
+"Compute instructs proxies to use when connecting to instance servers."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml139(para)
+msgid "For all-in-one XenServer domU deployments, set this to 169.254.0.1."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml140(para)
+msgid ""
+"For multi-host XenServer domU deployments, set to a dom0 management IP on "
+"the same network as the proxies."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml142(para)
+msgid ""
+"For multi-host libvirt deployments, set to a host management IP on the same "
+"network as the proxies."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml150(title)
+msgid "nova-novncproxy (noVNC)"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml152(para)
+msgid ""
+"You must install the <package>noVNC</package> package, which contains the "
+"<systemitem class=\"service\">nova-novncproxy</systemitem> service. As root,"
+" run the following command:"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml156(para)
+msgid "The service starts automatically on installation."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml157(para)
+msgid "To restart the service, run:"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml159(para)
+msgid ""
+"The configuration option parameter should point to your "
+"<filename>nova.conf</filename> file, which includes the message queue server"
+" address and credentials."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml162(para)
+msgid ""
+"By default, <systemitem class=\"service\">nova-novncproxy</systemitem> binds"
+" on <literal>0.0.0.0:6080</literal>."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml165(para)
+msgid ""
+"To connect the service to your Compute deployment, add the following "
+"configuration options to your <filename>nova.conf</filename> file:"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml169(para)
+msgid "<literal>vncserver_listen</literal>=<replaceable>0.0.0.0</replaceable>"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml172(para)
+msgid ""
+"Specifies the address on which the VNC service should bind. Make sure it is "
+"assigned one of the compute node interfaces. This address is the one used by"
+" your domain file."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml178(para)
+msgid ""
+"To use live migration, use the <replaceable>0.0.0.0</replaceable> address."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml183(para)
+msgid ""
+"<literal>vncserver_proxyclient_address</literal>=<replaceable>127.0.0.1</replaceable>"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml186(para)
+msgid ""
+"The address of the compute host that Compute instructs proxies to use when "
+"connecting to instance <literal>vncservers</literal>."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml193(title)
+msgid "Frequently asked questions about VNC access to virtual machines"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml199(literal)
+msgid "nova-xvpvncproxy"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml200(systemitem)
+msgid "nova-novncproxy"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml198(emphasis)
+msgid ""
+"Q: What is the difference between <placeholder-1/> and <placeholder-2/>?"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml202(para)
+msgid ""
+"A: <literal>nova-xvpvncproxy</literal>, which ships with OpenStack Compute, "
+"is a proxy that supports a simple Java client. <systemitem class=\"service"
+"\">nova-novncproxy</systemitem> uses noVNC to provide VNC support through a "
+"web browser."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml208(emphasis)
+msgid ""
+"Q: I want VNC support in the OpenStack dashboard. What services do I need?"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml210(para)
+msgid ""
+"A: You need <systemitem class=\"service\">nova-novncproxy</systemitem>, "
+"<systemitem class=\"service\">nova-consoleauth</systemitem>, and correctly "
+"configured compute hosts."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml216(emphasis)
+msgid ""
+"Q: When I use <placeholder-1/> or click on the VNC tab of the OpenStack "
+"dashboard, it hangs. Why?"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml218(para)
+msgid ""
+"A: Make sure you are running <systemitem class=\"service\">nova-"
+"consoleauth</systemitem> (in addition to <systemitem class=\"service\">nova-"
+"novncproxy</systemitem>). The proxies rely on <systemitem class=\"service"
+"\">nova-consoleauth</systemitem> to validate tokens, and waits for a reply "
+"from them until a timeout is reached."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml227(emphasis)
+msgid ""
+"Q: My VNC proxy worked fine during my all-in-one test, but now it doesn't "
+"work on multi host. Why?"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml230(para)
+msgid ""
+"A: The default options work for an all-in-one install, but changes must be "
+"made on your compute hosts once you start to build a cluster. As an example,"
+" suppose you have two servers:"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml236(para)
+msgid ""
+"Your <systemitem class=\"service\">nova-compute</systemitem> configuration "
+"file must set the following values:"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml248(para)
+msgid ""
+"<literal>novncproxy_base_url</literal> and "
+"<literal>xvpvncproxy_base_url</literal> use a public IP; this is the URL "
+"that is ultimately returned to clients, which generally do not have access "
+"to your private network. Your PROXYSERVER must be able to reach "
+"<literal>vncserver_proxyclient_address</literal>, because that is the "
+"address over which the VNC connection is proxied."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml260(emphasis)
+msgid "Q: My noVNC does not work with recent versions of web browsers. Why?"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml263(para)
+msgid ""
+"A: Make sure you have installed <literal>python-numpy</literal>, which is "
+"required to support a newer version of the WebSocket protocol (HyBi-07+)."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml270(emphasis)
+msgid ""
+"Q: How do I adjust the dimensions of the VNC window image in the OpenStack "
+"dashboard?"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml273(para)
+msgid ""
+"A: These values are hard-coded in a Django HTML template. To alter them, "
+"edit the <filename>_detail_vnc.html</filename> template file. The location "
+"of this file varies based on Linux distribution. On Ubuntu 12.04, the file "
+"is at "
+"<filename>/usr/share/pyshared/horizon/dashboards/nova/instances/templates/instances/_detail_vnc.html</filename>."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-vnc.xml279(para)
+msgid ""
+"Modify the <option>width</option> and <option>height</option> options, as "
+"follows:"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml11(title)
+msgid "Image Service command-line client"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml12(para)
+msgid ""
+"The <placeholder-1/> client is the command-line interface (CLI) for the "
+"OpenStack Image Service API and its extensions. This chapter documents "
+"<placeholder-2/> version 0.12.0."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml22(title)
+msgid "glance usage"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml43(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use image-create instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml52(emphasis)
+#: ./doc/common/ch_cli_glance_commands.xml180(emphasis)
+msgid "DEPRECATED!"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml59(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use image-delete instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml67(para)
+#: ./doc/common/ch_cli_glance_commands.xml131(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use image-list instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml75(para)
+#: ./doc/common/ch_cli_glance_commands.xml524(para)
+msgid "Create a new image."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml91(para)
+msgid "Download a specific image."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml99(para)
+#: ./doc/common/ch_cli_glance_commands.xml715(para)
+msgid "List images you can access."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml107(para)
+#: ./doc/common/ch_cli_glance_commands.xml163(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use member-list instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml115(para)
+#: ./doc/common/ch_cli_glance_commands.xml848(para)
+msgid "Describe a specific image."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml123(para)
+#: ./doc/common/ch_cli_glance_commands.xml886(para)
+msgid "Update a specific image."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml139(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use member-create instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml147(para)
+#: ./doc/common/ch_cli_glance_commands.xml1057(para)
+msgid "Share a specific image with a tenant."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml155(para)
+#: ./doc/common/ch_cli_glance_commands.xml1093(para)
+msgid "Remove a shared image from a tenant."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml171(para)
+#: ./doc/common/ch_cli_glance_commands.xml1118(para)
+msgid "Describe sharing permissions by image or tenant."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml187(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use image-show instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml195(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use image-update instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml212(title)
+msgid "glance optional arguments"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml225(para)
+msgid "Defaults to <code>env[GLANCECLIENT_DEBUG]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml233(para)
+msgid "Print more verbose output"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml241(para)
+msgid ""
+"Force retrieving the schema used to generate portions of the help text "
+"rather than using a cached copy. Ignored with api version 1"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml251(para)
+msgid ""
+"Explicitly allow glanceclient to perform \"insecure SSL\" (https) requests. "
+"The server's certificate will not be verified against any certificate "
+"authorities. This option should be used with caution."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml272(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml321(para)
+msgid ""
+"Path of client key to use in SSL connection. This option is not necessary if"
+" your key is prepended to your cert file."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml282(para)
+msgid ""
+"Path of CA TLS certificate(s) used to verify the remote server's "
+"certificate. Without this option glance looks for the default system CA "
+"certificates."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml292(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml341(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use --os-cacert."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml300(para)
+msgid "Number of seconds to wait for a response"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml308(para)
+msgid "Disable SSL compression when using https."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml316(para)
+msgid "Prevent select actions from requesting user confirmation."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml325(para)
+msgid ""
+"<emphasis>DEPRECATED!</emphasis> Only used for deprecated legacy commands."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml333(para)
+#: ./doc/common/ch_cli_glance_commands.xml342(para)
+#: ./doc/common/ch_cli_glance_commands.xml351(para)
+msgid ""
+"<emphasis>DEPRECATED!</emphasis> Send a fully-formed endpoint using --os- "
+"image-url instead."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml360(para)
+msgid "Defaults to <code>env[OS_USERNAME]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml368(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use --os-username."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml376(para)
+msgid "Defaults to <code>env[OS_PASSWORD]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml384(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use --os-password."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml392(para)
+msgid "Defaults to <code>env[OS_TENANT_ID]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml400(para)
+msgid "Defaults to <code>env[OS_TENANT_NAME]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml408(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use --os-tenant-name."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml416(para)
+msgid "Defaults to <code>env[OS_AUTH_URL]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml424(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use --os-auth-url."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml432(para)
+msgid "Defaults to <code>env[OS_REGION_NAME]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml440(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use --os-region-name."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml456(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use --os-auth-token."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml464(para)
+msgid "Defaults to <code>env[OS_IMAGE_URL]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml472(para)
+msgid "<emphasis>DEPRECATED!</emphasis> Use --os-image-url."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml480(para)
+msgid "Defaults to <code>env[OS_IMAGE_API_VERSION]</code> or 1"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml488(para)
+msgid "Defaults to <code>env[OS_SERVICE_TYPE]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml496(para)
+msgid "Defaults to <code>env[OS_ENDPOINT_TYPE]</code>"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml504(para)
+msgid "<emphasis>DEPRECATED!</emphasis> This option is completely ignored."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml512(title)
+msgid "glance image-create command"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml531(para)
+msgid "of image to reserve."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml539(para)
+#: ./doc/common/ch_cli_glance_commands.xml904(para)
+msgid "Name of image."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml547(para)
+msgid "Store to upload image to."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml555(para)
+#: ./doc/common/ch_cli_glance_commands.xml912(para)
+msgid ""
+"Disk format of image. Acceptable formats: ami, ari, aki, vhd, vmdk, raw, "
+"qcow2, vdi, and iso."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml564(para)
+#: ./doc/common/ch_cli_glance_commands.xml921(para)
+msgid ""
+"Container format of image. Acceptable formats: ami, ari, aki, bare, and ovf."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml573(para)
+#: ./doc/common/ch_cli_glance_commands.xml930(para)
+msgid "Tenant who should own image."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml581(para)
+msgid ""
+"Size of image data (in bytes). Only used with '-- location' and '--"
+"copy_from'."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml590(para)
+#: ./doc/common/ch_cli_glance_commands.xml946(para)
+msgid "Minimum size of disk needed to boot image (in gigabytes)."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml599(para)
+#: ./doc/common/ch_cli_glance_commands.xml955(para)
+msgid "Minimum amount of ram needed to boot image (in megabytes)."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml608(para)
+#: ./doc/common/ch_cli_glance_commands.xml964(para)
+msgid ""
+"URL where the data for this image already resides. For example, if the image"
+" data is stored in swift, you could specify "
+"'swift://account:key@example.com/container/obj'."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml619(para)
+msgid ""
+"Local file that contains disk image to be uploaded during creation. "
+"Alternatively, images can be passed to the client via stdin."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml629(para)
+msgid ""
+"Hash of image data used Glance can use for verification. Provide a md5 "
+"checksum here."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml638(para)
+#: ./doc/common/ch_cli_glance_commands.xml994(para)
+msgid ""
+"Similar to '--location' in usage, but this indicates that the Glance server "
+"should immediately copy the data and store it in its configured image store."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml648(para)
+#: ./doc/common/ch_cli_glance_commands.xml1004(para)
+msgid "Make image accessible to the public."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml656(para)
+#: ./doc/common/ch_cli_glance_commands.xml1012(para)
+msgid "Prevent image from being deleted."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml664(para)
+#: ./doc/common/ch_cli_glance_commands.xml1020(para)
+msgid ""
+"Arbitrary property to associate with image. May be used multiple times."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml673(para)
+#: ./doc/common/ch_cli_glance_commands.xml790(para)
+#: ./doc/common/ch_cli_glance_commands.xml866(para)
+#: ./doc/common/ch_cli_glance_commands.xml1039(para)
+msgid "Print image size in a human-friendly format."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml681(para)
+#: ./doc/common/ch_cli_glance_commands.xml1047(para)
+msgid "Show upload progress bar."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml689(title)
+msgid "glance image-delete command"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml698(para)
+msgid "Name or ID of image(s) to delete."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml706(title)
+msgid "glance image-list command"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml722(para)
+msgid "Filter images to those that have this name."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml730(para)
+msgid "Filter images to those that have this status."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml738(para)
+msgid ""
+"Filter images to those that have this container format. Acceptable formats: "
+"ami, ari, aki, bare, and ovf."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml748(para)
+msgid ""
+"Filter images to those that have this disk format. Acceptable formats: ami, "
+"ari, aki, vhd, vmdk, raw, qcow2, vdi, and iso."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml758(para)
+msgid "Filter images to those with a size greater than this."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml766(para)
+msgid "Filter images to those with a size less than this."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml774(para)
+msgid "Filter images by a user-defined image property."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml782(para)
+msgid "Number of images to request in each paginated request."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml798(para)
+msgid "Sort image list by specified field."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml806(para)
+msgid "Sort image list in specified direction."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml814(para)
+msgid "Allows the user to select a listing of public or non public images."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml823(para)
+msgid ""
+"Display only images owned by this tenant id. Filtering occurs on the client "
+"side so may be inefficient. This option is mainly intended for admin use. "
+"Use an empty string ('') to list images with no owner. Note: This option "
+"overrides the --is-public argument if present. Note: the v2 API supports "
+"more efficient server-side owner based filtering."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml837(para)
+msgid ""
+"Allows the admin user to list all images irrespective of the image's owner "
+"or is_public value."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml846(title)
+msgid "glance image-show command"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml855(para)
+msgid "Name or ID of image to describe."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml874(title)
+msgid "glance image-update command"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml893(para)
+msgid "Name or ID of image to modify."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml938(para)
+msgid "Size of image data (in bytes)."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml975(para)
+msgid ""
+"Local file that contains disk image to be uploaded during update. "
+"Alternatively, images can be passed to the client via stdin."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml985(para)
+msgid "Hash of image data used Glance can use for verification."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml1029(para)
+msgid ""
+"If this flag is present, delete all image properties not explicitly set in "
+"the update request. Otherwise, those properties not referenced are "
+"preserved."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml1055(title)
+msgid "glance member-create command"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml1064(para)
+msgid "Image to add member to."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml1072(para)
+msgid "Tenant to add as member"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml1083(para)
+msgid "Allow the specified tenant to share this image."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml1091(title)
+msgid "glance member-delete command"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml1100(para)
+msgid "Image from which to remove member"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml1108(para)
+msgid "Tenant to remove as member"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml1116(title)
+msgid "glance member-list command"
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml1125(para)
+msgid "Filter results by an image ID."
+msgstr ""
+
+#: ./doc/common/ch_cli_glance_commands.xml1133(para)
+msgid "Filter results by a tenant ID."
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml106(None)
+msgid ""
+"@@image: 'figures/launch_instances.png'; "
+"md5=8a7e6864bce97f6478db572daf3ef5de"
+msgstr "@@image: 'figures/launch_instances.png'; md5=8a7e6864bce97f6478db572daf3ef5de"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml164(None)
+msgid "@@image: 'figures/instances.png'; md5=6b0f5cb3009d447334ff8b5c5b2cd121"
+msgstr "@@image: 'figures/instances.png'; md5=6b0f5cb3009d447334ff8b5c5b2cd121"
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml10(para)
+msgid ""
+"You can launch an instance directly from one of the available OpenStack "
+"images. The OpenStack Image Service provides a pool of images that are "
+"accessible to members of different projects. When you launch an instance "
+"from an image, OpenStack creates a local copy of the image on the respective"
+" compute node where the instance is started."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml16(para)
+msgid ""
+"Alternatively, you can launch an instance from an image that you have copied"
+" to a persistent volume."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml18(para)
+msgid "To launch an instance, specify the following parameters:"
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml22(para)
+msgid ""
+"The <guilabel>instance source</guilabel>, which is an image or snapshot. "
+"Alternatively, you can boot from a volume, which is block storage, to which "
+"you've copied an image or snapshot."
+msgstr "<guilabel>インスタンスソース</guilabel>。イメージまたはスナップショット。または、インスタンスまたはスナップショットをコピーしたブロックストレージ、つまりボリュームからブートすることができます。"
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml28(para)
+msgid ""
+"The <guilabel>image</guilabel> or <guilabel>snapshot</guilabel>, which "
+"represents the operating system."
+msgstr "<guilabel>イメージ</guilabel>または<guilabel>スナップショット</guilabel>。オペレーティングシステムを指します。"
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml33(para)
+msgid "A <guilabel>name</guilabel> for your instance."
+msgstr "インスタンスの<guilabel>名前</guilabel>。"
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml49(para)
+msgid ""
+"A <emphasis role=\"bold\">keypair</emphasis> for your instance, which are "
+"SSH credentials that are injected into images when they are launched. For "
+"this to work, the image must contain the <literal>cloud-init</literal> "
+"package. Create at least one keypair for each project. If you already have "
+"generated a keypair with an external tool, you can import it into OpenStack."
+" You can use the keypair for multiple instances that belong to that project."
+msgstr "インスタンスの<emphasis role=\"bold\">キーペア</emphasis>。イメージ起動時にイメージに注入される SSH 認証情報です。キーペアを機能させるには、イメージに <literal>cloud-init</literal> パッケージがインストールされている必要があります。プロジェクトごとにキーペアを最低でも 1 つ作成します。すでに外部のツールでキーペアを生成している場合は、OpenStack にそのキーペアをインポートすることができます。プロジェクトに所属する複数のインスタンスに対して、キーペアを使用することができます。"
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml62(para)
+msgid ""
+"A <emphasis role=\"bold\">security group</emphasis>, which defines which "
+"incoming network traffic is forwarded to instances. Security groups hold a "
+"set of firewall policies, known as <emphasis role=\"italic\">security group "
+"rules</emphasis>."
+msgstr "<emphasis role=\"bold\">セキュリティグループ</emphasis>。どの受信ネットワークトラフィックがインスタンスに転送されるのかを定義します。セキュリティグループは、<emphasis role=\"italic\">セキュリティグループルール</emphasis>と呼ばれるファイアウォールポリシーを保持しています。"
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml73(para)
+msgid ""
+"If needed, you can assign a <emphasis role=\"bold\">floating (public) IP "
+"address</emphasis> to a running instance and attach a block storage device, "
+"or volume, for persistent storage."
+msgstr "必要であれば、<emphasis role=\"bold\">Floating IP (パブリック IP) アドレス</emphasis>を実行中のインスタンスに割り当てて、永続ストレージにブロックストレージまたはボリュームを接続することができます。"
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml80(title)
+msgid "To launch an instance:"
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml82(para)
+msgid "Log in to the OpenStack dashboard."
+msgstr "OpenStack Dashboard にログインします。"
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml85(para)
+msgid ""
+"If you are a member of multiple projects, select a project from the drop-"
+"down list at the top of the <guilabel>Project</guilabel> tab."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml90(para)
+msgid "Click the <guilabel>Images &amp; Snapshot</guilabel> category."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml92(para)
+msgid ""
+"The dashboard shows the images that have been uploaded to OpenStack Image "
+"Service and are available for this project."
+msgstr "ダッシュボードは OpenStack Image Service にアップロードされ、このプロジェクトに利用可能なイメージを表示します。"
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml100(title)
+msgid "OpenStack dashboard - Launch Instances window"
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml97(para)
+msgid ""
+"Select an image and click <guibutton>Launch</guibutton>. The "
+"<guilabel>Launch Image</guilabel> window appears: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml112(para)
+msgid "Specify the following parameters:"
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml116(para)
+msgid "Enter an instance name to assign to the virtual machine."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml120(para)
+msgid ""
+"From the <guilabel>Flavor</guilabel> drop-down list, select the size of the "
+"virtual machine to launch."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml125(para)
+msgid "Optionally, select a keypair."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml126(para)
+msgid ""
+"In case an image uses a static root password or a static key set (neither is"
+" recommended), you do not need to provide a keypair on starting the "
+"instance."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml132(para)
+msgid ""
+"In <guilabel>Instance Count</guilabel>, enter the number of virtual machines"
+" to launch from this image."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml137(para)
+msgid ""
+"Assign the instance to the default security group. If you added rules to "
+"this group, the instance implements these rules."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml150(para)
+msgid ""
+"Click <guibutton>Launch Instance</guibutton>. The instance is launched on "
+"any of the compute nodes in the cloud."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml155(para)
+msgid ""
+"After you have launched an instance, switch to the <guilabel>Instances &amp;"
+" Volumes</guilabel> category to view the instance name, its (private or "
+"public) IP address, size, status, task, and power state."
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml160(title)
+msgid "OpenStack dashboard - Instances"
+msgstr ""
+
+#: ./doc/common/section_dashboard_launch_instances_from_image.xml168(para)
+msgid ""
+"If you did not provide a keypair on starting and have not touched security "
+"groups or rules so far, by default the instance can only be accessed from "
+"inside the cloud through VNC at this point. Even pinging the instance is not"
+" possible."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml6(title)
+msgid "Integrate Identity with LDAP"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml7(para)
+msgid ""
+"Identity Service supports integration with an existing LDAP directory for "
+"authentication and authorization services."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml11(para)
+msgid ""
+"For OpenStack Identity to access an LDAP back end, you must enable the "
+"<option>authlogin_nsswitch_use_ldap</option> boolean value for SELinux on "
+"the Identity server. To enable and make the option persistent across "
+"reboots:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml18(para)
+msgid "You can integrate Identity with a single LDAP server."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml21(para)
+msgid ""
+"To configure Identity, set options in the "
+"<filename>/etc/keystone/keystone.conf</filename> file. Modify these examples"
+" as needed."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml25(title)
+msgid "To integrate Identity with LDAP"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml27(para)
+msgid "Enable the LDAP driver in the <filename>keystone.conf</filename> file:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml34(para)
+msgid ""
+"Define the destination LDAP server in the <filename>keystone.conf</filename>"
+" file:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml45(para)
+msgid ""
+"Create the organizational units (OU) in the LDAP directory, and define their"
+" corresponding location in the <filename>keystone.conf</filename> file:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml58(para)
+msgid ""
+"These schema attributes are extensible for compatibility with various "
+"schemas. For example, this entry maps to the <systemitem>person</systemitem>"
+" attribute in Active Directory:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml67(para)
+msgid ""
+"A read-only implementation is recommended for LDAP integration. These "
+"permissions are applied to object types in the "
+"<filename>keystone.conf</filename> file:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml85(para)
+msgid "Restart the Identity service:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml87(para)
+msgid ""
+"During service restart, authentication and authorization are unavailable."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml92(title)
+msgid "Additional LDAP integration settings"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml93(para)
+msgid "Set these options in the <filename>keystone.conf</filename> file."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml98(term)
+msgid "Filters"
+msgstr "フィルター"
+
+#: ./doc/common/section_keystone_config_ldap.xml100(para)
+msgid "Use filters to control the scope of data presented through LDAP."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml109(term)
+msgid "LDAP Account Status"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml111(para)
+msgid ""
+"Mask account status values for compatibility with various directory "
+"services. Superfluous accounts are filtered with "
+"<systemitem>user_filter</systemitem>."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap.xml115(para)
+msgid ""
+"For example, you can mask Active Directory account status attributes in the "
+"<filename>keystone.conf</filename> file:"
+msgstr ""
+
+#: ./doc/common/app_support.xml7(title)
+msgid "Community support"
+msgstr "コミュニティのサポート"
+
+#: ./doc/common/app_support.xml8(para)
+msgid ""
+"The following resources are available to help you run and use OpenStack. The"
+" OpenStack community constantly improves and adds to the main features of "
+"OpenStack, but if you have any questions, do not hesitate to ask. Use the "
+"following resources to get OpenStack support, and troubleshoot your "
+"installations."
+msgstr "OpenStackの利用に役立つ、以下のリソースがあります。OpenStackコミュニティは、OpenStackを継続的に改善、機能追加していますが、もしあなたが何らかの疑問に直面したら、遠慮せずに相談してください。下記のリソースをOpenStackのサポートとトラブルシュートに活用してください。"
+
+#: ./doc/common/app_support.xml15(title)
+msgid "Documentation"
+msgstr "ドキュメント"
+
+#: ./doc/common/app_support.xml16(para)
+msgid ""
+"For the available OpenStack documentation, see <link "
+"href=\"http://docs.openstack.org\">docs.openstack.org</link>."
+msgstr "OpenStackのドキュメントは、 <link href=\"http://docs.openstack.org\">docs.openstack.org</link>を参照してください。"
+
+#: ./doc/common/app_support.xml19(para) ./doc/common/app_support.xml393(para)
+#: ./doc/common/ch_getstart.xml208(para)
+msgid ""
+"To provide feedback on documentation, join and use the <email>openstack-"
+"docs@lists.openstack.org</email> mailing list at <link "
+"href=\"http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-"
+"docs\">OpenStack Documentation Mailing List</link>, or <link "
+"href=\"https://bugs.launchpad.net/openstack-manuals/+filebug\">report a "
+"bug</link>."
+msgstr "ドキュメントにフィードバックするには、 <link href=\"http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs\">OpenStack Documentation Mailing List</link>の <email>openstack-docs@lists.openstack.org</email>か、Launchpadの<link href=\"https://bugs.launchpad.net/openstack-manuals/+filebug\">report a bug</link>を活用してください。"
+
+#: ./doc/common/app_support.xml26(para)
+msgid ""
+"The following books explain how to install an OpenStack cloud and its "
+"associated components:"
+msgstr "OpenStackクラウドと関連コンポーネントの導入ガイド:"
+
+#: ./doc/common/app_support.xml33(citetitle)
+msgid "Installation Guide for Debian 7.0"
+msgstr "Installation Guide for Debian 7.0"
+
+#: ./doc/common/app_support.xml41(citetitle)
+msgid "Installation Guide for openSUSE and SUSE Linux Enterprise Server"
+msgstr "Installation Guide for openSUSE and SUSE Linux Enterprise Server"
+
+#: ./doc/common/app_support.xml49(citetitle)
+msgid "Installation Guide for Red Hat Enterprise Linux, CentOS, and Fedora"
+msgstr "Red Hat Enterprise Linux, CentOS, and Fedora向けインストールガイド"
+
+#: ./doc/common/app_support.xml58(citetitle)
+msgid "Installation Guide for Ubuntu 12.04/14.04 (LTS)"
+msgstr "インストールガイド Ubuntu 12.04/14.04 (LTS) 版"
+
+#: ./doc/common/app_support.xml63(para)
+msgid ""
+"The following books explain how to configure and run an OpenStack cloud:"
+msgstr "OpenStackクラウドの構成と実行ガイド:"
+
+#: ./doc/common/app_support.xml70(citetitle)
+msgid "Cloud Administrator Guide"
+msgstr "Cloud Administrator Guide"
+
+#: ./doc/common/app_support.xml76(citetitle)
+msgid "Configuration Reference"
+msgstr "Configuration Reference"
+
+#: ./doc/common/app_support.xml82(citetitle)
+msgid "Operations Guide"
+msgstr "Operations Guide"
+
+#: ./doc/common/app_support.xml88(citetitle)
+msgid "High Availability Guide"
+msgstr "High Availability Guide"
+
+#: ./doc/common/app_support.xml94(citetitle)
+msgid "Security Guide"
+msgstr "Security Guide"
+
+#: ./doc/common/app_support.xml100(citetitle)
+msgid "Virtual Machine Image Guide"
+msgstr "Virtual Machine Image Guide"
+
+#: ./doc/common/app_support.xml104(para)
+msgid ""
+"The following books explain how to use the OpenStack dashboard and command-"
+"line clients:"
+msgstr "OpenStackダッシュボードとCLIクライアントガイド"
+
+#: ./doc/common/app_support.xml111(citetitle)
+msgid "API Quick Start"
+msgstr "API Quick Start"
+
+#: ./doc/common/app_support.xml118(citetitle)
+msgid "End User Guide"
+msgstr "End User Guide"
+
+#: ./doc/common/app_support.xml125(citetitle)
+msgid "Admin User Guide"
+msgstr "Admin User Guide"
+
+#: ./doc/common/app_support.xml132(citetitle)
+msgid "Command-Line Interface Reference"
+msgstr "コマンドラインインターフェースリファレンス"
+
+#: ./doc/common/app_support.xml136(para)
+msgid ""
+"The following documentation provides reference and guidance information for "
+"the OpenStack APIs:"
+msgstr "OpenStack APIのリファレンスガイド"
+
+#: ./doc/common/app_support.xml142(link)
+msgid "OpenStack API Complete Reference (HTML)"
+msgstr "OpenStack API Complete Reference (HTML)"
+
+#: ./doc/common/app_support.xml148(link)
+msgid "API Complete Reference (PDF)"
+msgstr "API Complete Reference (PDF)"
+
+#: ./doc/common/app_support.xml153(citetitle)
+msgid "OpenStack Block Storage Service API v2 Reference"
+msgstr "OpenStack Block Storage Service API v2 Reference"
+
+#: ./doc/common/app_support.xml160(citetitle)
+msgid "OpenStack Compute API v2 and Extensions Reference"
+msgstr "OpenStack Compute API v2 and Extensions Reference"
+
+#: ./doc/common/app_support.xml167(citetitle)
+msgid "OpenStack Identity Service API v2.0 Reference"
+msgstr "OpenStack Identity Service API v2.0 Reference"
+
+#: ./doc/common/app_support.xml173(citetitle)
+msgid "OpenStack Image Service API v2 Reference"
+msgstr "OpenStack Identity Service API v2.0 Reference"
+
+#: ./doc/common/app_support.xml179(citetitle)
+msgid "OpenStack Networking API v2.0 Reference"
+msgstr "OpenStack Networking API v2.0 Reference"
+
+#: ./doc/common/app_support.xml185(citetitle)
+msgid "OpenStack Object Storage API v1 Reference"
+msgstr "OpenStack Object Storage API v1 Reference"
+
+#: ./doc/common/app_support.xml189(para)
+msgid ""
+"The <link href=\"http://docs.openstack.org/training-"
+"guides/content/\"><citetitle>Training Guides</citetitle></link> offer "
+"software training for cloud administration and management."
+msgstr "<link href=\"http://docs.openstack.org/training-guides/content/\"><citetitle>トレーニングガイド</citetitle></link>はクラウド管理者向けのソフトウェアトレーニングを提供します。"
+
+#: ./doc/common/app_support.xml196(title)
+msgid "ask.openstack.org"
+msgstr "ask.openstack.org"
+
+#: ./doc/common/app_support.xml197(para)
+msgid ""
+"During the set up or testing of OpenStack, you might have questions about "
+"how a specific task is completed or be in a situation where a feature does "
+"not work correctly. Use the <link "
+"href=\"http://ask.openstack.org\">ask.openstack.org</link> site to ask "
+"questions and get answers. When you visit the <link "
+"href=\"http://ask.openstack.org\">http://ask.openstack.org</link> site, scan"
+" the recently asked questions to see whether your question has already been "
+"answered. If not, ask a new question. Be sure to give a clear, concise "
+"summary in the title and provide as much detail as possible in the "
+"description. Paste in your command output or stack traces, links to screen "
+"shots, and any other information which might be useful."
+msgstr "OpenStackの導入やテスト中、特定のタスクが完了したのか、うまく動いていないのかを質問したくなるかもしれません。その時は、<link href=\"http://ask.openstack.org\">ask.openstack.org</link>が役に立ちます。<link href=\"http://ask.openstack.org\">ask.openstack.org</link>で、すでに同様の質問に回答がないかを確かめてみてください。もしなければ、質問しましょう。簡潔で明瞭なサマリーをタイトルにし、できるだけ詳細な情報を記入してください。コマンドの出力結果やスタックトレース、スクリーンショットへのリンク、その他有用な情報などがいいでしょう。"
+
+#: ./doc/common/app_support.xml214(title)
+msgid "OpenStack mailing lists"
+msgstr "OpenStack メーリングリスト"
+
+#: ./doc/common/app_support.xml215(para)
+msgid ""
+"A great way to get answers and insights is to post your question or "
+"problematic scenario to the OpenStack mailing list. You can learn from and "
+"help others who might have similar issues. To subscribe or view the "
+"archives, go to <link href=\"http://lists.openstack.org/cgi-"
+"bin/mailman/listinfo/openstack\">http://lists.openstack.org/cgi-"
+"bin/mailman/listinfo/openstack</link>. You might be interested in the other "
+"mailing lists for specific projects or development, which you can find <link"
+" href=\"http://wiki.openstack.org/MailingLists\">on the wiki</link>. A "
+"description of all mailing lists is available at <link "
+"href=\"http://wiki.openstack.org/MailingLists\">http://wiki.openstack.org/MailingLists</link>."
+msgstr "回答やヒントを得るとっておきの方法は、OpenStackメーリングリストへ質問や問題の状況を投稿することです。同様の問題に対処したことのある仲間が助けてくれることでしょう。購読の手続き、アーカイブの参照は<link href=\"http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack\">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</link>で行ってください。特定プロジェクトや環境についてのメーリングリストは、<link href=\"http://wiki.openstack.org/MailingLists\">on the wiki</link>で探してみましょう。すべてのメーリングリストは、<link href=\"http://wiki.openstack.org/MailingLists\">http://wiki.openstack.org/MailingLists</link>で参照できます。"
+
+#: ./doc/common/app_support.xml231(title)
+msgid "The OpenStack wiki"
+msgstr "OpenStack wiki"
+
+#: ./doc/common/app_support.xml232(para)
+msgid ""
+"The <link href=\"http://wiki.openstack.org/\">OpenStack wiki</link> contains"
+" a broad range of topics but some of the information can be difficult to "
+"find or is a few pages deep. Fortunately, the wiki search feature enables "
+"you to search by title or content. If you search for specific information, "
+"such as about networking or nova, you can find a large amount of relevant "
+"material. More is being added all the time, so be sure to check back often. "
+"You can find the search box in the upper-right corner of any OpenStack wiki "
+"page."
+msgstr "<link href=\"http://wiki.openstack.org/\">OpenStack wiki</link>は広い範囲のトピックを扱っていますが、情報によっては、探すのが難しかったり、情報が少なかったりします。幸いなことに wiki の検索機能で、タイトルと内容で探せます。もし特定の情報、たとえばネットワークや nova について探すのであれば、多くの関連情報を見つけられます。日々追加されているため、こまめに確認してみてください。OpenStack wiki ページの右上に、その検索窓はあります。"
+
+#: ./doc/common/app_support.xml243(title)
+msgid "The Launchpad Bugs area"
+msgstr "Launchpad バグエリア"
+
+#: ./doc/common/app_support.xml244(para)
+msgid ""
+"The OpenStack community values your set up and testing efforts and wants "
+"your feedback. To log a bug, you must sign up for a Launchpad account at "
+"<link "
+"href=\"https://launchpad.net/+login\">https://launchpad.net/+login</link>. "
+"You can view existing bugs and report bugs in the Launchpad Bugs area. Use "
+"the search feature to determine whether the bug has already been reported or"
+" already been fixed. If it still seems like your bug is unreported, fill out"
+" a bug report."
+msgstr "OpenStackコミュニティはあなたのセットアップ、テストの取り組みに価値を感じており、フィードバックを求めています。バグを登録するには、<link href=\"https://launchpad.net/+login\">https://launchpad.net/+login</link>でLaunchpadのアカウントを作成してください。Launchpadバグエリアにて、既知のバグの確認と報告ができます。すでにそのバグが報告、解決されていないかを判断するため、検索機能を活用してください。もしそのバグが報告されていなければ、バグレポートを入力しましょう。"
+
+#: ./doc/common/app_support.xml252(para)
+msgid "Some tips:"
+msgstr "使いこなすヒント:"
+
+#: ./doc/common/app_support.xml255(para)
+msgid "Give a clear, concise summary."
+msgstr "明瞭で簡潔なまとめを。"
+
+#: ./doc/common/app_support.xml258(para)
+msgid ""
+"Provide as much detail as possible in the description. Paste in your command"
+" output or stack traces, links to screen shots, and any other information "
+"which might be useful."
+msgstr "できるだけ詳細な情報を記入してください。コマンドの出力結果やスタックトレース、スクリーンショットへのリンク、その他有用な情報などがいいでしょう。"
+
+#: ./doc/common/app_support.xml264(para)
+msgid ""
+"Be sure to include the software and package versions that you are using, "
+"especially if you are using a development branch, such as, <literal>\"Juno "
+"release\" vs git commit bc79c3ecc55929bac585d04a03475b72e06a3208</literal>."
+msgstr "ソフトウェアとパッケージのバージョンを含めることを忘れずに。特に開発ブランチは<literal>\"Juno release\" vs git commit bc79c3ecc55929bac585d04a03475b72e06a3208</literal>のように明記しましょう。"
+
+#: ./doc/common/app_support.xml271(para)
+msgid ""
+"Any deployment-specific information is helpful, such as whether you are "
+"using Ubuntu 14.04 or are performing a multi-node installation."
+msgstr "環境固有の情報が役に立ちます。例えば、Ubuntu 14.04 の利用有無、複数ノードのインストール有無です。"
+
+#: ./doc/common/app_support.xml276(para)
+msgid "The following Launchpad Bugs areas are available:"
+msgstr "以下の Launchpad バグエリアが利用できます。"
+
+#: ./doc/common/app_support.xml282(link)
+msgid "Bugs: OpenStack Block Storage (cinder)"
+msgstr "Bugs: OpenStack Block Storage (cinder)"
+
+#: ./doc/common/app_support.xml288(link)
+msgid "Bugs: OpenStack Compute (nova)"
+msgstr "Bugs: OpenStack Compute (nova)"
+
+#: ./doc/common/app_support.xml293(link)
+msgid "Bugs: OpenStack Dashboard (horizon)"
+msgstr "Bugs : OpenStack Dashboard (horizon)"
+
+#: ./doc/common/app_support.xml299(link)
+msgid "Bugs: OpenStack Identity (keystone)"
+msgstr "Bugs : OpenStack Identity (keystone)"
+
+#: ./doc/common/app_support.xml305(link)
+msgid "Bugs: OpenStack Image Service (glance)"
+msgstr "Bugs : OpenStack Image Service (glance)"
+
+#: ./doc/common/app_support.xml311(link)
+msgid "Bugs: OpenStack Networking (neutron)"
+msgstr "Bugs : OpenStack Networking (neutron)"
+
+#: ./doc/common/app_support.xml317(link)
+msgid "Bugs: OpenStack Object Storage (swift)"
+msgstr "Bugs : OpenStack Object Storage (swift)"
+
+#: ./doc/common/app_support.xml324(link)
+msgid "Bugs: Bare Metal (ironic)"
+msgstr "Bugs: Bare Metal (ironic)"
+
+#: ./doc/common/app_support.xml329(link)
+msgid "Bugs: Data Processing Service (sahara)"
+msgstr "Bugs: Data Processing Service (sahara)"
+
+#: ./doc/common/app_support.xml335(link)
+msgid "Bugs: Database Service (trove)"
+msgstr "Bugs: Database Service (trove)"
+
+#: ./doc/common/app_support.xml340(link)
+msgid "Bugs: Orchestration (heat)"
+msgstr "Bugs: Orchestration (heat)"
+
+#: ./doc/common/app_support.xml345(link)
+msgid "Bugs: Telemetry (ceilometer)"
+msgstr "Bugs: Telemetry (ceilometer)"
+
+#: ./doc/common/app_support.xml350(link)
+msgid "Bugs: Queue Service (marconi)"
+msgstr "Bugs: Queue Service (marconi)"
+
+#: ./doc/common/app_support.xml356(link)
+msgid "Bugs: OpenStack API Documentation (developer.openstack.org)"
+msgstr "Bugs: OpenStack API Documentation (developer.openstack.org)"
+
+#: ./doc/common/app_support.xml362(link)
+msgid "Bugs: OpenStack Documentation (docs.openstack.org)"
+msgstr "Bugs: OpenStack Documentation (docs.openstack.org)"
+
+#: ./doc/common/app_support.xml368(title)
+msgid "The OpenStack IRC channel"
+msgstr "OpenStack IRC チャネル"
+
+#: ./doc/common/app_support.xml369(para)
+msgid ""
+"The OpenStack community lives in the #openstack IRC channel on the Freenode "
+"network. You can hang out, ask questions, or get immediate feedback for "
+"urgent and pressing issues. To install an IRC client or use a browser-based "
+"client, go to <link "
+"href=\"http://webchat.freenode.net\">http://webchat.freenode.net/</link>. "
+"You can also use Colloquy (Mac OS X, <link "
+"href=\"http://colloquy.info/\">http://colloquy.info/</link>), mIRC (Windows,"
+" <link href=\"http://www.mirc.com/\">http://www.mirc.com/</link>), or XChat "
+"(Linux). When you are in the IRC channel and want to share code or command "
+"output, the generally accepted method is to use a Paste Bin. The OpenStack "
+"project has one at <link "
+"href=\"http://paste.openstack.org\">http://paste.openstack.org</link>. Just "
+"paste your longer amounts of text or logs in the web form and you get a URL "
+"that you can paste into the channel. The OpenStack IRC channel is "
+"<literal>#openstack</literal> on <literal>irc.freenode.net</literal>. You "
+"can find a list of all OpenStack IRC channels at <link "
+"href=\"https://wiki.openstack.org/wiki/IRC\">https://wiki.openstack.org/wiki/IRC</link>."
+msgstr "OpenStackコミュニティはFreenode上の#openstack IRCチャネルを活用しています。あなたはそこに訪れ、質問することで、差し迫った問題へのフィードバックを迅速に得られます。IRCクライアントをインストール、もしくはブラウザベースのクライアントを使うには、<link href=\"http://webchat.freenode.net\">http://webchat.freenode.net/</link>にアクセスしてください。また、Colloquy (Mac OS X, <link href=\"http://colloquy.info/\">http://colloquy.info/</link>), mIRC (Windows, <link href=\"http://www.mirc.com/\">http://www.mirc.com/</link>), or XChat (Linux)なども使えます。IRCチャネル上でコードやコマンド出力結果を共有したい時には、Paste Binが多く使われています。OpenStackプロジェクトのPaste Binは<link href=\"http://paste.openstack.org\">http://paste.openstack.org</link>です。長めのテキストやログであっても、webフォームに貼り付けてURLを得るだけです。OpenStack IRCチャネルは、<literal>#openstack</literal> on <literal>irc.freenode.net</literal>です。OpenStack IRC チャネルは、<link href=\"https://wiki.openstack.org/wiki/IRC\">https://wiki.openstack.org/wiki/IRC</link>にリストがあります。"
+
+#: ./doc/common/app_support.xml392(title)
+msgid "Documentation feedback"
+msgstr "ドキュメントへのフィードバック"
+
+#: ./doc/common/app_support.xml399(title)
+msgid "OpenStack distribution packages"
+msgstr "OpenStackディストリビューション"
+
+#: ./doc/common/app_support.xml400(para)
+msgid ""
+"The following Linux distributions provide community-supported packages for "
+"OpenStack:"
+msgstr "OpenStackのコミュニティサポート版を提供しているディストリビューション"
+
+#: ./doc/common/app_support.xml404(emphasis)
+msgid "Debian:"
+msgstr "Debian:"
+
+#: ./doc/common/app_support.xml407(link)
+msgid "http://wiki.debian.org/OpenStack"
+msgstr "http://wiki.debian.org/OpenStack"
+
+#: ./doc/common/app_support.xml410(emphasis)
+msgid "CentOS, Fedora, and Red Hat Enterprise Linux:"
+msgstr "CentOS、Fedora、およびRed Hat Enterprise Linux:"
+
+#: ./doc/common/app_support.xml413(link)
+msgid "http://openstack.redhat.com/"
+msgstr "http://openstack.redhat.com/"
+
+#: ./doc/common/app_support.xml416(emphasis)
+msgid "openSUSE and SUSE Linux Enterprise Server:"
+msgstr "openSUSEとSUSE Linux Enterprise Server:"
+
+#: ./doc/common/app_support.xml420(link)
+msgid "http://en.opensuse.org/Portal:OpenStack"
+msgstr "http://en.opensuse.org/Portal:OpenStack"
+
+#: ./doc/common/app_support.xml423(emphasis)
+msgid "Ubuntu:"
+msgstr "Ubuntu:"
+
+#: ./doc/common/app_support.xml426(link)
+msgid "https://wiki.ubuntu.com/ServerTeam/CloudArchive"
+msgstr "https://wiki.ubuntu.com/ServerTeam/CloudArchive"
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml6(title)
+msgid "Troubleshoot Object Storage"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml7(para)
+msgid ""
+"For Object Storage, everything is logged in "
+"<filename>/var/log/syslog</filename> (or messages on some distros). Several "
+"settings enable further customization of logging, such as "
+"<literal>log_name</literal>, <literal>log_facility</literal>, and "
+"<literal>log_level</literal>, within the object server configuration files."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml11(title)
+msgid "Drive failure"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml12(para)
+msgid ""
+"In the event that a drive has failed, the first step is to make sure the "
+"drive is unmounted. This will make it easier for Object Storage to work "
+"around the failure until it has been resolved. If the drive is going to be "
+"replaced immediately, then it is just best to replace the drive, format it, "
+"remount it, and let replication fill it up."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml16(para)
+msgid ""
+"If the drive can’t be replaced immediately, then it is best to leave it "
+"unmounted, and remove the drive from the ring. This will allow all the "
+"replicas that were on that drive to be replicated elsewhere until the drive "
+"is replaced. Once the drive is replaced, it can be re-added to the ring."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml20(para)
+msgid ""
+"You can look at error messages in <filename>/var/log/kern.log</filename> for"
+" hints of drive failure."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml23(title)
+msgid "Server failure"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml24(para)
+msgid ""
+"If a server is having hardware issues, it is a good idea to make sure the "
+"Object Storage services are not running. This will allow Object Storage to "
+"work around the failure while you troubleshoot."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml27(para)
+msgid ""
+"If the server just needs a reboot, or a small amount of work that should "
+"only last a couple of hours, then it is probably best to let Object Storage "
+"work around the failure and get the machine fixed and back online. When the "
+"machine comes back online, replication will make sure that anything that is "
+"missing during the downtime will get updated."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml32(para)
+msgid ""
+"If the server has more serious issues, then it is probably best to remove "
+"all of the server’s devices from the ring. Once the server has been repaired"
+" and is back online, the server’s devices can be added back into the ring. "
+"It is important that the devices are reformatted before putting them back "
+"into the ring as it is likely to be responsible for a different set of "
+"partitions than before."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml40(title)
+msgid "Detect failed drives"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml41(para)
+msgid ""
+"It has been our experience that when a drive is about to fail, error "
+"messages will spew into /var/log/kern.log. There is a script called swift-"
+"drive-audit that can be run via cron to watch for bad drives. If errors are "
+"detected, it will unmount the bad drive, so that Object Storage can work "
+"around it. The script takes a configuration file with the following "
+"settings:"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml47(para)
+msgid ""
+"This script has only been tested on Ubuntu 10.04, so if you are using a "
+"different distro or OS, some care should be taken before using in "
+"production."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml52(title)
+msgid "Emergency recovery of ring builder files"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml53(para)
+msgid ""
+"You should always keep a backup of swift ring builder files. However, if an "
+"emergency occurs, this procedure may assist in returning your cluster to an "
+"operational state."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml56(para)
+msgid ""
+"Using existing swift tools, there is no way to recover a builder file from a"
+" <filename>ring.gz</filename> file. However, if you have a knowledge of "
+"Python, it is possible to construct a builder file that is pretty close to "
+"the one you have lost. The following is what you will need to do."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml61(para)
+msgid ""
+"This procedure is a last-resort for emergency circumstances. It requires "
+"knowledge of the swift python code and may not succeed."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml64(para)
+msgid "First, load the ring and a new ringbuilder object in a Python REPL:"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml67(para)
+msgid "Now, start copying the data we have in the ring into the builder."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml84(para)
+msgid ""
+"This is the extent of the recoverable fields. For "
+"<literal>min_part_hours</literal> you'll either have to remember what the "
+"value you used was, or just make up a new one."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml89(para)
+msgid ""
+"Try some validation: if this doesn't raise an exception, you may feel some "
+"hope. Not too much, though."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml92(para)
+msgid "Save the builder."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml96(para)
+msgid ""
+"You should now have a file called 'account.builder' in the current working "
+"directory. Next, run <literal>swift-ring-builder account.builder "
+"write_ring</literal> and compare the new account.ring.gz to the "
+"account.ring.gz that you started from. They probably won't be byte-for-byte "
+"identical, but if you load them up in a REPL and their "
+"<literal>_replica2part2dev_id</literal> and <literal>devs</literal> "
+"attributes are the same (or nearly so), then you're in good shape."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-troubleshoot.xml103(para)
+msgid ""
+"Next, repeat the procedure for <filename>container.ring.gz</filename> and "
+"<filename>object.ring.gz</filename>, and you might get usable builder files."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-account-reaper.xml7(title)
+msgid "Account reaper"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-account-reaper.xml8(para)
+msgid ""
+"In the background, the account reaper removes data from the deleted "
+"accounts."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-account-reaper.xml9(para)
+msgid ""
+"A reseller marks an account for deletion by issuing a <code>DELETE</code> "
+"request on the account’s storage URL. This action sets the "
+"<code>status</code> column of the account_stat table in the account database"
+" and replicas to <code>DELETED</code>, marking the account's data for "
+"deletion."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-account-reaper.xml17(para)
+msgid ""
+"It's on the developers' to-do list to write a utility that performs this "
+"task, preferably through a ReST call."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-account-reaper.xml12(para)
+msgid ""
+"Typically, a specific retention time or undelete are not provided. However, "
+"you can set a <code>delay_reaping</code> value in the <code>[account-"
+"reaper]</code> section of the account-server.conf to delay the actual "
+"deletion of data. At this time, to undelete you have to update the account "
+"database replicas directly, setting the status column to an empty string and"
+" updating the put_timestamp to be greater than the delete_timestamp. "
+"<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-account-reaper.xml20(para)
+msgid ""
+"The account reaper runs on each account server and scans the server "
+"occasionally for account databases marked for deletion. It only fires up on "
+"the accounts for which the server is the primary node, so that multiple "
+"account servers aren’t trying to do it simultaneously. Using multiple "
+"servers to delete one account might improve the deletion speed but requires "
+"coordination to avoid duplication. Speed really is not a big concern with "
+"data deletion, and large accounts aren’t deleted often."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-account-reaper.xml26(para)
+msgid ""
+"Deleting an account is simple. For each account container, all objects are "
+"deleted and then the container is deleted. Deletion requests that fail will "
+"not stop the overall process but will cause the overall process to fail "
+"eventually (for example, if an object delete times out, you will not be able"
+" to delete the container or the account). The account reaper keeps trying to"
+" delete an account until it is empty, at which point the database reclaim "
+"process within the db_replicator will remove the database files."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-account-reaper.xml32(para)
+msgid ""
+"A persistent error state may prevent the deletion of an object or container."
+" If this happens, you will see a message such as <code>“Account &lt;name&gt;"
+" has not been reaped since &lt;date&gt;”</code> in the log. You can control "
+"when this is logged with the <code>reap_warn_after</code> value in the <code"
+">[account-reaper]</code> section of the account-server.conf file. The "
+"default value is 30 days."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml7(title)
+#: ./doc/common/section_dashboard_access.xml304(guilabel)
+msgid "Flavors"
+msgstr "フレーバー"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml8(para)
+msgid ""
+"Admin users can use the <placeholder-1/> commands to customize and manage "
+"flavors. To see the available flavor-related commands, run:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml22(para)
+msgid ""
+"Configuration rights can be delegated to additional users by redefining the "
+"access controls for <option>compute_extension:flavormanage</option> in "
+"<filename>/etc/nova/policy.json</filename> on the <systemitem class=\"server"
+"\">nova-api</systemitem> server."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml26(para)
+msgid ""
+"To modify an existing flavor in the dashboard, you must delete the flavor "
+"and create a modified one with the same name."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml31(para)
+msgid "Flavors define these elements:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml33(caption)
+msgid "Identity Service configuration file sections"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml39(td)
+msgid "Element"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml45(literal)
+msgid "Name"
+msgstr "名前"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml47(replaceable)
+msgid "XX"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml47(replaceable)
+msgid "SIZE_NAME"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml46(td)
+msgid ""
+"A descriptive name. <placeholder-1/>.<placeholder-2/> is typically not "
+"required, though some third party tools may rely on it."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml52(literal)
+msgid "Memory_MB"
+msgstr "MB メモリー"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml53(td)
+msgid "Virtual machine memory in megabytes."
+msgstr "メガバイト単位の仮想マシンメモリー。"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml56(literal)
+msgid "Disk"
+msgstr "ディスク"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml57(td)
+msgid ""
+"Virtual root disk size in gigabytes. This is an ephemeral disk that the base"
+" image is copied into. When booting from a persistent volume it is not used."
+" The \"0\" size is a special case which uses the native base image size as "
+"the size of the ephemeral root volume."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml65(literal)
+msgid "Ephemeral"
+msgstr "エフェメラル"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml66(td)
+msgid ""
+"Specifies the size of a secondary ephemeral data disk. This is an empty, "
+"unformatted disk and exists only for the life of the instance."
+msgstr "二次的な一時データディスクの容量を指定します。これは空の、フォーマットされていないディスクです。インスタンスの生存期間だけ存在します。"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml71(literal)
+msgid "Swap"
+msgstr "スワップ"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml72(td)
+msgid "Optional swap space allocation for the instance."
+msgstr "インスタンスに割り当てられるスワップ空間。これはオプションです。"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml76(literal)
+msgid "VCPUs"
+msgstr "仮想 CPU"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml77(td)
+msgid "Number of virtual CPUs presented to the instance."
+msgstr "インスタンスに存在する仮想 CPU 数。"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml81(literal)
+msgid "RXTX_Factor"
+msgstr "RXTX_Factor"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml82(td)
+msgid ""
+"Optional property allows created servers to have a different bandwidth cap "
+"than that defined in the network they are attached to. This factor is "
+"multiplied by the rxtx_base property of the network. Default value is 1.0. "
+"That is, the same as attached network."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml90(literal)
+msgid "Is_Public"
+msgstr "Is_Public"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml91(td)
+msgid ""
+"Boolean value, whether flavor is available to all users or private to the "
+"tenant it was created in. Defaults to True."
+msgstr "論理値。フレーバーがすべてのユーザーに利用可能か、または作成されたプロジェクト内のみであるか。標準で真 (True) です。"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml96(literal)
+msgid "extra_specs"
+msgstr "extra_specs"
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml97(para)
+msgid ""
+"Key and value pairs that define on which compute nodes a flavor can run. "
+"These pairs must match corresponding pairs on the compute nodes. Use to "
+"implement special resources, such as flavors that run on only compute nodes "
+"with GPU hardware."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml105(para)
+msgid ""
+"Flavor customization can be limited by the hypervisor in use. For example "
+"the <systemitem>libvirt</systemitem> driver enables quotas on CPUs available"
+" to a VM, disk tuning, bandwidth I/O, watchdog behavior, random number "
+"generator device control, and instance VIF traffic control."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml110(term)
+msgid "CPU limits"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml111(para)
+msgid ""
+"You can configure the CPU limits with control parameters with the "
+"<placeholder-1/> client. For example, to configure the I/O limit, use:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml115(para)
+msgid ""
+"There are optional CPU control parameters for weight shares, enforcement "
+"intervals for runtime quotas, and a quota for maximum allowed bandwidth:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml121(para)
+msgid ""
+"<literal>cpu_shares</literal> specifies the proportional weighted share for "
+"the domain. If this element is omitted, the service defaults to the OS "
+"provided defaults. There is no unit for the value; it is a relative measure "
+"based on the setting of other VMs. For example, a VM configured with value "
+"2048 gets twice as much CPU time as a VM configured with value 1024."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml130(para)
+msgid ""
+"<literal>cpu_period</literal> specifies the enforcement interval (unit: "
+"microseconds) for QEMU and LXC hypervisors. Within a period, each VCPU of "
+"the domain is not allowed to consume more than the quota worth of runtime. "
+"The value should be in range <literal>[1000, 1000000]</literal>. A period "
+"with value 0 means no value."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml138(para)
+msgid ""
+"<literal>cpu_quota</literal> specifies the maximum allowed bandwidth (unit: "
+"microseconds). A domain with a negative-value quota indicates that the "
+"domain has infinite bandwidth, which means that it is not bandwidth "
+"controlled. The value should be in range <literal>[1000, "
+"18446744073709551]</literal> or less than 0. A quota with value 0 means no "
+"value. You can use this feature to ensure that all vCPUs run at the same "
+"speed. For example:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml147(para)
+msgid ""
+"In this example, the instance of <literal>m1.low_cpu</literal> can only "
+"consume a maximum of 50% CPU of a physical CPU computing capability."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml155(term)
+msgid "Disk tuning"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml156(para)
+msgid ""
+"Using disk I/O quotas, you can set maximum disk write to 10 MB per second "
+"for a VM user. For example:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml159(para)
+msgid "The disk I/O options are:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml162(para)
+msgid "disk_read_bytes_sec"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml165(para)
+msgid "disk_read_iops_sec"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml168(para)
+msgid "disk_write_bytes_sec"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml171(para)
+msgid "disk_write_iops_sec"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml174(para)
+msgid "disk_total_bytes_sec"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml177(para)
+msgid "disk_total_iops_sec"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml180(para)
+msgid "The vif I/O options are:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml183(para)
+msgid "vif_inbound_ average"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml186(para)
+msgid "vif_inbound_burst"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml189(para)
+msgid "vif_inbound_peak"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml192(para)
+msgid "vif_outbound_ average"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml195(para)
+msgid "vif_outbound_burst"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml198(para)
+msgid "vif_outbound_peak"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml202(term)
+msgid "Bandwidth I/O"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml203(para)
+msgid ""
+"Incoming and outgoing traffic can be shaped independently. The bandwidth "
+"element can have at most one inbound and at most one outbound child element."
+" If you leave any of these children element out, no quality of service (QoS)"
+" is applied on that traffic direction. So, if you want to shape only the "
+"network's incoming traffic, use inbound only (and vice versa). Each element "
+"has one mandatory attribute average, which specifies the average bit rate on"
+" the interface being shaped."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml209(para)
+msgid ""
+"There are also two optional attributes (integer): <option>peak</option>, "
+"which specifies maximum rate at which bridge can send data "
+"(kilobytes/second), and <option>burst</option>, the amount of bytes that can"
+" be burst at peak speed (kilobytes). The rate is shared equally within "
+"domains connected to the network."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml214(para)
+msgid ""
+"The following example configures a bandwidth limit for instance network "
+"traffic:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml219(term)
+msgid "Watchdog behavior"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml220(para)
+msgid ""
+"For the <systemitem>libvirt</systemitem> driver, you can enable and set the "
+"behavior of a virtual hardware watchdog device for each flavor. Watchdog "
+"devices keep an eye on the guest server, and carry out the configured action"
+" if the server hangs. The watchdog uses the i6300esb device (emulating a PCI"
+" Intel 6300ESB). If <literal>hw_watchdog_action</literal> is not specified, "
+"the watchdog is disabled."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml226(para)
+msgid "To set the behavior, use:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml227(replaceable)
+#: ./doc/common/section_cli_nova_customize_flavors.xml257(replaceable)
+#: ./doc/common/section_cli_nova_customize_flavors.xml258(replaceable)
+#: ./doc/common/section_cli_nova_customize_flavors.xml259(replaceable)
+msgid "FLAVOR-NAME"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml227(replaceable)
+msgid "ACTION"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml228(para)
+msgid "Valid <replaceable>ACTION</replaceable> values are:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml231(para)
+msgid "<literal>disabled</literal>(default) The device is not attached."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml234(para)
+msgid "<literal>reset</literal>Forcefully reset the guest."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml238(para)
+msgid "<literal>poweroff</literal>Forcefully power off the guest."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml242(para)
+msgid "<literal>pause</literal>Pause the guest."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml245(para)
+msgid ""
+"<literal>none</literal>Only enable the watchdog; do nothing if the server "
+"hangs."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml249(para)
+msgid ""
+"Watchdog behavior set using a specific image's properties will override "
+"behavior set using flavors."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml254(term)
+msgid "Random-number generator"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml255(para)
+msgid ""
+"If a random-number generator device has been added to the instance through "
+"its image properties, the device can be enabled and configured using:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml258(replaceable)
+msgid "RATE-BYTES"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml259(replaceable)
+msgid "RATE-PERIOD"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml263(para)
+msgid ""
+"<replaceable>RATE-BYTES</replaceable>(Integer) Allowed amount of bytes that "
+"the guest can read from the host's entropy per period."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml267(para)
+msgid ""
+"<replaceable>RATE-PERIOD</replaceable>(Integer) Duration of the read period "
+"in seconds."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml273(term)
+msgid "Instance VIF traffic control"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_customize_flavors.xml274(para)
+msgid ""
+"Flavors can also be assigned to particular projects. By default, a flavor is"
+" public and available to all projects. Private flavors are only accessible "
+"to those on the access list and are invisible to other projects. To create "
+"and assign a private flavor to a project, run these commands:"
+msgstr ""
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml6(title)
+msgid "Configure tenant-specific image locations with Object Storage"
+msgstr ""
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml14(para)
+msgid "The tenant who owns the image"
+msgstr ""
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml17(para)
+msgid ""
+"Tenants that are defined in <option>swift_store_admin_tenants</option> and "
+"that have admin-level accounts"
+msgstr ""
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml8(para)
+msgid ""
+"For some deployers, it is not ideal to store all images in one place to "
+"enable all tenants and users to access them. You can configure the Image "
+"Service to store image data in tenant-specific image locations. Then, only "
+"the following tenants can use the Image Service to access the created "
+"image:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml23(title)
+msgid "To configure tenant-specific image locations"
+msgstr ""
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml25(para)
+msgid ""
+"Configure swift as your <option>default_store</option> in the <filename"
+">glance-api.conf</filename> file."
+msgstr ""
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml33(para)
+msgid ""
+"<option>swift_store_multi_tenant</option>. Set to <literal>True</literal> to"
+" enable tenant-specific storage locations. Default is "
+"<literal>False</literal>."
+msgstr ""
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml39(para)
+msgid ""
+"<option>swift_store_admin_tenants</option>. Specify a list of tenant IDs "
+"that can grant read and write access to all Object Storage containers that "
+"are created by the Image Service."
+msgstr ""
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml30(para)
+msgid ""
+"Set these configuration options in the <filename>glance-api.conf</filename> "
+"file: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_objectstorage_tenant-specific-image-storage.xml48(para)
+msgid ""
+"With this configuration, images are stored in an Object Storage service "
+"(swift) endpoint that is pulled from the service catalog for the "
+"authenticated user."
 msgstr ""
 
 #: ./doc/common/ch_cli_keystone_commands.xml11(title)
@@ -11461,11 +13622,6 @@ msgstr ""
 msgid "keystone optional arguments"
 msgstr ""
 
-#: ./doc/common/ch_cli_keystone_commands.xml346(para)
-#: ./doc/common/ch_cli_heat_commands.xml325(para)
-msgid "Shows the client version and exits."
-msgstr ""
-
 #: ./doc/common/ch_cli_keystone_commands.xml354(para)
 msgid "Set request timeout (in seconds)."
 msgstr ""
@@ -11525,14 +13681,6 @@ msgid ""
 "<code>env[OS_SERVICE_ENDPOINT]</code>."
 msgstr ""
 
-#: ./doc/common/ch_cli_keystone_commands.xml445(para)
-#: ./doc/common/ch_cli_swift_commands.xml302(para)
-#: ./doc/common/ch_cli_trove_commands.xml558(para)
-msgid ""
-"Specify a CA bundle file to use in verifying a TLS (https) server "
-"certificate. Defaults to <code>env[OS_CACERT]</code>."
-msgstr ""
-
 #: ./doc/common/ch_cli_keystone_commands.xml455(para)
 msgid ""
 "Explicitly allow keystoneclient to perform \"insecure\" TLS (https) "
@@ -11984,3128 +14132,1097 @@ msgstr ""
 msgid "Name or ID of user to update."
 msgstr ""
 
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_getstart_conceptual_arch.xml16(None)
+#: ./doc/common/section_objectstorage-ringbuilder.xml6(title)
+msgid "Ring-builder"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-ringbuilder.xml7(para)
 msgid ""
-"@@image: 'figures/openstack_havana_conceptual_arch.png'; "
-"md5=96e1d5492d4c865fc9145710bb294a91"
-msgstr "@@image: 'figures/openstack_havana_conceptual_arch.png'; md5=96e1d5492d4c865fc9145710bb294a91"
+"Use the swift-ring-builder utility to build and manage rings. This utility "
+"assigns partitions to devices and writes an optimized Python structure to a "
+"gzipped, serialized file on disk for transmission to the servers. The server"
+" processes occasionally check the modification time of the file and reload "
+"in-memory copies of the ring structure as needed. If you use a slightly "
+"older version of the ring, one of the three replicas for a partition subset "
+"will be incorrect because of the way the ring-builder manages changes to the"
+" ring. You can work around this issue."
+msgstr ""
 
-#: ./doc/common/section_getstart_conceptual_arch.xml6(title)
-msgid "Conceptual architecture"
-msgstr "概念アーキテクチャー"
-
-#: ./doc/common/section_getstart_conceptual_arch.xml7(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml17(para)
 msgid ""
-"The following diagram shows the relationships among the OpenStack services:"
-msgstr "以下の図は OpenStack サービス間の関連性を示します。"
-
-#: ./doc/common/section_getstart_conceptual_arch.xml11(title)
-msgid "OpenStack conceptual architecture"
-msgstr "OpenStack の概念アーキテクチャー"
-
-#: ./doc/common/section_cli_nova_metadata.xml9(title)
-msgid "Insert metadata during launch"
+"The ring-builder also keeps its own builder file with the ring information "
+"and additional data required to build future rings. It is very important to "
+"keep multiple backup copies of these builder files. One option is to copy "
+"the builder files out to every server while copying the ring files "
+"themselves. Another is to upload the builder files into the cluster itself. "
+"If you lose the builder file, you have to create a new ring from scratch. "
+"Nearly all partitions would be assigned to different devices and, therefore,"
+" nearly all of the stored data would have to be replicated to new locations."
+" So, recovery from a builder file loss is possible, but data would be "
+"unreachable for an extended time."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_metadata.xml10(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml30(title)
+msgid "Ring data structure"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-ringbuilder.xml31(para)
 msgid ""
-"When booting a server, you can also add metadata, so that you can more "
-"easily identify it amongst your ever-growing elastic cloud. Use the "
-"<literal>--meta</literal> option with a key=value pair, where you can make "
-"up the string for both the key and the value. For example, you could add a "
-"description and also the creator of the server. <placeholder-1/>"
+"The ring data structure consists of three top level fields: a list of "
+"devices in the cluster, a list of lists of device ids indicating partition "
+"to device assignments, and an integer indicating the number of bits to shift"
+" an MD5 hash to calculate the partition for the hash."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_metadata.xml18(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml38(title)
+msgid "Partition assignment list"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-ringbuilder.xml39(para)
 msgid ""
-"When viewing the server information, you can see the metadata included on "
-"the <literal>metadata</literal> line: <placeholder-1/>"
+"This is a list of <literal>array(‘H’)</literal> of devices ids. The "
+"outermost list contains an <literal>array(‘H’)</literal> for each replica. "
+"Each <literal>array(‘H’)</literal> has a length equal to the partition count"
+" for the ring. Each integer in the <literal>array(‘H’)</literal> is an index"
+" into the above list of devices. The partition list is known internally to "
+"the Ring class as <literal>_replica2part2dev_id</literal>."
 msgstr ""
 
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-arch.xml23(None)
+#: ./doc/common/section_objectstorage-ringbuilder.xml48(para)
 msgid ""
-"@@image: '../common/figures/objectstorage-arch.png'; "
-"md5=90f6c7cf3947d7987eeb55d657cdc927"
-msgstr "@@image: '../common/figures/objectstorage-arch.png'; md5=90f6c7cf3947d7987eeb55d657cdc927"
+"So, to create a list of device dictionaries assigned to a partition, the "
+"Python code would look like: <placeholder-1/>"
+msgstr ""
 
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-arch.xml60(None)
+#: ./doc/common/section_objectstorage-ringbuilder.xml52(para)
 msgid ""
-"@@image: '../common/figures/objectstorage-nodes.png'; "
-"md5=2aa7eb3bddcf6826f33469920dc2a9c3"
-msgstr "@@image: '../common/figures/objectstorage-nodes.png'; md5=2aa7eb3bddcf6826f33469920dc2a9c3"
-
-#: ./doc/common/section_objectstorage-arch.xml11(title)
-msgid "Cluster architecture"
+"That code is a little simplistic because it does not account for the removal"
+" of duplicate devices. If a ring has more replicas than devices, a partition"
+" will have more than one replica on a device."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml13(title)
-msgid "Access tier"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-arch.xml14(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml56(para)
 msgid ""
-"Large-scale deployments segment off an access tier, which is considered the "
-"Object Storage system's central hub. The access tier fields the incoming API"
-" requests from clients and moves data in and out of the system. This tier "
-"consists of front-end load balancers, ssl-terminators, and authentication "
-"services. It runs the (distributed) brain of the Object Storage system: the "
-"proxy server processes."
+"<literal>array(‘H’)</literal> is used for memory conservation as there may "
+"be millions of partitions."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml20(title)
-msgid "Object Storage architecture"
+#: ./doc/common/section_objectstorage-ringbuilder.xml61(title)
+msgid "Replica counts"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml27(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml62(para)
 msgid ""
-"Because access servers are collocated in their own tier, you can scale out "
-"read/write access regardless of the storage capacity. For example, if a "
-"cluster is on the public Internet, requires SSL termination, and has a high "
-"demand for data access, you can provision many access servers. However, if "
-"the cluster is on a private network and used primarily for archival "
-"purposes, you need fewer access servers."
+"To support the gradual change in replica counts, a ring can have a real "
+"number of replicas and is not restricted to an integer number of replicas."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml32(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml65(para)
 msgid ""
-"Since this is an HTTP addressable storage service, you may incorporate a "
-"load balancer into the access tier."
+"A fractional replica count is for the whole ring and not for individual "
+"partitions. It indicates the average number of replicas for each partition. "
+"For example, a replica count of 3.2 means that 20 percent of partitions have"
+" four replicas and 80 percent have three replicas."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml34(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml70(para)
+msgid "The replica count is adjustable."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-ringbuilder.xml71(para)
+msgid "Example:"
+msgstr "例:"
+
+#: ./doc/common/section_objectstorage-ringbuilder.xml74(para)
 msgid ""
-"Typically, the tier consists of a collection of 1U servers. These machines "
-"use a moderate amount of RAM and are network I/O intensive. Since these "
-"systems field each incoming API request, you should provision them with two "
-"high-throughput (10GbE) interfaces - one for the incoming \"front-end\" "
-"requests and the other for the \"back-end\" access to the object storage "
-"nodes to put and fetch data."
+"You must rebalance the replica ring in globally distributed clusters. "
+"Operators of these clusters generally want an equal number of replicas and "
+"regions. Therefore, when an operator adds or removes a region, the operator "
+"adds or removes a replica. Removing unneeded replicas saves on the cost of "
+"disks."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml40(title)
-#: ./doc/common/section_objectstorage-arch.xml69(title)
-msgid "Factors to consider"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-arch.xml41(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml80(para)
 msgid ""
-"For most publicly facing deployments as well as private deployments "
-"available across a wide-reaching corporate network, you use SSL to encrypt "
-"traffic to the client. SSL adds significant processing load to establish "
-"sessions between clients, which is why you have to provision more capacity "
-"in the access layer. SSL may not be required for private deployments on "
-"trusted networks."
+"You can gradually increase the replica count at a rate that does not "
+"adversely affect cluster performance."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml49(title)
-msgid "Storage nodes"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-arch.xml50(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml90(para)
 msgid ""
-"In most configurations, each of the five zones should have an equal amount "
-"of storage capacity. Storage nodes use a reasonable amount of memory and "
-"CPU. Metadata needs to be readily available to return objects quickly. The "
-"object stores run services not only to field incoming requests from the "
-"access tier, but to also run replicators, auditors, and reapers. You can "
-"provision object stores provisioned with single gigabit or 10 gigabit "
-"network interface depending on the expected workload and desired "
-"performance."
+"Changes take effect after the ring is rebalanced. Therefore, if you intend "
+"to change from 3 replicas to 3.01 but you accidentally type "
+"<literal>2.01</literal>, no data is lost."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml57(title)
-#: ./doc/common/section_storage-concepts.xml21(td)
-#: ./doc/common/section_objectstorage-characteristics.xml46(title)
-msgid "Object Storage (swift)"
-msgstr "Object Storage (swift)"
+#: ./doc/common/section_objectstorage-ringbuilder.xml95(replaceable)
+msgid "X.builder"
+msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml64(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml94(para)
 msgid ""
-"Currently, a 2TB or 3TB SATA disk delivers good performance for the price. "
-"You can use desktop-grade drives if you have responsive remote hands in the "
-"datacenter and enterprise-grade drives if you don't."
+"Additionally, <placeholder-1/> can now take a decimal argument for the "
+"number of replicas."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml70(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml100(title)
+msgid "Partition shift value"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-ringbuilder.xml101(para)
 msgid ""
-"You should keep in mind the desired I/O performance for single-threaded "
-"requests . This system does not use RAID, so a single disk handles each "
-"request for an object. Disk performance impacts single-threaded response "
-"rates."
+"The partition shift value is known internally to the Ring class as "
+"<literal>_part_shift</literal>. This value is used to shift an MD5 hash to "
+"calculate the partition where the data for that hash should reside. Only the"
+" top four bytes of the hash is used in this process. For example, to compute"
+" the partition for the <literal>/account/container/object</literal> path, "
+"the Python code might look like the following code: <placeholder-1/>"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-arch.xml73(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml112(para)
 msgid ""
-"To achieve apparent higher throughput, the object storage system is designed"
-" to handle concurrent uploads/downloads. The network I/O capacity (1GbE, "
-"bonded 1GbE pair, or 10GbE) should match your desired concurrent throughput "
-"needs for reads and writes."
+"For a ring generated with part_power P, the partition shift value is "
+"<literal>32 - P</literal>."
 msgstr ""
 
-#: ./doc/common/section_dochistory.xml6(title)
-msgid "Document change history"
-msgstr "ドキュメント変更履歴"
+#: ./doc/common/section_objectstorage-ringbuilder.xml116(title)
+msgid "Build the ring"
+msgstr ""
 
-#: ./doc/common/section_dochistory.xml8(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml117(para)
+msgid "The ring builder process includes these high-level steps:"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-ringbuilder.xml121(para)
 msgid ""
-"This version of the guide replaces and obsoletes all previous versions. The "
-"following table describes the most recent changes:"
-msgstr "このバージョンのガイドはすべての旧バージョンを置き換え、廃止します。以下の表はもっとも最近の変更点を記載しています。"
+"The utility calculates the number of partitions to assign to each device "
+"based on the weight of the device. For example, for a partition at the power"
+" of 20, the ring has 1,048,576 partitions. One thousand devices of equal "
+"weight will each want 1,048.576 partitions. The devices are sorted by the "
+"number of partitions they desire and kept in order throughout the "
+"initialization process."
+msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml10(title)
-msgid "Host aggregates"
-msgstr "ホスト・アグリゲート"
-
-#: ./doc/common/section_cli_nova_host_aggregates.xml11(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml131(para)
 msgid ""
-"Host aggregates are a mechanism to further partition an availability zone; "
-"while availability zones are visible to users, host aggregates are only "
-"visible to administrators. Host Aggregates provide a mechanism to allow "
-"administrators to assign key-value pairs to groups of machines. Each node "
-"can have multiple aggregates, each aggregate can have multiple key-value "
-"pairs, and the same key-value pair can be assigned to multiple aggregates. "
-"This information can be used in the scheduler to enable advanced scheduling,"
-" to set up hypervisor resource pools or to define logical groups for "
-"migration."
+"Each device is also assigned a random tiebreaker value that is used when two"
+" devices desire the same number of partitions. This tiebreaker is not stored"
+" on disk anywhere, and so two different rings created with the same "
+"parameters will have different partition assignments. For repeatable "
+"partition assignments, <literal>RingBuilder.rebalance()</literal> takes an "
+"optional seed value that seeds the Python pseudo-random number generator."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml23(title)
-msgid "Command-line interface"
-msgstr "コマンドラインインターフェース"
-
-#: ./doc/common/section_cli_nova_host_aggregates.xml35(replaceable)
-#: ./doc/common/section_cli_nova_host_aggregates.xml111(replaceable)
-msgid "&lt;name&gt;"
-msgstr "&lt;name&gt;"
-
-#: ./doc/common/section_cli_nova_host_aggregates.xml36(replaceable)
-msgid "&lt;availability-zone&gt;"
-msgstr "&lt;availability-zone&gt;"
-
-#: ./doc/common/section_cli_nova_host_aggregates.xml38(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml145(para)
 msgid ""
-"Create a new aggregate named <replaceable>&lt;name&gt;</replaceable> in "
-"availability zone <replaceable>&lt;availability-zone&gt;</replaceable>. "
-"Returns the ID of the newly created aggregate. Hosts can be made available "
-"to multiple availability zones, but administrators should be careful when "
-"adding the host to a different host aggregate within the same availability "
-"zone and pay attention when using the <placeholder-1/> and <placeholder-2/> "
-"commands to avoid user confusion when they boot instances in different "
-"availability zones. An error occurs if you cannot add a particular host to "
-"an aggregate zone for which it is not intended."
+"The ring builder assigns each partition replica to the device that requires "
+"most partitions at that point while keeping it as far away as possible from "
+"other replicas. The ring builder prefers to assign a replica to a device in "
+"a region that does not already have a replica. If no such region is "
+"available, the ring builder searches for a device in a different zone, or on"
+" a different server. If it does not find one, it looks for a device with no "
+"replicas. Finally, if all options are exhausted, the ring builder assigns "
+"the replica to the device that has the fewest replicas already assigned."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml60(replaceable)
-#: ./doc/common/section_cli_nova_host_aggregates.xml68(replaceable)
-#: ./doc/common/section_cli_nova_host_aggregates.xml76(replaceable)
-#: ./doc/common/section_cli_nova_host_aggregates.xml87(replaceable)
-#: ./doc/common/section_cli_nova_host_aggregates.xml98(replaceable)
-#: ./doc/common/section_cli_nova_host_aggregates.xml110(replaceable)
-msgid "&lt;id&gt;"
-msgstr "&lt;id&gt;"
-
-#: ./doc/common/section_cli_nova_host_aggregates.xml62(para)
-msgid "Delete an aggregate with id <replaceable>&lt;id&gt;</replaceable>."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_host_aggregates.xml70(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml159(para)
 msgid ""
-"Show details of the aggregate with id <replaceable>&lt;id&gt;</replaceable>."
+"The ring builder assigns multiple replicas to one device only if the ring "
+"has fewer devices than it has replicas."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml77(replaceable)
-#: ./doc/common/section_cli_nova_host_aggregates.xml88(replaceable)
-msgid "&lt;host&gt;"
-msgstr "&lt;host&gt;"
-
-#: ./doc/common/section_cli_nova_host_aggregates.xml79(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml165(para)
 msgid ""
-"Add host with name <replaceable>&lt;host&gt;</replaceable> to aggregate with"
-" id <replaceable>&lt;id&gt;</replaceable>."
+"When building a new ring from an old ring, the ring builder recalculates the"
+" desired number of partitions that each device wants."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml90(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml174(para)
 msgid ""
-"Remove the host with name <replaceable>&lt;host&gt;</replaceable> from the "
-"aggregate with id <replaceable>&lt;id&gt;</replaceable>."
+"The ring builder unassigns any assigned partitions from any removed devices "
+"and adds these partitions to the gathered list."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml99(replaceable)
-#: ./doc/common/section_cli_nova_host_aggregates.xml100(replaceable)
-msgid "&lt;key=value&gt;"
-msgstr "&lt;key=value&gt;"
-
-#: ./doc/common/section_cli_nova_host_aggregates.xml103(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml180(para)
 msgid ""
-"Add or update metadata (key-value pairs) associated with the aggregate with "
-"id <replaceable>&lt;id&gt;</replaceable>."
+"The ring builder unassigns any partition replicas that can be spread out for"
+" better durability and adds these partitions to the gathered list."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml112(replaceable)
-msgid "&lt;availability_zone&gt;"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_host_aggregates.xml114(para)
-msgid "Update the name and availability zone (optional) for the aggregate."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_host_aggregates.xml128(para)
-msgid "Put/resume host into/from maintenance."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_host_aggregates.xml24(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml187(para)
 msgid ""
-"The <placeholder-1/> command-line tool supports the following aggregate-"
-"related commands. <placeholder-2/>"
+"The ring builder unassigns random partitions from any devices that have more"
+" partitions than they need and adds these partitions to the gathered list."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml134(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml170(para)
 msgid ""
-"Only administrators can access these commands. If you try to use these "
-"commands and the user name and tenant that you use to access the Compute "
-"service do not have the <literal>admin</literal> role or the appropriate "
-"privileges, these errors occur:"
+"The ring builder unassigns partitions and gathers these partitions for "
+"reassignment, as follows: <placeholder-1/>"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml146(title)
-msgid "Configure scheduler to support host aggregates"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_host_aggregates.xml147(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml197(para)
 msgid ""
-"One common use case for host aggregates is when you want to support "
-"scheduling instances to a subset of compute hosts because they have a "
-"specific capability. For example, you may want to allow users to request "
-"compute hosts that have SSD drives if they need access to faster disk I/O, "
-"or access to compute hosts that have GPU cards to take advantage of GPU-"
-"accelerated code."
+"The ring builder reassigns the gathered partitions to devices by using a "
+"similar method to the one described previously."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml154(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml202(para)
 msgid ""
-"To configure the scheduler to support host aggregates, the "
-"<literal>scheduler_default_filters</literal> configuration option must "
-"contain the <literal>AggregateInstanceExtraSpecsFilter</literal> in addition"
-" to the other filters used by the scheduler. Add the following line to "
-"<filename>/etc/nova/nova.conf</filename> on the host that runs the "
-"<systemitem class=\"service\">nova-scheduler</systemitem> service to enable "
-"host aggregates filtering, as well as the other filters that are typically "
-"enabled:<placeholder-1/>"
+"When the ring builder reassigns a replica to a partition, the ring builder "
+"records the time of the reassignment. The ring builder uses this value when "
+"it gathers partitions for reassignment so that no partition is moved twice "
+"in a configurable amount of time. The RingBuilder class knows this "
+"configurable amount of time as <literal>min_part_hours</literal>. The ring "
+"builder ignores this restriction for replicas of partitions on removed "
+"devices because removal of a device happens on device failure only, and "
+"reassignment is the only choice."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml168(title)
-msgid "Example: Specify compute hosts with SSDs"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_host_aggregates.xml169(para)
+#: ./doc/common/section_objectstorage-ringbuilder.xml216(para)
 msgid ""
-"This example configures the Compute service to enable users to request nodes"
-" that have solid-state drives (SSDs). You create a <literal>fast-"
-"io</literal> host aggregate in the <literal>nova</literal> availability zone"
-" and you add the <literal>ssd=true</literal> key-value pair to the "
-"aggregate. Then, you add the <literal>node1</literal>, and "
-"<literal>node2</literal> compute nodes to it."
+"Theses steps do not always perfectly rebalance a ring due to the random "
+"nature of gathering partitions for reassignment. To help reach a more "
+"balanced ring, the rebalance process is repeated until near perfect (less "
+"than 1 percent off) or when the balance does not improve by at least 1 "
+"percent (indicating we probably cannot get perfect balance due to wildly "
+"imbalanced zones or too many partitions recently moved)."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml204(para)
+#: ./doc/common/section_keystone-ssl-config.xml7(title)
+msgid "Configure the Identity Service with SSL"
+msgstr ""
+
+#: ./doc/common/section_keystone-ssl-config.xml8(para)
+msgid "You can configure the Identity Service to support two-way SSL."
+msgstr ""
+
+#: ./doc/common/section_keystone-ssl-config.xml10(para)
+msgid "You must obtain the x509 certificates externally and configure them."
+msgstr ""
+
+#: ./doc/common/section_keystone-ssl-config.xml12(para)
 msgid ""
-"Use the <placeholder-1/> command to create the "
-"<replaceable>ssd.large</replaceable> flavor called with an ID of 6, 8GB of "
-"RAM, 80GB root disk, and four vCPUs."
+"The Identity Service provides a set of sample certificates in the <filename "
+"class=\"directory\">examples/pki/certs</filename> and <filename "
+"class=\"directory\">examples/pki/private</filename> directories:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml207(replaceable)
-#: ./doc/common/section_cli_nova_host_aggregates.xml219(replaceable)
-msgid "ssd.large"
+#: ./doc/common/section_keystone-ssl-config.xml18(title)
+msgid "Certificate types"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml207(replaceable)
-msgid "6"
+#: ./doc/common/section_keystone-ssl-config.xml20(term)
+msgid "cacert.pem"
+msgstr "cacert.pem"
+
+#: ./doc/common/section_keystone-ssl-config.xml22(para)
+msgid "Certificate Authority chain to validate against."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml207(replaceable)
-msgid "8192"
+#: ./doc/common/section_keystone-ssl-config.xml27(term)
+msgid "ssl_cert.pem"
+msgstr "ssl_cert.pem"
+
+#: ./doc/common/section_keystone-ssl-config.xml29(para)
+msgid "Public certificate for Identity Service server."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml207(replaceable)
-msgid "80"
-msgstr "80"
+#: ./doc/common/section_keystone-ssl-config.xml34(term)
+msgid "middleware.pem"
+msgstr "middleware.pem"
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml207(replaceable)
-msgid "4"
-msgstr "4"
+#: ./doc/common/section_keystone-ssl-config.xml36(para)
+msgid "Public and private certificate for Identity Service middleware/client."
+msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml213(para)
+#: ./doc/common/section_keystone-ssl-config.xml41(term)
+msgid "cakey.pem"
+msgstr "cakey.pem"
+
+#: ./doc/common/section_keystone-ssl-config.xml43(para)
+msgid "Private key for the CA."
+msgstr "CA の秘密鍵。"
+
+#: ./doc/common/section_keystone-ssl-config.xml47(term)
+msgid "ssl_key.pem"
+msgstr "ssl_key.pem"
+
+#: ./doc/common/section_keystone-ssl-config.xml49(para)
+msgid "Private key for the Identity Service server."
+msgstr ""
+
+#: ./doc/common/section_keystone-ssl-config.xml55(para)
 msgid ""
-"Once the flavor is created, specify one or more key-value pairs that match "
-"the key-value pairs on the host aggregates. In this case, that is the "
-"<replaceable>ssd=true</replaceable> key-value pair. Setting a key-value pair"
-" on a flavor is done using the <placeholder-1/> command."
+"You can choose names for these certificates. You can also combine the "
+"public/private keys in the same file, if you wish. These certificates are "
+"provided as an example."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml219(replaceable)
-msgid "ssd=true"
+#: ./doc/common/section_keystone-ssl-config.xml61(title)
+msgid "SSL configuration"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml220(para)
+#: ./doc/common/section_keystone-ssl-config.xml62(para)
 msgid ""
-"Once it is set, you should see the <literal>extra_specs</literal> property "
-"of the <literal>ssd.large</literal> flavor populated with a key of "
-"<literal>ssd</literal> and a corresponding value of <literal>true</literal>."
+"To enable SSL with client authentication, modify the "
+"<literal>[ssl]</literal> section in the "
+"<filename>etc/keystone.conf</filename> file. The following SSL configuration"
+" example uses the included sample certificates:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml241(para)
-msgid ""
-"Now, when a user requests an instance with the <literal>ssd.large</literal> "
-"flavor, the scheduler only considers hosts with the "
-"<literal>ssd=true</literal> key-value pair. In this example, these are "
-"<literal>node1</literal> and <literal>node2</literal>."
+#: ./doc/common/section_keystone-ssl-config.xml74(title)
+msgid "Options"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml249(title)
-msgid "XenServer hypervisor pools to support live migration"
+#: ./doc/common/section_keystone-ssl-config.xml76(para)
+msgid "<literal>enable</literal>. True enables SSL. Default is False."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_host_aggregates.xml251(para)
+#: ./doc/common/section_keystone-ssl-config.xml80(para)
 msgid ""
-"When using the XenAPI-based hypervisor, the Compute service uses host "
-"aggregates to manage XenServer Resource pools, which are used in supporting "
-"live migration."
+"<literal>certfile</literal>. Path to the Identity Service public certificate"
+" file."
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml6(title)
-msgid "Migrate the Identity Service database"
+#: ./doc/common/section_keystone-ssl-config.xml84(para)
+msgid ""
+"<literal>keyfile</literal>. Path to the Identity Service private certificate"
+" file. If you include the private key in the certfile, you can omit the "
+"keyfile."
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml7(para)
-msgid ""
-"Between revisions of the Identity Service project, you might need to "
-"complete SQL migrations. The Identity Service project uses SQLAlchemy-"
-"migrate (see <link href=\"http://code.google.com/p/sqlalchemy-"
-"migrate/\">http://code.google.com/p/sqlalchemy-migrate/</link>) to migrate "
-"the SQL database between revisions. For core components, the source code "
-"stores migrations in a central repository under a "
-"<filename>keystone/common/sql/migrate_repo</filename> directory."
+#: ./doc/common/section_keystone-ssl-config.xml90(para)
+msgid "<literal>ca_certs</literal>. Path to the CA trust chain."
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml17(para)
+#: ./doc/common/section_keystone-ssl-config.xml94(para)
 msgid ""
-"Extensions to the Identity Service might also require SQL migrations. The "
-"directory <filename>keystone/contrib/example</filename> in the keystone "
-"repository contains a sample extension migration."
+"<literal>cert_required</literal>. Requires client certificate. Default is "
+"False."
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml23(title)
-msgid "To set up a migration for an extension"
+#: ./doc/common/section_cli_keystone_apiv3.xml5(title)
+msgid "Use Identity Service API v3 instead of API v2.0"
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml25(para)
+#: ./doc/common/section_cli_keystone_apiv3.xml6(para)
 msgid ""
-"Create a directory structure where <literal>my_extension</literal> is the "
-"name of the extension, as follows: "
-"<filename>keystone/contrib/my_extension/migrate_repo/versions/</filename>."
+"Use the following parameters in combination on any keystone command to "
+"specify which version of the API to use:"
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml31(para)
+#: ./doc/common/section_cli_keystone_apiv3.xml11(para)
 msgid ""
-"Create empty <filename>__init__.py</filename> files in the "
-"<filename>migrate_repo</filename> and <filename>versions</filename> "
-"subdirectories."
+"<parameter>--os-endpoint</parameter>. The endpoint to use instead of the one"
+" in the service catalog. Defaults to <code>env[OS_SERVICE_ENDPOINT]</code>."
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml37(para)
+#: ./doc/common/section_cli_keystone_apiv3.xml15(para)
 msgid ""
-"Create a <filename>migrate.cfg</filename> configuration file in the "
-"<filename>migrate_repo</filename> subdirectory, which conforms to a "
-"key/value <filename>.ini</filename> file format."
+"The <literal>keystone</literal> client detects the version of the API from "
+"this parameter."
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml41(para)
-msgid "An example configuration file:"
+#: ./doc/common/section_cli_keystone_apiv3.xml19(para)
+msgid ""
+"<parameter>--os-auth_url</parameter>. The Identity Service endpoint to use "
+"for authentication. Defaults to <code>env[OS_AUTH_URL]</code>."
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml49(title)
-msgid "To test a migration for a specific extension"
+#: ./doc/common/section_cli_keystone_apiv3.xml25(para)
+msgid ""
+"<parameter>--os-identity-api-version</parameter>. The Identity Service API "
+"version. Defaults to <code>env[OS_IDENTITY_API_VERSION]</code> or "
+"<literal>2.0</literal>."
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml50(para)
-msgid ""
-"You can use the <placeholder-1/> command with the "
-"<parameter>--extension</parameter> parameter for both the <placeholder-2/> "
-"and <placeholder-3/> commands. Ensure that the required configuration files "
-"exist before completing these steps."
+#: ./doc/common/section_cli_keystone_apiv3.xml31(para)
+msgid "For example, use the following parameters to use API v3:"
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml57(para)
-msgid "Test your migrations with an <literal>example</literal> extension:"
+#: ./doc/common/section_cli_keystone_apiv3.xml33(parameter)
+#: ./doc/common/section_cli_keystone_apiv3.xml35(parameter)
+msgid "--os-auth_url"
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml62(para)
-msgid "Migrate to version 1:"
+#: ./doc/common/section_cli_keystone_apiv3.xml33(parameter)
+#: ./doc/common/section_cli_keystone_apiv3.xml35(parameter)
+msgid "--os-identity-api-version"
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml66(para)
-msgid "Migrate back to version 0:"
+#: ./doc/common/section_cli_keystone_apiv3.xml34(para)
+msgid "Use the following parameters to use API v2.0:"
 msgstr ""
 
-#: ./doc/common/section_keystone_db_sync.xml70(para)
-msgid "Check the version:"
+#: ./doc/common/section_conventions.xml8(title)
+msgid "Conventions"
+msgstr "表記規則"
+
+#: ./doc/common/section_conventions.xml9(para)
+msgid "The OpenStack documentation uses several typesetting conventions."
+msgstr "OpenStack のドキュメントは、いくつかの植字の表記方法を採用しています。"
+
+#: ./doc/common/section_conventions.xml13(title)
+msgid "Notices"
+msgstr "注意"
+
+#: ./doc/common/section_conventions.xml14(para)
+msgid "Notices take three forms:"
+msgstr "注意には以下の 3 種類があります。"
+
+#: ./doc/common/section_conventions.xml16(para)
+msgid ""
+"The information in a note is usually in the form of a handy tip or reminder."
+msgstr "注記にある情報は一般的にちょっとしたヒントや備忘録の形式をとります。"
+
+#: ./doc/common/section_conventions.xml20(para)
+msgid ""
+"The information in an important notice is something you must be aware of "
+"before proceeding."
+msgstr "重要にある情報は続行する前に注意する必要があります。"
+
+#: ./doc/common/section_conventions.xml24(para)
+msgid ""
+"The information in warnings is critical. Warnings provide additional "
+"information about risk of data loss or security issues."
+msgstr "警告にある情報は致命的なものです。データ損失やセキュリティ問題のリスクに関する追加情報が提供されます。"
+
+#: ./doc/common/section_conventions.xml31(title)
+msgid "Command prompts"
+msgstr "コマンドプロンプト"
+
+#: ./doc/common/section_conventions.xml32(para)
+msgid ""
+"Commands prefixed with the <literal>#</literal> prompt are to be executed by"
+" the <literal>root</literal> user. These examples can also be executed by "
+"using the <placeholder-1/> command, if available."
+msgstr "<literal>#</literal> プロンプトから始まるコマンドは、<literal>root</literal> ユーザーにより実行されます。これらの例は、利用可能ならば、<placeholder-1/> コマンドを用いて実行することもできます。"
+
+#: ./doc/common/section_conventions.xml36(para)
+msgid ""
+"Commands prefixed with the <literal>$</literal> prompt can be executed by "
+"any user, including <literal>root</literal>."
+msgstr "<literal>$</literal> プロンプトから始まるコマンドは、<literal>root</literal> を含む、すべてのユーザーにより実行できます。"
+
+#: ./doc/common/ch_cli_ceilometer_commands.xml11(title)
+msgid "Telemetry command-line client"
 msgstr ""
 
-#: ./doc/common/section_getstart_trove.xml5(title)
-msgid "Database service overview"
-msgstr "Database の概要"
-
-#: ./doc/common/section_getstart_trove.xml6(para)
-msgid ""
-"The Database service provides scalable and reliable cloud provisioning "
-"functionality for both relational and non-relational database engines. Users"
-" can quickly and easily utilize database features without the burden of "
-"handling complex administrative tasks. Cloud users and database "
-"administrators can provision and manage multiple database instances as "
-"needed."
-msgstr "Database は、リレーショナルデータベースと非リレーショナルデータベースの両方のエンジン向けにスケール可能な信頼できるクラウド展開機能を提供します。ユーザーは、複雑な管理作業を実行することなく、迅速かつ容易にデータベース機能を利用できます。クラウドのユーザーとデータベース管理者は、必要に応じて複数のデータベースインスタンスを展開、管理できます。"
-
-#: ./doc/common/section_getstart_trove.xml7(para)
-msgid ""
-"The Database service provides resource isolation at high performance levels,"
-" and automates complex administrative tasks such as deployment, "
-"configuration, patching, backups, restores, and monitoring."
-msgstr "Database は、高性能にリソースを分割でき、配備、設定、パッチ適用、バックアップ、リストア、監視などの複雑な管理作業を自動化します。"
-
-#: ./doc/common/section_getstart_trove.xml9(title)
-msgid "Process flow example."
-msgstr "プロセスフロー例。"
-
-#: ./doc/common/section_getstart_trove.xml9(para)
-msgid "Here is a high-level process flow example for using Database services:"
-msgstr "これは、Database のサービスを利用するための、高レベルなプロセスフローの例です。"
-
-#: ./doc/common/section_getstart_trove.xml12(para)
-msgid "Administrator sets up infrastructure:"
-msgstr "管理者がインフラストラクチャーをセットアップします。"
-
-#: ./doc/common/section_getstart_trove.xml15(para)
-msgid "OpenStack administrator installs the Database service."
-msgstr "OpenStack 管理者が Database をインストールします。"
-
-#: ./doc/common/section_getstart_trove.xml18(para)
-msgid ""
-"She creates one image for each type of database the administrator wants to "
-"have (one for MySQL, one for MongoDB, and so on)."
-msgstr "管理者が使用したいデータベース種別ごとのイメージを作成します。例えば、MySQL、MongoDB などです。"
-
-#: ./doc/common/section_getstart_trove.xml23(para)
-msgid ""
-"OpenStack administrator updates the datastore to use the new images, using "
-"the <placeholder-1/> command."
-msgstr "OpenStack 管理者は、新しいイメージを使用するために、<placeholder-1/> コマンドを使用して、データストアを更新します。"
-
-#: ./doc/common/section_getstart_trove.xml30(para)
-msgid "End user uses database service:"
-msgstr "エンドユーザーがデータベースのサービスを使用します。"
-
-#: ./doc/common/section_getstart_trove.xml33(para)
-msgid ""
-"Now that the basic infrastructure is set up, an end user can create a Trove "
-"instance (database) whenever the user wants, using the <placeholder-1/> "
-"command."
-msgstr "ここまでに基本的なインフラストラクチャーがセットアップされました。エンドユーザーが、使用したいときに <placeholder-1/> コマンドを使用して、Trove インスタンス (データベース) を作成できます。"
-
-#: ./doc/common/section_getstart_trove.xml41(replaceable)
-msgid "instanceID"
-msgstr "instanceID"
-
-#: ./doc/common/section_getstart_trove.xml39(para)
-msgid ""
-"The end user gets the IP address of the Trove instance by using the "
-"<placeholder-1/> command to get the ID of the instance, and then using the "
-"<placeholder-2/> command to get the IP address."
-msgstr "エンドユーザーは、インスタンスの ID を取得するために <placeholder-1/> コマンドを使用し、IP アドレスを取得するために <placeholder-2/> コマンドを使用することにより、Trove インスタンスの IP アドレスを取得します。"
-
-#: ./doc/common/section_getstart_trove.xml44(para)
-msgid ""
-"The end user can now access the Trove instance using typical database access"
-" commands. MySQL example:"
-msgstr "エンドユーザーは、一般的なデータベースアクセスコマンドを使用して、Trove インスタンスにアクセスできます。MySQL の例:"
-
-#: ./doc/common/section_getstart_trove.xml45(replaceable)
-msgid "trove_ip_address"
-msgstr "trove_ip_address"
-
-#: ./doc/common/section_getstart_trove.xml51(title)
-msgid "Components:"
-msgstr "コンポーネント:"
-
-#: ./doc/common/section_getstart_trove.xml51(para)
-msgid "The Database service includes the following components:"
-msgstr "Database は以下のコンポーネントを含みます。"
-
-#: ./doc/common/section_getstart_trove.xml55(para)
-msgid ""
-"<code>python-troveclient</code> command-line client. A CLI that communicates"
-" with the <code>trove-api</code> component."
-msgstr "<code>python-troveclient</code> コマンドラインクライアント。<code>trove-api</code> コンポーネントと通信する CLI。"
-
-#: ./doc/common/section_getstart_trove.xml58(para)
-msgid ""
-"<code>trove-api</code> component. Provides an OpenStack-native RESTful API "
-"that supports JSON to provision and manage Trove instances."
-msgstr "<code>trove-api</code> コンポーネント。Trove インスタンスを展開、管理するために JSON をサポートする、OpenStack ネイティブ RESTful API を提供します。"
-
-#: ./doc/common/section_getstart_trove.xml62(para)
-msgid ""
-"<code>trove-conductor</code> service. Runs on the host, and receives "
-"messages from guest instances that want to update information on the host."
-msgstr "<code>trove-conductor</code> サービス。ホストで実行し、ホストに情報をアップロードしたいゲストインスタンスからのメッセージを受け取ります。"
-
-#: ./doc/common/section_getstart_trove.xml65(para)
-msgid ""
-"<code>trove-taskmanager</code> service. Instruments the complex system flows"
-" that support provisioning instances, managing the lifecycle of instances, "
-"and performing operations on instances."
-msgstr "<code>trove-taskmanager</code> サービス。インスタンスの展開、インスタンスのライフサイクルの管理、インスタンス上の処理の実行をサポートする複雑なシステムフローを備えます。"
-
-#: ./doc/common/section_getstart_trove.xml68(para)
-msgid ""
-"<code>trove-guestagent</code> service. Runs within the guest instance. "
-"Manages and performs operations on the database itself."
-msgstr "<code>trove-guestagent</code> サービス。ゲストインスタンスの中で実行します。データベース自身の処理を管理、実行します。"
-
-#: ./doc/common/ch_cli_swift_commands.xml11(title)
-msgid "Object Storage command-line client"
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml12(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml12(para)
 msgid ""
 "The <placeholder-1/> client is the command-line interface (CLI) for the "
-"OpenStack Object Storage API and its extensions. This chapter documents "
-"<placeholder-2/> version 2.1.0."
+"Telemetry API and its extensions. This chapter documents <placeholder-2/> "
+"version 1.0.10."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml22(title)
-msgid "swift usage"
+#: ./doc/common/ch_cli_ceilometer_commands.xml22(title)
+msgid "ceilometer usage"
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml41(para)
-#: ./doc/common/ch_cli_swift_commands.xml335(para)
-msgid "Delete a container or objects within a container."
+#: ./doc/common/ch_cli_ceilometer_commands.xml42(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml459(para)
+msgid "Create a new alarm based on state of other alarms."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml49(para)
-#: ./doc/common/ch_cli_swift_commands.xml399(para)
-msgid "Download objects from containers."
+#: ./doc/common/ch_cli_ceilometer_commands.xml50(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml601(para)
+msgid "Update an existing alarm based on state of other alarms."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml57(para)
-#: ./doc/common/ch_cli_swift_commands.xml513(para)
-msgid "Lists the containers for the account or the objects for a container."
+#: ./doc/common/ch_cli_ceilometer_commands.xml59(para)
+msgid "Create a new alarm (Deprecated). Use alarm-threshold- create instead."
 msgstr ""
 
-#: ./doc/common/ch_cli_swift_commands.xml66(para)
-msgid ""
-"Updates meta information for the account, container, or object; creates "
-"containers if not present."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml75(para)
-#: ./doc/common/ch_cli_swift_commands.xml661(para)
-msgid "Displays information for the account, container, or object."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml84(para)
-msgid "Uploads files or directories to the given container."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml92(para)
-msgid "List cluster capabilities."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml100(title)
-msgid "swift examples"
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml110(title)
-msgid "swift optional arguments"
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml131(para)
-msgid "Use SERVICENET internal network."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml139(para)
-msgid "Print more info."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml147(para)
-msgid ""
-"Show the curl commands and results of all http queries regardless of result "
-"status."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml156(para)
-msgid ""
-"Show the curl commands and results of all http queries which return an "
-"error."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml165(para)
-msgid "Suppress status output."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml173(para)
-msgid "for obtaining an auth token."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml181(para)
-msgid "Specify a version for authentication. Defaults to 1.0."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml189(para)
-msgid "User name for obtaining an auth token."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml197(para)
-msgid "Key for obtaining an auth token."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml205(para)
-msgid "The number of times to retry a failed connection."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml213(para)
-msgid "OpenStack username. Defaults to <code>env[OS_USERNAME]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml221(para)
-msgid "OpenStack password. Defaults to <code>env[OS_PASSWORD]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml229(para)
-msgid "OpenStack tenant ID. Defaults to <code>env[OS_TENANT_ID]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml237(para)
-msgid "OpenStack tenant name. Defaults to <code>env[OS_TENANT_NAME]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml246(para)
-msgid "OpenStack auth URL. Defaults to <code>env[OS_AUTH_URL]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml254(para)
-msgid ""
-"OpenStack token. Defaults to <code>env[OS_AUTH_TOKEN]</code>. Used with "
-"--os-storage-url to bypass the usual username/password authentication."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml264(para)
-msgid ""
-"OpenStack storage URL. Defaults to <code>env[OS_STORAGE_URL]</code>. "
-"Overrides the storage url returned during auth. Will bypass authentication "
-"when used with --os-auth-token."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml275(para)
-msgid "OpenStack region name. Defaults to <code>env[OS_REGION_NAME]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml284(para)
-msgid "OpenStack Service type. Defaults to <code>env[OS_SERVICE_TYPE]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml293(para)
-msgid ""
-"OpenStack Endpoint type. Defaults to <code>env[OS_ENDPOINT_TYPE]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml312(para)
-msgid ""
-"Allow swiftclient to access servers without having to verify the SSL "
-"certificate. Defaults to <code>env[SWIFTCLIENT_INSECURE]</code> (set to "
-"'true' to enable)."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml322(para)
-msgid ""
-"This option is deprecated and not used anymore. SSL compression should be "
-"disabled by default by the system SSL library."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml332(title)
-msgid "swift delete command"
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml342(para)
-msgid "Name of container to delete from."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml350(para)
-msgid "Name of object to delete. Specify multiple times for multiple objects."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml362(para)
-msgid "Delete all containers and objects."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml370(para)
-msgid "Do not delete segments of manifest objects."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml378(para)
-msgid "Number of threads to use for deleting objects. Default is 10."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml387(para)
-msgid "Number of threads to use for deleting containers. Default is 10."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml396(title)
-msgid "swift download command"
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml406(para)
-msgid ""
-"Name of container to download from. To download a whole account, omit this "
-"and specify --all."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml415(para)
-msgid ""
-"Name of object to download. Specify multiple times for multiple objects. "
-"Omit this to download all objects from the container."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml428(para)
-msgid "Indicates that you really want to download everything in the account."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml437(para)
-msgid "Marker to use when starting a container or account download."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml446(para)
-msgid "Only download items beginning with &lt;prefix&gt;."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml454(para)
-msgid ""
-"For a single file download, stream the output to &lt;out_file&gt;. "
-"Specifying \"-\" as &lt;out_file&gt; will redirect to stdout."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml464(para)
-msgid "Number of threads to use for downloading objects. Default is 10"
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml473(para)
-msgid "Number of threads to use for downloading containers. Default is 10"
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml482(para)
-msgid "Perform download(s), but don't actually write anything to disk."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml491(para)
-msgid ""
-"Adds a customized request header to the query, like \"Range\" or \"If-"
-"Match\". This argument is repeatable. Example --header \"content-"
-"type:text/plain\""
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml501(para)
-msgid "Skip downloading files that are identical on both sides."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml510(title)
-msgid "swift list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml520(para)
-msgid "Name of container to list object in."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml531(para)
-msgid "Long listing format, similar to ls -l."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml539(para)
-#: ./doc/common/ch_cli_swift_commands.xml688(para)
-msgid "Report sizes in human readable format similar to ls -lh."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml548(para)
-msgid "Used with -l or --lh, only report totals."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml556(para)
-msgid "Only list items beginning with the prefix."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml564(para)
-msgid ""
-"Roll up items with the given delimiter. For containers only. See OpenStack "
-"Swift API documentation for what this means."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml574(title)
-msgid "swift post command"
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml577(para)
-msgid ""
-"Updates meta information for the account, container, or object. If the "
-"container is not found, it will be created automatically."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml585(para)
-msgid "Name of container to post to."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml593(para)
-msgid "Name of object to post. Specify multiple times for multiple objects."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml605(para)
-msgid ""
-"Read ACL for containers. Quick summary of ACL syntax: .r:*, "
-".r:-.example.com, .r:www.example.com, account1, account2:user2"
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml615(para)
-msgid ""
-"Write ACL for containers. Quick summary of ACL syntax: account1 "
-"account2:user2"
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml624(para)
-msgid "Sync To for containers, for multi-cluster replication."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml632(para)
-msgid "Sync Key for containers, for multi-cluster replication."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml640(para)
-msgid ""
-"Sets a meta data item. This option may be repeated. Example: -m Color:Blue "
-"-m Size:Large"
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml649(para)
-msgid ""
-"Set request headers. This option may be repeated. Example -H \"content-"
-"type:text/plain\""
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml658(title)
-msgid "swift stat command"
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml668(para)
-msgid "Name of container to stat from."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml676(para)
-msgid "Name of object to stat. Specify multiple times for multiple objects."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml697(title)
-msgid "swift upload command"
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml700(para)
-msgid "Uploads specified files and directories to the given container."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml707(para)
-msgid "Name of container to upload to."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml715(para)
-msgid ""
-"Name of file or directory to upload. Specify multiple times for multiple "
-"uploads."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml727(para)
-msgid "Only upload files that have changed since the last upload."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml736(para)
-msgid "Skip uploading files that are identical on both sides."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml744(para)
-msgid ""
-"Upload files in segments no larger than &lt;size&gt; (in Bytes) and then "
-"create a \"manifest\" file that will download all the segments as if it were"
-" the original file."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml755(para)
-msgid ""
-"Upload the segments into the specified container. If not specified, the "
-"segments will be uploaded to a &lt;container&gt;_segments container to not "
-"pollute the main &lt;container&gt; listings."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml766(para)
-msgid ""
-"Indicates that you want the older segments of manifest objects left alone "
-"(in the case of overwrites)."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml775(para)
-msgid "Number of threads to use for uploading full objects. Default is 10."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml784(para)
-msgid "Number of threads to use for uploading object segments. Default is 10."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml793(para)
-msgid ""
-"Set request headers with the syntax header:value. This option may be "
-"repeated. Example -H \"content-type:text/plain\"."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml803(para)
-msgid ""
-"When used in conjunction with --segment-size it will create a Static Large "
-"Object instead of the default Dynamic Large Object."
-msgstr ""
-
-#: ./doc/common/ch_cli_swift_commands.xml813(para)
-msgid ""
-"Upload file and name object to &lt;object-name&gt; or upload dir and use &lt"
-";object-name&gt; as object prefix instead of folder name."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml6(title)
-msgid "Manage Networking service quotas"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml7(para)
-msgid ""
-"A quota limits the number of available resources. A default quota might be "
-"enforced for all tenants. When you try to create more resources than the "
-"quota allows, an error occurs:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml12(para)
-msgid ""
-"Per-tenant quota configuration is also supported by the quota extension API."
-" See <link linkend=\"cfg_quotas_per_tenant\"> Per-tenant quota "
-"configuration</link> for details."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml16(title)
-msgid "Basic quota configuration"
-msgstr "基本的なクォータ設定"
-
-#: ./doc/common/section_cli_neutron-quotas.xml17(para)
-msgid ""
-"In the Networking default quota mechanism, all tenants have the same quota "
-"values, such as the number of resources that a tenant can create."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml20(para)
-msgid ""
-"The quota value is defined in the OpenStack Networking "
-"<filename>neutron.conf</filename> configuration file. To disable quotas for "
-"a specific resource, such as network, subnet, or port, remove a "
-"corresponding item from <option>quota_items</option>. This example shows the"
-" default quota values:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml41(para)
-msgid ""
-"OpenStack Networking also supports quotas for L3 resources: router and "
-"floating IP. Add these lines to the <literal>quotas</literal> section in the"
-" <filename>neutron.conf</filename> file."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml52(para)
-#: ./doc/common/section_cli_neutron-quotas.xml67(para)
-msgid "The <option>quota_items</option> option does not affect these quotas."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml55(para)
-msgid ""
-"OpenStack Networking also supports quotas for security group resources: "
-"number of security groups and the number of rules for each security group. "
-"Add these lines to the <literal>quotas</literal> section in the "
-"<filename>neutron.conf</filename> file:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml72(title)
-msgid "Configure per-tenant quotas"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml73(para)
-msgid ""
-"OpenStack Networking also supports per-tenant quota limit by quota extension"
-" API."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml77(para)
-msgid "<placeholder-1/>. Deletes defined quotas for a specified tenant."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml81(para)
-msgid "<placeholder-1/>. Lists defined quotas for all tenants."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml85(para)
-msgid "<placeholder-1/>. Shows quotas for a specified tenant."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml89(para)
-msgid "<placeholder-1/>. Updates quotas for a specified tenant."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml75(para)
-msgid ""
-"Use these commands to manage per-tenant quotas:<placeholder-1/>Only users "
-"with the <literal>admin</literal> role can change a quota value. By default,"
-" the default set of quotas are enforced for all tenants, so no "
-"<placeholder-2/> command exists."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml98(title)
-msgid "Configure Networking to show per-tenant quotas"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml99(para)
-msgid ""
-"Set the <literal>quota_driver</literal> option in the "
-"<literal>neutron.conf</literal> file:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml102(para)
-msgid ""
-"When you set this option, the output for Networking commands shows "
-"<literal>quotas</literal>."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml106(title)
-msgid "List Networking extensions"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml107(para)
-msgid "To list the Networking extensions, run this command:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml110(para)
-msgid ""
-"The command shows the <literal>quotas</literal> extension, which provides "
-"per-tenant quota management support:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml128(title)
-msgid "Show information for the quotas extension"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml129(para)
-msgid ""
-"To show information for the <literal>quotas</literal> extension, run this "
-"command:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml143(para)
-msgid ""
-"Only some plug-ins support per-tenant quotas. Specifically, Open vSwitch, "
-"Linux Bridge, and VMware NSX support them, but new versions of other plug-"
-"ins might bring additional functionality. See the documentation for each "
-"plug-in."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml151(title)
-msgid "List tenants who have per-tenant quota support"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml152(para)
-msgid ""
-"The <placeholder-1/> command lists tenants for which the per-tenant quota is"
-" enabled. The command does not list tenants with default quota support. You "
-"must be an administrative user to run this command:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml165(title)
-msgid "Show per-tenant quota values"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml166(para)
-msgid ""
-"The <placeholder-1/> reports the current set of quota limits for the "
-"specified tenant. Non-administrative users can run this command without the "
-"<parameter>--tenant_id</parameter> parameter. If per-tenant quota limits are"
-" not enabled for the tenant, the command shows the default set of quotas:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml182(para)
-msgid ""
-"The following command shows the command output for a non-administrative "
-"user:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml196(title)
-msgid "Update quota values for a specified tenant"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml197(para)
-msgid ""
-"Use the <placeholder-1/> command to update a quota for a specified tenant:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml209(para)
-msgid "You can update quotas for multiple resources through one command:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml221(para)
-msgid ""
-"To update the limits for an L3 resource such as, router or floating IP, you "
-"must define new values for the quotas after the <parameter>--</parameter> "
-"directive."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml224(para)
-msgid ""
-"This example updates the limit of the number of floating IPs for the "
-"specified tenant:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml236(para)
-msgid ""
-"You can update the limits of multiple resources by including L2 resources "
-"and L3 resource through one command."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml251(title)
-msgid "Delete per-tenant quota values"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron-quotas.xml252(para)
-msgid "To clear per-tenant quota limits, use the <placeholder-1/> command:"
-msgstr "テナントごとのクォータ制限を解除するために、<placeholder-1/> コマンドを使用します。"
-
-#: ./doc/common/section_cli_neutron-quotas.xml256(para)
-msgid ""
-"After you run this command, you can see that quota values for the tenant are"
-" reset to the default values:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_terminate.xml8(title)
-msgid "Delete an instance"
-msgstr "インスタンスの削除"
-
-#: ./doc/common/section_cli_nova_terminate.xml9(para)
-msgid "When you no longer need an instance, you can delete it."
-msgstr "インスタンスが必要なくなった場合、インスタンスを削除できます。"
-
-#: ./doc/common/section_cli_nova_terminate.xml11(para)
-msgid "List all instances:"
-msgstr "すべてのインスタンスを一覧表示します。"
-
-#: ./doc/common/section_cli_nova_terminate.xml21(para)
-msgid ""
-"Run the <placeholder-1/> command to delete the instance. The following "
-"example shows deletion of the <filename>newServer</filename> instance, which"
-" is in <literal>ERROR</literal> state:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_terminate.xml24(para)
-msgid "The command does not notify that your server was deleted."
-msgstr "このコマンドでは、インスタンスの削除に関する通知はありません。"
-
-#: ./doc/common/section_cli_nova_terminate.xml25(para)
-msgid ""
-"To verify that the server was deleted, run the <placeholder-1/> command:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_terminate.xml33(para)
-msgid "The deleted instance does not appear in the list."
-msgstr "この一覧には、削除したインスタンスの表示がなくなっています。"
-
-#: ./doc/common/section_cli_keystone_example_usage.xml6(title)
-msgid "keystone command-line client example usage"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_example_usage.xml7(para)
-msgid ""
-"Before you can use keystone client commands, you must download and source an"
-" OpenStack RC file. For information, see the <citetitle>OpenStack Admin User"
-" Guide</citetitle>."
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_example_usage.xml10(para)
-msgid "The keystone command-line client uses the following syntax:"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_example_usage.xml12(replaceable)
-msgid "PARAMETER"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_example_usage.xml12(replaceable)
-msgid "ARGUMENT"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_example_usage.xml13(para)
-msgid ""
-"For example, you can run the <placeholder-1/> and <placeholder-2/> commands,"
-" as follows:"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_example_usage.xml22(replaceable)
-#: ./doc/common/section_cli_keystone_example_usage.xml23(replaceable)
-msgid "token"
-msgstr "トークン"
-
-#: ./doc/common/section_cli_keystone_example_usage.xml22(replaceable)
-#: ./doc/common/section_cli_keystone_example_usage.xml23(replaceable)
-msgid "endpoint"
-msgstr "エンドポイント"
-
-#: ./doc/common/section_cli_keystone_example_usage.xml31(replaceable)
-msgid "id"
-msgstr "id"
-
-#: ./doc/common/section_cli_keystone_example_usage.xml34(para)
-msgid ""
-"For information about using the keystone client commands to create and "
-"manage users, roles, and projects, see the <citetitle>OpenStack Admin User "
-"Guide</citetitle>."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_volumes.xml8(title)
-msgid "Manage Volumes"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_volumes.xml9(para)
-msgid ""
-"Depending on the setup of your cloud provider, they may give you an endpoint"
-" to use to manage volumes, or there may be an extension under the covers. In"
-" either case, you can use the <placeholder-1/> CLI to manage volumes:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_volumes.xml26(para)
-msgid "For example, to list IDs and names of Compute volumes, run:"
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml5(title)
-msgid "OpenStack Object Storage"
-msgstr "OpenStack Object Storage"
-
-#: ./doc/common/section_getstart_object-storage.xml6(para)
-msgid ""
-"The OpenStack Object Storage is a multi-tenant object storage system. It is "
-"highly scalable and can manage large amounts of unstructured data at low "
-"cost through a RESTful HTTP API."
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml11(term)
-msgid ""
-"Proxy servers (<systemitem class=\"service\">swift-proxy-"
-"server</systemitem>)"
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml13(para)
-msgid ""
-"Accepts OpenStack Object Storage API and raw HTTP requests to upload files, "
-"modify metadata, and create containers. It also serves file or container "
-"listings to web browsers. To improve performance, the proxy server can use "
-"an optional cache usually deployed with memcache."
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml20(term)
-msgid ""
-"Account servers (<systemitem class=\"service\">swift-account-"
-"server</systemitem>)"
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml22(para)
-msgid "Manages accounts defined with Object Storage."
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml26(term)
-msgid ""
-"Container servers (<systemitem class=\"service\">swift-container-"
-"server</systemitem>)"
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml28(para)
-msgid "Manages the mapping of containers or folders, within Object Storage."
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml32(term)
-msgid ""
-"Object servers (<systemitem class=\"service\">swift-object-"
-"server</systemitem>)"
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml34(para)
-msgid "Manages actual objects,such as files, on the storage nodes."
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml38(term)
-msgid "Various periodic processes"
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml39(para)
-msgid ""
-"Performs housekeeping tasks on the large data store. The replication "
-"services ensure consistency and availability through the cluster. Other "
-"periodic processes include auditors, updaters, and reapers."
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml45(term)
-msgid "WSGI middleware"
-msgstr ""
-
-#: ./doc/common/section_getstart_object-storage.xml46(para)
-msgid "Handles authentication and is usually OpenStack Identity."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml6(title)
-msgid "Secure the OpenStack Identity service connection to an LDAP back end"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml8(para)
-msgid ""
-"The Identity service supports the use of TLS to encrypt LDAP traffic. Before"
-" configuring this, you must first verify where your certificate authority "
-"file is located. For more information, see <xref linkend=\"certificates-for-"
-"pki\"/>."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml12(para)
-msgid "Once you verify the location of your certificate authority file:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml15(title)
-msgid "Configuring TLS encryption on LDAP traffic"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml17(para)
-msgid ""
-"Open the <filename>/etc/keystone/keystone.conf</filename> configuration "
-"file."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml23(para)
-msgid "Find the <literal>[ldap]</literal> section."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml26(para)
-msgid ""
-"In the <literal>[ldap]</literal> section, set the <literal>use_tls</literal>"
-" configuration key to <literal>True</literal>. Doing so will enable TLS."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml31(para)
-msgid ""
-"Configure the Identity service to use your certificate authorities file. To "
-"do so, set the <literal>tls_cacertfile</literal> configuration key in the "
-"<literal>ldap</literal> section to the certificate authorities file's path."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml37(para)
-msgid ""
-"You can also set the <literal>tls_cacertdir</literal> (also in the "
-"<literal>ldap</literal> section) to the directory where all certificate "
-"authorities files are kept. If both <literal>tls_cacertfile</literal> and "
-"<literal>tls_cacertdir</literal> are set, then the latter will be ignored."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml46(para)
-msgid ""
-"Specify what client certificate checks to perform on incoming TLS sessions "
-"from the LDAP server. To do so, set the <literal>tls_req_cert</literal> "
-"configuration key in the <literal>[ldap]</literal> section to "
-"<literal>demand</literal>, <literal>allow</literal>, or "
-"<literal>never</literal>:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml53(para)
-msgid ""
-"<parameter>demand</parameter>: a certificate will always be requested from "
-"the LDAP server. The session will be terminated if no certificate is "
-"provided, or if the certificate provided cannot be verified against the "
-"existing certificate authorities file."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml60(para)
-msgid ""
-"<parameter>allow</parameter>: a certificate will always be requested from "
-"the LDAP server. The session will proceed as normal even if a certificate is"
-" not provided. If a certificate is provided but it cannot be verified "
-"against the existing certificate authorities file, the certificate will be "
-"ignored and the session will proceed as normal."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml67(para)
-msgid "<parameter>never</parameter>: a certificate will never be requested."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml72(para)
-msgid ""
-"On distributions that include <application>openstack-config</application>, "
-"you can configure TLS encryption on LDAP traffic by running the following "
-"commands instead:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml80(replaceable)
-msgid "CA_FILE"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml82(replaceable)
-msgid "CERT_BEHAVIOR"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml83(para)
-#: ./doc/common/section_cli_nova_customize_flavors.xml260(para)
-#: ./doc/common/section_trusted-compute-pools.xml78(para)
-msgid "Where:"
-msgstr "各項目:"
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml85(para)
-msgid ""
-"<replaceable>CA_FILE</replaceable> is the absolute path to the certificate "
-"authorities file that should be used to encrypt LDAP traffic."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-hardening.xml88(para)
-msgid ""
-"<replaceable>CERT_BEHAVIOR</replaceable>: specifies what client certificate "
-"checks to perform on an incoming TLS session from the LDAP server "
-"(<literal>demand</literal>, <literal>allow</literal>, or "
-"<literal>never</literal>)."
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml7(title)
-#: ./doc/common/section_rpc.xml7(title)
-msgid "Configure the Oslo RPC messaging system"
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml9(para)
-msgid ""
-"OpenStack projects use an open standard for messaging middleware known as "
-"AMQP. This messaging middleware enables the OpenStack services that run on "
-"multiple servers to talk to each other. OpenStack Oslo RPC supports three "
-"implementations of AMQP: <application>RabbitMQ</application>, "
-"<application>Qpid</application>, and <application>ZeroMQ</application>."
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml18(title)
-#: ./doc/common/section_rpc.xml15(title)
-msgid "Configure RabbitMQ"
-msgstr "RabbitMQ の設定"
-
-#: ./doc/common/section_rpc-for-networking.xml20(para)
-msgid ""
-"OpenStack Oslo RPC uses <application>RabbitMQ</application> by default. Use "
-"these options to configure the <application>RabbitMQ</application> message "
-"system. The <option>rpc_backend</option> option is optional as long as "
-"<application>RabbitMQ</application> is the default messaging system. "
-"However, if it is included the configuration, you must set it to "
-"<literal>neutron.openstack.common.rpc.impl_kombu</literal>."
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml34(para)
-msgid ""
-"Use these options to configure the <application>RabbitMQ</application> "
-"messaging system. You can configure messaging communication for different "
-"installation scenarios, tune retries for RabbitMQ, and define the size of "
-"the RPC thread pool. To monitor notifications through RabbitMQ, you must set"
-" the <option>notification_driver</option> option to "
-"<literal>neutron.notifier.rabbit_notifier</literal> in the "
-"<filename>neutron.conf</filename> file:"
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml46(title)
-#: ./doc/common/section_rpc.xml39(title)
-msgid "Configure Qpid"
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml47(para)
-msgid ""
-"Use these options to configure the <application>Qpid</application> messaging"
-" system for OpenStack Oslo RPC. <application>Qpid</application> is not the "
-"default messaging system, so you must enable it by setting the "
-"<option>rpc_backend</option> option in the <filename>neutron.conf</filename>"
-" file:"
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml56(para)
-msgid ""
-"This critical option points the compute nodes to the "
-"<application>Qpid</application> broker (server). Set the "
-"<option>qpid_hostname</option> option to the host name where the broker runs"
-" in the <filename>neutron.conf</filename> file."
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml62(para)
-#: ./doc/common/section_rpc.xml52(para)
-msgid ""
-"The <option>--qpid_hostname</option> option accepts a host name or IP "
-"address value."
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml69(para)
-#: ./doc/common/section_rpc.xml56(para)
-msgid ""
-"If the <application>Qpid</application> broker listens on a port other than "
-"the AMQP default of <literal>5672</literal>, you must set the "
-"<option>qpid_port</option> option to that value:"
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml78(para)
-#: ./doc/common/section_rpc.xml61(para)
-msgid ""
-"If you configure the <application>Qpid</application> broker to require "
-"authentication, you must add a user name and password to the configuration:"
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml87(para)
-#: ./doc/common/section_rpc.xml66(para)
-msgid ""
-"By default, TCP is used as the transport. To enable SSL, set the "
-"<option>qpid_protocol</option> option:"
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml94(para)
-msgid ""
-"Use these additional options to configure the Qpid messaging driver for "
-"OpenStack Oslo RPC. These options are used infrequently."
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml102(title)
-#: ./doc/common/section_rpc.xml75(title)
-msgid "Configure ZeroMQ"
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml103(para)
-msgid ""
-"Use these options to configure the <application>ZeroMQ</application> "
-"messaging system for OpenStack Oslo RPC. <application>ZeroMQ</application> "
-"is not the default messaging system, so you must enable it by setting the "
-"<option>rpc_backend</option> option in the <filename>neutron.conf</filename>"
-" file:"
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml112(title)
-#: ./doc/common/section_rpc.xml85(title)
-msgid "Configure messaging"
-msgstr ""
-
-#: ./doc/common/section_rpc-for-networking.xml114(para)
-msgid ""
-"Use these common options to configure the "
-"<application>RabbitMQ</application>, <application>Qpid</application>, and "
-"<application>ZeroMq</application> messaging drivers:"
-msgstr ""
-
-#: ./doc/common/section_fibrechannel.xml5(title)
-msgid "Fibre Channel support in Compute"
-msgstr ""
-
-#: ./doc/common/section_fibrechannel.xml6(para)
-msgid ""
-"Fibre Channel support in OpenStack Compute is remote block storage attached "
-"to compute nodes for VMs."
-msgstr ""
-
-#. TODO: This below statement needs to be verified for current release
-#: ./doc/common/section_fibrechannel.xml9(para)
-msgid ""
-"In the Grizzly release, Fibre Channel supported only the KVM hypervisor."
-msgstr ""
-
-#: ./doc/common/section_fibrechannel.xml11(para)
-msgid ""
-"Compute and Block Storage for Fibre Channel do not support automatic zoning."
-" Fibre Channel arrays must be pre-zoned or directly attached to the KVM "
-"hosts."
-msgstr ""
-
-#: ./doc/common/section_fibrechannel.xml15(title)
-msgid "KVM host requirements"
-msgstr ""
-
-#: ./doc/common/section_fibrechannel.xml16(para)
-msgid "You must install these packages on the KVM host:"
-msgstr ""
-
-#: ./doc/common/section_fibrechannel.xml19(para)
-msgid ""
-"<package>sysfsutils</package> - Nova uses the <package>systool</package> "
-"application in this package."
-msgstr ""
-
-#: ./doc/common/section_fibrechannel.xml25(para)
-msgid ""
-"<package>sg3-utils</package> - Nova uses the <package>sg_scan</package> and "
-"<package>sginfo</package> applications."
-msgstr ""
-
-#: ./doc/common/section_fibrechannel.xml31(para)
-msgid "Installing the <package>multipath-tools</package> package is optional."
-msgstr ""
-
-#: ./doc/common/section_fibrechannel.xml35(title)
-msgid "Install required packages"
-msgstr ""
-
-#: ./doc/common/section_fibrechannel.xml36(para)
-msgid "Use these commands to install the system packages:"
-msgstr ""
-
-#: ./doc/common/section_fibrechannel.xml40(para)
-msgid "For systems running openSUSE or SUSE Linux Enterprise Server:"
-msgstr ""
-
-#: ./doc/common/section_fibrechannel.xml45(para)
-msgid "For systems running Red Hat:"
-msgstr ""
-
-#: ./doc/common/section_fibrechannel.xml49(para)
-msgid "For systems running Ubuntu:"
-msgstr ""
-
-#: ./doc/common/section_cli_help.xml6(title)
-msgid "Get help for client commands"
-msgstr "クライアントコマンドのヘルプの取得"
-
-#: ./doc/common/section_cli_help.xml7(para)
-msgid ""
-"To get usage information, including a list of commands with descriptions, "
-"for a client, run the following command:"
-msgstr "クライアントのコマンド一覧、概要、使用法を取得するために、以下のコマンドを実行します。"
-
-#: ./doc/common/section_cli_help.xml9(replaceable)
-#: ./doc/common/section_cli_help.xml59(replaceable)
-msgid "CLIENT_NAME"
-msgstr "CLIENT_NAME"
-
-#: ./doc/common/section_cli_help.xml10(para)
-msgid ""
-"For example, to get help information for the swift client, run the following"
-" command:"
-msgstr "例えば、swift クライアントの情報を取得する場合、以下のコマンドを実行します。"
-
-#: ./doc/common/section_cli_help.xml54(para)
-msgid ""
-"Depending on your credentials, you might not have permission to use every "
-"command."
-msgstr "クレデンシャルによっては、すべてのコマンドを使用する権限がないかもしれません。"
-
-#: ./doc/common/section_cli_help.xml57(para)
-msgid ""
-"After the <option>help</option> command, you can enter a command name to get"
-" help for that command, as follows:"
-msgstr "<option>help</option> コマンド後、そのコマンドのヘルプを表示するために、以下のとおりコマンド名を入力できます。"
-
-#: ./doc/common/section_cli_help.xml59(replaceable)
-msgid "COMMAND_NAME"
-msgstr "COMMAND_NAME"
-
-#: ./doc/common/section_cli_help.xml60(para)
-msgid ""
-"For example, to get help for the glance <placeholder-1/> command, enter the "
-"following command:"
-msgstr "例えば、glance <placeholder-1/> コマンドのヘルプを取得する場合、以下のコマンドを入力します。"
-
-#: ./doc/common/section_cli_help.xml64(para)
-msgid ""
-"The command returns a description of the command and its positional and "
-"optional arguments:"
-msgstr "このコマンドは、コマンドの説明、位置指定引数、オプション引数を返します。"
-
-#: ./doc/common/ch_getstart.xml6(title)
-msgid "Get started with OpenStack"
-msgstr "OpenStack 入門"
-
-#: ./doc/common/ch_getstart.xml7(para)
-msgid ""
-"The OpenStack project is an open source cloud computing platform for all "
-"types of clouds, which aims to be simple to implement, massively scalable, "
-"and feature rich. Developers and cloud computing technologists from around "
-"the world create the OpenStack project."
-msgstr "the OpenStack project はあらゆる種類のクラウド向けのオープンソースのクラウドコンピューティングプラットフォームです。シンプルな実装、大規模なスケーラビリティ、豊富な機能を目指しています。世界中の開発者とクラウドコンピューティング技術者が the OpenStack project を作成します。"
-
-#: ./doc/common/ch_getstart.xml12(para)
-msgid ""
-"OpenStack provides an Infrastructure-as-a-Service "
-"(<glossterm>IaaS</glossterm>) solution through a set of interrelated "
-"services. Each service offers an application programming interface "
-"(<glossterm>API</glossterm>) that facilitates this integration. Depending on"
-" your needs, you can install some or all services."
-msgstr "OpenStack は一組の相互に関係のあるサービスを通して Infrastructure-as-a-Service (<glossterm>IaaS</glossterm>) ソリューションを提供します。各サービスはこの統合を促す application programming interface (<glossterm>API</glossterm>) を提供します。必要に応じて、いくつかのサービス、またはすべてのサービスをインストールできます。"
-
-#: ./doc/common/ch_getstart.xml20(para)
-msgid ""
-"The following table describes the OpenStack services that make up the "
-"OpenStack architecture:"
-msgstr "以下の表は OpenStack アーキテクチャーを構成する OpenStack のサービスについて記載しています。"
-
-#: ./doc/common/ch_getstart.xml23(caption)
-#: ./doc/common/ch_getstart.xml188(title)
-msgid "OpenStack services"
-msgstr "OpenStack  のサービス"
-
-#: ./doc/common/ch_getstart.xml29(th)
-#: ./doc/common/section_keystone-concepts.xml83(term)
-#: ./doc/common/section_cli_overview.xml33(th)
-msgid "Service"
-msgstr "サービス"
-
-#: ./doc/common/ch_getstart.xml30(th)
-msgid "Project name"
-msgstr "プロジェクト名"
-
-#: ./doc/common/ch_getstart.xml38(glossterm)
-msgid "Dashboard"
-msgstr "Dashboard"
-
-#: ./doc/common/ch_getstart.xml42(glossterm)
-msgid "Horizon"
-msgstr "Horizon"
-
-#: ./doc/common/ch_getstart.xml44(td)
-msgid ""
-"Provides a web-based self-service portal to interact with underlying "
-"OpenStack services, such as launching an instance, assigning IP addresses "
-"and configuring access controls."
-msgstr "インスタンスの起動、IP アドレスの割り当て、アクセス制御の設定など、基礎となる OpenStack サービスを操作するために、ウェブベースのセルフサービスポータルを提供します。"
-
-#: ./doc/common/ch_getstart.xml52(glossterm)
-#: ./doc/common/section_dashboard_access.xml100(guilabel)
-#: ./doc/common/section_cli_overview.xml47(td)
-msgid "Compute"
-msgstr "Compute"
-
-#: ./doc/common/ch_getstart.xml56(glossterm)
-msgid "Nova"
-msgstr "Nova"
-
-#: ./doc/common/ch_getstart.xml58(td)
-msgid ""
-"Manages the lifecycle of compute instances in an OpenStack environment. "
-"Responsibilities include spawning, scheduling and decommissioning of virtual"
-" machines on demand."
-msgstr "OpenStack 環境でコンピュートインスタンスのライフサイクルを管理します。要求に応じて仮想マシンの作成、スケジューリング、廃棄などに責任を持ちます。"
-
-#: ./doc/common/ch_getstart.xml66(glossterm)
-#: ./doc/common/section_cli_overview.xml71(td)
-msgid "Networking"
-msgstr "Networking"
-
-#: ./doc/common/ch_getstart.xml70(glossterm)
-msgid "Neutron"
-msgstr "Neutron"
-
-#: ./doc/common/ch_getstart.xml72(td)
-msgid ""
-"Enables network connectivity as a service for other OpenStack services, such"
-" as OpenStack Compute. Provides an API for users to define networks and the "
-"attachments into them. Has a pluggable architecture that supports many "
-"popular networking vendors and technologies."
-msgstr "OpenStack Compute のような他の OpenStack サービスに対してサービスとしてのネットワーク接続性を可能にします。ユーザーがネットワークやそれらへの接続を定義するための API を提供します。数多くの人気のあるネットワークベンダーや技術をサポートする、プラグイン可能なアーキテクチャーを持ちます。"
-
-#: ./doc/common/ch_getstart.xml79(th)
-msgid "Storage"
-msgstr "ストレージ"
-
-#: ./doc/common/ch_getstart.xml83(glossterm)
-#: ./doc/common/section_cli_overview.xml78(td)
-msgid "Object Storage"
-msgstr "Object Storage"
-
-#: ./doc/common/ch_getstart.xml87(glossterm)
-msgid "Swift"
-msgstr "Swift"
-
-#: ./doc/common/ch_getstart.xml90(glossterm)
-msgid "RESTful"
-msgstr "RESTful"
-
-#: ./doc/common/ch_getstart.xml89(td)
-msgid ""
-"Stores and retrieves arbitrary unstructured data objects via a "
-"<placeholder-1/>, HTTP based API. It is highly fault tolerant with its data "
-"replication and scale out architecture. Its implementation is not like a "
-"file server with mountable directories."
-msgstr "<placeholder-1/>、HTTP ベースの API 経由で任意の非構造データオブジェクトを保存および取得します。そのデータ複製およびスケールアウトアーキテクチャーで高い耐障害性を持ちます。その実装はマウント可能なディレクトリを持つファイルサーバーのようではありません。"
-
-#: ./doc/common/ch_getstart.xml99(glossterm)
-#: ./doc/common/section_cli_overview.xml41(td)
-msgid "Block Storage"
-msgstr "Block Storage"
-
-#: ./doc/common/ch_getstart.xml103(glossterm)
-msgid "Cinder"
-msgstr "Cinder"
-
-#: ./doc/common/ch_getstart.xml105(td)
-msgid ""
-"Provides persistent block storage to running instances. Its pluggable driver"
-" architecture facilitates the creation and management of block storage "
-"devices."
-msgstr "実行中のインスタンスに永続的なブロックストレージを提供します。そのプラグイン可能なドライバーアーキテクチャーにより、ブロックストレージデバイスの作成と管理が容易になります。"
-
-#: ./doc/common/ch_getstart.xml110(th)
-msgid "Shared services"
-msgstr "共有サービス"
-
-#: ./doc/common/ch_getstart.xml114(glossterm)
-msgid "Identity service"
-msgstr "Identity"
-
-#: ./doc/common/ch_getstart.xml118(glossterm)
-msgid "Keystone"
-msgstr "Keystone"
-
-#: ./doc/common/ch_getstart.xml120(td)
-msgid ""
-"Provides an authentication and authorization service for other OpenStack "
-"services. Provides a catalog of endpoints for all OpenStack services."
-msgstr "他の OpenStack サービスに対して認証および認可サービスを提供します。すべての OpenStack サービスに対してエンドポイントのカタログを提供します。"
-
-#: ./doc/common/ch_getstart.xml127(glossterm)
-#: ./doc/common/section_cli_overview.xml65(td)
-msgid "Image Service"
-msgstr "Image Service"
-
-#: ./doc/common/ch_getstart.xml131(glossterm)
-msgid "Glance"
-msgstr "Glance"
-
-#: ./doc/common/ch_getstart.xml133(td)
-msgid ""
-"Stores and retrieves virtual machine disk images. OpenStack Compute makes "
-"use of this during instance provisioning."
-msgstr "仮想マシンディスクイメージを保存および取得します。OpenStack Compute がインスタンスの配備中に使用します。"
-
-#: ./doc/common/ch_getstart.xml142(glossterm)
-#: ./doc/common/section_cli_overview.xml93(td)
-msgid "Telemetry"
-msgstr "Telemetry"
-
-#: ./doc/common/ch_getstart.xml146(glossterm)
-msgid "Ceilometer"
-msgstr "Ceilometer"
-
-#: ./doc/common/ch_getstart.xml148(td)
-msgid ""
-"Monitors and meters the OpenStack cloud for billing, benchmarking, "
-"scalability, and statistical purposes."
-msgstr "課金、ベンチマーク、スケーラビリティ、統計などの目的のために、OpenStack クラウドを監視および測定します。"
-
-#: ./doc/common/ch_getstart.xml153(th)
-msgid "Higher-level services"
-msgstr "高レベルサービス"
-
-#: ./doc/common/ch_getstart.xml157(glossterm)
-#: ./doc/common/section_dashboard_access.xml192(guilabel)
-#: ./doc/common/section_cli_overview.xml86(td)
-msgid "Orchestration"
-msgstr "Orchestration"
-
-#: ./doc/common/ch_getstart.xml160(glossterm)
-msgid "Heat"
-msgstr "Heat"
-
-#: ./doc/common/ch_getstart.xml164(glossterm)
-msgid "HOT"
-msgstr "HOT"
-
-#: ./doc/common/ch_getstart.xml162(td)
-msgid ""
-"Orchestrates multiple composite cloud applications by using either the "
-"native <placeholder-1/> template format or the AWS CloudFormation template "
-"format, through both an OpenStack-native REST API and a CloudFormation-"
-"compatible Query API."
-msgstr "OpenStack ネイティブの REST API および CloudFormation 互換のクエリー API 経由で、ネイティブの <placeholder-1/> テンプレート形式または AWS CloudFormation テンプレート形式を使用することにより、複数の混合クラウドアプリケーションを統合します。"
-
-#: ./doc/common/ch_getstart.xml172(glossterm)
-#: ./doc/common/section_cli_overview.xml53(td)
-msgid "Database Service"
-msgstr "Database"
-
-#: ./doc/common/ch_getstart.xml176(glossterm)
-msgid "Trove"
-msgstr "Trove"
-
-#: ./doc/common/ch_getstart.xml178(td)
-msgid ""
-"Provides scalable and reliable Cloud Database-as-a-Service functionality for"
-" both relational and non-relational database engines."
-msgstr "リレーショナルデータベースと非リレーショナルデータベースの両エンジン用にスケール可能かつ信頼できるクラウド Database-as-a-Service を提供します。"
-
-#: ./doc/common/ch_getstart.xml189(para)
-msgid "This section describes OpenStack services in detail."
-msgstr "このセクションは OpenStack のサービスを詳細に記載します。"
-
-#: ./doc/common/ch_getstart.xml207(title)
-msgid "Feedback"
-msgstr "フィードバック"
-
-#: ./doc/common/section_getstart_compute.xml5(title)
-msgid "OpenStack Compute"
-msgstr "OpenStack Compute"
-
-#: ./doc/common/section_getstart_compute.xml6(para)
-msgid ""
-"OpenStack Compute is used to host and manage cloud computing systems and is "
-"a major part of an infrastructure-as-a-service (IaaS) system. The main "
-"modules are implemented in Python."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml9(para)
-msgid ""
-"OpenStack Compute interacts with OpenStack Identity for authentication, "
-"OpenStack Image Service for images, and OpenStack dashboard for the user and"
-" administrative interface. Access to images is limited by project and by "
-"user; quotas are limited per project (for example, the number of instances)."
-" OpenStack Compute can scale horizontally on standard hardware, and download"
-" images to launch instances."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml15(para)
-msgid ""
-"OpenStack Compute consists of the following areas and their components:"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml17(title)
-msgid "API"
-msgstr "API"
-
-#: ./doc/common/section_getstart_compute.xml19(systemitem)
-msgid "nova-api service"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml20(para)
-msgid ""
-"Accepts and responds to end user compute API calls. Supports the OpenStack "
-"Compute API, the Amazon EC2 API, and a special Admin API for privileged "
-"users to perform administrative actions. It enforces some policies and "
-"initiates most orchestration activities, such as running an instance."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml28(term)
-msgid "<systemitem class=\"service\">nova-api-metadata</systemitem> service"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml30(para)
-msgid ""
-"Accepts metadata requests from instances. The <systemitem class=\"service"
-"\">nova-api-metadata</systemitem> service is generally used when you run in "
-"multi-host mode with <systemitem class=\"service\">nova-network</systemitem>"
-" installations. For details, see <link href=\"http://docs.openstack.org"
-"/admin-guide-cloud/content/section_metadata-service.html\">Metadata "
-"service</link> in the <citetitle>Cloud Administrator Guide</citetitle>."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml38(para)
-msgid ""
-"On Debian systems, it is included in the <systemitem class=\"service\">nova-"
-"api</systemitem> package, and can be selected through "
-"<package>debconf</package>."
-msgstr "Debian システムの場合、<systemitem class=\"service\">nova-api</systemitem> パッケージに含まれます。<package>debconf</package> 経由で選択できます。"
-
-#: ./doc/common/section_getstart_compute.xml44(title)
-msgid "Compute core"
-msgstr "Compute コア"
-
-#: ./doc/common/section_getstart_compute.xml46(term)
-msgid "<systemitem class=\"service\">nova-compute</systemitem> process"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml47(para)
-msgid ""
-"A worker daemon that creates and terminates virtual machine instances "
-"through hypervisor APIs. For example, XenAPI for XenServer/XCP, libvirt for "
-"KVM or QEMU and VMwareAPI for VMware. Processing is fairly complex but "
-"fundamentally it accepts actions from the queue and performs a series of "
-"system commands, like launching a KVM instance, whilst updating its state in"
-" the database."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml56(term)
-msgid "<systemitem class=\"service\">nova-scheduler</systemitem> process"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml58(para)
-msgid ""
-"Conceptually the simplest piece of code in OpenStack Compute. It takes a "
-"virtual machine instance request from the queue and determines on which "
-"compute server host it will run."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml64(term)
-msgid "<systemitem class=\"service\">nova-conductor</systemitem> module"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml65(para)
-msgid ""
-"Mediates interactions between <systemitem class=\"service\">nova-"
-"compute</systemitem> and the database. It eliminates direct accesses to the "
-"cloud database made by <systemitem class=\"service\">nova-"
-"compute</systemitem>. The <systemitem class=\"service\">nova-"
-"conductor</systemitem> module scales horizontally. However, do not deploy it"
-" on any nodes where <systemitem class=\"service\">nova-compute</systemitem> "
-"runs. For more information, see <link "
-"href=\"http://russellbryantnet.wordpress.com/2012/11/19/a-new-nova-service-"
-"nova-conductor/\">A new Nova service: nova-conductor</link>."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml79(title)
-msgid "Networking for VMs"
-msgstr "仮想マシン用ネットワーク"
-
-#: ./doc/common/section_getstart_compute.xml80(term)
-msgid "<systemitem class=\"service\">nova-network</systemitem> worker daemon"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml82(para)
-msgid ""
-"Similar to <systemitem class=\"service\">nova-compute</systemitem>, it "
-"accepts networking tasks from the queue and performs tasks to manipulate the"
-" network, such as setting up bridging interfaces or changing iptables rules."
-" This functionality is being migrated to OpenStack Networking."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml90(term)
-msgid "<systemitem class=\"service\">nova-dhcpbridge</systemitem> script"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml92(para)
-msgid ""
-"The IP address leases and is recorded in the database using the dnsmasq "
-"<literal>dhcp-script</literal> facility. This functionality is being "
-"migrated to OpenStack Networkin which provides a different script."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml99(title)
-msgid "Console interface"
-msgstr "コンソールインターフェース"
-
-#: ./doc/common/section_getstart_compute.xml101(term)
-msgid "<systemitem class=\"service\">nova-consoleauth</systemitem> daemon"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml102(para)
-msgid ""
-"Authorizes tokens for users that console proxies provide. See <systemitem "
-"class=\"service\">nova-novncproxy</systemitem> and <systemitem "
-"class=\"service\">nova-xvpnvcproxy</systemitem>. This service must be "
-"running for console proxies to work. Many proxies of either type can be run "
-"against a single <systemitem class=\"service\">nova-consoleauth</systemitem>"
-" service in a cluster configuration. For information, see <link "
-"href=\"http://docs.openstack.org/trunk/config-reference/content/about-nova-"
-"consoleauth.html\">About nova-consoleauth</link>."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml114(term)
-msgid "<systemitem class=\"service\">nova-novncproxy</systemitem> daemon"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml116(para)
-msgid ""
-"Provides a proxy for accessing running instances through a VNC connection. "
-"Supports browser-based novnc clients."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml121(term)
-msgid "<systemitem class=\"service\">nova-xvpnvncproxy</systemitem> daemon"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml123(para)
-msgid ""
-"A proxy for accessing running instances through a VNC connection. It "
-"supports a Java client specifically designed for OpenStack."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml128(term)
-msgid "<systemitem class=\"service\">nova-cert</systemitem> daemon"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml129(para)
-msgid "x509 certificates."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml132(para)
-msgid ""
-"In Debian, a unique <package>nova-consoleproxy</package> package provides "
-"the <package>nova-novncproxy</package>, <package>nova-"
-"spicehtml5proxy</package>, and <package>nova-xvpvncproxy</package> packages."
-" To select packages, edit the <filename>/etc/default/nova-"
-"consoleproxy</filename> file or use the <package>debconf</package> "
-"interface. You can also manually edit the <filename>/etc/default/nova-"
-"consoleproxy</filename> file, and stop and start the console daemons."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml142(title)
-msgid "Image management (EC2 scenario)"
-msgstr "イメージ管理 (EC2 シナリオ)"
-
-#: ./doc/common/section_getstart_compute.xml144(term)
-msgid "<systemitem class=\"service\">nova-objectstore</systemitem> daemon"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml145(para)
-msgid ""
-"A S3 interface for registering images with the OpenStack Image Service. It "
-"is mainly used for installations that must support euca2ools. The euca2ools "
-"tools talk to <systemitem class=\"service\">nova-objectstore</systemitem> in"
-" <emphasis role=\"italic\">S3 language</emphasis>, and <systemitem "
-"class=\"service\">nova-objectstore</systemitem> translates S3 requests into "
-"Image service requests."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml154(term)
-msgid "euca2ools client"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml155(para)
-msgid ""
-"A set of command-line interpreter commands for managing cloud resources. "
-"Although it is not an OpenStack module, you can configure <systemitem "
-"class=\"service\">nova-api</systemitem> to support this EC2 interface. For "
-"more information, see the <link "
-"href=\"https://www.eucalyptus.com/docs/eucalyptus/3.4/index.html\">Eucalyptus"
-" 3.4 Documentation</link>."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml163(title)
-msgid "Command-line clients and other interfaces"
-msgstr "コマンドラインクライアントと他のインターフェース"
-
-#: ./doc/common/section_getstart_compute.xml164(term)
-msgid "nova client"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml165(para)
-msgid "Allows users to submit commands as a tenant administrator or end user."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml169(term)
-msgid "nova-manage client"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml170(para)
-msgid "Enables cloud administrators to submit commands."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml174(title)
-msgid "Other components"
-msgstr "他のコンポーネント"
-
-#: ./doc/common/section_getstart_compute.xml175(term)
-msgid "The queue"
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml175(para)
-msgid ""
-"A central hub for passing messages between daemons. It is usually "
-"implemented with <link href=\"http://www.rabbitmq.com/\">RabbitMQ</link>, "
-"but could be any AMQP message queue, such as <link "
-"href=\"http://qpid.apache.org/\">Apache Qpid</link> or <link "
-"href=\"http://www.zeromq.org/\">Zero MQ</link>."
-msgstr ""
-
-#: ./doc/common/section_getstart_compute.xml183(term)
-msgid "SQL database"
-msgstr "SQL データベース"
-
-#: ./doc/common/section_getstart_compute.xml184(para)
-msgid ""
-"Stores most build-time and runtime states for a cloud infrastructure. It "
-"includes instance types that are available for use, instances in use, "
-"available networks, and projects. Theoretically, OpenStack Compute can "
-"support any database that is supported by SQL-Alchemy. Note the databases "
-"which are widely used are SQLite3 databases (for test and development work),"
-" MySQL, and PostgreSQL."
+#: ./doc/common/ch_cli_ceilometer_commands.xml68(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml746(para)
+msgid "Delete an alarm."
 msgstr ""
 
-#: ./doc/common/section_getstart_compute.xml192(para)
-msgid ""
-"OpenStack Compute interacts with OpenStack Identity for authentication; "
-"OpenStack Image Service for images; and the OpenStack dashboard for a web "
-"interface."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-console.xml5(title)
-msgid "Configure remote console access"
-msgstr ""
-
-#. <?dbhtml stop-chunking?>
-#: ./doc/common/section_compute-configure-console.xml7(para)
-msgid ""
-"To provide a remote console or remote desktop access to guest virtual "
-"machines, use VNC or SPICE HTML5 through either the OpenStack dashboard or "
-"the command line. Best practice is to select one or the other to run."
-msgstr ""
-
-#: ./doc/common/section_xapi-resize-setup.xml7(title)
-msgid "Modify Dom0 for resize/migration support"
-msgstr ""
-
-#: ./doc/common/section_xapi-resize-setup.xml8(para)
-msgid "To resize servers with XenServer and XCP, you must:"
-msgstr ""
-
-#: ./doc/common/section_xapi-resize-setup.xml11(para)
-msgid ""
-"Establish a root trust between all hypervisor nodes of your deployment:"
-msgstr ""
-
-#: ./doc/common/section_xapi-resize-setup.xml13(para)
-msgid ""
-"To do so, generate an ssh key-pair with the <placeholder-1/> command. Ensure"
-" that each of your dom0's <filename>authorized_keys</filename> file (located"
-" in <filename>/root/.ssh/authorized_keys</filename>) contains the public key"
-" fingerprint (located in <filename>/root/.ssh/id_rsa.pub</filename>)."
+#: ./doc/common/ch_cli_ceilometer_commands.xml76(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml763(para)
+msgid "Display the change history of an alarm."
 msgstr ""
 
-#: ./doc/common/section_xapi-resize-setup.xml22(para)
-msgid ""
-"Provide an <filename>/images</filename> mount point to the dom0 for your "
-"hypervisor:"
-msgstr ""
-
-#: ./doc/common/section_xapi-resize-setup.xml24(para)
-msgid ""
-"Dom0 space is at a premium so creating a directory in dom0 is potentially "
-"dangerous and likely to fail especially when you resize large servers. The "
-"least you can do is to symlink <filename>/images</filename> to your local "
-"storage SR. The following instructions work for an English-based "
-"installation of XenServer (and XCP) and in the case of ext3-based SR (with "
-"which the resize functionality is known to work correctly)."
+#: ./doc/common/ch_cli_ceilometer_commands.xml84(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml790(para)
+msgid "List the user's alarms."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_sshkeys.xml6(title)
-msgid "Add keypair"
+#: ./doc/common/ch_cli_ceilometer_commands.xml92(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml809(para)
+msgid "Show an alarm."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_sshkeys.xml7(para)
-msgid ""
-"Create at least one keypair for each project. If you have generated a "
-"keypair with an external tool, you can import it into OpenStack. The keypair"
-" can be used for multiple instances that belong to a project."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_sshkeys.xml13(para)
-msgid "Create a key."
+#: ./doc/common/ch_cli_ceilometer_commands.xml100(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml826(para)
+msgid "Get the state of an alarm."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_sshkeys.xml14(para)
-msgid ""
-"To create a <literal>mykey</literal> key that you can associate with "
-"instances, run the following command:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml108(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml843(para)
+msgid "Set the state of an alarm."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_sshkeys.xml17(para)
-msgid ""
-"Save the <filename>mykey.pem</filename> file to a secure location. It "
-"enables root access to any instances with which the <literal>mykey</literal>"
-" key is associated."
+#: ./doc/common/ch_cli_ceilometer_commands.xml116(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml884(para)
+msgid "Create a new alarm based on computed statistics."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_sshkeys.xml22(para)
-msgid "Alternatively, you can import a keypair."
+#: ./doc/common/ch_cli_ceilometer_commands.xml124(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1074(para)
+msgid "Update an existing alarm based on computed statistics."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_sshkeys.xml23(para)
-msgid ""
-"To import an existing public key, <literal>mykey.pub</literal>, and "
-"associate it with the <literal>mykey</literal> key, run the following "
-"command:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml132(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1279(para)
+msgid "Update an existing alarm (Deprecated)."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_sshkeys.xml28(para)
-msgid ""
-"You must have the matching private key to access instances that are "
-"associated with this key."
+#: ./doc/common/ch_cli_ceilometer_commands.xml140(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1468(para)
+msgid "List events."
 msgstr ""
 
-#: ./doc/common/section_dashboard-configure-https.xml4(title)
-msgid "Configure the dashboard for HTTPS"
+#: ./doc/common/ch_cli_ceilometer_commands.xml148(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1487(para)
+msgid "Show a particular event."
 msgstr ""
 
-#: ./doc/common/section_dashboard-configure-https.xml5(para)
-#: ./doc/common/section_dashboard-configure.xml10(para)
-msgid ""
-"You can configure the dashboard for a secured HTTPS deployment. While the "
-"standard installation uses a non-encrypted HTTP channel, you can enable SSL "
-"support for the dashboard."
+#: ./doc/common/ch_cli_ceilometer_commands.xml156(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1504(para)
+msgid "List event types."
 msgstr ""
 
-#: ./doc/common/section_dashboard-configure-https.xml9(para)
-msgid ""
-"The following example uses the domain, \"http://openstack.example.com.\" Use"
-" a domain that fits your current setup."
+#: ./doc/common/ch_cli_ceilometer_commands.xml164(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1511(para)
+msgid "List the user's meters."
 msgstr ""
 
-#: ./doc/common/section_dashboard-configure-https.xml13(para)
-msgid ""
-"In<filename>/etc/openstack-dashboard/local_settings.py</filename> update the"
-" following directives:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml172(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1531(para)
+msgid "Query Alarm History."
 msgstr ""
 
-#: ./doc/common/section_dashboard-configure-https.xml19(para)
-msgid ""
-"The first option is required to enable HTTPS. The other recommended settings"
-" defend against cross-site scripting and require HTTPS."
+#: ./doc/common/ch_cli_ceilometer_commands.xml180(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1567(para)
+msgid "Query Alarms."
 msgstr ""
 
-#: ./doc/common/section_dashboard-configure-https.xml24(para)
-msgid ""
-"Edit <filename>/etc/apache2/ports.conf</filename> and add the following "
-"line:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml188(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1603(para)
+msgid "Query samples."
 msgstr ""
 
-#: ./doc/common/section_dashboard-configure-https.xml30(para)
-msgid ""
-"Edit <filename>/etc/apache2/conf.d/openstack-dashboard.conf:</filename>"
+#: ./doc/common/ch_cli_ceilometer_commands.xml196(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1639(para)
+msgid "List the resources."
 msgstr ""
 
-#: ./doc/common/section_dashboard-configure-https.xml33(para)
-msgid "Before:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml204(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1658(para)
+msgid "Show the resource."
 msgstr ""
 
-#: ./doc/common/section_dashboard-configure-https.xml46(para)
-msgid "After:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml212(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1681(para)
+msgid "Create a sample."
 msgstr ""
 
-#: ./doc/common/section_dashboard-configure-https.xml87(para)
-msgid ""
-"In this configuration, Apache http server listens on the port 443 and "
-"redirects all the hits to the HTTPS protocol for all the non-secured "
-"requests. The secured section defines the private key, public key, and "
-"certificate to use."
+#: ./doc/common/ch_cli_ceilometer_commands.xml220(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1764(para)
+msgid "List the samples for a meter."
 msgstr ""
 
-#: ./doc/common/section_dashboard-configure-https.xml94(para)
-msgid "Restart Apache http server. For Debian/Ubuntu/SUSE:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml228(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1800(para)
+msgid "List the statistics for a meter."
 msgstr ""
 
-#: ./doc/common/section_dashboard-configure-https.xml96(para)
-msgid "Or for Fedora/RHEL/CentOS:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml236(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1853(para)
+msgid "List trait info for an event type."
 msgstr ""
 
-#: ./doc/common/section_dashboard-configure-https.xml98(para)
-#: ./doc/common/section_dashboard-configure-http.xml32(para)
-msgid "Next, restart memcached:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml244(para)
+msgid "List trait all traits with name &lt;trait_name&gt; for Event Type"
 msgstr ""
 
-#: ./doc/common/section_dashboard-configure-https.xml100(para)
-msgid ""
-"If you try to access the dashboard through HTTP, the browser redirects you "
-"to the HTTPS page."
+#: ./doc/common/ch_cli_ceilometer_commands.xml270(title)
+msgid "ceilometer optional arguments"
 msgstr ""
 
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_getstart_logical_arch.xml38(None)
-msgid ""
-"@@image: 'figures/openstack-arch-havana-logical-v1.jpg'; "
-"md5=e7acaaee72722626b045eda3fae81841"
-msgstr "@@image: 'figures/openstack-arch-havana-logical-v1.jpg'; md5=e7acaaee72722626b045eda3fae81841"
-
-#: ./doc/common/section_getstart_logical_arch.xml5(title)
-#: ./doc/common/section_getstart_logical_arch.xml33(title)
-msgid "Logical architecture"
-msgstr "論理アーキテクチャー"
-
-#: ./doc/common/section_getstart_logical_arch.xml6(para)
-msgid ""
-"To design, deploy, and configure OpenStack, administrators must understand "
-"the logical architecture."
-msgstr "クラウド管理者は、OpenStack を設計、導入、設定するために、論理アーキテクチャーを理解する必要があります。"
-
-#: ./doc/common/section_getstart_logical_arch.xml7(para)
-msgid "OpenStack modules are one of the following types:"
-msgstr "OpenStack のモジュールは以下の種別のどれかです。"
-
-#: ./doc/common/section_getstart_logical_arch.xml9(term)
-msgid "Daemon"
+#: ./doc/common/ch_cli_ceilometer_commands.xml283(para)
+msgid "Defaults to <code>env[CEILOMETERCLIENT_DEBUG]</code>."
 msgstr ""
 
-#: ./doc/common/section_getstart_logical_arch.xml11(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml299(para)
 msgid ""
-"Runs as a background process. On Linux platforms, a daemon is usually "
-"installed as a service."
-msgstr ""
-
-#: ./doc/common/section_getstart_logical_arch.xml15(term)
-msgid "Script"
+"Explicitly allow ceilometerclient to perform \"insecure\" SSL (https) "
+"requests. The server's certificate will not be verified against any "
+"certificate authorities. This option should be used with caution."
 msgstr ""
 
-#: ./doc/common/section_getstart_logical_arch.xml17(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml331(para)
 msgid ""
-"Installs a virtual environment and runs tests. For example, the "
-"<code>run_tests.sh</code> script installs a virtual environment and runs "
-"unit tests on a service."
+"Path of CA TLS certificate(s) used to verifythe remote server's certificate."
+" Without this option ceilometer looks for the default system CA "
+"certificates."
 msgstr ""
 
-#: ./doc/common/section_getstart_logical_arch.xml21(term)
-msgid "Command-line interface (CLI)"
+#: ./doc/common/ch_cli_ceilometer_commands.xml349(para)
+msgid "Number of seconds to wait for a response."
 msgstr ""
 
-#: ./doc/common/section_getstart_logical_arch.xml23(para)
-msgid ""
-"Enables users to submit API calls to OpenStack services through easy-to-use "
-"commands."
+#: ./doc/common/ch_cli_ceilometer_commands.xml413(para)
+msgid "Defaults to <code>env[CEILOMETER_URL]</code>."
 msgstr ""
 
-#: ./doc/common/section_getstart_logical_arch.xml29(para)
-msgid ""
-"The following diagram shows the most common, but not the only, architecture "
-"for an OpenStack cloud:"
-msgstr "以下の図は、最も一般的ですが、唯一のものではない、OpenStack クラウドのアーキテクチャーを示します。"
-
-#: ./doc/common/section_getstart_logical_arch.xml42(para)
-msgid ""
-"As in <xref linkend=\"concept_arch\"/>, end users can interact through the "
-"dashboard, CLIs, and APIs. All services authenticate through a common "
-"Identity Service and individual services interact with each other through "
-"public APIs, except where privileged administrator commands are necessary."
-msgstr "<xref linkend=\"concept_arch\"/> にあるとおり、エンドユーザーはダッシュボード、CLI、API 経由で操作できます。すべてのサービスは共通の Identity Service 経由で認証されます。個々のサービスは、特権管理コマンドが必要となる場合を除いて、お互いにパブリック API 経由で相互作用します。"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_keystone-concepts.xml120(None)
-#: ./doc/common/section_keystone-concepts.xml125(None)
-msgid ""
-"@@image: 'figures/SCH_5002_V00_NUAC-Keystone.png'; "
-"md5=734714c50c99fc1d74bdfd9f9cd049a6"
-msgstr "@@image: 'figures/SCH_5002_V00_NUAC-Keystone.png'; md5=734714c50c99fc1d74bdfd9f9cd049a6"
-
-#: ./doc/common/section_keystone-concepts.xml7(title)
-msgid "OpenStack Identity concepts"
+#: ./doc/common/ch_cli_ceilometer_commands.xml421(para)
+msgid "Defaults to <code>env[CEILOMETER_API_VERSION]</code> or 2."
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts.xml8(para)
-msgid ""
-"The OpenStack<glossterm>Identity Service</glossterm> performs the following "
-"functions:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml445(title)
+msgid "ceilometer alarm-combination-create command"
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts.xml12(para)
-msgid "Tracking users and their permissions."
+#: ./doc/common/ch_cli_ceilometer_commands.xml466(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml891(para)
+msgid "Name of the alarm (must be unique per tenant). Required."
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts.xml15(para)
-msgid "Providing a catalog of available services with their API endpoints."
+#: ./doc/common/ch_cli_ceilometer_commands.xml475(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml624(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml900(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1097(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1302(para)
+msgid "Tenant to associate with alarm (only settable by admin users)."
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts.xml19(para)
-msgid ""
-"To understand OpenStack Identity, you must understand the following "
-"concepts:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml484(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml633(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml909(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1106(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1311(para)
+msgid "User to associate with alarm (only settable by admin users)."
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts.xml23(term)
-msgid "User"
-msgstr "ユーザー"
-
-#: ./doc/common/section_keystone-concepts.xml25(para)
-msgid ""
-"Digital representation of a person, system, or service who uses OpenStack "
-"cloud services. The Identity service validates that incoming requests are "
-"made by the user who claims to be making the call. Users have a login and "
-"may be assigned tokens to access resources. Users can be directly assigned "
-"to a particular tenant and behave as if they are contained in that tenant."
+#: ./doc/common/ch_cli_ceilometer_commands.xml493(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml642(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml918(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1115(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1320(para)
+msgid "Free text description of the alarm."
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts.xml36(term)
-msgid "Credentials"
-msgstr "クレデンシャル"
-
-#: ./doc/common/section_keystone-concepts.xml38(para)
-msgid ""
-"Data that confirms the user's identity. For example, user name and password;"
-" user name and API key; or an authentication token provided by the Identity "
-"Service."
+#: ./doc/common/ch_cli_ceilometer_commands.xml501(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml650(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml926(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1123(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1328(para)
+msgid "State of the alarm, one of: ['ok', 'alarm', 'insufficient_data']"
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts.xml45(term)
-msgid "Authentication"
-msgstr "認証"
-
-#: ./doc/common/section_keystone-concepts.xml47(para)
-msgid ""
-"The process of confirming the identity of a user. OpenStack Identity "
-"confirms an incoming request by validating a set of credentials supplied by "
-"the user."
+#: ./doc/common/ch_cli_ceilometer_commands.xml510(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml659(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml935(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1132(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1337(para)
+msgid "True if alarm evaluation/actioning is enabled."
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts.xml51(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml518(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml667(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml943(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1140(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1345(para)
 msgid ""
-"These credentials are initially a user name and password; or a user name and"
-" API key. When user credentials are validated, OpenStack Identity issues an "
-"authentication token which the user provides in subsequent requests."
+"URL to invoke when state transitions to alarm. May be used multiple times. "
+"Defaults to None."
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts.xml59(term)
-msgid "Token"
-msgstr "トークン"
-
-#: ./doc/common/section_keystone-concepts.xml61(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml527(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml676(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml952(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1149(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1354(para)
 msgid ""
-"An arbitrary bit of text that is used to access resources. Each token has "
-"information which defines access to resources. A token may be revoked at any"
-" time and is valid for a finite duration."
+"URL to invoke when state transitions to OK. May be used multiple times. "
+"Defaults to None."
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts.xml65(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml536(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml685(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml961(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1158(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1363(para)
 msgid ""
-"While OpenStack Identity supports token-based authentication in this "
-"release, the intention is to support additional protocols in the future. Its"
-" main purpose is to be an integration service, and not aspire to be a full-"
-"fledged identity store and management solution."
+"URL to invoke when state transitions to insufficient_data. May be used "
+"multiple times. Defaults to None."
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts.xml74(term)
-msgid "Tenant"
-msgstr "テナント"
-
-#: ./doc/common/section_keystone-concepts.xml76(para)
-msgid ""
-"A container used to group or isolate resources and/or identity objects. "
-"Depending on the service operator, a tenant may map to a customer, account, "
-"organization, or project."
-msgstr "リソース、主体オブジェクト、またはその組み合わせをグループ化、または分離するために使用されるコンテナー。サービス操作者に依存して、テナントが顧客、アカウント、組織、プロジェクトに対応付けられるかもしれません。"
-
-#: ./doc/common/section_keystone-concepts.xml85(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml546(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml695(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml971(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1168(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1373(para)
 msgid ""
-"An OpenStack service, such as Compute (nova), Object Storage (swift), or "
-"Image Service (glance). It provides one or more endpoints through which "
-"users can access resources and perform operations."
+"Only evaluate the alarm if the time at evaluation is within this time "
+"constraint. Start point(s) of the constraint are specified with a cron "
+"expression , whereas its duration is given in seconds. Can be specified "
+"multiple times for multiple time constraints, format is: "
+"name=&lt;CONSTRAINT_NAME&gt;;start=&lt; "
+"CRON&gt;;duration=&lt;SECONDS&gt;;[description=&lt;DESCRIPTION&gt;;[t "
+"imezone=&lt;IANA Timezone&gt;]] Defaults to None."
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts.xml92(term)
-msgid "Endpoint"
-msgstr "エンドポイント"
-
-#: ./doc/common/section_keystone-concepts.xml94(para)
-msgid ""
-"A network-accessible address where you access a service, usually a URL "
-"address. If you are using an extension for templates, an endpoint template "
-"can be created, which represents the templates of all the consumable "
-"services that are available across the regions."
+#: ./doc/common/ch_cli_ceilometer_commands.xml561(para)
+msgid "List of alarm ids. Required."
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts.xml102(term)
-msgid "Role"
-msgstr "役割"
-
-#: ./doc/common/section_keystone-concepts.xml104(para)
-msgid ""
-"A personality with a defined set of user rights and privileges to perform a "
-"specific set of operations."
+#: ./doc/common/ch_cli_ceilometer_commands.xml569(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml727(para)
+msgid "Operator to compare with, one of: ['and', 'or']."
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts.xml106(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml577(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1046(para)
 msgid ""
-"In the Identity service, a token that is issued to a user includes the list "
-"of roles. Services that are being called by that user determine how they "
-"interpret the set of roles a user has and to which operations or resources "
-"each role grants access."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts.xml114(para)
-msgid "The following diagram shows the OpenStack Identity process flow:"
-msgstr ""
-
-#: ./doc/common/section_kvm_enable.xml6(title)
-msgid "Enable KVM"
+"True if actions should be repeatedly notified while alarm remains in target "
+"state. Defaults to False."
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml7(para)
-msgid ""
-"To perform these steps, you must be logged in as the "
-"<systemitem>root</systemitem> user."
+#: ./doc/common/ch_cli_ceilometer_commands.xml586(title)
+msgid "ceilometer alarm-combination-update command"
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml11(para)
-msgid ""
-"To determine whether the <literal>svm</literal> or <literal>vmx</literal> "
-"CPU extensions are present, run this command:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml608(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1081(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1286(para)
+msgid "ID of the alarm to update. Required."
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml15(para)
-msgid ""
-"This command generates output if the CPU is hardware-virtualization capable."
-" Even if output is shown, you might still need to enable virtualization in "
-"the system BIOS for full support."
+#: ./doc/common/ch_cli_ceilometer_commands.xml616(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1089(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1294(para)
+msgid "Name of the alarm (must be unique per tenant)."
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml19(para)
-msgid ""
-"If no output appears, consult your system documentation to ensure that your "
-"CPU and motherboard support hardware virtualization. Verify that any "
-"relevant hardware virtualization options are enabled in the system BIOS."
+#: ./doc/common/ch_cli_ceilometer_commands.xml710(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1183(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1388(para)
+msgid "Name or list of names of the time constraints to remove."
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml24(para)
-msgid ""
-"The BIOS for each manufacturer is different. If you must enable "
-"virtualization in the BIOS, look for an option containing the words "
-"<literal>virtualization</literal>, <literal>VT</literal>, "
-"<literal>VMX</literal>, or <literal>SVM</literal>."
+#: ./doc/common/ch_cli_ceilometer_commands.xml719(para)
+msgid "List of alarm id."
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml32(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml735(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1252(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1457(para)
 msgid ""
-"To list the loaded kernel modules and verify that the <literal>kvm</literal>"
-" modules are loaded, run this command:"
+"True if actions should be repeatedly notified while alarm remains in target "
+"state."
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml36(para)
-msgid ""
-"If the output includes <systemitem>kvm_intel</systemitem> or "
-"<systemitem>kvm_amd</systemitem>, the <systemitem>kvm</systemitem> hardware "
-"virtualization modules are loaded and your kernel meets the module "
-"requirements for OpenStack Compute."
+#: ./doc/common/ch_cli_ceilometer_commands.xml744(title)
+msgid "ceilometer alarm-delete command"
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml43(para)
-msgid ""
-"If the output does not show that the <literal>kvm</literal> module is "
-"loaded, run this command to load it:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml753(para)
+msgid "ID of the alarm to delete. Required."
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml47(para)
-msgid "Run the command for your CPU. For Intel, run this command:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml761(title)
+msgid "ceilometer alarm-history command"
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml50(para)
-msgid "For AMD, run this command:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml770(para)
+msgid "ID of the alarm for which history is shown. Required."
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml52(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml778(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml797(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1036(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1242(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1518(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1646(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1771(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1807(para)
 msgid ""
-"Because a KVM installation can change user group membership, you might need "
-"to log in again for changes to take effect."
+"key[op]data_type::value; list. data_type is optional, but if supplied must "
+"be string, integer, float, or boolean."
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml55(para)
-msgid ""
-"If the kernel modules do not load automatically, use the procedures listed "
-"in these subsections."
+#: ./doc/common/ch_cli_ceilometer_commands.xml788(title)
+msgid "ceilometer alarm-list command"
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml59(para)
-msgid ""
-"If the checks indicate that required hardware virtualization support or "
-"kernel modules are disabled or unavailable, you must either enable this "
-"support on the system or find a system with this support."
+#: ./doc/common/ch_cli_ceilometer_commands.xml807(title)
+msgid "ceilometer alarm-show command"
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml64(para)
-msgid ""
-"Some systems require that you enable VT support in the system BIOS. If you "
-"believe your processor supports hardware acceleration but the previous "
-"command did not produce output, reboot your machine, enter the system BIOS, "
-"and enable the VT option."
+#: ./doc/common/ch_cli_ceilometer_commands.xml816(para)
+msgid "ID of the alarm to show. Required."
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml70(para)
-msgid ""
-"If KVM acceleration is not supported, configure Compute to use a different "
-"hypervisor, such as <link href=\"http://docs.openstack.org/trunk/config-"
-"reference/content/qemu.html\">QEMU</link> or <link "
-"href=\"http://docs.openstack.org/trunk/config-reference/content"
-"/introduction-to-xen.html\">Xen</link>."
+#: ./doc/common/ch_cli_ceilometer_commands.xml824(title)
+msgid "ceilometer alarm-state-get command"
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml76(para)
-msgid ""
-"These procedures help you load the kernel modules for Intel-based and AMD-"
-"based processors if they do not load automatically during KVM installation."
+#: ./doc/common/ch_cli_ceilometer_commands.xml833(para)
+msgid "ID of the alarm state to show. Required."
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml80(title)
-msgid "Intel-based processors"
-msgstr "Intel 系プロセッサー"
-
-#: ./doc/common/section_kvm_enable.xml81(para)
-msgid ""
-"If your compute host is Intel-based, run these commands as root to load the "
-"kernel modules:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml841(title)
+msgid "ceilometer alarm-state-set command"
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml85(para)
-msgid ""
-"Add these lines to the <filename>/etc/modules</filename> file so that these "
-"modules load on reboot:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml850(para)
+msgid "ID of the alarm state to set. Required."
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml91(title)
-msgid "AMD-based processors"
-msgstr "AMD 系プロセッサー"
-
-#: ./doc/common/section_kvm_enable.xml92(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml858(para)
 msgid ""
-"If your compute host is AMD-based, run these commands as root to load the "
-"kernel modules:"
+"State of the alarm, one of: ['ok', 'alarm', 'insufficient_data']. Required."
 msgstr ""
 
-#: ./doc/common/section_kvm_enable.xml96(para)
-msgid ""
-"Add these lines to <filename>/etc/modules</filename> file so that these "
-"modules load on reboot:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml867(title)
+msgid "ceilometer alarm-threshold-create command"
 msgstr ""
 
-#: ./doc/common/section_xapi-install-plugins.xml7(title)
-msgid "Install the XenAPI plug-ins"
+#: ./doc/common/ch_cli_ceilometer_commands.xml986(para)
+msgid "Metric to evaluate against. Required."
 msgstr ""
 
-#: ./doc/common/section_xapi-install-plugins.xml8(para)
-msgid ""
-"When you use Xen as the hypervisor for OpenStack Compute, you can install a "
-"Python script (or any executable) on the host side, and call that through "
-"the XenAPI. These scripts are called plug-ins. The XenAPI plug-ins live in "
-"the nova code repository. These plug-ins have to be copied to the Dom0 for "
-"the hypervisor, to the appropriate directory, where xapi can find them. "
-"There are several options for the installation. The important thing is to "
-"ensure that the version of the plug-ins are in line with the nova "
-"installation by only installing plug-ins from a matching nova repository."
+#: ./doc/common/ch_cli_ceilometer_commands.xml994(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1200(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1397(para)
+msgid "Length of each period (seconds) to evaluate over."
 msgstr ""
 
-#: ./doc/common/section_xapi-install-plugins.xml19(title)
-msgid "Manually install the plug-in"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1002(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1208(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1405(para)
+msgid "Number of periods to evaluate over."
 msgstr ""
 
-#: ./doc/common/section_xapi-install-plugins.xml22(para)
-msgid "Create temporary files/directories:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1010(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1216(para)
+msgid "Statistic to evaluate, one of: ['max', 'min', 'avg', 'sum', 'count']."
 msgstr ""
 
-#: ./doc/common/section_xapi-install-plugins.xml27(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1019(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1225(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1430(para)
 msgid ""
-"Get the source from github. The example assumes the master branch is used. "
-"Amend the URL to match the version being used:"
+"Operator to compare with, one of: ['lt', 'le', 'eq', 'ne', 'ge', 'gt']."
 msgstr ""
 
-#: ./doc/common/section_xapi-install-plugins.xml32(para)
-msgid ""
-"(Alternatively) To use the official Ubuntu packages, use the following "
-"commands to get the nova code base:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1028(para)
+msgid "Threshold to evaluate against. Required."
 msgstr ""
 
-#: ./doc/common/section_xapi-install-plugins.xml39(para)
-msgid "Copy the plug-ins to the hypervisor:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1055(title)
+msgid "ceilometer alarm-threshold-update command"
 msgstr ""
 
-#: ./doc/common/section_xapi-install-plugins.xml44(para)
-msgid "Remove the temporary files/directories:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1192(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1413(para)
+msgid "Metric to evaluate against."
 msgstr ""
 
-#: ./doc/common/section_xapi-install-plugins.xml51(title)
-msgid "Package a XenServer supplemental pack"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1234(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1439(para)
+msgid "Threshold to evaluate against."
 msgstr ""
 
-#: ./doc/common/section_xapi-install-plugins.xml52(para)
-msgid ""
-"Follow these steps to produce a supplemental pack from the nova sources, and"
-" package it as a XenServer supplemental pack."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1261(title)
+msgid "ceilometer alarm-update command"
 msgstr ""
 
-#: ./doc/common/section_xapi-install-plugins.xml57(para)
-msgid ""
-"Create RPM packages. Given you have the nova sources. Use one of the methods"
-" in <xref linkend=\"manual_install\"/>:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1421(para)
+msgid "Statistic to evaluate, one of: ['max', 'min', 'avg', 'sum', 'count']"
 msgstr ""
 
-#: ./doc/common/section_xapi-install-plugins.xml62(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1447(para)
 msgid ""
-"These commands leave an <filename>.rpm</filename> file in the "
-"<filename>rpmbuild/RPMS/noarch/</filename> directory."
+"A meter should match this resource metadata (key=value) additionally to the "
+"meter_name. Defaults to None."
 msgstr ""
 
-#: ./doc/common/section_xapi-install-plugins.xml68(para)
-msgid ""
-"Pack the RPM packages to a Supplemental Pack, using the XenServer DDK (the "
-"following command should be issued on the XenServer DDK virtual appliance, "
-"after the produced rpm file has been copied over):"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1466(title)
+msgid "ceilometer event-list command"
 msgstr ""
 
-#: ./doc/common/section_xapi-install-plugins.xml81(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1475(para)
 msgid ""
-"This command produces an <filename>.iso</filename> file in the output "
-"directory specified. Copy that file to the hypervisor."
-msgstr ""
-
-#: ./doc/common/section_xapi-install-plugins.xml87(para)
-msgid "Install the Supplemental Pack. Log in to the hypervisor, and issue:"
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-vnc-window.xml6(title)
-msgid "Change the size of the dashboard VNC window"
+"key[op]data_type::value; list. data_type is optional, but if supplied must "
+"be string, integer, floator datetime."
 msgstr ""
 
-#: ./doc/common/section_dashboard-configure-vnc-window.xml7(para)
-msgid ""
-"The <filename>_detail_vnc.html</filename> file defines the size of the VNC "
-"window. To change the window size, edit this file."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1485(title)
+msgid "ceilometer event-show command"
 msgstr ""
 
-#: ./doc/common/section_dashboard-configure-vnc-window.xml12(para)
-msgid ""
-"Edit "
-"<filename>/usr/share/pyshared/horizon/dashboards/nova/instances/templates/instances/_detail_vnc.html.</filename>"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1494(para)
+msgid "The id of the event. Should be a UUID Required."
 msgstr ""
 
-#: ./doc/common/section_dashboard-configure-vnc-window.xml16(para)
-msgid ""
-"Modify the <literal>width</literal> and <literal>height</literal> "
-"parameters, as follows:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1502(title)
+msgid "ceilometer event-type-list command"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_fileinjection.xml10(title)
-msgid "Inject files into instances"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1509(title)
+msgid "ceilometer meter-list command"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_fileinjection.xml11(para)
-msgid ""
-"You can inject local files into the instance file system when you launch an "
-"instance."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1528(title)
+msgid "ceilometer query-alarm-history command"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_fileinjection.xml13(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1538(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1574(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1610(para)
 msgid ""
-"Use the <parameter>--file dst-path=src-path</parameter> parameter on the "
-"nova <placeholder-1/> command."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_fileinjection.xml15(para)
-msgid "You can inject up to five files."
+"{complex_op: [{simple_op: {field_name: value}}]} The complex_op is one of: "
+"['and', 'or'], simple_op is one of: ['=', '!=', '&lt;', '&lt;=', '&gt;', "
+"'&gt;=']."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_fileinjection.xml16(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1548(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1584(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1620(para)
 msgid ""
-"For example, you might inject the "
-"<filename>special_authorized_keysfile</filename> file into the instance "
-"rather than using the regular ssh key injection."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_fileinjection.xml19(para)
-msgid "Run the following command:<placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml7(title)
-msgid "Certificates for PKI"
+"[{field_name: direction}, {field_name: direction}] The direction is one of: "
+"['asc', 'desc']."
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml8(para)
-msgid ""
-"PKI stands for Public Key Infrastructure. Tokens are documents, "
-"cryptographically signed using the X509 standard. In order to work correctly"
-" token generation requires a public/private key pair. The public key must be"
-" signed in an X509 certificate, and the certificate used to sign it must be "
-"available as Certificate Authority (CA) certificate. These files can be "
-"generated either using the <placeholder-1/> utility, or externally "
-"generated. The files need to be in the locations specified by the top level "
-"Identity Service configuration file <filename>keystone.conf</filename> as "
-"specified in the above section. Additionally, the private key should only be"
-" readable by the system user that will run the Identity Service."
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml23(para)
-msgid ""
-"The certificates can be world readable, but the private key cannot be. The "
-"private key should only be readable by the account that is going to sign "
-"tokens. When generating files with the <placeholder-1/> command, your best "
-"option is to run as the pki user. If you run nova-manage as root, you can "
-"append --keystone-user and --keystone-group parameters to set the username "
-"and group keystone is going to run under."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1557(para)
+msgid "Maximum number of alarm history items to return."
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml33(para)
-msgid ""
-"The values that specify where to read the certificates are under the "
-"<literal>[signing]</literal> section of the configuration file. The "
-"configuration values are:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1565(title)
+msgid "ceilometer query-alarms command"
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml38(para)
-msgid ""
-"<literal>token_format</literal> - Determines the algorithm used to generate "
-"tokens. Can be either <literal>UUID</literal> or <literal>PKI</literal>. "
-"Defaults to <literal>PKI</literal>."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1593(para)
+msgid "Maximum number of alarms to return."
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml45(para)
-msgid ""
-"<literal>certfile</literal> - Location of certificate used to verify tokens."
-" Default is <literal>/etc/keystone/ssl/certs/signing_cert.pem</literal>."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1601(title)
+msgid "ceilometer query-samples command"
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml51(para)
-msgid ""
-"<literal>keyfile</literal> - Location of private key used to sign tokens. "
-"Default is <literal>/etc/keystone/ssl/private/signing_key.pem</literal>."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1629(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1789(para)
+msgid "Maximum number of samples to return."
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml57(para)
-msgid ""
-"<literal>ca_certs</literal> - Location of certificate for the authority that"
-" issued the above certificate. Default is "
-"<literal>/etc/keystone/ssl/certs/ca.pem</literal>."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1637(title)
+msgid "ceilometer resource-list command"
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml64(para)
-msgid "<literal>key_size</literal> - Default is <literal>1024</literal>."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1656(title)
+msgid "ceilometer resource-show command"
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml69(para)
-msgid "<literal>valid_days</literal> - Default is <literal>3650</literal>."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1665(para)
+msgid "ID of the resource to show. Required."
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml74(para)
-msgid ""
-"<literal>ca_password</literal> - Password required to read the "
-"<literal>ca_file</literal>. Default is <literal>None</literal>."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1673(title)
+msgid "ceilometer sample-create command"
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml80(para)
-msgid ""
-"If <literal>token_format=UUID</literal>, a typical token looks like "
-"<literal>53f7f6ef0cc344b5be706bcc8b1479e1</literal>. If "
-"<literal>token_format=PKI</literal>, a typical token is a much longer "
-"string, such as:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1688(para)
+msgid "Tenant to associate with sample (only settable by admin users)."
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml113(title)
-msgid "Sign certificate issued by external CA"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1697(para)
+msgid "User to associate with sample (only settable by admin users)."
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml114(para)
-msgid ""
-"You can use a signing certificate issued by an external CA instead of "
-"generated by <placeholder-1/>. However, a certificate issued by an external "
-"CA must satisfy the following conditions:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1706(para)
+msgid "ID of the resource. Required."
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml121(para)
-msgid ""
-"all certificate and key files must be in Privacy Enhanced Mail (PEM) format"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1714(para)
+msgid "The meter name. Required."
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml125(para)
-msgid "private key files must not be protected by a password"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1722(para)
+msgid "The meter type. Required."
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml129(para)
-msgid ""
-"When using signing certificate issued by an external CA, you do not need to "
-"specify <literal>key_size</literal>, <literal>valid_days</literal>, and "
-"<literal>ca_password</literal> as they will be ignored."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1730(para)
+msgid "The meter unit. Required."
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml134(para)
-msgid ""
-"The basic workflow for using a signing certificate issued by an external CA "
-"involves:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1738(para)
+msgid "The sample volume. Required."
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml138(para)
-msgid "Request Signing Certificate from External CA"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1746(para)
+msgid "Resource metadata."
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml142(para)
-msgid "Convert certificate and private key to PEM if needed"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1754(para)
+msgid "The sample timestamp."
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml146(para)
-msgid "Install External Signing Certificate"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1762(title)
+msgid "ceilometer sample-list command"
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml151(title)
-msgid "Request a signing certificate from an external CA"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1781(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1817(para)
+msgid "Name of meter to show samples for. Required."
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml153(para)
-msgid ""
-"One way to request a signing certificate from an external CA is to first "
-"generate a PKCS #10 Certificate Request Syntax (CRS) using OpenSSL CLI."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1797(title)
+msgid "ceilometer statistics command"
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml156(para)
-msgid ""
-"Create a certificate request configuration file. For example, create the "
-"<filename>cert_req.conf</filename> file, as follows:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1825(para)
+msgid "Period in seconds over which to group samples."
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml176(para)
-msgid ""
-"Then generate a CRS with OpenSSL CLI. <emphasis role=\"strong\">Do not "
-"encrypt the generated private key. Must use the -nodes option.</emphasis>"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1833(para)
+msgid "Field for group by."
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml183(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1841(para)
 msgid ""
-"If everything is successful, you should end up with "
-"<filename>signing_cert_req.pem</filename> and "
-"<filename>signing_key.pem</filename>. Send "
-"<filename>signing_cert_req.pem</filename> to your CA to request a token "
-"signing certificate and make sure to ask the certificate to be in PEM "
-"format. Also, make sure your trusted CA certificate chain is also in PEM "
-"format."
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml193(title)
-msgid "Install an external signing certificate"
+"Function for data aggregation. Available aggregates are: count, cardinality,"
+" min, max, sum, stddev, avg. Defaults to []."
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml194(para)
-msgid "Assuming you have the following already:"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1851(title)
+msgid "ceilometer trait-description-list command"
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml197(para)
-msgid ""
-"<filename>signing_cert.pem</filename> - (Keystone token) signing certificate"
-" in PEM format"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1860(para)
+msgid "Type of the event for which traits will be shown. Required."
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml202(para)
-msgid ""
-"<filename>signing_key.pem</filename> - corresponding (non-encrypted) private"
-" key in PEM format"
+#: ./doc/common/ch_cli_ceilometer_commands.xml1869(title)
+msgid "ceilometer trait-list command"
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml208(para)
+#: ./doc/common/ch_cli_ceilometer_commands.xml1871(para)
 msgid ""
-"<filename>cacert.pem</filename> - trust CA certificate chain in PEM format"
-msgstr ""
-
-#: ./doc/common/section_keystone_certificates-for-pki.xml213(para)
-msgid "Copy the above to your certificate directory. For example:"
+"List trait all traits with name &lt;trait_name&gt; for Event Type "
+"&lt;event_type&gt;."
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml221(para)
-msgid "Make sure the certificate directory is only accessible by root."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1878(para)
+msgid "Type of the event for which traits will listed. Required."
 msgstr ""
 
-#: ./doc/common/section_keystone_certificates-for-pki.xml224(para)
-msgid ""
-"If your certificate directory path is different from the default "
-"<filename>/etc/keystone/ssl/certs</filename>, make sure it is reflected in "
-"the <literal>[signing]</literal> section of the configuration file."
+#: ./doc/common/ch_cli_ceilometer_commands.xml1887(para)
+msgid "The name of the trait to list. Required."
 msgstr ""
 
 #: ./doc/common/ch_cli_cinder_commands.xml11(title)
@@ -15994,6962 +16111,503 @@ msgstr ""
 msgid "Optional type for disk format (Default=raw)"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml7(title)
-#: ./doc/common/section_dashboard_access.xml304(guilabel)
-msgid "Flavors"
-msgstr "フレーバー"
+#: ./doc/common/section_cli_glance_manage_images.xml7(title)
+msgid "Manage images"
+msgstr "イメージの管理"
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml8(para)
+#: ./doc/common/section_cli_glance_manage_images.xml8(para)
 msgid ""
-"Admin users can use the <placeholder-1/> commands to customize and manage "
-"flavors. To see the available flavor-related commands, run:"
-msgstr ""
+"The cloud operator assigns roles to users. Roles determine who can upload "
+"and manage images. The operator might restrict image upload and management "
+"to only cloud administrators or operators."
+msgstr "クラウド運用者はユーザーにロールを割り当てます。ロールはイメージをアップロードおよび管理できるユーザーを決定します。運用者はイメージのアップロードと管理をクラウド管理者や運用者のみに制限するかもしれません。"
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml22(para)
+#: ./doc/common/section_cli_glance_manage_images.xml12(para)
 msgid ""
-"Configuration rights can be delegated to additional users by redefining the "
-"access controls for <option>compute_extension:flavormanage</option> in "
-"<filename>/etc/nova/policy.json</filename> on the <systemitem class=\"server"
-"\">nova-api</systemitem> server."
-msgstr ""
+"You can upload images through the <placeholder-1/> client or the Image "
+"Service API. You can also use the <placeholder-2/> client to list images, "
+"set and delete image metadata, delete images, and take a snapshot of a "
+"running instance to create an image. After you upload an image, you cannot "
+"change it."
+msgstr "<placeholder-1/> クライアントまたは Image Service API 経由でイメージをアップロードできます。また <placeholder-2/> クライアントを使用して、イメージを一覧表示し、イメージのメタデータを設定、削除し、イメージを削除するできます。また、イメージを作成するために稼働中のインスタンスのスナップショットを取得できます。イメージのアップロード後、変更できません。"
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml26(para)
+#: ./doc/common/section_cli_glance_manage_images.xml16(para)
 msgid ""
-"To modify an existing flavor in the dashboard, you must delete the flavor "
-"and create a modified one with the same name."
-msgstr ""
+"For details about image creation, see the <link "
+"href=\"http://docs.openstack.org/image-guide/content/\"><citetitle>Virtual "
+"Machine Image Guide</citetitle></link>."
+msgstr "イメージの作成に関する詳細は<link href=\"http://docs.openstack.org/image-guide/content/\"><citetitle>仮想マシンイメージガイド</citetitle></link>を参照してください。"
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml31(para)
-msgid "Flavors define these elements:"
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml21(title)
+msgid "List or get details for images (glance)"
+msgstr "イメージ (glance) の詳細の一覧表示と取得"
 
-#: ./doc/common/section_cli_nova_customize_flavors.xml33(caption)
-msgid "Identity Service configuration file sections"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml39(td)
-msgid "Element"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml45(literal)
-msgid "Name"
-msgstr "名前"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml47(replaceable)
-msgid "XX"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml47(replaceable)
-msgid "SIZE_NAME"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml46(td)
-msgid ""
-"A descriptive name. <placeholder-1/>.<placeholder-2/> is typically not "
-"required, though some third party tools may rely on it."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml52(literal)
-msgid "Memory_MB"
-msgstr "MB メモリー"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml53(td)
-msgid "Virtual machine memory in megabytes."
-msgstr "メガバイト単位の仮想マシンメモリー。"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml56(literal)
-msgid "Disk"
-msgstr "ディスク"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml57(td)
-msgid ""
-"Virtual root disk size in gigabytes. This is an ephemeral disk that the base"
-" image is copied into. When booting from a persistent volume it is not used."
-" The \"0\" size is a special case which uses the native base image size as "
-"the size of the ephemeral root volume."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml65(literal)
-msgid "Ephemeral"
-msgstr "エフェメラル"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml66(td)
-msgid ""
-"Specifies the size of a secondary ephemeral data disk. This is an empty, "
-"unformatted disk and exists only for the life of the instance."
-msgstr "二次的な一時データディスクの容量を指定します。これは空の、フォーマットされていないディスクです。インスタンスの生存期間だけ存在します。"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml71(literal)
-msgid "Swap"
-msgstr "スワップ"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml72(td)
-msgid "Optional swap space allocation for the instance."
-msgstr "インスタンスに割り当てられるスワップ空間。これはオプションです。"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml76(literal)
-msgid "VCPUs"
-msgstr "仮想 CPU"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml77(td)
-msgid "Number of virtual CPUs presented to the instance."
-msgstr "インスタンスに存在する仮想 CPU 数。"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml81(literal)
-msgid "RXTX_Factor"
-msgstr "RXTX_Factor"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml82(td)
-msgid ""
-"Optional property allows created servers to have a different bandwidth cap "
-"than that defined in the network they are attached to. This factor is "
-"multiplied by the rxtx_base property of the network. Default value is 1.0. "
-"That is, the same as attached network."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml90(literal)
-msgid "Is_Public"
-msgstr "Is_Public"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml91(td)
-msgid ""
-"Boolean value, whether flavor is available to all users or private to the "
-"tenant it was created in. Defaults to True."
-msgstr "論理値。フレーバーがすべてのユーザーに利用可能か、または作成されたプロジェクト内のみであるか。標準で真 (True) です。"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml96(literal)
-msgid "extra_specs"
-msgstr "extra_specs"
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml97(para)
-msgid ""
-"Key and value pairs that define on which compute nodes a flavor can run. "
-"These pairs must match corresponding pairs on the compute nodes. Use to "
-"implement special resources, such as flavors that run on only compute nodes "
-"with GPU hardware."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml105(para)
-msgid ""
-"Flavor customization can be limited by the hypervisor in use. For example "
-"the <systemitem>libvirt</systemitem> driver enables quotas on CPUs available"
-" to a VM, disk tuning, bandwidth I/O, watchdog behavior, random number "
-"generator device control, and instance VIF traffic control."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml110(term)
-msgid "CPU limits"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml111(para)
-msgid ""
-"You can configure the CPU limits with control parameters with the "
-"<placeholder-1/> client. For example, to configure the I/O limit, use:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml115(para)
-msgid ""
-"There are optional CPU control parameters for weight shares, enforcement "
-"intervals for runtime quotas, and a quota for maximum allowed bandwidth:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml121(para)
-msgid ""
-"<literal>cpu_shares</literal> specifies the proportional weighted share for "
-"the domain. If this element is omitted, the service defaults to the OS "
-"provided defaults. There is no unit for the value; it is a relative measure "
-"based on the setting of other VMs. For example, a VM configured with value "
-"2048 gets twice as much CPU time as a VM configured with value 1024."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml130(para)
-msgid ""
-"<literal>cpu_period</literal> specifies the enforcement interval (unit: "
-"microseconds) for QEMU and LXC hypervisors. Within a period, each VCPU of "
-"the domain is not allowed to consume more than the quota worth of runtime. "
-"The value should be in range <literal>[1000, 1000000]</literal>. A period "
-"with value 0 means no value."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml138(para)
-msgid ""
-"<literal>cpu_quota</literal> specifies the maximum allowed bandwidth (unit: "
-"microseconds). A domain with a negative-value quota indicates that the "
-"domain has infinite bandwidth, which means that it is not bandwidth "
-"controlled. The value should be in range <literal>[1000, "
-"18446744073709551]</literal> or less than 0. A quota with value 0 means no "
-"value. You can use this feature to ensure that all vCPUs run at the same "
-"speed. For example:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml147(para)
-msgid ""
-"In this example, the instance of <literal>m1.low_cpu</literal> can only "
-"consume a maximum of 50% CPU of a physical CPU computing capability."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml155(term)
-msgid "Disk tuning"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml156(para)
-msgid ""
-"Using disk I/O quotas, you can set maximum disk write to 10 MB per second "
-"for a VM user. For example:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml159(para)
-msgid "The disk I/O options are:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml162(para)
-msgid "disk_read_bytes_sec"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml165(para)
-msgid "disk_read_iops_sec"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml168(para)
-msgid "disk_write_bytes_sec"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml171(para)
-msgid "disk_write_iops_sec"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml174(para)
-msgid "disk_total_bytes_sec"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml177(para)
-msgid "disk_total_iops_sec"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml180(para)
-msgid "The vif I/O options are:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml183(para)
-msgid "vif_inbound_ average"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml186(para)
-msgid "vif_inbound_burst"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml189(para)
-msgid "vif_inbound_peak"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml192(para)
-msgid "vif_outbound_ average"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml195(para)
-msgid "vif_outbound_burst"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml198(para)
-msgid "vif_outbound_peak"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml202(term)
-msgid "Bandwidth I/O"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml203(para)
-msgid ""
-"Incoming and outgoing traffic can be shaped independently. The bandwidth "
-"element can have at most one inbound and at most one outbound child element."
-" If you leave any of these children element out, no quality of service (QoS)"
-" is applied on that traffic direction. So, if you want to shape only the "
-"network's incoming traffic, use inbound only (and vice versa). Each element "
-"has one mandatory attribute average, which specifies the average bit rate on"
-" the interface being shaped."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml209(para)
-msgid ""
-"There are also two optional attributes (integer): <option>peak</option>, "
-"which specifies maximum rate at which bridge can send data "
-"(kilobytes/second), and <option>burst</option>, the amount of bytes that can"
-" be burst at peak speed (kilobytes). The rate is shared equally within "
-"domains connected to the network."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml214(para)
-msgid ""
-"The following example configures a bandwidth limit for instance network "
-"traffic:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml219(term)
-msgid "Watchdog behavior"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml220(para)
-msgid ""
-"For the <systemitem>libvirt</systemitem> driver, you can enable and set the "
-"behavior of a virtual hardware watchdog device for each flavor. Watchdog "
-"devices keep an eye on the guest server, and carry out the configured action"
-" if the server hangs. The watchdog uses the i6300esb device (emulating a PCI"
-" Intel 6300ESB). If <literal>hw_watchdog_action</literal> is not specified, "
-"the watchdog is disabled."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml226(para)
-msgid "To set the behavior, use:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml227(replaceable)
-#: ./doc/common/section_cli_nova_customize_flavors.xml257(replaceable)
-#: ./doc/common/section_cli_nova_customize_flavors.xml258(replaceable)
-#: ./doc/common/section_cli_nova_customize_flavors.xml259(replaceable)
-msgid "FLAVOR-NAME"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml227(replaceable)
-msgid "ACTION"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml228(para)
-msgid "Valid <replaceable>ACTION</replaceable> values are:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml231(para)
-msgid "<literal>disabled</literal>(default) The device is not attached."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml234(para)
-msgid "<literal>reset</literal>Forcefully reset the guest."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml238(para)
-msgid "<literal>poweroff</literal>Forcefully power off the guest."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml242(para)
-msgid "<literal>pause</literal>Pause the guest."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml245(para)
-msgid ""
-"<literal>none</literal>Only enable the watchdog; do nothing if the server "
-"hangs."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml249(para)
-msgid ""
-"Watchdog behavior set using a specific image's properties will override "
-"behavior set using flavors."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml254(term)
-msgid "Random-number generator"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml255(para)
-msgid ""
-"If a random-number generator device has been added to the instance through "
-"its image properties, the device can be enabled and configured using:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml258(replaceable)
-msgid "RATE-BYTES"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml259(replaceable)
-msgid "RATE-PERIOD"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml263(para)
-msgid ""
-"<replaceable>RATE-BYTES</replaceable>(Integer) Allowed amount of bytes that "
-"the guest can read from the host's entropy per period."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml267(para)
-msgid ""
-"<replaceable>RATE-PERIOD</replaceable>(Integer) Duration of the read period "
-"in seconds."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml273(term)
-msgid "Instance VIF traffic control"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_customize_flavors.xml274(para)
-msgid ""
-"Flavors can also be assigned to particular projects. By default, a flavor is"
-" public and available to all projects. Private flavors are only accessible "
-"to those on the access list and are invisible to other projects. To create "
-"and assign a private flavor to a project, run these commands:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_evacuate.xml6(title)
-msgid "Evacuate instances"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_evacuate.xml7(para)
-msgid ""
-"If a cloud compute node fails due to a hardware malfunction or another "
-"reason, you can evacuate instances to make them available again. You can "
-"choose evacuation parameters for your use case."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_evacuate.xml10(para)
-msgid ""
-"To preserve user data on server disk, you must configure shared storage on "
-"the target host. Also, you must validate that the current VM host is down; "
-"otherwise, the evacuation fails with an error."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_evacuate.xml15(para)
-msgid ""
-"To list hosts and find a different host for the evacuated instance, run:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_evacuate.xml19(para)
-msgid ""
-"Evacuate the instance. You can pass the instance password to the command by "
-"using the <literal>--password &lt;pwd&gt;</literal> option. If you do not "
-"specify a password, one is generated and printed after the command finishes "
-"successfully. The following command evacuates a server without shared "
-"storage from a host that is down to the specified "
-"<replaceable>host_b</replaceable>:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_evacuate.xml24(replaceable)
-#: ./doc/common/section_cli_nova_evacuate.xml40(replaceable)
-msgid "evacuated_server_name"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_evacuate.xml24(replaceable)
-#: ./doc/common/section_cli_nova_evacuate.xml40(replaceable)
-msgid "host_b"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_evacuate.xml25(para)
-msgid ""
-"The instance is booted from a new disk, but preserves its configuration "
-"including its ID, name, uid, IP address, and so on. The command returns a "
-"password:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_evacuate.xml34(para)
-msgid ""
-"To preserve the user disk data on the evacuated server, deploy OpenStack "
-"Compute with a shared file system. To configure your system, see <link "
-"href=\"http://docs.openstack.org/icehouse/config-reference/content"
-"/configuring-openstack-compute-basics.html#section_configuring-compute-"
-"migrations\">Configure migrations</link> in <citetitle>OpenStack "
-"Configuration Reference</citetitle>. In the following example, the password "
-"remains unchanged:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_read-only-volumes.xml6(title)
-msgid "Set a volume to read-only access"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_read-only-volumes.xml7(para)
-msgid ""
-"To give multiple users shared, secure access to the same data, you can set a"
-" volume to read-only access."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_read-only-volumes.xml9(para)
-msgid "Run the following command to set a volume to read-only access:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_read-only-volumes.xml11(replaceable)
-msgid "VOLUME"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_read-only-volumes.xml11(replaceable)
-msgid "BOOLEAN"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_read-only-volumes.xml12(para)
-msgid ""
-"<replaceable>VOLUME</replaceable> is the ID of the target volume and "
-"<replaceable>BOOLEAN</replaceable> is a flag that enables read-only or "
-"read/write access to the volume."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_read-only-volumes.xml15(para)
-msgid "The following values for <replaceable>BOOLEAN</replaceable> are valid:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_read-only-volumes.xml19(para)
-msgid ""
-"<literal>true</literal>. Sets the read-only flag in the volume. When you "
-"attach the volume to an instance, the instance checks for this flag to "
-"determine whether to restrict volume access to read-only."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_read-only-volumes.xml25(para)
-msgid "<literal>false</literal>. Sets the volume to read/write access."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml7(title)
-msgid "Create and manage networks"
-msgstr "ネットワークの作成と管理"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml8(para)
-msgid "Before you run commands, set the following environment variables:"
-msgstr "コマンドを実行する前に、以下の環境変数を設定します。"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml15(title)
-msgid "Create networks"
-msgstr "ネットワークの作成"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml18(para)
-msgid "List the extensions of the system:"
-msgstr "システムの拡張を表示します。"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml34(para)
-msgid "Create a network:"
-msgstr "ネットワークを作成します。"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml53(para)
-msgid "Some fields of the created network are invisible to non-admin users."
-msgstr "作成したネットワークのフィールドで管理者ユーザー以外には表示されないものもあります。"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml58(para)
-msgid "Create a network with specified provider network type:"
-msgstr "指定のプロバイダーネットワークタイプでネットワークを作成します。"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml77(para)
-msgid ""
-"Just as shown previously, the unknown option <literal>--provider:network-"
-"type</literal> is used to create a <literal>local</literal> provider "
-"network."
-msgstr "先ほど説明したように、不明オプション <literal>--provider:network-type</literal> を使用して、<literal>local</literal> プロバイダーネットワークを作成します。"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml85(title)
-msgid "Create subnets"
-msgstr "サブネットの作成"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml88(para)
-msgid "Create a subnet:"
-msgstr "サブネットを作成します。"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml106(para)
-msgid ""
-"The <placeholder-1/> command has the following positional and optional "
-"parameters:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml111(para)
-msgid "The name or ID of the network to which the subnet belongs."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml113(para)
-msgid ""
-"In this example, <literal>net1</literal> is a positional argument that "
-"specifies the network name."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml118(para)
-msgid "The CIDR of the subnet."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml119(para)
-msgid ""
-"In this example, <literal>192.168.2.0/24</literal> is a positional argument "
-"that specifies the CIDR."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml125(para)
-msgid "The subnet name, which is optional."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml127(para)
-msgid ""
-"In this example, <literal>--name subnet1</literal> specifies the name of the"
-" subnet."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml136(title)
-msgid "Create routers"
-msgstr "ルーターの作成"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml139(para)
-msgid "Create a router:"
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml140(replaceable)
-msgid "router1"
-msgstr "router1"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml152(para)
-msgid ""
-"Take note of the unique router identifier returned, this will be required in"
-" subsequent steps."
-msgstr "返された一意なルーター ID を記録します。これは以降の手順に必要となります。"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml156(para)
-msgid "Link the router to the external provider network:"
-msgstr "ルーターを外部プロバイダーネットワークにリンクします。"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml157(replaceable)
-#: ./doc/common/section_cli_neutron_manage_networks.xml164(replaceable)
-msgid "ROUTER"
-msgstr "ROUTER"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml157(replaceable)
-msgid "NETWORK"
-msgstr "NETWORK"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml158(para)
-msgid ""
-"Replace <replaceable>ROUTER</replaceable> with the unique identifier of the "
-"router, replace <replaceable>NETWORK</replaceable> with the unique "
-"identifier of the external provider network."
-msgstr "<replaceable>ROUTER</replaceable> をルーターの一意な ID で置き換え、<replaceable>NETWOKR</replaceable> を外部プロバイダールーターの一意な ID で置き換えます。"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml163(para)
-msgid "Link the router to the subnet:"
-msgstr "ルーターをサブネットにリンクします。"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml164(replaceable)
-msgid "SUBNET"
-msgstr "SUBNET"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml165(para)
-msgid ""
-"Replace <replaceable>ROUTER</replaceable> with the unique identifier of the "
-"router, replace <replaceable>SUBNET</replaceable> with the unique identifier"
-" of the subnet."
-msgstr "<replaceable>ROUTER</replaceable> をルーターの一意な ID で置き換え、<replaceable>SUBNET</replaceable> をサブネットの一意な ID で置き換えます。"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml172(title)
-msgid "Create ports"
-msgstr "ポートの作成"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml175(para)
-msgid "Create a port with specified IP address:"
-msgstr "指定の IP アドレスでポートを作成します。"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml194(para)
-msgid ""
-"In the previous command, <literal>net1</literal> is the network name, which "
-"is a positional argument. <literal>--fixed-ip "
-"ip_address=192.168.2.40</literal> is an option, which specifies the port's "
-"fixed IP address we wanted."
-msgstr "上記のコマンドでは、<literal>net1</literal> がネットワーク名で、位置引数となっています。 <literal>--fixed-ip ip_address=192.168.2.40</literal> はオプションで、希望のポートの Fixed IP アドレスを指定します。"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml201(para)
-msgid ""
-"When creating a port, you can specify any unallocated IP in the subnet even "
-"if the address is not in a pre-defined pool of allocated IP addresses (set "
-"by your cloud provider)."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml208(para)
-msgid "Create a port without specified IP address:"
-msgstr "IP アドレス指定なしでポートを作成します。"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml229(para)
-msgid ""
-"Note that the system allocates one IP address if you do not specify an IP "
-"address in the <placeholder-1/> command."
-msgstr ""
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml234(para)
-msgid "Query ports with specified fixed IP addresses:"
-msgstr "指定の Fixed IP アドレスでポートを問い合わせします。"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml243(para)
-msgid ""
-"<literal>--fixed-ips ip_address=192.168.2.2 "
-"ip_address=192.168.2.40</literal> is one unknown option."
-msgstr "<literal>--fixed-ips ip_address=192.168.2.2 ip_address=192.168.2.40</literal> は不明オプションです。"
-
-#: ./doc/common/section_cli_neutron_manage_networks.xml246(para)
-msgid ""
-"<emphasis role=\"bold\">How to find unknown options?</emphasis> The unknown "
-"options can be easily found by watching the output of "
-"<literal>create_xxx</literal> or <literal>show_xxx</literal> command. For "
-"example, in the port creation command, we see the fixed_ips fields, which "
-"can be used as an unknown option."
-msgstr "<emphasis role=\"bold\">不明オプションの探し方</emphasis>: 不明オプションは、<literal>create_xxx</literal> または <literal>show_xxx</literal> コマンドの出力を見ているとすぐに見つけられます。例えば、ポート作成コマンドには fixed_ips フィールドがありますが、これは不明オプションとして使用することができます。"
-
-#: ./doc/common/ch_preface.xml7(title)
-msgid "Preface"
-msgstr "はじめに"
-
-#: ./doc/common/section_cli_keystone_apiv3.xml5(title)
-msgid "Use Identity Service API v3 instead of API v2.0"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_apiv3.xml6(para)
-msgid ""
-"Use the following parameters in combination on any keystone command to "
-"specify which version of the API to use:"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_apiv3.xml11(para)
-msgid ""
-"<parameter>--os-endpoint</parameter>. The endpoint to use instead of the one"
-" in the service catalog. Defaults to <code>env[OS_SERVICE_ENDPOINT]</code>."
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_apiv3.xml15(para)
-msgid ""
-"The <literal>keystone</literal> client detects the version of the API from "
-"this parameter."
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_apiv3.xml19(para)
-msgid ""
-"<parameter>--os-auth_url</parameter>. The Identity Service endpoint to use "
-"for authentication. Defaults to <code>env[OS_AUTH_URL]</code>."
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_apiv3.xml25(para)
-msgid ""
-"<parameter>--os-identity-api-version</parameter>. The Identity Service API "
-"version. Defaults to <code>env[OS_IDENTITY_API_VERSION]</code> or "
-"<literal>2.0</literal>."
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_apiv3.xml31(para)
-msgid "For example, use the following parameters to use API v3:"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_apiv3.xml33(parameter)
-#: ./doc/common/section_cli_keystone_apiv3.xml35(parameter)
-msgid "--os-auth_url"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_apiv3.xml33(parameter)
-#: ./doc/common/section_cli_keystone_apiv3.xml35(parameter)
-msgid "--os-identity-api-version"
-msgstr ""
-
-#: ./doc/common/section_cli_keystone_apiv3.xml34(para)
-msgid "Use the following parameters to use API v2.0:"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_trusted-compute-pools.xml45(None)
-#: ./doc/common/section_trusted-compute-pools.xml50(None)
-msgid ""
-"@@image: 'figures/OpenStackTrustedComputePool1.png'; "
-"md5=858fbd6148b927723cea5ad2c88d54bd"
-msgstr "@@image: 'figures/OpenStackTrustedComputePool1.png'; md5=858fbd6148b927723cea5ad2c88d54bd"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_trusted-compute-pools.xml150(None)
-#: ./doc/common/section_trusted-compute-pools.xml155(None)
-msgid ""
-"@@image: 'figures/OpenStackTrustedComputePool2.png'; "
-"md5=077261c595464638c4b3fcc92b6afb9a"
-msgstr "@@image: 'figures/OpenStackTrustedComputePool2.png'; md5=077261c595464638c4b3fcc92b6afb9a"
-
-#: ./doc/common/section_trusted-compute-pools.xml6(title)
-msgid "Trusted compute pools"
-msgstr "信頼済コンピュートプール"
-
-#: ./doc/common/section_trusted-compute-pools.xml7(para)
-msgid ""
-"Trusted compute pools enable administrators to designate a group of compute "
-"hosts as trusted. These hosts use hardware-based security features, such as "
-"the Intel Trusted Execution Technology (TXT), to provide an additional level"
-" of security. Combined with an external stand-alone, web-based remote "
-"attestation server, cloud providers can ensure that the compute node runs "
-"only software with verified measurements and can ensure a secure cloud "
-"stack."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml13(para)
-msgid ""
-"Using the trusted compute pools, cloud subscribers can request services to "
-"run on verified compute nodes."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml15(para)
-msgid "The remote attestation server performs node verification as follows:"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml19(para)
-msgid "Compute nodes boot with Intel TXT technology enabled."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml23(para)
-msgid "The compute node BIOS, hypervisor, and OS are measured."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml27(para)
-msgid ""
-"Measured data is sent to the attestation server when challenged by the "
-"attestation server."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml31(para)
-msgid ""
-"The attestation server verifies those measurements against a good and known "
-"database to determine node trustworthiness."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml35(para)
-msgid ""
-"A description of how to set up an attestation service is beyond the scope of"
-" this document. For an open source project that you can use to implement an "
-"attestation service, see the <link "
-"href=\"https://github.com/OpenAttestation/OpenAttestation\">Open "
-"Attestation</link> project."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml54(title)
-msgid "Configure Compute to use trusted compute pools"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml57(para)
-msgid ""
-"Enable scheduling support for trusted compute pools by adding the following "
-"lines in the <literal>DEFAULT</literal> section in the "
-"<filename>/etc/nova/nova.conf</filename> file:"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml66(para)
-msgid ""
-"Specify the connection information for your attestation service by adding "
-"the following lines to the <literal>trusted_computing</literal> section in "
-"the <filename>/etc/nova/nova.conf</filename> file:"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml81(term)
-msgid "server"
-msgstr "サーバー"
-
-#: ./doc/common/section_trusted-compute-pools.xml83(para)
-msgid "Host name or IP address of the host that runs the attestation service."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml88(term)
-msgid "port"
-msgstr "port"
-
-#: ./doc/common/section_trusted-compute-pools.xml90(para)
-msgid "HTTPS port for the attestation service."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml94(term)
-msgid "server_ca_file"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml96(para)
-msgid "Certificate file used to verify the attestation server's identity."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml101(term)
-msgid "api_url"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml103(para)
-msgid "The attestation service's URL path."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml107(term)
-msgid "auth_blob"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml109(para)
-msgid "An authentication blob, which is required by the attestation service."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml117(para)
-msgid ""
-"Restart the <systemitem class=\"service\">nova-compute</systemitem> and "
-"<systemitem class=\"service\">nova-scheduler</systemitem> services."
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml124(title)
-#: ./doc/common/section_compute_config-api.xml183(title)
-msgid "Configuration reference"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml125(para)
-msgid ""
-"To customize the trusted compute pools, use the following configuration "
-"option settings:"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml132(title)
-msgid "Specify trusted flavors"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml133(para)
-msgid "To designate hosts as trusted:"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml136(para)
-msgid ""
-"Configure one or more flavors as trusted by using the <placeholder-1/> "
-"command. For example, to set the <literal>m1.tiny</literal> flavor as "
-"trusted:"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml141(para)
-msgid ""
-"Request that your instance be run on a trusted host, by specifying a trusted"
-" flavor when booting the instance. For example:"
-msgstr ""
-
-#: ./doc/common/section_trusted-compute-pools.xml145(title)
-msgid "Trusted compute pool"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-ec2.xml6(title)
-msgid "Configure the EC2 API"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-ec2.xml7(para)
-msgid ""
-"You can set options in the <filename>nova.conf</filename> configuration file"
-" to control which network address and port the EC2 API listens on, the "
-"formatting of some API responses, and authentication related options."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-ec2.xml11(para)
-msgid ""
-"To customize these options for OpenStack EC2 API, use the configuration "
-"option settings documented in <xref linkend=\"config_table_nova_ec2\"/>."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml7(title)
-msgid "Features and benefits"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml12(th)
-msgid "Features"
-msgstr "特徴"
-
-#: ./doc/common/section_objectstorage-features.xml13(th)
-msgid "Benefits"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml18(emphasis)
-msgid "Leverages commodity hardware"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml19(td)
-msgid "No lock-in, lower price/GB."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml22(emphasis)
-msgid "HDD/node failure agnostic"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml23(td)
-msgid "Self-healing, reliable, data redundancy protects from failures."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml27(emphasis)
-msgid "Unlimited storage"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml28(td)
-msgid ""
-"Large and flat namespace, highly scalable read/write access, able to serve "
-"content directly from storage system."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml32(emphasis)
-msgid "Multi-dimensional scalability"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml34(td)
-msgid ""
-"Scale-out architecture: Scale vertically and horizontally-distributed "
-"storage. Backs up and archives large amounts of data with linear "
-"performance."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml39(emphasis)
-msgid "Account/container/object structure"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml40(td)
-msgid ""
-"No nesting, not a traditional file system: Optimized for scale, it scales to"
-" multiple petabytes and billions of objects."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml45(emphasis)
-msgid "Built-in replication 3✕ + data redundancy (compared with 2✕ on RAID)"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml48(td)
-msgid ""
-"A configurable number of accounts, containers and object copies for high "
-"availability."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml52(emphasis)
-msgid "Easily add capacity (unlike RAID resize)"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml54(td)
-msgid "Elastic data scaling with ease"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml57(emphasis)
-msgid "No central database"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml58(td)
-msgid "Higher performance, no bottlenecks"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml61(emphasis)
-msgid "RAID not required"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml62(td)
-msgid "Handle many small, random reads and writes efficiently"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml65(emphasis)
-msgid "Built-in management utilities"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml66(td)
-msgid ""
-"Account management: Create, add, verify, and delete users; Container "
-"management: Upload, download, and verify; Monitoring: Capacity, host, "
-"network, log trawling, and cluster health."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml72(emphasis)
-msgid "Drive auditing"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml73(td)
-msgid "Detect drive failures preempting data corruption"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml76(emphasis)
-msgid "Expiring objects"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml77(td)
-msgid ""
-"Users can set an expiration time or a TTL on an object to control access"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml81(emphasis)
-msgid "Direct object access"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml82(td)
-msgid "Enable direct browser access to content, such as for a control panel"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml86(emphasis)
-msgid "Realtime visibility into client requests"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml88(td)
-msgid "Know what users are requesting."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml91(emphasis)
-msgid "Supports S3 API"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml92(td)
-msgid "Utilize tools that were designed for the popular S3 API."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml96(emphasis)
-msgid "Restrict containers per account"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml98(td)
-msgid "Limit access to control usage by user."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml101(emphasis)
-msgid "Support for NetApp, Nexenta, SolidFire"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml103(td)
-msgid "Unified support for block volumes using a variety of storage systems."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml107(emphasis)
-msgid "Snapshot and backup API for block volumes"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml109(td)
-msgid "Data protection and recovery for VM data."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml112(emphasis)
-msgid "Standalone volume API available"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml114(td)
-msgid "Separate endpoint and API for integration with other compute systems."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml118(emphasis)
-msgid "Integration with Compute"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-features.xml120(td)
-msgid ""
-"Fully integrated with Compute for attaching block volumes and reporting on "
-"usage."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml6(title)
-msgid "User management"
-msgstr "ユーザー管理"
-
-#: ./doc/common/section_keystone-concepts-user-management.xml7(para)
-msgid "The main components of Identity user management are:"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml10(para)
-msgid ""
-"<emphasis role=\"bold\">User</emphasis>. Represents a human user. Has "
-"associated information such as user name, password, and email. This example "
-"creates a user named <literal>alice</literal>:"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml17(para)
-msgid ""
-"<emphasis role=\"bold\">Tenant</emphasis>. A project, group, or "
-"organization. When you make requests to OpenStack services, you must specify"
-" a tenant. For example, if you query the Compute service for a list of "
-"running instances, you get a list of all running instances in the tenant "
-"that you specified in your query. This example creates a tenant named "
-"<literal>acme</literal>:"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml27(para)
-msgid ""
-"Because the term <emphasis>project</emphasis> was used instead of "
-"<emphasis>tenant</emphasis> in earlier versions of OpenStack Compute, some "
-"command-line tools use <literal>--project_id</literal> instead of <literal"
-">--tenant-id</literal> or <literal>--os-tenant-id</literal> to refer to a "
-"tenant ID."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml38(para)
-msgid ""
-"<emphasis role=\"bold\">Role</emphasis>. Captures the operations that a user"
-" can perform in a given tenant."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml40(para)
-msgid "This example creates a role named <literal>compute-user</literal>:"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml44(para)
-msgid ""
-"Individual services, such as Compute and the Image Service, assign meaning "
-"to roles. In the Identity Service, a role is simply a name."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml51(para)
-msgid ""
-"The Identity Service assigns a tenant and a role to a user. You might assign"
-" the <literal>compute-user</literal> role to the <literal>alice</literal> "
-"user in the <literal>acme</literal> tenant:"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml74(para)
-msgid ""
-"A user can have different roles in different tenants. For example, Alice "
-"might also have the <literal>admin</literal> role in the "
-"<literal>Cyberdyne</literal> tenant. A user can also have multiple roles in "
-"the same tenant."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml78(para)
-msgid ""
-"The "
-"<filename>/etc/<replaceable>[SERVICE_CODENAME]</replaceable>/policy.json</filename>"
-" file controls the tasks that users can perform for a given service. For "
-"example, <filename>/etc/nova/policy.json</filename> specifies the access "
-"policy for the Compute service, <filename>/etc/glance/policy.json</filename>"
-" specifies the access policy for the Image Service, and "
-"<filename>/etc/keystone/policy.json</filename> specifies the access policy "
-"for the Identity Service."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml88(para)
-msgid ""
-"The default <filename>policy.json</filename> files in the Compute, Identity,"
-" and Image Service recognize only the <literal>admin</literal> role: all "
-"operations that do not require the <literal>admin</literal> role are "
-"accessible by any user that has any role in a tenant."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml93(para)
-msgid ""
-"If you wish to restrict users from performing operations in, say, the "
-"Compute service, you need to create a role in the Identity Service and then "
-"modify <filename>/etc/nova/policy.json</filename> so that this role is "
-"required for Compute operations."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml99(para)
-msgid ""
-"For example, this line in <filename>/etc/nova/policy.json</filename> "
-"specifies that there are no restrictions on which users can create volumes: "
-"if the user has any role in a tenant, they can create volumes in that "
-"tenant."
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml105(para)
-msgid ""
-"To restrict creation of volumes to users who had the <literal>compute-"
-"user</literal> role in a particular tenant, you would add <literal>\"role"
-":compute-user\"</literal>, like so:"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-user-management.xml110(para)
-msgid ""
-"To restrict all Compute service requests to require this role, the resulting"
-" file would look like:"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-spice.xml6(title)
-msgid "SPICE console"
-msgstr ""
-
-#: ./doc/common/section_compute-configure-spice.xml7(para)
-msgid ""
-"OpenStack Compute supports VNC consoles to guests. The VNC protocol is "
-"fairly limited, lacking support for multiple monitors, bi-directional audio,"
-" reliable cut-and-paste, video streaming and more. SPICE is a new protocol "
-"that aims to address the limitations in VNC and provide good remote desktop "
-"support."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-spice.xml12(para)
-msgid ""
-"SPICE support in OpenStack Compute shares a similar architecture to the VNC "
-"implementation. The OpenStack dashboard uses a SPICE-HTML5 widget in its "
-"console tab that communicates to the <systemitem class=\"service\">nova-"
-"spicehtml5proxy</systemitem> service by using SPICE-over-websockets. The "
-"<systemitem class=\"service\">nova-spicehtml5proxy</systemitem> service "
-"communicates directly with the hypervisor process by using SPICE."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-spice.xml19(para)
-msgid ""
-"VNC must be explicitly disabled to get access to the SPICE console. Set the "
-"<option>vnc_enabled</option> option to <literal>False</literal> in the "
-"<literal>[DEFAULT]</literal> section to disable the VNC console."
-msgstr ""
-
-#: ./doc/common/section_compute-configure-spice.xml22(para)
-msgid ""
-"Use the following options to configure SPICE as the console for OpenStack "
-"Compute:"
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure.xml6(title)
-msgid "Configure the dashboard"
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure.xml8(para)
-msgid "You can configure the dashboard for a simple HTTP deployment."
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure.xml14(para)
-msgid "Also, you can configure the size of the VNC window in the dashboard."
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-http.xml6(title)
-msgid "Configure the dashboard for HTTP"
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-http.xml8(para)
-msgid ""
-"You can configure the dashboard for a simple HTTP deployment. The standard "
-"installation uses a non-encrypted HTTP channel."
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-http.xml12(para)
-msgid ""
-"Specify the host for your OpenStack Identity Service endpoint in the "
-"<filename>/etc/openstack-dashboard/local_settings.py</filename> file with "
-"the <literal>OPENSTACK_HOST</literal> setting."
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-http.xml17(para)
-msgid "The following example shows this setting:"
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-http.xml19(para)
-msgid ""
-"The service catalog configuration in the Identity Service determines whether"
-" a service appears in the dashboard. For the full listing, see <link "
-"href=\"http://docs.openstack.org/developer/horizon/topics/settings.html\">Horizon"
-" Settings and Configuration</link>."
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-http.xml28(para)
-msgid "Restart Apache http server. For Ubuntu/Debian/SUSE:"
-msgstr ""
-
-#: ./doc/common/section_dashboard-configure-http.xml30(para)
-msgid "or for Fedora/RHEL/CentOS:"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_dashboard_access.xml89(None)
-msgid ""
-"@@image: 'figures/dashboard-project-tab.png'; "
-"md5=5b192a3d34c9285dbacd875395b8e4cc"
-msgstr "@@image: 'figures/dashboard-project-tab.png'; md5=5b192a3d34c9285dbacd875395b8e4cc"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_dashboard_access.xml214(None)
-msgid ""
-"@@image: 'figures/dashboard-admin-tab.png'; "
-"md5=039358c76c549d7d423da5b8aa826435"
-msgstr "@@image: 'figures/dashboard-admin-tab.png'; md5=039358c76c549d7d423da5b8aa826435"
-
-#: ./doc/common/section_dashboard_access.xml12(title)
-msgid "Log in to the dashboard"
-msgstr "ダッシュボードへのログイン"
-
-#: ./doc/common/section_dashboard_access.xml13(para)
-msgid ""
-"The dashboard is available on the node with the <literal>nova-"
-"dashboard</literal> server role."
-msgstr "ダッシュボードは <literal>nova-dashboard</literal> サーバーロールを持つノードで利用できます。"
-
-#: ./doc/common/section_dashboard_access.xml17(para)
-msgid ""
-"Ask the cloud operator for the host name or public IP address from which you"
-" can access the dashboard, and for your user name and password."
-msgstr "ダッシュボードにアクセスできるホスト名またはパブリック IP アドレス、およびあなたのユーザー名とパスワードをクラウド運用者に問い合わせます。"
-
-#: ./doc/common/section_dashboard_access.xml22(para)
-msgid "Open a web browser that has JavaScript and cookies enabled."
-msgstr "JavaScript とクッキーが有効化された、ウェブブラウザーを開きます。"
-
-#: ./doc/common/section_dashboard_access.xml25(para)
-msgid ""
-"To use the Virtual Network Computing (VNC) client for the dashboard, your "
-"browser must support HTML5 Canvas and HTML5 WebSockets. The VNC client is "
-"based on noVNC. For details, see <link "
-"href=\"https://github.com/kanaka/noVNC/blob/master/README.md\">noVNC: HTML5 "
-"VNC Client</link>. For a list of supported browsers, see <link "
-"href=\"https://github.com/kanaka/noVNC/wiki/Browser-support\">Browser "
-"support</link>."
-msgstr "ダッシュボード用の Virtual Network Computing (VNC) クライアントを使用する場合、お使いのブラウザーが HTML5 Canvas と HTML5 WebSockets をサポートする必要があります。この VNC クライアントは noVNC に基づいています。詳細は <link href=\"https://github.com/kanaka/noVNC/blob/master/README.md\">noVNC: HTML5 VNC Client</link> を参照してください。サポートされるブラウザーの一覧は <link href=\"https://github.com/kanaka/noVNC/wiki/Browser-support\">Browser support</link> を参照してください。"
-
-#: ./doc/common/section_dashboard_access.xml38(para)
-msgid ""
-"In the address bar, enter the host name or IP address for the dashboard."
-msgstr "アドレスバーにダッシュボードのホスト名または IP アドレスを入力します。"
-
-#: ./doc/common/section_dashboard_access.xml40(replaceable)
-msgid "ipAddressOrHostName"
-msgstr "ipAddressOrHostName"
-
-#: ./doc/common/section_dashboard_access.xml42(para)
-msgid ""
-"If a certificate warning appears when you try to access the URL for the "
-"first time, a self-signed certificate is in use, which is not considered "
-"trustworthy by default. Verify the certificate or add an exception in the "
-"browser to bypass the warning."
-msgstr "URL に初めてアクセスしようとしたときに、証明書の警告が表示された場合、自己署名証明書が使用されています。これは標準で信頼性が考慮されていません。警告を回避するために、証明書を検証するか、ブラウザーに例外を追加してください。"
-
-#: ./doc/common/section_dashboard_access.xml51(para)
-msgid ""
-"On the <guilabel>Log In</guilabel> page, enter your user name and password, "
-"and click <guibutton>Sign In</guibutton>."
-msgstr "<guilabel>ログイン</guilabel>ページで、ユーザー名とパスワードを入力し、<guibutton>ログイン</guibutton>をクリックします。"
-
-#: ./doc/common/section_dashboard_access.xml54(para)
-msgid ""
-"The top of the window displays your user name. You can also access "
-"<guilabel>Settings</guilabel> or sign out of the dashboard."
-msgstr "ウィンドウの最上部にユーザー名が表示されます。また、<guilabel>設定</guilabel>ページにアクセスしたり、ダッシュボードをログアウトしたりできます。"
-
-#: ./doc/common/section_dashboard_access.xml61(para)
-msgid ""
-"If you are logged in as an end user, the <link "
-"linkend=\"dashboard_project_tab\">Project</link> tab is displayed."
-msgstr "エンドユーザーとしてログインすると、<link linkend=\"dashboard_project_tab\">プロジェクト</link>タブが表示されます。"
-
-#: ./doc/common/section_dashboard_access.xml65(para)
-msgid ""
-"If you are logged in as an administrator, the <link "
-"linkend=\"dashboard_project_tab\">Project</link> tab and <link "
-"linkend=\"dashboard_admin_tab\">Admin</link> tab are displayed."
-msgstr "管理者としてログインすると、<link linkend=\"dashboard_project_tab\">プロジェクト</link>タブと<link linkend=\"dashboard_admin_tab\">管理</link>タブが表示されます。"
-
-#: ./doc/common/section_dashboard_access.xml57(para)
-msgid ""
-"The visible tabs and functions in the dashboard depend on the access "
-"permissions, or <emphasis role=\"italic\">roles</emphasis>, of the user you "
-"are logged in as.<placeholder-1/>"
-msgstr "ダッシュボードに表示されるタブや機能は、ログインしたユーザーのアクセス権限や<emphasis role=\"italic\">ロール</emphasis>に依存します。<placeholder-1/>"
-
-#: ./doc/common/section_dashboard_access.xml75(title)
-msgid "OpenStack dashboardProject tab"
-msgstr "OpenStack Dashboard プロジェクトタブ"
-
-#: ./doc/common/section_dashboard_access.xml76(para)
-msgid ""
-"Projects are organizational units in the cloud, and are also known as "
-"tenants or accounts. Each user is a member of one or more projects. Within a"
-" project, a user creates and manages instances."
-msgstr "プロジェクトは、クラウドにおける組織単位です。テナントやアカウントとしても知られています。各ユーザーは、1 つ以上のプロジェクトのメンバーです。ユーザーは、プロジェクト内でインスタンスを作成、管理します。"
-
-#: ./doc/common/section_dashboard_access.xml80(para)
-msgid ""
-"From the <guilabel>Project</guilabel> tab, you can view and manage the "
-"resources in a selected project, including instances and images. You select "
-"the project from the <guilabel>CURRENT PROJECT</guilabel> list at the top of"
-" the tab."
-msgstr "<guilabel>プロジェクト</guilabel>タブから、選択したプロジェクトにおける、インスタンスやイメージなどのリソースを表示、管理できます。タブの上部にある<guilabel>現在のプロジェクト</guilabel>リストからプロジェクトを選択します。"
-
-#: ./doc/common/section_dashboard_access.xml85(title)
-msgid "Project tab"
-msgstr "プロジェクトタブ"
-
-#: ./doc/common/section_dashboard_access.xml93(para)
-msgid ""
-"From the <guilabel>Project</guilabel> tab, you can access the following "
-"tabs:"
-msgstr "<guilabel>プロジェクト</guilabel>タブから、以下のタブにアクセスできます。"
-
-#: ./doc/common/section_dashboard_access.xml100(th)
-#: ./doc/common/section_dashboard_access.xml170(th)
-#: ./doc/common/section_dashboard_access.xml185(th)
-#: ./doc/common/section_dashboard_access.xml192(th)
-#: ./doc/common/section_dashboard_access.xml224(th)
-#: ./doc/common/section_dashboard_access.xml350(th)
-msgid "<placeholder-1/> tab"
-msgstr "<placeholder-1/> タブ"
-
-#: ./doc/common/section_dashboard_access.xml105(guilabel)
-#: ./doc/common/section_dashboard_access.xml229(guilabel)
-#: ./doc/common/section_cli_overview.xml7(title)
-msgid "Overview"
-msgstr "概要"
-
-#: ./doc/common/section_dashboard_access.xml106(para)
-msgid "View reports for the project."
-msgstr "プロジェクトのレポートを表示します。"
-
-#: ./doc/common/section_dashboard_access.xml109(guilabel)
-#: ./doc/common/section_dashboard_access.xml292(guilabel)
-msgid "Instances"
-msgstr "インスタンス"
-
-#: ./doc/common/section_dashboard_access.xml110(para)
-msgid ""
-"View, launch, create a snapshot from, stop, pause, or reboot instances, or "
-"connect to them through VNC."
-msgstr "インスタンスの表示、起動、スナップショットの作成をします。インスタンスの停止、一時停止、シャットダウンをします。または、インスタンスに VNC 経由で接続します。"
-
-#: ./doc/common/section_dashboard_access.xml114(guilabel)
-#: ./doc/common/section_dashboard_access.xml119(guilabel)
-#: ./doc/common/section_dashboard_access.xml299(guilabel)
-msgid "Volumes"
-msgstr "ボリューム"
-
-#: ./doc/common/section_dashboard_access.xml115(para)
-#: ./doc/common/section_dashboard_access.xml141(para)
-msgid "Use the following tabs to complete these tasks:"
-msgstr "これらの作業を実行するために、以下のタブを使用します。"
-
-#: ./doc/common/section_dashboard_access.xml121(para)
-msgid "View, create, edit, and delete volumes."
-msgstr "ボリュームを表示、作成、編集、削除します。"
-
-#: ./doc/common/section_dashboard_access.xml125(guilabel)
-msgid "Volume Snapshots"
-msgstr "ボリュームのスナップショット"
-
-#: ./doc/common/section_dashboard_access.xml127(para)
-msgid "View, create, edit, and delete volume snapshots."
-msgstr "ボリュームのスナップショットを表示、作成、編集、削除します。"
-
-#: ./doc/common/section_dashboard_access.xml133(guilabel)
-#: ./doc/common/section_dashboard_access.xml309(guilabel)
-msgid "Images"
-msgstr "イメージ"
-
-#: ./doc/common/section_dashboard_access.xml134(para)
-msgid ""
-"View images and instance snapshots created by project users, plus any images"
-" that are publicly available. Create, edit, and delete images, and launch "
-"instances from images and snapshots."
-msgstr "プロジェクトのユーザーにより作成された、イメージおよびインスタンスのスナップショットを表示します。加えて、すべてのパブリックなイメージを表示します。イメージを作成、編集、削除します。また、イメージやスナップショットからインスタンスを起動します。"
-
-#: ./doc/common/section_dashboard_access.xml140(guilabel)
-msgid "Access &amp; Security"
-msgstr "アクセスとセキュリティ"
-
-#: ./doc/common/section_dashboard_access.xml144(guilabel)
-msgid "Security Groups"
-msgstr "セキュリティグループ"
-
-#: ./doc/common/section_dashboard_access.xml145(para)
-msgid ""
-"View, create, edit, and delete security groups and security group rules."
-msgstr "セキュリティグループおよびセキュリティグループのルールを表示、作成、編集、削除します。"
-
-#: ./doc/common/section_dashboard_access.xml150(guilabel)
-msgid "Key Pairs"
-msgstr "キーペア"
-
-#: ./doc/common/section_dashboard_access.xml151(para)
-msgid "View, create, edit, import, and delete key pairs."
-msgstr "キーペアを表示、作成、編集、インポート、削除します。"
-
-#: ./doc/common/section_dashboard_access.xml156(guilabel)
-msgid "Floating IPs"
-msgstr "Floating IP"
-
-#: ./doc/common/section_dashboard_access.xml158(para)
-msgid "Allocate an IP address to or release it from a project."
-msgstr "プロジェクトに IP アドレスを確保します。または、解放します。"
-
-#: ./doc/common/section_dashboard_access.xml163(guilabel)
-msgid "API Access"
-msgstr "API アクセス"
-
-#: ./doc/common/section_dashboard_access.xml164(para)
-msgid "View API endpoints."
-msgstr "API エンドポイントを表示します。"
-
-#: ./doc/common/section_dashboard_access.xml170(guilabel)
-msgid "Network"
-msgstr "ネットワーク"
-
-#: ./doc/common/section_dashboard_access.xml173(guilabel)
-msgid "Network Topology"
-msgstr "ネットワークトポロジー"
-
-#: ./doc/common/section_dashboard_access.xml174(para)
-msgid "View the network topology."
-msgstr "ネットワークトポロジーを表示します。"
-
-#: ./doc/common/section_dashboard_access.xml177(guilabel)
-#: ./doc/common/section_dashboard_access.xml314(guilabel)
-msgid "Networks"
-msgstr "ネットワーク"
-
-#: ./doc/common/section_dashboard_access.xml178(para)
-msgid "Create and manage public and private networks."
-msgstr "パブリックネットワークおよびプライベートネットワークを作成、管理します。"
-
-#: ./doc/common/section_dashboard_access.xml181(guilabel)
-#: ./doc/common/section_dashboard_access.xml318(guilabel)
-msgid "Routers"
-msgstr "ルーター"
-
-#: ./doc/common/section_dashboard_access.xml182(para)
-msgid "Create and manage subnets."
-msgstr "サブネットを作成、管理します。"
-
-#: ./doc/common/section_dashboard_access.xml185(guilabel)
-msgid "Object Store"
-msgstr "オブジェクトストア"
-
-#: ./doc/common/section_dashboard_access.xml188(guilabel)
-#: ./doc/common/section_dashboard_access.xml195(guilabel)
-msgid "Containers"
-msgstr "コンテナー"
-
-#: ./doc/common/section_dashboard_access.xml189(para)
-msgid "Create and manage containers and objects."
-msgstr "コンテナーとオブジェクトを作成、管理します。"
-
-#: ./doc/common/section_dashboard_access.xml196(para)
-msgid "Use the REST API to orchestrate multiple composite cloud applications."
-msgstr "複数のコンポジットクラウドアプリケーションをオーケストレーションするために REST API を使用します。"
-
-#: ./doc/common/section_dashboard_access.xml203(title)
-msgid "OpenStack dashboardAdmin tab"
-msgstr "OpenStack Dashboard 管理タブ"
-
-#: ./doc/common/section_dashboard_access.xml204(para)
-msgid ""
-"Administrative users can use the <guilabel>Admin</guilabel> tab to view "
-"usage and to manage instances, volumes, flavors, images, projects, users, "
-"services, and quotas."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml209(title)
-msgid "Admin tab"
-msgstr "管理タブ"
-
-#: ./doc/common/section_dashboard_access.xml218(para)
-msgid "Access the following categories to complete these tasks:"
-msgstr "これらの作業を実行するために、以下のカテゴリにアクセスします。"
-
-#: ./doc/common/section_dashboard_access.xml224(guilabel)
-msgid "System Panel"
-msgstr "システムパネル"
-
-#: ./doc/common/section_dashboard_access.xml230(para)
-msgid "View basic reports."
-msgstr "基本的なレポートを表示します。"
-
-#: ./doc/common/section_dashboard_access.xml233(guilabel)
-msgid "Resource Usage"
-msgstr "リソース使用量"
-
-#: ./doc/common/section_dashboard_access.xml234(para)
-msgid "Use the following tabs to view the following usages:"
-msgstr "以下の使用量を表示するために、以下のタブを使用します。"
-
-#: ./doc/common/section_dashboard_access.xml269(guilabel)
-msgid "Daily Report"
-msgstr "日次レポート"
-
-#: ./doc/common/section_dashboard_access.xml271(para)
-msgid "View the daily report."
-msgstr ""
-
-#: ./doc/common/section_dashboard_access.xml275(guilabel)
-msgid "Stats"
-msgstr "統計情報"
-
-#: ./doc/common/section_dashboard_access.xml277(para)
-msgid "View the statistics of all resources."
-msgstr "すべてのリソースの統計情報を表示します。"
-
-#: ./doc/common/section_dashboard_access.xml283(guilabel)
-msgid "Hypervisors"
-msgstr "ハイパーバイザー"
-
-#: ./doc/common/section_dashboard_access.xml284(para)
-msgid "View the hypervisor summary."
-msgstr "ハイパーバイザーの概要を表示します。"
-
-#: ./doc/common/section_dashboard_access.xml287(guilabel)
-msgid "Host Aggregates"
-msgstr "ホストアグリゲート"
-
-#: ./doc/common/section_dashboard_access.xml288(para)
-msgid ""
-"View, create, and edit host aggregates. View the list of availability zones."
-msgstr "ホストアグリゲートを表示、作成、編集します。アベイラビリティゾーンの一覧を表示します。"
-
-#: ./doc/common/section_dashboard_access.xml293(para)
-msgid ""
-"View, pause, resume, suspend, migrate, soft or hard reboot, and delete "
-"running instances that belong to users of some, but not all, projects. Also,"
-" view the log for an instance or access an instance through VNC."
-msgstr "いくつかだが、すべてではないプロジェクトのユーザーが所属する実行中のインスタンスを表示、一時停止、再開、サスペンド、マイグレーション、ソフトリブート、ハードリブート、削除します。また、インスタンスのログを表示します。VNC 経由でインスタンスにアクセスします。"
-
-#: ./doc/common/section_dashboard_access.xml300(para)
-msgid "View, create, edit, and delete volumes and volume types."
-msgstr "ボリュームおよびボリューム形式を表示、作成、編集、削除します。"
-
-#: ./doc/common/section_dashboard_access.xml305(para)
-msgid ""
-"View, create, edit, view extra specifications for, and delete flavors. A "
-"flavor is size of an instance."
-msgstr "フレーバーの追加スペックを表示、作成、編集します。また、フレーバーを削除します。フレーバーはインスタンスの大きさです。"
-
-#: ./doc/common/section_dashboard_access.xml310(para)
-msgid "View, create, edit properties for, and delete custom images."
-msgstr "カスタムイメージのプロパティを表示、作成、編集します。また、カスタムイメージを削除します。"
-
-#: ./doc/common/section_dashboard_access.xml315(para)
-msgid "View, create, edit properties for, and delete networks."
-msgstr "ネットワークのプロパティを表示、作成、編集します。また、ネットワークを削除します。"
-
-#: ./doc/common/section_dashboard_access.xml319(para)
-msgid "View, create, edit properties for, and delete routers."
-msgstr "ルーターのプロパティを表示、作成、編集します。また、ルーターを削除します。"
-
-#: ./doc/common/section_dashboard_access.xml322(guilabel)
-msgid "System Info"
-msgstr "システム情報"
-
-#: ./doc/common/section_dashboard_access.xml323(para)
-msgid "Use the following tabs to view the service information:"
-msgstr "サービスの情報を表示するために以下のタブを使用します。"
-
-#: ./doc/common/section_dashboard_access.xml326(guilabel)
-msgid "Services"
-msgstr "サービス"
-
-#: ./doc/common/section_dashboard_access.xml327(para)
-msgid "View a list of the services."
-msgstr "サービスの一覧を表示します。"
-
-#: ./doc/common/section_dashboard_access.xml331(guilabel)
-msgid "Compute Services"
-msgstr "コンピュートサービス"
-
-#: ./doc/common/section_dashboard_access.xml332(para)
-msgid "View a list of all Compute services."
-msgstr "すべてのコンピュートサービスの一覧を表示します。"
-
-#: ./doc/common/section_dashboard_access.xml336(guilabel)
-msgid "Network Agents"
-msgstr "ネットワークエージェント"
-
-#: ./doc/common/section_dashboard_access.xml337(para)
-msgid "View the network agents."
-msgstr "ネットワークエージェントを表示します。"
-
-#: ./doc/common/section_dashboard_access.xml341(guilabel)
-msgid "Default Quotas"
-msgstr "標準のクォータ"
-
-#: ./doc/common/section_dashboard_access.xml342(para)
-msgid ""
-"View default quota values. Quotas are hard-coded in OpenStack Compute and "
-"define the maximum allowable size and number of resources."
-msgstr "規定のクォータ値を表示します。クォータは OpenStack Compute にハードコードされています。利用可能な最大値と最大リソース数を定義します。"
-
-#: ./doc/common/section_dashboard_access.xml350(guilabel)
-msgid "Identity Panel"
-msgstr "認証パネル"
-
-#: ./doc/common/section_dashboard_access.xml358(guilabel)
-msgid "Projects"
-msgstr "プロジェクト"
-
-#: ./doc/common/section_dashboard_access.xml359(para)
-msgid "View, create, assign users to, remove users from, and delete projects."
-msgstr "プロジェクトを表示、作成、削除します。またはプロジェクトのユーザーを追加、削除します。"
-
-#: ./doc/common/section_dashboard_access.xml363(guilabel)
-msgid "Users"
-msgstr "ユーザー"
-
-#: ./doc/common/section_dashboard_access.xml364(para)
-msgid "View, create, enable, disable, and delete users."
-msgstr "ユーザーを表示、作成、有効化、無効化、削除します。"
-
-#: ./doc/common/ch_using_openstack_overview.xml7(title)
-msgid ""
-"How can I <phrase audience=\"enduser\">use</phrase><phrase "
-"audience=\"adminuser\">administer</phrase> an OpenStack cloud?"
-msgstr "どのように OpenStack クラウドを<phrase audience=\"enduser\">利用</phrase><phrase audience=\"adminuser\">管理</phrase>できますか?"
-
-#: ./doc/common/ch_using_openstack_overview.xml11(para)
-msgid ""
-"As an OpenStack cloud end user, you can provision your own resources within "
-"the limits set by administrators."
-msgstr "OpenStack クラウドのエンドユーザーとして、管理者により設定された制限の範囲内で自身のリソースを配備できます。"
-
-#: ./doc/common/ch_using_openstack_overview.xml14(para)
-msgid ""
-"As an OpenStack cloud administrative user, you can manage tenants, known as "
-"<glossterm baseform=\"project\">projects</glossterm>, users, services, "
-"images, flavors, and quotas."
-msgstr "OpenStack クラウドの管理ユーザーとして、<glossterm baseform=\"project\">プロジェクト</glossterm>として知られているテナント、ユーザー、サービス、イメージ、フレーバー、クォータを管理できます。"
-
-#: ./doc/common/ch_using_openstack_overview.xml18(para)
-msgid ""
-"The examples in this guide show you how to perform tasks by using the "
-"following methods:"
-msgstr "このガイドの例は、以下の方法により、作業を実行する方法を示します。"
-
-#: ./doc/common/ch_using_openstack_overview.xml22(para)
-msgid ""
-"OpenStack dashboard. Use this web-based graphical interface, code named "
-"<link href=\"https://github.com/openstack/horizon/\">horizon</link>, to "
-"view, create, and manage resources<phrase audience=\"adminuser\"> and "
-"services</phrase>."
-msgstr "OpenStack Dashboard。リソース<phrase audience=\"adminuser\"> およびサービス</phrase>を表示、作成、管理するために、このウェブのグラフィカルインターフェース (コード名 <link href=\"https://github.com/openstack/horizon/\">Horizon</link>) を使用します。"
-
-#: ./doc/common/ch_using_openstack_overview.xml30(para)
-msgid ""
-"OpenStack command-line clients. Each core OpenStack project has a command-"
-"line client that you can use to run simple commands to view, create, and "
-"manage resources<phrase audience=\"adminuser\"> and services</phrase> in a "
-"cloud and automate tasks by using scripts."
-msgstr "OpenStack コマンドラインクライアント。各 OpenStack コアプロジェクトは、クラウドでリソース<phrase audience=\"adminuser\"> およびサービス</phrase>を表示、作成、管理するために、シンプルなコマンドを実行するために使用でき、スクリプトを使用して作業を自動化できるコマンドラインクライアントを持ちます。"
-
-#: ./doc/common/ch_using_openstack_overview.xml38(para)
-msgid "You can modify these examples for your specific use cases."
-msgstr "お使いの具体的なユースケースのために、これらの例を変更できます。"
-
-#: ./doc/common/ch_using_openstack_overview.xml40(para)
-msgid ""
-"In addition to these ways of interacting with a cloud, you can access the "
-"OpenStack APIs directly or indirectly through <link "
-"href=\"http://curl.haxx.se/\">cURL</link> commands or open SDKs. You can "
-"automate access or build tools to manage resources and services by using the"
-" native OpenStack APIs or the EC2 compatibility API."
-msgstr "クラウドと相互に作用するこれらの方法に加えて、<link href=\"http://curl.haxx.se/\">cURL</link> コマンドまたはオープン SDK 経由で直接的または間接的に OpenStack API にアクセスできます。ネイティブの OpenStack API や EC2 互換 API を使用することにより、リソースやサービスを管理するために、アクセスを自動化したり、ツールを作成したりできます。"
-
-#: ./doc/common/ch_using_openstack_overview.xml46(para)
-msgid ""
-"To use the OpenStack APIs, it helps to be familiar with HTTP/1.1, RESTful "
-"web services, the OpenStack services, and JSON or XML data serialization "
-"formats."
-msgstr "OpenStack API を使用するために、HTTP/1.1、RESTful ウェブサービス、OpenStack サービス、および JSON や XML データシリアライズ形式に慣れることは役に立ちます。"
-
-#: ./doc/common/section_xapi-ami-setup.xml7(title)
-msgid "Prepare for AMI type images"
-msgstr ""
-
-#: ./doc/common/section_xapi-ami-setup.xml8(para)
-msgid ""
-"To support AMI type images in your OpenStack installation, you must create a"
-" <filename>/boot/guest</filename> directory inside Dom0. The OpenStack VM "
-"extracts the kernel and ramdisk from the AKI and ARI images puts them in "
-"this location."
-msgstr ""
-
-#: ./doc/common/section_xapi-ami-setup.xml12(para)
-msgid ""
-"OpenStack maintains the contents of this directory and its size should not "
-"increase during normal operation. However, in case of power failures or "
-"accidental shutdowns, some files might be left over. To prevent these files "
-"from filling the Dom0 disk, set up this directory as a symlink that points "
-"to a subdirectory of the local SR."
-msgstr ""
-
-#: ./doc/common/section_xapi-ami-setup.xml18(para)
-msgid "Run these commands in Dom0 to achieve this setup:"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml8(title)
-msgid "Configuration file format"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml10(para)
-msgid ""
-"OpenStack uses the <glossterm>INI</glossterm> file format for configuration "
-"files. An INI file is a simple text file that specifies options as "
-"<literal>key=value</literal> pairs, grouped into sections. The "
-"<literal>DEFAULT</literal> section contains most of the configuration "
-"options. Lines starting with a hash sign (<literal>#</literal>) are comment "
-"lines. For example:"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml29(replaceable)
-msgid "KEYSTONE_DBPASS"
-msgstr "KEYSTONE_DBPASS"
-
-#: ./doc/common/section_config_format.xml29(replaceable)
-msgid "controller"
-msgstr "controller"
-
-#: ./doc/common/section_config_format.xml32(para)
-msgid ""
-"Options can have different type for values. The comments in the sample "
-"config files always mention these. The following types are used by "
-"OpenStack:"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml39(term)
-msgid "boolean value"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml41(para)
-msgid ""
-"Enables or disables an option. The allowed values are "
-"<literal>true</literal> and <literal>false</literal>."
-msgstr ""
-
-#: ./doc/common/section_config_format.xml51(term)
-msgid "floating point value"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml53(para)
-msgid ""
-"A floating point number like <literal>0.25</literal> or "
-"<literal>1000</literal>."
-msgstr ""
-
-#: ./doc/common/section_config_format.xml62(term)
-msgid "integer value"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml64(para)
-msgid ""
-"An integer number is a number without fractional components, like "
-"<literal>0</literal> or <literal>42</literal>."
-msgstr ""
-
-#: ./doc/common/section_config_format.xml74(term)
-msgid "list value"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml76(para)
-msgid ""
-"Represents values of other types, separated by commas. As an example, the "
-"following sets <option>allowed_rpc_exception_modules</option> to a list "
-"containing the four elements <literal>oslo.messaging.exceptions</literal>, "
-"<literal>nova.exception</literal>, <literal>cinder.exception</literal>, and "
-"<literal>exceptions</literal>:"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml92(term)
-msgid "multi valued"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml94(para)
-msgid ""
-"A multi-valued option is a string value and can be given more than once, all"
-" values will be used."
-msgstr ""
-
-#: ./doc/common/section_config_format.xml105(term)
-msgid "string value"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml107(para)
-msgid "Strings can be optionally enclosed with single or double quotes."
-msgstr ""
-
-#: ./doc/common/section_config_format.xml127(title)
-msgid "Sections"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml134(literal)
-#: ./doc/common/tables/keystone-debug.xml19(th)
-#: ./doc/common/tables/glance-policy.xml19(th)
-#: ./doc/common/tables/nova-ipv6.xml19(th)
-#: ./doc/common/tables/cinder-eqlx.xml19(th)
-#: ./doc/common/tables/nova-rpc_all.xml19(th)
-#: ./doc/common/tables/glance-qpid.xml19(th)
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml7(literal)
-#: ./doc/common/tables/nova-volumes.xml19(th)
-#: ./doc/common/tables/glance-gridfs.xml19(th)
-#: ./doc/common/tables/glance-filesystem.xml19(th)
-#: ./doc/common/tables/heat-redis.xml19(th)
-#: ./doc/common/tables/trove-logging.xml19(th)
-#: ./doc/common/tables/cinder-storage_gpfs.xml19(th)
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml19(th)
-#: ./doc/common/tables/nova-ca.xml19(th)
-#: ./doc/common/tables/cinder-huawei.xml19(th)
-#: ./doc/common/tables/keystone-qpid.xml19(th)
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml19(th)
-#: ./doc/common/tables/nova-glance.xml19(th)
-#: ./doc/common/tables/neutron-dhcp_agent.xml19(th)
-#: ./doc/common/tables/nova-neutron.xml19(th)
-#: ./doc/common/tables/cinder-backups_ceph.xml19(th)
-#: ./doc/common/tables/nova-metadata.xml19(th)
-#: ./doc/common/tables/glance-s3.xml19(th)
-#: ./doc/common/tables/glance-auth_token.xml19(th)
-#: ./doc/common/tables/neutron-kombu.xml19(th)
-#: ./doc/common/tables/trove-qpid.xml19(th)
-#: ./doc/common/tables/trove-compute.xml19(th)
-#: ./doc/common/tables/trove-nova.xml19(th)
-#: ./doc/common/tables/cinder-block-device.xml19(th)
-#: ./doc/common/tables/cinder-zones.xml19(th)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml19(th)
-#: ./doc/common/tables/neutron-common.xml19(th)
-#: ./doc/common/tables/neutron-compute.xml19(th)
-#: ./doc/common/tables/heat-rpc.xml19(th)
-#: ./doc/common/tables/neutron-openvswitch_agent.xml19(th)
-#: ./doc/common/tables/cinder-compute.xml19(th)
-#: ./doc/common/tables/cinder-lvm.xml19(th)
-#: ./doc/common/tables/cinder-storage_nfs.xml19(th)
-#: ./doc/common/tables/heat-cfn_api.xml19(th)
-#: ./doc/common/tables/nova-hypervisor.xml19(th)
-#: ./doc/common/tables/trove-rabbitmq.xml19(th)
-#: ./doc/common/tables/trove-api.xml19(th)
-#: ./doc/common/tables/cinder-quota.xml19(th)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml7(literal)
-#: ./doc/common/tables/nova-console.xml19(th)
-#: ./doc/common/tables/heat-clients.xml19(th)
-#: ./doc/common/tables/heat-notification.xml19(th)
-#: ./doc/common/tables/nova-common.xml19(th)
-#: ./doc/common/tables/glance-zmq.xml19(th)
-#: ./doc/common/tables/neutron-metering_agent.xml19(th)
-#: ./doc/common/tables/trove-taskmanager.xml19(th)
-#: ./doc/common/tables/keystone-zeromq.xml19(th)
-#: ./doc/common/tables/neutron-api.xml19(th)
-#: ./doc/common/tables/ceilometer-redis.xml19(th)
-#: ./doc/common/tables/ceilometer-swift.xml19(th)
-#: ./doc/common/tables/cinder-hplefthand.xml19(th)
-#: ./doc/common/tables/heat-qpid.xml19(th)
-#: ./doc/common/tables/nova-testing.xml19(th)
-#: ./doc/common/tables/cinder-backups.xml19(th)
-#: ./doc/common/tables/neutron-ml2_ofa.xml19(th)
-#: ./doc/common/tables/trove-debug.xml19(th)
-#: ./doc/common/tables/nova-s3.xml19(th)
-#: ./doc/common/tables/cinder-rpc.xml19(th)
-#: ./doc/common/tables/cinder-api.xml19(th)
-#: ./doc/common/tables/cinder-windows.xml19(th)
-#: ./doc/common/tables/glance-vmware.xml19(th)
-#: ./doc/common/tables/trove-backup.xml19(th)
-#: ./doc/common/tables/cinder-san.xml19(th)
-#: ./doc/common/tables/keystone-rpc.xml19(th)
-#: ./doc/common/tables/nova-db.xml19(th)
-#: ./doc/common/tables/glance-logging.xml19(th)
-#: ./doc/common/tables/cinder-zoning.xml19(th)
-#: ./doc/common/tables/glance-wsgi.xml19(th)
-#: ./doc/common/tables/nova-periodic.xml19(th)
-#: ./doc/common/tables/cinder-images.xml19(th)
-#: ./doc/common/tables/trove-swift.xml19(th)
-#: ./doc/common/tables/cinder-auth_token.xml19(th)
-#: ./doc/common/tables/heat-crypt.xml19(th)
-#: ./doc/common/tables/neutron-wsgi.xml19(th)
-#: ./doc/common/tables/neutron-scheduler.xml19(th)
-#: ./doc/common/tables/keystone-security.xml19(th)
-#: ./doc/common/tables/glance-rbd.xml19(th)
-#: ./doc/common/tables/heat-rabbitmq.xml19(th)
-#: ./doc/common/tables/ceilometer-logging.xml19(th)
-#: ./doc/common/tables/neutron-metadata.xml19(th)
-#: ./doc/common/tables/glance-redis.xml19(th)
-#: ./doc/common/tables/cinder-hp3par.xml19(th)
-#: ./doc/common/tables/cinder-storage_ceph.xml19(th)
-#: ./doc/common/tables/nova-livemigration.xml19(th)
-#: ./doc/common/tables/nova-ldap.xml19(th)
-#: ./doc/common/tables/nova-fping.xml19(th)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml19(th)
-#: ./doc/common/tables/nova-ec2.xml19(th)
-#: ./doc/common/tables/trove-zeromq.xml19(th)
-#: ./doc/common/tables/heat-database.xml19(th)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml7(literal)
-#: ./doc/common/tables/cinder-rootwrap.xml19(th)
-#: ./doc/common/tables/ceilometer-database.xml19(th)
-#: ./doc/common/tables/heat-debug.xml19(th)
-#: ./doc/common/tables/cinder-nexenta_nfs.xml19(th)
-#: ./doc/common/tables/trove-auth_token.xml19(th)
-#: ./doc/common/tables/heat-waitcondition_api.xml19(th)
-#: ./doc/common/tables/nova-policy.xml19(th)
-#: ./doc/common/tables/keystone-amqp.xml19(th)
-#: ./doc/common/tables/neutron-logging.xml19(th)
-#: ./doc/common/tables/glance-rpc.xml19(th)
-#: ./doc/common/tables/nova-authentication.xml19(th)
-#: ./doc/common/tables/cinder-vmware.xml19(th)
-#: ./doc/common/tables/glance-sheepdog.xml19(th)
-#: ./doc/common/tables/heat-logging.xml19(th)
-#: ./doc/common/tables/keystone-notification.xml19(th)
-#: ./doc/common/tables/neutron-qpid.xml19(th)
-#: ./doc/common/tables/glance-swift.xml19(th)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml7(literal)
-#: ./doc/common/tables/nova-libvirt.xml19(th)
-#: ./doc/common/tables/neutron-lbaas.xml19(th)
-#: ./doc/common/tables/cinder-backups_swift.xml19(th)
-#: ./doc/common/tables/ceilometer-rpc.xml19(th)
-#: ./doc/common/tables/heat-loadbalancer.xml19(th)
-#: ./doc/common/tables/heat-cloudwatch_api.xml19(th)
-#: ./doc/common/tables/nova-pci.xml19(th)
-#: ./doc/common/tables/glance-imagecache.xml19(th)
-#: ./doc/common/tables/trove-quota.xml19(th)
-#: ./doc/common/tables/cinder-storage.xml19(th)
-#: ./doc/common/tables/cinder-nas.xml19(th)
-#: ./doc/common/tables/nova-vpn.xml19(th)
-#: ./doc/common/tables/nova-wsgi.xml19(th)
-#: ./doc/common/tables/cinder-storage_glusterfs.xml19(th)
-#: ./doc/common/tables/nova-availabilityzones.xml19(th)
-#: ./doc/common/tables/heat-zeromq.xml19(th)
-#: ./doc/common/tables/nova-vnc.xml19(th)
-#: ./doc/common/tables/keystone-logging.xml19(th)
-#: ./doc/common/tables/neutron-l3_agent.xml19(th)
-#: ./doc/common/tables/cinder-coraid.xml19(th)
-#: ./doc/common/tables/nova-logging.xml19(th)
-#: ./doc/common/tables/nova-xen.xml19(th)
-#: ./doc/common/tables/ceilometer-collector.xml19(th)
-#: ./doc/common/tables/keystone-ec2.xml19(th)
-#: ./doc/common/tables/ceilometer-api.xml19(th)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml19(th)
-#: ./doc/common/tables/glance-common.xml19(th)
-#: ./doc/common/tables/nova-network.xml19(th)
-#: ./doc/common/tables/cinder-scality.xml19(th)
-#: ./doc/common/tables/neutron-notifier.xml19(th)
-#: ./doc/common/tables/cinder-common.xml19(th)
-#: ./doc/common/tables/nova-configdrive.xml19(th)
-#: ./doc/common/tables/cinder-database.xml19(th)
-#: ./doc/common/tables/neutron-rpc.xml19(th)
-#: ./doc/common/tables/trove-volume.xml19(th)
-#: ./doc/common/tables/nova-zeromq.xml19(th)
-#: ./doc/common/tables/glance-testing.xml19(th)
-#: ./doc/common/tables/glance-registry.xml19(th)
-#: ./doc/common/tables/glance-amqp.xml19(th)
-#: ./doc/common/tables/trove-database.xml19(th)
-#: ./doc/common/tables/heat-clients_backends.xml19(th)
-#: ./doc/common/tables/heat-amqp.xml19(th)
-#: ./doc/common/tables/cinder-hpmsa.xml19(th)
-#: ./doc/common/tables/cinder-emc.xml19(th)
-#: ./doc/common/tables/glance-rabbitmq.xml19(th)
-#: ./doc/common/tables/cinder-backups_tsm.xml19(th)
-#: ./doc/common/tables/nova-qpid.xml19(th)
-#: ./doc/common/tables/trove-rpc.xml19(th)
-#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml7(literal)
-#: ./doc/common/tables/ceilometer-qpid.xml19(th)
-#: ./doc/common/tables/neutron-zeromq.xml19(th)
-#: ./doc/common/tables/neutron-agent.xml19(th)
-#: ./doc/common/tables/neutron-policy.xml19(th)
-#: ./doc/common/tables/neutron-rootwrap.xml19(th)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml7(literal)
-#: ./doc/common/tables/trove-common.xml19(th)
-#: ./doc/common/tables/heat-api.xml19(th)
-#: ./doc/common/tables/ceilometer-amqp.xml19(th)
-#: ./doc/common/tables/keystone-auth_token.xml19(th)
-#: ./doc/common/tables/neutron-redis.xml19(th)
-#: ./doc/common/tables/neutron-ssl.xml19(th)
-#: ./doc/common/tables/ceilometer-exchange.xml19(th)
-#: ./doc/common/tables/ceilometer-common.xml19(th)
-#: ./doc/common/tables/keystone-misc.xml19(th)
-#: ./doc/common/tables/nova-scheduling.xml19(th)
-#: ./doc/common/tables/ceilometer-auth.xml19(th)
-#: ./doc/common/tables/trove-dns.xml19(th)
-#: ./doc/common/tables/neutron-db.xml19(th)
-#: ./doc/common/tables/keystone-redis.xml19(th)
-#: ./doc/common/tables/heat-auth_token.xml19(th)
-#: ./doc/common/tables/cinder-xiv.xml19(th)
-#: ./doc/common/tables/cinder-hds-hus.xml19(th)
-#: ./doc/common/tables/neutron-rabbitmq.xml19(th)
-#: ./doc/common/tables/keystone-policy.xml19(th)
-#: ./doc/common/tables/cinder-auth.xml19(th)
-#: ./doc/common/tables/nova-kombu.xml19(th)
-#: ./doc/common/tables/heat-quota.xml19(th)
-#: ./doc/common/tables/neutron-auth_token.xml19(th)
-#: ./doc/common/tables/cinder-storwize.xml19(th)
-#: ./doc/common/tables/nova-rootwrap.xml19(th)
-#: ./doc/common/tables/cinder-solidfire.xml19(th)
-#: ./doc/common/tables/glance-ssl.xml19(th)
-#: ./doc/common/tables/heat-metadata_api.xml19(th)
-#: ./doc/common/tables/neutron-vmware.xml19(th)
-#: ./doc/common/tables/nova-api.xml19(th)
-#: ./doc/common/tables/glance-matchmaker.xml19(th)
-#: ./doc/common/tables/cinder-san-solaris.xml19(th)
-#: ./doc/common/tables/trove-heat.xml19(th)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml19(th)
-#: ./doc/common/tables/neutron-quotas.xml19(th)
-#: ./doc/common/tables/nova-rpc.xml19(th)
-#: ./doc/common/tables/trove-guestagent.xml19(th)
-#: ./doc/common/tables/keystone-rabbit.xml19(th)
-#: ./doc/common/tables/glance-api.xml19(th)
-#: ./doc/common/tables/cinder-scheduler.xml19(th)
-#: ./doc/common/tables/keystone-api.xml19(th)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml19(th)
-#: ./doc/common/tables/neutron-testing.xml19(th)
-#: ./doc/common/tables/glance-cinder.xml19(th)
-#: ./doc/common/tables/nova-redis.xml19(th)
-#: ./doc/common/tables/ceilometer-inspector.xml19(th)
-#: ./doc/common/tables/nova-rabbitmq.xml19(th)
-#: ./doc/common/tables/heat-common.xml19(th)
-#: ./doc/common/tables/cinder-zadara.xml19(th)
-#: ./doc/common/tables/nova-quota.xml19(th)
-#: ./doc/common/tables/nova-conductor.xml19(th)
-#: ./doc/common/tables/nova-compute.xml19(th)
-#: ./doc/common/tables/cinder-storage_xen.xml19(th)
-#: ./doc/common/tables/trove-amqp.xml19(th)
-#: ./doc/common/tables/nova-xvpnvncproxy.xml19(th)
-msgid "[DEFAULT]"
-msgstr "[DEFAULT]"
-
-#: ./doc/common/section_config_format.xml136(para)
-msgid ""
-"Contains most configuration options. If the documentation for a "
-"configuration option does not specify its section, assume that it appears in"
-" this section."
-msgstr ""
-
-#: ./doc/common/section_config_format.xml145(literal)
-#: ./doc/common/tables/nova-db.xml33(th)
-#: ./doc/common/tables/heat-database.xml34(th)
-#: ./doc/common/tables/ceilometer-database.xml38(th)
-#: ./doc/common/tables/cinder-storage.xml134(th)
-#: ./doc/common/tables/cinder-common.xml226(th)
-#: ./doc/common/tables/cinder-connection.xml19(th)
-#: ./doc/common/tables/neutron-db.xml30(th)
-#: ./doc/common/tables/keystone-database.xml19(th)
-#: ./doc/common/tables/glance-db.xml19(th)
-msgid "[database]"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml147(para)
-msgid ""
-"Configuration options for the database that stores the state of the "
-"OpenStack service."
-msgstr ""
-
-#: ./doc/common/section_config_format.xml128(para)
-msgid ""
-"Configuration options are grouped by section. Most configuration file "
-"supports at least the following sections: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml158(title)
-msgid "Substitution"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml160(para)
-msgid ""
-"The configuration file supports variable substitution. After you set a "
-"configuration option, it can be referenced in later configuration values "
-"when you precede it with a <literal>$</literal>, like "
-"<literal>$OPTION</literal>."
-msgstr ""
-
-#: ./doc/common/section_config_format.xml167(para)
-msgid ""
-"The following example uses the values of <literal>rabbit_host</literal> and "
-"<literal>rabbit_port</literal> to define the value of the "
-"<literal>rabbit_hosts</literal> option, in this case as "
-"<literal>controller:5672</literal>."
-msgstr ""
-
-#: ./doc/common/section_config_format.xml185(para)
-msgid ""
-"To avoid substitution, use <literal>$$</literal>, it is replaced by a single"
-" <literal>$</literal>. For example, if your LDAP DNS password is "
-"<literal>$xkj432</literal>, specify it, as follows: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml191(para)
-msgid ""
-"The code uses the Python "
-"<literal>string.Template.safe_substitute()</literal> method to implement "
-"variable substitution. For more details on how variable substitution is "
-"resolved, see <link href=\"http://docs.python.org/2/library/string.html"
-"#template-strings\">http://docs.python.org/2/library/string.html#template-"
-"strings</link> and <link "
-"href=\"http://www.python.org/dev/peps/pep-0292/\">PEP 292</link>."
-msgstr ""
-
-#: ./doc/common/section_config_format.xml204(title)
-msgid "Whitespace"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml205(para)
-msgid ""
-"To include whitespace in a configuration value, use a quoted string. For "
-"example:"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml211(title)
-msgid "Define an alternate location for a config file"
-msgstr ""
-
-#: ./doc/common/section_config_format.xml212(para)
-msgid ""
-"Most services and the and the <placeholder-1/> command-line clients load the"
-" configuration file. To define an alternate location for the configuration "
-"file, pass the <parameter>--config-file "
-"<replaceable>CONFIG_FILE</replaceable></parameter> parameter when you start "
-"a service or call a <placeholder-2/> command."
-msgstr ""
-
-#: ./doc/common/section_about-object-storage.xml8(para)
-msgid ""
-"Object Storage is a robust, highly scalable and fault tolerant storage "
-"platform for unstructured data such as objects. Objects are stored bits, "
-"accessed through a RESTful, HTTP-based interface. You cannot access data at "
-"the block or file level. Object Storage is commonly used to archive and back"
-" up data, with use cases in virtual machine image, photo, video and music "
-"storage."
-msgstr ""
-
-#: ./doc/common/section_about-object-storage.xml15(para)
-msgid ""
-"Object Storage provides a high degree of availability, throughput, and "
-"performance with its scale out architecture. Each object is replicated "
-"across multiple servers, residing within the same data center or across data"
-" centers, which mitigates the risk of network and hardware failure. In the "
-"event of hardware failure, Object Storage will automatically copy objects to"
-" a new location to ensure that there are always three copies available. "
-"Object Storage is an eventually consistent distributed storage platform; it "
-"sacrifices consistency for maximum availability and partition tolerance. "
-"Object Storage enables you to create a reliable platform by using commodity "
-"hardware and inexpensive storage."
-msgstr ""
-
-#: ./doc/common/section_about-object-storage.xml27(para)
-msgid ""
-"For more information, review the key concepts in the developer documentation"
-" at <link "
-"href=\"http://docs.openstack.org/developer/swift/\">docs.openstack.org/developer/swift/</link>."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-assignments.xml6(title)
-msgid "Separate role authorization and user authentication"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-assignments.xml7(para)
-msgid ""
-"When you configure the Identity service to use an LDAP back end, you can "
-"split authentication and authorization using the "
-"<emphasis>Assignments</emphasis> feature."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-assignments.xml10(para)
-msgid ""
-"The Assignments feature enables administrators to manage project role "
-"authorization using the Identity service's own SQL database, while still "
-"providing user authentication through the LDAP directory."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-assignments.xml14(para)
-msgid "To configure this:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-assignments.xml16(title)
-msgid ""
-"Separating role authorization and user authentication through Assignments"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-assignments.xml19(para)
-msgid ""
-"Configure the Identity service to authenticate users through the LDAP "
-"driver. To do so, first find the <literal>[identity]</literal> section in "
-"the <filename>/etc/keystone/keystone.conf</filename> configuration file. "
-"Then, set the <literal>driver</literal> configuration key in that section to"
-" <literal>keystone.identity.backends.ldap.Identity</literal>:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-assignments.xml30(para)
-msgid ""
-"Next, enable the Assignment driver. To do so, find the "
-"<literal>[assignment]</literal> section in the "
-"<filename>/etc/keystone/keystone.conf</filename> configuration file. Then, "
-"set the <literal>driver</literal> configuration key in that section to "
-"<literal>keystone.assignment.backends.sql.Assignment</literal>:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap-assignments.xml41(para)
-msgid ""
-"On distributions that include <application>openstack-config</application>, "
-"you can configure both drivers by running the following commands instead:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml11(title)
-msgid "Manage volumes"
-msgstr "ボリュームの管理"
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml12(para)
-msgid ""
-"A volume is a detachable block storage device, similar to a USB hard drive. "
-"You can attach a volume to only one instance. To create and manage volumes, "
-"you use a combination of <placeholder-1/> and <placeholder-2/> client "
-"commands."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml16(title)
-msgid "Migrate a volume"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml17(para)
-msgid ""
-"As an administrator, you can migrate a volume with its data from one "
-"location to another in a manner that is transparent to users and workloads. "
-"You can migrate only detached volumes with no snapshots."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml21(para)
-msgid "Possible use cases for data migration include:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml24(para)
-msgid ""
-"Bring down a physical storage device for maintenance without disrupting "
-"workloads."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml28(para)
-msgid "Modify the properties of a volume."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml31(para)
-msgid "Free up space in a thinly-provisioned back end."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml35(para)
-msgid ""
-"Migrate a volume with the <placeholder-1/> command, as shown in the "
-"following example:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml36(replaceable)
-#: ./doc/common/section_cli_cinder_manage_volumes.xml274(replaceable)
-msgid "volumeID"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml36(replaceable)
-msgid "destinationHost"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml36(replaceable)
-msgid "True|False"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml37(para)
-msgid ""
-"In this example, <literal>--force-host-copy=True</literal> forces the "
-"generic host-based migration mechanism and bypasses any driver "
-"optimizations."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml40(para)
-msgid ""
-"If the volume is in use or has snapshots, the specified host destination "
-"cannot accept the volume. If the user is not an administrator, the migration"
-" fails."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml45(title)
-msgid "Create a volume"
-msgstr "ボリュームの作成"
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml46(para)
-msgid "This example creates a my-new-volume volume based on an image."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml49(para)
-msgid ""
-"List images, and note the ID of the image that you want to use for your "
-"volume:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml62(para)
-msgid ""
-"List the availability zones, and note the ID of the availability zone in "
-"which you want to create your volume:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml81(para)
-msgid ""
-"Create a volume with 8GB of space, and specify the availability zone and "
-"image:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml103(para)
-msgid ""
-"To verify that your volume was created successfully, list the available "
-"volumes:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml112(para)
-msgid ""
-"If your volume was created successfully, its status is "
-"<literal>available</literal>. If its status is <literal>error</literal>, you"
-" might have exceeded your quota."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml120(title)
-msgid "Attach a volume to an instance"
-msgstr "ボリュームのインスタンスへの接続"
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml123(para)
-msgid ""
-"Attach your volume to a server, specifying the server ID and the volume ID:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml133(para)
-msgid "Note the ID of your volume."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml136(para)
-msgid "Show information for your volume:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml138(para)
-msgid ""
-"The output shows that the volume is attached to the server with ID <literal"
-">84c6e57d-a6b1-44b6-81eb-fcb36afd31b5</literal>, is in the nova availability"
-" zone, and is bootable."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml165(title)
-msgid "Resize a volume"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml168(para)
-msgid "To resize your volume, you must first detach it from the server."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml170(para)
-msgid ""
-"To detach the volume from your server, pass the server ID and volume ID to "
-"the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml172(para)
-#: ./doc/common/section_cli_cinder_manage_volumes.xml191(para)
-msgid "The <placeholder-1/> command does not return any output."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml184(para)
-msgid "Note that the volume is now available."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml187(para)
-msgid ""
-"Resize the volume by passing the volume ID and the new size (a value greater"
-" than the old one) as parameters:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml197(title)
-msgid "Delete a volume"
-msgstr "ボリュームの削除"
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml200(para)
-msgid "To delete your volume, you must first detach it from the server."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml202(para)
-msgid ""
-"To detach the volume from your server and check for the list of existing "
-"volumes, see steps 1 and 2 in <xref linkend=\"cli_extend_volumes\"/>."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml206(para)
-msgid "Delete the volume using either the volume name or ID:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml208(para)
-msgid "The delete command does not return any output."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml212(para)
-msgid ""
-"List the volumes again, and note that the status of your volume is "
-"<literal>deleting</literal>:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml222(para)
-msgid ""
-"When the volume is fully deleted, it disappears from the list of volumes:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml234(title)
-msgid "Transfer a volume"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml235(para)
-msgid ""
-"You can transfer a volume from one owner to another by using the "
-"<placeholder-1/> commands. The volume donor, or original owner, creates a "
-"transfer request and sends the created transfer ID and authorization key to "
-"the volume recipient. The volume recipient, or new owner, accepts the "
-"transfer by using the ID and key."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml243(para)
-msgid ""
-"The procedure for volume transfer is intended for tenants (both the volume "
-"donor and recipient) within the same cloud."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml245(para)
-msgid "Use cases include:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml248(para)
-msgid ""
-"Create a custom bootable volume or a volume with a large data set and "
-"transfer it to a customer."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml251(para)
-msgid ""
-"For bulk import of data to the cloud, the data ingress system creates a new "
-"Block Storage volume, copies data from the physical device, and transfers "
-"device ownership to the end user."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml258(title)
-msgid "Create a volume transfer request"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml261(para)
-msgid "While logged in as the volume donor, list the available volumes:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml271(para)
-msgid ""
-"As the volume donor, request a volume transfer authorization code for a "
-"specific volume:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml275(para)
-msgid ""
-"The volume must be in an <literal>available</literal> state or the request "
-"will be denied. If the transfer request is valid in the database (that is, "
-"it has not expired or been deleted), the volume is placed in an "
-"<literal>awaiting transfer</literal> state. For example:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml279(para)
-msgid ""
-"The output shows the volume transfer ID in the <literal>id</literal> row and"
-" the authorization key."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml291(para)
-msgid ""
-"Optionally, you can specify a name for the transfer by using the <code"
-">--display-name <replaceable>displayName</replaceable></code> parameter."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml299(para)
-msgid ""
-"Send the volume transfer ID and authorization key to the new owner (for "
-"example, by email)."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml304(para)
-msgid "View pending transfers:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml313(para)
-msgid ""
-"After the volume recipient, or new owner, accepts the transfer, you can see "
-"that the transfer is no longer available:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml325(title)
-msgid "Accept a volume transfer request"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml328(para)
-msgid ""
-"As the volume recipient, you must first obtain the transfer ID and "
-"authorization key from the original owner."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml333(para)
-msgid "Display the transfer request details by using the ID:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml334(replaceable)
-#: ./doc/common/section_cli_cinder_manage_volumes.xml348(replaceable)
-#: ./doc/common/section_cli_cinder_manage_volumes.xml392(replaceable)
-msgid "transferID"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml347(para)
-msgid "Accept the request:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml348(replaceable)
-msgid "authKey"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml359(para)
-msgid ""
-"If you do not have a sufficient quota for the transfer, the transfer is "
-"refused."
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml367(title)
-msgid "Delete a volume transfer"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml371(para)
-msgid "List available volumes and their statuses:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml382(para)
-msgid "Find the matching transfer ID:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml391(para)
-msgid "Delete the volume:"
-msgstr ""
-
-#: ./doc/common/section_cli_cinder_manage_volumes.xml397(para)
-msgid ""
-"Verify that transfer list is now empty and that the volume is again "
-"available for transfer:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml6(title)
-msgid "Show usage statistics for hosts and instances"
-msgstr "ホストおよびインスタンスの使用統計の表示"
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml7(para)
-msgid ""
-"You can show basic statistics on resource usage for hosts and instances."
-msgstr "ホストやインスタンスのリソース使用状況に関する基本的な統計を表示できます。"
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml10(para)
-msgid ""
-"For more sophisticated monitoring, see the <link "
-"href=\"https://launchpad.net/ceilometer\">ceilometer</link> project. You can"
-" also use tools, such as <link href=\"http://ganglia.info/\">Ganglia</link> "
-"or <link href=\"http://graphite.wikidot.com/\">Graphite</link>, to gather "
-"more detailed data."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml20(title)
-msgid "Show host usage statistics"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml21(para)
-msgid ""
-"The following examples show the host usage statistics for a host called "
-"<filename>devstack</filename>."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml25(para)
-msgid "List the hosts and the nova-related services that run on them:"
-msgstr "ホストおよびそのホストで実行されている nova 関連のサービスを一覧表示します。"
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml37(para)
-msgid ""
-"Get a summary of resource usage of all of the instances running on the host:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml49(para)
-msgid ""
-"The <literal>cpu</literal> column shows the sum of the virtual CPUs for "
-"instances running on the host."
-msgstr "<literal>cpu</literal> の欄は、ホストで実行中のインスタンスの仮想 CPU 総数を表示します。"
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml51(para)
-msgid ""
-"The <literal>memory_mb</literal> column shows the sum of the memory (in MB) "
-"allocated to the instances that run on the host."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml54(para)
-msgid ""
-"The <literal>disk_gb</literal> column shows the sum of the root and "
-"ephemeral disk sizes (in GB) of the instances that run on the host."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml57(para)
-msgid ""
-"The row that has the value <literal>used_now</literal> in the "
-"<literal>PROJECT</literal> column shows the sum of the resources allocated "
-"to the instances that run on the host, plus the resources allocated to the "
-"virtual machine of the host itself."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml62(para)
-msgid ""
-"The row that has the value <literal>used_max</literal> row in the "
-"<literal>PROJECT</literal> column shows the sum of the resources allocated "
-"to the instances that run on the host."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml68(para)
-msgid ""
-"These values are computed by using information about the flavors of the "
-"instances that run on the hosts. This command does not query the CPU usage, "
-"memory usage, or hard disk usage of the physical host."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml75(title)
-msgid "Show instance usage statistics"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml77(para)
-msgid "Get CPU, memory, I/O, and network statistics for an instance."
-msgstr "インスタンスの CPU、メモリー、I/O、ネットワーク統計を取得します。"
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml79(para)
-msgid "List instances:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml87(para)
-msgid "Get diagnostic statistics:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_usage_statistics.xml108(para)
-msgid "Get summary statistics for each tenant:"
-msgstr "テナント別の統計サマリーを取得します。"
-
-#: ./doc/common/ch_cli_glance_commands.xml11(title)
-msgid "Image Service command-line client"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml12(para)
-msgid ""
-"The <placeholder-1/> client is the command-line interface (CLI) for the "
-"OpenStack Image Service API and its extensions. This chapter documents "
-"<placeholder-2/> version 0.12.0."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml22(title)
-msgid "glance usage"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml43(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use image-create instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml52(emphasis)
-#: ./doc/common/ch_cli_glance_commands.xml180(emphasis)
-msgid "DEPRECATED!"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml59(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use image-delete instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml67(para)
-#: ./doc/common/ch_cli_glance_commands.xml131(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use image-list instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml75(para)
-#: ./doc/common/ch_cli_glance_commands.xml524(para)
-msgid "Create a new image."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml91(para)
-msgid "Download a specific image."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml99(para)
-#: ./doc/common/ch_cli_glance_commands.xml715(para)
-msgid "List images you can access."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml107(para)
-#: ./doc/common/ch_cli_glance_commands.xml163(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use member-list instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml115(para)
-#: ./doc/common/ch_cli_glance_commands.xml848(para)
-msgid "Describe a specific image."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml123(para)
-#: ./doc/common/ch_cli_glance_commands.xml886(para)
-msgid "Update a specific image."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml139(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use member-create instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml147(para)
-#: ./doc/common/ch_cli_glance_commands.xml1057(para)
-msgid "Share a specific image with a tenant."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml155(para)
-#: ./doc/common/ch_cli_glance_commands.xml1093(para)
-msgid "Remove a shared image from a tenant."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml171(para)
-#: ./doc/common/ch_cli_glance_commands.xml1118(para)
-msgid "Describe sharing permissions by image or tenant."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml187(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use image-show instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml195(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use image-update instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml212(title)
-msgid "glance optional arguments"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml225(para)
-msgid "Defaults to <code>env[GLANCECLIENT_DEBUG]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml233(para)
-msgid "Print more verbose output"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml241(para)
-msgid ""
-"Force retrieving the schema used to generate portions of the help text "
-"rather than using a cached copy. Ignored with api version 1"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml251(para)
-msgid ""
-"Explicitly allow glanceclient to perform \"insecure SSL\" (https) requests. "
-"The server's certificate will not be verified against any certificate "
-"authorities. This option should be used with caution."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml282(para)
-msgid ""
-"Path of CA TLS certificate(s) used to verify the remote server's "
-"certificate. Without this option glance looks for the default system CA "
-"certificates."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml300(para)
-msgid "Number of seconds to wait for a response"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml308(para)
-msgid "Disable SSL compression when using https."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml316(para)
-msgid "Prevent select actions from requesting user confirmation."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml325(para)
-msgid ""
-"<emphasis>DEPRECATED!</emphasis> Only used for deprecated legacy commands."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml333(para)
-#: ./doc/common/ch_cli_glance_commands.xml342(para)
-#: ./doc/common/ch_cli_glance_commands.xml351(para)
-msgid ""
-"<emphasis>DEPRECATED!</emphasis> Send a fully-formed endpoint using --os- "
-"image-url instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml360(para)
-msgid "Defaults to <code>env[OS_USERNAME]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml368(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use --os-username."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml376(para)
-msgid "Defaults to <code>env[OS_PASSWORD]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml384(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use --os-password."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml392(para)
-msgid "Defaults to <code>env[OS_TENANT_ID]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml400(para)
-msgid "Defaults to <code>env[OS_TENANT_NAME]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml408(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use --os-tenant-name."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml416(para)
-msgid "Defaults to <code>env[OS_AUTH_URL]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml424(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use --os-auth-url."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml432(para)
-msgid "Defaults to <code>env[OS_REGION_NAME]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml440(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use --os-region-name."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml456(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use --os-auth-token."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml464(para)
-msgid "Defaults to <code>env[OS_IMAGE_URL]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml472(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use --os-image-url."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml480(para)
-msgid "Defaults to <code>env[OS_IMAGE_API_VERSION]</code> or 1"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml488(para)
-msgid "Defaults to <code>env[OS_SERVICE_TYPE]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml496(para)
-msgid "Defaults to <code>env[OS_ENDPOINT_TYPE]</code>"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml504(para)
-msgid "<emphasis>DEPRECATED!</emphasis> This option is completely ignored."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml512(title)
-msgid "glance image-create command"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml531(para)
-msgid "of image to reserve."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml539(para)
-#: ./doc/common/ch_cli_glance_commands.xml904(para)
-msgid "Name of image."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml547(para)
-msgid "Store to upload image to."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml555(para)
-#: ./doc/common/ch_cli_glance_commands.xml912(para)
-msgid ""
-"Disk format of image. Acceptable formats: ami, ari, aki, vhd, vmdk, raw, "
-"qcow2, vdi, and iso."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml564(para)
-#: ./doc/common/ch_cli_glance_commands.xml921(para)
-msgid ""
-"Container format of image. Acceptable formats: ami, ari, aki, bare, and ovf."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml573(para)
-#: ./doc/common/ch_cli_glance_commands.xml930(para)
-msgid "Tenant who should own image."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml581(para)
-msgid ""
-"Size of image data (in bytes). Only used with '-- location' and '--"
-"copy_from'."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml590(para)
-#: ./doc/common/ch_cli_glance_commands.xml946(para)
-msgid "Minimum size of disk needed to boot image (in gigabytes)."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml599(para)
-#: ./doc/common/ch_cli_glance_commands.xml955(para)
-msgid "Minimum amount of ram needed to boot image (in megabytes)."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml608(para)
-#: ./doc/common/ch_cli_glance_commands.xml964(para)
-msgid ""
-"URL where the data for this image already resides. For example, if the image"
-" data is stored in swift, you could specify "
-"'swift://account:key@example.com/container/obj'."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml619(para)
-msgid ""
-"Local file that contains disk image to be uploaded during creation. "
-"Alternatively, images can be passed to the client via stdin."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml629(para)
-msgid ""
-"Hash of image data used Glance can use for verification. Provide a md5 "
-"checksum here."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml638(para)
-#: ./doc/common/ch_cli_glance_commands.xml994(para)
-msgid ""
-"Similar to '--location' in usage, but this indicates that the Glance server "
-"should immediately copy the data and store it in its configured image store."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml648(para)
-#: ./doc/common/ch_cli_glance_commands.xml1004(para)
-msgid "Make image accessible to the public."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml656(para)
-#: ./doc/common/ch_cli_glance_commands.xml1012(para)
-msgid "Prevent image from being deleted."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml664(para)
-#: ./doc/common/ch_cli_glance_commands.xml1020(para)
-msgid ""
-"Arbitrary property to associate with image. May be used multiple times."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml673(para)
-#: ./doc/common/ch_cli_glance_commands.xml790(para)
-#: ./doc/common/ch_cli_glance_commands.xml866(para)
-#: ./doc/common/ch_cli_glance_commands.xml1039(para)
-msgid "Print image size in a human-friendly format."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml681(para)
-#: ./doc/common/ch_cli_glance_commands.xml1047(para)
-msgid "Show upload progress bar."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml689(title)
-msgid "glance image-delete command"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml698(para)
-msgid "Name or ID of image(s) to delete."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml706(title)
-msgid "glance image-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml722(para)
-msgid "Filter images to those that have this name."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml730(para)
-msgid "Filter images to those that have this status."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml738(para)
-msgid ""
-"Filter images to those that have this container format. Acceptable formats: "
-"ami, ari, aki, bare, and ovf."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml748(para)
-msgid ""
-"Filter images to those that have this disk format. Acceptable formats: ami, "
-"ari, aki, vhd, vmdk, raw, qcow2, vdi, and iso."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml758(para)
-msgid "Filter images to those with a size greater than this."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml766(para)
-msgid "Filter images to those with a size less than this."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml774(para)
-msgid "Filter images by a user-defined image property."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml782(para)
-msgid "Number of images to request in each paginated request."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml798(para)
-msgid "Sort image list by specified field."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml806(para)
-msgid "Sort image list in specified direction."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml814(para)
-msgid "Allows the user to select a listing of public or non public images."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml823(para)
-msgid ""
-"Display only images owned by this tenant id. Filtering occurs on the client "
-"side so may be inefficient. This option is mainly intended for admin use. "
-"Use an empty string ('') to list images with no owner. Note: This option "
-"overrides the --is-public argument if present. Note: the v2 API supports "
-"more efficient server-side owner based filtering."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml837(para)
-msgid ""
-"Allows the admin user to list all images irrespective of the image's owner "
-"or is_public value."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml846(title)
-msgid "glance image-show command"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml855(para)
-msgid "Name or ID of image to describe."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml874(title)
-msgid "glance image-update command"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml893(para)
-msgid "Name or ID of image to modify."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml938(para)
-msgid "Size of image data (in bytes)."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml975(para)
-msgid ""
-"Local file that contains disk image to be uploaded during update. "
-"Alternatively, images can be passed to the client via stdin."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml985(para)
-msgid "Hash of image data used Glance can use for verification."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml1029(para)
-msgid ""
-"If this flag is present, delete all image properties not explicitly set in "
-"the update request. Otherwise, those properties not referenced are "
-"preserved."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml1055(title)
-msgid "glance member-create command"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml1064(para)
-msgid "Image to add member to."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml1072(para)
-msgid "Tenant to add as member"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml1083(para)
-msgid "Allow the specified tenant to share this image."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml1091(title)
-msgid "glance member-delete command"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml1100(para)
-msgid "Image from which to remove member"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml1108(para)
-msgid "Tenant to remove as member"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml1116(title)
-msgid "glance member-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml1125(para)
-msgid "Filter results by an image ID."
-msgstr ""
-
-#: ./doc/common/ch_cli_glance_commands.xml1133(para)
-msgid "Filter results by a tenant ID."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_userdata.xml6(title)
-msgid "Provide user data to instances"
-msgstr "インスタンスへのユーザーデータの提供"
-
-#: ./doc/common/section_cli_nova_userdata.xml7(para)
-msgid ""
-"A <glossterm baseform=\"user data\">user data</glossterm> file is a special "
-"key in the metadata service that holds a file that cloud-aware applications "
-"in the guest instance can access. For example, one application that uses "
-"user data is the <link href=\"https://help.ubuntu.com/community/CloudInit"
-"\">cloud-init</link> system, which is an open-source package from Ubuntu "
-"that is available on various Linux distributions and which handles early "
-"initialization of a cloud instance."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_userdata.xml14(para)
-msgid ""
-"You can place user data in a local file and pass it through the <parameter"
-">--user-data &lt;user-data-file&gt;</parameter> parameter at instance "
-"creation:"
-msgstr "インスタンス作成時に <parameter>--user-data &lt;user-data-file&gt;</parameter> パラメーターを使用して、ローカルファイルのユーザーデータを渡すことができます。"
-
-#: ./doc/common/section_objectstorage-replication.xml6(title)
-#: ./doc/common/section_objectstorage-components.xml192(title)
-msgid "Replication"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml7(para)
-msgid ""
-"Because each replica in Object Storage functions independently and clients "
-"generally require only a simple majority of nodes to respond to consider an "
-"operation successful, transient failures like network partitions can quickly"
-" cause replicas to diverge. These differences are eventually reconciled by "
-"asynchronous, peer-to-peer replicator processes. The replicator processes "
-"traverse their local file systems and concurrently perform operations in a "
-"manner that balances load across physical disks."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml16(para)
-msgid ""
-"Replication uses a push model, with records and files generally only being "
-"copied from local to remote replicas. This is important because data on the "
-"node might not belong there (as in the case of hand offs and ring changes), "
-"and a replicator cannot know which data it should pull in from elsewhere in "
-"the cluster. Any node that contains data must ensure that data gets to where"
-" it belongs. The ring handles replica placement."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml24(para)
-msgid ""
-"To replicate deletions in addition to creations, every deleted record or "
-"file in the system is marked by a tombstone. The replication process cleans "
-"up tombstones after a time period known as the <emphasis "
-"role=\"italic\">consistency window</emphasis>. This window defines the "
-"duration of the replication and how long transient failure can remove a node"
-" from the cluster. Tombstone cleanup must be tied to replication to reach "
-"replica convergence."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml32(para)
-msgid ""
-"If a replicator detects that a remote drive has failed, the replicator uses "
-"the <literal>get_more_nodes</literal> interface for the ring to choose an "
-"alternate node with which to synchronize. The replicator can maintain "
-"desired levels of replication during disk failures, though some replicas "
-"might not be in an immediately usable location."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml39(para)
-msgid ""
-"The replicator does not maintain desired levels of replication when failures"
-" such as entire node failures occur; most failures are transient."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml43(para)
-msgid "The main replication types are:"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml46(para)
-msgid ""
-"<emphasis role=\"bold\">Database replication</emphasis>. Replicates "
-"containers and objects."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml51(para)
-msgid ""
-"<emphasis role=\"bold\">Object replication</emphasis>. Replicates object "
-"data."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml56(title)
-msgid "Database replication"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml57(para)
-msgid ""
-"Database replication completes a low-cost hash comparison to determine "
-"whether two replicas already match. Normally, this check can quickly verify "
-"that most databases in the system are already synchronized. If the hashes "
-"differ, the replicator synchronizes the databases by sharing records added "
-"since the last synchronization point."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml64(para)
-msgid ""
-"This synchronization point is a high water mark that notes the last record "
-"at which two databases were known to be synchronized, and is stored in each "
-"database as a tuple of the remote database ID and record ID. Database IDs "
-"are unique across all replicas of the database, and record IDs are "
-"monotonically increasing integers. After all new records are pushed to the "
-"remote database, the entire synchronization table of the local database is "
-"pushed, so the remote database can guarantee that it is synchronized with "
-"everything with which the local database was previously synchronized."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml75(para)
-msgid ""
-"If a replica is missing, the whole local database file is transmitted to the"
-" peer by using rsync(1) and is assigned a new unique ID."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml78(para)
-msgid ""
-"In practice, database replication can process hundreds of databases per "
-"concurrency setting per second (up to the number of available CPUs or disks)"
-" and is bound by the number of database transactions that must be performed."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml85(title)
-msgid "Object replication"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml86(para)
-msgid ""
-"The initial implementation of object replication performed an rsync to push "
-"data from a local partition to all remote servers where it was expected to "
-"reside. While this worked at small scale, replication times skyrocketed once"
-" directory structures could no longer be held in RAM. This scheme was "
-"modified to save a hash of the contents for each suffix directory to a per-"
-"partition hashes file. The hash for a suffix directory is no longer valid "
-"when the contents of that suffix directory is modified."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml95(para)
-msgid ""
-"The object replication process reads in hash files and calculates any "
-"invalidated hashes. Then, it transmits the hashes to each remote server that"
-" should hold the partition, and only suffix directories with differing "
-"hashes on the remote server are rsynced. After pushing files to the remote "
-"server, the replication process notifies it to recalculate hashes for the "
-"rsynced suffix directories."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-replication.xml103(para)
-msgid ""
-"The number of uncached directories that object replication must traverse, "
-"usually as a result of invalidated suffix directory hashes, impedes "
-"performance. To provide acceptable replication speeds, object replication is"
-" designed to invalidate around 2 percent of the hash space on a normal node "
-"each day."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_reboot.xml5(title)
-msgid "Reboot an instance"
-msgstr "インスタンスの再起動"
-
-#: ./doc/common/section_cli_nova_reboot.xml6(para)
-msgid ""
-"You can soft or hard reboot a running instance. A soft reboot attempts a "
-"graceful shut down and restart of the instance. A hard reboot power cycles "
-"the instance."
-msgstr "実行中のインスタンスのソフトリブートまたはハードリブートを行うことができます。ソフトリブートは、グレースフルシャットダウンの後インスタンスの再起動を試行します。ハードリブートは、インスタンスの電源を一旦切って再投入します。"
-
-#: ./doc/common/section_cli_nova_reboot.xml9(para)
-msgid "By default, when you reboot a server, it is a soft reboot."
-msgstr "デフォルトでは、サーバーをリブートする場合ソフトリブートとなっています。"
-
-#: ./doc/common/section_cli_nova_reboot.xml10(replaceable)
-#: ./doc/common/section_cli_nova_reboot.xml12(replaceable)
-msgid "SERVER"
-msgstr "SERVER"
-
-#: ./doc/common/section_cli_nova_reboot.xml11(para)
-msgid ""
-"To perform a hard reboot, pass the <parameter>--hard</parameter> parameter, "
-"as follows:"
-msgstr "ハードリブートを実行するには、以下のように <parameter>--hard</parameter> パラメーターを指定します。"
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml6(title)
-msgid "Ring-builder"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml7(para)
-msgid ""
-"Use the swift-ring-builder utility to build and manage rings. This utility "
-"assigns partitions to devices and writes an optimized Python structure to a "
-"gzipped, serialized file on disk for transmission to the servers. The server"
-" processes occasionally check the modification time of the file and reload "
-"in-memory copies of the ring structure as needed. If you use a slightly "
-"older version of the ring, one of the three replicas for a partition subset "
-"will be incorrect because of the way the ring-builder manages changes to the"
-" ring. You can work around this issue."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml17(para)
-msgid ""
-"The ring-builder also keeps its own builder file with the ring information "
-"and additional data required to build future rings. It is very important to "
-"keep multiple backup copies of these builder files. One option is to copy "
-"the builder files out to every server while copying the ring files "
-"themselves. Another is to upload the builder files into the cluster itself. "
-"If you lose the builder file, you have to create a new ring from scratch. "
-"Nearly all partitions would be assigned to different devices and, therefore,"
-" nearly all of the stored data would have to be replicated to new locations."
-" So, recovery from a builder file loss is possible, but data would be "
-"unreachable for an extended time."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml30(title)
-msgid "Ring data structure"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml31(para)
-msgid ""
-"The ring data structure consists of three top level fields: a list of "
-"devices in the cluster, a list of lists of device ids indicating partition "
-"to device assignments, and an integer indicating the number of bits to shift"
-" an MD5 hash to calculate the partition for the hash."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml38(title)
-msgid "Partition assignment list"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml39(para)
-msgid ""
-"This is a list of <literal>array(‘H’)</literal> of devices ids. The "
-"outermost list contains an <literal>array(‘H’)</literal> for each replica. "
-"Each <literal>array(‘H’)</literal> has a length equal to the partition count"
-" for the ring. Each integer in the <literal>array(‘H’)</literal> is an index"
-" into the above list of devices. The partition list is known internally to "
-"the Ring class as <literal>_replica2part2dev_id</literal>."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml48(para)
-msgid ""
-"So, to create a list of device dictionaries assigned to a partition, the "
-"Python code would look like: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml52(para)
-msgid ""
-"That code is a little simplistic because it does not account for the removal"
-" of duplicate devices. If a ring has more replicas than devices, a partition"
-" will have more than one replica on a device."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml56(para)
-msgid ""
-"<literal>array(‘H’)</literal> is used for memory conservation as there may "
-"be millions of partitions."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml61(title)
-msgid "Replica counts"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml62(para)
-msgid ""
-"To support the gradual change in replica counts, a ring can have a real "
-"number of replicas and is not restricted to an integer number of replicas."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml65(para)
-msgid ""
-"A fractional replica count is for the whole ring and not for individual "
-"partitions. It indicates the average number of replicas for each partition. "
-"For example, a replica count of 3.2 means that 20 percent of partitions have"
-" four replicas and 80 percent have three replicas."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml70(para)
-msgid "The replica count is adjustable."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml71(para)
-msgid "Example:"
-msgstr "例:"
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml74(para)
-msgid ""
-"You must rebalance the replica ring in globally distributed clusters. "
-"Operators of these clusters generally want an equal number of replicas and "
-"regions. Therefore, when an operator adds or removes a region, the operator "
-"adds or removes a replica. Removing unneeded replicas saves on the cost of "
-"disks."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml80(para)
-msgid ""
-"You can gradually increase the replica count at a rate that does not "
-"adversely affect cluster performance."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml90(para)
-msgid ""
-"Changes take effect after the ring is rebalanced. Therefore, if you intend "
-"to change from 3 replicas to 3.01 but you accidentally type "
-"<literal>2.01</literal>, no data is lost."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml95(replaceable)
-msgid "X.builder"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml94(para)
-msgid ""
-"Additionally, <placeholder-1/> can now take a decimal argument for the "
-"number of replicas."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml100(title)
-msgid "Partition shift value"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml101(para)
-msgid ""
-"The partition shift value is known internally to the Ring class as "
-"<literal>_part_shift</literal>. This value is used to shift an MD5 hash to "
-"calculate the partition where the data for that hash should reside. Only the"
-" top four bytes of the hash is used in this process. For example, to compute"
-" the partition for the <literal>/account/container/object</literal> path, "
-"the Python code might look like the following code: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml112(para)
-msgid ""
-"For a ring generated with part_power P, the partition shift value is "
-"<literal>32 - P</literal>."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml116(title)
-msgid "Build the ring"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml117(para)
-msgid "The ring builder process includes these high-level steps:"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml121(para)
-msgid ""
-"The utility calculates the number of partitions to assign to each device "
-"based on the weight of the device. For example, for a partition at the power"
-" of 20, the ring has 1,048,576 partitions. One thousand devices of equal "
-"weight will each want 1,048.576 partitions. The devices are sorted by the "
-"number of partitions they desire and kept in order throughout the "
-"initialization process."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml131(para)
-msgid ""
-"Each device is also assigned a random tiebreaker value that is used when two"
-" devices desire the same number of partitions. This tiebreaker is not stored"
-" on disk anywhere, and so two different rings created with the same "
-"parameters will have different partition assignments. For repeatable "
-"partition assignments, <literal>RingBuilder.rebalance()</literal> takes an "
-"optional seed value that seeds the Python pseudo-random number generator."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml145(para)
-msgid ""
-"The ring builder assigns each partition replica to the device that requires "
-"most partitions at that point while keeping it as far away as possible from "
-"other replicas. The ring builder prefers to assign a replica to a device in "
-"a region that does not already have a replica. If no such region is "
-"available, the ring builder searches for a device in a different zone, or on"
-" a different server. If it does not find one, it looks for a device with no "
-"replicas. Finally, if all options are exhausted, the ring builder assigns "
-"the replica to the device that has the fewest replicas already assigned."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml159(para)
-msgid ""
-"The ring builder assigns multiple replicas to one device only if the ring "
-"has fewer devices than it has replicas."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml165(para)
-msgid ""
-"When building a new ring from an old ring, the ring builder recalculates the"
-" desired number of partitions that each device wants."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml174(para)
-msgid ""
-"The ring builder unassigns any assigned partitions from any removed devices "
-"and adds these partitions to the gathered list."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml180(para)
-msgid ""
-"The ring builder unassigns any partition replicas that can be spread out for"
-" better durability and adds these partitions to the gathered list."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml187(para)
-msgid ""
-"The ring builder unassigns random partitions from any devices that have more"
-" partitions than they need and adds these partitions to the gathered list."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml170(para)
-msgid ""
-"The ring builder unassigns partitions and gathers these partitions for "
-"reassignment, as follows: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml197(para)
-msgid ""
-"The ring builder reassigns the gathered partitions to devices by using a "
-"similar method to the one described previously."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml202(para)
-msgid ""
-"When the ring builder reassigns a replica to a partition, the ring builder "
-"records the time of the reassignment. The ring builder uses this value when "
-"it gathers partitions for reassignment so that no partition is moved twice "
-"in a configurable amount of time. The RingBuilder class knows this "
-"configurable amount of time as <literal>min_part_hours</literal>. The ring "
-"builder ignores this restriction for replicas of partitions on removed "
-"devices because removal of a device happens on device failure only, and "
-"reassignment is the only choice."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-ringbuilder.xml216(para)
-msgid ""
-"Theses steps do not always perfectly rebalance a ring due to the random "
-"nature of gathering partitions for reassignment. To help reach a more "
-"balanced ring, the rebalance process is repeated until near perfect (less "
-"than 1 percent off) or when the balance does not improve by at least 1 "
-"percent (indicating we probably cannot get perfect balance due to wildly "
-"imbalanced zones or too many partitions recently moved)."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-account-reaper.xml7(title)
-msgid "Account reaper"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-account-reaper.xml8(para)
-msgid ""
-"In the background, the account reaper removes data from the deleted "
-"accounts."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-account-reaper.xml9(para)
-msgid ""
-"A reseller marks an account for deletion by issuing a <code>DELETE</code> "
-"request on the account’s storage URL. This action sets the "
-"<code>status</code> column of the account_stat table in the account database"
-" and replicas to <code>DELETED</code>, marking the account's data for "
-"deletion."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-account-reaper.xml17(para)
-msgid ""
-"It's on the developers' to-do list to write a utility that performs this "
-"task, preferably through a ReST call."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-account-reaper.xml12(para)
-msgid ""
-"Typically, a specific retention time or undelete are not provided. However, "
-"you can set a <code>delay_reaping</code> value in the <code>[account-"
-"reaper]</code> section of the account-server.conf to delay the actual "
-"deletion of data. At this time, to undelete you have to update the account "
-"database replicas directly, setting the status column to an empty string and"
-" updating the put_timestamp to be greater than the delete_timestamp. "
-"<placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-account-reaper.xml20(para)
-msgid ""
-"The account reaper runs on each account server and scans the server "
-"occasionally for account databases marked for deletion. It only fires up on "
-"the accounts for which the server is the primary node, so that multiple "
-"account servers aren’t trying to do it simultaneously. Using multiple "
-"servers to delete one account might improve the deletion speed but requires "
-"coordination to avoid duplication. Speed really is not a big concern with "
-"data deletion, and large accounts aren’t deleted often."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-account-reaper.xml26(para)
-msgid ""
-"Deleting an account is simple. For each account container, all objects are "
-"deleted and then the container is deleted. Deletion requests that fail will "
-"not stop the overall process but will cause the overall process to fail "
-"eventually (for example, if an object delete times out, you will not be able"
-" to delete the container or the account). The account reaper keeps trying to"
-" delete an account until it is empty, at which point the database reclaim "
-"process within the db_replicator will remove the database files."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-account-reaper.xml32(para)
-msgid ""
-"A persistent error state may prevent the deletion of an object or container."
-" If this happens, you will see a message such as <code>“Account &lt;name&gt;"
-" has not been reaped since &lt;date&gt;”</code> in the log. You can control "
-"when this is logged with the <code>reap_warn_after</code> value in the <code"
-">[account-reaper]</code> section of the account-server.conf file. The "
-"default value is 30 days."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml9(title)
-msgid "Troubleshoot Compute"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml10(para)
-msgid ""
-"Common problems for Compute typically involve misconfigured networking or "
-"credentials that are not sourced properly in the environment. Also, most "
-"flat networking configurations do not enable <placeholder-1/> or "
-"<placeholder-2/> from a compute node to the instances that run on that node."
-" Another common problem is trying to run 32-bit images on a 64-bit compute "
-"node. This section shows you how to troubleshoot Compute."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml19(title)
-msgid "Compute service logging"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml20(para)
-msgid ""
-"Compute stores a log file for each service in "
-"<filename>/var/log/nova</filename>. For example, <filename>nova-"
-"compute.log</filename> is the log for the <systemitem class=\"service"
-"\">nova-compute</systemitem> service. You can set the following options to "
-"format log strings for the nova.log module in the "
-"<filename>nova.conf</filename> file:"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml29(literal)
-msgid "logging_context_format_string"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml32(literal)
-msgid "logging_default_format_string"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml35(para)
-msgid ""
-"If the log level is set to <literal>debug</literal>, you can also specify "
-"<literal>logging_debug_format_suffix</literal> to append extra formatting. "
-"For information about what variables are available for the formatter see: "
-"<link "
-"href=\"http://docs.python.org/library/logging.html#formatter\">http://docs.python.org/library/logging.html#formatter</link>."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml42(para)
-msgid ""
-"You have two options for logging for OpenStack Compute based on "
-"configuration settings. In <filename>nova.conf</filename>, include the "
-"<literal>logfile</literal> option to enable logging. Alternatively you can "
-"set <literal>use_syslog = 1</literal> so that the nova daemon logs to "
-"syslog."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml50(title)
-msgid "Guru Meditation reports"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml51(para)
-msgid ""
-"A Guru Meditation report is sent by the Compute Service upon receipt of the "
-"<systemitem>SIGUSR1</systemitem> signal. This report is a general-purpose "
-"error report, including a complete report of the service's current state, "
-"and is sent to <systemitem>stderr</systemitem>."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml55(para)
-msgid ""
-"For example, if you redirect error output to <filename>nova-api-"
-"err.log</filename> using <placeholder-1/>, resulting in the process ID 8675,"
-" you can then run:"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml59(para)
-msgid ""
-"This command triggers the Guru Meditation report to be printed to "
-"<filename>/var/log/nova/nova-api-err.log</filename>."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml63(para)
-msgid ""
-"Package Displays information about the package to which the process belongs,"
-" including version information."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml65(para)
-msgid ""
-"Threads Displays stack traces and thread IDs for each of the threads within "
-"the process."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml67(para)
-msgid ""
-"Green Threads Displays stack traces for each of the green threads within the"
-" process (green threads do not have thread IDs)."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml69(para)
-msgid ""
-"Configuration Lists all configuration options currently accessible through "
-"the CONF object for the current process."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml61(para)
-msgid "The report has the following sections: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml72(para)
-msgid ""
-"For more information, see <link "
-"href=\"http://docs.openstack.org/developer/nova/devref/gmr.html\">Guru "
-"Meditation Reports</link>."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml77(title)
-msgid "Common errors and fixes for Compute"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml78(para)
-msgid ""
-"The <link href=\"ask.openstack.org\">ask.openstack.org</link> site offers a "
-"place to ask and answer questions, and you can also mark questions as "
-"frequently asked questions. This section describes some errors people have "
-"posted previously. Bugs are constantly being fixed, so online resources are "
-"a great way to get the most up-to-date errors and fixes."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml86(title)
-msgid "Credential errors, 401, and 403 forbidden errors"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml93(para)
-msgid ""
-"<emphasis role=\"bold\">Manual method</emphasis>. Get get the "
-"<filename>novarc</filename> file from the project ZIP file, save existing "
-"credentials in case of override. and manually source the "
-"<filename>novarc</filename> file."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml103(para)
-msgid ""
-"<emphasis role=\"bold\">Script method</emphasis>. Generates "
-"<filename>novarc</filename> from the project ZIP file and sources it for "
-"you."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml88(para)
-msgid ""
-"Missing credentials cause a "
-"<errorcode>403</errorcode><errortext>forbidden</errortext> error. To resolve"
-" this issue, use one of these methods:<placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml110(para)
-msgid ""
-"When you run <systemitem class=\"service\">nova-api</systemitem> the first "
-"time, it generates the certificate authority information, including "
-"<filename>openssl.cnf</filename>. If you start the CA services before this, "
-"you might not be able to create your ZIP file. Restart the services. When "
-"your CA information is available, create your ZIP file."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml118(para)
-msgid ""
-"Also, check your HTTP proxy settings to see whether they cause problems with"
-" <filename>novarc</filename> creation."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml123(title)
-msgid "Instance errors"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml124(para)
-msgid ""
-"Sometimes a particular instance shows <literal>pending</literal> or you "
-"cannot SSH to it. Sometimes the image itself is the problem. For example, "
-"when you use flat manager networking, you do not have a DHCP server and "
-"certain images do not support interface injection; you cannot connect to "
-"them. The fix for this problem is to use an image that does support this "
-"method, such as Ubuntu, which obtains an IP address correctly with "
-"FlatManager network settings."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml134(para)
-msgid ""
-"To troubleshoot other possible problems with an instance, such as an "
-"instance that stays in a spawning state, check the directory for the "
-"particular instance under <filename>/var/lib/nova/instances</filename> on "
-"the <systemitem class=\"service\">nova-compute</systemitem> host and make "
-"sure that these files are present:"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml143(filename)
-msgid "libvirt.xml"
-msgstr "libvirt.xml"
-
-#: ./doc/common/section_support-compute.xml146(filename)
-msgid "disk"
-msgstr "disk"
-
-#: ./doc/common/section_support-compute.xml149(filename)
-msgid "disk-raw"
-msgstr "disk-raw"
-
-#: ./doc/common/section_support-compute.xml152(filename)
-msgid "kernel"
-msgstr "kernel"
-
-#: ./doc/common/section_support-compute.xml155(filename)
-msgid "ramdisk"
-msgstr "ramdisk"
-
-#: ./doc/common/section_support-compute.xml158(para)
-msgid "After the instance starts, <filename>console.log</filename>"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml162(para)
-msgid ""
-"If any files are missing, empty, or very small, the <systemitem "
-"class=\"service\">nova-compute</systemitem> service did not successfully "
-"download the images from the Image Service."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml167(para)
-msgid ""
-"Also check <filename>nova-compute.log</filename> for exceptions. Sometimes "
-"they do not appear in the console output."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml170(para)
-msgid ""
-"Next, check the log file for the instance in the "
-"<filename>/var/log/libvirt/qemu</filename> directory to see if it exists and"
-" has any useful error messages in it."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml174(para)
-msgid ""
-"Finally, from the <filename>/var/lib/nova/instances</filename> directory for"
-" the instance, see if this command returns an error:"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml181(title)
-msgid "Empty log output for Linux instances"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml182(para)
-msgid ""
-"You can view the log output of running instances from either the "
-"<guilabel>Log</guilabel> tab of the dashboard or the output of "
-"<placeholder-1/>. In some cases, the log output of a running Linux instance "
-"will be empty or only display a single character (for example, the "
-"<keycap>?</keycap> character)."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml189(para)
-msgid ""
-"This occurs when the Compute service attempts to retrieve the log output of "
-"the instance via a serial console while the instance itself is not "
-"configured to send output to the console. To rectify this, append the "
-"following parameters to kernel arguments specified in the instance's boot "
-"loader:"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml196(para)
-msgid ""
-"Upon rebooting, the instance will be configured to send output to the "
-"Compute service."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml201(title)
-msgid "Reset the state of an instance"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml202(para)
-msgid ""
-"If an instance remains in an intermediate state, such as "
-"<literal>deleting</literal>, you can use the <placeholder-1/> command to "
-"manually reset the state of an instance to an error state. You can then "
-"delete the instance. For example:"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml209(para)
-msgid ""
-"You can also use the <parameter>--active</parameter> parameter to force the "
-"instance back to an active state instead of an error state. For example:"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml215(title)
-msgid "Injection problems"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml216(para)
-msgid ""
-"If instances do not boot or boot slowly, investigate file injection as a "
-"cause."
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml218(para)
-msgid ""
-"To disable injection in libvirt, set the following in "
-"<filename>nova.conf</filename>:"
-msgstr ""
-
-#: ./doc/common/section_support-compute.xml223(para)
-msgid ""
-"If you have not enabled the configuration drive and you want to make user-"
-"specified files available from the metadata server for to improve "
-"performance and avoid boot failure if injection fails, you must disable "
-"injection."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_search_ip.xml7(title)
-msgid "Search for an instance using IP address"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_search_ip.xml8(para)
-msgid ""
-"You can search for an instance using the IP address parameter, "
-"<literal>--ip</literal>, with the <placeholder-1/> command."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_search_ip.xml11(parameter)
-#: ./doc/common/section_cli_nova_search_ip.xml14(parameter)
-msgid "ip"
-msgstr "ip"
-
-#: ./doc/common/section_cli_nova_search_ip.xml11(replaceable)
-msgid "IP_ADDRESS"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_search_ip.xml12(para)
-msgid ""
-"The following example shows the results of a search on "
-"<filename>10.0.0.4</filename>."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_search_ip.xml14(replaceable)
-msgid "10.0.0.4"
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml7(title)
-msgid "Configure the Identity Service with SSL"
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml8(para)
-msgid "You can configure the Identity Service to support two-way SSL."
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml10(para)
-msgid "You must obtain the x509 certificates externally and configure them."
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml12(para)
-msgid ""
-"The Identity Service provides a set of sample certificates in the <filename "
-"class=\"directory\">examples/pki/certs</filename> and <filename "
-"class=\"directory\">examples/pki/private</filename> directories:"
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml18(title)
-msgid "Certificate types"
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml20(term)
-msgid "cacert.pem"
-msgstr "cacert.pem"
-
-#: ./doc/common/section_keystone-ssl-config.xml22(para)
-msgid "Certificate Authority chain to validate against."
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml27(term)
-msgid "ssl_cert.pem"
-msgstr "ssl_cert.pem"
-
-#: ./doc/common/section_keystone-ssl-config.xml29(para)
-msgid "Public certificate for Identity Service server."
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml34(term)
-msgid "middleware.pem"
-msgstr "middleware.pem"
-
-#: ./doc/common/section_keystone-ssl-config.xml36(para)
-msgid "Public and private certificate for Identity Service middleware/client."
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml41(term)
-msgid "cakey.pem"
-msgstr "cakey.pem"
-
-#: ./doc/common/section_keystone-ssl-config.xml43(para)
-msgid "Private key for the CA."
-msgstr "CA の秘密鍵。"
-
-#: ./doc/common/section_keystone-ssl-config.xml47(term)
-msgid "ssl_key.pem"
-msgstr "ssl_key.pem"
-
-#: ./doc/common/section_keystone-ssl-config.xml49(para)
-msgid "Private key for the Identity Service server."
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml55(para)
-msgid ""
-"You can choose names for these certificates. You can also combine the "
-"public/private keys in the same file, if you wish. These certificates are "
-"provided as an example."
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml61(title)
-msgid "SSL configuration"
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml62(para)
-msgid ""
-"To enable SSL with client authentication, modify the "
-"<literal>[ssl]</literal> section in the "
-"<filename>etc/keystone.conf</filename> file. The following SSL configuration"
-" example uses the included sample certificates:"
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml74(title)
-msgid "Options"
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml76(para)
-msgid "<literal>enable</literal>. True enables SSL. Default is False."
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml80(para)
-msgid ""
-"<literal>certfile</literal>. Path to the Identity Service public certificate"
-" file."
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml84(para)
-msgid ""
-"<literal>keyfile</literal>. Path to the Identity Service private certificate"
-" file. If you include the private key in the certfile, you can omit the "
-"keyfile."
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml90(para)
-msgid "<literal>ca_certs</literal>. Path to the CA trust chain."
-msgstr ""
-
-#: ./doc/common/section_keystone-ssl-config.xml94(para)
-msgid ""
-"<literal>cert_required</literal>. Requires client certificate. Default is "
-"False."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml6(title)
-msgid "Stop and start an instance"
-msgstr "インスタンスの停止と起動"
-
-#: ./doc/common/section_cli_nova_startstop.xml7(para)
-msgid "Use one of the following methods to stop and start an instance."
-msgstr "以下の手段の 1 つを使用して、インスタンスを停止して起動します。"
-
-#: ./doc/common/section_cli_nova_startstop.xml10(title)
-msgid "Pause and unpause an instance"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml13(para)
-msgid "To pause an instance, run the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml15(para)
-msgid ""
-"This command stores the state of the VM in RAM. A paused instance continues "
-"to run in a frozen state."
-msgstr "このコマンドは、RAM に仮想マシンの状態を保存します。一時停止となったインスタンスは、一時停止した状態で実行が継続されます。"
-
-#: ./doc/common/section_cli_nova_startstop.xml17(para)
-msgid "To unpause the instance, run the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml23(title)
-msgid "Suspend and resume an instance"
-msgstr "インスタンスの休止と再開"
-
-#: ./doc/common/section_cli_nova_startstop.xml25(para)
-msgid ""
-"Administrative users might want to suspend an instance if it is infrequently"
-" used or to perform system maintenance. When you suspend an instance, its VM"
-" state is stored on disk, all memory is written to disk, and the virtual "
-"machine is stopped. Suspending an instance is similar to placing a device in"
-" hibernation; memory and vCPUs become available to create other instances."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml33(para)
-msgid ""
-"To initiate a hypervisor-level suspend operation, run the following command:"
-msgstr "イパーバイザーレベルの休止操作を開始するには、以下のコマンドを実行します。"
-
-#: ./doc/common/section_cli_nova_startstop.xml38(para)
-msgid "To resume a suspended instance, run the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml45(title)
-msgid "Shelve and unshelve an instance"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml46(para)
-msgid ""
-"Shelving is useful if you have an instance that you are not using, but would"
-" like retain in your list of servers. For example, you can stop an instance "
-"at the end of a work week, and resume work again at the start of the next "
-"week. All associated data and resources are kept; however, anything still in"
-" memory is not retained. If a shelved instance is no longer needed, it can "
-"also be entirely removed."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml51(para)
-msgid "You can complete the following shelving tasks:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml53(term)
-msgid "Shelve an instance"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml54(para)
-msgid ""
-"Shuts down the instance, and stores it together with associated data and "
-"resources (a snapshot is taken if not volume backed). Anything in memory is "
-"lost. Use the following command:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml57(replaceable)
-#: ./doc/common/section_cli_nova_startstop.xml62(replaceable)
-#: ./doc/common/section_cli_nova_startstop.xml69(replaceable)
-msgid "SERVERNAME"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml60(term)
-msgid "Unshelve an instance"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml61(para)
-msgid "Restores the instance:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml65(term)
-msgid "Remove a shelved instance"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_startstop.xml66(para)
-msgid ""
-"Removes the instance from the server; data and resource associations are "
-"deleted. If an instance is no longer needed, you can move that instance off "
-"the hypervisor in order to minimize resource usage:"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-components.xml43(None)
-msgid ""
-"@@image: '../common/figures/objectstorage-buildingblocks.png'; "
-"md5=ed79466c8464513dbeaf1e0954280e5e"
-msgstr "@@image: '../common/figures/objectstorage-buildingblocks.png'; md5=ed79466c8464513dbeaf1e0954280e5e"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-components.xml86(None)
-msgid ""
-"@@image: '../common/figures/objectstorage-ring.png'; "
-"md5=a94e26734cec6980c3684d9e824eac2d"
-msgstr "@@image: '../common/figures/objectstorage-ring.png'; md5=a94e26734cec6980c3684d9e824eac2d"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-components.xml126(None)
-msgid ""
-"@@image: '../common/figures/objectstorage-zones.png'; "
-"md5=1b1dc0abe6ea0c516f22ce399deb75ed"
-msgstr "@@image: '../common/figures/objectstorage-zones.png'; md5=1b1dc0abe6ea0c516f22ce399deb75ed"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-components.xml144(None)
-msgid ""
-"@@image: '../common/figures/objectstorage-accountscontainers.png'; "
-"md5=4b15e5a202db5bde53c9b369058aeab8"
-msgstr "@@image: '../common/figures/objectstorage-accountscontainers.png'; md5=4b15e5a202db5bde53c9b369058aeab8"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-components.xml169(None)
-msgid ""
-"@@image: '../common/figures/objectstorage-partitions.png'; "
-"md5=2c161c2e92d6fefc8140ec86e79e9492"
-msgstr "@@image: '../common/figures/objectstorage-partitions.png'; md5=2c161c2e92d6fefc8140ec86e79e9492"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-components.xml195(None)
-msgid ""
-"@@image: '../common/figures/objectstorage-replication.png'; "
-"md5=9d55594d7f445764569ab04d8d4373b2"
-msgstr "@@image: '../common/figures/objectstorage-replication.png'; md5=9d55594d7f445764569ab04d8d4373b2"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-components.xml222(None)
-msgid ""
-"@@image: '../common/figures/objectstorage-usecase.png'; "
-"md5=07480e7175b383171173775fb96d70d7"
-msgstr "@@image: '../common/figures/objectstorage-usecase.png'; md5=07480e7175b383171173775fb96d70d7"
-
-#: ./doc/common/section_objectstorage-components.xml7(title)
-msgid "Components"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml8(para)
-msgid ""
-"The components that enable Object Storage to deliver high availability, high"
-" durability, and high concurrency are:"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml12(para)
-msgid ""
-"<emphasis role=\"bold\">Proxy servers.</emphasis> Handle all of the incoming"
-" API requests."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml16(para)
-msgid ""
-"<emphasis role=\"bold\">Rings.</emphasis> Map logical names of data to "
-"locations on particular disks."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml20(para)
-msgid ""
-"<emphasis role=\"bold\">Zones.</emphasis> Isolate data from other zones. A "
-"failure in one zone doesn’t impact the rest of the cluster because data is "
-"replicated across zones."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml25(para)
-msgid ""
-"<emphasis role=\"bold\">Accounts and containers.</emphasis> Each account and"
-" container are individual databases that are distributed across the cluster."
-" An account database contains the list of containers in that account. A "
-"container database contains the list of objects in that container."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml31(para)
-msgid "<emphasis role=\"bold\">Objects.</emphasis> The data itself."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml34(para)
-msgid ""
-"<emphasis role=\"bold\">Partitions.</emphasis> A partition stores objects, "
-"account databases, and container databases and helps manage locations where "
-"data lives in the cluster."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml40(title)
-msgid "Object Storage building blocks"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml48(title)
-msgid "Proxy servers"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml49(para)
-msgid ""
-"Proxy servers are the public face of Object Storage and handle all of the "
-"incoming API requests. Once a proxy server receives a request, it determines"
-" the storage node based on the object's URL, for example, "
-"https://swift.example.com/v1/account/container/object. Proxy servers also "
-"coordinate responses, handle failures, and coordinate timestamps."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml54(para)
-msgid ""
-"Proxy servers use a shared-nothing architecture and can be scaled as needed "
-"based on projected workloads. A minimum of two proxy servers should be "
-"deployed for redundancy. If one proxy server fails, the others take over."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml59(title)
-msgid "Rings"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml60(para)
-msgid ""
-"A ring represents a mapping between the names of entities stored on disk and"
-" their physical locations. There are separate rings for accounts, "
-"containers, and objects. When other components need to perform any operation"
-" on an object, container, or account, they need to interact with the "
-"appropriate ring to determine their location in the cluster."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml65(para)
-msgid ""
-"The ring maintains this mapping using zones, devices, partitions, and "
-"replicas. Each partition in the ring is replicated, by default, three times "
-"across the cluster, and partition locations are stored in the mapping "
-"maintained by the ring. The ring is also responsible for determining which "
-"devices are used for handoff in failure scenarios."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml70(para)
-msgid ""
-"Data can be isolated into zones in the ring. Each partition replica is "
-"guaranteed to reside in a different zone. A zone could represent a drive, a "
-"server, a cabinet, a switch, or even a data center."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml73(para)
-msgid ""
-"The partitions of the ring are equally divided among all of the devices in "
-"the Object Storage installation. When partitions need to be moved around "
-"(for example, if a device is added to the cluster), the ring ensures that a "
-"minimum number of partitions are moved at a time, and only one replica of a "
-"partition is moved at a time."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml77(para)
-msgid ""
-"Weights can be used to balance the distribution of partitions on drives "
-"across the cluster. This can be useful, for example, when differently sized "
-"drives are used in a cluster."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml80(para)
-msgid ""
-"The ring is used by the proxy server and several background processes (like "
-"replication)."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml83(title)
-msgid "The <emphasis role=\"bold\">ring</emphasis>"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml90(para)
-msgid ""
-"These rings are externally managed, in that the server processes themselves "
-"do not modify the rings, they are instead given new rings modified by other "
-"tools."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml92(para)
-msgid ""
-"The ring uses a configurable number of bits from a path’s MD5 hash as a "
-"partition index that designates a device. The number of bits kept from the "
-"hash is known as the partition power, and 2 to the partition power indicates"
-" the partition count. Partitioning the full MD5 hash ring allows other parts"
-" of the cluster to work in batches of items at once which ends up either "
-"more efficient or at least less complex than working with each item "
-"separately or the entire cluster all at once."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml101(para)
-msgid ""
-"Another configurable value is the replica count, which indicates how many of"
-" the partition-device assignments make up a single ring. For a given "
-"partition number, each replica’s device will not be in the same zone as any "
-"other replica's device. Zones can be used to group devices based on physical"
-" locations, power separations, network separations, or any other attribute "
-"that would improve the availability of multiple replicas at the same time."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml109(title)
-#: ./doc/common/section_objectstorage-components.xml123(title)
-msgid "Zones"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml110(para)
-msgid ""
-"Object Storage allows configuring zones in order to isolate failure "
-"boundaries. Each data replica resides in a separate zone, if possible. At "
-"the smallest level, a zone could be a single drive or a grouping of a few "
-"drives. If there were five object storage servers, then each server would "
-"represent its own zone. Larger deployments would have an entire rack (or "
-"multiple racks) of object servers, each representing a zone. The goal of "
-"zones is to allow the cluster to tolerate significant outages of storage "
-"servers without losing all replicas of the data."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml117(para)
-msgid ""
-"As mentioned earlier, everything in Object Storage is stored, by default, "
-"three times. Swift will place each replica \"as-uniquely-as-possible\" to "
-"ensure both high availability and high durability. This means that when "
-"chosing a replica location, Object Storage chooses a server in an unused "
-"zone before an unused server in a zone that already has a replica of the "
-"data."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml130(para)
-msgid ""
-"When a disk fails, replica data is automatically distributed to the other "
-"zones to ensure there are three copies of the data."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml134(title)
-#: ./doc/common/section_objectstorage-components.xml141(title)
-msgid "Accounts and containers"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml135(para)
-msgid ""
-"Each account and container is an individual SQLite database that is "
-"distributed across the cluster. An account database contains the list of "
-"containers in that account. A container database contains the list of "
-"objects in that container."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml148(para)
-msgid ""
-"To keep track of object data locations, each account in the system has a "
-"database that references all of its containers, and each container database "
-"references each object."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml153(title)
-#: ./doc/common/section_objectstorage-components.xml166(title)
-msgid "Partitions"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml154(para)
-msgid ""
-"A partition is a collection of stored data, including account databases, "
-"container databases, and objects. Partitions are core to the replication "
-"system."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml156(para)
-msgid ""
-"Think of a partition as a bin moving throughout a fulfillment center "
-"warehouse. Individual orders get thrown into the bin. The system treats that"
-" bin as a cohesive entity as it moves throughout the system. A bin is easier"
-" to deal with than many little things. It makes for fewer moving parts "
-"throughout the system."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml160(para)
-msgid ""
-"System replicators and object uploads/downloads operate on partitions. As "
-"the system scales up, its behavior continues to be predictable because the "
-"number of partitions is a fixed number."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml163(para)
-msgid ""
-"Implementing a partition is conceptually simple, a partition is just a "
-"directory sitting on a disk with a corresponding hash table of what it "
-"contains."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml175(title)
-msgid "Replicators"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml176(para)
-msgid ""
-"In order to ensure that there are three copies of the data everywhere, "
-"replicators continuously examine each partition. For each local partition, "
-"the replicator compares it against the replicated copies in the other zones "
-"to see if there are any differences."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml180(para)
-msgid ""
-"The replicator knows if replication needs to take place by examining hashes."
-" A hash file is created for each partition, which contains hashes of each "
-"directory in the partition. Each of the three hash files is compared. For a "
-"given partition, the hash files for each of the partition's copies are "
-"compared. If the hashes are different, then it is time to replicate, and the"
-" directory that needs to be replicated is copied over."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml186(para)
-msgid ""
-"This is where partitions come in handy. With fewer things in the system, "
-"larger chunks of data are transferred around (rather than lots of little TCP"
-" connections, which is inefficient) and there is a consistent number of "
-"hashes to compare."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml189(para)
-msgid ""
-"The cluster eventually has a consistent behavior where the newest data has a"
-" priority."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml199(para)
-msgid ""
-"If a zone goes down, one of the nodes containing a replica notices and "
-"proactively copies data to a handoff location."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml203(title)
-msgid "Use cases"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml204(para)
-msgid ""
-"The following sections show use cases for object uploads and downloads and "
-"introduce the components."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml206(title)
-msgid "Upload"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml207(para)
-msgid ""
-"A client uses the REST API to make a HTTP request to PUT an object into an "
-"existing container. The cluster receives the request. First, the system must"
-" figure out where the data is going to go. To do this, the account name, "
-"container name, and object name are all used to determine the partition "
-"where this object should live."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml211(para)
-msgid ""
-"Then a lookup in the ring figures out which storage nodes contain the "
-"partitions in question."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml213(para)
-msgid ""
-"The data is then sent to each storage node where it is placed in the "
-"appropriate partition. At least two of the three writes must be successful "
-"before the client is notified that the upload was successful."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml216(para)
-msgid ""
-"Next, the container database is updated asynchronously to reflect that there"
-" is a new object in it."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml219(title)
-msgid "Object Storage in use"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-components.xml228(title)
-msgid "Download"
-msgstr "ダウンロード"
-
-#: ./doc/common/section_objectstorage-components.xml229(para)
-msgid ""
-"A request comes in for an account/container/object. Using the same "
-"consistent hashing, the partition name is generated. A lookup in the ring "
-"reveals which storage nodes contain that partition. A request is made to one"
-" of the storage nodes to fetch the object and, if that fails, requests are "
-"made to the other nodes."
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml10(title)
-msgid "Storage concepts"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml11(para)
-msgid "The OpenStack stack uses the following storage types:"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml13(caption)
-msgid "Storage types"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml19(td)
-msgid "On-instance / ephemeral"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml20(td)
-msgid "Block storage (cinder)"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml26(td)
-msgid "Runs operating systems and provides scratch space"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml27(td)
-msgid ""
-"Used for adding additional persistent storage to a virtual machine (VM)"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml29(td)
-msgid "Used for storing virtual machine images and data"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml32(td)
-msgid "Persists until VM is terminated"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml33(td)
-#: ./doc/common/section_storage-concepts.xml34(td)
-msgid "Persists until deleted"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml37(td)
-#: ./doc/common/section_storage-concepts.xml38(td)
-msgid "Access associated with a VM"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml39(td)
-msgid "Available from anywhere"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml42(td)
-msgid "Implemented as a filesystem underlying OpenStack Compute"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml44(td)
-msgid ""
-"Mounted via OpenStack Block Storage controlled protocol (for example, iSCSI)"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml46(td)
-msgid "REST API"
-msgstr "REST API"
-
-#: ./doc/common/section_storage-concepts.xml49(td)
-msgid "Administrator configures size setting, based on flavors"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml51(td)
-msgid "Sizings based on need"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml52(td)
-msgid "Easily scalable for future growth"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml55(td)
-msgid "Example: 10GB first disk, 30GB/core second disk"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml56(td)
-msgid "Example: 1TB \"extra hard drive\""
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml57(td)
-msgid "Example: 10s of TBs of data set storage"
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml64(para)
-msgid ""
-"<emphasis>You cannot use OpenStack Object Storage like a traditional hard "
-"drive.</emphasis> The Object Storage relaxes some of the constraints of a "
-"POSIX-style file system to get other gains. You can access the objects "
-"through an API which uses HTTP. Subsequently you don't have to provide "
-"atomic operations (that is, relying on eventual consistency), you can scale "
-"a storage system easily and avoid a central point of failure."
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml73(para)
-msgid ""
-"<emphasis>The OpenStack Image Service is used to manage the virtual machine "
-"images in an OpenStack cluster, not store them.</emphasis> It provides an "
-"abstraction to different methods for storage - a bridge to the storage, not "
-"the storage itself."
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml80(para)
-msgid ""
-"<emphasis>The OpenStack Object Storage can function on its own.</emphasis> "
-"The Object Storage (swift) product can be used independently of the Compute "
-"(nova) product."
-msgstr ""
-
-#: ./doc/common/section_storage-concepts.xml62(para)
-msgid "You should note that:<placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml6(title)
-msgid "Launch instances"
-msgstr "インスタンスの起動"
-
-#: ./doc/common/section_cli_nova_boot.xml7(para)
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml8(para)
-msgid "Instances are virtual machines that run inside the cloud."
-msgstr "インスタンスはクラウド内で動作する仮想マシンです。"
-
-#: ./doc/common/section_cli_nova_boot.xml9(para)
-msgid "Before you can launch an instance, gather the following parameters:"
-msgstr "インスタンスを起動する前に、以下のパラメーターの情報を集めます。"
-
-#: ./doc/common/section_cli_nova_boot.xml13(para)
-msgid ""
-"The <emphasis role=\"bold\">instance source</emphasis> can be an image, "
-"snapshot, or block storage volume that contains an image or snapshot."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml18(para)
-msgid "A <emphasis role=\"bold\">name</emphasis> for your instance."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml21(para)
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml37(para)
-msgid ""
-"The <emphasis role=\"bold\">flavor</emphasis> for your instance, which "
-"defines the compute, memory, and storage capacity of nova computing "
-"instances. A flavor is an available hardware configuration for a server. It "
-"defines the size of a virtual server that can be launched."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml29(para)
-msgid ""
-"Any <emphasis role=\"bold\">user data</emphasis> files. A user data file is "
-"a special key in the metadata service that holds a file that cloud-aware "
-"applications in the guest instance can access. For example, one application "
-"that uses user data is the <link "
-"href=\"https://help.ubuntu.com/community/CloudInit\">cloud-init</link> "
-"system, which is an open-source package from Ubuntu that is available on "
-"various Linux distributions and that handles early initialization of a cloud"
-" instance."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml42(para)
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml45(para)
-msgid ""
-"Access and security credentials, which include one or both of the following "
-"credentials:"
-msgstr "アクセス、セキュリティクレデンシャル。以下のクレデンシャルの 1 つまたは両方が含まれます。"
-
-#: ./doc/common/section_cli_nova_boot.xml46(para)
-msgid ""
-"A <emphasis role=\"bold\">key pair</emphasis> for your instance, which are "
-"SSH credentials that are injected into images when they are launched. For "
-"the key pair to be successfully injected, the image must contain the "
-"<literal>cloud-init</literal> package. Create at least one key pair for each"
-" project. If you already have generated a key pair with an external tool, "
-"you can import it into OpenStack. You can use the key pair for multiple "
-"instances that belong to that project."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml60(para)
-msgid ""
-"A <emphasis role=\"bold\">security group</emphasis> that defines which "
-"incoming network traffic is forwarded to instances. Security groups hold a "
-"set of firewall policies, known as <emphasis role=\"italic\">security group "
-"rules</emphasis>."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml71(para)
-msgid ""
-"If needed, you can assign a <emphasis role=\"bold\">floating (public) IP "
-"address</emphasis> to a running instance."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml76(para)
-msgid ""
-"You can also attach a block storage device, or <emphasis "
-"role=\"bold\">volume</emphasis>, for persistent storage."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml82(para)
-msgid ""
-"Instances that use the default security group cannot, by default, be "
-"accessed from any IP address outside of the cloud. If you want those IP "
-"addresses to access the instances, you must modify the rules for the default"
-" security group."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml87(para)
-msgid ""
-"You can also assign a floating IP address to a running instance to make it "
-"accessible from outside the cloud. See <xref "
-"linkend=\"manage_ip_addresses\"/>."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml91(para)
-msgid ""
-"After you gather the parameters that you need to launch an instance, you can"
-" launch it from an <link linkend=\"launch_from_image\">image</link> or a "
-"<link linkend=\"boot_from_volume\">volume</link>. You can launch an instance"
-" directly from one of the available OpenStack images or from an image that "
-"you have copied to a persistent volume. The OpenStack Image Service provides"
-" a pool of images that are accessible to members of different projects."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml101(title)
-msgid "Gather parameters to launch an instance"
-msgstr "インスタンスを起動するためのパラメーター情報の収集"
-
-#: ./doc/common/section_cli_nova_boot.xml103(para)
-msgid "Before you begin, source the OpenStack RC file."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml108(para)
-msgid "Note the ID of the flavor that you want to use for your instance:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml123(para)
-msgid "Note the ID of the image from which you want to boot your instance:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml131(para)
-msgid ""
-"You can also filter the image list by using <placeholder-1/> to find a "
-"specific image, as follows:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml138(para)
-msgid "List the available security groups:"
-msgstr "利用可能なセキュリティグループを表示します。"
-
-#: ./doc/common/section_cli_nova_boot.xml140(para)
-msgid ""
-"If you are an admin user, specify the <option>--all-tenants</option> "
-"parameter to list groups for all tenants."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml145(para)
-msgid ""
-"Note the ID of the security group that you want to use for your instance:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml151(para)
-msgid ""
-"If you have not created any security groups, you can assign the instance to "
-"only the default security group."
-msgstr "セキュリティグループを作成していない場合、Default のセキュリティグループのみにインスタンスを割り当てることができます。"
-
-#: ./doc/common/section_cli_nova_boot.xml154(para)
-msgid "You can view rules for a specified security group:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml159(para)
-msgid ""
-"List the available key pairs and note the name of the key pair that you use "
-"for SSH access."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml168(title)
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml6(title)
-msgid "Launch an instance from an image"
-msgstr "イメージからのインスタンスの起動"
-
-#: ./doc/common/section_cli_nova_boot.xml171(para)
-msgid ""
-"After you gather required parameters, run the following command to launch an"
-" instance. Specify the server name, flavor ID, and image ID."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml174(para)
-msgid ""
-"Optionally, you can provide a key name for access control and a security "
-"group for security. You can also include metadata key and value pairs. For "
-"example, you can add a description for your server by providing the "
-"<parameter>--meta description=\"My Server\"</parameter> parameter."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml181(para)
-msgid ""
-"You can pass user data in a local file at instance launch by using the "
-"<parameter>--user-data <replaceable>USER-DATA-FILE</replaceable></parameter>"
-" parameter."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml186(replaceable)
-msgid "FLAVOR_ID"
-msgstr "FLAVOR_ID"
-
-#: ./doc/common/section_cli_nova_boot.xml186(replaceable)
-msgid "KEY_NAME"
-msgstr "KEY_NAME"
-
-#: ./doc/common/section_cli_nova_boot.xml187(replaceable)
-msgid "USER_DATA_FILE"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml187(replaceable)
-msgid "SEC_GROUP"
-msgstr "SEC_GROUP"
-
-#: ./doc/common/section_cli_nova_boot.xml187(replaceable)
-msgid "KEY=VALUE"
-msgstr "KEY=VALUE"
-
-#: ./doc/common/section_cli_nova_boot.xml189(para)
-msgid ""
-"The following command launches the <literal>MyCirrosServer</literal> "
-"instance with the <literal>m1.small</literal> flavor (ID of "
-"<literal>1</literal>), <literal>cirros-0.3.2-x86_64-uec</literal> image (ID "
-"of <literal>397e713c-b95b-4186-ad46-6126863ea0a9</literal>), "
-"<literal>default</literal> security group, <literal>KeyPair01</literal> key,"
-" and a user data file called <filename>cloudinit.file</filename>:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml202(replaceable)
-msgid "myCirrosServer"
-msgstr "myCirrosServer"
-
-#: ./doc/common/section_cli_nova_boot.xml203(para)
-msgid ""
-"Depending on the parameters that you provide, the command returns a list of "
-"server properties."
-msgstr "指定のパラメーターにより、コマンドはサーバーのプロパティ一覧を返します。"
-
-#: ./doc/common/section_cli_nova_boot.xml206(para)
-msgid ""
-"A status of <literal>BUILD</literal> indicates that the instance has "
-"started, but is not yet online."
-msgstr "<literal>BUILD</literal> の状態は、インスタンスが起動しているがオンラインにはなっていないことを示しています。"
-
-#: ./doc/common/section_cli_nova_boot.xml209(para)
-msgid ""
-"A status of <literal>ACTIVE</literal> indicates that the instance is active."
-msgstr "<literal>ACTIVE</literal> の状態は、インスタンスがアクティブであることを示しています。"
-
-#: ./doc/common/section_cli_nova_boot.xml241(para)
-msgid ""
-"Copy the server ID value from the <literal>id</literal> field in the output."
-" You use this ID to get details for or delete your server."
-msgstr "出力の <literal>id</literal> フィールドからサーバー ID の値をコピーします。この ID を使用して詳細を取得するか、サーバーを削除します。"
-
-#: ./doc/common/section_cli_nova_boot.xml245(para)
-msgid ""
-"Copy the administrative password value from the <literal>adminPass</literal>"
-" field. You use this value to log in to your server."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml249(para)
-msgid ""
-"You can also place arbitrary local files into the instance file system at "
-"creation time by using the <option>--file &lt;dst-path=src-path&gt;</option>"
-" option. You can store up to five files. For example, if you have a special "
-"authorized keys file named <filename>special_authorized_keysfile</filename> "
-"that you want to put on the instance rather than using the regular SSH key "
-"injection, you can use the <option>--file</option> option as shown in the "
-"following example:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml266(para)
-msgid "Check if the instance is online:"
-msgstr "インスタンスがオンラインになっているかどうかをチェックします。"
-
-#: ./doc/common/section_cli_nova_boot.xml268(para)
-msgid ""
-"The list shows the ID, name, status, and private (and if assigned, public) "
-"IP addresses for all instances in the project to which you belong:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_boot.xml278(para)
-msgid "If the status for the instance is ACTIVE, the instance is online."
-msgstr "インスタンスの状態が ACTIVE の場合、インスタンスはオンラインです。"
-
-#: ./doc/common/section_cli_nova_boot.xml280(para)
-msgid ""
-"To view the available options for the <placeholder-1/> command, run the "
-"following command:"
-msgstr "<placeholder-1/> コマンドで利用可能なオプションを確認するには、以下のコマンドを実行します。"
-
-#: ./doc/common/section_cli_nova_boot.xml287(para)
-msgid ""
-"If you did not provide a key pair, security groups, or rules, you can access"
-" the instance only from inside the cloud through VNC. Even pinging the "
-"instance is not possible."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml6(title)
-msgid "Integrate Identity with LDAP"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml7(para)
-msgid ""
-"Identity Service supports integration with an existing LDAP directory for "
-"authentication and authorization services."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml11(para)
-msgid ""
-"For OpenStack Identity to access an LDAP back end, you must enable the "
-"<option>authlogin_nsswitch_use_ldap</option> boolean value for SELinux on "
-"the Identity server. To enable and make the option persistent across "
-"reboots:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml18(para)
-msgid "You can integrate Identity with a single LDAP server."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml21(para)
-msgid ""
-"To configure Identity, set options in the "
-"<filename>/etc/keystone/keystone.conf</filename> file. Modify these examples"
-" as needed."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml25(title)
-msgid "To integrate Identity with LDAP"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml27(para)
-msgid "Enable the LDAP driver in the <filename>keystone.conf</filename> file:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml34(para)
-msgid ""
-"Define the destination LDAP server in the <filename>keystone.conf</filename>"
-" file:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml45(para)
-msgid ""
-"Create the organizational units (OU) in the LDAP directory, and define their"
-" corresponding location in the <filename>keystone.conf</filename> file:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml58(para)
-msgid ""
-"These schema attributes are extensible for compatibility with various "
-"schemas. For example, this entry maps to the <systemitem>person</systemitem>"
-" attribute in Active Directory:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml67(para)
-msgid ""
-"A read-only implementation is recommended for LDAP integration. These "
-"permissions are applied to object types in the "
-"<filename>keystone.conf</filename> file:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml85(para)
-msgid "Restart the Identity service:"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml87(para)
-msgid ""
-"During service restart, authentication and authorization are unavailable."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml92(title)
-msgid "Additional LDAP integration settings"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml93(para)
-msgid "Set these options in the <filename>keystone.conf</filename> file."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml98(term)
-msgid "Filters"
-msgstr "フィルター"
-
-#: ./doc/common/section_keystone_config_ldap.xml100(para)
-msgid "Use filters to control the scope of data presented through LDAP."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml109(term)
-msgid "LDAP Account Status"
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml111(para)
-msgid ""
-"Mask account status values for compatibility with various directory "
-"services. Superfluous accounts are filtered with "
-"<systemitem>user_filter</systemitem>."
-msgstr ""
-
-#: ./doc/common/section_keystone_config_ldap.xml115(para)
-msgid ""
-"For example, you can mask Active Directory account status attributes in the "
-"<filename>keystone.conf</filename> file:"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml106(None)
-msgid ""
-"@@image: 'figures/launch_instances.png'; "
-"md5=8a7e6864bce97f6478db572daf3ef5de"
-msgstr "@@image: 'figures/launch_instances.png'; md5=8a7e6864bce97f6478db572daf3ef5de"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml164(None)
-msgid "@@image: 'figures/instances.png'; md5=6b0f5cb3009d447334ff8b5c5b2cd121"
-msgstr "@@image: 'figures/instances.png'; md5=6b0f5cb3009d447334ff8b5c5b2cd121"
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml10(para)
-msgid ""
-"You can launch an instance directly from one of the available OpenStack "
-"images. The OpenStack Image Service provides a pool of images that are "
-"accessible to members of different projects. When you launch an instance "
-"from an image, OpenStack creates a local copy of the image on the respective"
-" compute node where the instance is started."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml16(para)
-msgid ""
-"Alternatively, you can launch an instance from an image that you have copied"
-" to a persistent volume."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml18(para)
-msgid "To launch an instance, specify the following parameters:"
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml22(para)
-msgid ""
-"The <guilabel>instance source</guilabel>, which is an image or snapshot. "
-"Alternatively, you can boot from a volume, which is block storage, to which "
-"you've copied an image or snapshot."
-msgstr "<guilabel>インスタンスソース</guilabel>。イメージまたはスナップショット。または、インスタンスまたはスナップショットをコピーしたブロックストレージ、つまりボリュームからブートすることができます。"
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml28(para)
-msgid ""
-"The <guilabel>image</guilabel> or <guilabel>snapshot</guilabel>, which "
-"represents the operating system."
-msgstr "<guilabel>イメージ</guilabel>または<guilabel>スナップショット</guilabel>。オペレーティングシステムを指します。"
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml33(para)
-msgid "A <guilabel>name</guilabel> for your instance."
-msgstr "インスタンスの<guilabel>名前</guilabel>。"
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml49(para)
+#: ./doc/common/section_cli_glance_manage_images.xml22(para)
 msgid ""
-"A <emphasis role=\"bold\">keypair</emphasis> for your instance, which are "
-"SSH credentials that are injected into images when they are launched. For "
-"this to work, the image must contain the <literal>cloud-init</literal> "
-"package. Create at least one keypair for each project. If you already have "
-"generated a keypair with an external tool, you can import it into OpenStack."
-" You can use the keypair for multiple instances that belong to that project."
-msgstr "インスタンスの<emphasis role=\"bold\">キーペア</emphasis>。イメージ起動時にイメージに注入される SSH 認証情報です。キーペアを機能させるには、イメージに <literal>cloud-init</literal> パッケージがインストールされている必要があります。プロジェクトごとにキーペアを最低でも 1 つ作成します。すでに外部のツールでキーペアを生成している場合は、OpenStack にそのキーペアをインポートすることができます。プロジェクトに所属する複数のインスタンスに対して、キーペアを使用することができます。"
+"To get a list of images and to then get further details about a single "
+"image, use <placeholder-1/> and <placeholder-2/>."
+msgstr "イメージの一覧を取得し、イメージ 1 つの詳細を取得するために、<placeholder-1/> および <placeholder-2/> を使用します。"
 
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml62(para)
+#: ./doc/common/section_cli_glance_manage_images.xml74(para)
 msgid ""
-"A <emphasis role=\"bold\">security group</emphasis>, which defines which "
-"incoming network traffic is forwarded to instances. Security groups hold a "
-"set of firewall policies, known as <emphasis role=\"italic\">security group "
-"rules</emphasis>."
-msgstr "<emphasis role=\"bold\">セキュリティグループ</emphasis>。どの受信ネットワークトラフィックがインスタンスに転送されるのかを定義します。セキュリティグループは、<emphasis role=\"italic\">セキュリティグループルール</emphasis>と呼ばれるファイアウォールポリシーを保持しています。"
+"When viewing a list of images, you can also use <placeholder-1/> to filter "
+"the list, as follows:"
+msgstr "イメージの一覧を表示するとき、以下のとおり、一覧をフィルターするために <placeholder-1/> を使用することもできます。"
 
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml73(para)
+#: ./doc/common/section_cli_glance_manage_images.xml80(para)
 msgid ""
-"If needed, you can assign a <emphasis role=\"bold\">floating (public) IP "
-"address</emphasis> to a running instance and attach a block storage device, "
-"or volume, for persistent storage."
-msgstr "必要であれば、<emphasis role=\"bold\">Floating IP (パブリック IP) アドレス</emphasis>を実行中のインスタンスに割り当てて、永続ストレージにブロックストレージまたはボリュームを接続することができます。"
+"To store location metadata for images, which enables direct file access for "
+"a client, update the <filename>/etc/glance/glance.conf</filename> file with "
+"the following statements:"
+msgstr "イメージの場所のメタデータを保存してクライアントが直接ファイルにアクセスできるようにするには、<filename>/etc/glance/glance.conf</filename> ファイルで以下のステートメントを追加更新します。"
 
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml80(title)
-msgid "To launch an instance:"
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml87(code)
+msgid "show_multiple_locations = True"
+msgstr "show_multiple_locations = True"
 
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml82(para)
-msgid "Log in to the OpenStack dashboard."
-msgstr "OpenStack Dashboard にログインします。"
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml85(para)
-msgid ""
-"If you are a member of multiple projects, select a project from the drop-"
-"down list at the top of the <guilabel>Project</guilabel> tab."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml90(para)
-msgid "Click the <guilabel>Images &amp; Snapshot</guilabel> category."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml92(para)
-msgid ""
-"The dashboard shows the images that have been uploaded to OpenStack Image "
-"Service and are available for this project."
-msgstr "ダッシュボードは OpenStack Image Service にアップロードされ、このプロジェクトに利用可能なイメージを表示します。"
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml100(title)
-msgid "OpenStack dashboard - Launch Instances window"
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml97(para)
-msgid ""
-"Select an image and click <guibutton>Launch</guibutton>. The "
-"<guilabel>Launch Image</guilabel> window appears: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml112(para)
-msgid "Specify the following parameters:"
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml116(para)
-msgid "Enter an instance name to assign to the virtual machine."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml120(para)
-msgid ""
-"From the <guilabel>Flavor</guilabel> drop-down list, select the size of the "
-"virtual machine to launch."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml125(para)
-msgid "Optionally, select a keypair."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml126(para)
-msgid ""
-"In case an image uses a static root password or a static key set (neither is"
-" recommended), you do not need to provide a keypair on starting the "
-"instance."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml132(para)
-msgid ""
-"In <guilabel>Instance Count</guilabel>, enter the number of virtual machines"
-" to launch from this image."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml137(para)
-msgid ""
-"Assign the instance to the default security group. If you added rules to "
-"this group, the instance implements these rules."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml150(para)
-msgid ""
-"Click <guibutton>Launch Instance</guibutton>. The instance is launched on "
-"any of the compute nodes in the cloud."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml155(para)
-msgid ""
-"After you have launched an instance, switch to the <guilabel>Instances &amp;"
-" Volumes</guilabel> category to view the instance name, its (private or "
-"public) IP address, size, status, task, and power state."
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml160(title)
-msgid "OpenStack dashboard - Instances"
-msgstr ""
-
-#: ./doc/common/section_dashboard_launch_instances_from_image.xml168(para)
-msgid ""
-"If you did not provide a keypair on starting and have not touched security "
-"groups or rules so far, by default the instance can only be accessed from "
-"inside the cloud through VNC at this point. Even pinging the instance is not"
-" possible."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml6(title)
-msgid "Troubleshoot the Identity service"
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml7(para)
-msgid ""
-"To troubleshoot the Identity service, review the logs in the "
-"<filename>/var/log/keystone/keystone.log</filename> file."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml10(para)
-msgid ""
-"Use the <filename>/etc/keystone/logging.conf</filename> file to configure "
-"the location of log files."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml13(para)
+#: ./doc/common/section_cli_glance_manage_images.xml90(para)
 msgid ""
-"The logs show the components that have come in to the WSGI request, and "
-"ideally show an error that explains why an authorization request failed. If "
-"you do not see the request in the logs, run keystone with "
-"<parameter>--debug</parameter> parameter. Pass the "
-"<parameter>--debug</parameter> parameter before the command parameters."
-msgstr ""
+"<code>filesystem_store_metadata_file = "
+"<replaceable>filePath</replaceable></code>, where "
+"<replaceable>filePath</replaceable> points to a JSON file that defines the "
+"mount point for OpenStack images on your system and a unique ID. For "
+"example: <placeholder-1/>"
+msgstr "<code>filesystem_store_metadata_file = <replaceable>filePath</replaceable></code>。<replaceable>filePath</replaceable> は、お使いのシステムの OpenStack イメージのマウントポイントを定義する JSON ファイルおよび一意な ID を参照するようにします。例: <placeholder-1/>"
 
-#: ./doc/common/section_identity-troubleshooting.xml20(title)
-msgid "Debug PKI middleware"
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml21(para)
-msgid ""
-"If you receive an <literal>Invalid OpenStack Identity Credentials</literal> "
-"message when you talk to an OpenStack service, it might be caused by the "
-"changeover from UUID tokens to PKI tokens in the Grizzly release. Learn how "
-"to troubleshoot this error."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml26(para)
-msgid ""
-"The PKI-based token validation scheme relies on certificates from Identity "
-"that are fetched through HTTP and stored in a local directory. The location "
-"for this directory is specified by the <literal>signing_dir</literal> "
-"configuration option. In your services configuration file, look for a "
-"section like this:"
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml41(para)
-msgid ""
-"If your service lacks this stanza, the <link "
-"href=\"https://github.com/openstack/python-"
-"keystoneclient/blob/master/keystoneclient/middleware/auth_token.py#L198\">keystoneclient/middleware/auth_token.py</link>"
-" file specifies the defaults. If no value is specified for this directory, "
-"it <link href=\"https://github.com/openstack/python-"
-"keystoneclient/blob/master/keystoneclient/middleware/auth_token.py#L299\">defaults"
-" to a secure temporary directory.</link> Initialization code for the service"
-" checks that the directory exists and is writable. If it does not exist, the"
-" code tries to create it. If this fails, the service fails to start. "
-"However, it often succeeds but problems occur later."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml53(para)
-msgid ""
-"The first thing to check is that the <literal>signing_dir</literal> does, in"
-" fact, exist. If it does, check for the presence of the certificate files "
-"inside there:"
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml64(para)
-msgid ""
-"This directory contains two certificates and the token revocation list. If "
-"these files are not present, your service cannot fetch them from Identity. "
-"To troubleshoot, try to talk to Identity to make sure it correctly serves "
-"files, as follows:"
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml70(para)
-msgid "This command fetches the signing certificate:"
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml81(para)
-msgid "Note the expiration dates of the certificate:"
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml84(para)
-msgid ""
-"The token revocation list is updated once a minute, but the certificates are"
-" not. One possible problem is that the certificates are the wrong files or "
-"garbage. You can remove these files and run another command against your "
-"server: They are fetched on demand."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml89(para)
-msgid ""
-"The Identity service log should show the access of the certificate files. "
-"You might have to turn up your logging levels. Set <literal>debug = "
-"True</literal> and <literal>verbose = True</literal> in your Identity "
-"configuration file and restart the Identity server."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml98(para)
-msgid ""
-"If the files do not appear in your directory after this, it is likely one of"
-" the following issues:"
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml102(para)
-msgid ""
-"Your service is configured incorrectly and cannot talk to Identity. Check "
-"the <literal>auth_port</literal> and <literal>auth_host</literal> values and"
-" make sure that you can talk to that service through cURL, as shown "
-"previously."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml110(para)
-msgid ""
-"Your signing directory is not writable. Use the <placeholder-1/> command to "
-"change its permissions so that the service (POSIX) user can write to it. "
-"Verify the change through <placeholder-2/> and <placeholder-3/> commands."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml118(para)
-msgid "The SELinux policy is denying access to the directory."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml122(para)
+#: ./doc/common/section_cli_glance_manage_images.xml102(para)
 msgid ""
-"SELinux troubles often occur when you use Fedora/RHEL-based packages and you"
-" choose configuration options that do not match the standard policy. Run the"
-" <placeholder-1/> command. If that makes a difference, you should relabel "
-"the directory. If you are using a sub-directory of the "
-"<filename>/var/cache/</filename> directory, run the following command:"
-msgstr ""
+"After you restart the Image Service, you can use the following syntax to "
+"view the image's location information:"
+msgstr "Image Service を再起動してから、以下の構文を使用してイメージの場所情報を確認します。"
 
-#: ./doc/common/section_identity-troubleshooting.xml131(para)
-msgid ""
-"If you are not using a <filename>/var/cache</filename> sub-directory, you "
-"should. Modify the <literal>signing_dir</literal> configuration option for "
-"your service and restart."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml135(para)
-msgid ""
-"Set back to <literal>setenforce enforcing</literal> to confirm that your "
-"changes solve the problem."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml137(para)
-msgid ""
-"If your certificates are fetched on demand, the PKI validation is working "
-"properly. Most likely, the token from Identity is not valid for the "
-"operation you are attempting to perform, and your user needs a different "
-"role for the operation."
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml144(title)
-msgid "Debug signing key file errors"
-msgstr ""
-
-#: ./doc/common/section_identity-troubleshooting.xml145(para)
-msgid ""
-"If an error occurs when the signing key file opens, it is possible that the "
-"person who ran the <placeholder-1/> command to generate certificates and "
-"keys did not use the correct user. When you run the <placeholder-2/> "
-"command, Identity generates a set of certificates and keys in "
-"<filename>/etc/keystone/ssl*</filename>, which is owned by root:root."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml103(replaceable)
+msgid "imageID"
+msgstr "imageID"
 
-#: ./doc/common/section_identity-troubleshooting.xml154(para)
+#: ./doc/common/section_cli_glance_manage_images.xml104(para)
 msgid ""
-"This can present a problem when you run the Identity daemon under the "
-"keystone user account (nologin) when you try to run PKI. Unless you run the "
-"<placeholder-1/> command against the files keystone:keystone or run the "
-"<placeholder-2/> command with the <parameter>--keystone-user</parameter> and"
-" <parameter>--keystone-group</parameter> parameters, you get an error, as "
+"For example, using the image ID shown above, you would issue the command as "
 "follows:"
-msgstr ""
+msgstr "例えば、上に示したイメージ ID を使用して、以下のとおりコマンドを発行します。"
 
-#: ./doc/common/section_identity-troubleshooting.xml172(title)
-msgid "Flush expired tokens from the token database table"
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml109(title)
+msgid "Create or update an image (glance)"
+msgstr "イメージ (glance) の作成・更新"
 
-#: ./doc/common/section_identity-troubleshooting.xml174(para)
-msgid ""
-"As you generate tokens, the token database table on the Identity server "
-"grows. To clear the token table, an administrative user must run the "
-"<placeholder-1/> command to flush the tokens. When you flush tokens, expired"
-" tokens are deleted and traceability is eliminated."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml110(para)
+msgid "To create an image, use <placeholder-1/>:"
+msgstr "イメージを作成するために、<placeholder-1/> を使用します。"
 
-#: ./doc/common/section_identity-troubleshooting.xml180(para)
-msgid ""
-"Use <placeholder-1/> to schedule this command to run frequently based on "
-"your workload. For large workloads, running it every minute is recommended."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml111(replaceable)
+#: ./doc/common/section_cli_glance_manage_images.xml114(replaceable)
+msgid "imageName"
+msgstr "imageName"
 
-#: ./doc/common/section_compute_config-firewalls.xml6(title)
-msgid "Compute service node firewall requirements"
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml112(para)
+msgid "To update an image by name or ID, use <placeholder-1/>:"
+msgstr "名前または ID によりイメージを更新するために、<placeholder-1/> を使用します。"
 
-#: ./doc/common/section_compute_config-firewalls.xml7(para)
+#: ./doc/common/section_cli_glance_manage_images.xml116(para)
 msgid ""
-"Console connections for virtual machines, whether direct or through a proxy,"
-" are received on ports <literal>5900</literal> to <literal>5999</literal>. "
-"You must configure the firewall on each Compute service node to enable "
-"network traffic on these ports."
+"The following table lists the optional arguments that you can use with the "
+"<placeholder-1/> and <placeholder-2/> commands to modify image properties. "
+"For more information, refer to Image Service chapter in the <link "
+"href=\"http://docs.openstack.org/cli-"
+"reference/content/index.html\">OpenStack Command-Line Interface "
+"Reference</link>."
 msgstr ""
 
-#: ./doc/common/section_compute_config-firewalls.xml11(title)
-msgid "Configure the service-node firewall"
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml126(parameter)
+msgid "--name NAME"
+msgstr "--name NAME"
 
-#: ./doc/common/section_compute_config-firewalls.xml12(para)
-msgid ""
-"On the server that hosts the Compute service, log in as "
-"<systemitem>root</systemitem>."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml129(para)
+msgid "The name of the image."
+msgstr "イメージの名前。"
 
-#: ./doc/common/section_compute_config-firewalls.xml14(para)
-msgid "Edit the <filename>/etc/sysconfig/iptables</filename> file."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml134(parameter)
+msgid "--disk-format DISK_FORMAT"
+msgstr "--disk-format DISK_FORMAT"
 
-#: ./doc/common/section_compute_config-firewalls.xml20(para)
+#: ./doc/common/section_cli_glance_manage_images.xml137(para)
 msgid ""
-"Add an INPUT rule that allows TCP traffic on ports that range from "
-"<literal>5900</literal> to <literal>5999</literal>:"
-msgstr ""
+"The disk format of the image. Acceptable formats are ami, ari, aki, vhd, "
+"vmdk, raw, qcow2, vdi, and iso."
+msgstr "イメージのディスク形式。利用可能な形式は ami、ari、aki、vhd、vmdk、raw、qcow2、vdi、iso です。"
 
-#: ./doc/common/section_compute_config-firewalls.xml26(para)
-msgid "The new rule must appear before any INPUT rules that REJECT traffic."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml143(parameter)
+msgid "--container-format CONTAINER_FORMAT"
+msgstr "--container-format CONTAINER_FORMAT"
 
-#: ./doc/common/section_compute_config-firewalls.xml32(para)
+#: ./doc/common/section_cli_glance_manage_images.xml146(para)
 msgid ""
-"Save the changes to the <filename>/etc/sysconfig/iptables</filename> file."
-msgstr ""
+"The container format of the image. Acceptable formats are ami, ari, aki, "
+"bare, and ovf."
+msgstr "イメージのコンテナー形式。対応形式は ami、ari、aki、bare、ovf です。"
 
-#: ./doc/common/section_compute_config-firewalls.xml38(para)
-msgid ""
-"Restart the <systemitem>iptables</systemitem> service to ensure that the "
-"change takes effect."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml152(parameter)
+msgid "--owner TENANT_ID"
+msgstr "--owner TENANT_ID"
 
-#: ./doc/common/section_compute_config-firewalls.xml45(para)
-msgid ""
-"The <systemitem>iptables</systemitem> firewall now enables incoming "
-"connections to the Compute services. Repeat this process for each Compute "
-"service node."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml155(para)
+msgid "The tenant who should own the image."
+msgstr "イメージを所有するプロジェクト。"
 
-#: ./doc/common/section_dashboard_customizing.xml6(title)
-msgid "Customize the dashboard"
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml160(parameter)
+msgid "--size SIZE"
+msgstr "--size SIZE"
 
-#: ./doc/common/section_dashboard_customizing.xml7(para)
-msgid ""
-"Adapted from <link href=\"http://www.prestonlee.com/2012/05/09/how-to-"
-"custom-brand-the-openstack-horizon-dashboard/\">How To Custom Brand The "
-"OpenStack “Horizon” Dashboard</link>."
-msgstr ""
-
-#: ./doc/common/section_dashboard_customizing.xml11(para)
-msgid ""
-"You install the OpenStack dashboard through the <literal>openstack-"
-"dashboard</literal> package. You can customize the dashboard with your own "
-"colors, logo, and site title through a CSS file."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml163(para)
+msgid "The size of image data, in bytes."
+msgstr "イメージデータの容量。バイト単位。"
 
-#: ./doc/common/section_dashboard_customizing.xml15(para)
-msgid ""
-"Canonical also provides an <literal>openstack-dashboard-ubuntu-"
-"theme</literal> package that brands the Python-based Django interface."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml168(parameter)
+msgid "--min-disk DISK_GB"
+msgstr "--min-disk DISK_GB"
 
-#: ./doc/common/section_dashboard_customizing.xml47(para)
-msgid ""
-"Create a graphical logo with a transparent background. The text "
-"<literal>TGen Cloud</literal> in this example is rendered through "
-"<filename>.png</filename> files of multiple sizes created with a graphics "
-"program."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml171(para)
+msgid "The minimum size of the disk needed to boot the image, in gigabytes."
+msgstr "ブートイメージに必要となるディスクの最小容量。ギガバイト単位。"
 
-#: ./doc/common/section_dashboard_customizing.xml52(para)
-msgid ""
-"Use a 200×27 for the logged-in banner graphic, and 365×50 for the login "
-"screen graphic."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml177(parameter)
+msgid "--min-ram DISK_RAM"
+msgstr "--min-ram DISK_RAM"
 
-#: ./doc/common/section_dashboard_customizing.xml56(para)
-msgid ""
-"Set the HTML title, which appears at the top of the browser window, by "
-"adding the following line to <filename>/etc/openstack-"
-"dashboard/local_settings.py</filename>:"
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml180(para)
+msgid "The minimum amount of RAM needed to boot the image, in megabytes."
+msgstr "ブートイメージに必要となるメモリの最小容量。ギガバイト単位。"
 
-#: ./doc/common/section_dashboard_customizing.xml59(code)
-msgid "SITE_BRANDING = \"Example, Inc. Cloud\""
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml185(parameter)
+msgid "--location IMAGE_URL"
+msgstr "--location IMAGE_URL"
 
-#: ./doc/common/section_dashboard_customizing.xml63(para)
+#: ./doc/common/section_cli_glance_manage_images.xml188(para)
 msgid ""
-"Upload your new graphic files to the following location: "
-"<filename>/usr/share/openstack-"
-"dashboard/openstack_dashboard/static/dashboard/img/</filename>"
-msgstr ""
+"The URL where the data for this image resides. For example, if the image "
+"data is stored in swift, you could specify "
+"<literal>swift://account:key@example.com/container/obj</literal>."
+msgstr "このイメージのデータが格納されている URL。例えば、イメージデータが swift に格納されている場合 <literal>swift://account:key@example.com/container/obj</literal> を指定します。"
 
-#: ./doc/common/section_dashboard_customizing.xml68(para)
-msgid ""
-"Create a CSS style sheet in the following directory: <filename>/usr/share"
-"/openstack-dashboard/openstack_dashboard/static/dashboard/css/</filename>"
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml195(parameter)
+msgid "--file FILE"
+msgstr "--file FILE"
 
-#: ./doc/common/section_dashboard_customizing.xml72(para)
+#: ./doc/common/section_cli_glance_manage_images.xml198(para)
 msgid ""
-"Edit your CSS file to override the Ubuntu customizations in the "
-"<filename>ubuntu.css</filename> file."
-msgstr ""
+"Local file that contains the disk image to be uploaded during the update. "
+"Alternatively, you can pass images to the client through stdin."
+msgstr "更新中にアップロードするディスクイメージを含むローカルファイル。または、標準入力からクライアントにイメージを渡すことができます。"
 
-#: ./doc/common/section_dashboard_customizing.xml75(para)
-msgid ""
-"Change the colors and image file names as appropriate, though the relative "
-"directory paths should be the same. The following example file shows you how"
-" to customize your CSS file:"
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml204(parameter)
+msgid "--checksum CHECKSUM"
+msgstr "--checksum CHECKSUM"
 
-#: ./doc/common/section_dashboard_customizing.xml114(para)
-msgid ""
-"Open the following HTML template in an editor: <filename>/usr/share"
-"/openstack-"
-"dashboard/openstack_dashboard/templates/_stylesheets.html</filename>"
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml207(para)
+msgid "Hash of image data to use for verification."
+msgstr "イメージデータの検証に使用するハッシュ。"
 
-#: ./doc/common/section_dashboard_customizing.xml118(para)
-msgid "Add a line to include your <filename>custom.css</filename> file:"
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml212(parameter)
+msgid "--copy-from IMAGE_URL"
+msgstr "--copy-from IMAGE_URL"
 
-#: ./doc/common/section_dashboard_customizing.xml123(emphasis)
+#: ./doc/common/section_cli_glance_manage_images.xml215(para)
 msgid ""
-"&lt;link href='{{ STATIC_URL }}dashboard/css/custom.css' media='screen' "
-"rel='stylesheet' /&gt;"
-msgstr "&lt;link href='{{ STATIC_URL }}dashboard/css/custom.css' media='screen' rel='stylesheet' /&gt;"
+"Similar to <parameter>--location</parameter> in usage, but indicates that "
+"the image server should immediately copy the data and store it in its "
+"configured image store."
+msgstr "使用方法は <parameter>--location</parameter> に似ていますが、イメージサーバーはすぐにデータをコピーして設定済みのイメージストアに保存する必要があると指定します。"
 
-#: ./doc/common/section_dashboard_customizing.xml127(title)
-msgid "Restart Apache:"
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml222(parameter)
+msgid "--is-public [True|False]"
+msgstr "--is-public [True|False]"
 
-#: ./doc/common/section_dashboard_customizing.xml128(para)
-#: ./doc/common/section_dashboard_sessions.xml180(para)
-msgid "On Ubuntu: <placeholder-1/>"
-msgstr "Ubuntu の場合: <placeholder-1/>"
+#: ./doc/common/section_cli_glance_manage_images.xml225(para)
+msgid "Makes an image accessible for all the tenants."
+msgstr "イメージをすべてのテナントからアクセス可能にします。"
 
-#: ./doc/common/section_dashboard_customizing.xml131(para)
-msgid "On Fedora, RHEL, CentOS: <placeholder-1/>"
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml230(parameter)
+msgid "--is-protected [True|False]"
+msgstr "--is-protected [True|False]"
 
-#: ./doc/common/section_dashboard_customizing.xml134(para)
-#: ./doc/common/section_dashboard_sessions.xml187(para)
-msgid "On openSUSE: <placeholder-1/>"
-msgstr "openSUSE の場合: <placeholder-1/>"
-
-#: ./doc/common/section_dashboard_customizing.xml139(para)
-msgid "Reload the dashboard in your browser to view your changes."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml233(para)
+msgid "Prevents an image from being deleted."
+msgstr "イメージが削除されることを防ぎます。"
 
-#: ./doc/common/section_dashboard_customizing.xml141(para)
-msgid "Modify your CSS file as appropriate."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml238(parameter)
+msgid "--property KEY=VALUE"
+msgstr "--property KEY=VALUE"
 
-#: ./doc/common/section_cli_version.xml6(title)
-msgid "Discover the version number for a client"
-msgstr "クライアントのバージョン番号の確認"
-
-#: ./doc/common/section_cli_version.xml7(para)
-msgid "Run the following command to discover the version number for a client:"
-msgstr "クライアントのバージョン番号を確認するために、以下のコマンドを実行します。"
-
-#: ./doc/common/section_cli_version.xml9(replaceable)
-#: ./doc/common/section_cli_install.xml208(replaceable)
-#: ./doc/common/section_cli_install.xml210(replaceable)
-#: ./doc/common/section_cli_install.xml222(replaceable)
-#: ./doc/common/section_cli_install.xml228(replaceable)
-#: ./doc/common/section_cli_install.xml236(replaceable)
-#: ./doc/common/section_cli_install.xml239(replaceable)
-msgid "PROJECT"
-msgstr "PROJECT"
-
-#: ./doc/common/section_cli_version.xml10(para)
+#: ./doc/common/section_cli_glance_manage_images.xml241(para)
 msgid ""
-"For example, to see the version number for the <placeholder-1/> client, run "
-"the following command:"
-msgstr "例えば、<placeholder-1/> クライアントのバージョン番号を取得するために、以下のコマンドを実行します。"
-
-#: ./doc/common/section_cli_version.xml14(para)
-msgid "The version number (2.15.0 in the example) is returned."
-msgstr "バージョン番号 (この例は 2.15.0) が返されます。"
+"Arbitrary property to associate with image. This option can be used multiple"
+" times."
+msgstr "イメージと関連付ける任意のプロパティ。このオプションは複数回使用できます。"
 
-#: ./doc/common/section_keystone-concepts-group-management.xml6(title)
-msgid "Groups"
-msgstr "グループ"
+#: ./doc/common/section_cli_glance_manage_images.xml247(parameter)
+msgid "--purge-props"
+msgstr "--purge-props"
 
-#: ./doc/common/section_keystone-concepts-group-management.xml7(para)
+#: ./doc/common/section_cli_glance_manage_images.xml250(para)
 msgid ""
-"A group is a collection of users. Administrators can create groups and add "
-"users to them. Then, rather than assign a role to each user individually, "
-"assign a role to the group. Every group is in a domain. Groups were "
-"introduced with the Identity API v3."
-msgstr ""
-
-#. TODO: eventually remove the last sentence, when v3 is
-#.              commonplace
-#: ./doc/common/section_keystone-concepts-group-management.xml14(para)
-msgid "Identity API V3 provides the following group-related operations:"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml18(para)
-msgid "Create a group"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml21(para)
-msgid "Delete a group"
-msgstr ""
+"Deletes all image properties that are not explicitly set in the update "
+"request. Otherwise, those properties not referenced are preserved."
+msgstr "更新要求に明示的に設定されていないイメージのプロパティをすべて削除します。そうでない場合は、参照されていないプロパティは保存されます。"
 
-#: ./doc/common/section_keystone-concepts-group-management.xml24(para)
-msgid "Update a group (change its name or description)"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml28(para)
-msgid "Add a user to a group"
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml256(parameter)
+msgid "--human-readable"
+msgstr "--human-readable"
 
-#: ./doc/common/section_keystone-concepts-group-management.xml31(para)
-msgid "Remove a user from a group"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml34(para)
-msgid "List group members"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml37(para)
-msgid "List groups for a user"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml40(para)
-msgid "Assign a role on a tenant to a group"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml43(para)
-msgid "Assign a role on a domain to a group"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml46(para)
-msgid "Query role assignments to groups"
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml259(para)
+msgid "Prints the image size in a human-friendly format."
+msgstr "人間が理解しやすい形式でイメージの容量を表示します。"
 
-#: ./doc/common/section_keystone-concepts-group-management.xml50(para)
+#: ./doc/common/section_cli_glance_manage_images.xml263(para)
 msgid ""
-"The Identity service server might not allow all operations. For example, if "
-"using the Identity server with the LDAP Identity back end and group updates "
-"are disabled, then a request to create, delete, or update a group fails."
+"The following example shows the command that you would use to upload a "
+"CentOS 6.3 image in qcow2 format and configure it for public access:"
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts-group-management.xml56(para)
-msgid "Here are a couple of examples:"
-msgstr ""
-
-#: ./doc/common/section_keystone-concepts-group-management.xml59(para)
+#: ./doc/common/section_cli_glance_manage_images.xml267(para)
 msgid ""
-"Group A is granted Role A on Tenant A. If User A is a member of Group A, "
-"when User A gets a token scoped to Tenant A, the token also includes Role A."
+"The following example shows how to update an existing image with a "
+"properties that describe the disk bus, the CD-ROM bus, and the VIF model:"
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts-group-management.xml65(para)
+#: ./doc/common/section_cli_glance_manage_images.xml274(para)
 msgid ""
-"Group B is granted Role B on Domain B. If User B is a member of Domain B, if"
-" User B gets a token scoped to Domain B, the token also includes Role B."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml11(title)
-msgid "Orchestration command-line client"
+"Currently the libvirt virtualization tool determines the disk, CD-ROM, and "
+"VIF device models based on the configured hypervisor type "
+"(<literal>libvirt_type</literal> in "
+"<filename>/etc/nova/nova.conf</filename>). For the sake of optimal "
+"performance, libvirt defaults to using virtio for both disk and VIF (NIC) "
+"models. The disadvantage of this approach is that it is not possible to run "
+"operating systems that lack virtio drivers, for example, BSD, Solaris, and "
+"older versions of Linux and Windows."
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml12(para)
+#: ./doc/common/section_cli_glance_manage_images.xml280(para)
 msgid ""
-"The <placeholder-1/> client is the command-line interface (CLI) for the "
-"Orchestration API and its extensions. This chapter documents "
-"<placeholder-2/> version 0.2.9."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml22(title)
-msgid "heat usage"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml39(para)
-#: ./doc/common/ch_cli_heat_commands.xml506(para)
-msgid "Resume the stack."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml47(para)
-#: ./doc/common/ch_cli_heat_commands.xml523(para)
-msgid "Suspend the stack."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml55(para)
-#: ./doc/common/ch_cli_heat_commands.xml540(para)
-msgid "Retrieve build information."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml63(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use stack-create instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml71(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use stack-delete instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml79(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use stack-show instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml87(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use event-show instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml95(para)
-#: ./doc/common/ch_cli_heat_commands.xml547(para)
-msgid "List events for a stack."
-msgstr ""
+"If you specify a disk or CD-ROM bus model that is not supported, see <xref "
+"linkend=\"bus_models\"/>. If you specify a VIF model that is not supported, "
+"the instance fails to launch. See <xref linkend=\"vif_models\"/>."
+msgstr "サポートされていないディスクや CD-ROM バスモデルを指定する場合、<xref linkend=\"bus_models\"/>を参照してください。サポートされていない VIF モデルを指定する場合、インスタンスは起動できません。<xref linkend=\"vif_models\"/>を参照してください。"
 
-#: ./doc/common/ch_cli_heat_commands.xml103(para)
-#: ./doc/common/ch_cli_heat_commands.xml575(para)
-msgid "Describe the event."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml111(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use template-show instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml119(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use stack-list instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml127(para)
-#: ./doc/common/ch_cli_heat_commands.xml608(para)
-msgid "Show available outputs."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml135(para)
-#: ./doc/common/ch_cli_heat_commands.xml625(para)
-msgid "Show a specific stack output."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml143(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use resource-show instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml151(para)
-#: ./doc/common/ch_cli_heat_commands.xml650(para)
-msgid "Show list of resources belonging to a stack."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml159(para)
-#: ./doc/common/ch_cli_heat_commands.xml667(para)
-msgid "List resource metadata."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml167(para)
-#: ./doc/common/ch_cli_heat_commands.xml692(para)
-msgid "Describe the resource."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml175(para)
-#: ./doc/common/ch_cli_heat_commands.xml717(para)
-msgid "Send a signal to a resource."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml183(para)
-#: ./doc/common/ch_cli_heat_commands.xml762(para)
-msgid "Generate a template based on a resource."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml191(para)
-#: ./doc/common/ch_cli_heat_commands.xml790(para)
-msgid "List the available resource types."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml199(para)
-#: ./doc/common/ch_cli_heat_commands.xml797(para)
-msgid "Show the resource type."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml207(para)
-#: ./doc/common/ch_cli_heat_commands.xml814(para)
-msgid "Abandon the stack."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml215(para)
-#: ./doc/common/ch_cli_heat_commands.xml834(para)
-msgid "Adopt a stack."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml223(para)
-#: ./doc/common/ch_cli_heat_commands.xml932(para)
-msgid "Create the stack."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml231(para)
-#: ./doc/common/ch_cli_heat_commands.xml1019(para)
-msgid "Delete the stack(s)."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml239(para)
-#: ./doc/common/ch_cli_heat_commands.xml1037(para)
-msgid "List the user's stacks."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml247(para)
-#: ./doc/common/ch_cli_heat_commands.xml1076(para)
-msgid "Preview the stack."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml255(para)
-#: ./doc/common/ch_cli_heat_commands.xml1154(para)
-msgid "Describe the stack."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml263(para)
-#: ./doc/common/ch_cli_heat_commands.xml1173(para)
-msgid "Update the stack."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml271(para)
-#: ./doc/common/ch_cli_heat_commands.xml1243(para)
-msgid "Get the template for the specified stack."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml279(para)
-#: ./doc/common/ch_cli_heat_commands.xml1261(para)
-msgid "Validate a template with parameters."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml287(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use stack-update instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml295(para)
-msgid "<emphasis>DEPRECATED!</emphasis> Use template-validate instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml320(title)
-msgid "heat optional arguments"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml333(para)
-msgid "Defaults to <code>env[HEATCLIENT_DEBUG]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml349(para)
-msgid ""
-"Explicitly allow the client to perform \"insecure\" SSL (https) requests. "
-"The server's certificate will not be verified against any certificate "
-"authorities. This option should be used with caution."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml370(para)
+#: ./doc/common/section_cli_glance_manage_images.xml284(para)
 msgid ""
-"Path of client key to use in SSL connection.This option is not necessary if "
-"your key is prepended to your cert file."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml380(para)
-msgid ""
-"Path of CA SSL certificate(s) used to verify the remote server's "
-"certificate. Without this option the client looks for the default system CA "
-"certificates."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml390(para)
-msgid ""
-"Number of seconds to wait for an API response, defaults to system socket "
-"timeout"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml455(para)
-msgid ""
-"Do not contact keystone for a token. Defaults to "
-"<code>env[OS_NO_CLIENT_AUTH]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml464(para)
-msgid "Defaults to <code>env[HEAT_URL]</code>."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml472(para)
-msgid "Defaults to <code>env[HEAT_API_VERSION]</code> or 1."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml496(para)
-msgid "Send os-username and os-password to heat."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml504(title)
-msgid "heat action-resume command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml513(para)
-msgid "Name or ID of stack to resume."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml521(title)
-msgid "heat action-suspend command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml530(para)
-msgid "Name or ID of stack to suspend."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml538(title)
-msgid "heat build-info command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml545(title)
-msgid "heat event-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml554(para)
-#: ./doc/common/ch_cli_heat_commands.xml582(para)
-msgid "Name or ID of stack to show the events for."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml565(para)
-msgid "Name of the resource to filter events by."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml573(title)
-msgid "heat event-show command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml590(para)
-msgid "Name of the resource the event belongs to."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml598(para)
-msgid "ID of event to display details for."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml606(title)
-msgid "heat output-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml615(para)
-#: ./doc/common/ch_cli_heat_commands.xml632(para)
-msgid "Name or ID of stack to query."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml623(title)
-msgid "heat output-show command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml640(para)
-msgid "Name of an output to display."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml648(title)
-msgid "heat resource-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml657(para)
-msgid "Name or ID of stack to show the resources for."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml665(title)
-msgid "heat resource-metadata command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml674(para)
-msgid "Name or ID of stack to show the resource metadata for."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml682(para)
-msgid "Name of the resource to show the metadata for."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml690(title)
-msgid "heat resource-show command"
+"The valid model values depend on the <literal>libvirt_type</literal> "
+"setting, as shown in the following tables."
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml699(para)
-msgid "Name or ID of stack to show the resource for."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml287(caption)
+msgid "Disk and CD-ROM bus model values"
+msgstr "ディスクと CD-ROM のバスモデルの値"
 
-#: ./doc/common/ch_cli_heat_commands.xml707(para)
-msgid "Name of the resource to show the details for."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml292(th)
+#: ./doc/common/section_cli_glance_manage_images.xml336(th)
+msgid "libvirt_type setting"
+msgstr "libvirt_type 設定"
 
-#: ./doc/common/ch_cli_heat_commands.xml715(title)
-msgid "heat resource-signal command"
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml293(th)
+#: ./doc/common/section_cli_glance_manage_images.xml337(th)
+msgid "Supported model values"
+msgstr "サポートされるモデルの値"
 
-#: ./doc/common/ch_cli_heat_commands.xml724(para)
-msgid "Name or ID of stack the resource belongs to."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml298(td)
+#: ./doc/common/section_cli_glance_manage_images.xml342(td)
+msgid "qemu or kvm"
+msgstr "qemu または kvm"
 
-#: ./doc/common/ch_cli_heat_commands.xml732(para)
-msgid "Name of the resource to signal."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml303(para)
+#: ./doc/common/section_cli_glance_manage_images.xml320(para)
+msgid "ide"
+msgstr "ide"
 
-#: ./doc/common/ch_cli_heat_commands.xml743(para)
-msgid "JSON Data to send to the signal handler."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml306(para)
+msgid "scsi"
+msgstr "scsi"
 
-#: ./doc/common/ch_cli_heat_commands.xml751(para)
-msgid "File containing JSON data to send to the signal handler."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml309(para)
+#: ./doc/common/section_cli_glance_manage_images.xml359(para)
+msgid "virtio"
+msgstr "virtio"
 
-#: ./doc/common/ch_cli_heat_commands.xml760(title)
-msgid "heat resource-template command"
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml316(td)
+#: ./doc/common/section_cli_glance_manage_images.xml323(para)
+#: ./doc/common/section_cli_glance_manage_images.xml366(td)
+msgid "xen"
+msgstr "xen"
 
-#: ./doc/common/ch_cli_heat_commands.xml769(para)
-msgid "Name of the resource to generate a template for."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml331(caption)
+msgid "VIF model values"
+msgstr "仮想インターフェースのモデルの値"
 
-#: ./doc/common/ch_cli_heat_commands.xml780(para)
-msgid "The template output format, one of: yaml, json."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml347(para)
+#: ./doc/common/section_cli_glance_manage_images.xml370(para)
+msgid "e1000"
+msgstr "e1000"
 
-#: ./doc/common/ch_cli_heat_commands.xml788(title)
-msgid "heat resource-type-list command"
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml350(para)
+#: ./doc/common/section_cli_glance_manage_images.xml376(para)
+msgid "ne2k_pci"
+msgstr "ne2k_pci"
 
-#: ./doc/common/ch_cli_heat_commands.xml795(title)
-msgid "heat resource-type-show command"
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml353(para)
+#: ./doc/common/section_cli_glance_manage_images.xml379(para)
+msgid "pcnet"
+msgstr "pcnet"
 
-#: ./doc/common/ch_cli_heat_commands.xml804(para)
-msgid "Resource type to get the details for."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml812(title)
-msgid "heat stack-abandon command"
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml356(para)
+#: ./doc/common/section_cli_glance_manage_images.xml382(para)
+msgid "rtl8139"
+msgstr "rtl8139"
 
-#: ./doc/common/ch_cli_heat_commands.xml821(para)
-msgid "Name or ID of stack to abandon."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml373(para)
+msgid "netfront"
+msgstr "netfront"
 
-#: ./doc/common/ch_cli_heat_commands.xml829(title)
-msgid "heat stack-adopt command"
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml388(td)
+msgid "vmware"
+msgstr "vmware"
 
-#: ./doc/common/ch_cli_heat_commands.xml841(para)
-msgid "Name of the stack to adopt."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml393(para)
+msgid "VirtualE1000"
+msgstr "VirtualE1000"
 
-#: ./doc/common/ch_cli_heat_commands.xml852(para)
-#: ./doc/common/ch_cli_heat_commands.xml950(para)
-#: ./doc/common/ch_cli_heat_commands.xml1094(para)
-#: ./doc/common/ch_cli_heat_commands.xml1191(para)
-#: ./doc/common/ch_cli_heat_commands.xml1276(para)
-msgid "Path to the template."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml860(para)
-#: ./doc/common/ch_cli_heat_commands.xml958(para)
-#: ./doc/common/ch_cli_heat_commands.xml1102(para)
-#: ./doc/common/ch_cli_heat_commands.xml1199(para)
-#: ./doc/common/ch_cli_heat_commands.xml1284(para)
-msgid "Path to the environment."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml868(para)
-#: ./doc/common/ch_cli_heat_commands.xml966(para)
-#: ./doc/common/ch_cli_heat_commands.xml1110(para)
-#: ./doc/common/ch_cli_heat_commands.xml1207(para)
-#: ./doc/common/ch_cli_heat_commands.xml1268(para)
-msgid "URL of template."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml396(para)
+msgid "VirtualPCNet32"
+msgstr "VirtualPCNet32"
 
-#: ./doc/common/ch_cli_heat_commands.xml876(para)
-msgid "URL to retrieve template object (e.g from swift)."
-msgstr ""
+#: ./doc/common/section_cli_glance_manage_images.xml399(para)
+msgid "VirtualVmxnet"
+msgstr "VirtualVmxnet"
 
-#: ./doc/common/ch_cli_heat_commands.xml884(para)
-#: ./doc/common/ch_cli_heat_commands.xml982(para)
+#: ./doc/common/section_cli_glance_manage_images.xml411(para)
 msgid ""
-"Stack creation timeout in minutes. <emphasis>DEPRECATED</emphasis> use "
-"--timeout instead."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml893(para)
-#: ./doc/common/ch_cli_heat_commands.xml991(para)
-msgid "Stack creation timeout in minutes."
-msgstr "スタック作成のタイムアウト時間（分単位）。"
-
-#: ./doc/common/ch_cli_heat_commands.xml901(para)
-msgid "Path to adopt stack data file."
+"If you encounter problems in creating an image in Image Service or Compute, "
+"the following information may help you troubleshoot the creation process."
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml909(para)
-#: ./doc/common/ch_cli_heat_commands.xml999(para)
-msgid "Enable rollback on create/update failure."
-msgstr "作成/更新失敗時のロールバックを有効にします。"
-
-#: ./doc/common/ch_cli_heat_commands.xml917(para)
-#: ./doc/common/ch_cli_heat_commands.xml1007(para)
-#: ./doc/common/ch_cli_heat_commands.xml1231(para)
+#: ./doc/common/section_cli_glance_manage_images.xml415(para)
 msgid ""
-"Parameter values used to create the stack. This can be specified multiple "
-"times, or once with parameters separated by a semicolon."
-msgstr ""
+"Ensure that the version of qemu you are using is version 0.14 or later. "
+"Earlier versions of qemu result in an <literal>unknown option -s</literal> "
+"error message in the <filename>nova-compute.log</filename> file."
+msgstr "QEMU のバージョン 0.14 以降を使用していることを確認します。古いバージョンの QEMU を使用していると、<filename>nova-compute.log</filename> に <literal>unknown option -s</literal> エラーメッセージが記録されます。"
 
-#: ./doc/common/ch_cli_heat_commands.xml927(title)
-msgid "heat stack-create command"
+#: ./doc/common/section_keystone-external-auth.xml7(title)
+msgid "External authentication with Identity"
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml939(para)
-msgid "Name of the stack to create."
-msgstr "作成するスタックの名前。"
-
-#: ./doc/common/ch_cli_heat_commands.xml974(para)
-#: ./doc/common/ch_cli_heat_commands.xml1215(para)
-#: ./doc/common/ch_cli_heat_commands.xml1292(para)
-msgid "URL to retrieve template object (e.g. from swift)."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml1017(title)
-msgid "heat stack-delete command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml1026(para)
-msgid "Name or ID of stack(s) to delete."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml1034(title)
-msgid "heat stack-list command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml1044(para)
+#: ./doc/common/section_keystone-external-auth.xml8(para)
 msgid ""
-"Filter parameters to apply on returned stacks. This can be specified "
-"multiple times, or once with parameters separated by a semicolon."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml1054(para)
-msgid "Limit the number of stacks returned."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml1062(para)
-msgid "Only return stacks that appear after the given stack ID."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml1071(title)
-msgid "heat stack-preview command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml1083(para)
-msgid "Name of the stack to preview."
+"When Identity runs in <literal>apache-httpd</literal>, you can use external "
+"authentication methods that differ from the authentication provided by the "
+"identity store back end. For example, you can use an SQL identity back end "
+"together with X.509 authentication, Kerberos, and so on instead of using the"
+" user name and password combination."
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml1118(para)
-msgid "URL to retrieve template object (e.g from swift)"
+#: ./doc/common/section_keystone-external-auth.xml15(title)
+msgid "Use HTTPD authentication"
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml1126(para)
-msgid "Stack timeout in minutes. Default: 60"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml1134(para)
-msgid "Enable rollback on failure"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml1142(para)
+#: ./doc/common/section_keystone-external-auth.xml16(para)
 msgid ""
-"Parameter values used to preview the stack. This can be specified multiple "
-"times, or once with parameters separated by semicolon."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml1152(title)
-msgid "heat stack-show command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml1161(para)
-msgid "Name or ID of stack to describe."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml1169(title)
-msgid "heat stack-update command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml1180(para)
-msgid "Name or ID of stack to update."
+"Web servers, like Apache HTTP, support many methods of authentication. "
+"Identity can allow the web server to perform the authentication. The web "
+"server then passes the authenticated user to Identity by using the "
+"<literal>REMOTE_USER</literal> environment variable. This user must already "
+"exist in the Identity back end to get a token from the controller. To use "
+"this method, Identity should run on <literal>apache-httpd</literal>."
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml1223(para)
-msgid "Stack update timeout in minutes."
+#: ./doc/common/section_keystone-external-auth.xml27(title)
+msgid "Use X.509"
 msgstr ""
 
-#: ./doc/common/ch_cli_heat_commands.xml1241(title)
-msgid "heat template-show command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml1250(para)
-msgid "Name or ID of stack to get the template for."
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml1258(title)
-msgid "heat template-validate command"
-msgstr ""
-
-#: ./doc/common/ch_cli_heat_commands.xml1300(para)
+#: ./doc/common/section_keystone-external-auth.xml28(para)
 msgid ""
-"Parameter values to validate. This can be specified multiple times, or once "
-"with parameters separated by a semicolon."
+"The following Apache configuration snippet authenticates the user based on a"
+" valid X.509 certificate from a known CA:"
 msgstr ""
 
-#: ./doc/common/section_cli_overview.xml8(para)
-msgid ""
-"You can use the OpenStack command-line clients to run simple commands that "
-"make API calls. You can run these commands from the command line or in "
-"scripts to automate tasks. If you provide OpenStack credentials, you can run"
-" these commands on any computer."
-msgstr "API コールを行う簡単なコマンドを実行するために、OpenStack コマンドラインクライアントを使用できます。コマンドラインから、または作業を自動化するためのスクリプトでこれらのコマンドを実行できます。OpenStack クレデンシャルを指定すると、どのコンピューターでもこれらのコマンドを実行できます。"
-
-#: ./doc/common/section_cli_overview.xml12(para)
-msgid ""
-"Internally, each client command runs cURL commands that embed API requests. "
-"The OpenStack APIs are RESTful APIs that use the HTTP protocol, including "
-"methods, URIs, media types, and response codes."
-msgstr "内部的に、各クライアントコマンドは API リクエストを組み込んだ cURL コマンドを実行します。OpenStack API は、メソッド、URI、メディアタイプ、応答コードを含む HTTP プロトコルを使用する RESTful API です。"
+#: ./doc/common/section_getstart_object-storage.xml5(title)
+msgid "OpenStack Object Storage"
+msgstr "OpenStack Object Storage"
 
-#: ./doc/common/section_cli_overview.xml16(para)
+#: ./doc/common/section_getstart_object-storage.xml6(para)
 msgid ""
-"These open-source Python clients run on Linux or Mac OS X systems and are "
-"easy to learn and use. Each OpenStack service has its own command-line "
-"client. On some client commands, you can specify a <placeholder-1/> "
-"parameter to show the underlying API request for the command. This is a good"
-" way to become familiar with the OpenStack API calls."
-msgstr "これらのオープンソースの Python クライアントは、Linux または Mac OS X システムで実行します。これらは簡単に習得し、使用できます。OpenStack の各サービスは自身のコマンドラインクライアントを持ちます。いくつかのクライアントコマンドでは、コマンドのベースになる API リクエストを表示するために、<placeholder-1/> パラメーターを指定できます。これは OpenStack API コールに慣れるために良い方法です。"
-
-#: ./doc/common/section_cli_overview.xml23(para)
-msgid ""
-"The following table lists the command-line client for each OpenStack service"
-" with its package name and description."
-msgstr "以下の表は、各 OpenStack サービスのコマンドラインクライアント、そのパッケージ名、説明の一覧です。"
-
-#: ./doc/common/section_cli_overview.xml26(caption)
-msgid "OpenStack services and clients"
-msgstr "OpenStack のサービスとクライアント"
-
-#: ./doc/common/section_cli_overview.xml34(th)
-msgid "Client"
-msgstr "クライアント"
-
-#: ./doc/common/section_cli_overview.xml35(th)
-msgid "Package"
-msgstr "パッケージ"
-
-#: ./doc/common/section_cli_overview.xml43(package)
-msgid "python-cinderclient"
-msgstr "python-cinderclient"
-
-#: ./doc/common/section_cli_overview.xml44(td)
-msgid "Create and manage volumes."
-msgstr "ボリュームを作成、管理します。"
-
-#: ./doc/common/section_cli_overview.xml49(package)
-msgid "python-novaclient"
-msgstr "python-novaclient"
-
-#: ./doc/common/section_cli_overview.xml50(td)
-msgid "Create and manage images, instances, and flavors."
-msgstr "イメージ、インスタンス、フレーバーを作成、管理します。"
-
-#: ./doc/common/section_cli_overview.xml55(package)
-msgid "python-troveclient"
-msgstr "python-troveclient"
-
-#: ./doc/common/section_cli_overview.xml56(td)
-msgid "Create and manage databases."
-msgstr "データベースを作成、管理します。"
-
-#: ./doc/common/section_cli_overview.xml59(td)
-msgid "Identity"
-msgstr "Identity"
-
-#: ./doc/common/section_cli_overview.xml61(package)
-msgid "python-keystoneclient"
-msgstr "python-keystoneclient"
-
-#: ./doc/common/section_cli_overview.xml62(td)
-msgid "Create and manage users, tenants, roles, endpoints, and credentials."
-msgstr "ユーザー、プロジェクト、ロール、エンドポイント、クレデンシャルを作成、管理します。"
-
-#: ./doc/common/section_cli_overview.xml67(package)
-msgid "python-glanceclient"
-msgstr "python-glanceclient"
-
-#: ./doc/common/section_cli_overview.xml68(td)
-msgid "Create and manage images."
-msgstr "イメージを作成、管理します。"
-
-#: ./doc/common/section_cli_overview.xml73(package)
-msgid "python-neutronclient"
-msgstr "python-neutronclient"
-
-#: ./doc/common/section_cli_overview.xml74(td)
-msgid ""
-"Configure networks for guest servers. This client was previously called "
-"<placeholder-1/>."
-msgstr "ゲストサーバー用のネットワークを設定します。このクライアントは以前 <placeholder-1/> と呼ばれていました。"
-
-#: ./doc/common/section_cli_overview.xml80(package)
-msgid "python-swiftclient"
-msgstr "python-swiftclient"
-
-#: ./doc/common/section_cli_overview.xml81(td)
-msgid ""
-"Gather statistics, list items, update metadata, and upload, download, and "
-"delete files stored by the Object Storage service. Gain access to an Object "
-"Storage installation for ad hoc processing."
-msgstr "統計情報を収集し、項目を一覧表示し、メタデータを更新し、Object Storage サービスにより保存されたファイルをアップロード、ダウンロード、削除します。"
-
-#: ./doc/common/section_cli_overview.xml88(package)
-msgid "python-heatclient"
-msgstr "python-heatclient"
-
-#: ./doc/common/section_cli_overview.xml89(td)
-msgid ""
-"Launch stacks from templates, view details of running stacks including "
-"events and resources, and update and delete stacks."
-msgstr "テンプレートからスタックを起動し、イベントやリソースを含む実行中のスタックの詳細を表示し、スタックを更新、削除します。"
-
-#: ./doc/common/section_cli_overview.xml95(package)
-msgid "python-ceilometerclient"
-msgstr "python-ceilometerclient"
-
-#: ./doc/common/section_cli_overview.xml96(td)
-msgid "Create and collect measurements across OpenStack."
-msgstr "OpenStack 全体の測定項目を作成、収集します。"
-
-#: ./doc/common/section_cli_overview.xml100(para)
-msgid "An OpenStack <placeholder-1/> client is in development."
-msgstr "OpenStack <placeholder-1/> クライアントが開発中です。"
-
-#: ./doc/common/section_cli_overview.xml102(para)
-msgid ""
-"For client installation instructions, see <link "
-"href=\"http://docs.openstack.org/user-"
-"guide/content/install_clients.html\">Install the OpenStack command-line "
-"clients</link>. For information about the OpenStack RC file, see <link "
-"href=\"http://docs.openstack.org/user-"
-"guide/content/cli_openrc.html\">Download and source the OpenStack RC "
-"file</link>."
-msgstr "クライアントのインストールの説明は <link href=\"http://docs.openstack.org/user-guide/content/install_clients.html\">OpenStack コマンドラインクライアントのインストール</link>を参照してください。OpenStack RC ファイルに関する情報は <link href=\"http://docs.openstack.org/user-guide/content/cli_openrc.html\">OpenStack RC ファイルのダウンロードと読み込み</link>を参照してください。"
-
-#: ./doc/common/section_rpc.xml8(para)
-msgid ""
-"OpenStack projects use AMQP, an open standard for messaging middleware. "
-"OpenStack services that run on multiple servers to talk to each other. "
-"OpenStack Oslo RPC supports three implementations of AMQP: "
-"<application>RabbitMQ</application>, <application>Qpid</application>, and "
-"<application>ZeroMQ</application>."
+"The OpenStack Object Storage is a multi-tenant object storage system. It is "
+"highly scalable and can manage large amounts of unstructured data at low "
+"cost through a RESTful HTTP API."
 msgstr ""
 
-#: ./doc/common/section_rpc.xml16(para)
-msgid ""
-"OpenStack Oslo RPC uses <application>RabbitMQ</application> by default. Use "
-"these options to configure the <application>RabbitMQ</application> message "
-"system. The <literal>rpc_backend</literal> option is not required as long as"
-" <application>RabbitMQ</application> is the default messaging system. "
-"However, if it is included the configuration, you must set it to "
-"<literal>nova.openstack.common.rpc.impl_kombu</literal>."
-msgstr ""
+#: ./doc/common/section_getstart_object-storage.xml9(para)
+#: ./doc/common/section_getstart_networking.xml11(para)
+msgid "It includes the following components:"
+msgstr "以下のコンポーネントを含みます。"
 
-#: ./doc/common/section_rpc.xml25(para)
+#: ./doc/common/section_getstart_object-storage.xml11(term)
 msgid ""
-"You can use these additional options to configure the "
-"<application>RabbitMQ</application> messaging system. You can configure "
-"messaging communication for different installation scenarios, tune retries "
-"for RabbitMQ, and define the size of the RPC thread pool. To monitor "
-"notifications through RabbitMQ, you must set the "
-"<option>notification_driver</option> option to "
-"<literal>nova.notifier.rabbit_notifier</literal> in the "
-"<filename>nova.conf</filename> file. The default for sending usage data is "
-"sixty seconds plus a random number of seconds from zero to sixty."
+"Proxy servers (<systemitem class=\"service\">swift-proxy-"
+"server</systemitem>)"
 msgstr ""
 
-#: ./doc/common/section_rpc.xml40(para)
+#: ./doc/common/section_getstart_object-storage.xml13(para)
 msgid ""
-"Use these options to configure the <application>Qpid</application> messaging"
-" system for OpenStack Oslo RPC. <application>Qpid</application> is not the "
-"default messaging system, so you must enable it by setting the "
-"<option>rpc_backend</option> option in the <filename>nova.conf</filename> "
-"file."
+"Accepts OpenStack Object Storage API and raw HTTP requests to upload files, "
+"modify metadata, and create containers. It also serves file or container "
+"listings to web browsers. To improve performance, the proxy server can use "
+"an optional cache usually deployed with memcache."
 msgstr ""
 
-#: ./doc/common/section_rpc.xml47(para)
+#: ./doc/common/section_getstart_object-storage.xml20(term)
 msgid ""
-"This critical option points the compute nodes to the "
-"<application>Qpid</application> broker (server). Set "
-"<option>qpid_hostname</option> to the host name where the broker runs in the"
-" <filename>nova.conf</filename> file."
+"Account servers (<systemitem class=\"service\">swift-account-"
+"server</systemitem>)"
 msgstr ""
 
-#: ./doc/common/section_rpc.xml69(para)
-msgid ""
-"This table lists additional options that you use to configure the Qpid "
-"messaging driver for OpenStack Oslo RPC. These options are used "
-"infrequently."
+#: ./doc/common/section_getstart_object-storage.xml22(para)
+msgid "Manages accounts defined with Object Storage."
 msgstr ""
 
-#: ./doc/common/section_rpc.xml76(para)
+#: ./doc/common/section_getstart_object-storage.xml26(term)
 msgid ""
-"Use these options to configure the <application>ZeroMQ</application> "
-"messaging system for OpenStack Oslo RPC. <application>ZeroMQ</application> "
-"is not the default messaging system, so you must enable it by setting the "
-"<option>rpc_backend</option> option in the <filename>nova.conf</filename> "
-"file."
+"Container servers (<systemitem class=\"service\">swift-container-"
+"server</systemitem>)"
 msgstr ""
 
-#: ./doc/common/section_rpc.xml86(para)
-msgid ""
-"Use these options to configure the <application>RabbitMQ</application> and "
-"<application>Qpid</application> messaging drivers."
+#: ./doc/common/section_getstart_object-storage.xml28(para)
+msgid "Manages the mapping of containers or folders, within Object Storage."
 msgstr ""
 
-#: ./doc/common/section_cli_install.xml7(title)
-msgid "Install the OpenStack command-line clients"
-msgstr "OpenStack コマンドラインクライアントのインストール"
-
-#: ./doc/common/section_cli_install.xml8(para)
-msgid ""
-"Install the prerequisite software and the Python package for each OpenStack "
-"client."
-msgstr "前提ソフトウェアと各 OpenStack クライアント用の Python パッケージをインストールします。"
-
-#: ./doc/common/section_cli_install.xml11(title)
-msgid "Install the prerequisite software"
-msgstr "前提ソフトウェアのインストール"
-
-#: ./doc/common/section_cli_install.xml12(para)
-msgid ""
-"The following table lists the software that you need to have to run the "
-"command-line clients, and provides installation instructions as needed."
-msgstr "以下の表は、コマンドラインクライアントを実行するために必要となるソフトウェアの一覧です。必要に応じてインストール手順が書かれています。"
-
-#: ./doc/common/section_cli_install.xml16(caption)
-msgid "Prerequisite software"
-msgstr "前提ソフトウェア"
-
-#: ./doc/common/section_cli_install.xml21(th)
-msgid "Prerequisite"
-msgstr "前提"
-
-#: ./doc/common/section_cli_install.xml28(para)
-msgid "Python 2.6 or later"
-msgstr "Python 2.6 またはそれ以降"
-
-#: ./doc/common/section_cli_install.xml31(para)
-msgid "Currently, the clients do not support Python 3."
-msgstr "現在、クライアントは Python 3 をサポートしません。"
-
-#: ./doc/common/section_cli_install.xml37(para)
-msgid "<package>setuptools</package> package"
-msgstr "<package>setuptools</package> パッケージ"
-
-#: ./doc/common/section_cli_install.xml40(para)
-msgid "Installed by default on Mac OS X."
-msgstr "Mac OS X に標準でインストールされます。"
-
-#: ./doc/common/section_cli_install.xml41(para)
-msgid ""
-"Many Linux distributions provide packages to make "
-"<package>setuptools</package> easy to install. Search your package manager "
-"for <package>setuptools</package> to find an installation package. If you "
-"cannot find one, download the <package>setuptools</package> package directly"
-" from <link "
-"href=\"http://pypi.python.org/pypi/setuptools\">http://pypi.python.org/pypi/setuptools</link>."
-msgstr "多くの Linux ディストリビューションはインストールしやすい <package>setuptools</package> パッケージを提供します。インストールパッケージを検索するために、パッケージマネージャーで <package>setuptools</package> を検索します。見つけられない場合、<link href=\"http://pypi.python.org/pypi/setuptools\">http://pypi.python.org/pypi/setuptools</link> から <package>setuptools</package> パッケージを直接ダウンロードします。"
-
-#: ./doc/common/section_cli_install.xml49(para)
-msgid ""
-"The recommended way to install <package>setuptools</package> on Microsoft "
-"Windows is to follow the documentation provided <link "
-"href=\"https://pypi.python.org/pypi/setuptools#windows\">on the setuptools "
-"website</link>. Another option is to use the unofficial binary installer "
-"maintained by Christoph Gohlke (<link "
-"href=\"http://www.lfd.uci.edu/~gohlke/pythonlibs/#setuptools\">http://www.lfd.uci.edu/~gohlke/pythonlibs/#setuptools</link>)."
-msgstr "Microsoft Windows に <package>setuptools</package> をインストールする推奨の方法は <link href=\"https://pypi.python.org/pypi/setuptools#windows\">setuptools ウェブサイト</link> で提供されているドキュメントに従うことです。他の選択肢は hristoph Gohlke (<link href=\"http://www.lfd.uci.edu/~gohlke/pythonlibs/#setuptools\">http://www.lfd.uci.edu/~gohlke/pythonlibs/#setuptools</link>) によりメンテナンスされている非公式のバイナリインストーラーを使用することです。"
-
-#: ./doc/common/section_cli_install.xml62(package)
-msgid "pip"
-msgstr "pip"
-
-#: ./doc/common/section_cli_install.xml62(td)
-msgid "<placeholder-1/> package"
-msgstr "<placeholder-1/> パッケージ"
-
-#: ./doc/common/section_cli_install.xml64(para)
+#: ./doc/common/section_getstart_object-storage.xml32(term)
 msgid ""
-"To install the clients on a Linux, Mac OS X, or Microsoft Windows system, "
-"use <package>pip</package>. It is easy to use, ensures that you get the "
-"latest version of the clients from the <link "
-"href=\"http://pypi.python.org/pypi/python-novaclient/\">Python Package "
-"Index</link>, and lets you update or remove the packages later on."
-msgstr "Linux、Mac OS X、Microsoft Windows システムにクライアントをインストールするために、<package>pip</package> を使用します。これは使いやすく、必ず <link href=\"http://pypi.python.org/pypi/python-novaclient/\">Python Package Index</link> から最新バージョンのクライアントを取得します。後からパッケージの更新や削除ができます。"
-
-#: ./doc/common/section_cli_install.xml73(para)
-msgid ""
-"Install <package>pip</package> through the package manager for your system:"
-msgstr "お使いのシステムのパッケージマネージャーを利用して <package>pip</package> をインストールします。"
-
-#: ./doc/common/section_cli_install.xml76(title)
-msgid "MacOS"
-msgstr "MacOS"
-
-#: ./doc/common/section_cli_install.xml80(title)
-msgid "Microsoft Windows"
-msgstr "Microsoft Windows"
-
-#: ./doc/common/section_cli_install.xml81(para)
-msgid ""
-"Ensure that the <filename>C:\\Python27\\Scripts</filename> directory is "
-"defined in the <literal>PATH</literal> environment variable, and use the "
-"<placeholder-1/> command from the <package>setuptools</package> package: "
-"<placeholder-2/>Another option is to use the unofficial binary installer "
-"provided by Christoph Gohlke (<link "
-"href=\"http://www.lfd.uci.edu/~gohlke/pythonlibs/#pip\">http://www.lfd.uci.edu/~gohlke/pythonlibs/#pip</link>)."
-msgstr "<filename>C:\\Python27\\Scripts</filename> ディレクトリが <literal>PATH</literal> 環境変数に定義され、<package>setuptools</package> パッケージから <placeholder-1/> コマンドを使用できることを確認します。 <placeholder-2/> もう一つの選択肢は Christoph Gohlke (<link href=\"http://www.lfd.uci.edu/~gohlke/pythonlibs/#pip\">http://www.lfd.uci.edu/~gohlke/pythonlibs/#pip</link>) により提供されている非公式のバイナリインストーラーを使用することです。"
-
-#: ./doc/common/section_cli_install.xml98(title)
-msgid "Ubuntu 12.04/14.04"
-msgstr "Ubuntu 12.04/14.04"
-
-#: ./doc/common/section_cli_install.xml99(para)
-msgid ""
-"A packaged version enables you to use <package>dpkg</package> or <package"
-">apt-get</package> to install the <package>python-novaclient</package>: "
-"<placeholder-1/>"
-msgstr "<package>python-novaclient</package> をインストールするために、パッケージ化されたバージョンにより <package>dpkg</package> または <package>apt-get</package> を使用できます。<placeholder-1/>"
-
-#: ./doc/common/section_cli_install.xml108(title)
-msgid "Ubuntu and Debian"
-msgstr "Ubuntu と Debian"
-
-#: ./doc/common/section_cli_install.xml114(title)
-msgid "Red Hat Enterprise Linux, CentOS, or Fedora"
-msgstr "Red Hat Enterprise Linux、CentOS、Fedora"
-
-#: ./doc/common/section_cli_install.xml115(para)
-msgid ""
-"A packaged version available in <link "
-"href=\"http://openstack.redhat.com/\">RDO</link> enables you to use "
-"<package>yum</package> to install the clients, or you can install "
-"<package>pip</package> and use it to manage client installation: "
-"<placeholder-1/>"
-msgstr "クライアントをインストールするために、<link href=\"http://openstack.redhat.com/\">RDO</link> で利用可能なパッケージ化されたバージョンにより <package>rpm</package> を使用できます。または、<package>pip</package> をインストールして、クライアントを管理できます。<placeholder-1/>"
-
-#: ./doc/common/section_cli_install.xml123(title)
-msgid "openSUSE 12.2 and earlier"
-msgstr "openSUSE 12.2 およびそれ以前"
-
-#: ./doc/common/section_cli_install.xml124(para)
-msgid ""
-"A <link href=\"https://build.opensuse.org/package/show?package=python-"
-"novaclient&amp;project=Cloud:OpenStack:Master\">packaged version available "
-"in the Open Build Service</link> enables you to use <package>rpm</package> "
-"or <package>zypper</package> to install the clients, or you can install "
-"<package>pip</package> and use it to manage client installation: "
-"<placeholder-1/>"
-msgstr "python-novaclient をインストールするために、<link href=\"https://build.opensuse.org/package/show?package=python-novaclient&amp;project=Cloud:OpenStack:Master\">Open Build Service で利用可能なパッケージ化されたバージョン</link>により <package>rpm</package> または <package>zypper</package> を使用できます。または、<package>pip</package> をインストールして、クライアントを管理できます。<placeholder-1/>"
-
-#: ./doc/common/section_cli_install.xml135(title)
-msgid "openSUSE 12.3 and later"
-msgstr "openSUSE 12.3 およびそれ以降"
-
-#: ./doc/common/section_cli_install.xml136(para)
-msgid ""
-"A packaged version enables you to use <package>rpm</package> or "
-"<package>zypper</package> to install the clients. See <xref "
-"linkend=\"cli_clients_install\"/>"
-msgstr "クライアントをインストールするために、パッケージ化されたバージョンにより <package>rpm</package> または <package>zypper</package> を使用できます。<xref linkend=\"cli_clients_install\"/>を参照してください。"
-
-#: ./doc/common/section_cli_install.xml147(title)
-msgid "Install the clients"
-msgstr "クライアントのインストール"
-
-#: ./doc/common/section_cli_install.xml148(para)
-msgid ""
-"When following the instructions in this section, replace "
-"<replaceable>PROJECT</replaceable> with the lowercase name of the client to "
-"install, such as <placeholder-1/>. Repeat for each client. The following "
-"values are valid:"
-msgstr "このセクションにある説明に従うとき、<placeholder-1/> のように、インストールするクライアントの小文字名で <replaceable>PROJECT</replaceable> を置き換えてください。各クライアントに対して繰り返します。以下の値が有効です。"
-
-#: ./doc/common/section_cli_install.xml155(para)
-msgid "<literal>ceilometer</literal> - Telemetry API"
-msgstr "<literal>ceilometer</literal> - Telemetry API"
-
-#: ./doc/common/section_cli_install.xml159(para)
-msgid "<literal>cinder</literal> - Block Storage API and extensions"
-msgstr "<literal>cinder</literal> - Block Storage API およびその拡張"
-
-#: ./doc/common/section_cli_install.xml163(para)
-msgid "<literal>glance</literal> - Image Service API"
-msgstr "<literal>glance</literal> - Image Service API"
-
-#: ./doc/common/section_cli_install.xml167(para)
-msgid "<literal>heat</literal> - Orchestration API"
-msgstr "<literal>heat</literal> - Orchestration API"
-
-#: ./doc/common/section_cli_install.xml171(para)
-msgid "<literal>keystone</literal> - Identity service API and extensions"
-msgstr "<literal>keystone</literal> - Identity service API およびその拡張"
-
-#: ./doc/common/section_cli_install.xml175(para)
-msgid "<literal>neutron</literal> - Networking API"
-msgstr "<literal>neutron</literal> - Networking API"
-
-#: ./doc/common/section_cli_install.xml179(para)
-msgid "<literal>nova</literal> - Compute API and extensions"
-msgstr "<literal>nova</literal> - Compute API およびその拡張"
-
-#: ./doc/common/section_cli_install.xml183(para)
-msgid "<literal>swift</literal> - Object Storage API"
-msgstr "<literal>swift</literal> - Object Storage API"
-
-#: ./doc/common/section_cli_install.xml187(para)
-msgid "<literal>trove</literal> - Database Service API"
-msgstr "<literal>trove</literal> - Database Service API"
-
-#: ./doc/common/section_cli_install.xml191(para)
-msgid ""
-"The following example shows the command for installing the nova client with "
-"<replaceable>pip</replaceable>."
-msgstr "以下の例は、<replaceable>pip</replaceable> を用いて nova クライアントをインストールするコマンドです。"
-
-#: ./doc/common/section_cli_install.xml196(title)
-msgid "Installing with pip"
-msgstr "pip を用いたインストール"
-
-#: ./doc/common/section_cli_install.xml197(para)
-msgid ""
-"Use <package>pip</package> to install the OpenStack clients on a Linux, Mac "
-"OS X, or Microsoft Windows system. It is easy to use and ensures that you "
-"get the latest version of the client from the <link "
-"href=\"http://pypi.python.org/pypi\">Python Package Index</link>. Also, "
-"<package>pip</package> enables you to update or remove a package."
-msgstr "Linux、Mac OS X、Microsoft Windows システムにクライアントをインストールするために <package>pip</package> を使用します。これは使いやすく、必ず <link href=\"http://pypi.python.org/pypi\">Python Package Index</link> から最新バージョンのクライアントを取得します。また、<package>pip</package> がパッケージの更新や削除ができます。"
-
-#: ./doc/common/section_cli_install.xml204(para)
-msgid "Install each client separately by using the following command:"
-msgstr "以下のコマンドを使用して、各クライアントをそれぞれインストールします。"
-
-#: ./doc/common/section_cli_install.xml207(para)
-msgid "For Mac OS X or Linux:"
-msgstr "Mac OS X または Linux の場合:"
-
-#: ./doc/common/section_cli_install.xml209(para)
-msgid "For Microsoft Windows:"
-msgstr "Microsoft Windows の場合:"
-
-#: ./doc/common/section_cli_install.xml214(title)
-msgid "Installing from packages"
-msgstr "パッケージからのインストール"
-
-#: ./doc/common/section_cli_install.xml215(para)
-msgid ""
-"RDO and openSUSE have client packages that can be installed without "
-"<filename>pip</filename>."
-msgstr "RDO と openSUSE は、<filename>pip</filename> なしでインストールできるクライアントパッケージがあります。"
-
-#: ./doc/common/section_cli_install.xml217(para)
-msgid ""
-"On Red Hat Enterprise Linux, CentOS, or Fedora, use <placeholder-1/> to "
-"install the clients from the packaged versions available in <link "
-"href=\"http://openstack.redhat.com/\">RDO</link>: <placeholder-2/>"
-msgstr "Red Hat Enterprise Linux、CentOS、Fedora の場合、<link href=\"http://openstack.redhat.com/\">RDO</link> にあるパッケージ化されたバージョンからクライアントをインストールするために、<placeholder-1/> を使用します。<placeholder-2/>"
-
-#: ./doc/common/section_cli_install.xml223(para)
-msgid ""
-"For openSUSE, use <package>rpm</package> or <package>zypper</package> to "
-"install the clients from the packaged versions available in <link "
-"href=\"https://build.opensuse.org/package/show?package=python-"
-"novaclient&amp;project=Cloud:OpenStack:Master\">the Open Build "
-"Service</link>:<placeholder-1/>"
-msgstr "openSUSE の場合、<link href=\"https://build.opensuse.org/package/show?package=python-novaclient&amp;project=Cloud:OpenStack:Master\">the Open Build Service</link> にあるパッケージ化されたバージョンからクライアントをインストールするために、<package>rpm</package> または <package>zypper</package> を使用します。<placeholder-1/>"
-
-#: ./doc/common/section_cli_install.xml232(title)
-msgid "Upgrade or remove clients"
-msgstr "クライアントの更新や削除"
-
-#: ./doc/common/section_cli_install.xml233(para)
-msgid ""
-"To upgrade a client, add the <literal>--upgrade</literal> option to the "
-"<placeholder-1/> command:"
-msgstr "クライアントを更新する場合、<placeholder-1/> コマンドに <literal>--upgrade</literal> オプションを追加します。"
-
-#: ./doc/common/section_cli_install.xml237(para)
-msgid "To remove the a client, run the <placeholder-1/> command:"
-msgstr "クライアントを削除する場合、<placeholder-1/> コマンドを実行します。"
-
-#: ./doc/common/section_cli_install.xml242(title)
-msgid "What's next"
-msgstr "次はどうする"
-
-#: ./doc/common/section_cli_install.xml243(para)
-msgid ""
-"Before you can run client commands, you must create and source the "
-"<filename><replaceable>PROJECT</replaceable>-openrc.sh</filename> file to "
-"set environment variables. See <xref linkend=\"cli_openrc\"/>."
-msgstr "クライアントコマンドを実行する前に、環境変数を設定するために <filename><replaceable>PROJECT</replaceable>-openrc.sh</filename> ファイルを作成して読み込む必要があります。"
-
-#: ./doc/common/section_keystone-concepts-service-management.xml5(title)
-msgid "Service management"
-msgstr "サービス管理"
+"Object servers (<systemitem class=\"service\">swift-object-"
+"server</systemitem>)"
+msgstr ""
 
-#: ./doc/common/section_keystone-concepts-service-management.xml6(para)
-msgid ""
-"The Identity Service provides identity, token, catalog, and policy services."
-" It consists of:"
+#: ./doc/common/section_getstart_object-storage.xml34(para)
+msgid "Manages actual objects,such as files, on the storage nodes."
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts-service-management.xml11(para)
-msgid ""
-"<systemitem class=\"service\">keystone-all</systemitem>. Starts both the "
-"service and administrative APIs in a single process to provide Catalog, "
-"Authorization, and Authentication services for OpenStack."
+#: ./doc/common/section_getstart_object-storage.xml38(term)
+msgid "Various periodic processes"
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts-service-management.xml17(para)
+#: ./doc/common/section_getstart_object-storage.xml39(para)
 msgid ""
-"Identity Service functions. Each has a pluggable back end that allows "
-"different ways to use the particular service. Most support standard back "
-"ends like LDAP or SQL."
+"Performs housekeeping tasks on the large data store. The replication "
+"services ensure consistency and availability through the cluster. Other "
+"periodic processes include auditors, updaters, and reapers."
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts-service-management.xml23(para)
-msgid ""
-"The Identity Service also maintains a user that corresponds to each service,"
-" such as, a user named <emphasis>nova</emphasis> for the Compute service, "
-"and a special service tenant called <emphasis>service</emphasis>."
+#: ./doc/common/section_getstart_object-storage.xml45(term)
+msgid "WSGI middleware"
 msgstr ""
 
-#: ./doc/common/section_keystone-concepts-service-management.xml28(para)
-msgid ""
-"For information about how to create services and endpoints, see the <link "
-"href=\"http://docs.openstack.org/user-guide-"
-"admin/content/index.html\"><citetitle>OpenStack Admin User "
-"Guide</citetitle></link>."
+#: ./doc/common/section_getstart_object-storage.xml46(para)
+msgid "Handles authentication and is usually OpenStack Identity."
 msgstr ""
 
 #: ./doc/common/ch_cli_trove_commands.xml11(title)
@@ -23685,6 +17343,2851 @@ msgstr ""
 msgid "Optional new host of user."
 msgstr ""
 
+#: ./doc/common/section_dashboard-configure-https.xml4(title)
+msgid "Configure the dashboard for HTTPS"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml5(para)
+#: ./doc/common/section_dashboard-configure.xml10(para)
+msgid ""
+"You can configure the dashboard for a secured HTTPS deployment. While the "
+"standard installation uses a non-encrypted HTTP channel, you can enable SSL "
+"support for the dashboard."
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml9(para)
+msgid ""
+"The following example uses the domain, \"http://openstack.example.com.\" Use"
+" a domain that fits your current setup."
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml13(para)
+msgid ""
+"In<filename>/etc/openstack-dashboard/local_settings.py</filename> update the"
+" following directives:"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml19(para)
+msgid ""
+"The first option is required to enable HTTPS. The other recommended settings"
+" defend against cross-site scripting and require HTTPS."
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml24(para)
+msgid ""
+"Edit <filename>/etc/apache2/ports.conf</filename> and add the following "
+"line:"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml30(para)
+msgid ""
+"Edit <filename>/etc/apache2/conf.d/openstack-dashboard.conf:</filename>"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml33(para)
+msgid "Before:"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml46(para)
+msgid "After:"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml87(para)
+msgid ""
+"In this configuration, Apache http server listens on the port 443 and "
+"redirects all the hits to the HTTPS protocol for all the non-secured "
+"requests. The secured section defines the private key, public key, and "
+"certificate to use."
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml94(para)
+msgid "Restart Apache http server. For Debian/Ubuntu/SUSE:"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml96(para)
+msgid "Or for Fedora/RHEL/CentOS:"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-https.xml100(para)
+msgid ""
+"If you try to access the dashboard through HTTP, the browser redirects you "
+"to the HTTPS page."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_volumes.xml8(title)
+msgid "Manage Volumes"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_volumes.xml9(para)
+msgid ""
+"Depending on the setup of your cloud provider, they may give you an endpoint"
+" to use to manage volumes, or there may be an extension under the covers. In"
+" either case, you can use the <placeholder-1/> CLI to manage volumes:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_volumes.xml26(para)
+msgid "For example, to list IDs and names of Compute volumes, run:"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-console.xml5(title)
+msgid "Configure remote console access"
+msgstr ""
+
+#. <?dbhtml stop-chunking?>
+#: ./doc/common/section_compute-configure-console.xml7(para)
+msgid ""
+"To provide a remote console or remote desktop access to guest virtual "
+"machines, use VNC or SPICE HTML5 through either the OpenStack dashboard or "
+"the command line. Best practice is to select one or the other to run."
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-characteristics.xml49(None)
+msgid ""
+"@@image: '../common/figures/objectstorage.png'; "
+"md5=e26e374ace84070f5fed24e73adcd562"
+msgstr "@@image: '../common/figures/objectstorage.png'; md5=e26e374ace84070f5fed24e73adcd562"
+
+#: ./doc/common/section_objectstorage-characteristics.xml7(title)
+msgid "Object Storage characteristics"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml8(para)
+msgid "The key characteristics of Object Storage are that:"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml11(para)
+msgid "All objects stored in Object Storage have a URL."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml14(para)
+msgid ""
+"All objects stored are replicated 3✕ in as-unique-as-possible zones, which "
+"can be defined as a group of drives, a node, a rack, and so on."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml18(para)
+msgid "All objects have their own metadata."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml21(para)
+msgid ""
+"Developers interact with the object storage system through a RESTful HTTP "
+"API."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml25(para)
+msgid "Object data can be located anywhere in the cluster."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml28(para)
+msgid ""
+"The cluster scales by adding additional nodes without sacrificing "
+"performance, which allows a more cost-effective linear storage expansion "
+"than fork-lift upgrades."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml33(para)
+msgid "Data doesn't have to be migrate to an entirely new storage system."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml36(para)
+msgid "New nodes can be added to the cluster without downtime."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml39(para)
+msgid "Failed nodes and disks can be swapped out without downtime."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml42(para)
+msgid ""
+"It runs on industry-standard hardware, such as Dell, HP, and Supermicro."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-characteristics.xml53(para)
+msgid ""
+"Developers can either write directly to the Swift API or use one of the many"
+" client libraries that exist for all of the popular programming languages, "
+"such as Java, Python, Ruby, and C#. Amazon S3 and RackSpace Cloud Files "
+"users should be very familiar with Object Storage. Users new to object "
+"storage systems will have to adjust to a different approach and mindset than"
+" those required for a traditional filesystem."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml6(title)
+msgid "Stop and start an instance"
+msgstr "インスタンスの停止と起動"
+
+#: ./doc/common/section_cli_nova_startstop.xml7(para)
+msgid "Use one of the following methods to stop and start an instance."
+msgstr "以下の手段の 1 つを使用して、インスタンスを停止して起動します。"
+
+#: ./doc/common/section_cli_nova_startstop.xml10(title)
+msgid "Pause and unpause an instance"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml13(para)
+msgid "To pause an instance, run the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml15(para)
+msgid ""
+"This command stores the state of the VM in RAM. A paused instance continues "
+"to run in a frozen state."
+msgstr "このコマンドは、RAM に仮想マシンの状態を保存します。一時停止となったインスタンスは、一時停止した状態で実行が継続されます。"
+
+#: ./doc/common/section_cli_nova_startstop.xml17(para)
+msgid "To unpause the instance, run the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml23(title)
+msgid "Suspend and resume an instance"
+msgstr "インスタンスの休止と再開"
+
+#: ./doc/common/section_cli_nova_startstop.xml25(para)
+msgid ""
+"Administrative users might want to suspend an instance if it is infrequently"
+" used or to perform system maintenance. When you suspend an instance, its VM"
+" state is stored on disk, all memory is written to disk, and the virtual "
+"machine is stopped. Suspending an instance is similar to placing a device in"
+" hibernation; memory and vCPUs become available to create other instances."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml33(para)
+msgid ""
+"To initiate a hypervisor-level suspend operation, run the following command:"
+msgstr "イパーバイザーレベルの休止操作を開始するには、以下のコマンドを実行します。"
+
+#: ./doc/common/section_cli_nova_startstop.xml38(para)
+msgid "To resume a suspended instance, run the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml45(title)
+msgid "Shelve and unshelve an instance"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml46(para)
+msgid ""
+"Shelving is useful if you have an instance that you are not using, but would"
+" like retain in your list of servers. For example, you can stop an instance "
+"at the end of a work week, and resume work again at the start of the next "
+"week. All associated data and resources are kept; however, anything still in"
+" memory is not retained. If a shelved instance is no longer needed, it can "
+"also be entirely removed."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml51(para)
+msgid "You can complete the following shelving tasks:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml53(term)
+msgid "Shelve an instance"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml54(para)
+msgid ""
+"Shuts down the instance, and stores it together with associated data and "
+"resources (a snapshot is taken if not volume backed). Anything in memory is "
+"lost. Use the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml57(replaceable)
+#: ./doc/common/section_cli_nova_startstop.xml62(replaceable)
+#: ./doc/common/section_cli_nova_startstop.xml69(replaceable)
+msgid "SERVERNAME"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml60(term)
+msgid "Unshelve an instance"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml61(para)
+msgid "Restores the instance:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml65(term)
+msgid "Remove a shelved instance"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_startstop.xml66(para)
+msgid ""
+"Removes the instance from the server; data and resource associations are "
+"deleted. If an instance is no longer needed, you can move that instance off "
+"the hypervisor in order to minimize resource usage:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_metadata.xml9(title)
+msgid "Insert metadata during launch"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_metadata.xml10(para)
+msgid ""
+"When booting a server, you can also add metadata, so that you can more "
+"easily identify it amongst your ever-growing elastic cloud. Use the "
+"<literal>--meta</literal> option with a key=value pair, where you can make "
+"up the string for both the key and the value. For example, you could add a "
+"description and also the creator of the server. <placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_metadata.xml18(para)
+msgid ""
+"When viewing the server information, you can see the metadata included on "
+"the <literal>metadata</literal> line: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml7(title)
+#: ./doc/common/section_dashboard_access.xml105(guilabel)
+#: ./doc/common/section_dashboard_access.xml229(guilabel)
+msgid "Overview"
+msgstr "概要"
+
+#: ./doc/common/section_cli_overview.xml8(para)
+msgid ""
+"Each OpenStack project provides a command-line client, which enables you to "
+"access the project API through easy-to-use commands. For example, the "
+"Compute service provides a nova command-line client."
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml13(para)
+msgid ""
+"You can run the commands from the command line, or include the commands "
+"within scripts to automate tasks. If you provide OpenStack credentials, such"
+" as your user name and password, you can run these commands on any computer."
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml19(para)
+msgid ""
+"Internally, each command uses cURL command-line tools, which embed API "
+"requests. OpenStack APIs are RESTful APIs, and use the HTTP protocol. They "
+"include methods, URIs, media types, and response codes."
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml24(para)
+msgid ""
+"OpenStack APIs are open-source Python clients, and can run on Linux or Mac "
+"OS X systems. On some client commands, you can specify a <placeholder-1/> "
+"parameter to show the underlying API request for the command. This is a good"
+" way to become familiar with the OpenStack API calls."
+msgstr ""
+
+#: ./doc/common/section_cli_overview.xml30(para)
+msgid ""
+"The following table lists the command-line client for each OpenStack service"
+" with its package name and description."
+msgstr "以下の表は、各 OpenStack サービスのコマンドラインクライアント、そのパッケージ名、説明の一覧です。"
+
+#: ./doc/common/section_cli_overview.xml33(caption)
+msgid "OpenStack services and clients"
+msgstr "OpenStack のサービスとクライアント"
+
+#: ./doc/common/section_cli_overview.xml40(th)
+#: ./doc/common/ch_getstart.xml29(th)
+#: ./doc/common/section_keystone-concepts.xml83(term)
+msgid "Service"
+msgstr "サービス"
+
+#: ./doc/common/section_cli_overview.xml41(th)
+msgid "Client"
+msgstr "クライアント"
+
+#: ./doc/common/section_cli_overview.xml42(th)
+msgid "Package"
+msgstr "パッケージ"
+
+#: ./doc/common/section_cli_overview.xml48(td)
+#: ./doc/common/ch_getstart.xml99(glossterm)
+msgid "Block Storage"
+msgstr "Block Storage"
+
+#: ./doc/common/section_cli_overview.xml50(package)
+msgid "python-cinderclient"
+msgstr "python-cinderclient"
+
+#: ./doc/common/section_cli_overview.xml51(td)
+msgid "Create and manage volumes."
+msgstr "ボリュームを作成、管理します。"
+
+#: ./doc/common/section_cli_overview.xml54(td)
+#: ./doc/common/section_dashboard_access.xml100(guilabel)
+#: ./doc/common/ch_getstart.xml52(glossterm)
+msgid "Compute"
+msgstr "Compute"
+
+#: ./doc/common/section_cli_overview.xml56(package)
+msgid "python-novaclient"
+msgstr "python-novaclient"
+
+#: ./doc/common/section_cli_overview.xml57(td)
+msgid "Create and manage images, instances, and flavors."
+msgstr "イメージ、インスタンス、フレーバーを作成、管理します。"
+
+#: ./doc/common/section_cli_overview.xml60(td)
+#: ./doc/common/ch_getstart.xml172(glossterm)
+msgid "Database Service"
+msgstr "Database"
+
+#: ./doc/common/section_cli_overview.xml62(package)
+msgid "python-troveclient"
+msgstr "python-troveclient"
+
+#: ./doc/common/section_cli_overview.xml63(td)
+msgid "Create and manage databases."
+msgstr "データベースを作成、管理します。"
+
+#: ./doc/common/section_cli_overview.xml66(td)
+msgid "Identity"
+msgstr "Identity"
+
+#: ./doc/common/section_cli_overview.xml68(package)
+msgid "python-keystoneclient"
+msgstr "python-keystoneclient"
+
+#: ./doc/common/section_cli_overview.xml69(td)
+msgid "Create and manage users, tenants, roles, endpoints, and credentials."
+msgstr "ユーザー、プロジェクト、ロール、エンドポイント、クレデンシャルを作成、管理します。"
+
+#: ./doc/common/section_cli_overview.xml72(td)
+#: ./doc/common/ch_getstart.xml127(glossterm)
+msgid "Image Service"
+msgstr "Image Service"
+
+#: ./doc/common/section_cli_overview.xml74(package)
+msgid "python-glanceclient"
+msgstr "python-glanceclient"
+
+#: ./doc/common/section_cli_overview.xml75(td)
+msgid "Create and manage images."
+msgstr "イメージを作成、管理します。"
+
+#: ./doc/common/section_cli_overview.xml78(td)
+#: ./doc/common/ch_getstart.xml66(glossterm)
+msgid "Networking"
+msgstr "Networking"
+
+#: ./doc/common/section_cli_overview.xml80(package)
+msgid "python-neutronclient"
+msgstr "python-neutronclient"
+
+#: ./doc/common/section_cli_overview.xml81(td)
+msgid ""
+"Configure networks for guest servers. This client was previously called "
+"<placeholder-1/>."
+msgstr "ゲストサーバー用のネットワークを設定します。このクライアントは以前 <placeholder-1/> と呼ばれていました。"
+
+#: ./doc/common/section_cli_overview.xml85(td)
+#: ./doc/common/ch_getstart.xml83(glossterm)
+msgid "Object Storage"
+msgstr "Object Storage"
+
+#: ./doc/common/section_cli_overview.xml87(package)
+msgid "python-swiftclient"
+msgstr "python-swiftclient"
+
+#: ./doc/common/section_cli_overview.xml88(td)
+msgid ""
+"Gather statistics, list items, update metadata, and upload, download, and "
+"delete files stored by the Object Storage service. Gain access to an Object "
+"Storage installation for ad hoc processing."
+msgstr "統計情報を収集し、項目を一覧表示し、メタデータを更新し、Object Storage サービスにより保存されたファイルをアップロード、ダウンロード、削除します。"
+
+#: ./doc/common/section_cli_overview.xml93(td)
+#: ./doc/common/section_dashboard_access.xml192(guilabel)
+#: ./doc/common/ch_getstart.xml157(glossterm)
+msgid "Orchestration"
+msgstr "Orchestration"
+
+#: ./doc/common/section_cli_overview.xml95(package)
+msgid "python-heatclient"
+msgstr "python-heatclient"
+
+#: ./doc/common/section_cli_overview.xml96(td)
+msgid ""
+"Launch stacks from templates, view details of running stacks including "
+"events and resources, and update and delete stacks."
+msgstr "テンプレートからスタックを起動し、イベントやリソースを含む実行中のスタックの詳細を表示し、スタックを更新、削除します。"
+
+#: ./doc/common/section_cli_overview.xml100(td)
+#: ./doc/common/ch_getstart.xml142(glossterm)
+msgid "Telemetry"
+msgstr "Telemetry"
+
+#: ./doc/common/section_cli_overview.xml102(package)
+msgid "python-ceilometerclient"
+msgstr "python-ceilometerclient"
+
+#: ./doc/common/section_cli_overview.xml103(td)
+msgid "Create and collect measurements across OpenStack."
+msgstr "OpenStack 全体の測定項目を作成、収集します。"
+
+#: ./doc/common/section_cli_overview.xml107(para)
+msgid "An OpenStack <placeholder-1/> client is in development."
+msgstr "OpenStack <placeholder-1/> クライアントが開発中です。"
+
+#: ./doc/common/section_cli_overview.xml109(para)
+msgid ""
+"For client installation instructions, see <link "
+"href=\"http://docs.openstack.org/user-"
+"guide/content/install_clients.html\">Install the OpenStack command-line "
+"clients</link>. For information about the OpenStack RC file, see <link "
+"href=\"http://docs.openstack.org/user-"
+"guide/content/cli_openrc.html\">Download and source the OpenStack RC "
+"file</link>."
+msgstr "クライアントのインストールの説明は <link href=\"http://docs.openstack.org/user-guide/content/install_clients.html\">OpenStack コマンドラインクライアントのインストール</link>を参照してください。OpenStack RC ファイルに関する情報は <link href=\"http://docs.openstack.org/user-guide/content/cli_openrc.html\">OpenStack RC ファイルのダウンロードと読み込み</link>を参照してください。"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_getstart_logical_arch.xml38(None)
+msgid ""
+"@@image: 'figures/openstack-arch-havana-logical-v1.jpg'; "
+"md5=e7acaaee72722626b045eda3fae81841"
+msgstr "@@image: 'figures/openstack-arch-havana-logical-v1.jpg'; md5=e7acaaee72722626b045eda3fae81841"
+
+#: ./doc/common/section_getstart_logical_arch.xml5(title)
+#: ./doc/common/section_getstart_logical_arch.xml33(title)
+msgid "Logical architecture"
+msgstr "論理アーキテクチャー"
+
+#: ./doc/common/section_getstart_logical_arch.xml6(para)
+msgid ""
+"To design, deploy, and configure OpenStack, administrators must understand "
+"the logical architecture."
+msgstr "クラウド管理者は、OpenStack を設計、導入、設定するために、論理アーキテクチャーを理解する必要があります。"
+
+#: ./doc/common/section_getstart_logical_arch.xml7(para)
+msgid "OpenStack modules are one of the following types:"
+msgstr "OpenStack のモジュールは以下の種別のどれかです。"
+
+#: ./doc/common/section_getstart_logical_arch.xml9(term)
+msgid "Daemon"
+msgstr ""
+
+#: ./doc/common/section_getstart_logical_arch.xml11(para)
+msgid ""
+"Runs as a background process. On Linux platforms, a daemon is usually "
+"installed as a service."
+msgstr ""
+
+#: ./doc/common/section_getstart_logical_arch.xml15(term)
+msgid "Script"
+msgstr ""
+
+#: ./doc/common/section_getstart_logical_arch.xml17(para)
+msgid ""
+"Installs a virtual environment and runs tests. For example, the "
+"<code>run_tests.sh</code> script installs a virtual environment and runs "
+"unit tests on a service."
+msgstr ""
+
+#: ./doc/common/section_getstart_logical_arch.xml21(term)
+msgid "Command-line interface (CLI)"
+msgstr ""
+
+#: ./doc/common/section_getstart_logical_arch.xml23(para)
+msgid ""
+"Enables users to submit API calls to OpenStack services through easy-to-use "
+"commands."
+msgstr ""
+
+#: ./doc/common/section_getstart_logical_arch.xml29(para)
+msgid ""
+"The following diagram shows the most common, but not the only, architecture "
+"for an OpenStack cloud:"
+msgstr "以下の図は、最も一般的ですが、唯一のものではない、OpenStack クラウドのアーキテクチャーを示します。"
+
+#: ./doc/common/section_getstart_logical_arch.xml42(para)
+msgid ""
+"As in <xref linkend=\"concept_arch\"/>, end users can interact through the "
+"dashboard, CLIs, and APIs. All services authenticate through a common "
+"Identity Service and individual services interact with each other through "
+"public APIs, except where privileged administrator commands are necessary."
+msgstr "<xref linkend=\"concept_arch\"/> にあるとおり、エンドユーザーはダッシュボード、CLI、API 経由で操作できます。すべてのサービスは共通の Identity Service 経由で認証されます。個々のサービスは、特権管理コマンドが必要となる場合を除いて、お互いにパブリック API 経由で相互作用します。"
+
+#: ./doc/common/section_cli_neutron-quotas.xml6(title)
+msgid "Manage Networking service quotas"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml7(para)
+msgid ""
+"A quota limits the number of available resources. A default quota might be "
+"enforced for all tenants. When you try to create more resources than the "
+"quota allows, an error occurs:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml12(para)
+msgid ""
+"Per-tenant quota configuration is also supported by the quota extension API."
+" See <link linkend=\"cfg_quotas_per_tenant\"> Per-tenant quota "
+"configuration</link> for details."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml16(title)
+msgid "Basic quota configuration"
+msgstr "基本的なクォータ設定"
+
+#: ./doc/common/section_cli_neutron-quotas.xml17(para)
+msgid ""
+"In the Networking default quota mechanism, all tenants have the same quota "
+"values, such as the number of resources that a tenant can create."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml20(para)
+msgid ""
+"The quota value is defined in the OpenStack Networking "
+"<filename>neutron.conf</filename> configuration file. To disable quotas for "
+"a specific resource, such as network, subnet, or port, remove a "
+"corresponding item from <option>quota_items</option>. This example shows the"
+" default quota values:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml41(para)
+msgid ""
+"OpenStack Networking also supports quotas for L3 resources: router and "
+"floating IP. Add these lines to the <literal>quotas</literal> section in the"
+" <filename>neutron.conf</filename> file."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml52(para)
+#: ./doc/common/section_cli_neutron-quotas.xml67(para)
+msgid "The <option>quota_items</option> option does not affect these quotas."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml55(para)
+msgid ""
+"OpenStack Networking also supports quotas for security group resources: "
+"number of security groups and the number of rules for each security group. "
+"Add these lines to the <literal>quotas</literal> section in the "
+"<filename>neutron.conf</filename> file:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml72(title)
+msgid "Configure per-tenant quotas"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml73(para)
+msgid ""
+"OpenStack Networking also supports per-tenant quota limit by quota extension"
+" API."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml77(para)
+msgid "<placeholder-1/>. Deletes defined quotas for a specified tenant."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml81(para)
+msgid "<placeholder-1/>. Lists defined quotas for all tenants."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml85(para)
+msgid "<placeholder-1/>. Shows quotas for a specified tenant."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml89(para)
+msgid "<placeholder-1/>. Updates quotas for a specified tenant."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml75(para)
+msgid ""
+"Use these commands to manage per-tenant quotas:<placeholder-1/>Only users "
+"with the <literal>admin</literal> role can change a quota value. By default,"
+" the default set of quotas are enforced for all tenants, so no "
+"<placeholder-2/> command exists."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml98(title)
+msgid "Configure Networking to show per-tenant quotas"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml99(para)
+msgid ""
+"Set the <literal>quota_driver</literal> option in the "
+"<literal>neutron.conf</literal> file:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml102(para)
+msgid ""
+"When you set this option, the output for Networking commands shows "
+"<literal>quotas</literal>."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml106(title)
+msgid "List Networking extensions"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml107(para)
+msgid "To list the Networking extensions, run this command:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml110(para)
+msgid ""
+"The command shows the <literal>quotas</literal> extension, which provides "
+"per-tenant quota management support:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml128(title)
+msgid "Show information for the quotas extension"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml129(para)
+msgid ""
+"To show information for the <literal>quotas</literal> extension, run this "
+"command:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml143(para)
+msgid ""
+"Only some plug-ins support per-tenant quotas. Specifically, Open vSwitch, "
+"Linux Bridge, and VMware NSX support them, but new versions of other plug-"
+"ins might bring additional functionality. See the documentation for each "
+"plug-in."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml151(title)
+msgid "List tenants who have per-tenant quota support"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml152(para)
+msgid ""
+"The <placeholder-1/> command lists tenants for which the per-tenant quota is"
+" enabled. The command does not list tenants with default quota support. You "
+"must be an administrative user to run this command:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml165(title)
+msgid "Show per-tenant quota values"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml166(para)
+msgid ""
+"The <placeholder-1/> reports the current set of quota limits for the "
+"specified tenant. Non-administrative users can run this command without the "
+"<parameter>--tenant_id</parameter> parameter. If per-tenant quota limits are"
+" not enabled for the tenant, the command shows the default set of quotas:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml182(para)
+msgid ""
+"The following command shows the command output for a non-administrative "
+"user:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml196(title)
+msgid "Update quota values for a specified tenant"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml197(para)
+msgid ""
+"Use the <placeholder-1/> command to update a quota for a specified tenant:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml209(para)
+msgid "You can update quotas for multiple resources through one command:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml221(para)
+msgid ""
+"To update the limits for an L3 resource such as, router or floating IP, you "
+"must define new values for the quotas after the <parameter>--</parameter> "
+"directive."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml224(para)
+msgid ""
+"This example updates the limit of the number of floating IPs for the "
+"specified tenant:"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml236(para)
+msgid ""
+"You can update the limits of multiple resources by including L2 resources "
+"and L3 resource through one command."
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml251(title)
+msgid "Delete per-tenant quota values"
+msgstr ""
+
+#: ./doc/common/section_cli_neutron-quotas.xml252(para)
+msgid "To clear per-tenant quota limits, use the <placeholder-1/> command:"
+msgstr "テナントごとのクォータ制限を解除するために、<placeholder-1/> コマンドを使用します。"
+
+#: ./doc/common/section_cli_neutron-quotas.xml256(para)
+msgid ""
+"After you run this command, you can see that quota values for the tenant are"
+" reset to the default values:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml10(title)
+msgid "Host aggregates"
+msgstr "ホスト・アグリゲート"
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml11(para)
+msgid ""
+"Host aggregates are a mechanism to further partition an availability zone; "
+"while availability zones are visible to users, host aggregates are only "
+"visible to administrators. Host Aggregates provide a mechanism to allow "
+"administrators to assign key-value pairs to groups of machines. Each node "
+"can have multiple aggregates, each aggregate can have multiple key-value "
+"pairs, and the same key-value pair can be assigned to multiple aggregates. "
+"This information can be used in the scheduler to enable advanced scheduling,"
+" to set up hypervisor resource pools or to define logical groups for "
+"migration."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml23(title)
+msgid "Command-line interface"
+msgstr "コマンドラインインターフェース"
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml35(replaceable)
+#: ./doc/common/section_cli_nova_host_aggregates.xml111(replaceable)
+msgid "&lt;name&gt;"
+msgstr "&lt;name&gt;"
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml36(replaceable)
+msgid "&lt;availability-zone&gt;"
+msgstr "&lt;availability-zone&gt;"
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml38(para)
+msgid ""
+"Create a new aggregate named <replaceable>&lt;name&gt;</replaceable> in "
+"availability zone <replaceable>&lt;availability-zone&gt;</replaceable>. "
+"Returns the ID of the newly created aggregate. Hosts can be made available "
+"to multiple availability zones, but administrators should be careful when "
+"adding the host to a different host aggregate within the same availability "
+"zone and pay attention when using the <placeholder-1/> and <placeholder-2/> "
+"commands to avoid user confusion when they boot instances in different "
+"availability zones. An error occurs if you cannot add a particular host to "
+"an aggregate zone for which it is not intended."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml60(replaceable)
+#: ./doc/common/section_cli_nova_host_aggregates.xml68(replaceable)
+#: ./doc/common/section_cli_nova_host_aggregates.xml76(replaceable)
+#: ./doc/common/section_cli_nova_host_aggregates.xml87(replaceable)
+#: ./doc/common/section_cli_nova_host_aggregates.xml98(replaceable)
+#: ./doc/common/section_cli_nova_host_aggregates.xml110(replaceable)
+msgid "&lt;id&gt;"
+msgstr "&lt;id&gt;"
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml62(para)
+msgid "Delete an aggregate with id <replaceable>&lt;id&gt;</replaceable>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml70(para)
+msgid ""
+"Show details of the aggregate with id <replaceable>&lt;id&gt;</replaceable>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml77(replaceable)
+#: ./doc/common/section_cli_nova_host_aggregates.xml88(replaceable)
+msgid "&lt;host&gt;"
+msgstr "&lt;host&gt;"
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml79(para)
+msgid ""
+"Add host with name <replaceable>&lt;host&gt;</replaceable> to aggregate with"
+" id <replaceable>&lt;id&gt;</replaceable>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml90(para)
+msgid ""
+"Remove the host with name <replaceable>&lt;host&gt;</replaceable> from the "
+"aggregate with id <replaceable>&lt;id&gt;</replaceable>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml99(replaceable)
+#: ./doc/common/section_cli_nova_host_aggregates.xml100(replaceable)
+msgid "&lt;key=value&gt;"
+msgstr "&lt;key=value&gt;"
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml103(para)
+msgid ""
+"Add or update metadata (key-value pairs) associated with the aggregate with "
+"id <replaceable>&lt;id&gt;</replaceable>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml112(replaceable)
+msgid "&lt;availability_zone&gt;"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml114(para)
+msgid "Update the name and availability zone (optional) for the aggregate."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml128(para)
+msgid "Put/resume host into/from maintenance."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml24(para)
+msgid ""
+"The <placeholder-1/> command-line tool supports the following aggregate-"
+"related commands. <placeholder-2/>"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml134(para)
+msgid ""
+"Only administrators can access these commands. If you try to use these "
+"commands and the user name and tenant that you use to access the Compute "
+"service do not have the <literal>admin</literal> role or the appropriate "
+"privileges, these errors occur:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml146(title)
+msgid "Configure scheduler to support host aggregates"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml147(para)
+msgid ""
+"One common use case for host aggregates is when you want to support "
+"scheduling instances to a subset of compute hosts because they have a "
+"specific capability. For example, you may want to allow users to request "
+"compute hosts that have SSD drives if they need access to faster disk I/O, "
+"or access to compute hosts that have GPU cards to take advantage of GPU-"
+"accelerated code."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml154(para)
+msgid ""
+"To configure the scheduler to support host aggregates, the "
+"<literal>scheduler_default_filters</literal> configuration option must "
+"contain the <literal>AggregateInstanceExtraSpecsFilter</literal> in addition"
+" to the other filters used by the scheduler. Add the following line to "
+"<filename>/etc/nova/nova.conf</filename> on the host that runs the "
+"<systemitem class=\"service\">nova-scheduler</systemitem> service to enable "
+"host aggregates filtering, as well as the other filters that are typically "
+"enabled:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml168(title)
+msgid "Example: Specify compute hosts with SSDs"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml169(para)
+msgid ""
+"This example configures the Compute service to enable users to request nodes"
+" that have solid-state drives (SSDs). You create a <literal>fast-"
+"io</literal> host aggregate in the <literal>nova</literal> availability zone"
+" and you add the <literal>ssd=true</literal> key-value pair to the "
+"aggregate. Then, you add the <literal>node1</literal>, and "
+"<literal>node2</literal> compute nodes to it."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml204(para)
+msgid ""
+"Use the <placeholder-1/> command to create the "
+"<replaceable>ssd.large</replaceable> flavor called with an ID of 6, 8GB of "
+"RAM, 80GB root disk, and four vCPUs."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml207(replaceable)
+#: ./doc/common/section_cli_nova_host_aggregates.xml219(replaceable)
+msgid "ssd.large"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml207(replaceable)
+msgid "6"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml207(replaceable)
+msgid "8192"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml207(replaceable)
+msgid "80"
+msgstr "80"
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml207(replaceable)
+msgid "4"
+msgstr "4"
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml213(para)
+msgid ""
+"Once the flavor is created, specify one or more key-value pairs that match "
+"the key-value pairs on the host aggregates. In this case, that is the "
+"<replaceable>ssd=true</replaceable> key-value pair. Setting a key-value pair"
+" on a flavor is done using the <placeholder-1/> command."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml219(replaceable)
+msgid "ssd=true"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml220(para)
+msgid ""
+"Once it is set, you should see the <literal>extra_specs</literal> property "
+"of the <literal>ssd.large</literal> flavor populated with a key of "
+"<literal>ssd</literal> and a corresponding value of <literal>true</literal>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml241(para)
+msgid ""
+"Now, when a user requests an instance with the <literal>ssd.large</literal> "
+"flavor, the scheduler only considers hosts with the "
+"<literal>ssd=true</literal> key-value pair. In this example, these are "
+"<literal>node1</literal> and <literal>node2</literal>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml249(title)
+msgid "XenServer hypervisor pools to support live migration"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_host_aggregates.xml251(para)
+msgid ""
+"When using the XenAPI-based hypervisor, the Compute service uses host "
+"aggregates to manage XenServer Resource pools, which are used in supporting "
+"live migration."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml6(title)
+#: ./doc/common/section_objectstorage-components.xml192(title)
+msgid "Replication"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml7(para)
+msgid ""
+"Because each replica in Object Storage functions independently and clients "
+"generally require only a simple majority of nodes to respond to consider an "
+"operation successful, transient failures like network partitions can quickly"
+" cause replicas to diverge. These differences are eventually reconciled by "
+"asynchronous, peer-to-peer replicator processes. The replicator processes "
+"traverse their local file systems and concurrently perform operations in a "
+"manner that balances load across physical disks."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml16(para)
+msgid ""
+"Replication uses a push model, with records and files generally only being "
+"copied from local to remote replicas. This is important because data on the "
+"node might not belong there (as in the case of hand offs and ring changes), "
+"and a replicator cannot know which data it should pull in from elsewhere in "
+"the cluster. Any node that contains data must ensure that data gets to where"
+" it belongs. The ring handles replica placement."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml24(para)
+msgid ""
+"To replicate deletions in addition to creations, every deleted record or "
+"file in the system is marked by a tombstone. The replication process cleans "
+"up tombstones after a time period known as the <emphasis "
+"role=\"italic\">consistency window</emphasis>. This window defines the "
+"duration of the replication and how long transient failure can remove a node"
+" from the cluster. Tombstone cleanup must be tied to replication to reach "
+"replica convergence."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml32(para)
+msgid ""
+"If a replicator detects that a remote drive has failed, the replicator uses "
+"the <literal>get_more_nodes</literal> interface for the ring to choose an "
+"alternate node with which to synchronize. The replicator can maintain "
+"desired levels of replication during disk failures, though some replicas "
+"might not be in an immediately usable location."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml39(para)
+msgid ""
+"The replicator does not maintain desired levels of replication when failures"
+" such as entire node failures occur; most failures are transient."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml43(para)
+msgid "The main replication types are:"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml46(para)
+msgid ""
+"<emphasis role=\"bold\">Database replication</emphasis>. Replicates "
+"containers and objects."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml51(para)
+msgid ""
+"<emphasis role=\"bold\">Object replication</emphasis>. Replicates object "
+"data."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml56(title)
+msgid "Database replication"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml57(para)
+msgid ""
+"Database replication completes a low-cost hash comparison to determine "
+"whether two replicas already match. Normally, this check can quickly verify "
+"that most databases in the system are already synchronized. If the hashes "
+"differ, the replicator synchronizes the databases by sharing records added "
+"since the last synchronization point."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml64(para)
+msgid ""
+"This synchronization point is a high water mark that notes the last record "
+"at which two databases were known to be synchronized, and is stored in each "
+"database as a tuple of the remote database ID and record ID. Database IDs "
+"are unique across all replicas of the database, and record IDs are "
+"monotonically increasing integers. After all new records are pushed to the "
+"remote database, the entire synchronization table of the local database is "
+"pushed, so the remote database can guarantee that it is synchronized with "
+"everything with which the local database was previously synchronized."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml75(para)
+msgid ""
+"If a replica is missing, the whole local database file is transmitted to the"
+" peer by using rsync(1) and is assigned a new unique ID."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml78(para)
+msgid ""
+"In practice, database replication can process hundreds of databases per "
+"concurrency setting per second (up to the number of available CPUs or disks)"
+" and is bound by the number of database transactions that must be performed."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml85(title)
+msgid "Object replication"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml86(para)
+msgid ""
+"The initial implementation of object replication performed an rsync to push "
+"data from a local partition to all remote servers where it was expected to "
+"reside. While this worked at small scale, replication times skyrocketed once"
+" directory structures could no longer be held in RAM. This scheme was "
+"modified to save a hash of the contents for each suffix directory to a per-"
+"partition hashes file. The hash for a suffix directory is no longer valid "
+"when the contents of that suffix directory is modified."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml95(para)
+msgid ""
+"The object replication process reads in hash files and calculates any "
+"invalidated hashes. Then, it transmits the hashes to each remote server that"
+" should hold the partition, and only suffix directories with differing "
+"hashes on the remote server are rsynced. After pushing files to the remote "
+"server, the replication process notifies it to recalculate hashes for the "
+"rsynced suffix directories."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-replication.xml103(para)
+msgid ""
+"The number of uncached directories that object replication must traverse, "
+"usually as a result of invalidated suffix directory hashes, impedes "
+"performance. To provide acceptable replication speeds, object replication is"
+" designed to invalidate around 2 percent of the hash space on a normal node "
+"each day."
+msgstr ""
+
+#: ./doc/common/section_getstart_networking.xml5(title)
+msgid "OpenStack Networking"
+msgstr "OpenStack Networking"
+
+#: ./doc/common/section_getstart_networking.xml6(para)
+msgid ""
+"OpenStack Networking allows you to create and attach interface devices "
+"managed by other OpenStack services to networks. Plug-ins can be implemented"
+" to accomodate different networking equipment and software, providing "
+"flexibility to OpenStack architecture and deployment."
+msgstr ""
+
+#: ./doc/common/section_getstart_networking.xml14(systemitem)
+msgid "neutron-server"
+msgstr "neutron-server"
+
+#: ./doc/common/section_getstart_networking.xml15(para)
+msgid ""
+"Accepts and routes API requests to the appropriate OpenStack Networking "
+"plug-in for action."
+msgstr ""
+
+#: ./doc/common/section_getstart_networking.xml19(term)
+msgid "OpenStack Networking plug-ins and agents"
+msgstr ""
+
+#: ./doc/common/section_getstart_networking.xml20(para)
+msgid ""
+"Plugs and unplugs ports, creates networks or subnets, and provides IP "
+"addressing. These plug-ins and agents differ depending on the vendor and "
+"technologies used in the particular cloud. OpenStack Networking ships with "
+"plug-ins and agents for Cisco virtual and physical switches, NEC OpenFlow "
+"products, Open vSwitch, Linux bridging, Ryu Network Operating System, and "
+"the VMware NSX product."
+msgstr ""
+
+#: ./doc/common/section_getstart_networking.xml27(para)
+msgid ""
+"The common agents are L3 (layer 3), DHCP (dynamic host IP addressing), and a"
+" plug-in agent."
+msgstr ""
+
+#: ./doc/common/section_getstart_networking.xml31(term)
+#: ./doc/common/section_getstart_block-storage.xml35(term)
+msgid "Messaging queue"
+msgstr ""
+
+#: ./doc/common/section_getstart_networking.xml32(para)
+msgid ""
+"Used by most OpenStack Networking installations to route information between"
+" the neutron-server and various agents, as well as a database to store "
+"networking state for particular plug-ins."
+msgstr ""
+
+#: ./doc/common/section_getstart_networking.xml38(para)
+msgid ""
+"OpenStack Networking mainly interacts with OpenStack Compute to provide "
+"networks and connectivity for its instances."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_evacuate.xml6(title)
+msgid "Evacuate instances"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_evacuate.xml7(para)
+msgid ""
+"If a cloud compute node fails due to a hardware malfunction or another "
+"reason, you can evacuate instances to make them available again. You can "
+"choose evacuation parameters for your use case."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_evacuate.xml10(para)
+msgid ""
+"To preserve user data on server disk, you must configure shared storage on "
+"the target host. Also, you must validate that the current VM host is down; "
+"otherwise, the evacuation fails with an error."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_evacuate.xml15(para)
+msgid ""
+"To list hosts and find a different host for the evacuated instance, run:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_evacuate.xml19(para)
+msgid ""
+"Evacuate the instance. You can pass the instance password to the command by "
+"using the <literal>--password &lt;pwd&gt;</literal> option. If you do not "
+"specify a password, one is generated and printed after the command finishes "
+"successfully. The following command evacuates a server without shared "
+"storage from a host that is down to the specified "
+"<replaceable>host_b</replaceable>:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_evacuate.xml24(replaceable)
+#: ./doc/common/section_cli_nova_evacuate.xml40(replaceable)
+msgid "evacuated_server_name"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_evacuate.xml24(replaceable)
+#: ./doc/common/section_cli_nova_evacuate.xml40(replaceable)
+msgid "host_b"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_evacuate.xml25(para)
+msgid ""
+"The instance is booted from a new disk, but preserves its configuration "
+"including its ID, name, uid, IP address, and so on. The command returns a "
+"password:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_evacuate.xml34(para)
+msgid ""
+"To preserve the user disk data on the evacuated server, deploy OpenStack "
+"Compute with a shared file system. To configure your system, see <link "
+"href=\"http://docs.openstack.org/icehouse/config-reference/content"
+"/configuring-openstack-compute-basics.html#section_configuring-compute-"
+"migrations\">Configure migrations</link> in <citetitle>OpenStack "
+"Configuration Reference</citetitle>. In the following example, the password "
+"remains unchanged:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_terminate.xml8(title)
+msgid "Delete an instance"
+msgstr "インスタンスの削除"
+
+#: ./doc/common/section_cli_nova_terminate.xml9(para)
+msgid "When you no longer need an instance, you can delete it."
+msgstr "インスタンスが必要なくなった場合、インスタンスを削除できます。"
+
+#: ./doc/common/section_cli_nova_terminate.xml11(para)
+msgid "List all instances:"
+msgstr "すべてのインスタンスを一覧表示します。"
+
+#: ./doc/common/section_cli_nova_terminate.xml21(para)
+msgid ""
+"Run the <placeholder-1/> command to delete the instance. The following "
+"example shows deletion of the <filename>newServer</filename> instance, which"
+" is in <literal>ERROR</literal> state:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_terminate.xml24(para)
+msgid "The command does not notify that your server was deleted."
+msgstr "このコマンドでは、インスタンスの削除に関する通知はありません。"
+
+#: ./doc/common/section_cli_nova_terminate.xml25(para)
+msgid ""
+"To verify that the server was deleted, run the <placeholder-1/> command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_terminate.xml33(para)
+msgid "The deleted instance does not appear in the list."
+msgstr "この一覧には、削除したインスタンスの表示がなくなっています。"
+
+#: ./doc/common/section_compute-configure-spice.xml6(title)
+msgid "SPICE console"
+msgstr ""
+
+#: ./doc/common/section_compute-configure-spice.xml7(para)
+msgid ""
+"OpenStack Compute supports VNC consoles to guests. The VNC protocol is "
+"fairly limited, lacking support for multiple monitors, bi-directional audio,"
+" reliable cut-and-paste, video streaming and more. SPICE is a new protocol "
+"that aims to address the limitations in VNC and provide good remote desktop "
+"support."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-spice.xml12(para)
+msgid ""
+"SPICE support in OpenStack Compute shares a similar architecture to the VNC "
+"implementation. The OpenStack dashboard uses a SPICE-HTML5 widget in its "
+"console tab that communicates to the <systemitem class=\"service\">nova-"
+"spicehtml5proxy</systemitem> service by using SPICE-over-websockets. The "
+"<systemitem class=\"service\">nova-spicehtml5proxy</systemitem> service "
+"communicates directly with the hypervisor process by using SPICE."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-spice.xml19(para)
+msgid ""
+"VNC must be explicitly disabled to get access to the SPICE console. Set the "
+"<option>vnc_enabled</option> option to <literal>False</literal> in the "
+"<literal>[DEFAULT]</literal> section to disable the VNC console."
+msgstr ""
+
+#: ./doc/common/section_compute-configure-spice.xml22(para)
+msgid ""
+"Use the following options to configure SPICE as the console for OpenStack "
+"Compute:"
+msgstr ""
+
+#: ./doc/common/section_getstart_block-storage.xml5(title)
+msgid "OpenStack Block Storage"
+msgstr "OpenStack Block Storage"
+
+#: ./doc/common/section_getstart_block-storage.xml6(para)
+msgid ""
+"OpenStack Block Storage enables management of volumes, volume snapshots, and"
+" volume types. It consists of the following components:"
+msgstr ""
+
+#: ./doc/common/section_getstart_block-storage.xml11(systemitem)
+msgid "cinder-api"
+msgstr ""
+
+#: ./doc/common/section_getstart_block-storage.xml12(para)
+msgid ""
+"Accepts API requests and routes them to <systemitem class=\"service"
+"\">cinder-volume</systemitem> for action."
+msgstr ""
+
+#: ./doc/common/section_getstart_block-storage.xml17(systemitem)
+msgid "cinder-volume"
+msgstr ""
+
+#: ./doc/common/section_getstart_block-storage.xml18(para)
+msgid ""
+"Responds to requests to read from and write to the OpenStack Block Storage "
+"database to maintain state, interacting with other processes (like "
+"<systemitem class=\"service\">cinder-scheduler</systemitem>) through a "
+"message queue and directly upon block storage providing hardware or "
+"software. It can interact with a variety of storage providers through a "
+"driver architecture."
+msgstr ""
+
+#: ./doc/common/section_getstart_block-storage.xml28(term)
+msgid "<systemitem class=\"service\">cinder-scheduler</systemitem> daemon"
+msgstr ""
+
+#: ./doc/common/section_getstart_block-storage.xml30(para)
+msgid ""
+"Like the <systemitem class=\"service\">nova-scheduler</systemitem>, picks "
+"the optimal block storage provider node on which to create the volume."
+msgstr ""
+
+#: ./doc/common/section_getstart_block-storage.xml36(para)
+msgid "Routes information between the Block Storage processes."
+msgstr ""
+
+#: ./doc/common/section_getstart_block-storage.xml40(para)
+msgid ""
+"OpenStack Block Storage interacts with OpenStack Compute to provide volumes "
+"for instances."
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-vnc-window.xml6(title)
+msgid "Change the size of the dashboard VNC window"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-vnc-window.xml7(para)
+msgid ""
+"The <filename>_detail_vnc.html</filename> file defines the size of the VNC "
+"window. To change the window size, edit this file."
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-vnc-window.xml12(para)
+msgid ""
+"Edit "
+"<filename>/usr/share/pyshared/horizon/dashboards/nova/instances/templates/instances/_detail_vnc.html.</filename>"
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure-vnc-window.xml16(para)
+msgid ""
+"Modify the <literal>width</literal> and <literal>height</literal> "
+"parameters, as follows:"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml6(title)
+msgid "Use the VNC console"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml7(para)
+msgid ""
+"To interact through the VNC console, you can use a VNC client directly, a "
+"special Java client, or a web browser. For information about how to "
+"configure the console, see <xref linkend=\"installing-openstack-"
+"dashboard\"/>."
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml15(title)
+msgid "Get an access URL"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml16(para)
+msgid ""
+"The Compute service enables you to create access_urls through the os-"
+"consoles extension. Support for accessing this URL is provided by the nova "
+"client:"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml19(replaceable)
+#: ./doc/common/section_using-vnc-console.xml25(replaceable)
+#: ./doc/common/section_using-vnc-console.xml52(replaceable)
+#: ./doc/common/section_using-vnc-console.xml65(replaceable)
+msgid "[server_id]"
+msgstr "[server_id]"
+
+#: ./doc/common/section_using-vnc-console.xml19(replaceable)
+msgid "[novnc|xvpvnc]"
+msgstr "[novnc|xvpvnc]"
+
+#: ./doc/common/section_using-vnc-console.xml20(para)
+msgid ""
+"Specify '<literal>novnc</literal>' to get a URL suitable for pasting into a "
+"web browser."
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml22(para)
+msgid ""
+"Specify '<literal>xvpvnc</literal>' for a URL suitable for pasting into the "
+"Java client."
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml24(para)
+msgid "To request a web browser URL:"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml28(title)
+msgid "Access a VNC console with a Java client"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml29(para)
+msgid ""
+"To enable support for the OpenStack Java VNC client in compute, run the "
+"<literal>nova-xvpvncproxy</literal> service."
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml34(para)
+msgid ""
+"<literal>xvpvncproxy_port</literal>=<replaceable>[port]</replaceable> - port"
+" to bind (defaults to 6081)"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml38(para)
+msgid ""
+"<literal>xvpvncproxy_host</literal>=<replaceable>[host]</replaceable> - host"
+" to bind (defaults to 0.0.0.0)"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml42(para)
+msgid ""
+"As a client, you need a special Java client, which is a slightly modified "
+"version of TightVNC that supports our token auth:"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml48(para)
+msgid ""
+"To create a session, request an access URL by using <placeholder-1/>. Then, "
+"run the client as follows."
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml51(para)
+msgid "To get an access URL:"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml53(para)
+msgid "To run the client:"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml54(replaceable)
+msgid "[access_url]"
+msgstr "[access_url]"
+
+#: ./doc/common/section_using-vnc-console.xml59(title)
+msgid "Access a VNC console with a web browser"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml61(para)
+msgid ""
+"Retrieving an access_url for a web browser is similar to the flow for the "
+"Java client."
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml63(para)
+msgid "To get the access URL, run the following command:"
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml66(para)
+msgid "Paste the URL into your web browser."
+msgstr ""
+
+#: ./doc/common/section_using-vnc-console.xml68(para)
+msgid ""
+"Additionally, you can use the OpenStack dashboard, known as horizon, to "
+"access browser-based VNC consoles for instances."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_userdata.xml6(title)
+msgid "Provide user data to instances"
+msgstr "インスタンスへのユーザーデータの提供"
+
+#: ./doc/common/section_cli_nova_userdata.xml7(para)
+msgid ""
+"A <glossterm baseform=\"user data\">user data</glossterm> file is a special "
+"key in the metadata service that holds a file that cloud-aware applications "
+"in the guest instance can access. For example, one application that uses "
+"user data is the <link href=\"https://help.ubuntu.com/community/CloudInit"
+"\">cloud-init</link> system, which is an open-source package from Ubuntu "
+"that is available on various Linux distributions and which handles early "
+"initialization of a cloud instance."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_userdata.xml14(para)
+msgid ""
+"You can place user data in a local file and pass it through the <parameter"
+">--user-data &lt;user-data-file&gt;</parameter> parameter at instance "
+"creation:"
+msgstr "インスタンス作成時に <parameter>--user-data &lt;user-data-file&gt;</parameter> パラメーターを使用して、ローカルファイルのユーザーデータを渡すことができます。"
+
+#: ./doc/common/section_cli_nova_sshkeys.xml6(title)
+msgid "Add keypair"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_sshkeys.xml7(para)
+msgid ""
+"Create at least one keypair for each project. If you have generated a "
+"keypair with an external tool, you can import it into OpenStack. The keypair"
+" can be used for multiple instances that belong to a project."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_sshkeys.xml13(para)
+msgid "Create a key."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_sshkeys.xml14(para)
+msgid ""
+"To create a <literal>mykey</literal> key that you can associate with "
+"instances, run the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_sshkeys.xml17(para)
+msgid ""
+"Save the <filename>mykey.pem</filename> file to a secure location. It "
+"enables root access to any instances with which the <literal>mykey</literal>"
+" key is associated."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_sshkeys.xml22(para)
+msgid "Alternatively, you can import a keypair."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_sshkeys.xml23(para)
+msgid ""
+"To import an existing public key, <literal>mykey.pub</literal>, and "
+"associate it with the <literal>mykey</literal> key, run the following "
+"command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_sshkeys.xml28(para)
+msgid ""
+"You must have the matching private key to access instances that are "
+"associated with this key."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml6(title)
+msgid "Secure the OpenStack Identity service connection to an LDAP back end"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml8(para)
+msgid ""
+"The Identity service supports the use of TLS to encrypt LDAP traffic. Before"
+" configuring this, you must first verify where your certificate authority "
+"file is located. For more information, see <xref linkend=\"certificates-for-"
+"pki\"/>."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml12(para)
+msgid "Once you verify the location of your certificate authority file:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml15(title)
+msgid "Configuring TLS encryption on LDAP traffic"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml17(para)
+msgid ""
+"Open the <filename>/etc/keystone/keystone.conf</filename> configuration "
+"file."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml23(para)
+msgid "Find the <literal>[ldap]</literal> section."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml26(para)
+msgid ""
+"In the <literal>[ldap]</literal> section, set the <literal>use_tls</literal>"
+" configuration key to <literal>True</literal>. Doing so will enable TLS."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml31(para)
+msgid ""
+"Configure the Identity service to use your certificate authorities file. To "
+"do so, set the <literal>tls_cacertfile</literal> configuration key in the "
+"<literal>ldap</literal> section to the certificate authorities file's path."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml37(para)
+msgid ""
+"You can also set the <literal>tls_cacertdir</literal> (also in the "
+"<literal>ldap</literal> section) to the directory where all certificate "
+"authorities files are kept. If both <literal>tls_cacertfile</literal> and "
+"<literal>tls_cacertdir</literal> are set, then the latter will be ignored."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml46(para)
+msgid ""
+"Specify what client certificate checks to perform on incoming TLS sessions "
+"from the LDAP server. To do so, set the <literal>tls_req_cert</literal> "
+"configuration key in the <literal>[ldap]</literal> section to "
+"<literal>demand</literal>, <literal>allow</literal>, or "
+"<literal>never</literal>:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml53(para)
+msgid ""
+"<parameter>demand</parameter>: a certificate will always be requested from "
+"the LDAP server. The session will be terminated if no certificate is "
+"provided, or if the certificate provided cannot be verified against the "
+"existing certificate authorities file."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml60(para)
+msgid ""
+"<parameter>allow</parameter>: a certificate will always be requested from "
+"the LDAP server. The session will proceed as normal even if a certificate is"
+" not provided. If a certificate is provided but it cannot be verified "
+"against the existing certificate authorities file, the certificate will be "
+"ignored and the session will proceed as normal."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml67(para)
+msgid "<parameter>never</parameter>: a certificate will never be requested."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml72(para)
+msgid ""
+"On distributions that include <application>openstack-config</application>, "
+"you can configure TLS encryption on LDAP traffic by running the following "
+"commands instead:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml80(replaceable)
+msgid "CA_FILE"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml82(replaceable)
+msgid "CERT_BEHAVIOR"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml85(para)
+msgid ""
+"<replaceable>CA_FILE</replaceable> is the absolute path to the certificate "
+"authorities file that should be used to encrypt LDAP traffic."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-hardening.xml88(para)
+msgid ""
+"<replaceable>CERT_BEHAVIOR</replaceable>: specifies what client certificate "
+"checks to perform on an incoming TLS session from the LDAP server "
+"(<literal>demand</literal>, <literal>allow</literal>, or "
+"<literal>never</literal>)."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml7(title)
+msgid "Certificates for PKI"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml8(para)
+msgid ""
+"PKI stands for Public Key Infrastructure. Tokens are documents, "
+"cryptographically signed using the X509 standard. In order to work correctly"
+" token generation requires a public/private key pair. The public key must be"
+" signed in an X509 certificate, and the certificate used to sign it must be "
+"available as Certificate Authority (CA) certificate. These files can be "
+"generated either using the <placeholder-1/> utility, or externally "
+"generated. The files need to be in the locations specified by the top level "
+"Identity Service configuration file <filename>keystone.conf</filename> as "
+"specified in the above section. Additionally, the private key should only be"
+" readable by the system user that will run the Identity Service."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml23(para)
+msgid ""
+"The certificates can be world readable, but the private key cannot be. The "
+"private key should only be readable by the account that is going to sign "
+"tokens. When generating files with the <placeholder-1/> command, your best "
+"option is to run as the pki user. If you run nova-manage as root, you can "
+"append --keystone-user and --keystone-group parameters to set the username "
+"and group keystone is going to run under."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml33(para)
+msgid ""
+"The values that specify where to read the certificates are under the "
+"<literal>[signing]</literal> section of the configuration file. The "
+"configuration values are:"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml38(para)
+msgid ""
+"<literal>token_format</literal> - Determines the algorithm used to generate "
+"tokens. Can be either <literal>UUID</literal> or <literal>PKI</literal>. "
+"Defaults to <literal>PKI</literal>."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml45(para)
+msgid ""
+"<literal>certfile</literal> - Location of certificate used to verify tokens."
+" Default is <literal>/etc/keystone/ssl/certs/signing_cert.pem</literal>."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml51(para)
+msgid ""
+"<literal>keyfile</literal> - Location of private key used to sign tokens. "
+"Default is <literal>/etc/keystone/ssl/private/signing_key.pem</literal>."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml57(para)
+msgid ""
+"<literal>ca_certs</literal> - Location of certificate for the authority that"
+" issued the above certificate. Default is "
+"<literal>/etc/keystone/ssl/certs/ca.pem</literal>."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml64(para)
+msgid "<literal>key_size</literal> - Default is <literal>1024</literal>."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml69(para)
+msgid "<literal>valid_days</literal> - Default is <literal>3650</literal>."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml74(para)
+msgid ""
+"<literal>ca_password</literal> - Password required to read the "
+"<literal>ca_file</literal>. Default is <literal>None</literal>."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml80(para)
+msgid ""
+"If <literal>token_format=UUID</literal>, a typical token looks like "
+"<literal>53f7f6ef0cc344b5be706bcc8b1479e1</literal>. If "
+"<literal>token_format=PKI</literal>, a typical token is a much longer "
+"string, such as:"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml113(title)
+msgid "Sign certificate issued by external CA"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml114(para)
+msgid ""
+"You can use a signing certificate issued by an external CA instead of "
+"generated by <placeholder-1/>. However, a certificate issued by an external "
+"CA must satisfy the following conditions:"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml121(para)
+msgid ""
+"all certificate and key files must be in Privacy Enhanced Mail (PEM) format"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml125(para)
+msgid "private key files must not be protected by a password"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml129(para)
+msgid ""
+"When using signing certificate issued by an external CA, you do not need to "
+"specify <literal>key_size</literal>, <literal>valid_days</literal>, and "
+"<literal>ca_password</literal> as they will be ignored."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml134(para)
+msgid ""
+"The basic workflow for using a signing certificate issued by an external CA "
+"involves:"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml138(para)
+msgid "Request Signing Certificate from External CA"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml142(para)
+msgid "Convert certificate and private key to PEM if needed"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml146(para)
+msgid "Install External Signing Certificate"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml151(title)
+msgid "Request a signing certificate from an external CA"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml153(para)
+msgid ""
+"One way to request a signing certificate from an external CA is to first "
+"generate a PKCS #10 Certificate Request Syntax (CRS) using OpenSSL CLI."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml156(para)
+msgid ""
+"Create a certificate request configuration file. For example, create the "
+"<filename>cert_req.conf</filename> file, as follows:"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml176(para)
+msgid ""
+"Then generate a CRS with OpenSSL CLI. <emphasis role=\"strong\">Do not "
+"encrypt the generated private key. Must use the -nodes option.</emphasis>"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml183(para)
+msgid ""
+"If everything is successful, you should end up with "
+"<filename>signing_cert_req.pem</filename> and "
+"<filename>signing_key.pem</filename>. Send "
+"<filename>signing_cert_req.pem</filename> to your CA to request a token "
+"signing certificate and make sure to ask the certificate to be in PEM "
+"format. Also, make sure your trusted CA certificate chain is also in PEM "
+"format."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml193(title)
+msgid "Install an external signing certificate"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml194(para)
+msgid "Assuming you have the following already:"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml197(para)
+msgid ""
+"<filename>signing_cert.pem</filename> - (Keystone token) signing certificate"
+" in PEM format"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml202(para)
+msgid ""
+"<filename>signing_key.pem</filename> - corresponding (non-encrypted) private"
+" key in PEM format"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml208(para)
+msgid ""
+"<filename>cacert.pem</filename> - trust CA certificate chain in PEM format"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml213(para)
+msgid "Copy the above to your certificate directory. For example:"
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml221(para)
+msgid "Make sure the certificate directory is only accessible by root."
+msgstr ""
+
+#: ./doc/common/section_keystone_certificates-for-pki.xml224(para)
+msgid ""
+"If your certificate directory path is different from the default "
+"<filename>/etc/keystone/ssl/certs</filename>, make sure it is reflected in "
+"the <literal>[signing]</literal> section of the configuration file."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_get_console.xml6(title)
+msgid "Access an instance through a console"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_get_console.xml7(para)
+msgid ""
+"To access an instance through a VNC console, run the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_get_console.xml9(para)
+msgid "The command returns a URL from which you can access your instance:"
+msgstr "このコマンドは、インスタンスにアクセスするための URL を返します。"
+
+#: ./doc/common/section_cli_nova_get_console.xml15(para)
+msgid ""
+"To access an instance through a non-VNC console, specify the "
+"<parameter>novnc</parameter> parameter instead of the "
+"<parameter>xvpvnc</parameter> parameter."
+msgstr ""
+
+#: ./doc/common/section_compute_config-firewalls.xml6(title)
+msgid "Compute service node firewall requirements"
+msgstr ""
+
+#: ./doc/common/section_compute_config-firewalls.xml7(para)
+msgid ""
+"Console connections for virtual machines, whether direct or through a proxy,"
+" are received on ports <literal>5900</literal> to <literal>5999</literal>. "
+"You must configure the firewall on each Compute service node to enable "
+"network traffic on these ports."
+msgstr ""
+
+#: ./doc/common/section_compute_config-firewalls.xml11(title)
+msgid "Configure the service-node firewall"
+msgstr ""
+
+#: ./doc/common/section_compute_config-firewalls.xml12(para)
+msgid ""
+"On the server that hosts the Compute service, log in as "
+"<systemitem>root</systemitem>."
+msgstr ""
+
+#: ./doc/common/section_compute_config-firewalls.xml14(para)
+msgid "Edit the <filename>/etc/sysconfig/iptables</filename> file."
+msgstr ""
+
+#: ./doc/common/section_compute_config-firewalls.xml20(para)
+msgid ""
+"Add an INPUT rule that allows TCP traffic on ports that range from "
+"<literal>5900</literal> to <literal>5999</literal>:"
+msgstr ""
+
+#: ./doc/common/section_compute_config-firewalls.xml26(para)
+msgid "The new rule must appear before any INPUT rules that REJECT traffic."
+msgstr ""
+
+#: ./doc/common/section_compute_config-firewalls.xml32(para)
+msgid ""
+"Save the changes to the <filename>/etc/sysconfig/iptables</filename> file."
+msgstr ""
+
+#: ./doc/common/section_compute_config-firewalls.xml38(para)
+msgid ""
+"Restart the <systemitem>iptables</systemitem> service to ensure that the "
+"change takes effect."
+msgstr ""
+
+#: ./doc/common/section_compute_config-firewalls.xml45(para)
+msgid ""
+"The <systemitem>iptables</systemitem> firewall now enables incoming "
+"connections to the Compute services. Repeat this process for each Compute "
+"service node."
+msgstr ""
+
+#: ./doc/common/section_about-object-storage.xml7(title)
+#: ./doc/common/section_objectstorage-intro.xml7(title)
+msgid "Introduction to Object Storage"
+msgstr ""
+
+#: ./doc/common/section_about-object-storage.xml8(para)
+msgid ""
+"Object Storage is a robust, highly scalable and fault tolerant storage "
+"platform for unstructured data such as objects. Objects are stored bits, "
+"accessed through a RESTful, HTTP-based interface. You cannot access data at "
+"the block or file level. Object Storage is commonly used to archive and back"
+" up data, with use cases in virtual machine image, photo, video and music "
+"storage."
+msgstr ""
+
+#: ./doc/common/section_about-object-storage.xml15(para)
+msgid ""
+"Object Storage provides a high degree of availability, throughput, and "
+"performance with its scale out architecture. Each object is replicated "
+"across multiple servers, residing within the same data center or across data"
+" centers, which mitigates the risk of network and hardware failure. In the "
+"event of hardware failure, Object Storage will automatically copy objects to"
+" a new location to ensure that there are always three copies available. "
+"Object Storage is an eventually consistent distributed storage platform; it "
+"sacrifices consistency for maximum availability and partition tolerance. "
+"Object Storage enables you to create a reliable platform by using commodity "
+"hardware and inexpensive storage."
+msgstr ""
+
+#: ./doc/common/section_about-object-storage.xml27(para)
+msgid ""
+"For more information, review the key concepts in the developer documentation"
+" at <link "
+"href=\"http://docs.openstack.org/developer/swift/\">docs.openstack.org/developer/swift/</link>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml10(title)
+msgid "Launch an instance from a volume"
+msgstr "ボリュームからのインスタンスの起動"
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml11(para)
+msgid "You can boot instances from a volume instead of an image."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml12(para)
+msgid ""
+"To complete these tasks, use these parameters on the nova <placeholder-1/> "
+"command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml20(th)
+msgid "Task"
+msgstr "タスク"
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml21(th)
+msgid "nova boot parameter"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml22(th)
+msgid "See"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml27(td)
+msgid "Boot an instance from an image and attach a non-bootable volume."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml29(parameter)
+#: ./doc/common/section_cli_nova_boot_from_volume.xml35(parameter)
+#: ./doc/common/section_cli_nova_boot_from_volume.xml41(parameter)
+msgid "--block-device"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml33(td)
+msgid "Create a volume from an image and boot an instance from that volume."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml39(td)
+msgid "Boot from an existing source image, volume, or snapshot."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml45(td)
+msgid "Attach a swap disk to an instance."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml47(parameter)
+msgid "--swap"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml51(td)
+msgid "Attach an ephemeral disk to an instance."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml52(parameter)
+msgid "--ephemeral"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml58(para)
+msgid ""
+"To attach a volume to a running instance, see <xref "
+"linkend=\"cli_attach_volume\"/>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml62(title)
+msgid "Boot instance from image and attach non-bootable volume"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml64(para)
+msgid ""
+"Create a non-bootable volume and attach that volume to an instance that you "
+"boot from an image."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml66(para)
+msgid ""
+"To create a non-bootable volume, do not create it from an image. The volume "
+"must be entirely empty with no partition table and no file system."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml71(para)
+msgid "Create a non-bootable volume:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml98(para)
+#: ./doc/common/section_cli_cinder_manage_volumes.xml176(para)
+msgid "List volumes:"
+msgstr "ボリュームを一覧表示します。"
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml107(para)
+msgid ""
+"Boot an instance from an image and attach the empty volume to the instance:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml149(title)
+msgid "Create volume from image and boot instance"
+msgstr "イメージからのボリュームの作成とインスタンスの起動"
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml150(para)
+msgid ""
+"You can create a volume from an existing image, volume, or snapshot. This "
+"procedure shows you how to create a volume from an image, and use the volume"
+" to boot an instance."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml165(para)
+msgid "Note the ID of the image that you want to use to create a volume."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml183(para)
+msgid "Note the ID of the flavor that you want to use to create a volume."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml187(para)
+msgid ""
+"To create a bootable volume from an image and launch an instance from this "
+"volume, use the <parameter>--block-device</parameter> parameter."
+msgstr "イメージから起動可能なボリュームを作成し、このボリュームからインスタンスを起動するために、<parameter>--block-device</parameter> パラメーターを使用します。"
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
+#: ./doc/common/section_cli_nova_boot_from_volume.xml329(replaceable)
+msgid "FLAVOR"
+msgstr "FLAVOR"
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
+#: ./doc/common/section_cli_nova_boot_from_volume.xml205(replaceable)
+msgid "SOURCE"
+msgstr "SOURCE"
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
+#: ./doc/common/section_cli_nova_boot_from_volume.xml217(replaceable)
+msgid "ID"
+msgstr "ID"
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
+#: ./doc/common/section_cli_nova_boot_from_volume.xml224(replaceable)
+msgid "DEST"
+msgstr "DEST"
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
+#: ./doc/common/section_cli_nova_boot_from_volume.xml233(replaceable)
+msgid "SIZE"
+msgstr "SIZE"
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
+msgid "PRESERVE"
+msgstr "PRESERVE"
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
+#: ./doc/common/section_cli_nova_boot_from_volume.xml250(replaceable)
+msgid "INDEX"
+msgstr "INDEX"
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml191(replaceable)
+#: ./doc/common/section_cli_nova_boot_from_volume.xml329(replaceable)
+msgid "NAME"
+msgstr "NAME"
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml192(para)
+msgid "The parameters are:"
+msgstr "パラメーターは以下のとおりです。"
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml195(para)
+msgid ""
+"<parameter>--flavor</parameter><replaceable>FLAVOR</replaceable>. The flavor"
+" ID or name."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml200(para)
+msgid ""
+"<parameter>--block-device</parameter> "
+"source=<replaceable>SOURCE</replaceable>,id=<replaceable>ID</replaceable>,dest=<replaceable>DEST</replaceable>,size=<replaceable>SIZE</replaceable>,shutdown=<replaceable>PRESERVE</replaceable>,bootindex=<replaceable>INDEX</replaceable>"
+msgstr "<parameter>--block-device</parameter> source=<replaceable>SOURCE</replaceable>,id=<replaceable>ID</replaceable>,dest=<replaceable>DEST</replaceable>,size=<replaceable>SIZE</replaceable>,shutdown=<replaceable>PRESERVE</replaceable>,bootindex=<replaceable>INDEX</replaceable>"
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml205(emphasis)
+msgid "source=<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml207(para)
+msgid ""
+"The type of object used to create the block device. Valid values are "
+"<literal>volume</literal>, <literal>snapshot</literal>, "
+"<literal>image</literal>, and <literal>blank</literal>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml217(emphasis)
+msgid "id=<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml219(para)
+msgid "The ID of the source object."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml224(emphasis)
+msgid "dest=<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml226(para)
+msgid ""
+"The type of the target virtual device. Valid values are "
+"<literal>volume</literal> and <literal>local</literal>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml233(emphasis)
+msgid "size=<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml235(para)
+msgid "The size of the volume that is created."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml240(emphasis)
+msgid "shutdown={preserve|remove}"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml242(para)
+msgid ""
+"What to do with the volume when the instance is deleted. "
+"<literal>preserve</literal> does not delete the volume. "
+"<literal>remove</literal> deletes the volume."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml250(emphasis)
+msgid "bootindex=<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml252(para)
+msgid ""
+"Orders the boot disks. Use <literal>0</literal> to boot from this volume."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml260(para)
+msgid "<replaceable>NAME</replaceable>. The name for the server."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml266(para)
+msgid ""
+"Create a bootable volume from an image, before the instance boots. The "
+"volume is not deleted when the instance is terminated:"
+msgstr "インスタンスの起動前に、起動可能なボリュームをイメージから作成します。このボリュームはインスタンスの終了時に削除されません。"
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml307(para)
+msgid ""
+"List volumes to see the bootable volume and its attached "
+"<literal>myInstanceFromVolume</literal> instance:"
+msgstr "起動可能なボリュームと接続された <literal>myInstanceFromVolume</literal> インスタンスを参照するためにボリュームを一覧表示します。"
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml320(title)
+msgid "Attach swap or ephemeral disk to an instance"
+msgstr "インスタンスへのスワップや一時ディスクの接続"
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml321(para)
+msgid ""
+"Use the nova <placeholder-1/><parameter>--swap</parameter> parameter to "
+"attach a swap disk on boot or the nova "
+"<placeholder-2/><parameter>--ephemeral</parameter> parameter to attach an "
+"ephemeral disk on boot. When you terminate the instance, both disks are "
+"deleted."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml327(para)
+msgid "Boot an instance with a 512MB swap disk and 2GB ephemeral disk:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_boot_from_volume.xml331(para)
+msgid ""
+"The flavor defines the maximum swap and ephemeral disk size. You cannot "
+"exceed these maximum values."
+msgstr "フレーバーが最大スワップと一時ディスクの容量を定義します。これらの最大値を超過できません。"
+
+#: ./doc/common/section_xapi-resize-setup.xml7(title)
+msgid "Modify Dom0 for resize/migration support"
+msgstr ""
+
+#: ./doc/common/section_xapi-resize-setup.xml8(para)
+msgid "To resize servers with XenServer and XCP, you must:"
+msgstr ""
+
+#: ./doc/common/section_xapi-resize-setup.xml11(para)
+msgid ""
+"Establish a root trust between all hypervisor nodes of your deployment:"
+msgstr ""
+
+#: ./doc/common/section_xapi-resize-setup.xml13(para)
+msgid ""
+"To do so, generate an ssh key-pair with the <placeholder-1/> command. Ensure"
+" that each of your dom0's <filename>authorized_keys</filename> file (located"
+" in <filename>/root/.ssh/authorized_keys</filename>) contains the public key"
+" fingerprint (located in <filename>/root/.ssh/id_rsa.pub</filename>)."
+msgstr ""
+
+#: ./doc/common/section_xapi-resize-setup.xml22(para)
+msgid ""
+"Provide an <filename>/images</filename> mount point to the dom0 for your "
+"hypervisor:"
+msgstr ""
+
+#: ./doc/common/section_xapi-resize-setup.xml24(para)
+msgid ""
+"Dom0 space is at a premium so creating a directory in dom0 is potentially "
+"dangerous and likely to fail especially when you resize large servers. The "
+"least you can do is to symlink <filename>/images</filename> to your local "
+"storage SR. The following instructions work for an English-based "
+"installation of XenServer (and XCP) and in the case of ext3-based SR (with "
+"which the resize functionality is known to work correctly)."
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_dashboard_access.xml89(None)
+msgid ""
+"@@image: 'figures/dashboard-project-tab.png'; "
+"md5=5b192a3d34c9285dbacd875395b8e4cc"
+msgstr "@@image: 'figures/dashboard-project-tab.png'; md5=5b192a3d34c9285dbacd875395b8e4cc"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_dashboard_access.xml214(None)
+msgid ""
+"@@image: 'figures/dashboard-admin-tab.png'; "
+"md5=039358c76c549d7d423da5b8aa826435"
+msgstr "@@image: 'figures/dashboard-admin-tab.png'; md5=039358c76c549d7d423da5b8aa826435"
+
+#: ./doc/common/section_dashboard_access.xml12(title)
+msgid "Log in to the dashboard"
+msgstr "ダッシュボードへのログイン"
+
+#: ./doc/common/section_dashboard_access.xml13(para)
+msgid ""
+"The dashboard is available on the node with the <literal>nova-"
+"dashboard</literal> server role."
+msgstr "ダッシュボードは <literal>nova-dashboard</literal> サーバーロールを持つノードで利用できます。"
+
+#: ./doc/common/section_dashboard_access.xml17(para)
+msgid ""
+"Ask the cloud operator for the host name or public IP address from which you"
+" can access the dashboard, and for your user name and password."
+msgstr "ダッシュボードにアクセスできるホスト名またはパブリック IP アドレス、およびあなたのユーザー名とパスワードをクラウド運用者に問い合わせます。"
+
+#: ./doc/common/section_dashboard_access.xml22(para)
+msgid "Open a web browser that has JavaScript and cookies enabled."
+msgstr "JavaScript とクッキーが有効化された、ウェブブラウザーを開きます。"
+
+#: ./doc/common/section_dashboard_access.xml25(para)
+msgid ""
+"To use the Virtual Network Computing (VNC) client for the dashboard, your "
+"browser must support HTML5 Canvas and HTML5 WebSockets. The VNC client is "
+"based on noVNC. For details, see <link "
+"href=\"https://github.com/kanaka/noVNC/blob/master/README.md\">noVNC: HTML5 "
+"VNC Client</link>. For a list of supported browsers, see <link "
+"href=\"https://github.com/kanaka/noVNC/wiki/Browser-support\">Browser "
+"support</link>."
+msgstr "ダッシュボード用の Virtual Network Computing (VNC) クライアントを使用する場合、お使いのブラウザーが HTML5 Canvas と HTML5 WebSockets をサポートする必要があります。この VNC クライアントは noVNC に基づいています。詳細は <link href=\"https://github.com/kanaka/noVNC/blob/master/README.md\">noVNC: HTML5 VNC Client</link> を参照してください。サポートされるブラウザーの一覧は <link href=\"https://github.com/kanaka/noVNC/wiki/Browser-support\">Browser support</link> を参照してください。"
+
+#: ./doc/common/section_dashboard_access.xml38(para)
+msgid ""
+"In the address bar, enter the host name or IP address for the dashboard."
+msgstr "アドレスバーにダッシュボードのホスト名または IP アドレスを入力します。"
+
+#: ./doc/common/section_dashboard_access.xml40(replaceable)
+msgid "ipAddressOrHostName"
+msgstr "ipAddressOrHostName"
+
+#: ./doc/common/section_dashboard_access.xml42(para)
+msgid ""
+"If a certificate warning appears when you try to access the URL for the "
+"first time, a self-signed certificate is in use, which is not considered "
+"trustworthy by default. Verify the certificate or add an exception in the "
+"browser to bypass the warning."
+msgstr "URL に初めてアクセスしようとしたときに、証明書の警告が表示された場合、自己署名証明書が使用されています。これは標準で信頼性が考慮されていません。警告を回避するために、証明書を検証するか、ブラウザーに例外を追加してください。"
+
+#: ./doc/common/section_dashboard_access.xml51(para)
+msgid ""
+"On the <guilabel>Log In</guilabel> page, enter your user name and password, "
+"and click <guibutton>Sign In</guibutton>."
+msgstr "<guilabel>ログイン</guilabel>ページで、ユーザー名とパスワードを入力し、<guibutton>ログイン</guibutton>をクリックします。"
+
+#: ./doc/common/section_dashboard_access.xml54(para)
+msgid ""
+"The top of the window displays your user name. You can also access "
+"<guilabel>Settings</guilabel> or sign out of the dashboard."
+msgstr "ウィンドウの最上部にユーザー名が表示されます。また、<guilabel>設定</guilabel>ページにアクセスしたり、ダッシュボードをログアウトしたりできます。"
+
+#: ./doc/common/section_dashboard_access.xml61(para)
+msgid ""
+"If you are logged in as an end user, the <link "
+"linkend=\"dashboard_project_tab\">Project</link> tab is displayed."
+msgstr "エンドユーザーとしてログインすると、<link linkend=\"dashboard_project_tab\">プロジェクト</link>タブが表示されます。"
+
+#: ./doc/common/section_dashboard_access.xml65(para)
+msgid ""
+"If you are logged in as an administrator, the <link "
+"linkend=\"dashboard_project_tab\">Project</link> tab and <link "
+"linkend=\"dashboard_admin_tab\">Admin</link> tab are displayed."
+msgstr "管理者としてログインすると、<link linkend=\"dashboard_project_tab\">プロジェクト</link>タブと<link linkend=\"dashboard_admin_tab\">管理</link>タブが表示されます。"
+
+#: ./doc/common/section_dashboard_access.xml57(para)
+msgid ""
+"The visible tabs and functions in the dashboard depend on the access "
+"permissions, or <emphasis role=\"italic\">roles</emphasis>, of the user you "
+"are logged in as.<placeholder-1/>"
+msgstr "ダッシュボードに表示されるタブや機能は、ログインしたユーザーのアクセス権限や<emphasis role=\"italic\">ロール</emphasis>に依存します。<placeholder-1/>"
+
+#: ./doc/common/section_dashboard_access.xml75(title)
+msgid "OpenStack dashboardProject tab"
+msgstr "OpenStack Dashboard プロジェクトタブ"
+
+#: ./doc/common/section_dashboard_access.xml76(para)
+msgid ""
+"Projects are organizational units in the cloud, and are also known as "
+"tenants or accounts. Each user is a member of one or more projects. Within a"
+" project, a user creates and manages instances."
+msgstr "プロジェクトは、クラウドにおける組織単位です。テナントやアカウントとしても知られています。各ユーザーは、1 つ以上のプロジェクトのメンバーです。ユーザーは、プロジェクト内でインスタンスを作成、管理します。"
+
+#: ./doc/common/section_dashboard_access.xml80(para)
+msgid ""
+"From the <guilabel>Project</guilabel> tab, you can view and manage the "
+"resources in a selected project, including instances and images. You select "
+"the project from the <guilabel>CURRENT PROJECT</guilabel> list at the top of"
+" the tab."
+msgstr "<guilabel>プロジェクト</guilabel>タブから、選択したプロジェクトにおける、インスタンスやイメージなどのリソースを表示、管理できます。タブの上部にある<guilabel>現在のプロジェクト</guilabel>リストからプロジェクトを選択します。"
+
+#: ./doc/common/section_dashboard_access.xml85(title)
+msgid "Project tab"
+msgstr "プロジェクトタブ"
+
+#: ./doc/common/section_dashboard_access.xml93(para)
+msgid ""
+"From the <guilabel>Project</guilabel> tab, you can access the following "
+"tabs:"
+msgstr "<guilabel>プロジェクト</guilabel>タブから、以下のタブにアクセスできます。"
+
+#: ./doc/common/section_dashboard_access.xml100(th)
+#: ./doc/common/section_dashboard_access.xml170(th)
+#: ./doc/common/section_dashboard_access.xml185(th)
+#: ./doc/common/section_dashboard_access.xml192(th)
+#: ./doc/common/section_dashboard_access.xml224(th)
+#: ./doc/common/section_dashboard_access.xml350(th)
+msgid "<placeholder-1/> tab"
+msgstr "<placeholder-1/> タブ"
+
+#: ./doc/common/section_dashboard_access.xml106(para)
+msgid "View reports for the project."
+msgstr "プロジェクトのレポートを表示します。"
+
+#: ./doc/common/section_dashboard_access.xml109(guilabel)
+#: ./doc/common/section_dashboard_access.xml292(guilabel)
+msgid "Instances"
+msgstr "インスタンス"
+
+#: ./doc/common/section_dashboard_access.xml110(para)
+msgid ""
+"View, launch, create a snapshot from, stop, pause, or reboot instances, or "
+"connect to them through VNC."
+msgstr "インスタンスの表示、起動、スナップショットの作成をします。インスタンスの停止、一時停止、シャットダウンをします。または、インスタンスに VNC 経由で接続します。"
+
+#: ./doc/common/section_dashboard_access.xml114(guilabel)
+#: ./doc/common/section_dashboard_access.xml119(guilabel)
+#: ./doc/common/section_dashboard_access.xml299(guilabel)
+msgid "Volumes"
+msgstr "ボリューム"
+
+#: ./doc/common/section_dashboard_access.xml115(para)
+#: ./doc/common/section_dashboard_access.xml141(para)
+msgid "Use the following tabs to complete these tasks:"
+msgstr "これらの作業を実行するために、以下のタブを使用します。"
+
+#: ./doc/common/section_dashboard_access.xml121(para)
+msgid "View, create, edit, and delete volumes."
+msgstr "ボリュームを表示、作成、編集、削除します。"
+
+#: ./doc/common/section_dashboard_access.xml125(guilabel)
+msgid "Volume Snapshots"
+msgstr "ボリュームのスナップショット"
+
+#: ./doc/common/section_dashboard_access.xml127(para)
+msgid "View, create, edit, and delete volume snapshots."
+msgstr "ボリュームのスナップショットを表示、作成、編集、削除します。"
+
+#: ./doc/common/section_dashboard_access.xml133(guilabel)
+#: ./doc/common/section_dashboard_access.xml309(guilabel)
+msgid "Images"
+msgstr "イメージ"
+
+#: ./doc/common/section_dashboard_access.xml134(para)
+msgid ""
+"View images and instance snapshots created by project users, plus any images"
+" that are publicly available. Create, edit, and delete images, and launch "
+"instances from images and snapshots."
+msgstr "プロジェクトのユーザーにより作成された、イメージおよびインスタンスのスナップショットを表示します。加えて、すべてのパブリックなイメージを表示します。イメージを作成、編集、削除します。また、イメージやスナップショットからインスタンスを起動します。"
+
+#: ./doc/common/section_dashboard_access.xml140(guilabel)
+msgid "Access &amp; Security"
+msgstr "アクセスとセキュリティ"
+
+#: ./doc/common/section_dashboard_access.xml144(guilabel)
+msgid "Security Groups"
+msgstr "セキュリティグループ"
+
+#: ./doc/common/section_dashboard_access.xml145(para)
+msgid ""
+"View, create, edit, and delete security groups and security group rules."
+msgstr "セキュリティグループおよびセキュリティグループのルールを表示、作成、編集、削除します。"
+
+#: ./doc/common/section_dashboard_access.xml150(guilabel)
+msgid "Key Pairs"
+msgstr "キーペア"
+
+#: ./doc/common/section_dashboard_access.xml151(para)
+msgid "View, create, edit, import, and delete key pairs."
+msgstr "キーペアを表示、作成、編集、インポート、削除します。"
+
+#: ./doc/common/section_dashboard_access.xml156(guilabel)
+msgid "Floating IPs"
+msgstr "Floating IP"
+
+#: ./doc/common/section_dashboard_access.xml158(para)
+msgid "Allocate an IP address to or release it from a project."
+msgstr "プロジェクトに IP アドレスを確保します。または、解放します。"
+
+#: ./doc/common/section_dashboard_access.xml163(guilabel)
+msgid "API Access"
+msgstr "API アクセス"
+
+#: ./doc/common/section_dashboard_access.xml164(para)
+msgid "View API endpoints."
+msgstr "API エンドポイントを表示します。"
+
+#: ./doc/common/section_dashboard_access.xml170(guilabel)
+msgid "Network"
+msgstr "ネットワーク"
+
+#: ./doc/common/section_dashboard_access.xml173(guilabel)
+msgid "Network Topology"
+msgstr "ネットワークトポロジー"
+
+#: ./doc/common/section_dashboard_access.xml174(para)
+msgid "View the network topology."
+msgstr "ネットワークトポロジーを表示します。"
+
+#: ./doc/common/section_dashboard_access.xml177(guilabel)
+#: ./doc/common/section_dashboard_access.xml314(guilabel)
+msgid "Networks"
+msgstr "ネットワーク"
+
+#: ./doc/common/section_dashboard_access.xml178(para)
+msgid "Create and manage public and private networks."
+msgstr "パブリックネットワークおよびプライベートネットワークを作成、管理します。"
+
+#: ./doc/common/section_dashboard_access.xml181(guilabel)
+#: ./doc/common/section_dashboard_access.xml318(guilabel)
+msgid "Routers"
+msgstr "ルーター"
+
+#: ./doc/common/section_dashboard_access.xml182(para)
+msgid "Create and manage subnets."
+msgstr "サブネットを作成、管理します。"
+
+#: ./doc/common/section_dashboard_access.xml185(guilabel)
+msgid "Object Store"
+msgstr "オブジェクトストア"
+
+#: ./doc/common/section_dashboard_access.xml188(guilabel)
+#: ./doc/common/section_dashboard_access.xml195(guilabel)
+msgid "Containers"
+msgstr "コンテナー"
+
+#: ./doc/common/section_dashboard_access.xml189(para)
+msgid "Create and manage containers and objects."
+msgstr "コンテナーとオブジェクトを作成、管理します。"
+
+#: ./doc/common/section_dashboard_access.xml196(para)
+msgid "Use the REST API to orchestrate multiple composite cloud applications."
+msgstr "複数のコンポジットクラウドアプリケーションをオーケストレーションするために REST API を使用します。"
+
+#: ./doc/common/section_dashboard_access.xml203(title)
+msgid "OpenStack dashboardAdmin tab"
+msgstr "OpenStack Dashboard 管理タブ"
+
+#: ./doc/common/section_dashboard_access.xml204(para)
+msgid ""
+"Administrative users can use the <guilabel>Admin</guilabel> tab to view "
+"usage and to manage instances, volumes, flavors, images, projects, users, "
+"services, and quotas."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml209(title)
+msgid "Admin tab"
+msgstr "管理タブ"
+
+#: ./doc/common/section_dashboard_access.xml218(para)
+msgid "Access the following categories to complete these tasks:"
+msgstr "これらの作業を実行するために、以下のカテゴリにアクセスします。"
+
+#: ./doc/common/section_dashboard_access.xml224(guilabel)
+msgid "System Panel"
+msgstr "システムパネル"
+
+#: ./doc/common/section_dashboard_access.xml230(para)
+msgid "View basic reports."
+msgstr "基本的なレポートを表示します。"
+
+#: ./doc/common/section_dashboard_access.xml233(guilabel)
+msgid "Resource Usage"
+msgstr "リソース使用量"
+
+#: ./doc/common/section_dashboard_access.xml234(para)
+msgid "Use the following tabs to view the following usages:"
+msgstr "以下の使用量を表示するために、以下のタブを使用します。"
+
+#: ./doc/common/section_dashboard_access.xml269(guilabel)
+msgid "Daily Report"
+msgstr "日次レポート"
+
+#: ./doc/common/section_dashboard_access.xml271(para)
+msgid "View the daily report."
+msgstr ""
+
+#: ./doc/common/section_dashboard_access.xml275(guilabel)
+msgid "Stats"
+msgstr "統計情報"
+
+#: ./doc/common/section_dashboard_access.xml277(para)
+msgid "View the statistics of all resources."
+msgstr "すべてのリソースの統計情報を表示します。"
+
+#: ./doc/common/section_dashboard_access.xml283(guilabel)
+msgid "Hypervisors"
+msgstr "ハイパーバイザー"
+
+#: ./doc/common/section_dashboard_access.xml284(para)
+msgid "View the hypervisor summary."
+msgstr "ハイパーバイザーの概要を表示します。"
+
+#: ./doc/common/section_dashboard_access.xml287(guilabel)
+msgid "Host Aggregates"
+msgstr "ホストアグリゲート"
+
+#: ./doc/common/section_dashboard_access.xml288(para)
+msgid ""
+"View, create, and edit host aggregates. View the list of availability zones."
+msgstr "ホストアグリゲートを表示、作成、編集します。アベイラビリティゾーンの一覧を表示します。"
+
+#: ./doc/common/section_dashboard_access.xml293(para)
+msgid ""
+"View, pause, resume, suspend, migrate, soft or hard reboot, and delete "
+"running instances that belong to users of some, but not all, projects. Also,"
+" view the log for an instance or access an instance through VNC."
+msgstr "いくつかだが、すべてではないプロジェクトのユーザーが所属する実行中のインスタンスを表示、一時停止、再開、サスペンド、マイグレーション、ソフトリブート、ハードリブート、削除します。また、インスタンスのログを表示します。VNC 経由でインスタンスにアクセスします。"
+
+#: ./doc/common/section_dashboard_access.xml300(para)
+msgid "View, create, edit, and delete volumes and volume types."
+msgstr "ボリュームおよびボリューム形式を表示、作成、編集、削除します。"
+
+#: ./doc/common/section_dashboard_access.xml305(para)
+msgid ""
+"View, create, edit, view extra specifications for, and delete flavors. A "
+"flavor is size of an instance."
+msgstr "フレーバーの追加スペックを表示、作成、編集します。また、フレーバーを削除します。フレーバーはインスタンスの大きさです。"
+
+#: ./doc/common/section_dashboard_access.xml310(para)
+msgid "View, create, edit properties for, and delete custom images."
+msgstr "カスタムイメージのプロパティを表示、作成、編集します。また、カスタムイメージを削除します。"
+
+#: ./doc/common/section_dashboard_access.xml315(para)
+msgid "View, create, edit properties for, and delete networks."
+msgstr "ネットワークのプロパティを表示、作成、編集します。また、ネットワークを削除します。"
+
+#: ./doc/common/section_dashboard_access.xml319(para)
+msgid "View, create, edit properties for, and delete routers."
+msgstr "ルーターのプロパティを表示、作成、編集します。また、ルーターを削除します。"
+
+#: ./doc/common/section_dashboard_access.xml322(guilabel)
+msgid "System Info"
+msgstr "システム情報"
+
+#: ./doc/common/section_dashboard_access.xml323(para)
+msgid "Use the following tabs to view the service information:"
+msgstr "サービスの情報を表示するために以下のタブを使用します。"
+
+#: ./doc/common/section_dashboard_access.xml326(guilabel)
+msgid "Services"
+msgstr "サービス"
+
+#: ./doc/common/section_dashboard_access.xml327(para)
+msgid "View a list of the services."
+msgstr "サービスの一覧を表示します。"
+
+#: ./doc/common/section_dashboard_access.xml331(guilabel)
+msgid "Compute Services"
+msgstr "コンピュートサービス"
+
+#: ./doc/common/section_dashboard_access.xml332(para)
+msgid "View a list of all Compute services."
+msgstr "すべてのコンピュートサービスの一覧を表示します。"
+
+#: ./doc/common/section_dashboard_access.xml336(guilabel)
+msgid "Network Agents"
+msgstr "ネットワークエージェント"
+
+#: ./doc/common/section_dashboard_access.xml337(para)
+msgid "View the network agents."
+msgstr "ネットワークエージェントを表示します。"
+
+#: ./doc/common/section_dashboard_access.xml341(guilabel)
+msgid "Default Quotas"
+msgstr "標準のクォータ"
+
+#: ./doc/common/section_dashboard_access.xml342(para)
+msgid ""
+"View default quota values. Quotas are hard-coded in OpenStack Compute and "
+"define the maximum allowable size and number of resources."
+msgstr "規定のクォータ値を表示します。クォータは OpenStack Compute にハードコードされています。利用可能な最大値と最大リソース数を定義します。"
+
+#: ./doc/common/section_dashboard_access.xml350(guilabel)
+msgid "Identity Panel"
+msgstr "認証パネル"
+
+#: ./doc/common/section_dashboard_access.xml358(guilabel)
+msgid "Projects"
+msgstr "プロジェクト"
+
+#: ./doc/common/section_dashboard_access.xml359(para)
+msgid "View, create, assign users to, remove users from, and delete projects."
+msgstr "プロジェクトを表示、作成、削除します。またはプロジェクトのユーザーを追加、削除します。"
+
+#: ./doc/common/section_dashboard_access.xml363(guilabel)
+msgid "Users"
+msgstr "ユーザー"
+
+#: ./doc/common/section_dashboard_access.xml364(para)
+msgid "View, create, enable, disable, and delete users."
+msgstr "ユーザーを表示、作成、有効化、無効化、削除します。"
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml6(title)
+msgid "Show usage statistics for hosts and instances"
+msgstr "ホストおよびインスタンスの使用統計の表示"
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml7(para)
+msgid ""
+"You can show basic statistics on resource usage for hosts and instances."
+msgstr "ホストやインスタンスのリソース使用状況に関する基本的な統計を表示できます。"
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml10(para)
+msgid ""
+"For more sophisticated monitoring, see the <link "
+"href=\"https://launchpad.net/ceilometer\">ceilometer</link> project. You can"
+" also use tools, such as <link href=\"http://ganglia.info/\">Ganglia</link> "
+"or <link href=\"http://graphite.wikidot.com/\">Graphite</link>, to gather "
+"more detailed data."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml20(title)
+msgid "Show host usage statistics"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml21(para)
+msgid ""
+"The following examples show the host usage statistics for a host called "
+"<filename>devstack</filename>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml25(para)
+msgid "List the hosts and the nova-related services that run on them:"
+msgstr "ホストおよびそのホストで実行されている nova 関連のサービスを一覧表示します。"
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml37(para)
+msgid ""
+"Get a summary of resource usage of all of the instances running on the host:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml49(para)
+msgid ""
+"The <literal>cpu</literal> column shows the sum of the virtual CPUs for "
+"instances running on the host."
+msgstr "<literal>cpu</literal> の欄は、ホストで実行中のインスタンスの仮想 CPU 総数を表示します。"
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml51(para)
+msgid ""
+"The <literal>memory_mb</literal> column shows the sum of the memory (in MB) "
+"allocated to the instances that run on the host."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml54(para)
+msgid ""
+"The <literal>disk_gb</literal> column shows the sum of the root and "
+"ephemeral disk sizes (in GB) of the instances that run on the host."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml57(para)
+msgid ""
+"The row that has the value <literal>used_now</literal> in the "
+"<literal>PROJECT</literal> column shows the sum of the resources allocated "
+"to the instances that run on the host, plus the resources allocated to the "
+"virtual machine of the host itself."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml62(para)
+msgid ""
+"The row that has the value <literal>used_max</literal> row in the "
+"<literal>PROJECT</literal> column shows the sum of the resources allocated "
+"to the instances that run on the host."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml68(para)
+msgid ""
+"These values are computed by using information about the flavors of the "
+"instances that run on the hosts. This command does not query the CPU usage, "
+"memory usage, or hard disk usage of the physical host."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml75(title)
+msgid "Show instance usage statistics"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml77(para)
+msgid "Get CPU, memory, I/O, and network statistics for an instance."
+msgstr "インスタンスの CPU、メモリー、I/O、ネットワーク統計を取得します。"
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml79(para)
+msgid "List instances:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml87(para)
+msgid "Get diagnostic statistics:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_usage_statistics.xml108(para)
+msgid "Get summary statistics for each tenant:"
+msgstr "テナント別の統計サマリーを取得します。"
+
 #: ./doc/common/section_cli_openrc.xml7(title)
 msgid "Set environment variables using the OpenStack RC file"
 msgstr "OpenStack RC ファイルを用いた環境変数の設定"
@@ -23861,157 +20364,2668 @@ msgstr "PASSWORD"
 msgid "Where <replaceable>PASSWORD</replaceable> is your password."
 msgstr "<replaceable>PASSWORD</replaceable> は、お使いのパスワードです。"
 
-#: ./doc/common/section_cli_nova_baremetal.xml5(title)
-msgid "Manage bare-metal nodes"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_baremetal.xml6(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-components.xml43(None)
 msgid ""
-"The bare-metal driver for OpenStack Compute manages provisioning of physical"
-" hardware by using common cloud APIs and tools such as Orchestration (Heat)."
-" The use case for this driver is for single tenant clouds such as a high-"
-"performance computing cluster or for deploying OpenStack itself."
-msgstr ""
+"@@image: '../common/figures/objectstorage-buildingblocks.png'; "
+"md5=ed79466c8464513dbeaf1e0954280e5e"
+msgstr "@@image: '../common/figures/objectstorage-buildingblocks.png'; md5=ed79466c8464513dbeaf1e0954280e5e"
 
-#: ./doc/common/section_cli_nova_baremetal.xml10(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-components.xml86(None)
 msgid ""
-"If you use the bare-metal driver, you must create a network interface and "
-"add it to a bare-metal node. Then, you can launch an instance from a bare-"
-"metal image."
-msgstr ""
+"@@image: '../common/figures/objectstorage-ring.png'; "
+"md5=a94e26734cec6980c3684d9e824eac2d"
+msgstr "@@image: '../common/figures/objectstorage-ring.png'; md5=a94e26734cec6980c3684d9e824eac2d"
 
-#: ./doc/common/section_cli_nova_baremetal.xml13(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-components.xml126(None)
 msgid ""
-"Development efforts are focused on moving the driver out of the Compute code"
-" base in the Icehouse release."
-msgstr ""
+"@@image: '../common/figures/objectstorage-zones.png'; "
+"md5=1b1dc0abe6ea0c516f22ce399deb75ed"
+msgstr "@@image: '../common/figures/objectstorage-zones.png'; md5=1b1dc0abe6ea0c516f22ce399deb75ed"
 
-#: ./doc/common/section_cli_nova_baremetal.xml15(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-components.xml144(None)
 msgid ""
-"You can list and delete bare-metal nodes. When you delete a node, any "
-"associated network interfaces are removed. You can list and remove network "
-"interfaces that are associated with a bare-metal node."
-msgstr ""
+"@@image: '../common/figures/objectstorage-accountscontainers.png'; "
+"md5=4b15e5a202db5bde53c9b369058aeab8"
+msgstr "@@image: '../common/figures/objectstorage-accountscontainers.png'; md5=4b15e5a202db5bde53c9b369058aeab8"
 
-#: ./doc/common/section_cli_nova_baremetal.xml19(title)
-msgid "Commands"
-msgstr "コマンド"
-
-#: ./doc/common/section_cli_nova_baremetal.xml20(para)
-msgid "The following commands can be used to manage bare-metal nodes."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_baremetal.xml22(para)
-msgid "<placeholder-1/>. Adds a network interface to a bare-metal node."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_baremetal.xml26(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-components.xml169(None)
 msgid ""
-"<placeholder-1/>. Lists network interfaces associated with a bare-metal "
-"node."
-msgstr ""
+"@@image: '../common/figures/objectstorage-partitions.png'; "
+"md5=2c161c2e92d6fefc8140ec86e79e9492"
+msgstr "@@image: '../common/figures/objectstorage-partitions.png'; md5=2c161c2e92d6fefc8140ec86e79e9492"
 
-#: ./doc/common/section_cli_nova_baremetal.xml30(para)
-msgid "<placeholder-1/>. Removes a network interface from a bare-metal node."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_baremetal.xml34(para)
-msgid "<placeholder-1/>. Creates a bare-metal node."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_baremetal.xml38(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-components.xml195(None)
 msgid ""
-"<placeholder-1/>. Removes a bare-metal node and any associated interfaces."
-msgstr ""
+"@@image: '../common/figures/objectstorage-replication.png'; "
+"md5=9d55594d7f445764569ab04d8d4373b2"
+msgstr "@@image: '../common/figures/objectstorage-replication.png'; md5=9d55594d7f445764569ab04d8d4373b2"
 
-#: ./doc/common/section_cli_nova_baremetal.xml42(para)
-msgid "<placeholder-1/>. Lists available bare-metal nodes."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_baremetal.xml46(para)
-msgid "<placeholder-1/>. Shows information about a bare-metal node."
-msgstr ""
-
-#: ./doc/common/section_cli_nova_baremetal.xml51(title)
-msgid "Create a bare-metal node"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_baremetal.xml52(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/common/section_objectstorage-components.xml222(None)
 msgid ""
-"When you create a bare-metal node, your PM address, username, and password "
-"should match those that are configured in your hardware's BIOS/IPMI "
-"configuration."
+"@@image: '../common/figures/objectstorage-usecase.png'; "
+"md5=07480e7175b383171173775fb96d70d7"
+msgstr "@@image: '../common/figures/objectstorage-usecase.png'; md5=07480e7175b383171173775fb96d70d7"
+
+#: ./doc/common/section_objectstorage-components.xml7(title)
+msgid "Components"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml57(para)
+#: ./doc/common/section_objectstorage-components.xml8(para)
 msgid ""
-"The following example shows the command and results from creating a node "
-"with the PM address <filename>1.2.3.4</filename>, the PM username "
-"<literal>ipmi</literal>, and password <literal>ipmi</literal>."
+"The components that enable Object Storage to deliver high availability, high"
+" durability, and high concurrency are:"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml79(title)
-msgid "Add a network interface to the node:"
-msgstr "ベアメタルノードにネットワークインターフェースを追加します。"
-
-#: ./doc/common/section_cli_nova_baremetal.xml80(para)
+#: ./doc/common/section_objectstorage-components.xml12(para)
 msgid ""
-"For each NIC on the node, you must create an interface, specifying the "
-"interface's MAC address."
+"<emphasis role=\"bold\">Proxy servers.</emphasis> Handle all of the incoming"
+" API requests."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml92(title)
-msgid "Launch an instance from a bare-metal image:"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_baremetal.xml94(para)
+#: ./doc/common/section_objectstorage-components.xml16(para)
 msgid ""
-"A bare-metal instance is an instance created directly on a physical machine "
-"without any virtualization layer running underneath it. Nova retains power "
-"control via IPMI. In some situations, Nova may retain network control via "
-"Neutron and OpenFlow."
+"<emphasis role=\"bold\">Rings.</emphasis> Map logical names of data to "
+"locations on particular disks."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml107(para)
+#: ./doc/common/section_objectstorage-components.xml20(para)
 msgid ""
-"Set the <parameter>--availability_zone</parameter> parameter to specify "
-"which zone or node to use to start the server. Separate the zone from the "
-"host name with a comma. For example:"
-msgstr "<parameter>--availability_zone</parameter> パラメーターを設定して、サーバーを起動するゾーンまたはノードを指定します。ホスト名とゾーンはコンマで区切ります。例えば以下のようになります。"
-
-#: ./doc/common/section_cli_nova_baremetal.xml110(replaceable)
-msgid "HOST"
+"<emphasis role=\"bold\">Zones.</emphasis> Isolate data from other zones. A "
+"failure in one zone doesn’t impact the rest of the cluster because data is "
+"replicated across zones."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml110(replaceable)
-msgid "NODE"
-msgstr ""
-
-#: ./doc/common/section_cli_nova_baremetal.xml111(para)
+#: ./doc/common/section_objectstorage-components.xml25(para)
 msgid ""
-"<literal>host</literal> is optional for the "
-"<literal>--availability_zone</literal> parameter. You can specify simply "
-"<literal>zone:,node</literal>. You must still use the comma."
+"<emphasis role=\"bold\">Accounts and containers.</emphasis> Each account and"
+" container are individual databases that are distributed across the cluster."
+" An account database contains the list of containers in that account. A "
+"container database contains the list of objects in that container."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml118(title)
-msgid "List bare-metal nodes and interfaces:"
+#: ./doc/common/section_objectstorage-components.xml31(para)
+msgid "<emphasis role=\"bold\">Objects.</emphasis> The data itself."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml120(para)
+#: ./doc/common/section_objectstorage-components.xml34(para)
 msgid ""
-"Use the <placeholder-1/> command to view all bare-metal nodes and "
-"interfaces. When a node is in use, its status includes the UUID of the "
-"instance that runs on it:"
+"<emphasis role=\"bold\">Partitions.</emphasis> A partition stores objects, "
+"account databases, and container databases and helps manage locations where "
+"data lives in the cluster."
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml130(title)
-msgid "Show details for a bare-metal node:"
+#: ./doc/common/section_objectstorage-components.xml40(title)
+msgid "Object Storage building blocks"
 msgstr ""
 
-#: ./doc/common/section_cli_nova_baremetal.xml131(para)
+#: ./doc/common/section_objectstorage-components.xml48(title)
+msgid "Proxy servers"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml49(para)
 msgid ""
-"Use the <placeholder-1/> command to view the details for a bare-metal node."
+"Proxy servers are the public face of Object Storage and handle all of the "
+"incoming API requests. Once a proxy server receives a request, it determines"
+" the storage node based on the object's URL, for example, "
+"https://swift.example.com/v1/account/container/object. Proxy servers also "
+"coordinate responses, handle failures, and coordinate timestamps."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml54(para)
+msgid ""
+"Proxy servers use a shared-nothing architecture and can be scaled as needed "
+"based on projected workloads. A minimum of two proxy servers should be "
+"deployed for redundancy. If one proxy server fails, the others take over."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml59(title)
+msgid "Rings"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml60(para)
+msgid ""
+"A ring represents a mapping between the names of entities stored on disk and"
+" their physical locations. There are separate rings for accounts, "
+"containers, and objects. When other components need to perform any operation"
+" on an object, container, or account, they need to interact with the "
+"appropriate ring to determine their location in the cluster."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml65(para)
+msgid ""
+"The ring maintains this mapping using zones, devices, partitions, and "
+"replicas. Each partition in the ring is replicated, by default, three times "
+"across the cluster, and partition locations are stored in the mapping "
+"maintained by the ring. The ring is also responsible for determining which "
+"devices are used for handoff in failure scenarios."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml70(para)
+msgid ""
+"Data can be isolated into zones in the ring. Each partition replica is "
+"guaranteed to reside in a different zone. A zone could represent a drive, a "
+"server, a cabinet, a switch, or even a data center."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml73(para)
+msgid ""
+"The partitions of the ring are equally divided among all of the devices in "
+"the Object Storage installation. When partitions need to be moved around "
+"(for example, if a device is added to the cluster), the ring ensures that a "
+"minimum number of partitions are moved at a time, and only one replica of a "
+"partition is moved at a time."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml77(para)
+msgid ""
+"Weights can be used to balance the distribution of partitions on drives "
+"across the cluster. This can be useful, for example, when differently sized "
+"drives are used in a cluster."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml80(para)
+msgid ""
+"The ring is used by the proxy server and several background processes (like "
+"replication)."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml83(title)
+msgid "The <emphasis role=\"bold\">ring</emphasis>"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml90(para)
+msgid ""
+"These rings are externally managed, in that the server processes themselves "
+"do not modify the rings, they are instead given new rings modified by other "
+"tools."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml92(para)
+msgid ""
+"The ring uses a configurable number of bits from a path’s MD5 hash as a "
+"partition index that designates a device. The number of bits kept from the "
+"hash is known as the partition power, and 2 to the partition power indicates"
+" the partition count. Partitioning the full MD5 hash ring allows other parts"
+" of the cluster to work in batches of items at once which ends up either "
+"more efficient or at least less complex than working with each item "
+"separately or the entire cluster all at once."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml101(para)
+msgid ""
+"Another configurable value is the replica count, which indicates how many of"
+" the partition-device assignments make up a single ring. For a given "
+"partition number, each replica’s device will not be in the same zone as any "
+"other replica's device. Zones can be used to group devices based on physical"
+" locations, power separations, network separations, or any other attribute "
+"that would improve the availability of multiple replicas at the same time."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml109(title)
+#: ./doc/common/section_objectstorage-components.xml123(title)
+msgid "Zones"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml110(para)
+msgid ""
+"Object Storage allows configuring zones in order to isolate failure "
+"boundaries. Each data replica resides in a separate zone, if possible. At "
+"the smallest level, a zone could be a single drive or a grouping of a few "
+"drives. If there were five object storage servers, then each server would "
+"represent its own zone. Larger deployments would have an entire rack (or "
+"multiple racks) of object servers, each representing a zone. The goal of "
+"zones is to allow the cluster to tolerate significant outages of storage "
+"servers without losing all replicas of the data."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml117(para)
+msgid ""
+"As mentioned earlier, everything in Object Storage is stored, by default, "
+"three times. Swift will place each replica \"as-uniquely-as-possible\" to "
+"ensure both high availability and high durability. This means that when "
+"chosing a replica location, Object Storage chooses a server in an unused "
+"zone before an unused server in a zone that already has a replica of the "
+"data."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml130(para)
+msgid ""
+"When a disk fails, replica data is automatically distributed to the other "
+"zones to ensure there are three copies of the data."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml134(title)
+#: ./doc/common/section_objectstorage-components.xml141(title)
+msgid "Accounts and containers"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml135(para)
+msgid ""
+"Each account and container is an individual SQLite database that is "
+"distributed across the cluster. An account database contains the list of "
+"containers in that account. A container database contains the list of "
+"objects in that container."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml148(para)
+msgid ""
+"To keep track of object data locations, each account in the system has a "
+"database that references all of its containers, and each container database "
+"references each object."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml153(title)
+#: ./doc/common/section_objectstorage-components.xml166(title)
+msgid "Partitions"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml154(para)
+msgid ""
+"A partition is a collection of stored data, including account databases, "
+"container databases, and objects. Partitions are core to the replication "
+"system."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml156(para)
+msgid ""
+"Think of a partition as a bin moving throughout a fulfillment center "
+"warehouse. Individual orders get thrown into the bin. The system treats that"
+" bin as a cohesive entity as it moves throughout the system. A bin is easier"
+" to deal with than many little things. It makes for fewer moving parts "
+"throughout the system."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml160(para)
+msgid ""
+"System replicators and object uploads/downloads operate on partitions. As "
+"the system scales up, its behavior continues to be predictable because the "
+"number of partitions is a fixed number."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml163(para)
+msgid ""
+"Implementing a partition is conceptually simple, a partition is just a "
+"directory sitting on a disk with a corresponding hash table of what it "
+"contains."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml175(title)
+msgid "Replicators"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml176(para)
+msgid ""
+"In order to ensure that there are three copies of the data everywhere, "
+"replicators continuously examine each partition. For each local partition, "
+"the replicator compares it against the replicated copies in the other zones "
+"to see if there are any differences."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml180(para)
+msgid ""
+"The replicator knows if replication needs to take place by examining hashes."
+" A hash file is created for each partition, which contains hashes of each "
+"directory in the partition. Each of the three hash files is compared. For a "
+"given partition, the hash files for each of the partition's copies are "
+"compared. If the hashes are different, then it is time to replicate, and the"
+" directory that needs to be replicated is copied over."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml186(para)
+msgid ""
+"This is where partitions come in handy. With fewer things in the system, "
+"larger chunks of data are transferred around (rather than lots of little TCP"
+" connections, which is inefficient) and there is a consistent number of "
+"hashes to compare."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml189(para)
+msgid ""
+"The cluster eventually has a consistent behavior where the newest data has a"
+" priority."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml199(para)
+msgid ""
+"If a zone goes down, one of the nodes containing a replica notices and "
+"proactively copies data to a handoff location."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml203(title)
+msgid "Use cases"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml204(para)
+msgid ""
+"The following sections show use cases for object uploads and downloads and "
+"introduce the components."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml206(title)
+msgid "Upload"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml207(para)
+msgid ""
+"A client uses the REST API to make a HTTP request to PUT an object into an "
+"existing container. The cluster receives the request. First, the system must"
+" figure out where the data is going to go. To do this, the account name, "
+"container name, and object name are all used to determine the partition "
+"where this object should live."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml211(para)
+msgid ""
+"Then a lookup in the ring figures out which storage nodes contain the "
+"partitions in question."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml213(para)
+msgid ""
+"The data is then sent to each storage node where it is placed in the "
+"appropriate partition. At least two of the three writes must be successful "
+"before the client is notified that the upload was successful."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml216(para)
+msgid ""
+"Next, the container database is updated asynchronously to reflect that there"
+" is a new object in it."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml219(title)
+msgid "Object Storage in use"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-components.xml228(title)
+msgid "Download"
+msgstr "ダウンロード"
+
+#: ./doc/common/section_objectstorage-components.xml229(para)
+msgid ""
+"A request comes in for an account/container/object. Using the same "
+"consistent hashing, the partition name is generated. A lookup in the ring "
+"reveals which storage nodes contain that partition. A request is made to one"
+" of the storage nodes to fetch the object and, if that fails, requests are "
+"made to the other nodes."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml11(title)
+msgid "Manage volumes"
+msgstr "ボリュームの管理"
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml12(para)
+msgid ""
+"A volume is a detachable block storage device, similar to a USB hard drive. "
+"You can attach a volume to only one instance. To create and manage volumes, "
+"you use a combination of <placeholder-1/> and <placeholder-2/> client "
+"commands."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml16(title)
+msgid "Migrate a volume"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml17(para)
+msgid ""
+"As an administrator, you can migrate a volume with its data from one "
+"location to another in a manner that is transparent to users and workloads. "
+"You can migrate only detached volumes with no snapshots."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml21(para)
+msgid "Possible use cases for data migration include:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml24(para)
+msgid ""
+"Bring down a physical storage device for maintenance without disrupting "
+"workloads."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml28(para)
+msgid "Modify the properties of a volume."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml31(para)
+msgid "Free up space in a thinly-provisioned back end."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml35(para)
+msgid ""
+"Migrate a volume with the <placeholder-1/> command, as shown in the "
+"following example:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml36(replaceable)
+#: ./doc/common/section_cli_cinder_manage_volumes.xml274(replaceable)
+msgid "volumeID"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml36(replaceable)
+msgid "destinationHost"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml36(replaceable)
+msgid "True|False"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml37(para)
+msgid ""
+"In this example, <literal>--force-host-copy=True</literal> forces the "
+"generic host-based migration mechanism and bypasses any driver "
+"optimizations."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml40(para)
+msgid ""
+"If the volume is in use or has snapshots, the specified host destination "
+"cannot accept the volume. If the user is not an administrator, the migration"
+" fails."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml45(title)
+msgid "Create a volume"
+msgstr "ボリュームの作成"
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml46(para)
+msgid "This example creates a my-new-volume volume based on an image."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml49(para)
+msgid ""
+"List images, and note the ID of the image that you want to use for your "
+"volume:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml62(para)
+msgid ""
+"List the availability zones, and note the ID of the availability zone in "
+"which you want to create your volume:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml81(para)
+msgid ""
+"Create a volume with 8GB of space, and specify the availability zone and "
+"image:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml103(para)
+msgid ""
+"To verify that your volume was created successfully, list the available "
+"volumes:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml112(para)
+msgid ""
+"If your volume was created successfully, its status is "
+"<literal>available</literal>. If its status is <literal>error</literal>, you"
+" might have exceeded your quota."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml120(title)
+msgid "Attach a volume to an instance"
+msgstr "ボリュームのインスタンスへの接続"
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml123(para)
+msgid ""
+"Attach your volume to a server, specifying the server ID and the volume ID:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml133(para)
+msgid "Note the ID of your volume."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml136(para)
+msgid "Show information for your volume:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml138(para)
+msgid ""
+"The output shows that the volume is attached to the server with ID <literal"
+">84c6e57d-a6b1-44b6-81eb-fcb36afd31b5</literal>, is in the nova availability"
+" zone, and is bootable."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml165(title)
+msgid "Resize a volume"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml168(para)
+msgid "To resize your volume, you must first detach it from the server."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml170(para)
+msgid ""
+"To detach the volume from your server, pass the server ID and volume ID to "
+"the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml172(para)
+#: ./doc/common/section_cli_cinder_manage_volumes.xml191(para)
+msgid "The <placeholder-1/> command does not return any output."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml184(para)
+msgid "Note that the volume is now available."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml187(para)
+msgid ""
+"Resize the volume by passing the volume ID and the new size (a value greater"
+" than the old one) as parameters:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml197(title)
+msgid "Delete a volume"
+msgstr "ボリュームの削除"
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml200(para)
+msgid "To delete your volume, you must first detach it from the server."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml202(para)
+msgid ""
+"To detach the volume from your server and check for the list of existing "
+"volumes, see steps 1 and 2 in <xref linkend=\"cli_extend_volumes\"/>."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml206(para)
+msgid "Delete the volume using either the volume name or ID:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml208(para)
+msgid "The delete command does not return any output."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml212(para)
+msgid ""
+"List the volumes again, and note that the status of your volume is "
+"<literal>deleting</literal>:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml222(para)
+msgid ""
+"When the volume is fully deleted, it disappears from the list of volumes:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml234(title)
+msgid "Transfer a volume"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml235(para)
+msgid ""
+"You can transfer a volume from one owner to another by using the "
+"<placeholder-1/> commands. The volume donor, or original owner, creates a "
+"transfer request and sends the created transfer ID and authorization key to "
+"the volume recipient. The volume recipient, or new owner, accepts the "
+"transfer by using the ID and key."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml243(para)
+msgid ""
+"The procedure for volume transfer is intended for tenants (both the volume "
+"donor and recipient) within the same cloud."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml245(para)
+msgid "Use cases include:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml248(para)
+msgid ""
+"Create a custom bootable volume or a volume with a large data set and "
+"transfer it to a customer."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml251(para)
+msgid ""
+"For bulk import of data to the cloud, the data ingress system creates a new "
+"Block Storage volume, copies data from the physical device, and transfers "
+"device ownership to the end user."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml258(title)
+msgid "Create a volume transfer request"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml261(para)
+msgid "While logged in as the volume donor, list the available volumes:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml271(para)
+msgid ""
+"As the volume donor, request a volume transfer authorization code for a "
+"specific volume:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml275(para)
+msgid ""
+"The volume must be in an <literal>available</literal> state or the request "
+"will be denied. If the transfer request is valid in the database (that is, "
+"it has not expired or been deleted), the volume is placed in an "
+"<literal>awaiting transfer</literal> state. For example:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml279(para)
+msgid ""
+"The output shows the volume transfer ID in the <literal>id</literal> row and"
+" the authorization key."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml291(para)
+msgid ""
+"Optionally, you can specify a name for the transfer by using the <code"
+">--display-name <replaceable>displayName</replaceable></code> parameter."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml299(para)
+msgid ""
+"Send the volume transfer ID and authorization key to the new owner (for "
+"example, by email)."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml304(para)
+msgid "View pending transfers:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml313(para)
+msgid ""
+"After the volume recipient, or new owner, accepts the transfer, you can see "
+"that the transfer is no longer available:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml325(title)
+msgid "Accept a volume transfer request"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml328(para)
+msgid ""
+"As the volume recipient, you must first obtain the transfer ID and "
+"authorization key from the original owner."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml333(para)
+msgid "Display the transfer request details by using the ID:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml334(replaceable)
+#: ./doc/common/section_cli_cinder_manage_volumes.xml348(replaceable)
+#: ./doc/common/section_cli_cinder_manage_volumes.xml392(replaceable)
+msgid "transferID"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml347(para)
+msgid "Accept the request:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml348(replaceable)
+msgid "authKey"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml359(para)
+msgid ""
+"If you do not have a sufficient quota for the transfer, the transfer is "
+"refused."
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml367(title)
+msgid "Delete a volume transfer"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml371(para)
+msgid "List available volumes and their statuses:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml382(para)
+msgid "Find the matching transfer ID:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml391(para)
+msgid "Delete the volume:"
+msgstr ""
+
+#: ./doc/common/section_cli_cinder_manage_volumes.xml397(para)
+msgid ""
+"Verify that transfer list is now empty and that the volume is again "
+"available for transfer:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_search_ip.xml7(title)
+msgid "Search for an instance using IP address"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_search_ip.xml8(para)
+msgid ""
+"You can search for an instance using the IP address parameter, "
+"<literal>--ip</literal>, with the <placeholder-1/> command."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_search_ip.xml11(parameter)
+#: ./doc/common/section_cli_nova_search_ip.xml14(parameter)
+msgid "ip"
+msgstr "ip"
+
+#: ./doc/common/section_cli_nova_search_ip.xml11(replaceable)
+msgid "IP_ADDRESS"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_search_ip.xml12(para)
+msgid ""
+"The following example shows the results of a search on "
+"<filename>10.0.0.4</filename>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_search_ip.xml14(replaceable)
+msgid "10.0.0.4"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml5(title)
+msgid "OpenStack Compute"
+msgstr "OpenStack Compute"
+
+#: ./doc/common/section_getstart_compute.xml6(para)
+msgid ""
+"OpenStack Compute is used to host and manage cloud computing systems and is "
+"a major part of an infrastructure-as-a-service (IaaS) system. The main "
+"modules are implemented in Python."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml9(para)
+msgid ""
+"OpenStack Compute interacts with OpenStack Identity for authentication, "
+"OpenStack Image Service for images, and OpenStack dashboard for the user and"
+" administrative interface. Access to images is limited by project and by "
+"user; quotas are limited per project (for example, the number of instances)."
+" OpenStack Compute can scale horizontally on standard hardware, and download"
+" images to launch instances."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml15(para)
+msgid ""
+"OpenStack Compute consists of the following areas and their components:"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml17(title)
+msgid "API"
+msgstr "API"
+
+#: ./doc/common/section_getstart_compute.xml19(systemitem)
+msgid "nova-api service"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml20(para)
+msgid ""
+"Accepts and responds to end user compute API calls. Supports the OpenStack "
+"Compute API, the Amazon EC2 API, and a special Admin API for privileged "
+"users to perform administrative actions. It enforces some policies and "
+"initiates most orchestration activities, such as running an instance."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml28(term)
+msgid "<systemitem class=\"service\">nova-api-metadata</systemitem> service"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml30(para)
+msgid ""
+"Accepts metadata requests from instances. The <systemitem class=\"service"
+"\">nova-api-metadata</systemitem> service is generally used when you run in "
+"multi-host mode with <systemitem class=\"service\">nova-network</systemitem>"
+" installations. For details, see <link href=\"http://docs.openstack.org"
+"/admin-guide-cloud/content/section_metadata-service.html\">Metadata "
+"service</link> in the <citetitle>Cloud Administrator Guide</citetitle>."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml38(para)
+msgid ""
+"On Debian systems, it is included in the <systemitem class=\"service\">nova-"
+"api</systemitem> package, and can be selected through "
+"<package>debconf</package>."
+msgstr "Debian システムの場合、<systemitem class=\"service\">nova-api</systemitem> パッケージに含まれます。<package>debconf</package> 経由で選択できます。"
+
+#: ./doc/common/section_getstart_compute.xml44(title)
+msgid "Compute core"
+msgstr "Compute コア"
+
+#: ./doc/common/section_getstart_compute.xml46(term)
+msgid "<systemitem class=\"service\">nova-compute</systemitem> process"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml47(para)
+msgid ""
+"A worker daemon that creates and terminates virtual machine instances "
+"through hypervisor APIs. For example, XenAPI for XenServer/XCP, libvirt for "
+"KVM or QEMU and VMwareAPI for VMware. Processing is fairly complex but "
+"fundamentally it accepts actions from the queue and performs a series of "
+"system commands, like launching a KVM instance, whilst updating its state in"
+" the database."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml56(term)
+msgid "<systemitem class=\"service\">nova-scheduler</systemitem> process"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml58(para)
+msgid ""
+"Conceptually the simplest piece of code in OpenStack Compute. It takes a "
+"virtual machine instance request from the queue and determines on which "
+"compute server host it will run."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml64(term)
+msgid "<systemitem class=\"service\">nova-conductor</systemitem> module"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml65(para)
+msgid ""
+"Mediates interactions between <systemitem class=\"service\">nova-"
+"compute</systemitem> and the database. It eliminates direct accesses to the "
+"cloud database made by <systemitem class=\"service\">nova-"
+"compute</systemitem>. The <systemitem class=\"service\">nova-"
+"conductor</systemitem> module scales horizontally. However, do not deploy it"
+" on any nodes where <systemitem class=\"service\">nova-compute</systemitem> "
+"runs. For more information, see <link "
+"href=\"http://russellbryantnet.wordpress.com/2012/11/19/a-new-nova-service-"
+"nova-conductor/\">A new Nova service: nova-conductor</link>."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml79(title)
+msgid "Networking for VMs"
+msgstr "仮想マシン用ネットワーク"
+
+#: ./doc/common/section_getstart_compute.xml80(term)
+msgid "<systemitem class=\"service\">nova-network</systemitem> worker daemon"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml82(para)
+msgid ""
+"Similar to <systemitem class=\"service\">nova-compute</systemitem>, it "
+"accepts networking tasks from the queue and performs tasks to manipulate the"
+" network, such as setting up bridging interfaces or changing iptables rules."
+" This functionality is being migrated to OpenStack Networking."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml90(term)
+msgid "<systemitem class=\"service\">nova-dhcpbridge</systemitem> script"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml92(para)
+msgid ""
+"The IP address leases and is recorded in the database using the dnsmasq "
+"<literal>dhcp-script</literal> facility. This functionality is being "
+"migrated to OpenStack Networkin which provides a different script."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml99(title)
+msgid "Console interface"
+msgstr "コンソールインターフェース"
+
+#: ./doc/common/section_getstart_compute.xml101(term)
+msgid "<systemitem class=\"service\">nova-consoleauth</systemitem> daemon"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml102(para)
+msgid ""
+"Authorizes tokens for users that console proxies provide. See <systemitem "
+"class=\"service\">nova-novncproxy</systemitem> and <systemitem "
+"class=\"service\">nova-xvpnvcproxy</systemitem>. This service must be "
+"running for console proxies to work. Many proxies of either type can be run "
+"against a single <systemitem class=\"service\">nova-consoleauth</systemitem>"
+" service in a cluster configuration. For information, see <link "
+"href=\"http://docs.openstack.org/trunk/config-reference/content/about-nova-"
+"consoleauth.html\">About nova-consoleauth</link>."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml114(term)
+msgid "<systemitem class=\"service\">nova-novncproxy</systemitem> daemon"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml116(para)
+msgid ""
+"Provides a proxy for accessing running instances through a VNC connection. "
+"Supports browser-based novnc clients."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml121(term)
+msgid "<systemitem class=\"service\">nova-xvpnvncproxy</systemitem> daemon"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml123(para)
+msgid ""
+"A proxy for accessing running instances through a VNC connection. It "
+"supports a Java client specifically designed for OpenStack."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml128(term)
+msgid "<systemitem class=\"service\">nova-cert</systemitem> daemon"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml129(para)
+msgid "x509 certificates."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml132(para)
+msgid ""
+"In Debian, a unique <package>nova-consoleproxy</package> package provides "
+"the <package>nova-novncproxy</package>, <package>nova-"
+"spicehtml5proxy</package>, and <package>nova-xvpvncproxy</package> packages."
+" To select packages, edit the <filename>/etc/default/nova-"
+"consoleproxy</filename> file or use the <package>debconf</package> "
+"interface. You can also manually edit the <filename>/etc/default/nova-"
+"consoleproxy</filename> file, and stop and start the console daemons."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml142(title)
+msgid "Image management (EC2 scenario)"
+msgstr "イメージ管理 (EC2 シナリオ)"
+
+#: ./doc/common/section_getstart_compute.xml144(term)
+msgid "<systemitem class=\"service\">nova-objectstore</systemitem> daemon"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml145(para)
+msgid ""
+"A S3 interface for registering images with the OpenStack Image Service. It "
+"is mainly used for installations that must support euca2ools. The euca2ools "
+"tools talk to <systemitem class=\"service\">nova-objectstore</systemitem> in"
+" <emphasis role=\"italic\">S3 language</emphasis>, and <systemitem "
+"class=\"service\">nova-objectstore</systemitem> translates S3 requests into "
+"Image service requests."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml154(term)
+msgid "euca2ools client"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml155(para)
+msgid ""
+"A set of command-line interpreter commands for managing cloud resources. "
+"Although it is not an OpenStack module, you can configure <systemitem "
+"class=\"service\">nova-api</systemitem> to support this EC2 interface. For "
+"more information, see the <link "
+"href=\"https://www.eucalyptus.com/docs/eucalyptus/3.4/index.html\">Eucalyptus"
+" 3.4 Documentation</link>."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml163(title)
+msgid "Command-line clients and other interfaces"
+msgstr "コマンドラインクライアントと他のインターフェース"
+
+#: ./doc/common/section_getstart_compute.xml164(term)
+msgid "nova client"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml165(para)
+msgid "Allows users to submit commands as a tenant administrator or end user."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml169(term)
+msgid "nova-manage client"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml170(para)
+msgid "Enables cloud administrators to submit commands."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml174(title)
+msgid "Other components"
+msgstr "他のコンポーネント"
+
+#: ./doc/common/section_getstart_compute.xml175(term)
+msgid "The queue"
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml175(para)
+msgid ""
+"A central hub for passing messages between daemons. It is usually "
+"implemented with <link href=\"http://www.rabbitmq.com/\">RabbitMQ</link>, "
+"but could be any AMQP message queue, such as <link "
+"href=\"http://qpid.apache.org/\">Apache Qpid</link> or <link "
+"href=\"http://www.zeromq.org/\">Zero MQ</link>."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml183(term)
+msgid "SQL database"
+msgstr "SQL データベース"
+
+#: ./doc/common/section_getstart_compute.xml184(para)
+msgid ""
+"Stores most build-time and runtime states for a cloud infrastructure. It "
+"includes instance types that are available for use, instances in use, "
+"available networks, and projects. Theoretically, OpenStack Compute can "
+"support any database that is supported by SQL-Alchemy. Note the databases "
+"which are widely used are SQLite3 databases (for test and development work),"
+" MySQL, and PostgreSQL."
+msgstr ""
+
+#: ./doc/common/section_getstart_compute.xml192(para)
+msgid ""
+"OpenStack Compute interacts with OpenStack Identity for authentication; "
+"OpenStack Image Service for images; and the OpenStack dashboard for a web "
+"interface."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_manage_images.xml6(title)
+msgid "Create an image (nova)"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_manage_images.xml7(para)
+msgid ""
+"You can use the <placeholder-1/> client to take a snapshot of a running "
+"instance to create an image."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_manage_images.xml9(para)
+msgid ""
+"To minimize the potential for data loss and ensure that you create an "
+"accurate image, you should shut down the instance before you take a "
+"snapshot."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_manage_images.xml12(para)
+msgid ""
+"You cannot create a snapshot from an instance that has an attached volume. "
+"Detach the volume, create the image, and remount the volume."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_manage_images.xml18(para)
+msgid ""
+"For more information, see <link href=\"http://docs.openstack.org/trunk"
+"/openstack-ops/content/snapshots.html\">Taking Snapshots</link> in the "
+"<citetitle>OpenStack Operations Guide</citetitle>."
+msgstr "詳細情報は、<citetitle>OpenStack 運用ガイド</citetitle> の<link href=\"http://docs.openstack.org/trunk/openstack-ops/content/snapshots.html\">スナップショットの作成方法</link>を参照してください。"
+
+#: ./doc/common/section_cli_nova_manage_images.xml24(para)
+msgid "List instances to get the server name:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_manage_images.xml31(para)
+msgid ""
+"In this example, the server is named <literal>myCirrosServer</literal>."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_manage_images.xml33(para)
+msgid ""
+"Use this server to create a snapshot: <placeholder-1/>The command creates a "
+"qemu snapshot and automatically uploads the image to your repository. Only "
+"the tenant that creates the image has access to it."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_manage_images.xml81(para)
+msgid ""
+"To launch an instance from your image, include the image ID and flavor ID, "
+"as in the following example:"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml6(title)
+msgid "Groups"
+msgstr "グループ"
+
+#: ./doc/common/section_keystone-concepts-group-management.xml7(para)
+msgid ""
+"A group is a collection of users. Administrators can create groups and add "
+"users to them. Then, rather than assign a role to each user individually, "
+"assign a role to the group. Every group is in a domain. Groups were "
+"introduced with the Identity API v3."
+msgstr ""
+
+#. TODO: eventually remove the last sentence, when v3 is
+#.              commonplace
+#: ./doc/common/section_keystone-concepts-group-management.xml14(para)
+msgid "Identity API V3 provides the following group-related operations:"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml18(para)
+msgid "Create a group"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml21(para)
+msgid "Delete a group"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml24(para)
+msgid "Update a group (change its name or description)"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml28(para)
+msgid "Add a user to a group"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml31(para)
+msgid "Remove a user from a group"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml34(para)
+msgid "List group members"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml37(para)
+msgid "List groups for a user"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml40(para)
+msgid "Assign a role on a tenant to a group"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml43(para)
+msgid "Assign a role on a domain to a group"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml46(para)
+msgid "Query role assignments to groups"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml50(para)
+msgid ""
+"The Identity service server might not allow all operations. For example, if "
+"using the Identity server with the LDAP Identity back end and group updates "
+"are disabled, then a request to create, delete, or update a group fails."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml56(para)
+msgid "Here are a couple of examples:"
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml59(para)
+msgid ""
+"Group A is granted Role A on Tenant A. If User A is a member of Group A, "
+"when User A gets a token scoped to Tenant A, the token also includes Role A."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-group-management.xml65(para)
+msgid ""
+"Group B is granted Role B on Domain B. If User B is a member of Domain B, if"
+" User B gets a token scoped to Domain B, the token also includes Role B."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-assignments.xml6(title)
+msgid "Separate role authorization and user authentication"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-assignments.xml7(para)
+msgid ""
+"When you configure the Identity service to use an LDAP back end, you can "
+"split authentication and authorization using the "
+"<emphasis>Assignments</emphasis> feature."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-assignments.xml10(para)
+msgid ""
+"The Assignments feature enables administrators to manage project role "
+"authorization using the Identity service's own SQL database, while still "
+"providing user authentication through the LDAP directory."
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-assignments.xml14(para)
+msgid "To configure this:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-assignments.xml16(title)
+msgid ""
+"Separating role authorization and user authentication through Assignments"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-assignments.xml19(para)
+msgid ""
+"Configure the Identity service to authenticate users through the LDAP "
+"driver. To do so, first find the <literal>[identity]</literal> section in "
+"the <filename>/etc/keystone/keystone.conf</filename> configuration file. "
+"Then, set the <literal>driver</literal> configuration key in that section to"
+" <literal>keystone.identity.backends.ldap.Identity</literal>:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-assignments.xml30(para)
+msgid ""
+"Next, enable the Assignment driver. To do so, find the "
+"<literal>[assignment]</literal> section in the "
+"<filename>/etc/keystone/keystone.conf</filename> configuration file. Then, "
+"set the <literal>driver</literal> configuration key in that section to "
+"<literal>keystone.assignment.backends.sql.Assignment</literal>:"
+msgstr ""
+
+#: ./doc/common/section_keystone_config_ldap-assignments.xml41(para)
+msgid ""
+"On distributions that include <application>openstack-config</application>, "
+"you can configure both drivers by running the following commands instead:"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml7(title)
+msgid "Install the OpenStack command-line clients"
+msgstr "OpenStack コマンドラインクライアントのインストール"
+
+#: ./doc/common/section_cli_install.xml8(para)
+msgid ""
+"Install the prerequisite software and the Python package for each OpenStack "
+"client."
+msgstr "前提ソフトウェアと各 OpenStack クライアント用の Python パッケージをインストールします。"
+
+#: ./doc/common/section_cli_install.xml11(title)
+msgid "Install the prerequisite software"
+msgstr "前提ソフトウェアのインストール"
+
+#: ./doc/common/section_cli_install.xml13(para)
+msgid ""
+"Most Linux distributions include packaged versions of the command-line "
+"clients that you can install directly, see <xref "
+"linkend=\"cli_clients_install_packages\"/>."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml17(para)
+msgid ""
+"If you need to install the command-line packages source packages, the "
+"following table lists the software that you need to have to run the command-"
+"line clients, and provides installation instructions as needed."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml24(caption)
+msgid "Prerequisite software"
+msgstr "前提ソフトウェア"
+
+#: ./doc/common/section_cli_install.xml29(th)
+msgid "Prerequisite"
+msgstr "前提"
+
+#: ./doc/common/section_cli_install.xml36(para)
+msgid "Python 2.6 or later"
+msgstr "Python 2.6 またはそれ以降"
+
+#: ./doc/common/section_cli_install.xml39(para)
+msgid "Currently, the clients do not support Python 3."
+msgstr "現在、クライアントは Python 3 をサポートしません。"
+
+#: ./doc/common/section_cli_install.xml45(para)
+msgid "<package>setuptools</package> package"
+msgstr "<package>setuptools</package> パッケージ"
+
+#: ./doc/common/section_cli_install.xml48(para)
+msgid "Installed by default on Mac OS X."
+msgstr "Mac OS X に標準でインストールされます。"
+
+#: ./doc/common/section_cli_install.xml49(para)
+msgid ""
+"Many Linux distributions provide packages to make "
+"<package>setuptools</package> easy to install. Search your package manager "
+"for <package>setuptools</package> to find an installation package. If you "
+"cannot find one, download the <package>setuptools</package> package directly"
+" from <link "
+"href=\"http://pypi.python.org/pypi/setuptools\">http://pypi.python.org/pypi/setuptools</link>."
+msgstr "多くの Linux ディストリビューションはインストールしやすい <package>setuptools</package> パッケージを提供します。インストールパッケージを検索するために、パッケージマネージャーで <package>setuptools</package> を検索します。見つけられない場合、<link href=\"http://pypi.python.org/pypi/setuptools\">http://pypi.python.org/pypi/setuptools</link> から <package>setuptools</package> パッケージを直接ダウンロードします。"
+
+#: ./doc/common/section_cli_install.xml57(para)
+msgid ""
+"The recommended way to install <package>setuptools</package> on Microsoft "
+"Windows is to follow the documentation provided <link "
+"href=\"https://pypi.python.org/pypi/setuptools#windows\">on the setuptools "
+"website</link>. Another option is to use the unofficial binary installer "
+"maintained by Christoph Gohlke (<link "
+"href=\"http://www.lfd.uci.edu/~gohlke/pythonlibs/#setuptools\">http://www.lfd.uci.edu/~gohlke/pythonlibs/#setuptools</link>)."
+msgstr "Microsoft Windows に <package>setuptools</package> をインストールする推奨の方法は <link href=\"https://pypi.python.org/pypi/setuptools#windows\">setuptools ウェブサイト</link> で提供されているドキュメントに従うことです。他の選択肢は hristoph Gohlke (<link href=\"http://www.lfd.uci.edu/~gohlke/pythonlibs/#setuptools\">http://www.lfd.uci.edu/~gohlke/pythonlibs/#setuptools</link>) によりメンテナンスされている非公式のバイナリインストーラーを使用することです。"
+
+#: ./doc/common/section_cli_install.xml70(package)
+msgid "pip"
+msgstr "pip"
+
+#: ./doc/common/section_cli_install.xml70(td)
+msgid "<placeholder-1/> package"
+msgstr "<placeholder-1/> パッケージ"
+
+#: ./doc/common/section_cli_install.xml72(para)
+msgid ""
+"To install the clients on a Linux, Mac OS X, or Microsoft Windows system, "
+"use <package>pip</package>. It is easy to use, ensures that you get the "
+"latest version of the clients from the <link "
+"href=\"http://pypi.python.org/\">Python Package Index</link>, and lets you "
+"update or remove the packages later on."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml81(para)
+msgid ""
+"Install <package>pip</package> through the package manager for your system:"
+msgstr "お使いのシステムのパッケージマネージャーを利用して <package>pip</package> をインストールします。"
+
+#: ./doc/common/section_cli_install.xml84(title)
+msgid "MacOS"
+msgstr "MacOS"
+
+#: ./doc/common/section_cli_install.xml88(title)
+msgid "Microsoft Windows"
+msgstr "Microsoft Windows"
+
+#: ./doc/common/section_cli_install.xml89(para)
+msgid ""
+"Ensure that the <filename>C:\\Python27\\Scripts</filename> directory is "
+"defined in the <literal>PATH</literal> environment variable, and use the "
+"<placeholder-1/> command from the <package>setuptools</package> package: "
+"<placeholder-2/>Another option is to use the unofficial binary installer "
+"provided by Christoph Gohlke (<link "
+"href=\"http://www.lfd.uci.edu/~gohlke/pythonlibs/#pip\">http://www.lfd.uci.edu/~gohlke/pythonlibs/#pip</link>)."
+msgstr "<filename>C:\\Python27\\Scripts</filename> ディレクトリが <literal>PATH</literal> 環境変数に定義され、<package>setuptools</package> パッケージから <placeholder-1/> コマンドを使用できることを確認します。 <placeholder-2/> もう一つの選択肢は Christoph Gohlke (<link href=\"http://www.lfd.uci.edu/~gohlke/pythonlibs/#pip\">http://www.lfd.uci.edu/~gohlke/pythonlibs/#pip</link>) により提供されている非公式のバイナリインストーラーを使用することです。"
+
+#: ./doc/common/section_cli_install.xml106(title)
+msgid "Ubuntu and Debian"
+msgstr "Ubuntu と Debian"
+
+#: ./doc/common/section_cli_install.xml112(title)
+msgid "Red Hat Enterprise Linux, CentOS, or Fedora"
+msgstr "Red Hat Enterprise Linux、CentOS、Fedora"
+
+#: ./doc/common/section_cli_install.xml113(para)
+msgid ""
+"A packaged version enables you to use <package>yum</package> to install the "
+"package: <placeholder-1/> There are also packaged versions of the clients "
+"available in <link href=\"http://openstack.redhat.com/\">RDO</link> that "
+"enable <package>yum</package> to install the clients as described in <xref "
+"linkend=\"cli_clients_install_packages\"/>."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml125(title)
+msgid "SUSE Linux Enterprise Linux 11"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml126(para)
+msgid ""
+"A <link href=\"https://build.opensuse.org/package/show?package=python-"
+"pip&amp;project=Cloud:OpenStack:Master\">packaged version available in the "
+"Open Build Service</link> enables you to use or <package>zypper</package> to"
+" install the package. First, add the Open Build Service repository: "
+"<placeholder-1/> Then install <package>pip</package> and use it to manage "
+"client installation: <placeholder-2/> There are also packaged versions of "
+"the clients available that enable <package>zypper</package> to install the "
+"clients as described in <xref linkend=\"cli_clients_install_packages\"/>."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml141(title)
+msgid "openSUSE"
+msgstr "openSUSE"
+
+#: ./doc/common/section_cli_install.xml142(para)
+msgid ""
+"You can install <package>pip</package> and use it to manage client "
+"installation: <placeholder-1/> There are also packaged versions of the "
+"clients available that enable <package>zypper</package> to install the "
+"clients as described in <xref linkend=\"cli_clients_install_packages\"/>"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml157(title)
+msgid "Install the clients"
+msgstr "クライアントのインストール"
+
+#: ./doc/common/section_cli_install.xml158(para)
+msgid ""
+"When following the instructions in this section, replace "
+"<replaceable>PROJECT</replaceable> with the lowercase name of the client to "
+"install, such as <placeholder-1/>. Repeat for each client. The following "
+"values are valid:"
+msgstr "このセクションにある説明に従うとき、<placeholder-1/> のように、インストールするクライアントの小文字名で <replaceable>PROJECT</replaceable> を置き換えてください。各クライアントに対して繰り返します。以下の値が有効です。"
+
+#: ./doc/common/section_cli_install.xml165(para)
+msgid "<literal>ceilometer</literal> - Telemetry API"
+msgstr "<literal>ceilometer</literal> - Telemetry API"
+
+#: ./doc/common/section_cli_install.xml169(para)
+msgid "<literal>cinder</literal> - Block Storage API and extensions"
+msgstr "<literal>cinder</literal> - Block Storage API およびその拡張"
+
+#: ./doc/common/section_cli_install.xml173(para)
+msgid "<literal>glance</literal> - Image Service API"
+msgstr "<literal>glance</literal> - Image Service API"
+
+#: ./doc/common/section_cli_install.xml177(para)
+msgid "<literal>heat</literal> - Orchestration API"
+msgstr "<literal>heat</literal> - Orchestration API"
+
+#: ./doc/common/section_cli_install.xml181(para)
+msgid "<literal>keystone</literal> - Identity service API and extensions"
+msgstr "<literal>keystone</literal> - Identity service API およびその拡張"
+
+#: ./doc/common/section_cli_install.xml185(para)
+msgid "<literal>neutron</literal> - Networking API"
+msgstr "<literal>neutron</literal> - Networking API"
+
+#: ./doc/common/section_cli_install.xml189(para)
+msgid "<literal>nova</literal> - Compute API and extensions"
+msgstr "<literal>nova</literal> - Compute API およびその拡張"
+
+#: ./doc/common/section_cli_install.xml193(para)
+msgid "<literal>swift</literal> - Object Storage API"
+msgstr "<literal>swift</literal> - Object Storage API"
+
+#: ./doc/common/section_cli_install.xml197(para)
+msgid "<literal>trove</literal> - Database Service API"
+msgstr "<literal>trove</literal> - Database Service API"
+
+#: ./doc/common/section_cli_install.xml201(para)
+msgid ""
+"The following example shows the command for installing the nova client with "
+"<replaceable>pip</replaceable>."
+msgstr "以下の例は、<replaceable>pip</replaceable> を用いて nova クライアントをインストールするコマンドです。"
+
+#: ./doc/common/section_cli_install.xml206(title)
+msgid "Installing with pip"
+msgstr "pip を用いたインストール"
+
+#: ./doc/common/section_cli_install.xml207(para)
+msgid ""
+"Use <package>pip</package> to install the OpenStack clients on a Linux, Mac "
+"OS X, or Microsoft Windows system. It is easy to use and ensures that you "
+"get the latest version of the client from the <link "
+"href=\"http://pypi.python.org/pypi\">Python Package Index</link>. Also, "
+"<package>pip</package> enables you to update or remove a package."
+msgstr "Linux、Mac OS X、Microsoft Windows システムにクライアントをインストールするために <package>pip</package> を使用します。これは使いやすく、必ず <link href=\"http://pypi.python.org/pypi\">Python Package Index</link> から最新バージョンのクライアントを取得します。また、<package>pip</package> がパッケージの更新や削除ができます。"
+
+#: ./doc/common/section_cli_install.xml214(para)
+msgid "Install each client separately by using the following command:"
+msgstr "以下のコマンドを使用して、各クライアントをそれぞれインストールします。"
+
+#: ./doc/common/section_cli_install.xml217(para)
+msgid "For Mac OS X or Linux:"
+msgstr "Mac OS X または Linux の場合:"
+
+#: ./doc/common/section_cli_install.xml218(replaceable)
+#: ./doc/common/section_cli_install.xml220(replaceable)
+#: ./doc/common/section_cli_install.xml232(replaceable)
+#: ./doc/common/section_cli_install.xml236(replaceable)
+#: ./doc/common/section_cli_install.xml243(replaceable)
+#: ./doc/common/section_cli_install.xml252(replaceable)
+#: ./doc/common/section_cli_install.xml255(replaceable)
+#: ./doc/common/section_cli_version.xml9(replaceable)
+msgid "PROJECT"
+msgstr "PROJECT"
+
+#: ./doc/common/section_cli_install.xml219(para)
+msgid "For Microsoft Windows:"
+msgstr "Microsoft Windows の場合:"
+
+#: ./doc/common/section_cli_install.xml224(title)
+msgid "Installing from packages"
+msgstr "パッケージからのインストール"
+
+#: ./doc/common/section_cli_install.xml225(para)
+msgid ""
+"RDO, openSUSE and SUSE Linux Enterprise have client packages that can be "
+"installed without <filename>pip</filename>."
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml227(para)
+msgid ""
+"On Red Hat Enterprise Linux, CentOS, or Fedora, use <placeholder-1/> to "
+"install the clients from the packaged versions available in <link "
+"href=\"http://openstack.redhat.com/\">RDO</link>: <placeholder-2/>"
+msgstr "Red Hat Enterprise Linux、CentOS、Fedora の場合、<link href=\"http://openstack.redhat.com/\">RDO</link> にあるパッケージ化されたバージョンからクライアントをインストールするために、<placeholder-1/> を使用します。<placeholder-2/>"
+
+#: ./doc/common/section_cli_install.xml233(para)
+msgid ""
+"For openSUSE, use <package>zypper</package> to install the clients from the "
+"distribution packages Service: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml237(para)
+msgid ""
+"For SUSE Linux Enterprise Server, use <package>zypper</package> to install "
+"the clients from the distribution packages in the Open Build Service. First,"
+" add the Open Build Service repository: <placeholder-1/> Then you can "
+"install the packages: <placeholder-2/>"
+msgstr ""
+
+#: ./doc/common/section_cli_install.xml248(title)
+msgid "Upgrade or remove clients"
+msgstr "クライアントの更新や削除"
+
+#: ./doc/common/section_cli_install.xml249(para)
+msgid ""
+"To upgrade a client, add the <literal>--upgrade</literal> option to the "
+"<placeholder-1/> command:"
+msgstr "クライアントを更新する場合、<placeholder-1/> コマンドに <literal>--upgrade</literal> オプションを追加します。"
+
+#: ./doc/common/section_cli_install.xml253(para)
+msgid "To remove the a client, run the <placeholder-1/> command:"
+msgstr "クライアントを削除する場合、<placeholder-1/> コマンドを実行します。"
+
+#: ./doc/common/section_cli_install.xml258(title)
+msgid "What's next"
+msgstr "次はどうする"
+
+#: ./doc/common/section_cli_install.xml259(para)
+msgid ""
+"Before you can run client commands, you must create and source the "
+"<filename><replaceable>PROJECT</replaceable>-openrc.sh</filename> file to "
+"set environment variables. See <xref linkend=\"cli_openrc\"/>."
+msgstr "クライアントコマンドを実行する前に、環境変数を設定するために <filename><replaceable>PROJECT</replaceable>-openrc.sh</filename> ファイルを作成して読み込む必要があります。"
+
+#: ./doc/common/section_cli_help.xml6(title)
+msgid "Get help for client commands"
+msgstr "クライアントコマンドのヘルプの取得"
+
+#: ./doc/common/section_cli_help.xml7(para)
+msgid ""
+"To get usage information, including a list of commands with descriptions, "
+"for a client, run the following command:"
+msgstr "クライアントのコマンド一覧、概要、使用法を取得するために、以下のコマンドを実行します。"
+
+#: ./doc/common/section_cli_help.xml9(replaceable)
+#: ./doc/common/section_cli_help.xml59(replaceable)
+msgid "CLIENT_NAME"
+msgstr "CLIENT_NAME"
+
+#: ./doc/common/section_cli_help.xml10(para)
+msgid ""
+"For example, to get help information for the swift client, run the following"
+" command:"
+msgstr "例えば、swift クライアントの情報を取得する場合、以下のコマンドを実行します。"
+
+#: ./doc/common/section_cli_help.xml54(para)
+msgid ""
+"Depending on your credentials, you might not have permission to use every "
+"command."
+msgstr "クレデンシャルによっては、すべてのコマンドを使用する権限がないかもしれません。"
+
+#: ./doc/common/section_cli_help.xml57(para)
+msgid ""
+"After the <option>help</option> command, you can enter a command name to get"
+" help for that command, as follows:"
+msgstr "<option>help</option> コマンド後、そのコマンドのヘルプを表示するために、以下のとおりコマンド名を入力できます。"
+
+#: ./doc/common/section_cli_help.xml59(replaceable)
+msgid "COMMAND_NAME"
+msgstr "COMMAND_NAME"
+
+#: ./doc/common/section_cli_help.xml60(para)
+msgid ""
+"For example, to get help for the glance <placeholder-1/> command, enter the "
+"following command:"
+msgstr "例えば、glance <placeholder-1/> コマンドのヘルプを取得する場合、以下のコマンドを入力します。"
+
+#: ./doc/common/section_cli_help.xml64(para)
+msgid ""
+"The command returns a description of the command and its positional and "
+"optional arguments:"
+msgstr "このコマンドは、コマンドの説明、位置指定引数、オプション引数を返します。"
+
+#: ./doc/common/section_objectstorage-intro.xml8(para)
+msgid ""
+"OpenStack Object Storage (code-named swift) is open source software for "
+"creating redundant, scalable data storage using clusters of standardized "
+"servers to store petabytes of accessible data. It is a long-term storage "
+"system for large amounts of static data that can be retrieved, leveraged, "
+"and updated. Object Storage uses a distributed architecture with no central "
+"point of control, providing greater scalability, redundancy, and permanence."
+" Objects are written to multiple hardware devices, with the OpenStack "
+"software responsible for ensuring data replication and integrity across the "
+"cluster. Storage clusters scale horizontally by adding new nodes. Should a "
+"node fail, OpenStack works to replicate its content from other active nodes."
+" Because OpenStack uses software logic to ensure data replication and "
+"distribution across different devices, inexpensive commodity hard drives and"
+" servers can be used in lieu of more expensive equipment."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-intro.xml19(para)
+msgid ""
+"Object Storage is ideal for cost effective, scale-out storage. It provides a"
+" fully distributed, API-accessible storage platform that can be integrated "
+"directly into applications or used for backup, archiving, and data "
+"retention."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml8(title)
+msgid "Configuration file format"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml10(para)
+msgid ""
+"OpenStack uses the <glossterm>INI</glossterm> file format for configuration "
+"files. An INI file is a simple text file that specifies options as "
+"<literal>key=value</literal> pairs, grouped into sections. The "
+"<literal>DEFAULT</literal> section contains most of the configuration "
+"options. Lines starting with a hash sign (<literal>#</literal>) are comment "
+"lines. For example:"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml29(replaceable)
+msgid "KEYSTONE_DBPASS"
+msgstr "KEYSTONE_DBPASS"
+
+#: ./doc/common/section_config_format.xml29(replaceable)
+msgid "controller"
+msgstr "controller"
+
+#: ./doc/common/section_config_format.xml32(para)
+msgid ""
+"Options can have different type for values. The comments in the sample "
+"config files always mention these. The following types are used by "
+"OpenStack:"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml39(term)
+msgid "boolean value"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml41(para)
+msgid ""
+"Enables or disables an option. The allowed values are "
+"<literal>true</literal> and <literal>false</literal>."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml51(term)
+msgid "floating point value"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml53(para)
+msgid ""
+"A floating point number like <literal>0.25</literal> or "
+"<literal>1000</literal>."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml62(term)
+msgid "integer value"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml64(para)
+msgid ""
+"An integer number is a number without fractional components, like "
+"<literal>0</literal> or <literal>42</literal>."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml74(term)
+msgid "list value"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml76(para)
+msgid ""
+"Represents values of other types, separated by commas. As an example, the "
+"following sets <option>allowed_rpc_exception_modules</option> to a list "
+"containing the four elements <literal>oslo.messaging.exceptions</literal>, "
+"<literal>nova.exception</literal>, <literal>cinder.exception</literal>, and "
+"<literal>exceptions</literal>:"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml92(term)
+msgid "multi valued"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml94(para)
+msgid ""
+"A multi-valued option is a string value and can be given more than once, all"
+" values will be used."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml105(term)
+msgid "string value"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml107(para)
+msgid "Strings can be optionally enclosed with single or double quotes."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml127(title)
+msgid "Sections"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml134(literal)
+#: ./doc/common/tables/ceilometer-database.xml19(th)
+#: ./doc/common/tables/neutron-openvswitch_agent.xml19(th)
+#: ./doc/common/tables/heat-clients.xml19(th)
+#: ./doc/common/tables/cinder-solidfire.xml19(th)
+#: ./doc/common/tables/neutron-rpc.xml19(th)
+#: ./doc/common/tables/nova-periodic.xml19(th)
+#: ./doc/common/tables/keystone-policy.xml19(th)
+#: ./doc/common/tables/glance-auth_token.xml19(th)
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml19(th)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml7(literal)
+#: ./doc/common/tables/ceilometer-redis.xml19(th)
+#: ./doc/common/tables/cinder-storage_ceph.xml19(th)
+#: ./doc/common/tables/nova-testing.xml19(th)
+#: ./doc/common/tables/nova-metadata.xml19(th)
+#: ./doc/common/tables/cinder-hp3par.xml19(th)
+#: ./doc/common/tables/keystone-misc.xml19(th)
+#: ./doc/common/tables/neutron-scheduler.xml19(th)
+#: ./doc/common/tables/glance-rbd.xml19(th)
+#: ./doc/common/tables/cinder-storage_xen.xml19(th)
+#: ./doc/common/tables/ceilometer-common.xml19(th)
+#: ./doc/common/tables/cinder-database.xml19(th)
+#: ./doc/common/tables/ceilometer-logging.xml19(th)
+#: ./doc/common/tables/heat-common.xml19(th)
+#: ./doc/common/tables/nova-ipv6.xml19(th)
+#: ./doc/common/tables/nova-vnc.xml19(th)
+#: ./doc/common/tables/trove-qpid.xml19(th)
+#: ./doc/common/tables/keystone-api.xml19(th)
+#: ./doc/common/tables/glance-rpc.xml19(th)
+#: ./doc/common/tables/neutron-policy.xml19(th)
+#: ./doc/common/tables/nova-xen.xml19(th)
+#: ./doc/common/tables/trove-amqp.xml19(th)
+#: ./doc/common/tables/glance-matchmaker.xml19(th)
+#: ./doc/common/tables/nova-rabbitmq.xml19(th)
+#: ./doc/common/tables/nova-policy.xml19(th)
+#: ./doc/common/tables/ceilometer-inspector.xml19(th)
+#: ./doc/common/tables/cinder-scheduler.xml19(th)
+#: ./doc/common/tables/neutron-logging.xml19(th)
+#: ./doc/common/tables/nova-availabilityzones.xml19(th)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml19(th)
+#: ./doc/common/tables/neutron-rootwrap.xml19(th)
+#: ./doc/common/tables/cinder-auth.xml19(th)
+#: ./doc/common/tables/heat-qpid.xml19(th)
+#: ./doc/common/tables/neutron-auth_token.xml19(th)
+#: ./doc/common/tables/nova-ldap.xml19(th)
+#: ./doc/common/tables/ceilometer-auth.xml19(th)
+#: ./doc/common/tables/cinder-quota.xml19(th)
+#: ./doc/common/tables/nova-compute.xml19(th)
+#: ./doc/common/tables/keystone-rabbit.xml19(th)
+#: ./doc/common/tables/cinder-backups_ceph.xml19(th)
+#: ./doc/common/tables/heat-cfn_api.xml19(th)
+#: ./doc/common/tables/neutron-vmware.xml19(th)
+#: ./doc/common/tables/nova-zeromq.xml19(th)
+#: ./doc/common/tables/cinder-storage.xml19(th)
+#: ./doc/common/tables/glance-registry.xml19(th)
+#: ./doc/common/tables/heat-quota.xml19(th)
+#: ./doc/common/tables/nova-common.xml19(th)
+#: ./doc/common/tables/nova-volumes.xml19(th)
+#: ./doc/common/tables/neutron-redis.xml19(th)
+#: ./doc/common/tables/heat-zeromq.xml19(th)
+#: ./doc/common/tables/heat-amqp.xml19(th)
+#: ./doc/common/tables/nova-redis.xml19(th)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml7(literal)
+#: ./doc/common/tables/nova-db.xml19(th)
+#: ./doc/common/tables/glance-rabbitmq.xml19(th)
+#: ./doc/common/tables/neutron-l3_agent.xml19(th)
+#: ./doc/common/tables/glance-policy.xml19(th)
+#: ./doc/common/tables/nova-neutron.xml19(th)
+#: ./doc/common/tables/cinder-backups.xml19(th)
+#: ./doc/common/tables/glance-vmware.xml19(th)
+#: ./doc/common/tables/cinder-zoning.xml19(th)
+#: ./doc/common/tables/heat-notification.xml19(th)
+#: ./doc/common/tables/nova-vpn.xml19(th)
+#: ./doc/common/tables/trove-common.xml19(th)
+#: ./doc/common/tables/trove-api.xml19(th)
+#: ./doc/common/tables/cinder-zadara.xml19(th)
+#: ./doc/common/tables/nova-conductor.xml19(th)
+#: ./doc/common/tables/nova-livemigration.xml19(th)
+#: ./doc/common/tables/heat-rabbitmq.xml19(th)
+#: ./doc/common/tables/keystone-amqp.xml19(th)
+#: ./doc/common/tables/keystone-rpc.xml19(th)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml7(literal)
+#: ./doc/common/tables/cinder-zones.xml19(th)
+#: ./doc/common/tables/cinder-scality.xml19(th)
+#: ./doc/common/tables/neutron-agent.xml19(th)
+#: ./doc/common/tables/cinder-emc.xml19(th)
+#: ./doc/common/tables/cinder-vmware.xml19(th)
+#: ./doc/common/tables/heat-metadata_api.xml19(th)
+#: ./doc/common/tables/trove-rabbitmq.xml19(th)
+#: ./doc/common/tables/neutron-kombu.xml19(th)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml19(th)
+#: ./doc/common/tables/neutron-ml2_ofa.xml19(th)
+#: ./doc/common/tables/glance-api.xml19(th)
+#: ./doc/common/tables/heat-waitcondition_api.xml19(th)
+#: ./doc/common/tables/cinder-storwize.xml19(th)
+#: ./doc/common/tables/cinder-hplefthand.xml19(th)
+#: ./doc/common/tables/glance-s3.xml19(th)
+#: ./doc/common/tables/nova-rootwrap.xml19(th)
+#: ./doc/common/tables/heat-loadbalancer.xml19(th)
+#: ./doc/common/tables/ceilometer-api.xml19(th)
+#: ./doc/common/tables/ceilometer-exchange.xml19(th)
+#: ./doc/common/tables/cinder-lvm.xml19(th)
+#: ./doc/common/tables/trove-dns.xml19(th)
+#: ./doc/common/tables/trove-volume.xml19(th)
+#: ./doc/common/tables/heat-auth_token.xml19(th)
+#: ./doc/common/tables/neutron-quotas.xml19(th)
+#: ./doc/common/tables/cinder-storage_nfs.xml19(th)
+#: ./doc/common/tables/heat-api.xml19(th)
+#: ./doc/common/tables/glance-logging.xml19(th)
+#: ./doc/common/tables/neutron-metering_agent.xml19(th)
+#: ./doc/common/tables/neutron-zeromq.xml19(th)
+#: ./doc/common/tables/cinder-storage_glusterfs.xml19(th)
+#: ./doc/common/tables/cinder-common.xml19(th)
+#: ./doc/common/tables/glance-swift.xml19(th)
+#: ./doc/common/tables/trove-quota.xml19(th)
+#: ./doc/common/tables/cinder-auth_token.xml19(th)
+#: ./doc/common/tables/cinder-xiv.xml19(th)
+#: ./doc/common/tables/nova-glance.xml19(th)
+#: ./doc/common/tables/keystone-auth_token.xml19(th)
+#: ./doc/common/tables/nova-s3.xml19(th)
+#: ./doc/common/tables/nova-pci.xml19(th)
+#: ./doc/common/tables/cinder-api.xml19(th)
+#: ./doc/common/tables/trove-heat.xml19(th)
+#: ./doc/common/tables/glance-sheepdog.xml19(th)
+#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml7(literal)
+#: ./doc/common/tables/cinder-windows.xml19(th)
+#: ./doc/common/tables/cinder-san-solaris.xml19(th)
+#: ./doc/common/tables/keystone-zeromq.xml19(th)
+#: ./doc/common/tables/ceilometer-rpc.xml19(th)
+#: ./doc/common/tables/glance-filesystem.xml19(th)
+#: ./doc/common/tables/trove-rpc.xml19(th)
+#: ./doc/common/tables/ceilometer-swift.xml19(th)
+#: ./doc/common/tables/trove-backup.xml19(th)
+#: ./doc/common/tables/nova-network.xml19(th)
+#: ./doc/common/tables/glance-redis.xml19(th)
+#: ./doc/common/tables/nova-ca.xml19(th)
+#: ./doc/common/tables/neutron-dhcp_agent.xml19(th)
+#: ./doc/common/tables/ceilometer-collector.xml19(th)
+#: ./doc/common/tables/cinder-hds-hus.xml19(th)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml19(th)
+#: ./doc/common/tables/heat-debug.xml19(th)
+#: ./doc/common/tables/nova-kombu.xml19(th)
+#: ./doc/common/tables/trove-guestagent.xml19(th)
+#: ./doc/common/tables/nova-qpid.xml19(th)
+#: ./doc/common/tables/glance-qpid.xml19(th)
+#: ./doc/common/tables/glance-amqp.xml19(th)
+#: ./doc/common/tables/glance-zmq.xml19(th)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml7(literal)
+#: ./doc/common/tables/neutron-testing.xml19(th)
+#: ./doc/common/tables/trove-compute.xml19(th)
+#: ./doc/common/tables/cinder-rpc.xml19(th)
+#: ./doc/common/tables/cinder-hpmsa.xml19(th)
+#: ./doc/common/tables/cinder-storage_gpfs.xml19(th)
+#: ./doc/common/tables/keystone-notification.xml19(th)
+#: ./doc/common/tables/trove-zeromq.xml19(th)
+#: ./doc/common/tables/neutron-lbaas.xml19(th)
+#: ./doc/common/tables/cinder-backups_swift.xml19(th)
+#: ./doc/common/tables/trove-database.xml19(th)
+#: ./doc/common/tables/nova-authentication.xml19(th)
+#: ./doc/common/tables/glance-gridfs.xml19(th)
+#: ./doc/common/tables/neutron-notifier.xml19(th)
+#: ./doc/common/tables/nova-rpc_all.xml19(th)
+#: ./doc/common/tables/nova-scheduling.xml19(th)
+#: ./doc/common/tables/cinder-eqlx.xml19(th)
+#: ./doc/common/tables/heat-redis.xml19(th)
+#: ./doc/common/tables/nova-ec2.xml19(th)
+#: ./doc/common/tables/cinder-block-device.xml19(th)
+#: ./doc/common/tables/neutron-metadata.xml19(th)
+#: ./doc/common/tables/nova-fping.xml19(th)
+#: ./doc/common/tables/neutron-compute.xml19(th)
+#: ./doc/common/tables/glance-imagecache.xml19(th)
+#: ./doc/common/tables/cinder-nas.xml19(th)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml19(th)
+#: ./doc/common/tables/keystone-logging.xml19(th)
+#: ./doc/common/tables/heat-rpc.xml19(th)
+#: ./doc/common/tables/trove-taskmanager.xml19(th)
+#: ./doc/common/tables/heat-cloudwatch_api.xml19(th)
+#: ./doc/common/tables/cinder-images.xml19(th)
+#: ./doc/common/tables/cinder-huawei.xml19(th)
+#: ./doc/common/tables/nova-console.xml19(th)
+#: ./doc/common/tables/cinder-nexenta_nfs.xml19(th)
+#: ./doc/common/tables/nova-quota.xml19(th)
+#: ./doc/common/tables/heat-logging.xml19(th)
+#: ./doc/common/tables/heat-crypt.xml19(th)
+#: ./doc/common/tables/neutron-ssl.xml19(th)
+#: ./doc/common/tables/cinder-coraid.xml19(th)
+#: ./doc/common/tables/neutron-wsgi.xml19(th)
+#: ./doc/common/tables/cinder-compute.xml19(th)
+#: ./doc/common/tables/glance-wsgi.xml19(th)
+#: ./doc/common/tables/neutron-qpid.xml19(th)
+#: ./doc/common/tables/nova-rpc.xml19(th)
+#: ./doc/common/tables/cinder-backups_tsm.xml19(th)
+#: ./doc/common/tables/cinder-san.xml19(th)
+#: ./doc/common/tables/nova-logging.xml19(th)
+#: ./doc/common/tables/keystone-security.xml19(th)
+#: ./doc/common/tables/nova-api.xml19(th)
+#: ./doc/common/tables/trove-auth_token.xml19(th)
+#: ./doc/common/tables/glance-cinder.xml19(th)
+#: ./doc/common/tables/glance-common.xml19(th)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml7(literal)
+#: ./doc/common/tables/trove-nova.xml19(th)
+#: ./doc/common/tables/neutron-rabbitmq.xml19(th)
+#: ./doc/common/tables/keystone-ec2.xml19(th)
+#: ./doc/common/tables/neutron-api.xml19(th)
+#: ./doc/common/tables/trove-logging.xml19(th)
+#: ./doc/common/tables/keystone-redis.xml19(th)
+#: ./doc/common/tables/nova-xvpnvncproxy.xml19(th)
+#: ./doc/common/tables/heat-clients_backends.xml19(th)
+#: ./doc/common/tables/glance-testing.xml19(th)
+#: ./doc/common/tables/neutron-common.xml19(th)
+#: ./doc/common/tables/nova-hypervisor.xml19(th)
+#: ./doc/common/tables/keystone-qpid.xml19(th)
+#: ./doc/common/tables/nova-wsgi.xml19(th)
+#: ./doc/common/tables/nova-configdrive.xml19(th)
+#: ./doc/common/tables/ceilometer-qpid.xml19(th)
+#: ./doc/common/tables/heat-database.xml19(th)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml19(th)
+#: ./doc/common/tables/neutron-db.xml19(th)
+#: ./doc/common/tables/trove-debug.xml19(th)
+#: ./doc/common/tables/trove-swift.xml19(th)
+#: ./doc/common/tables/nova-libvirt.xml19(th)
+#: ./doc/common/tables/ceilometer-amqp.xml19(th)
+#: ./doc/common/tables/glance-ssl.xml19(th)
+#: ./doc/common/tables/keystone-debug.xml19(th)
+#: ./doc/common/tables/cinder-rootwrap.xml19(th)
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml19(th)
+msgid "[DEFAULT]"
+msgstr "[DEFAULT]"
+
+#: ./doc/common/section_config_format.xml136(para)
+msgid ""
+"Contains most configuration options. If the documentation for a "
+"configuration option does not specify its section, assume that it appears in"
+" this section."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml145(literal)
+#: ./doc/common/tables/ceilometer-database.xml38(th)
+#: ./doc/common/tables/cinder-storage.xml134(th)
+#: ./doc/common/tables/nova-db.xml33(th)
+#: ./doc/common/tables/cinder-common.xml226(th)
+#: ./doc/common/tables/cinder-connection.xml19(th)
+#: ./doc/common/tables/glance-db.xml19(th)
+#: ./doc/common/tables/heat-database.xml34(th)
+#: ./doc/common/tables/neutron-db.xml30(th)
+#: ./doc/common/tables/keystone-database.xml19(th)
+msgid "[database]"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml147(para)
+msgid ""
+"Configuration options for the database that stores the state of the "
+"OpenStack service."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml128(para)
+msgid ""
+"Configuration options are grouped by section. Most configuration file "
+"supports at least the following sections: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml158(title)
+msgid "Substitution"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml160(para)
+msgid ""
+"The configuration file supports variable substitution. After you set a "
+"configuration option, it can be referenced in later configuration values "
+"when you precede it with a <literal>$</literal>, like "
+"<literal>$OPTION</literal>."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml167(para)
+msgid ""
+"The following example uses the values of <literal>rabbit_host</literal> and "
+"<literal>rabbit_port</literal> to define the value of the "
+"<literal>rabbit_hosts</literal> option, in this case as "
+"<literal>controller:5672</literal>."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml185(para)
+msgid ""
+"To avoid substitution, use <literal>$$</literal>, it is replaced by a single"
+" <literal>$</literal>. For example, if your LDAP DNS password is "
+"<literal>$xkj432</literal>, specify it, as follows: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml191(para)
+msgid ""
+"The code uses the Python "
+"<literal>string.Template.safe_substitute()</literal> method to implement "
+"variable substitution. For more details on how variable substitution is "
+"resolved, see <link href=\"http://docs.python.org/2/library/string.html"
+"#template-strings\">http://docs.python.org/2/library/string.html#template-"
+"strings</link> and <link "
+"href=\"http://www.python.org/dev/peps/pep-0292/\">PEP 292</link>."
+msgstr ""
+
+#: ./doc/common/section_config_format.xml204(title)
+msgid "Whitespace"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml205(para)
+msgid ""
+"To include whitespace in a configuration value, use a quoted string. For "
+"example:"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml211(title)
+msgid "Define an alternate location for a config file"
+msgstr ""
+
+#: ./doc/common/section_config_format.xml212(para)
+msgid ""
+"Most services and the and the <placeholder-1/> command-line clients load the"
+" configuration file. To define an alternate location for the configuration "
+"file, pass the <parameter>--config-file "
+"<replaceable>CONFIG_FILE</replaceable></parameter> parameter when you start "
+"a service or call a <placeholder-2/> command."
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml5(title)
+msgid "OpenStack Image Service"
+msgstr "OpenStack Image Service"
+
+#: ./doc/common/section_getstart_image.xml6(para)
+msgid ""
+"The OpenStack Image Service is central to infrastructure-as-a-service (IaaS)"
+" as shown in <xref linkend=\"conceptual-architecture\"/>. It accepts API "
+"requests for disk or server images, and image metadata from end users or "
+"OpenStack Compute components. It also supports the storage of disk or server"
+" images on various repository types, including OpenStack Object Storage."
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml12(para)
+msgid ""
+"A number of periodic processes run on the OpenStack Image Service to support"
+" caching. Replication services ensures consistency and availability through "
+"the cluster. Other periodic processes include auditors, updaters, and "
+"reapers."
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml16(para)
+msgid "The OpenStack Image Service includes the following components:"
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml20(systemitem)
+msgid "glance-api"
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml21(para)
+msgid "Accepts Image API calls for image discovery, retrieval, and storage."
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml25(systemitem)
+msgid "glance-registry"
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml26(para)
+msgid ""
+"Stores, processes, and retrieves metadata about images. Metadata includes "
+"items such as size and type."
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml28(title)
+msgid "Security note"
+msgstr "セキュリティノート"
+
+#: ./doc/common/section_getstart_image.xml29(para)
+msgid ""
+"The registry is a private internal service meant for use by OpenStack Image "
+"Service. Do not disclose it to users."
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml35(term)
+msgid "Database"
+msgstr "データベース"
+
+#: ./doc/common/section_getstart_image.xml36(para)
+msgid ""
+"Stores image metadata and you can choose your database depending on your "
+"preference. Most deployments use MySQL or SQlite."
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml41(term)
+msgid "Storage repository for image files"
+msgstr ""
+
+#: ./doc/common/section_getstart_image.xml42(para)
+msgid ""
+"Various repository types are supported including normal file systems, Object"
+" Storage, RADOS block devices, HTTP, and Amazon S3. Note that some "
+"repositories will only support read-only usage."
+msgstr ""
+
+#: ./doc/common/ch_getstart.xml6(title)
+msgid "Get started with OpenStack"
+msgstr "OpenStack 入門"
+
+#: ./doc/common/ch_getstart.xml7(para)
+msgid ""
+"The OpenStack project is an open source cloud computing platform for all "
+"types of clouds, which aims to be simple to implement, massively scalable, "
+"and feature rich. Developers and cloud computing technologists from around "
+"the world create the OpenStack project."
+msgstr "the OpenStack project はあらゆる種類のクラウド向けのオープンソースのクラウドコンピューティングプラットフォームです。シンプルな実装、大規模なスケーラビリティ、豊富な機能を目指しています。世界中の開発者とクラウドコンピューティング技術者が the OpenStack project を作成します。"
+
+#: ./doc/common/ch_getstart.xml12(para)
+msgid ""
+"OpenStack provides an Infrastructure-as-a-Service "
+"(<glossterm>IaaS</glossterm>) solution through a set of interrelated "
+"services. Each service offers an application programming interface "
+"(<glossterm>API</glossterm>) that facilitates this integration. Depending on"
+" your needs, you can install some or all services."
+msgstr "OpenStack は一組の相互に関係のあるサービスを通して Infrastructure-as-a-Service (<glossterm>IaaS</glossterm>) ソリューションを提供します。各サービスはこの統合を促す application programming interface (<glossterm>API</glossterm>) を提供します。必要に応じて、いくつかのサービス、またはすべてのサービスをインストールできます。"
+
+#: ./doc/common/ch_getstart.xml20(para)
+msgid ""
+"The following table describes the OpenStack services that make up the "
+"OpenStack architecture:"
+msgstr "以下の表は OpenStack アーキテクチャーを構成する OpenStack のサービスについて記載しています。"
+
+#: ./doc/common/ch_getstart.xml23(caption)
+#: ./doc/common/ch_getstart.xml188(title)
+msgid "OpenStack services"
+msgstr "OpenStack  のサービス"
+
+#: ./doc/common/ch_getstart.xml30(th)
+msgid "Project name"
+msgstr "プロジェクト名"
+
+#: ./doc/common/ch_getstart.xml38(glossterm)
+msgid "Dashboard"
+msgstr "Dashboard"
+
+#: ./doc/common/ch_getstart.xml42(glossterm)
+msgid "Horizon"
+msgstr "Horizon"
+
+#: ./doc/common/ch_getstart.xml44(td)
+msgid ""
+"Provides a web-based self-service portal to interact with underlying "
+"OpenStack services, such as launching an instance, assigning IP addresses "
+"and configuring access controls."
+msgstr "インスタンスの起動、IP アドレスの割り当て、アクセス制御の設定など、基礎となる OpenStack サービスを操作するために、ウェブベースのセルフサービスポータルを提供します。"
+
+#: ./doc/common/ch_getstart.xml56(glossterm)
+msgid "Nova"
+msgstr "Nova"
+
+#: ./doc/common/ch_getstart.xml58(td)
+msgid ""
+"Manages the lifecycle of compute instances in an OpenStack environment. "
+"Responsibilities include spawning, scheduling and decommissioning of virtual"
+" machines on demand."
+msgstr "OpenStack 環境でコンピュートインスタンスのライフサイクルを管理します。要求に応じて仮想マシンの作成、スケジューリング、廃棄などに責任を持ちます。"
+
+#: ./doc/common/ch_getstart.xml70(glossterm)
+msgid "Neutron"
+msgstr "Neutron"
+
+#: ./doc/common/ch_getstart.xml72(td)
+msgid ""
+"Enables network connectivity as a service for other OpenStack services, such"
+" as OpenStack Compute. Provides an API for users to define networks and the "
+"attachments into them. Has a pluggable architecture that supports many "
+"popular networking vendors and technologies."
+msgstr "OpenStack Compute のような他の OpenStack サービスに対してサービスとしてのネットワーク接続性を可能にします。ユーザーがネットワークやそれらへの接続を定義するための API を提供します。数多くの人気のあるネットワークベンダーや技術をサポートする、プラグイン可能なアーキテクチャーを持ちます。"
+
+#: ./doc/common/ch_getstart.xml79(th)
+msgid "Storage"
+msgstr "ストレージ"
+
+#: ./doc/common/ch_getstart.xml87(glossterm)
+msgid "Swift"
+msgstr "Swift"
+
+#: ./doc/common/ch_getstart.xml90(glossterm)
+msgid "RESTful"
+msgstr "RESTful"
+
+#: ./doc/common/ch_getstart.xml89(td)
+msgid ""
+"Stores and retrieves arbitrary unstructured data objects via a "
+"<placeholder-1/>, HTTP based API. It is highly fault tolerant with its data "
+"replication and scale out architecture. Its implementation is not like a "
+"file server with mountable directories."
+msgstr "<placeholder-1/>、HTTP ベースの API 経由で任意の非構造データオブジェクトを保存および取得します。そのデータ複製およびスケールアウトアーキテクチャーで高い耐障害性を持ちます。その実装はマウント可能なディレクトリを持つファイルサーバーのようではありません。"
+
+#: ./doc/common/ch_getstart.xml103(glossterm)
+msgid "Cinder"
+msgstr "Cinder"
+
+#: ./doc/common/ch_getstart.xml105(td)
+msgid ""
+"Provides persistent block storage to running instances. Its pluggable driver"
+" architecture facilitates the creation and management of block storage "
+"devices."
+msgstr "実行中のインスタンスに永続的なブロックストレージを提供します。そのプラグイン可能なドライバーアーキテクチャーにより、ブロックストレージデバイスの作成と管理が容易になります。"
+
+#: ./doc/common/ch_getstart.xml110(th)
+msgid "Shared services"
+msgstr "共有サービス"
+
+#: ./doc/common/ch_getstart.xml114(glossterm)
+msgid "Identity service"
+msgstr "Identity"
+
+#: ./doc/common/ch_getstart.xml118(glossterm)
+msgid "Keystone"
+msgstr "Keystone"
+
+#: ./doc/common/ch_getstart.xml120(td)
+msgid ""
+"Provides an authentication and authorization service for other OpenStack "
+"services. Provides a catalog of endpoints for all OpenStack services."
+msgstr "他の OpenStack サービスに対して認証および認可サービスを提供します。すべての OpenStack サービスに対してエンドポイントのカタログを提供します。"
+
+#: ./doc/common/ch_getstart.xml131(glossterm)
+msgid "Glance"
+msgstr "Glance"
+
+#: ./doc/common/ch_getstart.xml133(td)
+msgid ""
+"Stores and retrieves virtual machine disk images. OpenStack Compute makes "
+"use of this during instance provisioning."
+msgstr "仮想マシンディスクイメージを保存および取得します。OpenStack Compute がインスタンスの配備中に使用します。"
+
+#: ./doc/common/ch_getstart.xml146(glossterm)
+msgid "Ceilometer"
+msgstr "Ceilometer"
+
+#: ./doc/common/ch_getstart.xml148(td)
+msgid ""
+"Monitors and meters the OpenStack cloud for billing, benchmarking, "
+"scalability, and statistical purposes."
+msgstr "課金、ベンチマーク、スケーラビリティ、統計などの目的のために、OpenStack クラウドを監視および測定します。"
+
+#: ./doc/common/ch_getstart.xml153(th)
+msgid "Higher-level services"
+msgstr "高レベルサービス"
+
+#: ./doc/common/ch_getstart.xml160(glossterm)
+msgid "Heat"
+msgstr "Heat"
+
+#: ./doc/common/ch_getstart.xml164(glossterm)
+msgid "HOT"
+msgstr "HOT"
+
+#: ./doc/common/ch_getstart.xml162(td)
+msgid ""
+"Orchestrates multiple composite cloud applications by using either the "
+"native <placeholder-1/> template format or the AWS CloudFormation template "
+"format, through both an OpenStack-native REST API and a CloudFormation-"
+"compatible Query API."
+msgstr "OpenStack ネイティブの REST API および CloudFormation 互換のクエリー API 経由で、ネイティブの <placeholder-1/> テンプレート形式または AWS CloudFormation テンプレート形式を使用することにより、複数の混合クラウドアプリケーションを統合します。"
+
+#: ./doc/common/ch_getstart.xml176(glossterm)
+msgid "Trove"
+msgstr "Trove"
+
+#: ./doc/common/ch_getstart.xml178(td)
+msgid ""
+"Provides scalable and reliable Cloud Database-as-a-Service functionality for"
+" both relational and non-relational database engines."
+msgstr "リレーショナルデータベースと非リレーショナルデータベースの両エンジン用にスケール可能かつ信頼できるクラウド Database-as-a-Service を提供します。"
+
+#: ./doc/common/ch_getstart.xml189(para)
+msgid "This section describes OpenStack services in detail."
+msgstr "このセクションは OpenStack のサービスを詳細に記載します。"
+
+#: ./doc/common/ch_getstart.xml207(title)
+msgid "Feedback"
+msgstr "フィードバック"
+
+#: ./doc/common/section_fibrechannel.xml5(title)
+msgid "Fibre Channel support in Compute"
+msgstr ""
+
+#: ./doc/common/section_fibrechannel.xml6(para)
+msgid ""
+"Fibre Channel support in OpenStack Compute is remote block storage attached "
+"to compute nodes for VMs."
+msgstr ""
+
+#. TODO: This below statement needs to be verified for current release
+#: ./doc/common/section_fibrechannel.xml9(para)
+msgid ""
+"In the Grizzly release, Fibre Channel supported only the KVM hypervisor."
+msgstr ""
+
+#: ./doc/common/section_fibrechannel.xml11(para)
+msgid ""
+"Compute and Block Storage for Fibre Channel do not support automatic zoning."
+" Fibre Channel arrays must be pre-zoned or directly attached to the KVM "
+"hosts."
+msgstr ""
+
+#: ./doc/common/section_fibrechannel.xml15(title)
+msgid "KVM host requirements"
+msgstr ""
+
+#: ./doc/common/section_fibrechannel.xml16(para)
+msgid "You must install these packages on the KVM host:"
+msgstr ""
+
+#: ./doc/common/section_fibrechannel.xml19(para)
+msgid ""
+"<package>sysfsutils</package> - Nova uses the <package>systool</package> "
+"application in this package."
+msgstr ""
+
+#: ./doc/common/section_fibrechannel.xml25(para)
+msgid ""
+"<package>sg3-utils</package> - Nova uses the <package>sg_scan</package> and "
+"<package>sginfo</package> applications."
+msgstr ""
+
+#: ./doc/common/section_fibrechannel.xml31(para)
+msgid "Installing the <package>multipath-tools</package> package is optional."
+msgstr ""
+
+#: ./doc/common/section_fibrechannel.xml35(title)
+msgid "Install required packages"
+msgstr ""
+
+#: ./doc/common/section_fibrechannel.xml36(para)
+msgid "Use these commands to install the system packages:"
+msgstr ""
+
+#: ./doc/common/section_fibrechannel.xml40(para)
+msgid "For systems running openSUSE or SUSE Linux Enterprise Server:"
+msgstr ""
+
+#: ./doc/common/section_fibrechannel.xml45(para)
+msgid "For systems running Red Hat:"
+msgstr ""
+
+#: ./doc/common/section_fibrechannel.xml49(para)
+msgid "For systems running Ubuntu:"
+msgstr ""
+
+#: ./doc/common/section_cli_keystone_services.xml7(title)
+msgid "Create and manage services and service users"
+msgstr "サービスとサービスユーザーの作成と管理"
+
+#: ./doc/common/section_cli_keystone_services.xml8(para)
+msgid "The Identity Service enables you to define services, as follows:"
+msgstr "Identity  により、以下のようなサービスを定義できます。"
+
+#: ./doc/common/section_cli_keystone_services.xml12(para)
+msgid ""
+"Service catalog template. The Identity Service acts as a service catalog of "
+"endpoints for other OpenStack services. The "
+"<literal>etc/default_catalog.templates</literal> template file defines the "
+"endpoints for services. When the Identity Service uses a template file back "
+"end, any changes that are made to the endpoints are cached. These changes do"
+" not persist when you restart the service or reboot the machine."
+msgstr "サービスカタログテンプレート。Identity は、他の OpenStack サービスのエンドポイントのサービスカタログとして動作します。<literal>etc/default_catalog.templates</literal> テンプレートファイルは、サービスのエンドポイントを定義します。Identity がテンプレートファイルバックエンドを使用するとき、エンドポイントに対して実行された変更はすべてキャッシュされます。サービスの再起動やマシンの再起動をしたとき、これらの変更は保持されません。"
+
+#: ./doc/common/section_cli_keystone_services.xml23(para)
+msgid ""
+"A SQL back end for the catalog service. When the Identity Service is online,"
+" you must add the services to the catalog. When you deploy a system for "
+"production, use the SQL back end."
+msgstr "カタログサービスの SQL バックエンド。Identity がオンラインのとき、サービスをカタログに追加する必要があります。システムを本番環境に導入するとき、SQL バックエンドを使用します。"
+
+#: ./doc/common/section_cli_keystone_services.xml29(para)
+msgid ""
+"The <literal>auth_token</literal> middleware supports the use of either a "
+"shared secret or users for each service."
+msgstr "<literal>auth_token</literal> ミドルウェアは、共有シークレットの使用、各サービス用のユーザーの使用をサポートします。"
+
+#: ./doc/common/section_cli_keystone_services.xml32(para)
+msgid ""
+"To authenticate users against the Identity Service, you must create a "
+"service user for each OpenStack service. For example, create a service user "
+"for the Compute, Block Storage, and Networking services."
+msgstr "Identity に対してユーザーを認証するために、各 OpenStack サービスのサービスユーザーを作成する必要があります。例えば、Compute、Block Storage、Networking のサービスのサービスユーザーを作成します。"
+
+#: ./doc/common/section_cli_keystone_services.xml36(para)
+msgid ""
+"To configure the OpenStack services with service users, create a project for"
+" all services and create users for each service. Assign the admin role to "
+"each service user and project pair. This role enables users to validate "
+"tokens and authenticate and authorize other user requests."
+msgstr "サービスユーザーを持つ OpenStack サービスを設定するために、すべてのサービスのプロジェクトを作成し、各サービスのユーザーを作成します。各サービスユーザーとプロジェクトのペアに admin ロールを割り当てます。このロールにより、ユーザーがトークンを検証し、他のユーザーのリクエストを認証、認可できます。"
+
+#: ./doc/common/section_cli_keystone_services.xml42(title)
+msgid "Create a service"
+msgstr "サービスの作成"
+
+#: ./doc/common/section_cli_keystone_services.xml45(para)
+msgid "List the available services:"
+msgstr "利用可能なサービスを一覧表示します。"
+
+#: ./doc/common/section_cli_keystone_services.xml59(para)
+msgid "To create a service, run this command:"
+msgstr "サービスを作成するために、このコマンドを実行します。"
+
+#: ./doc/common/section_cli_keystone_services.xml60(replaceable)
+msgid "service_name"
+msgstr "service_name"
+
+#: ./doc/common/section_cli_keystone_services.xml60(replaceable)
+msgid "service_type"
+msgstr "service_type"
+
+#: ./doc/common/section_cli_keystone_services.xml60(replaceable)
+msgid "service_description"
+msgstr "service_description"
+
+#: ./doc/common/section_cli_keystone_services.xml61(para)
+msgid "The arguments are:"
+msgstr "引数は以下のとおりです。"
+
+#: ./doc/common/section_cli_keystone_services.xml64(para)
+msgid ""
+"<code><replaceable>service_name</replaceable></code>. The unique name of the"
+" new service."
+msgstr "<code><replaceable>service_name</replaceable></code>。新しいサービスの一意な名前。"
+
+#: ./doc/common/section_cli_keystone_services.xml68(para)
+msgid ""
+"<code><replaceable>service_type</replaceable></code>. The service type, such"
+" as <code>identity</code>, <code>compute</code>, <code>network</code>, "
+"<code>image</code>, <code>object-store</code> or any other service "
+"identifier string."
+msgstr "<code><replaceable>service_type</replaceable></code>。<code>identity</code>、<code>compute</code>、<code>network</code>、<code>image</code>、<code>object-store</code>、他のサービス識別文字列などのサービス種別。"
+
+#: ./doc/common/section_cli_keystone_services.xml78(para)
+msgid ""
+"<code><replaceable>service_description</replaceable></code>. The description"
+" of the service."
+msgstr "<code><replaceable>service_description</replaceable></code>。サービスの説明。"
+
+#: ./doc/common/section_cli_keystone_services.xml82(para)
+msgid ""
+"For example, to create a <literal>swift</literal> service of type <literal"
+">object-store</literal>, run this command:"
+msgstr "例えば、<literal>object-store</literal> 種別の <literal>swift</literal> サービスを作成するために、このコマンドを実行します。"
+
+#: ./doc/common/section_cli_keystone_services.xml97(para)
+msgid "To get details for a service, run this command:"
+msgstr "サービスの詳細を取得するために、このコマンドを実行します。"
+
+#: ./doc/common/section_cli_keystone_services.xml99(replaceable)
+msgid "service_ID"
+msgstr "service_ID"
+
+#: ./doc/common/section_cli_keystone_services.xml114(title)
+msgid "Create service users"
+msgstr "サービスユーザーの作成"
+
+#: ./doc/common/section_cli_keystone_services.xml117(para)
+msgid ""
+"Create a project for the service users. Typically, this project is named "
+"<literal>service</literal>, but choose any name you like:"
+msgstr "サービスユーザーのプロジェクトを作成します。このプロジェクトは一般的に、<literal>service</literal> という名前ですが、お好きなものを利用できます。"
+
+#: ./doc/common/section_cli_keystone_services.xml122(para)
+msgid "The output shows the ID for the project."
+msgstr "この出力はプロジェクトの ID を表示します。"
+
+#: ./doc/common/section_cli_keystone_services.xml123(para)
+msgid ""
+"Make a note of this ID. You need it to create service users and assign "
+"roles."
+msgstr "この ID を記録します。サービスユーザーの作成とロールの割り当てに必要になります。"
+
+#: ./doc/common/section_cli_keystone_services.xml135(para)
+msgid "Create service users for the relevant services for your deployment."
+msgstr "お使いの環境に関連するサービス用のサービスユーザーを作成します。"
+
+#: ./doc/common/section_cli_keystone_services.xml139(para)
+msgid ""
+"To assign the admin role to the service user-project pairs, run this command"
+" to get the ID of the admin role:"
+msgstr "サービスユーザーとプロジェクトのペアに admin ロールを割り当てるために、admin ロールの ID を取得するために、このコマンドを実行します。"
+
+#: ./doc/common/section_cli_keystone_services.xml155(para)
+msgid "Assign the admin role to the user-project pair:"
+msgstr "ユーザーとプロジェクトのペアに admin ロールを割り当てます。"
+
+#: ./doc/common/section_cli_keystone_services.xml157(replaceable)
+msgid "SERVICE_USER_ID"
+msgstr "SERVICE_USER_ID"
+
+#: ./doc/common/section_cli_keystone_services.xml157(replaceable)
+msgid "ADMIN_ROLE_ID"
+msgstr "ADMIN_ROLE_ID"
+
+#: ./doc/common/section_cli_keystone_services.xml157(replaceable)
+msgid "SERVICE_PROJECT_ID"
+msgstr "SERVICE_PROJECT_ID"
+
+#: ./doc/common/section_cli_keystone_services.xml162(title)
+msgid "Delete a service"
+msgstr "サービスの削除"
+
+#: ./doc/common/section_cli_keystone_services.xml163(para)
+msgid "To delete a specified service, specify its ID:"
+msgstr "指定したサービスを削除するために、その ID を指定します。"
+
+#: ./doc/common/section_cli_keystone_services.xml164(replaceable)
+msgid "SERVICE_ID"
+msgstr "SERVICE_ID"
+
+#: ./doc/common/section_keystone-concepts-domain-management.xml6(title)
+msgid "Domains"
+msgstr "ドメイン"
+
+#: ./doc/common/section_keystone-concepts-domain-management.xml7(para)
+msgid ""
+"A domain defines administrative boundaries for the management of Identity "
+"entities. A domain may represent an individual, company, or operator-owned "
+"space. It is used for exposing administrative activities directly to the "
+"system users."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts-domain-management.xml10(para)
+msgid ""
+"A domain is a collection of tenants, users, and roles. Users may be given a "
+"domain's administrator role. A domain administrator may create tenants, "
+"users, and groups within a domain and assign roles to users and groups."
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml6(title)
+msgid "Customize the dashboard"
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml7(para)
+msgid ""
+"Adapted from <link href=\"http://www.prestonlee.com/2012/05/09/how-to-"
+"custom-brand-the-openstack-horizon-dashboard/\">How To Custom Brand The "
+"OpenStack “Horizon” Dashboard</link>."
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml11(para)
+msgid ""
+"You install the OpenStack dashboard through the <literal>openstack-"
+"dashboard</literal> package. You can customize the dashboard with your own "
+"colors, logo, and site title through a CSS file."
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml15(para)
+msgid ""
+"Canonical also provides an <literal>openstack-dashboard-ubuntu-"
+"theme</literal> package that brands the Python-based Django interface."
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml47(para)
+msgid ""
+"Create a graphical logo with a transparent background. The text "
+"<literal>TGen Cloud</literal> in this example is rendered through "
+"<filename>.png</filename> files of multiple sizes created with a graphics "
+"program."
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml52(para)
+msgid ""
+"Use a 200×27 for the logged-in banner graphic, and 365×50 for the login "
+"screen graphic."
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml56(para)
+msgid ""
+"Set the HTML title, which appears at the top of the browser window, by "
+"adding the following line to <filename>/etc/openstack-"
+"dashboard/local_settings.py</filename>:"
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml59(code)
+msgid "SITE_BRANDING = \"Example, Inc. Cloud\""
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml63(para)
+msgid ""
+"Upload your new graphic files to the following location: "
+"<filename>/usr/share/openstack-"
+"dashboard/openstack_dashboard/static/dashboard/img/</filename>"
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml68(para)
+msgid ""
+"Create a CSS style sheet in the following directory: <filename>/usr/share"
+"/openstack-dashboard/openstack_dashboard/static/dashboard/css/</filename>"
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml72(para)
+msgid ""
+"Edit your CSS file to override the Ubuntu customizations in the "
+"<filename>ubuntu.css</filename> file."
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml75(para)
+msgid ""
+"Change the colors and image file names as appropriate, though the relative "
+"directory paths should be the same. The following example file shows you how"
+" to customize your CSS file:"
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml114(para)
+msgid ""
+"Open the following HTML template in an editor: <filename>/usr/share"
+"/openstack-"
+"dashboard/openstack_dashboard/templates/_stylesheets.html</filename>"
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml118(para)
+msgid "Add a line to include your <filename>custom.css</filename> file:"
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml123(emphasis)
+msgid ""
+"&lt;link href='{{ STATIC_URL }}dashboard/css/custom.css' media='screen' "
+"rel='stylesheet' /&gt;"
+msgstr "&lt;link href='{{ STATIC_URL }}dashboard/css/custom.css' media='screen' rel='stylesheet' /&gt;"
+
+#: ./doc/common/section_dashboard_customizing.xml127(title)
+msgid "Restart Apache:"
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml128(para)
+#: ./doc/common/section_dashboard_sessions.xml180(para)
+msgid "On Ubuntu: <placeholder-1/>"
+msgstr "Ubuntu の場合: <placeholder-1/>"
+
+#: ./doc/common/section_dashboard_customizing.xml131(para)
+msgid "On Fedora, RHEL, CentOS: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml134(para)
+#: ./doc/common/section_dashboard_sessions.xml187(para)
+msgid "On openSUSE: <placeholder-1/>"
+msgstr "openSUSE の場合: <placeholder-1/>"
+
+#: ./doc/common/section_dashboard_customizing.xml139(para)
+msgid "Reload the dashboard in your browser to view your changes."
+msgstr ""
+
+#: ./doc/common/section_dashboard_customizing.xml141(para)
+msgid "Modify your CSS file as appropriate."
 msgstr ""
 
 #: ./doc/common/section_compute_config-api.xml6(title)
@@ -24271,207 +23285,1222 @@ msgid ""
 "linkend=\"config_table_nova_api\"/>."
 msgstr ""
 
-#: ./doc/common/section_getstart_block-storage.xml5(title)
-msgid "OpenStack Block Storage"
-msgstr "OpenStack Block Storage"
+#: ./doc/common/section_cli_nova_fileinjection.xml10(title)
+msgid "Inject files into instances"
+msgstr ""
 
-#: ./doc/common/section_getstart_block-storage.xml6(para)
+#: ./doc/common/section_cli_nova_fileinjection.xml11(para)
 msgid ""
-"OpenStack Block Storage enables management of volumes, volume snapshots, and"
-" volume types. It consists of the following components:"
+"You can inject local files into the instance file system when you launch an "
+"instance."
 msgstr ""
 
-#: ./doc/common/section_getstart_block-storage.xml11(systemitem)
-msgid "cinder-api"
-msgstr ""
-
-#: ./doc/common/section_getstart_block-storage.xml12(para)
+#: ./doc/common/section_cli_nova_fileinjection.xml13(para)
 msgid ""
-"Accepts API requests and routes them to <systemitem class=\"service"
-"\">cinder-volume</systemitem> for action."
+"Use the <parameter>--file dst-path=src-path</parameter> parameter on the "
+"nova <placeholder-1/> command."
 msgstr ""
 
-#: ./doc/common/section_getstart_block-storage.xml17(systemitem)
-msgid "cinder-volume"
+#: ./doc/common/section_cli_nova_fileinjection.xml15(para)
+msgid "You can inject up to five files."
 msgstr ""
 
-#: ./doc/common/section_getstart_block-storage.xml18(para)
+#: ./doc/common/section_cli_nova_fileinjection.xml16(para)
 msgid ""
-"Responds to requests to read from and write to the OpenStack Block Storage "
-"database to maintain state, interacting with other processes (like "
-"<systemitem class=\"service\">cinder-scheduler</systemitem>) through a "
-"message queue and directly upon block storage providing hardware or "
-"software. It can interact with a variety of storage providers through a "
-"driver architecture."
+"For example, you might inject the "
+"<filename>special_authorized_keysfile</filename> file into the instance "
+"rather than using the regular ssh key injection."
 msgstr ""
 
-#: ./doc/common/section_getstart_block-storage.xml28(term)
-msgid "<systemitem class=\"service\">cinder-scheduler</systemitem> daemon"
+#: ./doc/common/section_cli_nova_fileinjection.xml19(para)
+msgid "Run the following command:<placeholder-1/>"
 msgstr ""
 
-#: ./doc/common/section_getstart_block-storage.xml30(para)
+#: ./doc/common/ch_preface.xml7(title)
+msgid "Preface"
+msgstr "はじめに"
+
+#: ./doc/common/section_cli_nova_resizerebuild.xml6(title)
+msgid "Change the size of your server"
+msgstr "サーバーの大きさの変更"
+
+#: ./doc/common/section_cli_nova_resizerebuild.xml7(para)
+msgid "You change the size of a server by changing its flavor."
+msgstr "フレーバーを変更することでサーバーの大きさを変更します。"
+
+#: ./doc/common/section_cli_nova_resizerebuild.xml10(para)
 msgid ""
-"Like the <systemitem class=\"service\">nova-scheduler</systemitem>, picks "
-"the optimal block storage provider node on which to create the volume."
+"Show information about your server, including its size, which is shown as "
+"the value of the flavor property."
 msgstr ""
 
-#: ./doc/common/section_getstart_block-storage.xml36(para)
-msgid "Routes information between the Block Storage processes."
+#: ./doc/common/section_cli_nova_resizerebuild.xml43(para)
+msgid "The size (flavor) of the server is <literal>m1.small (2)</literal>."
 msgstr ""
 
-#: ./doc/common/section_getstart_block-storage.xml40(para)
+#: ./doc/common/section_cli_nova_resizerebuild.xml46(para)
+msgid "List the available flavors with the following command:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_resizerebuild.xml59(para)
 msgid ""
-"OpenStack Block Storage interacts with OpenStack Compute to provide volumes "
-"for instances."
+"To resize the server, pass the server ID or name and the new flavor to the "
+"<placeholder-1/> command. Include the <literal>--poll</literal> parameter to"
+" report the resize progress."
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml5(title)
-msgid "OpenStack Image Service"
-msgstr "OpenStack Image Service"
+#: ./doc/common/section_cli_nova_resizerebuild.xml67(para)
+msgid "Show the status for your server:"
+msgstr "サーバーの状態を表示します。"
 
-#: ./doc/common/section_getstart_image.xml6(para)
+#: ./doc/common/section_cli_nova_resizerebuild.xml74(para)
+msgid "When the resize completes, the status becomes VERIFY_RESIZE."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_resizerebuild.xml77(para)
+msgid "Confirm the resize:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_resizerebuild.xml79(para)
+#: ./doc/common/section_cli_nova_resizerebuild.xml85(para)
+msgid "The server status becomes ACTIVE."
+msgstr "サーバーの状態が ACTIVE に変わります。"
+
+#: ./doc/common/section_cli_nova_resizerebuild.xml82(para)
 msgid ""
-"The OpenStack Image Service is central to infrastructure-as-a-service (IaaS)"
-" as shown in <xref linkend=\"conceptual-architecture\"/>. It accepts API "
-"requests for disk or server images, and image metadata from end users or "
-"OpenStack Compute components. It also supports the storage of disk or server"
-" images on various repository types, including OpenStack Object Storage."
+"If the resize fails or does not work as expected, you can revert the resize:"
+msgstr "リサイズに失敗した場合や予想通りにリサイズが行われなかった場合、リサイズを元に戻すことができます。"
+
+#: ./doc/common/section_dashboard-configure.xml6(title)
+msgid "Configure the dashboard"
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml12(para)
+#: ./doc/common/section_dashboard-configure.xml8(para)
+msgid "You can configure the dashboard for a simple HTTP deployment."
+msgstr ""
+
+#: ./doc/common/section_dashboard-configure.xml14(para)
+msgid "Also, you can configure the size of the VNC window in the dashboard."
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml10(title)
+msgid "Storage concepts"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml11(para)
+msgid "The OpenStack stack uses the following storage types:"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml13(caption)
+msgid "Storage types"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml19(td)
+msgid "On-instance / ephemeral"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml20(td)
+msgid "Block storage (cinder)"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml26(td)
+msgid "Runs operating systems and provides scratch space"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml27(td)
 msgid ""
-"A number of periodic processes run on the OpenStack Image Service to support"
-" caching. Replication services ensures consistency and availability through "
-"the cluster. Other periodic processes include auditors, updaters, and "
-"reapers."
+"Used for adding additional persistent storage to a virtual machine (VM)"
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml16(para)
-msgid "The OpenStack Image Service includes the following components:"
+#: ./doc/common/section_storage-concepts.xml29(td)
+msgid "Used for storing virtual machine images and data"
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml20(systemitem)
-msgid "glance-api"
+#: ./doc/common/section_storage-concepts.xml32(td)
+msgid "Persists until VM is terminated"
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml21(para)
-msgid "Accepts Image API calls for image discovery, retrieval, and storage."
+#: ./doc/common/section_storage-concepts.xml33(td)
+#: ./doc/common/section_storage-concepts.xml34(td)
+msgid "Persists until deleted"
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml25(systemitem)
-msgid "glance-registry"
+#: ./doc/common/section_storage-concepts.xml37(td)
+#: ./doc/common/section_storage-concepts.xml38(td)
+msgid "Access associated with a VM"
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml26(para)
+#: ./doc/common/section_storage-concepts.xml39(td)
+msgid "Available from anywhere"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml42(td)
+msgid "Implemented as a filesystem underlying OpenStack Compute"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml44(td)
 msgid ""
-"Stores, processes, and retrieves metadata about images. Metadata includes "
-"items such as size and type."
+"Mounted via OpenStack Block Storage controlled protocol (for example, iSCSI)"
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml28(title)
-msgid "Security note"
-msgstr "セキュリティノート"
+#: ./doc/common/section_storage-concepts.xml46(td)
+msgid "REST API"
+msgstr "REST API"
 
-#: ./doc/common/section_getstart_image.xml29(para)
+#: ./doc/common/section_storage-concepts.xml49(td)
+msgid "Administrator configures size setting, based on flavors"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml51(td)
+msgid "Sizings based on need"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml52(td)
+msgid "Easily scalable for future growth"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml55(td)
+msgid "Example: 10GB first disk, 30GB/core second disk"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml56(td)
+msgid "Example: 1TB \"extra hard drive\""
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml57(td)
+msgid "Example: 10s of TBs of data set storage"
+msgstr ""
+
+#: ./doc/common/section_storage-concepts.xml64(para)
 msgid ""
-"The registry is a private internal service meant for use by OpenStack Image "
-"Service. Do not disclose it to users."
+"<emphasis>You cannot use OpenStack Object Storage like a traditional hard "
+"drive.</emphasis> The Object Storage relaxes some of the constraints of a "
+"POSIX-style file system to get other gains. You can access the objects "
+"through an API which uses HTTP. Subsequently you don't have to provide "
+"atomic operations (that is, relying on eventual consistency), you can scale "
+"a storage system easily and avoid a central point of failure."
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml35(term)
-msgid "Database"
-msgstr "データベース"
-
-#: ./doc/common/section_getstart_image.xml36(para)
+#: ./doc/common/section_storage-concepts.xml73(para)
 msgid ""
-"Stores image metadata and you can choose your database depending on your "
-"preference. Most deployments use MySQL or SQlite."
+"<emphasis>The OpenStack Image Service is used to manage the virtual machine "
+"images in an OpenStack cluster, not store them.</emphasis> It provides an "
+"abstraction to different methods for storage - a bridge to the storage, not "
+"the storage itself."
 msgstr ""
 
-#: ./doc/common/section_getstart_image.xml41(term)
-msgid "Storage repository for image files"
-msgstr ""
-
-#: ./doc/common/section_getstart_image.xml42(para)
+#: ./doc/common/section_storage-concepts.xml80(para)
 msgid ""
-"Various repository types are supported including normal file systems, Object"
-" Storage, RADOS block devices, HTTP, and Amazon S3. Note that some "
-"repositories will only support read-only usage."
+"<emphasis>The OpenStack Object Storage can function on its own.</emphasis> "
+"The Object Storage (swift) product can be used independently of the Compute "
+"(nova) product."
 msgstr ""
 
+#: ./doc/common/section_storage-concepts.xml62(para)
+msgid "You should note that:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/common/section_rpc-for-networking.xml9(para)
+msgid ""
+"OpenStack projects use an open standard for messaging middleware known as "
+"AMQP. This messaging middleware enables the OpenStack services that run on "
+"multiple servers to talk to each other. OpenStack Oslo RPC supports three "
+"implementations of AMQP: <application>RabbitMQ</application>, "
+"<application>Qpid</application>, and <application>ZeroMQ</application>."
+msgstr ""
+
+#: ./doc/common/section_rpc-for-networking.xml20(para)
+msgid ""
+"OpenStack Oslo RPC uses <application>RabbitMQ</application> by default. Use "
+"these options to configure the <application>RabbitMQ</application> message "
+"system. The <option>rpc_backend</option> option is optional as long as "
+"<application>RabbitMQ</application> is the default messaging system. "
+"However, if it is included the configuration, you must set it to "
+"<literal>neutron.openstack.common.rpc.impl_kombu</literal>."
+msgstr ""
+
+#: ./doc/common/section_rpc-for-networking.xml34(para)
+msgid ""
+"Use these options to configure the <application>RabbitMQ</application> "
+"messaging system. You can configure messaging communication for different "
+"installation scenarios, tune retries for RabbitMQ, and define the size of "
+"the RPC thread pool. To monitor notifications through RabbitMQ, you must set"
+" the <option>notification_driver</option> option to "
+"<literal>neutron.notifier.rabbit_notifier</literal> in the "
+"<filename>neutron.conf</filename> file:"
+msgstr ""
+
+#: ./doc/common/section_rpc-for-networking.xml47(para)
+msgid ""
+"Use these options to configure the <application>Qpid</application> messaging"
+" system for OpenStack Oslo RPC. <application>Qpid</application> is not the "
+"default messaging system, so you must enable it by setting the "
+"<option>rpc_backend</option> option in the <filename>neutron.conf</filename>"
+" file:"
+msgstr ""
+
+#: ./doc/common/section_rpc-for-networking.xml56(para)
+msgid ""
+"This critical option points the compute nodes to the "
+"<application>Qpid</application> broker (server). Set the "
+"<option>qpid_hostname</option> option to the host name where the broker runs"
+" in the <filename>neutron.conf</filename> file."
+msgstr ""
+
+#: ./doc/common/section_rpc-for-networking.xml94(para)
+msgid ""
+"Use these additional options to configure the Qpid messaging driver for "
+"OpenStack Oslo RPC. These options are used infrequently."
+msgstr ""
+
+#: ./doc/common/section_rpc-for-networking.xml103(para)
+msgid ""
+"Use these options to configure the <application>ZeroMQ</application> "
+"messaging system for OpenStack Oslo RPC. <application>ZeroMQ</application> "
+"is not the default messaging system, so you must enable it by setting the "
+"<option>rpc_backend</option> option in the <filename>neutron.conf</filename>"
+" file:"
+msgstr ""
+
+#: ./doc/common/section_rpc-for-networking.xml114(para)
+msgid ""
+"Use these common options to configure the "
+"<application>RabbitMQ</application>, <application>Qpid</application>, and "
+"<application>ZeroMq</application> messaging drivers:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml6(title)
+msgid "Add security group and rules"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml7(para)
+msgid ""
+"The following procedure shows you how to add security groups and add rules "
+"to the default security group."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml10(title)
+msgid "Add or delete a security group"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml11(para)
+msgid "Use the <placeholder-1/> command to add security groups."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml13(para)
+msgid ""
+"The following example shows how to create the <literal>secure1</literal> "
+"security group:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml21(para)
+msgid ""
+"After you create the security group, you can view it in the security group "
+"list:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml30(para)
+msgid ""
+"Use the <placeholder-1/> command to delete security groups. You cannot "
+"delete the default security group. The default security group has these "
+"initial settings:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml36(para)
+msgid ""
+"All the traffic originated by the instances (outbound traffic) is allowed"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml40(para)
+msgid "All the traffic destined to instances (inbound traffic) is denied"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml44(para)
+msgid "All the instances inside the group are allowed to talk to each other"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml49(para)
+msgid ""
+"You can add extra rules into the default security group for handling the "
+"egress traffic. Rules are ingress only at this time."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml53(para)
+msgid ""
+"The following example deletes the <literal>secure1</literal> group. When you"
+" view the security group list, it no longer appears:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml65(title)
+msgid "Modify security group rules"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml69(para)
+msgid "You cannot change the default outbound behavior."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml66(para)
+msgid ""
+"The security group rules control the incoming traffic that can access the "
+"instances in the group, while all outbound traffic is automatically allowed."
+" <placeholder-1/>Every security group rule is a policy that allows you to "
+"specify inbound connections that can access the instance by source address, "
+"destination port, and IP protocol (TCP, UDP or ICMP). Currently, you cannot "
+"manage ipv6 and other protocols through the security rules, making them "
+"permitted by default. To manage such protocols, you can deploy a firewall in"
+" front of your OpenStack cloud to control other types of traffic. The "
+"command requires the following arguments for both TCP and UDP rules:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml84(emphasis)
+#: ./doc/common/section_cli_nova_secgroups.xml124(emphasis)
+#: ./doc/common/section_cli_nova_secgroups.xml209(emphasis)
+msgid "&lt;secgroup&gt;"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml86(para)
+#: ./doc/common/section_cli_nova_secgroups.xml126(para)
+#: ./doc/common/section_cli_nova_secgroups.xml211(para)
+msgid "ID of security group."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml91(emphasis)
+#: ./doc/common/section_cli_nova_secgroups.xml131(emphasis)
+#: ./doc/common/section_cli_nova_secgroups.xml216(emphasis)
+msgid "&lt;ip_proto&gt;"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml98(emphasis)
+#: ./doc/common/section_cli_nova_secgroups.xml223(emphasis)
+msgid "&lt;from_port&gt;"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml105(emphasis)
+#: ./doc/common/section_cli_nova_secgroups.xml230(emphasis)
+msgid "&lt;to_port&gt;"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml112(emphasis)
+#: ./doc/common/section_cli_nova_secgroups.xml152(emphasis)
+#: ./doc/common/section_cli_nova_secgroups.xml237(emphasis)
+msgid "&lt;cidr&gt;"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml118(para)
+msgid ""
+"For ICMP rules, instead of specifying a begin and end port, you specify the "
+"allowed ICMP code and ICMP type:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml133(para)
+msgid "IP protocol (with icmp specified)."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml138(emphasis)
+msgid "&lt;ICMP_code&gt;"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml140(para)
+msgid "The ICMP code."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml145(emphasis)
+msgid "&lt;ICMP_type&gt;"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml147(para)
+msgid "The ICMP type."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml154(para)
+msgid "CIDR for the source address range."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml159(para)
+msgid ""
+"Entering <literal>-1</literal> for both code and type indicates that all "
+"ICMP codes and types are allowed."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml164(title)
+msgid "The CIDR notation"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml165(para)
+msgid ""
+"That notation allows you to specify a base IP address and a suffix that "
+"designates the number of significant bits in the IP address used to identify"
+" the network. For example, by specifying a "
+"<literal>88.170.60.32/27</literal>, you specify "
+"<literal>88.170.60.32</literal> as the <emphasis role=\"bold\">base "
+"IP</emphasis> and <literal>27</literal> as the <emphasis "
+"role=\"bold\">suffix</emphasis>. Because you use an IPV4 format, only 5 bits"
+" are available for the host part (32 minus 27). The "
+"<literal>0.0.0.0/0</literal> notation means you allow the entire IPV4 range,"
+" which allows all addresses."
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml179(para)
+msgid ""
+"For example, to allow any IP address to access a web server running on one "
+"of your instances inside the default security group:"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml188(para)
+msgid ""
+"To allow any IP address to ping an instance inside the default security "
+"group (Code 0, Type 8 for the ECHO request):"
+msgstr ""
+
+#: ./doc/common/section_cli_nova_secgroups.xml204(para)
+msgid ""
+"To delete a rule, you must specify exactly the same arguments that you used "
+"to create it:"
+msgstr ""
+
+#: ./doc/common/section_cli_version.xml6(title)
+msgid "Discover the version number for a client"
+msgstr "クライアントのバージョン番号の確認"
+
+#: ./doc/common/section_cli_version.xml7(para)
+msgid "Run the following command to discover the version number for a client:"
+msgstr "クライアントのバージョン番号を確認するために、以下のコマンドを実行します。"
+
+#: ./doc/common/section_cli_version.xml10(para)
+msgid ""
+"For example, to see the version number for the <placeholder-1/> client, run "
+"the following command:"
+msgstr "例えば、<placeholder-1/> クライアントのバージョン番号を取得するために、以下のコマンドを実行します。"
+
+#: ./doc/common/section_cli_version.xml14(para)
+msgid "The version number (2.15.0 in the example) is returned."
+msgstr "バージョン番号 (この例は 2.15.0) が返されます。"
+
+#: ./doc/common/section_xen-install.xml6(title)
+msgid "Install XenServer and XCP"
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml8(para)
+msgid ""
+"Before you can run OpenStack with XCP or XenServer, you must install the "
+"software on <link "
+"href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/installation.html#sys_requirements\">an"
+" appropriate server</link>."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml13(para)
+msgid ""
+"Xen is a type 1 hypervisor: When your server starts, Xen is the first "
+"software that runs. Consequently, you must install XenServer or XCP before "
+"you install the operating system where you want to run OpenStack code. The "
+"OpenStack services then run in a virtual machine that you install on top of "
+"XenServer."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml20(para)
+msgid ""
+"Before you can install your system, decide whether to install a free or paid"
+" edition of Citrix XenServer or Xen Cloud Platform from Xen.org. Download "
+"the software from these locations:"
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml28(link)
+msgid "http://www.citrix.com/XenServer/download"
+msgstr "http://www.citrix.com/XenServer/download"
+
+#: ./doc/common/section_xen-install.xml33(link)
+msgid "http://www.xen.org/download/xcp/index.html"
+msgstr "http://www.xen.org/download/xcp/index.html"
+
+#: ./doc/common/section_xen-install.xml36(para)
+msgid ""
+"When you install many servers, you might find it easier to perform <link "
+"href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/installation.html#pxe_boot_install\">PXE"
+" boot installations of XenServer or XCP</link>. You can also package any "
+"post-installation changes that you want to make to your XenServer by <link "
+"href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/supplemental_pack_ddk.html\">creating"
+" your own XenServer supplemental pack</link>."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml46(para)
+msgid ""
+"You can also install the <package>xcp-xenapi</package> package on Debian-"
+"based distributions to get XCP. However, this is not as mature or feature "
+"complete as above distributions. This modifies your boot loader to first "
+"boot Xen and boot your existing OS on top of Xen as Dom0. The xapi daemon "
+"runs in Dom0. Find more details at <link "
+"href=\"http://wiki.xen.org/wiki/Project_Kronos\">http://wiki.xen.org/wiki/Project_Kronos</link>."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml55(para)
+msgid ""
+"Make sure you use the EXT type of storage repository (SR). Features that "
+"require access to VHD files (such as copy on write, snapshot and migration) "
+"do not work when you use the LVM SR. Storage repository (SR) is a XenAPI-"
+"specific term relating to the physical storage where virtual disks are "
+"stored."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml61(para)
+msgid ""
+"On the XenServer/XCP installation screen, choose the <guilabel>XenDesktop "
+"Optimized</guilabel> option. If you use an answer file, make sure you use "
+"<literal>srtype=\"ext\"</literal> in the <option>installation</option> tag "
+"of the answer file."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml69(title)
+msgid "Post-installation steps"
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml70(para)
+msgid "Complete these steps to install OpenStack in your XenServer system:"
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml74(para)
+msgid ""
+"For resize and migrate functionality, complete the changes described in the "
+"<citetitle>Configure resize</citetitle> section in the <link href"
+"=\"../config-reference/content/index.html\"><citetitle>OpenStack "
+"Configuration Reference</citetitle></link>."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml82(para)
+msgid ""
+"Install the VIF isolation rules to help prevent mac and IP address spoofing."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml86(para)
+msgid "Install the XenAPI plug-ins. See the following section."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml90(para)
+msgid ""
+"To support AMI type images, you must set up <literal>/boot/guest</literal> "
+"symlink/directory in Dom0. For detailed instructions, see next section."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml96(para)
+msgid ""
+"To support resize/migration, set up an ssh trust relation between your "
+"XenServer hosts, and ensure <literal>/images</literal> is properly set up. "
+"See next section for more details."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml102(para)
+msgid ""
+"Create a Paravirtualized virtual machine that can run the OpenStack compute "
+"code."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml106(para)
+msgid ""
+"Install and configure the <systemitem class=\"service\">nova-"
+"compute</systemitem> in the above virtual machine."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml111(para)
+msgid ""
+"For more information, see how DevStack performs the last three steps for "
+"developer deployments. For more information about DevStack, see "
+"<citetitle>Getting Started With XenServer and Devstack</citetitle> (<link "
+"href=\"https://github.com/openstack-"
+"dev/devstack/blob/master/tools/xen/README.md\">https://github.com/openstack-"
+"dev/devstack/blob/master/tools/xen/README.md</link>). Find more information "
+"about the first step, see <citetitle>Multi Tenancy Networking Protections in"
+" XenServer</citetitle> (<link "
+"href=\"https://github.com/openstack/nova/blob/master/plugins/xenserver/doc/networking.rst\">https://github.com/openstack/nova/blob/master/plugins/xenserver/doc/networking.rst</link>)."
+" For information about how to install the XenAPI plug-ins, see "
+"<citetitle>XenAPI README</citetitle> (<link "
+"href=\"https://github.com/openstack/nova/blob/master/plugins/xenserver/xenapi/README\">https://github.com/openstack/nova/blob/master/plugins/xenserver/xenapi/README</link>)."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml131(title)
+msgid "Xen boot from ISO"
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml132(para)
+msgid ""
+"XenServer, through the XenAPI integration with OpenStack, provides a feature"
+" to boot instances from an ISO file. To activate the Boot From ISO feature, "
+"you must configure the SR elements on XenServer host, as follows:"
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml139(para)
+msgid ""
+"Create an ISO-typed SR, such as an NFS ISO library, for instance. For this, "
+"using XenCenter is a simple method. You must export an NFS volume from a "
+"remote NFS server. Make sure it is exported in read-write mode."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml146(para)
+msgid "On the compute host, find and record the uuid of this ISO SR:"
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml151(para)
+msgid "Locate the uuid of the NFS ISO library:"
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml155(para)
+msgid ""
+"Set the uuid and configuration. Even if an NFS mount point is not local, you"
+" must specify <literal>local-storage-iso</literal>."
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml161(para)
+msgid ""
+"Make sure the host-uuid from <literal>xe pbd-list</literal> equals the uuid "
+"of the host you found previously:"
+msgstr ""
+
+#: ./doc/common/section_xen-install.xml167(para)
+msgid ""
+"You can now add images through the OpenStack Image Service with <literal"
+">disk-format=iso</literal>, and boot them in OpenStack Compute:"
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml7(title)
+msgid "Install the XenAPI plug-ins"
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml8(para)
+msgid ""
+"When you use Xen as the hypervisor for OpenStack Compute, you can install a "
+"Python script (or any executable) on the host side, and call that through "
+"the XenAPI. These scripts are called plug-ins. The XenAPI plug-ins live in "
+"the nova code repository. These plug-ins have to be copied to the Dom0 for "
+"the hypervisor, to the appropriate directory, where xapi can find them. "
+"There are several options for the installation. The important thing is to "
+"ensure that the version of the plug-ins are in line with the nova "
+"installation by only installing plug-ins from a matching nova repository."
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml19(title)
+msgid "Manually install the plug-in"
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml22(para)
+msgid "Create temporary files/directories:"
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml27(para)
+msgid ""
+"Get the source from github. The example assumes the master branch is used. "
+"Amend the URL to match the version being used:"
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml32(para)
+msgid ""
+"(Alternatively) To use the official Ubuntu packages, use the following "
+"commands to get the nova code base:"
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml39(para)
+msgid "Copy the plug-ins to the hypervisor:"
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml44(para)
+msgid "Remove the temporary files/directories:"
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml51(title)
+msgid "Package a XenServer supplemental pack"
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml52(para)
+msgid ""
+"Follow these steps to produce a supplemental pack from the nova sources, and"
+" package it as a XenServer supplemental pack."
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml57(para)
+msgid ""
+"Create RPM packages. Given you have the nova sources. Use one of the methods"
+" in <xref linkend=\"manual_install\"/>:"
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml62(para)
+msgid ""
+"These commands leave an <filename>.rpm</filename> file in the "
+"<filename>rpmbuild/RPMS/noarch/</filename> directory."
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml68(para)
+msgid ""
+"Pack the RPM packages to a Supplemental Pack, using the XenServer DDK (the "
+"following command should be issued on the XenServer DDK virtual appliance, "
+"after the produced rpm file has been copied over):"
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml81(para)
+msgid ""
+"This command produces an <filename>.iso</filename> file in the output "
+"directory specified. Copy that file to the hypervisor."
+msgstr ""
+
+#: ./doc/common/section_xapi-install-plugins.xml87(para)
+msgid "Install the Supplemental Pack. Log in to the hypervisor, and issue:"
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml5(title)
+msgid "Orchestration module"
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml6(para)
+msgid ""
+"The Orchestration module provides a template-based orchestration for "
+"describing a cloud application, by running OpenStack API calls to generate "
+"running cloud applications. The software integrates other core components of"
+" OpenStack into a one-file template system. The templates allow you to "
+"create most OpenStack resource types, such as instances, floating IPs, "
+"volumes, security groups and users. It also provides advanced functionality,"
+" such as instance high availability, instance auto-scaling, and nested "
+"stacks. This enables OpenStack core projects to receive a larger user base."
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml16(para)
+msgid ""
+"The service enables deployers to integrate with the Orchestration module "
+"directly or through custom plug-ins."
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml18(para)
+msgid "The Orchestration module consists of the following components:"
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml22(term)
+msgid "<code>heat</code> command-line client"
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml23(para)
+msgid ""
+"A CLI that communicates with the heat-api to run AWS CloudFormation APIs. "
+"End developers can directly use the Orchestration REST API."
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml28(term)
+msgid "<code>heat-api</code> component"
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml28(para)
+msgid ""
+"An OpenStack-native REST API that processes API requests by sending them to "
+"the heat-engine over Remote Procedure Call (RPC)."
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml34(term)
+msgid "<code>heat-api-cfn</code> component"
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml34(para)
+msgid ""
+"An AWS Query API that is compatible with AWS CloudFormation. It processes "
+"API requests by sending them to the heat-engine over RPC."
+msgstr ""
+
+#: ./doc/common/section_getstart_orchestration.xml40(code)
+msgid "heat-engine"
+msgstr "heat-engine"
+
+#: ./doc/common/section_getstart_orchestration.xml41(para)
+msgid ""
+"Orchestrates the launching of templates and provides events back to the API "
+"consumer."
+msgstr ""
+
+#: ./doc/common/ch_using_openstack_overview.xml7(title)
+msgid ""
+"How can I <phrase audience=\"enduser\">use</phrase><phrase "
+"audience=\"adminuser\">administer</phrase> an OpenStack cloud?"
+msgstr "どのように OpenStack クラウドを<phrase audience=\"enduser\">利用</phrase><phrase audience=\"adminuser\">管理</phrase>できますか?"
+
+#: ./doc/common/ch_using_openstack_overview.xml11(para)
+msgid ""
+"As an OpenStack cloud end user, you can provision your own resources within "
+"the limits set by administrators."
+msgstr "OpenStack クラウドのエンドユーザーとして、管理者により設定された制限の範囲内で自身のリソースを配備できます。"
+
+#: ./doc/common/ch_using_openstack_overview.xml14(para)
+msgid ""
+"As an OpenStack cloud administrative user, you can manage tenants, known as "
+"<glossterm baseform=\"project\">projects</glossterm>, users, services, "
+"images, flavors, and quotas."
+msgstr "OpenStack クラウドの管理ユーザーとして、<glossterm baseform=\"project\">プロジェクト</glossterm>として知られているテナント、ユーザー、サービス、イメージ、フレーバー、クォータを管理できます。"
+
+#: ./doc/common/ch_using_openstack_overview.xml18(para)
+msgid ""
+"The examples in this guide show you how to perform tasks by using the "
+"following methods:"
+msgstr "このガイドの例は、以下の方法により、作業を実行する方法を示します。"
+
+#: ./doc/common/ch_using_openstack_overview.xml22(para)
+msgid ""
+"OpenStack dashboard. Use this web-based graphical interface, code named "
+"<link href=\"https://github.com/openstack/horizon/\">horizon</link>, to "
+"view, create, and manage resources<phrase audience=\"adminuser\"> and "
+"services</phrase>."
+msgstr "OpenStack Dashboard。リソース<phrase audience=\"adminuser\"> およびサービス</phrase>を表示、作成、管理するために、このウェブのグラフィカルインターフェース (コード名 <link href=\"https://github.com/openstack/horizon/\">Horizon</link>) を使用します。"
+
+#: ./doc/common/ch_using_openstack_overview.xml30(para)
+msgid ""
+"OpenStack command-line clients. Each core OpenStack project has a command-"
+"line client that you can use to run simple commands to view, create, and "
+"manage resources<phrase audience=\"adminuser\"> and services</phrase> in a "
+"cloud and automate tasks by using scripts."
+msgstr "OpenStack コマンドラインクライアント。各 OpenStack コアプロジェクトは、クラウドでリソース<phrase audience=\"adminuser\"> およびサービス</phrase>を表示、作成、管理するために、シンプルなコマンドを実行するために使用でき、スクリプトを使用して作業を自動化できるコマンドラインクライアントを持ちます。"
+
+#: ./doc/common/ch_using_openstack_overview.xml38(para)
+msgid "You can modify these examples for your specific use cases."
+msgstr "お使いの具体的なユースケースのために、これらの例を変更できます。"
+
+#: ./doc/common/ch_using_openstack_overview.xml40(para)
+msgid ""
+"In addition to these ways of interacting with a cloud, you can access the "
+"OpenStack APIs directly or indirectly through <link "
+"href=\"http://curl.haxx.se/\">cURL</link> commands or open SDKs. You can "
+"automate access or build tools to manage resources and services by using the"
+" native OpenStack APIs or the EC2 compatibility API."
+msgstr "クラウドと相互に作用するこれらの方法に加えて、<link href=\"http://curl.haxx.se/\">cURL</link> コマンドまたはオープン SDK 経由で直接的または間接的に OpenStack API にアクセスできます。ネイティブの OpenStack API や EC2 互換 API を使用することにより、リソースやサービスを管理するために、アクセスを自動化したり、ツールを作成したりできます。"
+
+#: ./doc/common/ch_using_openstack_overview.xml46(para)
+msgid ""
+"To use the OpenStack APIs, it helps to be familiar with HTTP/1.1, RESTful "
+"web services, the OpenStack services, and JSON or XML data serialization "
+"formats."
+msgstr "OpenStack API を使用するために、HTTP/1.1、RESTful ウェブサービス、OpenStack サービス、および JSON や XML データシリアライズ形式に慣れることは役に立ちます。"
+
 #. When image changes, this message will be marked fuzzy or untranslated for
 #. you.
 #. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/common/section_objectstorage-characteristics.xml49(None)
+#: ./doc/common/section_keystone-concepts.xml120(None)
+#: ./doc/common/section_keystone-concepts.xml125(None)
 msgid ""
-"@@image: '../common/figures/objectstorage.png'; "
-"md5=e26e374ace84070f5fed24e73adcd562"
-msgstr "@@image: '../common/figures/objectstorage.png'; md5=e26e374ace84070f5fed24e73adcd562"
+"@@image: 'figures/SCH_5002_V00_NUAC-Keystone.png'; "
+"md5=734714c50c99fc1d74bdfd9f9cd049a6"
+msgstr "@@image: 'figures/SCH_5002_V00_NUAC-Keystone.png'; md5=734714c50c99fc1d74bdfd9f9cd049a6"
 
-#: ./doc/common/section_objectstorage-characteristics.xml7(title)
-msgid "Object Storage characteristics"
+#: ./doc/common/section_keystone-concepts.xml7(title)
+msgid "OpenStack Identity concepts"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-characteristics.xml8(para)
-msgid "The key characteristics of Object Storage are that:"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-characteristics.xml11(para)
-msgid "All objects stored in Object Storage have a URL."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-characteristics.xml14(para)
+#: ./doc/common/section_keystone-concepts.xml8(para)
 msgid ""
-"All objects stored are replicated 3✕ in as-unique-as-possible zones, which "
-"can be defined as a group of drives, a node, a rack, and so on."
+"The OpenStack<glossterm>Identity Service</glossterm> performs the following "
+"functions:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-characteristics.xml18(para)
-msgid "All objects have their own metadata."
+#: ./doc/common/section_keystone-concepts.xml12(para)
+msgid "Tracking users and their permissions."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-characteristics.xml21(para)
+#: ./doc/common/section_keystone-concepts.xml15(para)
+msgid "Providing a catalog of available services with their API endpoints."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts.xml19(para)
 msgid ""
-"Developers interact with the object storage system through a RESTful HTTP "
-"API."
+"To understand OpenStack Identity, you must understand the following "
+"concepts:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-characteristics.xml25(para)
-msgid "Object data can be located anywhere in the cluster."
-msgstr ""
+#: ./doc/common/section_keystone-concepts.xml23(term)
+msgid "User"
+msgstr "ユーザー"
 
-#: ./doc/common/section_objectstorage-characteristics.xml28(para)
+#: ./doc/common/section_keystone-concepts.xml25(para)
 msgid ""
-"The cluster scales by adding additional nodes without sacrificing "
-"performance, which allows a more cost-effective linear storage expansion "
-"than fork-lift upgrades."
+"Digital representation of a person, system, or service who uses OpenStack "
+"cloud services. The Identity service validates that incoming requests are "
+"made by the user who claims to be making the call. Users have a login and "
+"may be assigned tokens to access resources. Users can be directly assigned "
+"to a particular tenant and behave as if they are contained in that tenant."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-characteristics.xml33(para)
-msgid "Data doesn't have to be migrate to an entirely new storage system."
-msgstr ""
+#: ./doc/common/section_keystone-concepts.xml36(term)
+msgid "Credentials"
+msgstr "クレデンシャル"
 
-#: ./doc/common/section_objectstorage-characteristics.xml36(para)
-msgid "New nodes can be added to the cluster without downtime."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-characteristics.xml39(para)
-msgid "Failed nodes and disks can be swapped out without downtime."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-characteristics.xml42(para)
+#: ./doc/common/section_keystone-concepts.xml38(para)
 msgid ""
-"It runs on industry-standard hardware, such as Dell, HP, and Supermicro."
+"Data that confirms the user's identity. For example, user name and password;"
+" user name and API key; or an authentication token provided by the Identity "
+"Service."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-characteristics.xml53(para)
+#: ./doc/common/section_keystone-concepts.xml45(term)
+msgid "Authentication"
+msgstr "認証"
+
+#: ./doc/common/section_keystone-concepts.xml47(para)
 msgid ""
-"Developers can either write directly to the Swift API or use one of the many"
-" client libraries that exist for all of the popular programming languages, "
-"such as Java, Python, Ruby, and C#. Amazon S3 and RackSpace Cloud Files "
-"users should be very familiar with Object Storage. Users new to object "
-"storage systems will have to adjust to a different approach and mindset than"
-" those required for a traditional filesystem."
+"The process of confirming the identity of a user. OpenStack Identity "
+"confirms an incoming request by validating a set of credentials supplied by "
+"the user."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts.xml51(para)
+msgid ""
+"These credentials are initially a user name and password; or a user name and"
+" API key. When user credentials are validated, OpenStack Identity issues an "
+"authentication token which the user provides in subsequent requests."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts.xml59(term)
+msgid "Token"
+msgstr "トークン"
+
+#: ./doc/common/section_keystone-concepts.xml61(para)
+msgid ""
+"An arbitrary bit of text that is used to access resources. Each token has "
+"information which defines access to resources. A token may be revoked at any"
+" time and is valid for a finite duration."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts.xml65(para)
+msgid ""
+"While OpenStack Identity supports token-based authentication in this "
+"release, the intention is to support additional protocols in the future. Its"
+" main purpose is to be an integration service, and not aspire to be a full-"
+"fledged identity store and management solution."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts.xml74(term)
+msgid "Tenant"
+msgstr "テナント"
+
+#: ./doc/common/section_keystone-concepts.xml76(para)
+msgid ""
+"A container used to group or isolate resources and/or identity objects. "
+"Depending on the service operator, a tenant may map to a customer, account, "
+"organization, or project."
+msgstr "リソース、主体オブジェクト、またはその組み合わせをグループ化、または分離するために使用されるコンテナー。サービス操作者に依存して、テナントが顧客、アカウント、組織、プロジェクトに対応付けられるかもしれません。"
+
+#: ./doc/common/section_keystone-concepts.xml85(para)
+msgid ""
+"An OpenStack service, such as Compute (nova), Object Storage (swift), or "
+"Image Service (glance). It provides one or more endpoints through which "
+"users can access resources and perform operations."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts.xml92(term)
+msgid "Endpoint"
+msgstr "エンドポイント"
+
+#: ./doc/common/section_keystone-concepts.xml94(para)
+msgid ""
+"A network-accessible address where you access a service, usually a URL "
+"address. If you are using an extension for templates, an endpoint template "
+"can be created, which represents the templates of all the consumable "
+"services that are available across the regions."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts.xml102(term)
+msgid "Role"
+msgstr "役割"
+
+#: ./doc/common/section_keystone-concepts.xml104(para)
+msgid ""
+"A personality with a defined set of user rights and privileges to perform a "
+"specific set of operations."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts.xml106(para)
+msgid ""
+"In the Identity service, a token that is issued to a user includes the list "
+"of roles. Services that are being called by that user determine how they "
+"interpret the set of roles a user has and to which operations or resources "
+"each role grants access."
+msgstr ""
+
+#: ./doc/common/section_keystone-concepts.xml114(para)
+msgid "The following diagram shows the OpenStack Identity process flow:"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml7(title)
+msgid "Features and benefits"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml12(th)
+msgid "Features"
+msgstr "特徴"
+
+#: ./doc/common/section_objectstorage-features.xml13(th)
+msgid "Benefits"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml18(emphasis)
+msgid "Leverages commodity hardware"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml19(td)
+msgid "No lock-in, lower price/GB."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml22(emphasis)
+msgid "HDD/node failure agnostic"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml23(td)
+msgid "Self-healing, reliable, data redundancy protects from failures."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml27(emphasis)
+msgid "Unlimited storage"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml28(td)
+msgid ""
+"Large and flat namespace, highly scalable read/write access, able to serve "
+"content directly from storage system."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml32(emphasis)
+msgid "Multi-dimensional scalability"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml34(td)
+msgid ""
+"Scale-out architecture: Scale vertically and horizontally-distributed "
+"storage. Backs up and archives large amounts of data with linear "
+"performance."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml39(emphasis)
+msgid "Account/container/object structure"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml40(td)
+msgid ""
+"No nesting, not a traditional file system: Optimized for scale, it scales to"
+" multiple petabytes and billions of objects."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml45(emphasis)
+msgid "Built-in replication 3✕ + data redundancy (compared with 2✕ on RAID)"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml48(td)
+msgid ""
+"A configurable number of accounts, containers and object copies for high "
+"availability."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml52(emphasis)
+msgid "Easily add capacity (unlike RAID resize)"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml54(td)
+msgid "Elastic data scaling with ease"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml57(emphasis)
+msgid "No central database"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml58(td)
+msgid "Higher performance, no bottlenecks"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml61(emphasis)
+msgid "RAID not required"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml62(td)
+msgid "Handle many small, random reads and writes efficiently"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml65(emphasis)
+msgid "Built-in management utilities"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml66(td)
+msgid ""
+"Account management: Create, add, verify, and delete users; Container "
+"management: Upload, download, and verify; Monitoring: Capacity, host, "
+"network, log trawling, and cluster health."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml72(emphasis)
+msgid "Drive auditing"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml73(td)
+msgid "Detect drive failures preempting data corruption"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml76(emphasis)
+msgid "Expiring objects"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml77(td)
+msgid ""
+"Users can set an expiration time or a TTL on an object to control access"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml81(emphasis)
+msgid "Direct object access"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml82(td)
+msgid "Enable direct browser access to content, such as for a control panel"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml86(emphasis)
+msgid "Realtime visibility into client requests"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml88(td)
+msgid "Know what users are requesting."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml91(emphasis)
+msgid "Supports S3 API"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml92(td)
+msgid "Utilize tools that were designed for the popular S3 API."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml96(emphasis)
+msgid "Restrict containers per account"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml98(td)
+msgid "Limit access to control usage by user."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml101(emphasis)
+msgid "Support for NetApp, Nexenta, SolidFire"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml103(td)
+msgid "Unified support for block volumes using a variety of storage systems."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml107(emphasis)
+msgid "Snapshot and backup API for block volumes"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml109(td)
+msgid "Data protection and recovery for VM data."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml112(emphasis)
+msgid "Standalone volume API available"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml114(td)
+msgid "Separate endpoint and API for integration with other compute systems."
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml118(emphasis)
+msgid "Integration with Compute"
+msgstr ""
+
+#: ./doc/common/section_objectstorage-features.xml120(td)
+msgid ""
+"Fully integrated with Compute for attaching block volumes and reporting on "
+"usage."
 msgstr ""
 
 #: ./doc/common/section_dashboard_sessions.xml6(title)
@@ -24736,837 +24765,4510 @@ msgid ""
 "cookie-based-sessions\">cookie-based sessions</link> documentation."
 msgstr "Django <link href=\"https://docs.djangoproject.com/en/dev/topics/http/sessions/#using-cookie-based-sessions\">cookie-based sessions</link> ドキュメントを参照してください。"
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml6(title)
-msgid "Troubleshoot Object Storage"
+#: ./doc/common/section_kvm_enable.xml6(title)
+msgid "Enable KVM"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml7(para)
+#: ./doc/common/section_kvm_enable.xml7(para)
 msgid ""
-"For Object Storage, everything is logged in "
-"<filename>/var/log/syslog</filename> (or messages on some distros). Several "
-"settings enable further customization of logging, such as "
-"<literal>log_name</literal>, <literal>log_facility</literal>, and "
-"<literal>log_level</literal>, within the object server configuration files."
+"To perform these steps, you must be logged in as the "
+"<systemitem>root</systemitem> user."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml11(title)
-msgid "Drive failure"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-troubleshoot.xml12(para)
+#: ./doc/common/section_kvm_enable.xml11(para)
 msgid ""
-"In the event that a drive has failed, the first step is to make sure the "
-"drive is unmounted. This will make it easier for Object Storage to work "
-"around the failure until it has been resolved. If the drive is going to be "
-"replaced immediately, then it is just best to replace the drive, format it, "
-"remount it, and let replication fill it up."
+"To determine whether the <literal>svm</literal> or <literal>vmx</literal> "
+"CPU extensions are present, run this command:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml16(para)
+#: ./doc/common/section_kvm_enable.xml15(para)
 msgid ""
-"If the drive can’t be replaced immediately, then it is best to leave it "
-"unmounted, and remove the drive from the ring. This will allow all the "
-"replicas that were on that drive to be replicated elsewhere until the drive "
-"is replaced. Once the drive is replaced, it can be re-added to the ring."
+"This command generates output if the CPU is hardware-virtualization capable."
+" Even if output is shown, you might still need to enable virtualization in "
+"the system BIOS for full support."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml20(para)
+#: ./doc/common/section_kvm_enable.xml19(para)
 msgid ""
-"You can look at error messages in <filename>/var/log/kern.log</filename> for"
-" hints of drive failure."
+"If no output appears, consult your system documentation to ensure that your "
+"CPU and motherboard support hardware virtualization. Verify that any "
+"relevant hardware virtualization options are enabled in the system BIOS."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml23(title)
-msgid "Server failure"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-troubleshoot.xml24(para)
+#: ./doc/common/section_kvm_enable.xml24(para)
 msgid ""
-"If a server is having hardware issues, it is a good idea to make sure the "
-"Object Storage services are not running. This will allow Object Storage to "
-"work around the failure while you troubleshoot."
+"The BIOS for each manufacturer is different. If you must enable "
+"virtualization in the BIOS, look for an option containing the words "
+"<literal>virtualization</literal>, <literal>VT</literal>, "
+"<literal>VMX</literal>, or <literal>SVM</literal>."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml27(para)
+#: ./doc/common/section_kvm_enable.xml32(para)
 msgid ""
-"If the server just needs a reboot, or a small amount of work that should "
-"only last a couple of hours, then it is probably best to let Object Storage "
-"work around the failure and get the machine fixed and back online. When the "
-"machine comes back online, replication will make sure that anything that is "
-"missing during the downtime will get updated."
+"To list the loaded kernel modules and verify that the <literal>kvm</literal>"
+" modules are loaded, run this command:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml32(para)
+#: ./doc/common/section_kvm_enable.xml36(para)
 msgid ""
-"If the server has more serious issues, then it is probably best to remove "
-"all of the server’s devices from the ring. Once the server has been repaired"
-" and is back online, the server’s devices can be added back into the ring. "
-"It is important that the devices are reformatted before putting them back "
-"into the ring as it is likely to be responsible for a different set of "
-"partitions than before."
+"If the output includes <systemitem>kvm_intel</systemitem> or "
+"<systemitem>kvm_amd</systemitem>, the <systemitem>kvm</systemitem> hardware "
+"virtualization modules are loaded and your kernel meets the module "
+"requirements for OpenStack Compute."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml40(title)
-msgid "Detect failed drives"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-troubleshoot.xml41(para)
+#: ./doc/common/section_kvm_enable.xml43(para)
 msgid ""
-"It has been our experience that when a drive is about to fail, error "
-"messages will spew into /var/log/kern.log. There is a script called swift-"
-"drive-audit that can be run via cron to watch for bad drives. If errors are "
-"detected, it will unmount the bad drive, so that Object Storage can work "
-"around it. The script takes a configuration file with the following "
-"settings:"
+"If the output does not show that the <literal>kvm</literal> module is "
+"loaded, run this command to load it:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml47(para)
+#: ./doc/common/section_kvm_enable.xml47(para)
+msgid "Run the command for your CPU. For Intel, run this command:"
+msgstr ""
+
+#: ./doc/common/section_kvm_enable.xml50(para)
+msgid "For AMD, run this command:"
+msgstr ""
+
+#: ./doc/common/section_kvm_enable.xml52(para)
 msgid ""
-"This script has only been tested on Ubuntu 10.04, so if you are using a "
-"different distro or OS, some care should be taken before using in "
-"production."
+"Because a KVM installation can change user group membership, you might need "
+"to log in again for changes to take effect."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml52(title)
-msgid "Emergency recovery of ring builder files"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-troubleshoot.xml53(para)
+#: ./doc/common/section_kvm_enable.xml55(para)
 msgid ""
-"You should always keep a backup of swift ring builder files. However, if an "
-"emergency occurs, this procedure may assist in returning your cluster to an "
-"operational state."
+"If the kernel modules do not load automatically, use the procedures listed "
+"in these subsections."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml56(para)
+#: ./doc/common/section_kvm_enable.xml59(para)
 msgid ""
-"Using existing swift tools, there is no way to recover a builder file from a"
-" <filename>ring.gz</filename> file. However, if you have a knowledge of "
-"Python, it is possible to construct a builder file that is pretty close to "
-"the one you have lost. The following is what you will need to do."
+"If the checks indicate that required hardware virtualization support or "
+"kernel modules are disabled or unavailable, you must either enable this "
+"support on the system or find a system with this support."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml61(para)
+#: ./doc/common/section_kvm_enable.xml64(para)
 msgid ""
-"This procedure is a last-resort for emergency circumstances. It requires "
-"knowledge of the swift python code and may not succeed."
+"Some systems require that you enable VT support in the system BIOS. If you "
+"believe your processor supports hardware acceleration but the previous "
+"command did not produce output, reboot your machine, enter the system BIOS, "
+"and enable the VT option."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml64(para)
-msgid "First, load the ring and a new ringbuilder object in a Python REPL:"
-msgstr ""
-
-#: ./doc/common/section_objectstorage-troubleshoot.xml67(para)
-msgid "Now, start copying the data we have in the ring into the builder."
-msgstr ""
-
-#: ./doc/common/section_objectstorage-troubleshoot.xml84(para)
+#: ./doc/common/section_kvm_enable.xml70(para)
 msgid ""
-"This is the extent of the recoverable fields. For "
-"<literal>min_part_hours</literal> you'll either have to remember what the "
-"value you used was, or just make up a new one."
+"If KVM acceleration is not supported, configure Compute to use a different "
+"hypervisor, such as <link href=\"http://docs.openstack.org/trunk/config-"
+"reference/content/qemu.html\">QEMU</link> or <link "
+"href=\"http://docs.openstack.org/trunk/config-reference/content"
+"/introduction-to-xen.html\">Xen</link>."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml89(para)
+#: ./doc/common/section_kvm_enable.xml76(para)
 msgid ""
-"Try some validation: if this doesn't raise an exception, you may feel some "
-"hope. Not too much, though."
+"These procedures help you load the kernel modules for Intel-based and AMD-"
+"based processors if they do not load automatically during KVM installation."
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml92(para)
-msgid "Save the builder."
-msgstr ""
+#: ./doc/common/section_kvm_enable.xml80(title)
+msgid "Intel-based processors"
+msgstr "Intel 系プロセッサー"
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml96(para)
+#: ./doc/common/section_kvm_enable.xml81(para)
 msgid ""
-"You should now have a file called 'account.builder' in the current working "
-"directory. Next, run <literal>swift-ring-builder account.builder "
-"write_ring</literal> and compare the new account.ring.gz to the "
-"account.ring.gz that you started from. They probably won't be byte-for-byte "
-"identical, but if you load them up in a REPL and their "
-"<literal>_replica2part2dev_id</literal> and <literal>devs</literal> "
-"attributes are the same (or nearly so), then you're in good shape."
+"If your compute host is Intel-based, run these commands as root to load the "
+"kernel modules:"
 msgstr ""
 
-#: ./doc/common/section_objectstorage-troubleshoot.xml103(para)
+#: ./doc/common/section_kvm_enable.xml85(para)
 msgid ""
-"Next, repeat the procedure for <filename>container.ring.gz</filename> and "
-"<filename>object.ring.gz</filename>, and you might get usable builder files."
+"Add these lines to the <filename>/etc/modules</filename> file so that these "
+"modules load on reboot:"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml8(caption)
-#: ./doc/common/tables/ceilometer-cells.xml8(caption)
-msgid "Description of configuration options for cells"
+#: ./doc/common/section_kvm_enable.xml91(title)
+msgid "AMD-based processors"
+msgstr "AMD 系プロセッサー"
+
+#: ./doc/common/section_kvm_enable.xml92(para)
+msgid ""
+"If your compute host is AMD-based, run these commands as root to load the "
+"kernel modules:"
+msgstr ""
+
+#: ./doc/common/section_kvm_enable.xml96(para)
+msgid ""
+"Add these lines to <filename>/etc/modules</filename> file so that these "
+"modules load on reboot:"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-database.xml8(caption)
+#: ./doc/common/tables/cinder-database.xml8(caption)
+#: ./doc/common/tables/trove-database.xml8(caption)
+#: ./doc/common/tables/heat-database.xml8(caption)
+#: ./doc/common/tables/keystone-database.xml8(caption)
+msgid "Description of configuration options for database"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml13(th)
-#: ./doc/common/tables/trove-db_mongodb.xml13(th)
-#: ./doc/common/tables/keystone-debug.xml13(th)
-#: ./doc/common/tables/glance-policy.xml13(th)
-#: ./doc/common/tables/neutron-mlnx.xml13(th)
-#: ./doc/common/tables/nova-ipv6.xml13(th)
-#: ./doc/common/tables/cinder-eqlx.xml13(th)
-#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml12(th)
-#: ./doc/common/tables/swift-object-expirer-filter-cache.xml12(th)
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml12(th)
-#: ./doc/common/tables/nova-rpc_all.xml13(th)
-#: ./doc/common/tables/neutron-ml2_l2pop.xml13(th)
-#: ./doc/common/tables/glance-qpid.xml13(th)
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml12(th)
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml13(th)
-#: ./doc/common/tables/neutron-ml2_gre.xml13(th)
-#: ./doc/common/tables/nova-volumes.xml13(th)
-#: ./doc/common/tables/glance-gridfs.xml13(th)
-#: ./doc/common/tables/neutron-ml2_arista.xml13(th)
-#: ./doc/common/tables/glance-filesystem.xml13(th)
-#: ./doc/common/tables/heat-redis.xml13(th)
-#: ./doc/common/tables/trove-logging.xml13(th)
-#: ./doc/common/tables/swift-container-server-container-updater.xml12(th)
-#: ./doc/common/tables/cinder-storage_gpfs.xml13(th)
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml13(th)
-#: ./doc/common/tables/nova-tilera.xml13(th)
-#: ./doc/common/tables/nova-ca.xml13(th)
-#: ./doc/common/tables/heat-clients_nova.xml13(th)
-#: ./doc/common/tables/swift-account-server-filter-recon.xml12(th)
-#: ./doc/common/tables/cinder-huawei.xml13(th)
-#: ./doc/common/tables/keystone-qpid.xml13(th)
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml13(th)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml12(th)
-#: ./doc/common/tables/nova-glance.xml13(th)
-#: ./doc/common/tables/neutron-dhcp_agent.xml13(th)
-#: ./doc/common/tables/nova-neutron.xml13(th)
-#: ./doc/common/tables/cinder-backups_ceph.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml12(th)
-#: ./doc/common/tables/nova-metadata.xml13(th)
-#: ./doc/common/tables/glance-s3.xml13(th)
-#: ./doc/common/tables/glance-auth_token.xml13(th)
-#: ./doc/common/tables/neutron-kombu.xml13(th)
-#: ./doc/common/tables/trove-redis.xml13(th)
-#: ./doc/common/tables/trove-qpid.xml13(th)
-#: ./doc/common/tables/trove-compute.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml12(th)
-#: ./doc/common/tables/trove-nova.xml13(th)
-#: ./doc/common/tables/ceilometer-cells.xml13(th)
-#: ./doc/common/tables/keystone-oauth.xml13(th)
-#: ./doc/common/tables/cinder-block-device.xml13(th)
-#: ./doc/common/tables/cinder-zones.xml13(th)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml13(th)
-#: ./doc/common/tables/swift-container-server-container-sync.xml12(th)
-#: ./doc/common/tables/neutron-common.xml13(th)
-#: ./doc/common/tables/neutron-compute.xml13(th)
-#: ./doc/common/tables/swift-object-server-object-auditor.xml12(th)
-#: ./doc/common/tables/keystone-ldap.xml13(th)
-#: ./doc/common/tables/heat-rpc.xml13(th)
-#: ./doc/common/tables/neutron-openvswitch_agent.xml13(th)
-#: ./doc/common/tables/cinder-compute.xml13(th)
-#: ./doc/common/tables/keystone-identity.xml13(th)
-#: ./doc/common/tables/cinder-lvm.xml13(th)
-#: ./doc/common/tables/keystone-trust.xml13(th)
-#: ./doc/common/tables/cinder-storage_nfs.xml13(th)
-#: ./doc/common/tables/neutron-plumgrid.xml13(th)
-#: ./doc/common/tables/heat-cfn_api.xml13(th)
-#: ./doc/common/tables/nova-hypervisor.xml13(th)
-#: ./doc/common/tables/trove-rabbitmq.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml12(th)
-#: ./doc/common/tables/trove-api.xml13(th)
-#: ./doc/common/tables/cinder-quota.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml12(th)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml12(th)
-#: ./doc/common/tables/nova-console.xml13(th)
-#: ./doc/common/tables/ceilometer-events.xml13(th)
-#: ./doc/common/tables/keystone-os_inherit.xml13(th)
-#: ./doc/common/tables/heat-clients.xml13(th)
-#: ./doc/common/tables/heat-notification.xml13(th)
-#: ./doc/common/tables/keystone-assignment.xml13(th)
-#: ./doc/common/tables/nova-common.xml13(th)
-#: ./doc/common/tables/swift-object-server-object-updater.xml12(th)
-#: ./doc/common/tables/glance-zmq.xml13(th)
-#: ./doc/common/tables/neutron-metering_agent.xml13(th)
-#: ./doc/common/tables/trove-taskmanager.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml12(th)
-#: ./doc/common/tables/keystone-zeromq.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml12(th)
-#: ./doc/common/tables/nova-keymgr.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml12(th)
-#: ./doc/common/tables/neutron-api.xml13(th)
-#: ./doc/common/tables/ceilometer-redis.xml13(th)
-#: ./doc/common/tables/ceilometer-swift.xml13(th)
-#: ./doc/common/tables/cinder-hplefthand.xml13(th)
-#: ./doc/common/tables/heat-qpid.xml13(th)
-#: ./doc/common/tables/nova-testing.xml13(th)
-#: ./doc/common/tables/cinder-backups.xml13(th)
-#: ./doc/common/tables/swift-container-server-pipeline-main.xml12(th)
-#: ./doc/common/tables/neutron-ml2_ofa.xml13(th)
-#: ./doc/common/tables/trove-debug.xml13(th)
-#: ./doc/common/tables/swift-rsyncd-object.xml12(th)
-#: ./doc/common/tables/nova-s3.xml13(th)
-#: ./doc/common/tables/nova-zookeeper.xml13(th)
-#: ./doc/common/tables/cinder-rpc.xml13(th)
-#: ./doc/common/tables/cinder-api.xml13(th)
-#: ./doc/common/tables/cinder-windows.xml13(th)
-#: ./doc/common/tables/glance-vmware.xml13(th)
-#: ./doc/common/tables/swift-object-server-pipeline-main.xml12(th)
-#: ./doc/common/tables/trove-backup.xml13(th)
-#: ./doc/common/tables/nova-auth_token.xml13(th)
-#: ./doc/common/tables/cinder-san.xml13(th)
-#: ./doc/common/tables/swift-account-server-app-account-server.xml12(th)
-#: ./doc/common/tables/keystone-rpc.xml13(th)
-#: ./doc/common/tables/cinder-keymgr.xml13(th)
-#: ./doc/common/tables/nova-db.xml13(th)
-#: ./doc/common/tables/neutron-ml2_vxlan.xml13(th)
-#: ./doc/common/tables/glance-logging.xml13(th)
-#: ./doc/common/tables/cinder-zoning.xml13(th)
-#: ./doc/common/tables/glance-wsgi.xml13(th)
-#: ./doc/common/tables/nova-periodic.xml13(th)
-#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml12(th)
-#: ./doc/common/tables/cinder-images.xml13(th)
-#: ./doc/common/tables/trove-swift.xml13(th)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml12(th)
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml12(th)
-#: ./doc/common/tables/cinder-auth_token.xml13(th)
-#: ./doc/common/tables/heat-crypt.xml13(th)
-#: ./doc/common/tables/neutron-wsgi.xml13(th)
-#: ./doc/common/tables/neutron-scheduler.xml13(th)
-#: ./doc/common/tables/keystone-security.xml13(th)
-#: ./doc/common/tables/ceilometer-vmware.xml13(th)
-#: ./doc/common/tables/glance-rbd.xml13(th)
-#: ./doc/common/tables/heat-clients_heat.xml13(th)
-#: ./doc/common/tables/heat-rabbitmq.xml13(th)
-#: ./doc/common/tables/ceilometer-logging.xml13(th)
-#: ./doc/common/tables/neutron-metadata.xml13(th)
-#: ./doc/common/tables/glance-redis.xml13(th)
-#: ./doc/common/tables/keystone-stats.xml13(th)
-#: ./doc/common/tables/cinder-hp3par.xml13(th)
-#: ./doc/common/tables/cinder-storage_ceph.xml13(th)
-#: ./doc/common/tables/nova-livemigration.xml13(th)
-#: ./doc/common/tables/nova-ldap.xml13(th)
-#: ./doc/common/tables/nova-fping.xml13(th)
-#: ./doc/common/tables/heat-clients_swift.xml13(th)
-#: ./doc/common/tables/neutron-securitygroups.xml13(th)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml13(th)
-#: ./doc/common/tables/nova-ec2.xml13(th)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml12(th)
-#: ./doc/common/tables/trove-zeromq.xml13(th)
-#: ./doc/common/tables/heat-database.xml13(th)
-#: ./doc/common/tables/keystone-catalog.xml13(th)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml12(th)
-#: ./doc/common/tables/cinder-rootwrap.xml13(th)
 #: ./doc/common/tables/ceilometer-database.xml13(th)
-#: ./doc/common/tables/heat-debug.xml13(th)
-#: ./doc/common/tables/cinder-nexenta_nfs.xml13(th)
-#: ./doc/common/tables/trove-auth_token.xml13(th)
-#: ./doc/common/tables/heat-waitcondition_api.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml12(th)
-#: ./doc/common/tables/neutron-ml2_vlan.xml13(th)
-#: ./doc/common/tables/nova-policy.xml13(th)
-#: ./doc/common/tables/keystone-amqp.xml13(th)
-#: ./doc/common/tables/neutron-logging.xml13(th)
-#: ./doc/common/tables/trove-db_cassandra.xml13(th)
+#: ./doc/common/tables/neutron-openvswitch_agent.xml13(th)
+#: ./doc/common/tables/heat-clients.xml13(th)
+#: ./doc/common/tables/cinder-solidfire.xml13(th)
+#: ./doc/common/tables/neutron-rpc.xml13(th)
+#: ./doc/common/tables/trove-db_percona.xml13(th)
+#: ./doc/common/tables/nova-periodic.xml13(th)
+#: ./doc/common/tables/keystone-auth.xml13(th)
+#: ./doc/common/tables/keystone-policy.xml13(th)
+#: ./doc/common/tables/glance-auth_token.xml13(th)
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml13(th)
+#: ./doc/common/tables/swift-container-server-container-sync.xml12(th)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml12(th)
+#: ./doc/common/tables/cinder-zoning_fabric.xml13(th)
+#: ./doc/common/tables/ceilometer-redis.xml13(th)
+#: ./doc/common/tables/cinder-storage_ceph.xml13(th)
+#: ./doc/common/tables/ceilometer-vmware.xml13(th)
+#: ./doc/common/tables/neutron-cisco.xml13(th)
+#: ./doc/common/tables/nova-testing.xml13(th)
+#: ./doc/common/tables/nova-metadata.xml13(th)
+#: ./doc/common/tables/heat-clients_nova.xml13(th)
+#: ./doc/common/tables/cinder-hp3par.xml13(th)
+#: ./doc/common/tables/keystone-misc.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml12(th)
+#: ./doc/common/tables/neutron-scheduler.xml13(th)
+#: ./doc/common/tables/glance-rbd.xml13(th)
+#: ./doc/common/tables/cinder-storage_xen.xml13(th)
+#: ./doc/common/tables/ceilometer-common.xml13(th)
+#: ./doc/common/tables/cinder-database.xml13(th)
+#: ./doc/common/tables/ceilometer-logging.xml13(th)
+#: ./doc/common/tables/heat-common.xml13(th)
+#: ./doc/common/tables/nova-ipv6.xml13(th)
+#: ./doc/common/tables/nova-vnc.xml13(th)
+#: ./doc/common/tables/trove-qpid.xml13(th)
+#: ./doc/common/tables/keystone-api.xml13(th)
+#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml12(th)
+#: ./doc/common/tables/swift-container-server-container-auditor.xml12(th)
 #: ./doc/common/tables/glance-rpc.xml13(th)
-#: ./doc/common/tables/nova-authentication.xml13(th)
+#: ./doc/common/tables/neutron-policy.xml13(th)
+#: ./doc/common/tables/nova-spice.xml13(th)
+#: ./doc/common/tables/heat-clients_heat.xml13(th)
+#: ./doc/common/tables/nova-xen.xml13(th)
+#: ./doc/common/tables/trove-amqp.xml13(th)
+#: ./doc/common/tables/glance-matchmaker.xml13(th)
+#: ./doc/common/tables/nova-rabbitmq.xml13(th)
+#: ./doc/common/tables/neutron-ml2_cisco.xml13(th)
+#: ./doc/common/tables/nova-policy.xml13(th)
+#: ./doc/common/tables/keystone-identity.xml13(th)
+#: ./doc/common/tables/ceilometer-inspector.xml13(th)
+#: ./doc/common/tables/cinder-scheduler.xml13(th)
+#: ./doc/common/tables/trove-db_cassandra.xml13(th)
+#: ./doc/common/tables/neutron-logging.xml13(th)
+#: ./doc/common/tables/nova-availabilityzones.xml13(th)
+#: ./doc/common/tables/keystone-catalog.xml13(th)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml13(th)
+#: ./doc/common/tables/neutron-rootwrap.xml13(th)
+#: ./doc/common/tables/cinder-auth.xml13(th)
+#: ./doc/common/tables/swift-swift-swift-constraints.xml12(th)
+#: ./doc/common/tables/heat-qpid.xml13(th)
+#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml12(th)
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml12(th)
+#: ./doc/common/tables/nova-zookeeper.xml13(th)
+#: ./doc/common/tables/nova-keymgr.xml13(th)
+#: ./doc/common/tables/neutron-auth_token.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml12(th)
+#: ./doc/common/tables/nova-ldap.xml13(th)
+#: ./doc/common/tables/swift-container-server-filter-recon.xml12(th)
+#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml12(th)
+#: ./doc/common/tables/ceilometer-auth.xml13(th)
+#: ./doc/common/tables/cinder-quota.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml12(th)
+#: ./doc/common/tables/keystone-os_inherit.xml13(th)
+#: ./doc/common/tables/neutron-sdnve.xml13(th)
+#: ./doc/common/tables/nova-compute.xml13(th)
+#: ./doc/common/tables/keystone-rabbit.xml13(th)
+#: ./doc/common/tables/cinder-backups_ceph.xml13(th)
+#: ./doc/common/tables/nova-vmware.xml13(th)
+#: ./doc/common/tables/heat-cfn_api.xml13(th)
+#: ./doc/common/tables/neutron-vmware.xml13(th)
+#: ./doc/common/tables/nova-rdp.xml13(th)
+#: ./doc/common/tables/keystone-assignment.xml13(th)
+#: ./doc/common/tables/nova-zeromq.xml13(th)
+#: ./doc/common/tables/cinder-storage.xml13(th)
+#: ./doc/common/tables/glance-registry.xml13(th)
+#: ./doc/common/tables/neutron-embrane.xml13(th)
+#: ./doc/common/tables/heat-quota.xml13(th)
+#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml12(th)
+#: ./doc/common/tables/nova-common.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml12(th)
+#: ./doc/common/tables/nova-volumes.xml13(th)
+#: ./doc/common/tables/neutron-redis.xml13(th)
+#: ./doc/common/tables/trove-db_mysql.xml13(th)
+#: ./doc/common/tables/heat-zeromq.xml13(th)
+#: ./doc/common/tables/heat-amqp.xml13(th)
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml13(th)
+#: ./doc/common/tables/nova-redis.xml13(th)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml12(th)
+#: ./doc/common/tables/nova-db.xml13(th)
+#: ./doc/common/tables/glance-rabbitmq.xml13(th)
+#: ./doc/common/tables/neutron-l3_agent.xml13(th)
+#: ./doc/common/tables/swift-container-server-pipeline-main.xml12(th)
+#: ./doc/common/tables/glance-policy.xml13(th)
+#: ./doc/common/tables/nova-neutron.xml13(th)
+#: ./doc/common/tables/cinder-backups.xml13(th)
+#: ./doc/common/tables/cinder-keymgr.xml13(th)
+#: ./doc/common/tables/ceilometer-cells.xml13(th)
+#: ./doc/common/tables/keystone-ldap.xml13(th)
+#: ./doc/common/tables/glance-vmware.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml12(th)
+#: ./doc/common/tables/cinder-zoning.xml13(th)
+#: ./doc/common/tables/heat-notification.xml13(th)
+#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml12(th)
+#: ./doc/common/tables/nova-vpn.xml13(th)
+#: ./doc/common/tables/neutron-vpn.xml13(th)
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml12(th)
+#: ./doc/common/tables/trove-common.xml13(th)
+#: ./doc/common/tables/trove-api.xml13(th)
+#: ./doc/common/tables/cinder-zadara.xml13(th)
+#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml12(th)
+#: ./doc/common/tables/nova-conductor.xml13(th)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml12(th)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml12(th)
+#: ./doc/common/tables/nova-livemigration.xml13(th)
+#: ./doc/common/tables/heat-rabbitmq.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml12(th)
+#: ./doc/common/tables/neutron-cadf.xml13(th)
+#: ./doc/common/tables/keystone-amqp.xml13(th)
+#: ./doc/common/tables/keystone-rpc.xml13(th)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml12(th)
+#: ./doc/common/tables/cinder-zones.xml13(th)
+#: ./doc/common/tables/cinder-scality.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml12(th)
+#: ./doc/common/tables/neutron-agent.xml13(th)
+#: ./doc/common/tables/cinder-emc.xml13(th)
 #: ./doc/common/tables/cinder-vmware.xml13(th)
-#: ./doc/common/tables/glance-sheepdog.xml13(th)
-#: ./doc/common/tables/heat-logging.xml13(th)
-#: ./doc/common/tables/keystone-notification.xml13(th)
-#: ./doc/common/tables/neutron-qpid.xml13(th)
-#: ./doc/common/tables/neutron-hyperv_agent.xml13(th)
+#: ./doc/common/tables/neutron-ml2_flat.xml13(th)
+#: ./doc/common/tables/heat-metadata_api.xml13(th)
+#: ./doc/common/tables/trove-rabbitmq.xml13(th)
+#: ./doc/common/tables/nova-upgrade_levels.xml13(th)
+#: ./doc/common/tables/neutron-kombu.xml13(th)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml13(th)
+#: ./doc/common/tables/neutron-ml2_ofa.xml13(th)
+#: ./doc/common/tables/glance-api.xml13(th)
+#: ./doc/common/tables/heat-waitcondition_api.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml12(th)
+#: ./doc/common/tables/swift-rsyncd-container.xml12(th)
+#: ./doc/common/tables/cinder-storwize.xml13(th)
+#: ./doc/common/tables/cinder-hplefthand.xml13(th)
+#: ./doc/common/tables/glance-s3.xml13(th)
+#: ./doc/common/tables/nova-rootwrap.xml13(th)
+#: ./doc/common/tables/heat-loadbalancer.xml13(th)
+#: ./doc/common/tables/ceilometer-api.xml13(th)
+#: ./doc/common/tables/ceilometer-exchange.xml13(th)
+#: ./doc/common/tables/cinder-lvm.xml13(th)
+#: ./doc/common/tables/trove-dns.xml13(th)
+#: ./doc/common/tables/nova-cells.xml13(th)
+#: ./doc/common/tables/trove-volume.xml13(th)
+#: ./doc/common/tables/heat-auth_token.xml13(th)
+#: ./doc/common/tables/neutron-quotas.xml13(th)
+#: ./doc/common/tables/nova-auth_token.xml13(th)
+#: ./doc/common/tables/cinder-storage_nfs.xml13(th)
+#: ./doc/common/tables/heat-api.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml12(th)
+#: ./doc/common/tables/heat-clients_ceilometer.xml13(th)
+#: ./doc/common/tables/neutron-ryu.xml13(th)
+#: ./doc/common/tables/glance-logging.xml13(th)
+#: ./doc/common/tables/swift-rsyncd-account.xml12(th)
+#: ./doc/common/tables/neutron-metering_agent.xml13(th)
+#: ./doc/common/tables/neutron-zeromq.xml13(th)
+#: ./doc/common/tables/cinder-storage_glusterfs.xml13(th)
+#: ./doc/common/tables/cinder-common.xml13(th)
 #: ./doc/common/tables/glance-swift.xml13(th)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml12(th)
+#: ./doc/common/tables/trove-quota.xml13(th)
+#: ./doc/common/tables/cinder-auth_token.xml13(th)
+#: ./doc/common/tables/ceilometer-alarm.xml13(th)
+#: ./doc/common/tables/ceilometer-events.xml13(th)
+#: ./doc/common/tables/cinder-xiv.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml12(th)
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml13(th)
+#: ./doc/common/tables/nova-glance.xml13(th)
+#: ./doc/common/tables/keystone-auth_token.xml13(th)
+#: ./doc/common/tables/nova-s3.xml13(th)
+#: ./doc/common/tables/nova-pci.xml13(th)
+#: ./doc/common/tables/swift-account-server-filter-recon.xml12(th)
+#: ./doc/common/tables/heat-clients_cinder.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml12(th)
+#: ./doc/common/tables/keystone-revoke.xml13(th)
+#: ./doc/common/tables/cinder-api.xml13(th)
+#: ./doc/common/tables/trove-db_couchbase.xml13(th)
+#: ./doc/common/tables/heat-clients_trove.xml13(th)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml12(th)
+#: ./doc/common/tables/neutron-plumgrid.xml13(th)
+#: ./doc/common/tables/trove-heat.xml13(th)
+#: ./doc/common/tables/glance-sheepdog.xml13(th)
+#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml12(th)
+#: ./doc/common/tables/cinder-windows.xml13(th)
+#: ./doc/common/tables/cinder-san-solaris.xml13(th)
+#: ./doc/common/tables/neutron-nuage.xml13(th)
+#: ./doc/common/tables/keystone-zeromq.xml13(th)
 #: ./doc/common/tables/neutron-bigswitch.xml13(th)
-#: ./doc/common/tables/nova-libvirt.xml13(th)
+#: ./doc/common/tables/ceilometer-rpc.xml13(th)
+#: ./doc/common/tables/swift-container-server-container-updater.xml12(th)
+#: ./doc/common/tables/trove-db_mongodb.xml13(th)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml12(th)
+#: ./doc/common/tables/glance-filesystem.xml13(th)
+#: ./doc/common/tables/trove-rpc.xml13(th)
+#: ./doc/common/tables/ceilometer-swift.xml13(th)
+#: ./doc/common/tables/trove-backup.xml13(th)
+#: ./doc/common/tables/nova-network.xml13(th)
+#: ./doc/common/tables/glance-redis.xml13(th)
+#: ./doc/common/tables/keystone-ssl.xml13(th)
+#: ./doc/common/tables/nova-ca.xml13(th)
+#: ./doc/common/tables/neutron-dhcp_agent.xml13(th)
+#: ./doc/common/tables/ceilometer-collector.xml13(th)
+#: ./doc/common/tables/cinder-hds-hus.xml13(th)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml13(th)
+#: ./doc/common/tables/swift-swift-swift-hash.xml12(th)
+#: ./doc/common/tables/neutron-ml2_gre.xml13(th)
+#: ./doc/common/tables/neutron-varmour.xml13(th)
+#: ./doc/common/tables/heat-debug.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml12(th)
+#: ./doc/common/tables/nova-kombu.xml13(th)
+#: ./doc/common/tables/trove-guestagent.xml13(th)
+#: ./doc/common/tables/nova-qpid.xml13(th)
+#: ./doc/common/tables/glance-qpid.xml13(th)
+#: ./doc/common/tables/neutron-ml2_l2pop.xml13(th)
+#: ./doc/common/tables/glance-amqp.xml13(th)
+#: ./doc/common/tables/glance-zmq.xml13(th)
+#: ./doc/common/tables/neutron-embrane_lb.xml13(th)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml12(th)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml12(th)
+#: ./doc/common/tables/neutron-testing.xml13(th)
+#: ./doc/common/tables/swift-object-server-pipeline-main.xml12(th)
+#: ./doc/common/tables/swift-memcache-memcache.xml12(th)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml12(th)
+#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml12(th)
+#: ./doc/common/tables/trove-compute.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml12(th)
+#: ./doc/common/tables/swift-object-expirer-filter-cache.xml12(th)
+#: ./doc/common/tables/trove-db_redis.xml13(th)
+#: ./doc/common/tables/cinder-rpc.xml13(th)
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml12(th)
+#: ./doc/common/tables/cinder-hpmsa.xml13(th)
+#: ./doc/common/tables/nova-apiv3.xml13(th)
+#: ./doc/common/tables/keystone-oauth.xml13(th)
+#: ./doc/common/tables/cinder-storage_gpfs.xml13(th)
+#: ./doc/common/tables/neutron-ml2_vlan.xml13(th)
+#: ./doc/common/tables/keystone-notification.xml13(th)
+#: ./doc/common/tables/swift-object-server-object-auditor.xml12(th)
+#: ./doc/common/tables/trove-zeromq.xml13(th)
 #: ./doc/common/tables/neutron-lbaas.xml13(th)
 #: ./doc/common/tables/cinder-backups_swift.xml13(th)
-#: ./doc/common/tables/neutron-ml2_cisco.xml13(th)
-#: ./doc/common/tables/ceilometer-rpc.xml13(th)
-#: ./doc/common/tables/heat-loadbalancer.xml13(th)
-#: ./doc/common/tables/heat-cloudwatch_api.xml13(th)
-#: ./doc/common/tables/nova-pci.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml12(th)
-#: ./doc/common/tables/heat-clients_ceilometer.xml13(th)
-#: ./doc/common/tables/neutron-varmour.xml13(th)
-#: ./doc/common/tables/glance-imagecache.xml13(th)
-#: ./doc/common/tables/trove-quota.xml13(th)
-#: ./doc/common/tables/swift-rsyncd-account.xml12(th)
-#: ./doc/common/tables/cinder-storage.xml13(th)
-#: ./doc/common/tables/cinder-nas.xml13(th)
-#: ./doc/common/tables/nova-vpn.xml13(th)
-#: ./doc/common/tables/nova-wsgi.xml13(th)
-#: ./doc/common/tables/cinder-storage_glusterfs.xml13(th)
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml12(th)
-#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml12(th)
-#: ./doc/common/tables/nova-availabilityzones.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml12(th)
-#: ./doc/common/tables/heat-zeromq.xml13(th)
-#: ./doc/common/tables/keystone-memcache.xml13(th)
-#: ./doc/common/tables/nova-vnc.xml13(th)
-#: ./doc/common/tables/swift-swift-swift-constraints.xml12(th)
-#: ./doc/common/tables/neutron-cisco.xml13(th)
-#: ./doc/common/tables/keystone-logging.xml13(th)
-#: ./doc/common/tables/nova-hyperv.xml13(th)
-#: ./doc/common/tables/neutron-l3_agent.xml13(th)
-#: ./doc/common/tables/swift-object-server-filter-recon.xml12(th)
-#: ./doc/common/tables/cinder-coraid.xml13(th)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml12(th)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml12(th)
-#: ./doc/common/tables/nova-vmware.xml13(th)
-#: ./doc/common/tables/nova-logging.xml13(th)
-#: ./doc/common/tables/nova-xen.xml13(th)
-#: ./doc/common/tables/ceilometer-collector.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml12(th)
-#: ./doc/common/tables/keystone-ec2.xml13(th)
-#: ./doc/common/tables/keystone-auth.xml13(th)
-#: ./doc/common/tables/swift-memcache-memcache.xml12(th)
-#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml12(th)
-#: ./doc/common/tables/neutron-ml2.xml13(th)
-#: ./doc/common/tables/ceilometer-api.xml13(th)
-#: ./doc/common/tables/heat-clients_trove.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml12(th)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml13(th)
-#: ./doc/common/tables/glance-common.xml13(th)
-#: ./doc/common/tables/nova-network.xml13(th)
-#: ./doc/common/tables/cinder-scality.xml13(th)
-#: ./doc/common/tables/neutron-notifier.xml13(th)
-#: ./doc/common/tables/cinder-common.xml13(th)
-#: ./doc/common/tables/nova-trustedcomputing.xml13(th)
-#: ./doc/common/tables/neutron-ml2_flat.xml13(th)
-#: ./doc/common/tables/heat-clients_cinder.xml13(th)
-#: ./doc/common/tables/nova-configdrive.xml13(th)
-#: ./doc/common/tables/cinder-database.xml13(th)
-#: ./doc/common/tables/neutron-rpc.xml13(th)
-#: ./doc/common/tables/cinder-zoning_manager.xml13(th)
-#: ./doc/common/tables/trove-volume.xml13(th)
-#: ./doc/common/tables/keystone-cache.xml13(th)
-#: ./doc/common/tables/nova-zeromq.xml13(th)
-#: ./doc/common/tables/glance-testing.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml12(th)
-#: ./doc/common/tables/glance-registry.xml13(th)
-#: ./doc/common/tables/glance-amqp.xml13(th)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml12(th)
 #: ./doc/common/tables/trove-database.xml13(th)
-#: ./doc/common/tables/heat-clients_backends.xml13(th)
-#: ./doc/common/tables/heat-amqp.xml13(th)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml12(th)
-#: ./doc/common/tables/cinder-hpmsa.xml13(th)
-#: ./doc/common/tables/cinder-emc.xml13(th)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml12(th)
-#: ./doc/common/tables/neutron-fwaas.xml13(th)
-#: ./doc/common/tables/glance-rabbitmq.xml13(th)
-#: ./doc/common/tables/cinder-backups_tsm.xml13(th)
-#: ./doc/common/tables/neutron-sdnve.xml13(th)
-#: ./doc/common/tables/trove-db_mysql.xml13(th)
-#: ./doc/common/tables/nova-qpid.xml13(th)
-#: ./doc/common/tables/trove-rpc.xml13(th)
-#: ./doc/common/tables/cinder-connection.xml13(th)
-#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml12(th)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml12(th)
-#: ./doc/common/tables/trove-db_redis.xml13(th)
-#: ./doc/common/tables/ceilometer-qpid.xml13(th)
-#: ./doc/common/tables/neutron-zeromq.xml13(th)
-#: ./doc/common/tables/keystone-token.xml13(th)
-#: ./doc/common/tables/neutron-vpn.xml13(th)
-#: ./doc/common/tables/neutron-agent.xml13(th)
-#: ./doc/common/tables/neutron-ryu.xml13(th)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml12(th)
-#: ./doc/common/tables/trove-db_couchbase.xml13(th)
-#: ./doc/common/tables/neutron-policy.xml13(th)
-#: ./doc/common/tables/neutron-rootwrap.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml12(th)
-#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml12(th)
-#: ./doc/common/tables/trove-common.xml13(th)
-#: ./doc/common/tables/cinder-ssl.xml13(th)
-#: ./doc/common/tables/heat-api.xml13(th)
-#: ./doc/common/tables/trove-db_percona.xml13(th)
-#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml12(th)
-#: ./doc/common/tables/ceilometer-amqp.xml13(th)
-#: ./doc/common/tables/keystone-auth_token.xml13(th)
-#: ./doc/common/tables/neutron-meta.xml13(th)
-#: ./doc/common/tables/neutron-redis.xml13(th)
-#: ./doc/common/tables/neutron-ssl.xml13(th)
-#: ./doc/common/tables/ceilometer-exchange.xml13(th)
-#: ./doc/common/tables/ceilometer-common.xml13(th)
-#: ./doc/common/tables/ceilometer-alarm.xml13(th)
-#: ./doc/common/tables/keystone-misc.xml13(th)
-#: ./doc/common/tables/nova-scheduling.xml13(th)
-#: ./doc/common/tables/ceilometer-auth.xml13(th)
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml12(th)
-#: ./doc/common/tables/neutron-ml2_mlnx.xml13(th)
-#: ./doc/common/tables/swift-container-server-filter-recon.xml12(th)
-#: ./doc/common/tables/trove-dns.xml13(th)
-#: ./doc/common/tables/neutron-db.xml13(th)
-#: ./doc/common/tables/neutron-ml2_brocade.xml13(th)
-#: ./doc/common/tables/neutron-brocade.xml13(th)
-#: ./doc/common/tables/keystone-redis.xml13(th)
-#: ./doc/common/tables/heat-auth_token.xml13(th)
-#: ./doc/common/tables/keystone-database.xml13(th)
-#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml12(th)
-#: ./doc/common/tables/heat-clients_neutron.xml13(th)
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml13(th)
-#: ./doc/common/tables/cinder-xiv.xml13(th)
-#: ./doc/common/tables/cinder-hds-hus.xml13(th)
-#: ./doc/common/tables/neutron-rabbitmq.xml13(th)
-#: ./doc/common/tables/keystone-kvs.xml13(th)
-#: ./doc/common/tables/trove-ssl.xml13(th)
-#: ./doc/common/tables/keystone-policy.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml12(th)
-#: ./doc/common/tables/swift-swift-swift-hash.xml12(th)
-#: ./doc/common/tables/cinder-auth.xml13(th)
-#: ./doc/common/tables/nova-kombu.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml12(th)
-#: ./doc/common/tables/neutron-ml2_odl.xml13(th)
-#: ./doc/common/tables/heat-quota.xml13(th)
-#: ./doc/common/tables/nova-spice.xml13(th)
-#: ./doc/common/tables/cinder-zoning_fabric.xml13(th)
-#: ./doc/common/tables/neutron-midonet.xml13(th)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml12(th)
+#: ./doc/common/tables/nova-authentication.xml13(th)
 #: ./doc/common/tables/neutron-nvsd.xml13(th)
-#: ./doc/common/tables/neutron-embrane_lb.xml13(th)
-#: ./doc/common/tables/neutron-auth_token.xml13(th)
-#: ./doc/common/tables/cinder-storwize.xml13(th)
-#: ./doc/common/tables/nova-rootwrap.xml13(th)
-#: ./doc/common/tables/cinder-solidfire.xml13(th)
-#: ./doc/common/tables/keystone-revoke.xml13(th)
-#: ./doc/common/tables/glance-ssl.xml13(th)
-#: ./doc/common/tables/heat-metadata_api.xml13(th)
-#: ./doc/common/tables/nova-apiv3.xml13(th)
-#: ./doc/common/tables/glance-db.xml13(th)
-#: ./doc/common/tables/neutron-vmware.xml13(th)
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml12(th)
-#: ./doc/common/tables/nova-api.xml13(th)
-#: ./doc/common/tables/glance-matchmaker.xml13(th)
-#: ./doc/common/tables/keystone-ssl.xml13(th)
-#: ./doc/common/tables/swift-rsyncd-container.xml12(th)
-#: ./doc/common/tables/cinder-san-solaris.xml13(th)
-#: ./doc/common/tables/trove-heat.xml13(th)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml13(th)
-#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml12(th)
-#: ./doc/common/tables/glance-paste.xml13(th)
-#: ./doc/common/tables/nova-rdp.xml13(th)
-#: ./doc/common/tables/neutron-quotas.xml13(th)
-#: ./doc/common/tables/nova-rpc.xml13(th)
-#: ./doc/common/tables/trove-guestagent.xml13(th)
-#: ./doc/common/tables/nova-baremetal.xml13(th)
-#: ./doc/common/tables/heat-clients_keystone.xml13(th)
 #: ./doc/common/tables/swift-account-server-pipeline-main.xml12(th)
-#: ./doc/common/tables/keystone-rabbit.xml13(th)
-#: ./doc/common/tables/glance-api.xml13(th)
-#: ./doc/common/tables/cinder-scheduler.xml13(th)
-#: ./doc/common/tables/keystone-api.xml13(th)
-#: ./doc/common/tables/neutron-ml2_ncs.xml13(th)
-#: ./doc/common/tables/neutron-nec.xml13(th)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml13(th)
-#: ./doc/common/tables/neutron-cadf.xml13(th)
-#: ./doc/common/tables/neutron-testing.xml13(th)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml12(th)
-#: ./doc/common/tables/glance-cinder.xml13(th)
-#: ./doc/common/tables/nova-redis.xml13(th)
-#: ./doc/common/tables/neutron-embrane.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml12(th)
-#: ./doc/common/tables/nova-upgrade_levels.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml12(th)
-#: ./doc/common/tables/ceilometer-inspector.xml13(th)
-#: ./doc/common/tables/nova-rabbitmq.xml13(th)
-#: ./doc/common/tables/heat-common.xml13(th)
+#: ./doc/common/tables/glance-gridfs.xml13(th)
+#: ./doc/common/tables/neutron-notifier.xml13(th)
+#: ./doc/common/tables/nova-rpc_all.xml13(th)
+#: ./doc/common/tables/neutron-hyperv_agent.xml13(th)
 #: ./doc/common/tables/keystone-federation.xml13(th)
-#: ./doc/common/tables/cinder-zadara.xml13(th)
-#: ./doc/common/tables/neutron-nuage.xml13(th)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml12(th)
-#: ./doc/common/tables/ceilometer-ssl.xml13(th)
-#: ./doc/common/tables/nova-quota.xml13(th)
-#: ./doc/common/tables/nova-conductor.xml13(th)
-#: ./doc/common/tables/nova-compute.xml13(th)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml12(th)
-#: ./doc/common/tables/cinder-storage_xen.xml13(th)
+#: ./doc/common/tables/nova-scheduling.xml13(th)
+#: ./doc/common/tables/cinder-ssl.xml13(th)
+#: ./doc/common/tables/trove-ssl.xml13(th)
+#: ./doc/common/tables/cinder-eqlx.xml13(th)
+#: ./doc/common/tables/heat-redis.xml13(th)
+#: ./doc/common/tables/nova-ec2.xml13(th)
 #: ./doc/common/tables/keystone-credential.xml13(th)
-#: ./doc/common/tables/trove-amqp.xml13(th)
+#: ./doc/common/tables/cinder-block-device.xml13(th)
+#: ./doc/common/tables/neutron-metadata.xml13(th)
+#: ./doc/common/tables/nova-fping.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml12(th)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml12(th)
+#: ./doc/common/tables/neutron-ml2_ncs.xml13(th)
+#: ./doc/common/tables/neutron-ml2_arista.xml13(th)
+#: ./doc/common/tables/nova-trustedcomputing.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml12(th)
+#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml12(th)
+#: ./doc/common/tables/neutron-compute.xml13(th)
+#: ./doc/common/tables/glance-imagecache.xml13(th)
+#: ./doc/common/tables/neutron-ml2_brocade.xml13(th)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml12(th)
+#: ./doc/common/tables/cinder-nas.xml13(th)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml13(th)
+#: ./doc/common/tables/heat-clients_swift.xml13(th)
+#: ./doc/common/tables/keystone-logging.xml13(th)
+#: ./doc/common/tables/neutron-brocade.xml13(th)
+#: ./doc/common/tables/neutron-ml2_odl.xml13(th)
+#: ./doc/common/tables/swift-object-server-filter-recon.xml12(th)
+#: ./doc/common/tables/cinder-connection.xml13(th)
+#: ./doc/common/tables/heat-rpc.xml13(th)
+#: ./doc/common/tables/trove-taskmanager.xml13(th)
+#: ./doc/common/tables/heat-cloudwatch_api.xml13(th)
+#: ./doc/common/tables/cinder-images.xml13(th)
+#: ./doc/common/tables/cinder-huawei.xml13(th)
+#: ./doc/common/tables/nova-console.xml13(th)
+#: ./doc/common/tables/neutron-fwaas.xml13(th)
+#: ./doc/common/tables/cinder-nexenta_nfs.xml13(th)
+#: ./doc/common/tables/nova-quota.xml13(th)
+#: ./doc/common/tables/heat-logging.xml13(th)
+#: ./doc/common/tables/trove-redis.xml13(th)
+#: ./doc/common/tables/keystone-stats.xml13(th)
+#: ./doc/common/tables/heat-crypt.xml13(th)
+#: ./doc/common/tables/neutron-ssl.xml13(th)
+#: ./doc/common/tables/neutron-midonet.xml13(th)
+#: ./doc/common/tables/cinder-coraid.xml13(th)
+#: ./doc/common/tables/neutron-wsgi.xml13(th)
+#: ./doc/common/tables/cinder-compute.xml13(th)
+#: ./doc/common/tables/swift-rsyncd-object.xml12(th)
+#: ./doc/common/tables/glance-wsgi.xml13(th)
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml12(th)
+#: ./doc/common/tables/nova-baremetal.xml13(th)
+#: ./doc/common/tables/neutron-qpid.xml13(th)
+#: ./doc/common/tables/nova-rpc.xml13(th)
+#: ./doc/common/tables/cinder-backups_tsm.xml13(th)
+#: ./doc/common/tables/cinder-san.xml13(th)
+#: ./doc/common/tables/nova-logging.xml13(th)
+#: ./doc/common/tables/neutron-nec.xml13(th)
+#: ./doc/common/tables/keystone-security.xml13(th)
+#: ./doc/common/tables/heat-clients_neutron.xml13(th)
+#: ./doc/common/tables/nova-api.xml13(th)
+#: ./doc/common/tables/neutron-ml2_mlnx.xml13(th)
+#: ./doc/common/tables/trove-auth_token.xml13(th)
+#: ./doc/common/tables/keystone-trust.xml13(th)
+#: ./doc/common/tables/glance-cinder.xml13(th)
+#: ./doc/common/tables/swift-object-server-object-updater.xml12(th)
+#: ./doc/common/tables/glance-common.xml13(th)
+#: ./doc/common/tables/neutron-ml2_vxlan.xml13(th)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml12(th)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml12(th)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml12(th)
+#: ./doc/common/tables/trove-nova.xml13(th)
+#: ./doc/common/tables/neutron-meta.xml13(th)
+#: ./doc/common/tables/neutron-rabbitmq.xml13(th)
+#: ./doc/common/tables/keystone-ec2.xml13(th)
+#: ./doc/common/tables/heat-clients_keystone.xml13(th)
+#: ./doc/common/tables/neutron-api.xml13(th)
+#: ./doc/common/tables/trove-logging.xml13(th)
+#: ./doc/common/tables/glance-db.xml13(th)
+#: ./doc/common/tables/keystone-kvs.xml13(th)
+#: ./doc/common/tables/keystone-redis.xml13(th)
 #: ./doc/common/tables/nova-xvpnvncproxy.xml13(th)
+#: ./doc/common/tables/glance-paste.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml12(th)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml12(th)
+#: ./doc/common/tables/nova-hyperv.xml13(th)
+#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml12(th)
+#: ./doc/common/tables/heat-clients_backends.xml13(th)
+#: ./doc/common/tables/glance-testing.xml13(th)
+#: ./doc/common/tables/neutron-common.xml13(th)
+#: ./doc/common/tables/nova-hypervisor.xml13(th)
+#: ./doc/common/tables/keystone-qpid.xml13(th)
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml12(th)
+#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml12(th)
+#: ./doc/common/tables/nova-wsgi.xml13(th)
+#: ./doc/common/tables/keystone-cache.xml13(th)
+#: ./doc/common/tables/nova-configdrive.xml13(th)
+#: ./doc/common/tables/keystone-token.xml13(th)
+#: ./doc/common/tables/ceilometer-ssl.xml13(th)
+#: ./doc/common/tables/ceilometer-qpid.xml13(th)
+#: ./doc/common/tables/heat-database.xml13(th)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml13(th)
+#: ./doc/common/tables/neutron-ml2.xml13(th)
+#: ./doc/common/tables/neutron-db.xml13(th)
+#: ./doc/common/tables/keystone-database.xml13(th)
+#: ./doc/common/tables/keystone-memcache.xml13(th)
+#: ./doc/common/tables/trove-debug.xml13(th)
+#: ./doc/common/tables/trove-swift.xml13(th)
+#: ./doc/common/tables/nova-tilera.xml13(th)
+#: ./doc/common/tables/nova-libvirt.xml13(th)
+#: ./doc/common/tables/neutron-mlnx.xml13(th)
+#: ./doc/common/tables/cinder-zoning_manager.xml13(th)
+#: ./doc/common/tables/ceilometer-amqp.xml13(th)
+#: ./doc/common/tables/glance-ssl.xml13(th)
+#: ./doc/common/tables/neutron-securitygroups.xml13(th)
+#: ./doc/common/tables/keystone-debug.xml13(th)
+#: ./doc/common/tables/cinder-rootwrap.xml13(th)
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml13(th)
 msgid "Configuration option = Default value"
 msgstr "設定オプション = 既定値"
 
-#: ./doc/common/tables/nova-cells.xml19(th)
-#: ./doc/common/tables/nova-rpc_all.xml198(th)
-#: ./doc/common/tables/ceilometer-cells.xml19(th)
-#: ./doc/common/tables/nova-db.xml26(th)
-#: ./doc/common/tables/nova-scheduling.xml118(th)
-#: ./doc/common/tables/nova-rpc.xml62(th)
-#: ./doc/common/tables/nova-upgrade_levels.xml19(th)
-#: ./doc/common/tables/nova-quota.xml82(th)
-msgid "[cells]"
+#: ./doc/common/tables/ceilometer-database.xml22(td)
+msgid "database_connection = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml22(td)
-#: ./doc/common/tables/ceilometer-cells.xml26(td)
-msgid "call_timeout = 60"
+#: ./doc/common/tables/ceilometer-database.xml23(td)
+msgid "(StrOpt) DEPRECATED - Database connection string."
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml23(td)
-#: ./doc/common/tables/ceilometer-cells.xml27(td)
-msgid "(IntOpt) Seconds to wait for response from a call to a cell."
+#: ./doc/common/tables/ceilometer-database.xml26(td)
+msgid "mysql_engine = InnoDB"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml26(td)
-#: ./doc/common/tables/ceilometer-cells.xml30(td)
-msgid "capabilities = hypervisor=xenserver;kvm, os=linux;windows"
+#: ./doc/common/tables/ceilometer-database.xml27(td)
+msgid "(StrOpt) MySQL engine to use."
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml27(td)
-#: ./doc/common/tables/ceilometer-cells.xml31(td)
-msgid "(ListOpt) Key/Multi-value list with the capabilities of the cell"
+#: ./doc/common/tables/ceilometer-database.xml30(td)
+msgid "sqlite_db = ceilometer.sqlite"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml30(td)
-#: ./doc/common/tables/ceilometer-cells.xml34(td)
-msgid "cell_type = compute"
+#: ./doc/common/tables/ceilometer-database.xml31(td)
+#: ./doc/common/tables/nova-db.xml105(td)
+#: ./doc/common/tables/glance-db.xml87(td)
+#: ./doc/common/tables/neutron-db.xml23(td)
+#: ./doc/common/tables/keystone-database.xml87(td)
+msgid "(StrOpt) The file name to use with SQLite"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml31(td)
-#: ./doc/common/tables/ceilometer-cells.xml35(td)
-msgid "(StrOpt) Type of cell: api or compute"
+#: ./doc/common/tables/ceilometer-database.xml34(td)
+#: ./doc/common/tables/nova-db.xml108(td)
+#: ./doc/common/tables/cinder-common.xml170(td)
+#: ./doc/common/tables/glance-db.xml90(td)
+#: ./doc/common/tables/heat-database.xml30(td)
+#: ./doc/common/tables/neutron-db.xml26(td)
+#: ./doc/common/tables/keystone-database.xml90(td)
+msgid "sqlite_synchronous = True"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml34(td)
-msgid "cells_config = None"
+#: ./doc/common/tables/ceilometer-database.xml35(td)
+#: ./doc/common/tables/nova-db.xml109(td)
+#: ./doc/common/tables/glance-db.xml91(td)
+#: ./doc/common/tables/neutron-db.xml27(td)
+#: ./doc/common/tables/keystone-database.xml91(td)
+msgid "(BoolOpt) If True, SQLite uses synchronous mode"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml35(td)
+#: ./doc/common/tables/ceilometer-database.xml41(td)
+#: ./doc/common/tables/cinder-storage.xml137(td)
+#: ./doc/common/tables/nova-db.xml36(td)
+#: ./doc/common/tables/glance-db.xml22(td)
+#: ./doc/common/tables/heat-database.xml37(td)
+#: ./doc/common/tables/neutron-db.xml33(td)
+#: ./doc/common/tables/keystone-database.xml22(td)
+msgid "backend = sqlalchemy"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-database.xml42(td)
+#: ./doc/common/tables/cinder-database.xml23(td)
+#: ./doc/common/tables/cinder-storage.xml138(td)
+#: ./doc/common/tables/nova-db.xml37(td)
+#: ./doc/common/tables/glance-db.xml23(td)
+#: ./doc/common/tables/heat-database.xml38(td)
+#: ./doc/common/tables/neutron-db.xml34(td)
+#: ./doc/common/tables/keystone-database.xml23(td)
+msgid "(StrOpt) The backend to use for db"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-database.xml45(td)
 msgid ""
-"(StrOpt) Configuration file from which to read cells configuration. If "
-"given, overrides reading cells from the database."
+"connection = sqlite:////usr/lib/python/site-"
+"packages/ceilometer/openstack/common/db/$sqlite_db"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml38(td)
-msgid "driver = nova.cells.rpc_driver.CellsRPCDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-cells.xml39(td)
-msgid "(StrOpt) Cells communication driver to use"
-msgstr ""
-
-#: ./doc/common/tables/nova-cells.xml42(td)
-#: ./doc/common/tables/ceilometer-cells.xml38(td)
-#: ./doc/common/tables/keystone-ssl.xml77(td)
-msgid "enable = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-cells.xml43(td)
-#: ./doc/common/tables/ceilometer-cells.xml39(td)
-msgid "(BoolOpt) Enable cell functionality"
-msgstr ""
-
-#: ./doc/common/tables/nova-cells.xml46(td)
-msgid "instance_update_num_instances = 1"
-msgstr ""
-
-#: ./doc/common/tables/nova-cells.xml47(td)
-msgid "(IntOpt) Number of instances to update per periodic task run"
-msgstr ""
-
-#: ./doc/common/tables/nova-cells.xml50(td)
-msgid "instance_updated_at_threshold = 3600"
-msgstr ""
-
-#: ./doc/common/tables/nova-cells.xml51(td)
+#: ./doc/common/tables/ceilometer-database.xml46(td)
+#: ./doc/common/tables/nova-db.xml41(td)
+#: ./doc/common/tables/cinder-connection.xml23(td)
+#: ./doc/common/tables/glance-db.xml27(td)
+#: ./doc/common/tables/heat-database.xml42(td)
+#: ./doc/common/tables/neutron-db.xml38(td)
+#: ./doc/common/tables/keystone-database.xml27(td)
 msgid ""
-"(IntOpt) Number of seconds after an instance was updated or deleted to "
-"continue to update cells"
+"(StrOpt) The SQLAlchemy connection string used to connect to the database"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml54(td)
-#: ./doc/common/tables/ceilometer-cells.xml42(td)
-msgid "manager = nova.cells.manager.CellsManager"
+#: ./doc/common/tables/ceilometer-database.xml49(td)
+#: ./doc/common/tables/nova-db.xml44(td)
+#: ./doc/common/tables/cinder-connection.xml26(td)
+#: ./doc/common/tables/glance-db.xml30(td)
+#: ./doc/common/tables/heat-database.xml45(td)
+#: ./doc/common/tables/neutron-db.xml41(td)
+#: ./doc/common/tables/keystone-database.xml30(td)
+msgid "connection_debug = 0"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml55(td)
-#: ./doc/common/tables/ceilometer-cells.xml43(td)
-msgid "(StrOpt) Manager for cells"
-msgstr ""
-
-#: ./doc/common/tables/nova-cells.xml58(td)
-msgid "max_hop_count = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-cells.xml59(td)
-msgid "(IntOpt) Maximum number of hops for cells routing."
-msgstr ""
-
-#: ./doc/common/tables/nova-cells.xml62(td)
-#: ./doc/common/tables/ceilometer-cells.xml46(td)
-msgid "mute_child_interval = 300"
-msgstr ""
-
-#: ./doc/common/tables/nova-cells.xml63(td)
-#: ./doc/common/tables/ceilometer-cells.xml47(td)
+#: ./doc/common/tables/ceilometer-database.xml50(td)
+#: ./doc/common/tables/nova-db.xml45(td)
+#: ./doc/common/tables/cinder-connection.xml27(td)
+#: ./doc/common/tables/glance-db.xml31(td)
+#: ./doc/common/tables/heat-database.xml46(td)
+#: ./doc/common/tables/neutron-db.xml42(td)
+#: ./doc/common/tables/keystone-database.xml31(td)
 msgid ""
-"(IntOpt) Number of seconds after which a lack of capability and capacity "
-"updates signals the child cell is to be treated as a mute."
+"(IntOpt) Verbosity of SQL debugging information. 0=None, 100=Everything"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml66(td)
-msgid "mute_weight_multiplier = -10.0"
+#: ./doc/common/tables/ceilometer-database.xml53(td)
+#: ./doc/common/tables/nova-db.xml48(td)
+#: ./doc/common/tables/cinder-connection.xml30(td)
+#: ./doc/common/tables/glance-db.xml34(td)
+#: ./doc/common/tables/heat-database.xml49(td)
+#: ./doc/common/tables/neutron-db.xml45(td)
+#: ./doc/common/tables/keystone-database.xml34(td)
+msgid "connection_trace = False"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml67(td)
+#: ./doc/common/tables/ceilometer-database.xml54(td)
+#: ./doc/common/tables/nova-db.xml49(td)
+#: ./doc/common/tables/cinder-connection.xml31(td)
+#: ./doc/common/tables/glance-db.xml35(td)
+#: ./doc/common/tables/heat-database.xml50(td)
+#: ./doc/common/tables/neutron-db.xml46(td)
+#: ./doc/common/tables/keystone-database.xml35(td)
+msgid "(BoolOpt) Add python stack traces to SQL as comment strings"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-database.xml57(td)
+#: ./doc/common/tables/nova-db.xml68(td)
+#: ./doc/common/tables/cinder-common.xml229(td)
+#: ./doc/common/tables/glance-db.xml54(td)
+#: ./doc/common/tables/heat-database.xml53(td)
+#: ./doc/common/tables/neutron-db.xml65(td)
+#: ./doc/common/tables/keystone-database.xml54(td)
+msgid "idle_timeout = 3600"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-database.xml58(td)
+#: ./doc/common/tables/nova-db.xml69(td)
+#: ./doc/common/tables/glance-db.xml55(td)
+#: ./doc/common/tables/neutron-db.xml66(td)
+#: ./doc/common/tables/keystone-database.xml55(td)
+msgid "(IntOpt) Timeout before idle sql connections are reaped"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-database.xml61(td)
+#: ./doc/common/tables/cinder-storage.xml141(td)
+#: ./doc/common/tables/nova-db.xml72(td)
+#: ./doc/common/tables/glance-db.xml58(td)
+#: ./doc/common/tables/heat-database.xml57(td)
+#: ./doc/common/tables/keystone-database.xml58(td)
+msgid "max_overflow = None"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-database.xml62(td)
+#: ./doc/common/tables/cinder-storage.xml142(td)
+#: ./doc/common/tables/nova-db.xml73(td)
+#: ./doc/common/tables/glance-db.xml59(td)
+#: ./doc/common/tables/heat-database.xml58(td)
+#: ./doc/common/tables/neutron-db.xml70(td)
+#: ./doc/common/tables/keystone-database.xml59(td)
+msgid "(IntOpt) If set, use this value for max_overflow with sqlalchemy"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-database.xml65(td)
+#: ./doc/common/tables/nova-db.xml76(td)
+#: ./doc/common/tables/glance-db.xml62(td)
+#: ./doc/common/tables/heat-database.xml61(td)
+#: ./doc/common/tables/keystone-database.xml62(td)
+msgid "max_pool_size = None"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-database.xml66(td)
+#: ./doc/common/tables/cinder-storage.xml146(td)
+#: ./doc/common/tables/nova-db.xml77(td)
+#: ./doc/common/tables/glance-db.xml63(td)
+#: ./doc/common/tables/heat-database.xml62(td)
+#: ./doc/common/tables/neutron-db.xml74(td)
+#: ./doc/common/tables/keystone-database.xml63(td)
+msgid "(IntOpt) Maximum number of SQL connections to keep open in a pool"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-database.xml69(td)
+#: ./doc/common/tables/cinder-storage.xml149(td)
+#: ./doc/common/tables/nova-db.xml80(td)
+#: ./doc/common/tables/glance-db.xml66(td)
+#: ./doc/common/tables/heat-database.xml65(td)
+#: ./doc/common/tables/neutron-db.xml77(td)
+#: ./doc/common/tables/keystone-database.xml66(td)
+msgid "max_retries = 10"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-database.xml70(td)
+#: ./doc/common/tables/nova-db.xml81(td)
+#: ./doc/common/tables/glance-db.xml67(td)
+#: ./doc/common/tables/neutron-db.xml78(td)
+#: ./doc/common/tables/keystone-database.xml67(td)
 msgid ""
-"(FloatOpt) Multiplier used to weigh mute children. (The value should be "
-"negative.)"
+"(IntOpt) Maximum db connection retries during startup. (setting -1 implies "
+"an infinite retry count)"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml70(td)
-msgid "mute_weight_value = 1000.0"
+#: ./doc/common/tables/ceilometer-database.xml73(td)
+#: ./doc/common/tables/cinder-storage.xml153(td)
+#: ./doc/common/tables/nova-db.xml84(td)
+#: ./doc/common/tables/glance-db.xml70(td)
+#: ./doc/common/tables/heat-database.xml69(td)
+#: ./doc/common/tables/neutron-db.xml81(td)
+#: ./doc/common/tables/keystone-database.xml70(td)
+msgid "min_pool_size = 1"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml71(td)
+#: ./doc/common/tables/ceilometer-database.xml74(td)
+#: ./doc/common/tables/cinder-storage.xml154(td)
+#: ./doc/common/tables/nova-db.xml85(td)
+#: ./doc/common/tables/glance-db.xml71(td)
+#: ./doc/common/tables/heat-database.xml70(td)
+#: ./doc/common/tables/neutron-db.xml82(td)
+#: ./doc/common/tables/keystone-database.xml71(td)
+msgid "(IntOpt) Minimum number of SQL connections to keep open in a pool"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-database.xml77(td)
+#: ./doc/common/tables/nova-db.xml92(td)
+#: ./doc/common/tables/glance-db.xml78(td)
+#: ./doc/common/tables/heat-database.xml73(td)
+#: ./doc/common/tables/keystone-database.xml78(td)
+msgid "pool_timeout = None"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-database.xml78(td)
+#: ./doc/common/tables/nova-db.xml93(td)
+#: ./doc/common/tables/glance-db.xml79(td)
+#: ./doc/common/tables/heat-database.xml74(td)
+#: ./doc/common/tables/neutron-db.xml86(td)
+#: ./doc/common/tables/keystone-database.xml79(td)
+msgid "(IntOpt) If set, use this value for pool_timeout with sqlalchemy"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-database.xml81(td)
+#: ./doc/common/tables/nova-db.xml96(td)
+#: ./doc/common/tables/cinder-common.xml233(td)
+#: ./doc/common/tables/glance-db.xml82(td)
+#: ./doc/common/tables/heat-database.xml77(td)
+#: ./doc/common/tables/neutron-db.xml89(td)
+#: ./doc/common/tables/keystone-database.xml82(td)
+msgid "retry_interval = 10"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-database.xml82(td)
+#: ./doc/common/tables/nova-db.xml97(td)
+#: ./doc/common/tables/glance-db.xml83(td)
+#: ./doc/common/tables/neutron-db.xml90(td)
+#: ./doc/common/tables/keystone-database.xml83(td)
+msgid "(IntOpt) Interval between retries of opening a sql connection"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-database.xml85(td)
+#: ./doc/common/tables/heat-database.xml81(td)
+#: ./doc/common/tables/neutron-db.xml93(td)
+msgid "slave_connection ="
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-database.xml86(td)
+#: ./doc/common/tables/nova-db.xml101(td)
+#: ./doc/common/tables/heat-database.xml82(td)
+#: ./doc/common/tables/neutron-db.xml94(td)
 msgid ""
-"(FloatOpt) Weight value assigned to mute children. (The value should be "
-"positive.)"
+"(StrOpt) The SQLAlchemy connection string used to connect to the slave "
+"database"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml74(td)
-#: ./doc/common/tables/ceilometer-cells.xml50(td)
-msgid "name = nova"
+#: ./doc/common/tables/ceilometer-database.xml89(td)
+msgid "time_to_live = -1"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml75(td)
-#: ./doc/common/tables/ceilometer-cells.xml51(td)
-msgid "(StrOpt) Name of this cell"
-msgstr ""
-
-#: ./doc/common/tables/nova-cells.xml78(td)
-msgid "offset_weight_multiplier = 1.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-cells.xml79(td)
-msgid "(FloatOpt) Multiplier used to weigh offset weigher."
-msgstr ""
-
-#: ./doc/common/tables/nova-cells.xml82(td)
-#: ./doc/common/tables/ceilometer-cells.xml54(td)
-msgid "reserve_percent = 10.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-cells.xml83(td)
-#: ./doc/common/tables/ceilometer-cells.xml55(td)
+#: ./doc/common/tables/ceilometer-database.xml90(td)
 msgid ""
-"(FloatOpt) Percentage of cell capacity to hold in reserve. Affects both "
-"memory and disk utilization"
+"(IntOpt) Number of seconds that samples are kept in the database for (&lt;= "
+"0 means forever)."
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml86(td)
-#: ./doc/common/tables/ceilometer-cells.xml58(td)
-msgid "topic = cells"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml8(caption)
+msgid "Description of configuration options for openvswitch_agent"
 msgstr ""
 
-#: ./doc/common/tables/nova-cells.xml87(td)
-#: ./doc/common/tables/ceilometer-cells.xml59(td)
-msgid "(StrOpt) The topic cells nodes listen on"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml22(td)
+msgid "ovs_integration_bridge = br-int"
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml8(caption)
-msgid "Description of configuration options for db_mongodb"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml23(td)
+msgid "(StrOpt) Name of Open vSwitch bridge to use"
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml19(th)
-msgid "[mongodb]"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml26(td)
+msgid "ovs_use_veth = False"
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml22(td)
-#: ./doc/common/tables/trove-db_cassandra.xml22(td)
-#: ./doc/common/tables/trove-db_redis.xml22(td)
-#: ./doc/common/tables/trove-db_couchbase.xml22(td)
-msgid "backup_strategy = None"
+#: ./doc/common/tables/neutron-openvswitch_agent.xml27(td)
+msgid "(BoolOpt) Uses veth for an interface or not"
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml23(td)
-#: ./doc/common/tables/trove-backup.xml51(td)
+#: ./doc/common/tables/neutron-openvswitch_agent.xml30(td)
+msgid "ovs_vsctl_timeout = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml31(td)
+msgid "(IntOpt) Timeout in seconds for ovs-vsctl commands"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml34(th)
+#: ./doc/common/tables/neutron-rpc.xml66(th)
+#: ./doc/common/tables/neutron-ml2_ofa.xml34(th)
+#: ./doc/common/tables/neutron-metering_agent.xml30(th)
+#: ./doc/common/tables/neutron-nvsd.xml19(th)
+#: ./doc/common/tables/neutron-hyperv_agent.xml19(th)
+#: ./doc/common/tables/neutron-common.xml182(th)
+msgid "[AGENT]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml37(td)
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml44(td)
+msgid "l2_population = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml38(td)
+msgid ""
+"(BoolOpt) Use ml2 l2population mechanism driver to learn remote mac and IPs "
+"and improve tunnel scalability"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml41(td)
+msgid "minimize_polling = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml42(td)
+msgid "(BoolOpt) Minimize polling by monitoring ovsdb for interface changes."
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml45(td)
+msgid "ovsdb_monitor_respawn_interval = 30"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml46(td)
+msgid ""
+"(IntOpt) The number of seconds to wait before respawning the ovsdb monitor "
+"after losing communication with it"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml49(td)
+msgid "tunnel_types ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml50(td)
+msgid "(ListOpt) Network types supported by the agent (gre and/or vxlan)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml53(td)
+msgid "veth_mtu = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml54(td)
+msgid "(IntOpt) MTU size of veth interfaces"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml57(td)
+msgid "vxlan_udp_port = 4789"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml58(td)
+msgid "(IntOpt) The UDP port to use for VXLAN tunnels."
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml61(th)
+#: ./doc/common/tables/neutron-cisco.xml54(th)
+msgid "[CISCO_N1K]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml64(td)
+msgid "local_ip = 10.0.0.3"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml65(td)
+msgid "(StrOpt) N1K Local IP"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml68(th)
+#: ./doc/common/tables/neutron-ryu.xml19(th)
+msgid "[OVS]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml71(td)
+#: ./doc/common/tables/neutron-cisco.xml57(td)
+msgid "bridge_mappings ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml72(td)
+msgid "(ListOpt) List of &lt;physical_network&gt;:&lt;bridge&gt;"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml75(td)
+msgid "enable_tunneling = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml76(td)
+msgid "(BoolOpt) Enable tunneling support"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml79(td)
+msgid "int_peer_patch_port = patch-tun"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml80(td)
+msgid "(StrOpt) Peer patch port in integration bridge for tunnel bridge"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml83(td)
+#: ./doc/common/tables/neutron-cisco.xml73(td)
+#: ./doc/common/tables/nova-vmware.xml46(td)
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml140(td)
+#: ./doc/common/tables/neutron-bigswitch.xml140(td)
+#: ./doc/common/tables/neutron-nvsd.xml22(td)
+msgid "integration_bridge = br-int"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml84(td)
+#: ./doc/common/tables/neutron-sdnve.xml43(td)
+msgid "(StrOpt) Integration bridge to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml87(td)
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml48(td)
+msgid "local_ip ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml88(td)
+msgid "(StrOpt) Local IP address of GRE tunnel endpoints."
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml91(td)
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml29(td)
+#: ./doc/common/tables/neutron-ml2_vlan.xml22(td)
+#: ./doc/common/tables/neutron-hyperv_agent.xml45(td)
+msgid "network_vlan_ranges ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml92(td)
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml30(td)
+#: ./doc/common/tables/neutron-hyperv_agent.xml46(td)
+#: ./doc/common/tables/neutron-mlnx.xml42(td)
+msgid ""
+"(ListOpt) List of &lt;physical_network&gt;:&lt;vlan_min&gt;:&lt;vlan_max&gt;"
+" or &lt;physical_network&gt;"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml95(td)
+#: ./doc/common/tables/neutron-cisco.xml89(td)
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml33(td)
+#: ./doc/common/tables/neutron-hyperv_agent.xml49(td)
+msgid "tenant_network_type = local"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml96(td)
+msgid ""
+"(StrOpt) Network type for tenant networks (local, vlan, gre, vxlan, or none)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml99(td)
+msgid "tun_peer_patch_port = patch-int"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml100(td)
+msgid "(StrOpt) Peer patch port in tunnel bridge for integration bridge"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml103(td)
+#: ./doc/common/tables/neutron-cisco.xml93(td)
+msgid "tunnel_bridge = br-tun"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml104(td)
+msgid "(StrOpt) Tunnel bridge to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml107(td)
+#: ./doc/common/tables/neutron-ml2_gre.xml22(td)
+msgid "tunnel_id_ranges ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml108(td)
+msgid "(ListOpt) List of &lt;tun_min&gt;:&lt;tun_max&gt;"
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml111(td)
+msgid "tunnel_type ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-openvswitch_agent.xml112(td)
+msgid ""
+"(StrOpt) The type of tunnels to use when utilizing tunnels, either 'gre' or "
+"'vxlan'"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml8(caption)
+msgid "Description of configuration options for clients"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml22(td)
+msgid "region_name_for_services = None"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml23(td)
+msgid "(StrOpt) Default region name used to get services endpoints."
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml26(th)
+msgid "[clients]"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml29(td)
+#: ./doc/common/tables/heat-clients_nova.xml22(td)
+#: ./doc/common/tables/heat-clients_heat.xml22(td)
+#: ./doc/common/tables/heat-cfn_api.xml64(td)
+#: ./doc/common/tables/heat-api.xml145(td)
+#: ./doc/common/tables/heat-clients_ceilometer.xml22(td)
+#: ./doc/common/tables/heat-clients_cinder.xml22(td)
+#: ./doc/common/tables/heat-clients_trove.xml22(td)
+#: ./doc/common/tables/nova-ca.xml65(td)
+#: ./doc/common/tables/cinder-ssl.xml22(td)
+#: ./doc/common/tables/trove-ssl.xml22(td)
+#: ./doc/common/tables/heat-clients_swift.xml22(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml60(td)
+#: ./doc/common/tables/neutron-ssl.xml37(td)
+#: ./doc/common/tables/heat-clients_neutron.xml22(td)
+#: ./doc/common/tables/heat-clients_keystone.xml22(td)
+#: ./doc/common/tables/ceilometer-ssl.xml22(td)
+#: ./doc/common/tables/glance-ssl.xml22(td)
+msgid "ca_file = None"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml30(td)
+#: ./doc/common/tables/heat-clients_nova.xml23(td)
+#: ./doc/common/tables/heat-clients_heat.xml23(td)
+#: ./doc/common/tables/heat-clients_ceilometer.xml23(td)
+#: ./doc/common/tables/heat-clients_cinder.xml23(td)
+#: ./doc/common/tables/heat-clients_trove.xml23(td)
+#: ./doc/common/tables/heat-clients_swift.xml23(td)
+#: ./doc/common/tables/heat-clients_neutron.xml23(td)
+#: ./doc/common/tables/heat-clients_keystone.xml23(td)
+msgid "(StrOpt) Optional CA cert file to use in SSL connections."
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml33(td)
+#: ./doc/common/tables/heat-clients_nova.xml26(td)
+#: ./doc/common/tables/heat-clients_heat.xml26(td)
+#: ./doc/common/tables/heat-cfn_api.xml45(td)
+#: ./doc/common/tables/heat-cfn_api.xml68(td)
+#: ./doc/common/tables/heat-api.xml115(td)
+#: ./doc/common/tables/heat-api.xml149(td)
+#: ./doc/common/tables/heat-clients_ceilometer.xml26(td)
+#: ./doc/common/tables/heat-clients_cinder.xml26(td)
+#: ./doc/common/tables/heat-clients_trove.xml26(td)
+#: ./doc/common/tables/nova-ca.xml69(td)
+#: ./doc/common/tables/cinder-ssl.xml26(td)
+#: ./doc/common/tables/trove-ssl.xml26(td)
+#: ./doc/common/tables/heat-clients_swift.xml26(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml41(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml64(td)
+#: ./doc/common/tables/neutron-ssl.xml41(td)
+#: ./doc/common/tables/neutron-nec.xml26(td)
+#: ./doc/common/tables/heat-clients_neutron.xml26(td)
+#: ./doc/common/tables/heat-clients_keystone.xml26(td)
+#: ./doc/common/tables/ceilometer-ssl.xml26(td)
+#: ./doc/common/tables/glance-ssl.xml26(td)
+msgid "cert_file = None"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml34(td)
+#: ./doc/common/tables/heat-clients_nova.xml27(td)
+#: ./doc/common/tables/heat-clients_heat.xml27(td)
+#: ./doc/common/tables/heat-clients_ceilometer.xml27(td)
+#: ./doc/common/tables/heat-clients_cinder.xml27(td)
+#: ./doc/common/tables/heat-clients_trove.xml27(td)
+#: ./doc/common/tables/heat-clients_swift.xml27(td)
+#: ./doc/common/tables/heat-clients_neutron.xml27(td)
+#: ./doc/common/tables/heat-clients_keystone.xml27(td)
+msgid "(StrOpt) Optional PEM-formatted certificate chain file."
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml37(td)
+#: ./doc/common/tables/heat-clients_nova.xml30(td)
+#: ./doc/common/tables/heat-clients_heat.xml30(td)
+#: ./doc/common/tables/heat-clients_ceilometer.xml30(td)
+#: ./doc/common/tables/heat-clients_cinder.xml30(td)
+#: ./doc/common/tables/heat-clients_trove.xml30(td)
+#: ./doc/common/tables/heat-clients_swift.xml30(td)
+#: ./doc/common/tables/heat-clients_neutron.xml30(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml39(td)
+#: ./doc/common/tables/heat-clients_keystone.xml30(td)
+msgid "endpoint_type = publicURL"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml38(td)
+#: ./doc/common/tables/heat-clients_nova.xml31(td)
+#: ./doc/common/tables/heat-clients_heat.xml31(td)
+#: ./doc/common/tables/heat-clients_ceilometer.xml31(td)
+#: ./doc/common/tables/heat-clients_cinder.xml31(td)
+#: ./doc/common/tables/heat-clients_trove.xml31(td)
+#: ./doc/common/tables/heat-clients_swift.xml31(td)
+#: ./doc/common/tables/heat-clients_neutron.xml31(td)
+#: ./doc/common/tables/heat-clients_keystone.xml31(td)
+msgid ""
+"(StrOpt) Type of endpoint in Identity service catalog to use for "
+"communication with the OpenStack service."
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml41(td)
+#: ./doc/common/tables/glance-auth_token.xml101(td)
+#: ./doc/common/tables/heat-clients_nova.xml34(td)
+#: ./doc/common/tables/heat-clients_heat.xml34(td)
+#: ./doc/common/tables/neutron-auth_token.xml101(td)
+#: ./doc/common/tables/ceilometer-auth.xml101(td)
+#: ./doc/common/tables/ceilometer-auth.xml136(td)
+#: ./doc/common/tables/heat-auth_token.xml101(td)
+#: ./doc/common/tables/nova-auth_token.xml94(td)
+#: ./doc/common/tables/heat-clients_ceilometer.xml34(td)
+#: ./doc/common/tables/cinder-auth_token.xml101(td)
+#: ./doc/common/tables/keystone-auth_token.xml101(td)
+#: ./doc/common/tables/heat-clients_cinder.xml34(td)
+#: ./doc/common/tables/heat-clients_trove.xml34(td)
+#: ./doc/common/tables/heat-clients_swift.xml34(td)
+#: ./doc/common/tables/heat-clients_neutron.xml34(td)
+#: ./doc/common/tables/trove-auth_token.xml101(td)
+#: ./doc/common/tables/heat-clients_keystone.xml34(td)
+msgid "insecure = False"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml42(td)
+#: ./doc/common/tables/heat-clients_nova.xml35(td)
+#: ./doc/common/tables/heat-clients_heat.xml35(td)
+#: ./doc/common/tables/heat-clients_ceilometer.xml35(td)
+#: ./doc/common/tables/heat-clients_cinder.xml35(td)
+#: ./doc/common/tables/heat-clients_trove.xml35(td)
+#: ./doc/common/tables/heat-clients_swift.xml35(td)
+#: ./doc/common/tables/heat-clients_neutron.xml35(td)
+#: ./doc/common/tables/heat-clients_keystone.xml35(td)
+msgid "(BoolOpt) If set, then the server's certificate will not be verified."
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml45(td)
+#: ./doc/common/tables/heat-clients_nova.xml38(td)
+#: ./doc/common/tables/heat-clients_heat.xml38(td)
+#: ./doc/common/tables/heat-cfn_api.xml49(td)
+#: ./doc/common/tables/heat-cfn_api.xml72(td)
+#: ./doc/common/tables/heat-api.xml119(td)
+#: ./doc/common/tables/heat-api.xml153(td)
+#: ./doc/common/tables/heat-clients_ceilometer.xml38(td)
+#: ./doc/common/tables/heat-clients_cinder.xml38(td)
+#: ./doc/common/tables/heat-clients_trove.xml38(td)
+#: ./doc/common/tables/nova-ca.xml73(td)
+#: ./doc/common/tables/cinder-ssl.xml30(td)
+#: ./doc/common/tables/trove-ssl.xml30(td)
+#: ./doc/common/tables/heat-clients_swift.xml38(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml45(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml68(td)
+#: ./doc/common/tables/neutron-ssl.xml45(td)
+#: ./doc/common/tables/neutron-nec.xml46(td)
+#: ./doc/common/tables/heat-clients_neutron.xml38(td)
+#: ./doc/common/tables/heat-clients_keystone.xml38(td)
+#: ./doc/common/tables/ceilometer-ssl.xml30(td)
+#: ./doc/common/tables/glance-ssl.xml30(td)
+msgid "key_file = None"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients.xml46(td)
+#: ./doc/common/tables/heat-clients_nova.xml39(td)
+#: ./doc/common/tables/heat-clients_heat.xml39(td)
+#: ./doc/common/tables/heat-clients_ceilometer.xml39(td)
+#: ./doc/common/tables/heat-clients_cinder.xml39(td)
+#: ./doc/common/tables/heat-clients_trove.xml39(td)
+#: ./doc/common/tables/heat-clients_swift.xml39(td)
+#: ./doc/common/tables/heat-clients_neutron.xml39(td)
+#: ./doc/common/tables/heat-clients_keystone.xml39(td)
+msgid "(StrOpt) Optional PEM-formatted file that contains the private key."
+msgstr ""
+
+#: ./doc/common/tables/cinder-solidfire.xml8(caption)
+msgid "Description of configuration options for solidfire"
+msgstr ""
+
+#: ./doc/common/tables/cinder-solidfire.xml22(td)
+msgid "sf_account_prefix = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-solidfire.xml23(td)
+msgid ""
+"(StrOpt) Create SolidFire accounts with this prefix. Any string can be used "
+"here, but the string \"hostname\" is special and will create a prefix using "
+"the cinder node hostsname (previous default behavior). The default is NO "
+"prefix."
+msgstr ""
+
+#: ./doc/common/tables/cinder-solidfire.xml26(td)
+msgid "sf_allow_tenant_qos = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-solidfire.xml27(td)
+msgid "(BoolOpt) Allow tenants to specify QOS on create"
+msgstr ""
+
+#: ./doc/common/tables/cinder-solidfire.xml30(td)
+msgid "sf_api_port = 443"
+msgstr ""
+
+#: ./doc/common/tables/cinder-solidfire.xml31(td)
+msgid ""
+"(IntOpt) SolidFire API port. Useful if the device api is behind a proxy on a"
+" different port."
+msgstr ""
+
+#: ./doc/common/tables/cinder-solidfire.xml34(td)
+msgid "sf_emulate_512 = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-solidfire.xml35(td)
+msgid "(BoolOpt) Set 512 byte emulation on volume creation;"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml8(caption)
+#: ./doc/common/tables/glance-rpc.xml8(caption)
+#: ./doc/common/tables/keystone-rpc.xml8(caption)
+#: ./doc/common/tables/ceilometer-rpc.xml8(caption)
+#: ./doc/common/tables/trove-rpc.xml8(caption)
+#: ./doc/common/tables/cinder-rpc.xml8(caption)
+#: ./doc/common/tables/heat-rpc.xml8(caption)
+#: ./doc/common/tables/nova-rpc.xml8(caption)
+msgid "Description of configuration options for rpc"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml22(td)
+#: ./doc/common/tables/trove-amqp.xml22(td)
+#: ./doc/common/tables/heat-amqp.xml22(td)
+#: ./doc/common/tables/keystone-amqp.xml22(td)
+#: ./doc/common/tables/glance-amqp.xml22(td)
+#: ./doc/common/tables/cinder-rpc.xml26(td)
+#: ./doc/common/tables/nova-rpc_all.xml22(td)
+#: ./doc/common/tables/nova-rpc.xml22(td)
+#: ./doc/common/tables/ceilometer-amqp.xml22(td)
+msgid "amqp_auto_delete = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml23(td)
+#: ./doc/common/tables/trove-amqp.xml23(td)
+#: ./doc/common/tables/heat-amqp.xml23(td)
+#: ./doc/common/tables/keystone-amqp.xml23(td)
+#: ./doc/common/tables/glance-amqp.xml23(td)
+#: ./doc/common/tables/cinder-rpc.xml27(td)
+#: ./doc/common/tables/nova-rpc_all.xml23(td)
+#: ./doc/common/tables/nova-rpc.xml23(td)
+#: ./doc/common/tables/ceilometer-amqp.xml23(td)
+msgid "(BoolOpt) Auto-delete queues in amqp."
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml26(td)
+#: ./doc/common/tables/trove-amqp.xml26(td)
+#: ./doc/common/tables/heat-amqp.xml26(td)
+#: ./doc/common/tables/keystone-amqp.xml26(td)
+#: ./doc/common/tables/glance-amqp.xml26(td)
+#: ./doc/common/tables/cinder-rpc.xml30(td)
+#: ./doc/common/tables/nova-rpc_all.xml26(td)
+#: ./doc/common/tables/nova-rpc.xml26(td)
+#: ./doc/common/tables/ceilometer-amqp.xml26(td)
+msgid "amqp_durable_queues = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml27(td)
+#: ./doc/common/tables/trove-amqp.xml27(td)
+#: ./doc/common/tables/heat-amqp.xml27(td)
+#: ./doc/common/tables/keystone-amqp.xml27(td)
+#: ./doc/common/tables/glance-amqp.xml27(td)
+#: ./doc/common/tables/cinder-rpc.xml31(td)
+#: ./doc/common/tables/nova-rpc_all.xml27(td)
+#: ./doc/common/tables/nova-rpc.xml27(td)
+#: ./doc/common/tables/ceilometer-amqp.xml27(td)
+msgid "(BoolOpt) Use durable queues in amqp."
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml30(td)
+msgid "control_exchange = neutron"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml31(td)
+#: ./doc/common/tables/trove-amqp.xml35(td)
+#: ./doc/common/tables/heat-amqp.xml31(td)
+#: ./doc/common/tables/ceilometer-exchange.xml27(td)
+msgid "(StrOpt) AMQP exchange to connect to if using RabbitMQ or Qpid"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml34(td)
+#: ./doc/common/tables/ceilometer-redis.xml26(td)
+#: ./doc/common/tables/glance-matchmaker.xml22(td)
+#: ./doc/common/tables/trove-rpc.xml30(td)
+#: ./doc/common/tables/cinder-rpc.xml66(td)
+#: ./doc/common/tables/nova-rpc_all.xml54(td)
+#: ./doc/common/tables/heat-rpc.xml30(td)
+#: ./doc/common/tables/nova-rpc.xml34(td)
+#: ./doc/common/tables/keystone-redis.xml26(td)
+msgid "matchmaker_heartbeat_freq = 300"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml35(td)
+#: ./doc/common/tables/ceilometer-redis.xml27(td)
+#: ./doc/common/tables/trove-rpc.xml31(td)
+#: ./doc/common/tables/heat-rpc.xml31(td)
+msgid "(IntOpt) Heartbeat frequency"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml38(td)
+#: ./doc/common/tables/ceilometer-redis.xml30(td)
+#: ./doc/common/tables/glance-matchmaker.xml26(td)
+#: ./doc/common/tables/trove-rpc.xml34(td)
+#: ./doc/common/tables/cinder-rpc.xml70(td)
+#: ./doc/common/tables/nova-rpc_all.xml58(td)
+#: ./doc/common/tables/heat-rpc.xml34(td)
+#: ./doc/common/tables/nova-rpc.xml38(td)
+#: ./doc/common/tables/keystone-redis.xml30(td)
+msgid "matchmaker_heartbeat_ttl = 600"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml39(td)
+#: ./doc/common/tables/ceilometer-redis.xml31(td)
+#: ./doc/common/tables/glance-matchmaker.xml27(td)
+#: ./doc/common/tables/trove-rpc.xml35(td)
+#: ./doc/common/tables/cinder-rpc.xml71(td)
+#: ./doc/common/tables/nova-rpc_all.xml59(td)
+#: ./doc/common/tables/heat-rpc.xml35(td)
+#: ./doc/common/tables/nova-rpc.xml39(td)
+#: ./doc/common/tables/keystone-redis.xml31(td)
+msgid "(IntOpt) Heartbeat time-to-live."
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml42(td)
+msgid "rpc_backend = neutron.openstack.common.rpc.impl_kombu"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml43(td)
+#: ./doc/common/tables/ceilometer-rpc.xml31(td)
+#: ./doc/common/tables/trove-rpc.xml51(td)
+#: ./doc/common/tables/heat-rpc.xml39(td)
+msgid "(StrOpt) The messaging module to use, defaults to kombu."
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml46(td)
+#: ./doc/common/tables/keystone-amqp.xml50(td)
+#: ./doc/common/tables/ceilometer-rpc.xml34(td)
+#: ./doc/common/tables/trove-rpc.xml54(td)
+#: ./doc/common/tables/glance-zmq.xml22(td)
+#: ./doc/common/tables/cinder-rpc.xml186(td)
+#: ./doc/common/tables/nova-rpc_all.xml154(td)
+#: ./doc/common/tables/heat-rpc.xml42(td)
+#: ./doc/common/tables/nova-rpc.xml46(td)
+msgid "rpc_cast_timeout = 30"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml47(td)
+#: ./doc/common/tables/keystone-amqp.xml51(td)
+#: ./doc/common/tables/ceilometer-rpc.xml35(td)
+#: ./doc/common/tables/trove-rpc.xml55(td)
+#: ./doc/common/tables/glance-zmq.xml23(td)
+#: ./doc/common/tables/cinder-rpc.xml187(td)
+#: ./doc/common/tables/nova-rpc_all.xml155(td)
+#: ./doc/common/tables/heat-rpc.xml43(td)
+#: ./doc/common/tables/nova-rpc.xml47(td)
+msgid ""
+"(IntOpt) Seconds to wait before a cast expires (TTL). Only supported by "
+"impl_zmq."
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml50(td)
+#: ./doc/common/tables/keystone-amqp.xml54(td)
+#: ./doc/common/tables/ceilometer-rpc.xml38(td)
+#: ./doc/common/tables/trove-rpc.xml58(td)
+#: ./doc/common/tables/glance-amqp.xml42(td)
+#: ./doc/common/tables/cinder-rpc.xml190(td)
+#: ./doc/common/tables/nova-rpc_all.xml158(td)
+#: ./doc/common/tables/heat-rpc.xml46(td)
+#: ./doc/common/tables/nova-rpc.xml50(td)
+msgid "rpc_conn_pool_size = 30"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml51(td)
+#: ./doc/common/tables/ceilometer-rpc.xml39(td)
+#: ./doc/common/tables/trove-rpc.xml59(td)
+#: ./doc/common/tables/heat-rpc.xml47(td)
+msgid "(IntOpt) Size of RPC connection pool"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml54(td)
+#: ./doc/common/tables/keystone-amqp.xml58(td)
+#: ./doc/common/tables/ceilometer-rpc.xml42(td)
+#: ./doc/common/tables/trove-rpc.xml62(td)
+#: ./doc/common/tables/glance-amqp.xml46(td)
+#: ./doc/common/tables/cinder-rpc.xml194(td)
+#: ./doc/common/tables/nova-rpc_all.xml162(td)
+#: ./doc/common/tables/heat-rpc.xml50(td)
+#: ./doc/common/tables/nova-rpc.xml54(td)
+msgid "rpc_response_timeout = 60"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml55(td)
+#: ./doc/common/tables/ceilometer-rpc.xml43(td)
+#: ./doc/common/tables/trove-rpc.xml63(td)
+#: ./doc/common/tables/heat-rpc.xml51(td)
+msgid "(IntOpt) Seconds to wait for a response from call or multicall"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml58(td)
+#: ./doc/common/tables/keystone-amqp.xml62(td)
+#: ./doc/common/tables/ceilometer-rpc.xml46(td)
+#: ./doc/common/tables/trove-rpc.xml66(td)
+#: ./doc/common/tables/glance-amqp.xml50(td)
+#: ./doc/common/tables/cinder-rpc.xml198(td)
+#: ./doc/common/tables/nova-rpc_all.xml166(td)
+#: ./doc/common/tables/heat-rpc.xml54(td)
+#: ./doc/common/tables/nova-rpc.xml58(td)
+msgid "rpc_thread_pool_size = 64"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml59(td)
+#: ./doc/common/tables/ceilometer-rpc.xml47(td)
+#: ./doc/common/tables/trove-rpc.xml67(td)
+#: ./doc/common/tables/heat-rpc.xml55(td)
+msgid "(IntOpt) Size of RPC thread pool"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml62(td)
+msgid "rpc_workers = 0"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml63(td)
+msgid "(IntOpt) Number of RPC worker processes for service"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml69(td)
+msgid "rpc_support_old_agents = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml70(td)
+msgid "(BoolOpt) Enable server RPC compatibility with old agents"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml73(th)
+#: ./doc/common/tables/ceilometer-redis.xml49(th)
+#: ./doc/common/tables/glance-matchmaker.xml30(th)
+#: ./doc/common/tables/cinder-rpc.xml238(th)
+#: ./doc/common/tables/nova-rpc_all.xml205(th)
+#: ./doc/common/tables/heat-rpc.xml58(th)
+#: ./doc/common/tables/trove-redis.xml34(th)
+#: ./doc/common/tables/nova-rpc.xml69(th)
+#: ./doc/common/tables/keystone-redis.xml42(th)
+msgid "[matchmaker_ring]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml76(td)
+#: ./doc/common/tables/ceilometer-redis.xml52(td)
+#: ./doc/common/tables/glance-matchmaker.xml33(td)
+#: ./doc/common/tables/cinder-rpc.xml241(td)
+#: ./doc/common/tables/nova-rpc_all.xml208(td)
+#: ./doc/common/tables/heat-rpc.xml61(td)
+#: ./doc/common/tables/trove-redis.xml37(td)
+#: ./doc/common/tables/nova-rpc.xml72(td)
+#: ./doc/common/tables/keystone-redis.xml45(td)
+msgid "ringfile = /etc/oslo/matchmaker_ring.json"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml77(td)
+#: ./doc/common/tables/ceilometer-redis.xml53(td)
+#: ./doc/common/tables/heat-rpc.xml62(td)
+#: ./doc/common/tables/trove-redis.xml38(td)
+msgid "(StrOpt) Matchmaker ring file (JSON)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml80(th)
+#: ./doc/common/tables/ceilometer-rpc.xml92(th)
+#: ./doc/common/tables/trove-rpc.xml70(th)
+#: ./doc/common/tables/heat-rpc.xml65(th)
+msgid "[rpc_notifier2]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml83(td)
+#: ./doc/common/tables/ceilometer-rpc.xml95(td)
+#: ./doc/common/tables/trove-rpc.xml73(td)
+#: ./doc/common/tables/heat-rpc.xml68(td)
+msgid "topics = notifications"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rpc.xml84(td)
+#: ./doc/common/tables/trove-rpc.xml74(td)
+msgid "(ListOpt) AMQP topic(s) used for openstack notifications"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_percona.xml8(caption)
+msgid "Description of configuration options for db_percona"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_percona.xml19(th)
+msgid "[percona]"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_percona.xml22(td)
+#: ./doc/common/tables/trove-db_mysql.xml22(td)
+#: ./doc/common/tables/trove-backup.xml50(td)
+msgid "backup_strategy = InnoBackupEx"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_percona.xml23(td)
 #: ./doc/common/tables/trove-db_cassandra.xml23(td)
 #: ./doc/common/tables/trove-db_mysql.xml23(td)
-#: ./doc/common/tables/trove-db_redis.xml23(td)
 #: ./doc/common/tables/trove-db_couchbase.xml23(td)
-#: ./doc/common/tables/trove-db_percona.xml23(td)
+#: ./doc/common/tables/trove-db_mongodb.xml23(td)
+#: ./doc/common/tables/trove-backup.xml51(td)
+#: ./doc/common/tables/trove-db_redis.xml23(td)
 msgid "(StrOpt) Default strategy to perform backups."
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml26(td)
-msgid "mount_point = /var/lib/mongodb"
+#: ./doc/common/tables/trove-db_percona.xml26(td)
+#: ./doc/common/tables/trove-db_mysql.xml26(td)
+msgid "mount_point = /var/lib/mysql"
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml27(td)
+#: ./doc/common/tables/trove-db_percona.xml27(td)
 #: ./doc/common/tables/trove-db_cassandra.xml27(td)
 #: ./doc/common/tables/trove-db_mysql.xml27(td)
-#: ./doc/common/tables/trove-db_redis.xml27(td)
 #: ./doc/common/tables/trove-db_couchbase.xml27(td)
-#: ./doc/common/tables/trove-db_percona.xml27(td)
+#: ./doc/common/tables/trove-db_mongodb.xml27(td)
+#: ./doc/common/tables/trove-db_redis.xml27(td)
 msgid ""
 "(StrOpt) Filesystem path for mounting volumes if volume support is enabled"
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml30(td)
-msgid "tcp_ports = 2500, 27017"
+#: ./doc/common/tables/trove-db_percona.xml30(td)
+#: ./doc/common/tables/trove-db_mysql.xml30(td)
+msgid "root_on_create = False"
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml31(td)
+#: ./doc/common/tables/trove-db_percona.xml31(td)
+#: ./doc/common/tables/trove-db_mysql.xml31(td)
+msgid ""
+"(BoolOpt) Enable the automatic creation of the root user for the service "
+"during instance-create. The generated password for the root user is "
+"immediately returned in the response of instance-create as the 'password' "
+"field."
+msgstr ""
+
+#: ./doc/common/tables/trove-db_percona.xml34(td)
+#: ./doc/common/tables/trove-db_mysql.xml34(td)
+msgid "tcp_ports = 3306"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_percona.xml35(td)
 #: ./doc/common/tables/trove-db_cassandra.xml31(td)
 #: ./doc/common/tables/trove-db_mysql.xml35(td)
-#: ./doc/common/tables/trove-db_redis.xml31(td)
 #: ./doc/common/tables/trove-db_couchbase.xml31(td)
-#: ./doc/common/tables/trove-db_percona.xml35(td)
+#: ./doc/common/tables/trove-db_mongodb.xml31(td)
+#: ./doc/common/tables/trove-db_redis.xml31(td)
 msgid ""
 "(ListOpt) List of TCP ports and/or port ranges to open in the security group"
 " (only applicable if trove_security_groups_support is True)"
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml34(td)
+#: ./doc/common/tables/trove-db_percona.xml38(td)
 #: ./doc/common/tables/trove-db_cassandra.xml34(td)
 #: ./doc/common/tables/trove-db_mysql.xml38(td)
-#: ./doc/common/tables/trove-db_redis.xml34(td)
 #: ./doc/common/tables/trove-db_couchbase.xml34(td)
-#: ./doc/common/tables/trove-db_percona.xml38(td)
+#: ./doc/common/tables/trove-db_mongodb.xml34(td)
+#: ./doc/common/tables/trove-db_redis.xml34(td)
 msgid "udp_ports ="
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml35(td)
+#: ./doc/common/tables/trove-db_percona.xml39(td)
+#: ./doc/common/tables/trove-db_cassandra.xml35(td)
+#: ./doc/common/tables/trove-db_mysql.xml39(td)
+#: ./doc/common/tables/trove-db_couchbase.xml35(td)
+#: ./doc/common/tables/trove-db_redis.xml35(td)
 msgid ""
-"(ListOpt) List of UPD ports and/or port ranges to open in the security group"
+"(ListOpt) List of UDP ports and/or port ranges to open in the security group"
 " (only applicable if trove_security_groups_support is True)"
 msgstr ""
 
+#: ./doc/common/tables/trove-db_percona.xml42(td)
+#: ./doc/common/tables/trove-db_couchbase.xml38(td)
 #: ./doc/common/tables/trove-db_mongodb.xml38(td)
 #: ./doc/common/tables/trove-db_redis.xml38(td)
-#: ./doc/common/tables/trove-db_couchbase.xml38(td)
-#: ./doc/common/tables/trove-db_percona.xml42(td)
 msgid "usage_timeout = 450"
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mongodb.xml39(td)
+#: ./doc/common/tables/trove-db_percona.xml43(td)
 #: ./doc/common/tables/trove-db_cassandra.xml39(td)
 #: ./doc/common/tables/trove-db_mysql.xml43(td)
-#: ./doc/common/tables/trove-db_redis.xml39(td)
 #: ./doc/common/tables/trove-db_couchbase.xml39(td)
-#: ./doc/common/tables/trove-db_percona.xml43(td)
+#: ./doc/common/tables/trove-db_mongodb.xml39(td)
+#: ./doc/common/tables/trove-db_redis.xml39(td)
 msgid "(IntOpt) Timeout to wait for a guest to become active."
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml8(caption)
-#: ./doc/common/tables/trove-debug.xml8(caption)
-#: ./doc/common/tables/heat-debug.xml8(caption)
-msgid "Description of configuration options for debug"
+#: ./doc/common/tables/nova-periodic.xml8(caption)
+msgid "Description of configuration options for periodic"
+msgstr ""
+
+#: ./doc/common/tables/nova-periodic.xml22(td)
+msgid "periodic_enable = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-periodic.xml23(td)
+msgid "(BoolOpt) Enable periodic tasks"
+msgstr ""
+
+#: ./doc/common/tables/nova-periodic.xml26(td)
+#: ./doc/common/tables/cinder-common.xml130(td)
+msgid "periodic_fuzzy_delay = 60"
+msgstr ""
+
+#: ./doc/common/tables/nova-periodic.xml27(td)
+#: ./doc/common/tables/neutron-common.xml163(td)
+msgid ""
+"(IntOpt) Range of seconds to randomly delay when starting the periodic task "
+"scheduler to reduce stampeding. (Disable by setting to 0)"
+msgstr ""
+
+#: ./doc/common/tables/nova-periodic.xml30(td)
+#: ./doc/common/tables/cinder-common.xml158(td)
+#: ./doc/common/tables/neutron-api.xml54(td)
+msgid "run_external_periodic_tasks = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-periodic.xml31(td)
+#: ./doc/common/tables/cinder-common.xml159(td)
+#: ./doc/common/tables/neutron-api.xml55(td)
+msgid ""
+"(BoolOpt) Some periodic tasks can be run in a separate process. Should we "
+"run them here?"
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml8(caption)
+#: ./doc/common/tables/cinder-auth.xml8(caption)
+#: ./doc/common/tables/ceilometer-auth.xml8(caption)
+msgid "Description of configuration options for auth"
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml19(th)
+msgid "[auth]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml22(td)
+msgid "external = keystone.auth.plugins.external.DefaultDomain"
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml23(td)
+msgid "(StrOpt) The external (REMOTE_USER) auth plugin module."
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml26(td)
+msgid "methods = external, password, token"
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml27(td)
+msgid "(ListOpt) Default auth methods."
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml30(td)
+msgid "password = keystone.auth.plugins.password.Password"
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml31(td)
+msgid "(StrOpt) The password auth plugin module."
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml34(td)
+msgid "token = keystone.auth.plugins.token.Token"
+msgstr ""
+
+#: ./doc/common/tables/keystone-auth.xml35(td)
+msgid "(StrOpt) The token auth plugin module."
+msgstr ""
+
+#: ./doc/common/tables/keystone-policy.xml8(caption)
+#: ./doc/common/tables/neutron-policy.xml8(caption)
+#: ./doc/common/tables/nova-policy.xml8(caption)
+#: ./doc/common/tables/glance-policy.xml8(caption)
+msgid "Description of configuration options for policy"
+msgstr ""
+
+#: ./doc/common/tables/keystone-policy.xml22(td)
+#: ./doc/common/tables/nova-policy.xml58(td)
+#: ./doc/common/tables/glance-policy.xml22(td)
+#: ./doc/common/tables/ceilometer-api.xml34(td)
+#: ./doc/common/tables/heat-api.xml42(td)
+#: ./doc/common/tables/cinder-common.xml138(td)
+msgid "policy_default_rule = default"
+msgstr ""
+
+#: ./doc/common/tables/keystone-policy.xml23(td)
+#: ./doc/common/tables/ceilometer-api.xml35(td)
+#: ./doc/common/tables/heat-api.xml43(td)
+msgid "(StrOpt) Rule enforced when requested rule is not found"
+msgstr ""
+
+#: ./doc/common/tables/keystone-policy.xml26(td)
+#: ./doc/common/tables/neutron-policy.xml26(td)
+#: ./doc/common/tables/nova-policy.xml62(td)
+#: ./doc/common/tables/glance-policy.xml26(td)
+#: ./doc/common/tables/ceilometer-api.xml38(td)
+#: ./doc/common/tables/heat-api.xml46(td)
+#: ./doc/common/tables/cinder-common.xml142(td)
+msgid "policy_file = policy.json"
+msgstr ""
+
+#: ./doc/common/tables/keystone-policy.xml27(td)
+#: ./doc/common/tables/ceilometer-api.xml39(td)
+#: ./doc/common/tables/heat-api.xml47(td)
+msgid "(StrOpt) JSON file containing policy"
+msgstr ""
+
+#: ./doc/common/tables/keystone-policy.xml30(th)
+msgid "[policy]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-policy.xml33(td)
+msgid "driver = keystone.policy.backends.sql.Policy"
+msgstr ""
+
+#: ./doc/common/tables/keystone-policy.xml34(td)
+msgid "(StrOpt) Keystone Policy backend driver."
+msgstr ""
+
+#: ./doc/common/tables/keystone-policy.xml37(td)
+#: ./doc/common/tables/keystone-api.xml46(td)
+#: ./doc/common/tables/keystone-identity.xml38(td)
+#: ./doc/common/tables/keystone-catalog.xml26(td)
+#: ./doc/common/tables/keystone-assignment.xml34(td)
+msgid "list_limit = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-policy.xml38(td)
+msgid ""
+"(IntOpt) Maximum number of entities that will be returned in a policy "
+"collection."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml8(caption)
+#: ./doc/common/tables/neutron-auth_token.xml8(caption)
+#: ./doc/common/tables/heat-auth_token.xml8(caption)
+#: ./doc/common/tables/nova-auth_token.xml8(caption)
+#: ./doc/common/tables/cinder-auth_token.xml8(caption)
+#: ./doc/common/tables/keystone-auth_token.xml8(caption)
+#: ./doc/common/tables/trove-auth_token.xml8(caption)
+msgid "Description of configuration options for auth_token"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml22(td)
+#: ./doc/common/tables/glance-auth_token.xml117(td)
+#: ./doc/common/tables/ceilometer-common.xml38(td)
+#: ./doc/common/tables/neutron-auth_token.xml22(td)
+#: ./doc/common/tables/neutron-auth_token.xml117(td)
+#: ./doc/common/tables/ceilometer-auth.xml117(td)
+#: ./doc/common/tables/nova-common.xml50(td)
+#: ./doc/common/tables/heat-auth_token.xml22(td)
+#: ./doc/common/tables/heat-auth_token.xml117(td)
+#: ./doc/common/tables/nova-auth_token.xml110(td)
+#: ./doc/common/tables/cinder-auth_token.xml22(td)
+#: ./doc/common/tables/cinder-auth_token.xml117(td)
+#: ./doc/common/tables/keystone-auth_token.xml22(td)
+#: ./doc/common/tables/keystone-auth_token.xml117(td)
+#: ./doc/common/tables/trove-auth_token.xml22(td)
+#: ./doc/common/tables/trove-auth_token.xml117(td)
+msgid "memcached_servers = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml23(td)
+#: ./doc/common/tables/ceilometer-common.xml39(td)
+#: ./doc/common/tables/neutron-auth_token.xml23(td)
+#: ./doc/common/tables/nova-common.xml51(td)
+#: ./doc/common/tables/heat-auth_token.xml23(td)
+#: ./doc/common/tables/cinder-auth_token.xml23(td)
+#: ./doc/common/tables/keystone-auth_token.xml23(td)
+#: ./doc/common/tables/trove-auth_token.xml23(td)
+msgid "(ListOpt) Memcached servers or None for in process cache."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml26(th)
+#: ./doc/common/tables/neutron-auth_token.xml26(th)
+#: ./doc/common/tables/ceilometer-auth.xml26(th)
+#: ./doc/common/tables/heat-auth_token.xml26(th)
+#: ./doc/common/tables/nova-auth_token.xml19(th)
+#: ./doc/common/tables/cinder-auth_token.xml26(th)
+#: ./doc/common/tables/keystone-auth_token.xml26(th)
+#: ./doc/common/tables/trove-auth_token.xml26(th)
+msgid "[keystone_authtoken]"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml29(td)
+#: ./doc/common/tables/neutron-auth_token.xml29(td)
+#: ./doc/common/tables/ceilometer-auth.xml29(td)
+#: ./doc/common/tables/glance-registry.xml22(td)
+#: ./doc/common/tables/heat-auth_token.xml29(td)
+#: ./doc/common/tables/nova-auth_token.xml22(td)
+#: ./doc/common/tables/cinder-auth_token.xml29(td)
+#: ./doc/common/tables/keystone-auth_token.xml29(td)
+#: ./doc/common/tables/neutron-embrane_lb.xml22(td)
+#: ./doc/common/tables/trove-auth_token.xml29(td)
+#: ./doc/common/tables/neutron-common.xml22(td)
+#: ./doc/common/tables/neutron-common.xml192(td)
+#: ./doc/common/tables/neutron-common.xml219(td)
+msgid "admin_password = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml30(td)
+#: ./doc/common/tables/neutron-auth_token.xml30(td)
+#: ./doc/common/tables/ceilometer-auth.xml30(td)
+#: ./doc/common/tables/heat-auth_token.xml30(td)
+#: ./doc/common/tables/nova-auth_token.xml23(td)
+#: ./doc/common/tables/cinder-auth_token.xml30(td)
+#: ./doc/common/tables/keystone-auth_token.xml30(td)
+#: ./doc/common/tables/trove-auth_token.xml30(td)
+msgid "(StrOpt) Keystone account password"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml33(td)
+#: ./doc/common/tables/neutron-auth_token.xml33(td)
+#: ./doc/common/tables/ceilometer-auth.xml33(td)
+#: ./doc/common/tables/heat-auth_token.xml33(td)
+#: ./doc/common/tables/nova-auth_token.xml26(td)
+#: ./doc/common/tables/cinder-auth_token.xml33(td)
+#: ./doc/common/tables/keystone-auth_token.xml33(td)
+#: ./doc/common/tables/trove-auth_token.xml33(td)
+msgid "admin_tenant_name = admin"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml34(td)
+#: ./doc/common/tables/neutron-auth_token.xml34(td)
+#: ./doc/common/tables/ceilometer-auth.xml34(td)
+#: ./doc/common/tables/heat-auth_token.xml34(td)
+#: ./doc/common/tables/nova-auth_token.xml27(td)
+#: ./doc/common/tables/cinder-auth_token.xml34(td)
+#: ./doc/common/tables/keystone-auth_token.xml34(td)
+#: ./doc/common/tables/trove-auth_token.xml34(td)
+msgid "(StrOpt) Keystone service account tenant name to validate user tokens"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml37(td)
+#: ./doc/common/tables/neutron-auth_token.xml37(td)
+#: ./doc/common/tables/ceilometer-auth.xml37(td)
+#: ./doc/common/tables/heat-auth_token.xml37(td)
+#: ./doc/common/tables/nova-auth_token.xml30(td)
+#: ./doc/common/tables/cinder-auth_token.xml37(td)
+#: ./doc/common/tables/keystone-auth_token.xml37(td)
+#: ./doc/common/tables/trove-auth_token.xml37(td)
+msgid "admin_token = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml38(td)
+#: ./doc/common/tables/neutron-auth_token.xml38(td)
+#: ./doc/common/tables/ceilometer-auth.xml38(td)
+#: ./doc/common/tables/heat-auth_token.xml38(td)
+#: ./doc/common/tables/nova-auth_token.xml31(td)
+#: ./doc/common/tables/cinder-auth_token.xml38(td)
+#: ./doc/common/tables/keystone-auth_token.xml38(td)
+#: ./doc/common/tables/trove-auth_token.xml38(td)
+msgid ""
+"(StrOpt) Single shared secret with the Keystone configuration used for "
+"bootstrapping a Keystone installation, or otherwise bypassing the normal "
+"authentication process."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml41(td)
+#: ./doc/common/tables/neutron-auth_token.xml41(td)
+#: ./doc/common/tables/ceilometer-auth.xml41(td)
+#: ./doc/common/tables/glance-registry.xml30(td)
+#: ./doc/common/tables/heat-auth_token.xml41(td)
+#: ./doc/common/tables/nova-auth_token.xml34(td)
+#: ./doc/common/tables/cinder-auth_token.xml41(td)
+#: ./doc/common/tables/keystone-auth_token.xml41(td)
+#: ./doc/common/tables/trove-auth_token.xml41(td)
+#: ./doc/common/tables/neutron-common.xml30(td)
+#: ./doc/common/tables/neutron-common.xml200(td)
+msgid "admin_user = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml42(td)
+#: ./doc/common/tables/neutron-auth_token.xml42(td)
+#: ./doc/common/tables/ceilometer-auth.xml42(td)
+#: ./doc/common/tables/heat-auth_token.xml42(td)
+#: ./doc/common/tables/nova-auth_token.xml35(td)
+#: ./doc/common/tables/cinder-auth_token.xml42(td)
+#: ./doc/common/tables/keystone-auth_token.xml42(td)
+#: ./doc/common/tables/trove-auth_token.xml42(td)
+msgid "(StrOpt) Keystone account username"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml45(td)
+#: ./doc/common/tables/neutron-auth_token.xml45(td)
+#: ./doc/common/tables/ceilometer-auth.xml45(td)
+#: ./doc/common/tables/heat-auth_token.xml45(td)
+#: ./doc/common/tables/nova-auth_token.xml38(td)
+#: ./doc/common/tables/cinder-auth_token.xml45(td)
+#: ./doc/common/tables/keystone-auth_token.xml45(td)
+#: ./doc/common/tables/trove-auth_token.xml45(td)
+msgid "auth_admin_prefix ="
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml46(td)
+#: ./doc/common/tables/neutron-auth_token.xml46(td)
+#: ./doc/common/tables/ceilometer-auth.xml46(td)
+#: ./doc/common/tables/heat-auth_token.xml46(td)
+#: ./doc/common/tables/nova-auth_token.xml39(td)
+#: ./doc/common/tables/cinder-auth_token.xml46(td)
+#: ./doc/common/tables/keystone-auth_token.xml46(td)
+#: ./doc/common/tables/trove-auth_token.xml46(td)
+msgid "(StrOpt) Prefix to prepend at the beginning of the path"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml49(td)
+#: ./doc/common/tables/neutron-auth_token.xml49(td)
+#: ./doc/common/tables/ceilometer-auth.xml49(td)
+#: ./doc/common/tables/heat-auth_token.xml49(td)
+#: ./doc/common/tables/nova-auth_token.xml42(td)
+#: ./doc/common/tables/cinder-auth_token.xml49(td)
+#: ./doc/common/tables/keystone-auth_token.xml49(td)
+#: ./doc/common/tables/trove-auth_token.xml49(td)
+msgid "auth_host = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml50(td)
+#: ./doc/common/tables/neutron-auth_token.xml50(td)
+#: ./doc/common/tables/ceilometer-auth.xml50(td)
+#: ./doc/common/tables/heat-auth_token.xml50(td)
+#: ./doc/common/tables/nova-auth_token.xml43(td)
+#: ./doc/common/tables/cinder-auth_token.xml50(td)
+#: ./doc/common/tables/keystone-auth_token.xml50(td)
+#: ./doc/common/tables/trove-auth_token.xml50(td)
+msgid "(StrOpt) Host providing the admin Identity API endpoint"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml53(td)
+#: ./doc/common/tables/neutron-auth_token.xml53(td)
+#: ./doc/common/tables/ceilometer-auth.xml53(td)
+#: ./doc/common/tables/heat-auth_token.xml53(td)
+#: ./doc/common/tables/nova-auth_token.xml46(td)
+#: ./doc/common/tables/cinder-auth_token.xml53(td)
+#: ./doc/common/tables/keystone-auth_token.xml53(td)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml21(td)
+#: ./doc/common/tables/trove-auth_token.xml53(td)
+msgid "auth_port = 35357"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml54(td)
+#: ./doc/common/tables/neutron-auth_token.xml54(td)
+#: ./doc/common/tables/ceilometer-auth.xml54(td)
+#: ./doc/common/tables/heat-auth_token.xml54(td)
+#: ./doc/common/tables/nova-auth_token.xml47(td)
+#: ./doc/common/tables/cinder-auth_token.xml54(td)
+#: ./doc/common/tables/keystone-auth_token.xml54(td)
+#: ./doc/common/tables/trove-auth_token.xml54(td)
+msgid "(IntOpt) Port of the admin Identity API endpoint"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml57(td)
+#: ./doc/common/tables/neutron-auth_token.xml57(td)
+#: ./doc/common/tables/ceilometer-auth.xml57(td)
+#: ./doc/common/tables/heat-auth_token.xml57(td)
+#: ./doc/common/tables/nova-auth_token.xml50(td)
+#: ./doc/common/tables/cinder-auth_token.xml57(td)
+#: ./doc/common/tables/keystone-auth_token.xml57(td)
+#: ./doc/common/tables/trove-auth_token.xml57(td)
+msgid "auth_protocol = https"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml58(td)
+#: ./doc/common/tables/neutron-auth_token.xml58(td)
+#: ./doc/common/tables/ceilometer-auth.xml58(td)
+#: ./doc/common/tables/heat-auth_token.xml58(td)
+#: ./doc/common/tables/nova-auth_token.xml51(td)
+#: ./doc/common/tables/cinder-auth_token.xml58(td)
+#: ./doc/common/tables/keystone-auth_token.xml58(td)
+#: ./doc/common/tables/trove-auth_token.xml58(td)
+msgid "(StrOpt) Protocol of the admin Identity API endpoint(http or https)"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml61(td)
+#: ./doc/common/tables/neutron-auth_token.xml61(td)
+#: ./doc/common/tables/ceilometer-auth.xml61(td)
+#: ./doc/common/tables/heat-auth_token.xml61(td)
+#: ./doc/common/tables/nova-auth_token.xml54(td)
+#: ./doc/common/tables/heat-api.xml92(td)
+#: ./doc/common/tables/cinder-auth_token.xml61(td)
+#: ./doc/common/tables/keystone-auth_token.xml61(td)
+#: ./doc/common/tables/trove-auth_token.xml61(td)
+msgid "auth_uri = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml62(td)
+#: ./doc/common/tables/neutron-auth_token.xml62(td)
+#: ./doc/common/tables/ceilometer-auth.xml62(td)
+#: ./doc/common/tables/heat-auth_token.xml62(td)
+#: ./doc/common/tables/nova-auth_token.xml55(td)
+#: ./doc/common/tables/cinder-auth_token.xml62(td)
+#: ./doc/common/tables/keystone-auth_token.xml62(td)
+#: ./doc/common/tables/trove-auth_token.xml62(td)
+msgid "(StrOpt) Complete public Identity API endpoint"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml65(td)
+#: ./doc/common/tables/neutron-auth_token.xml65(td)
+#: ./doc/common/tables/ceilometer-auth.xml65(td)
+#: ./doc/common/tables/heat-auth_token.xml65(td)
+#: ./doc/common/tables/nova-auth_token.xml58(td)
+#: ./doc/common/tables/cinder-auth_token.xml65(td)
+#: ./doc/common/tables/keystone-auth_token.xml65(td)
+#: ./doc/common/tables/trove-auth_token.xml65(td)
+msgid "auth_version = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml66(td)
+#: ./doc/common/tables/neutron-auth_token.xml66(td)
+#: ./doc/common/tables/ceilometer-auth.xml66(td)
+#: ./doc/common/tables/heat-auth_token.xml66(td)
+#: ./doc/common/tables/nova-auth_token.xml59(td)
+#: ./doc/common/tables/cinder-auth_token.xml66(td)
+#: ./doc/common/tables/keystone-auth_token.xml66(td)
+#: ./doc/common/tables/trove-auth_token.xml66(td)
+msgid "(StrOpt) API version of the admin Identity API endpoint"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml69(td)
+#: ./doc/common/tables/neutron-auth_token.xml69(td)
+#: ./doc/common/tables/ceilometer-auth.xml69(td)
+#: ./doc/common/tables/heat-auth_token.xml69(td)
+#: ./doc/common/tables/nova-auth_token.xml62(td)
+#: ./doc/common/tables/cinder-auth_token.xml69(td)
+#: ./doc/common/tables/keystone-auth_token.xml69(td)
+#: ./doc/common/tables/trove-auth_token.xml69(td)
+msgid "cache = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml70(td)
+#: ./doc/common/tables/neutron-auth_token.xml70(td)
+#: ./doc/common/tables/ceilometer-auth.xml70(td)
+#: ./doc/common/tables/heat-auth_token.xml70(td)
+#: ./doc/common/tables/nova-auth_token.xml63(td)
+#: ./doc/common/tables/cinder-auth_token.xml70(td)
+#: ./doc/common/tables/keystone-auth_token.xml70(td)
+#: ./doc/common/tables/trove-auth_token.xml70(td)
+msgid "(StrOpt) Env key for the swift cache"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml73(td)
+#: ./doc/common/tables/neutron-auth_token.xml73(td)
+#: ./doc/common/tables/ceilometer-auth.xml73(td)
+#: ./doc/common/tables/heat-auth_token.xml73(td)
+#: ./doc/common/tables/nova-auth_token.xml66(td)
+#: ./doc/common/tables/cinder-auth_token.xml73(td)
+#: ./doc/common/tables/keystone-auth_token.xml73(td)
+#: ./doc/common/tables/trove-auth_token.xml73(td)
+msgid "cafile = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml74(td)
+#: ./doc/common/tables/neutron-auth_token.xml74(td)
+#: ./doc/common/tables/ceilometer-auth.xml74(td)
+#: ./doc/common/tables/heat-auth_token.xml74(td)
+#: ./doc/common/tables/nova-auth_token.xml67(td)
+#: ./doc/common/tables/cinder-auth_token.xml74(td)
+#: ./doc/common/tables/keystone-auth_token.xml74(td)
+#: ./doc/common/tables/trove-auth_token.xml74(td)
+msgid ""
+"(StrOpt) A PEM encoded Certificate Authority to use when verifying HTTPs "
+"connections. Defaults to system CAs."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml77(td)
+#: ./doc/common/tables/neutron-auth_token.xml77(td)
+#: ./doc/common/tables/ceilometer-auth.xml77(td)
+#: ./doc/common/tables/heat-auth_token.xml77(td)
+#: ./doc/common/tables/nova-auth_token.xml70(td)
+#: ./doc/common/tables/cinder-auth_token.xml77(td)
+#: ./doc/common/tables/keystone-auth_token.xml77(td)
+#: ./doc/common/tables/trove-auth_token.xml77(td)
+msgid "certfile = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml78(td)
+#: ./doc/common/tables/glance-auth_token.xml106(td)
+#: ./doc/common/tables/neutron-auth_token.xml78(td)
+#: ./doc/common/tables/neutron-auth_token.xml106(td)
+#: ./doc/common/tables/ceilometer-auth.xml78(td)
+#: ./doc/common/tables/ceilometer-auth.xml106(td)
+#: ./doc/common/tables/heat-auth_token.xml78(td)
+#: ./doc/common/tables/heat-auth_token.xml106(td)
+#: ./doc/common/tables/nova-auth_token.xml71(td)
+#: ./doc/common/tables/nova-auth_token.xml99(td)
+#: ./doc/common/tables/cinder-auth_token.xml78(td)
+#: ./doc/common/tables/cinder-auth_token.xml106(td)
+#: ./doc/common/tables/keystone-auth_token.xml78(td)
+#: ./doc/common/tables/keystone-auth_token.xml106(td)
+#: ./doc/common/tables/trove-auth_token.xml78(td)
+#: ./doc/common/tables/trove-auth_token.xml106(td)
+msgid "(StrOpt) Required if Keystone server requires client certificate"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml81(td)
+#: ./doc/common/tables/neutron-auth_token.xml81(td)
+#: ./doc/common/tables/ceilometer-auth.xml81(td)
+#: ./doc/common/tables/heat-auth_token.xml81(td)
+#: ./doc/common/tables/nova-auth_token.xml74(td)
+#: ./doc/common/tables/cinder-auth_token.xml81(td)
+#: ./doc/common/tables/keystone-auth_token.xml81(td)
+#: ./doc/common/tables/trove-auth_token.xml81(td)
+msgid "delay_auth_decision = False"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml82(td)
+#: ./doc/common/tables/neutron-auth_token.xml82(td)
+#: ./doc/common/tables/ceilometer-auth.xml82(td)
+#: ./doc/common/tables/heat-auth_token.xml82(td)
+#: ./doc/common/tables/nova-auth_token.xml75(td)
+#: ./doc/common/tables/cinder-auth_token.xml82(td)
+#: ./doc/common/tables/keystone-auth_token.xml82(td)
+#: ./doc/common/tables/trove-auth_token.xml82(td)
+msgid ""
+"(BoolOpt) Do not handle authorization requests within the middleware, but "
+"delegate the authorization decision to downstream WSGI components"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml85(td)
+#: ./doc/common/tables/neutron-auth_token.xml85(td)
+#: ./doc/common/tables/ceilometer-auth.xml85(td)
+#: ./doc/common/tables/heat-auth_token.xml85(td)
+#: ./doc/common/tables/nova-auth_token.xml78(td)
+#: ./doc/common/tables/cinder-auth_token.xml85(td)
+#: ./doc/common/tables/keystone-auth_token.xml85(td)
+#: ./doc/common/tables/trove-auth_token.xml85(td)
+#: ./doc/common/tables/keystone-token.xml38(td)
+msgid "enforce_token_bind = permissive"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml86(td)
+#: ./doc/common/tables/neutron-auth_token.xml86(td)
+#: ./doc/common/tables/ceilometer-auth.xml86(td)
+#: ./doc/common/tables/heat-auth_token.xml86(td)
+#: ./doc/common/tables/nova-auth_token.xml79(td)
+#: ./doc/common/tables/cinder-auth_token.xml86(td)
+#: ./doc/common/tables/keystone-auth_token.xml86(td)
+#: ./doc/common/tables/trove-auth_token.xml86(td)
+msgid ""
+"(StrOpt) Used to control the use and type of token binding. Can be set to: "
+"\"disabled\" to not check token binding. \"permissive\" (default) to "
+"validate binding information if the bind type is of a form known to the "
+"server and ignore it if not. \"strict\" like \"permissive\" but if the bind "
+"type is unknown the token will be rejected. \"required\" any form of token "
+"binding is needed to be allowed. Finally the name of a binding method that "
+"must be present in tokens."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml89(td)
+#: ./doc/common/tables/neutron-auth_token.xml89(td)
+#: ./doc/common/tables/ceilometer-auth.xml89(td)
+#: ./doc/common/tables/heat-auth_token.xml89(td)
+#: ./doc/common/tables/nova-auth_token.xml82(td)
+#: ./doc/common/tables/cinder-auth_token.xml89(td)
+#: ./doc/common/tables/keystone-auth_token.xml89(td)
+#: ./doc/common/tables/trove-auth_token.xml89(td)
+msgid "http_connect_timeout = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml90(td)
+#: ./doc/common/tables/neutron-auth_token.xml90(td)
+#: ./doc/common/tables/ceilometer-auth.xml90(td)
+#: ./doc/common/tables/heat-auth_token.xml90(td)
+#: ./doc/common/tables/nova-auth_token.xml83(td)
+#: ./doc/common/tables/cinder-auth_token.xml90(td)
+#: ./doc/common/tables/keystone-auth_token.xml90(td)
+#: ./doc/common/tables/trove-auth_token.xml90(td)
+msgid ""
+"(BoolOpt) Request timeout value for communicating with Identity API server."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml93(td)
+#: ./doc/common/tables/neutron-auth_token.xml93(td)
+#: ./doc/common/tables/ceilometer-auth.xml93(td)
+#: ./doc/common/tables/heat-auth_token.xml93(td)
+#: ./doc/common/tables/nova-auth_token.xml86(td)
+#: ./doc/common/tables/cinder-auth_token.xml93(td)
+#: ./doc/common/tables/keystone-auth_token.xml93(td)
+#: ./doc/common/tables/trove-auth_token.xml93(td)
+msgid "http_request_max_retries = 3"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml94(td)
+#: ./doc/common/tables/neutron-auth_token.xml94(td)
+#: ./doc/common/tables/ceilometer-auth.xml94(td)
+#: ./doc/common/tables/heat-auth_token.xml94(td)
+#: ./doc/common/tables/nova-auth_token.xml87(td)
+#: ./doc/common/tables/cinder-auth_token.xml94(td)
+#: ./doc/common/tables/keystone-auth_token.xml94(td)
+#: ./doc/common/tables/trove-auth_token.xml94(td)
+msgid ""
+"(IntOpt) How many times are we trying to reconnect when communicating with "
+"Identity API Server."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml97(td)
+#: ./doc/common/tables/neutron-auth_token.xml97(td)
+#: ./doc/common/tables/ceilometer-auth.xml97(td)
+#: ./doc/common/tables/heat-auth_token.xml97(td)
+#: ./doc/common/tables/nova-auth_token.xml90(td)
+#: ./doc/common/tables/cinder-auth_token.xml97(td)
+#: ./doc/common/tables/keystone-auth_token.xml97(td)
+#: ./doc/common/tables/trove-auth_token.xml97(td)
+msgid "include_service_catalog = True"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml98(td)
+#: ./doc/common/tables/neutron-auth_token.xml98(td)
+#: ./doc/common/tables/ceilometer-auth.xml98(td)
+#: ./doc/common/tables/heat-auth_token.xml98(td)
+#: ./doc/common/tables/nova-auth_token.xml91(td)
+#: ./doc/common/tables/cinder-auth_token.xml98(td)
+#: ./doc/common/tables/keystone-auth_token.xml98(td)
+#: ./doc/common/tables/trove-auth_token.xml98(td)
+msgid ""
+"(BoolOpt) (optional) indicate whether to set the X-Service-Catalog header. "
+"If False, middleware will not ask for service catalog on token validation "
+"and will not set the X-Service-Catalog header."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml102(td)
+#: ./doc/common/tables/neutron-auth_token.xml102(td)
+#: ./doc/common/tables/ceilometer-auth.xml102(td)
+#: ./doc/common/tables/heat-auth_token.xml102(td)
+#: ./doc/common/tables/nova-auth_token.xml95(td)
+#: ./doc/common/tables/cinder-auth_token.xml102(td)
+#: ./doc/common/tables/keystone-auth_token.xml102(td)
+#: ./doc/common/tables/trove-auth_token.xml102(td)
+msgid "(BoolOpt) Verify HTTPS connections."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml105(td)
+#: ./doc/common/tables/neutron-auth_token.xml105(td)
+#: ./doc/common/tables/ceilometer-auth.xml105(td)
+#: ./doc/common/tables/heat-auth_token.xml105(td)
+#: ./doc/common/tables/nova-auth_token.xml98(td)
+#: ./doc/common/tables/cinder-auth_token.xml105(td)
+#: ./doc/common/tables/keystone-auth_token.xml105(td)
+#: ./doc/common/tables/trove-auth_token.xml105(td)
+msgid "keyfile = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml109(td)
+#: ./doc/common/tables/neutron-auth_token.xml109(td)
+#: ./doc/common/tables/ceilometer-auth.xml109(td)
+#: ./doc/common/tables/heat-auth_token.xml109(td)
+#: ./doc/common/tables/nova-auth_token.xml102(td)
+#: ./doc/common/tables/cinder-auth_token.xml109(td)
+#: ./doc/common/tables/keystone-auth_token.xml109(td)
+#: ./doc/common/tables/trove-auth_token.xml109(td)
+msgid "memcache_secret_key = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml110(td)
+#: ./doc/common/tables/neutron-auth_token.xml110(td)
+#: ./doc/common/tables/ceilometer-auth.xml110(td)
+#: ./doc/common/tables/heat-auth_token.xml110(td)
+#: ./doc/common/tables/nova-auth_token.xml103(td)
+#: ./doc/common/tables/cinder-auth_token.xml110(td)
+#: ./doc/common/tables/keystone-auth_token.xml110(td)
+#: ./doc/common/tables/trove-auth_token.xml110(td)
+msgid ""
+"(StrOpt) (optional, mandatory if memcache_security_strategy is defined) this"
+" string is used for key derivation."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml113(td)
+#: ./doc/common/tables/neutron-auth_token.xml113(td)
+#: ./doc/common/tables/ceilometer-auth.xml113(td)
+#: ./doc/common/tables/heat-auth_token.xml113(td)
+#: ./doc/common/tables/nova-auth_token.xml106(td)
+#: ./doc/common/tables/cinder-auth_token.xml113(td)
+#: ./doc/common/tables/keystone-auth_token.xml113(td)
+#: ./doc/common/tables/trove-auth_token.xml113(td)
+msgid "memcache_security_strategy = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml114(td)
+#: ./doc/common/tables/neutron-auth_token.xml114(td)
+#: ./doc/common/tables/ceilometer-auth.xml114(td)
+#: ./doc/common/tables/heat-auth_token.xml114(td)
+#: ./doc/common/tables/nova-auth_token.xml107(td)
+#: ./doc/common/tables/cinder-auth_token.xml114(td)
+#: ./doc/common/tables/keystone-auth_token.xml114(td)
+#: ./doc/common/tables/trove-auth_token.xml114(td)
+msgid ""
+"(StrOpt) (optional) if defined, indicate whether token data should be "
+"authenticated or authenticated and encrypted. Acceptable values are MAC or "
+"ENCRYPT. If MAC, token data is authenticated (with HMAC) in the cache. If "
+"ENCRYPT, token data is encrypted and authenticated in the cache. If the "
+"value is not one of these options or empty, auth_token will raise an "
+"exception on initialization."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml118(td)
+#: ./doc/common/tables/neutron-auth_token.xml118(td)
+#: ./doc/common/tables/ceilometer-auth.xml118(td)
+#: ./doc/common/tables/heat-auth_token.xml118(td)
+#: ./doc/common/tables/nova-auth_token.xml111(td)
+#: ./doc/common/tables/cinder-auth_token.xml118(td)
+#: ./doc/common/tables/keystone-auth_token.xml118(td)
+#: ./doc/common/tables/trove-auth_token.xml118(td)
+msgid ""
+"(ListOpt) Optionally specify a list of memcached server(s) to use for "
+"caching. If left undefined, tokens will instead be cached in-process."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml121(td)
+#: ./doc/common/tables/neutron-auth_token.xml121(td)
+#: ./doc/common/tables/ceilometer-auth.xml121(td)
+#: ./doc/common/tables/heat-auth_token.xml121(td)
+#: ./doc/common/tables/nova-auth_token.xml114(td)
+#: ./doc/common/tables/cinder-auth_token.xml121(td)
+#: ./doc/common/tables/keystone-auth_token.xml121(td)
+#: ./doc/common/tables/trove-auth_token.xml121(td)
+msgid "revocation_cache_time = 300"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml122(td)
+#: ./doc/common/tables/neutron-auth_token.xml122(td)
+#: ./doc/common/tables/ceilometer-auth.xml122(td)
+#: ./doc/common/tables/heat-auth_token.xml122(td)
+#: ./doc/common/tables/nova-auth_token.xml115(td)
+#: ./doc/common/tables/cinder-auth_token.xml122(td)
+#: ./doc/common/tables/keystone-auth_token.xml122(td)
+#: ./doc/common/tables/trove-auth_token.xml122(td)
+msgid ""
+"(IntOpt) Determines the frequency at which the list of revoked tokens is "
+"retrieved from the Identity service (in seconds). A high number of "
+"revocation events combined with a low cache duration may significantly "
+"reduce performance."
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml125(td)
+#: ./doc/common/tables/neutron-auth_token.xml125(td)
+#: ./doc/common/tables/ceilometer-auth.xml125(td)
+#: ./doc/common/tables/heat-auth_token.xml125(td)
+#: ./doc/common/tables/nova-auth_token.xml118(td)
+#: ./doc/common/tables/cinder-auth_token.xml125(td)
+#: ./doc/common/tables/keystone-auth_token.xml125(td)
+#: ./doc/common/tables/trove-auth_token.xml125(td)
+msgid "signing_dir = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml126(td)
+#: ./doc/common/tables/neutron-auth_token.xml126(td)
+#: ./doc/common/tables/ceilometer-auth.xml126(td)
+#: ./doc/common/tables/heat-auth_token.xml126(td)
+#: ./doc/common/tables/nova-auth_token.xml119(td)
+#: ./doc/common/tables/cinder-auth_token.xml126(td)
+#: ./doc/common/tables/keystone-auth_token.xml126(td)
+#: ./doc/common/tables/trove-auth_token.xml126(td)
+msgid "(StrOpt) Directory used to cache files related to PKI tokens"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml129(td)
+#: ./doc/common/tables/neutron-auth_token.xml129(td)
+#: ./doc/common/tables/ceilometer-auth.xml129(td)
+#: ./doc/common/tables/heat-auth_token.xml129(td)
+#: ./doc/common/tables/nova-auth_token.xml122(td)
+#: ./doc/common/tables/cinder-auth_token.xml129(td)
+#: ./doc/common/tables/keystone-auth_token.xml129(td)
+#: ./doc/common/tables/trove-auth_token.xml129(td)
+msgid "token_cache_time = 300"
+msgstr ""
+
+#: ./doc/common/tables/glance-auth_token.xml130(td)
+#: ./doc/common/tables/neutron-auth_token.xml130(td)
+#: ./doc/common/tables/ceilometer-auth.xml130(td)
+#: ./doc/common/tables/heat-auth_token.xml130(td)
+#: ./doc/common/tables/nova-auth_token.xml123(td)
+#: ./doc/common/tables/cinder-auth_token.xml130(td)
+#: ./doc/common/tables/keystone-auth_token.xml130(td)
+#: ./doc/common/tables/trove-auth_token.xml130(td)
+msgid ""
+"(IntOpt) In order to prevent excessive effort spent validating tokens, the "
+"middleware caches previously-seen tokens for a configurable duration (in "
+"seconds). Set to -1 to disable caching completely."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml8(caption)
+msgid "Description of configuration options for netapp_7mode_nfs"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml22(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml22(td)
+msgid "expiry_thres_minutes = 720"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml23(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml23(td)
+msgid ""
+"(IntOpt) This option specifies the threshold for last access time for images"
+" in the NFS image cache. When a cache cleaning cycle begins, images in the "
+"cache that have not been accessed in the last M minutes, where M is the "
+"value of this parameter, will be deleted from the cache to create free space"
+" on the NFS share."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml26(td)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml26(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml22(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml22(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml30(td)
+msgid "netapp_login = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml27(td)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml27(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml23(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml23(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml31(td)
+msgid ""
+"(StrOpt) Administrative user account name used to access the storage system "
+"or proxy server."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml30(td)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml30(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml26(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml26(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml34(td)
+msgid "netapp_password = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml31(td)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml31(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml27(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml27(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml35(td)
+msgid ""
+"(StrOpt) Password for the administrative user account specified in the "
+"netapp_login option."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml34(td)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml38(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml30(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml30(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml38(td)
+msgid "netapp_server_hostname = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml35(td)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml39(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml31(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml31(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml39(td)
+msgid ""
+"(StrOpt) The hostname (or IP address) for the storage system or proxy "
+"server."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml38(td)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml42(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml34(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml34(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml42(td)
+msgid "netapp_server_port = 80"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml39(td)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml43(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml35(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml35(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml43(td)
+msgid ""
+"(IntOpt) The TCP port to use for communication with the storage system or "
+"proxy server. Traditionally, port 80 is used for HTTP and port 443 is used "
+"for HTTPS; however, this value should be changed if an alternate port has "
+"been configured on the storage system or proxy server."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml42(td)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml46(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml42(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml42(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml46(td)
+msgid "netapp_storage_family = ontap_cluster"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml43(td)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml47(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml43(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml43(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml47(td)
+msgid ""
+"(StrOpt) The storage family type used on the storage system; valid values "
+"are ontap_7mode for using Data ONTAP operating in 7-Mode, ontap_cluster for "
+"using clustered Data ONTAP, or eseries for using E-Series."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml46(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml46(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml46(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml50(td)
+msgid "netapp_storage_protocol = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml47(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml47(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml47(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml51(td)
+msgid ""
+"(StrOpt) The storage protocol to be used on the data path with the storage "
+"system; valid values are iscsi or nfs."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml50(td)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml54(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml50(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml50(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml54(td)
+msgid "netapp_transport_type = http"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml51(td)
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml55(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml51(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml51(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml55(td)
+msgid ""
+"(StrOpt) The transport protocol used when communicating with the storage "
+"system or proxy server. Valid values are http or https."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml54(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml62(td)
+msgid "thres_avl_size_perc_start = 20"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml55(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml63(td)
+msgid ""
+"(IntOpt) If the percentage of available space for an NFS share has dropped "
+"below the value specified by this option, the NFS image cache will be "
+"cleaned."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml58(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml66(td)
+msgid "thres_avl_size_perc_stop = 60"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml59(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml67(td)
+msgid ""
+"(IntOpt) When the percentage of available space on an NFS share has reached "
+"the percentage specified by this option, the driver will stop clearing files"
+" from the NFS image cache that have not been accessed in the last M minutes,"
+" where M is the value of the expiry_thres_minutes configuration option."
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml7(literal)
+msgid "[container-sync]"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml7(literal)
+#: ./doc/common/tables/swift-container-server-container-auditor.xml7(literal)
+#: ./doc/common/tables/swift-container-server-filter-recon.xml7(literal)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml7(literal)
+#: ./doc/common/tables/swift-container-server-pipeline-main.xml7(literal)
+#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml7(literal)
+#: ./doc/common/tables/swift-container-server-container-updater.xml7(literal)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml7(literal)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml7(literal)
+msgid "container-server.conf-sample"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml7(caption)
+#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml7(caption)
+#: ./doc/common/tables/swift-container-server-container-auditor.xml7(caption)
+#: ./doc/common/tables/swift-swift-swift-constraints.xml7(caption)
+#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml7(caption)
+#: ./doc/common/tables/swift-container-server-filter-recon.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml7(caption)
+#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml7(caption)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml7(caption)
+#: ./doc/common/tables/swift-container-server-pipeline-main.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml7(caption)
+#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml7(caption)
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml7(caption)
+#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml7(caption)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml7(caption)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml7(caption)
+#: ./doc/common/tables/swift-rsyncd-container.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml7(caption)
+#: ./doc/common/tables/swift-rsyncd-account.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml7(caption)
+#: ./doc/common/tables/swift-account-server-filter-recon.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml7(caption)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml7(caption)
+#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml7(caption)
+#: ./doc/common/tables/swift-container-server-container-updater.xml7(caption)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml7(caption)
+#: ./doc/common/tables/swift-swift-swift-hash.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml7(caption)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml7(caption)
+#: ./doc/common/tables/swift-object-server-pipeline-main.xml7(caption)
+#: ./doc/common/tables/swift-memcache-memcache.xml7(caption)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml7(caption)
+#: ./doc/common/tables/swift-object-expirer-filter-cache.xml7(caption)
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml7(caption)
+#: ./doc/common/tables/swift-object-server-object-auditor.xml7(caption)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml7(caption)
+#: ./doc/common/tables/swift-account-server-pipeline-main.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml7(caption)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml7(caption)
+#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml7(caption)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml7(caption)
+#: ./doc/common/tables/swift-object-server-filter-recon.xml7(caption)
+#: ./doc/common/tables/swift-rsyncd-object.xml7(caption)
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml7(caption)
+#: ./doc/common/tables/swift-object-server-object-updater.xml7(caption)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml7(caption)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml7(caption)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml7(caption)
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml7(caption)
+#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml7(caption)
+msgid ""
+"Description of configuration options for <placeholder-1/> in "
+"<placeholder-2/>"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml18(td)
+msgid "log_name = container-sync"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml70(td)
+#: ./doc/common/tables/swift-container-server-container-auditor.xml18(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml61(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml64(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml18(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml18(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml18(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml24(td)
+#: ./doc/common/tables/swift-object-server-object-auditor.xml18(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml18(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml18(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml18(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml58(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml18(td)
+msgid "Label used when logging"
+msgstr "ログ取得するときに使用するラベル"
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml73(td)
+#: ./doc/common/tables/swift-container-server-container-auditor.xml21(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml64(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml67(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml21(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml21(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml21(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml27(td)
+#: ./doc/common/tables/swift-object-server-object-auditor.xml21(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml21(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml21(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml33(td)
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml21(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml21(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml61(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml21(td)
+msgid "log_facility = LOG_LOCAL0"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml73(td)
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml24(td)
+#: ./doc/common/tables/swift-container-server-container-auditor.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml24(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml64(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml24(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml67(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml24(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml21(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml21(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml21(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml27(td)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml24(td)
+#: ./doc/common/tables/swift-object-server-object-auditor.xml21(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml24(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml21(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml21(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml33(td)
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml21(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml21(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml61(td)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml24(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml21(td)
+msgid "Syslog log facility"
+msgstr "Syslog ログファシリティ"
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml76(td)
+#: ./doc/common/tables/swift-container-server-container-auditor.xml24(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml67(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml70(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml24(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml24(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml24(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml30(td)
+#: ./doc/common/tables/swift-object-server-object-auditor.xml24(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml24(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml24(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml36(td)
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml24(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml24(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml64(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml24(td)
+msgid "log_level = INFO"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml76(td)
+#: ./doc/common/tables/swift-container-server-container-auditor.xml24(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml67(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml70(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml24(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml24(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml24(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml30(td)
+#: ./doc/common/tables/swift-object-server-object-auditor.xml24(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml24(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml24(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml36(td)
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml24(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml24(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml64(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml24(td)
+msgid "Logging level"
+msgstr "ログレベル"
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml82(td)
+#: ./doc/common/tables/swift-container-server-container-auditor.xml27(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml70(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml73(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml27(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml27(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml27(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml33(td)
+#: ./doc/common/tables/swift-object-server-object-auditor.xml27(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml27(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml27(td)
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml27(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml27(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml67(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml27(td)
+msgid "log_address = /dev/log"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml82(td)
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml33(td)
+#: ./doc/common/tables/swift-container-server-container-auditor.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml30(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml70(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml33(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml73(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml33(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml27(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml27(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml27(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml33(td)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml33(td)
+#: ./doc/common/tables/swift-object-server-object-auditor.xml27(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml33(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml27(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml27(td)
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml27(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml27(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml67(td)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml33(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml27(td)
+msgid "Location where syslog sends the logs to"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml30(td)
+msgid "sync_proxy = http://10.1.1.1:8888,http://10.1.1.2:8888"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml30(td)
+msgid "If you need to use an HTTP proxy, set it here. Defaults to no proxy."
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml33(td)
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml18(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml30(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml30(td)
+msgid "interval = 300"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml33(td)
+#: ./doc/common/tables/swift-container-server-container-auditor.xml30(td)
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml18(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml42(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml30(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml42(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml30(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml30(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml33(td)
+msgid "Minimum time for a pass to take"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml36(td)
+msgid "container_time = 60"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-sync.xml36(td)
+msgid "Maximum amount of time to spend syncing each container"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml7(literal)
+msgid "proxy-server.conf-sample"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml18(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml18(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml18(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml18(td)
+msgid "bind_ip = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml18(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml18(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml18(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml18(td)
+msgid "IP Address for server to bind to"
+msgstr "サーバーがバインドする IP アドレス"
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml21(td)
+msgid "bind_port = 80"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml21(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml21(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml21(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml21(td)
+msgid "Port for server to bind to"
+msgstr "サーバーがバインドするポート"
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml24(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml24(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml24(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml24(td)
+msgid "bind_timeout = 30"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml24(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml24(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml24(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml24(td)
+msgid "Seconds to attempt bind before giving up"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml27(td)
+#: ./doc/common/tables/heat-cfn_api.xml33(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml27(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml27(td)
+#: ./doc/common/tables/heat-api.xml103(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml29(td)
+#: ./doc/common/tables/neutron-wsgi.xml22(td)
+#: ./doc/common/tables/glance-common.xml30(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml27(td)
+#: ./doc/common/tables/trove-debug.xml26(td)
+msgid "backlog = 4096"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml27(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml27(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml27(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml27(td)
+msgid "Maximum number of allowed pending TCP connections"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml30(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml33(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml33(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml18(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml45(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml33(td)
+msgid "swift_dir = /etc/swift"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml30(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml33(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml33(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml18(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml45(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml33(td)
+msgid "Swift configuration directory"
+msgstr "Swift 設定ディレクトリー"
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml33(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml30(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml30(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml21(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml30(td)
+msgid "user = swift"
+msgstr "user = swift"
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml33(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml30(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml30(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml21(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml30(td)
+msgid "User to run as"
+msgstr "実行するユーザー"
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml36(td)
+msgid "expose_info = true"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml36(td)
+msgid "Enables exposing configuration settings via HTTP GET /info."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml39(td)
+msgid "admin_key = secret_admin_key"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml39(td)
+msgid ""
+"to use for admin calls that are HMAC signed. Default is empty, which will "
+"disable admin calls to /info. the proxy server. For most cases, this should "
+"be `egg:swift#proxy`. request whenever it has to failover to a handoff node"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml42(td)
+msgid "disallowed_sections = container_quotas, tempurl"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml42(td)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml64(td)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml67(td)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml79(td)
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml85(td)
+#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml18(td)
+#: ./doc/common/tables/neutron-rootwrap.xml50(td)
+#: ./doc/common/tables/neutron-rootwrap.xml54(td)
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml36(td)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml39(td)
+#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml18(td)
+#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml57(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml81(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml87(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml90(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml93(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml96(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml102(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml105(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml108(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml111(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml114(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml58(td)
+#: ./doc/common/tables/swift-container-server-pipeline-main.xml18(td)
+#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml21(td)
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml24(td)
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml27(td)
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml33(td)
+#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml24(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml45(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml48(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml45(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml51(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml54(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml57(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml60(td)
+#: ./doc/common/tables/swift-rsyncd-container.xml18(td)
+#: ./doc/common/tables/swift-rsyncd-container.xml21(td)
+#: ./doc/common/tables/swift-rsyncd-container.xml24(td)
+#: ./doc/common/tables/swift-rsyncd-container.xml27(td)
+#: ./doc/common/tables/swift-rsyncd-account.xml18(td)
+#: ./doc/common/tables/swift-rsyncd-account.xml21(td)
+#: ./doc/common/tables/swift-rsyncd-account.xml24(td)
+#: ./doc/common/tables/swift-rsyncd-account.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml57(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml60(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml63(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml66(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml69(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml72(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml75(td)
+#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml18(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml45(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml51(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml75(td)
+#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml36(td)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml39(td)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml42(td)
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml45(td)
+#: ./doc/common/tables/swift-object-server-pipeline-main.xml18(td)
+#: ./doc/common/tables/swift-memcache-memcache.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml36(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml39(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml42(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml45(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml48(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml51(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml54(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml57(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml60(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml72(td)
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml18(td)
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml21(td)
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml24(td)
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml27(td)
+#: ./doc/common/tables/swift-object-server-object-auditor.xml45(td)
+#: ./doc/common/tables/swift-account-server-pipeline-main.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml36(td)
+#: ./doc/common/tables/swift-object-server-filter-recon.xml24(td)
+#: ./doc/common/tables/swift-rsyncd-object.xml18(td)
+#: ./doc/common/tables/swift-rsyncd-object.xml21(td)
+#: ./doc/common/tables/swift-rsyncd-object.xml24(td)
+#: ./doc/common/tables/swift-rsyncd-object.xml27(td)
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml39(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml24(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml33(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml42(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml48(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml51(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml57(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml60(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml63(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml66(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml69(td)
+#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml21(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml45(td)
+#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml21(td)
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml18(td)
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml21(td)
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml24(td)
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml21(td)
+msgid "No help text available for this option."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml45(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml45(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml51(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml45(td)
+msgid "workers = auto"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml45(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml45(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml51(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml45(td)
+msgid ""
+"a much higher value, one can reduce the impact of slow file system "
+"operations in one request from negatively impacting other requests."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml48(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml48(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml54(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml48(td)
+msgid "max_clients = 1024"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml48(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml48(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml54(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml48(td)
+msgid ""
+"Maximum number of clients one worker can process simultaneously Lowering the"
+" number of clients handled per worker, and raising the number of workers can"
+" lessen the impact that a CPU intensive, or blocking, request can have on "
+"other requests served by the same worker. If the maximum number of clients "
+"is set to one, then a given worker will not perform another call while "
+"processing, allowing other workers a chance to process it."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml58(td)
+msgid "cert_file = /etc/swift/proxy.crt"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml58(td)
+msgid "to the ssl .crt. This should be enabled for testing purposes only."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml61(td)
+msgid "key_file = /etc/swift/proxy.key"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml61(td)
+msgid "to the ssl .key. This should be enabled for testing purposes only."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml64(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml45(td)
+msgid "expiring_objects_container_divisor = 86400"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml67(td)
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml24(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml48(td)
+msgid "expiring_objects_account_name = expiring_objects"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml70(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml61(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml64(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml24(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml58(td)
+msgid "log_name = swift"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml79(td)
+msgid "log_headers = false"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml85(td)
+msgid "trans_id_suffix ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml88(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml73(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml76(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml36(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml70(td)
+msgid "log_custom_handlers ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml88(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml73(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml76(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml36(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml70(td)
+msgid ""
+"Comma-separated list of functions to call to setup custom log handlers."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml91(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml76(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml79(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml39(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml73(td)
+msgid "log_udp_host ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml91(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml76(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml79(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml39(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml73(td)
+msgid "If not set, the UDB receiver for syslog is disabled."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml94(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml79(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml82(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml42(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml76(td)
+msgid "log_udp_port = 514"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml94(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml79(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml82(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml42(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml76(td)
+msgid "Port value for UDB receiver, if enabled."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml97(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml82(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml85(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml45(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml79(td)
+msgid "log_statsd_host = localhost"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml97(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml82(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml85(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml45(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml79(td)
+msgid "If not set, the StatsD feature is disabled."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml100(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml85(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml88(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml48(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml82(td)
+msgid "log_statsd_port = 8125"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml100(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml85(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml88(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml48(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml82(td)
+msgid "Port value for the StatsD server."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml103(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml88(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml91(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml51(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml85(td)
+msgid "log_statsd_default_sample_rate = 1.0"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml103(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml88(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml91(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml51(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml85(td)
+msgid ""
+"Defines the probability of sending a sample for any given event or timing "
+"measurement."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml107(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml92(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml95(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml55(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml89(td)
+msgid "log_statsd_sample_rate_factor = 1.0"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml107(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml92(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml95(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml55(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml89(td)
+msgid ""
+"Not recommended to set this to a value less than 1.0, if frequency of "
+"logging is too high, tune the log_statsd_default_sample_rate instead."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml112(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml97(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml100(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml60(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml94(td)
+msgid "log_statsd_metric_prefix ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml112(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml97(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml100(td)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml60(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml94(td)
+msgid "Value will be prepended to every metric sent to the StatsD server."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml115(td)
+msgid "cors_allow_origin ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml115(td)
+msgid ""
+"is a list of hosts that are included with any CORS request by default and "
+"returned with the Access-Control-Allow-Origin header in addition to what the"
+" container has set. to call to setup custom log handlers. for eventlet the "
+"proxy server. For most cases, this should be `egg:swift#proxy`. request "
+"whenever it has to failover to a handoff node"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml118(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml115(td)
+msgid "client_timeout = 60"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml118(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml115(td)
+msgid "Timeout to read one chunk from a client external services"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml121(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml103(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml103(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml100(td)
+msgid "eventlet_debug = false"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml121(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml103(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml103(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml100(td)
+msgid "If true, turn on debug logging for eventlet"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml8(caption)
+msgid "Description of configuration options for zoning_fabric"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml19(th)
+msgid "[BRCD_FABRIC_EXAMPLE]"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml22(td)
+msgid "fc_fabric_address ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml23(td)
+msgid "(StrOpt) Management IP of fabric"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml26(td)
+msgid "fc_fabric_password ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml27(td)
+msgid "(StrOpt) Password for user"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml30(td)
+msgid "fc_fabric_port = 22"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml31(td)
+msgid "(IntOpt) Connecting port"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml34(td)
+msgid "fc_fabric_user ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml35(td)
+msgid "(StrOpt) Fabric user ID"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml38(td)
+msgid "principal_switch_wwn = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml39(td)
+msgid "(StrOpt) Principal switch WWN of the fabric"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml42(td)
+msgid "zone_activate = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml43(td)
+msgid "(BoolOpt) overridden zoning activation state"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml46(td)
+msgid "zone_name_prefix = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml47(td)
+msgid "(StrOpt) overridden zone name prefix"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml50(td)
+#: ./doc/common/tables/cinder-zoning.xml33(td)
+msgid "zoning_policy = initiator-target"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_fabric.xml51(td)
+msgid "(StrOpt) overridden zoning policy"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-redis.xml8(caption)
+#: ./doc/common/tables/neutron-redis.xml8(caption)
+#: ./doc/common/tables/nova-redis.xml8(caption)
+#: ./doc/common/tables/glance-redis.xml8(caption)
+#: ./doc/common/tables/heat-redis.xml8(caption)
+#: ./doc/common/tables/trove-redis.xml8(caption)
+#: ./doc/common/tables/keystone-redis.xml8(caption)
+msgid "Description of configuration options for redis"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-redis.xml22(td)
+#: ./doc/common/tables/nova-common.xml42(td)
+#: ./doc/common/tables/neutron-redis.xml22(td)
+#: ./doc/common/tables/cinder-common.xml58(td)
+#: ./doc/common/tables/heat-redis.xml22(td)
+msgid "host = oslo"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-redis.xml23(td)
+msgid ""
+"(StrOpt) Name of this node, which must be valid in an AMQP key. Can be an "
+"opaque identifier. For ZeroMQ only, must be a valid host name, FQDN, or IP "
+"address."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-redis.xml34(th)
+#: ./doc/common/tables/neutron-redis.xml26(th)
+#: ./doc/common/tables/heat-redis.xml26(th)
+#: ./doc/common/tables/trove-redis.xml19(th)
+msgid "[matchmaker_redis]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-redis.xml37(td)
+#: ./doc/common/tables/neutron-redis.xml29(td)
+#: ./doc/common/tables/glance-redis.xml22(td)
+#: ./doc/common/tables/heat-redis.xml29(td)
+#: ./doc/common/tables/trove-redis.xml22(td)
+#: ./doc/common/tables/neutron-nec.xml38(td)
+#: ./doc/common/tables/keystone-redis.xml22(td)
+msgid "host = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-redis.xml38(td)
+#: ./doc/common/tables/neutron-redis.xml30(td)
+#: ./doc/common/tables/heat-redis.xml30(td)
+#: ./doc/common/tables/trove-redis.xml23(td)
+msgid "(StrOpt) Host to locate redis"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-redis.xml41(td)
+#: ./doc/common/tables/neutron-redis.xml33(td)
+#: ./doc/common/tables/nova-redis.xml22(td)
+#: ./doc/common/tables/keystone-ldap.xml90(td)
+#: ./doc/common/tables/glance-redis.xml26(td)
+#: ./doc/common/tables/cinder-rpc.xml82(td)
+#: ./doc/common/tables/heat-redis.xml33(td)
+#: ./doc/common/tables/neutron-ml2_ncs.xml22(td)
+#: ./doc/common/tables/neutron-ml2_odl.xml22(td)
+#: ./doc/common/tables/trove-redis.xml26(td)
+#: ./doc/common/tables/keystone-redis.xml34(td)
+msgid "password = None"
+msgstr "password = None"
+
+#: ./doc/common/tables/ceilometer-redis.xml42(td)
+#: ./doc/common/tables/neutron-redis.xml34(td)
+#: ./doc/common/tables/heat-redis.xml34(td)
+#: ./doc/common/tables/trove-redis.xml27(td)
+msgid "(StrOpt) Password for Redis server. (optional)"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-redis.xml45(td)
+#: ./doc/common/tables/nova-common.xml74(td)
+#: ./doc/common/tables/neutron-redis.xml37(td)
+#: ./doc/common/tables/glance-redis.xml30(td)
+#: ./doc/common/tables/cinder-rpc.xml86(td)
+#: ./doc/common/tables/heat-redis.xml37(td)
+#: ./doc/common/tables/trove-redis.xml30(td)
+#: ./doc/common/tables/keystone-redis.xml38(td)
+msgid "port = 6379"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-redis.xml46(td)
+#: ./doc/common/tables/nova-common.xml75(td)
+#: ./doc/common/tables/neutron-redis.xml38(td)
+#: ./doc/common/tables/glance-redis.xml31(td)
+#: ./doc/common/tables/cinder-rpc.xml87(td)
+#: ./doc/common/tables/heat-redis.xml38(td)
+#: ./doc/common/tables/trove-redis.xml31(td)
+#: ./doc/common/tables/keystone-redis.xml39(td)
+msgid "(IntOpt) Use this port to connect to redis host."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml8(caption)
+msgid "Description of configuration options for storage_ceph"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml22(td)
+msgid "rbd_ceph_conf ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml23(td)
+msgid "(StrOpt) path to the ceph configuration file to use"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml26(td)
+msgid "rbd_flatten_volume_from_snapshot = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml27(td)
+msgid "(BoolOpt) flatten volumes created from snapshots to remove dependency"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml30(td)
+msgid "rbd_max_clone_depth = 5"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml31(td)
+msgid ""
+"(IntOpt) maximum number of nested clones that can be taken of a volume "
+"before enforcing a flatten prior to next clone. A value of zero disables "
+"cloning"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml34(td)
+msgid "rbd_pool = rbd"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml35(td)
+msgid "(StrOpt) the RADOS pool in which rbd volumes are stored"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml38(td)
+#: ./doc/common/tables/nova-volumes.xml115(td)
+msgid "rbd_secret_uuid = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml39(td)
+msgid "(StrOpt) the libvirt uuid of the secret for the rbd_uservolumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml42(td)
+#: ./doc/common/tables/nova-volumes.xml119(td)
+msgid "rbd_user = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml43(td)
+msgid ""
+"(StrOpt) the RADOS client name for accessing rbd volumes - only set when "
+"using cephx authentication"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml46(td)
+msgid "volume_tmp_dir = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_ceph.xml47(td)
+msgid ""
+"(StrOpt) where to store temporary image files if the volume driver does not "
+"write them directly to the volume"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml8(caption)
+#: ./doc/common/tables/nova-vmware.xml8(caption)
+#: ./doc/common/tables/neutron-vmware.xml8(caption)
+#: ./doc/common/tables/glance-vmware.xml8(caption)
+#: ./doc/common/tables/cinder-vmware.xml8(caption)
+msgid "Description of configuration options for vmware"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml19(th)
+#: ./doc/common/tables/nova-vnc.xml42(th)
+#: ./doc/common/tables/nova-vmware.xml19(th)
+#: ./doc/common/tables/nova-network.xml254(th)
+msgid "[vmware]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml22(td)
+#: ./doc/common/tables/nova-vmware.xml22(td)
+msgid "api_retry_count = 10"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml23(td)
+msgid "(IntOpt) Number of times a VMware Vsphere API must be retried"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml26(td)
+msgid "host_ip ="
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml27(td)
+msgid "(StrOpt) IP address of the VMware Vsphere host"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml30(td)
+msgid "host_password ="
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml31(td)
+msgid "(StrOpt) Password of VMware Vsphere"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml34(td)
+msgid "host_username ="
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml35(td)
+msgid "(StrOpt) Username of VMware Vsphere"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml38(td)
+#: ./doc/common/tables/nova-vmware.xml54(td)
+msgid "task_poll_interval = 0.5"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-vmware.xml39(td)
+msgid "(FloatOpt) Sleep time in seconds for polling an ongoing async task"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml8(caption)
+msgid "Description of configuration options for cisco"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml19(th)
+msgid "[CISCO]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml22(td)
+msgid ""
+"model_class = "
+"neutron.plugins.cisco.models.virt_phy_sw_v2.VirtualPhysicalSwitchModelV2"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml23(td)
+msgid "(StrOpt) Model Class"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml26(td)
+msgid ""
+"nexus_driver = "
+"neutron.plugins.cisco.test.nexus.fake_nexus_driver.CiscoNEXUSFakeDriver"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml27(td)
+msgid "(StrOpt) Nexus Driver Name"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml30(td)
+msgid "nexus_l3_enable = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml31(td)
+msgid "(BoolOpt) Enable L3 support on the Nexus switches"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml34(td)
+msgid "provider_vlan_auto_create = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml35(td)
+msgid ""
+"(BoolOpt) Provider VLANs are automatically created as needed on the Nexus "
+"switch"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml38(td)
+msgid "provider_vlan_auto_trunk = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml39(td)
+msgid ""
+"(BoolOpt) Provider VLANs are automatically trunked as needed on the ports of"
+" the Nexus switch"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml42(td)
+msgid "provider_vlan_name_prefix = p-"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml43(td)
+msgid "(StrOpt) VLAN Name prefix for provider vlans"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml46(td)
+#: ./doc/common/tables/neutron-cisco.xml122(td)
+msgid "svi_round_robin = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml47(td)
+#: ./doc/common/tables/neutron-cisco.xml123(td)
+msgid "(BoolOpt) Distribute SVI interfaces over all switches"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml50(td)
+#: ./doc/common/tables/neutron-cisco.xml126(td)
+msgid "vlan_name_prefix = q-"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml51(td)
+#: ./doc/common/tables/neutron-cisco.xml127(td)
+msgid "(StrOpt) VLAN Name prefix"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml58(td)
+msgid "(StrOpt) N1K Bridge Mappings"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml61(td)
+msgid "default_network_profile = default_network_profile"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml62(td)
+msgid "(StrOpt) N1K default network profile"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml65(td)
+msgid "default_policy_profile = service_profile"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml66(td)
+msgid "(StrOpt) N1K default policy profile"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml69(td)
+msgid "enable_tunneling = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml70(td)
+msgid "(BoolOpt) N1K Enable Tunneling"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml74(td)
+msgid "(StrOpt) N1K Integration Bridge"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml77(td)
+msgid "network_node_policy_profile = dhcp_pp"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml78(td)
+msgid "(StrOpt) N1K policy profile for network node"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml81(td)
+msgid "network_vlan_ranges = vlan:1:4095"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml82(td)
+msgid "(StrOpt) N1K Network VLAN Ranges"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml85(td)
+msgid "poll_duration = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml86(td)
+msgid "(StrOpt) N1K Policy profile polling duration in seconds"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml90(td)
+msgid "(StrOpt) N1K Tenant Network Type"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml94(td)
+msgid "(StrOpt) N1K Tunnel Bridge"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml97(td)
+msgid "vxlan_id_ranges = 5000:10000"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml98(td)
+msgid "(StrOpt) N1K VXLAN ID Ranges"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml101(th)
+msgid "[CISCO_PLUGINS]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml104(td)
+msgid ""
+"nexus_plugin = neutron.plugins.cisco.nexus.cisco_nexus_plugin_v2.NexusPlugin"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml105(td)
+msgid "(StrOpt) Nexus Switch to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml108(td)
+msgid ""
+"vswitch_plugin = "
+"neutron.plugins.openvswitch.ovs_neutron_plugin.OVSNeutronPluginV2"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml109(td)
+msgid "(StrOpt) Virtual Switch to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml112(th)
+msgid "[cisco_csr_ipsec]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml115(td)
+msgid "status_check_interval = 60"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml116(td)
+msgid "(IntOpt) Status check interval for Cisco CSR IPSec connections"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cisco.xml119(th)
+#: ./doc/common/tables/neutron-ml2_cisco.xml19(th)
+msgid "[ml2_cisco]"
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml8(caption)
+#: ./doc/common/tables/neutron-testing.xml8(caption)
+#: ./doc/common/tables/glance-testing.xml8(caption)
+msgid "Description of configuration options for testing"
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml22(td)
+#: ./doc/common/tables/keystone-rpc.xml22(td)
+#: ./doc/common/tables/cinder-rpc.xml22(td)
+msgid ""
+"allowed_rpc_exception_modules = oslo.messaging.exceptions, nova.exception, "
+"cinder.exception, exceptions"
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml23(td)
+#: ./doc/common/tables/keystone-rpc.xml23(td)
+#: ./doc/common/tables/ceilometer-rpc.xml23(td)
+#: ./doc/common/tables/cinder-rpc.xml23(td)
+#: ./doc/common/tables/heat-rpc.xml23(td)
+#: ./doc/common/tables/neutron-common.xml39(td)
+msgid ""
+"(ListOpt) Modules of exceptions that are permitted to be recreated upon "
+"receiving exception data from an rpc call."
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml22(td)
 #: ./doc/common/tables/nova-testing.xml26(td)
-#: ./doc/common/tables/trove-debug.xml22(td)
-#: ./doc/common/tables/cinder-api.xml30(td)
-#: ./doc/common/tables/glance-wsgi.xml22(td)
-#: ./doc/common/tables/heat-debug.xml22(td)
 #: ./doc/common/tables/ceilometer-common.xml22(td)
+#: ./doc/common/tables/cinder-api.xml30(td)
+#: ./doc/common/tables/heat-debug.xml22(td)
 #: ./doc/common/tables/neutron-testing.xml22(td)
+#: ./doc/common/tables/glance-wsgi.xml22(td)
+#: ./doc/common/tables/trove-debug.xml22(td)
+#: ./doc/common/tables/keystone-debug.xml22(td)
 msgid "backdoor_port = None"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml23(td)
-#: ./doc/common/tables/trove-debug.xml23(td)
+#: ./doc/common/tables/nova-testing.xml27(td)
+msgid ""
+"(StrOpt) Enable eventlet backdoor. Acceptable values are 0, &lt;port&gt; and"
+" &lt;start&gt;:&lt;end&gt;, where 0 results in listening on a random tcp "
+"port number, &lt;port&gt; results in listening on the specified port number "
+"and not enabling backdoorif it is in use and &lt;start&gt;:&lt;end&gt; "
+"results in listening on the smallest unused port number within the specified"
+" range of port numbers. The chosen port is displayed in the service's log "
+"file."
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml30(td)
+msgid "fake_call = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml31(td)
+msgid "(BoolOpt) If True, skip using the queue and make local calls"
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml34(td)
+msgid "fake_network = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml35(td)
+msgid "(BoolOpt) If passed, use fake network devices and addresses"
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml38(td)
+#: ./doc/common/tables/trove-amqp.xml38(td)
+#: ./doc/common/tables/keystone-rabbit.xml22(td)
+#: ./doc/common/tables/heat-amqp.xml42(td)
+#: ./doc/common/tables/glance-rabbitmq.xml26(td)
+#: ./doc/common/tables/neutron-testing.xml26(td)
+#: ./doc/common/tables/cinder-rpc.xml42(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml22(td)
+msgid "fake_rabbit = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml39(td)
+#: ./doc/common/tables/keystone-rabbit.xml23(td)
+#: ./doc/common/tables/glance-rabbitmq.xml27(td)
+#: ./doc/common/tables/cinder-rpc.xml43(td)
+msgid "(BoolOpt) If passed, use a fake RabbitMQ provider."
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml42(td)
+#: ./doc/common/tables/cinder-common.xml110(td)
+msgid "monkey_patch = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml43(td)
+msgid "(BoolOpt) Whether to log monkey patching"
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml46(td)
+msgid ""
+"monkey_patch_modules = "
+"nova.api.ec2.cloud:nova.notifications.notify_decorator, "
+"nova.compute.api:nova.notifications.notify_decorator"
+msgstr ""
+
+#: ./doc/common/tables/nova-testing.xml47(td)
+#: ./doc/common/tables/cinder-common.xml115(td)
+msgid "(ListOpt) List of modules/decorators to monkey patch"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml8(caption)
+#: ./doc/common/tables/neutron-metadata.xml8(caption)
+msgid "Description of configuration options for metadata"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml22(td)
+msgid "metadata_host = $my_ip"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml23(td)
+msgid "(StrOpt) The IP address for the metadata API server"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml26(td)
+msgid "metadata_listen = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml27(td)
+msgid "(StrOpt) The IP address on which the metadata API will listen."
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml30(td)
+msgid "metadata_listen_port = 8775"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml31(td)
+msgid "(IntOpt) The port on which the metadata API will listen."
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml34(td)
+msgid "metadata_manager = nova.api.manager.MetadataManager"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml35(td)
+msgid "(StrOpt) OpenStack metadata service manager"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml38(td)
+msgid "metadata_port = 8775"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml39(td)
+msgid "(IntOpt) The port for the metadata API port"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml42(td)
+msgid "metadata_workers = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml43(td)
+msgid ""
+"(IntOpt) Number of workers for metadata service. The default will be the "
+"number of CPUs available."
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml46(td)
+msgid ""
+"vendordata_driver = nova.api.metadata.vendordata_json.JsonFileVendorData"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml47(td)
+msgid "(StrOpt) Driver to use for vendor data"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml50(td)
+msgid "vendordata_jsonfile_path = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-metadata.xml51(td)
+msgid "(StrOpt) File to load json formatted vendor data from"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_nova.xml8(caption)
+msgid "Description of configuration options for clients_nova"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_nova.xml19(th)
+msgid "[clients_nova]"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml8(caption)
+msgid "Description of configuration options for hp3par"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml22(td)
+msgid "hp3par_api_url ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml23(td)
+msgid ""
+"(StrOpt) 3PAR WSAPI Server Url like https://&lt;3par ip&gt;:8080/api/v1"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml26(td)
+msgid "hp3par_cpg = OpenStack"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml27(td)
+msgid "(StrOpt) The CPG to use for volume creation"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml30(td)
+msgid "hp3par_cpg_snap ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml31(td)
+msgid ""
+"(StrOpt) The CPG to use for Snapshots for volumes. If empty hp3par_cpg will "
+"be used"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml34(td)
+msgid "hp3par_debug = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml35(td)
+msgid "(BoolOpt) Enable HTTP debugging to 3PAR"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml38(td)
+msgid "hp3par_iscsi_ips ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml39(td)
+msgid "(ListOpt) List of target iSCSI addresses to use."
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml42(td)
+msgid "hp3par_password ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml43(td)
+msgid "(StrOpt) 3PAR Super user password"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml46(td)
+msgid "hp3par_snapshot_expiration ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml47(td)
+msgid ""
+"(StrOpt) The time in hours when a snapshot expires and is deleted. This must"
+" be larger than expiration"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml50(td)
+msgid "hp3par_snapshot_retention ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml51(td)
+msgid ""
+"(StrOpt) The time in hours to retain a snapshot. You can't delete it before "
+"this expires."
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml54(td)
+msgid "hp3par_username ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-hp3par.xml55(td)
+msgid "(StrOpt) 3PAR Super user username"
+msgstr ""
+
+#: ./doc/common/tables/keystone-misc.xml8(caption)
+msgid "Description of configuration options for misc"
+msgstr ""
+
+#: ./doc/common/tables/keystone-misc.xml22(td)
+#: ./doc/common/tables/ceilometer-common.xml34(td)
+#: ./doc/common/tables/nova-common.xml46(td)
+#: ./doc/common/tables/trove-common.xml58(td)
+#: ./doc/common/tables/cinder-common.xml70(td)
+#: ./doc/common/tables/heat-debug.xml38(td)
+#: ./doc/common/tables/glance-common.xml70(td)
+#: ./doc/common/tables/neutron-common.xml142(td)
+msgid "lock_path = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-misc.xml23(td)
+#: ./doc/common/tables/ceilometer-common.xml35(td)
+#: ./doc/common/tables/nova-common.xml47(td)
+#: ./doc/common/tables/trove-common.xml59(td)
+#: ./doc/common/tables/heat-debug.xml39(td)
+#: ./doc/common/tables/glance-common.xml71(td)
+#: ./doc/common/tables/neutron-common.xml143(td)
+msgid "(StrOpt) Directory to use for lock files."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml7(literal)
+msgid "[filter:cname_lookup]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml18(td)
+msgid "use = egg:swift#cname_lookup"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml18(td)
+#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml18(td)
+#: ./doc/common/tables/swift-container-server-filter-recon.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml18(td)
+#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml18(td)
+#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml18(td)
+#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml18(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml18(td)
+#: ./doc/common/tables/swift-account-server-filter-recon.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml18(td)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml18(td)
+#: ./doc/common/tables/swift-object-expirer-filter-cache.xml18(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml18(td)
+#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml18(td)
+#: ./doc/common/tables/swift-object-server-filter-recon.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml18(td)
+msgid "Entry point of paste.deploy in the server"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml21(td)
+msgid "set log_name = cname_lookup"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml21(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml21(td)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml21(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml21(td)
+msgid "Label to use when logging"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml24(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml24(td)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml24(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml24(td)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml24(td)
+msgid "set log_facility = LOG_LOCAL0"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml27(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml27(td)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml27(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml27(td)
+msgid "set log_level = INFO"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml27(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml27(td)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml27(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml27(td)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml27(td)
+msgid "Log level"
+msgstr "ログレベル"
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml30(td)
+msgid "set log_headers = false"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml30(td)
+msgid "If True, log headers in each request"
+msgstr "真ならば、各リクエストにおいてヘッダーを記録します。"
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml30(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml33(td)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml33(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml33(td)
+msgid "set log_address = /dev/log"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml36(td)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml36(td)
+msgid "storage_domain = example.com"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml36(td)
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml36(td)
+msgid ""
+"Domain that matches your cloud. Multiple domains can be specified using a "
+"comma-separated list."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml40(td)
+msgid "lookup_depth = 1"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml40(td)
+msgid ""
+"Because CNAMES can be recursive, specifies the number of levels through "
+"which to search."
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml8(caption)
+#: ./doc/common/tables/cinder-scheduler.xml8(caption)
+msgid "Description of configuration options for scheduler"
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml22(td)
+msgid "network_auto_schedule = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml23(td)
+msgid "(BoolOpt) Allow auto scheduling networks to DHCP agent."
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml26(td)
+msgid ""
+"network_scheduler_driver = "
+"neutron.scheduler.dhcp_agent_scheduler.ChanceScheduler"
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml27(td)
+msgid "(StrOpt) Driver to use for scheduling network to DHCP agent"
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml30(td)
+msgid "router_auto_schedule = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml31(td)
+msgid "(BoolOpt) Allow auto scheduling of routers to L3 agent."
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml34(td)
+msgid "router_delete_namespaces = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml35(td)
+msgid "(BoolOpt) Delete namespace after removing a router."
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml38(td)
+msgid ""
+"router_scheduler_driver = "
+"neutron.scheduler.l3_agent_scheduler.ChanceScheduler"
+msgstr ""
+
+#: ./doc/common/tables/neutron-scheduler.xml39(td)
+msgid "(StrOpt) Driver to use for scheduling router to a default L3 agent"
+msgstr ""
+
+#: ./doc/common/tables/glance-rbd.xml8(caption)
+msgid "Description of configuration options for rbd"
+msgstr ""
+
+#: ./doc/common/tables/glance-rbd.xml22(td)
+msgid "rbd_store_ceph_conf = /etc/ceph/ceph.conf"
+msgstr ""
+
+#: ./doc/common/tables/glance-rbd.xml23(td)
+msgid ""
+"(StrOpt) Ceph configuration file path. If &lt;None&gt;, librados will locate"
+" the default config. If using cephx authentication, this file should include"
+" a reference to the right keyring in a client.&lt;USER&gt; section."
+msgstr ""
+
+#: ./doc/common/tables/glance-rbd.xml26(td)
+msgid "rbd_store_chunk_size = 8"
+msgstr ""
+
+#: ./doc/common/tables/glance-rbd.xml27(td)
+msgid ""
+"(IntOpt) RADOS images will be chunked into objects of this size (in "
+"megabytes). For best performance, this should be a power of two."
+msgstr ""
+
+#: ./doc/common/tables/glance-rbd.xml30(td)
+msgid "rbd_store_pool = images"
+msgstr ""
+
+#: ./doc/common/tables/glance-rbd.xml31(td)
+msgid "(StrOpt) RADOS pool in which images are stored."
+msgstr ""
+
+#: ./doc/common/tables/glance-rbd.xml34(td)
+msgid "rbd_store_user = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-rbd.xml35(td)
+msgid ""
+"(StrOpt) RADOS user to authenticate as (only applicable if using Cephx. If "
+"&lt;None&gt;, a default will be chosen based on the client. section in "
+"rbd_store_ceph_conf)."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml8(caption)
+msgid "Description of configuration options for storage_xen"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml22(td)
+msgid "xenapi_connection_password = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml23(td)
+msgid "(StrOpt) Password for XenAPI connection"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml26(td)
+msgid "xenapi_connection_url = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml27(td)
+msgid "(StrOpt) URL for XenAPI connection"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml30(td)
+#: ./doc/common/tables/neutron-rootwrap.xml49(td)
+msgid "xenapi_connection_username = root"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml31(td)
+msgid "(StrOpt) Username for XenAPI connection"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml34(td)
+msgid "xenapi_nfs_server = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml35(td)
+msgid "(StrOpt) NFS server to be used by XenAPINFSDriver"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml38(td)
+msgid "xenapi_nfs_serverpath = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml39(td)
+msgid "(StrOpt) Path of exported NFS, used by XenAPINFSDriver"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml42(td)
+msgid "xenapi_sr_base_path = /var/run/sr-mount"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_xen.xml43(td)
+#: ./doc/common/tables/nova-xen.xml177(td)
+msgid "(StrOpt) Base path to the storage repository"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-common.xml8(caption)
+#: ./doc/common/tables/heat-common.xml8(caption)
+#: ./doc/common/tables/nova-common.xml8(caption)
+#: ./doc/common/tables/trove-common.xml8(caption)
+#: ./doc/common/tables/cinder-common.xml8(caption)
+#: ./doc/common/tables/glance-common.xml8(caption)
+#: ./doc/common/tables/neutron-common.xml8(caption)
+msgid "Description of configuration options for common"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-common.xml23(td)
 #: ./doc/common/tables/cinder-api.xml31(td)
 #: ./doc/common/tables/heat-debug.xml23(td)
-#: ./doc/common/tables/ceilometer-common.xml23(td)
 #: ./doc/common/tables/neutron-testing.xml23(td)
+#: ./doc/common/tables/trove-debug.xml23(td)
+#: ./doc/common/tables/keystone-debug.xml23(td)
 msgid ""
 "(StrOpt) Enable eventlet backdoor. Acceptable values are 0, &lt;port&gt;, "
 "and &lt;start&gt;:&lt;end&gt;, where 0 results in listening on a random tcp "
@@ -25577,256 +29279,615 @@ msgid ""
 "displayed in the service's log file."
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml26(td)
-#: ./doc/common/tables/trove-debug.xml30(td)
-#: ./doc/common/tables/glance-logging.xml22(td)
+#: ./doc/common/tables/ceilometer-common.xml26(td)
+#: ./doc/common/tables/nova-common.xml38(td)
+#: ./doc/common/tables/cinder-common.xml42(td)
+#: ./doc/common/tables/heat-debug.xml30(td)
+#: ./doc/common/tables/glance-common.xml46(td)
+#: ./doc/common/tables/neutron-common.xml122(td)
+#: ./doc/common/tables/trove-debug.xml34(td)
+#: ./doc/common/tables/keystone-debug.xml30(td)
+msgid "disable_process_locking = False"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-common.xml27(td)
+msgid "(BoolOpt) Whether to disable inter-process locks."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-common.xml30(td)
+#: ./doc/common/tables/neutron-logging.xml30(td)
+#: ./doc/common/tables/glance-logging.xml30(td)
+#: ./doc/common/tables/cinder-common.xml50(td)
+#: ./doc/common/tables/heat-debug.xml34(td)
+#: ./doc/common/tables/nova-logging.xml30(td)
+#: ./doc/common/tables/trove-debug.xml38(td)
+#: ./doc/common/tables/keystone-debug.xml34(td)
+msgid "fatal_deprecations = False"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-common.xml31(td)
+#: ./doc/common/tables/glance-logging.xml31(td)
+#: ./doc/common/tables/cinder-common.xml51(td)
+#: ./doc/common/tables/keystone-debug.xml35(td)
+msgid "(BoolOpt) Make deprecations fatal"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-common.xml42(td)
+msgid "notification_workers = 1"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-common.xml43(td)
+msgid ""
+"(IntOpt) Number of workers for notification service. A single notification "
+"agent is enabled by default."
+msgstr ""
+
+#: ./doc/common/tables/cinder-database.xml22(td)
+#: ./doc/common/tables/nova-baremetal.xml22(td)
+#: ./doc/common/tables/heat-database.xml22(td)
+msgid "db_backend = sqlalchemy"
+msgstr ""
+
+#: ./doc/common/tables/cinder-database.xml26(td)
+msgid "db_driver = cinder.db"
+msgstr ""
+
+#: ./doc/common/tables/cinder-database.xml27(td)
+msgid "(StrOpt) driver to use for database access"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml8(caption)
+#: ./doc/common/tables/neutron-logging.xml8(caption)
+#: ./doc/common/tables/glance-logging.xml8(caption)
+#: ./doc/common/tables/keystone-logging.xml8(caption)
+#: ./doc/common/tables/heat-logging.xml8(caption)
+#: ./doc/common/tables/nova-logging.xml8(caption)
+#: ./doc/common/tables/trove-logging.xml8(caption)
+msgid "Description of configuration options for logging"
+msgstr ""
+
 #: ./doc/common/tables/ceilometer-logging.xml22(td)
-#: ./doc/common/tables/heat-debug.xml26(td)
 #: ./doc/common/tables/neutron-logging.xml22(td)
-#: ./doc/common/tables/nova-logging.xml22(td)
+#: ./doc/common/tables/glance-logging.xml22(td)
 #: ./doc/common/tables/cinder-common.xml26(td)
+#: ./doc/common/tables/heat-debug.xml26(td)
+#: ./doc/common/tables/nova-logging.xml22(td)
+#: ./doc/common/tables/trove-debug.xml30(td)
+#: ./doc/common/tables/keystone-debug.xml26(td)
 msgid "debug = False"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml27(td)
-#: ./doc/common/tables/trove-debug.xml31(td)
-#: ./doc/common/tables/glance-logging.xml23(td)
 #: ./doc/common/tables/ceilometer-logging.xml23(td)
-#: ./doc/common/tables/heat-debug.xml27(td)
 #: ./doc/common/tables/neutron-logging.xml23(td)
-#: ./doc/common/tables/nova-logging.xml23(td)
+#: ./doc/common/tables/glance-logging.xml23(td)
 #: ./doc/common/tables/cinder-common.xml27(td)
+#: ./doc/common/tables/heat-debug.xml27(td)
+#: ./doc/common/tables/nova-logging.xml23(td)
+#: ./doc/common/tables/trove-debug.xml31(td)
+#: ./doc/common/tables/keystone-debug.xml27(td)
 msgid ""
 "(BoolOpt) Print debugging output (set logging level to DEBUG instead of "
 "default WARNING level)."
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml30(td)
-#: ./doc/common/tables/neutron-common.xml122(td)
-#: ./doc/common/tables/nova-common.xml38(td)
-#: ./doc/common/tables/trove-debug.xml34(td)
-#: ./doc/common/tables/heat-debug.xml30(td)
-#: ./doc/common/tables/glance-common.xml46(td)
-#: ./doc/common/tables/cinder-common.xml42(td)
-#: ./doc/common/tables/ceilometer-common.xml26(td)
-msgid "disable_process_locking = False"
+#: ./doc/common/tables/ceilometer-logging.xml26(td)
+#: ./doc/common/tables/glance-logging.xml26(td)
+#: ./doc/common/tables/keystone-logging.xml22(td)
+msgid ""
+"default_log_levels = amqp=WARN, amqplib=WARN, boto=WARN, qpid=WARN, "
+"sqlalchemy=WARN, suds=INFO, iso8601=WARN, "
+"requests.packages.urllib3.connectionpool=WARN"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml31(td)
-#: ./doc/common/tables/neutron-common.xml123(td)
-#: ./doc/common/tables/nova-common.xml39(td)
-#: ./doc/common/tables/trove-debug.xml35(td)
-#: ./doc/common/tables/heat-debug.xml31(td)
-#: ./doc/common/tables/glance-common.xml47(td)
-#: ./doc/common/tables/cinder-common.xml43(td)
-msgid "(BoolOpt) Whether to disable inter-process locks"
+#: ./doc/common/tables/ceilometer-logging.xml27(td)
+#: ./doc/common/tables/glance-logging.xml27(td)
+#: ./doc/common/tables/cinder-common.xml35(td)
+#: ./doc/common/tables/keystone-logging.xml23(td)
+msgid "(ListOpt) List of logger=LEVEL pairs"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml34(td)
-#: ./doc/common/tables/trove-debug.xml38(td)
-#: ./doc/common/tables/glance-logging.xml30(td)
-#: ./doc/common/tables/heat-debug.xml34(td)
-#: ./doc/common/tables/neutron-logging.xml30(td)
-#: ./doc/common/tables/nova-logging.xml30(td)
-#: ./doc/common/tables/cinder-common.xml50(td)
-#: ./doc/common/tables/ceilometer-common.xml30(td)
-msgid "fatal_deprecations = False"
+#: ./doc/common/tables/ceilometer-logging.xml30(td)
+#: ./doc/common/tables/nova-compute.xml54(td)
+#: ./doc/common/tables/heat-amqp.xml34(td)
+#: ./doc/common/tables/trove-common.xml42(td)
+#: ./doc/common/tables/neutron-notifier.xml22(td)
+msgid "default_notification_level = INFO"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml35(td)
-#: ./doc/common/tables/glance-logging.xml31(td)
-#: ./doc/common/tables/cinder-common.xml51(td)
-#: ./doc/common/tables/ceilometer-common.xml31(td)
-msgid "(BoolOpt) Make deprecations fatal"
+#: ./doc/common/tables/ceilometer-logging.xml31(td)
+#: ./doc/common/tables/nova-compute.xml55(td)
+#: ./doc/common/tables/heat-amqp.xml35(td)
+#: ./doc/common/tables/trove-common.xml43(td)
+#: ./doc/common/tables/neutron-notifier.xml23(td)
+msgid "(StrOpt) Default notification level for outgoing notifications"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml34(td)
+#: ./doc/common/tables/neutron-logging.xml34(td)
+#: ./doc/common/tables/glance-logging.xml34(td)
+#: ./doc/common/tables/keystone-logging.xml26(td)
+#: ./doc/common/tables/cinder-images.xml62(td)
+#: ./doc/common/tables/heat-logging.xml26(td)
+#: ./doc/common/tables/nova-logging.xml38(td)
+#: ./doc/common/tables/trove-logging.xml26(td)
+msgid "instance_format = \"[instance: %(uuid)s] \""
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml35(td)
+#: ./doc/common/tables/neutron-logging.xml35(td)
+#: ./doc/common/tables/glance-logging.xml35(td)
+#: ./doc/common/tables/keystone-logging.xml27(td)
+#: ./doc/common/tables/cinder-images.xml63(td)
+#: ./doc/common/tables/heat-logging.xml27(td)
+#: ./doc/common/tables/nova-logging.xml39(td)
+#: ./doc/common/tables/trove-logging.xml27(td)
+msgid ""
+"(StrOpt) If an instance is passed with the log message, format it like this"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml38(td)
+#: ./doc/common/tables/neutron-logging.xml38(td)
+#: ./doc/common/tables/glance-logging.xml38(td)
+#: ./doc/common/tables/keystone-logging.xml30(td)
+#: ./doc/common/tables/cinder-images.xml66(td)
+#: ./doc/common/tables/heat-logging.xml30(td)
+#: ./doc/common/tables/nova-logging.xml42(td)
+#: ./doc/common/tables/trove-logging.xml30(td)
+msgid "instance_uuid_format = \"[instance: %(uuid)s] \""
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml39(td)
+#: ./doc/common/tables/neutron-logging.xml39(td)
+#: ./doc/common/tables/glance-logging.xml39(td)
+#: ./doc/common/tables/keystone-logging.xml31(td)
+#: ./doc/common/tables/cinder-images.xml67(td)
+#: ./doc/common/tables/heat-logging.xml31(td)
+#: ./doc/common/tables/nova-logging.xml43(td)
+#: ./doc/common/tables/trove-logging.xml31(td)
+msgid ""
+"(StrOpt) If an instance UUID is passed with the log message, format it like "
+"this"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml42(td)
+#: ./doc/common/tables/neutron-logging.xml42(td)
+#: ./doc/common/tables/glance-logging.xml42(td)
+#: ./doc/common/tables/cinder-common.xml74(td)
+#: ./doc/common/tables/keystone-logging.xml34(td)
+#: ./doc/common/tables/heat-logging.xml34(td)
+#: ./doc/common/tables/nova-logging.xml46(td)
+#: ./doc/common/tables/trove-logging.xml34(td)
+msgid "log_config_append = None"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml43(td)
+#: ./doc/common/tables/neutron-logging.xml43(td)
+#: ./doc/common/tables/glance-logging.xml43(td)
+#: ./doc/common/tables/cinder-common.xml75(td)
+#: ./doc/common/tables/keystone-logging.xml35(td)
+#: ./doc/common/tables/heat-logging.xml35(td)
+#: ./doc/common/tables/nova-logging.xml47(td)
+#: ./doc/common/tables/trove-logging.xml35(td)
+msgid ""
+"(StrOpt) The name of logging configuration file. It does not disable "
+"existing loggers, but just appends specified logging configuration to any "
+"other existing logging options. Please see the Python logging module "
+"documentation for details on logging configuration files."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml46(td)
+#: ./doc/common/tables/neutron-logging.xml46(td)
+#: ./doc/common/tables/glance-logging.xml46(td)
+#: ./doc/common/tables/cinder-common.xml78(td)
+#: ./doc/common/tables/keystone-logging.xml38(td)
+#: ./doc/common/tables/heat-logging.xml38(td)
+#: ./doc/common/tables/nova-logging.xml50(td)
+#: ./doc/common/tables/trove-logging.xml38(td)
+msgid "log_date_format = %Y-%m-%d %H:%M:%S"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml47(td)
+#: ./doc/common/tables/neutron-logging.xml47(td)
+#: ./doc/common/tables/glance-logging.xml47(td)
+#: ./doc/common/tables/cinder-common.xml79(td)
+#: ./doc/common/tables/keystone-logging.xml39(td)
+#: ./doc/common/tables/heat-logging.xml39(td)
+#: ./doc/common/tables/nova-logging.xml51(td)
+#: ./doc/common/tables/trove-logging.xml39(td)
+msgid ""
+"(StrOpt) Format string for %%(asctime)s in log records. Default: %(default)s"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml50(td)
+#: ./doc/common/tables/neutron-logging.xml50(td)
+#: ./doc/common/tables/glance-logging.xml50(td)
+#: ./doc/common/tables/cinder-common.xml82(td)
+#: ./doc/common/tables/keystone-logging.xml42(td)
+#: ./doc/common/tables/heat-logging.xml42(td)
+#: ./doc/common/tables/nova-logging.xml54(td)
+#: ./doc/common/tables/trove-logging.xml42(td)
+msgid "log_dir = None"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml51(td)
+#: ./doc/common/tables/neutron-logging.xml51(td)
+#: ./doc/common/tables/glance-logging.xml51(td)
+#: ./doc/common/tables/cinder-common.xml83(td)
+#: ./doc/common/tables/keystone-logging.xml43(td)
+#: ./doc/common/tables/heat-logging.xml43(td)
+#: ./doc/common/tables/nova-logging.xml55(td)
+#: ./doc/common/tables/trove-logging.xml43(td)
+msgid ""
+"(StrOpt) (Optional) The base directory used for relative --log-file paths"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml54(td)
+#: ./doc/common/tables/neutron-logging.xml54(td)
+#: ./doc/common/tables/glance-logging.xml54(td)
+#: ./doc/common/tables/cinder-common.xml86(td)
+#: ./doc/common/tables/keystone-logging.xml46(td)
+#: ./doc/common/tables/heat-logging.xml46(td)
+#: ./doc/common/tables/nova-logging.xml58(td)
+#: ./doc/common/tables/trove-logging.xml46(td)
+msgid "log_file = None"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml55(td)
+#: ./doc/common/tables/neutron-logging.xml55(td)
+#: ./doc/common/tables/glance-logging.xml55(td)
+#: ./doc/common/tables/cinder-common.xml87(td)
+#: ./doc/common/tables/keystone-logging.xml47(td)
+#: ./doc/common/tables/heat-logging.xml47(td)
+#: ./doc/common/tables/nova-logging.xml59(td)
+#: ./doc/common/tables/trove-logging.xml47(td)
+msgid ""
+"(StrOpt) (Optional) Name of log file to output to. If no default is set, "
+"logging will go to stdout."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml58(td)
+#: ./doc/common/tables/neutron-logging.xml58(td)
+#: ./doc/common/tables/glance-logging.xml58(td)
+#: ./doc/common/tables/cinder-common.xml90(td)
+#: ./doc/common/tables/keystone-logging.xml50(td)
+#: ./doc/common/tables/heat-logging.xml50(td)
+#: ./doc/common/tables/nova-logging.xml62(td)
+#: ./doc/common/tables/trove-logging.xml50(td)
+msgid "log_format = None"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml59(td)
+#: ./doc/common/tables/neutron-logging.xml59(td)
+#: ./doc/common/tables/glance-logging.xml59(td)
+#: ./doc/common/tables/cinder-common.xml91(td)
+#: ./doc/common/tables/keystone-logging.xml51(td)
+#: ./doc/common/tables/heat-logging.xml51(td)
+#: ./doc/common/tables/nova-logging.xml63(td)
+#: ./doc/common/tables/trove-logging.xml51(td)
+msgid ""
+"(StrOpt) DEPRECATED. A logging.Formatter log message format string which may"
+" use any of the available logging.LogRecord attributes. This option is "
+"deprecated. Please use logging_context_format_string and "
+"logging_default_format_string instead."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml62(td)
+#: ./doc/common/tables/neutron-logging.xml62(td)
+#: ./doc/common/tables/glance-logging.xml62(td)
+#: ./doc/common/tables/cinder-common.xml94(td)
+#: ./doc/common/tables/keystone-logging.xml54(td)
+#: ./doc/common/tables/heat-logging.xml54(td)
+#: ./doc/common/tables/trove-logging.xml54(td)
+msgid ""
+"logging_context_format_string = %(asctime)s.%(msecs)03d %(process)d "
+"%(levelname)s %(name)s [%(request_id)s %(user_identity)s] "
+"%(instance)s%(message)s"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml63(td)
+#: ./doc/common/tables/glance-logging.xml63(td)
+#: ./doc/common/tables/cinder-common.xml95(td)
+#: ./doc/common/tables/keystone-logging.xml55(td)
+msgid "(StrOpt) Format string to use for log messages with context"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml66(td)
+#: ./doc/common/tables/neutron-logging.xml66(td)
+#: ./doc/common/tables/glance-logging.xml66(td)
+#: ./doc/common/tables/cinder-common.xml98(td)
+#: ./doc/common/tables/keystone-logging.xml58(td)
+#: ./doc/common/tables/heat-logging.xml58(td)
+#: ./doc/common/tables/nova-logging.xml70(td)
+#: ./doc/common/tables/trove-logging.xml58(td)
+msgid "logging_debug_format_suffix = %(funcName)s %(pathname)s:%(lineno)d"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml67(td)
+#: ./doc/common/tables/glance-logging.xml67(td)
+#: ./doc/common/tables/cinder-common.xml99(td)
+#: ./doc/common/tables/keystone-logging.xml59(td)
+msgid "(StrOpt) Data to append to log format when level is DEBUG"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml70(td)
+#: ./doc/common/tables/neutron-logging.xml70(td)
+#: ./doc/common/tables/glance-logging.xml70(td)
+#: ./doc/common/tables/cinder-common.xml102(td)
+#: ./doc/common/tables/keystone-logging.xml62(td)
+#: ./doc/common/tables/heat-logging.xml62(td)
+#: ./doc/common/tables/nova-logging.xml74(td)
+#: ./doc/common/tables/trove-logging.xml62(td)
+msgid ""
+"logging_default_format_string = %(asctime)s.%(msecs)03d %(process)d "
+"%(levelname)s %(name)s [-] %(instance)s%(message)s"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml71(td)
+#: ./doc/common/tables/glance-logging.xml71(td)
+#: ./doc/common/tables/cinder-common.xml103(td)
+#: ./doc/common/tables/keystone-logging.xml63(td)
+msgid "(StrOpt) Format string to use for log messages without context"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml74(td)
+#: ./doc/common/tables/neutron-logging.xml74(td)
+#: ./doc/common/tables/glance-logging.xml74(td)
+#: ./doc/common/tables/cinder-common.xml106(td)
+#: ./doc/common/tables/keystone-logging.xml66(td)
+#: ./doc/common/tables/heat-logging.xml66(td)
+#: ./doc/common/tables/nova-logging.xml78(td)
+#: ./doc/common/tables/trove-logging.xml66(td)
+msgid ""
+"logging_exception_prefix = %(asctime)s.%(msecs)03d %(process)d TRACE "
+"%(name)s %(instance)s"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml75(td)
+#: ./doc/common/tables/glance-logging.xml75(td)
+#: ./doc/common/tables/cinder-common.xml107(td)
+#: ./doc/common/tables/keystone-logging.xml67(td)
+msgid "(StrOpt) Prefix each line of exception output with this format"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml38(td)
-#: ./doc/common/tables/trove-logging.xml74(td)
-#: ./doc/common/tables/heat-notification.xml26(td)
-#: ./doc/common/tables/cinder-rpc.xml90(td)
-#: ./doc/common/tables/glance-logging.xml78(td)
 #: ./doc/common/tables/ceilometer-logging.xml78(td)
 #: ./doc/common/tables/neutron-logging.xml78(td)
+#: ./doc/common/tables/heat-notification.xml26(td)
+#: ./doc/common/tables/glance-logging.xml78(td)
+#: ./doc/common/tables/cinder-rpc.xml90(td)
 #: ./doc/common/tables/nova-logging.xml82(td)
+#: ./doc/common/tables/trove-logging.xml74(td)
+#: ./doc/common/tables/keystone-debug.xml38(td)
 msgid "publish_errors = False"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml39(td)
-#: ./doc/common/tables/cinder-rpc.xml91(td)
-#: ./doc/common/tables/glance-logging.xml79(td)
 #: ./doc/common/tables/ceilometer-logging.xml79(td)
+#: ./doc/common/tables/glance-logging.xml79(td)
+#: ./doc/common/tables/cinder-rpc.xml91(td)
+#: ./doc/common/tables/keystone-debug.xml39(td)
 msgid "(BoolOpt) Publish error events"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml42(td)
-#: ./doc/common/tables/trove-debug.xml46(td)
-msgid "pydev_debug_host = None"
+#: ./doc/common/tables/ceilometer-logging.xml82(td)
+#: ./doc/common/tables/neutron-logging.xml82(td)
+#: ./doc/common/tables/glance-logging.xml82(td)
+#: ./doc/common/tables/cinder-common.xml194(td)
+#: ./doc/common/tables/keystone-logging.xml70(td)
+#: ./doc/common/tables/heat-logging.xml70(td)
+#: ./doc/common/tables/nova-logging.xml86(td)
+#: ./doc/common/tables/trove-logging.xml78(td)
+msgid "syslog_log_facility = LOG_USER"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml43(td)
-msgid "(StrOpt) Host to connect to for remote debugger."
+#: ./doc/common/tables/ceilometer-logging.xml83(td)
+#: ./doc/common/tables/glance-logging.xml83(td)
+#: ./doc/common/tables/cinder-common.xml195(td)
+#: ./doc/common/tables/keystone-logging.xml71(td)
+msgid "(StrOpt) Syslog facility to receive log lines"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml46(td)
-#: ./doc/common/tables/trove-debug.xml50(td)
-msgid "pydev_debug_port = None"
+#: ./doc/common/tables/ceilometer-logging.xml86(td)
+#: ./doc/common/tables/neutron-logging.xml90(td)
+#: ./doc/common/tables/glance-logging.xml86(td)
+#: ./doc/common/tables/cinder-common.xml210(td)
+#: ./doc/common/tables/keystone-logging.xml74(td)
+#: ./doc/common/tables/heat-logging.xml74(td)
+#: ./doc/common/tables/nova-logging.xml90(td)
+#: ./doc/common/tables/trove-logging.xml82(td)
+msgid "use_stderr = True"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml47(td)
-msgid "(IntOpt) Port to connect to for remote debugger."
+#: ./doc/common/tables/ceilometer-logging.xml87(td)
+#: ./doc/common/tables/neutron-logging.xml91(td)
+#: ./doc/common/tables/glance-logging.xml87(td)
+#: ./doc/common/tables/cinder-common.xml211(td)
+#: ./doc/common/tables/keystone-logging.xml75(td)
+#: ./doc/common/tables/heat-logging.xml75(td)
+#: ./doc/common/tables/nova-logging.xml91(td)
+#: ./doc/common/tables/trove-logging.xml83(td)
+msgid "(BoolOpt) Log output to standard error"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml50(td)
-msgid "standard_threads = False"
+#: ./doc/common/tables/ceilometer-logging.xml90(td)
+#: ./doc/common/tables/neutron-logging.xml94(td)
+#: ./doc/common/tables/neutron-rootwrap.xml30(td)
+#: ./doc/common/tables/nova-rootwrap.xml30(td)
+#: ./doc/common/tables/glance-logging.xml90(td)
+#: ./doc/common/tables/cinder-common.xml214(td)
+#: ./doc/common/tables/keystone-logging.xml78(td)
+#: ./doc/common/tables/heat-logging.xml78(td)
+#: ./doc/common/tables/nova-logging.xml94(td)
+#: ./doc/common/tables/trove-logging.xml86(td)
+#: ./doc/common/tables/cinder-rootwrap.xml30(td)
+msgid "use_syslog = False"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml51(td)
-msgid "(BoolOpt) Do not monkey-patch threading system modules."
+#: ./doc/common/tables/ceilometer-logging.xml91(td)
+#: ./doc/common/tables/glance-logging.xml91(td)
+#: ./doc/common/tables/cinder-common.xml215(td)
+#: ./doc/common/tables/keystone-logging.xml79(td)
+#: ./doc/common/tables/nova-logging.xml95(td)
+msgid ""
+"(BoolOpt) Use syslog for logging. Existing syslog format is DEPRECATED "
+"during I, and then will be changed in J to honor RFC5424"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml94(td)
+#: ./doc/common/tables/glance-logging.xml94(td)
+#: ./doc/common/tables/cinder-common.xml218(td)
+#: ./doc/common/tables/keystone-logging.xml82(td)
+#: ./doc/common/tables/nova-logging.xml98(td)
+msgid "use_syslog_rfc_format = False"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml95(td)
+#: ./doc/common/tables/glance-logging.xml95(td)
+#: ./doc/common/tables/cinder-common.xml219(td)
+#: ./doc/common/tables/keystone-logging.xml83(td)
+#: ./doc/common/tables/nova-logging.xml99(td)
+msgid ""
+"(BoolOpt) (Optional) Use syslog rfc5424 format for logging. If enabled, will"
+" add APP-NAME (RFC5424) before the MSG part of the syslog message. The old "
+"format without APP-NAME is deprecated in I, and will be removed in J."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml98(td)
+#: ./doc/common/tables/neutron-logging.xml98(td)
+#: ./doc/common/tables/glance-logging.xml98(td)
+#: ./doc/common/tables/cinder-common.xml222(td)
+#: ./doc/common/tables/keystone-logging.xml86(td)
+#: ./doc/common/tables/heat-logging.xml82(td)
+#: ./doc/common/tables/nova-logging.xml102(td)
+#: ./doc/common/tables/trove-debug.xml78(td)
+msgid "verbose = False"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml99(td)
+#: ./doc/common/tables/neutron-logging.xml99(td)
+#: ./doc/common/tables/glance-logging.xml99(td)
+#: ./doc/common/tables/cinder-common.xml223(td)
+#: ./doc/common/tables/keystone-logging.xml87(td)
+#: ./doc/common/tables/heat-logging.xml83(td)
+#: ./doc/common/tables/nova-logging.xml103(td)
+#: ./doc/common/tables/trove-debug.xml79(td)
+msgid ""
+"(BoolOpt) Print more verbose output (set logging level to INFO instead of "
+"default WARNING level)."
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml54(th)
 #: ./doc/common/tables/ceilometer-logging.xml102(th)
 #: ./doc/common/tables/neutron-cadf.xml19(th)
+#: ./doc/common/tables/keystone-debug.xml54(th)
 msgid "[audit]"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml57(td)
+#: ./doc/common/tables/ceilometer-logging.xml105(td)
+#: ./doc/common/tables/neutron-cadf.xml22(td)
+msgid "api_audit_map = api_audit_map.conf"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-logging.xml106(td)
+#: ./doc/common/tables/neutron-cadf.xml23(td)
+msgid "(StrOpt) File containing mapping for api paths and service endpoints"
+msgstr ""
+
 #: ./doc/common/tables/ceilometer-logging.xml109(td)
 #: ./doc/common/tables/neutron-cadf.xml26(td)
+#: ./doc/common/tables/keystone-debug.xml57(td)
 msgid "namespace = openstack"
 msgstr ""
 
-#: ./doc/common/tables/keystone-debug.xml58(td)
 #: ./doc/common/tables/ceilometer-logging.xml110(td)
 #: ./doc/common/tables/neutron-cadf.xml27(td)
+#: ./doc/common/tables/keystone-debug.xml58(td)
 msgid "(StrOpt) namespace prefix for generated id"
 msgstr ""
 
-#: ./doc/common/tables/glance-policy.xml8(caption)
-#: ./doc/common/tables/nova-policy.xml8(caption)
-#: ./doc/common/tables/neutron-policy.xml8(caption)
-#: ./doc/common/tables/keystone-policy.xml8(caption)
-msgid "Description of configuration options for policy"
+#: ./doc/common/tables/heat-common.xml22(td)
+msgid "deferred_auth_method = password"
 msgstr ""
 
-#: ./doc/common/tables/glance-policy.xml22(td)
-#: ./doc/common/tables/nova-policy.xml58(td)
-#: ./doc/common/tables/ceilometer-api.xml34(td)
-#: ./doc/common/tables/cinder-common.xml138(td)
-#: ./doc/common/tables/heat-api.xml42(td)
-#: ./doc/common/tables/keystone-policy.xml22(td)
-msgid "policy_default_rule = default"
+#: ./doc/common/tables/heat-common.xml23(td)
+msgid "(StrOpt) Select deferred auth method, stored password or trusts."
 msgstr ""
 
-#: ./doc/common/tables/glance-policy.xml23(td)
-msgid "(StrOpt) The default policy to use."
+#: ./doc/common/tables/heat-common.xml26(td)
+msgid "environment_dir = /etc/heat/environment.d"
 msgstr ""
 
-#: ./doc/common/tables/glance-policy.xml26(td)
-#: ./doc/common/tables/nova-policy.xml62(td)
-#: ./doc/common/tables/ceilometer-api.xml38(td)
-#: ./doc/common/tables/cinder-common.xml142(td)
-#: ./doc/common/tables/neutron-policy.xml26(td)
-#: ./doc/common/tables/heat-api.xml46(td)
-#: ./doc/common/tables/keystone-policy.xml26(td)
-msgid "policy_file = policy.json"
+#: ./doc/common/tables/heat-common.xml27(td)
+msgid "(StrOpt) The directory to search for environment files."
 msgstr ""
 
-#: ./doc/common/tables/glance-policy.xml27(td)
-msgid "(StrOpt) The location of the policy file."
+#: ./doc/common/tables/heat-common.xml30(td)
+msgid "event_purge_batch_size = 10"
 msgstr ""
 
-#: ./doc/common/tables/neutron-mlnx.xml8(caption)
-msgid "Description of configuration options for mlnx"
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml19(th)
-#: ./doc/common/tables/neutron-ml2_mlnx.xml19(th)
-#: ./doc/common/tables/neutron-vmware.xml70(th)
-msgid "[ESWITCH]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml22(td)
-msgid "backoff_rate = 2"
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml23(td)
+#: ./doc/common/tables/heat-common.xml31(td)
 msgid ""
-"(IntOpt) backoff rate multiplier for waiting period between retries for "
-"request to daemon, i.e. value of 2 will double the request timeout each "
-"retry"
+"(IntOpt) Controls how many events will be pruned whenever a stack's events "
+"exceed max_events_per_stack. Set this lower to keep more events at the "
+"expense of more frequent purges."
 msgstr ""
 
-#: ./doc/common/tables/neutron-mlnx.xml26(td)
-msgid "daemon_endpoint = tcp://127.0.0.1:60001"
+#: ./doc/common/tables/heat-common.xml34(td)
+msgid "instance_driver = heat.engine.nova"
 msgstr ""
 
-#: ./doc/common/tables/neutron-mlnx.xml27(td)
-msgid "(StrOpt) eswitch daemon end point"
+#: ./doc/common/tables/heat-common.xml35(td)
+msgid "(StrOpt) Driver to use for controlling instances."
 msgstr ""
 
-#: ./doc/common/tables/neutron-mlnx.xml30(td)
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml22(td)
-msgid "physical_interface_mappings ="
+#: ./doc/common/tables/heat-common.xml38(td)
+msgid "instance_user = ec2-user"
 msgstr ""
 
-#: ./doc/common/tables/neutron-mlnx.xml31(td)
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml23(td)
-msgid "(ListOpt) List of &lt;physical_network&gt;:&lt;physical_interface&gt;"
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml34(td)
-msgid "request_timeout = 3000"
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml35(td)
+#: ./doc/common/tables/heat-common.xml39(td)
 msgid ""
-"(IntOpt) The number of milliseconds the agent will wait for response on "
-"request to daemon."
+"(StrOpt) The default user for new instances. This option is deprecated and "
+"will be removed in the Juno release. If it's empty, Heat will use the "
+"default user set up with your cloud image (for OS::Nova::Server) or "
+"'ec2-user' (for AWS::EC2::Instance)."
 msgstr ""
 
-#: ./doc/common/tables/neutron-mlnx.xml38(th)
-msgid "[MLNX]"
+#: ./doc/common/tables/heat-common.xml42(td)
+msgid "keystone_backend = heat.common.heat_keystoneclient.KeystoneClientV3"
 msgstr ""
 
-#: ./doc/common/tables/neutron-mlnx.xml41(td)
-msgid "network_vlan_ranges = default:1:1000"
+#: ./doc/common/tables/heat-common.xml43(td)
+msgid "(StrOpt) Fully qualified class name to use as a keystone backend."
 msgstr ""
 
-#: ./doc/common/tables/neutron-mlnx.xml42(td)
-#: ./doc/common/tables/neutron-openvswitch_agent.xml92(td)
-#: ./doc/common/tables/neutron-hyperv_agent.xml46(td)
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml30(td)
+#: ./doc/common/tables/heat-common.xml46(td)
+#: ./doc/common/tables/cinder-common.xml134(td)
+#: ./doc/common/tables/trove-rpc.xml42(td)
+msgid "periodic_interval = 60"
+msgstr ""
+
+#: ./doc/common/tables/heat-common.xml47(td)
+msgid "(IntOpt) Seconds between running periodic tasks."
+msgstr ""
+
+#: ./doc/common/tables/heat-common.xml50(td)
+msgid "plugin_dirs = /usr/lib64/heat, /usr/lib/heat"
+msgstr ""
+
+#: ./doc/common/tables/heat-common.xml51(td)
+msgid "(ListOpt) List of directories to search for plug-ins."
+msgstr ""
+
+#: ./doc/common/tables/heat-common.xml54(th)
+msgid "[revision]"
+msgstr ""
+
+#: ./doc/common/tables/heat-common.xml57(td)
+msgid "heat_revision = unknown"
+msgstr ""
+
+#: ./doc/common/tables/heat-common.xml58(td)
 msgid ""
-"(ListOpt) List of &lt;physical_network&gt;:&lt;vlan_min&gt;:&lt;vlan_max&gt;"
-" or &lt;physical_network&gt;"
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml45(td)
-msgid "physical_network_type = eth"
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml46(td)
-msgid "(StrOpt) Physical network type for provider network (eth or ib)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml49(td)
-msgid "physical_network_type_mappings ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml50(td)
-msgid ""
-"(ListOpt) List of &lt;physical_network&gt;:&lt;physical_network_type&gt; "
-"with physical_network_type is either eth or ib"
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml53(td)
-msgid "tenant_network_type = vlan"
-msgstr ""
-
-#: ./doc/common/tables/neutron-mlnx.xml54(td)
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml34(td)
-msgid "(StrOpt) Network type for tenant networks (local, vlan, or none)"
+"(StrOpt) Heat build revision. If you would prefer to manage your build "
+"revision separately, you can move this section to a different file and add "
+"it as another config option."
 msgstr ""
 
 #: ./doc/common/tables/nova-ipv6.xml8(caption)
@@ -25865,202 +29926,68 @@ msgstr ""
 msgid "(BoolOpt) Use IPv6"
 msgstr ""
 
-#: ./doc/common/tables/cinder-eqlx.xml8(caption)
-msgid "Description of configuration options for eqlx"
+#: ./doc/common/tables/nova-vnc.xml8(caption)
+msgid "Description of configuration options for vnc"
 msgstr ""
 
-#: ./doc/common/tables/cinder-eqlx.xml22(td)
-msgid "eqlx_chap_login = admin"
+#: ./doc/common/tables/nova-vnc.xml22(td)
+msgid "novncproxy_base_url = http://127.0.0.1:6080/vnc_auto.html"
 msgstr ""
 
-#: ./doc/common/tables/cinder-eqlx.xml23(td)
-msgid "(StrOpt) Existing CHAP account name"
-msgstr ""
-
-#: ./doc/common/tables/cinder-eqlx.xml26(td)
-msgid "eqlx_chap_password = password"
-msgstr ""
-
-#: ./doc/common/tables/cinder-eqlx.xml27(td)
-msgid "(StrOpt) Password for specified CHAP account name"
-msgstr ""
-
-#: ./doc/common/tables/cinder-eqlx.xml30(td)
-msgid "eqlx_cli_max_retries = 5"
-msgstr ""
-
-#: ./doc/common/tables/cinder-eqlx.xml31(td)
-msgid "(IntOpt) Maximum retry count for reconnection"
-msgstr ""
-
-#: ./doc/common/tables/cinder-eqlx.xml34(td)
-msgid "eqlx_cli_timeout = 30"
-msgstr ""
-
-#: ./doc/common/tables/cinder-eqlx.xml35(td)
-msgid "(IntOpt) Timeout for the Group Manager cli command execution"
-msgstr ""
-
-#: ./doc/common/tables/cinder-eqlx.xml38(td)
-msgid "eqlx_group_name = group-0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-eqlx.xml39(td)
-msgid "(StrOpt) Group name to use for creating volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-eqlx.xml42(td)
-msgid "eqlx_pool = default"
-msgstr ""
-
-#: ./doc/common/tables/cinder-eqlx.xml43(td)
-msgid "(StrOpt) Pool in which volumes will be created"
-msgstr ""
-
-#: ./doc/common/tables/cinder-eqlx.xml46(td)
-msgid "eqlx_use_chap = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-eqlx.xml47(td)
-msgid "(BoolOpt) Use CHAP authentication for targets?"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml7(literal)
-msgid "[filter:catch_errors]"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml7(literal)
-#: ./doc/common/tables/swift-object-expirer-filter-cache.xml7(literal)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml7(literal)
-#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml7(literal)
-#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml7(literal)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml7(literal)
-msgid "object-expirer.conf-sample"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml7(caption)
-#: ./doc/common/tables/swift-object-expirer-filter-cache.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml7(caption)
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml7(caption)
-#: ./doc/common/tables/swift-container-server-container-updater.xml7(caption)
-#: ./doc/common/tables/swift-account-server-filter-recon.xml7(caption)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml7(caption)
-#: ./doc/common/tables/swift-container-server-container-sync.xml7(caption)
-#: ./doc/common/tables/swift-object-server-object-auditor.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml7(caption)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml7(caption)
-#: ./doc/common/tables/swift-object-server-object-updater.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml7(caption)
-#: ./doc/common/tables/swift-container-server-pipeline-main.xml7(caption)
-#: ./doc/common/tables/swift-rsyncd-object.xml7(caption)
-#: ./doc/common/tables/swift-object-server-pipeline-main.xml7(caption)
-#: ./doc/common/tables/swift-account-server-app-account-server.xml7(caption)
-#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml7(caption)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml7(caption)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml7(caption)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml7(caption)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml7(caption)
-#: ./doc/common/tables/swift-rsyncd-account.xml7(caption)
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml7(caption)
-#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml7(caption)
-#: ./doc/common/tables/swift-swift-swift-constraints.xml7(caption)
-#: ./doc/common/tables/swift-object-server-filter-recon.xml7(caption)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml7(caption)
-#: ./doc/common/tables/swift-memcache-memcache.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml7(caption)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml7(caption)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml7(caption)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml7(caption)
-#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml7(caption)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml7(caption)
-#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml7(caption)
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml7(caption)
-#: ./doc/common/tables/swift-container-server-filter-recon.xml7(caption)
-#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml7(caption)
-#: ./doc/common/tables/swift-swift-swift-hash.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml7(caption)
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml7(caption)
-#: ./doc/common/tables/swift-rsyncd-container.xml7(caption)
-#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml7(caption)
-#: ./doc/common/tables/swift-account-server-pipeline-main.xml7(caption)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml7(caption)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml7(caption)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml7(caption)
+#: ./doc/common/tables/nova-vnc.xml23(td)
 msgid ""
-"Description of configuration options for <placeholder-1/> in "
-"<placeholder-2/>"
+"(StrOpt) Location of VNC console proxy, in the form "
+"\"http://127.0.0.1:6080/vnc_auto.html\""
 msgstr ""
 
-#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml18(td)
-msgid "use = egg:swift#catch_errors"
+#: ./doc/common/tables/nova-vnc.xml26(td)
+msgid "vnc_enabled = True"
 msgstr ""
 
-#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml18(td)
-#: ./doc/common/tables/swift-object-expirer-filter-cache.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml18(td)
-#: ./doc/common/tables/swift-account-server-filter-recon.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml18(td)
-#: ./doc/common/tables/swift-account-server-app-account-server.xml18(td)
-#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml18(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml18(td)
-#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml18(td)
-#: ./doc/common/tables/swift-object-server-filter-recon.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml18(td)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml18(td)
-#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml18(td)
-#: ./doc/common/tables/swift-container-server-filter-recon.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml18(td)
-#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml18(td)
-msgid "Entry point of paste.deploy in the server"
+#: ./doc/common/tables/nova-vnc.xml27(td)
+msgid "(BoolOpt) Enable VNC related features"
 msgstr ""
 
-#: ./doc/common/tables/swift-object-expirer-filter-cache.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml7(literal)
-msgid "[filter:cache]"
+#: ./doc/common/tables/nova-vnc.xml30(td)
+msgid "vnc_keymap = en-us"
 msgstr ""
 
-#: ./doc/common/tables/swift-object-expirer-filter-cache.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml18(td)
-msgid "use = egg:swift#memcache"
+#: ./doc/common/tables/nova-vnc.xml31(td)
+msgid "(StrOpt) Keymap for VNC"
+msgstr ""
+
+#: ./doc/common/tables/nova-vnc.xml34(td)
+msgid "vncserver_listen = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/nova-vnc.xml35(td)
+msgid "(StrOpt) IP address on which instance vncservers should listen"
+msgstr ""
+
+#: ./doc/common/tables/nova-vnc.xml38(td)
+msgid "vncserver_proxyclient_address = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/nova-vnc.xml39(td)
+msgid ""
+"(StrOpt) The address to which proxy clients (like nova-xvpvncproxy) should "
+"connect"
+msgstr ""
+
+#: ./doc/common/tables/nova-vnc.xml45(td)
+msgid "vnc_port = 5900"
+msgstr ""
+
+#: ./doc/common/tables/nova-vnc.xml46(td)
+msgid "(IntOpt) VNC starting port"
+msgstr ""
+
+#: ./doc/common/tables/nova-vnc.xml49(td)
+msgid "vnc_port_total = 10000"
+msgstr ""
+
+#: ./doc/common/tables/nova-vnc.xml50(td)
+msgid "(IntOpt) Total number of VNC ports"
 msgstr ""
 
 #: ./doc/common/tables/cinder-netapp_cdot_extraspecs.xml5(caption)
@@ -26224,189 +30151,2487 @@ msgid ""
 "provisioning on the storage controller."
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml7(literal)
+#: ./doc/common/tables/trove-qpid.xml8(caption)
+#: ./doc/common/tables/heat-qpid.xml8(caption)
+#: ./doc/common/tables/nova-qpid.xml8(caption)
+#: ./doc/common/tables/glance-qpid.xml8(caption)
+#: ./doc/common/tables/neutron-qpid.xml8(caption)
+#: ./doc/common/tables/keystone-qpid.xml8(caption)
+#: ./doc/common/tables/ceilometer-qpid.xml8(caption)
+msgid "Description of configuration options for qpid"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml22(td)
+#: ./doc/common/tables/heat-qpid.xml22(td)
+#: ./doc/common/tables/nova-qpid.xml22(td)
+#: ./doc/common/tables/glance-qpid.xml22(td)
+#: ./doc/common/tables/cinder-rpc.xml94(td)
+#: ./doc/common/tables/nova-rpc_all.xml62(td)
+#: ./doc/common/tables/neutron-qpid.xml22(td)
+#: ./doc/common/tables/keystone-qpid.xml22(td)
+#: ./doc/common/tables/ceilometer-qpid.xml22(td)
+msgid "qpid_heartbeat = 60"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml23(td)
+#: ./doc/common/tables/heat-qpid.xml23(td)
+#: ./doc/common/tables/neutron-qpid.xml23(td)
+#: ./doc/common/tables/ceilometer-qpid.xml23(td)
+msgid "(IntOpt) Seconds between connection keepalive heartbeats"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml26(td)
+#: ./doc/common/tables/heat-qpid.xml26(td)
+#: ./doc/common/tables/nova-qpid.xml26(td)
+#: ./doc/common/tables/glance-qpid.xml26(td)
+#: ./doc/common/tables/cinder-rpc.xml98(td)
+#: ./doc/common/tables/nova-rpc_all.xml66(td)
+#: ./doc/common/tables/neutron-qpid.xml26(td)
+#: ./doc/common/tables/keystone-qpid.xml26(td)
+#: ./doc/common/tables/ceilometer-qpid.xml26(td)
+msgid "qpid_hostname = localhost"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml27(td)
+#: ./doc/common/tables/heat-qpid.xml27(td)
+#: ./doc/common/tables/neutron-qpid.xml27(td)
+#: ./doc/common/tables/ceilometer-qpid.xml27(td)
+msgid "(StrOpt) Qpid broker hostname"
+msgstr "(文字列オプション) Qpid ブローカーのホスト名"
+
+#: ./doc/common/tables/trove-qpid.xml30(td)
+#: ./doc/common/tables/heat-qpid.xml30(td)
+#: ./doc/common/tables/nova-qpid.xml30(td)
+#: ./doc/common/tables/glance-qpid.xml30(td)
+#: ./doc/common/tables/cinder-rpc.xml102(td)
+#: ./doc/common/tables/nova-rpc_all.xml70(td)
+#: ./doc/common/tables/neutron-qpid.xml30(td)
+#: ./doc/common/tables/keystone-qpid.xml30(td)
+#: ./doc/common/tables/ceilometer-qpid.xml30(td)
+msgid "qpid_hosts = $qpid_hostname:$qpid_port"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml31(td)
+#: ./doc/common/tables/heat-qpid.xml31(td)
+#: ./doc/common/tables/neutron-qpid.xml31(td)
+#: ./doc/common/tables/ceilometer-qpid.xml31(td)
+msgid "(ListOpt) Qpid HA cluster host:port pairs"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml34(td)
+#: ./doc/common/tables/heat-qpid.xml34(td)
+#: ./doc/common/tables/nova-qpid.xml34(td)
+#: ./doc/common/tables/glance-qpid.xml34(td)
+#: ./doc/common/tables/cinder-rpc.xml106(td)
+#: ./doc/common/tables/nova-rpc_all.xml74(td)
+#: ./doc/common/tables/neutron-qpid.xml34(td)
+#: ./doc/common/tables/keystone-qpid.xml34(td)
+#: ./doc/common/tables/ceilometer-qpid.xml34(td)
+msgid "qpid_password ="
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml35(td)
+#: ./doc/common/tables/heat-qpid.xml35(td)
+#: ./doc/common/tables/neutron-qpid.xml35(td)
+#: ./doc/common/tables/ceilometer-qpid.xml35(td)
+msgid "(StrOpt) Password for qpid connection"
+msgstr "(文字列オプション) qpid 接続のパスワード"
+
+#: ./doc/common/tables/trove-qpid.xml38(td)
+#: ./doc/common/tables/heat-qpid.xml38(td)
+#: ./doc/common/tables/nova-qpid.xml38(td)
+#: ./doc/common/tables/glance-qpid.xml38(td)
+#: ./doc/common/tables/cinder-rpc.xml110(td)
+#: ./doc/common/tables/nova-rpc_all.xml78(td)
+#: ./doc/common/tables/neutron-qpid.xml38(td)
+#: ./doc/common/tables/keystone-qpid.xml38(td)
+#: ./doc/common/tables/ceilometer-qpid.xml38(td)
+msgid "qpid_port = 5672"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml39(td)
+#: ./doc/common/tables/heat-qpid.xml39(td)
+#: ./doc/common/tables/neutron-qpid.xml39(td)
+#: ./doc/common/tables/ceilometer-qpid.xml39(td)
+msgid "(IntOpt) Qpid broker port"
+msgstr "(整数オプション) Qpid ブローカーのポート"
+
+#: ./doc/common/tables/trove-qpid.xml42(td)
+#: ./doc/common/tables/heat-qpid.xml42(td)
+#: ./doc/common/tables/nova-qpid.xml42(td)
+#: ./doc/common/tables/glance-qpid.xml42(td)
+#: ./doc/common/tables/cinder-rpc.xml114(td)
+#: ./doc/common/tables/nova-rpc_all.xml82(td)
+#: ./doc/common/tables/neutron-qpid.xml42(td)
+#: ./doc/common/tables/keystone-qpid.xml42(td)
+#: ./doc/common/tables/ceilometer-qpid.xml42(td)
+msgid "qpid_protocol = tcp"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml43(td)
+#: ./doc/common/tables/heat-qpid.xml43(td)
+#: ./doc/common/tables/neutron-qpid.xml43(td)
+#: ./doc/common/tables/ceilometer-qpid.xml43(td)
+msgid "(StrOpt) Transport to use, either 'tcp' or 'ssl'"
+msgstr "(文字列オプション) 使用する転送方式、'tcp' または 'ssl'"
+
+#: ./doc/common/tables/trove-qpid.xml46(td)
+#: ./doc/common/tables/heat-qpid.xml46(td)
+#: ./doc/common/tables/nova-qpid.xml46(td)
+#: ./doc/common/tables/glance-qpid.xml46(td)
+#: ./doc/common/tables/cinder-rpc.xml118(td)
+#: ./doc/common/tables/nova-rpc_all.xml86(td)
+#: ./doc/common/tables/neutron-qpid.xml46(td)
+#: ./doc/common/tables/keystone-qpid.xml46(td)
+#: ./doc/common/tables/ceilometer-qpid.xml46(td)
+msgid "qpid_sasl_mechanisms ="
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml47(td)
+#: ./doc/common/tables/heat-qpid.xml47(td)
+#: ./doc/common/tables/neutron-qpid.xml47(td)
+#: ./doc/common/tables/ceilometer-qpid.xml47(td)
+msgid "(StrOpt) Space separated list of SASL mechanisms to use for auth"
+msgstr "(文字列オプション) 認証に使用する SASL メカニズムの空白区切り一覧"
+
+#: ./doc/common/tables/trove-qpid.xml50(td)
+#: ./doc/common/tables/heat-qpid.xml50(td)
+#: ./doc/common/tables/nova-qpid.xml50(td)
+#: ./doc/common/tables/glance-qpid.xml50(td)
+#: ./doc/common/tables/cinder-rpc.xml122(td)
+#: ./doc/common/tables/nova-rpc_all.xml90(td)
+#: ./doc/common/tables/neutron-qpid.xml50(td)
+#: ./doc/common/tables/keystone-qpid.xml50(td)
+#: ./doc/common/tables/ceilometer-qpid.xml50(td)
+msgid "qpid_tcp_nodelay = True"
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml51(td)
+#: ./doc/common/tables/heat-qpid.xml51(td)
+#: ./doc/common/tables/neutron-qpid.xml51(td)
+#: ./doc/common/tables/ceilometer-qpid.xml51(td)
+msgid "(BoolOpt) Disable Nagle algorithm"
+msgstr "(論理値オプション) Nagle アルゴリズムの無効化"
+
+#: ./doc/common/tables/trove-qpid.xml54(td)
+#: ./doc/common/tables/heat-qpid.xml58(td)
+#: ./doc/common/tables/nova-qpid.xml58(td)
+#: ./doc/common/tables/glance-qpid.xml58(td)
+#: ./doc/common/tables/cinder-rpc.xml130(td)
+#: ./doc/common/tables/nova-rpc_all.xml98(td)
+#: ./doc/common/tables/neutron-qpid.xml58(td)
+#: ./doc/common/tables/keystone-qpid.xml58(td)
+#: ./doc/common/tables/ceilometer-qpid.xml58(td)
+msgid "qpid_username ="
+msgstr ""
+
+#: ./doc/common/tables/trove-qpid.xml55(td)
+#: ./doc/common/tables/heat-qpid.xml59(td)
+#: ./doc/common/tables/neutron-qpid.xml59(td)
+#: ./doc/common/tables/ceilometer-qpid.xml59(td)
+msgid "(StrOpt) Username for qpid connection"
+msgstr "(文字列オプション) qpid 接続のユーザー名"
+
+#: ./doc/common/tables/keystone-api.xml8(caption)
+#: ./doc/common/tables/trove-api.xml8(caption)
+#: ./doc/common/tables/glance-api.xml8(caption)
+#: ./doc/common/tables/ceilometer-api.xml8(caption)
+#: ./doc/common/tables/heat-api.xml8(caption)
+#: ./doc/common/tables/cinder-api.xml8(caption)
+#: ./doc/common/tables/nova-api.xml8(caption)
+#: ./doc/common/tables/neutron-api.xml8(caption)
+msgid "Description of configuration options for api"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml22(td)
+msgid "admin_bind_host = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml23(td)
+msgid ""
+"(StrOpt) The IP Address of the network interface to for the admin service to"
+" listen on."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml26(td)
+msgid "admin_endpoint = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml27(td)
+msgid ""
+"(StrOpt) The base admin endpoint URL for keystone that are advertised to "
+"clients (NOTE: this does NOT affect how keystone listens for connections). "
+"Defaults to the base host URL of the request. Eg a request to "
+"http://server:35357/v2.0/users will default to http://server:35357. You "
+"should only need to set this value if the base URL contains a path (eg "
+"/prefix/v2.0) or the endpoint should be found on a different server."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml30(td)
+msgid "admin_port = 35357"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml31(td)
+msgid "(IntOpt) The port number which the admin service listens on."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml34(td)
+msgid "admin_token = ADMIN"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml35(td)
+msgid ""
+"(StrOpt) A \"shared secret\" that can be used to bootstrap Keystone. This "
+"\"token\" does not represent a user, and carries no explicit authorization. "
+"To disable in production (highly recommended), remove "
+"AdminTokenAuthMiddleware from your paste application pipelines (for example,"
+" in keystone-paste.ini)."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml38(td)
+msgid "compute_port = 8774"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml39(td)
+msgid "(IntOpt) The port which the OpenStack Compute service listens on."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml42(td)
+msgid "domain_id_immutable = True"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml43(td)
+msgid ""
+"(BoolOpt) Set this to false if you want to enable the ability for user, "
+"group and project entities to be moved between domains by updating their "
+"domain_id. Allowing such movement is not recommended if the scope of a "
+"domain admin is being restricted by use of an appropriate policy file (see "
+"policy.v3cloudsample as an example)."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml47(td)
+msgid ""
+"(IntOpt) The maximum number of entities that will be returned in a "
+"collection can be set with list_limit, with no limit set by default. This "
+"global limit may be then overridden for a specific driver, by specifying a "
+"list_limit in the appropriate section (e.g. [assignment])."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml50(td)
+msgid "max_param_size = 64"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml51(td)
+msgid "(IntOpt) limit the sizes of user &amp; tenant ID/names."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml54(td)
+#: ./doc/common/tables/ceilometer-api.xml26(td)
+#: ./doc/common/tables/neutron-api.xml46(td)
+msgid "max_request_body_size = 114688"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml55(td)
+msgid ""
+"(IntOpt) enforced by optional sizelimit middleware "
+"(keystone.middleware:RequestBodySizeLimiter)."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml58(td)
+msgid "max_token_size = 8192"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml59(td)
+msgid ""
+"(IntOpt) similar to max_param_size, but provides an exception for token "
+"values."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml62(td)
+msgid "member_role_id = 9fe2ff9ee4384b1894a90878d3e92bab"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml63(td)
+msgid ""
+"(StrOpt) During a SQL upgrade member_role_id will be used to create a new "
+"role that will replace records in the user_tenant_membership table with "
+"explicit role grants. After migration, the member_role_id will be used in "
+"the API add_user_to_project."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml66(td)
+msgid "member_role_name = _member_"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml67(td)
+msgid ""
+"(StrOpt) During a SQL upgrade member_role_id will be used to create a new "
+"role that will replace records in the user_tenant_membership table with "
+"explicit role grants. After migration, member_role_name will be ignored."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml70(td)
+msgid "public_bind_host = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml71(td)
+msgid ""
+"(StrOpt) The IP Address of the network interface to for the public service "
+"to listen on."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml74(td)
+msgid "public_endpoint = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml75(td)
+msgid ""
+"(StrOpt) The base public endpoint URL for keystone that are advertised to "
+"clients (NOTE: this does NOT affect how keystone listens for connections). "
+"Defaults to the base host URL of the request. Eg a request to "
+"http://server:5000/v2.0/users will default to http://server:5000. You should"
+" only need to set this value if the base URL contains a path (eg "
+"/prefix/v2.0) or the endpoint should be found on a different server."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml78(td)
+msgid "public_port = 5000"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml79(td)
+msgid "(IntOpt) The port number which the public service listens on."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml82(td)
+msgid "tcp_keepalive = False"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml83(td)
+msgid ""
+"(BoolOpt) Set this to True if you want to enable TCP_KEEPALIVE on server "
+"sockets i.e. sockets used by the keystone wsgi server for client "
+"connections."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml86(td)
+#: ./doc/common/tables/trove-api.xml74(td)
+#: ./doc/common/tables/cinder-common.xml198(td)
+#: ./doc/common/tables/neutron-wsgi.xml30(td)
+#: ./doc/common/tables/glance-wsgi.xml34(td)
+#: ./doc/common/tables/nova-wsgi.xml38(td)
+msgid "tcp_keepidle = 600"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml87(td)
+msgid ""
+"(IntOpt) Sets the value of TCP_KEEPIDLE in seconds for each server socket. "
+"Only applies if tcp_keepalive is True. Not supported on OS X."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml90(th)
+msgid "[endpoint_filter]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml93(td)
+msgid "driver = keystone.contrib.endpoint_filter.backends.sql.EndpointFilter"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml94(td)
+msgid "(StrOpt) Keystone Endpoint Filter backend driver"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml97(td)
+msgid "return_all_endpoints_if_no_filter = True"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml98(td)
+msgid "(BoolOpt) Toggle to return all active endpoints if no filter exists."
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml101(th)
+#: ./doc/common/tables/heat-api.xml131(th)
+#: ./doc/common/tables/glance-paste.xml19(th)
+msgid "[paste_deploy]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml104(td)
+msgid "config_file = keystone-paste.ini"
+msgstr ""
+
+#: ./doc/common/tables/keystone-api.xml105(td)
+msgid ""
+"(StrOpt) Name of the paste configuration file that defines the available "
+"pipelines."
+msgstr ""
+
+#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml7(literal)
 #: ./doc/common/tables/swift-proxy-server-pipeline-main.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml7(literal)
-msgid "proxy-server.conf-sample"
+#: ./doc/common/tables/swift-container-server-pipeline-main.xml7(literal)
+#: ./doc/common/tables/swift-object-server-pipeline-main.xml7(literal)
+#: ./doc/common/tables/swift-account-server-pipeline-main.xml7(literal)
+msgid "[pipeline:main]"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml7(literal)
+#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml7(literal)
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml7(literal)
+#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml7(literal)
+#: ./doc/common/tables/swift-object-expirer-filter-cache.xml7(literal)
+#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml7(literal)
+msgid "object-expirer.conf-sample"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml18(td)
+msgid "pipeline = catch_errors cache proxy-server"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-auditor.xml7(literal)
+msgid "[container-auditor]"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-auditor.xml18(td)
+msgid "log_name = container-auditor"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-auditor.xml30(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml30(td)
+msgid "interval = 1800"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-auditor.xml33(td)
+msgid "containers_per_second = 200"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-auditor.xml33(td)
+msgid ""
+"Maximum containers audited per second. Should be tuned according to "
+"individual system specs. 0 is unlimited. mounted to prevent accidentally "
+"writing to the root device process simultaneously (it will actually "
+"accept(2) N + 1). Setting this to one (1) will only handle one request at a "
+"time, without accepting another request concurrently. By increasing the "
+"number of workers to a much higher value, one can reduce the impact of slow "
+"file system operations in one request from negatively impacting other "
+"requests."
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-auditor.xml36(td)
+#: ./doc/common/tables/swift-container-server-filter-recon.xml21(td)
+#: ./doc/common/tables/swift-account-server-filter-recon.xml21(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml63(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml49(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml72(td)
+#: ./doc/common/tables/swift-object-server-object-auditor.xml42(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml57(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml42(td)
+#: ./doc/common/tables/swift-object-server-filter-recon.xml21(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml42(td)
+msgid "recon_cache_path = /var/cache/swift"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-auditor.xml36(td)
+#: ./doc/common/tables/swift-container-server-filter-recon.xml21(td)
+#: ./doc/common/tables/swift-account-server-filter-recon.xml21(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml63(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml49(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml72(td)
+#: ./doc/common/tables/swift-object-server-object-auditor.xml42(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml57(td)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml42(td)
+#: ./doc/common/tables/swift-object-server-filter-recon.xml21(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml42(td)
+msgid "Directory where stats for a few items will be stored"
+msgstr ""
+
+#: ./doc/common/tables/glance-rpc.xml22(td)
+msgid ""
+"allowed_rpc_exception_modules = openstack.common.exception, "
+"glance.common.exception, exceptions"
+msgstr ""
+
+#: ./doc/common/tables/glance-rpc.xml23(td)
+#: ./doc/common/tables/trove-rpc.xml23(td)
+msgid ""
+"(ListOpt) Modules of exceptions that are permitted to be recreatedupon "
+"receiving exception data from an rpc call."
+msgstr ""
+
+#: ./doc/common/tables/neutron-policy.xml22(td)
+msgid "allow_overlapping_ips = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-policy.xml23(td)
+msgid "(BoolOpt) Allow overlapping IP support in Neutron"
+msgstr ""
+
+#: ./doc/common/tables/neutron-policy.xml27(td)
+msgid "(StrOpt) The policy file to use"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml8(caption)
+msgid "Description of configuration options for spice"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml19(th)
+msgid "[spice]"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml22(td)
+msgid "agent_enabled = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml23(td)
+msgid "(BoolOpt) Enable spice guest agent support"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml26(td)
+#: ./doc/common/tables/keystone-os_inherit.xml22(td)
+#: ./doc/common/tables/nova-rdp.xml22(td)
+#: ./doc/common/tables/nova-apiv3.xml22(td)
+#: ./doc/common/tables/neutron-fwaas.xml22(td)
+#: ./doc/common/tables/keystone-cache.xml38(td)
+msgid "enabled = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml27(td)
+msgid "(BoolOpt) Enable spice related features"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml30(td)
+msgid "html5proxy_base_url = http://127.0.0.1:6082/spice_auto.html"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml31(td)
+msgid ""
+"(StrOpt) Location of spice HTML5 console proxy, in the form "
+"\"http://127.0.0.1:6082/spice_auto.html\""
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml34(td)
+msgid "keymap = en-us"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml35(td)
+msgid "(StrOpt) Keymap for spice"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml38(td)
+msgid "server_listen = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml39(td)
+msgid "(StrOpt) IP address on which instance spice server should listen"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml42(td)
+msgid "server_proxyclient_address = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/nova-spice.xml43(td)
+msgid ""
+"(StrOpt) The address to which proxy clients (like nova-spicehtml5proxy) "
+"should connect"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_heat.xml8(caption)
+msgid "Description of configuration options for clients_heat"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_heat.xml19(th)
+msgid "[clients_heat]"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_heat.xml42(td)
+#: ./doc/common/tables/neutron-ml2_ncs.xml30(td)
+#: ./doc/common/tables/neutron-ml2_odl.xml34(td)
+msgid "url = None"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_heat.xml43(td)
+msgid ""
+"(StrOpt) Optional heat url in format like "
+"http://0.0.0.0:8004/v1/%(tenant_id)s."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml8(caption)
+msgid "Description of configuration options for xen"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml22(td)
+msgid "console_driver = nova.console.xvp.XVPConsoleProxy"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml23(td)
+msgid "(StrOpt) Driver to use for the console proxy"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml26(td)
+msgid "console_vmrc_error_retries = 10"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml27(td)
+msgid "(IntOpt) Number of retries for retrieving VMRC information"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml30(td)
+msgid "console_vmrc_port = 443"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml31(td)
+msgid "(IntOpt) Port for VMware VMRC connections"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml34(td)
+msgid "console_xvp_conf = /etc/xvp.conf"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml35(td)
+msgid "(StrOpt) Generated XVP conf file"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml38(td)
+msgid "console_xvp_conf_template = $pybasedir/nova/console/xvp.conf.template"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml39(td)
+msgid "(StrOpt) XVP conf template"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml42(td)
+msgid "console_xvp_log = /var/log/xvp.log"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml43(td)
+msgid "(StrOpt) XVP log file"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml46(td)
+msgid "console_xvp_multiplex_port = 5900"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml47(td)
+msgid "(IntOpt) Port for XVP to multiplex VNC connections on"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml50(td)
+msgid "console_xvp_pid = /var/run/xvp.pid"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml51(td)
+msgid "(StrOpt) XVP master process pid file"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml54(td)
+msgid "stub_compute = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml55(td)
+msgid "(BoolOpt) Stub calls to compute worker for tests"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml58(th)
+#: ./doc/common/tables/nova-volumes.xml84(th)
+#: ./doc/common/tables/nova-livemigration.xml26(th)
+#: ./doc/common/tables/nova-hypervisor.xml54(th)
+#: ./doc/common/tables/nova-libvirt.xml30(th)
+msgid "[libvirt]"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml61(td)
+msgid "xen_hvmloader_path = /usr/lib/xen/boot/hvmloader"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml62(td)
+msgid "(StrOpt) Location where the Xen hvmloader is kept"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml65(th)
+#: ./doc/common/tables/nova-volumes.xml131(th)
+#: ./doc/common/tables/nova-baremetal.xml130(th)
+msgid "[xenserver]"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml68(td)
+msgid "agent_path = usr/sbin/xe-update-networking"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml69(td)
+msgid ""
+"(StrOpt) Specifies the path in which the XenAPI guest agent should be "
+"located. If the agent is present, network configuration is not injected into"
+" the image. Used if compute_driver=xenapi.XenAPIDriver and "
+"flat_injected=True"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml72(td)
+msgid "agent_resetnetwork_timeout = 60"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml73(td)
+msgid ""
+"(IntOpt) Number of seconds to wait for agent reply to resetnetwork request"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml76(td)
+msgid "agent_timeout = 30"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml77(td)
+msgid "(IntOpt) Number of seconds to wait for agent reply"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml80(td)
+msgid "agent_version_timeout = 300"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml81(td)
+msgid "(IntOpt) Number of seconds to wait for agent to be fully operational"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml84(td)
+msgid "cache_images = all"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml85(td)
+msgid ""
+"(StrOpt) Cache glance images locally. `all` will cache all images, `some` "
+"will only cache images that have the image_property `cache_in_nova=True`, "
+"and `none` turns off caching entirely"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml88(td)
+msgid "check_host = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml89(td)
+msgid ""
+"(BoolOpt) Ensure compute service is running on host XenAPI connects to."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml92(td)
+msgid "connection_concurrent = 5"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml93(td)
+msgid ""
+"(IntOpt) Maximum number of concurrent XenAPI connections. Used only if "
+"compute_driver=xenapi.XenAPIDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml96(td)
+msgid "connection_password = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml97(td)
+msgid ""
+"(StrOpt) Password for connection to XenServer/Xen Cloud Platform. Used only "
+"if compute_driver=xenapi.XenAPIDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml100(td)
+msgid "connection_url = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml101(td)
+msgid ""
+"(StrOpt) URL for connection to XenServer/Xen Cloud Platform. A special value"
+" of unix://local can be used to connect to the local unix socket. Required "
+"if compute_driver=xenapi.XenAPIDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml104(td)
+msgid "connection_username = root"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml105(td)
+msgid ""
+"(StrOpt) Username for connection to XenServer/Xen Cloud Platform. Used only "
+"if compute_driver=xenapi.XenAPIDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml108(td)
+msgid "default_os_type = linux"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml109(td)
+msgid "(StrOpt) Default OS type"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml112(td)
+msgid "disable_agent = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml113(td)
+msgid ""
+"(BoolOpt) Disables the use of the XenAPI agent in any image regardless of "
+"what image properties are present."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml116(td)
+msgid "image_compression_level = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml117(td)
+msgid ""
+"(IntOpt) Compression level for images, e.g., 9 for gzip -9. Range is 1-9, 9 "
+"being most compressed but most CPU intensive on dom0."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml120(td)
+msgid "image_upload_handler = nova.virt.xenapi.image.glance.GlanceStore"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml121(td)
+msgid "(StrOpt) Dom0 plugin driver used to handle image uploads."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml124(td)
+msgid "introduce_vdi_retry_wait = 20"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml125(td)
+msgid ""
+"(IntOpt) Number of seconds to wait for an SR to settle if the VDI does not "
+"exist when first introduced"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml128(td)
+msgid "ipxe_boot_menu_url = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml129(td)
+msgid "(StrOpt) URL to the iPXE boot menu"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml132(td)
+msgid "ipxe_mkisofs_cmd = mkisofs"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml133(td)
+#: ./doc/common/tables/nova-configdrive.xml39(td)
+msgid ""
+"(StrOpt) Name and optionally path of the tool used for ISO image creation"
+msgstr "(文字列オプション) ISO イメージの作成に使用するツールの名前と (任意で) パス"
+
+#: ./doc/common/tables/nova-xen.xml136(td)
+msgid "ipxe_network_name = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml137(td)
+msgid "(StrOpt) Name of network to use for booting iPXE ISOs"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml140(td)
+msgid "iqn_prefix = iqn.2010-10.org.openstack"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml141(td)
+msgid "(StrOpt) IQN Prefix"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml144(td)
+msgid "login_timeout = 10"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml145(td)
+msgid "(IntOpt) Timeout in seconds for XenAPI login."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml148(td)
+msgid "max_kernel_ramdisk_size = 16777216"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml149(td)
+msgid "(IntOpt) Maximum size in bytes of kernel or ramdisk images"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml152(td)
+msgid "num_vbd_unplug_retries = 10"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml153(td)
+msgid "(IntOpt) Maximum number of retries to unplug VBD"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml156(td)
+msgid "ovs_integration_bridge = xapi1"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml157(td)
+#: ./doc/common/tables/nova-neutron.xml67(td)
+msgid "(StrOpt) Name of Integration Bridge used by Open vSwitch"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml160(td)
+msgid "remap_vbd_dev = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml161(td)
+msgid ""
+"(BoolOpt) Used to enable the remapping of VBD dev (Works around an issue in "
+"Ubuntu Maverick)"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml164(td)
+msgid "remap_vbd_dev_prefix = sd"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml165(td)
+msgid ""
+"(StrOpt) Specify prefix to remap VBD dev to (ex. /dev/xvdb -&gt; /dev/sdb)"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml168(td)
+msgid "running_timeout = 60"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml169(td)
+msgid "(IntOpt) Number of seconds to wait for instance to go to running state"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml172(td)
+msgid "sparse_copy = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml173(td)
+msgid ""
+"(BoolOpt) Whether to use sparse_copy for copying data on a resize down "
+"(False will use standard dd). This speeds up resizes down considerably since"
+" large runs of zeros won't have to be rsynced"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml176(td)
+msgid "sr_base_path = /var/run/sr-mount"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml180(td)
+msgid "sr_matching_filter = default-sr:true"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml181(td)
+msgid ""
+"(StrOpt) Filter for finding the SR to be used to install guest instances on."
+" To use the Local Storage in default XenServer/XCP installations set this "
+"flag to other-config:i18n-key=local-storage. To select an SR with a "
+"different matching criteria, you could set it to other-"
+"config:my_favorite_sr=true. On the other hand, to fall back on the Default "
+"SR, as displayed by XenCenter, set this flag to: default-sr:true"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml184(td)
+msgid "target_host = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml185(td)
+msgid "(StrOpt) The iSCSI Target Host"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml188(td)
+msgid "target_port = 3260"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml189(td)
+msgid "(StrOpt) The iSCSI Target Port, default is port 3260"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml192(td)
+msgid "torrent_base_url = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml193(td)
+msgid "(StrOpt) Base URL for torrent files."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml196(td)
+msgid "torrent_download_stall_cutoff = 600"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml197(td)
+msgid ""
+"(IntOpt) Number of seconds a download can remain at the same progress "
+"percentage w/o being considered a stall"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml200(td)
+msgid "torrent_images = none"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml201(td)
+msgid ""
+"(StrOpt) Whether or not to download images via Bit Torrent (all|some|none)."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml204(td)
+msgid "torrent_listen_port_end = 6891"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml205(td)
+msgid "(IntOpt) End of port range to listen on"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml208(td)
+msgid "torrent_listen_port_start = 6881"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml209(td)
+msgid "(IntOpt) Beginning of port range to listen on"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml212(td)
+msgid "torrent_max_last_accessed = 86400"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml213(td)
+msgid ""
+"(IntOpt) Cached torrent files not accessed within this number of seconds can"
+" be reaped"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml216(td)
+msgid "torrent_max_seeder_processes_per_host = 1"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml217(td)
+msgid ""
+"(IntOpt) Maximum number of seeder processes to run concurrently within a "
+"given dom0. (-1 = no limit)"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml220(td)
+msgid "torrent_seed_chance = 1.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml221(td)
+msgid "(FloatOpt) Probability that peer will become a seeder. (1.0 = 100%)"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml224(td)
+msgid "torrent_seed_duration = 3600"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml225(td)
+msgid ""
+"(IntOpt) Number of seconds after downloading an image via BitTorrent that it"
+" should be seeded for other peers."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml228(td)
+msgid "use_agent_default = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml229(td)
+msgid ""
+"(BoolOpt) Determines if the XenAPI agent should be used when the image used "
+"does not contain a hint to declare if the agent is present or not. The hint "
+"is a glance property \"xenapi_use_agent\" that has the value \"True\" or "
+"\"False\". Note that waiting for the agent when it is not present will "
+"significantly increase server boot times."
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml232(td)
+msgid "use_join_force = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml233(td)
+msgid "(BoolOpt) To use for hosts with different CPUs"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml236(td)
+msgid "vhd_coalesce_max_attempts = 20"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml237(td)
+msgid ""
+"(IntOpt) Max number of times to poll for VHD to coalesce. Used only if "
+"compute_driver=xenapi.XenAPIDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml240(td)
+msgid "vhd_coalesce_poll_interval = 5.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-xen.xml241(td)
+msgid ""
+"(FloatOpt) The interval used for polling of coalescing vhds. Used only if "
+"compute_driver=xenapi.XenAPIDriver"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml8(caption)
+#: ./doc/common/tables/heat-amqp.xml8(caption)
+#: ./doc/common/tables/keystone-amqp.xml8(caption)
+#: ./doc/common/tables/glance-amqp.xml8(caption)
+#: ./doc/common/tables/ceilometer-amqp.xml8(caption)
+msgid "Description of configuration options for amqp"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml30(td)
+msgid "conductor_queue = trove-conductor"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml31(td)
+#: ./doc/common/tables/trove-common.xml71(td)
+#: ./doc/common/tables/trove-api.xml39(td)
+#: ./doc/common/tables/trove-api.xml83(td)
+#: ./doc/common/tables/trove-api.xml91(td)
+#: ./doc/common/tables/trove-api.xml95(td)
+#: ./doc/common/tables/trove-dns.xml23(td)
+#: ./doc/common/tables/trove-dns.xml27(td)
+#: ./doc/common/tables/trove-dns.xml31(td)
+#: ./doc/common/tables/trove-dns.xml35(td)
+#: ./doc/common/tables/trove-dns.xml39(td)
+#: ./doc/common/tables/trove-dns.xml43(td)
+#: ./doc/common/tables/trove-dns.xml47(td)
+#: ./doc/common/tables/trove-dns.xml51(td)
+#: ./doc/common/tables/trove-dns.xml55(td)
+#: ./doc/common/tables/trove-dns.xml59(td)
+#: ./doc/common/tables/trove-dns.xml63(td)
+#: ./doc/common/tables/trove-dns.xml67(td)
+#: ./doc/common/tables/trove-dns.xml79(td)
+#: ./doc/common/tables/trove-volume.xml23(td)
+#: ./doc/common/tables/trove-volume.xml27(td)
+#: ./doc/common/tables/trove-volume.xml31(td)
+#: ./doc/common/tables/trove-volume.xml43(td)
+#: ./doc/common/tables/trove-heat.xml27(td)
+#: ./doc/common/tables/trove-rpc.xml27(td)
+#: ./doc/common/tables/trove-backup.xml39(td)
+#: ./doc/common/tables/trove-backup.xml55(td)
+#: ./doc/common/tables/trove-guestagent.xml39(td)
+#: ./doc/common/tables/trove-guestagent.xml51(td)
+#: ./doc/common/tables/trove-compute.xml23(td)
+#: ./doc/common/tables/trove-compute.xml27(td)
+#: ./doc/common/tables/trove-logging.xml23(td)
+#: ./doc/common/tables/trove-logging.xml71(td)
+#: ./doc/common/tables/trove-debug.xml55(td)
+#: ./doc/common/tables/trove-debug.xml59(td)
+#: ./doc/common/tables/trove-debug.xml63(td)
+#: ./doc/common/tables/trove-debug.xml67(td)
+#: ./doc/common/tables/trove-debug.xml71(td)
+#: ./doc/common/tables/trove-debug.xml75(td)
+#: ./doc/common/tables/trove-swift.xml23(td)
+msgid "(StrOpt) No help text available for this option."
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml34(td)
+#: ./doc/common/tables/glance-rabbitmq.xml22(td)
+#: ./doc/common/tables/keystone-amqp.xml30(td)
+#: ./doc/common/tables/ceilometer-exchange.xml26(td)
+#: ./doc/common/tables/cinder-rpc.xml34(td)
+#: ./doc/common/tables/nova-rpc_all.xml30(td)
+#: ./doc/common/tables/nova-rpc.xml30(td)
+msgid "control_exchange = openstack"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml39(td)
+#: ./doc/common/tables/heat-amqp.xml43(td)
+#: ./doc/common/tables/neutron-testing.xml27(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml23(td)
+msgid "(BoolOpt) If passed, use a fake RabbitMQ provider"
+msgstr "(論理値オプション) 指定されると、擬似 RabbitMQ プロバイダーを使用します。"
+
+#: ./doc/common/tables/trove-amqp.xml42(td)
+#: ./doc/common/tables/keystone-rabbit.xml30(td)
+#: ./doc/common/tables/glance-rabbitmq.xml34(td)
+#: ./doc/common/tables/heat-rabbitmq.xml22(td)
+#: ./doc/common/tables/neutron-kombu.xml22(td)
+#: ./doc/common/tables/nova-kombu.xml26(td)
+#: ./doc/common/tables/cinder-rpc.xml50(td)
+#: ./doc/common/tables/nova-rpc_all.xml38(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml26(td)
+msgid "kombu_ssl_ca_certs ="
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml43(td)
+#: ./doc/common/tables/heat-rabbitmq.xml23(td)
+#: ./doc/common/tables/neutron-kombu.xml23(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml27(td)
+msgid "(StrOpt) SSL certification authority file (valid only if SSL enabled)"
+msgstr "(文字列オプション) SSL 認証局ファイル (SSL が有効化されているときのみ有効)。"
+
+#: ./doc/common/tables/trove-amqp.xml46(td)
+#: ./doc/common/tables/keystone-rabbit.xml34(td)
+#: ./doc/common/tables/glance-rabbitmq.xml38(td)
+#: ./doc/common/tables/heat-rabbitmq.xml26(td)
+#: ./doc/common/tables/neutron-kombu.xml26(td)
+#: ./doc/common/tables/nova-kombu.xml30(td)
+#: ./doc/common/tables/cinder-rpc.xml54(td)
+#: ./doc/common/tables/nova-rpc_all.xml42(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml30(td)
+msgid "kombu_ssl_certfile ="
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml47(td)
+#: ./doc/common/tables/heat-rabbitmq.xml27(td)
+#: ./doc/common/tables/neutron-kombu.xml27(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml31(td)
+msgid "(StrOpt) SSL cert file (valid only if SSL enabled)"
+msgstr "(文字列オプション) SSL 証明書ファイル (SSL が有効化されているときのみ有効)。"
+
+#: ./doc/common/tables/trove-amqp.xml50(td)
+#: ./doc/common/tables/keystone-rabbit.xml38(td)
+#: ./doc/common/tables/glance-rabbitmq.xml42(td)
+#: ./doc/common/tables/heat-rabbitmq.xml30(td)
+#: ./doc/common/tables/neutron-kombu.xml30(td)
+#: ./doc/common/tables/nova-kombu.xml34(td)
+#: ./doc/common/tables/cinder-rpc.xml58(td)
+#: ./doc/common/tables/nova-rpc_all.xml46(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml34(td)
+msgid "kombu_ssl_keyfile ="
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml51(td)
+#: ./doc/common/tables/heat-rabbitmq.xml31(td)
+#: ./doc/common/tables/neutron-kombu.xml31(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml35(td)
+msgid "(StrOpt) SSL key file (valid only if SSL enabled)"
+msgstr "(文字列オプション) SSL キーファイル (SSL が有効化されているときのみ有効)。"
+
+#: ./doc/common/tables/trove-amqp.xml54(td)
+#: ./doc/common/tables/keystone-rabbit.xml42(td)
+#: ./doc/common/tables/glance-rabbitmq.xml46(td)
+#: ./doc/common/tables/heat-rabbitmq.xml34(td)
+#: ./doc/common/tables/neutron-kombu.xml34(td)
+#: ./doc/common/tables/nova-kombu.xml38(td)
+#: ./doc/common/tables/cinder-rpc.xml62(td)
+#: ./doc/common/tables/nova-rpc_all.xml50(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml38(td)
+msgid "kombu_ssl_version ="
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml55(td)
+#: ./doc/common/tables/heat-rabbitmq.xml35(td)
+msgid ""
+"(StrOpt) SSL version to use (valid only if SSL enabled). valid values are "
+"TLSv1, SSLv23 and SSLv3. SSLv2 may be available on some distributions"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml58(td)
+#: ./doc/common/tables/nova-common.xml58(td)
+#: ./doc/common/tables/heat-amqp.xml50(td)
+#: ./doc/common/tables/keystone-amqp.xml38(td)
+#: ./doc/common/tables/glance-amqp.xml30(td)
+#: ./doc/common/tables/cinder-rpc.xml74(td)
+#: ./doc/common/tables/neutron-notifier.xml30(td)
+#: ./doc/common/tables/ceilometer-amqp.xml30(td)
+msgid "notification_driver = []"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml59(td)
+#: ./doc/common/tables/heat-amqp.xml51(td)
+#: ./doc/common/tables/neutron-notifier.xml31(td)
+#: ./doc/common/tables/ceilometer-amqp.xml31(td)
+msgid "(MultiStrOpt) Driver or drivers to handle sending notifications"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml62(td)
+msgid ""
+"notification_service_id = {'couchbase': 'fa62fe68-74d9-4779-a24e-"
+"36f19602c415', 'mongodb': 'c8c907af-7375-456f-b929-b637ff9209ee', "
+"'cassandra': '459a230d-4e97-4344-9067-2a54a310b0ed', 'redis': 'b216ffc5-1947"
+"-456c-a4cf-70f94c05f7d0', 'mysql': '2f3ff068-2bfb-4f70-9a9d-a6bb65bc084b'}"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml63(td)
+msgid "(DictOpt) Unique ID to tag notification events."
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml66(td)
+#: ./doc/common/tables/nova-common.xml62(td)
+#: ./doc/common/tables/heat-amqp.xml54(td)
+#: ./doc/common/tables/keystone-amqp.xml42(td)
+#: ./doc/common/tables/glance-amqp.xml34(td)
+#: ./doc/common/tables/cinder-rpc.xml78(td)
+#: ./doc/common/tables/neutron-notifier.xml34(td)
+#: ./doc/common/tables/ceilometer-amqp.xml34(td)
+msgid "notification_topics = notifications"
+msgstr ""
+
+#: ./doc/common/tables/trove-amqp.xml67(td)
+#: ./doc/common/tables/neutron-notifier.xml35(td)
+msgid "(ListOpt) AMQP topic used for openstack notifications"
+msgstr ""
+
+#: ./doc/common/tables/glance-matchmaker.xml8(caption)
+msgid "Description of configuration options for matchmaker"
+msgstr ""
+
+#: ./doc/common/tables/glance-matchmaker.xml23(td)
+#: ./doc/common/tables/cinder-rpc.xml67(td)
+#: ./doc/common/tables/nova-rpc_all.xml55(td)
+#: ./doc/common/tables/nova-rpc.xml35(td)
+#: ./doc/common/tables/keystone-redis.xml27(td)
+msgid "(IntOpt) Heartbeat frequency."
+msgstr ""
+
+#: ./doc/common/tables/glance-matchmaker.xml34(td)
+#: ./doc/common/tables/cinder-rpc.xml242(td)
+#: ./doc/common/tables/nova-rpc_all.xml209(td)
+#: ./doc/common/tables/nova-rpc.xml73(td)
+#: ./doc/common/tables/keystone-redis.xml46(td)
+msgid "(StrOpt) Matchmaker ring file (JSON)."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml8(caption)
+#: ./doc/common/tables/glance-rabbitmq.xml8(caption)
+#: ./doc/common/tables/heat-rabbitmq.xml8(caption)
+#: ./doc/common/tables/trove-rabbitmq.xml8(caption)
+#: ./doc/common/tables/neutron-rabbitmq.xml8(caption)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml8(caption)
+msgid "Description of configuration options for rabbitmq"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml22(td)
+#: ./doc/common/tables/keystone-rabbit.xml46(td)
+#: ./doc/common/tables/glance-rabbitmq.xml50(td)
+#: ./doc/common/tables/heat-rabbitmq.xml38(td)
+#: ./doc/common/tables/trove-rabbitmq.xml22(td)
+#: ./doc/common/tables/cinder-rpc.xml134(td)
+#: ./doc/common/tables/nova-rpc_all.xml102(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml22(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml42(td)
+msgid "rabbit_ha_queues = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml23(td)
+#: ./doc/common/tables/keystone-rabbit.xml47(td)
+#: ./doc/common/tables/glance-rabbitmq.xml51(td)
+#: ./doc/common/tables/cinder-rpc.xml135(td)
+#: ./doc/common/tables/nova-rpc_all.xml103(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml23(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml43(td)
+msgid ""
+"(BoolOpt) Use HA queues in RabbitMQ (x-ha-policy: all). If you change this "
+"option, you must wipe the RabbitMQ database."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml26(td)
+#: ./doc/common/tables/keystone-rabbit.xml50(td)
+#: ./doc/common/tables/glance-rabbitmq.xml54(td)
+#: ./doc/common/tables/heat-rabbitmq.xml42(td)
+#: ./doc/common/tables/trove-rabbitmq.xml26(td)
+#: ./doc/common/tables/cinder-rpc.xml138(td)
+#: ./doc/common/tables/nova-rpc_all.xml106(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml26(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml46(td)
+msgid "rabbit_host = localhost"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml27(td)
+#: ./doc/common/tables/keystone-rabbit.xml51(td)
+#: ./doc/common/tables/glance-rabbitmq.xml55(td)
+#: ./doc/common/tables/cinder-rpc.xml139(td)
+#: ./doc/common/tables/nova-rpc_all.xml107(td)
+msgid "(StrOpt) The RabbitMQ broker address where a single node is used."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml30(td)
+#: ./doc/common/tables/keystone-rabbit.xml54(td)
+#: ./doc/common/tables/glance-rabbitmq.xml58(td)
+#: ./doc/common/tables/heat-rabbitmq.xml46(td)
+#: ./doc/common/tables/trove-rabbitmq.xml30(td)
+#: ./doc/common/tables/cinder-rpc.xml142(td)
+#: ./doc/common/tables/nova-rpc_all.xml110(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml30(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml50(td)
+msgid "rabbit_hosts = $rabbit_host:$rabbit_port"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml31(td)
+#: ./doc/common/tables/keystone-rabbit.xml55(td)
+#: ./doc/common/tables/glance-rabbitmq.xml59(td)
+#: ./doc/common/tables/cinder-rpc.xml143(td)
+#: ./doc/common/tables/nova-rpc_all.xml111(td)
+msgid "(ListOpt) RabbitMQ HA cluster host:port pairs."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml34(td)
+#: ./doc/common/tables/keystone-rabbit.xml58(td)
+#: ./doc/common/tables/glance-rabbitmq.xml62(td)
+#: ./doc/common/tables/cinder-rpc.xml146(td)
+#: ./doc/common/tables/nova-rpc_all.xml114(td)
+msgid "rabbit_login_method = AMQPLAIN"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml35(td)
+#: ./doc/common/tables/keystone-rabbit.xml59(td)
+#: ./doc/common/tables/glance-rabbitmq.xml63(td)
+#: ./doc/common/tables/cinder-rpc.xml147(td)
+#: ./doc/common/tables/nova-rpc_all.xml115(td)
+msgid "(StrOpt) the RabbitMQ login method"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml38(td)
+#: ./doc/common/tables/keystone-rabbit.xml62(td)
+#: ./doc/common/tables/glance-rabbitmq.xml66(td)
+#: ./doc/common/tables/heat-rabbitmq.xml50(td)
+#: ./doc/common/tables/trove-rabbitmq.xml34(td)
+#: ./doc/common/tables/cinder-rpc.xml150(td)
+#: ./doc/common/tables/nova-rpc_all.xml118(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml34(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml54(td)
+msgid "rabbit_max_retries = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml39(td)
+#: ./doc/common/tables/keystone-rabbit.xml63(td)
+#: ./doc/common/tables/glance-rabbitmq.xml67(td)
+#: ./doc/common/tables/cinder-rpc.xml151(td)
+#: ./doc/common/tables/nova-rpc_all.xml119(td)
+msgid ""
+"(IntOpt) Maximum number of RabbitMQ connection retries. Default is 0 "
+"(infinite retry count)."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml42(td)
+#: ./doc/common/tables/keystone-rabbit.xml66(td)
+#: ./doc/common/tables/glance-rabbitmq.xml70(td)
+#: ./doc/common/tables/heat-rabbitmq.xml54(td)
+#: ./doc/common/tables/trove-rabbitmq.xml38(td)
+#: ./doc/common/tables/cinder-rpc.xml154(td)
+#: ./doc/common/tables/nova-rpc_all.xml122(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml38(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml58(td)
+msgid "rabbit_password = guest"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml43(td)
+#: ./doc/common/tables/keystone-rabbit.xml67(td)
+#: ./doc/common/tables/glance-rabbitmq.xml71(td)
+#: ./doc/common/tables/cinder-rpc.xml155(td)
+#: ./doc/common/tables/nova-rpc_all.xml123(td)
+msgid "(StrOpt) The RabbitMQ password."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml46(td)
+#: ./doc/common/tables/keystone-rabbit.xml70(td)
+#: ./doc/common/tables/glance-rabbitmq.xml74(td)
+#: ./doc/common/tables/heat-rabbitmq.xml58(td)
+#: ./doc/common/tables/trove-rabbitmq.xml42(td)
+#: ./doc/common/tables/cinder-rpc.xml158(td)
+#: ./doc/common/tables/nova-rpc_all.xml126(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml42(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml62(td)
+msgid "rabbit_port = 5672"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml47(td)
+#: ./doc/common/tables/keystone-rabbit.xml71(td)
+#: ./doc/common/tables/glance-rabbitmq.xml75(td)
+#: ./doc/common/tables/cinder-rpc.xml159(td)
+#: ./doc/common/tables/nova-rpc_all.xml127(td)
+msgid "(IntOpt) The RabbitMQ broker port where a single node is used."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml50(td)
+#: ./doc/common/tables/keystone-rabbit.xml74(td)
+#: ./doc/common/tables/glance-rabbitmq.xml78(td)
+#: ./doc/common/tables/heat-rabbitmq.xml62(td)
+#: ./doc/common/tables/trove-rabbitmq.xml46(td)
+#: ./doc/common/tables/cinder-rpc.xml162(td)
+#: ./doc/common/tables/nova-rpc_all.xml130(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml46(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml66(td)
+msgid "rabbit_retry_backoff = 2"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml51(td)
+#: ./doc/common/tables/keystone-rabbit.xml75(td)
+#: ./doc/common/tables/glance-rabbitmq.xml79(td)
+#: ./doc/common/tables/cinder-rpc.xml163(td)
+#: ./doc/common/tables/nova-rpc_all.xml131(td)
+msgid ""
+"(IntOpt) How long to backoff for between retries when connecting to "
+"RabbitMQ."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml54(td)
+#: ./doc/common/tables/keystone-rabbit.xml78(td)
+#: ./doc/common/tables/glance-rabbitmq.xml82(td)
+#: ./doc/common/tables/heat-rabbitmq.xml66(td)
+#: ./doc/common/tables/trove-rabbitmq.xml50(td)
+#: ./doc/common/tables/cinder-rpc.xml166(td)
+#: ./doc/common/tables/nova-rpc_all.xml134(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml50(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml70(td)
+msgid "rabbit_retry_interval = 1"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml55(td)
+#: ./doc/common/tables/keystone-rabbit.xml79(td)
+#: ./doc/common/tables/glance-rabbitmq.xml83(td)
+#: ./doc/common/tables/cinder-rpc.xml167(td)
+#: ./doc/common/tables/nova-rpc_all.xml135(td)
+msgid "(IntOpt) How frequently to retry connecting with RabbitMQ."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml58(td)
+#: ./doc/common/tables/keystone-rabbit.xml82(td)
+#: ./doc/common/tables/glance-rabbitmq.xml86(td)
+#: ./doc/common/tables/heat-rabbitmq.xml70(td)
+#: ./doc/common/tables/trove-rabbitmq.xml54(td)
+#: ./doc/common/tables/cinder-rpc.xml170(td)
+#: ./doc/common/tables/nova-rpc_all.xml138(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml54(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml74(td)
+msgid "rabbit_use_ssl = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml59(td)
+#: ./doc/common/tables/keystone-rabbit.xml83(td)
+#: ./doc/common/tables/glance-rabbitmq.xml87(td)
+#: ./doc/common/tables/cinder-rpc.xml171(td)
+#: ./doc/common/tables/nova-rpc_all.xml139(td)
+msgid "(BoolOpt) Connect over SSL for RabbitMQ."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml62(td)
+#: ./doc/common/tables/keystone-rabbit.xml86(td)
+#: ./doc/common/tables/glance-rabbitmq.xml90(td)
+#: ./doc/common/tables/heat-rabbitmq.xml74(td)
+#: ./doc/common/tables/trove-rabbitmq.xml58(td)
+#: ./doc/common/tables/cinder-rpc.xml174(td)
+#: ./doc/common/tables/nova-rpc_all.xml142(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml58(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml78(td)
+msgid "rabbit_userid = guest"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml63(td)
+#: ./doc/common/tables/keystone-rabbit.xml87(td)
+#: ./doc/common/tables/glance-rabbitmq.xml91(td)
+#: ./doc/common/tables/cinder-rpc.xml175(td)
+#: ./doc/common/tables/nova-rpc_all.xml143(td)
+msgid "(StrOpt) The RabbitMQ userid."
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml66(td)
+#: ./doc/common/tables/keystone-rabbit.xml90(td)
+#: ./doc/common/tables/glance-rabbitmq.xml94(td)
+#: ./doc/common/tables/heat-rabbitmq.xml78(td)
+#: ./doc/common/tables/trove-rabbitmq.xml62(td)
+#: ./doc/common/tables/cinder-rpc.xml178(td)
+#: ./doc/common/tables/nova-rpc_all.xml146(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml62(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml82(td)
+msgid "rabbit_virtual_host = /"
+msgstr ""
+
+#: ./doc/common/tables/nova-rabbitmq.xml67(td)
+#: ./doc/common/tables/keystone-rabbit.xml91(td)
+#: ./doc/common/tables/glance-rabbitmq.xml95(td)
+#: ./doc/common/tables/cinder-rpc.xml179(td)
+#: ./doc/common/tables/nova-rpc_all.xml147(td)
+msgid "(StrOpt) The RabbitMQ virtual host."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_cisco.xml8(caption)
+msgid "Description of configuration options for ml2_cisco"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_cisco.xml22(td)
+msgid "managed_physical_network = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_cisco.xml23(td)
+msgid "(StrOpt) The physical network managed by the switches."
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml22(td)
+msgid "allow_instance_snapshots = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml23(td)
+msgid "(BoolOpt) Permit instance snapshot operations."
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml26(td)
+msgid "allow_migrate_to_same_host = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml27(td)
+msgid ""
+"(BoolOpt) Allow migrate machine to the same host. Useful when testing in "
+"single-host environments."
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml30(td)
+msgid "allow_resize_to_same_host = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml31(td)
+msgid ""
+"(BoolOpt) Allow destination machine to match source for resize. Useful when "
+"testing in single-host environments."
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml34(td)
+#: ./doc/common/tables/cinder-quota.xml22(td)
+msgid "max_age = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml35(td)
+msgid "(IntOpt) Number of seconds between subsequent usage refreshes"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml38(td)
+msgid "max_local_block_devices = 3"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml39(td)
+msgid ""
+"(IntOpt) Maximum number of devices that will result in a local image being "
+"created on the hypervisor node. Setting this to 0 means nova will allow only"
+" boot from volume. A negative number means unlimited."
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml42(td)
+msgid "osapi_compute_unique_server_name_scope ="
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml43(td)
+msgid ""
+"(StrOpt) When set, compute API will consider duplicate hostnames invalid "
+"within the specified scope, regardless of case. Should be empty, \"project\""
+" or \"global\"."
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml46(td)
+#: ./doc/common/tables/cinder-api.xml50(td)
+msgid "osapi_max_limit = 1000"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml47(td)
+msgid ""
+"(IntOpt) The maximum number of items returned in a single response from a "
+"collection resource"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml50(td)
+#: ./doc/common/tables/cinder-api.xml54(td)
+msgid "osapi_max_request_body_size = 114688"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml51(td)
+msgid "(IntOpt) The maximum body size per each osapi request(bytes)"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml54(td)
+msgid "password_length = 12"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml55(td)
+msgid "(IntOpt) Length of generated instance admin passwords"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml59(td)
+#: ./doc/common/tables/cinder-common.xml139(td)
+msgid "(StrOpt) Rule checked when requested rule is not found"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml63(td)
+#: ./doc/common/tables/cinder-common.xml143(td)
+msgid "(StrOpt) JSON file representing policy"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml66(td)
+#: ./doc/common/tables/cinder-quota.xml42(td)
+msgid "reservation_expire = 86400"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml67(td)
+msgid "(IntOpt) Number of seconds until a reservation expires"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml70(td)
+msgid "resize_fs_using_block_device = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml71(td)
+msgid ""
+"(BoolOpt) Attempt to resize the filesystem by accessing the image over a "
+"block device. This is done by the host and may not be necessary if the image"
+" contains a recent version of cloud-init. Possible mechanisms require the "
+"nbd driver (for qcow and raw), or loop (for raw)."
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml74(td)
+#: ./doc/common/tables/cinder-common.xml202(td)
+msgid "until_refresh = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-policy.xml75(td)
+msgid "(IntOpt) Count of reservations until usage is refreshed"
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml8(caption)
+msgid "Description of configuration options for identity"
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml19(th)
+msgid "[identity]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml22(td)
+msgid "default_domain_id = default"
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml23(td)
+msgid ""
+"(StrOpt) This references the domain to use for all Identity API v2 requests "
+"(which are not aware of domains). A domain with this ID will be created for "
+"you by keystone-manage db_sync in migration 008. The domain referenced by "
+"this ID cannot be deleted on the v3 API, to prevent accidentally breaking "
+"the v2 API. There is nothing special about this domain, other than the fact "
+"that it must exist to order to maintain support for your v2 clients."
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml26(td)
+msgid "domain_config_dir = /etc/keystone/domains"
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml27(td)
+msgid ""
+"(StrOpt) Path for Keystone to locate the domain specificidentity "
+"configuration files if domain_specific_drivers_enabled is set to true."
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml30(td)
+msgid "domain_specific_drivers_enabled = False"
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml31(td)
+msgid ""
+"(BoolOpt) A subset (or all) of domains can have their own identity driver, "
+"each with their own partial configuration file in a domain configuration "
+"directory. Only values specific to the domain need to be placed in the "
+"domain specific configuration file. This feature is disabled by default; set"
+" to True to enable."
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml34(td)
+msgid "driver = keystone.identity.backends.sql.Identity"
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml35(td)
+msgid "(StrOpt) Keystone Identity backend driver."
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml39(td)
+msgid ""
+"(IntOpt) Maximum number of entities that will be returned in an identity "
+"collection."
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml42(td)
+msgid "max_password_length = 4096"
+msgstr ""
+
+#: ./doc/common/tables/keystone-identity.xml43(td)
+msgid ""
+"(IntOpt) Maximum supported length for user passwords; decrease to improve "
+"performance."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-inspector.xml8(caption)
+msgid "Description of configuration options for inspector"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-inspector.xml22(td)
+msgid "hypervisor_inspector = libvirt"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-inspector.xml23(td)
+msgid "(StrOpt) Inspector to use for inspecting the hypervisor layer."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-inspector.xml26(td)
+msgid "libvirt_type = kvm"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-inspector.xml27(td)
+msgid ""
+"(StrOpt) Libvirt domain type (valid options are: kvm, lxc, qemu, uml, xen)."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-inspector.xml30(td)
+msgid "libvirt_uri ="
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-inspector.xml31(td)
+msgid ""
+"(StrOpt) Override the default libvirt URI (which is dependent on "
+"libvirt_type)."
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml22(td)
+msgid ""
+"scheduler_default_filters = AvailabilityZoneFilter, CapacityFilter, "
+"CapabilitiesFilter"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml23(td)
+#: ./doc/common/tables/nova-scheduling.xml79(td)
+msgid ""
+"(ListOpt) Which filter class names to use for filtering hosts when not "
+"specified in the request."
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml26(td)
+msgid "scheduler_default_weighers = CapacityWeigher"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml27(td)
+msgid "(ListOpt) Which weigher class names to use for weighing hosts."
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml30(td)
+msgid "scheduler_driver = cinder.scheduler.filter_scheduler.FilterScheduler"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml31(td)
+msgid "(StrOpt) Default scheduler driver to use"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml34(td)
+msgid "scheduler_host_manager = cinder.scheduler.host_manager.HostManager"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml35(td)
+#: ./doc/common/tables/nova-scheduling.xml91(td)
+msgid "(StrOpt) The scheduler host manager class to use"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml38(td)
+#: ./doc/common/tables/nova-scheduling.xml98(td)
+msgid "scheduler_json_config_location ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml39(td)
+#: ./doc/common/tables/nova-scheduling.xml99(td)
+msgid "(StrOpt) Absolute path to scheduler configuration JSON file."
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml42(td)
+msgid "scheduler_manager = cinder.scheduler.manager.SchedulerManager"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml43(td)
+msgid "(StrOpt) full class name for the Manager for scheduler"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml46(td)
+#: ./doc/common/tables/nova-scheduling.xml106(td)
+msgid "scheduler_max_attempts = 3"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml47(td)
+msgid "(IntOpt) Maximum number of attempts to schedule an volume"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml50(td)
+msgid "scheduler_topic = cinder-scheduler"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scheduler.xml51(td)
+msgid "(StrOpt) the topic scheduler nodes listen on"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_cassandra.xml8(caption)
+msgid "Description of configuration options for db_cassandra"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_cassandra.xml19(th)
+msgid "[cassandra]"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_cassandra.xml22(td)
+#: ./doc/common/tables/trove-db_couchbase.xml22(td)
+#: ./doc/common/tables/trove-db_mongodb.xml22(td)
+#: ./doc/common/tables/trove-db_redis.xml22(td)
+msgid "backup_strategy = None"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_cassandra.xml26(td)
+msgid "mount_point = /var/lib/cassandra"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_cassandra.xml30(td)
+msgid "tcp_ports = 7000, 7001, 9042, 9160"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_cassandra.xml38(td)
+msgid "usage_timeout = 600"
+msgstr ""
+
+#: ./doc/common/tables/neutron-logging.xml26(td)
+#: ./doc/common/tables/trove-common.xml34(td)
+#: ./doc/common/tables/heat-logging.xml22(td)
+msgid ""
+"default_log_levels = amqp=WARN, amqplib=WARN, boto=WARN, qpid=WARN, "
+"sqlalchemy=WARN, suds=INFO, iso8601=WARN"
+msgstr ""
+
+#: ./doc/common/tables/neutron-logging.xml27(td)
+#: ./doc/common/tables/trove-common.xml35(td)
+#: ./doc/common/tables/heat-logging.xml23(td)
+#: ./doc/common/tables/nova-logging.xml27(td)
+msgid "(ListOpt) list of logger=LEVEL pairs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-logging.xml31(td)
+#: ./doc/common/tables/heat-debug.xml35(td)
+#: ./doc/common/tables/nova-logging.xml31(td)
+#: ./doc/common/tables/trove-debug.xml39(td)
+msgid "(BoolOpt) make deprecations fatal"
+msgstr ""
+
+#: ./doc/common/tables/neutron-logging.xml63(td)
+#: ./doc/common/tables/heat-logging.xml55(td)
+#: ./doc/common/tables/nova-logging.xml67(td)
+#: ./doc/common/tables/trove-logging.xml55(td)
+msgid "(StrOpt) format string to use for log messages with context"
+msgstr ""
+
+#: ./doc/common/tables/neutron-logging.xml67(td)
+#: ./doc/common/tables/heat-logging.xml59(td)
+#: ./doc/common/tables/nova-logging.xml71(td)
+#: ./doc/common/tables/trove-logging.xml59(td)
+msgid "(StrOpt) data to append to log format when level is DEBUG"
+msgstr ""
+
+#: ./doc/common/tables/neutron-logging.xml71(td)
+#: ./doc/common/tables/heat-logging.xml63(td)
+#: ./doc/common/tables/nova-logging.xml75(td)
+#: ./doc/common/tables/trove-logging.xml63(td)
+msgid "(StrOpt) format string to use for log messages without context"
+msgstr ""
+
+#: ./doc/common/tables/neutron-logging.xml75(td)
+#: ./doc/common/tables/heat-logging.xml67(td)
+#: ./doc/common/tables/nova-logging.xml79(td)
+#: ./doc/common/tables/trove-logging.xml67(td)
+msgid "(StrOpt) prefix each line of exception output with this format"
+msgstr ""
+
+#: ./doc/common/tables/neutron-logging.xml79(td)
+#: ./doc/common/tables/heat-notification.xml27(td)
+#: ./doc/common/tables/nova-logging.xml83(td)
+#: ./doc/common/tables/trove-logging.xml75(td)
+msgid "(BoolOpt) publish error events"
+msgstr ""
+
+#: ./doc/common/tables/neutron-logging.xml83(td)
+#: ./doc/common/tables/heat-logging.xml71(td)
+#: ./doc/common/tables/nova-logging.xml87(td)
+#: ./doc/common/tables/trove-logging.xml79(td)
+msgid "(StrOpt) syslog facility to receive log lines"
+msgstr ""
+
+#: ./doc/common/tables/neutron-logging.xml86(td)
+#: ./doc/common/tables/neutron-nec.xml58(td)
+msgid "use_ssl = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-logging.xml87(td)
+msgid "(BoolOpt) Enable SSL on the API server"
+msgstr ""
+
+#: ./doc/common/tables/neutron-logging.xml95(td)
+#: ./doc/common/tables/heat-logging.xml79(td)
+#: ./doc/common/tables/trove-logging.xml87(td)
+msgid "(BoolOpt) Use syslog for logging."
+msgstr "(論理値オプション) ロギングのために syslog の利用。"
+
+#: ./doc/common/tables/nova-availabilityzones.xml8(caption)
+msgid "Description of configuration options for availabilityzones"
+msgstr ""
+
+#: ./doc/common/tables/nova-availabilityzones.xml22(td)
+msgid "default_availability_zone = nova"
+msgstr ""
+
+#: ./doc/common/tables/nova-availabilityzones.xml23(td)
+msgid "(StrOpt) Default compute node availability_zone"
+msgstr ""
+
+#: ./doc/common/tables/nova-availabilityzones.xml26(td)
+msgid "default_schedule_zone = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-availabilityzones.xml27(td)
+msgid "(StrOpt) Availability zone to use when user doesn't specify one"
+msgstr ""
+
+#: ./doc/common/tables/nova-availabilityzones.xml30(td)
+msgid "internal_service_availability_zone = internal"
+msgstr ""
+
+#: ./doc/common/tables/nova-availabilityzones.xml31(td)
+msgid "(StrOpt) The availability_zone to show internal services under"
+msgstr ""
+
+#: ./doc/common/tables/keystone-catalog.xml8(caption)
+msgid "Description of configuration options for catalog"
+msgstr ""
+
+#: ./doc/common/tables/keystone-catalog.xml19(th)
+msgid "[catalog]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-catalog.xml22(td)
+msgid "driver = keystone.catalog.backends.sql.Catalog"
+msgstr ""
+
+#: ./doc/common/tables/keystone-catalog.xml23(td)
+msgid "(StrOpt) Keystone catalog backend driver."
+msgstr ""
+
+#: ./doc/common/tables/keystone-catalog.xml27(td)
+msgid ""
+"(IntOpt) Maximum number of entities that will be returned in a catalog "
+"collection."
+msgstr ""
+
+#: ./doc/common/tables/keystone-catalog.xml30(td)
+msgid "template_file = default_catalog.templates"
+msgstr ""
+
+#: ./doc/common/tables/keystone-catalog.xml31(td)
+msgid ""
+"(StrOpt) Catalog template file name for use with the template catalog "
+"backend."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml8(caption)
+msgid "Description of configuration options for netapp_eseries_iscsi"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml22(td)
+msgid "netapp_controller_ips = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml23(td)
+msgid ""
+"(StrOpt) This option is only utilized when the storage family is configured "
+"to eseries. This option is used to restrict provisioning to the specified "
+"controllers. Specify the value of this option to be a comma separated list "
+"of controller hostnames or IP addresses to be used for provisioning."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml34(td)
+msgid "netapp_sa_password = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml35(td)
+msgid "(StrOpt) Password for the NetApp E-Series storage array."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml50(td)
+msgid "netapp_storage_pools = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml51(td)
+msgid ""
+"(StrOpt) This option is used to restrict provisioning to the specified "
+"storage pools. Only dynamic disk pools are currently supported. Specify the "
+"value of this option to be a comma separated list of disk pool names to be "
+"used for provisioning."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml58(td)
+msgid "netapp_webservice_path = /devmgr/v2"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml59(td)
+msgid ""
+"(StrOpt) This option is used to specify the path to the E-Series proxy "
+"application on a proxy server. The value is combined with the value of the "
+"netapp_transport_type, netapp_server_hostname, and netapp_server_port "
+"options to create the URL used by the driver to connect to the proxy "
+"application."
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml8(caption)
+#: ./doc/common/tables/nova-rootwrap.xml8(caption)
+#: ./doc/common/tables/cinder-rootwrap.xml8(caption)
+msgid "Description of configuration options for rootwrap"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml22(td)
+msgid ""
+"filters_path = "
+"/etc/neutron/rootwrap.d,/usr/share/neutron/rootwrap,/etc/quantum/rootwrap.d,/usr/share/quantum/rootwrap"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml23(td)
+#: ./doc/common/tables/nova-rootwrap.xml23(td)
+#: ./doc/common/tables/cinder-rootwrap.xml23(td)
+msgid ""
+"List of directories to load filter definitions from (separated by ','). "
+"These directories MUST all be only writeable by root !"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml26(td)
+#: ./doc/common/tables/nova-rootwrap.xml26(td)
+#: ./doc/common/tables/cinder-rootwrap.xml26(td)
+msgid "exec_dirs = /sbin,/usr/sbin,/bin,/usr/bin"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml27(td)
+#: ./doc/common/tables/nova-rootwrap.xml27(td)
+#: ./doc/common/tables/cinder-rootwrap.xml27(td)
+msgid ""
+"List of directories to search executables in, in case filters do not "
+"explicitely specify a full path (separated by ',') If not specified, "
+"defaults to system PATH environment variable. These directories MUST all be "
+"only writeable by root !"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml31(td)
+#: ./doc/common/tables/nova-rootwrap.xml31(td)
+#: ./doc/common/tables/cinder-rootwrap.xml31(td)
+msgid "Enable logging to syslog Default value is False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml34(td)
+#: ./doc/common/tables/nova-rootwrap.xml34(td)
+#: ./doc/common/tables/cinder-rootwrap.xml34(td)
+msgid "syslog_log_facility = syslog"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml35(td)
+#: ./doc/common/tables/cinder-rootwrap.xml35(td)
+msgid ""
+"Which syslog facility to use. Valid values include auth, authpriv, syslog, "
+"local0, local1... Default value is 'syslog'"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml38(td)
+#: ./doc/common/tables/nova-rootwrap.xml38(td)
+#: ./doc/common/tables/cinder-rootwrap.xml38(td)
+msgid "syslog_log_level = ERROR"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml39(td)
+#: ./doc/common/tables/nova-rootwrap.xml39(td)
+#: ./doc/common/tables/cinder-rootwrap.xml39(td)
+msgid ""
+"Which messages to log. INFO means log all usage ERROR means only log "
+"unsuccessful attempts"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml42(th)
+msgid "[xenapi]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml45(td)
+msgid "xenapi_connection_url = &lt;None&gt;"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml46(td)
+msgid ""
+"XenAPI configuration is only required by the L2 agent if it is to target a "
+"XenServer/XCP compute host's dom0."
+msgstr ""
+
+#: ./doc/common/tables/neutron-rootwrap.xml53(td)
+msgid "xenapi_connection_password = &lt;None&gt;"
+msgstr ""
+
+#: ./doc/common/tables/cinder-auth.xml22(td)
+#: ./doc/common/tables/glance-registry.xml38(td)
+#: ./doc/common/tables/nova-authentication.xml22(td)
+msgid "auth_strategy = noauth"
+msgstr ""
+
+#: ./doc/common/tables/cinder-auth.xml23(td)
+msgid ""
+"(StrOpt) The strategy to use for auth. Supports noauth, keystone, and "
+"deprecated."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml7(literal)
+msgid "[swift-constraints]"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml7(literal)
+#: ./doc/common/tables/swift-swift-swift-hash.xml7(literal)
+msgid "swift.conf-sample"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml18(td)
+msgid "max_file_size = 5368709122"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml18(td)
+msgid ""
+"The largest normal object that can be saved in the cluster. This is also the"
+" limit on the size of each segment of a large object when using the large "
+"object manifest support. This value is set in bytes. Setting it to lower "
+"than 1MiB will cause some tests to fail. It is STRONGLY recommended to leave"
+" this value at the default (5 * 2**30 + 2)."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml29(td)
+msgid "max_meta_name_length = 128"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml29(td)
+msgid ""
+"The maximum number of bytes in the utf8 encoding of the name portion of a "
+"metadata header."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml34(td)
+msgid "max_meta_value_length = 256"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml34(td)
+msgid "The max number of bytes in the utf8 encoding of a metadata value."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml38(td)
+msgid "max_meta_count = 90"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml38(td)
+msgid ""
+"The maximum number of metadata keys that can be stored on a single account, "
+"container, or object."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml43(td)
+msgid "max_meta_overall_size = 4096"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml43(td)
+msgid ""
+"The maximum number of bytes in the utf8 encoding of the metadata (keys + "
+"values)."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml48(td)
+msgid "max_header_size = 8192"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml48(td)
+msgid "The maximum number of bytes in the utf8 encoding of each header."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml52(td)
+msgid "max_object_name_length = 1024"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml52(td)
+msgid "The maximum number of bytes in the utf8 encoding of an object name."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml56(td)
+msgid "container_listing_limit = 10000"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml56(td)
+msgid ""
+"The default (and maximum) number of items returned for a container listing "
+"request."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml61(td)
+msgid "account_listing_limit = 10000"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml61(td)
+msgid ""
+"The default (and maximum) number of items returned for an account listing "
+"request."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml65(td)
+msgid "max_account_name_length = 256"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml65(td)
+msgid "The maximum number of bytes in the utf8 encoding of an account name."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml69(td)
+msgid "max_container_name_length = 256"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-constraints.xml69(td)
+msgid "The maximum number of bytes in the utf8 encoding of a container name."
+msgstr ""
+
+#: ./doc/common/tables/heat-qpid.xml54(td)
+#: ./doc/common/tables/nova-qpid.xml54(td)
+#: ./doc/common/tables/glance-qpid.xml54(td)
+#: ./doc/common/tables/cinder-rpc.xml126(td)
+#: ./doc/common/tables/nova-rpc_all.xml94(td)
+#: ./doc/common/tables/neutron-qpid.xml54(td)
+#: ./doc/common/tables/keystone-qpid.xml54(td)
+#: ./doc/common/tables/ceilometer-qpid.xml54(td)
+msgid "qpid_topology_version = 1"
+msgstr ""
+
+#: ./doc/common/tables/heat-qpid.xml55(td)
+#: ./doc/common/tables/nova-qpid.xml55(td)
+#: ./doc/common/tables/glance-qpid.xml55(td)
+#: ./doc/common/tables/cinder-rpc.xml127(td)
+#: ./doc/common/tables/nova-rpc_all.xml95(td)
+#: ./doc/common/tables/neutron-qpid.xml55(td)
+#: ./doc/common/tables/keystone-qpid.xml55(td)
+#: ./doc/common/tables/ceilometer-qpid.xml55(td)
+msgid ""
+"(IntOpt) The qpid topology version to use. Version 1 is what was originally "
+"used by impl_qpid. Version 2 includes some backwards-incompatible changes "
+"that allow broker federation to work. Users should update to version 2 when "
+"they are able to take everything down, as it requires a clean break."
+msgstr ""
+
+#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml7(literal)
+msgid "[filter:catch_errors]"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-expirer-filter-catch_errors.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml18(td)
+msgid "use = egg:swift#catch_errors"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml7(literal)
+msgid "[filter:slo]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml18(td)
+msgid "use = egg:swift#slo"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml21(td)
+msgid "max_manifest_segments = 1000"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml24(td)
+msgid "max_manifest_size = 2097152"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml27(td)
+msgid "min_segment_size = 1048576"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml21(td)
+msgid "rate_limit_after_segment = 10"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml30(td)
+#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml21(td)
+msgid ""
+"Rate limit the download of large object segments after this segment is "
+"downloaded."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml33(td)
+msgid "rate_limit_segments_per_sec = 0"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml33(td)
+#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml24(td)
+msgid ""
+"Rate limit large object downloads at this rate. contact for a normal "
+"request. You can use '* replicas' at the end to have it use the number given"
+" times the number of replicas for the ring being used for the request. "
+"paste.deploy to use for auth. To use tempauth set to: `egg:swift#tempauth` "
+"each request"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-slo.xml36(td)
+#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml27(td)
+msgid "max_get_time = 86400"
+msgstr ""
+
+#: ./doc/common/tables/nova-zookeeper.xml8(caption)
+msgid "Description of configuration options for zookeeper"
+msgstr ""
+
+#: ./doc/common/tables/nova-zookeeper.xml19(th)
+msgid "[zookeeper]"
+msgstr ""
+
+#: ./doc/common/tables/nova-zookeeper.xml22(td)
+msgid "address = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-zookeeper.xml23(td)
+msgid ""
+"(StrOpt) The ZooKeeper addresses for servicegroup service in the format of "
+"host1:port,host2:port,host3:port"
+msgstr ""
+
+#: ./doc/common/tables/nova-zookeeper.xml26(td)
+msgid "recv_timeout = 4000"
+msgstr ""
+
+#: ./doc/common/tables/nova-zookeeper.xml27(td)
+msgid "(IntOpt) The recv_timeout parameter for the zk session"
+msgstr ""
+
+#: ./doc/common/tables/nova-zookeeper.xml30(td)
+msgid "sg_prefix = /servicegroups"
+msgstr ""
+
+#: ./doc/common/tables/nova-zookeeper.xml31(td)
+msgid "(StrOpt) The prefix used in ZooKeeper to store ephemeral nodes"
+msgstr ""
+
+#: ./doc/common/tables/nova-zookeeper.xml34(td)
+msgid "sg_retry_interval = 5"
+msgstr ""
+
+#: ./doc/common/tables/nova-zookeeper.xml35(td)
+msgid "(IntOpt) Number of seconds to wait until retrying to join the session"
+msgstr ""
+
+#: ./doc/common/tables/nova-keymgr.xml8(caption)
+#: ./doc/common/tables/cinder-keymgr.xml8(caption)
+msgid "Description of configuration options for keymgr"
+msgstr ""
+
+#: ./doc/common/tables/nova-keymgr.xml19(th)
+#: ./doc/common/tables/cinder-keymgr.xml19(th)
+msgid "[keymgr]"
+msgstr ""
+
+#: ./doc/common/tables/nova-keymgr.xml22(td)
+msgid "api_class = nova.keymgr.conf_key_mgr.ConfKeyManager"
+msgstr ""
+
+#: ./doc/common/tables/nova-keymgr.xml23(td)
+#: ./doc/common/tables/cinder-keymgr.xml23(td)
+msgid "(StrOpt) The full class name of the key manager API class"
+msgstr ""
+
+#: ./doc/common/tables/nova-keymgr.xml26(td)
+#: ./doc/common/tables/cinder-keymgr.xml26(td)
+msgid "fixed_key = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-keymgr.xml27(td)
+#: ./doc/common/tables/cinder-keymgr.xml27(td)
+msgid "(StrOpt) Fixed key returned by key manager, specified in hex"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml7(literal)
+#: ./doc/common/tables/swift-object-expirer-filter-cache.xml7(literal)
+msgid "[filter:cache]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-cache.xml18(td)
+#: ./doc/common/tables/swift-object-expirer-filter-cache.xml18(td)
+msgid "use = egg:swift#memcache"
 msgstr ""
 
 #: ./doc/common/tables/swift-proxy-server-filter-cache.xml21(td)
 msgid "set log_name = cache"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml21(td)
-#: ./doc/common/tables/swift-account-server-app-account-server.xml21(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml21(td)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml21(td)
-msgid "Label to use when logging"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml24(td)
-#: ./doc/common/tables/swift-account-server-app-account-server.xml24(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml24(td)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml24(td)
-msgid "set log_facility = LOG_LOCAL0"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml24(td)
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml64(td)
-#: ./doc/common/tables/swift-container-server-container-updater.xml21(td)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml24(td)
-#: ./doc/common/tables/swift-container-server-container-sync.xml21(td)
-#: ./doc/common/tables/swift-object-server-object-auditor.xml21(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml27(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml24(td)
-#: ./doc/common/tables/swift-account-server-app-account-server.xml24(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml24(td)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml21(td)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml33(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml67(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml61(td)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml24(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml21(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml21(td)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml73(td)
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml24(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml24(td)
-msgid "Syslog log facility"
-msgstr "Syslog ログファシリティ"
-
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml27(td)
-#: ./doc/common/tables/swift-account-server-app-account-server.xml27(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml27(td)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml27(td)
-msgid "set log_level = INFO"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml27(td)
-#: ./doc/common/tables/swift-account-server-app-account-server.xml27(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml27(td)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml27(td)
-msgid "Log level"
-msgstr "ログレベル"
-
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml30(td)
-msgid "set log_headers = false"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml30(td)
-msgid "If True, log headers in each request"
-msgstr "真ならば、各リクエストにおいてヘッダーを記録します。"
-
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml30(td)
-#: ./doc/common/tables/swift-account-server-app-account-server.xml33(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml33(td)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml33(td)
-msgid "set log_address = /dev/log"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml33(td)
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml70(td)
-#: ./doc/common/tables/swift-container-server-container-updater.xml27(td)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml33(td)
-#: ./doc/common/tables/swift-container-server-container-sync.xml27(td)
-#: ./doc/common/tables/swift-object-server-object-auditor.xml27(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml33(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml30(td)
-#: ./doc/common/tables/swift-account-server-app-account-server.xml33(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml33(td)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml27(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml73(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml67(td)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml33(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml27(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml27(td)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml82(td)
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml33(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml33(td)
-msgid "Location where syslog sends the logs to"
-msgstr ""
-
 #: ./doc/common/tables/swift-proxy-server-filter-cache.xml36(td)
 #: ./doc/common/tables/swift-memcache-memcache.xml18(td)
 msgid "memcache_servers = 127.0.0.1:11211"
@@ -26422,135 +32647,6 @@ msgstr ""
 msgid "memcache_serialization_support = 2"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-cache.xml39(td)
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml58(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml57(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml60(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml63(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml66(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml69(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml72(td)
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml75(td)
-#: ./doc/common/tables/swift-object-server-object-auditor.xml45(td)
-#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml57(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml81(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml87(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml90(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml93(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml96(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml102(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml105(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml108(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml111(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml114(td)
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml27(td)
-#: ./doc/common/tables/swift-container-server-pipeline-main.xml18(td)
-#: ./doc/common/tables/swift-rsyncd-object.xml18(td)
-#: ./doc/common/tables/swift-rsyncd-object.xml21(td)
-#: ./doc/common/tables/swift-rsyncd-object.xml24(td)
-#: ./doc/common/tables/swift-rsyncd-object.xml27(td)
-#: ./doc/common/tables/swift-object-server-pipeline-main.xml18(td)
-#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml36(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml45(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml48(td)
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml36(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml36(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml39(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml42(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml45(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml48(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml51(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml54(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml57(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml60(td)
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml72(td)
-#: ./doc/common/tables/swift-rsyncd-account.xml18(td)
-#: ./doc/common/tables/swift-rsyncd-account.xml21(td)
-#: ./doc/common/tables/swift-rsyncd-account.xml24(td)
-#: ./doc/common/tables/swift-rsyncd-account.xml27(td)
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml18(td)
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml21(td)
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml24(td)
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml27(td)
-#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml21(td)
-#: ./doc/common/tables/swift-object-server-filter-recon.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml21(td)
-#: ./doc/common/tables/swift-memcache-memcache.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml45(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml51(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml54(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml57(td)
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml60(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml45(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml51(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml75(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml24(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml33(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml42(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml48(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml51(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml57(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml60(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml63(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml66(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml69(td)
-#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml36(td)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml39(td)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml42(td)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml45(td)
-#: ./doc/common/tables/neutron-rootwrap.xml50(td)
-#: ./doc/common/tables/neutron-rootwrap.xml54(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml42(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml64(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml67(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml79(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml85(td)
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml39(td)
-#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml18(td)
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml18(td)
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml21(td)
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml24(td)
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml27(td)
-#: ./doc/common/tables/swift-rsyncd-container.xml18(td)
-#: ./doc/common/tables/swift-rsyncd-container.xml21(td)
-#: ./doc/common/tables/swift-rsyncd-container.xml24(td)
-#: ./doc/common/tables/swift-rsyncd-container.xml27(td)
-#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml21(td)
-#: ./doc/common/tables/swift-account-server-pipeline-main.xml18(td)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml24(td)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml27(td)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml33(td)
-#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml18(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml45(td)
-msgid "No help text available for this option."
-msgstr ""
-
 #: ./doc/common/tables/swift-proxy-server-filter-cache.xml42(td)
 #: ./doc/common/tables/swift-memcache-memcache.xml24(td)
 msgid "memcache_max_connections = 2"
@@ -26561,1903 +32657,2745 @@ msgstr ""
 msgid "Max number of connections to each memcached server per worker services"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml8(caption)
-msgid "Description of configuration options for rpc_all"
+#: ./doc/common/tables/nova-ldap.xml8(caption)
+#: ./doc/common/tables/keystone-ldap.xml8(caption)
+msgid "Description of configuration options for ldap"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml22(td)
-#: ./doc/common/tables/cinder-rpc.xml26(td)
-#: ./doc/common/tables/keystone-amqp.xml22(td)
-#: ./doc/common/tables/neutron-rpc.xml22(td)
-#: ./doc/common/tables/glance-amqp.xml22(td)
-#: ./doc/common/tables/heat-amqp.xml22(td)
-#: ./doc/common/tables/ceilometer-amqp.xml22(td)
-#: ./doc/common/tables/nova-rpc.xml22(td)
-#: ./doc/common/tables/trove-amqp.xml22(td)
-msgid "amqp_auto_delete = False"
+#: ./doc/common/tables/nova-ldap.xml22(td)
+msgid "ldap_dns_base_dn = ou=hosts,dc=example,dc=org"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml23(td)
-#: ./doc/common/tables/cinder-rpc.xml27(td)
-#: ./doc/common/tables/keystone-amqp.xml23(td)
-#: ./doc/common/tables/neutron-rpc.xml23(td)
-#: ./doc/common/tables/glance-amqp.xml23(td)
-#: ./doc/common/tables/heat-amqp.xml23(td)
-#: ./doc/common/tables/ceilometer-amqp.xml23(td)
-#: ./doc/common/tables/nova-rpc.xml23(td)
-#: ./doc/common/tables/trove-amqp.xml23(td)
-msgid "(BoolOpt) Auto-delete queues in amqp."
+#: ./doc/common/tables/nova-ldap.xml23(td)
+msgid "(StrOpt) Base DN for DNS entries in LDAP"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml26(td)
-#: ./doc/common/tables/cinder-rpc.xml30(td)
-#: ./doc/common/tables/keystone-amqp.xml26(td)
-#: ./doc/common/tables/neutron-rpc.xml26(td)
-#: ./doc/common/tables/glance-amqp.xml26(td)
-#: ./doc/common/tables/heat-amqp.xml26(td)
-#: ./doc/common/tables/ceilometer-amqp.xml26(td)
-#: ./doc/common/tables/nova-rpc.xml26(td)
-#: ./doc/common/tables/trove-amqp.xml26(td)
-msgid "amqp_durable_queues = False"
+#: ./doc/common/tables/nova-ldap.xml26(td)
+msgid "ldap_dns_password = password"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml27(td)
-#: ./doc/common/tables/cinder-rpc.xml31(td)
-#: ./doc/common/tables/keystone-amqp.xml27(td)
-#: ./doc/common/tables/neutron-rpc.xml27(td)
-#: ./doc/common/tables/glance-amqp.xml27(td)
-#: ./doc/common/tables/heat-amqp.xml27(td)
-#: ./doc/common/tables/ceilometer-amqp.xml27(td)
-#: ./doc/common/tables/nova-rpc.xml27(td)
-#: ./doc/common/tables/trove-amqp.xml27(td)
-msgid "(BoolOpt) Use durable queues in amqp."
+#: ./doc/common/tables/nova-ldap.xml27(td)
+msgid "(StrOpt) Password for LDAP DNS"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml30(td)
-#: ./doc/common/tables/cinder-rpc.xml34(td)
-#: ./doc/common/tables/keystone-amqp.xml30(td)
-#: ./doc/common/tables/glance-rabbitmq.xml22(td)
-#: ./doc/common/tables/ceilometer-exchange.xml26(td)
-#: ./doc/common/tables/nova-rpc.xml30(td)
-#: ./doc/common/tables/trove-amqp.xml34(td)
-msgid "control_exchange = openstack"
+#: ./doc/common/tables/nova-ldap.xml30(td)
+msgid "ldap_dns_servers = ['dns.example.org']"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml31(td)
-#: ./doc/common/tables/cinder-rpc.xml35(td)
-#: ./doc/common/tables/keystone-amqp.xml31(td)
-#: ./doc/common/tables/glance-rabbitmq.xml23(td)
-#: ./doc/common/tables/nova-rpc.xml31(td)
+#: ./doc/common/tables/nova-ldap.xml31(td)
+msgid "(MultiStrOpt) DNS Servers for LDAP DNS driver"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml34(td)
+msgid "ldap_dns_soa_expiry = 86400"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml35(td)
 msgid ""
-"(StrOpt) The default exchange under which topics are scoped. May be "
-"overridden by an exchange name specified in the transport_url option."
+"(StrOpt) Expiry interval (in seconds) for LDAP DNS driver Statement of "
+"Authority"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml34(td)
-#: ./doc/common/tables/cinder-rpc.xml46(td)
+#: ./doc/common/tables/nova-ldap.xml38(td)
+msgid "ldap_dns_soa_hostmaster = hostmaster@example.org"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml39(td)
+msgid "(StrOpt) Hostmaster for LDAP DNS driver Statement of Authority"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml42(td)
+msgid "ldap_dns_soa_minimum = 7200"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml43(td)
+msgid ""
+"(StrOpt) Minimum interval (in seconds) for LDAP DNS driver Statement of "
+"Authority"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml46(td)
+msgid "ldap_dns_soa_refresh = 1800"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml47(td)
+msgid ""
+"(StrOpt) Refresh interval (in seconds) for LDAP DNS driver Statement of "
+"Authority"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml50(td)
+msgid "ldap_dns_soa_retry = 3600"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml51(td)
+msgid ""
+"(StrOpt) Retry interval (in seconds) for LDAP DNS driver Statement of "
+"Authority"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml54(td)
+msgid "ldap_dns_url = ldap://ldap.example.com:389"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml55(td)
+msgid "(StrOpt) URL for LDAP server which will store DNS entries"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml58(td)
+msgid "ldap_dns_user = uid=admin,ou=people,dc=example,dc=org"
+msgstr ""
+
+#: ./doc/common/tables/nova-ldap.xml59(td)
+msgid "(StrOpt) User for LDAP DNS"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-filter-recon.xml7(literal)
+#: ./doc/common/tables/swift-account-server-filter-recon.xml7(literal)
+#: ./doc/common/tables/swift-object-server-filter-recon.xml7(literal)
+msgid "[filter:recon]"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-filter-recon.xml18(td)
+#: ./doc/common/tables/swift-account-server-filter-recon.xml18(td)
+#: ./doc/common/tables/swift-object-server-filter-recon.xml18(td)
+msgid "use = egg:swift#recon"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml18(td)
+msgid ""
+"pipeline = catch_errors gatekeeper healthcheck proxy-logging cache "
+"container_sync bulk tempurl slo dlo ratelimit tempauth container-quotas "
+"account-quotas proxy-logging proxy-server"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml22(td)
+#: ./doc/common/tables/neutron-common.xml58(td)
+#: ./doc/common/tables/neutron-common.xml208(td)
+msgid "auth_strategy = keystone"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml23(td)
+#: ./doc/common/tables/nova-authentication.xml23(td)
+msgid "(StrOpt) The strategy to use for auth: noauth or keystone."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml133(th)
+msgid "[service_credentials]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml137(td)
+msgid ""
+"(BoolOpt) Disables X.509 certificate validation when an SSL connection to "
+"Identity Service is established."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml140(td)
+msgid "os_auth_url = http://localhost:5000/v2.0"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml141(td)
+msgid "(StrOpt) Auth URL to use for OpenStack service access."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml144(td)
+msgid "os_cacert = None"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml145(td)
+msgid "(StrOpt) Certificate chain for SSL validation."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml148(td)
+msgid "os_endpoint_type = publicURL"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml149(td)
+msgid ""
+"(StrOpt) Type of endpoint in Identity service catalog to use for "
+"communication with OpenStack services."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml152(td)
+msgid "os_password = admin"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml153(td)
+msgid "(StrOpt) Password to use for OpenStack service access."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml156(td)
+#: ./doc/common/tables/nova-volumes.xml46(td)
+#: ./doc/common/tables/cinder-compute.xml46(td)
+#: ./doc/common/tables/glance-common.xml82(td)
+msgid "os_region_name = None"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml157(td)
+msgid "(StrOpt) Region name to use for OpenStack service endpoints."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml160(td)
+msgid "os_tenant_id ="
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml161(td)
+msgid "(StrOpt) Tenant ID to use for OpenStack service access."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml164(td)
+msgid "os_tenant_name = admin"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml165(td)
+msgid "(StrOpt) Tenant name to use for OpenStack service access."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml168(td)
+msgid "os_username = ceilometer"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-auth.xml169(td)
+msgid "(StrOpt) User name to use for OpenStack service access."
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml8(caption)
+#: ./doc/common/tables/heat-quota.xml8(caption)
+#: ./doc/common/tables/trove-quota.xml8(caption)
+#: ./doc/common/tables/nova-quota.xml8(caption)
+msgid "Description of configuration options for quota"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml23(td)
+msgid "(IntOpt) number of seconds between subsequent usage refreshes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml26(td)
+msgid "quota_driver = cinder.quota.DbQuotaDriver"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml27(td)
+msgid "(StrOpt) default driver to use for quota checks"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml30(td)
+msgid "quota_gigabytes = 1000"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml31(td)
+msgid ""
+"(IntOpt) number of volume gigabytes (snapshots are also included) allowed "
+"per project"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml34(td)
+msgid "quota_snapshots = 10"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml35(td)
+msgid "(IntOpt) number of volume snapshots allowed per project"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml38(td)
+msgid "quota_volumes = 10"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml39(td)
+msgid "(IntOpt) number of volumes allowed per project"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml43(td)
+msgid "(IntOpt) number of seconds until a reservation expires"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml46(td)
+msgid "use_default_quota_class = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-quota.xml47(td)
+msgid "(BoolOpt) whether to use default quota class for default quota"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml7(literal)
+msgid "[filter:account-quotas]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml18(td)
+msgid "use = egg:swift#account_quotas"
+msgstr ""
+
+#: ./doc/common/tables/keystone-os_inherit.xml8(caption)
+msgid "Description of configuration options for os_inherit"
+msgstr ""
+
+#: ./doc/common/tables/keystone-os_inherit.xml19(th)
+msgid "[os_inherit]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-os_inherit.xml23(td)
+msgid ""
+"(BoolOpt) role-assignment inheritance to projects from owning domain can be "
+"optionally enabled."
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml8(caption)
+msgid "Description of configuration options for sdnve"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml19(th)
+msgid "[SDNVE]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml22(td)
+msgid "base_url = /one/nb/v2/"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml23(td)
+msgid "(StrOpt) Base URL for SDN-VE controller REST API"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml26(td)
+msgid "controller_ips = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml27(td)
+msgid "(ListOpt) List of IP addresses of SDN-VE controller(s)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml30(td)
+msgid "default_tenant_type = OF"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml31(td)
+msgid "(StrOpt) Tenant type: OF (default) and OVERLAY"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml34(td)
+msgid "format = json"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml35(td)
+msgid "(StrOpt) SDN-VE request/response format"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml38(td)
+msgid "info = sdnve_info_string"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml39(td)
+msgid "(StrOpt) SDN-VE RPC subject"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml42(td)
+msgid "integration_bridge = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml46(td)
+msgid "interface_mappings ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml47(td)
+msgid "(ListOpt) List of &lt;physical_network_name&gt;:&lt;interface_name&gt;"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml50(td)
+msgid "of_signature = SDNVE-OF"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml51(td)
+msgid ""
+"(StrOpt) The string in tenant description that indicates the tenant is a OF "
+"tenant"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml54(td)
+msgid "out_of_band = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml55(td)
+msgid "(BoolOpt) Indicating if controller is out of band or not"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml58(td)
+msgid "overlay_signature = SDNVE-OVERLAY"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml59(td)
+msgid ""
+"(StrOpt) The string in tenant description that indicates the tenant is a "
+"OVERLAY tenant"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml62(td)
+msgid "password = admin"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml63(td)
+msgid "(StrOpt) SDN-VE administrator password"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml66(td)
+msgid "port = 8443"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml67(td)
+msgid "(StrOpt) SDN-VE controller port number"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml70(td)
+msgid "reset_bridge = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml71(td)
+msgid "(BoolOpt) Reset the integration bridge before use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml74(td)
+msgid "use_fake_controller = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml75(td)
+msgid "(BoolOpt) If set to True uses a fake controller."
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml78(td)
+msgid "userid = admin"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml79(td)
+msgid "(StrOpt) SDN-VE administrator user id"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml82(th)
+msgid "[SDNVE_AGENT]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml85(td)
+#: ./doc/common/tables/neutron-hyperv_agent.xml38(td)
+msgid "polling_interval = 2"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml86(td)
+msgid "(IntOpt) Agent polling interval if necessary"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml89(td)
+#: ./doc/common/tables/neutron-common.xml174(td)
+#: ./doc/common/tables/neutron-common.xml185(td)
+msgid "root_helper = sudo"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml90(td)
+msgid "(StrOpt) Using root helper"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml93(td)
+msgid "rpc = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-sdnve.xml94(td)
+msgid "(BoolOpt) Whether using rpc"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml8(caption)
+#: ./doc/common/tables/trove-compute.xml8(caption)
+#: ./doc/common/tables/neutron-compute.xml8(caption)
+#: ./doc/common/tables/cinder-compute.xml8(caption)
+msgid "Description of configuration options for compute"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml22(td)
+msgid "compute_available_monitors = ['nova.compute.monitors.all_monitors']"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml23(td)
+msgid ""
+"(MultiStrOpt) Monitor classes available to the compute which may be "
+"specified more than once."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml26(td)
+msgid "compute_driver = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml27(td)
+msgid ""
+"(StrOpt) Driver to use for controlling virtualization. Options include: "
+"libvirt.LibvirtDriver, xenapi.XenAPIDriver, fake.FakeDriver, "
+"baremetal.BareMetalDriver, vmwareapi.VMwareESXDriver, "
+"vmwareapi.VMwareVCDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml30(td)
+msgid "compute_manager = nova.compute.manager.ComputeManager"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml31(td)
+msgid "(StrOpt) Full class name for the Manager for compute"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml34(td)
+msgid "compute_monitors ="
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml35(td)
+msgid ""
+"(ListOpt) A list of monitors that can be used for getting compute metrics."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml38(td)
+msgid "compute_stats_class = nova.compute.stats.Stats"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml39(td)
+msgid "(StrOpt) Class that will manage stats for the local compute host"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml42(td)
+msgid "console_host = oslo"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml43(td)
+msgid ""
+"(StrOpt) Console proxy host to use to connect to instances on this host."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml46(td)
+msgid "console_manager = nova.console.manager.ConsoleProxyManager"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml47(td)
+msgid "(StrOpt) Full class name for the Manager for console proxy"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml50(td)
+msgid "default_flavor = m1.small"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml51(td)
+msgid ""
+"(StrOpt) Default flavor to use for the EC2 API only. The Nova API does not "
+"support a default flavor."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml58(td)
+#: ./doc/common/tables/heat-amqp.xml38(td)
+#: ./doc/common/tables/keystone-amqp.xml34(td)
+#: ./doc/common/tables/ceilometer-exchange.xml30(td)
+msgid "default_publisher_id = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml59(td)
+#: ./doc/common/tables/heat-amqp.xml39(td)
+#: ./doc/common/tables/trove-common.xml51(td)
+#: ./doc/common/tables/keystone-amqp.xml35(td)
+#: ./doc/common/tables/ceilometer-exchange.xml31(td)
+#: ./doc/common/tables/neutron-notifier.xml27(td)
+msgid "(StrOpt) Default publisher_id for outgoing notifications"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml62(td)
+msgid "enable_instance_password = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml63(td)
+msgid ""
+"(BoolOpt) Enables returning of the instance password by the relevant server "
+"API calls such as create, rebuild or rescue, If the hypervisor does not "
+"support password injection then the password returned will not be correct"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml66(td)
+msgid "heal_instance_info_cache_interval = 60"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml67(td)
+msgid ""
+"(IntOpt) Number of seconds between instance info_cache self healing updates"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml70(td)
+msgid "image_cache_manager_interval = 2400"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml71(td)
+msgid ""
+"(IntOpt) Number of seconds to wait between runs of the image cache manager"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml74(td)
+msgid "image_cache_subdirectory_name = _base"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml75(td)
+msgid ""
+"(StrOpt) Where cached images are stored under $instances_path. This is NOT "
+"the full path - just a folder name. For per-compute-host cached images, set "
+"to _base_$my_ip"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml78(td)
+msgid "image_handlers = download"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml79(td)
+msgid ""
+"(ListOpt) Specifies which image handler extension names to use for handling "
+"images. The first extension in the list which can handle the image with a "
+"suitable location will be used."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml82(td)
+msgid "instance_build_timeout = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml83(td)
+msgid ""
+"(IntOpt) Amount of time in seconds an instance can be in BUILD before going "
+"into ERROR status.Set to 0 to disable."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml86(td)
+msgid "instance_delete_interval = 300"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml87(td)
+msgid "(IntOpt) Interval in seconds for retrying failed instance file deletes"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml90(td)
+msgid "instance_usage_audit = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml91(td)
+msgid "(BoolOpt) Generate periodic compute.instance.exists notifications"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml94(td)
+msgid "instance_usage_audit_period = month"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml95(td)
+msgid ""
+"(StrOpt) Time period to generate instance usages for. Time period must be "
+"hour, day, month or year"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml98(td)
+msgid "instances_path = $state_path/instances"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml99(td)
+msgid "(StrOpt) Where instances are stored on disk"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml102(td)
+msgid "maximum_instance_delete_attempts = 5"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml103(td)
+msgid "(IntOpt) The number of times to attempt to reap an instance's files."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml106(td)
+msgid "reboot_timeout = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml107(td)
+msgid ""
+"(IntOpt) Automatically hard reboot an instance if it has been stuck in a "
+"rebooting state longer than N seconds. Set to 0 to disable."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml110(td)
+msgid "reclaim_instance_interval = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml111(td)
+msgid "(IntOpt) Interval in seconds for reclaiming deleted instances"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml114(td)
+msgid "resize_confirm_window = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml115(td)
+msgid ""
+"(IntOpt) Automatically confirm resizes after N seconds. Set to 0 to disable."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml118(td)
+msgid "resume_guests_state_on_host_boot = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml119(td)
+msgid ""
+"(BoolOpt) Whether to start guests that were running before the host rebooted"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml122(td)
+msgid "running_deleted_instance_action = reap"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml123(td)
+msgid ""
+"(StrOpt) Action to take if a running deleted instance is detected.Valid "
+"options are 'noop', 'log', 'shutdown', or 'reap'. Set to 'noop' to take no "
+"action."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml126(td)
+msgid "running_deleted_instance_poll_interval = 1800"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml127(td)
+msgid "(IntOpt) Number of seconds to wait between runs of the cleanup task."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml130(td)
+msgid "running_deleted_instance_timeout = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml131(td)
+msgid ""
+"(IntOpt) Number of seconds after being deleted when a running instance "
+"should be considered eligible for cleanup."
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml134(td)
+msgid "shelved_offload_time = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml135(td)
+msgid ""
+"(IntOpt) Time in seconds before a shelved instance is eligible for removing "
+"from a host. -1 never offload, 0 offload when shelved"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml138(td)
+msgid "shelved_poll_interval = 3600"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml139(td)
+msgid "(IntOpt) Interval in seconds for polling shelved instances to offload"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml142(td)
+msgid "sync_power_state_interval = 600"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml143(td)
+msgid ""
+"(IntOpt) Interval to sync power states between the database and the "
+"hypervisor"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml146(td)
+msgid "vif_plugging_is_fatal = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml147(td)
+msgid "(BoolOpt) Fail instance boot if vif plugging fails"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml150(td)
+msgid "vif_plugging_timeout = 300"
+msgstr ""
+
+#: ./doc/common/tables/nova-compute.xml151(td)
+msgid ""
+"(IntOpt) Number of seconds to wait for neutron vif plugging events to arrive"
+" before continuing or failing (see vif_plugging_is_fatal). If this is set to"
+" zero and vif_plugging_is_fatal is False, events should not be expected to "
+"arrive at all."
+msgstr ""
+
+#: ./doc/common/tables/keystone-rabbit.xml8(caption)
+msgid "Description of configuration options for rabbit"
+msgstr ""
+
+#: ./doc/common/tables/keystone-rabbit.xml26(td)
 #: ./doc/common/tables/glance-rabbitmq.xml30(td)
 #: ./doc/common/tables/nova-kombu.xml22(td)
-#: ./doc/common/tables/keystone-rabbit.xml26(td)
+#: ./doc/common/tables/cinder-rpc.xml46(td)
+#: ./doc/common/tables/nova-rpc_all.xml34(td)
 msgid "kombu_reconnect_delay = 1.0"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml35(td)
-#: ./doc/common/tables/cinder-rpc.xml47(td)
+#: ./doc/common/tables/keystone-rabbit.xml27(td)
 #: ./doc/common/tables/glance-rabbitmq.xml31(td)
 #: ./doc/common/tables/nova-kombu.xml23(td)
-#: ./doc/common/tables/keystone-rabbit.xml27(td)
+#: ./doc/common/tables/cinder-rpc.xml47(td)
+#: ./doc/common/tables/nova-rpc_all.xml35(td)
 msgid ""
 "(FloatOpt) How long to wait before reconnecting in response to an AMQP "
 "consumer cancel notification."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml38(td)
-#: ./doc/common/tables/neutron-kombu.xml22(td)
-#: ./doc/common/tables/cinder-rpc.xml50(td)
-#: ./doc/common/tables/heat-rabbitmq.xml22(td)
-#: ./doc/common/tables/glance-rabbitmq.xml34(td)
-#: ./doc/common/tables/nova-kombu.xml26(td)
-#: ./doc/common/tables/keystone-rabbit.xml30(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml26(td)
-#: ./doc/common/tables/trove-amqp.xml42(td)
-msgid "kombu_ssl_ca_certs ="
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml39(td)
-#: ./doc/common/tables/cinder-rpc.xml51(td)
+#: ./doc/common/tables/keystone-rabbit.xml31(td)
 #: ./doc/common/tables/glance-rabbitmq.xml35(td)
 #: ./doc/common/tables/nova-kombu.xml27(td)
-#: ./doc/common/tables/keystone-rabbit.xml31(td)
+#: ./doc/common/tables/cinder-rpc.xml51(td)
+#: ./doc/common/tables/nova-rpc_all.xml39(td)
 msgid "(StrOpt) SSL certification authority file (valid only if SSL enabled)."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml42(td)
-#: ./doc/common/tables/neutron-kombu.xml26(td)
-#: ./doc/common/tables/cinder-rpc.xml54(td)
-#: ./doc/common/tables/heat-rabbitmq.xml26(td)
-#: ./doc/common/tables/glance-rabbitmq.xml38(td)
-#: ./doc/common/tables/nova-kombu.xml30(td)
-#: ./doc/common/tables/keystone-rabbit.xml34(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml30(td)
-#: ./doc/common/tables/trove-amqp.xml46(td)
-msgid "kombu_ssl_certfile ="
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml43(td)
-#: ./doc/common/tables/cinder-rpc.xml55(td)
+#: ./doc/common/tables/keystone-rabbit.xml35(td)
 #: ./doc/common/tables/glance-rabbitmq.xml39(td)
 #: ./doc/common/tables/nova-kombu.xml31(td)
-#: ./doc/common/tables/keystone-rabbit.xml35(td)
+#: ./doc/common/tables/cinder-rpc.xml55(td)
+#: ./doc/common/tables/nova-rpc_all.xml43(td)
 msgid "(StrOpt) SSL cert file (valid only if SSL enabled)."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml46(td)
-#: ./doc/common/tables/neutron-kombu.xml30(td)
-#: ./doc/common/tables/cinder-rpc.xml58(td)
-#: ./doc/common/tables/heat-rabbitmq.xml30(td)
-#: ./doc/common/tables/glance-rabbitmq.xml42(td)
-#: ./doc/common/tables/nova-kombu.xml34(td)
-#: ./doc/common/tables/keystone-rabbit.xml38(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml34(td)
-#: ./doc/common/tables/trove-amqp.xml50(td)
-msgid "kombu_ssl_keyfile ="
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml47(td)
-#: ./doc/common/tables/cinder-rpc.xml59(td)
+#: ./doc/common/tables/keystone-rabbit.xml39(td)
 #: ./doc/common/tables/glance-rabbitmq.xml43(td)
 #: ./doc/common/tables/nova-kombu.xml35(td)
-#: ./doc/common/tables/keystone-rabbit.xml39(td)
+#: ./doc/common/tables/cinder-rpc.xml59(td)
+#: ./doc/common/tables/nova-rpc_all.xml47(td)
 msgid "(StrOpt) SSL key file (valid only if SSL enabled)."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml50(td)
-#: ./doc/common/tables/neutron-kombu.xml34(td)
-#: ./doc/common/tables/cinder-rpc.xml62(td)
-#: ./doc/common/tables/heat-rabbitmq.xml34(td)
-#: ./doc/common/tables/glance-rabbitmq.xml46(td)
-#: ./doc/common/tables/nova-kombu.xml38(td)
-#: ./doc/common/tables/keystone-rabbit.xml42(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml38(td)
-#: ./doc/common/tables/trove-amqp.xml54(td)
-msgid "kombu_ssl_version ="
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml51(td)
-#: ./doc/common/tables/cinder-rpc.xml63(td)
+#: ./doc/common/tables/keystone-rabbit.xml43(td)
 #: ./doc/common/tables/glance-rabbitmq.xml47(td)
 #: ./doc/common/tables/nova-kombu.xml39(td)
-#: ./doc/common/tables/keystone-rabbit.xml43(td)
+#: ./doc/common/tables/cinder-rpc.xml63(td)
+#: ./doc/common/tables/nova-rpc_all.xml51(td)
 msgid ""
 "(StrOpt) SSL version to use (valid only if SSL enabled). valid values are "
 "TLSv1, SSLv23 and SSLv3. SSLv2 may be available on some distributions."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml54(td)
-#: ./doc/common/tables/heat-rpc.xml30(td)
-#: ./doc/common/tables/ceilometer-redis.xml26(td)
-#: ./doc/common/tables/cinder-rpc.xml66(td)
-#: ./doc/common/tables/neutron-rpc.xml34(td)
-#: ./doc/common/tables/trove-rpc.xml30(td)
-#: ./doc/common/tables/keystone-redis.xml26(td)
-#: ./doc/common/tables/glance-matchmaker.xml22(td)
-#: ./doc/common/tables/nova-rpc.xml34(td)
-msgid "matchmaker_heartbeat_freq = 300"
+#: ./doc/common/tables/cinder-backups_ceph.xml8(caption)
+msgid "Description of configuration options for backups_ceph"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml55(td)
-#: ./doc/common/tables/cinder-rpc.xml67(td)
-#: ./doc/common/tables/keystone-redis.xml27(td)
-#: ./doc/common/tables/glance-matchmaker.xml23(td)
-#: ./doc/common/tables/nova-rpc.xml35(td)
-msgid "(IntOpt) Heartbeat frequency."
+#: ./doc/common/tables/cinder-backups_ceph.xml22(td)
+msgid "backup_ceph_chunk_size = 134217728"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml58(td)
-#: ./doc/common/tables/heat-rpc.xml34(td)
-#: ./doc/common/tables/ceilometer-redis.xml30(td)
-#: ./doc/common/tables/cinder-rpc.xml70(td)
-#: ./doc/common/tables/neutron-rpc.xml38(td)
-#: ./doc/common/tables/trove-rpc.xml34(td)
-#: ./doc/common/tables/keystone-redis.xml30(td)
-#: ./doc/common/tables/glance-matchmaker.xml26(td)
-#: ./doc/common/tables/nova-rpc.xml38(td)
-msgid "matchmaker_heartbeat_ttl = 600"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml59(td)
-#: ./doc/common/tables/heat-rpc.xml35(td)
-#: ./doc/common/tables/ceilometer-redis.xml31(td)
-#: ./doc/common/tables/cinder-rpc.xml71(td)
-#: ./doc/common/tables/neutron-rpc.xml39(td)
-#: ./doc/common/tables/trove-rpc.xml35(td)
-#: ./doc/common/tables/keystone-redis.xml31(td)
-#: ./doc/common/tables/glance-matchmaker.xml27(td)
-#: ./doc/common/tables/nova-rpc.xml39(td)
-msgid "(IntOpt) Heartbeat time-to-live."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml62(td)
-#: ./doc/common/tables/glance-qpid.xml22(td)
-#: ./doc/common/tables/keystone-qpid.xml22(td)
-#: ./doc/common/tables/trove-qpid.xml22(td)
-#: ./doc/common/tables/heat-qpid.xml22(td)
-#: ./doc/common/tables/cinder-rpc.xml94(td)
-#: ./doc/common/tables/neutron-qpid.xml22(td)
-#: ./doc/common/tables/nova-qpid.xml22(td)
-#: ./doc/common/tables/ceilometer-qpid.xml22(td)
-msgid "qpid_heartbeat = 60"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml63(td)
-#: ./doc/common/tables/glance-qpid.xml23(td)
-#: ./doc/common/tables/keystone-qpid.xml23(td)
-#: ./doc/common/tables/cinder-rpc.xml95(td)
-#: ./doc/common/tables/nova-qpid.xml23(td)
-msgid "(IntOpt) Seconds between connection keepalive heartbeats."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml66(td)
-#: ./doc/common/tables/glance-qpid.xml26(td)
-#: ./doc/common/tables/keystone-qpid.xml26(td)
-#: ./doc/common/tables/trove-qpid.xml26(td)
-#: ./doc/common/tables/heat-qpid.xml26(td)
-#: ./doc/common/tables/cinder-rpc.xml98(td)
-#: ./doc/common/tables/neutron-qpid.xml26(td)
-#: ./doc/common/tables/nova-qpid.xml26(td)
-#: ./doc/common/tables/ceilometer-qpid.xml26(td)
-msgid "qpid_hostname = localhost"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml67(td)
-#: ./doc/common/tables/glance-qpid.xml27(td)
-#: ./doc/common/tables/keystone-qpid.xml27(td)
-#: ./doc/common/tables/cinder-rpc.xml99(td)
-#: ./doc/common/tables/nova-qpid.xml27(td)
-msgid "(StrOpt) Qpid broker hostname."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml70(td)
-#: ./doc/common/tables/glance-qpid.xml30(td)
-#: ./doc/common/tables/keystone-qpid.xml30(td)
-#: ./doc/common/tables/trove-qpid.xml30(td)
-#: ./doc/common/tables/heat-qpid.xml30(td)
-#: ./doc/common/tables/cinder-rpc.xml102(td)
-#: ./doc/common/tables/neutron-qpid.xml30(td)
-#: ./doc/common/tables/nova-qpid.xml30(td)
-#: ./doc/common/tables/ceilometer-qpid.xml30(td)
-msgid "qpid_hosts = $qpid_hostname:$qpid_port"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml71(td)
-#: ./doc/common/tables/glance-qpid.xml31(td)
-#: ./doc/common/tables/keystone-qpid.xml31(td)
-#: ./doc/common/tables/cinder-rpc.xml103(td)
-#: ./doc/common/tables/nova-qpid.xml31(td)
-msgid "(ListOpt) Qpid HA cluster host:port pairs."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml74(td)
-#: ./doc/common/tables/glance-qpid.xml34(td)
-#: ./doc/common/tables/keystone-qpid.xml34(td)
-#: ./doc/common/tables/trove-qpid.xml34(td)
-#: ./doc/common/tables/heat-qpid.xml34(td)
-#: ./doc/common/tables/cinder-rpc.xml106(td)
-#: ./doc/common/tables/neutron-qpid.xml34(td)
-#: ./doc/common/tables/nova-qpid.xml34(td)
-#: ./doc/common/tables/ceilometer-qpid.xml34(td)
-msgid "qpid_password ="
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml75(td)
-#: ./doc/common/tables/glance-qpid.xml35(td)
-#: ./doc/common/tables/keystone-qpid.xml35(td)
-#: ./doc/common/tables/cinder-rpc.xml107(td)
-#: ./doc/common/tables/nova-qpid.xml35(td)
-msgid "(StrOpt) Password for Qpid connection."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml78(td)
-#: ./doc/common/tables/glance-qpid.xml38(td)
-#: ./doc/common/tables/keystone-qpid.xml38(td)
-#: ./doc/common/tables/trove-qpid.xml38(td)
-#: ./doc/common/tables/heat-qpid.xml38(td)
-#: ./doc/common/tables/cinder-rpc.xml110(td)
-#: ./doc/common/tables/neutron-qpid.xml38(td)
-#: ./doc/common/tables/nova-qpid.xml38(td)
-#: ./doc/common/tables/ceilometer-qpid.xml38(td)
-msgid "qpid_port = 5672"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml79(td)
-#: ./doc/common/tables/glance-qpid.xml39(td)
-#: ./doc/common/tables/keystone-qpid.xml39(td)
-#: ./doc/common/tables/cinder-rpc.xml111(td)
-#: ./doc/common/tables/nova-qpid.xml39(td)
-msgid "(IntOpt) Qpid broker port."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml82(td)
-#: ./doc/common/tables/glance-qpid.xml42(td)
-#: ./doc/common/tables/keystone-qpid.xml42(td)
-#: ./doc/common/tables/trove-qpid.xml42(td)
-#: ./doc/common/tables/heat-qpid.xml42(td)
-#: ./doc/common/tables/cinder-rpc.xml114(td)
-#: ./doc/common/tables/neutron-qpid.xml42(td)
-#: ./doc/common/tables/nova-qpid.xml42(td)
-#: ./doc/common/tables/ceilometer-qpid.xml42(td)
-msgid "qpid_protocol = tcp"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml83(td)
-#: ./doc/common/tables/glance-qpid.xml43(td)
-#: ./doc/common/tables/keystone-qpid.xml43(td)
-#: ./doc/common/tables/cinder-rpc.xml115(td)
-#: ./doc/common/tables/nova-qpid.xml43(td)
-msgid "(StrOpt) Transport to use, either 'tcp' or 'ssl'."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml86(td)
-#: ./doc/common/tables/glance-qpid.xml46(td)
-#: ./doc/common/tables/keystone-qpid.xml46(td)
-#: ./doc/common/tables/trove-qpid.xml46(td)
-#: ./doc/common/tables/heat-qpid.xml46(td)
-#: ./doc/common/tables/cinder-rpc.xml118(td)
-#: ./doc/common/tables/neutron-qpid.xml46(td)
-#: ./doc/common/tables/nova-qpid.xml46(td)
-#: ./doc/common/tables/ceilometer-qpid.xml46(td)
-msgid "qpid_sasl_mechanisms ="
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml87(td)
-#: ./doc/common/tables/glance-qpid.xml47(td)
-#: ./doc/common/tables/keystone-qpid.xml47(td)
-#: ./doc/common/tables/cinder-rpc.xml119(td)
-#: ./doc/common/tables/nova-qpid.xml47(td)
-msgid "(StrOpt) Space separated list of SASL mechanisms to use for auth."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml90(td)
-#: ./doc/common/tables/glance-qpid.xml50(td)
-#: ./doc/common/tables/keystone-qpid.xml50(td)
-#: ./doc/common/tables/trove-qpid.xml50(td)
-#: ./doc/common/tables/heat-qpid.xml50(td)
-#: ./doc/common/tables/cinder-rpc.xml122(td)
-#: ./doc/common/tables/neutron-qpid.xml50(td)
-#: ./doc/common/tables/nova-qpid.xml50(td)
-#: ./doc/common/tables/ceilometer-qpid.xml50(td)
-msgid "qpid_tcp_nodelay = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml91(td)
-#: ./doc/common/tables/glance-qpid.xml51(td)
-#: ./doc/common/tables/keystone-qpid.xml51(td)
-#: ./doc/common/tables/cinder-rpc.xml123(td)
-#: ./doc/common/tables/nova-qpid.xml51(td)
-msgid "(BoolOpt) Whether to disable the Nagle algorithm."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml94(td)
-#: ./doc/common/tables/glance-qpid.xml54(td)
-#: ./doc/common/tables/keystone-qpid.xml54(td)
-#: ./doc/common/tables/heat-qpid.xml54(td)
-#: ./doc/common/tables/cinder-rpc.xml126(td)
-#: ./doc/common/tables/neutron-qpid.xml54(td)
-#: ./doc/common/tables/nova-qpid.xml54(td)
-#: ./doc/common/tables/ceilometer-qpid.xml54(td)
-msgid "qpid_topology_version = 1"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml95(td)
-#: ./doc/common/tables/glance-qpid.xml55(td)
-#: ./doc/common/tables/keystone-qpid.xml55(td)
-#: ./doc/common/tables/heat-qpid.xml55(td)
-#: ./doc/common/tables/cinder-rpc.xml127(td)
-#: ./doc/common/tables/neutron-qpid.xml55(td)
-#: ./doc/common/tables/nova-qpid.xml55(td)
-#: ./doc/common/tables/ceilometer-qpid.xml55(td)
+#: ./doc/common/tables/cinder-backups_ceph.xml23(td)
 msgid ""
-"(IntOpt) The qpid topology version to use. Version 1 is what was originally "
-"used by impl_qpid. Version 2 includes some backwards-incompatible changes "
-"that allow broker federation to work. Users should update to version 2 when "
-"they are able to take everything down, as it requires a clean break."
+"(IntOpt) The chunk size, in bytes, that a backup is broken into before "
+"transfer to the Ceph object store."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml98(td)
-#: ./doc/common/tables/glance-qpid.xml58(td)
-#: ./doc/common/tables/keystone-qpid.xml58(td)
-#: ./doc/common/tables/trove-qpid.xml54(td)
-#: ./doc/common/tables/heat-qpid.xml58(td)
-#: ./doc/common/tables/cinder-rpc.xml130(td)
-#: ./doc/common/tables/neutron-qpid.xml58(td)
-#: ./doc/common/tables/nova-qpid.xml58(td)
-#: ./doc/common/tables/ceilometer-qpid.xml58(td)
-msgid "qpid_username ="
+#: ./doc/common/tables/cinder-backups_ceph.xml26(td)
+msgid "backup_ceph_conf = /etc/ceph/ceph.conf"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml99(td)
-#: ./doc/common/tables/glance-qpid.xml59(td)
-#: ./doc/common/tables/keystone-qpid.xml59(td)
-#: ./doc/common/tables/cinder-rpc.xml131(td)
-#: ./doc/common/tables/nova-qpid.xml59(td)
-msgid "(StrOpt) Username for Qpid connection."
+#: ./doc/common/tables/cinder-backups_ceph.xml27(td)
+msgid "(StrOpt) Ceph configuration file to use."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml102(td)
-#: ./doc/common/tables/trove-rabbitmq.xml22(td)
-#: ./doc/common/tables/cinder-rpc.xml134(td)
-#: ./doc/common/tables/heat-rabbitmq.xml38(td)
-#: ./doc/common/tables/glance-rabbitmq.xml50(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml22(td)
-#: ./doc/common/tables/keystone-rabbit.xml46(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml42(td)
-#: ./doc/common/tables/nova-rabbitmq.xml22(td)
-msgid "rabbit_ha_queues = False"
+#: ./doc/common/tables/cinder-backups_ceph.xml30(td)
+msgid "backup_ceph_pool = backups"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml103(td)
-#: ./doc/common/tables/cinder-rpc.xml135(td)
-#: ./doc/common/tables/glance-rabbitmq.xml51(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml23(td)
-#: ./doc/common/tables/keystone-rabbit.xml47(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml43(td)
-#: ./doc/common/tables/nova-rabbitmq.xml23(td)
+#: ./doc/common/tables/cinder-backups_ceph.xml31(td)
+msgid "(StrOpt) The Ceph pool where volume backups are stored."
+msgstr ""
+
+#: ./doc/common/tables/cinder-backups_ceph.xml34(td)
+msgid "backup_ceph_stripe_count = 0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-backups_ceph.xml35(td)
+msgid "(IntOpt) RBD stripe count to use when creating a backup image."
+msgstr ""
+
+#: ./doc/common/tables/cinder-backups_ceph.xml38(td)
+msgid "backup_ceph_stripe_unit = 0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-backups_ceph.xml39(td)
+msgid "(IntOpt) RBD stripe unit to use when creating a backup image."
+msgstr ""
+
+#: ./doc/common/tables/cinder-backups_ceph.xml42(td)
+msgid "backup_ceph_user = cinder"
+msgstr ""
+
+#: ./doc/common/tables/cinder-backups_ceph.xml43(td)
 msgid ""
-"(BoolOpt) Use HA queues in RabbitMQ (x-ha-policy: all). If you change this "
-"option, you must wipe the RabbitMQ database."
+"(StrOpt) The Ceph user to connect with. Default here is to use the same user"
+" as for Cinder volumes. If not using cephx this should be set to None."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml106(td)
-#: ./doc/common/tables/trove-rabbitmq.xml26(td)
-#: ./doc/common/tables/cinder-rpc.xml138(td)
-#: ./doc/common/tables/heat-rabbitmq.xml42(td)
-#: ./doc/common/tables/glance-rabbitmq.xml54(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml26(td)
-#: ./doc/common/tables/keystone-rabbit.xml50(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml46(td)
-#: ./doc/common/tables/nova-rabbitmq.xml26(td)
-msgid "rabbit_host = localhost"
+#: ./doc/common/tables/cinder-backups_ceph.xml46(td)
+msgid "restore_discard_excess_bytes = True"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml107(td)
-#: ./doc/common/tables/cinder-rpc.xml139(td)
-#: ./doc/common/tables/glance-rabbitmq.xml55(td)
-#: ./doc/common/tables/keystone-rabbit.xml51(td)
-#: ./doc/common/tables/nova-rabbitmq.xml27(td)
-msgid "(StrOpt) The RabbitMQ broker address where a single node is used."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml110(td)
-#: ./doc/common/tables/trove-rabbitmq.xml30(td)
-#: ./doc/common/tables/cinder-rpc.xml142(td)
-#: ./doc/common/tables/heat-rabbitmq.xml46(td)
-#: ./doc/common/tables/glance-rabbitmq.xml58(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml30(td)
-#: ./doc/common/tables/keystone-rabbit.xml54(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml50(td)
-#: ./doc/common/tables/nova-rabbitmq.xml30(td)
-msgid "rabbit_hosts = $rabbit_host:$rabbit_port"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml111(td)
-#: ./doc/common/tables/cinder-rpc.xml143(td)
-#: ./doc/common/tables/glance-rabbitmq.xml59(td)
-#: ./doc/common/tables/keystone-rabbit.xml55(td)
-#: ./doc/common/tables/nova-rabbitmq.xml31(td)
-msgid "(ListOpt) RabbitMQ HA cluster host:port pairs."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml114(td)
-#: ./doc/common/tables/cinder-rpc.xml146(td)
-#: ./doc/common/tables/glance-rabbitmq.xml62(td)
-#: ./doc/common/tables/keystone-rabbit.xml58(td)
-#: ./doc/common/tables/nova-rabbitmq.xml34(td)
-msgid "rabbit_login_method = AMQPLAIN"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml115(td)
-#: ./doc/common/tables/cinder-rpc.xml147(td)
-#: ./doc/common/tables/glance-rabbitmq.xml63(td)
-#: ./doc/common/tables/keystone-rabbit.xml59(td)
-#: ./doc/common/tables/nova-rabbitmq.xml35(td)
-msgid "(StrOpt) the RabbitMQ login method"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml118(td)
-#: ./doc/common/tables/trove-rabbitmq.xml34(td)
-#: ./doc/common/tables/cinder-rpc.xml150(td)
-#: ./doc/common/tables/heat-rabbitmq.xml50(td)
-#: ./doc/common/tables/glance-rabbitmq.xml66(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml34(td)
-#: ./doc/common/tables/keystone-rabbit.xml62(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml54(td)
-#: ./doc/common/tables/nova-rabbitmq.xml38(td)
-msgid "rabbit_max_retries = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml119(td)
-#: ./doc/common/tables/cinder-rpc.xml151(td)
-#: ./doc/common/tables/glance-rabbitmq.xml67(td)
-#: ./doc/common/tables/keystone-rabbit.xml63(td)
-#: ./doc/common/tables/nova-rabbitmq.xml39(td)
+#: ./doc/common/tables/cinder-backups_ceph.xml47(td)
 msgid ""
-"(IntOpt) Maximum number of RabbitMQ connection retries. Default is 0 "
-"(infinite retry count)."
+"(BoolOpt) If True, always discard excess bytes when restoring volumes i.e. "
+"pad with zeroes."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml122(td)
-#: ./doc/common/tables/trove-rabbitmq.xml38(td)
-#: ./doc/common/tables/cinder-rpc.xml154(td)
-#: ./doc/common/tables/heat-rabbitmq.xml54(td)
-#: ./doc/common/tables/glance-rabbitmq.xml70(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml38(td)
-#: ./doc/common/tables/keystone-rabbit.xml66(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml58(td)
-#: ./doc/common/tables/nova-rabbitmq.xml42(td)
-msgid "rabbit_password = guest"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml123(td)
-#: ./doc/common/tables/cinder-rpc.xml155(td)
-#: ./doc/common/tables/glance-rabbitmq.xml71(td)
-#: ./doc/common/tables/keystone-rabbit.xml67(td)
-#: ./doc/common/tables/nova-rabbitmq.xml43(td)
-msgid "(StrOpt) The RabbitMQ password."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml126(td)
-#: ./doc/common/tables/trove-rabbitmq.xml42(td)
-#: ./doc/common/tables/cinder-rpc.xml158(td)
-#: ./doc/common/tables/heat-rabbitmq.xml58(td)
-#: ./doc/common/tables/glance-rabbitmq.xml74(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml42(td)
-#: ./doc/common/tables/keystone-rabbit.xml70(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml62(td)
-#: ./doc/common/tables/nova-rabbitmq.xml46(td)
-msgid "rabbit_port = 5672"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml127(td)
-#: ./doc/common/tables/cinder-rpc.xml159(td)
-#: ./doc/common/tables/glance-rabbitmq.xml75(td)
-#: ./doc/common/tables/keystone-rabbit.xml71(td)
-#: ./doc/common/tables/nova-rabbitmq.xml47(td)
-msgid "(IntOpt) The RabbitMQ broker port where a single node is used."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml130(td)
-#: ./doc/common/tables/trove-rabbitmq.xml46(td)
-#: ./doc/common/tables/cinder-rpc.xml162(td)
-#: ./doc/common/tables/heat-rabbitmq.xml62(td)
-#: ./doc/common/tables/glance-rabbitmq.xml78(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml46(td)
-#: ./doc/common/tables/keystone-rabbit.xml74(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml66(td)
-#: ./doc/common/tables/nova-rabbitmq.xml50(td)
-msgid "rabbit_retry_backoff = 2"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml131(td)
-#: ./doc/common/tables/cinder-rpc.xml163(td)
-#: ./doc/common/tables/glance-rabbitmq.xml79(td)
-#: ./doc/common/tables/keystone-rabbit.xml75(td)
-#: ./doc/common/tables/nova-rabbitmq.xml51(td)
+#: ./doc/common/tables/nova-vmware.xml23(td)
 msgid ""
-"(IntOpt) How long to backoff for between retries when connecting to "
-"RabbitMQ."
+"(IntOpt) The number of times we retry on failures, e.g., socket error, etc."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml134(td)
-#: ./doc/common/tables/trove-rabbitmq.xml50(td)
-#: ./doc/common/tables/cinder-rpc.xml166(td)
-#: ./doc/common/tables/heat-rabbitmq.xml66(td)
-#: ./doc/common/tables/glance-rabbitmq.xml82(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml50(td)
-#: ./doc/common/tables/keystone-rabbit.xml78(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml70(td)
-#: ./doc/common/tables/nova-rabbitmq.xml54(td)
-msgid "rabbit_retry_interval = 1"
+#: ./doc/common/tables/nova-vmware.xml26(td)
+msgid "cluster_name = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml135(td)
-#: ./doc/common/tables/cinder-rpc.xml167(td)
-#: ./doc/common/tables/glance-rabbitmq.xml83(td)
-#: ./doc/common/tables/keystone-rabbit.xml79(td)
-#: ./doc/common/tables/nova-rabbitmq.xml55(td)
-msgid "(IntOpt) How frequently to retry connecting with RabbitMQ."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml138(td)
-#: ./doc/common/tables/trove-rabbitmq.xml54(td)
-#: ./doc/common/tables/cinder-rpc.xml170(td)
-#: ./doc/common/tables/heat-rabbitmq.xml70(td)
-#: ./doc/common/tables/glance-rabbitmq.xml86(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml54(td)
-#: ./doc/common/tables/keystone-rabbit.xml82(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml74(td)
-#: ./doc/common/tables/nova-rabbitmq.xml58(td)
-msgid "rabbit_use_ssl = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml139(td)
-#: ./doc/common/tables/cinder-rpc.xml171(td)
-#: ./doc/common/tables/glance-rabbitmq.xml87(td)
-#: ./doc/common/tables/keystone-rabbit.xml83(td)
-#: ./doc/common/tables/nova-rabbitmq.xml59(td)
-msgid "(BoolOpt) Connect over SSL for RabbitMQ."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml142(td)
-#: ./doc/common/tables/trove-rabbitmq.xml58(td)
-#: ./doc/common/tables/cinder-rpc.xml174(td)
-#: ./doc/common/tables/heat-rabbitmq.xml74(td)
-#: ./doc/common/tables/glance-rabbitmq.xml90(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml58(td)
-#: ./doc/common/tables/keystone-rabbit.xml86(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml78(td)
-#: ./doc/common/tables/nova-rabbitmq.xml62(td)
-msgid "rabbit_userid = guest"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml143(td)
-#: ./doc/common/tables/cinder-rpc.xml175(td)
-#: ./doc/common/tables/glance-rabbitmq.xml91(td)
-#: ./doc/common/tables/keystone-rabbit.xml87(td)
-#: ./doc/common/tables/nova-rabbitmq.xml63(td)
-msgid "(StrOpt) The RabbitMQ userid."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml146(td)
-#: ./doc/common/tables/trove-rabbitmq.xml62(td)
-#: ./doc/common/tables/cinder-rpc.xml178(td)
-#: ./doc/common/tables/heat-rabbitmq.xml78(td)
-#: ./doc/common/tables/glance-rabbitmq.xml94(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml62(td)
-#: ./doc/common/tables/keystone-rabbit.xml90(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml82(td)
-#: ./doc/common/tables/nova-rabbitmq.xml66(td)
-msgid "rabbit_virtual_host = /"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml147(td)
-#: ./doc/common/tables/cinder-rpc.xml179(td)
-#: ./doc/common/tables/glance-rabbitmq.xml95(td)
-#: ./doc/common/tables/keystone-rabbit.xml91(td)
-#: ./doc/common/tables/nova-rabbitmq.xml67(td)
-msgid "(StrOpt) The RabbitMQ virtual host."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml150(td)
-#: ./doc/common/tables/cinder-rpc.xml182(td)
-#: ./doc/common/tables/keystone-amqp.xml46(td)
-#: ./doc/common/tables/glance-amqp.xml38(td)
-#: ./doc/common/tables/nova-rpc.xml42(td)
-msgid "rpc_backend = rabbit"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml151(td)
-#: ./doc/common/tables/cinder-rpc.xml183(td)
-#: ./doc/common/tables/keystone-amqp.xml47(td)
-#: ./doc/common/tables/glance-amqp.xml39(td)
-#: ./doc/common/tables/nova-rpc.xml43(td)
+#: ./doc/common/tables/nova-vmware.xml27(td)
 msgid ""
-"(StrOpt) The messaging driver to use, defaults to rabbit. Other drivers "
-"include qpid and zmq."
+"(MultiStrOpt) Name of a VMware Cluster ComputeResource. Used only if "
+"compute_driver is vmwareapi.VMwareVCDriver."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml154(td)
-#: ./doc/common/tables/heat-rpc.xml42(td)
-#: ./doc/common/tables/glance-zmq.xml22(td)
-#: ./doc/common/tables/cinder-rpc.xml186(td)
-#: ./doc/common/tables/keystone-amqp.xml50(td)
-#: ./doc/common/tables/ceilometer-rpc.xml34(td)
-#: ./doc/common/tables/neutron-rpc.xml46(td)
-#: ./doc/common/tables/trove-rpc.xml54(td)
-#: ./doc/common/tables/nova-rpc.xml46(td)
-msgid "rpc_cast_timeout = 30"
+#: ./doc/common/tables/nova-vmware.xml30(td)
+msgid "datastore_regex = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml155(td)
-#: ./doc/common/tables/heat-rpc.xml43(td)
-#: ./doc/common/tables/glance-zmq.xml23(td)
-#: ./doc/common/tables/cinder-rpc.xml187(td)
-#: ./doc/common/tables/keystone-amqp.xml51(td)
-#: ./doc/common/tables/ceilometer-rpc.xml35(td)
-#: ./doc/common/tables/neutron-rpc.xml47(td)
-#: ./doc/common/tables/trove-rpc.xml55(td)
-#: ./doc/common/tables/nova-rpc.xml47(td)
+#: ./doc/common/tables/nova-vmware.xml31(td)
+msgid "(StrOpt) Regex to match the name of a datastore."
+msgstr ""
+
+#: ./doc/common/tables/nova-vmware.xml34(td)
+msgid "host_ip = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-vmware.xml35(td)
+msgid "(StrOpt) Hostname or IP address for connection to VMware ESX/VC host."
+msgstr ""
+
+#: ./doc/common/tables/nova-vmware.xml38(td)
+msgid "host_password = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-vmware.xml39(td)
+msgid "(StrOpt) Password for connection to VMware ESX/VC host."
+msgstr ""
+
+#: ./doc/common/tables/nova-vmware.xml42(td)
+msgid "host_username = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-vmware.xml43(td)
+msgid "(StrOpt) Username for connection to VMware ESX/VC host."
+msgstr ""
+
+#: ./doc/common/tables/nova-vmware.xml47(td)
+msgid "(StrOpt) Name of Integration Bridge"
+msgstr ""
+
+#: ./doc/common/tables/nova-vmware.xml50(td)
+msgid "maximum_objects = 100"
+msgstr ""
+
+#: ./doc/common/tables/nova-vmware.xml51(td)
 msgid ""
-"(IntOpt) Seconds to wait before a cast expires (TTL). Only supported by "
-"impl_zmq."
+"(IntOpt) The maximum number of ObjectContent data objects that should be "
+"returned in a single result. A positive value will cause the operation to "
+"suspend the retrieval when the count of objects reaches the specified "
+"maximum. The server may still limit the count to something less than the "
+"configured value. Any remaining objects may be retrieved with additional "
+"requests."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml158(td)
-#: ./doc/common/tables/heat-rpc.xml46(td)
-#: ./doc/common/tables/cinder-rpc.xml190(td)
-#: ./doc/common/tables/keystone-amqp.xml54(td)
-#: ./doc/common/tables/ceilometer-rpc.xml38(td)
-#: ./doc/common/tables/neutron-rpc.xml50(td)
-#: ./doc/common/tables/glance-amqp.xml42(td)
-#: ./doc/common/tables/trove-rpc.xml58(td)
-#: ./doc/common/tables/nova-rpc.xml50(td)
-msgid "rpc_conn_pool_size = 30"
+#: ./doc/common/tables/nova-vmware.xml55(td)
+msgid "(FloatOpt) The interval used for polling of remote tasks."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml159(td)
-#: ./doc/common/tables/cinder-rpc.xml191(td)
-#: ./doc/common/tables/keystone-amqp.xml55(td)
-#: ./doc/common/tables/glance-amqp.xml43(td)
-#: ./doc/common/tables/nova-rpc.xml51(td)
-msgid "(IntOpt) Size of RPC connection pool."
-msgstr "(整数オプション) RPC 接続プールの容量。"
-
-#: ./doc/common/tables/nova-rpc_all.xml162(td)
-#: ./doc/common/tables/heat-rpc.xml50(td)
-#: ./doc/common/tables/cinder-rpc.xml194(td)
-#: ./doc/common/tables/keystone-amqp.xml58(td)
-#: ./doc/common/tables/ceilometer-rpc.xml42(td)
-#: ./doc/common/tables/neutron-rpc.xml54(td)
-#: ./doc/common/tables/glance-amqp.xml46(td)
-#: ./doc/common/tables/trove-rpc.xml62(td)
-#: ./doc/common/tables/nova-rpc.xml54(td)
-msgid "rpc_response_timeout = 60"
+#: ./doc/common/tables/nova-vmware.xml58(td)
+msgid "use_linked_clone = True"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml163(td)
-#: ./doc/common/tables/cinder-rpc.xml195(td)
-#: ./doc/common/tables/keystone-amqp.xml59(td)
-#: ./doc/common/tables/glance-amqp.xml47(td)
-#: ./doc/common/tables/nova-rpc.xml55(td)
-msgid "(IntOpt) Seconds to wait for a response from a call."
+#: ./doc/common/tables/nova-vmware.xml59(td)
+msgid "(BoolOpt) Whether to use linked clone"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml166(td)
-#: ./doc/common/tables/heat-rpc.xml54(td)
-#: ./doc/common/tables/cinder-rpc.xml198(td)
-#: ./doc/common/tables/keystone-amqp.xml62(td)
-#: ./doc/common/tables/ceilometer-rpc.xml46(td)
-#: ./doc/common/tables/neutron-rpc.xml58(td)
-#: ./doc/common/tables/glance-amqp.xml50(td)
-#: ./doc/common/tables/trove-rpc.xml66(td)
-#: ./doc/common/tables/nova-rpc.xml58(td)
-msgid "rpc_thread_pool_size = 64"
+#: ./doc/common/tables/nova-vmware.xml62(td)
+msgid "wsdl_location = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml167(td)
-#: ./doc/common/tables/cinder-rpc.xml199(td)
-#: ./doc/common/tables/keystone-amqp.xml63(td)
-#: ./doc/common/tables/glance-amqp.xml51(td)
-#: ./doc/common/tables/nova-rpc.xml59(td)
-msgid "(IntOpt) Size of RPC greenthread pool."
+#: ./doc/common/tables/nova-vmware.xml63(td)
+msgid ""
+"(StrOpt) Optional VIM Service WSDL Location e.g "
+"http://&lt;server&gt;/vimService.wsdl. Optional over-ride to default "
+"location for bug work-arounds"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml170(td)
-#: ./doc/common/tables/glance-zmq.xml26(td)
+#: ./doc/common/tables/heat-cfn_api.xml8(caption)
+msgid "Description of configuration options for cfn_api"
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml22(td)
+msgid "instance_connection_https_validate_certificates = 1"
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml23(td)
+msgid ""
+"(StrOpt) Instance connection to CFN/CW API validate certs if SSL is used."
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml26(td)
+msgid "instance_connection_is_secure = 0"
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml27(td)
+msgid "(StrOpt) Instance connection to CFN/CW API via https."
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml30(th)
+msgid "[heat_api_cfn]"
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml34(td)
+#: ./doc/common/tables/heat-api.xml104(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml30(td)
+msgid "(IntOpt) Number of backlog requests to configure the socket with."
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml37(td)
+#: ./doc/common/tables/heat-api.xml107(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml33(td)
+#: ./doc/common/tables/glance-common.xml34(td)
+#: ./doc/common/tables/neutron-common.xml70(td)
+msgid "bind_host = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml38(td)
+#: ./doc/common/tables/heat-api.xml108(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml34(td)
+#: ./doc/common/tables/glance-common.xml35(td)
+msgid ""
+"(StrOpt) Address to bind the server. Useful when selecting a particular "
+"network interface."
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml41(td)
+msgid "bind_port = 8000"
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml42(td)
+#: ./doc/common/tables/heat-api.xml112(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml38(td)
+#: ./doc/common/tables/glance-common.xml39(td)
+msgid "(IntOpt) The port on which the server will listen."
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml46(td)
+#: ./doc/common/tables/heat-api.xml116(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml42(td)
+msgid "(StrOpt) Location of the SSL certificate file to use for SSL mode."
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml50(td)
+#: ./doc/common/tables/heat-api.xml120(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml46(td)
+msgid "(StrOpt) Location of the SSL key file to use for enabling SSL mode."
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml53(td)
+#: ./doc/common/tables/trove-api.xml66(td)
+#: ./doc/common/tables/heat-api.xml123(td)
+#: ./doc/common/tables/cinder-api.xml46(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml49(td)
+#: ./doc/common/tables/glance-wsgi.xml30(td)
+#: ./doc/common/tables/nova-api.xml42(td)
+#: ./doc/common/tables/neutron-api.xml42(td)
+msgid "max_header_line = 16384"
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml54(td)
+#: ./doc/common/tables/heat-api.xml124(td)
+#: ./doc/common/tables/cinder-api.xml47(td)
+#: ./doc/common/tables/nova-api.xml43(td)
+msgid ""
+"(IntOpt) Maximum line size of message headers to be accepted. "
+"max_header_line may need to be increased when using large tokens (typically "
+"those generated by the Keystone v3 API with big service catalogs)."
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml57(td)
+#: ./doc/common/tables/heat-api.xml127(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml53(td)
+msgid "workers = 0"
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml58(td)
+#: ./doc/common/tables/heat-api.xml128(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml54(td)
+msgid "(IntOpt) Number of workers for Heat service."
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml61(th)
+#: ./doc/common/tables/heat-api.xml142(th)
+#: ./doc/common/tables/keystone-ssl.xml54(th)
+#: ./doc/common/tables/nova-ca.xml62(th)
+#: ./doc/common/tables/cinder-ssl.xml19(th)
+#: ./doc/common/tables/trove-ssl.xml19(th)
+#: ./doc/common/tables/heat-cloudwatch_api.xml57(th)
+#: ./doc/common/tables/neutron-ssl.xml34(th)
+#: ./doc/common/tables/ceilometer-ssl.xml19(th)
+msgid "[ssl]"
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml65(td)
+#: ./doc/common/tables/heat-api.xml146(td)
+#: ./doc/common/tables/cinder-common.xml175(td)
+#: ./doc/common/tables/cinder-ssl.xml23(td)
+#: ./doc/common/tables/trove-ssl.xml23(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml61(td)
+#: ./doc/common/tables/neutron-ssl.xml23(td)
+#: ./doc/common/tables/neutron-ssl.xml38(td)
+#: ./doc/common/tables/nova-wsgi.xml27(td)
+#: ./doc/common/tables/ceilometer-ssl.xml23(td)
+msgid "(StrOpt) CA certificate file to use to verify connecting clients"
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml69(td)
+#: ./doc/common/tables/heat-api.xml150(td)
+#: ./doc/common/tables/cinder-common.xml179(td)
+#: ./doc/common/tables/cinder-ssl.xml27(td)
+#: ./doc/common/tables/trove-ssl.xml27(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml65(td)
+#: ./doc/common/tables/neutron-ssl.xml27(td)
+#: ./doc/common/tables/neutron-ssl.xml42(td)
+#: ./doc/common/tables/ceilometer-ssl.xml27(td)
+msgid "(StrOpt) Certificate file to use when starting the server securely"
+msgstr ""
+
+#: ./doc/common/tables/heat-cfn_api.xml73(td)
+#: ./doc/common/tables/heat-api.xml154(td)
+#: ./doc/common/tables/cinder-common.xml183(td)
+#: ./doc/common/tables/cinder-ssl.xml31(td)
+#: ./doc/common/tables/trove-ssl.xml31(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml69(td)
+#: ./doc/common/tables/neutron-ssl.xml31(td)
+#: ./doc/common/tables/neutron-ssl.xml46(td)
+#: ./doc/common/tables/ceilometer-ssl.xml31(td)
+msgid "(StrOpt) Private key file to use when starting the server securely"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml22(td)
+msgid "default_interface_name = breth0"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml23(td)
+msgid ""
+"(StrOpt) Name of the interface on a L2 Gateway transport nodewhich should be"
+" used by default when setting up a network connection"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml26(td)
+msgid "default_l2_gw_service_uuid = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml27(td)
+msgid ""
+"(StrOpt) Unique identifier of the NSX L2 Gateway service which will be used "
+"by default for network gateways"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml30(td)
+msgid "default_l3_gw_service_uuid = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml31(td)
+msgid ""
+"(StrOpt) Unique identifier of the NSX L3 Gateway service which will be used "
+"for implementing routers and floating IPs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml34(td)
+msgid "default_service_cluster_uuid = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml35(td)
+msgid ""
+"(StrOpt) Unique identifier of the Service Cluster which will be used by "
+"logical services like dhcp and metadata"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml38(td)
+msgid "default_tz_uuid = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml39(td)
+msgid ""
+"(StrOpt) This is uuid of the default NSX Transport zone that will be used "
+"for creating tunneled isolated \"Neutron\" networks. It needs to be created "
+"in NSX before starting Neutron with the nsx plugin."
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml42(td)
+msgid "http_timeout = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml43(td)
+msgid "(IntOpt) Time before aborting a request"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml46(td)
+msgid "nsx_controllers = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml47(td)
+msgid "(ListOpt) Lists the NSX controllers in this cluster"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml50(td)
+msgid "nsx_password = admin"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml51(td)
+msgid "(StrOpt) Password for NSX controllers in this cluster"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml54(td)
+msgid "nsx_user = admin"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml55(td)
+msgid "(StrOpt) User name for NSX controllers in this cluster"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml58(td)
+msgid "redirects = 2"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml59(td)
+msgid "(IntOpt) Number of times a redirect should be followed"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml62(td)
+msgid "req_timeout = 30"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml63(td)
+msgid "(IntOpt) Total time limit for a cluster request"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml66(td)
+msgid "retries = 2"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml67(td)
+msgid "(IntOpt) Number of time a request should be retried"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml70(th)
+#: ./doc/common/tables/neutron-ml2_mlnx.xml19(th)
+#: ./doc/common/tables/neutron-mlnx.xml19(th)
+msgid "[ESWITCH]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml73(td)
+msgid "retries = 3"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml74(td)
+msgid ""
+"(IntOpt) The number of retries the agent will send request to daemon before "
+"giving up"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml77(th)
+msgid "[NSX]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml80(td)
+msgid "agent_mode = agent"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml81(td)
+msgid "(StrOpt) The mode used to implement DHCP/metadata services."
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml84(td)
+msgid "concurrent_connections = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml85(td)
+msgid "(IntOpt) Maximum concurrent connections to each NSX controller."
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml88(td)
+msgid "default_transport_type = stt"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml89(td)
+msgid ""
+"(StrOpt) The default network tranport type to use (stt, gre, bridge, "
+"ipsec_gre, or ipsec_stt)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml92(td)
+msgid "max_lp_per_bridged_ls = 5000"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml93(td)
+msgid ""
+"(IntOpt) Maximum number of ports of a logical switch on a bridged transport "
+"zone (default 5000)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml96(td)
+msgid "max_lp_per_overlay_ls = 256"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml97(td)
+msgid ""
+"(IntOpt) Maximum number of ports of a logical switch on an overlay transport"
+" zone (default 256)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml100(td)
+msgid "metadata_mode = access_network"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml101(td)
+msgid ""
+"(StrOpt) If set to access_network this enables a dedicated connection to the"
+" metadata proxy for metadata server access via Neutron router. If set to "
+"dhcp_host_route this enables host route injection via the dhcp agent. This "
+"option is only useful if running on a host that does not support namespaces "
+"otherwise access_network should be used."
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml104(td)
+msgid "nsx_gen_timeout = -1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml105(td)
+msgid ""
+"(IntOpt) Number of seconds a generation id should be valid for (default -1 "
+"meaning do not time out)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml108(td)
+msgid "replication_mode = service"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml109(td)
+msgid ""
+"(StrOpt) The default option leverages service nodes to perform packet "
+"replication though one could set to this to 'source' to perform replication "
+"locally. This is useful if one does not want to deploy a service node(s)."
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml112(th)
+msgid "[NSX_DHCP]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml115(td)
+msgid "default_lease_time = 43200"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml116(td)
+msgid "(IntOpt) Default DHCP lease time"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml119(td)
+msgid "domain_name = openstacklocal"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml120(td)
+#: ./doc/common/tables/nova-network.xml51(td)
+#: ./doc/common/tables/neutron-common.xml111(td)
+msgid "(StrOpt) Domain to use for building the hostnames"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml123(td)
+msgid "extra_domain_name_servers ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml124(td)
+msgid "(ListOpt) Comma separated list of additional domain name servers"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml127(th)
+msgid "[NSX_LSN]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml130(td)
+msgid "sync_on_missing_data = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml131(td)
+msgid ""
+"(BoolOpt) Pull LSN information from NSX in case it is missing from the local"
+" data store. This is useful to rebuild the local store in case of server "
+"recovery."
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml134(th)
+msgid "[NSX_METADATA]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml137(td)
+msgid "metadata_server_address = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml138(td)
+msgid "(StrOpt) IP address used by Metadata server."
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml141(td)
+msgid "metadata_server_port = 8775"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml142(td)
+msgid "(IntOpt) TCP Port used by Metadata server."
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml145(td)
+msgid "metadata_shared_secret ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml146(td)
+#: ./doc/common/tables/neutron-metadata.xml35(td)
+msgid "(StrOpt) Shared secret to sign instance-id request"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml149(th)
+msgid "[NSX_SYNC]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml152(td)
+msgid "always_read_status = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml153(td)
+msgid ""
+"(BoolOpt) Always read operational status from backend on show operations. "
+"Enabling this option might slow down the system."
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml156(td)
+msgid "max_random_sync_delay = 0"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml157(td)
+msgid ""
+"(IntOpt) Maximum value for the additional random delay in seconds between "
+"runs of the state synchronization task"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml160(td)
+msgid "min_chunk_size = 500"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml161(td)
+msgid ""
+"(IntOpt) Minimum number of resources to be retrieved from NSX during state "
+"synchronization"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml164(td)
+msgid "min_sync_req_delay = 1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml165(td)
+msgid ""
+"(IntOpt) Minimum delay, in seconds, between two state synchronization "
+"queries to NSX. It must not exceed state_sync_interval"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml168(td)
+msgid "state_sync_interval = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml169(td)
+msgid ""
+"(IntOpt) Interval in seconds between runs of the state synchronization task."
+" Set it to 0 to disable it"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml172(th)
+msgid "[vcns]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml175(td)
+msgid "datacenter_moid = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml176(td)
+msgid ""
+"(StrOpt) Optional parameter identifying the ID of datacenter to deploy NSX "
+"Edges"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml179(td)
+msgid "datastore_id = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml180(td)
+#: ./doc/common/tables/neutron-vmware.xml184(td)
+msgid ""
+"(StrOpt) Optional parameter identifying the ID of datastore to deploy NSX "
+"Edges"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml183(td)
+msgid "deployment_container_id = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml187(td)
+msgid "external_network = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml188(td)
+msgid "(StrOpt) Network ID for physical network connectivity"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml191(td)
+msgid "manager_uri = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml192(td)
+msgid "(StrOpt) uri for vsm"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml195(td)
+msgid "password = default"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml196(td)
+msgid "(StrOpt) Password for vsm"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml199(td)
+#: ./doc/common/tables/neutron-embrane_lb.xml62(td)
+msgid "resource_pool_id = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml200(td)
+msgid ""
+"(StrOpt) Optional parameter identifying the ID of resource to deploy NSX "
+"Edges"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml203(td)
+msgid "task_status_check_interval = 2000"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml204(td)
+msgid "(IntOpt) Task status check interval"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml207(td)
+msgid "user = admin"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vmware.xml208(td)
+msgid "(StrOpt) User name for vsm"
+msgstr ""
+
+#: ./doc/common/tables/nova-rdp.xml8(caption)
+msgid "Description of configuration options for rdp"
+msgstr ""
+
+#: ./doc/common/tables/nova-rdp.xml19(th)
+msgid "[rdp]"
+msgstr ""
+
+#: ./doc/common/tables/nova-rdp.xml23(td)
+msgid "(BoolOpt) Enable RDP related features"
+msgstr ""
+
+#: ./doc/common/tables/nova-rdp.xml26(td)
+msgid "html5_proxy_base_url = http://127.0.0.1:6083/"
+msgstr ""
+
+#: ./doc/common/tables/nova-rdp.xml27(td)
+msgid ""
+"(StrOpt) Location of RDP html5 console proxy, in the form "
+"\"http://127.0.0.1:6083/\""
+msgstr ""
+
+#: ./doc/common/tables/keystone-assignment.xml8(caption)
+msgid "Description of configuration options for assignment"
+msgstr ""
+
+#: ./doc/common/tables/keystone-assignment.xml19(th)
+msgid "[assignment]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-assignment.xml22(td)
+#: ./doc/common/tables/keystone-token.xml26(td)
+msgid "cache_time = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-assignment.xml23(td)
+msgid ""
+"(IntOpt) TTL (in seconds) to cache assignment data. This has no effect "
+"unless global caching is enabled."
+msgstr ""
+
+#: ./doc/common/tables/keystone-assignment.xml26(td)
+#: ./doc/common/tables/keystone-revoke.xml22(td)
+#: ./doc/common/tables/keystone-token.xml30(td)
+msgid "caching = True"
+msgstr ""
+
+#: ./doc/common/tables/keystone-assignment.xml27(td)
+msgid ""
+"(BoolOpt) Toggle for assignment caching. This has no effect unless global "
+"caching is enabled."
+msgstr ""
+
+#: ./doc/common/tables/keystone-assignment.xml30(td)
+msgid "driver = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-assignment.xml31(td)
+msgid "(StrOpt) Keystone Assignment backend driver."
+msgstr ""
+
+#: ./doc/common/tables/keystone-assignment.xml35(td)
+msgid ""
+"(IntOpt) Maximum number of entities that will be returned in an assignment "
+"collection."
+msgstr ""
+
+#: ./doc/common/tables/nova-zeromq.xml8(caption)
+#: ./doc/common/tables/heat-zeromq.xml8(caption)
+#: ./doc/common/tables/neutron-zeromq.xml8(caption)
+#: ./doc/common/tables/keystone-zeromq.xml8(caption)
+#: ./doc/common/tables/trove-zeromq.xml8(caption)
+msgid "Description of configuration options for zeromq"
+msgstr ""
+
+#: ./doc/common/tables/nova-zeromq.xml22(td)
+#: ./doc/common/tables/heat-zeromq.xml22(td)
+#: ./doc/common/tables/neutron-zeromq.xml22(td)
 #: ./doc/common/tables/keystone-zeromq.xml22(td)
+#: ./doc/common/tables/ceilometer-rpc.xml50(td)
+#: ./doc/common/tables/glance-zmq.xml26(td)
 #: ./doc/common/tables/cinder-rpc.xml202(td)
 #: ./doc/common/tables/trove-zeromq.xml22(td)
-#: ./doc/common/tables/ceilometer-rpc.xml50(td)
-#: ./doc/common/tables/heat-zeromq.xml22(td)
-#: ./doc/common/tables/nova-zeromq.xml22(td)
-#: ./doc/common/tables/neutron-zeromq.xml22(td)
+#: ./doc/common/tables/nova-rpc_all.xml170(td)
 msgid "rpc_zmq_bind_address = *"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml171(td)
-#: ./doc/common/tables/glance-zmq.xml27(td)
+#: ./doc/common/tables/nova-zeromq.xml23(td)
+#: ./doc/common/tables/heat-zeromq.xml23(td)
+#: ./doc/common/tables/neutron-zeromq.xml23(td)
 #: ./doc/common/tables/keystone-zeromq.xml23(td)
+#: ./doc/common/tables/ceilometer-rpc.xml51(td)
+#: ./doc/common/tables/glance-zmq.xml27(td)
 #: ./doc/common/tables/cinder-rpc.xml203(td)
 #: ./doc/common/tables/trove-zeromq.xml23(td)
-#: ./doc/common/tables/ceilometer-rpc.xml51(td)
-#: ./doc/common/tables/heat-zeromq.xml23(td)
-#: ./doc/common/tables/nova-zeromq.xml23(td)
-#: ./doc/common/tables/neutron-zeromq.xml23(td)
+#: ./doc/common/tables/nova-rpc_all.xml171(td)
 msgid ""
 "(StrOpt) ZeroMQ bind address. Should be a wildcard (*), an ethernet "
 "interface, or IP. The \"host\" option should point or resolve to this "
 "address."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml174(td)
-#: ./doc/common/tables/glance-zmq.xml30(td)
+#: ./doc/common/tables/nova-zeromq.xml26(td)
+#: ./doc/common/tables/heat-zeromq.xml26(td)
+#: ./doc/common/tables/neutron-zeromq.xml26(td)
 #: ./doc/common/tables/keystone-zeromq.xml26(td)
+#: ./doc/common/tables/ceilometer-rpc.xml54(td)
+#: ./doc/common/tables/glance-zmq.xml30(td)
 #: ./doc/common/tables/cinder-rpc.xml206(td)
 #: ./doc/common/tables/trove-zeromq.xml26(td)
-#: ./doc/common/tables/ceilometer-rpc.xml54(td)
-#: ./doc/common/tables/heat-zeromq.xml26(td)
-#: ./doc/common/tables/nova-zeromq.xml26(td)
-#: ./doc/common/tables/neutron-zeromq.xml26(td)
+#: ./doc/common/tables/nova-rpc_all.xml174(td)
 msgid "rpc_zmq_contexts = 1"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml175(td)
-#: ./doc/common/tables/glance-zmq.xml31(td)
-#: ./doc/common/tables/keystone-zeromq.xml27(td)
-#: ./doc/common/tables/cinder-rpc.xml207(td)
 #: ./doc/common/tables/nova-zeromq.xml27(td)
+#: ./doc/common/tables/keystone-zeromq.xml27(td)
+#: ./doc/common/tables/glance-zmq.xml31(td)
+#: ./doc/common/tables/cinder-rpc.xml207(td)
+#: ./doc/common/tables/nova-rpc_all.xml175(td)
 msgid "(IntOpt) Number of ZeroMQ contexts, defaults to 1."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml178(td)
-#: ./doc/common/tables/glance-zmq.xml34(td)
+#: ./doc/common/tables/nova-zeromq.xml30(td)
+#: ./doc/common/tables/heat-zeromq.xml30(td)
+#: ./doc/common/tables/neutron-zeromq.xml30(td)
 #: ./doc/common/tables/keystone-zeromq.xml30(td)
+#: ./doc/common/tables/ceilometer-rpc.xml58(td)
+#: ./doc/common/tables/glance-zmq.xml34(td)
 #: ./doc/common/tables/cinder-rpc.xml210(td)
 #: ./doc/common/tables/trove-zeromq.xml30(td)
-#: ./doc/common/tables/ceilometer-rpc.xml58(td)
-#: ./doc/common/tables/heat-zeromq.xml30(td)
-#: ./doc/common/tables/nova-zeromq.xml30(td)
-#: ./doc/common/tables/neutron-zeromq.xml30(td)
+#: ./doc/common/tables/nova-rpc_all.xml178(td)
 msgid "rpc_zmq_host = oslo"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml179(td)
-#: ./doc/common/tables/glance-zmq.xml35(td)
+#: ./doc/common/tables/nova-zeromq.xml31(td)
+#: ./doc/common/tables/heat-zeromq.xml31(td)
+#: ./doc/common/tables/neutron-zeromq.xml31(td)
 #: ./doc/common/tables/keystone-zeromq.xml31(td)
+#: ./doc/common/tables/ceilometer-rpc.xml59(td)
+#: ./doc/common/tables/glance-zmq.xml35(td)
 #: ./doc/common/tables/cinder-rpc.xml211(td)
 #: ./doc/common/tables/trove-zeromq.xml31(td)
-#: ./doc/common/tables/ceilometer-rpc.xml59(td)
-#: ./doc/common/tables/heat-zeromq.xml31(td)
-#: ./doc/common/tables/nova-zeromq.xml31(td)
-#: ./doc/common/tables/neutron-zeromq.xml31(td)
+#: ./doc/common/tables/nova-rpc_all.xml179(td)
 msgid ""
 "(StrOpt) Name of this node. Must be a valid hostname, FQDN, or IP address. "
 "Must match \"host\" option, if running Nova."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml182(td)
-#: ./doc/common/tables/glance-zmq.xml38(td)
+#: ./doc/common/tables/nova-zeromq.xml34(td)
+#: ./doc/common/tables/heat-zeromq.xml34(td)
+#: ./doc/common/tables/neutron-zeromq.xml34(td)
 #: ./doc/common/tables/keystone-zeromq.xml34(td)
+#: ./doc/common/tables/ceilometer-rpc.xml62(td)
+#: ./doc/common/tables/glance-zmq.xml38(td)
 #: ./doc/common/tables/cinder-rpc.xml214(td)
 #: ./doc/common/tables/trove-zeromq.xml34(td)
-#: ./doc/common/tables/ceilometer-rpc.xml62(td)
-#: ./doc/common/tables/heat-zeromq.xml34(td)
-#: ./doc/common/tables/nova-zeromq.xml34(td)
-#: ./doc/common/tables/neutron-zeromq.xml34(td)
+#: ./doc/common/tables/nova-rpc_all.xml182(td)
 msgid "rpc_zmq_ipc_dir = /var/run/openstack"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml183(td)
-#: ./doc/common/tables/glance-zmq.xml39(td)
-#: ./doc/common/tables/keystone-zeromq.xml35(td)
-#: ./doc/common/tables/cinder-rpc.xml215(td)
 #: ./doc/common/tables/nova-zeromq.xml35(td)
+#: ./doc/common/tables/keystone-zeromq.xml35(td)
+#: ./doc/common/tables/glance-zmq.xml39(td)
+#: ./doc/common/tables/cinder-rpc.xml215(td)
+#: ./doc/common/tables/nova-rpc_all.xml183(td)
 msgid "(StrOpt) Directory for holding IPC sockets."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml186(td)
-#: ./doc/common/tables/glance-zmq.xml42(td)
-#: ./doc/common/tables/keystone-zeromq.xml38(td)
-#: ./doc/common/tables/cinder-rpc.xml218(td)
 #: ./doc/common/tables/nova-zeromq.xml38(td)
+#: ./doc/common/tables/keystone-zeromq.xml38(td)
+#: ./doc/common/tables/glance-zmq.xml42(td)
+#: ./doc/common/tables/cinder-rpc.xml218(td)
+#: ./doc/common/tables/nova-rpc_all.xml186(td)
 msgid ""
 "rpc_zmq_matchmaker = oslo.messaging._drivers.matchmaker.MatchMakerLocalhost"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml187(td)
-#: ./doc/common/tables/glance-zmq.xml43(td)
-#: ./doc/common/tables/keystone-zeromq.xml39(td)
-#: ./doc/common/tables/cinder-rpc.xml219(td)
 #: ./doc/common/tables/nova-zeromq.xml39(td)
+#: ./doc/common/tables/keystone-zeromq.xml39(td)
+#: ./doc/common/tables/glance-zmq.xml43(td)
+#: ./doc/common/tables/cinder-rpc.xml219(td)
+#: ./doc/common/tables/nova-rpc_all.xml187(td)
 msgid "(StrOpt) MatchMaker driver."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml190(td)
-#: ./doc/common/tables/glance-zmq.xml46(td)
+#: ./doc/common/tables/nova-zeromq.xml42(td)
+#: ./doc/common/tables/heat-zeromq.xml42(td)
+#: ./doc/common/tables/neutron-zeromq.xml42(td)
 #: ./doc/common/tables/keystone-zeromq.xml42(td)
+#: ./doc/common/tables/ceilometer-rpc.xml70(td)
+#: ./doc/common/tables/glance-zmq.xml46(td)
 #: ./doc/common/tables/cinder-rpc.xml222(td)
 #: ./doc/common/tables/trove-zeromq.xml42(td)
-#: ./doc/common/tables/ceilometer-rpc.xml70(td)
-#: ./doc/common/tables/heat-zeromq.xml42(td)
-#: ./doc/common/tables/nova-zeromq.xml42(td)
-#: ./doc/common/tables/neutron-zeromq.xml42(td)
+#: ./doc/common/tables/nova-rpc_all.xml190(td)
 msgid "rpc_zmq_port = 9501"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml191(td)
-#: ./doc/common/tables/glance-zmq.xml47(td)
-#: ./doc/common/tables/keystone-zeromq.xml43(td)
-#: ./doc/common/tables/cinder-rpc.xml223(td)
 #: ./doc/common/tables/nova-zeromq.xml43(td)
+#: ./doc/common/tables/keystone-zeromq.xml43(td)
+#: ./doc/common/tables/glance-zmq.xml47(td)
+#: ./doc/common/tables/cinder-rpc.xml223(td)
+#: ./doc/common/tables/nova-rpc_all.xml191(td)
 msgid "(IntOpt) ZeroMQ receiver listening port."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml194(td)
-#: ./doc/common/tables/glance-zmq.xml50(td)
+#: ./doc/common/tables/nova-zeromq.xml46(td)
+#: ./doc/common/tables/heat-zeromq.xml46(td)
+#: ./doc/common/tables/neutron-zeromq.xml46(td)
 #: ./doc/common/tables/keystone-zeromq.xml46(td)
+#: ./doc/common/tables/ceilometer-rpc.xml74(td)
+#: ./doc/common/tables/glance-zmq.xml50(td)
 #: ./doc/common/tables/cinder-rpc.xml226(td)
 #: ./doc/common/tables/trove-zeromq.xml46(td)
-#: ./doc/common/tables/ceilometer-rpc.xml74(td)
-#: ./doc/common/tables/heat-zeromq.xml46(td)
-#: ./doc/common/tables/nova-zeromq.xml46(td)
-#: ./doc/common/tables/neutron-zeromq.xml46(td)
+#: ./doc/common/tables/nova-rpc_all.xml194(td)
 msgid "rpc_zmq_topic_backlog = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml195(td)
-#: ./doc/common/tables/glance-zmq.xml51(td)
+#: ./doc/common/tables/nova-zeromq.xml47(td)
+#: ./doc/common/tables/heat-zeromq.xml47(td)
+#: ./doc/common/tables/neutron-zeromq.xml47(td)
 #: ./doc/common/tables/keystone-zeromq.xml47(td)
+#: ./doc/common/tables/ceilometer-rpc.xml75(td)
+#: ./doc/common/tables/glance-zmq.xml51(td)
 #: ./doc/common/tables/cinder-rpc.xml227(td)
 #: ./doc/common/tables/trove-zeromq.xml47(td)
-#: ./doc/common/tables/ceilometer-rpc.xml75(td)
-#: ./doc/common/tables/heat-zeromq.xml47(td)
-#: ./doc/common/tables/nova-zeromq.xml47(td)
-#: ./doc/common/tables/neutron-zeromq.xml47(td)
+#: ./doc/common/tables/nova-rpc_all.xml195(td)
 msgid ""
 "(IntOpt) Maximum number of ingress messages to locally buffer per topic. "
 "Default is unlimited."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml201(td)
-#: ./doc/common/tables/nova-rpc.xml65(td)
-msgid "rpc_driver_queue_base = cells.intercell"
+#: ./doc/common/tables/cinder-storage.xml8(caption)
+msgid "Description of configuration options for storage"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml202(td)
-#: ./doc/common/tables/nova-rpc.xml66(td)
+#: ./doc/common/tables/cinder-storage.xml22(td)
+msgid "allocated_capacity_weight_multiplier = -1.0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml23(td)
+#: ./doc/common/tables/cinder-storage.xml27(td)
 msgid ""
-"(StrOpt) Base queue name to use when communicating between cells. Various "
-"topics by message type will be appended to this."
+"(FloatOpt) Multiplier used for weighing volume capacity. Negative numbers "
+"mean to stack vs spread."
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml205(th)
-#: ./doc/common/tables/trove-redis.xml34(th)
-#: ./doc/common/tables/heat-rpc.xml58(th)
-#: ./doc/common/tables/ceilometer-redis.xml49(th)
-#: ./doc/common/tables/cinder-rpc.xml238(th)
-#: ./doc/common/tables/neutron-rpc.xml73(th)
-#: ./doc/common/tables/keystone-redis.xml42(th)
-#: ./doc/common/tables/glance-matchmaker.xml30(th)
-#: ./doc/common/tables/nova-rpc.xml69(th)
-msgid "[matchmaker_ring]"
+#: ./doc/common/tables/cinder-storage.xml26(td)
+msgid "capacity_weight_multiplier = 1.0"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml208(td)
-#: ./doc/common/tables/trove-redis.xml37(td)
-#: ./doc/common/tables/heat-rpc.xml61(td)
-#: ./doc/common/tables/ceilometer-redis.xml52(td)
-#: ./doc/common/tables/cinder-rpc.xml241(td)
-#: ./doc/common/tables/neutron-rpc.xml76(td)
-#: ./doc/common/tables/keystone-redis.xml45(td)
-#: ./doc/common/tables/glance-matchmaker.xml33(td)
-#: ./doc/common/tables/nova-rpc.xml72(td)
-msgid "ringfile = /etc/oslo/matchmaker_ring.json"
+#: ./doc/common/tables/cinder-storage.xml30(td)
+msgid "enabled_backends = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-rpc_all.xml209(td)
-#: ./doc/common/tables/cinder-rpc.xml242(td)
-#: ./doc/common/tables/keystone-redis.xml46(td)
-#: ./doc/common/tables/glance-matchmaker.xml34(td)
-#: ./doc/common/tables/nova-rpc.xml73(td)
-msgid "(StrOpt) Matchmaker ring file (JSON)."
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml212(th)
-#: ./doc/common/tables/nova-rpc.xml76(th)
-#: ./doc/common/tables/nova-upgrade_levels.xml26(th)
-msgid "[upgrade_levels]"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml215(td)
-#: ./doc/common/tables/nova-rpc.xml79(td)
-msgid "baseapi = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-rpc_all.xml216(td)
-#: ./doc/common/tables/nova-rpc.xml80(td)
+#: ./doc/common/tables/cinder-storage.xml31(td)
 msgid ""
-"(StrOpt) Set a version cap for messages sent to the base api in any service"
+"(ListOpt) A list of backend names to use. These backend names should be "
+"backed by a unique [CONFIG] group with its options"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_l2pop.xml8(caption)
-msgid "Description of configuration options for ml2_l2pop"
+#: ./doc/common/tables/cinder-storage.xml34(td)
+msgid "iscsi_helper = tgtadm"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_l2pop.xml19(th)
-msgid "[l2pop]"
+#: ./doc/common/tables/cinder-storage.xml35(td)
+msgid "(StrOpt) iscsi target user-land tool to use"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_l2pop.xml22(td)
-msgid "agent_boot_time = 180"
+#: ./doc/common/tables/cinder-storage.xml38(td)
+msgid "iscsi_iotype = fileio"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_l2pop.xml23(td)
+#: ./doc/common/tables/cinder-storage.xml39(td)
 msgid ""
-"(IntOpt) Delay within which agent is expected to update existing ports whent"
-" it restarts"
+"(StrOpt) Sets the behavior of the iSCSI target to either perform blockio or "
+"fileio optionally, auto can be set and Cinder will autodetect type of "
+"backing device"
 msgstr ""
 
-#: ./doc/common/tables/glance-qpid.xml8(caption)
-#: ./doc/common/tables/keystone-qpid.xml8(caption)
-#: ./doc/common/tables/trove-qpid.xml8(caption)
-#: ./doc/common/tables/heat-qpid.xml8(caption)
-#: ./doc/common/tables/neutron-qpid.xml8(caption)
-#: ./doc/common/tables/nova-qpid.xml8(caption)
-#: ./doc/common/tables/ceilometer-qpid.xml8(caption)
-msgid "Description of configuration options for qpid"
+#: ./doc/common/tables/cinder-storage.xml42(td)
+msgid "iscsi_ip_address = $my_ip"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml7(literal)
-#: ./doc/common/tables/swift-container-server-container-updater.xml7(literal)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml7(literal)
-#: ./doc/common/tables/swift-container-server-container-sync.xml7(literal)
-#: ./doc/common/tables/swift-container-server-pipeline-main.xml7(literal)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml7(literal)
+#: ./doc/common/tables/cinder-storage.xml43(td)
+msgid "(StrOpt) The IP address that the iSCSI daemon is listening on"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml46(td)
+msgid "iscsi_num_targets = 100"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml47(td)
+msgid "(IntOpt) The maximum number of iscsi target ids per host"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml50(td)
+msgid "iscsi_port = 3260"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml51(td)
+msgid "(IntOpt) The port that the iSCSI daemon is listening on"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml54(td)
+msgid "iscsi_target_prefix = iqn.2010-10.org.openstack:"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml55(td)
+msgid "(StrOpt) prefix for iscsi volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml58(td)
+msgid "iser_helper = tgtadm"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml59(td)
+msgid "(StrOpt) iser target user-land tool to use"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml62(td)
+msgid "iser_ip_address = $my_ip"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml63(td)
+msgid "(StrOpt) The IP address that the iSER daemon is listening on"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml66(td)
+msgid "iser_num_targets = 100"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml67(td)
+msgid "(IntOpt) The maximum number of iser target ids per host"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml70(td)
+msgid "iser_port = 3260"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml71(td)
+msgid "(IntOpt) The port that the iSER daemon is listening on"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml74(td)
+msgid "iser_target_prefix = iqn.2010-10.org.iser.openstack:"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml75(td)
+msgid "(StrOpt) prefix for iser volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml78(td)
+msgid "max_gigabytes = 10000"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml79(td)
+msgid ""
+"(IntOpt) This configure option has been deprecated along with the "
+"SimpleScheduler. New scheduler is able to gather capacity information for "
+"each host, thus setting the maximum number of volume gigabytes for host is "
+"no longer needed. It's safe to remove this configure from cinder.conf."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml82(td)
+msgid "migration_create_volume_timeout_secs = 300"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml83(td)
+msgid ""
+"(IntOpt) Timeout for creating the volume to migrate to when performing "
+"volume migration (seconds)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml86(td)
+msgid "num_iser_scan_tries = 3"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml87(td)
+msgid ""
+"(IntOpt) The maximum number of times to rescan iSER targetto find volume"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml90(td)
+msgid "num_volume_device_scan_tries = 3"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml91(td)
+msgid "(IntOpt) The maximum number of times to rescan targets to find volume"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml94(td)
+msgid "volume_backend_name = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml95(td)
+msgid "(StrOpt) The backend name for a given driver implementation"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml98(td)
+#: ./doc/common/tables/nova-libvirt.xml85(td)
+msgid "volume_clear = zero"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml99(td)
+msgid ""
+"(StrOpt) Method used to wipe old voumes (valid options are: none, zero, "
+"shred)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml102(td)
+msgid "volume_clear_ionice = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml103(td)
+msgid ""
+"(StrOpt) The flag to pass to ionice to alter the i/o priority of the process"
+" used to zero a volume after deletion, for example \"-c3\" for idle only "
+"priority."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml106(td)
+#: ./doc/common/tables/nova-libvirt.xml89(td)
+msgid "volume_clear_size = 0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml107(td)
+#: ./doc/common/tables/nova-libvirt.xml90(td)
+msgid "(IntOpt) Size in MiB to wipe at start of old volumes. 0 =&gt; all"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml110(td)
+msgid "volume_dd_blocksize = 1M"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml111(td)
+msgid "(StrOpt) The default block size used when copying/clearing volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml114(td)
+msgid "volume_driver = cinder.volume.drivers.lvm.LVMISCSIDriver"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml115(td)
+msgid "(StrOpt) Driver to use for volume creation"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml118(td)
+msgid "volume_manager = cinder.volume.manager.VolumeManager"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml119(td)
+msgid "(StrOpt) full class name for the Manager for volume"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml122(td)
+msgid "volume_service_inithost_offload = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml123(td)
+msgid "(BoolOpt) Offload pending volume delete during volume service startup"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml126(td)
+msgid "volume_usage_audit_period = month"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml127(td)
+msgid ""
+"(StrOpt) time period to generate volume usages for. Time period must be "
+"hour, day, month or year"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml130(td)
+msgid "volumes_dir = $state_path/volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml131(td)
+msgid "(StrOpt) Volume configuration file storage directory"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml145(td)
+msgid "max_pool_size = 5"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage.xml150(td)
+#: ./doc/common/tables/heat-database.xml66(td)
+msgid ""
+"(IntOpt) maximum db connection retries during startup. (setting -1 implies "
+"an infinite retry count)"
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml8(caption)
+msgid "Description of configuration options for registry"
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml23(td)
+msgid "(StrOpt) The administrators password."
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml26(td)
+#: ./doc/common/tables/neutron-common.xml26(td)
+#: ./doc/common/tables/neutron-common.xml196(td)
+msgid "admin_tenant_name = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml27(td)
+msgid "(StrOpt) The tenant name of the administrative user."
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml31(td)
+msgid "(StrOpt) The administrators user name."
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml34(td)
+#: ./doc/common/tables/neutron-common.xml54(td)
+#: ./doc/common/tables/neutron-common.xml204(td)
+msgid "auth_region = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml35(td)
+msgid "(StrOpt) The region for the authentication service."
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml39(td)
+msgid "(StrOpt) The strategy to use for authentication."
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml42(td)
+#: ./doc/common/tables/neutron-common.xml62(td)
+#: ./doc/common/tables/neutron-common.xml212(td)
+msgid "auth_url = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml43(td)
+msgid "(StrOpt) The URL to the keystone service."
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml46(td)
+msgid "registry_client_ca_file = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml47(td)
+msgid ""
+"(StrOpt) The path to the certifying authority cert file to use in SSL "
+"connections to the registry server."
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml50(td)
+msgid "registry_client_cert_file = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml51(td)
+msgid ""
+"(StrOpt) The path to the cert file to use in SSL connections to the registry"
+" server."
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml54(td)
+msgid "registry_client_insecure = False"
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml55(td)
+msgid ""
+"(BoolOpt) When using SSL in connections to the registry server, do not "
+"require validation via a certifying authority."
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml58(td)
+msgid "registry_client_key_file = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml59(td)
+msgid ""
+"(StrOpt) The path to the key file to use in SSL connections to the registry "
+"server."
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml62(td)
+msgid "registry_client_protocol = http"
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml63(td)
+msgid ""
+"(StrOpt) The protocol to use for communication with the registry server. "
+"Either http or https."
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml66(td)
+msgid "registry_client_timeout = 600"
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml67(td)
+msgid ""
+"(IntOpt) The period of time, in seconds, that the API server will wait for a"
+" registry request to complete. A value of 0 implies no timeout."
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml70(td)
+msgid "registry_host = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml71(td)
+msgid "(StrOpt) Address to find the registry server."
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml74(td)
+msgid "registry_port = 9191"
+msgstr ""
+
+#: ./doc/common/tables/glance-registry.xml75(td)
+msgid "(IntOpt) Port the registry server is listening on."
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml8(caption)
+msgid "Description of configuration options for embrane"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml19(th)
+#: ./doc/common/tables/neutron-common.xml216(th)
+msgid "[heleos]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml22(td)
+msgid "admin_username = admin"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml23(td)
+#: ./doc/common/tables/neutron-embrane_lb.xml27(td)
+msgid "(StrOpt) ESM admin username."
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml26(td)
+msgid "async_requests = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml27(td)
+#: ./doc/common/tables/neutron-embrane_lb.xml31(td)
+msgid "(BoolOpt) Define if the requests have run asynchronously or not"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml30(td)
+#: ./doc/common/tables/neutron-embrane_lb.xml34(td)
+msgid "dummy_utif_id = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml31(td)
+msgid "(StrOpt) Dummy user traffic Security Zone id"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml34(td)
+#: ./doc/common/tables/neutron-embrane_lb.xml38(td)
+msgid "esm_mgmt = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml35(td)
+#: ./doc/common/tables/neutron-embrane_lb.xml39(td)
+msgid "(StrOpt) ESM management root address"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml38(td)
+#: ./doc/common/tables/neutron-embrane_lb.xml42(td)
+msgid "inband_id = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml39(td)
+msgid "(StrOpt) In band Security Zone id"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml42(td)
+#: ./doc/common/tables/neutron-embrane_lb.xml54(td)
+msgid "mgmt_id = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml43(td)
+msgid "(StrOpt) Management Security Zone id"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml46(td)
+#: ./doc/common/tables/neutron-embrane_lb.xml58(td)
+msgid "oob_id = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml47(td)
+msgid "(StrOpt) Out of band Security Zone id"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml50(td)
+msgid "resource_pool_id = default"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml51(td)
+#: ./doc/common/tables/neutron-embrane_lb.xml63(td)
+msgid "(StrOpt) Shared resource pool id"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml54(td)
+msgid "router_image = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane.xml55(td)
+msgid "(StrOpt) Router image id (Embrane FW/VPN)"
+msgstr ""
+
+#: ./doc/common/tables/heat-quota.xml22(td)
+msgid "max_events_per_stack = 1000"
+msgstr ""
+
+#: ./doc/common/tables/heat-quota.xml23(td)
+msgid ""
+"(IntOpt) Maximum events that will be available per stack. Older events will "
+"be deleted when this is reached. Set to 0 for unlimited events per stack."
+msgstr ""
+
+#: ./doc/common/tables/heat-quota.xml26(td)
+msgid "max_nested_stack_depth = 3"
+msgstr ""
+
+#: ./doc/common/tables/heat-quota.xml27(td)
+msgid "(IntOpt) Maximum depth allowed when using nested stacks."
+msgstr ""
+
+#: ./doc/common/tables/heat-quota.xml30(td)
+msgid "max_resources_per_stack = 1000"
+msgstr ""
+
+#: ./doc/common/tables/heat-quota.xml31(td)
+msgid "(IntOpt) Maximum resources allowed per top-level stack."
+msgstr ""
+
+#: ./doc/common/tables/heat-quota.xml34(td)
+msgid "max_stacks_per_tenant = 100"
+msgstr ""
+
+#: ./doc/common/tables/heat-quota.xml35(td)
+msgid ""
+"(IntOpt) Maximum number of stacks any one tenant may have active at one "
+"time."
+msgstr ""
+
+#: ./doc/common/tables/heat-quota.xml38(td)
+msgid "max_template_size = 524288"
+msgstr ""
+
+#: ./doc/common/tables/heat-quota.xml39(td)
+msgid "(IntOpt) Maximum raw byte size of any template."
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml7(literal)
 #: ./doc/common/tables/swift-container-server-filter-healthcheck.xml7(literal)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml7(literal)
-#: ./doc/common/tables/swift-container-server-filter-recon.xml7(literal)
-msgid "container-server.conf-sample"
+#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml7(literal)
+#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml7(literal)
+msgid "[filter:healthcheck]"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml18(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml18(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml18(td)
-msgid "bind_ip = 0.0.0.0"
+#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml7(literal)
+#: ./doc/common/tables/swift-account-server-filter-recon.xml7(literal)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml7(literal)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml7(literal)
+#: ./doc/common/tables/swift-account-server-pipeline-main.xml7(literal)
+#: ./doc/common/tables/swift-account-server-account-auditor.xml7(literal)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml7(literal)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml7(literal)
+msgid "account-server.conf-sample"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml18(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml18(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml18(td)
-msgid "IP Address for server to bind to"
-msgstr "サーバーがバインドする IP アドレス"
-
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml21(td)
-msgid "bind_port = 6001"
+#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml18(td)
+#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml18(td)
+#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml18(td)
+#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml18(td)
+msgid "use = egg:swift#healthcheck"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml21(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml21(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml21(td)
-msgid "Port for server to bind to"
-msgstr "サーバーがバインドするポート"
-
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml24(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml24(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml24(td)
-msgid "bind_timeout = 30"
+#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml21(td)
+#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml21(td)
+#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml21(td)
+#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml21(td)
+msgid "disable_path ="
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml24(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml24(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml24(td)
-msgid "Seconds to attempt bind before giving up"
+#: ./doc/common/tables/nova-common.xml22(td)
+msgid "bindir = /usr/local/bin"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml27(td)
-#: ./doc/common/tables/heat-cfn_api.xml33(td)
-#: ./doc/common/tables/trove-debug.xml26(td)
-#: ./doc/common/tables/neutron-wsgi.xml22(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml27(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml27(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml29(td)
-#: ./doc/common/tables/glance-common.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml27(td)
-#: ./doc/common/tables/heat-api.xml103(td)
-msgid "backlog = 4096"
+#: ./doc/common/tables/nova-common.xml23(td)
+msgid "(StrOpt) Directory where nova binaries are installed"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml27(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml27(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml27(td)
-msgid "Maximum number of allowed pending TCP connections"
+#: ./doc/common/tables/nova-common.xml26(td)
+msgid "compute_topic = compute"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml30(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml21(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml30(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml33(td)
-msgid "user = swift"
-msgstr "user = swift"
-
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml30(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml21(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml30(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml30(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml33(td)
-msgid "User to run as"
-msgstr "実行するユーザー"
-
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml33(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml18(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml33(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml33(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml45(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml30(td)
-msgid "swift_dir = /etc/swift"
+#: ./doc/common/tables/nova-common.xml27(td)
+msgid "(StrOpt) The topic compute nodes listen on"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml33(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml18(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml33(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml33(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml45(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml30(td)
-msgid "Swift configuration directory"
-msgstr "Swift 設定ディレクトリー"
-
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml36(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml36(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml36(td)
-msgid "devices = /srv/node"
+#: ./doc/common/tables/nova-common.xml30(td)
+msgid "console_topic = console"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml36(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml36(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml36(td)
-msgid "Parent directory of where devices are mounted"
-msgstr "デバイスがマウントされる場所の親ディレクトリー"
-
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml39(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml39(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml39(td)
-msgid "mount_check = true"
+#: ./doc/common/tables/nova-common.xml31(td)
+msgid "(StrOpt) The topic console proxy nodes listen on"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml39(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml39(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml39(td)
+#: ./doc/common/tables/nova-common.xml34(td)
+msgid "consoleauth_topic = consoleauth"
+msgstr ""
+
+#: ./doc/common/tables/nova-common.xml35(td)
+msgid "(StrOpt) The topic console auth proxy nodes listen on"
+msgstr ""
+
+#: ./doc/common/tables/nova-common.xml39(td)
+#: ./doc/common/tables/cinder-common.xml43(td)
+#: ./doc/common/tables/heat-debug.xml31(td)
+#: ./doc/common/tables/glance-common.xml47(td)
+#: ./doc/common/tables/neutron-common.xml123(td)
+#: ./doc/common/tables/trove-debug.xml35(td)
+#: ./doc/common/tables/keystone-debug.xml31(td)
+msgid "(BoolOpt) Whether to disable inter-process locks"
+msgstr ""
+
+#: ./doc/common/tables/nova-common.xml43(td)
 msgid ""
-"Whether or not check if the devices are mounted to prevent accidentally "
-"writing to the root device"
-msgstr "不注意によりルートデバイスに書き込むことを防ぐために、デバイスがマウントされているかを確認するかどうか"
-
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml42(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml42(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml42(td)
-msgid "disable_fallocate = false"
+"(StrOpt) Name of this node. This can be an opaque identifier. It is not "
+"necessarily a hostname, FQDN, or IP address. However, the node name must be "
+"valid within an AMQP key, and if using ZeroMQ, a valid hostname, FQDN, or IP"
+" address"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml42(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml42(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml42(td)
+#: ./doc/common/tables/nova-common.xml54(td)
+#: ./doc/common/tables/cinder-common.xml118(td)
+msgid "my_ip = 10.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/nova-common.xml55(td)
+msgid "(StrOpt) IP address of this host"
+msgstr ""
+
+#: ./doc/common/tables/nova-common.xml59(td)
+#: ./doc/common/tables/keystone-amqp.xml39(td)
+#: ./doc/common/tables/glance-amqp.xml31(td)
+#: ./doc/common/tables/cinder-rpc.xml75(td)
+msgid "(MultiStrOpt) Driver or drivers to handle sending notifications."
+msgstr ""
+
+#: ./doc/common/tables/nova-common.xml63(td)
+#: ./doc/common/tables/keystone-amqp.xml43(td)
+#: ./doc/common/tables/glance-amqp.xml35(td)
+#: ./doc/common/tables/cinder-rpc.xml79(td)
+msgid "(ListOpt) AMQP topic used for OpenStack notifications."
+msgstr ""
+
+#: ./doc/common/tables/nova-common.xml66(td)
+msgid "notify_api_faults = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-common.xml67(td)
 msgid ""
-"Disable \"fast fail\" fallocate checks if the underlying filesystem does not"
-" support it."
+"(BoolOpt) If set, send api.fault notifications on caught exceptions in the "
+"API service."
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml45(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml51(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml45(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml45(td)
-msgid "workers = auto"
+#: ./doc/common/tables/nova-common.xml70(td)
+msgid "notify_on_state_change = None"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml45(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml51(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml45(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml45(td)
+#: ./doc/common/tables/nova-common.xml71(td)
 msgid ""
-"a much higher value, one can reduce the impact of slow file system "
-"operations in one request from negatively impacting other requests."
+"(StrOpt) If set, send compute.instance.update notifications on instance "
+"state changes. Valid values are None for no notifications, \"vm_state\" for "
+"notifications on VM state changes, or \"vm_and_task_state\" for "
+"notifications on VM and task state changes."
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml48(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml54(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml48(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml48(td)
-msgid "max_clients = 1024"
+#: ./doc/common/tables/nova-common.xml78(td)
+msgid "pybasedir = /usr/lib/python/site-packages"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml48(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml54(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml48(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml48(td)
+#: ./doc/common/tables/nova-common.xml79(td)
+msgid "(StrOpt) Directory where the nova python module is installed"
+msgstr ""
+
+#: ./doc/common/tables/nova-common.xml82(td)
+#: ./doc/common/tables/cinder-common.xml146(td)
+#: ./doc/common/tables/trove-rpc.xml46(td)
+msgid "report_interval = 10"
+msgstr ""
+
+#: ./doc/common/tables/nova-common.xml83(td)
+msgid "(IntOpt) Seconds between nodes reporting state to datastore"
+msgstr ""
+
+#: ./doc/common/tables/nova-common.xml86(td)
+msgid "rootwrap_config = /etc/nova/rootwrap.conf"
+msgstr ""
+
+#: ./doc/common/tables/nova-common.xml87(td)
+#: ./doc/common/tables/cinder-common.xml155(td)
 msgid ""
-"Maximum number of clients one worker can process simultaneously Lowering the"
-" number of clients handled per worker, and raising the number of workers can"
-" lessen the impact that a CPU intensive, or blocking, request can have on "
-"other requests served by the same worker. If the maximum number of clients "
-"is set to one, then a given worker will not perform another call while "
-"processing, allowing other workers a chance to process it."
+"(StrOpt) Path to the rootwrap configuration file to use for running commands"
+" as root"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml58(td)
-msgid "allowed_sync_hosts = 127.0.0.1"
+#: ./doc/common/tables/nova-common.xml90(td)
+#: ./doc/common/tables/cinder-common.xml162(td)
+msgid "service_down_time = 60"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml61(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml24(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml64(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml58(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml70(td)
-msgid "log_name = swift"
+#: ./doc/common/tables/nova-common.xml91(td)
+msgid "(IntOpt) Maximum time since last check-in for up service"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml61(td)
-#: ./doc/common/tables/swift-container-server-container-updater.xml18(td)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml18(td)
-#: ./doc/common/tables/swift-container-server-container-sync.xml18(td)
-#: ./doc/common/tables/swift-object-server-object-auditor.xml18(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml24(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml18(td)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml18(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml64(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml58(td)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml18(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml18(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml18(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml70(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml18(td)
-msgid "Label used when logging"
-msgstr "ログ取得するときに使用するラベル"
-
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml64(td)
-#: ./doc/common/tables/swift-container-server-container-updater.xml21(td)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml21(td)
-#: ./doc/common/tables/swift-container-server-container-sync.xml21(td)
-#: ./doc/common/tables/swift-object-server-object-auditor.xml21(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml27(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml21(td)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml21(td)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml33(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml67(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml61(td)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml21(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml21(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml73(td)
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml21(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml21(td)
-msgid "log_facility = LOG_LOCAL0"
+#: ./doc/common/tables/nova-common.xml94(td)
+msgid "state_path = $pybasedir"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml67(td)
-#: ./doc/common/tables/swift-container-server-container-updater.xml24(td)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml24(td)
-#: ./doc/common/tables/swift-container-server-container-sync.xml24(td)
-#: ./doc/common/tables/swift-object-server-object-auditor.xml24(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml30(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml24(td)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml24(td)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml36(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml70(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml64(td)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml24(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml24(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml76(td)
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml24(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml24(td)
-msgid "log_level = INFO"
+#: ./doc/common/tables/nova-common.xml95(td)
+msgid "(StrOpt) Top-level directory for maintaining nova's state"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml67(td)
-#: ./doc/common/tables/swift-container-server-container-updater.xml24(td)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml24(td)
-#: ./doc/common/tables/swift-container-server-container-sync.xml24(td)
-#: ./doc/common/tables/swift-object-server-object-auditor.xml24(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml30(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml24(td)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml24(td)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml36(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml70(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml64(td)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml24(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml24(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml76(td)
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml24(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml24(td)
-msgid "Logging level"
-msgstr "ログレベル"
-
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml70(td)
-#: ./doc/common/tables/swift-container-server-container-updater.xml27(td)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml27(td)
-#: ./doc/common/tables/swift-container-server-container-sync.xml27(td)
-#: ./doc/common/tables/swift-object-server-object-auditor.xml27(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml33(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml27(td)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml27(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml73(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml67(td)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml27(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml27(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml82(td)
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml27(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml27(td)
-msgid "log_address = /dev/log"
+#: ./doc/common/tables/nova-common.xml98(td)
+msgid "tempdir = None"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml73(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml36(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml76(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml70(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml88(td)
-msgid "log_custom_handlers ="
+#: ./doc/common/tables/nova-common.xml99(td)
+msgid "(StrOpt) Explicitly specify the temporary working directory"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml73(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml36(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml76(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml70(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml88(td)
+#: ./doc/common/tables/nova-common.xml102(td)
+#: ./doc/common/tables/keystone-amqp.xml66(td)
+#: ./doc/common/tables/glance-amqp.xml54(td)
+#: ./doc/common/tables/cinder-rpc.xml230(td)
+msgid "transport_url = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-common.xml103(td)
+#: ./doc/common/tables/keystone-amqp.xml67(td)
+#: ./doc/common/tables/glance-amqp.xml55(td)
+#: ./doc/common/tables/cinder-rpc.xml231(td)
 msgid ""
-"Comma-separated list of functions to call to setup custom log handlers."
+"(StrOpt) A URL representing the messaging driver to use and its full "
+"configuration. If not set, we fall back to the rpc_backend option and driver"
+" specific configuration."
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml76(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml39(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml79(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml73(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml91(td)
-msgid "log_udp_host ="
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml7(literal)
+#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml7(literal)
+msgid "[app:proxy-server]"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml76(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml39(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml79(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml73(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml91(td)
-msgid "If not set, the UDB receiver for syslog is disabled."
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml18(td)
+#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml18(td)
+msgid "use = egg:swift#proxy"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml79(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml42(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml82(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml76(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml94(td)
-msgid "log_udp_port = 514"
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml21(td)
+msgid "set log_name = proxy-server"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml79(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml42(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml82(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml76(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml94(td)
-msgid "Port value for UDB receiver, if enabled."
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml33(td)
+msgid "log_handoffs = true"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml82(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml45(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml85(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml79(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml97(td)
-msgid "log_statsd_host = localhost"
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml36(td)
+msgid "recheck_account_existence = 60"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml82(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml45(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml85(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml79(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml97(td)
-msgid "If not set, the StatsD feature is disabled."
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml36(td)
+msgid "Cache timeout in seconds to send memcached for account existence"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml85(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml48(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml88(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml82(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml100(td)
-msgid "log_statsd_port = 8125"
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml39(td)
+msgid "recheck_container_existence = 60"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml85(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml48(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml88(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml82(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml100(td)
-msgid "Port value for the StatsD server."
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml39(td)
+msgid "Cache timeout in seconds to send memcached for container existence"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml88(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml51(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml91(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml85(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml103(td)
-msgid "log_statsd_default_sample_rate = 1.0"
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml42(td)
+msgid "object_chunk_size = 8192"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml88(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml51(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml91(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml85(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml103(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml42(td)
+msgid "Chunk size to read from object servers"
+msgstr "オブジェクトサーバーから読み込むチャンク容量"
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml45(td)
+msgid "client_chunk_size = 8192"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml45(td)
+msgid "Chunk size to read from clients"
+msgstr "クライアントから読み込むチャンク容量"
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml48(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml51(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml45(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml36(td)
+msgid "node_timeout = 10"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml48(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml112(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml51(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml36(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml57(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml36(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml45(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml36(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml36(td)
+msgid "Request timeout to external services"
+msgstr "外部サービスへのリクエストのタイムアウト"
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml51(td)
+msgid "recoverable_node_timeout = node_timeout"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml51(td)
 msgid ""
-"Defines the probability of sending a sample for any given event or timing "
-"measurement."
+"Request timeout to external services for requests that, on failure, can be "
+"recovered from. For example, object GET. from a client external services"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml92(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml55(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml95(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml89(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml107(td)
-msgid "log_statsd_sample_rate_factor = 1.0"
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml54(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml109(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml54(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml39(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml39(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml48(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml39(td)
+msgid "conn_timeout = 0.5"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml92(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml55(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml95(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml89(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml107(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml54(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml109(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml54(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml39(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml39(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml48(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml39(td)
+msgid "Connection timeout to external services"
+msgstr "外部サービスへの接続のタイムアウト"
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml57(td)
+msgid "post_quorum_timeout = 0.5"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml60(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml45(td)
+msgid "error_suppression_interval = 60"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml60(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml45(td)
 msgid ""
-"Not recommended to set this to a value less than 1.0, if frequency of "
-"logging is too high, tune the log_statsd_default_sample_rate instead."
+"Time in seconds that must elapse since the last error for a node to be "
+"considered no longer error limited"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml97(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml60(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml100(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml94(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml112(td)
-msgid "log_statsd_metric_prefix ="
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml63(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml48(td)
+msgid "error_suppression_limit = 10"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml97(td)
-#: ./doc/common/tables/swift-object-expirer-DEFAULT.xml60(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml100(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml94(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml112(td)
-msgid "Value will be prepended to every metric sent to the StatsD server."
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml63(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml48(td)
+msgid "Error count to consider a node error limited"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml100(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml97(td)
-msgid "db_preallocation = off"
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml66(td)
+msgid "allow_account_management = false"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml100(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml97(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml66(td)
+msgid "Whether account PUTs and DELETEs are even callable"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml69(td)
+msgid "object_post_as_copy = true"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml69(td)
 msgid ""
-"If you don't mind the extra disk space usage in overhead, you can turn this "
-"on to preallocate disk space with SQLite databases to decrease "
-"fragmentation. underlying filesystem does not support it. to setup custom "
-"log handlers. bytes you'd like fallocate to reserve, whether there is space "
-"for the given file size or not. This is useful for systems that behave badly"
-" when they completely run out of space; you can make the services pretend "
-"they're out of space early. server. For most cases, this should be "
-"`egg:swift#account`. replication passes account can be reclaimed"
+"Set object_post_as_copy = false to turn on fast posts where only the "
+"metadata changes are stored anew and the original data file is kept in "
+"place. This makes for quicker posts; but since the container metadata isn't "
+"updated in this mode, features like container sync won't be able to sync "
+"posts."
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml103(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml103(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml100(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml121(td)
-msgid "eventlet_debug = false"
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml72(td)
+msgid "account_autocreate = false"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml103(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml103(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml100(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml121(td)
-msgid "If true, turn on debug logging for eventlet"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml106(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml106(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml103(td)
-msgid "fallocate_reserve = 0"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-DEFAULT.xml106(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml106(td)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml103(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml72(td)
 msgid ""
-"You can set fallocate_reserve to the number of bytes you'd like fallocate to"
-" reserve, whether there is space for the given file size or not. This is "
-"useful for systems that behave badly when they completely run out of space; "
-"you can make the services pretend they're out of space early. server. For "
-"most cases, this should be `egg:swift#object`."
+"If set to 'true' authorized accounts that do not yet exist within the Swift "
+"cluster will be automatically created."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml8(caption)
-msgid "Description of configuration options for ml2_bigswitch"
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml75(td)
+msgid "max_containers_per_account = 0"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml19(th)
-#: ./doc/common/tables/neutron-bigswitch.xml19(th)
-msgid "[NOVA]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml22(td)
-#: ./doc/common/tables/neutron-bigswitch.xml22(td)
-msgid "node_override_vif_802.1qbg ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml23(td)
-#: ./doc/common/tables/neutron-bigswitch.xml23(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to 802.1qbg"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml26(td)
-#: ./doc/common/tables/neutron-bigswitch.xml26(td)
-msgid "node_override_vif_802.1qbh ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml27(td)
-#: ./doc/common/tables/neutron-bigswitch.xml27(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to 802.1qbh"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml30(td)
-#: ./doc/common/tables/neutron-bigswitch.xml30(td)
-msgid "node_override_vif_binding_failed ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml31(td)
-#: ./doc/common/tables/neutron-bigswitch.xml31(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml75(td)
 msgid ""
-"(ListOpt) Nova compute nodes to manually set VIF type to binding_failed"
+"If set to a positive value, trying to create a container when the account "
+"already has at least this maximum containers will result in a 403 Forbidden."
+" Note: This is a soft limit, meaning a user might exceed the cap for "
+"recheck_account_existence before the 403s kick in."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml34(td)
-#: ./doc/common/tables/neutron-bigswitch.xml34(td)
-msgid "node_override_vif_bridge ="
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml78(td)
+msgid "max_containers_whitelist ="
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml35(td)
-#: ./doc/common/tables/neutron-bigswitch.xml35(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to bridge"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml38(td)
-#: ./doc/common/tables/neutron-bigswitch.xml38(td)
-msgid "node_override_vif_hostdev ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml39(td)
-#: ./doc/common/tables/neutron-bigswitch.xml39(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to hostdev"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml42(td)
-#: ./doc/common/tables/neutron-bigswitch.xml42(td)
-msgid "node_override_vif_hyperv ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml43(td)
-#: ./doc/common/tables/neutron-bigswitch.xml43(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to hyperv"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml46(td)
-#: ./doc/common/tables/neutron-bigswitch.xml46(td)
-msgid "node_override_vif_ivs ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml47(td)
-#: ./doc/common/tables/neutron-bigswitch.xml47(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to ivs"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml50(td)
-#: ./doc/common/tables/neutron-bigswitch.xml50(td)
-msgid "node_override_vif_midonet ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml51(td)
-#: ./doc/common/tables/neutron-bigswitch.xml51(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to midonet"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml54(td)
-#: ./doc/common/tables/neutron-bigswitch.xml54(td)
-msgid "node_override_vif_mlnx_direct ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml55(td)
-#: ./doc/common/tables/neutron-bigswitch.xml55(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to mlnx_direct"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml58(td)
-#: ./doc/common/tables/neutron-bigswitch.xml58(td)
-msgid "node_override_vif_other ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml59(td)
-#: ./doc/common/tables/neutron-bigswitch.xml59(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to other"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml62(td)
-#: ./doc/common/tables/neutron-bigswitch.xml62(td)
-msgid "node_override_vif_ovs ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml63(td)
-#: ./doc/common/tables/neutron-bigswitch.xml63(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to ovs"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml66(td)
-#: ./doc/common/tables/neutron-bigswitch.xml66(td)
-msgid "node_override_vif_unbound ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml67(td)
-#: ./doc/common/tables/neutron-bigswitch.xml67(td)
-msgid "(ListOpt) Nova compute nodes to manually set VIF type to unbound"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml70(td)
-#: ./doc/common/tables/neutron-bigswitch.xml70(td)
-msgid "vif_type = ovs"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml71(td)
-#: ./doc/common/tables/neutron-bigswitch.xml71(td)
-msgid "(StrOpt) Virtual interface type to configure on Nova compute nodes"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml74(td)
-#: ./doc/common/tables/neutron-bigswitch.xml74(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml78(td)
 msgid ""
-"vif_types = unbound, binding_failed, ovs, ivs, bridge, 802.1qbg, 802.1qbh, "
-"hyperv, midonet, mlnx_direct, hostdev, other"
+"is a comma separated list of account names that ignore the "
+"max_containers_per_account cap."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml75(td)
-#: ./doc/common/tables/neutron-bigswitch.xml75(td)
-msgid "(ListOpt) List of allowed vif_type values."
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml81(td)
+msgid "deny_host_headers ="
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml78(th)
-#: ./doc/common/tables/neutron-bigswitch.xml78(th)
-#: ./doc/common/tables/neutron-nuage.xml19(th)
-msgid "[RESTPROXY]"
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml84(td)
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml21(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml54(td)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml36(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml45(td)
+msgid "auto_create_account_prefix = ."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml81(td)
-#: ./doc/common/tables/neutron-bigswitch.xml81(td)
-msgid "add_meta_server_route = True"
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml84(td)
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml21(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml54(td)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml36(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml45(td)
+msgid "Prefix to use when automatically creating accounts"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml82(td)
-#: ./doc/common/tables/neutron-bigswitch.xml82(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml87(td)
+msgid "put_queue_depth = 10"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml90(td)
+msgid "sorting_method = shuffle"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml93(td)
+msgid "timing_expiry = 300"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml96(td)
+msgid "max_large_object_get_time = 86400"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml99(td)
+msgid "request_node_count = 2 * replicas"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml99(td)
 msgid ""
-"(BoolOpt) Flag to decide if a route to the metadata server should be "
-"injected into the VM"
+"* replicas Set to the number of nodes to contact for a normal request. You "
+"can use '* replicas' at the end to have it use the number given times the "
+"number of replicas for the ring being used for the request. conf file for "
+"values will only be shown to the list of swift_owners. The exact default "
+"definition of a swift_owner is headers&gt; up to the auth system in use, but"
+" usually indicates administrative responsibilities. paste.deploy to use for "
+"auth. To use tempauth set to: `egg:swift#tempauth` each request"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml85(td)
-#: ./doc/common/tables/neutron-bigswitch.xml85(td)
-msgid "auto_sync_on_failure = True"
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml102(td)
+msgid "read_affinity = r1z1=100, r1z2=200, r2=300"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml86(td)
-#: ./doc/common/tables/neutron-bigswitch.xml86(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml105(td)
+msgid "read_affinity ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml108(td)
+msgid "write_affinity = r1, r2"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml111(td)
+msgid "write_affinity ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml114(td)
+msgid "write_affinity_node_count = 2 * replicas"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml117(td)
 msgid ""
-"(BoolOpt) If neutron fails to create a resource because the backend "
-"controller doesn't know of a dependency, the plugin automatically triggers a"
-" full data synchronization to the controller."
+"swift_owner_headers = x-container-read, x-container-write, x-container-sync-"
+"key, x-container-sync-to, x-account-meta-temp-url-key, x-account-meta-temp-"
+"url-key-2, x-account-access-control"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml89(td)
-#: ./doc/common/tables/neutron-bigswitch.xml89(td)
-msgid "cache_connections = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml90(td)
-#: ./doc/common/tables/neutron-bigswitch.xml90(td)
-msgid "(BoolOpt) Re-use HTTP/HTTPS connections to the controller."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml93(td)
-#: ./doc/common/tables/neutron-bigswitch.xml93(td)
-msgid "consistency_interval = 60"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml94(td)
-#: ./doc/common/tables/neutron-bigswitch.xml94(td)
+#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml117(td)
 msgid ""
-"(IntOpt) Time between verifications that the backend controller database is "
-"consistent with Neutron"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml97(td)
-#: ./doc/common/tables/neutron-bigswitch.xml97(td)
-msgid "neutron_id = neutron-oslo"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml98(td)
-#: ./doc/common/tables/neutron-bigswitch.xml98(td)
-msgid "(StrOpt) User defined identifier for this Neutron deployment"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml101(td)
-#: ./doc/common/tables/neutron-bigswitch.xml101(td)
-msgid "no_ssl_validation = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml102(td)
-#: ./doc/common/tables/neutron-bigswitch.xml102(td)
-msgid "(BoolOpt) Disables SSL certificate validation for controllers"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml105(td)
-#: ./doc/common/tables/neutron-bigswitch.xml105(td)
-msgid "server_auth = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml106(td)
-#: ./doc/common/tables/neutron-bigswitch.xml106(td)
-msgid ""
-"(StrOpt) The username and password for authenticating against the Big Switch"
-" or Floodlight controller."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml109(td)
-#: ./doc/common/tables/neutron-bigswitch.xml109(td)
-msgid "server_ssl = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml110(td)
-#: ./doc/common/tables/neutron-bigswitch.xml110(td)
-msgid ""
-"(BoolOpt) If True, Use SSL when connecting to the Big Switch or Floodlight "
-"controller."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml113(td)
-#: ./doc/common/tables/neutron-bigswitch.xml113(td)
-msgid "server_timeout = 10"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml114(td)
-#: ./doc/common/tables/neutron-bigswitch.xml114(td)
-msgid ""
-"(IntOpt) Maximum number of seconds to wait for proxy request to connect and "
-"complete."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml117(td)
-#: ./doc/common/tables/neutron-bigswitch.xml117(td)
-msgid "servers = localhost:8800"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml118(td)
-#: ./doc/common/tables/neutron-bigswitch.xml118(td)
-msgid ""
-"(ListOpt) A comma separated list of Big Switch or Floodlight servers and "
-"port numbers. The plugin proxies the requests to the Big Switch/Floodlight "
-"server, which performs the networking configuration. Only oneserver is "
-"needed per deployment, but you may wish todeploy multiple servers to support"
-" failover."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml121(td)
-#: ./doc/common/tables/neutron-bigswitch.xml121(td)
-msgid "ssl_cert_directory = /etc/neutron/plugins/bigswitch/ssl"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml122(td)
-#: ./doc/common/tables/neutron-bigswitch.xml122(td)
-msgid ""
-"(StrOpt) Directory containing ca_certs and host_certs certificate "
-"directories."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml125(td)
-#: ./doc/common/tables/neutron-bigswitch.xml125(td)
-msgid "ssl_sticky = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml126(td)
-#: ./doc/common/tables/neutron-bigswitch.xml126(td)
-msgid ""
-"(BoolOpt) Trust and store the first certificate received for each controller"
-" address and use it to validate future connections to that address."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml129(td)
-#: ./doc/common/tables/neutron-bigswitch.xml129(td)
-msgid "sync_data = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml130(td)
-#: ./doc/common/tables/neutron-bigswitch.xml130(td)
-msgid "(BoolOpt) Sync data on connect"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml133(td)
-#: ./doc/common/tables/neutron-bigswitch.xml133(td)
-msgid "thread_pool_size = 4"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml134(td)
-#: ./doc/common/tables/neutron-bigswitch.xml134(td)
-msgid ""
-"(IntOpt) Maximum number of threads to spawn to handle large volumes of port "
-"creations."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml137(th)
-#: ./doc/common/tables/neutron-bigswitch.xml137(th)
-msgid "[RESTPROXYAGENT]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml140(td)
-#: ./doc/common/tables/neutron-openvswitch_agent.xml83(td)
-#: ./doc/common/tables/neutron-bigswitch.xml140(td)
-#: ./doc/common/tables/neutron-cisco.xml73(td)
-#: ./doc/common/tables/nova-vmware.xml46(td)
-#: ./doc/common/tables/neutron-nvsd.xml22(td)
-msgid "integration_bridge = br-int"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml141(td)
-#: ./doc/common/tables/neutron-bigswitch.xml141(td)
-msgid ""
-"(StrOpt) Name of integration bridge on compute nodes used for security group"
-" insertion."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml144(td)
-#: ./doc/common/tables/neutron-bigswitch.xml144(td)
-msgid "polling_interval = 5"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml145(td)
-#: ./doc/common/tables/neutron-bigswitch.xml145(td)
-msgid "(IntOpt) Seconds between agent checks for port changes"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml148(td)
-#: ./doc/common/tables/neutron-bigswitch.xml148(td)
-msgid "virtual_switch_type = ovs"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml149(td)
-#: ./doc/common/tables/neutron-bigswitch.xml149(td)
-msgid "(StrOpt) Virtual switch type."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml152(th)
-#: ./doc/common/tables/neutron-bigswitch.xml152(th)
-msgid "[ROUTER]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml155(td)
-#: ./doc/common/tables/neutron-bigswitch.xml155(td)
-msgid "max_router_rules = 200"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml156(td)
-#: ./doc/common/tables/neutron-bigswitch.xml156(td)
-msgid "(IntOpt) Maximum number of router rules"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml159(td)
-#: ./doc/common/tables/neutron-bigswitch.xml159(td)
-msgid "tenant_default_router_rule = ['*:any:any:permit']"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_bigswitch.xml160(td)
-#: ./doc/common/tables/neutron-bigswitch.xml160(td)
-msgid ""
-"(MultiStrOpt) The default router rules installed in new tenant routers. "
-"Repeat the config option for each rule. Format is "
-"&lt;tenant&gt;:&lt;source&gt;:&lt;destination&gt;:&lt;action&gt; Use an * to"
-" specify default for all tenants."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_gre.xml8(caption)
-msgid "Description of configuration options for ml2_gre"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_gre.xml19(th)
-msgid "[ml2_type_gre]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_gre.xml22(td)
-#: ./doc/common/tables/neutron-openvswitch_agent.xml107(td)
-msgid "tunnel_id_ranges ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_gre.xml23(td)
-msgid ""
-"(ListOpt) Comma-separated list of &lt;tun_min&gt;:&lt;tun_max&gt; tuples "
-"enumerating ranges of GRE tunnel IDs that are available for tenant network "
-"allocation"
+"the sample These are the headers whose conf file for values will only be "
+"shown to the list of swift_owners. The exact default definition of a "
+"swift_owner is headers&gt; up to the auth system in use, but usually "
+"indicates administrative responsibilities. paste.deploy to use for auth. To "
+"use tempauth set to: `egg:swift#tempauth` each request"
 msgstr ""
 
 #: ./doc/common/tables/nova-volumes.xml8(caption)
@@ -28525,13 +35463,6 @@ msgstr ""
 msgid "(IntOpt) Number of cinderclient retries on failed http calls"
 msgstr ""
 
-#: ./doc/common/tables/nova-volumes.xml46(td)
-#: ./doc/common/tables/cinder-compute.xml46(td)
-#: ./doc/common/tables/glance-common.xml82(td)
-#: ./doc/common/tables/ceilometer-auth.xml156(td)
-msgid "os_region_name = None"
-msgstr ""
-
 #: ./doc/common/tables/nova-volumes.xml47(td)
 msgid "(StrOpt) Region name of this node"
 msgstr ""
@@ -28554,8 +35485,8 @@ msgid "(IntOpt) Interval in seconds for gathering volume usages"
 msgstr ""
 
 #: ./doc/common/tables/nova-volumes.xml58(th)
-#: ./doc/common/tables/nova-tilera.xml19(th)
 #: ./doc/common/tables/nova-baremetal.xml19(th)
+#: ./doc/common/tables/nova-tilera.xml19(th)
 msgid "[baremetal]"
 msgstr ""
 
@@ -28606,14 +35537,6 @@ msgstr ""
 msgid "(IntOpt) Interval between volume attachment attempts, in seconds"
 msgstr ""
 
-#: ./doc/common/tables/nova-volumes.xml84(th)
-#: ./doc/common/tables/nova-hypervisor.xml54(th)
-#: ./doc/common/tables/nova-livemigration.xml26(th)
-#: ./doc/common/tables/nova-libvirt.xml30(th)
-#: ./doc/common/tables/nova-xen.xml58(th)
-msgid "[libvirt]"
-msgstr ""
-
 #: ./doc/common/tables/nova-volumes.xml87(td)
 #: ./doc/common/tables/cinder-storage_glusterfs.xml22(td)
 msgid "glusterfs_mount_point_base = $state_path/mnt"
@@ -28678,20 +35601,10 @@ msgid ""
 "Currently supported protocols: [gluster]"
 msgstr ""
 
-#: ./doc/common/tables/nova-volumes.xml115(td)
-#: ./doc/common/tables/cinder-storage_ceph.xml38(td)
-msgid "rbd_secret_uuid = None"
-msgstr ""
-
 #: ./doc/common/tables/nova-volumes.xml116(td)
 msgid "(StrOpt) The libvirt UUID of the secret for the rbd_uservolumes"
 msgstr ""
 
-#: ./doc/common/tables/nova-volumes.xml119(td)
-#: ./doc/common/tables/cinder-storage_ceph.xml42(td)
-msgid "rbd_user = None"
-msgstr ""
-
 #: ./doc/common/tables/nova-volumes.xml120(td)
 msgid "(StrOpt) The RADOS client name for accessing rbd volumes"
 msgstr ""
@@ -28716,12 +35629,6 @@ msgstr ""
 msgid "(StrOpt) Base dir where Scality SOFS shall be mounted"
 msgstr ""
 
-#: ./doc/common/tables/nova-volumes.xml131(th)
-#: ./doc/common/tables/nova-xen.xml65(th)
-#: ./doc/common/tables/nova-baremetal.xml130(th)
-msgid "[xenserver]"
-msgstr ""
-
 #: ./doc/common/tables/nova-volumes.xml134(td)
 msgid "block_device_creation_timeout = 10"
 msgstr ""
@@ -28730,1725 +35637,453 @@ msgstr ""
 msgid "(IntOpt) Time to wait for a block device to be created"
 msgstr ""
 
-#: ./doc/common/tables/glance-gridfs.xml8(caption)
-msgid "Description of configuration options for gridfs"
+#: ./doc/common/tables/neutron-redis.xml23(td)
+msgid "(StrOpt) The hostname Neutron is running on"
 msgstr ""
 
-#: ./doc/common/tables/glance-gridfs.xml22(td)
-msgid "mongodb_store_db = None"
+#: ./doc/common/tables/trove-db_mysql.xml8(caption)
+msgid "Description of configuration options for db_mysql"
 msgstr ""
 
-#: ./doc/common/tables/glance-gridfs.xml23(td)
-msgid "(StrOpt) Database to use."
+#: ./doc/common/tables/trove-db_mysql.xml19(th)
+msgid "[mysql]"
 msgstr ""
 
-#: ./doc/common/tables/glance-gridfs.xml26(td)
-msgid "mongodb_store_uri = None"
+#: ./doc/common/tables/trove-db_mysql.xml42(td)
+msgid "usage_timeout = 400"
 msgstr ""
 
-#: ./doc/common/tables/glance-gridfs.xml27(td)
+#: ./doc/common/tables/heat-zeromq.xml27(td)
+#: ./doc/common/tables/neutron-zeromq.xml27(td)
+#: ./doc/common/tables/ceilometer-rpc.xml55(td)
+#: ./doc/common/tables/trove-zeromq.xml27(td)
+msgid "(IntOpt) Number of ZeroMQ contexts, defaults to 1"
+msgstr ""
+
+#: ./doc/common/tables/heat-zeromq.xml35(td)
+#: ./doc/common/tables/neutron-zeromq.xml35(td)
+#: ./doc/common/tables/ceilometer-rpc.xml63(td)
+#: ./doc/common/tables/trove-zeromq.xml35(td)
+msgid "(StrOpt) Directory for holding IPC sockets"
+msgstr ""
+
+#: ./doc/common/tables/heat-zeromq.xml38(td)
 msgid ""
-"(StrOpt) Hostname or IP address of the instance to connect to, or a mongodb "
-"URI, or a list of hostnames / mongodb URIs. If host is an IPv6 literal it "
-"must be enclosed in '[' and ']' characters following the RFC2732 URL syntax "
-"(e.g. '[::1]' for localhost)."
+"rpc_zmq_matchmaker = "
+"heat.openstack.common.rpc.matchmaker.MatchMakerLocalhost"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml8(caption)
-msgid "Description of configuration options for ml2_arista"
+#: ./doc/common/tables/heat-zeromq.xml39(td)
+#: ./doc/common/tables/neutron-zeromq.xml39(td)
+#: ./doc/common/tables/ceilometer-rpc.xml67(td)
+#: ./doc/common/tables/trove-zeromq.xml39(td)
+msgid "(StrOpt) MatchMaker driver"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml19(th)
-msgid "[ml2_arista]"
+#: ./doc/common/tables/heat-zeromq.xml43(td)
+#: ./doc/common/tables/neutron-zeromq.xml43(td)
+#: ./doc/common/tables/ceilometer-rpc.xml71(td)
+#: ./doc/common/tables/trove-zeromq.xml43(td)
+msgid "(IntOpt) ZeroMQ receiver listening port"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml22(td)
-msgid "eapi_host ="
+#: ./doc/common/tables/heat-amqp.xml30(td)
+msgid "control_exchange = heat"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml23(td)
+#: ./doc/common/tables/heat-amqp.xml46(td)
 msgid ""
-"(StrOpt) Arista EOS IP address. This is required field.If not set, all "
-"communications to Arista EOSwill fail"
+"list_notifier_drivers = ['heat.openstack.common.notifier.no_op_notifier']"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml26(td)
-msgid "eapi_password ="
+#: ./doc/common/tables/heat-amqp.xml47(td)
+msgid "(MultiStrOpt) List of drivers to send notifications"
+msgstr "(複数文字列オプション) 通知を送信するドライバーの一覧"
+
+#: ./doc/common/tables/heat-amqp.xml55(td)
+#: ./doc/common/tables/ceilometer-amqp.xml35(td)
+msgid "(ListOpt) AMQP topic used for OpenStack notifications"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml27(td)
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml8(caption)
+msgid "Description of configuration options for linuxbridge_agent"
+msgstr ""
+
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml19(th)
+msgid "[LINUX_BRIDGE]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml22(td)
+#: ./doc/common/tables/neutron-mlnx.xml30(td)
+msgid "physical_interface_mappings ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml23(td)
+#: ./doc/common/tables/neutron-mlnx.xml31(td)
+msgid "(ListOpt) List of &lt;physical_network&gt;:&lt;physical_interface&gt;"
+msgstr ""
+
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml26(th)
+msgid "[VLANS]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml34(td)
+#: ./doc/common/tables/neutron-mlnx.xml54(td)
+msgid "(StrOpt) Network type for tenant networks (local, vlan, or none)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml37(th)
+msgid "[VXLAN]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml40(td)
+msgid "enable_vxlan = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml41(td)
 msgid ""
-"(StrOpt) Password for Arista EOS. This is required field.if not set, all "
-"communications to Arista EOSwill fail"
+"(BoolOpt) Enable VXLAN on the agent. Can be enabled when agent is managed by"
+" ml2 plugin using linuxbridge mechanism driver"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml30(td)
-msgid "eapi_username ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_arista.xml31(td)
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml45(td)
 msgid ""
-"(StrOpt) Username for Arista EOS. This is required field.if not set, all "
-"communications to Arista EOSwill fail"
+"(BoolOpt) Extension to use alongside ml2 plugin's l2population mechanism "
+"driver. It enables the plugin to populate VXLAN forwarding table."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml34(td)
-msgid "region_name = RegionOne"
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml49(td)
+msgid "(StrOpt) Local IP address of the VXLAN endpoints."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml35(td)
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml52(td)
+msgid "tos = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml53(td)
+msgid "(IntOpt) TOS for vxlan interface protocol packets."
+msgstr ""
+
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml56(td)
+msgid "ttl = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml57(td)
+msgid "(IntOpt) TTL for vxlan interface protocol packets."
+msgstr ""
+
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml60(td)
+msgid "vxlan_group = 224.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-linuxbridge_agent.xml61(td)
+msgid "(StrOpt) Multicast group for vxlan interface."
+msgstr ""
+
+#: ./doc/common/tables/nova-redis.xml23(td)
+#: ./doc/common/tables/glance-redis.xml27(td)
+#: ./doc/common/tables/cinder-rpc.xml83(td)
+#: ./doc/common/tables/keystone-redis.xml35(td)
+msgid "(StrOpt) Password for Redis server (optional)."
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml21(td)
+msgid "bind_port = 6001"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml36(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml36(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml36(td)
+msgid "devices = /srv/node"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml36(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml36(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml36(td)
+msgid "Parent directory of where devices are mounted"
+msgstr "デバイスがマウントされる場所の親ディレクトリー"
+
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml39(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml39(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml39(td)
+msgid "mount_check = true"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml39(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml39(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml39(td)
 msgid ""
-"(StrOpt) Defines Region Name that is assigned to this OpenStackController. "
-"This is useful when multipleOpenStack/Neutron controllers are managing the "
-"sameArista HW clusters. Note that this name must match withthe region name "
-"registered (or known) to keystoneservice. Authentication with Keysotne is "
-"performed byEOS. This is optional. If not set, a value of\"RegionOne\" is "
-"assumed"
+"Whether or not check if the devices are mounted to prevent accidentally "
+"writing to the root device"
+msgstr "不注意によりルートデバイスに書き込むことを防ぐために、デバイスがマウントされているかを確認するかどうか"
+
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml42(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml42(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml42(td)
+msgid "disable_fallocate = false"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml38(td)
-msgid "sync_interval = 180"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_arista.xml39(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml42(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml42(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml42(td)
 msgid ""
-"(IntOpt) Sync interval in seconds between Neutron plugin andEOS. This "
-"interval defines how often thesynchronization is performed. This is an "
-"optionalfield. If not set, a value of 180 seconds is assumed"
+"Disable \"fast fail\" fallocate checks if the underlying filesystem does not"
+" support it."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml42(td)
-msgid "use_fqdn = True"
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml58(td)
+msgid "allowed_sync_hosts = 127.0.0.1"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_arista.xml43(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml100(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml97(td)
+msgid "db_preallocation = off"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml100(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml97(td)
 msgid ""
-"(BoolOpt) Defines if hostnames are sent to Arista EOS as "
-"FQDNs(\"node1.domain.com\") or as short names (\"node1\").This is optional. "
-"If not set, a value of \"True\"is assumed."
+"If you don't mind the extra disk space usage in overhead, you can turn this "
+"on to preallocate disk space with SQLite databases to decrease "
+"fragmentation. underlying filesystem does not support it. to setup custom "
+"log handlers. bytes you'd like fallocate to reserve, whether there is space "
+"for the given file size or not. This is useful for systems that behave badly"
+" when they completely run out of space; you can make the services pretend "
+"they're out of space early. server. For most cases, this should be "
+"`egg:swift#account`. replication passes account can be reclaimed"
 msgstr ""
 
-#: ./doc/common/tables/glance-filesystem.xml8(caption)
-msgid "Description of configuration options for filesystem"
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml106(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml106(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml103(td)
+msgid "fallocate_reserve = 0"
 msgstr ""
 
-#: ./doc/common/tables/glance-filesystem.xml22(td)
-msgid "filesystem_store_datadir = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-filesystem.xml23(td)
+#: ./doc/common/tables/swift-container-server-DEFAULT.xml106(td)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml106(td)
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml103(td)
 msgid ""
-"(StrOpt) Directory to which the Filesystem backend store writes images."
+"You can set fallocate_reserve to the number of bytes you'd like fallocate to"
+" reserve, whether there is space for the given file size or not. This is "
+"useful for systems that behave badly when they completely run out of space; "
+"you can make the services pretend they're out of space early. server. For "
+"most cases, this should be `egg:swift#object`."
 msgstr ""
 
-#: ./doc/common/tables/glance-filesystem.xml26(td)
-msgid "filesystem_store_datadirs = None"
+#: ./doc/common/tables/nova-db.xml8(caption)
+#: ./doc/common/tables/glance-db.xml8(caption)
+#: ./doc/common/tables/neutron-db.xml8(caption)
+msgid "Description of configuration options for db"
 msgstr ""
 
-#: ./doc/common/tables/glance-filesystem.xml27(td)
+#: ./doc/common/tables/nova-db.xml22(td)
+msgid "db_driver = nova.db"
+msgstr ""
+
+#: ./doc/common/tables/nova-db.xml23(td)
+msgid "(StrOpt) The driver to use for database access"
+msgstr ""
+
+#: ./doc/common/tables/nova-db.xml26(th)
+#: ./doc/common/tables/ceilometer-cells.xml19(th)
+#: ./doc/common/tables/nova-upgrade_levels.xml19(th)
+#: ./doc/common/tables/nova-cells.xml19(th)
+#: ./doc/common/tables/nova-rpc_all.xml198(th)
+#: ./doc/common/tables/nova-scheduling.xml118(th)
+#: ./doc/common/tables/nova-quota.xml82(th)
+#: ./doc/common/tables/nova-rpc.xml62(th)
+msgid "[cells]"
+msgstr ""
+
+#: ./doc/common/tables/nova-db.xml29(td)
+msgid "db_check_interval = 60"
+msgstr ""
+
+#: ./doc/common/tables/nova-db.xml30(td)
 msgid ""
-"(MultiStrOpt) List of directories and its priorities to which the Filesystem"
-" backend store writes images."
+"(IntOpt) Interval, in seconds, for getting fresh cell information from the "
+"database."
 msgstr ""
 
-#: ./doc/common/tables/glance-filesystem.xml30(td)
-msgid "filesystem_store_metadata_file = None"
+#: ./doc/common/tables/nova-db.xml40(td)
+#: ./doc/common/tables/glance-db.xml26(td)
+#: ./doc/common/tables/keystone-database.xml26(td)
+msgid "connection = None"
 msgstr ""
 
-#: ./doc/common/tables/glance-filesystem.xml31(td)
+#: ./doc/common/tables/nova-db.xml52(td)
+#: ./doc/common/tables/glance-db.xml38(td)
+#: ./doc/common/tables/neutron-db.xml49(td)
+#: ./doc/common/tables/keystone-database.xml38(td)
+msgid "db_inc_retry_interval = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-db.xml53(td)
+#: ./doc/common/tables/glance-db.xml39(td)
+#: ./doc/common/tables/neutron-db.xml50(td)
+#: ./doc/common/tables/keystone-database.xml39(td)
 msgid ""
-"(StrOpt) The path to a file which contains the metadata to be returned with "
-"any location associated with this store. The file must contain a valid JSON "
-"dict."
+"(BoolOpt) Whether to increase interval between db connection retries, up to "
+"db_max_retry_interval"
 msgstr ""
 
-#: ./doc/common/tables/heat-redis.xml8(caption)
-#: ./doc/common/tables/trove-redis.xml8(caption)
-#: ./doc/common/tables/ceilometer-redis.xml8(caption)
-#: ./doc/common/tables/glance-redis.xml8(caption)
-#: ./doc/common/tables/neutron-redis.xml8(caption)
-#: ./doc/common/tables/keystone-redis.xml8(caption)
-#: ./doc/common/tables/nova-redis.xml8(caption)
-msgid "Description of configuration options for redis"
+#: ./doc/common/tables/nova-db.xml56(td)
+#: ./doc/common/tables/glance-db.xml42(td)
+#: ./doc/common/tables/neutron-db.xml53(td)
+#: ./doc/common/tables/keystone-database.xml42(td)
+msgid "db_max_retries = 20"
 msgstr ""
 
-#: ./doc/common/tables/heat-redis.xml22(td)
-#: ./doc/common/tables/nova-common.xml42(td)
-#: ./doc/common/tables/ceilometer-redis.xml22(td)
-#: ./doc/common/tables/cinder-common.xml58(td)
-#: ./doc/common/tables/neutron-redis.xml22(td)
-msgid "host = oslo"
-msgstr ""
-
-#: ./doc/common/tables/heat-redis.xml23(td)
+#: ./doc/common/tables/nova-db.xml57(td)
+#: ./doc/common/tables/glance-db.xml43(td)
+#: ./doc/common/tables/neutron-db.xml54(td)
+#: ./doc/common/tables/keystone-database.xml43(td)
 msgid ""
-"(StrOpt) Name of the engine node. This can be an opaque identifier. It is "
-"not necessarily a hostname, FQDN, or IP address."
+"(IntOpt) maximum db connection retries before error is raised. (setting -1 "
+"implies an infinite retry count)"
 msgstr ""
 
-#: ./doc/common/tables/heat-redis.xml26(th)
-#: ./doc/common/tables/trove-redis.xml19(th)
-#: ./doc/common/tables/ceilometer-redis.xml34(th)
-#: ./doc/common/tables/neutron-redis.xml26(th)
-msgid "[matchmaker_redis]"
+#: ./doc/common/tables/nova-db.xml60(td)
+#: ./doc/common/tables/glance-db.xml46(td)
+#: ./doc/common/tables/neutron-db.xml57(td)
+#: ./doc/common/tables/keystone-database.xml46(td)
+msgid "db_max_retry_interval = 10"
 msgstr ""
 
-#: ./doc/common/tables/heat-redis.xml29(td)
-#: ./doc/common/tables/trove-redis.xml22(td)
-#: ./doc/common/tables/ceilometer-redis.xml37(td)
-#: ./doc/common/tables/glance-redis.xml22(td)
-#: ./doc/common/tables/neutron-redis.xml29(td)
-#: ./doc/common/tables/keystone-redis.xml22(td)
-#: ./doc/common/tables/neutron-nec.xml38(td)
-msgid "host = 127.0.0.1"
-msgstr ""
-
-#: ./doc/common/tables/heat-redis.xml30(td)
-#: ./doc/common/tables/trove-redis.xml23(td)
-#: ./doc/common/tables/ceilometer-redis.xml38(td)
-#: ./doc/common/tables/neutron-redis.xml30(td)
-msgid "(StrOpt) Host to locate redis"
-msgstr ""
-
-#: ./doc/common/tables/heat-redis.xml33(td)
-#: ./doc/common/tables/trove-redis.xml26(td)
-#: ./doc/common/tables/keystone-ldap.xml90(td)
-#: ./doc/common/tables/ceilometer-redis.xml41(td)
-#: ./doc/common/tables/cinder-rpc.xml82(td)
-#: ./doc/common/tables/glance-redis.xml26(td)
-#: ./doc/common/tables/neutron-redis.xml33(td)
-#: ./doc/common/tables/keystone-redis.xml34(td)
-#: ./doc/common/tables/neutron-ml2_odl.xml22(td)
-#: ./doc/common/tables/neutron-ml2_ncs.xml22(td)
-#: ./doc/common/tables/nova-redis.xml22(td)
-msgid "password = None"
-msgstr "password = None"
-
-#: ./doc/common/tables/heat-redis.xml34(td)
-#: ./doc/common/tables/trove-redis.xml27(td)
-#: ./doc/common/tables/ceilometer-redis.xml42(td)
-#: ./doc/common/tables/neutron-redis.xml34(td)
-msgid "(StrOpt) Password for Redis server. (optional)"
-msgstr ""
-
-#: ./doc/common/tables/heat-redis.xml37(td)
-#: ./doc/common/tables/trove-redis.xml30(td)
-#: ./doc/common/tables/nova-common.xml74(td)
-#: ./doc/common/tables/ceilometer-redis.xml45(td)
-#: ./doc/common/tables/cinder-rpc.xml86(td)
-#: ./doc/common/tables/glance-redis.xml30(td)
-#: ./doc/common/tables/neutron-redis.xml37(td)
-#: ./doc/common/tables/keystone-redis.xml38(td)
-msgid "port = 6379"
-msgstr ""
-
-#: ./doc/common/tables/heat-redis.xml38(td)
-#: ./doc/common/tables/trove-redis.xml31(td)
-#: ./doc/common/tables/nova-common.xml75(td)
-#: ./doc/common/tables/ceilometer-redis.xml46(td)
-#: ./doc/common/tables/cinder-rpc.xml87(td)
-#: ./doc/common/tables/glance-redis.xml31(td)
-#: ./doc/common/tables/neutron-redis.xml38(td)
-#: ./doc/common/tables/keystone-redis.xml39(td)
-msgid "(IntOpt) Use this port to connect to redis host."
-msgstr ""
-
-#: ./doc/common/tables/trove-logging.xml8(caption)
-#: ./doc/common/tables/glance-logging.xml8(caption)
-#: ./doc/common/tables/ceilometer-logging.xml8(caption)
-#: ./doc/common/tables/neutron-logging.xml8(caption)
-#: ./doc/common/tables/heat-logging.xml8(caption)
-#: ./doc/common/tables/keystone-logging.xml8(caption)
-#: ./doc/common/tables/nova-logging.xml8(caption)
-msgid "Description of configuration options for logging"
-msgstr ""
-
-#: ./doc/common/tables/trove-logging.xml22(td)
-msgid "format_options = -m 5"
-msgstr ""
-
-#: ./doc/common/tables/trove-logging.xml23(td)
-#: ./doc/common/tables/trove-logging.xml71(td)
-#: ./doc/common/tables/trove-compute.xml23(td)
-#: ./doc/common/tables/trove-compute.xml27(td)
-#: ./doc/common/tables/trove-api.xml39(td)
-#: ./doc/common/tables/trove-api.xml83(td)
-#: ./doc/common/tables/trove-api.xml91(td)
-#: ./doc/common/tables/trove-api.xml95(td)
-#: ./doc/common/tables/trove-debug.xml55(td)
-#: ./doc/common/tables/trove-debug.xml59(td)
-#: ./doc/common/tables/trove-debug.xml63(td)
-#: ./doc/common/tables/trove-debug.xml67(td)
-#: ./doc/common/tables/trove-debug.xml71(td)
-#: ./doc/common/tables/trove-debug.xml75(td)
-#: ./doc/common/tables/trove-backup.xml39(td)
-#: ./doc/common/tables/trove-backup.xml55(td)
-#: ./doc/common/tables/trove-swift.xml23(td)
-#: ./doc/common/tables/trove-volume.xml23(td)
-#: ./doc/common/tables/trove-volume.xml27(td)
-#: ./doc/common/tables/trove-volume.xml31(td)
-#: ./doc/common/tables/trove-volume.xml43(td)
-#: ./doc/common/tables/trove-rpc.xml27(td)
-#: ./doc/common/tables/trove-common.xml71(td)
-#: ./doc/common/tables/trove-dns.xml23(td)
-#: ./doc/common/tables/trove-dns.xml27(td)
-#: ./doc/common/tables/trove-dns.xml31(td)
-#: ./doc/common/tables/trove-dns.xml35(td)
-#: ./doc/common/tables/trove-dns.xml39(td)
-#: ./doc/common/tables/trove-dns.xml43(td)
-#: ./doc/common/tables/trove-dns.xml47(td)
-#: ./doc/common/tables/trove-dns.xml51(td)
-#: ./doc/common/tables/trove-dns.xml55(td)
-#: ./doc/common/tables/trove-dns.xml59(td)
-#: ./doc/common/tables/trove-dns.xml63(td)
-#: ./doc/common/tables/trove-dns.xml67(td)
-#: ./doc/common/tables/trove-dns.xml79(td)
-#: ./doc/common/tables/trove-heat.xml27(td)
-#: ./doc/common/tables/trove-guestagent.xml39(td)
-#: ./doc/common/tables/trove-guestagent.xml51(td)
-#: ./doc/common/tables/trove-amqp.xml31(td)
-msgid "(StrOpt) No help text available for this option."
-msgstr ""
-
-#: ./doc/common/tables/trove-logging.xml26(td)
-#: ./doc/common/tables/glance-logging.xml34(td)
-#: ./doc/common/tables/cinder-images.xml62(td)
-#: ./doc/common/tables/ceilometer-logging.xml34(td)
-#: ./doc/common/tables/neutron-logging.xml34(td)
-#: ./doc/common/tables/heat-logging.xml26(td)
-#: ./doc/common/tables/keystone-logging.xml26(td)
-#: ./doc/common/tables/nova-logging.xml38(td)
-msgid "instance_format = \"[instance: %(uuid)s] \""
-msgstr ""
-
-#: ./doc/common/tables/trove-logging.xml27(td)
-#: ./doc/common/tables/glance-logging.xml35(td)
-#: ./doc/common/tables/cinder-images.xml63(td)
-#: ./doc/common/tables/ceilometer-logging.xml35(td)
-#: ./doc/common/tables/neutron-logging.xml35(td)
-#: ./doc/common/tables/heat-logging.xml27(td)
-#: ./doc/common/tables/keystone-logging.xml27(td)
-#: ./doc/common/tables/nova-logging.xml39(td)
+#: ./doc/common/tables/nova-db.xml61(td)
+#: ./doc/common/tables/glance-db.xml47(td)
+#: ./doc/common/tables/neutron-db.xml58(td)
+#: ./doc/common/tables/keystone-database.xml47(td)
 msgid ""
-"(StrOpt) If an instance is passed with the log message, format it like this"
+"(IntOpt) max seconds between db connection retries, if db_inc_retry_interval"
+" is enabled"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml30(td)
-#: ./doc/common/tables/glance-logging.xml38(td)
-#: ./doc/common/tables/cinder-images.xml66(td)
-#: ./doc/common/tables/ceilometer-logging.xml38(td)
-#: ./doc/common/tables/neutron-logging.xml38(td)
-#: ./doc/common/tables/heat-logging.xml30(td)
-#: ./doc/common/tables/keystone-logging.xml30(td)
-#: ./doc/common/tables/nova-logging.xml42(td)
-msgid "instance_uuid_format = \"[instance: %(uuid)s] \""
+#: ./doc/common/tables/nova-db.xml64(td)
+#: ./doc/common/tables/glance-db.xml50(td)
+#: ./doc/common/tables/neutron-db.xml61(td)
+#: ./doc/common/tables/keystone-database.xml50(td)
+msgid "db_retry_interval = 1"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml31(td)
-#: ./doc/common/tables/glance-logging.xml39(td)
-#: ./doc/common/tables/cinder-images.xml67(td)
-#: ./doc/common/tables/ceilometer-logging.xml39(td)
-#: ./doc/common/tables/neutron-logging.xml39(td)
-#: ./doc/common/tables/heat-logging.xml31(td)
-#: ./doc/common/tables/keystone-logging.xml31(td)
-#: ./doc/common/tables/nova-logging.xml43(td)
+#: ./doc/common/tables/nova-db.xml65(td)
+#: ./doc/common/tables/glance-db.xml51(td)
+#: ./doc/common/tables/neutron-db.xml62(td)
+#: ./doc/common/tables/keystone-database.xml51(td)
+msgid "(IntOpt) seconds between db connection retries"
+msgstr ""
+
+#: ./doc/common/tables/nova-db.xml88(td)
+msgid "mysql_sql_mode = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-db.xml89(td)
 msgid ""
-"(StrOpt) If an instance UUID is passed with the log message, format it like "
-"this"
+"(StrOpt) The SQL mode to be used for MySQL sessions (default is empty, "
+"meaning do not override any server-side SQL mode setting)"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml34(td)
-#: ./doc/common/tables/glance-logging.xml42(td)
-#: ./doc/common/tables/ceilometer-logging.xml42(td)
-#: ./doc/common/tables/neutron-logging.xml42(td)
-#: ./doc/common/tables/heat-logging.xml34(td)
-#: ./doc/common/tables/keystone-logging.xml34(td)
-#: ./doc/common/tables/nova-logging.xml46(td)
-#: ./doc/common/tables/cinder-common.xml74(td)
-msgid "log_config_append = None"
+#: ./doc/common/tables/nova-db.xml100(td)
+msgid "slave_connection = None"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml35(td)
-#: ./doc/common/tables/glance-logging.xml43(td)
-#: ./doc/common/tables/ceilometer-logging.xml43(td)
-#: ./doc/common/tables/neutron-logging.xml43(td)
-#: ./doc/common/tables/heat-logging.xml35(td)
-#: ./doc/common/tables/keystone-logging.xml35(td)
-#: ./doc/common/tables/nova-logging.xml47(td)
-#: ./doc/common/tables/cinder-common.xml75(td)
+#: ./doc/common/tables/nova-db.xml104(td)
+msgid "sqlite_db = nova.sqlite"
+msgstr ""
+
+#: ./doc/common/tables/nova-db.xml112(td)
+#: ./doc/common/tables/glance-db.xml94(td)
+#: ./doc/common/tables/neutron-db.xml97(td)
+#: ./doc/common/tables/keystone-database.xml94(td)
+msgid "use_db_reconnect = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-db.xml113(td)
+#: ./doc/common/tables/glance-db.xml95(td)
+#: ./doc/common/tables/neutron-db.xml98(td)
+#: ./doc/common/tables/keystone-database.xml95(td)
 msgid ""
-"(StrOpt) The name of logging configuration file. It does not disable "
-"existing loggers, but just appends specified logging configuration to any "
-"other existing logging options. Please see the Python logging module "
-"documentation for details on logging configuration files."
+"(BoolOpt) Enable the experimental use of database reconnect on connection "
+"lost"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml38(td)
-#: ./doc/common/tables/glance-logging.xml46(td)
-#: ./doc/common/tables/ceilometer-logging.xml46(td)
-#: ./doc/common/tables/neutron-logging.xml46(td)
-#: ./doc/common/tables/heat-logging.xml38(td)
-#: ./doc/common/tables/keystone-logging.xml38(td)
-#: ./doc/common/tables/nova-logging.xml50(td)
-#: ./doc/common/tables/cinder-common.xml78(td)
-msgid "log_date_format = %Y-%m-%d %H:%M:%S"
-msgstr ""
-
-#: ./doc/common/tables/trove-logging.xml39(td)
-#: ./doc/common/tables/glance-logging.xml47(td)
-#: ./doc/common/tables/ceilometer-logging.xml47(td)
-#: ./doc/common/tables/neutron-logging.xml47(td)
-#: ./doc/common/tables/heat-logging.xml39(td)
-#: ./doc/common/tables/keystone-logging.xml39(td)
-#: ./doc/common/tables/nova-logging.xml51(td)
-#: ./doc/common/tables/cinder-common.xml79(td)
+#: ./doc/common/tables/glance-rabbitmq.xml23(td)
+#: ./doc/common/tables/keystone-amqp.xml31(td)
+#: ./doc/common/tables/cinder-rpc.xml35(td)
+#: ./doc/common/tables/nova-rpc_all.xml31(td)
+#: ./doc/common/tables/nova-rpc.xml31(td)
 msgid ""
-"(StrOpt) Format string for %%(asctime)s in log records. Default: %(default)s"
+"(StrOpt) The default exchange under which topics are scoped. May be "
+"overridden by an exchange name specified in the transport_url option."
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml42(td)
-#: ./doc/common/tables/glance-logging.xml50(td)
-#: ./doc/common/tables/ceilometer-logging.xml50(td)
-#: ./doc/common/tables/neutron-logging.xml50(td)
-#: ./doc/common/tables/heat-logging.xml42(td)
-#: ./doc/common/tables/keystone-logging.xml42(td)
-#: ./doc/common/tables/nova-logging.xml54(td)
-#: ./doc/common/tables/cinder-common.xml82(td)
-msgid "log_dir = None"
+#: ./doc/common/tables/neutron-l3_agent.xml8(caption)
+msgid "Description of configuration options for l3_agent"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml43(td)
-#: ./doc/common/tables/glance-logging.xml51(td)
-#: ./doc/common/tables/ceilometer-logging.xml51(td)
-#: ./doc/common/tables/neutron-logging.xml51(td)
-#: ./doc/common/tables/heat-logging.xml43(td)
-#: ./doc/common/tables/keystone-logging.xml43(td)
-#: ./doc/common/tables/nova-logging.xml55(td)
-#: ./doc/common/tables/cinder-common.xml83(td)
+#: ./doc/common/tables/neutron-l3_agent.xml22(td)
+msgid "enable_metadata_proxy = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-l3_agent.xml23(td)
+msgid "(BoolOpt) Allow running metadata proxy."
+msgstr ""
+
+#: ./doc/common/tables/neutron-l3_agent.xml26(td)
+msgid "external_network_bridge = br-ex"
+msgstr ""
+
+#: ./doc/common/tables/neutron-l3_agent.xml27(td)
+msgid "(StrOpt) Name of bridge used for external network traffic."
+msgstr ""
+
+#: ./doc/common/tables/neutron-l3_agent.xml30(td)
+msgid "gateway_external_network_id ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-l3_agent.xml31(td)
 msgid ""
-"(StrOpt) (Optional) The base directory used for relative --log-file paths"
+"(StrOpt) UUID of external network for routers implemented by the agents."
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml46(td)
-#: ./doc/common/tables/glance-logging.xml54(td)
-#: ./doc/common/tables/ceilometer-logging.xml54(td)
-#: ./doc/common/tables/neutron-logging.xml54(td)
-#: ./doc/common/tables/heat-logging.xml46(td)
-#: ./doc/common/tables/keystone-logging.xml46(td)
-#: ./doc/common/tables/nova-logging.xml58(td)
-#: ./doc/common/tables/cinder-common.xml86(td)
-msgid "log_file = None"
+#: ./doc/common/tables/neutron-l3_agent.xml34(td)
+msgid "handle_internal_only_routers = True"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml47(td)
-#: ./doc/common/tables/glance-logging.xml55(td)
-#: ./doc/common/tables/ceilometer-logging.xml55(td)
-#: ./doc/common/tables/neutron-logging.xml55(td)
-#: ./doc/common/tables/heat-logging.xml47(td)
-#: ./doc/common/tables/keystone-logging.xml47(td)
-#: ./doc/common/tables/nova-logging.xml59(td)
-#: ./doc/common/tables/cinder-common.xml87(td)
+#: ./doc/common/tables/neutron-l3_agent.xml35(td)
+msgid "(BoolOpt) Agent should implement routers with no gateway"
+msgstr ""
+
+#: ./doc/common/tables/neutron-l3_agent.xml38(td)
+msgid "router_id ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-l3_agent.xml39(td)
 msgid ""
-"(StrOpt) (Optional) Name of log file to output to. If no default is set, "
-"logging will go to stdout."
+"(StrOpt) If namespaces is disabled, the l3 agent can only configure a router"
+" that has the matching router ID."
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml50(td)
-#: ./doc/common/tables/glance-logging.xml58(td)
-#: ./doc/common/tables/ceilometer-logging.xml58(td)
-#: ./doc/common/tables/neutron-logging.xml58(td)
-#: ./doc/common/tables/heat-logging.xml50(td)
-#: ./doc/common/tables/keystone-logging.xml50(td)
-#: ./doc/common/tables/nova-logging.xml62(td)
-#: ./doc/common/tables/cinder-common.xml90(td)
-msgid "log_format = None"
+#: ./doc/common/tables/neutron-l3_agent.xml42(td)
+msgid "send_arp_for_ha = 0"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml51(td)
-#: ./doc/common/tables/glance-logging.xml59(td)
-#: ./doc/common/tables/ceilometer-logging.xml59(td)
-#: ./doc/common/tables/neutron-logging.xml59(td)
-#: ./doc/common/tables/heat-logging.xml51(td)
-#: ./doc/common/tables/keystone-logging.xml51(td)
-#: ./doc/common/tables/nova-logging.xml63(td)
-#: ./doc/common/tables/cinder-common.xml91(td)
+#: ./doc/common/tables/neutron-l3_agent.xml43(td)
 msgid ""
-"(StrOpt) DEPRECATED. A logging.Formatter log message format string which may"
-" use any of the available logging.LogRecord attributes. This option is "
-"deprecated. Please use logging_context_format_string and "
-"logging_default_format_string instead."
+"(IntOpt) Send this many gratuitous ARPs for HA setup, if less than or equal "
+"to 0, the feature is disabled"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml54(td)
-#: ./doc/common/tables/glance-logging.xml62(td)
-#: ./doc/common/tables/ceilometer-logging.xml62(td)
-#: ./doc/common/tables/neutron-logging.xml62(td)
-#: ./doc/common/tables/heat-logging.xml54(td)
-#: ./doc/common/tables/keystone-logging.xml54(td)
-#: ./doc/common/tables/cinder-common.xml94(td)
-msgid ""
-"logging_context_format_string = %(asctime)s.%(msecs)03d %(process)d "
-"%(levelname)s %(name)s [%(request_id)s %(user_identity)s] "
-"%(instance)s%(message)s"
+#: ./doc/common/tables/swift-container-server-pipeline-main.xml18(td)
+msgid "pipeline = healthcheck recon container-server"
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml55(td)
-#: ./doc/common/tables/neutron-logging.xml63(td)
-#: ./doc/common/tables/heat-logging.xml55(td)
-#: ./doc/common/tables/nova-logging.xml67(td)
-msgid "(StrOpt) format string to use for log messages with context"
+#: ./doc/common/tables/glance-policy.xml23(td)
+msgid "(StrOpt) The default policy to use."
 msgstr ""
 
-#: ./doc/common/tables/trove-logging.xml58(td)
-#: ./doc/common/tables/glance-logging.xml66(td)
-#: ./doc/common/tables/ceilometer-logging.xml66(td)
-#: ./doc/common/tables/neutron-logging.xml66(td)
-#: ./doc/common/tables/heat-logging.xml58(td)
-#: ./doc/common/tables/keystone-logging.xml58(td)
-#: ./doc/common/tables/nova-logging.xml70(td)
-#: ./doc/common/tables/cinder-common.xml98(td)
-msgid "logging_debug_format_suffix = %(funcName)s %(pathname)s:%(lineno)d"
-msgstr ""
-
-#: ./doc/common/tables/trove-logging.xml59(td)
-#: ./doc/common/tables/neutron-logging.xml67(td)
-#: ./doc/common/tables/heat-logging.xml59(td)
-#: ./doc/common/tables/nova-logging.xml71(td)
-msgid "(StrOpt) data to append to log format when level is DEBUG"
-msgstr ""
-
-#: ./doc/common/tables/trove-logging.xml62(td)
-#: ./doc/common/tables/glance-logging.xml70(td)
-#: ./doc/common/tables/ceilometer-logging.xml70(td)
-#: ./doc/common/tables/neutron-logging.xml70(td)
-#: ./doc/common/tables/heat-logging.xml62(td)
-#: ./doc/common/tables/keystone-logging.xml62(td)
-#: ./doc/common/tables/nova-logging.xml74(td)
-#: ./doc/common/tables/cinder-common.xml102(td)
-msgid ""
-"logging_default_format_string = %(asctime)s.%(msecs)03d %(process)d "
-"%(levelname)s %(name)s [-] %(instance)s%(message)s"
-msgstr ""
-
-#: ./doc/common/tables/trove-logging.xml63(td)
-#: ./doc/common/tables/neutron-logging.xml71(td)
-#: ./doc/common/tables/heat-logging.xml63(td)
-#: ./doc/common/tables/nova-logging.xml75(td)
-msgid "(StrOpt) format string to use for log messages without context"
-msgstr ""
-
-#: ./doc/common/tables/trove-logging.xml66(td)
-#: ./doc/common/tables/glance-logging.xml74(td)
-#: ./doc/common/tables/ceilometer-logging.xml74(td)
-#: ./doc/common/tables/neutron-logging.xml74(td)
-#: ./doc/common/tables/heat-logging.xml66(td)
-#: ./doc/common/tables/keystone-logging.xml66(td)
-#: ./doc/common/tables/nova-logging.xml78(td)
-#: ./doc/common/tables/cinder-common.xml106(td)
-msgid ""
-"logging_exception_prefix = %(asctime)s.%(msecs)03d %(process)d TRACE "
-"%(name)s %(instance)s"
-msgstr ""
-
-#: ./doc/common/tables/trove-logging.xml67(td)
-#: ./doc/common/tables/neutron-logging.xml75(td)
-#: ./doc/common/tables/heat-logging.xml67(td)
-#: ./doc/common/tables/nova-logging.xml79(td)
-msgid "(StrOpt) prefix each line of exception output with this format"
-msgstr ""
-
-#: ./doc/common/tables/trove-logging.xml70(td)
-msgid "network_label_regex = ^private$"
-msgstr ""
-
-#: ./doc/common/tables/trove-logging.xml75(td)
-#: ./doc/common/tables/heat-notification.xml27(td)
-#: ./doc/common/tables/neutron-logging.xml79(td)
-#: ./doc/common/tables/nova-logging.xml83(td)
-msgid "(BoolOpt) publish error events"
-msgstr ""
-
-#: ./doc/common/tables/trove-logging.xml78(td)
-#: ./doc/common/tables/glance-logging.xml82(td)
-#: ./doc/common/tables/ceilometer-logging.xml82(td)
-#: ./doc/common/tables/neutron-logging.xml82(td)
-#: ./doc/common/tables/heat-logging.xml70(td)
-#: ./doc/common/tables/keystone-logging.xml70(td)
-#: ./doc/common/tables/nova-logging.xml86(td)
-#: ./doc/common/tables/cinder-common.xml194(td)
-msgid "syslog_log_facility = LOG_USER"
-msgstr ""
-
-#: ./doc/common/tables/trove-logging.xml79(td)
-#: ./doc/common/tables/neutron-logging.xml83(td)
-#: ./doc/common/tables/heat-logging.xml71(td)
-#: ./doc/common/tables/nova-logging.xml87(td)
-msgid "(StrOpt) syslog facility to receive log lines"
-msgstr ""
-
-#: ./doc/common/tables/trove-logging.xml82(td)
-#: ./doc/common/tables/glance-logging.xml86(td)
-#: ./doc/common/tables/ceilometer-logging.xml86(td)
-#: ./doc/common/tables/neutron-logging.xml90(td)
-#: ./doc/common/tables/heat-logging.xml74(td)
-#: ./doc/common/tables/keystone-logging.xml74(td)
-#: ./doc/common/tables/nova-logging.xml90(td)
-#: ./doc/common/tables/cinder-common.xml210(td)
-msgid "use_stderr = True"
-msgstr ""
-
-#: ./doc/common/tables/trove-logging.xml83(td)
-#: ./doc/common/tables/glance-logging.xml87(td)
-#: ./doc/common/tables/ceilometer-logging.xml87(td)
-#: ./doc/common/tables/neutron-logging.xml91(td)
-#: ./doc/common/tables/heat-logging.xml75(td)
-#: ./doc/common/tables/keystone-logging.xml75(td)
-#: ./doc/common/tables/nova-logging.xml91(td)
-#: ./doc/common/tables/cinder-common.xml211(td)
-msgid "(BoolOpt) Log output to standard error"
-msgstr ""
-
-#: ./doc/common/tables/trove-logging.xml86(td)
-#: ./doc/common/tables/glance-logging.xml90(td)
-#: ./doc/common/tables/ceilometer-logging.xml90(td)
-#: ./doc/common/tables/cinder-rootwrap.xml30(td)
-#: ./doc/common/tables/neutron-logging.xml94(td)
-#: ./doc/common/tables/heat-logging.xml78(td)
-#: ./doc/common/tables/keystone-logging.xml78(td)
-#: ./doc/common/tables/nova-logging.xml94(td)
-#: ./doc/common/tables/cinder-common.xml214(td)
-#: ./doc/common/tables/neutron-rootwrap.xml30(td)
-#: ./doc/common/tables/nova-rootwrap.xml30(td)
-msgid "use_syslog = False"
-msgstr ""
-
-#: ./doc/common/tables/trove-logging.xml87(td)
-#: ./doc/common/tables/neutron-logging.xml95(td)
-#: ./doc/common/tables/heat-logging.xml79(td)
-msgid "(BoolOpt) Use syslog for logging."
-msgstr "(論理値オプション) ロギングのために syslog の利用。"
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml7(literal)
-msgid "[container-updater]"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml18(td)
-msgid "log_name = container-updater"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml30(td)
-#: ./doc/common/tables/swift-container-server-container-sync.xml33(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml30(td)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml18(td)
-msgid "interval = 300"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml30(td)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml42(td)
-#: ./doc/common/tables/swift-container-server-container-sync.xml33(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml30(td)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml30(td)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml30(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml42(td)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml18(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml33(td)
-msgid "Minimum time for a pass to take"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml33(td)
-msgid "concurrency = 4"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml33(td)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml39(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml33(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml39(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml54(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml39(td)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml30(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml30(td)
-msgid "Number of replication workers to spawn"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml36(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml36(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml112(td)
-msgid "node_timeout = 3"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml36(td)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml45(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml36(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml48(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml36(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml112(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml57(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml51(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml36(td)
-msgid "Request timeout to external services"
-msgstr "外部サービスへのリクエストのタイムアウト"
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml39(td)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml48(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml54(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml39(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml109(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml54(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml39(td)
-msgid "conn_timeout = 0.5"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml39(td)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml48(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml54(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml39(td)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml109(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml54(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml39(td)
-msgid "Connection timeout to external services"
-msgstr "外部サービスへの接続のタイムアウト"
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml42(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml39(td)
-msgid "slowdown = 0.01"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml42(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml39(td)
-msgid "Time in seconds to wait between objects"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml45(td)
-msgid "account_suppression_time = 60"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml45(td)
-msgid ""
-"Seconds to suppress updating an account that has generated an error "
-"(timeout, not yet found, etc.)"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml49(td)
-#: ./doc/common/tables/swift-account-server-filter-recon.xml21(td)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml57(td)
-#: ./doc/common/tables/swift-object-server-object-auditor.xml42(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml42(td)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml42(td)
-#: ./doc/common/tables/swift-object-server-filter-recon.xml21(td)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml36(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml72(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml63(td)
-#: ./doc/common/tables/swift-container-server-filter-recon.xml21(td)
-msgid "recon_cache_path = /var/cache/swift"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-updater.xml49(td)
-#: ./doc/common/tables/swift-account-server-filter-recon.xml21(td)
-#: ./doc/common/tables/swift-container-server-container-replicator.xml57(td)
-#: ./doc/common/tables/swift-object-server-object-auditor.xml42(td)
-#: ./doc/common/tables/swift-object-server-object-updater.xml42(td)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml42(td)
-#: ./doc/common/tables/swift-object-server-filter-recon.xml21(td)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml36(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml72(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml63(td)
-#: ./doc/common/tables/swift-container-server-filter-recon.xml21(td)
-msgid "Directory where stats for a few items will be stored"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml8(caption)
-msgid "Description of configuration options for storage_gpfs"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml22(td)
-msgid "gpfs_images_dir = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml23(td)
-msgid ""
-"(StrOpt) Specifies the path of the Image service repository in GPFS. Leave "
-"undefined if not storing images in GPFS."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml26(td)
-msgid "gpfs_images_share_mode = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml27(td)
-msgid ""
-"(StrOpt) Specifies the type of image copy to be used. Set this when the "
-"Image service repository also uses GPFS so that image files can be "
-"transferred efficiently from the Image service to the Block Storage service."
-" There are two valid values: \"copy\" specifies that a full copy of the "
-"image is made; \"copy_on_write\" specifies that copy-on-write optimization "
-"strategy is used and unmodified blocks of the image file are shared "
-"efficiently."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml30(td)
-msgid "gpfs_max_clone_depth = 0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml31(td)
-msgid ""
-"(IntOpt) Specifies an upper limit on the number of indirections required to "
-"reach a specific block due to snapshots or clones. A lengthy chain of copy-"
-"on-write snapshots or clones can have a negative impact on performance, but "
-"improves space utilization. 0 indicates unlimited clone depth."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml34(td)
-msgid "gpfs_mount_point_base = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml35(td)
-msgid ""
-"(StrOpt) Specifies the path of the GPFS directory where Block Storage volume"
-" and snapshot files are stored."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml38(td)
-msgid "gpfs_sparse_volumes = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml39(td)
-msgid ""
-"(BoolOpt) Specifies that volumes are created as sparse files which initially"
-" consume no space. If set to False, the volume is created as a fully "
-"allocated file, in which case, creation may take a significantly longer "
-"time."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml42(td)
-msgid "gpfs_storage_pool = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_gpfs.xml43(td)
-msgid ""
-"(StrOpt) Specifies the storage pool that volumes are assigned to. By "
-"default, the system storage pool is used."
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml8(caption)
-msgid "Description of configuration options for nexenta_iscsi"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml22(td)
-msgid "nexenta_blocksize ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml23(td)
-msgid "(StrOpt) block size for volumes (blank=default,8KB)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml26(td)
-msgid "nexenta_host ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml27(td)
-msgid "(StrOpt) IP address of Nexenta SA"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml30(td)
-msgid "nexenta_iscsi_target_portal_port = 3260"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml31(td)
-msgid "(IntOpt) Nexenta target portal port"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml34(td)
-msgid "nexenta_password = nexenta"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml35(td)
-msgid "(StrOpt) Password to connect to Nexenta SA"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml38(td)
-msgid "nexenta_rest_port = 2000"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml39(td)
-msgid "(IntOpt) HTTP port to connect to Nexenta REST API server"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml42(td)
-msgid "nexenta_rest_protocol = auto"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml43(td)
-msgid "(StrOpt) Use http or https for REST connection (default auto)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml46(td)
-msgid "nexenta_rrmgr_compression = 0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml47(td)
-msgid ""
-"(IntOpt) Enable stream compression, level 1..9. 1 - gives best speed; 9 - "
-"gives best compression."
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml50(td)
-msgid "nexenta_rrmgr_connections = 2"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml51(td)
-msgid "(IntOpt) Number of TCP connections."
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml54(td)
-msgid "nexenta_rrmgr_tcp_buf_size = 4096"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml55(td)
-msgid "(IntOpt) TCP Buffer size in KiloBytes."
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml58(td)
-msgid "nexenta_sparse = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml59(td)
-msgid "(BoolOpt) flag to create sparse volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml62(td)
-msgid "nexenta_sparsed_volumes = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml63(td)
-#: ./doc/common/tables/cinder-storage_nfs.xml39(td)
-#: ./doc/common/tables/cinder-storage_glusterfs.xml35(td)
-msgid ""
-"(BoolOpt) Create volumes as sparsed files which take no space.If set to "
-"False volume is created as regular file.In such case volume creation takes a"
-" lot of time."
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml66(td)
-msgid "nexenta_target_group_prefix = cinder/"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml67(td)
-msgid "(StrOpt) prefix for iSCSI target groups on SA"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml70(td)
-msgid "nexenta_target_prefix = iqn.1986-03.com.sun:02:cinder-"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml71(td)
-msgid "(StrOpt) IQN prefix for iSCSI targets"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml74(td)
-msgid "nexenta_user = admin"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml75(td)
-msgid "(StrOpt) User name to connect to Nexenta SA"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml78(td)
-msgid "nexenta_volume = cinder"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nexenta_iscsi.xml79(td)
-msgid "(StrOpt) pool on SA that will hold all volumes"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml8(caption)
-msgid "Description of configuration options for tilera"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml22(td)
-msgid "tile_pdu_ip = 10.0.100.1"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml23(td)
-msgid "(StrOpt) IP address of tilera pdu"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml26(td)
-msgid "tile_pdu_mgr = /tftpboot/pdu_mgr"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml27(td)
-msgid "(StrOpt) Management script for tilera pdu"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml30(td)
-msgid "tile_pdu_off = 2"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml31(td)
-msgid "(IntOpt) Power status of tilera PDU is OFF"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml34(td)
-msgid "tile_pdu_on = 1"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml35(td)
-msgid "(IntOpt) Power status of tilera PDU is ON"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml38(td)
-msgid "tile_pdu_status = 9"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml39(td)
-msgid "(IntOpt) Power status of tilera PDU"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml42(td)
-msgid "tile_power_wait = 9"
-msgstr ""
-
-#: ./doc/common/tables/nova-tilera.xml43(td)
-msgid ""
-"(IntOpt) Wait time in seconds until check the result after tilera power "
-"operations"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml8(caption)
-msgid "Description of configuration options for ca"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml22(td)
-msgid "ca_file = cacert.pem"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml23(td)
-msgid "(StrOpt) Filename of root CA"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml26(td)
-msgid "ca_path = $state_path/CA"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml27(td)
-msgid "(StrOpt) Where we keep our root CA"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml30(td)
-msgid "cert_manager = nova.cert.manager.CertManager"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml31(td)
-msgid "(StrOpt) Full class name for the Manager for cert"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml34(td)
-msgid "cert_topic = cert"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml35(td)
-msgid "(StrOpt) The topic cert nodes listen on"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml38(td)
-msgid "crl_file = crl.pem"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml39(td)
-msgid "(StrOpt) Filename of root Certificate Revocation List"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml42(td)
-msgid "key_file = private/cakey.pem"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml43(td)
-msgid "(StrOpt) Filename of private key"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml46(td)
-msgid "keys_path = $state_path/keys"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml47(td)
-msgid "(StrOpt) Where we keep our keys"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml50(td)
-msgid ""
-"project_cert_subject = /C=US/ST=California/O=OpenStack/OU=NovaDev/CN"
-"=project-ca-%.16s-%s"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml51(td)
-msgid ""
-"(StrOpt) Subject for certificate for projects, %s for project, timestamp"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml54(td)
-msgid "use_project_ca = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml55(td)
-msgid "(BoolOpt) Should we use a CA for each project?"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml58(td)
-msgid ""
-"user_cert_subject = "
-"/C=US/ST=California/O=OpenStack/OU=NovaDev/CN=%.16s-%.16s-%s"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml59(td)
-msgid ""
-"(StrOpt) Subject for certificate for users, %s for project, user, timestamp"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml62(th)
-#: ./doc/common/tables/heat-cfn_api.xml61(th)
-#: ./doc/common/tables/heat-cloudwatch_api.xml57(th)
-#: ./doc/common/tables/cinder-ssl.xml19(th)
-#: ./doc/common/tables/heat-api.xml142(th)
-#: ./doc/common/tables/neutron-ssl.xml34(th)
-#: ./doc/common/tables/trove-ssl.xml19(th)
-#: ./doc/common/tables/keystone-ssl.xml54(th)
-#: ./doc/common/tables/ceilometer-ssl.xml19(th)
-msgid "[ssl]"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml65(td)
-#: ./doc/common/tables/heat-clients_nova.xml22(td)
-#: ./doc/common/tables/heat-cfn_api.xml64(td)
-#: ./doc/common/tables/heat-clients.xml29(td)
-#: ./doc/common/tables/heat-clients_heat.xml22(td)
-#: ./doc/common/tables/heat-clients_swift.xml22(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml60(td)
-#: ./doc/common/tables/heat-clients_ceilometer.xml22(td)
-#: ./doc/common/tables/heat-clients_trove.xml22(td)
-#: ./doc/common/tables/heat-clients_cinder.xml22(td)
-#: ./doc/common/tables/cinder-ssl.xml22(td)
-#: ./doc/common/tables/heat-api.xml145(td)
-#: ./doc/common/tables/neutron-ssl.xml37(td)
-#: ./doc/common/tables/heat-clients_neutron.xml22(td)
-#: ./doc/common/tables/trove-ssl.xml22(td)
-#: ./doc/common/tables/glance-ssl.xml22(td)
-#: ./doc/common/tables/heat-clients_keystone.xml22(td)
-#: ./doc/common/tables/ceilometer-ssl.xml22(td)
-msgid "ca_file = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml66(td)
-#: ./doc/common/tables/glance-ssl.xml23(td)
-msgid "(StrOpt) CA certificate file to use to verify connecting clients."
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml69(td)
-#: ./doc/common/tables/heat-clients_nova.xml26(td)
-#: ./doc/common/tables/heat-cfn_api.xml45(td)
-#: ./doc/common/tables/heat-cfn_api.xml68(td)
-#: ./doc/common/tables/heat-clients.xml33(td)
-#: ./doc/common/tables/heat-clients_heat.xml26(td)
-#: ./doc/common/tables/heat-clients_swift.xml26(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml41(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml64(td)
-#: ./doc/common/tables/heat-clients_ceilometer.xml26(td)
-#: ./doc/common/tables/heat-clients_trove.xml26(td)
-#: ./doc/common/tables/heat-clients_cinder.xml26(td)
-#: ./doc/common/tables/cinder-ssl.xml26(td)
-#: ./doc/common/tables/heat-api.xml115(td)
-#: ./doc/common/tables/heat-api.xml149(td)
-#: ./doc/common/tables/neutron-ssl.xml41(td)
-#: ./doc/common/tables/heat-clients_neutron.xml26(td)
-#: ./doc/common/tables/trove-ssl.xml26(td)
-#: ./doc/common/tables/glance-ssl.xml26(td)
-#: ./doc/common/tables/heat-clients_keystone.xml26(td)
-#: ./doc/common/tables/neutron-nec.xml26(td)
-#: ./doc/common/tables/ceilometer-ssl.xml26(td)
-msgid "cert_file = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml70(td)
-msgid "(StrOpt) Certificate file to use when starting the server securely."
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml73(td)
-#: ./doc/common/tables/heat-clients_nova.xml38(td)
-#: ./doc/common/tables/heat-cfn_api.xml49(td)
-#: ./doc/common/tables/heat-cfn_api.xml72(td)
-#: ./doc/common/tables/heat-clients.xml45(td)
-#: ./doc/common/tables/heat-clients_heat.xml38(td)
-#: ./doc/common/tables/heat-clients_swift.xml38(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml45(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml68(td)
-#: ./doc/common/tables/heat-clients_ceilometer.xml38(td)
-#: ./doc/common/tables/heat-clients_trove.xml38(td)
-#: ./doc/common/tables/heat-clients_cinder.xml38(td)
-#: ./doc/common/tables/cinder-ssl.xml30(td)
-#: ./doc/common/tables/heat-api.xml119(td)
-#: ./doc/common/tables/heat-api.xml153(td)
-#: ./doc/common/tables/neutron-ssl.xml45(td)
-#: ./doc/common/tables/heat-clients_neutron.xml38(td)
-#: ./doc/common/tables/trove-ssl.xml30(td)
-#: ./doc/common/tables/glance-ssl.xml30(td)
-#: ./doc/common/tables/heat-clients_keystone.xml38(td)
-#: ./doc/common/tables/neutron-nec.xml46(td)
-#: ./doc/common/tables/ceilometer-ssl.xml30(td)
-msgid "key_file = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-ca.xml74(td)
-msgid "(StrOpt) Private key file to use when starting the server securely."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_nova.xml8(caption)
-msgid "Description of configuration options for clients_nova"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_nova.xml19(th)
-msgid "[clients_nova]"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_nova.xml23(td)
-#: ./doc/common/tables/heat-clients.xml30(td)
-#: ./doc/common/tables/heat-clients_heat.xml23(td)
-#: ./doc/common/tables/heat-clients_swift.xml23(td)
-#: ./doc/common/tables/heat-clients_ceilometer.xml23(td)
-#: ./doc/common/tables/heat-clients_trove.xml23(td)
-#: ./doc/common/tables/heat-clients_cinder.xml23(td)
-#: ./doc/common/tables/heat-clients_neutron.xml23(td)
-#: ./doc/common/tables/heat-clients_keystone.xml23(td)
-msgid "(StrOpt) Optional CA cert file to use in SSL connections."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_nova.xml27(td)
-#: ./doc/common/tables/heat-clients.xml34(td)
-#: ./doc/common/tables/heat-clients_heat.xml27(td)
-#: ./doc/common/tables/heat-clients_swift.xml27(td)
-#: ./doc/common/tables/heat-clients_ceilometer.xml27(td)
-#: ./doc/common/tables/heat-clients_trove.xml27(td)
-#: ./doc/common/tables/heat-clients_cinder.xml27(td)
-#: ./doc/common/tables/heat-clients_neutron.xml27(td)
-#: ./doc/common/tables/heat-clients_keystone.xml27(td)
-msgid "(StrOpt) Optional PEM-formatted certificate chain file."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_nova.xml30(td)
-#: ./doc/common/tables/heat-clients.xml37(td)
-#: ./doc/common/tables/heat-clients_heat.xml30(td)
-#: ./doc/common/tables/heat-clients_swift.xml30(td)
-#: ./doc/common/tables/heat-clients_ceilometer.xml30(td)
-#: ./doc/common/tables/heat-clients_trove.xml30(td)
-#: ./doc/common/tables/heat-clients_cinder.xml30(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml39(td)
-#: ./doc/common/tables/heat-clients_neutron.xml30(td)
-#: ./doc/common/tables/heat-clients_keystone.xml30(td)
-msgid "endpoint_type = publicURL"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_nova.xml31(td)
-#: ./doc/common/tables/heat-clients.xml38(td)
-#: ./doc/common/tables/heat-clients_heat.xml31(td)
-#: ./doc/common/tables/heat-clients_swift.xml31(td)
-#: ./doc/common/tables/heat-clients_ceilometer.xml31(td)
-#: ./doc/common/tables/heat-clients_trove.xml31(td)
-#: ./doc/common/tables/heat-clients_cinder.xml31(td)
-#: ./doc/common/tables/heat-clients_neutron.xml31(td)
-#: ./doc/common/tables/heat-clients_keystone.xml31(td)
-msgid ""
-"(StrOpt) Type of endpoint in Identity service catalog to use for "
-"communication with the OpenStack service."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_nova.xml34(td)
-#: ./doc/common/tables/glance-auth_token.xml101(td)
-#: ./doc/common/tables/heat-clients.xml41(td)
-#: ./doc/common/tables/nova-auth_token.xml94(td)
-#: ./doc/common/tables/cinder-auth_token.xml101(td)
-#: ./doc/common/tables/heat-clients_heat.xml34(td)
-#: ./doc/common/tables/heat-clients_swift.xml34(td)
-#: ./doc/common/tables/trove-auth_token.xml101(td)
-#: ./doc/common/tables/heat-clients_ceilometer.xml34(td)
-#: ./doc/common/tables/heat-clients_trove.xml34(td)
-#: ./doc/common/tables/heat-clients_cinder.xml34(td)
-#: ./doc/common/tables/keystone-auth_token.xml101(td)
-#: ./doc/common/tables/ceilometer-auth.xml101(td)
-#: ./doc/common/tables/ceilometer-auth.xml136(td)
-#: ./doc/common/tables/heat-auth_token.xml101(td)
-#: ./doc/common/tables/heat-clients_neutron.xml34(td)
-#: ./doc/common/tables/neutron-auth_token.xml101(td)
-#: ./doc/common/tables/heat-clients_keystone.xml34(td)
-msgid "insecure = False"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_nova.xml35(td)
-#: ./doc/common/tables/heat-clients.xml42(td)
-#: ./doc/common/tables/heat-clients_heat.xml35(td)
-#: ./doc/common/tables/heat-clients_swift.xml35(td)
-#: ./doc/common/tables/heat-clients_ceilometer.xml35(td)
-#: ./doc/common/tables/heat-clients_trove.xml35(td)
-#: ./doc/common/tables/heat-clients_cinder.xml35(td)
-#: ./doc/common/tables/heat-clients_neutron.xml35(td)
-#: ./doc/common/tables/heat-clients_keystone.xml35(td)
-msgid "(BoolOpt) If set, then the server's certificate will not be verified."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_nova.xml39(td)
-#: ./doc/common/tables/heat-clients.xml46(td)
-#: ./doc/common/tables/heat-clients_heat.xml39(td)
-#: ./doc/common/tables/heat-clients_swift.xml39(td)
-#: ./doc/common/tables/heat-clients_ceilometer.xml39(td)
-#: ./doc/common/tables/heat-clients_trove.xml39(td)
-#: ./doc/common/tables/heat-clients_cinder.xml39(td)
-#: ./doc/common/tables/heat-clients_neutron.xml39(td)
-#: ./doc/common/tables/heat-clients_keystone.xml39(td)
-msgid "(StrOpt) Optional PEM-formatted file that contains the private key."
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-filter-recon.xml7(literal)
-#: ./doc/common/tables/swift-object-server-filter-recon.xml7(literal)
-#: ./doc/common/tables/swift-container-server-filter-recon.xml7(literal)
-msgid "[filter:recon]"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-filter-recon.xml7(literal)
-#: ./doc/common/tables/swift-account-server-app-account-server.xml7(literal)
-#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml7(literal)
-#: ./doc/common/tables/swift-account-server-account-auditor.xml7(literal)
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml7(literal)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml7(literal)
-#: ./doc/common/tables/swift-account-server-pipeline-main.xml7(literal)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml7(literal)
-msgid "account-server.conf-sample"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-filter-recon.xml18(td)
-#: ./doc/common/tables/swift-object-server-filter-recon.xml18(td)
-#: ./doc/common/tables/swift-container-server-filter-recon.xml18(td)
-msgid "use = egg:swift#recon"
-msgstr ""
-
-#: ./doc/common/tables/cinder-huawei.xml8(caption)
-msgid "Description of configuration options for huawei"
-msgstr ""
-
-#: ./doc/common/tables/cinder-huawei.xml22(td)
-msgid "cinder_huawei_conf_file = /etc/cinder/cinder_huawei_conf.xml"
-msgstr ""
-
-#: ./doc/common/tables/cinder-huawei.xml23(td)
-msgid "(StrOpt) config data for cinder huawei plugin"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml8(caption)
-msgid "Description of configuration options for netapp_eseries_iscsi"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml22(td)
-msgid "netapp_controller_ips = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml23(td)
-msgid ""
-"(StrOpt) This option is only utilized when the storage family is configured "
-"to eseries. This option is used to restrict provisioning to the specified "
-"controllers. Specify the value of this option to be a comma separated list "
-"of controller hostnames or IP addresses to be used for provisioning."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml26(td)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml22(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml22(td)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml26(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml30(td)
-msgid "netapp_login = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml27(td)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml23(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml23(td)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml27(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml31(td)
-msgid ""
-"(StrOpt) Administrative user account name used to access the storage system "
-"or proxy server."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml30(td)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml26(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml26(td)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml30(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml34(td)
-msgid "netapp_password = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml31(td)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml27(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml27(td)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml31(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml35(td)
-msgid ""
-"(StrOpt) Password for the administrative user account specified in the "
-"netapp_login option."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml34(td)
-msgid "netapp_sa_password = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml35(td)
-msgid "(StrOpt) Password for the NetApp E-Series storage array."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml38(td)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml30(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml30(td)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml34(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml38(td)
-msgid "netapp_server_hostname = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml39(td)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml31(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml31(td)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml35(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml39(td)
-msgid ""
-"(StrOpt) The hostname (or IP address) for the storage system or proxy "
-"server."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml42(td)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml34(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml34(td)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml38(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml42(td)
-msgid "netapp_server_port = 80"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml43(td)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml35(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml35(td)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml39(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml43(td)
-msgid ""
-"(IntOpt) The TCP port to use for communication with the storage system or "
-"proxy server. Traditionally, port 80 is used for HTTP and port 443 is used "
-"for HTTPS; however, this value should be changed if an alternate port has "
-"been configured on the storage system or proxy server."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml46(td)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml42(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml42(td)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml42(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml46(td)
-msgid "netapp_storage_family = ontap_cluster"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml47(td)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml43(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml43(td)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml43(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml47(td)
-msgid ""
-"(StrOpt) The storage family type used on the storage system; valid values "
-"are ontap_7mode for using Data ONTAP operating in 7-Mode, ontap_cluster for "
-"using clustered Data ONTAP, or eseries for using E-Series."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml50(td)
-msgid "netapp_storage_pools = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml51(td)
-msgid ""
-"(StrOpt) This option is used to restrict provisioning to the specified "
-"storage pools. Only dynamic disk pools are currently supported. Specify the "
-"value of this option to be a comma separated list of disk pool names to be "
-"used for provisioning."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml54(td)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml50(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml50(td)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml50(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml54(td)
-msgid "netapp_transport_type = http"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml55(td)
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml51(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml51(td)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml51(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml55(td)
-msgid ""
-"(StrOpt) The transport protocol used when communicating with the storage "
-"system or proxy server. Valid values are http or https."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml58(td)
-msgid "netapp_webservice_path = /devmgr/v2"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_eseries_iscsi.xml59(td)
-msgid ""
-"(StrOpt) This option is used to specify the path to the E-Series proxy "
-"application on a proxy server. The value is combined with the value of the "
-"netapp_transport_type, netapp_server_hostname, and netapp_server_port "
-"options to create the URL used by the driver to connect to the proxy "
-"application."
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml7(literal)
-msgid "[container-replicator]"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml18(td)
-msgid "log_name = container-replicator"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml30(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml30(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml30(td)
-msgid "vm_test_mode = no"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml30(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml30(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml30(td)
-msgid "Indicates that you are using a VM environment"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml33(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml33(td)
-msgid "per_diff = 1000"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml33(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml33(td)
-msgid "Limit number of items to get per diff"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml36(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml36(td)
-msgid "max_diffs = 100"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml36(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml36(td)
-msgid "Caps how long the replicator spends trying to sync a database per pass"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml39(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml39(td)
-msgid "concurrency = 8"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml42(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml42(td)
-msgid "interval = 30"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml45(td)
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml48(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml51(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml36(td)
-msgid "node_timeout = 10"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml51(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml66(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml57(td)
-msgid "reclaim_age = 604800"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml51(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml66(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml57(td)
-msgid "Time elapsed in seconds before an object can be reclaimed"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml54(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml36(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml60(td)
-msgid "run_pause = 30"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-replicator.xml54(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml36(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml60(td)
-msgid "Time in seconds to wait between replication passes"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml8(caption)
-msgid "Description of configuration options for glance"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml22(td)
-#: ./doc/common/tables/cinder-images.xml22(td)
-msgid "allowed_direct_url_schemes ="
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml23(td)
-msgid ""
-"(ListOpt) A list of url scheme that can be downloaded directly via the "
-"direct_url. Currently supported schemes: [file]."
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml26(td)
-#: ./doc/common/tables/cinder-images.xml26(td)
-msgid "glance_api_insecure = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml27(td)
-#: ./doc/common/tables/cinder-images.xml27(td)
-msgid "(BoolOpt) Allow to perform insecure SSL (https) requests to glance"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml30(td)
-#: ./doc/common/tables/cinder-images.xml30(td)
-msgid "glance_api_servers = $glance_host:$glance_port"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml31(td)
-msgid ""
-"(ListOpt) A list of the glance api servers available to nova. Prefix with "
-"https:// for ssl-based glance api servers. ([hostname|ip]:port)"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml34(td)
-#: ./doc/common/tables/cinder-images.xml42(td)
-msgid "glance_host = $my_ip"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml35(td)
-msgid "(StrOpt) Default glance hostname or IP address"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml38(td)
-#: ./doc/common/tables/cinder-images.xml46(td)
-msgid "glance_num_retries = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml39(td)
-msgid "(IntOpt) Number of retries when downloading an image from glance"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml42(td)
-#: ./doc/common/tables/cinder-images.xml50(td)
-msgid "glance_port = 9292"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml43(td)
-msgid "(IntOpt) Default glance port"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml46(td)
-msgid "glance_protocol = http"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml47(td)
-msgid ""
-"(StrOpt) Default protocol to use when connecting to glance. Set to https for"
-" SSL."
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml50(td)
-msgid "osapi_glance_link_prefix = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml51(td)
-msgid ""
-"(StrOpt) Base URL that will be presented to users in links to glance "
-"resources"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml54(th)
-msgid "[image_file_url]"
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml57(td)
-msgid "filesystems ="
-msgstr ""
-
-#: ./doc/common/tables/nova-glance.xml58(td)
-msgid ""
-"(ListOpt) List of file systems that are configured in this file in the "
-"image_file_url:&lt;list entry name&gt; sections"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml8(caption)
-msgid "Description of configuration options for dhcp_agent"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml22(td)
-#: ./doc/common/tables/nova-network.xml74(td)
-msgid "dnsmasq_config_file ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml23(td)
-#: ./doc/common/tables/nova-network.xml75(td)
-msgid "(StrOpt) Override the default dnsmasq settings with this file"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml26(td)
-msgid "dnsmasq_dns_servers = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml27(td)
-msgid ""
-"(ListOpt) Comma-separated list of the DNS servers which will be used as "
-"forwarders."
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml30(td)
-msgid "dnsmasq_lease_max = 16777216"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml31(td)
-msgid "(IntOpt) Limit number of leases to prevent a denial-of-service."
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml34(td)
-msgid "enable_isolated_metadata = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml35(td)
-msgid "(BoolOpt) Support Metadata requests on isolated networks."
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml38(td)
-msgid "enable_metadata_network = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml39(td)
-msgid ""
-"(BoolOpt) Allows for serving metadata requests from a dedicated network. "
-"Requires enable_isolated_metadata = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml42(td)
-msgid "num_sync_threads = 4"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml43(td)
-msgid "(IntOpt) Number of threads to use during sync process."
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml46(td)
-msgid "resync_interval = 5"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml47(td)
-msgid "(IntOpt) Interval to resync."
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml50(td)
-msgid "use_namespaces = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-dhcp_agent.xml51(td)
-msgid "(BoolOpt) Allow overlapping IP."
+#: ./doc/common/tables/glance-policy.xml27(td)
+msgid "(StrOpt) The location of the policy file."
 msgstr ""
 
 #: ./doc/common/tables/nova-neutron.xml8(caption)
@@ -30553,11 +36188,6 @@ msgstr ""
 msgid "neutron_ovs_bridge = br-int"
 msgstr ""
 
-#: ./doc/common/tables/nova-neutron.xml67(td)
-#: ./doc/common/tables/nova-xen.xml157(td)
-msgid "(StrOpt) Name of Integration Bridge used by Open vSwitch"
-msgstr ""
-
 #: ./doc/common/tables/nova-neutron.xml70(td)
 msgid "neutron_region_name = None"
 msgstr ""
@@ -30592,1170 +36222,95 @@ msgid ""
 "resolve instance ids."
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml8(caption)
-msgid "Description of configuration options for backups_ceph"
+#: ./doc/common/tables/cinder-backups.xml8(caption)
+msgid "Description of configuration options for backups"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml22(td)
-msgid "backup_ceph_chunk_size = 134217728"
+#: ./doc/common/tables/cinder-backups.xml22(td)
+msgid "backup_api_class = cinder.backup.api.API"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml23(td)
+#: ./doc/common/tables/cinder-backups.xml23(td)
+msgid "(StrOpt) The full class name of the volume backup API class"
+msgstr ""
+
+#: ./doc/common/tables/cinder-backups.xml26(td)
+msgid "backup_compression_algorithm = zlib"
+msgstr ""
+
+#: ./doc/common/tables/cinder-backups.xml27(td)
+msgid "(StrOpt) Compression algorithm (None to disable)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-backups.xml30(td)
+msgid "backup_driver = cinder.backup.drivers.swift"
+msgstr ""
+
+#: ./doc/common/tables/cinder-backups.xml31(td)
+msgid "(StrOpt) Driver to use for backups."
+msgstr ""
+
+#: ./doc/common/tables/cinder-backups.xml34(td)
+msgid "backup_manager = cinder.backup.manager.BackupManager"
+msgstr ""
+
+#: ./doc/common/tables/cinder-backups.xml35(td)
+msgid "(StrOpt) full class name for the Manager for volume backup"
+msgstr ""
+
+#: ./doc/common/tables/cinder-backups.xml38(td)
+msgid "backup_metadata_version = 1"
+msgstr ""
+
+#: ./doc/common/tables/cinder-backups.xml39(td)
 msgid ""
-"(IntOpt) The chunk size, in bytes, that a backup is broken into before "
-"transfer to the Ceph object store."
+"(IntOpt) Backup metadata version to be used when backing up volume metadata."
+" If this number is bumped, make sure the service doing the restore supports "
+"the new version."
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml26(td)
-msgid "backup_ceph_conf = /etc/ceph/ceph.conf"
+#: ./doc/common/tables/cinder-backups.xml42(td)
+msgid "backup_name_template = backup-%s"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml27(td)
-msgid "(StrOpt) Ceph configuration file to use."
+#: ./doc/common/tables/cinder-backups.xml43(td)
+msgid "(StrOpt) Template string to be used to generate backup names"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml30(td)
-msgid "backup_ceph_pool = backups"
+#: ./doc/common/tables/cinder-backups.xml46(td)
+msgid "backup_topic = cinder-backup"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml31(td)
-msgid "(StrOpt) The Ceph pool where volume backups are stored."
+#: ./doc/common/tables/cinder-backups.xml47(td)
+msgid "(StrOpt) the topic volume backup nodes listen on"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml34(td)
-msgid "backup_ceph_stripe_count = 0"
+#: ./doc/common/tables/cinder-backups.xml50(td)
+#: ./doc/common/tables/nova-api.xml90(td)
+msgid "snapshot_name_template = snapshot-%s"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml35(td)
-msgid "(IntOpt) RBD stripe count to use when creating a backup image."
+#: ./doc/common/tables/cinder-backups.xml51(td)
+#: ./doc/common/tables/nova-api.xml91(td)
+msgid "(StrOpt) Template string to be used to generate snapshot names"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml38(td)
-msgid "backup_ceph_stripe_unit = 0"
+#: ./doc/common/tables/cinder-backups.xml54(td)
+msgid "snapshot_same_host = True"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml39(td)
-msgid "(IntOpt) RBD stripe unit to use when creating a backup image."
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups_ceph.xml42(td)
-msgid "backup_ceph_user = cinder"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups_ceph.xml43(td)
+#: ./doc/common/tables/cinder-backups.xml55(td)
 msgid ""
-"(StrOpt) The Ceph user to connect with. Default here is to use the same user"
-" as for Cinder volumes. If not using cephx this should be set to None."
+"(BoolOpt) Create volume from snapshot at the host where snapshot resides"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml46(td)
-msgid "restore_discard_excess_bytes = True"
+#: ./doc/common/tables/cinder-keymgr.xml22(td)
+msgid "api_class = cinder.keymgr.conf_key_mgr.ConfKeyManager"
 msgstr ""
 
-#: ./doc/common/tables/cinder-backups_ceph.xml47(td)
-msgid ""
-"(BoolOpt) If True, always discard excess bytes when restoring volumes i.e. "
-"pad with zeroes."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml7(literal)
-msgid "[filter:name_check]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml18(td)
-msgid "use = egg:swift#name_check"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml21(td)
-msgid "forbidden_chars = '\"`&lt;&gt;"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml21(td)
-msgid "Characters that are not allowed in a name"
-msgstr "名前において許可されない文字"
-
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml24(td)
-msgid "maximum_length = 255"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml24(td)
-msgid "Maximum length of a name"
-msgstr "名前の最大長"
-
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml27(td)
-msgid "forbidden_regexp = /\\./|/\\.\\./|/\\.$|/\\.\\.$"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml27(td)
-msgid "Substrings to forbid, using regular expression syntax"
-msgstr "禁止されている部分文字列、正規表現構文の使用"
-
-#: ./doc/common/tables/nova-metadata.xml8(caption)
-#: ./doc/common/tables/neutron-metadata.xml8(caption)
-msgid "Description of configuration options for metadata"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml22(td)
-msgid "metadata_host = $my_ip"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml23(td)
-msgid "(StrOpt) The IP address for the metadata API server"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml26(td)
-msgid "metadata_listen = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml27(td)
-msgid "(StrOpt) The IP address on which the metadata API will listen."
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml30(td)
-msgid "metadata_listen_port = 8775"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml31(td)
-msgid "(IntOpt) The port on which the metadata API will listen."
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml34(td)
-msgid "metadata_manager = nova.api.manager.MetadataManager"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml35(td)
-msgid "(StrOpt) OpenStack metadata service manager"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml38(td)
-msgid "metadata_port = 8775"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml39(td)
-msgid "(IntOpt) The port for the metadata API port"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml42(td)
-msgid "metadata_workers = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml43(td)
-msgid ""
-"(IntOpt) Number of workers for metadata service. The default will be the "
-"number of CPUs available."
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml46(td)
-msgid ""
-"vendordata_driver = nova.api.metadata.vendordata_json.JsonFileVendorData"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml47(td)
-msgid "(StrOpt) Driver to use for vendor data"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml50(td)
-msgid "vendordata_jsonfile_path = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-metadata.xml51(td)
-msgid "(StrOpt) File to load json formatted vendor data from"
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml8(caption)
-#: ./doc/common/tables/nova-s3.xml8(caption)
-msgid "Description of configuration options for s3"
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml22(td)
-msgid "s3_store_access_key = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml23(td)
-msgid "(StrOpt) The S3 query token access key."
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml26(td)
-msgid "s3_store_bucket = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml27(td)
-msgid "(StrOpt) The S3 bucket to be used to store the Glance data."
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml30(td)
-msgid "s3_store_bucket_url_format = subdomain"
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml31(td)
-msgid ""
-"(StrOpt) The S3 calling format used to determine the bucket. Either "
-"subdomain or path can be used."
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml34(td)
-msgid "s3_store_create_bucket_on_put = False"
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml35(td)
-msgid ""
-"(BoolOpt) A boolean to determine if the S3 bucket should be created on "
-"upload if it does not exist or if an error should be returned to the user."
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml38(td)
-msgid "s3_store_host = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml39(td)
-msgid "(StrOpt) The host where the S3 server is listening."
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml42(td)
-msgid "s3_store_object_buffer_dir = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml43(td)
-msgid ""
-"(StrOpt) The local directory where uploads will be staged before they are "
-"transferred into S3."
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml46(td)
-msgid "s3_store_secret_key = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-s3.xml47(td)
-msgid "(StrOpt) The S3 query token secret key."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml8(caption)
-#: ./doc/common/tables/nova-auth_token.xml8(caption)
-#: ./doc/common/tables/cinder-auth_token.xml8(caption)
-#: ./doc/common/tables/trove-auth_token.xml8(caption)
-#: ./doc/common/tables/keystone-auth_token.xml8(caption)
-#: ./doc/common/tables/heat-auth_token.xml8(caption)
-#: ./doc/common/tables/neutron-auth_token.xml8(caption)
-msgid "Description of configuration options for auth_token"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml22(td)
-#: ./doc/common/tables/glance-auth_token.xml117(td)
-#: ./doc/common/tables/nova-common.xml50(td)
-#: ./doc/common/tables/nova-auth_token.xml110(td)
-#: ./doc/common/tables/cinder-auth_token.xml22(td)
-#: ./doc/common/tables/cinder-auth_token.xml117(td)
-#: ./doc/common/tables/trove-auth_token.xml22(td)
-#: ./doc/common/tables/trove-auth_token.xml117(td)
-#: ./doc/common/tables/keystone-auth_token.xml22(td)
-#: ./doc/common/tables/keystone-auth_token.xml117(td)
-#: ./doc/common/tables/ceilometer-common.xml38(td)
-#: ./doc/common/tables/ceilometer-auth.xml117(td)
-#: ./doc/common/tables/heat-auth_token.xml22(td)
-#: ./doc/common/tables/heat-auth_token.xml117(td)
-#: ./doc/common/tables/neutron-auth_token.xml22(td)
-#: ./doc/common/tables/neutron-auth_token.xml117(td)
-msgid "memcached_servers = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml23(td)
-#: ./doc/common/tables/nova-common.xml51(td)
-#: ./doc/common/tables/cinder-auth_token.xml23(td)
-#: ./doc/common/tables/trove-auth_token.xml23(td)
-#: ./doc/common/tables/keystone-auth_token.xml23(td)
-#: ./doc/common/tables/ceilometer-common.xml39(td)
-#: ./doc/common/tables/heat-auth_token.xml23(td)
-#: ./doc/common/tables/neutron-auth_token.xml23(td)
-msgid "(ListOpt) Memcached servers or None for in process cache."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml26(th)
-#: ./doc/common/tables/nova-auth_token.xml19(th)
-#: ./doc/common/tables/cinder-auth_token.xml26(th)
-#: ./doc/common/tables/trove-auth_token.xml26(th)
-#: ./doc/common/tables/keystone-auth_token.xml26(th)
-#: ./doc/common/tables/ceilometer-auth.xml26(th)
-#: ./doc/common/tables/heat-auth_token.xml26(th)
-#: ./doc/common/tables/neutron-auth_token.xml26(th)
-msgid "[keystone_authtoken]"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml29(td)
-#: ./doc/common/tables/neutron-common.xml22(td)
-#: ./doc/common/tables/neutron-common.xml192(td)
-#: ./doc/common/tables/neutron-common.xml219(td)
-#: ./doc/common/tables/nova-auth_token.xml22(td)
-#: ./doc/common/tables/cinder-auth_token.xml29(td)
-#: ./doc/common/tables/trove-auth_token.xml29(td)
-#: ./doc/common/tables/glance-registry.xml22(td)
-#: ./doc/common/tables/keystone-auth_token.xml29(td)
-#: ./doc/common/tables/ceilometer-auth.xml29(td)
-#: ./doc/common/tables/heat-auth_token.xml29(td)
-#: ./doc/common/tables/neutron-embrane_lb.xml22(td)
-#: ./doc/common/tables/neutron-auth_token.xml29(td)
-msgid "admin_password = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml30(td)
-#: ./doc/common/tables/nova-auth_token.xml23(td)
-#: ./doc/common/tables/cinder-auth_token.xml30(td)
-#: ./doc/common/tables/trove-auth_token.xml30(td)
-#: ./doc/common/tables/keystone-auth_token.xml30(td)
-#: ./doc/common/tables/ceilometer-auth.xml30(td)
-#: ./doc/common/tables/heat-auth_token.xml30(td)
-#: ./doc/common/tables/neutron-auth_token.xml30(td)
-msgid "(StrOpt) Keystone account password"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml33(td)
-#: ./doc/common/tables/nova-auth_token.xml26(td)
-#: ./doc/common/tables/cinder-auth_token.xml33(td)
-#: ./doc/common/tables/trove-auth_token.xml33(td)
-#: ./doc/common/tables/keystone-auth_token.xml33(td)
-#: ./doc/common/tables/ceilometer-auth.xml33(td)
-#: ./doc/common/tables/heat-auth_token.xml33(td)
-#: ./doc/common/tables/neutron-auth_token.xml33(td)
-msgid "admin_tenant_name = admin"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml34(td)
-#: ./doc/common/tables/nova-auth_token.xml27(td)
-#: ./doc/common/tables/cinder-auth_token.xml34(td)
-#: ./doc/common/tables/trove-auth_token.xml34(td)
-#: ./doc/common/tables/keystone-auth_token.xml34(td)
-#: ./doc/common/tables/ceilometer-auth.xml34(td)
-#: ./doc/common/tables/heat-auth_token.xml34(td)
-#: ./doc/common/tables/neutron-auth_token.xml34(td)
-msgid "(StrOpt) Keystone service account tenant name to validate user tokens"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml37(td)
-#: ./doc/common/tables/nova-auth_token.xml30(td)
-#: ./doc/common/tables/cinder-auth_token.xml37(td)
-#: ./doc/common/tables/trove-auth_token.xml37(td)
-#: ./doc/common/tables/keystone-auth_token.xml37(td)
-#: ./doc/common/tables/ceilometer-auth.xml37(td)
-#: ./doc/common/tables/heat-auth_token.xml37(td)
-#: ./doc/common/tables/neutron-auth_token.xml37(td)
-msgid "admin_token = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml38(td)
-#: ./doc/common/tables/nova-auth_token.xml31(td)
-#: ./doc/common/tables/cinder-auth_token.xml38(td)
-#: ./doc/common/tables/trove-auth_token.xml38(td)
-#: ./doc/common/tables/keystone-auth_token.xml38(td)
-#: ./doc/common/tables/ceilometer-auth.xml38(td)
-#: ./doc/common/tables/heat-auth_token.xml38(td)
-#: ./doc/common/tables/neutron-auth_token.xml38(td)
-msgid ""
-"(StrOpt) Single shared secret with the Keystone configuration used for "
-"bootstrapping a Keystone installation, or otherwise bypassing the normal "
-"authentication process."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml41(td)
-#: ./doc/common/tables/neutron-common.xml30(td)
-#: ./doc/common/tables/neutron-common.xml200(td)
-#: ./doc/common/tables/nova-auth_token.xml34(td)
-#: ./doc/common/tables/cinder-auth_token.xml41(td)
-#: ./doc/common/tables/trove-auth_token.xml41(td)
-#: ./doc/common/tables/glance-registry.xml30(td)
-#: ./doc/common/tables/keystone-auth_token.xml41(td)
-#: ./doc/common/tables/ceilometer-auth.xml41(td)
-#: ./doc/common/tables/heat-auth_token.xml41(td)
-#: ./doc/common/tables/neutron-auth_token.xml41(td)
-msgid "admin_user = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml42(td)
-#: ./doc/common/tables/nova-auth_token.xml35(td)
-#: ./doc/common/tables/cinder-auth_token.xml42(td)
-#: ./doc/common/tables/trove-auth_token.xml42(td)
-#: ./doc/common/tables/keystone-auth_token.xml42(td)
-#: ./doc/common/tables/ceilometer-auth.xml42(td)
-#: ./doc/common/tables/heat-auth_token.xml42(td)
-#: ./doc/common/tables/neutron-auth_token.xml42(td)
-msgid "(StrOpt) Keystone account username"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml45(td)
-#: ./doc/common/tables/nova-auth_token.xml38(td)
-#: ./doc/common/tables/cinder-auth_token.xml45(td)
-#: ./doc/common/tables/trove-auth_token.xml45(td)
-#: ./doc/common/tables/keystone-auth_token.xml45(td)
-#: ./doc/common/tables/ceilometer-auth.xml45(td)
-#: ./doc/common/tables/heat-auth_token.xml45(td)
-#: ./doc/common/tables/neutron-auth_token.xml45(td)
-msgid "auth_admin_prefix ="
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml46(td)
-#: ./doc/common/tables/nova-auth_token.xml39(td)
-#: ./doc/common/tables/cinder-auth_token.xml46(td)
-#: ./doc/common/tables/trove-auth_token.xml46(td)
-#: ./doc/common/tables/keystone-auth_token.xml46(td)
-#: ./doc/common/tables/ceilometer-auth.xml46(td)
-#: ./doc/common/tables/heat-auth_token.xml46(td)
-#: ./doc/common/tables/neutron-auth_token.xml46(td)
-msgid "(StrOpt) Prefix to prepend at the beginning of the path"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml49(td)
-#: ./doc/common/tables/nova-auth_token.xml42(td)
-#: ./doc/common/tables/cinder-auth_token.xml49(td)
-#: ./doc/common/tables/trove-auth_token.xml49(td)
-#: ./doc/common/tables/keystone-auth_token.xml49(td)
-#: ./doc/common/tables/ceilometer-auth.xml49(td)
-#: ./doc/common/tables/heat-auth_token.xml49(td)
-#: ./doc/common/tables/neutron-auth_token.xml49(td)
-msgid "auth_host = 127.0.0.1"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml50(td)
-#: ./doc/common/tables/nova-auth_token.xml43(td)
-#: ./doc/common/tables/cinder-auth_token.xml50(td)
-#: ./doc/common/tables/trove-auth_token.xml50(td)
-#: ./doc/common/tables/keystone-auth_token.xml50(td)
-#: ./doc/common/tables/ceilometer-auth.xml50(td)
-#: ./doc/common/tables/heat-auth_token.xml50(td)
-#: ./doc/common/tables/neutron-auth_token.xml50(td)
-msgid "(StrOpt) Host providing the admin Identity API endpoint"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml53(td)
-#: ./doc/common/tables/nova-auth_token.xml46(td)
-#: ./doc/common/tables/cinder-auth_token.xml53(td)
-#: ./doc/common/tables/trove-auth_token.xml53(td)
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml21(td)
-#: ./doc/common/tables/keystone-auth_token.xml53(td)
-#: ./doc/common/tables/ceilometer-auth.xml53(td)
-#: ./doc/common/tables/heat-auth_token.xml53(td)
-#: ./doc/common/tables/neutron-auth_token.xml53(td)
-msgid "auth_port = 35357"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml54(td)
-#: ./doc/common/tables/nova-auth_token.xml47(td)
-#: ./doc/common/tables/cinder-auth_token.xml54(td)
-#: ./doc/common/tables/trove-auth_token.xml54(td)
-#: ./doc/common/tables/keystone-auth_token.xml54(td)
-#: ./doc/common/tables/ceilometer-auth.xml54(td)
-#: ./doc/common/tables/heat-auth_token.xml54(td)
-#: ./doc/common/tables/neutron-auth_token.xml54(td)
-msgid "(IntOpt) Port of the admin Identity API endpoint"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml57(td)
-#: ./doc/common/tables/nova-auth_token.xml50(td)
-#: ./doc/common/tables/cinder-auth_token.xml57(td)
-#: ./doc/common/tables/trove-auth_token.xml57(td)
-#: ./doc/common/tables/keystone-auth_token.xml57(td)
-#: ./doc/common/tables/ceilometer-auth.xml57(td)
-#: ./doc/common/tables/heat-auth_token.xml57(td)
-#: ./doc/common/tables/neutron-auth_token.xml57(td)
-msgid "auth_protocol = https"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml58(td)
-#: ./doc/common/tables/nova-auth_token.xml51(td)
-#: ./doc/common/tables/cinder-auth_token.xml58(td)
-#: ./doc/common/tables/trove-auth_token.xml58(td)
-#: ./doc/common/tables/keystone-auth_token.xml58(td)
-#: ./doc/common/tables/ceilometer-auth.xml58(td)
-#: ./doc/common/tables/heat-auth_token.xml58(td)
-#: ./doc/common/tables/neutron-auth_token.xml58(td)
-msgid "(StrOpt) Protocol of the admin Identity API endpoint(http or https)"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml61(td)
-#: ./doc/common/tables/nova-auth_token.xml54(td)
-#: ./doc/common/tables/cinder-auth_token.xml61(td)
-#: ./doc/common/tables/trove-auth_token.xml61(td)
-#: ./doc/common/tables/heat-api.xml92(td)
-#: ./doc/common/tables/keystone-auth_token.xml61(td)
-#: ./doc/common/tables/ceilometer-auth.xml61(td)
-#: ./doc/common/tables/heat-auth_token.xml61(td)
-#: ./doc/common/tables/neutron-auth_token.xml61(td)
-msgid "auth_uri = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml62(td)
-#: ./doc/common/tables/nova-auth_token.xml55(td)
-#: ./doc/common/tables/cinder-auth_token.xml62(td)
-#: ./doc/common/tables/trove-auth_token.xml62(td)
-#: ./doc/common/tables/keystone-auth_token.xml62(td)
-#: ./doc/common/tables/ceilometer-auth.xml62(td)
-#: ./doc/common/tables/heat-auth_token.xml62(td)
-#: ./doc/common/tables/neutron-auth_token.xml62(td)
-msgid "(StrOpt) Complete public Identity API endpoint"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml65(td)
-#: ./doc/common/tables/nova-auth_token.xml58(td)
-#: ./doc/common/tables/cinder-auth_token.xml65(td)
-#: ./doc/common/tables/trove-auth_token.xml65(td)
-#: ./doc/common/tables/keystone-auth_token.xml65(td)
-#: ./doc/common/tables/ceilometer-auth.xml65(td)
-#: ./doc/common/tables/heat-auth_token.xml65(td)
-#: ./doc/common/tables/neutron-auth_token.xml65(td)
-msgid "auth_version = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml66(td)
-#: ./doc/common/tables/nova-auth_token.xml59(td)
-#: ./doc/common/tables/cinder-auth_token.xml66(td)
-#: ./doc/common/tables/trove-auth_token.xml66(td)
-#: ./doc/common/tables/keystone-auth_token.xml66(td)
-#: ./doc/common/tables/ceilometer-auth.xml66(td)
-#: ./doc/common/tables/heat-auth_token.xml66(td)
-#: ./doc/common/tables/neutron-auth_token.xml66(td)
-msgid "(StrOpt) API version of the admin Identity API endpoint"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml69(td)
-#: ./doc/common/tables/nova-auth_token.xml62(td)
-#: ./doc/common/tables/cinder-auth_token.xml69(td)
-#: ./doc/common/tables/trove-auth_token.xml69(td)
-#: ./doc/common/tables/keystone-auth_token.xml69(td)
-#: ./doc/common/tables/ceilometer-auth.xml69(td)
-#: ./doc/common/tables/heat-auth_token.xml69(td)
-#: ./doc/common/tables/neutron-auth_token.xml69(td)
-msgid "cache = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml70(td)
-#: ./doc/common/tables/nova-auth_token.xml63(td)
-#: ./doc/common/tables/cinder-auth_token.xml70(td)
-#: ./doc/common/tables/trove-auth_token.xml70(td)
-#: ./doc/common/tables/keystone-auth_token.xml70(td)
-#: ./doc/common/tables/ceilometer-auth.xml70(td)
-#: ./doc/common/tables/heat-auth_token.xml70(td)
-#: ./doc/common/tables/neutron-auth_token.xml70(td)
-msgid "(StrOpt) Env key for the swift cache"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml73(td)
-#: ./doc/common/tables/nova-auth_token.xml66(td)
-#: ./doc/common/tables/cinder-auth_token.xml73(td)
-#: ./doc/common/tables/trove-auth_token.xml73(td)
-#: ./doc/common/tables/keystone-auth_token.xml73(td)
-#: ./doc/common/tables/ceilometer-auth.xml73(td)
-#: ./doc/common/tables/heat-auth_token.xml73(td)
-#: ./doc/common/tables/neutron-auth_token.xml73(td)
-msgid "cafile = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml74(td)
-#: ./doc/common/tables/nova-auth_token.xml67(td)
-#: ./doc/common/tables/cinder-auth_token.xml74(td)
-#: ./doc/common/tables/trove-auth_token.xml74(td)
-#: ./doc/common/tables/keystone-auth_token.xml74(td)
-#: ./doc/common/tables/ceilometer-auth.xml74(td)
-#: ./doc/common/tables/heat-auth_token.xml74(td)
-#: ./doc/common/tables/neutron-auth_token.xml74(td)
-msgid ""
-"(StrOpt) A PEM encoded Certificate Authority to use when verifying HTTPs "
-"connections. Defaults to system CAs."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml77(td)
-#: ./doc/common/tables/nova-auth_token.xml70(td)
-#: ./doc/common/tables/cinder-auth_token.xml77(td)
-#: ./doc/common/tables/trove-auth_token.xml77(td)
-#: ./doc/common/tables/keystone-auth_token.xml77(td)
-#: ./doc/common/tables/ceilometer-auth.xml77(td)
-#: ./doc/common/tables/heat-auth_token.xml77(td)
-#: ./doc/common/tables/neutron-auth_token.xml77(td)
-msgid "certfile = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml78(td)
-#: ./doc/common/tables/glance-auth_token.xml106(td)
-#: ./doc/common/tables/nova-auth_token.xml71(td)
-#: ./doc/common/tables/nova-auth_token.xml99(td)
-#: ./doc/common/tables/cinder-auth_token.xml78(td)
-#: ./doc/common/tables/cinder-auth_token.xml106(td)
-#: ./doc/common/tables/trove-auth_token.xml78(td)
-#: ./doc/common/tables/trove-auth_token.xml106(td)
-#: ./doc/common/tables/keystone-auth_token.xml78(td)
-#: ./doc/common/tables/keystone-auth_token.xml106(td)
-#: ./doc/common/tables/ceilometer-auth.xml78(td)
-#: ./doc/common/tables/ceilometer-auth.xml106(td)
-#: ./doc/common/tables/heat-auth_token.xml78(td)
-#: ./doc/common/tables/heat-auth_token.xml106(td)
-#: ./doc/common/tables/neutron-auth_token.xml78(td)
-#: ./doc/common/tables/neutron-auth_token.xml106(td)
-msgid "(StrOpt) Required if Keystone server requires client certificate"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml81(td)
-#: ./doc/common/tables/nova-auth_token.xml74(td)
-#: ./doc/common/tables/cinder-auth_token.xml81(td)
-#: ./doc/common/tables/trove-auth_token.xml81(td)
-#: ./doc/common/tables/keystone-auth_token.xml81(td)
-#: ./doc/common/tables/ceilometer-auth.xml81(td)
-#: ./doc/common/tables/heat-auth_token.xml81(td)
-#: ./doc/common/tables/neutron-auth_token.xml81(td)
-msgid "delay_auth_decision = False"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml82(td)
-#: ./doc/common/tables/nova-auth_token.xml75(td)
-#: ./doc/common/tables/cinder-auth_token.xml82(td)
-#: ./doc/common/tables/trove-auth_token.xml82(td)
-#: ./doc/common/tables/keystone-auth_token.xml82(td)
-#: ./doc/common/tables/ceilometer-auth.xml82(td)
-#: ./doc/common/tables/heat-auth_token.xml82(td)
-#: ./doc/common/tables/neutron-auth_token.xml82(td)
-msgid ""
-"(BoolOpt) Do not handle authorization requests within the middleware, but "
-"delegate the authorization decision to downstream WSGI components"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml85(td)
-#: ./doc/common/tables/nova-auth_token.xml78(td)
-#: ./doc/common/tables/cinder-auth_token.xml85(td)
-#: ./doc/common/tables/trove-auth_token.xml85(td)
-#: ./doc/common/tables/keystone-token.xml38(td)
-#: ./doc/common/tables/keystone-auth_token.xml85(td)
-#: ./doc/common/tables/ceilometer-auth.xml85(td)
-#: ./doc/common/tables/heat-auth_token.xml85(td)
-#: ./doc/common/tables/neutron-auth_token.xml85(td)
-msgid "enforce_token_bind = permissive"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml86(td)
-#: ./doc/common/tables/nova-auth_token.xml79(td)
-#: ./doc/common/tables/cinder-auth_token.xml86(td)
-#: ./doc/common/tables/trove-auth_token.xml86(td)
-#: ./doc/common/tables/keystone-auth_token.xml86(td)
-#: ./doc/common/tables/ceilometer-auth.xml86(td)
-#: ./doc/common/tables/heat-auth_token.xml86(td)
-#: ./doc/common/tables/neutron-auth_token.xml86(td)
-msgid ""
-"(StrOpt) Used to control the use and type of token binding. Can be set to: "
-"\"disabled\" to not check token binding. \"permissive\" (default) to "
-"validate binding information if the bind type is of a form known to the "
-"server and ignore it if not. \"strict\" like \"permissive\" but if the bind "
-"type is unknown the token will be rejected. \"required\" any form of token "
-"binding is needed to be allowed. Finally the name of a binding method that "
-"must be present in tokens."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml89(td)
-#: ./doc/common/tables/nova-auth_token.xml82(td)
-#: ./doc/common/tables/cinder-auth_token.xml89(td)
-#: ./doc/common/tables/trove-auth_token.xml89(td)
-#: ./doc/common/tables/keystone-auth_token.xml89(td)
-#: ./doc/common/tables/ceilometer-auth.xml89(td)
-#: ./doc/common/tables/heat-auth_token.xml89(td)
-#: ./doc/common/tables/neutron-auth_token.xml89(td)
-msgid "http_connect_timeout = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml90(td)
-#: ./doc/common/tables/nova-auth_token.xml83(td)
-#: ./doc/common/tables/cinder-auth_token.xml90(td)
-#: ./doc/common/tables/trove-auth_token.xml90(td)
-#: ./doc/common/tables/keystone-auth_token.xml90(td)
-#: ./doc/common/tables/ceilometer-auth.xml90(td)
-#: ./doc/common/tables/heat-auth_token.xml90(td)
-#: ./doc/common/tables/neutron-auth_token.xml90(td)
-msgid ""
-"(BoolOpt) Request timeout value for communicating with Identity API server."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml93(td)
-#: ./doc/common/tables/nova-auth_token.xml86(td)
-#: ./doc/common/tables/cinder-auth_token.xml93(td)
-#: ./doc/common/tables/trove-auth_token.xml93(td)
-#: ./doc/common/tables/keystone-auth_token.xml93(td)
-#: ./doc/common/tables/ceilometer-auth.xml93(td)
-#: ./doc/common/tables/heat-auth_token.xml93(td)
-#: ./doc/common/tables/neutron-auth_token.xml93(td)
-msgid "http_request_max_retries = 3"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml94(td)
-#: ./doc/common/tables/nova-auth_token.xml87(td)
-#: ./doc/common/tables/cinder-auth_token.xml94(td)
-#: ./doc/common/tables/trove-auth_token.xml94(td)
-#: ./doc/common/tables/keystone-auth_token.xml94(td)
-#: ./doc/common/tables/ceilometer-auth.xml94(td)
-#: ./doc/common/tables/heat-auth_token.xml94(td)
-#: ./doc/common/tables/neutron-auth_token.xml94(td)
-msgid ""
-"(IntOpt) How many times are we trying to reconnect when communicating with "
-"Identity API Server."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml97(td)
-#: ./doc/common/tables/nova-auth_token.xml90(td)
-#: ./doc/common/tables/cinder-auth_token.xml97(td)
-#: ./doc/common/tables/trove-auth_token.xml97(td)
-#: ./doc/common/tables/keystone-auth_token.xml97(td)
-#: ./doc/common/tables/ceilometer-auth.xml97(td)
-#: ./doc/common/tables/heat-auth_token.xml97(td)
-#: ./doc/common/tables/neutron-auth_token.xml97(td)
-msgid "include_service_catalog = True"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml98(td)
-#: ./doc/common/tables/nova-auth_token.xml91(td)
-#: ./doc/common/tables/cinder-auth_token.xml98(td)
-#: ./doc/common/tables/trove-auth_token.xml98(td)
-#: ./doc/common/tables/keystone-auth_token.xml98(td)
-#: ./doc/common/tables/ceilometer-auth.xml98(td)
-#: ./doc/common/tables/heat-auth_token.xml98(td)
-#: ./doc/common/tables/neutron-auth_token.xml98(td)
-msgid ""
-"(BoolOpt) (optional) indicate whether to set the X-Service-Catalog header. "
-"If False, middleware will not ask for service catalog on token validation "
-"and will not set the X-Service-Catalog header."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml102(td)
-#: ./doc/common/tables/nova-auth_token.xml95(td)
-#: ./doc/common/tables/cinder-auth_token.xml102(td)
-#: ./doc/common/tables/trove-auth_token.xml102(td)
-#: ./doc/common/tables/keystone-auth_token.xml102(td)
-#: ./doc/common/tables/ceilometer-auth.xml102(td)
-#: ./doc/common/tables/heat-auth_token.xml102(td)
-#: ./doc/common/tables/neutron-auth_token.xml102(td)
-msgid "(BoolOpt) Verify HTTPS connections."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml105(td)
-#: ./doc/common/tables/nova-auth_token.xml98(td)
-#: ./doc/common/tables/cinder-auth_token.xml105(td)
-#: ./doc/common/tables/trove-auth_token.xml105(td)
-#: ./doc/common/tables/keystone-auth_token.xml105(td)
-#: ./doc/common/tables/ceilometer-auth.xml105(td)
-#: ./doc/common/tables/heat-auth_token.xml105(td)
-#: ./doc/common/tables/neutron-auth_token.xml105(td)
-msgid "keyfile = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml109(td)
-#: ./doc/common/tables/nova-auth_token.xml102(td)
-#: ./doc/common/tables/cinder-auth_token.xml109(td)
-#: ./doc/common/tables/trove-auth_token.xml109(td)
-#: ./doc/common/tables/keystone-auth_token.xml109(td)
-#: ./doc/common/tables/ceilometer-auth.xml109(td)
-#: ./doc/common/tables/heat-auth_token.xml109(td)
-#: ./doc/common/tables/neutron-auth_token.xml109(td)
-msgid "memcache_secret_key = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml110(td)
-#: ./doc/common/tables/nova-auth_token.xml103(td)
-#: ./doc/common/tables/cinder-auth_token.xml110(td)
-#: ./doc/common/tables/trove-auth_token.xml110(td)
-#: ./doc/common/tables/keystone-auth_token.xml110(td)
-#: ./doc/common/tables/ceilometer-auth.xml110(td)
-#: ./doc/common/tables/heat-auth_token.xml110(td)
-#: ./doc/common/tables/neutron-auth_token.xml110(td)
-msgid ""
-"(StrOpt) (optional, mandatory if memcache_security_strategy is defined) this"
-" string is used for key derivation."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml113(td)
-#: ./doc/common/tables/nova-auth_token.xml106(td)
-#: ./doc/common/tables/cinder-auth_token.xml113(td)
-#: ./doc/common/tables/trove-auth_token.xml113(td)
-#: ./doc/common/tables/keystone-auth_token.xml113(td)
-#: ./doc/common/tables/ceilometer-auth.xml113(td)
-#: ./doc/common/tables/heat-auth_token.xml113(td)
-#: ./doc/common/tables/neutron-auth_token.xml113(td)
-msgid "memcache_security_strategy = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml114(td)
-#: ./doc/common/tables/nova-auth_token.xml107(td)
-#: ./doc/common/tables/cinder-auth_token.xml114(td)
-#: ./doc/common/tables/trove-auth_token.xml114(td)
-#: ./doc/common/tables/keystone-auth_token.xml114(td)
-#: ./doc/common/tables/ceilometer-auth.xml114(td)
-#: ./doc/common/tables/heat-auth_token.xml114(td)
-#: ./doc/common/tables/neutron-auth_token.xml114(td)
-msgid ""
-"(StrOpt) (optional) if defined, indicate whether token data should be "
-"authenticated or authenticated and encrypted. Acceptable values are MAC or "
-"ENCRYPT. If MAC, token data is authenticated (with HMAC) in the cache. If "
-"ENCRYPT, token data is encrypted and authenticated in the cache. If the "
-"value is not one of these options or empty, auth_token will raise an "
-"exception on initialization."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml118(td)
-#: ./doc/common/tables/nova-auth_token.xml111(td)
-#: ./doc/common/tables/cinder-auth_token.xml118(td)
-#: ./doc/common/tables/trove-auth_token.xml118(td)
-#: ./doc/common/tables/keystone-auth_token.xml118(td)
-#: ./doc/common/tables/ceilometer-auth.xml118(td)
-#: ./doc/common/tables/heat-auth_token.xml118(td)
-#: ./doc/common/tables/neutron-auth_token.xml118(td)
-msgid ""
-"(ListOpt) Optionally specify a list of memcached server(s) to use for "
-"caching. If left undefined, tokens will instead be cached in-process."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml121(td)
-#: ./doc/common/tables/nova-auth_token.xml114(td)
-#: ./doc/common/tables/cinder-auth_token.xml121(td)
-#: ./doc/common/tables/trove-auth_token.xml121(td)
-#: ./doc/common/tables/keystone-auth_token.xml121(td)
-#: ./doc/common/tables/ceilometer-auth.xml121(td)
-#: ./doc/common/tables/heat-auth_token.xml121(td)
-#: ./doc/common/tables/neutron-auth_token.xml121(td)
-msgid "revocation_cache_time = 300"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml122(td)
-#: ./doc/common/tables/nova-auth_token.xml115(td)
-#: ./doc/common/tables/cinder-auth_token.xml122(td)
-#: ./doc/common/tables/trove-auth_token.xml122(td)
-#: ./doc/common/tables/keystone-auth_token.xml122(td)
-#: ./doc/common/tables/ceilometer-auth.xml122(td)
-#: ./doc/common/tables/heat-auth_token.xml122(td)
-#: ./doc/common/tables/neutron-auth_token.xml122(td)
-msgid ""
-"(IntOpt) Determines the frequency at which the list of revoked tokens is "
-"retrieved from the Identity service (in seconds). A high number of "
-"revocation events combined with a low cache duration may significantly "
-"reduce performance."
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml125(td)
-#: ./doc/common/tables/nova-auth_token.xml118(td)
-#: ./doc/common/tables/cinder-auth_token.xml125(td)
-#: ./doc/common/tables/trove-auth_token.xml125(td)
-#: ./doc/common/tables/keystone-auth_token.xml125(td)
-#: ./doc/common/tables/ceilometer-auth.xml125(td)
-#: ./doc/common/tables/heat-auth_token.xml125(td)
-#: ./doc/common/tables/neutron-auth_token.xml125(td)
-msgid "signing_dir = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml126(td)
-#: ./doc/common/tables/nova-auth_token.xml119(td)
-#: ./doc/common/tables/cinder-auth_token.xml126(td)
-#: ./doc/common/tables/trove-auth_token.xml126(td)
-#: ./doc/common/tables/keystone-auth_token.xml126(td)
-#: ./doc/common/tables/ceilometer-auth.xml126(td)
-#: ./doc/common/tables/heat-auth_token.xml126(td)
-#: ./doc/common/tables/neutron-auth_token.xml126(td)
-msgid "(StrOpt) Directory used to cache files related to PKI tokens"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml129(td)
-#: ./doc/common/tables/nova-auth_token.xml122(td)
-#: ./doc/common/tables/cinder-auth_token.xml129(td)
-#: ./doc/common/tables/trove-auth_token.xml129(td)
-#: ./doc/common/tables/keystone-auth_token.xml129(td)
-#: ./doc/common/tables/ceilometer-auth.xml129(td)
-#: ./doc/common/tables/heat-auth_token.xml129(td)
-#: ./doc/common/tables/neutron-auth_token.xml129(td)
-msgid "token_cache_time = 300"
-msgstr ""
-
-#: ./doc/common/tables/glance-auth_token.xml130(td)
-#: ./doc/common/tables/nova-auth_token.xml123(td)
-#: ./doc/common/tables/cinder-auth_token.xml130(td)
-#: ./doc/common/tables/trove-auth_token.xml130(td)
-#: ./doc/common/tables/keystone-auth_token.xml130(td)
-#: ./doc/common/tables/ceilometer-auth.xml130(td)
-#: ./doc/common/tables/heat-auth_token.xml130(td)
-#: ./doc/common/tables/neutron-auth_token.xml130(td)
-msgid ""
-"(IntOpt) In order to prevent excessive effort spent validating tokens, the "
-"middleware caches previously-seen tokens for a configurable duration (in "
-"seconds). Set to -1 to disable caching completely."
-msgstr ""
-
-#: ./doc/common/tables/neutron-kombu.xml8(caption)
-#: ./doc/common/tables/nova-kombu.xml8(caption)
-msgid "Description of configuration options for kombu"
-msgstr ""
-
-#: ./doc/common/tables/neutron-kombu.xml23(td)
-#: ./doc/common/tables/heat-rabbitmq.xml23(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml27(td)
-#: ./doc/common/tables/trove-amqp.xml43(td)
-msgid "(StrOpt) SSL certification authority file (valid only if SSL enabled)"
-msgstr "(文字列オプション) SSL 認証局ファイル (SSL が有効化されているときのみ有効)。"
-
-#: ./doc/common/tables/neutron-kombu.xml27(td)
-#: ./doc/common/tables/heat-rabbitmq.xml27(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml31(td)
-#: ./doc/common/tables/trove-amqp.xml47(td)
-msgid "(StrOpt) SSL cert file (valid only if SSL enabled)"
-msgstr "(文字列オプション) SSL 証明書ファイル (SSL が有効化されているときのみ有効)。"
-
-#: ./doc/common/tables/neutron-kombu.xml31(td)
-#: ./doc/common/tables/heat-rabbitmq.xml31(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml35(td)
-#: ./doc/common/tables/trove-amqp.xml51(td)
-msgid "(StrOpt) SSL key file (valid only if SSL enabled)"
-msgstr "(文字列オプション) SSL キーファイル (SSL が有効化されているときのみ有効)。"
-
-#: ./doc/common/tables/neutron-kombu.xml35(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml39(td)
-msgid ""
-"(StrOpt) If SSL is enabled, the SSL version to use. Valid values are TLSv1, "
-"SSLv23 and SSLv3. SSLv2 might be available on some distributions."
-msgstr ""
-
-#: ./doc/common/tables/trove-redis.xml38(td)
-#: ./doc/common/tables/heat-rpc.xml62(td)
-#: ./doc/common/tables/ceilometer-redis.xml53(td)
-#: ./doc/common/tables/neutron-rpc.xml77(td)
-msgid "(StrOpt) Matchmaker ring file (JSON)"
-msgstr ""
-
-#: ./doc/common/tables/trove-qpid.xml23(td)
-#: ./doc/common/tables/heat-qpid.xml23(td)
-#: ./doc/common/tables/neutron-qpid.xml23(td)
-#: ./doc/common/tables/ceilometer-qpid.xml23(td)
-msgid "(IntOpt) Seconds between connection keepalive heartbeats"
-msgstr ""
-
-#: ./doc/common/tables/trove-qpid.xml27(td)
-#: ./doc/common/tables/heat-qpid.xml27(td)
-#: ./doc/common/tables/neutron-qpid.xml27(td)
-#: ./doc/common/tables/ceilometer-qpid.xml27(td)
-msgid "(StrOpt) Qpid broker hostname"
-msgstr "(文字列オプション) Qpid ブローカーのホスト名"
-
-#: ./doc/common/tables/trove-qpid.xml31(td)
-#: ./doc/common/tables/heat-qpid.xml31(td)
-#: ./doc/common/tables/neutron-qpid.xml31(td)
-#: ./doc/common/tables/ceilometer-qpid.xml31(td)
-msgid "(ListOpt) Qpid HA cluster host:port pairs"
-msgstr ""
-
-#: ./doc/common/tables/trove-qpid.xml35(td)
-#: ./doc/common/tables/heat-qpid.xml35(td)
-#: ./doc/common/tables/neutron-qpid.xml35(td)
-#: ./doc/common/tables/ceilometer-qpid.xml35(td)
-msgid "(StrOpt) Password for qpid connection"
-msgstr "(文字列オプション) qpid 接続のパスワード"
-
-#: ./doc/common/tables/trove-qpid.xml39(td)
-#: ./doc/common/tables/heat-qpid.xml39(td)
-#: ./doc/common/tables/neutron-qpid.xml39(td)
-#: ./doc/common/tables/ceilometer-qpid.xml39(td)
-msgid "(IntOpt) Qpid broker port"
-msgstr "(整数オプション) Qpid ブローカーのポート"
-
-#: ./doc/common/tables/trove-qpid.xml43(td)
-#: ./doc/common/tables/heat-qpid.xml43(td)
-#: ./doc/common/tables/neutron-qpid.xml43(td)
-#: ./doc/common/tables/ceilometer-qpid.xml43(td)
-msgid "(StrOpt) Transport to use, either 'tcp' or 'ssl'"
-msgstr "(文字列オプション) 使用する転送方式、'tcp' または 'ssl'"
-
-#: ./doc/common/tables/trove-qpid.xml47(td)
-#: ./doc/common/tables/heat-qpid.xml47(td)
-#: ./doc/common/tables/neutron-qpid.xml47(td)
-#: ./doc/common/tables/ceilometer-qpid.xml47(td)
-msgid "(StrOpt) Space separated list of SASL mechanisms to use for auth"
-msgstr "(文字列オプション) 認証に使用する SASL メカニズムの空白区切り一覧"
-
-#: ./doc/common/tables/trove-qpid.xml51(td)
-#: ./doc/common/tables/heat-qpid.xml51(td)
-#: ./doc/common/tables/neutron-qpid.xml51(td)
-#: ./doc/common/tables/ceilometer-qpid.xml51(td)
-msgid "(BoolOpt) Disable Nagle algorithm"
-msgstr "(論理値オプション) Nagle アルゴリズムの無効化"
-
-#: ./doc/common/tables/trove-qpid.xml55(td)
-#: ./doc/common/tables/heat-qpid.xml59(td)
-#: ./doc/common/tables/neutron-qpid.xml59(td)
-#: ./doc/common/tables/ceilometer-qpid.xml59(td)
-msgid "(StrOpt) Username for qpid connection"
-msgstr "(文字列オプション) qpid 接続のユーザー名"
-
-#: ./doc/common/tables/trove-compute.xml8(caption)
-#: ./doc/common/tables/neutron-compute.xml8(caption)
-#: ./doc/common/tables/cinder-compute.xml8(caption)
-#: ./doc/common/tables/nova-compute.xml8(caption)
-msgid "Description of configuration options for compute"
-msgstr ""
-
-#: ./doc/common/tables/trove-compute.xml22(td)
-msgid "ip_regex = None"
-msgstr ""
-
-#: ./doc/common/tables/trove-compute.xml26(td)
-msgid "nova_compute_url = http://localhost:8774/v2"
-msgstr ""
-
-#: ./doc/common/tables/trove-compute.xml30(td)
-msgid "root_grant = ALL"
-msgstr ""
-
-#: ./doc/common/tables/trove-compute.xml31(td)
-#: ./doc/common/tables/trove-api.xml23(td)
-#: ./doc/common/tables/trove-guestagent.xml43(td)
-#: ./doc/common/tables/trove-guestagent.xml47(td)
-msgid "(ListOpt) No help text available for this option."
-msgstr ""
-
-#: ./doc/common/tables/trove-compute.xml34(td)
-msgid "root_grant_option = True"
-msgstr ""
-
-#: ./doc/common/tables/trove-compute.xml35(td)
-#: ./doc/common/tables/trove-api.xml99(td)
-#: ./doc/common/tables/trove-taskmanager.xml71(td)
-#: ./doc/common/tables/trove-taskmanager.xml75(td)
-#: ./doc/common/tables/trove-database.xml31(td)
-#: ./doc/common/tables/trove-dns.xml83(td)
-msgid "(BoolOpt) No help text available for this option."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml7(literal)
-msgid "[filter:ratelimit]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml18(td)
-msgid "use = egg:swift#ratelimit"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml21(td)
-msgid "set log_name = ratelimit"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml36(td)
-msgid "clock_accuracy = 1000"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml36(td)
-msgid ""
-"Represents how accurate the proxy servers' system clocks are with each "
-"other. 1000 means that all the proxies' clock are accurate to each other "
-"within 1 millisecond. No ratelimit should be higher than the clock accuracy."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml39(td)
-msgid "max_sleep_time_seconds = 60"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml39(td)
-msgid ""
-"App will immediately return a 498 response if the necessary sleep time ever "
-"exceeds the given max_sleep_time_seconds."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml42(td)
-msgid "log_sleep_time_seconds = 0"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml42(td)
-msgid ""
-"To allow visibility into rate limiting set this value &gt; 0 and all sleeps "
-"greater than the number will be logged."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml45(td)
-msgid "rate_buffer_seconds = 5"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml45(td)
-msgid ""
-"Number of seconds the rate counter can drop and be allowed to catch up (at a"
-" faster than listed rate). A larger number will result in larger spikes in "
-"rate but better average accuracy."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml48(td)
-msgid "account_ratelimit = 0"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml48(td)
-msgid ""
-"If set, will limit PUT and DELETE requests to /account_name/container_name. "
-"Number is in requests per second."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml51(td)
-msgid "account_whitelist = a,b"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml51(td)
-msgid "Comma separated lists of account names that will not be rate limited."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml54(td)
-msgid "account_blacklist = c,d"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml54(td)
-msgid ""
-"Comma separated lists of account names that will not be allowed. Returns a "
-"497 response. r: for containers of size x, limit requests per second to r. "
-"Will limit PUT, DELETE, and POST requests to /a/c/o. "
-"container_listing_ratelimit_x = r: for containers of size x, limit listing "
-"requests per second to r. Will limit GET requests to /a/c."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml57(td)
-msgid "with container_limit_x = r"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml60(td)
-msgid "container_ratelimit_0 = 100"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml63(td)
-msgid "container_ratelimit_10 = 50"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml66(td)
-msgid "container_ratelimit_50 = 20"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml69(td)
-msgid "container_listing_ratelimit_0 = 100"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml72(td)
-msgid "container_listing_ratelimit_10 = 50"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml75(td)
-msgid "container_listing_ratelimit_50 = 20"
-msgstr ""
-
-#: ./doc/common/tables/trove-nova.xml8(caption)
-msgid "Description of configuration options for nova"
-msgstr ""
-
-#: ./doc/common/tables/trove-nova.xml22(td)
-msgid "nova_proxy_admin_pass ="
-msgstr ""
-
-#: ./doc/common/tables/trove-nova.xml23(td)
-msgid "(StrOpt) Admin password used to connect to nova,"
-msgstr ""
-
-#: ./doc/common/tables/trove-nova.xml26(td)
-msgid "nova_proxy_admin_tenant_name ="
-msgstr ""
-
-#: ./doc/common/tables/trove-nova.xml27(td)
-msgid "(StrOpt) Admin tenant used to connect to nova."
-msgstr ""
-
-#: ./doc/common/tables/trove-nova.xml30(td)
-msgid "nova_proxy_admin_user ="
-msgstr ""
-
-#: ./doc/common/tables/trove-nova.xml31(td)
-msgid "(StrOpt) Admin username used to connect to nova."
+#: ./doc/common/tables/ceilometer-cells.xml8(caption)
+#: ./doc/common/tables/nova-cells.xml8(caption)
+msgid "Description of configuration options for cells"
 msgstr ""
 
 #: ./doc/common/tables/ceilometer-cells.xml22(td)
@@ -31768,696 +36323,99 @@ msgstr ""
 msgid "(IntOpt) Seconds between bandwidth updates for cells."
 msgstr ""
 
-#: ./doc/common/tables/keystone-oauth.xml8(caption)
-msgid "Description of configuration options for oauth"
+#: ./doc/common/tables/ceilometer-cells.xml26(td)
+#: ./doc/common/tables/nova-cells.xml22(td)
+msgid "call_timeout = 60"
 msgstr ""
 
-#: ./doc/common/tables/keystone-oauth.xml19(th)
-msgid "[oauth1]"
+#: ./doc/common/tables/ceilometer-cells.xml27(td)
+#: ./doc/common/tables/nova-cells.xml23(td)
+msgid "(IntOpt) Seconds to wait for response from a call to a cell."
 msgstr ""
 
-#: ./doc/common/tables/keystone-oauth.xml22(td)
-msgid "access_token_duration = 86400"
+#: ./doc/common/tables/ceilometer-cells.xml30(td)
+#: ./doc/common/tables/nova-cells.xml26(td)
+msgid "capabilities = hypervisor=xenserver;kvm, os=linux;windows"
 msgstr ""
 
-#: ./doc/common/tables/keystone-oauth.xml23(td)
-msgid "(IntOpt) Duration (in seconds) for the OAuth Access Token."
+#: ./doc/common/tables/ceilometer-cells.xml31(td)
+#: ./doc/common/tables/nova-cells.xml27(td)
+msgid "(ListOpt) Key/Multi-value list with the capabilities of the cell"
 msgstr ""
 
-#: ./doc/common/tables/keystone-oauth.xml26(td)
-msgid "driver = keystone.contrib.oauth1.backends.sql.OAuth1"
+#: ./doc/common/tables/ceilometer-cells.xml34(td)
+#: ./doc/common/tables/nova-cells.xml30(td)
+msgid "cell_type = compute"
 msgstr ""
 
-#: ./doc/common/tables/keystone-oauth.xml27(td)
-#: ./doc/common/tables/keystone-credential.xml23(td)
-msgid "(StrOpt) Keystone Credential backend driver."
+#: ./doc/common/tables/ceilometer-cells.xml35(td)
+#: ./doc/common/tables/nova-cells.xml31(td)
+msgid "(StrOpt) Type of cell: api or compute"
 msgstr ""
 
-#: ./doc/common/tables/keystone-oauth.xml30(td)
-msgid "request_token_duration = 28800"
+#: ./doc/common/tables/ceilometer-cells.xml38(td)
+#: ./doc/common/tables/nova-cells.xml42(td)
+#: ./doc/common/tables/keystone-ssl.xml77(td)
+msgid "enable = False"
 msgstr ""
 
-#: ./doc/common/tables/keystone-oauth.xml31(td)
-msgid "(IntOpt) Duration (in seconds) for the OAuth Request Token."
+#: ./doc/common/tables/ceilometer-cells.xml39(td)
+#: ./doc/common/tables/nova-cells.xml43(td)
+msgid "(BoolOpt) Enable cell functionality"
 msgstr ""
 
-#: ./doc/common/tables/cinder-block-device.xml8(caption)
-msgid "Description of configuration options for block-device"
+#: ./doc/common/tables/ceilometer-cells.xml42(td)
+#: ./doc/common/tables/nova-cells.xml54(td)
+msgid "manager = nova.cells.manager.CellsManager"
 msgstr ""
 
-#: ./doc/common/tables/cinder-block-device.xml22(td)
-msgid "available_devices ="
+#: ./doc/common/tables/ceilometer-cells.xml43(td)
+#: ./doc/common/tables/nova-cells.xml55(td)
+msgid "(StrOpt) Manager for cells"
 msgstr ""
 
-#: ./doc/common/tables/cinder-block-device.xml23(td)
-msgid "(ListOpt) List of all available devices"
+#: ./doc/common/tables/ceilometer-cells.xml46(td)
+#: ./doc/common/tables/nova-cells.xml62(td)
+msgid "mute_child_interval = 300"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zones.xml8(caption)
-msgid "Description of configuration options for zones"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zones.xml22(td)
-msgid "cloned_volume_same_az = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zones.xml23(td)
+#: ./doc/common/tables/ceilometer-cells.xml47(td)
+#: ./doc/common/tables/nova-cells.xml63(td)
 msgid ""
-"(BoolOpt) Ensure that the new volumes are the same AZ as snapshot or source "
-"volume"
+"(IntOpt) Number of seconds after which a lack of capability and capacity "
+"updates signals the child cell is to be treated as a mute."
 msgstr ""
 
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml8(caption)
-msgid "Description of configuration options for netapp_7mode_iscsi"
+#: ./doc/common/tables/ceilometer-cells.xml50(td)
+#: ./doc/common/tables/nova-cells.xml74(td)
+msgid "name = nova"
 msgstr ""
 
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml38(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml38(td)
-msgid "netapp_size_multiplier = 1.2"
+#: ./doc/common/tables/ceilometer-cells.xml51(td)
+#: ./doc/common/tables/nova-cells.xml75(td)
+msgid "(StrOpt) Name of this cell"
 msgstr ""
 
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml39(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml39(td)
+#: ./doc/common/tables/ceilometer-cells.xml54(td)
+#: ./doc/common/tables/nova-cells.xml82(td)
+msgid "reserve_percent = 10.0"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-cells.xml55(td)
+#: ./doc/common/tables/nova-cells.xml83(td)
 msgid ""
-"(FloatOpt) The quantity to be multiplied by the requested volume size to "
-"ensure enough space is available on the virtual storage server (Vserver) to "
-"fulfill the volume creation request."
+"(FloatOpt) Percentage of cell capacity to hold in reserve. Affects both "
+"memory and disk utilization"
 msgstr ""
 
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml46(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml46(td)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml46(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml50(td)
-msgid "netapp_storage_protocol = None"
+#: ./doc/common/tables/ceilometer-cells.xml58(td)
+#: ./doc/common/tables/nova-cells.xml86(td)
+msgid "topic = cells"
 msgstr ""
 
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml47(td)
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml47(td)
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml47(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml51(td)
-msgid ""
-"(StrOpt) The storage protocol to be used on the data path with the storage "
-"system; valid values are iscsi or nfs."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml54(td)
-msgid "netapp_vfiler = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml55(td)
-msgid ""
-"(StrOpt) The vFiler unit on which provisioning of block storage volumes will"
-" be done. This option is only used by the driver when connecting to an "
-"instance with a storage family of Data ONTAP operating in 7-Mode and the "
-"storage protocol selected is iSCSI. Only use this option when utilizing the "
-"MultiStore feature on the NetApp storage system."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml58(td)
-msgid "netapp_volume_list = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml59(td)
-msgid ""
-"(StrOpt) This option is only utilized when the storage protocol is "
-"configured to use iSCSI. This option is used to restrict provisioning to the"
-" specified controller volumes. Specify the value of this option to be a "
-"comma separated list of NetApp controller volume names to be used for "
-"provisioning."
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-sync.xml7(literal)
-msgid "[container-sync]"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-sync.xml18(td)
-msgid "log_name = container-sync"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-sync.xml30(td)
-msgid "sync_proxy = http://10.1.1.1:8888,http://10.1.1.2:8888"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-sync.xml30(td)
-msgid "If you need to use an HTTP proxy, set it here. Defaults to no proxy."
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-sync.xml36(td)
-msgid "container_time = 60"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-sync.xml36(td)
-msgid "Maximum amount of time to spend syncing each container"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml8(caption)
-#: ./doc/common/tables/nova-common.xml8(caption)
-#: ./doc/common/tables/glance-common.xml8(caption)
-#: ./doc/common/tables/cinder-common.xml8(caption)
-#: ./doc/common/tables/trove-common.xml8(caption)
-#: ./doc/common/tables/ceilometer-common.xml8(caption)
-#: ./doc/common/tables/heat-common.xml8(caption)
-msgid "Description of configuration options for common"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml23(td)
-#: ./doc/common/tables/neutron-common.xml193(td)
-msgid "(StrOpt) Admin password"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml26(td)
-#: ./doc/common/tables/neutron-common.xml196(td)
-#: ./doc/common/tables/glance-registry.xml26(td)
-msgid "admin_tenant_name = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml27(td)
-#: ./doc/common/tables/neutron-common.xml197(td)
-msgid "(StrOpt) Admin tenant name"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml31(td)
-msgid "(StrOpt) Admin username"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml34(td)
-msgid "agent_down_time = 75"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml35(td)
-msgid ""
-"(IntOpt) Seconds to regard the agent is down; should be at least twice "
-"report_interval, to be sure the agent is down for good."
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml38(td)
-#: ./doc/common/tables/heat-rpc.xml22(td)
-#: ./doc/common/tables/ceilometer-rpc.xml22(td)
-#: ./doc/common/tables/trove-rpc.xml22(td)
-msgid ""
-"allowed_rpc_exception_modules = nova.exception, cinder.exception, exceptions"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml39(td)
-#: ./doc/common/tables/heat-rpc.xml23(td)
-#: ./doc/common/tables/nova-testing.xml23(td)
-#: ./doc/common/tables/cinder-rpc.xml23(td)
-#: ./doc/common/tables/keystone-rpc.xml23(td)
-#: ./doc/common/tables/ceilometer-rpc.xml23(td)
-msgid ""
-"(ListOpt) Modules of exceptions that are permitted to be recreated upon "
-"receiving exception data from an rpc call."
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml42(td)
-msgid "api_workers = 0"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml43(td)
-msgid "(IntOpt) Number of separate worker processes for service"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml46(td)
-msgid "auth_ca_cert = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml47(td)
-msgid "(StrOpt) Certificate Authority public key (CA cert) file for ssl"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml50(td)
-msgid "auth_insecure = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml51(td)
-msgid "(BoolOpt) Turn off verification of the certificate for ssl"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml54(td)
-#: ./doc/common/tables/neutron-common.xml204(td)
-#: ./doc/common/tables/glance-registry.xml34(td)
-msgid "auth_region = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml55(td)
-#: ./doc/common/tables/neutron-common.xml205(td)
-msgid "(StrOpt) Authentication region"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml58(td)
-#: ./doc/common/tables/neutron-common.xml208(td)
-#: ./doc/common/tables/ceilometer-auth.xml22(td)
-msgid "auth_strategy = keystone"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml59(td)
-#: ./doc/common/tables/neutron-common.xml209(td)
-msgid "(StrOpt) The type of authentication to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml62(td)
-#: ./doc/common/tables/neutron-common.xml212(td)
-#: ./doc/common/tables/glance-registry.xml42(td)
-msgid "auth_url = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml63(td)
-#: ./doc/common/tables/neutron-common.xml213(td)
-msgid "(StrOpt) Authentication URL"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml66(td)
-msgid "base_mac = fa:16:3e:00:00:00"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml67(td)
-msgid "(StrOpt) The base MAC address Neutron will use for VIFs"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml70(td)
-#: ./doc/common/tables/heat-cfn_api.xml37(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml33(td)
-#: ./doc/common/tables/glance-common.xml34(td)
-#: ./doc/common/tables/heat-api.xml107(td)
-msgid "bind_host = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml71(td)
-msgid "(StrOpt) The host IP to bind to"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml74(td)
-msgid "bind_port = 9696"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml75(td)
-msgid "(IntOpt) The port to bind to"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml78(td)
-msgid "ca_certs = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml79(td)
-msgid "(StrOpt) CA certificates"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml82(td)
-msgid "core_plugin = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml83(td)
-msgid "(StrOpt) The core plugin Neutron will use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml86(td)
-msgid "ctl_cert = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml87(td)
-msgid "(StrOpt) controller certificate"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml90(td)
-msgid "ctl_privkey = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml91(td)
-msgid "(StrOpt) controller private key"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml94(td)
-msgid "dhcp_agent_notification = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml95(td)
-msgid "(BoolOpt) Allow sending resource operation notification to DHCP agent"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml98(td)
-msgid "dhcp_agents_per_network = 1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml99(td)
-msgid "(IntOpt) Number of DHCP agents scheduled to host a network."
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml102(td)
-msgid "dhcp_confs = $state_path/dhcp"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml103(td)
-msgid "(StrOpt) Location to store DHCP server config files"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml106(td)
-msgid "dhcp_delete_namespaces = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml107(td)
-msgid "(BoolOpt) Delete namespace after removing a dhcp server."
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml110(td)
-msgid "dhcp_domain = openstacklocal"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml111(td)
-#: ./doc/common/tables/nova-network.xml51(td)
-#: ./doc/common/tables/neutron-vmware.xml120(td)
-msgid "(StrOpt) Domain to use for building the hostnames"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml114(td)
-msgid "dhcp_driver = neutron.agent.linux.dhcp.Dnsmasq"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml115(td)
-msgid "(StrOpt) The driver used to manage the DHCP server."
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml118(td)
-msgid "dhcp_lease_duration = 86400"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml119(td)
-msgid "(IntOpt) DHCP lease duration"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml126(td)
-msgid "endpoint_type = adminURL"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml127(td)
-msgid ""
-"(StrOpt) Network service endpoint type to pull from the keystone catalog"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml130(td)
-msgid "force_gateway_on_subnet = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml131(td)
-msgid "(BoolOpt) Ensure that configured gateway is on subnet"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml134(td)
-msgid "interface_driver = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml135(td)
-msgid "(StrOpt) The driver used to manage the virtual interface."
-msgstr "(文字列オプション) 仮想インターフェースを管理するために使用するドライバー。"
-
-#: ./doc/common/tables/neutron-common.xml138(td)
-msgid "ip_lib_force_root = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml139(td)
-msgid "(BoolOpt) Force ip_lib calls to use the root helper"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml142(td)
-#: ./doc/common/tables/nova-common.xml46(td)
-#: ./doc/common/tables/heat-debug.xml38(td)
-#: ./doc/common/tables/glance-common.xml70(td)
-#: ./doc/common/tables/cinder-common.xml70(td)
-#: ./doc/common/tables/trove-common.xml58(td)
-#: ./doc/common/tables/ceilometer-common.xml34(td)
-#: ./doc/common/tables/keystone-misc.xml22(td)
-msgid "lock_path = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml143(td)
-#: ./doc/common/tables/nova-common.xml47(td)
-#: ./doc/common/tables/heat-debug.xml39(td)
-#: ./doc/common/tables/glance-common.xml71(td)
-#: ./doc/common/tables/trove-common.xml59(td)
-#: ./doc/common/tables/ceilometer-common.xml35(td)
-#: ./doc/common/tables/keystone-misc.xml23(td)
-msgid "(StrOpt) Directory to use for lock files."
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml146(td)
-msgid "mac_generation_retries = 16"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml147(td)
-msgid "(IntOpt) How many times Neutron will retry MAC generation"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml150(td)
-msgid "max_dns_nameservers = 5"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml151(td)
-msgid "(IntOpt) Maximum number of DNS nameservers"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml154(td)
-msgid "max_fixed_ips_per_port = 5"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml155(td)
-msgid "(IntOpt) Maximum number of fixed ips per port"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml158(td)
-msgid "max_subnet_host_routes = 20"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml159(td)
-msgid "(IntOpt) Maximum number of host routes per subnet"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml162(td)
-msgid "periodic_fuzzy_delay = 5"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml163(td)
-#: ./doc/common/tables/nova-periodic.xml27(td)
-msgid ""
-"(IntOpt) Range of seconds to randomly delay when starting the periodic task "
-"scheduler to reduce stampeding. (Disable by setting to 0)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml166(td)
-msgid "periodic_interval = 40"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml167(td)
-msgid "(IntOpt) Seconds between running periodic tasks"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml170(td)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml27(td)
-msgid "report_interval = 300"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml171(td)
-msgid "(IntOpt) Interval between two metering reports"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml174(td)
-#: ./doc/common/tables/neutron-common.xml185(td)
-#: ./doc/common/tables/neutron-sdnve.xml89(td)
-msgid "root_helper = sudo"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml175(td)
-#: ./doc/common/tables/neutron-common.xml186(td)
-msgid "(StrOpt) Root helper application."
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml178(td)
-msgid "state_path = /var/lib/neutron"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml179(td)
-msgid ""
-"(StrOpt) Where to store Neutron state files. This directory must be writable"
-" by the agent."
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml182(th)
-#: ./doc/common/tables/neutron-openvswitch_agent.xml34(th)
-#: ./doc/common/tables/neutron-metering_agent.xml30(th)
-#: ./doc/common/tables/neutron-ml2_ofa.xml34(th)
-#: ./doc/common/tables/neutron-hyperv_agent.xml19(th)
-#: ./doc/common/tables/neutron-rpc.xml66(th)
-#: ./doc/common/tables/neutron-nvsd.xml19(th)
-msgid "[AGENT]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml189(th)
-msgid "[PROXY]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml201(td)
-msgid "(StrOpt) Admin user"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml216(th)
-#: ./doc/common/tables/neutron-embrane.xml19(th)
-msgid "[heleos]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-common.xml220(td)
-#: ./doc/common/tables/neutron-embrane_lb.xml23(td)
-msgid "(StrOpt) ESM admin password."
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml22(td)
-msgid "notify_nova_on_port_data_changes = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml23(td)
-msgid ""
-"(BoolOpt) Send notification to nova when port data (fixed_ips/floatingip) "
-"changes so nova can update its cache."
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml26(td)
-msgid "notify_nova_on_port_status_changes = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml27(td)
-msgid "(BoolOpt) Send notification to nova when port status changes"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml30(td)
-msgid "nova_admin_auth_url = http://localhost:5000/v2.0"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml31(td)
-msgid "(StrOpt) Authorization URL for connecting to nova in admin context"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml34(td)
-msgid "nova_admin_password = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml35(td)
-msgid "(StrOpt) Password for connection to nova in admin context"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml38(td)
-msgid "nova_admin_tenant_id = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml39(td)
-msgid "(StrOpt) The uuid of the admin nova tenant"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml42(td)
-msgid "nova_admin_username = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml43(td)
-msgid "(StrOpt) Username for connecting to nova in admin context"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml46(td)
-msgid "nova_region_name = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml47(td)
-msgid ""
-"(StrOpt) Name of nova region to use. Useful if keystone manages more than "
-"one region."
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml50(td)
-msgid "nova_url = http://127.0.0.1:8774"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml51(td)
-msgid "(StrOpt) URL for connection to nova"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml54(td)
-msgid "send_events_interval = 2"
-msgstr ""
-
-#: ./doc/common/tables/neutron-compute.xml55(td)
-msgid ""
-"(IntOpt) Number of seconds between sending events to nova if there are any "
-"events to send."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml7(literal)
-msgid "[object-auditor]"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml7(literal)
-#: ./doc/common/tables/swift-object-server-object-updater.xml7(literal)
-#: ./doc/common/tables/swift-object-server-pipeline-main.xml7(literal)
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml7(literal)
-#: ./doc/common/tables/swift-object-server-filter-recon.xml7(literal)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml7(literal)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml7(literal)
-#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml7(literal)
-msgid "object-server.conf-sample"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml18(td)
-msgid "log_name = object-auditor"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml30(td)
-msgid "files_per_second = 20"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml30(td)
-msgid ""
-"Maximum files audited per second. Should be tuned according to individual "
-"system specs. 0 is unlimited."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml33(td)
-msgid "bytes_per_second = 10000000"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml33(td)
-msgid ""
-"Maximum bytes audited per second. Should be tuned according to individual "
-"system specs. 0 is unlimited. mounted to prevent accidentally writing to the"
-" root device process simultaneously (it will actually accept(2) N + 1). "
-"Setting this to one (1) will only handle one request at a time, without "
-"accepting another request concurrently. By increasing the number of workers "
-"to a much higher value, one can reduce the impact of slow file system "
-"operations in one request from negatively impacting other requests. "
-"underlying filesystem does not support it. to setup custom log handlers. "
-"bytes you'd like fallocate to reserve, whether there is space for the given "
-"file size or not. This is useful for systems that behave badly when they "
-"completely run out of space; you can make the services pretend they're out "
-"of space early. container server. For most cases, this should be "
-"`egg:swift#container`."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml36(td)
-msgid "log_time = 3600"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml36(td)
-msgid "Frequency of status logs in seconds."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml39(td)
-msgid "zero_byte_files_per_second = 50"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml39(td)
-msgid "Maximum zero byte files audited per second."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-auditor.xml45(td)
-msgid "object_size_stats ="
-msgstr ""
-
-#: ./doc/common/tables/keystone-ldap.xml8(caption)
-#: ./doc/common/tables/nova-ldap.xml8(caption)
-msgid "Description of configuration options for ldap"
+#: ./doc/common/tables/ceilometer-cells.xml59(td)
+#: ./doc/common/tables/nova-cells.xml87(td)
+msgid "(StrOpt) The topic cells nodes listen on"
 msgstr ""
 
 #: ./doc/common/tables/keystone-ldap.xml19(th)
@@ -33083,2970 +37041,6 @@ msgstr ""
 msgid "(StrOpt) Search base for users."
 msgstr ""
 
-#: ./doc/common/tables/heat-rpc.xml8(caption)
-#: ./doc/common/tables/cinder-rpc.xml8(caption)
-#: ./doc/common/tables/keystone-rpc.xml8(caption)
-#: ./doc/common/tables/glance-rpc.xml8(caption)
-#: ./doc/common/tables/ceilometer-rpc.xml8(caption)
-#: ./doc/common/tables/neutron-rpc.xml8(caption)
-#: ./doc/common/tables/trove-rpc.xml8(caption)
-#: ./doc/common/tables/nova-rpc.xml8(caption)
-msgid "Description of configuration options for rpc"
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml26(td)
-msgid "engine_life_check_timeout = 2"
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml27(td)
-msgid ""
-"(IntOpt) RPC timeout for the engine liveness check that is used for stack "
-"locking."
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml31(td)
-#: ./doc/common/tables/ceilometer-redis.xml27(td)
-#: ./doc/common/tables/neutron-rpc.xml35(td)
-#: ./doc/common/tables/trove-rpc.xml31(td)
-msgid "(IntOpt) Heartbeat frequency"
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml38(td)
-msgid "rpc_backend = heat.openstack.common.rpc.impl_kombu"
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml39(td)
-#: ./doc/common/tables/ceilometer-rpc.xml31(td)
-#: ./doc/common/tables/neutron-rpc.xml43(td)
-#: ./doc/common/tables/trove-rpc.xml51(td)
-msgid "(StrOpt) The messaging module to use, defaults to kombu."
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml47(td)
-#: ./doc/common/tables/ceilometer-rpc.xml39(td)
-#: ./doc/common/tables/neutron-rpc.xml51(td)
-#: ./doc/common/tables/trove-rpc.xml59(td)
-msgid "(IntOpt) Size of RPC connection pool"
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml51(td)
-#: ./doc/common/tables/ceilometer-rpc.xml43(td)
-#: ./doc/common/tables/neutron-rpc.xml55(td)
-#: ./doc/common/tables/trove-rpc.xml63(td)
-msgid "(IntOpt) Seconds to wait for a response from call or multicall"
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml55(td)
-#: ./doc/common/tables/ceilometer-rpc.xml47(td)
-#: ./doc/common/tables/neutron-rpc.xml59(td)
-#: ./doc/common/tables/trove-rpc.xml67(td)
-msgid "(IntOpt) Size of RPC thread pool"
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml65(th)
-#: ./doc/common/tables/ceilometer-rpc.xml92(th)
-#: ./doc/common/tables/neutron-rpc.xml80(th)
-#: ./doc/common/tables/trove-rpc.xml70(th)
-msgid "[rpc_notifier2]"
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml68(td)
-#: ./doc/common/tables/ceilometer-rpc.xml95(td)
-#: ./doc/common/tables/neutron-rpc.xml83(td)
-#: ./doc/common/tables/trove-rpc.xml73(td)
-msgid "topics = notifications"
-msgstr ""
-
-#: ./doc/common/tables/heat-rpc.xml69(td)
-#: ./doc/common/tables/ceilometer-rpc.xml96(td)
-msgid "(ListOpt) AMQP topic(s) used for OpenStack notifications"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml8(caption)
-msgid "Description of configuration options for openvswitch_agent"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml22(td)
-msgid "ovs_integration_bridge = br-int"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml23(td)
-msgid "(StrOpt) Name of Open vSwitch bridge to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml26(td)
-msgid "ovs_use_veth = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml27(td)
-msgid "(BoolOpt) Uses veth for an interface or not"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml30(td)
-msgid "ovs_vsctl_timeout = 10"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml31(td)
-msgid "(IntOpt) Timeout in seconds for ovs-vsctl commands"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml37(td)
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml44(td)
-msgid "l2_population = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml38(td)
-msgid ""
-"(BoolOpt) Use ml2 l2population mechanism driver to learn remote mac and IPs "
-"and improve tunnel scalability"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml41(td)
-msgid "minimize_polling = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml42(td)
-msgid "(BoolOpt) Minimize polling by monitoring ovsdb for interface changes."
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml45(td)
-msgid "ovsdb_monitor_respawn_interval = 30"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml46(td)
-msgid ""
-"(IntOpt) The number of seconds to wait before respawning the ovsdb monitor "
-"after losing communication with it"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml49(td)
-msgid "tunnel_types ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml50(td)
-msgid "(ListOpt) Network types supported by the agent (gre and/or vxlan)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml53(td)
-msgid "veth_mtu = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml54(td)
-msgid "(IntOpt) MTU size of veth interfaces"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml57(td)
-msgid "vxlan_udp_port = 4789"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml58(td)
-msgid "(IntOpt) The UDP port to use for VXLAN tunnels."
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml61(th)
-#: ./doc/common/tables/neutron-cisco.xml54(th)
-msgid "[CISCO_N1K]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml64(td)
-msgid "local_ip = 10.0.0.3"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml65(td)
-msgid "(StrOpt) N1K Local IP"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml68(th)
-#: ./doc/common/tables/neutron-ryu.xml19(th)
-msgid "[OVS]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml71(td)
-#: ./doc/common/tables/neutron-cisco.xml57(td)
-msgid "bridge_mappings ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml72(td)
-msgid "(ListOpt) List of &lt;physical_network&gt;:&lt;bridge&gt;"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml75(td)
-msgid "enable_tunneling = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml76(td)
-msgid "(BoolOpt) Enable tunneling support"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml79(td)
-msgid "int_peer_patch_port = patch-tun"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml80(td)
-msgid "(StrOpt) Peer patch port in integration bridge for tunnel bridge"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml84(td)
-#: ./doc/common/tables/neutron-sdnve.xml43(td)
-msgid "(StrOpt) Integration bridge to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml87(td)
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml48(td)
-msgid "local_ip ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml88(td)
-msgid "(StrOpt) Local IP address of GRE tunnel endpoints."
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml91(td)
-#: ./doc/common/tables/neutron-ml2_vlan.xml22(td)
-#: ./doc/common/tables/neutron-hyperv_agent.xml45(td)
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml29(td)
-msgid "network_vlan_ranges ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml95(td)
-#: ./doc/common/tables/neutron-hyperv_agent.xml49(td)
-#: ./doc/common/tables/neutron-cisco.xml89(td)
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml33(td)
-msgid "tenant_network_type = local"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml96(td)
-msgid ""
-"(StrOpt) Network type for tenant networks (local, vlan, gre, vxlan, or none)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml99(td)
-msgid "tun_peer_patch_port = patch-int"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml100(td)
-msgid "(StrOpt) Peer patch port in tunnel bridge for integration bridge"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml103(td)
-#: ./doc/common/tables/neutron-cisco.xml93(td)
-msgid "tunnel_bridge = br-tun"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml104(td)
-msgid "(StrOpt) Tunnel bridge to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml108(td)
-msgid "(ListOpt) List of &lt;tun_min&gt;:&lt;tun_max&gt;"
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml111(td)
-msgid "tunnel_type ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-openvswitch_agent.xml112(td)
-msgid ""
-"(StrOpt) The type of tunnels to use when utilizing tunnels, either 'gre' or "
-"'vxlan'"
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml22(td)
-msgid "nova_api_insecure = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml23(td)
-msgid "(BoolOpt) Allow to perform insecure SSL requests to nova"
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml26(td)
-msgid "nova_ca_certificates_file = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml27(td)
-msgid ""
-"(StrOpt) Location of ca certificates file to use for nova client requests."
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml30(td)
-msgid "nova_catalog_admin_info = compute:nova:adminURL"
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml31(td)
-msgid "(StrOpt) Same as nova_catalog_info, but for admin endpoint."
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml34(td)
-msgid "nova_catalog_info = compute:nova:publicURL"
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml35(td)
-msgid ""
-"(StrOpt) Info to match when looking for nova in the service catalog. Format "
-"is : separated values of the form: "
-"&lt;service_type&gt;:&lt;service_name&gt;:&lt;endpoint_type&gt;"
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml38(td)
-msgid "nova_endpoint_admin_template = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml39(td)
-msgid "(StrOpt) Same as nova_endpoint_template, but for admin endpoint."
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml42(td)
-msgid "nova_endpoint_template = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml43(td)
-msgid ""
-"(StrOpt) Override service catalog lookup with template for nova endpoint "
-"e.g. http://localhost:8774/v2/%(project_id)s"
-msgstr ""
-
-#: ./doc/common/tables/cinder-compute.xml47(td)
-msgid "(StrOpt) region name of this node"
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml8(caption)
-msgid "Description of configuration options for identity"
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml19(th)
-msgid "[identity]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml22(td)
-msgid "default_domain_id = default"
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml23(td)
-msgid ""
-"(StrOpt) This references the domain to use for all Identity API v2 requests "
-"(which are not aware of domains). A domain with this ID will be created for "
-"you by keystone-manage db_sync in migration 008. The domain referenced by "
-"this ID cannot be deleted on the v3 API, to prevent accidentally breaking "
-"the v2 API. There is nothing special about this domain, other than the fact "
-"that it must exist to order to maintain support for your v2 clients."
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml26(td)
-msgid "domain_config_dir = /etc/keystone/domains"
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml27(td)
-msgid ""
-"(StrOpt) Path for Keystone to locate the domain specificidentity "
-"configuration files if domain_specific_drivers_enabled is set to true."
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml30(td)
-msgid "domain_specific_drivers_enabled = False"
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml31(td)
-msgid ""
-"(BoolOpt) A subset (or all) of domains can have their own identity driver, "
-"each with their own partial configuration file in a domain configuration "
-"directory. Only values specific to the domain need to be placed in the "
-"domain specific configuration file. This feature is disabled by default; set"
-" to True to enable."
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml34(td)
-msgid "driver = keystone.identity.backends.sql.Identity"
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml35(td)
-msgid "(StrOpt) Keystone Identity backend driver."
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml38(td)
-#: ./doc/common/tables/keystone-assignment.xml34(td)
-#: ./doc/common/tables/keystone-catalog.xml26(td)
-#: ./doc/common/tables/keystone-policy.xml37(td)
-#: ./doc/common/tables/keystone-api.xml46(td)
-msgid "list_limit = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml39(td)
-msgid ""
-"(IntOpt) Maximum number of entities that will be returned in an identity "
-"collection."
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml42(td)
-msgid "max_password_length = 4096"
-msgstr ""
-
-#: ./doc/common/tables/keystone-identity.xml43(td)
-msgid ""
-"(IntOpt) Maximum supported length for user passwords; decrease to improve "
-"performance."
-msgstr ""
-
-#: ./doc/common/tables/cinder-lvm.xml8(caption)
-msgid "Description of configuration options for lvm"
-msgstr ""
-
-#: ./doc/common/tables/cinder-lvm.xml22(td)
-msgid "lvm_mirrors = 0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-lvm.xml23(td)
-msgid ""
-"(IntOpt) If set, create lvms with multiple mirrors. Note that this requires "
-"lvm_mirrors + 2 pvs with available space"
-msgstr ""
-
-#: ./doc/common/tables/cinder-lvm.xml26(td)
-msgid "lvm_type = default"
-msgstr ""
-
-#: ./doc/common/tables/cinder-lvm.xml27(td)
-msgid "(StrOpt) Type of LVM volumes to deploy; (default or thin)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-lvm.xml30(td)
-msgid "volume_group = cinder-volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-lvm.xml31(td)
-msgid "(StrOpt) Name for the VG that will contain exported volumes"
-msgstr ""
-
-#: ./doc/common/tables/keystone-trust.xml8(caption)
-msgid "Description of configuration options for trust"
-msgstr ""
-
-#: ./doc/common/tables/keystone-trust.xml19(th)
-msgid "[trust]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-trust.xml22(td)
-msgid "driver = keystone.trust.backends.sql.Trust"
-msgstr ""
-
-#: ./doc/common/tables/keystone-trust.xml23(td)
-msgid "(StrOpt) Keystone Trust backend driver."
-msgstr ""
-
-#: ./doc/common/tables/keystone-trust.xml26(td)
-#: ./doc/common/tables/trove-rpc.xml80(td)
-msgid "enabled = True"
-msgstr ""
-
-#: ./doc/common/tables/keystone-trust.xml27(td)
-msgid ""
-"(BoolOpt) delegation and impersonation features can be optionally disabled."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_nfs.xml8(caption)
-msgid "Description of configuration options for storage_nfs"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_nfs.xml23(td)
-msgid ""
-"(StrOpt) Mount options passed to the nfs client. See section of the nfs man "
-"page for details."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_nfs.xml27(td)
-msgid "(StrOpt) Base dir containing mount points for nfs shares."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_nfs.xml30(td)
-msgid "nfs_oversub_ratio = 1.0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_nfs.xml31(td)
-msgid ""
-"(FloatOpt) This will compare the allocated to available space on the volume "
-"destination. If the ratio exceeds this number, the destination will no "
-"longer be valid."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_nfs.xml34(td)
-msgid "nfs_shares_config = /etc/cinder/nfs_shares"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_nfs.xml35(td)
-#: ./doc/common/tables/cinder-nexenta_nfs.xml31(td)
-msgid "(StrOpt) File with the list of available nfs shares"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_nfs.xml38(td)
-msgid "nfs_sparsed_volumes = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_nfs.xml42(td)
-msgid "nfs_used_ratio = 0.95"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_nfs.xml43(td)
-msgid ""
-"(FloatOpt) Percent of ACTUAL usage of the underlying volume before no new "
-"volumes can be allocated to the volume destination."
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml8(caption)
-msgid "Description of configuration options for plumgrid"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml19(th)
-msgid "[plumgriddirector]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml22(td)
-msgid "director_server = localhost"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml23(td)
-msgid "(StrOpt) PLUMgrid Director server to connect to"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml26(td)
-msgid "director_server_port = 8080"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml27(td)
-msgid "(StrOpt) PLUMgrid Director server port to connect to"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml30(td)
-#: ./doc/common/tables/neutron-ml2_brocade.xml30(td)
-msgid "password = password"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml31(td)
-msgid "(StrOpt) PLUMgrid Director admin password"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml34(td)
-msgid "servertimeout = 5"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml35(td)
-msgid "(IntOpt) PLUMgrid Director server timeout"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml38(td)
-msgid "username = username"
-msgstr ""
-
-#: ./doc/common/tables/neutron-plumgrid.xml39(td)
-msgid "(StrOpt) PLUMgrid Director admin username"
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml8(caption)
-msgid "Description of configuration options for cfn_api"
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml22(td)
-msgid "instance_connection_https_validate_certificates = 1"
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml23(td)
-msgid ""
-"(StrOpt) Instance connection to CFN/CW API validate certs if SSL is used."
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml26(td)
-msgid "instance_connection_is_secure = 0"
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml27(td)
-msgid "(StrOpt) Instance connection to CFN/CW API via https."
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml30(th)
-msgid "[heat_api_cfn]"
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml34(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml30(td)
-#: ./doc/common/tables/heat-api.xml104(td)
-msgid "(IntOpt) Number of backlog requests to configure the socket with."
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml38(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml34(td)
-#: ./doc/common/tables/glance-common.xml35(td)
-#: ./doc/common/tables/heat-api.xml108(td)
-msgid ""
-"(StrOpt) Address to bind the server. Useful when selecting a particular "
-"network interface."
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml41(td)
-msgid "bind_port = 8000"
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml42(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml38(td)
-#: ./doc/common/tables/glance-common.xml39(td)
-#: ./doc/common/tables/heat-api.xml112(td)
-msgid "(IntOpt) The port on which the server will listen."
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml46(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml42(td)
-#: ./doc/common/tables/heat-api.xml116(td)
-msgid "(StrOpt) Location of the SSL certificate file to use for SSL mode."
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml50(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml46(td)
-#: ./doc/common/tables/heat-api.xml120(td)
-msgid "(StrOpt) Location of the SSL key file to use for enabling SSL mode."
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml53(td)
-#: ./doc/common/tables/trove-api.xml66(td)
-#: ./doc/common/tables/neutron-api.xml42(td)
-#: ./doc/common/tables/cinder-api.xml46(td)
-#: ./doc/common/tables/glance-wsgi.xml30(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml49(td)
-#: ./doc/common/tables/heat-api.xml123(td)
-#: ./doc/common/tables/nova-api.xml42(td)
-msgid "max_header_line = 16384"
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml54(td)
-#: ./doc/common/tables/cinder-api.xml47(td)
-#: ./doc/common/tables/heat-api.xml124(td)
-#: ./doc/common/tables/nova-api.xml43(td)
-msgid ""
-"(IntOpt) Maximum line size of message headers to be accepted. "
-"max_header_line may need to be increased when using large tokens (typically "
-"those generated by the Keystone v3 API with big service catalogs)."
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml57(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml53(td)
-#: ./doc/common/tables/heat-api.xml127(td)
-msgid "workers = 0"
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml58(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml54(td)
-#: ./doc/common/tables/heat-api.xml128(td)
-msgid "(IntOpt) Number of workers for Heat service."
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml65(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml61(td)
-#: ./doc/common/tables/nova-wsgi.xml27(td)
-#: ./doc/common/tables/cinder-common.xml175(td)
-#: ./doc/common/tables/cinder-ssl.xml23(td)
-#: ./doc/common/tables/heat-api.xml146(td)
-#: ./doc/common/tables/neutron-ssl.xml23(td)
-#: ./doc/common/tables/neutron-ssl.xml38(td)
-#: ./doc/common/tables/trove-ssl.xml23(td)
-#: ./doc/common/tables/ceilometer-ssl.xml23(td)
-msgid "(StrOpt) CA certificate file to use to verify connecting clients"
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml69(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml65(td)
-#: ./doc/common/tables/cinder-common.xml179(td)
-#: ./doc/common/tables/cinder-ssl.xml27(td)
-#: ./doc/common/tables/heat-api.xml150(td)
-#: ./doc/common/tables/neutron-ssl.xml27(td)
-#: ./doc/common/tables/neutron-ssl.xml42(td)
-#: ./doc/common/tables/trove-ssl.xml27(td)
-#: ./doc/common/tables/ceilometer-ssl.xml27(td)
-msgid "(StrOpt) Certificate file to use when starting the server securely"
-msgstr ""
-
-#: ./doc/common/tables/heat-cfn_api.xml73(td)
-#: ./doc/common/tables/heat-cloudwatch_api.xml69(td)
-#: ./doc/common/tables/cinder-common.xml183(td)
-#: ./doc/common/tables/cinder-ssl.xml31(td)
-#: ./doc/common/tables/heat-api.xml154(td)
-#: ./doc/common/tables/neutron-ssl.xml31(td)
-#: ./doc/common/tables/neutron-ssl.xml46(td)
-#: ./doc/common/tables/trove-ssl.xml31(td)
-#: ./doc/common/tables/ceilometer-ssl.xml31(td)
-msgid "(StrOpt) Private key file to use when starting the server securely"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml8(caption)
-msgid "Description of configuration options for hypervisor"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml22(td)
-msgid "default_ephemeral_format = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml23(td)
-msgid ""
-"(StrOpt) The default format an ephemeral_volume will be formatted with on "
-"creation."
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml26(td)
-msgid "force_raw_images = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml27(td)
-msgid "(BoolOpt) Force backing images to raw format"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml30(td)
-msgid "preallocate_images = none"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml31(td)
-msgid ""
-"(StrOpt) VM image preallocation mode: \"none\" =&gt; no storage provisioning"
-" is done up front, \"space\" =&gt; storage is fully allocated at instance "
-"start"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml34(td)
-msgid "rescue_timeout = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml35(td)
-msgid ""
-"(IntOpt) Automatically unrescue an instance after N seconds. Set to 0 to "
-"disable."
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml38(td)
-msgid "timeout_nbd = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml39(td)
-msgid "(IntOpt) Amount of time, in seconds, to wait for NBD device start up."
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml42(td)
-msgid "use_cow_images = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml43(td)
-msgid "(BoolOpt) Whether to use cow images"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml46(td)
-msgid "vcpu_pin_set = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml47(td)
-msgid ""
-"(StrOpt) Defines which pcpus that instance vcpus can use. For example, "
-"\"4-12,^8,15\""
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml50(td)
-msgid "virt_mkfs = []"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml51(td)
-msgid ""
-"(MultiStrOpt) Name of the mkfs commands for ephemeral device. The format is "
-"&lt;os_type&gt;=&lt;mkfs command&gt;"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml57(td)
-msgid ""
-"block_migration_flag = VIR_MIGRATE_UNDEFINE_SOURCE, VIR_MIGRATE_PEER2PEER, "
-"VIR_MIGRATE_NON_SHARED_INC"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml58(td)
-msgid "(StrOpt) Migration flags to be set for block migration"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml61(td)
-msgid "disk_cachemodes ="
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml62(td)
-msgid ""
-"(ListOpt) Specific cachemodes to use for different disk types e.g: "
-"file=directsync,block=none"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml65(td)
-msgid "images_rbd_ceph_conf ="
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml66(td)
-msgid "(StrOpt) Path to the ceph configuration file to use"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml69(td)
-msgid "images_rbd_pool = rbd"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml70(td)
-msgid "(StrOpt) The RADOS pool in which rbd volumes are stored"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml73(td)
-msgid "images_type = default"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml74(td)
-msgid ""
-"(StrOpt) VM Images format. Acceptable values are: raw, qcow2, lvm, rbd, "
-"default. If default is specified, then use_cow_images flag is used instead "
-"of this one."
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml77(td)
-msgid "images_volume_group = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml78(td)
-msgid ""
-"(StrOpt) LVM Volume Group that is used for VM images, when you specify "
-"images_type=lvm."
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml81(td)
-msgid "inject_key = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml82(td)
-msgid "(BoolOpt) Inject the ssh public key at boot time"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml85(td)
-msgid "inject_partition = -2"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml86(td)
-msgid ""
-"(IntOpt) The partition to inject to : -2 =&gt; disable, -1 =&gt; inspect "
-"(libguestfs only), 0 =&gt; not partitioned, &gt;0 =&gt; partition number"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml89(td)
-msgid "inject_password = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml90(td)
-msgid "(BoolOpt) Inject the admin password at boot time, without an agent."
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml93(td)
-msgid "iscsi_use_multipath = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml94(td)
-msgid "(BoolOpt) Use multipath connection of the iSCSI volume"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml97(td)
-msgid "iser_use_multipath = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml98(td)
-msgid "(BoolOpt) Use multipath connection of the iSER volume"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml101(td)
-msgid "rescue_image_id = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml102(td)
-msgid "(StrOpt) Rescue ami image"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml105(td)
-msgid "rescue_kernel_id = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml106(td)
-msgid "(StrOpt) Rescue aki image"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml109(td)
-msgid "rescue_ramdisk_id = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml110(td)
-msgid "(StrOpt) Rescue ari image"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml113(td)
-msgid "snapshot_compression = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml114(td)
-msgid ""
-"(BoolOpt) Compress snapshot images when possible. This currently applies "
-"exclusively to qcow2 images"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml117(td)
-msgid "snapshot_image_format = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml118(td)
-msgid ""
-"(StrOpt) Snapshot image format (valid options are : raw, qcow2, vmdk, vdi). "
-"Defaults to same as source image"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml121(td)
-msgid "sparse_logical_volumes = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml122(td)
-msgid ""
-"(BoolOpt) Create sparse logical volumes (with virtualsize) if this flag is "
-"set to True."
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml125(td)
-msgid "use_usb_tablet = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml126(td)
-msgid "(BoolOpt) Sync virtual and real mouse cursors in Windows VMs"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml129(td)
-msgid "use_virtio_for_bridges = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-hypervisor.xml130(td)
-msgid "(BoolOpt) Use virtio for bridge interfaces with KVM/QEMU"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml8(caption)
-#: ./doc/common/tables/heat-rabbitmq.xml8(caption)
-#: ./doc/common/tables/glance-rabbitmq.xml8(caption)
-#: ./doc/common/tables/neutron-rabbitmq.xml8(caption)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml8(caption)
-#: ./doc/common/tables/nova-rabbitmq.xml8(caption)
-msgid "Description of configuration options for rabbitmq"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml23(td)
-#: ./doc/common/tables/heat-rabbitmq.xml39(td)
-msgid ""
-"(BoolOpt) use H/A queues in RabbitMQ (x-ha-policy: all).You need to wipe "
-"RabbitMQ database when changing this option."
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml27(td)
-#: ./doc/common/tables/heat-rabbitmq.xml43(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml27(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml47(td)
-msgid "(StrOpt) The RabbitMQ broker address where a single node is used"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml31(td)
-#: ./doc/common/tables/heat-rabbitmq.xml47(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml31(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml51(td)
-msgid "(ListOpt) RabbitMQ HA cluster host:port pairs"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml35(td)
-#: ./doc/common/tables/heat-rabbitmq.xml51(td)
-msgid ""
-"(IntOpt) maximum retries with trying to connect to RabbitMQ (the default of "
-"0 implies an infinite retry count)"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml39(td)
-#: ./doc/common/tables/heat-rabbitmq.xml55(td)
-msgid "(StrOpt) the RabbitMQ password"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml43(td)
-#: ./doc/common/tables/heat-rabbitmq.xml59(td)
-#: ./doc/common/tables/neutron-rabbitmq.xml43(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml63(td)
-msgid "(IntOpt) The RabbitMQ broker port where a single node is used"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml47(td)
-#: ./doc/common/tables/heat-rabbitmq.xml63(td)
-msgid ""
-"(IntOpt) how long to backoff for between retries when connecting to RabbitMQ"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml51(td)
-#: ./doc/common/tables/heat-rabbitmq.xml67(td)
-msgid "(IntOpt) how frequently to retry connecting with RabbitMQ"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml55(td)
-#: ./doc/common/tables/heat-rabbitmq.xml71(td)
-msgid "(BoolOpt) connect over SSL for RabbitMQ"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml59(td)
-#: ./doc/common/tables/heat-rabbitmq.xml75(td)
-msgid "(StrOpt) the RabbitMQ userid"
-msgstr ""
-
-#: ./doc/common/tables/trove-rabbitmq.xml63(td)
-#: ./doc/common/tables/heat-rabbitmq.xml79(td)
-msgid "(StrOpt) the RabbitMQ virtual host"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml7(literal)
-msgid "[filter:tempurl]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml18(td)
-msgid "use = egg:swift#tempurl"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml21(td)
-msgid "methods = GET HEAD PUT"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml21(td)
-msgid "HTTP methods allowed with Temporary URLs"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml24(td)
-msgid "incoming_remove_headers = x-timestamp"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml24(td)
-msgid ""
-"Headers to remove from incoming requests. Simply a whitespace delimited list"
-" of header names and names can optionally end with '*' to indicate a prefix "
-"match."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml28(td)
-msgid "incoming_allow_headers ="
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml28(td)
-msgid ""
-"Headers allowed as exceptions to incoming_remove_headers. Simply a "
-"whitespace delimited list of header names and names can optionally end with "
-"'*' to indicate a prefix match."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml33(td)
-msgid "outgoing_remove_headers = x-object-meta-*"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml33(td)
-msgid ""
-"Headers to remove from outgoing responses. Simply a whitespace delimited "
-"list of header names and names can optionally end with '*' to indicate a "
-"prefix match."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml38(td)
-msgid "outgoing_allow_headers = x-object-meta-public-*"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml38(td)
-msgid ""
-"Headers allowed as exceptions to outgoing_allow_headers. Simply a whitespace"
-" delimited list of header names and names can optionally end with '*' to "
-"indicate a prefix match."
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml8(caption)
-#: ./doc/common/tables/neutron-api.xml8(caption)
-#: ./doc/common/tables/cinder-api.xml8(caption)
-#: ./doc/common/tables/ceilometer-api.xml8(caption)
-#: ./doc/common/tables/heat-api.xml8(caption)
-#: ./doc/common/tables/nova-api.xml8(caption)
-#: ./doc/common/tables/glance-api.xml8(caption)
-#: ./doc/common/tables/keystone-api.xml8(caption)
-msgid "Description of configuration options for api"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml22(td)
-msgid "admin_roles = admin"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml26(td)
-msgid "api_extensions_path = trove/extensions/routes"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml27(td)
-msgid "(StrOpt) Path to extensions."
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml30(td)
-#: ./doc/common/tables/neutron-api.xml38(td)
-#: ./doc/common/tables/cinder-api.xml22(td)
-#: ./doc/common/tables/nova-wsgi.xml22(td)
-#: ./doc/common/tables/heat-api.xml134(td)
-msgid "api_paste_config = api-paste.ini"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml31(td)
-msgid "(StrOpt) File name for the paste.deploy config for trove-api."
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml34(td)
-msgid "bind_port = 8779"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml35(td)
-#: ./doc/common/tables/trove-api.xml47(td)
-#: ./doc/common/tables/trove-api.xml51(td)
-#: ./doc/common/tables/trove-api.xml55(td)
-#: ./doc/common/tables/trove-api.xml59(td)
-#: ./doc/common/tables/trove-api.xml63(td)
-#: ./doc/common/tables/trove-api.xml79(td)
-#: ./doc/common/tables/trove-api.xml87(td)
-#: ./doc/common/tables/trove-api.xml103(td)
-#: ./doc/common/tables/trove-taskmanager.xml43(td)
-#: ./doc/common/tables/trove-taskmanager.xml47(td)
-#: ./doc/common/tables/trove-taskmanager.xml51(td)
-#: ./doc/common/tables/trove-taskmanager.xml55(td)
-#: ./doc/common/tables/trove-taskmanager.xml59(td)
-#: ./doc/common/tables/trove-backup.xml71(td)
-#: ./doc/common/tables/trove-volume.xml39(td)
-#: ./doc/common/tables/trove-volume.xml47(td)
-#: ./doc/common/tables/trove-database.xml27(td)
-#: ./doc/common/tables/trove-rpc.xml39(td)
-#: ./doc/common/tables/trove-rpc.xml43(td)
-#: ./doc/common/tables/trove-common.xml23(td)
-#: ./doc/common/tables/trove-common.xml27(td)
-#: ./doc/common/tables/trove-common.xml47(td)
-#: ./doc/common/tables/trove-dns.xml71(td)
-#: ./doc/common/tables/trove-dns.xml75(td)
-#: ./doc/common/tables/trove-heat.xml23(td)
-#: ./doc/common/tables/trove-guestagent.xml23(td)
-#: ./doc/common/tables/trove-guestagent.xml27(td)
-#: ./doc/common/tables/trove-guestagent.xml31(td)
-msgid "(IntOpt) No help text available for this option."
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml38(td)
-msgid "db_api_implementation = trove.db.sqlalchemy.api"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml42(td)
-msgid "hostname_require_ipv4 = True"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml43(td)
-msgid "(BoolOpt) Require user hostnames to be IPv4 addresses."
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml46(td)
-msgid "http_delete_rate = 200"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml50(td)
-msgid "http_get_rate = 200"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml54(td)
-msgid "http_post_rate = 200"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml58(td)
-msgid "http_put_rate = 200"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml62(td)
-msgid "instances_page_size = 20"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml67(td)
-#: ./doc/common/tables/glance-wsgi.xml31(td)
-msgid ""
-"(IntOpt) Maximum line size of message headers to be accepted. "
-"max_header_line may need to be increased when using large tokens (typically "
-"those generated by the Keystone v3 API with big service catalogs"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml70(td)
-msgid "region = LOCAL_DEV"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml71(td)
-msgid "(StrOpt) The region this service is located."
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml74(td)
-#: ./doc/common/tables/glance-wsgi.xml34(td)
-#: ./doc/common/tables/neutron-wsgi.xml30(td)
-#: ./doc/common/tables/nova-wsgi.xml38(td)
-#: ./doc/common/tables/cinder-common.xml198(td)
-#: ./doc/common/tables/keystone-api.xml86(td)
-msgid "tcp_keepidle = 600"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml75(td)
-#: ./doc/common/tables/neutron-wsgi.xml31(td)
-#: ./doc/common/tables/nova-wsgi.xml39(td)
-#: ./doc/common/tables/cinder-common.xml199(td)
-msgid ""
-"(IntOpt) Sets the value of TCP_KEEPIDLE in seconds for each server socket. "
-"Not supported on OS X."
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml78(td)
-msgid "trove_api_workers = None"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml82(td)
-msgid "trove_auth_url = http://0.0.0.0:5000/v2.0"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml86(td)
-msgid "trove_conductor_workers = 1"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml90(td)
-msgid "trove_security_group_name_prefix = SecGroup"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml94(td)
-msgid "trove_security_group_rule_cidr = 0.0.0.0/0"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml98(td)
-msgid "trove_security_groups_support = True"
-msgstr ""
-
-#: ./doc/common/tables/trove-api.xml102(td)
-msgid "users_page_size = 20"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml8(caption)
-#: ./doc/common/tables/trove-quota.xml8(caption)
-#: ./doc/common/tables/heat-quota.xml8(caption)
-#: ./doc/common/tables/nova-quota.xml8(caption)
-msgid "Description of configuration options for quota"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml22(td)
-#: ./doc/common/tables/nova-policy.xml34(td)
-msgid "max_age = 0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml23(td)
-msgid "(IntOpt) number of seconds between subsequent usage refreshes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml26(td)
-msgid "quota_driver = cinder.quota.DbQuotaDriver"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml27(td)
-msgid "(StrOpt) default driver to use for quota checks"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml30(td)
-msgid "quota_gigabytes = 1000"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml31(td)
-msgid ""
-"(IntOpt) number of volume gigabytes (snapshots are also included) allowed "
-"per project"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml34(td)
-msgid "quota_snapshots = 10"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml35(td)
-msgid "(IntOpt) number of volume snapshots allowed per project"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml38(td)
-msgid "quota_volumes = 10"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml39(td)
-msgid "(IntOpt) number of volumes allowed per project"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml42(td)
-#: ./doc/common/tables/nova-policy.xml66(td)
-msgid "reservation_expire = 86400"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml43(td)
-msgid "(IntOpt) number of seconds until a reservation expires"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml46(td)
-msgid "use_default_quota_class = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-quota.xml47(td)
-msgid "(BoolOpt) whether to use default quota class for default quota"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml7(literal)
-#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml7(literal)
-#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml7(literal)
-#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml7(literal)
-msgid "[filter:healthcheck]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml18(td)
-#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml18(td)
-#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml18(td)
-#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml18(td)
-msgid "use = egg:swift#healthcheck"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-healthcheck.xml21(td)
-#: ./doc/common/tables/swift-account-server-filter-healthcheck.xml21(td)
-#: ./doc/common/tables/swift-container-server-filter-healthcheck.xml21(td)
-#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml21(td)
-msgid "disable_path ="
-msgstr ""
-
-#: ./doc/common/tables/nova-console.xml8(caption)
-msgid "Description of configuration options for console"
-msgstr ""
-
-#: ./doc/common/tables/nova-console.xml22(td)
-msgid "console_public_hostname = oslo"
-msgstr ""
-
-#: ./doc/common/tables/nova-console.xml23(td)
-msgid "(StrOpt) Publicly visible name for this console host"
-msgstr ""
-
-#: ./doc/common/tables/nova-console.xml26(td)
-msgid "console_token_ttl = 600"
-msgstr ""
-
-#: ./doc/common/tables/nova-console.xml27(td)
-msgid "(IntOpt) How many seconds before deleting tokens"
-msgstr ""
-
-#: ./doc/common/tables/nova-console.xml30(td)
-msgid "consoleauth_manager = nova.consoleauth.manager.ConsoleAuthManager"
-msgstr ""
-
-#: ./doc/common/tables/nova-console.xml31(td)
-msgid "(StrOpt) Manager for console auth"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml8(caption)
-msgid "Description of configuration options for events"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml19(th)
-msgid "[event]"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml22(td)
-msgid "definitions_cfg_file = event_definitions.yaml"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml23(td)
-msgid "(StrOpt) Configuration file for event definitions."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml26(td)
-msgid "drop_unmatched_notifications = False"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml27(td)
-msgid ""
-"(BoolOpt) Drop notifications if no event definition matches. (Otherwise, we "
-"convert them with just the default traits)"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml30(th)
-msgid "[notification]"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml33(td)
-msgid "ack_on_event_error = True"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml34(td)
-msgid "(BoolOpt) Acknowledge message when event persistence fails."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml37(td)
-msgid "store_events = False"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-events.xml38(td)
-msgid "(BoolOpt) Save event details."
-msgstr ""
-
-#: ./doc/common/tables/keystone-os_inherit.xml8(caption)
-msgid "Description of configuration options for os_inherit"
-msgstr ""
-
-#: ./doc/common/tables/keystone-os_inherit.xml19(th)
-msgid "[os_inherit]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-os_inherit.xml22(td)
-#: ./doc/common/tables/keystone-cache.xml38(td)
-#: ./doc/common/tables/neutron-fwaas.xml22(td)
-#: ./doc/common/tables/nova-spice.xml26(td)
-#: ./doc/common/tables/nova-apiv3.xml22(td)
-#: ./doc/common/tables/nova-rdp.xml22(td)
-msgid "enabled = False"
-msgstr ""
-
-#: ./doc/common/tables/keystone-os_inherit.xml23(td)
-msgid ""
-"(BoolOpt) role-assignment inheritance to projects from owning domain can be "
-"optionally enabled."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients.xml8(caption)
-msgid "Description of configuration options for clients"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients.xml22(td)
-msgid "region_name_for_services = None"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients.xml23(td)
-msgid "(StrOpt) Default region name used to get services endpoints."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients.xml26(th)
-msgid "[clients]"
-msgstr ""
-
-#: ./doc/common/tables/heat-notification.xml8(caption)
-#: ./doc/common/tables/keystone-notification.xml8(caption)
-msgid "Description of configuration options for notification"
-msgstr ""
-
-#: ./doc/common/tables/heat-notification.xml22(td)
-#: ./doc/common/tables/keystone-notification.xml22(td)
-msgid "onready = None"
-msgstr ""
-
-#: ./doc/common/tables/heat-notification.xml23(td)
-msgid ""
-"(StrOpt) onready allows you to send a notification when the heat processes "
-"are ready to serve. This is either a module with the notify() method or a "
-"shell command. To enable notifications with systemd, one may use the "
-"'systemd-notify --ready' shell command or the 'heat.common.systemd' "
-"notification module."
-msgstr ""
-
-#: ./doc/common/tables/keystone-assignment.xml8(caption)
-msgid "Description of configuration options for assignment"
-msgstr ""
-
-#: ./doc/common/tables/keystone-assignment.xml19(th)
-msgid "[assignment]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-assignment.xml22(td)
-#: ./doc/common/tables/keystone-token.xml26(td)
-msgid "cache_time = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-assignment.xml23(td)
-msgid ""
-"(IntOpt) TTL (in seconds) to cache assignment data. This has no effect "
-"unless global caching is enabled."
-msgstr ""
-
-#: ./doc/common/tables/keystone-assignment.xml26(td)
-#: ./doc/common/tables/keystone-token.xml30(td)
-#: ./doc/common/tables/keystone-revoke.xml22(td)
-msgid "caching = True"
-msgstr ""
-
-#: ./doc/common/tables/keystone-assignment.xml27(td)
-msgid ""
-"(BoolOpt) Toggle for assignment caching. This has no effect unless global "
-"caching is enabled."
-msgstr ""
-
-#: ./doc/common/tables/keystone-assignment.xml30(td)
-msgid "driver = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-assignment.xml31(td)
-msgid "(StrOpt) Keystone Assignment backend driver."
-msgstr ""
-
-#: ./doc/common/tables/keystone-assignment.xml35(td)
-msgid ""
-"(IntOpt) Maximum number of entities that will be returned in an assignment "
-"collection."
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml22(td)
-msgid "bindir = /usr/local/bin"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml23(td)
-msgid "(StrOpt) Directory where nova binaries are installed"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml26(td)
-msgid "compute_topic = compute"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml27(td)
-msgid "(StrOpt) The topic compute nodes listen on"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml30(td)
-msgid "console_topic = console"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml31(td)
-msgid "(StrOpt) The topic console proxy nodes listen on"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml34(td)
-msgid "consoleauth_topic = consoleauth"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml35(td)
-msgid "(StrOpt) The topic console auth proxy nodes listen on"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml43(td)
-msgid ""
-"(StrOpt) Name of this node. This can be an opaque identifier. It is not "
-"necessarily a hostname, FQDN, or IP address. However, the node name must be "
-"valid within an AMQP key, and if using ZeroMQ, a valid hostname, FQDN, or IP"
-" address"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml54(td)
-#: ./doc/common/tables/cinder-common.xml118(td)
-msgid "my_ip = 10.0.0.1"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml55(td)
-msgid "(StrOpt) IP address of this host"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml58(td)
-#: ./doc/common/tables/cinder-rpc.xml74(td)
-#: ./doc/common/tables/keystone-amqp.xml38(td)
-#: ./doc/common/tables/neutron-notifier.xml30(td)
-#: ./doc/common/tables/glance-amqp.xml30(td)
-#: ./doc/common/tables/heat-amqp.xml50(td)
-#: ./doc/common/tables/ceilometer-amqp.xml30(td)
-#: ./doc/common/tables/trove-amqp.xml58(td)
-msgid "notification_driver = []"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml59(td)
-#: ./doc/common/tables/cinder-rpc.xml75(td)
-#: ./doc/common/tables/keystone-amqp.xml39(td)
-#: ./doc/common/tables/glance-amqp.xml31(td)
-msgid "(MultiStrOpt) Driver or drivers to handle sending notifications."
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml62(td)
-#: ./doc/common/tables/cinder-rpc.xml78(td)
-#: ./doc/common/tables/keystone-amqp.xml42(td)
-#: ./doc/common/tables/neutron-notifier.xml34(td)
-#: ./doc/common/tables/glance-amqp.xml34(td)
-#: ./doc/common/tables/heat-amqp.xml54(td)
-#: ./doc/common/tables/ceilometer-amqp.xml34(td)
-#: ./doc/common/tables/trove-amqp.xml66(td)
-msgid "notification_topics = notifications"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml63(td)
-#: ./doc/common/tables/cinder-rpc.xml79(td)
-#: ./doc/common/tables/keystone-amqp.xml43(td)
-#: ./doc/common/tables/glance-amqp.xml35(td)
-msgid "(ListOpt) AMQP topic used for OpenStack notifications."
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml66(td)
-msgid "notify_api_faults = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml67(td)
-msgid ""
-"(BoolOpt) If set, send api.fault notifications on caught exceptions in the "
-"API service."
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml70(td)
-msgid "notify_on_state_change = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml71(td)
-msgid ""
-"(StrOpt) If set, send compute.instance.update notifications on instance "
-"state changes. Valid values are None for no notifications, \"vm_state\" for "
-"notifications on VM state changes, or \"vm_and_task_state\" for "
-"notifications on VM and task state changes."
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml78(td)
-msgid "pybasedir = /usr/lib/python/site-packages"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml79(td)
-msgid "(StrOpt) Directory where the nova python module is installed"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml82(td)
-#: ./doc/common/tables/cinder-common.xml146(td)
-#: ./doc/common/tables/trove-rpc.xml46(td)
-msgid "report_interval = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml83(td)
-msgid "(IntOpt) Seconds between nodes reporting state to datastore"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml86(td)
-msgid "rootwrap_config = /etc/nova/rootwrap.conf"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml87(td)
-#: ./doc/common/tables/cinder-common.xml155(td)
-msgid ""
-"(StrOpt) Path to the rootwrap configuration file to use for running commands"
-" as root"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml90(td)
-#: ./doc/common/tables/cinder-common.xml162(td)
-msgid "service_down_time = 60"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml91(td)
-msgid "(IntOpt) Maximum time since last check-in for up service"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml94(td)
-msgid "state_path = $pybasedir"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml95(td)
-msgid "(StrOpt) Top-level directory for maintaining nova's state"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml98(td)
-msgid "tempdir = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml99(td)
-msgid "(StrOpt) Explicitly specify the temporary working directory"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml102(td)
-#: ./doc/common/tables/cinder-rpc.xml230(td)
-#: ./doc/common/tables/keystone-amqp.xml66(td)
-#: ./doc/common/tables/glance-amqp.xml54(td)
-msgid "transport_url = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-common.xml103(td)
-#: ./doc/common/tables/cinder-rpc.xml231(td)
-#: ./doc/common/tables/keystone-amqp.xml67(td)
-#: ./doc/common/tables/glance-amqp.xml55(td)
-msgid ""
-"(StrOpt) A URL representing the messaging driver to use and its full "
-"configuration. If not set, we fall back to the rpc_backend option and driver"
-" specific configuration."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-updater.xml7(literal)
-msgid "[object-updater]"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-updater.xml18(td)
-msgid "log_name = object-updater"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-updater.xml33(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml39(td)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml30(td)
-msgid "concurrency = 1"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-updater.xml36(td)
-#: ./doc/common/tables/swift-object-server-object-replicator.xml57(td)
-msgid "node_timeout = &lt;whatever's in the DEFAULT section or 10&gt;"
-msgstr ""
-
-#: ./doc/common/tables/glance-zmq.xml8(caption)
-msgid "Description of configuration options for zmq"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metering_agent.xml8(caption)
-msgid "Description of configuration options for metering_agent"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metering_agent.xml22(td)
-msgid ""
-"driver = "
-"neutron.services.metering.drivers.noop.noop_driver.NoopMeteringDriver"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metering_agent.xml23(td)
-msgid "(StrOpt) Metering driver"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metering_agent.xml26(td)
-msgid "measure_interval = 30"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metering_agent.xml27(td)
-msgid "(IntOpt) Interval between two metering measures"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metering_agent.xml33(td)
-msgid "report_interval = 30"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metering_agent.xml34(td)
-msgid ""
-"(FloatOpt) Seconds between nodes reporting state to server; should be less "
-"than agent_down_time, best if it is half or less than agent_down_time."
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml8(caption)
-msgid "Description of configuration options for taskmanager"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml22(td)
-msgid "cloudinit_location = /etc/trove/cloudinit"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml23(td)
-msgid "(StrOpt) Path to folder with cloudinit scripts."
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml26(td)
-msgid "datastore_manager = None"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml27(td)
-msgid ""
-"(StrOpt) Manager class in guestagent, setup by taskmanager on instance "
-"provision."
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml30(td)
-msgid "datastore_registry_ext = {}"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml31(td)
-msgid ""
-"(DictOpt) Extension for default datastore managers. Allows to use custom "
-"managers for each of datastore supported in trove."
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml34(td)
-msgid "exists_notification_ticks = 360"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml35(td)
-msgid ""
-"(IntOpt) Number of report_intervals to wait between pushing events (see "
-"report_interval)."
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml38(td)
-msgid "exists_notification_transformer = None"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml39(td)
-msgid "(StrOpt) Transformer for exists notifications."
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml42(td)
-msgid "reboot_time_out = 120"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml46(td)
-msgid "resize_time_out = 600"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml50(td)
-msgid "revert_time_out = 600"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml54(td)
-msgid "server_delete_time_out = 60"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml58(td)
-msgid "state_change_wait_time = 180"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml62(td)
-msgid "update_status_on_fail = False"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml63(td)
-msgid ""
-"(BoolOpt) If instance fails to become active, taskmanager updates statuses, "
-"service status = FAILED_TIMEOUT_GUESTAGENT, instance task status = "
-"BUILDING_ERROR_TIMEOUT_GA."
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml66(td)
-#: ./doc/common/tables/trove-guestagent.xml66(td)
-msgid "usage_sleep_time = 5"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml67(td)
-#: ./doc/common/tables/trove-guestagent.xml67(td)
-msgid "(IntOpt) Time to sleep during the check active guest."
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml70(td)
-msgid "use_heat = False"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml74(td)
-msgid "use_nova_server_volume = False"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml78(td)
-msgid "verify_swift_checksum_on_restore = True"
-msgstr ""
-
-#: ./doc/common/tables/trove-taskmanager.xml79(td)
-msgid ""
-"(BoolOpt) Enable verification of swift checksum before starting restore; "
-"makes sure the checksum of original backup matches checksum of the swift "
-"backup file."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml7(literal)
-msgid "[filter:account-quotas]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-account-quotas.xml18(td)
-msgid "use = egg:swift#account_quotas"
-msgstr ""
-
-#: ./doc/common/tables/keystone-zeromq.xml8(caption)
-#: ./doc/common/tables/trove-zeromq.xml8(caption)
-#: ./doc/common/tables/heat-zeromq.xml8(caption)
-#: ./doc/common/tables/nova-zeromq.xml8(caption)
-#: ./doc/common/tables/neutron-zeromq.xml8(caption)
-msgid "Description of configuration options for zeromq"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml7(literal)
-#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml7(literal)
-msgid "[app:proxy-server]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml18(td)
-#: ./doc/common/tables/swift-object-expirer-app-proxy-server.xml18(td)
-msgid "use = egg:swift#proxy"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml21(td)
-msgid "set log_name = proxy-server"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml33(td)
-msgid "log_handoffs = true"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml36(td)
-msgid "recheck_account_existence = 60"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml36(td)
-msgid "Cache timeout in seconds to send memcached for account existence"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml39(td)
-msgid "recheck_container_existence = 60"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml39(td)
-msgid "Cache timeout in seconds to send memcached for container existence"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml42(td)
-msgid "object_chunk_size = 8192"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml42(td)
-msgid "Chunk size to read from object servers"
-msgstr "オブジェクトサーバーから読み込むチャンク容量"
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml45(td)
-msgid "client_chunk_size = 8192"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml45(td)
-msgid "Chunk size to read from clients"
-msgstr "クライアントから読み込むチャンク容量"
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml51(td)
-msgid "recoverable_node_timeout = node_timeout"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml51(td)
-msgid ""
-"Request timeout to external services for requests that, on failure, can be "
-"recovered from. For example, object GET. from a client external services"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml57(td)
-msgid "post_quorum_timeout = 0.5"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml60(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml45(td)
-msgid "error_suppression_interval = 60"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml60(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml45(td)
-msgid ""
-"Time in seconds that must elapse since the last error for a node to be "
-"considered no longer error limited"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml63(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml48(td)
-msgid "error_suppression_limit = 10"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml63(td)
-#: ./doc/common/tables/swift-account-server-account-replicator.xml48(td)
-msgid "Error count to consider a node error limited"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml66(td)
-msgid "allow_account_management = false"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml66(td)
-msgid "Whether account PUTs and DELETEs are even callable"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml69(td)
-msgid "object_post_as_copy = true"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml69(td)
-msgid ""
-"Set object_post_as_copy = false to turn on fast posts where only the "
-"metadata changes are stored anew and the original data file is kept in "
-"place. This makes for quicker posts; but since the container metadata isn't "
-"updated in this mode, features like container sync won't be able to sync "
-"posts."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml72(td)
-msgid "account_autocreate = false"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml72(td)
-msgid ""
-"If set to 'true' authorized accounts that do not yet exist within the Swift "
-"cluster will be automatically created."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml75(td)
-msgid "max_containers_per_account = 0"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml75(td)
-msgid ""
-"If set to a positive value, trying to create a container when the account "
-"already has at least this maximum containers will result in a 403 Forbidden."
-" Note: This is a soft limit, meaning a user might exceed the cap for "
-"recheck_account_existence before the 403s kick in."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml78(td)
-msgid "max_containers_whitelist ="
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml78(td)
-msgid ""
-"is a comma separated list of account names that ignore the "
-"max_containers_per_account cap."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml81(td)
-msgid "deny_host_headers ="
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml84(td)
-#: ./doc/common/tables/swift-account-server-app-account-server.xml36(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml45(td)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml54(td)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml21(td)
-msgid "auto_create_account_prefix = ."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml84(td)
-#: ./doc/common/tables/swift-account-server-app-account-server.xml36(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml45(td)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml54(td)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml21(td)
-msgid "Prefix to use when automatically creating accounts"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml87(td)
-msgid "put_queue_depth = 10"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml90(td)
-msgid "sorting_method = shuffle"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml93(td)
-msgid "timing_expiry = 300"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml96(td)
-msgid "max_large_object_get_time = 86400"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml99(td)
-msgid "request_node_count = 2 * replicas"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml99(td)
-msgid ""
-"* replicas Set to the number of nodes to contact for a normal request. You "
-"can use '* replicas' at the end to have it use the number given times the "
-"number of replicas for the ring being used for the request. conf file for "
-"values will only be shown to the list of swift_owners. The exact default "
-"definition of a swift_owner is headers&gt; up to the auth system in use, but"
-" usually indicates administrative responsibilities. paste.deploy to use for "
-"auth. To use tempauth set to: `egg:swift#tempauth` each request"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml102(td)
-msgid "read_affinity = r1z1=100, r1z2=200, r2=300"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml105(td)
-msgid "read_affinity ="
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml108(td)
-msgid "write_affinity = r1, r2"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml111(td)
-msgid "write_affinity ="
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml114(td)
-msgid "write_affinity_node_count = 2 * replicas"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml117(td)
-msgid ""
-"swift_owner_headers = x-container-read, x-container-write, x-container-sync-"
-"key, x-container-sync-to, x-account-meta-temp-url-key, x-account-meta-temp-"
-"url-key-2, x-account-access-control"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-app-proxy-server.xml117(td)
-msgid ""
-"the sample These are the headers whose conf file for values will only be "
-"shown to the list of swift_owners. The exact default definition of a "
-"swift_owner is headers&gt; up to the auth system in use, but usually "
-"indicates administrative responsibilities. paste.deploy to use for auth. To "
-"use tempauth set to: `egg:swift#tempauth` each request"
-msgstr ""
-
-#: ./doc/common/tables/nova-keymgr.xml8(caption)
-#: ./doc/common/tables/cinder-keymgr.xml8(caption)
-msgid "Description of configuration options for keymgr"
-msgstr ""
-
-#: ./doc/common/tables/nova-keymgr.xml19(th)
-#: ./doc/common/tables/cinder-keymgr.xml19(th)
-msgid "[keymgr]"
-msgstr ""
-
-#: ./doc/common/tables/nova-keymgr.xml22(td)
-msgid "api_class = nova.keymgr.conf_key_mgr.ConfKeyManager"
-msgstr ""
-
-#: ./doc/common/tables/nova-keymgr.xml23(td)
-#: ./doc/common/tables/cinder-keymgr.xml23(td)
-msgid "(StrOpt) The full class name of the key manager API class"
-msgstr ""
-
-#: ./doc/common/tables/nova-keymgr.xml26(td)
-#: ./doc/common/tables/cinder-keymgr.xml26(td)
-msgid "fixed_key = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-keymgr.xml27(td)
-#: ./doc/common/tables/cinder-keymgr.xml27(td)
-msgid "(StrOpt) Fixed key returned by key manager, specified in hex"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml7(literal)
-msgid "[filter:dlo]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml18(td)
-msgid "use = egg:swift#dlo"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml30(td)
-msgid "rate_limit_after_segment = 10"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml21(td)
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml30(td)
-msgid ""
-"Rate limit the download of large object segments after this segment is "
-"downloaded."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml24(td)
-msgid "rate_limit_segments_per_sec = 1"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml24(td)
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml33(td)
-msgid ""
-"Rate limit large object downloads at this rate. contact for a normal "
-"request. You can use '* replicas' at the end to have it use the number given"
-" times the number of replicas for the ring being used for the request. "
-"paste.deploy to use for auth. To use tempauth set to: `egg:swift#tempauth` "
-"each request"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml27(td)
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml36(td)
-msgid "max_get_time = 86400"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml22(td)
-msgid "allow_bulk = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml23(td)
-msgid "(BoolOpt) Allow the usage of the bulk API"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml26(td)
-msgid "allow_pagination = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml27(td)
-msgid "(BoolOpt) Allow the usage of the pagination"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml30(td)
-msgid "allow_sorting = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml31(td)
-msgid "(BoolOpt) Allow the usage of the sorting"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml34(td)
-msgid "api_extensions_path ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml35(td)
-msgid "(StrOpt) The path for API extensions"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml39(td)
-msgid "(StrOpt) The API paste config file to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml43(td)
-msgid "(IntOpt) Max header line to accommodate large tokens"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml46(td)
-#: ./doc/common/tables/ceilometer-api.xml26(td)
-#: ./doc/common/tables/keystone-api.xml54(td)
-msgid "max_request_body_size = 114688"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml47(td)
-msgid "(IntOpt) the maximum body size per each request(bytes)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml50(td)
-msgid "pagination_max_limit = -1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml51(td)
-msgid ""
-"(StrOpt) The maximum number of items returned in a single response, value "
-"was 'infinite' or negative integer means no limit"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml54(td)
-#: ./doc/common/tables/nova-periodic.xml30(td)
-#: ./doc/common/tables/cinder-common.xml158(td)
-msgid "run_external_periodic_tasks = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml55(td)
-#: ./doc/common/tables/nova-periodic.xml31(td)
-#: ./doc/common/tables/cinder-common.xml159(td)
-msgid ""
-"(BoolOpt) Some periodic tasks can be run in a separate process. Should we "
-"run them here?"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml58(td)
-msgid "service_plugins ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml59(td)
-msgid "(ListOpt) The service plugins Neutron will use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml62(th)
-msgid "[service_providers]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml65(td)
-msgid "service_provider = []"
-msgstr ""
-
-#: ./doc/common/tables/neutron-api.xml66(td)
-msgid ""
-"(MultiStrOpt) Defines providers for advanced services using the format: "
-"&lt;service_type&gt;:&lt;name&gt;:&lt;driver&gt;[:default]"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-redis.xml23(td)
-msgid ""
-"(StrOpt) Name of this node, which must be valid in an AMQP key. Can be an "
-"opaque identifier. For ZeroMQ only, must be a valid host name, FQDN, or IP "
-"address."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-swift.xml8(caption)
-#: ./doc/common/tables/trove-swift.xml8(caption)
-#: ./doc/common/tables/glance-swift.xml8(caption)
-msgid "Description of configuration options for swift"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-swift.xml22(td)
-msgid "reseller_prefix = AUTH_"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-swift.xml23(td)
-msgid ""
-"(StrOpt) Swift reseller prefix. Must be on par with reseller_prefix in "
-"proxy-server.conf."
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml8(caption)
-msgid "Description of configuration options for hplefthand"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml22(td)
-msgid "hplefthand_api_url = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml23(td)
-msgid ""
-"(StrOpt) HP LeftHand WSAPI Server Url like https://&lt;LeftHand "
-"ip&gt;:8081/lhos"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml26(td)
-msgid "hplefthand_clustername = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml27(td)
-msgid "(StrOpt) HP LeftHand cluster name"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml30(td)
-msgid "hplefthand_debug = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml31(td)
-msgid "(BoolOpt) Enable HTTP debugging to LeftHand"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml34(td)
-msgid "hplefthand_iscsi_chap_enabled = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml35(td)
-msgid ""
-"(BoolOpt) Configure CHAP authentication for iSCSI connections (Default: "
-"Disabled)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml38(td)
-msgid "hplefthand_password = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml39(td)
-msgid "(StrOpt) HP LeftHand Super user password"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml42(td)
-msgid "hplefthand_username = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hplefthand.xml43(td)
-msgid "(StrOpt) HP LeftHand Super user username"
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml8(caption)
-#: ./doc/common/tables/glance-testing.xml8(caption)
-#: ./doc/common/tables/neutron-testing.xml8(caption)
-msgid "Description of configuration options for testing"
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml22(td)
-#: ./doc/common/tables/cinder-rpc.xml22(td)
-#: ./doc/common/tables/keystone-rpc.xml22(td)
-msgid ""
-"allowed_rpc_exception_modules = oslo.messaging.exceptions, nova.exception, "
-"cinder.exception, exceptions"
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml27(td)
-msgid ""
-"(StrOpt) Enable eventlet backdoor. Acceptable values are 0, &lt;port&gt; and"
-" &lt;start&gt;:&lt;end&gt;, where 0 results in listening on a random tcp "
-"port number, &lt;port&gt; results in listening on the specified port number "
-"and not enabling backdoorif it is in use and &lt;start&gt;:&lt;end&gt; "
-"results in listening on the smallest unused port number within the specified"
-" range of port numbers. The chosen port is displayed in the service's log "
-"file."
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml30(td)
-msgid "fake_call = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml31(td)
-msgid "(BoolOpt) If True, skip using the queue and make local calls"
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml34(td)
-msgid "fake_network = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml35(td)
-msgid "(BoolOpt) If passed, use fake network devices and addresses"
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml38(td)
-#: ./doc/common/tables/cinder-rpc.xml42(td)
-#: ./doc/common/tables/heat-amqp.xml42(td)
-#: ./doc/common/tables/glance-rabbitmq.xml26(td)
-#: ./doc/common/tables/keystone-rabbit.xml22(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml22(td)
-#: ./doc/common/tables/neutron-testing.xml26(td)
-#: ./doc/common/tables/trove-amqp.xml38(td)
-msgid "fake_rabbit = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml39(td)
-#: ./doc/common/tables/cinder-rpc.xml43(td)
-#: ./doc/common/tables/glance-rabbitmq.xml27(td)
-#: ./doc/common/tables/keystone-rabbit.xml23(td)
-msgid "(BoolOpt) If passed, use a fake RabbitMQ provider."
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml42(td)
-#: ./doc/common/tables/cinder-common.xml110(td)
-msgid "monkey_patch = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml43(td)
-msgid "(BoolOpt) Whether to log monkey patching"
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml46(td)
-msgid ""
-"monkey_patch_modules = "
-"nova.api.ec2.cloud:nova.notifications.notify_decorator, "
-"nova.compute.api:nova.notifications.notify_decorator"
-msgstr ""
-
-#: ./doc/common/tables/nova-testing.xml47(td)
-#: ./doc/common/tables/cinder-common.xml115(td)
-msgid "(ListOpt) List of modules/decorators to monkey patch"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml8(caption)
-msgid "Description of configuration options for backups"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml22(td)
-msgid "backup_api_class = cinder.backup.api.API"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml23(td)
-msgid "(StrOpt) The full class name of the volume backup API class"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml26(td)
-msgid "backup_compression_algorithm = zlib"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml27(td)
-msgid "(StrOpt) Compression algorithm (None to disable)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml30(td)
-msgid "backup_driver = cinder.backup.drivers.swift"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml31(td)
-msgid "(StrOpt) Driver to use for backups."
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml34(td)
-msgid "backup_manager = cinder.backup.manager.BackupManager"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml35(td)
-msgid "(StrOpt) full class name for the Manager for volume backup"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml38(td)
-msgid "backup_metadata_version = 1"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml39(td)
-msgid ""
-"(IntOpt) Backup metadata version to be used when backing up volume metadata."
-" If this number is bumped, make sure the service doing the restore supports "
-"the new version."
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml42(td)
-msgid "backup_name_template = backup-%s"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml43(td)
-msgid "(StrOpt) Template string to be used to generate backup names"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml46(td)
-msgid "backup_topic = cinder-backup"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml47(td)
-msgid "(StrOpt) the topic volume backup nodes listen on"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml50(td)
-#: ./doc/common/tables/nova-api.xml90(td)
-msgid "snapshot_name_template = snapshot-%s"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml51(td)
-#: ./doc/common/tables/nova-api.xml91(td)
-msgid "(StrOpt) Template string to be used to generate snapshot names"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml54(td)
-msgid "snapshot_same_host = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups.xml55(td)
-msgid ""
-"(BoolOpt) Create volume from snapshot at the host where snapshot resides"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-pipeline-main.xml7(literal)
-#: ./doc/common/tables/swift-object-server-pipeline-main.xml7(literal)
-#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml7(literal)
-#: ./doc/common/tables/swift-account-server-pipeline-main.xml7(literal)
-#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml7(literal)
-msgid "[pipeline:main]"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-pipeline-main.xml18(td)
-msgid "pipeline = healthcheck recon container-server"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ofa.xml8(caption)
-msgid "Description of configuration options for ml2_ofa"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ofa.xml22(td)
-msgid "ofp_listen_host ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ofa.xml23(td)
-msgid "(StrOpt) openflow listen host"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ofa.xml26(td)
-msgid "ofp_ssl_listen_port = 6633"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ofa.xml27(td)
-msgid "(IntOpt) openflow ssl listen port"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ofa.xml30(td)
-msgid "ofp_tcp_listen_port = 6633"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ofa.xml31(td)
-msgid "(IntOpt) openflow tcp listen port"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ofa.xml37(td)
-msgid "get_datapath_retry_times = 60"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ofa.xml38(td)
-msgid "(IntOpt) Number of seconds to retry acquiring an Open vSwitch datapath"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml27(td)
-#: ./doc/common/tables/neutron-wsgi.xml23(td)
-msgid "(IntOpt) Number of backlog requests to configure the socket with"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml39(td)
-#: ./doc/common/tables/heat-debug.xml35(td)
-#: ./doc/common/tables/neutron-logging.xml31(td)
-#: ./doc/common/tables/nova-logging.xml31(td)
-msgid "(BoolOpt) make deprecations fatal"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml42(td)
-msgid "pydev_debug = disabled"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml43(td)
-msgid ""
-"(StrOpt) Enable or disable pydev remote debugging. If value is 'auto' tries "
-"to connect to remote debugger server, but in case of error continues running"
-" with debugging disabled."
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml47(td)
-msgid "(StrOpt) Pydev debug server host (localhost by default)."
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml51(td)
-msgid "(IntOpt) Pydev debug server port (5678 by default)."
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml54(td)
-msgid "remote_cinder_client = trove.common.remote.cinder_client"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml58(td)
-msgid "remote_dns_client = trove.common.remote.dns_client"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml62(td)
-msgid "remote_guest_client = trove.common.remote.guest_client"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml66(td)
-msgid "remote_heat_client = trove.common.remote.heat_client"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml70(td)
-msgid "remote_nova_client = trove.common.remote.nova_client"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml74(td)
-msgid "remote_swift_client = trove.common.remote.swift_client"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml78(td)
-#: ./doc/common/tables/glance-logging.xml98(td)
-#: ./doc/common/tables/ceilometer-logging.xml98(td)
-#: ./doc/common/tables/neutron-logging.xml98(td)
-#: ./doc/common/tables/heat-logging.xml82(td)
-#: ./doc/common/tables/keystone-logging.xml86(td)
-#: ./doc/common/tables/nova-logging.xml102(td)
-#: ./doc/common/tables/cinder-common.xml222(td)
-msgid "verbose = False"
-msgstr ""
-
-#: ./doc/common/tables/trove-debug.xml79(td)
-#: ./doc/common/tables/glance-logging.xml99(td)
-#: ./doc/common/tables/ceilometer-logging.xml99(td)
-#: ./doc/common/tables/neutron-logging.xml99(td)
-#: ./doc/common/tables/heat-logging.xml83(td)
-#: ./doc/common/tables/keystone-logging.xml87(td)
-#: ./doc/common/tables/nova-logging.xml103(td)
-#: ./doc/common/tables/cinder-common.xml223(td)
-msgid ""
-"(BoolOpt) Print more verbose output (set logging level to INFO instead of "
-"default WARNING level)."
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-object.xml7(literal)
-msgid "[object]"
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-object.xml7(literal)
-#: ./doc/common/tables/swift-rsyncd-account.xml7(literal)
-#: ./doc/common/tables/swift-rsyncd-container.xml7(literal)
-msgid "rsyncd.conf-sample"
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-object.xml18(td)
-msgid "max connections = 8"
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-object.xml21(td)
-#: ./doc/common/tables/swift-rsyncd-account.xml21(td)
-#: ./doc/common/tables/swift-rsyncd-container.xml21(td)
-msgid "path = /srv/node"
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-object.xml24(td)
-#: ./doc/common/tables/swift-rsyncd-account.xml24(td)
-#: ./doc/common/tables/swift-rsyncd-container.xml24(td)
-msgid "read only = false"
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-object.xml27(td)
-msgid "lock file = /var/lock/object.lock"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml22(td)
-msgid "buckets_path = $state_path/buckets"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml23(td)
-msgid "(StrOpt) Path to S3 buckets"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml26(td)
-msgid "image_decryption_dir = /tmp"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml27(td)
-msgid "(StrOpt) Parent directory for tempdir used for image decryption"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml30(td)
-msgid "s3_access_key = notchecked"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml31(td)
-msgid "(StrOpt) Access key to use for S3 server for images"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml34(td)
-msgid "s3_affix_tenant = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml35(td)
-msgid ""
-"(BoolOpt) Whether to affix the tenant id to the access key when downloading "
-"from S3"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml38(td)
-msgid "s3_host = $my_ip"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml39(td)
-msgid "(StrOpt) Hostname or IP for OpenStack to use when accessing the S3 api"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml42(td)
-msgid "s3_listen = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml43(td)
-msgid "(StrOpt) IP address for S3 API to listen"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml46(td)
-msgid "s3_listen_port = 3333"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml47(td)
-msgid "(IntOpt) Port for S3 API to listen"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml50(td)
-msgid "s3_port = 3333"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml51(td)
-msgid "(IntOpt) Port used when accessing the S3 api"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml54(td)
-msgid "s3_secret_key = notchecked"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml55(td)
-msgid "(StrOpt) Secret key to use for S3 server for images"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml58(td)
-msgid "s3_use_ssl = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-s3.xml59(td)
-msgid "(BoolOpt) Whether to use SSL when talking to S3"
-msgstr ""
-
-#: ./doc/common/tables/nova-zookeeper.xml8(caption)
-msgid "Description of configuration options for zookeeper"
-msgstr ""
-
-#: ./doc/common/tables/nova-zookeeper.xml19(th)
-msgid "[zookeeper]"
-msgstr ""
-
-#: ./doc/common/tables/nova-zookeeper.xml22(td)
-msgid "address = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-zookeeper.xml23(td)
-msgid ""
-"(StrOpt) The ZooKeeper addresses for servicegroup service in the format of "
-"host1:port,host2:port,host3:port"
-msgstr ""
-
-#: ./doc/common/tables/nova-zookeeper.xml26(td)
-msgid "recv_timeout = 4000"
-msgstr ""
-
-#: ./doc/common/tables/nova-zookeeper.xml27(td)
-msgid "(IntOpt) The recv_timeout parameter for the zk session"
-msgstr ""
-
-#: ./doc/common/tables/nova-zookeeper.xml30(td)
-msgid "sg_prefix = /servicegroups"
-msgstr ""
-
-#: ./doc/common/tables/nova-zookeeper.xml31(td)
-msgid "(StrOpt) The prefix used in ZooKeeper to store ephemeral nodes"
-msgstr ""
-
-#: ./doc/common/tables/nova-zookeeper.xml34(td)
-msgid "sg_retry_interval = 5"
-msgstr ""
-
-#: ./doc/common/tables/nova-zookeeper.xml35(td)
-msgid "(IntOpt) Number of seconds to wait until retrying to join the session"
-msgstr ""
-
-#: ./doc/common/tables/cinder-rpc.xml38(td)
-msgid "default_timeout = 20"
-msgstr ""
-
-#: ./doc/common/tables/cinder-rpc.xml39(td)
-msgid "(IntOpt) Default Time Out For CLI operations in minutes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-rpc.xml83(td)
-#: ./doc/common/tables/glance-redis.xml27(td)
-#: ./doc/common/tables/keystone-redis.xml35(td)
-#: ./doc/common/tables/nova-redis.xml23(td)
-msgid "(StrOpt) Password for Redis server (optional)."
-msgstr ""
-
-#: ./doc/common/tables/cinder-rpc.xml234(td)
-msgid "volume_topic = cinder-volume"
-msgstr ""
-
-#: ./doc/common/tables/cinder-rpc.xml235(td)
-msgid "(StrOpt) the topic volume nodes listen on"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml23(td)
-msgid "(StrOpt) File name for the paste.deploy config for cinder-api"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml26(td)
-msgid "api_rate_limit = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml27(td)
-msgid "(BoolOpt) whether to rate limit the api"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml34(td)
-#: ./doc/common/tables/ceilometer-api.xml22(td)
-#: ./doc/common/tables/glance-api.xml38(td)
-msgid "enable_v1_api = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml35(td)
-msgid "(BoolOpt) Deploy v1 of the Cinder API."
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml38(td)
-#: ./doc/common/tables/glance-api.xml46(td)
-msgid "enable_v2_api = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml39(td)
-msgid "(BoolOpt) Deploy v2 of the Cinder API."
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml42(td)
-msgid "extra_capabilities = {}"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml43(td)
-msgid ""
-"(StrOpt) User defined capabilities, a JSON formatted string specifying "
-"key/value pairs."
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml50(td)
-#: ./doc/common/tables/nova-policy.xml46(td)
-msgid "osapi_max_limit = 1000"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml51(td)
-msgid ""
-"(IntOpt) the maximum number of items returned in a single response from a "
-"collection resource"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml54(td)
-#: ./doc/common/tables/nova-policy.xml50(td)
-msgid "osapi_max_request_body_size = 114688"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml55(td)
-msgid "(IntOpt) Max size for body of a request"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml58(td)
-msgid "osapi_volume_base_URL = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml59(td)
-msgid ""
-"(StrOpt) Base URL that will be presented to users in links to the OpenStack "
-"Volume API"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml62(td)
-msgid "osapi_volume_ext_list ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml63(td)
-msgid ""
-"(ListOpt) Specify list of extensions to load when using "
-"osapi_volume_extension option with cinder.api.contrib.select_extensions"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml66(td)
-msgid "osapi_volume_extension = ['cinder.api.contrib.standard_extensions']"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml67(td)
-msgid "(MultiStrOpt) osapi volume extension to load"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml70(td)
-msgid "osapi_volume_listen = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml71(td)
-msgid "(StrOpt) IP address for OpenStack Volume API to listen"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml74(td)
-msgid "osapi_volume_listen_port = 8776"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml75(td)
-msgid "(IntOpt) port for os volume api to listen"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml78(td)
-msgid "osapi_volume_workers = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml79(td)
-msgid "(IntOpt) Number of workers for OpenStack Volume API service"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml82(td)
-msgid "transfer_api_class = cinder.transfer.api.API"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml83(td)
-msgid "(StrOpt) The full class name of the volume transfer API class"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml86(td)
-msgid "volume_api_class = cinder.volume.api.API"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml90(td)
-msgid "volume_name_template = volume-%s"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml91(td)
-msgid "(StrOpt) Template string to be used to generate volume names"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml94(td)
-msgid "volume_transfer_key_length = 16"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml95(td)
-msgid "(IntOpt) The number of characters in the autogenerated auth key."
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml98(td)
-msgid "volume_transfer_salt_length = 8"
-msgstr ""
-
-#: ./doc/common/tables/cinder-api.xml99(td)
-msgid "(IntOpt) The number of characters in the salt."
-msgstr ""
-
-#: ./doc/common/tables/cinder-windows.xml8(caption)
-msgid "Description of configuration options for windows"
-msgstr ""
-
-#: ./doc/common/tables/cinder-windows.xml22(td)
-msgid "windows_iscsi_lun_path = C:\\iSCSIVirtualDisks"
-msgstr ""
-
-#: ./doc/common/tables/cinder-windows.xml23(td)
-msgid "(StrOpt) Path to store VHD backed volumes"
-msgstr ""
-
-#: ./doc/common/tables/glance-vmware.xml8(caption)
-#: ./doc/common/tables/ceilometer-vmware.xml8(caption)
-#: ./doc/common/tables/cinder-vmware.xml8(caption)
-#: ./doc/common/tables/nova-vmware.xml8(caption)
-#: ./doc/common/tables/neutron-vmware.xml8(caption)
-msgid "Description of configuration options for vmware"
-msgstr ""
-
 #: ./doc/common/tables/glance-vmware.xml22(td)
 msgid "vmware_api_insecure = False"
 msgstr ""
@@ -36135,720 +37129,12 @@ msgid ""
 " server."
 msgstr ""
 
-#: ./doc/common/tables/swift-object-server-pipeline-main.xml18(td)
-msgid "pipeline = healthcheck recon object-server"
+#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml7(literal)
+msgid "[filter:container-quotas]"
 msgstr ""
 
-#: ./doc/common/tables/trove-backup.xml8(caption)
-msgid "Description of configuration options for backup"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml22(td)
-msgid "backup_aes_cbc_key = default_aes_cbc_key"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml23(td)
-msgid "(StrOpt) Default OpenSSL aes_cbc key."
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml26(td)
-msgid "backup_chunk_size = 65536"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml27(td)
-msgid ""
-"(IntOpt) Chunk size to stream to swift container. This should be in "
-"multiples of 128 bytes, since this is the size of an md5 digest block "
-"allowing the process to update the file checksum during streaming. See: "
-"http://stackoverflow.com/questions/1131220/"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml30(td)
-msgid ""
-"backup_incremental_strategy = {'InnoBackupEx': 'InnoBackupExIncremental'}"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml31(td)
-msgid ""
-"(DictOpt) Incremental Backup Runner Based off of the default strategy. For "
-"strategies that do not implement an incremental the runner will use the "
-"default full backup."
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml34(td)
-msgid "backup_namespace = trove.guestagent.strategies.backup.mysql_impl"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml35(td)
-msgid "(StrOpt) Namespace to load backup strategies from."
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml38(td)
-msgid "backup_runner = trove.guestagent.backup.backup_types.InnoBackupEx"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml42(td)
-msgid "backup_runner_options = {}"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml43(td)
-msgid "(DictOpt) Additional options to be passed to the backup runner."
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml46(td)
-msgid "backup_segment_max_size = 2147483648"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml47(td)
-msgid "(IntOpt) Maximum size of each segment of the backup file."
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml50(td)
-#: ./doc/common/tables/trove-db_mysql.xml22(td)
-#: ./doc/common/tables/trove-db_percona.xml22(td)
-msgid "backup_strategy = InnoBackupEx"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml54(td)
-msgid "backup_swift_container = database_backups"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml58(td)
-msgid "backup_use_gzip_compression = True"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml59(td)
-msgid "(BoolOpt) Compress backups using gzip."
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml62(td)
-msgid "backup_use_openssl_encryption = True"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml63(td)
-msgid "(BoolOpt) Encrypt backups using OpenSSL."
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml66(td)
-msgid "backup_use_snet = False"
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml67(td)
-msgid "(BoolOpt) Send backup files over snet."
-msgstr ""
-
-#: ./doc/common/tables/trove-backup.xml70(td)
-msgid "backups_page_size = 20"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml8(caption)
-msgid "Description of configuration options for san"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml22(td)
-msgid "san_clustername ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml23(td)
-msgid "(StrOpt) Cluster name to use for creating volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml26(td)
-msgid "san_ip ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml27(td)
-msgid "(StrOpt) IP address of SAN controller"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml30(td)
-msgid "san_is_local = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml31(td)
-msgid ""
-"(BoolOpt) Execute commands locally instead of over SSH; use if the volume "
-"service is running on the SAN device"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml34(td)
-msgid "san_login = admin"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml35(td)
-msgid "(StrOpt) Username for SAN controller"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml38(td)
-msgid "san_password ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml39(td)
-msgid "(StrOpt) Password for SAN controller"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml42(td)
-msgid "san_private_key ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml43(td)
-msgid "(StrOpt) Filename of private key to use for SSH authentication"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml46(td)
-msgid "san_ssh_port = 22"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml47(td)
-msgid "(IntOpt) SSH port to use with SAN"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml50(td)
-msgid "san_thin_provision = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml51(td)
-msgid "(BoolOpt) Use thin provisioning for SAN volumes?"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml54(td)
-msgid "ssh_conn_timeout = 30"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml55(td)
-msgid "(IntOpt) SSH connection timeout in seconds"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml58(td)
-msgid "ssh_max_pool_conn = 5"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml59(td)
-msgid "(IntOpt) Maximum ssh connections in the pool"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml62(td)
-msgid "ssh_min_pool_conn = 1"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san.xml63(td)
-msgid "(IntOpt) Minimum ssh connections in the pool"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-app-account-server.xml7(literal)
-msgid "[app:account-server]"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-app-account-server.xml18(td)
-msgid "use = egg:swift#account"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-app-account-server.xml21(td)
-msgid "set log_name = account-server"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-app-account-server.xml30(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml30(td)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml30(td)
-msgid "set log_requests = true"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-app-account-server.xml30(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml30(td)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml30(td)
-msgid "Whether or not to log requests"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-app-account-server.xml39(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml48(td)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml60(td)
-msgid "replication_server = false"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-app-account-server.xml39(td)
-#: ./doc/common/tables/swift-container-server-app-container-server.xml48(td)
-#: ./doc/common/tables/swift-object-server-app-object-server.xml60(td)
-msgid ""
-"If defined, tells server how to handle replication verbs in requests. When "
-"set to True (or 1), only replication verbs will be accepted. When set to "
-"False, replication verbs will be rejected. When undefined, server will "
-"accept any verb in the request."
-msgstr ""
-
-#: ./doc/common/tables/cinder-keymgr.xml22(td)
-msgid "api_class = cinder.keymgr.conf_key_mgr.ConfKeyManager"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml8(caption)
-#: ./doc/common/tables/neutron-db.xml8(caption)
-#: ./doc/common/tables/glance-db.xml8(caption)
-msgid "Description of configuration options for db"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml22(td)
-msgid "db_driver = nova.db"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml23(td)
-msgid "(StrOpt) The driver to use for database access"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml29(td)
-msgid "db_check_interval = 60"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml30(td)
-msgid ""
-"(IntOpt) Interval, in seconds, for getting fresh cell information from the "
-"database."
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml36(td)
-#: ./doc/common/tables/heat-database.xml37(td)
-#: ./doc/common/tables/ceilometer-database.xml41(td)
-#: ./doc/common/tables/cinder-storage.xml137(td)
-#: ./doc/common/tables/neutron-db.xml33(td)
-#: ./doc/common/tables/keystone-database.xml22(td)
-#: ./doc/common/tables/glance-db.xml22(td)
-msgid "backend = sqlalchemy"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml37(td)
-#: ./doc/common/tables/heat-database.xml38(td)
-#: ./doc/common/tables/ceilometer-database.xml42(td)
-#: ./doc/common/tables/cinder-storage.xml138(td)
-#: ./doc/common/tables/cinder-database.xml23(td)
-#: ./doc/common/tables/neutron-db.xml34(td)
-#: ./doc/common/tables/keystone-database.xml23(td)
-#: ./doc/common/tables/glance-db.xml23(td)
-msgid "(StrOpt) The backend to use for db"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml40(td)
-#: ./doc/common/tables/keystone-database.xml26(td)
-#: ./doc/common/tables/glance-db.xml26(td)
-msgid "connection = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml41(td)
-#: ./doc/common/tables/heat-database.xml42(td)
-#: ./doc/common/tables/ceilometer-database.xml46(td)
-#: ./doc/common/tables/cinder-connection.xml23(td)
-#: ./doc/common/tables/neutron-db.xml38(td)
-#: ./doc/common/tables/keystone-database.xml27(td)
-#: ./doc/common/tables/glance-db.xml27(td)
-msgid ""
-"(StrOpt) The SQLAlchemy connection string used to connect to the database"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml44(td)
-#: ./doc/common/tables/heat-database.xml45(td)
-#: ./doc/common/tables/ceilometer-database.xml49(td)
-#: ./doc/common/tables/cinder-connection.xml26(td)
-#: ./doc/common/tables/neutron-db.xml41(td)
-#: ./doc/common/tables/keystone-database.xml30(td)
-#: ./doc/common/tables/glance-db.xml30(td)
-msgid "connection_debug = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml45(td)
-#: ./doc/common/tables/heat-database.xml46(td)
-#: ./doc/common/tables/ceilometer-database.xml50(td)
-#: ./doc/common/tables/cinder-connection.xml27(td)
-#: ./doc/common/tables/neutron-db.xml42(td)
-#: ./doc/common/tables/keystone-database.xml31(td)
-#: ./doc/common/tables/glance-db.xml31(td)
-msgid ""
-"(IntOpt) Verbosity of SQL debugging information. 0=None, 100=Everything"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml48(td)
-#: ./doc/common/tables/heat-database.xml49(td)
-#: ./doc/common/tables/ceilometer-database.xml53(td)
-#: ./doc/common/tables/cinder-connection.xml30(td)
-#: ./doc/common/tables/neutron-db.xml45(td)
-#: ./doc/common/tables/keystone-database.xml34(td)
-#: ./doc/common/tables/glance-db.xml34(td)
-msgid "connection_trace = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml49(td)
-#: ./doc/common/tables/heat-database.xml50(td)
-#: ./doc/common/tables/ceilometer-database.xml54(td)
-#: ./doc/common/tables/cinder-connection.xml31(td)
-#: ./doc/common/tables/neutron-db.xml46(td)
-#: ./doc/common/tables/keystone-database.xml35(td)
-#: ./doc/common/tables/glance-db.xml35(td)
-msgid "(BoolOpt) Add python stack traces to SQL as comment strings"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml52(td)
-#: ./doc/common/tables/neutron-db.xml49(td)
-#: ./doc/common/tables/keystone-database.xml38(td)
-#: ./doc/common/tables/glance-db.xml38(td)
-msgid "db_inc_retry_interval = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml53(td)
-#: ./doc/common/tables/neutron-db.xml50(td)
-#: ./doc/common/tables/keystone-database.xml39(td)
-#: ./doc/common/tables/glance-db.xml39(td)
-msgid ""
-"(BoolOpt) Whether to increase interval between db connection retries, up to "
-"db_max_retry_interval"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml56(td)
-#: ./doc/common/tables/neutron-db.xml53(td)
-#: ./doc/common/tables/keystone-database.xml42(td)
-#: ./doc/common/tables/glance-db.xml42(td)
-msgid "db_max_retries = 20"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml57(td)
-#: ./doc/common/tables/neutron-db.xml54(td)
-#: ./doc/common/tables/keystone-database.xml43(td)
-#: ./doc/common/tables/glance-db.xml43(td)
-msgid ""
-"(IntOpt) maximum db connection retries before error is raised. (setting -1 "
-"implies an infinite retry count)"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml60(td)
-#: ./doc/common/tables/neutron-db.xml57(td)
-#: ./doc/common/tables/keystone-database.xml46(td)
-#: ./doc/common/tables/glance-db.xml46(td)
-msgid "db_max_retry_interval = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml61(td)
-#: ./doc/common/tables/neutron-db.xml58(td)
-#: ./doc/common/tables/keystone-database.xml47(td)
-#: ./doc/common/tables/glance-db.xml47(td)
-msgid ""
-"(IntOpt) max seconds between db connection retries, if db_inc_retry_interval"
-" is enabled"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml64(td)
-#: ./doc/common/tables/neutron-db.xml61(td)
-#: ./doc/common/tables/keystone-database.xml50(td)
-#: ./doc/common/tables/glance-db.xml50(td)
-msgid "db_retry_interval = 1"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml65(td)
-#: ./doc/common/tables/neutron-db.xml62(td)
-#: ./doc/common/tables/keystone-database.xml51(td)
-#: ./doc/common/tables/glance-db.xml51(td)
-msgid "(IntOpt) seconds between db connection retries"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml68(td)
-#: ./doc/common/tables/heat-database.xml53(td)
-#: ./doc/common/tables/ceilometer-database.xml57(td)
-#: ./doc/common/tables/cinder-common.xml229(td)
-#: ./doc/common/tables/neutron-db.xml65(td)
-#: ./doc/common/tables/keystone-database.xml54(td)
-#: ./doc/common/tables/glance-db.xml54(td)
-msgid "idle_timeout = 3600"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml69(td)
-#: ./doc/common/tables/ceilometer-database.xml58(td)
-#: ./doc/common/tables/neutron-db.xml66(td)
-#: ./doc/common/tables/keystone-database.xml55(td)
-#: ./doc/common/tables/glance-db.xml55(td)
-msgid "(IntOpt) Timeout before idle sql connections are reaped"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml72(td)
-#: ./doc/common/tables/heat-database.xml57(td)
-#: ./doc/common/tables/ceilometer-database.xml61(td)
-#: ./doc/common/tables/cinder-storage.xml141(td)
-#: ./doc/common/tables/keystone-database.xml58(td)
-#: ./doc/common/tables/glance-db.xml58(td)
-msgid "max_overflow = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml73(td)
-#: ./doc/common/tables/heat-database.xml58(td)
-#: ./doc/common/tables/ceilometer-database.xml62(td)
-#: ./doc/common/tables/cinder-storage.xml142(td)
-#: ./doc/common/tables/neutron-db.xml70(td)
-#: ./doc/common/tables/keystone-database.xml59(td)
-#: ./doc/common/tables/glance-db.xml59(td)
-msgid "(IntOpt) If set, use this value for max_overflow with sqlalchemy"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml76(td)
-#: ./doc/common/tables/heat-database.xml61(td)
-#: ./doc/common/tables/ceilometer-database.xml65(td)
-#: ./doc/common/tables/keystone-database.xml62(td)
-#: ./doc/common/tables/glance-db.xml62(td)
-msgid "max_pool_size = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml77(td)
-#: ./doc/common/tables/heat-database.xml62(td)
-#: ./doc/common/tables/ceilometer-database.xml66(td)
-#: ./doc/common/tables/cinder-storage.xml146(td)
-#: ./doc/common/tables/neutron-db.xml74(td)
-#: ./doc/common/tables/keystone-database.xml63(td)
-#: ./doc/common/tables/glance-db.xml63(td)
-msgid "(IntOpt) Maximum number of SQL connections to keep open in a pool"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml80(td)
-#: ./doc/common/tables/heat-database.xml65(td)
-#: ./doc/common/tables/ceilometer-database.xml69(td)
-#: ./doc/common/tables/cinder-storage.xml149(td)
-#: ./doc/common/tables/neutron-db.xml77(td)
-#: ./doc/common/tables/keystone-database.xml66(td)
-#: ./doc/common/tables/glance-db.xml66(td)
-msgid "max_retries = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml81(td)
-#: ./doc/common/tables/ceilometer-database.xml70(td)
-#: ./doc/common/tables/neutron-db.xml78(td)
-#: ./doc/common/tables/keystone-database.xml67(td)
-#: ./doc/common/tables/glance-db.xml67(td)
-msgid ""
-"(IntOpt) Maximum db connection retries during startup. (setting -1 implies "
-"an infinite retry count)"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml84(td)
-#: ./doc/common/tables/heat-database.xml69(td)
-#: ./doc/common/tables/ceilometer-database.xml73(td)
-#: ./doc/common/tables/cinder-storage.xml153(td)
-#: ./doc/common/tables/neutron-db.xml81(td)
-#: ./doc/common/tables/keystone-database.xml70(td)
-#: ./doc/common/tables/glance-db.xml70(td)
-msgid "min_pool_size = 1"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml85(td)
-#: ./doc/common/tables/heat-database.xml70(td)
-#: ./doc/common/tables/ceilometer-database.xml74(td)
-#: ./doc/common/tables/cinder-storage.xml154(td)
-#: ./doc/common/tables/neutron-db.xml82(td)
-#: ./doc/common/tables/keystone-database.xml71(td)
-#: ./doc/common/tables/glance-db.xml71(td)
-msgid "(IntOpt) Minimum number of SQL connections to keep open in a pool"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml88(td)
-msgid "mysql_sql_mode = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml89(td)
-msgid ""
-"(StrOpt) The SQL mode to be used for MySQL sessions (default is empty, "
-"meaning do not override any server-side SQL mode setting)"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml92(td)
-#: ./doc/common/tables/heat-database.xml73(td)
-#: ./doc/common/tables/ceilometer-database.xml77(td)
-#: ./doc/common/tables/keystone-database.xml78(td)
-#: ./doc/common/tables/glance-db.xml78(td)
-msgid "pool_timeout = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml93(td)
-#: ./doc/common/tables/heat-database.xml74(td)
-#: ./doc/common/tables/ceilometer-database.xml78(td)
-#: ./doc/common/tables/neutron-db.xml86(td)
-#: ./doc/common/tables/keystone-database.xml79(td)
-#: ./doc/common/tables/glance-db.xml79(td)
-msgid "(IntOpt) If set, use this value for pool_timeout with sqlalchemy"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml96(td)
-#: ./doc/common/tables/heat-database.xml77(td)
-#: ./doc/common/tables/ceilometer-database.xml81(td)
-#: ./doc/common/tables/cinder-common.xml233(td)
-#: ./doc/common/tables/neutron-db.xml89(td)
-#: ./doc/common/tables/keystone-database.xml82(td)
-#: ./doc/common/tables/glance-db.xml82(td)
-msgid "retry_interval = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml97(td)
-#: ./doc/common/tables/ceilometer-database.xml82(td)
-#: ./doc/common/tables/neutron-db.xml90(td)
-#: ./doc/common/tables/keystone-database.xml83(td)
-#: ./doc/common/tables/glance-db.xml83(td)
-msgid "(IntOpt) Interval between retries of opening a sql connection"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml100(td)
-msgid "slave_connection = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml101(td)
-#: ./doc/common/tables/heat-database.xml82(td)
-#: ./doc/common/tables/ceilometer-database.xml86(td)
-#: ./doc/common/tables/neutron-db.xml94(td)
-msgid ""
-"(StrOpt) The SQLAlchemy connection string used to connect to the slave "
-"database"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml104(td)
-msgid "sqlite_db = nova.sqlite"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml105(td)
-#: ./doc/common/tables/ceilometer-database.xml31(td)
-#: ./doc/common/tables/neutron-db.xml23(td)
-#: ./doc/common/tables/keystone-database.xml87(td)
-#: ./doc/common/tables/glance-db.xml87(td)
-msgid "(StrOpt) The file name to use with SQLite"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml108(td)
-#: ./doc/common/tables/heat-database.xml30(td)
-#: ./doc/common/tables/ceilometer-database.xml34(td)
-#: ./doc/common/tables/cinder-common.xml170(td)
-#: ./doc/common/tables/neutron-db.xml26(td)
-#: ./doc/common/tables/keystone-database.xml90(td)
-#: ./doc/common/tables/glance-db.xml90(td)
-msgid "sqlite_synchronous = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml109(td)
-#: ./doc/common/tables/ceilometer-database.xml35(td)
-#: ./doc/common/tables/neutron-db.xml27(td)
-#: ./doc/common/tables/keystone-database.xml91(td)
-#: ./doc/common/tables/glance-db.xml91(td)
-msgid "(BoolOpt) If True, SQLite uses synchronous mode"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml112(td)
-#: ./doc/common/tables/neutron-db.xml97(td)
-#: ./doc/common/tables/keystone-database.xml94(td)
-#: ./doc/common/tables/glance-db.xml94(td)
-msgid "use_db_reconnect = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-db.xml113(td)
-#: ./doc/common/tables/neutron-db.xml98(td)
-#: ./doc/common/tables/keystone-database.xml95(td)
-#: ./doc/common/tables/glance-db.xml95(td)
-msgid ""
-"(BoolOpt) Enable the experimental use of database reconnect on connection "
-"lost"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_vxlan.xml8(caption)
-msgid "Description of configuration options for ml2_vxlan"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_vxlan.xml19(th)
-msgid "[ml2_type_vxlan]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_vxlan.xml22(td)
-msgid "vni_ranges ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_vxlan.xml23(td)
-msgid ""
-"(ListOpt) Comma-separated list of &lt;vni_min&gt;:&lt;vni_max&gt; tuples "
-"enumerating ranges of VXLAN VNI IDs that are available for tenant network "
-"allocation"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_vxlan.xml26(td)
-msgid "vxlan_group = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_vxlan.xml27(td)
-msgid ""
-"(StrOpt) Multicast group for VXLAN. If unset, disables VXLAN multicast mode."
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml26(td)
-#: ./doc/common/tables/ceilometer-logging.xml26(td)
-#: ./doc/common/tables/keystone-logging.xml22(td)
-msgid ""
-"default_log_levels = amqp=WARN, amqplib=WARN, boto=WARN, qpid=WARN, "
-"sqlalchemy=WARN, suds=INFO, iso8601=WARN, "
-"requests.packages.urllib3.connectionpool=WARN"
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml27(td)
-#: ./doc/common/tables/ceilometer-logging.xml27(td)
-#: ./doc/common/tables/keystone-logging.xml23(td)
-#: ./doc/common/tables/cinder-common.xml35(td)
-msgid "(ListOpt) List of logger=LEVEL pairs"
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml63(td)
-#: ./doc/common/tables/ceilometer-logging.xml63(td)
-#: ./doc/common/tables/keystone-logging.xml55(td)
-#: ./doc/common/tables/cinder-common.xml95(td)
-msgid "(StrOpt) Format string to use for log messages with context"
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml67(td)
-#: ./doc/common/tables/ceilometer-logging.xml67(td)
-#: ./doc/common/tables/keystone-logging.xml59(td)
-#: ./doc/common/tables/cinder-common.xml99(td)
-msgid "(StrOpt) Data to append to log format when level is DEBUG"
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml71(td)
-#: ./doc/common/tables/ceilometer-logging.xml71(td)
-#: ./doc/common/tables/keystone-logging.xml63(td)
-#: ./doc/common/tables/cinder-common.xml103(td)
-msgid "(StrOpt) Format string to use for log messages without context"
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml75(td)
-#: ./doc/common/tables/ceilometer-logging.xml75(td)
-#: ./doc/common/tables/keystone-logging.xml67(td)
-#: ./doc/common/tables/cinder-common.xml107(td)
-msgid "(StrOpt) Prefix each line of exception output with this format"
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml83(td)
-#: ./doc/common/tables/ceilometer-logging.xml83(td)
-#: ./doc/common/tables/keystone-logging.xml71(td)
-#: ./doc/common/tables/cinder-common.xml195(td)
-msgid "(StrOpt) Syslog facility to receive log lines"
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml91(td)
-#: ./doc/common/tables/ceilometer-logging.xml91(td)
-#: ./doc/common/tables/keystone-logging.xml79(td)
-#: ./doc/common/tables/nova-logging.xml95(td)
-#: ./doc/common/tables/cinder-common.xml215(td)
-msgid ""
-"(BoolOpt) Use syslog for logging. Existing syslog format is DEPRECATED "
-"during I, and then will be changed in J to honor RFC5424"
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml94(td)
-#: ./doc/common/tables/ceilometer-logging.xml94(td)
-#: ./doc/common/tables/keystone-logging.xml82(td)
-#: ./doc/common/tables/nova-logging.xml98(td)
-#: ./doc/common/tables/cinder-common.xml218(td)
-msgid "use_syslog_rfc_format = False"
-msgstr ""
-
-#: ./doc/common/tables/glance-logging.xml95(td)
-#: ./doc/common/tables/ceilometer-logging.xml95(td)
-#: ./doc/common/tables/keystone-logging.xml83(td)
-#: ./doc/common/tables/nova-logging.xml99(td)
-#: ./doc/common/tables/cinder-common.xml219(td)
-msgid ""
-"(BoolOpt) (Optional) Use syslog rfc5424 format for logging. If enabled, will"
-" add APP-NAME (RFC5424) before the MSG part of the syslog message. The old "
-"format without APP-NAME is deprecated in I, and will be removed in J."
+#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml18(td)
+msgid "use = egg:swift#container_quotas"
 msgstr ""
 
 #: ./doc/common/tables/cinder-zoning.xml8(caption)
@@ -36879,642 +37165,756 @@ msgid ""
 "fabric"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning.xml33(td)
-#: ./doc/common/tables/cinder-zoning_fabric.xml50(td)
-msgid "zoning_policy = initiator-target"
-msgstr ""
-
 #: ./doc/common/tables/cinder-zoning.xml34(td)
 msgid "(StrOpt) Zoning policy configured by user"
 msgstr ""
 
-#: ./doc/common/tables/glance-wsgi.xml8(caption)
-#: ./doc/common/tables/neutron-wsgi.xml8(caption)
-#: ./doc/common/tables/nova-wsgi.xml8(caption)
-msgid "Description of configuration options for wsgi"
+#: ./doc/common/tables/heat-notification.xml8(caption)
+#: ./doc/common/tables/keystone-notification.xml8(caption)
+msgid "Description of configuration options for notification"
 msgstr ""
 
-#: ./doc/common/tables/glance-wsgi.xml23(td)
-msgid "(IntOpt) port for eventlet backdoor to listen"
+#: ./doc/common/tables/heat-notification.xml22(td)
+#: ./doc/common/tables/keystone-notification.xml22(td)
+msgid "onready = None"
 msgstr ""
 
-#: ./doc/common/tables/glance-wsgi.xml26(td)
-msgid "eventlet_hub = poll"
-msgstr ""
-
-#: ./doc/common/tables/glance-wsgi.xml27(td)
+#: ./doc/common/tables/heat-notification.xml23(td)
 msgid ""
-"(StrOpt) Name of eventlet hub to use. Traditionally, we have only supported "
-"'poll', however 'selects' may be appropriate for some platforms. See "
-"http://eventlet.net/doc/hubs.html for more details."
+"(StrOpt) onready allows you to send a notification when the heat processes "
+"are ready to serve. This is either a module with the notify() method or a "
+"shell command. To enable notifications with systemd, one may use the "
+"'systemd-notify --ready' shell command or the 'heat.common.systemd' "
+"notification module."
 msgstr ""
 
-#: ./doc/common/tables/glance-wsgi.xml35(td)
+#: ./doc/common/tables/nova-vpn.xml8(caption)
+#: ./doc/common/tables/neutron-vpn.xml8(caption)
+msgid "Description of configuration options for vpn"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml22(td)
+msgid "boot_script_template = $pybasedir/nova/cloudpipe/bootscript.template"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml23(td)
+msgid "(StrOpt) Template for cloudpipe instance boot script"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml26(td)
+msgid "dmz_cidr ="
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml27(td)
+msgid "(ListOpt) A list of dmz range that should be accepted"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml30(td)
+msgid "dmz_mask = 255.255.255.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml31(td)
+msgid "(StrOpt) Netmask to push into openvpn config"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml34(td)
+msgid "dmz_net = 10.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml35(td)
+msgid "(StrOpt) Network to push into openvpn config"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml38(td)
+msgid "vpn_flavor = m1.tiny"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml39(td)
+msgid "(StrOpt) Flavor for vpn instances"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml42(td)
+msgid "vpn_image_id = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml43(td)
+msgid "(StrOpt) Image ID used when starting up a cloudpipe vpn server"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml46(td)
+msgid "vpn_ip = $my_ip"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml47(td)
+msgid "(StrOpt) Public IP for the cloudpipe VPN servers"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml50(td)
+msgid "vpn_key_suffix = -vpn"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml51(td)
+msgid "(StrOpt) Suffix to add to project name for vpn key and secgroups"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml54(td)
+msgid "vpn_start = 1000"
+msgstr ""
+
+#: ./doc/common/tables/nova-vpn.xml55(td)
+msgid "(IntOpt) First Vpn port for private networks"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vpn.xml19(th)
+msgid "[ipsec]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vpn.xml22(td)
+msgid "config_base_dir = $state_path/ipsec"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vpn.xml23(td)
+msgid "(StrOpt) Location to store ipsec server config files"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vpn.xml26(td)
+msgid "ipsec_status_check_interval = 60"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vpn.xml27(td)
+msgid "(IntOpt) Interval for checking ipsec status"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vpn.xml30(th)
+msgid "[openswan]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vpn.xml33(td)
 msgid ""
-"(IntOpt) The value for the socket option TCP_KEEPIDLE. This is the time in "
-"seconds that the connection must be idle before TCP starts sending keepalive"
-" probes."
+"ipsec_config_template = /usr/lib/python/site-"
+"packages/neutron/services/vpn/device_drivers/template/openswan/ipsec.conf.template"
 msgstr ""
 
-#: ./doc/common/tables/nova-periodic.xml8(caption)
-msgid "Description of configuration options for periodic"
+#: ./doc/common/tables/neutron-vpn.xml34(td)
+msgid "(StrOpt) Template file for ipsec configuration"
 msgstr ""
 
-#: ./doc/common/tables/nova-periodic.xml22(td)
-msgid "periodic_enable = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-periodic.xml23(td)
-msgid "(BoolOpt) Enable periodic tasks"
-msgstr ""
-
-#: ./doc/common/tables/nova-periodic.xml26(td)
-#: ./doc/common/tables/cinder-common.xml130(td)
-msgid "periodic_fuzzy_delay = 60"
-msgstr ""
-
-#: ./doc/common/tables/cinder-images.xml8(caption)
-msgid "Description of configuration options for images"
-msgstr ""
-
-#: ./doc/common/tables/cinder-images.xml23(td)
+#: ./doc/common/tables/neutron-vpn.xml37(td)
 msgid ""
-"(ListOpt) A list of url schemes that can be downloaded directly via the "
-"direct_url. Currently supported schemes: [file]."
+"ipsec_secret_template = /usr/lib/python/site-"
+"packages/neutron/services/vpn/device_drivers/template/openswan/ipsec.secret.template"
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml31(td)
+#: ./doc/common/tables/neutron-vpn.xml38(td)
+msgid "(StrOpt) Template file for ipsec secret configuration"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vpn.xml41(th)
+msgid "[vpnagent]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-vpn.xml44(td)
 msgid ""
-"(ListOpt) A list of the glance api servers available to cinder "
-"([hostname|ip]:port)"
+"vpn_device_driver = "
+"['neutron.services.vpn.device_drivers.ipsec.OpenSwanDriver']"
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml34(td)
-msgid "glance_api_ssl_compression = False"
+#: ./doc/common/tables/neutron-vpn.xml45(td)
+msgid "(MultiStrOpt) The vpn device drivers Neutron will use"
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml35(td)
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml7(literal)
+msgid "[object-expirer]"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml27(td)
+#: ./doc/common/tables/neutron-common.xml170(td)
+msgid "report_interval = 300"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml30(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml39(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml33(td)
+msgid "concurrency = 1"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml30(td)
+#: ./doc/common/tables/swift-account-server-account-replicator.xml39(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml33(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml39(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml39(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml33(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml54(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml30(td)
+msgid "Number of replication workers to spawn"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml33(td)
+msgid "processes = 0"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml36(td)
+msgid "process = 0"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-expirer-object-expirer.xml36(td)
 msgid ""
-"(BoolOpt) Whether to attempt to negotiate SSL layer compression when using "
-"SSL (https) requests. Set to False to disable SSL layer compression. In some"
-" cases disabling this may improve data throughput, eg when high network "
-"bandwidth is available and you are using already compressed image formats "
-"such as qcow2 ."
+"(it will actually accept(2) N + 1). Setting this to one (1) will only handle"
+" one request at a time, without accepting another request concurrently."
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml38(td)
-msgid "glance_api_version = 1"
+#: ./doc/common/tables/trove-common.xml22(td)
+msgid "configurations_page_size = 20"
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml39(td)
-msgid "(IntOpt) Version of the glance api to use"
+#: ./doc/common/tables/trove-common.xml23(td)
+#: ./doc/common/tables/trove-common.xml27(td)
+#: ./doc/common/tables/trove-common.xml47(td)
+#: ./doc/common/tables/trove-api.xml35(td)
+#: ./doc/common/tables/trove-api.xml47(td)
+#: ./doc/common/tables/trove-api.xml51(td)
+#: ./doc/common/tables/trove-api.xml55(td)
+#: ./doc/common/tables/trove-api.xml59(td)
+#: ./doc/common/tables/trove-api.xml63(td)
+#: ./doc/common/tables/trove-api.xml79(td)
+#: ./doc/common/tables/trove-api.xml87(td)
+#: ./doc/common/tables/trove-api.xml103(td)
+#: ./doc/common/tables/trove-dns.xml71(td)
+#: ./doc/common/tables/trove-dns.xml75(td)
+#: ./doc/common/tables/trove-volume.xml39(td)
+#: ./doc/common/tables/trove-volume.xml47(td)
+#: ./doc/common/tables/trove-heat.xml23(td)
+#: ./doc/common/tables/trove-rpc.xml39(td)
+#: ./doc/common/tables/trove-rpc.xml43(td)
+#: ./doc/common/tables/trove-backup.xml71(td)
+#: ./doc/common/tables/trove-guestagent.xml23(td)
+#: ./doc/common/tables/trove-guestagent.xml27(td)
+#: ./doc/common/tables/trove-guestagent.xml31(td)
+#: ./doc/common/tables/trove-database.xml27(td)
+#: ./doc/common/tables/trove-taskmanager.xml43(td)
+#: ./doc/common/tables/trove-taskmanager.xml47(td)
+#: ./doc/common/tables/trove-taskmanager.xml51(td)
+#: ./doc/common/tables/trove-taskmanager.xml55(td)
+#: ./doc/common/tables/trove-taskmanager.xml59(td)
+msgid "(IntOpt) No help text available for this option."
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml43(td)
-msgid "(StrOpt) default glance hostname or ip"
+#: ./doc/common/tables/trove-common.xml26(td)
+msgid "databases_page_size = 20"
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml47(td)
-msgid "(IntOpt) Number retries when downloading an image from glance"
+#: ./doc/common/tables/trove-common.xml30(td)
+msgid "default_datastore = None"
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml51(td)
-msgid "(IntOpt) default glance port"
-msgstr ""
-
-#: ./doc/common/tables/cinder-images.xml54(td)
-msgid "glance_request_timeout = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-images.xml55(td)
+#: ./doc/common/tables/trove-common.xml31(td)
 msgid ""
-"(IntOpt) http/https timeout value for glance operations. If no value (None) "
-"is supplied here, the glanceclient default value is used."
+"(StrOpt) The default datastore id or name to use if one is not provided by "
+"the user. If the default value is None, the field becomes required in the "
+"instance-create request."
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml58(td)
-msgid "image_conversion_dir = $state_path/conversion"
+#: ./doc/common/tables/trove-common.xml38(td)
+msgid "default_neutron_networks ="
 msgstr ""
 
-#: ./doc/common/tables/cinder-images.xml59(td)
-msgid "(StrOpt) Directory used for temporary storage during image conversion"
-msgstr ""
-
-#: ./doc/common/tables/cinder-images.xml70(td)
-msgid "use_multipath_for_image_xfer = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-images.xml71(td)
+#: ./doc/common/tables/trove-common.xml39(td)
 msgid ""
-"(BoolOpt) Do we attach/detach volumes in cinder using multipath for volume "
-"to image and image to volume transfers?"
+"(ListOpt) List of network IDs which should be attached to instance when "
+"networks are not specified in API call."
 msgstr ""
 
-#: ./doc/common/tables/trove-swift.xml22(td)
-msgid "swift_url = http://localhost:8080/v1/AUTH_"
+#: ./doc/common/tables/trove-common.xml46(td)
+msgid "default_password_length = 36"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-app-container-server.xml7(literal)
-msgid "[app:container-server]"
+#: ./doc/common/tables/trove-common.xml50(td)
+#: ./doc/common/tables/neutron-notifier.xml26(td)
+msgid "default_publisher_id = $host"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-app-container-server.xml18(td)
-msgid "use = egg:swift#container"
+#: ./doc/common/tables/trove-common.xml54(td)
+msgid "expected_filetype_suffixes = json"
 msgstr ""
 
-#: ./doc/common/tables/swift-container-server-app-container-server.xml21(td)
-msgid "set log_name = container-server"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-app-container-server.xml42(td)
-msgid "allow_versions = false"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-app-container-server.xml42(td)
-msgid "Enable/Disable object versioning feature"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml7(literal)
-msgid "[filter:slo]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml18(td)
-msgid "use = egg:swift#slo"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml21(td)
-msgid "max_manifest_segments = 1000"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml24(td)
-msgid "max_manifest_size = 2097152"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml27(td)
-msgid "min_segment_size = 1048576"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-slo.xml33(td)
-msgid "rate_limit_segments_per_sec = 0"
-msgstr ""
-
-#: ./doc/common/tables/heat-crypt.xml8(caption)
-msgid "Description of configuration options for crypt"
-msgstr ""
-
-#: ./doc/common/tables/heat-crypt.xml22(td)
-msgid "auth_encryption_key = notgood but just long enough i think"
-msgstr ""
-
-#: ./doc/common/tables/heat-crypt.xml23(td)
-msgid "(StrOpt) Encryption key used for authentication info in database."
-msgstr ""
-
-#: ./doc/common/tables/neutron-wsgi.xml26(td)
-msgid "retry_until_window = 30"
-msgstr ""
-
-#: ./doc/common/tables/neutron-wsgi.xml27(td)
-msgid "(IntOpt) Number of seconds to keep retrying to listen"
-msgstr ""
-
-#: ./doc/common/tables/neutron-scheduler.xml8(caption)
-#: ./doc/common/tables/cinder-scheduler.xml8(caption)
-msgid "Description of configuration options for scheduler"
-msgstr ""
-
-#: ./doc/common/tables/neutron-scheduler.xml22(td)
-msgid "network_auto_schedule = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-scheduler.xml23(td)
-msgid "(BoolOpt) Allow auto scheduling networks to DHCP agent."
-msgstr ""
-
-#: ./doc/common/tables/neutron-scheduler.xml26(td)
+#: ./doc/common/tables/trove-common.xml55(td)
 msgid ""
-"network_scheduler_driver = "
-"neutron.scheduler.dhcp_agent_scheduler.ChanceScheduler"
+"(ListOpt) Filetype endings not to be reattached to an id by the utils method"
+" correct_id_with_req."
 msgstr ""
 
-#: ./doc/common/tables/neutron-scheduler.xml27(td)
-msgid "(StrOpt) Driver to use for scheduling network to DHCP agent"
+#: ./doc/common/tables/trove-common.xml62(td)
+msgid "pybasedir = /usr/lib/python/site-packages/trove"
 msgstr ""
 
-#: ./doc/common/tables/neutron-scheduler.xml30(td)
-msgid "router_auto_schedule = True"
+#: ./doc/common/tables/trove-common.xml63(td)
+msgid "(StrOpt) Directory where the trove python module is installed."
 msgstr ""
 
-#: ./doc/common/tables/neutron-scheduler.xml31(td)
-msgid "(BoolOpt) Allow auto scheduling of routers to L3 agent."
+#: ./doc/common/tables/trove-common.xml66(td)
+msgid "pydev_path = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-scheduler.xml34(td)
-msgid "router_delete_namespaces = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-scheduler.xml35(td)
-msgid "(BoolOpt) Delete namespace after removing a router."
-msgstr ""
-
-#: ./doc/common/tables/neutron-scheduler.xml38(td)
+#: ./doc/common/tables/trove-common.xml67(td)
 msgid ""
-"router_scheduler_driver = "
-"neutron.scheduler.l3_agent_scheduler.ChanceScheduler"
+"(StrOpt) Set path to pydevd library, used if pydevd is not found in python "
+"sys.path."
 msgstr ""
 
-#: ./doc/common/tables/neutron-scheduler.xml39(td)
-msgid "(StrOpt) Driver to use for scheduling router to a default L3 agent"
+#: ./doc/common/tables/trove-common.xml70(td)
+msgid "taskmanager_queue = taskmanager"
 msgstr ""
 
-#: ./doc/common/tables/keystone-security.xml8(caption)
-msgid "Description of configuration options for security"
+#: ./doc/common/tables/trove-common.xml74(td)
+msgid "template_path = /etc/trove/templates/"
 msgstr ""
 
-#: ./doc/common/tables/keystone-security.xml22(td)
-msgid "crypt_strength = 40000"
+#: ./doc/common/tables/trove-common.xml75(td)
+msgid "(StrOpt) Path which leads to datastore templates."
 msgstr ""
 
-#: ./doc/common/tables/keystone-security.xml23(td)
+#: ./doc/common/tables/trove-api.xml22(td)
+msgid "admin_roles = admin"
+msgstr ""
+
+#: ./doc/common/tables/trove-api.xml23(td)
+#: ./doc/common/tables/trove-guestagent.xml43(td)
+#: ./doc/common/tables/trove-guestagent.xml47(td)
+#: ./doc/common/tables/trove-compute.xml31(td)
+msgid "(ListOpt) No help text available for this option."
+msgstr ""
+
+#: ./doc/common/tables/trove-api.xml26(td)
+msgid "api_extensions_path = trove/extensions/routes"
+msgstr ""
+
+#: ./doc/common/tables/trove-api.xml27(td)
+msgid "(StrOpt) Path to extensions."
+msgstr ""
+
+#: ./doc/common/tables/trove-api.xml30(td)
+#: ./doc/common/tables/heat-api.xml134(td)
+#: ./doc/common/tables/cinder-api.xml22(td)
+#: ./doc/common/tables/neutron-api.xml38(td)
+#: ./doc/common/tables/nova-wsgi.xml22(td)
+msgid "api_paste_config = api-paste.ini"
+msgstr ""
+
+#: ./doc/common/tables/trove-api.xml31(td)
+msgid "(StrOpt) File name for the paste.deploy config for trove-api."
+msgstr ""
+
+#: ./doc/common/tables/trove-api.xml34(td)
+msgid "bind_port = 8779"
+msgstr ""
+
+#: ./doc/common/tables/trove-api.xml38(td)
+msgid "db_api_implementation = trove.db.sqlalchemy.api"
+msgstr ""
+
+#: ./doc/common/tables/trove-api.xml42(td)
+msgid "hostname_require_ipv4 = True"
+msgstr ""
+
+#: ./doc/common/tables/trove-api.xml43(td)
+msgid "(BoolOpt) Require user hostnames to be IPv4 addresses."
+msgstr ""
+
+#: ./doc/common/tables/trove-api.xml46(td)
+msgid "http_delete_rate = 200"
+msgstr ""
+
+#: ./doc/common/tables/trove-api.xml50(td)
+msgid "http_get_rate = 200"
+msgstr ""
+
+#: ./doc/common/tables/trove-api.xml54(td)
+msgid "http_post_rate = 200"
+msgstr ""
+
+#: ./doc/common/tables/trove-api.xml58(td)
+msgid "http_put_rate = 200"
+msgstr ""
+
+#: ./doc/common/tables/trove-api.xml62(td)
+msgid "instances_page_size = 20"
+msgstr ""
+
+#: ./doc/common/tables/trove-api.xml67(td)
+#: ./doc/common/tables/glance-wsgi.xml31(td)
 msgid ""
-"(IntOpt) The value passed as the keyword \"rounds\" to passlib encrypt "
-"method."
+"(IntOpt) Maximum line size of message headers to be accepted. "
+"max_header_line may need to be increased when using large tokens (typically "
+"those generated by the Keystone v3 API with big service catalogs"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-vmware.xml19(th)
-#: ./doc/common/tables/nova-vnc.xml42(th)
-#: ./doc/common/tables/nova-vmware.xml19(th)
-#: ./doc/common/tables/nova-network.xml254(th)
-msgid "[vmware]"
+#: ./doc/common/tables/trove-api.xml70(td)
+msgid "region = LOCAL_DEV"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-vmware.xml22(td)
-#: ./doc/common/tables/nova-vmware.xml22(td)
-msgid "api_retry_count = 10"
+#: ./doc/common/tables/trove-api.xml71(td)
+msgid "(StrOpt) The region this service is located."
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-vmware.xml23(td)
-msgid "(IntOpt) Number of times a VMware Vsphere API must be retried"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-vmware.xml26(td)
-msgid "host_ip ="
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-vmware.xml27(td)
-msgid "(StrOpt) IP address of the VMware Vsphere host"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-vmware.xml30(td)
-msgid "host_password ="
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-vmware.xml31(td)
-msgid "(StrOpt) Password of VMware Vsphere"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-vmware.xml34(td)
-msgid "host_username ="
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-vmware.xml35(td)
-msgid "(StrOpt) Username of VMware Vsphere"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-vmware.xml38(td)
-#: ./doc/common/tables/nova-vmware.xml54(td)
-msgid "task_poll_interval = 0.5"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-vmware.xml39(td)
-msgid "(FloatOpt) Sleep time in seconds for polling an ongoing async task"
-msgstr ""
-
-#: ./doc/common/tables/glance-rbd.xml8(caption)
-msgid "Description of configuration options for rbd"
-msgstr ""
-
-#: ./doc/common/tables/glance-rbd.xml22(td)
-msgid "rbd_store_ceph_conf = /etc/ceph/ceph.conf"
-msgstr ""
-
-#: ./doc/common/tables/glance-rbd.xml23(td)
+#: ./doc/common/tables/trove-api.xml75(td)
+#: ./doc/common/tables/cinder-common.xml199(td)
+#: ./doc/common/tables/neutron-wsgi.xml31(td)
+#: ./doc/common/tables/nova-wsgi.xml39(td)
 msgid ""
-"(StrOpt) Ceph configuration file path. If &lt;None&gt;, librados will locate"
-" the default config. If using cephx authentication, this file should include"
-" a reference to the right keyring in a client.&lt;USER&gt; section."
+"(IntOpt) Sets the value of TCP_KEEPIDLE in seconds for each server socket. "
+"Not supported on OS X."
 msgstr ""
 
-#: ./doc/common/tables/glance-rbd.xml26(td)
-msgid "rbd_store_chunk_size = 8"
+#: ./doc/common/tables/trove-api.xml78(td)
+msgid "trove_api_workers = None"
 msgstr ""
 
-#: ./doc/common/tables/glance-rbd.xml27(td)
+#: ./doc/common/tables/trove-api.xml82(td)
+msgid "trove_auth_url = http://0.0.0.0:5000/v2.0"
+msgstr ""
+
+#: ./doc/common/tables/trove-api.xml86(td)
+msgid "trove_conductor_workers = 1"
+msgstr ""
+
+#: ./doc/common/tables/trove-api.xml90(td)
+msgid "trove_security_group_name_prefix = SecGroup"
+msgstr ""
+
+#: ./doc/common/tables/trove-api.xml94(td)
+msgid "trove_security_group_rule_cidr = 0.0.0.0/0"
+msgstr ""
+
+#: ./doc/common/tables/trove-api.xml98(td)
+msgid "trove_security_groups_support = True"
+msgstr ""
+
+#: ./doc/common/tables/trove-api.xml99(td)
+#: ./doc/common/tables/trove-dns.xml83(td)
+#: ./doc/common/tables/trove-compute.xml35(td)
+#: ./doc/common/tables/trove-database.xml31(td)
+#: ./doc/common/tables/trove-taskmanager.xml71(td)
+#: ./doc/common/tables/trove-taskmanager.xml75(td)
+msgid "(BoolOpt) No help text available for this option."
+msgstr ""
+
+#: ./doc/common/tables/trove-api.xml102(td)
+msgid "users_page_size = 20"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml8(caption)
+msgid "Description of configuration options for zadara"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml22(td)
+msgid "zadara_password = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml23(td)
+msgid "(StrOpt) Password for the VPSA"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml26(td)
+msgid "zadara_user = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml27(td)
+msgid "(StrOpt) User name for the VPSA"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml30(td)
+msgid "zadara_vol_encrypt = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml31(td)
+msgid "(BoolOpt) Default encryption policy for volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml34(td)
+msgid "zadara_vol_name_template = OS_%s"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml35(td)
+msgid "(StrOpt) Default template for VPSA volume names"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml38(td)
+msgid "zadara_vol_thin = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml39(td)
+msgid "(BoolOpt) Default thin provisioning policy for volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml42(td)
+msgid "zadara_vpsa_allow_nonexistent_delete = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml43(td)
+msgid "(BoolOpt) Don't halt on deletion of non-existing volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml46(td)
+msgid "zadara_vpsa_auto_detach_on_delete = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml47(td)
+msgid "(BoolOpt) Automatically detach from servers on volume delete"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml50(td)
+msgid "zadara_vpsa_ip = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml51(td)
+msgid "(StrOpt) Management IP of Zadara VPSA"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml54(td)
+msgid "zadara_vpsa_poolname = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml55(td)
+msgid "(StrOpt) Name of VPSA storage pool for volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml58(td)
+msgid "zadara_vpsa_port = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml59(td)
+msgid "(StrOpt) Zadara VPSA port number"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml62(td)
+msgid "zadara_vpsa_use_ssl = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zadara.xml63(td)
+msgid "(BoolOpt) Use SSL connection"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-filter-healthcheck.xml7(literal)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml7(literal)
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml7(literal)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml7(literal)
+#: ./doc/common/tables/swift-object-server-pipeline-main.xml7(literal)
+#: ./doc/common/tables/swift-object-server-object-auditor.xml7(literal)
+#: ./doc/common/tables/swift-object-server-filter-recon.xml7(literal)
+#: ./doc/common/tables/swift-object-server-object-updater.xml7(literal)
+msgid "object-server.conf-sample"
+msgstr ""
+
+#: ./doc/common/tables/nova-conductor.xml8(caption)
+msgid "Description of configuration options for conductor"
+msgstr ""
+
+#: ./doc/common/tables/nova-conductor.xml22(td)
+msgid "migrate_max_retries = -1"
+msgstr ""
+
+#: ./doc/common/tables/nova-conductor.xml23(td)
 msgid ""
-"(IntOpt) RADOS images will be chunked into objects of this size (in "
-"megabytes). For best performance, this should be a power of two."
+"(IntOpt) Number of times to retry live-migration before failing. If == -1, "
+"try until out of hosts. If == 0, only try once, no retries."
 msgstr ""
 
-#: ./doc/common/tables/glance-rbd.xml30(td)
-msgid "rbd_store_pool = images"
+#: ./doc/common/tables/nova-conductor.xml26(th)
+msgid "[conductor]"
 msgstr ""
 
-#: ./doc/common/tables/glance-rbd.xml31(td)
-msgid "(StrOpt) RADOS pool in which images are stored."
+#: ./doc/common/tables/nova-conductor.xml29(td)
+msgid "manager = nova.conductor.manager.ConductorManager"
 msgstr ""
 
-#: ./doc/common/tables/glance-rbd.xml34(td)
-msgid "rbd_store_user = None"
+#: ./doc/common/tables/nova-conductor.xml30(td)
+msgid "(StrOpt) Full class name for the Manager for conductor"
 msgstr ""
 
-#: ./doc/common/tables/glance-rbd.xml35(td)
+#: ./doc/common/tables/nova-conductor.xml33(td)
+msgid "topic = conductor"
+msgstr ""
+
+#: ./doc/common/tables/nova-conductor.xml34(td)
+msgid "(StrOpt) The topic on which conductor nodes listen"
+msgstr ""
+
+#: ./doc/common/tables/nova-conductor.xml37(td)
+msgid "use_local = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-conductor.xml38(td)
+msgid "(BoolOpt) Perform nova-conductor operations locally"
+msgstr ""
+
+#: ./doc/common/tables/nova-conductor.xml41(td)
+msgid "workers = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-conductor.xml42(td)
 msgid ""
-"(StrOpt) RADOS user to authenticate as (only applicable if using Cephx. If "
-"&lt;None&gt;, a default will be chosen based on the client. section in "
-"rbd_store_ceph_conf)."
+"(IntOpt) Number of workers for OpenStack Conductor service. The default will"
+" be the number of CPUs available."
 msgstr ""
 
-#: ./doc/common/tables/heat-clients_heat.xml8(caption)
-msgid "Description of configuration options for clients_heat"
+#: ./doc/common/tables/swift-object-server-app-object-server.xml7(literal)
+msgid "[app:object-server]"
 msgstr ""
 
-#: ./doc/common/tables/heat-clients_heat.xml19(th)
-msgid "[clients_heat]"
+#: ./doc/common/tables/swift-object-server-app-object-server.xml18(td)
+msgid "use = egg:swift#object"
 msgstr ""
 
-#: ./doc/common/tables/heat-clients_heat.xml42(td)
-#: ./doc/common/tables/neutron-ml2_odl.xml34(td)
-#: ./doc/common/tables/neutron-ml2_ncs.xml30(td)
-msgid "url = None"
+#: ./doc/common/tables/swift-object-server-app-object-server.xml21(td)
+msgid "set log_name = object-server"
 msgstr ""
 
-#: ./doc/common/tables/heat-clients_heat.xml43(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml30(td)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml30(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml30(td)
+msgid "set log_requests = true"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml30(td)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml30(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml30(td)
+msgid "Whether or not to log requests"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml36(td)
+msgid "max_upload_time = 86400"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml36(td)
+msgid "Maximum time allowed to upload an object"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml39(td)
+msgid "slow = 0"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml39(td)
 msgid ""
-"(StrOpt) Optional heat url in format like "
-"http://0.0.0.0:8004/v1/%(tenant_id)s."
+"If &gt; 0, Minimum time in seconds for a PUT or DELETE request to complete"
 msgstr ""
 
-#: ./doc/common/tables/heat-rabbitmq.xml35(td)
-#: ./doc/common/tables/trove-amqp.xml55(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml42(td)
+msgid "keep_cache_size = 5424880"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml42(td)
+msgid "Largest object size to keep in buffer cache"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml45(td)
+msgid "keep_cache_private = false"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml45(td)
+msgid "Allow non-public objects to stay in kernel's buffer cache"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml48(td)
+msgid "mb_per_sync = 512"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml48(td)
+msgid "On PUT requests, sync file every n MB"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-app-object-server.xml51(td)
 msgid ""
-"(StrOpt) SSL version to use (valid only if SSL enabled). valid values are "
-"TLSv1, SSLv23 and SSLv3. SSLv2 may be available on some distributions"
+"allowed_headers = Content-Disposition, Content-Encoding, X-Delete-At, X"
+"-Object-Manifest, X-Static-Large-Object"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-logging.xml30(td)
-#: ./doc/common/tables/neutron-notifier.xml22(td)
-#: ./doc/common/tables/heat-amqp.xml34(td)
-#: ./doc/common/tables/trove-common.xml42(td)
-#: ./doc/common/tables/nova-compute.xml54(td)
-msgid "default_notification_level = INFO"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-logging.xml31(td)
-#: ./doc/common/tables/neutron-notifier.xml23(td)
-#: ./doc/common/tables/heat-amqp.xml35(td)
-#: ./doc/common/tables/trove-common.xml43(td)
-#: ./doc/common/tables/nova-compute.xml55(td)
-msgid "(StrOpt) Default notification level for outgoing notifications"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-logging.xml105(td)
-#: ./doc/common/tables/neutron-cadf.xml22(td)
-msgid "api_audit_map = api_audit_map.conf"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-logging.xml106(td)
-#: ./doc/common/tables/neutron-cadf.xml23(td)
-msgid "(StrOpt) File containing mapping for api paths and service endpoints"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metadata.xml22(td)
-msgid "meta_flavor_driver_mappings = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metadata.xml23(td)
-msgid "(StrOpt) Mapping between flavor and LinuxInterfaceDriver"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metadata.xml26(td)
-msgid "metadata_backlog = 128"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metadata.xml27(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml51(td)
 msgid ""
-"(IntOpt) Number of backlog requests to configure the metadata server socket "
-"with"
+"Comma-separated list of headers that can be set in metadata of an object"
 msgstr ""
 
-#: ./doc/common/tables/neutron-metadata.xml30(td)
-msgid "metadata_port = 9697"
+#: ./doc/common/tables/swift-object-server-app-object-server.xml57(td)
+msgid "threads_per_disk = 0"
 msgstr ""
 
-#: ./doc/common/tables/neutron-metadata.xml31(td)
-msgid "(IntOpt) TCP Port used by Neutron metadata namespace proxy."
-msgstr ""
-
-#: ./doc/common/tables/neutron-metadata.xml34(td)
-msgid "metadata_proxy_shared_secret ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-metadata.xml35(td)
-#: ./doc/common/tables/neutron-vmware.xml146(td)
-msgid "(StrOpt) Shared secret to sign instance-id request"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metadata.xml38(td)
-msgid "metadata_proxy_socket = $state_path/metadata_proxy"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metadata.xml39(td)
-msgid "(StrOpt) Location of Metadata Proxy UNIX domain socket"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metadata.xml42(td)
-msgid "metadata_workers = 0"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metadata.xml43(td)
-msgid "(IntOpt) Number of separate worker processes for metadata server"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metadata.xml46(td)
-msgid "nova_metadata_ip = 127.0.0.1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metadata.xml47(td)
-msgid "(StrOpt) IP address used by Nova metadata server."
-msgstr ""
-
-#: ./doc/common/tables/neutron-metadata.xml50(td)
-msgid "nova_metadata_port = 8775"
-msgstr ""
-
-#: ./doc/common/tables/neutron-metadata.xml51(td)
-msgid "(IntOpt) TCP Port used by Nova metadata server."
-msgstr ""
-
-#: ./doc/common/tables/glance-redis.xml23(td)
-#: ./doc/common/tables/keystone-redis.xml23(td)
-msgid "(StrOpt) Host to locate redis."
-msgstr ""
-
-#: ./doc/common/tables/keystone-stats.xml8(caption)
-msgid "Description of configuration options for stats"
-msgstr ""
-
-#: ./doc/common/tables/keystone-stats.xml19(th)
-msgid "[stats]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-stats.xml22(td)
-msgid "driver = keystone.contrib.stats.backends.kvs.Stats"
-msgstr ""
-
-#: ./doc/common/tables/keystone-stats.xml23(td)
-msgid "(StrOpt) Keystone stats backend driver."
-msgstr ""
-
-#: ./doc/common/tables/cinder-hp3par.xml8(caption)
-msgid "Description of configuration options for hp3par"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hp3par.xml22(td)
-msgid "hp3par_api_url ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-hp3par.xml23(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml57(td)
 msgid ""
-"(StrOpt) 3PAR WSAPI Server Url like https://&lt;3par ip&gt;:8080/api/v1"
+"Size of the per-disk thread pool used for performing disk I/O. The default "
+"of 0 means to not use a per-disk thread pool. It is recommended to keep this"
+" value small, as large values can result in high read latencies due to large"
+" queue depths. A good starting point is 4 threads per disk."
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml26(td)
-msgid "hp3par_cpg = OpenStack"
+#: ./doc/common/tables/swift-object-server-app-object-server.xml60(td)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml39(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml48(td)
+msgid "replication_server = false"
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml27(td)
-msgid "(StrOpt) The CPG to use for volume creation"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hp3par.xml30(td)
-msgid "hp3par_cpg_snap ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-hp3par.xml31(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml60(td)
+#: ./doc/common/tables/swift-account-server-app-account-server.xml39(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml48(td)
 msgid ""
-"(StrOpt) The CPG to use for Snapshots for volumes. If empty hp3par_cpg will "
-"be used"
+"If defined, tells server how to handle replication verbs in requests. When "
+"set to True (or 1), only replication verbs will be accepted. When set to "
+"False, replication verbs will be rejected. When undefined, server will "
+"accept any verb in the request."
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml34(td)
-msgid "hp3par_debug = False"
+#: ./doc/common/tables/swift-object-server-app-object-server.xml63(td)
+msgid "replication_concurrency = 4"
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml35(td)
-msgid "(BoolOpt) Enable HTTP debugging to 3PAR"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hp3par.xml38(td)
-msgid "hp3par_iscsi_ips ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-hp3par.xml39(td)
-msgid "(ListOpt) List of target iSCSI addresses to use."
-msgstr ""
-
-#: ./doc/common/tables/cinder-hp3par.xml42(td)
-msgid "hp3par_password ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-hp3par.xml43(td)
-msgid "(StrOpt) 3PAR Super user password"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hp3par.xml46(td)
-msgid "hp3par_snapshot_expiration ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-hp3par.xml47(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml63(td)
 msgid ""
-"(StrOpt) The time in hours when a snapshot expires and is deleted. This must"
-" be larger than expiration"
+"Set to restrict the number of concurrent incoming REPLICATION requests; set "
+"to 0 for unlimited"
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml50(td)
-msgid "hp3par_snapshot_retention ="
+#: ./doc/common/tables/swift-object-server-app-object-server.xml66(td)
+msgid "replication_one_per_device = True"
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml51(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml66(td)
 msgid ""
-"(StrOpt) The time in hours to retain a snapshot. You can't delete it before "
-"this expires."
+"Restricts incoming REPLICATION requests to one per device, "
+"replication_currency above allowing. This can help control I/O to each "
+"device, but you may wish to set this to False to allow multiple REPLICATION "
+"requests (up to the above replication_concurrency setting) per device."
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml54(td)
-msgid "hp3par_username ="
+#: ./doc/common/tables/swift-object-server-app-object-server.xml69(td)
+msgid "replication_lock_timeout = 15"
 msgstr ""
 
-#: ./doc/common/tables/cinder-hp3par.xml55(td)
-msgid "(StrOpt) 3PAR Super user username"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_ceph.xml8(caption)
-msgid "Description of configuration options for storage_ceph"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_ceph.xml22(td)
-msgid "rbd_ceph_conf ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_ceph.xml23(td)
-msgid "(StrOpt) path to the ceph configuration file to use"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_ceph.xml26(td)
-msgid "rbd_flatten_volume_from_snapshot = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_ceph.xml27(td)
-msgid "(BoolOpt) flatten volumes created from snapshots to remove dependency"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_ceph.xml30(td)
-msgid "rbd_max_clone_depth = 5"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_ceph.xml31(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml69(td)
 msgid ""
-"(IntOpt) maximum number of nested clones that can be taken of a volume "
-"before enforcing a flatten prior to next clone. A value of zero disables "
-"cloning"
+"Number of seconds to wait for an existing replication device lock before "
+"giving up."
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_ceph.xml34(td)
-msgid "rbd_pool = rbd"
+#: ./doc/common/tables/swift-object-server-app-object-server.xml72(td)
+msgid "replication_failure_threshold = 100"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_ceph.xml35(td)
-msgid "(StrOpt) the RADOS pool in which rbd volumes are stored"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_ceph.xml39(td)
-msgid "(StrOpt) the libvirt uuid of the secret for the rbd_uservolumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_ceph.xml43(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml72(td)
 msgid ""
-"(StrOpt) the RADOS client name for accessing rbd volumes - only set when "
-"using cephx authentication"
+"The number of subrequest failures before the replication_failure_ratio is "
+"checked"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_ceph.xml46(td)
-msgid "volume_tmp_dir = None"
+#: ./doc/common/tables/swift-object-server-app-object-server.xml75(td)
+msgid "replication_failure_ratio = 1.0"
 msgstr ""
 
-#: ./doc/common/tables/cinder-storage_ceph.xml47(td)
+#: ./doc/common/tables/swift-object-server-app-object-server.xml75(td)
 msgid ""
-"(StrOpt) where to store temporary image files if the volume driver does not "
-"write them directly to the volume"
+"If the value of failures / successes of REPLICATION subrequests exceeds this"
+" ratio, the overall REPLICATION request will be aborted"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml21(td)
+msgid "set log_name = catch_errors"
 msgstr ""
 
 #: ./doc/common/tables/nova-livemigration.xml8(caption)
@@ -37556,478 +37956,142 @@ msgid ""
 "migration target hostname)"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml22(td)
-msgid "ldap_dns_base_dn = ou=hosts,dc=example,dc=org"
-msgstr ""
-
-#: ./doc/common/tables/nova-ldap.xml23(td)
-msgid "(StrOpt) Base DN for DNS entries in LDAP"
-msgstr ""
-
-#: ./doc/common/tables/nova-ldap.xml26(td)
-msgid "ldap_dns_password = password"
-msgstr ""
-
-#: ./doc/common/tables/nova-ldap.xml27(td)
-msgid "(StrOpt) Password for LDAP DNS"
-msgstr ""
-
-#: ./doc/common/tables/nova-ldap.xml30(td)
-msgid "ldap_dns_servers = ['dns.example.org']"
-msgstr ""
-
-#: ./doc/common/tables/nova-ldap.xml31(td)
-msgid "(MultiStrOpt) DNS Servers for LDAP DNS driver"
-msgstr ""
-
-#: ./doc/common/tables/nova-ldap.xml34(td)
-msgid "ldap_dns_soa_expiry = 86400"
-msgstr ""
-
-#: ./doc/common/tables/nova-ldap.xml35(td)
+#: ./doc/common/tables/heat-rabbitmq.xml39(td)
+#: ./doc/common/tables/trove-rabbitmq.xml23(td)
 msgid ""
-"(StrOpt) Expiry interval (in seconds) for LDAP DNS driver Statement of "
-"Authority"
+"(BoolOpt) use H/A queues in RabbitMQ (x-ha-policy: all).You need to wipe "
+"RabbitMQ database when changing this option."
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml38(td)
-msgid "ldap_dns_soa_hostmaster = hostmaster@example.org"
+#: ./doc/common/tables/heat-rabbitmq.xml43(td)
+#: ./doc/common/tables/trove-rabbitmq.xml27(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml27(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml47(td)
+msgid "(StrOpt) The RabbitMQ broker address where a single node is used"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml39(td)
-msgid "(StrOpt) Hostmaster for LDAP DNS driver Statement of Authority"
+#: ./doc/common/tables/heat-rabbitmq.xml47(td)
+#: ./doc/common/tables/trove-rabbitmq.xml31(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml31(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml51(td)
+msgid "(ListOpt) RabbitMQ HA cluster host:port pairs"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml42(td)
-msgid "ldap_dns_soa_minimum = 7200"
-msgstr ""
-
-#: ./doc/common/tables/nova-ldap.xml43(td)
+#: ./doc/common/tables/heat-rabbitmq.xml51(td)
+#: ./doc/common/tables/trove-rabbitmq.xml35(td)
 msgid ""
-"(StrOpt) Minimum interval (in seconds) for LDAP DNS driver Statement of "
-"Authority"
+"(IntOpt) maximum retries with trying to connect to RabbitMQ (the default of "
+"0 implies an infinite retry count)"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml46(td)
-msgid "ldap_dns_soa_refresh = 1800"
+#: ./doc/common/tables/heat-rabbitmq.xml55(td)
+#: ./doc/common/tables/trove-rabbitmq.xml39(td)
+msgid "(StrOpt) the RabbitMQ password"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml47(td)
+#: ./doc/common/tables/heat-rabbitmq.xml59(td)
+#: ./doc/common/tables/trove-rabbitmq.xml43(td)
+#: ./doc/common/tables/neutron-rabbitmq.xml43(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml63(td)
+msgid "(IntOpt) The RabbitMQ broker port where a single node is used"
+msgstr ""
+
+#: ./doc/common/tables/heat-rabbitmq.xml63(td)
+#: ./doc/common/tables/trove-rabbitmq.xml47(td)
 msgid ""
-"(StrOpt) Refresh interval (in seconds) for LDAP DNS driver Statement of "
-"Authority"
+"(IntOpt) how long to backoff for between retries when connecting to RabbitMQ"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml50(td)
-msgid "ldap_dns_soa_retry = 3600"
+#: ./doc/common/tables/heat-rabbitmq.xml67(td)
+#: ./doc/common/tables/trove-rabbitmq.xml51(td)
+msgid "(IntOpt) how frequently to retry connecting with RabbitMQ"
 msgstr ""
 
-#: ./doc/common/tables/nova-ldap.xml51(td)
+#: ./doc/common/tables/heat-rabbitmq.xml71(td)
+#: ./doc/common/tables/trove-rabbitmq.xml55(td)
+msgid "(BoolOpt) connect over SSL for RabbitMQ"
+msgstr ""
+
+#: ./doc/common/tables/heat-rabbitmq.xml75(td)
+#: ./doc/common/tables/trove-rabbitmq.xml59(td)
+msgid "(StrOpt) the RabbitMQ userid"
+msgstr ""
+
+#: ./doc/common/tables/heat-rabbitmq.xml79(td)
+#: ./doc/common/tables/trove-rabbitmq.xml63(td)
+msgid "(StrOpt) the RabbitMQ virtual host"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml7(literal)
+msgid "[filter:keystoneauth]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml18(td)
+msgid "use = egg:swift#keystoneauth"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml21(td)
+msgid "operator_roles = admin, swiftoperator"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml24(td)
+msgid "reseller_admin_role = ResellerAdmin"
+msgstr ""
+
+#: ./doc/common/tables/neutron-cadf.xml8(caption)
+msgid "Description of configuration options for cadf"
+msgstr ""
+
+#: ./doc/common/tables/keystone-amqp.xml46(td)
+#: ./doc/common/tables/glance-amqp.xml38(td)
+#: ./doc/common/tables/cinder-rpc.xml182(td)
+#: ./doc/common/tables/nova-rpc_all.xml150(td)
+#: ./doc/common/tables/nova-rpc.xml42(td)
+msgid "rpc_backend = rabbit"
+msgstr ""
+
+#: ./doc/common/tables/keystone-amqp.xml47(td)
+#: ./doc/common/tables/glance-amqp.xml39(td)
+#: ./doc/common/tables/cinder-rpc.xml183(td)
+#: ./doc/common/tables/nova-rpc_all.xml151(td)
+#: ./doc/common/tables/nova-rpc.xml43(td)
 msgid ""
-"(StrOpt) Retry interval (in seconds) for LDAP DNS driver Statement of "
-"Authority"
-msgstr ""
-
-#: ./doc/common/tables/nova-ldap.xml54(td)
-msgid "ldap_dns_url = ldap://ldap.example.com:389"
-msgstr ""
-
-#: ./doc/common/tables/nova-ldap.xml55(td)
-msgid "(StrOpt) URL for LDAP server which will store DNS entries"
-msgstr ""
-
-#: ./doc/common/tables/nova-ldap.xml58(td)
-msgid "ldap_dns_user = uid=admin,ou=people,dc=example,dc=org"
-msgstr ""
-
-#: ./doc/common/tables/nova-ldap.xml59(td)
-msgid "(StrOpt) User for LDAP DNS"
-msgstr ""
-
-#: ./doc/common/tables/nova-fping.xml8(caption)
-msgid "Description of configuration options for fping"
-msgstr ""
-
-#: ./doc/common/tables/nova-fping.xml22(td)
-msgid "fping_path = /usr/sbin/fping"
-msgstr ""
-
-#: ./doc/common/tables/nova-fping.xml23(td)
-msgid "(StrOpt) Full path to fping."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_swift.xml8(caption)
-msgid "Description of configuration options for clients_swift"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_swift.xml19(th)
-msgid "[clients_swift]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-securitygroups.xml8(caption)
-msgid "Description of configuration options for securitygroups"
-msgstr ""
-
-#: ./doc/common/tables/neutron-securitygroups.xml19(th)
-msgid "[SECURITYGROUP]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-securitygroups.xml22(td)
-msgid "enable_security_group = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-securitygroups.xml23(td)
-msgid ""
-"(BoolOpt) Controls whether the neutron security group API is enabled in the "
-"server. It should be false when using no security groups or using the nova "
-"security group API."
-msgstr ""
-
-#: ./doc/common/tables/neutron-securitygroups.xml26(td)
-#: ./doc/common/tables/nova-network.xml78(td)
-msgid "firewall_driver = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-securitygroups.xml27(td)
-msgid "(StrOpt) Driver for security groups firewall in the L2 agent"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml8(caption)
-msgid "Description of configuration options for netapp_cdot_iscsi"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml54(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml58(td)
-msgid "netapp_vserver = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml55(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml59(td)
-msgid ""
-"(StrOpt) This option specifies the virtual storage server (Vserver) name on "
-"the storage cluster on which provisioning of block storage volumes should "
-"occur. If using the NFS storage protocol, this parameter is mandatory for "
-"storage service catalog support (utilized by Cinder volume type extra_specs "
-"support). If this option is specified, the exports belonging to the Vserver "
-"will only be used for provisioning in the future. Block storage volumes on "
-"exports not belonging to the Vserver specified by this option will continue "
-"to function normally."
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml8(caption)
-#: ./doc/common/tables/keystone-ec2.xml8(caption)
-msgid "Description of configuration options for ec2"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml22(td)
-msgid "ec2_dmz_host = $my_ip"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml23(td)
-msgid "(StrOpt) The internal IP address of the EC2 API server"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml26(td)
-msgid "ec2_host = $my_ip"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml27(td)
-msgid "(StrOpt) The IP address of the EC2 API server"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml30(td)
-msgid "ec2_listen = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml31(td)
-msgid "(StrOpt) The IP address on which the EC2 API will listen."
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml34(td)
-msgid "ec2_listen_port = 8773"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml35(td)
-msgid "(IntOpt) The port on which the EC2 API will listen."
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml38(td)
-msgid "ec2_path = /services/Cloud"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml39(td)
-msgid "(StrOpt) The path prefix used to call the ec2 API server"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml42(td)
-msgid "ec2_port = 8773"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml43(td)
-msgid "(IntOpt) The port of the EC2 API server"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml46(td)
-msgid "ec2_private_dns_show_ip = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml47(td)
-msgid ""
-"(BoolOpt) Return the IP address as private dns hostname in describe "
-"instances"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml50(td)
-msgid "ec2_scheme = http"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml51(td)
-msgid ""
-"(StrOpt) The protocol to use when connecting to the EC2 API server (http, "
-"https)"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml54(td)
-msgid "ec2_strict_validation = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml55(td)
-msgid "(BoolOpt) Validate security group names according to EC2 specification"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml58(td)
-msgid "ec2_timestamp_expiry = 300"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml59(td)
-msgid "(IntOpt) Time in seconds before ec2 timestamp expires"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml62(td)
-msgid "ec2_workers = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml63(td)
-msgid ""
-"(IntOpt) Number of workers for EC2 API service. The default will be equal to"
-" the number of CPUs available."
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml66(td)
-#: ./doc/common/tables/keystone-ec2.xml38(td)
-msgid "keystone_ec2_url = http://localhost:5000/v2.0/ec2tokens"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml67(td)
-#: ./doc/common/tables/keystone-ec2.xml39(td)
-msgid "(StrOpt) URL to get token from ec2 request."
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml70(td)
-msgid "lockout_attempts = 5"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml71(td)
-msgid "(IntOpt) Number of failed auths before lockout."
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml74(td)
-msgid "lockout_minutes = 15"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml75(td)
-msgid "(IntOpt) Number of minutes to lockout if triggered."
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml78(td)
-msgid "lockout_window = 15"
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml79(td)
-msgid "(IntOpt) Number of minutes for lockout window."
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml82(td)
-msgid "region_list ="
-msgstr ""
-
-#: ./doc/common/tables/nova-ec2.xml83(td)
-msgid "(ListOpt) List of region=fqdn pairs separated by commas"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-account-auditor.xml7(literal)
-msgid "[account-auditor]"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-account-auditor.xml18(td)
-msgid "log_name = account-auditor"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-account-auditor.xml30(td)
-#: ./doc/common/tables/swift-container-server-container-auditor.xml30(td)
-msgid "interval = 1800"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-account-auditor.xml39(td)
-msgid "accounts_per_second = 200"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-account-auditor.xml39(td)
-msgid ""
-"Maximum accounts audited per second. Should be tuned according to individual"
-" system specs. 0 is unlimited."
-msgstr ""
-
-#: ./doc/common/tables/trove-zeromq.xml27(td)
-#: ./doc/common/tables/ceilometer-rpc.xml55(td)
-#: ./doc/common/tables/heat-zeromq.xml27(td)
-#: ./doc/common/tables/neutron-zeromq.xml27(td)
-msgid "(IntOpt) Number of ZeroMQ contexts, defaults to 1"
-msgstr ""
-
-#: ./doc/common/tables/trove-zeromq.xml35(td)
-#: ./doc/common/tables/ceilometer-rpc.xml63(td)
-#: ./doc/common/tables/heat-zeromq.xml35(td)
-#: ./doc/common/tables/neutron-zeromq.xml35(td)
-msgid "(StrOpt) Directory for holding IPC sockets"
-msgstr ""
-
-#: ./doc/common/tables/trove-zeromq.xml38(td)
-msgid ""
-"rpc_zmq_matchmaker = "
-"trove.openstack.common.rpc.matchmaker.MatchMakerLocalhost"
-msgstr ""
-
-#: ./doc/common/tables/trove-zeromq.xml39(td)
-#: ./doc/common/tables/ceilometer-rpc.xml67(td)
-#: ./doc/common/tables/heat-zeromq.xml39(td)
-#: ./doc/common/tables/neutron-zeromq.xml39(td)
-msgid "(StrOpt) MatchMaker driver"
-msgstr ""
-
-#: ./doc/common/tables/trove-zeromq.xml43(td)
-#: ./doc/common/tables/ceilometer-rpc.xml71(td)
-#: ./doc/common/tables/heat-zeromq.xml43(td)
-#: ./doc/common/tables/neutron-zeromq.xml43(td)
-msgid "(IntOpt) ZeroMQ receiver listening port"
-msgstr ""
-
-#: ./doc/common/tables/heat-database.xml8(caption)
-#: ./doc/common/tables/ceilometer-database.xml8(caption)
-#: ./doc/common/tables/cinder-database.xml8(caption)
-#: ./doc/common/tables/trove-database.xml8(caption)
-#: ./doc/common/tables/keystone-database.xml8(caption)
-msgid "Description of configuration options for database"
-msgstr ""
-
-#: ./doc/common/tables/heat-database.xml22(td)
-#: ./doc/common/tables/cinder-database.xml22(td)
-#: ./doc/common/tables/nova-baremetal.xml22(td)
-msgid "db_backend = sqlalchemy"
-msgstr ""
-
-#: ./doc/common/tables/heat-database.xml23(td)
-msgid "(StrOpt) The backend to use for db."
-msgstr ""
-
-#: ./doc/common/tables/heat-database.xml26(td)
-msgid "sqlite_db = heat.sqlite"
-msgstr ""
-
-#: ./doc/common/tables/heat-database.xml27(td)
-#: ./doc/common/tables/cinder-common.xml167(td)
-msgid "(StrOpt) the filename to use with sqlite"
-msgstr ""
-
-#: ./doc/common/tables/heat-database.xml31(td)
-#: ./doc/common/tables/cinder-common.xml171(td)
-msgid "(BoolOpt) If true, use synchronous mode for sqlite"
-msgstr ""
-
-#: ./doc/common/tables/heat-database.xml41(td)
-msgid ""
-"connection = sqlite:////usr/lib/python/site-"
-"packages/heat/openstack/common/db/$sqlite_db"
-msgstr ""
-
-#: ./doc/common/tables/heat-database.xml54(td)
-#: ./doc/common/tables/cinder-common.xml230(td)
-msgid "(IntOpt) timeout before idle sql connections are reaped"
-msgstr ""
-
-#: ./doc/common/tables/heat-database.xml66(td)
-#: ./doc/common/tables/cinder-storage.xml150(td)
-msgid ""
-"(IntOpt) maximum db connection retries during startup. (setting -1 implies "
-"an infinite retry count)"
-msgstr ""
-
-#: ./doc/common/tables/heat-database.xml78(td)
-#: ./doc/common/tables/cinder-common.xml234(td)
-msgid "(IntOpt) interval between retries of opening a sql connection"
-msgstr ""
-
-#: ./doc/common/tables/heat-database.xml81(td)
-#: ./doc/common/tables/ceilometer-database.xml85(td)
-#: ./doc/common/tables/neutron-db.xml93(td)
-msgid "slave_connection ="
-msgstr ""
-
-#: ./doc/common/tables/keystone-catalog.xml8(caption)
-msgid "Description of configuration options for catalog"
-msgstr ""
-
-#: ./doc/common/tables/keystone-catalog.xml19(th)
-msgid "[catalog]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-catalog.xml22(td)
-msgid "driver = keystone.catalog.backends.sql.Catalog"
-msgstr ""
-
-#: ./doc/common/tables/keystone-catalog.xml23(td)
-msgid "(StrOpt) Keystone catalog backend driver."
-msgstr ""
-
-#: ./doc/common/tables/keystone-catalog.xml27(td)
-msgid ""
-"(IntOpt) Maximum number of entities that will be returned in a catalog "
-"collection."
-msgstr ""
-
-#: ./doc/common/tables/keystone-catalog.xml30(td)
-msgid "template_file = default_catalog.templates"
-msgstr ""
-
-#: ./doc/common/tables/keystone-catalog.xml31(td)
-msgid ""
-"(StrOpt) Catalog template file name for use with the template catalog "
-"backend."
+"(StrOpt) The messaging driver to use, defaults to rabbit. Other drivers "
+"include qpid and zmq."
+msgstr ""
+
+#: ./doc/common/tables/keystone-amqp.xml55(td)
+#: ./doc/common/tables/glance-amqp.xml43(td)
+#: ./doc/common/tables/cinder-rpc.xml191(td)
+#: ./doc/common/tables/nova-rpc_all.xml159(td)
+#: ./doc/common/tables/nova-rpc.xml51(td)
+msgid "(IntOpt) Size of RPC connection pool."
+msgstr "(整数オプション) RPC 接続プールの容量。"
+
+#: ./doc/common/tables/keystone-amqp.xml59(td)
+#: ./doc/common/tables/glance-amqp.xml47(td)
+#: ./doc/common/tables/cinder-rpc.xml195(td)
+#: ./doc/common/tables/nova-rpc_all.xml163(td)
+#: ./doc/common/tables/nova-rpc.xml55(td)
+msgid "(IntOpt) Seconds to wait for a response from a call."
+msgstr ""
+
+#: ./doc/common/tables/keystone-amqp.xml63(td)
+#: ./doc/common/tables/glance-amqp.xml51(td)
+#: ./doc/common/tables/cinder-rpc.xml199(td)
+#: ./doc/common/tables/nova-rpc_all.xml167(td)
+#: ./doc/common/tables/nova-rpc.xml59(td)
+msgid "(IntOpt) Size of RPC greenthread pool."
 msgstr ""
 
 #: ./doc/common/tables/swift-object-server-DEFAULT.xml21(td)
 msgid "bind_port = 6000"
 msgstr ""
 
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml45(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml64(td)
-msgid "expiring_objects_container_divisor = 86400"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml48(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml67(td)
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml24(td)
-msgid "expiring_objects_account_name = expiring_objects"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml115(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml118(td)
-msgid "client_timeout = 60"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-DEFAULT.xml115(td)
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml118(td)
-msgid "Timeout to read one chunk from a client external services"
+#: ./doc/common/tables/swift-object-server-DEFAULT.xml112(td)
+#: ./doc/common/tables/swift-container-server-container-updater.xml36(td)
+#: ./doc/common/tables/swift-container-server-app-container-server.xml36(td)
+msgid "node_timeout = 3"
 msgstr ""
 
 #: ./doc/common/tables/swift-object-server-DEFAULT.xml118(td)
@@ -38046,415 +38110,156 @@ msgstr ""
 msgid "Size of chunks to read/write to disk"
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml8(caption)
-#: ./doc/common/tables/neutron-rootwrap.xml8(caption)
-#: ./doc/common/tables/nova-rootwrap.xml8(caption)
-msgid "Description of configuration options for rootwrap"
+#: ./doc/common/tables/cinder-zones.xml8(caption)
+msgid "Description of configuration options for zones"
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml22(td)
-msgid "filters_path = /etc/cinder/rootwrap.d,/usr/share/cinder/rootwrap"
+#: ./doc/common/tables/cinder-zones.xml22(td)
+msgid "cloned_volume_same_az = True"
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml23(td)
-#: ./doc/common/tables/neutron-rootwrap.xml23(td)
-#: ./doc/common/tables/nova-rootwrap.xml23(td)
+#: ./doc/common/tables/cinder-zones.xml23(td)
 msgid ""
-"List of directories to load filter definitions from (separated by ','). "
-"These directories MUST all be only writeable by root !"
+"(BoolOpt) Ensure that the new volumes are the same AZ as snapshot or source "
+"volume"
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml26(td)
-#: ./doc/common/tables/neutron-rootwrap.xml26(td)
-#: ./doc/common/tables/nova-rootwrap.xml26(td)
-msgid "exec_dirs = /sbin,/usr/sbin,/bin,/usr/bin"
+#: ./doc/common/tables/cinder-scality.xml8(caption)
+msgid "Description of configuration options for scality"
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml27(td)
-#: ./doc/common/tables/neutron-rootwrap.xml27(td)
-#: ./doc/common/tables/nova-rootwrap.xml27(td)
+#: ./doc/common/tables/cinder-scality.xml30(td)
+msgid "scality_sofs_volume_dir = cinder/volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-scality.xml31(td)
+msgid "(StrOpt) Path from Scality SOFS root to volume dir"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml7(literal)
+msgid "[filter:tempauth]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml18(td)
+msgid "use = egg:swift#tempauth"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml21(td)
+msgid "set log_name = tempauth"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml36(td)
+msgid "reseller_prefix = AUTH"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml36(td)
+msgid "The naming scope for the auth service. Swift"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml39(td)
+msgid "auth_prefix = /auth/"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml39(td)
 msgid ""
-"List of directories to search executables in, in case filters do not "
-"explicitely specify a full path (separated by ',') If not specified, "
-"defaults to system PATH environment variable. These directories MUST all be "
-"only writeable by root !"
+"The HTTP request path prefix for the auth service. Swift itself reserves "
+"anything beginning with the letter `v`."
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml31(td)
-#: ./doc/common/tables/neutron-rootwrap.xml31(td)
-#: ./doc/common/tables/nova-rootwrap.xml31(td)
-msgid "Enable logging to syslog Default value is False"
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml42(td)
+msgid "token_life = 86400"
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml34(td)
-#: ./doc/common/tables/neutron-rootwrap.xml34(td)
-#: ./doc/common/tables/nova-rootwrap.xml34(td)
-msgid "syslog_log_facility = syslog"
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml42(td)
+msgid "The number of seconds a token is valid."
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml35(td)
-#: ./doc/common/tables/neutron-rootwrap.xml35(td)
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml45(td)
+msgid "allow_overrides = true"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml48(td)
+msgid "storage_url_scheme = default"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml48(td)
 msgid ""
-"Which syslog facility to use. Valid values include auth, authpriv, syslog, "
-"local0, local1... Default value is 'syslog'"
+"Scheme to return with storage urls: http, https, or default (chooses based "
+"on what the server is running as) This can be useful with an SSL load "
+"balancer in front of a non-SSL server."
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml38(td)
-#: ./doc/common/tables/neutron-rootwrap.xml38(td)
-#: ./doc/common/tables/nova-rootwrap.xml38(td)
-msgid "syslog_log_level = ERROR"
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml51(td)
+msgid "user_admin_admin = admin .admin .reseller_admin"
 msgstr ""
 
-#: ./doc/common/tables/cinder-rootwrap.xml39(td)
-#: ./doc/common/tables/neutron-rootwrap.xml39(td)
-#: ./doc/common/tables/nova-rootwrap.xml39(td)
-msgid ""
-"Which messages to log. INFO means log all usage ERROR means only log "
-"unsuccessful attempts"
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml54(td)
+msgid "user_test_tester = testing .admin"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-database.xml22(td)
-msgid "database_connection = None"
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml57(td)
+msgid "user_test2_tester2 = testing2 .admin"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-database.xml23(td)
-msgid "(StrOpt) DEPRECATED - Database connection string."
+#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml60(td)
+msgid "user_test_tester3 = testing3"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-database.xml26(td)
-msgid "mysql_engine = InnoDB"
+#: ./doc/common/tables/neutron-agent.xml8(caption)
+msgid "Description of configuration options for agent"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-database.xml27(td)
-msgid "(StrOpt) MySQL engine to use."
+#: ./doc/common/tables/neutron-agent.xml22(td)
+msgid "external_pids = $state_path/external/pids"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-database.xml30(td)
-msgid "sqlite_db = ceilometer.sqlite"
+#: ./doc/common/tables/neutron-agent.xml23(td)
+msgid "(StrOpt) Location to store child pid files"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-database.xml45(td)
-msgid ""
-"connection = sqlite:////usr/lib/python/site-"
-"packages/ceilometer/openstack/common/db/$sqlite_db"
+#: ./doc/common/tables/neutron-agent.xml26(td)
+#: ./doc/common/tables/nova-network.xml170(td)
+msgid "network_device_mtu = None"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-database.xml89(td)
-msgid "time_to_live = -1"
+#: ./doc/common/tables/neutron-agent.xml27(td)
+msgid "(IntOpt) MTU setting for device."
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-database.xml90(td)
-msgid ""
-"(IntOpt) Number of seconds that samples are kept in the database for (&lt;= "
-"0 means forever)."
+#: ./doc/common/tables/cinder-emc.xml8(caption)
+msgid "Description of configuration options for emc"
 msgstr ""
 
-#: ./doc/common/tables/cinder-nexenta_nfs.xml8(caption)
-msgid "Description of configuration options for nexenta_nfs"
+#: ./doc/common/tables/cinder-emc.xml22(td)
+msgid "cinder_emc_config_file = /etc/cinder/cinder_emc_config.xml"
 msgstr ""
 
-#: ./doc/common/tables/cinder-nexenta_nfs.xml22(td)
-msgid "nexenta_mount_point_base = $state_path/mnt"
+#: ./doc/common/tables/cinder-emc.xml23(td)
+msgid "(StrOpt) use this file for cinder emc plugin config data"
 msgstr ""
 
-#: ./doc/common/tables/cinder-nexenta_nfs.xml23(td)
-msgid "(StrOpt) Base dir containing mount points for nfs shares"
+#: ./doc/common/tables/cinder-emc.xml26(td)
+msgid "max_luns_per_storage_group = 256"
 msgstr ""
 
-#: ./doc/common/tables/cinder-nexenta_nfs.xml26(td)
-msgid "nexenta_nms_cache_volroot = True"
+#: ./doc/common/tables/cinder-emc.xml27(td)
+msgid "(IntOpt) Default max number of LUNs in a storage group"
 msgstr ""
 
-#: ./doc/common/tables/cinder-nexenta_nfs.xml27(td)
-msgid ""
-"(BoolOpt) If set True cache NexentaStor appliance volroot option value."
+#: ./doc/common/tables/cinder-emc.xml30(td)
+msgid "naviseccli_path ="
 msgstr ""
 
-#: ./doc/common/tables/cinder-nexenta_nfs.xml30(td)
-msgid "nexenta_shares_config = /etc/cinder/nfs_shares"
+#: ./doc/common/tables/cinder-emc.xml31(td)
+msgid "(StrOpt) Naviseccli Path"
 msgstr ""
 
-#: ./doc/common/tables/cinder-nexenta_nfs.xml34(td)
-msgid "nexenta_volume_compression = on"
+#: ./doc/common/tables/cinder-emc.xml34(td)
+msgid "storage_vnx_pool_name = None"
 msgstr ""
 
-#: ./doc/common/tables/cinder-nexenta_nfs.xml35(td)
-msgid "(StrOpt) Default compression value for new ZFS folders."
-msgstr ""
-
-#: ./doc/common/tables/heat-waitcondition_api.xml8(caption)
-msgid "Description of configuration options for waitcondition_api"
-msgstr ""
-
-#: ./doc/common/tables/heat-waitcondition_api.xml22(td)
-#: ./doc/common/tables/heat-api.xml30(td)
-msgid "heat_waitcondition_server_url ="
-msgstr ""
-
-#: ./doc/common/tables/heat-waitcondition_api.xml23(td)
-#: ./doc/common/tables/heat-api.xml31(td)
-msgid "(StrOpt) URL of the Heat waitcondition server."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml7(literal)
-msgid "[filter:bulk]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml18(td)
-msgid "use = egg:swift#bulk"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml21(td)
-msgid "max_containers_per_extraction = 10000"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml24(td)
-msgid "max_failed_extractions = 1000"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml27(td)
-msgid "max_deletes_per_request = 10000"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml30(td)
-msgid "max_failed_deletes = 1000"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml33(td)
-msgid "yield_frequency = 10"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml36(td)
-msgid "delete_container_retry_count = 0"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_vlan.xml8(caption)
-msgid "Description of configuration options for ml2_vlan"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_vlan.xml19(th)
-msgid "[ml2_type_vlan]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_vlan.xml23(td)
-msgid ""
-"(ListOpt) List of &lt;physical_network&gt;:&lt;vlan_min&gt;:&lt;vlan_max&gt;"
-" or &lt;physical_network&gt; specifying physical_network names usable for "
-"VLAN provider and tenant networks, as well as ranges of VLAN tags on each "
-"available for allocation to tenant networks."
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml22(td)
-msgid "allow_instance_snapshots = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml23(td)
-msgid "(BoolOpt) Permit instance snapshot operations."
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml26(td)
-msgid "allow_migrate_to_same_host = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml27(td)
-msgid ""
-"(BoolOpt) Allow migrate machine to the same host. Useful when testing in "
-"single-host environments."
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml30(td)
-msgid "allow_resize_to_same_host = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml31(td)
-msgid ""
-"(BoolOpt) Allow destination machine to match source for resize. Useful when "
-"testing in single-host environments."
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml35(td)
-msgid "(IntOpt) Number of seconds between subsequent usage refreshes"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml38(td)
-msgid "max_local_block_devices = 3"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml39(td)
-msgid ""
-"(IntOpt) Maximum number of devices that will result in a local image being "
-"created on the hypervisor node. Setting this to 0 means nova will allow only"
-" boot from volume. A negative number means unlimited."
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml42(td)
-msgid "osapi_compute_unique_server_name_scope ="
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml43(td)
-msgid ""
-"(StrOpt) When set, compute API will consider duplicate hostnames invalid "
-"within the specified scope, regardless of case. Should be empty, \"project\""
-" or \"global\"."
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml47(td)
-msgid ""
-"(IntOpt) The maximum number of items returned in a single response from a "
-"collection resource"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml51(td)
-msgid "(IntOpt) The maximum body size per each osapi request(bytes)"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml54(td)
-msgid "password_length = 12"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml55(td)
-msgid "(IntOpt) Length of generated instance admin passwords"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml59(td)
-#: ./doc/common/tables/cinder-common.xml139(td)
-msgid "(StrOpt) Rule checked when requested rule is not found"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml63(td)
-#: ./doc/common/tables/cinder-common.xml143(td)
-msgid "(StrOpt) JSON file representing policy"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml67(td)
-msgid "(IntOpt) Number of seconds until a reservation expires"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml70(td)
-msgid "resize_fs_using_block_device = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml71(td)
-msgid ""
-"(BoolOpt) Attempt to resize the filesystem by accessing the image over a "
-"block device. This is done by the host and may not be necessary if the image"
-" contains a recent version of cloud-init. Possible mechanisms require the "
-"nbd driver (for qcow and raw), or loop (for raw)."
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml74(td)
-#: ./doc/common/tables/cinder-common.xml202(td)
-msgid "until_refresh = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-policy.xml75(td)
-msgid "(IntOpt) Count of reservations until usage is refreshed"
-msgstr ""
-
-#: ./doc/common/tables/keystone-amqp.xml8(caption)
-#: ./doc/common/tables/glance-amqp.xml8(caption)
-#: ./doc/common/tables/heat-amqp.xml8(caption)
-#: ./doc/common/tables/ceilometer-amqp.xml8(caption)
-#: ./doc/common/tables/trove-amqp.xml8(caption)
-msgid "Description of configuration options for amqp"
-msgstr ""
-
-#: ./doc/common/tables/keystone-amqp.xml34(td)
-#: ./doc/common/tables/heat-amqp.xml38(td)
-#: ./doc/common/tables/ceilometer-exchange.xml30(td)
-#: ./doc/common/tables/nova-compute.xml58(td)
-msgid "default_publisher_id = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-amqp.xml35(td)
-#: ./doc/common/tables/neutron-notifier.xml27(td)
-#: ./doc/common/tables/heat-amqp.xml39(td)
-#: ./doc/common/tables/trove-common.xml51(td)
-#: ./doc/common/tables/ceilometer-exchange.xml31(td)
-#: ./doc/common/tables/nova-compute.xml59(td)
-msgid "(StrOpt) Default publisher_id for outgoing notifications"
-msgstr ""
-
-#: ./doc/common/tables/neutron-logging.xml26(td)
-#: ./doc/common/tables/heat-logging.xml22(td)
-#: ./doc/common/tables/trove-common.xml34(td)
-msgid ""
-"default_log_levels = amqp=WARN, amqplib=WARN, boto=WARN, qpid=WARN, "
-"sqlalchemy=WARN, suds=INFO, iso8601=WARN"
-msgstr ""
-
-#: ./doc/common/tables/neutron-logging.xml27(td)
-#: ./doc/common/tables/heat-logging.xml23(td)
-#: ./doc/common/tables/nova-logging.xml27(td)
-#: ./doc/common/tables/trove-common.xml35(td)
-msgid "(ListOpt) list of logger=LEVEL pairs"
-msgstr ""
-
-#: ./doc/common/tables/neutron-logging.xml86(td)
-#: ./doc/common/tables/neutron-nec.xml58(td)
-msgid "use_ssl = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-logging.xml87(td)
-msgid "(BoolOpt) Enable SSL on the API server"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_cassandra.xml8(caption)
-msgid "Description of configuration options for db_cassandra"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_cassandra.xml19(th)
-msgid "[cassandra]"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_cassandra.xml26(td)
-msgid "mount_point = /var/lib/cassandra"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_cassandra.xml30(td)
-msgid "tcp_ports = 7000, 7001, 9042, 9160"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_cassandra.xml35(td)
-#: ./doc/common/tables/trove-db_mysql.xml39(td)
-#: ./doc/common/tables/trove-db_redis.xml35(td)
-#: ./doc/common/tables/trove-db_couchbase.xml35(td)
-#: ./doc/common/tables/trove-db_percona.xml39(td)
-msgid ""
-"(ListOpt) List of UDP ports and/or port ranges to open in the security group"
-" (only applicable if trove_security_groups_support is True)"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_cassandra.xml38(td)
-msgid "usage_timeout = 600"
-msgstr ""
-
-#: ./doc/common/tables/glance-rpc.xml22(td)
-msgid ""
-"allowed_rpc_exception_modules = openstack.common.exception, "
-"glance.common.exception, exceptions"
-msgstr ""
-
-#: ./doc/common/tables/glance-rpc.xml23(td)
-#: ./doc/common/tables/trove-rpc.xml23(td)
-msgid ""
-"(ListOpt) Modules of exceptions that are permitted to be recreatedupon "
-"receiving exception data from an rpc call."
-msgstr ""
-
-#: ./doc/common/tables/nova-authentication.xml8(caption)
-msgid "Description of configuration options for authentication"
-msgstr ""
-
-#: ./doc/common/tables/nova-authentication.xml22(td)
-#: ./doc/common/tables/glance-registry.xml38(td)
-#: ./doc/common/tables/cinder-auth.xml22(td)
-msgid "auth_strategy = noauth"
-msgstr ""
-
-#: ./doc/common/tables/nova-authentication.xml23(td)
-#: ./doc/common/tables/ceilometer-auth.xml23(td)
-msgid "(StrOpt) The strategy to use for auth: noauth or keystone."
+#: ./doc/common/tables/cinder-emc.xml35(td)
+msgid "(StrOpt) ISCSI pool name"
 msgstr ""
 
 #: ./doc/common/tables/cinder-vmware.xml26(td)
@@ -38532,116 +38337,1849 @@ msgid ""
 "location for bug work-arounds."
 msgstr ""
 
-#: ./doc/common/tables/glance-sheepdog.xml8(caption)
-msgid "Description of configuration options for sheepdog"
+#: ./doc/common/tables/neutron-ml2_flat.xml8(caption)
+msgid "Description of configuration options for ml2_flat"
 msgstr ""
 
-#: ./doc/common/tables/glance-sheepdog.xml22(td)
-msgid "sheepdog_store_address = 127.0.0.1"
+#: ./doc/common/tables/neutron-ml2_flat.xml19(th)
+msgid "[ml2_type_flat]"
 msgstr ""
 
-#: ./doc/common/tables/glance-sheepdog.xml23(td)
-msgid "(StrOpt) IP address of sheep daemon."
+#: ./doc/common/tables/neutron-ml2_flat.xml22(td)
+msgid "flat_networks ="
 msgstr ""
 
-#: ./doc/common/tables/glance-sheepdog.xml26(td)
-msgid "sheepdog_store_chunk_size = 64"
-msgstr ""
-
-#: ./doc/common/tables/glance-sheepdog.xml27(td)
+#: ./doc/common/tables/neutron-ml2_flat.xml23(td)
 msgid ""
-"(IntOpt) Images will be chunked into objects of this size (in megabytes). "
-"For best performance, this should be a power of two."
+"(ListOpt) List of physical_network names with which flat networks can be "
+"created. Use * to allow flat networks with arbitrary physical_network names."
 msgstr ""
 
-#: ./doc/common/tables/glance-sheepdog.xml30(td)
-msgid "sheepdog_store_port = 7000"
+#: ./doc/common/tables/heat-metadata_api.xml8(caption)
+msgid "Description of configuration options for metadata_api"
 msgstr ""
 
-#: ./doc/common/tables/glance-sheepdog.xml31(td)
-msgid "(IntOpt) Port of sheep daemon."
+#: ./doc/common/tables/heat-metadata_api.xml22(td)
+#: ./doc/common/tables/heat-api.xml22(td)
+msgid "heat_metadata_server_url ="
 msgstr ""
 
-#: ./doc/common/tables/keystone-notification.xml23(td)
+#: ./doc/common/tables/heat-metadata_api.xml23(td)
+#: ./doc/common/tables/heat-api.xml23(td)
+msgid "(StrOpt) URL of the Heat metadata server."
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml8(caption)
+msgid "Description of configuration options for upgrade_levels"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml22(td)
+msgid "scheduler = nova.cells.scheduler.CellsScheduler"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml23(td)
+msgid "(StrOpt) Cells scheduler to use"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml26(th)
+#: ./doc/common/tables/nova-rpc_all.xml212(th)
+#: ./doc/common/tables/nova-rpc.xml76(th)
+msgid "[upgrade_levels]"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml29(td)
+msgid "cells = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml30(td)
+msgid "(StrOpt) Set a version cap for messages sent to local cells services"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml33(td)
+msgid "cert = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml34(td)
+msgid "(StrOpt) Set a version cap for messages sent to cert services"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml37(td)
+msgid "compute = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml38(td)
 msgid ""
-"(StrOpt) onready allows you to send a notification when the process is ready"
-" to serve For example, to have it notify using systemd, one could set shell "
-"command: \"onready = systemd-notify --ready\" or a module with notify() "
-"method: \"onready = keystone.common.systemd\"."
+"(StrOpt) Set a version cap for messages sent to compute services. If you "
+"plan to do a live upgrade from havana to icehouse, you should set this "
+"option to \"icehouse-compat\" before beginning the live upgrade procedure."
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml8(caption)
-msgid "Description of configuration options for hyperv_agent"
+#: ./doc/common/tables/nova-upgrade_levels.xml41(td)
+msgid "conductor = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml22(td)
-msgid "enable_metrics_collection = False"
+#: ./doc/common/tables/nova-upgrade_levels.xml42(td)
+msgid "(StrOpt) Set a version cap for messages sent to conductor services"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml23(td)
+#: ./doc/common/tables/nova-upgrade_levels.xml45(td)
+msgid "console = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml46(td)
+msgid "(StrOpt) Set a version cap for messages sent to console services"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml49(td)
+msgid "consoleauth = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml50(td)
+msgid "(StrOpt) Set a version cap for messages sent to consoleauth services"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml53(td)
+msgid "intercell = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml54(td)
+msgid "(StrOpt) Set a version cap for messages sent between cells services"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml57(td)
+msgid "network = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml58(td)
+msgid "(StrOpt) Set a version cap for messages sent to network services"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml61(td)
+msgid "scheduler = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-upgrade_levels.xml62(td)
+msgid "(StrOpt) Set a version cap for messages sent to scheduler services"
+msgstr ""
+
+#: ./doc/common/tables/neutron-kombu.xml8(caption)
+#: ./doc/common/tables/nova-kombu.xml8(caption)
+msgid "Description of configuration options for kombu"
+msgstr ""
+
+#: ./doc/common/tables/neutron-kombu.xml35(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml39(td)
 msgid ""
-"(BoolOpt) Enables metrics collections for switch ports by using Hyper-V's "
-"metric APIs. Collected data can by retrieved by other apps and services, "
-"e.g.: Ceilometer. Requires Hyper-V / Windows Server 2012 and above"
+"(StrOpt) If SSL is enabled, the SSL version to use. Valid values are TLSv1, "
+"SSLv23 and SSLv3. SSLv2 might be available on some distributions."
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml26(td)
-msgid "local_network_vswitch = private"
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml8(caption)
+msgid "Description of configuration options for netapp_cdot_iscsi"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml27(td)
-msgid "(StrOpt) Private vswitch name used for local networks"
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml38(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml38(td)
+msgid "netapp_size_multiplier = 1.2"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml30(td)
-msgid "metrics_max_retries = 100"
-msgstr ""
-
-#: ./doc/common/tables/neutron-hyperv_agent.xml31(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml39(td)
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml39(td)
 msgid ""
-"(IntOpt) Specifies the maximum number of retries to enable Hyper-V's port "
-"metrics collection. The agent will try to enable the feature once every "
-"polling_interval period for at most metrics_max_retries or until it "
-"succeedes."
+"(FloatOpt) The quantity to be multiplied by the requested volume size to "
+"ensure enough space is available on the virtual storage server (Vserver) to "
+"fulfill the volume creation request."
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml34(td)
-msgid "physical_network_vswitch_mappings ="
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml54(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml58(td)
+msgid "netapp_vserver = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml35(td)
+#: ./doc/common/tables/cinder-netapp_cdot_iscsi.xml55(td)
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml59(td)
 msgid ""
-"(ListOpt) List of &lt;physical_network&gt;:&lt;vswitch&gt; where the "
-"physical networks can be expressed with wildcards, e.g.: .\"*:external\""
+"(StrOpt) This option specifies the virtual storage server (Vserver) name on "
+"the storage cluster on which provisioning of block storage volumes should "
+"occur. If using the NFS storage protocol, this parameter is mandatory for "
+"storage service catalog support (utilized by Cinder volume type extra_specs "
+"support). If this option is specified, the exports belonging to the Vserver "
+"will only be used for provisioning in the future. Block storage volumes on "
+"exports not belonging to the Vserver specified by this option will continue "
+"to function normally."
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml38(td)
-#: ./doc/common/tables/neutron-sdnve.xml85(td)
-msgid "polling_interval = 2"
+#: ./doc/common/tables/neutron-ml2_ofa.xml8(caption)
+msgid "Description of configuration options for ml2_ofa"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml39(td)
+#: ./doc/common/tables/neutron-ml2_ofa.xml22(td)
+msgid "ofp_listen_host ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ofa.xml23(td)
+msgid "(StrOpt) openflow listen host"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ofa.xml26(td)
+msgid "ofp_ssl_listen_port = 6633"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ofa.xml27(td)
+msgid "(IntOpt) openflow ssl listen port"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ofa.xml30(td)
+msgid "ofp_tcp_listen_port = 6633"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ofa.xml31(td)
+msgid "(IntOpt) openflow tcp listen port"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ofa.xml37(td)
+msgid "get_datapath_retry_times = 60"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ofa.xml38(td)
+msgid "(IntOpt) Number of seconds to retry acquiring an Open vSwitch datapath"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml22(td)
+msgid "admin_role = admin"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml23(td)
+msgid "(StrOpt) Role used to identify an authenticated user as administrator."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml26(td)
+msgid "allow_anonymous_access = False"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml27(td)
 msgid ""
-"(IntOpt) The number of seconds the agent will wait between polling for local"
-" device changes."
+"(BoolOpt) Allow unauthenticated users to access the API with read-only "
+"privileges. This only applies when using ContextMiddleware."
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml42(th)
-msgid "[HYPERV]"
+#: ./doc/common/tables/glance-api.xml30(td)
+msgid "default_publisher_id = image.localhost"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml50(td)
-msgid "(StrOpt) Network type for tenant networks (local, flat, vlan or none)"
+#: ./doc/common/tables/glance-api.xml31(td)
+msgid "(StrOpt) Default publisher_id for outgoing notifications."
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml56(td)
-#: ./doc/common/tables/nova-hyperv.xml30(td)
-msgid "force_hyperv_utils_v1 = False"
+#: ./doc/common/tables/glance-api.xml34(td)
+msgid "default_store = file"
 msgstr ""
 
-#: ./doc/common/tables/neutron-hyperv_agent.xml57(td)
-#: ./doc/common/tables/nova-hyperv.xml31(td)
-msgid "(BoolOpt) Force V1 WMI utility classes"
+#: ./doc/common/tables/glance-api.xml35(td)
+msgid ""
+"(StrOpt) Default scheme to use to store image data. The scheme must be "
+"registered by one of the stores defined by the 'known_stores' config option."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml38(td)
+#: ./doc/common/tables/ceilometer-api.xml22(td)
+#: ./doc/common/tables/cinder-api.xml34(td)
+msgid "enable_v1_api = True"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml39(td)
+msgid "(BoolOpt) Deploy the v1 OpenStack Images API."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml42(td)
+msgid "enable_v1_registry = True"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml43(td)
+msgid "(BoolOpt) Deploy the v1 OpenStack Registry API."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml46(td)
+#: ./doc/common/tables/cinder-api.xml38(td)
+msgid "enable_v2_api = True"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml47(td)
+msgid "(BoolOpt) Deploy the v2 OpenStack Images API."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml50(td)
+msgid "enable_v2_registry = True"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml51(td)
+msgid "(BoolOpt) Deploy the v2 OpenStack Registry API."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml54(td)
+msgid "image_size_cap = 1099511627776"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml55(td)
+msgid ""
+"(IntOpt) Maximum size of image a user can upload in bytes. Defaults to "
+"1099511627776 bytes (1 TB)."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml58(td)
+msgid "known_stores = glance.store.filesystem.Store, glance.store.http.Store"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml59(td)
+msgid ""
+"(ListOpt) List of which store classes and store class locations are "
+"currently known to glance at startup."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml62(td)
+msgid "location_strategy = location_order"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml63(td)
+msgid ""
+"(StrOpt) This value sets what strategy will be used to determine the image "
+"location order. Currently two strategies are packaged with Glance "
+"'location_order' and 'store_type'."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml66(td)
+msgid "owner_is_tenant = True"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml67(td)
+msgid ""
+"(BoolOpt) When true, this option sets the owner of an image to be the "
+"tenant. Otherwise, the owner of the image will be the authenticated user "
+"issuing the request."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml70(td)
+msgid "send_identity_headers = False"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml71(td)
+msgid ""
+"(BoolOpt) Whether to pass through headers containing user and tenant "
+"information when making requests to the registry. This allows the registry "
+"to use the context middleware without the keystoneclients' auth_token "
+"middleware, removing calls to the keystone auth service. It is recommended "
+"that when using this option, secure communication between glance api and "
+"glance registry is ensured by means other than auth_token middleware."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml74(td)
+msgid "show_multiple_locations = False"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml75(td)
+msgid ""
+"(BoolOpt) Whether to include the backend image locations in image "
+"properties. Revealing storage location can be a security risk, so use this "
+"setting with caution! The overrides show_image_direct_url."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml78(td)
+msgid "use_user_token = True"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml79(td)
+msgid ""
+"(BoolOpt) Whether to pass through the user token when making requests to the"
+" registry."
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml82(th)
+msgid "[store_type_location_strategy]"
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml85(td)
+msgid "store_type_preference ="
+msgstr ""
+
+#: ./doc/common/tables/glance-api.xml86(td)
+msgid ""
+"(ListOpt) The store names to use to get store preference order. The name "
+"must be registered by one of the stores defined by the 'known_stores' config"
+" option. This option will be applied when you using 'store_type' option as "
+"image location strategy defined by the 'location_strategy' config option."
+msgstr ""
+
+#: ./doc/common/tables/heat-waitcondition_api.xml8(caption)
+msgid "Description of configuration options for waitcondition_api"
+msgstr ""
+
+#: ./doc/common/tables/heat-waitcondition_api.xml22(td)
+#: ./doc/common/tables/heat-api.xml30(td)
+msgid "heat_waitcondition_server_url ="
+msgstr ""
+
+#: ./doc/common/tables/heat-waitcondition_api.xml23(td)
+#: ./doc/common/tables/heat-api.xml31(td)
+msgid "(StrOpt) URL of the Heat waitcondition server."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml7(literal)
+msgid "[filter:gatekeeper]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml18(td)
+msgid "use = egg:swift#gatekeeper"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml21(td)
+msgid "set log_name = gatekeeper"
+msgstr ""
+
+#: ./doc/common/tables/swift-rsyncd-container.xml7(literal)
+msgid "[container]"
+msgstr ""
+
+#: ./doc/common/tables/swift-rsyncd-container.xml7(literal)
+#: ./doc/common/tables/swift-rsyncd-account.xml7(literal)
+#: ./doc/common/tables/swift-rsyncd-object.xml7(literal)
+msgid "rsyncd.conf-sample"
+msgstr ""
+
+#: ./doc/common/tables/swift-rsyncd-container.xml18(td)
+msgid "max connections = 4"
+msgstr ""
+
+#: ./doc/common/tables/swift-rsyncd-container.xml21(td)
+#: ./doc/common/tables/swift-rsyncd-account.xml21(td)
+#: ./doc/common/tables/swift-rsyncd-object.xml21(td)
+msgid "path = /srv/node"
+msgstr ""
+
+#: ./doc/common/tables/swift-rsyncd-container.xml24(td)
+#: ./doc/common/tables/swift-rsyncd-account.xml24(td)
+#: ./doc/common/tables/swift-rsyncd-object.xml24(td)
+msgid "read only = false"
+msgstr ""
+
+#: ./doc/common/tables/swift-rsyncd-container.xml27(td)
+msgid "lock file = /var/lock/container.lock"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml8(caption)
+msgid "Description of configuration options for storwize"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml22(td)
+msgid "storwize_svc_connection_protocol = iSCSI"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml23(td)
+msgid "(StrOpt) Connection protocol (iSCSI/FC)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml26(td)
+msgid "storwize_svc_flashcopy_timeout = 120"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml27(td)
+msgid ""
+"(IntOpt) Maximum number of seconds to wait for FlashCopy to be prepared. "
+"Maximum value is 600 seconds (10 minutes)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml30(td)
+msgid "storwize_svc_iscsi_chap_enabled = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml31(td)
+msgid ""
+"(BoolOpt) Configure CHAP authentication for iSCSI connections (Default: "
+"Enabled)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml34(td)
+msgid "storwize_svc_multihostmap_enabled = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml35(td)
+msgid "(BoolOpt) Allows vdisk to multi host mapping"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml38(td)
+msgid "storwize_svc_multipath_enabled = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml39(td)
+msgid ""
+"(BoolOpt) Connect with multipath (FC only; iSCSI multipath is controlled by "
+"Nova)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml42(td)
+msgid "storwize_svc_vol_autoexpand = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml43(td)
+msgid "(BoolOpt) Storage system autoexpand parameter for volumes (True/False)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml46(td)
+msgid "storwize_svc_vol_compression = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml47(td)
+msgid "(BoolOpt) Storage system compression option for volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml50(td)
+msgid "storwize_svc_vol_easytier = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml51(td)
+msgid "(BoolOpt) Enable Easy Tier for volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml54(td)
+msgid "storwize_svc_vol_grainsize = 256"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml55(td)
+msgid ""
+"(IntOpt) Storage system grain size parameter for volumes (32/64/128/256)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml58(td)
+msgid "storwize_svc_vol_iogrp = 0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml59(td)
+msgid "(IntOpt) The I/O group in which to allocate volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml62(td)
+msgid "storwize_svc_vol_rsize = 2"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml63(td)
+msgid ""
+"(IntOpt) Storage system space-efficiency parameter for volumes (percentage)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml66(td)
+msgid "storwize_svc_vol_warning = 0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml67(td)
+msgid ""
+"(IntOpt) Storage system threshold for volume capacity warnings (percentage)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml70(td)
+msgid "storwize_svc_volpool_name = volpool"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storwize.xml71(td)
+msgid "(StrOpt) Storage system storage pool for volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml8(caption)
+msgid "Description of configuration options for hplefthand"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml22(td)
+msgid "hplefthand_api_url = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml23(td)
+msgid ""
+"(StrOpt) HP LeftHand WSAPI Server Url like https://&lt;LeftHand "
+"ip&gt;:8081/lhos"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml26(td)
+msgid "hplefthand_clustername = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml27(td)
+msgid "(StrOpt) HP LeftHand cluster name"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml30(td)
+msgid "hplefthand_debug = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml31(td)
+msgid "(BoolOpt) Enable HTTP debugging to LeftHand"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml34(td)
+msgid "hplefthand_iscsi_chap_enabled = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml35(td)
+msgid ""
+"(BoolOpt) Configure CHAP authentication for iSCSI connections (Default: "
+"Disabled)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml38(td)
+msgid "hplefthand_password = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml39(td)
+msgid "(StrOpt) HP LeftHand Super user password"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml42(td)
+msgid "hplefthand_username = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hplefthand.xml43(td)
+msgid "(StrOpt) HP LeftHand Super user username"
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml8(caption)
+#: ./doc/common/tables/nova-s3.xml8(caption)
+msgid "Description of configuration options for s3"
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml22(td)
+msgid "s3_store_access_key = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml23(td)
+msgid "(StrOpt) The S3 query token access key."
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml26(td)
+msgid "s3_store_bucket = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml27(td)
+msgid "(StrOpt) The S3 bucket to be used to store the Glance data."
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml30(td)
+msgid "s3_store_bucket_url_format = subdomain"
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml31(td)
+msgid ""
+"(StrOpt) The S3 calling format used to determine the bucket. Either "
+"subdomain or path can be used."
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml34(td)
+msgid "s3_store_create_bucket_on_put = False"
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml35(td)
+msgid ""
+"(BoolOpt) A boolean to determine if the S3 bucket should be created on "
+"upload if it does not exist or if an error should be returned to the user."
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml38(td)
+msgid "s3_store_host = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml39(td)
+msgid "(StrOpt) The host where the S3 server is listening."
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml42(td)
+msgid "s3_store_object_buffer_dir = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml43(td)
+msgid ""
+"(StrOpt) The local directory where uploads will be staged before they are "
+"transferred into S3."
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml46(td)
+msgid "s3_store_secret_key = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-s3.xml47(td)
+msgid "(StrOpt) The S3 query token secret key."
+msgstr ""
+
+#: ./doc/common/tables/nova-rootwrap.xml22(td)
+msgid "filters_path = /etc/nova/rootwrap.d,/usr/share/nova/rootwrap"
+msgstr ""
+
+#: ./doc/common/tables/nova-rootwrap.xml35(td)
+msgid ""
+"Which syslog facility to use. Valid values include auth, authpriv, syslog, "
+"user0, user1... Default value is 'syslog'"
+msgstr ""
+
+#: ./doc/common/tables/heat-loadbalancer.xml8(caption)
+msgid "Description of configuration options for loadbalancer"
+msgstr ""
+
+#: ./doc/common/tables/heat-loadbalancer.xml22(td)
+msgid "loadbalancer_template = None"
+msgstr ""
+
+#: ./doc/common/tables/heat-loadbalancer.xml23(td)
+msgid "(StrOpt) Custom template for the built-in loadbalancer nested stack."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml23(td)
+msgid "(BoolOpt) Deploy the deprecated v1 API."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml27(td)
+msgid "(IntOpt) The maximum body size per request, in bytes"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml30(td)
+msgid "pipeline_cfg_file = pipeline.yaml"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml31(td)
+msgid "(StrOpt) Configuration file for pipeline definition."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml42(td)
+msgid "reserved_metadata_length = 256"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml43(td)
+msgid "(IntOpt) Limit on length of reserved metadata values."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml46(td)
+msgid "reserved_metadata_namespace = metering."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml47(td)
+msgid "(ListOpt) List of metadata prefixes reserved for metering use."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml50(th)
+msgid "[api]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml53(td)
+#: ./doc/common/tables/trove-rpc.xml26(td)
+msgid "host = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml54(td)
+msgid "(StrOpt) The listen IP for the ceilometer API server."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml57(td)
+msgid "port = 8777"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-api.xml58(td)
+msgid "(IntOpt) The port for the ceilometer API server."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml8(caption)
+msgid "Description of configuration options for exchange"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml22(td)
+msgid "cinder_control_exchange = cinder"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml23(td)
+msgid "(StrOpt) Exchange name for Cinder notifications."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml34(td)
+msgid "glance_control_exchange = glance"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml35(td)
+msgid "(StrOpt) Exchange name for Glance notifications."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml38(td)
+msgid "heat_control_exchange = heat"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml39(td)
+msgid "(StrOpt) Exchange name for Heat notifications"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml42(td)
+msgid "http_control_exchanges = ['nova', 'glance', 'neutron', 'cinder']"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml43(td)
+msgid "(MultiStrOpt) Exchanges name to listen for notifications."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml46(td)
+msgid "neutron_control_exchange = neutron"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml47(td)
+msgid "(StrOpt) Exchange name for Neutron notifications."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml50(td)
+msgid "nova_control_exchange = nova"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml51(td)
+msgid "(StrOpt) Exchange name for Nova notifications."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml54(td)
+msgid "sample_source = openstack"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-exchange.xml55(td)
+msgid "(StrOpt) Source for samples emitted on this instance."
+msgstr ""
+
+#: ./doc/common/tables/cinder-lvm.xml8(caption)
+msgid "Description of configuration options for lvm"
+msgstr ""
+
+#: ./doc/common/tables/cinder-lvm.xml22(td)
+msgid "lvm_mirrors = 0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-lvm.xml23(td)
+msgid ""
+"(IntOpt) If set, create lvms with multiple mirrors. Note that this requires "
+"lvm_mirrors + 2 pvs with available space"
+msgstr ""
+
+#: ./doc/common/tables/cinder-lvm.xml26(td)
+msgid "lvm_type = default"
+msgstr ""
+
+#: ./doc/common/tables/cinder-lvm.xml27(td)
+msgid "(StrOpt) Type of LVM volumes to deploy; (default or thin)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-lvm.xml30(td)
+msgid "volume_group = cinder-volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-lvm.xml31(td)
+msgid "(StrOpt) Name for the VG that will contain exported volumes"
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml8(caption)
+msgid "Description of configuration options for dns"
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml22(td)
+msgid "dns_account_id ="
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml26(td)
+msgid "dns_auth_url ="
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml30(td)
+msgid "dns_domain_id ="
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml34(td)
+msgid "dns_domain_name ="
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml38(td)
+msgid "dns_driver = trove.dns.driver.DnsDriver"
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml42(td)
+msgid "dns_endpoint_url = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml46(td)
+msgid "dns_hostname ="
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml50(td)
+msgid "dns_instance_entry_factory = trove.dns.driver.DnsInstanceEntryFactory"
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml54(td)
+msgid "dns_management_base_url ="
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml58(td)
+msgid "dns_passkey ="
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml62(td)
+msgid "dns_region ="
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml66(td)
+msgid "dns_service_type ="
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml70(td)
+msgid "dns_time_out = 120"
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml74(td)
+msgid "dns_ttl = 300"
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml78(td)
+msgid "dns_username ="
+msgstr ""
+
+#: ./doc/common/tables/trove-dns.xml82(td)
+msgid "trove_dns_support = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml34(td)
+msgid "cells_config = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml35(td)
+msgid ""
+"(StrOpt) Configuration file from which to read cells configuration. If "
+"given, overrides reading cells from the database."
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml38(td)
+msgid "driver = nova.cells.rpc_driver.CellsRPCDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml39(td)
+msgid "(StrOpt) Cells communication driver to use"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml46(td)
+msgid "instance_update_num_instances = 1"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml47(td)
+msgid "(IntOpt) Number of instances to update per periodic task run"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml50(td)
+msgid "instance_updated_at_threshold = 3600"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml51(td)
+msgid ""
+"(IntOpt) Number of seconds after an instance was updated or deleted to "
+"continue to update cells"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml58(td)
+msgid "max_hop_count = 10"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml59(td)
+msgid "(IntOpt) Maximum number of hops for cells routing."
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml66(td)
+msgid "mute_weight_multiplier = -10.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml67(td)
+msgid ""
+"(FloatOpt) Multiplier used to weigh mute children. (The value should be "
+"negative.)"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml70(td)
+msgid "mute_weight_value = 1000.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml71(td)
+msgid ""
+"(FloatOpt) Weight value assigned to mute children. (The value should be "
+"positive.)"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml78(td)
+msgid "offset_weight_multiplier = 1.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-cells.xml79(td)
+msgid "(FloatOpt) Multiplier used to weigh offset weigher."
+msgstr ""
+
+#: ./doc/common/tables/trove-volume.xml8(caption)
+msgid "Description of configuration options for volume"
+msgstr ""
+
+#: ./doc/common/tables/trove-volume.xml22(td)
+msgid "block_device_mapping = vdb"
+msgstr ""
+
+#: ./doc/common/tables/trove-volume.xml26(td)
+msgid "cinder_url = http://localhost:8776/v2"
+msgstr ""
+
+#: ./doc/common/tables/trove-volume.xml30(td)
+msgid "device_path = /dev/vdb"
+msgstr ""
+
+#: ./doc/common/tables/trove-volume.xml34(td)
+msgid "trove_volume_support = True"
+msgstr ""
+
+#: ./doc/common/tables/trove-volume.xml35(td)
+msgid "(BoolOpt) Whether to provision a cinder volume for datadir."
+msgstr ""
+
+#: ./doc/common/tables/trove-volume.xml38(td)
+msgid "volume_format_timeout = 120"
+msgstr ""
+
+#: ./doc/common/tables/trove-volume.xml42(td)
+msgid "volume_fstype = ext3"
+msgstr ""
+
+#: ./doc/common/tables/trove-volume.xml46(td)
+msgid "volume_time_out = 60"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml8(caption)
+msgid "Description of configuration options for quotas"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml22(td)
+msgid "max_routes = 30"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml23(td)
+msgid "(IntOpt) Maximum number of routes"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml26(th)
+msgid "[QUOTAS]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml29(td)
+msgid "default_quota = -1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml30(td)
+msgid ""
+"(IntOpt) Default number of resource allowed per tenant. A negative value "
+"means unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml33(td)
+msgid "quota_driver = neutron.db.quota_db.DbQuotaDriver"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml34(td)
+#: ./doc/common/tables/nova-quota.xml35(td)
+msgid "(StrOpt) Default driver to use for quota checks"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml37(td)
+msgid "quota_firewall = 1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml38(td)
+msgid ""
+"(IntOpt) Number of firewalls allowed per tenant. A negative value means "
+"unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml41(td)
+msgid "quota_firewall_policy = 1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml42(td)
+msgid ""
+"(IntOpt) Number of firewall policies allowed per tenant. A negative value "
+"means unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml45(td)
+msgid "quota_firewall_rule = -1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml46(td)
+msgid ""
+"(IntOpt) Number of firewall rules allowed per tenant. A negative value means"
+" unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml49(td)
+msgid "quota_floatingip = 50"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml50(td)
+msgid ""
+"(IntOpt) Number of floating IPs allowed per tenant. A negative value means "
+"unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml53(td)
+msgid "quota_health_monitor = -1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml54(td)
+msgid ""
+"(IntOpt) Number of health monitors allowed per tenant. A negative value "
+"means unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml57(td)
+msgid "quota_items = network, subnet, port"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml58(td)
+msgid "(ListOpt) Resource name(s) that are supported in quota features"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml61(td)
+msgid "quota_member = -1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml62(td)
+msgid ""
+"(IntOpt) Number of pool members allowed per tenant. A negative value means "
+"unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml65(td)
+msgid "quota_network = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml66(td)
+msgid ""
+"(IntOpt) Number of networks allowed per tenant.A negative value means "
+"unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml69(td)
+msgid "quota_network_gateway = 5"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml70(td)
+msgid ""
+"(IntOpt) Number of network gateways allowed per tenant, -1 for unlimited"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml73(td)
+msgid "quota_packet_filter = 100"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml74(td)
+msgid "(IntOpt) Number of packet_filters allowed per tenant, -1 for unlimited"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml77(td)
+msgid "quota_pool = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml78(td)
+msgid ""
+"(IntOpt) Number of pools allowed per tenant. A negative value means "
+"unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml81(td)
+msgid "quota_port = 50"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml82(td)
+msgid ""
+"(IntOpt) Number of ports allowed per tenant. A negative value means "
+"unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml85(td)
+msgid "quota_router = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml86(td)
+msgid ""
+"(IntOpt) Number of routers allowed per tenant. A negative value means "
+"unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml89(td)
+msgid "quota_security_group = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml90(td)
+msgid ""
+"(IntOpt) Number of security groups allowed per tenant. A negative value "
+"means unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml93(td)
+msgid "quota_security_group_rule = 100"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml94(td)
+msgid ""
+"(IntOpt) Number of security rules allowed per tenant. A negative value means"
+" unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml97(td)
+msgid "quota_subnet = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml98(td)
+msgid ""
+"(IntOpt) Number of subnets allowed per tenant, A negative value means "
+"unlimited."
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml101(td)
+msgid "quota_vip = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-quotas.xml102(td)
+msgid ""
+"(IntOpt) Number of vips allowed per tenant. A negative value means "
+"unlimited."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml8(caption)
+msgid "Description of configuration options for storage_nfs"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml23(td)
+msgid ""
+"(StrOpt) Mount options passed to the nfs client. See section of the nfs man "
+"page for details."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml27(td)
+msgid "(StrOpt) Base dir containing mount points for nfs shares."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml30(td)
+msgid "nfs_oversub_ratio = 1.0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml31(td)
+msgid ""
+"(FloatOpt) This will compare the allocated to available space on the volume "
+"destination. If the ratio exceeds this number, the destination will no "
+"longer be valid."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml34(td)
+msgid "nfs_shares_config = /etc/cinder/nfs_shares"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml35(td)
+#: ./doc/common/tables/cinder-nexenta_nfs.xml31(td)
+msgid "(StrOpt) File with the list of available nfs shares"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml38(td)
+msgid "nfs_sparsed_volumes = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml39(td)
+#: ./doc/common/tables/cinder-storage_glusterfs.xml35(td)
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml63(td)
+msgid ""
+"(BoolOpt) Create volumes as sparsed files which take no space.If set to "
+"False volume is created as regular file.In such case volume creation takes a"
+" lot of time."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml42(td)
+msgid "nfs_used_ratio = 0.95"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_nfs.xml43(td)
+msgid ""
+"(FloatOpt) Percent of ACTUAL usage of the underlying volume before no new "
+"volumes can be allocated to the volume destination."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml26(td)
+msgid "heat_stack_user_role = heat_stack_user"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml27(td)
+msgid "(StrOpt) Keystone role for heat template-defined users."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml34(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml22(td)
+msgid "heat_watch_server_url ="
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml35(td)
+#: ./doc/common/tables/heat-cloudwatch_api.xml23(td)
+msgid "(StrOpt) URL of the Heat CloudWatch server."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml38(td)
+msgid "max_json_body_size = 1048576"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml39(td)
+msgid ""
+"(IntOpt) Maximum raw byte size of JSON request body. Should be larger than "
+"max_template_size."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml50(td)
+msgid "secure_proxy_ssl_header = X-Forwarded-Proto"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml51(td)
+msgid ""
+"(StrOpt) The HTTP Header that will be used to determine which the original "
+"request protocol scheme was, even if it was removed by an SSL terminator "
+"proxy."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml54(td)
+msgid "stack_action_timeout = 3600"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml55(td)
+msgid "(IntOpt) Timeout in seconds for stack action (ie. create or update)."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml58(td)
+msgid "stack_domain_admin = None"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml59(td)
+msgid ""
+"(StrOpt) Keystone username, a user with roles sufficient to manage users and"
+" projects in the stack_user_domain."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml62(td)
+msgid "stack_domain_admin_password = None"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml63(td)
+msgid "(StrOpt) Keystone password for stack_domain_admin user."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml66(td)
+msgid "stack_user_domain = None"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml67(td)
+msgid ""
+"(StrOpt) Keystone domain ID which contains heat template-defined users."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml70(td)
+msgid "trusts_delegated_roles = heat_stack_owner"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml71(td)
+msgid "(ListOpt) Subset of trustor roles to be delegated to heat."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml74(th)
+msgid "[auth_password]"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml77(td)
+#: ./doc/common/tables/heat-api.xml88(td)
+msgid "allowed_auth_uris ="
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml78(td)
+#: ./doc/common/tables/heat-api.xml89(td)
+msgid ""
+"(ListOpt) Allowed keystone endpoints for auth_uri when multi_cloud is "
+"enabled. At least one endpoint needs to be specified."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml81(td)
+#: ./doc/common/tables/heat-api.xml96(td)
+msgid "multi_cloud = False"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml82(td)
+#: ./doc/common/tables/heat-api.xml97(td)
+msgid "(BoolOpt) Allow orchestration of multiple clouds."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml85(th)
+msgid "[ec2authtoken]"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml93(td)
+msgid "(StrOpt) Authentication Endpoint URI."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml100(th)
+msgid "[heat_api]"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml111(td)
+msgid "bind_port = 8004"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml135(td)
+msgid "(StrOpt) The API paste config file to use."
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml138(td)
+#: ./doc/common/tables/glance-paste.xml26(td)
+msgid "flavor = None"
+msgstr ""
+
+#: ./doc/common/tables/heat-api.xml139(td)
+msgid "(StrOpt) The flavor to use."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml7(literal)
+msgid "[filter:tempurl]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml18(td)
+msgid "use = egg:swift#tempurl"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml21(td)
+msgid "methods = GET HEAD PUT"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml21(td)
+msgid "HTTP methods allowed with Temporary URLs"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml24(td)
+msgid "incoming_remove_headers = x-timestamp"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml24(td)
+msgid ""
+"Headers to remove from incoming requests. Simply a whitespace delimited list"
+" of header names and names can optionally end with '*' to indicate a prefix "
+"match."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml28(td)
+msgid "incoming_allow_headers ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml28(td)
+msgid ""
+"Headers allowed as exceptions to incoming_remove_headers. Simply a "
+"whitespace delimited list of header names and names can optionally end with "
+"'*' to indicate a prefix match."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml33(td)
+msgid "outgoing_remove_headers = x-object-meta-*"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml33(td)
+msgid ""
+"Headers to remove from outgoing responses. Simply a whitespace delimited "
+"list of header names and names can optionally end with '*' to indicate a "
+"prefix match."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml38(td)
+msgid "outgoing_allow_headers = x-object-meta-public-*"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-tempurl.xml38(td)
+msgid ""
+"Headers allowed as exceptions to outgoing_allow_headers. Simply a whitespace"
+" delimited list of header names and names can optionally end with '*' to "
+"indicate a prefix match."
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_ceilometer.xml8(caption)
+msgid "Description of configuration options for clients_ceilometer"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_ceilometer.xml19(th)
+msgid "[clients_ceilometer]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml8(caption)
+msgid "Description of configuration options for ryu"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml22(td)
+msgid "openflow_rest_api = 127.0.0.1:8080"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml23(td)
+msgid "(StrOpt) OpenFlow REST API location"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml26(td)
+msgid "ovsdb_interface = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml27(td)
+msgid "(StrOpt) OVSDB interface to connect to"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml30(td)
+msgid "ovsdb_ip = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml31(td)
+msgid "(StrOpt) OVSDB IP to connect to"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml34(td)
+msgid "ovsdb_port = 6634"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml35(td)
+msgid "(IntOpt) OVSDB port to connect to"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml38(td)
+msgid "tunnel_interface = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml39(td)
+msgid "(StrOpt) Tunnel interface to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml42(td)
+msgid "tunnel_ip = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml43(td)
+msgid "(StrOpt) Tunnel IP to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml46(td)
+msgid "tunnel_key_max = 16777215"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml47(td)
+msgid "(IntOpt) Maximum tunnel ID to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml50(td)
+msgid "tunnel_key_min = 1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ryu.xml51(td)
+msgid "(IntOpt) Minimum tunnel ID to use"
+msgstr ""
+
+#: ./doc/common/tables/swift-rsyncd-account.xml7(literal)
+msgid "[account]"
+msgstr ""
+
+#: ./doc/common/tables/swift-rsyncd-account.xml18(td)
+msgid "max connections = 2"
+msgstr ""
+
+#: ./doc/common/tables/swift-rsyncd-account.xml27(td)
+msgid "lock file = /var/lock/account.lock"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metering_agent.xml8(caption)
+msgid "Description of configuration options for metering_agent"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metering_agent.xml22(td)
+msgid ""
+"driver = "
+"neutron.services.metering.drivers.noop.noop_driver.NoopMeteringDriver"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metering_agent.xml23(td)
+msgid "(StrOpt) Metering driver"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metering_agent.xml26(td)
+msgid "measure_interval = 30"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metering_agent.xml27(td)
+msgid "(IntOpt) Interval between two metering measures"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metering_agent.xml33(td)
+msgid "report_interval = 30"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metering_agent.xml34(td)
+msgid ""
+"(FloatOpt) Seconds between nodes reporting state to server; should be less "
+"than agent_down_time, best if it is half or less than agent_down_time."
+msgstr ""
+
+#: ./doc/common/tables/neutron-zeromq.xml38(td)
+msgid ""
+"rpc_zmq_matchmaker = "
+"neutron.openstack.common.rpc.matchmaker.MatchMakerLocalhost"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_glusterfs.xml8(caption)
+msgid "Description of configuration options for storage_glusterfs"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_glusterfs.xml23(td)
+msgid "(StrOpt) Base dir containing mount points for gluster shares."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_glusterfs.xml26(td)
+msgid "glusterfs_qcow2_volumes = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_glusterfs.xml27(td)
+msgid "(BoolOpt) Create volumes as QCOW2 files rather than raw files."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_glusterfs.xml30(td)
+msgid "glusterfs_shares_config = /etc/cinder/glusterfs_shares"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_glusterfs.xml31(td)
+msgid "(StrOpt) File with the list of available gluster shares"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_glusterfs.xml34(td)
+msgid "glusterfs_sparsed_volumes = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml22(td)
+msgid "compute_api_class = cinder.compute.nova.API"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml23(td)
+msgid "(StrOpt) The full class name of the compute API class to use"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml30(td)
+msgid "default_availability_zone = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml31(td)
+msgid ""
+"(StrOpt) default availability zone to use when creating a new volume. If "
+"this is not set then we use the value from the storage_availability_zone "
+"option as the default availability_zone for new volumes."
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml34(td)
+msgid ""
+"default_log_levels = amqp=WARN, amqplib=WARN, boto=WARN, qpid=WARN, "
+"sqlalchemy=WARN, suds=INFO, oslo.messaging=INFO, iso8601=WARN, "
+"requests.packages.urllib3.connectionpool=WARN"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml38(td)
+msgid "default_volume_type = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml39(td)
+msgid "(StrOpt) default volume type to use"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml46(td)
+#: ./doc/common/tables/nova-api.xml26(td)
+msgid "enable_new_services = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml47(td)
+#: ./doc/common/tables/nova-api.xml27(td)
+msgid "(BoolOpt) Services to be added to the available pool on create"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml54(td)
+#: ./doc/common/tables/nova-logging.xml34(td)
+msgid "fatal_exception_format_errors = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml55(td)
+msgid "(BoolOpt) make exception message format errors fatal"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml59(td)
+msgid ""
+"(StrOpt) Name of this node. This can be an opaque identifier. It is not "
+"necessarily a hostname, FQDN, or IP address."
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml62(td)
+msgid "iet_conf = /etc/iet/ietd.conf"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml63(td)
+msgid "(StrOpt) IET configuration file"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml66(td)
+msgid "lio_initiator_iqns ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml67(td)
+msgid ""
+"(StrOpt) Comma-separated list of initiator IQNs allowed to connect to the "
+"iSCSI target. (From Nova compute nodes.)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml71(td)
+msgid "(StrOpt) Directory to use for lock files. Default to a temp directory"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml111(td)
+msgid "(BoolOpt) Enable monkey patching"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml114(td)
+msgid "monkey_patch_modules ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml119(td)
+msgid "(StrOpt) ip address of this host"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml122(td)
+msgid "no_snapshot_gb_quota = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml123(td)
+msgid "(BoolOpt) Whether snapshots count against GigaByte quota"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml126(td)
+msgid "num_shell_tries = 3"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml127(td)
+msgid "(IntOpt) number of times to attempt to run flakey shell commands"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml131(td)
+msgid ""
+"(IntOpt) range of seconds to randomly delay when starting the periodic task "
+"scheduler to reduce stampeding. (Disable by setting to 0)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml135(td)
+msgid "(IntOpt) seconds between running periodic tasks"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml147(td)
+msgid "(IntOpt) seconds between nodes reporting state to datastore"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml150(td)
+msgid "reserved_percentage = 0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml151(td)
+msgid "(IntOpt) The percentage of backend capacity is reserved"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml154(td)
+msgid "rootwrap_config = /etc/cinder/rootwrap.conf"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml163(td)
+msgid "(IntOpt) maximum time since last check-in for up service"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml166(td)
+msgid "sqlite_db = cinder.sqlite"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml167(td)
+#: ./doc/common/tables/heat-database.xml27(td)
+msgid "(StrOpt) the filename to use with sqlite"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml171(td)
+#: ./doc/common/tables/heat-database.xml31(td)
+msgid "(BoolOpt) If true, use synchronous mode for sqlite"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml174(td)
+#: ./doc/common/tables/neutron-ssl.xml22(td)
+#: ./doc/common/tables/nova-wsgi.xml26(td)
+msgid "ssl_ca_file = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml178(td)
+#: ./doc/common/tables/neutron-ssl.xml26(td)
+#: ./doc/common/tables/nova-wsgi.xml30(td)
+msgid "ssl_cert_file = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml182(td)
+#: ./doc/common/tables/neutron-ssl.xml30(td)
+#: ./doc/common/tables/nova-wsgi.xml34(td)
+msgid "ssl_key_file = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml186(td)
+msgid "state_path = /var/lib/cinder"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml187(td)
+msgid "(StrOpt) Top-level directory for maintaining cinder's state"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml190(td)
+msgid "storage_availability_zone = nova"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml191(td)
+msgid "(StrOpt) availability zone of this node"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml203(td)
+msgid "(IntOpt) count of reservations until usage is refreshed"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml206(td)
+#: ./doc/common/tables/nova-api.xml94(td)
+msgid "use_forwarded_for = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml207(td)
+#: ./doc/common/tables/nova-api.xml95(td)
+msgid ""
+"(BoolOpt) Treat X-Forwarded-For as the canonical remote address. Only enable"
+" this if you have a sanitizing proxy."
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml230(td)
+#: ./doc/common/tables/heat-database.xml54(td)
+msgid "(IntOpt) timeout before idle sql connections are reaped"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml234(td)
+#: ./doc/common/tables/heat-database.xml78(td)
+msgid "(IntOpt) interval between retries of opening a sql connection"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml237(td)
+msgid "use_tpool = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-common.xml238(td)
+msgid ""
+"(BoolOpt) Enable the experimental use of thread pooling for all DB API calls"
+msgstr ""
+
+#: ./doc/common/tables/glance-swift.xml8(caption)
+#: ./doc/common/tables/ceilometer-swift.xml8(caption)
+#: ./doc/common/tables/trove-swift.xml8(caption)
+msgid "Description of configuration options for swift"
 msgstr ""
 
 #: ./doc/common/tables/glance-swift.xml22(td)
@@ -38814,215 +40352,3558 @@ msgid ""
 "(StrOpt) The user to authenticate against the Swift authentication service."
 msgstr ""
 
-#: ./doc/common/tables/swift-account-server-DEFAULT.xml21(td)
-msgid "bind_port = 6002"
+#: ./doc/common/tables/trove-quota.xml22(td)
+msgid "max_accepted_volume_size = 5"
+msgstr ""
+
+#: ./doc/common/tables/trove-quota.xml23(td)
+msgid "(IntOpt) Default maximum volume size for an instance."
+msgstr ""
+
+#: ./doc/common/tables/trove-quota.xml26(td)
+msgid "max_backups_per_user = 50"
+msgstr ""
+
+#: ./doc/common/tables/trove-quota.xml27(td)
+msgid "(IntOpt) Default maximum number of backups created by a tenant."
+msgstr ""
+
+#: ./doc/common/tables/trove-quota.xml30(td)
+msgid "max_instances_per_user = 5"
+msgstr ""
+
+#: ./doc/common/tables/trove-quota.xml31(td)
+msgid "(IntOpt) Default maximum number of instances per tenant."
+msgstr ""
+
+#: ./doc/common/tables/trove-quota.xml34(td)
+msgid "max_volumes_per_user = 20"
+msgstr ""
+
+#: ./doc/common/tables/trove-quota.xml35(td)
+msgid ""
+"(IntOpt) Default maximum volume capacity (in GB) spanning across all trove "
+"volumes per tenant"
+msgstr ""
+
+#: ./doc/common/tables/trove-quota.xml38(td)
+msgid "quota_driver = trove.quota.quota.DbQuotaDriver"
+msgstr ""
+
+#: ./doc/common/tables/trove-quota.xml39(td)
+msgid "(StrOpt) Default driver to use for quota checks."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml8(caption)
+msgid "Description of configuration options for alarm"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml19(th)
+msgid "[alarm]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml22(td)
+msgid "evaluation_interval = 60"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml23(td)
+msgid ""
+"(IntOpt) Period of evaluation cycle, should be &gt;= than configured "
+"pipeline interval for collection of underlying metrics."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml26(td)
+msgid "evaluation_service = ceilometer.alarm.service.SingletonAlarmService"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml27(td)
+msgid "(StrOpt) Class to launch as alarm evaluation service."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml30(td)
+msgid "notifier_rpc_topic = alarm_notifier"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml31(td)
+msgid "(StrOpt) The topic that ceilometer uses for alarm notifier messages."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml34(td)
+msgid "partition_rpc_topic = alarm_partition_coordination"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml35(td)
+msgid ""
+"(StrOpt) The topic that ceilometer uses for alarm partition coordination "
+"messages."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml38(td)
+msgid "record_history = True"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml39(td)
+msgid "(BoolOpt) Record alarm change events."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml42(td)
+msgid "rest_notifier_certificate_file ="
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml43(td)
+msgid "(StrOpt) SSL Client certificate for REST notifier."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml46(td)
+msgid "rest_notifier_certificate_key ="
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml47(td)
+msgid "(StrOpt) SSL Client private key for REST notifier."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml50(td)
+msgid "rest_notifier_ssl_verify = True"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-alarm.xml51(td)
+msgid ""
+"(BoolOpt) Whether to verify the SSL Server certificate when calling alarm "
+"action."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml8(caption)
+msgid "Description of configuration options for events"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml19(th)
+msgid "[event]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml22(td)
+msgid "definitions_cfg_file = event_definitions.yaml"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml23(td)
+msgid "(StrOpt) Configuration file for event definitions."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml26(td)
+msgid "drop_unmatched_notifications = False"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml27(td)
+msgid ""
+"(BoolOpt) Drop notifications if no event definition matches. (Otherwise, we "
+"convert them with just the default traits)"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml30(th)
+msgid "[notification]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml33(td)
+msgid "ack_on_event_error = True"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml34(td)
+msgid "(BoolOpt) Acknowledge message when event persistence fails."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml37(td)
+msgid "store_events = False"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-events.xml38(td)
+msgid "(BoolOpt) Save event details."
+msgstr ""
+
+#: ./doc/common/tables/cinder-xiv.xml8(caption)
+msgid "Description of configuration options for xiv"
+msgstr ""
+
+#: ./doc/common/tables/cinder-xiv.xml22(td)
+msgid "xiv_chap = disabled"
+msgstr ""
+
+#: ./doc/common/tables/cinder-xiv.xml23(td)
+msgid ""
+"(StrOpt) CHAP authentication mode, effective only for iscsi "
+"(disabled|enabled)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-xiv.xml26(td)
+msgid "xiv_ds8k_connection_type = iscsi"
+msgstr ""
+
+#: ./doc/common/tables/cinder-xiv.xml27(td)
+msgid ""
+"(StrOpt) Connection type to the IBM Storage Array (fibre_channel|iscsi)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-xiv.xml30(td)
+msgid "xiv_ds8k_proxy = xiv_ds8k_openstack.nova_proxy.XIVDS8KNovaProxy"
+msgstr ""
+
+#: ./doc/common/tables/cinder-xiv.xml31(td)
+msgid "(StrOpt) Proxy driver that connects to the IBM Storage Array"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml7(literal)
+msgid "[filter:name_check]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml18(td)
+msgid "use = egg:swift#name_check"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml21(td)
+msgid "forbidden_chars = '\"`&lt;&gt;"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml21(td)
+msgid "Characters that are not allowed in a name"
+msgstr "名前において許可されない文字"
+
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml24(td)
+msgid "maximum_length = 255"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml24(td)
+msgid "Maximum length of a name"
+msgstr "名前の最大長"
+
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml27(td)
+msgid "forbidden_regexp = /\\./|/\\.\\./|/\\.$|/\\.\\.$"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-name_check.xml27(td)
+msgid "Substrings to forbid, using regular expression syntax"
+msgstr "禁止されている部分文字列、正規表現構文の使用"
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml8(caption)
+msgid "Description of configuration options for ml2_bigswitch"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml19(th)
+#: ./doc/common/tables/neutron-bigswitch.xml19(th)
+msgid "[NOVA]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml22(td)
+#: ./doc/common/tables/neutron-bigswitch.xml22(td)
+msgid "node_override_vif_802.1qbg ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml23(td)
+#: ./doc/common/tables/neutron-bigswitch.xml23(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to 802.1qbg"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml26(td)
+#: ./doc/common/tables/neutron-bigswitch.xml26(td)
+msgid "node_override_vif_802.1qbh ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml27(td)
+#: ./doc/common/tables/neutron-bigswitch.xml27(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to 802.1qbh"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml30(td)
+#: ./doc/common/tables/neutron-bigswitch.xml30(td)
+msgid "node_override_vif_binding_failed ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml31(td)
+#: ./doc/common/tables/neutron-bigswitch.xml31(td)
+msgid ""
+"(ListOpt) Nova compute nodes to manually set VIF type to binding_failed"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml34(td)
+#: ./doc/common/tables/neutron-bigswitch.xml34(td)
+msgid "node_override_vif_bridge ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml35(td)
+#: ./doc/common/tables/neutron-bigswitch.xml35(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to bridge"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml38(td)
+#: ./doc/common/tables/neutron-bigswitch.xml38(td)
+msgid "node_override_vif_hostdev ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml39(td)
+#: ./doc/common/tables/neutron-bigswitch.xml39(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to hostdev"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml42(td)
+#: ./doc/common/tables/neutron-bigswitch.xml42(td)
+msgid "node_override_vif_hyperv ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml43(td)
+#: ./doc/common/tables/neutron-bigswitch.xml43(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to hyperv"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml46(td)
+#: ./doc/common/tables/neutron-bigswitch.xml46(td)
+msgid "node_override_vif_ivs ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml47(td)
+#: ./doc/common/tables/neutron-bigswitch.xml47(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to ivs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml50(td)
+#: ./doc/common/tables/neutron-bigswitch.xml50(td)
+msgid "node_override_vif_midonet ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml51(td)
+#: ./doc/common/tables/neutron-bigswitch.xml51(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to midonet"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml54(td)
+#: ./doc/common/tables/neutron-bigswitch.xml54(td)
+msgid "node_override_vif_mlnx_direct ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml55(td)
+#: ./doc/common/tables/neutron-bigswitch.xml55(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to mlnx_direct"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml58(td)
+#: ./doc/common/tables/neutron-bigswitch.xml58(td)
+msgid "node_override_vif_other ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml59(td)
+#: ./doc/common/tables/neutron-bigswitch.xml59(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to other"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml62(td)
+#: ./doc/common/tables/neutron-bigswitch.xml62(td)
+msgid "node_override_vif_ovs ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml63(td)
+#: ./doc/common/tables/neutron-bigswitch.xml63(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to ovs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml66(td)
+#: ./doc/common/tables/neutron-bigswitch.xml66(td)
+msgid "node_override_vif_unbound ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml67(td)
+#: ./doc/common/tables/neutron-bigswitch.xml67(td)
+msgid "(ListOpt) Nova compute nodes to manually set VIF type to unbound"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml70(td)
+#: ./doc/common/tables/neutron-bigswitch.xml70(td)
+msgid "vif_type = ovs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml71(td)
+#: ./doc/common/tables/neutron-bigswitch.xml71(td)
+msgid "(StrOpt) Virtual interface type to configure on Nova compute nodes"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml74(td)
+#: ./doc/common/tables/neutron-bigswitch.xml74(td)
+msgid ""
+"vif_types = unbound, binding_failed, ovs, ivs, bridge, 802.1qbg, 802.1qbh, "
+"hyperv, midonet, mlnx_direct, hostdev, other"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml75(td)
+#: ./doc/common/tables/neutron-bigswitch.xml75(td)
+msgid "(ListOpt) List of allowed vif_type values."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml78(th)
+#: ./doc/common/tables/neutron-nuage.xml19(th)
+#: ./doc/common/tables/neutron-bigswitch.xml78(th)
+msgid "[RESTPROXY]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml81(td)
+#: ./doc/common/tables/neutron-bigswitch.xml81(td)
+msgid "add_meta_server_route = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml82(td)
+#: ./doc/common/tables/neutron-bigswitch.xml82(td)
+msgid ""
+"(BoolOpt) Flag to decide if a route to the metadata server should be "
+"injected into the VM"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml85(td)
+#: ./doc/common/tables/neutron-bigswitch.xml85(td)
+msgid "auto_sync_on_failure = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml86(td)
+#: ./doc/common/tables/neutron-bigswitch.xml86(td)
+msgid ""
+"(BoolOpt) If neutron fails to create a resource because the backend "
+"controller doesn't know of a dependency, the plugin automatically triggers a"
+" full data synchronization to the controller."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml89(td)
+#: ./doc/common/tables/neutron-bigswitch.xml89(td)
+msgid "cache_connections = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml90(td)
+#: ./doc/common/tables/neutron-bigswitch.xml90(td)
+msgid "(BoolOpt) Re-use HTTP/HTTPS connections to the controller."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml93(td)
+#: ./doc/common/tables/neutron-bigswitch.xml93(td)
+msgid "consistency_interval = 60"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml94(td)
+#: ./doc/common/tables/neutron-bigswitch.xml94(td)
+msgid ""
+"(IntOpt) Time between verifications that the backend controller database is "
+"consistent with Neutron"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml97(td)
+#: ./doc/common/tables/neutron-bigswitch.xml97(td)
+msgid "neutron_id = neutron-oslo"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml98(td)
+#: ./doc/common/tables/neutron-bigswitch.xml98(td)
+msgid "(StrOpt) User defined identifier for this Neutron deployment"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml101(td)
+#: ./doc/common/tables/neutron-bigswitch.xml101(td)
+msgid "no_ssl_validation = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml102(td)
+#: ./doc/common/tables/neutron-bigswitch.xml102(td)
+msgid "(BoolOpt) Disables SSL certificate validation for controllers"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml105(td)
+#: ./doc/common/tables/neutron-bigswitch.xml105(td)
+msgid "server_auth = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml106(td)
+#: ./doc/common/tables/neutron-bigswitch.xml106(td)
+msgid ""
+"(StrOpt) The username and password for authenticating against the Big Switch"
+" or Floodlight controller."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml109(td)
+#: ./doc/common/tables/neutron-bigswitch.xml109(td)
+msgid "server_ssl = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml110(td)
+#: ./doc/common/tables/neutron-bigswitch.xml110(td)
+msgid ""
+"(BoolOpt) If True, Use SSL when connecting to the Big Switch or Floodlight "
+"controller."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml113(td)
+#: ./doc/common/tables/neutron-bigswitch.xml113(td)
+msgid "server_timeout = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml114(td)
+#: ./doc/common/tables/neutron-bigswitch.xml114(td)
+msgid ""
+"(IntOpt) Maximum number of seconds to wait for proxy request to connect and "
+"complete."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml117(td)
+#: ./doc/common/tables/neutron-bigswitch.xml117(td)
+msgid "servers = localhost:8800"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml118(td)
+#: ./doc/common/tables/neutron-bigswitch.xml118(td)
+msgid ""
+"(ListOpt) A comma separated list of Big Switch or Floodlight servers and "
+"port numbers. The plugin proxies the requests to the Big Switch/Floodlight "
+"server, which performs the networking configuration. Only oneserver is "
+"needed per deployment, but you may wish todeploy multiple servers to support"
+" failover."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml121(td)
+#: ./doc/common/tables/neutron-bigswitch.xml121(td)
+msgid "ssl_cert_directory = /etc/neutron/plugins/bigswitch/ssl"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml122(td)
+#: ./doc/common/tables/neutron-bigswitch.xml122(td)
+msgid ""
+"(StrOpt) Directory containing ca_certs and host_certs certificate "
+"directories."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml125(td)
+#: ./doc/common/tables/neutron-bigswitch.xml125(td)
+msgid "ssl_sticky = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml126(td)
+#: ./doc/common/tables/neutron-bigswitch.xml126(td)
+msgid ""
+"(BoolOpt) Trust and store the first certificate received for each controller"
+" address and use it to validate future connections to that address."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml129(td)
+#: ./doc/common/tables/neutron-bigswitch.xml129(td)
+msgid "sync_data = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml130(td)
+#: ./doc/common/tables/neutron-bigswitch.xml130(td)
+msgid "(BoolOpt) Sync data on connect"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml133(td)
+#: ./doc/common/tables/neutron-bigswitch.xml133(td)
+msgid "thread_pool_size = 4"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml134(td)
+#: ./doc/common/tables/neutron-bigswitch.xml134(td)
+msgid ""
+"(IntOpt) Maximum number of threads to spawn to handle large volumes of port "
+"creations."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml137(th)
+#: ./doc/common/tables/neutron-bigswitch.xml137(th)
+msgid "[RESTPROXYAGENT]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml141(td)
+#: ./doc/common/tables/neutron-bigswitch.xml141(td)
+msgid ""
+"(StrOpt) Name of integration bridge on compute nodes used for security group"
+" insertion."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml144(td)
+#: ./doc/common/tables/neutron-bigswitch.xml144(td)
+msgid "polling_interval = 5"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml145(td)
+#: ./doc/common/tables/neutron-bigswitch.xml145(td)
+msgid "(IntOpt) Seconds between agent checks for port changes"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml148(td)
+#: ./doc/common/tables/neutron-bigswitch.xml148(td)
+msgid "virtual_switch_type = ovs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml149(td)
+#: ./doc/common/tables/neutron-bigswitch.xml149(td)
+msgid "(StrOpt) Virtual switch type."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml152(th)
+#: ./doc/common/tables/neutron-bigswitch.xml152(th)
+msgid "[ROUTER]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml155(td)
+#: ./doc/common/tables/neutron-bigswitch.xml155(td)
+msgid "max_router_rules = 200"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml156(td)
+#: ./doc/common/tables/neutron-bigswitch.xml156(td)
+msgid "(IntOpt) Maximum number of router rules"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml159(td)
+#: ./doc/common/tables/neutron-bigswitch.xml159(td)
+msgid "tenant_default_router_rule = ['*:any:any:permit']"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_bigswitch.xml160(td)
+#: ./doc/common/tables/neutron-bigswitch.xml160(td)
+msgid ""
+"(MultiStrOpt) The default router rules installed in new tenant routers. "
+"Repeat the config option for each rule. Format is "
+"&lt;tenant&gt;:&lt;source&gt;:&lt;destination&gt;:&lt;action&gt; Use an * to"
+" specify default for all tenants."
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml8(caption)
+msgid "Description of configuration options for glance"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml22(td)
+#: ./doc/common/tables/cinder-images.xml22(td)
+msgid "allowed_direct_url_schemes ="
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml23(td)
+msgid ""
+"(ListOpt) A list of url scheme that can be downloaded directly via the "
+"direct_url. Currently supported schemes: [file]."
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml26(td)
+#: ./doc/common/tables/cinder-images.xml26(td)
+msgid "glance_api_insecure = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml27(td)
+#: ./doc/common/tables/cinder-images.xml27(td)
+msgid "(BoolOpt) Allow to perform insecure SSL (https) requests to glance"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml30(td)
+#: ./doc/common/tables/cinder-images.xml30(td)
+msgid "glance_api_servers = $glance_host:$glance_port"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml31(td)
+msgid ""
+"(ListOpt) A list of the glance api servers available to nova. Prefix with "
+"https:// for ssl-based glance api servers. ([hostname|ip]:port)"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml34(td)
+#: ./doc/common/tables/cinder-images.xml42(td)
+msgid "glance_host = $my_ip"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml35(td)
+msgid "(StrOpt) Default glance hostname or IP address"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml38(td)
+#: ./doc/common/tables/cinder-images.xml46(td)
+msgid "glance_num_retries = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml39(td)
+msgid "(IntOpt) Number of retries when downloading an image from glance"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml42(td)
+#: ./doc/common/tables/cinder-images.xml50(td)
+msgid "glance_port = 9292"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml43(td)
+msgid "(IntOpt) Default glance port"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml46(td)
+msgid "glance_protocol = http"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml47(td)
+msgid ""
+"(StrOpt) Default protocol to use when connecting to glance. Set to https for"
+" SSL."
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml50(td)
+msgid "osapi_glance_link_prefix = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml51(td)
+msgid ""
+"(StrOpt) Base URL that will be presented to users in links to glance "
+"resources"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml54(th)
+msgid "[image_file_url]"
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml57(td)
+msgid "filesystems ="
+msgstr ""
+
+#: ./doc/common/tables/nova-glance.xml58(td)
+msgid ""
+"(ListOpt) List of file systems that are configured in this file in the "
+"image_file_url:&lt;list entry name&gt; sections"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml22(td)
+msgid "buckets_path = $state_path/buckets"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml23(td)
+msgid "(StrOpt) Path to S3 buckets"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml26(td)
+msgid "image_decryption_dir = /tmp"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml27(td)
+msgid "(StrOpt) Parent directory for tempdir used for image decryption"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml30(td)
+msgid "s3_access_key = notchecked"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml31(td)
+msgid "(StrOpt) Access key to use for S3 server for images"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml34(td)
+msgid "s3_affix_tenant = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml35(td)
+msgid ""
+"(BoolOpt) Whether to affix the tenant id to the access key when downloading "
+"from S3"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml38(td)
+msgid "s3_host = $my_ip"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml39(td)
+msgid "(StrOpt) Hostname or IP for OpenStack to use when accessing the S3 api"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml42(td)
+msgid "s3_listen = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml43(td)
+msgid "(StrOpt) IP address for S3 API to listen"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml46(td)
+msgid "s3_listen_port = 3333"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml47(td)
+msgid "(IntOpt) Port for S3 API to listen"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml50(td)
+msgid "s3_port = 3333"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml51(td)
+msgid "(IntOpt) Port used when accessing the S3 api"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml54(td)
+msgid "s3_secret_key = notchecked"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml55(td)
+msgid "(StrOpt) Secret key to use for S3 server for images"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml58(td)
+msgid "s3_use_ssl = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-s3.xml59(td)
+msgid "(BoolOpt) Whether to use SSL when talking to S3"
+msgstr ""
+
+#: ./doc/common/tables/nova-pci.xml8(caption)
+msgid "Description of configuration options for pci"
+msgstr ""
+
+#: ./doc/common/tables/nova-pci.xml22(td)
+msgid "pci_alias = []"
+msgstr ""
+
+#: ./doc/common/tables/nova-pci.xml23(td)
+msgid ""
+"(MultiStrOpt) An alias for a PCI passthrough device requirement. This allows"
+" users to specify the alias in the extra_spec for a flavor, without needing "
+"to repeat all the PCI property requirements. For example: pci_alias = { "
+"\"name\": \"QuicAssist\", \"product_id\": \"0443\", \"vendor_id\": \"8086\","
+" \"device_type\": \"ACCEL\" } defines an alias for the Intel QuickAssist "
+"card. (multi valued)"
+msgstr ""
+
+#: ./doc/common/tables/nova-pci.xml26(td)
+msgid "pci_passthrough_whitelist = []"
+msgstr ""
+
+#: ./doc/common/tables/nova-pci.xml27(td)
+msgid ""
+"(MultiStrOpt) White list of PCI devices available to VMs. For example: "
+"pci_passthrough_whitelist = [{\"vendor_id\": \"8086\", \"product_id\": "
+"\"0443\"}]"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_cinder.xml8(caption)
+msgid "Description of configuration options for clients_cinder"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_cinder.xml19(th)
+msgid "[clients_cinder]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml7(literal)
+msgid "[filter:ratelimit]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml18(td)
+msgid "use = egg:swift#ratelimit"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml21(td)
+msgid "set log_name = ratelimit"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml36(td)
+msgid "clock_accuracy = 1000"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml36(td)
+msgid ""
+"Represents how accurate the proxy servers' system clocks are with each "
+"other. 1000 means that all the proxies' clock are accurate to each other "
+"within 1 millisecond. No ratelimit should be higher than the clock accuracy."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml39(td)
+msgid "max_sleep_time_seconds = 60"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml39(td)
+msgid ""
+"App will immediately return a 498 response if the necessary sleep time ever "
+"exceeds the given max_sleep_time_seconds."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml42(td)
+msgid "log_sleep_time_seconds = 0"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml42(td)
+msgid ""
+"To allow visibility into rate limiting set this value &gt; 0 and all sleeps "
+"greater than the number will be logged."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml45(td)
+msgid "rate_buffer_seconds = 5"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml45(td)
+msgid ""
+"Number of seconds the rate counter can drop and be allowed to catch up (at a"
+" faster than listed rate). A larger number will result in larger spikes in "
+"rate but better average accuracy."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml48(td)
+msgid "account_ratelimit = 0"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml48(td)
+msgid ""
+"If set, will limit PUT and DELETE requests to /account_name/container_name. "
+"Number is in requests per second."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml51(td)
+msgid "account_whitelist = a,b"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml51(td)
+msgid "Comma separated lists of account names that will not be rate limited."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml54(td)
+msgid "account_blacklist = c,d"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml54(td)
+msgid ""
+"Comma separated lists of account names that will not be allowed. Returns a "
+"497 response. r: for containers of size x, limit requests per second to r. "
+"Will limit PUT, DELETE, and POST requests to /a/c/o. "
+"container_listing_ratelimit_x = r: for containers of size x, limit listing "
+"requests per second to r. Will limit GET requests to /a/c."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml57(td)
+msgid "with container_limit_x = r"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml60(td)
+msgid "container_ratelimit_0 = 100"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml63(td)
+msgid "container_ratelimit_10 = 50"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml66(td)
+msgid "container_ratelimit_50 = 20"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml69(td)
+msgid "container_listing_ratelimit_0 = 100"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml72(td)
+msgid "container_listing_ratelimit_10 = 50"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-ratelimit.xml75(td)
+msgid "container_listing_ratelimit_50 = 20"
+msgstr ""
+
+#: ./doc/common/tables/keystone-revoke.xml8(caption)
+msgid "Description of configuration options for revoke"
+msgstr ""
+
+#: ./doc/common/tables/keystone-revoke.xml19(th)
+msgid "[revoke]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-revoke.xml23(td)
+msgid ""
+"(BoolOpt) Toggle for revocation event cacheing. This has no effect unless "
+"global caching is enabled."
+msgstr ""
+
+#: ./doc/common/tables/keystone-revoke.xml26(td)
+msgid "driver = keystone.contrib.revoke.backends.kvs.Revoke"
+msgstr ""
+
+#: ./doc/common/tables/keystone-revoke.xml27(td)
+msgid ""
+"(StrOpt) An implementation of the backend for persisting revocation events."
+msgstr ""
+
+#: ./doc/common/tables/keystone-revoke.xml30(td)
+msgid "expiration_buffer = 1800"
+msgstr ""
+
+#: ./doc/common/tables/keystone-revoke.xml31(td)
+msgid ""
+"(IntOpt) This value (calculated in seconds) is added to token expiration "
+"before a revocation event may be removed from the backend."
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml23(td)
+msgid "(StrOpt) File name for the paste.deploy config for cinder-api"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml26(td)
+msgid "api_rate_limit = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml27(td)
+msgid "(BoolOpt) whether to rate limit the api"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml35(td)
+msgid "(BoolOpt) Deploy v1 of the Cinder API."
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml39(td)
+msgid "(BoolOpt) Deploy v2 of the Cinder API."
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml42(td)
+msgid "extra_capabilities = {}"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml43(td)
+msgid ""
+"(StrOpt) User defined capabilities, a JSON formatted string specifying "
+"key/value pairs."
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml51(td)
+msgid ""
+"(IntOpt) the maximum number of items returned in a single response from a "
+"collection resource"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml55(td)
+msgid "(IntOpt) Max size for body of a request"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml58(td)
+msgid "osapi_volume_base_URL = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml59(td)
+msgid ""
+"(StrOpt) Base URL that will be presented to users in links to the OpenStack "
+"Volume API"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml62(td)
+msgid "osapi_volume_ext_list ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml63(td)
+msgid ""
+"(ListOpt) Specify list of extensions to load when using "
+"osapi_volume_extension option with cinder.api.contrib.select_extensions"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml66(td)
+msgid "osapi_volume_extension = ['cinder.api.contrib.standard_extensions']"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml67(td)
+msgid "(MultiStrOpt) osapi volume extension to load"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml70(td)
+msgid "osapi_volume_listen = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml71(td)
+msgid "(StrOpt) IP address for OpenStack Volume API to listen"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml74(td)
+msgid "osapi_volume_listen_port = 8776"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml75(td)
+msgid "(IntOpt) port for os volume api to listen"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml78(td)
+msgid "osapi_volume_workers = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml79(td)
+msgid "(IntOpt) Number of workers for OpenStack Volume API service"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml82(td)
+msgid "transfer_api_class = cinder.transfer.api.API"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml83(td)
+msgid "(StrOpt) The full class name of the volume transfer API class"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml86(td)
+msgid "volume_api_class = cinder.volume.api.API"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml90(td)
+msgid "volume_name_template = volume-%s"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml91(td)
+msgid "(StrOpt) Template string to be used to generate volume names"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml94(td)
+msgid "volume_transfer_key_length = 16"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml95(td)
+msgid "(IntOpt) The number of characters in the autogenerated auth key."
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml98(td)
+msgid "volume_transfer_salt_length = 8"
+msgstr ""
+
+#: ./doc/common/tables/cinder-api.xml99(td)
+msgid "(IntOpt) The number of characters in the salt."
+msgstr ""
+
+#: ./doc/common/tables/trove-db_couchbase.xml8(caption)
+msgid "Description of configuration options for db_couchbase"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_couchbase.xml19(th)
+msgid "[couchbase]"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_couchbase.xml26(td)
+msgid "mount_point = /var/lib/couchbase"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_couchbase.xml30(td)
+msgid "tcp_ports = 8091, 8092, 4369, 11209-11211, 21100-21199"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_trove.xml8(caption)
+msgid "Description of configuration options for clients_trove"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_trove.xml19(th)
+msgid "[clients_trove]"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml7(literal)
+msgid "[account-replicator]"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml18(td)
+msgid "log_name = account-replicator"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml30(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml30(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml30(td)
+msgid "vm_test_mode = no"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml30(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml30(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml30(td)
+msgid "Indicates that you are using a VM environment"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml33(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml33(td)
+msgid "per_diff = 1000"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml33(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml33(td)
+msgid "Limit number of items to get per diff"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml36(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml36(td)
+msgid "max_diffs = 100"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml36(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml36(td)
+msgid "Caps how long the replicator spends trying to sync a database per pass"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml39(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml39(td)
+msgid "concurrency = 8"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml42(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml42(td)
+msgid "interval = 30"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml57(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml66(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml51(td)
+msgid "reclaim_age = 604800"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml57(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml66(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml51(td)
+msgid "Time elapsed in seconds before an object can be reclaimed"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml60(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml36(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml54(td)
+msgid "run_pause = 30"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-replicator.xml60(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml36(td)
+#: ./doc/common/tables/swift-container-server-container-replicator.xml54(td)
+msgid "Time in seconds to wait between replication passes"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml8(caption)
+msgid "Description of configuration options for plumgrid"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml19(th)
+msgid "[plumgriddirector]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml22(td)
+msgid "director_server = localhost"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml23(td)
+msgid "(StrOpt) PLUMgrid Director server to connect to"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml26(td)
+msgid "director_server_port = 8080"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml27(td)
+msgid "(StrOpt) PLUMgrid Director server port to connect to"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml30(td)
+#: ./doc/common/tables/neutron-ml2_brocade.xml30(td)
+msgid "password = password"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml31(td)
+msgid "(StrOpt) PLUMgrid Director admin password"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml34(td)
+msgid "servertimeout = 5"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml35(td)
+msgid "(IntOpt) PLUMgrid Director server timeout"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml38(td)
+msgid "username = username"
+msgstr ""
+
+#: ./doc/common/tables/neutron-plumgrid.xml39(td)
+msgid "(StrOpt) PLUMgrid Director admin username"
+msgstr ""
+
+#: ./doc/common/tables/trove-heat.xml8(caption)
+msgid "Description of configuration options for heat"
+msgstr ""
+
+#: ./doc/common/tables/trove-heat.xml22(td)
+msgid "heat_time_out = 60"
+msgstr ""
+
+#: ./doc/common/tables/trove-heat.xml26(td)
+msgid "heat_url = http://localhost:8004/v1"
+msgstr ""
+
+#: ./doc/common/tables/glance-sheepdog.xml8(caption)
+msgid "Description of configuration options for sheepdog"
+msgstr ""
+
+#: ./doc/common/tables/glance-sheepdog.xml22(td)
+msgid "sheepdog_store_address = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/glance-sheepdog.xml23(td)
+msgid "(StrOpt) IP address of sheep daemon."
+msgstr ""
+
+#: ./doc/common/tables/glance-sheepdog.xml26(td)
+msgid "sheepdog_store_chunk_size = 64"
+msgstr ""
+
+#: ./doc/common/tables/glance-sheepdog.xml27(td)
+msgid ""
+"(IntOpt) Images will be chunked into objects of this size (in megabytes). "
+"For best performance, this should be a power of two."
+msgstr ""
+
+#: ./doc/common/tables/glance-sheepdog.xml30(td)
+msgid "sheepdog_store_port = 7000"
+msgstr ""
+
+#: ./doc/common/tables/glance-sheepdog.xml31(td)
+msgid "(IntOpt) Port of sheep daemon."
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml7(literal)
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml7(literal)
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml7(literal)
+msgid "container-sync-realms.conf-sample"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml18(td)
+msgid "mtime_check_interval = 300"
+msgstr ""
+
+#: ./doc/common/tables/cinder-windows.xml8(caption)
+msgid "Description of configuration options for windows"
+msgstr ""
+
+#: ./doc/common/tables/cinder-windows.xml22(td)
+msgid "windows_iscsi_lun_path = C:\\iSCSIVirtualDisks"
+msgstr ""
+
+#: ./doc/common/tables/cinder-windows.xml23(td)
+msgid "(StrOpt) Path to store VHD backed volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san-solaris.xml8(caption)
+msgid "Description of configuration options for san-solaris"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san-solaris.xml22(td)
+msgid "san_zfs_volume_base = rpool/"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san-solaris.xml23(td)
+msgid "(StrOpt) The ZFS path under which to create zvols for volumes."
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml8(caption)
+msgid "Description of configuration options for nuage"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml22(td)
+msgid "auth_resource ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml23(td)
+msgid "(StrOpt) Nuage provided uri for initial authorization to access VSD"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml26(td)
+msgid "base_uri = /"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml27(td)
+msgid "(StrOpt) Nuage provided base uri to reach out to VSD"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml30(td)
+msgid "default_floatingip_quota = 254"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml31(td)
+msgid "(IntOpt) Per Net Partition quota of floating ips"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml34(td)
+msgid "default_net_partition_name = OpenStackDefaultNetPartition"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml35(td)
+msgid ""
+"(StrOpt) Default Network partition in which VSD will orchestrate network "
+"resources using openstack"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml38(td)
+msgid "organization = system"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml39(td)
+msgid ""
+"(StrOpt) Organization name in which VSD will orchestrate network resources "
+"using openstack"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml42(td)
+msgid "server = localhost:8800"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml43(td)
+msgid "(StrOpt) IP Address and Port of Nuage's VSD server"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml46(td)
+msgid "serverauth = username:password"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml47(td)
+msgid "(StrOpt) Username and password for authentication"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml50(td)
+msgid "serverssl = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nuage.xml51(td)
+msgid "(BoolOpt) Boolean for SSL connection with VSD server"
 msgstr ""
 
 #: ./doc/common/tables/neutron-bigswitch.xml8(caption)
 msgid "Description of configuration options for bigswitch"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml8(caption)
-msgid "Description of configuration options for libvirt"
-msgstr ""
-
-#: ./doc/common/tables/nova-libvirt.xml22(td)
-msgid "remove_unused_base_images = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-libvirt.xml23(td)
-msgid "(BoolOpt) Should unused base images be removed?"
-msgstr ""
-
-#: ./doc/common/tables/nova-libvirt.xml26(td)
-msgid "remove_unused_original_minimum_age_seconds = 86400"
-msgstr ""
-
-#: ./doc/common/tables/nova-libvirt.xml27(td)
+#: ./doc/common/tables/ceilometer-rpc.xml22(td)
+#: ./doc/common/tables/trove-rpc.xml22(td)
+#: ./doc/common/tables/heat-rpc.xml22(td)
+#: ./doc/common/tables/neutron-common.xml38(td)
 msgid ""
-"(IntOpt) Unused unresized base images younger than this will not be removed"
+"allowed_rpc_exception_modules = nova.exception, cinder.exception, exceptions"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml33(td)
-msgid "checksum_base_images = False"
+#: ./doc/common/tables/ceilometer-rpc.xml26(td)
+msgid "dispatcher = ['database']"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml34(td)
-msgid "(BoolOpt) Write a checksum for files in _base to disk"
+#: ./doc/common/tables/ceilometer-rpc.xml27(td)
+msgid "(MultiStrOpt) Dispatcher to process data."
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml37(td)
-msgid "checksum_interval_seconds = 3600"
+#: ./doc/common/tables/ceilometer-rpc.xml30(td)
+msgid "rpc_backend = ceilometer.openstack.common.rpc.impl_kombu"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml38(td)
-msgid "(IntOpt) How frequently to checksum base images"
-msgstr ""
-
-#: ./doc/common/tables/nova-libvirt.xml41(td)
-msgid "connection_uri ="
-msgstr ""
-
-#: ./doc/common/tables/nova-libvirt.xml42(td)
+#: ./doc/common/tables/ceilometer-rpc.xml66(td)
 msgid ""
-"(StrOpt) Override the default libvirt URI (which is dependent on virt_type)"
+"rpc_zmq_matchmaker = "
+"ceilometer.openstack.common.rpc.matchmaker.MatchMakerLocalhost"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml45(td)
-msgid "cpu_mode = None"
+#: ./doc/common/tables/ceilometer-rpc.xml78(th)
+msgid "[publisher]"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml46(td)
+#: ./doc/common/tables/ceilometer-rpc.xml81(td)
+msgid "metering_secret = change this or be hacked"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-rpc.xml82(td)
+msgid "(StrOpt) Secret value for signing metering messages."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-rpc.xml85(th)
+msgid "[publisher_rpc]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-rpc.xml88(td)
+msgid "metering_topic = metering"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-rpc.xml89(td)
+msgid "(StrOpt) The topic that ceilometer uses for metering messages."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-rpc.xml96(td)
+#: ./doc/common/tables/heat-rpc.xml69(td)
+msgid "(ListOpt) AMQP topic(s) used for OpenStack notifications"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-updater.xml7(literal)
+msgid "[container-updater]"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-updater.xml18(td)
+msgid "log_name = container-updater"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-updater.xml33(td)
+msgid "concurrency = 4"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-updater.xml42(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml39(td)
+msgid "slowdown = 0.01"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-updater.xml42(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml39(td)
+msgid "Time in seconds to wait between objects"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-updater.xml45(td)
+msgid "account_suppression_time = 60"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-updater.xml45(td)
 msgid ""
-"(StrOpt) Set to \"host-model\" to clone the host CPU feature flags; to "
-"\"host-passthrough\" to use the host CPU model exactly; to \"custom\" to use"
-" a named CPU model; to \"none\" to not set any CPU model. If "
-"virt_type=\"kvm|qemu\", it will default to \"host-model\", otherwise it will"
-" default to \"none\""
+"Seconds to suppress updating an account that has generated an error "
+"(timeout, not yet found, etc.)"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml49(td)
-msgid "cpu_model = None"
+#: ./doc/common/tables/trove-db_mongodb.xml8(caption)
+msgid "Description of configuration options for db_mongodb"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml50(td)
+#: ./doc/common/tables/trove-db_mongodb.xml19(th)
+msgid "[mongodb]"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_mongodb.xml26(td)
+msgid "mount_point = /var/lib/mongodb"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_mongodb.xml30(td)
+msgid "tcp_ports = 2500, 27017"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_mongodb.xml35(td)
 msgid ""
-"(StrOpt) Set to a named libvirt CPU model (see names listed in "
-"/usr/share/libvirt/cpu_map.xml). Only has effect if cpu_mode=\"custom\" and "
-"virt_type=\"kvm|qemu\""
+"(ListOpt) List of UPD ports and/or port ranges to open in the security group"
+" (only applicable if trove_security_groups_support is True)"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml53(td)
-msgid "disk_prefix = None"
+#: ./doc/common/tables/swift-object-server-object-replicator.xml7(literal)
+msgid "[object-replicator]"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml54(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml18(td)
+msgid "log_name = object-replicator"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml33(td)
+msgid "daemonize = on"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml33(td)
+msgid "Whether or not to run replication as a daemon"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml42(td)
+msgid "stats_interval = 300"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml42(td)
+msgid "Interval in seconds between logging replication statistics"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml45(td)
+msgid "sync_method = rsync"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml48(td)
+msgid "rsync_timeout = 900"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml48(td)
+msgid "Max duration (seconds) of a partition rsync"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml51(td)
+msgid "rsync_bwlimit = 0"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml54(td)
+msgid "rsync_io_timeout = 30"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml54(td)
+msgid "Passed to rsync for a max duration (seconds) of an I/O op"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml57(td)
+#: ./doc/common/tables/swift-object-server-object-updater.xml36(td)
+msgid "node_timeout = &lt;whatever's in the DEFAULT section or 10&gt;"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml60(td)
+msgid "http_timeout = 60"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml60(td)
+msgid "Maximum duration for an HTTP request"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml63(td)
+msgid "lockup_timeout = 1800"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml63(td)
 msgid ""
-"(StrOpt) Override the default disk prefix for the devices attached to a "
-"server, which is dependent on virt_type. (valid options are: sd, xvd, uvd, "
-"vd)"
+"Attempts to kill all workers if nothing replications for lockup_timeout "
+"seconds"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml57(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml69(td)
+msgid "ring_check_interval = 15"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml69(td)
+msgid "How often (in seconds) to check the ring"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml75(td)
+msgid "rsync_error_log_line_length = 0"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml78(td)
+msgid "handoffs_first = False"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml78(td)
 msgid ""
-"image_info_filename_pattern = "
-"$instances_path/$image_cache_subdirectory_name/%(image)s.info"
+"If set to True, partitions that are not supposed to be on the node will be "
+"replicated first. The default setting should not be changed, except for "
+"extreme situations."
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml58(td)
+#: ./doc/common/tables/swift-object-server-object-replicator.xml81(td)
+msgid "handoff_delete = auto"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-replicator.xml81(td)
 msgid ""
-"(StrOpt) Allows image information files to be stored in non-standard "
-"locations"
+"By default handoff partitions will be removed when it has successfully "
+"replicated to all the canonical nodes. If set to an integer n, it will "
+"remove the partition if it is successfully replicated to n nodes. The "
+"default setting should not be changed, except for extremem situations. This "
+"uses what's set here, or what's set in the DEFAULT section, or 10 (though "
+"other sections use 3 as the final default)."
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml61(td)
-msgid "remove_unused_kernels = False"
+#: ./doc/common/tables/glance-filesystem.xml8(caption)
+msgid "Description of configuration options for filesystem"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml62(td)
+#: ./doc/common/tables/glance-filesystem.xml22(td)
+msgid "filesystem_store_datadir = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-filesystem.xml23(td)
 msgid ""
-"(BoolOpt) Should unused kernel images be removed? This is only safe to "
-"enable if all compute nodes have been updated to support this option. This "
-"will be enabled by default in future."
+"(StrOpt) Directory to which the Filesystem backend store writes images."
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml65(td)
-msgid "remove_unused_resized_minimum_age_seconds = 3600"
+#: ./doc/common/tables/glance-filesystem.xml26(td)
+msgid "filesystem_store_datadirs = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml66(td)
+#: ./doc/common/tables/glance-filesystem.xml27(td)
 msgid ""
-"(IntOpt) Unused resized base images younger than this will not be removed"
+"(MultiStrOpt) List of directories and its priorities to which the Filesystem"
+" backend store writes images."
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml69(td)
-msgid "rng_dev_path = None"
+#: ./doc/common/tables/glance-filesystem.xml30(td)
+msgid "filesystem_store_metadata_file = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml70(td)
+#: ./doc/common/tables/glance-filesystem.xml31(td)
 msgid ""
-"(StrOpt) A path to a device that will be used as source of entropy on the "
-"host. Permitted options are: /dev/random or /dev/hwrng"
+"(StrOpt) The path to a file which contains the metadata to be returned with "
+"any location associated with this store. The file must contain a valid JSON "
+"dict."
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml73(td)
-msgid "snapshots_directory = $instances_path/snapshots"
+#: ./doc/common/tables/trove-rpc.xml38(td)
+msgid "num_tries = 3"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml74(td)
+#: ./doc/common/tables/trove-rpc.xml47(td)
+msgid "(IntOpt) The interval in seconds which periodic tasks are run."
+msgstr ""
+
+#: ./doc/common/tables/trove-rpc.xml50(td)
+msgid "rpc_backend = trove.openstack.common.rpc.impl_kombu"
+msgstr ""
+
+#: ./doc/common/tables/trove-rpc.xml77(th)
+msgid "[secure_messages]"
+msgstr ""
+
+#: ./doc/common/tables/trove-rpc.xml80(td)
+#: ./doc/common/tables/keystone-trust.xml26(td)
+msgid "enabled = True"
+msgstr ""
+
+#: ./doc/common/tables/trove-rpc.xml81(td)
 msgid ""
-"(StrOpt) Location where libvirt driver will store snapshots before uploading"
-" them to image service"
+"(BoolOpt) Whether Secure Messaging (Signing) is enabled, defaults to enabled"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml77(td)
-msgid "vif_driver = nova.virt.libvirt.vif.LibvirtGenericVIFDriver"
+#: ./doc/common/tables/trove-rpc.xml84(td)
+msgid "encrypt = False"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml78(td)
+#: ./doc/common/tables/trove-rpc.xml85(td)
 msgid ""
-"(StrOpt) DEPRECATED. The libvirt VIF driver to configure the VIFs.This "
-"option is deprecated and will be removed in the Juno release."
+"(BoolOpt) Whether Secure Messaging (Encryption) is enabled, defaults to not "
+"enabled"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml81(td)
-msgid "virt_type = kvm"
+#: ./doc/common/tables/trove-rpc.xml88(td)
+msgid "enforced = False"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml82(td)
+#: ./doc/common/tables/trove-rpc.xml89(td)
 msgid ""
-"(StrOpt) Libvirt domain type (valid options are: kvm, lxc, qemu, uml, xen)"
+"(BoolOpt) Whether Secure Messaging (Signing) is enforced, defaults to not "
+"enforced"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml85(td)
-#: ./doc/common/tables/cinder-storage.xml98(td)
-msgid "volume_clear = zero"
+#: ./doc/common/tables/trove-rpc.xml92(td)
+msgid "kds_endpoint = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml86(td)
+#: ./doc/common/tables/trove-rpc.xml93(td)
+msgid "(StrOpt) KDS endpoint (ex: http://kds.example.com:35357/v3)"
+msgstr ""
+
+#: ./doc/common/tables/trove-rpc.xml96(td)
+msgid "secret_key = None"
+msgstr ""
+
+#: ./doc/common/tables/trove-rpc.xml97(td)
 msgid ""
-"(StrOpt) Method used to wipe old volumes (valid options are: none, zero, "
-"shred)"
+"(MultiStrOpt) A list of keys: (ex: name:&lt;base64 encoded key&gt;), ignored"
+" if secret_keys_file is set"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml89(td)
-#: ./doc/common/tables/cinder-storage.xml106(td)
-msgid "volume_clear_size = 0"
+#: ./doc/common/tables/trove-rpc.xml100(td)
+msgid "secret_keys_file = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml90(td)
-#: ./doc/common/tables/cinder-storage.xml107(td)
-msgid "(IntOpt) Size in MiB to wipe at start of old volumes. 0 =&gt; all"
-msgstr ""
-
-#: ./doc/common/tables/nova-libvirt.xml93(td)
+#: ./doc/common/tables/trove-rpc.xml101(td)
 msgid ""
-"volume_drivers = iscsi=nova.virt.libvirt.volume.LibvirtISCSIVolumeDriver, "
-"iser=nova.virt.libvirt.volume.LibvirtISERVolumeDriver, "
-"local=nova.virt.libvirt.volume.LibvirtVolumeDriver, "
-"fake=nova.virt.libvirt.volume.LibvirtFakeVolumeDriver, "
-"rbd=nova.virt.libvirt.volume.LibvirtNetVolumeDriver, "
-"sheepdog=nova.virt.libvirt.volume.LibvirtNetVolumeDriver, "
-"nfs=nova.virt.libvirt.volume.LibvirtNFSVolumeDriver, "
-"aoe=nova.virt.libvirt.volume.LibvirtAOEVolumeDriver, "
-"glusterfs=nova.virt.libvirt.volume.LibvirtGlusterfsVolumeDriver, "
-"fibre_channel=nova.virt.libvirt.volume.LibvirtFibreChannelVolumeDriver, "
-"scality=nova.virt.libvirt.volume.LibvirtScalityVolumeDriver"
+"(StrOpt) Path to the file containing the keys, takes precedence over "
+"secret_key"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml94(td)
-msgid "(ListOpt) Libvirt handlers for remote volumes."
+#: ./doc/common/tables/ceilometer-swift.xml22(td)
+msgid "reseller_prefix = AUTH_"
 msgstr ""
 
-#: ./doc/common/tables/nova-libvirt.xml97(td)
-msgid "wait_soft_reboot_seconds = 120"
-msgstr ""
-
-#: ./doc/common/tables/nova-libvirt.xml98(td)
+#: ./doc/common/tables/ceilometer-swift.xml23(td)
 msgid ""
-"(IntOpt) Number of seconds to wait for instance to shut down after soft "
-"reboot request is made. We fall back to hard reboot if instance does not "
-"shutdown within this window."
+"(StrOpt) Swift reseller prefix. Must be on par with reseller_prefix in "
+"proxy-server.conf."
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml8(caption)
+msgid "Description of configuration options for backup"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml22(td)
+msgid "backup_aes_cbc_key = default_aes_cbc_key"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml23(td)
+msgid "(StrOpt) Default OpenSSL aes_cbc key."
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml26(td)
+msgid "backup_chunk_size = 65536"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml27(td)
+msgid ""
+"(IntOpt) Chunk size to stream to swift container. This should be in "
+"multiples of 128 bytes, since this is the size of an md5 digest block "
+"allowing the process to update the file checksum during streaming. See: "
+"http://stackoverflow.com/questions/1131220/"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml30(td)
+msgid ""
+"backup_incremental_strategy = {'InnoBackupEx': 'InnoBackupExIncremental'}"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml31(td)
+msgid ""
+"(DictOpt) Incremental Backup Runner Based off of the default strategy. For "
+"strategies that do not implement an incremental the runner will use the "
+"default full backup."
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml34(td)
+msgid "backup_namespace = trove.guestagent.strategies.backup.mysql_impl"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml35(td)
+msgid "(StrOpt) Namespace to load backup strategies from."
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml38(td)
+msgid "backup_runner = trove.guestagent.backup.backup_types.InnoBackupEx"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml42(td)
+msgid "backup_runner_options = {}"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml43(td)
+msgid "(DictOpt) Additional options to be passed to the backup runner."
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml46(td)
+msgid "backup_segment_max_size = 2147483648"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml47(td)
+msgid "(IntOpt) Maximum size of each segment of the backup file."
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml54(td)
+msgid "backup_swift_container = database_backups"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml58(td)
+msgid "backup_use_gzip_compression = True"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml59(td)
+msgid "(BoolOpt) Compress backups using gzip."
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml62(td)
+msgid "backup_use_openssl_encryption = True"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml63(td)
+msgid "(BoolOpt) Encrypt backups using OpenSSL."
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml66(td)
+msgid "backup_use_snet = False"
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml67(td)
+msgid "(BoolOpt) Send backup files over snet."
+msgstr ""
+
+#: ./doc/common/tables/trove-backup.xml70(td)
+msgid "backups_page_size = 20"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml8(caption)
+msgid "Description of configuration options for network"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml22(td)
+msgid "allow_same_net_traffic = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml23(td)
+msgid "(BoolOpt) Whether to allow network traffic from same network"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml26(td)
+msgid "auto_assign_floating_ip = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml27(td)
+msgid "(BoolOpt) Autoassigning floating IP to VM"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml30(td)
+msgid "cnt_vpn_clients = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml31(td)
+msgid "(IntOpt) Number of addresses reserved for vpn clients"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml34(td)
+msgid "create_unique_mac_address_attempts = 5"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml35(td)
+msgid "(IntOpt) Number of attempts to create unique mac address"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml38(td)
+msgid "default_access_ip_network_name = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml39(td)
+msgid "(StrOpt) Name of network to use to set access IPs for instances"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml42(td)
+msgid "default_floating_pool = nova"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml43(td)
+msgid "(StrOpt) Default pool for floating IPs"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml46(td)
+msgid "defer_iptables_apply = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml47(td)
+msgid ""
+"(BoolOpt) Whether to batch up the application of IPTables rules during a "
+"host restart and apply all at the end of the init phase"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml50(td)
+msgid "dhcp_domain = novalocal"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml54(td)
+msgid "dhcp_lease_time = 120"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml55(td)
+msgid "(IntOpt) Lifetime of a DHCP lease in seconds"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml58(td)
+msgid "dhcpbridge = $bindir/nova-dhcpbridge"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml59(td)
+msgid "(StrOpt) Location of nova-dhcpbridge"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml62(td)
+msgid "dhcpbridge_flagfile = ['/etc/nova/nova-dhcpbridge.conf']"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml63(td)
+msgid "(MultiStrOpt) Location of flagfiles for dhcpbridge"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml66(td)
+msgid "dns_server = []"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml67(td)
+msgid ""
+"(MultiStrOpt) If set, uses specific DNS server for dnsmasq. Can be specified"
+" multiple times."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml70(td)
+msgid "dns_update_periodic_interval = -1"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml71(td)
+msgid ""
+"(IntOpt) Number of seconds to wait between runs of updates to DNS entries."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml74(td)
+#: ./doc/common/tables/neutron-dhcp_agent.xml22(td)
+msgid "dnsmasq_config_file ="
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml75(td)
+#: ./doc/common/tables/neutron-dhcp_agent.xml23(td)
+msgid "(StrOpt) Override the default dnsmasq settings with this file"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml78(td)
+#: ./doc/common/tables/neutron-securitygroups.xml26(td)
+msgid "firewall_driver = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml79(td)
+msgid ""
+"(StrOpt) Firewall driver (defaults to hypervisor specific iptables driver)"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml82(td)
+msgid "fixed_ip_disassociate_timeout = 600"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml83(td)
+msgid "(IntOpt) Seconds after which a deallocated IP is disassociated"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml86(td)
+msgid "flat_injected = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml87(td)
+msgid "(BoolOpt) Whether to attempt to inject network setup into guest"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml90(td)
+msgid "flat_interface = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml91(td)
+msgid "(StrOpt) FlatDhcp will bridge into this interface if set"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml94(td)
+msgid "flat_network_bridge = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml95(td)
+msgid "(StrOpt) Bridge for simple network instances"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml98(td)
+msgid "flat_network_dns = 8.8.4.4"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml99(td)
+msgid "(StrOpt) DNS server for simple network"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml102(td)
+msgid "floating_ip_dns_manager = nova.network.noop_dns_driver.NoopDNSDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml103(td)
+msgid "(StrOpt) Full class name for the DNS Manager for floating IPs"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml106(td)
+msgid "force_dhcp_release = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml107(td)
+msgid "(BoolOpt) If True, send a dhcp release on instance termination"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml110(td)
+msgid "force_snat_range = []"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml111(td)
+msgid ""
+"(MultiStrOpt) Traffic to this range will always be snatted to the fallback "
+"ip, even if it would normally be bridged out of the node. Can be specified "
+"multiple times."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml114(td)
+msgid "forward_bridge_interface = ['all']"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml115(td)
+msgid ""
+"(MultiStrOpt) An interface that bridges can forward to. If this is set to "
+"all then all traffic will be forwarded. Can be specified multiple times."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml118(td)
+msgid "gateway = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml119(td)
+msgid "(StrOpt) Default IPv4 gateway"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml122(td)
+msgid "injected_network_template = $pybasedir/nova/virt/interfaces.template"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml123(td)
+msgid "(StrOpt) Template file for injected network"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml126(td)
+msgid "instance_dns_domain ="
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml127(td)
+msgid "(StrOpt) Full class name for the DNS Zone for instance IPs"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml130(td)
+msgid "instance_dns_manager = nova.network.noop_dns_driver.NoopDNSDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml131(td)
+msgid "(StrOpt) Full class name for the DNS Manager for instance IPs"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml134(td)
+msgid "iptables_bottom_regex ="
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml135(td)
+msgid ""
+"(StrOpt) Regular expression to match iptables rule that should always be on "
+"the bottom."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml138(td)
+msgid "iptables_drop_action = DROP"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml139(td)
+msgid ""
+"(StrOpt) The table that iptables to jump to when a packet is to be dropped."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml142(td)
+msgid "iptables_top_regex ="
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml143(td)
+msgid ""
+"(StrOpt) Regular expression to match iptables rule that should always be on "
+"the top."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml146(td)
+msgid "l3_lib = nova.network.l3.LinuxNetL3"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml147(td)
+msgid "(StrOpt) Indicates underlying L3 management library"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml150(td)
+msgid ""
+"linuxnet_interface_driver = "
+"nova.network.linux_net.LinuxBridgeInterfaceDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml151(td)
+msgid "(StrOpt) Driver used to create ethernet devices."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml154(td)
+msgid "linuxnet_ovs_integration_bridge = br-int"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml155(td)
+msgid "(StrOpt) Name of Open vSwitch bridge used with linuxnet"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml158(td)
+msgid "multi_host = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml159(td)
+msgid ""
+"(BoolOpt) Default value for multi_host in networks. Also, if set, some rpc "
+"network calls will be sent directly to host."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml162(td)
+msgid "network_allocate_retries = 0"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml163(td)
+msgid "(IntOpt) Number of times to retry network allocation on failures"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml166(td)
+msgid "network_api_class = nova.network.api.API"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml167(td)
+msgid "(StrOpt) The full class name of the network API class to use"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml171(td)
+msgid "(IntOpt) MTU setting for network interface"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml174(td)
+msgid "network_driver = nova.network.linux_net"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml175(td)
+msgid "(StrOpt) Driver to use for network creation"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml178(td)
+msgid "network_manager = nova.network.manager.VlanManager"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml179(td)
+msgid "(StrOpt) Full class name for the Manager for network"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml182(td)
+msgid "network_size = 256"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml183(td)
+msgid "(IntOpt) Number of addresses in each private subnet"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml186(td)
+msgid "network_topic = network"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml187(td)
+msgid "(StrOpt) The topic network nodes listen on"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml190(td)
+msgid "networks_path = $state_path/networks"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml191(td)
+msgid "(StrOpt) Location to keep network config files"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml194(td)
+msgid "num_networks = 1"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml195(td)
+msgid "(IntOpt) Number of networks to support"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml198(td)
+msgid "ovs_vsctl_timeout = 120"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml199(td)
+msgid ""
+"(IntOpt) Amount of time, in seconds, that ovs_vsctl should wait for a "
+"response from the database. 0 is to wait forever."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml202(td)
+msgid "public_interface = eth0"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml203(td)
+msgid "(StrOpt) Interface for public IP addresses"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml206(td)
+msgid "routing_source_ip = $my_ip"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml207(td)
+msgid "(StrOpt) Public IP of network host"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml210(td)
+msgid "security_group_api = nova"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml211(td)
+msgid "(StrOpt) The full class name of the security API class"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml214(td)
+msgid "send_arp_for_ha = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml215(td)
+msgid "(BoolOpt) Send gratuitous ARPs for HA setup"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml218(td)
+msgid "send_arp_for_ha_count = 3"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml219(td)
+msgid "(IntOpt) Send this many gratuitous ARPs for HA setup"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml222(td)
+msgid "share_dhcp_address = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml223(td)
+msgid ""
+"(BoolOpt) If True in multi_host mode, all compute hosts share the same dhcp "
+"address. The same IP address used for DHCP will be added on each nova-"
+"network node which is only visible to the vms on the same host."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml226(td)
+msgid "teardown_unused_network_gateway = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml227(td)
+msgid ""
+"(BoolOpt) If True, unused gateway devices (VLAN and bridge) are deleted in "
+"VLAN network mode with multi hosted networks"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml230(td)
+msgid "update_dns_entries = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml231(td)
+msgid ""
+"(BoolOpt) If True, when a DNS entry must be updated, it sends a fanout cast "
+"to all network hosts to update their DNS entries in multi host mode"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml234(td)
+msgid "use_network_dns_servers = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml235(td)
+msgid ""
+"(BoolOpt) If set, uses the dns1 and dns2 from the network ref. as dns "
+"servers."
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml238(td)
+msgid "use_neutron_default_nets = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml239(td)
+msgid "(StrOpt) Control for checking for default networks"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml242(td)
+msgid "use_single_default_gateway = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml243(td)
+msgid ""
+"(BoolOpt) Use single default gateway. Only first nic of vm will get default "
+"gateway from dhcp server"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml246(td)
+msgid "vlan_interface = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml247(td)
+msgid "(StrOpt) VLANs will bridge into this interface if set"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml250(td)
+msgid "vlan_start = 100"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml251(td)
+msgid "(IntOpt) First VLAN for private networks"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml257(td)
+msgid "vlan_interface = vmnic0"
+msgstr ""
+
+#: ./doc/common/tables/nova-network.xml258(td)
+msgid "(StrOpt) Physical ethernet adapter name for vlan networking"
+msgstr ""
+
+#: ./doc/common/tables/glance-redis.xml23(td)
+#: ./doc/common/tables/keystone-redis.xml23(td)
+msgid "(StrOpt) Host to locate redis."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml8(caption)
+#: ./doc/common/tables/cinder-ssl.xml8(caption)
+#: ./doc/common/tables/trove-ssl.xml8(caption)
+#: ./doc/common/tables/neutron-ssl.xml8(caption)
+#: ./doc/common/tables/ceilometer-ssl.xml8(caption)
+#: ./doc/common/tables/glance-ssl.xml8(caption)
+msgid "Description of configuration options for ssl"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml19(th)
+msgid "[signing]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml22(td)
+#: ./doc/common/tables/keystone-ssl.xml57(td)
+msgid "ca_certs = /etc/keystone/ssl/certs/ca.pem"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml23(td)
+msgid "(StrOpt) Path of the CA for token signing."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml26(td)
+#: ./doc/common/tables/keystone-ssl.xml61(td)
+msgid "ca_key = /etc/keystone/ssl/private/cakey.pem"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml27(td)
+msgid "(StrOpt) Path of the CA Key for token signing."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml30(td)
+msgid "cert_subject = /C=US/ST=Unset/L=Unset/O=Unset/CN=www.example.com"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml31(td)
+msgid ""
+"(StrOpt) Certificate Subject (auto generated certificate) for token signing."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml34(td)
+msgid "certfile = /etc/keystone/ssl/certs/signing_cert.pem"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml35(td)
+msgid "(StrOpt) Path of the certfile for token signing."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml38(td)
+msgid "key_size = 2048"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml39(td)
+msgid ""
+"(IntOpt) Key Size (in bits) for token signing cert (auto generated "
+"certificate)."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml42(td)
+msgid "keyfile = /etc/keystone/ssl/private/signing_key.pem"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml43(td)
+msgid "(StrOpt) Path of the keyfile for token signing."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml46(td)
+msgid "token_format = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml47(td)
+msgid "(StrOpt) Deprecated in favor of provider in the [token] section."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml50(td)
+#: ./doc/common/tables/keystone-ssl.xml89(td)
+msgid "valid_days = 3650"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml51(td)
+msgid ""
+"(IntOpt) Day the token signing cert is valid for (auto generated "
+"certificate)."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml58(td)
+msgid "(StrOpt) Path of the ca cert file for SSL."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml62(td)
+msgid "(StrOpt) Path of the CA key file for SSL."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml65(td)
+msgid "cert_required = False"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml66(td)
+msgid "(BoolOpt) Require client certificate."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml69(td)
+msgid "cert_subject = /C=US/ST=Unset/L=Unset/O=Unset/CN=localhost"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml70(td)
+msgid "(StrOpt) SSL Certificate Subject (auto generated certificate)."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml73(td)
+msgid "certfile = /etc/keystone/ssl/certs/keystone.pem"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml74(td)
+msgid "(StrOpt) Path of the certfile for SSL."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml78(td)
+msgid "(BoolOpt) Toggle for SSL support on the keystone eventlet servers."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml81(td)
+msgid "key_size = 1024"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml82(td)
+msgid "(IntOpt) SSL Key Length (in bits) (auto generated certificate)."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml85(td)
+msgid "keyfile = /etc/keystone/ssl/private/keystonekey.pem"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml86(td)
+msgid "(StrOpt) Path of the keyfile for SSL."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ssl.xml90(td)
+msgid ""
+"(IntOpt) Days the certificate is valid for once signed (auto generated "
+"certificate)."
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml8(caption)
+msgid "Description of configuration options for ca"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml22(td)
+msgid "ca_file = cacert.pem"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml23(td)
+msgid "(StrOpt) Filename of root CA"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml26(td)
+msgid "ca_path = $state_path/CA"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml27(td)
+msgid "(StrOpt) Where we keep our root CA"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml30(td)
+msgid "cert_manager = nova.cert.manager.CertManager"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml31(td)
+msgid "(StrOpt) Full class name for the Manager for cert"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml34(td)
+msgid "cert_topic = cert"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml35(td)
+msgid "(StrOpt) The topic cert nodes listen on"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml38(td)
+msgid "crl_file = crl.pem"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml39(td)
+msgid "(StrOpt) Filename of root Certificate Revocation List"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml42(td)
+msgid "key_file = private/cakey.pem"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml43(td)
+msgid "(StrOpt) Filename of private key"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml46(td)
+msgid "keys_path = $state_path/keys"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml47(td)
+msgid "(StrOpt) Where we keep our keys"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml50(td)
+msgid ""
+"project_cert_subject = /C=US/ST=California/O=OpenStack/OU=NovaDev/CN"
+"=project-ca-%.16s-%s"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml51(td)
+msgid ""
+"(StrOpt) Subject for certificate for projects, %s for project, timestamp"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml54(td)
+msgid "use_project_ca = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml55(td)
+msgid "(BoolOpt) Should we use a CA for each project?"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml58(td)
+msgid ""
+"user_cert_subject = "
+"/C=US/ST=California/O=OpenStack/OU=NovaDev/CN=%.16s-%.16s-%s"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml59(td)
+msgid ""
+"(StrOpt) Subject for certificate for users, %s for project, user, timestamp"
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml66(td)
+#: ./doc/common/tables/glance-ssl.xml23(td)
+msgid "(StrOpt) CA certificate file to use to verify connecting clients."
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml70(td)
+msgid "(StrOpt) Certificate file to use when starting the server securely."
+msgstr ""
+
+#: ./doc/common/tables/nova-ca.xml74(td)
+msgid "(StrOpt) Private key file to use when starting the server securely."
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml8(caption)
+msgid "Description of configuration options for dhcp_agent"
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml26(td)
+msgid "dnsmasq_dns_servers = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml27(td)
+msgid ""
+"(ListOpt) Comma-separated list of the DNS servers which will be used as "
+"forwarders."
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml30(td)
+msgid "dnsmasq_lease_max = 16777216"
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml31(td)
+msgid "(IntOpt) Limit number of leases to prevent a denial-of-service."
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml34(td)
+msgid "enable_isolated_metadata = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml35(td)
+msgid "(BoolOpt) Support Metadata requests on isolated networks."
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml38(td)
+msgid "enable_metadata_network = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml39(td)
+msgid ""
+"(BoolOpt) Allows for serving metadata requests from a dedicated network. "
+"Requires enable_isolated_metadata = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml42(td)
+msgid "num_sync_threads = 4"
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml43(td)
+msgid "(IntOpt) Number of threads to use during sync process."
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml46(td)
+msgid "resync_interval = 5"
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml47(td)
+msgid "(IntOpt) Interval to resync."
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml50(td)
+msgid "use_namespaces = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-dhcp_agent.xml51(td)
+msgid "(BoolOpt) Allow overlapping IP."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml8(caption)
+msgid "Description of configuration options for collector"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml22(td)
+msgid "collector_workers = 1"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml23(td)
+msgid ""
+"(IntOpt) Number of workers for collector service. A single collector is "
+"enabled by default."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml26(th)
+msgid "[collector]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml29(td)
+msgid "udp_address = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml30(td)
+msgid ""
+"(StrOpt) Address to which the UDP socket is bound. Set to an empty string to"
+" disable."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml33(td)
+msgid "udp_port = 4952"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml34(td)
+msgid "(IntOpt) Port to which the UDP socket is bound."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml37(th)
+msgid "[dispatcher_file]"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml40(td)
+msgid "backup_count = 0"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml41(td)
+msgid "(IntOpt) The max number of the files to keep."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml44(td)
+msgid "file_path = None"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml45(td)
+msgid "(StrOpt) Name and the location of the file to record meters."
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml48(td)
+msgid "max_bytes = 0"
+msgstr ""
+
+#: ./doc/common/tables/ceilometer-collector.xml49(td)
+msgid "(IntOpt) The max size of the file."
+msgstr ""
+
+#: ./doc/common/tables/cinder-hds-hus.xml8(caption)
+msgid "Description of configuration options for hds-hus"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hds-hus.xml22(td)
+msgid "hds_cinder_config_file = /opt/hds/hus/cinder_hus_conf.xml"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hds-hus.xml23(td)
+msgid "(StrOpt) configuration file for HDS cinder plugin for HUS"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml8(caption)
+msgid "Description of configuration options for netapp_7mode_iscsi"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml54(td)
+msgid "netapp_vfiler = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml55(td)
+msgid ""
+"(StrOpt) The vFiler unit on which provisioning of block storage volumes will"
+" be done. This option is only used by the driver when connecting to an "
+"instance with a storage family of Data ONTAP operating in 7-Mode and the "
+"storage protocol selected is iSCSI. Only use this option when utilizing the "
+"MultiStore feature on the NetApp storage system."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml58(td)
+msgid "netapp_volume_list = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_7mode_iscsi.xml59(td)
+msgid ""
+"(StrOpt) This option is only utilized when the storage protocol is "
+"configured to use iSCSI. This option is used to restrict provisioning to the"
+" specified controller volumes. Specify the value of this option to be a "
+"comma separated list of NetApp controller volume names to be used for "
+"provisioning."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-hash.xml7(literal)
+msgid "[swift-hash]"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-hash.xml18(td)
+msgid "swift_hash_path_suffix = changeme"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-hash.xml18(td)
+msgid ""
+"A suffix used by hash_path to offer a bit more security when generating "
+"hashes for paths. It simply appends this value to all paths; if someone "
+"knows this suffix, it's easier for them to guess the hash a path will end up"
+" with. New installations are advised to set this parameter to a random "
+"secret, which would not be disclosed ouside the organization. The same "
+"secret needs to be used by all swift servers of the same cluster. Existing "
+"installations should set this parameter to an empty string."
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-hash.xml29(td)
+msgid "swift_hash_path_prefix = changeme"
+msgstr ""
+
+#: ./doc/common/tables/swift-swift-swift-hash.xml29(td)
+msgid ""
+"A prefix used by hash_path to offer a bit more security when generating "
+"hashes for paths. It simply appends this value to all paths; if someone "
+"knows this suffix, it's easier for them to guess the hash a path will end up"
+" with. New installations are advised to set this parameter to a random "
+"secret, which would not be disclosed ouside the organization. The same "
+"secret needs to be used by all swift servers of the same cluster. Existing "
+"installations should set this parameter to an empty string."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_gre.xml8(caption)
+msgid "Description of configuration options for ml2_gre"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_gre.xml19(th)
+msgid "[ml2_type_gre]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_gre.xml23(td)
+msgid ""
+"(ListOpt) Comma-separated list of &lt;tun_min&gt;:&lt;tun_max&gt; tuples "
+"enumerating ranges of GRE tunnel IDs that are available for tenant network "
+"allocation"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml8(caption)
+msgid "Description of configuration options for varmour"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml19(th)
+msgid "[vArmour]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml22(td)
+msgid "director = localhost"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml23(td)
+msgid "(StrOpt) vArmour director ip"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml26(td)
+msgid "director_port = 443"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml27(td)
+msgid "(StrOpt) vArmour director port"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml30(td)
+msgid "password = varmour"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml31(td)
+msgid "(StrOpt) vArmour director password"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml34(td)
+msgid "username = varmour"
+msgstr ""
+
+#: ./doc/common/tables/neutron-varmour.xml35(td)
+msgid "(StrOpt) vArmour director username"
+msgstr ""
+
+#: ./doc/common/tables/heat-debug.xml8(caption)
+#: ./doc/common/tables/trove-debug.xml8(caption)
+#: ./doc/common/tables/keystone-debug.xml8(caption)
+msgid "Description of configuration options for debug"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml7(literal)
+msgid "[filter:dlo]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml18(td)
+msgid "use = egg:swift#dlo"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-dlo.xml24(td)
+msgid "rate_limit_segments_per_sec = 1"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml8(caption)
+msgid "Description of configuration options for guestagent"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml22(td)
+msgid "agent_call_high_timeout = 60"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml26(td)
+msgid "agent_call_low_timeout = 5"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml30(td)
+msgid "agent_heartbeat_time = 10"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml34(td)
+msgid "guest_config = $pybasedir/etc/trove/trove-guestagent.conf.sample"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml35(td)
+msgid "(StrOpt) Path to guestagent config file."
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml38(td)
+msgid "guest_id = None"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml42(td)
+msgid "ignore_dbs = lost+found, mysql, information_schema"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml46(td)
+msgid "ignore_users = os_admin, root"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml50(td)
+msgid "mount_options = defaults,noatime"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml54(td)
+msgid "restore_namespace = trove.guestagent.strategies.restore.mysql_impl"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml55(td)
+msgid "(StrOpt) Namespace to load restore strategies from."
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml58(td)
+msgid "storage_namespace = trove.guestagent.strategies.storage.swift"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml59(td)
+msgid "(StrOpt) Namespace to load the default storage strategy from."
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml62(td)
+msgid "storage_strategy = SwiftStorage"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml63(td)
+msgid "(StrOpt) Default strategy to store backups."
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml66(td)
+#: ./doc/common/tables/trove-taskmanager.xml66(td)
+msgid "usage_sleep_time = 5"
+msgstr ""
+
+#: ./doc/common/tables/trove-guestagent.xml67(td)
+#: ./doc/common/tables/trove-taskmanager.xml67(td)
+msgid "(IntOpt) Time to sleep during the check active guest."
+msgstr ""
+
+#: ./doc/common/tables/nova-qpid.xml23(td)
+#: ./doc/common/tables/glance-qpid.xml23(td)
+#: ./doc/common/tables/cinder-rpc.xml95(td)
+#: ./doc/common/tables/nova-rpc_all.xml63(td)
+#: ./doc/common/tables/keystone-qpid.xml23(td)
+msgid "(IntOpt) Seconds between connection keepalive heartbeats."
+msgstr ""
+
+#: ./doc/common/tables/nova-qpid.xml27(td)
+#: ./doc/common/tables/glance-qpid.xml27(td)
+#: ./doc/common/tables/cinder-rpc.xml99(td)
+#: ./doc/common/tables/nova-rpc_all.xml67(td)
+#: ./doc/common/tables/keystone-qpid.xml27(td)
+msgid "(StrOpt) Qpid broker hostname."
+msgstr ""
+
+#: ./doc/common/tables/nova-qpid.xml31(td)
+#: ./doc/common/tables/glance-qpid.xml31(td)
+#: ./doc/common/tables/cinder-rpc.xml103(td)
+#: ./doc/common/tables/nova-rpc_all.xml71(td)
+#: ./doc/common/tables/keystone-qpid.xml31(td)
+msgid "(ListOpt) Qpid HA cluster host:port pairs."
+msgstr ""
+
+#: ./doc/common/tables/nova-qpid.xml35(td)
+#: ./doc/common/tables/glance-qpid.xml35(td)
+#: ./doc/common/tables/cinder-rpc.xml107(td)
+#: ./doc/common/tables/nova-rpc_all.xml75(td)
+#: ./doc/common/tables/keystone-qpid.xml35(td)
+msgid "(StrOpt) Password for Qpid connection."
+msgstr ""
+
+#: ./doc/common/tables/nova-qpid.xml39(td)
+#: ./doc/common/tables/glance-qpid.xml39(td)
+#: ./doc/common/tables/cinder-rpc.xml111(td)
+#: ./doc/common/tables/nova-rpc_all.xml79(td)
+#: ./doc/common/tables/keystone-qpid.xml39(td)
+msgid "(IntOpt) Qpid broker port."
+msgstr ""
+
+#: ./doc/common/tables/nova-qpid.xml43(td)
+#: ./doc/common/tables/glance-qpid.xml43(td)
+#: ./doc/common/tables/cinder-rpc.xml115(td)
+#: ./doc/common/tables/nova-rpc_all.xml83(td)
+#: ./doc/common/tables/keystone-qpid.xml43(td)
+msgid "(StrOpt) Transport to use, either 'tcp' or 'ssl'."
+msgstr ""
+
+#: ./doc/common/tables/nova-qpid.xml47(td)
+#: ./doc/common/tables/glance-qpid.xml47(td)
+#: ./doc/common/tables/cinder-rpc.xml119(td)
+#: ./doc/common/tables/nova-rpc_all.xml87(td)
+#: ./doc/common/tables/keystone-qpid.xml47(td)
+msgid "(StrOpt) Space separated list of SASL mechanisms to use for auth."
+msgstr ""
+
+#: ./doc/common/tables/nova-qpid.xml51(td)
+#: ./doc/common/tables/glance-qpid.xml51(td)
+#: ./doc/common/tables/cinder-rpc.xml123(td)
+#: ./doc/common/tables/nova-rpc_all.xml91(td)
+#: ./doc/common/tables/keystone-qpid.xml51(td)
+msgid "(BoolOpt) Whether to disable the Nagle algorithm."
+msgstr ""
+
+#: ./doc/common/tables/nova-qpid.xml59(td)
+#: ./doc/common/tables/glance-qpid.xml59(td)
+#: ./doc/common/tables/cinder-rpc.xml131(td)
+#: ./doc/common/tables/nova-rpc_all.xml99(td)
+#: ./doc/common/tables/keystone-qpid.xml59(td)
+msgid "(StrOpt) Username for Qpid connection."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_l2pop.xml8(caption)
+msgid "Description of configuration options for ml2_l2pop"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_l2pop.xml19(th)
+msgid "[l2pop]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_l2pop.xml22(td)
+msgid "agent_boot_time = 180"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_l2pop.xml23(td)
+msgid ""
+"(IntOpt) Delay within which agent is expected to update existing ports whent"
+" it restarts"
+msgstr ""
+
+#: ./doc/common/tables/glance-zmq.xml8(caption)
+msgid "Description of configuration options for zmq"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml8(caption)
+msgid "Description of configuration options for embrane_lb"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml19(th)
+msgid "[heleoslb]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml23(td)
+#: ./doc/common/tables/neutron-common.xml220(td)
+msgid "(StrOpt) ESM admin password."
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml26(td)
+msgid "admin_username = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml30(td)
+msgid "async_requests = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml35(td)
+msgid "(StrOpt) Dummy user traffic Security Zone id for LBs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml43(td)
+msgid "(StrOpt) In band Security Zone id for LBs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml46(td)
+msgid "lb_flavor = small"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml47(td)
+msgid "(StrOpt) choose LB image flavor to use, accepted values: small, medium"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml50(td)
+msgid "lb_image = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml51(td)
+msgid "(StrOpt) Load Balancer image id (Embrane LB)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml55(td)
+msgid "(StrOpt) Management Security Zone id for LBs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml59(td)
+msgid "(StrOpt) Out of band Security Zone id for LBs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml66(td)
+msgid "sync_interval = 60"
+msgstr ""
+
+#: ./doc/common/tables/neutron-embrane_lb.xml67(td)
+msgid "(IntOpt) resource synchronization interval in seconds"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml7(literal)
+msgid "[filter:authtoken]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml18(td)
+msgid "auth_host = keystonehost"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml24(td)
+msgid "auth_protocol = http"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml27(td)
+msgid "auth_uri = http://keystonehost:5000/"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml30(td)
+msgid "admin_tenant_name = service"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml33(td)
+msgid "admin_user = swift"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml36(td)
+msgid "admin_password = password"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml39(td)
+msgid "delay_auth_decision = 1"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml42(td)
+msgid "cache = swift.cache"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml45(td)
+msgid "include_service_catalog = False"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-pipeline-main.xml18(td)
+msgid "pipeline = healthcheck recon object-server"
+msgstr ""
+
+#: ./doc/common/tables/swift-memcache-memcache.xml7(literal)
+#: ./doc/common/tables/keystone-memcache.xml19(th)
+msgid "[memcache]"
+msgstr ""
+
+#: ./doc/common/tables/swift-memcache-memcache.xml7(literal)
+msgid "memcache.conf-sample"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-app-account-server.xml7(literal)
+msgid "[app:account-server]"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-app-account-server.xml18(td)
+msgid "use = egg:swift#account"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-app-account-server.xml21(td)
+msgid "set log_name = account-server"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml7(literal)
+msgid "[filter:formpost]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml18(td)
+msgid "use = egg:swift#formpost"
+msgstr ""
+
+#: ./doc/common/tables/trove-compute.xml22(td)
+msgid "ip_regex = None"
+msgstr ""
+
+#: ./doc/common/tables/trove-compute.xml26(td)
+msgid "nova_compute_url = http://localhost:8774/v2"
+msgstr ""
+
+#: ./doc/common/tables/trove-compute.xml30(td)
+msgid "root_grant = ALL"
+msgstr ""
+
+#: ./doc/common/tables/trove-compute.xml34(td)
+msgid "root_grant_option = True"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml7(literal)
+msgid "[filter:proxy-logging]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml18(td)
+msgid "use = egg:swift#proxy_logging"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml21(td)
+msgid "access_log_name = swift"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml24(td)
+msgid "access_log_facility = LOG_LOCAL0"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml27(td)
+msgid "access_log_level = INFO"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml30(td)
+msgid "access_log_address = /dev/log"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml33(td)
+msgid "access_log_udp_host ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml36(td)
+msgid "access_log_udp_port = 514"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml39(td)
+msgid "access_log_statsd_host = localhost"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml42(td)
+msgid "access_log_statsd_port = 8125"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml45(td)
+msgid "access_log_statsd_default_sample_rate = 1.0"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml48(td)
+msgid "access_log_statsd_sample_rate_factor = 1.0"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml51(td)
+msgid "access_log_statsd_metric_prefix ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml54(td)
+msgid "access_log_headers = false"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml57(td)
+msgid "access_log_headers_only ="
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml60(td)
+msgid "logged with access_log_headers = True."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml63(td)
+msgid "reveal_sensitive_prefix = 8192"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml63(td)
+msgid ""
+"The X-Auth-Token is sensitive data. If revealed to an unauthorised person, "
+"they can now make requests against an account until the token expires. Set "
+"reveal_sensitive_prefix to the number of characters of the token that are "
+"logged. For example reveal_sensitive_prefix = 12 so only first 12 characters"
+" of the token are logged. Or, set to 0 to completely remove the token."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml72(td)
+msgid "log_statsd_valid_http_methods = GET,HEAD,POST,PUT,DELETE,COPY,OPTIONS"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_redis.xml8(caption)
+msgid "Description of configuration options for db_redis"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_redis.xml19(th)
+msgid "[redis]"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_redis.xml26(td)
+msgid "mount_point = /var/lib/redis"
+msgstr ""
+
+#: ./doc/common/tables/trove-db_redis.xml30(td)
+msgid "tcp_ports = 6379"
+msgstr ""
+
+#: ./doc/common/tables/cinder-rpc.xml38(td)
+msgid "default_timeout = 20"
+msgstr ""
+
+#: ./doc/common/tables/cinder-rpc.xml39(td)
+msgid "(IntOpt) Default Time Out For CLI operations in minutes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-rpc.xml234(td)
+msgid "volume_topic = cinder-volume"
+msgstr ""
+
+#: ./doc/common/tables/cinder-rpc.xml235(td)
+msgid "(StrOpt) the topic volume nodes listen on"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml7(literal)
+msgid "[realm2]"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml18(td)
+msgid "key = realm2key"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml21(td)
+msgid "key2 = realm2key2"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml24(td)
+msgid "cluster_name3 = https://host3/v1/"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm2.xml27(td)
+msgid "cluster_name4 = https://host4/v1/"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hpmsa.xml8(caption)
+msgid "Description of configuration options for hpmsa"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hpmsa.xml22(td)
+msgid "msa_vdisk = OpenStack"
+msgstr ""
+
+#: ./doc/common/tables/cinder-hpmsa.xml23(td)
+msgid "(StrOpt) The VDisk to use for volume creation."
+msgstr ""
+
+#: ./doc/common/tables/nova-apiv3.xml8(caption)
+msgid "Description of configuration options for apiv3"
+msgstr ""
+
+#: ./doc/common/tables/nova-apiv3.xml19(th)
+msgid "[osapi_v3]"
+msgstr ""
+
+#: ./doc/common/tables/nova-apiv3.xml23(td)
+msgid "(BoolOpt) Whether the V3 API is enabled or not"
+msgstr ""
+
+#: ./doc/common/tables/nova-apiv3.xml26(td)
+msgid "extensions_blacklist ="
+msgstr ""
+
+#: ./doc/common/tables/nova-apiv3.xml27(td)
+msgid ""
+"(ListOpt) A list of v3 API extensions to never load. Specify the extension "
+"aliases here."
+msgstr ""
+
+#: ./doc/common/tables/nova-apiv3.xml30(td)
+msgid "extensions_whitelist ="
+msgstr ""
+
+#: ./doc/common/tables/nova-apiv3.xml31(td)
+msgid ""
+"(ListOpt) If the list is not empty then a v3 API extension will only be "
+"loaded if it exists in this list. Specify the extension aliases here."
+msgstr ""
+
+#: ./doc/common/tables/keystone-oauth.xml8(caption)
+msgid "Description of configuration options for oauth"
+msgstr ""
+
+#: ./doc/common/tables/keystone-oauth.xml19(th)
+msgid "[oauth1]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-oauth.xml22(td)
+msgid "access_token_duration = 86400"
+msgstr ""
+
+#: ./doc/common/tables/keystone-oauth.xml23(td)
+msgid "(IntOpt) Duration (in seconds) for the OAuth Access Token."
+msgstr ""
+
+#: ./doc/common/tables/keystone-oauth.xml26(td)
+msgid "driver = keystone.contrib.oauth1.backends.sql.OAuth1"
+msgstr ""
+
+#: ./doc/common/tables/keystone-oauth.xml27(td)
+#: ./doc/common/tables/keystone-credential.xml23(td)
+msgid "(StrOpt) Keystone Credential backend driver."
+msgstr ""
+
+#: ./doc/common/tables/keystone-oauth.xml30(td)
+msgid "request_token_duration = 28800"
+msgstr ""
+
+#: ./doc/common/tables/keystone-oauth.xml31(td)
+msgid "(IntOpt) Duration (in seconds) for the OAuth Request Token."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml8(caption)
+msgid "Description of configuration options for storage_gpfs"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml22(td)
+msgid "gpfs_images_dir = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml23(td)
+msgid ""
+"(StrOpt) Specifies the path of the Image service repository in GPFS. Leave "
+"undefined if not storing images in GPFS."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml26(td)
+msgid "gpfs_images_share_mode = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml27(td)
+msgid ""
+"(StrOpt) Specifies the type of image copy to be used. Set this when the "
+"Image service repository also uses GPFS so that image files can be "
+"transferred efficiently from the Image service to the Block Storage service."
+" There are two valid values: \"copy\" specifies that a full copy of the "
+"image is made; \"copy_on_write\" specifies that copy-on-write optimization "
+"strategy is used and unmodified blocks of the image file are shared "
+"efficiently."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml30(td)
+msgid "gpfs_max_clone_depth = 0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml31(td)
+msgid ""
+"(IntOpt) Specifies an upper limit on the number of indirections required to "
+"reach a specific block due to snapshots or clones. A lengthy chain of copy-"
+"on-write snapshots or clones can have a negative impact on performance, but "
+"improves space utilization. 0 indicates unlimited clone depth."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml34(td)
+msgid "gpfs_mount_point_base = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml35(td)
+msgid ""
+"(StrOpt) Specifies the path of the GPFS directory where Block Storage volume"
+" and snapshot files are stored."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml38(td)
+msgid "gpfs_sparse_volumes = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml39(td)
+msgid ""
+"(BoolOpt) Specifies that volumes are created as sparse files which initially"
+" consume no space. If set to False, the volume is created as a fully "
+"allocated file, in which case, creation may take a significantly longer "
+"time."
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml42(td)
+msgid "gpfs_storage_pool = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-storage_gpfs.xml43(td)
+msgid ""
+"(StrOpt) Specifies the storage pool that volumes are assigned to. By "
+"default, the system storage pool is used."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_vlan.xml8(caption)
+msgid "Description of configuration options for ml2_vlan"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_vlan.xml19(th)
+msgid "[ml2_type_vlan]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_vlan.xml23(td)
+msgid ""
+"(ListOpt) List of &lt;physical_network&gt;:&lt;vlan_min&gt;:&lt;vlan_max&gt;"
+" or &lt;physical_network&gt; specifying physical_network names usable for "
+"VLAN provider and tenant networks, as well as ranges of VLAN tags on each "
+"available for allocation to tenant networks."
+msgstr ""
+
+#: ./doc/common/tables/keystone-notification.xml23(td)
+msgid ""
+"(StrOpt) onready allows you to send a notification when the process is ready"
+" to serve For example, to have it notify using systemd, one could set shell "
+"command: \"onready = systemd-notify --ready\" or a module with notify() "
+"method: \"onready = keystone.common.systemd\"."
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml7(literal)
+msgid "[object-auditor]"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml18(td)
+msgid "log_name = object-auditor"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml30(td)
+msgid "files_per_second = 20"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml30(td)
+msgid ""
+"Maximum files audited per second. Should be tuned according to individual "
+"system specs. 0 is unlimited."
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml33(td)
+msgid "bytes_per_second = 10000000"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml33(td)
+msgid ""
+"Maximum bytes audited per second. Should be tuned according to individual "
+"system specs. 0 is unlimited. mounted to prevent accidentally writing to the"
+" root device process simultaneously (it will actually accept(2) N + 1). "
+"Setting this to one (1) will only handle one request at a time, without "
+"accepting another request concurrently. By increasing the number of workers "
+"to a much higher value, one can reduce the impact of slow file system "
+"operations in one request from negatively impacting other requests. "
+"underlying filesystem does not support it. to setup custom log handlers. "
+"bytes you'd like fallocate to reserve, whether there is space for the given "
+"file size or not. This is useful for systems that behave badly when they "
+"completely run out of space; you can make the services pretend they're out "
+"of space early. container server. For most cases, this should be "
+"`egg:swift#container`."
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml36(td)
+msgid "log_time = 3600"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml36(td)
+msgid "Frequency of status logs in seconds."
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml39(td)
+msgid "zero_byte_files_per_second = 50"
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml39(td)
+msgid "Maximum zero byte files audited per second."
+msgstr ""
+
+#: ./doc/common/tables/swift-object-server-object-auditor.xml45(td)
+msgid "object_size_stats ="
+msgstr ""
+
+#: ./doc/common/tables/trove-zeromq.xml38(td)
+msgid ""
+"rpc_zmq_matchmaker = "
+"trove.openstack.common.rpc.matchmaker.MatchMakerLocalhost"
 msgstr ""
 
 #: ./doc/common/tables/neutron-lbaas.xml8(caption)
@@ -39329,4052 +44210,6 @@ msgstr ""
 msgid "(StrOpt) Swift user name"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_cisco.xml8(caption)
-msgid "Description of configuration options for ml2_cisco"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_cisco.xml19(th)
-#: ./doc/common/tables/neutron-cisco.xml119(th)
-msgid "[ml2_cisco]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_cisco.xml22(td)
-msgid "managed_physical_network = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_cisco.xml23(td)
-msgid "(StrOpt) The physical network managed by the switches."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml26(td)
-msgid "dispatcher = ['database']"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml27(td)
-msgid "(MultiStrOpt) Dispatcher to process data."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml30(td)
-msgid "rpc_backend = ceilometer.openstack.common.rpc.impl_kombu"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml66(td)
-msgid ""
-"rpc_zmq_matchmaker = "
-"ceilometer.openstack.common.rpc.matchmaker.MatchMakerLocalhost"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml78(th)
-msgid "[publisher]"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml81(td)
-msgid "metering_secret = change this or be hacked"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml82(td)
-msgid "(StrOpt) Secret value for signing metering messages."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml85(th)
-msgid "[publisher_rpc]"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml88(td)
-msgid "metering_topic = metering"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-rpc.xml89(td)
-msgid "(StrOpt) The topic that ceilometer uses for metering messages."
-msgstr ""
-
-#: ./doc/common/tables/heat-loadbalancer.xml8(caption)
-msgid "Description of configuration options for loadbalancer"
-msgstr ""
-
-#: ./doc/common/tables/heat-loadbalancer.xml22(td)
-msgid "loadbalancer_template = None"
-msgstr ""
-
-#: ./doc/common/tables/heat-loadbalancer.xml23(td)
-msgid "(StrOpt) Custom template for the built-in loadbalancer nested stack."
-msgstr ""
-
-#: ./doc/common/tables/heat-cloudwatch_api.xml8(caption)
-msgid "Description of configuration options for cloudwatch_api"
-msgstr ""
-
-#: ./doc/common/tables/heat-cloudwatch_api.xml22(td)
-#: ./doc/common/tables/heat-api.xml34(td)
-msgid "heat_watch_server_url ="
-msgstr ""
-
-#: ./doc/common/tables/heat-cloudwatch_api.xml23(td)
-#: ./doc/common/tables/heat-api.xml35(td)
-msgid "(StrOpt) URL of the Heat CloudWatch server."
-msgstr ""
-
-#: ./doc/common/tables/heat-cloudwatch_api.xml26(th)
-msgid "[heat_api_cloudwatch]"
-msgstr ""
-
-#: ./doc/common/tables/heat-cloudwatch_api.xml37(td)
-msgid "bind_port = 8003"
-msgstr ""
-
-#: ./doc/common/tables/heat-cloudwatch_api.xml50(td)
-msgid ""
-"(IntOpt) Maximum line size of message headers to be accepted. "
-"max_header_line may need to be increased when using large tokens (typically "
-"those generated by the Keystone v3 API with big service catalogs.)"
-msgstr ""
-
-#: ./doc/common/tables/nova-pci.xml8(caption)
-msgid "Description of configuration options for pci"
-msgstr ""
-
-#: ./doc/common/tables/nova-pci.xml22(td)
-msgid "pci_alias = []"
-msgstr ""
-
-#: ./doc/common/tables/nova-pci.xml23(td)
-msgid ""
-"(MultiStrOpt) An alias for a PCI passthrough device requirement. This allows"
-" users to specify the alias in the extra_spec for a flavor, without needing "
-"to repeat all the PCI property requirements. For example: pci_alias = { "
-"\"name\": \"QuicAssist\", \"product_id\": \"0443\", \"vendor_id\": \"8086\","
-" \"device_type\": \"ACCEL\" } defines an alias for the Intel QuickAssist "
-"card. (multi valued)"
-msgstr ""
-
-#: ./doc/common/tables/nova-pci.xml26(td)
-msgid "pci_passthrough_whitelist = []"
-msgstr ""
-
-#: ./doc/common/tables/nova-pci.xml27(td)
-msgid ""
-"(MultiStrOpt) White list of PCI devices available to VMs. For example: "
-"pci_passthrough_whitelist = [{\"vendor_id\": \"8086\", \"product_id\": "
-"\"0443\"}]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml7(literal)
-msgid "[filter:proxy-logging]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml18(td)
-msgid "use = egg:swift#proxy_logging"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml21(td)
-msgid "access_log_name = swift"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml24(td)
-msgid "access_log_facility = LOG_LOCAL0"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml27(td)
-msgid "access_log_level = INFO"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml30(td)
-msgid "access_log_address = /dev/log"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml33(td)
-msgid "access_log_udp_host ="
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml36(td)
-msgid "access_log_udp_port = 514"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml39(td)
-msgid "access_log_statsd_host = localhost"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml42(td)
-msgid "access_log_statsd_port = 8125"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml45(td)
-msgid "access_log_statsd_default_sample_rate = 1.0"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml48(td)
-msgid "access_log_statsd_sample_rate_factor = 1.0"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml51(td)
-msgid "access_log_statsd_metric_prefix ="
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml54(td)
-msgid "access_log_headers = false"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml57(td)
-msgid "access_log_headers_only ="
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml60(td)
-msgid "logged with access_log_headers = True."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml63(td)
-msgid "reveal_sensitive_prefix = 8192"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml63(td)
-msgid ""
-"The X-Auth-Token is sensitive data. If revealed to an unauthorised person, "
-"they can now make requests against an account until the token expires. Set "
-"reveal_sensitive_prefix to the number of characters of the token that are "
-"logged. For example reveal_sensitive_prefix = 12 so only first 12 characters"
-" of the token are logged. Or, set to 0 to completely remove the token."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-proxy-logging.xml72(td)
-msgid "log_statsd_valid_http_methods = GET,HEAD,POST,PUT,DELETE,COPY,OPTIONS"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_ceilometer.xml8(caption)
-msgid "Description of configuration options for clients_ceilometer"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_ceilometer.xml19(th)
-msgid "[clients_ceilometer]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-varmour.xml8(caption)
-msgid "Description of configuration options for varmour"
-msgstr ""
-
-#: ./doc/common/tables/neutron-varmour.xml19(th)
-msgid "[vArmour]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-varmour.xml22(td)
-msgid "director = localhost"
-msgstr ""
-
-#: ./doc/common/tables/neutron-varmour.xml23(td)
-msgid "(StrOpt) vArmour director ip"
-msgstr ""
-
-#: ./doc/common/tables/neutron-varmour.xml26(td)
-msgid "director_port = 443"
-msgstr ""
-
-#: ./doc/common/tables/neutron-varmour.xml27(td)
-msgid "(StrOpt) vArmour director port"
-msgstr ""
-
-#: ./doc/common/tables/neutron-varmour.xml30(td)
-msgid "password = varmour"
-msgstr ""
-
-#: ./doc/common/tables/neutron-varmour.xml31(td)
-msgid "(StrOpt) vArmour director password"
-msgstr ""
-
-#: ./doc/common/tables/neutron-varmour.xml34(td)
-msgid "username = varmour"
-msgstr ""
-
-#: ./doc/common/tables/neutron-varmour.xml35(td)
-msgid "(StrOpt) vArmour director username"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml8(caption)
-msgid "Description of configuration options for imagecache"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml22(td)
-msgid "cleanup_scrubber = False"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml23(td)
-msgid ""
-"(BoolOpt) A boolean that determines if the scrubber should clean up the "
-"files it uses for taking data. Only one server in your deployment should be "
-"designated the cleanup host."
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml26(td)
-msgid "cleanup_scrubber_time = 86400"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml27(td)
-msgid ""
-"(IntOpt) Items must have a modified time that is older than this value in "
-"order to be candidates for cleanup."
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml30(td)
-msgid "delayed_delete = False"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml31(td)
-msgid "(BoolOpt) Turn on/off delayed delete."
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml34(td)
-msgid "image_cache_dir = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml35(td)
-msgid "(StrOpt) Base directory that the Image Cache uses."
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml38(td)
-msgid "image_cache_driver = sqlite"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml39(td)
-msgid "(StrOpt) The driver to use for image cache management."
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml42(td)
-msgid "image_cache_max_size = 10737418240"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml43(td)
-msgid "(IntOpt) The maximum size in bytes that the cache can use."
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml46(td)
-msgid "image_cache_sqlite_db = cache.db"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml47(td)
-msgid ""
-"(StrOpt) The path to the sqlite file database that will be used for image "
-"cache management."
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml50(td)
-msgid "image_cache_stall_time = 86400"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml51(td)
-msgid ""
-"(IntOpt) The amount of time to let an image remain in the cache without "
-"being accessed."
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml54(td)
-msgid "scrub_time = 0"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml55(td)
-msgid ""
-"(IntOpt) The amount of time in seconds to delay before performing a delete."
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml58(td)
-msgid "scrubber_datadir = /var/lib/glance/scrubber"
-msgstr ""
-
-#: ./doc/common/tables/glance-imagecache.xml59(td)
-msgid ""
-"(StrOpt) Directory that the scrubber will use to track information about "
-"what to delete. Make sure this is set in glance-api.conf and glance-"
-"scrubber.conf."
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml22(td)
-msgid "max_accepted_volume_size = 5"
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml23(td)
-msgid "(IntOpt) Default maximum volume size for an instance."
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml26(td)
-msgid "max_backups_per_user = 50"
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml27(td)
-msgid "(IntOpt) Default maximum number of backups created by a tenant."
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml30(td)
-msgid "max_instances_per_user = 5"
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml31(td)
-msgid "(IntOpt) Default maximum number of instances per tenant."
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml34(td)
-msgid "max_volumes_per_user = 20"
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml35(td)
-msgid ""
-"(IntOpt) Default maximum volume capacity (in GB) spanning across all trove "
-"volumes per tenant"
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml38(td)
-msgid "quota_driver = trove.quota.quota.DbQuotaDriver"
-msgstr ""
-
-#: ./doc/common/tables/trove-quota.xml39(td)
-msgid "(StrOpt) Default driver to use for quota checks."
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-account.xml7(literal)
-msgid "[account]"
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-account.xml18(td)
-msgid "max connections = 2"
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-account.xml27(td)
-msgid "lock file = /var/lock/account.lock"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml8(caption)
-msgid "Description of configuration options for storage"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml22(td)
-msgid "allocated_capacity_weight_multiplier = -1.0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml23(td)
-#: ./doc/common/tables/cinder-storage.xml27(td)
-msgid ""
-"(FloatOpt) Multiplier used for weighing volume capacity. Negative numbers "
-"mean to stack vs spread."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml26(td)
-msgid "capacity_weight_multiplier = 1.0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml30(td)
-msgid "enabled_backends = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml31(td)
-msgid ""
-"(ListOpt) A list of backend names to use. These backend names should be "
-"backed by a unique [CONFIG] group with its options"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml34(td)
-msgid "iscsi_helper = tgtadm"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml35(td)
-msgid "(StrOpt) iscsi target user-land tool to use"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml38(td)
-msgid "iscsi_iotype = fileio"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml39(td)
-msgid ""
-"(StrOpt) Sets the behavior of the iSCSI target to either perform blockio or "
-"fileio optionally, auto can be set and Cinder will autodetect type of "
-"backing device"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml42(td)
-msgid "iscsi_ip_address = $my_ip"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml43(td)
-msgid "(StrOpt) The IP address that the iSCSI daemon is listening on"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml46(td)
-msgid "iscsi_num_targets = 100"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml47(td)
-msgid "(IntOpt) The maximum number of iscsi target ids per host"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml50(td)
-msgid "iscsi_port = 3260"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml51(td)
-msgid "(IntOpt) The port that the iSCSI daemon is listening on"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml54(td)
-msgid "iscsi_target_prefix = iqn.2010-10.org.openstack:"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml55(td)
-msgid "(StrOpt) prefix for iscsi volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml58(td)
-msgid "iser_helper = tgtadm"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml59(td)
-msgid "(StrOpt) iser target user-land tool to use"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml62(td)
-msgid "iser_ip_address = $my_ip"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml63(td)
-msgid "(StrOpt) The IP address that the iSER daemon is listening on"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml66(td)
-msgid "iser_num_targets = 100"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml67(td)
-msgid "(IntOpt) The maximum number of iser target ids per host"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml70(td)
-msgid "iser_port = 3260"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml71(td)
-msgid "(IntOpt) The port that the iSER daemon is listening on"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml74(td)
-msgid "iser_target_prefix = iqn.2010-10.org.iser.openstack:"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml75(td)
-msgid "(StrOpt) prefix for iser volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml78(td)
-msgid "max_gigabytes = 10000"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml79(td)
-msgid ""
-"(IntOpt) This configure option has been deprecated along with the "
-"SimpleScheduler. New scheduler is able to gather capacity information for "
-"each host, thus setting the maximum number of volume gigabytes for host is "
-"no longer needed. It's safe to remove this configure from cinder.conf."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml82(td)
-msgid "migration_create_volume_timeout_secs = 300"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml83(td)
-msgid ""
-"(IntOpt) Timeout for creating the volume to migrate to when performing "
-"volume migration (seconds)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml86(td)
-msgid "num_iser_scan_tries = 3"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml87(td)
-msgid ""
-"(IntOpt) The maximum number of times to rescan iSER targetto find volume"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml90(td)
-msgid "num_volume_device_scan_tries = 3"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml91(td)
-msgid "(IntOpt) The maximum number of times to rescan targets to find volume"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml94(td)
-msgid "volume_backend_name = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml95(td)
-msgid "(StrOpt) The backend name for a given driver implementation"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml99(td)
-msgid ""
-"(StrOpt) Method used to wipe old voumes (valid options are: none, zero, "
-"shred)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml102(td)
-msgid "volume_clear_ionice = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml103(td)
-msgid ""
-"(StrOpt) The flag to pass to ionice to alter the i/o priority of the process"
-" used to zero a volume after deletion, for example \"-c3\" for idle only "
-"priority."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml110(td)
-msgid "volume_dd_blocksize = 1M"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml111(td)
-msgid "(StrOpt) The default block size used when copying/clearing volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml114(td)
-msgid "volume_driver = cinder.volume.drivers.lvm.LVMISCSIDriver"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml115(td)
-msgid "(StrOpt) Driver to use for volume creation"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml118(td)
-msgid "volume_manager = cinder.volume.manager.VolumeManager"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml119(td)
-msgid "(StrOpt) full class name for the Manager for volume"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml122(td)
-msgid "volume_service_inithost_offload = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml123(td)
-msgid "(BoolOpt) Offload pending volume delete during volume service startup"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml126(td)
-msgid "volume_usage_audit_period = month"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml127(td)
-msgid ""
-"(StrOpt) time period to generate volume usages for. Time period must be "
-"hour, day, month or year"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml130(td)
-msgid "volumes_dir = $state_path/volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml131(td)
-msgid "(StrOpt) Volume configuration file storage directory"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage.xml145(td)
-msgid "max_pool_size = 5"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nas.xml8(caption)
-msgid "Description of configuration options for nas"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nas.xml22(td)
-msgid "nas_ip ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-nas.xml23(td)
-msgid "(StrOpt) IP address or Hostname of NAS system."
-msgstr ""
-
-#: ./doc/common/tables/cinder-nas.xml26(td)
-msgid "nas_login = admin"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nas.xml27(td)
-msgid "(StrOpt) User name to connect to NAS system."
-msgstr ""
-
-#: ./doc/common/tables/cinder-nas.xml30(td)
-msgid "nas_password ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-nas.xml31(td)
-msgid "(StrOpt) Password to connect to NAS system."
-msgstr ""
-
-#: ./doc/common/tables/cinder-nas.xml34(td)
-msgid "nas_private_key ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-nas.xml35(td)
-msgid "(StrOpt) Filename of private key to use for SSH authentication."
-msgstr ""
-
-#: ./doc/common/tables/cinder-nas.xml38(td)
-msgid "nas_ssh_port = 22"
-msgstr ""
-
-#: ./doc/common/tables/cinder-nas.xml39(td)
-msgid "(IntOpt) SSH port to use to connect to NAS system."
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml8(caption)
-#: ./doc/common/tables/neutron-vpn.xml8(caption)
-msgid "Description of configuration options for vpn"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml22(td)
-msgid "boot_script_template = $pybasedir/nova/cloudpipe/bootscript.template"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml23(td)
-msgid "(StrOpt) Template for cloudpipe instance boot script"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml26(td)
-msgid "dmz_cidr ="
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml27(td)
-msgid "(ListOpt) A list of dmz range that should be accepted"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml30(td)
-msgid "dmz_mask = 255.255.255.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml31(td)
-msgid "(StrOpt) Netmask to push into openvpn config"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml34(td)
-msgid "dmz_net = 10.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml35(td)
-msgid "(StrOpt) Network to push into openvpn config"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml38(td)
-msgid "vpn_flavor = m1.tiny"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml39(td)
-msgid "(StrOpt) Flavor for vpn instances"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml42(td)
-msgid "vpn_image_id = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml43(td)
-msgid "(StrOpt) Image ID used when starting up a cloudpipe vpn server"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml46(td)
-msgid "vpn_ip = $my_ip"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml47(td)
-msgid "(StrOpt) Public IP for the cloudpipe VPN servers"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml50(td)
-msgid "vpn_key_suffix = -vpn"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml51(td)
-msgid "(StrOpt) Suffix to add to project name for vpn key and secgroups"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml54(td)
-msgid "vpn_start = 1000"
-msgstr ""
-
-#: ./doc/common/tables/nova-vpn.xml55(td)
-msgid "(IntOpt) First Vpn port for private networks"
-msgstr ""
-
-#: ./doc/common/tables/nova-wsgi.xml23(td)
-msgid "(StrOpt) File name for the paste.deploy config for nova-api"
-msgstr ""
-
-#: ./doc/common/tables/nova-wsgi.xml26(td)
-#: ./doc/common/tables/cinder-common.xml174(td)
-#: ./doc/common/tables/neutron-ssl.xml22(td)
-msgid "ssl_ca_file = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-wsgi.xml30(td)
-#: ./doc/common/tables/cinder-common.xml178(td)
-#: ./doc/common/tables/neutron-ssl.xml26(td)
-msgid "ssl_cert_file = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-wsgi.xml31(td)
-msgid "(StrOpt) SSL certificate of API server"
-msgstr ""
-
-#: ./doc/common/tables/nova-wsgi.xml34(td)
-#: ./doc/common/tables/cinder-common.xml182(td)
-#: ./doc/common/tables/neutron-ssl.xml30(td)
-msgid "ssl_key_file = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-wsgi.xml35(td)
-msgid "(StrOpt) SSL private key of API server"
-msgstr ""
-
-#: ./doc/common/tables/nova-wsgi.xml42(td)
-msgid "wsgi_default_pool_size = 1000"
-msgstr ""
-
-#: ./doc/common/tables/nova-wsgi.xml43(td)
-msgid "(IntOpt) Size of the pool of greenthreads used by wsgi"
-msgstr ""
-
-#: ./doc/common/tables/nova-wsgi.xml46(td)
-msgid ""
-"wsgi_log_format = %(client_ip)s \"%(request_line)s\" status: %(status_code)s"
-" len: %(body_length)s time: %(wall_seconds).7f"
-msgstr ""
-
-#: ./doc/common/tables/nova-wsgi.xml47(td)
-msgid ""
-"(StrOpt) A python format string that is used as the template to generate log"
-" lines. The following values can be formatted into it: client_ip, date_time,"
-" request_line, status_code, body_length, wall_seconds."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_glusterfs.xml8(caption)
-msgid "Description of configuration options for storage_glusterfs"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_glusterfs.xml23(td)
-msgid "(StrOpt) Base dir containing mount points for gluster shares."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_glusterfs.xml26(td)
-msgid "glusterfs_qcow2_volumes = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_glusterfs.xml27(td)
-msgid "(BoolOpt) Create volumes as QCOW2 files rather than raw files."
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_glusterfs.xml30(td)
-msgid "glusterfs_shares_config = /etc/cinder/glusterfs_shares"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_glusterfs.xml31(td)
-msgid "(StrOpt) File with the list of available gluster shares"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_glusterfs.xml34(td)
-msgid "glusterfs_sparsed_volumes = True"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml7(literal)
-msgid "[realm1]"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml7(literal)
-#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml7(literal)
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml7(literal)
-msgid "container-sync-realms.conf-sample"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml18(td)
-msgid "key = realm1key"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml21(td)
-msgid "key2 = realm1key2"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml24(td)
-msgid "cluster_name1 = https://host1/v1/"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm1.xml27(td)
-msgid "cluster_name2 = https://host2/v1/"
-msgstr ""
-
-#: ./doc/common/tables/nova-availabilityzones.xml8(caption)
-msgid "Description of configuration options for availabilityzones"
-msgstr ""
-
-#: ./doc/common/tables/nova-availabilityzones.xml22(td)
-msgid "default_availability_zone = nova"
-msgstr ""
-
-#: ./doc/common/tables/nova-availabilityzones.xml23(td)
-msgid "(StrOpt) Default compute node availability_zone"
-msgstr ""
-
-#: ./doc/common/tables/nova-availabilityzones.xml26(td)
-msgid "default_schedule_zone = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-availabilityzones.xml27(td)
-msgid "(StrOpt) Availability zone to use when user doesn't specify one"
-msgstr ""
-
-#: ./doc/common/tables/nova-availabilityzones.xml30(td)
-msgid "internal_service_availability_zone = internal"
-msgstr ""
-
-#: ./doc/common/tables/nova-availabilityzones.xml31(td)
-msgid "(StrOpt) The availability_zone to show internal services under"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml7(literal)
-msgid "[filter:container_sync]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml18(td)
-msgid "use = egg:swift#container_sync"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml21(td)
-msgid "allow_full_urls = true"
-msgstr ""
-
-#: ./doc/common/tables/heat-zeromq.xml38(td)
-msgid ""
-"rpc_zmq_matchmaker = "
-"heat.openstack.common.rpc.matchmaker.MatchMakerLocalhost"
-msgstr ""
-
-#: ./doc/common/tables/keystone-memcache.xml8(caption)
-msgid "Description of configuration options for memcache"
-msgstr ""
-
-#: ./doc/common/tables/keystone-memcache.xml19(th)
-#: ./doc/common/tables/swift-memcache-memcache.xml7(literal)
-msgid "[memcache]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-memcache.xml22(td)
-msgid "max_compare_and_set_retry = 16"
-msgstr ""
-
-#: ./doc/common/tables/keystone-memcache.xml23(td)
-msgid ""
-"(IntOpt) Number of compare-and-set attempts to make when using compare-and-"
-"set in the token memcache back end."
-msgstr ""
-
-#: ./doc/common/tables/keystone-memcache.xml26(td)
-msgid "servers = localhost:11211"
-msgstr ""
-
-#: ./doc/common/tables/keystone-memcache.xml27(td)
-msgid "(ListOpt) Memcache servers in the format of \"host:port\""
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml8(caption)
-msgid "Description of configuration options for vnc"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml22(td)
-msgid "novncproxy_base_url = http://127.0.0.1:6080/vnc_auto.html"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml23(td)
-msgid ""
-"(StrOpt) Location of VNC console proxy, in the form "
-"\"http://127.0.0.1:6080/vnc_auto.html\""
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml26(td)
-msgid "vnc_enabled = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml27(td)
-msgid "(BoolOpt) Enable VNC related features"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml30(td)
-msgid "vnc_keymap = en-us"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml31(td)
-msgid "(StrOpt) Keymap for VNC"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml34(td)
-msgid "vncserver_listen = 127.0.0.1"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml35(td)
-msgid "(StrOpt) IP address on which instance vncservers should listen"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml38(td)
-msgid "vncserver_proxyclient_address = 127.0.0.1"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml39(td)
-msgid ""
-"(StrOpt) The address to which proxy clients (like nova-xvpvncproxy) should "
-"connect"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml45(td)
-msgid "vnc_port = 5900"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml46(td)
-msgid "(IntOpt) VNC starting port"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml49(td)
-msgid "vnc_port_total = 10000"
-msgstr ""
-
-#: ./doc/common/tables/nova-vnc.xml50(td)
-msgid "(IntOpt) Total number of VNC ports"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml7(literal)
-msgid "[swift-constraints]"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml7(literal)
-#: ./doc/common/tables/swift-swift-swift-hash.xml7(literal)
-msgid "swift.conf-sample"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml18(td)
-msgid "max_file_size = 5368709122"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml18(td)
-msgid ""
-"The largest normal object that can be saved in the cluster. This is also the"
-" limit on the size of each segment of a large object when using the large "
-"object manifest support. This value is set in bytes. Setting it to lower "
-"than 1MiB will cause some tests to fail. It is STRONGLY recommended to leave"
-" this value at the default (5 * 2**30 + 2)."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml29(td)
-msgid "max_meta_name_length = 128"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml29(td)
-msgid ""
-"The maximum number of bytes in the utf8 encoding of the name portion of a "
-"metadata header."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml34(td)
-msgid "max_meta_value_length = 256"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml34(td)
-msgid "The max number of bytes in the utf8 encoding of a metadata value."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml38(td)
-msgid "max_meta_count = 90"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml38(td)
-msgid ""
-"The maximum number of metadata keys that can be stored on a single account, "
-"container, or object."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml43(td)
-msgid "max_meta_overall_size = 4096"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml43(td)
-msgid ""
-"The maximum number of bytes in the utf8 encoding of the metadata (keys + "
-"values)."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml48(td)
-msgid "max_header_size = 8192"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml48(td)
-msgid "The maximum number of bytes in the utf8 encoding of each header."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml52(td)
-msgid "max_object_name_length = 1024"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml52(td)
-msgid "The maximum number of bytes in the utf8 encoding of an object name."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml56(td)
-msgid "container_listing_limit = 10000"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml56(td)
-msgid ""
-"The default (and maximum) number of items returned for a container listing "
-"request."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml61(td)
-msgid "account_listing_limit = 10000"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml61(td)
-msgid ""
-"The default (and maximum) number of items returned for an account listing "
-"request."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml65(td)
-msgid "max_account_name_length = 256"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml65(td)
-msgid "The maximum number of bytes in the utf8 encoding of an account name."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml69(td)
-msgid "max_container_name_length = 256"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-constraints.xml69(td)
-msgid "The maximum number of bytes in the utf8 encoding of a container name."
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml8(caption)
-msgid "Description of configuration options for cisco"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml19(th)
-msgid "[CISCO]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml22(td)
-msgid ""
-"model_class = "
-"neutron.plugins.cisco.models.virt_phy_sw_v2.VirtualPhysicalSwitchModelV2"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml23(td)
-msgid "(StrOpt) Model Class"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml26(td)
-msgid ""
-"nexus_driver = "
-"neutron.plugins.cisco.test.nexus.fake_nexus_driver.CiscoNEXUSFakeDriver"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml27(td)
-msgid "(StrOpt) Nexus Driver Name"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml30(td)
-msgid "nexus_l3_enable = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml31(td)
-msgid "(BoolOpt) Enable L3 support on the Nexus switches"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml34(td)
-msgid "provider_vlan_auto_create = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml35(td)
-msgid ""
-"(BoolOpt) Provider VLANs are automatically created as needed on the Nexus "
-"switch"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml38(td)
-msgid "provider_vlan_auto_trunk = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml39(td)
-msgid ""
-"(BoolOpt) Provider VLANs are automatically trunked as needed on the ports of"
-" the Nexus switch"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml42(td)
-msgid "provider_vlan_name_prefix = p-"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml43(td)
-msgid "(StrOpt) VLAN Name prefix for provider vlans"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml46(td)
-#: ./doc/common/tables/neutron-cisco.xml122(td)
-msgid "svi_round_robin = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml47(td)
-#: ./doc/common/tables/neutron-cisco.xml123(td)
-msgid "(BoolOpt) Distribute SVI interfaces over all switches"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml50(td)
-#: ./doc/common/tables/neutron-cisco.xml126(td)
-msgid "vlan_name_prefix = q-"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml51(td)
-#: ./doc/common/tables/neutron-cisco.xml127(td)
-msgid "(StrOpt) VLAN Name prefix"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml58(td)
-msgid "(StrOpt) N1K Bridge Mappings"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml61(td)
-msgid "default_network_profile = default_network_profile"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml62(td)
-msgid "(StrOpt) N1K default network profile"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml65(td)
-msgid "default_policy_profile = service_profile"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml66(td)
-msgid "(StrOpt) N1K default policy profile"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml69(td)
-msgid "enable_tunneling = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml70(td)
-msgid "(BoolOpt) N1K Enable Tunneling"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml74(td)
-msgid "(StrOpt) N1K Integration Bridge"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml77(td)
-msgid "network_node_policy_profile = dhcp_pp"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml78(td)
-msgid "(StrOpt) N1K policy profile for network node"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml81(td)
-msgid "network_vlan_ranges = vlan:1:4095"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml82(td)
-msgid "(StrOpt) N1K Network VLAN Ranges"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml85(td)
-msgid "poll_duration = 10"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml86(td)
-msgid "(StrOpt) N1K Policy profile polling duration in seconds"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml90(td)
-msgid "(StrOpt) N1K Tenant Network Type"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml94(td)
-msgid "(StrOpt) N1K Tunnel Bridge"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml97(td)
-msgid "vxlan_id_ranges = 5000:10000"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml98(td)
-msgid "(StrOpt) N1K VXLAN ID Ranges"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml101(th)
-msgid "[CISCO_PLUGINS]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml104(td)
-msgid ""
-"nexus_plugin = neutron.plugins.cisco.nexus.cisco_nexus_plugin_v2.NexusPlugin"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml105(td)
-msgid "(StrOpt) Nexus Switch to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml108(td)
-msgid ""
-"vswitch_plugin = "
-"neutron.plugins.openvswitch.ovs_neutron_plugin.OVSNeutronPluginV2"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml109(td)
-msgid "(StrOpt) Virtual Switch to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml112(th)
-msgid "[cisco_csr_ipsec]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml115(td)
-msgid "status_check_interval = 60"
-msgstr ""
-
-#: ./doc/common/tables/neutron-cisco.xml116(td)
-msgid "(IntOpt) Status check interval for Cisco CSR IPSec connections"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml8(caption)
-msgid "Description of configuration options for hyperv"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml22(td)
-msgid "dynamic_memory_ratio = 1.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml23(td)
-msgid ""
-"(FloatOpt) Enables dynamic memory allocation (ballooning) when set to a "
-"value greater than 1. The value expresses the ratio between the total RAM "
-"assigned to an instance and its startup RAM amount. For example a ratio of "
-"2.0 for an instance with 1024MB of RAM implies 512MB of RAM allocated at "
-"startup"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml26(td)
-msgid "enable_instance_metrics_collection = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml27(td)
-msgid ""
-"(BoolOpt) Enables metrics collections for an instance by using Hyper-V's "
-"metric APIs. Collected data can by retrieved by other apps and services, "
-"e.g.: Ceilometer. Requires Hyper-V / Windows Server 2012 and above"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml34(td)
-msgid "instances_path_share ="
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml35(td)
-msgid ""
-"(StrOpt) The name of a Windows share name mapped to the \"instances_path\" "
-"dir and used by the resize feature to copy files to the target host. If left"
-" blank, an administrative share will be used, looking for the same "
-"\"instances_path\" used locally"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml38(td)
-msgid "limit_cpu_features = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml39(td)
-msgid ""
-"(BoolOpt) Required for live migration among hosts with different CPU "
-"features"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml42(td)
-msgid "mounted_disk_query_retry_count = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml43(td)
-msgid ""
-"(IntOpt) The number of times to retry checking for a disk mounted via iSCSI."
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml46(td)
-msgid "mounted_disk_query_retry_interval = 5"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml47(td)
-msgid "(IntOpt) Interval between checks for a mounted iSCSI disk, in seconds."
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml50(td)
-msgid "qemu_img_cmd = qemu-img.exe"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml51(td)
-msgid ""
-"(StrOpt) Path of qemu-img command which is used to convert between different"
-" image types"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml54(td)
-msgid "vswitch_name = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-hyperv.xml55(td)
-msgid ""
-"(StrOpt) External virtual switch Name, if not provided, the first external "
-"virtual switch is used"
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml8(caption)
-msgid "Description of configuration options for l3_agent"
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml22(td)
-msgid "enable_metadata_proxy = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml23(td)
-msgid "(BoolOpt) Allow running metadata proxy."
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml26(td)
-msgid "external_network_bridge = br-ex"
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml27(td)
-msgid "(StrOpt) Name of bridge used for external network traffic."
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml30(td)
-msgid "gateway_external_network_id ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml31(td)
-msgid ""
-"(StrOpt) UUID of external network for routers implemented by the agents."
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml34(td)
-msgid "handle_internal_only_routers = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml35(td)
-msgid "(BoolOpt) Agent should implement routers with no gateway"
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml38(td)
-msgid "router_id ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml39(td)
-msgid ""
-"(StrOpt) If namespaces is disabled, the l3 agent can only configure a router"
-" that has the matching router ID."
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml42(td)
-msgid "send_arp_for_ha = 0"
-msgstr ""
-
-#: ./doc/common/tables/neutron-l3_agent.xml43(td)
-msgid ""
-"(IntOpt) Send this many gratuitous ARPs for HA setup, if less than or equal "
-"to 0, the feature is disabled"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-filter-recon.xml24(td)
-msgid "recon_lock_path = /var/lock"
-msgstr ""
-
-#: ./doc/common/tables/cinder-coraid.xml8(caption)
-msgid "Description of configuration options for coraid"
-msgstr ""
-
-#: ./doc/common/tables/cinder-coraid.xml22(td)
-msgid "coraid_esm_address ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-coraid.xml23(td)
-msgid "(StrOpt) IP address of Coraid ESM"
-msgstr ""
-
-#: ./doc/common/tables/cinder-coraid.xml26(td)
-msgid "coraid_group = admin"
-msgstr ""
-
-#: ./doc/common/tables/cinder-coraid.xml27(td)
-msgid ""
-"(StrOpt) Name of group on Coraid ESM to which coraid_user belongs (must have"
-" admin privilege)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-coraid.xml30(td)
-msgid "coraid_password = password"
-msgstr ""
-
-#: ./doc/common/tables/cinder-coraid.xml31(td)
-msgid "(StrOpt) Password to connect to Coraid ESM"
-msgstr ""
-
-#: ./doc/common/tables/cinder-coraid.xml34(td)
-msgid "coraid_repository_key = coraid_repository"
-msgstr ""
-
-#: ./doc/common/tables/cinder-coraid.xml35(td)
-msgid "(StrOpt) Volume Type key name to store ESM Repository Name"
-msgstr ""
-
-#: ./doc/common/tables/cinder-coraid.xml38(td)
-msgid "coraid_user = admin"
-msgstr ""
-
-#: ./doc/common/tables/cinder-coraid.xml39(td)
-msgid "(StrOpt) User name to connect to Coraid ESM"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-auditor.xml7(literal)
-msgid "[container-auditor]"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-auditor.xml18(td)
-msgid "log_name = container-auditor"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-auditor.xml33(td)
-msgid "containers_per_second = 200"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-server-container-auditor.xml33(td)
-msgid ""
-"Maximum containers audited per second. Should be tuned according to "
-"individual system specs. 0 is unlimited. mounted to prevent accidentally "
-"writing to the root device process simultaneously (it will actually "
-"accept(2) N + 1). Setting this to one (1) will only handle one request at a "
-"time, without accepting another request concurrently. By increasing the "
-"number of workers to a much higher value, one can reduce the impact of slow "
-"file system operations in one request from negatively impacting other "
-"requests."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-catch_errors.xml21(td)
-msgid "set log_name = catch_errors"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml23(td)
-msgid ""
-"(IntOpt) The number of times we retry on failures, e.g., socket error, etc."
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml26(td)
-msgid "cluster_name = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml27(td)
-msgid ""
-"(MultiStrOpt) Name of a VMware Cluster ComputeResource. Used only if "
-"compute_driver is vmwareapi.VMwareVCDriver."
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml30(td)
-msgid "datastore_regex = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml31(td)
-msgid "(StrOpt) Regex to match the name of a datastore."
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml34(td)
-msgid "host_ip = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml35(td)
-msgid "(StrOpt) Hostname or IP address for connection to VMware ESX/VC host."
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml38(td)
-msgid "host_password = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml39(td)
-msgid "(StrOpt) Password for connection to VMware ESX/VC host."
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml42(td)
-msgid "host_username = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml43(td)
-msgid "(StrOpt) Username for connection to VMware ESX/VC host."
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml47(td)
-msgid "(StrOpt) Name of Integration Bridge"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml50(td)
-msgid "maximum_objects = 100"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml51(td)
-msgid ""
-"(IntOpt) The maximum number of ObjectContent data objects that should be "
-"returned in a single result. A positive value will cause the operation to "
-"suspend the retrieval when the count of objects reaches the specified "
-"maximum. The server may still limit the count to something less than the "
-"configured value. Any remaining objects may be retrieved with additional "
-"requests."
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml55(td)
-msgid "(FloatOpt) The interval used for polling of remote tasks."
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml58(td)
-msgid "use_linked_clone = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml59(td)
-msgid "(BoolOpt) Whether to use linked clone"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml62(td)
-msgid "wsdl_location = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-vmware.xml63(td)
-msgid ""
-"(StrOpt) Optional VIM Service WSDL Location e.g "
-"http://&lt;server&gt;/vimService.wsdl. Optional over-ride to default "
-"location for bug work-arounds"
-msgstr ""
-
-#: ./doc/common/tables/nova-logging.xml26(td)
-msgid ""
-"default_log_levels = amqp=WARN, amqplib=WARN, boto=WARN, qpid=WARN, "
-"sqlalchemy=WARN, suds=INFO, oslo.messaging=INFO, iso8601=WARN"
-msgstr ""
-
-#: ./doc/common/tables/nova-logging.xml34(td)
-#: ./doc/common/tables/cinder-common.xml54(td)
-msgid "fatal_exception_format_errors = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-logging.xml35(td)
-msgid "(BoolOpt) Make exception message format errors fatal"
-msgstr ""
-
-#: ./doc/common/tables/nova-logging.xml66(td)
-msgid ""
-"logging_context_format_string = %(asctime)s.%(msecs)03d %(process)d "
-"%(levelname)s %(name)s [%(request_id)s %(user)s %(tenant)s] "
-"%(instance)s%(message)s"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml8(caption)
-msgid "Description of configuration options for xen"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml22(td)
-msgid "console_driver = nova.console.xvp.XVPConsoleProxy"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml23(td)
-msgid "(StrOpt) Driver to use for the console proxy"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml26(td)
-msgid "console_vmrc_error_retries = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml27(td)
-msgid "(IntOpt) Number of retries for retrieving VMRC information"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml30(td)
-msgid "console_vmrc_port = 443"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml31(td)
-msgid "(IntOpt) Port for VMware VMRC connections"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml34(td)
-msgid "console_xvp_conf = /etc/xvp.conf"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml35(td)
-msgid "(StrOpt) Generated XVP conf file"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml38(td)
-msgid "console_xvp_conf_template = $pybasedir/nova/console/xvp.conf.template"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml39(td)
-msgid "(StrOpt) XVP conf template"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml42(td)
-msgid "console_xvp_log = /var/log/xvp.log"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml43(td)
-msgid "(StrOpt) XVP log file"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml46(td)
-msgid "console_xvp_multiplex_port = 5900"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml47(td)
-msgid "(IntOpt) Port for XVP to multiplex VNC connections on"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml50(td)
-msgid "console_xvp_pid = /var/run/xvp.pid"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml51(td)
-msgid "(StrOpt) XVP master process pid file"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml54(td)
-msgid "stub_compute = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml55(td)
-msgid "(BoolOpt) Stub calls to compute worker for tests"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml61(td)
-msgid "xen_hvmloader_path = /usr/lib/xen/boot/hvmloader"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml62(td)
-msgid "(StrOpt) Location where the Xen hvmloader is kept"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml68(td)
-msgid "agent_path = usr/sbin/xe-update-networking"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml69(td)
-msgid ""
-"(StrOpt) Specifies the path in which the XenAPI guest agent should be "
-"located. If the agent is present, network configuration is not injected into"
-" the image. Used if compute_driver=xenapi.XenAPIDriver and "
-"flat_injected=True"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml72(td)
-msgid "agent_resetnetwork_timeout = 60"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml73(td)
-msgid ""
-"(IntOpt) Number of seconds to wait for agent reply to resetnetwork request"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml76(td)
-msgid "agent_timeout = 30"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml77(td)
-msgid "(IntOpt) Number of seconds to wait for agent reply"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml80(td)
-msgid "agent_version_timeout = 300"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml81(td)
-msgid "(IntOpt) Number of seconds to wait for agent to be fully operational"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml84(td)
-msgid "cache_images = all"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml85(td)
-msgid ""
-"(StrOpt) Cache glance images locally. `all` will cache all images, `some` "
-"will only cache images that have the image_property `cache_in_nova=True`, "
-"and `none` turns off caching entirely"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml88(td)
-msgid "check_host = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml89(td)
-msgid ""
-"(BoolOpt) Ensure compute service is running on host XenAPI connects to."
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml92(td)
-msgid "connection_concurrent = 5"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml93(td)
-msgid ""
-"(IntOpt) Maximum number of concurrent XenAPI connections. Used only if "
-"compute_driver=xenapi.XenAPIDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml96(td)
-msgid "connection_password = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml97(td)
-msgid ""
-"(StrOpt) Password for connection to XenServer/Xen Cloud Platform. Used only "
-"if compute_driver=xenapi.XenAPIDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml100(td)
-msgid "connection_url = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml101(td)
-msgid ""
-"(StrOpt) URL for connection to XenServer/Xen Cloud Platform. A special value"
-" of unix://local can be used to connect to the local unix socket. Required "
-"if compute_driver=xenapi.XenAPIDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml104(td)
-msgid "connection_username = root"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml105(td)
-msgid ""
-"(StrOpt) Username for connection to XenServer/Xen Cloud Platform. Used only "
-"if compute_driver=xenapi.XenAPIDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml108(td)
-msgid "default_os_type = linux"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml109(td)
-msgid "(StrOpt) Default OS type"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml112(td)
-msgid "disable_agent = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml113(td)
-msgid ""
-"(BoolOpt) Disables the use of the XenAPI agent in any image regardless of "
-"what image properties are present."
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml116(td)
-msgid "image_compression_level = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml117(td)
-msgid ""
-"(IntOpt) Compression level for images, e.g., 9 for gzip -9. Range is 1-9, 9 "
-"being most compressed but most CPU intensive on dom0."
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml120(td)
-msgid "image_upload_handler = nova.virt.xenapi.image.glance.GlanceStore"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml121(td)
-msgid "(StrOpt) Dom0 plugin driver used to handle image uploads."
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml124(td)
-msgid "introduce_vdi_retry_wait = 20"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml125(td)
-msgid ""
-"(IntOpt) Number of seconds to wait for an SR to settle if the VDI does not "
-"exist when first introduced"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml128(td)
-msgid "ipxe_boot_menu_url = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml129(td)
-msgid "(StrOpt) URL to the iPXE boot menu"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml132(td)
-msgid "ipxe_mkisofs_cmd = mkisofs"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml133(td)
-#: ./doc/common/tables/nova-configdrive.xml39(td)
-msgid ""
-"(StrOpt) Name and optionally path of the tool used for ISO image creation"
-msgstr "(文字列オプション) ISO イメージの作成に使用するツールの名前と (任意で) パス"
-
-#: ./doc/common/tables/nova-xen.xml136(td)
-msgid "ipxe_network_name = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml137(td)
-msgid "(StrOpt) Name of network to use for booting iPXE ISOs"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml140(td)
-msgid "iqn_prefix = iqn.2010-10.org.openstack"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml141(td)
-msgid "(StrOpt) IQN Prefix"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml144(td)
-msgid "login_timeout = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml145(td)
-msgid "(IntOpt) Timeout in seconds for XenAPI login."
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml148(td)
-msgid "max_kernel_ramdisk_size = 16777216"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml149(td)
-msgid "(IntOpt) Maximum size in bytes of kernel or ramdisk images"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml152(td)
-msgid "num_vbd_unplug_retries = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml153(td)
-msgid "(IntOpt) Maximum number of retries to unplug VBD"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml156(td)
-msgid "ovs_integration_bridge = xapi1"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml160(td)
-msgid "remap_vbd_dev = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml161(td)
-msgid ""
-"(BoolOpt) Used to enable the remapping of VBD dev (Works around an issue in "
-"Ubuntu Maverick)"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml164(td)
-msgid "remap_vbd_dev_prefix = sd"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml165(td)
-msgid ""
-"(StrOpt) Specify prefix to remap VBD dev to (ex. /dev/xvdb -&gt; /dev/sdb)"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml168(td)
-msgid "running_timeout = 60"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml169(td)
-msgid "(IntOpt) Number of seconds to wait for instance to go to running state"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml172(td)
-msgid "sparse_copy = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml173(td)
-msgid ""
-"(BoolOpt) Whether to use sparse_copy for copying data on a resize down "
-"(False will use standard dd). This speeds up resizes down considerably since"
-" large runs of zeros won't have to be rsynced"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml176(td)
-msgid "sr_base_path = /var/run/sr-mount"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml177(td)
-#: ./doc/common/tables/cinder-storage_xen.xml43(td)
-msgid "(StrOpt) Base path to the storage repository"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml180(td)
-msgid "sr_matching_filter = default-sr:true"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml181(td)
-msgid ""
-"(StrOpt) Filter for finding the SR to be used to install guest instances on."
-" To use the Local Storage in default XenServer/XCP installations set this "
-"flag to other-config:i18n-key=local-storage. To select an SR with a "
-"different matching criteria, you could set it to other-"
-"config:my_favorite_sr=true. On the other hand, to fall back on the Default "
-"SR, as displayed by XenCenter, set this flag to: default-sr:true"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml184(td)
-msgid "target_host = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml185(td)
-msgid "(StrOpt) The iSCSI Target Host"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml188(td)
-msgid "target_port = 3260"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml189(td)
-msgid "(StrOpt) The iSCSI Target Port, default is port 3260"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml192(td)
-msgid "torrent_base_url = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml193(td)
-msgid "(StrOpt) Base URL for torrent files."
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml196(td)
-msgid "torrent_download_stall_cutoff = 600"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml197(td)
-msgid ""
-"(IntOpt) Number of seconds a download can remain at the same progress "
-"percentage w/o being considered a stall"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml200(td)
-msgid "torrent_images = none"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml201(td)
-msgid ""
-"(StrOpt) Whether or not to download images via Bit Torrent (all|some|none)."
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml204(td)
-msgid "torrent_listen_port_end = 6891"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml205(td)
-msgid "(IntOpt) End of port range to listen on"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml208(td)
-msgid "torrent_listen_port_start = 6881"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml209(td)
-msgid "(IntOpt) Beginning of port range to listen on"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml212(td)
-msgid "torrent_max_last_accessed = 86400"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml213(td)
-msgid ""
-"(IntOpt) Cached torrent files not accessed within this number of seconds can"
-" be reaped"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml216(td)
-msgid "torrent_max_seeder_processes_per_host = 1"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml217(td)
-msgid ""
-"(IntOpt) Maximum number of seeder processes to run concurrently within a "
-"given dom0. (-1 = no limit)"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml220(td)
-msgid "torrent_seed_chance = 1.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml221(td)
-msgid "(FloatOpt) Probability that peer will become a seeder. (1.0 = 100%)"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml224(td)
-msgid "torrent_seed_duration = 3600"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml225(td)
-msgid ""
-"(IntOpt) Number of seconds after downloading an image via BitTorrent that it"
-" should be seeded for other peers."
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml228(td)
-msgid "use_agent_default = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml229(td)
-msgid ""
-"(BoolOpt) Determines if the XenAPI agent should be used when the image used "
-"does not contain a hint to declare if the agent is present or not. The hint "
-"is a glance property \"xenapi_use_agent\" that has the value \"True\" or "
-"\"False\". Note that waiting for the agent when it is not present will "
-"significantly increase server boot times."
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml232(td)
-msgid "use_join_force = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml233(td)
-msgid "(BoolOpt) To use for hosts with different CPUs"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml236(td)
-msgid "vhd_coalesce_max_attempts = 20"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml237(td)
-msgid ""
-"(IntOpt) Max number of times to poll for VHD to coalesce. Used only if "
-"compute_driver=xenapi.XenAPIDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml240(td)
-msgid "vhd_coalesce_poll_interval = 5.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-xen.xml241(td)
-msgid ""
-"(FloatOpt) The interval used for polling of coalescing vhds. Used only if "
-"compute_driver=xenapi.XenAPIDriver"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml8(caption)
-msgid "Description of configuration options for collector"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml22(td)
-msgid "collector_workers = 1"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml23(td)
-msgid ""
-"(IntOpt) Number of workers for collector service. A single collector is "
-"enabled by default."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml26(th)
-msgid "[collector]"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml29(td)
-msgid "udp_address = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml30(td)
-msgid ""
-"(StrOpt) Address to which the UDP socket is bound. Set to an empty string to"
-" disable."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml33(td)
-msgid "udp_port = 4952"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml34(td)
-msgid "(IntOpt) Port to which the UDP socket is bound."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml37(th)
-msgid "[dispatcher_file]"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml40(td)
-msgid "backup_count = 0"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml41(td)
-msgid "(IntOpt) The max number of the files to keep."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml44(td)
-msgid "file_path = None"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml45(td)
-msgid "(StrOpt) Name and the location of the file to record meters."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml48(td)
-msgid "max_bytes = 0"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-collector.xml49(td)
-msgid "(IntOpt) The max size of the file."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml7(literal)
-msgid "[filter:list-endpoints]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml18(td)
-msgid "use = egg:swift#list_endpoints"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml21(td)
-msgid "list_endpoints_path = /endpoints/"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml22(td)
-msgid "keystone_ec2_cafile = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml23(td)
-msgid ""
-"(StrOpt) A PEM encoded certificate authority to use when verifying HTTPS "
-"connections. Defaults to the system CAs."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml26(td)
-msgid "keystone_ec2_certfile = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml27(td)
-msgid ""
-"(StrOpt) Client certificate key filename. Required if EC2 server requires "
-"client certificate."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml30(td)
-msgid "keystone_ec2_insecure = False"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml31(td)
-msgid "(BoolOpt) Disable SSL certificate verification."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml34(td)
-msgid "keystone_ec2_keyfile = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml35(td)
-msgid "(StrOpt) Required if EC2 server requires client certificate."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml42(th)
-msgid "[ec2]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml45(td)
-msgid "driver = keystone.contrib.ec2.backends.kvs.Ec2"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ec2.xml46(td)
-msgid "(StrOpt) Keystone EC2Credential backend driver."
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml8(caption)
-#: ./doc/common/tables/ceilometer-auth.xml8(caption)
-#: ./doc/common/tables/cinder-auth.xml8(caption)
-msgid "Description of configuration options for auth"
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml19(th)
-msgid "[auth]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml22(td)
-msgid "external = keystone.auth.plugins.external.DefaultDomain"
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml23(td)
-msgid "(StrOpt) The external (REMOTE_USER) auth plugin module."
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml26(td)
-msgid "methods = external, password, token"
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml27(td)
-msgid "(ListOpt) Default auth methods."
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml30(td)
-msgid "password = keystone.auth.plugins.password.Password"
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml31(td)
-msgid "(StrOpt) The password auth plugin module."
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml34(td)
-msgid "token = keystone.auth.plugins.token.Token"
-msgstr ""
-
-#: ./doc/common/tables/keystone-auth.xml35(td)
-msgid "(StrOpt) The token auth plugin module."
-msgstr ""
-
-#: ./doc/common/tables/swift-memcache-memcache.xml7(literal)
-msgid "memcache.conf-sample"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml7(literal)
-msgid "[filter:keystoneauth]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml18(td)
-msgid "use = egg:swift#keystoneauth"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml21(td)
-msgid "operator_roles = admin, swiftoperator"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-keystoneauth.xml24(td)
-msgid "reseller_admin_role = ResellerAdmin"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2.xml8(caption)
-msgid "Description of configuration options for ml2"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2.xml19(th)
-msgid "[ml2]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2.xml22(td)
-msgid "mechanism_drivers ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2.xml23(td)
-msgid ""
-"(ListOpt) An ordered list of networking mechanism driver entrypoints to be "
-"loaded from the neutron.ml2.mechanism_drivers namespace."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2.xml26(td)
-msgid "tenant_network_types = local"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2.xml27(td)
-msgid ""
-"(ListOpt) Ordered list of network_types to allocate as tenant networks."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2.xml30(td)
-msgid "type_drivers = local, flat, vlan, gre, vxlan"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2.xml31(td)
-msgid ""
-"(ListOpt) List of network type driver entrypoints to be loaded from the "
-"neutron.ml2.type_drivers namespace."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml23(td)
-msgid "(BoolOpt) Deploy the deprecated v1 API."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml27(td)
-msgid "(IntOpt) The maximum body size per request, in bytes"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml30(td)
-msgid "pipeline_cfg_file = pipeline.yaml"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml31(td)
-msgid "(StrOpt) Configuration file for pipeline definition."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml35(td)
-#: ./doc/common/tables/heat-api.xml43(td)
-#: ./doc/common/tables/keystone-policy.xml23(td)
-msgid "(StrOpt) Rule enforced when requested rule is not found"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml39(td)
-#: ./doc/common/tables/heat-api.xml47(td)
-#: ./doc/common/tables/keystone-policy.xml27(td)
-msgid "(StrOpt) JSON file containing policy"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml42(td)
-msgid "reserved_metadata_length = 256"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml43(td)
-msgid "(IntOpt) Limit on length of reserved metadata values."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml46(td)
-msgid "reserved_metadata_namespace = metering."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml47(td)
-msgid "(ListOpt) List of metadata prefixes reserved for metering use."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml50(th)
-msgid "[api]"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml53(td)
-#: ./doc/common/tables/trove-rpc.xml26(td)
-msgid "host = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml54(td)
-msgid "(StrOpt) The listen IP for the ceilometer API server."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml57(td)
-msgid "port = 8777"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-api.xml58(td)
-msgid "(IntOpt) The port for the ceilometer API server."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_trove.xml8(caption)
-msgid "Description of configuration options for clients_trove"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_trove.xml19(th)
-msgid "[clients_trove]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml7(literal)
-msgid "[filter:gatekeeper]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml18(td)
-msgid "use = egg:swift#gatekeeper"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-gatekeeper.xml21(td)
-msgid "set log_name = gatekeeper"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml8(caption)
-msgid "Description of configuration options for netapp_7mode_nfs"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml22(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml22(td)
-msgid "expiry_thres_minutes = 720"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml23(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml23(td)
-msgid ""
-"(IntOpt) This option specifies the threshold for last access time for images"
-" in the NFS image cache. When a cache cleaning cycle begins, images in the "
-"cache that have not been accessed in the last M minutes, where M is the "
-"value of this parameter, will be deleted from the cache to create free space"
-" on the NFS share."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml54(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml62(td)
-msgid "thres_avl_size_perc_start = 20"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml55(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml63(td)
-msgid ""
-"(IntOpt) If the percentage of available space for an NFS share has dropped "
-"below the value specified by this option, the NFS image cache will be "
-"cleaned."
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml58(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml66(td)
-msgid "thres_avl_size_perc_stop = 60"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_7mode_nfs.xml59(td)
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml67(td)
-msgid ""
-"(IntOpt) When the percentage of available space on an NFS share has reached "
-"the percentage specified by this option, the driver will stop clearing files"
-" from the NFS image cache that have not been accessed in the last M minutes,"
-" where M is the value of the expiry_thres_minutes configuration option."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml22(td)
-msgid "allow_additional_image_properties = True"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml23(td)
-msgid ""
-"(BoolOpt) Whether to allow users to specify image properties beyond what the"
-" image schema provides"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml26(td)
-msgid "api_limit_max = 1000"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml27(td)
-msgid ""
-"(IntOpt) Maximum permissible number of items that could be returned by a "
-"request"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml31(td)
-msgid ""
-"(IntOpt) The backlog value that will be used when creating the TCP listener "
-"socket."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml38(td)
-msgid "bind_port = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml42(td)
-msgid "data_api = glance.db.sqlalchemy.api"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml43(td)
-msgid "(StrOpt) Python module path of data access API"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml50(td)
-msgid "image_location_quota = 10"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml51(td)
-msgid ""
-"(IntOpt) Maximum number of locations allowed on an image. Negative values "
-"evaluate to unlimited."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml54(td)
-msgid "image_member_quota = 128"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml55(td)
-msgid ""
-"(IntOpt) Maximum number of image members per image. Negative values evaluate"
-" to unlimited."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml58(td)
-msgid "image_property_quota = 128"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml59(td)
-msgid ""
-"(IntOpt) Maximum number of properties allowed on an image. Negative values "
-"evaluate to unlimited."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml62(td)
-msgid "image_tag_quota = 128"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml63(td)
-msgid ""
-"(IntOpt) Maximum number of tags allowed on an image. Negative values "
-"evaluate to unlimited."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml66(td)
-msgid "limit_param_default = 25"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml67(td)
-msgid ""
-"(IntOpt) Default value for the number of items returned by a request if not "
-"specified explicitly in the request"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml74(td)
-msgid "metadata_encryption_key = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml75(td)
-msgid ""
-"(StrOpt) Key used for encrypting sensitive metadata while talking to the "
-"registry or database."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml78(td)
-msgid "notifier_strategy = default"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml79(td)
-msgid ""
-"(StrOpt) Notifications can be sent when images are create, updated or "
-"deleted. There are three methods of sending notifications, logging (via the "
-"log_file directive), rabbit (via a rabbitmq queue), qpid (via a Qpid message"
-" queue), or noop (no notifications sent, the default). (DEPRECATED)"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml83(td)
-msgid "(StrOpt) Region name of this node."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml86(td)
-msgid "property_protection_file = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml87(td)
-msgid "(StrOpt) The location of the property protection file."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml90(td)
-msgid "property_protection_rule_format = roles"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml91(td)
-msgid ""
-"(StrOpt) This config value indicates whether \"roles\" or \"policies\" are "
-"used in the property protection file."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml94(td)
-msgid "show_image_direct_url = False"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml95(td)
-msgid ""
-"(BoolOpt) Whether to include the backend image storage location in image "
-"properties. Revealing storage location can be a security risk, so use this "
-"setting with caution!"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml98(td)
-msgid "user_storage_quota = 0"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml99(td)
-msgid ""
-"(IntOpt) Set a system wide quota for every user. This value is the total "
-"number of bytes that a user can use across all storage systems. A value of 0"
-" means unlimited."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml102(td)
-msgid "workers = 1"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml103(td)
-msgid ""
-"(IntOpt) The number of child process workers that will be created to service"
-" API requests."
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml106(th)
-msgid "[image_format]"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml109(td)
-msgid "container_formats = ami, ari, aki, bare, ovf, ova"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml110(td)
-msgid "(ListOpt) Supported values for the 'container_format' image attribute"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml113(td)
-msgid "disk_formats = ami, ari, aki, vhd, vmdk, raw, qcow2, vdi, iso"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml114(td)
-msgid "(ListOpt) Supported values for the 'disk_format' image attribute"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml117(th)
-msgid "[task]"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml120(td)
-msgid "task_time_to_live = 48"
-msgstr ""
-
-#: ./doc/common/tables/glance-common.xml121(td)
-msgid ""
-"(IntOpt) Time in hours for which a task lives after, either succeeding or "
-"failing"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml8(caption)
-msgid "Description of configuration options for network"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml22(td)
-msgid "allow_same_net_traffic = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml23(td)
-msgid "(BoolOpt) Whether to allow network traffic from same network"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml26(td)
-msgid "auto_assign_floating_ip = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml27(td)
-msgid "(BoolOpt) Autoassigning floating IP to VM"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml30(td)
-msgid "cnt_vpn_clients = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml31(td)
-msgid "(IntOpt) Number of addresses reserved for vpn clients"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml34(td)
-msgid "create_unique_mac_address_attempts = 5"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml35(td)
-msgid "(IntOpt) Number of attempts to create unique mac address"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml38(td)
-msgid "default_access_ip_network_name = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml39(td)
-msgid "(StrOpt) Name of network to use to set access IPs for instances"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml42(td)
-msgid "default_floating_pool = nova"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml43(td)
-msgid "(StrOpt) Default pool for floating IPs"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml46(td)
-msgid "defer_iptables_apply = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml47(td)
-msgid ""
-"(BoolOpt) Whether to batch up the application of IPTables rules during a "
-"host restart and apply all at the end of the init phase"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml50(td)
-msgid "dhcp_domain = novalocal"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml54(td)
-msgid "dhcp_lease_time = 120"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml55(td)
-msgid "(IntOpt) Lifetime of a DHCP lease in seconds"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml58(td)
-msgid "dhcpbridge = $bindir/nova-dhcpbridge"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml59(td)
-msgid "(StrOpt) Location of nova-dhcpbridge"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml62(td)
-msgid "dhcpbridge_flagfile = ['/etc/nova/nova-dhcpbridge.conf']"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml63(td)
-msgid "(MultiStrOpt) Location of flagfiles for dhcpbridge"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml66(td)
-msgid "dns_server = []"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml67(td)
-msgid ""
-"(MultiStrOpt) If set, uses specific DNS server for dnsmasq. Can be specified"
-" multiple times."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml70(td)
-msgid "dns_update_periodic_interval = -1"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml71(td)
-msgid ""
-"(IntOpt) Number of seconds to wait between runs of updates to DNS entries."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml79(td)
-msgid ""
-"(StrOpt) Firewall driver (defaults to hypervisor specific iptables driver)"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml82(td)
-msgid "fixed_ip_disassociate_timeout = 600"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml83(td)
-msgid "(IntOpt) Seconds after which a deallocated IP is disassociated"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml86(td)
-msgid "flat_injected = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml87(td)
-msgid "(BoolOpt) Whether to attempt to inject network setup into guest"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml90(td)
-msgid "flat_interface = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml91(td)
-msgid "(StrOpt) FlatDhcp will bridge into this interface if set"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml94(td)
-msgid "flat_network_bridge = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml95(td)
-msgid "(StrOpt) Bridge for simple network instances"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml98(td)
-msgid "flat_network_dns = 8.8.4.4"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml99(td)
-msgid "(StrOpt) DNS server for simple network"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml102(td)
-msgid "floating_ip_dns_manager = nova.network.noop_dns_driver.NoopDNSDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml103(td)
-msgid "(StrOpt) Full class name for the DNS Manager for floating IPs"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml106(td)
-msgid "force_dhcp_release = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml107(td)
-msgid "(BoolOpt) If True, send a dhcp release on instance termination"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml110(td)
-msgid "force_snat_range = []"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml111(td)
-msgid ""
-"(MultiStrOpt) Traffic to this range will always be snatted to the fallback "
-"ip, even if it would normally be bridged out of the node. Can be specified "
-"multiple times."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml114(td)
-msgid "forward_bridge_interface = ['all']"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml115(td)
-msgid ""
-"(MultiStrOpt) An interface that bridges can forward to. If this is set to "
-"all then all traffic will be forwarded. Can be specified multiple times."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml118(td)
-msgid "gateway = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml119(td)
-msgid "(StrOpt) Default IPv4 gateway"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml122(td)
-msgid "injected_network_template = $pybasedir/nova/virt/interfaces.template"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml123(td)
-msgid "(StrOpt) Template file for injected network"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml126(td)
-msgid "instance_dns_domain ="
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml127(td)
-msgid "(StrOpt) Full class name for the DNS Zone for instance IPs"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml130(td)
-msgid "instance_dns_manager = nova.network.noop_dns_driver.NoopDNSDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml131(td)
-msgid "(StrOpt) Full class name for the DNS Manager for instance IPs"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml134(td)
-msgid "iptables_bottom_regex ="
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml135(td)
-msgid ""
-"(StrOpt) Regular expression to match iptables rule that should always be on "
-"the bottom."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml138(td)
-msgid "iptables_drop_action = DROP"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml139(td)
-msgid ""
-"(StrOpt) The table that iptables to jump to when a packet is to be dropped."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml142(td)
-msgid "iptables_top_regex ="
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml143(td)
-msgid ""
-"(StrOpt) Regular expression to match iptables rule that should always be on "
-"the top."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml146(td)
-msgid "l3_lib = nova.network.l3.LinuxNetL3"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml147(td)
-msgid "(StrOpt) Indicates underlying L3 management library"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml150(td)
-msgid ""
-"linuxnet_interface_driver = "
-"nova.network.linux_net.LinuxBridgeInterfaceDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml151(td)
-msgid "(StrOpt) Driver used to create ethernet devices."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml154(td)
-msgid "linuxnet_ovs_integration_bridge = br-int"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml155(td)
-msgid "(StrOpt) Name of Open vSwitch bridge used with linuxnet"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml158(td)
-msgid "multi_host = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml159(td)
-msgid ""
-"(BoolOpt) Default value for multi_host in networks. Also, if set, some rpc "
-"network calls will be sent directly to host."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml162(td)
-msgid "network_allocate_retries = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml163(td)
-msgid "(IntOpt) Number of times to retry network allocation on failures"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml166(td)
-msgid "network_api_class = nova.network.api.API"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml167(td)
-msgid "(StrOpt) The full class name of the network API class to use"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml170(td)
-#: ./doc/common/tables/neutron-agent.xml26(td)
-msgid "network_device_mtu = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml171(td)
-msgid "(IntOpt) MTU setting for network interface"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml174(td)
-msgid "network_driver = nova.network.linux_net"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml175(td)
-msgid "(StrOpt) Driver to use for network creation"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml178(td)
-msgid "network_manager = nova.network.manager.VlanManager"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml179(td)
-msgid "(StrOpt) Full class name for the Manager for network"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml182(td)
-msgid "network_size = 256"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml183(td)
-msgid "(IntOpt) Number of addresses in each private subnet"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml186(td)
-msgid "network_topic = network"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml187(td)
-msgid "(StrOpt) The topic network nodes listen on"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml190(td)
-msgid "networks_path = $state_path/networks"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml191(td)
-msgid "(StrOpt) Location to keep network config files"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml194(td)
-msgid "num_networks = 1"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml195(td)
-msgid "(IntOpt) Number of networks to support"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml198(td)
-msgid "ovs_vsctl_timeout = 120"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml199(td)
-msgid ""
-"(IntOpt) Amount of time, in seconds, that ovs_vsctl should wait for a "
-"response from the database. 0 is to wait forever."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml202(td)
-msgid "public_interface = eth0"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml203(td)
-msgid "(StrOpt) Interface for public IP addresses"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml206(td)
-msgid "routing_source_ip = $my_ip"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml207(td)
-msgid "(StrOpt) Public IP of network host"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml210(td)
-msgid "security_group_api = nova"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml211(td)
-msgid "(StrOpt) The full class name of the security API class"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml214(td)
-msgid "send_arp_for_ha = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml215(td)
-msgid "(BoolOpt) Send gratuitous ARPs for HA setup"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml218(td)
-msgid "send_arp_for_ha_count = 3"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml219(td)
-msgid "(IntOpt) Send this many gratuitous ARPs for HA setup"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml222(td)
-msgid "share_dhcp_address = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml223(td)
-msgid ""
-"(BoolOpt) If True in multi_host mode, all compute hosts share the same dhcp "
-"address. The same IP address used for DHCP will be added on each nova-"
-"network node which is only visible to the vms on the same host."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml226(td)
-msgid "teardown_unused_network_gateway = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml227(td)
-msgid ""
-"(BoolOpt) If True, unused gateway devices (VLAN and bridge) are deleted in "
-"VLAN network mode with multi hosted networks"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml230(td)
-msgid "update_dns_entries = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml231(td)
-msgid ""
-"(BoolOpt) If True, when a DNS entry must be updated, it sends a fanout cast "
-"to all network hosts to update their DNS entries in multi host mode"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml234(td)
-msgid "use_network_dns_servers = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml235(td)
-msgid ""
-"(BoolOpt) If set, uses the dns1 and dns2 from the network ref. as dns "
-"servers."
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml238(td)
-msgid "use_neutron_default_nets = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml239(td)
-msgid "(StrOpt) Control for checking for default networks"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml242(td)
-msgid "use_single_default_gateway = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml243(td)
-msgid ""
-"(BoolOpt) Use single default gateway. Only first nic of vm will get default "
-"gateway from dhcp server"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml246(td)
-msgid "vlan_interface = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml247(td)
-msgid "(StrOpt) VLANs will bridge into this interface if set"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml250(td)
-msgid "vlan_start = 100"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml251(td)
-msgid "(IntOpt) First VLAN for private networks"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml257(td)
-msgid "vlan_interface = vmnic0"
-msgstr ""
-
-#: ./doc/common/tables/nova-network.xml258(td)
-msgid "(StrOpt) Physical ethernet adapter name for vlan networking"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scality.xml8(caption)
-msgid "Description of configuration options for scality"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scality.xml30(td)
-msgid "scality_sofs_volume_dir = cinder/volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scality.xml31(td)
-msgid "(StrOpt) Path from Scality SOFS root to volume dir"
-msgstr ""
-
-#: ./doc/common/tables/neutron-notifier.xml8(caption)
-msgid "Description of configuration options for notifier"
-msgstr ""
-
-#: ./doc/common/tables/neutron-notifier.xml26(td)
-#: ./doc/common/tables/trove-common.xml50(td)
-msgid "default_publisher_id = $host"
-msgstr ""
-
-#: ./doc/common/tables/neutron-notifier.xml31(td)
-#: ./doc/common/tables/heat-amqp.xml51(td)
-#: ./doc/common/tables/ceilometer-amqp.xml31(td)
-#: ./doc/common/tables/trove-amqp.xml59(td)
-msgid "(MultiStrOpt) Driver or drivers to handle sending notifications"
-msgstr ""
-
-#: ./doc/common/tables/neutron-notifier.xml35(td)
-#: ./doc/common/tables/trove-amqp.xml67(td)
-msgid "(ListOpt) AMQP topic used for openstack notifications"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml22(td)
-msgid "compute_api_class = cinder.compute.nova.API"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml23(td)
-msgid "(StrOpt) The full class name of the compute API class to use"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml30(td)
-msgid "default_availability_zone = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml31(td)
-msgid ""
-"(StrOpt) default availability zone to use when creating a new volume. If "
-"this is not set then we use the value from the storage_availability_zone "
-"option as the default availability_zone for new volumes."
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml34(td)
-msgid ""
-"default_log_levels = amqp=WARN, amqplib=WARN, boto=WARN, qpid=WARN, "
-"sqlalchemy=WARN, suds=INFO, oslo.messaging=INFO, iso8601=WARN, "
-"requests.packages.urllib3.connectionpool=WARN"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml38(td)
-msgid "default_volume_type = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml39(td)
-msgid "(StrOpt) default volume type to use"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml46(td)
-#: ./doc/common/tables/nova-api.xml26(td)
-msgid "enable_new_services = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml47(td)
-#: ./doc/common/tables/nova-api.xml27(td)
-msgid "(BoolOpt) Services to be added to the available pool on create"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml55(td)
-msgid "(BoolOpt) make exception message format errors fatal"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml59(td)
-msgid ""
-"(StrOpt) Name of this node. This can be an opaque identifier. It is not "
-"necessarily a hostname, FQDN, or IP address."
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml62(td)
-msgid "iet_conf = /etc/iet/ietd.conf"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml63(td)
-msgid "(StrOpt) IET configuration file"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml66(td)
-msgid "lio_initiator_iqns ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml67(td)
-msgid ""
-"(StrOpt) Comma-separated list of initiator IQNs allowed to connect to the "
-"iSCSI target. (From Nova compute nodes.)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml71(td)
-msgid "(StrOpt) Directory to use for lock files. Default to a temp directory"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml111(td)
-msgid "(BoolOpt) Enable monkey patching"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml114(td)
-msgid "monkey_patch_modules ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml119(td)
-msgid "(StrOpt) ip address of this host"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml122(td)
-msgid "no_snapshot_gb_quota = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml123(td)
-msgid "(BoolOpt) Whether snapshots count against GigaByte quota"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml126(td)
-msgid "num_shell_tries = 3"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml127(td)
-msgid "(IntOpt) number of times to attempt to run flakey shell commands"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml131(td)
-msgid ""
-"(IntOpt) range of seconds to randomly delay when starting the periodic task "
-"scheduler to reduce stampeding. (Disable by setting to 0)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml134(td)
-#: ./doc/common/tables/trove-rpc.xml42(td)
-#: ./doc/common/tables/heat-common.xml46(td)
-msgid "periodic_interval = 60"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml135(td)
-msgid "(IntOpt) seconds between running periodic tasks"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml147(td)
-msgid "(IntOpt) seconds between nodes reporting state to datastore"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml150(td)
-msgid "reserved_percentage = 0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml151(td)
-msgid "(IntOpt) The percentage of backend capacity is reserved"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml154(td)
-msgid "rootwrap_config = /etc/cinder/rootwrap.conf"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml163(td)
-msgid "(IntOpt) maximum time since last check-in for up service"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml166(td)
-msgid "sqlite_db = cinder.sqlite"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml186(td)
-msgid "state_path = /var/lib/cinder"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml187(td)
-msgid "(StrOpt) Top-level directory for maintaining cinder's state"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml190(td)
-msgid "storage_availability_zone = nova"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml191(td)
-msgid "(StrOpt) availability zone of this node"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml203(td)
-msgid "(IntOpt) count of reservations until usage is refreshed"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml206(td)
-#: ./doc/common/tables/nova-api.xml94(td)
-msgid "use_forwarded_for = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml207(td)
-#: ./doc/common/tables/nova-api.xml95(td)
-msgid ""
-"(BoolOpt) Treat X-Forwarded-For as the canonical remote address. Only enable"
-" this if you have a sanitizing proxy."
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml237(td)
-msgid "use_tpool = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-common.xml238(td)
-msgid ""
-"(BoolOpt) Enable the experimental use of thread pooling for all DB API calls"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml8(caption)
-msgid "Description of configuration options for trustedcomputing"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml19(th)
-msgid "[trusted_computing]"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml22(td)
-msgid "attestation_api_url = /OpenAttestationWebServices/V1.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml23(td)
-msgid "(StrOpt) Attestation web API URL"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml26(td)
-msgid "attestation_auth_blob = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml27(td)
-msgid "(StrOpt) Attestation authorization blob - must change"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml30(td)
-msgid "attestation_auth_timeout = 60"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml31(td)
-msgid "(IntOpt) Attestation status cache valid period length"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml34(td)
-msgid "attestation_port = 8443"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml35(td)
-msgid "(StrOpt) Attestation server port"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml38(td)
-msgid "attestation_server = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml39(td)
-msgid "(StrOpt) Attestation server HTTP"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml42(td)
-msgid "attestation_server_ca_file = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-trustedcomputing.xml43(td)
-msgid "(StrOpt) Attestation server Cert file for Identity verification"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_flat.xml8(caption)
-msgid "Description of configuration options for ml2_flat"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_flat.xml19(th)
-msgid "[ml2_type_flat]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_flat.xml22(td)
-msgid "flat_networks ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_flat.xml23(td)
-msgid ""
-"(ListOpt) List of physical_network names with which flat networks can be "
-"created. Use * to allow flat networks with arbitrary physical_network names."
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_cinder.xml8(caption)
-msgid "Description of configuration options for clients_cinder"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_cinder.xml19(th)
-msgid "[clients_cinder]"
-msgstr ""
-
-#: ./doc/common/tables/nova-configdrive.xml8(caption)
-msgid "Description of configuration options for configdrive"
-msgstr "コンフィグドライブの設定オプションの説明"
-
-#: ./doc/common/tables/nova-configdrive.xml22(td)
-msgid "config_drive_format = iso9660"
-msgstr "config_drive_format = iso9660"
-
-#: ./doc/common/tables/nova-configdrive.xml23(td)
-msgid "(StrOpt) Config drive format. One of iso9660 (default) or vfat"
-msgstr "(文字列オプション) コンフィグドライブの形式。iso9660 (デフォルト) または vfat のいずれか"
-
-#: ./doc/common/tables/nova-configdrive.xml26(td)
-msgid ""
-"config_drive_skip_versions = 1.0 2007-01-19 2007-03-01 2007-08-29 2007-10-10"
-" 2007-12-15 2008-02-01 2008-09-01"
-msgstr "config_drive_skip_versions = 1.0 2007-01-19 2007-03-01 2007-08-29 2007-10-10 2007-12-15 2008-02-01 2008-09-01"
-
-#: ./doc/common/tables/nova-configdrive.xml27(td)
-msgid ""
-"(StrOpt) List of metadata versions to skip placing into the config drive"
-msgstr "(文字列オプション) コンフィグドライブへの設定を省略するメタデータバージョンの一覧"
-
-#: ./doc/common/tables/nova-configdrive.xml30(td)
-msgid "config_drive_tempdir = None"
-msgstr "config_drive_tempdir = None"
-
-#: ./doc/common/tables/nova-configdrive.xml31(td)
-msgid ""
-"(StrOpt) Where to put temporary files associated with config drive creation"
-msgstr "(文字列オプション) コンフィグドライブの作成に関連する一時ファイルを保存する場所"
-
-#: ./doc/common/tables/nova-configdrive.xml34(td)
-msgid "force_config_drive = None"
-msgstr "force_config_drive = None"
-
-#: ./doc/common/tables/nova-configdrive.xml35(td)
-msgid ""
-"(StrOpt) Set to force injection to take place on a config drive (if set, "
-"valid options are: always)"
-msgstr "(文字列オプション) コンフィグドライブで行われる注入を強制するように設定します (設定されている場合は、有効なオプションは always となります)。"
-
-#: ./doc/common/tables/nova-configdrive.xml38(td)
-msgid "mkisofs_cmd = genisoimage"
-msgstr "mkisofs_cmd = genisoimage"
-
-#: ./doc/common/tables/nova-configdrive.xml45(td)
-msgid "config_drive_cdrom = False"
-msgstr "config_drive_cdrom = False"
-
-#: ./doc/common/tables/nova-configdrive.xml46(td)
-msgid ""
-"(BoolOpt) Attaches the Config Drive image as a cdrom drive instead of a disk"
-" drive"
-msgstr "(論理値オプション) ディスクドライブではなく、CD ドライブとしてコンフィグドライブイメージを接続します。"
-
-#: ./doc/common/tables/nova-configdrive.xml49(td)
-msgid "config_drive_inject_password = False"
-msgstr "config_drive_inject_password = False"
-
-#: ./doc/common/tables/nova-configdrive.xml50(td)
-msgid "(BoolOpt) Sets the admin password in the config drive image"
-msgstr "(論理値オプション) コンフィグドライブのイメージに管理者パスワードを設定します。"
-
-#: ./doc/common/tables/cinder-database.xml26(td)
-msgid "db_driver = cinder.db"
-msgstr ""
-
-#: ./doc/common/tables/cinder-database.xml27(td)
-msgid "(StrOpt) driver to use for database access"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rpc.xml30(td)
-msgid "control_exchange = neutron"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rpc.xml31(td)
-#: ./doc/common/tables/heat-amqp.xml31(td)
-#: ./doc/common/tables/ceilometer-exchange.xml27(td)
-#: ./doc/common/tables/trove-amqp.xml35(td)
-msgid "(StrOpt) AMQP exchange to connect to if using RabbitMQ or Qpid"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rpc.xml42(td)
-msgid "rpc_backend = neutron.openstack.common.rpc.impl_kombu"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rpc.xml62(td)
-msgid "rpc_workers = 0"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rpc.xml63(td)
-msgid "(IntOpt) Number of RPC worker processes for service"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rpc.xml69(td)
-msgid "rpc_support_old_agents = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rpc.xml70(td)
-msgid "(BoolOpt) Enable server RPC compatibility with old agents"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rpc.xml84(td)
-#: ./doc/common/tables/trove-rpc.xml74(td)
-msgid "(ListOpt) AMQP topic(s) used for openstack notifications"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zoning_manager.xml8(caption)
-msgid "Description of configuration options for zoning_manager"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zoning_manager.xml22(td)
-msgid ""
-"brcd_sb_connector = "
-"cinder.zonemanager.drivers.brocade.brcd_fc_zone_client_cli.BrcdFCZoneClientCLI"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zoning_manager.xml23(td)
-msgid "(StrOpt) Southbound connector for zoning operation"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zoning_manager.xml26(td)
-msgid ""
-"fc_san_lookup_service = "
-"cinder.zonemanager.drivers.brocade.brcd_fc_san_lookup_service.BrcdFCSanLookupService"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zoning_manager.xml27(td)
-msgid "(StrOpt) FC San Lookup Service"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zoning_manager.xml30(td)
-msgid ""
-"zone_driver = "
-"cinder.zonemanager.drivers.brocade.brcd_fc_zone_driver.BrcdFCZoneDriver"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zoning_manager.xml31(td)
-msgid "(StrOpt) FC Zone Driver responsible for zone management"
-msgstr ""
-
-#: ./doc/common/tables/trove-volume.xml8(caption)
-msgid "Description of configuration options for volume"
-msgstr ""
-
-#: ./doc/common/tables/trove-volume.xml22(td)
-msgid "block_device_mapping = vdb"
-msgstr ""
-
-#: ./doc/common/tables/trove-volume.xml26(td)
-msgid "cinder_url = http://localhost:8776/v2"
-msgstr ""
-
-#: ./doc/common/tables/trove-volume.xml30(td)
-msgid "device_path = /dev/vdb"
-msgstr ""
-
-#: ./doc/common/tables/trove-volume.xml34(td)
-msgid "trove_volume_support = True"
-msgstr ""
-
-#: ./doc/common/tables/trove-volume.xml35(td)
-msgid "(BoolOpt) Whether to provision a cinder volume for datadir."
-msgstr ""
-
-#: ./doc/common/tables/trove-volume.xml38(td)
-msgid "volume_format_timeout = 120"
-msgstr ""
-
-#: ./doc/common/tables/trove-volume.xml42(td)
-msgid "volume_fstype = ext3"
-msgstr ""
-
-#: ./doc/common/tables/trove-volume.xml46(td)
-msgid "volume_time_out = 60"
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml8(caption)
-msgid "Description of configuration options for cache"
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml19(th)
-msgid "[cache]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml22(td)
-msgid "backend = keystone.common.cache.noop"
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml23(td)
-msgid ""
-"(StrOpt) Dogpile.cache backend module. It is recommended that Memcache "
-"(dogpile.cache.memcache) or Redis (dogpile.cache.redis) be used in "
-"production deployments. Small workloads (single process) like devstack can "
-"use the dogpile.cache.memory backend."
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml26(td)
-msgid "backend_argument = []"
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml27(td)
-msgid ""
-"(MultiStrOpt) Arguments supplied to the backend module. Specify this option "
-"once per argument to be passed to the dogpile.cache backend. Example format:"
-" \"&lt;argname&gt;:&lt;value&gt;\"."
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml30(td)
-msgid "config_prefix = cache.keystone"
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml31(td)
-msgid ""
-"(StrOpt) Prefix for building the configuration dictionary for the cache "
-"region. This should not need to be changed unless there is another "
-"dogpile.cache region with the same configuration name."
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml34(td)
-msgid "debug_cache_backend = False"
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml35(td)
-msgid ""
-"(BoolOpt) Extra debugging from the cache backend (cache keys, "
-"get/set/delete/etc calls) This is only really useful if you need to see the "
-"specific cache-backend get/set/delete calls with the keys/values. Typically "
-"this should be left set to False."
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml39(td)
-msgid ""
-"(BoolOpt) Global toggle for all caching using the should_cache_fn mechanism."
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml42(td)
-msgid "expiration_time = 600"
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml43(td)
-msgid ""
-"(IntOpt) Default TTL, in seconds, for any cached item in the dogpile.cache "
-"region. This applies to any cached method that doesn't have an explicit "
-"cache expiration time defined for it."
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml46(td)
-msgid "proxies ="
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml47(td)
-msgid ""
-"(ListOpt) Proxy Classes to import that will affect the way the dogpile.cache"
-" backend functions. See the dogpile.cache documentation on changing-backend-"
-"behavior. Comma delimited list e.g. my.dogpile.proxy.Class, "
-"my.dogpile.proxyClass2."
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml50(td)
-msgid "use_key_mangler = True"
-msgstr ""
-
-#: ./doc/common/tables/keystone-cache.xml51(td)
-msgid ""
-"(BoolOpt) Use a key-mangling function (sha1) to ensure fixed length cache-"
-"keys. This is toggle-able for debugging purposes, it is highly recommended "
-"to always leave this set to True."
-msgstr ""
-
-#: ./doc/common/tables/glance-testing.xml22(td)
-msgid "pydev_worker_debug_host = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-testing.xml23(td)
-msgid ""
-"(StrOpt) The hostname/IP of the pydev process listening for debug "
-"connections"
-msgstr ""
-
-#: ./doc/common/tables/glance-testing.xml26(td)
-msgid "pydev_worker_debug_port = 5678"
-msgstr ""
-
-#: ./doc/common/tables/glance-testing.xml27(td)
-msgid ""
-"(IntOpt) The port on which a pydev process is listening for connections."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml7(literal)
-msgid "[filter:tempauth]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml18(td)
-msgid "use = egg:swift#tempauth"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml21(td)
-msgid "set log_name = tempauth"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml36(td)
-msgid "reseller_prefix = AUTH"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml36(td)
-msgid "The naming scope for the auth service. Swift"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml39(td)
-msgid "auth_prefix = /auth/"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml39(td)
-msgid ""
-"The HTTP request path prefix for the auth service. Swift itself reserves "
-"anything beginning with the letter `v`."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml42(td)
-msgid "token_life = 86400"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml42(td)
-msgid "The number of seconds a token is valid."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml45(td)
-msgid "allow_overrides = true"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml48(td)
-msgid "storage_url_scheme = default"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml48(td)
-msgid ""
-"Scheme to return with storage urls: http, https, or default (chooses based "
-"on what the server is running as) This can be useful with an SSL load "
-"balancer in front of a non-SSL server."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml51(td)
-msgid "user_admin_admin = admin .admin .reseller_admin"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml54(td)
-msgid "user_test_tester = testing .admin"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml57(td)
-msgid "user_test2_tester2 = testing2 .admin"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-tempauth.xml60(td)
-msgid "user_test_tester3 = testing3"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml8(caption)
-msgid "Description of configuration options for registry"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml23(td)
-msgid "(StrOpt) The administrators password."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml27(td)
-msgid "(StrOpt) The tenant name of the administrative user."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml31(td)
-msgid "(StrOpt) The administrators user name."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml35(td)
-msgid "(StrOpt) The region for the authentication service."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml39(td)
-msgid "(StrOpt) The strategy to use for authentication."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml43(td)
-msgid "(StrOpt) The URL to the keystone service."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml46(td)
-msgid "registry_client_ca_file = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml47(td)
-msgid ""
-"(StrOpt) The path to the certifying authority cert file to use in SSL "
-"connections to the registry server."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml50(td)
-msgid "registry_client_cert_file = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml51(td)
-msgid ""
-"(StrOpt) The path to the cert file to use in SSL connections to the registry"
-" server."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml54(td)
-msgid "registry_client_insecure = False"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml55(td)
-msgid ""
-"(BoolOpt) When using SSL in connections to the registry server, do not "
-"require validation via a certifying authority."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml58(td)
-msgid "registry_client_key_file = None"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml59(td)
-msgid ""
-"(StrOpt) The path to the key file to use in SSL connections to the registry "
-"server."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml62(td)
-msgid "registry_client_protocol = http"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml63(td)
-msgid ""
-"(StrOpt) The protocol to use for communication with the registry server. "
-"Either http or https."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml66(td)
-msgid "registry_client_timeout = 600"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml67(td)
-msgid ""
-"(IntOpt) The period of time, in seconds, that the API server will wait for a"
-" registry request to complete. A value of 0 implies no timeout."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml70(td)
-msgid "registry_host = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml71(td)
-msgid "(StrOpt) Address to find the registry server."
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml74(td)
-msgid "registry_port = 9191"
-msgstr ""
-
-#: ./doc/common/tables/glance-registry.xml75(td)
-msgid "(IntOpt) Port the registry server is listening on."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml7(literal)
-msgid "[object-replicator]"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml18(td)
-msgid "log_name = object-replicator"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml33(td)
-msgid "daemonize = on"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml33(td)
-msgid "Whether or not to run replication as a daemon"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml42(td)
-msgid "stats_interval = 300"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml42(td)
-msgid "Interval in seconds between logging replication statistics"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml45(td)
-msgid "sync_method = rsync"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml48(td)
-msgid "rsync_timeout = 900"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml48(td)
-msgid "Max duration (seconds) of a partition rsync"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml51(td)
-msgid "rsync_bwlimit = 0"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml54(td)
-msgid "rsync_io_timeout = 30"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml54(td)
-msgid "Passed to rsync for a max duration (seconds) of an I/O op"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml60(td)
-msgid "http_timeout = 60"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml60(td)
-msgid "Maximum duration for an HTTP request"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml63(td)
-msgid "lockup_timeout = 1800"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml63(td)
-msgid ""
-"Attempts to kill all workers if nothing replications for lockup_timeout "
-"seconds"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml69(td)
-msgid "ring_check_interval = 15"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml69(td)
-msgid "How often (in seconds) to check the ring"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml75(td)
-msgid "rsync_error_log_line_length = 0"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml78(td)
-msgid "handoffs_first = False"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml78(td)
-msgid ""
-"If set to True, partitions that are not supposed to be on the node will be "
-"replicated first. The default setting should not be changed, except for "
-"extreme situations."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml81(td)
-msgid "handoff_delete = auto"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-object-replicator.xml81(td)
-msgid ""
-"By default handoff partitions will be removed when it has successfully "
-"replicated to all the canonical nodes. If set to an integer n, it will "
-"remove the partition if it is successfully replicated to n nodes. The "
-"default setting should not be changed, except for extremem situations. This "
-"uses what's set here, or what's set in the DEFAULT section, or 10 (though "
-"other sections use 3 as the final default)."
-msgstr ""
-
 #: ./doc/common/tables/trove-database.xml22(td)
 msgid "sql_connection = sqlite:///trove_test.sqlite"
 msgstr ""
@@ -43400,1501 +44235,242 @@ msgid ""
 "(BoolOpt) Allow insecure logging while executing queries through SQLAlchemy."
 msgstr ""
 
-#: ./doc/common/tables/heat-clients_backends.xml8(caption)
-msgid "Description of configuration options for clients_backends"
+#: ./doc/common/tables/swift-container-server-app-container-server.xml7(literal)
+msgid "[app:container-server]"
 msgstr ""
 
-#: ./doc/common/tables/heat-clients_backends.xml22(td)
-msgid "cloud_backend = heat.engine.clients.OpenStackClients"
+#: ./doc/common/tables/swift-container-server-app-container-server.xml18(td)
+msgid "use = egg:swift#container"
 msgstr ""
 
-#: ./doc/common/tables/heat-clients_backends.xml23(td)
-msgid "(StrOpt) Fully qualified class name to use as a client backend."
+#: ./doc/common/tables/swift-container-server-app-container-server.xml21(td)
+msgid "set log_name = container-server"
 msgstr ""
 
-#: ./doc/common/tables/heat-amqp.xml30(td)
-msgid "control_exchange = heat"
+#: ./doc/common/tables/swift-container-server-app-container-server.xml42(td)
+msgid "allow_versions = false"
 msgstr ""
 
-#: ./doc/common/tables/heat-amqp.xml43(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml23(td)
-#: ./doc/common/tables/neutron-testing.xml27(td)
-#: ./doc/common/tables/trove-amqp.xml39(td)
-msgid "(BoolOpt) If passed, use a fake RabbitMQ provider"
-msgstr "(論理値オプション) 指定されると、擬似 RabbitMQ プロバイダーを使用します。"
+#: ./doc/common/tables/swift-container-server-app-container-server.xml42(td)
+msgid "Enable/Disable object versioning feature"
+msgstr ""
 
-#: ./doc/common/tables/heat-amqp.xml46(td)
+#: ./doc/common/tables/nova-authentication.xml8(caption)
+msgid "Description of configuration options for authentication"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml8(caption)
+msgid "Description of configuration options for nvsd"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml23(td)
+msgid "(StrOpt) integration bridge"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml26(th)
+msgid "[nvsd]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml29(td)
+msgid "nvsd_ip = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml30(td)
+msgid "(StrOpt) NVSD Controller IP address"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml33(td)
+msgid "nvsd_passwd = oc123"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml34(td)
+msgid "(StrOpt) NVSD Controller password"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml37(td)
+msgid "nvsd_port = 8082"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml38(td)
+msgid "(IntOpt) NVSD Controller Port number"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml41(td)
+msgid "nvsd_retries = 0"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml42(td)
+msgid "(IntOpt) Number of login retries to NVSD controller"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml45(td)
+msgid "nvsd_user = ocplugin"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml46(td)
+msgid "(StrOpt) NVSD Controller username"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml49(td)
+msgid "request_timeout = 30"
+msgstr ""
+
+#: ./doc/common/tables/neutron-nvsd.xml50(td)
+msgid "(IntOpt) NVSD controller REST API request timeout in seconds"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-pipeline-main.xml18(td)
+msgid "pipeline = healthcheck recon account-server"
+msgstr ""
+
+#: ./doc/common/tables/glance-gridfs.xml8(caption)
+msgid "Description of configuration options for gridfs"
+msgstr ""
+
+#: ./doc/common/tables/glance-gridfs.xml22(td)
+msgid "mongodb_store_db = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-gridfs.xml23(td)
+msgid "(StrOpt) Database to use."
+msgstr ""
+
+#: ./doc/common/tables/glance-gridfs.xml26(td)
+msgid "mongodb_store_uri = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-gridfs.xml27(td)
 msgid ""
-"list_notifier_drivers = ['heat.openstack.common.notifier.no_op_notifier']"
+"(StrOpt) Hostname or IP address of the instance to connect to, or a mongodb "
+"URI, or a list of hostnames / mongodb URIs. If host is an IPv6 literal it "
+"must be enclosed in '[' and ']' characters following the RFC2732 URL syntax "
+"(e.g. '[::1]' for localhost)."
 msgstr ""
 
-#: ./doc/common/tables/heat-amqp.xml47(td)
-msgid "(MultiStrOpt) List of drivers to send notifications"
-msgstr "(複数文字列オプション) 通知を送信するドライバーの一覧"
-
-#: ./doc/common/tables/heat-amqp.xml55(td)
-#: ./doc/common/tables/ceilometer-amqp.xml35(td)
-msgid "(ListOpt) AMQP topic used for OpenStack notifications"
+#: ./doc/common/tables/neutron-notifier.xml8(caption)
+msgid "Description of configuration options for notifier"
 msgstr ""
 
-#: ./doc/common/tables/swift-dispersion-dispersion.xml7(literal)
-msgid "[dispersion]"
+#: ./doc/common/tables/nova-rpc_all.xml8(caption)
+msgid "Description of configuration options for rpc_all"
 msgstr ""
 
-#: ./doc/common/tables/swift-dispersion-dispersion.xml7(literal)
-msgid "dispersion.conf-sample"
+#: ./doc/common/tables/nova-rpc_all.xml201(td)
+#: ./doc/common/tables/nova-rpc.xml65(td)
+msgid "rpc_driver_queue_base = cells.intercell"
 msgstr ""
 
-#: ./doc/common/tables/swift-dispersion-dispersion.xml18(td)
-msgid "auth_url = http://localhost:8080/auth/v1.0"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml18(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml27(td)
-msgid "Endpoint for auth server, such as keystone"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml21(td)
-msgid "auth_user = test:tester"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml21(td)
-#: ./doc/common/tables/swift-dispersion-dispersion.xml30(td)
-msgid "Default user for dispersion in this context"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml24(td)
-msgid "auth_key = testing"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml27(td)
-msgid "auth_url = http://localhost:5000/v2.0/"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml30(td)
-msgid "auth_user = tenant:user"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml33(td)
-msgid "auth_key = password"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml36(td)
-msgid "auth_version = 2.0"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml36(td)
-msgid "Indicates which version of auth"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml39(td)
-msgid "Indicates whether endpoint for auth is public or internal"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml42(td)
-msgid "keystone_api_insecure = no"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml48(td)
-msgid "dispersion_coverage = 1.0"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml51(td)
-msgid "retries = 5"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml54(td)
-#: ./doc/common/tables/swift-account-server-account-reaper.xml30(td)
-msgid "concurrency = 25"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml57(td)
-msgid "container_populate = yes"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml60(td)
-msgid "object_populate = yes"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml63(td)
-msgid "container_report = yes"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml66(td)
-msgid "object_report = yes"
-msgstr ""
-
-#: ./doc/common/tables/swift-dispersion-dispersion.xml69(td)
-msgid "dump_json = no"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hpmsa.xml8(caption)
-msgid "Description of configuration options for hpmsa"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hpmsa.xml22(td)
-msgid "msa_vdisk = OpenStack"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hpmsa.xml23(td)
-msgid "(StrOpt) The VDisk to use for volume creation."
-msgstr ""
-
-#: ./doc/common/tables/cinder-emc.xml8(caption)
-msgid "Description of configuration options for emc"
-msgstr ""
-
-#: ./doc/common/tables/cinder-emc.xml22(td)
-msgid "cinder_emc_config_file = /etc/cinder/cinder_emc_config.xml"
-msgstr ""
-
-#: ./doc/common/tables/cinder-emc.xml23(td)
-msgid "(StrOpt) use this file for cinder emc plugin config data"
-msgstr ""
-
-#: ./doc/common/tables/cinder-emc.xml26(td)
-msgid "max_luns_per_storage_group = 256"
-msgstr ""
-
-#: ./doc/common/tables/cinder-emc.xml27(td)
-msgid "(IntOpt) Default max number of LUNs in a storage group"
-msgstr ""
-
-#: ./doc/common/tables/cinder-emc.xml30(td)
-msgid "naviseccli_path ="
-msgstr ""
-
-#: ./doc/common/tables/cinder-emc.xml31(td)
-msgid "(StrOpt) Naviseccli Path"
-msgstr ""
-
-#: ./doc/common/tables/cinder-emc.xml34(td)
-msgid "storage_vnx_pool_name = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-emc.xml35(td)
-msgid "(StrOpt) ISCSI pool name"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-account-replicator.xml7(literal)
-msgid "[account-replicator]"
-msgstr ""
-
-#: ./doc/common/tables/swift-account-server-account-replicator.xml18(td)
-msgid "log_name = account-replicator"
-msgstr ""
-
-#: ./doc/common/tables/neutron-fwaas.xml8(caption)
-msgid "Description of configuration options for fwaas"
-msgstr ""
-
-#: ./doc/common/tables/neutron-fwaas.xml19(th)
-#: ./doc/common/tables/neutron-nec.xml73(th)
-msgid "[fwaas]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-fwaas.xml23(td)
-msgid "(BoolOpt) Enable FWaaS"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups_tsm.xml8(caption)
-msgid "Description of configuration options for backups_tsm"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups_tsm.xml22(td)
-msgid "backup_tsm_compression = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups_tsm.xml23(td)
-msgid "(BoolOpt) Enable or Disable compression for backups"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups_tsm.xml26(td)
-msgid "backup_tsm_password = password"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups_tsm.xml27(td)
-msgid "(StrOpt) TSM password for the running username"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups_tsm.xml30(td)
-msgid "backup_tsm_volume_prefix = backup"
-msgstr ""
-
-#: ./doc/common/tables/cinder-backups_tsm.xml31(td)
-msgid "(StrOpt) Volume prefix for the backup id when backing up to TSM"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml8(caption)
-msgid "Description of configuration options for sdnve"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml19(th)
-msgid "[SDNVE]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml22(td)
-msgid "base_url = /one/nb/v2/"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml23(td)
-msgid "(StrOpt) Base URL for SDN-VE controller REST API"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml26(td)
-msgid "controller_ips = 127.0.0.1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml27(td)
-msgid "(ListOpt) List of IP addresses of SDN-VE controller(s)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml30(td)
-msgid "default_tenant_type = OF"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml31(td)
-msgid "(StrOpt) Tenant type: OF (default) and OVERLAY"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml34(td)
-msgid "format = json"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml35(td)
-msgid "(StrOpt) SDN-VE request/response format"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml38(td)
-msgid "info = sdnve_info_string"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml39(td)
-msgid "(StrOpt) SDN-VE RPC subject"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml42(td)
-msgid "integration_bridge = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml46(td)
-msgid "interface_mappings ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml47(td)
-msgid "(ListOpt) List of &lt;physical_network_name&gt;:&lt;interface_name&gt;"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml50(td)
-msgid "of_signature = SDNVE-OF"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml51(td)
+#: ./doc/common/tables/nova-rpc_all.xml202(td)
+#: ./doc/common/tables/nova-rpc.xml66(td)
 msgid ""
-"(StrOpt) The string in tenant description that indicates the tenant is a OF "
-"tenant"
+"(StrOpt) Base queue name to use when communicating between cells. Various "
+"topics by message type will be appended to this."
 msgstr ""
 
-#: ./doc/common/tables/neutron-sdnve.xml54(td)
-msgid "out_of_band = True"
+#: ./doc/common/tables/nova-rpc_all.xml215(td)
+#: ./doc/common/tables/nova-rpc.xml79(td)
+msgid "baseapi = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-sdnve.xml55(td)
-msgid "(BoolOpt) Indicating if controller is out of band or not"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml58(td)
-msgid "overlay_signature = SDNVE-OVERLAY"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml59(td)
+#: ./doc/common/tables/nova-rpc_all.xml216(td)
+#: ./doc/common/tables/nova-rpc.xml80(td)
 msgid ""
-"(StrOpt) The string in tenant description that indicates the tenant is a "
-"OVERLAY tenant"
+"(StrOpt) Set a version cap for messages sent to the base api in any service"
 msgstr ""
 
-#: ./doc/common/tables/neutron-sdnve.xml62(td)
-msgid "password = admin"
+#: ./doc/common/tables/neutron-hyperv_agent.xml8(caption)
+msgid "Description of configuration options for hyperv_agent"
 msgstr ""
 
-#: ./doc/common/tables/neutron-sdnve.xml63(td)
-msgid "(StrOpt) SDN-VE administrator password"
+#: ./doc/common/tables/neutron-hyperv_agent.xml22(td)
+msgid "enable_metrics_collection = False"
 msgstr ""
 
-#: ./doc/common/tables/neutron-sdnve.xml66(td)
-msgid "port = 8443"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml67(td)
-msgid "(StrOpt) SDN-VE controller port number"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml70(td)
-msgid "reset_bridge = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml71(td)
-msgid "(BoolOpt) Reset the integration bridge before use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml74(td)
-msgid "use_fake_controller = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml75(td)
-msgid "(BoolOpt) If set to True uses a fake controller."
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml78(td)
-msgid "userid = admin"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml79(td)
-msgid "(StrOpt) SDN-VE administrator user id"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml82(th)
-msgid "[SDNVE_AGENT]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml86(td)
-msgid "(IntOpt) Agent polling interval if necessary"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml90(td)
-msgid "(StrOpt) Using root helper"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml93(td)
-msgid "rpc = True"
-msgstr ""
-
-#: ./doc/common/tables/neutron-sdnve.xml94(td)
-msgid "(BoolOpt) Whether using rpc"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_mysql.xml8(caption)
-msgid "Description of configuration options for db_mysql"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_mysql.xml19(th)
-msgid "[mysql]"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_mysql.xml26(td)
-#: ./doc/common/tables/trove-db_percona.xml26(td)
-msgid "mount_point = /var/lib/mysql"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_mysql.xml30(td)
-#: ./doc/common/tables/trove-db_percona.xml30(td)
-msgid "root_on_create = False"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_mysql.xml31(td)
-#: ./doc/common/tables/trove-db_percona.xml31(td)
+#: ./doc/common/tables/neutron-hyperv_agent.xml23(td)
 msgid ""
-"(BoolOpt) Enable the automatic creation of the root user for the service "
-"during instance-create. The generated password for the root user is "
-"immediately returned in the response of instance-create as the 'password' "
-"field."
+"(BoolOpt) Enables metrics collections for switch ports by using Hyper-V's "
+"metric APIs. Collected data can by retrieved by other apps and services, "
+"e.g.: Ceilometer. Requires Hyper-V / Windows Server 2012 and above"
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mysql.xml34(td)
-#: ./doc/common/tables/trove-db_percona.xml34(td)
-msgid "tcp_ports = 3306"
+#: ./doc/common/tables/neutron-hyperv_agent.xml26(td)
+msgid "local_network_vswitch = private"
 msgstr ""
 
-#: ./doc/common/tables/trove-db_mysql.xml42(td)
-msgid "usage_timeout = 400"
+#: ./doc/common/tables/neutron-hyperv_agent.xml27(td)
+msgid "(StrOpt) Private vswitch name used for local networks"
 msgstr ""
 
-#: ./doc/common/tables/trove-rpc.xml38(td)
-msgid "num_tries = 3"
+#: ./doc/common/tables/neutron-hyperv_agent.xml30(td)
+msgid "metrics_max_retries = 100"
 msgstr ""
 
-#: ./doc/common/tables/trove-rpc.xml47(td)
-msgid "(IntOpt) The interval in seconds which periodic tasks are run."
-msgstr ""
-
-#: ./doc/common/tables/trove-rpc.xml50(td)
-msgid "rpc_backend = trove.openstack.common.rpc.impl_kombu"
-msgstr ""
-
-#: ./doc/common/tables/trove-rpc.xml77(th)
-msgid "[secure_messages]"
-msgstr ""
-
-#: ./doc/common/tables/trove-rpc.xml81(td)
+#: ./doc/common/tables/neutron-hyperv_agent.xml31(td)
 msgid ""
-"(BoolOpt) Whether Secure Messaging (Signing) is enabled, defaults to enabled"
+"(IntOpt) Specifies the maximum number of retries to enable Hyper-V's port "
+"metrics collection. The agent will try to enable the feature once every "
+"polling_interval period for at most metrics_max_retries or until it "
+"succeedes."
 msgstr ""
 
-#: ./doc/common/tables/trove-rpc.xml84(td)
-msgid "encrypt = False"
+#: ./doc/common/tables/neutron-hyperv_agent.xml34(td)
+msgid "physical_network_vswitch_mappings ="
 msgstr ""
 
-#: ./doc/common/tables/trove-rpc.xml85(td)
+#: ./doc/common/tables/neutron-hyperv_agent.xml35(td)
 msgid ""
-"(BoolOpt) Whether Secure Messaging (Encryption) is enabled, defaults to not "
-"enabled"
+"(ListOpt) List of &lt;physical_network&gt;:&lt;vswitch&gt; where the "
+"physical networks can be expressed with wildcards, e.g.: .\"*:external\""
 msgstr ""
 
-#: ./doc/common/tables/trove-rpc.xml88(td)
-msgid "enforced = False"
-msgstr ""
-
-#: ./doc/common/tables/trove-rpc.xml89(td)
+#: ./doc/common/tables/neutron-hyperv_agent.xml39(td)
 msgid ""
-"(BoolOpt) Whether Secure Messaging (Signing) is enforced, defaults to not "
-"enforced"
+"(IntOpt) The number of seconds the agent will wait between polling for local"
+" device changes."
 msgstr ""
 
-#: ./doc/common/tables/trove-rpc.xml92(td)
-msgid "kds_endpoint = None"
+#: ./doc/common/tables/neutron-hyperv_agent.xml42(th)
+msgid "[HYPERV]"
 msgstr ""
 
-#: ./doc/common/tables/trove-rpc.xml93(td)
-msgid "(StrOpt) KDS endpoint (ex: http://kds.example.com:35357/v3)"
+#: ./doc/common/tables/neutron-hyperv_agent.xml50(td)
+msgid "(StrOpt) Network type for tenant networks (local, flat, vlan or none)"
 msgstr ""
 
-#: ./doc/common/tables/trove-rpc.xml96(td)
-msgid "secret_key = None"
+#: ./doc/common/tables/neutron-hyperv_agent.xml56(td)
+#: ./doc/common/tables/nova-hyperv.xml30(td)
+msgid "force_hyperv_utils_v1 = False"
 msgstr ""
 
-#: ./doc/common/tables/trove-rpc.xml97(td)
+#: ./doc/common/tables/neutron-hyperv_agent.xml57(td)
+#: ./doc/common/tables/nova-hyperv.xml31(td)
+msgid "(BoolOpt) Force V1 WMI utility classes"
+msgstr ""
+
+#: ./doc/common/tables/keystone-federation.xml8(caption)
+msgid "Description of configuration options for federation"
+msgstr ""
+
+#: ./doc/common/tables/keystone-federation.xml19(th)
+msgid "[federation]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-federation.xml22(td)
+msgid "assertion_prefix ="
+msgstr ""
+
+#: ./doc/common/tables/keystone-federation.xml23(td)
 msgid ""
-"(MultiStrOpt) A list of keys: (ex: name:&lt;base64 encoded key&gt;), ignored"
-" if secret_keys_file is set"
+"(StrOpt) Value to be used when filtering assertion parameters from the "
+"environment."
 msgstr ""
 
-#: ./doc/common/tables/trove-rpc.xml100(td)
-msgid "secret_keys_file = None"
+#: ./doc/common/tables/keystone-federation.xml26(td)
+msgid "driver = keystone.contrib.federation.backends.sql.Federation"
 msgstr ""
 
-#: ./doc/common/tables/trove-rpc.xml101(td)
-msgid ""
-"(StrOpt) Path to the file containing the keys, takes precedence over "
-"secret_key"
-msgstr ""
-
-#: ./doc/common/tables/cinder-connection.xml8(caption)
-msgid "Description of configuration options for connection"
-msgstr ""
-
-#: ./doc/common/tables/cinder-connection.xml22(td)
-msgid "connection = sqlite:///$state_path/$sqlite_db"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-DEFAULT.xml18(td)
-msgid "mtime_check_interval = 300"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml7(literal)
-msgid "[filter:authtoken]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml18(td)
-msgid "auth_host = keystonehost"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml24(td)
-msgid "auth_protocol = http"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml27(td)
-msgid "auth_uri = http://keystonehost:5000/"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml30(td)
-msgid "admin_tenant_name = service"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml33(td)
-msgid "admin_user = swift"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml36(td)
-msgid "admin_password = password"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml39(td)
-msgid "delay_auth_decision = 1"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml42(td)
-msgid "cache = swift.cache"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-authtoken.xml45(td)
-msgid "include_service_catalog = False"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_redis.xml8(caption)
-msgid "Description of configuration options for db_redis"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_redis.xml19(th)
-msgid "[redis]"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_redis.xml26(td)
-msgid "mount_point = /var/lib/redis"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_redis.xml30(td)
-msgid "tcp_ports = 6379"
-msgstr ""
-
-#: ./doc/common/tables/neutron-zeromq.xml38(td)
-msgid ""
-"rpc_zmq_matchmaker = "
-"neutron.openstack.common.rpc.matchmaker.MatchMakerLocalhost"
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml8(caption)
-msgid "Description of configuration options for token"
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml19(th)
-msgid "[token]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml22(td)
-msgid "bind ="
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml23(td)
-msgid ""
-"(ListOpt) External auth mechanisms that should add bind information to token"
-" e.g. kerberos, x509."
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml27(td)
-msgid ""
-"(IntOpt) Time to cache tokens (in seconds). This has no effect unless global"
-" and token caching are enabled."
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml31(td)
-msgid ""
-"(BoolOpt) Toggle for token system cacheing. This has no effect unless global"
-" caching is enabled."
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml34(td)
-msgid "driver = keystone.token.backends.sql.Token"
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml35(td)
-msgid "(StrOpt) Keystone Token persistence backend driver."
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml39(td)
-msgid ""
-"(StrOpt) Enforcement policy on tokens presented to keystone with bind "
-"information. One of disabled, permissive, strict, required or a specifically"
-" required bind mode e.g. kerberos or x509 to require binding to that "
-"authentication."
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml42(td)
-msgid "expiration = 3600"
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml43(td)
-msgid "(IntOpt) Amount of time a token should remain valid (in seconds)."
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml46(td)
-msgid "provider = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml47(td)
-msgid ""
-"(StrOpt) Controls the token construction, validation, and revocation "
-"operations. Core providers are "
-"\"keystone.token.providers.[pki|uuid].Provider\"."
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml50(td)
-msgid "revocation_cache_time = 3600"
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml51(td)
-msgid ""
-"(IntOpt) Time to cache the revocation list and the revocation events if "
-"revoke extension is enabled (in seconds). This has no effect unless global "
-"and token caching are enabled."
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml54(td)
-msgid "revoke_by_id = True"
-msgstr ""
-
-#: ./doc/common/tables/keystone-token.xml55(td)
-msgid ""
-"(BoolOpt) Revoke token by token identifier. Setting revoke_by_id to True "
-"enables various forms of enumerating tokens, e.g. `list tokens for user`. "
-"These enumerations are processed to determine the list of tokens to revoke. "
-"Only disable if you are switching to using the Revoke extension with a "
-"backend other than KVS, which stores events in memory."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml19(th)
-msgid "[ipsec]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml22(td)
-msgid "config_base_dir = $state_path/ipsec"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml23(td)
-msgid "(StrOpt) Location to store ipsec server config files"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml26(td)
-msgid "ipsec_status_check_interval = 60"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml27(td)
-msgid "(IntOpt) Interval for checking ipsec status"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml30(th)
-msgid "[openswan]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml33(td)
-msgid ""
-"ipsec_config_template = /usr/lib/python/site-"
-"packages/neutron/services/vpn/device_drivers/template/openswan/ipsec.conf.template"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml34(td)
-msgid "(StrOpt) Template file for ipsec configuration"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml37(td)
-msgid ""
-"ipsec_secret_template = /usr/lib/python/site-"
-"packages/neutron/services/vpn/device_drivers/template/openswan/ipsec.secret.template"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml38(td)
-msgid "(StrOpt) Template file for ipsec secret configuration"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml41(th)
-msgid "[vpnagent]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml44(td)
-msgid ""
-"vpn_device_driver = "
-"['neutron.services.vpn.device_drivers.ipsec.OpenSwanDriver']"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vpn.xml45(td)
-msgid "(MultiStrOpt) The vpn device drivers Neutron will use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-agent.xml8(caption)
-msgid "Description of configuration options for agent"
-msgstr ""
-
-#: ./doc/common/tables/neutron-agent.xml22(td)
-msgid "external_pids = $state_path/external/pids"
-msgstr ""
-
-#: ./doc/common/tables/neutron-agent.xml23(td)
-msgid "(StrOpt) Location to store child pid files"
-msgstr ""
-
-#: ./doc/common/tables/neutron-agent.xml27(td)
-msgid "(IntOpt) MTU setting for device."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml8(caption)
-msgid "Description of configuration options for ryu"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml22(td)
-msgid "openflow_rest_api = 127.0.0.1:8080"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml23(td)
-msgid "(StrOpt) OpenFlow REST API location"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml26(td)
-msgid "ovsdb_interface = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml27(td)
-msgid "(StrOpt) OVSDB interface to connect to"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml30(td)
-msgid "ovsdb_ip = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml31(td)
-msgid "(StrOpt) OVSDB IP to connect to"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml34(td)
-msgid "ovsdb_port = 6634"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml35(td)
-msgid "(IntOpt) OVSDB port to connect to"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml38(td)
-msgid "tunnel_interface = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml39(td)
-msgid "(StrOpt) Tunnel interface to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml42(td)
-msgid "tunnel_ip = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml43(td)
-msgid "(StrOpt) Tunnel IP to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml46(td)
-msgid "tunnel_key_max = 16777215"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml47(td)
-msgid "(IntOpt) Maximum tunnel ID to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml50(td)
-msgid "tunnel_key_min = 1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ryu.xml51(td)
-msgid "(IntOpt) Minimum tunnel ID to use"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml7(literal)
-msgid "[app:object-server]"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml18(td)
-msgid "use = egg:swift#object"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml21(td)
-msgid "set log_name = object-server"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml36(td)
-msgid "max_upload_time = 86400"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml36(td)
-msgid "Maximum time allowed to upload an object"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml39(td)
-msgid "slow = 0"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml39(td)
-msgid ""
-"If &gt; 0, Minimum time in seconds for a PUT or DELETE request to complete"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml42(td)
-msgid "keep_cache_size = 5424880"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml42(td)
-msgid "Largest object size to keep in buffer cache"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml45(td)
-msgid "keep_cache_private = false"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml45(td)
-msgid "Allow non-public objects to stay in kernel's buffer cache"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml48(td)
-msgid "mb_per_sync = 512"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml48(td)
-msgid "On PUT requests, sync file every n MB"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml51(td)
-msgid ""
-"allowed_headers = Content-Disposition, Content-Encoding, X-Delete-At, X"
-"-Object-Manifest, X-Static-Large-Object"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml51(td)
-msgid ""
-"Comma-separated list of headers that can be set in metadata of an object"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml57(td)
-msgid "threads_per_disk = 0"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml57(td)
-msgid ""
-"Size of the per-disk thread pool used for performing disk I/O. The default "
-"of 0 means to not use a per-disk thread pool. It is recommended to keep this"
-" value small, as large values can result in high read latencies due to large"
-" queue depths. A good starting point is 4 threads per disk."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml63(td)
-msgid "replication_concurrency = 4"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml63(td)
-msgid ""
-"Set to restrict the number of concurrent incoming REPLICATION requests; set "
-"to 0 for unlimited"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml66(td)
-msgid "replication_one_per_device = True"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml66(td)
-msgid ""
-"Restricts incoming REPLICATION requests to one per device, "
-"replication_currency above allowing. This can help control I/O to each "
-"device, but you may wish to set this to False to allow multiple REPLICATION "
-"requests (up to the above replication_concurrency setting) per device."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml69(td)
-msgid "replication_lock_timeout = 15"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml69(td)
-msgid ""
-"Number of seconds to wait for an existing replication device lock before "
-"giving up."
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml72(td)
-msgid "replication_failure_threshold = 100"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml72(td)
-msgid ""
-"The number of subrequest failures before the replication_failure_ratio is "
-"checked"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml75(td)
-msgid "replication_failure_ratio = 1.0"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-server-app-object-server.xml75(td)
-msgid ""
-"If the value of failures / successes of REPLICATION subrequests exceeds this"
-" ratio, the overall REPLICATION request will be aborted"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_couchbase.xml8(caption)
-msgid "Description of configuration options for db_couchbase"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_couchbase.xml19(th)
-msgid "[couchbase]"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_couchbase.xml26(td)
-msgid "mount_point = /var/lib/couchbase"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_couchbase.xml30(td)
-msgid "tcp_ports = 8091, 8092, 4369, 11209-11211, 21100-21199"
-msgstr ""
-
-#: ./doc/common/tables/neutron-policy.xml22(td)
-msgid "allow_overlapping_ips = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-policy.xml23(td)
-msgid "(BoolOpt) Allow overlapping IP support in Neutron"
-msgstr ""
-
-#: ./doc/common/tables/neutron-policy.xml27(td)
-msgid "(StrOpt) The policy file to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rootwrap.xml22(td)
-msgid ""
-"filters_path = "
-"/etc/neutron/rootwrap.d,/usr/share/neutron/rootwrap,/etc/quantum/rootwrap.d,/usr/share/quantum/rootwrap"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rootwrap.xml42(th)
-msgid "[xenapi]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rootwrap.xml45(td)
-msgid "xenapi_connection_url = &lt;None&gt;"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rootwrap.xml46(td)
-msgid ""
-"XenAPI configuration is only required by the L2 agent if it is to target a "
-"XenServer/XCP compute host's dom0."
-msgstr ""
-
-#: ./doc/common/tables/neutron-rootwrap.xml49(td)
-#: ./doc/common/tables/cinder-storage_xen.xml30(td)
-msgid "xenapi_connection_username = root"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rootwrap.xml53(td)
-msgid "xenapi_connection_password = &lt;None&gt;"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml21(td)
-msgid "bind_port = 80"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml36(td)
-msgid "expose_info = true"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml36(td)
-msgid "Enables exposing configuration settings via HTTP GET /info."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml39(td)
-msgid "admin_key = secret_admin_key"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml39(td)
-msgid ""
-"to use for admin calls that are HMAC signed. Default is empty, which will "
-"disable admin calls to /info. the proxy server. For most cases, this should "
-"be `egg:swift#proxy`. request whenever it has to failover to a handoff node"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml42(td)
-msgid "disallowed_sections = container_quotas, tempurl"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml58(td)
-msgid "cert_file = /etc/swift/proxy.crt"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml58(td)
-msgid "to the ssl .crt. This should be enabled for testing purposes only."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml61(td)
-msgid "key_file = /etc/swift/proxy.key"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml61(td)
-msgid "to the ssl .key. This should be enabled for testing purposes only."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml79(td)
-msgid "log_headers = false"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml85(td)
-msgid "trans_id_suffix ="
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml115(td)
-msgid "cors_allow_origin ="
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-DEFAULT.xml115(td)
-msgid ""
-"is a list of hosts that are included with any CORS request by default and "
-"returned with the Access-Control-Allow-Origin header in addition to what the"
-" container has set. to call to setup custom log handlers. for eventlet the "
-"proxy server. For most cases, this should be `egg:swift#proxy`. request "
-"whenever it has to failover to a handoff node"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml7(literal)
-msgid "[filter:staticweb]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml18(td)
-msgid "use = egg:swift#staticweb"
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml22(td)
-msgid "configurations_page_size = 20"
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml26(td)
-msgid "databases_page_size = 20"
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml30(td)
-msgid "default_datastore = None"
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml31(td)
-msgid ""
-"(StrOpt) The default datastore id or name to use if one is not provided by "
-"the user. If the default value is None, the field becomes required in the "
-"instance-create request."
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml38(td)
-msgid "default_neutron_networks ="
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml39(td)
-msgid ""
-"(ListOpt) List of network IDs which should be attached to instance when "
-"networks are not specified in API call."
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml46(td)
-msgid "default_password_length = 36"
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml54(td)
-msgid "expected_filetype_suffixes = json"
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml55(td)
-msgid ""
-"(ListOpt) Filetype endings not to be reattached to an id by the utils method"
-" correct_id_with_req."
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml62(td)
-msgid "pybasedir = /usr/lib/python/site-packages/trove"
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml63(td)
-msgid "(StrOpt) Directory where the trove python module is installed."
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml66(td)
-msgid "pydev_path = None"
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml67(td)
-msgid ""
-"(StrOpt) Set path to pydevd library, used if pydevd is not found in python "
-"sys.path."
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml70(td)
-msgid "taskmanager_queue = taskmanager"
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml74(td)
-msgid "template_path = /etc/trove/templates/"
-msgstr ""
-
-#: ./doc/common/tables/trove-common.xml75(td)
-msgid "(StrOpt) Path which leads to datastore templates."
-msgstr ""
-
-#: ./doc/common/tables/cinder-ssl.xml8(caption)
-#: ./doc/common/tables/neutron-ssl.xml8(caption)
-#: ./doc/common/tables/trove-ssl.xml8(caption)
-#: ./doc/common/tables/glance-ssl.xml8(caption)
-#: ./doc/common/tables/keystone-ssl.xml8(caption)
-#: ./doc/common/tables/ceilometer-ssl.xml8(caption)
-msgid "Description of configuration options for ssl"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml22(td)
-#: ./doc/common/tables/heat-metadata_api.xml22(td)
-msgid "heat_metadata_server_url ="
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml23(td)
-#: ./doc/common/tables/heat-metadata_api.xml23(td)
-msgid "(StrOpt) URL of the Heat metadata server."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml26(td)
-msgid "heat_stack_user_role = heat_stack_user"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml27(td)
-msgid "(StrOpt) Keystone role for heat template-defined users."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml38(td)
-msgid "max_json_body_size = 1048576"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml39(td)
-msgid ""
-"(IntOpt) Maximum raw byte size of JSON request body. Should be larger than "
-"max_template_size."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml50(td)
-msgid "secure_proxy_ssl_header = X-Forwarded-Proto"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml51(td)
-msgid ""
-"(StrOpt) The HTTP Header that will be used to determine which the original "
-"request protocol scheme was, even if it was removed by an SSL terminator "
-"proxy."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml54(td)
-msgid "stack_action_timeout = 3600"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml55(td)
-msgid "(IntOpt) Timeout in seconds for stack action (ie. create or update)."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml58(td)
-msgid "stack_domain_admin = None"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml59(td)
-msgid ""
-"(StrOpt) Keystone username, a user with roles sufficient to manage users and"
-" projects in the stack_user_domain."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml62(td)
-msgid "stack_domain_admin_password = None"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml63(td)
-msgid "(StrOpt) Keystone password for stack_domain_admin user."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml66(td)
-msgid "stack_user_domain = None"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml67(td)
-msgid ""
-"(StrOpt) Keystone domain ID which contains heat template-defined users."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml70(td)
-msgid "trusts_delegated_roles = heat_stack_owner"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml71(td)
-msgid "(ListOpt) Subset of trustor roles to be delegated to heat."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml74(th)
-msgid "[auth_password]"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml77(td)
-#: ./doc/common/tables/heat-api.xml88(td)
-msgid "allowed_auth_uris ="
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml78(td)
-#: ./doc/common/tables/heat-api.xml89(td)
-msgid ""
-"(ListOpt) Allowed keystone endpoints for auth_uri when multi_cloud is "
-"enabled. At least one endpoint needs to be specified."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml81(td)
-#: ./doc/common/tables/heat-api.xml96(td)
-msgid "multi_cloud = False"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml82(td)
-#: ./doc/common/tables/heat-api.xml97(td)
-msgid "(BoolOpt) Allow orchestration of multiple clouds."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml85(th)
-msgid "[ec2authtoken]"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml93(td)
-msgid "(StrOpt) Authentication Endpoint URI."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml100(th)
-msgid "[heat_api]"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml111(td)
-msgid "bind_port = 8004"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml131(th)
-#: ./doc/common/tables/glance-paste.xml19(th)
-#: ./doc/common/tables/keystone-api.xml101(th)
-msgid "[paste_deploy]"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml135(td)
-msgid "(StrOpt) The API paste config file to use."
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml138(td)
-#: ./doc/common/tables/glance-paste.xml26(td)
-msgid "flavor = None"
-msgstr ""
-
-#: ./doc/common/tables/heat-api.xml139(td)
-msgid "(StrOpt) The flavor to use."
-msgstr ""
-
-#: ./doc/common/tables/trove-db_percona.xml8(caption)
-msgid "Description of configuration options for db_percona"
-msgstr ""
-
-#: ./doc/common/tables/trove-db_percona.xml19(th)
-msgid "[percona]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml8(caption)
-msgid "Description of configuration options for meta"
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml19(th)
-msgid "[META]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml22(td)
-msgid "default_flavor ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml23(td)
-msgid "(StrOpt) Default flavor to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml26(td)
-msgid "default_l3_flavor ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml27(td)
-msgid "(StrOpt) Default L3 flavor to use"
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml30(td)
-msgid "extension_map ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml31(td)
-msgid "(StrOpt) A list of extensions, per plugin, to load."
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml34(td)
-msgid "l3_plugin_list ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml35(td)
-msgid "(StrOpt) List of L3 plugins to load"
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml38(td)
-msgid "plugin_list ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml39(td)
-msgid "(StrOpt) List of plugins to load"
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml42(td)
-msgid "rpc_flavor ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml43(td)
-msgid "(StrOpt) Flavor of which plugin handles RPC"
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml46(td)
-msgid "supported_extension_aliases ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-meta.xml47(td)
-msgid "(StrOpt) Supported extension aliases"
-msgstr ""
-
-#: ./doc/common/tables/neutron-redis.xml23(td)
-msgid "(StrOpt) The hostname Neutron is running on"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml8(caption)
-msgid "Description of configuration options for exchange"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml22(td)
-msgid "cinder_control_exchange = cinder"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml23(td)
-msgid "(StrOpt) Exchange name for Cinder notifications."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml34(td)
-msgid "glance_control_exchange = glance"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml35(td)
-msgid "(StrOpt) Exchange name for Glance notifications."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml38(td)
-msgid "heat_control_exchange = heat"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml39(td)
-msgid "(StrOpt) Exchange name for Heat notifications"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml42(td)
-msgid "http_control_exchanges = ['nova', 'glance', 'neutron', 'cinder']"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml43(td)
-msgid "(MultiStrOpt) Exchanges name to listen for notifications."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml46(td)
-msgid "neutron_control_exchange = neutron"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml47(td)
-msgid "(StrOpt) Exchange name for Neutron notifications."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml50(td)
-msgid "nova_control_exchange = nova"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml51(td)
-msgid "(StrOpt) Exchange name for Nova notifications."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml54(td)
-msgid "sample_source = openstack"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-exchange.xml55(td)
-msgid "(StrOpt) Source for samples emitted on this instance."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-common.xml27(td)
-msgid "(BoolOpt) Whether to disable inter-process locks."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-common.xml42(td)
-msgid "notification_workers = 1"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-common.xml43(td)
-msgid ""
-"(IntOpt) Number of workers for notification service. A single notification "
-"agent is enabled by default."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml8(caption)
-msgid "Description of configuration options for alarm"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml19(th)
-msgid "[alarm]"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml22(td)
-msgid "evaluation_interval = 60"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml23(td)
-msgid ""
-"(IntOpt) Period of evaluation cycle, should be &gt;= than configured "
-"pipeline interval for collection of underlying metrics."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml26(td)
-msgid "evaluation_service = ceilometer.alarm.service.SingletonAlarmService"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml27(td)
-msgid "(StrOpt) Class to launch as alarm evaluation service."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml30(td)
-msgid "notifier_rpc_topic = alarm_notifier"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml31(td)
-msgid "(StrOpt) The topic that ceilometer uses for alarm notifier messages."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml34(td)
-msgid "partition_rpc_topic = alarm_partition_coordination"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml35(td)
-msgid ""
-"(StrOpt) The topic that ceilometer uses for alarm partition coordination "
-"messages."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml38(td)
-msgid "record_history = True"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml39(td)
-msgid "(BoolOpt) Record alarm change events."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml42(td)
-msgid "rest_notifier_certificate_file ="
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml43(td)
-msgid "(StrOpt) SSL Client certificate for REST notifier."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml46(td)
-msgid "rest_notifier_certificate_key ="
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml47(td)
-msgid "(StrOpt) SSL Client private key for REST notifier."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml50(td)
-msgid "rest_notifier_ssl_verify = True"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-alarm.xml51(td)
-msgid ""
-"(BoolOpt) Whether to verify the SSL Server certificate when calling alarm "
-"action."
-msgstr ""
-
-#: ./doc/common/tables/keystone-misc.xml8(caption)
-msgid "Description of configuration options for misc"
+#: ./doc/common/tables/keystone-federation.xml27(td)
+msgid "(StrOpt) Keystone Federation backend driver."
 msgstr ""
 
 #: ./doc/common/tables/nova-scheduling.xml8(caption)
@@ -45038,13 +44614,6 @@ msgid ""
 "ServerGroupAntiAffinityFilter, ServerGroupAffinityFilter"
 msgstr ""
 
-#: ./doc/common/tables/nova-scheduling.xml79(td)
-#: ./doc/common/tables/cinder-scheduler.xml23(td)
-msgid ""
-"(ListOpt) Which filter class names to use for filtering hosts when not "
-"specified in the request."
-msgstr ""
-
 #: ./doc/common/tables/nova-scheduling.xml82(td)
 msgid "scheduler_driver = nova.scheduler.filter_scheduler.FilterScheduler"
 msgstr ""
@@ -45069,11 +44638,6 @@ msgstr ""
 msgid "scheduler_host_manager = nova.scheduler.host_manager.HostManager"
 msgstr ""
 
-#: ./doc/common/tables/nova-scheduling.xml91(td)
-#: ./doc/common/tables/cinder-scheduler.xml35(td)
-msgid "(StrOpt) The scheduler host manager class to use"
-msgstr ""
-
 #: ./doc/common/tables/nova-scheduling.xml94(td)
 msgid "scheduler_host_subset_size = 1"
 msgstr ""
@@ -45087,16 +44651,6 @@ msgid ""
 "will be ignored, and 1 will be used instead"
 msgstr ""
 
-#: ./doc/common/tables/nova-scheduling.xml98(td)
-#: ./doc/common/tables/cinder-scheduler.xml38(td)
-msgid "scheduler_json_config_location ="
-msgstr ""
-
-#: ./doc/common/tables/nova-scheduling.xml99(td)
-#: ./doc/common/tables/cinder-scheduler.xml39(td)
-msgid "(StrOpt) Absolute path to scheduler configuration JSON file."
-msgstr ""
-
 #: ./doc/common/tables/nova-scheduling.xml102(td)
 msgid "scheduler_manager = nova.scheduler.manager.SchedulerManager"
 msgstr ""
@@ -45105,11 +44659,6 @@ msgstr ""
 msgid "(StrOpt) Full class name for the Manager for scheduler"
 msgstr ""
 
-#: ./doc/common/tables/nova-scheduling.xml106(td)
-#: ./doc/common/tables/cinder-scheduler.xml46(td)
-msgid "scheduler_max_attempts = 3"
-msgstr ""
-
 #: ./doc/common/tables/nova-scheduling.xml107(td)
 msgid "(IntOpt) Maximum number of attempts to schedule an instance"
 msgstr ""
@@ -45221,230 +44770,699 @@ msgid ""
 "weight would be name1.value * 1.0 + name2.value * -1.0."
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml133(th)
-msgid "[service_credentials]"
+#: ./doc/common/tables/cinder-eqlx.xml8(caption)
+msgid "Description of configuration options for eqlx"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml137(td)
+#: ./doc/common/tables/cinder-eqlx.xml22(td)
+msgid "eqlx_chap_login = admin"
+msgstr ""
+
+#: ./doc/common/tables/cinder-eqlx.xml23(td)
+msgid "(StrOpt) Existing CHAP account name"
+msgstr ""
+
+#: ./doc/common/tables/cinder-eqlx.xml26(td)
+msgid "eqlx_chap_password = password"
+msgstr ""
+
+#: ./doc/common/tables/cinder-eqlx.xml27(td)
+msgid "(StrOpt) Password for specified CHAP account name"
+msgstr ""
+
+#: ./doc/common/tables/cinder-eqlx.xml30(td)
+msgid "eqlx_cli_max_retries = 5"
+msgstr ""
+
+#: ./doc/common/tables/cinder-eqlx.xml31(td)
+msgid "(IntOpt) Maximum retry count for reconnection"
+msgstr ""
+
+#: ./doc/common/tables/cinder-eqlx.xml34(td)
+msgid "eqlx_cli_timeout = 30"
+msgstr ""
+
+#: ./doc/common/tables/cinder-eqlx.xml35(td)
+msgid "(IntOpt) Timeout for the Group Manager cli command execution"
+msgstr ""
+
+#: ./doc/common/tables/cinder-eqlx.xml38(td)
+msgid "eqlx_group_name = group-0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-eqlx.xml39(td)
+msgid "(StrOpt) Group name to use for creating volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-eqlx.xml42(td)
+msgid "eqlx_pool = default"
+msgstr ""
+
+#: ./doc/common/tables/cinder-eqlx.xml43(td)
+msgid "(StrOpt) Pool in which volumes will be created"
+msgstr ""
+
+#: ./doc/common/tables/cinder-eqlx.xml46(td)
+msgid "eqlx_use_chap = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-eqlx.xml47(td)
+msgid "(BoolOpt) Use CHAP authentication for targets?"
+msgstr ""
+
+#: ./doc/common/tables/heat-redis.xml23(td)
 msgid ""
-"(BoolOpt) Disables X.509 certificate validation when an SSL connection to "
-"Identity Service is established."
+"(StrOpt) Name of the engine node. This can be an opaque identifier. It is "
+"not necessarily a hostname, FQDN, or IP address."
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml140(td)
-msgid "os_auth_url = http://localhost:5000/v2.0"
+#: ./doc/common/tables/nova-ec2.xml8(caption)
+#: ./doc/common/tables/keystone-ec2.xml8(caption)
+msgid "Description of configuration options for ec2"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml141(td)
-msgid "(StrOpt) Auth URL to use for OpenStack service access."
+#: ./doc/common/tables/nova-ec2.xml22(td)
+msgid "ec2_dmz_host = $my_ip"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml144(td)
-msgid "os_cacert = None"
+#: ./doc/common/tables/nova-ec2.xml23(td)
+msgid "(StrOpt) The internal IP address of the EC2 API server"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml145(td)
-msgid "(StrOpt) Certificate chain for SSL validation."
+#: ./doc/common/tables/nova-ec2.xml26(td)
+msgid "ec2_host = $my_ip"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml148(td)
-msgid "os_endpoint_type = publicURL"
+#: ./doc/common/tables/nova-ec2.xml27(td)
+msgid "(StrOpt) The IP address of the EC2 API server"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml149(td)
+#: ./doc/common/tables/nova-ec2.xml30(td)
+msgid "ec2_listen = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-ec2.xml31(td)
+msgid "(StrOpt) The IP address on which the EC2 API will listen."
+msgstr ""
+
+#: ./doc/common/tables/nova-ec2.xml34(td)
+msgid "ec2_listen_port = 8773"
+msgstr ""
+
+#: ./doc/common/tables/nova-ec2.xml35(td)
+msgid "(IntOpt) The port on which the EC2 API will listen."
+msgstr ""
+
+#: ./doc/common/tables/nova-ec2.xml38(td)
+msgid "ec2_path = /services/Cloud"
+msgstr ""
+
+#: ./doc/common/tables/nova-ec2.xml39(td)
+msgid "(StrOpt) The path prefix used to call the ec2 API server"
+msgstr ""
+
+#: ./doc/common/tables/nova-ec2.xml42(td)
+msgid "ec2_port = 8773"
+msgstr ""
+
+#: ./doc/common/tables/nova-ec2.xml43(td)
+msgid "(IntOpt) The port of the EC2 API server"
+msgstr ""
+
+#: ./doc/common/tables/nova-ec2.xml46(td)
+msgid "ec2_private_dns_show_ip = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-ec2.xml47(td)
 msgid ""
-"(StrOpt) Type of endpoint in Identity service catalog to use for "
-"communication with OpenStack services."
+"(BoolOpt) Return the IP address as private dns hostname in describe "
+"instances"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml152(td)
-msgid "os_password = admin"
+#: ./doc/common/tables/nova-ec2.xml50(td)
+msgid "ec2_scheme = http"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-auth.xml153(td)
-msgid "(StrOpt) Password to use for OpenStack service access."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-auth.xml157(td)
-msgid "(StrOpt) Region name to use for OpenStack service endpoints."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-auth.xml160(td)
-msgid "os_tenant_id ="
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-auth.xml161(td)
-msgid "(StrOpt) Tenant ID to use for OpenStack service access."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-auth.xml164(td)
-msgid "os_tenant_name = admin"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-auth.xml165(td)
-msgid "(StrOpt) Tenant name to use for OpenStack service access."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-auth.xml168(td)
-msgid "os_username = ceilometer"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-auth.xml169(td)
-msgid "(StrOpt) User name to use for OpenStack service access."
-msgstr ""
-
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml7(literal)
-msgid "[drive-audit]"
-msgstr ""
-
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml7(literal)
-msgid "drive-audit.conf-sample"
-msgstr ""
-
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml18(td)
-msgid "device_dir = /srv/node"
-msgstr ""
-
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml18(td)
-msgid "Directory devices are mounted under"
-msgstr ""
-
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml30(td)
-msgid "minutes = 60"
-msgstr ""
-
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml30(td)
-msgid "Number of minutes to look back in `/var/log/kern.log`"
-msgstr ""
-
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml33(td)
-msgid "error_limit = 1"
-msgstr ""
-
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml33(td)
-msgid "Number of errors to find before a device is unmounted"
-msgstr ""
-
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml36(td)
-msgid "log_file_pattern = /var/log/kern*"
-msgstr ""
-
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml36(td)
+#: ./doc/common/tables/nova-ec2.xml51(td)
 msgid ""
-"Location of the log file with globbing pattern to check against device "
-"errors locate device blocks with errors in the log file"
+"(StrOpt) The protocol to use when connecting to the EC2 API server (http, "
+"https)"
 msgstr ""
 
-#: ./doc/common/tables/swift-drive-audit-drive-audit.xml39(td)
-msgid "regex_pattern_1 = \\berror\\b.*\\b(dm-[0-9]{1,2}\\d?)\\b"
+#: ./doc/common/tables/nova-ec2.xml54(td)
+msgid "ec2_strict_validation = True"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_mlnx.xml8(caption)
-msgid "Description of configuration options for ml2_mlnx"
+#: ./doc/common/tables/nova-ec2.xml55(td)
+msgid "(BoolOpt) Validate security group names according to EC2 specification"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_mlnx.xml22(td)
-msgid "apply_profile_patch = False"
+#: ./doc/common/tables/nova-ec2.xml58(td)
+msgid "ec2_timestamp_expiry = 300"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_mlnx.xml23(td)
-msgid "(BoolOpt) Enable server compatibility with old nova"
+#: ./doc/common/tables/nova-ec2.xml59(td)
+msgid "(IntOpt) Time in seconds before ec2 timestamp expires"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_mlnx.xml26(td)
-msgid "vnic_type = mlnx_direct"
+#: ./doc/common/tables/nova-ec2.xml62(td)
+msgid "ec2_workers = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_mlnx.xml27(td)
-msgid "(StrOpt) Type of VM network interface: mlnx_direct or hostdev"
+#: ./doc/common/tables/nova-ec2.xml63(td)
+msgid ""
+"(IntOpt) Number of workers for EC2 API service. The default will be equal to"
+" the number of CPUs available."
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml8(caption)
-msgid "Description of configuration options for dns"
+#: ./doc/common/tables/nova-ec2.xml66(td)
+#: ./doc/common/tables/keystone-ec2.xml38(td)
+msgid "keystone_ec2_url = http://localhost:5000/v2.0/ec2tokens"
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml22(td)
-msgid "dns_account_id ="
+#: ./doc/common/tables/nova-ec2.xml67(td)
+#: ./doc/common/tables/keystone-ec2.xml39(td)
+msgid "(StrOpt) URL to get token from ec2 request."
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml26(td)
-msgid "dns_auth_url ="
+#: ./doc/common/tables/nova-ec2.xml70(td)
+msgid "lockout_attempts = 5"
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml30(td)
-msgid "dns_domain_id ="
+#: ./doc/common/tables/nova-ec2.xml71(td)
+msgid "(IntOpt) Number of failed auths before lockout."
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml34(td)
-msgid "dns_domain_name ="
+#: ./doc/common/tables/nova-ec2.xml74(td)
+msgid "lockout_minutes = 15"
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml38(td)
-msgid "dns_driver = trove.dns.driver.DnsDriver"
+#: ./doc/common/tables/nova-ec2.xml75(td)
+msgid "(IntOpt) Number of minutes to lockout if triggered."
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml42(td)
-msgid "dns_endpoint_url = 0.0.0.0"
+#: ./doc/common/tables/nova-ec2.xml78(td)
+msgid "lockout_window = 15"
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml46(td)
-msgid "dns_hostname ="
+#: ./doc/common/tables/nova-ec2.xml79(td)
+msgid "(IntOpt) Number of minutes for lockout window."
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml50(td)
-msgid "dns_instance_entry_factory = trove.dns.driver.DnsInstanceEntryFactory"
+#: ./doc/common/tables/nova-ec2.xml82(td)
+msgid "region_list ="
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml54(td)
-msgid "dns_management_base_url ="
+#: ./doc/common/tables/nova-ec2.xml83(td)
+msgid "(ListOpt) List of region=fqdn pairs separated by commas"
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml58(td)
-msgid "dns_passkey ="
+#: ./doc/common/tables/keystone-credential.xml8(caption)
+msgid "Description of configuration options for credential"
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml62(td)
-msgid "dns_region ="
+#: ./doc/common/tables/keystone-credential.xml19(th)
+msgid "[credential]"
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml66(td)
-msgid "dns_service_type ="
+#: ./doc/common/tables/keystone-credential.xml22(td)
+msgid "driver = keystone.credential.backends.sql.Credential"
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml70(td)
-msgid "dns_time_out = 120"
+#: ./doc/common/tables/cinder-block-device.xml8(caption)
+msgid "Description of configuration options for block-device"
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml74(td)
-msgid "dns_ttl = 300"
+#: ./doc/common/tables/cinder-block-device.xml22(td)
+msgid "available_devices ="
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml78(td)
-msgid "dns_username ="
+#: ./doc/common/tables/cinder-block-device.xml23(td)
+msgid "(ListOpt) List of all available devices"
 msgstr ""
 
-#: ./doc/common/tables/trove-dns.xml82(td)
-msgid "trove_dns_support = False"
+#: ./doc/common/tables/neutron-metadata.xml22(td)
+msgid "meta_flavor_driver_mappings = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-db.xml22(td)
-msgid "sqlite_db ="
+#: ./doc/common/tables/neutron-metadata.xml23(td)
+msgid "(StrOpt) Mapping between flavor and LinuxInterfaceDriver"
 msgstr ""
 
-#: ./doc/common/tables/neutron-db.xml37(td)
-msgid "connection = sqlite://"
+#: ./doc/common/tables/neutron-metadata.xml26(td)
+msgid "metadata_backlog = 128"
 msgstr ""
 
-#: ./doc/common/tables/neutron-db.xml69(td)
-msgid "max_overflow = 20"
+#: ./doc/common/tables/neutron-metadata.xml27(td)
+msgid ""
+"(IntOpt) Number of backlog requests to configure the metadata server socket "
+"with"
 msgstr ""
 
-#: ./doc/common/tables/neutron-db.xml73(td)
-msgid "max_pool_size = 10"
+#: ./doc/common/tables/neutron-metadata.xml30(td)
+msgid "metadata_port = 9697"
 msgstr ""
 
-#: ./doc/common/tables/neutron-db.xml85(td)
-msgid "pool_timeout = 10"
+#: ./doc/common/tables/neutron-metadata.xml31(td)
+msgid "(IntOpt) TCP Port used by Neutron metadata namespace proxy."
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml34(td)
+msgid "metadata_proxy_shared_secret ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml38(td)
+msgid "metadata_proxy_socket = $state_path/metadata_proxy"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml39(td)
+msgid "(StrOpt) Location of Metadata Proxy UNIX domain socket"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml42(td)
+msgid "metadata_workers = 0"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml43(td)
+msgid "(IntOpt) Number of separate worker processes for metadata server"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml46(td)
+msgid "nova_metadata_ip = 127.0.0.1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml47(td)
+msgid "(StrOpt) IP address used by Nova metadata server."
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml50(td)
+msgid "nova_metadata_port = 8775"
+msgstr ""
+
+#: ./doc/common/tables/neutron-metadata.xml51(td)
+msgid "(IntOpt) TCP Port used by Nova metadata server."
+msgstr ""
+
+#: ./doc/common/tables/nova-fping.xml8(caption)
+msgid "Description of configuration options for fping"
+msgstr ""
+
+#: ./doc/common/tables/nova-fping.xml22(td)
+msgid "fping_path = /usr/sbin/fping"
+msgstr ""
+
+#: ./doc/common/tables/nova-fping.xml23(td)
+msgid "(StrOpt) Full path to fping."
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml7(literal)
+msgid "[filter:staticweb]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-staticweb.xml18(td)
+msgid "use = egg:swift#staticweb"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-replicator.xml7(literal)
+msgid "[container-replicator]"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-server-container-replicator.xml18(td)
+msgid "log_name = container-replicator"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ncs.xml8(caption)
+msgid "Description of configuration options for ml2_ncs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ncs.xml19(th)
+msgid "[ml2_ncs]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ncs.xml23(td)
+#: ./doc/common/tables/neutron-ml2_odl.xml23(td)
+msgid "(StrOpt) HTTP password for authentication"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ncs.xml26(td)
+#: ./doc/common/tables/neutron-ml2_odl.xml30(td)
+msgid "timeout = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ncs.xml27(td)
+#: ./doc/common/tables/neutron-ml2_odl.xml31(td)
+msgid "(IntOpt) HTTP timeout in seconds."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ncs.xml31(td)
+msgid "(StrOpt) HTTP URL of Tail-f NCS REST interface."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ncs.xml34(td)
+#: ./doc/common/tables/neutron-ml2_odl.xml38(td)
+msgid "username = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_ncs.xml35(td)
+#: ./doc/common/tables/neutron-ml2_odl.xml39(td)
+msgid "(StrOpt) HTTP username for authentication"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml8(caption)
+msgid "Description of configuration options for ml2_arista"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml19(th)
+msgid "[ml2_arista]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml22(td)
+msgid "eapi_host ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml23(td)
+msgid ""
+"(StrOpt) Arista EOS IP address. This is required field.If not set, all "
+"communications to Arista EOSwill fail"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml26(td)
+msgid "eapi_password ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml27(td)
+msgid ""
+"(StrOpt) Password for Arista EOS. This is required field.if not set, all "
+"communications to Arista EOSwill fail"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml30(td)
+msgid "eapi_username ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml31(td)
+msgid ""
+"(StrOpt) Username for Arista EOS. This is required field.if not set, all "
+"communications to Arista EOSwill fail"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml34(td)
+msgid "region_name = RegionOne"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml35(td)
+msgid ""
+"(StrOpt) Defines Region Name that is assigned to this OpenStackController. "
+"This is useful when multipleOpenStack/Neutron controllers are managing the "
+"sameArista HW clusters. Note that this name must match withthe region name "
+"registered (or known) to keystoneservice. Authentication with Keysotne is "
+"performed byEOS. This is optional. If not set, a value of\"RegionOne\" is "
+"assumed"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml38(td)
+msgid "sync_interval = 180"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml39(td)
+msgid ""
+"(IntOpt) Sync interval in seconds between Neutron plugin andEOS. This "
+"interval defines how often thesynchronization is performed. This is an "
+"optionalfield. If not set, a value of 180 seconds is assumed"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml42(td)
+msgid "use_fqdn = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_arista.xml43(td)
+msgid ""
+"(BoolOpt) Defines if hostnames are sent to Arista EOS as "
+"FQDNs(\"node1.domain.com\") or as short names (\"node1\").This is optional. "
+"If not set, a value of \"True\"is assumed."
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml8(caption)
+msgid "Description of configuration options for trustedcomputing"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml19(th)
+msgid "[trusted_computing]"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml22(td)
+msgid "attestation_api_url = /OpenAttestationWebServices/V1.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml23(td)
+msgid "(StrOpt) Attestation web API URL"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml26(td)
+msgid "attestation_auth_blob = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml27(td)
+msgid "(StrOpt) Attestation authorization blob - must change"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml30(td)
+msgid "attestation_auth_timeout = 60"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml31(td)
+msgid "(IntOpt) Attestation status cache valid period length"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml34(td)
+msgid "attestation_port = 8443"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml35(td)
+msgid "(StrOpt) Attestation server port"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml38(td)
+msgid "attestation_server = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml39(td)
+msgid "(StrOpt) Attestation server HTTP"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml42(td)
+msgid "attestation_server_ca_file = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-trustedcomputing.xml43(td)
+msgid "(StrOpt) Attestation server Cert file for Identity verification"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml7(literal)
+msgid "[filter:bulk]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml18(td)
+msgid "use = egg:swift#bulk"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml21(td)
+msgid "max_containers_per_extraction = 10000"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml24(td)
+msgid "max_failed_extractions = 1000"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml27(td)
+msgid "max_deletes_per_request = 10000"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml30(td)
+msgid "max_failed_deletes = 1000"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml33(td)
+msgid "yield_frequency = 10"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-bulk.xml36(td)
+msgid "delete_container_retry_count = 0"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml22(td)
+msgid "notify_nova_on_port_data_changes = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml23(td)
+msgid ""
+"(BoolOpt) Send notification to nova when port data (fixed_ips/floatingip) "
+"changes so nova can update its cache."
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml26(td)
+msgid "notify_nova_on_port_status_changes = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml27(td)
+msgid "(BoolOpt) Send notification to nova when port status changes"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml30(td)
+msgid "nova_admin_auth_url = http://localhost:5000/v2.0"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml31(td)
+msgid "(StrOpt) Authorization URL for connecting to nova in admin context"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml34(td)
+msgid "nova_admin_password = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml35(td)
+msgid "(StrOpt) Password for connection to nova in admin context"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml38(td)
+msgid "nova_admin_tenant_id = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml39(td)
+msgid "(StrOpt) The uuid of the admin nova tenant"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml42(td)
+msgid "nova_admin_username = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml43(td)
+msgid "(StrOpt) Username for connecting to nova in admin context"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml46(td)
+msgid "nova_region_name = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml47(td)
+msgid ""
+"(StrOpt) Name of nova region to use. Useful if keystone manages more than "
+"one region."
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml50(td)
+msgid "nova_url = http://127.0.0.1:8774"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml51(td)
+msgid "(StrOpt) URL for connection to nova"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml54(td)
+msgid "send_events_interval = 2"
+msgstr ""
+
+#: ./doc/common/tables/neutron-compute.xml55(td)
+msgid ""
+"(IntOpt) Number of seconds between sending events to nova if there are any "
+"events to send."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml8(caption)
+msgid "Description of configuration options for imagecache"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml22(td)
+msgid "cleanup_scrubber = False"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml23(td)
+msgid ""
+"(BoolOpt) A boolean that determines if the scrubber should clean up the "
+"files it uses for taking data. Only one server in your deployment should be "
+"designated the cleanup host."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml26(td)
+msgid "cleanup_scrubber_time = 86400"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml27(td)
+msgid ""
+"(IntOpt) Items must have a modified time that is older than this value in "
+"order to be candidates for cleanup."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml30(td)
+msgid "delayed_delete = False"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml31(td)
+msgid "(BoolOpt) Turn on/off delayed delete."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml34(td)
+msgid "image_cache_dir = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml35(td)
+msgid "(StrOpt) Base directory that the Image Cache uses."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml38(td)
+msgid "image_cache_driver = sqlite"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml39(td)
+msgid "(StrOpt) The driver to use for image cache management."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml42(td)
+msgid "image_cache_max_size = 10737418240"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml43(td)
+msgid "(IntOpt) The maximum size in bytes that the cache can use."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml46(td)
+msgid "image_cache_sqlite_db = cache.db"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml47(td)
+msgid ""
+"(StrOpt) The path to the sqlite file database that will be used for image "
+"cache management."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml50(td)
+msgid "image_cache_stall_time = 86400"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml51(td)
+msgid ""
+"(IntOpt) The amount of time to let an image remain in the cache without "
+"being accessed."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml54(td)
+msgid "scrub_time = 0"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml55(td)
+msgid ""
+"(IntOpt) The amount of time in seconds to delay before performing a delete."
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml58(td)
+msgid "scrubber_datadir = /var/lib/glance/scrubber"
+msgstr ""
+
+#: ./doc/common/tables/glance-imagecache.xml59(td)
+msgid ""
+"(StrOpt) Directory that the scrubber will use to track information about "
+"what to delete. Make sure this is set in glance-api.conf and glance-"
+"scrubber.conf."
 msgstr ""
 
 #: ./doc/common/tables/neutron-ml2_brocade.xml8(caption)
@@ -45497,6 +45515,91 @@ msgstr ""
 msgid "(StrOpt) The SSH username to use"
 msgstr ""
 
+#: ./doc/common/tables/swift-account-server-account-auditor.xml7(literal)
+msgid "[account-auditor]"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-auditor.xml18(td)
+msgid "log_name = account-auditor"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-auditor.xml39(td)
+msgid "accounts_per_second = 200"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-account-auditor.xml39(td)
+msgid ""
+"Maximum accounts audited per second. Should be tuned according to individual"
+" system specs. 0 is unlimited."
+msgstr ""
+
+#: ./doc/common/tables/cinder-nas.xml8(caption)
+msgid "Description of configuration options for nas"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nas.xml22(td)
+msgid "nas_ip ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-nas.xml23(td)
+msgid "(StrOpt) IP address or Hostname of NAS system."
+msgstr ""
+
+#: ./doc/common/tables/cinder-nas.xml26(td)
+msgid "nas_login = admin"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nas.xml27(td)
+msgid "(StrOpt) User name to connect to NAS system."
+msgstr ""
+
+#: ./doc/common/tables/cinder-nas.xml30(td)
+msgid "nas_password ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-nas.xml31(td)
+msgid "(StrOpt) Password to connect to NAS system."
+msgstr ""
+
+#: ./doc/common/tables/cinder-nas.xml34(td)
+msgid "nas_private_key ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-nas.xml35(td)
+msgid "(StrOpt) Filename of private key to use for SSH authentication."
+msgstr ""
+
+#: ./doc/common/tables/cinder-nas.xml38(td)
+msgid "nas_ssh_port = 22"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nas.xml39(td)
+msgid "(IntOpt) SSH port to use to connect to NAS system."
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml8(caption)
+msgid "Description of configuration options for netapp_cdot_nfs"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml26(td)
+msgid "netapp_copyoffload_tool_path = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml27(td)
+msgid ""
+"(StrOpt) This option specifies the path of the NetApp copy offload tool "
+"binary. Ensure that the binary has execute permissions set which allow the "
+"effective user of the cinder-volume process to execute the file."
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_swift.xml8(caption)
+msgid "Description of configuration options for clients_swift"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_swift.xml19(th)
+msgid "[clients_swift]"
+msgstr ""
+
 #: ./doc/common/tables/neutron-brocade.xml8(caption)
 msgid "Description of configuration options for brocade"
 msgstr ""
@@ -45529,299 +45632,6 @@ msgstr ""
 msgid "username ="
 msgstr ""
 
-#: ./doc/common/tables/keystone-database.xml74(td)
-#: ./doc/common/tables/glance-db.xml74(td)
-msgid "mysql_sql_mode = TRADITIONAL"
-msgstr ""
-
-#: ./doc/common/tables/keystone-database.xml75(td)
-#: ./doc/common/tables/glance-db.xml75(td)
-msgid ""
-"(StrOpt) The SQL mode to be used for MySQL sessions. This option, including "
-"the default, overrides any server-set SQL mode. To use whatever SQL mode is "
-"set by the server configuration, set this to no value. Example: "
-"mysql_sql_mode="
-msgstr ""
-
-#: ./doc/common/tables/keystone-database.xml86(td)
-msgid "sqlite_db = keystone.sqlite"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-expirer-pipeline-main.xml18(td)
-msgid "pipeline = catch_errors cache proxy-server"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_neutron.xml8(caption)
-msgid "Description of configuration options for clients_neutron"
-msgstr ""
-
-#: ./doc/common/tables/heat-clients_neutron.xml19(th)
-msgid "[clients_neutron]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml8(caption)
-msgid "Description of configuration options for linuxbridge_agent"
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml19(th)
-msgid "[LINUX_BRIDGE]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml26(th)
-msgid "[VLANS]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml37(th)
-msgid "[VXLAN]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml40(td)
-msgid "enable_vxlan = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml41(td)
-msgid ""
-"(BoolOpt) Enable VXLAN on the agent. Can be enabled when agent is managed by"
-" ml2 plugin using linuxbridge mechanism driver"
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml45(td)
-msgid ""
-"(BoolOpt) Extension to use alongside ml2 plugin's l2population mechanism "
-"driver. It enables the plugin to populate VXLAN forwarding table."
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml49(td)
-msgid "(StrOpt) Local IP address of the VXLAN endpoints."
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml52(td)
-msgid "tos = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml53(td)
-msgid "(IntOpt) TOS for vxlan interface protocol packets."
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml56(td)
-msgid "ttl = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml57(td)
-msgid "(IntOpt) TTL for vxlan interface protocol packets."
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml60(td)
-msgid "vxlan_group = 224.0.0.1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-linuxbridge_agent.xml61(td)
-msgid "(StrOpt) Multicast group for vxlan interface."
-msgstr ""
-
-#: ./doc/common/tables/cinder-xiv.xml8(caption)
-msgid "Description of configuration options for xiv"
-msgstr ""
-
-#: ./doc/common/tables/cinder-xiv.xml22(td)
-msgid "xiv_chap = disabled"
-msgstr ""
-
-#: ./doc/common/tables/cinder-xiv.xml23(td)
-msgid ""
-"(StrOpt) CHAP authentication mode, effective only for iscsi "
-"(disabled|enabled)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-xiv.xml26(td)
-msgid "xiv_ds8k_connection_type = iscsi"
-msgstr ""
-
-#: ./doc/common/tables/cinder-xiv.xml27(td)
-msgid ""
-"(StrOpt) Connection type to the IBM Storage Array (fibre_channel|iscsi)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-xiv.xml30(td)
-msgid "xiv_ds8k_proxy = xiv_ds8k_openstack.nova_proxy.XIVDS8KNovaProxy"
-msgstr ""
-
-#: ./doc/common/tables/cinder-xiv.xml31(td)
-msgid "(StrOpt) Proxy driver that connects to the IBM Storage Array"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hds-hus.xml8(caption)
-msgid "Description of configuration options for hds-hus"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hds-hus.xml22(td)
-msgid "hds_cinder_config_file = /opt/hds/hus/cinder_hus_conf.xml"
-msgstr ""
-
-#: ./doc/common/tables/cinder-hds-hus.xml23(td)
-msgid "(StrOpt) configuration file for HDS cinder plugin for HUS"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rabbitmq.xml35(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml55(td)
-msgid ""
-"(IntOpt) Maximum number of RabbitMQ connection retries. Default is 0 "
-"(infinite retry count)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rabbitmq.xml39(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml59(td)
-msgid "(StrOpt) The RabbitMQ password"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rabbitmq.xml47(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml67(td)
-msgid ""
-"(IntOpt) How long to backoff for between retries when connecting to RabbitMQ"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rabbitmq.xml51(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml71(td)
-msgid "(IntOpt) How frequently to retry connecting with RabbitMQ"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rabbitmq.xml55(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml75(td)
-msgid "(BoolOpt) Connect over SSL for RabbitMQ"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rabbitmq.xml59(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml79(td)
-msgid "(StrOpt) The RabbitMQ userid"
-msgstr ""
-
-#: ./doc/common/tables/neutron-rabbitmq.xml63(td)
-#: ./doc/common/tables/ceilometer-rabbitmq.xml83(td)
-msgid "(StrOpt) The RabbitMQ virtual host"
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml8(caption)
-msgid "Description of configuration options for kvs"
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml19(th)
-msgid "[kvs]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml22(td)
-msgid "backends ="
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml23(td)
-msgid ""
-"(ListOpt) Extra dogpile.cache backend modules to register with the "
-"dogpile.cache library."
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml26(td)
-msgid "config_prefix = keystone.kvs"
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml27(td)
-msgid ""
-"(StrOpt) Prefix for building the configuration dictionary for the KVS "
-"region. This should not need to be changed unless there is another "
-"dogpile.cache region with the same configuration name."
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml30(td)
-msgid "default_lock_timeout = 5"
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml31(td)
-msgid "(IntOpt) Default lock timeout for distributed locking."
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml34(td)
-msgid "enable_key_mangler = True"
-msgstr ""
-
-#: ./doc/common/tables/keystone-kvs.xml35(td)
-msgid ""
-"(BoolOpt) Toggle to disable using a key-mangling function to ensure fixed "
-"length keys. This is toggle-able for debugging purposes, it is highly "
-"recommended to always leave this set to True."
-msgstr ""
-
-#: ./doc/common/tables/keystone-policy.xml30(th)
-msgid "[policy]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-policy.xml33(td)
-msgid "driver = keystone.policy.backends.sql.Policy"
-msgstr ""
-
-#: ./doc/common/tables/keystone-policy.xml34(td)
-msgid "(StrOpt) Keystone Policy backend driver."
-msgstr ""
-
-#: ./doc/common/tables/keystone-policy.xml38(td)
-msgid ""
-"(IntOpt) Maximum number of entities that will be returned in a policy "
-"collection."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml7(literal)
-msgid "[filter:container-quotas]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-container-quotas.xml18(td)
-msgid "use = egg:swift#container_quotas"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-hash.xml7(literal)
-msgid "[swift-hash]"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-hash.xml18(td)
-msgid "swift_hash_path_suffix = changeme"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-hash.xml18(td)
-msgid ""
-"A suffix used by hash_path to offer a bit more security when generating "
-"hashes for paths. It simply appends this value to all paths; if someone "
-"knows this suffix, it's easier for them to guess the hash a path will end up"
-" with. New installations are advised to set this parameter to a random "
-"secret, which would not be disclosed ouside the organization. The same "
-"secret needs to be used by all swift servers of the same cluster. Existing "
-"installations should set this parameter to an empty string."
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-hash.xml29(td)
-msgid "swift_hash_path_prefix = changeme"
-msgstr ""
-
-#: ./doc/common/tables/swift-swift-swift-hash.xml29(td)
-msgid ""
-"A prefix used by hash_path to offer a bit more security when generating "
-"hashes for paths. It simply appends this value to all paths; if someone "
-"knows this suffix, it's easier for them to guess the hash a path will end up"
-" with. New installations are advised to set this parameter to a random "
-"secret, which would not be disclosed ouside the organization. The same "
-"secret needs to be used by all swift servers of the same cluster. Existing "
-"installations should set this parameter to an empty string."
-msgstr ""
-
-#: ./doc/common/tables/cinder-auth.xml23(td)
-msgid ""
-"(StrOpt) The strategy to use for auth. Supports noauth, keystone, and "
-"deprecated."
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml7(literal)
-msgid "[filter:formpost]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-formpost.xml18(td)
-msgid "use = egg:swift#formpost"
-msgstr ""
-
 #: ./doc/common/tables/neutron-ml2_odl.xml8(caption)
 msgid "Description of configuration options for ml2_odl"
 msgstr ""
@@ -45830,11 +45640,6 @@ msgstr ""
 msgid "[ml2_odl]"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_odl.xml23(td)
-#: ./doc/common/tables/neutron-ml2_ncs.xml23(td)
-msgid "(StrOpt) HTTP password for authentication"
-msgstr ""
-
 #: ./doc/common/tables/neutron-ml2_odl.xml26(td)
 msgid "session_timeout = 30"
 msgstr ""
@@ -45843,196 +45648,464 @@ msgstr ""
 msgid "(IntOpt) Tomcat session timeout in minutes."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_odl.xml30(td)
-#: ./doc/common/tables/neutron-ml2_ncs.xml26(td)
-msgid "timeout = 10"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_odl.xml31(td)
-#: ./doc/common/tables/neutron-ml2_ncs.xml27(td)
-msgid "(IntOpt) HTTP timeout in seconds."
-msgstr ""
-
 #: ./doc/common/tables/neutron-ml2_odl.xml35(td)
 msgid "(StrOpt) HTTP URL of OpenDaylight REST interface."
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_odl.xml38(td)
-#: ./doc/common/tables/neutron-ml2_ncs.xml34(td)
-msgid "username = None"
+#: ./doc/common/tables/swift-object-server-filter-recon.xml24(td)
+msgid "recon_lock_path = /var/lock"
 msgstr ""
 
-#: ./doc/common/tables/neutron-ml2_odl.xml39(td)
-#: ./doc/common/tables/neutron-ml2_ncs.xml35(td)
-msgid "(StrOpt) HTTP username for authentication"
+#: ./doc/common/tables/cinder-connection.xml8(caption)
+msgid "Description of configuration options for connection"
 msgstr ""
 
-#: ./doc/common/tables/heat-quota.xml22(td)
-msgid "max_events_per_stack = 1000"
+#: ./doc/common/tables/cinder-connection.xml22(td)
+msgid "connection = sqlite:///$state_path/$sqlite_db"
 msgstr ""
 
-#: ./doc/common/tables/heat-quota.xml23(td)
+#: ./doc/common/tables/heat-rpc.xml26(td)
+msgid "engine_life_check_timeout = 2"
+msgstr ""
+
+#: ./doc/common/tables/heat-rpc.xml27(td)
 msgid ""
-"(IntOpt) Maximum events that will be available per stack. Older events will "
-"be deleted when this is reached. Set to 0 for unlimited events per stack."
+"(IntOpt) RPC timeout for the engine liveness check that is used for stack "
+"locking."
 msgstr ""
 
-#: ./doc/common/tables/heat-quota.xml26(td)
-msgid "max_nested_stack_depth = 3"
+#: ./doc/common/tables/heat-rpc.xml38(td)
+msgid "rpc_backend = heat.openstack.common.rpc.impl_kombu"
 msgstr ""
 
-#: ./doc/common/tables/heat-quota.xml27(td)
-msgid "(IntOpt) Maximum depth allowed when using nested stacks."
+#: ./doc/common/tables/trove-taskmanager.xml8(caption)
+msgid "Description of configuration options for taskmanager"
 msgstr ""
 
-#: ./doc/common/tables/heat-quota.xml30(td)
-msgid "max_resources_per_stack = 1000"
+#: ./doc/common/tables/trove-taskmanager.xml22(td)
+msgid "cloudinit_location = /etc/trove/cloudinit"
 msgstr ""
 
-#: ./doc/common/tables/heat-quota.xml31(td)
-msgid "(IntOpt) Maximum resources allowed per top-level stack."
+#: ./doc/common/tables/trove-taskmanager.xml23(td)
+msgid "(StrOpt) Path to folder with cloudinit scripts."
 msgstr ""
 
-#: ./doc/common/tables/heat-quota.xml34(td)
-msgid "max_stacks_per_tenant = 100"
+#: ./doc/common/tables/trove-taskmanager.xml26(td)
+msgid "datastore_manager = None"
 msgstr ""
 
-#: ./doc/common/tables/heat-quota.xml35(td)
+#: ./doc/common/tables/trove-taskmanager.xml27(td)
 msgid ""
-"(IntOpt) Maximum number of stacks any one tenant may have active at one "
-"time."
+"(StrOpt) Manager class in guestagent, setup by taskmanager on instance "
+"provision."
 msgstr ""
 
-#: ./doc/common/tables/heat-quota.xml38(td)
-msgid "max_template_size = 524288"
+#: ./doc/common/tables/trove-taskmanager.xml30(td)
+msgid "datastore_registry_ext = {}"
 msgstr ""
 
-#: ./doc/common/tables/heat-quota.xml39(td)
-msgid "(IntOpt) Maximum raw byte size of any template."
-msgstr ""
-
-#: ./doc/common/tables/nova-spice.xml8(caption)
-msgid "Description of configuration options for spice"
-msgstr ""
-
-#: ./doc/common/tables/nova-spice.xml19(th)
-msgid "[spice]"
-msgstr ""
-
-#: ./doc/common/tables/nova-spice.xml22(td)
-msgid "agent_enabled = True"
-msgstr ""
-
-#: ./doc/common/tables/nova-spice.xml23(td)
-msgid "(BoolOpt) Enable spice guest agent support"
-msgstr ""
-
-#: ./doc/common/tables/nova-spice.xml27(td)
-msgid "(BoolOpt) Enable spice related features"
-msgstr ""
-
-#: ./doc/common/tables/nova-spice.xml30(td)
-msgid "html5proxy_base_url = http://127.0.0.1:6082/spice_auto.html"
-msgstr ""
-
-#: ./doc/common/tables/nova-spice.xml31(td)
+#: ./doc/common/tables/trove-taskmanager.xml31(td)
 msgid ""
-"(StrOpt) Location of spice HTML5 console proxy, in the form "
-"\"http://127.0.0.1:6082/spice_auto.html\""
+"(DictOpt) Extension for default datastore managers. Allows to use custom "
+"managers for each of datastore supported in trove."
 msgstr ""
 
-#: ./doc/common/tables/nova-spice.xml34(td)
-msgid "keymap = en-us"
+#: ./doc/common/tables/trove-taskmanager.xml34(td)
+msgid "exists_notification_ticks = 360"
 msgstr ""
 
-#: ./doc/common/tables/nova-spice.xml35(td)
-msgid "(StrOpt) Keymap for spice"
-msgstr ""
-
-#: ./doc/common/tables/nova-spice.xml38(td)
-msgid "server_listen = 127.0.0.1"
-msgstr ""
-
-#: ./doc/common/tables/nova-spice.xml39(td)
-msgid "(StrOpt) IP address on which instance spice server should listen"
-msgstr ""
-
-#: ./doc/common/tables/nova-spice.xml42(td)
-msgid "server_proxyclient_address = 127.0.0.1"
-msgstr ""
-
-#: ./doc/common/tables/nova-spice.xml43(td)
+#: ./doc/common/tables/trove-taskmanager.xml35(td)
 msgid ""
-"(StrOpt) The address to which proxy clients (like nova-spicehtml5proxy) "
-"should connect"
+"(IntOpt) Number of report_intervals to wait between pushing events (see "
+"report_interval)."
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml8(caption)
-msgid "Description of configuration options for zoning_fabric"
+#: ./doc/common/tables/trove-taskmanager.xml38(td)
+msgid "exists_notification_transformer = None"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml19(th)
-msgid "[BRCD_FABRIC_EXAMPLE]"
+#: ./doc/common/tables/trove-taskmanager.xml39(td)
+msgid "(StrOpt) Transformer for exists notifications."
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml22(td)
-msgid "fc_fabric_address ="
+#: ./doc/common/tables/trove-taskmanager.xml42(td)
+msgid "reboot_time_out = 120"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml23(td)
-msgid "(StrOpt) Management IP of fabric"
+#: ./doc/common/tables/trove-taskmanager.xml46(td)
+msgid "resize_time_out = 600"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml26(td)
-msgid "fc_fabric_password ="
+#: ./doc/common/tables/trove-taskmanager.xml50(td)
+msgid "revert_time_out = 600"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml27(td)
-msgid "(StrOpt) Password for user"
+#: ./doc/common/tables/trove-taskmanager.xml54(td)
+msgid "server_delete_time_out = 60"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml30(td)
-msgid "fc_fabric_port = 22"
+#: ./doc/common/tables/trove-taskmanager.xml58(td)
+msgid "state_change_wait_time = 180"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml31(td)
-msgid "(IntOpt) Connecting port"
+#: ./doc/common/tables/trove-taskmanager.xml62(td)
+msgid "update_status_on_fail = False"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml34(td)
-msgid "fc_fabric_user ="
+#: ./doc/common/tables/trove-taskmanager.xml63(td)
+msgid ""
+"(BoolOpt) If instance fails to become active, taskmanager updates statuses, "
+"service status = FAILED_TIMEOUT_GUESTAGENT, instance task status = "
+"BUILDING_ERROR_TIMEOUT_GA."
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml35(td)
-msgid "(StrOpt) Fabric user ID"
+#: ./doc/common/tables/trove-taskmanager.xml70(td)
+msgid "use_heat = False"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml38(td)
-msgid "principal_switch_wwn = None"
+#: ./doc/common/tables/trove-taskmanager.xml74(td)
+msgid "use_nova_server_volume = False"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml39(td)
-msgid "(StrOpt) Principal switch WWN of the fabric"
+#: ./doc/common/tables/trove-taskmanager.xml78(td)
+msgid "verify_swift_checksum_on_restore = True"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml42(td)
-msgid "zone_activate = True"
+#: ./doc/common/tables/trove-taskmanager.xml79(td)
+msgid ""
+"(BoolOpt) Enable verification of swift checksum before starting restore; "
+"makes sure the checksum of original backup matches checksum of the swift "
+"backup file."
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml43(td)
-msgid "(BoolOpt) overridden zoning activation state"
+#: ./doc/common/tables/heat-cloudwatch_api.xml8(caption)
+msgid "Description of configuration options for cloudwatch_api"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml46(td)
-msgid "zone_name_prefix = None"
+#: ./doc/common/tables/heat-cloudwatch_api.xml26(th)
+msgid "[heat_api_cloudwatch]"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml47(td)
-msgid "(StrOpt) overridden zone name prefix"
+#: ./doc/common/tables/heat-cloudwatch_api.xml37(td)
+msgid "bind_port = 8003"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zoning_fabric.xml51(td)
-msgid "(StrOpt) overridden zoning policy"
+#: ./doc/common/tables/heat-cloudwatch_api.xml50(td)
+msgid ""
+"(IntOpt) Maximum line size of message headers to be accepted. "
+"max_header_line may need to be increased when using large tokens (typically "
+"those generated by the Keystone v3 API with big service catalogs.)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml8(caption)
+msgid "Description of configuration options for images"
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml23(td)
+msgid ""
+"(ListOpt) A list of url schemes that can be downloaded directly via the "
+"direct_url. Currently supported schemes: [file]."
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml31(td)
+msgid ""
+"(ListOpt) A list of the glance api servers available to cinder "
+"([hostname|ip]:port)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml34(td)
+msgid "glance_api_ssl_compression = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml35(td)
+msgid ""
+"(BoolOpt) Whether to attempt to negotiate SSL layer compression when using "
+"SSL (https) requests. Set to False to disable SSL layer compression. In some"
+" cases disabling this may improve data throughput, eg when high network "
+"bandwidth is available and you are using already compressed image formats "
+"such as qcow2 ."
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml38(td)
+msgid "glance_api_version = 1"
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml39(td)
+msgid "(IntOpt) Version of the glance api to use"
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml43(td)
+msgid "(StrOpt) default glance hostname or ip"
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml47(td)
+msgid "(IntOpt) Number retries when downloading an image from glance"
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml51(td)
+msgid "(IntOpt) default glance port"
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml54(td)
+msgid "glance_request_timeout = None"
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml55(td)
+msgid ""
+"(IntOpt) http/https timeout value for glance operations. If no value (None) "
+"is supplied here, the glanceclient default value is used."
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml58(td)
+msgid "image_conversion_dir = $state_path/conversion"
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml59(td)
+msgid "(StrOpt) Directory used for temporary storage during image conversion"
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml70(td)
+msgid "use_multipath_for_image_xfer = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-images.xml71(td)
+msgid ""
+"(BoolOpt) Do we attach/detach volumes in cinder using multipath for volume "
+"to image and image to volume transfers?"
+msgstr ""
+
+#: ./doc/common/tables/cinder-huawei.xml8(caption)
+msgid "Description of configuration options for huawei"
+msgstr ""
+
+#: ./doc/common/tables/cinder-huawei.xml22(td)
+msgid "cinder_huawei_conf_file = /etc/cinder/cinder_huawei_conf.xml"
+msgstr ""
+
+#: ./doc/common/tables/cinder-huawei.xml23(td)
+msgid "(StrOpt) config data for cinder huawei plugin"
+msgstr ""
+
+#: ./doc/common/tables/nova-console.xml8(caption)
+msgid "Description of configuration options for console"
+msgstr ""
+
+#: ./doc/common/tables/nova-console.xml22(td)
+msgid "console_public_hostname = oslo"
+msgstr ""
+
+#: ./doc/common/tables/nova-console.xml23(td)
+msgid "(StrOpt) Publicly visible name for this console host"
+msgstr ""
+
+#: ./doc/common/tables/nova-console.xml26(td)
+msgid "console_token_ttl = 600"
+msgstr ""
+
+#: ./doc/common/tables/nova-console.xml27(td)
+msgid "(IntOpt) How many seconds before deleting tokens"
+msgstr ""
+
+#: ./doc/common/tables/nova-console.xml30(td)
+msgid "consoleauth_manager = nova.consoleauth.manager.ConsoleAuthManager"
+msgstr ""
+
+#: ./doc/common/tables/nova-console.xml31(td)
+msgid "(StrOpt) Manager for console auth"
+msgstr ""
+
+#: ./doc/common/tables/neutron-fwaas.xml8(caption)
+msgid "Description of configuration options for fwaas"
+msgstr ""
+
+#: ./doc/common/tables/neutron-fwaas.xml19(th)
+#: ./doc/common/tables/neutron-nec.xml73(th)
+msgid "[fwaas]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-fwaas.xml23(td)
+msgid "(BoolOpt) Enable FWaaS"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_nfs.xml8(caption)
+msgid "Description of configuration options for nexenta_nfs"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_nfs.xml22(td)
+msgid "nexenta_mount_point_base = $state_path/mnt"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_nfs.xml23(td)
+msgid "(StrOpt) Base dir containing mount points for nfs shares"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_nfs.xml26(td)
+msgid "nexenta_nms_cache_volroot = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_nfs.xml27(td)
+msgid ""
+"(BoolOpt) If set True cache NexentaStor appliance volroot option value."
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_nfs.xml30(td)
+msgid "nexenta_shares_config = /etc/cinder/nfs_shares"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_nfs.xml34(td)
+msgid "nexenta_volume_compression = on"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_nfs.xml35(td)
+msgid "(StrOpt) Default compression value for new ZFS folders."
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml22(td)
+msgid "bandwidth_poll_interval = 600"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml23(td)
+msgid ""
+"(IntOpt) Interval to pull network bandwidth usage info. Not supported on all"
+" hypervisors. Set to 0 to disable."
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml26(td)
+msgid "enable_network_quota = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml27(td)
+msgid "(BoolOpt) Enables or disables quota checking for tenant networks"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml30(td)
+msgid "quota_cores = 20"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml31(td)
+msgid "(IntOpt) Number of instance cores allowed per project"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml34(td)
+msgid "quota_driver = nova.quota.DbQuotaDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml38(td)
+msgid "quota_fixed_ips = -1"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml39(td)
+msgid ""
+"(IntOpt) Number of fixed IPs allowed per project (this should be at least "
+"the number of instances allowed)"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml42(td)
+msgid "quota_floating_ips = 10"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml43(td)
+msgid "(IntOpt) Number of floating IPs allowed per project"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml46(td)
+msgid "quota_injected_file_content_bytes = 10240"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml47(td)
+msgid "(IntOpt) Number of bytes allowed per injected file"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml50(td)
+msgid "quota_injected_file_path_bytes = 255"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml51(td)
+msgid "(IntOpt) Number of bytes allowed per injected file path"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml54(td)
+msgid "quota_injected_files = 5"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml55(td)
+msgid "(IntOpt) Number of injected files allowed"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml58(td)
+msgid "quota_instances = 10"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml59(td)
+msgid "(IntOpt) Number of instances allowed per project"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml62(td)
+msgid "quota_key_pairs = 100"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml63(td)
+msgid "(IntOpt) Number of key pairs per user"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml66(td)
+msgid "quota_metadata_items = 128"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml67(td)
+msgid "(IntOpt) Number of metadata items allowed per instance"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml70(td)
+msgid "quota_ram = 51200"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml71(td)
+msgid "(IntOpt) Megabytes of instance RAM allowed per project"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml74(td)
+msgid "quota_security_group_rules = 20"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml75(td)
+msgid "(IntOpt) Number of security rules per security group"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml78(td)
+msgid "quota_security_groups = 10"
+msgstr ""
+
+#: ./doc/common/tables/nova-quota.xml79(td)
+msgid "(IntOpt) Number of security groups per project"
+msgstr ""
+
+#: ./doc/common/tables/keystone-stats.xml8(caption)
+msgid "Description of configuration options for stats"
+msgstr ""
+
+#: ./doc/common/tables/keystone-stats.xml19(th)
+msgid "[stats]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-stats.xml22(td)
+msgid "driver = keystone.contrib.stats.backends.kvs.Stats"
+msgstr ""
+
+#: ./doc/common/tables/keystone-stats.xml23(td)
+msgid "(StrOpt) Keystone stats backend driver."
+msgstr ""
+
+#: ./doc/common/tables/heat-crypt.xml8(caption)
+msgid "Description of configuration options for crypt"
+msgstr ""
+
+#: ./doc/common/tables/heat-crypt.xml22(td)
+msgid "auth_encryption_key = notgood but just long enough i think"
+msgstr ""
+
+#: ./doc/common/tables/heat-crypt.xml23(td)
+msgid "(StrOpt) Encryption key used for authentication info in database."
 msgstr ""
 
 #: ./doc/common/tables/neutron-midonet.xml8(caption)
@@ -46095,1469 +46168,207 @@ msgstr ""
 msgid "(StrOpt) MidoNet admin username."
 msgstr ""
 
-#: ./doc/common/tables/neutron-nvsd.xml8(caption)
-msgid "Description of configuration options for nvsd"
+#: ./doc/common/tables/cinder-coraid.xml8(caption)
+msgid "Description of configuration options for coraid"
 msgstr ""
 
-#: ./doc/common/tables/neutron-nvsd.xml23(td)
-msgid "(StrOpt) integration bridge"
+#: ./doc/common/tables/cinder-coraid.xml22(td)
+msgid "coraid_esm_address ="
 msgstr ""
 
-#: ./doc/common/tables/neutron-nvsd.xml26(th)
-msgid "[nvsd]"
+#: ./doc/common/tables/cinder-coraid.xml23(td)
+msgid "(StrOpt) IP address of Coraid ESM"
 msgstr ""
 
-#: ./doc/common/tables/neutron-nvsd.xml29(td)
-msgid "nvsd_ip = 127.0.0.1"
+#: ./doc/common/tables/cinder-coraid.xml26(td)
+msgid "coraid_group = admin"
 msgstr ""
 
-#: ./doc/common/tables/neutron-nvsd.xml30(td)
-msgid "(StrOpt) NVSD Controller IP address"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nvsd.xml33(td)
-msgid "nvsd_passwd = oc123"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nvsd.xml34(td)
-msgid "(StrOpt) NVSD Controller password"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nvsd.xml37(td)
-msgid "nvsd_port = 8082"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nvsd.xml38(td)
-msgid "(IntOpt) NVSD Controller Port number"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nvsd.xml41(td)
-msgid "nvsd_retries = 0"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nvsd.xml42(td)
-msgid "(IntOpt) Number of login retries to NVSD controller"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nvsd.xml45(td)
-msgid "nvsd_user = ocplugin"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nvsd.xml46(td)
-msgid "(StrOpt) NVSD Controller username"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nvsd.xml49(td)
-msgid "request_timeout = 30"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nvsd.xml50(td)
-msgid "(IntOpt) NVSD controller REST API request timeout in seconds"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml8(caption)
-msgid "Description of configuration options for embrane_lb"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml19(th)
-msgid "[heleoslb]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml26(td)
-msgid "admin_username = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml27(td)
-#: ./doc/common/tables/neutron-embrane.xml23(td)
-msgid "(StrOpt) ESM admin username."
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml30(td)
-msgid "async_requests = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml31(td)
-#: ./doc/common/tables/neutron-embrane.xml27(td)
-msgid "(BoolOpt) Define if the requests have run asynchronously or not"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml34(td)
-#: ./doc/common/tables/neutron-embrane.xml30(td)
-msgid "dummy_utif_id = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml35(td)
-msgid "(StrOpt) Dummy user traffic Security Zone id for LBs"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml38(td)
-#: ./doc/common/tables/neutron-embrane.xml34(td)
-msgid "esm_mgmt = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml39(td)
-#: ./doc/common/tables/neutron-embrane.xml35(td)
-msgid "(StrOpt) ESM management root address"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml42(td)
-#: ./doc/common/tables/neutron-embrane.xml38(td)
-msgid "inband_id = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml43(td)
-msgid "(StrOpt) In band Security Zone id for LBs"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml46(td)
-msgid "lb_flavor = small"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml47(td)
-msgid "(StrOpt) choose LB image flavor to use, accepted values: small, medium"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml50(td)
-msgid "lb_image = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml51(td)
-msgid "(StrOpt) Load Balancer image id (Embrane LB)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml54(td)
-#: ./doc/common/tables/neutron-embrane.xml42(td)
-msgid "mgmt_id = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml55(td)
-msgid "(StrOpt) Management Security Zone id for LBs"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml58(td)
-#: ./doc/common/tables/neutron-embrane.xml46(td)
-msgid "oob_id = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml59(td)
-msgid "(StrOpt) Out of band Security Zone id for LBs"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml62(td)
-#: ./doc/common/tables/neutron-vmware.xml199(td)
-msgid "resource_pool_id = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml63(td)
-#: ./doc/common/tables/neutron-embrane.xml51(td)
-msgid "(StrOpt) Shared resource pool id"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml66(td)
-msgid "sync_interval = 60"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane_lb.xml67(td)
-msgid "(IntOpt) resource synchronization interval in seconds"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml8(caption)
-msgid "Description of configuration options for storwize"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml22(td)
-msgid "storwize_svc_connection_protocol = iSCSI"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml23(td)
-msgid "(StrOpt) Connection protocol (iSCSI/FC)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml26(td)
-msgid "storwize_svc_flashcopy_timeout = 120"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml27(td)
-msgid ""
-"(IntOpt) Maximum number of seconds to wait for FlashCopy to be prepared. "
-"Maximum value is 600 seconds (10 minutes)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml30(td)
-msgid "storwize_svc_iscsi_chap_enabled = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml31(td)
-msgid ""
-"(BoolOpt) Configure CHAP authentication for iSCSI connections (Default: "
-"Enabled)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml34(td)
-msgid "storwize_svc_multihostmap_enabled = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml35(td)
-msgid "(BoolOpt) Allows vdisk to multi host mapping"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml38(td)
-msgid "storwize_svc_multipath_enabled = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml39(td)
-msgid ""
-"(BoolOpt) Connect with multipath (FC only; iSCSI multipath is controlled by "
-"Nova)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml42(td)
-msgid "storwize_svc_vol_autoexpand = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml43(td)
-msgid "(BoolOpt) Storage system autoexpand parameter for volumes (True/False)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml46(td)
-msgid "storwize_svc_vol_compression = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml47(td)
-msgid "(BoolOpt) Storage system compression option for volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml50(td)
-msgid "storwize_svc_vol_easytier = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml51(td)
-msgid "(BoolOpt) Enable Easy Tier for volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml54(td)
-msgid "storwize_svc_vol_grainsize = 256"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml55(td)
-msgid ""
-"(IntOpt) Storage system grain size parameter for volumes (32/64/128/256)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml58(td)
-msgid "storwize_svc_vol_iogrp = 0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml59(td)
-msgid "(IntOpt) The I/O group in which to allocate volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml62(td)
-msgid "storwize_svc_vol_rsize = 2"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml63(td)
-msgid ""
-"(IntOpt) Storage system space-efficiency parameter for volumes (percentage)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml66(td)
-msgid "storwize_svc_vol_warning = 0"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml67(td)
-msgid ""
-"(IntOpt) Storage system threshold for volume capacity warnings (percentage)"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml70(td)
-msgid "storwize_svc_volpool_name = volpool"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storwize.xml71(td)
-msgid "(StrOpt) Storage system storage pool for volumes"
-msgstr ""
-
-#: ./doc/common/tables/nova-rootwrap.xml22(td)
-msgid "filters_path = /etc/nova/rootwrap.d,/usr/share/nova/rootwrap"
-msgstr ""
-
-#: ./doc/common/tables/nova-rootwrap.xml35(td)
-msgid ""
-"Which syslog facility to use. Valid values include auth, authpriv, syslog, "
-"user0, user1... Default value is 'syslog'"
-msgstr ""
-
-#: ./doc/common/tables/cinder-solidfire.xml8(caption)
-msgid "Description of configuration options for solidfire"
-msgstr ""
-
-#: ./doc/common/tables/cinder-solidfire.xml22(td)
-msgid "sf_account_prefix = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-solidfire.xml23(td)
-msgid ""
-"(StrOpt) Create SolidFire accounts with this prefix. Any string can be used "
-"here, but the string \"hostname\" is special and will create a prefix using "
-"the cinder node hostsname (previous default behavior). The default is NO "
-"prefix."
-msgstr ""
-
-#: ./doc/common/tables/cinder-solidfire.xml26(td)
-msgid "sf_allow_tenant_qos = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-solidfire.xml27(td)
-msgid "(BoolOpt) Allow tenants to specify QOS on create"
-msgstr ""
-
-#: ./doc/common/tables/cinder-solidfire.xml30(td)
-msgid "sf_api_port = 443"
-msgstr ""
-
-#: ./doc/common/tables/cinder-solidfire.xml31(td)
-msgid ""
-"(IntOpt) SolidFire API port. Useful if the device api is behind a proxy on a"
-" different port."
-msgstr ""
-
-#: ./doc/common/tables/cinder-solidfire.xml34(td)
-msgid "sf_emulate_512 = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-solidfire.xml35(td)
-msgid "(BoolOpt) Set 512 byte emulation on volume creation;"
-msgstr ""
-
-#: ./doc/common/tables/keystone-revoke.xml8(caption)
-msgid "Description of configuration options for revoke"
-msgstr ""
-
-#: ./doc/common/tables/keystone-revoke.xml19(th)
-msgid "[revoke]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-revoke.xml23(td)
-msgid ""
-"(BoolOpt) Toggle for revocation event cacheing. This has no effect unless "
-"global caching is enabled."
-msgstr ""
-
-#: ./doc/common/tables/keystone-revoke.xml26(td)
-msgid "driver = keystone.contrib.revoke.backends.kvs.Revoke"
-msgstr ""
-
-#: ./doc/common/tables/keystone-revoke.xml27(td)
-msgid ""
-"(StrOpt) An implementation of the backend for persisting revocation events."
-msgstr ""
-
-#: ./doc/common/tables/keystone-revoke.xml30(td)
-msgid "expiration_buffer = 1800"
-msgstr ""
-
-#: ./doc/common/tables/keystone-revoke.xml31(td)
-msgid ""
-"(IntOpt) This value (calculated in seconds) is added to token expiration "
-"before a revocation event may be removed from the backend."
-msgstr ""
-
-#: ./doc/common/tables/glance-ssl.xml27(td)
-msgid "(StrOpt) Certificate file to use when starting API server securely."
-msgstr ""
-
-#: ./doc/common/tables/glance-ssl.xml31(td)
-msgid "(StrOpt) Private key file to use when starting API server securely."
-msgstr ""
-
-#: ./doc/common/tables/heat-metadata_api.xml8(caption)
-msgid "Description of configuration options for metadata_api"
-msgstr ""
-
-#: ./doc/common/tables/nova-apiv3.xml8(caption)
-msgid "Description of configuration options for apiv3"
-msgstr ""
-
-#: ./doc/common/tables/nova-apiv3.xml19(th)
-msgid "[osapi_v3]"
-msgstr ""
-
-#: ./doc/common/tables/nova-apiv3.xml23(td)
-msgid "(BoolOpt) Whether the V3 API is enabled or not"
-msgstr ""
-
-#: ./doc/common/tables/nova-apiv3.xml26(td)
-msgid "extensions_blacklist ="
-msgstr ""
-
-#: ./doc/common/tables/nova-apiv3.xml27(td)
-msgid ""
-"(ListOpt) A list of v3 API extensions to never load. Specify the extension "
-"aliases here."
-msgstr ""
-
-#: ./doc/common/tables/nova-apiv3.xml30(td)
-msgid "extensions_whitelist ="
-msgstr ""
-
-#: ./doc/common/tables/nova-apiv3.xml31(td)
-msgid ""
-"(ListOpt) If the list is not empty then a v3 API extension will only be "
-"loaded if it exists in this list. Specify the extension aliases here."
-msgstr ""
-
-#: ./doc/common/tables/glance-db.xml86(td)
-msgid "sqlite_db = glance.sqlite"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml22(td)
-msgid "default_interface_name = breth0"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml23(td)
-msgid ""
-"(StrOpt) Name of the interface on a L2 Gateway transport nodewhich should be"
-" used by default when setting up a network connection"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml26(td)
-msgid "default_l2_gw_service_uuid = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml27(td)
-msgid ""
-"(StrOpt) Unique identifier of the NSX L2 Gateway service which will be used "
-"by default for network gateways"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml30(td)
-msgid "default_l3_gw_service_uuid = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml31(td)
-msgid ""
-"(StrOpt) Unique identifier of the NSX L3 Gateway service which will be used "
-"for implementing routers and floating IPs"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml34(td)
-msgid "default_service_cluster_uuid = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml35(td)
-msgid ""
-"(StrOpt) Unique identifier of the Service Cluster which will be used by "
-"logical services like dhcp and metadata"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml38(td)
-msgid "default_tz_uuid = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml39(td)
-msgid ""
-"(StrOpt) This is uuid of the default NSX Transport zone that will be used "
-"for creating tunneled isolated \"Neutron\" networks. It needs to be created "
-"in NSX before starting Neutron with the nsx plugin."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml42(td)
-msgid "http_timeout = 10"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml43(td)
-msgid "(IntOpt) Time before aborting a request"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml46(td)
-msgid "nsx_controllers = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml47(td)
-msgid "(ListOpt) Lists the NSX controllers in this cluster"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml50(td)
-msgid "nsx_password = admin"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml51(td)
-msgid "(StrOpt) Password for NSX controllers in this cluster"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml54(td)
-msgid "nsx_user = admin"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml55(td)
-msgid "(StrOpt) User name for NSX controllers in this cluster"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml58(td)
-msgid "redirects = 2"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml59(td)
-msgid "(IntOpt) Number of times a redirect should be followed"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml62(td)
-msgid "req_timeout = 30"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml63(td)
-msgid "(IntOpt) Total time limit for a cluster request"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml66(td)
-msgid "retries = 2"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml67(td)
-msgid "(IntOpt) Number of time a request should be retried"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml73(td)
-msgid "retries = 3"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml74(td)
-msgid ""
-"(IntOpt) The number of retries the agent will send request to daemon before "
-"giving up"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml77(th)
-msgid "[NSX]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml80(td)
-msgid "agent_mode = agent"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml81(td)
-msgid "(StrOpt) The mode used to implement DHCP/metadata services."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml84(td)
-msgid "concurrent_connections = 10"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml85(td)
-msgid "(IntOpt) Maximum concurrent connections to each NSX controller."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml88(td)
-msgid "default_transport_type = stt"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml89(td)
-msgid ""
-"(StrOpt) The default network tranport type to use (stt, gre, bridge, "
-"ipsec_gre, or ipsec_stt)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml92(td)
-msgid "max_lp_per_bridged_ls = 5000"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml93(td)
-msgid ""
-"(IntOpt) Maximum number of ports of a logical switch on a bridged transport "
-"zone (default 5000)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml96(td)
-msgid "max_lp_per_overlay_ls = 256"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml97(td)
-msgid ""
-"(IntOpt) Maximum number of ports of a logical switch on an overlay transport"
-" zone (default 256)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml100(td)
-msgid "metadata_mode = access_network"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml101(td)
-msgid ""
-"(StrOpt) If set to access_network this enables a dedicated connection to the"
-" metadata proxy for metadata server access via Neutron router. If set to "
-"dhcp_host_route this enables host route injection via the dhcp agent. This "
-"option is only useful if running on a host that does not support namespaces "
-"otherwise access_network should be used."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml104(td)
-msgid "nsx_gen_timeout = -1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml105(td)
-msgid ""
-"(IntOpt) Number of seconds a generation id should be valid for (default -1 "
-"meaning do not time out)"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml108(td)
-msgid "replication_mode = service"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml109(td)
-msgid ""
-"(StrOpt) The default option leverages service nodes to perform packet "
-"replication though one could set to this to 'source' to perform replication "
-"locally. This is useful if one does not want to deploy a service node(s)."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml112(th)
-msgid "[NSX_DHCP]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml115(td)
-msgid "default_lease_time = 43200"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml116(td)
-msgid "(IntOpt) Default DHCP lease time"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml119(td)
-msgid "domain_name = openstacklocal"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml123(td)
-msgid "extra_domain_name_servers ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml124(td)
-msgid "(ListOpt) Comma separated list of additional domain name servers"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml127(th)
-msgid "[NSX_LSN]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml130(td)
-msgid "sync_on_missing_data = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml131(td)
-msgid ""
-"(BoolOpt) Pull LSN information from NSX in case it is missing from the local"
-" data store. This is useful to rebuild the local store in case of server "
-"recovery."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml134(th)
-msgid "[NSX_METADATA]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml137(td)
-msgid "metadata_server_address = 127.0.0.1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml138(td)
-msgid "(StrOpt) IP address used by Metadata server."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml141(td)
-msgid "metadata_server_port = 8775"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml142(td)
-msgid "(IntOpt) TCP Port used by Metadata server."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml145(td)
-msgid "metadata_shared_secret ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml149(th)
-msgid "[NSX_SYNC]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml152(td)
-msgid "always_read_status = False"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml153(td)
-msgid ""
-"(BoolOpt) Always read operational status from backend on show operations. "
-"Enabling this option might slow down the system."
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml156(td)
-msgid "max_random_sync_delay = 0"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml157(td)
-msgid ""
-"(IntOpt) Maximum value for the additional random delay in seconds between "
-"runs of the state synchronization task"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml160(td)
-msgid "min_chunk_size = 500"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml161(td)
-msgid ""
-"(IntOpt) Minimum number of resources to be retrieved from NSX during state "
-"synchronization"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml164(td)
-msgid "min_sync_req_delay = 1"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml165(td)
-msgid ""
-"(IntOpt) Minimum delay, in seconds, between two state synchronization "
-"queries to NSX. It must not exceed state_sync_interval"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml168(td)
-msgid "state_sync_interval = 10"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml169(td)
-msgid ""
-"(IntOpt) Interval in seconds between runs of the state synchronization task."
-" Set it to 0 to disable it"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml172(th)
-msgid "[vcns]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml175(td)
-msgid "datacenter_moid = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml176(td)
-msgid ""
-"(StrOpt) Optional parameter identifying the ID of datacenter to deploy NSX "
-"Edges"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml179(td)
-msgid "datastore_id = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml180(td)
-#: ./doc/common/tables/neutron-vmware.xml184(td)
-msgid ""
-"(StrOpt) Optional parameter identifying the ID of datastore to deploy NSX "
-"Edges"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml183(td)
-msgid "deployment_container_id = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml187(td)
-msgid "external_network = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml188(td)
-msgid "(StrOpt) Network ID for physical network connectivity"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml191(td)
-msgid "manager_uri = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml192(td)
-msgid "(StrOpt) uri for vsm"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml195(td)
-msgid "password = default"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml196(td)
-msgid "(StrOpt) Password for vsm"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml200(td)
-msgid ""
-"(StrOpt) Optional parameter identifying the ID of resource to deploy NSX "
-"Edges"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml203(td)
-msgid "task_status_check_interval = 2000"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml204(td)
-msgid "(IntOpt) Task status check interval"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml207(td)
-msgid "user = admin"
-msgstr ""
-
-#: ./doc/common/tables/neutron-vmware.xml208(td)
-msgid "(StrOpt) User name for vsm"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml7(literal)
-msgid "[realm2]"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml18(td)
-msgid "key = realm2key"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml21(td)
-msgid "key2 = realm2key2"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml24(td)
-msgid "cluster_name3 = https://host3/v1/"
-msgstr ""
-
-#: ./doc/common/tables/swift-container-sync-realms-realm2.xml27(td)
-msgid "cluster_name4 = https://host4/v1/"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml22(td)
-msgid "api_rate_limit = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml23(td)
-msgid ""
-"(BoolOpt) Whether to use per-user rate limiting for the api. This option is "
-"only used by v2 api. Rate limiting is removed from v3 api."
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml30(td)
-msgid "enabled_apis = ec2, osapi_compute, metadata"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml31(td)
-msgid "(ListOpt) A list of APIs to enable by default"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml34(td)
-msgid "enabled_ssl_apis ="
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml35(td)
-msgid "(ListOpt) A list of APIs with enabled SSL"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml38(td)
-msgid "instance_name_template = instance-%08x"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml39(td)
-msgid "(StrOpt) Template string to be used to generate instance names"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml46(td)
-msgid "multi_instance_display_name_template = %(name)s-%(uuid)s"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml47(td)
-msgid ""
-"(StrOpt) When creating multiple instances with a single request using the "
-"os-multiple-create API extension, this template will be used to build the "
-"display name for each instance. The benefit is that the instances end up "
-"with different hostnames. To restore legacy behavior of every instance "
-"having the same name, set this option to \"%(name)s\". Valid keys for the "
-"template are: name, uuid, count."
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml50(td)
-msgid "non_inheritable_image_properties = cache_in_nova, bittorrent"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml51(td)
-msgid ""
-"(ListOpt) These are image properties which a snapshot should not inherit "
-"from an instance"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml54(td)
-msgid "null_kernel = nokernel"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml55(td)
-msgid ""
-"(StrOpt) Kernel image that indicates not to use a kernel, but to use a raw "
-"disk image instead"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml58(td)
-msgid "osapi_compute_ext_list ="
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml59(td)
-msgid ""
-"(ListOpt) Specify list of extensions to load when using "
-"osapi_compute_extension option with "
-"nova.api.openstack.compute.contrib.select_extensions"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml62(td)
-msgid ""
-"osapi_compute_extension = "
-"['nova.api.openstack.compute.contrib.standard_extensions']"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml63(td)
-msgid "(MultiStrOpt) osapi compute extension to load"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml66(td)
-msgid "osapi_compute_link_prefix = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml67(td)
-msgid ""
-"(StrOpt) Base URL that will be presented to users in links to the OpenStack "
-"Compute API"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml70(td)
-msgid "osapi_compute_listen = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml71(td)
-msgid "(StrOpt) The IP address on which the OpenStack API will listen."
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml74(td)
-msgid "osapi_compute_listen_port = 8774"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml75(td)
-msgid "(IntOpt) The port on which the OpenStack API will listen."
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml78(td)
-msgid "osapi_compute_workers = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml79(td)
-msgid ""
-"(IntOpt) Number of workers for OpenStack API service. The default will be "
-"the number of CPUs available."
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml82(td)
-msgid "osapi_hide_server_address_states = building"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml83(td)
-msgid "(ListOpt) List of instance states that should hide network info"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml86(td)
-msgid "servicegroup_driver = db"
-msgstr ""
-
-#: ./doc/common/tables/nova-api.xml87(td)
-msgid ""
-"(StrOpt) The driver for servicegroup service (valid options are: db, zk, mc)"
-msgstr ""
-
-#: ./doc/common/tables/glance-matchmaker.xml8(caption)
-msgid "Description of configuration options for matchmaker"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml19(th)
-msgid "[signing]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml22(td)
-#: ./doc/common/tables/keystone-ssl.xml57(td)
-msgid "ca_certs = /etc/keystone/ssl/certs/ca.pem"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml23(td)
-msgid "(StrOpt) Path of the CA for token signing."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml26(td)
-#: ./doc/common/tables/keystone-ssl.xml61(td)
-msgid "ca_key = /etc/keystone/ssl/private/cakey.pem"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml27(td)
-msgid "(StrOpt) Path of the CA Key for token signing."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml30(td)
-msgid "cert_subject = /C=US/ST=Unset/L=Unset/O=Unset/CN=www.example.com"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml31(td)
-msgid ""
-"(StrOpt) Certificate Subject (auto generated certificate) for token signing."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml34(td)
-msgid "certfile = /etc/keystone/ssl/certs/signing_cert.pem"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml35(td)
-msgid "(StrOpt) Path of the certfile for token signing."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml38(td)
-msgid "key_size = 2048"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml39(td)
-msgid ""
-"(IntOpt) Key Size (in bits) for token signing cert (auto generated "
-"certificate)."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml42(td)
-msgid "keyfile = /etc/keystone/ssl/private/signing_key.pem"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml43(td)
-msgid "(StrOpt) Path of the keyfile for token signing."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml46(td)
-msgid "token_format = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml47(td)
-msgid "(StrOpt) Deprecated in favor of provider in the [token] section."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml50(td)
-#: ./doc/common/tables/keystone-ssl.xml89(td)
-msgid "valid_days = 3650"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml51(td)
-msgid ""
-"(IntOpt) Day the token signing cert is valid for (auto generated "
-"certificate)."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml58(td)
-msgid "(StrOpt) Path of the ca cert file for SSL."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml62(td)
-msgid "(StrOpt) Path of the CA key file for SSL."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml65(td)
-msgid "cert_required = False"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml66(td)
-msgid "(BoolOpt) Require client certificate."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml69(td)
-msgid "cert_subject = /C=US/ST=Unset/L=Unset/O=Unset/CN=localhost"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml70(td)
-msgid "(StrOpt) SSL Certificate Subject (auto generated certificate)."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml73(td)
-msgid "certfile = /etc/keystone/ssl/certs/keystone.pem"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml74(td)
-msgid "(StrOpt) Path of the certfile for SSL."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml78(td)
-msgid "(BoolOpt) Toggle for SSL support on the keystone eventlet servers."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml81(td)
-msgid "key_size = 1024"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml82(td)
-msgid "(IntOpt) SSL Key Length (in bits) (auto generated certificate)."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml85(td)
-msgid "keyfile = /etc/keystone/ssl/private/keystonekey.pem"
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml86(td)
-msgid "(StrOpt) Path of the keyfile for SSL."
-msgstr ""
-
-#: ./doc/common/tables/keystone-ssl.xml90(td)
-msgid ""
-"(IntOpt) Days the certificate is valid for once signed (auto generated "
-"certificate)."
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-container.xml7(literal)
-msgid "[container]"
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-container.xml18(td)
-msgid "max connections = 4"
-msgstr ""
-
-#: ./doc/common/tables/swift-rsyncd-container.xml27(td)
-msgid "lock file = /var/lock/container.lock"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san-solaris.xml8(caption)
-msgid "Description of configuration options for san-solaris"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san-solaris.xml22(td)
-msgid "san_zfs_volume_base = rpool/"
-msgstr ""
-
-#: ./doc/common/tables/cinder-san-solaris.xml23(td)
-msgid "(StrOpt) The ZFS path under which to create zvols for volumes."
-msgstr ""
-
-#: ./doc/common/tables/trove-heat.xml8(caption)
-msgid "Description of configuration options for heat"
-msgstr ""
-
-#: ./doc/common/tables/trove-heat.xml22(td)
-msgid "heat_time_out = 60"
-msgstr ""
-
-#: ./doc/common/tables/trove-heat.xml26(td)
-msgid "heat_url = http://localhost:8004/v1"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml8(caption)
-msgid "Description of configuration options for netapp_cdot_nfs"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml26(td)
-msgid "netapp_copyoffload_tool_path = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-netapp_cdot_nfs.xml27(td)
+#: ./doc/common/tables/cinder-coraid.xml27(td)
 msgid ""
-"(StrOpt) This option specifies the path of the NetApp copy offload tool "
-"binary. Ensure that the binary has execute permissions set which allow the "
-"effective user of the cinder-volume process to execute the file."
+"(StrOpt) Name of group on Coraid ESM to which coraid_user belongs (must have"
+" admin privilege)"
 msgstr ""
 
-#: ./doc/common/tables/glance-paste.xml8(caption)
-msgid "Description of configuration options for paste"
+#: ./doc/common/tables/cinder-coraid.xml30(td)
+msgid "coraid_password = password"
 msgstr ""
 
-#: ./doc/common/tables/glance-paste.xml22(td)
-msgid "config_file = None"
+#: ./doc/common/tables/cinder-coraid.xml31(td)
+msgid "(StrOpt) Password to connect to Coraid ESM"
 msgstr ""
 
-#: ./doc/common/tables/glance-paste.xml23(td)
-msgid "(StrOpt) Name of the paste configuration file."
+#: ./doc/common/tables/cinder-coraid.xml34(td)
+msgid "coraid_repository_key = coraid_repository"
 msgstr ""
 
-#: ./doc/common/tables/glance-paste.xml27(td)
-msgid ""
-"(StrOpt) Partial name of a pipeline in your paste configuration file with "
-"the service name removed. For example, if your paste section name is "
-"[pipeline:glance-api-keystone] use the value \"keystone\""
-msgstr ""
-
-#: ./doc/common/tables/nova-rdp.xml8(caption)
-msgid "Description of configuration options for rdp"
-msgstr ""
-
-#: ./doc/common/tables/nova-rdp.xml19(th)
-msgid "[rdp]"
-msgstr ""
-
-#: ./doc/common/tables/nova-rdp.xml23(td)
-msgid "(BoolOpt) Enable RDP related features"
-msgstr ""
-
-#: ./doc/common/tables/nova-rdp.xml26(td)
-msgid "html5_proxy_base_url = http://127.0.0.1:6083/"
-msgstr ""
-
-#: ./doc/common/tables/nova-rdp.xml27(td)
-msgid ""
-"(StrOpt) Location of RDP html5 console proxy, in the form "
-"\"http://127.0.0.1:6083/\""
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml8(caption)
-msgid "Description of configuration options for quotas"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml22(td)
-msgid "max_routes = 30"
+#: ./doc/common/tables/cinder-coraid.xml35(td)
+msgid "(StrOpt) Volume Type key name to store ESM Repository Name"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml23(td)
-msgid "(IntOpt) Maximum number of routes"
+#: ./doc/common/tables/cinder-coraid.xml38(td)
+msgid "coraid_user = admin"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml26(th)
-msgid "[QUOTAS]"
+#: ./doc/common/tables/cinder-coraid.xml39(td)
+msgid "(StrOpt) User name to connect to Coraid ESM"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml29(td)
-msgid "default_quota = -1"
+#: ./doc/common/tables/neutron-wsgi.xml8(caption)
+#: ./doc/common/tables/glance-wsgi.xml8(caption)
+#: ./doc/common/tables/nova-wsgi.xml8(caption)
+msgid "Description of configuration options for wsgi"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml30(td)
-msgid ""
-"(IntOpt) Default number of resource allowed per tenant. A negative value "
-"means unlimited."
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml33(td)
-msgid "quota_driver = neutron.db.quota_db.DbQuotaDriver"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml34(td)
-#: ./doc/common/tables/nova-quota.xml35(td)
-msgid "(StrOpt) Default driver to use for quota checks"
+#: ./doc/common/tables/neutron-wsgi.xml23(td)
+#: ./doc/common/tables/trove-debug.xml27(td)
+msgid "(IntOpt) Number of backlog requests to configure the socket with"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml37(td)
-msgid "quota_firewall = 1"
+#: ./doc/common/tables/neutron-wsgi.xml26(td)
+msgid "retry_until_window = 30"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml38(td)
-msgid ""
-"(IntOpt) Number of firewalls allowed per tenant. A negative value means "
-"unlimited."
+#: ./doc/common/tables/neutron-wsgi.xml27(td)
+msgid "(IntOpt) Number of seconds to keep retrying to listen"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml41(td)
-msgid "quota_firewall_policy = 1"
+#: ./doc/common/tables/cinder-compute.xml22(td)
+msgid "nova_api_insecure = False"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml42(td)
-msgid ""
-"(IntOpt) Number of firewall policies allowed per tenant. A negative value "
-"means unlimited."
+#: ./doc/common/tables/cinder-compute.xml23(td)
+msgid "(BoolOpt) Allow to perform insecure SSL requests to nova"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml45(td)
-msgid "quota_firewall_rule = -1"
+#: ./doc/common/tables/cinder-compute.xml26(td)
+msgid "nova_ca_certificates_file = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml46(td)
+#: ./doc/common/tables/cinder-compute.xml27(td)
 msgid ""
-"(IntOpt) Number of firewall rules allowed per tenant. A negative value means"
-" unlimited."
+"(StrOpt) Location of ca certificates file to use for nova client requests."
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml49(td)
-msgid "quota_floatingip = 50"
+#: ./doc/common/tables/cinder-compute.xml30(td)
+msgid "nova_catalog_admin_info = compute:nova:adminURL"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml50(td)
-msgid ""
-"(IntOpt) Number of floating IPs allowed per tenant. A negative value means "
-"unlimited."
+#: ./doc/common/tables/cinder-compute.xml31(td)
+msgid "(StrOpt) Same as nova_catalog_info, but for admin endpoint."
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml53(td)
-msgid "quota_health_monitor = -1"
+#: ./doc/common/tables/cinder-compute.xml34(td)
+msgid "nova_catalog_info = compute:nova:publicURL"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml54(td)
+#: ./doc/common/tables/cinder-compute.xml35(td)
 msgid ""
-"(IntOpt) Number of health monitors allowed per tenant. A negative value "
-"means unlimited."
+"(StrOpt) Info to match when looking for nova in the service catalog. Format "
+"is : separated values of the form: "
+"&lt;service_type&gt;:&lt;service_name&gt;:&lt;endpoint_type&gt;"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml57(td)
-msgid "quota_items = network, subnet, port"
+#: ./doc/common/tables/cinder-compute.xml38(td)
+msgid "nova_endpoint_admin_template = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml58(td)
-msgid "(ListOpt) Resource name(s) that are supported in quota features"
+#: ./doc/common/tables/cinder-compute.xml39(td)
+msgid "(StrOpt) Same as nova_endpoint_template, but for admin endpoint."
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml61(td)
-msgid "quota_member = -1"
+#: ./doc/common/tables/cinder-compute.xml42(td)
+msgid "nova_endpoint_template = None"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml62(td)
+#: ./doc/common/tables/cinder-compute.xml43(td)
 msgid ""
-"(IntOpt) Number of pool members allowed per tenant. A negative value means "
-"unlimited."
+"(StrOpt) Override service catalog lookup with template for nova endpoint "
+"e.g. http://localhost:8774/v2/%(project_id)s"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml65(td)
-msgid "quota_network = 10"
+#: ./doc/common/tables/cinder-compute.xml47(td)
+msgid "(StrOpt) region name of this node"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml66(td)
-msgid ""
-"(IntOpt) Number of networks allowed per tenant.A negative value means "
-"unlimited."
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml69(td)
-msgid "quota_network_gateway = 5"
+#: ./doc/common/tables/swift-rsyncd-object.xml7(literal)
+msgid "[object]"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml70(td)
-msgid ""
-"(IntOpt) Number of network gateways allowed per tenant, -1 for unlimited"
+#: ./doc/common/tables/swift-rsyncd-object.xml18(td)
+msgid "max connections = 8"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml73(td)
-msgid "quota_packet_filter = 100"
+#: ./doc/common/tables/swift-rsyncd-object.xml27(td)
+msgid "lock file = /var/lock/object.lock"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml74(td)
-msgid "(IntOpt) Number of packet_filters allowed per tenant, -1 for unlimited"
+#: ./doc/common/tables/glance-wsgi.xml23(td)
+msgid "(IntOpt) port for eventlet backdoor to listen"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml77(td)
-msgid "quota_pool = 10"
+#: ./doc/common/tables/glance-wsgi.xml26(td)
+msgid "eventlet_hub = poll"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml78(td)
+#: ./doc/common/tables/glance-wsgi.xml27(td)
 msgid ""
-"(IntOpt) Number of pools allowed per tenant. A negative value means "
-"unlimited."
+"(StrOpt) Name of eventlet hub to use. Traditionally, we have only supported "
+"'poll', however 'selects' may be appropriate for some platforms. See "
+"http://eventlet.net/doc/hubs.html for more details."
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml81(td)
-msgid "quota_port = 50"
-msgstr ""
-
-#: ./doc/common/tables/neutron-quotas.xml82(td)
+#: ./doc/common/tables/glance-wsgi.xml35(td)
 msgid ""
-"(IntOpt) Number of ports allowed per tenant. A negative value means "
-"unlimited."
+"(IntOpt) The value for the socket option TCP_KEEPIDLE. This is the time in "
+"seconds that the connection must be idle before TCP starts sending keepalive"
+" probes."
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml85(td)
-msgid "quota_router = 10"
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml7(literal)
+msgid "[drive-audit]"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml86(td)
-msgid ""
-"(IntOpt) Number of routers allowed per tenant. A negative value means "
-"unlimited."
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml7(literal)
+msgid "drive-audit.conf-sample"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml89(td)
-msgid "quota_security_group = 10"
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml18(td)
+msgid "device_dir = /srv/node"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml90(td)
-msgid ""
-"(IntOpt) Number of security groups allowed per tenant. A negative value "
-"means unlimited."
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml18(td)
+msgid "Directory devices are mounted under"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml93(td)
-msgid "quota_security_group_rule = 100"
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml30(td)
+msgid "minutes = 60"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml94(td)
-msgid ""
-"(IntOpt) Number of security rules allowed per tenant. A negative value means"
-" unlimited."
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml30(td)
+msgid "Number of minutes to look back in `/var/log/kern.log`"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml97(td)
-msgid "quota_subnet = 10"
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml33(td)
+msgid "error_limit = 1"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml98(td)
-msgid ""
-"(IntOpt) Number of subnets allowed per tenant, A negative value means "
-"unlimited."
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml33(td)
+msgid "Number of errors to find before a device is unmounted"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml101(td)
-msgid "quota_vip = 10"
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml36(td)
+msgid "log_file_pattern = /var/log/kern*"
 msgstr ""
 
-#: ./doc/common/tables/neutron-quotas.xml102(td)
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml36(td)
 msgid ""
-"(IntOpt) Number of vips allowed per tenant. A negative value means "
-"unlimited."
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml8(caption)
-msgid "Description of configuration options for guestagent"
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml22(td)
-msgid "agent_call_high_timeout = 60"
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml26(td)
-msgid "agent_call_low_timeout = 5"
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml30(td)
-msgid "agent_heartbeat_time = 10"
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml34(td)
-msgid "guest_config = $pybasedir/etc/trove/trove-guestagent.conf.sample"
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml35(td)
-msgid "(StrOpt) Path to guestagent config file."
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml38(td)
-msgid "guest_id = None"
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml42(td)
-msgid "ignore_dbs = lost+found, mysql, information_schema"
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml46(td)
-msgid "ignore_users = os_admin, root"
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml50(td)
-msgid "mount_options = defaults,noatime"
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml54(td)
-msgid "restore_namespace = trove.guestagent.strategies.restore.mysql_impl"
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml55(td)
-msgid "(StrOpt) Namespace to load restore strategies from."
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml58(td)
-msgid "storage_namespace = trove.guestagent.strategies.storage.swift"
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml59(td)
-msgid "(StrOpt) Namespace to load the default storage strategy from."
-msgstr ""
-
-#: ./doc/common/tables/trove-guestagent.xml62(td)
-msgid "storage_strategy = SwiftStorage"
+"Location of the log file with globbing pattern to check against device "
+"errors locate device blocks with errors in the log file"
 msgstr ""
 
-#: ./doc/common/tables/trove-guestagent.xml63(td)
-msgid "(StrOpt) Default strategy to store backups."
+#: ./doc/common/tables/swift-drive-audit-drive-audit.xml39(td)
+msgid "regex_pattern_1 = \\berror\\b.*\\b(dm-[0-9]{1,2}\\d?)\\b"
 msgstr ""
 
 #: ./doc/common/tables/nova-baremetal.xml8(caption)
@@ -47798,431 +46609,143 @@ msgstr ""
 msgid "(StrOpt) The XenAPI VIF driver using XenServer Network APIs."
 msgstr ""
 
-#: ./doc/common/tables/heat-clients_keystone.xml8(caption)
-msgid "Description of configuration options for clients_keystone"
+#: ./doc/common/tables/cinder-backups_tsm.xml8(caption)
+msgid "Description of configuration options for backups_tsm"
 msgstr ""
 
-#: ./doc/common/tables/heat-clients_keystone.xml19(th)
-msgid "[clients_keystone]"
+#: ./doc/common/tables/cinder-backups_tsm.xml22(td)
+msgid "backup_tsm_compression = True"
 msgstr ""
 
-#: ./doc/common/tables/swift-account-server-pipeline-main.xml18(td)
-msgid "pipeline = healthcheck recon account-server"
+#: ./doc/common/tables/cinder-backups_tsm.xml23(td)
+msgid "(BoolOpt) Enable or Disable compression for backups"
 msgstr ""
 
-#: ./doc/common/tables/keystone-rabbit.xml8(caption)
-msgid "Description of configuration options for rabbit"
+#: ./doc/common/tables/cinder-backups_tsm.xml26(td)
+msgid "backup_tsm_password = password"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml22(td)
-msgid "admin_role = admin"
+#: ./doc/common/tables/cinder-backups_tsm.xml27(td)
+msgid "(StrOpt) TSM password for the running username"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml23(td)
-msgid "(StrOpt) Role used to identify an authenticated user as administrator."
+#: ./doc/common/tables/cinder-backups_tsm.xml30(td)
+msgid "backup_tsm_volume_prefix = backup"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml26(td)
-msgid "allow_anonymous_access = False"
+#: ./doc/common/tables/cinder-backups_tsm.xml31(td)
+msgid "(StrOpt) Volume prefix for the backup id when backing up to TSM"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml27(td)
+#: ./doc/common/tables/cinder-san.xml8(caption)
+msgid "Description of configuration options for san"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san.xml22(td)
+msgid "san_clustername ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-san.xml23(td)
+msgid "(StrOpt) Cluster name to use for creating volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san.xml26(td)
+msgid "san_ip ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-san.xml27(td)
+msgid "(StrOpt) IP address of SAN controller"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san.xml30(td)
+msgid "san_is_local = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san.xml31(td)
 msgid ""
-"(BoolOpt) Allow unauthenticated users to access the API with read-only "
-"privileges. This only applies when using ContextMiddleware."
+"(BoolOpt) Execute commands locally instead of over SSH; use if the volume "
+"service is running on the SAN device"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml30(td)
-msgid "default_publisher_id = image.localhost"
+#: ./doc/common/tables/cinder-san.xml34(td)
+msgid "san_login = admin"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml31(td)
-msgid "(StrOpt) Default publisher_id for outgoing notifications."
+#: ./doc/common/tables/cinder-san.xml35(td)
+msgid "(StrOpt) Username for SAN controller"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml34(td)
-msgid "default_store = file"
+#: ./doc/common/tables/cinder-san.xml38(td)
+msgid "san_password ="
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml35(td)
+#: ./doc/common/tables/cinder-san.xml39(td)
+msgid "(StrOpt) Password for SAN controller"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san.xml42(td)
+msgid "san_private_key ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-san.xml43(td)
+msgid "(StrOpt) Filename of private key to use for SSH authentication"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san.xml46(td)
+msgid "san_ssh_port = 22"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san.xml47(td)
+msgid "(IntOpt) SSH port to use with SAN"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san.xml50(td)
+msgid "san_thin_provision = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san.xml51(td)
+msgid "(BoolOpt) Use thin provisioning for SAN volumes?"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san.xml54(td)
+msgid "ssh_conn_timeout = 30"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san.xml55(td)
+msgid "(IntOpt) SSH connection timeout in seconds"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san.xml58(td)
+msgid "ssh_max_pool_conn = 5"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san.xml59(td)
+msgid "(IntOpt) Maximum ssh connections in the pool"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san.xml62(td)
+msgid "ssh_min_pool_conn = 1"
+msgstr ""
+
+#: ./doc/common/tables/cinder-san.xml63(td)
+msgid "(IntOpt) Minimum ssh connections in the pool"
+msgstr ""
+
+#: ./doc/common/tables/nova-logging.xml26(td)
 msgid ""
-"(StrOpt) Default scheme to use to store image data. The scheme must be "
-"registered by one of the stores defined by the 'known_stores' config option."
+"default_log_levels = amqp=WARN, amqplib=WARN, boto=WARN, qpid=WARN, "
+"sqlalchemy=WARN, suds=INFO, oslo.messaging=INFO, iso8601=WARN"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml39(td)
-msgid "(BoolOpt) Deploy the v1 OpenStack Images API."
+#: ./doc/common/tables/nova-logging.xml35(td)
+msgid "(BoolOpt) Make exception message format errors fatal"
 msgstr ""
 
-#: ./doc/common/tables/glance-api.xml42(td)
-msgid "enable_v1_registry = True"
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml43(td)
-msgid "(BoolOpt) Deploy the v1 OpenStack Registry API."
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml47(td)
-msgid "(BoolOpt) Deploy the v2 OpenStack Images API."
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml50(td)
-msgid "enable_v2_registry = True"
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml51(td)
-msgid "(BoolOpt) Deploy the v2 OpenStack Registry API."
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml54(td)
-msgid "image_size_cap = 1099511627776"
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml55(td)
+#: ./doc/common/tables/nova-logging.xml66(td)
 msgid ""
-"(IntOpt) Maximum size of image a user can upload in bytes. Defaults to "
-"1099511627776 bytes (1 TB)."
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml58(td)
-msgid "known_stores = glance.store.filesystem.Store, glance.store.http.Store"
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml59(td)
-msgid ""
-"(ListOpt) List of which store classes and store class locations are "
-"currently known to glance at startup."
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml62(td)
-msgid "location_strategy = location_order"
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml63(td)
-msgid ""
-"(StrOpt) This value sets what strategy will be used to determine the image "
-"location order. Currently two strategies are packaged with Glance "
-"'location_order' and 'store_type'."
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml66(td)
-msgid "owner_is_tenant = True"
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml67(td)
-msgid ""
-"(BoolOpt) When true, this option sets the owner of an image to be the "
-"tenant. Otherwise, the owner of the image will be the authenticated user "
-"issuing the request."
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml70(td)
-msgid "send_identity_headers = False"
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml71(td)
-msgid ""
-"(BoolOpt) Whether to pass through headers containing user and tenant "
-"information when making requests to the registry. This allows the registry "
-"to use the context middleware without the keystoneclients' auth_token "
-"middleware, removing calls to the keystone auth service. It is recommended "
-"that when using this option, secure communication between glance api and "
-"glance registry is ensured by means other than auth_token middleware."
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml74(td)
-msgid "show_multiple_locations = False"
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml75(td)
-msgid ""
-"(BoolOpt) Whether to include the backend image locations in image "
-"properties. Revealing storage location can be a security risk, so use this "
-"setting with caution! The overrides show_image_direct_url."
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml78(td)
-msgid "use_user_token = True"
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml79(td)
-msgid ""
-"(BoolOpt) Whether to pass through the user token when making requests to the"
-" registry."
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml82(th)
-msgid "[store_type_location_strategy]"
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml85(td)
-msgid "store_type_preference ="
-msgstr ""
-
-#: ./doc/common/tables/glance-api.xml86(td)
-msgid ""
-"(ListOpt) The store names to use to get store preference order. The name "
-"must be registered by one of the stores defined by the 'known_stores' config"
-" option. This option will be applied when you using 'store_type' option as "
-"image location strategy defined by the 'location_strategy' config option."
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml22(td)
-msgid ""
-"scheduler_default_filters = AvailabilityZoneFilter, CapacityFilter, "
-"CapabilitiesFilter"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml26(td)
-msgid "scheduler_default_weighers = CapacityWeigher"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml27(td)
-msgid "(ListOpt) Which weigher class names to use for weighing hosts."
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml30(td)
-msgid "scheduler_driver = cinder.scheduler.filter_scheduler.FilterScheduler"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml31(td)
-msgid "(StrOpt) Default scheduler driver to use"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml34(td)
-msgid "scheduler_host_manager = cinder.scheduler.host_manager.HostManager"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml42(td)
-msgid "scheduler_manager = cinder.scheduler.manager.SchedulerManager"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml43(td)
-msgid "(StrOpt) full class name for the Manager for scheduler"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml47(td)
-msgid "(IntOpt) Maximum number of attempts to schedule an volume"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml50(td)
-msgid "scheduler_topic = cinder-scheduler"
-msgstr ""
-
-#: ./doc/common/tables/cinder-scheduler.xml51(td)
-msgid "(StrOpt) the topic scheduler nodes listen on"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml22(td)
-msgid "admin_bind_host = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml23(td)
-msgid ""
-"(StrOpt) The IP Address of the network interface to for the admin service to"
-" listen on."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml26(td)
-msgid "admin_endpoint = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml27(td)
-msgid ""
-"(StrOpt) The base admin endpoint URL for keystone that are advertised to "
-"clients (NOTE: this does NOT affect how keystone listens for connections). "
-"Defaults to the base host URL of the request. Eg a request to "
-"http://server:35357/v2.0/users will default to http://server:35357. You "
-"should only need to set this value if the base URL contains a path (eg "
-"/prefix/v2.0) or the endpoint should be found on a different server."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml30(td)
-msgid "admin_port = 35357"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml31(td)
-msgid "(IntOpt) The port number which the admin service listens on."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml34(td)
-msgid "admin_token = ADMIN"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml35(td)
-msgid ""
-"(StrOpt) A \"shared secret\" that can be used to bootstrap Keystone. This "
-"\"token\" does not represent a user, and carries no explicit authorization. "
-"To disable in production (highly recommended), remove "
-"AdminTokenAuthMiddleware from your paste application pipelines (for example,"
-" in keystone-paste.ini)."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml38(td)
-msgid "compute_port = 8774"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml39(td)
-msgid "(IntOpt) The port which the OpenStack Compute service listens on."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml42(td)
-msgid "domain_id_immutable = True"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml43(td)
-msgid ""
-"(BoolOpt) Set this to false if you want to enable the ability for user, "
-"group and project entities to be moved between domains by updating their "
-"domain_id. Allowing such movement is not recommended if the scope of a "
-"domain admin is being restricted by use of an appropriate policy file (see "
-"policy.v3cloudsample as an example)."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml47(td)
-msgid ""
-"(IntOpt) The maximum number of entities that will be returned in a "
-"collection can be set with list_limit, with no limit set by default. This "
-"global limit may be then overridden for a specific driver, by specifying a "
-"list_limit in the appropriate section (e.g. [assignment])."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml50(td)
-msgid "max_param_size = 64"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml51(td)
-msgid "(IntOpt) limit the sizes of user &amp; tenant ID/names."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml55(td)
-msgid ""
-"(IntOpt) enforced by optional sizelimit middleware "
-"(keystone.middleware:RequestBodySizeLimiter)."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml58(td)
-msgid "max_token_size = 8192"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml59(td)
-msgid ""
-"(IntOpt) similar to max_param_size, but provides an exception for token "
-"values."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml62(td)
-msgid "member_role_id = 9fe2ff9ee4384b1894a90878d3e92bab"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml63(td)
-msgid ""
-"(StrOpt) During a SQL upgrade member_role_id will be used to create a new "
-"role that will replace records in the user_tenant_membership table with "
-"explicit role grants. After migration, the member_role_id will be used in "
-"the API add_user_to_project."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml66(td)
-msgid "member_role_name = _member_"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml67(td)
-msgid ""
-"(StrOpt) During a SQL upgrade member_role_id will be used to create a new "
-"role that will replace records in the user_tenant_membership table with "
-"explicit role grants. After migration, member_role_name will be ignored."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml70(td)
-msgid "public_bind_host = 0.0.0.0"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml71(td)
-msgid ""
-"(StrOpt) The IP Address of the network interface to for the public service "
-"to listen on."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml74(td)
-msgid "public_endpoint = None"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml75(td)
-msgid ""
-"(StrOpt) The base public endpoint URL for keystone that are advertised to "
-"clients (NOTE: this does NOT affect how keystone listens for connections). "
-"Defaults to the base host URL of the request. Eg a request to "
-"http://server:5000/v2.0/users will default to http://server:5000. You should"
-" only need to set this value if the base URL contains a path (eg "
-"/prefix/v2.0) or the endpoint should be found on a different server."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml78(td)
-msgid "public_port = 5000"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml79(td)
-msgid "(IntOpt) The port number which the public service listens on."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml82(td)
-msgid "tcp_keepalive = False"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml83(td)
-msgid ""
-"(BoolOpt) Set this to True if you want to enable TCP_KEEPALIVE on server "
-"sockets i.e. sockets used by the keystone wsgi server for client "
-"connections."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml87(td)
-msgid ""
-"(IntOpt) Sets the value of TCP_KEEPIDLE in seconds for each server socket. "
-"Only applies if tcp_keepalive is True. Not supported on OS X."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml90(th)
-msgid "[endpoint_filter]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml93(td)
-msgid "driver = keystone.contrib.endpoint_filter.backends.sql.EndpointFilter"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml94(td)
-msgid "(StrOpt) Keystone Endpoint Filter backend driver"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml97(td)
-msgid "return_all_endpoints_if_no_filter = True"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml98(td)
-msgid "(BoolOpt) Toggle to return all active endpoints if no filter exists."
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml104(td)
-msgid "config_file = keystone-paste.ini"
-msgstr ""
-
-#: ./doc/common/tables/keystone-api.xml105(td)
-msgid ""
-"(StrOpt) Name of the paste configuration file that defines the available "
-"pipelines."
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ncs.xml8(caption)
-msgid "Description of configuration options for ml2_ncs"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ncs.xml19(th)
-msgid "[ml2_ncs]"
-msgstr ""
-
-#: ./doc/common/tables/neutron-ml2_ncs.xml31(td)
-msgid "(StrOpt) HTTP URL of Tail-f NCS REST interface."
+"logging_context_format_string = %(asctime)s.%(msecs)03d %(process)d "
+"%(levelname)s %(name)s [%(request_id)s %(user)s %(tenant)s] "
+"%(instance)s%(message)s"
 msgstr ""
 
 #: ./doc/common/tables/neutron-nec.xml8(caption)
@@ -48329,26 +46852,209 @@ msgstr ""
 msgid "(StrOpt) Name of the FWaaS Driver"
 msgstr ""
 
-#: ./doc/common/tables/neutron-cadf.xml8(caption)
-msgid "Description of configuration options for cadf"
+#: ./doc/common/tables/keystone-security.xml8(caption)
+msgid "Description of configuration options for security"
 msgstr ""
 
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml7(literal)
-msgid "[object-expirer]"
+#: ./doc/common/tables/keystone-security.xml22(td)
+msgid "crypt_strength = 40000"
 msgstr ""
 
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml33(td)
-msgid "processes = 0"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml36(td)
-msgid "process = 0"
-msgstr ""
-
-#: ./doc/common/tables/swift-object-expirer-object-expirer.xml36(td)
+#: ./doc/common/tables/keystone-security.xml23(td)
 msgid ""
-"(it will actually accept(2) N + 1). Setting this to one (1) will only handle"
-" one request at a time, without accepting another request concurrently."
+"(IntOpt) The value passed as the keyword \"rounds\" to passlib encrypt "
+"method."
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_neutron.xml8(caption)
+msgid "Description of configuration options for clients_neutron"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_neutron.xml19(th)
+msgid "[clients_neutron]"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml22(td)
+msgid "api_rate_limit = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml23(td)
+msgid ""
+"(BoolOpt) Whether to use per-user rate limiting for the api. This option is "
+"only used by v2 api. Rate limiting is removed from v3 api."
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml30(td)
+msgid "enabled_apis = ec2, osapi_compute, metadata"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml31(td)
+msgid "(ListOpt) A list of APIs to enable by default"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml34(td)
+msgid "enabled_ssl_apis ="
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml35(td)
+msgid "(ListOpt) A list of APIs with enabled SSL"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml38(td)
+msgid "instance_name_template = instance-%08x"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml39(td)
+msgid "(StrOpt) Template string to be used to generate instance names"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml46(td)
+msgid "multi_instance_display_name_template = %(name)s-%(uuid)s"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml47(td)
+msgid ""
+"(StrOpt) When creating multiple instances with a single request using the "
+"os-multiple-create API extension, this template will be used to build the "
+"display name for each instance. The benefit is that the instances end up "
+"with different hostnames. To restore legacy behavior of every instance "
+"having the same name, set this option to \"%(name)s\". Valid keys for the "
+"template are: name, uuid, count."
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml50(td)
+msgid "non_inheritable_image_properties = cache_in_nova, bittorrent"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml51(td)
+msgid ""
+"(ListOpt) These are image properties which a snapshot should not inherit "
+"from an instance"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml54(td)
+msgid "null_kernel = nokernel"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml55(td)
+msgid ""
+"(StrOpt) Kernel image that indicates not to use a kernel, but to use a raw "
+"disk image instead"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml58(td)
+msgid "osapi_compute_ext_list ="
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml59(td)
+msgid ""
+"(ListOpt) Specify list of extensions to load when using "
+"osapi_compute_extension option with "
+"nova.api.openstack.compute.contrib.select_extensions"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml62(td)
+msgid ""
+"osapi_compute_extension = "
+"['nova.api.openstack.compute.contrib.standard_extensions']"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml63(td)
+msgid "(MultiStrOpt) osapi compute extension to load"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml66(td)
+msgid "osapi_compute_link_prefix = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml67(td)
+msgid ""
+"(StrOpt) Base URL that will be presented to users in links to the OpenStack "
+"Compute API"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml70(td)
+msgid "osapi_compute_listen = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml71(td)
+msgid "(StrOpt) The IP address on which the OpenStack API will listen."
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml74(td)
+msgid "osapi_compute_listen_port = 8774"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml75(td)
+msgid "(IntOpt) The port on which the OpenStack API will listen."
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml78(td)
+msgid "osapi_compute_workers = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml79(td)
+msgid ""
+"(IntOpt) Number of workers for OpenStack API service. The default will be "
+"the number of CPUs available."
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml82(td)
+msgid "osapi_hide_server_address_states = building"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml83(td)
+msgid "(ListOpt) List of instance states that should hide network info"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml86(td)
+msgid "servicegroup_driver = db"
+msgstr ""
+
+#: ./doc/common/tables/nova-api.xml87(td)
+msgid ""
+"(StrOpt) The driver for servicegroup service (valid options are: db, zk, mc)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_mlnx.xml8(caption)
+msgid "Description of configuration options for ml2_mlnx"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_mlnx.xml22(td)
+msgid "apply_profile_patch = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_mlnx.xml23(td)
+msgid "(BoolOpt) Enable server compatibility with old nova"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_mlnx.xml26(td)
+msgid "vnic_type = mlnx_direct"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_mlnx.xml27(td)
+msgid "(StrOpt) Type of VM network interface: mlnx_direct or hostdev"
+msgstr ""
+
+#: ./doc/common/tables/keystone-trust.xml8(caption)
+msgid "Description of configuration options for trust"
+msgstr ""
+
+#: ./doc/common/tables/keystone-trust.xml19(th)
+msgid "[trust]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-trust.xml22(td)
+msgid "driver = keystone.trust.backends.sql.Trust"
+msgstr ""
+
+#: ./doc/common/tables/keystone-trust.xml23(td)
+msgid "(StrOpt) Keystone Trust backend driver."
+msgstr ""
+
+#: ./doc/common/tables/keystone-trust.xml27(td)
+msgid ""
+"(BoolOpt) delegation and impersonation features can be optionally disabled."
 msgstr ""
 
 #: ./doc/common/tables/glance-cinder.xml8(caption)
@@ -48381,475 +47087,758 @@ msgstr ""
 msgid "(IntOpt) Number of cinderclient retries on failed http calls."
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane.xml8(caption)
-msgid "Description of configuration options for embrane"
+#: ./doc/common/tables/swift-object-server-object-updater.xml7(literal)
+msgid "[object-updater]"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane.xml22(td)
-msgid "admin_username = admin"
+#: ./doc/common/tables/swift-object-server-object-updater.xml18(td)
+msgid "log_name = object-updater"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane.xml26(td)
-msgid "async_requests = True"
+#: ./doc/common/tables/glance-common.xml22(td)
+msgid "allow_additional_image_properties = True"
 msgstr ""
 
-#: ./doc/common/tables/neutron-embrane.xml31(td)
-msgid "(StrOpt) Dummy user traffic Security Zone id"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane.xml39(td)
-msgid "(StrOpt) In band Security Zone id"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane.xml43(td)
-msgid "(StrOpt) Management Security Zone id"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane.xml47(td)
-msgid "(StrOpt) Out of band Security Zone id"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane.xml50(td)
-msgid "resource_pool_id = default"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane.xml54(td)
-msgid "router_image = None"
-msgstr ""
-
-#: ./doc/common/tables/neutron-embrane.xml55(td)
-msgid "(StrOpt) Router image id (Embrane FW/VPN)"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-pipeline-main.xml18(td)
+#: ./doc/common/tables/glance-common.xml23(td)
 msgid ""
-"pipeline = catch_errors gatekeeper healthcheck proxy-logging cache "
-"container_sync bulk tempurl slo dlo ratelimit tempauth container-quotas "
-"account-quotas proxy-logging proxy-server"
+"(BoolOpt) Whether to allow users to specify image properties beyond what the"
+" image schema provides"
 msgstr ""
 
-#: ./doc/common/tables/nova-upgrade_levels.xml8(caption)
-msgid "Description of configuration options for upgrade_levels"
+#: ./doc/common/tables/glance-common.xml26(td)
+msgid "api_limit_max = 1000"
 msgstr ""
 
-#: ./doc/common/tables/nova-upgrade_levels.xml22(td)
-msgid "scheduler = nova.cells.scheduler.CellsScheduler"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml23(td)
-msgid "(StrOpt) Cells scheduler to use"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml29(td)
-msgid "cells = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml30(td)
-msgid "(StrOpt) Set a version cap for messages sent to local cells services"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml33(td)
-msgid "cert = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml34(td)
-msgid "(StrOpt) Set a version cap for messages sent to cert services"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml37(td)
-msgid "compute = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml38(td)
+#: ./doc/common/tables/glance-common.xml27(td)
 msgid ""
-"(StrOpt) Set a version cap for messages sent to compute services. If you "
-"plan to do a live upgrade from havana to icehouse, you should set this "
-"option to \"icehouse-compat\" before beginning the live upgrade procedure."
+"(IntOpt) Maximum permissible number of items that could be returned by a "
+"request"
 msgstr ""
 
-#: ./doc/common/tables/nova-upgrade_levels.xml41(td)
-msgid "conductor = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml42(td)
-msgid "(StrOpt) Set a version cap for messages sent to conductor services"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml45(td)
-msgid "console = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml46(td)
-msgid "(StrOpt) Set a version cap for messages sent to console services"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml49(td)
-msgid "consoleauth = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml50(td)
-msgid "(StrOpt) Set a version cap for messages sent to consoleauth services"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml53(td)
-msgid "intercell = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml54(td)
-msgid "(StrOpt) Set a version cap for messages sent between cells services"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml57(td)
-msgid "network = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml58(td)
-msgid "(StrOpt) Set a version cap for messages sent to network services"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml61(td)
-msgid "scheduler = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-upgrade_levels.xml62(td)
-msgid "(StrOpt) Set a version cap for messages sent to scheduler services"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml7(literal)
-msgid "[filter:cname_lookup]"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml18(td)
-msgid "use = egg:swift#cname_lookup"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml21(td)
-msgid "set log_name = cname_lookup"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml36(td)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml36(td)
-msgid "storage_domain = example.com"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml36(td)
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml36(td)
+#: ./doc/common/tables/glance-common.xml31(td)
 msgid ""
-"Domain that matches your cloud. Multiple domains can be specified using a "
-"comma-separated list."
+"(IntOpt) The backlog value that will be used when creating the TCP listener "
+"socket."
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml40(td)
-msgid "lookup_depth = 1"
+#: ./doc/common/tables/glance-common.xml38(td)
+msgid "bind_port = None"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-cname_lookup.xml40(td)
+#: ./doc/common/tables/glance-common.xml42(td)
+msgid "data_api = glance.db.sqlalchemy.api"
+msgstr ""
+
+#: ./doc/common/tables/glance-common.xml43(td)
+msgid "(StrOpt) Python module path of data access API"
+msgstr ""
+
+#: ./doc/common/tables/glance-common.xml50(td)
+msgid "image_location_quota = 10"
+msgstr ""
+
+#: ./doc/common/tables/glance-common.xml51(td)
 msgid ""
-"Because CNAMES can be recursive, specifies the number of levels through "
-"which to search."
+"(IntOpt) Maximum number of locations allowed on an image. Negative values "
+"evaluate to unlimited."
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-inspector.xml8(caption)
-msgid "Description of configuration options for inspector"
+#: ./doc/common/tables/glance-common.xml54(td)
+msgid "image_member_quota = 128"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-inspector.xml22(td)
-msgid "hypervisor_inspector = libvirt"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-inspector.xml23(td)
-msgid "(StrOpt) Inspector to use for inspecting the hypervisor layer."
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-inspector.xml26(td)
-msgid "libvirt_type = kvm"
-msgstr ""
-
-#: ./doc/common/tables/ceilometer-inspector.xml27(td)
+#: ./doc/common/tables/glance-common.xml55(td)
 msgid ""
-"(StrOpt) Libvirt domain type (valid options are: kvm, lxc, qemu, uml, xen)."
+"(IntOpt) Maximum number of image members per image. Negative values evaluate"
+" to unlimited."
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-inspector.xml30(td)
-msgid "libvirt_uri ="
+#: ./doc/common/tables/glance-common.xml58(td)
+msgid "image_property_quota = 128"
 msgstr ""
 
-#: ./doc/common/tables/ceilometer-inspector.xml31(td)
+#: ./doc/common/tables/glance-common.xml59(td)
 msgid ""
-"(StrOpt) Override the default libvirt URI (which is dependent on "
-"libvirt_type)."
+"(IntOpt) Maximum number of properties allowed on an image. Negative values "
+"evaluate to unlimited."
 msgstr ""
 
-#: ./doc/common/tables/heat-common.xml22(td)
-msgid "deferred_auth_method = password"
+#: ./doc/common/tables/glance-common.xml62(td)
+msgid "image_tag_quota = 128"
 msgstr ""
 
-#: ./doc/common/tables/heat-common.xml23(td)
-msgid "(StrOpt) Select deferred auth method, stored password or trusts."
-msgstr ""
-
-#: ./doc/common/tables/heat-common.xml26(td)
-msgid "environment_dir = /etc/heat/environment.d"
-msgstr ""
-
-#: ./doc/common/tables/heat-common.xml27(td)
-msgid "(StrOpt) The directory to search for environment files."
-msgstr ""
-
-#: ./doc/common/tables/heat-common.xml30(td)
-msgid "event_purge_batch_size = 10"
-msgstr ""
-
-#: ./doc/common/tables/heat-common.xml31(td)
+#: ./doc/common/tables/glance-common.xml63(td)
 msgid ""
-"(IntOpt) Controls how many events will be pruned whenever a stack's events "
-"exceed max_events_per_stack. Set this lower to keep more events at the "
-"expense of more frequent purges."
+"(IntOpt) Maximum number of tags allowed on an image. Negative values "
+"evaluate to unlimited."
 msgstr ""
 
-#: ./doc/common/tables/heat-common.xml34(td)
-msgid "instance_driver = heat.engine.nova"
+#: ./doc/common/tables/glance-common.xml66(td)
+msgid "limit_param_default = 25"
 msgstr ""
 
-#: ./doc/common/tables/heat-common.xml35(td)
-msgid "(StrOpt) Driver to use for controlling instances."
-msgstr ""
-
-#: ./doc/common/tables/heat-common.xml38(td)
-msgid "instance_user = ec2-user"
-msgstr ""
-
-#: ./doc/common/tables/heat-common.xml39(td)
+#: ./doc/common/tables/glance-common.xml67(td)
 msgid ""
-"(StrOpt) The default user for new instances. This option is deprecated and "
-"will be removed in the Juno release. If it's empty, Heat will use the "
-"default user set up with your cloud image (for OS::Nova::Server) or "
-"'ec2-user' (for AWS::EC2::Instance)."
+"(IntOpt) Default value for the number of items returned by a request if not "
+"specified explicitly in the request"
 msgstr ""
 
-#: ./doc/common/tables/heat-common.xml42(td)
-msgid "keystone_backend = heat.common.heat_keystoneclient.KeystoneClientV3"
+#: ./doc/common/tables/glance-common.xml74(td)
+msgid "metadata_encryption_key = None"
 msgstr ""
 
-#: ./doc/common/tables/heat-common.xml43(td)
-msgid "(StrOpt) Fully qualified class name to use as a keystone backend."
-msgstr ""
-
-#: ./doc/common/tables/heat-common.xml47(td)
-msgid "(IntOpt) Seconds between running periodic tasks."
-msgstr ""
-
-#: ./doc/common/tables/heat-common.xml50(td)
-msgid "plugin_dirs = /usr/lib64/heat, /usr/lib/heat"
-msgstr ""
-
-#: ./doc/common/tables/heat-common.xml51(td)
-msgid "(ListOpt) List of directories to search for plug-ins."
-msgstr ""
-
-#: ./doc/common/tables/heat-common.xml54(th)
-msgid "[revision]"
-msgstr ""
-
-#: ./doc/common/tables/heat-common.xml57(td)
-msgid "heat_revision = unknown"
-msgstr ""
-
-#: ./doc/common/tables/heat-common.xml58(td)
+#: ./doc/common/tables/glance-common.xml75(td)
 msgid ""
-"(StrOpt) Heat build revision. If you would prefer to manage your build "
-"revision separately, you can move this section to a different file and add "
-"it as another config option."
+"(StrOpt) Key used for encrypting sensitive metadata while talking to the "
+"registry or database."
 msgstr ""
 
-#: ./doc/common/tables/keystone-federation.xml8(caption)
-msgid "Description of configuration options for federation"
+#: ./doc/common/tables/glance-common.xml78(td)
+msgid "notifier_strategy = default"
 msgstr ""
 
-#: ./doc/common/tables/keystone-federation.xml19(th)
-msgid "[federation]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-federation.xml22(td)
-msgid "assertion_prefix ="
-msgstr ""
-
-#: ./doc/common/tables/keystone-federation.xml23(td)
+#: ./doc/common/tables/glance-common.xml79(td)
 msgid ""
-"(StrOpt) Value to be used when filtering assertion parameters from the "
-"environment."
+"(StrOpt) Notifications can be sent when images are create, updated or "
+"deleted. There are three methods of sending notifications, logging (via the "
+"log_file directive), rabbit (via a rabbitmq queue), qpid (via a Qpid message"
+" queue), or noop (no notifications sent, the default). (DEPRECATED)"
 msgstr ""
 
-#: ./doc/common/tables/keystone-federation.xml26(td)
-msgid "driver = keystone.contrib.federation.backends.sql.Federation"
+#: ./doc/common/tables/glance-common.xml83(td)
+msgid "(StrOpt) Region name of this node."
 msgstr ""
 
-#: ./doc/common/tables/keystone-federation.xml27(td)
-msgid "(StrOpt) Keystone Federation backend driver."
+#: ./doc/common/tables/glance-common.xml86(td)
+msgid "property_protection_file = None"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zadara.xml8(caption)
-msgid "Description of configuration options for zadara"
+#: ./doc/common/tables/glance-common.xml87(td)
+msgid "(StrOpt) The location of the property protection file."
 msgstr ""
 
-#: ./doc/common/tables/cinder-zadara.xml22(td)
-msgid "zadara_password = None"
+#: ./doc/common/tables/glance-common.xml90(td)
+msgid "property_protection_rule_format = roles"
 msgstr ""
 
-#: ./doc/common/tables/cinder-zadara.xml23(td)
-msgid "(StrOpt) Password for the VPSA"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml26(td)
-msgid "zadara_user = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml27(td)
-msgid "(StrOpt) User name for the VPSA"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml30(td)
-msgid "zadara_vol_encrypt = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml31(td)
-msgid "(BoolOpt) Default encryption policy for volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml34(td)
-msgid "zadara_vol_name_template = OS_%s"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml35(td)
-msgid "(StrOpt) Default template for VPSA volume names"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml38(td)
-msgid "zadara_vol_thin = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml39(td)
-msgid "(BoolOpt) Default thin provisioning policy for volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml42(td)
-msgid "zadara_vpsa_allow_nonexistent_delete = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml43(td)
-msgid "(BoolOpt) Don't halt on deletion of non-existing volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml46(td)
-msgid "zadara_vpsa_auto_detach_on_delete = True"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml47(td)
-msgid "(BoolOpt) Automatically detach from servers on volume delete"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml50(td)
-msgid "zadara_vpsa_ip = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml51(td)
-msgid "(StrOpt) Management IP of Zadara VPSA"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml54(td)
-msgid "zadara_vpsa_poolname = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml55(td)
-msgid "(StrOpt) Name of VPSA storage pool for volumes"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml58(td)
-msgid "zadara_vpsa_port = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml59(td)
-msgid "(StrOpt) Zadara VPSA port number"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml62(td)
-msgid "zadara_vpsa_use_ssl = False"
-msgstr ""
-
-#: ./doc/common/tables/cinder-zadara.xml63(td)
-msgid "(BoolOpt) Use SSL connection"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml8(caption)
-msgid "Description of configuration options for nuage"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml22(td)
-msgid "auth_resource ="
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml23(td)
-msgid "(StrOpt) Nuage provided uri for initial authorization to access VSD"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml26(td)
-msgid "base_uri = /"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml27(td)
-msgid "(StrOpt) Nuage provided base uri to reach out to VSD"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml30(td)
-msgid "default_floatingip_quota = 254"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml31(td)
-msgid "(IntOpt) Per Net Partition quota of floating ips"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml34(td)
-msgid "default_net_partition_name = OpenStackDefaultNetPartition"
-msgstr ""
-
-#: ./doc/common/tables/neutron-nuage.xml35(td)
+#: ./doc/common/tables/glance-common.xml91(td)
 msgid ""
-"(StrOpt) Default Network partition in which VSD will orchestrate network "
-"resources using openstack"
+"(StrOpt) This config value indicates whether \"roles\" or \"policies\" are "
+"used in the property protection file."
 msgstr ""
 
-#: ./doc/common/tables/neutron-nuage.xml38(td)
-msgid "organization = system"
+#: ./doc/common/tables/glance-common.xml94(td)
+msgid "show_image_direct_url = False"
 msgstr ""
 
-#: ./doc/common/tables/neutron-nuage.xml39(td)
+#: ./doc/common/tables/glance-common.xml95(td)
 msgid ""
-"(StrOpt) Organization name in which VSD will orchestrate network resources "
-"using openstack"
+"(BoolOpt) Whether to include the backend image storage location in image "
+"properties. Revealing storage location can be a security risk, so use this "
+"setting with caution!"
 msgstr ""
 
-#: ./doc/common/tables/neutron-nuage.xml42(td)
-msgid "server = localhost:8800"
+#: ./doc/common/tables/glance-common.xml98(td)
+msgid "user_storage_quota = 0"
 msgstr ""
 
-#: ./doc/common/tables/neutron-nuage.xml43(td)
-msgid "(StrOpt) IP Address and Port of Nuage's VSD server"
+#: ./doc/common/tables/glance-common.xml99(td)
+msgid ""
+"(IntOpt) Set a system wide quota for every user. This value is the total "
+"number of bytes that a user can use across all storage systems. A value of 0"
+" means unlimited."
 msgstr ""
 
-#: ./doc/common/tables/neutron-nuage.xml46(td)
-msgid "serverauth = username:password"
+#: ./doc/common/tables/glance-common.xml102(td)
+msgid "workers = 1"
 msgstr ""
 
-#: ./doc/common/tables/neutron-nuage.xml47(td)
-msgid "(StrOpt) Username and password for authentication"
+#: ./doc/common/tables/glance-common.xml103(td)
+msgid ""
+"(IntOpt) The number of child process workers that will be created to service"
+" API requests."
 msgstr ""
 
-#: ./doc/common/tables/neutron-nuage.xml50(td)
-msgid "serverssl = False"
+#: ./doc/common/tables/glance-common.xml106(th)
+msgid "[image_format]"
 msgstr ""
 
-#: ./doc/common/tables/neutron-nuage.xml51(td)
-msgid "(BoolOpt) Boolean for SSL connection with VSD server"
+#: ./doc/common/tables/glance-common.xml109(td)
+msgid "container_formats = ami, ari, aki, bare, ovf, ova"
+msgstr ""
+
+#: ./doc/common/tables/glance-common.xml110(td)
+msgid "(ListOpt) Supported values for the 'container_format' image attribute"
+msgstr ""
+
+#: ./doc/common/tables/glance-common.xml113(td)
+msgid "disk_formats = ami, ari, aki, vhd, vmdk, raw, qcow2, vdi, iso"
+msgstr ""
+
+#: ./doc/common/tables/glance-common.xml114(td)
+msgid "(ListOpt) Supported values for the 'disk_format' image attribute"
+msgstr ""
+
+#: ./doc/common/tables/glance-common.xml117(th)
+msgid "[task]"
+msgstr ""
+
+#: ./doc/common/tables/glance-common.xml120(td)
+msgid "task_time_to_live = 48"
+msgstr ""
+
+#: ./doc/common/tables/glance-common.xml121(td)
+msgid ""
+"(IntOpt) Time in hours for which a task lives after, either succeeding or "
+"failing"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_vxlan.xml8(caption)
+msgid "Description of configuration options for ml2_vxlan"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_vxlan.xml19(th)
+msgid "[ml2_type_vxlan]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_vxlan.xml22(td)
+msgid "vni_ranges ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_vxlan.xml23(td)
+msgid ""
+"(ListOpt) Comma-separated list of &lt;vni_min&gt;:&lt;vni_max&gt; tuples "
+"enumerating ranges of VXLAN VNI IDs that are available for tenant network "
+"allocation"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_vxlan.xml26(td)
+msgid "vxlan_group = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2_vxlan.xml27(td)
+msgid ""
+"(StrOpt) Multicast group for VXLAN. If unset, disables VXLAN multicast mode."
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml7(literal)
+msgid "[dispersion]"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml7(literal)
+msgid "dispersion.conf-sample"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml18(td)
+msgid "auth_url = http://localhost:8080/auth/v1.0"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml18(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml27(td)
+msgid "Endpoint for auth server, such as keystone"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml21(td)
+msgid "auth_user = test:tester"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml21(td)
+#: ./doc/common/tables/swift-dispersion-dispersion.xml30(td)
+msgid "Default user for dispersion in this context"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml24(td)
+msgid "auth_key = testing"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml27(td)
+msgid "auth_url = http://localhost:5000/v2.0/"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml30(td)
+msgid "auth_user = tenant:user"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml33(td)
+msgid "auth_key = password"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml36(td)
+msgid "auth_version = 2.0"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml36(td)
+msgid "Indicates which version of auth"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml39(td)
+msgid "Indicates whether endpoint for auth is public or internal"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml42(td)
+msgid "keystone_api_insecure = no"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml48(td)
+msgid "dispersion_coverage = 1.0"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml51(td)
+msgid "retries = 5"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml54(td)
+#: ./doc/common/tables/swift-account-server-account-reaper.xml30(td)
+msgid "concurrency = 25"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml57(td)
+msgid "container_populate = yes"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml60(td)
+msgid "object_populate = yes"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml63(td)
+msgid "container_report = yes"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml66(td)
+msgid "object_report = yes"
+msgstr ""
+
+#: ./doc/common/tables/swift-dispersion-dispersion.xml69(td)
+msgid "dump_json = no"
+msgstr ""
+
+#: ./doc/common/tables/swift-account-server-DEFAULT.xml21(td)
+msgid "bind_port = 6002"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml7(literal)
+msgid "[filter:domain_remap]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml18(td)
+msgid "use = egg:swift#domain_remap"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml21(td)
+msgid "set log_name = domain_remap"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml40(td)
+msgid "path_root = v1"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml40(td)
+msgid "Root path"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml43(td)
+msgid "reseller_prefixes = AUTH"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml43(td)
+msgid "Reseller prefix"
+msgstr ""
+
+#: ./doc/common/tables/trove-nova.xml8(caption)
+msgid "Description of configuration options for nova"
+msgstr ""
+
+#: ./doc/common/tables/trove-nova.xml22(td)
+msgid "nova_proxy_admin_pass ="
+msgstr ""
+
+#: ./doc/common/tables/trove-nova.xml23(td)
+msgid "(StrOpt) Admin password used to connect to nova,"
+msgstr ""
+
+#: ./doc/common/tables/trove-nova.xml26(td)
+msgid "nova_proxy_admin_tenant_name ="
+msgstr ""
+
+#: ./doc/common/tables/trove-nova.xml27(td)
+msgid "(StrOpt) Admin tenant used to connect to nova."
+msgstr ""
+
+#: ./doc/common/tables/trove-nova.xml30(td)
+msgid "nova_proxy_admin_user ="
+msgstr ""
+
+#: ./doc/common/tables/trove-nova.xml31(td)
+msgid "(StrOpt) Admin username used to connect to nova."
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml8(caption)
+msgid "Description of configuration options for meta"
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml19(th)
+msgid "[META]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml22(td)
+msgid "default_flavor ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml23(td)
+msgid "(StrOpt) Default flavor to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml26(td)
+msgid "default_l3_flavor ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml27(td)
+msgid "(StrOpt) Default L3 flavor to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml30(td)
+msgid "extension_map ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml31(td)
+msgid "(StrOpt) A list of extensions, per plugin, to load."
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml34(td)
+msgid "l3_plugin_list ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml35(td)
+msgid "(StrOpt) List of L3 plugins to load"
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml38(td)
+msgid "plugin_list ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml39(td)
+msgid "(StrOpt) List of plugins to load"
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml42(td)
+msgid "rpc_flavor ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml43(td)
+msgid "(StrOpt) Flavor of which plugin handles RPC"
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml46(td)
+msgid "supported_extension_aliases ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-meta.xml47(td)
+msgid "(StrOpt) Supported extension aliases"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rabbitmq.xml35(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml55(td)
+msgid ""
+"(IntOpt) Maximum number of RabbitMQ connection retries. Default is 0 "
+"(infinite retry count)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rabbitmq.xml39(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml59(td)
+msgid "(StrOpt) The RabbitMQ password"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rabbitmq.xml47(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml67(td)
+msgid ""
+"(IntOpt) How long to backoff for between retries when connecting to RabbitMQ"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rabbitmq.xml51(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml71(td)
+msgid "(IntOpt) How frequently to retry connecting with RabbitMQ"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rabbitmq.xml55(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml75(td)
+msgid "(BoolOpt) Connect over SSL for RabbitMQ"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rabbitmq.xml59(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml79(td)
+msgid "(StrOpt) The RabbitMQ userid"
+msgstr ""
+
+#: ./doc/common/tables/neutron-rabbitmq.xml63(td)
+#: ./doc/common/tables/ceilometer-rabbitmq.xml83(td)
+msgid "(StrOpt) The RabbitMQ virtual host"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml22(td)
+msgid "keystone_ec2_cafile = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml23(td)
+msgid ""
+"(StrOpt) A PEM encoded certificate authority to use when verifying HTTPS "
+"connections. Defaults to the system CAs."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml26(td)
+msgid "keystone_ec2_certfile = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml27(td)
+msgid ""
+"(StrOpt) Client certificate key filename. Required if EC2 server requires "
+"client certificate."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml30(td)
+msgid "keystone_ec2_insecure = False"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml31(td)
+msgid "(BoolOpt) Disable SSL certificate verification."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml34(td)
+msgid "keystone_ec2_keyfile = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml35(td)
+msgid "(StrOpt) Required if EC2 server requires client certificate."
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml42(th)
+msgid "[ec2]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml45(td)
+msgid "driver = keystone.contrib.ec2.backends.kvs.Ec2"
+msgstr ""
+
+#: ./doc/common/tables/keystone-ec2.xml46(td)
+msgid "(StrOpt) Keystone EC2Credential backend driver."
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_keystone.xml8(caption)
+msgid "Description of configuration options for clients_keystone"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_keystone.xml19(th)
+msgid "[clients_keystone]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml22(td)
+msgid "allow_bulk = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml23(td)
+msgid "(BoolOpt) Allow the usage of the bulk API"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml26(td)
+msgid "allow_pagination = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml27(td)
+msgid "(BoolOpt) Allow the usage of the pagination"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml30(td)
+msgid "allow_sorting = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml31(td)
+msgid "(BoolOpt) Allow the usage of the sorting"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml34(td)
+msgid "api_extensions_path ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml35(td)
+msgid "(StrOpt) The path for API extensions"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml39(td)
+msgid "(StrOpt) The API paste config file to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml43(td)
+msgid "(IntOpt) Max header line to accommodate large tokens"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml47(td)
+msgid "(IntOpt) the maximum body size per each request(bytes)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml50(td)
+msgid "pagination_max_limit = -1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml51(td)
+msgid ""
+"(StrOpt) The maximum number of items returned in a single response, value "
+"was 'infinite' or negative integer means no limit"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml58(td)
+msgid "service_plugins ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml59(td)
+msgid "(ListOpt) The service plugins Neutron will use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml62(th)
+msgid "[service_providers]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml65(td)
+msgid "service_provider = []"
+msgstr ""
+
+#: ./doc/common/tables/neutron-api.xml66(td)
+msgid ""
+"(MultiStrOpt) Defines providers for advanced services using the format: "
+"&lt;service_type&gt;:&lt;name&gt;:&lt;driver&gt;[:default]"
+msgstr ""
+
+#: ./doc/common/tables/trove-logging.xml22(td)
+msgid "format_options = -m 5"
+msgstr ""
+
+#: ./doc/common/tables/trove-logging.xml70(td)
+msgid "network_label_regex = ^private$"
+msgstr ""
+
+#: ./doc/common/tables/glance-db.xml74(td)
+#: ./doc/common/tables/keystone-database.xml74(td)
+msgid "mysql_sql_mode = TRADITIONAL"
+msgstr ""
+
+#: ./doc/common/tables/glance-db.xml75(td)
+#: ./doc/common/tables/keystone-database.xml75(td)
+msgid ""
+"(StrOpt) The SQL mode to be used for MySQL sessions. This option, including "
+"the default, overrides any server-set SQL mode. To use whatever SQL mode is "
+"set by the server configuration, set this to no value. Example: "
+"mysql_sql_mode="
+msgstr ""
+
+#: ./doc/common/tables/glance-db.xml86(td)
+msgid "sqlite_db = glance.sqlite"
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml8(caption)
+msgid "Description of configuration options for kvs"
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml19(th)
+msgid "[kvs]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml22(td)
+msgid "backends ="
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml23(td)
+msgid ""
+"(ListOpt) Extra dogpile.cache backend modules to register with the "
+"dogpile.cache library."
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml26(td)
+msgid "config_prefix = keystone.kvs"
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml27(td)
+msgid ""
+"(StrOpt) Prefix for building the configuration dictionary for the KVS "
+"region. This should not need to be changed unless there is another "
+"dogpile.cache region with the same configuration name."
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml30(td)
+msgid "default_lock_timeout = 5"
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml31(td)
+msgid "(IntOpt) Default lock timeout for distributed locking."
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml34(td)
+msgid "enable_key_mangler = True"
+msgstr ""
+
+#: ./doc/common/tables/keystone-kvs.xml35(td)
+msgid ""
+"(BoolOpt) Toggle to disable using a key-mangling function to ensure fixed "
+"length keys. This is toggle-able for debugging purposes, it is highly "
+"recommended to always leave this set to True."
+msgstr ""
+
+#: ./doc/common/tables/nova-xvpnvncproxy.xml8(caption)
+msgid "Description of configuration options for xvpnvncproxy"
+msgstr ""
+
+#: ./doc/common/tables/nova-xvpnvncproxy.xml22(td)
+msgid "xvpvncproxy_base_url = http://127.0.0.1:6081/console"
+msgstr ""
+
+#: ./doc/common/tables/nova-xvpnvncproxy.xml23(td)
+msgid ""
+"(StrOpt) Location of nova xvp VNC console proxy, in the form "
+"\"http://127.0.0.1:6081/console\""
+msgstr ""
+
+#: ./doc/common/tables/nova-xvpnvncproxy.xml26(td)
+msgid "xvpvncproxy_host = 0.0.0.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-xvpnvncproxy.xml27(td)
+msgid "(StrOpt) Address that the XCP VNC proxy should bind to"
+msgstr ""
+
+#: ./doc/common/tables/nova-xvpnvncproxy.xml30(td)
+msgid "xvpvncproxy_port = 6081"
+msgstr ""
+
+#: ./doc/common/tables/nova-xvpnvncproxy.xml31(td)
+msgid "(IntOpt) Port that the XCP VNC proxy should bind to"
+msgstr ""
+
+#: ./doc/common/tables/glance-paste.xml8(caption)
+msgid "Description of configuration options for paste"
+msgstr ""
+
+#: ./doc/common/tables/glance-paste.xml22(td)
+msgid "config_file = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-paste.xml23(td)
+msgid "(StrOpt) Name of the paste configuration file."
+msgstr ""
+
+#: ./doc/common/tables/glance-paste.xml27(td)
+msgid ""
+"(StrOpt) Partial name of a pipeline in your paste configuration file with "
+"the service name removed. For example, if your paste section name is "
+"[pipeline:glance-api-keystone] use the value \"keystone\""
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml7(literal)
+msgid "[filter:list-endpoints]"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml18(td)
+msgid "use = egg:swift#list_endpoints"
+msgstr ""
+
+#: ./doc/common/tables/swift-proxy-server-filter-list-endpoints.xml21(td)
+msgid "list_endpoints_path = /endpoints/"
 msgstr ""
 
 #: ./doc/common/tables/swift-account-server-account-reaper.xml7(literal)
@@ -48884,599 +47873,1621 @@ msgstr ""
 msgid "reap_warn_after = 2592000"
 msgstr ""
 
-#: ./doc/common/tables/nova-quota.xml22(td)
-msgid "bandwidth_poll_interval = 600"
+#: ./doc/common/tables/nova-hyperv.xml8(caption)
+msgid "Description of configuration options for hyperv"
 msgstr ""
 
-#: ./doc/common/tables/nova-quota.xml23(td)
+#: ./doc/common/tables/nova-hyperv.xml22(td)
+msgid "dynamic_memory_ratio = 1.0"
+msgstr ""
+
+#: ./doc/common/tables/nova-hyperv.xml23(td)
 msgid ""
-"(IntOpt) Interval to pull network bandwidth usage info. Not supported on all"
-" hypervisors. Set to 0 to disable."
+"(FloatOpt) Enables dynamic memory allocation (ballooning) when set to a "
+"value greater than 1. The value expresses the ratio between the total RAM "
+"assigned to an instance and its startup RAM amount. For example a ratio of "
+"2.0 for an instance with 1024MB of RAM implies 512MB of RAM allocated at "
+"startup"
 msgstr ""
 
-#: ./doc/common/tables/nova-quota.xml26(td)
-msgid "enable_network_quota = False"
+#: ./doc/common/tables/nova-hyperv.xml26(td)
+msgid "enable_instance_metrics_collection = False"
 msgstr ""
 
-#: ./doc/common/tables/nova-quota.xml27(td)
-msgid "(BoolOpt) Enables or disables quota checking for tenant networks"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml30(td)
-msgid "quota_cores = 20"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml31(td)
-msgid "(IntOpt) Number of instance cores allowed per project"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml34(td)
-msgid "quota_driver = nova.quota.DbQuotaDriver"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml38(td)
-msgid "quota_fixed_ips = -1"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml39(td)
+#: ./doc/common/tables/nova-hyperv.xml27(td)
 msgid ""
-"(IntOpt) Number of fixed IPs allowed per project (this should be at least "
-"the number of instances allowed)"
+"(BoolOpt) Enables metrics collections for an instance by using Hyper-V's "
+"metric APIs. Collected data can by retrieved by other apps and services, "
+"e.g.: Ceilometer. Requires Hyper-V / Windows Server 2012 and above"
 msgstr ""
 
-#: ./doc/common/tables/nova-quota.xml42(td)
-msgid "quota_floating_ips = 10"
+#: ./doc/common/tables/nova-hyperv.xml34(td)
+msgid "instances_path_share ="
 msgstr ""
 
-#: ./doc/common/tables/nova-quota.xml43(td)
-msgid "(IntOpt) Number of floating IPs allowed per project"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml46(td)
-msgid "quota_injected_file_content_bytes = 10240"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml47(td)
-msgid "(IntOpt) Number of bytes allowed per injected file"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml50(td)
-msgid "quota_injected_file_path_bytes = 255"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml51(td)
-msgid "(IntOpt) Number of bytes allowed per injected file path"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml54(td)
-msgid "quota_injected_files = 5"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml55(td)
-msgid "(IntOpt) Number of injected files allowed"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml58(td)
-msgid "quota_instances = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml59(td)
-msgid "(IntOpt) Number of instances allowed per project"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml62(td)
-msgid "quota_key_pairs = 100"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml63(td)
-msgid "(IntOpt) Number of key pairs per user"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml66(td)
-msgid "quota_metadata_items = 128"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml67(td)
-msgid "(IntOpt) Number of metadata items allowed per instance"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml70(td)
-msgid "quota_ram = 51200"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml71(td)
-msgid "(IntOpt) Megabytes of instance RAM allowed per project"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml74(td)
-msgid "quota_security_group_rules = 20"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml75(td)
-msgid "(IntOpt) Number of security rules per security group"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml78(td)
-msgid "quota_security_groups = 10"
-msgstr ""
-
-#: ./doc/common/tables/nova-quota.xml79(td)
-msgid "(IntOpt) Number of security groups per project"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml8(caption)
-msgid "Description of configuration options for conductor"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml22(td)
-msgid "migrate_max_retries = -1"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml23(td)
+#: ./doc/common/tables/nova-hyperv.xml35(td)
 msgid ""
-"(IntOpt) Number of times to retry live-migration before failing. If == -1, "
-"try until out of hosts. If == 0, only try once, no retries."
+"(StrOpt) The name of a Windows share name mapped to the \"instances_path\" "
+"dir and used by the resize feature to copy files to the target host. If left"
+" blank, an administrative share will be used, looking for the same "
+"\"instances_path\" used locally"
 msgstr ""
 
-#: ./doc/common/tables/nova-conductor.xml26(th)
-msgid "[conductor]"
+#: ./doc/common/tables/nova-hyperv.xml38(td)
+msgid "limit_cpu_features = False"
 msgstr ""
 
-#: ./doc/common/tables/nova-conductor.xml29(td)
-msgid "manager = nova.conductor.manager.ConductorManager"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml30(td)
-msgid "(StrOpt) Full class name for the Manager for conductor"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml33(td)
-msgid "topic = conductor"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml34(td)
-msgid "(StrOpt) The topic on which conductor nodes listen"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml37(td)
-msgid "use_local = False"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml38(td)
-msgid "(BoolOpt) Perform nova-conductor operations locally"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml41(td)
-msgid "workers = None"
-msgstr ""
-
-#: ./doc/common/tables/nova-conductor.xml42(td)
+#: ./doc/common/tables/nova-hyperv.xml39(td)
 msgid ""
-"(IntOpt) Number of workers for OpenStack Conductor service. The default will"
-" be the number of CPUs available."
+"(BoolOpt) Required for live migration among hosts with different CPU "
+"features"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml22(td)
-msgid "compute_available_monitors = ['nova.compute.monitors.all_monitors']"
+#: ./doc/common/tables/nova-hyperv.xml42(td)
+msgid "mounted_disk_query_retry_count = 10"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml23(td)
+#: ./doc/common/tables/nova-hyperv.xml43(td)
 msgid ""
-"(MultiStrOpt) Monitor classes available to the compute which may be "
-"specified more than once."
+"(IntOpt) The number of times to retry checking for a disk mounted via iSCSI."
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml26(td)
-msgid "compute_driver = None"
+#: ./doc/common/tables/nova-hyperv.xml46(td)
+msgid "mounted_disk_query_retry_interval = 5"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml27(td)
+#: ./doc/common/tables/nova-hyperv.xml47(td)
+msgid "(IntOpt) Interval between checks for a mounted iSCSI disk, in seconds."
+msgstr ""
+
+#: ./doc/common/tables/nova-hyperv.xml50(td)
+msgid "qemu_img_cmd = qemu-img.exe"
+msgstr ""
+
+#: ./doc/common/tables/nova-hyperv.xml51(td)
 msgid ""
-"(StrOpt) Driver to use for controlling virtualization. Options include: "
-"libvirt.LibvirtDriver, xenapi.XenAPIDriver, fake.FakeDriver, "
-"baremetal.BareMetalDriver, vmwareapi.VMwareESXDriver, "
-"vmwareapi.VMwareVCDriver"
+"(StrOpt) Path of qemu-img command which is used to convert between different"
+" image types"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml30(td)
-msgid "compute_manager = nova.compute.manager.ComputeManager"
+#: ./doc/common/tables/nova-hyperv.xml54(td)
+msgid "vswitch_name = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml31(td)
-msgid "(StrOpt) Full class name for the Manager for compute"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml34(td)
-msgid "compute_monitors ="
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml35(td)
+#: ./doc/common/tables/nova-hyperv.xml55(td)
 msgid ""
-"(ListOpt) A list of monitors that can be used for getting compute metrics."
+"(StrOpt) External virtual switch Name, if not provided, the first external "
+"virtual switch is used"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml38(td)
-msgid "compute_stats_class = nova.compute.stats.Stats"
+#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml7(literal)
+msgid "[filter:container_sync]"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml39(td)
-msgid "(StrOpt) Class that will manage stats for the local compute host"
+#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml18(td)
+msgid "use = egg:swift#container_sync"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml42(td)
-msgid "console_host = oslo"
+#: ./doc/common/tables/swift-proxy-server-filter-container_sync.xml21(td)
+msgid "allow_full_urls = true"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml43(td)
+#: ./doc/common/tables/heat-clients_backends.xml8(caption)
+msgid "Description of configuration options for clients_backends"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_backends.xml22(td)
+msgid "cloud_backend = heat.engine.clients.OpenStackClients"
+msgstr ""
+
+#: ./doc/common/tables/heat-clients_backends.xml23(td)
+msgid "(StrOpt) Fully qualified class name to use as a client backend."
+msgstr ""
+
+#: ./doc/common/tables/glance-testing.xml22(td)
+msgid "pydev_worker_debug_host = None"
+msgstr ""
+
+#: ./doc/common/tables/glance-testing.xml23(td)
 msgid ""
-"(StrOpt) Console proxy host to use to connect to instances on this host."
+"(StrOpt) The hostname/IP of the pydev process listening for debug "
+"connections"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml46(td)
-msgid "console_manager = nova.console.manager.ConsoleProxyManager"
+#: ./doc/common/tables/glance-testing.xml26(td)
+msgid "pydev_worker_debug_port = 5678"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml47(td)
-msgid "(StrOpt) Full class name for the Manager for console proxy"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml50(td)
-msgid "default_flavor = m1.small"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml51(td)
+#: ./doc/common/tables/glance-testing.xml27(td)
 msgid ""
-"(StrOpt) Default flavor to use for the EC2 API only. The Nova API does not "
-"support a default flavor."
+"(IntOpt) The port on which a pydev process is listening for connections."
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml62(td)
-msgid "enable_instance_password = True"
+#: ./doc/common/tables/neutron-common.xml23(td)
+#: ./doc/common/tables/neutron-common.xml193(td)
+msgid "(StrOpt) Admin password"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml63(td)
+#: ./doc/common/tables/neutron-common.xml27(td)
+#: ./doc/common/tables/neutron-common.xml197(td)
+msgid "(StrOpt) Admin tenant name"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml31(td)
+msgid "(StrOpt) Admin username"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml34(td)
+msgid "agent_down_time = 75"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml35(td)
 msgid ""
-"(BoolOpt) Enables returning of the instance password by the relevant server "
-"API calls such as create, rebuild or rescue, If the hypervisor does not "
-"support password injection then the password returned will not be correct"
+"(IntOpt) Seconds to regard the agent is down; should be at least twice "
+"report_interval, to be sure the agent is down for good."
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml66(td)
-msgid "heal_instance_info_cache_interval = 60"
+#: ./doc/common/tables/neutron-common.xml42(td)
+msgid "api_workers = 0"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml67(td)
+#: ./doc/common/tables/neutron-common.xml43(td)
+msgid "(IntOpt) Number of separate worker processes for service"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml46(td)
+msgid "auth_ca_cert = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml47(td)
+msgid "(StrOpt) Certificate Authority public key (CA cert) file for ssl"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml50(td)
+msgid "auth_insecure = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml51(td)
+msgid "(BoolOpt) Turn off verification of the certificate for ssl"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml55(td)
+#: ./doc/common/tables/neutron-common.xml205(td)
+msgid "(StrOpt) Authentication region"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml59(td)
+#: ./doc/common/tables/neutron-common.xml209(td)
+msgid "(StrOpt) The type of authentication to use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml63(td)
+#: ./doc/common/tables/neutron-common.xml213(td)
+msgid "(StrOpt) Authentication URL"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml66(td)
+msgid "base_mac = fa:16:3e:00:00:00"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml67(td)
+msgid "(StrOpt) The base MAC address Neutron will use for VIFs"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml71(td)
+msgid "(StrOpt) The host IP to bind to"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml74(td)
+msgid "bind_port = 9696"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml75(td)
+msgid "(IntOpt) The port to bind to"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml78(td)
+msgid "ca_certs = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml79(td)
+msgid "(StrOpt) CA certificates"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml82(td)
+msgid "core_plugin = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml83(td)
+msgid "(StrOpt) The core plugin Neutron will use"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml86(td)
+msgid "ctl_cert = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml87(td)
+msgid "(StrOpt) controller certificate"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml90(td)
+msgid "ctl_privkey = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml91(td)
+msgid "(StrOpt) controller private key"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml94(td)
+msgid "dhcp_agent_notification = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml95(td)
+msgid "(BoolOpt) Allow sending resource operation notification to DHCP agent"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml98(td)
+msgid "dhcp_agents_per_network = 1"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml99(td)
+msgid "(IntOpt) Number of DHCP agents scheduled to host a network."
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml102(td)
+msgid "dhcp_confs = $state_path/dhcp"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml103(td)
+msgid "(StrOpt) Location to store DHCP server config files"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml106(td)
+msgid "dhcp_delete_namespaces = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml107(td)
+msgid "(BoolOpt) Delete namespace after removing a dhcp server."
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml110(td)
+msgid "dhcp_domain = openstacklocal"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml114(td)
+msgid "dhcp_driver = neutron.agent.linux.dhcp.Dnsmasq"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml115(td)
+msgid "(StrOpt) The driver used to manage the DHCP server."
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml118(td)
+msgid "dhcp_lease_duration = 86400"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml119(td)
+msgid "(IntOpt) DHCP lease duration"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml126(td)
+msgid "endpoint_type = adminURL"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml127(td)
 msgid ""
-"(IntOpt) Number of seconds between instance info_cache self healing updates"
+"(StrOpt) Network service endpoint type to pull from the keystone catalog"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml70(td)
-msgid "image_cache_manager_interval = 2400"
+#: ./doc/common/tables/neutron-common.xml130(td)
+msgid "force_gateway_on_subnet = False"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml71(td)
+#: ./doc/common/tables/neutron-common.xml131(td)
+msgid "(BoolOpt) Ensure that configured gateway is on subnet"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml134(td)
+msgid "interface_driver = None"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml135(td)
+msgid "(StrOpt) The driver used to manage the virtual interface."
+msgstr "(文字列オプション) 仮想インターフェースを管理するために使用するドライバー。"
+
+#: ./doc/common/tables/neutron-common.xml138(td)
+msgid "ip_lib_force_root = False"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml139(td)
+msgid "(BoolOpt) Force ip_lib calls to use the root helper"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml146(td)
+msgid "mac_generation_retries = 16"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml147(td)
+msgid "(IntOpt) How many times Neutron will retry MAC generation"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml150(td)
+msgid "max_dns_nameservers = 5"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml151(td)
+msgid "(IntOpt) Maximum number of DNS nameservers"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml154(td)
+msgid "max_fixed_ips_per_port = 5"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml155(td)
+msgid "(IntOpt) Maximum number of fixed ips per port"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml158(td)
+msgid "max_subnet_host_routes = 20"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml159(td)
+msgid "(IntOpt) Maximum number of host routes per subnet"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml162(td)
+msgid "periodic_fuzzy_delay = 5"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml166(td)
+msgid "periodic_interval = 40"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml167(td)
+msgid "(IntOpt) Seconds between running periodic tasks"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml171(td)
+msgid "(IntOpt) Interval between two metering reports"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml175(td)
+#: ./doc/common/tables/neutron-common.xml186(td)
+msgid "(StrOpt) Root helper application."
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml178(td)
+msgid "state_path = /var/lib/neutron"
+msgstr ""
+
+#: ./doc/common/tables/neutron-common.xml179(td)
 msgid ""
-"(IntOpt) Number of seconds to wait between runs of the image cache manager"
+"(StrOpt) Where to store Neutron state files. This directory must be writable"
+" by the agent."
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml74(td)
-msgid "image_cache_subdirectory_name = _base"
+#: ./doc/common/tables/neutron-common.xml189(th)
+msgid "[PROXY]"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml75(td)
+#: ./doc/common/tables/neutron-common.xml201(td)
+msgid "(StrOpt) Admin user"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml8(caption)
+msgid "Description of configuration options for hypervisor"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml22(td)
+msgid "default_ephemeral_format = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml23(td)
 msgid ""
-"(StrOpt) Where cached images are stored under $instances_path. This is NOT "
-"the full path - just a folder name. For per-compute-host cached images, set "
-"to _base_$my_ip"
+"(StrOpt) The default format an ephemeral_volume will be formatted with on "
+"creation."
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml78(td)
-msgid "image_handlers = download"
+#: ./doc/common/tables/nova-hypervisor.xml26(td)
+msgid "force_raw_images = True"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml79(td)
+#: ./doc/common/tables/nova-hypervisor.xml27(td)
+msgid "(BoolOpt) Force backing images to raw format"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml30(td)
+msgid "preallocate_images = none"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml31(td)
 msgid ""
-"(ListOpt) Specifies which image handler extension names to use for handling "
-"images. The first extension in the list which can handle the image with a "
-"suitable location will be used."
+"(StrOpt) VM image preallocation mode: \"none\" =&gt; no storage provisioning"
+" is done up front, \"space\" =&gt; storage is fully allocated at instance "
+"start"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml82(td)
-msgid "instance_build_timeout = 0"
+#: ./doc/common/tables/nova-hypervisor.xml34(td)
+msgid "rescue_timeout = 0"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml83(td)
+#: ./doc/common/tables/nova-hypervisor.xml35(td)
 msgid ""
-"(IntOpt) Amount of time in seconds an instance can be in BUILD before going "
-"into ERROR status.Set to 0 to disable."
+"(IntOpt) Automatically unrescue an instance after N seconds. Set to 0 to "
+"disable."
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml86(td)
-msgid "instance_delete_interval = 300"
+#: ./doc/common/tables/nova-hypervisor.xml38(td)
+msgid "timeout_nbd = 10"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml87(td)
-msgid "(IntOpt) Interval in seconds for retrying failed instance file deletes"
+#: ./doc/common/tables/nova-hypervisor.xml39(td)
+msgid "(IntOpt) Amount of time, in seconds, to wait for NBD device start up."
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml90(td)
-msgid "instance_usage_audit = False"
+#: ./doc/common/tables/nova-hypervisor.xml42(td)
+msgid "use_cow_images = True"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml91(td)
-msgid "(BoolOpt) Generate periodic compute.instance.exists notifications"
+#: ./doc/common/tables/nova-hypervisor.xml43(td)
+msgid "(BoolOpt) Whether to use cow images"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml94(td)
-msgid "instance_usage_audit_period = month"
+#: ./doc/common/tables/nova-hypervisor.xml46(td)
+msgid "vcpu_pin_set = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml95(td)
+#: ./doc/common/tables/nova-hypervisor.xml47(td)
 msgid ""
-"(StrOpt) Time period to generate instance usages for. Time period must be "
-"hour, day, month or year"
+"(StrOpt) Defines which pcpus that instance vcpus can use. For example, "
+"\"4-12,^8,15\""
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml98(td)
-msgid "instances_path = $state_path/instances"
+#: ./doc/common/tables/nova-hypervisor.xml50(td)
+msgid "virt_mkfs = []"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml99(td)
-msgid "(StrOpt) Where instances are stored on disk"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml102(td)
-msgid "maximum_instance_delete_attempts = 5"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml103(td)
-msgid "(IntOpt) The number of times to attempt to reap an instance's files."
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml106(td)
-msgid "reboot_timeout = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml107(td)
+#: ./doc/common/tables/nova-hypervisor.xml51(td)
 msgid ""
-"(IntOpt) Automatically hard reboot an instance if it has been stuck in a "
-"rebooting state longer than N seconds. Set to 0 to disable."
+"(MultiStrOpt) Name of the mkfs commands for ephemeral device. The format is "
+"&lt;os_type&gt;=&lt;mkfs command&gt;"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml110(td)
-msgid "reclaim_instance_interval = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml111(td)
-msgid "(IntOpt) Interval in seconds for reclaiming deleted instances"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml114(td)
-msgid "resize_confirm_window = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml115(td)
+#: ./doc/common/tables/nova-hypervisor.xml57(td)
 msgid ""
-"(IntOpt) Automatically confirm resizes after N seconds. Set to 0 to disable."
+"block_migration_flag = VIR_MIGRATE_UNDEFINE_SOURCE, VIR_MIGRATE_PEER2PEER, "
+"VIR_MIGRATE_NON_SHARED_INC"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml118(td)
-msgid "resume_guests_state_on_host_boot = False"
+#: ./doc/common/tables/nova-hypervisor.xml58(td)
+msgid "(StrOpt) Migration flags to be set for block migration"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml119(td)
+#: ./doc/common/tables/nova-hypervisor.xml61(td)
+msgid "disk_cachemodes ="
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml62(td)
 msgid ""
-"(BoolOpt) Whether to start guests that were running before the host rebooted"
+"(ListOpt) Specific cachemodes to use for different disk types e.g: "
+"file=directsync,block=none"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml122(td)
-msgid "running_deleted_instance_action = reap"
+#: ./doc/common/tables/nova-hypervisor.xml65(td)
+msgid "images_rbd_ceph_conf ="
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml123(td)
+#: ./doc/common/tables/nova-hypervisor.xml66(td)
+msgid "(StrOpt) Path to the ceph configuration file to use"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml69(td)
+msgid "images_rbd_pool = rbd"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml70(td)
+msgid "(StrOpt) The RADOS pool in which rbd volumes are stored"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml73(td)
+msgid "images_type = default"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml74(td)
 msgid ""
-"(StrOpt) Action to take if a running deleted instance is detected.Valid "
-"options are 'noop', 'log', 'shutdown', or 'reap'. Set to 'noop' to take no "
-"action."
+"(StrOpt) VM Images format. Acceptable values are: raw, qcow2, lvm, rbd, "
+"default. If default is specified, then use_cow_images flag is used instead "
+"of this one."
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml126(td)
-msgid "running_deleted_instance_poll_interval = 1800"
+#: ./doc/common/tables/nova-hypervisor.xml77(td)
+msgid "images_volume_group = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml127(td)
-msgid "(IntOpt) Number of seconds to wait between runs of the cleanup task."
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml130(td)
-msgid "running_deleted_instance_timeout = 0"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml131(td)
+#: ./doc/common/tables/nova-hypervisor.xml78(td)
 msgid ""
-"(IntOpt) Number of seconds after being deleted when a running instance "
-"should be considered eligible for cleanup."
+"(StrOpt) LVM Volume Group that is used for VM images, when you specify "
+"images_type=lvm."
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml134(td)
-msgid "shelved_offload_time = 0"
+#: ./doc/common/tables/nova-hypervisor.xml81(td)
+msgid "inject_key = False"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml135(td)
+#: ./doc/common/tables/nova-hypervisor.xml82(td)
+msgid "(BoolOpt) Inject the ssh public key at boot time"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml85(td)
+msgid "inject_partition = -2"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml86(td)
 msgid ""
-"(IntOpt) Time in seconds before a shelved instance is eligible for removing "
-"from a host. -1 never offload, 0 offload when shelved"
+"(IntOpt) The partition to inject to : -2 =&gt; disable, -1 =&gt; inspect "
+"(libguestfs only), 0 =&gt; not partitioned, &gt;0 =&gt; partition number"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml138(td)
-msgid "shelved_poll_interval = 3600"
+#: ./doc/common/tables/nova-hypervisor.xml89(td)
+msgid "inject_password = False"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml139(td)
-msgid "(IntOpt) Interval in seconds for polling shelved instances to offload"
+#: ./doc/common/tables/nova-hypervisor.xml90(td)
+msgid "(BoolOpt) Inject the admin password at boot time, without an agent."
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml142(td)
-msgid "sync_power_state_interval = 600"
+#: ./doc/common/tables/nova-hypervisor.xml93(td)
+msgid "iscsi_use_multipath = False"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml143(td)
+#: ./doc/common/tables/nova-hypervisor.xml94(td)
+msgid "(BoolOpt) Use multipath connection of the iSCSI volume"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml97(td)
+msgid "iser_use_multipath = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml98(td)
+msgid "(BoolOpt) Use multipath connection of the iSER volume"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml101(td)
+msgid "rescue_image_id = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml102(td)
+msgid "(StrOpt) Rescue ami image"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml105(td)
+msgid "rescue_kernel_id = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml106(td)
+msgid "(StrOpt) Rescue aki image"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml109(td)
+msgid "rescue_ramdisk_id = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml110(td)
+msgid "(StrOpt) Rescue ari image"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml113(td)
+msgid "snapshot_compression = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-hypervisor.xml114(td)
 msgid ""
-"(IntOpt) Interval to sync power states between the database and the "
-"hypervisor"
+"(BoolOpt) Compress snapshot images when possible. This currently applies "
+"exclusively to qcow2 images"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml146(td)
-msgid "vif_plugging_is_fatal = True"
+#: ./doc/common/tables/nova-hypervisor.xml117(td)
+msgid "snapshot_image_format = None"
 msgstr ""
 
-#: ./doc/common/tables/nova-compute.xml147(td)
-msgid "(BoolOpt) Fail instance boot if vif plugging fails"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml150(td)
-msgid "vif_plugging_timeout = 300"
-msgstr ""
-
-#: ./doc/common/tables/nova-compute.xml151(td)
+#: ./doc/common/tables/nova-hypervisor.xml118(td)
 msgid ""
-"(IntOpt) Number of seconds to wait for neutron vif plugging events to arrive"
-" before continuing or failing (see vif_plugging_is_fatal). If this is set to"
-" zero and vif_plugging_is_fatal is False, events should not be expected to "
-"arrive at all."
+"(StrOpt) Snapshot image format (valid options are : raw, qcow2, vmdk, vdi). "
+"Defaults to same as source image"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml7(literal)
-msgid "[filter:domain_remap]"
+#: ./doc/common/tables/nova-hypervisor.xml121(td)
+msgid "sparse_logical_volumes = False"
 msgstr ""
 
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml18(td)
-msgid "use = egg:swift#domain_remap"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml21(td)
-msgid "set log_name = domain_remap"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml40(td)
-msgid "path_root = v1"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml40(td)
-msgid "Root path"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml43(td)
-msgid "reseller_prefixes = AUTH"
-msgstr ""
-
-#: ./doc/common/tables/swift-proxy-server-filter-domain_remap.xml43(td)
-msgid "Reseller prefix"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_xen.xml8(caption)
-msgid "Description of configuration options for storage_xen"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_xen.xml22(td)
-msgid "xenapi_connection_password = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_xen.xml23(td)
-msgid "(StrOpt) Password for XenAPI connection"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_xen.xml26(td)
-msgid "xenapi_connection_url = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_xen.xml27(td)
-msgid "(StrOpt) URL for XenAPI connection"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_xen.xml31(td)
-msgid "(StrOpt) Username for XenAPI connection"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_xen.xml34(td)
-msgid "xenapi_nfs_server = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_xen.xml35(td)
-msgid "(StrOpt) NFS server to be used by XenAPINFSDriver"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_xen.xml38(td)
-msgid "xenapi_nfs_serverpath = None"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_xen.xml39(td)
-msgid "(StrOpt) Path of exported NFS, used by XenAPINFSDriver"
-msgstr ""
-
-#: ./doc/common/tables/cinder-storage_xen.xml42(td)
-msgid "xenapi_sr_base_path = /var/run/sr-mount"
-msgstr ""
-
-#: ./doc/common/tables/keystone-credential.xml8(caption)
-msgid "Description of configuration options for credential"
-msgstr ""
-
-#: ./doc/common/tables/keystone-credential.xml19(th)
-msgid "[credential]"
-msgstr ""
-
-#: ./doc/common/tables/keystone-credential.xml22(td)
-msgid "driver = keystone.credential.backends.sql.Credential"
-msgstr ""
-
-#: ./doc/common/tables/trove-amqp.xml30(td)
-msgid "conductor_queue = trove-conductor"
-msgstr ""
-
-#: ./doc/common/tables/trove-amqp.xml62(td)
+#: ./doc/common/tables/nova-hypervisor.xml122(td)
 msgid ""
-"notification_service_id = {'couchbase': 'fa62fe68-74d9-4779-a24e-"
-"36f19602c415', 'mongodb': 'c8c907af-7375-456f-b929-b637ff9209ee', "
-"'cassandra': '459a230d-4e97-4344-9067-2a54a310b0ed', 'redis': 'b216ffc5-1947"
-"-456c-a4cf-70f94c05f7d0', 'mysql': '2f3ff068-2bfb-4f70-9a9d-a6bb65bc084b'}"
+"(BoolOpt) Create sparse logical volumes (with virtualsize) if this flag is "
+"set to True."
 msgstr ""
 
-#: ./doc/common/tables/trove-amqp.xml63(td)
-msgid "(DictOpt) Unique ID to tag notification events."
+#: ./doc/common/tables/nova-hypervisor.xml125(td)
+msgid "use_usb_tablet = True"
 msgstr ""
 
-#: ./doc/common/tables/nova-xvpnvncproxy.xml8(caption)
-msgid "Description of configuration options for xvpnvncproxy"
+#: ./doc/common/tables/nova-hypervisor.xml126(td)
+msgid "(BoolOpt) Sync virtual and real mouse cursors in Windows VMs"
 msgstr ""
 
-#: ./doc/common/tables/nova-xvpnvncproxy.xml22(td)
-msgid "xvpvncproxy_base_url = http://127.0.0.1:6081/console"
+#: ./doc/common/tables/nova-hypervisor.xml129(td)
+msgid "use_virtio_for_bridges = True"
 msgstr ""
 
-#: ./doc/common/tables/nova-xvpnvncproxy.xml23(td)
+#: ./doc/common/tables/nova-hypervisor.xml130(td)
+msgid "(BoolOpt) Use virtio for bridge interfaces with KVM/QEMU"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml7(literal)
+msgid "[realm1]"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml18(td)
+msgid "key = realm1key"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml21(td)
+msgid "key2 = realm1key2"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml24(td)
+msgid "cluster_name1 = https://host1/v1/"
+msgstr ""
+
+#: ./doc/common/tables/swift-container-sync-realms-realm1.xml27(td)
+msgid "cluster_name2 = https://host2/v1/"
+msgstr ""
+
+#: ./doc/common/tables/nova-wsgi.xml23(td)
+msgid "(StrOpt) File name for the paste.deploy config for nova-api"
+msgstr ""
+
+#: ./doc/common/tables/nova-wsgi.xml31(td)
+msgid "(StrOpt) SSL certificate of API server"
+msgstr ""
+
+#: ./doc/common/tables/nova-wsgi.xml35(td)
+msgid "(StrOpt) SSL private key of API server"
+msgstr ""
+
+#: ./doc/common/tables/nova-wsgi.xml42(td)
+msgid "wsgi_default_pool_size = 1000"
+msgstr ""
+
+#: ./doc/common/tables/nova-wsgi.xml43(td)
+msgid "(IntOpt) Size of the pool of greenthreads used by wsgi"
+msgstr ""
+
+#: ./doc/common/tables/nova-wsgi.xml46(td)
 msgid ""
-"(StrOpt) Location of nova xvp VNC console proxy, in the form "
-"\"http://127.0.0.1:6081/console\""
+"wsgi_log_format = %(client_ip)s \"%(request_line)s\" status: %(status_code)s"
+" len: %(body_length)s time: %(wall_seconds).7f"
 msgstr ""
 
-#: ./doc/common/tables/nova-xvpnvncproxy.xml26(td)
-msgid "xvpvncproxy_host = 0.0.0.0"
+#: ./doc/common/tables/nova-wsgi.xml47(td)
+msgid ""
+"(StrOpt) A python format string that is used as the template to generate log"
+" lines. The following values can be formatted into it: client_ip, date_time,"
+" request_line, status_code, body_length, wall_seconds."
 msgstr ""
 
-#: ./doc/common/tables/nova-xvpnvncproxy.xml27(td)
-msgid "(StrOpt) Address that the XCP VNC proxy should bind to"
+#: ./doc/common/tables/keystone-cache.xml8(caption)
+msgid "Description of configuration options for cache"
 msgstr ""
 
-#: ./doc/common/tables/nova-xvpnvncproxy.xml30(td)
-msgid "xvpvncproxy_port = 6081"
+#: ./doc/common/tables/keystone-cache.xml19(th)
+msgid "[cache]"
 msgstr ""
 
-#: ./doc/common/tables/nova-xvpnvncproxy.xml31(td)
-msgid "(IntOpt) Port that the XCP VNC proxy should bind to"
+#: ./doc/common/tables/keystone-cache.xml22(td)
+msgid "backend = keystone.common.cache.noop"
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml23(td)
+msgid ""
+"(StrOpt) Dogpile.cache backend module. It is recommended that Memcache "
+"(dogpile.cache.memcache) or Redis (dogpile.cache.redis) be used in "
+"production deployments. Small workloads (single process) like devstack can "
+"use the dogpile.cache.memory backend."
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml26(td)
+msgid "backend_argument = []"
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml27(td)
+msgid ""
+"(MultiStrOpt) Arguments supplied to the backend module. Specify this option "
+"once per argument to be passed to the dogpile.cache backend. Example format:"
+" \"&lt;argname&gt;:&lt;value&gt;\"."
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml30(td)
+msgid "config_prefix = cache.keystone"
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml31(td)
+msgid ""
+"(StrOpt) Prefix for building the configuration dictionary for the cache "
+"region. This should not need to be changed unless there is another "
+"dogpile.cache region with the same configuration name."
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml34(td)
+msgid "debug_cache_backend = False"
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml35(td)
+msgid ""
+"(BoolOpt) Extra debugging from the cache backend (cache keys, "
+"get/set/delete/etc calls) This is only really useful if you need to see the "
+"specific cache-backend get/set/delete calls with the keys/values. Typically "
+"this should be left set to False."
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml39(td)
+msgid ""
+"(BoolOpt) Global toggle for all caching using the should_cache_fn mechanism."
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml42(td)
+msgid "expiration_time = 600"
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml43(td)
+msgid ""
+"(IntOpt) Default TTL, in seconds, for any cached item in the dogpile.cache "
+"region. This applies to any cached method that doesn't have an explicit "
+"cache expiration time defined for it."
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml46(td)
+msgid "proxies ="
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml47(td)
+msgid ""
+"(ListOpt) Proxy Classes to import that will affect the way the dogpile.cache"
+" backend functions. See the dogpile.cache documentation on changing-backend-"
+"behavior. Comma delimited list e.g. my.dogpile.proxy.Class, "
+"my.dogpile.proxyClass2."
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml50(td)
+msgid "use_key_mangler = True"
+msgstr ""
+
+#: ./doc/common/tables/keystone-cache.xml51(td)
+msgid ""
+"(BoolOpt) Use a key-mangling function (sha1) to ensure fixed length cache-"
+"keys. This is toggle-able for debugging purposes, it is highly recommended "
+"to always leave this set to True."
+msgstr ""
+
+#: ./doc/common/tables/nova-configdrive.xml8(caption)
+msgid "Description of configuration options for configdrive"
+msgstr "コンフィグドライブの設定オプションの説明"
+
+#: ./doc/common/tables/nova-configdrive.xml22(td)
+msgid "config_drive_format = iso9660"
+msgstr "config_drive_format = iso9660"
+
+#: ./doc/common/tables/nova-configdrive.xml23(td)
+msgid "(StrOpt) Config drive format. One of iso9660 (default) or vfat"
+msgstr "(文字列オプション) コンフィグドライブの形式。iso9660 (デフォルト) または vfat のいずれか"
+
+#: ./doc/common/tables/nova-configdrive.xml26(td)
+msgid ""
+"config_drive_skip_versions = 1.0 2007-01-19 2007-03-01 2007-08-29 2007-10-10"
+" 2007-12-15 2008-02-01 2008-09-01"
+msgstr "config_drive_skip_versions = 1.0 2007-01-19 2007-03-01 2007-08-29 2007-10-10 2007-12-15 2008-02-01 2008-09-01"
+
+#: ./doc/common/tables/nova-configdrive.xml27(td)
+msgid ""
+"(StrOpt) List of metadata versions to skip placing into the config drive"
+msgstr "(文字列オプション) コンフィグドライブへの設定を省略するメタデータバージョンの一覧"
+
+#: ./doc/common/tables/nova-configdrive.xml30(td)
+msgid "config_drive_tempdir = None"
+msgstr "config_drive_tempdir = None"
+
+#: ./doc/common/tables/nova-configdrive.xml31(td)
+msgid ""
+"(StrOpt) Where to put temporary files associated with config drive creation"
+msgstr "(文字列オプション) コンフィグドライブの作成に関連する一時ファイルを保存する場所"
+
+#: ./doc/common/tables/nova-configdrive.xml34(td)
+msgid "force_config_drive = None"
+msgstr "force_config_drive = None"
+
+#: ./doc/common/tables/nova-configdrive.xml35(td)
+msgid ""
+"(StrOpt) Set to force injection to take place on a config drive (if set, "
+"valid options are: always)"
+msgstr "(文字列オプション) コンフィグドライブで行われる注入を強制するように設定します (設定されている場合は、有効なオプションは always となります)。"
+
+#: ./doc/common/tables/nova-configdrive.xml38(td)
+msgid "mkisofs_cmd = genisoimage"
+msgstr "mkisofs_cmd = genisoimage"
+
+#: ./doc/common/tables/nova-configdrive.xml45(td)
+msgid "config_drive_cdrom = False"
+msgstr "config_drive_cdrom = False"
+
+#: ./doc/common/tables/nova-configdrive.xml46(td)
+msgid ""
+"(BoolOpt) Attaches the Config Drive image as a cdrom drive instead of a disk"
+" drive"
+msgstr "(論理値オプション) ディスクドライブではなく、CD ドライブとしてコンフィグドライブイメージを接続します。"
+
+#: ./doc/common/tables/nova-configdrive.xml49(td)
+msgid "config_drive_inject_password = False"
+msgstr "config_drive_inject_password = False"
+
+#: ./doc/common/tables/nova-configdrive.xml50(td)
+msgid "(BoolOpt) Sets the admin password in the config drive image"
+msgstr "(論理値オプション) コンフィグドライブのイメージに管理者パスワードを設定します。"
+
+#: ./doc/common/tables/keystone-token.xml8(caption)
+msgid "Description of configuration options for token"
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml19(th)
+msgid "[token]"
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml22(td)
+msgid "bind ="
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml23(td)
+msgid ""
+"(ListOpt) External auth mechanisms that should add bind information to token"
+" e.g. kerberos, x509."
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml27(td)
+msgid ""
+"(IntOpt) Time to cache tokens (in seconds). This has no effect unless global"
+" and token caching are enabled."
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml31(td)
+msgid ""
+"(BoolOpt) Toggle for token system cacheing. This has no effect unless global"
+" caching is enabled."
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml34(td)
+msgid "driver = keystone.token.backends.sql.Token"
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml35(td)
+msgid "(StrOpt) Keystone Token persistence backend driver."
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml39(td)
+msgid ""
+"(StrOpt) Enforcement policy on tokens presented to keystone with bind "
+"information. One of disabled, permissive, strict, required or a specifically"
+" required bind mode e.g. kerberos or x509 to require binding to that "
+"authentication."
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml42(td)
+msgid "expiration = 3600"
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml43(td)
+msgid "(IntOpt) Amount of time a token should remain valid (in seconds)."
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml46(td)
+msgid "provider = None"
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml47(td)
+msgid ""
+"(StrOpt) Controls the token construction, validation, and revocation "
+"operations. Core providers are "
+"\"keystone.token.providers.[pki|uuid].Provider\"."
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml50(td)
+msgid "revocation_cache_time = 3600"
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml51(td)
+msgid ""
+"(IntOpt) Time to cache the revocation list and the revocation events if "
+"revoke extension is enabled (in seconds). This has no effect unless global "
+"and token caching are enabled."
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml54(td)
+msgid "revoke_by_id = True"
+msgstr ""
+
+#: ./doc/common/tables/keystone-token.xml55(td)
+msgid ""
+"(BoolOpt) Revoke token by token identifier. Setting revoke_by_id to True "
+"enables various forms of enumerating tokens, e.g. `list tokens for user`. "
+"These enumerations are processed to determine the list of tokens to revoke. "
+"Only disable if you are switching to using the Revoke extension with a "
+"backend other than KVS, which stores events in memory."
+msgstr ""
+
+#: ./doc/common/tables/heat-database.xml23(td)
+msgid "(StrOpt) The backend to use for db."
+msgstr ""
+
+#: ./doc/common/tables/heat-database.xml26(td)
+msgid "sqlite_db = heat.sqlite"
+msgstr ""
+
+#: ./doc/common/tables/heat-database.xml41(td)
+msgid ""
+"connection = sqlite:////usr/lib/python/site-"
+"packages/heat/openstack/common/db/$sqlite_db"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2.xml8(caption)
+msgid "Description of configuration options for ml2"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2.xml19(th)
+msgid "[ml2]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2.xml22(td)
+msgid "mechanism_drivers ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2.xml23(td)
+msgid ""
+"(ListOpt) An ordered list of networking mechanism driver entrypoints to be "
+"loaded from the neutron.ml2.mechanism_drivers namespace."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2.xml26(td)
+msgid "tenant_network_types = local"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2.xml27(td)
+msgid ""
+"(ListOpt) Ordered list of network_types to allocate as tenant networks."
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2.xml30(td)
+msgid "type_drivers = local, flat, vlan, gre, vxlan"
+msgstr ""
+
+#: ./doc/common/tables/neutron-ml2.xml31(td)
+msgid ""
+"(ListOpt) List of network type driver entrypoints to be loaded from the "
+"neutron.ml2.type_drivers namespace."
+msgstr ""
+
+#: ./doc/common/tables/neutron-db.xml22(td)
+msgid "sqlite_db ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-db.xml37(td)
+msgid "connection = sqlite://"
+msgstr ""
+
+#: ./doc/common/tables/neutron-db.xml69(td)
+msgid "max_overflow = 20"
+msgstr ""
+
+#: ./doc/common/tables/neutron-db.xml73(td)
+msgid "max_pool_size = 10"
+msgstr ""
+
+#: ./doc/common/tables/neutron-db.xml85(td)
+msgid "pool_timeout = 10"
+msgstr ""
+
+#: ./doc/common/tables/keystone-database.xml86(td)
+msgid "sqlite_db = keystone.sqlite"
+msgstr ""
+
+#: ./doc/common/tables/keystone-memcache.xml8(caption)
+msgid "Description of configuration options for memcache"
+msgstr ""
+
+#: ./doc/common/tables/keystone-memcache.xml22(td)
+msgid "max_compare_and_set_retry = 16"
+msgstr ""
+
+#: ./doc/common/tables/keystone-memcache.xml23(td)
+msgid ""
+"(IntOpt) Number of compare-and-set attempts to make when using compare-and-"
+"set in the token memcache back end."
+msgstr ""
+
+#: ./doc/common/tables/keystone-memcache.xml26(td)
+msgid "servers = localhost:11211"
+msgstr ""
+
+#: ./doc/common/tables/keystone-memcache.xml27(td)
+msgid "(ListOpt) Memcache servers in the format of \"host:port\""
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml42(td)
+msgid "pydev_debug = disabled"
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml43(td)
+msgid ""
+"(StrOpt) Enable or disable pydev remote debugging. If value is 'auto' tries "
+"to connect to remote debugger server, but in case of error continues running"
+" with debugging disabled."
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml46(td)
+#: ./doc/common/tables/keystone-debug.xml42(td)
+msgid "pydev_debug_host = None"
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml47(td)
+msgid "(StrOpt) Pydev debug server host (localhost by default)."
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml50(td)
+#: ./doc/common/tables/keystone-debug.xml46(td)
+msgid "pydev_debug_port = None"
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml51(td)
+msgid "(IntOpt) Pydev debug server port (5678 by default)."
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml54(td)
+msgid "remote_cinder_client = trove.common.remote.cinder_client"
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml58(td)
+msgid "remote_dns_client = trove.common.remote.dns_client"
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml62(td)
+msgid "remote_guest_client = trove.common.remote.guest_client"
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml66(td)
+msgid "remote_heat_client = trove.common.remote.heat_client"
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml70(td)
+msgid "remote_nova_client = trove.common.remote.nova_client"
+msgstr ""
+
+#: ./doc/common/tables/trove-debug.xml74(td)
+msgid "remote_swift_client = trove.common.remote.swift_client"
+msgstr ""
+
+#: ./doc/common/tables/trove-swift.xml22(td)
+msgid "swift_url = http://localhost:8080/v1/AUTH_"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml8(caption)
+msgid "Description of configuration options for tilera"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml22(td)
+msgid "tile_pdu_ip = 10.0.100.1"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml23(td)
+msgid "(StrOpt) IP address of tilera pdu"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml26(td)
+msgid "tile_pdu_mgr = /tftpboot/pdu_mgr"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml27(td)
+msgid "(StrOpt) Management script for tilera pdu"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml30(td)
+msgid "tile_pdu_off = 2"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml31(td)
+msgid "(IntOpt) Power status of tilera PDU is OFF"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml34(td)
+msgid "tile_pdu_on = 1"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml35(td)
+msgid "(IntOpt) Power status of tilera PDU is ON"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml38(td)
+msgid "tile_pdu_status = 9"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml39(td)
+msgid "(IntOpt) Power status of tilera PDU"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml42(td)
+msgid "tile_power_wait = 9"
+msgstr ""
+
+#: ./doc/common/tables/nova-tilera.xml43(td)
+msgid ""
+"(IntOpt) Wait time in seconds until check the result after tilera power "
+"operations"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml8(caption)
+msgid "Description of configuration options for libvirt"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml22(td)
+msgid "remove_unused_base_images = True"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml23(td)
+msgid "(BoolOpt) Should unused base images be removed?"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml26(td)
+msgid "remove_unused_original_minimum_age_seconds = 86400"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml27(td)
+msgid ""
+"(IntOpt) Unused unresized base images younger than this will not be removed"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml33(td)
+msgid "checksum_base_images = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml34(td)
+msgid "(BoolOpt) Write a checksum for files in _base to disk"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml37(td)
+msgid "checksum_interval_seconds = 3600"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml38(td)
+msgid "(IntOpt) How frequently to checksum base images"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml41(td)
+msgid "connection_uri ="
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml42(td)
+msgid ""
+"(StrOpt) Override the default libvirt URI (which is dependent on virt_type)"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml45(td)
+msgid "cpu_mode = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml46(td)
+msgid ""
+"(StrOpt) Set to \"host-model\" to clone the host CPU feature flags; to "
+"\"host-passthrough\" to use the host CPU model exactly; to \"custom\" to use"
+" a named CPU model; to \"none\" to not set any CPU model. If "
+"virt_type=\"kvm|qemu\", it will default to \"host-model\", otherwise it will"
+" default to \"none\""
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml49(td)
+msgid "cpu_model = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml50(td)
+msgid ""
+"(StrOpt) Set to a named libvirt CPU model (see names listed in "
+"/usr/share/libvirt/cpu_map.xml). Only has effect if cpu_mode=\"custom\" and "
+"virt_type=\"kvm|qemu\""
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml53(td)
+msgid "disk_prefix = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml54(td)
+msgid ""
+"(StrOpt) Override the default disk prefix for the devices attached to a "
+"server, which is dependent on virt_type. (valid options are: sd, xvd, uvd, "
+"vd)"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml57(td)
+msgid ""
+"image_info_filename_pattern = "
+"$instances_path/$image_cache_subdirectory_name/%(image)s.info"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml58(td)
+msgid ""
+"(StrOpt) Allows image information files to be stored in non-standard "
+"locations"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml61(td)
+msgid "remove_unused_kernels = False"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml62(td)
+msgid ""
+"(BoolOpt) Should unused kernel images be removed? This is only safe to "
+"enable if all compute nodes have been updated to support this option. This "
+"will be enabled by default in future."
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml65(td)
+msgid "remove_unused_resized_minimum_age_seconds = 3600"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml66(td)
+msgid ""
+"(IntOpt) Unused resized base images younger than this will not be removed"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml69(td)
+msgid "rng_dev_path = None"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml70(td)
+msgid ""
+"(StrOpt) A path to a device that will be used as source of entropy on the "
+"host. Permitted options are: /dev/random or /dev/hwrng"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml73(td)
+msgid "snapshots_directory = $instances_path/snapshots"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml74(td)
+msgid ""
+"(StrOpt) Location where libvirt driver will store snapshots before uploading"
+" them to image service"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml77(td)
+msgid "vif_driver = nova.virt.libvirt.vif.LibvirtGenericVIFDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml78(td)
+msgid ""
+"(StrOpt) DEPRECATED. The libvirt VIF driver to configure the VIFs.This "
+"option is deprecated and will be removed in the Juno release."
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml81(td)
+msgid "virt_type = kvm"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml82(td)
+msgid ""
+"(StrOpt) Libvirt domain type (valid options are: kvm, lxc, qemu, uml, xen)"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml86(td)
+msgid ""
+"(StrOpt) Method used to wipe old volumes (valid options are: none, zero, "
+"shred)"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml93(td)
+msgid ""
+"volume_drivers = iscsi=nova.virt.libvirt.volume.LibvirtISCSIVolumeDriver, "
+"iser=nova.virt.libvirt.volume.LibvirtISERVolumeDriver, "
+"local=nova.virt.libvirt.volume.LibvirtVolumeDriver, "
+"fake=nova.virt.libvirt.volume.LibvirtFakeVolumeDriver, "
+"rbd=nova.virt.libvirt.volume.LibvirtNetVolumeDriver, "
+"sheepdog=nova.virt.libvirt.volume.LibvirtNetVolumeDriver, "
+"nfs=nova.virt.libvirt.volume.LibvirtNFSVolumeDriver, "
+"aoe=nova.virt.libvirt.volume.LibvirtAOEVolumeDriver, "
+"glusterfs=nova.virt.libvirt.volume.LibvirtGlusterfsVolumeDriver, "
+"fibre_channel=nova.virt.libvirt.volume.LibvirtFibreChannelVolumeDriver, "
+"scality=nova.virt.libvirt.volume.LibvirtScalityVolumeDriver"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml94(td)
+msgid "(ListOpt) Libvirt handlers for remote volumes."
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml97(td)
+msgid "wait_soft_reboot_seconds = 120"
+msgstr ""
+
+#: ./doc/common/tables/nova-libvirt.xml98(td)
+msgid ""
+"(IntOpt) Number of seconds to wait for instance to shut down after soft "
+"reboot request is made. We fall back to hard reboot if instance does not "
+"shutdown within this window."
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml8(caption)
+msgid "Description of configuration options for mlnx"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml22(td)
+msgid "backoff_rate = 2"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml23(td)
+msgid ""
+"(IntOpt) backoff rate multiplier for waiting period between retries for "
+"request to daemon, i.e. value of 2 will double the request timeout each "
+"retry"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml26(td)
+msgid "daemon_endpoint = tcp://127.0.0.1:60001"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml27(td)
+msgid "(StrOpt) eswitch daemon end point"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml34(td)
+msgid "request_timeout = 3000"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml35(td)
+msgid ""
+"(IntOpt) The number of milliseconds the agent will wait for response on "
+"request to daemon."
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml38(th)
+msgid "[MLNX]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml41(td)
+msgid "network_vlan_ranges = default:1:1000"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml45(td)
+msgid "physical_network_type = eth"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml46(td)
+msgid "(StrOpt) Physical network type for provider network (eth or ib)"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml49(td)
+msgid "physical_network_type_mappings ="
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml50(td)
+msgid ""
+"(ListOpt) List of &lt;physical_network&gt;:&lt;physical_network_type&gt; "
+"with physical_network_type is either eth or ib"
+msgstr ""
+
+#: ./doc/common/tables/neutron-mlnx.xml53(td)
+msgid "tenant_network_type = vlan"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_manager.xml8(caption)
+msgid "Description of configuration options for zoning_manager"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_manager.xml22(td)
+msgid ""
+"brcd_sb_connector = "
+"cinder.zonemanager.drivers.brocade.brcd_fc_zone_client_cli.BrcdFCZoneClientCLI"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_manager.xml23(td)
+msgid "(StrOpt) Southbound connector for zoning operation"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_manager.xml26(td)
+msgid ""
+"fc_san_lookup_service = "
+"cinder.zonemanager.drivers.brocade.brcd_fc_san_lookup_service.BrcdFCSanLookupService"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_manager.xml27(td)
+msgid "(StrOpt) FC San Lookup Service"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_manager.xml30(td)
+msgid ""
+"zone_driver = "
+"cinder.zonemanager.drivers.brocade.brcd_fc_zone_driver.BrcdFCZoneDriver"
+msgstr ""
+
+#: ./doc/common/tables/cinder-zoning_manager.xml31(td)
+msgid "(StrOpt) FC Zone Driver responsible for zone management"
+msgstr ""
+
+#: ./doc/common/tables/glance-ssl.xml27(td)
+msgid "(StrOpt) Certificate file to use when starting API server securely."
+msgstr ""
+
+#: ./doc/common/tables/glance-ssl.xml31(td)
+msgid "(StrOpt) Private key file to use when starting API server securely."
+msgstr ""
+
+#: ./doc/common/tables/neutron-securitygroups.xml8(caption)
+msgid "Description of configuration options for securitygroups"
+msgstr ""
+
+#: ./doc/common/tables/neutron-securitygroups.xml19(th)
+msgid "[SECURITYGROUP]"
+msgstr ""
+
+#: ./doc/common/tables/neutron-securitygroups.xml22(td)
+msgid "enable_security_group = True"
+msgstr ""
+
+#: ./doc/common/tables/neutron-securitygroups.xml23(td)
+msgid ""
+"(BoolOpt) Controls whether the neutron security group API is enabled in the "
+"server. It should be false when using no security groups or using the nova "
+"security group API."
+msgstr ""
+
+#: ./doc/common/tables/neutron-securitygroups.xml27(td)
+msgid "(StrOpt) Driver for security groups firewall in the L2 agent"
+msgstr ""
+
+#: ./doc/common/tables/keystone-debug.xml43(td)
+msgid "(StrOpt) Host to connect to for remote debugger."
+msgstr ""
+
+#: ./doc/common/tables/keystone-debug.xml47(td)
+msgid "(IntOpt) Port to connect to for remote debugger."
+msgstr ""
+
+#: ./doc/common/tables/keystone-debug.xml50(td)
+msgid "standard_threads = False"
+msgstr ""
+
+#: ./doc/common/tables/keystone-debug.xml51(td)
+msgid "(BoolOpt) Do not monkey-patch threading system modules."
+msgstr ""
+
+#: ./doc/common/tables/cinder-rootwrap.xml22(td)
+msgid "filters_path = /etc/cinder/rootwrap.d,/usr/share/cinder/rootwrap"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml8(caption)
+msgid "Description of configuration options for nexenta_iscsi"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml22(td)
+msgid "nexenta_blocksize ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml23(td)
+msgid "(StrOpt) block size for volumes (blank=default,8KB)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml26(td)
+msgid "nexenta_host ="
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml27(td)
+msgid "(StrOpt) IP address of Nexenta SA"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml30(td)
+msgid "nexenta_iscsi_target_portal_port = 3260"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml31(td)
+msgid "(IntOpt) Nexenta target portal port"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml34(td)
+msgid "nexenta_password = nexenta"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml35(td)
+msgid "(StrOpt) Password to connect to Nexenta SA"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml38(td)
+msgid "nexenta_rest_port = 2000"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml39(td)
+msgid "(IntOpt) HTTP port to connect to Nexenta REST API server"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml42(td)
+msgid "nexenta_rest_protocol = auto"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml43(td)
+msgid "(StrOpt) Use http or https for REST connection (default auto)"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml46(td)
+msgid "nexenta_rrmgr_compression = 0"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml47(td)
+msgid ""
+"(IntOpt) Enable stream compression, level 1..9. 1 - gives best speed; 9 - "
+"gives best compression."
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml50(td)
+msgid "nexenta_rrmgr_connections = 2"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml51(td)
+msgid "(IntOpt) Number of TCP connections."
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml54(td)
+msgid "nexenta_rrmgr_tcp_buf_size = 4096"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml55(td)
+msgid "(IntOpt) TCP Buffer size in KiloBytes."
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml58(td)
+msgid "nexenta_sparse = False"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml59(td)
+msgid "(BoolOpt) flag to create sparse volumes"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml62(td)
+msgid "nexenta_sparsed_volumes = True"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml66(td)
+msgid "nexenta_target_group_prefix = cinder/"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml67(td)
+msgid "(StrOpt) prefix for iSCSI target groups on SA"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml70(td)
+msgid "nexenta_target_prefix = iqn.1986-03.com.sun:02:cinder-"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml71(td)
+msgid "(StrOpt) IQN prefix for iSCSI targets"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml74(td)
+msgid "nexenta_user = admin"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml75(td)
+msgid "(StrOpt) User name to connect to Nexenta SA"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml78(td)
+msgid "nexenta_volume = cinder"
+msgstr ""
+
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml79(td)
+msgid "(StrOpt) pool on SA that will hold all volumes"
 msgstr ""
 
 #. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
-#: ./doc/common/tables/nova-xvpnvncproxy.xml0(None)
+#: ./doc/common/tables/cinder-nexenta_iscsi.xml0(None)
 msgid "translator-credits"
 msgstr "Akihiro Motoki <amotoki@gmail.com>, 2013\nTomoyuki KATO <tomo@dream.daynight.jp>, 2012-2014\ntmak <t.makabe@gmail.com>, 2013"
diff --git a/doc/config-reference/locale/config-reference.pot b/doc/config-reference/locale/config-reference.pot
index 52ebcc9a1a..1898b679e6 100644
--- a/doc/config-reference/locale/config-reference.pot
+++ b/doc/config-reference/locale/config-reference.pot
@@ -1,7 +1,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2014-05-29 06:09+0000\n"
+"POT-Creation-Date: 2014-06-03 06:11+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -9,6 +9,26 @@ msgstr ""
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
+#: ./doc/config-reference/ch_identityconfigure.xml:7(title)
+msgid "Identity service"
+msgstr ""
+
+#: ./doc/config-reference/ch_identityconfigure.xml:8(para)
+msgid "This chapter details the OpenStack Identity service configuration options. For installation prerequisites and step-by-step walkthroughs, see the <citetitle>OpenStack Installation Guide</citetitle> for your distribution (<link href=\"docs.openstack.org\">docs.openstack.org</link>) and <citetitle><link href=\"http://docs.openstack.org/admin-guide-cloud/content/\">Cloud Administrator Guide</link></citetitle>."
+msgstr ""
+
+#: ./doc/config-reference/ch_identityconfigure.xml:16(title)
+msgid "Identity service configuration file"
+msgstr ""
+
+#: ./doc/config-reference/ch_identityconfigure.xml:17(para)
+msgid "The Identity service is configured in the <filename>/etc/keystone/keystone.conf</filename> file."
+msgstr ""
+
+#: ./doc/config-reference/ch_identityconfigure.xml:19(para)
+msgid "The following tables provide a comprehensive list of the Identity service options."
+msgstr ""
+
 #: ./doc/config-reference/ch_telemetryconfigure.xml:7(title) ./doc/config-reference/ch_config-overview.xml:24(para)
 msgid "Telemetry"
 msgstr ""
@@ -25,26 +45,6 @@ msgstr ""
 msgid "The following tables provide a comprehensive list of the Telemetry configuration options."
 msgstr ""
 
-#: ./doc/config-reference/ch_imageservice.xml:7(title)
-msgid "Image Service"
-msgstr ""
-
-#: ./doc/config-reference/ch_imageservice.xml:8(para)
-msgid "Compute relies on an external image service to store virtual machine images and maintain a catalog of available images. By default, Compute is configured to use the OpenStack Image Service (Glance), which is currently the only supported image service."
-msgstr ""
-
-#: ./doc/config-reference/ch_imageservice.xml:15(para)
-msgid "If your installation requires euca2ools to register new images, you must run the <systemitem class=\"service\">nova-objectstore</systemitem> service. This service provides an Amazon S3 front-end for Glance, which is required by euca2ools."
-msgstr ""
-
-#: ./doc/config-reference/ch_imageservice.xml:20(para)
-msgid "To customize the Compute Service, use the configuration option settings documented in <xref linkend=\"config_table_nova_glance\"/> and <xref linkend=\"config_table_nova_s3\"/>."
-msgstr ""
-
-#: ./doc/config-reference/ch_imageservice.xml:24(para)
-msgid "You can modify many options in the OpenStack Image Service. The following tables provide a comprehensive list."
-msgstr ""
-
 #: ./doc/config-reference/ch_config-overview.xml:6(title)
 msgid "OpenStack configuration overview"
 msgstr ""
@@ -93,12 +93,112 @@ msgstr ""
 msgid "Orchestration"
 msgstr ""
 
-#: ./doc/config-reference/ch_databaseserviceconfigure.xml:8(para)
-msgid "The Database Service provides a scalable and reliable Cloud Database-as-a-Service functionality for both relational and non-relational database engines."
+#: ./doc/config-reference/bk-config-ref.xml:6(title) ./doc/config-reference/bk-config-ref.xml:8(titleabbrev)
+msgid "OpenStack Configuration Reference"
 msgstr ""
 
-#: ./doc/config-reference/ch_databaseserviceconfigure.xml:12(para)
-msgid "The following tables provide a comprehensive list of the Database Service configuration options."
+#: ./doc/config-reference/bk-config-ref.xml:16(orgname) ./doc/config-reference/bk-config-ref.xml:21(holder)
+msgid "OpenStack Foundation"
+msgstr ""
+
+#: ./doc/config-reference/bk-config-ref.xml:20(year)
+msgid "2013"
+msgstr ""
+
+#: ./doc/config-reference/bk-config-ref.xml:23(productname)
+msgid "OpenStack"
+msgstr ""
+
+#: ./doc/config-reference/bk-config-ref.xml:24(releaseinfo)
+msgid "icehouse"
+msgstr ""
+
+#: ./doc/config-reference/bk-config-ref.xml:28(remark)
+msgid "Copyright details are filled in by the template."
+msgstr ""
+
+#: ./doc/config-reference/bk-config-ref.xml:33(para)
+msgid "This document is for system administrators who want to look up configuration options. It contains lists of configuration options available with OpenStack and uses auto-generation to generate options and the descriptions from the code for each project. It includes sample configuration files."
+msgstr ""
+
+#: ./doc/config-reference/bk-config-ref.xml:43(date)
+msgid "2014-04-16"
+msgstr ""
+
+#: ./doc/config-reference/bk-config-ref.xml:47(para)
+msgid "Update for Icehouse: Updated all configuration tables, include sample configuration files, add chapters for Database Service, Orchestration, and Telemetry."
+msgstr ""
+
+#: ./doc/config-reference/bk-config-ref.xml:58(date)
+msgid "2014-03-11"
+msgstr ""
+
+#: ./doc/config-reference/bk-config-ref.xml:62(para)
+msgid "Sorted component listing. Moved procedures to the <link href=\"http://docs.openstack.org/admin-guide-cloud/content/\"><citetitle>Cloud Administrator Guide</citetitle></link>"
+msgstr ""
+
+#: ./doc/config-reference/bk-config-ref.xml:71(date)
+msgid "2014-01-09"
+msgstr ""
+
+#: ./doc/config-reference/bk-config-ref.xml:75(para)
+msgid "Removes content addressed in installation, merges duplicated content, and revises legacy references."
+msgstr ""
+
+#: ./doc/config-reference/bk-config-ref.xml:84(date)
+msgid "2013-10-17"
+msgstr ""
+
+#: ./doc/config-reference/bk-config-ref.xml:88(para)
+msgid "Havana release."
+msgstr ""
+
+#: ./doc/config-reference/bk-config-ref.xml:94(date)
+msgid "2013-08-16"
+msgstr ""
+
+#: ./doc/config-reference/bk-config-ref.xml:98(para)
+msgid "Moves Block Storage driver configuration information from the <citetitle>Block Storage Administration Guide</citetitle> to this reference."
+msgstr ""
+
+#: ./doc/config-reference/bk-config-ref.xml:108(date)
+msgid "2013-06-10"
+msgstr ""
+
+#: ./doc/config-reference/bk-config-ref.xml:112(para)
+msgid "Initial creation of Configuration Reference."
+msgstr ""
+
+#: ./doc/config-reference/ch_orchestrationconfigure.xml:8(para)
+msgid "The Orchestration service is designed to manage the lifecycle of infrastructure and applications within OpenStack clouds. Its various agents and services are configured in the <filename>/etc/heat/heat.conf</filename> file."
+msgstr ""
+
+#: ./doc/config-reference/ch_orchestrationconfigure.xml:12(para)
+msgid "To install Orchestration, see the <citetitle>OpenStack Installation Guide</citetitle> for your distribution (<link href=\"docs.openstack.org\">docs.openstack.org</link>)."
+msgstr ""
+
+#: ./doc/config-reference/ch_orchestrationconfigure.xml:16(para)
+msgid "The following tables provide a comprehensive list of the Orchestration configuration options."
+msgstr ""
+
+#: ./doc/config-reference/ch_blockstorageconfigure.xml:7(title)
+msgid "Block Storage"
+msgstr ""
+
+#: ./doc/config-reference/ch_blockstorageconfigure.xml:8(para)
+msgid "The OpenStack Block Storage service works with many different storage drivers that you can configure by using these instructions."
+msgstr ""
+
+#: ./doc/config-reference/ch_blockstorageconfigure.xml:12(title) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:212(title) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:140(title)
+msgid "<filename>cinder.conf</filename> configuration file"
+msgstr ""
+
+#: ./doc/config-reference/ch_blockstorageconfigure.xml:13(para)
+msgid "The <filename>cinder.conf</filename> file is installed in <filename>/etc/cinder</filename> by default. When you manually install the Block Storage service, the options in the <filename>cinder.conf</filename> file are set to default values."
+msgstr ""
+
+#: ./doc/config-reference/ch_blockstorageconfigure.xml:17(para)
+msgid "This example shows a typical <filename>cinder.conf</filename> file:"
 msgstr ""
 
 #: ./doc/config-reference/table_default-ports-peripheral-services.xml:6(caption)
@@ -209,224 +309,132 @@ msgstr ""
 msgid "OpenStack Block Storage, Networking, Orchestration, and Compute."
 msgstr ""
 
-#: ./doc/config-reference/ch_computeconfigure.xml:6(title) ./doc/config-reference/networking/section_networking-options-reference.xml:43(title)
-msgid "Compute"
+#: ./doc/config-reference/ch_imageservice.xml:7(title)
+msgid "Image Service"
 msgstr ""
 
-#: ./doc/config-reference/ch_computeconfigure.xml:7(para)
-msgid "The OpenStack Compute service is a cloud computing fabric controller, which is the main part of an IaaS system. You can use OpenStack Compute to host and manage cloud computing systems. This section describes the OpenStack Compute configuration options."
+#: ./doc/config-reference/ch_imageservice.xml:8(para)
+msgid "Compute relies on an external image service to store virtual machine images and maintain a catalog of available images. By default, Compute is configured to use the OpenStack Image Service (Glance), which is currently the only supported image service."
 msgstr ""
 
-#: ./doc/config-reference/ch_computeconfigure.xml:12(para)
-msgid "To configure your Compute installation, you must define configuration options in these files:"
+#: ./doc/config-reference/ch_imageservice.xml:15(para)
+msgid "If your installation requires euca2ools to register new images, you must run the <systemitem class=\"service\">nova-objectstore</systemitem> service. This service provides an Amazon S3 front-end for Glance, which is required by euca2ools."
 msgstr ""
 
-#: ./doc/config-reference/ch_computeconfigure.xml:16(para)
-msgid "<filename>nova.conf</filename>. Contains most of the Compute configuration options. Resides in the <filename>/etc/nova</filename> directory."
+#: ./doc/config-reference/ch_imageservice.xml:20(para)
+msgid "To customize the Compute Service, use the configuration option settings documented in <xref linkend=\"config_table_nova_glance\"/> and <xref linkend=\"config_table_nova_s3\"/>."
 msgstr ""
 
-#: ./doc/config-reference/ch_computeconfigure.xml:21(para)
-msgid "<filename>api-paste.ini</filename>. Defines Compute limits. Resides in the <filename>/etc/nova</filename> directory."
+#: ./doc/config-reference/ch_imageservice.xml:24(para)
+msgid "You can modify many options in the OpenStack Image Service. The following tables provide a comprehensive list."
 msgstr ""
 
-#: ./doc/config-reference/ch_computeconfigure.xml:26(para)
-msgid "Related Image Service and Identity service management configuration files."
+#: ./doc/config-reference/ch_databaseserviceconfigure.xml:8(para)
+msgid "The Database Service provides a scalable and reliable Cloud Database-as-a-Service functionality for both relational and non-relational database engines."
 msgstr ""
 
-#: ./doc/config-reference/ch_computeconfigure.xml:32(title)
-msgid "Configure logging"
+#: ./doc/config-reference/ch_databaseserviceconfigure.xml:12(para)
+msgid "The following tables provide a comprehensive list of the Database Service configuration options."
 msgstr ""
 
-#: ./doc/config-reference/ch_computeconfigure.xml:33(para)
-msgid "You can use <filename>nova.conf</filename> file to configure where Compute logs events, the level of logging, and log formats."
+#: ./doc/config-reference/ch_objectstorageconfigure.xml:6(title)
+msgid "Object Storage"
 msgstr ""
 
-#: ./doc/config-reference/ch_computeconfigure.xml:36(para)
-msgid "To customize log formats for OpenStack Compute, use the configuration option settings documented in <xref linkend=\"config_table_nova_logging\"/>."
+#: ./doc/config-reference/ch_objectstorageconfigure.xml:7(para)
+msgid "OpenStack Object Storage uses multiple configuration files for multiple services and background daemons, and <placeholder-1/> to manage server configurations. Default configuration options appear in the <code>[DEFAULT]</code> section. You can override the default values by setting values in the other sections."
 msgstr ""
 
-#: ./doc/config-reference/ch_computeconfigure.xml:41(title)
-msgid "Configure authentication and authorization"
+#: ./doc/config-reference/ch_objectstorageconfigure.xml:17(title)
+msgid "Object server configuration"
 msgstr ""
 
-#: ./doc/config-reference/ch_computeconfigure.xml:42(para)
-msgid "There are different methods of authentication for the OpenStack Compute project, including no authentication. The preferred system is the OpenStack Identity service, code-named Keystone."
+#: ./doc/config-reference/ch_objectstorageconfigure.xml:18(para)
+msgid "Find an example object server configuration at <filename>etc/object-server.conf-sample</filename> in the source code repository."
 msgstr ""
 
-#: ./doc/config-reference/ch_computeconfigure.xml:46(para)
-msgid "To customize authorization settings for Compute, use the configuration options documented in <xref linkend=\"config_table_nova_authentication\"/>."
+#: ./doc/config-reference/ch_objectstorageconfigure.xml:21(para) ./doc/config-reference/ch_objectstorageconfigure.xml:48(para) ./doc/config-reference/ch_objectstorageconfigure.xml:71(para) ./doc/config-reference/ch_objectstorageconfigure.xml:101(para) ./doc/config-reference/ch_objectstorageconfigure.xml:118(para) ./doc/config-reference/ch_objectstorageconfigure.xml:145(para) ./doc/config-reference/ch_objectstorageconfigure.xml:186(para) ./doc/config-reference/ch_objectstorageconfigure.xml:195(para)
+msgid "The available configuration options are:"
 msgstr ""
 
-#: ./doc/config-reference/ch_computeconfigure.xml:49(para)
-msgid "To customize certificate authority settings for Compute, use the configuration options documented in <xref linkend=\"config_table_nova_ca\"/>."
+#: ./doc/config-reference/ch_objectstorageconfigure.xml:39(title)
+msgid "Sample object server configuration file"
 msgstr ""
 
-#: ./doc/config-reference/ch_computeconfigure.xml:52(para)
-msgid "To customize Compute and the Identity service to use LDAP as a backend, refer to the configuration options documented in <xref linkend=\"config_table_nova_ldap\"/>."
+#: ./doc/config-reference/ch_objectstorageconfigure.xml:44(title)
+msgid "Object expirer configuration"
 msgstr ""
 
-#: ./doc/config-reference/ch_computeconfigure.xml:58(title)
-msgid "Configure resize"
+#: ./doc/config-reference/ch_objectstorageconfigure.xml:45(para)
+msgid "Find an example object expirer configuration at <filename>etc/object-expirer.conf-sample</filename> in the source code repository."
 msgstr ""
 
-#: ./doc/config-reference/ch_computeconfigure.xml:59(para)
-msgid "Resize (or Server resize) is the ability to change the flavor of a server, thus allowing it to upscale or downscale according to user needs. For this feature to work properly, you might need to configure some underlying virt layers."
+#: ./doc/config-reference/ch_objectstorageconfigure.xml:62(title)
+msgid "Sample object expirer configuration file"
 msgstr ""
 
-#: ./doc/config-reference/ch_computeconfigure.xml:64(title) ./doc/config-reference/compute/section_hypervisor_kvm.xml:5(title)
-msgid "KVM"
+#: ./doc/config-reference/ch_objectstorageconfigure.xml:67(title)
+msgid "Container server configuration"
 msgstr ""
 
-#: ./doc/config-reference/ch_computeconfigure.xml:65(para)
-msgid "Resize on KVM is implemented currently by transferring the images between compute nodes over ssh. For KVM you need hostnames to resolve properly and passwordless ssh access between your compute hosts. Direct access from one compute host to another is needed to copy the VM file across."
+#: ./doc/config-reference/ch_objectstorageconfigure.xml:68(para)
+msgid "Find an example container server configuration at <filename>etc/container-server.conf-sample</filename> in the source code repository."
 msgstr ""
 
-#: ./doc/config-reference/ch_computeconfigure.xml:70(para)
-msgid "Cloud end users can find out how to resize a server by reading the <link href=\"http://docs.openstack.org/user-guide/content/nova_cli_resize.html\">OpenStack End User Guide</link>."
+#: ./doc/config-reference/ch_objectstorageconfigure.xml:91(title)
+msgid "Sample container server configuration file"
 msgstr ""
 
-#: ./doc/config-reference/ch_computeconfigure.xml:76(title)
-msgid "XenServer"
+#: ./doc/config-reference/ch_objectstorageconfigure.xml:97(title)
+msgid "Container sync realms configuration"
 msgstr ""
 
-#: ./doc/config-reference/ch_computeconfigure.xml:77(para)
-msgid "To get resize to work with XenServer (and XCP), you need to establish a root trust between all hypervisor nodes and provide an /image mount point to your hypervisors dom0."
+#: ./doc/config-reference/ch_objectstorageconfigure.xml:98(para)
+msgid "Find an example container sync realms configuration at <filename>etc/container-sync-realms.conf-sample</filename> in the source code repository."
 msgstr ""
 
-#: ./doc/config-reference/bk-config-ref.xml:6(title) ./doc/config-reference/bk-config-ref.xml:8(titleabbrev)
-msgid "OpenStack Configuration Reference"
+#: ./doc/config-reference/ch_objectstorageconfigure.xml:109(title)
+msgid "Sample container sync realms configuration file"
 msgstr ""
 
-#: ./doc/config-reference/bk-config-ref.xml:16(orgname) ./doc/config-reference/bk-config-ref.xml:21(holder)
-msgid "OpenStack Foundation"
+#: ./doc/config-reference/ch_objectstorageconfigure.xml:114(title)
+msgid "Account server configuration"
 msgstr ""
 
-#: ./doc/config-reference/bk-config-ref.xml:20(year)
-msgid "2013"
+#: ./doc/config-reference/ch_objectstorageconfigure.xml:115(para)
+msgid "Find an example account server configuration at <filename>etc/account-server.conf-sample</filename> in the source code repository."
 msgstr ""
 
-#: ./doc/config-reference/bk-config-ref.xml:23(productname)
-msgid "OpenStack"
+#: ./doc/config-reference/ch_objectstorageconfigure.xml:136(title)
+msgid "Sample account server configuration file"
 msgstr ""
 
-#: ./doc/config-reference/bk-config-ref.xml:24(releaseinfo)
-msgid "icehouse"
+#: ./doc/config-reference/ch_objectstorageconfigure.xml:141(title)
+msgid "Proxy server configuration"
 msgstr ""
 
-#: ./doc/config-reference/bk-config-ref.xml:28(remark)
-msgid "Copyright details are filled in by the template."
+#: ./doc/config-reference/ch_objectstorageconfigure.xml:142(para)
+msgid "Find an example proxy server configuration at <filename>etc/proxy-server.conf-sample</filename> in the source code repository."
 msgstr ""
 
-#: ./doc/config-reference/bk-config-ref.xml:33(para)
-msgid "This document is for system administrators who want to look up configuration options. It contains lists of configuration options available with OpenStack and uses auto-generation to generate options and the descriptions from the code for each project. It includes sample configuration files."
+#: ./doc/config-reference/ch_objectstorageconfigure.xml:177(title)
+msgid "Sample proxy server configuration file"
 msgstr ""
 
-#: ./doc/config-reference/bk-config-ref.xml:43(date)
-msgid "2014-04-16"
+#: ./doc/config-reference/ch_objectstorageconfigure.xml:182(title)
+msgid "Proxy server memcache configuration"
 msgstr ""
 
-#: ./doc/config-reference/bk-config-ref.xml:47(para)
-msgid "Update for Icehouse: Updated all configuration tables, include sample configuration files, add chapters for Database Service, Orchestration, and Telemetry."
+#: ./doc/config-reference/ch_objectstorageconfigure.xml:183(para)
+msgid "Find an example memcache configuration for the proxy server at <filename>etc/memcache.conf-sample</filename> in the source code repository."
 msgstr ""
 
-#: ./doc/config-reference/bk-config-ref.xml:58(date)
-msgid "2014-03-11"
+#: ./doc/config-reference/ch_objectstorageconfigure.xml:191(title)
+msgid "Rsyncd configuration"
 msgstr ""
 
-#: ./doc/config-reference/bk-config-ref.xml:62(para)
-msgid "Sorted component listing. Moved procedures to the <link href=\"http://docs.openstack.org/admin-guide-cloud/content/\"><citetitle>Cloud Administrator Guide</citetitle></link>"
-msgstr ""
-
-#: ./doc/config-reference/bk-config-ref.xml:71(date)
-msgid "2014-01-09"
-msgstr ""
-
-#: ./doc/config-reference/bk-config-ref.xml:75(para)
-msgid "Removes content addressed in installation, merges duplicated content, and revises legacy references."
-msgstr ""
-
-#: ./doc/config-reference/bk-config-ref.xml:84(date)
-msgid "2013-10-17"
-msgstr ""
-
-#: ./doc/config-reference/bk-config-ref.xml:88(para)
-msgid "Havana release."
-msgstr ""
-
-#: ./doc/config-reference/bk-config-ref.xml:94(date)
-msgid "2013-08-16"
-msgstr ""
-
-#: ./doc/config-reference/bk-config-ref.xml:98(para)
-msgid "Moves Block Storage driver configuration information from the <citetitle>Block Storage Administration Guide</citetitle> to this reference."
-msgstr ""
-
-#: ./doc/config-reference/bk-config-ref.xml:108(date)
-msgid "2013-06-10"
-msgstr ""
-
-#: ./doc/config-reference/bk-config-ref.xml:112(para)
-msgid "Initial creation of Configuration Reference."
-msgstr ""
-
-#: ./doc/config-reference/ch_blockstorageconfigure.xml:7(title)
-msgid "Block Storage"
-msgstr ""
-
-#: ./doc/config-reference/ch_blockstorageconfigure.xml:8(para)
-msgid "The OpenStack Block Storage service works with many different storage drivers that you can configure by using these instructions."
-msgstr ""
-
-#: ./doc/config-reference/ch_blockstorageconfigure.xml:12(title) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:212(title) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:140(title)
-msgid "<filename>cinder.conf</filename> configuration file"
-msgstr ""
-
-#: ./doc/config-reference/ch_blockstorageconfigure.xml:13(para)
-msgid "The <filename>cinder.conf</filename> file is installed in <filename>/etc/cinder</filename> by default. When you manually install the Block Storage service, the options in the <filename>cinder.conf</filename> file are set to default values."
-msgstr ""
-
-#: ./doc/config-reference/ch_blockstorageconfigure.xml:17(para)
-msgid "This example shows a typical <filename>cinder.conf</filename> file:"
-msgstr ""
-
-#: ./doc/config-reference/app_firewalls-ports.xml:6(title)
-msgid "Firewalls and default ports"
-msgstr ""
-
-#: ./doc/config-reference/app_firewalls-ports.xml:7(para)
-msgid "On some deployments, such as ones where restrictive firewalls are in place, you might need to manually configure a firewall to permit OpenStack service traffic."
-msgstr ""
-
-#: ./doc/config-reference/app_firewalls-ports.xml:10(para)
-msgid "To manually configure a firewall, you must permit traffic through the ports that each OpenStack service uses. This table lists the default ports that each OpenStack service uses:"
-msgstr ""
-
-#: ./doc/config-reference/app_firewalls-ports.xml:15(para)
-msgid "To function properly, some OpenStack components depend on other, non-OpenStack services. For example, the OpenStack dashboard uses HTTP for non-secure communication. In this case, you must configure the firewall to allow traffic to and from HTTP."
-msgstr ""
-
-#: ./doc/config-reference/app_firewalls-ports.xml:20(para)
-msgid "This table lists the ports that other OpenStack components use:"
-msgstr ""
-
-#: ./doc/config-reference/ch_identityconfigure.xml:7(title)
-msgid "Identity service"
-msgstr ""
-
-#: ./doc/config-reference/ch_identityconfigure.xml:8(para)
-msgid "This chapter details the OpenStack Identity service configuration options. For installation prerequisites and step-by-step walkthroughs, see the <citetitle>OpenStack Installation Guide</citetitle> for your distribution (<link href=\"docs.openstack.org\">docs.openstack.org</link>) and <citetitle><link href=\"http://docs.openstack.org/admin-guide-cloud/content/\">Cloud Administrator Guide</link></citetitle>."
-msgstr ""
-
-#: ./doc/config-reference/ch_identityconfigure.xml:16(title)
-msgid "Identity service configuration file"
-msgstr ""
-
-#: ./doc/config-reference/ch_identityconfigure.xml:17(para)
-msgid "The Identity service is configured in the <filename>/etc/keystone/keystone.conf</filename> file."
-msgstr ""
-
-#: ./doc/config-reference/ch_identityconfigure.xml:19(para)
-msgid "The following tables provide a comprehensive list of the Identity service options."
+#: ./doc/config-reference/ch_objectstorageconfigure.xml:192(para)
+msgid "Find an example rsyncd configuration at <filename>etc/rsyncd.conf-sample</filename> in the source code repository."
 msgstr ""
 
 #: ./doc/config-reference/table_default-ports-primary-services.xml:6(caption)
@@ -641,112 +649,108 @@ msgstr ""
 msgid "8777"
 msgstr ""
 
-#: ./doc/config-reference/ch_objectstorageconfigure.xml:6(title)
-msgid "Object Storage"
+#: ./doc/config-reference/ch_computeconfigure.xml:6(title) ./doc/config-reference/networking/section_networking-options-reference.xml:43(title)
+msgid "Compute"
 msgstr ""
 
-#: ./doc/config-reference/ch_objectstorageconfigure.xml:7(para)
-msgid "OpenStack Object Storage uses multiple configuration files for multiple services and background daemons, and <placeholder-1/> to manage server configurations. Default configuration options appear in the <code>[DEFAULT]</code> section. You can override the default values by setting values in the other sections."
+#: ./doc/config-reference/ch_computeconfigure.xml:7(para)
+msgid "The OpenStack Compute service is a cloud computing fabric controller, which is the main part of an IaaS system. You can use OpenStack Compute to host and manage cloud computing systems. This section describes the OpenStack Compute configuration options."
 msgstr ""
 
-#: ./doc/config-reference/ch_objectstorageconfigure.xml:17(title)
-msgid "Object server configuration"
+#: ./doc/config-reference/ch_computeconfigure.xml:12(para)
+msgid "To configure your Compute installation, you must define configuration options in these files:"
 msgstr ""
 
-#: ./doc/config-reference/ch_objectstorageconfigure.xml:18(para)
-msgid "Find an example object server configuration at <filename>etc/object-server.conf-sample</filename> in the source code repository."
+#: ./doc/config-reference/ch_computeconfigure.xml:16(para)
+msgid "<filename>nova.conf</filename>. Contains most of the Compute configuration options. Resides in the <filename>/etc/nova</filename> directory."
 msgstr ""
 
-#: ./doc/config-reference/ch_objectstorageconfigure.xml:21(para) ./doc/config-reference/ch_objectstorageconfigure.xml:48(para) ./doc/config-reference/ch_objectstorageconfigure.xml:71(para) ./doc/config-reference/ch_objectstorageconfigure.xml:101(para) ./doc/config-reference/ch_objectstorageconfigure.xml:118(para) ./doc/config-reference/ch_objectstorageconfigure.xml:145(para) ./doc/config-reference/ch_objectstorageconfigure.xml:186(para) ./doc/config-reference/ch_objectstorageconfigure.xml:195(para)
-msgid "The available configuration options are:"
+#: ./doc/config-reference/ch_computeconfigure.xml:21(para)
+msgid "<filename>api-paste.ini</filename>. Defines Compute limits. Resides in the <filename>/etc/nova</filename> directory."
 msgstr ""
 
-#: ./doc/config-reference/ch_objectstorageconfigure.xml:39(title)
-msgid "Sample object server configuration file"
+#: ./doc/config-reference/ch_computeconfigure.xml:26(para)
+msgid "Related Image Service and Identity service management configuration files."
 msgstr ""
 
-#: ./doc/config-reference/ch_objectstorageconfigure.xml:44(title)
-msgid "Object expirer configuration"
+#: ./doc/config-reference/ch_computeconfigure.xml:32(title)
+msgid "Configure logging"
 msgstr ""
 
-#: ./doc/config-reference/ch_objectstorageconfigure.xml:45(para)
-msgid "Find an example object expirer configuration at <filename>etc/object-expirer.conf-sample</filename> in the source code repository."
+#: ./doc/config-reference/ch_computeconfigure.xml:33(para)
+msgid "You can use <filename>nova.conf</filename> file to configure where Compute logs events, the level of logging, and log formats."
 msgstr ""
 
-#: ./doc/config-reference/ch_objectstorageconfigure.xml:62(title)
-msgid "Sample object expirer configuration file"
+#: ./doc/config-reference/ch_computeconfigure.xml:36(para)
+msgid "To customize log formats for OpenStack Compute, use the configuration option settings documented in <xref linkend=\"config_table_nova_logging\"/>."
 msgstr ""
 
-#: ./doc/config-reference/ch_objectstorageconfigure.xml:67(title)
-msgid "Container server configuration"
+#: ./doc/config-reference/ch_computeconfigure.xml:41(title)
+msgid "Configure authentication and authorization"
 msgstr ""
 
-#: ./doc/config-reference/ch_objectstorageconfigure.xml:68(para)
-msgid "Find an example container server configuration at <filename>etc/container-server.conf-sample</filename> in the source code repository."
+#: ./doc/config-reference/ch_computeconfigure.xml:42(para)
+msgid "There are different methods of authentication for the OpenStack Compute project, including no authentication. The preferred system is the OpenStack Identity service, code-named Keystone."
 msgstr ""
 
-#: ./doc/config-reference/ch_objectstorageconfigure.xml:91(title)
-msgid "Sample container server configuration file"
+#: ./doc/config-reference/ch_computeconfigure.xml:46(para)
+msgid "To customize authorization settings for Compute, use the configuration options documented in <xref linkend=\"config_table_nova_authentication\"/>."
 msgstr ""
 
-#: ./doc/config-reference/ch_objectstorageconfigure.xml:97(title)
-msgid "Container sync realms configuration"
+#: ./doc/config-reference/ch_computeconfigure.xml:49(para)
+msgid "To customize certificate authority settings for Compute, use the configuration options documented in <xref linkend=\"config_table_nova_ca\"/>."
 msgstr ""
 
-#: ./doc/config-reference/ch_objectstorageconfigure.xml:98(para)
-msgid "Find an example container sync realms configuration at <filename>etc/container-sync-realms.conf-sample</filename> in the source code repository."
+#: ./doc/config-reference/ch_computeconfigure.xml:52(para)
+msgid "To customize Compute and the Identity service to use LDAP as a backend, refer to the configuration options documented in <xref linkend=\"config_table_nova_ldap\"/>."
 msgstr ""
 
-#: ./doc/config-reference/ch_objectstorageconfigure.xml:109(title)
-msgid "Sample container sync realms configuration file"
+#: ./doc/config-reference/ch_computeconfigure.xml:58(title)
+msgid "Configure resize"
 msgstr ""
 
-#: ./doc/config-reference/ch_objectstorageconfigure.xml:114(title)
-msgid "Account server configuration"
+#: ./doc/config-reference/ch_computeconfigure.xml:59(para)
+msgid "Resize (or Server resize) is the ability to change the flavor of a server, thus allowing it to upscale or downscale according to user needs. For this feature to work properly, you might need to configure some underlying virt layers."
 msgstr ""
 
-#: ./doc/config-reference/ch_objectstorageconfigure.xml:115(para)
-msgid "Find an example account server configuration at <filename>etc/account-server.conf-sample</filename> in the source code repository."
+#: ./doc/config-reference/ch_computeconfigure.xml:64(title) ./doc/config-reference/compute/section_hypervisor_kvm.xml:5(title)
+msgid "KVM"
 msgstr ""
 
-#: ./doc/config-reference/ch_objectstorageconfigure.xml:136(title)
-msgid "Sample account server configuration file"
+#: ./doc/config-reference/ch_computeconfigure.xml:65(para)
+msgid "Resize on KVM is implemented currently by transferring the images between compute nodes over ssh. For KVM you need hostnames to resolve properly and passwordless ssh access between your compute hosts. Direct access from one compute host to another is needed to copy the VM file across."
 msgstr ""
 
-#: ./doc/config-reference/ch_objectstorageconfigure.xml:141(title)
-msgid "Proxy server configuration"
+#: ./doc/config-reference/ch_computeconfigure.xml:70(para)
+msgid "Cloud end users can find out how to resize a server by reading the <link href=\"http://docs.openstack.org/user-guide/content/nova_cli_resize.html\">OpenStack End User Guide</link>."
 msgstr ""
 
-#: ./doc/config-reference/ch_objectstorageconfigure.xml:142(para)
-msgid "Find an example proxy server configuration at <filename>etc/proxy-server.conf-sample</filename> in the source code repository."
+#: ./doc/config-reference/ch_computeconfigure.xml:76(title)
+msgid "XenServer"
 msgstr ""
 
-#: ./doc/config-reference/ch_objectstorageconfigure.xml:177(title)
-msgid "Sample proxy server configuration file"
+#: ./doc/config-reference/ch_computeconfigure.xml:77(para)
+msgid "To get resize to work with XenServer (and XCP), you need to establish a root trust between all hypervisor nodes and provide an /image mount point to your hypervisors dom0."
 msgstr ""
 
-#: ./doc/config-reference/ch_objectstorageconfigure.xml:182(title)
-msgid "Proxy server memcache configuration"
+#: ./doc/config-reference/app_firewalls-ports.xml:6(title)
+msgid "Firewalls and default ports"
 msgstr ""
 
-#: ./doc/config-reference/ch_objectstorageconfigure.xml:183(para)
-msgid "Find an example memcache configuration for the proxy server at <filename>etc/memcache.conf-sample</filename> in the source code repository."
+#: ./doc/config-reference/app_firewalls-ports.xml:7(para)
+msgid "On some deployments, such as ones where restrictive firewalls are in place, you might need to manually configure a firewall to permit OpenStack service traffic."
 msgstr ""
 
-#: ./doc/config-reference/ch_objectstorageconfigure.xml:191(title)
-msgid "Rsyncd configuration"
+#: ./doc/config-reference/app_firewalls-ports.xml:10(para)
+msgid "To manually configure a firewall, you must permit traffic through the ports that each OpenStack service uses. This table lists the default ports that each OpenStack service uses:"
 msgstr ""
 
-#: ./doc/config-reference/ch_objectstorageconfigure.xml:192(para)
-msgid "Find an example rsyncd configuration at <filename>etc/rsyncd.conf-sample</filename> in the source code repository."
+#: ./doc/config-reference/app_firewalls-ports.xml:15(para)
+msgid "To function properly, some OpenStack components depend on other, non-OpenStack services. For example, the OpenStack dashboard uses HTTP for non-secure communication. In this case, you must configure the firewall to allow traffic to and from HTTP."
 msgstr ""
 
-#: ./doc/config-reference/ch_dashboardconfigure.xml:6(title)
-msgid "Dashboard"
-msgstr ""
-
-#: ./doc/config-reference/ch_dashboardconfigure.xml:7(para)
-msgid "This chapter describes how to configure the OpenStack dashboard with Apache web server."
+#: ./doc/config-reference/app_firewalls-ports.xml:20(para)
+msgid "This table lists the ports that other OpenStack components use:"
 msgstr ""
 
 #: ./doc/config-reference/ch_networkingconfigure.xml:7(title)
@@ -757,270 +761,5985 @@ msgstr ""
 msgid "This chapter explains the OpenStack Networking configuration options. For installation prerequisites, steps, and use cases, see the <citetitle>OpenStack Installation Guide</citetitle> for your distribution (<link href=\"docs.openstack.org\">docs.openstack.org</link>) and <citetitle><link href=\"http://docs.openstack.org/admin-guide-cloud/content/\">Cloud Administrator Guide</link></citetitle>."
 msgstr ""
 
-#: ./doc/config-reference/ch_orchestrationconfigure.xml:8(para)
-msgid "The Orchestration service is designed to manage the lifecycle of infrastructure and applications within OpenStack clouds. Its various agents and services are configured in the <filename>/etc/heat/heat.conf</filename> file."
+#: ./doc/config-reference/ch_dashboardconfigure.xml:6(title)
+msgid "Dashboard"
 msgstr ""
 
-#: ./doc/config-reference/ch_orchestrationconfigure.xml:12(para)
-msgid "To install Orchestration, see the <citetitle>OpenStack Installation Guide</citetitle> for your distribution (<link href=\"docs.openstack.org\">docs.openstack.org</link>)."
+#: ./doc/config-reference/ch_dashboardconfigure.xml:7(para)
+msgid "This chapter describes how to configure the OpenStack dashboard with Apache web server."
 msgstr ""
 
-#: ./doc/config-reference/ch_orchestrationconfigure.xml:16(para)
-msgid "The following tables provide a comprehensive list of the Orchestration configuration options."
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:6(title)
+msgid "Networking configuration options"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-configure-xen.xml:6(title) ./doc/config-reference/compute/section_compute-configure-xen.xml:70(title)
-msgid "Xen configuration reference"
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:7(para)
+msgid "The options and descriptions listed in this introduction are auto generated from the code in the Networking service project, which provides software-defined networking between VMs run in Compute. The list contains common options, while the subsections list the options for the various networking plug-ins."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-configure-xen.xml:7(para)
-msgid "The following section discusses some commonly changed options in XenServer. The table below provides a complete reference of all configuration options available for configuring Xen with OpenStack."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-configure-xen.xml:11(para)
-msgid "The recommended way to use Xen with OpenStack is through the XenAPI driver. To enable the XenAPI driver, add the following configuration options <filename>/etc/nova/nova.conf</filename> and restart the <systemitem class=\"service\">nova-compute</systemitem> service:"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-configure-xen.xml:19(para)
-msgid "These connection details are used by the OpenStack Compute service to contact your hypervisor and are the same details you use to connect XenCenter, the XenServer management console, to your XenServer or XCP box."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-configure-xen.xml:23(para)
-msgid "The <literal>xenapi_connection_url</literal> is generally the management network IP address of the XenServer. Though it is possible to use the internal network IP Address (169.250.0.1) to contact XenAPI, this does not allow live migration between hosts, and other functionalities like host aggregates do not work."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-configure-xen.xml:30(para)
-msgid "It is possible to manage Xen using libvirt, though this is not well-tested or supported. To experiment using Xen through libvirt add the following configuration options <filename>/etc/nova/nova.conf</filename>: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-configure-xen.xml:38(title) ./doc/config-reference/networking/section_networking-options-reference.xml:19(title)
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:19(title) ./doc/config-reference/compute/section_compute-configure-xen.xml:38(title)
 msgid "Agent"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-configure-xen.xml:39(para)
-msgid "If you don't have the guest agent on your VMs, it takes a long time for nova to decide the VM has successfully started. Generally a large timeout is required for Windows instances, bug you may want to tweak <literal>agent_version_timeout</literal>"
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:20(para)
+msgid "Use the following options to alter agent-related settings."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-configure-xen.xml:44(title)
-msgid "Firewall"
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:25(title)
+msgid "API"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-configure-xen.xml:45(para)
-msgid "If using nova-network, IPTables is supported: <placeholder-1/> Alternately, doing the isolation in Dom0: <placeholder-2/>"
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:26(para)
+msgid "Use the following options to alter API-related settings."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-configure-xen.xml:51(title)
-msgid "VNC proxy address"
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:31(title)
+msgid "Token authentication"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-configure-xen.xml:52(para)
-msgid "Assuming you are talking to XenAPI through the host local management network, and XenServer is on the address: 169.254.0.1, you can use the following: <literal>vncserver_proxyclient_address=169.254.0.1</literal>"
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:32(para)
+msgid "Use the following options to alter token authentication settings."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-configure-xen.xml:58(title)
-msgid "Storage"
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:37(title)
+msgid "CADF"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-configure-xen.xml:65(para)
-msgid "To use a XenServer pool, you must create the pool by using the Host Aggregates feature."
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:38(para)
+msgid "Use the following options to alter Cloud Audit Data Federation (CADF) settings."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-configure-xen.xml:59(para)
-msgid "You can specify which Storage Repository to use with nova by looking at the following flag. The default is to use the local-storage setup by the default installer: <placeholder-1/> Another good alternative is to use the \"default\" storage (for example if you have attached NFS or any other shared storage): <placeholder-2/><placeholder-3/>"
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:44(para)
+msgid "Use the following options to alter Compute-related settings."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-configure-xen.xml:71(para)
-msgid "To customize the Xen driver, use the configuration option settings documented in <xref linkend=\"config_table_nova_xen\"/>."
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:49(title)
+msgid "Database"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:50(para) ./doc/config-reference/networking/section_networking-options-reference.xml:56(para)
+msgid "Use the following options to alter Database-related settings."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:55(title)
+msgid "DHCP agent"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:61(title)
+msgid "Embrane LBaaS driver"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:62(para)
+msgid "Use the following options to alter Embrane Loadbalancer-as-a-Service related settings."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:68(title)
+msgid "Firewall-as-a-Service driver"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:69(para)
+msgid "Use the following options in the <filename>fwaas_driver.ini</filename> file for the FwaaS driver."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:75(title)
+msgid "L3 agent"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:76(para)
+msgid "Use the following options in the <filename>l3_agent.ini</filename> file for the L3 agent."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:82(title)
+msgid "Loadbalancer-as-a-Service agent"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:83(para)
+msgid "Use the following options in the <filename>lbaas_agent.ini</filename> file for the LbaaS agent."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:89(title)
+msgid "Logging"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:90(para)
+msgid "Use the following options to alter logging settings."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:95(title)
+msgid "Metadata Agent"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:96(para)
+msgid "Use the following options in the <filename>metadata_agent.ini</filename> file for the Metadata agent."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:102(title)
+msgid "Metering Agent"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:103(para)
+msgid "Use the following options in the <filename>metering_agent.ini</filename> file for the Metering agent."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:109(title)
+msgid "Policy"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:110(para)
+msgid "Use the following options in the <filename>neutron.conf</filename> file to change policy settings."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:116(title)
+msgid "Quotas"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:117(para)
+msgid "Use the following options in the <filename>neutron.conf</filename> file for the quota system."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:123(title)
+msgid "Rootwrap"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:124(para)
+msgid "Use the following options in the <filename>neutron.conf</filename> file for the rootwrap settings"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:130(title)
+msgid "Scheduler"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:131(para)
+msgid "Use the following options in the <filename>neutron.conf</filename> file to change scheduler settings."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:137(title)
+msgid "Security Groups"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:138(para)
+msgid "Use the following options in the configuration file for your driver to change security group settings."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:144(title)
+msgid "SSL"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:145(para)
+msgid "Use the following options in the <filename>neutron.conf</filename> file to enable SSL."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:151(title)
+msgid "Testing"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:152(para)
+msgid "Use the following options to alter testing-related features."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:157(title)
+msgid "vArmour Firewall-as-a-Service driver"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:158(para)
+msgid "Use the following options in the <filename>l3_agent.ini</filename> file for the vArmour FwaaS driver."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:164(title)
+msgid "VPN"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:165(para)
+msgid "Use the following options in the <filename>vpn_agent.ini</filename> file for the VPN agent."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:171(title)
+msgid "WSGI"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-options-reference.xml:172(para)
+msgid "Use the following options in the <filename>neutron.conf</filename> file to configure the WSGI layer."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:4(title)
+msgid "Networking sample configuration files"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:5(para)
+msgid "All the files in this section can be found in <filename class=\"directory\">/etc/neutron/</filename>."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:7(title)
+msgid "neutron.conf"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:8(para)
+msgid "Use the <filename>neutron.conf</filename> file to configure the majority of the OpenStack Networking options."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:15(title) ./doc/config-reference/block-storage/section_block-storage-sample-configuration-files.xml:15(title) ./doc/config-reference/compute/section_compute-sample-configuration-files.xml:7(title)
+msgid "api-paste.ini"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:16(para)
+msgid "Use the <filename>api-paste.ini</filename> to configure the OpenStack Networking API."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:22(title) ./doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml:35(title) ./doc/config-reference/identity/section_keystone-sample-conf-files.xml:42(title) ./doc/config-reference/block-storage/section_block-storage-sample-configuration-files.xml:22(title) ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:50(title) ./doc/config-reference/compute/section_compute-sample-configuration-files.xml:15(title)
+msgid "policy.json"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:23(para)
+msgid "Use the <filename>policy.json</filename> file to define additional access controls that apply to the OpenStack Networking service."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:30(title) ./doc/config-reference/block-storage/section_block-storage-sample-configuration-files.xml:27(title) ./doc/config-reference/compute/section_compute-sample-configuration-files.xml:22(title)
+msgid "rootwrap.conf"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:31(para)
+msgid "Use the <filename>rootwrap.conf</filename> file to define configuration values used by the <placeholder-1/> script when the OpenStack Networking service must escalate its privileges to those of the root user."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:39(title)
+msgid "Configuration files for plug-in agents"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:40(para)
+msgid "Each plug-in agent that runs on an OpenStack Networking node, to perform local networking configuration for the node's VMs and networking services, has its own configuration file."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:44(title)
+msgid "dhcp_agent.ini"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:50(title)
+msgid "l3_agent.ini"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:56(title)
+msgid "lbaas_agent.ini"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:62(title)
+msgid "metadata_agent.ini"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins.xml:7(title)
+msgid "Networking plug-ins"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins.xml:8(para)
+msgid "OpenStack Networking introduces the concept of a plug-in, which is a back-end implementation of the OpenStack Networking API. A plug-in can use a variety of technologies to implement the logical API requests. Some OpenStack Networking plug-ins might use basic Linux VLANs and IP tables, while others might use more advanced technologies, such as L2-in-L3 tunneling or OpenFlow. These sections detail the configuration options for the various plug-ins."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins.xml:19(title)
+msgid "BigSwitch configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins.xml:25(title)
+msgid "Brocade configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins.xml:31(title)
+msgid "CISCO configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins.xml:37(title)
+msgid "CloudBase Hyper-V Agent configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins.xml:44(title)
+msgid "Embrane configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins.xml:51(title)
+msgid "IBM SDN-VE configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins.xml:57(title)
+msgid "Linux bridge Agent configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins.xml:64(title)
+msgid "Mellanox configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins.xml:70(title)
+msgid "Meta Plug-in configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins.xml:71(para)
+msgid "The Meta Plug-in allows you to use multiple plug-ins at the same time."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins.xml:79(title)
+msgid "MidoNet configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins.xml:85(title)
+msgid "NEC configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins.xml:91(title)
+msgid "Nuage configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins.xml:97(title)
+msgid "One Convergence NVSD configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins.xml:103(title)
+msgid "VMware NSX configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins.xml:109(title)
+msgid "Open vSwitch Agent configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins.xml:116(title)
+msgid "PLUMgrid configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins.xml:122(title)
+msgid "Ryu configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:7(title)
+msgid "Modular Layer 2 (ml2) configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:8(para)
+msgid "The Modular Layer 2 (ml2) plug-in has two components: network types and mechanisms. You can configure these components separately. This section describes these configuration options."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:13(title)
+msgid "MTU bug with VXLAN tunnelling"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:14(para)
+msgid "Due to a bug in Linux Bridge software maximum transmission unit (MTU) handling, using VXLAN tunnels does not work by default."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:19(para)
+msgid "A simple workaround is to increase the MTU value of the physical interface and physical switch fabric by at least 50 bytes. For example, increase the MTU value to 1550. This value enables an automatic 50-byte MTU difference between the physical interface (1500) and the VXLAN interface (automatically 1500-50 = 1450). An MTU value of 1450 causes issues when virtual machine taps are configured at an MTU value of 1500."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:30(para)
+msgid "Another workaround is to decrease the virtual ethernet devices' MTU. Set the <option>network_device_mtu</option> option to 1450 in the <filename>neutron.conf</filename> file, and set all guest virtual machines' MTU to the same value by using a DHCP option. For information about how to use this option, see <link href=\"http://docs.openstack.org/admin-guide-cloud/content/ch_networking.html#openvswitch_plugin\">Configure OVS plug-in</link>."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:45(title)
+msgid "Modular Layer 2 (ml2) Flat Type configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:50(title)
+msgid "Modular Layer 2 (ml2) GRE Type configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:55(title)
+msgid "Modular Layer 2 (ml2) VLAN Type configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:60(title)
+msgid "Modular Layer 2 (ml2) VXLAN Type configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:65(title)
+msgid "Modular Layer 2 (ml2) Arista Mechanism configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:71(title)
+msgid "Modular Layer 2 (ml2) BigSwitch Mechanism configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:76(title)
+msgid "Modular Layer 2 (ml2) Brocade Mechanism configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:81(title)
+msgid "Modular Layer 2 (ml2) Cisco Mechanism configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:86(title)
+msgid "Modular Layer 2 (ml2) Mellanox Mechanism configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:91(title)
+msgid "Modular Layer 2 (ml2) OpenDaylight Mechanism configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:96(title)
+msgid "Modular Layer 2 (ml2) OpenFlow Mechanism configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:101(title)
+msgid "Modular Layer 2 (ml2) L2 Population Mechanism configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:106(title)
+msgid "Modular Layer 2 (ml2) Tail-f NCS Mechanism configuration options"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-log-files.xml:6(title)
+msgid "Log files used by Networking"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-log-files.xml:7(para)
+msgid "The corresponding log file of each Networking service is stored in the <filename>/var/log/neutron/</filename> directory of the host on which each service runs."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-log-files.xml:11(caption)
+msgid "Log files used by Networking services"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-log-files.xml:16(td) ./doc/config-reference/dashboard/section_dashboard-log-files.xml:19(td) ./doc/config-reference/block-storage/section_cinder-log-files.xml:17(td) ./doc/config-reference/compute/section_nova-log-files.xml:17(td)
+msgid "Log file"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-log-files.xml:19(td)
+msgid "Service/interface"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-log-files.xml:27(filename)
+msgid "dhcp-agent.log"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-log-files.xml:30(systemitem)
+msgid "neutron-dhcp-agent"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-log-files.xml:35(filename)
+msgid "l3-agent.log"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-log-files.xml:38(systemitem)
+msgid "neutron-l3-agent"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-log-files.xml:43(filename)
+msgid "lbaas-agent.log"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-log-files.xml:46(systemitem)
+msgid "neutron-lbaas-agent"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-log-files.xml:48(para)
+msgid "The <systemitem class=\"service\">neutron-lbaas-agent</systemitem> service only runs when Load Balancer as a Service is enabled."
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-log-files.xml:56(filename)
+msgid "linuxbridge-agent.log"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-log-files.xml:59(systemitem)
+msgid "neutron-linuxbridge-agent"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-log-files.xml:64(filename)
+msgid "metadata-agent.log"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-log-files.xml:67(systemitem)
+msgid "neutron-metadata-agent"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-log-files.xml:72(filename)
+msgid "metering-agent.log"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-log-files.xml:75(systemitem)
+msgid "neutron-metering-agent"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-log-files.xml:80(filename)
+msgid "openvswitch-agent.log"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-log-files.xml:83(systemitem)
+msgid "neutron-openvswitch-agent"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-log-files.xml:88(filename)
+msgid "server.log"
+msgstr ""
+
+#: ./doc/config-reference/networking/section_networking-log-files.xml:91(systemitem)
+msgid "neutron-server"
+msgstr ""
+
+#: ./doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml:4(title)
+msgid "Telemetry sample configuration files"
+msgstr ""
+
+#: ./doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml:5(para)
+msgid "All the files in this section can be found in the <filename class=\"directory\">/etc/ceilometer/</filename> directory."
+msgstr ""
+
+#: ./doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml:8(title)
+msgid "ceilometer.conf"
+msgstr ""
+
+#: ./doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml:9(para)
+msgid "The configuration for the Telemetry services and agents is found in the <filename>ceilometer.conf</filename> file."
+msgstr ""
+
+#: ./doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml:11(para) ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:11(para) ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:19(para)
+msgid "This file must be modified after installation."
+msgstr ""
+
+#: ./doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml:18(title)
+msgid "event_definitions.yaml"
+msgstr ""
+
+#: ./doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml:19(para)
+msgid "The <filename>event_definitions.yaml</filename> file defines how events received from other OpenStack components should be translated to Telemetry samples."
+msgstr ""
+
+#: ./doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml:22(para) ./doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml:31(para) ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:26(para)
+msgid "You should not need to modify this file."
+msgstr ""
+
+#: ./doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml:26(title)
+msgid "pipeline.yaml"
+msgstr ""
+
+#: ./doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml:27(para)
+msgid "Pipelines describe a coupling between sources of samples and the corresponding sinks for transformation and publication of these data. They are defined in the <filename>pipeline.yaml</filename> file."
+msgstr ""
+
+#: ./doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml:36(para)
+msgid "The <filename>policy.json</filename> file defines additional access controls that apply to the Telemetry service."
+msgstr ""
+
+#: ./doc/config-reference/identity/section_keystone-sample-conf-files.xml:6(title)
+msgid "Identity service sample configuration files"
+msgstr ""
+
+#: ./doc/config-reference/identity/section_keystone-sample-conf-files.xml:7(para)
+msgid "All the files in this section can be found in the <systemitem>/etc/keystone</systemitem> directory."
+msgstr ""
+
+#: ./doc/config-reference/identity/section_keystone-sample-conf-files.xml:10(title)
+msgid "keystone.conf"
+msgstr ""
+
+#: ./doc/config-reference/identity/section_keystone-sample-conf-files.xml:11(para)
+msgid "The majority of the Identity service configuration is performed from the <filename>keystone.conf</filename> file."
+msgstr ""
+
+#: ./doc/config-reference/identity/section_keystone-sample-conf-files.xml:19(title)
+msgid "keystone-paste.ini"
+msgstr ""
+
+#: ./doc/config-reference/identity/section_keystone-sample-conf-files.xml:20(para)
+msgid "The <filename>keystone-paste.ini</filename> file configures the Web Service Gateway Interface (WSGI) middleware pipeline for the Identity service."
+msgstr ""
+
+#: ./doc/config-reference/identity/section_keystone-sample-conf-files.xml:30(title)
+msgid "logging.conf"
+msgstr ""
+
+#: ./doc/config-reference/identity/section_keystone-sample-conf-files.xml:31(para)
+msgid "A special logging configuration file can be specified in the <filename>keystone.conf</filename> configuration file (for example, <filename>/etc/keystone/logging.conf</filename>). For details, see the Python logging module documentation ( <link href=\"http://docs.python.org/2/howto/logging.html#configuring-logging\">Python Logging</link>)."
+msgstr ""
+
+#: ./doc/config-reference/identity/section_keystone-sample-conf-files.xml:43(para)
+msgid "The <filename>policy.json</filename> file defines additional access controls that apply to the Identity service."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-cors.xml:6(title)
+msgid "Cross-origin resource sharing"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-cors.xml:7(para)
+msgid "Cross-Origin Resource Sharing (CORS) is a mechanism to allow code running in a browser (JavaScript for example) to make requests to a domain other then the one from where it originated. OpenStack Object Storage supports CORS requests to containers and objects within the containers using metadata held on the container."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-cors.xml:11(para)
+msgid "In addition to the metadata on containers, you can use the <option>cors_allow_origin</option> option in the <filename>proxy-server.conf</filename> file to set a list of hosts that are included with any CORS request by default."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:6(title)
+msgid "Object Storage general service configuration"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:7(para)
+msgid "Most Object Storage services fall into two categories, Object Storage's wsgi servers and background daemons."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:11(para)
+msgid "Object Storage uses paste.deploy to manage server configurations. Read more at <link href=\"http://pythonpaste.org/deploy/\">http://pythonpaste.org/deploy/</link>."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:14(para)
+msgid "Default configuration options are set in the `[DEFAULT]` section, and any options specified there can be overridden in any of the other sections when the syntax <literal>set option_name = value</literal> is in place."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:19(para)
+msgid "Configuration for servers and daemons can be expressed together in the same file for each type of server, or separately. If a required section for the service trying to start is missing there will be an error. Sections not used by the service are ignored."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:25(para)
+msgid "Consider the example of an Object Storage node. By convention configuration for the <systemitem class=\"service\">object-server</systemitem>, <systemitem class=\"service\">object-updater</systemitem>, <systemitem class=\"service\">object-replicator</systemitem>, and <systemitem class=\"service\">object-auditor</systemitem> exist in a single file <filename>/etc/swift/object-server.conf</filename>:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:51(para)
+msgid "Object Storage services expect a configuration path as the first argument:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:59(para)
+msgid "If you omit the object-auditor section, this file cannot be used as the configuration path when starting the <placeholder-1/> daemon:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:67(para)
+msgid "If the configuration path is a directory instead of a file all of the files in the directory with the file extension \".conf\" will be combined to generate the configuration object which is delivered to the Object Storage service. This is referred to generally as \"directory-based configuration\"."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:74(para)
+msgid "Directory-based configuration leverages ConfigParser's native multi-file support. Files ending in \".conf\" in the given directory are parsed in lexicographical order. File names starting with '.' are ignored. A mixture of file and directory configuration paths is not supported - if the configuration path is a file, only that file will be parsed."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:82(para)
+msgid "The Object Storage service management tool <filename>swift-init</filename> has adopted the convention of looking for <filename>/etc/swift/{type}-server.conf.d/</filename> if the file <filename>/etc/swift/{type}-server.conf</filename> file does not exist."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:90(para)
+msgid "When using directory-based configuration, if the same option under the same section appears more than once in different files, the last value parsed is said to override previous occurrences. You can ensure proper override precedence by prefixing the files in the configuration directory with numerical values, as in the following example file layout:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:109(para)
+msgid "You can inspect the resulting combined configuration object using the <placeholder-1/> command-line tool."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:113(para)
+msgid "All the services of an Object Store deployment share a common configuration in the <literal>[swift-hash]</literal> section of the <filename>/etc/swift/swift.conf</filename> file. The <option>swift_hash_path_suffix</option> and <option>swift_hash_path_prefix</option> values must be identical on all the nodes."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:6(title)
+msgid "Configure Object Storage features"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:8(title)
+msgid "Object Storage zones"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:9(para)
+msgid "In OpenStack Object Storage, data is placed across different tiers of failure domains. First, data is spread across regions, then zones, then servers, and finally across drives. Data is placed to get the highest failure domain isolation. If you deploy multiple regions, the Object Storage service places the data across the regions. Within a region, each replica of the data should be stored in unique zones, if possible. If there is only one zone, data should be placed on different servers. And if there is only one server, data should be placed on different drives."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:20(para)
+msgid "Regions are widely separated installations with a high-latency or otherwise constrained network link between them. Zones are arbitrarily assigned, and it is up to the administrator of the Object Storage cluster to choose an isolation level and attempt to maintain the isolation level through appropriate zone assignment. For example, a zone may be defined as a rack with a single power source. Or a zone may be a DC room with a common utility provider. Servers are identified by a unique IP/port. Drives are locally attached storage volumes identified by mount point."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:31(para)
+msgid "In small clusters (five nodes or fewer), everything is normally in a single zone. Larger Object Storage deployments may assign zone designations differently; for example, an entire cabinet or rack of servers may be designated as a single zone to maintain replica availability if the cabinet becomes unavailable (for example, due to failure of the top of rack switches or a dedicated circuit). In very large deployments, such as service provider level deployments, each zone might have an entirely autonomous switching and power infrastructure, so that even the loss of an electrical circuit or switching aggregator would result in the loss of a single replica at most."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:45(title)
+msgid "Rackspace zone recommendations"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:46(para)
+msgid "For ease of maintenance on OpenStack Object Storage, Rackspace recommends that you set up at least five nodes. Each node is assigned its own zone (for a total of five zones), which gives you host level redundancy. This enables you to take down a single zone for maintenance and still guarantee object availability in the event that another zone fails during your maintenance."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:54(para)
+msgid "You could keep each server in its own cabinet to achieve cabinet level isolation, but you may wish to wait until your Object Storage service is better established before developing cabinet-level isolation. OpenStack Object Storage is flexible; if you later decide to change the isolation level, you can take down one zone at a time and move them to appropriate new homes."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:62(title)
+msgid "RAID controller configuration"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:63(para)
+msgid "OpenStack Object Storage does not require RAID. In fact, most RAID configurations cause significant performance degradation. The main reason for using a RAID controller is the battery-backed cache. It is very important for data integrity reasons that when the operating system confirms a write has been committed that the write has actually been committed to a persistent location. Most disks lie about hardware commits by default, instead writing to a faster write cache for performance reasons. In most cases, that write cache exists only in non-persistent memory. In the case of a loss of power, this data may never actually get committed to disk, resulting in discrepancies that the underlying file system must handle."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:76(para)
+msgid "OpenStack Object Storage works best on the XFS file system, and this document assumes that the hardware being used is configured appropriately to be mounted with the <placeholder-1/> option. For more information, refer to the XFS FAQ: <link href=\"http://xfs.org/index.php/XFS_FAQ\">http://xfs.org/index.php/XFS_FAQ</link>"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:84(para)
+msgid "To get the most out of your hardware, it is essential that every disk used in OpenStack Object Storage is configured as a standalone, individual RAID 0 disk; in the case of 6 disks, you would have six RAID 0s or one JBOD. Some RAID controllers do not support JBOD or do not support battery backed cache with JBOD. To ensure the integrity of your data, you must ensure that the individual drive caches are disabled and the battery backed cache in your RAID card is configured and used. Failure to configure the controller properly in this case puts data at risk in the case of sudden loss of power."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:96(para)
+msgid "You can also use hybrid drives or similar options for battery backed up cache configurations without a RAID controller."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:102(title)
+msgid "Throttle resources through rate limits"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:103(para)
+msgid "Rate limiting in OpenStack Object Storage is implemented as a pluggable middleware that you configure on the proxy server. Rate limiting is performed on requests that result in database writes to the account and container SQLite databases. It uses memcached and is dependent on the proxy servers having highly synchronized time. The rate limits are limited by the accuracy of the proxy server clocks."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:112(title)
+msgid "Configure rate limiting"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:113(para)
+msgid "All configuration is optional. If no account or container limits are provided, no rate limiting occurs. Available configuration options include:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:119(para)
+msgid "The container rate limits are linearly interpolated from the values given. A sample container rate limiting could be:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:122(para)
+msgid "container_ratelimit_100 = 100"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:123(para)
+msgid "container_ratelimit_200 = 50"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:124(para)
+msgid "container_ratelimit_500 = 20"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:125(para)
+msgid "This would result in:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:127(caption)
+msgid "Values for Rate Limiting with Sample Configuration Settings"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:131(td)
+msgid "Container Size"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:132(td)
+msgid "Rate Limit"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:135(td)
+msgid "0-99"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:136(td)
+msgid "No limiting"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:139(td) ./doc/config-reference/object-storage/section_object-storage-features.xml:140(td)
+msgid "100"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:144(td)
+msgid "150"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:145(td)
+msgid "75"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:148(td)
+msgid "500"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:149(td) ./doc/config-reference/object-storage/section_object-storage-features.xml:153(td)
+msgid "20"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:152(td)
+msgid "1000"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:160(title)
+msgid "Health check"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:161(para)
+msgid "Provides an easy way to monitor whether the Object Storage proxy server is alive. If you access the proxy with the path <filename>/healthcheck</filename>, it responds with <literal>OK</literal> in the response body, which monitoring tools can use."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:169(title)
+msgid "Domain remap"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:170(para)
+msgid "Middleware that translates container and account parts of a domain to path parameters that the proxy server understands."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:178(title)
+msgid "CNAME lookup"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:179(para)
+msgid "Middleware that translates an unknown domain in the host header to something that ends with the configured <code>storage_domain</code> by looking up the given domain's CNAME record in DNS."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:189(title)
+msgid "Temporary URL"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:190(para)
+msgid "Allows the creation of URLs to provide temporary access to objects. For example, a website may wish to provide a link to download a large object in OpenStack Object Storage, but the Object Storage account has no public access. The website can generate a URL that provides GET access for a limited time to the resource. When the web browser user clicks on the link, the browser downloads the object directly from Object Storage, eliminating the need for the website to act as a proxy for the request. If the user shares the link with all his friends, or accidentally posts it on a forum, the direct access is limited to the expiration time set when the website created the link."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:201(literal)
+msgid "temp_url_sig"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:203(para)
+msgid "A cryptographic signature"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:207(literal)
+msgid "temp_url_expires"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:209(para)
+msgid "An expiration date, in Unix time"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:198(para)
+msgid "A temporary URL is the typical URL associated with an object, with two additional query parameters:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:213(para)
+msgid "An example of a temporary URL:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:219(para)
+msgid "To create temporary URLs, first set the <literal>X-Account-Meta-Temp-URL-Key</literal> header on your Object Storage account to an arbitrary string. This string serves as a secret key. For example, to set a key of <literal>b3968d0207b54ece87cccc06515a89d4</literal> using the <placeholder-1/> command-line tool:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:224(replaceable)
+msgid "b3968d0207b54ece87cccc06515a89d4"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:225(para)
+msgid "Next, generate an HMAC-SHA1 (RFC 2104) signature to specify:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:229(para)
+msgid "Which HTTP method to allow (typically <literal>GET</literal> or <literal>PUT</literal>)"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:234(para)
+msgid "The expiry date as a Unix timestamp"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:237(para)
+msgid "The full path to the object"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:240(para)
+msgid "The secret key set as the <literal>X-Account-Meta-Temp-URL-Key</literal>"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:244(para)
+msgid "Here is code generating the signature for a GET for 24 hours on <code>/v1/AUTH_account/container/object</code>:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:259(para)
+msgid "Any alteration of the resource path or query arguments results in a <errorcode>401</errorcode><errortext>Unauthorized</errortext> error. Similarly, a PUT where GET was the allowed method returns a <errorcode>401</errorcode>. HEAD is allowed if GET or PUT is allowed. Using this in combination with browser form post translation middleware could also allow direct-from-browser uploads to specific locations in Object Storage."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:269(para)
+msgid "Changing the <literal>X-Account-Meta-Temp-URL-Key</literal> invalidates any previously generated temporary URLs within 60 seconds (the memcache time for the key). Object Storage supports up to two keys, specified by <literal>X-Account-Meta-Temp-URL-Key</literal> and <literal>X-Account-Meta-Temp-URL-Key-2</literal>. Signatures are checked against both keys, if present. This is to allow for key rotation without invalidating all existing temporary URLs."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:281(para)
+msgid "Opject Storage includes a script called <placeholder-1/> that generates the query parameters automatically:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:288(para)
+msgid "Because this command only returns the path, you must prefix the Object Storage host name (for example, <literal>https://swift-cluster.example.com</literal>)."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:291(para)
+msgid "With GET Temporary URLs, a <literal>Content-Disposition</literal> header is set on the response so that browsers interpret this as a file attachment to be saved. The file name chosen is based on the object name, but you can override this with a <literal>filename</literal> query parameter. The following example specifies a filename of <filename>My Test File.pdf</filename>:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:314(emphasis)
+msgid "tempurl"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:303(para)
+msgid "To enable Temporary URL functionality, edit <filename>/etc/swift/proxy-server.conf</filename> to add <literal>tempurl</literal> to the <literal>pipeline</literal> variable defined in the <literal>[pipeline:main]</literal> section. The <literal>tempurl</literal> entry should appear immediately before the authentication filters in the pipeline, such as <literal>authtoken</literal>, <literal>tempauth</literal> or <literal>keystoneauth</literal>. For example:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:321(title)
+msgid "Name check filter"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:322(para)
+msgid "Name Check is a filter that disallows any paths that contain defined forbidden characters or that exceed a defined length."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:330(title)
+msgid "Constraints"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:331(para)
+msgid "To change the OpenStack Object Storage internal limits, update the values in the <literal>swift-constraints</literal> section in the <filename>swift.conf</filename> file. Use caution when you update these values because they affect the performance in the entire cluster."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:342(title)
+msgid "Cluster health"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:343(para)
+msgid "Use the <placeholder-1/> tool to measure overall cluster health. This tool checks if a set of deliberately distributed containers and objects are currently in their proper places within the cluster. For instance, a common deployment has three replicas of each object. The health of that object can be measured by checking if each replica is in its proper place. If only 2 of the 3 is in place the object’s health can be said to be at 66.66%, where 100% would be perfect. A single object’s health, especially an older object, usually reflects the health of that entire partition the object is in. If you make enough objects on a distinct percentage of the partitions in the cluster,you get a good estimate of the overall cluster health. In practice, about 1% partition coverage seems to balance well between accuracy and the amount of time it takes to gather results. The first thing that needs to be done to provide this health value is create a new account solely for this usage. Next, you need to place the containers and objects throughout the system so that they are on distinct partitions. The <placeholder-2/> tool does this by making up random container and object names until they fall on distinct partitions. Last, and repeatedly for the life of the cluster, you must run the <placeholder-3/> tool to check the health of each of these containers and objects. These tools need direct access to the entire cluster and to the ring files (installing them on a proxy server suffices). The <placeholder-4/> and <placeholder-5/> commands both use the same configuration file, <filename>/etc/swift/dispersion.conf</filename>. Example <filename>dispersion.conf</filename> file:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:384(para)
+msgid "There are also configuration options for specifying the dispersion coverage, which defaults to 1%, retries, concurrency, and so on. However, the defaults are usually fine. Once the configuration is in place, run <placeholder-1/> to populate the containers and objects throughout the cluster. Now that those containers and objects are in place, you can run <placeholder-2/> to get a dispersion report, or the overall health of the cluster. Here is an example of a cluster in perfect health:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:404(para)
+msgid "Now, deliberately double the weight of a device in the object ring (with replication turned off) and re-run the dispersion report to show what impact that has:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:420(para)
+msgid "You can see the health of the objects in the cluster has gone down significantly. Of course, this test environment has just four devices, in a production environment with many devices the impact of one device change is much less. Next, run the replicators to get everything put back into place and then rerun the dispersion report:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:437(para)
+msgid "Alternatively, the dispersion report can also be output in json format. This allows it to be more easily consumed by third-party utilities:"
+msgstr ""
+
+#. Usage documented in http://docs.openstack.org/developer/swift/overview_large_objects.html
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:451(title)
+msgid "Static Large Object (SLO) support"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:452(para)
+msgid "This feature is very similar to Dynamic Large Object (DLO) support in that it enables the user to upload many objects concurrently and afterwards download them as a single object. It is different in that it does not rely on eventually consistent container listings to do so. Instead, a user-defined manifest of the object segments is used."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:464(title)
+msgid "Container quotas"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:465(para)
+msgid "The <code>container_quotas</code> middleware implements simple quotas that can be imposed on Object Storage containers by a user with the ability to set container metadata, most likely the account administrator. This can be useful for limiting the scope of containers that are delegated to non-admin users, exposed to formpost uploads, or just as a self-imposed sanity check."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:470(para)
+msgid "Any object PUT operations that exceed these quotas return a 413 response (request entity too large) with a descriptive body."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:473(para)
+msgid "Quotas are subject to several limitations: eventual consistency, the timeliness of the cached container_info (60 second ttl by default), and it is unable to reject chunked transfer uploads that exceed the quota (though once the quota is exceeded, new chunked transfers are refused)."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:479(para)
+msgid "Set quotas by adding meta values to the container. These values are validated when you set them:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:483(para)
+msgid "X-Container-Meta-Quota-Bytes: Maximum size of the container, in bytes."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:487(para)
+msgid "X-Container-Meta-Quota-Count: Maximum object count of the container."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:496(title)
+msgid "Account quotas"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:497(para)
+msgid "The <parameter>x-account-meta-quota-bytes</parameter> metadata entry must be requests (PUT, POST) if a given account quota (in bytes) is exceeded while DELETE requests are still allowed."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:501(para)
+msgid "The <parameter>x-account-meta-quota-bytes</parameter> metadata entry must be set to store and enable the quota. Write requests to this metadata entry are only permitted for resellers. There is no account quota limitation on a reseller account even if <parameter>x-account-meta-quota-bytes</parameter> is set."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:508(para)
+msgid "Any object PUT operations that exceed the quota return a 413 response (request entity too large) with a descriptive body."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:511(para)
+msgid "The following command uses an admin account that own the Reseller role to set a quota on the test account:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:515(para)
+msgid "Here is the stat listing of an account where quota has been set:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:525(para)
+msgid "This command removes the account quota:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:529(title)
+msgid "Bulk delete"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:530(para)
+msgid "Use <code>bulk-delete</code> to delete multiple files from an account with a single request. Responds to DELETE requests with a header 'X-Bulk-Delete: true_value'. The body of the DELETE request is a new line-separated list of files to delete. The files listed must be URL encoded and in the form:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:540(para)
+msgid "If all files are successfully deleted (or did not exist), the operation returns <code>HTTPOk</code>. If any files failed to delete, the operation returns <code>HTTPBadGateway</code>. In both cases, the response body is a JSON dictionary that shows the number of files that were successfully deleted or not found. The files that failed are listed."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:553(title)
+msgid "Drive audit"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:554(para)
+msgid "The <option>swift-drive-audit</option> configuration items reference a script that can be run by using <placeholder-1/> to watch for bad drives. If errors are detected, it unmounts the bad drive, so that OpenStack Object Storage can work around it. It takes the following options:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:565(title)
+msgid "Form post"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:566(para)
+msgid "Middleware that provides the ability to upload objects to a cluster using an HTML form POST. The format of the form is:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:581(para)
+msgid "The <literal>swift-url</literal> is the URL to the Object Storage destination, such as: <uri>https://swift-cluster.example.com/v1/AUTH_account/container/object_prefix</uri> The name of each file uploaded is appended to the specified <literal>swift-url</literal>. So, you can upload directly to the root of container with a URL like: <uri>https://swift-cluster.example.com/v1/AUTH_account/container/</uri> Optionally, you can include an object prefix to better separate different users’ uploads, such as: <uri>https://swift-cluster.example.com/v1/AUTH_account/container/object_prefix</uri>"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:591(para)
+msgid "The form method must be POST and the enctype must be set as <literal>multipart/form-data</literal>."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:594(para)
+msgid "The redirect attribute is the URL to redirect the browser to after the upload completes. The URL has status and message query parameters added to it, indicating the HTTP status code for the upload (2xx is success) and a possible message for further information if there was an error (such as <literal>“max_file_size exceeded”</literal>)."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:601(para)
+msgid "The <literal>max_file_size</literal> attribute must be included and indicates the largest single file upload that can be done, in bytes."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:604(para)
+msgid "The <literal>max_file_count</literal> attribute must be included and indicates the maximum number of files that can be uploaded with the form. Include additional <code>&lt;![CDATA[&lt;input type=\"file\" name=\"filexx\"/&gt;]]&gt;</code> attributes if desired."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:610(para)
+msgid "The expires attribute is the Unix timestamp before which the form must be submitted before it is invalidated."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:613(para)
+msgid "The signature attribute is the HMAC-SHA1 signature of the form. This sample Python code shows how to compute the signature:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:630(para)
+msgid "The key is the value of the <literal>X-Account-Meta-Temp-URL-Key</literal> header on the account."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:633(para)
+msgid "Be certain to use the full path, from the <literal>/v1/</literal> onward."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:635(para)
+msgid "The command-line tool <placeholder-1/> may be used (mostly just when testing) to compute expires and signature."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:639(para)
+msgid "The file attributes must appear after the other attributes to be processed correctly. If attributes come after the file, they are not sent with the sub-request because on the server side, all attributes in the file cannot be parsed unless the whole file is read into memory and the server does not have enough memory to service these requests. So, attributes that follow the file are ignored."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:652(title)
+msgid "Static web sites"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-features.xml:653(para)
+msgid "When configured, this middleware serves container data as a static web site with index file and error file resolution and optional file listings. This mode is normally only active for anonymous requests."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_configure_s3.xml:6(title)
+msgid "Configure Object Storage with the S3 API"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_configure_s3.xml:7(para)
+msgid "The Swift3 middleware emulates the S3 REST API on top of Object Storage."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_configure_s3.xml:9(para)
+msgid "The following operations are currently supported:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_configure_s3.xml:12(para)
+msgid "GET Service"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_configure_s3.xml:15(para)
+msgid "DELETE Bucket"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_configure_s3.xml:18(para)
+msgid "GET Bucket (List Objects)"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_configure_s3.xml:21(para)
+msgid "PUT Bucket"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_configure_s3.xml:24(para)
+msgid "DELETE Object"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_configure_s3.xml:27(para)
+msgid "GET Object"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_configure_s3.xml:30(para)
+msgid "HEAD Object"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_configure_s3.xml:33(para)
+msgid "PUT Object"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_configure_s3.xml:36(para)
+msgid "PUT Object (Copy)"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_configure_s3.xml:39(para)
+msgid "To use this middleware, first download the latest version from its repository to your proxy server(s)."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_configure_s3.xml:43(para)
+msgid "Then, install it using standard python mechanisms, such as:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_configure_s3.xml:46(para)
+msgid "Alternatively, if you have configured the Ubuntu Cloud Archive, you may use: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_configure_s3.xml:49(para)
+msgid "To add this middleware to your configuration, add the <systemitem>swift3</systemitem> middleware in front of the <systemitem>swauth</systemitem> middleware, and before any other middleware that look at Object Storage requests (like rate limiting)."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_configure_s3.xml:52(para)
+msgid "Ensure that your <filename>proxy-server.conf</filename> file contains <systemitem>swift3</systemitem> in the pipeline and the <code>[filter:swift3]</code> section, as shown below:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_configure_s3.xml:60(para)
+msgid "Next, configure the tool that you use to connect to the S3 API. For S3curl, for example, you must add your host IP information by adding your host IP to the @endpoints array (line 33 in s3curl.pl):"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_configure_s3.xml:65(para)
+msgid "Now you can send commands to the endpoint, such as:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_configure_s3.xml:68(para)
+msgid "To set up your client, ensure you are using the ec2 credentials, which can be downloaded from the <guilabel>API Endpoints</guilabel> tab of the dashboard. The host should also point to the Object Storage storage node's hostname. It also will have to use the old-style calling format, and not the hostname-based container format. Here is an example client setup using the Python boto library on a locally installed all-in-one Object Storage installation."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:6(title)
+msgid "Endpoint listing middleware"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:7(para)
+msgid "The endpoint listing middleware enables third-party services that use data locality information to integrate with OpenStack Object Storage. This middleware reduces network overhead and is designed for third-party services that run inside the firewall. Deploy this middleware on a proxy server because usage of this middleware is not authenticated."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:11(para)
+msgid "Format requests for endpoints, as follows:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:12(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:13(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:14(replaceable)
+msgid "{account}"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:12(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:13(replaceable)
+msgid "{container}"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:12(replaceable)
+msgid "{object}"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:15(para)
+msgid "Use the <option>list_endpoints_path</option> configuration option in the <filename>proxy_server.conf</filename> file to customize the <literal>/endpoints/</literal> path."
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:18(para)
+msgid "Responses are JSON-encoded lists of endpoints, as follows:"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:20(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:21(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:22(replaceable)
+msgid "{server}"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:20(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:21(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:22(replaceable)
+msgid "{port}"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:20(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:21(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:22(replaceable)
+msgid "{dev}"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:20(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:21(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:22(replaceable)
+msgid "{part}"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:20(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:21(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:22(replaceable)
+msgid "{acc}"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:20(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:21(replaceable)
+msgid "{cont}"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:20(replaceable)
+msgid "{obj}"
+msgstr ""
+
+#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:23(para)
+msgid "An example response is:"
+msgstr ""
+
+#: ./doc/config-reference/dashboard/section_dashboard-sample-configuration-files.xml:6(title) ./doc/config-reference/compute/section_compute-sample-configuration-files.xml:4(title)
+msgid "Additional sample configuration files"
+msgstr ""
+
+#: ./doc/config-reference/dashboard/section_dashboard-sample-configuration-files.xml:7(para)
+msgid "Find the following files in <systemitem>/etc/openstack-dashboard</systemitem>."
+msgstr ""
+
+#: ./doc/config-reference/dashboard/section_dashboard-sample-configuration-files.xml:9(title)
+msgid "keystone_policy.json"
+msgstr ""
+
+#: ./doc/config-reference/dashboard/section_dashboard-sample-configuration-files.xml:10(para)
+msgid "The <filename>keystone_policy.json</filename> file defines additional access controls for the dashboard that apply to the Identity service."
+msgstr ""
+
+#: ./doc/config-reference/dashboard/section_dashboard-sample-configuration-files.xml:14(para)
+msgid "The <filename>keystone_policy.json</filename> file must match the Identity service <filename>/etc/keystone/policy.json</filename> policy file."
+msgstr ""
+
+#: ./doc/config-reference/dashboard/section_dashboard-sample-configuration-files.xml:22(title)
+msgid "nova_policy.json"
+msgstr ""
+
+#: ./doc/config-reference/dashboard/section_dashboard-sample-configuration-files.xml:23(para)
+msgid "The <filename>nova_policy.json</filename> file defines additional access controls for the dashboard that apply to the Compute service."
+msgstr ""
+
+#: ./doc/config-reference/dashboard/section_dashboard-sample-configuration-files.xml:27(para)
+msgid "The <filename>nova_policy.json</filename> file must match the Compute <filename>/etc/nova/policy.json</filename> policy file."
+msgstr ""
+
+#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:6(title)
+msgid "Log files used by the dashboard"
+msgstr ""
+
+#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:7(para)
+msgid "The dashboard is served to users through the Apache web server (<systemitem>httpd</systemitem>). As a result, logs relating to the dashboard appear in the following files in the <filename>/var/log/httpd</filename> or <filename>/var/log/apache2</filename> directory of where the dashboard is hosted."
+msgstr ""
+
+#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:14(caption)
+msgid "Log files used by the dashboard/httpd"
+msgstr ""
+
+#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:22(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:309(th) ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:80(th) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:322(td) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:206(th) ./doc/config-reference/block-storage/drivers/coraid-driver.xml:358(th) ./doc/config-reference/compute/section_compute-scheduler.xml:614(th) ./doc/config-reference/compute/section_compute-scheduler.xml:695(th)
+msgid "Description"
+msgstr ""
+
+#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:30(filename)
+msgid "access_log"
+msgstr ""
+
+#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:32(td)
+msgid "This file logs all attempts to access the web server."
+msgstr ""
+
+#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:38(filename)
+msgid "error_log"
+msgstr ""
+
+#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:40(td)
+msgid "This file logs all unsuccessful attempts to access the web server, along with the reason each attempt/request failed."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_misc.xml:6(title)
+msgid "Additional options"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_misc.xml:8(para)
+msgid "These options can also be set in the <filename>cinder.conf</filename> file."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:6(title)
+msgid "Log files used by Block Storage"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:7(para)
+msgid "The corresponding log file of each Block Storage service is stored in the <filename>/var/log/cinder/</filename> directory of the host on which each service runs."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:11(caption)
+msgid "Log files used by Block Storage services"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:20(td)
+msgid "Service/interface (for CentOS, Fedora, openSUSE, Red Hat Enterprise Linux, and SUSE Linux Enterprise)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:24(td)
+msgid "Service/interface (for Ubuntu and Debian)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:32(filename) ./doc/config-reference/compute/section_nova-log-files.xml:32(filename)
+msgid "api.log"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:35(systemitem)
+msgid "openstack-cinder-api"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:38(systemitem)
+msgid "cinder-api"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:43(filename)
+msgid "cinder-manage.log"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:46(systemitem) ./doc/config-reference/block-storage/section_cinder-log-files.xml:49(systemitem)
+msgid "cinder-manage"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:54(filename) ./doc/config-reference/compute/section_nova-log-files.xml:119(filename)
+msgid "scheduler.log"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:57(systemitem)
+msgid "openstack-cinder-scheduler"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:60(systemitem)
+msgid "cinder-scheduler"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:65(filename)
+msgid "volume.log"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:68(systemitem)
+msgid "openstack-cinder-volume"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:71(systemitem) ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:179(systemitem)
+msgid "cinder-volume"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_fc-zoning.xml:4(title)
+msgid "Fibre Channel Zone Manager"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_fc-zoning.xml:5(para)
+msgid "The Fibre Channel Zone Manager allows FC SAN Zone/Access control management in conjunction with Fibre Channel block storage. The configuration of Fibre Channel Zone Manager and various zone drivers are described in this section."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_fc-zoning.xml:10(title)
+msgid "Configure Block Storage to use Fibre Channel Zone Manager"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_fc-zoning.xml:12(para)
+msgid "If Block Storage is configured to use a Fibre Channel volume driver that supports Zone Manager, update <filename>cinder.conf</filename> to add the following configuration options to enable Fibre Channel Zone Manager."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_fc-zoning.xml:17(para) ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:305(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:375(para)
+msgid "Make the following changes in the <filename>/etc/cinder/cinder.conf</filename> file."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_fc-zoning.xml:21(para)
+msgid "To use different Fibre Channel Zone Drivers, use the parameters described in this section."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_fc-zoning.xml:24(para)
+msgid "When multi backend configuration is used, provide the <option>zoning_mode</option> configuration option as part of the volume driver configuration where <option>volume_driver</option> option is specified."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_fc-zoning.xml:30(para)
+msgid "Default value of <option>zoning_mode</option> is <literal>None</literal> and this needs to be changed to <literal>fabric</literal> to allow fabric zoning."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_fc-zoning.xml:35(para)
+msgid "<option>zoning_policy</option> can be configured as <literal>initiator-target</literal> or <literal>initiator</literal>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_fc-zoning.xml:42(title)
+msgid "Brocade Fibre Channel Zone Driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_fc-zoning.xml:43(para)
+msgid "Brocade Fibre Channel Zone Driver performs zoning operations via SSH. Configure Brocade Zone Driver and lookup service by specifying the following parameters:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_fc-zoning.xml:47(para)
+msgid "Configure SAN fabric parameters in the form of fabric groups as described in the example below:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_fc-zoning.xml:51(para)
+msgid "Define a fabric group for each fabric using the fabric names used in <option>fc_fabric_names</option> configuration option as group name."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_fc-zoning.xml:57(title) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:23(title) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:15(title) ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:16(title) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:42(title) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:16(title)
+msgid "System requirements"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_fc-zoning.xml:58(para)
+msgid "Brocade Fibre Channel Zone Driver requires firmware version FOS v6.4 or higher."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_fc-zoning.xml:60(para)
+msgid "As a best practice for zone management, use a user account with <literal>zoneadmin</literal> role. Users with <literal>admin</literal> role (including the default <literal>admin</literal> user account) are limited to a maximum of two concurrent SSH sessions."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_fc-zoning.xml:66(para)
+msgid "For information about how to manage Brocade Fibre Channel switches, see the Brocade Fabric OS user documentation."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_backup-drivers.xml:6(title)
+msgid "Backup drivers"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_backup-drivers.xml:7(para)
+msgid "This section describes how to configure the <systemitem class=\"service\">cinder-backup</systemitem> service and its drivers."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_backup-drivers.xml:10(para)
+msgid "The volume drivers are included with the Block Storage repository (<link href=\"https://github.com/openstack/cinder\">https://github.com/openstack/cinder</link>). To set a backup driver, use the <literal>backup_driver</literal> flag. By default there is no backup driver enabled."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:6(title)
+msgid "Introduction to the Block Storage service"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:7(para)
+msgid "The OpenStack Block Storage service provides persistent block storage resources that OpenStack Compute instances can consume. This includes secondary attached storage similar to the Amazon Elastic Block Storage (EBS) offering. In addition, you can write images to a Block Storage device for Compute to use as a bootable persistent instance."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:11(para)
+msgid "The Block Storage service differs slightly from the Amazon EBS offering. The Block Storage service does not provide a shared storage solution like NFS. With the Block Storage service, you can attach a device to only one instance."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:14(para)
+msgid "The Block Storage service provides:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:17(para)
+msgid "<systemitem class=\"service\">cinder-api</systemitem>. A WSGI app that authenticates and routes requests throughout the Block Storage service. It supports the OpenStack APIs only, although there is a translation that can be done through Compute's EC2 interface, which calls in to the Block Storage client."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:23(para)
+msgid "<systemitem class=\"service\">cinder-scheduler</systemitem>. Schedules and routes requests to the appropriate volume service. Depending upon your configuration, this may be simple round-robin scheduling to the running volume services, or it can be more sophisticated through the use of the Filter Scheduler. The Filter Scheduler is the default and enables filters on things like Capacity, Availability Zone, Volume Types, and Capabilities as well as custom filters."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:31(para)
+msgid "<systemitem class=\"service\">cinder-volume</systemitem>. Manages Block Storage devices, specifically the back-end devices themselves."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:36(para)
+msgid "<systemitem class=\"service\">cinder-backup</systemitem>. Provides a means to back up a Block Storage volume to OpenStack Object Storage (swift)."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:41(para)
+msgid "The Block Storage service contains the following components:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:44(para)
+msgid "<emphasis role=\"bold\">Back-end Storage Devices</emphasis>. The Block Storage service requires some form of back-end storage that the service is built on. The default implementation is to use LVM on a local volume group named \"cinder-volumes.\" In addition to the base driver implementation, the Block Storage service also provides the means to add support for other storage devices to be utilized such as external Raid Arrays or other storage appliances. These back-end storage devices may have custom block sizes when using KVM or QEMU as the hypervisor."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:53(para)
+msgid "<emphasis role=\"bold\">Users and Tenants (Projects)</emphasis>. The Block Storage service can be used by many different cloud computing consumers or customers (tenants on a shared system), using role-based access assignments. Roles control the actions that a user is allowed to perform. In the default configuration, most actions do not require a particular role, but this can be configured by the system administrator in the appropriate <filename>policy.json</filename> file that maintains the rules. A user's access to particular volumes is limited by tenant, but the username and password are assigned per user. Key pairs granting access to a volume are enabled per user, but quotas to control resource consumption across available hardware resources are per tenant."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:63(para)
+msgid "For tenants, quota controls are available to limit:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:67(para)
+msgid "The number of volumes that can be created."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:71(para)
+msgid "The number of snapshots that can be created."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:75(para)
+msgid "The total number of GBs allowed per tenant (shared between snapshots and volumes)."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:79(para)
+msgid "You can revise the default quota values with the Block Storage CLI, so the limits placed by quotas are editable by admin users."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:83(para)
+msgid "<emphasis role=\"bold\">Volumes, Snapshots, and Backups</emphasis>. The basic resources offered by the Block Storage service are volumes and snapshots which are derived from volumes and volume backups:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:88(para)
+msgid "<emphasis role=\"bold\">Volumes</emphasis>. Allocated block storage resources that can be attached to instances as secondary storage or they can be used as the root store to boot instances. Volumes are persistent R/W block storage devices most commonly attached to the compute node through iSCSI."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:97(para)
+msgid "<emphasis role=\"bold\">Snapshots</emphasis>. A read-only point in time copy of a volume. The snapshot can be created from a volume that is currently in use (through the use of <option>--force True</option>) or in an available state. The snapshot can then be used to create a new volume through create from snapshot."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:104(para)
+msgid "<emphasis role=\"bold\">Backups</emphasis>. An archived copy of a volume currently stored in OpenStack Object Storage (swift)."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_volume-drivers.xml:6(title)
+msgid "Volume drivers"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_volume-drivers.xml:7(para)
+msgid "To use different volume drivers for the <systemitem class=\"service\">cinder-volume</systemitem> service, use the parameters described in these sections."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_volume-drivers.xml:10(para)
+msgid "The volume drivers are included in the Block Storage repository (<link href=\"https://github.com/openstack/cinder\">https://github.com/openstack/cinder</link>). To set a volume driver, use the <literal>volume_driver</literal> flag. The default is:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_block-storage-sample-configuration-files.xml:4(title)
+msgid "Block Storage sample configuration files"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_block-storage-sample-configuration-files.xml:5(para)
+msgid "All the files in this section can be found in <systemitem>/etc/cinder</systemitem>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_block-storage-sample-configuration-files.xml:7(title) ./doc/config-reference/block-storage/drivers/coraid-driver.xml:373(filename)
+msgid "cinder.conf"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_block-storage-sample-configuration-files.xml:8(para)
+msgid "Use the <filename>cinder.conf</filename> file to configure the majority of the Block Storage service options."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_block-storage-sample-configuration-files.xml:16(para)
+msgid "Use the <filename>api-paste.ini</filename> file to configure the Block Storage API service."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_block-storage-sample-configuration-files.xml:23(para)
+msgid "The <filename>policy.json</filename> file defines additional access controls that apply to the Block Storage service."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/section_block-storage-sample-configuration-files.xml:28(para)
+msgid "The <filename>rootwrap.conf</filename> file defines configuration values used by the <placeholder-1/> script when the Block Storage service must escalate its privileges to those of the root user."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:6(title)
+msgid "Huawei storage driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:7(para)
+msgid "The Huawei driver supports the iSCSI and Fibre Channel connections and enables OceanStor T series unified storage, OceanStor Dorado high-performance storage, and OceanStor HVS high-end storage to provide block storage services for OpenStack."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:11(title) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:34(title) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:24(title) ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:42(title) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:66(title) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:325(title) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:33(title) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:231(title)
+msgid "Supported operations"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:15(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:46(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:72(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:91(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:38(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:28(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:36(para) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:236(para)
+msgid "Create volume"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:18(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:49(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:75(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:94(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:41(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:31(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:39(para)
+msgid "Delete volume"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:21(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:52(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:78(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:97(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:44(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:34(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:42(para)
+msgid "Attach volume"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:24(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:55(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:81(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:100(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:47(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:37(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:45(para) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:257(para)
+msgid "Detach volume"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:27(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:58(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:103(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:50(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:46(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:48(para)
+msgid "Create snapshot"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:30(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:61(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:106(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:53(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:49(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:51(para)
+msgid "Delete snapshot"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:33(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:109(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:68(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:58(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:54(para) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:244(para)
+msgid "Create volume from snapshot"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:36(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:112(para)
+msgid "Create clone volume"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:39(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:64(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:84(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:115(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:59(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:52(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:60(para)
+msgid "Copy image to volume"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:42(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:67(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:87(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:118(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:62(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:55(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:63(para)
+msgid "Copy volume to image"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:12(para)
+msgid "OceanStor T series unified storage supports the following operations:<placeholder-1/>OceanStor Dorado5100 supports the following operations:<placeholder-2/>OceanStor Dorado2100 G2 supports the following operations:<placeholder-3/>OceanStor HVS supports the following operations:<placeholder-4/>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:123(title)
+msgid "Configure Cinder nodes"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:124(para)
+msgid "In <filename>/etc/cinder</filename>, create the driver configuration file named <filename>cinder_huawei_conf.xml</filename>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:127(para)
+msgid "You must configure <option>Product</option> and <option>Protocol</option> to specify a storage system and link type. The following uses the iSCSI driver as an example. The driver configuration file of OceanStor T series unified storage is shown as follows:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:158(para)
+msgid "The driver configuration file of OceanStor Dorado5100 is shown as follows:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:184(para)
+msgid "The driver configuration file of OceanStor Dorado2100 G2 is shown as follows:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:208(para)
+msgid "The driver configuration file of OceanStor HVS is shown as follows:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:234(para)
+msgid "You do not need to configure the iSCSI target IP address for the Fibre Channel driver. In the prior example, delete the iSCSI configuration:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:244(para)
+msgid "To add <option>volume_driver</option> and <option>cinder_huawei_conf_file</option> items, you can modify the <filename>cinder.conf</filename> configuration file as follows:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:250(para)
+msgid "You can configure multiple Huawei back-end storages as follows:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:261(para)
+msgid "OceanStor HVS storage system supports the QoS function. You must create a QoS policy for the HVS storage system and create the volume type to enable QoS as follows:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:270(para)
+msgid "<option>OpenStack_QoS_high</option> is a QoS policy created by a user for the HVS storage system. <option>QoS_high</option> is the self-defined volume type. Set the <option>io_priority</option> option to <literal>high</literal>, <literal>normal</literal>, or <literal>low</literal>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:278(para)
+msgid "OceanStor HVS storage system supports the SmartTier function. SmartTier has three tiers. You can create the volume type to enable SmartTier as follows:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:286(para)
+msgid "<option>distribute_policy</option> and <option>transfer_strategy</option> can only be set to <literal>high</literal>, <literal>normal</literal>, or <literal>low</literal>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:293(title)
+msgid "Configuration file details"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:294(para)
+msgid "This table describes the Huawei storage driver configuration options:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:297(caption)
+msgid "Huawei storage driver configuration options"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:306(th) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:203(th)
+msgid "Flag name"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:307(th) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:320(td) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:204(th)
+msgid "Type"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:308(th) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:321(td) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:205(th)
+msgid "Default"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:315(option)
+msgid "Product"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:318(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:332(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:343(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:355(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:367(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:379(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:394(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:499(td) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:329(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:337(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:394(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:406(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:423(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:434(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:213(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:228(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:266(para)
+msgid "Required"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:324(para)
+msgid "Type of a storage product. Valid values are <literal>T</literal>, <literal>Dorado</literal>, or <literal>HVS</literal>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:331(option)
+msgid "Protocol"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:337(literal) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:416(para)
+msgid "iSCSI"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:338(literal)
+msgid "FC"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:336(td)
+msgid "Type of a protocol. Valid values are <placeholder-1/> or <placeholder-2/>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:342(option)
+msgid "ControllerIP0"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:347(td)
+msgid "IP address of the primary controller (not required for the HVS)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:352(option)
+msgid "ControllerIP1"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:361(para)
+msgid "IP address of the secondary controller (not required for the HVS)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:366(option)
+msgid "HVSURL"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:371(td)
+msgid "Access address of the Rest port (required only for the HVS)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:376(option)
+msgid "UserName"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:385(para)
+msgid "User name of an administrator"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:390(option)
+msgid "UserPassword"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:400(para)
+msgid "Password of an administrator"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:405(option)
+msgid "LUNType"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:408(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:425(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:443(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:461(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:474(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:489(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:511(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:522(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:532(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:543(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:551(td) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:345(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:357(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:367(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:379(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:445(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:456(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:221(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:275(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:299(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:310(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:334(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:345(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:366(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:384(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:394(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:415(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:426(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:436(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:452(para)
+msgid "Optional"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:411(para)
+msgid "Thin"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:414(para)
+msgid "Type of a created LUN. Valid values are <literal>Thick</literal> or <literal>Thin</literal>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:421(option)
+msgid "StripUnitSize"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:428(para)
+msgid "64"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:431(para)
+msgid "Stripe depth of a created LUN. The value is expressed in KB."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:433(para)
+msgid "This flag is not valid for a thin LUN."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:439(option)
+msgid "WriteType"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:446(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:464(para)
+msgid "1"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:449(para)
+msgid "Cache write method. The method can be write back, write through, or Required write back. The default value is <literal>1</literal>, indicating write back."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:458(option)
+msgid "MirrorSwitch"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:467(para)
+msgid "Cache mirroring policy. The default value is <literal>1</literal>, indicating that a mirroring policy is used."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:473(option)
+msgid "Prefetch Type"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:476(para)
+msgid "3"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:479(para)
+msgid "Cache prefetch strategy. The strategy can be constant prefetch, variable prefetch, or intelligent prefetch. Default value is <literal>3</literal>, which indicates intelligent prefetch and is not required for the HVS."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:488(option)
+msgid "Prefetch Value"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:491(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:446(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:385(para)
+msgid "0"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:494(para)
+msgid "Cache prefetch value."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:498(option)
+msgid "StoragePool"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:504(para)
+msgid "Name of a storage pool that you want to use. Not required for the Dorado2100 G2."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:510(option)
+msgid "DefaultTargetIP"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:516(para)
+msgid "Default IP address of the iSCSI port provided for compute nodes."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:521(option)
+msgid "Initiator Name"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:527(para)
+msgid "Name of a compute node initiator."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:531(option)
+msgid "Initiator TargetIP"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:537(para)
+msgid "IP address of the iSCSI port provided for compute nodes."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:542(option)
+msgid "OSType"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:545(para)
+msgid "Linux"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:547(td)
+msgid "The OS type for a compute node."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:550(option)
+msgid "HostIP"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:555(td)
+msgid "The IPs for compute nodes."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:562(para)
+msgid "You can configure one iSCSI target port for each or all compute nodes. The driver checks whether a target port IP address is configured for the current compute node. If not, select <option>DefaultTargetIP</option>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:569(para)
+msgid "You can configure multiple storage pools in one configuration file, which supports the use of multiple storage pools in a storage system. (HVS allows configuration of only one storage pool.)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:576(para)
+msgid "For details about LUN configuration information, see the <placeholder-1/> command in the command-line interface (CLI) documentation or run the <placeholder-2/> on the storage system CLI."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:585(para)
+msgid "After the driver is loaded, the storage system obtains any modification of the driver configuration file in real time and you do not need to restart the <systemitem class=\"service\">cinder-volume</systemitem> service."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:4(title)
+msgid "IBM GPFS volume driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:5(para)
+msgid "IBM General Parallel File System (GPFS) is a cluster file system that provides concurrent access to file systems from multiple nodes. The storage provided by these nodes can be direct attached, network attached, SAN attached, or a combination of these methods. GPFS provides many features beyond common data access, including data replication, policy based storage management, and space efficient file snapshot and clone operations."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:14(title)
+msgid "How the GPFS driver works"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:15(para)
+msgid "The GPFS driver enables the use of GPFS in a fashion similar to that of the NFS driver. With the GPFS driver, instances do not actually access a storage device at the block level. Instead, volume backing files are created in a GPFS file system and mapped to instances, which emulate a block device."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:23(para)
+msgid "GPFS software must be installed and running on nodes where Block Storage and Compute services run in the OpenStack environment. A GPFS file system must also be created and mounted on these nodes before starting the <literal>cinder-volume</literal> service. The details of these GPFS specific steps are covered in <citetitle>GPFS: Concepts, Planning, and Installation Guide</citetitle> and <citetitle>GPFS: Administration and Programming Reference</citetitle>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:35(para)
+msgid "Optionally, the Image Service can be configured to store images on a GPFS file system. When a Block Storage volume is created from an image, if both image data and volume data reside in the same GPFS file system, the data from image file is moved efficiently to the volume file using copy-on-write optimization strategy."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:43(title)
+msgid "Enable the GPFS driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:44(para)
+msgid "To use the Block Storage service with the GPFS driver, first set the <literal>volume_driver</literal> in <filename>cinder.conf</filename>:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:48(para)
+msgid "The following table contains the configuration options supported by the GPFS driver."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:53(para)
+msgid "The <literal>gpfs_images_share_mode</literal> flag is only valid if the Image Service is configured to use GPFS with the <literal>gpfs_images_dir</literal> flag. When the value of this flag is <literal>copy_on_write</literal>, the paths specified by the <literal>gpfs_mount_point_base</literal> and <literal>gpfs_images_dir</literal> flags must both reside in the same GPFS file system and in the same GPFS file set."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:66(title)
+msgid "Volume creation options"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:67(para)
+msgid "It is possible to specify additional volume configuration options on a per-volume basis by specifying volume metadata. The volume is created using the specified options. Changing the metadata after the volume is created has no effect. The following table lists the volume creation options supported by the GPFS volume driver."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:75(caption)
+msgid "Volume Create Options for GPFS Volume Drive"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:79(th)
+msgid "Metadata Item Name"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:85(literal) ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:98(literal) ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:99(literal)
+msgid "fstype"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:88(literal)
+msgid "fstype=swap"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:86(td)
+msgid "Specifies whether to create a file system or a swap area on the new volume. If <placeholder-1/> is specified, the mkswap command is used to create a swap area. Otherwise the mkfs command is passed the specified file system type, for example ext3, ext4 or ntfs."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:96(literal)
+msgid "fslabel"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:97(td)
+msgid "Sets the file system label for the file system specified by <placeholder-1/> option. This value is only used if <placeholder-2/> is specified."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:103(literal)
+msgid "data_pool_name"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:105(para)
+msgid "Specifies the GPFS storage pool to which the volume is to be assigned. Note: The GPFS storage pool must already have been created."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:111(literal)
+msgid "replicas"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:113(para)
+msgid "Specifies how many copies of the volume file to create. Valid values are 1, 2, and, for GPFS V3.5.0.7 and later, 3. This value cannot be greater than the value of the <literal>MaxDataReplicas</literal> attribute of the file system."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:122(literal)
+msgid "dio"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:124(para)
+msgid "Enables or disables the Direct I/O caching policy for the volume file. Valid values are <literal>yes</literal> and <literal>no</literal>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:130(literal)
+msgid "write_affinity_depth"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:132(para)
+msgid "Specifies the allocation policy to be used for the volume file. Note: This option only works if <literal>allow-write-affinity</literal> is set for the GPFS data pool."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:139(literal)
+msgid "block_group_factor"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:141(para)
+msgid "Specifies how many blocks are laid out sequentially in the volume file to behave as a single large block. Note: This option only works if <literal>allow-write-affinity</literal> is set for the GPFS data pool."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:149(literal)
+msgid "write_affinity_failure_group"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:151(para)
+msgid "Specifies the range of nodes (in GPFS shared nothing architecture) where replicas of blocks in the volume file are to be written. See <citetitle>GPFS: Administration and Programming Reference</citetitle> for more details on this option."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:162(title)
+msgid "Example: Volume creation options"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:163(para)
+msgid "This example shows the creation of a 50GB volume with an <systemitem>ext4</systemitem> file system labeled <literal>newfs</literal> and direct IO enabled:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:169(title)
+msgid "Operational notes for GPFS driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:171(title) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:644(title)
+msgid "Snapshots and clones"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:172(para)
+msgid "Volume snapshots are implemented using the GPFS file clone feature. Whenever a new snapshot is created, the snapshot file is efficiently created as a read-only clone parent of the volume, and the volume file uses copy-on-write optimization strategy to minimize data movement."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:178(para)
+msgid "Similarly when a new volume is created from a snapshot or from an existing volume, the same approach is taken. The same approach is also used when a new volume is created from an Image Service image, if the source image is in raw format, and <literal>gpfs_images_share_mode</literal> is set to <literal>copy_on_write</literal>."
 msgstr ""
 
 #. When image changes, this message will be marked fuzzy or untranslated for you.
 #. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:134(None)
-msgid "@@image: '../../common/figures/xenserver_architecture.png'; md5=8eb25be1693aa7865967ac7b07d3e563"
+#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:62(None)
+msgid "@@image: '../../../common/figures/xenapinfs/local_config.png'; md5=16a3864b0ec636518335246360438fd1"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:7(title)
-msgid "Xen, XenAPI, XenServer, and XCP"
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:78(None)
+msgid "@@image: '../../../common/figures/xenapinfs/remote_config.png'; md5=eab22f6aa5413c2043936872ea44e459"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:9(title)
-msgid "This section needs help"
+#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:4(title)
+msgid "XenAPINFS"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:10(para)
-msgid "This section is low quality, and contains out of date information. The Documentation Team is currently looking for individuals with experience with the hypervisor to <link href=\"https://blueprints.launchpad.net/openstack-manuals/+spec/redocument-xen\">Re-document Xen integration with OpenStack</link>."
+#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:5(para)
+msgid "XenAPINFS is a Block Storage (Cinder) driver that uses an NFS share through the XenAPI Storage Manager to store virtual disk images and expose those virtual disks as volumes."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:16(para)
-msgid "This section describes Xen, XenAPI, XenServer, and XCP, their differences, and how to use them with OpenStack. After you understand how the Xen and KVM architectures differ, you can determine when to use each architecture in your OpenStack cloud."
+#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:8(para)
+msgid "This driver does not access the NFS share directly. It accesses the share only through XenAPI Storage Manager. Consider this driver as a reference implementation for use of the XenAPI Storage Manager in OpenStack (present in XenServer and XCP)."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:22(title)
-msgid "Xen terminology"
+#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:14(title) ./doc/config-reference/block-storage/drivers/coraid-driver.xml:72(title)
+msgid "Requirements"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:23(para)
-msgid "<emphasis role=\"bold\">Xen</emphasis>. A hypervisor that provides the fundamental isolation between virtual machines. Xen is open source (GPLv2) and is managed by Xen.org, an cross-industry organization."
+#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:17(para)
+msgid "A XenServer/XCP installation that acts as Storage Controller. This hypervisor is known as the storage controller."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:27(para)
-msgid "Xen is a component of many different products and projects. The hypervisor itself is very similar across all these projects, but the way that it is managed can be different, which can cause confusion if you're not clear which tool stack you are using. Make sure you know what tool stack you want before you get started."
+#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:22(para)
+msgid "Use XenServer/XCP as your hypervisor for Compute nodes."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:33(para)
-msgid "<emphasis role=\"bold\">Xen Cloud Platform (XCP)</emphasis>. An open source (GPLv2) tool stack for Xen. It is designed specifically as a platform for enterprise and cloud computing, and is well integrated with OpenStack. XCP is available both as a binary distribution, installed from an iso, and from Linux distributions, such as <link href=\"http://packages.ubuntu.com/precise/xcp-xapi\">xcp-xapi</link> in Ubuntu. The current versions of XCP available in Linux distributions do not yet include all the features available in the binary distribution of XCP."
+#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:26(para)
+msgid "An NFS share that is configured for XenServer/XCP. For specific requirements and export options, see the administration guide for your specific XenServer version. The NFS share must be accessible by all XenServers components within your cloud."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:45(para)
-msgid "<emphasis role=\"bold\">Citrix XenServer</emphasis>. A commercial product. It is based on XCP, and exposes the same tool stack and management API. As an analogy, think of XenServer being based on XCP in the way that Red Hat Enterprise Linux is based on Fedora. XenServer has a free version (which is very similar to XCP) and paid-for versions with additional features enabled. Citrix provides support for XenServer, but as of July 2012, they do not provide any support for XCP. For a comparison between these products see the <link href=\"http://wiki.xen.org/wiki/XCP/XenServer_Feature_Matrix\"> XCP Feature Matrix</link>."
+#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:34(para)
+msgid "To create volumes from XenServer type images (vhd tgz files), XenServer Nova plug-ins are also required on the storage controller."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:57(para)
-msgid "Both XenServer and XCP include Xen, Linux, and the primary control daemon known as <emphasis role=\"bold\">xapi</emphasis>."
+#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:40(para)
+msgid "You can use a XenServer as a storage controller and compute node at the same time. This minimal configuration consists of a XenServer/XCP box and an NFS share."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:60(para)
-msgid "The API shared between XCP and XenServer is called <emphasis role=\"bold\">XenAPI</emphasis>. OpenStack usually refers to XenAPI, to indicate that the integration works equally well on XCP and XenServer. Sometimes, a careless person will refer to XenServer specifically, but you can be reasonably confident that anything that works on XenServer will also work on the latest version of XCP. Read the <link href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/sdk.html#object_model_overview\"> XenAPI Object Model Overview</link> for definitions of XenAPI specific terms such as SR, VDI, VIF and PIF."
+#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:47(title)
+msgid "Configuration patterns"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:73(title)
-msgid "Privileged and unprivileged domains"
+#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:50(para)
+msgid "Local configuration (Recommended): The driver runs in a virtual machine on top of the storage controller. With this configuration, you can create volumes from <literal>qemu-img</literal>-supported formats."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:74(para)
-msgid "A Xen host runs a number of virtual machines, VMs, or domains (the terms are synonymous on Xen). One of these is in charge of running the rest of the system, and is known as \"domain 0,\" or \"dom0.\" It is the first domain to boot after Xen, and owns the storage and networking hardware, the device drivers, and the primary control software. Any other VM is unprivileged, and are known as a \"domU\" or \"guest\". All customer VMs are unprivileged of course, but you should note that on Xen the OpenStack control software (<systemitem class=\"service\">nova-compute</systemitem>) also runs in a domU. This gives a level of security isolation between the privileged system software and the OpenStack software (much of which is customer-facing). This architecture is described in more detail later."
+#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:57(title)
+msgid "Local configuration"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:90(para)
-msgid "There is an ongoing project to split domain 0 into multiple privileged domains known as <emphasis role=\"bold\">driver domains</emphasis> and <emphasis role=\"bold\">stub domains</emphasis>. This would give even better separation between critical components. This technology is what powers Citrix XenClient RT, and is likely to be added into XCP in the next few years. However, the current architecture just has three levels of separation: dom0, the OpenStack domU, and the completely unprivileged customer VMs."
+#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:68(para)
+msgid "Remote configuration: The driver is not a guest VM of the storage controller. With this configuration, you can only use XenServer vhd-type images to create volumes."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:103(title)
-msgid "Paravirtualized versus hardware virtualized domains"
+#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:73(title)
+msgid "Remote configuration"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:105(para)
-msgid "A Xen virtual machine can be <emphasis role=\"bold\">paravirtualized (PV)</emphasis> or <emphasis role=\"bold\">hardware virtualized (HVM)</emphasis>. This refers to the interaction between Xen, domain 0, and the guest VM's kernel. PV guests are aware of the fact that they are virtualized and will co-operate with Xen and domain 0; this gives them better performance characteristics. HVM guests are not aware of their environment, and the hardware has to pretend that they are running on an unvirtualized machine. HVM guests do not need to modify the guest operating system, which is essential when running Windows."
+#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:86(title) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:312(caption)
+msgid "Configuration options"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:118(para)
-msgid "In OpenStack, customer VMs may run in either PV or HVM mode. However, the OpenStack domU (that's the one running <systemitem class=\"service\">nova-compute</systemitem>) <emphasis role=\"bold\">must</emphasis> be running in PV mode."
+#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:87(para)
+msgid "Assuming the following setup:"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:126(title)
-msgid "XenAPI Deployment Architecture"
+#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:90(para)
+msgid "XenServer box at <literal>10.2.2.1</literal>"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:128(para)
-msgid "When you deploy OpenStack on XCP or XenServer, you get something similar to this: <placeholder-1/>"
+#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:94(para)
+msgid "XenServer password is <literal>r00tme</literal>"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:140(para)
-msgid "The hypervisor: Xen"
+#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:98(para)
+msgid "NFS server is <literal>nfs.example.com</literal>"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:143(para)
-msgid "Domain 0: runs xapi and some small pieces from OpenStack (some xapi plug-ins and network isolation rules). The majority of this is provided by XenServer or XCP (or yourself using Kronos)."
+#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:102(para)
+msgid "NFS export is at <literal>/volumes</literal>"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:150(para)
-msgid "OpenStack VM: The <systemitem class=\"service\">nova-compute</systemitem> code runs in a paravirtualized virtual machine, running on the host under management. Each host runs a local instance of <systemitem class=\"service\">nova-compute</systemitem>. It will often also be running nova-network (depending on your network mode). In this case, nova-network is managing the addresses given to the tenant VMs through DHCP."
+#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:106(para)
+msgid "To use XenAPINFS as your cinder driver, set these configuration options in the <filename>cinder.conf</filename> file:"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:162(para)
-msgid "Nova uses the XenAPI Python library to talk to xapi, and it uses the Management Network to reach from the domU to dom0 without leaving the host."
+#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:115(para)
+msgid "The following table shows the configuration options that the XenAPINFS driver supports:"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:138(para)
-msgid "Key things to note: <placeholder-1/>"
+#: ./doc/config-reference/block-storage/drivers/sheepdog-driver.xml:6(title)
+msgid "Sheepdog driver"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:170(para)
-msgid "The above diagram assumes FlatDHCP networking (the DevStack default)."
+#: ./doc/config-reference/block-storage/drivers/sheepdog-driver.xml:7(para)
+msgid "Sheepdog is an open-source distributed storage system that provides a virtual storage pool utilizing internal disk of commodity servers."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:176(para)
-msgid "Management network - RabbitMQ, MySQL, etc. Please note that the VM images are downloaded by the XenAPI plug-ins, so make sure that the images can be downloaded through the management network. It usually means binding those services to the management interface."
+#: ./doc/config-reference/block-storage/drivers/sheepdog-driver.xml:10(para)
+msgid "Sheepdog scales to several hundred nodes, and has powerful virtual disk management features like snapshot, cloning, rollback, thin proisioning."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:186(para)
-msgid "Tenant network - controlled by nova-network. The parameters of this network depend on the networking model selected (Flat, Flat DHCP, VLAN)."
+#: ./doc/config-reference/block-storage/drivers/sheepdog-driver.xml:13(para)
+msgid "More information can be found on <link href=\"http://sheepdog.github.io/sheepdog/\">Sheepdog Project</link>."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:193(para)
-msgid "Public network - floating IPs, public API endpoints."
+#: ./doc/config-reference/block-storage/drivers/sheepdog-driver.xml:15(para)
+msgid "This driver enables use of Sheepdog through Qemu/KVM."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:174(para)
-msgid "There are three main OpenStack Networks:<placeholder-1/>"
+#: ./doc/config-reference/block-storage/drivers/sheepdog-driver.xml:16(para)
+msgid "Set the following <literal>volume_driver</literal> in <filename>cinder.conf</filename>:"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:199(para)
-msgid "The networks shown here must be connected to the corresponding physical networks within the data center. In the simplest case, three individual physical network cards could be used. It is also possible to use VLANs to separate these networks. Please note, that the selected configuration must be in line with the networking model selected for the cloud. (In case of VLAN networking, the physical channels have to be able to forward the tagged traffic.)"
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:6(title)
+msgid "EMC SMI-S iSCSI and FC drivers"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:168(para)
-msgid "Some notes on the networking: <placeholder-1/>"
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:7(para)
+msgid "The EMC volume drivers, <literal>EMCSMISISCSIDriver</literal> and <literal>EMCSMISFCDriver</literal>, has the ability to create/delete and attach/detach volumes and create/delete snapshots, and so on."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:214(title)
-msgid "XenAPI pools"
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:11(para)
+msgid "The driver runs volume operations by communicating with the backend EMC storage. It uses a CIM client in Python called PyWBEM to perform CIM operations over HTTP."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:215(para)
-msgid "The host-aggregates feature enables you to create pools of XenServer hosts to enable live migration when using shared storage. However, you cannot configure shared storage."
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:15(para)
+msgid "The EMC CIM Object Manager (ECOM) is packaged with the EMC SMI-S provider. It is a CIM server that enables CIM clients to perform CIM operations over HTTP by using SMI-S in the back-end for EMC storage operations."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:221(title)
-msgid "Further reading"
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:19(para)
+msgid "The EMC SMI-S Provider supports the SNIA Storage Management Initiative (SMI), an ANSI standard for storage management. It supports VMAX and VNX storage systems."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:225(para)
-msgid "Citrix XenServer official documentation:<link href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/\"> http://docs.vmd.citrix.com/XenServer</link>."
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:24(para)
+msgid "EMC SMI-S Provider V4.6.1 and higher is required. You can download SMI-S from the <link href=\"https://support.emc.com\">EMC's support</link> web site (login is required). See the EMC SMI-S Provider release notes for installation instructions."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:232(para)
-msgid "What is Xen? by Xen.org: <link href=\"http://xen.org/files/Marketing/WhatisXen.pdf\"> http://xen.org/files/Marketing/WhatisXen.pdf</link>."
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:30(para)
+msgid "EMC storage VMAX Family and VNX Series are supported."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:238(para)
-msgid "Xen Hypervisor project: <link href=\"http://xen.org/products/xenhyp.html\"> http://xen.org/products/xenhyp.html</link>."
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:35(para)
+msgid "VMAX and VNX arrays support these operations:"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:244(para)
-msgid "XCP project: <link href=\"http://xen.org/products/cloudxen.html\"> http://xen.org/products/cloudxen.html</link>."
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:56(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:57(para)
+msgid "Create cloned volume"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:250(para)
-msgid "Further XenServer and OpenStack information: <link href=\"http://wiki.openstack.org/XenServer\"> http://wiki.openstack.org/XenServer</link>."
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:65(para)
+msgid "Only VNX supports the following operations:"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_introduction-to-xen.xml:222(para)
-msgid "Here are some of the resources available to learn more about Xen: <placeholder-1/>"
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:71(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:43(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:66(para)
+msgid "Extend volume"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_hypervisor_baremetal.xml:6(title)
-msgid "Baremetal driver"
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:76(title)
+msgid "Set up the SMI-S drivers"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_hypervisor_baremetal.xml:7(para)
-msgid "The baremetal driver is a hypervisor driver for OpenStack Nova Compute. Within the OpenStack framework, it has the same role as the drivers for other hypervisors (libvirt, xen, etc), and yet it is presently unique in that the hardware is not virtualized - there is no hypervisor between the tenants and the physical hardware. It exposes hardware through the OpenStack APIs, using pluggable sub-drivers to deliver machine imaging (PXE) and power control (IPMI). With this, provisioning and management of physical hardware is accomplished by using common cloud APIs and tools, such as the Orchestration module (heat) or salt-cloud. However, due to this unique situation, using the baremetal driver requires some additional preparation of its environment, the details of which are beyond the scope of this guide."
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:78(title)
+msgid "To set up the EMC SMI-S drivers"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_hypervisor_baremetal.xml:20(para)
-msgid "Some OpenStack Compute features are not implemented by the baremetal hypervisor driver. See the <link href=\"http://wiki.openstack.org/HypervisorSupportMatrix\"> hypervisor support matrix</link> for details."
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:80(para)
+msgid "Install the <package>python-pywbem</package> package for your distribution. See <xref linkend=\"install-pywbem\"/>."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_hypervisor_baremetal.xml:24(para)
-msgid "For the Baremetal driver to be loaded and function properly, ensure that the following options are set in <filename>/etc/nova/nova.conf</filename> on your <systemitem class=\"service\">nova-compute</systemitem> hosts."
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:85(para)
+msgid "Download SMI-S from PowerLink and install it. Add your VNX/VMAX arrays to SMI-S."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_hypervisor_baremetal.xml:34(para)
-msgid "Many configuration options are specific to the Baremetal driver. Also, some additional steps are required, such as building the baremetal deploy ramdisk. See the <link href=\"https://wiki.openstack.org/wiki/Baremetal\">main wiki page</link> for details and implementation suggestions."
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:87(para)
+msgid "For information, see <xref linkend=\"setup-smi-s\"/> and the SMI-S release notes."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_hypervisor_baremetal.xml:40(para)
-msgid "To customize the Baremetal driver, use the configuration option settings documented in <xref linkend=\"config_table_nova_baremetal\"/>."
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:91(para)
+msgid "Register with VNX. See <xref linkend=\"register-vnx-iscsi\"/> for the VNX iSCSI driver and <xref linkend=\"register-vnx-fc\"/> for the VNX FC driver."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:98(para)
+msgid "Create a masking view on VMAX. See <xref linkend=\"create-masking\"/>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:103(title)
+msgid "Install the <package>python-pywbem</package> package"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:104(para)
+msgid "Install the <package>python-pywbem</package> package for your distribution, as follows:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:108(para)
+msgid "On Ubuntu:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:112(para)
+msgid "On openSUSE:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:116(para)
+msgid "On Fedora:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:122(title)
+msgid "Set up SMI-S"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:123(para)
+msgid "You can install SMI-S on a non-OpenStack host. Supported platforms include different flavors of Windows, Red Hat, and SUSE Linux. SMI-S can be installed on a physical server or a VM hosted by an ESX server. Note that the supported hypervisor for a VM running SMI-S is ESX only. See the EMC SMI-S Provider release notes for more information on supported platforms and installation instructions."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:132(para)
+msgid "You must discover storage arrays on the SMI-S server before you can use the Cinder driver. Follow instructions in the SMI-S release notes."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:137(para)
+msgid "SMI-S is usually installed at <filename>/opt/emc/ECIM/ECOM/bin</filename> on Linux and <filename>C:\\Program Files\\EMC\\ECIM\\ECOM\\bin</filename> on Windows. After you install and configure SMI-S, go to that directory and type <placeholder-1/>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:144(para)
+msgid "Use <placeholder-1/> in <placeholder-2/> to add an array. Use <placeholder-3/> and examine the output after the array is added. Make sure that the arrays are recognized by the SMI-S server before using the EMC Cinder driver."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:152(title)
+msgid "Register with VNX for the iSCSI driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:153(para)
+msgid "To export a VNX volume to a Compute node or a Volume node, you must register the node with VNX."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:156(title)
+msgid "Register the node"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:157(para)
+msgid "On the Compute node or Volume node <literal>1.1.1.1</literal>, do the following (assume <literal>10.10.61.35</literal> is the iscsi target):"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:165(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:109(para)
+msgid "Log in to VNX from the node using the target corresponding to the SPA port:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:168(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:112(para)
+msgid "Where <literal>iqn.1992-04.com.emc:cx.apm01234567890.a0</literal> is the initiator name of the node. Login to Unisphere, go to <literal>VNX00000</literal>-&gt;Hosts-&gt;Initiators, Refresh and wait until initiator <literal>iqn.1992-04.com.emc:cx.apm01234567890.a0</literal> with SP Port <literal>A-8v0</literal> appears."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:176(para)
+msgid "Click the <guibutton>Register</guibutton> button, select <guilabel>CLARiiON/VNX</guilabel>, and enter the host name <literal>myhost1</literal> and IP address <literal>myhost1</literal>. Click <guibutton>Register</guibutton>. Now host <literal>1.1.1.1</literal> also appears under Hosts-&gt;Host List."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:182(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:126(para)
+msgid "Log out of VNX on the node:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:185(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:129(para)
+msgid "Log in to VNX from the node using the target corresponding to the SPB port:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:189(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:133(para)
+msgid "In Unisphere register the initiator with the SPB port."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:191(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:135(para)
+msgid "Log out:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:196(title)
+msgid "Register with VNX for the FC driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:197(para)
+msgid "For a VNX volume to be exported to a Compute node or a Volume node, SAN zoning needs to be configured on the node and WWNs of the node need to be registered with VNX in Unisphere."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:203(title)
+msgid "Create a masking view on VMAX"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:204(para)
+msgid "For VMAX iSCSI and FC drivers, you need to do initial setup in Unisphere for VMAX. In Unisphere for VMAX, create an initiator group, a storage group, and a port group. Put them in a masking view. The initiator group contains the initiator names of the OpenStack hosts. The storage group will contain volumes provisioned by Block Storage."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:214(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:142(para)
+msgid "Make the following changes in <filename>/etc/cinder/cinder.conf</filename>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:216(para)
+msgid "For VMAX iSCSI driver, add the following entries, where <literal>10.10.61.45</literal> is the IP address of the VMAX iSCSI target:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:223(para)
+msgid "For VNX iSCSI driver, add the following entries, where <literal>10.10.61.35</literal> is the IP address of the VNX iSCSI target:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:230(para)
+msgid "For VMAX and VNX FC drivers, add the following entries:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:234(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:169(para)
+msgid "Restart the <systemitem class=\"service\">cinder-volume</systemitem> service."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:238(title)
+msgid "<filename>cinder_emc_config.xml</filename> configuration file"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:240(para)
+msgid "Create the <filename>/etc/cinder/cinder_emc_config.xml</filename> file. You do not need to restart the service for this change."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:242(para)
+msgid "For VMAX, add the following lines to the XML file:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:245(para)
+msgid "For VNX, add the following lines to the XML file:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:248(para)
+msgid "Where:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:251(para)
+msgid "<systemitem>StorageType</systemitem> is the thin pool from which the user wants to create the volume. Thin pools can be created using Unisphere for VMAX and VNX. If the <literal>StorageType</literal> tag is not defined, you have to define volume types and set the pool name in extra specs."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:260(para)
+msgid "<systemitem>EcomServerIp</systemitem> and <systemitem>EcomServerPort</systemitem> are the IP address and port number of the ECOM server which is packaged with SMI-S."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:265(para)
+msgid "<systemitem>EcomUserName</systemitem> and <systemitem>EcomPassword</systemitem> are credentials for the ECOM server."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:270(para)
+msgid "<systemitem>Timeout</systemitem> specifies the maximum number of seconds you want to wait for an operation to finish."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:277(para)
+msgid "To attach VMAX volumes to an OpenStack VM, you must create a Masking View by using Unisphere for VMAX. The Masking View must have an Initiator Group that contains the initiator of the OpenStack compute node that hosts the VM."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:287(title) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:173(title)
+msgid "Volume type support"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:288(para)
+msgid "Volume type support enables a single instance of <systemitem>cinder-volume</systemitem> to support multiple pools and thick/thin provisioning."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:291(para)
+msgid "When the <literal>StorageType</literal> tag in <filename>cinder_emc_config.xml</filename> is used, the pool name is specified in the tag. Only thin provisioning is supported in this case."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:295(para)
+msgid "When the <literal>StorageType</literal> tag is not used in <filename>cinder_emc_config.xml</filename>, the volume type needs to be used to define a pool name and a provisioning type. The pool name is the name of a pre-created pool. The provisioning type could be either <literal>thin</literal> or <literal>thick</literal>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:301(para)
+msgid "Here is an example of how to set up volume type. First create volume types. Then define extra specs for each volume type."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:305(title)
+msgid "Setup volume types"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:307(para)
+msgid "Create the volume types:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:312(para)
+msgid "Setup the volume type extra specs:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:319(para)
+msgid "In the above example, two volume types are created. They are <literal>High Performance</literal> and <literal> Standard Performance</literal>. For <literal>High Performance </literal>, <literal>storagetype:pool</literal> is set to <literal>smi_pool</literal> and <literal>storagetype:provisioning </literal> is set to <literal>thick</literal>. Similarly for <literal>Standard Performance</literal>, <literal> storagetype:pool</literal>. is set to <literal>smi_pool2</literal> and <literal>storagetype:provisioning</literal> is set to <literal>thin</literal>. If <literal>storagetype:provisioning </literal> is not specified, it will default to <literal> thin</literal>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:331(para)
+msgid "Volume type names <literal>High Performance</literal> and <literal>Standard Performance</literal> are user-defined and can be any names. Extra spec keys <literal>storagetype:pool</literal> and <literal>storagetype:provisioning</literal> have to be the exact names listed here. Extra spec value <literal>smi_pool </literal> is your pool name. The extra spec value for <literal>storagetype:provisioning</literal> has to be either <literal>thick</literal> or <literal>thin</literal>. The driver will look for a volume type first. If the volume type is specified when creating a volume, the driver will look for the volume type definition and find the matching pool and provisioning type. If the volume type is not specified, it will fall back to use the <literal>StorageType</literal> tag in <filename> cinder_emc_config.xml</filename>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/solidfire-volume-driver.xml:5(title)
+msgid "SolidFire"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/solidfire-volume-driver.xml:6(para)
+msgid "The SolidFire Cluster is a high performance all SSD iSCSI storage device that provides massive scale out capability and extreme fault tolerance. A key feature of the SolidFire cluster is the ability to set and modify during operation specific QoS levels on a volume for volume basis. The SolidFire cluster offers this along with de-duplication, compression, and an architecture that takes full advantage of SSDs."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/solidfire-volume-driver.xml:14(para)
+msgid "To configure the use of a SolidFire cluster with Block Storage, modify your <filename>cinder.conf</filename> file as follows:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/solidfire-volume-driver.xml:23(para)
+msgid "The SolidFire driver creates a unique account prefixed with <literal>$cinder-volume-service-hostname-$tenant-id</literal> on the SolidFire cluster for each tenant that accesses the cluster through the Volume API. Unfortunately, this account formation results in issues for High Availability (HA) installations and installations where the <systemitem class=\"service\">cinder-volume</systemitem> service can move to a new node. HA installations can return an <errortext>Account Not Found</errortext> error because the call to the SolidFire cluster is not always going to be sent from the same node. In installations where the <systemitem class=\"service\">cinder-volume</systemitem> service moves to a new node, the same issue can occur when you perform operations on existing volumes, such as clone, extend, delete, and so on."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/solidfire-volume-driver.xml:41(para)
+msgid "Set the <option>sf_account_prefix</option> option to an empty string ('') in the <filename>cinder.conf</filename> file. This setting results in unique accounts being created on the SolidFire cluster, but the accounts are prefixed with the <systemitem>tenant-id</systemitem> or any unique identifier that you choose and are independent of the host where the <systemitem class=\"service\">cinder-volume</systemitem> service resides."
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:19(None)
+msgid "@@image: '../../../common/figures/ceph/ceph-architecture.png'; md5=f7e854c9dbfb64534c47c3583e774c81"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:4(title)
+msgid "Ceph RADOS Block Device (RBD)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:5(para)
+msgid "If you use KVM or QEMU as your hypervisor, you can configure the Compute service to use <link href=\"http://ceph.com/ceph-storage/block-storage/\"> Ceph RADOS block devices (RBD)</link> for volumes."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:15(title)
+msgid "Ceph architecture"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:9(para)
+msgid "Ceph is a massively scalable, open source, distributed storage system. It is comprised of an object store, block store, and a POSIX-compliant distributed file system. The platform can auto-scale to the exabyte level and beyond. It runs on commodity hardware, is self-healing and self-managing, and has no single point of failure. Ceph is in the Linux kernel and is integrated with the OpenStack cloud operating system. Due to its open-source nature, you can install and use this portable storage platform in public or private clouds. <placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:25(title)
+msgid "RADOS"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:26(para)
+msgid "Ceph is based on <emphasis>RADOS: Reliable Autonomic Distributed Object Store</emphasis>. RADOS distributes objects across the storage cluster and replicates objects for fault tolerance. RADOS contains the following major components:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:32(para)
+msgid "<emphasis>Object Storage Device (OSD) Daemon</emphasis>. The storage daemon for the RADOS service, which interacts with the OSD (physical or logical storage unit for your data)."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:35(para)
+msgid "You must run this daemon on each server in your cluster. For each OSD, you can have an associated hard drive disk. For performance purposes, pool your hard drive disk with raid arrays, logical volume management (LVM), or B-tree file system (<systemitem>Btrfs</systemitem>) pooling. By default, the following pools are created: data, metadata, and RBD."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:42(para)
+msgid "<emphasis>Meta-Data Server (MDS)</emphasis>. Stores metadata. MDSs build a POSIX file system on top of objects for Ceph clients. However, if you do not use the Ceph file system, you do not need a metadata server."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:49(para)
+msgid "<emphasis>Monitor (MON)</emphasis>. A lightweight daemon that handles all communications with external applications and clients. It also provides a consensus for distributed decision making in a Ceph/RADOS cluster. For instance, when you mount a Ceph shared on a client, you point to the address of a MON server. It checks the state and the consistency of the data. In an ideal setup, you must run at least three <code>ceph-mon</code> daemons on separate servers."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:58(para)
+msgid "Ceph developers recommend that you use <systemitem>Btrfs</systemitem> as a file system for storage. XFS might be a better alternative for production environments;XFS is an excellent alternative to Btrfs. The ext4 file system is also compatible but does not exploit the power of Ceph."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:63(para)
+msgid "If using <systemitem>Btrfs</systemitem>, ensure that you use the correct version (see <link href=\"http://ceph.com/docs/master/start/os-recommendations/.\">Ceph Dependencies</link>)."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:66(para)
+msgid "For more information about usable file systems, see <link href=\"http://ceph.com/ceph-storage/file-system/\">ceph.com/ceph-storage/file-system/</link>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:72(title)
+msgid "Ways to store, use, and expose data"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:73(para)
+msgid "To store and access your data, you can use the following storage systems:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:77(para)
+msgid "<emphasis>RADOS</emphasis>. Use as an object, default storage mechanism."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:81(para)
+msgid "<emphasis>RBD</emphasis>. Use as a block device. The Linux kernel RBD (rados block device) driver allows striping a Linux block device over multiple distributed object store data objects. It is compatible with the KVM RBD image."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:88(para)
+msgid "<emphasis>CephFS</emphasis>. Use as a file, POSIX-compliant file system."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:92(para)
+msgid "Ceph exposes RADOS; you can access it through the following interfaces:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:95(para)
+msgid "<emphasis>RADOS Gateway</emphasis>. OpenStack Object Storage and Amazon-S3 compatible RESTful interface (see <link href=\"http://ceph.com/wiki/RADOS_Gateway\">RADOS_Gateway</link>)."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:101(para)
+msgid "<emphasis>librados</emphasis>, and its related C/C++ bindings."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:104(para)
+msgid "<emphasis>rbd and QEMU-RBD</emphasis>. Linux kernel and QEMU block devices that stripe data across multiple objects."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:111(title)
+msgid "Driver options"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:112(para)
+msgid "The following table contains the configuration options supported by the Ceph RADOS Block Device driver."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-xiv-volume-driver.xml:5(title)
+msgid "IBM XIV/DS8K volume driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-xiv-volume-driver.xml:6(para)
+msgid "There is a unified volume back-end for IBM XIV and DS8K storage. Set the following in your <filename>cinder.conf</filename>, and use the following options to configure it."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:9(title)
+msgid "HDS HUS iSCSI driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:10(para)
+msgid "This Block Storage volume driver provides iSCSI support for <link href=\"http://www.hds.com/products/storage-systems/hitachi-unified-storage-100-family.html\">HUS (Hitachi Unified Storage) </link> arrays such as, HUS-110, HUS-130, and HUS-150."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:16(para)
+msgid "Use the HDS <placeholder-1/> command to communicate with an HUS array. You can download this utility package from the HDS support site (<link href=\"https://HDSSupport.hds.com\">https://HDSSupport.hds.com</link>)."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:21(para)
+msgid "Platform: Ubuntu 12.04LTS or newer."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:25(para)
+msgid "These operations are supported:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:40(para)
+msgid "Clone volume"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:61(para)
+msgid "Get statistics"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:66(title) ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:134(title) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:35(title)
+msgid "Configuration"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:71(para)
+msgid "Do not confuse differentiated services with the OpenStack Block Storage volume services."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:67(para)
+msgid "The HDS driver supports the concept of differentiated services, where a volume type can be associated with the fine-tuned performance characteristics of an HDP the dynamic pool where volumes are created. For instance, an HDP can consist of fast SSDs to provide speed. HDP can provide a certain reliability based on things like its RAID level characteristics. HDS driver maps volume type to the volume_type option in its configuration file."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:79(para)
+msgid "Configuration is read from an XML-format file. Examples are shown for single and multi back-end cases."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:84(para)
+msgid "Configuration is read from an XML file. This example shows the configuration for single back-end and for multi-back-end cases."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:93(para)
+msgid "It is okay to manage multiple HUS arrays by using multiple OpenStack Block Storage instances (or servers)."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:89(para)
+msgid "It is not recommended to manage an HUS array simultaneously from multiple OpenStack Block Storage instances or servers. <placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:102(title)
+msgid "HUS setup"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:103(para)
+msgid "Before using iSCSI services, use the HUS UI to create an iSCSI domain for each EVS providing iSCSI services."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:107(title)
+msgid "Single back-end"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:108(para)
+msgid "In a single back-end deployment, only one OpenStack Block Storage instance runs on the OpenStack Block Storage server and controls one HUS array: this deployment requires these configuration files:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:121(para)
+msgid "The configuration file location may differ."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:114(para)
+msgid "Set the <option>hds_cinder_config_file</option> option in the <filename>/etc/cinder/cinder.conf</filename> file to use the HDS volume driver. This option points to a configuration file.<placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:128(para)
+msgid "Configure <option>hds_cinder_config_file</option> at the location specified previously. For example, <filename>/opt/hds/hus/cinder_hds_conf.xml</filename>:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:159(title)
+msgid "Multi back-end"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:160(para)
+msgid "In a multi back-end deployment, more than one OpenStack Block Storage instance runs on the same server. In this example, two HUS arrays are used, possibly providing different storage performance:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:166(para)
+msgid "Configure <filename>/etc/cinder/cinder.conf</filename>: the <literal>hus1</literal><option>hus2</option> configuration blocks are created. Set the <option>hds_cinder_config_file</option> option to point to a unique configuration file for each block. Set the <option>volume_driver</option> option for each back-end to <literal>cinder.volume.drivers.hds.hds.HUSDriver</literal>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:190(para)
+msgid "Configure <filename>/opt/hds/hus/cinder_hus1_conf.xml</filename>:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:216(para)
+msgid "Configure the <filename>/opt/hds/hus/cinder_hus2_conf.xml</filename> file:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:245(title)
+msgid "Type extra specs: <option>volume_backend</option> and volume type"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:247(para)
+msgid "If you use volume types, you must configure them in the configuration file and set the <option>volume_backend_name</option> option to the appropriate back-end. In the previous multi back-end example, the <literal>platinum</literal> volume type is served by hus-2, and the <literal>regular</literal> volume type is served by hus-1."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:258(title)
+msgid "Non differentiated deployment of HUS arrays"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:259(para)
+msgid "You can deploy multiple OpenStack Block Storage instances that each control a separate HUS array. Each instance has no volume type associated with it. The OpenStack Block Storage filtering algorithm selects the HUS array with the largest available free space. In each configuration file, you must define the <literal>default</literal><option>volume_type</option> in the service labels."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:270(title)
+msgid "HDS iSCSI volume driver configuration options"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:277(para)
+msgid "There is no relative precedence or weight among these four labels."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:271(para)
+msgid "These details apply to the XML format configuration file that is read by HDS volume driver. These differentiated service labels are predefined: <literal>svc_0</literal>, <literal>svc_1</literal>, <literal>svc_2</literal>, and <literal>svc_3</literal><placeholder-1/>. Each respective service label associates with these parameters and tags:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:283(para)
+msgid "<option>volume-types</option>: A create_volume call with a certain volume type shall be matched up with this tag. <literal>default</literal> is special in that any service associated with this type is used to create volume when no other labels match. Other labels are case sensitive and should exactly match. If no configured volume_types match the incoming requested type, an error occurs in volume creation."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:294(para)
+msgid "<option>HDP</option>, the pool ID associated with the service."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:298(para)
+msgid "An iSCSI port dedicated to the service."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:307(para)
+msgid "The get_volume_stats() always provides the available capacity based on the combined sum of all the HDPs that are used in these services labels."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:301(para)
+msgid "Typically a OpenStack Block Storage volume instance has only one such service label. For example, any <literal>svc_0</literal>, <literal>svc_1</literal>, <literal>svc_2</literal>, or <literal>svc_3</literal> can be associated with it. But any mix of these service labels can be used in the same instance <placeholder-1/>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:319(td) ./doc/config-reference/compute/section_compute-scheduler.xml:613(th) ./doc/config-reference/compute/section_compute-scheduler.xml:694(th)
+msgid "Option"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:327(option)
+msgid "mgmt_ip0"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:331(para)
+msgid "Management Port 0 IP address"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:335(option)
+msgid "mgmt_ip1"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:339(para)
+msgid "Management Port 1 IP address"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:343(option)
+msgid "hus_cmd"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:348(para)
+msgid "<option>hus_cmd</option> is the command used to communicate with the HUS array. If it is not set, the default value is <placeholder-1/>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:355(option) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:59(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:123(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:342(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:398(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:458(replaceable) ./doc/config-reference/block-storage/drivers/coraid-driver.xml:301(replaceable)
+msgid "username"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:360(para)
+msgid "Username is required only if secure mode is used"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:365(option) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:60(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:124(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:343(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:399(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:459(replaceable) ./doc/config-reference/block-storage/drivers/coraid-driver.xml:303(replaceable) ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:58(replaceable)
+msgid "password"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:370(para)
+msgid "Password is required only if secure mode is used"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:376(option)
+msgid "svc_0, svc_1, svc_2, svc_3"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:380(para)
+msgid "(at least one label has to be defined)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:383(para)
+msgid "Service labels: these four predefined names help four different sets of configuration options -- each can specify iSCSI port address, HDP and a unique volume type."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:392(option)
+msgid "snapshot"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:397(para)
+msgid "A service label which helps specify configuration for snapshots, such as, HDP."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:404(option)
+msgid "volume_type"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:409(para)
+msgid "<option>volume_type</option> tag is used to match volume type. <literal>Default</literal> meets any type of <option>volume_type</option>, or if it is not specified. Any other volume_type is selected if exactly matched during <literal>create_volume</literal>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:421(option)
+msgid "iscsi_ip"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:426(para)
+msgid "iSCSI port IP address where volume attaches for this volume type."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:432(option)
+msgid "hdp"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:437(para)
+msgid "HDP, the pool number where volume, or snapshot should be created."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:443(option)
+msgid "lun_start"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:448(para)
+msgid "LUN allocation starts at this number."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:454(option)
+msgid "lun_end"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:457(para)
+msgid "4096"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:459(para)
+msgid "LUN allocation is up to, but not including, this number."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:4(title)
+msgid "HP 3PAR Fibre Channel and iSCSI drivers"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:5(para)
+msgid "The <filename>HP3PARFCDriver</filename> and <filename>HP3PARISCSIDriver</filename> drivers, which are based on the Block Storage service (Cinder) plug-in architecture, run volume operations by communicating with the HP 3PAR storage system over HTTP, HTTPS, and SSH connections. The HTTP and HTTPS communications use <package>hp3parclient</package>, which is part of the Python standard library."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:13(para)
+msgid "For information about how to manage HP 3PAR storage systems, see the HP 3PAR user documentation."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:17(para)
+msgid "To use the HP 3PAR drivers, install the following software and components on the HP 3PAR storage system:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:22(para)
+msgid "HP 3PAR Operating System software version 3.1.3 or higher"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:26(para)
+msgid "HP 3PAR Web Services API Server must be enabled and running"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:30(para)
+msgid "One Common Provisioning Group (CPG)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:33(para)
+msgid "Additionally, you must install the <package>hp3parclient</package> version 3.0 or newer from the Python standard library on the system with the enabled Block Storage service volume drivers."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:45(para)
+msgid "Create volumes."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:48(para)
+msgid "Delete volumes."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:51(para)
+msgid "Extend volumes."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:54(para)
+msgid "Attach volumes."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:57(para)
+msgid "Detach volumes."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:60(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:343(para)
+msgid "Create snapshots."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:63(para)
+msgid "Delete snapshots."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:66(para)
+msgid "Create volumes from snapshots."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:69(para)
+msgid "Create cloned volumes."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:72(para)
+msgid "Copy images to volumes."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:75(para)
+msgid "Copy volumes to images."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:78(para)
+msgid "Volume migration(backend assisted)."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:81(para)
+msgid "Volume type support for both HP 3PAR drivers includes the ability to set the following capabilities in the OpenStack Block Storage API <filename>cinder.api.contrib.types_extra_specs</filename> volume type extra specs extension module:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:88(literal)
+msgid "hp3par:cpg"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:91(literal)
+msgid "hp3par:snap_cpg"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:94(literal)
+msgid "hp3par:provisioning"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:97(literal)
+msgid "hp3par:persona"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:100(literal)
+msgid "hp3par:vvs"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:103(para)
+msgid "To work with the default filter scheduler, the key values are case sensitive and scoped with <literal>hp3par:</literal>. For information about how to set the key-value pairs and associate them with a volume type, run the following command: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:112(para)
+msgid "Volumes that are cloned only support extra specs keys cpg, snap_cpg, provisioning and vvs. The others are ignored. In addition the comments section of the cloned volume in the HP 3PAR StoreServ storage array is not populated."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:118(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:166(para)
+msgid "If volume types are not used or a particular key is not set for a volume type, the following defaults are used:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:123(para)
+msgid "<literal>hp3par:cpg</literal> - Defaults to the <literal>hp3par_cpg</literal> setting in the <filename>cinder.conf</filename> file."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:128(para)
+msgid "<literal>hp3par:snap_cpg</literal> - Defaults to the <literal>hp3par_snap</literal> setting in the <filename>cinder.conf</filename> file. If <literal>hp3par_snap</literal> is not set, it defaults to the <literal>hp3par_cpg</literal> setting."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:136(para)
+msgid "<literal>hp3par:provisioning</literal> - Defaults to thin provisioning, the valid values are <literal>thin</literal> and <literal>full</literal>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:142(para)
+msgid "<literal>hp3par:persona</literal> - Defaults to the <literal>1 - Generic</literal> persona. The valid values are, <literal>1 - Generic</literal>, <literal>2 - Generic-ALUA</literal>, <literal>6 - Generic-legacy</literal>, <literal>7 - HPUX-legacy</literal>, <literal>8 - AIX-legacy</literal>, <literal>9 - EGENERA</literal>, <literal>10 - ONTAP-legacy</literal>, <literal>11 - VMware</literal>, <literal>12 - OpenVMS</literal>, <literal>13 - HPUX</literal>, and <literal>15 - WindowsServer</literal>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:156(para)
+msgid "QoS support for both HP 3PAR drivers includes the ability to set the following capabilities in the OpenStack Block Storage API <filename>cinder.api.contrib.qos_specs_manage</filename> qos specs extension module:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:163(literal)
+msgid "minBWS"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:166(literal)
+msgid "maxBWS"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:169(literal)
+msgid "minIOPS"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:172(literal)
+msgid "maxIOPS"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:175(literal)
+msgid "latency"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:178(literal)
+msgid "priority"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:181(para)
+msgid "The qos keys above no longer require to be scoped but must be created and associated to a volume type. For information about how to set the key-value pairs and associate them with a volume type, run the following commands: <placeholder-1/><placeholder-2/><placeholder-3/>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:191(para)
+msgid "The following keys require that the HP 3PAR StoreServ storage array has a Priority Optimization license installed."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:196(para)
+msgid "<literal>hp3par:vvs</literal> - The virtual volume set name that has been predefined by the Administrator with Quality of Service (QoS) rules associated to it. If you specify extra_specs <literal>hp3par:vvs</literal>, the qos_specs <literal>minIOPS</literal>, <literal>maxIOPS</literal>, <literal>minBWS</literal>, and <literal>maxBWS</literal> settings are ignored."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:207(para)
+msgid "<literal>minBWS</literal> - The QoS I/O issue bandwidth minimum goal in MBs. If not set, the I/O issue bandwidth rate has no minimum goal."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:212(para)
+msgid "<literal>maxBWS</literal> - The QoS I/O issue bandwidth rate limit in MBs. If not set, the I/O issue bandwidth rate has no limit."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:217(para)
+msgid "<literal>minIOPS</literal> - The QoS I/O issue count minimum goal. If not set, the I/O issue count has no minimum goal."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:222(para)
+msgid "<literal>maxIOPS</literal> - The QoS I/O issue count rate limit. If not set, the I/O issue count rate has no limit."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:227(para)
+msgid "<literal>latency</literal> - The latency goal in milliseconds."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:231(para)
+msgid "<literal>priority</literal> - The priority of the QoS rule over other rules. If not set, the priority is normal, valid values are low, normal and high."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:238(para)
+msgid "Since the Icehouse release, minIOPS and maxIOPS must be used together to set I/O limits. Similarly, minBWS and maxBWS must be used together. If only one is set the other will be set to the same value."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:245(title)
+msgid "Enable the HP 3PAR Fibre Channel and iSCSI drivers"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:247(para)
+msgid "The <filename>HP3PARFCDriver</filename> and <filename>HP3PARISCSIDriver</filename> are installed with the OpenStack software."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:252(para)
+msgid "Install the <filename>hp3parclient</filename> Python package on the OpenStack Block Storage system. <placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:259(para)
+msgid "Verify that the HP 3PAR Web Services API server is enabled and running on the HP 3PAR storage system."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:264(para)
+msgid "Log onto the HP 3PAR storage system with administrator access."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:267(replaceable)
+msgid "&lt;HP 3PAR IP Address&gt;"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:270(para)
+msgid "View the current state of the Web Services API Server."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:277(para)
+msgid "If the Web Services API Server is disabled, start it."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:286(para)
+msgid "If the HTTP or HTTPS state is disabled, enable one of them. <placeholder-1/> or <placeholder-2/>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:293(para)
+msgid "To stop the Web Services API Server, use the stopwsapi command. For other options run the <placeholder-1/> command."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:300(para)
+msgid "If you are not using an existing CPG, create a CPG on the HP 3PAR storage system to be used as the default location for creating volumes."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:308(emphasis) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:245(emphasis) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:380(emphasis)
+msgid "## REQUIRED SETTINGS"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:343(emphasis) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:262(emphasis) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:400(emphasis)
+msgid "## OPTIONAL SETTINGS"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:356(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:270(para)
+msgid "You can enable only one driver on each cinder instance unless you enable multiple back-end support. See the Cinder multiple back-end support instructions to enable this feature."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:363(para)
+msgid "You can configure one or more iSCSI addresses by using the <option>hp3par_iscsi_ips</option> option. When you configure multiple addresses, the driver selects the iSCSI port with the fewest active volumes at attach time. The IP address might include an IP port by using a colon (<literal>:</literal>) to separate the address from port. If you do not define an IP port, the default port 3260 is used. Separate IP addresses with a comma (<literal>,</literal>). The <option>iscsi_ip_address</option>/<option>iscsi_port</option> options might be used as an alternative to <option>hp3par_iscsi_ips</option> for single port iSCSI configuration."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:382(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:299(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:413(para)
+msgid "Save the changes to the <filename>cinder.conf</filename> file and restart the <systemitem class=\"service\">cinder-volume</systemitem> service."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:388(para)
+msgid "The HP 3PAR Fibre Channel and iSCSI drivers are now enabled on your OpenStack system. If you experience problems, review the Block Storage service log files for errors."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:4(title)
+msgid "Nexenta drivers"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:5(para)
+msgid "NexentaStor Appliance is NAS/SAN software platform designed for building reliable and fast network storage arrays. The Nexenta Storage Appliance uses ZFS as a disk management system. NexentaStor can serve as a storage node for the OpenStack and its virtual servers through iSCSI and NFS protocols."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:9(para)
+msgid "With the NFS option, every Compute volume is represented by a directory designated to be its own file system in the ZFS file system. These file systems are exported using NFS."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:12(para)
+msgid "With either option some minimal setup is required to tell OpenStack which NexentaStor servers are being used, whether they are supporting iSCSI and/or NFS and how to access each of the servers."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:16(para)
+msgid "Typically the only operation required on the NexentaStor servers is to create the containing directory for the iSCSI or NFS exports. For NFS this containing directory must be explicitly exported via NFS. There is no software that must be installed on the NexentaStor servers; they are controlled using existing management plane interfaces."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:24(title)
+msgid "Nexenta iSCSI driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:25(para)
+msgid "The Nexenta iSCSI driver allows you to use a NexentaStor appliance to store Compute volumes. Every Compute volume is represented by a single zvol in a predefined Nexenta namespace. For every new volume the driver creates a iSCSI target and iSCSI target group that are used to access it from compute hosts."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:29(para)
+msgid "The Nexenta iSCSI volume driver should work with all versions of NexentaStor. The NexentaStor appliance must be installed and configured according to the relevant Nexenta documentation. A pool and an enclosing namespace must be created for all iSCSI volumes to be accessed through the volume driver. This should be done as specified in the release specific NexentaStor documentation."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:36(para)
+msgid "The NexentaStor Appliance iSCSI driver is selected using the normal procedures for one or multiple back-end volume drivers. You must configure these items for each NexentaStor appliance that the iSCSI volume driver controls:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:42(title)
+msgid "Enable the Nexenta iSCSI driver and related options"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:44(para)
+msgid "This table contains the options supported by the Nexenta iSCSI driver."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:48(para)
+msgid "To use Compute with the Nexenta iSCSI driver, first set the <code>volume_driver</code>:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:52(para)
+msgid "Then, set the <code>nexenta_host</code> parameter and other parameters from the table, if needed."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:59(title)
+msgid "Nexenta NFS driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:60(para)
+msgid "The Nexenta NFS driver allows you to use NexentaStor appliance to store Compute volumes via NFS. Every Compute volume is represented by a single NFS file within a shared directory."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:64(para)
+msgid "While the NFS protocols standardize file access for users, they do not standardize administrative actions such as taking snapshots or replicating file systems. The OpenStack Volume Drivers bring a common interface to these operations. The Nexenta NFS driver implements these standard actions using the ZFS management plane that already is deployed on NexentaStor appliances."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:71(para)
+msgid "The Nexenta NFS volume driver should work with all versions of NexentaStor. The NexentaStor appliance must be installed and configured according to the relevant Nexenta documentation. A single-parent file system must be created for all virtual disk directories supported for OpenStack. This directory must be created and exported on each NexentaStor appliance. This should be done as specified in the release specific NexentaStor documentation."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:78(title)
+msgid "Enable the Nexenta NFS driver and related options"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:80(para)
+msgid "To use Compute with the Nexenta NFS driver, first set the <code>volume_driver</code>:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:85(para)
+msgid "The following table contains the options supported by the Nexenta NFS driver."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:89(para)
+msgid "Add your list of Nexenta NFS servers to the file you specified with the <code>nexenta_shares_config</code> option. For example, if the value of this option was set to <filename>/etc/cinder/nfs_shares</filename>, then:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:98(para)
+msgid "Comments are allowed in this file. They begin with a <code>#</code>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:100(para)
+msgid "Each line in this file represents a NFS share. The first part of the line is the NFS share URL, the second is the connection URL to the NexentaStor Appliance."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:4(title)
+msgid "HP LeftHand/StoreVirtual driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:5(para)
+msgid "The <filename>HPLeftHandISCSIDriver</filename> is based on the Block Storage service (Cinder) plug-in architecture. Volume operations are run by communicating with the HP LeftHand/StoreVirtual system over HTTPS, or SSH connections. HTTPS communications use the <package>hplefthandclient</package>, which is part of the Python standard library."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:15(para)
+msgid "The <filename>HPLeftHandISCSIDriver</filename> can be configured to run in one of two possible modes, legacy mode which uses SSH/CLIQ to communicate with the HP LeftHand/StoreVirtual array, or standard mode which uses a new REST client to communicate with the array. No new functionality has been, or will be, supported in legacy mode. For performance improvements and new functionality, the driver must be configured for standard mode, the <package>hplefthandclient</package> must be downloaded, and HP LeftHand/StoreVirtual Operating System software version 11.5 or higher is required on the array. To configure the driver in standard mode, see <xref linkend=\"hp-lefthand-rest-driver\"/>. To configure the driver in legacy mode, see <xref linkend=\"hp-lefthand-clix-driver\"/>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:33(para)
+msgid "For information about how to manage HP LeftHand/StoreVirtual storage systems, see the HP LeftHand/StoreVirtual user documentation."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:37(title)
+msgid "HP LeftHand/StoreVirtual REST driver standard mode"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:38(para)
+msgid "This section describes how to configure the HP LeftHand/StoreVirtual Cinder driver in standard mode."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:43(para)
+msgid "To use the HP LeftHand/StoreVirtual driver in standard mode, do the following:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:48(para)
+msgid "Install LeftHand/StoreVirtual Operating System software version 11.5 or higher on the HP LeftHand/StoreVirtual storage system."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:54(para)
+msgid "Create a cluster group."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:57(para)
+msgid "Install the <package>hplefthandclient</package> version 1.0.2 from the Python Package Index on the system with the enabled Block Storage service volume drivers."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:69(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:328(para)
+msgid "Create volumes"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:72(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:331(para)
+msgid "Delete volumes"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:75(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:334(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:638(title)
+msgid "Extend volumes"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:78(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:337(para)
+msgid "Attach volumes"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:81(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:340(para)
+msgid "Detach volumes"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:84(para)
+msgid "Create snapshots"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:87(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:346(para)
+msgid "Delete snapshots"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:90(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:349(para)
+msgid "Create volumes from snapshots"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:93(para)
+msgid "Create cloned volumes"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:96(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:352(para)
+msgid "Copy images to volumes"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:99(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:355(para)
+msgid "Copy volumes to images"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:102(para)
+msgid "Backend assisted volume migration"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:105(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:656(title)
+msgid "Volume retype"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:108(para)
+msgid "When a volume is migrated, using Backend assisted volume migration, both source and destination clusters must be in the same HP LeftHand/StoreVirtual management group. The HP LeftHand/StoreVirtual array will use native LeftHand APIs to migrate the volume. The volume cannot be attached or have snapshots to migrate."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:115(para)
+msgid "Volume type support for the driver includes the ability to set the following capabilities in the OpenStack Cinder API <filename>cinder.api.contrib.types_extra_specs</filename> volume type extra specs extension module."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:124(literal) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:169(term)
+msgid "hplh:provisioning"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:129(literal) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:152(term) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:175(term)
+msgid "hplh:ao"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:134(literal) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:156(term) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:181(term)
+msgid "hplh:data_pl"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:138(para)
+msgid "To work with the default filter scheduler, the key values are case sensitive and scoped with <literal>'hplh:'</literal>. For information about how to set the key-value pairs and associate them with a volume type, run the following command:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:149(para)
+msgid "The following keys require that the HP LeftHand/StoreVirtual storage array be configured for."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:153(para)
+msgid "The HP LeftHand/StoreVirtual storage array must be configured for Adaptive Optimization."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:157(para)
+msgid "The HP LeftHand/StoreVirtual storage array must be able to support the Data Protection level specified by the extra spec."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:170(para)
+msgid "Defaults to <parameter>thin</parameter> provisioning, the valid values are, <parameter>thin</parameter> and <parameter>full</parameter>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:176(para)
+msgid "Defaults to <parameter>true</parameter>, the valid values are, <parameter>true</parameter> and <parameter>false</parameter>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:182(para)
+msgid "Defaults to <parameter>r-0</parameter>, Network RAID-0 (None), the valid values are,"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:185(para)
+msgid "<parameter>r-0</parameter>, Network RAID-0 (None)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:189(para)
+msgid "<parameter>r-5</parameter>, Network RAID-5 (Single Parity)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:193(para)
+msgid "<parameter>r-10-2</parameter>, Network RAID-10 (2-Way Mirror)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:197(para)
+msgid "<parameter>r-10-3</parameter>, Network RAID-10 (3-Way Mirror)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:201(para)
+msgid "<parameter>r-10-4</parameter>, Network RAID-10 (4-Way Mirror)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:205(para)
+msgid "<parameter>r-6</parameter>, Network RAID-6 (Dual Parity),"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:217(title)
+msgid "Enable the HP LeftHand/StoreVirtual iSCSI driver in standard mode"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:219(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:362(para)
+msgid "The <filename>HPLeftHandISCSIDriver</filename> is installed with the OpenStack software."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:226(para)
+msgid "Install the <filename>hplefthandclient</filename> Python package on the OpenStack Block Storage system."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:234(para)
+msgid "If you are not using an existing cluster, create a cluster on the HP LeftHand storage system to be used as the cluster for creating volumes."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:240(para)
+msgid "Make the following changes in the <filename>/etc/cinder/cinder.conf</filename> file:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:248(replaceable)
+msgid "https://10.10.0.141:8081/lhos"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:251(replaceable) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:386(replaceable)
+msgid "lhuser"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:254(replaceable) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:389(replaceable)
+msgid "lhpass"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:257(replaceable) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:395(replaceable)
+msgid "ClusterLefthand"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:283(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:80(para)
+msgid "CHAP secrets are passed from OpenStack Block Storage to Compute in clear text. This communication should be secured to ensure that CHAP secrets are not discovered."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:290(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:68(para)
+msgid "CHAP secrets are added to existing hosts as well as newly-created ones. If the CHAP option is enabled, hosts will not be able to access the storage without the generated secrets."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:276(para)
+msgid "If the <option>hplefthand_iscsi_chap_enabled</option> is set to <literal>true</literal>, the driver will associate randomly-generated CHAP secrets with all hosts on the HP LeftHand/StoreVirtual system. OpenStack Compute nodes use these secrets when creating iSCSI connections. <placeholder-1/><placeholder-2/>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:307(para)
+msgid "The HP LeftHand/StoreVirtual driver is now enabled in standard mode on your OpenStack system. If you experience problems, review the Block Storage service log files for errors."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:314(title)
+msgid "HP LeftHand/StoreVirtual CLIQ driver legacy mode"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:315(para)
+msgid "This section describes how to configure the HP LeftHand/StoreVirtual Cinder driver in legacy mode."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:318(para)
+msgid "The <filename>HPLeftHandISCSIDriver</filename> allows you to use a HP Lefthand/StoreVirtual SAN that supports the CLIQ interface. Every supported volume operation translates into a CLIQ call in the back-end."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:360(title)
+msgid "Enable the HP LeftHand/StoreVirtual iSCSI driver in legacy mode"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:369(para)
+msgid "If you are not using an existing cluster, create a cluster on the HP Lefthand storage system to be used as the cluster for creating volumes."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:383(replaceable)
+msgid "10.10.0.141"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:422(para)
+msgid "The HP LeftHand/StoreVirtual driver is now enabled in legacy mode on your OpenStack system. If you experience problems, review the Block Storage service log files for errors."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:426(para)
+msgid "To configure the VSA"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:429(para)
+msgid "Configure CHAP on each of the <systemitem class=\"service\">nova-compute</systemitem> nodes."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:436(para)
+msgid "Add server associations on the VSA with the associated CHAPS and initiator information. The name should correspond to the <parameter>hostname</parameter> of the <parameter>nova-compute</parameter> node. For Xen, this is the hypervisor host name. To do this, use either CLIQ or the Centralized Management Console."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/glusterfs-driver.xml:6(title)
+msgid "GlusterFS driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/glusterfs-driver.xml:7(para)
+msgid "GlusterFS is an open-source scalable distributed file system that is able to grow to petabytes and beyond in size. More information can be found on <link href=\"http://www.gluster.org/\">Gluster's homepage</link>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/glusterfs-driver.xml:12(para)
+msgid "This driver enables use of GlusterFS in a similar fashion as the NFS driver. It supports basic volume operations, and like NFS, does not support snapshot/clone."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/glusterfs-driver.xml:16(para)
+msgid "You must use a Linux kernel of version 3.4 or greater (or version 2.6.32 or greater in Red Hat Enterprise Linux/CentOS 6.3+) when working with Gluster-based volumes. See <link href=\"https://bugs.launchpad.net/nova/+bug/1177103\">Bug 1177103</link> for more information."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/glusterfs-driver.xml:22(para)
+msgid "To use Block Storage with GlusterFS, first set the <literal>volume_driver</literal> in <filename>cinder.conf</filename>:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/glusterfs-driver.xml:26(para)
+msgid "The following table contains the configuration options supported by the GlusterFS driver."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:4(title)
+msgid "NFS driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:5(para)
+msgid "The Network File System (NFS) is a distributed file system protocol originally developed by Sun Microsystems in 1984. An NFS server <emphasis>exports</emphasis> one or more of its file systems, known as <emphasis>shares</emphasis>. An NFS client can mount these exported shares on its own file system. You can perform file actions on this mounted remote file system as if the file system were local."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:13(title)
+msgid "How the NFS driver works"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:14(para)
+msgid "The NFS driver, and other drivers based on it, work quite differently than a traditional block storage driver."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:17(para)
+msgid "The NFS driver does not actually allow an instance to access a storage device at the block level. Instead, files are created on an NFS share and mapped to instances, which emulates a block device. This works in a similar way to QEMU, which stores instances in the <filename>/var/lib/nova/instances</filename> directory."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:26(title)
+msgid "Enable the NFS driver and related options"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:27(para)
+msgid "To use Cinder with the NFS driver, first set the <literal>volume_driver</literal> in <filename>cinder.conf</filename>:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:31(para)
+msgid "The following table contains the options supported by the NFS driver."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:36(para)
+msgid "As of the Icehouse release, the NFS driver (and other drivers based off it) will attempt to mount shares using version 4.1 of the NFS protocol (including pNFS). If the mount attempt is unsuccessful due to a lack of client or server support, a subsequent mount attempt that requests the default behavior of the <placeholder-1/> command will be performed. On most distributions, the default behavior is to attempt mounting first with NFS v4.0, then silently fall back to NFS v3.0 if necessary. If the <option>nfs_mount_options</option> configuration option contains a request for a specific version of NFS to be used, or if specific options are specified in the shares configuration file specified by the <option>nfs_shares_config</option> configuration option, the mount will be attempted as requested with no subsequent attempts."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:55(title)
+msgid "How to use the NFS driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:58(para)
+msgid "Access to one or more NFS servers. Creating an NFS server is outside the scope of this document. This example assumes access to the following NFS servers and mount points:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:64(literal)
+msgid "192.168.1.200:/storage"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:67(literal)
+msgid "192.168.1.201:/storage"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:70(literal)
+msgid "192.168.1.202:/storage"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:73(para)
+msgid "This example demonstrates the use of with this driver with multiple NFS servers. Multiple servers are not required. One is usually enough."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:78(para)
+msgid "Add your list of NFS servers to the file you specified with the <literal>nfs_shares_config</literal> option. For example, if the value of this option was set to <literal>/etc/cinder/shares.txt</literal>, then:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:88(para)
+msgid "Comments are allowed in this file. They begin with a <literal>#</literal>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:92(para)
+msgid "Configure the <literal>nfs_mount_point_base</literal> option. This is a directory where <systemitem class=\"service\">cinder-volume</systemitem> mounts all NFS shares stored in <literal>shares.txt</literal>. For this example, <literal>/var/lib/cinder/nfs</literal> is used. You can, of course, use the default value of <literal>$state_path/mnt</literal>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:103(para)
+msgid "Start the <systemitem class=\"service\">cinder-volume</systemitem> service. <literal>/var/lib/cinder/nfs</literal> should now contain a directory for each NFS share specified in <literal>shares.txt</literal>. The name of each directory is a hashed name:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:115(para)
+msgid "You can now create volumes as you normally would:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:120(para)
+msgid "This volume can also be attached and deleted just like other volumes. However, snapshotting is <emphasis>not</emphasis> supported."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:127(title)
+msgid "NFS driver notes"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:130(para)
+msgid "<systemitem class=\"service\">cinder-volume</systemitem> manages the mounting of the NFS shares as well as volume creation on the shares. Keep this in mind when planning your OpenStack architecture. If you have one master NFS server, it might make sense to only have one <systemitem class=\"service\">cinder-volume</systemitem> service to handle all requests to that NFS server. However, if that single server is unable to handle all requests, more than one <systemitem class=\"service\">cinder-volume</systemitem> service is needed as well as potentially more than one NFS server."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:146(para)
+msgid "Because data is stored in a file and not actually on a block storage device, you might not see the same IO performance as you would with a traditional block storage driver. Please test accordingly."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:153(para)
+msgid "Despite possible IO performance loss, having volume data stored in a file might be beneficial. For example, backing up volumes can be as easy as copying the volume files."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:158(para)
+msgid "Regular IO flushing and syncing still stands."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:6(title)
+msgid "EMC VNX direct driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:7(para)
+msgid "Use the EMC VNX direct driver to create, attach, detach, and delete volumes, create and delete snapshots, and so on. This driver is based on the Cinder-defined <literal>ISCSIDriver</literal> driver."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:11(para)
+msgid "To complete volume operations, the driver uses the NaviSec command-line interface (CLI) to communicate with back-end EMC VNX storage."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:19(para)
+msgid "Flare version 5.32 or later."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:22(para)
+msgid "You must activate VNX Snapshot and Thin Provisioning license for the array. Ensure that all the iSCSI ports from the VNX are accessible through OpenStack hosts."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:27(para)
+msgid "Navisphere CLI v7.32 or later."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:30(para)
+msgid "EMC storage VNX Series are supported."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:71(title)
+msgid "Set up the VNX direct driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:72(para)
+msgid "Complete these high-level tasks to set up the VNX direct driver:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:76(para)
+msgid "Install NaviSecCLI. You must install the NaviSecCLI tool on the controller node and all the Cinder nodes in an OpenStack deployment. See <xref linkend=\"install-naviseccli\"/>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:83(para)
+msgid "Register with VNX. See <xref linkend=\"register-vnx-direct-iscsi\"/>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:89(title)
+msgid "Install NaviSecCLI"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:90(para)
+msgid "On Ubuntu x64, download the NaviSecCLI deb package from <link href=\"https://github.com/emc-openstack/naviseccli\">EMC's OpenStack Github</link> web site."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:92(para)
+msgid "For all the other variants of Linux, download the NaviSecCLI rpm package from EMC's support web site for <link href=\"https://support.emc.com/downloads/36656_VNX2-Series\">VNX2 series</link> or <link href=\"https://support.emc.com/downloads/12781_VNX1-Series\">VNX1 series</link>. Login is required."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:96(title)
+msgid "Register with VNX"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:97(para)
+msgid "To export a VNX volume to a compute node or a volume node, you must register the node with VNX."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:100(title)
+msgid "To register the node"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:101(para)
+msgid "On the compute node or volume node <literal>1.1.1.1</literal>, do the following (assume <literal>10.10.61.35</literal> is the iSCSI target):"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:120(para)
+msgid "Click <guibutton>Register</guibutton>, select <guilabel>CLARiiON/VNX</guilabel>, and enter the host name <literal>myhost1</literal> and IP address <literal>myhost1</literal>. Click <guibutton>Register</guibutton>. Now host <literal>1.1.1.1</literal> also appears under Hosts-&gt;Host List."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:144(para)
+msgid "For the VNX iSCSI driver, add the following entries, where <literal>10.10.61.35</literal> is the IP address of the VNX iSCSI target, <literal>10.10.72.41</literal> is the IP address of the VNX array (SPA or SPB), <systemitem>default_timeout</systemitem> is the default time out for CLI operations in minutes, and <systemitem>max_luns_per_storage_group</systemitem> is the default max number of LUNs in a storage group:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:164(para)
+msgid "To find out <literal>max_luns_per_storage_group </literal> for each VNX model, refer to the <link href=\"https://support.emc.com/search/?text=White%20Paper%20Introduction%20to%20the%20VNX%20Series\">EMC's support</link> web site (login is required)."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:174(para)
+msgid "Volume type support allows user to choose thick/thin provisioning capabilities."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:176(para)
+msgid "Here is an example of how to setup volume type. First create volume types. Then define extra specs for each volume type."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:180(title)
+msgid "To set up volume types"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:182(para)
+msgid "Setup volume types:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:187(para)
+msgid "Setup volume type extra specs:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:192(para)
+msgid "The previous example creates two volume types: <literal>TypeA</literal> and <literal>TypeB</literal>. For <literal>TypeA</literal>, <literal>storagetype:provisioning </literal> is set to <literal>thick</literal>. Similarly for <literal>TypeB</literal>, <literal>storagetype:provisioning </literal> is set to <literal>thin</literal>. If <literal> storagetype:provisioning</literal> is not specified, it will be default to <literal>thick</literal>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:5(title)
+msgid "IBM Storwize family and SVC volume driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:6(para)
+msgid "The volume management driver for Storwize family and SAN Volume Controller (SVC) provides OpenStack Compute instances with access to IBM Storwize family or SVC storage systems."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:11(title)
+msgid "Configure the Storwize family and SVC system"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:13(title)
+msgid "Network configuration"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:14(para)
+msgid "The Storwize family or SVC system must be configured for iSCSI, Fibre Channel, or both."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:16(para)
+msgid "If using iSCSI, each Storwize family or SVC node should have at least one iSCSI IP address. The IBM Storwize/SVC driver uses an iSCSI IP address associated with the volume's preferred node (if available) to attach the volume to the instance, otherwise it uses the first available iSCSI IP address of the system. The driver obtains the iSCSI IP address directly from the storage system; you do not need to provide these iSCSI IP addresses directly to the driver."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:27(para)
+msgid "If using iSCSI, ensure that the compute nodes have iSCSI network access to the Storwize family or SVC system."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:32(para)
+msgid "OpenStack Nova's Grizzly version supports iSCSI multipath. Once this is configured on the Nova host (outside the scope of this documentation), multipath is enabled."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:37(para)
+msgid "If using Fibre Channel (FC), each Storwize family or SVC node should have at least one WWPN port configured. If the <literal>storwize_svc_multipath_enabled</literal> flag is set to True in the Cinder configuration file, the driver uses all available WWPNs to attach the volume to the instance (details about the configuration flags appear in the <link linkend=\"ibm-storwize-svc-driver2\"> next section</link>). If the flag is not set, the driver uses the WWPN associated with the volume's preferred node (if available), otherwise it uses the first available WWPN of the system. The driver obtains the WWPNs directly from the storage system; you do not need to provide these WWPNs directly to the driver."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:54(para)
+msgid "If using FC, ensure that the compute nodes have FC connectivity to the Storwize family or SVC system."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:60(title)
+msgid "iSCSI CHAP authentication"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:75(para)
+msgid "Not all OpenStack Compute drivers support CHAP authentication. Please check compatibility before using."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:61(para)
+msgid "If using iSCSI for data access and the <literal>storwize_svc_iscsi_chap_enabled</literal> is set to <literal>True</literal>, the driver will associate randomly-generated CHAP secrets with all hosts on the Storwize family system. OpenStack compute nodes use these secrets when creating iSCSI connections. <placeholder-1/><placeholder-2/><placeholder-3/>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:87(title)
+msgid "Configure storage pools"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:88(para)
+msgid "Each instance of the IBM Storwize/SVC driver allocates all volumes in a single pool. The pool should be created in advance and be provided to the driver using the <literal>storwize_svc_volpool_name</literal> configuration flag. Details about the configuration flags and how to provide the flags to the driver appear in the <link linkend=\"ibm-storwize-svc-driver2\"> next section</link>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:99(title)
+msgid "Configure user authentication for the driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:101(para)
+msgid "The driver requires access to the Storwize family or SVC system management interface. The driver communicates with the management using SSH. The driver should be provided with the Storwize family or SVC management IP using the <literal>san_ip</literal> flag, and the management port should be provided by the <literal>san_ssh_port</literal> flag. By default, the port value is configured to be port 22 (SSH)."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:111(para)
+msgid "Make sure the compute node running the <systemitem class=\"service\">cinder-volume</systemitem> management driver has SSH network access to the storage system."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:118(para)
+msgid "To allow the driver to communicate with the Storwize family or SVC system, you must provide the driver with a user on the storage system. The driver has two authentication methods: password-based authentication and SSH key pair authentication. The user should have an Administrator role. It is suggested to create a new user for the management driver. Please consult with your storage and security administrator regarding the preferred authentication method and how passwords or SSH keys should be stored in a secure manner."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:129(para)
+msgid "When creating a new user on the Storwize or SVC system, make sure the user belongs to the Administrator group or to another group that has an Administrator role."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:134(para)
+msgid "If using password authentication, assign a password to the user on the Storwize or SVC system. The driver configuration flags for the user and password are <literal>san_login</literal> and <literal>san_password</literal>, respectively."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:140(para)
+msgid "If you are using the SSH key pair authentication, create SSH private and public keys using the instructions below or by any other method. Associate the public key with the user by uploading the public key: select the \"choose file\" option in the Storwize family or SVC management GUI under \"SSH public key\". Alternatively, you may associate the SSH public key using the command line interface; details can be found in the Storwize and SVC documentation. The private key should be provided to the driver using the <literal>san_private_key</literal> configuration flag."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:154(title)
+msgid "Create a SSH key pair with OpenSSH"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:155(para)
+msgid "You can create an SSH key pair using OpenSSH, by running:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:158(para)
+msgid "The command prompts for a file to save the key pair. For example, if you select 'key' as the filename, two files are created: <literal>key</literal> and <literal>key.pub</literal>. The <literal>key</literal> file holds the private SSH key and <literal>key.pub</literal> holds the public SSH key."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:165(para)
+msgid "The command also prompts for a pass phrase, which should be empty."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:167(para)
+msgid "The private key file should be provided to the driver using the <literal>san_private_key</literal> configuration flag. The public key should be uploaded to the Storwize family or SVC system using the storage management GUI or command line interface."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:173(para)
+msgid "Ensure that Cinder has read permissions on the private key file."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:179(title)
+msgid "Configure the Storwize family and SVC driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:181(title)
+msgid "Enable the Storwize family and SVC driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:182(para)
+msgid "Set the volume driver to the Storwize family and SVC driver by setting the <literal>volume_driver</literal> option in <filename>cinder.conf</filename> as follows:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:189(title)
+msgid "Storwize family and SVC driver options in cinder.conf"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:191(para)
+msgid "The following options specify default values for all volumes. Some can be over-ridden using volume types, which are described below."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:195(caption)
+msgid "List of configuration flags for Storwize storage and SVC driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:211(literal)
+msgid "san_ip"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:215(para)
+msgid "Management IP or host name"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:219(literal)
+msgid "san_ssh_port"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:222(para)
+msgid "22"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:223(para)
+msgid "Management port"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:226(literal)
+msgid "san_login"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:230(para)
+msgid "Management login username"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:234(literal)
+msgid "san_password"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:238(para)
+msgid "The authentication requires either a password (<literal>san_password</literal>) or SSH private key (<literal>san_private_key</literal>). One must be specified. If both are specified, the driver uses only the SSH private key."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:236(para)
+msgid "Required <placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:248(para)
+msgid "Management login password"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:252(literal)
+msgid "san_private_key"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:254(para)
+msgid "Required <footnoteref linkend=\"storwize-svc-fn1\"/>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:258(para)
+msgid "Management login SSH private key"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:264(literal)
+msgid "storwize_svc_volpool_name"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:268(para)
+msgid "Default pool name for volumes"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:273(literal)
+msgid "storwize_svc_vol_rsize"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:276(para)
+msgid "2"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:280(para)
+msgid "The driver creates thin-provisioned volumes by default. The <literal>storwize_svc_vol_rsize</literal> flag defines the initial physical allocation percentage for thin-provisioned volumes, or if set to <literal>-1</literal>, the driver creates full allocated volumes. More details about the available options are available in the Storwize family and SVC documentation."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:277(para)
+msgid "Initial physical allocation (percentage) <placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:297(literal)
+msgid "storwize_svc_vol_warning"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:300(para)
+msgid "0 (disabled)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:301(para)
+msgid "Space allocation warning threshold (percentage) <footnoteref linkend=\"storwize-svc-fn3\"/>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:308(literal)
+msgid "storwize_svc_vol_autoexpand"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:311(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:367(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:427(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:453(para)
+msgid "True"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:314(para)
+msgid "Defines whether thin-provisioned volumes can be auto expanded by the storage system, a value of <literal>True</literal> means that auto expansion is enabled, a value of <literal>False</literal> disables auto expansion. Details about this option can be found in the <literal>–autoexpand</literal> flag of the Storwize family and SVC command line interface <literal>mkvdisk</literal> command."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:312(para)
+msgid "Enable or disable volume auto expand <placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:332(literal)
+msgid "storwize_svc_vol_grainsize"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:335(para)
+msgid "256"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:336(para)
+msgid "Volume grain size <footnoteref linkend=\"storwize-svc-fn3\"/> in KB"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:342(literal)
+msgid "storwize_svc_vol_compression"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:346(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:437(para) ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:88(replaceable)
+msgid "False"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:350(para)
+msgid "Defines whether Real-time Compression is used for the volumes created with OpenStack. Details on Real-time Compression can be found in the Storwize family and SVC documentation. The Storwize or SVC system must have compression enabled for this feature to work."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:347(para)
+msgid "Enable or disable Real-time Compression <placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:364(literal)
+msgid "storwize_svc_vol_easytier"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:370(para)
+msgid "Defines whether Easy Tier is used for the volumes created with OpenStack. Details on EasyTier can be found in the Storwize family and SVC documentation. The Storwize or SVC system must have Easy Tier enabled for this feature to work."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:368(para)
+msgid "Enable or disable Easy Tier <placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:382(literal)
+msgid "storwize_svc_vol_iogrp"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:386(para)
+msgid "The I/O group in which to allocate vdisks"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:391(literal)
+msgid "storwize_svc_flashcopy_timeout"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:395(para)
+msgid "120"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:398(para)
+msgid "The driver wait timeout threshold when creating an OpenStack snapshot. This is actually the maximum amount of time that the driver waits for the Storwize family or SVC system to prepare a new FlashCopy mapping. The driver accepts a maximum wait time of 600 seconds (10 minutes)."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:396(para)
+msgid "FlashCopy timeout threshold <placeholder-1/> (seconds)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:412(literal)
+msgid "storwize_svc_connection_protocol"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:417(para)
+msgid "Connection protocol to use (currently supports 'iSCSI' or 'FC')"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:423(literal)
+msgid "storwize_svc_iscsi_chap_enabled"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:428(para)
+msgid "Configure CHAP authentication for iSCSI connections"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:433(literal)
+msgid "storwize_svc_multipath_enabled"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:440(para)
+msgid "Multipath for iSCSI connections requires no storage-side configuration and is enabled if the compute host has multipath configured."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:438(para)
+msgid "Enable multipath for FC connections <placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:449(literal)
+msgid "storwize_svc_multihost_enabled"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:457(para)
+msgid "This option allows the driver to map a vdisk to more than one host at a time. This scenario occurs during migration of a virtual machine with an attached volume; the volume is simultaneously mapped to both the source and destination compute hosts. If your deployment does not require attaching vdisks to multiple hosts, setting this flag to False will provide added safety."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:454(para)
+msgid "Enable mapping vdisks to multiple hosts <placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:478(title)
+msgid "Placement with volume types"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:479(para)
+msgid "The IBM Storwize/SVC driver exposes capabilities that can be added to the <literal>extra specs</literal> of volume types, and used by the filter scheduler to determine placement of new volumes. Make sure to prefix these keys with <literal>capabilities:</literal> to indicate that the scheduler should use them. The following <literal>extra specs</literal> are supported:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:490(para)
+msgid "capabilities:volume_back-end_name - Specify a specific back-end where the volume should be created. The back-end name is a concatenation of the name of the IBM Storwize/SVC storage system as shown in <literal>lssystem</literal>, an underscore, and the name of the pool (mdisk group). For example: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:501(para)
+msgid "capabilities:compression_support - Specify a back-end according to compression support. A value of <literal>True</literal> should be used to request a back-end that supports compression, and a value of <literal>False</literal> will request a back-end that does not support compression. If you do not have constraints on compression support, do not set this key. Note that specifying <literal>True</literal> does not enable compression; it only requests that the volume be placed on a back-end that supports compression. Example syntax: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:517(para)
+msgid "capabilities:easytier_support - Similar semantics as the <literal>compression_support</literal> key, but for specifying according to support of the Easy Tier feature. Example syntax: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:525(para)
+msgid "capabilities:storage_protocol - Specifies the connection protocol used to attach volumes of this type to instances. Legal values are <literal>iSCSI</literal> and <literal>FC</literal>. This <literal>extra specs</literal> value is used for both placement and setting the protocol used for this volume. In the example syntax, note &lt;in&gt; is used as opposed to &lt;is&gt; used in the previous examples. <placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:540(title)
+msgid "Configure per-volume creation options"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:541(para)
+msgid "Volume types can also be used to pass options to the IBM Storwize/SVC driver, which over-ride the default values set in the configuration file. Contrary to the previous examples where the \"capabilities\" scope was used to pass parameters to the Cinder scheduler, options can be passed to the IBM Storwize/SVC driver with the \"drivers\" scope."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:548(para)
+msgid "The following <literal>extra specs</literal> keys are supported by the IBM Storwize/SVC driver:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:552(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:662(para)
+msgid "rsize"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:555(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:665(para)
+msgid "warning"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:558(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:668(para)
+msgid "autoexpand"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:561(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:671(para)
+msgid "grainsize"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:564(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:674(para)
+msgid "compression"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:567(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:677(para)
+msgid "easytier"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:570(para)
+msgid "multipath"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:573(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:680(para)
+msgid "iogrp"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:576(para)
+msgid "These keys have the same semantics as their counterparts in the configuration file. They are set similarly; for example, <literal>rsize=2</literal> or <literal>compression=False</literal>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:582(title)
+msgid "Example: Volume types"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:583(para)
+msgid "In the following example, we create a volume type to specify a controller that supports iSCSI and compression, to use iSCSI when attaching the volume, and to enable compression:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:589(para)
+msgid "We can then create a 50GB volume using this type:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:593(para)
+msgid "Volume types can be used, for example, to provide users with different"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:597(para)
+msgid "performance levels (such as, allocating entirely on an HDD tier, using Easy Tier for an HDD-SDD mix, or allocating entirely on an SSD tier)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:603(para)
+msgid "resiliency levels (such as, allocating volumes in pools with different RAID levels)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:608(para)
+msgid "features (such as, enabling/disabling Real-time Compression)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:615(title)
+msgid "Operational notes for the Storwize family and SVC driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:618(title)
+msgid "Migrate volumes"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:619(para)
+msgid "In the context of OpenStack Block Storage's volume migration feature, the IBM Storwize/SVC driver enables the storage's virtualization technology. When migrating a volume from one pool to another, the volume will appear in the destination pool almost immediately, while the storage moves the data in the background."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:627(para)
+msgid "To enable this feature, both pools involved in a given volume migration must have the same values for <literal>extent_size</literal>. If the pools have different values for <literal>extent_size</literal>, the data will still be moved directly between the pools (not host-side copy), but the operation will be synchronous."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:639(para)
+msgid "The IBM Storwize/SVC driver allows for extending a volume's size, but only for volumes without snapshots."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:645(para)
+msgid "Snapshots are implemented using FlashCopy with no background copy (space-efficient). Volume clones (volumes created from existing volumes) are implemented with FlashCopy, but with background copy enabled. This means that volume clones are independent, full copies. While this background copy is taking place, attempting to delete or extend the source volume will result in that operation waiting for the copy to complete."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:657(para)
+msgid "The IBM Storwize/SVC driver enables you to modify volume types. When you modify volume types, you can also change these extra specs properties:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:684(para)
+msgid "When you change the <literal>rsize</literal>, <literal>grainsize</literal> or <literal>compression</literal> properties, volume copies are asynchronously synchronized on the array."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:691(para)
+msgid "To change the <literal>iogrp</literal> property, IBM Storwize/SVC firmware version 6.4.0 or later is required."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:5(title)
+msgid "NetApp unified driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:6(para)
+msgid "The NetApp unified driver is a block storage driver that supports multiple storage families and protocols. A storage family corresponds to storage systems built on different NetApp technologies such as clustered Data ONTAP, Data ONTAP operating in 7-Mode, and E-Series. The storage protocol refers to the protocol used to initiate data storage and access operations on those storage systems like iSCSI and NFS. The NetApp unified driver can be configured to provision and manage OpenStack volumes on a given storage family using a specified storage protocol. The OpenStack volumes can then be used for accessing and storing data using the storage protocol on the storage family system. The NetApp unified driver is an extensible interface that can support new storage families and protocols."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:21(title)
+msgid "NetApp clustered Data ONTAP storage family"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:22(para)
+msgid "The NetApp clustered Data ONTAP storage family represents a configuration group which provides OpenStack compute instances access to clustered Data ONTAP storage systems. At present it can be configured in OpenStack Block Storage to work with iSCSI and NFS storage protocols."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:28(title)
+msgid "NetApp iSCSI configuration for clustered Data ONTAP"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:30(para)
+msgid "The NetApp iSCSI configuration for clustered Data ONTAP is an interface from OpenStack to clustered Data ONTAP storage systems for provisioning and managing the SAN block storage entity; that is, a NetApp LUN which can be accessed using the iSCSI protocol."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:35(para)
+msgid "The iSCSI configuration for clustered Data ONTAP is a direct interface from OpenStack Block Storage to the clustered Data ONTAP instance and as such does not require additional management software to achieve the desired functionality. It uses NetApp APIs to interact with the clustered Data ONTAP instance."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:42(title)
+msgid "Configuration options for clustered Data ONTAP family with iSCSI protocol"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:44(para)
+msgid "Configure the volume driver, storage family and storage protocol to the NetApp unified driver, clustered Data ONTAP, and iSCSI respectively by setting the <option>volume_driver</option>, <option>netapp_storage_family</option> and <option>netapp_storage_protocol</option> options in <filename>cinder.conf</filename> as follows:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:56(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:120(replaceable)
+msgid "openstack-vserver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:57(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:121(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:340(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:396(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:456(replaceable)
+msgid "myhostname"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:63(para) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:346(para) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:471(para)
+msgid "You must override the default value of <option>netapp_storage_protocol</option> with <literal>iscsi</literal> in order to utilize the iSCSI protocol."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:71(para) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:137(para)
+msgid "If you specify an account in the <option>netapp_login</option> that only has virtual storage server (Vserver) administration privileges (rather than cluster-wide administration privileges), some advanced features of the NetApp unified driver will not work and you may see warnings in the OpenStack Block Storage logs."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:81(para) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:256(para)
+msgid "For more information on these options and other deployment and operational scenarios, visit the <link href=\"https://communities.netapp.com/groups/openstack\"> OpenStack NetApp community</link>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:91(title)
+msgid "NetApp NFS configuration for clustered Data ONTAP"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:93(para)
+msgid "The NetApp NFS configuration for clustered Data ONTAP is an interface from OpenStack to a clustered Data ONTAP system for provisioning and managing OpenStack volumes on NFS exports provided by the clustered Data ONTAP system that are accessed using the NFS protocol."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:99(para)
+msgid "The NFS configuration for clustered Data ONTAP is a direct interface from OpenStack Block Storage to the clustered Data ONTAP instance and as such does not require any additional management software to achieve the desired functionality. It uses NetApp APIs to interact with the clustered Data ONTAP instance."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:106(title)
+msgid "Configuration options for the clustered Data ONTAP family with NFS protocol"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:108(para)
+msgid "Configure the volume driver, storage family and storage protocol to NetApp unified driver, clustered Data ONTAP, and NFS respectively by setting the <option>volume_driver</option>, <option>netapp_storage_family</option> and <option>netapp_storage_protocol</option> options in <filename>cinder.conf</filename> as follows:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:125(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:400(replaceable)
+msgid "/etc/cinder/nfs_shares"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:130(para) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:405(para)
+msgid "Additional NetApp NFS configuration options are shared with the generic NFS driver. These options can be found here: <xref linkend=\"config_table_cinder_storage_nfs\"/>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:148(title)
+msgid "NetApp NFS Copy Offload client"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:149(para)
+msgid "A feature was added in the Icehouse release of the NetApp unified driver that enables Image Service images to be efficiently copied to a destination Block Storage volume. When the Block Storage and Image Service are configured to use the NetApp NFS Copy Offload client, a controller-side copy will be attempted before reverting to downloading the image from the Image Service. This improves image provisioning times while reducing the consumption of bandwidth and CPU cycles on the host(s) running the Image and Block Storage services. This is due to the copy operation being performed completely within the storage cluster."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:158(para)
+msgid "The NetApp NFS Copy Offload client can be used in either of the following scenarios:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:162(para)
+msgid "The Image Service is configured to store images in an NFS share that is exported from a NetApp FlexVol volume <emphasis>and</emphasis> the destination for the new Block Storage volume will be on an NFS share exported from a different FlexVol volume than the one used by the Image Service. Both FlexVols must be located within the same cluster."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:169(para)
+msgid "The source image from the Image Service has already been cached in an NFS image cache within a Block Storage backend. The cached image resides on a different FlexVol volume than the destination for the new Block Storage volume. Both FlexVols must be located within the same cluster."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:175(para)
+msgid "To use this feature, you must configure the Image Service, as follows:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:179(para)
+msgid "Set the <option>default_store</option> configuration option to <literal>file</literal>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:184(para)
+msgid "Set the <option>filesystem_store_datadir</option> configuration option to the path to the Image Service NFS export."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:189(para)
+msgid "Set the <option>show_image_direct_url</option> configuration option to <literal>True</literal>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:194(para)
+msgid "Set the <option>show_multiple_locations</option> configuration option to <literal>True</literal>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:199(para)
+msgid "Set the <option>filesystem_store_metadata_file</option> configuration option to a metadata file. The metadata file should contain a JSON object that contains the correct information about the NFS export used by the Image Service, similar to:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:207(replaceable)
+msgid "nfs://192.168.0.1/myGlanceExport"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:208(replaceable)
+msgid "/var/lib/glance/images"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:213(para)
+msgid "To use this feature, you must configure the Block Storage service, as follows:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:217(para)
+msgid "Set the <option>netapp_copyoffload_tool_path</option> configuration option to the path to the NetApp Copy Offload binary."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:222(para)
+msgid "Set the <option>glance_api_version</option> configuration option to <literal>2</literal>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:228(para)
+msgid "This feature requires that:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:231(para)
+msgid "The storage system must have Data ONTAP v8.2 or greater installed."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:235(para)
+msgid "The vStorage feature must be enabled on each storage virtual machine (SVM, also known as a Vserver) that is permitted to interact with the copy offload client."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:242(para)
+msgid "To configure the copy offload workflow, enable NFS v4.0 or greater and export it from the SVM."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:249(para)
+msgid "To download the NetApp copy offload binary to be utilized in conjunction with the <option>netapp_copyoffload_tool_path</option> configuration option, please visit the download page at the <link href=\"https://communities.netapp.com/docs/DOC-33412\">NetApp OpenStack Community site</link>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:264(title)
+msgid "NetApp-supported extra specs for clustered Data ONTAP"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:266(para)
+msgid "Extra specs enable vendors to specify extra filter criteria that the Block Storage scheduler uses when it determines which volume node should fulfill a volume provisioning request. When you use the NetApp unified driver with a clustered Data ONTAP storage system, you can leverage extra specs with OpenStack Block Storage volume types to ensure that OpenStack Block Storage volumes are created on storage back ends that have certain properties. For example, when you configure QoS, mirroring, or compression for a storage back end."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:276(para)
+msgid "Extra specs are associated with OpenStack Block Storage volume types, so that when users request volumes of a particular volume type, the volumes are created on storage back ends that meet the list of requirements. For example, the back ends have the available space or extra specs. You can use the specs in the following table when you define OpenStack Block Storage volume types by using the <placeholder-1/> command."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:287(para)
+msgid "It is recommended to only set the value of extra specs to <literal>True</literal> when combining multiple specs to enforce a certain logic set. If you desire to remove volumes with a certain feature enabled from consideration from the OpenStack Block Storage volume scheduler, be sure to use the negated spec name with a value of <literal>True</literal> rather than setting the positive spec to a value of <literal>False</literal>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:300(title)
+msgid "NetApp Data ONTAP operating in 7-Mode storage family"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:302(para)
+msgid "The NetApp Data ONTAP operating in 7-Mode storage family represents a configuration group which provides OpenStack compute instances access to 7-Mode storage systems. At present it can be configured in OpenStack Block Storage to work with iSCSI and NFS storage protocols."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:308(title)
+msgid "NetApp iSCSI configuration for Data ONTAP operating in 7-Mode"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:310(para)
+msgid "The NetApp iSCSI configuration for Data ONTAP operating in 7-Mode is an interface from OpenStack to Data ONTAP operating in 7-Mode storage systems for provisioning and managing the SAN block storage entity, that is, a LUN which can be accessed using iSCSI protocol."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:316(para)
+msgid "The iSCSI configuration for Data ONTAP operating in 7-Mode is a direct interface from OpenStack to Data ONTAP operating in 7-Mode storage system and it does not require additional management software to achieve the desired functionality. It uses NetApp ONTAPI to interact with the Data ONTAP operating in 7-Mode storage system."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:324(title)
+msgid "Configuration options for the Data ONTAP operating in 7-Mode storage family with iSCSI protocol"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:327(para)
+msgid "Configure the volume driver, storage family and storage protocol to the NetApp unified driver, Data ONTAP operating in 7-Mode, and iSCSI respectively by setting the <option>volume_driver</option>, <option>netapp_storage_family</option> and <option>netapp_storage_protocol</option> options in <filename>cinder.conf</filename> as follows:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:354(para) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:412(para)
+msgid "For more information on these options and other deployment and operational scenarios, visit the <link href=\"https://communities.netapp.com/groups/openstack\">OpenStack NetApp community</link>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:363(title)
+msgid "NetApp NFS configuration for Data ONTAP operating in 7-Mode"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:365(para)
+msgid "The NetApp NFS configuration for Data ONTAP operating in 7-Mode is an interface from OpenStack to Data ONTAP operating in 7-Mode storage system for provisioning and managing OpenStack volumes on NFS exports provided by the Data ONTAP operating in 7-Mode storage system which can then be accessed using NFS protocol."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:372(para)
+msgid "The NFS configuration for Data ONTAP operating in 7-Mode is a direct interface from OpenStack Block Storage to the Data ONTAP operating in 7-Mode instance and as such does not require any additional management software to achieve the desired functionality. It uses NetApp ONTAPI to interact with the Data ONTAP operating in 7-Mode storage system."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:380(title)
+msgid "Configuration options for the Data ONTAP operating in 7-Mode family with NFS protocol"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:383(para)
+msgid "Configure the volume driver, storage family and storage protocol to the NetApp unified driver, Data ONTAP operating in 7-Mode, and NFS respectively by setting the <option>volume_driver</option>, <option>netapp_storage_family</option> and <option>netapp_storage_protocol</option> options in <filename>cinder.conf</filename> as follows:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:422(title)
+msgid "NetApp E-Series storage family"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:423(para)
+msgid "The NetApp E-Series storage family represents a configuration group which provides OpenStack compute instances access to E-Series storage systems. At present it can be configured in OpenStack Block Storage to work with the iSCSI storage protocol."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:429(title)
+msgid "NetApp iSCSI configuration for E-Series"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:430(para)
+msgid "The NetApp iSCSI configuration for E-Series is an interface from OpenStack to E-Series storage systems for provisioning and managing the SAN block storage entity; that is, a NetApp LUN which can be accessed using the iSCSI protocol."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:435(para)
+msgid "The iSCSI configuration for E-Series is an interface from OpenStack Block Storage to the E-Series proxy instance and as such requires the deployment of the proxy instance in order to achieve the desired functionality. The driver uses REST APIs to interact with the E-Series proxy instance, which in turn interacts directly with the E-Series controllers."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:442(title)
+msgid "Configuration options for E-Series storage family with iSCSI protocol"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:444(para)
+msgid "Configure the volume driver, storage family and storage protocol to the NetApp unified driver, E-Series, and iSCSI respectively by setting the <option>volume_driver</option>, <option>netapp_storage_family</option> and <option>netapp_storage_protocol</option> options in <filename>cinder.conf</filename> as follows:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:460(replaceable)
+msgid "1.2.3.4,5.6.7.8"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:461(replaceable)
+msgid "arrayPassword"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:462(replaceable)
+msgid "pool1,pool2"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:465(para)
+msgid "You must override the default value of <option>netapp_storage_family</option> with <literal>eseries</literal> in order to utilize the E-Series driver."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:479(para)
+msgid "For more information on these options and other deployment and operational scenarios, visit the <link href=\"https://communities.netapp.com/groups/openstack\"> OpenStack NetApp community.</link>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:490(title)
+msgid "Upgrading prior NetApp drivers to the NetApp unified driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:492(para)
+msgid "NetApp introduced a new unified block storage driver in Havana for configuring different storage families and storage protocols. This requires defining upgrade path for NetApp drivers which existed in releases prior to Havana. This section covers the upgrade configuration for NetApp drivers to the new unified configuration and a list of deprecated NetApp drivers."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:500(title)
+msgid "Upgraded NetApp drivers"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:501(para)
+msgid "This section describes how to update OpenStack Block Storage configuration from a pre-Havana release to the new unified driver format."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:505(title)
+msgid "Driver upgrade configuration"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:508(para)
+msgid "NetApp iSCSI direct driver for Clustered Data ONTAP in Grizzly (or earlier)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:513(para) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:527(para) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:542(para) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:557(para)
+msgid "NetApp Unified Driver configuration"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:522(para)
+msgid "NetApp NFS direct driver for Clustered Data ONTAP in Grizzly (or earlier)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:536(para)
+msgid "NetApp iSCSI direct driver for Data ONTAP operating in 7-Mode storage controller in Grizzly (or earlier)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:551(para)
+msgid "NetApp NFS direct driver for Data ONTAP operating in 7-Mode storage controller in Grizzly (or earlier)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:570(title)
+msgid "Deprecated NetApp drivers"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:571(para)
+msgid "This section lists the NetApp drivers in previous releases that are deprecated in Havana."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:575(para)
+msgid "NetApp iSCSI driver for clustered Data ONTAP."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:582(para)
+msgid "NetApp NFS driver for clustered Data ONTAP."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:589(para)
+msgid "NetApp iSCSI driver for Data ONTAP operating in 7-Mode storage controller."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:596(para)
+msgid "NetApp NFS driver for Data ONTAP operating in 7-Mode storage controller."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:604(para)
+msgid "See the <link href=\"https://communities.netapp.com/groups/openstack\">OpenStack NetApp community</link> for support information on deprecated NetApp drivers in the Havana release."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/lvm-volume-driver.xml:6(title)
+msgid "LVM"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/lvm-volume-driver.xml:7(para)
+msgid "The default volume back-end uses local volumes managed by LVM."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/lvm-volume-driver.xml:8(para)
+msgid "This driver supports different transport protocols to attach volumes, currently ISCSI and ISER."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/lvm-volume-driver.xml:10(para)
+msgid "Set the following in your <filename>cinder.conf</filename>, and use the following options to configure for ISCSI transport:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/lvm-volume-driver.xml:16(para)
+msgid "and for the ISER transport:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:4(title)
+msgid "XenAPI Storage Manager volume driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:5(para)
+msgid "The Xen Storage Manager volume driver (xensm) is a XenAPI hypervisor specific volume driver, and can be used to provide basic storage functionality, including volume creation and destruction, on a number of different storage back-ends. It also enables the capability of using more sophisticated storage back-ends for operations like cloning/snapshots, and so on. Some of the storage plug-ins that are already supported in Citrix XenServer and Xen Cloud Platform (XCP) are:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:15(para)
+msgid "NFS VHD: Storage repository (SR) plug-in that stores disks as Virtual Hard Disk (VHD) files on a remote Network File System (NFS)."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:20(para)
+msgid "Local VHD on LVM: SR plug-in that represents disks as VHD disks on Logical Volumes (LVM) within a locally-attached Volume Group."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:25(para)
+msgid "HBA LUN-per-VDI driver: SR plug-in that represents Logical Units (LUs) as Virtual Disk Images (VDIs) sourced by host bus adapters (HBAs). For example, hardware-based iSCSI or FC support."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:31(para)
+msgid "NetApp: SR driver for mapping of LUNs to VDIs on a NETAPP server, providing use of fast snapshot and clone features on the filer."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:36(para)
+msgid "LVHD over FC: SR plug-in that represents disks as VHDs on Logical Volumes within a Volume Group created on an HBA LUN. For example, hardware-based iSCSI or FC support."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:42(para)
+msgid "iSCSI: Base ISCSI SR driver, provides a LUN-per-VDI. Does not support creation of VDIs but accesses existing LUNs on a target."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:47(para)
+msgid "LVHD over iSCSI: SR plug-in that represents disks as Logical Volumes within a Volume Group created on an iSCSI LUN."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:52(para)
+msgid "EqualLogic: SR driver for mapping of LUNs to VDIs on a EQUALLOGIC array group, providing use of fast snapshot and clone features on the array."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:58(title)
+msgid "Design and operation"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:60(title)
+msgid "Definitions"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:63(para)
+msgid "<emphasis role=\"bold\">Back-end:</emphasis> A term for a particular storage back-end. This could be iSCSI, NFS, NetApp, and so on."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:68(para)
+msgid "<emphasis role=\"bold\">Back-end-config:</emphasis> All the parameters required to connect to a specific back-end. For example, for NFS, this would be the server, path, and so on."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:75(para)
+msgid "<emphasis role=\"bold\">Flavor:</emphasis> This term is equivalent to volume \"types\". A user friendly term to specify some notion of quality of service. For example, \"gold\" might mean that the volumes use a back-end where backups are possible. A flavor can be associated with multiple back-ends. The volume scheduler, with the help of the driver, decides which back-end is used to create a volume of a particular flavor. Currently, the driver uses a simple \"first-fit\" policy, where the first back-end that can successfully create this volume is the one that is used."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:93(title)
+msgid "Operation"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:94(para)
+msgid "The admin uses the nova-manage command detailed below to add flavors and back-ends."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:96(para)
+msgid "One or more <systemitem class=\"service\">cinder-volume</systemitem> service instances are deployed for each availability zone. When an instance is started, it creates storage repositories (SRs) to connect to the back-ends available within that zone. All <systemitem class=\"service\">cinder-volume</systemitem> instances within a zone can see all the available back-ends. These instances are completely symmetric and hence should be able to service any <literal>create_volume</literal> request within the zone."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:108(title)
+msgid "On XenServer, PV guests required"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:109(para)
+msgid "Note that when using XenServer you can only attach a volume to a PV guest."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:115(title)
+msgid "Configure XenAPI Storage Manager"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:117(title) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:291(title)
+msgid "Prerequisites"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:120(para)
+msgid "xensm requires that you use either Citrix XenServer or XCP as the hypervisor. The NetApp and EqualLogic back-ends are not supported on XCP."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:126(para)
+msgid "Ensure all <emphasis role=\"bold\">hosts</emphasis> running volume and Compute services have connectivity to the storage system."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:141(systemitem) ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:181(systemitem) ./doc/config-reference/compute/section_nova-log-files.xml:65(systemitem)
+msgid "nova-compute"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:138(emphasis)
+msgid "Set the following configuration options for the nova volume service: (<placeholder-1/> also requires the volume_driver configuration option.)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:152(emphasis)
+msgid "You must create the back-end configurations that the volume driver uses before you start the volume service."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:161(para)
+msgid "SR type and configuration connection parameters are in keeping with the <link href=\"http://support.citrix.com/article/CTX124887\">XenAPI Command Line Interface</link>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:168(para)
+msgid "Example: For the NFS storage manager plug-in, run these commands:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:177(emphasis)
+msgid "Start <placeholder-1/> and <placeholder-2/> with the new configuration options."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:188(title)
+msgid "Create and access the volumes from VMs"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:189(para)
+msgid "Currently, the flavors have not been tied to the volume types API. As a result, we simply end up creating volumes in a \"first fit\" order on the given back-ends."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:193(para)
+msgid "Use the standard <placeholder-1/> or OpenStack API commands (such as volume extensions) to create, destroy, attach, or detach volumes."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-msa-driver.xml:4(title)
+msgid "HP MSA Fibre Channel driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-msa-driver.xml:5(para)
+msgid "The HP MSA fiber channel driver runs volume operations on the storage array over HTTP."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-msa-driver.xml:7(para)
+msgid "A VDisk must be created on the HP MSA array first. This can be done using the web interface or the command-line interface of the array."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-msa-driver.xml:9(para)
+msgid "The following options must be defined in the <systemitem>cinder-volume</systemitem> configuration file (<filename>/etc/cinder/cinder.conf</filename>):"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-msa-driver.xml:14(para)
+msgid "Set the <option>volume_driver</option> option to <literal>cinder.volume.drivers.san.hp.hp_msa_fc.HPMSAFCDriver</literal>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-msa-driver.xml:19(para)
+msgid "Set the <option>san_ip</option> option to the hostname or IP address of your HP MSA array."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-msa-driver.xml:23(para)
+msgid "Set the <option>san_login</option> option to the login of an existing user of the HP MSA array."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/hp-msa-driver.xml:28(para)
+msgid "Set the <option>san_password</option> option to the password for this user."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:6(title)
+msgid "Dell EqualLogic volume driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:7(para)
+msgid "The Dell EqualLogic volume driver interacts with configured EqualLogic arrays and supports various operations, such as volume creation and deletion, volume attachment and detachment, snapshot creation and deletion, and clone creation."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:12(para)
+msgid "To configure and use a Dell EqualLogic array with Block Storage, modify your <filename>cinder.conf</filename> as follows."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:15(para)
+msgid "Set the <option>volume_driver</option> option to the Dell EqualLogic volume driver:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:18(para)
+msgid "Set the <option>san_ip</option> option to the IP address to reach the EqualLogic Group through SSH:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:21(para)
+msgid "Set the <option>san_login</option> option to the user name to login to the Group manager:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:24(para)
+msgid "Set the <option>san_password</option> option to the password to login the Group manager with:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:27(para)
+msgid "Optionally set the <option>san_thin_provision</option> option to false to disable creation of thin-provisioned volumes:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:31(para)
+msgid "The following table describes additional options that the driver supports:"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:286(None)
+msgid "@@image: '../../../common/figures/coraid/Repository_Creation_Plan_screen.png'; md5=83038804978648c2db4001a46c11f8ba"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:6(title)
+msgid "Coraid AoE driver configuration"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:7(para)
+msgid "Coraid storage appliances can provide block-level storage to OpenStack instances. Coraid storage appliances use the low-latency ATA-over-Ethernet (ATA) protocol to provide high-bandwidth data transfer between hosts and data on the network."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:11(para)
+msgid "Once configured for OpenStack, you can:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:14(para)
+msgid "Create, delete, attach, and detach block storage volumes."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:18(para)
+msgid "Create, list, and delete volume snapshots."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:21(para)
+msgid "Create a volume from a snapshot, copy an image to a volume, copy a volume to an image, clone a volume, and get volume statistics."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:26(para)
+msgid "This document describes how to configure the OpenStack Block Storage service for use with Coraid storage appliances."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:29(title)
+msgid "Terminology"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:30(para)
+msgid "These terms are used in this section:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:34(th)
+msgid "Term"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:35(th)
+msgid "Definition"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:40(td)
+msgid "AoE"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:41(td)
+msgid "ATA-over-Ethernet protocol"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:44(td)
+msgid "EtherCloud Storage Manager (ESM)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:45(td)
+msgid "ESM provides live monitoring and management of EtherDrive appliances that use the AoE protocol, such as the SRX and VSX."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:50(td)
+msgid "Fully-Qualified Repository Name (FQRN)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:53(replaceable)
+msgid "performance_class"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:53(replaceable)
+msgid "availability_class"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:53(replaceable)
+msgid "profile_name"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:53(replaceable)
+msgid "repository_name"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:51(td)
+msgid "The FQRN is the full identifier of a storage profile. FQRN syntax is: <placeholder-1/><placeholder-2/><placeholder-3/><placeholder-4/><placeholder-5/><placeholder-6/><placeholder-7/>"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:56(td)
+msgid "SAN"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:57(td)
+msgid "Storage Area Network"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:60(td)
+msgid "SRX"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:61(td)
+msgid "Coraid EtherDrive SRX block storage appliance"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:64(td)
+msgid "VSX"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:65(td)
+msgid "Coraid EtherDrive VSX storage virtualization appliance"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:73(para)
+msgid "To support the OpenStack Block Storage service, your SAN must include an SRX for physical storage, a VSX running at least CorOS v2.0.6 for snapshot support, and an ESM running at least v2.1.1 for storage repository orchestration. Ensure that all storage appliances are installed and connected to your network before you configure OpenStack volumes."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:79(para)
+msgid "In order for the node to communicate with the SAN, you must install the Coraid AoE Linux driver on each Compute node on the network that runs an OpenStack instance."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:84(title)
+msgid "Overview"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:85(para)
+msgid "To configure the OpenStack Block Storage for use with Coraid storage appliances, perform the following procedures:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:89(para)
+msgid "<link linkend=\"coraid_installing_aoe_driver\">Download and install the Coraid Linux AoE driver</link>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:93(para)
+msgid "<link linkend=\"coraid_creating_storage_profile\">Create a storage profile by using the Coraid ESM GUI</link>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:97(para)
+msgid "<link linkend=\"coraid_creating_storage_repository\">Create a storage repository by using the ESM GUI and record the FQRN</link>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:102(para)
+msgid "<link linkend=\"coraid_configuring_cinder.conf\">Configure the <filename>cinder.conf</filename> file</link>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:106(para)
+msgid "<link linkend=\"coraid_creating_associating_volume_type\">Create and associate a block storage volume type</link>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:113(title)
+msgid "Install the Coraid AoE driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:114(para)
+msgid "Install the Coraid AoE driver on every compute node that will require access to block storage."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:116(para)
+msgid "The latest AoE drivers will always be located at <link href=\"http://support.coraid.com/support/linux/\">http://support.coraid.com/support/linux/</link>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:119(para)
+msgid "To download and install the AoE driver, follow the instructions below, replacing “aoeXXX” with the AoE driver file name:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:124(para)
+msgid "Download the latest Coraid AoE driver."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:130(para)
+msgid "Unpack the AoE driver."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:133(para)
+msgid "Install the AoE driver."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:139(para)
+msgid "Initialize the AoE driver."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:145(para)
+msgid "Optionally, specify the Ethernet interfaces that the node can use to communicate with the SAN."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:147(para)
+msgid "The AoE driver may use every Ethernet interface available to the node unless limited with the <literal>aoe_iflist</literal> parameter. For more information about the <literal>aoe_iflist</literal> parameter, see the <filename>aoe readme</filename> file included with the AoE driver."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:154(replaceable)
+msgid "eth1 eth2 ..."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:160(title)
+msgid "Create a storage profile"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:161(para)
+msgid "To create a storage profile using the ESM GUI:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:164(para)
+msgid "Log in to the ESM."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:167(para)
+msgid "Click <guibutton>Storage Profiles</guibutton> in the <guilabel>SAN Domain</guilabel> pane."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:171(para)
+msgid "Choose <guimenuitem>Menu &gt; Create Storage Profile</guimenuitem>. If the option is unavailable, you might not have appropriate permissions. Make sure you are logged in to the ESM as the SAN administrator."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:177(para)
+msgid "Use the storage class selector to select a storage class."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:179(para)
+msgid "Each storage class includes performance and availability criteria (see the Storage Classes topic in the ESM Online Help for information on the different options)."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:184(para)
+msgid "Select a RAID type (if more than one is available) for the selected profile type."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:188(para)
+msgid "Type a <guilabel>Storage Profile</guilabel> name."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:189(para)
+msgid "The name is restricted to alphanumeric characters, underscore (_), and hyphen (-), and cannot exceed 32 characters."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:194(para)
+msgid "Select the drive size from the drop-down menu."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:197(para)
+msgid "Select the number of drives to be initialized for each RAID (LUN) from the drop-down menu (if the selected RAID type requires multiple drives)."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:202(para)
+msgid "Type the number of RAID sets (LUNs) you want to create in the repository by using this profile."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:206(para)
+msgid "Click <guibutton>Next</guibutton>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:211(title)
+msgid "Create a storage repository and get the FQRN"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:212(para)
+msgid "Create a storage repository and get its fully qualified repository name (FQRN):"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:216(para)
+msgid "Access the <guilabel>Create Storage Repository</guilabel> dialog box."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:220(para)
+msgid "Type a Storage Repository name."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:221(para)
+msgid "The name is restricted to alphanumeric characters, underscore (_), hyphen (-), and cannot exceed 32 characters."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:226(para)
+msgid "Click <guibutton>Limited</guibutton> or <guibutton>Unlimited</guibutton> to indicate the maximum repository size."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:229(para)
+msgid "<guibutton>Limited</guibutton> sets the amount of space that can be allocated to the repository. Specify the size in TB, GB, or MB."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:232(para)
+msgid "When the difference between the reserved space and the space already allocated to LUNs is less than is required by a LUN allocation request, the reserved space is increased until the repository limit is reached."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:237(para)
+msgid "The reserved space does not include space used for parity or space used for mirrors. If parity and/or mirrors are required, the actual space allocated to the repository from the SAN is greater than that specified in reserved space."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:243(para)
+msgid "<emphasis role=\"bold\">Unlimited</emphasis>—Unlimited means that the amount of space allocated to the repository is unlimited and additional space is allocated to the repository automatically when space is required and available."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:249(para)
+msgid "Drives specified in the associated Storage Profile must be available on the SAN in order to allocate additional resources."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:255(para)
+msgid "Check the <guibutton>Resizeable LUN</guibutton> box."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:257(para)
+msgid "This is required for OpenStack volumes."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:259(para)
+msgid "If the Storage Profile associated with the repository has platinum availability, the Resizeable LUN box is automatically checked."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:265(para)
+msgid "Check the <guibutton>Show Allocation Plan API calls</guibutton> box. Click <guibutton>Next</guibutton>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:270(para)
+msgid "Record the FQRN and click <guibutton>Finish</guibutton>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:272(para)
+msgid "The FQRN is located in the first line of output following the <literal>Plan</literal> keyword in the <guilabel>Repository Creation Plan</guilabel> window. The FQRN syntax is <replaceable>performance_class</replaceable><placeholder-1/><replaceable>availability_class</replaceable><placeholder-2/><replaceable>profile_name</replaceable><placeholder-3/><replaceable>repository_name</replaceable>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:277(para)
+msgid "In this example, the FQRN is <literal>Bronze-Platinum:BP1000:OSTest</literal>, and is highlighted."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:281(title)
+msgid "Repository Creation Plan screen"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:290(para)
+msgid "Record the FQRN; it is a required parameter later in the configuration procedure."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:296(title)
+msgid "Configure options in the cinder.conf file"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:297(para)
+msgid "Edit or add the following lines to the file<filename> /etc/cinder/cinder.conf</filename>:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:300(replaceable)
+msgid "ESM_IP_address"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:302(replaceable)
+msgid "Access_Control_Group_name"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:304(replaceable) ./doc/config-reference/block-storage/drivers/coraid-driver.xml:352(replaceable) ./doc/config-reference/block-storage/drivers/coraid-driver.xml:370(replaceable)
+msgid "coraid_repository_key"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:306(para)
+msgid "Access to storage devices and storage repositories can be controlled using Access Control Groups configured in ESM. Configuring <filename>cinder.conf</filename> to log on to ESM as the SAN administrator (user name <literal>admin</literal>), will grant full access to the devices and repositories configured in ESM."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:312(para)
+msgid "Optionally, you can configure an ESM Access Control Group and user. Then, use the <filename>cinder.conf</filename> file to configure access to the ESM through that group, and user limits access from the OpenStack instance to devices and storage repositories that are defined in the group."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:317(para)
+msgid "To manage access to the SAN by using Access Control Groups, you must enable the Use Access Control setting in the <emphasis role=\"bold\">ESM System Setup</emphasis> &gt;<emphasis role=\"bold\"> Security</emphasis> screen."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:321(para)
+msgid "For more information, see the ESM Online Help."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:324(title)
+msgid "Create and associate a volume type"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:325(para)
+msgid "Create and associate a volume with the ESM storage repository."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:329(para)
+msgid "Restart Cinder."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:335(para)
+msgid "Create a volume."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:336(replaceable)
+msgid "volume_type_name"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:337(para)
+msgid "where <replaceable>volume_type_name</replaceable> is the name you assign the volume. You will see output similar to the following:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:345(para)
+msgid "Record the value in the ID field; you use this value in the next step."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:349(para)
+msgid "Associate the volume type with the Storage Repository."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:352(replaceable) ./doc/config-reference/block-storage/drivers/coraid-driver.xml:363(replaceable)
+msgid "UUID"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:352(replaceable) ./doc/config-reference/block-storage/drivers/coraid-driver.xml:378(replaceable)
+msgid "FQRN"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:357(th)
+msgid "Variable"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:364(td)
+msgid "The ID returned from the <placeholder-1/> command. You can use the <placeholder-2/> command to recover the ID."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:375(literal)
+msgid "coraid_repository"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:371(td)
+msgid "The key name used to associate the Cinder volume type with the ESM in the <placeholder-1/> file. If no key name was defined, this is default value for <placeholder-2/>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:379(td)
+msgid "The FQRN recorded during the Create Storage Repository process."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:6(title)
+msgid "VMware VMDK driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:8(para)
+msgid "Use the VMware VMDK driver to enable management of the OpenStack Block Storage volumes on vCenter-managed data stores. Volumes are backed by VMDK files on data stores that use any VMware-compatible storage technology such as NFS, iSCSI, FiberChannel, and vSAN."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:14(para)
+msgid "The VMware ESX VMDK driver is deprecated as of the Icehouse release and might be removed in Juno or a subsequent release. The VMware vCenter VMDK driver continues to be fully supported."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:20(title)
+msgid "Functional context"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:21(para)
+msgid "The VMware VMDK driver connects to vCenter, through which it can dynamically access all the data stores visible from the ESX hosts in the managed cluster."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:24(para)
+msgid "When you create a volume, the VMDK driver creates a VMDK file on demand. The VMDK file creation completes only when the volume is subsequently attached to an instance, because the set of data stores visible to the instance determines where to place the volume."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:29(para)
+msgid "The running vSphere VM is automatically reconfigured to attach the VMDK file as an extra disk. Once attached, you can log in to the running vSphere VM to rescan and discover this extra disk."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:36(para)
+msgid "The recommended volume driver for OpenStack Block Storage is the VMware vCenter VMDK driver. When you configure the driver, you must match it with the appropriate OpenStack Compute driver from VMware and both drivers must point to the same server."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:41(para)
+msgid "In the <filename>nova.conf</filename> file, use this option to define the Compute driver:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:44(para)
+msgid "In the <filename>cinder.conf</filename> file, use this option to define the volume driver:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:47(para)
+msgid "The following table lists various options that the drivers support for the OpenStack Block Storage configuration (<filename>cinder.conf</filename>):"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:53(title) ./doc/config-reference/compute/section_hypervisor_vmware.xml:317(th)
+msgid "VMDK disk type"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:54(para)
+msgid "The VMware VMDK drivers support the creation of VMDK disk files of type <literal>thin</literal>, <literal>thick</literal>, or <literal>eagerZeroedThick</literal>. Use the <code>vmware:vmdk_type</code> extra spec key with the appropriate value to specify the VMDK disk file type. The following table captures the mapping between the extra spec entry and the VMDK disk file type:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:63(caption)
+msgid "Extra spec entry to VMDK disk file type mapping"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:67(td)
+msgid "Disk file type"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:68(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:114(td)
+msgid "Extra spec key"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:69(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:115(td)
+msgid "Extra spec value"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:74(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:76(td) ./doc/config-reference/compute/section_hypervisor_vmware.xml:328(td)
+msgid "thin"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:75(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:80(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:85(td)
+msgid "vmware:vmdk_type"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:79(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:81(td)
+msgid "thick"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:84(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:86(td)
+msgid "eagerZeroedThick"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:90(para)
+msgid "If you do not specify a <code>vmdk_type</code> extra spec entry, the default disk file type is <literal>thin</literal>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:93(para)
+msgid "The following example shows how to create a <code>thick</code> VMDK volume by using the appropriate <code>vmdk_type</code>:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:101(title) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:113(td)
+msgid "Clone type"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:102(para)
+msgid "With the VMware VMDK drivers, you can create a volume from another source volume or a snapshot point. The VMware vCenter VMDK driver supports the <literal>full</literal> and <literal>linked/fast</literal> clone types. Use the <code>vmware:clone_type</code> extra spec key to specify the clone type. The following table captures the mapping for clone types:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:110(caption)
+msgid "Extra spec entry to clone type mapping"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:120(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:122(td)
+msgid "full"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:121(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:126(td)
+msgid "vmware:clone_type"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:125(td)
+msgid "linked/fast"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:127(td)
+msgid "linked"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:131(para)
+msgid "If you do not specify the clone type, the default is <literal>full</literal>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:133(para)
+msgid "The following example shows linked cloning from another source volume:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:139(para)
+msgid "The VMware ESX VMDK driver ignores the extra spec entry and always creates a <literal>full</literal> clone."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:145(title)
+msgid "Use vCenter storage policies to specify back-end data stores"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:148(para)
+msgid "This section describes how to configure back-end data stores using storage policies. In vCenter, you can create one or more storage policies and expose them as a Block Storage volume-type to a vmdk volume. The storage policies are exposed to the vmdk driver through the extra spec property with the <literal>vmware:storage_profile</literal> key."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:155(para)
+msgid "For example, assume a storage policy in vCenter named <literal>gold_policy.</literal> and a Block Storage volume type named <literal>vol1</literal> with the extra spec key <literal>vmware:storage_profile</literal> set to the value <literal>gold_policy</literal>. Any Block Storage volume creation that uses the <literal>vol1</literal> volume type places the volume only in data stores that match the <literal>gold_policy</literal> storage policy."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:164(para)
+msgid "The Block Storage back-end configuration for vSphere data stores is automatically determined based on the vCenter configuration. If you configure a connection to connect to vCenter version 5.5 or later in the <filename>cinder.conf</filename> file, the use of storage policies to configure back-end data stores is automatically supported."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:172(para)
+msgid "You must configure any data stores that you configure for the Block Storage service for the Compute service."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:177(title)
+msgid "To configure back-end data stores by using storage policies"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:180(para)
+msgid "In vCenter, tag the data stores to be used for the back end."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:182(para)
+msgid "OpenStack also supports policies that are created by using vendor-specific capabilities; for example vSAN-specific storage policies."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:186(para)
+msgid "The tag value serves as the policy. For details, see <xref linkend=\"vmware-spbm\"/>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:192(para)
+msgid "Set the extra spec key <literal>vmware:storage_profile</literal> in the desired Block Storage volume types to the policy name that you created in the previous step."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:199(para)
+msgid "Optionally, for the <parameter>vmware_host_version</parameter> parameter, enter the version number of your vSphere platform. For example, <placeholder-1/>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:204(para)
+msgid "This setting overrides the default location for the corresponding WSDL file. Among other scenarios, you can use this setting to prevent WSDL error messages during the development phase or to work with a newer version of vCenter."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:211(para) ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:117(para) ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:180(para)
+msgid "Complete the other vCenter configuration parameters as appropriate."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:216(para)
+msgid "The following considerations apply to configuring SPBM for the Block Storage service:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:220(para)
+msgid "Any volume that is created without an associated policy (that is to say, without an associated volume type that specifies <literal>vmware:storage_profile</literal> extra spec), there is no policy-based placement for that volume."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:232(para)
+msgid "The VMware vCenter and ESX VMDK drivers support these operations:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:239(para)
+msgid "Create volume from another source volume. (Supported only if source volume is not attached to an instance.)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:247(para)
+msgid "Create volume from glance image"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:250(para)
+msgid "Attach volume (When a volume is attached to an instance, a reconfigure operation is performed on the instance to add the volume's VMDK to it. The user must manually rescan and mount the device from within the guest operating system.)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:260(para)
+msgid "Create snapshot (Allowed only if volume is not attached to an instance.)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:264(para)
+msgid "Delete snapshot (Allowed only if volume is not attached to an instance.)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:268(para)
+msgid "Upload as image to glance (Allowed only if volume is not attached to an instance.)"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:273(para)
+msgid "Although the VMware ESX VMDK driver supports these operations, it has not been extensively tested."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:279(title)
+msgid "Storage policy-based configuration in vCenter"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:280(para)
+msgid "You can configure Storage Policy-Based Management (SPBM) profiles for vCenter data stores supporting the Compute, Image Service, and Block Storage components of an OpenStack implementation."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:284(para)
+msgid "In a vSphere OpenStack deployment, SPBM enables you to delegate several data stores for storage, which reduces the risk of running out of storage space. The policy logic selects the data store based on accessibility and available storage space."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:294(para)
+msgid "Determine the data stores to be used by the SPBM policy."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:298(para)
+msgid "Determine the tag that identifies the data stores in the OpenStack component configuration."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:303(para)
+msgid "Create separate policies or sets of data stores for separate OpenStack components."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:309(title)
+msgid "Create storage policies in vCenter"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:311(title)
+msgid "To create storage policies in vCenter"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:313(para)
+msgid "In vCenter, create the tag that identifies the data stores:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:317(para)
+msgid "From the Home screen, click <guimenuitem>Tags</guimenuitem>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:321(para)
+msgid "Specify a name for the tag."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:324(para)
+msgid "Specify a tag category. For example, <filename>spbm-cinder</filename>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:330(para) ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:132(para)
+msgid "Apply the tag to the data stores to be used by the SPBM policy."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:333(para) ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:142(para)
+msgid "For details about creating tags in vSphere, see the <link href=\"http://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.vsphere.vcenterhost.doc/GUID-379F40D3-8CD6-449E-89CB-79C4E2683221.html\">vSphere documentation</link>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:340(para)
+msgid "In vCenter, create a tag-based storage policy that uses one or more tags to identify a set of data stores."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:344(para)
+msgid "You use this tag name and category when you configure the <filename>*.conf</filename> file for the OpenStack component. For details about creating tags in vSphere, see the <link href=\"http://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.vsphere.storage.doc/GUID-89091D59-D844-46B2-94C2-35A3961D23E7.html\">vSphere documentation</link>."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:355(title)
+msgid "Data store selection"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:356(para)
+msgid "If storage policy is enabled, the driver initially selects all the data stores that match the associated storage policy."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:359(para)
+msgid "If two or more data stores match the storage policy, the driver chooses a data store that is connected to the maximum number of hosts."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:362(para)
+msgid "In case of ties, the driver chooses the data store with lowest space utilization, where space utilization is defined by the <literal>(1-freespace/totalspace)</literal> metric."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:367(para)
+msgid "These actions reduce the number of volume migrations while attaching the volume to instances."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:369(para)
+msgid "The volume must be migrated if the ESX host for the instance cannot access the data store that contains the volume."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/windows-volume-driver.xml:6(title)
+msgid "Windows"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/windows-volume-driver.xml:7(para)
+msgid "There is a volume back-end for Windows. Set the following in your <filename>cinder.conf</filename>, and use the options below to configure it."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/zadara-volume-driver.xml:6(title)
+msgid "Zadara"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/zadara-volume-driver.xml:7(para)
+msgid "There is a volume back-end for Zadara. Set the following in your <filename>cinder.conf</filename>, and use the following options to configure it."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/samples/emc-vnx.xml:3(StorageType) ./doc/config-reference/block-storage/drivers/samples/emc-vnx.xml:5(EcomServerPort) ./doc/config-reference/block-storage/drivers/samples/emc-vmax.xml:3(StorageType) ./doc/config-reference/block-storage/drivers/samples/emc-vmax.xml:4(MaskingView) ./doc/config-reference/block-storage/drivers/samples/emc-vmax.xml:6(EcomServerPort)
+msgid "xxxx"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/samples/emc-vnx.xml:4(EcomServerIp) ./doc/config-reference/block-storage/drivers/samples/emc-vmax.xml:5(EcomServerIp)
+msgid "x.x.x.x"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/samples/emc-vnx.xml:6(EcomUserName) ./doc/config-reference/block-storage/drivers/samples/emc-vnx.xml:7(EcomPassword) ./doc/config-reference/block-storage/drivers/samples/emc-vmax.xml:7(EcomUserName) ./doc/config-reference/block-storage/drivers/samples/emc-vmax.xml:8(EcomPassword)
+msgid "xxxxxxxx"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/drivers/samples/emc-vnx.xml:8(Timeout) ./doc/config-reference/block-storage/drivers/samples/emc-vmax.xml:9(Timeout)
+msgid "xx"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/backup/tsm-backup-driver.xml:6(title)
+msgid "IBM Tivoli Storage Manager backup driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/backup/tsm-backup-driver.xml:7(para)
+msgid "The IBM Tivoli Storage Manager (TSM) backup driver enables performing volume backups to a TSM server."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/backup/tsm-backup-driver.xml:10(para)
+msgid "The TSM client should be installed and configured on the machine running the <systemitem class=\"service\">cinder-backup </systemitem> service. See the <citetitle>IBM Tivoli Storage Manager Backup-Archive Client Installation and User's Guide</citetitle> for details on installing the TSM client."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/backup/tsm-backup-driver.xml:17(para)
+msgid "To enable the IBM TSM backup driver, include the following option in <filename>cinder.conf</filename>:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/backup/tsm-backup-driver.xml:20(para)
+msgid "The following configuration options are available for the TSM backup driver."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/backup/tsm-backup-driver.xml:23(para)
+msgid "This example shows the default options for the TSM backup driver."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/backup/swift-backup-driver.xml:5(title)
+msgid "Swift backup driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/backup/swift-backup-driver.xml:6(para)
+msgid "The backup driver for Swift back-end performs a volume backup to a Swift object storage system."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/backup/swift-backup-driver.xml:8(para)
+msgid "To enable the Swift backup driver, include the following option in the <filename>cinder.conf</filename> file:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/backup/swift-backup-driver.xml:12(para)
+msgid "The following configuration options are available for the Swift back-end backup driver."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/backup/swift-backup-driver.xml:16(para)
+msgid "This example shows the default options for the Swift back-end backup driver."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:5(title)
+msgid "Ceph backup driver"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:6(para)
+msgid "The Ceph backup driver backs up volumes of any type to a Ceph back-end store. The driver can also detect whether the volume to be backed up is a Ceph RBD volume, and if so, it tries to perform incremental and differential backups."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:11(para)
+msgid "For source Ceph RBD volumes, you can perform backups within the same Ceph pool (not recommended) and backups between different Ceph pools and between different Ceph clusters."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:15(para)
+msgid "At the time of writing, differential backup support in Ceph/librbd was quite new. This driver attempts a differential backup in the first instance. If the differential backup fails, the driver falls back to full backup/copy."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:20(para)
+msgid "If incremental backups are used, multiple backups of the same volume are stored as snapshots so that minimal space is consumed in the backup store. It takes far less time to restore a volume than to take a full copy."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:26(para)
+msgid "Block Storage enables you to:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:29(para)
+msgid "Restore to a new volume, which is the default and recommended action."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:34(para)
+msgid "Restore to the original volume from which the backup was taken. The restore action takes a full copy because this is the safest action."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:42(para)
+msgid "To enable the Ceph backup driver, include the following option in the <filename>cinder.conf</filename> file:"
+msgstr ""
+
+#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:46(para)
+msgid "The following configuration options are available for the Ceph backup driver."
+msgstr ""
+
+#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:50(para)
+msgid "This example shows the default options for the Ceph backup driver."
+msgstr ""
+
+#: ./doc/config-reference/database-service/section-databaseservice-db.xml:7(title)
+msgid "Configure the database"
+msgstr ""
+
+#: ./doc/config-reference/database-service/section-databaseservice-db.xml:9(para)
+msgid "Use the options to configure the used databases:"
+msgstr ""
+
+#: ./doc/config-reference/database-service/section-databaseservice-rpc.xml:7(title) ./doc/config-reference/orchestration/section_orchestration-rpc.xml:7(title) ./doc/config-reference/image-service/section_image-service-rpc.xml:6(title)
+msgid "Configure the RPC messaging system"
+msgstr ""
+
+#: ./doc/config-reference/database-service/section-databaseservice-rpc.xml:8(para)
+msgid "OpenStack projects use an open standard for messaging middleware known as AMQP. This messaging middleware enables the OpenStack services that run on multiple servers to talk to each other. OpenStack Trove RPC supports three implementations of AMQP: <application>RabbitMQ</application>, <application>Qpid</application>, and <application>ZeroMQ</application>."
+msgstr ""
+
+#: ./doc/config-reference/database-service/section-databaseservice-rpc.xml:17(title) ./doc/config-reference/orchestration/section_orchestration-rpc.xml:17(title)
+msgid "Configure RabbitMQ"
+msgstr ""
+
+#: ./doc/config-reference/database-service/section-databaseservice-rpc.xml:18(para)
+msgid "Use these options to configure the <application>RabbitMQ</application> messaging system:"
+msgstr ""
+
+#: ./doc/config-reference/database-service/section-databaseservice-rpc.xml:24(title) ./doc/config-reference/orchestration/section_orchestration-rpc.xml:42(title)
+msgid "Configure Qpid"
+msgstr ""
+
+#: ./doc/config-reference/database-service/section-databaseservice-rpc.xml:25(para)
+msgid "Use these options to configure the <application>Qpid</application> messaging system:"
+msgstr ""
+
+#: ./doc/config-reference/database-service/section-databaseservice-rpc.xml:31(title)
+msgid "Configure ZeroMq"
+msgstr ""
+
+#: ./doc/config-reference/database-service/section-databaseservice-rpc.xml:32(para)
+msgid "Use these options to configure the <application>ZeroMq</application> messaging system:"
+msgstr ""
+
+#: ./doc/config-reference/database-service/section-databaseservice-rpc.xml:38(title) ./doc/config-reference/orchestration/section_orchestration-rpc.xml:97(title)
+msgid "Configure messaging"
+msgstr ""
+
+#: ./doc/config-reference/database-service/section-databaseservice-rpc.xml:40(para) ./doc/config-reference/orchestration/section_orchestration-rpc.xml:99(para)
+msgid "Use these common options to configure the <application>RabbitMQ</application>, <application>Qpid</application>, and <application>ZeroMq</application> messaging drivers:"
+msgstr ""
+
+#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:8(para)
+msgid "OpenStack projects use an open standard for messaging middleware known as AMQP. This messaging middleware enables the OpenStack services that run on multiple servers to talk to each other. OpenStack Oslo RPC supports three implementations of AMQP: <application>RabbitMQ</application>, <application>Qpid</application>, and <application>ZeroMQ</application>."
+msgstr ""
+
+#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:19(para)
+msgid "OpenStack Oslo RPC uses <application>RabbitMQ</application> by default. Use these options to configure the <application>RabbitMQ</application> message system. The <option>rpc_backend</option> option is optional as long as <application>RabbitMQ</application> is the default messaging system. However, if it is included in the configuration, you must set it to <literal>heat.openstack.common.rpc.impl_kombu</literal>."
+msgstr ""
+
+#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:31(para)
+msgid "Use these options to configure the <application>RabbitMQ</application> messaging system. You can configure messaging communication for different installation scenarios, tune retries for RabbitMQ, and define the size of the RPC thread pool. To monitor notifications through RabbitMQ, you must set the <option>notification_driver</option> option to <literal>heat.notifier.rabbit_notifier</literal> in the <filename>heat.conf</filename> file:"
+msgstr ""
+
+#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:43(para)
+msgid "Use these options to configure the <application>Qpid</application> messaging system for OpenStack Oslo RPC. <application>Qpid</application> is not the default messaging system, so you must enable it by setting the <option>rpc_backend</option> option in the <filename>heat.conf</filename> file:"
+msgstr ""
+
+#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:50(para)
+msgid "This critical option points the compute nodes to the <application>Qpid</application> broker (server). Set the <option>qpid_hostname</option> option to the host name where the broker runs in the <filename>heat.conf</filename> file."
+msgstr ""
+
+#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:56(para)
+msgid "The <option>qpid_hostname</option> option accepts a host name or IP address value."
+msgstr ""
+
+#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:61(para)
+msgid "If the <application>Qpid</application> broker listens on a port other than the AMQP default of <literal>5672</literal>, you must set the <option>qpid_port</option> option to that value:"
+msgstr ""
+
+#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:68(para)
+msgid "If you configure the <application>Qpid</application> broker to require authentication, you must add a user name and password to the configuration:"
+msgstr ""
+
+#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:74(para)
+msgid "By default, TCP is used as the transport. To enable SSL, set the <option>qpid_protocol</option> option:"
+msgstr ""
+
+#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:79(para)
+msgid "Use these additional options to configure the Qpid messaging driver for OpenStack Oslo RPC. These options are used infrequently."
+msgstr ""
+
+#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:87(title)
+msgid "Configure ZeroMQ"
+msgstr ""
+
+#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:88(para)
+msgid "Use these options to configure the <application>ZeroMQ</application> messaging system for OpenStack Oslo RPC. <application>ZeroMQ</application> is not the default messaging system, so you must enable it by setting the <option>rpc_backend</option> option in the <filename>heat.conf</filename> file:"
+msgstr ""
+
+#: ./doc/config-reference/orchestration/section_orchestration-api.xml:7(title)
+msgid "Configure APIs"
+msgstr ""
+
+#: ./doc/config-reference/orchestration/section_orchestration-api.xml:8(para)
+msgid "The following options allow configuration of the APIs that Orchestration supports. Currently this includes compatibility APIs for CloudFormation and CloudWatch and a native API."
+msgstr ""
+
+#: ./doc/config-reference/orchestration/section_orchestration-clients.xml:7(title)
+msgid "Configure Clients"
+msgstr ""
+
+#: ./doc/config-reference/orchestration/section_orchestration-clients.xml:8(para)
+msgid "The following options allow configuration of the clients that Orchestration uses to talk to other services."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:4(title)
+msgid "Image Service sample configuration files"
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:5(para)
+msgid "All the files in this section can be found in the <filename class=\"directory\">/etc/glance/</filename> directory."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:8(title)
+msgid "glance-api.conf"
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:9(para)
+msgid "The configuration file for the Image Service API is found in the <filename>glance-api.conf</filename> file."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:15(title)
+msgid "glance-registry.conf"
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:16(para)
+msgid "Configuration for the Image Service's registry, which stores the metadata about images, is found in the <filename>glance-registry.conf</filename> file."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:23(title)
+msgid "glance-api-paste.ini"
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:24(para)
+msgid "Configuration for the Image Service's API middleware pipeline is found in the <filename>glance-api-paste.ini</filename> file."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:30(title)
+msgid "glance-registry-paste.ini"
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:31(para)
+msgid "The Image Service's middleware pipeline for its registry is found in the <filename>glance-registry-paste.ini</filename> file."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:36(title)
+msgid "glance-scrubber.conf"
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:37(para)
+msgid "<placeholder-1/> is a utility for the Image Service that cleans up images that have been deleted; its configuration is stored in the <filename>glance-scrubber.conf</filename> file."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:40(para)
+msgid "Multiple instances of <systemitem>glance-scrubber</systemitem> can be run in a single deployment, but only one of them can be designated as the <systemitem>cleanup_scrubber</systemitem> in the <filename>glance-scrubber.conf</filename> file. The <systemitem>cleanup_scrubber</systemitem> coordinates other <systemitem>glance-scrubber</systemitem> instances by maintaining the master queue of images that need to be removed."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:51(para)
+msgid "The <filename>/etc/glance/policy.json</filename> file defines additional access controls that apply to the Image Service."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-rpc.xml:7(para)
+msgid "OpenStack projects use an open standard for messaging middleware known as AMQP. This messaging middleware enables the OpenStack services that run on multiple servers to talk to each other. The OpenStack common library project, oslo, supports three implementations of AMQP: <application>RabbitMQ</application>, <application>Qpid</application>, and <application>ZeroMQ</application>."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-rpc.xml:14(para)
+msgid "The following tables contain settings to configure the messaging middleware for the Image Service:"
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:6(title)
+msgid "Configure vCenter data stores for the Image Service back end"
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:9(para)
+msgid "To use vCenter data stores for the Image Service back end, you must update the <filename>glance-api.conf</filename> file, as follows:"
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:14(para)
+msgid "Add data store parameters to the <literal>VMware Datastore Store Options</literal> section."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:18(para)
+msgid "Specify vSphere as the back end."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:22(para)
+msgid "You must configure any configured Image Service data stores for the Compute service."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:29(para)
+msgid "If you intend to use multiple data stores for the back end, use the SPBM feature."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:25(para)
+msgid "You can specify vCenter data stores directly by using the data store name or Storage Policy Based Management (SPBM), which requires vCenter Server 5.5 or later. For details, see <xref linkend=\"glance-backend-DS\"/>. <placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:32(para)
+msgid "In the <literal>DEFAULT</literal> section, set the <parameter>default_store</parameter> parameter to <placeholder-1/>, as shown in this code sample:"
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:42(para)
+msgid "The following table describes the parameters in the <literal>VMware Datastore Store Options</literal> section:"
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:46(para)
+msgid "The following block of text shows a sample configuration:"
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:55(replaceable)
+msgid "ADMINISTRATOR"
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:63(replaceable)
+msgid "DATACENTER"
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:66(replaceable)
+msgid "datastore1"
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:81(replaceable)
+msgid "5"
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:85(replaceable)
+msgid "/openstack_glance"
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:90(title)
+msgid "Configure vCenter data stores for the back end"
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:91(para)
+msgid "You can specify a vCenter data store for the back end by setting the <parameter>vmware_datastore_name</parameter> parameter value to the vCenter name of the data store. This configuration limits the back end to a single data store."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:96(para)
+msgid "Alternatively, you can specify a SPBM policy, which can comprise multiple vCenter data stores. Both approaches are described."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:100(para)
+msgid "SPBM requires vCenter Server 5.5 or later."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:103(title)
+msgid "To configure a single data store"
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:105(para)
+msgid "If present, comment or delete the <parameter>vmware_pbm_wsdl_location</parameter> and <parameter>vmware_pbm_policy</parameter> parameters."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:111(para)
+msgid "Uncomment and define the <parameter>vmware_datastore_name</parameter> parameter with the name of the vCenter data store."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:122(title)
+msgid "To configure multiple data stores using SPBM"
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:125(para)
+msgid "In vCenter, use tagging to identify the data stores and define a storage policy:"
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:129(para)
+msgid "Create the tag."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:136(para)
+msgid "Create a tag-based storage policy that uses one or more tags to identify a set of data stores."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:146(para)
+msgid "For details about storage policies in vSphere, see the <link href=\"http://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.vsphere.storage.doc/GUID-A8BA9141-31F1-4555-A554-4B5B04D75E54.html\">vSphere documentation</link>."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:153(para)
+msgid "Return to the <filename>glance-api.conf</filename> file."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:158(para)
+msgid "Comment or delete the <parameter>vmware_datastore_name</parameter> parameter."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:163(para)
+msgid "Uncomment and define the <parameter>vmware_pbm_policy</parameter> parameter by entering the same value as the tag you defined and applied to the data stores in vCenter."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:170(para)
+msgid "Uncomment and define the <parameter>vmware_pbm_wsdl_location</parameter> parameter by entering the location of the PBM service WSDL file. For example, <filename>file:///opt/SDK/spbm/wsdl/pbmService.wsdl</filename>."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:176(para)
+msgid "If you do not set this parameter, the storage policy cannot be used to place images in the data store."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-api.xml:6(title)
+msgid "Configure the API"
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-api.xml:7(para)
+msgid "The Image Service has two APIs: the user-facing API, and the registry API, which is for internal requests that require access to the database."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-api.xml:10(para)
+msgid "Both of the APIs currently have two major versions, v1 and v2. It is possible to run either or both version, by setting appropriate values of <literal>enable_v1_api</literal>, <literal>enable_v2_api</literal>, <literal>enable_v1_registry</literal> and <literal>enable_v2_registry</literal>. If the v2 API is used, running <systemitem class=\"service\">glance-registry</systemitem> is optional, as v2 of <systemitem class=\"service\">glance-api</systemitem> can connect directly to the database."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-api.xml:18(para)
+msgid "Tables of all options used to configure the APIs, including enabling SSL and modifying WSGI settings are found below."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backends.xml:6(title)
+msgid "Configuring Backends"
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-backends.xml:7(para)
+msgid "The image service supports several different backends for storing virtual machine images, including Cinder, a directory on a local file system, GridFS, Ceph RBD, Amazon S3, Sheepdog, OpenStack Object Storage or VMWare ESX. The following tables detail the options available for each."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-ISO-support.xml:5(title)
+msgid "Support for ISO images"
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-ISO-support.xml:6(para)
+msgid "You can load ISO images into the Image Service. You can subsequently boot an ISO image using Compute."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-ISO-support.xml:9(title)
+msgid "To load an ISO image to an Image Service data store"
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-ISO-support.xml:12(para)
+msgid "Obtain the ISO image. For example, <filename>ubuntu-13.04-server-amd64.iso</filename>."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-ISO-support.xml:16(para)
+msgid "In the Image Service, run the following command:"
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-ISO-support.xml:21(para)
+msgid "In this command, <literal>ubuntu.iso</literal> is the name for the ISO image after it is loaded to the Image Service, and <literal>ubuntu-13.04-server-amd64.iso</literal> is the name of the source ISO image."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-ISO-support.xml:28(para)
+msgid "Optionally, confirm the upload in Compute."
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-ISO-support.xml:29(para) ./doc/config-reference/image-service/section_image-service-ISO-support.xml:36(para)
+msgid "Run this command:"
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-ISO-support.xml:34(title)
+msgid "To boot an instance from an ISO image"
+msgstr ""
+
+#: ./doc/config-reference/image-service/section_image-service-ISO-support.xml:39(para)
+msgid "In this command, <literal>ubuntu.iso</literal> is the ISO image, and <literal>instance_name</literal> is the name of the new instance."
 msgstr ""
 
 #: ./doc/config-reference/compute/section_compute-configure-backing-storage.xml:6(title)
@@ -1043,138 +6762,6 @@ msgstr ""
 msgid "Local <link href=\"http://http//en.wikipedia.org/wiki/Logical_Volume_Manager_(Linux)\">LVM volumes</link> can also be used. Set <literal>images_volume_group = nova_local</literal> where <literal>nova_local</literal> is the name of the LVM group you have created."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-hypervisors.xml:6(title)
-msgid "Hypervisors"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-hypervisors.xml:7(para)
-msgid "OpenStack Compute supports many hypervisors, which might make it difficult for you to choose one. Most installations use only one hypervisor. However you can use <xref linkend=\"computefilter\"/> and <xref linkend=\"imagepropertiesfilter\"/> to schedule to different hypervisors within the same installation. The following links help you choose a hypervisor. See <link href=\"http://wiki.openstack.org/HypervisorSupportMatrix\">http://wiki.openstack.org/HypervisorSupportMatrix</link> for a detailed list of features and support across the hypervisors."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-hypervisors.xml:18(para)
-msgid "The following hypervisors are supported:"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-hypervisors.xml:21(para)
-msgid "<link href=\"http://www.linux-kvm.org/page/Main_Page\">KVM</link> - Kernel-based Virtual Machine. The virtual disk formats that it supports is inherited from QEMU since it uses a modified QEMU program to launch the virtual machine. The supported formats include raw images, the qcow2, and VMware formats."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-hypervisors.xml:30(para)
-msgid "<link href=\"http://lxc.sourceforge.net/\">LXC</link> - Linux Containers (through libvirt), use to run Linux-based virtual machines."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-hypervisors.xml:35(para)
-msgid "<link href=\"http://wiki.qemu.org/Manual\">QEMU</link> - Quick EMUlator, generally only used for development purposes."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-hypervisors.xml:40(para)
-msgid "<link href=\"http://user-mode-linux.sourceforge.net/\">UML</link> - User Mode Linux, generally only used for development purposes."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-hypervisors.xml:46(para)
-msgid "<link href=\"http://www.vmware.com/products/vsphere-hypervisor/support.html\">VMware vSphere</link> 4.1 update 1 and newer, runs VMware-based Linux and Windows images through a connection with a vCenter server or directly with an ESXi host."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-hypervisors.xml:52(para)
-msgid "<link href=\"http://www.xen.org\">Xen</link> - XenServer, Xen Cloud Platform (XCP), use to run Linux or Windows virtual machines. You must install the <systemitem class=\"service\">nova-compute</systemitem> service in a para-virtualized VM."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-hypervisors.xml:60(para)
-msgid "<link href=\"http://www.microsoft.com/en-us/server-cloud/windows-server/server-virtualization-features.aspx\"> Hyper-V</link> - Server virtualization with Microsoft's Hyper-V, use to run Windows, Linux, and FreeBSD virtual machines. Runs <systemitem class=\"service\">nova-compute</systemitem> natively on the Windows virtualization platform."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-hypervisors.xml:69(para)
-msgid "<link href=\"https://wiki.openstack.org/wiki/Baremetal\"> Bare Metal</link> - Not a hypervisor in the traditional sense, this driver provisions physical hardware through pluggable sub-drivers (for example, PXE for image deployment, and IPMI for power management)."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-hypervisors.xml:78(title)
-msgid "Hypervisor configuration basics"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-hypervisors.xml:79(para)
-msgid "The node where the <systemitem class=\"service\">nova-compute</systemitem> service is installed and running is the machine that runs all the virtual machines, referred to as the compute node in this guide."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-hypervisors.xml:83(para)
-msgid "By default, the selected hypervisor is KVM. To change to another hypervisor, change the <literal>virt_type</literal> option in the <literal>[libvirt]</literal> section of <filename>nova.conf</filename> and restart the <systemitem class=\"service\">nova-compute</systemitem> service."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-hypervisors.xml:87(para)
-msgid "Here are the general <filename>nova.conf</filename> options that are used to configure the compute node's hypervisor: <xref linkend=\"config_table_nova_hypervisor\"/>."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-hypervisors.xml:90(para)
-msgid "Specific options for particular hypervisors can be found in following sections."
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/config-reference/compute/section_compute-config-samples.xml:41(None)
-msgid "@@image: '../../common/figures/SCH_5004_V00_NUAC-Network_mode_KVM_Flat_OpenStack.png'; md5=1e883ef27e5912b5c516d153b8844a28"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/config-reference/compute/section_compute-config-samples.xml:80(None)
-msgid "@@image: '../../common/figures/SCH_5005_V00_NUAC-Network_mode_XEN_Flat_OpenStack.png'; md5=3b151435a0fda3702d4fac5a964fac83"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-config-samples.xml:6(title)
-msgid "Example <filename>nova.conf</filename> configuration files"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-config-samples.xml:8(para)
-msgid "The following sections describe the configuration options in the <filename>nova.conf</filename> file. You must copy the <filename>nova.conf</filename> file to each compute node. The sample <filename>nova.conf</filename> files show examples of specific configurations."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-config-samples.xml:14(title)
-msgid "Small, private cloud"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-config-samples.xml:15(para)
-msgid "This example <filename>nova.conf</filename> file configures a small private cloud with cloud controller services, database server, and messaging server on the same server. In this case, CONTROLLER_IP represents the IP address of a central server, BRIDGE_INTERFACE represents the bridge such as br100, the NETWORK_INTERFACE represents an interface to your VLAN setup, and passwords are represented as DB_PASSWORD_COMPUTE for your Compute (nova) database password, and RABBIT PASSWORD represents the password to your message queue installation."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-config-samples.xml:28(title) ./doc/config-reference/compute/section_compute-config-samples.xml:35(title) ./doc/config-reference/compute/section_compute-config-samples.xml:74(title)
-msgid "KVM, Flat, MySQL, and Glance, OpenStack or EC2 API"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-config-samples.xml:30(para)
-msgid "This example <filename>nova.conf</filename> file, from an internal Rackspace test system, is used for demonstrations."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-config-samples.xml:47(title)
-msgid "XenServer, Flat networking, MySQL, and Glance, OpenStack API"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-config-samples.xml:49(para)
-msgid "This example <filename>nova.conf</filename> file is from an internal Rackspace test system."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_lxc.xml:6(title)
-msgid "LXC (Linux containers)"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_lxc.xml:7(para)
-msgid "LXC (also known as Linux containers) is a virtualization technology that works at the operating system level. This is different from hardware virtualization, the approach used by other hypervisors such as KVM, Xen, and VMware. LXC (as currently implemented using libvirt in the Compute service) is not a secure virtualization technology for multi-tenant environments (specifically, containers may affect resource quotas for other containers hosted on the same machine). Additional containment technologies, such as AppArmor, may be used to provide better isolation between containers, although this is not the case by default. For all these reasons, the choice of this virtualization technology is not recommended in production."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_lxc.xml:15(para)
-msgid "If your compute hosts do not have hardware support for virtualization, LXC will likely provide better performance than QEMU. In addition, if your guests must access specialized hardware, such as GPUs, this might be easier to achieve with LXC than other hypervisors."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_lxc.xml:18(para)
-msgid "Some OpenStack Compute features might be missing when running with LXC as the hypervisor. See the <link href=\"http://wiki.openstack.org/HypervisorSupportMatrix\">hypervisor support matrix</link> for details."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_lxc.xml:21(para)
-msgid "To enable LXC, ensure the following options are set in <filename>/etc/nova/nova.conf</filename> on all hosts running the <systemitem class=\"service\">nova-compute</systemitem> service.<placeholder-1/>"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_lxc.xml:28(para)
-msgid "On Ubuntu 12.04, enable LXC support in OpenStack by installing the <literal>nova-compute-lxc</literal> package."
-msgstr ""
-
 #: ./doc/config-reference/compute/section_compute-configure-db.xml:6(title)
 msgid "Database configuration"
 msgstr ""
@@ -1195,235 +6782,6 @@ msgstr ""
 msgid "In either case, use the configuration option settings documented in <xref linkend=\"config_table_nova_db\"/> to configure the connection string for the nova database."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-options-reference.xml:6(title)
-msgid "Compute sample configuration files"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-options-reference.xml:8(title)
-msgid "nova.conf - configuration options"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-options-reference.xml:9(para)
-msgid "For a complete list of all available configuration options for each OpenStack Compute service, run bin/nova-&lt;servicename&gt; --help."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-sample-configuration-files.xml:4(title) ./doc/config-reference/dashboard/section_dashboard-sample-configuration-files.xml:6(title)
-msgid "Additional sample configuration files"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-sample-configuration-files.xml:5(para)
-msgid "Files in this section can be found in <systemitem>/etc/nova</systemitem>."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-sample-configuration-files.xml:7(title) ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:15(title) ./doc/config-reference/block-storage/section_block-storage-sample-configuration-files.xml:15(title)
-msgid "api-paste.ini"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-sample-configuration-files.xml:8(para)
-msgid "The Compute service stores its API configuration settings in the <filename>api-paste.ini</filename> file."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-sample-configuration-files.xml:15(title) ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:22(title) ./doc/config-reference/block-storage/section_block-storage-sample-configuration-files.xml:22(title) ./doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml:35(title) ./doc/config-reference/identity/section_keystone-sample-conf-files.xml:42(title) ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:50(title)
-msgid "policy.json"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-sample-configuration-files.xml:16(para)
-msgid "The <filename>policy.json</filename> file defines additional access controls that apply to the Compute service."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-sample-configuration-files.xml:22(title) ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:30(title) ./doc/config-reference/block-storage/section_block-storage-sample-configuration-files.xml:27(title)
-msgid "rootwrap.conf"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-sample-configuration-files.xml:23(para)
-msgid "The <filename>rootwrap.conf</filename> file defines configuration values used by the rootwrap script when the Compute service needs to escalate its privileges to those of the root user."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-configure-console.xml:7(title)
-msgid "Configure remote console access"
-msgstr ""
-
-#. <?dbhtml stop-chunking?>
-#: ./doc/config-reference/compute/section_compute-configure-console.xml:9(para)
-msgid "OpenStack has two main methods for providing a remote console or remote desktop access to guest Virtual Machines. They are VNC, and SPICE HTML5 and can be used either through the OpenStack dashboard and the command line. Best practice is to select one or the other to run."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:6(para)
-msgid "KVM is configured as the default hypervisor for Compute."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:8(para)
-msgid "This document contains several sections about hypervisor selection. If you are reading this document linearly, you do not want to load the KVM module before you install <systemitem class=\"service\">nova-compute</systemitem>. The <systemitem class=\"service\">nova-compute</systemitem> service depends on qemu-kvm, which installs <filename>/lib/udev/rules.d/45-qemu-kvm.rules</filename>, which sets the correct permissions on the /dev/kvm device node."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:15(para)
-msgid "To enable KVM explicitly, add the following configuration options to the <filename>/etc/nova/nova.conf</filename> file:"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:21(para)
-msgid "The KVM hypervisor supports the following virtual machine image formats:"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:24(para) ./doc/config-reference/compute/section_hypervisor_qemu.xml:44(para)
-msgid "Raw"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:27(para) ./doc/config-reference/compute/section_hypervisor_qemu.xml:47(para)
-msgid "QEMU Copy-on-write (qcow2)"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:30(para)
-msgid "QED Qemu Enhanced Disk"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:33(para)
-msgid "VMWare virtual machine disk format (vmdk)"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:36(para)
-msgid "This section describes how to enable KVM on your system. For more information, see the following distribution-specific documentation:"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:40(para)
-msgid "<link href=\"http://fedoraproject.org/wiki/Getting_started_with_virtualization\">Fedora: Getting started with virtualization</link> from the Fedora project wiki."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:46(para)
-msgid "<link href=\"https://help.ubuntu.com/community/KVM/Installation\">Ubuntu: KVM/Installation</link> from the Community Ubuntu documentation."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:50(para)
-msgid "<link href=\"http://static.debian-handbook.info/browse/stable/sect.virtualization.html#idp11279352\">Debian: Virtualization with KVM</link> from the Debian handbook."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:55(para)
-msgid "<link href=\"http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Host_Configuration_and_Guest_Installation_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system.html\">Red Hat Enterprise Linux: Installing virtualization packages on an existing Red Hat Enterprise Linux system</link> from the <citetitle>Red Hat Enterprise Linux Virtualization Host Configuration and Guest Installation Guide</citetitle>."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:63(para)
-msgid "<link href=\"http://doc.opensuse.org/documentation/html/openSUSE/opensuse-kvm/cha.kvm.requires.html#sec.kvm.requires.install\">openSUSE: Installing KVM</link> from the openSUSE Virtualization with KVM manual."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:69(para)
-msgid "<link href=\"http://doc.opensuse.org/products/draft/SLES/SLES-kvm_sd_draft/cha.kvm.requires.html#sec.kvm.requires.install\">SLES: Installing KVM</link> from the SUSE Linux Enterprise Server Virtualization with KVM manual."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:79(title)
-msgid "Specify the CPU model of KVM guests"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:80(para)
-msgid "The Compute service enables you to control the guest CPU model that is exposed to KVM virtual machines. Use cases include:"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:84(para)
-msgid "To maximize performance of virtual machines by exposing new host CPU features to the guest"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:88(para)
-msgid "To ensure a consistent default CPU across all machines, removing reliance of variable QEMU defaults"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:92(para)
-msgid "In libvirt, the CPU is specified by providing a base CPU model name (which is a shorthand for a set of feature flags), a set of additional feature flags, and the topology (sockets/cores/threads). The libvirt KVM driver provides a number of standard CPU model names. These models are defined in the <filename>/usr/share/libvirt/cpu_map.xml</filename> file. Check this file to determine which models are supported by your local installation."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:98(para)
-msgid "Two Compute configuration options in the <literal>[libvirt]</literal> group of <filename>nova.conf</filename> define which type of CPU model is exposed to the hypervisor when using KVM: <literal>cpu_mode</literal> and <literal>cpu_model</literal>."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:102(para)
-msgid "The <literal>cpu_mode</literal> option can take one of the following values: <literal>none</literal>, <literal>host-passthrough</literal>, <literal>host-model</literal>, and <literal>custom</literal>."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:106(title)
-msgid "Host model (default for KVM &amp; QEMU)"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:107(para)
-msgid "If your <filename>nova.conf</filename> file contains <literal>cpu_mode=host-model</literal>, libvirt identifies the CPU model in <filename>/usr/share/libvirt/cpu_map.xml</filename> file that most closely matches the host, and requests additional CPU flags to complete the match. This configuration provides the maximum functionality and performance and maintains good reliability and compatibility if the guest is migrated to another host with slightly different host CPUs."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:116(title)
-msgid "Host pass through"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:117(para)
-msgid "If your <filename>nova.conf</filename> file contains <literal>cpu_mode=host-passthrough</literal>, libvirt tells KVM to pass through the host CPU with no modifications. The difference to host-model, instead of just matching feature flags, every last detail of the host CPU is matched. This gives absolutely best performance, and can be important to some apps which check low level CPU details, but it comes at a cost with respect to migration: the guest can only be migrated to an exactly matching host CPU."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:126(title)
-msgid "Custom"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:127(para)
-msgid "If your <filename>nova.conf</filename> file contains <literal>cpu_mode=custom</literal>, you can explicitly specify one of the supported named model using the cpu_model configuration option. For example, to configure the KVM guests to expose Nehalem CPUs, your <filename>nova.conf</filename> file should contain:"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:137(title)
-msgid "None (default for all libvirt-driven hypervisors other than KVM &amp; QEMU)"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:139(para)
-msgid "If your <filename>nova.conf</filename> file contains <literal>cpu_mode=none</literal>, libvirt does not specify a CPU model. Instead, the hypervisor chooses the default model."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:145(title)
-msgid "Guest agent support"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:146(para)
-msgid "Use guest agents to enable optional access between compute nodes and guests through a socket, using the QMP protocol."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:148(para)
-msgid "To enable this feature, you must set <literal>hw_qemu_guest_agent=yes</literal> as a metadata parameter on the image you wish to use to create guest-agent-capable instances from. You can explicitly disable the feature by setting <literal>hw_qemu_guest_agent=no</literal> in the image metadata."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:154(title)
-msgid "KVM performance tweaks"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:155(para)
-msgid "The <link href=\"http://www.linux-kvm.org/page/VhostNet\">VHostNet</link> kernel module improves network performance. To load the kernel module, run the following command as root:"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:161(title)
-msgid "Troubleshoot KVM"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:162(para)
-msgid "Trying to launch a new virtual machine instance fails with the <literal>ERROR</literal>state, and the following error appears in the <filename>/var/log/nova/nova-compute.log</filename> file:"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:166(para)
-msgid "This message indicates that the KVM kernel modules were not loaded."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:167(para)
-msgid "If you cannot start VMs after installation without rebooting, the permissions might not be correct. This can happen if you load the KVM module before you install <systemitem class=\"service\">nova-compute</systemitem>. To check whether the group is set to <systemitem>kvm</systemitem>, run:"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:172(para)
-msgid "If it is not set to <systemitem>kvm</systemitem>, run:"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-conductor.xml:7(title)
-msgid "Conductor"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-conductor.xml:8(para)
-msgid "The <systemitem class=\"service\">nova-conductor</systemitem> service enables OpenStack to function without compute nodes accessing the database. Conceptually, it implements a new layer on top of <systemitem class=\"service\">nova-compute</systemitem>. It should not be deployed on compute nodes, or else the security benefits of removing database access from <systemitem class=\"service\">nova-compute</systemitem> are negated. Just like other nova services such as <systemitem class=\"service\">nova-api</systemitem> or nova-scheduler, it can be scaled horizontally. You can run multiple instances of <systemitem class=\"service\">nova-conductor</systemitem> on different machines as needed for scaling purposes."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-conductor.xml:21(para)
-msgid "The methods exposed by <systemitem class=\"service\">nova-conductor</systemitem> are relatively simple methods used by <systemitem class=\"service\">nova-compute</systemitem> to offload its database operations. Places where <systemitem class=\"service\">nova-compute</systemitem> previously performed database access are now talking to <systemitem class=\"service\">nova-conductor</systemitem>. However, we have plans in the medium to long term to move more and more of what is currently in <systemitem class=\"service\">nova-compute</systemitem> up to the <systemitem class=\"service\">nova-conductor</systemitem> layer. The Compute service will start to look like a less intelligent slave service to <systemitem class=\"service\">nova-conductor</systemitem>. The conductor service will implement long running complex operations, ensuring forward progress and graceful error handling. This will be especially beneficial for operations that cross multiple compute nodes, such as migrations or resizes."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-conductor.xml:40(para)
-msgid "To customize the Conductor, use the configuration option settings documented in <xref linkend=\"config_table_nova_conductor\"/>."
-msgstr ""
-
 #: ./doc/config-reference/compute/section_nova-conf.xml:6(title)
 msgid "Overview of nova.conf"
 msgstr ""
@@ -1496,6 +6854,50 @@ msgstr ""
 msgid "Configuration options are grouped by section. The Compute configuration file supports the following sections: <placeholder-1/>"
 msgstr ""
 
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/config-reference/compute/section_compute-config-samples.xml:41(None)
+msgid "@@image: '../../common/figures/SCH_5004_V00_NUAC-Network_mode_KVM_Flat_OpenStack.png'; md5=1e883ef27e5912b5c516d153b8844a28"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/config-reference/compute/section_compute-config-samples.xml:80(None)
+msgid "@@image: '../../common/figures/SCH_5005_V00_NUAC-Network_mode_XEN_Flat_OpenStack.png'; md5=3b151435a0fda3702d4fac5a964fac83"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-config-samples.xml:6(title)
+msgid "Example <filename>nova.conf</filename> configuration files"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-config-samples.xml:8(para)
+msgid "The following sections describe the configuration options in the <filename>nova.conf</filename> file. You must copy the <filename>nova.conf</filename> file to each compute node. The sample <filename>nova.conf</filename> files show examples of specific configurations."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-config-samples.xml:14(title)
+msgid "Small, private cloud"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-config-samples.xml:15(para)
+msgid "This example <filename>nova.conf</filename> file configures a small private cloud with cloud controller services, database server, and messaging server on the same server. In this case, CONTROLLER_IP represents the IP address of a central server, BRIDGE_INTERFACE represents the bridge such as br100, the NETWORK_INTERFACE represents an interface to your VLAN setup, and passwords are represented as DB_PASSWORD_COMPUTE for your Compute (nova) database password, and RABBIT PASSWORD represents the password to your message queue installation."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-config-samples.xml:28(title) ./doc/config-reference/compute/section_compute-config-samples.xml:35(title) ./doc/config-reference/compute/section_compute-config-samples.xml:74(title)
+msgid "KVM, Flat, MySQL, and Glance, OpenStack or EC2 API"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-config-samples.xml:30(para)
+msgid "This example <filename>nova.conf</filename> file, from an internal Rackspace test system, is used for demonstrations."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-config-samples.xml:47(title)
+msgid "XenServer, Flat networking, MySQL, and Glance, OpenStack API"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-config-samples.xml:49(para)
+msgid "This example <filename>nova.conf</filename> file is from an internal Rackspace test system."
+msgstr ""
+
 #: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:6(title)
 msgid "Hyper-V virtualization platform"
 msgstr ""
@@ -1928,124 +7330,515 @@ msgstr ""
 msgid "Verify that you are synchronized with a network time source. Instructions for configuring NTP on your Hyper-V compute node are located <placeholder-1/>"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:6(title)
-msgid "Compute log files"
+#: ./doc/config-reference/compute/section_hypervisor_baremetal.xml:6(title)
+msgid "Baremetal driver"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:7(para)
-msgid "The corresponding log file of each Compute service is stored in the <filename>/var/log/nova/</filename> directory of the host on which each service runs."
+#: ./doc/config-reference/compute/section_hypervisor_baremetal.xml:7(para)
+msgid "The baremetal driver is a hypervisor driver for OpenStack Nova Compute. Within the OpenStack framework, it has the same role as the drivers for other hypervisors (libvirt, xen, etc), and yet it is presently unique in that the hardware is not virtualized - there is no hypervisor between the tenants and the physical hardware. It exposes hardware through the OpenStack APIs, using pluggable sub-drivers to deliver machine imaging (PXE) and power control (IPMI). With this, provisioning and management of physical hardware is accomplished by using common cloud APIs and tools, such as the Orchestration module (heat) or salt-cloud. However, due to this unique situation, using the baremetal driver requires some additional preparation of its environment, the details of which are beyond the scope of this guide."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:11(caption)
-msgid "Log files used by Compute services"
+#: ./doc/config-reference/compute/section_hypervisor_baremetal.xml:20(para)
+msgid "Some OpenStack Compute features are not implemented by the baremetal hypervisor driver. See the <link href=\"http://wiki.openstack.org/HypervisorSupportMatrix\"> hypervisor support matrix</link> for details."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:17(td) ./doc/config-reference/networking/section_networking-log-files.xml:16(td) ./doc/config-reference/block-storage/section_cinder-log-files.xml:17(td) ./doc/config-reference/dashboard/section_dashboard-log-files.xml:19(td)
-msgid "Log file"
+#: ./doc/config-reference/compute/section_hypervisor_baremetal.xml:24(para)
+msgid "For the Baremetal driver to be loaded and function properly, ensure that the following options are set in <filename>/etc/nova/nova.conf</filename> on your <systemitem class=\"service\">nova-compute</systemitem> hosts."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:20(td)
-msgid "Service name (CentOS/Fedora/openSUSE/Red Hat Enterprise Linux/SUSE Linux Enterprise)"
+#: ./doc/config-reference/compute/section_hypervisor_baremetal.xml:34(para)
+msgid "Many configuration options are specific to the Baremetal driver. Also, some additional steps are required, such as building the baremetal deploy ramdisk. See the <link href=\"https://wiki.openstack.org/wiki/Baremetal\">main wiki page</link> for details and implementation suggestions."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:24(td)
-msgid "Service name (Ubuntu/Debian)"
+#: ./doc/config-reference/compute/section_hypervisor_baremetal.xml:40(para)
+msgid "To customize the Baremetal driver, use the configuration option settings documented in <xref linkend=\"config_table_nova_baremetal\"/>."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:32(filename) ./doc/config-reference/block-storage/section_cinder-log-files.xml:32(filename)
-msgid "api.log"
+#: ./doc/config-reference/compute/section_compute-configure-console.xml:7(title)
+msgid "Configure remote console access"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:34(td)
-msgid "openstack-nova-api"
+#. <?dbhtml stop-chunking?>
+#: ./doc/config-reference/compute/section_compute-configure-console.xml:9(para)
+msgid "OpenStack has two main methods for providing a remote console or remote desktop access to guest Virtual Machines. They are VNC, and SPICE HTML5 and can be used either through the OpenStack dashboard and the command line. Best practice is to select one or the other to run."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:43(filename)
-msgid "cert.log"
+#: ./doc/config-reference/compute/section_hypervisor_lxc.xml:6(title)
+msgid "LXC (Linux containers)"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:45(para)
-msgid "The X509 certificate service (<systemitem>openstack-nova-cert</systemitem>/<systemitem>nova-cert</systemitem>) is only required by the EC2 API to the Compute service."
+#: ./doc/config-reference/compute/section_hypervisor_lxc.xml:7(para)
+msgid "LXC (also known as Linux containers) is a virtualization technology that works at the operating system level. This is different from hardware virtualization, the approach used by other hypervisors such as KVM, Xen, and VMware. LXC (as currently implemented using libvirt in the Compute service) is not a secure virtualization technology for multi-tenant environments (specifically, containers may affect resource quotas for other containers hosted on the same machine). Additional containment technologies, such as AppArmor, may be used to provide better isolation between containers, although this is not the case by default. For all these reasons, the choice of this virtualization technology is not recommended in production."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:51(systemitem)
-msgid "openstack-nova-cert"
+#: ./doc/config-reference/compute/section_hypervisor_lxc.xml:15(para)
+msgid "If your compute hosts do not have hardware support for virtualization, LXC will likely provide better performance than QEMU. In addition, if your guests must access specialized hardware, such as GPUs, this might be easier to achieve with LXC than other hypervisors."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:54(systemitem)
-msgid "nova-cert"
+#: ./doc/config-reference/compute/section_hypervisor_lxc.xml:18(para)
+msgid "Some OpenStack Compute features might be missing when running with LXC as the hypervisor. See the <link href=\"http://wiki.openstack.org/HypervisorSupportMatrix\">hypervisor support matrix</link> for details."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:59(filename)
-msgid "compute.log"
+#: ./doc/config-reference/compute/section_hypervisor_lxc.xml:21(para)
+msgid "To enable LXC, ensure the following options are set in <filename>/etc/nova/nova.conf</filename> on all hosts running the <systemitem class=\"service\">nova-compute</systemitem> service.<placeholder-1/>"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:62(systemitem)
-msgid "openstack-nova-compute"
+#: ./doc/config-reference/compute/section_hypervisor_lxc.xml:28(para)
+msgid "On Ubuntu 12.04, enable LXC support in OpenStack by installing the <literal>nova-compute-lxc</literal> package."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:65(systemitem) ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:141(systemitem) ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:181(systemitem)
-msgid "nova-compute"
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:134(None)
+msgid "@@image: '../../common/figures/xenserver_architecture.png'; md5=8eb25be1693aa7865967ac7b07d3e563"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:70(filename)
-msgid "conductor.log"
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:7(title)
+msgid "Xen, XenAPI, XenServer, and XCP"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:73(systemitem)
-msgid "openstack-nova-conductor"
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:9(title)
+msgid "This section needs help"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:76(systemitem)
-msgid "nova-conductor"
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:10(para)
+msgid "This section is low quality, and contains out of date information. The Documentation Team is currently looking for individuals with experience with the hypervisor to <link href=\"https://blueprints.launchpad.net/openstack-manuals/+spec/redocument-xen\">Re-document Xen integration with OpenStack</link>."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:81(filename)
-msgid "consoleauth.log"
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:16(para)
+msgid "This section describes Xen, XenAPI, XenServer, and XCP, their differences, and how to use them with OpenStack. After you understand how the Xen and KVM architectures differ, you can determine when to use each architecture in your OpenStack cloud."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:84(systemitem)
-msgid "openstack-nova-consoleauth"
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:22(title)
+msgid "Xen terminology"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:87(systemitem)
-msgid "nova-consoleauth"
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:23(para)
+msgid "<emphasis role=\"bold\">Xen</emphasis>. A hypervisor that provides the fundamental isolation between virtual machines. Xen is open source (GPLv2) and is managed by Xen.org, an cross-industry organization."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:92(filename)
-msgid "network.log"
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:27(para)
+msgid "Xen is a component of many different products and projects. The hypervisor itself is very similar across all these projects, but the way that it is managed can be different, which can cause confusion if you're not clear which tool stack you are using. Make sure you know what tool stack you want before you get started."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:93(para)
-msgid "The <systemitem>nova</systemitem> network service (<systemitem>openstack-nova-network</systemitem>/<systemitem>nova-network</systemitem>) only runs in deployments that are not configured to use the Networking service (<systemitem>neutron</systemitem>)."
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:33(para)
+msgid "<emphasis role=\"bold\">Xen Cloud Platform (XCP)</emphasis>. An open source (GPLv2) tool stack for Xen. It is designed specifically as a platform for enterprise and cloud computing, and is well integrated with OpenStack. XCP is available both as a binary distribution, installed from an iso, and from Linux distributions, such as <link href=\"http://packages.ubuntu.com/precise/xcp-xapi\">xcp-xapi</link> in Ubuntu. The current versions of XCP available in Linux distributions do not yet include all the features available in the binary distribution of XCP."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:100(systemitem)
-msgid "openstack-nova-network"
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:45(para)
+msgid "<emphasis role=\"bold\">Citrix XenServer</emphasis>. A commercial product. It is based on XCP, and exposes the same tool stack and management API. As an analogy, think of XenServer being based on XCP in the way that Red Hat Enterprise Linux is based on Fedora. XenServer has a free version (which is very similar to XCP) and paid-for versions with additional features enabled. Citrix provides support for XenServer, but as of July 2012, they do not provide any support for XCP. For a comparison between these products see the <link href=\"http://wiki.xen.org/wiki/XCP/XenServer_Feature_Matrix\"> XCP Feature Matrix</link>."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:103(systemitem)
-msgid "nova-network"
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:57(para)
+msgid "Both XenServer and XCP include Xen, Linux, and the primary control daemon known as <emphasis role=\"bold\">xapi</emphasis>."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:108(filename)
-msgid "nova-manage.log"
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:60(para)
+msgid "The API shared between XCP and XenServer is called <emphasis role=\"bold\">XenAPI</emphasis>. OpenStack usually refers to XenAPI, to indicate that the integration works equally well on XCP and XenServer. Sometimes, a careless person will refer to XenServer specifically, but you can be reasonably confident that anything that works on XenServer will also work on the latest version of XCP. Read the <link href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/sdk.html#object_model_overview\"> XenAPI Object Model Overview</link> for definitions of XenAPI specific terms such as SR, VDI, VIF and PIF."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:111(systemitem) ./doc/config-reference/compute/section_nova-log-files.xml:114(systemitem)
-msgid "nova-manage"
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:73(title)
+msgid "Privileged and unprivileged domains"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:119(filename) ./doc/config-reference/block-storage/section_cinder-log-files.xml:54(filename)
-msgid "scheduler.log"
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:74(para)
+msgid "A Xen host runs a number of virtual machines, VMs, or domains (the terms are synonymous on Xen). One of these is in charge of running the rest of the system, and is known as \"domain 0,\" or \"dom0.\" It is the first domain to boot after Xen, and owns the storage and networking hardware, the device drivers, and the primary control software. Any other VM is unprivileged, and are known as a \"domU\" or \"guest\". All customer VMs are unprivileged of course, but you should note that on Xen the OpenStack control software (<systemitem class=\"service\">nova-compute</systemitem>) also runs in a domU. This gives a level of security isolation between the privileged system software and the OpenStack software (much of which is customer-facing). This architecture is described in more detail later."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:122(systemitem)
-msgid "openstack-nova-scheduler"
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:90(para)
+msgid "There is an ongoing project to split domain 0 into multiple privileged domains known as <emphasis role=\"bold\">driver domains</emphasis> and <emphasis role=\"bold\">stub domains</emphasis>. This would give even better separation between critical components. This technology is what powers Citrix XenClient RT, and is likely to be added into XCP in the next few years. However, the current architecture just has three levels of separation: dom0, the OpenStack domU, and the completely unprivileged customer VMs."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_nova-log-files.xml:125(systemitem)
-msgid "nova-scheduler"
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:103(title)
+msgid "Paravirtualized versus hardware virtualized domains"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:105(para)
+msgid "A Xen virtual machine can be <emphasis role=\"bold\">paravirtualized (PV)</emphasis> or <emphasis role=\"bold\">hardware virtualized (HVM)</emphasis>. This refers to the interaction between Xen, domain 0, and the guest VM's kernel. PV guests are aware of the fact that they are virtualized and will co-operate with Xen and domain 0; this gives them better performance characteristics. HVM guests are not aware of their environment, and the hardware has to pretend that they are running on an unvirtualized machine. HVM guests do not need to modify the guest operating system, which is essential when running Windows."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:118(para)
+msgid "In OpenStack, customer VMs may run in either PV or HVM mode. However, the OpenStack domU (that's the one running <systemitem class=\"service\">nova-compute</systemitem>) <emphasis role=\"bold\">must</emphasis> be running in PV mode."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:126(title)
+msgid "XenAPI Deployment Architecture"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:128(para)
+msgid "When you deploy OpenStack on XCP or XenServer, you get something similar to this: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:140(para)
+msgid "The hypervisor: Xen"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:143(para)
+msgid "Domain 0: runs xapi and some small pieces from OpenStack (some xapi plug-ins and network isolation rules). The majority of this is provided by XenServer or XCP (or yourself using Kronos)."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:150(para)
+msgid "OpenStack VM: The <systemitem class=\"service\">nova-compute</systemitem> code runs in a paravirtualized virtual machine, running on the host under management. Each host runs a local instance of <systemitem class=\"service\">nova-compute</systemitem>. It will often also be running nova-network (depending on your network mode). In this case, nova-network is managing the addresses given to the tenant VMs through DHCP."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:162(para)
+msgid "Nova uses the XenAPI Python library to talk to xapi, and it uses the Management Network to reach from the domU to dom0 without leaving the host."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:138(para)
+msgid "Key things to note: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:170(para)
+msgid "The above diagram assumes FlatDHCP networking (the DevStack default)."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:176(para)
+msgid "Management network - RabbitMQ, MySQL, etc. Please note that the VM images are downloaded by the XenAPI plug-ins, so make sure that the images can be downloaded through the management network. It usually means binding those services to the management interface."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:186(para)
+msgid "Tenant network - controlled by nova-network. The parameters of this network depend on the networking model selected (Flat, Flat DHCP, VLAN)."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:193(para)
+msgid "Public network - floating IPs, public API endpoints."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:174(para)
+msgid "There are three main OpenStack Networks:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:199(para)
+msgid "The networks shown here must be connected to the corresponding physical networks within the data center. In the simplest case, three individual physical network cards could be used. It is also possible to use VLANs to separate these networks. Please note, that the selected configuration must be in line with the networking model selected for the cloud. (In case of VLAN networking, the physical channels have to be able to forward the tagged traffic.)"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:168(para)
+msgid "Some notes on the networking: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:214(title)
+msgid "XenAPI pools"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:215(para)
+msgid "The host-aggregates feature enables you to create pools of XenServer hosts to enable live migration when using shared storage. However, you cannot configure shared storage."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:221(title)
+msgid "Further reading"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:225(para)
+msgid "Citrix XenServer official documentation:<link href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/\"> http://docs.vmd.citrix.com/XenServer</link>."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:232(para)
+msgid "What is Xen? by Xen.org: <link href=\"http://xen.org/files/Marketing/WhatisXen.pdf\"> http://xen.org/files/Marketing/WhatisXen.pdf</link>."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:238(para)
+msgid "Xen Hypervisor project: <link href=\"http://xen.org/products/xenhyp.html\"> http://xen.org/products/xenhyp.html</link>."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:244(para)
+msgid "XCP project: <link href=\"http://xen.org/products/cloudxen.html\"> http://xen.org/products/cloudxen.html</link>."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:250(para)
+msgid "Further XenServer and OpenStack information: <link href=\"http://wiki.openstack.org/XenServer\"> http://wiki.openstack.org/XenServer</link>."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_introduction-to-xen.xml:222(para)
+msgid "Here are some of the resources available to learn more about Xen: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:6(title)
+msgid "Cells"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:8(para)
+msgid "<emphasis role=\"italic\">Cells</emphasis> functionality allows you to scale an OpenStack Compute cloud in a more distributed fashion without having to use complicated technologies like database and message queue clustering. It is intended to support very large deployments."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:12(para)
+msgid "When this functionality is enabled, the hosts in an OpenStack Compute cloud are partitioned into groups called cells. Cells are configured as a tree. The top-level cell should have a host that runs a <systemitem class=\"service\">nova-api</systemitem> service, but no <systemitem class=\"service\">nova-compute</systemitem> services. Each child cell should run all of the typical <systemitem class=\"service\">nova-*</systemitem> services in a regular Compute cloud except for <systemitem class=\"service\">nova-api</systemitem>. You can think of cells as a normal Compute deployment in that each cell has its own database server and message queue broker."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:20(para)
+msgid "The <systemitem class=\"service\">nova-cells</systemitem> service handles communication between cells and selects cells for new instances. This service is required for every cell. Communication between cells is pluggable, and currently the only option is communication through RPC."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:24(para)
+msgid "Cells scheduling is separate from host scheduling. <systemitem class=\"service\">nova-cells</systemitem> first picks a cell. Once a cell is selected and the new build request reaches its <systemitem class=\"service\">nova-cells</systemitem> service, it is sent over to the host scheduler in that cell and the build proceeds as it would have without cells."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:32(para)
+msgid "Cell functionality is currently considered experimental."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:35(title)
+msgid "Cell configuration options"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:40(literal)
+msgid "enable"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:42(para)
+msgid "Set this is <literal>True</literal> to turn on cell functionality, which is off by default."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:47(literal)
+msgid "name"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:49(para)
+msgid "Name of the current cell. This must be unique for each cell."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:53(literal)
+msgid "capabilities"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:55(para)
+msgid "List of arbitrary <literal><replaceable>key</replaceable>=<replaceable>value</replaceable></literal> pairs defining capabilities of the current cell. Values include <literal>hypervisor=xenserver;kvm,os=linux;windows</literal>."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:63(literal)
+msgid "call_timeout"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:65(para)
+msgid "How long in seconds to wait for replies from calls between cells."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:70(term)
+msgid "scheduler_filter_classes"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:72(para)
+msgid "Filter classes that the cells scheduler should use. By default, uses \"<literal>nova.cells.filters.all_filters</literal>\" to map to all cells filters included with Compute."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:78(term) ./doc/config-reference/compute/section_compute-scheduler.xml:637(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:726(literal)
+msgid "scheduler_weight_classes"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:79(para)
+msgid "Weight classes the cells scheduler should use. By default, uses \"<literal>nova.cells.weights.all_weighers</literal>\" to map to all cells weight algorithms (weighers) included with Compute."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:85(term) ./doc/config-reference/compute/section_compute-scheduler.xml:620(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:622(option) ./doc/config-reference/compute/section_compute-scheduler.xml:719(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:721(option)
+msgid "ram_weight_multiplier"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:87(para)
+msgid "Multiplier used for weighing ram. Negative numbers mean you want Compute to stack VMs on one host instead of spreading out new VMs to more hosts in the cell. Default value is 10.0."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:36(para)
+msgid "Cells are disabled by default. All cell-related configuration options go under a <literal>[cells]</literal> section in <filename>nova.conf</filename>. The following cell-related options are currently supported:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:96(title)
+msgid "Configure the API (top-level) cell"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:97(para)
+msgid "The compute API class must be changed in the API cell so that requests can be proxied through nova-cells down to the correct cell properly. Add the following to <filename>nova.conf</filename> in the API cell:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:109(title)
+msgid "Configure the child cells"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:118(replaceable)
+msgid "cell1"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:110(para)
+msgid "Add the following to <filename>nova.conf</filename> in the child cells, replacing <replaceable>cell1</replaceable> with the name of each cell:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:121(title)
+msgid "Configure the database in each cell"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:122(para)
+msgid "Before bringing the services online, the database in each cell needs to be configured with information about related cells. In particular, the API cell needs to know about its immediate children, and the child cells must know about their immediate agents. The information needed is the <application>RabbitMQ</application> server credentials for the particular cell."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:127(para)
+msgid "Use the <placeholder-1/> command to add this information to the database in each cell:<placeholder-2/>"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:149(para)
+msgid "As an example, assume we have an API cell named <literal>api</literal> and a child cell named <literal>cell1</literal>. Within the api cell, we have the following RabbitMQ server info:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:157(para)
+msgid "And in the child cell named <literal>cell1</literal> we have the following RabbitMQ server info:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:164(para)
+msgid "We would run this in the API cell, as root.<placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:169(para)
+msgid "Repeat the above for all child cells."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:170(para)
+msgid "In the child cell, we would run the following, as root:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:175(para)
+msgid "To customize the Compute cells, use the configuration option settings documented in <xref linkend=\"config_table_nova_cells\"/>."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:180(title)
+msgid "Cell scheduling configuration"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:181(para)
+msgid "To determine the best cell for launching a new instance, Compute uses a set of filters and weights configured in <filename>/etc/nova/nova.conf</filename>. The following options are available to prioritize cells for scheduling:"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:187(para)
+msgid "<code>scheduler_filter_classes</code> - Specifies the list of filter classes. By default <code>nova.cells.weights.all_filters</code> is specified, which maps to all cells filters included with Compute (see <xref linkend=\"scheduler-filters\"/>)."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:193(para)
+msgid "<code>scheduler_weight_classes</code> - Specifies the list of weight classes. By default <code>nova.cells.weights.all_weighers</code> is specified, which maps to all cell weight algorithms (weighers) included with Compute. The following modules are available:"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:198(para)
+msgid "<code>mute_child</code>: Downgrades the likelihood of child cells being chosen for scheduling requests, which haven't sent capacity or capability updates in a while. Options include <code>mute_weight_multiplier</code> (multiplier for mute children; value should be negative) and <code>mute_weight_value</code> (assigned to mute children; should be a positive value)."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:207(para)
+msgid "<code>ram_by_instance_type</code>: Select cells with the most RAM capacity for the instance type being requested. Because higher weights win, Compute returns the number of available units for the instance type requested. The <code>ram_weight_multiplier</code> option defaults to 10.0 that adds to the weight by a factor of 10. Use a negative number to stack VMs on one host instead of spreading out new VMs to more hosts in the cell."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:215(para)
+msgid "<code>weight_offset</code>: Allows modifying the database to weight a particular cell. You can use this when you want to disable a cell (for example, '0'), or to set a default cell by making its weight_offset very high (for example, '999999999999999'). The highest weight will be the first cell to be scheduled for launching an instance."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:223(para)
+msgid "Additionally, the following options are available for the cell scheduler:"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:227(para)
+msgid "<code>scheduler_retries</code> - Specifies how many times the scheduler tries to launch a new instance when no cells are available (default=10)."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:231(para)
+msgid "<code>scheduler_retry_delay</code> - Specifies the delay (in seconds) between retries (default=2)."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:236(para)
+msgid "As an admin user, you can also add a filter that directs builds to a particular cell. The <filename>policy.json</filename> file must have a line with <literal>\"cells_scheduler_filter:TargetCellFilter\" : \"is_admin:True\"</literal> to let an admin user specify a scheduler hint to direct a build to a particular cell."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:243(title)
+msgid "Optional cell configuration"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:244(para)
+msgid "Cells currently keeps all inter-cell communication data, including user names and passwords, in the database. This is undesirable and unnecessary since cells data isn't updated very frequently. Instead, create a JSON file to input cells data specified via a <code>[cells]cells_config</code> option. When specified, the database is no longer consulted when reloading cells data. The file will need the columns present in the Cell model (excluding common database fields and the <code>id</code> column). The queue connection information must be specified through a <code>transport_url</code> field, instead of <code>username</code>, <code>password</code>, and so on. The <code>transport_url</code> has the following form:"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:256(replaceable)
+msgid "USERNAME"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:256(replaceable)
+msgid "PASSWORD"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:256(replaceable)
+msgid "HOSTNAME"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:256(replaceable)
+msgid "PORT"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:256(replaceable)
+msgid "VIRTUAL_HOST"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-cells.xml:257(para)
+msgid "The scheme can be either <literal>qpid</literal> or <literal>rabbit</literal>, as shown previously. The following sample shows this optional configuration:"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:7(title)
+msgid "QEMU"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:8(para)
+msgid "From the perspective of the Compute service, the QEMU hypervisor is very similar to the KVM hypervisor. Both are controlled through libvirt, both support the same feature set, and all virtual machine images that are compatible with KVM are also compatible with QEMU. The main difference is that QEMU does not support native virtualization. Consequently, QEMU has worse performance than KVM and is a poor choice for a production deployment."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:15(para)
+msgid "Running on older hardware that lacks virtualization support."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:19(para)
+msgid "Running the Compute service inside of a virtual machine for development or testing purposes, where the hypervisor does not support native virtualization for guests."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:13(para)
+msgid "The typical uses cases for QEMU are<placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:25(para)
+msgid "To enable QEMU, add these settings to <filename>nova.conf</filename>:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:30(para)
+msgid "For some operations you may also have to install the <placeholder-1/> utility:"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:32(para)
+msgid "On Ubuntu: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:35(para)
+msgid "On Red Hat Enterprise Linux, Fedora, or CentOS: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:38(para)
+msgid "On openSUSE: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:41(para)
+msgid "The QEMU hypervisor supports the following virtual machine image formats:"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:44(para) ./doc/config-reference/compute/section_hypervisor_kvm.xml:24(para)
+msgid "Raw"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:47(para) ./doc/config-reference/compute/section_hypervisor_kvm.xml:27(para)
+msgid "QEMU Copy-on-write (qcow2)"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:50(para)
+msgid "VMware virtual machine disk format (vmdk)"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:54(title)
+msgid "Tips and fixes for QEMU on RHEL"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:55(para)
+msgid "If you are testing OpenStack in a virtual machine, you must configure Compute to use qemu without KVM and hardware virtualization. The second command relaxes SELinux rules to allow this mode of operation (<link href=\"https://bugzilla.redhat.com/show_bug.cgi?id=753589\"> https://bugzilla.redhat.com/show_bug.cgi?id=753589</link>). The last two commands here work around a libvirt issue fixed in Red Hat Enterprise Linux 6.4. Nested virtualization will be the much slower TCG variety, and you should provide lots of memory to the top-level guest, because the OpenStack-created guests default to 2GM RAM with no overcommit."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:64(para)
+msgid "The second command, <placeholder-1/>, may take a while."
 msgstr ""
 
 #. When image changes, this message will be marked fuzzy or untranslated for you.
@@ -2266,10 +8059,6 @@ msgstr ""
 msgid "vmware_disktype property"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:317(th) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:53(title)
-msgid "VMDK disk type"
-msgstr ""
-
 #: ./doc/config-reference/compute/section_hypervisor_vmware.xml:322(td)
 msgid "sparse"
 msgstr ""
@@ -2278,10 +8067,6 @@ msgstr ""
 msgid "Monolithic Sparse"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:328(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:74(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:76(td)
-msgid "thin"
-msgstr ""
-
 #: ./doc/config-reference/compute/section_hypervisor_vmware.xml:330(para)
 msgid "VMFS flat, thin provisioned"
 msgstr ""
@@ -2546,6 +8331,274 @@ msgstr ""
 msgid "To customize the VMware driver, use the configuration option settings documented in <xref linkend=\"config_table_nova_vmware\"/>."
 msgstr ""
 
+#: ./doc/config-reference/compute/section_compute-options-reference.xml:6(title)
+msgid "Compute sample configuration files"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-options-reference.xml:8(title)
+msgid "nova.conf - configuration options"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_compute-options-reference.xml:9(para)
+msgid "For a complete list of all available configuration options for each OpenStack Compute service, run bin/nova-&lt;servicename&gt; --help."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:6(para)
+msgid "KVM is configured as the default hypervisor for Compute."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:8(para)
+msgid "This document contains several sections about hypervisor selection. If you are reading this document linearly, you do not want to load the KVM module before you install <systemitem class=\"service\">nova-compute</systemitem>. The <systemitem class=\"service\">nova-compute</systemitem> service depends on qemu-kvm, which installs <filename>/lib/udev/rules.d/45-qemu-kvm.rules</filename>, which sets the correct permissions on the /dev/kvm device node."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:15(para)
+msgid "To enable KVM explicitly, add the following configuration options to the <filename>/etc/nova/nova.conf</filename> file:"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:21(para)
+msgid "The KVM hypervisor supports the following virtual machine image formats:"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:30(para)
+msgid "QED Qemu Enhanced Disk"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:33(para)
+msgid "VMWare virtual machine disk format (vmdk)"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:36(para)
+msgid "This section describes how to enable KVM on your system. For more information, see the following distribution-specific documentation:"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:40(para)
+msgid "<link href=\"http://fedoraproject.org/wiki/Getting_started_with_virtualization\">Fedora: Getting started with virtualization</link> from the Fedora project wiki."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:46(para)
+msgid "<link href=\"https://help.ubuntu.com/community/KVM/Installation\">Ubuntu: KVM/Installation</link> from the Community Ubuntu documentation."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:50(para)
+msgid "<link href=\"http://static.debian-handbook.info/browse/stable/sect.virtualization.html#idp11279352\">Debian: Virtualization with KVM</link> from the Debian handbook."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:55(para)
+msgid "<link href=\"http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Host_Configuration_and_Guest_Installation_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system.html\">Red Hat Enterprise Linux: Installing virtualization packages on an existing Red Hat Enterprise Linux system</link> from the <citetitle>Red Hat Enterprise Linux Virtualization Host Configuration and Guest Installation Guide</citetitle>."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:63(para)
+msgid "<link href=\"http://doc.opensuse.org/documentation/html/openSUSE/opensuse-kvm/cha.kvm.requires.html#sec.kvm.requires.install\">openSUSE: Installing KVM</link> from the openSUSE Virtualization with KVM manual."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:69(para)
+msgid "<link href=\"http://doc.opensuse.org/products/draft/SLES/SLES-kvm_sd_draft/cha.kvm.requires.html#sec.kvm.requires.install\">SLES: Installing KVM</link> from the SUSE Linux Enterprise Server Virtualization with KVM manual."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:79(title)
+msgid "Specify the CPU model of KVM guests"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:80(para)
+msgid "The Compute service enables you to control the guest CPU model that is exposed to KVM virtual machines. Use cases include:"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:84(para)
+msgid "To maximize performance of virtual machines by exposing new host CPU features to the guest"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:88(para)
+msgid "To ensure a consistent default CPU across all machines, removing reliance of variable QEMU defaults"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:92(para)
+msgid "In libvirt, the CPU is specified by providing a base CPU model name (which is a shorthand for a set of feature flags), a set of additional feature flags, and the topology (sockets/cores/threads). The libvirt KVM driver provides a number of standard CPU model names. These models are defined in the <filename>/usr/share/libvirt/cpu_map.xml</filename> file. Check this file to determine which models are supported by your local installation."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:98(para)
+msgid "Two Compute configuration options in the <literal>[libvirt]</literal> group of <filename>nova.conf</filename> define which type of CPU model is exposed to the hypervisor when using KVM: <literal>cpu_mode</literal> and <literal>cpu_model</literal>."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:102(para)
+msgid "The <literal>cpu_mode</literal> option can take one of the following values: <literal>none</literal>, <literal>host-passthrough</literal>, <literal>host-model</literal>, and <literal>custom</literal>."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:106(title)
+msgid "Host model (default for KVM &amp; QEMU)"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:107(para)
+msgid "If your <filename>nova.conf</filename> file contains <literal>cpu_mode=host-model</literal>, libvirt identifies the CPU model in <filename>/usr/share/libvirt/cpu_map.xml</filename> file that most closely matches the host, and requests additional CPU flags to complete the match. This configuration provides the maximum functionality and performance and maintains good reliability and compatibility if the guest is migrated to another host with slightly different host CPUs."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:116(title)
+msgid "Host pass through"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:117(para)
+msgid "If your <filename>nova.conf</filename> file contains <literal>cpu_mode=host-passthrough</literal>, libvirt tells KVM to pass through the host CPU with no modifications. The difference to host-model, instead of just matching feature flags, every last detail of the host CPU is matched. This gives absolutely best performance, and can be important to some apps which check low level CPU details, but it comes at a cost with respect to migration: the guest can only be migrated to an exactly matching host CPU."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:126(title)
+msgid "Custom"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:127(para)
+msgid "If your <filename>nova.conf</filename> file contains <literal>cpu_mode=custom</literal>, you can explicitly specify one of the supported named model using the cpu_model configuration option. For example, to configure the KVM guests to expose Nehalem CPUs, your <filename>nova.conf</filename> file should contain:"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:137(title)
+msgid "None (default for all libvirt-driven hypervisors other than KVM &amp; QEMU)"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:139(para)
+msgid "If your <filename>nova.conf</filename> file contains <literal>cpu_mode=none</literal>, libvirt does not specify a CPU model. Instead, the hypervisor chooses the default model."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:145(title)
+msgid "Guest agent support"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:146(para)
+msgid "Use guest agents to enable optional access between compute nodes and guests through a socket, using the QMP protocol."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:148(para)
+msgid "To enable this feature, you must set <literal>hw_qemu_guest_agent=yes</literal> as a metadata parameter on the image you wish to use to create guest-agent-capable instances from. You can explicitly disable the feature by setting <literal>hw_qemu_guest_agent=no</literal> in the image metadata."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:154(title)
+msgid "KVM performance tweaks"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:155(para)
+msgid "The <link href=\"http://www.linux-kvm.org/page/VhostNet\">VHostNet</link> kernel module improves network performance. To load the kernel module, run the following command as root:"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:161(title)
+msgid "Troubleshoot KVM"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:162(para)
+msgid "Trying to launch a new virtual machine instance fails with the <literal>ERROR</literal>state, and the following error appears in the <filename>/var/log/nova/nova-compute.log</filename> file:"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:166(para)
+msgid "This message indicates that the KVM kernel modules were not loaded."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:167(para)
+msgid "If you cannot start VMs after installation without rebooting, the permissions might not be correct. This can happen if you load the KVM module before you install <systemitem class=\"service\">nova-compute</systemitem>. To check whether the group is set to <systemitem>kvm</systemitem>, run:"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_hypervisor_kvm.xml:172(para)
+msgid "If it is not set to <systemitem>kvm</systemitem>, run:"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_nova-log-files.xml:6(title)
+msgid "Compute log files"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_nova-log-files.xml:7(para)
+msgid "The corresponding log file of each Compute service is stored in the <filename>/var/log/nova/</filename> directory of the host on which each service runs."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_nova-log-files.xml:11(caption)
+msgid "Log files used by Compute services"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_nova-log-files.xml:20(td)
+msgid "Service name (CentOS/Fedora/openSUSE/Red Hat Enterprise Linux/SUSE Linux Enterprise)"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_nova-log-files.xml:24(td)
+msgid "Service name (Ubuntu/Debian)"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_nova-log-files.xml:34(td)
+msgid "openstack-nova-api"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_nova-log-files.xml:43(filename)
+msgid "cert.log"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_nova-log-files.xml:45(para)
+msgid "The X509 certificate service (<systemitem>openstack-nova-cert</systemitem>/<systemitem>nova-cert</systemitem>) is only required by the EC2 API to the Compute service."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_nova-log-files.xml:51(systemitem)
+msgid "openstack-nova-cert"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_nova-log-files.xml:54(systemitem)
+msgid "nova-cert"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_nova-log-files.xml:59(filename)
+msgid "compute.log"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_nova-log-files.xml:62(systemitem)
+msgid "openstack-nova-compute"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_nova-log-files.xml:70(filename)
+msgid "conductor.log"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_nova-log-files.xml:73(systemitem)
+msgid "openstack-nova-conductor"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_nova-log-files.xml:76(systemitem)
+msgid "nova-conductor"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_nova-log-files.xml:81(filename)
+msgid "consoleauth.log"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_nova-log-files.xml:84(systemitem)
+msgid "openstack-nova-consoleauth"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_nova-log-files.xml:87(systemitem)
+msgid "nova-consoleauth"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_nova-log-files.xml:92(filename)
+msgid "network.log"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_nova-log-files.xml:93(para)
+msgid "The <systemitem>nova</systemitem> network service (<systemitem>openstack-nova-network</systemitem>/<systemitem>nova-network</systemitem>) only runs in deployments that are not configured to use the Networking service (<systemitem>neutron</systemitem>)."
+msgstr ""
+
+#: ./doc/config-reference/compute/section_nova-log-files.xml:100(systemitem)
+msgid "openstack-nova-network"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_nova-log-files.xml:103(systemitem)
+msgid "nova-network"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_nova-log-files.xml:108(filename)
+msgid "nova-manage.log"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_nova-log-files.xml:111(systemitem) ./doc/config-reference/compute/section_nova-log-files.xml:114(systemitem)
+msgid "nova-manage"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_nova-log-files.xml:122(systemitem)
+msgid "openstack-nova-scheduler"
+msgstr ""
+
+#: ./doc/config-reference/compute/section_nova-log-files.xml:125(systemitem)
+msgid "nova-scheduler"
+msgstr ""
+
 #. When image changes, this message will be marked fuzzy or untranslated for you.
 #. It doesn't matter what you translate it to: it's not used at all.
 #: ./doc/config-reference/compute/section_compute-scheduler.xml:112(None)
@@ -3062,18 +9115,6 @@ msgstr ""
 msgid "Section"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-scheduler.xml:613(th) ./doc/config-reference/compute/section_compute-scheduler.xml:694(th) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:319(td)
-msgid "Option"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-scheduler.xml:614(th) ./doc/config-reference/compute/section_compute-scheduler.xml:695(th) ./doc/config-reference/block-storage/drivers/coraid-driver.xml:358(th) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:322(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:309(th) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:206(th) ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:80(th) ./doc/config-reference/dashboard/section_dashboard-log-files.xml:22(td)
-msgid "Description"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-scheduler.xml:620(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:622(option) ./doc/config-reference/compute/section_compute-scheduler.xml:719(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:721(option) ./doc/config-reference/compute/section_compute-cells.xml:85(term)
-msgid "ram_weight_multiplier"
-msgstr ""
-
 #: ./doc/config-reference/compute/section_compute-scheduler.xml:621(td)
 msgid "By default, the scheduler spreads instances across all hosts evenly. Set the <placeholder-1/> option to a negative number if you prefer stacking instead of spreading. Use a floating-point value."
 msgstr ""
@@ -3086,10 +9127,6 @@ msgstr ""
 msgid "New instances are scheduled on a host that is chosen randomly from a subset of the N best hosts. This property defines the subset size from which a host is chosen. A value of 1 chooses the first host returned by the weighing functions.This value must be at least 1. A value less than 1 is ignored, and 1 is used instead. Use an integer value."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-scheduler.xml:637(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:726(literal) ./doc/config-reference/compute/section_compute-cells.xml:78(term)
-msgid "scheduler_weight_classes"
-msgstr ""
-
 #: ./doc/config-reference/compute/section_compute-scheduler.xml:638(literal)
 msgid "nova.scheduler.weights.all_weighers"
 msgstr ""
@@ -3202,6201 +9239,164 @@ msgstr ""
 msgid "To customize the Compute scheduler, use the configuration option settings documented in <xref linkend=\"config_table_nova_scheduling\"/>."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:6(title)
-msgid "Cells"
+#: ./doc/config-reference/compute/section_compute-sample-configuration-files.xml:5(para)
+msgid "Files in this section can be found in <systemitem>/etc/nova</systemitem>."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:8(para)
-msgid "<emphasis role=\"italic\">Cells</emphasis> functionality allows you to scale an OpenStack Compute cloud in a more distributed fashion without having to use complicated technologies like database and message queue clustering. It is intended to support very large deployments."
+#: ./doc/config-reference/compute/section_compute-sample-configuration-files.xml:8(para)
+msgid "The Compute service stores its API configuration settings in the <filename>api-paste.ini</filename> file."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:12(para)
-msgid "When this functionality is enabled, the hosts in an OpenStack Compute cloud are partitioned into groups called cells. Cells are configured as a tree. The top-level cell should have a host that runs a <systemitem class=\"service\">nova-api</systemitem> service, but no <systemitem class=\"service\">nova-compute</systemitem> services. Each child cell should run all of the typical <systemitem class=\"service\">nova-*</systemitem> services in a regular Compute cloud except for <systemitem class=\"service\">nova-api</systemitem>. You can think of cells as a normal Compute deployment in that each cell has its own database server and message queue broker."
+#: ./doc/config-reference/compute/section_compute-sample-configuration-files.xml:16(para)
+msgid "The <filename>policy.json</filename> file defines additional access controls that apply to the Compute service."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:20(para)
-msgid "The <systemitem class=\"service\">nova-cells</systemitem> service handles communication between cells and selects cells for new instances. This service is required for every cell. Communication between cells is pluggable, and currently the only option is communication through RPC."
+#: ./doc/config-reference/compute/section_compute-sample-configuration-files.xml:23(para)
+msgid "The <filename>rootwrap.conf</filename> file defines configuration values used by the rootwrap script when the Compute service needs to escalate its privileges to those of the root user."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:24(para)
-msgid "Cells scheduling is separate from host scheduling. <systemitem class=\"service\">nova-cells</systemitem> first picks a cell. Once a cell is selected and the new build request reaches its <systemitem class=\"service\">nova-cells</systemitem> service, it is sent over to the host scheduler in that cell and the build proceeds as it would have without cells."
+#: ./doc/config-reference/compute/section_compute-hypervisors.xml:6(title)
+msgid "Hypervisors"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:32(para)
-msgid "Cell functionality is currently considered experimental."
+#: ./doc/config-reference/compute/section_compute-hypervisors.xml:7(para)
+msgid "OpenStack Compute supports many hypervisors, which might make it difficult for you to choose one. Most installations use only one hypervisor. However you can use <xref linkend=\"computefilter\"/> and <xref linkend=\"imagepropertiesfilter\"/> to schedule to different hypervisors within the same installation. The following links help you choose a hypervisor. See <link href=\"http://wiki.openstack.org/HypervisorSupportMatrix\">http://wiki.openstack.org/HypervisorSupportMatrix</link> for a detailed list of features and support across the hypervisors."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:35(title)
-msgid "Cell configuration options"
+#: ./doc/config-reference/compute/section_compute-hypervisors.xml:18(para)
+msgid "The following hypervisors are supported:"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:40(literal)
-msgid "enable"
+#: ./doc/config-reference/compute/section_compute-hypervisors.xml:21(para)
+msgid "<link href=\"http://www.linux-kvm.org/page/Main_Page\">KVM</link> - Kernel-based Virtual Machine. The virtual disk formats that it supports is inherited from QEMU since it uses a modified QEMU program to launch the virtual machine. The supported formats include raw images, the qcow2, and VMware formats."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:42(para)
-msgid "Set this is <literal>True</literal> to turn on cell functionality, which is off by default."
+#: ./doc/config-reference/compute/section_compute-hypervisors.xml:30(para)
+msgid "<link href=\"http://lxc.sourceforge.net/\">LXC</link> - Linux Containers (through libvirt), use to run Linux-based virtual machines."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:47(literal)
-msgid "name"
+#: ./doc/config-reference/compute/section_compute-hypervisors.xml:35(para)
+msgid "<link href=\"http://wiki.qemu.org/Manual\">QEMU</link> - Quick EMUlator, generally only used for development purposes."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:49(para)
-msgid "Name of the current cell. This must be unique for each cell."
+#: ./doc/config-reference/compute/section_compute-hypervisors.xml:40(para)
+msgid "<link href=\"http://user-mode-linux.sourceforge.net/\">UML</link> - User Mode Linux, generally only used for development purposes."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:53(literal)
-msgid "capabilities"
+#: ./doc/config-reference/compute/section_compute-hypervisors.xml:46(para)
+msgid "<link href=\"http://www.vmware.com/products/vsphere-hypervisor/support.html\">VMware vSphere</link> 4.1 update 1 and newer, runs VMware-based Linux and Windows images through a connection with a vCenter server or directly with an ESXi host."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:55(para)
-msgid "List of arbitrary <literal><replaceable>key</replaceable>=<replaceable>value</replaceable></literal> pairs defining capabilities of the current cell. Values include <literal>hypervisor=xenserver;kvm,os=linux;windows</literal>."
+#: ./doc/config-reference/compute/section_compute-hypervisors.xml:52(para)
+msgid "<link href=\"http://www.xen.org\">Xen</link> - XenServer, Xen Cloud Platform (XCP), use to run Linux or Windows virtual machines. You must install the <systemitem class=\"service\">nova-compute</systemitem> service in a para-virtualized VM."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:63(literal)
-msgid "call_timeout"
+#: ./doc/config-reference/compute/section_compute-hypervisors.xml:60(para)
+msgid "<link href=\"http://www.microsoft.com/en-us/server-cloud/windows-server/server-virtualization-features.aspx\"> Hyper-V</link> - Server virtualization with Microsoft's Hyper-V, use to run Windows, Linux, and FreeBSD virtual machines. Runs <systemitem class=\"service\">nova-compute</systemitem> natively on the Windows virtualization platform."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:65(para)
-msgid "How long in seconds to wait for replies from calls between cells."
+#: ./doc/config-reference/compute/section_compute-hypervisors.xml:69(para)
+msgid "<link href=\"https://wiki.openstack.org/wiki/Baremetal\"> Bare Metal</link> - Not a hypervisor in the traditional sense, this driver provisions physical hardware through pluggable sub-drivers (for example, PXE for image deployment, and IPMI for power management)."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:70(term)
-msgid "scheduler_filter_classes"
+#: ./doc/config-reference/compute/section_compute-hypervisors.xml:78(title)
+msgid "Hypervisor configuration basics"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:72(para)
-msgid "Filter classes that the cells scheduler should use. By default, uses \"<literal>nova.cells.filters.all_filters</literal>\" to map to all cells filters included with Compute."
+#: ./doc/config-reference/compute/section_compute-hypervisors.xml:79(para)
+msgid "The node where the <systemitem class=\"service\">nova-compute</systemitem> service is installed and running is the machine that runs all the virtual machines, referred to as the compute node in this guide."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:79(para)
-msgid "Weight classes the cells scheduler should use. By default, uses \"<literal>nova.cells.weights.all_weighers</literal>\" to map to all cells weight algorithms (weighers) included with Compute."
+#: ./doc/config-reference/compute/section_compute-hypervisors.xml:83(para)
+msgid "By default, the selected hypervisor is KVM. To change to another hypervisor, change the <literal>virt_type</literal> option in the <literal>[libvirt]</literal> section of <filename>nova.conf</filename> and restart the <systemitem class=\"service\">nova-compute</systemitem> service."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:87(para)
-msgid "Multiplier used for weighing ram. Negative numbers mean you want Compute to stack VMs on one host instead of spreading out new VMs to more hosts in the cell. Default value is 10.0."
+#: ./doc/config-reference/compute/section_compute-hypervisors.xml:87(para)
+msgid "Here are the general <filename>nova.conf</filename> options that are used to configure the compute node's hypervisor: <xref linkend=\"config_table_nova_hypervisor\"/>."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:36(para)
-msgid "Cells are disabled by default. All cell-related configuration options go under a <literal>[cells]</literal> section in <filename>nova.conf</filename>. The following cell-related options are currently supported:<placeholder-1/>"
+#: ./doc/config-reference/compute/section_compute-hypervisors.xml:90(para)
+msgid "Specific options for particular hypervisors can be found in following sections."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:96(title)
-msgid "Configure the API (top-level) cell"
+#: ./doc/config-reference/compute/section_compute-conductor.xml:7(title)
+msgid "Conductor"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:97(para)
-msgid "The compute API class must be changed in the API cell so that requests can be proxied through nova-cells down to the correct cell properly. Add the following to <filename>nova.conf</filename> in the API cell:<placeholder-1/>"
+#: ./doc/config-reference/compute/section_compute-conductor.xml:8(para)
+msgid "The <systemitem class=\"service\">nova-conductor</systemitem> service enables OpenStack to function without compute nodes accessing the database. Conceptually, it implements a new layer on top of <systemitem class=\"service\">nova-compute</systemitem>. It should not be deployed on compute nodes, or else the security benefits of removing database access from <systemitem class=\"service\">nova-compute</systemitem> are negated. Just like other nova services such as <systemitem class=\"service\">nova-api</systemitem> or nova-scheduler, it can be scaled horizontally. You can run multiple instances of <systemitem class=\"service\">nova-conductor</systemitem> on different machines as needed for scaling purposes."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:109(title)
-msgid "Configure the child cells"
+#: ./doc/config-reference/compute/section_compute-conductor.xml:21(para)
+msgid "The methods exposed by <systemitem class=\"service\">nova-conductor</systemitem> are relatively simple methods used by <systemitem class=\"service\">nova-compute</systemitem> to offload its database operations. Places where <systemitem class=\"service\">nova-compute</systemitem> previously performed database access are now talking to <systemitem class=\"service\">nova-conductor</systemitem>. However, we have plans in the medium to long term to move more and more of what is currently in <systemitem class=\"service\">nova-compute</systemitem> up to the <systemitem class=\"service\">nova-conductor</systemitem> layer. The Compute service will start to look like a less intelligent slave service to <systemitem class=\"service\">nova-conductor</systemitem>. The conductor service will implement long running complex operations, ensuring forward progress and graceful error handling. This will be especially beneficial for operations that cross multiple compute nodes, such as migrations or resizes."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:118(replaceable)
-msgid "cell1"
+#: ./doc/config-reference/compute/section_compute-conductor.xml:40(para)
+msgid "To customize the Conductor, use the configuration option settings documented in <xref linkend=\"config_table_nova_conductor\"/>."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:110(para)
-msgid "Add the following to <filename>nova.conf</filename> in the child cells, replacing <replaceable>cell1</replaceable> with the name of each cell:<placeholder-1/>"
+#: ./doc/config-reference/compute/section_compute-configure-xen.xml:6(title) ./doc/config-reference/compute/section_compute-configure-xen.xml:70(title)
+msgid "Xen configuration reference"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:121(title)
-msgid "Configure the database in each cell"
+#: ./doc/config-reference/compute/section_compute-configure-xen.xml:7(para)
+msgid "The following section discusses some commonly changed options in XenServer. The table below provides a complete reference of all configuration options available for configuring Xen with OpenStack."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:122(para)
-msgid "Before bringing the services online, the database in each cell needs to be configured with information about related cells. In particular, the API cell needs to know about its immediate children, and the child cells must know about their immediate agents. The information needed is the <application>RabbitMQ</application> server credentials for the particular cell."
+#: ./doc/config-reference/compute/section_compute-configure-xen.xml:11(para)
+msgid "The recommended way to use Xen with OpenStack is through the XenAPI driver. To enable the XenAPI driver, add the following configuration options <filename>/etc/nova/nova.conf</filename> and restart the <systemitem class=\"service\">nova-compute</systemitem> service:"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:127(para)
-msgid "Use the <placeholder-1/> command to add this information to the database in each cell:<placeholder-2/>"
+#: ./doc/config-reference/compute/section_compute-configure-xen.xml:19(para)
+msgid "These connection details are used by the OpenStack Compute service to contact your hypervisor and are the same details you use to connect XenCenter, the XenServer management console, to your XenServer or XCP box."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:149(para)
-msgid "As an example, assume we have an API cell named <literal>api</literal> and a child cell named <literal>cell1</literal>. Within the api cell, we have the following RabbitMQ server info:<placeholder-1/>"
+#: ./doc/config-reference/compute/section_compute-configure-xen.xml:23(para)
+msgid "The <literal>xenapi_connection_url</literal> is generally the management network IP address of the XenServer. Though it is possible to use the internal network IP Address (169.250.0.1) to contact XenAPI, this does not allow live migration between hosts, and other functionalities like host aggregates do not work."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:157(para)
-msgid "And in the child cell named <literal>cell1</literal> we have the following RabbitMQ server info:<placeholder-1/>"
+#: ./doc/config-reference/compute/section_compute-configure-xen.xml:30(para)
+msgid "It is possible to manage Xen using libvirt, though this is not well-tested or supported. To experiment using Xen through libvirt add the following configuration options <filename>/etc/nova/nova.conf</filename>: <placeholder-1/>"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:164(para)
-msgid "We would run this in the API cell, as root.<placeholder-1/>"
+#: ./doc/config-reference/compute/section_compute-configure-xen.xml:39(para)
+msgid "If you don't have the guest agent on your VMs, it takes a long time for nova to decide the VM has successfully started. Generally a large timeout is required for Windows instances, bug you may want to tweak <literal>agent_version_timeout</literal>"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:169(para)
-msgid "Repeat the above for all child cells."
+#: ./doc/config-reference/compute/section_compute-configure-xen.xml:44(title)
+msgid "Firewall"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:170(para)
-msgid "In the child cell, we would run the following, as root:<placeholder-1/>"
+#: ./doc/config-reference/compute/section_compute-configure-xen.xml:45(para)
+msgid "If using nova-network, IPTables is supported: <placeholder-1/> Alternately, doing the isolation in Dom0: <placeholder-2/>"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:175(para)
-msgid "To customize the Compute cells, use the configuration option settings documented in <xref linkend=\"config_table_nova_cells\"/>."
+#: ./doc/config-reference/compute/section_compute-configure-xen.xml:51(title)
+msgid "VNC proxy address"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:180(title)
-msgid "Cell scheduling configuration"
+#: ./doc/config-reference/compute/section_compute-configure-xen.xml:52(para)
+msgid "Assuming you are talking to XenAPI through the host local management network, and XenServer is on the address: 169.254.0.1, you can use the following: <literal>vncserver_proxyclient_address=169.254.0.1</literal>"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:181(para)
-msgid "To determine the best cell for launching a new instance, Compute uses a set of filters and weights configured in <filename>/etc/nova/nova.conf</filename>. The following options are available to prioritize cells for scheduling:"
+#: ./doc/config-reference/compute/section_compute-configure-xen.xml:58(title)
+msgid "Storage"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:187(para)
-msgid "<code>scheduler_filter_classes</code> - Specifies the list of filter classes. By default <code>nova.cells.weights.all_filters</code> is specified, which maps to all cells filters included with Compute (see <xref linkend=\"scheduler-filters\"/>)."
+#: ./doc/config-reference/compute/section_compute-configure-xen.xml:65(para)
+msgid "To use a XenServer pool, you must create the pool by using the Host Aggregates feature."
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:193(para)
-msgid "<code>scheduler_weight_classes</code> - Specifies the list of weight classes. By default <code>nova.cells.weights.all_weighers</code> is specified, which maps to all cell weight algorithms (weighers) included with Compute. The following modules are available:"
+#: ./doc/config-reference/compute/section_compute-configure-xen.xml:59(para)
+msgid "You can specify which Storage Repository to use with nova by looking at the following flag. The default is to use the local-storage setup by the default installer: <placeholder-1/> Another good alternative is to use the \"default\" storage (for example if you have attached NFS or any other shared storage): <placeholder-2/><placeholder-3/>"
 msgstr ""
 
-#: ./doc/config-reference/compute/section_compute-cells.xml:198(para)
-msgid "<code>mute_child</code>: Downgrades the likelihood of child cells being chosen for scheduling requests, which haven't sent capacity or capability updates in a while. Options include <code>mute_weight_multiplier</code> (multiplier for mute children; value should be negative) and <code>mute_weight_value</code> (assigned to mute children; should be a positive value)."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-cells.xml:207(para)
-msgid "<code>ram_by_instance_type</code>: Select cells with the most RAM capacity for the instance type being requested. Because higher weights win, Compute returns the number of available units for the instance type requested. The <code>ram_weight_multiplier</code> option defaults to 10.0 that adds to the weight by a factor of 10. Use a negative number to stack VMs on one host instead of spreading out new VMs to more hosts in the cell."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-cells.xml:215(para)
-msgid "<code>weight_offset</code>: Allows modifying the database to weight a particular cell. You can use this when you want to disable a cell (for example, '0'), or to set a default cell by making its weight_offset very high (for example, '999999999999999'). The highest weight will be the first cell to be scheduled for launching an instance."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-cells.xml:223(para)
-msgid "Additionally, the following options are available for the cell scheduler:"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-cells.xml:227(para)
-msgid "<code>scheduler_retries</code> - Specifies how many times the scheduler tries to launch a new instance when no cells are available (default=10)."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-cells.xml:231(para)
-msgid "<code>scheduler_retry_delay</code> - Specifies the delay (in seconds) between retries (default=2)."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-cells.xml:236(para)
-msgid "As an admin user, you can also add a filter that directs builds to a particular cell. The <filename>policy.json</filename> file must have a line with <literal>\"cells_scheduler_filter:TargetCellFilter\" : \"is_admin:True\"</literal> to let an admin user specify a scheduler hint to direct a build to a particular cell."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-cells.xml:243(title)
-msgid "Optional cell configuration"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-cells.xml:244(para)
-msgid "Cells currently keeps all inter-cell communication data, including user names and passwords, in the database. This is undesirable and unnecessary since cells data isn't updated very frequently. Instead, create a JSON file to input cells data specified via a <code>[cells]cells_config</code> option. When specified, the database is no longer consulted when reloading cells data. The file will need the columns present in the Cell model (excluding common database fields and the <code>id</code> column). The queue connection information must be specified through a <code>transport_url</code> field, instead of <code>username</code>, <code>password</code>, and so on. The <code>transport_url</code> has the following form:"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-cells.xml:256(replaceable)
-msgid "USERNAME"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-cells.xml:256(replaceable)
-msgid "PASSWORD"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-cells.xml:256(replaceable)
-msgid "HOSTNAME"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-cells.xml:256(replaceable)
-msgid "PORT"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-cells.xml:256(replaceable)
-msgid "VIRTUAL_HOST"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_compute-cells.xml:257(para)
-msgid "The scheme can be either <literal>qpid</literal> or <literal>rabbit</literal>, as shown previously. The following sample shows this optional configuration:"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:7(title)
-msgid "QEMU"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:8(para)
-msgid "From the perspective of the Compute service, the QEMU hypervisor is very similar to the KVM hypervisor. Both are controlled through libvirt, both support the same feature set, and all virtual machine images that are compatible with KVM are also compatible with QEMU. The main difference is that QEMU does not support native virtualization. Consequently, QEMU has worse performance than KVM and is a poor choice for a production deployment."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:15(para)
-msgid "Running on older hardware that lacks virtualization support."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:19(para)
-msgid "Running the Compute service inside of a virtual machine for development or testing purposes, where the hypervisor does not support native virtualization for guests."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:13(para)
-msgid "The typical uses cases for QEMU are<placeholder-1/>"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:25(para)
-msgid "To enable QEMU, add these settings to <filename>nova.conf</filename>:<placeholder-1/>"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:30(para)
-msgid "For some operations you may also have to install the <placeholder-1/> utility:"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:32(para)
-msgid "On Ubuntu: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:35(para)
-msgid "On Red Hat Enterprise Linux, Fedora, or CentOS: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:38(para)
-msgid "On openSUSE: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:41(para)
-msgid "The QEMU hypervisor supports the following virtual machine image formats:"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:50(para)
-msgid "VMware virtual machine disk format (vmdk)"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:54(title)
-msgid "Tips and fixes for QEMU on RHEL"
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:55(para)
-msgid "If you are testing OpenStack in a virtual machine, you must configure Compute to use qemu without KVM and hardware virtualization. The second command relaxes SELinux rules to allow this mode of operation (<link href=\"https://bugzilla.redhat.com/show_bug.cgi?id=753589\"> https://bugzilla.redhat.com/show_bug.cgi?id=753589</link>). The last two commands here work around a libvirt issue fixed in Red Hat Enterprise Linux 6.4. Nested virtualization will be the much slower TCG variety, and you should provide lots of memory to the top-level guest, because the OpenStack-created guests default to 2GM RAM with no overcommit."
-msgstr ""
-
-#: ./doc/config-reference/compute/section_hypervisor_qemu.xml:64(para)
-msgid "The second command, <placeholder-1/>, may take a while."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-log-files.xml:6(title)
-msgid "Log files used by Networking"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-log-files.xml:7(para)
-msgid "The corresponding log file of each Networking service is stored in the <filename>/var/log/neutron/</filename> directory of the host on which each service runs."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-log-files.xml:11(caption)
-msgid "Log files used by Networking services"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-log-files.xml:19(td)
-msgid "Service/interface"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-log-files.xml:27(filename)
-msgid "dhcp-agent.log"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-log-files.xml:30(systemitem)
-msgid "neutron-dhcp-agent"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-log-files.xml:35(filename)
-msgid "l3-agent.log"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-log-files.xml:38(systemitem)
-msgid "neutron-l3-agent"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-log-files.xml:43(filename)
-msgid "lbaas-agent.log"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-log-files.xml:46(systemitem)
-msgid "neutron-lbaas-agent"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-log-files.xml:48(para)
-msgid "The <systemitem class=\"service\">neutron-lbaas-agent</systemitem> service only runs when Load Balancer as a Service is enabled."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-log-files.xml:56(filename)
-msgid "linuxbridge-agent.log"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-log-files.xml:59(systemitem)
-msgid "neutron-linuxbridge-agent"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-log-files.xml:64(filename)
-msgid "metadata-agent.log"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-log-files.xml:67(systemitem)
-msgid "neutron-metadata-agent"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-log-files.xml:72(filename)
-msgid "metering-agent.log"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-log-files.xml:75(systemitem)
-msgid "neutron-metering-agent"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-log-files.xml:80(filename)
-msgid "openvswitch-agent.log"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-log-files.xml:83(systemitem)
-msgid "neutron-openvswitch-agent"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-log-files.xml:88(filename)
-msgid "server.log"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-log-files.xml:91(systemitem)
-msgid "neutron-server"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins.xml:7(title)
-msgid "Networking plug-ins"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins.xml:8(para)
-msgid "OpenStack Networking introduces the concept of a plug-in, which is a back-end implementation of the OpenStack Networking API. A plug-in can use a variety of technologies to implement the logical API requests. Some OpenStack Networking plug-ins might use basic Linux VLANs and IP tables, while others might use more advanced technologies, such as L2-in-L3 tunneling or OpenFlow. These sections detail the configuration options for the various plug-ins."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins.xml:19(title)
-msgid "BigSwitch configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins.xml:25(title)
-msgid "Brocade configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins.xml:31(title)
-msgid "CISCO configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins.xml:37(title)
-msgid "CloudBase Hyper-V Agent configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins.xml:44(title)
-msgid "Embrane configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins.xml:51(title)
-msgid "IBM SDN-VE configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins.xml:57(title)
-msgid "Linux bridge Agent configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins.xml:64(title)
-msgid "Mellanox configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins.xml:70(title)
-msgid "Meta Plug-in configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins.xml:71(para)
-msgid "The Meta Plug-in allows you to use multiple plug-ins at the same time."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins.xml:79(title)
-msgid "MidoNet configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins.xml:85(title)
-msgid "NEC configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins.xml:91(title)
-msgid "Nuage configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins.xml:97(title)
-msgid "One Convergence NVSD configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins.xml:103(title)
-msgid "VMware NSX configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins.xml:109(title)
-msgid "Open vSwitch Agent configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins.xml:116(title)
-msgid "PLUMgrid configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins.xml:122(title)
-msgid "Ryu configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:7(title)
-msgid "Modular Layer 2 (ml2) configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:8(para)
-msgid "The Modular Layer 2 (ml2) plug-in has two components: network types and mechanisms. You can configure these components separately. This section describes these configuration options."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:13(title)
-msgid "MTU bug with VXLAN tunnelling"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:14(para)
-msgid "Due to a bug in Linux Bridge software maximum transmission unit (MTU) handling, using VXLAN tunnels does not work by default."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:19(para)
-msgid "A simple workaround is to increase the MTU value of the physical interface and physical switch fabric by at least 50 bytes. For example, increase the MTU value to 1550. This value enables an automatic 50-byte MTU difference between the physical interface (1500) and the VXLAN interface (automatically 1500-50 = 1450). An MTU value of 1450 causes issues when virtual machine taps are configured at an MTU value of 1500."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:30(para)
-msgid "Another workaround is to decrease the virtual ethernet devices' MTU. Set the <option>network_device_mtu</option> option to 1450 in the <filename>neutron.conf</filename> file, and set all guest virtual machines' MTU to the same value by using a DHCP option. For information about how to use this option, see <link href=\"http://docs.openstack.org/admin-guide-cloud/content/ch_networking.html#openvswitch_plugin\">Configure OVS plug-in</link>."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:45(title)
-msgid "Modular Layer 2 (ml2) Flat Type configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:50(title)
-msgid "Modular Layer 2 (ml2) GRE Type configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:55(title)
-msgid "Modular Layer 2 (ml2) VLAN Type configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:60(title)
-msgid "Modular Layer 2 (ml2) VXLAN Type configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:65(title)
-msgid "Modular Layer 2 (ml2) Arista Mechanism configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:71(title)
-msgid "Modular Layer 2 (ml2) BigSwitch Mechanism configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:76(title)
-msgid "Modular Layer 2 (ml2) Brocade Mechanism configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:81(title)
-msgid "Modular Layer 2 (ml2) Cisco Mechanism configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:86(title)
-msgid "Modular Layer 2 (ml2) Mellanox Mechanism configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:91(title)
-msgid "Modular Layer 2 (ml2) OpenDaylight Mechanism configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:96(title)
-msgid "Modular Layer 2 (ml2) OpenFlow Mechanism configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:101(title)
-msgid "Modular Layer 2 (ml2) L2 Population Mechanism configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:106(title)
-msgid "Modular Layer 2 (ml2) Tail-f NCS Mechanism configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:6(title)
-msgid "Networking configuration options"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:7(para)
-msgid "The options and descriptions listed in this introduction are auto generated from the code in the Networking service project, which provides software-defined networking between VMs run in Compute. The list contains common options, while the subsections list the options for the various networking plug-ins."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:20(para)
-msgid "Use the following options to alter agent-related settings."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:25(title)
-msgid "API"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:26(para)
-msgid "Use the following options to alter API-related settings."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:31(title)
-msgid "Token authentication"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:32(para)
-msgid "Use the following options to alter token authentication settings."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:37(title)
-msgid "CADF"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:38(para)
-msgid "Use the following options to alter Cloud Audit Data Federation (CADF) settings."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:44(para)
-msgid "Use the following options to alter Compute-related settings."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:49(title)
-msgid "Database"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:50(para) ./doc/config-reference/networking/section_networking-options-reference.xml:56(para)
-msgid "Use the following options to alter Database-related settings."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:55(title)
-msgid "DHCP agent"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:61(title)
-msgid "Embrane LBaaS driver"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:62(para)
-msgid "Use the following options to alter Embrane Loadbalancer-as-a-Service related settings."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:68(title)
-msgid "Firewall-as-a-Service driver"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:69(para)
-msgid "Use the following options in the <filename>fwaas_driver.ini</filename> file for the FwaaS driver."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:75(title)
-msgid "L3 agent"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:76(para)
-msgid "Use the following options in the <filename>l3_agent.ini</filename> file for the L3 agent."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:82(title)
-msgid "Loadbalancer-as-a-Service agent"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:83(para)
-msgid "Use the following options in the <filename>lbaas_agent.ini</filename> file for the LbaaS agent."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:89(title)
-msgid "Logging"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:90(para)
-msgid "Use the following options to alter logging settings."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:95(title)
-msgid "Metadata Agent"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:96(para)
-msgid "Use the following options in the <filename>metadata_agent.ini</filename> file for the Metadata agent."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:102(title)
-msgid "Metering Agent"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:103(para)
-msgid "Use the following options in the <filename>metering_agent.ini</filename> file for the Metering agent."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:109(title)
-msgid "Policy"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:110(para)
-msgid "Use the following options in the <filename>neutron.conf</filename> file to change policy settings."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:116(title)
-msgid "Quotas"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:117(para)
-msgid "Use the following options in the <filename>neutron.conf</filename> file for the quota system."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:123(title)
-msgid "Rootwrap"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:124(para)
-msgid "Use the following options in the <filename>neutron.conf</filename> file for the rootwrap settings"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:130(title)
-msgid "Scheduler"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:131(para)
-msgid "Use the following options in the <filename>neutron.conf</filename> file to change scheduler settings."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:137(title)
-msgid "Security Groups"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:138(para)
-msgid "Use the following options in the configuration file for your driver to change security group settings."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:144(title)
-msgid "SSL"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:145(para)
-msgid "Use the following options in the <filename>neutron.conf</filename> file to enable SSL."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:151(title)
-msgid "Testing"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:152(para)
-msgid "Use the following options to alter testing-related features."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:157(title)
-msgid "vArmour Firewall-as-a-Service driver"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:158(para)
-msgid "Use the following options in the <filename>l3_agent.ini</filename> file for the vArmour FwaaS driver."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:164(title)
-msgid "VPN"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:165(para)
-msgid "Use the following options in the <filename>vpn_agent.ini</filename> file for the VPN agent."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:171(title)
-msgid "WSGI"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-options-reference.xml:172(para)
-msgid "Use the following options in the <filename>neutron.conf</filename> file to configure the WSGI layer."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:4(title)
-msgid "Networking sample configuration files"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:5(para)
-msgid "All the files in this section can be found in <filename class=\"directory\">/etc/neutron/</filename>."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:7(title)
-msgid "neutron.conf"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:8(para)
-msgid "Use the <filename>neutron.conf</filename> file to configure the majority of the OpenStack Networking options."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:16(para)
-msgid "Use the <filename>api-paste.ini</filename> to configure the OpenStack Networking API."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:23(para)
-msgid "Use the <filename>policy.json</filename> file to define additional access controls that apply to the OpenStack Networking service."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:31(para)
-msgid "Use the <filename>rootwrap.conf</filename> file to define configuration values used by the <placeholder-1/> script when the OpenStack Networking service must escalate its privileges to those of the root user."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:39(title)
-msgid "Configuration files for plug-in agents"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:40(para)
-msgid "Each plug-in agent that runs on an OpenStack Networking node, to perform local networking configuration for the node's VMs and networking services, has its own configuration file."
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:44(title)
-msgid "dhcp_agent.ini"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:50(title)
-msgid "l3_agent.ini"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:56(title)
-msgid "lbaas_agent.ini"
-msgstr ""
-
-#: ./doc/config-reference/networking/section_networking-sample-configuration-files.xml:62(title)
-msgid "metadata_agent.ini"
-msgstr ""
-
-#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:7(title) ./doc/config-reference/database-service/section-databaseservice-rpc.xml:7(title) ./doc/config-reference/image-service/section_image-service-rpc.xml:6(title)
-msgid "Configure the RPC messaging system"
-msgstr ""
-
-#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:8(para)
-msgid "OpenStack projects use an open standard for messaging middleware known as AMQP. This messaging middleware enables the OpenStack services that run on multiple servers to talk to each other. OpenStack Oslo RPC supports three implementations of AMQP: <application>RabbitMQ</application>, <application>Qpid</application>, and <application>ZeroMQ</application>."
-msgstr ""
-
-#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:17(title) ./doc/config-reference/database-service/section-databaseservice-rpc.xml:17(title)
-msgid "Configure RabbitMQ"
-msgstr ""
-
-#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:19(para)
-msgid "OpenStack Oslo RPC uses <application>RabbitMQ</application> by default. Use these options to configure the <application>RabbitMQ</application> message system. The <option>rpc_backend</option> option is optional as long as <application>RabbitMQ</application> is the default messaging system. However, if it is included in the configuration, you must set it to <literal>heat.openstack.common.rpc.impl_kombu</literal>."
-msgstr ""
-
-#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:31(para)
-msgid "Use these options to configure the <application>RabbitMQ</application> messaging system. You can configure messaging communication for different installation scenarios, tune retries for RabbitMQ, and define the size of the RPC thread pool. To monitor notifications through RabbitMQ, you must set the <option>notification_driver</option> option to <literal>heat.notifier.rabbit_notifier</literal> in the <filename>heat.conf</filename> file:"
-msgstr ""
-
-#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:42(title) ./doc/config-reference/database-service/section-databaseservice-rpc.xml:24(title)
-msgid "Configure Qpid"
-msgstr ""
-
-#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:43(para)
-msgid "Use these options to configure the <application>Qpid</application> messaging system for OpenStack Oslo RPC. <application>Qpid</application> is not the default messaging system, so you must enable it by setting the <option>rpc_backend</option> option in the <filename>heat.conf</filename> file:"
-msgstr ""
-
-#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:50(para)
-msgid "This critical option points the compute nodes to the <application>Qpid</application> broker (server). Set the <option>qpid_hostname</option> option to the host name where the broker runs in the <filename>heat.conf</filename> file."
-msgstr ""
-
-#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:56(para)
-msgid "The <option>qpid_hostname</option> option accepts a host name or IP address value."
-msgstr ""
-
-#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:61(para)
-msgid "If the <application>Qpid</application> broker listens on a port other than the AMQP default of <literal>5672</literal>, you must set the <option>qpid_port</option> option to that value:"
-msgstr ""
-
-#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:68(para)
-msgid "If you configure the <application>Qpid</application> broker to require authentication, you must add a user name and password to the configuration:"
-msgstr ""
-
-#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:74(para)
-msgid "By default, TCP is used as the transport. To enable SSL, set the <option>qpid_protocol</option> option:"
-msgstr ""
-
-#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:79(para)
-msgid "Use these additional options to configure the Qpid messaging driver for OpenStack Oslo RPC. These options are used infrequently."
-msgstr ""
-
-#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:87(title)
-msgid "Configure ZeroMQ"
-msgstr ""
-
-#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:88(para)
-msgid "Use these options to configure the <application>ZeroMQ</application> messaging system for OpenStack Oslo RPC. <application>ZeroMQ</application> is not the default messaging system, so you must enable it by setting the <option>rpc_backend</option> option in the <filename>heat.conf</filename> file:"
-msgstr ""
-
-#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:97(title) ./doc/config-reference/database-service/section-databaseservice-rpc.xml:38(title)
-msgid "Configure messaging"
-msgstr ""
-
-#: ./doc/config-reference/orchestration/section_orchestration-rpc.xml:99(para) ./doc/config-reference/database-service/section-databaseservice-rpc.xml:40(para)
-msgid "Use these common options to configure the <application>RabbitMQ</application>, <application>Qpid</application>, and <application>ZeroMq</application> messaging drivers:"
-msgstr ""
-
-#: ./doc/config-reference/orchestration/section_orchestration-clients.xml:7(title)
-msgid "Configure Clients"
-msgstr ""
-
-#: ./doc/config-reference/orchestration/section_orchestration-clients.xml:8(para)
-msgid "The following options allow configuration of the clients that Orchestration uses to talk to other services."
-msgstr ""
-
-#: ./doc/config-reference/orchestration/section_orchestration-api.xml:7(title)
-msgid "Configure APIs"
-msgstr ""
-
-#: ./doc/config-reference/orchestration/section_orchestration-api.xml:8(para)
-msgid "The following options allow configuration of the APIs that Orchestration supports. Currently this includes compatibility APIs for CloudFormation and CloudWatch and a native API."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_backup-drivers.xml:6(title)
-msgid "Backup drivers"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_backup-drivers.xml:7(para)
-msgid "This section describes how to configure the <systemitem class=\"service\">cinder-backup</systemitem> service and its drivers."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_backup-drivers.xml:10(para)
-msgid "The volume drivers are included with the Block Storage repository (<link href=\"https://github.com/openstack/cinder\">https://github.com/openstack/cinder</link>). To set a backup driver, use the <literal>backup_driver</literal> flag. By default there is no backup driver enabled."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:6(title)
-msgid "Log files used by Block Storage"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:7(para)
-msgid "The corresponding log file of each Block Storage service is stored in the <filename>/var/log/cinder/</filename> directory of the host on which each service runs."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:11(caption)
-msgid "Log files used by Block Storage services"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:20(td)
-msgid "Service/interface (for CentOS, Fedora, openSUSE, Red Hat Enterprise Linux, and SUSE Linux Enterprise)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:24(td)
-msgid "Service/interface (for Ubuntu and Debian)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:35(systemitem)
-msgid "openstack-cinder-api"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:38(systemitem)
-msgid "cinder-api"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:43(filename)
-msgid "cinder-manage.log"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:46(systemitem) ./doc/config-reference/block-storage/section_cinder-log-files.xml:49(systemitem)
-msgid "cinder-manage"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:57(systemitem)
-msgid "openstack-cinder-scheduler"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:60(systemitem)
-msgid "cinder-scheduler"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:65(filename)
-msgid "volume.log"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:68(systemitem)
-msgid "openstack-cinder-volume"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_cinder-log-files.xml:71(systemitem) ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:179(systemitem)
-msgid "cinder-volume"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_fc-zoning.xml:4(title)
-msgid "Fibre Channel Zone Manager"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_fc-zoning.xml:5(para)
-msgid "The Fibre Channel Zone Manager allows FC SAN Zone/Access control management in conjunction with Fibre Channel block storage. The configuration of Fibre Channel Zone Manager and various zone drivers are described in this section."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_fc-zoning.xml:10(title)
-msgid "Configure Block Storage to use Fibre Channel Zone Manager"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_fc-zoning.xml:12(para)
-msgid "If Block Storage is configured to use a Fibre Channel volume driver that supports Zone Manager, update <filename>cinder.conf</filename> to add the following configuration options to enable Fibre Channel Zone Manager."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_fc-zoning.xml:17(para) ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:305(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:375(para)
-msgid "Make the following changes in the <filename>/etc/cinder/cinder.conf</filename> file."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_fc-zoning.xml:21(para)
-msgid "To use different Fibre Channel Zone Drivers, use the parameters described in this section."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_fc-zoning.xml:24(para)
-msgid "When multi backend configuration is used, provide the <option>zoning_mode</option> configuration option as part of the volume driver configuration where <option>volume_driver</option> option is specified."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_fc-zoning.xml:30(para)
-msgid "Default value of <option>zoning_mode</option> is <literal>None</literal> and this needs to be changed to <literal>fabric</literal> to allow fabric zoning."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_fc-zoning.xml:35(para)
-msgid "<option>zoning_policy</option> can be configured as <literal>initiator-target</literal> or <literal>initiator</literal>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_fc-zoning.xml:42(title)
-msgid "Brocade Fibre Channel Zone Driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_fc-zoning.xml:43(para)
-msgid "Brocade Fibre Channel Zone Driver performs zoning operations via SSH. Configure Brocade Zone Driver and lookup service by specifying the following parameters:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_fc-zoning.xml:47(para)
-msgid "Configure SAN fabric parameters in the form of fabric groups as described in the example below:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_fc-zoning.xml:51(para)
-msgid "Define a fabric group for each fabric using the fabric names used in <option>fc_fabric_names</option> configuration option as group name."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_fc-zoning.xml:57(title) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:15(title) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:23(title) ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:16(title) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:42(title) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:16(title)
-msgid "System requirements"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_fc-zoning.xml:58(para)
-msgid "Brocade Fibre Channel Zone Driver requires firmware version FOS v6.4 or higher."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_fc-zoning.xml:60(para)
-msgid "As a best practice for zone management, use a user account with <literal>zoneadmin</literal> role. Users with <literal>admin</literal> role (including the default <literal>admin</literal> user account) are limited to a maximum of two concurrent SSH sessions."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_fc-zoning.xml:66(para)
-msgid "For information about how to manage Brocade Fibre Channel switches, see the Brocade Fabric OS user documentation."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_volume-drivers.xml:6(title)
-msgid "Volume drivers"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_volume-drivers.xml:7(para)
-msgid "To use different volume drivers for the <systemitem class=\"service\">cinder-volume</systemitem> service, use the parameters described in these sections."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_volume-drivers.xml:10(para)
-msgid "The volume drivers are included in the Block Storage repository (<link href=\"https://github.com/openstack/cinder\">https://github.com/openstack/cinder</link>). To set a volume driver, use the <literal>volume_driver</literal> flag. The default is:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_misc.xml:6(title)
-msgid "Additional options"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_misc.xml:8(para)
-msgid "These options can also be set in the <filename>cinder.conf</filename> file."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_block-storage-sample-configuration-files.xml:4(title)
-msgid "Block Storage sample configuration files"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_block-storage-sample-configuration-files.xml:5(para)
-msgid "All the files in this section can be found in <systemitem>/etc/cinder</systemitem>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_block-storage-sample-configuration-files.xml:7(title) ./doc/config-reference/block-storage/drivers/coraid-driver.xml:373(filename)
-msgid "cinder.conf"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_block-storage-sample-configuration-files.xml:8(para)
-msgid "Use the <filename>cinder.conf</filename> file to configure the majority of the Block Storage service options."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_block-storage-sample-configuration-files.xml:16(para)
-msgid "Use the <filename>api-paste.ini</filename> file to configure the Block Storage API service."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_block-storage-sample-configuration-files.xml:23(para)
-msgid "The <filename>policy.json</filename> file defines additional access controls that apply to the Block Storage service."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_block-storage-sample-configuration-files.xml:28(para)
-msgid "The <filename>rootwrap.conf</filename> file defines configuration values used by the <placeholder-1/> script when the Block Storage service must escalate its privileges to those of the root user."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:6(title)
-msgid "Introduction to the Block Storage service"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:7(para)
-msgid "The OpenStack Block Storage service provides persistent block storage resources that OpenStack Compute instances can consume. This includes secondary attached storage similar to the Amazon Elastic Block Storage (EBS) offering. In addition, you can write images to a Block Storage device for Compute to use as a bootable persistent instance."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:11(para)
-msgid "The Block Storage service differs slightly from the Amazon EBS offering. The Block Storage service does not provide a shared storage solution like NFS. With the Block Storage service, you can attach a device to only one instance."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:14(para)
-msgid "The Block Storage service provides:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:17(para)
-msgid "<systemitem class=\"service\">cinder-api</systemitem>. A WSGI app that authenticates and routes requests throughout the Block Storage service. It supports the OpenStack APIs only, although there is a translation that can be done through Compute's EC2 interface, which calls in to the Block Storage client."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:23(para)
-msgid "<systemitem class=\"service\">cinder-scheduler</systemitem>. Schedules and routes requests to the appropriate volume service. Depending upon your configuration, this may be simple round-robin scheduling to the running volume services, or it can be more sophisticated through the use of the Filter Scheduler. The Filter Scheduler is the default and enables filters on things like Capacity, Availability Zone, Volume Types, and Capabilities as well as custom filters."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:31(para)
-msgid "<systemitem class=\"service\">cinder-volume</systemitem>. Manages Block Storage devices, specifically the back-end devices themselves."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:36(para)
-msgid "<systemitem class=\"service\">cinder-backup</systemitem>. Provides a means to back up a Block Storage volume to OpenStack Object Storage (swift)."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:41(para)
-msgid "The Block Storage service contains the following components:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:44(para)
-msgid "<emphasis role=\"bold\">Back-end Storage Devices</emphasis>. The Block Storage service requires some form of back-end storage that the service is built on. The default implementation is to use LVM on a local volume group named \"cinder-volumes.\" In addition to the base driver implementation, the Block Storage service also provides the means to add support for other storage devices to be utilized such as external Raid Arrays or other storage appliances. These back-end storage devices may have custom block sizes when using KVM or QEMU as the hypervisor."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:53(para)
-msgid "<emphasis role=\"bold\">Users and Tenants (Projects)</emphasis>. The Block Storage service can be used by many different cloud computing consumers or customers (tenants on a shared system), using role-based access assignments. Roles control the actions that a user is allowed to perform. In the default configuration, most actions do not require a particular role, but this can be configured by the system administrator in the appropriate <filename>policy.json</filename> file that maintains the rules. A user's access to particular volumes is limited by tenant, but the username and password are assigned per user. Key pairs granting access to a volume are enabled per user, but quotas to control resource consumption across available hardware resources are per tenant."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:63(para)
-msgid "For tenants, quota controls are available to limit:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:67(para)
-msgid "The number of volumes that can be created."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:71(para)
-msgid "The number of snapshots that can be created."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:75(para)
-msgid "The total number of GBs allowed per tenant (shared between snapshots and volumes)."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:79(para)
-msgid "You can revise the default quota values with the Block Storage CLI, so the limits placed by quotas are editable by admin users."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:83(para)
-msgid "<emphasis role=\"bold\">Volumes, Snapshots, and Backups</emphasis>. The basic resources offered by the Block Storage service are volumes and snapshots which are derived from volumes and volume backups:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:88(para)
-msgid "<emphasis role=\"bold\">Volumes</emphasis>. Allocated block storage resources that can be attached to instances as secondary storage or they can be used as the root store to boot instances. Volumes are persistent R/W block storage devices most commonly attached to the compute node through iSCSI."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:97(para)
-msgid "<emphasis role=\"bold\">Snapshots</emphasis>. A read-only point in time copy of a volume. The snapshot can be created from a volume that is currently in use (through the use of <option>--force True</option>) or in an available state. The snapshot can then be used to create a new volume through create from snapshot."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/section_block-storage-overview.xml:104(para)
-msgid "<emphasis role=\"bold\">Backups</emphasis>. An archived copy of a volume currently stored in OpenStack Object Storage (swift)."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:6(title)
-msgid "VMware VMDK driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:8(para)
-msgid "Use the VMware VMDK driver to enable management of the OpenStack Block Storage volumes on vCenter-managed data stores. Volumes are backed by VMDK files on data stores that use any VMware-compatible storage technology such as NFS, iSCSI, FiberChannel, and vSAN."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:14(para)
-msgid "The VMware ESX VMDK driver is deprecated as of the Icehouse release and might be removed in Juno or a subsequent release. The VMware vCenter VMDK driver continues to be fully supported."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:20(title)
-msgid "Functional context"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:21(para)
-msgid "The VMware VMDK driver connects to vCenter, through which it can dynamically access all the data stores visible from the ESX hosts in the managed cluster."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:24(para)
-msgid "When you create a volume, the VMDK driver creates a VMDK file on demand. The VMDK file creation completes only when the volume is subsequently attached to an instance, because the set of data stores visible to the instance determines where to place the volume."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:29(para)
-msgid "The running vSphere VM is automatically reconfigured to attach the VMDK file as an extra disk. Once attached, you can log in to the running vSphere VM to rescan and discover this extra disk."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:35(title) ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:134(title) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:66(title)
-msgid "Configuration"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:36(para)
-msgid "The recommended volume driver for OpenStack Block Storage is the VMware vCenter VMDK driver. When you configure the driver, you must match it with the appropriate OpenStack Compute driver from VMware and both drivers must point to the same server."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:41(para)
-msgid "In the <filename>nova.conf</filename> file, use this option to define the Compute driver:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:44(para)
-msgid "In the <filename>cinder.conf</filename> file, use this option to define the volume driver:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:47(para)
-msgid "The following table lists various options that the drivers support for the OpenStack Block Storage configuration (<filename>cinder.conf</filename>):"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:54(para)
-msgid "The VMware VMDK drivers support the creation of VMDK disk files of type <literal>thin</literal>, <literal>thick</literal>, or <literal>eagerZeroedThick</literal>. Use the <code>vmware:vmdk_type</code> extra spec key with the appropriate value to specify the VMDK disk file type. The following table captures the mapping between the extra spec entry and the VMDK disk file type:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:63(caption)
-msgid "Extra spec entry to VMDK disk file type mapping"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:67(td)
-msgid "Disk file type"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:68(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:114(td)
-msgid "Extra spec key"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:69(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:115(td)
-msgid "Extra spec value"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:75(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:80(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:85(td)
-msgid "vmware:vmdk_type"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:79(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:81(td)
-msgid "thick"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:84(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:86(td)
-msgid "eagerZeroedThick"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:90(para)
-msgid "If you do not specify a <code>vmdk_type</code> extra spec entry, the default disk file type is <literal>thin</literal>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:93(para)
-msgid "The following example shows how to create a <code>thick</code> VMDK volume by using the appropriate <code>vmdk_type</code>:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:101(title) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:113(td)
-msgid "Clone type"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:102(para)
-msgid "With the VMware VMDK drivers, you can create a volume from another source volume or a snapshot point. The VMware vCenter VMDK driver supports the <literal>full</literal> and <literal>linked/fast</literal> clone types. Use the <code>vmware:clone_type</code> extra spec key to specify the clone type. The following table captures the mapping for clone types:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:110(caption)
-msgid "Extra spec entry to clone type mapping"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:120(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:122(td)
-msgid "full"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:121(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:126(td)
-msgid "vmware:clone_type"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:125(td)
-msgid "linked/fast"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:127(td)
-msgid "linked"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:131(para)
-msgid "If you do not specify the clone type, the default is <literal>full</literal>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:133(para)
-msgid "The following example shows linked cloning from another source volume:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:139(para)
-msgid "The VMware ESX VMDK driver ignores the extra spec entry and always creates a <literal>full</literal> clone."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:145(title)
-msgid "Use vCenter storage policies to specify back-end data stores"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:148(para)
-msgid "This section describes how to configure back-end data stores using storage policies. In vCenter, you can create one or more storage policies and expose them as a Block Storage volume-type to a vmdk volume. The storage policies are exposed to the vmdk driver through the extra spec property with the <literal>vmware:storage_profile</literal> key."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:155(para)
-msgid "For example, assume a storage policy in vCenter named <literal>gold_policy.</literal> and a Block Storage volume type named <literal>vol1</literal> with the extra spec key <literal>vmware:storage_profile</literal> set to the value <literal>gold_policy</literal>. Any Block Storage volume creation that uses the <literal>vol1</literal> volume type places the volume only in data stores that match the <literal>gold_policy</literal> storage policy."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:164(para)
-msgid "The Block Storage back-end configuration for vSphere data stores is automatically determined based on the vCenter configuration. If you configure a connection to connect to vCenter version 5.5 or later in the <filename>cinder.conf</filename> file, the use of storage policies to configure back-end data stores is automatically supported."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:172(para)
-msgid "You must configure any data stores that you configure for the Block Storage service for the Compute service."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:177(title)
-msgid "To configure back-end data stores by using storage policies"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:180(para)
-msgid "In vCenter, tag the data stores to be used for the back end."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:182(para)
-msgid "OpenStack also supports policies that are created by using vendor-specific capabilities; for example vSAN-specific storage policies."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:186(para)
-msgid "The tag value serves as the policy. For details, see <xref linkend=\"vmware-spbm\"/>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:192(para)
-msgid "Set the extra spec key <literal>vmware:storage_profile</literal> in the desired Block Storage volume types to the policy name that you created in the previous step."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:199(para)
-msgid "Optionally, for the <parameter>vmware_host_version</parameter> parameter, enter the version number of your vSphere platform. For example, <placeholder-1/>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:204(para)
-msgid "This setting overrides the default location for the corresponding WSDL file. Among other scenarios, you can use this setting to prevent WSDL error messages during the development phase or to work with a newer version of vCenter."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:211(para) ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:117(para) ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:180(para)
-msgid "Complete the other vCenter configuration parameters as appropriate."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:216(para)
-msgid "The following considerations apply to configuring SPBM for the Block Storage service:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:220(para)
-msgid "Any volume that is created without an associated policy (that is to say, without an associated volume type that specifies <literal>vmware:storage_profile</literal> extra spec), there is no policy-based placement for that volume."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:231(title) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:24(title) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:11(title) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:34(title) ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:42(title) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:66(title) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:325(title) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:33(title)
-msgid "Supported operations"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:232(para)
-msgid "The VMware vCenter and ESX VMDK drivers support these operations:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:236(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:28(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:15(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:46(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:72(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:91(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:38(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:36(para)
-msgid "Create volume"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:239(para)
-msgid "Create volume from another source volume. (Supported only if source volume is not attached to an instance.)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:244(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:58(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:33(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:109(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:68(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:54(para)
-msgid "Create volume from snapshot"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:247(para)
-msgid "Create volume from glance image"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:250(para)
-msgid "Attach volume (When a volume is attached to an instance, a reconfigure operation is performed on the instance to add the volume's VMDK to it. The user must manually rescan and mount the device from within the guest operating system.)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:257(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:37(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:24(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:55(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:81(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:100(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:47(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:45(para)
-msgid "Detach volume"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:260(para)
-msgid "Create snapshot (Allowed only if volume is not attached to an instance.)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:264(para)
-msgid "Delete snapshot (Allowed only if volume is not attached to an instance.)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:268(para)
-msgid "Upload as image to glance (Allowed only if volume is not attached to an instance.)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:273(para)
-msgid "Although the VMware ESX VMDK driver supports these operations, it has not been extensively tested."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:279(title)
-msgid "Storage policy-based configuration in vCenter"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:280(para)
-msgid "You can configure Storage Policy-Based Management (SPBM) profiles for vCenter data stores supporting the Compute, Image Service, and Block Storage components of an OpenStack implementation."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:284(para)
-msgid "In a vSphere OpenStack deployment, SPBM enables you to delegate several data stores for storage, which reduces the risk of running out of storage space. The policy logic selects the data store based on accessibility and available storage space."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:291(title) ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:117(title)
-msgid "Prerequisites"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:294(para)
-msgid "Determine the data stores to be used by the SPBM policy."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:298(para)
-msgid "Determine the tag that identifies the data stores in the OpenStack component configuration."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:303(para)
-msgid "Create separate policies or sets of data stores for separate OpenStack components."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:309(title)
-msgid "Create storage policies in vCenter"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:311(title)
-msgid "To create storage policies in vCenter"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:313(para)
-msgid "In vCenter, create the tag that identifies the data stores:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:317(para)
-msgid "From the Home screen, click <guimenuitem>Tags</guimenuitem>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:321(para)
-msgid "Specify a name for the tag."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:324(para)
-msgid "Specify a tag category. For example, <filename>spbm-cinder</filename>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:330(para) ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:132(para)
-msgid "Apply the tag to the data stores to be used by the SPBM policy."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:333(para) ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:142(para)
-msgid "For details about creating tags in vSphere, see the <link href=\"http://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.vsphere.vcenterhost.doc/GUID-379F40D3-8CD6-449E-89CB-79C4E2683221.html\">vSphere documentation</link>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:340(para)
-msgid "In vCenter, create a tag-based storage policy that uses one or more tags to identify a set of data stores."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:344(para)
-msgid "You use this tag name and category when you configure the <filename>*.conf</filename> file for the OpenStack component. For details about creating tags in vSphere, see the <link href=\"http://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.vsphere.storage.doc/GUID-89091D59-D844-46B2-94C2-35A3961D23E7.html\">vSphere documentation</link>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:355(title)
-msgid "Data store selection"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:356(para)
-msgid "If storage policy is enabled, the driver initially selects all the data stores that match the associated storage policy."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:359(para)
-msgid "If two or more data stores match the storage policy, the driver chooses a data store that is connected to the maximum number of hosts."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:362(para)
-msgid "In case of ties, the driver chooses the data store with lowest space utilization, where space utilization is defined by the <literal>(1-freespace/totalspace)</literal> metric."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:367(para)
-msgid "These actions reduce the number of volume migrations while attaching the volume to instances."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:369(para)
-msgid "The volume must be migrated if the ESX host for the instance cannot access the data store that contains the volume."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:4(title)
-msgid "Nexenta drivers"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:5(para)
-msgid "NexentaStor Appliance is NAS/SAN software platform designed for building reliable and fast network storage arrays. The Nexenta Storage Appliance uses ZFS as a disk management system. NexentaStor can serve as a storage node for the OpenStack and its virtual servers through iSCSI and NFS protocols."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:9(para)
-msgid "With the NFS option, every Compute volume is represented by a directory designated to be its own file system in the ZFS file system. These file systems are exported using NFS."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:12(para)
-msgid "With either option some minimal setup is required to tell OpenStack which NexentaStor servers are being used, whether they are supporting iSCSI and/or NFS and how to access each of the servers."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:16(para)
-msgid "Typically the only operation required on the NexentaStor servers is to create the containing directory for the iSCSI or NFS exports. For NFS this containing directory must be explicitly exported via NFS. There is no software that must be installed on the NexentaStor servers; they are controlled using existing management plane interfaces."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:24(title)
-msgid "Nexenta iSCSI driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:25(para)
-msgid "The Nexenta iSCSI driver allows you to use a NexentaStor appliance to store Compute volumes. Every Compute volume is represented by a single zvol in a predefined Nexenta namespace. For every new volume the driver creates a iSCSI target and iSCSI target group that are used to access it from compute hosts."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:29(para)
-msgid "The Nexenta iSCSI volume driver should work with all versions of NexentaStor. The NexentaStor appliance must be installed and configured according to the relevant Nexenta documentation. A pool and an enclosing namespace must be created for all iSCSI volumes to be accessed through the volume driver. This should be done as specified in the release specific NexentaStor documentation."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:36(para)
-msgid "The NexentaStor Appliance iSCSI driver is selected using the normal procedures for one or multiple back-end volume drivers. You must configure these items for each NexentaStor appliance that the iSCSI volume driver controls:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:42(title)
-msgid "Enable the Nexenta iSCSI driver and related options"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:44(para)
-msgid "This table contains the options supported by the Nexenta iSCSI driver."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:48(para)
-msgid "To use Compute with the Nexenta iSCSI driver, first set the <code>volume_driver</code>:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:52(para)
-msgid "Then, set the <code>nexenta_host</code> parameter and other parameters from the table, if needed."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:59(title)
-msgid "Nexenta NFS driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:60(para)
-msgid "The Nexenta NFS driver allows you to use NexentaStor appliance to store Compute volumes via NFS. Every Compute volume is represented by a single NFS file within a shared directory."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:64(para)
-msgid "While the NFS protocols standardize file access for users, they do not standardize administrative actions such as taking snapshots or replicating file systems. The OpenStack Volume Drivers bring a common interface to these operations. The Nexenta NFS driver implements these standard actions using the ZFS management plane that already is deployed on NexentaStor appliances."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:71(para)
-msgid "The Nexenta NFS volume driver should work with all versions of NexentaStor. The NexentaStor appliance must be installed and configured according to the relevant Nexenta documentation. A single-parent file system must be created for all virtual disk directories supported for OpenStack. This directory must be created and exported on each NexentaStor appliance. This should be done as specified in the release specific NexentaStor documentation."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:78(title)
-msgid "Enable the Nexenta NFS driver and related options"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:80(para)
-msgid "To use Compute with the Nexenta NFS driver, first set the <code>volume_driver</code>:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:85(para)
-msgid "The following table contains the options supported by the Nexenta NFS driver."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:89(para)
-msgid "Add your list of Nexenta NFS servers to the file you specified with the <code>nexenta_shares_config</code> option. For example, if the value of this option was set to <filename>/etc/cinder/nfs_shares</filename>, then:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:98(para)
-msgid "Comments are allowed in this file. They begin with a <code>#</code>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nexenta-volume-driver.xml:100(para)
-msgid "Each line in this file represents a NFS share. The first part of the line is the NFS share URL, the second is the connection URL to the NexentaStor Appliance."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/sheepdog-driver.xml:6(title)
-msgid "Sheepdog driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/sheepdog-driver.xml:7(para)
-msgid "Sheepdog is an open-source distributed storage system that provides a virtual storage pool utilizing internal disk of commodity servers."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/sheepdog-driver.xml:10(para)
-msgid "Sheepdog scales to several hundred nodes, and has powerful virtual disk management features like snapshot, cloning, rollback, thin proisioning."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/sheepdog-driver.xml:13(para)
-msgid "More information can be found on <link href=\"http://sheepdog.github.io/sheepdog/\">Sheepdog Project</link>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/sheepdog-driver.xml:15(para)
-msgid "This driver enables use of Sheepdog through Qemu/KVM."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/sheepdog-driver.xml:16(para)
-msgid "Set the following <literal>volume_driver</literal> in <filename>cinder.conf</filename>:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/zadara-volume-driver.xml:6(title)
-msgid "Zadara"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/zadara-volume-driver.xml:7(para)
-msgid "There is a volume back-end for Zadara. Set the following in your <filename>cinder.conf</filename>, and use the following options to configure it."
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:286(None)
-msgid "@@image: '../../../common/figures/coraid/Repository_Creation_Plan_screen.png'; md5=83038804978648c2db4001a46c11f8ba"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:6(title)
-msgid "Coraid AoE driver configuration"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:7(para)
-msgid "Coraid storage appliances can provide block-level storage to OpenStack instances. Coraid storage appliances use the low-latency ATA-over-Ethernet (ATA) protocol to provide high-bandwidth data transfer between hosts and data on the network."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:11(para)
-msgid "Once configured for OpenStack, you can:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:14(para)
-msgid "Create, delete, attach, and detach block storage volumes."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:18(para)
-msgid "Create, list, and delete volume snapshots."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:21(para)
-msgid "Create a volume from a snapshot, copy an image to a volume, copy a volume to an image, clone a volume, and get volume statistics."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:26(para)
-msgid "This document describes how to configure the OpenStack Block Storage service for use with Coraid storage appliances."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:29(title)
-msgid "Terminology"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:30(para)
-msgid "These terms are used in this section:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:34(th)
-msgid "Term"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:35(th)
-msgid "Definition"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:40(td)
-msgid "AoE"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:41(td)
-msgid "ATA-over-Ethernet protocol"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:44(td)
-msgid "EtherCloud Storage Manager (ESM)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:45(td)
-msgid "ESM provides live monitoring and management of EtherDrive appliances that use the AoE protocol, such as the SRX and VSX."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:50(td)
-msgid "Fully-Qualified Repository Name (FQRN)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:53(replaceable)
-msgid "performance_class"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:53(replaceable)
-msgid "availability_class"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:53(replaceable)
-msgid "profile_name"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:53(replaceable)
-msgid "repository_name"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:51(td)
-msgid "The FQRN is the full identifier of a storage profile. FQRN syntax is: <placeholder-1/><placeholder-2/><placeholder-3/><placeholder-4/><placeholder-5/><placeholder-6/><placeholder-7/>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:56(td)
-msgid "SAN"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:57(td)
-msgid "Storage Area Network"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:60(td)
-msgid "SRX"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:61(td)
-msgid "Coraid EtherDrive SRX block storage appliance"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:64(td)
-msgid "VSX"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:65(td)
-msgid "Coraid EtherDrive VSX storage virtualization appliance"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:72(title) ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:14(title)
-msgid "Requirements"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:73(para)
-msgid "To support the OpenStack Block Storage service, your SAN must include an SRX for physical storage, a VSX running at least CorOS v2.0.6 for snapshot support, and an ESM running at least v2.1.1 for storage repository orchestration. Ensure that all storage appliances are installed and connected to your network before you configure OpenStack volumes."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:79(para)
-msgid "In order for the node to communicate with the SAN, you must install the Coraid AoE Linux driver on each Compute node on the network that runs an OpenStack instance."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:84(title)
-msgid "Overview"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:85(para)
-msgid "To configure the OpenStack Block Storage for use with Coraid storage appliances, perform the following procedures:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:89(para)
-msgid "<link linkend=\"coraid_installing_aoe_driver\">Download and install the Coraid Linux AoE driver</link>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:93(para)
-msgid "<link linkend=\"coraid_creating_storage_profile\">Create a storage profile by using the Coraid ESM GUI</link>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:97(para)
-msgid "<link linkend=\"coraid_creating_storage_repository\">Create a storage repository by using the ESM GUI and record the FQRN</link>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:102(para)
-msgid "<link linkend=\"coraid_configuring_cinder.conf\">Configure the <filename>cinder.conf</filename> file</link>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:106(para)
-msgid "<link linkend=\"coraid_creating_associating_volume_type\">Create and associate a block storage volume type</link>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:113(title)
-msgid "Install the Coraid AoE driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:114(para)
-msgid "Install the Coraid AoE driver on every compute node that will require access to block storage."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:116(para)
-msgid "The latest AoE drivers will always be located at <link href=\"http://support.coraid.com/support/linux/\">http://support.coraid.com/support/linux/</link>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:119(para)
-msgid "To download and install the AoE driver, follow the instructions below, replacing “aoeXXX” with the AoE driver file name:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:124(para)
-msgid "Download the latest Coraid AoE driver."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:130(para)
-msgid "Unpack the AoE driver."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:133(para)
-msgid "Install the AoE driver."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:139(para)
-msgid "Initialize the AoE driver."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:145(para)
-msgid "Optionally, specify the Ethernet interfaces that the node can use to communicate with the SAN."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:147(para)
-msgid "The AoE driver may use every Ethernet interface available to the node unless limited with the <literal>aoe_iflist</literal> parameter. For more information about the <literal>aoe_iflist</literal> parameter, see the <filename>aoe readme</filename> file included with the AoE driver."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:154(replaceable)
-msgid "eth1 eth2 ..."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:160(title)
-msgid "Create a storage profile"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:161(para)
-msgid "To create a storage profile using the ESM GUI:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:164(para)
-msgid "Log in to the ESM."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:167(para)
-msgid "Click <guibutton>Storage Profiles</guibutton> in the <guilabel>SAN Domain</guilabel> pane."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:171(para)
-msgid "Choose <guimenuitem>Menu &gt; Create Storage Profile</guimenuitem>. If the option is unavailable, you might not have appropriate permissions. Make sure you are logged in to the ESM as the SAN administrator."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:177(para)
-msgid "Use the storage class selector to select a storage class."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:179(para)
-msgid "Each storage class includes performance and availability criteria (see the Storage Classes topic in the ESM Online Help for information on the different options)."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:184(para)
-msgid "Select a RAID type (if more than one is available) for the selected profile type."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:188(para)
-msgid "Type a <guilabel>Storage Profile</guilabel> name."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:189(para)
-msgid "The name is restricted to alphanumeric characters, underscore (_), and hyphen (-), and cannot exceed 32 characters."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:194(para)
-msgid "Select the drive size from the drop-down menu."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:197(para)
-msgid "Select the number of drives to be initialized for each RAID (LUN) from the drop-down menu (if the selected RAID type requires multiple drives)."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:202(para)
-msgid "Type the number of RAID sets (LUNs) you want to create in the repository by using this profile."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:206(para)
-msgid "Click <guibutton>Next</guibutton>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:211(title)
-msgid "Create a storage repository and get the FQRN"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:212(para)
-msgid "Create a storage repository and get its fully qualified repository name (FQRN):"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:216(para)
-msgid "Access the <guilabel>Create Storage Repository</guilabel> dialog box."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:220(para)
-msgid "Type a Storage Repository name."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:221(para)
-msgid "The name is restricted to alphanumeric characters, underscore (_), hyphen (-), and cannot exceed 32 characters."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:226(para)
-msgid "Click <guibutton>Limited</guibutton> or <guibutton>Unlimited</guibutton> to indicate the maximum repository size."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:229(para)
-msgid "<guibutton>Limited</guibutton> sets the amount of space that can be allocated to the repository. Specify the size in TB, GB, or MB."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:232(para)
-msgid "When the difference between the reserved space and the space already allocated to LUNs is less than is required by a LUN allocation request, the reserved space is increased until the repository limit is reached."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:237(para)
-msgid "The reserved space does not include space used for parity or space used for mirrors. If parity and/or mirrors are required, the actual space allocated to the repository from the SAN is greater than that specified in reserved space."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:243(para)
-msgid "<emphasis role=\"bold\">Unlimited</emphasis>—Unlimited means that the amount of space allocated to the repository is unlimited and additional space is allocated to the repository automatically when space is required and available."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:249(para)
-msgid "Drives specified in the associated Storage Profile must be available on the SAN in order to allocate additional resources."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:255(para)
-msgid "Check the <guibutton>Resizeable LUN</guibutton> box."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:257(para)
-msgid "This is required for OpenStack volumes."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:259(para)
-msgid "If the Storage Profile associated with the repository has platinum availability, the Resizeable LUN box is automatically checked."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:265(para)
-msgid "Check the <guibutton>Show Allocation Plan API calls</guibutton> box. Click <guibutton>Next</guibutton>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:270(para)
-msgid "Record the FQRN and click <guibutton>Finish</guibutton>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:272(para)
-msgid "The FQRN is located in the first line of output following the <literal>Plan</literal> keyword in the <guilabel>Repository Creation Plan</guilabel> window. The FQRN syntax is <replaceable>performance_class</replaceable><placeholder-1/><replaceable>availability_class</replaceable><placeholder-2/><replaceable>profile_name</replaceable><placeholder-3/><replaceable>repository_name</replaceable>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:277(para)
-msgid "In this example, the FQRN is <literal>Bronze-Platinum:BP1000:OSTest</literal>, and is highlighted."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:281(title)
-msgid "Repository Creation Plan screen"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:290(para)
-msgid "Record the FQRN; it is a required parameter later in the configuration procedure."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:296(title)
-msgid "Configure options in the cinder.conf file"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:297(para)
-msgid "Edit or add the following lines to the file<filename> /etc/cinder/cinder.conf</filename>:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:300(replaceable)
-msgid "ESM_IP_address"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:301(replaceable) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:355(option) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:59(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:123(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:342(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:398(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:458(replaceable)
-msgid "username"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:302(replaceable)
-msgid "Access_Control_Group_name"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:303(replaceable) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:365(option) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:60(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:124(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:343(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:399(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:459(replaceable) ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:58(replaceable)
-msgid "password"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:304(replaceable) ./doc/config-reference/block-storage/drivers/coraid-driver.xml:352(replaceable) ./doc/config-reference/block-storage/drivers/coraid-driver.xml:370(replaceable)
-msgid "coraid_repository_key"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:306(para)
-msgid "Access to storage devices and storage repositories can be controlled using Access Control Groups configured in ESM. Configuring <filename>cinder.conf</filename> to log on to ESM as the SAN administrator (user name <literal>admin</literal>), will grant full access to the devices and repositories configured in ESM."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:312(para)
-msgid "Optionally, you can configure an ESM Access Control Group and user. Then, use the <filename>cinder.conf</filename> file to configure access to the ESM through that group, and user limits access from the OpenStack instance to devices and storage repositories that are defined in the group."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:317(para)
-msgid "To manage access to the SAN by using Access Control Groups, you must enable the Use Access Control setting in the <emphasis role=\"bold\">ESM System Setup</emphasis> &gt;<emphasis role=\"bold\"> Security</emphasis> screen."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:321(para)
-msgid "For more information, see the ESM Online Help."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:324(title)
-msgid "Create and associate a volume type"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:325(para)
-msgid "Create and associate a volume with the ESM storage repository."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:329(para)
-msgid "Restart Cinder."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:335(para)
-msgid "Create a volume."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:336(replaceable)
-msgid "volume_type_name"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:337(para)
-msgid "where <replaceable>volume_type_name</replaceable> is the name you assign the volume. You will see output similar to the following:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:345(para)
-msgid "Record the value in the ID field; you use this value in the next step."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:349(para)
-msgid "Associate the volume type with the Storage Repository."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:352(replaceable) ./doc/config-reference/block-storage/drivers/coraid-driver.xml:363(replaceable)
-msgid "UUID"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:352(replaceable) ./doc/config-reference/block-storage/drivers/coraid-driver.xml:378(replaceable)
-msgid "FQRN"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:357(th)
-msgid "Variable"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:364(td)
-msgid "The ID returned from the <placeholder-1/> command. You can use the <placeholder-2/> command to recover the ID."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:375(literal)
-msgid "coraid_repository"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:371(td)
-msgid "The key name used to associate the Cinder volume type with the ESM in the <placeholder-1/> file. If no key name was defined, this is default value for <placeholder-2/>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:379(td)
-msgid "The FQRN recorded during the Create Storage Repository process."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/solidfire-volume-driver.xml:5(title)
-msgid "SolidFire"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/solidfire-volume-driver.xml:6(para)
-msgid "The SolidFire Cluster is a high performance all SSD iSCSI storage device that provides massive scale out capability and extreme fault tolerance. A key feature of the SolidFire cluster is the ability to set and modify during operation specific QoS levels on a volume for volume basis. The SolidFire cluster offers this along with de-duplication, compression, and an architecture that takes full advantage of SSDs."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/solidfire-volume-driver.xml:14(para)
-msgid "To configure the use of a SolidFire cluster with Block Storage, modify your <filename>cinder.conf</filename> file as follows:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/solidfire-volume-driver.xml:23(para)
-msgid "The SolidFire driver creates a unique account prefixed with <literal>$cinder-volume-service-hostname-$tenant-id</literal> on the SolidFire cluster for each tenant that accesses the cluster through the Volume API. Unfortunately, this account formation results in issues for High Availability (HA) installations and installations where the <systemitem class=\"service\">cinder-volume</systemitem> service can move to a new node. HA installations can return an <errortext>Account Not Found</errortext> error because the call to the SolidFire cluster is not always going to be sent from the same node. In installations where the <systemitem class=\"service\">cinder-volume</systemitem> service moves to a new node, the same issue can occur when you perform operations on existing volumes, such as clone, extend, delete, and so on."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/solidfire-volume-driver.xml:41(para)
-msgid "Set the <option>sf_account_prefix</option> option to an empty string ('') in the <filename>cinder.conf</filename> file. This setting results in unique accounts being created on the SolidFire cluster, but the accounts are prefixed with the <systemitem>tenant-id</systemitem> or any unique identifier that you choose and are independent of the host where the <systemitem class=\"service\">cinder-volume</systemitem> service resides."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:4(title)
-msgid "XenAPI Storage Manager volume driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:5(para)
-msgid "The Xen Storage Manager volume driver (xensm) is a XenAPI hypervisor specific volume driver, and can be used to provide basic storage functionality, including volume creation and destruction, on a number of different storage back-ends. It also enables the capability of using more sophisticated storage back-ends for operations like cloning/snapshots, and so on. Some of the storage plug-ins that are already supported in Citrix XenServer and Xen Cloud Platform (XCP) are:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:15(para)
-msgid "NFS VHD: Storage repository (SR) plug-in that stores disks as Virtual Hard Disk (VHD) files on a remote Network File System (NFS)."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:20(para)
-msgid "Local VHD on LVM: SR plug-in that represents disks as VHD disks on Logical Volumes (LVM) within a locally-attached Volume Group."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:25(para)
-msgid "HBA LUN-per-VDI driver: SR plug-in that represents Logical Units (LUs) as Virtual Disk Images (VDIs) sourced by host bus adapters (HBAs). For example, hardware-based iSCSI or FC support."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:31(para)
-msgid "NetApp: SR driver for mapping of LUNs to VDIs on a NETAPP server, providing use of fast snapshot and clone features on the filer."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:36(para)
-msgid "LVHD over FC: SR plug-in that represents disks as VHDs on Logical Volumes within a Volume Group created on an HBA LUN. For example, hardware-based iSCSI or FC support."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:42(para)
-msgid "iSCSI: Base ISCSI SR driver, provides a LUN-per-VDI. Does not support creation of VDIs but accesses existing LUNs on a target."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:47(para)
-msgid "LVHD over iSCSI: SR plug-in that represents disks as Logical Volumes within a Volume Group created on an iSCSI LUN."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:52(para)
-msgid "EqualLogic: SR driver for mapping of LUNs to VDIs on a EQUALLOGIC array group, providing use of fast snapshot and clone features on the array."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:58(title)
-msgid "Design and operation"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:60(title)
-msgid "Definitions"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:63(para)
-msgid "<emphasis role=\"bold\">Back-end:</emphasis> A term for a particular storage back-end. This could be iSCSI, NFS, NetApp, and so on."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:68(para)
-msgid "<emphasis role=\"bold\">Back-end-config:</emphasis> All the parameters required to connect to a specific back-end. For example, for NFS, this would be the server, path, and so on."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:75(para)
-msgid "<emphasis role=\"bold\">Flavor:</emphasis> This term is equivalent to volume \"types\". A user friendly term to specify some notion of quality of service. For example, \"gold\" might mean that the volumes use a back-end where backups are possible. A flavor can be associated with multiple back-ends. The volume scheduler, with the help of the driver, decides which back-end is used to create a volume of a particular flavor. Currently, the driver uses a simple \"first-fit\" policy, where the first back-end that can successfully create this volume is the one that is used."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:93(title)
-msgid "Operation"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:94(para)
-msgid "The admin uses the nova-manage command detailed below to add flavors and back-ends."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:96(para)
-msgid "One or more <systemitem class=\"service\">cinder-volume</systemitem> service instances are deployed for each availability zone. When an instance is started, it creates storage repositories (SRs) to connect to the back-ends available within that zone. All <systemitem class=\"service\">cinder-volume</systemitem> instances within a zone can see all the available back-ends. These instances are completely symmetric and hence should be able to service any <literal>create_volume</literal> request within the zone."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:108(title)
-msgid "On XenServer, PV guests required"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:109(para)
-msgid "Note that when using XenServer you can only attach a volume to a PV guest."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:115(title)
-msgid "Configure XenAPI Storage Manager"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:120(para)
-msgid "xensm requires that you use either Citrix XenServer or XCP as the hypervisor. The NetApp and EqualLogic back-ends are not supported on XCP."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:126(para)
-msgid "Ensure all <emphasis role=\"bold\">hosts</emphasis> running volume and Compute services have connectivity to the storage system."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:138(emphasis)
-msgid "Set the following configuration options for the nova volume service: (<placeholder-1/> also requires the volume_driver configuration option.)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:152(emphasis)
-msgid "You must create the back-end configurations that the volume driver uses before you start the volume service."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:161(para)
-msgid "SR type and configuration connection parameters are in keeping with the <link href=\"http://support.citrix.com/article/CTX124887\">XenAPI Command Line Interface</link>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:168(para)
-msgid "Example: For the NFS storage manager plug-in, run these commands:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:177(emphasis)
-msgid "Start <placeholder-1/> and <placeholder-2/> with the new configuration options."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:188(title)
-msgid "Create and access the volumes from VMs"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:189(para)
-msgid "Currently, the flavors have not been tied to the volume types API. As a result, we simply end up creating volumes in a \"first fit\" order on the given back-ends."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:193(para)
-msgid "Use the standard <placeholder-1/> or OpenStack API commands (such as volume extensions) to create, destroy, attach, or detach volumes."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:9(title)
-msgid "HDS HUS iSCSI driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:10(para)
-msgid "This Block Storage volume driver provides iSCSI support for <link href=\"http://www.hds.com/products/storage-systems/hitachi-unified-storage-100-family.html\">HUS (Hitachi Unified Storage) </link> arrays such as, HUS-110, HUS-130, and HUS-150."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:16(para)
-msgid "Use the HDS <placeholder-1/> command to communicate with an HUS array. You can download this utility package from the HDS support site (<link href=\"https://HDSSupport.hds.com\">https://HDSSupport.hds.com</link>)."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:21(para)
-msgid "Platform: Ubuntu 12.04LTS or newer."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:25(para)
-msgid "These operations are supported:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:31(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:18(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:49(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:75(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:94(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:41(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:39(para)
-msgid "Delete volume"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:34(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:21(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:52(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:78(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:97(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:44(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:42(para)
-msgid "Attach volume"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:40(para)
-msgid "Clone volume"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:43(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:71(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:66(para)
-msgid "Extend volume"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:46(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:27(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:58(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:103(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:50(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:48(para)
-msgid "Create snapshot"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:49(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:30(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:61(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:106(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:53(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:51(para)
-msgid "Delete snapshot"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:52(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:39(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:64(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:84(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:115(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:59(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:60(para)
-msgid "Copy image to volume"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:55(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:42(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:67(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:87(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:118(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:62(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:63(para)
-msgid "Copy volume to image"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:61(para)
-msgid "Get statistics"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:71(para)
-msgid "Do not confuse differentiated services with the OpenStack Block Storage volume services."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:67(para)
-msgid "The HDS driver supports the concept of differentiated services, where a volume type can be associated with the fine-tuned performance characteristics of an HDP the dynamic pool where volumes are created. For instance, an HDP can consist of fast SSDs to provide speed. HDP can provide a certain reliability based on things like its RAID level characteristics. HDS driver maps volume type to the volume_type option in its configuration file."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:79(para)
-msgid "Configuration is read from an XML-format file. Examples are shown for single and multi back-end cases."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:84(para)
-msgid "Configuration is read from an XML file. This example shows the configuration for single back-end and for multi-back-end cases."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:93(para)
-msgid "It is okay to manage multiple HUS arrays by using multiple OpenStack Block Storage instances (or servers)."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:89(para)
-msgid "It is not recommended to manage an HUS array simultaneously from multiple OpenStack Block Storage instances or servers. <placeholder-1/>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:102(title)
-msgid "HUS setup"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:103(para)
-msgid "Before using iSCSI services, use the HUS UI to create an iSCSI domain for each EVS providing iSCSI services."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:107(title)
-msgid "Single back-end"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:108(para)
-msgid "In a single back-end deployment, only one OpenStack Block Storage instance runs on the OpenStack Block Storage server and controls one HUS array: this deployment requires these configuration files:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:121(para)
-msgid "The configuration file location may differ."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:114(para)
-msgid "Set the <option>hds_cinder_config_file</option> option in the <filename>/etc/cinder/cinder.conf</filename> file to use the HDS volume driver. This option points to a configuration file.<placeholder-1/>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:128(para)
-msgid "Configure <option>hds_cinder_config_file</option> at the location specified previously. For example, <filename>/opt/hds/hus/cinder_hds_conf.xml</filename>:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:159(title)
-msgid "Multi back-end"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:160(para)
-msgid "In a multi back-end deployment, more than one OpenStack Block Storage instance runs on the same server. In this example, two HUS arrays are used, possibly providing different storage performance:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:166(para)
-msgid "Configure <filename>/etc/cinder/cinder.conf</filename>: the <literal>hus1</literal><option>hus2</option> configuration blocks are created. Set the <option>hds_cinder_config_file</option> option to point to a unique configuration file for each block. Set the <option>volume_driver</option> option for each back-end to <literal>cinder.volume.drivers.hds.hds.HUSDriver</literal>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:190(para)
-msgid "Configure <filename>/opt/hds/hus/cinder_hus1_conf.xml</filename>:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:216(para)
-msgid "Configure the <filename>/opt/hds/hus/cinder_hus2_conf.xml</filename> file:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:245(title)
-msgid "Type extra specs: <option>volume_backend</option> and volume type"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:247(para)
-msgid "If you use volume types, you must configure them in the configuration file and set the <option>volume_backend_name</option> option to the appropriate back-end. In the previous multi back-end example, the <literal>platinum</literal> volume type is served by hus-2, and the <literal>regular</literal> volume type is served by hus-1."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:258(title)
-msgid "Non differentiated deployment of HUS arrays"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:259(para)
-msgid "You can deploy multiple OpenStack Block Storage instances that each control a separate HUS array. Each instance has no volume type associated with it. The OpenStack Block Storage filtering algorithm selects the HUS array with the largest available free space. In each configuration file, you must define the <literal>default</literal><option>volume_type</option> in the service labels."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:270(title)
-msgid "HDS iSCSI volume driver configuration options"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:277(para)
-msgid "There is no relative precedence or weight among these four labels."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:271(para)
-msgid "These details apply to the XML format configuration file that is read by HDS volume driver. These differentiated service labels are predefined: <literal>svc_0</literal>, <literal>svc_1</literal>, <literal>svc_2</literal>, and <literal>svc_3</literal><placeholder-1/>. Each respective service label associates with these parameters and tags:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:283(para)
-msgid "<option>volume-types</option>: A create_volume call with a certain volume type shall be matched up with this tag. <literal>default</literal> is special in that any service associated with this type is used to create volume when no other labels match. Other labels are case sensitive and should exactly match. If no configured volume_types match the incoming requested type, an error occurs in volume creation."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:294(para)
-msgid "<option>HDP</option>, the pool ID associated with the service."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:298(para)
-msgid "An iSCSI port dedicated to the service."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:307(para)
-msgid "The get_volume_stats() always provides the available capacity based on the combined sum of all the HDPs that are used in these services labels."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:301(para)
-msgid "Typically a OpenStack Block Storage volume instance has only one such service label. For example, any <literal>svc_0</literal>, <literal>svc_1</literal>, <literal>svc_2</literal>, or <literal>svc_3</literal> can be associated with it. But any mix of these service labels can be used in the same instance <placeholder-1/>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:312(caption) ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:86(title)
-msgid "Configuration options"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:320(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:307(th) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:204(th)
-msgid "Type"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:321(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:308(th) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:205(th)
-msgid "Default"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:327(option)
-msgid "mgmt_ip0"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:329(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:337(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:394(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:406(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:423(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:434(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:318(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:332(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:343(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:355(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:367(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:379(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:394(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:499(td) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:213(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:228(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:266(para)
-msgid "Required"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:331(para)
-msgid "Management Port 0 IP address"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:335(option)
-msgid "mgmt_ip1"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:339(para)
-msgid "Management Port 1 IP address"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:343(option)
-msgid "hus_cmd"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:345(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:357(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:367(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:379(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:445(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:456(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:408(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:425(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:443(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:461(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:474(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:489(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:511(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:522(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:532(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:543(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:551(td) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:221(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:275(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:299(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:310(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:334(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:345(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:366(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:384(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:394(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:415(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:426(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:436(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:452(para)
-msgid "Optional"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:348(para)
-msgid "<option>hus_cmd</option> is the command used to communicate with the HUS array. If it is not set, the default value is <placeholder-1/>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:360(para)
-msgid "Username is required only if secure mode is used"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:370(para)
-msgid "Password is required only if secure mode is used"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:376(option)
-msgid "svc_0, svc_1, svc_2, svc_3"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:380(para)
-msgid "(at least one label has to be defined)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:383(para)
-msgid "Service labels: these four predefined names help four different sets of configuration options -- each can specify iSCSI port address, HDP and a unique volume type."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:392(option)
-msgid "snapshot"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:397(para)
-msgid "A service label which helps specify configuration for snapshots, such as, HDP."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:404(option)
-msgid "volume_type"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:409(para)
-msgid "<option>volume_type</option> tag is used to match volume type. <literal>Default</literal> meets any type of <option>volume_type</option>, or if it is not specified. Any other volume_type is selected if exactly matched during <literal>create_volume</literal>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:421(option)
-msgid "iscsi_ip"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:426(para)
-msgid "iSCSI port IP address where volume attaches for this volume type."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:432(option)
-msgid "hdp"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:437(para)
-msgid "HDP, the pool number where volume, or snapshot should be created."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:443(option)
-msgid "lun_start"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:446(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:491(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:385(para)
-msgid "0"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:448(para)
-msgid "LUN allocation starts at this number."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:454(option)
-msgid "lun_end"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:457(para)
-msgid "4096"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:459(para)
-msgid "LUN allocation is up to, but not including, this number."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-xiv-volume-driver.xml:5(title)
-msgid "IBM XIV/DS8K volume driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-xiv-volume-driver.xml:6(para)
-msgid "There is a unified volume back-end for IBM XIV and DS8K storage. Set the following in your <filename>cinder.conf</filename>, and use the following options to configure it."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:5(title)
-msgid "NetApp unified driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:6(para)
-msgid "The NetApp unified driver is a block storage driver that supports multiple storage families and protocols. A storage family corresponds to storage systems built on different NetApp technologies such as clustered Data ONTAP, Data ONTAP operating in 7-Mode, and E-Series. The storage protocol refers to the protocol used to initiate data storage and access operations on those storage systems like iSCSI and NFS. The NetApp unified driver can be configured to provision and manage OpenStack volumes on a given storage family using a specified storage protocol. The OpenStack volumes can then be used for accessing and storing data using the storage protocol on the storage family system. The NetApp unified driver is an extensible interface that can support new storage families and protocols."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:21(title)
-msgid "NetApp clustered Data ONTAP storage family"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:22(para)
-msgid "The NetApp clustered Data ONTAP storage family represents a configuration group which provides OpenStack compute instances access to clustered Data ONTAP storage systems. At present it can be configured in OpenStack Block Storage to work with iSCSI and NFS storage protocols."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:28(title)
-msgid "NetApp iSCSI configuration for clustered Data ONTAP"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:30(para)
-msgid "The NetApp iSCSI configuration for clustered Data ONTAP is an interface from OpenStack to clustered Data ONTAP storage systems for provisioning and managing the SAN block storage entity; that is, a NetApp LUN which can be accessed using the iSCSI protocol."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:35(para)
-msgid "The iSCSI configuration for clustered Data ONTAP is a direct interface from OpenStack Block Storage to the clustered Data ONTAP instance and as such does not require additional management software to achieve the desired functionality. It uses NetApp APIs to interact with the clustered Data ONTAP instance."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:42(title)
-msgid "Configuration options for clustered Data ONTAP family with iSCSI protocol"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:44(para)
-msgid "Configure the volume driver, storage family and storage protocol to the NetApp unified driver, clustered Data ONTAP, and iSCSI respectively by setting the <option>volume_driver</option>, <option>netapp_storage_family</option> and <option>netapp_storage_protocol</option> options in <filename>cinder.conf</filename> as follows:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:56(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:120(replaceable)
-msgid "openstack-vserver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:57(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:121(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:340(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:396(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:456(replaceable)
-msgid "myhostname"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:63(para) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:346(para) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:471(para)
-msgid "You must override the default value of <option>netapp_storage_protocol</option> with <literal>iscsi</literal> in order to utilize the iSCSI protocol."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:71(para) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:137(para)
-msgid "If you specify an account in the <option>netapp_login</option> that only has virtual storage server (Vserver) administration privileges (rather than cluster-wide administration privileges), some advanced features of the NetApp unified driver will not work and you may see warnings in the OpenStack Block Storage logs."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:81(para) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:256(para)
-msgid "For more information on these options and other deployment and operational scenarios, visit the <link href=\"https://communities.netapp.com/groups/openstack\"> OpenStack NetApp community</link>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:91(title)
-msgid "NetApp NFS configuration for clustered Data ONTAP"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:93(para)
-msgid "The NetApp NFS configuration for clustered Data ONTAP is an interface from OpenStack to a clustered Data ONTAP system for provisioning and managing OpenStack volumes on NFS exports provided by the clustered Data ONTAP system that are accessed using the NFS protocol."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:99(para)
-msgid "The NFS configuration for clustered Data ONTAP is a direct interface from OpenStack Block Storage to the clustered Data ONTAP instance and as such does not require any additional management software to achieve the desired functionality. It uses NetApp APIs to interact with the clustered Data ONTAP instance."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:106(title)
-msgid "Configuration options for the clustered Data ONTAP family with NFS protocol"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:108(para)
-msgid "Configure the volume driver, storage family and storage protocol to NetApp unified driver, clustered Data ONTAP, and NFS respectively by setting the <option>volume_driver</option>, <option>netapp_storage_family</option> and <option>netapp_storage_protocol</option> options in <filename>cinder.conf</filename> as follows:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:125(replaceable) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:400(replaceable)
-msgid "/etc/cinder/nfs_shares"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:130(para) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:405(para)
-msgid "Additional NetApp NFS configuration options are shared with the generic NFS driver. These options can be found here: <xref linkend=\"config_table_cinder_storage_nfs\"/>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:148(title)
-msgid "NetApp NFS Copy Offload client"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:149(para)
-msgid "A feature was added in the Icehouse release of the NetApp unified driver that enables Image Service images to be efficiently copied to a destination Block Storage volume. When the Block Storage and Image Service are configured to use the NetApp NFS Copy Offload client, a controller-side copy will be attempted before reverting to downloading the image from the Image Service. This improves image provisioning times while reducing the consumption of bandwidth and CPU cycles on the host(s) running the Image and Block Storage services. This is due to the copy operation being performed completely within the storage cluster."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:158(para)
-msgid "The NetApp NFS Copy Offload client can be used in either of the following scenarios:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:162(para)
-msgid "The Image Service is configured to store images in an NFS share that is exported from a NetApp FlexVol volume <emphasis>and</emphasis> the destination for the new Block Storage volume will be on an NFS share exported from a different FlexVol volume than the one used by the Image Service. Both FlexVols must be located within the same cluster."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:169(para)
-msgid "The source image from the Image Service has already been cached in an NFS image cache within a Block Storage backend. The cached image resides on a different FlexVol volume than the destination for the new Block Storage volume. Both FlexVols must be located within the same cluster."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:175(para)
-msgid "To use this feature, you must configure the Image Service, as follows:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:179(para)
-msgid "Set the <option>default_store</option> configuration option to <literal>file</literal>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:184(para)
-msgid "Set the <option>filesystem_store_datadir</option> configuration option to the path to the Image Service NFS export."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:189(para)
-msgid "Set the <option>show_image_direct_url</option> configuration option to <literal>True</literal>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:194(para)
-msgid "Set the <option>show_multiple_locations</option> configuration option to <literal>True</literal>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:199(para)
-msgid "Set the <option>filesystem_store_metadata_file</option> configuration option to a metadata file. The metadata file should contain a JSON object that contains the correct information about the NFS export used by the Image Service, similar to:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:207(replaceable)
-msgid "nfs://192.168.0.1/myGlanceExport"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:208(replaceable)
-msgid "/var/lib/glance/images"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:213(para)
-msgid "To use this feature, you must configure the Block Storage service, as follows:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:217(para)
-msgid "Set the <option>netapp_copyoffload_tool_path</option> configuration option to the path to the NetApp Copy Offload binary."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:222(para)
-msgid "Set the <option>glance_api_version</option> configuration option to <literal>2</literal>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:228(para)
-msgid "This feature requires that:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:231(para)
-msgid "The storage system must have Data ONTAP v8.2 or greater installed."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:235(para)
-msgid "The vStorage feature must be enabled on each storage virtual machine (SVM, also known as a Vserver) that is permitted to interact with the copy offload client."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:242(para)
-msgid "To configure the copy offload workflow, enable NFS v4.0 or greater and export it from the SVM."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:249(para)
-msgid "To download the NetApp copy offload binary to be utilized in conjunction with the <option>netapp_copyoffload_tool_path</option> configuration option, please visit the download page at the <link href=\"https://communities.netapp.com/docs/DOC-33412\">NetApp OpenStack Community site</link>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:264(title)
-msgid "NetApp-supported extra specs for clustered Data ONTAP"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:266(para)
-msgid "Extra specs enable vendors to specify extra filter criteria that the Block Storage scheduler uses when it determines which volume node should fulfill a volume provisioning request. When you use the NetApp unified driver with a clustered Data ONTAP storage system, you can leverage extra specs with OpenStack Block Storage volume types to ensure that OpenStack Block Storage volumes are created on storage back ends that have certain properties. For example, when you configure QoS, mirroring, or compression for a storage back end."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:276(para)
-msgid "Extra specs are associated with OpenStack Block Storage volume types, so that when users request volumes of a particular volume type, the volumes are created on storage back ends that meet the list of requirements. For example, the back ends have the available space or extra specs. You can use the specs in the following table when you define OpenStack Block Storage volume types by using the <placeholder-1/> command."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:287(para)
-msgid "It is recommended to only set the value of extra specs to <literal>True</literal> when combining multiple specs to enforce a certain logic set. If you desire to remove volumes with a certain feature enabled from consideration from the OpenStack Block Storage volume scheduler, be sure to use the negated spec name with a value of <literal>True</literal> rather than setting the positive spec to a value of <literal>False</literal>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:300(title)
-msgid "NetApp Data ONTAP operating in 7-Mode storage family"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:302(para)
-msgid "The NetApp Data ONTAP operating in 7-Mode storage family represents a configuration group which provides OpenStack compute instances access to 7-Mode storage systems. At present it can be configured in OpenStack Block Storage to work with iSCSI and NFS storage protocols."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:308(title)
-msgid "NetApp iSCSI configuration for Data ONTAP operating in 7-Mode"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:310(para)
-msgid "The NetApp iSCSI configuration for Data ONTAP operating in 7-Mode is an interface from OpenStack to Data ONTAP operating in 7-Mode storage systems for provisioning and managing the SAN block storage entity, that is, a LUN which can be accessed using iSCSI protocol."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:316(para)
-msgid "The iSCSI configuration for Data ONTAP operating in 7-Mode is a direct interface from OpenStack to Data ONTAP operating in 7-Mode storage system and it does not require additional management software to achieve the desired functionality. It uses NetApp ONTAPI to interact with the Data ONTAP operating in 7-Mode storage system."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:324(title)
-msgid "Configuration options for the Data ONTAP operating in 7-Mode storage family with iSCSI protocol"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:327(para)
-msgid "Configure the volume driver, storage family and storage protocol to the NetApp unified driver, Data ONTAP operating in 7-Mode, and iSCSI respectively by setting the <option>volume_driver</option>, <option>netapp_storage_family</option> and <option>netapp_storage_protocol</option> options in <filename>cinder.conf</filename> as follows:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:354(para) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:412(para)
-msgid "For more information on these options and other deployment and operational scenarios, visit the <link href=\"https://communities.netapp.com/groups/openstack\">OpenStack NetApp community</link>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:363(title)
-msgid "NetApp NFS configuration for Data ONTAP operating in 7-Mode"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:365(para)
-msgid "The NetApp NFS configuration for Data ONTAP operating in 7-Mode is an interface from OpenStack to Data ONTAP operating in 7-Mode storage system for provisioning and managing OpenStack volumes on NFS exports provided by the Data ONTAP operating in 7-Mode storage system which can then be accessed using NFS protocol."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:372(para)
-msgid "The NFS configuration for Data ONTAP operating in 7-Mode is a direct interface from OpenStack Block Storage to the Data ONTAP operating in 7-Mode instance and as such does not require any additional management software to achieve the desired functionality. It uses NetApp ONTAPI to interact with the Data ONTAP operating in 7-Mode storage system."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:380(title)
-msgid "Configuration options for the Data ONTAP operating in 7-Mode family with NFS protocol"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:383(para)
-msgid "Configure the volume driver, storage family and storage protocol to the NetApp unified driver, Data ONTAP operating in 7-Mode, and NFS respectively by setting the <option>volume_driver</option>, <option>netapp_storage_family</option> and <option>netapp_storage_protocol</option> options in <filename>cinder.conf</filename> as follows:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:422(title)
-msgid "NetApp E-Series storage family"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:423(para)
-msgid "The NetApp E-Series storage family represents a configuration group which provides OpenStack compute instances access to E-Series storage systems. At present it can be configured in OpenStack Block Storage to work with the iSCSI storage protocol."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:429(title)
-msgid "NetApp iSCSI configuration for E-Series"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:430(para)
-msgid "The NetApp iSCSI configuration for E-Series is an interface from OpenStack to E-Series storage systems for provisioning and managing the SAN block storage entity; that is, a NetApp LUN which can be accessed using the iSCSI protocol."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:435(para)
-msgid "The iSCSI configuration for E-Series is an interface from OpenStack Block Storage to the E-Series proxy instance and as such requires the deployment of the proxy instance in order to achieve the desired functionality. The driver uses REST APIs to interact with the E-Series proxy instance, which in turn interacts directly with the E-Series controllers."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:442(title)
-msgid "Configuration options for E-Series storage family with iSCSI protocol"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:444(para)
-msgid "Configure the volume driver, storage family and storage protocol to the NetApp unified driver, E-Series, and iSCSI respectively by setting the <option>volume_driver</option>, <option>netapp_storage_family</option> and <option>netapp_storage_protocol</option> options in <filename>cinder.conf</filename> as follows:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:460(replaceable)
-msgid "1.2.3.4,5.6.7.8"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:461(replaceable)
-msgid "arrayPassword"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:462(replaceable)
-msgid "pool1,pool2"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:465(para)
-msgid "You must override the default value of <option>netapp_storage_family</option> with <literal>eseries</literal> in order to utilize the E-Series driver."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:479(para)
-msgid "For more information on these options and other deployment and operational scenarios, visit the <link href=\"https://communities.netapp.com/groups/openstack\"> OpenStack NetApp community.</link>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:490(title)
-msgid "Upgrading prior NetApp drivers to the NetApp unified driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:492(para)
-msgid "NetApp introduced a new unified block storage driver in Havana for configuring different storage families and storage protocols. This requires defining upgrade path for NetApp drivers which existed in releases prior to Havana. This section covers the upgrade configuration for NetApp drivers to the new unified configuration and a list of deprecated NetApp drivers."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:500(title)
-msgid "Upgraded NetApp drivers"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:501(para)
-msgid "This section describes how to update OpenStack Block Storage configuration from a pre-Havana release to the new unified driver format."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:505(title)
-msgid "Driver upgrade configuration"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:508(para)
-msgid "NetApp iSCSI direct driver for Clustered Data ONTAP in Grizzly (or earlier)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:513(para) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:527(para) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:542(para) ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:557(para)
-msgid "NetApp Unified Driver configuration"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:522(para)
-msgid "NetApp NFS direct driver for Clustered Data ONTAP in Grizzly (or earlier)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:536(para)
-msgid "NetApp iSCSI direct driver for Data ONTAP operating in 7-Mode storage controller in Grizzly (or earlier)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:551(para)
-msgid "NetApp NFS direct driver for Data ONTAP operating in 7-Mode storage controller in Grizzly (or earlier)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:570(title)
-msgid "Deprecated NetApp drivers"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:571(para)
-msgid "This section lists the NetApp drivers in previous releases that are deprecated in Havana."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:575(para)
-msgid "NetApp iSCSI driver for clustered Data ONTAP."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:582(para)
-msgid "NetApp NFS driver for clustered Data ONTAP."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:589(para)
-msgid "NetApp iSCSI driver for Data ONTAP operating in 7-Mode storage controller."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:596(para)
-msgid "NetApp NFS driver for Data ONTAP operating in 7-Mode storage controller."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/netapp-volume-driver.xml:604(para)
-msgid "See the <link href=\"https://communities.netapp.com/groups/openstack\">OpenStack NetApp community</link> for support information on deprecated NetApp drivers in the Havana release."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:6(title)
-msgid "Huawei storage driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:7(para)
-msgid "The Huawei driver supports the iSCSI and Fibre Channel connections and enables OceanStor T series unified storage, OceanStor Dorado high-performance storage, and OceanStor HVS high-end storage to provide block storage services for OpenStack."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:36(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:112(para)
-msgid "Create clone volume"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:12(para)
-msgid "OceanStor T series unified storage supports the following operations:<placeholder-1/>OceanStor Dorado5100 supports the following operations:<placeholder-2/>OceanStor Dorado2100 G2 supports the following operations:<placeholder-3/>OceanStor HVS supports the following operations:<placeholder-4/>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:123(title)
-msgid "Configure Cinder nodes"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:124(para)
-msgid "In <filename>/etc/cinder</filename>, create the driver configuration file named <filename>cinder_huawei_conf.xml</filename>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:127(para)
-msgid "You must configure <option>Product</option> and <option>Protocol</option> to specify a storage system and link type. The following uses the iSCSI driver as an example. The driver configuration file of OceanStor T series unified storage is shown as follows:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:158(para)
-msgid "The driver configuration file of OceanStor Dorado5100 is shown as follows:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:184(para)
-msgid "The driver configuration file of OceanStor Dorado2100 G2 is shown as follows:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:208(para)
-msgid "The driver configuration file of OceanStor HVS is shown as follows:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:234(para)
-msgid "You do not need to configure the iSCSI target IP address for the Fibre Channel driver. In the prior example, delete the iSCSI configuration:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:244(para)
-msgid "To add <option>volume_driver</option> and <option>cinder_huawei_conf_file</option> items, you can modify the <filename>cinder.conf</filename> configuration file as follows:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:250(para)
-msgid "You can configure multiple Huawei back-end storages as follows:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:261(para)
-msgid "OceanStor HVS storage system supports the QoS function. You must create a QoS policy for the HVS storage system and create the volume type to enable QoS as follows:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:270(para)
-msgid "<option>OpenStack_QoS_high</option> is a QoS policy created by a user for the HVS storage system. <option>QoS_high</option> is the self-defined volume type. Set the <option>io_priority</option> option to <literal>high</literal>, <literal>normal</literal>, or <literal>low</literal>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:278(para)
-msgid "OceanStor HVS storage system supports the SmartTier function. SmartTier has three tiers. You can create the volume type to enable SmartTier as follows:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:286(para)
-msgid "<option>distribute_policy</option> and <option>transfer_strategy</option> can only be set to <literal>high</literal>, <literal>normal</literal>, or <literal>low</literal>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:293(title)
-msgid "Configuration file details"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:294(para)
-msgid "This table describes the Huawei storage driver configuration options:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:297(caption)
-msgid "Huawei storage driver configuration options"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:306(th) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:203(th)
-msgid "Flag name"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:315(option)
-msgid "Product"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:324(para)
-msgid "Type of a storage product. Valid values are <literal>T</literal>, <literal>Dorado</literal>, or <literal>HVS</literal>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:331(option)
-msgid "Protocol"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:337(literal) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:416(para)
-msgid "iSCSI"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:338(literal)
-msgid "FC"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:336(td)
-msgid "Type of a protocol. Valid values are <placeholder-1/> or <placeholder-2/>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:342(option)
-msgid "ControllerIP0"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:347(td)
-msgid "IP address of the primary controller (not required for the HVS)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:352(option)
-msgid "ControllerIP1"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:361(para)
-msgid "IP address of the secondary controller (not required for the HVS)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:366(option)
-msgid "HVSURL"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:371(td)
-msgid "Access address of the Rest port (required only for the HVS)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:376(option)
-msgid "UserName"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:385(para)
-msgid "User name of an administrator"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:390(option)
-msgid "UserPassword"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:400(para)
-msgid "Password of an administrator"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:405(option)
-msgid "LUNType"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:411(para)
-msgid "Thin"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:414(para)
-msgid "Type of a created LUN. Valid values are <literal>Thick</literal> or <literal>Thin</literal>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:421(option)
-msgid "StripUnitSize"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:428(para)
-msgid "64"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:431(para)
-msgid "Stripe depth of a created LUN. The value is expressed in KB."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:433(para)
-msgid "This flag is not valid for a thin LUN."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:439(option)
-msgid "WriteType"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:446(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:464(para)
-msgid "1"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:449(para)
-msgid "Cache write method. The method can be write back, write through, or Required write back. The default value is <literal>1</literal>, indicating write back."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:458(option)
-msgid "MirrorSwitch"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:467(para)
-msgid "Cache mirroring policy. The default value is <literal>1</literal>, indicating that a mirroring policy is used."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:473(option)
-msgid "Prefetch Type"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:476(para)
-msgid "3"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:479(para)
-msgid "Cache prefetch strategy. The strategy can be constant prefetch, variable prefetch, or intelligent prefetch. Default value is <literal>3</literal>, which indicates intelligent prefetch and is not required for the HVS."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:488(option)
-msgid "Prefetch Value"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:494(para)
-msgid "Cache prefetch value."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:498(option)
-msgid "StoragePool"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:504(para)
-msgid "Name of a storage pool that you want to use. Not required for the Dorado2100 G2."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:510(option)
-msgid "DefaultTargetIP"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:516(para)
-msgid "Default IP address of the iSCSI port provided for compute nodes."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:521(option)
-msgid "Initiator Name"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:527(para)
-msgid "Name of a compute node initiator."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:531(option)
-msgid "Initiator TargetIP"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:537(para)
-msgid "IP address of the iSCSI port provided for compute nodes."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:542(option)
-msgid "OSType"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:545(para)
-msgid "Linux"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:547(td)
-msgid "The OS type for a compute node."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:550(option)
-msgid "HostIP"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:555(td)
-msgid "The IPs for compute nodes."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:562(para)
-msgid "You can configure one iSCSI target port for each or all compute nodes. The driver checks whether a target port IP address is configured for the current compute node. If not, select <option>DefaultTargetIP</option>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:569(para)
-msgid "You can configure multiple storage pools in one configuration file, which supports the use of multiple storage pools in a storage system. (HVS allows configuration of only one storage pool.)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:576(para)
-msgid "For details about LUN configuration information, see the <placeholder-1/> command in the command-line interface (CLI) documentation or run the <placeholder-2/> on the storage system CLI."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:585(para)
-msgid "After the driver is loaded, the storage system obtains any modification of the driver configuration file in real time and you do not need to restart the <systemitem class=\"service\">cinder-volume</systemitem> service."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/glusterfs-driver.xml:6(title)
-msgid "GlusterFS driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/glusterfs-driver.xml:7(para)
-msgid "GlusterFS is an open-source scalable distributed file system that is able to grow to petabytes and beyond in size. More information can be found on <link href=\"http://www.gluster.org/\">Gluster's homepage</link>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/glusterfs-driver.xml:12(para)
-msgid "This driver enables use of GlusterFS in a similar fashion as the NFS driver. It supports basic volume operations, and like NFS, does not support snapshot/clone."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/glusterfs-driver.xml:16(para)
-msgid "You must use a Linux kernel of version 3.4 or greater (or version 2.6.32 or greater in Red Hat Enterprise Linux/CentOS 6.3+) when working with Gluster-based volumes. See <link href=\"https://bugs.launchpad.net/nova/+bug/1177103\">Bug 1177103</link> for more information."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/glusterfs-driver.xml:22(para)
-msgid "To use Block Storage with GlusterFS, first set the <literal>volume_driver</literal> in <filename>cinder.conf</filename>:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/glusterfs-driver.xml:26(para)
-msgid "The following table contains the configuration options supported by the GlusterFS driver."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:6(title)
-msgid "EMC SMI-S iSCSI and FC drivers"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:7(para)
-msgid "The EMC volume drivers, <literal>EMCSMISISCSIDriver</literal> and <literal>EMCSMISFCDriver</literal>, has the ability to create/delete and attach/detach volumes and create/delete snapshots, and so on."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:11(para)
-msgid "The driver runs volume operations by communicating with the backend EMC storage. It uses a CIM client in Python called PyWBEM to perform CIM operations over HTTP."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:15(para)
-msgid "The EMC CIM Object Manager (ECOM) is packaged with the EMC SMI-S provider. It is a CIM server that enables CIM clients to perform CIM operations over HTTP by using SMI-S in the back-end for EMC storage operations."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:19(para)
-msgid "The EMC SMI-S Provider supports the SNIA Storage Management Initiative (SMI), an ANSI standard for storage management. It supports VMAX and VNX storage systems."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:24(para)
-msgid "EMC SMI-S Provider V4.6.1 and higher is required. You can download SMI-S from the <link href=\"https://support.emc.com\">EMC's support</link> web site (login is required). See the EMC SMI-S Provider release notes for installation instructions."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:30(para)
-msgid "EMC storage VMAX Family and VNX Series are supported."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:35(para)
-msgid "VMAX and VNX arrays support these operations:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:56(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:57(para)
-msgid "Create cloned volume"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:65(para)
-msgid "Only VNX supports the following operations:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:76(title)
-msgid "Set up the SMI-S drivers"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:78(title)
-msgid "To set up the EMC SMI-S drivers"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:80(para)
-msgid "Install the <package>python-pywbem</package> package for your distribution. See <xref linkend=\"install-pywbem\"/>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:85(para)
-msgid "Download SMI-S from PowerLink and install it. Add your VNX/VMAX arrays to SMI-S."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:87(para)
-msgid "For information, see <xref linkend=\"setup-smi-s\"/> and the SMI-S release notes."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:91(para)
-msgid "Register with VNX. See <xref linkend=\"register-vnx-iscsi\"/> for the VNX iSCSI driver and <xref linkend=\"register-vnx-fc\"/> for the VNX FC driver."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:98(para)
-msgid "Create a masking view on VMAX. See <xref linkend=\"create-masking\"/>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:103(title)
-msgid "Install the <package>python-pywbem</package> package"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:104(para)
-msgid "Install the <package>python-pywbem</package> package for your distribution, as follows:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:108(para)
-msgid "On Ubuntu:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:112(para)
-msgid "On openSUSE:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:116(para)
-msgid "On Fedora:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:122(title)
-msgid "Set up SMI-S"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:123(para)
-msgid "You can install SMI-S on a non-OpenStack host. Supported platforms include different flavors of Windows, Red Hat, and SUSE Linux. SMI-S can be installed on a physical server or a VM hosted by an ESX server. Note that the supported hypervisor for a VM running SMI-S is ESX only. See the EMC SMI-S Provider release notes for more information on supported platforms and installation instructions."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:132(para)
-msgid "You must discover storage arrays on the SMI-S server before you can use the Cinder driver. Follow instructions in the SMI-S release notes."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:137(para)
-msgid "SMI-S is usually installed at <filename>/opt/emc/ECIM/ECOM/bin</filename> on Linux and <filename>C:\\Program Files\\EMC\\ECIM\\ECOM\\bin</filename> on Windows. After you install and configure SMI-S, go to that directory and type <placeholder-1/>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:144(para)
-msgid "Use <placeholder-1/> in <placeholder-2/> to add an array. Use <placeholder-3/> and examine the output after the array is added. Make sure that the arrays are recognized by the SMI-S server before using the EMC Cinder driver."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:152(title)
-msgid "Register with VNX for the iSCSI driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:153(para)
-msgid "To export a VNX volume to a Compute node or a Volume node, you must register the node with VNX."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:156(title)
-msgid "Register the node"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:157(para)
-msgid "On the Compute node or Volume node <literal>1.1.1.1</literal>, do the following (assume <literal>10.10.61.35</literal> is the iscsi target):"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:165(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:109(para)
-msgid "Log in to VNX from the node using the target corresponding to the SPA port:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:168(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:112(para)
-msgid "Where <literal>iqn.1992-04.com.emc:cx.apm01234567890.a0</literal> is the initiator name of the node. Login to Unisphere, go to <literal>VNX00000</literal>-&gt;Hosts-&gt;Initiators, Refresh and wait until initiator <literal>iqn.1992-04.com.emc:cx.apm01234567890.a0</literal> with SP Port <literal>A-8v0</literal> appears."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:176(para)
-msgid "Click the <guibutton>Register</guibutton> button, select <guilabel>CLARiiON/VNX</guilabel>, and enter the host name <literal>myhost1</literal> and IP address <literal>myhost1</literal>. Click <guibutton>Register</guibutton>. Now host <literal>1.1.1.1</literal> also appears under Hosts-&gt;Host List."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:182(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:126(para)
-msgid "Log out of VNX on the node:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:185(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:129(para)
-msgid "Log in to VNX from the node using the target corresponding to the SPB port:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:189(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:133(para)
-msgid "In Unisphere register the initiator with the SPB port."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:191(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:135(para)
-msgid "Log out:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:196(title)
-msgid "Register with VNX for the FC driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:197(para)
-msgid "For a VNX volume to be exported to a Compute node or a Volume node, SAN zoning needs to be configured on the node and WWNs of the node need to be registered with VNX in Unisphere."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:203(title)
-msgid "Create a masking view on VMAX"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:204(para)
-msgid "For VMAX iSCSI and FC drivers, you need to do initial setup in Unisphere for VMAX. In Unisphere for VMAX, create an initiator group, a storage group, and a port group. Put them in a masking view. The initiator group contains the initiator names of the OpenStack hosts. The storage group will contain volumes provisioned by Block Storage."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:214(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:142(para)
-msgid "Make the following changes in <filename>/etc/cinder/cinder.conf</filename>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:216(para)
-msgid "For VMAX iSCSI driver, add the following entries, where <literal>10.10.61.45</literal> is the IP address of the VMAX iSCSI target:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:223(para)
-msgid "For VNX iSCSI driver, add the following entries, where <literal>10.10.61.35</literal> is the IP address of the VNX iSCSI target:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:230(para)
-msgid "For VMAX and VNX FC drivers, add the following entries:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:234(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:169(para)
-msgid "Restart the <systemitem class=\"service\">cinder-volume</systemitem> service."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:238(title)
-msgid "<filename>cinder_emc_config.xml</filename> configuration file"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:240(para)
-msgid "Create the <filename>/etc/cinder/cinder_emc_config.xml</filename> file. You do not need to restart the service for this change."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:242(para)
-msgid "For VMAX, add the following lines to the XML file:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:245(para)
-msgid "For VNX, add the following lines to the XML file:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:248(para)
-msgid "Where:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:251(para)
-msgid "<systemitem>StorageType</systemitem> is the thin pool from which the user wants to create the volume. Thin pools can be created using Unisphere for VMAX and VNX. If the <literal>StorageType</literal> tag is not defined, you have to define volume types and set the pool name in extra specs."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:260(para)
-msgid "<systemitem>EcomServerIp</systemitem> and <systemitem>EcomServerPort</systemitem> are the IP address and port number of the ECOM server which is packaged with SMI-S."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:265(para)
-msgid "<systemitem>EcomUserName</systemitem> and <systemitem>EcomPassword</systemitem> are credentials for the ECOM server."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:270(para)
-msgid "<systemitem>Timeout</systemitem> specifies the maximum number of seconds you want to wait for an operation to finish."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:277(para)
-msgid "To attach VMAX volumes to an OpenStack VM, you must create a Masking View by using Unisphere for VMAX. The Masking View must have an Initiator Group that contains the initiator of the OpenStack compute node that hosts the VM."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:287(title) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:173(title)
-msgid "Volume type support"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:288(para)
-msgid "Volume type support enables a single instance of <systemitem>cinder-volume</systemitem> to support multiple pools and thick/thin provisioning."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:291(para)
-msgid "When the <literal>StorageType</literal> tag in <filename>cinder_emc_config.xml</filename> is used, the pool name is specified in the tag. Only thin provisioning is supported in this case."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:295(para)
-msgid "When the <literal>StorageType</literal> tag is not used in <filename>cinder_emc_config.xml</filename>, the volume type needs to be used to define a pool name and a provisioning type. The pool name is the name of a pre-created pool. The provisioning type could be either <literal>thin</literal> or <literal>thick</literal>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:301(para)
-msgid "Here is an example of how to set up volume type. First create volume types. Then define extra specs for each volume type."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:305(title)
-msgid "Setup volume types"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:307(para)
-msgid "Create the volume types:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:312(para)
-msgid "Setup the volume type extra specs:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:319(para)
-msgid "In the above example, two volume types are created. They are <literal>High Performance</literal> and <literal> Standard Performance</literal>. For <literal>High Performance </literal>, <literal>storagetype:pool</literal> is set to <literal>smi_pool</literal> and <literal>storagetype:provisioning </literal> is set to <literal>thick</literal>. Similarly for <literal>Standard Performance</literal>, <literal> storagetype:pool</literal>. is set to <literal>smi_pool2</literal> and <literal>storagetype:provisioning</literal> is set to <literal>thin</literal>. If <literal>storagetype:provisioning </literal> is not specified, it will default to <literal> thin</literal>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:331(para)
-msgid "Volume type names <literal>High Performance</literal> and <literal>Standard Performance</literal> are user-defined and can be any names. Extra spec keys <literal>storagetype:pool</literal> and <literal>storagetype:provisioning</literal> have to be the exact names listed here. Extra spec value <literal>smi_pool </literal> is your pool name. The extra spec value for <literal>storagetype:provisioning</literal> has to be either <literal>thick</literal> or <literal>thin</literal>. The driver will look for a volume type first. If the volume type is specified when creating a volume, the driver will look for the volume type definition and find the matching pool and provisioning type. If the volume type is not specified, it will fall back to use the <literal>StorageType</literal> tag in <filename> cinder_emc_config.xml</filename>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:4(title)
-msgid "HP 3PAR Fibre Channel and iSCSI drivers"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:5(para)
-msgid "The <filename>HP3PARFCDriver</filename> and <filename>HP3PARISCSIDriver</filename> drivers, which are based on the Block Storage service (Cinder) plug-in architecture, run volume operations by communicating with the HP 3PAR storage system over HTTP, HTTPS, and SSH connections. The HTTP and HTTPS communications use <package>hp3parclient</package>, which is part of the Python standard library."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:13(para)
-msgid "For information about how to manage HP 3PAR storage systems, see the HP 3PAR user documentation."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:17(para)
-msgid "To use the HP 3PAR drivers, install the following software and components on the HP 3PAR storage system:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:22(para)
-msgid "HP 3PAR Operating System software version 3.1.3 or higher"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:26(para)
-msgid "HP 3PAR Web Services API Server must be enabled and running"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:30(para)
-msgid "One Common Provisioning Group (CPG)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:33(para)
-msgid "Additionally, you must install the <package>hp3parclient</package> version 3.0 or newer from the Python standard library on the system with the enabled Block Storage service volume drivers."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:45(para)
-msgid "Create volumes."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:48(para)
-msgid "Delete volumes."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:51(para)
-msgid "Extend volumes."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:54(para)
-msgid "Attach volumes."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:57(para)
-msgid "Detach volumes."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:60(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:343(para)
-msgid "Create snapshots."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:63(para)
-msgid "Delete snapshots."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:66(para)
-msgid "Create volumes from snapshots."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:69(para)
-msgid "Create cloned volumes."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:72(para)
-msgid "Copy images to volumes."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:75(para)
-msgid "Copy volumes to images."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:78(para)
-msgid "Volume migration(backend assisted)."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:81(para)
-msgid "Volume type support for both HP 3PAR drivers includes the ability to set the following capabilities in the OpenStack Block Storage API <filename>cinder.api.contrib.types_extra_specs</filename> volume type extra specs extension module:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:88(literal)
-msgid "hp3par:cpg"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:91(literal)
-msgid "hp3par:snap_cpg"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:94(literal)
-msgid "hp3par:provisioning"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:97(literal)
-msgid "hp3par:persona"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:100(literal)
-msgid "hp3par:vvs"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:103(para)
-msgid "To work with the default filter scheduler, the key values are case sensitive and scoped with <literal>hp3par:</literal>. For information about how to set the key-value pairs and associate them with a volume type, run the following command: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:112(para)
-msgid "Volumes that are cloned only support extra specs keys cpg, snap_cpg, provisioning and vvs. The others are ignored. In addition the comments section of the cloned volume in the HP 3PAR StoreServ storage array is not populated."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:118(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:166(para)
-msgid "If volume types are not used or a particular key is not set for a volume type, the following defaults are used:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:123(para)
-msgid "<literal>hp3par:cpg</literal> - Defaults to the <literal>hp3par_cpg</literal> setting in the <filename>cinder.conf</filename> file."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:128(para)
-msgid "<literal>hp3par:snap_cpg</literal> - Defaults to the <literal>hp3par_snap</literal> setting in the <filename>cinder.conf</filename> file. If <literal>hp3par_snap</literal> is not set, it defaults to the <literal>hp3par_cpg</literal> setting."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:136(para)
-msgid "<literal>hp3par:provisioning</literal> - Defaults to thin provisioning, the valid values are <literal>thin</literal> and <literal>full</literal>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:142(para)
-msgid "<literal>hp3par:persona</literal> - Defaults to the <literal>1 - Generic</literal> persona. The valid values are, <literal>1 - Generic</literal>, <literal>2 - Generic-ALUA</literal>, <literal>6 - Generic-legacy</literal>, <literal>7 - HPUX-legacy</literal>, <literal>8 - AIX-legacy</literal>, <literal>9 - EGENERA</literal>, <literal>10 - ONTAP-legacy</literal>, <literal>11 - VMware</literal>, <literal>12 - OpenVMS</literal>, <literal>13 - HPUX</literal>, and <literal>15 - WindowsServer</literal>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:156(para)
-msgid "QoS support for both HP 3PAR drivers includes the ability to set the following capabilities in the OpenStack Block Storage API <filename>cinder.api.contrib.qos_specs_manage</filename> qos specs extension module:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:163(literal)
-msgid "minBWS"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:166(literal)
-msgid "maxBWS"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:169(literal)
-msgid "minIOPS"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:172(literal)
-msgid "maxIOPS"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:175(literal)
-msgid "latency"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:178(literal)
-msgid "priority"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:181(para)
-msgid "The qos keys above no longer require to be scoped but must be created and associated to a volume type. For information about how to set the key-value pairs and associate them with a volume type, run the following commands: <placeholder-1/><placeholder-2/><placeholder-3/>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:191(para)
-msgid "The following keys require that the HP 3PAR StoreServ storage array has a Priority Optimization license installed."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:196(para)
-msgid "<literal>hp3par:vvs</literal> - The virtual volume set name that has been predefined by the Administrator with Quality of Service (QoS) rules associated to it. If you specify extra_specs <literal>hp3par:vvs</literal>, the qos_specs <literal>minIOPS</literal>, <literal>maxIOPS</literal>, <literal>minBWS</literal>, and <literal>maxBWS</literal> settings are ignored."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:207(para)
-msgid "<literal>minBWS</literal> - The QoS I/O issue bandwidth minimum goal in MBs. If not set, the I/O issue bandwidth rate has no minimum goal."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:212(para)
-msgid "<literal>maxBWS</literal> - The QoS I/O issue bandwidth rate limit in MBs. If not set, the I/O issue bandwidth rate has no limit."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:217(para)
-msgid "<literal>minIOPS</literal> - The QoS I/O issue count minimum goal. If not set, the I/O issue count has no minimum goal."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:222(para)
-msgid "<literal>maxIOPS</literal> - The QoS I/O issue count rate limit. If not set, the I/O issue count rate has no limit."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:227(para)
-msgid "<literal>latency</literal> - The latency goal in milliseconds."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:231(para)
-msgid "<literal>priority</literal> - The priority of the QoS rule over other rules. If not set, the priority is normal, valid values are low, normal and high."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:238(para)
-msgid "Since the Icehouse release, minIOPS and maxIOPS must be used together to set I/O limits. Similarly, minBWS and maxBWS must be used together. If only one is set the other will be set to the same value."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:245(title)
-msgid "Enable the HP 3PAR Fibre Channel and iSCSI drivers"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:247(para)
-msgid "The <filename>HP3PARFCDriver</filename> and <filename>HP3PARISCSIDriver</filename> are installed with the OpenStack software."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:252(para)
-msgid "Install the <filename>hp3parclient</filename> Python package on the OpenStack Block Storage system. <placeholder-1/>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:259(para)
-msgid "Verify that the HP 3PAR Web Services API server is enabled and running on the HP 3PAR storage system."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:264(para)
-msgid "Log onto the HP 3PAR storage system with administrator access."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:267(replaceable)
-msgid "&lt;HP 3PAR IP Address&gt;"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:270(para)
-msgid "View the current state of the Web Services API Server."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:277(para)
-msgid "If the Web Services API Server is disabled, start it."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:286(para)
-msgid "If the HTTP or HTTPS state is disabled, enable one of them. <placeholder-1/> or <placeholder-2/>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:293(para)
-msgid "To stop the Web Services API Server, use the stopwsapi command. For other options run the <placeholder-1/> command."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:300(para)
-msgid "If you are not using an existing CPG, create a CPG on the HP 3PAR storage system to be used as the default location for creating volumes."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:308(emphasis) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:245(emphasis) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:380(emphasis)
-msgid "## REQUIRED SETTINGS"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:343(emphasis) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:262(emphasis) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:400(emphasis)
-msgid "## OPTIONAL SETTINGS"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:356(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:270(para)
-msgid "You can enable only one driver on each cinder instance unless you enable multiple back-end support. See the Cinder multiple back-end support instructions to enable this feature."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:363(para)
-msgid "You can configure one or more iSCSI addresses by using the <option>hp3par_iscsi_ips</option> option. When you configure multiple addresses, the driver selects the iSCSI port with the fewest active volumes at attach time. The IP address might include an IP port by using a colon (<literal>:</literal>) to separate the address from port. If you do not define an IP port, the default port 3260 is used. Separate IP addresses with a comma (<literal>,</literal>). The <option>iscsi_ip_address</option>/<option>iscsi_port</option> options might be used as an alternative to <option>hp3par_iscsi_ips</option> for single port iSCSI configuration."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:382(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:299(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:413(para)
-msgid "Save the changes to the <filename>cinder.conf</filename> file and restart the <systemitem class=\"service\">cinder-volume</systemitem> service."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:388(para)
-msgid "The HP 3PAR Fibre Channel and iSCSI drivers are now enabled on your OpenStack system. If you experience problems, review the Block Storage service log files for errors."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:6(title)
-msgid "Dell EqualLogic volume driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:7(para)
-msgid "The Dell EqualLogic volume driver interacts with configured EqualLogic arrays and supports various operations, such as volume creation and deletion, volume attachment and detachment, snapshot creation and deletion, and clone creation."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:12(para)
-msgid "To configure and use a Dell EqualLogic array with Block Storage, modify your <filename>cinder.conf</filename> as follows."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:15(para)
-msgid "Set the <option>volume_driver</option> option to the Dell EqualLogic volume driver:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:18(para)
-msgid "Set the <option>san_ip</option> option to the IP address to reach the EqualLogic Group through SSH:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:21(para)
-msgid "Set the <option>san_login</option> option to the user name to login to the Group manager:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:24(para)
-msgid "Set the <option>san_password</option> option to the password to login the Group manager with:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:27(para)
-msgid "Optionally set the <option>san_thin_provision</option> option to false to disable creation of thin-provisioned volumes:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/dell-equallogic-driver.xml:31(para)
-msgid "The following table describes additional options that the driver supports:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:5(title)
-msgid "IBM Storwize family and SVC volume driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:6(para)
-msgid "The volume management driver for Storwize family and SAN Volume Controller (SVC) provides OpenStack Compute instances with access to IBM Storwize family or SVC storage systems."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:11(title)
-msgid "Configure the Storwize family and SVC system"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:13(title)
-msgid "Network configuration"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:14(para)
-msgid "The Storwize family or SVC system must be configured for iSCSI, Fibre Channel, or both."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:16(para)
-msgid "If using iSCSI, each Storwize family or SVC node should have at least one iSCSI IP address. The IBM Storwize/SVC driver uses an iSCSI IP address associated with the volume's preferred node (if available) to attach the volume to the instance, otherwise it uses the first available iSCSI IP address of the system. The driver obtains the iSCSI IP address directly from the storage system; you do not need to provide these iSCSI IP addresses directly to the driver."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:27(para)
-msgid "If using iSCSI, ensure that the compute nodes have iSCSI network access to the Storwize family or SVC system."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:32(para)
-msgid "OpenStack Nova's Grizzly version supports iSCSI multipath. Once this is configured on the Nova host (outside the scope of this documentation), multipath is enabled."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:37(para)
-msgid "If using Fibre Channel (FC), each Storwize family or SVC node should have at least one WWPN port configured. If the <literal>storwize_svc_multipath_enabled</literal> flag is set to True in the Cinder configuration file, the driver uses all available WWPNs to attach the volume to the instance (details about the configuration flags appear in the <link linkend=\"ibm-storwize-svc-driver2\"> next section</link>). If the flag is not set, the driver uses the WWPN associated with the volume's preferred node (if available), otherwise it uses the first available WWPN of the system. The driver obtains the WWPNs directly from the storage system; you do not need to provide these WWPNs directly to the driver."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:54(para)
-msgid "If using FC, ensure that the compute nodes have FC connectivity to the Storwize family or SVC system."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:60(title)
-msgid "iSCSI CHAP authentication"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:68(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:290(para)
-msgid "CHAP secrets are added to existing hosts as well as newly-created ones. If the CHAP option is enabled, hosts will not be able to access the storage without the generated secrets."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:75(para)
-msgid "Not all OpenStack Compute drivers support CHAP authentication. Please check compatibility before using."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:80(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:283(para)
-msgid "CHAP secrets are passed from OpenStack Block Storage to Compute in clear text. This communication should be secured to ensure that CHAP secrets are not discovered."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:61(para)
-msgid "If using iSCSI for data access and the <literal>storwize_svc_iscsi_chap_enabled</literal> is set to <literal>True</literal>, the driver will associate randomly-generated CHAP secrets with all hosts on the Storwize family system. OpenStack compute nodes use these secrets when creating iSCSI connections. <placeholder-1/><placeholder-2/><placeholder-3/>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:87(title)
-msgid "Configure storage pools"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:88(para)
-msgid "Each instance of the IBM Storwize/SVC driver allocates all volumes in a single pool. The pool should be created in advance and be provided to the driver using the <literal>storwize_svc_volpool_name</literal> configuration flag. Details about the configuration flags and how to provide the flags to the driver appear in the <link linkend=\"ibm-storwize-svc-driver2\"> next section</link>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:99(title)
-msgid "Configure user authentication for the driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:101(para)
-msgid "The driver requires access to the Storwize family or SVC system management interface. The driver communicates with the management using SSH. The driver should be provided with the Storwize family or SVC management IP using the <literal>san_ip</literal> flag, and the management port should be provided by the <literal>san_ssh_port</literal> flag. By default, the port value is configured to be port 22 (SSH)."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:111(para)
-msgid "Make sure the compute node running the <systemitem class=\"service\">cinder-volume</systemitem> management driver has SSH network access to the storage system."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:118(para)
-msgid "To allow the driver to communicate with the Storwize family or SVC system, you must provide the driver with a user on the storage system. The driver has two authentication methods: password-based authentication and SSH key pair authentication. The user should have an Administrator role. It is suggested to create a new user for the management driver. Please consult with your storage and security administrator regarding the preferred authentication method and how passwords or SSH keys should be stored in a secure manner."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:129(para)
-msgid "When creating a new user on the Storwize or SVC system, make sure the user belongs to the Administrator group or to another group that has an Administrator role."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:134(para)
-msgid "If using password authentication, assign a password to the user on the Storwize or SVC system. The driver configuration flags for the user and password are <literal>san_login</literal> and <literal>san_password</literal>, respectively."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:140(para)
-msgid "If you are using the SSH key pair authentication, create SSH private and public keys using the instructions below or by any other method. Associate the public key with the user by uploading the public key: select the \"choose file\" option in the Storwize family or SVC management GUI under \"SSH public key\". Alternatively, you may associate the SSH public key using the command line interface; details can be found in the Storwize and SVC documentation. The private key should be provided to the driver using the <literal>san_private_key</literal> configuration flag."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:154(title)
-msgid "Create a SSH key pair with OpenSSH"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:155(para)
-msgid "You can create an SSH key pair using OpenSSH, by running:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:158(para)
-msgid "The command prompts for a file to save the key pair. For example, if you select 'key' as the filename, two files are created: <literal>key</literal> and <literal>key.pub</literal>. The <literal>key</literal> file holds the private SSH key and <literal>key.pub</literal> holds the public SSH key."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:165(para)
-msgid "The command also prompts for a pass phrase, which should be empty."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:167(para)
-msgid "The private key file should be provided to the driver using the <literal>san_private_key</literal> configuration flag. The public key should be uploaded to the Storwize family or SVC system using the storage management GUI or command line interface."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:173(para)
-msgid "Ensure that Cinder has read permissions on the private key file."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:179(title)
-msgid "Configure the Storwize family and SVC driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:181(title)
-msgid "Enable the Storwize family and SVC driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:182(para)
-msgid "Set the volume driver to the Storwize family and SVC driver by setting the <literal>volume_driver</literal> option in <filename>cinder.conf</filename> as follows:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:189(title)
-msgid "Storwize family and SVC driver options in cinder.conf"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:191(para)
-msgid "The following options specify default values for all volumes. Some can be over-ridden using volume types, which are described below."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:195(caption)
-msgid "List of configuration flags for Storwize storage and SVC driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:211(literal)
-msgid "san_ip"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:215(para)
-msgid "Management IP or host name"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:219(literal)
-msgid "san_ssh_port"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:222(para)
-msgid "22"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:223(para)
-msgid "Management port"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:226(literal)
-msgid "san_login"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:230(para)
-msgid "Management login username"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:234(literal)
-msgid "san_password"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:238(para)
-msgid "The authentication requires either a password (<literal>san_password</literal>) or SSH private key (<literal>san_private_key</literal>). One must be specified. If both are specified, the driver uses only the SSH private key."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:236(para)
-msgid "Required <placeholder-1/>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:248(para)
-msgid "Management login password"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:252(literal)
-msgid "san_private_key"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:254(para)
-msgid "Required <footnoteref linkend=\"storwize-svc-fn1\"/>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:258(para)
-msgid "Management login SSH private key"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:264(literal)
-msgid "storwize_svc_volpool_name"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:268(para)
-msgid "Default pool name for volumes"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:273(literal)
-msgid "storwize_svc_vol_rsize"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:276(para)
-msgid "2"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:280(para)
-msgid "The driver creates thin-provisioned volumes by default. The <literal>storwize_svc_vol_rsize</literal> flag defines the initial physical allocation percentage for thin-provisioned volumes, or if set to <literal>-1</literal>, the driver creates full allocated volumes. More details about the available options are available in the Storwize family and SVC documentation."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:277(para)
-msgid "Initial physical allocation (percentage) <placeholder-1/>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:297(literal)
-msgid "storwize_svc_vol_warning"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:300(para)
-msgid "0 (disabled)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:301(para)
-msgid "Space allocation warning threshold (percentage) <footnoteref linkend=\"storwize-svc-fn3\"/>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:308(literal)
-msgid "storwize_svc_vol_autoexpand"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:311(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:367(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:427(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:453(para)
-msgid "True"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:314(para)
-msgid "Defines whether thin-provisioned volumes can be auto expanded by the storage system, a value of <literal>True</literal> means that auto expansion is enabled, a value of <literal>False</literal> disables auto expansion. Details about this option can be found in the <literal>–autoexpand</literal> flag of the Storwize family and SVC command line interface <literal>mkvdisk</literal> command."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:312(para)
-msgid "Enable or disable volume auto expand <placeholder-1/>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:332(literal)
-msgid "storwize_svc_vol_grainsize"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:335(para)
-msgid "256"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:336(para)
-msgid "Volume grain size <footnoteref linkend=\"storwize-svc-fn3\"/> in KB"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:342(literal)
-msgid "storwize_svc_vol_compression"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:346(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:437(para) ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:88(replaceable)
-msgid "False"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:350(para)
-msgid "Defines whether Real-time Compression is used for the volumes created with OpenStack. Details on Real-time Compression can be found in the Storwize family and SVC documentation. The Storwize or SVC system must have compression enabled for this feature to work."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:347(para)
-msgid "Enable or disable Real-time Compression <placeholder-1/>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:364(literal)
-msgid "storwize_svc_vol_easytier"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:370(para)
-msgid "Defines whether Easy Tier is used for the volumes created with OpenStack. Details on EasyTier can be found in the Storwize family and SVC documentation. The Storwize or SVC system must have Easy Tier enabled for this feature to work."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:368(para)
-msgid "Enable or disable Easy Tier <placeholder-1/>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:382(literal)
-msgid "storwize_svc_vol_iogrp"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:386(para)
-msgid "The I/O group in which to allocate vdisks"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:391(literal)
-msgid "storwize_svc_flashcopy_timeout"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:395(para)
-msgid "120"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:398(para)
-msgid "The driver wait timeout threshold when creating an OpenStack snapshot. This is actually the maximum amount of time that the driver waits for the Storwize family or SVC system to prepare a new FlashCopy mapping. The driver accepts a maximum wait time of 600 seconds (10 minutes)."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:396(para)
-msgid "FlashCopy timeout threshold <placeholder-1/> (seconds)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:412(literal)
-msgid "storwize_svc_connection_protocol"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:417(para)
-msgid "Connection protocol to use (currently supports 'iSCSI' or 'FC')"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:423(literal)
-msgid "storwize_svc_iscsi_chap_enabled"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:428(para)
-msgid "Configure CHAP authentication for iSCSI connections"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:433(literal)
-msgid "storwize_svc_multipath_enabled"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:440(para)
-msgid "Multipath for iSCSI connections requires no storage-side configuration and is enabled if the compute host has multipath configured."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:438(para)
-msgid "Enable multipath for FC connections <placeholder-1/>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:449(literal)
-msgid "storwize_svc_multihost_enabled"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:457(para)
-msgid "This option allows the driver to map a vdisk to more than one host at a time. This scenario occurs during migration of a virtual machine with an attached volume; the volume is simultaneously mapped to both the source and destination compute hosts. If your deployment does not require attaching vdisks to multiple hosts, setting this flag to False will provide added safety."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:454(para)
-msgid "Enable mapping vdisks to multiple hosts <placeholder-1/>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:478(title)
-msgid "Placement with volume types"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:479(para)
-msgid "The IBM Storwize/SVC driver exposes capabilities that can be added to the <literal>extra specs</literal> of volume types, and used by the filter scheduler to determine placement of new volumes. Make sure to prefix these keys with <literal>capabilities:</literal> to indicate that the scheduler should use them. The following <literal>extra specs</literal> are supported:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:490(para)
-msgid "capabilities:volume_back-end_name - Specify a specific back-end where the volume should be created. The back-end name is a concatenation of the name of the IBM Storwize/SVC storage system as shown in <literal>lssystem</literal>, an underscore, and the name of the pool (mdisk group). For example: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:501(para)
-msgid "capabilities:compression_support - Specify a back-end according to compression support. A value of <literal>True</literal> should be used to request a back-end that supports compression, and a value of <literal>False</literal> will request a back-end that does not support compression. If you do not have constraints on compression support, do not set this key. Note that specifying <literal>True</literal> does not enable compression; it only requests that the volume be placed on a back-end that supports compression. Example syntax: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:517(para)
-msgid "capabilities:easytier_support - Similar semantics as the <literal>compression_support</literal> key, but for specifying according to support of the Easy Tier feature. Example syntax: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:525(para)
-msgid "capabilities:storage_protocol - Specifies the connection protocol used to attach volumes of this type to instances. Legal values are <literal>iSCSI</literal> and <literal>FC</literal>. This <literal>extra specs</literal> value is used for both placement and setting the protocol used for this volume. In the example syntax, note &lt;in&gt; is used as opposed to &lt;is&gt; used in the previous examples. <placeholder-1/>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:540(title)
-msgid "Configure per-volume creation options"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:541(para)
-msgid "Volume types can also be used to pass options to the IBM Storwize/SVC driver, which over-ride the default values set in the configuration file. Contrary to the previous examples where the \"capabilities\" scope was used to pass parameters to the Cinder scheduler, options can be passed to the IBM Storwize/SVC driver with the \"drivers\" scope."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:548(para)
-msgid "The following <literal>extra specs</literal> keys are supported by the IBM Storwize/SVC driver:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:552(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:662(para)
-msgid "rsize"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:555(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:665(para)
-msgid "warning"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:558(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:668(para)
-msgid "autoexpand"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:561(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:671(para)
-msgid "grainsize"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:564(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:674(para)
-msgid "compression"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:567(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:677(para)
-msgid "easytier"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:570(para)
-msgid "multipath"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:573(para) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:680(para)
-msgid "iogrp"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:576(para)
-msgid "These keys have the same semantics as their counterparts in the configuration file. They are set similarly; for example, <literal>rsize=2</literal> or <literal>compression=False</literal>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:582(title)
-msgid "Example: Volume types"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:583(para)
-msgid "In the following example, we create a volume type to specify a controller that supports iSCSI and compression, to use iSCSI when attaching the volume, and to enable compression:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:589(para)
-msgid "We can then create a 50GB volume using this type:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:593(para)
-msgid "Volume types can be used, for example, to provide users with different"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:597(para)
-msgid "performance levels (such as, allocating entirely on an HDD tier, using Easy Tier for an HDD-SDD mix, or allocating entirely on an SSD tier)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:603(para)
-msgid "resiliency levels (such as, allocating volumes in pools with different RAID levels)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:608(para)
-msgid "features (such as, enabling/disabling Real-time Compression)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:615(title)
-msgid "Operational notes for the Storwize family and SVC driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:618(title)
-msgid "Migrate volumes"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:619(para)
-msgid "In the context of OpenStack Block Storage's volume migration feature, the IBM Storwize/SVC driver enables the storage's virtualization technology. When migrating a volume from one pool to another, the volume will appear in the destination pool almost immediately, while the storage moves the data in the background."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:627(para)
-msgid "To enable this feature, both pools involved in a given volume migration must have the same values for <literal>extent_size</literal>. If the pools have different values for <literal>extent_size</literal>, the data will still be moved directly between the pools (not host-side copy), but the operation will be synchronous."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:638(title) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:75(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:334(para)
-msgid "Extend volumes"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:639(para)
-msgid "The IBM Storwize/SVC driver allows for extending a volume's size, but only for volumes without snapshots."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:644(title) ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:171(title)
-msgid "Snapshots and clones"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:645(para)
-msgid "Snapshots are implemented using FlashCopy with no background copy (space-efficient). Volume clones (volumes created from existing volumes) are implemented with FlashCopy, but with background copy enabled. This means that volume clones are independent, full copies. While this background copy is taking place, attempting to delete or extend the source volume will result in that operation waiting for the copy to complete."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:656(title) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:105(para)
-msgid "Volume retype"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:657(para)
-msgid "The IBM Storwize/SVC driver enables you to modify volume types. When you modify volume types, you can also change these extra specs properties:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:684(para)
-msgid "When you change the <literal>rsize</literal>, <literal>grainsize</literal> or <literal>compression</literal> properties, volume copies are asynchronously synchronized on the array."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:691(para)
-msgid "To change the <literal>iogrp</literal> property, IBM Storwize/SVC firmware version 6.4.0 or later is required."
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:62(None)
-msgid "@@image: '../../../common/figures/xenapinfs/local_config.png'; md5=16a3864b0ec636518335246360438fd1"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:78(None)
-msgid "@@image: '../../../common/figures/xenapinfs/remote_config.png'; md5=eab22f6aa5413c2043936872ea44e459"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:4(title)
-msgid "XenAPINFS"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:5(para)
-msgid "XenAPINFS is a Block Storage (Cinder) driver that uses an NFS share through the XenAPI Storage Manager to store virtual disk images and expose those virtual disks as volumes."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:8(para)
-msgid "This driver does not access the NFS share directly. It accesses the share only through XenAPI Storage Manager. Consider this driver as a reference implementation for use of the XenAPI Storage Manager in OpenStack (present in XenServer and XCP)."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:17(para)
-msgid "A XenServer/XCP installation that acts as Storage Controller. This hypervisor is known as the storage controller."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:22(para)
-msgid "Use XenServer/XCP as your hypervisor for Compute nodes."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:26(para)
-msgid "An NFS share that is configured for XenServer/XCP. For specific requirements and export options, see the administration guide for your specific XenServer version. The NFS share must be accessible by all XenServers components within your cloud."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:34(para)
-msgid "To create volumes from XenServer type images (vhd tgz files), XenServer Nova plug-ins are also required on the storage controller."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:40(para)
-msgid "You can use a XenServer as a storage controller and compute node at the same time. This minimal configuration consists of a XenServer/XCP box and an NFS share."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:47(title)
-msgid "Configuration patterns"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:50(para)
-msgid "Local configuration (Recommended): The driver runs in a virtual machine on top of the storage controller. With this configuration, you can create volumes from <literal>qemu-img</literal>-supported formats."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:57(title)
-msgid "Local configuration"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:68(para)
-msgid "Remote configuration: The driver is not a guest VM of the storage controller. With this configuration, you can only use XenServer vhd-type images to create volumes."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:73(title)
-msgid "Remote configuration"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:87(para)
-msgid "Assuming the following setup:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:90(para)
-msgid "XenServer box at <literal>10.2.2.1</literal>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:94(para)
-msgid "XenServer password is <literal>r00tme</literal>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:98(para)
-msgid "NFS server is <literal>nfs.example.com</literal>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:102(para)
-msgid "NFS export is at <literal>/volumes</literal>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:106(para)
-msgid "To use XenAPINFS as your cinder driver, set these configuration options in the <filename>cinder.conf</filename> file:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:115(para)
-msgid "The following table shows the configuration options that the XenAPINFS driver supports:"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:19(None)
-msgid "@@image: '../../../common/figures/ceph/ceph-architecture.png'; md5=f7e854c9dbfb64534c47c3583e774c81"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:4(title)
-msgid "Ceph RADOS Block Device (RBD)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:5(para)
-msgid "If you use KVM or QEMU as your hypervisor, you can configure the Compute service to use <link href=\"http://ceph.com/ceph-storage/block-storage/\"> Ceph RADOS block devices (RBD)</link> for volumes."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:15(title)
-msgid "Ceph architecture"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:9(para)
-msgid "Ceph is a massively scalable, open source, distributed storage system. It is comprised of an object store, block store, and a POSIX-compliant distributed file system. The platform can auto-scale to the exabyte level and beyond. It runs on commodity hardware, is self-healing and self-managing, and has no single point of failure. Ceph is in the Linux kernel and is integrated with the OpenStack cloud operating system. Due to its open-source nature, you can install and use this portable storage platform in public or private clouds. <placeholder-1/>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:25(title)
-msgid "RADOS"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:26(para)
-msgid "Ceph is based on <emphasis>RADOS: Reliable Autonomic Distributed Object Store</emphasis>. RADOS distributes objects across the storage cluster and replicates objects for fault tolerance. RADOS contains the following major components:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:32(para)
-msgid "<emphasis>Object Storage Device (OSD) Daemon</emphasis>. The storage daemon for the RADOS service, which interacts with the OSD (physical or logical storage unit for your data)."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:35(para)
-msgid "You must run this daemon on each server in your cluster. For each OSD, you can have an associated hard drive disk. For performance purposes, pool your hard drive disk with raid arrays, logical volume management (LVM), or B-tree file system (<systemitem>Btrfs</systemitem>) pooling. By default, the following pools are created: data, metadata, and RBD."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:42(para)
-msgid "<emphasis>Meta-Data Server (MDS)</emphasis>. Stores metadata. MDSs build a POSIX file system on top of objects for Ceph clients. However, if you do not use the Ceph file system, you do not need a metadata server."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:49(para)
-msgid "<emphasis>Monitor (MON)</emphasis>. A lightweight daemon that handles all communications with external applications and clients. It also provides a consensus for distributed decision making in a Ceph/RADOS cluster. For instance, when you mount a Ceph shared on a client, you point to the address of a MON server. It checks the state and the consistency of the data. In an ideal setup, you must run at least three <code>ceph-mon</code> daemons on separate servers."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:58(para)
-msgid "Ceph developers recommend that you use <systemitem>Btrfs</systemitem> as a file system for storage. XFS might be a better alternative for production environments;XFS is an excellent alternative to Btrfs. The ext4 file system is also compatible but does not exploit the power of Ceph."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:63(para)
-msgid "If using <systemitem>Btrfs</systemitem>, ensure that you use the correct version (see <link href=\"http://ceph.com/docs/master/start/os-recommendations/.\">Ceph Dependencies</link>)."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:66(para)
-msgid "For more information about usable file systems, see <link href=\"http://ceph.com/ceph-storage/file-system/\">ceph.com/ceph-storage/file-system/</link>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:72(title)
-msgid "Ways to store, use, and expose data"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:73(para)
-msgid "To store and access your data, you can use the following storage systems:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:77(para)
-msgid "<emphasis>RADOS</emphasis>. Use as an object, default storage mechanism."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:81(para)
-msgid "<emphasis>RBD</emphasis>. Use as a block device. The Linux kernel RBD (rados block device) driver allows striping a Linux block device over multiple distributed object store data objects. It is compatible with the KVM RBD image."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:88(para)
-msgid "<emphasis>CephFS</emphasis>. Use as a file, POSIX-compliant file system."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:92(para)
-msgid "Ceph exposes RADOS; you can access it through the following interfaces:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:95(para)
-msgid "<emphasis>RADOS Gateway</emphasis>. OpenStack Object Storage and Amazon-S3 compatible RESTful interface (see <link href=\"http://ceph.com/wiki/RADOS_Gateway\">RADOS_Gateway</link>)."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:101(para)
-msgid "<emphasis>librados</emphasis>, and its related C/C++ bindings."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:104(para)
-msgid "<emphasis>rbd and QEMU-RBD</emphasis>. Linux kernel and QEMU block devices that stripe data across multiple objects."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:111(title)
-msgid "Driver options"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:112(para)
-msgid "The following table contains the configuration options supported by the Ceph RADOS Block Device driver."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:4(title)
-msgid "HP LeftHand/StoreVirtual driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:5(para)
-msgid "The <filename>HPLeftHandISCSIDriver</filename> is based on the Block Storage service (Cinder) plug-in architecture. Volume operations are run by communicating with the HP LeftHand/StoreVirtual system over HTTPS, or SSH connections. HTTPS communications use the <package>hplefthandclient</package>, which is part of the Python standard library."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:15(para)
-msgid "The <filename>HPLeftHandISCSIDriver</filename> can be configured to run in one of two possible modes, legacy mode which uses SSH/CLIQ to communicate with the HP LeftHand/StoreVirtual array, or standard mode which uses a new REST client to communicate with the array. No new functionality has been, or will be, supported in legacy mode. For performance improvements and new functionality, the driver must be configured for standard mode, the <package>hplefthandclient</package> must be downloaded, and HP LeftHand/StoreVirtual Operating System software version 11.5 or higher is required on the array. To configure the driver in standard mode, see <xref linkend=\"hp-lefthand-rest-driver\"/>. To configure the driver in legacy mode, see <xref linkend=\"hp-lefthand-clix-driver\"/>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:33(para)
-msgid "For information about how to manage HP LeftHand/StoreVirtual storage systems, see the HP LeftHand/StoreVirtual user documentation."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:37(title)
-msgid "HP LeftHand/StoreVirtual REST driver standard mode"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:38(para)
-msgid "This section describes how to configure the HP LeftHand/StoreVirtual Cinder driver in standard mode."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:43(para)
-msgid "To use the HP LeftHand/StoreVirtual driver in standard mode, do the following:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:48(para)
-msgid "Install LeftHand/StoreVirtual Operating System software version 11.5 or higher on the HP LeftHand/StoreVirtual storage system."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:54(para)
-msgid "Create a cluster group."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:57(para)
-msgid "Install the <package>hplefthandclient</package> version 1.0.2 from the Python Package Index on the system with the enabled Block Storage service volume drivers."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:69(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:328(para)
-msgid "Create volumes"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:72(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:331(para)
-msgid "Delete volumes"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:78(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:337(para)
-msgid "Attach volumes"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:81(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:340(para)
-msgid "Detach volumes"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:84(para)
-msgid "Create snapshots"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:87(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:346(para)
-msgid "Delete snapshots"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:90(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:349(para)
-msgid "Create volumes from snapshots"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:93(para)
-msgid "Create cloned volumes"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:96(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:352(para)
-msgid "Copy images to volumes"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:99(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:355(para)
-msgid "Copy volumes to images"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:102(para)
-msgid "Backend assisted volume migration"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:108(para)
-msgid "When a volume is migrated, using Backend assisted volume migration, both source and destination clusters must be in the same HP LeftHand/StoreVirtual management group. The HP LeftHand/StoreVirtual array will use native LeftHand APIs to migrate the volume. The volume cannot be attached or have snapshots to migrate."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:115(para)
-msgid "Volume type support for the driver includes the ability to set the following capabilities in the OpenStack Cinder API <filename>cinder.api.contrib.types_extra_specs</filename> volume type extra specs extension module."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:124(literal) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:169(term)
-msgid "hplh:provisioning"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:129(literal) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:152(term) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:175(term)
-msgid "hplh:ao"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:134(literal) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:156(term) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:181(term)
-msgid "hplh:data_pl"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:138(para)
-msgid "To work with the default filter scheduler, the key values are case sensitive and scoped with <literal>'hplh:'</literal>. For information about how to set the key-value pairs and associate them with a volume type, run the following command:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:149(para)
-msgid "The following keys require that the HP LeftHand/StoreVirtual storage array be configured for."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:153(para)
-msgid "The HP LeftHand/StoreVirtual storage array must be configured for Adaptive Optimization."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:157(para)
-msgid "The HP LeftHand/StoreVirtual storage array must be able to support the Data Protection level specified by the extra spec."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:170(para)
-msgid "Defaults to <parameter>thin</parameter> provisioning, the valid values are, <parameter>thin</parameter> and <parameter>full</parameter>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:176(para)
-msgid "Defaults to <parameter>true</parameter>, the valid values are, <parameter>true</parameter> and <parameter>false</parameter>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:182(para)
-msgid "Defaults to <parameter>r-0</parameter>, Network RAID-0 (None), the valid values are,"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:185(para)
-msgid "<parameter>r-0</parameter>, Network RAID-0 (None)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:189(para)
-msgid "<parameter>r-5</parameter>, Network RAID-5 (Single Parity)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:193(para)
-msgid "<parameter>r-10-2</parameter>, Network RAID-10 (2-Way Mirror)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:197(para)
-msgid "<parameter>r-10-3</parameter>, Network RAID-10 (3-Way Mirror)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:201(para)
-msgid "<parameter>r-10-4</parameter>, Network RAID-10 (4-Way Mirror)"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:205(para)
-msgid "<parameter>r-6</parameter>, Network RAID-6 (Dual Parity),"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:217(title)
-msgid "Enable the HP LeftHand/StoreVirtual iSCSI driver in standard mode"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:219(para) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:362(para)
-msgid "The <filename>HPLeftHandISCSIDriver</filename> is installed with the OpenStack software."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:226(para)
-msgid "Install the <filename>hplefthandclient</filename> Python package on the OpenStack Block Storage system."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:234(para)
-msgid "If you are not using an existing cluster, create a cluster on the HP LeftHand storage system to be used as the cluster for creating volumes."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:240(para)
-msgid "Make the following changes in the <filename>/etc/cinder/cinder.conf</filename> file:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:248(replaceable)
-msgid "https://10.10.0.141:8081/lhos"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:251(replaceable) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:386(replaceable)
-msgid "lhuser"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:254(replaceable) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:389(replaceable)
-msgid "lhpass"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:257(replaceable) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:395(replaceable)
-msgid "ClusterLefthand"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:276(para)
-msgid "If the <option>hplefthand_iscsi_chap_enabled</option> is set to <literal>true</literal>, the driver will associate randomly-generated CHAP secrets with all hosts on the HP LeftHand/StoreVirtual system. OpenStack Compute nodes use these secrets when creating iSCSI connections. <placeholder-1/><placeholder-2/>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:307(para)
-msgid "The HP LeftHand/StoreVirtual driver is now enabled in standard mode on your OpenStack system. If you experience problems, review the Block Storage service log files for errors."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:314(title)
-msgid "HP LeftHand/StoreVirtual CLIQ driver legacy mode"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:315(para)
-msgid "This section describes how to configure the HP LeftHand/StoreVirtual Cinder driver in legacy mode."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:318(para)
-msgid "The <filename>HPLeftHandISCSIDriver</filename> allows you to use a HP Lefthand/StoreVirtual SAN that supports the CLIQ interface. Every supported volume operation translates into a CLIQ call in the back-end."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:360(title)
-msgid "Enable the HP LeftHand/StoreVirtual iSCSI driver in legacy mode"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:369(para)
-msgid "If you are not using an existing cluster, create a cluster on the HP Lefthand storage system to be used as the cluster for creating volumes."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:383(replaceable)
-msgid "10.10.0.141"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:422(para)
-msgid "The HP LeftHand/StoreVirtual driver is now enabled in legacy mode on your OpenStack system. If you experience problems, review the Block Storage service log files for errors."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:426(para)
-msgid "To configure the VSA"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:429(para)
-msgid "Configure CHAP on each of the <systemitem class=\"service\">nova-compute</systemitem> nodes."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:436(para)
-msgid "Add server associations on the VSA with the associated CHAPS and initiator information. The name should correspond to the <parameter>hostname</parameter> of the <parameter>nova-compute</parameter> node. For Xen, this is the hypervisor host name. To do this, use either CLIQ or the Centralized Management Console."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-msa-driver.xml:4(title)
-msgid "HP MSA Fibre Channel driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-msa-driver.xml:5(para)
-msgid "The HP MSA fiber channel driver runs volume operations on the storage array over HTTP."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-msa-driver.xml:7(para)
-msgid "A VDisk must be created on the HP MSA array first. This can be done using the web interface or the command-line interface of the array."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-msa-driver.xml:9(para)
-msgid "The following options must be defined in the <systemitem>cinder-volume</systemitem> configuration file (<filename>/etc/cinder/cinder.conf</filename>):"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-msa-driver.xml:14(para)
-msgid "Set the <option>volume_driver</option> option to <literal>cinder.volume.drivers.san.hp.hp_msa_fc.HPMSAFCDriver</literal>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-msa-driver.xml:19(para)
-msgid "Set the <option>san_ip</option> option to the hostname or IP address of your HP MSA array."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-msa-driver.xml:23(para)
-msgid "Set the <option>san_login</option> option to the login of an existing user of the HP MSA array."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/hp-msa-driver.xml:28(para)
-msgid "Set the <option>san_password</option> option to the password for this user."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/windows-volume-driver.xml:6(title)
-msgid "Windows"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/windows-volume-driver.xml:7(para)
-msgid "There is a volume back-end for Windows. Set the following in your <filename>cinder.conf</filename>, and use the options below to configure it."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/lvm-volume-driver.xml:6(title)
-msgid "LVM"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/lvm-volume-driver.xml:7(para)
-msgid "The default volume back-end uses local volumes managed by LVM."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/lvm-volume-driver.xml:8(para)
-msgid "This driver supports different transport protocols to attach volumes, currently ISCSI and ISER."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/lvm-volume-driver.xml:10(para)
-msgid "Set the following in your <filename>cinder.conf</filename>, and use the following options to configure for ISCSI transport:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/lvm-volume-driver.xml:16(para)
-msgid "and for the ISER transport:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:6(title)
-msgid "EMC VNX direct driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:7(para)
-msgid "Use the EMC VNX direct driver to create, attach, detach, and delete volumes, create and delete snapshots, and so on. This driver is based on the Cinder-defined <literal>ISCSIDriver</literal> driver."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:11(para)
-msgid "To complete volume operations, the driver uses the NaviSec command-line interface (CLI) to communicate with back-end EMC VNX storage."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:19(para)
-msgid "Flare version 5.32 or later."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:22(para)
-msgid "You must activate VNX Snapshot and Thin Provisioning license for the array. Ensure that all the iSCSI ports from the VNX are accessible through OpenStack hosts."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:27(para)
-msgid "Navisphere CLI v7.32 or later."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:30(para)
-msgid "EMC storage VNX Series are supported."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:71(title)
-msgid "Set up the VNX direct driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:72(para)
-msgid "Complete these high-level tasks to set up the VNX direct driver:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:76(para)
-msgid "Install NaviSecCLI. You must install the NaviSecCLI tool on the controller node and all the Cinder nodes in an OpenStack deployment. See <xref linkend=\"install-naviseccli\"/>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:83(para)
-msgid "Register with VNX. See <xref linkend=\"register-vnx-direct-iscsi\"/>"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:89(title)
-msgid "Install NaviSecCLI"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:90(para)
-msgid "On Ubuntu x64, download the NaviSecCLI deb package from <link href=\"https://github.com/emc-openstack/naviseccli\">EMC's OpenStack Github</link> web site."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:92(para)
-msgid "For all the other variants of Linux, download the NaviSecCLI rpm package from EMC's support web site for <link href=\"https://support.emc.com/downloads/36656_VNX2-Series\">VNX2 series</link> or <link href=\"https://support.emc.com/downloads/12781_VNX1-Series\">VNX1 series</link>. Login is required."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:96(title)
-msgid "Register with VNX"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:97(para)
-msgid "To export a VNX volume to a compute node or a volume node, you must register the node with VNX."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:100(title)
-msgid "To register the node"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:101(para)
-msgid "On the compute node or volume node <literal>1.1.1.1</literal>, do the following (assume <literal>10.10.61.35</literal> is the iSCSI target):"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:120(para)
-msgid "Click <guibutton>Register</guibutton>, select <guilabel>CLARiiON/VNX</guilabel>, and enter the host name <literal>myhost1</literal> and IP address <literal>myhost1</literal>. Click <guibutton>Register</guibutton>. Now host <literal>1.1.1.1</literal> also appears under Hosts-&gt;Host List."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:144(para)
-msgid "For the VNX iSCSI driver, add the following entries, where <literal>10.10.61.35</literal> is the IP address of the VNX iSCSI target, <literal>10.10.72.41</literal> is the IP address of the VNX array (SPA or SPB), <systemitem>default_timeout</systemitem> is the default time out for CLI operations in minutes, and <systemitem>max_luns_per_storage_group</systemitem> is the default max number of LUNs in a storage group:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:164(para)
-msgid "To find out <literal>max_luns_per_storage_group </literal> for each VNX model, refer to the <link href=\"https://support.emc.com/search/?text=White%20Paper%20Introduction%20to%20the%20VNX%20Series\">EMC's support</link> web site (login is required)."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:174(para)
-msgid "Volume type support allows user to choose thick/thin provisioning capabilities."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:176(para)
-msgid "Here is an example of how to setup volume type. First create volume types. Then define extra specs for each volume type."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:180(title)
-msgid "To set up volume types"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:182(para)
-msgid "Setup volume types:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:187(para)
-msgid "Setup volume type extra specs:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:192(para)
-msgid "The previous example creates two volume types: <literal>TypeA</literal> and <literal>TypeB</literal>. For <literal>TypeA</literal>, <literal>storagetype:provisioning </literal> is set to <literal>thick</literal>. Similarly for <literal>TypeB</literal>, <literal>storagetype:provisioning </literal> is set to <literal>thin</literal>. If <literal> storagetype:provisioning</literal> is not specified, it will be default to <literal>thick</literal>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:4(title)
-msgid "NFS driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:5(para)
-msgid "The Network File System (NFS) is a distributed file system protocol originally developed by Sun Microsystems in 1984. An NFS server <emphasis>exports</emphasis> one or more of its file systems, known as <emphasis>shares</emphasis>. An NFS client can mount these exported shares on its own file system. You can perform file actions on this mounted remote file system as if the file system were local."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:13(title)
-msgid "How the NFS driver works"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:14(para)
-msgid "The NFS driver, and other drivers based on it, work quite differently than a traditional block storage driver."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:17(para)
-msgid "The NFS driver does not actually allow an instance to access a storage device at the block level. Instead, files are created on an NFS share and mapped to instances, which emulates a block device. This works in a similar way to QEMU, which stores instances in the <filename>/var/lib/nova/instances</filename> directory."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:26(title)
-msgid "Enable the NFS driver and related options"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:27(para)
-msgid "To use Cinder with the NFS driver, first set the <literal>volume_driver</literal> in <filename>cinder.conf</filename>:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:31(para)
-msgid "The following table contains the options supported by the NFS driver."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:36(para)
-msgid "As of the Icehouse release, the NFS driver (and other drivers based off it) will attempt to mount shares using version 4.1 of the NFS protocol (including pNFS). If the mount attempt is unsuccessful due to a lack of client or server support, a subsequent mount attempt that requests the default behavior of the <placeholder-1/> command will be performed. On most distributions, the default behavior is to attempt mounting first with NFS v4.0, then silently fall back to NFS v3.0 if necessary. If the <option>nfs_mount_options</option> configuration option contains a request for a specific version of NFS to be used, or if specific options are specified in the shares configuration file specified by the <option>nfs_shares_config</option> configuration option, the mount will be attempted as requested with no subsequent attempts."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:55(title)
-msgid "How to use the NFS driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:58(para)
-msgid "Access to one or more NFS servers. Creating an NFS server is outside the scope of this document. This example assumes access to the following NFS servers and mount points:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:64(literal)
-msgid "192.168.1.200:/storage"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:67(literal)
-msgid "192.168.1.201:/storage"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:70(literal)
-msgid "192.168.1.202:/storage"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:73(para)
-msgid "This example demonstrates the use of with this driver with multiple NFS servers. Multiple servers are not required. One is usually enough."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:78(para)
-msgid "Add your list of NFS servers to the file you specified with the <literal>nfs_shares_config</literal> option. For example, if the value of this option was set to <literal>/etc/cinder/shares.txt</literal>, then:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:88(para)
-msgid "Comments are allowed in this file. They begin with a <literal>#</literal>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:92(para)
-msgid "Configure the <literal>nfs_mount_point_base</literal> option. This is a directory where <systemitem class=\"service\">cinder-volume</systemitem> mounts all NFS shares stored in <literal>shares.txt</literal>. For this example, <literal>/var/lib/cinder/nfs</literal> is used. You can, of course, use the default value of <literal>$state_path/mnt</literal>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:103(para)
-msgid "Start the <systemitem class=\"service\">cinder-volume</systemitem> service. <literal>/var/lib/cinder/nfs</literal> should now contain a directory for each NFS share specified in <literal>shares.txt</literal>. The name of each directory is a hashed name:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:115(para)
-msgid "You can now create volumes as you normally would:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:120(para)
-msgid "This volume can also be attached and deleted just like other volumes. However, snapshotting is <emphasis>not</emphasis> supported."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:127(title)
-msgid "NFS driver notes"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:130(para)
-msgid "<systemitem class=\"service\">cinder-volume</systemitem> manages the mounting of the NFS shares as well as volume creation on the shares. Keep this in mind when planning your OpenStack architecture. If you have one master NFS server, it might make sense to only have one <systemitem class=\"service\">cinder-volume</systemitem> service to handle all requests to that NFS server. However, if that single server is unable to handle all requests, more than one <systemitem class=\"service\">cinder-volume</systemitem> service is needed as well as potentially more than one NFS server."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:146(para)
-msgid "Because data is stored in a file and not actually on a block storage device, you might not see the same IO performance as you would with a traditional block storage driver. Please test accordingly."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:153(para)
-msgid "Despite possible IO performance loss, having volume data stored in a file might be beneficial. For example, backing up volumes can be as easy as copying the volume files."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/nfs-volume-driver.xml:158(para)
-msgid "Regular IO flushing and syncing still stands."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:4(title)
-msgid "IBM GPFS volume driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:5(para)
-msgid "IBM General Parallel File System (GPFS) is a cluster file system that provides concurrent access to file systems from multiple nodes. The storage provided by these nodes can be direct attached, network attached, SAN attached, or a combination of these methods. GPFS provides many features beyond common data access, including data replication, policy based storage management, and space efficient file snapshot and clone operations."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:14(title)
-msgid "How the GPFS driver works"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:15(para)
-msgid "The GPFS driver enables the use of GPFS in a fashion similar to that of the NFS driver. With the GPFS driver, instances do not actually access a storage device at the block level. Instead, volume backing files are created in a GPFS file system and mapped to instances, which emulate a block device."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:23(para)
-msgid "GPFS software must be installed and running on nodes where Block Storage and Compute services run in the OpenStack environment. A GPFS file system must also be created and mounted on these nodes before starting the <literal>cinder-volume</literal> service. The details of these GPFS specific steps are covered in <citetitle>GPFS: Concepts, Planning, and Installation Guide</citetitle> and <citetitle>GPFS: Administration and Programming Reference</citetitle>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:35(para)
-msgid "Optionally, the Image Service can be configured to store images on a GPFS file system. When a Block Storage volume is created from an image, if both image data and volume data reside in the same GPFS file system, the data from image file is moved efficiently to the volume file using copy-on-write optimization strategy."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:43(title)
-msgid "Enable the GPFS driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:44(para)
-msgid "To use the Block Storage service with the GPFS driver, first set the <literal>volume_driver</literal> in <filename>cinder.conf</filename>:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:48(para)
-msgid "The following table contains the configuration options supported by the GPFS driver."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:53(para)
-msgid "The <literal>gpfs_images_share_mode</literal> flag is only valid if the Image Service is configured to use GPFS with the <literal>gpfs_images_dir</literal> flag. When the value of this flag is <literal>copy_on_write</literal>, the paths specified by the <literal>gpfs_mount_point_base</literal> and <literal>gpfs_images_dir</literal> flags must both reside in the same GPFS file system and in the same GPFS file set."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:66(title)
-msgid "Volume creation options"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:67(para)
-msgid "It is possible to specify additional volume configuration options on a per-volume basis by specifying volume metadata. The volume is created using the specified options. Changing the metadata after the volume is created has no effect. The following table lists the volume creation options supported by the GPFS volume driver."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:75(caption)
-msgid "Volume Create Options for GPFS Volume Drive"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:79(th)
-msgid "Metadata Item Name"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:85(literal) ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:98(literal) ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:99(literal)
-msgid "fstype"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:88(literal)
-msgid "fstype=swap"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:86(td)
-msgid "Specifies whether to create a file system or a swap area on the new volume. If <placeholder-1/> is specified, the mkswap command is used to create a swap area. Otherwise the mkfs command is passed the specified file system type, for example ext3, ext4 or ntfs."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:96(literal)
-msgid "fslabel"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:97(td)
-msgid "Sets the file system label for the file system specified by <placeholder-1/> option. This value is only used if <placeholder-2/> is specified."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:103(literal)
-msgid "data_pool_name"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:105(para)
-msgid "Specifies the GPFS storage pool to which the volume is to be assigned. Note: The GPFS storage pool must already have been created."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:111(literal)
-msgid "replicas"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:113(para)
-msgid "Specifies how many copies of the volume file to create. Valid values are 1, 2, and, for GPFS V3.5.0.7 and later, 3. This value cannot be greater than the value of the <literal>MaxDataReplicas</literal> attribute of the file system."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:122(literal)
-msgid "dio"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:124(para)
-msgid "Enables or disables the Direct I/O caching policy for the volume file. Valid values are <literal>yes</literal> and <literal>no</literal>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:130(literal)
-msgid "write_affinity_depth"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:132(para)
-msgid "Specifies the allocation policy to be used for the volume file. Note: This option only works if <literal>allow-write-affinity</literal> is set for the GPFS data pool."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:139(literal)
-msgid "block_group_factor"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:141(para)
-msgid "Specifies how many blocks are laid out sequentially in the volume file to behave as a single large block. Note: This option only works if <literal>allow-write-affinity</literal> is set for the GPFS data pool."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:149(literal)
-msgid "write_affinity_failure_group"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:151(para)
-msgid "Specifies the range of nodes (in GPFS shared nothing architecture) where replicas of blocks in the volume file are to be written. See <citetitle>GPFS: Administration and Programming Reference</citetitle> for more details on this option."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:162(title)
-msgid "Example: Volume creation options"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:163(para)
-msgid "This example shows the creation of a 50GB volume with an <systemitem>ext4</systemitem> file system labeled <literal>newfs</literal> and direct IO enabled:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:169(title)
-msgid "Operational notes for GPFS driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:172(para)
-msgid "Volume snapshots are implemented using the GPFS file clone feature. Whenever a new snapshot is created, the snapshot file is efficiently created as a read-only clone parent of the volume, and the volume file uses copy-on-write optimization strategy to minimize data movement."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:178(para)
-msgid "Similarly when a new volume is created from a snapshot or from an existing volume, the same approach is taken. The same approach is also used when a new volume is created from an Image Service image, if the source image is in raw format, and <literal>gpfs_images_share_mode</literal> is set to <literal>copy_on_write</literal>."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/samples/emc-vmax.xml:3(StorageType) ./doc/config-reference/block-storage/drivers/samples/emc-vmax.xml:4(MaskingView) ./doc/config-reference/block-storage/drivers/samples/emc-vmax.xml:6(EcomServerPort) ./doc/config-reference/block-storage/drivers/samples/emc-vnx.xml:3(StorageType) ./doc/config-reference/block-storage/drivers/samples/emc-vnx.xml:5(EcomServerPort)
-msgid "xxxx"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/samples/emc-vmax.xml:5(EcomServerIp) ./doc/config-reference/block-storage/drivers/samples/emc-vnx.xml:4(EcomServerIp)
-msgid "x.x.x.x"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/samples/emc-vmax.xml:7(EcomUserName) ./doc/config-reference/block-storage/drivers/samples/emc-vmax.xml:8(EcomPassword) ./doc/config-reference/block-storage/drivers/samples/emc-vnx.xml:6(EcomUserName) ./doc/config-reference/block-storage/drivers/samples/emc-vnx.xml:7(EcomPassword)
-msgid "xxxxxxxx"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/drivers/samples/emc-vmax.xml:9(Timeout) ./doc/config-reference/block-storage/drivers/samples/emc-vnx.xml:8(Timeout)
-msgid "xx"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/backup/tsm-backup-driver.xml:6(title)
-msgid "IBM Tivoli Storage Manager backup driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/backup/tsm-backup-driver.xml:7(para)
-msgid "The IBM Tivoli Storage Manager (TSM) backup driver enables performing volume backups to a TSM server."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/backup/tsm-backup-driver.xml:10(para)
-msgid "The TSM client should be installed and configured on the machine running the <systemitem class=\"service\">cinder-backup </systemitem> service. See the <citetitle>IBM Tivoli Storage Manager Backup-Archive Client Installation and User's Guide</citetitle> for details on installing the TSM client."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/backup/tsm-backup-driver.xml:17(para)
-msgid "To enable the IBM TSM backup driver, include the following option in <filename>cinder.conf</filename>:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/backup/tsm-backup-driver.xml:20(para)
-msgid "The following configuration options are available for the TSM backup driver."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/backup/tsm-backup-driver.xml:23(para)
-msgid "This example shows the default options for the TSM backup driver."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:5(title)
-msgid "Ceph backup driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:6(para)
-msgid "The Ceph backup driver backs up volumes of any type to a Ceph back-end store. The driver can also detect whether the volume to be backed up is a Ceph RBD volume, and if so, it tries to perform incremental and differential backups."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:11(para)
-msgid "For source Ceph RBD volumes, you can perform backups within the same Ceph pool (not recommended) and backups between different Ceph pools and between different Ceph clusters."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:15(para)
-msgid "At the time of writing, differential backup support in Ceph/librbd was quite new. This driver attempts a differential backup in the first instance. If the differential backup fails, the driver falls back to full backup/copy."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:20(para)
-msgid "If incremental backups are used, multiple backups of the same volume are stored as snapshots so that minimal space is consumed in the backup store. It takes far less time to restore a volume than to take a full copy."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:26(para)
-msgid "Block Storage enables you to:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:29(para)
-msgid "Restore to a new volume, which is the default and recommended action."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:34(para)
-msgid "Restore to the original volume from which the backup was taken. The restore action takes a full copy because this is the safest action."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:42(para)
-msgid "To enable the Ceph backup driver, include the following option in the <filename>cinder.conf</filename> file:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:46(para)
-msgid "The following configuration options are available for the Ceph backup driver."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/backup/ceph-backup-driver.xml:50(para)
-msgid "This example shows the default options for the Ceph backup driver."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/backup/swift-backup-driver.xml:5(title)
-msgid "Swift backup driver"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/backup/swift-backup-driver.xml:6(para)
-msgid "The backup driver for Swift back-end performs a volume backup to a Swift object storage system."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/backup/swift-backup-driver.xml:8(para)
-msgid "To enable the Swift backup driver, include the following option in the <filename>cinder.conf</filename> file:"
-msgstr ""
-
-#: ./doc/config-reference/block-storage/backup/swift-backup-driver.xml:12(para)
-msgid "The following configuration options are available for the Swift back-end backup driver."
-msgstr ""
-
-#: ./doc/config-reference/block-storage/backup/swift-backup-driver.xml:16(para)
-msgid "This example shows the default options for the Swift back-end backup driver."
-msgstr ""
-
-#: ./doc/config-reference/database-service/section-databaseservice-rpc.xml:8(para)
-msgid "OpenStack projects use an open standard for messaging middleware known as AMQP. This messaging middleware enables the OpenStack services that run on multiple servers to talk to each other. OpenStack Trove RPC supports three implementations of AMQP: <application>RabbitMQ</application>, <application>Qpid</application>, and <application>ZeroMQ</application>."
-msgstr ""
-
-#: ./doc/config-reference/database-service/section-databaseservice-rpc.xml:18(para)
-msgid "Use these options to configure the <application>RabbitMQ</application> messaging system:"
-msgstr ""
-
-#: ./doc/config-reference/database-service/section-databaseservice-rpc.xml:25(para)
-msgid "Use these options to configure the <application>Qpid</application> messaging system:"
-msgstr ""
-
-#: ./doc/config-reference/database-service/section-databaseservice-rpc.xml:31(title)
-msgid "Configure ZeroMq"
-msgstr ""
-
-#: ./doc/config-reference/database-service/section-databaseservice-rpc.xml:32(para)
-msgid "Use these options to configure the <application>ZeroMq</application> messaging system:"
-msgstr ""
-
-#: ./doc/config-reference/database-service/section-databaseservice-db.xml:7(title)
-msgid "Configure the database"
-msgstr ""
-
-#: ./doc/config-reference/database-service/section-databaseservice-db.xml:9(para)
-msgid "Use the options to configure the used databases:"
-msgstr ""
-
-#: ./doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml:4(title)
-msgid "Telemetry sample configuration files"
-msgstr ""
-
-#: ./doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml:5(para)
-msgid "All the files in this section can be found in the <filename class=\"directory\">/etc/ceilometer/</filename> directory."
-msgstr ""
-
-#: ./doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml:8(title)
-msgid "ceilometer.conf"
-msgstr ""
-
-#: ./doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml:9(para)
-msgid "The configuration for the Telemetry services and agents is found in the <filename>ceilometer.conf</filename> file."
-msgstr ""
-
-#: ./doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml:11(para) ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:11(para) ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:19(para)
-msgid "This file must be modified after installation."
-msgstr ""
-
-#: ./doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml:18(title)
-msgid "event_definitions.yaml"
-msgstr ""
-
-#: ./doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml:19(para)
-msgid "The <filename>event_definitions.yaml</filename> file defines how events received from other OpenStack components should be translated to Telemetry samples."
-msgstr ""
-
-#: ./doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml:22(para) ./doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml:31(para) ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:26(para)
-msgid "You should not need to modify this file."
-msgstr ""
-
-#: ./doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml:26(title)
-msgid "pipeline.yaml"
-msgstr ""
-
-#: ./doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml:27(para)
-msgid "Pipelines describe a coupling between sources of samples and the corresponding sinks for transformation and publication of these data. They are defined in the <filename>pipeline.yaml</filename> file."
-msgstr ""
-
-#: ./doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml:36(para)
-msgid "The <filename>policy.json</filename> file defines additional access controls that apply to the Telemetry service."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:6(title)
-msgid "Endpoint listing middleware"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:7(para)
-msgid "The endpoint listing middleware enables third-party services that use data locality information to integrate with OpenStack Object Storage. This middleware reduces network overhead and is designed for third-party services that run inside the firewall. Deploy this middleware on a proxy server because usage of this middleware is not authenticated."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:11(para)
-msgid "Format requests for endpoints, as follows:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:12(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:13(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:14(replaceable)
-msgid "{account}"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:12(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:13(replaceable)
-msgid "{container}"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:12(replaceable)
-msgid "{object}"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:15(para)
-msgid "Use the <option>list_endpoints_path</option> configuration option in the <filename>proxy_server.conf</filename> file to customize the <literal>/endpoints/</literal> path."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:18(para)
-msgid "Responses are JSON-encoded lists of endpoints, as follows:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:20(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:21(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:22(replaceable)
-msgid "{server}"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:20(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:21(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:22(replaceable)
-msgid "{port}"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:20(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:21(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:22(replaceable)
-msgid "{dev}"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:20(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:21(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:22(replaceable)
-msgid "{part}"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:20(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:21(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:22(replaceable)
-msgid "{acc}"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:20(replaceable) ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:21(replaceable)
-msgid "{cont}"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:20(replaceable)
-msgid "{obj}"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-listendpoints.xml:23(para)
-msgid "An example response is:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_configure_s3.xml:6(title)
-msgid "Configure Object Storage with the S3 API"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_configure_s3.xml:7(para)
-msgid "The Swift3 middleware emulates the S3 REST API on top of Object Storage."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_configure_s3.xml:9(para)
-msgid "The following operations are currently supported:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_configure_s3.xml:12(para)
-msgid "GET Service"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_configure_s3.xml:15(para)
-msgid "DELETE Bucket"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_configure_s3.xml:18(para)
-msgid "GET Bucket (List Objects)"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_configure_s3.xml:21(para)
-msgid "PUT Bucket"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_configure_s3.xml:24(para)
-msgid "DELETE Object"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_configure_s3.xml:27(para)
-msgid "GET Object"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_configure_s3.xml:30(para)
-msgid "HEAD Object"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_configure_s3.xml:33(para)
-msgid "PUT Object"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_configure_s3.xml:36(para)
-msgid "PUT Object (Copy)"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_configure_s3.xml:39(para)
-msgid "To use this middleware, first download the latest version from its repository to your proxy server(s)."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_configure_s3.xml:43(para)
-msgid "Then, install it using standard python mechanisms, such as:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_configure_s3.xml:46(para)
-msgid "Alternatively, if you have configured the Ubuntu Cloud Archive, you may use: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_configure_s3.xml:49(para)
-msgid "To add this middleware to your configuration, add the <systemitem>swift3</systemitem> middleware in front of the <systemitem>swauth</systemitem> middleware, and before any other middleware that look at Object Storage requests (like rate limiting)."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_configure_s3.xml:52(para)
-msgid "Ensure that your <filename>proxy-server.conf</filename> file contains <systemitem>swift3</systemitem> in the pipeline and the <code>[filter:swift3]</code> section, as shown below:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_configure_s3.xml:60(para)
-msgid "Next, configure the tool that you use to connect to the S3 API. For S3curl, for example, you must add your host IP information by adding your host IP to the @endpoints array (line 33 in s3curl.pl):"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_configure_s3.xml:65(para)
-msgid "Now you can send commands to the endpoint, such as:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_configure_s3.xml:68(para)
-msgid "To set up your client, ensure you are using the ec2 credentials, which can be downloaded from the <guilabel>API Endpoints</guilabel> tab of the dashboard. The host should also point to the Object Storage storage node's hostname. It also will have to use the old-style calling format, and not the hostname-based container format. Here is an example client setup using the Python boto library on a locally installed all-in-one Object Storage installation."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:6(title)
-msgid "Configure Object Storage features"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:8(title)
-msgid "Object Storage zones"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:9(para)
-msgid "In OpenStack Object Storage, data is placed across different tiers of failure domains. First, data is spread across regions, then zones, then servers, and finally across drives. Data is placed to get the highest failure domain isolation. If you deploy multiple regions, the Object Storage service places the data across the regions. Within a region, each replica of the data should be stored in unique zones, if possible. If there is only one zone, data should be placed on different servers. And if there is only one server, data should be placed on different drives."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:20(para)
-msgid "Regions are widely separated installations with a high-latency or otherwise constrained network link between them. Zones are arbitrarily assigned, and it is up to the administrator of the Object Storage cluster to choose an isolation level and attempt to maintain the isolation level through appropriate zone assignment. For example, a zone may be defined as a rack with a single power source. Or a zone may be a DC room with a common utility provider. Servers are identified by a unique IP/port. Drives are locally attached storage volumes identified by mount point."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:31(para)
-msgid "In small clusters (five nodes or fewer), everything is normally in a single zone. Larger Object Storage deployments may assign zone designations differently; for example, an entire cabinet or rack of servers may be designated as a single zone to maintain replica availability if the cabinet becomes unavailable (for example, due to failure of the top of rack switches or a dedicated circuit). In very large deployments, such as service provider level deployments, each zone might have an entirely autonomous switching and power infrastructure, so that even the loss of an electrical circuit or switching aggregator would result in the loss of a single replica at most."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:45(title)
-msgid "Rackspace zone recommendations"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:46(para)
-msgid "For ease of maintenance on OpenStack Object Storage, Rackspace recommends that you set up at least five nodes. Each node is assigned its own zone (for a total of five zones), which gives you host level redundancy. This enables you to take down a single zone for maintenance and still guarantee object availability in the event that another zone fails during your maintenance."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:54(para)
-msgid "You could keep each server in its own cabinet to achieve cabinet level isolation, but you may wish to wait until your Object Storage service is better established before developing cabinet-level isolation. OpenStack Object Storage is flexible; if you later decide to change the isolation level, you can take down one zone at a time and move them to appropriate new homes."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:62(title)
-msgid "RAID controller configuration"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:63(para)
-msgid "OpenStack Object Storage does not require RAID. In fact, most RAID configurations cause significant performance degradation. The main reason for using a RAID controller is the battery-backed cache. It is very important for data integrity reasons that when the operating system confirms a write has been committed that the write has actually been committed to a persistent location. Most disks lie about hardware commits by default, instead writing to a faster write cache for performance reasons. In most cases, that write cache exists only in non-persistent memory. In the case of a loss of power, this data may never actually get committed to disk, resulting in discrepancies that the underlying file system must handle."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:76(para)
-msgid "OpenStack Object Storage works best on the XFS file system, and this document assumes that the hardware being used is configured appropriately to be mounted with the <placeholder-1/> option. For more information, refer to the XFS FAQ: <link href=\"http://xfs.org/index.php/XFS_FAQ\">http://xfs.org/index.php/XFS_FAQ</link>"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:84(para)
-msgid "To get the most out of your hardware, it is essential that every disk used in OpenStack Object Storage is configured as a standalone, individual RAID 0 disk; in the case of 6 disks, you would have six RAID 0s or one JBOD. Some RAID controllers do not support JBOD or do not support battery backed cache with JBOD. To ensure the integrity of your data, you must ensure that the individual drive caches are disabled and the battery backed cache in your RAID card is configured and used. Failure to configure the controller properly in this case puts data at risk in the case of sudden loss of power."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:96(para)
-msgid "You can also use hybrid drives or similar options for battery backed up cache configurations without a RAID controller."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:102(title)
-msgid "Throttle resources through rate limits"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:103(para)
-msgid "Rate limiting in OpenStack Object Storage is implemented as a pluggable middleware that you configure on the proxy server. Rate limiting is performed on requests that result in database writes to the account and container SQLite databases. It uses memcached and is dependent on the proxy servers having highly synchronized time. The rate limits are limited by the accuracy of the proxy server clocks."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:112(title)
-msgid "Configure rate limiting"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:113(para)
-msgid "All configuration is optional. If no account or container limits are provided, no rate limiting occurs. Available configuration options include:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:119(para)
-msgid "The container rate limits are linearly interpolated from the values given. A sample container rate limiting could be:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:122(para)
-msgid "container_ratelimit_100 = 100"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:123(para)
-msgid "container_ratelimit_200 = 50"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:124(para)
-msgid "container_ratelimit_500 = 20"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:125(para)
-msgid "This would result in:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:127(caption)
-msgid "Values for Rate Limiting with Sample Configuration Settings"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:131(td)
-msgid "Container Size"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:132(td)
-msgid "Rate Limit"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:135(td)
-msgid "0-99"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:136(td)
-msgid "No limiting"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:139(td) ./doc/config-reference/object-storage/section_object-storage-features.xml:140(td)
-msgid "100"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:144(td)
-msgid "150"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:145(td)
-msgid "75"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:148(td)
-msgid "500"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:149(td) ./doc/config-reference/object-storage/section_object-storage-features.xml:153(td)
-msgid "20"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:152(td)
-msgid "1000"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:160(title)
-msgid "Health check"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:161(para)
-msgid "Provides an easy way to monitor whether the Object Storage proxy server is alive. If you access the proxy with the path <filename>/healthcheck</filename>, it responds with <literal>OK</literal> in the response body, which monitoring tools can use."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:169(title)
-msgid "Domain remap"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:170(para)
-msgid "Middleware that translates container and account parts of a domain to path parameters that the proxy server understands."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:178(title)
-msgid "CNAME lookup"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:179(para)
-msgid "Middleware that translates an unknown domain in the host header to something that ends with the configured <code>storage_domain</code> by looking up the given domain's CNAME record in DNS."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:189(title)
-msgid "Temporary URL"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:190(para)
-msgid "Allows the creation of URLs to provide temporary access to objects. For example, a website may wish to provide a link to download a large object in OpenStack Object Storage, but the Object Storage account has no public access. The website can generate a URL that provides GET access for a limited time to the resource. When the web browser user clicks on the link, the browser downloads the object directly from Object Storage, eliminating the need for the website to act as a proxy for the request. If the user shares the link with all his friends, or accidentally posts it on a forum, the direct access is limited to the expiration time set when the website created the link."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:201(literal)
-msgid "temp_url_sig"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:203(para)
-msgid "A cryptographic signature"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:207(literal)
-msgid "temp_url_expires"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:209(para)
-msgid "An expiration date, in Unix time"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:198(para)
-msgid "A temporary URL is the typical URL associated with an object, with two additional query parameters:<placeholder-1/>"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:213(para)
-msgid "An example of a temporary URL:<placeholder-1/>"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:219(para)
-msgid "To create temporary URLs, first set the <literal>X-Account-Meta-Temp-URL-Key</literal> header on your Object Storage account to an arbitrary string. This string serves as a secret key. For example, to set a key of <literal>b3968d0207b54ece87cccc06515a89d4</literal> using the <placeholder-1/> command-line tool:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:224(replaceable)
-msgid "b3968d0207b54ece87cccc06515a89d4"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:225(para)
-msgid "Next, generate an HMAC-SHA1 (RFC 2104) signature to specify:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:229(para)
-msgid "Which HTTP method to allow (typically <literal>GET</literal> or <literal>PUT</literal>)"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:234(para)
-msgid "The expiry date as a Unix timestamp"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:237(para)
-msgid "The full path to the object"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:240(para)
-msgid "The secret key set as the <literal>X-Account-Meta-Temp-URL-Key</literal>"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:244(para)
-msgid "Here is code generating the signature for a GET for 24 hours on <code>/v1/AUTH_account/container/object</code>:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:259(para)
-msgid "Any alteration of the resource path or query arguments results in a <errorcode>401</errorcode><errortext>Unauthorized</errortext> error. Similarly, a PUT where GET was the allowed method returns a <errorcode>401</errorcode>. HEAD is allowed if GET or PUT is allowed. Using this in combination with browser form post translation middleware could also allow direct-from-browser uploads to specific locations in Object Storage."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:269(para)
-msgid "Changing the <literal>X-Account-Meta-Temp-URL-Key</literal> invalidates any previously generated temporary URLs within 60 seconds (the memcache time for the key). Object Storage supports up to two keys, specified by <literal>X-Account-Meta-Temp-URL-Key</literal> and <literal>X-Account-Meta-Temp-URL-Key-2</literal>. Signatures are checked against both keys, if present. This is to allow for key rotation without invalidating all existing temporary URLs."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:281(para)
-msgid "Opject Storage includes a script called <placeholder-1/> that generates the query parameters automatically:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:288(para)
-msgid "Because this command only returns the path, you must prefix the Object Storage host name (for example, <literal>https://swift-cluster.example.com</literal>)."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:291(para)
-msgid "With GET Temporary URLs, a <literal>Content-Disposition</literal> header is set on the response so that browsers interpret this as a file attachment to be saved. The file name chosen is based on the object name, but you can override this with a <literal>filename</literal> query parameter. The following example specifies a filename of <filename>My Test File.pdf</filename>:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:314(emphasis)
-msgid "tempurl"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:303(para)
-msgid "To enable Temporary URL functionality, edit <filename>/etc/swift/proxy-server.conf</filename> to add <literal>tempurl</literal> to the <literal>pipeline</literal> variable defined in the <literal>[pipeline:main]</literal> section. The <literal>tempurl</literal> entry should appear immediately before the authentication filters in the pipeline, such as <literal>authtoken</literal>, <literal>tempauth</literal> or <literal>keystoneauth</literal>. For example:<placeholder-1/>"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:321(title)
-msgid "Name check filter"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:322(para)
-msgid "Name Check is a filter that disallows any paths that contain defined forbidden characters or that exceed a defined length."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:330(title)
-msgid "Constraints"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:331(para)
-msgid "To change the OpenStack Object Storage internal limits, update the values in the <literal>swift-constraints</literal> section in the <filename>swift.conf</filename> file. Use caution when you update these values because they affect the performance in the entire cluster."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:342(title)
-msgid "Cluster health"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:343(para)
-msgid "Use the <placeholder-1/> tool to measure overall cluster health. This tool checks if a set of deliberately distributed containers and objects are currently in their proper places within the cluster. For instance, a common deployment has three replicas of each object. The health of that object can be measured by checking if each replica is in its proper place. If only 2 of the 3 is in place the object’s health can be said to be at 66.66%, where 100% would be perfect. A single object’s health, especially an older object, usually reflects the health of that entire partition the object is in. If you make enough objects on a distinct percentage of the partitions in the cluster,you get a good estimate of the overall cluster health. In practice, about 1% partition coverage seems to balance well between accuracy and the amount of time it takes to gather results. The first thing that needs to be done to provide this health value is create a new account solely for this usage. Next, you need to place the containers and objects throughout the system so that they are on distinct partitions. The <placeholder-2/> tool does this by making up random container and object names until they fall on distinct partitions. Last, and repeatedly for the life of the cluster, you must run the <placeholder-3/> tool to check the health of each of these containers and objects. These tools need direct access to the entire cluster and to the ring files (installing them on a proxy server suffices). The <placeholder-4/> and <placeholder-5/> commands both use the same configuration file, <filename>/etc/swift/dispersion.conf</filename>. Example <filename>dispersion.conf</filename> file:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:384(para)
-msgid "There are also configuration options for specifying the dispersion coverage, which defaults to 1%, retries, concurrency, and so on. However, the defaults are usually fine. Once the configuration is in place, run <placeholder-1/> to populate the containers and objects throughout the cluster. Now that those containers and objects are in place, you can run <placeholder-2/> to get a dispersion report, or the overall health of the cluster. Here is an example of a cluster in perfect health:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:404(para)
-msgid "Now, deliberately double the weight of a device in the object ring (with replication turned off) and re-run the dispersion report to show what impact that has:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:420(para)
-msgid "You can see the health of the objects in the cluster has gone down significantly. Of course, this test environment has just four devices, in a production environment with many devices the impact of one device change is much less. Next, run the replicators to get everything put back into place and then rerun the dispersion report:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:437(para)
-msgid "Alternatively, the dispersion report can also be output in json format. This allows it to be more easily consumed by third-party utilities:"
-msgstr ""
-
-#. Usage documented in http://docs.openstack.org/developer/swift/overview_large_objects.html
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:451(title)
-msgid "Static Large Object (SLO) support"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:452(para)
-msgid "This feature is very similar to Dynamic Large Object (DLO) support in that it enables the user to upload many objects concurrently and afterwards download them as a single object. It is different in that it does not rely on eventually consistent container listings to do so. Instead, a user-defined manifest of the object segments is used."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:464(title)
-msgid "Container quotas"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:465(para)
-msgid "The <code>container_quotas</code> middleware implements simple quotas that can be imposed on Object Storage containers by a user with the ability to set container metadata, most likely the account administrator. This can be useful for limiting the scope of containers that are delegated to non-admin users, exposed to formpost uploads, or just as a self-imposed sanity check."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:470(para)
-msgid "Any object PUT operations that exceed these quotas return a 413 response (request entity too large) with a descriptive body."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:473(para)
-msgid "Quotas are subject to several limitations: eventual consistency, the timeliness of the cached container_info (60 second ttl by default), and it is unable to reject chunked transfer uploads that exceed the quota (though once the quota is exceeded, new chunked transfers are refused)."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:479(para)
-msgid "Set quotas by adding meta values to the container. These values are validated when you set them:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:483(para)
-msgid "X-Container-Meta-Quota-Bytes: Maximum size of the container, in bytes."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:487(para)
-msgid "X-Container-Meta-Quota-Count: Maximum object count of the container."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:496(title)
-msgid "Account quotas"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:497(para)
-msgid "The <parameter>x-account-meta-quota-bytes</parameter> metadata entry must be requests (PUT, POST) if a given account quota (in bytes) is exceeded while DELETE requests are still allowed."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:501(para)
-msgid "The <parameter>x-account-meta-quota-bytes</parameter> metadata entry must be set to store and enable the quota. Write requests to this metadata entry are only permitted for resellers. There is no account quota limitation on a reseller account even if <parameter>x-account-meta-quota-bytes</parameter> is set."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:508(para)
-msgid "Any object PUT operations that exceed the quota return a 413 response (request entity too large) with a descriptive body."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:511(para)
-msgid "The following command uses an admin account that own the Reseller role to set a quota on the test account:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:515(para)
-msgid "Here is the stat listing of an account where quota has been set:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:525(para)
-msgid "This command removes the account quota:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:529(title)
-msgid "Bulk delete"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:530(para)
-msgid "Use <code>bulk-delete</code> to delete multiple files from an account with a single request. Responds to DELETE requests with a header 'X-Bulk-Delete: true_value'. The body of the DELETE request is a new line-separated list of files to delete. The files listed must be URL encoded and in the form:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:540(para)
-msgid "If all files are successfully deleted (or did not exist), the operation returns <code>HTTPOk</code>. If any files failed to delete, the operation returns <code>HTTPBadGateway</code>. In both cases, the response body is a JSON dictionary that shows the number of files that were successfully deleted or not found. The files that failed are listed."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:553(title)
-msgid "Drive audit"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:554(para)
-msgid "The <option>swift-drive-audit</option> configuration items reference a script that can be run by using <placeholder-1/> to watch for bad drives. If errors are detected, it unmounts the bad drive, so that OpenStack Object Storage can work around it. It takes the following options:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:565(title)
-msgid "Form post"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:566(para)
-msgid "Middleware that provides the ability to upload objects to a cluster using an HTML form POST. The format of the form is:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:581(para)
-msgid "The <literal>swift-url</literal> is the URL to the Object Storage destination, such as: <uri>https://swift-cluster.example.com/v1/AUTH_account/container/object_prefix</uri> The name of each file uploaded is appended to the specified <literal>swift-url</literal>. So, you can upload directly to the root of container with a URL like: <uri>https://swift-cluster.example.com/v1/AUTH_account/container/</uri> Optionally, you can include an object prefix to better separate different users’ uploads, such as: <uri>https://swift-cluster.example.com/v1/AUTH_account/container/object_prefix</uri>"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:591(para)
-msgid "The form method must be POST and the enctype must be set as <literal>multipart/form-data</literal>."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:594(para)
-msgid "The redirect attribute is the URL to redirect the browser to after the upload completes. The URL has status and message query parameters added to it, indicating the HTTP status code for the upload (2xx is success) and a possible message for further information if there was an error (such as <literal>“max_file_size exceeded”</literal>)."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:601(para)
-msgid "The <literal>max_file_size</literal> attribute must be included and indicates the largest single file upload that can be done, in bytes."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:604(para)
-msgid "The <literal>max_file_count</literal> attribute must be included and indicates the maximum number of files that can be uploaded with the form. Include additional <code>&lt;![CDATA[&lt;input type=\"file\" name=\"filexx\"/&gt;]]&gt;</code> attributes if desired."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:610(para)
-msgid "The expires attribute is the Unix timestamp before which the form must be submitted before it is invalidated."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:613(para)
-msgid "The signature attribute is the HMAC-SHA1 signature of the form. This sample Python code shows how to compute the signature:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:630(para)
-msgid "The key is the value of the <literal>X-Account-Meta-Temp-URL-Key</literal> header on the account."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:633(para)
-msgid "Be certain to use the full path, from the <literal>/v1/</literal> onward."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:635(para)
-msgid "The command-line tool <placeholder-1/> may be used (mostly just when testing) to compute expires and signature."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:639(para)
-msgid "The file attributes must appear after the other attributes to be processed correctly. If attributes come after the file, they are not sent with the sub-request because on the server side, all attributes in the file cannot be parsed unless the whole file is read into memory and the server does not have enough memory to service these requests. So, attributes that follow the file are ignored."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:652(title)
-msgid "Static web sites"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-features.xml:653(para)
-msgid "When configured, this middleware serves container data as a static web site with index file and error file resolution and optional file listings. This mode is normally only active for anonymous requests."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-cors.xml:6(title)
-msgid "Cross-origin resource sharing"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-cors.xml:7(para)
-msgid "Cross-Origin Resource Sharing (CORS) is a mechanism to allow code running in a browser (JavaScript for example) to make requests to a domain other then the one from where it originated. OpenStack Object Storage supports CORS requests to containers and objects within the containers using metadata held on the container."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-cors.xml:11(para)
-msgid "In addition to the metadata on containers, you can use the <option>cors_allow_origin</option> option in the <filename>proxy-server.conf</filename> file to set a list of hosts that are included with any CORS request by default."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:6(title)
-msgid "Object Storage general service configuration"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:7(para)
-msgid "Most Object Storage services fall into two categories, Object Storage's wsgi servers and background daemons."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:11(para)
-msgid "Object Storage uses paste.deploy to manage server configurations. Read more at <link href=\"http://pythonpaste.org/deploy/\">http://pythonpaste.org/deploy/</link>."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:14(para)
-msgid "Default configuration options are set in the `[DEFAULT]` section, and any options specified there can be overridden in any of the other sections when the syntax <literal>set option_name = value</literal> is in place."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:19(para)
-msgid "Configuration for servers and daemons can be expressed together in the same file for each type of server, or separately. If a required section for the service trying to start is missing there will be an error. Sections not used by the service are ignored."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:25(para)
-msgid "Consider the example of an Object Storage node. By convention configuration for the <systemitem class=\"service\">object-server</systemitem>, <systemitem class=\"service\">object-updater</systemitem>, <systemitem class=\"service\">object-replicator</systemitem>, and <systemitem class=\"service\">object-auditor</systemitem> exist in a single file <filename>/etc/swift/object-server.conf</filename>:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:51(para)
-msgid "Object Storage services expect a configuration path as the first argument:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:59(para)
-msgid "If you omit the object-auditor section, this file cannot be used as the configuration path when starting the <placeholder-1/> daemon:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:67(para)
-msgid "If the configuration path is a directory instead of a file all of the files in the directory with the file extension \".conf\" will be combined to generate the configuration object which is delivered to the Object Storage service. This is referred to generally as \"directory-based configuration\"."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:74(para)
-msgid "Directory-based configuration leverages ConfigParser's native multi-file support. Files ending in \".conf\" in the given directory are parsed in lexicographical order. File names starting with '.' are ignored. A mixture of file and directory configuration paths is not supported - if the configuration path is a file, only that file will be parsed."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:82(para)
-msgid "The Object Storage service management tool <filename>swift-init</filename> has adopted the convention of looking for <filename>/etc/swift/{type}-server.conf.d/</filename> if the file <filename>/etc/swift/{type}-server.conf</filename> file does not exist."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:90(para)
-msgid "When using directory-based configuration, if the same option under the same section appears more than once in different files, the last value parsed is said to override previous occurrences. You can ensure proper override precedence by prefixing the files in the configuration directory with numerical values, as in the following example file layout:"
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:109(para)
-msgid "You can inspect the resulting combined configuration object using the <placeholder-1/> command-line tool."
-msgstr ""
-
-#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:113(para)
-msgid "All the services of an Object Store deployment share a common configuration in the <literal>[swift-hash]</literal> section of the <filename>/etc/swift/swift.conf</filename> file. The <option>swift_hash_path_suffix</option> and <option>swift_hash_path_prefix</option> values must be identical on all the nodes."
-msgstr ""
-
-#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:6(title)
-msgid "Log files used by the dashboard"
-msgstr ""
-
-#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:7(para)
-msgid "The dashboard is served to users through the Apache web server (<systemitem>httpd</systemitem>). As a result, logs relating to the dashboard appear in the following files in the <filename>/var/log/httpd</filename> or <filename>/var/log/apache2</filename> directory of where the dashboard is hosted."
-msgstr ""
-
-#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:14(caption)
-msgid "Log files used by the dashboard/httpd"
-msgstr ""
-
-#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:30(filename)
-msgid "access_log"
-msgstr ""
-
-#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:32(td)
-msgid "This file logs all attempts to access the web server."
-msgstr ""
-
-#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:38(filename)
-msgid "error_log"
-msgstr ""
-
-#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:40(td)
-msgid "This file logs all unsuccessful attempts to access the web server, along with the reason each attempt/request failed."
-msgstr ""
-
-#: ./doc/config-reference/dashboard/section_dashboard-sample-configuration-files.xml:7(para)
-msgid "Find the following files in <systemitem>/etc/openstack-dashboard</systemitem>."
-msgstr ""
-
-#: ./doc/config-reference/dashboard/section_dashboard-sample-configuration-files.xml:9(title)
-msgid "keystone_policy.json"
-msgstr ""
-
-#: ./doc/config-reference/dashboard/section_dashboard-sample-configuration-files.xml:10(para)
-msgid "The <filename>keystone_policy.json</filename> file defines additional access controls for the dashboard that apply to the Identity service."
-msgstr ""
-
-#: ./doc/config-reference/dashboard/section_dashboard-sample-configuration-files.xml:14(para)
-msgid "The <filename>keystone_policy.json</filename> file must match the Identity service <filename>/etc/keystone/policy.json</filename> policy file."
-msgstr ""
-
-#: ./doc/config-reference/dashboard/section_dashboard-sample-configuration-files.xml:22(title)
-msgid "nova_policy.json"
-msgstr ""
-
-#: ./doc/config-reference/dashboard/section_dashboard-sample-configuration-files.xml:23(para)
-msgid "The <filename>nova_policy.json</filename> file defines additional access controls for the dashboard that apply to the Compute service."
-msgstr ""
-
-#: ./doc/config-reference/dashboard/section_dashboard-sample-configuration-files.xml:27(para)
-msgid "The <filename>nova_policy.json</filename> file must match the Compute <filename>/etc/nova/policy.json</filename> policy file."
-msgstr ""
-
-#: ./doc/config-reference/identity/section_keystone-sample-conf-files.xml:6(title)
-msgid "Identity service sample configuration files"
-msgstr ""
-
-#: ./doc/config-reference/identity/section_keystone-sample-conf-files.xml:7(para)
-msgid "All the files in this section can be found in the <systemitem>/etc/keystone</systemitem> directory."
-msgstr ""
-
-#: ./doc/config-reference/identity/section_keystone-sample-conf-files.xml:10(title)
-msgid "keystone.conf"
-msgstr ""
-
-#: ./doc/config-reference/identity/section_keystone-sample-conf-files.xml:11(para)
-msgid "The majority of the Identity service configuration is performed from the <filename>keystone.conf</filename> file."
-msgstr ""
-
-#: ./doc/config-reference/identity/section_keystone-sample-conf-files.xml:19(title)
-msgid "keystone-paste.ini"
-msgstr ""
-
-#: ./doc/config-reference/identity/section_keystone-sample-conf-files.xml:20(para)
-msgid "The <filename>keystone-paste.ini</filename> file configures the Web Service Gateway Interface (WSGI) middleware pipeline for the Identity service."
-msgstr ""
-
-#: ./doc/config-reference/identity/section_keystone-sample-conf-files.xml:30(title)
-msgid "logging.conf"
-msgstr ""
-
-#: ./doc/config-reference/identity/section_keystone-sample-conf-files.xml:31(para)
-msgid "A special logging configuration file can be specified in the <filename>keystone.conf</filename> configuration file (for example, <filename>/etc/keystone/logging.conf</filename>). For details, see the Python logging module documentation ( <link href=\"http://docs.python.org/2/howto/logging.html#configuring-logging\">Python Logging</link>)."
-msgstr ""
-
-#: ./doc/config-reference/identity/section_keystone-sample-conf-files.xml:43(para)
-msgid "The <filename>policy.json</filename> file defines additional access controls that apply to the Identity service."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:4(title)
-msgid "Image Service sample configuration files"
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:5(para)
-msgid "All the files in this section can be found in the <filename class=\"directory\">/etc/glance/</filename> directory."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:8(title)
-msgid "glance-api.conf"
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:9(para)
-msgid "The configuration file for the Image Service API is found in the <filename>glance-api.conf</filename> file."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:15(title)
-msgid "glance-registry.conf"
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:16(para)
-msgid "Configuration for the Image Service's registry, which stores the metadata about images, is found in the <filename>glance-registry.conf</filename> file."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:23(title)
-msgid "glance-api-paste.ini"
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:24(para)
-msgid "Configuration for the Image Service's API middleware pipeline is found in the <filename>glance-api-paste.ini</filename> file."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:30(title)
-msgid "glance-registry-paste.ini"
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:31(para)
-msgid "The Image Service's middleware pipeline for its registry is found in the <filename>glance-registry-paste.ini</filename> file."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:36(title)
-msgid "glance-scrubber.conf"
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:37(para)
-msgid "<placeholder-1/> is a utility for the Image Service that cleans up images that have been deleted; its configuration is stored in the <filename>glance-scrubber.conf</filename> file."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:40(para)
-msgid "Multiple instances of <systemitem>glance-scrubber</systemitem> can be run in a single deployment, but only one of them can be designated as the <systemitem>cleanup_scrubber</systemitem> in the <filename>glance-scrubber.conf</filename> file. The <systemitem>cleanup_scrubber</systemitem> coordinates other <systemitem>glance-scrubber</systemitem> instances by maintaining the master queue of images that need to be removed."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-sample-configuration-files.xml:51(para)
-msgid "The <filename>/etc/glance/policy.json</filename> file defines additional access controls that apply to the Image Service."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-ISO-support.xml:5(title)
-msgid "Support for ISO images"
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-ISO-support.xml:6(para)
-msgid "You can load ISO images into the Image Service. You can subsequently boot an ISO image using Compute."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-ISO-support.xml:9(title)
-msgid "To load an ISO image to an Image Service data store"
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-ISO-support.xml:12(para)
-msgid "Obtain the ISO image. For example, <filename>ubuntu-13.04-server-amd64.iso</filename>."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-ISO-support.xml:16(para)
-msgid "In the Image Service, run the following command:"
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-ISO-support.xml:21(para)
-msgid "In this command, <literal>ubuntu.iso</literal> is the name for the ISO image after it is loaded to the Image Service, and <literal>ubuntu-13.04-server-amd64.iso</literal> is the name of the source ISO image."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-ISO-support.xml:28(para)
-msgid "Optionally, confirm the upload in Compute."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-ISO-support.xml:29(para) ./doc/config-reference/image-service/section_image-service-ISO-support.xml:36(para)
-msgid "Run this command:"
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-ISO-support.xml:34(title)
-msgid "To boot an instance from an ISO image"
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-ISO-support.xml:39(para)
-msgid "In this command, <literal>ubuntu.iso</literal> is the ISO image, and <literal>instance_name</literal> is the name of the new instance."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-rpc.xml:7(para)
-msgid "OpenStack projects use an open standard for messaging middleware known as AMQP. This messaging middleware enables the OpenStack services that run on multiple servers to talk to each other. The OpenStack common library project, oslo, supports three implementations of AMQP: <application>RabbitMQ</application>, <application>Qpid</application>, and <application>ZeroMQ</application>."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-rpc.xml:14(para)
-msgid "The following tables contain settings to configure the messaging middleware for the Image Service:"
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:6(title)
-msgid "Configure vCenter data stores for the Image Service back end"
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:9(para)
-msgid "To use vCenter data stores for the Image Service back end, you must update the <filename>glance-api.conf</filename> file, as follows:"
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:14(para)
-msgid "Add data store parameters to the <literal>VMware Datastore Store Options</literal> section."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:18(para)
-msgid "Specify vSphere as the back end."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:22(para)
-msgid "You must configure any configured Image Service data stores for the Compute service."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:29(para)
-msgid "If you intend to use multiple data stores for the back end, use the SPBM feature."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:25(para)
-msgid "You can specify vCenter data stores directly by using the data store name or Storage Policy Based Management (SPBM), which requires vCenter Server 5.5 or later. For details, see <xref linkend=\"glance-backend-DS\"/>. <placeholder-1/>"
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:32(para)
-msgid "In the <literal>DEFAULT</literal> section, set the <parameter>default_store</parameter> parameter to <placeholder-1/>, as shown in this code sample:"
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:42(para)
-msgid "The following table describes the parameters in the <literal>VMware Datastore Store Options</literal> section:"
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:46(para)
-msgid "The following block of text shows a sample configuration:"
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:55(replaceable)
-msgid "ADMINISTRATOR"
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:63(replaceable)
-msgid "DATACENTER"
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:66(replaceable)
-msgid "datastore1"
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:81(replaceable)
-msgid "5"
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:85(replaceable)
-msgid "/openstack_glance"
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:90(title)
-msgid "Configure vCenter data stores for the back end"
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:91(para)
-msgid "You can specify a vCenter data store for the back end by setting the <parameter>vmware_datastore_name</parameter> parameter value to the vCenter name of the data store. This configuration limits the back end to a single data store."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:96(para)
-msgid "Alternatively, you can specify a SPBM policy, which can comprise multiple vCenter data stores. Both approaches are described."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:100(para)
-msgid "SPBM requires vCenter Server 5.5 or later."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:103(title)
-msgid "To configure a single data store"
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:105(para)
-msgid "If present, comment or delete the <parameter>vmware_pbm_wsdl_location</parameter> and <parameter>vmware_pbm_policy</parameter> parameters."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:111(para)
-msgid "Uncomment and define the <parameter>vmware_datastore_name</parameter> parameter with the name of the vCenter data store."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:122(title)
-msgid "To configure multiple data stores using SPBM"
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:125(para)
-msgid "In vCenter, use tagging to identify the data stores and define a storage policy:"
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:129(para)
-msgid "Create the tag."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:136(para)
-msgid "Create a tag-based storage policy that uses one or more tags to identify a set of data stores."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:146(para)
-msgid "For details about storage policies in vSphere, see the <link href=\"http://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.vsphere.storage.doc/GUID-A8BA9141-31F1-4555-A554-4B5B04D75E54.html\">vSphere documentation</link>."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:153(para)
-msgid "Return to the <filename>glance-api.conf</filename> file."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:158(para)
-msgid "Comment or delete the <parameter>vmware_datastore_name</parameter> parameter."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:163(para)
-msgid "Uncomment and define the <parameter>vmware_pbm_policy</parameter> parameter by entering the same value as the tag you defined and applied to the data stores in vCenter."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:170(para)
-msgid "Uncomment and define the <parameter>vmware_pbm_wsdl_location</parameter> parameter by entering the location of the PBM service WSDL file. For example, <filename>file:///opt/SDK/spbm/wsdl/pbmService.wsdl</filename>."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:176(para)
-msgid "If you do not set this parameter, the storage policy cannot be used to place images in the data store."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backends.xml:6(title)
-msgid "Configuring Backends"
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-backends.xml:7(para)
-msgid "The image service supports several different backends for storing virtual machine images, including Cinder, a directory on a local file system, GridFS, Ceph RBD, Amazon S3, Sheepdog, OpenStack Object Storage or VMWare ESX. The following tables detail the options available for each."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-api.xml:6(title)
-msgid "Configure the API"
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-api.xml:7(para)
-msgid "The Image Service has two APIs: the user-facing API, and the registry API, which is for internal requests that require access to the database."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-api.xml:10(para)
-msgid "Both of the APIs currently have two major versions, v1 and v2. It is possible to run either or both version, by setting appropriate values of <literal>enable_v1_api</literal>, <literal>enable_v2_api</literal>, <literal>enable_v1_registry</literal> and <literal>enable_v2_registry</literal>. If the v2 API is used, running <systemitem class=\"service\">glance-registry</systemitem> is optional, as v2 of <systemitem class=\"service\">glance-api</systemitem> can connect directly to the database."
-msgstr ""
-
-#: ./doc/config-reference/image-service/section_image-service-api.xml:18(para)
-msgid "Tables of all options used to configure the APIs, including enabling SSL and modifying WSGI settings are found below."
+#: ./doc/config-reference/compute/section_compute-configure-xen.xml:71(para)
+msgid "To customize the Xen driver, use the configuration option settings documented in <xref linkend=\"config_table_nova_xen\"/>."
 msgstr ""
 
 #. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
-#: ./doc/config-reference/image-service/section_image-service-api.xml:0(None)
+#: ./doc/config-reference/compute/section_compute-configure-xen.xml:0(None)
 msgid "translator-credits"
 msgstr ""
 
diff --git a/doc/glossary/locale/glossary.pot b/doc/glossary/locale/glossary.pot
index 0b547dc4ff..d784b8e447 100644
--- a/doc/glossary/locale/glossary.pot
+++ b/doc/glossary/locale/glossary.pot
@@ -1,7 +1,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2014-05-30 06:09+0000\n"
+"POT-Creation-Date: 2014-06-03 06:11+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -9,6 +9,18 @@ msgstr ""
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
+#: ./doc/glossary/openstack-glossary.xml:7(title) ./doc/glossary/openstack-glossary.xml:10(title)
+msgid "OpenStack glossary"
+msgstr ""
+
+#: ./doc/glossary/openstack-glossary.xml:11(para)
+msgid "Use this glossary to get definitions of OpenStack-related words and phrases."
+msgstr ""
+
+#: ./doc/glossary/openstack-glossary.xml:13(para)
+msgid "To add to this glossary, fork the <literal>openstack-manuals</literal> repository on github.com and update the source files through the OpenStack contribution process."
+msgstr ""
+
 #: ./doc/glossary/glossary-terms.xml:10(title)
 msgid "Glossary"
 msgstr ""
@@ -7633,20 +7645,8 @@ msgstr ""
 msgid "Tool used in OpenStack development to ensure correctly ordered testing of changes in parallel."
 msgstr ""
 
-#: ./doc/glossary/openstack-glossary.xml:7(title) ./doc/glossary/openstack-glossary.xml:10(title)
-msgid "OpenStack glossary"
-msgstr ""
-
-#: ./doc/glossary/openstack-glossary.xml:11(para)
-msgid "Use this glossary to get definitions of OpenStack-related words and phrases."
-msgstr ""
-
-#: ./doc/glossary/openstack-glossary.xml:13(para)
-msgid "To add to this glossary, fork the <literal>openstack-manuals</literal> repository on github.com and update the source files through the OpenStack contribution process."
-msgstr ""
-
 #. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
-#: ./doc/glossary/openstack-glossary.xml:0(None)
+#: ./doc/glossary/glossary-terms.xml:0(None)
 msgid "translator-credits"
 msgstr ""
 
diff --git a/doc/high-availability-guide/locale/high-availability-guide.pot b/doc/high-availability-guide/locale/high-availability-guide.pot
index c4e2b3e6e8..e11265b684 100644
--- a/doc/high-availability-guide/locale/high-availability-guide.pot
+++ b/doc/high-availability-guide/locale/high-availability-guide.pot
@@ -1,7 +1,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2014-06-02 06:10+0000\n"
+"POT-Creation-Date: 2014-06-03 06:11+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -9,24 +9,12 @@ msgstr ""
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
-#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml:6(title)
-msgid "OpenStack controller nodes"
+#: ./doc/high-availability-guide/ch_controller.xml:6(title)
+msgid "Cloud controller cluster stack"
 msgstr ""
 
-#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml:8(simpara)
-msgid "OpenStack controller nodes contain:"
-msgstr ""
-
-#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml:11(simpara)
-msgid "All OpenStack API services"
-msgstr ""
-
-#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml:16(simpara)
-msgid "All OpenStack schedulers"
-msgstr ""
-
-#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml:21(simpara)
-msgid "Memcached service"
+#: ./doc/high-availability-guide/ch_controller.xml:8(simpara)
+msgid "The cloud controller runs on the management network and must talk to all other services."
 msgstr ""
 
 #: ./doc/high-availability-guide/ch_ha_aa_network.xml:6(title)
@@ -61,26 +49,6 @@ msgstr ""
 msgid "The neutron L2 agent does not need to be highly available. It has to be installed on each Data Forwarding Node and controls the virtual networking drivers as Open vSwitch or Linux Bridge. One L2 agent runs per node and controls its virtual interfaces. That’s why it cannot be distributed and highly available."
 msgstr ""
 
-#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml:6(title)
-msgid "HAproxy nodes"
-msgstr ""
-
-#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml:8(simpara)
-msgid "HAProxy is a very fast and reliable solution offering high availability, load balancing, and proxying for TCP and HTTP-based applications. It is particularly suited for web sites crawling under very high loads while needing persistence or Layer 7 processing. Supporting tens of thousands of connections is clearly realistic with today’s hardware."
-msgstr ""
-
-#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml:12(simpara)
-msgid "For installing HAproxy on your nodes, you should consider its <link href=\"http://haproxy.1wt.eu/#docs\">official documentation</link>. Also, you have to consider that this service should not be a single point of failure, so you need at least two nodes running HAproxy."
-msgstr ""
-
-#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml:15(simpara)
-msgid "Here is an example for HAproxy configuration file:"
-msgstr ""
-
-#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml:155(simpara)
-msgid "After each change of this file, you should restart HAproxy."
-msgstr ""
-
 #: ./doc/high-availability-guide/ch_pacemaker.xml:6(title)
 msgid "The Pacemaker cluster stack"
 msgstr ""
@@ -97,10 +65,6 @@ msgstr ""
 msgid "Pacemaker interacts with applications through <emphasis>resource agents</emphasis> (RAs), of which it supports over 70 natively. Pacemaker can also easily use third-party RAs. An OpenStack high-availability configuration uses existing native Pacemaker RAs (such as those managing MySQL databases or virtual IP addresses), existing third-party RAs (such as for RabbitMQ), and native OpenStack RAs (such as those managing the OpenStack Identity and Image Services)."
 msgstr ""
 
-#: ./doc/high-availability-guide/part_active_passive.xml:6(title)
-msgid "HA using active/passive"
-msgstr ""
-
 #: ./doc/high-availability-guide/ch_ha_aa_rabbitmq.xml:6(title)
 msgid "RabbitMQ"
 msgstr ""
@@ -121,98 +85,6 @@ msgstr ""
 msgid "Configure OpenStack services to use Rabbit HA queues"
 msgstr ""
 
-#: ./doc/high-availability-guide/bk-ha-guide.xml:8(title)
-msgid "OpenStack High Availability Guide"
-msgstr ""
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml:11(firstname)
-msgid "Florian"
-msgstr ""
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml:12(surname)
-msgid "Haas"
-msgstr ""
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml:14(email)
-msgid "florian@hastexo.com"
-msgstr ""
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml:16(orgname)
-msgid "hastexo"
-msgstr ""
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml:20(year)
-msgid "2012"
-msgstr ""
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml:21(year)
-msgid "2013"
-msgstr ""
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml:22(year)
-msgid "2014"
-msgstr ""
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml:23(holder)
-msgid "OpenStack Contributors"
-msgstr ""
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml:25(releaseinfo)
-msgid "current"
-msgstr ""
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml:26(productname)
-msgid "OpenStack"
-msgstr ""
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml:30(remark)
-msgid "Copyright details are filled in by the template."
-msgstr ""
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml:34(para)
-msgid "This guide describes how to install, configure, and manage OpenStack for high availability."
-msgstr ""
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml:39(date)
-msgid "2014-05-16"
-msgstr ""
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml:43(para)
-msgid "Conversion to Docbook."
-msgstr ""
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml:49(date)
-msgid "2014-04-17"
-msgstr ""
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml:53(para)
-msgid "Minor cleanup of typos, otherwise no major revisions for Icehouse release."
-msgstr ""
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml:60(date)
-msgid "2012-01-16"
-msgstr ""
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml:64(para)
-msgid "Organizes guide based on cloud controller and compute nodes."
-msgstr ""
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml:70(date)
-msgid "2012-05-24"
-msgstr ""
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml:74(para)
-msgid "Begin trunk designation."
-msgstr ""
-
-#: ./doc/high-availability-guide/ch_controller.xml:6(title)
-msgid "Cloud controller cluster stack"
-msgstr ""
-
-#: ./doc/high-availability-guide/ch_controller.xml:8(simpara)
-msgid "The cloud controller runs on the management network and must talk to all other services."
-msgstr ""
-
 #: ./doc/high-availability-guide/ch_intro.xml:6(title)
 msgid "Introduction to OpenStack High Availability"
 msgstr ""
@@ -321,6 +193,90 @@ msgstr ""
 msgid "These are some of the more common ways to implement these high availability architectures, but they are by no means the only ways to do it. The important thing is to make sure that your services are redundant, and available; how you achieve that is up to you. This document will cover some of the more common options for highly available systems."
 msgstr ""
 
+#: ./doc/high-availability-guide/bk-ha-guide.xml:8(title)
+msgid "OpenStack High Availability Guide"
+msgstr ""
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml:11(firstname)
+msgid "Florian"
+msgstr ""
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml:12(surname)
+msgid "Haas"
+msgstr ""
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml:14(email)
+msgid "florian@hastexo.com"
+msgstr ""
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml:16(orgname)
+msgid "hastexo"
+msgstr ""
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml:20(year)
+msgid "2012"
+msgstr ""
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml:21(year)
+msgid "2013"
+msgstr ""
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml:22(year)
+msgid "2014"
+msgstr ""
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml:23(holder)
+msgid "OpenStack Contributors"
+msgstr ""
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml:25(releaseinfo)
+msgid "current"
+msgstr ""
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml:26(productname)
+msgid "OpenStack"
+msgstr ""
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml:30(remark)
+msgid "Copyright details are filled in by the template."
+msgstr ""
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml:34(para)
+msgid "This guide describes how to install, configure, and manage OpenStack for high availability."
+msgstr ""
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml:39(date)
+msgid "2014-05-16"
+msgstr ""
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml:43(para)
+msgid "Conversion to Docbook."
+msgstr ""
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml:49(date)
+msgid "2014-04-17"
+msgstr ""
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml:53(para)
+msgid "Minor cleanup of typos, otherwise no major revisions for Icehouse release."
+msgstr ""
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml:60(date)
+msgid "2012-01-16"
+msgstr ""
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml:64(para)
+msgid "Organizes guide based on cloud controller and compute nodes."
+msgstr ""
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml:70(date)
+msgid "2012-05-24"
+msgstr ""
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml:74(para)
+msgid "Begin trunk designation."
+msgstr ""
+
 #: ./doc/high-availability-guide/ch_network.xml:6(title)
 msgid "Network controller cluster stack"
 msgstr ""
@@ -333,8 +289,48 @@ msgstr ""
 msgid "Both nodes should have the same hostname since the Networking scheduler will be aware of one node, for example a virtual router attached to a single L3 node."
 msgstr ""
 
-#: ./doc/high-availability-guide/part_active_active.xml:6(title)
-msgid "HA using active/active"
+#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml:6(title)
+msgid "HAproxy nodes"
+msgstr ""
+
+#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml:8(simpara)
+msgid "HAProxy is a very fast and reliable solution offering high availability, load balancing, and proxying for TCP and HTTP-based applications. It is particularly suited for web sites crawling under very high loads while needing persistence or Layer 7 processing. Supporting tens of thousands of connections is clearly realistic with today’s hardware."
+msgstr ""
+
+#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml:12(simpara)
+msgid "For installing HAproxy on your nodes, you should consider its <link href=\"http://haproxy.1wt.eu/#docs\">official documentation</link>. Also, you have to consider that this service should not be a single point of failure, so you need at least two nodes running HAproxy."
+msgstr ""
+
+#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml:15(simpara)
+msgid "Here is an example for HAproxy configuration file:"
+msgstr ""
+
+#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml:155(simpara)
+msgid "After each change of this file, you should restart HAproxy."
+msgstr ""
+
+#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml:6(title)
+msgid "OpenStack controller nodes"
+msgstr ""
+
+#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml:8(simpara)
+msgid "OpenStack controller nodes contain:"
+msgstr ""
+
+#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml:11(simpara)
+msgid "All OpenStack API services"
+msgstr ""
+
+#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml:16(simpara)
+msgid "All OpenStack schedulers"
+msgstr ""
+
+#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml:21(simpara)
+msgid "Memcached service"
+msgstr ""
+
+#: ./doc/high-availability-guide/part_active_passive.xml:6(title)
+msgid "HA using active/passive"
 msgstr ""
 
 #: ./doc/high-availability-guide/ch_api.xml:6(title)
@@ -357,868 +353,8 @@ msgstr ""
 msgid "The choice of database isn’t a foregone conclusion; you’re not required to use MySQL. It is, however, a fairly common choice in OpenStack installations, so we’ll cover it here."
 msgstr ""
 
-#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml:6(title)
-msgid "Starting Corosync"
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml:8(simpara)
-msgid "Corosync is started as a regular system service. Depending on your distribution, it may ship with a LSB (System V style) init script, an upstart job, or a systemd unit file. Either way, the service is usually named <literal>corosync</literal>:"
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml:14(simpara)
-msgid "<literal>/etc/init.d/corosync start</literal> (LSB)"
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml:18(simpara)
-msgid "<literal>service corosync start</literal> (LSB, alternate)"
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml:22(simpara)
-msgid "<literal>start corosync</literal> (upstart)"
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml:26(simpara)
-msgid "<literal>systemctl start corosync</literal> (systemd)"
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml:30(simpara)
-msgid "You can now check the Corosync connectivity with two tools."
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml:31(simpara)
-msgid "The <literal>corosync-cfgtool</literal> utility, when invoked with the <literal>-s</literal> option, gives a summary of the health of the communication rings:"
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml:42(simpara)
-msgid "The <literal>corosync-objctl</literal> utility can be used to dump the Corosync cluster member list:"
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml:51(simpara)
-msgid "You should see a <literal>status=joined</literal> entry for each of your constituent cluster nodes."
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml:6(title)
-msgid "Set up Corosync"
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml:8(simpara)
-msgid "Besides installing the <literal>corosync</literal> package, you must also create a configuration file, stored in <literal>/etc/corosync/corosync.conf</literal>. Most distributions ship an example configuration file (<literal>corosync.conf.example</literal>) as part of the documentation bundled with the <literal>corosync</literal> package. An example Corosync configuration file is shown below:"
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml:16(title)
-msgid "Corosync configuration file (<literal>corosync.conf</literal>)"
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml:90(para)
-msgid "The <literal>token</literal> value specifies the time, in milliseconds, during which the Corosync token is expected to be transmitted around the ring. When this timeout expires, the token is declared lost, and after <literal>token_retransmits_before_loss_const</literal> lost tokens the non-responding <emphasis>processor</emphasis> (cluster node) is declared dead. In other words, <literal>token</literal> × <literal>token_retransmits_before_loss_const</literal> is the maximum time a node is allowed to not respond to cluster messages before being considered dead. The default for <literal>token</literal> is 1000 (1 second), with 4 allowed retransmits. These defaults are intended to minimize failover times, but can cause frequent \"false alarms\" and unintended failovers in case of short network interruptions. The values used here are safer, albeit with slightly extended failover times."
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml:106(para)
-msgid "With <literal>secauth</literal> enabled, Corosync nodes mutually authenticate using a 128-byte shared secret stored in <literal>/etc/corosync/authkey</literal>, which may be generated with the <literal>corosync-keygen</literal> utility. When using <literal>secauth</literal>, cluster communications are also encrypted."
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml:114(para)
-msgid "In Corosync configurations using redundant networking (with more than one <literal>interface</literal>), you must select a Redundant Ring Protocol (RRP) mode other than <literal>none</literal>. <literal>active</literal> is the recommended RRP mode."
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml:121(para)
-msgid "There are several things to note about the recommended interface configuration:"
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml:127(simpara)
-msgid "The <literal>ringnumber</literal> must differ between all configured interfaces, starting with 0."
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml:133(simpara)
-msgid "The <literal>bindnetaddr</literal> is the <emphasis>network</emphasis> address of the interfaces to bind to. The example uses two network addresses of <literal>/24</literal> IPv4 subnets."
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml:139(simpara)
-msgid "Multicast groups (<literal>mcastaddr</literal>) <emphasis>must not</emphasis> be reused across cluster boundaries. In other words, no two distinct clusters should ever use the same multicast group. Be sure to select multicast addresses compliant with <link href=\"http://www.ietf.org/rfc/rfc2365.txt\">RFC 2365, \"Administratively Scoped IP Multicast\"</link>."
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml:148(simpara)
-msgid "For firewall configurations, note that Corosync communicates over UDP only, and uses <literal>mcastport</literal> (for receives) and <literal>mcastport</literal>-1 (for sends)."
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml:157(para)
-msgid "The <literal>service</literal> declaration for the <literal>pacemaker</literal> service may be placed in the <literal>corosync.conf</literal> file directly, or in its own separate file, <literal>/etc/corosync/service.d/pacemaker</literal>."
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml:164(simpara)
-msgid "Once created, the <literal>corosync.conf</literal> file (and the <literal>authkey</literal> file if the <literal>secauth</literal> option is enabled) must be synchronized across all cluster nodes."
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_set_basic_cluster_properties.xml:6(title)
-msgid "Set basic cluster properties"
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_set_basic_cluster_properties.xml:8(simpara)
-msgid "Once your Pacemaker cluster is set up, it is recommended to set a few basic cluster properties. To do so, start the <literal>crm</literal> shell and change into the configuration menu by entering <literal>configure</literal>. Alternatively. you may jump straight into the Pacemaker configuration menu by typing <literal>crm configure</literal> directly from a shell prompt."
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_set_basic_cluster_properties.xml:14(simpara)
-msgid "Then, set the following properties:"
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_set_basic_cluster_properties.xml:22(para)
-msgid "Setting <literal>no-quorum-policy=\"ignore\"</literal> is required in 2-node Pacemaker clusters for the following reason: if quorum enforcement is enabled, and one of the two nodes fails, then the remaining node can not establish a <emphasis>majority</emphasis> of quorum votes necessary to run services, and thus it is unable to take over any resources. The appropriate workaround is to ignore loss of quorum in the cluster. This is safe and necessary <emphasis>only</emphasis> in 2-node clusters. Do not set this property in Pacemaker clusters with more than two nodes."
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_set_basic_cluster_properties.xml:34(para)
-msgid "Setting <literal>pe-warn-series-max</literal>, <literal>pe-input-series-max</literal> and <literal>pe-error-series-max</literal> to 1000 instructs Pacemaker to keep a longer history of the inputs processed, and errors and warnings generated, by its Policy Engine. This history is typically useful in case cluster troubleshooting becomes necessary."
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_set_basic_cluster_properties.xml:43(para)
-msgid "Pacemaker uses an event-driven approach to cluster state processing. However, certain Pacemaker actions occur at a configurable interval, <literal>cluster-recheck-interval</literal>, which defaults to 15 minutes. It is usually prudent to reduce this to a shorter interval, such as 5 or 3 minutes."
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_set_basic_cluster_properties.xml:52(simpara)
-msgid "Once you have made these changes, you may <literal>commit</literal> the updated configuration."
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml:6(title)
-msgid "Install packages"
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml:8(simpara)
-msgid "On any host that is meant to be part of a Pacemaker cluster, you must first establish cluster communications through the Corosync messaging layer. This involves Install the following packages (and their dependencies, which your package manager will normally install automatically):"
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml:15(simpara)
-msgid "<literal>pacemaker</literal> Note that the crm shell should be downloaded separately."
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml:20(literal)
-msgid "crmsh"
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml:25(literal)
-msgid "corosync"
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml:30(literal)
-msgid "cluster-glue"
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml:34(simpara)
-msgid "<literal>fence-agents</literal> (Fedora only; all other distributions use fencing agents from <literal>cluster-glue</literal>)"
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml:40(literal)
-msgid "resource-agents"
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_start_pacemaker.xml:6(title)
-msgid "Start Pacemaker"
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_start_pacemaker.xml:8(simpara)
-msgid "Once the Corosync services have been started, and you have established that the cluster is communicating properly, it is safe to start <literal>pacemakerd</literal>, the Pacemaker master control process:"
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_start_pacemaker.xml:13(simpara)
-msgid "<literal>/etc/init.d/pacemaker start</literal> (LSB)"
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_start_pacemaker.xml:17(simpara)
-msgid "<literal>service pacemaker start</literal> (LSB, alternate)"
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_start_pacemaker.xml:21(simpara)
-msgid "<literal>start pacemaker</literal> (upstart)"
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_start_pacemaker.xml:25(simpara)
-msgid "<literal>systemctl start pacemaker</literal> (systemd)"
-msgstr ""
-
-#: ./doc/high-availability-guide/pacemaker/section_start_pacemaker.xml:29(simpara)
-msgid "Once Pacemaker services have started, Pacemaker will create a default empty cluster configuration with no resources. You may observe Pacemaker’s status with the <literal>crm_mon</literal> utility:"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_keystone.xml:6(title)
-msgid "Highly available OpenStack Identity"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_keystone.xml:8(simpara)
-msgid "OpenStack Identity is the Identity Service in OpenStack and used by many services. Making the OpenStack Identity service highly available in active / passive mode involves"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_keystone.xml:12(simpara)
-msgid "Configure OpenStack Identity to listen on the VIP address,"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_keystone.xml:17(simpara)
-msgid "managing OpenStack Identity daemon with the Pacemaker cluster manager,"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_keystone.xml:22(simpara) ./doc/high-availability-guide/api/section_cinder_api.xml:21(simpara) ./doc/high-availability-guide/api/section_neutron_server.xml:22(simpara) ./doc/high-availability-guide/api/section_glance_api.xml:22(simpara)
-msgid "Configure OpenStack services to use this IP address."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_keystone.xml:28(simpara)
-msgid "Here is the <link href=\"http://docs.openstack.org/trunk/install-guide/install/apt/content/ch_installing-openstack-identity-service.html\">documentation</link> for installing OpenStack Identity service."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_keystone.xml:32(title)
-msgid "Add OpenStack Identity resource to Pacemaker"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_keystone.xml:34(simpara) ./doc/high-availability-guide/api/section_cinder_api.xml:35(simpara) ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml:26(simpara) ./doc/high-availability-guide/api/section_neutron_server.xml:34(simpara) ./doc/high-availability-guide/api/section_glance_api.xml:34(simpara) ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml:18(simpara) ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml:18(simpara) ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml:18(simpara)
-msgid "First of all, you need to download the resource agent to your system:"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_keystone.xml:40(simpara)
-msgid "You can now add the Pacemaker configuration for OpenStack Identity resource. Connect to the Pacemaker cluster with <literal>crm configure</literal>, and add the following cluster resources:"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_keystone.xml:46(simpara)
-msgid "This configuration creates <literal>p_keystone</literal>, a resource for managing the OpenStack Identity service."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_keystone.xml:47(simpara)
-msgid "<literal>crm configure</literal> supports batch input, so you may copy and paste the above into your live pacemaker configuration, and then make changes as required. For example, you may enter <literal>edit p_ip_keystone</literal> from the <literal>crm configure</literal> menu and edit the resource to match your preferred virtual IP address."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_keystone.xml:52(simpara)
-msgid "Once completed, commit your configuration changes by entering <literal>commit</literal> from the <literal>crm configure</literal> menu. Pacemaker will then start the OpenStack Identity service, and its dependent resources, on one of your nodes."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_keystone.xml:58(title)
-msgid "Configure OpenStack Identity service"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_keystone.xml:60(simpara)
-msgid "You need to edit your OpenStack Identity configuration file (<literal>keystone.conf</literal>) and change the bind parameters:"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_keystone.xml:61(simpara)
-msgid "On Havana:"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_keystone.xml:63(simpara)
-msgid "On Icehouse, the <literal>admin_bind_host</literal> option lets you use a private network for the admin access."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_keystone.xml:66(simpara)
-msgid "To be sure all data will be highly available, you should be sure that you store everything in the MySQL database (which is also highly available):"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_keystone.xml:76(title)
-msgid "Configure OpenStack services to use the highly available OpenStack Identity"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_keystone.xml:78(simpara)
-msgid "Your OpenStack services must now point their OpenStack Identity configuration to the highly available, virtual cluster IP address — rather than a OpenStack Identity server’s physical IP address as you normally would."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_keystone.xml:81(simpara)
-msgid "For example with OpenStack Compute, if your OpenStack Identity service IP address is 192.168.42.103 as in the configuration explained here, you would use the following line in your API configuration file (<literal>api-paste.ini</literal>):"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_keystone.xml:86(simpara)
-msgid "You also need to create the OpenStack Identity Endpoint with this IP."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_keystone.xml:87(simpara)
-msgid "NOTE : If you are using both private and public IP addresses, you should create two Virtual IP addresses and define your endpoint like this:"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_keystone.xml:89(simpara)
-msgid "If you are using the horizon dashboard, you should edit the <literal>local_settings.py</literal> file:"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_api_vip.xml:6(title)
-msgid "Configure the VIP"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_api_vip.xml:8(simpara)
-msgid "First, you must select and assign a virtual IP address (VIP) that can freely float between cluster nodes."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_api_vip.xml:9(simpara)
-msgid "This configuration creates <literal>p_ip_api</literal>, a virtual IP address for use by the API node (192.168.42.103) :"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml:6(title)
-msgid "Highly available Block Storage API"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml:8(simpara)
-msgid "Making the Block Storage (cinder) API service highly available in active / passive mode involves"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml:11(simpara)
-msgid "Configure Block Storage to listen on the VIP address,"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml:16(simpara)
-msgid "managing Block Storage API daemon with the Pacemaker cluster manager,"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml:27(simpara)
-msgid "Here is the <link href=\"http://docs.openstack.org/trunk/install-guide/install/apt/content/ch_cinder.html\">documentation</link> for installing Block Storage service."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml:33(title)
-msgid "Add Block Storage API resource to Pacemaker"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml:39(simpara)
-msgid "You can now add the Pacemaker configuration for Block Storage API resource. Connect to the Pacemaker cluster with <literal>crm configure</literal>, and add the following cluster resources:"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml:46(simpara) ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml:36(simpara) ./doc/high-availability-guide/api/section_glance_api.xml:44(simpara) ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml:29(simpara) ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml:29(simpara) ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml:29(simpara) ./doc/high-availability-guide/controller/section_mysql.xml:197(simpara) ./doc/high-availability-guide/controller/section_rabbitmq.xml:185(simpara)
-msgid "This configuration creates"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml:49(simpara)
-msgid "<literal>p_cinder-api</literal>, a resource for manage Block Storage API service"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml:53(simpara)
-msgid "<literal>crm configure</literal> supports batch input, so you may copy and paste the above into your live pacemaker configuration, and then make changes as required. For example, you may enter <literal>edit p_ip_cinder-api</literal> from the <literal>crm configure</literal> menu and edit the resource to match your preferred virtual IP address."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml:58(simpara)
-msgid "Once completed, commit your configuration changes by entering <literal>commit</literal> from the <literal>crm configure</literal> menu. Pacemaker will then start the Block Storage API service, and its dependent resources, on one of your nodes."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml:64(title)
-msgid "Configure Block Storage API service"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml:66(simpara)
-msgid "Edit <literal>/etc/cinder/cinder.conf</literal>:"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml:79(title)
-msgid "Configure OpenStack services to use highly available Block Storage API"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml:81(simpara)
-msgid "Your OpenStack services must now point their Block Storage API configuration to the highly available, virtual cluster IP address — rather than a Block Storage API server’s physical IP address as you normally would."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml:84(simpara)
-msgid "You must create the Block Storage API endpoint with this IP."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml:86(simpara)
-msgid "If you are using both private and public IP, you should create two Virtual IPs and define your endpoint like this:"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml:6(title)
-msgid "Highly available Telemetry central agent"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml:8(simpara)
-msgid "Telemetry (ceilometer) is the metering and monitoring service in OpenStack. The Central agent polls for resource utilization statistics for resources not tied to instances or compute nodes."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml:12(simpara)
-msgid "Due to limitations of a polling model, a single instance of this agent can be polling a given list of meters. In this setup, we install this service on the API nodes also in the active / passive mode."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml:16(simpara)
-msgid "Making the Telemetry central agent service highly available in active / passive mode involves managing its daemon with the Pacemaker cluster manager."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml:19(simpara)
-msgid "You will find at <link href=\"http://docs.openstack.org/developer/ceilometer/install/manual.html#installing-the-central-agent\">this page</link> the process to install the Telemetry central agent."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml:24(title)
-msgid "Add the Telemetry central agent resource to Pacemaker"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml:30(simpara)
-msgid "You may then proceed with adding the Pacemaker configuration for the Telemetry central agent resource. Connect to the Pacemaker cluster with <literal>crm configure</literal>, and add the following cluster resources:"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml:39(simpara)
-msgid "<literal>p_ceilometer-agent-central</literal>, a resource for manage Ceilometer Central Agent service"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml:43(simpara) ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml:36(simpara) ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml:37(simpara) ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml:37(simpara)
-msgid "<literal>crm configure</literal> supports batch input, so you may copy and paste the above into your live pacemaker configuration, and then make changes as required."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml:46(simpara)
-msgid "Once completed, commit your configuration changes by entering <literal>commit</literal> from the <literal>crm configure</literal> menu. Pacemaker will then start the Ceilometer Central Agent service, and its dependent resources, on one of your nodes."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml:52(title)
-msgid "Configure Telemetry central agent service"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml:54(simpara)
-msgid "Edit <literal>/etc/ceilometer/ceilometer.conf</literal> :"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml:6(title)
-msgid "Highly available OpenStack Networking server"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml:8(simpara)
-msgid "OpenStack Networking is the network connectivity service in OpenStack. Making the OpenStack Networking Server service highly available in active / passive mode involves"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml:12(simpara)
-msgid "Configure OpenStack Networking to listen on the VIP address,"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml:17(simpara)
-msgid "managing OpenStack Networking API Server daemon with the Pacemaker cluster manager,"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml:28(simpara)
-msgid "Here is the <link href=\"http://docs.openstack.org/trunk/install-guide/install/apt/content/ch_installing-openstack-networking.html\">documentation</link> for installing OpenStack Networking service."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml:32(title)
-msgid "Add OpenStack Networking Server resource to Pacemaker"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml:38(simpara)
-msgid "You can now add the Pacemaker configuration for OpenStack Networking Server resource. Connect to the Pacemaker cluster with <literal>crm configure</literal>, and add the following cluster resources:"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml:45(simpara)
-msgid "This configuration creates <literal>p_neutron-server</literal>, a resource for manage OpenStack Networking Server service"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml:46(simpara)
-msgid "<literal>crm configure</literal> supports batch input, so you may copy and paste the above into your live pacemaker configuration, and then make changes as required. For example, you may enter <literal>edit p_neutron-server</literal> from the <literal>crm configure</literal> menu and edit the resource to match your preferred virtual IP address."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml:51(simpara)
-msgid "Once completed, commit your configuration changes by entering <literal>commit</literal> from the <literal>crm configure</literal> menu. Pacemaker will then start the OpenStack Networking API service, and its dependent resources, on one of your nodes."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml:57(title)
-msgid "Configure OpenStack Networking server"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml:59(simpara)
-msgid "Edit <literal>/etc/neutron/neutron.conf</literal> :"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml:76(title)
-msgid "Configure OpenStack services to use highly available OpenStack Networking server"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml:78(simpara)
-msgid "Your OpenStack services must now point their OpenStack Networking Server configuration to the highly available, virtual cluster IP address — rather than an OpenStack Networking server’s physical IP address as you normally would."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml:81(simpara)
-msgid "For example, you should configure OpenStack Compute for using highly available OpenStack Networking server in editing <literal>nova.conf</literal> file:"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml:83(simpara)
-msgid "You need to create the OpenStack Networking server endpoint with this IP."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml:85(simpara) ./doc/high-availability-guide/api/section_glance_api.xml:91(simpara)
-msgid "If you are using both private and public IP addresses, you should create two Virtual IP addresses and define your endpoint like this:"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml:6(title)
-msgid "Highly available OpenStack Image API"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml:8(simpara)
-msgid "OpenStack Image Service offers a service for discovering, registering, and retrieving virtual machine images. To make the OpenStack Image API service highly available in active / passive mode, you must:"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml:12(simpara)
-msgid "Configure OpenStack Image to listen on the VIP address."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml:17(simpara)
-msgid "Manage OpenStack Image API daemon with the Pacemaker cluster manager."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml:28(simpara)
-msgid "Here is the <link href=\"http://docs.openstack.org/trunk/install-guide/install/apt/content/ch_installing-openstack-image.html\">documentation</link> for installing OpenStack Image API service."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml:32(title)
-msgid "Add OpenStack Image API resource to Pacemaker"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml:38(simpara)
-msgid "You can now add the Pacemaker configuration for OpenStack Image API resource. Connect to the Pacemaker cluster with <literal>crm configure</literal>, and add the following cluster resources:"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml:47(simpara)
-msgid "<literal>p_glance-api</literal>, a resource for manage OpenStack Image API service"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml:51(simpara)
-msgid "<literal>crm configure</literal> supports batch input, so you may copy and paste the above into your live pacemaker configuration, and then make changes as required. For example, you may enter <literal>edit p_ip_glance-api</literal> from the <literal>crm configure</literal> menu and edit the resource to match your preferred virtual IP address."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml:56(simpara)
-msgid "Once completed, commit your configuration changes by entering <literal>commit</literal> from the <literal>crm configure</literal> menu. Pacemaker will then start the OpenStack Image API service, and its dependent resources, on one of your nodes."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml:62(title)
-msgid "Configure OpenStack Image Service API"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml:64(simpara)
-msgid "Edit <literal>/etc/glance/glance-api.conf</literal>:"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml:80(title)
-msgid "Configure OpenStack services to use high available OpenStack Image API"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml:82(simpara)
-msgid "Your OpenStack services must now point their OpenStack Image API configuration to the highly available, virtual cluster IP address — rather than an OpenStack Image API server’s physical IP address as you normally would."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml:85(simpara)
-msgid "For OpenStack Compute, for example, if your OpenStack Image API service IP address is 192.168.42.104 as in the configuration explained here, you would use the following line in your <literal>nova.conf</literal> file:"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml:89(simpara)
-msgid "You must also create the OpenStack Image API endpoint with this IP."
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_api_pacemaker.xml:6(title)
-msgid "Configure Pacemaker group"
-msgstr ""
-
-#: ./doc/high-availability-guide/api/section_api_pacemaker.xml:8(simpara)
-msgid "Finally, we need to create a service <literal>group</literal> to ensure that virtual IP is linked to the API services resources:"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml:6(title)
-msgid "Configure RabbitMQ"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml:8(simpara)
-msgid "Here we are building a cluster of RabbitMQ nodes to construct a RabbitMQ broker. Mirrored queues in RabbitMQ improve the availability of service since it will be resilient to failures. We have to consider that while exchanges and bindings will survive the loss of individual nodes, queues and their messages will not because a queue and its contents is located on one node. If we lose this node, we also lose the queue."
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml:13(simpara)
-msgid "We consider that we run (at least) two RabbitMQ servers. To build a broker, we need to ensure that all nodes have the same erlang cookie file. To do so, stop RabbitMQ everywhere and copy the cookie from rabbit1 server to other server(s):"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml:18(simpara)
-msgid "Then, start RabbitMQ on nodes. If RabbitMQ fails to start, you can’t continue to the next step."
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml:20(simpara)
-msgid "Now, we are building the HA cluster. From rabbit2, run these commands:"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml:24(simpara)
-msgid "To verify the cluster status :"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml:29(simpara)
-msgid "If the cluster is working, you can now proceed to creating users and passwords for queues."
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml:31(emphasis)
-msgid "Note for RabbitMQ version 3"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml:33(simpara)
-msgid "Queue mirroring is no longer controlled by the <emphasis>x-ha-policy</emphasis> argument when declaring a queue. OpenStack can continue to declare this argument, but it won’t cause queues to be mirrored. We need to make sure that all queues (except those with auto-generated names) are mirrored across all running nodes:"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml:38(link)
-msgid "More information about High availability in RabbitMQ"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml:6(title)
-msgid "Configure OpenStack services to use RabbitMQ"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml:8(simpara)
-msgid "We have to configure the OpenStack components to use at least two RabbitMQ nodes."
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml:9(simpara)
-msgid "Do this configuration on all services using RabbitMQ:"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml:10(simpara)
-msgid "RabbitMQ HA cluster host:port pairs:"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml:12(simpara)
-msgid "How frequently to retry connecting with RabbitMQ:"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml:14(simpara)
-msgid "How long to back-off for between retries when connecting to RabbitMQ:"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml:16(simpara)
-msgid "Maximum retries with trying to connect to RabbitMQ (infinite by default):"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml:18(simpara)
-msgid "Use durable queues in RabbitMQ:"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml:20(simpara)
-msgid "Use H/A queues in RabbitMQ (x-ha-policy: all):"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml:22(simpara)
-msgid "If you change the configuration from an old setup which did not use HA queues, you should interrupt the service:"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml:26(simpara)
-msgid "Services currently working with HA queues: OpenStack Compute, OpenStack Block Storage, OpenStack Networking, Telemetry."
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml:8(simpara)
-msgid "This setup has been tested with RabbitMQ 2.7.1."
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml:11(title)
-msgid "On Ubuntu / Debian"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml:13(simpara) ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml:23(simpara)
-msgid "RabbitMQ is packaged on both distros:"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml:16(link)
-msgid "Official manual for installing RabbitMQ on Ubuntu / Debian"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml:21(title)
-msgid "On Fedora / RHEL"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml:26(link)
-msgid "Official manual for installing RabbitMQ on Fedora / RHEL"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_memcached.xml:6(title)
-msgid "Memcached"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_memcached.xml:8(simpara)
-msgid "Most of OpenStack services use an application to offer persistence and store ephemeral data (like tokens). Memcached is one of them and can scale-out easily without specific trick."
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_memcached.xml:10(simpara)
-msgid "To install and configure it, read the <link href=\"http://code.google.com/p/memcached/wiki/NewStart\">official documentation</link>."
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_memcached.xml:11(simpara)
-msgid "Memory caching is managed by oslo-incubator so the way to use multiple memcached servers is the same for all projects."
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_memcached.xml:12(simpara)
-msgid "Example with two hosts:"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_memcached.xml:14(simpara)
-msgid "By default, controller1 handles the caching service but if the host goes down, controller2 does the job. For more information about memcached installation, see the OpenStack Cloud Administrator Guide."
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:6(title)
-msgid "Run OpenStack API and schedulers"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:10(title)
-msgid "API services"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:12(simpara)
-msgid "All OpenStack projects have an API service for controlling all the resources in the Cloud. In Active / Active mode, the most common setup is to scale-out these services on at least two nodes and use load-balancing and virtual IP (with HAproxy &amp; Keepalived in this setup)."
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:16(emphasis)
-msgid "Configure API OpenStack services"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:18(simpara)
-msgid "To configure our Cloud using Highly available and scalable API services, we need to ensure that:"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:21(simpara)
-msgid "You use Virtual IP when configuring OpenStack Identity endpoints."
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:26(simpara)
-msgid "All OpenStack configuration files should refer to Virtual IP."
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:32(emphasis)
-msgid "In case of failure"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:34(simpara)
-msgid "The monitor check is quite simple since it just establishes a TCP connection to the API port. Comparing to the Active / Passive mode using Corosync &amp; Resources Agents, we don’t check if the service is actually running). That’s why all OpenStack API should be monitored by another tool (i.e. Nagios) with the goal to detect failures in the Cloud Framework infrastructure."
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:41(title)
-msgid "Schedulers"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:43(simpara)
-msgid "OpenStack schedulers are used to determine how to dispatch compute, network and volume requests. The most common setup is to use RabbitMQ as messaging system already documented in this guide. Those services are connected to the messaging backend and can scale-out :"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:48(simpara)
-msgid "nova-scheduler"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:53(simpara)
-msgid "nova-conductor"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:58(simpara)
-msgid "cinder-scheduler"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:63(simpara)
-msgid "neutron-server"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:68(simpara)
-msgid "ceilometer-collector"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:73(simpara)
-msgid "heat-engine"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:78(simpara)
-msgid "Please refer to the RabbitMQ section for configure these services with multiple messaging servers."
-msgstr ""
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml:6(title)
-msgid "Highly available neutron L3 agent"
-msgstr ""
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml:8(simpara)
-msgid "The neutron L3 agent provides L3/NAT forwarding to ensure external network access for VMs on tenant networks. High availability for the L3 agent is achieved by adopting Pacemaker."
-msgstr ""
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml:12(simpara)
-msgid "Here is the <link href=\"http://docs.openstack.org/trunk/config-reference/content/section_adv_cfg_l3_agent.html\">documentation</link> for installing neutron L3 agent."
-msgstr ""
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml:16(title)
-msgid "Add neutron L3 agent resource to Pacemaker"
-msgstr ""
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml:22(simpara)
-msgid "You may now proceed with adding the Pacemaker configuration for neutron L3 agent resource. Connect to the Pacemaker cluster with <literal>crm configure</literal>, and add the following cluster resources:"
-msgstr ""
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml:32(simpara)
-msgid "<literal>p_neutron-l3-agent</literal>, a resource for manage Neutron L3 Agent service"
-msgstr ""
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml:39(simpara)
-msgid "Once completed, commit your configuration changes by entering <literal>commit</literal> from the <literal>crm configure</literal> menu. Pacemaker will then start the neutron L3 agent service, and its dependent resources, on one of your nodes."
-msgstr ""
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml:43(simpara)
-msgid "This method does not ensure a zero downtime since it has to recreate all the namespaces and virtual routers on the node."
-msgstr ""
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml:6(title)
-msgid "Highly available neutron metadata agent"
-msgstr ""
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml:8(simpara)
-msgid "Neutron metadata agent allows Compute API metadata to be reachable by VMs on tenant networks. High availability for the metadata agent is achieved by adopting Pacemaker."
-msgstr ""
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml:12(simpara)
-msgid "Here is the <link href=\"http://docs.openstack.org/trunk/config-reference/content/networking-options-metadata.html\">documentation</link> for installing Neutron Metadata Agent."
-msgstr ""
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml:16(title)
-msgid "Add neutron metadata agent resource to Pacemaker"
-msgstr ""
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml:22(simpara)
-msgid "You may now proceed with adding the Pacemaker configuration for neutron metadata agent resource. Connect to the Pacemaker cluster with <literal>crm configure</literal>, and add the following cluster resources:"
-msgstr ""
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml:32(simpara)
-msgid "<literal>p_neutron-metadata-agent</literal>, a resource for manage Neutron Metadata Agent service"
-msgstr ""
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml:40(simpara)
-msgid "Once completed, commit your configuration changes by entering <literal>commit</literal> from the <literal>crm configure</literal> menu. Pacemaker will then start the neutron metadata agent service, and its dependent resources, on one of your nodes."
-msgstr ""
-
-#: ./doc/high-availability-guide/network/section_manage_network_resources.xml:6(title)
-msgid "Manage network resources"
-msgstr ""
-
-#: ./doc/high-availability-guide/network/section_manage_network_resources.xml:8(simpara)
-msgid "You can now add the Pacemaker configuration for managing all network resources together with a group. Connect to the Pacemaker cluster with <literal>crm configure</literal>, and add the following cluster resources:"
-msgstr ""
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml:6(title)
-msgid "Highly available neutron DHCP agent"
-msgstr ""
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml:8(simpara)
-msgid "Neutron DHCP agent distributes IP addresses to the VMs with dnsmasq (by default). High availability for the DHCP agent is achieved by adopting Pacemaker."
-msgstr ""
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml:12(simpara)
-msgid "Here is the <link href=\"http://docs.openstack.org/trunk/config-reference/content/section_adv_cfg_dhcp_agent.html\">documentation</link> for installing neutron DHCP agent."
-msgstr ""
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml:16(title)
-msgid "Add neutron DHCP agent resource to Pacemaker"
-msgstr ""
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml:22(simpara)
-msgid "You may now proceed with adding the Pacemaker configuration for neutron DHCP agent resource. Connect to the Pacemaker cluster with <literal>crm configure</literal>, and add the following cluster resources:"
-msgstr ""
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml:32(simpara)
-msgid "<literal>p_neutron-dhcp-agent</literal>, a resource for manage Neutron DHCP Agent service"
-msgstr ""
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml:40(simpara)
-msgid "Once completed, commit your configuration changes by entering <literal>commit</literal> from the <literal>crm configure</literal> menu. Pacemaker will then start the neutron DHCP agent service, and its dependent resources, on one of your nodes."
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_network/section_run_neutron_l3_agent.xml:6(title)
-msgid "Run neutron L3 agent"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_network/section_run_neutron_l3_agent.xml:8(simpara)
-msgid "The neutron L3 agent is scalable thanks to the scheduler that allows distribution of virtual routers across multiple nodes. But there is no native feature to make these routers highly available. At this time, the Active / Passive solution exists to run the Neutron L3 agent in failover mode with Pacemaker. See the Active / Passive section of this guide."
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_network/section_run_neutron_metadata_agent.xml:6(title)
-msgid "Run neutron metadata agent"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_network/section_run_neutron_metadata_agent.xml:8(simpara)
-msgid "There is no native feature to make this service highly available. At this time, the Active / Passive solution exists to run the neutron metadata agent in failover mode with Pacemaker. See the Active / Passive section of this guide."
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_network/section_run_neutron_dhcp_agent.xml:6(title)
-msgid "Run neutron DHCP agent"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_network/section_run_neutron_dhcp_agent.xml:8(simpara)
-msgid "OpenStack Networking service has a scheduler that lets you run multiple agents across nodes. Also, the DHCP agent can be natively highly available. For details, see <link href=\"http://docs.openstack.org/trunk/config-reference/content/app_demo_multi_dhcp_agents.html\">OpenStack Configuration Reference</link>."
+#: ./doc/high-availability-guide/part_active_active.xml:6(title)
+msgid "HA using active/active"
 msgstr ""
 
 #: ./doc/high-availability-guide/ha_aa_db/section_ha_aa_db_galera_monitoring.xml:6(title)
@@ -1229,14 +365,6 @@ msgstr ""
 msgid "(Coming soon)"
 msgstr ""
 
-#: ./doc/high-availability-guide/ha_aa_db/section_other_ways_to_provide_a_highly_available_database.xml:6(title)
-msgid "Other ways to provide a highly available database"
-msgstr ""
-
-#: ./doc/high-availability-guide/ha_aa_db/section_other_ways_to_provide_a_highly_available_database.xml:8(simpara)
-msgid "MySQL with Galera is by no means the only way to achieve database HA. MariaDB (<link href=\"https://mariadb.org/\">https://mariadb.org/</link>) and Percona (<link href=\"http://www.percona.com/\">http://www.percona.com/</link>) also work with Galera. You also have the option to use Postgres, which has its own replication, or another database HA option."
-msgstr ""
-
 #: ./doc/high-availability-guide/ha_aa_db/section_ha_aa_db_mysql_galera.xml:6(title)
 msgid "MySQL with Galera"
 msgstr ""
@@ -1333,6 +461,534 @@ msgstr ""
 msgid "You should see a status that looks something like this:"
 msgstr ""
 
+#: ./doc/high-availability-guide/ha_aa_db/section_other_ways_to_provide_a_highly_available_database.xml:6(title)
+msgid "Other ways to provide a highly available database"
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_db/section_other_ways_to_provide_a_highly_available_database.xml:8(simpara)
+msgid "MySQL with Galera is by no means the only way to achieve database HA. MariaDB (<link href=\"https://mariadb.org/\">https://mariadb.org/</link>) and Percona (<link href=\"http://www.percona.com/\">http://www.percona.com/</link>) also work with Galera. You also have the option to use Postgres, which has its own replication, or another database HA option."
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_network/section_run_neutron_l3_agent.xml:6(title)
+msgid "Run neutron L3 agent"
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_network/section_run_neutron_l3_agent.xml:8(simpara)
+msgid "The neutron L3 agent is scalable thanks to the scheduler that allows distribution of virtual routers across multiple nodes. But there is no native feature to make these routers highly available. At this time, the Active / Passive solution exists to run the Neutron L3 agent in failover mode with Pacemaker. See the Active / Passive section of this guide."
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_network/section_run_neutron_metadata_agent.xml:6(title)
+msgid "Run neutron metadata agent"
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_network/section_run_neutron_metadata_agent.xml:8(simpara)
+msgid "There is no native feature to make this service highly available. At this time, the Active / Passive solution exists to run the neutron metadata agent in failover mode with Pacemaker. See the Active / Passive section of this guide."
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_network/section_run_neutron_dhcp_agent.xml:6(title)
+msgid "Run neutron DHCP agent"
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_network/section_run_neutron_dhcp_agent.xml:8(simpara)
+msgid "OpenStack Networking service has a scheduler that lets you run multiple agents across nodes. Also, the DHCP agent can be natively highly available. For details, see <link href=\"http://docs.openstack.org/trunk/config-reference/content/app_demo_multi_dhcp_agents.html\">OpenStack Configuration Reference</link>."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml:6(title)
+msgid "Highly available Block Storage API"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml:8(simpara)
+msgid "Making the Block Storage (cinder) API service highly available in active / passive mode involves"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml:11(simpara)
+msgid "Configure Block Storage to listen on the VIP address,"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml:16(simpara)
+msgid "managing Block Storage API daemon with the Pacemaker cluster manager,"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml:21(simpara) ./doc/high-availability-guide/api/section_glance_api.xml:22(simpara) ./doc/high-availability-guide/api/section_neutron_server.xml:22(simpara) ./doc/high-availability-guide/api/section_keystone.xml:22(simpara)
+msgid "Configure OpenStack services to use this IP address."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml:27(simpara)
+msgid "Here is the <link href=\"http://docs.openstack.org/trunk/install-guide/install/apt/content/ch_cinder.html\">documentation</link> for installing Block Storage service."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml:33(title)
+msgid "Add Block Storage API resource to Pacemaker"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml:35(simpara) ./doc/high-availability-guide/api/section_glance_api.xml:34(simpara) ./doc/high-availability-guide/api/section_neutron_server.xml:34(simpara) ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml:26(simpara) ./doc/high-availability-guide/api/section_keystone.xml:34(simpara) ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml:18(simpara) ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml:18(simpara) ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml:18(simpara)
+msgid "First of all, you need to download the resource agent to your system:"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml:39(simpara)
+msgid "You can now add the Pacemaker configuration for Block Storage API resource. Connect to the Pacemaker cluster with <literal>crm configure</literal>, and add the following cluster resources:"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml:46(simpara) ./doc/high-availability-guide/api/section_glance_api.xml:44(simpara) ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml:36(simpara) ./doc/high-availability-guide/controller/section_rabbitmq.xml:185(simpara) ./doc/high-availability-guide/controller/section_mysql.xml:197(simpara) ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml:29(simpara) ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml:29(simpara) ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml:29(simpara)
+msgid "This configuration creates"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml:49(simpara)
+msgid "<literal>p_cinder-api</literal>, a resource for manage Block Storage API service"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml:53(simpara)
+msgid "<literal>crm configure</literal> supports batch input, so you may copy and paste the above into your live pacemaker configuration, and then make changes as required. For example, you may enter <literal>edit p_ip_cinder-api</literal> from the <literal>crm configure</literal> menu and edit the resource to match your preferred virtual IP address."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml:58(simpara)
+msgid "Once completed, commit your configuration changes by entering <literal>commit</literal> from the <literal>crm configure</literal> menu. Pacemaker will then start the Block Storage API service, and its dependent resources, on one of your nodes."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml:64(title)
+msgid "Configure Block Storage API service"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml:66(simpara)
+msgid "Edit <literal>/etc/cinder/cinder.conf</literal>:"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml:79(title)
+msgid "Configure OpenStack services to use highly available Block Storage API"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml:81(simpara)
+msgid "Your OpenStack services must now point their Block Storage API configuration to the highly available, virtual cluster IP address — rather than a Block Storage API server’s physical IP address as you normally would."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml:84(simpara)
+msgid "You must create the Block Storage API endpoint with this IP."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml:86(simpara)
+msgid "If you are using both private and public IP, you should create two Virtual IPs and define your endpoint like this:"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_api_pacemaker.xml:6(title)
+msgid "Configure Pacemaker group"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_api_pacemaker.xml:8(simpara)
+msgid "Finally, we need to create a service <literal>group</literal> to ensure that virtual IP is linked to the API services resources:"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml:6(title)
+msgid "Highly available OpenStack Image API"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml:8(simpara)
+msgid "OpenStack Image Service offers a service for discovering, registering, and retrieving virtual machine images. To make the OpenStack Image API service highly available in active / passive mode, you must:"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml:12(simpara)
+msgid "Configure OpenStack Image to listen on the VIP address."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml:17(simpara)
+msgid "Manage OpenStack Image API daemon with the Pacemaker cluster manager."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml:28(simpara)
+msgid "Here is the <link href=\"http://docs.openstack.org/trunk/install-guide/install/apt/content/ch_installing-openstack-image.html\">documentation</link> for installing OpenStack Image API service."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml:32(title)
+msgid "Add OpenStack Image API resource to Pacemaker"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml:38(simpara)
+msgid "You can now add the Pacemaker configuration for OpenStack Image API resource. Connect to the Pacemaker cluster with <literal>crm configure</literal>, and add the following cluster resources:"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml:47(simpara)
+msgid "<literal>p_glance-api</literal>, a resource for manage OpenStack Image API service"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml:51(simpara)
+msgid "<literal>crm configure</literal> supports batch input, so you may copy and paste the above into your live pacemaker configuration, and then make changes as required. For example, you may enter <literal>edit p_ip_glance-api</literal> from the <literal>crm configure</literal> menu and edit the resource to match your preferred virtual IP address."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml:56(simpara)
+msgid "Once completed, commit your configuration changes by entering <literal>commit</literal> from the <literal>crm configure</literal> menu. Pacemaker will then start the OpenStack Image API service, and its dependent resources, on one of your nodes."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml:62(title)
+msgid "Configure OpenStack Image Service API"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml:64(simpara)
+msgid "Edit <literal>/etc/glance/glance-api.conf</literal>:"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml:80(title)
+msgid "Configure OpenStack services to use high available OpenStack Image API"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml:82(simpara)
+msgid "Your OpenStack services must now point their OpenStack Image API configuration to the highly available, virtual cluster IP address — rather than an OpenStack Image API server’s physical IP address as you normally would."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml:85(simpara)
+msgid "For OpenStack Compute, for example, if your OpenStack Image API service IP address is 192.168.42.104 as in the configuration explained here, you would use the following line in your <literal>nova.conf</literal> file:"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml:89(simpara)
+msgid "You must also create the OpenStack Image API endpoint with this IP."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml:91(simpara) ./doc/high-availability-guide/api/section_neutron_server.xml:85(simpara)
+msgid "If you are using both private and public IP addresses, you should create two Virtual IP addresses and define your endpoint like this:"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml:6(title)
+msgid "Highly available OpenStack Networking server"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml:8(simpara)
+msgid "OpenStack Networking is the network connectivity service in OpenStack. Making the OpenStack Networking Server service highly available in active / passive mode involves"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml:12(simpara)
+msgid "Configure OpenStack Networking to listen on the VIP address,"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml:17(simpara)
+msgid "managing OpenStack Networking API Server daemon with the Pacemaker cluster manager,"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml:28(simpara)
+msgid "Here is the <link href=\"http://docs.openstack.org/trunk/install-guide/install/apt/content/ch_installing-openstack-networking.html\">documentation</link> for installing OpenStack Networking service."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml:32(title)
+msgid "Add OpenStack Networking Server resource to Pacemaker"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml:38(simpara)
+msgid "You can now add the Pacemaker configuration for OpenStack Networking Server resource. Connect to the Pacemaker cluster with <literal>crm configure</literal>, and add the following cluster resources:"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml:45(simpara)
+msgid "This configuration creates <literal>p_neutron-server</literal>, a resource for manage OpenStack Networking Server service"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml:46(simpara)
+msgid "<literal>crm configure</literal> supports batch input, so you may copy and paste the above into your live pacemaker configuration, and then make changes as required. For example, you may enter <literal>edit p_neutron-server</literal> from the <literal>crm configure</literal> menu and edit the resource to match your preferred virtual IP address."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml:51(simpara)
+msgid "Once completed, commit your configuration changes by entering <literal>commit</literal> from the <literal>crm configure</literal> menu. Pacemaker will then start the OpenStack Networking API service, and its dependent resources, on one of your nodes."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml:57(title)
+msgid "Configure OpenStack Networking server"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml:59(simpara)
+msgid "Edit <literal>/etc/neutron/neutron.conf</literal> :"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml:76(title)
+msgid "Configure OpenStack services to use highly available OpenStack Networking server"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml:78(simpara)
+msgid "Your OpenStack services must now point their OpenStack Networking Server configuration to the highly available, virtual cluster IP address — rather than an OpenStack Networking server’s physical IP address as you normally would."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml:81(simpara)
+msgid "For example, you should configure OpenStack Compute for using highly available OpenStack Networking server in editing <literal>nova.conf</literal> file:"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml:83(simpara)
+msgid "You need to create the OpenStack Networking server endpoint with this IP."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml:6(title)
+msgid "Highly available Telemetry central agent"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml:8(simpara)
+msgid "Telemetry (ceilometer) is the metering and monitoring service in OpenStack. The Central agent polls for resource utilization statistics for resources not tied to instances or compute nodes."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml:12(simpara)
+msgid "Due to limitations of a polling model, a single instance of this agent can be polling a given list of meters. In this setup, we install this service on the API nodes also in the active / passive mode."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml:16(simpara)
+msgid "Making the Telemetry central agent service highly available in active / passive mode involves managing its daemon with the Pacemaker cluster manager."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml:19(simpara)
+msgid "You will find at <link href=\"http://docs.openstack.org/developer/ceilometer/install/manual.html#installing-the-central-agent\">this page</link> the process to install the Telemetry central agent."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml:24(title)
+msgid "Add the Telemetry central agent resource to Pacemaker"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml:30(simpara)
+msgid "You may then proceed with adding the Pacemaker configuration for the Telemetry central agent resource. Connect to the Pacemaker cluster with <literal>crm configure</literal>, and add the following cluster resources:"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml:39(simpara)
+msgid "<literal>p_ceilometer-agent-central</literal>, a resource for manage Ceilometer Central Agent service"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml:43(simpara) ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml:37(simpara) ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml:36(simpara) ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml:37(simpara)
+msgid "<literal>crm configure</literal> supports batch input, so you may copy and paste the above into your live pacemaker configuration, and then make changes as required."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml:46(simpara)
+msgid "Once completed, commit your configuration changes by entering <literal>commit</literal> from the <literal>crm configure</literal> menu. Pacemaker will then start the Ceilometer Central Agent service, and its dependent resources, on one of your nodes."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml:52(title)
+msgid "Configure Telemetry central agent service"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml:54(simpara)
+msgid "Edit <literal>/etc/ceilometer/ceilometer.conf</literal> :"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_keystone.xml:6(title)
+msgid "Highly available OpenStack Identity"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_keystone.xml:8(simpara)
+msgid "OpenStack Identity is the Identity Service in OpenStack and used by many services. Making the OpenStack Identity service highly available in active / passive mode involves"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_keystone.xml:12(simpara)
+msgid "Configure OpenStack Identity to listen on the VIP address,"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_keystone.xml:17(simpara)
+msgid "managing OpenStack Identity daemon with the Pacemaker cluster manager,"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_keystone.xml:28(simpara)
+msgid "Here is the <link href=\"http://docs.openstack.org/trunk/install-guide/install/apt/content/ch_installing-openstack-identity-service.html\">documentation</link> for installing OpenStack Identity service."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_keystone.xml:32(title)
+msgid "Add OpenStack Identity resource to Pacemaker"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_keystone.xml:40(simpara)
+msgid "You can now add the Pacemaker configuration for OpenStack Identity resource. Connect to the Pacemaker cluster with <literal>crm configure</literal>, and add the following cluster resources:"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_keystone.xml:46(simpara)
+msgid "This configuration creates <literal>p_keystone</literal>, a resource for managing the OpenStack Identity service."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_keystone.xml:47(simpara)
+msgid "<literal>crm configure</literal> supports batch input, so you may copy and paste the above into your live pacemaker configuration, and then make changes as required. For example, you may enter <literal>edit p_ip_keystone</literal> from the <literal>crm configure</literal> menu and edit the resource to match your preferred virtual IP address."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_keystone.xml:52(simpara)
+msgid "Once completed, commit your configuration changes by entering <literal>commit</literal> from the <literal>crm configure</literal> menu. Pacemaker will then start the OpenStack Identity service, and its dependent resources, on one of your nodes."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_keystone.xml:58(title)
+msgid "Configure OpenStack Identity service"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_keystone.xml:60(simpara)
+msgid "You need to edit your OpenStack Identity configuration file (<literal>keystone.conf</literal>) and change the bind parameters:"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_keystone.xml:61(simpara)
+msgid "On Havana:"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_keystone.xml:63(simpara)
+msgid "On Icehouse, the <literal>admin_bind_host</literal> option lets you use a private network for the admin access."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_keystone.xml:66(simpara)
+msgid "To be sure all data will be highly available, you should be sure that you store everything in the MySQL database (which is also highly available):"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_keystone.xml:76(title)
+msgid "Configure OpenStack services to use the highly available OpenStack Identity"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_keystone.xml:78(simpara)
+msgid "Your OpenStack services must now point their OpenStack Identity configuration to the highly available, virtual cluster IP address — rather than a OpenStack Identity server’s physical IP address as you normally would."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_keystone.xml:81(simpara)
+msgid "For example with OpenStack Compute, if your OpenStack Identity service IP address is 192.168.42.103 as in the configuration explained here, you would use the following line in your API configuration file (<literal>api-paste.ini</literal>):"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_keystone.xml:86(simpara)
+msgid "You also need to create the OpenStack Identity Endpoint with this IP."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_keystone.xml:87(simpara)
+msgid "NOTE : If you are using both private and public IP addresses, you should create two Virtual IP addresses and define your endpoint like this:"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_keystone.xml:89(simpara)
+msgid "If you are using the horizon dashboard, you should edit the <literal>local_settings.py</literal> file:"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_api_vip.xml:6(title)
+msgid "Configure the VIP"
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_api_vip.xml:8(simpara)
+msgid "First, you must select and assign a virtual IP address (VIP) that can freely float between cluster nodes."
+msgstr ""
+
+#: ./doc/high-availability-guide/api/section_api_vip.xml:9(simpara)
+msgid "This configuration creates <literal>p_ip_api</literal>, a virtual IP address for use by the API node (192.168.42.103) :"
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:6(title)
+msgid "Highly available RabbitMQ"
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:8(simpara)
+msgid "RabbitMQ is the default AMQP server used by many OpenStack services. Making the RabbitMQ service highly available involves:"
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:12(simpara)
+msgid "configuring a DRBD device for use by RabbitMQ,"
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:17(simpara)
+msgid "configuring RabbitMQ to use a data directory residing on that DRBD device,"
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:23(simpara) ./doc/high-availability-guide/controller/section_mysql.xml:23(simpara)
+msgid "selecting and assigning a virtual IP address (VIP) that can freely float between cluster nodes,"
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:29(simpara)
+msgid "configuring RabbitMQ to listen on that IP address,"
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:34(simpara)
+msgid "managing all resources, including the RabbitMQ daemon itself, with the Pacemaker cluster manager."
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:41(simpara)
+msgid "There is an alternative method of configuring RabbitMQ for high availability. That approach, known as <link href=\"http://www.rabbitmq.com/ha.html\">active-active mirrored queues</link>, happens to be the one preferred by the RabbitMQ developers — however it has shown less than ideal consistency and reliability in OpenStack clusters. Thus, at the time of writing, the Pacemaker/DRBD based approach remains the recommended one for OpenStack environments, although this may change in the near future as RabbitMQ active-active mirrored queues mature."
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:53(title) ./doc/high-availability-guide/controller/section_mysql.xml:50(title)
+msgid "Configure DRBD"
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:55(simpara)
+msgid "The Pacemaker based RabbitMQ server requires a DRBD resource from which it mounts the <literal>/var/lib/rabbitmq</literal> directory. In this example, the DRBD resource is simply named <literal>rabbitmq</literal>:"
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:60(title)
+msgid "<literal>rabbitmq</literal> DRBD resource configuration (<literal>/etc/drbd.d/rabbitmq.res</literal>)"
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:76(simpara)
+msgid "This resource uses an underlying local disk (in DRBD terminology, a <emphasis>backing device</emphasis>) named <literal>/dev/data/rabbitmq</literal> on both cluster nodes, <literal>node1</literal> and <literal>node2</literal>. Normally, this would be an LVM Logical Volume specifically set aside for this purpose. The DRBD <literal>meta-disk</literal> is <literal>internal</literal>, meaning DRBD-specific metadata is being stored at the end of the <literal>disk</literal> device itself. The device is configured to communicate between IPv4 addresses 10.0.42.100 and 10.0.42.254, using TCP port 7701. Once enabled, it will map to a local DRBD block device with the device minor number 1, that is, <literal>/dev/drbd1</literal>."
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:85(simpara) ./doc/high-availability-guide/controller/section_mysql.xml:82(simpara)
+msgid "Enabling a DRBD resource is explained in detail in <link href=\"http://www.drbd.org/users-guide-8.3/s-first-time-up.html\">the DRBD User’s Guide</link>. In brief, the proper sequence of commands is this:"
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:93(para)
+msgid "Initializes DRBD metadata and writes the initial set of metadata to <literal>/dev/data/rabbitmq</literal>. Must be completed on both nodes."
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:99(para)
+msgid "Creates the <literal>/dev/drbd1</literal> device node, <emphasis>attaches</emphasis> the DRBD device to its backing store, and <emphasis>connects</emphasis> the DRBD node to its peer. Must be completed on both nodes."
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:106(para) ./doc/high-availability-guide/controller/section_mysql.xml:103(para)
+msgid "Kicks off the initial device synchronization, and puts the device into the <literal>primary</literal> (readable and writable) role. See <link href=\"http://www.drbd.org/users-guide-8.3/ch-admin.html#s-roles\">Resource roles</link> (from the DRBD User’s Guide) for a more detailed description of the primary and secondary roles in DRBD. Must be completed <emphasis>on one node only,</emphasis> namely the one where you are about to continue with creating your filesystem."
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:120(title)
+msgid "Create a file system"
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:122(simpara)
+msgid "Once the DRBD resource is running and in the primary role (and potentially still in the process of running the initial device synchronization), you may proceed with creating the filesystem for RabbitMQ data. XFS is generally the recommended filesystem:"
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:127(simpara) ./doc/high-availability-guide/controller/section_mysql.xml:124(simpara)
+msgid "You may also use the alternate device path for the DRBD device, which may be easier to remember as it includes the self-explanatory resource name:"
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:131(simpara) ./doc/high-availability-guide/controller/section_mysql.xml:128(simpara)
+msgid "Once completed, you may safely return the device to the secondary role. Any ongoing device synchronization will continue in the background:"
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:138(title)
+msgid "Prepare RabbitMQ for Pacemaker high availability"
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:140(simpara)
+msgid "In order for Pacemaker monitoring to function properly, you must ensure that RabbitMQ’s <literal>.erlang.cookie</literal> files are identical on all nodes, regardless of whether DRBD is mounted there or not. The simplest way of doing so is to take an existing <literal>.erlang.cookie</literal> from one of your nodes, copying it to the RabbitMQ data directory on the other node, and also copying it to the DRBD-backed filesystem."
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:153(title)
+msgid "Add RabbitMQ resources to Pacemaker"
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:155(simpara)
+msgid "You may now proceed with adding the Pacemaker configuration for RabbitMQ resources. Connect to the Pacemaker cluster with <literal>crm configure</literal>, and add the following cluster resources:"
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:188(simpara)
+msgid "<literal>p_ip_rabbitmp</literal>, a virtual IP address for use by RabbitMQ (192.168.42.100),"
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:193(simpara)
+msgid "<literal>p_fs_rabbitmq</literal>, a Pacemaker managed filesystem mounted to <literal>/var/lib/rabbitmq</literal> on whatever node currently runs the RabbitMQ service,"
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:199(simpara)
+msgid "<literal>ms_drbd_rabbitmq</literal>, the <emphasis>master/slave set</emphasis> managing the <literal>rabbitmq</literal> DRBD resource,"
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:204(simpara) ./doc/high-availability-guide/controller/section_mysql.xml:216(simpara)
+msgid "a service <literal>group</literal> and <literal>order</literal> and <literal>colocation</literal> constraints to ensure resources are started on the correct nodes, and in the correct sequence."
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:210(simpara)
+msgid "<literal>crm configure</literal> supports batch input, so you may copy and paste the above into your live pacemaker configuration, and then make changes as required. For example, you may enter <literal>edit p_ip_rabbitmq</literal> from the <literal>crm configure</literal> menu and edit the resource to match your preferred virtual IP address."
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:215(simpara)
+msgid "Once completed, commit your configuration changes by entering <literal>commit</literal> from the <literal>crm configure</literal> menu. Pacemaker will then start the RabbitMQ service, and its dependent resources, on one of your nodes."
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:221(title)
+msgid "Configure OpenStack services for highly available RabbitMQ"
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:223(simpara)
+msgid "Your OpenStack services must now point their RabbitMQ configuration to the highly available, virtual cluster IP address — rather than a RabbitMQ server’s physical IP address as you normally would."
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:226(simpara)
+msgid "For OpenStack Image, for example, if your RabbitMQ service IP address is 192.168.42.100 as in the configuration explained here, you would use the following line in your OpenStack Image API configuration file (<literal>glance-api.conf</literal>):"
+msgstr ""
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:231(simpara)
+msgid "No other changes are necessary to your OpenStack configuration. If the node currently hosting your RabbitMQ experiences a problem necessitating service failover, your OpenStack services may experience a brief RabbitMQ interruption, as they would in the event of a network hiccup, and then continue to run normally."
+msgstr ""
+
 #: ./doc/high-availability-guide/controller/section_mysql.xml:6(title)
 msgid "Highly available MySQL"
 msgstr ""
@@ -1349,10 +1005,6 @@ msgstr ""
 msgid "Configure MySQL to use a data directory residing on that DRBD device,"
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_mysql.xml:23(simpara) ./doc/high-availability-guide/controller/section_rabbitmq.xml:23(simpara)
-msgid "selecting and assigning a virtual IP address (VIP) that can freely float between cluster nodes,"
-msgstr ""
-
 #: ./doc/high-availability-guide/controller/section_mysql.xml:29(simpara)
 msgid "Configure MySQL to listen on that IP address,"
 msgstr ""
@@ -1365,10 +1017,6 @@ msgstr ""
 msgid "<link href=\"http://codership.com/products/mysql_galera\">MySQL/Galera</link> is an alternative method of Configure MySQL for high availability. It is likely to become the preferred method of achieving MySQL high availability once it has sufficiently matured. At the time of writing, however, the Pacemaker/DRBD based approach remains the recommended one for OpenStack environments."
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_mysql.xml:50(title) ./doc/high-availability-guide/controller/section_rabbitmq.xml:53(title)
-msgid "Configure DRBD"
-msgstr ""
-
 #: ./doc/high-availability-guide/controller/section_mysql.xml:52(simpara)
 msgid "The Pacemaker based MySQL server requires a DRBD resource from which it mounts the <literal>/var/lib/mysql</literal> directory. In this example, the DRBD resource is simply named <literal>mysql</literal>:"
 msgstr ""
@@ -1381,10 +1029,6 @@ msgstr ""
 msgid "This resource uses an underlying local disk (in DRBD terminology, a <emphasis>backing device</emphasis>) named <literal>/dev/data/mysql</literal> on both cluster nodes, <literal>node1</literal> and <literal>node2</literal>. Normally, this would be an LVM Logical Volume specifically set aside for this purpose. The DRBD <literal>meta-disk</literal> is <literal>internal</literal>, meaning DRBD-specific metadata is being stored at the end of the <literal>disk</literal> device itself. The device is configured to communicate between IPv4 addresses 10.0.42.100 and 10.0.42.254, using TCP port 7700. Once enabled, it will map to a local DRBD block device with the device minor number 0, that is, <literal>/dev/drbd0</literal>."
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_mysql.xml:82(simpara) ./doc/high-availability-guide/controller/section_rabbitmq.xml:85(simpara)
-msgid "Enabling a DRBD resource is explained in detail in <link href=\"http://www.drbd.org/users-guide-8.3/s-first-time-up.html\">the DRBD User’s Guide</link>. In brief, the proper sequence of commands is this:"
-msgstr ""
-
 #: ./doc/high-availability-guide/controller/section_mysql.xml:90(para)
 msgid "Initializes DRBD metadata and writes the initial set of metadata to <literal>/dev/data/mysql</literal>. Must be completed on both nodes."
 msgstr ""
@@ -1393,10 +1037,6 @@ msgstr ""
 msgid "Creates the <literal>/dev/drbd0</literal> device node, <emphasis>attaches</emphasis> the DRBD device to its backing store, and <emphasis>connects</emphasis> the DRBD node to its peer. Must be completed on both nodes."
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_mysql.xml:103(para) ./doc/high-availability-guide/controller/section_rabbitmq.xml:106(para)
-msgid "Kicks off the initial device synchronization, and puts the device into the <literal>primary</literal> (readable and writable) role. See <link href=\"http://www.drbd.org/users-guide-8.3/ch-admin.html#s-roles\">Resource roles</link> (from the DRBD User’s Guide) for a more detailed description of the primary and secondary roles in DRBD. Must be completed <emphasis>on one node only,</emphasis> namely the one where you are about to continue with creating your filesystem."
-msgstr ""
-
 #: ./doc/high-availability-guide/controller/section_mysql.xml:117(title)
 msgid "Creating a file system"
 msgstr ""
@@ -1405,14 +1045,6 @@ msgstr ""
 msgid "Once the DRBD resource is running and in the primary role (and potentially still in the process of running the initial device synchronization), you may proceed with creating the filesystem for MySQL data. XFS is the generally recommended filesystem:"
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_mysql.xml:124(simpara) ./doc/high-availability-guide/controller/section_rabbitmq.xml:127(simpara)
-msgid "You may also use the alternate device path for the DRBD device, which may be easier to remember as it includes the self-explanatory resource name:"
-msgstr ""
-
-#: ./doc/high-availability-guide/controller/section_mysql.xml:128(simpara) ./doc/high-availability-guide/controller/section_rabbitmq.xml:131(simpara)
-msgid "Once completed, you may safely return the device to the secondary role. Any ongoing device synchronization will continue in the background:"
-msgstr ""
-
 #: ./doc/high-availability-guide/controller/section_mysql.xml:135(title)
 msgid "Prepare MySQL for Pacemaker high availability"
 msgstr ""
@@ -1453,10 +1085,6 @@ msgstr ""
 msgid "<literal>ms_drbd_mysql</literal>, the <emphasis>master/slave set</emphasis> managing the <literal>mysql</literal> DRBD resource,"
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_mysql.xml:216(simpara) ./doc/high-availability-guide/controller/section_rabbitmq.xml:204(simpara)
-msgid "a service <literal>group</literal> and <literal>order</literal> and <literal>colocation</literal> constraints to ensure resources are started on the correct nodes, and in the correct sequence."
-msgstr ""
-
 #: ./doc/high-availability-guide/controller/section_mysql.xml:222(simpara)
 msgid "<literal>crm configure</literal> supports batch input, so you may copy and paste the above into your live pacemaker configuration, and then make changes as required. For example, you may enter <literal>edit p_ip_mysql</literal> from the <literal>crm configure</literal> menu and edit the resource to match your preferred virtual IP address."
 msgstr ""
@@ -1481,116 +1109,488 @@ msgstr ""
 msgid "No other changes are necessary to your OpenStack configuration. If the node currently hosting your database experiences a problem necessitating service failover, your OpenStack services may experience a brief MySQL interruption, as they would in the event of a network hiccup, and then continue to run normally."
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:6(title)
-msgid "Highly available RabbitMQ"
+#: ./doc/high-availability-guide/ha_aa_controllers/section_memcached.xml:6(title)
+msgid "Memcached"
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:8(simpara)
-msgid "RabbitMQ is the default AMQP server used by many OpenStack services. Making the RabbitMQ service highly available involves:"
+#: ./doc/high-availability-guide/ha_aa_controllers/section_memcached.xml:8(simpara)
+msgid "Most of OpenStack services use an application to offer persistence and store ephemeral data (like tokens). Memcached is one of them and can scale-out easily without specific trick."
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:12(simpara)
-msgid "configuring a DRBD device for use by RabbitMQ,"
+#: ./doc/high-availability-guide/ha_aa_controllers/section_memcached.xml:10(simpara)
+msgid "To install and configure it, read the <link href=\"http://code.google.com/p/memcached/wiki/NewStart\">official documentation</link>."
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:17(simpara)
-msgid "configuring RabbitMQ to use a data directory residing on that DRBD device,"
+#: ./doc/high-availability-guide/ha_aa_controllers/section_memcached.xml:11(simpara)
+msgid "Memory caching is managed by oslo-incubator so the way to use multiple memcached servers is the same for all projects."
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:29(simpara)
-msgid "configuring RabbitMQ to listen on that IP address,"
+#: ./doc/high-availability-guide/ha_aa_controllers/section_memcached.xml:12(simpara)
+msgid "Example with two hosts:"
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:34(simpara)
-msgid "managing all resources, including the RabbitMQ daemon itself, with the Pacemaker cluster manager."
+#: ./doc/high-availability-guide/ha_aa_controllers/section_memcached.xml:14(simpara)
+msgid "By default, controller1 handles the caching service but if the host goes down, controller2 does the job. For more information about memcached installation, see the OpenStack Cloud Administrator Guide."
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:41(simpara)
-msgid "There is an alternative method of configuring RabbitMQ for high availability. That approach, known as <link href=\"http://www.rabbitmq.com/ha.html\">active-active mirrored queues</link>, happens to be the one preferred by the RabbitMQ developers — however it has shown less than ideal consistency and reliability in OpenStack clusters. Thus, at the time of writing, the Pacemaker/DRBD based approach remains the recommended one for OpenStack environments, although this may change in the near future as RabbitMQ active-active mirrored queues mature."
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:6(title)
+msgid "Run OpenStack API and schedulers"
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:55(simpara)
-msgid "The Pacemaker based RabbitMQ server requires a DRBD resource from which it mounts the <literal>/var/lib/rabbitmq</literal> directory. In this example, the DRBD resource is simply named <literal>rabbitmq</literal>:"
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:10(title)
+msgid "API services"
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:60(title)
-msgid "<literal>rabbitmq</literal> DRBD resource configuration (<literal>/etc/drbd.d/rabbitmq.res</literal>)"
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:12(simpara)
+msgid "All OpenStack projects have an API service for controlling all the resources in the Cloud. In Active / Active mode, the most common setup is to scale-out these services on at least two nodes and use load-balancing and virtual IP (with HAproxy &amp; Keepalived in this setup)."
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:76(simpara)
-msgid "This resource uses an underlying local disk (in DRBD terminology, a <emphasis>backing device</emphasis>) named <literal>/dev/data/rabbitmq</literal> on both cluster nodes, <literal>node1</literal> and <literal>node2</literal>. Normally, this would be an LVM Logical Volume specifically set aside for this purpose. The DRBD <literal>meta-disk</literal> is <literal>internal</literal>, meaning DRBD-specific metadata is being stored at the end of the <literal>disk</literal> device itself. The device is configured to communicate between IPv4 addresses 10.0.42.100 and 10.0.42.254, using TCP port 7701. Once enabled, it will map to a local DRBD block device with the device minor number 1, that is, <literal>/dev/drbd1</literal>."
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:16(emphasis)
+msgid "Configure API OpenStack services"
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:93(para)
-msgid "Initializes DRBD metadata and writes the initial set of metadata to <literal>/dev/data/rabbitmq</literal>. Must be completed on both nodes."
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:18(simpara)
+msgid "To configure our Cloud using Highly available and scalable API services, we need to ensure that:"
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:99(para)
-msgid "Creates the <literal>/dev/drbd1</literal> device node, <emphasis>attaches</emphasis> the DRBD device to its backing store, and <emphasis>connects</emphasis> the DRBD node to its peer. Must be completed on both nodes."
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:21(simpara)
+msgid "You use Virtual IP when configuring OpenStack Identity endpoints."
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:120(title)
-msgid "Create a file system"
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:26(simpara)
+msgid "All OpenStack configuration files should refer to Virtual IP."
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:122(simpara)
-msgid "Once the DRBD resource is running and in the primary role (and potentially still in the process of running the initial device synchronization), you may proceed with creating the filesystem for RabbitMQ data. XFS is generally the recommended filesystem:"
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:32(emphasis)
+msgid "In case of failure"
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:138(title)
-msgid "Prepare RabbitMQ for Pacemaker high availability"
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:34(simpara)
+msgid "The monitor check is quite simple since it just establishes a TCP connection to the API port. Comparing to the Active / Passive mode using Corosync &amp; Resources Agents, we don’t check if the service is actually running). That’s why all OpenStack API should be monitored by another tool (i.e. Nagios) with the goal to detect failures in the Cloud Framework infrastructure."
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:140(simpara)
-msgid "In order for Pacemaker monitoring to function properly, you must ensure that RabbitMQ’s <literal>.erlang.cookie</literal> files are identical on all nodes, regardless of whether DRBD is mounted there or not. The simplest way of doing so is to take an existing <literal>.erlang.cookie</literal> from one of your nodes, copying it to the RabbitMQ data directory on the other node, and also copying it to the DRBD-backed filesystem."
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:41(title)
+msgid "Schedulers"
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:153(title)
-msgid "Add RabbitMQ resources to Pacemaker"
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:43(simpara)
+msgid "OpenStack schedulers are used to determine how to dispatch compute, network and volume requests. The most common setup is to use RabbitMQ as messaging system already documented in this guide. Those services are connected to the messaging backend and can scale-out :"
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:155(simpara)
-msgid "You may now proceed with adding the Pacemaker configuration for RabbitMQ resources. Connect to the Pacemaker cluster with <literal>crm configure</literal>, and add the following cluster resources:"
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:48(simpara)
+msgid "nova-scheduler"
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:188(simpara)
-msgid "<literal>p_ip_rabbitmp</literal>, a virtual IP address for use by RabbitMQ (192.168.42.100),"
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:53(simpara)
+msgid "nova-conductor"
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:193(simpara)
-msgid "<literal>p_fs_rabbitmq</literal>, a Pacemaker managed filesystem mounted to <literal>/var/lib/rabbitmq</literal> on whatever node currently runs the RabbitMQ service,"
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:58(simpara)
+msgid "cinder-scheduler"
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:199(simpara)
-msgid "<literal>ms_drbd_rabbitmq</literal>, the <emphasis>master/slave set</emphasis> managing the <literal>rabbitmq</literal> DRBD resource,"
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:63(simpara)
+msgid "neutron-server"
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:210(simpara)
-msgid "<literal>crm configure</literal> supports batch input, so you may copy and paste the above into your live pacemaker configuration, and then make changes as required. For example, you may enter <literal>edit p_ip_rabbitmq</literal> from the <literal>crm configure</literal> menu and edit the resource to match your preferred virtual IP address."
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:68(simpara)
+msgid "ceilometer-collector"
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:215(simpara)
-msgid "Once completed, commit your configuration changes by entering <literal>commit</literal> from the <literal>crm configure</literal> menu. Pacemaker will then start the RabbitMQ service, and its dependent resources, on one of your nodes."
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:73(simpara)
+msgid "heat-engine"
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:221(title)
-msgid "Configure OpenStack services for highly available RabbitMQ"
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:78(simpara)
+msgid "Please refer to the RabbitMQ section for configure these services with multiple messaging servers."
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:223(simpara)
-msgid "Your OpenStack services must now point their RabbitMQ configuration to the highly available, virtual cluster IP address — rather than a RabbitMQ server’s physical IP address as you normally would."
+#: ./doc/high-availability-guide/pacemaker/section_start_pacemaker.xml:6(title)
+msgid "Start Pacemaker"
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:226(simpara)
-msgid "For OpenStack Image, for example, if your RabbitMQ service IP address is 192.168.42.100 as in the configuration explained here, you would use the following line in your OpenStack Image API configuration file (<literal>glance-api.conf</literal>):"
+#: ./doc/high-availability-guide/pacemaker/section_start_pacemaker.xml:8(simpara)
+msgid "Once the Corosync services have been started, and you have established that the cluster is communicating properly, it is safe to start <literal>pacemakerd</literal>, the Pacemaker master control process:"
 msgstr ""
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:231(simpara)
-msgid "No other changes are necessary to your OpenStack configuration. If the node currently hosting your RabbitMQ experiences a problem necessitating service failover, your OpenStack services may experience a brief RabbitMQ interruption, as they would in the event of a network hiccup, and then continue to run normally."
+#: ./doc/high-availability-guide/pacemaker/section_start_pacemaker.xml:13(simpara)
+msgid "<literal>/etc/init.d/pacemaker start</literal> (LSB)"
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_start_pacemaker.xml:17(simpara)
+msgid "<literal>service pacemaker start</literal> (LSB, alternate)"
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_start_pacemaker.xml:21(simpara)
+msgid "<literal>start pacemaker</literal> (upstart)"
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_start_pacemaker.xml:25(simpara)
+msgid "<literal>systemctl start pacemaker</literal> (systemd)"
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_start_pacemaker.xml:29(simpara)
+msgid "Once Pacemaker services have started, Pacemaker will create a default empty cluster configuration with no resources. You may observe Pacemaker’s status with the <literal>crm_mon</literal> utility:"
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml:6(title)
+msgid "Set up Corosync"
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml:8(simpara)
+msgid "Besides installing the <literal>corosync</literal> package, you must also create a configuration file, stored in <literal>/etc/corosync/corosync.conf</literal>. Most distributions ship an example configuration file (<literal>corosync.conf.example</literal>) as part of the documentation bundled with the <literal>corosync</literal> package. An example Corosync configuration file is shown below:"
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml:16(title)
+msgid "Corosync configuration file (<literal>corosync.conf</literal>)"
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml:90(para)
+msgid "The <literal>token</literal> value specifies the time, in milliseconds, during which the Corosync token is expected to be transmitted around the ring. When this timeout expires, the token is declared lost, and after <literal>token_retransmits_before_loss_const</literal> lost tokens the non-responding <emphasis>processor</emphasis> (cluster node) is declared dead. In other words, <literal>token</literal> × <literal>token_retransmits_before_loss_const</literal> is the maximum time a node is allowed to not respond to cluster messages before being considered dead. The default for <literal>token</literal> is 1000 (1 second), with 4 allowed retransmits. These defaults are intended to minimize failover times, but can cause frequent \"false alarms\" and unintended failovers in case of short network interruptions. The values used here are safer, albeit with slightly extended failover times."
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml:106(para)
+msgid "With <literal>secauth</literal> enabled, Corosync nodes mutually authenticate using a 128-byte shared secret stored in <literal>/etc/corosync/authkey</literal>, which may be generated with the <literal>corosync-keygen</literal> utility. When using <literal>secauth</literal>, cluster communications are also encrypted."
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml:114(para)
+msgid "In Corosync configurations using redundant networking (with more than one <literal>interface</literal>), you must select a Redundant Ring Protocol (RRP) mode other than <literal>none</literal>. <literal>active</literal> is the recommended RRP mode."
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml:121(para)
+msgid "There are several things to note about the recommended interface configuration:"
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml:127(simpara)
+msgid "The <literal>ringnumber</literal> must differ between all configured interfaces, starting with 0."
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml:133(simpara)
+msgid "The <literal>bindnetaddr</literal> is the <emphasis>network</emphasis> address of the interfaces to bind to. The example uses two network addresses of <literal>/24</literal> IPv4 subnets."
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml:139(simpara)
+msgid "Multicast groups (<literal>mcastaddr</literal>) <emphasis>must not</emphasis> be reused across cluster boundaries. In other words, no two distinct clusters should ever use the same multicast group. Be sure to select multicast addresses compliant with <link href=\"http://www.ietf.org/rfc/rfc2365.txt\">RFC 2365, \"Administratively Scoped IP Multicast\"</link>."
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml:148(simpara)
+msgid "For firewall configurations, note that Corosync communicates over UDP only, and uses <literal>mcastport</literal> (for receives) and <literal>mcastport</literal>-1 (for sends)."
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml:157(para)
+msgid "The <literal>service</literal> declaration for the <literal>pacemaker</literal> service may be placed in the <literal>corosync.conf</literal> file directly, or in its own separate file, <literal>/etc/corosync/service.d/pacemaker</literal>."
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml:164(simpara)
+msgid "Once created, the <literal>corosync.conf</literal> file (and the <literal>authkey</literal> file if the <literal>secauth</literal> option is enabled) must be synchronized across all cluster nodes."
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml:6(title)
+msgid "Install packages"
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml:8(simpara)
+msgid "On any host that is meant to be part of a Pacemaker cluster, you must first establish cluster communications through the Corosync messaging layer. This involves Install the following packages (and their dependencies, which your package manager will normally install automatically):"
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml:15(simpara)
+msgid "<literal>pacemaker</literal> Note that the crm shell should be downloaded separately."
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml:20(literal)
+msgid "crmsh"
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml:25(literal)
+msgid "corosync"
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml:30(literal)
+msgid "cluster-glue"
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml:34(simpara)
+msgid "<literal>fence-agents</literal> (Fedora only; all other distributions use fencing agents from <literal>cluster-glue</literal>)"
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml:40(literal)
+msgid "resource-agents"
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_set_basic_cluster_properties.xml:6(title)
+msgid "Set basic cluster properties"
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_set_basic_cluster_properties.xml:8(simpara)
+msgid "Once your Pacemaker cluster is set up, it is recommended to set a few basic cluster properties. To do so, start the <literal>crm</literal> shell and change into the configuration menu by entering <literal>configure</literal>. Alternatively. you may jump straight into the Pacemaker configuration menu by typing <literal>crm configure</literal> directly from a shell prompt."
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_set_basic_cluster_properties.xml:14(simpara)
+msgid "Then, set the following properties:"
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_set_basic_cluster_properties.xml:22(para)
+msgid "Setting <literal>no-quorum-policy=\"ignore\"</literal> is required in 2-node Pacemaker clusters for the following reason: if quorum enforcement is enabled, and one of the two nodes fails, then the remaining node can not establish a <emphasis>majority</emphasis> of quorum votes necessary to run services, and thus it is unable to take over any resources. The appropriate workaround is to ignore loss of quorum in the cluster. This is safe and necessary <emphasis>only</emphasis> in 2-node clusters. Do not set this property in Pacemaker clusters with more than two nodes."
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_set_basic_cluster_properties.xml:34(para)
+msgid "Setting <literal>pe-warn-series-max</literal>, <literal>pe-input-series-max</literal> and <literal>pe-error-series-max</literal> to 1000 instructs Pacemaker to keep a longer history of the inputs processed, and errors and warnings generated, by its Policy Engine. This history is typically useful in case cluster troubleshooting becomes necessary."
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_set_basic_cluster_properties.xml:43(para)
+msgid "Pacemaker uses an event-driven approach to cluster state processing. However, certain Pacemaker actions occur at a configurable interval, <literal>cluster-recheck-interval</literal>, which defaults to 15 minutes. It is usually prudent to reduce this to a shorter interval, such as 5 or 3 minutes."
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_set_basic_cluster_properties.xml:52(simpara)
+msgid "Once you have made these changes, you may <literal>commit</literal> the updated configuration."
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml:6(title)
+msgid "Starting Corosync"
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml:8(simpara)
+msgid "Corosync is started as a regular system service. Depending on your distribution, it may ship with a LSB (System V style) init script, an upstart job, or a systemd unit file. Either way, the service is usually named <literal>corosync</literal>:"
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml:14(simpara)
+msgid "<literal>/etc/init.d/corosync start</literal> (LSB)"
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml:18(simpara)
+msgid "<literal>service corosync start</literal> (LSB, alternate)"
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml:22(simpara)
+msgid "<literal>start corosync</literal> (upstart)"
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml:26(simpara)
+msgid "<literal>systemctl start corosync</literal> (systemd)"
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml:30(simpara)
+msgid "You can now check the Corosync connectivity with two tools."
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml:31(simpara)
+msgid "The <literal>corosync-cfgtool</literal> utility, when invoked with the <literal>-s</literal> option, gives a summary of the health of the communication rings:"
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml:42(simpara)
+msgid "The <literal>corosync-objctl</literal> utility can be used to dump the Corosync cluster member list:"
+msgstr ""
+
+#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml:51(simpara)
+msgid "You should see a <literal>status=joined</literal> entry for each of your constituent cluster nodes."
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml:6(title)
+msgid "Configure OpenStack services to use RabbitMQ"
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml:8(simpara)
+msgid "We have to configure the OpenStack components to use at least two RabbitMQ nodes."
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml:9(simpara)
+msgid "Do this configuration on all services using RabbitMQ:"
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml:10(simpara)
+msgid "RabbitMQ HA cluster host:port pairs:"
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml:12(simpara)
+msgid "How frequently to retry connecting with RabbitMQ:"
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml:14(simpara)
+msgid "How long to back-off for between retries when connecting to RabbitMQ:"
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml:16(simpara)
+msgid "Maximum retries with trying to connect to RabbitMQ (infinite by default):"
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml:18(simpara)
+msgid "Use durable queues in RabbitMQ:"
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml:20(simpara)
+msgid "Use H/A queues in RabbitMQ (x-ha-policy: all):"
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml:22(simpara)
+msgid "If you change the configuration from an old setup which did not use HA queues, you should interrupt the service:"
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml:26(simpara)
+msgid "Services currently working with HA queues: OpenStack Compute, OpenStack Block Storage, OpenStack Networking, Telemetry."
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml:8(simpara)
+msgid "This setup has been tested with RabbitMQ 2.7.1."
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml:11(title)
+msgid "On Ubuntu / Debian"
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml:13(simpara) ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml:23(simpara)
+msgid "RabbitMQ is packaged on both distros:"
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml:16(link)
+msgid "Official manual for installing RabbitMQ on Ubuntu / Debian"
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml:21(title)
+msgid "On Fedora / RHEL"
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml:26(link)
+msgid "Official manual for installing RabbitMQ on Fedora / RHEL"
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml:6(title)
+msgid "Configure RabbitMQ"
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml:8(simpara)
+msgid "Here we are building a cluster of RabbitMQ nodes to construct a RabbitMQ broker. Mirrored queues in RabbitMQ improve the availability of service since it will be resilient to failures. We have to consider that while exchanges and bindings will survive the loss of individual nodes, queues and their messages will not because a queue and its contents is located on one node. If we lose this node, we also lose the queue."
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml:13(simpara)
+msgid "We consider that we run (at least) two RabbitMQ servers. To build a broker, we need to ensure that all nodes have the same erlang cookie file. To do so, stop RabbitMQ everywhere and copy the cookie from rabbit1 server to other server(s):"
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml:18(simpara)
+msgid "Then, start RabbitMQ on nodes. If RabbitMQ fails to start, you can’t continue to the next step."
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml:20(simpara)
+msgid "Now, we are building the HA cluster. From rabbit2, run these commands:"
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml:24(simpara)
+msgid "To verify the cluster status :"
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml:29(simpara)
+msgid "If the cluster is working, you can now proceed to creating users and passwords for queues."
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml:31(emphasis)
+msgid "Note for RabbitMQ version 3"
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml:33(simpara)
+msgid "Queue mirroring is no longer controlled by the <emphasis>x-ha-policy</emphasis> argument when declaring a queue. OpenStack can continue to declare this argument, but it won’t cause queues to be mirrored. We need to make sure that all queues (except those with auto-generated names) are mirrored across all running nodes:"
+msgstr ""
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml:38(link)
+msgid "More information about High availability in RabbitMQ"
+msgstr ""
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml:6(title)
+msgid "Highly available neutron metadata agent"
+msgstr ""
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml:8(simpara)
+msgid "Neutron metadata agent allows Compute API metadata to be reachable by VMs on tenant networks. High availability for the metadata agent is achieved by adopting Pacemaker."
+msgstr ""
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml:12(simpara)
+msgid "Here is the <link href=\"http://docs.openstack.org/trunk/config-reference/content/networking-options-metadata.html\">documentation</link> for installing Neutron Metadata Agent."
+msgstr ""
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml:16(title)
+msgid "Add neutron metadata agent resource to Pacemaker"
+msgstr ""
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml:22(simpara)
+msgid "You may now proceed with adding the Pacemaker configuration for neutron metadata agent resource. Connect to the Pacemaker cluster with <literal>crm configure</literal>, and add the following cluster resources:"
+msgstr ""
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml:32(simpara)
+msgid "<literal>p_neutron-metadata-agent</literal>, a resource for manage Neutron Metadata Agent service"
+msgstr ""
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml:40(simpara)
+msgid "Once completed, commit your configuration changes by entering <literal>commit</literal> from the <literal>crm configure</literal> menu. Pacemaker will then start the neutron metadata agent service, and its dependent resources, on one of your nodes."
+msgstr ""
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml:6(title)
+msgid "Highly available neutron L3 agent"
+msgstr ""
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml:8(simpara)
+msgid "The neutron L3 agent provides L3/NAT forwarding to ensure external network access for VMs on tenant networks. High availability for the L3 agent is achieved by adopting Pacemaker."
+msgstr ""
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml:12(simpara)
+msgid "Here is the <link href=\"http://docs.openstack.org/trunk/config-reference/content/section_adv_cfg_l3_agent.html\">documentation</link> for installing neutron L3 agent."
+msgstr ""
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml:16(title)
+msgid "Add neutron L3 agent resource to Pacemaker"
+msgstr ""
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml:22(simpara)
+msgid "You may now proceed with adding the Pacemaker configuration for neutron L3 agent resource. Connect to the Pacemaker cluster with <literal>crm configure</literal>, and add the following cluster resources:"
+msgstr ""
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml:32(simpara)
+msgid "<literal>p_neutron-l3-agent</literal>, a resource for manage Neutron L3 Agent service"
+msgstr ""
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml:39(simpara)
+msgid "Once completed, commit your configuration changes by entering <literal>commit</literal> from the <literal>crm configure</literal> menu. Pacemaker will then start the neutron L3 agent service, and its dependent resources, on one of your nodes."
+msgstr ""
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml:43(simpara)
+msgid "This method does not ensure a zero downtime since it has to recreate all the namespaces and virtual routers on the node."
+msgstr ""
+
+#: ./doc/high-availability-guide/network/section_manage_network_resources.xml:6(title)
+msgid "Manage network resources"
+msgstr ""
+
+#: ./doc/high-availability-guide/network/section_manage_network_resources.xml:8(simpara)
+msgid "You can now add the Pacemaker configuration for managing all network resources together with a group. Connect to the Pacemaker cluster with <literal>crm configure</literal>, and add the following cluster resources:"
+msgstr ""
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml:6(title)
+msgid "Highly available neutron DHCP agent"
+msgstr ""
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml:8(simpara)
+msgid "Neutron DHCP agent distributes IP addresses to the VMs with dnsmasq (by default). High availability for the DHCP agent is achieved by adopting Pacemaker."
+msgstr ""
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml:12(simpara)
+msgid "Here is the <link href=\"http://docs.openstack.org/trunk/config-reference/content/section_adv_cfg_dhcp_agent.html\">documentation</link> for installing neutron DHCP agent."
+msgstr ""
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml:16(title)
+msgid "Add neutron DHCP agent resource to Pacemaker"
+msgstr ""
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml:22(simpara)
+msgid "You may now proceed with adding the Pacemaker configuration for neutron DHCP agent resource. Connect to the Pacemaker cluster with <literal>crm configure</literal>, and add the following cluster resources:"
+msgstr ""
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml:32(simpara)
+msgid "<literal>p_neutron-dhcp-agent</literal>, a resource for manage Neutron DHCP Agent service"
+msgstr ""
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml:40(simpara)
+msgid "Once completed, commit your configuration changes by entering <literal>commit</literal> from the <literal>crm configure</literal> menu. Pacemaker will then start the neutron DHCP agent service, and its dependent resources, on one of your nodes."
 msgstr ""
 
 #. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml:0(None)
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml:0(None)
 msgid "translator-credits"
 msgstr ""
 
diff --git a/doc/high-availability-guide/locale/ja.po b/doc/high-availability-guide/locale/ja.po
index a9cb92ad4a..72f27cc174 100644
--- a/doc/high-availability-guide/locale/ja.po
+++ b/doc/high-availability-guide/locale/ja.po
@@ -4,7 +4,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: OpenStack Manuals\n"
-"POT-Creation-Date: 2014-06-02 05:42+0000\n"
+"POT-Creation-Date: 2014-06-03 02:30+0000\n"
 "PO-Revision-Date: 2014-06-02 00:30+0000\n"
 "Last-Translator: Tomoyuki KATO <tomo@dream.daynight.jp>\n"
 "Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n"
@@ -14,25 +14,15 @@ msgstr ""
 "Language: ja\n"
 "Plural-Forms: nplurals=1; plural=0;\n"
 
-#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml6(title)
-msgid "OpenStack controller nodes"
-msgstr "OpenStack コントローラーノード"
+#: ./doc/high-availability-guide/ch_controller.xml6(title)
+msgid "Cloud controller cluster stack"
+msgstr "クラウドコントローラーのクラスタースタック"
 
-#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml8(simpara)
-msgid "OpenStack controller nodes contain:"
-msgstr "OpenStack コントローラーノードは次のものを含みます。"
-
-#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml11(simpara)
-msgid "All OpenStack API services"
-msgstr "すべての OpenStack API サービス"
-
-#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml16(simpara)
-msgid "All OpenStack schedulers"
-msgstr "すべての OpenStack スケジューラー"
-
-#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml21(simpara)
-msgid "Memcached service"
-msgstr "Memcached サービス"
+#: ./doc/high-availability-guide/ch_controller.xml8(simpara)
+msgid ""
+"The cloud controller runs on the management network and must talk to all "
+"other services."
+msgstr "クラウドコントローラーは、管理ネットワークで動作し、他のすべてのサービスと通信できる必要があります。"
 
 #: ./doc/high-availability-guide/ch_ha_aa_network.xml6(title)
 msgid "OpenStack network nodes"
@@ -71,35 +61,6 @@ msgid ""
 "highly available."
 msgstr "neutron L2 エージェントは高可用性にする必要がありません。各データ転送ノードにインストールされる必要があります。また、Open vSwitch または Linux Bridge として仮想ネットワークドライバーを制御します。1 つの L2 エージェントをノードごとに実行し、その仮想インターフェースを制御します。これが分散できず、高可用性にできない理由です。"
 
-#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml6(title)
-msgid "HAproxy nodes"
-msgstr "HAproxy ノード"
-
-#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml8(simpara)
-msgid ""
-"HAProxy is a very fast and reliable solution offering high availability, "
-"load balancing, and proxying for TCP and HTTP-based applications. It is "
-"particularly suited for web sites crawling under very high loads while "
-"needing persistence or Layer 7 processing. Supporting tens of thousands of "
-"connections is clearly realistic with today’s hardware."
-msgstr "HAProxy は高可用性、負荷分散、TCP と HTTP ベースのアプリケーションに対するプロキシを提供する非常に高速かつ信頼性のあるソリューションです。とくに永続性とレイヤー 7 処理を必要とする、非常に負荷の高いウェブサイトに適しています。数千の接続をサポートすることは、今日のハードウェアではかなり現実的です。"
-
-#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml12(simpara)
-msgid ""
-"For installing HAproxy on your nodes, you should consider its <link "
-"href=\"http://haproxy.1wt.eu/#docs\">official documentation</link>. Also, "
-"you have to consider that this service should not be a single point of "
-"failure, so you need at least two nodes running HAproxy."
-msgstr "ノードに HAproxy をインストールするために、<link href=\"http://haproxy.1wt.eu/#docs\">公式ドキュメント</link>を参照すべきです。また、このサービスが単一障害点にならないように、少なくとも 2 つのノードで HAproxy を実行すべきであることを考慮する必要があります。"
-
-#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml15(simpara)
-msgid "Here is an example for HAproxy configuration file:"
-msgstr "これは HAproxy 設定ファイルの例です。"
-
-#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml155(simpara)
-msgid "After each change of this file, you should restart HAproxy."
-msgstr "このファイルをそれぞれ変更した後、HAproxy を再起動しなければいけません。"
-
 #: ./doc/high-availability-guide/ch_pacemaker.xml6(title)
 msgid "The Pacemaker cluster stack"
 msgstr "Pacemaker クラスタースタック"
@@ -133,10 +94,6 @@ msgid ""
 "OpenStack Identity and Image Services)."
 msgstr "Pacemaker は <emphasis>リソースエージェント</emphasis> (RA) を経由してアプリケーションと通信します。これは標準で 70 近くのアプリケーションをサポートします。Pacemaker はサードパーティーの RA を簡単に使用することもできます。OpenStack の高可用性設定は、既存の標準の Pacemaker RA (MySQL データベースまたは仮想 IP アドレスの管理など)、既存のサードパーティー RA (RabbitMQ など)、および標準の OpenStack RA (OpenStack 認証サービスおよびイメージサービスなど) を使用します。"
 
-#: ./doc/high-availability-guide/part_active_passive.xml6(title)
-msgid "HA using active/passive"
-msgstr "アクティブ/パッシブを使用した HA"
-
 #: ./doc/high-availability-guide/ch_ha_aa_rabbitmq.xml6(title)
 msgid "RabbitMQ"
 msgstr "RabbitMQ"
@@ -160,103 +117,6 @@ msgstr "高可用性 キュー用の RabbitMQ の設定"
 msgid "Configure OpenStack services to use Rabbit HA queues"
 msgstr "RabbitMQ HA キューを使用するための OpenStack サービスの設定"
 
-#: ./doc/high-availability-guide/bk-ha-guide.xml8(title)
-msgid "OpenStack High Availability Guide"
-msgstr "OpenStack 高可用性ガイド"
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml11(firstname)
-msgid "Florian"
-msgstr "Florian"
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml12(surname)
-msgid "Haas"
-msgstr "Haas"
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml14(email)
-msgid "florian@hastexo.com"
-msgstr "florian@hastexo.com"
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml16(orgname)
-msgid "hastexo"
-msgstr "hastexo"
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml20(year)
-msgid "2012"
-msgstr "2012"
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml21(year)
-msgid "2013"
-msgstr "2013"
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml22(year)
-msgid "2014"
-msgstr "2014"
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml23(holder)
-msgid "OpenStack Contributors"
-msgstr "OpenStack 貢献者"
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml25(releaseinfo)
-msgid "current"
-msgstr "カレント"
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml26(productname)
-msgid "OpenStack"
-msgstr "OpenStack"
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml30(remark)
-msgid "Copyright details are filled in by the template."
-msgstr "Copyright details are filled in by the template."
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml34(para)
-msgid ""
-"This guide describes how to install, configure, and manage OpenStack for "
-"high availability."
-msgstr "このガイドは、高可用性 OpenStack をインストール、設定、管理する方法について記載します。"
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml39(date)
-msgid "2014-05-16"
-msgstr "2014-05-16"
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml43(para)
-msgid "Conversion to Docbook."
-msgstr "Docbook 形式への変換。"
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml49(date)
-msgid "2014-04-17"
-msgstr "2014-04-17"
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml53(para)
-msgid ""
-"Minor cleanup of typos, otherwise no major revisions for Icehouse release."
-msgstr "誤字脱字の軽微な修正。Icehouse リリース向けの大きな改版はありません。"
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml60(date)
-msgid "2012-01-16"
-msgstr "2012-01-16"
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml64(para)
-msgid "Organizes guide based on cloud controller and compute nodes."
-msgstr "クラウドコントローラーとコンピュートノードに基づいてガイドを整理しました。"
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml70(date)
-msgid "2012-05-24"
-msgstr "2012-05-24"
-
-#: ./doc/high-availability-guide/bk-ha-guide.xml74(para)
-msgid "Begin trunk designation."
-msgstr "trunk 指定を始めました。"
-
-#: ./doc/high-availability-guide/ch_controller.xml6(title)
-msgid "Cloud controller cluster stack"
-msgstr "クラウドコントローラーのクラスタースタック"
-
-#: ./doc/high-availability-guide/ch_controller.xml8(simpara)
-msgid ""
-"The cloud controller runs on the management network and must talk to all "
-"other services."
-msgstr "クラウドコントローラーは、管理ネットワークで動作し、他のすべてのサービスと通信できる必要があります。"
-
 #: ./doc/high-availability-guide/ch_intro.xml6(title)
 msgid "Introduction to OpenStack High Availability"
 msgstr "OpenStack 高可用性の概要"
@@ -438,6 +298,93 @@ msgid ""
 "of the more common options for highly available systems."
 msgstr "これらの高可用性アーキテクチャーを実現する、より一般的な方法がいくつかありますが、それらは唯一の方法ではありません。重要なことは、サービスが冗長であり、利用可能であることを確実にすることです。あなたがしたいように達成します。このドキュメントは高可用性システムのより一般的なオプションをいくつか取り扱います。"
 
+#: ./doc/high-availability-guide/bk-ha-guide.xml8(title)
+msgid "OpenStack High Availability Guide"
+msgstr "OpenStack 高可用性ガイド"
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml11(firstname)
+msgid "Florian"
+msgstr "Florian"
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml12(surname)
+msgid "Haas"
+msgstr "Haas"
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml14(email)
+msgid "florian@hastexo.com"
+msgstr "florian@hastexo.com"
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml16(orgname)
+msgid "hastexo"
+msgstr "hastexo"
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml20(year)
+msgid "2012"
+msgstr "2012"
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml21(year)
+msgid "2013"
+msgstr "2013"
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml22(year)
+msgid "2014"
+msgstr "2014"
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml23(holder)
+msgid "OpenStack Contributors"
+msgstr "OpenStack 貢献者"
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml25(releaseinfo)
+msgid "current"
+msgstr "カレント"
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml26(productname)
+msgid "OpenStack"
+msgstr "OpenStack"
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml30(remark)
+msgid "Copyright details are filled in by the template."
+msgstr "Copyright details are filled in by the template."
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml34(para)
+msgid ""
+"This guide describes how to install, configure, and manage OpenStack for "
+"high availability."
+msgstr "このガイドは、高可用性 OpenStack をインストール、設定、管理する方法について記載します。"
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml39(date)
+msgid "2014-05-16"
+msgstr "2014-05-16"
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml43(para)
+msgid "Conversion to Docbook."
+msgstr "Docbook 形式への変換。"
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml49(date)
+msgid "2014-04-17"
+msgstr "2014-04-17"
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml53(para)
+msgid ""
+"Minor cleanup of typos, otherwise no major revisions for Icehouse release."
+msgstr "誤字脱字の軽微な修正。Icehouse リリース向けの大きな改版はありません。"
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml60(date)
+msgid "2012-01-16"
+msgstr "2012-01-16"
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml64(para)
+msgid "Organizes guide based on cloud controller and compute nodes."
+msgstr "クラウドコントローラーとコンピュートノードに基づいてガイドを整理しました。"
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml70(date)
+msgid "2012-05-24"
+msgstr "2012-05-24"
+
+#: ./doc/high-availability-guide/bk-ha-guide.xml74(para)
+msgid "Begin trunk designation."
+msgstr "trunk 指定を始めました。"
+
 #: ./doc/high-availability-guide/ch_network.xml6(title)
 msgid "Network controller cluster stack"
 msgstr "ネットワークコントローラーのクラスタースタック"
@@ -455,9 +402,58 @@ msgid ""
 "node."
 msgstr "Networking スケジューラーが 1 つのノードに認識するよう、両方のノードが同じホスト名を持つべきです。たとえば、単一の L3 ノードに接続された仮想ルーターです。"
 
-#: ./doc/high-availability-guide/part_active_active.xml6(title)
-msgid "HA using active/active"
-msgstr "アクティブ/アクティブを使用した HA"
+#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml6(title)
+msgid "HAproxy nodes"
+msgstr "HAproxy ノード"
+
+#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml8(simpara)
+msgid ""
+"HAProxy is a very fast and reliable solution offering high availability, "
+"load balancing, and proxying for TCP and HTTP-based applications. It is "
+"particularly suited for web sites crawling under very high loads while "
+"needing persistence or Layer 7 processing. Supporting tens of thousands of "
+"connections is clearly realistic with today’s hardware."
+msgstr "HAProxy は高可用性、負荷分散、TCP と HTTP ベースのアプリケーションに対するプロキシを提供する非常に高速かつ信頼性のあるソリューションです。とくに永続性とレイヤー 7 処理を必要とする、非常に負荷の高いウェブサイトに適しています。数千の接続をサポートすることは、今日のハードウェアではかなり現実的です。"
+
+#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml12(simpara)
+msgid ""
+"For installing HAproxy on your nodes, you should consider its <link "
+"href=\"http://haproxy.1wt.eu/#docs\">official documentation</link>. Also, "
+"you have to consider that this service should not be a single point of "
+"failure, so you need at least two nodes running HAproxy."
+msgstr "ノードに HAproxy をインストールするために、<link href=\"http://haproxy.1wt.eu/#docs\">公式ドキュメント</link>を参照すべきです。また、このサービスが単一障害点にならないように、少なくとも 2 つのノードで HAproxy を実行すべきであることを考慮する必要があります。"
+
+#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml15(simpara)
+msgid "Here is an example for HAproxy configuration file:"
+msgstr "これは HAproxy 設定ファイルの例です。"
+
+#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml155(simpara)
+msgid "After each change of this file, you should restart HAproxy."
+msgstr "このファイルをそれぞれ変更した後、HAproxy を再起動しなければいけません。"
+
+#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml6(title)
+msgid "OpenStack controller nodes"
+msgstr "OpenStack コントローラーノード"
+
+#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml8(simpara)
+msgid "OpenStack controller nodes contain:"
+msgstr "OpenStack コントローラーノードは次のものを含みます。"
+
+#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml11(simpara)
+msgid "All OpenStack API services"
+msgstr "すべての OpenStack API サービス"
+
+#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml16(simpara)
+msgid "All OpenStack schedulers"
+msgstr "すべての OpenStack スケジューラー"
+
+#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml21(simpara)
+msgid "Memcached service"
+msgstr "Memcached サービス"
+
+#: ./doc/high-availability-guide/part_active_passive.xml6(title)
+msgid "HA using active/passive"
+msgstr "アクティブ/パッシブを使用した HA"
 
 #: ./doc/high-availability-guide/ch_api.xml6(title)
 msgid "API node cluster stack"
@@ -489,1269 +485,9 @@ msgid ""
 "installations, so we’ll cover it here."
 msgstr "データベースの選択は決められたものではありません。必ずしも MySQL を使用する必要がありません。しかしながら、OpenStack のインストール環境ではかなり一般的な選択肢であるため、ここでは MySQL を取り扱います。"
 
-#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml6(title)
-msgid "Starting Corosync"
-msgstr "Corosync の開始"
-
-#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml8(simpara)
-msgid ""
-"Corosync is started as a regular system service. Depending on your "
-"distribution, it may ship with a LSB (System V style) init script, an "
-"upstart job, or a systemd unit file. Either way, the service is usually "
-"named <literal>corosync</literal>:"
-msgstr "Corosync は通常のシステムサービスとして開始されます。お使いのディストリビューションにより、LSB (System V 形式) init スクリプト、upstart ジョブ、または systemd ユニットファイルが同梱されています。どの方法においても、サービスは通常 <literal>corosync</literal> という名前です:"
-
-#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml14(simpara)
-msgid "<literal>/etc/init.d/corosync start</literal> (LSB)"
-msgstr "<literal>/etc/init.d/corosync start</literal> (LSB)"
-
-#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml18(simpara)
-msgid "<literal>service corosync start</literal> (LSB, alternate)"
-msgstr "<literal>service corosync start</literal> (LSB, 代替)"
-
-#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml22(simpara)
-msgid "<literal>start corosync</literal> (upstart)"
-msgstr "<literal>start corosync</literal> (upstart)"
-
-#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml26(simpara)
-msgid "<literal>systemctl start corosync</literal> (systemd)"
-msgstr "<literal>systemctl start corosync</literal> (systemd)"
-
-#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml30(simpara)
-msgid "You can now check the Corosync connectivity with two tools."
-msgstr "2 つのツールを用いて Corosync 接続性を確認できます。"
-
-#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml31(simpara)
-msgid ""
-"The <literal>corosync-cfgtool</literal> utility, when invoked with the "
-"<literal>-s</literal> option, gives a summary of the health of the "
-"communication rings:"
-msgstr "<literal>corosync-cfgtool</literal> ユーティリティは、<literal>-s</literal> オプションを用いるとき、通信リングの健全性の概要を表示します:"
-
-#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml42(simpara)
-msgid ""
-"The <literal>corosync-objctl</literal> utility can be used to dump the "
-"Corosync cluster member list:"
-msgstr "<literal>corosync-objctl</literal> ユーティリティは Corosync クラスターのメンバー一覧をダンプするために使用できます:"
-
-#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml51(simpara)
-msgid ""
-"You should see a <literal>status=joined</literal> entry for each of your "
-"constituent cluster nodes."
-msgstr "組み込まれているそれぞれのクラスターノードの項目が <literal>status=joined</literal> になっていることが確認できるはずです。"
-
-#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml6(title)
-msgid "Set up Corosync"
-msgstr "Corosync のセットアップ"
-
-#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml8(simpara)
-msgid ""
-"Besides installing the <literal>corosync</literal> package, you must also "
-"create a configuration file, stored in "
-"<literal>/etc/corosync/corosync.conf</literal>. Most distributions ship an "
-"example configuration file (<literal>corosync.conf.example</literal>) as "
-"part of the documentation bundled with the <literal>corosync</literal> "
-"package. An example Corosync configuration file is shown below:"
-msgstr "<literal>corosync</literal> パッケージのインストールに関連して、<literal>/etc/corosync/corosync.conf</literal> に保存する、設定ファイルを作成する必要があります。多くのディストリビューションは、<literal>corosync</literal> パッケージに同梱されているドキュメントの一部として、サンプル設定ファイル (<literal>corosync.conf.example</literal>) が同梱されています。サンプルの Corosync 設定ファイルを以下に示します:"
-
-#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml16(title)
-msgid "Corosync configuration file (<literal>corosync.conf</literal>)"
-msgstr "Corosync 設定ファイル (<literal>corosync.conf</literal>)"
-
-#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml90(para)
-msgid ""
-"The <literal>token</literal> value specifies the time, in milliseconds, "
-"during which the Corosync token is expected to be transmitted around the "
-"ring. When this timeout expires, the token is declared lost, and after "
-"<literal>token_retransmits_before_loss_const</literal> lost tokens the non-"
-"responding <emphasis>processor</emphasis> (cluster node) is declared dead. "
-"In other words, <literal>token</literal> × "
-"<literal>token_retransmits_before_loss_const</literal> is the maximum time a"
-" node is allowed to not respond to cluster messages before being considered "
-"dead. The default for <literal>token</literal> is 1000 (1 second), with 4 "
-"allowed retransmits. These defaults are intended to minimize failover times,"
-" but can cause frequent \"false alarms\" and unintended failovers in case of"
-" short network interruptions. The values used here are safer, albeit with "
-"slightly extended failover times."
-msgstr "<literal>token</literal> の値は、Corosync トークンがリングを 1 周するまでの時間をミリ秒単位で指定します。このタイムアウトを経過した場合、トークンが消失したと判定します。<literal>token_retransmits_before_loss_const</literal> はトークンを失った後、応答のない <emphasis>processor</emphasis> (クラスターノード) が障害と判定されます。言い換えると、<literal>token</literal> × <literal>token_retransmits_before_loss_const</literal> が、ノードが障害と判定されるまでに、クラスターメッセージに応答しなくてもよい最大時間です。 <literal>token</literal> の規定値は 1000 (1 秒) で、再送 が 4 回まで許可されます。これらの規定値は、フェイルオーバー時間を最小化する狙いですが、頻繁に「誤報」を起こし、短時間のネットワーク障害により意図せずフェイルオーバーする可能性があります。ここで使用されている値は、フェイルオーバー時間をわずかに延ばしたとしても、より安全なものです。"
-
-#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml106(para)
-msgid ""
-"With <literal>secauth</literal> enabled, Corosync nodes mutually "
-"authenticate using a 128-byte shared secret stored in "
-"<literal>/etc/corosync/authkey</literal>, which may be generated with the "
-"<literal>corosync-keygen</literal> utility. When using "
-"<literal>secauth</literal>, cluster communications are also encrypted."
-msgstr "<literal>secauth</literal> を有効化している場合、Corosync ノードは <literal>/etc/corosync/authkey</literal> に保存されている 128 ビットの共有シークレットを使用して相互に認証します。このシークレットは <literal>corosync-keygen</literal> ユーティリティを用いて生成できます。<literal>secauth</literal> を使用するとき、クラスター通信も暗号化されます。"
-
-#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml114(para)
-msgid ""
-"In Corosync configurations using redundant networking (with more than one "
-"<literal>interface</literal>), you must select a Redundant Ring Protocol "
-"(RRP) mode other than <literal>none</literal>. <literal>active</literal> is "
-"the recommended RRP mode."
-msgstr "冗長ネットワーク (複数の <literal>interface</literal>) を使用した Corosync 設定の場合、Redundant Ring Protocol (RRP) モードを <literal>none</literal> 以外で選択する必要があります。<literal>active</literal> が推奨 RRP モードです。"
-
-#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml121(para)
-msgid ""
-"There are several things to note about the recommended interface "
-"configuration:"
-msgstr "インターフェースの推奨設定に関する注意事項がいくつかあります。"
-
-#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml127(simpara)
-msgid ""
-"The <literal>ringnumber</literal> must differ between all configured "
-"interfaces, starting with 0."
-msgstr "<literal>ringnumber</literal> はすべての設定済みインターフェースで異なる必要があります。0 から始まります。"
-
-#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml133(simpara)
-msgid ""
-"The <literal>bindnetaddr</literal> is the <emphasis>network</emphasis> "
-"address of the interfaces to bind to. The example uses two network addresses"
-" of <literal>/24</literal> IPv4 subnets."
-msgstr "<literal>bindnetaddr</literal> はバインドするインターフェースの<emphasis>ネットワーク</emphasis>アドレスです。この例は二つの <literal>/24</literal> IPv4 サブネットのネットワークアドレスを使用します。"
-
-#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml139(simpara)
-msgid ""
-"Multicast groups (<literal>mcastaddr</literal>) <emphasis>must "
-"not</emphasis> be reused across cluster boundaries. In other words, no two "
-"distinct clusters should ever use the same multicast group. Be sure to "
-"select multicast addresses compliant with <link "
-"href=\"http://www.ietf.org/rfc/rfc2365.txt\">RFC 2365, \"Administratively "
-"Scoped IP Multicast\"</link>."
-msgstr "マルチキャストグループ (<literal>mcastaddr</literal>) は、クラスターの境界をまたがって再利用できません。違い言い方をすると、2 つの別のクラスターは同じマルチキャストグループを使用できません。<link href=\"http://www.ietf.org/rfc/rfc2365.txt\">RFC 2365, \"Administratively Scoped IP Multicast\"</link> に適合しているマルチキャストアドレスを必ず選択してください。"
-
-#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml148(simpara)
-msgid ""
-"For firewall configurations, note that Corosync communicates over UDP only, "
-"and uses <literal>mcastport</literal> (for receives) and "
-"<literal>mcastport</literal>-1 (for sends)."
-msgstr "ファイアウォール設定に関して、Corosync は UDP のみを使用して通信し、<literal>mcastport</literal> (受信用) と <literal>mcastport</literal>-1 (送信用) を使用することに注意してください。"
-
-#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml157(para)
-msgid ""
-"The <literal>service</literal> declaration for the "
-"<literal>pacemaker</literal> service may be placed in the "
-"<literal>corosync.conf</literal> file directly, or in its own separate file,"
-" <literal>/etc/corosync/service.d/pacemaker</literal>."
-msgstr "<literal>pacemaker</literal> サービスに関する <literal>service</literal> 宣言は、<literal>corosync.conf</literal> ファイルに直接置かれるか、別のファイル <literal>/etc/corosync/service.d/pacemaker</literal> に置かれるかもしれません。"
-
-#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml164(simpara)
-msgid ""
-"Once created, the <literal>corosync.conf</literal> file (and the "
-"<literal>authkey</literal> file if the <literal>secauth</literal> option is "
-"enabled) must be synchronized across all cluster nodes."
-msgstr "一度作成すると、<literal>corosync.conf</literal> ファイル (および、<literal>secauth</literal> オプションが有効化されている場合は <literal>authkey</literal> ファイル) はすべてのクラスターノードで同期する必要があります。"
-
-#: ./doc/high-availability-guide/pacemaker/section_set_basic_cluster_properties.xml6(title)
-msgid "Set basic cluster properties"
-msgstr "基本的なクラスターのプロパティの設定"
-
-#: ./doc/high-availability-guide/pacemaker/section_set_basic_cluster_properties.xml8(simpara)
-msgid ""
-"Once your Pacemaker cluster is set up, it is recommended to set a few basic "
-"cluster properties. To do so, start the <literal>crm</literal> shell and "
-"change into the configuration menu by entering <literal>configure</literal>."
-" Alternatively. you may jump straight into the Pacemaker configuration menu "
-"by typing <literal>crm configure</literal> directly from a shell prompt."
-msgstr "Pacemaker クラスターを構築すると、いくつかの基本的なクラスタープロパティを設定することを推奨します。そうするために、<literal>crm</literal> シェルを開始し、<literal>configure</literal> と入力して設定メニューに変更します。代わりに、シェルプロンプトから直接 <literal>crm configure</literal> と入力して、Pacemaker 設定メニューに入ることもできます。"
-
-#: ./doc/high-availability-guide/pacemaker/section_set_basic_cluster_properties.xml14(simpara)
-msgid "Then, set the following properties:"
-msgstr "そして、以下のプロパティを設定します。"
-
-#: ./doc/high-availability-guide/pacemaker/section_set_basic_cluster_properties.xml22(para)
-msgid ""
-"Setting <literal>no-quorum-policy=\"ignore\"</literal> is required in 2-node"
-" Pacemaker clusters for the following reason: if quorum enforcement is "
-"enabled, and one of the two nodes fails, then the remaining node can not "
-"establish a <emphasis>majority</emphasis> of quorum votes necessary to run "
-"services, and thus it is unable to take over any resources. The appropriate "
-"workaround is to ignore loss of quorum in the cluster. This is safe and "
-"necessary <emphasis>only</emphasis> in 2-node clusters. Do not set this "
-"property in Pacemaker clusters with more than two nodes."
-msgstr "2 ノード Pacemaker クラスターの場合、以下の理由により <literal>no-quorum-policy=\"ignore\"</literal> の設定が必要になります。クォーラム強制が有効化されていると、2 ノードのどちらかに障害が発生した場合、残りのノードがサービスの実行に必要なクォーラムの<emphasis>過半数</emphasis>を獲得できなくなります。そのため、あらゆるリソースがテイクオーバーできません。適切な回避策は、クラスターでクォーラムの損失を無視することです。これは 2 ノードクラスター<emphasis>のみ</emphasis>で安全であり、必要になります。2 ノードより多い Pacemaker クラスターでは、このプロパティを設定してはいけません。"
-
-#: ./doc/high-availability-guide/pacemaker/section_set_basic_cluster_properties.xml34(para)
-msgid ""
-"Setting <literal>pe-warn-series-max</literal>, <literal>pe-input-series-"
-"max</literal> and <literal>pe-error-series-max</literal> to 1000 instructs "
-"Pacemaker to keep a longer history of the inputs processed, and errors and "
-"warnings generated, by its Policy Engine. This history is typically useful "
-"in case cluster troubleshooting becomes necessary."
-msgstr "<literal>pe-warn-series-max</literal>、<literal>pe-input-series-max</literal> および <literal>pe-error-series-max</literal> を 1000 に設定することにより、Pacemaker のポリシーエンジンにより、処理された入力、生成されたエラーと警告の履歴をより長く保持するよう Pacemaker に指示します。この履歴は一般的にクラスターのトラブルシューティングが必要となる場合に役に立ちます。"
-
-#: ./doc/high-availability-guide/pacemaker/section_set_basic_cluster_properties.xml43(para)
-msgid ""
-"Pacemaker uses an event-driven approach to cluster state processing. "
-"However, certain Pacemaker actions occur at a configurable interval, "
-"<literal>cluster-recheck-interval</literal>, which defaults to 15 minutes. "
-"It is usually prudent to reduce this to a shorter interval, such as 5 or 3 "
-"minutes."
-msgstr "Pacemaker はクラスター状態の処理にイベント駆動の方法を使用します。しかしながら、特定の Pacemaker アクションは、設定可能な間隔 <literal>cluster-recheck-interval</literal> で発生します。このデフォルトは 15 分です。一般的に 5 分や 3 分のようにより短い間隔にこれを慎重に減らします。"
-
-#: ./doc/high-availability-guide/pacemaker/section_set_basic_cluster_properties.xml52(simpara)
-msgid ""
-"Once you have made these changes, you may <literal>commit</literal> the "
-"updated configuration."
-msgstr "これらの変更を実行すると、更新した設定を <literal>commit</literal> できます。"
-
-#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml6(title)
-msgid "Install packages"
-msgstr "パッケージのインストール"
-
-#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml8(simpara)
-msgid ""
-"On any host that is meant to be part of a Pacemaker cluster, you must first "
-"establish cluster communications through the Corosync messaging layer. This "
-"involves Install the following packages (and their dependencies, which your "
-"package manager will normally install automatically):"
-msgstr "Pacemaker クラスターに参加させるすべてのホストにおいて、まず Corosync メッセージング層によるクラスター通信を確立する必要があります。これは、以下のパッケージをインストールする必要があります (また通常、パッケージ管理ソフトウェアが自動的にそれらに依存するものをインストールします)。"
-
-#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml15(simpara)
-msgid ""
-"<literal>pacemaker</literal> Note that the crm shell should be downloaded "
-"separately."
-msgstr "<literal>pacemaker</literal> は crm シェルを別途ダウンロードする必要があることに注意してください。"
-
-#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml20(literal)
-msgid "crmsh"
-msgstr "crmsh"
-
-#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml25(literal)
-msgid "corosync"
-msgstr "corosync"
-
-#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml30(literal)
-msgid "cluster-glue"
-msgstr "cluster-glue"
-
-#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml34(simpara)
-msgid ""
-"<literal>fence-agents</literal> (Fedora only; all other distributions use "
-"fencing agents from <literal>cluster-glue</literal>)"
-msgstr "<literal>fence-agents</literal> (Fedora のみ、他のすべてのディストリビューションは <literal>cluster-glue</literal> からフェンシング・エージェントを使用します)"
-
-#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml40(literal)
-msgid "resource-agents"
-msgstr "resource-agents"
-
-#: ./doc/high-availability-guide/pacemaker/section_start_pacemaker.xml6(title)
-msgid "Start Pacemaker"
-msgstr "Pacemaker の開始"
-
-#: ./doc/high-availability-guide/pacemaker/section_start_pacemaker.xml8(simpara)
-msgid ""
-"Once the Corosync services have been started, and you have established that "
-"the cluster is communicating properly, it is safe to start "
-"<literal>pacemakerd</literal>, the Pacemaker master control process:"
-msgstr "Corosync サービスが開始されると、クラスターが適切に通信するよう設定されます。<literal>pacemakerd</literal>, Pacemaker マスター制御プロセスを安全に開始されます:"
-
-#: ./doc/high-availability-guide/pacemaker/section_start_pacemaker.xml13(simpara)
-msgid "<literal>/etc/init.d/pacemaker start</literal> (LSB)"
-msgstr "<literal>/etc/init.d/pacemaker start</literal> (LSB)"
-
-#: ./doc/high-availability-guide/pacemaker/section_start_pacemaker.xml17(simpara)
-msgid "<literal>service pacemaker start</literal> (LSB, alternate)"
-msgstr "<literal>service pacemaker start</literal> (LSB, 代替)"
-
-#: ./doc/high-availability-guide/pacemaker/section_start_pacemaker.xml21(simpara)
-msgid "<literal>start pacemaker</literal> (upstart)"
-msgstr "<literal>start pacemaker</literal> (upstart)"
-
-#: ./doc/high-availability-guide/pacemaker/section_start_pacemaker.xml25(simpara)
-msgid "<literal>systemctl start pacemaker</literal> (systemd)"
-msgstr "<literal>systemctl start pacemaker</literal> (systemd)"
-
-#: ./doc/high-availability-guide/pacemaker/section_start_pacemaker.xml29(simpara)
-msgid ""
-"Once Pacemaker services have started, Pacemaker will create a default empty "
-"cluster configuration with no resources. You may observe Pacemaker’s status "
-"with the <literal>crm_mon</literal> utility:"
-msgstr "Pacemaker サービスが開始されると、Pacemaker はリソースを持たない空の標準クラスター設定を作成します。<literal>crm_mon</literal> ユーティリティを用いて Pacemaker の状態を確認できます。"
-
-#: ./doc/high-availability-guide/api/section_keystone.xml6(title)
-msgid "Highly available OpenStack Identity"
-msgstr "高可用性 OpenStack Identity"
-
-#: ./doc/high-availability-guide/api/section_keystone.xml8(simpara)
-msgid ""
-"OpenStack Identity is the Identity Service in OpenStack and used by many "
-"services. Making the OpenStack Identity service highly available in active /"
-" passive mode involves"
-msgstr "OpenStack Identity は OpenStack における認証サービスです。OpenStack Identity Service をアクティブ / パッシブモードで高可用性にすることは、次のことが関連します。"
-
-#: ./doc/high-availability-guide/api/section_keystone.xml12(simpara)
-msgid "Configure OpenStack Identity to listen on the VIP address,"
-msgstr "OpenStack Identity がその仮想 IP アドレスでリッスンするよう設定します。"
-
-#: ./doc/high-availability-guide/api/section_keystone.xml17(simpara)
-msgid "managing OpenStack Identity daemon with the Pacemaker cluster manager,"
-msgstr "Pacemaker クラスターマネージャーを用いた OpenStack Identity デーモンの管理"
-
-#: ./doc/high-availability-guide/api/section_keystone.xml22(simpara)
-#: ./doc/high-availability-guide/api/section_cinder_api.xml21(simpara)
-#: ./doc/high-availability-guide/api/section_neutron_server.xml22(simpara)
-#: ./doc/high-availability-guide/api/section_glance_api.xml22(simpara)
-msgid "Configure OpenStack services to use this IP address."
-msgstr "OpenStack のサービスがこの IP アドレスを使用するよう設定します。"
-
-#: ./doc/high-availability-guide/api/section_keystone.xml28(simpara)
-msgid ""
-"Here is the <link href=\"http://docs.openstack.org/trunk/install-"
-"guide/install/apt/content/ch_installing-openstack-identity-"
-"service.html\">documentation</link> for installing OpenStack Identity "
-"service."
-msgstr "ここに OpenStack Identity Service をインストールするための<link href=\"http://docs.openstack.org/trunk/install-guide/install/apt/content/ch_installing-openstack-identity-service.html\">ドキュメント</link>があります。"
-
-#: ./doc/high-availability-guide/api/section_keystone.xml32(title)
-msgid "Add OpenStack Identity resource to Pacemaker"
-msgstr "OpenStack Identity リソースの Pacemaker への追加"
-
-#: ./doc/high-availability-guide/api/section_keystone.xml34(simpara)
-#: ./doc/high-availability-guide/api/section_cinder_api.xml35(simpara)
-#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml26(simpara)
-#: ./doc/high-availability-guide/api/section_neutron_server.xml34(simpara)
-#: ./doc/high-availability-guide/api/section_glance_api.xml34(simpara)
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml18(simpara)
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml18(simpara)
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml18(simpara)
-msgid "First of all, you need to download the resource agent to your system:"
-msgstr "まず初めに、リソースエージェントをシステムにダウンロードする必要があります。"
-
-#: ./doc/high-availability-guide/api/section_keystone.xml40(simpara)
-msgid ""
-"You can now add the Pacemaker configuration for OpenStack Identity resource."
-" Connect to the Pacemaker cluster with <literal>crm configure</literal>, and"
-" add the following cluster resources:"
-msgstr "OpenStack Identity リソース用の Pacemaker 設定を追加できます。<literal>crm configure</literal> を用いて Pacemaker クラスターに接続し、以下のクラスターリソースを追加します。"
-
-#: ./doc/high-availability-guide/api/section_keystone.xml46(simpara)
-msgid ""
-"This configuration creates <literal>p_keystone</literal>, a resource for "
-"managing the OpenStack Identity service."
-msgstr "この設定は OpenStack Identity サービスを管理するためのリソース <literal>p_keystone</literal> を作成します。"
-
-#: ./doc/high-availability-guide/api/section_keystone.xml47(simpara)
-msgid ""
-"<literal>crm configure</literal> supports batch input, so you may copy and "
-"paste the above into your live pacemaker configuration, and then make "
-"changes as required. For example, you may enter <literal>edit "
-"p_ip_keystone</literal> from the <literal>crm configure</literal> menu and "
-"edit the resource to match your preferred virtual IP address."
-msgstr "<literal>crm configure</literal> はバッチ入力をサポートします。そのため、現在の pacemaker 設定の中に上をコピー・ペーストし、適宜変更を反映できます。たとえば、お好みの仮想 IP アドレスに一致させるために、<literal>crm configure</literal> メニューから <literal>edit p_ip_keystone</literal> と入力し、リソースを編集できます。"
-
-#: ./doc/high-availability-guide/api/section_keystone.xml52(simpara)
-msgid ""
-"Once completed, commit your configuration changes by entering "
-"<literal>commit</literal> from the <literal>crm configure</literal> menu. "
-"Pacemaker will then start the OpenStack Identity service, and its dependent "
-"resources, on one of your nodes."
-msgstr "完了すると、<literal>crm configure</literal> メニューから <literal>commit</literal> と入力し、設定の変更をコミットします。Pacemaker は OpenStack Identity サービスおよび依存するリソースを同じノードに起動します。"
-
-#: ./doc/high-availability-guide/api/section_keystone.xml58(title)
-msgid "Configure OpenStack Identity service"
-msgstr "OpenStack Identity Service の設定"
-
-#: ./doc/high-availability-guide/api/section_keystone.xml60(simpara)
-msgid ""
-"You need to edit your OpenStack Identity configuration file "
-"(<literal>keystone.conf</literal>) and change the bind parameters:"
-msgstr "OpenStack Identity の設定ファイル (<literal>keystone.conf</literal>) を編集し、バインドのパラメーターを変更する必要があります。"
-
-#: ./doc/high-availability-guide/api/section_keystone.xml61(simpara)
-msgid "On Havana:"
-msgstr "Havana の場合:"
-
-#: ./doc/high-availability-guide/api/section_keystone.xml63(simpara)
-msgid ""
-"On Icehouse, the <literal>admin_bind_host</literal> option lets you use a "
-"private network for the admin access."
-msgstr "Icehouse の場合、<literal>admin_bind_host</literal> オプションにより管理アクセス用のプライベートネットワークを使用できます。"
-
-#: ./doc/high-availability-guide/api/section_keystone.xml66(simpara)
-msgid ""
-"To be sure all data will be highly available, you should be sure that you "
-"store everything in the MySQL database (which is also highly available):"
-msgstr "確実にすべてのデータが高可用性にするために、確実にすべてのものを (高可用性な) MySQL データベースに保存すべきです。"
-
-#: ./doc/high-availability-guide/api/section_keystone.xml76(title)
-msgid ""
-"Configure OpenStack services to use the highly available OpenStack Identity"
-msgstr "高可用性 OpenStack Identity を使用するための OpenStack サービスの設定"
-
-#: ./doc/high-availability-guide/api/section_keystone.xml78(simpara)
-msgid ""
-"Your OpenStack services must now point their OpenStack Identity "
-"configuration to the highly available, virtual cluster IP address — rather "
-"than a OpenStack Identity server’s physical IP address as you normally "
-"would."
-msgstr "OpenStack サービスは、通常どおり OpenStack Identity サーバーの物理 IP アドレスを指定する代わりに、OpenStack Identity サーバーの設定が高可用性と仮想クラスター IP アドレスを指し示す必要があります。"
-
-#: ./doc/high-availability-guide/api/section_keystone.xml81(simpara)
-msgid ""
-"For example with OpenStack Compute, if your OpenStack Identity service IP "
-"address is 192.168.42.103 as in the configuration explained here, you would "
-"use the following line in your API configuration file (<literal>api-"
-"paste.ini</literal>):"
-msgstr "OpenStack Compute を用いた例として、OpenStack Identity Service の IP アドレスがここで説明された設定にあるように 192.168.42.103 ならば、API 設定ファイル (<literal>api-paste.ini</literal>) で以下の行を使用する必要があります。"
-
-#: ./doc/high-availability-guide/api/section_keystone.xml86(simpara)
-msgid "You also need to create the OpenStack Identity Endpoint with this IP."
-msgstr "この IP を用いて OpenStack Identity エンドポイントを作成する必要があります。"
-
-#: ./doc/high-availability-guide/api/section_keystone.xml87(simpara)
-msgid ""
-"NOTE : If you are using both private and public IP addresses, you should "
-"create two Virtual IP addresses and define your endpoint like this:"
-msgstr "注: プライベート IP とパブリック IP の両方を使用する場合、2 つの仮想 IP アドレスを作成し、次のようにエンドポイントを定義すべきです。"
-
-#: ./doc/high-availability-guide/api/section_keystone.xml89(simpara)
-msgid ""
-"If you are using the horizon dashboard, you should edit the "
-"<literal>local_settings.py</literal> file:"
-msgstr "Dashboard を使用している場合、<literal>local_settings.py</literal> ファイルを編集する必要があります。"
-
-#: ./doc/high-availability-guide/api/section_api_vip.xml6(title)
-msgid "Configure the VIP"
-msgstr "仮想 IP の設定"
-
-#: ./doc/high-availability-guide/api/section_api_vip.xml8(simpara)
-msgid ""
-"First, you must select and assign a virtual IP address (VIP) that can freely"
-" float between cluster nodes."
-msgstr "まず初めに、クラスターノード間で自由に移動できる仮想 IP アドレス (VIP) を選択して割り当てる必要があります。"
-
-#: ./doc/high-availability-guide/api/section_api_vip.xml9(simpara)
-msgid ""
-"This configuration creates <literal>p_ip_api</literal>, a virtual IP address"
-" for use by the API node (192.168.42.103) :"
-msgstr "この設定は API ノードにより使用される仮想 IP アドレス (192.168.42.103) <literal>p_ip_api</literal> を作成します。"
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml6(title)
-msgid "Highly available Block Storage API"
-msgstr "高可用性 Block Storage API"
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml8(simpara)
-msgid ""
-"Making the Block Storage (cinder) API service highly available in active / "
-"passive mode involves"
-msgstr "Block Storage (cinder) API サービスのアクティブ / パッシブモードでの高可用化"
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml11(simpara)
-msgid "Configure Block Storage to listen on the VIP address,"
-msgstr "Block Storage がその仮想 IP アドレスをリッスンする設定"
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml16(simpara)
-msgid "managing Block Storage API daemon with the Pacemaker cluster manager,"
-msgstr "Pacemaker クラスターマネージャーを用いた Block Storage API デーモンの管理"
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml27(simpara)
-msgid ""
-"Here is the <link href=\"http://docs.openstack.org/trunk/install-"
-"guide/install/apt/content/ch_cinder.html\">documentation</link> for "
-"installing Block Storage service."
-msgstr "ここに Block Storage のインストールに関する<link href=\"http://docs.openstack.org/trunk/install-guide/install/apt/content/ch_cinder.html\">ドキュメント</link>があります。"
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml33(title)
-msgid "Add Block Storage API resource to Pacemaker"
-msgstr "Block Storage API リソースの Pacemaker への追加"
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml39(simpara)
-msgid ""
-"You can now add the Pacemaker configuration for Block Storage API resource. "
-"Connect to the Pacemaker cluster with <literal>crm configure</literal>, and "
-"add the following cluster resources:"
-msgstr "Block Storage API リソース用の Pacemaker 設定を追加できます。<literal>crm configure</literal> を用いて Pacemaker クラスターに接続し、以下のクラスターリソースを追加します。"
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml46(simpara)
-#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml36(simpara)
-#: ./doc/high-availability-guide/api/section_glance_api.xml44(simpara)
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml29(simpara)
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml29(simpara)
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml29(simpara)
-#: ./doc/high-availability-guide/controller/section_mysql.xml197(simpara)
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml185(simpara)
-msgid "This configuration creates"
-msgstr "この設定により、次のものが作成されます。"
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml49(simpara)
-msgid ""
-"<literal>p_cinder-api</literal>, a resource for manage Block Storage API "
-"service"
-msgstr "<literal>p_cinder-api</literal>, Block Storage API サービスを管理するためのリソース"
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml53(simpara)
-msgid ""
-"<literal>crm configure</literal> supports batch input, so you may copy and "
-"paste the above into your live pacemaker configuration, and then make "
-"changes as required. For example, you may enter <literal>edit p_ip_cinder-"
-"api</literal> from the <literal>crm configure</literal> menu and edit the "
-"resource to match your preferred virtual IP address."
-msgstr "<literal>crm configure</literal> はバッチ入力をサポートします。そのため、現在の pacemaker 設定の中に上をコピー・ペーストし、適宜変更を反映できます。たとえば、お好みの仮想 IP アドレスに一致させるために、<literal>crm configure</literal> メニューから <literal>edit p_ip_cinder-api</literal> と入力し、リソースを編集できます。"
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml58(simpara)
-msgid ""
-"Once completed, commit your configuration changes by entering "
-"<literal>commit</literal> from the <literal>crm configure</literal> menu. "
-"Pacemaker will then start the Block Storage API service, and its dependent "
-"resources, on one of your nodes."
-msgstr "完了すると、<literal>crm configure</literal> メニューから <literal>commit</literal> と入力し、設定の変更をコミットします。Pacemaker は Block Storage API サービスおよび依存するリソースを同じノードに起動します。"
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml64(title)
-msgid "Configure Block Storage API service"
-msgstr "Block Storage API サービスの設定"
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml66(simpara)
-msgid "Edit <literal>/etc/cinder/cinder.conf</literal>:"
-msgstr "<literal>/etc/cinder/cinder.conf</literal> を編集します。"
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml79(title)
-msgid "Configure OpenStack services to use highly available Block Storage API"
-msgstr "高可用性 Block Storage API を使用するための OpenStack サービスの設定"
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml81(simpara)
-msgid ""
-"Your OpenStack services must now point their Block Storage API configuration"
-" to the highly available, virtual cluster IP address — rather than a Block "
-"Storage API server’s physical IP address as you normally would."
-msgstr "OpenStack サービスは、通常どおり Block Storage API サーバーの物理 IP アドレスを指定する代わりに、Block Storage API の設定が高可用性と仮想クラスター IP アドレスを指し示す必要があります。"
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml84(simpara)
-msgid "You must create the Block Storage API endpoint with this IP."
-msgstr "この IP を用いて Block Storage API エンドポイントを作成する必要があります。"
-
-#: ./doc/high-availability-guide/api/section_cinder_api.xml86(simpara)
-msgid ""
-"If you are using both private and public IP, you should create two Virtual "
-"IPs and define your endpoint like this:"
-msgstr "プライベート IP とパブリック IP の両方を使用する場合、2 つの仮想 IP アドレスを作成し、次のようにエンドポイントを定義すべきです。"
-
-#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml6(title)
-msgid "Highly available Telemetry central agent"
-msgstr "高可用性 Telemetry 中央エージェント"
-
-#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml8(simpara)
-msgid ""
-"Telemetry (ceilometer) is the metering and monitoring service in OpenStack. "
-"The Central agent polls for resource utilization statistics for resources "
-"not tied to instances or compute nodes."
-msgstr "Telemetry (ceilometer) は OpenStack のメータリングとモニタリングのサービスです。中央エージェントは、インスタンスやコンピュートノードに結びつけられていないリソースに対して、リソースの利用状況の統計情報を収集します。"
-
-#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml12(simpara)
-msgid ""
-"Due to limitations of a polling model, a single instance of this agent can "
-"be polling a given list of meters. In this setup, we install this service on"
-" the API nodes also in the active / passive mode."
-msgstr "収集モデルの制限により、このエージェントの単一のインスタンスが指定された一覧の利用状況を収集できます。このセットアップの場合、このサービスもアクティブ / パッシブモードで API ノードにインストールします。"
-
-#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml16(simpara)
-msgid ""
-"Making the Telemetry central agent service highly available in active / "
-"passive mode involves managing its daemon with the Pacemaker cluster "
-"manager."
-msgstr "Telemetry 中央エージェントサービスをアクティブ / パッシブモードで高可用性にすることは、Pacemaker クラスターマネージャーでそのデーモンを管理することが関連します。"
-
-#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml19(simpara)
-msgid ""
-"You will find at <link "
-"href=\"http://docs.openstack.org/developer/ceilometer/install/manual.html"
-"#installing-the-central-agent\">this page</link> the process to install the "
-"Telemetry central agent."
-msgstr "Telemetry 中央エージェントをインストールする手順が<link href=\"http://docs.openstack.org/developer/ceilometer/install/manual.html#installing-the-central-agent\">このページ</link>にあります。"
-
-#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml24(title)
-msgid "Add the Telemetry central agent resource to Pacemaker"
-msgstr "Telemetry 中央エージェントリソースの Pacemaker への追加"
-
-#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml30(simpara)
-msgid ""
-"You may then proceed with adding the Pacemaker configuration for the "
-"Telemetry central agent resource. Connect to the Pacemaker cluster with "
-"<literal>crm configure</literal>, and add the following cluster resources:"
-msgstr "Telemetry 中央エージェントリソース用の Pacemaker 設定を追加して、次に進むことができます。<literal>crm configure</literal> を用いて Pacemaker クラスターに接続し、以下のクラスターリソースを追加します。"
-
-#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml39(simpara)
-msgid ""
-"<literal>p_ceilometer-agent-central</literal>, a resource for manage "
-"Ceilometer Central Agent service"
-msgstr "<literal>p_ceilometer-agent-central</literal>, Ceilometer 中央エージェントサービスを管理するためのリソース。"
-
-#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml43(simpara)
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml36(simpara)
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml37(simpara)
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml37(simpara)
-msgid ""
-"<literal>crm configure</literal> supports batch input, so you may copy and "
-"paste the above into your live pacemaker configuration, and then make "
-"changes as required."
-msgstr "<literal>crm configure</literal> はバッチ入力をサポートします。そのため、現在の pacemaker 設定の中に上をコピー・ペーストし、適宜変更を反映できます。"
-
-#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml46(simpara)
-msgid ""
-"Once completed, commit your configuration changes by entering "
-"<literal>commit</literal> from the <literal>crm configure</literal> menu. "
-"Pacemaker will then start the Ceilometer Central Agent service, and its "
-"dependent resources, on one of your nodes."
-msgstr "完了すると、<literal>crm configure</literal> メニューから <literal>commit</literal> と入力し、設定の変更をコミットします。Pacemaker は Ceilometer 中央エージェント サービスおよび依存するリソースを同じノードに起動します。"
-
-#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml52(title)
-msgid "Configure Telemetry central agent service"
-msgstr "Telemetry 中央エージェントサービスの設定"
-
-#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml54(simpara)
-msgid "Edit <literal>/etc/ceilometer/ceilometer.conf</literal> :"
-msgstr "<literal>/etc/ceilometer/ceilometer.conf</literal> を編集します。"
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml6(title)
-msgid "Highly available OpenStack Networking server"
-msgstr "高可用性 OpenStack Networking サーバー"
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml8(simpara)
-msgid ""
-"OpenStack Networking is the network connectivity service in OpenStack. "
-"Making the OpenStack Networking Server service highly available in active / "
-"passive mode involves"
-msgstr "OpenStack Networking は OpenStack におけるネットワーク接続性のサービスです。OpenStack Networking サーバーをアクティブ / パッシブモードで高可用性にすることは、次のことが関連します。"
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml12(simpara)
-msgid "Configure OpenStack Networking to listen on the VIP address,"
-msgstr "OpenStack Networking がその仮想 IP アドレスをリッスンする設定"
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml17(simpara)
-msgid ""
-"managing OpenStack Networking API Server daemon with the Pacemaker cluster "
-"manager,"
-msgstr "Pacemaker クラスターマネージャーを用いた OpenStack Networking API サーバーデーモンの管理"
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml28(simpara)
-msgid ""
-"Here is the <link href=\"http://docs.openstack.org/trunk/install-"
-"guide/install/apt/content/ch_installing-openstack-"
-"networking.html\">documentation</link> for installing OpenStack Networking "
-"service."
-msgstr "ここに OpenStack Networking Service をインストールするための<link href=\"http://docs.openstack.org/trunk/install-guide/install/apt/content/ch_installing-openstack-networking.html\">ドキュメント</link>があります。"
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml32(title)
-msgid "Add OpenStack Networking Server resource to Pacemaker"
-msgstr "OpenStack Networking Server リソースの Pacemaker への追加"
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml38(simpara)
-msgid ""
-"You can now add the Pacemaker configuration for OpenStack Networking Server "
-"resource. Connect to the Pacemaker cluster with <literal>crm "
-"configure</literal>, and add the following cluster resources:"
-msgstr "OpenStack Networking Server リソース用の Pacemaker 設定を追加できます。<literal>crm configure</literal> を用いて Pacemaker クラスターに接続し、以下のクラスターリソースを追加します。"
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml45(simpara)
-msgid ""
-"This configuration creates <literal>p_neutron-server</literal>, a resource "
-"for manage OpenStack Networking Server service"
-msgstr "この設定は OpenStack Networking サーバーサービスを管理するためのリソース <literal>p_neutron-server</literal> を作成します。"
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml46(simpara)
-msgid ""
-"<literal>crm configure</literal> supports batch input, so you may copy and "
-"paste the above into your live pacemaker configuration, and then make "
-"changes as required. For example, you may enter <literal>edit p_neutron-"
-"server</literal> from the <literal>crm configure</literal> menu and edit the"
-" resource to match your preferred virtual IP address."
-msgstr "<literal>crm configure</literal> はバッチ入力をサポートします。そのため、現在の pacemaker 設定の中に上をコピー・ペーストし、適宜変更を反映できます。たとえば、お好みの仮想 IP アドレスに一致させるために、<literal>crm configure</literal> メニューから <literal>edit p_neutron-server</literal> と入力し、リソースを編集できます。"
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml51(simpara)
-msgid ""
-"Once completed, commit your configuration changes by entering "
-"<literal>commit</literal> from the <literal>crm configure</literal> menu. "
-"Pacemaker will then start the OpenStack Networking API service, and its "
-"dependent resources, on one of your nodes."
-msgstr "完了すると、<literal>crm configure</literal> メニューから <literal>commit</literal> と入力し、設定の変更をコミットします。Pacemaker は OpenStack Networking API サービスおよび依存するリソースを同じノードに起動します。"
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml57(title)
-msgid "Configure OpenStack Networking server"
-msgstr "OpenStack Networking Server の設定"
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml59(simpara)
-msgid "Edit <literal>/etc/neutron/neutron.conf</literal> :"
-msgstr "<literal>/etc/neutron/neutron.conf</literal> を編集します。"
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml76(title)
-msgid ""
-"Configure OpenStack services to use highly available OpenStack Networking "
-"server"
-msgstr "高可用性 OpenStack Networking を使用するための OpenStack サービスの設定"
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml78(simpara)
-msgid ""
-"Your OpenStack services must now point their OpenStack Networking Server "
-"configuration to the highly available, virtual cluster IP address — rather "
-"than an OpenStack Networking server’s physical IP address as you normally "
-"would."
-msgstr "OpenStack サービスは、通常どおり OpenStack Networking サーバーの物理 IP アドレスを指定する代わりに、OpenStack Networking サーバーの設定が高可用性と仮想クラスター IP アドレスを指し示す必要があります。"
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml81(simpara)
-msgid ""
-"For example, you should configure OpenStack Compute for using highly "
-"available OpenStack Networking server in editing "
-"<literal>nova.conf</literal> file:"
-msgstr "たとえば、高可用性 Networking サーバーを使用するために、<literal>nova.conf</literal> ファイルを編集して OpenStack Compute を設定する必要があります :"
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml83(simpara)
-msgid ""
-"You need to create the OpenStack Networking server endpoint with this IP."
-msgstr "この IP を用いて OpenStack Networking Server エンドポイントを作成する必要があります。"
-
-#: ./doc/high-availability-guide/api/section_neutron_server.xml85(simpara)
-#: ./doc/high-availability-guide/api/section_glance_api.xml91(simpara)
-msgid ""
-"If you are using both private and public IP addresses, you should create two"
-" Virtual IP addresses and define your endpoint like this:"
-msgstr "プライベート IP とパブリック IP の両方を使用する場合、2 つの仮想 IP アドレスを作成し、次のようにエンドポイントを定義すべきです。"
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml6(title)
-msgid "Highly available OpenStack Image API"
-msgstr "高可用性 OpenStack Image API"
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml8(simpara)
-msgid ""
-"OpenStack Image Service offers a service for discovering, registering, and "
-"retrieving virtual machine images. To make the OpenStack Image API service "
-"highly available in active / passive mode, you must:"
-msgstr "OpenStack Image Service は仮想マシンイメージの検索、登録、取得に関するサービスを提供します。OpenStack Image API サービスをアクティブ / パッシブモードで高可用性にするために、以下を実行する必要があります。"
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml12(simpara)
-msgid "Configure OpenStack Image to listen on the VIP address."
-msgstr "OpenStack Image がその仮想 IP アドレスをリッスンするよう設定します。"
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml17(simpara)
-msgid "Manage OpenStack Image API daemon with the Pacemaker cluster manager."
-msgstr "Pacemaker クラスターマネージャーを用いた OpenStack Image API デーモンを管理します。"
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml28(simpara)
-msgid ""
-"Here is the <link href=\"http://docs.openstack.org/trunk/install-"
-"guide/install/apt/content/ch_installing-openstack-"
-"image.html\">documentation</link> for installing OpenStack Image API "
-"service."
-msgstr "ここに OpenStack Image API Service をインストールするための<link href=\"http://docs.openstack.org/trunk/install-guide/install/apt/content/ch_installing-openstack-image.html\">ドキュメント</link>があります。"
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml32(title)
-msgid "Add OpenStack Image API resource to Pacemaker"
-msgstr "OpenStack Image API リソースの Pacemaker への追加"
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml38(simpara)
-msgid ""
-"You can now add the Pacemaker configuration for OpenStack Image API "
-"resource. Connect to the Pacemaker cluster with <literal>crm "
-"configure</literal>, and add the following cluster resources:"
-msgstr "OpenStack Image API リソース用の Pacemaker 設定を追加できます。<literal>crm configure</literal> を用いて Pacemaker クラスターに接続し、以下のクラスターリソースを追加します。"
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml47(simpara)
-msgid ""
-"<literal>p_glance-api</literal>, a resource for manage OpenStack Image API "
-"service"
-msgstr "<literal>p_glance-api</literal>, OpenStack Image API サービスを管理するためのリソース"
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml51(simpara)
-msgid ""
-"<literal>crm configure</literal> supports batch input, so you may copy and "
-"paste the above into your live pacemaker configuration, and then make "
-"changes as required. For example, you may enter <literal>edit p_ip_glance-"
-"api</literal> from the <literal>crm configure</literal> menu and edit the "
-"resource to match your preferred virtual IP address."
-msgstr "<literal>crm configure</literal> はバッチ入力をサポートします。そのため、現在の pacemaker 設定の中に上をコピー・ペーストし、適宜変更を反映できます。たとえば、お好みの仮想 IP アドレスに一致させるために、<literal>crm configure</literal> メニューから <literal>edit p_ip_glance-api</literal> と入力し、リソースを編集できます。"
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml56(simpara)
-msgid ""
-"Once completed, commit your configuration changes by entering "
-"<literal>commit</literal> from the <literal>crm configure</literal> menu. "
-"Pacemaker will then start the OpenStack Image API service, and its dependent"
-" resources, on one of your nodes."
-msgstr "完了すると、<literal>crm configure</literal> メニューから <literal>commit</literal> と入力し、設定の変更をコミットします。Pacemaker は OpenStack Image API サービスおよび依存するリソースを同じノードに起動します。"
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml62(title)
-msgid "Configure OpenStack Image Service API"
-msgstr "OpenStack Image Service API の設定"
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml64(simpara)
-msgid "Edit <literal>/etc/glance/glance-api.conf</literal>:"
-msgstr "<literal>/etc/glance/glance-api.conf</literal> を編集します。"
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml80(title)
-msgid "Configure OpenStack services to use high available OpenStack Image API"
-msgstr "高可用性 OpenStack Image Service API を使用するための OpenStack サービスの設定"
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml82(simpara)
-msgid ""
-"Your OpenStack services must now point their OpenStack Image API "
-"configuration to the highly available, virtual cluster IP address — rather "
-"than an OpenStack Image API server’s physical IP address as you normally "
-"would."
-msgstr "OpenStack サービスは、通常どおり OpenStack Image API サーバーの物理 IP アドレスを指定する代わりに、OpenStack Image API の設定が高可用性と仮想クラスター IP アドレスを指し示す必要があります。"
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml85(simpara)
-msgid ""
-"For OpenStack Compute, for example, if your OpenStack Image API service IP "
-"address is 192.168.42.104 as in the configuration explained here, you would "
-"use the following line in your <literal>nova.conf</literal> file:"
-msgstr "OpenStack Compute の例として、OpenStack Image API の IP アドレスがここで説明された設定にあるように 192.168.42.104 ならば、<literal>nova.conf</literal> ファイルで以下の行を使用する必要があります。"
-
-#: ./doc/high-availability-guide/api/section_glance_api.xml89(simpara)
-msgid "You must also create the OpenStack Image API endpoint with this IP."
-msgstr "この IP を用いて OpenStack Image API エンドポイントを作成する必要があります。"
-
-#: ./doc/high-availability-guide/api/section_api_pacemaker.xml6(title)
-msgid "Configure Pacemaker group"
-msgstr "Pacemaker グループの設定"
-
-#: ./doc/high-availability-guide/api/section_api_pacemaker.xml8(simpara)
-msgid ""
-"Finally, we need to create a service <literal>group</literal> to ensure that"
-" virtual IP is linked to the API services resources:"
-msgstr "最終的に、仮想 IP が API サービスリソースとリンクされるよう、サービス <literal>グループ</literal> を作成する必要があります。"
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml6(title)
-msgid "Configure RabbitMQ"
-msgstr "RabbitMQ の設定"
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml8(simpara)
-msgid ""
-"Here we are building a cluster of RabbitMQ nodes to construct a RabbitMQ "
-"broker. Mirrored queues in RabbitMQ improve the availability of service "
-"since it will be resilient to failures. We have to consider that while "
-"exchanges and bindings will survive the loss of individual nodes, queues and"
-" their messages will not because a queue and its contents is located on one "
-"node. If we lose this node, we also lose the queue."
-msgstr "これから RabbitMQ ブローカーを構築するために RabbitMQ ノードのクラスターを構築します。障害の耐性ができるため、RabbitMQ のキューミラーによりサービスの可用性を高められます。メッセージ交換とバインドにより個々のノードの損失があると、キューとその内容が 1 つのノードに置かれているため、キューとそれらのメッセージが無くなることに注意してください。このノードが失われた場合、キューも失われます。"
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml13(simpara)
-msgid ""
-"We consider that we run (at least) two RabbitMQ servers. To build a broker, "
-"we need to ensure that all nodes have the same erlang cookie file. To do so,"
-" stop RabbitMQ everywhere and copy the cookie from rabbit1 server to other "
-"server(s):"
-msgstr "(少なくとも) 2 つの RabbitMQ サーバーを実行することを考えます。ブローカーを構築するために、すべてのノードが必ず同じ erlang クッキーファイルを持つ必要があります。そうするために、すべての RabbitMQ を停止し、クッキーを rabbit1 サーバーから他のサーバーにコピーします。"
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml18(simpara)
-msgid ""
-"Then, start RabbitMQ on nodes. If RabbitMQ fails to start, you can’t "
-"continue to the next step."
-msgstr "そして、ノードで RabbitMQ を起動します。RabbitMQ の起動に失敗した場合、次の手順に進めません。"
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml20(simpara)
-msgid "Now, we are building the HA cluster. From rabbit2, run these commands:"
-msgstr "これで、HA クラスターの構築ができました。rabbit2 からこれらのコマンドを実行します。"
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml24(simpara)
-msgid "To verify the cluster status :"
-msgstr "クラスターの状態を確認する方法:"
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml29(simpara)
-msgid ""
-"If the cluster is working, you can now proceed to creating users and "
-"passwords for queues."
-msgstr "クラスターが動作していれば、キュー用のユーザーとパスワードを作成する手順に進めます。"
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml31(emphasis)
-msgid "Note for RabbitMQ version 3"
-msgstr "RabbitMQ バージョン 3 の注意事項"
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml33(simpara)
-msgid ""
-"Queue mirroring is no longer controlled by the <emphasis>x-ha-"
-"policy</emphasis> argument when declaring a queue. OpenStack can continue to"
-" declare this argument, but it won’t cause queues to be mirrored. We need to"
-" make sure that all queues (except those with auto-generated names) are "
-"mirrored across all running nodes:"
-msgstr "キューの宣言時、キューミラーが <emphasis>x-ha-policy</emphasis> 引数により制御されなくなりました。OpenStack がこの引数を宣言し続けますが、キューはミラーされません。すべてのキュー (自動生成された名前を除いて) が実行中の全ノードにわたり確実にミラーされる必要があります。"
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml38(link)
-msgid "More information about High availability in RabbitMQ"
-msgstr "RabbitMQ の高可用性に関する詳細"
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml6(title)
-msgid "Configure OpenStack services to use RabbitMQ"
-msgstr "RabbitMQ を使用するための OpenStack サービスの設定"
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml8(simpara)
-msgid ""
-"We have to configure the OpenStack components to use at least two RabbitMQ "
-"nodes."
-msgstr "2 つ以上の RabbitMQ ノードを使用するよう、OpenStack のコンポーネントを設定する必要があります。"
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml9(simpara)
-msgid "Do this configuration on all services using RabbitMQ:"
-msgstr "RabbitMQ を使用するすべてのサービスでこの設定を行います。"
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml10(simpara)
-msgid "RabbitMQ HA cluster host:port pairs:"
-msgstr "RabbitMQ HA クラスターの host:port の組:"
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml12(simpara)
-msgid "How frequently to retry connecting with RabbitMQ:"
-msgstr "RabbitMQ と再接続する頻度:"
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml14(simpara)
-msgid "How long to back-off for between retries when connecting to RabbitMQ:"
-msgstr "RabbitMQ に接続するとき再試行するまでにバックオフする間隔:"
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml16(simpara)
-msgid ""
-"Maximum retries with trying to connect to RabbitMQ (infinite by default):"
-msgstr "RabbitMQ に接続を試行する最大回数 (デフォルトで無制限):"
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml18(simpara)
-msgid "Use durable queues in RabbitMQ:"
-msgstr "RabbitMQ での永続キューの使用:"
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml20(simpara)
-msgid "Use H/A queues in RabbitMQ (x-ha-policy: all):"
-msgstr "RabbitMQ での H/A キューの使用 (x-ha-policy: all):"
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml22(simpara)
-msgid ""
-"If you change the configuration from an old setup which did not use HA "
-"queues, you should interrupt the service:"
-msgstr "HA キューを使用していない古いセットアップから設定を変更した場合、サービスを中断しなければいけません。"
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml26(simpara)
-msgid ""
-"Services currently working with HA queues: OpenStack Compute, OpenStack "
-"Block Storage, OpenStack Networking, Telemetry."
-msgstr "次のサービスはいま HA キューで動作しています。OpenStack Compute、OpenStack Cinder、OpenStack Networking、Telemetry。"
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml8(simpara)
-msgid "This setup has been tested with RabbitMQ 2.7.1."
-msgstr "このセットアップは RabbitMQ 2.7.1 を用いてテストしました。"
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml11(title)
-msgid "On Ubuntu / Debian"
-msgstr "Ubuntu / Debian の場合"
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml13(simpara)
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml23(simpara)
-msgid "RabbitMQ is packaged on both distros:"
-msgstr "RabbitMQ がどちらもパッケージ化されています。"
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml16(link)
-msgid "Official manual for installing RabbitMQ on Ubuntu / Debian"
-msgstr "Ubuntu / Debian に RabbitMQ をインストールする方法の公式マニュアル"
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml21(title)
-msgid "On Fedora / RHEL"
-msgstr "Fedora / RHEL の場合"
-
-#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml26(link)
-msgid "Official manual for installing RabbitMQ on Fedora / RHEL"
-msgstr "Fedora / RHEL に RabbitMQ をインストールする方法の公式マニュアル"
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_memcached.xml6(title)
-msgid "Memcached"
-msgstr "Memcached"
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_memcached.xml8(simpara)
-msgid ""
-"Most of OpenStack services use an application to offer persistence and store"
-" ephemeral data (like tokens). Memcached is one of them and can scale-out "
-"easily without specific trick."
-msgstr "ほとんどの OpenStack サービスは、永続性を提供し、(トークンのような) 一時的なデータを保存するために、アプリケーションを使用します。memcached は、それらの一つで、特別な工夫をすることなく簡単にスケールアウト可能にできます。"
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_memcached.xml10(simpara)
-msgid ""
-"To install and configure it, read the <link "
-"href=\"http://code.google.com/p/memcached/wiki/NewStart\">official "
-"documentation</link>."
-msgstr "インストールおよび設定するために、<link href=\"http://code.google.com/p/memcached/wiki/NewStart\">公式ドキュメント</link>を参照します。"
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_memcached.xml11(simpara)
-msgid ""
-"Memory caching is managed by oslo-incubator so the way to use multiple "
-"memcached servers is the same for all projects."
-msgstr "メモリキャッシュは、複数の memcached サーバーを使用する方法がすべてのプロジェクトで同じにするために、Oslo インキュベーターにより管理されています。"
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_memcached.xml12(simpara)
-msgid "Example with two hosts:"
-msgstr "2 つのホストを用いた例:"
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_memcached.xml14(simpara)
-msgid ""
-"By default, controller1 handles the caching service but if the host goes "
-"down, controller2 does the job. For more information about memcached "
-"installation, see the OpenStack Cloud Administrator Guide."
-msgstr "デフォルトで、controller1 がキャッシュサービスを処理します。しかし、このホストが停止すると、controller2 がこのジョブを実行します。memcached のインストールに関する詳細は OpenStack クラウド管理者ガイドを参照してください。"
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml6(title)
-msgid "Run OpenStack API and schedulers"
-msgstr "OpenStack API &amp; スケジューラーの実行"
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml10(title)
-msgid "API services"
-msgstr "API サービス"
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml12(simpara)
-msgid ""
-"All OpenStack projects have an API service for controlling all the resources"
-" in the Cloud. In Active / Active mode, the most common setup is to scale-"
-"out these services on at least two nodes and use load-balancing and virtual "
-"IP (with HAproxy &amp; Keepalived in this setup)."
-msgstr "すべての OpenStack プロジェクトは、クラウドにあるすべてのリソースを制御するための API サービスを持ちます。アクティブ / アクティブモードの場合、最も一般的なセットアップ環境は、少なくとも 2 つのノードにこれらのサービスをスケールアウトし、(このセットアップで HAproxy と Keepalived を用いて) 負荷分散および仮想 IP を使用します。"
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml16(emphasis)
-msgid "Configure API OpenStack services"
-msgstr "OpenStack サービスの API の設定"
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml18(simpara)
-msgid ""
-"To configure our Cloud using Highly available and scalable API services, we "
-"need to ensure that:"
-msgstr "私たちのクラウド環境が高可用性かつスケーラブルな API サービスを使用するよう設定するために、以下の事項を確認する必要があります。"
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml21(simpara)
-msgid "You use Virtual IP when configuring OpenStack Identity endpoints."
-msgstr "OpenStack Identity エンドポイントを設定するときに仮想 IP を使用します。"
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml26(simpara)
-msgid "All OpenStack configuration files should refer to Virtual IP."
-msgstr "すべての OpenStack 設定ファイルは仮想 IP を参照すべきです。"
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml32(emphasis)
-msgid "In case of failure"
-msgstr "失敗の場合"
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml34(simpara)
-msgid ""
-"The monitor check is quite simple since it just establishes a TCP connection"
-" to the API port. Comparing to the Active / Passive mode using Corosync "
-"&amp; Resources Agents, we don’t check if the service is actually running). "
-"That’s why all OpenStack API should be monitored by another tool (i.e. "
-"Nagios) with the goal to detect failures in the Cloud Framework "
-"infrastructure."
-msgstr "API ポートへの TCP 接続を確立するだけのため、監視チェックは極めてシンプルです。Corosync とリソースエージェントを使用するアクティブ / パッシブモードと比べて、サービスが実際に動作しているかを確認しません。そのため、クラウドのフレームワーク環境における障害を検知するために、すべての OpenStack API は他のツール (例: Nagios) により監視すべきです。"
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml41(title)
-msgid "Schedulers"
-msgstr "スケジューラー"
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml43(simpara)
-msgid ""
-"OpenStack schedulers are used to determine how to dispatch compute, network "
-"and volume requests. The most common setup is to use RabbitMQ as messaging "
-"system already documented in this guide. Those services are connected to the"
-" messaging backend and can scale-out :"
-msgstr "OpenStack スケジューラーは、コンピュート、ネットワーク、ボリュームのリクエストをどのようにディスパッチするかを決めるために使用されます。最も一般的なセットアップ環境は、このガイドにドキュメント化されたメッセージングシステムとして RabbitMQ を使用することです。これらのサービスはメッセージングのバックエンドに接続され、スケールアウトできます。"
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml48(simpara)
-msgid "nova-scheduler"
-msgstr "nova-scheduler"
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml53(simpara)
-msgid "nova-conductor"
-msgstr "nova-conductor"
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml58(simpara)
-msgid "cinder-scheduler"
-msgstr "cinder-scheduler"
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml63(simpara)
-msgid "neutron-server"
-msgstr "neutron-server"
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml68(simpara)
-msgid "ceilometer-collector"
-msgstr "ceilometer-collector"
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml73(simpara)
-msgid "heat-engine"
-msgstr "heat-engine"
-
-#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml78(simpara)
-msgid ""
-"Please refer to the RabbitMQ section for configure these services with "
-"multiple messaging servers."
-msgstr "これらのサービスを複数のメッセージングサービスを用いて設定する方法は、RabbitMQ のセクションを参照してください。"
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml6(title)
-msgid "Highly available neutron L3 agent"
-msgstr "高可用性 Neutron L3 エージェント"
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml8(simpara)
-msgid ""
-"The neutron L3 agent provides L3/NAT forwarding to ensure external network "
-"access for VMs on tenant networks. High availability for the L3 agent is "
-"achieved by adopting Pacemaker."
-msgstr "Neutron L3 エージェントは、プロジェクトのネットワークにある仮想マシンが確実に外部ネットワークにアクセスできるように、L3/NAT 転送機能を提供します。"
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml12(simpara)
-msgid ""
-"Here is the <link href=\"http://docs.openstack.org/trunk/config-"
-"reference/content/section_adv_cfg_l3_agent.html\">documentation</link> for "
-"installing neutron L3 agent."
-msgstr "ここに Neutron L3 エージェントをインストールするための<link href=\"http://docs.openstack.org/trunk/config-reference/content/section_adv_cfg_l3_agent.html\">ドキュメント</link>があります。"
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml16(title)
-msgid "Add neutron L3 agent resource to Pacemaker"
-msgstr "Neutron L3 Agent リソースの Pacemaker への追加"
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml22(simpara)
-msgid ""
-"You may now proceed with adding the Pacemaker configuration for neutron L3 "
-"agent resource. Connect to the Pacemaker cluster with <literal>crm "
-"configure</literal>, and add the following cluster resources:"
-msgstr "Neutron L3 Agent リソース用の Pacemaker 設定を追加して、次に進むことができます。<literal>crm configure</literal> を用いて Pacemaker クラスターに接続し、以下のクラスターリソースを追加します。"
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml32(simpara)
-msgid ""
-"<literal>p_neutron-l3-agent</literal>, a resource for manage Neutron L3 "
-"Agent service"
-msgstr "<literal>p_neutron-l3-agent</literal>, Neutron L3 Agent サービスを管理するためのリソース。"
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml39(simpara)
-msgid ""
-"Once completed, commit your configuration changes by entering "
-"<literal>commit</literal> from the <literal>crm configure</literal> menu. "
-"Pacemaker will then start the neutron L3 agent service, and its dependent "
-"resources, on one of your nodes."
-msgstr "完了すると、<literal>crm configure</literal> メニューから <literal>commit</literal> と入力し、設定の変更をコミットします。Pacemaker は Neutron L3 Agent サービスおよび依存するリソースを同じノードに起動します。"
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml43(simpara)
-msgid ""
-"This method does not ensure a zero downtime since it has to recreate all the"
-" namespaces and virtual routers on the node."
-msgstr "この方法は、ノードですべての名前空間と仮想ルーターを再作成する必要があるため、無停止を保証しません。"
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml6(title)
-msgid "Highly available neutron metadata agent"
-msgstr "高可用性 Neutron Metadata Agent"
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml8(simpara)
-msgid ""
-"Neutron metadata agent allows Compute API metadata to be reachable by VMs on"
-" tenant networks. High availability for the metadata agent is achieved by "
-"adopting Pacemaker."
-msgstr "Neutron Metadata エージェントにより Nova API Metadata がプロジェクトのネットワークにある仮想マシンによりアクセスできるようになります。Metadata エージェントの高可用性は Pacemaker の適用により実現されます。"
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml12(simpara)
-msgid ""
-"Here is the <link href=\"http://docs.openstack.org/trunk/config-"
-"reference/content/networking-options-metadata.html\">documentation</link> "
-"for installing Neutron Metadata Agent."
-msgstr "ここに Neutron Metadata エージェントをインストールするための<link href=\"http://docs.openstack.org/trunk/config-reference/content/networking-options-metadata.html\">ドキュメント</link>があります。"
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml16(title)
-msgid "Add neutron metadata agent resource to Pacemaker"
-msgstr "Neutron Metadata Agent リソースの Pacemaker への追加"
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml22(simpara)
-msgid ""
-"You may now proceed with adding the Pacemaker configuration for neutron "
-"metadata agent resource. Connect to the Pacemaker cluster with <literal>crm "
-"configure</literal>, and add the following cluster resources:"
-msgstr "OpenStack Metadata Agent リソース用の Pacemaker 設定を追加して、次に進むことができます。<literal>crm configure</literal> を用いて Pacemaker クラスターに接続し、以下のクラスターリソースを追加します。"
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml32(simpara)
-msgid ""
-"<literal>p_neutron-metadata-agent</literal>, a resource for manage Neutron "
-"Metadata Agent service"
-msgstr "<literal>p_neutron-metadata-agent</literal>, Neutron Metadata Agent サービスを管理するためのリソース。"
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml40(simpara)
-msgid ""
-"Once completed, commit your configuration changes by entering "
-"<literal>commit</literal> from the <literal>crm configure</literal> menu. "
-"Pacemaker will then start the neutron metadata agent service, and its "
-"dependent resources, on one of your nodes."
-msgstr "完了すると、<literal>crm configure</literal> メニューから <literal>commit</literal> と入力し、設定の変更をコミットします。Pacemaker は Neutron Metadata Agent サービスおよび依存するリソースを同じノードに起動します。"
-
-#: ./doc/high-availability-guide/network/section_manage_network_resources.xml6(title)
-msgid "Manage network resources"
-msgstr "ネットワークリソースの管理"
-
-#: ./doc/high-availability-guide/network/section_manage_network_resources.xml8(simpara)
-msgid ""
-"You can now add the Pacemaker configuration for managing all network "
-"resources together with a group. Connect to the Pacemaker cluster with "
-"<literal>crm configure</literal>, and add the following cluster resources:"
-msgstr "すべてのネットワークリソースをグループと一緒に管理するための Pacemaker 設定を追加できます。<literal>crm configure</literal> を用いて Pacemaker クラスターに接続し、以下のクラスターリソースを追加します。"
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml6(title)
-msgid "Highly available neutron DHCP agent"
-msgstr "高可用性 Neutron DHCP Agent"
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml8(simpara)
-msgid ""
-"Neutron DHCP agent distributes IP addresses to the VMs with dnsmasq (by "
-"default). High availability for the DHCP agent is achieved by adopting "
-"Pacemaker."
-msgstr "Neutron DHCP エージェントは (デフォルトで) dnsmasq を用いて仮想マシンに IP アドレスを配布します。DHCP エージェントの高可用性は Pacemaker の適用により実現されます。"
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml12(simpara)
-msgid ""
-"Here is the <link href=\"http://docs.openstack.org/trunk/config-"
-"reference/content/section_adv_cfg_dhcp_agent.html\">documentation</link> for"
-" installing neutron DHCP agent."
-msgstr "ここに Neutron DHCP エージェントをインストールするための<link href=\"http://docs.openstack.org/trunk/config-reference/content/section_adv_cfg_dhcp_agent.html\">ドキュメント</link>があります。"
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml16(title)
-msgid "Add neutron DHCP agent resource to Pacemaker"
-msgstr "Neutron DHCP Agent リソースの Pacemaker への追加"
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml22(simpara)
-msgid ""
-"You may now proceed with adding the Pacemaker configuration for neutron DHCP"
-" agent resource. Connect to the Pacemaker cluster with <literal>crm "
-"configure</literal>, and add the following cluster resources:"
-msgstr "OpenStack DHCP Agent リソース用の Pacemaker 設定を追加して、次に進むことができます。<literal>crm configure</literal> を用いて Pacemaker クラスターに接続し、以下のクラスターリソースを追加します。"
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml32(simpara)
-msgid ""
-"<literal>p_neutron-dhcp-agent</literal>, a resource for manage Neutron DHCP "
-"Agent service"
-msgstr "<literal>p_neutron-dhcp-agent</literal>, Neutron DHCP Agent サービスを管理するためのリソース。"
-
-#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml40(simpara)
-msgid ""
-"Once completed, commit your configuration changes by entering "
-"<literal>commit</literal> from the <literal>crm configure</literal> menu. "
-"Pacemaker will then start the neutron DHCP agent service, and its dependent "
-"resources, on one of your nodes."
-msgstr "完了すると、<literal>crm configure</literal> メニューから <literal>commit</literal> と入力し、設定の変更をコミットします。Pacemaker は Neutron DHCP Agent サービスおよび依存するリソースを同じノードに起動します。"
-
-#: ./doc/high-availability-guide/ha_aa_network/section_run_neutron_l3_agent.xml6(title)
-msgid "Run neutron L3 agent"
-msgstr "Neutron L3 エージェントの実行"
-
-#: ./doc/high-availability-guide/ha_aa_network/section_run_neutron_l3_agent.xml8(simpara)
-msgid ""
-"The neutron L3 agent is scalable thanks to the scheduler that allows "
-"distribution of virtual routers across multiple nodes. But there is no "
-"native feature to make these routers highly available. At this time, the "
-"Active / Passive solution exists to run the Neutron L3 agent in failover "
-"mode with Pacemaker. See the Active / Passive section of this guide."
-msgstr "仮想ルーターを複数のノードに渡り配布できるスケジューラーのおかげで、Neutron L3 エージェントがスケール可能になりました。しかし、これらのルーターを高可用性にする独自の機能はありません。今のところ、Pacemaker のフェイルオーバーモードで Neutron L3 エージェントを実行させる、アクティブ / パッシブのソリューションがあります。このガイドのアクティブ / パッシブのセクションを参照ください。"
-
-#: ./doc/high-availability-guide/ha_aa_network/section_run_neutron_metadata_agent.xml6(title)
-msgid "Run neutron metadata agent"
-msgstr "Neutron メタデータエージェントの実行"
-
-#: ./doc/high-availability-guide/ha_aa_network/section_run_neutron_metadata_agent.xml8(simpara)
-msgid ""
-"There is no native feature to make this service highly available. At this "
-"time, the Active / Passive solution exists to run the neutron metadata agent"
-" in failover mode with Pacemaker. See the Active / Passive section of this "
-"guide."
-msgstr "このサービスを高可用性にする独自の機能はありません。今のところ、Pacemaker のフェイルオーバーモードで Neutron メタデータエージェントを実行させる、アクティブ / パッシブのソリューションがあります。このガイドのアクティブ / パッシブのセクションを参照ください。"
-
-#: ./doc/high-availability-guide/ha_aa_network/section_run_neutron_dhcp_agent.xml6(title)
-msgid "Run neutron DHCP agent"
-msgstr "Neutron DHCP エージェントの実行"
-
-#: ./doc/high-availability-guide/ha_aa_network/section_run_neutron_dhcp_agent.xml8(simpara)
-msgid ""
-"OpenStack Networking service has a scheduler that lets you run multiple "
-"agents across nodes. Also, the DHCP agent can be natively highly available. "
-"For details, see <link href=\"http://docs.openstack.org/trunk/config-"
-"reference/content/app_demo_multi_dhcp_agents.html\">OpenStack Configuration "
-"Reference</link>."
-msgstr "OpenStack Networking Service はノードをまたがり複数のエージェントを実行できるスケジューラーがあります。また、DHCP エージェントはネイティブで高可用性にできます。詳細は <link href=\"http://docs.openstack.org/trunk/config-reference/content/app_demo_multi_dhcp_agents.html\">OpenStack 設定リファレンス</link>を参照してください。"
+#: ./doc/high-availability-guide/part_active_active.xml6(title)
+msgid "HA using active/active"
+msgstr "アクティブ/アクティブを使用した HA"
 
 #: ./doc/high-availability-guide/ha_aa_db/section_ha_aa_db_galera_monitoring.xml6(title)
 msgid "Galera monitoring scripts"
@@ -1761,20 +497,6 @@ msgstr "Galera 監視スクリプト"
 msgid "(Coming soon)"
 msgstr "(近日公開)"
 
-#: ./doc/high-availability-guide/ha_aa_db/section_other_ways_to_provide_a_highly_available_database.xml6(title)
-msgid "Other ways to provide a highly available database"
-msgstr "高可用性データベースを提供する別の方法"
-
-#: ./doc/high-availability-guide/ha_aa_db/section_other_ways_to_provide_a_highly_available_database.xml8(simpara)
-msgid ""
-"MySQL with Galera is by no means the only way to achieve database HA. "
-"MariaDB (<link href=\"https://mariadb.org/\">https://mariadb.org/</link>) "
-"and Percona (<link "
-"href=\"http://www.percona.com/\">http://www.percona.com/</link>) also work "
-"with Galera. You also have the option to use Postgres, which has its own "
-"replication, or another database HA option."
-msgstr "MySQL と Galera の併用がデータベースを HA 化する唯一の方法ではありません。MariaDB (<link href=\"https://mariadb.org/\">https://mariadb.org/</link>) や Percona (<link href=\"http://www.percona.com/\">http://www.percona.com/</link>) も Galera と併用できます。独自のレプリケーション機能を持つ Postgres や他のデータベースの HA オプションを使用するという選択肢もあります。"
-
 #: ./doc/high-availability-guide/ha_aa_db/section_ha_aa_db_mysql_galera.xml6(title)
 msgid "MySQL with Galera"
 msgstr "Galera を用いた MySQL"
@@ -1909,6 +631,836 @@ msgstr "MySQL クライアントを開き、さまざまなパラメーターの
 msgid "You should see a status that looks something like this:"
 msgstr "このように見える状態を確認すべきです。"
 
+#: ./doc/high-availability-guide/ha_aa_db/section_other_ways_to_provide_a_highly_available_database.xml6(title)
+msgid "Other ways to provide a highly available database"
+msgstr "高可用性データベースを提供する別の方法"
+
+#: ./doc/high-availability-guide/ha_aa_db/section_other_ways_to_provide_a_highly_available_database.xml8(simpara)
+msgid ""
+"MySQL with Galera is by no means the only way to achieve database HA. "
+"MariaDB (<link href=\"https://mariadb.org/\">https://mariadb.org/</link>) "
+"and Percona (<link "
+"href=\"http://www.percona.com/\">http://www.percona.com/</link>) also work "
+"with Galera. You also have the option to use Postgres, which has its own "
+"replication, or another database HA option."
+msgstr "MySQL と Galera の併用がデータベースを HA 化する唯一の方法ではありません。MariaDB (<link href=\"https://mariadb.org/\">https://mariadb.org/</link>) や Percona (<link href=\"http://www.percona.com/\">http://www.percona.com/</link>) も Galera と併用できます。独自のレプリケーション機能を持つ Postgres や他のデータベースの HA オプションを使用するという選択肢もあります。"
+
+#: ./doc/high-availability-guide/ha_aa_network/section_run_neutron_l3_agent.xml6(title)
+msgid "Run neutron L3 agent"
+msgstr "Neutron L3 エージェントの実行"
+
+#: ./doc/high-availability-guide/ha_aa_network/section_run_neutron_l3_agent.xml8(simpara)
+msgid ""
+"The neutron L3 agent is scalable thanks to the scheduler that allows "
+"distribution of virtual routers across multiple nodes. But there is no "
+"native feature to make these routers highly available. At this time, the "
+"Active / Passive solution exists to run the Neutron L3 agent in failover "
+"mode with Pacemaker. See the Active / Passive section of this guide."
+msgstr "仮想ルーターを複数のノードに渡り配布できるスケジューラーのおかげで、Neutron L3 エージェントがスケール可能になりました。しかし、これらのルーターを高可用性にする独自の機能はありません。今のところ、Pacemaker のフェイルオーバーモードで Neutron L3 エージェントを実行させる、アクティブ / パッシブのソリューションがあります。このガイドのアクティブ / パッシブのセクションを参照ください。"
+
+#: ./doc/high-availability-guide/ha_aa_network/section_run_neutron_metadata_agent.xml6(title)
+msgid "Run neutron metadata agent"
+msgstr "Neutron メタデータエージェントの実行"
+
+#: ./doc/high-availability-guide/ha_aa_network/section_run_neutron_metadata_agent.xml8(simpara)
+msgid ""
+"There is no native feature to make this service highly available. At this "
+"time, the Active / Passive solution exists to run the neutron metadata agent"
+" in failover mode with Pacemaker. See the Active / Passive section of this "
+"guide."
+msgstr "このサービスを高可用性にする独自の機能はありません。今のところ、Pacemaker のフェイルオーバーモードで Neutron メタデータエージェントを実行させる、アクティブ / パッシブのソリューションがあります。このガイドのアクティブ / パッシブのセクションを参照ください。"
+
+#: ./doc/high-availability-guide/ha_aa_network/section_run_neutron_dhcp_agent.xml6(title)
+msgid "Run neutron DHCP agent"
+msgstr "Neutron DHCP エージェントの実行"
+
+#: ./doc/high-availability-guide/ha_aa_network/section_run_neutron_dhcp_agent.xml8(simpara)
+msgid ""
+"OpenStack Networking service has a scheduler that lets you run multiple "
+"agents across nodes. Also, the DHCP agent can be natively highly available. "
+"For details, see <link href=\"http://docs.openstack.org/trunk/config-"
+"reference/content/app_demo_multi_dhcp_agents.html\">OpenStack Configuration "
+"Reference</link>."
+msgstr "OpenStack Networking Service はノードをまたがり複数のエージェントを実行できるスケジューラーがあります。また、DHCP エージェントはネイティブで高可用性にできます。詳細は <link href=\"http://docs.openstack.org/trunk/config-reference/content/app_demo_multi_dhcp_agents.html\">OpenStack 設定リファレンス</link>を参照してください。"
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml6(title)
+msgid "Highly available Block Storage API"
+msgstr "高可用性 Block Storage API"
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml8(simpara)
+msgid ""
+"Making the Block Storage (cinder) API service highly available in active / "
+"passive mode involves"
+msgstr "Block Storage (cinder) API サービスのアクティブ / パッシブモードでの高可用化"
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml11(simpara)
+msgid "Configure Block Storage to listen on the VIP address,"
+msgstr "Block Storage がその仮想 IP アドレスをリッスンする設定"
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml16(simpara)
+msgid "managing Block Storage API daemon with the Pacemaker cluster manager,"
+msgstr "Pacemaker クラスターマネージャーを用いた Block Storage API デーモンの管理"
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml21(simpara)
+#: ./doc/high-availability-guide/api/section_glance_api.xml22(simpara)
+#: ./doc/high-availability-guide/api/section_neutron_server.xml22(simpara)
+#: ./doc/high-availability-guide/api/section_keystone.xml22(simpara)
+msgid "Configure OpenStack services to use this IP address."
+msgstr "OpenStack のサービスがこの IP アドレスを使用するよう設定します。"
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml27(simpara)
+msgid ""
+"Here is the <link href=\"http://docs.openstack.org/trunk/install-"
+"guide/install/apt/content/ch_cinder.html\">documentation</link> for "
+"installing Block Storage service."
+msgstr "ここに Block Storage のインストールに関する<link href=\"http://docs.openstack.org/trunk/install-guide/install/apt/content/ch_cinder.html\">ドキュメント</link>があります。"
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml33(title)
+msgid "Add Block Storage API resource to Pacemaker"
+msgstr "Block Storage API リソースの Pacemaker への追加"
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml35(simpara)
+#: ./doc/high-availability-guide/api/section_glance_api.xml34(simpara)
+#: ./doc/high-availability-guide/api/section_neutron_server.xml34(simpara)
+#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml26(simpara)
+#: ./doc/high-availability-guide/api/section_keystone.xml34(simpara)
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml18(simpara)
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml18(simpara)
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml18(simpara)
+msgid "First of all, you need to download the resource agent to your system:"
+msgstr "まず初めに、リソースエージェントをシステムにダウンロードする必要があります。"
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml39(simpara)
+msgid ""
+"You can now add the Pacemaker configuration for Block Storage API resource. "
+"Connect to the Pacemaker cluster with <literal>crm configure</literal>, and "
+"add the following cluster resources:"
+msgstr "Block Storage API リソース用の Pacemaker 設定を追加できます。<literal>crm configure</literal> を用いて Pacemaker クラスターに接続し、以下のクラスターリソースを追加します。"
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml46(simpara)
+#: ./doc/high-availability-guide/api/section_glance_api.xml44(simpara)
+#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml36(simpara)
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml185(simpara)
+#: ./doc/high-availability-guide/controller/section_mysql.xml197(simpara)
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml29(simpara)
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml29(simpara)
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml29(simpara)
+msgid "This configuration creates"
+msgstr "この設定により、次のものが作成されます。"
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml49(simpara)
+msgid ""
+"<literal>p_cinder-api</literal>, a resource for manage Block Storage API "
+"service"
+msgstr "<literal>p_cinder-api</literal>, Block Storage API サービスを管理するためのリソース"
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml53(simpara)
+msgid ""
+"<literal>crm configure</literal> supports batch input, so you may copy and "
+"paste the above into your live pacemaker configuration, and then make "
+"changes as required. For example, you may enter <literal>edit p_ip_cinder-"
+"api</literal> from the <literal>crm configure</literal> menu and edit the "
+"resource to match your preferred virtual IP address."
+msgstr "<literal>crm configure</literal> はバッチ入力をサポートします。そのため、現在の pacemaker 設定の中に上をコピー・ペーストし、適宜変更を反映できます。たとえば、お好みの仮想 IP アドレスに一致させるために、<literal>crm configure</literal> メニューから <literal>edit p_ip_cinder-api</literal> と入力し、リソースを編集できます。"
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml58(simpara)
+msgid ""
+"Once completed, commit your configuration changes by entering "
+"<literal>commit</literal> from the <literal>crm configure</literal> menu. "
+"Pacemaker will then start the Block Storage API service, and its dependent "
+"resources, on one of your nodes."
+msgstr "完了すると、<literal>crm configure</literal> メニューから <literal>commit</literal> と入力し、設定の変更をコミットします。Pacemaker は Block Storage API サービスおよび依存するリソースを同じノードに起動します。"
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml64(title)
+msgid "Configure Block Storage API service"
+msgstr "Block Storage API サービスの設定"
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml66(simpara)
+msgid "Edit <literal>/etc/cinder/cinder.conf</literal>:"
+msgstr "<literal>/etc/cinder/cinder.conf</literal> を編集します。"
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml79(title)
+msgid "Configure OpenStack services to use highly available Block Storage API"
+msgstr "高可用性 Block Storage API を使用するための OpenStack サービスの設定"
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml81(simpara)
+msgid ""
+"Your OpenStack services must now point their Block Storage API configuration"
+" to the highly available, virtual cluster IP address — rather than a Block "
+"Storage API server’s physical IP address as you normally would."
+msgstr "OpenStack サービスは、通常どおり Block Storage API サーバーの物理 IP アドレスを指定する代わりに、Block Storage API の設定が高可用性と仮想クラスター IP アドレスを指し示す必要があります。"
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml84(simpara)
+msgid "You must create the Block Storage API endpoint with this IP."
+msgstr "この IP を用いて Block Storage API エンドポイントを作成する必要があります。"
+
+#: ./doc/high-availability-guide/api/section_cinder_api.xml86(simpara)
+msgid ""
+"If you are using both private and public IP, you should create two Virtual "
+"IPs and define your endpoint like this:"
+msgstr "プライベート IP とパブリック IP の両方を使用する場合、2 つの仮想 IP アドレスを作成し、次のようにエンドポイントを定義すべきです。"
+
+#: ./doc/high-availability-guide/api/section_api_pacemaker.xml6(title)
+msgid "Configure Pacemaker group"
+msgstr "Pacemaker グループの設定"
+
+#: ./doc/high-availability-guide/api/section_api_pacemaker.xml8(simpara)
+msgid ""
+"Finally, we need to create a service <literal>group</literal> to ensure that"
+" virtual IP is linked to the API services resources:"
+msgstr "最終的に、仮想 IP が API サービスリソースとリンクされるよう、サービス <literal>グループ</literal> を作成する必要があります。"
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml6(title)
+msgid "Highly available OpenStack Image API"
+msgstr "高可用性 OpenStack Image API"
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml8(simpara)
+msgid ""
+"OpenStack Image Service offers a service for discovering, registering, and "
+"retrieving virtual machine images. To make the OpenStack Image API service "
+"highly available in active / passive mode, you must:"
+msgstr "OpenStack Image Service は仮想マシンイメージの検索、登録、取得に関するサービスを提供します。OpenStack Image API サービスをアクティブ / パッシブモードで高可用性にするために、以下を実行する必要があります。"
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml12(simpara)
+msgid "Configure OpenStack Image to listen on the VIP address."
+msgstr "OpenStack Image がその仮想 IP アドレスをリッスンするよう設定します。"
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml17(simpara)
+msgid "Manage OpenStack Image API daemon with the Pacemaker cluster manager."
+msgstr "Pacemaker クラスターマネージャーを用いた OpenStack Image API デーモンを管理します。"
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml28(simpara)
+msgid ""
+"Here is the <link href=\"http://docs.openstack.org/trunk/install-"
+"guide/install/apt/content/ch_installing-openstack-"
+"image.html\">documentation</link> for installing OpenStack Image API "
+"service."
+msgstr "ここに OpenStack Image API Service をインストールするための<link href=\"http://docs.openstack.org/trunk/install-guide/install/apt/content/ch_installing-openstack-image.html\">ドキュメント</link>があります。"
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml32(title)
+msgid "Add OpenStack Image API resource to Pacemaker"
+msgstr "OpenStack Image API リソースの Pacemaker への追加"
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml38(simpara)
+msgid ""
+"You can now add the Pacemaker configuration for OpenStack Image API "
+"resource. Connect to the Pacemaker cluster with <literal>crm "
+"configure</literal>, and add the following cluster resources:"
+msgstr "OpenStack Image API リソース用の Pacemaker 設定を追加できます。<literal>crm configure</literal> を用いて Pacemaker クラスターに接続し、以下のクラスターリソースを追加します。"
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml47(simpara)
+msgid ""
+"<literal>p_glance-api</literal>, a resource for manage OpenStack Image API "
+"service"
+msgstr "<literal>p_glance-api</literal>, OpenStack Image API サービスを管理するためのリソース"
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml51(simpara)
+msgid ""
+"<literal>crm configure</literal> supports batch input, so you may copy and "
+"paste the above into your live pacemaker configuration, and then make "
+"changes as required. For example, you may enter <literal>edit p_ip_glance-"
+"api</literal> from the <literal>crm configure</literal> menu and edit the "
+"resource to match your preferred virtual IP address."
+msgstr "<literal>crm configure</literal> はバッチ入力をサポートします。そのため、現在の pacemaker 設定の中に上をコピー・ペーストし、適宜変更を反映できます。たとえば、お好みの仮想 IP アドレスに一致させるために、<literal>crm configure</literal> メニューから <literal>edit p_ip_glance-api</literal> と入力し、リソースを編集できます。"
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml56(simpara)
+msgid ""
+"Once completed, commit your configuration changes by entering "
+"<literal>commit</literal> from the <literal>crm configure</literal> menu. "
+"Pacemaker will then start the OpenStack Image API service, and its dependent"
+" resources, on one of your nodes."
+msgstr "完了すると、<literal>crm configure</literal> メニューから <literal>commit</literal> と入力し、設定の変更をコミットします。Pacemaker は OpenStack Image API サービスおよび依存するリソースを同じノードに起動します。"
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml62(title)
+msgid "Configure OpenStack Image Service API"
+msgstr "OpenStack Image Service API の設定"
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml64(simpara)
+msgid "Edit <literal>/etc/glance/glance-api.conf</literal>:"
+msgstr "<literal>/etc/glance/glance-api.conf</literal> を編集します。"
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml80(title)
+msgid "Configure OpenStack services to use high available OpenStack Image API"
+msgstr "高可用性 OpenStack Image Service API を使用するための OpenStack サービスの設定"
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml82(simpara)
+msgid ""
+"Your OpenStack services must now point their OpenStack Image API "
+"configuration to the highly available, virtual cluster IP address — rather "
+"than an OpenStack Image API server’s physical IP address as you normally "
+"would."
+msgstr "OpenStack サービスは、通常どおり OpenStack Image API サーバーの物理 IP アドレスを指定する代わりに、OpenStack Image API の設定が高可用性と仮想クラスター IP アドレスを指し示す必要があります。"
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml85(simpara)
+msgid ""
+"For OpenStack Compute, for example, if your OpenStack Image API service IP "
+"address is 192.168.42.104 as in the configuration explained here, you would "
+"use the following line in your <literal>nova.conf</literal> file:"
+msgstr "OpenStack Compute の例として、OpenStack Image API の IP アドレスがここで説明された設定にあるように 192.168.42.104 ならば、<literal>nova.conf</literal> ファイルで以下の行を使用する必要があります。"
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml89(simpara)
+msgid "You must also create the OpenStack Image API endpoint with this IP."
+msgstr "この IP を用いて OpenStack Image API エンドポイントを作成する必要があります。"
+
+#: ./doc/high-availability-guide/api/section_glance_api.xml91(simpara)
+#: ./doc/high-availability-guide/api/section_neutron_server.xml85(simpara)
+msgid ""
+"If you are using both private and public IP addresses, you should create two"
+" Virtual IP addresses and define your endpoint like this:"
+msgstr "プライベート IP とパブリック IP の両方を使用する場合、2 つの仮想 IP アドレスを作成し、次のようにエンドポイントを定義すべきです。"
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml6(title)
+msgid "Highly available OpenStack Networking server"
+msgstr "高可用性 OpenStack Networking サーバー"
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml8(simpara)
+msgid ""
+"OpenStack Networking is the network connectivity service in OpenStack. "
+"Making the OpenStack Networking Server service highly available in active / "
+"passive mode involves"
+msgstr "OpenStack Networking は OpenStack におけるネットワーク接続性のサービスです。OpenStack Networking サーバーをアクティブ / パッシブモードで高可用性にすることは、次のことが関連します。"
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml12(simpara)
+msgid "Configure OpenStack Networking to listen on the VIP address,"
+msgstr "OpenStack Networking がその仮想 IP アドレスをリッスンする設定"
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml17(simpara)
+msgid ""
+"managing OpenStack Networking API Server daemon with the Pacemaker cluster "
+"manager,"
+msgstr "Pacemaker クラスターマネージャーを用いた OpenStack Networking API サーバーデーモンの管理"
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml28(simpara)
+msgid ""
+"Here is the <link href=\"http://docs.openstack.org/trunk/install-"
+"guide/install/apt/content/ch_installing-openstack-"
+"networking.html\">documentation</link> for installing OpenStack Networking "
+"service."
+msgstr "ここに OpenStack Networking Service をインストールするための<link href=\"http://docs.openstack.org/trunk/install-guide/install/apt/content/ch_installing-openstack-networking.html\">ドキュメント</link>があります。"
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml32(title)
+msgid "Add OpenStack Networking Server resource to Pacemaker"
+msgstr "OpenStack Networking Server リソースの Pacemaker への追加"
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml38(simpara)
+msgid ""
+"You can now add the Pacemaker configuration for OpenStack Networking Server "
+"resource. Connect to the Pacemaker cluster with <literal>crm "
+"configure</literal>, and add the following cluster resources:"
+msgstr "OpenStack Networking Server リソース用の Pacemaker 設定を追加できます。<literal>crm configure</literal> を用いて Pacemaker クラスターに接続し、以下のクラスターリソースを追加します。"
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml45(simpara)
+msgid ""
+"This configuration creates <literal>p_neutron-server</literal>, a resource "
+"for manage OpenStack Networking Server service"
+msgstr "この設定は OpenStack Networking サーバーサービスを管理するためのリソース <literal>p_neutron-server</literal> を作成します。"
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml46(simpara)
+msgid ""
+"<literal>crm configure</literal> supports batch input, so you may copy and "
+"paste the above into your live pacemaker configuration, and then make "
+"changes as required. For example, you may enter <literal>edit p_neutron-"
+"server</literal> from the <literal>crm configure</literal> menu and edit the"
+" resource to match your preferred virtual IP address."
+msgstr "<literal>crm configure</literal> はバッチ入力をサポートします。そのため、現在の pacemaker 設定の中に上をコピー・ペーストし、適宜変更を反映できます。たとえば、お好みの仮想 IP アドレスに一致させるために、<literal>crm configure</literal> メニューから <literal>edit p_neutron-server</literal> と入力し、リソースを編集できます。"
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml51(simpara)
+msgid ""
+"Once completed, commit your configuration changes by entering "
+"<literal>commit</literal> from the <literal>crm configure</literal> menu. "
+"Pacemaker will then start the OpenStack Networking API service, and its "
+"dependent resources, on one of your nodes."
+msgstr "完了すると、<literal>crm configure</literal> メニューから <literal>commit</literal> と入力し、設定の変更をコミットします。Pacemaker は OpenStack Networking API サービスおよび依存するリソースを同じノードに起動します。"
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml57(title)
+msgid "Configure OpenStack Networking server"
+msgstr "OpenStack Networking Server の設定"
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml59(simpara)
+msgid "Edit <literal>/etc/neutron/neutron.conf</literal> :"
+msgstr "<literal>/etc/neutron/neutron.conf</literal> を編集します。"
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml76(title)
+msgid ""
+"Configure OpenStack services to use highly available OpenStack Networking "
+"server"
+msgstr "高可用性 OpenStack Networking を使用するための OpenStack サービスの設定"
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml78(simpara)
+msgid ""
+"Your OpenStack services must now point their OpenStack Networking Server "
+"configuration to the highly available, virtual cluster IP address — rather "
+"than an OpenStack Networking server’s physical IP address as you normally "
+"would."
+msgstr "OpenStack サービスは、通常どおり OpenStack Networking サーバーの物理 IP アドレスを指定する代わりに、OpenStack Networking サーバーの設定が高可用性と仮想クラスター IP アドレスを指し示す必要があります。"
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml81(simpara)
+msgid ""
+"For example, you should configure OpenStack Compute for using highly "
+"available OpenStack Networking server in editing "
+"<literal>nova.conf</literal> file:"
+msgstr "たとえば、高可用性 Networking サーバーを使用するために、<literal>nova.conf</literal> ファイルを編集して OpenStack Compute を設定する必要があります :"
+
+#: ./doc/high-availability-guide/api/section_neutron_server.xml83(simpara)
+msgid ""
+"You need to create the OpenStack Networking server endpoint with this IP."
+msgstr "この IP を用いて OpenStack Networking Server エンドポイントを作成する必要があります。"
+
+#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml6(title)
+msgid "Highly available Telemetry central agent"
+msgstr "高可用性 Telemetry 中央エージェント"
+
+#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml8(simpara)
+msgid ""
+"Telemetry (ceilometer) is the metering and monitoring service in OpenStack. "
+"The Central agent polls for resource utilization statistics for resources "
+"not tied to instances or compute nodes."
+msgstr "Telemetry (ceilometer) は OpenStack のメータリングとモニタリングのサービスです。中央エージェントは、インスタンスやコンピュートノードに結びつけられていないリソースに対して、リソースの利用状況の統計情報を収集します。"
+
+#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml12(simpara)
+msgid ""
+"Due to limitations of a polling model, a single instance of this agent can "
+"be polling a given list of meters. In this setup, we install this service on"
+" the API nodes also in the active / passive mode."
+msgstr "収集モデルの制限により、このエージェントの単一のインスタンスが指定された一覧の利用状況を収集できます。このセットアップの場合、このサービスもアクティブ / パッシブモードで API ノードにインストールします。"
+
+#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml16(simpara)
+msgid ""
+"Making the Telemetry central agent service highly available in active / "
+"passive mode involves managing its daemon with the Pacemaker cluster "
+"manager."
+msgstr "Telemetry 中央エージェントサービスをアクティブ / パッシブモードで高可用性にすることは、Pacemaker クラスターマネージャーでそのデーモンを管理することが関連します。"
+
+#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml19(simpara)
+msgid ""
+"You will find at <link "
+"href=\"http://docs.openstack.org/developer/ceilometer/install/manual.html"
+"#installing-the-central-agent\">this page</link> the process to install the "
+"Telemetry central agent."
+msgstr "Telemetry 中央エージェントをインストールする手順が<link href=\"http://docs.openstack.org/developer/ceilometer/install/manual.html#installing-the-central-agent\">このページ</link>にあります。"
+
+#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml24(title)
+msgid "Add the Telemetry central agent resource to Pacemaker"
+msgstr "Telemetry 中央エージェントリソースの Pacemaker への追加"
+
+#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml30(simpara)
+msgid ""
+"You may then proceed with adding the Pacemaker configuration for the "
+"Telemetry central agent resource. Connect to the Pacemaker cluster with "
+"<literal>crm configure</literal>, and add the following cluster resources:"
+msgstr "Telemetry 中央エージェントリソース用の Pacemaker 設定を追加して、次に進むことができます。<literal>crm configure</literal> を用いて Pacemaker クラスターに接続し、以下のクラスターリソースを追加します。"
+
+#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml39(simpara)
+msgid ""
+"<literal>p_ceilometer-agent-central</literal>, a resource for manage "
+"Ceilometer Central Agent service"
+msgstr "<literal>p_ceilometer-agent-central</literal>, Ceilometer 中央エージェントサービスを管理するためのリソース。"
+
+#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml43(simpara)
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml37(simpara)
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml36(simpara)
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml37(simpara)
+msgid ""
+"<literal>crm configure</literal> supports batch input, so you may copy and "
+"paste the above into your live pacemaker configuration, and then make "
+"changes as required."
+msgstr "<literal>crm configure</literal> はバッチ入力をサポートします。そのため、現在の pacemaker 設定の中に上をコピー・ペーストし、適宜変更を反映できます。"
+
+#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml46(simpara)
+msgid ""
+"Once completed, commit your configuration changes by entering "
+"<literal>commit</literal> from the <literal>crm configure</literal> menu. "
+"Pacemaker will then start the Ceilometer Central Agent service, and its "
+"dependent resources, on one of your nodes."
+msgstr "完了すると、<literal>crm configure</literal> メニューから <literal>commit</literal> と入力し、設定の変更をコミットします。Pacemaker は Ceilometer 中央エージェント サービスおよび依存するリソースを同じノードに起動します。"
+
+#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml52(title)
+msgid "Configure Telemetry central agent service"
+msgstr "Telemetry 中央エージェントサービスの設定"
+
+#: ./doc/high-availability-guide/api/section_ceilometer_agent_central.xml54(simpara)
+msgid "Edit <literal>/etc/ceilometer/ceilometer.conf</literal> :"
+msgstr "<literal>/etc/ceilometer/ceilometer.conf</literal> を編集します。"
+
+#: ./doc/high-availability-guide/api/section_keystone.xml6(title)
+msgid "Highly available OpenStack Identity"
+msgstr "高可用性 OpenStack Identity"
+
+#: ./doc/high-availability-guide/api/section_keystone.xml8(simpara)
+msgid ""
+"OpenStack Identity is the Identity Service in OpenStack and used by many "
+"services. Making the OpenStack Identity service highly available in active /"
+" passive mode involves"
+msgstr "OpenStack Identity は OpenStack における認証サービスです。OpenStack Identity Service をアクティブ / パッシブモードで高可用性にすることは、次のことが関連します。"
+
+#: ./doc/high-availability-guide/api/section_keystone.xml12(simpara)
+msgid "Configure OpenStack Identity to listen on the VIP address,"
+msgstr "OpenStack Identity がその仮想 IP アドレスでリッスンするよう設定します。"
+
+#: ./doc/high-availability-guide/api/section_keystone.xml17(simpara)
+msgid "managing OpenStack Identity daemon with the Pacemaker cluster manager,"
+msgstr "Pacemaker クラスターマネージャーを用いた OpenStack Identity デーモンの管理"
+
+#: ./doc/high-availability-guide/api/section_keystone.xml28(simpara)
+msgid ""
+"Here is the <link href=\"http://docs.openstack.org/trunk/install-"
+"guide/install/apt/content/ch_installing-openstack-identity-"
+"service.html\">documentation</link> for installing OpenStack Identity "
+"service."
+msgstr "ここに OpenStack Identity Service をインストールするための<link href=\"http://docs.openstack.org/trunk/install-guide/install/apt/content/ch_installing-openstack-identity-service.html\">ドキュメント</link>があります。"
+
+#: ./doc/high-availability-guide/api/section_keystone.xml32(title)
+msgid "Add OpenStack Identity resource to Pacemaker"
+msgstr "OpenStack Identity リソースの Pacemaker への追加"
+
+#: ./doc/high-availability-guide/api/section_keystone.xml40(simpara)
+msgid ""
+"You can now add the Pacemaker configuration for OpenStack Identity resource."
+" Connect to the Pacemaker cluster with <literal>crm configure</literal>, and"
+" add the following cluster resources:"
+msgstr "OpenStack Identity リソース用の Pacemaker 設定を追加できます。<literal>crm configure</literal> を用いて Pacemaker クラスターに接続し、以下のクラスターリソースを追加します。"
+
+#: ./doc/high-availability-guide/api/section_keystone.xml46(simpara)
+msgid ""
+"This configuration creates <literal>p_keystone</literal>, a resource for "
+"managing the OpenStack Identity service."
+msgstr "この設定は OpenStack Identity サービスを管理するためのリソース <literal>p_keystone</literal> を作成します。"
+
+#: ./doc/high-availability-guide/api/section_keystone.xml47(simpara)
+msgid ""
+"<literal>crm configure</literal> supports batch input, so you may copy and "
+"paste the above into your live pacemaker configuration, and then make "
+"changes as required. For example, you may enter <literal>edit "
+"p_ip_keystone</literal> from the <literal>crm configure</literal> menu and "
+"edit the resource to match your preferred virtual IP address."
+msgstr "<literal>crm configure</literal> はバッチ入力をサポートします。そのため、現在の pacemaker 設定の中に上をコピー・ペーストし、適宜変更を反映できます。たとえば、お好みの仮想 IP アドレスに一致させるために、<literal>crm configure</literal> メニューから <literal>edit p_ip_keystone</literal> と入力し、リソースを編集できます。"
+
+#: ./doc/high-availability-guide/api/section_keystone.xml52(simpara)
+msgid ""
+"Once completed, commit your configuration changes by entering "
+"<literal>commit</literal> from the <literal>crm configure</literal> menu. "
+"Pacemaker will then start the OpenStack Identity service, and its dependent "
+"resources, on one of your nodes."
+msgstr "完了すると、<literal>crm configure</literal> メニューから <literal>commit</literal> と入力し、設定の変更をコミットします。Pacemaker は OpenStack Identity サービスおよび依存するリソースを同じノードに起動します。"
+
+#: ./doc/high-availability-guide/api/section_keystone.xml58(title)
+msgid "Configure OpenStack Identity service"
+msgstr "OpenStack Identity Service の設定"
+
+#: ./doc/high-availability-guide/api/section_keystone.xml60(simpara)
+msgid ""
+"You need to edit your OpenStack Identity configuration file "
+"(<literal>keystone.conf</literal>) and change the bind parameters:"
+msgstr "OpenStack Identity の設定ファイル (<literal>keystone.conf</literal>) を編集し、バインドのパラメーターを変更する必要があります。"
+
+#: ./doc/high-availability-guide/api/section_keystone.xml61(simpara)
+msgid "On Havana:"
+msgstr "Havana の場合:"
+
+#: ./doc/high-availability-guide/api/section_keystone.xml63(simpara)
+msgid ""
+"On Icehouse, the <literal>admin_bind_host</literal> option lets you use a "
+"private network for the admin access."
+msgstr "Icehouse の場合、<literal>admin_bind_host</literal> オプションにより管理アクセス用のプライベートネットワークを使用できます。"
+
+#: ./doc/high-availability-guide/api/section_keystone.xml66(simpara)
+msgid ""
+"To be sure all data will be highly available, you should be sure that you "
+"store everything in the MySQL database (which is also highly available):"
+msgstr "確実にすべてのデータが高可用性にするために、確実にすべてのものを (高可用性な) MySQL データベースに保存すべきです。"
+
+#: ./doc/high-availability-guide/api/section_keystone.xml76(title)
+msgid ""
+"Configure OpenStack services to use the highly available OpenStack Identity"
+msgstr "高可用性 OpenStack Identity を使用するための OpenStack サービスの設定"
+
+#: ./doc/high-availability-guide/api/section_keystone.xml78(simpara)
+msgid ""
+"Your OpenStack services must now point their OpenStack Identity "
+"configuration to the highly available, virtual cluster IP address — rather "
+"than a OpenStack Identity server’s physical IP address as you normally "
+"would."
+msgstr "OpenStack サービスは、通常どおり OpenStack Identity サーバーの物理 IP アドレスを指定する代わりに、OpenStack Identity サーバーの設定が高可用性と仮想クラスター IP アドレスを指し示す必要があります。"
+
+#: ./doc/high-availability-guide/api/section_keystone.xml81(simpara)
+msgid ""
+"For example with OpenStack Compute, if your OpenStack Identity service IP "
+"address is 192.168.42.103 as in the configuration explained here, you would "
+"use the following line in your API configuration file (<literal>api-"
+"paste.ini</literal>):"
+msgstr "OpenStack Compute を用いた例として、OpenStack Identity Service の IP アドレスがここで説明された設定にあるように 192.168.42.103 ならば、API 設定ファイル (<literal>api-paste.ini</literal>) で以下の行を使用する必要があります。"
+
+#: ./doc/high-availability-guide/api/section_keystone.xml86(simpara)
+msgid "You also need to create the OpenStack Identity Endpoint with this IP."
+msgstr "この IP を用いて OpenStack Identity エンドポイントを作成する必要があります。"
+
+#: ./doc/high-availability-guide/api/section_keystone.xml87(simpara)
+msgid ""
+"NOTE : If you are using both private and public IP addresses, you should "
+"create two Virtual IP addresses and define your endpoint like this:"
+msgstr "注: プライベート IP とパブリック IP の両方を使用する場合、2 つの仮想 IP アドレスを作成し、次のようにエンドポイントを定義すべきです。"
+
+#: ./doc/high-availability-guide/api/section_keystone.xml89(simpara)
+msgid ""
+"If you are using the horizon dashboard, you should edit the "
+"<literal>local_settings.py</literal> file:"
+msgstr "Dashboard を使用している場合、<literal>local_settings.py</literal> ファイルを編集する必要があります。"
+
+#: ./doc/high-availability-guide/api/section_api_vip.xml6(title)
+msgid "Configure the VIP"
+msgstr "仮想 IP の設定"
+
+#: ./doc/high-availability-guide/api/section_api_vip.xml8(simpara)
+msgid ""
+"First, you must select and assign a virtual IP address (VIP) that can freely"
+" float between cluster nodes."
+msgstr "まず初めに、クラスターノード間で自由に移動できる仮想 IP アドレス (VIP) を選択して割り当てる必要があります。"
+
+#: ./doc/high-availability-guide/api/section_api_vip.xml9(simpara)
+msgid ""
+"This configuration creates <literal>p_ip_api</literal>, a virtual IP address"
+" for use by the API node (192.168.42.103) :"
+msgstr "この設定は API ノードにより使用される仮想 IP アドレス (192.168.42.103) <literal>p_ip_api</literal> を作成します。"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml6(title)
+msgid "Highly available RabbitMQ"
+msgstr "高可用性 RabbitMQ"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml8(simpara)
+msgid ""
+"RabbitMQ is the default AMQP server used by many OpenStack services. Making "
+"the RabbitMQ service highly available involves:"
+msgstr "RabbitMQ が多くの OpenStack サービスにより使用される標準の AMQP サーバーです。RabbitMQ サービスを高可用性にすることは、次のことが関連します。"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml12(simpara)
+msgid "configuring a DRBD device for use by RabbitMQ,"
+msgstr "RabbitMQ により使用するための DRBD デバイスを設定します。"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml17(simpara)
+msgid ""
+"configuring RabbitMQ to use a data directory residing on that DRBD device,"
+msgstr "RabbitMQ が DRBD デバイスにあるデータディレクトリを使用するよう設定します。"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml23(simpara)
+#: ./doc/high-availability-guide/controller/section_mysql.xml23(simpara)
+msgid ""
+"selecting and assigning a virtual IP address (VIP) that can freely float "
+"between cluster nodes,"
+msgstr "クラスターノード間で自由に移動できる仮想 IP アドレス (VIP) を選択して割り当てます。"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml29(simpara)
+msgid "configuring RabbitMQ to listen on that IP address,"
+msgstr "RabbitMQ がその IP アドレスでリッスンするよう設定します。"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml34(simpara)
+msgid ""
+"managing all resources, including the RabbitMQ daemon itself, with the "
+"Pacemaker cluster manager."
+msgstr "RabbitMQ デーモン自身を含む、すべてのリソースを Pacemaker クラスターマネージャーで管理します。"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml41(simpara)
+msgid ""
+"There is an alternative method of configuring RabbitMQ for high "
+"availability. That approach, known as <link "
+"href=\"http://www.rabbitmq.com/ha.html\">active-active mirrored "
+"queues</link>, happens to be the one preferred by the RabbitMQ developers — "
+"however it has shown less than ideal consistency and reliability in "
+"OpenStack clusters. Thus, at the time of writing, the Pacemaker/DRBD based "
+"approach remains the recommended one for OpenStack environments, although "
+"this may change in the near future as RabbitMQ active-active mirrored queues"
+" mature."
+msgstr "RabbitMQ を高可用性に設定する別の方法があります。この方法は、<link href=\"http://www.rabbitmq.com/ha.html\">アクティブ・アクティブのキューのミラー</link>として知られ、RabbitMQ 開発者に好まれているものです。しかしながら、OpenStack クラスターにおける理想的な一貫性と信頼性よりは劣るものです。そのため、執筆時点では、Pacemaker/DRBD による方法が OpenStack 環境に対する推奨事項として残されています。これは RabbitMQ のアクティブ・アクティブのキューのミラーが成熟すると、近い将来に変更される可能性もあります。"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml53(title)
+#: ./doc/high-availability-guide/controller/section_mysql.xml50(title)
+msgid "Configure DRBD"
+msgstr "DRBD の設定"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml55(simpara)
+msgid ""
+"The Pacemaker based RabbitMQ server requires a DRBD resource from which it "
+"mounts the <literal>/var/lib/rabbitmq</literal> directory. In this example, "
+"the DRBD resource is simply named <literal>rabbitmq</literal>:"
+msgstr "Pacemaker ベースの RabbitMQ サーバーは <literal>/var/lib/rabbitmq</literal> ディレクトリをマウントする DRBD リソースが必要です。この例では、DRBD リソースは単に <literal>rabbitmq</literal> という名前になっています。"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml60(title)
+msgid ""
+"<literal>rabbitmq</literal> DRBD resource configuration "
+"(<literal>/etc/drbd.d/rabbitmq.res</literal>)"
+msgstr "<literal>rabbitmq</literal> DRBD リソース設定 (<literal>/etc/drbd.d/rabbitmq.res</literal>)"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml76(simpara)
+msgid ""
+"This resource uses an underlying local disk (in DRBD terminology, a "
+"<emphasis>backing device</emphasis>) named "
+"<literal>/dev/data/rabbitmq</literal> on both cluster nodes, "
+"<literal>node1</literal> and <literal>node2</literal>. Normally, this would "
+"be an LVM Logical Volume specifically set aside for this purpose. The DRBD "
+"<literal>meta-disk</literal> is <literal>internal</literal>, meaning DRBD-"
+"specific metadata is being stored at the end of the <literal>disk</literal> "
+"device itself. The device is configured to communicate between IPv4 "
+"addresses 10.0.42.100 and 10.0.42.254, using TCP port 7701. Once enabled, it"
+" will map to a local DRBD block device with the device minor number 1, that "
+"is, <literal>/dev/drbd1</literal>."
+msgstr "このリソースは、両方のクラスターノード <literal>node1</literal> と <literal>node2</literal> において、<literal>/dev/data/rabbitmq</literal> という名前のバックエンドのローカルディスク (DRBD の用語で <emphasis>backing device</emphasis>) を使用します。通常、これはこの目的のために特別に設定された LVM 論理ボリュームでしょう。DRBD <literal>meta-disk</literal> は <literal>internal</literal> です。これは DRBD 固有のメタデータが <literal>disk</literal> デバイス自身の最後に保存されることを意味します。このデバイスは IPv4 アドレス 10.0.42.100 と 10.0.42.254 の間で TCP ポート 7701 を使用して通信するよう設定されます。一度有効化されると、デバイスマイナー番号 1 を持つローカル DRBD ブロックデバイス、つまり <literal>/dev/drbd1</literal> にマップされます。"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml85(simpara)
+#: ./doc/high-availability-guide/controller/section_mysql.xml82(simpara)
+msgid ""
+"Enabling a DRBD resource is explained in detail in <link "
+"href=\"http://www.drbd.org/users-guide-8.3/s-first-time-up.html\">the DRBD "
+"User’s Guide</link>. In brief, the proper sequence of commands is this:"
+msgstr "DRBD リソースを有効化する方法は <link href=\"http://www.drbd.org/users-guide-8.3/s-first-time-up.html\">DRBD ユーザーガイド</link> に詳細に説明されています。要約すると、正しいコマンドの流れはこのとおりです。"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml93(para)
+msgid ""
+"Initializes DRBD metadata and writes the initial set of metadata to "
+"<literal>/dev/data/rabbitmq</literal>. Must be completed on both nodes."
+msgstr "DRBD メタデータを初期化し、メタデータの初期セットを <literal>/dev/data/rabbitmq</literal> に書き込みます。両方のノードで完了する必要があります。"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml99(para)
+msgid ""
+"Creates the <literal>/dev/drbd1</literal> device node, "
+"<emphasis>attaches</emphasis> the DRBD device to its backing store, and "
+"<emphasis>connects</emphasis> the DRBD node to its peer. Must be completed "
+"on both nodes."
+msgstr "<literal>/dev/drbd1</literal> デバイスノードを作成し、DRBD デバイスをそのバックエンドに<emphasis>接続</emphasis>し、DRBD ノードを同期先に<emphasis>接続</emphasis>します。両方のノードで完了する必要があります。"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml106(para)
+#: ./doc/high-availability-guide/controller/section_mysql.xml103(para)
+msgid ""
+"Kicks off the initial device synchronization, and puts the device into the "
+"<literal>primary</literal> (readable and writable) role. See <link "
+"href=\"http://www.drbd.org/users-guide-8.3/ch-admin.html#s-roles\">Resource "
+"roles</link> (from the DRBD User’s Guide) for a more detailed description of"
+" the primary and secondary roles in DRBD. Must be completed <emphasis>on one"
+" node only,</emphasis> namely the one where you are about to continue with "
+"creating your filesystem."
+msgstr "初期デバイス同期を開始し、デバイスを <literal>プライマリ</literal> (読み書き可能) ロールにします。DRBD のプライマリロールとセカンダリロールの詳細は (DRBD User’s Guide の) <link href=\"http://www.drbd.org/users-guide-8.3/ch-admin.html#s-roles\">Resource roles</link> を参照してください。必ず<emphasis>一つのノードのみで</emphasis>実行する必要があります。つまり、ファイルシステムを作成しようとしているノードのみです。"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml120(title)
+msgid "Create a file system"
+msgstr "ファイルシステムの作成"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml122(simpara)
+msgid ""
+"Once the DRBD resource is running and in the primary role (and potentially "
+"still in the process of running the initial device synchronization), you may"
+" proceed with creating the filesystem for RabbitMQ data. XFS is generally "
+"the recommended filesystem:"
+msgstr "DRBD リソースが実行中になり、プライマリロールになると (まだ初期デバイス同期が実行中かもしれません)、RabbitMQ データのファイルシステムの作成を進められます。XFS が一般的に推奨されるファイルシステムです。"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml127(simpara)
+#: ./doc/high-availability-guide/controller/section_mysql.xml124(simpara)
+msgid ""
+"You may also use the alternate device path for the DRBD device, which may be"
+" easier to remember as it includes the self-explanatory resource name:"
+msgstr "DRBD デバイスに対する代替デバイスパスを使用することもできます。これは自己説明的なリソース名を含むため、より覚えやすいでしょう。"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml131(simpara)
+#: ./doc/high-availability-guide/controller/section_mysql.xml128(simpara)
+msgid ""
+"Once completed, you may safely return the device to the secondary role. Any "
+"ongoing device synchronization will continue in the background:"
+msgstr "一度完了すると、デバイスを安全にセカンダリロールに戻せます。すべての動作中のデバイス同期はバックエンドで継続されます。"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml138(title)
+msgid "Prepare RabbitMQ for Pacemaker high availability"
+msgstr "Pacemaker 高可用性のための RabbitMQ の準備"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml140(simpara)
+msgid ""
+"In order for Pacemaker monitoring to function properly, you must ensure that"
+" RabbitMQ’s <literal>.erlang.cookie</literal> files are identical on all "
+"nodes, regardless of whether DRBD is mounted there or not. The simplest way "
+"of doing so is to take an existing <literal>.erlang.cookie</literal> from "
+"one of your nodes, copying it to the RabbitMQ data directory on the other "
+"node, and also copying it to the DRBD-backed filesystem."
+msgstr "Pacemaker の監視を正しく機能させるために、DRBD がマウントされているかどうかに関わらず、RabbitMQ の <literal>.erlang.cookie</literal> ファイルをすべてのノードで必ず同じにする必要があります。そうする最も簡単な方法は、どこかのノードから既存の <literal>.erlang.cookie</literal> を取得し、他のノードの RabbitMQ データディレクトリおよび DRBD のバックエンドファイルシステムにコピーすることです。"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml153(title)
+msgid "Add RabbitMQ resources to Pacemaker"
+msgstr "RabbitMQ リソースの Pacemaker への追加"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml155(simpara)
+msgid ""
+"You may now proceed with adding the Pacemaker configuration for RabbitMQ "
+"resources. Connect to the Pacemaker cluster with <literal>crm "
+"configure</literal>, and add the following cluster resources:"
+msgstr "OpenStack RabbitMQ リソース用の Pacemaker 設定を追加して、次に進むことができます。<literal>crm configure</literal> を用いて Pacemaker クラスターに接続し、以下のクラスターリソースを追加します。"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml188(simpara)
+msgid ""
+"<literal>p_ip_rabbitmp</literal>, a virtual IP address for use by RabbitMQ "
+"(192.168.42.100),"
+msgstr "<literal>p_ip_rabbitmp</literal>, RabbitMQ により使用される仮想 IP アドレス (192.168.42.100),"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml193(simpara)
+msgid ""
+"<literal>p_fs_rabbitmq</literal>, a Pacemaker managed filesystem mounted to "
+"<literal>/var/lib/rabbitmq</literal> on whatever node currently runs the "
+"RabbitMQ service,"
+msgstr "<literal>p_fs_rabbitmq</literal>, 現在 RabbitMQ サービスを実行している、すべてのノードにおいて <literal>/var/lib/rabbitmq</literal> にマウントされている、Pacemaker が管理しているファイルシステム。"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml199(simpara)
+msgid ""
+"<literal>ms_drbd_rabbitmq</literal>, the <emphasis>master/slave "
+"set</emphasis> managing the <literal>rabbitmq</literal> DRBD resource,"
+msgstr "<literal>ms_drbd_rabbitmq</literal>, <literal>rabbitmq</literal> DRBD リソースを管理している<emphasis>マスター/スレーブの組</emphasis>。"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml204(simpara)
+#: ./doc/high-availability-guide/controller/section_mysql.xml216(simpara)
+msgid ""
+"a service <literal>group</literal> and <literal>order</literal> and "
+"<literal>colocation</literal> constraints to ensure resources are started on"
+" the correct nodes, and in the correct sequence."
+msgstr "リソースが適切なノードにおいて、適切な順序で起動されることを確実にする、サービスの <literal>group</literal>, <literal>order</literal> および <literal>colocation</literal> 制約。"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml210(simpara)
+msgid ""
+"<literal>crm configure</literal> supports batch input, so you may copy and "
+"paste the above into your live pacemaker configuration, and then make "
+"changes as required. For example, you may enter <literal>edit "
+"p_ip_rabbitmq</literal> from the <literal>crm configure</literal> menu and "
+"edit the resource to match your preferred virtual IP address."
+msgstr "<literal>crm configure</literal> はバッチ入力をサポートします。そのため、現在の pacemaker 設定の中に上をコピー・ペーストし、適宜変更を反映できます。たとえば、お好みの仮想 IP アドレスに一致させるために、<literal>crm configure</literal> メニューから <literal>edit p_ip_rabbitmq</literal> と入力し、リソースを編集できます。"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml215(simpara)
+msgid ""
+"Once completed, commit your configuration changes by entering "
+"<literal>commit</literal> from the <literal>crm configure</literal> menu. "
+"Pacemaker will then start the RabbitMQ service, and its dependent resources,"
+" on one of your nodes."
+msgstr "完了すると、<literal>crm configure</literal> メニューから <literal>commit</literal> と入力し、設定の変更をコミットします。Pacemaker は RabbitMQ サービスおよび依存するリソースを同じノードに起動します。"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml221(title)
+msgid "Configure OpenStack services for highly available RabbitMQ"
+msgstr "高可用性 RabbitMQ のための OpenStack サービスの設定"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml223(simpara)
+msgid ""
+"Your OpenStack services must now point their RabbitMQ configuration to the "
+"highly available, virtual cluster IP address — rather than a RabbitMQ "
+"server’s physical IP address as you normally would."
+msgstr "OpenStack サービスは、通常どおり RabbitMQ サーバーの物理 IP アドレスを指定する代わりに、RabbitMQ の設定が高可用性と仮想クラスター IP アドレスを指し示す必要があります。"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml226(simpara)
+msgid ""
+"For OpenStack Image, for example, if your RabbitMQ service IP address is "
+"192.168.42.100 as in the configuration explained here, you would use the "
+"following line in your OpenStack Image API configuration file (<literal"
+">glance-api.conf</literal>):"
+msgstr "OpenStack Image の例として、RabbitMQ サーバーの IP アドレスがここで説明された設定にあるように 192.168.42.100 ならば、OpenStack Image API 定ファイル (<literal>glance-api.conf</literal>) で以下の行を使用する必要があります。"
+
+#: ./doc/high-availability-guide/controller/section_rabbitmq.xml231(simpara)
+msgid ""
+"No other changes are necessary to your OpenStack configuration. If the node "
+"currently hosting your RabbitMQ experiences a problem necessitating service "
+"failover, your OpenStack services may experience a brief RabbitMQ "
+"interruption, as they would in the event of a network hiccup, and then "
+"continue to run normally."
+msgstr "OpenStack の設定に他の変更は必要ありません。現在 RabbitMQ を稼働しているノードが、サービスのフェイルオーバーを必要とする問題に遭遇した場合、ネットワークの中断と通常どおりの動作継続により、OpenStack のサービスは MySQL の短時間の中断に遭遇するかもしれません。"
+
 #: ./doc/high-availability-guide/controller/section_mysql.xml6(title)
 msgid "Highly available MySQL"
 msgstr "高可用性 MySQL"
@@ -1927,13 +1479,6 @@ msgstr "MySQL により使用するための DRBD デバイスの設定,"
 msgid "Configure MySQL to use a data directory residing on that DRBD device,"
 msgstr "MySQL がこの DRBD デバイスにあるデータディレクトリを使用するよう設定します。"
 
-#: ./doc/high-availability-guide/controller/section_mysql.xml23(simpara)
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml23(simpara)
-msgid ""
-"selecting and assigning a virtual IP address (VIP) that can freely float "
-"between cluster nodes,"
-msgstr "クラスターノード間で自由に移動できる仮想 IP アドレス (VIP) を選択して割り当てます。"
-
 #: ./doc/high-availability-guide/controller/section_mysql.xml29(simpara)
 msgid "Configure MySQL to listen on that IP address,"
 msgstr "その IP アドレスをリッスンするよう MySQL を設定します。"
@@ -1955,11 +1500,6 @@ msgid ""
 "environments."
 msgstr "<link href=\"http://codership.com/products/mysql_galera\">MySQL/Galera</link> は MySQL を高可用性に設定するもう一つの方法です。十分に成熟すれば、MySQL の高可用性を達成する好ましい方法になるでしょう。しかしながら、執筆時点では、Pacemaker/DRBD による方法が OpenStack 環境に対する推奨のものです。"
 
-#: ./doc/high-availability-guide/controller/section_mysql.xml50(title)
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml53(title)
-msgid "Configure DRBD"
-msgstr "DRBD の設定"
-
 #: ./doc/high-availability-guide/controller/section_mysql.xml52(simpara)
 msgid ""
 "The Pacemaker based MySQL server requires a DRBD resource from which it "
@@ -1988,14 +1528,6 @@ msgid ""
 "is, <literal>/dev/drbd0</literal>."
 msgstr "このリソースは、両方のクラスターノード <literal>node1</literal> と <literal>node2</literal> において、<literal>/dev/data/mysql</literal> という名前のバックエンドのローカルディスク (DRBD の用語で <emphasis>backing device</emphasis>) を使用します。通常、これはこの目的のために特別に設定された LVM 論理ボリュームでしょう。DRBD <literal>meta-disk</literal> は <literal>internal</literal> です。これは DRBD 固有のメタデータが <literal>disk</literal> デバイス自身の最後に保存されることを意味します。このデバイスは IPv4 アドレス 10.0.42.100 と 10.0.42.254 の間で TCP ポート 7700 を使用して通信するよう設定されます。一度有効化されると、デバイスマイナー番号 0 を持つローカル DRBD ブロックデバイス、つまり <literal>/dev/drbd0</literal> にマップされます。"
 
-#: ./doc/high-availability-guide/controller/section_mysql.xml82(simpara)
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml85(simpara)
-msgid ""
-"Enabling a DRBD resource is explained in detail in <link "
-"href=\"http://www.drbd.org/users-guide-8.3/s-first-time-up.html\">the DRBD "
-"User’s Guide</link>. In brief, the proper sequence of commands is this:"
-msgstr "DRBD リソースを有効化する方法は <link href=\"http://www.drbd.org/users-guide-8.3/s-first-time-up.html\">DRBD ユーザーガイド</link> に詳細に説明されています。要約すると、正しいコマンドの流れはこのとおりです。"
-
 #: ./doc/high-availability-guide/controller/section_mysql.xml90(para)
 msgid ""
 "Initializes DRBD metadata and writes the initial set of metadata to "
@@ -2010,18 +1542,6 @@ msgid ""
 "on both nodes."
 msgstr "<literal>/dev/drbd0</literal> デバイスノードを作成し、DRBD デバイスをそのバックエンドに<emphasis>接続</emphasis>し、DRBD ノードを同期先に<emphasis>接続</emphasis>します。両方のノードで完了する必要があります。"
 
-#: ./doc/high-availability-guide/controller/section_mysql.xml103(para)
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml106(para)
-msgid ""
-"Kicks off the initial device synchronization, and puts the device into the "
-"<literal>primary</literal> (readable and writable) role. See <link "
-"href=\"http://www.drbd.org/users-guide-8.3/ch-admin.html#s-roles\">Resource "
-"roles</link> (from the DRBD User’s Guide) for a more detailed description of"
-" the primary and secondary roles in DRBD. Must be completed <emphasis>on one"
-" node only,</emphasis> namely the one where you are about to continue with "
-"creating your filesystem."
-msgstr "初期デバイス同期を開始し、デバイスを <literal>プライマリ</literal> (読み書き可能) ロールにします。DRBD のプライマリロールとセカンダリロールの詳細は (DRBD User’s Guide の) <link href=\"http://www.drbd.org/users-guide-8.3/ch-admin.html#s-roles\">Resource roles</link> を参照してください。必ず<emphasis>一つのノードのみで</emphasis>実行する必要があります。つまり、ファイルシステムを作成しようとしているノードのみです。"
-
 #: ./doc/high-availability-guide/controller/section_mysql.xml117(title)
 msgid "Creating a file system"
 msgstr "ファイルシステムの作成"
@@ -2034,20 +1554,6 @@ msgid ""
 "recommended filesystem:"
 msgstr "DRBD リソースが実行中になり、プライマリロールになると (まだ初期デバイス同期が実行中かもしれません)、MySQL データのファイルシステムの作成を進められます。XFS が一般的に推奨されるファイルシステムです。"
 
-#: ./doc/high-availability-guide/controller/section_mysql.xml124(simpara)
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml127(simpara)
-msgid ""
-"You may also use the alternate device path for the DRBD device, which may be"
-" easier to remember as it includes the self-explanatory resource name:"
-msgstr "DRBD デバイスに対する代替デバイスパスを使用することもできます。これは自己説明的なリソース名を含むため、より覚えやすいでしょう。"
-
-#: ./doc/high-availability-guide/controller/section_mysql.xml128(simpara)
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml131(simpara)
-msgid ""
-"Once completed, you may safely return the device to the secondary role. Any "
-"ongoing device synchronization will continue in the background:"
-msgstr "一度完了すると、デバイスを安全にセカンダリロールに戻せます。すべての動作中のデバイス同期はバックエンドで継続されます。"
-
 #: ./doc/high-availability-guide/controller/section_mysql.xml135(title)
 msgid "Prepare MySQL for Pacemaker high availability"
 msgstr "Pacemaker 高可用性のための MySQL の準備"
@@ -2109,14 +1615,6 @@ msgid ""
 "managing the <literal>mysql</literal> DRBD resource,"
 msgstr "<literal>ms_drbd_mysql</literal>, <literal>mysql</literal> DRBD リソースを管理している<emphasis>マスター/スレーブの組</emphasis>。"
 
-#: ./doc/high-availability-guide/controller/section_mysql.xml216(simpara)
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml204(simpara)
-msgid ""
-"a service <literal>group</literal> and <literal>order</literal> and "
-"<literal>colocation</literal> constraints to ensure resources are started on"
-" the correct nodes, and in the correct sequence."
-msgstr "リソースが適切なノードにおいて、適切な順序で起動されることを確実にする、サービスの <literal>group</literal>, <literal>order</literal> および <literal>colocation</literal> 制約。"
-
 #: ./doc/high-availability-guide/controller/section_mysql.xml222(simpara)
 msgid ""
 "<literal>crm configure</literal> supports batch input, so you may copy and "
@@ -2162,192 +1660,694 @@ msgid ""
 "normally."
 msgstr "OpenStack の設定に他の変更は必要ありません。現在データベースを稼働しているノードが、サービスのフェイルオーバーを必要とする問題に遭遇した場合、ネットワークの中断と通常どおりの動作継続により、OpenStack のサービスは MySQL の短時間の中断に遭遇するかもしれません。"
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml6(title)
-msgid "Highly available RabbitMQ"
-msgstr "高可用性 RabbitMQ"
+#: ./doc/high-availability-guide/ha_aa_controllers/section_memcached.xml6(title)
+msgid "Memcached"
+msgstr "Memcached"
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml8(simpara)
+#: ./doc/high-availability-guide/ha_aa_controllers/section_memcached.xml8(simpara)
 msgid ""
-"RabbitMQ is the default AMQP server used by many OpenStack services. Making "
-"the RabbitMQ service highly available involves:"
-msgstr "RabbitMQ が多くの OpenStack サービスにより使用される標準の AMQP サーバーです。RabbitMQ サービスを高可用性にすることは、次のことが関連します。"
+"Most of OpenStack services use an application to offer persistence and store"
+" ephemeral data (like tokens). Memcached is one of them and can scale-out "
+"easily without specific trick."
+msgstr "ほとんどの OpenStack サービスは、永続性を提供し、(トークンのような) 一時的なデータを保存するために、アプリケーションを使用します。memcached は、それらの一つで、特別な工夫をすることなく簡単にスケールアウト可能にできます。"
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml12(simpara)
-msgid "configuring a DRBD device for use by RabbitMQ,"
-msgstr "RabbitMQ により使用するための DRBD デバイスを設定します。"
-
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml17(simpara)
+#: ./doc/high-availability-guide/ha_aa_controllers/section_memcached.xml10(simpara)
 msgid ""
-"configuring RabbitMQ to use a data directory residing on that DRBD device,"
-msgstr "RabbitMQ が DRBD デバイスにあるデータディレクトリを使用するよう設定します。"
+"To install and configure it, read the <link "
+"href=\"http://code.google.com/p/memcached/wiki/NewStart\">official "
+"documentation</link>."
+msgstr "インストールおよび設定するために、<link href=\"http://code.google.com/p/memcached/wiki/NewStart\">公式ドキュメント</link>を参照します。"
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml29(simpara)
-msgid "configuring RabbitMQ to listen on that IP address,"
-msgstr "RabbitMQ がその IP アドレスでリッスンするよう設定します。"
-
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml34(simpara)
+#: ./doc/high-availability-guide/ha_aa_controllers/section_memcached.xml11(simpara)
 msgid ""
-"managing all resources, including the RabbitMQ daemon itself, with the "
-"Pacemaker cluster manager."
-msgstr "RabbitMQ デーモン自身を含む、すべてのリソースを Pacemaker クラスターマネージャーで管理します。"
+"Memory caching is managed by oslo-incubator so the way to use multiple "
+"memcached servers is the same for all projects."
+msgstr "メモリキャッシュは、複数の memcached サーバーを使用する方法がすべてのプロジェクトで同じにするために、Oslo インキュベーターにより管理されています。"
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml41(simpara)
+#: ./doc/high-availability-guide/ha_aa_controllers/section_memcached.xml12(simpara)
+msgid "Example with two hosts:"
+msgstr "2 つのホストを用いた例:"
+
+#: ./doc/high-availability-guide/ha_aa_controllers/section_memcached.xml14(simpara)
 msgid ""
-"There is an alternative method of configuring RabbitMQ for high "
-"availability. That approach, known as <link "
-"href=\"http://www.rabbitmq.com/ha.html\">active-active mirrored "
-"queues</link>, happens to be the one preferred by the RabbitMQ developers — "
-"however it has shown less than ideal consistency and reliability in "
-"OpenStack clusters. Thus, at the time of writing, the Pacemaker/DRBD based "
-"approach remains the recommended one for OpenStack environments, although "
-"this may change in the near future as RabbitMQ active-active mirrored queues"
-" mature."
-msgstr "RabbitMQ を高可用性に設定する別の方法があります。この方法は、<link href=\"http://www.rabbitmq.com/ha.html\">アクティブ・アクティブのキューのミラー</link>として知られ、RabbitMQ 開発者に好まれているものです。しかしながら、OpenStack クラスターにおける理想的な一貫性と信頼性よりは劣るものです。そのため、執筆時点では、Pacemaker/DRBD による方法が OpenStack 環境に対する推奨事項として残されています。これは RabbitMQ のアクティブ・アクティブのキューのミラーが成熟すると、近い将来に変更される可能性もあります。"
+"By default, controller1 handles the caching service but if the host goes "
+"down, controller2 does the job. For more information about memcached "
+"installation, see the OpenStack Cloud Administrator Guide."
+msgstr "デフォルトで、controller1 がキャッシュサービスを処理します。しかし、このホストが停止すると、controller2 がこのジョブを実行します。memcached のインストールに関する詳細は OpenStack クラウド管理者ガイドを参照してください。"
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml55(simpara)
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml6(title)
+msgid "Run OpenStack API and schedulers"
+msgstr "OpenStack API &amp; スケジューラーの実行"
+
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml10(title)
+msgid "API services"
+msgstr "API サービス"
+
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml12(simpara)
 msgid ""
-"The Pacemaker based RabbitMQ server requires a DRBD resource from which it "
-"mounts the <literal>/var/lib/rabbitmq</literal> directory. In this example, "
-"the DRBD resource is simply named <literal>rabbitmq</literal>:"
-msgstr "Pacemaker ベースの RabbitMQ サーバーは <literal>/var/lib/rabbitmq</literal> ディレクトリをマウントする DRBD リソースが必要です。この例では、DRBD リソースは単に <literal>rabbitmq</literal> という名前になっています。"
+"All OpenStack projects have an API service for controlling all the resources"
+" in the Cloud. In Active / Active mode, the most common setup is to scale-"
+"out these services on at least two nodes and use load-balancing and virtual "
+"IP (with HAproxy &amp; Keepalived in this setup)."
+msgstr "すべての OpenStack プロジェクトは、クラウドにあるすべてのリソースを制御するための API サービスを持ちます。アクティブ / アクティブモードの場合、最も一般的なセットアップ環境は、少なくとも 2 つのノードにこれらのサービスをスケールアウトし、(このセットアップで HAproxy と Keepalived を用いて) 負荷分散および仮想 IP を使用します。"
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml60(title)
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml16(emphasis)
+msgid "Configure API OpenStack services"
+msgstr "OpenStack サービスの API の設定"
+
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml18(simpara)
 msgid ""
-"<literal>rabbitmq</literal> DRBD resource configuration "
-"(<literal>/etc/drbd.d/rabbitmq.res</literal>)"
-msgstr "<literal>rabbitmq</literal> DRBD リソース設定 (<literal>/etc/drbd.d/rabbitmq.res</literal>)"
+"To configure our Cloud using Highly available and scalable API services, we "
+"need to ensure that:"
+msgstr "私たちのクラウド環境が高可用性かつスケーラブルな API サービスを使用するよう設定するために、以下の事項を確認する必要があります。"
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml76(simpara)
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml21(simpara)
+msgid "You use Virtual IP when configuring OpenStack Identity endpoints."
+msgstr "OpenStack Identity エンドポイントを設定するときに仮想 IP を使用します。"
+
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml26(simpara)
+msgid "All OpenStack configuration files should refer to Virtual IP."
+msgstr "すべての OpenStack 設定ファイルは仮想 IP を参照すべきです。"
+
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml32(emphasis)
+msgid "In case of failure"
+msgstr "失敗の場合"
+
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml34(simpara)
 msgid ""
-"This resource uses an underlying local disk (in DRBD terminology, a "
-"<emphasis>backing device</emphasis>) named "
-"<literal>/dev/data/rabbitmq</literal> on both cluster nodes, "
-"<literal>node1</literal> and <literal>node2</literal>. Normally, this would "
-"be an LVM Logical Volume specifically set aside for this purpose. The DRBD "
-"<literal>meta-disk</literal> is <literal>internal</literal>, meaning DRBD-"
-"specific metadata is being stored at the end of the <literal>disk</literal> "
-"device itself. The device is configured to communicate between IPv4 "
-"addresses 10.0.42.100 and 10.0.42.254, using TCP port 7701. Once enabled, it"
-" will map to a local DRBD block device with the device minor number 1, that "
-"is, <literal>/dev/drbd1</literal>."
-msgstr "このリソースは、両方のクラスターノード <literal>node1</literal> と <literal>node2</literal> において、<literal>/dev/data/rabbitmq</literal> という名前のバックエンドのローカルディスク (DRBD の用語で <emphasis>backing device</emphasis>) を使用します。通常、これはこの目的のために特別に設定された LVM 論理ボリュームでしょう。DRBD <literal>meta-disk</literal> は <literal>internal</literal> です。これは DRBD 固有のメタデータが <literal>disk</literal> デバイス自身の最後に保存されることを意味します。このデバイスは IPv4 アドレス 10.0.42.100 と 10.0.42.254 の間で TCP ポート 7701 を使用して通信するよう設定されます。一度有効化されると、デバイスマイナー番号 1 を持つローカル DRBD ブロックデバイス、つまり <literal>/dev/drbd1</literal> にマップされます。"
+"The monitor check is quite simple since it just establishes a TCP connection"
+" to the API port. Comparing to the Active / Passive mode using Corosync "
+"&amp; Resources Agents, we don’t check if the service is actually running). "
+"That’s why all OpenStack API should be monitored by another tool (i.e. "
+"Nagios) with the goal to detect failures in the Cloud Framework "
+"infrastructure."
+msgstr "API ポートへの TCP 接続を確立するだけのため、監視チェックは極めてシンプルです。Corosync とリソースエージェントを使用するアクティブ / パッシブモードと比べて、サービスが実際に動作しているかを確認しません。そのため、クラウドのフレームワーク環境における障害を検知するために、すべての OpenStack API は他のツール (例: Nagios) により監視すべきです。"
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml93(para)
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml41(title)
+msgid "Schedulers"
+msgstr "スケジューラー"
+
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml43(simpara)
 msgid ""
-"Initializes DRBD metadata and writes the initial set of metadata to "
-"<literal>/dev/data/rabbitmq</literal>. Must be completed on both nodes."
-msgstr "DRBD メタデータを初期化し、メタデータの初期セットを <literal>/dev/data/rabbitmq</literal> に書き込みます。両方のノードで完了する必要があります。"
+"OpenStack schedulers are used to determine how to dispatch compute, network "
+"and volume requests. The most common setup is to use RabbitMQ as messaging "
+"system already documented in this guide. Those services are connected to the"
+" messaging backend and can scale-out :"
+msgstr "OpenStack スケジューラーは、コンピュート、ネットワーク、ボリュームのリクエストをどのようにディスパッチするかを決めるために使用されます。最も一般的なセットアップ環境は、このガイドにドキュメント化されたメッセージングシステムとして RabbitMQ を使用することです。これらのサービスはメッセージングのバックエンドに接続され、スケールアウトできます。"
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml99(para)
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml48(simpara)
+msgid "nova-scheduler"
+msgstr "nova-scheduler"
+
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml53(simpara)
+msgid "nova-conductor"
+msgstr "nova-conductor"
+
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml58(simpara)
+msgid "cinder-scheduler"
+msgstr "cinder-scheduler"
+
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml63(simpara)
+msgid "neutron-server"
+msgstr "neutron-server"
+
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml68(simpara)
+msgid "ceilometer-collector"
+msgstr "ceilometer-collector"
+
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml73(simpara)
+msgid "heat-engine"
+msgstr "heat-engine"
+
+#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml78(simpara)
 msgid ""
-"Creates the <literal>/dev/drbd1</literal> device node, "
-"<emphasis>attaches</emphasis> the DRBD device to its backing store, and "
-"<emphasis>connects</emphasis> the DRBD node to its peer. Must be completed "
-"on both nodes."
-msgstr "<literal>/dev/drbd1</literal> デバイスノードを作成し、DRBD デバイスをそのバックエンドに<emphasis>接続</emphasis>し、DRBD ノードを同期先に<emphasis>接続</emphasis>します。両方のノードで完了する必要があります。"
+"Please refer to the RabbitMQ section for configure these services with "
+"multiple messaging servers."
+msgstr "これらのサービスを複数のメッセージングサービスを用いて設定する方法は、RabbitMQ のセクションを参照してください。"
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml120(title)
-msgid "Create a file system"
-msgstr "ファイルシステムの作成"
+#: ./doc/high-availability-guide/pacemaker/section_start_pacemaker.xml6(title)
+msgid "Start Pacemaker"
+msgstr "Pacemaker の開始"
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml122(simpara)
+#: ./doc/high-availability-guide/pacemaker/section_start_pacemaker.xml8(simpara)
 msgid ""
-"Once the DRBD resource is running and in the primary role (and potentially "
-"still in the process of running the initial device synchronization), you may"
-" proceed with creating the filesystem for RabbitMQ data. XFS is generally "
-"the recommended filesystem:"
-msgstr "DRBD リソースが実行中になり、プライマリロールになると (まだ初期デバイス同期が実行中かもしれません)、RabbitMQ データのファイルシステムの作成を進められます。XFS が一般的に推奨されるファイルシステムです。"
+"Once the Corosync services have been started, and you have established that "
+"the cluster is communicating properly, it is safe to start "
+"<literal>pacemakerd</literal>, the Pacemaker master control process:"
+msgstr "Corosync サービスが開始されると、クラスターが適切に通信するよう設定されます。<literal>pacemakerd</literal>, Pacemaker マスター制御プロセスを安全に開始されます:"
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml138(title)
-msgid "Prepare RabbitMQ for Pacemaker high availability"
-msgstr "Pacemaker 高可用性のための RabbitMQ の準備"
+#: ./doc/high-availability-guide/pacemaker/section_start_pacemaker.xml13(simpara)
+msgid "<literal>/etc/init.d/pacemaker start</literal> (LSB)"
+msgstr "<literal>/etc/init.d/pacemaker start</literal> (LSB)"
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml140(simpara)
+#: ./doc/high-availability-guide/pacemaker/section_start_pacemaker.xml17(simpara)
+msgid "<literal>service pacemaker start</literal> (LSB, alternate)"
+msgstr "<literal>service pacemaker start</literal> (LSB, 代替)"
+
+#: ./doc/high-availability-guide/pacemaker/section_start_pacemaker.xml21(simpara)
+msgid "<literal>start pacemaker</literal> (upstart)"
+msgstr "<literal>start pacemaker</literal> (upstart)"
+
+#: ./doc/high-availability-guide/pacemaker/section_start_pacemaker.xml25(simpara)
+msgid "<literal>systemctl start pacemaker</literal> (systemd)"
+msgstr "<literal>systemctl start pacemaker</literal> (systemd)"
+
+#: ./doc/high-availability-guide/pacemaker/section_start_pacemaker.xml29(simpara)
 msgid ""
-"In order for Pacemaker monitoring to function properly, you must ensure that"
-" RabbitMQ’s <literal>.erlang.cookie</literal> files are identical on all "
-"nodes, regardless of whether DRBD is mounted there or not. The simplest way "
-"of doing so is to take an existing <literal>.erlang.cookie</literal> from "
-"one of your nodes, copying it to the RabbitMQ data directory on the other "
-"node, and also copying it to the DRBD-backed filesystem."
-msgstr "Pacemaker の監視を正しく機能させるために、DRBD がマウントされているかどうかに関わらず、RabbitMQ の <literal>.erlang.cookie</literal> ファイルをすべてのノードで必ず同じにする必要があります。そうする最も簡単な方法は、どこかのノードから既存の <literal>.erlang.cookie</literal> を取得し、他のノードの RabbitMQ データディレクトリおよび DRBD のバックエンドファイルシステムにコピーすることです。"
+"Once Pacemaker services have started, Pacemaker will create a default empty "
+"cluster configuration with no resources. You may observe Pacemaker’s status "
+"with the <literal>crm_mon</literal> utility:"
+msgstr "Pacemaker サービスが開始されると、Pacemaker はリソースを持たない空の標準クラスター設定を作成します。<literal>crm_mon</literal> ユーティリティを用いて Pacemaker の状態を確認できます。"
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml153(title)
-msgid "Add RabbitMQ resources to Pacemaker"
-msgstr "RabbitMQ リソースの Pacemaker への追加"
+#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml6(title)
+msgid "Set up Corosync"
+msgstr "Corosync のセットアップ"
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml155(simpara)
+#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml8(simpara)
 msgid ""
-"You may now proceed with adding the Pacemaker configuration for RabbitMQ "
-"resources. Connect to the Pacemaker cluster with <literal>crm "
+"Besides installing the <literal>corosync</literal> package, you must also "
+"create a configuration file, stored in "
+"<literal>/etc/corosync/corosync.conf</literal>. Most distributions ship an "
+"example configuration file (<literal>corosync.conf.example</literal>) as "
+"part of the documentation bundled with the <literal>corosync</literal> "
+"package. An example Corosync configuration file is shown below:"
+msgstr "<literal>corosync</literal> パッケージのインストールに関連して、<literal>/etc/corosync/corosync.conf</literal> に保存する、設定ファイルを作成する必要があります。多くのディストリビューションは、<literal>corosync</literal> パッケージに同梱されているドキュメントの一部として、サンプル設定ファイル (<literal>corosync.conf.example</literal>) が同梱されています。サンプルの Corosync 設定ファイルを以下に示します:"
+
+#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml16(title)
+msgid "Corosync configuration file (<literal>corosync.conf</literal>)"
+msgstr "Corosync 設定ファイル (<literal>corosync.conf</literal>)"
+
+#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml90(para)
+msgid ""
+"The <literal>token</literal> value specifies the time, in milliseconds, "
+"during which the Corosync token is expected to be transmitted around the "
+"ring. When this timeout expires, the token is declared lost, and after "
+"<literal>token_retransmits_before_loss_const</literal> lost tokens the non-"
+"responding <emphasis>processor</emphasis> (cluster node) is declared dead. "
+"In other words, <literal>token</literal> × "
+"<literal>token_retransmits_before_loss_const</literal> is the maximum time a"
+" node is allowed to not respond to cluster messages before being considered "
+"dead. The default for <literal>token</literal> is 1000 (1 second), with 4 "
+"allowed retransmits. These defaults are intended to minimize failover times,"
+" but can cause frequent \"false alarms\" and unintended failovers in case of"
+" short network interruptions. The values used here are safer, albeit with "
+"slightly extended failover times."
+msgstr "<literal>token</literal> の値は、Corosync トークンがリングを 1 周するまでの時間をミリ秒単位で指定します。このタイムアウトを経過した場合、トークンが消失したと判定します。<literal>token_retransmits_before_loss_const</literal> はトークンを失った後、応答のない <emphasis>processor</emphasis> (クラスターノード) が障害と判定されます。言い換えると、<literal>token</literal> × <literal>token_retransmits_before_loss_const</literal> が、ノードが障害と判定されるまでに、クラスターメッセージに応答しなくてもよい最大時間です。 <literal>token</literal> の規定値は 1000 (1 秒) で、再送 が 4 回まで許可されます。これらの規定値は、フェイルオーバー時間を最小化する狙いですが、頻繁に「誤報」を起こし、短時間のネットワーク障害により意図せずフェイルオーバーする可能性があります。ここで使用されている値は、フェイルオーバー時間をわずかに延ばしたとしても、より安全なものです。"
+
+#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml106(para)
+msgid ""
+"With <literal>secauth</literal> enabled, Corosync nodes mutually "
+"authenticate using a 128-byte shared secret stored in "
+"<literal>/etc/corosync/authkey</literal>, which may be generated with the "
+"<literal>corosync-keygen</literal> utility. When using "
+"<literal>secauth</literal>, cluster communications are also encrypted."
+msgstr "<literal>secauth</literal> を有効化している場合、Corosync ノードは <literal>/etc/corosync/authkey</literal> に保存されている 128 ビットの共有シークレットを使用して相互に認証します。このシークレットは <literal>corosync-keygen</literal> ユーティリティを用いて生成できます。<literal>secauth</literal> を使用するとき、クラスター通信も暗号化されます。"
+
+#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml114(para)
+msgid ""
+"In Corosync configurations using redundant networking (with more than one "
+"<literal>interface</literal>), you must select a Redundant Ring Protocol "
+"(RRP) mode other than <literal>none</literal>. <literal>active</literal> is "
+"the recommended RRP mode."
+msgstr "冗長ネットワーク (複数の <literal>interface</literal>) を使用した Corosync 設定の場合、Redundant Ring Protocol (RRP) モードを <literal>none</literal> 以外で選択する必要があります。<literal>active</literal> が推奨 RRP モードです。"
+
+#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml121(para)
+msgid ""
+"There are several things to note about the recommended interface "
+"configuration:"
+msgstr "インターフェースの推奨設定に関する注意事項がいくつかあります。"
+
+#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml127(simpara)
+msgid ""
+"The <literal>ringnumber</literal> must differ between all configured "
+"interfaces, starting with 0."
+msgstr "<literal>ringnumber</literal> はすべての設定済みインターフェースで異なる必要があります。0 から始まります。"
+
+#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml133(simpara)
+msgid ""
+"The <literal>bindnetaddr</literal> is the <emphasis>network</emphasis> "
+"address of the interfaces to bind to. The example uses two network addresses"
+" of <literal>/24</literal> IPv4 subnets."
+msgstr "<literal>bindnetaddr</literal> はバインドするインターフェースの<emphasis>ネットワーク</emphasis>アドレスです。この例は二つの <literal>/24</literal> IPv4 サブネットのネットワークアドレスを使用します。"
+
+#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml139(simpara)
+msgid ""
+"Multicast groups (<literal>mcastaddr</literal>) <emphasis>must "
+"not</emphasis> be reused across cluster boundaries. In other words, no two "
+"distinct clusters should ever use the same multicast group. Be sure to "
+"select multicast addresses compliant with <link "
+"href=\"http://www.ietf.org/rfc/rfc2365.txt\">RFC 2365, \"Administratively "
+"Scoped IP Multicast\"</link>."
+msgstr "マルチキャストグループ (<literal>mcastaddr</literal>) は、クラスターの境界をまたがって再利用できません。違い言い方をすると、2 つの別のクラスターは同じマルチキャストグループを使用できません。<link href=\"http://www.ietf.org/rfc/rfc2365.txt\">RFC 2365, \"Administratively Scoped IP Multicast\"</link> に適合しているマルチキャストアドレスを必ず選択してください。"
+
+#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml148(simpara)
+msgid ""
+"For firewall configurations, note that Corosync communicates over UDP only, "
+"and uses <literal>mcastport</literal> (for receives) and "
+"<literal>mcastport</literal>-1 (for sends)."
+msgstr "ファイアウォール設定に関して、Corosync は UDP のみを使用して通信し、<literal>mcastport</literal> (受信用) と <literal>mcastport</literal>-1 (送信用) を使用することに注意してください。"
+
+#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml157(para)
+msgid ""
+"The <literal>service</literal> declaration for the "
+"<literal>pacemaker</literal> service may be placed in the "
+"<literal>corosync.conf</literal> file directly, or in its own separate file,"
+" <literal>/etc/corosync/service.d/pacemaker</literal>."
+msgstr "<literal>pacemaker</literal> サービスに関する <literal>service</literal> 宣言は、<literal>corosync.conf</literal> ファイルに直接置かれるか、別のファイル <literal>/etc/corosync/service.d/pacemaker</literal> に置かれるかもしれません。"
+
+#: ./doc/high-availability-guide/pacemaker/section_set_up_corosync.xml164(simpara)
+msgid ""
+"Once created, the <literal>corosync.conf</literal> file (and the "
+"<literal>authkey</literal> file if the <literal>secauth</literal> option is "
+"enabled) must be synchronized across all cluster nodes."
+msgstr "一度作成すると、<literal>corosync.conf</literal> ファイル (および、<literal>secauth</literal> オプションが有効化されている場合は <literal>authkey</literal> ファイル) はすべてのクラスターノードで同期する必要があります。"
+
+#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml6(title)
+msgid "Install packages"
+msgstr "パッケージのインストール"
+
+#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml8(simpara)
+msgid ""
+"On any host that is meant to be part of a Pacemaker cluster, you must first "
+"establish cluster communications through the Corosync messaging layer. This "
+"involves Install the following packages (and their dependencies, which your "
+"package manager will normally install automatically):"
+msgstr "Pacemaker クラスターに参加させるすべてのホストにおいて、まず Corosync メッセージング層によるクラスター通信を確立する必要があります。これは、以下のパッケージをインストールする必要があります (また通常、パッケージ管理ソフトウェアが自動的にそれらに依存するものをインストールします)。"
+
+#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml15(simpara)
+msgid ""
+"<literal>pacemaker</literal> Note that the crm shell should be downloaded "
+"separately."
+msgstr "<literal>pacemaker</literal> は crm シェルを別途ダウンロードする必要があることに注意してください。"
+
+#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml20(literal)
+msgid "crmsh"
+msgstr "crmsh"
+
+#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml25(literal)
+msgid "corosync"
+msgstr "corosync"
+
+#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml30(literal)
+msgid "cluster-glue"
+msgstr "cluster-glue"
+
+#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml34(simpara)
+msgid ""
+"<literal>fence-agents</literal> (Fedora only; all other distributions use "
+"fencing agents from <literal>cluster-glue</literal>)"
+msgstr "<literal>fence-agents</literal> (Fedora のみ、他のすべてのディストリビューションは <literal>cluster-glue</literal> からフェンシング・エージェントを使用します)"
+
+#: ./doc/high-availability-guide/pacemaker/section_install_packages.xml40(literal)
+msgid "resource-agents"
+msgstr "resource-agents"
+
+#: ./doc/high-availability-guide/pacemaker/section_set_basic_cluster_properties.xml6(title)
+msgid "Set basic cluster properties"
+msgstr "基本的なクラスターのプロパティの設定"
+
+#: ./doc/high-availability-guide/pacemaker/section_set_basic_cluster_properties.xml8(simpara)
+msgid ""
+"Once your Pacemaker cluster is set up, it is recommended to set a few basic "
+"cluster properties. To do so, start the <literal>crm</literal> shell and "
+"change into the configuration menu by entering <literal>configure</literal>."
+" Alternatively. you may jump straight into the Pacemaker configuration menu "
+"by typing <literal>crm configure</literal> directly from a shell prompt."
+msgstr "Pacemaker クラスターを構築すると、いくつかの基本的なクラスタープロパティを設定することを推奨します。そうするために、<literal>crm</literal> シェルを開始し、<literal>configure</literal> と入力して設定メニューに変更します。代わりに、シェルプロンプトから直接 <literal>crm configure</literal> と入力して、Pacemaker 設定メニューに入ることもできます。"
+
+#: ./doc/high-availability-guide/pacemaker/section_set_basic_cluster_properties.xml14(simpara)
+msgid "Then, set the following properties:"
+msgstr "そして、以下のプロパティを設定します。"
+
+#: ./doc/high-availability-guide/pacemaker/section_set_basic_cluster_properties.xml22(para)
+msgid ""
+"Setting <literal>no-quorum-policy=\"ignore\"</literal> is required in 2-node"
+" Pacemaker clusters for the following reason: if quorum enforcement is "
+"enabled, and one of the two nodes fails, then the remaining node can not "
+"establish a <emphasis>majority</emphasis> of quorum votes necessary to run "
+"services, and thus it is unable to take over any resources. The appropriate "
+"workaround is to ignore loss of quorum in the cluster. This is safe and "
+"necessary <emphasis>only</emphasis> in 2-node clusters. Do not set this "
+"property in Pacemaker clusters with more than two nodes."
+msgstr "2 ノード Pacemaker クラスターの場合、以下の理由により <literal>no-quorum-policy=\"ignore\"</literal> の設定が必要になります。クォーラム強制が有効化されていると、2 ノードのどちらかに障害が発生した場合、残りのノードがサービスの実行に必要なクォーラムの<emphasis>過半数</emphasis>を獲得できなくなります。そのため、あらゆるリソースがテイクオーバーできません。適切な回避策は、クラスターでクォーラムの損失を無視することです。これは 2 ノードクラスター<emphasis>のみ</emphasis>で安全であり、必要になります。2 ノードより多い Pacemaker クラスターでは、このプロパティを設定してはいけません。"
+
+#: ./doc/high-availability-guide/pacemaker/section_set_basic_cluster_properties.xml34(para)
+msgid ""
+"Setting <literal>pe-warn-series-max</literal>, <literal>pe-input-series-"
+"max</literal> and <literal>pe-error-series-max</literal> to 1000 instructs "
+"Pacemaker to keep a longer history of the inputs processed, and errors and "
+"warnings generated, by its Policy Engine. This history is typically useful "
+"in case cluster troubleshooting becomes necessary."
+msgstr "<literal>pe-warn-series-max</literal>、<literal>pe-input-series-max</literal> および <literal>pe-error-series-max</literal> を 1000 に設定することにより、Pacemaker のポリシーエンジンにより、処理された入力、生成されたエラーと警告の履歴をより長く保持するよう Pacemaker に指示します。この履歴は一般的にクラスターのトラブルシューティングが必要となる場合に役に立ちます。"
+
+#: ./doc/high-availability-guide/pacemaker/section_set_basic_cluster_properties.xml43(para)
+msgid ""
+"Pacemaker uses an event-driven approach to cluster state processing. "
+"However, certain Pacemaker actions occur at a configurable interval, "
+"<literal>cluster-recheck-interval</literal>, which defaults to 15 minutes. "
+"It is usually prudent to reduce this to a shorter interval, such as 5 or 3 "
+"minutes."
+msgstr "Pacemaker はクラスター状態の処理にイベント駆動の方法を使用します。しかしながら、特定の Pacemaker アクションは、設定可能な間隔 <literal>cluster-recheck-interval</literal> で発生します。このデフォルトは 15 分です。一般的に 5 分や 3 分のようにより短い間隔にこれを慎重に減らします。"
+
+#: ./doc/high-availability-guide/pacemaker/section_set_basic_cluster_properties.xml52(simpara)
+msgid ""
+"Once you have made these changes, you may <literal>commit</literal> the "
+"updated configuration."
+msgstr "これらの変更を実行すると、更新した設定を <literal>commit</literal> できます。"
+
+#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml6(title)
+msgid "Starting Corosync"
+msgstr "Corosync の開始"
+
+#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml8(simpara)
+msgid ""
+"Corosync is started as a regular system service. Depending on your "
+"distribution, it may ship with a LSB (System V style) init script, an "
+"upstart job, or a systemd unit file. Either way, the service is usually "
+"named <literal>corosync</literal>:"
+msgstr "Corosync は通常のシステムサービスとして開始されます。お使いのディストリビューションにより、LSB (System V 形式) init スクリプト、upstart ジョブ、または systemd ユニットファイルが同梱されています。どの方法においても、サービスは通常 <literal>corosync</literal> という名前です:"
+
+#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml14(simpara)
+msgid "<literal>/etc/init.d/corosync start</literal> (LSB)"
+msgstr "<literal>/etc/init.d/corosync start</literal> (LSB)"
+
+#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml18(simpara)
+msgid "<literal>service corosync start</literal> (LSB, alternate)"
+msgstr "<literal>service corosync start</literal> (LSB, 代替)"
+
+#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml22(simpara)
+msgid "<literal>start corosync</literal> (upstart)"
+msgstr "<literal>start corosync</literal> (upstart)"
+
+#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml26(simpara)
+msgid "<literal>systemctl start corosync</literal> (systemd)"
+msgstr "<literal>systemctl start corosync</literal> (systemd)"
+
+#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml30(simpara)
+msgid "You can now check the Corosync connectivity with two tools."
+msgstr "2 つのツールを用いて Corosync 接続性を確認できます。"
+
+#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml31(simpara)
+msgid ""
+"The <literal>corosync-cfgtool</literal> utility, when invoked with the "
+"<literal>-s</literal> option, gives a summary of the health of the "
+"communication rings:"
+msgstr "<literal>corosync-cfgtool</literal> ユーティリティは、<literal>-s</literal> オプションを用いるとき、通信リングの健全性の概要を表示します:"
+
+#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml42(simpara)
+msgid ""
+"The <literal>corosync-objctl</literal> utility can be used to dump the "
+"Corosync cluster member list:"
+msgstr "<literal>corosync-objctl</literal> ユーティリティは Corosync クラスターのメンバー一覧をダンプするために使用できます:"
+
+#: ./doc/high-availability-guide/pacemaker/section_starting_corosync.xml51(simpara)
+msgid ""
+"You should see a <literal>status=joined</literal> entry for each of your "
+"constituent cluster nodes."
+msgstr "組み込まれているそれぞれのクラスターノードの項目が <literal>status=joined</literal> になっていることが確認できるはずです。"
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml6(title)
+msgid "Configure OpenStack services to use RabbitMQ"
+msgstr "RabbitMQ を使用するための OpenStack サービスの設定"
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml8(simpara)
+msgid ""
+"We have to configure the OpenStack components to use at least two RabbitMQ "
+"nodes."
+msgstr "2 つ以上の RabbitMQ ノードを使用するよう、OpenStack のコンポーネントを設定する必要があります。"
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml9(simpara)
+msgid "Do this configuration on all services using RabbitMQ:"
+msgstr "RabbitMQ を使用するすべてのサービスでこの設定を行います。"
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml10(simpara)
+msgid "RabbitMQ HA cluster host:port pairs:"
+msgstr "RabbitMQ HA クラスターの host:port の組:"
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml12(simpara)
+msgid "How frequently to retry connecting with RabbitMQ:"
+msgstr "RabbitMQ と再接続する頻度:"
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml14(simpara)
+msgid "How long to back-off for between retries when connecting to RabbitMQ:"
+msgstr "RabbitMQ に接続するとき再試行するまでにバックオフする間隔:"
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml16(simpara)
+msgid ""
+"Maximum retries with trying to connect to RabbitMQ (infinite by default):"
+msgstr "RabbitMQ に接続を試行する最大回数 (デフォルトで無制限):"
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml18(simpara)
+msgid "Use durable queues in RabbitMQ:"
+msgstr "RabbitMQ での永続キューの使用:"
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml20(simpara)
+msgid "Use H/A queues in RabbitMQ (x-ha-policy: all):"
+msgstr "RabbitMQ での H/A キューの使用 (x-ha-policy: all):"
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml22(simpara)
+msgid ""
+"If you change the configuration from an old setup which did not use HA "
+"queues, you should interrupt the service:"
+msgstr "HA キューを使用していない古いセットアップから設定を変更した場合、サービスを中断しなければいけません。"
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_openstack_services_to_user_rabbitmq.xml26(simpara)
+msgid ""
+"Services currently working with HA queues: OpenStack Compute, OpenStack "
+"Block Storage, OpenStack Networking, Telemetry."
+msgstr "次のサービスはいま HA キューで動作しています。OpenStack Compute、OpenStack Cinder、OpenStack Networking、Telemetry。"
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml8(simpara)
+msgid "This setup has been tested with RabbitMQ 2.7.1."
+msgstr "このセットアップは RabbitMQ 2.7.1 を用いてテストしました。"
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml11(title)
+msgid "On Ubuntu / Debian"
+msgstr "Ubuntu / Debian の場合"
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml13(simpara)
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml23(simpara)
+msgid "RabbitMQ is packaged on both distros:"
+msgstr "RabbitMQ がどちらもパッケージ化されています。"
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml16(link)
+msgid "Official manual for installing RabbitMQ on Ubuntu / Debian"
+msgstr "Ubuntu / Debian に RabbitMQ をインストールする方法の公式マニュアル"
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml21(title)
+msgid "On Fedora / RHEL"
+msgstr "Fedora / RHEL の場合"
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_install_rabbitmq.xml26(link)
+msgid "Official manual for installing RabbitMQ on Fedora / RHEL"
+msgstr "Fedora / RHEL に RabbitMQ をインストールする方法の公式マニュアル"
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml6(title)
+msgid "Configure RabbitMQ"
+msgstr "RabbitMQ の設定"
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml8(simpara)
+msgid ""
+"Here we are building a cluster of RabbitMQ nodes to construct a RabbitMQ "
+"broker. Mirrored queues in RabbitMQ improve the availability of service "
+"since it will be resilient to failures. We have to consider that while "
+"exchanges and bindings will survive the loss of individual nodes, queues and"
+" their messages will not because a queue and its contents is located on one "
+"node. If we lose this node, we also lose the queue."
+msgstr "これから RabbitMQ ブローカーを構築するために RabbitMQ ノードのクラスターを構築します。障害の耐性ができるため、RabbitMQ のキューミラーによりサービスの可用性を高められます。メッセージ交換とバインドにより個々のノードの損失があると、キューとその内容が 1 つのノードに置かれているため、キューとそれらのメッセージが無くなることに注意してください。このノードが失われた場合、キューも失われます。"
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml13(simpara)
+msgid ""
+"We consider that we run (at least) two RabbitMQ servers. To build a broker, "
+"we need to ensure that all nodes have the same erlang cookie file. To do so,"
+" stop RabbitMQ everywhere and copy the cookie from rabbit1 server to other "
+"server(s):"
+msgstr "(少なくとも) 2 つの RabbitMQ サーバーを実行することを考えます。ブローカーを構築するために、すべてのノードが必ず同じ erlang クッキーファイルを持つ必要があります。そうするために、すべての RabbitMQ を停止し、クッキーを rabbit1 サーバーから他のサーバーにコピーします。"
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml18(simpara)
+msgid ""
+"Then, start RabbitMQ on nodes. If RabbitMQ fails to start, you can’t "
+"continue to the next step."
+msgstr "そして、ノードで RabbitMQ を起動します。RabbitMQ の起動に失敗した場合、次の手順に進めません。"
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml20(simpara)
+msgid "Now, we are building the HA cluster. From rabbit2, run these commands:"
+msgstr "これで、HA クラスターの構築ができました。rabbit2 からこれらのコマンドを実行します。"
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml24(simpara)
+msgid "To verify the cluster status :"
+msgstr "クラスターの状態を確認する方法:"
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml29(simpara)
+msgid ""
+"If the cluster is working, you can now proceed to creating users and "
+"passwords for queues."
+msgstr "クラスターが動作していれば、キュー用のユーザーとパスワードを作成する手順に進めます。"
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml31(emphasis)
+msgid "Note for RabbitMQ version 3"
+msgstr "RabbitMQ バージョン 3 の注意事項"
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml33(simpara)
+msgid ""
+"Queue mirroring is no longer controlled by the <emphasis>x-ha-"
+"policy</emphasis> argument when declaring a queue. OpenStack can continue to"
+" declare this argument, but it won’t cause queues to be mirrored. We need to"
+" make sure that all queues (except those with auto-generated names) are "
+"mirrored across all running nodes:"
+msgstr "キューの宣言時、キューミラーが <emphasis>x-ha-policy</emphasis> 引数により制御されなくなりました。OpenStack がこの引数を宣言し続けますが、キューはミラーされません。すべてのキュー (自動生成された名前を除いて) が実行中の全ノードにわたり確実にミラーされる必要があります。"
+
+#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml38(link)
+msgid "More information about High availability in RabbitMQ"
+msgstr "RabbitMQ の高可用性に関する詳細"
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml6(title)
+msgid "Highly available neutron metadata agent"
+msgstr "高可用性 Neutron Metadata Agent"
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml8(simpara)
+msgid ""
+"Neutron metadata agent allows Compute API metadata to be reachable by VMs on"
+" tenant networks. High availability for the metadata agent is achieved by "
+"adopting Pacemaker."
+msgstr "Neutron Metadata エージェントにより Nova API Metadata がプロジェクトのネットワークにある仮想マシンによりアクセスできるようになります。Metadata エージェントの高可用性は Pacemaker の適用により実現されます。"
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml12(simpara)
+msgid ""
+"Here is the <link href=\"http://docs.openstack.org/trunk/config-"
+"reference/content/networking-options-metadata.html\">documentation</link> "
+"for installing Neutron Metadata Agent."
+msgstr "ここに Neutron Metadata エージェントをインストールするための<link href=\"http://docs.openstack.org/trunk/config-reference/content/networking-options-metadata.html\">ドキュメント</link>があります。"
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml16(title)
+msgid "Add neutron metadata agent resource to Pacemaker"
+msgstr "Neutron Metadata Agent リソースの Pacemaker への追加"
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml22(simpara)
+msgid ""
+"You may now proceed with adding the Pacemaker configuration for neutron "
+"metadata agent resource. Connect to the Pacemaker cluster with <literal>crm "
 "configure</literal>, and add the following cluster resources:"
-msgstr "OpenStack RabbitMQ リソース用の Pacemaker 設定を追加して、次に進むことができます。<literal>crm configure</literal> を用いて Pacemaker クラスターに接続し、以下のクラスターリソースを追加します。"
+msgstr "OpenStack Metadata Agent リソース用の Pacemaker 設定を追加して、次に進むことができます。<literal>crm configure</literal> を用いて Pacemaker クラスターに接続し、以下のクラスターリソースを追加します。"
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml188(simpara)
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml32(simpara)
 msgid ""
-"<literal>p_ip_rabbitmp</literal>, a virtual IP address for use by RabbitMQ "
-"(192.168.42.100),"
-msgstr "<literal>p_ip_rabbitmp</literal>, RabbitMQ により使用される仮想 IP アドレス (192.168.42.100),"
+"<literal>p_neutron-metadata-agent</literal>, a resource for manage Neutron "
+"Metadata Agent service"
+msgstr "<literal>p_neutron-metadata-agent</literal>, Neutron Metadata Agent サービスを管理するためのリソース。"
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml193(simpara)
-msgid ""
-"<literal>p_fs_rabbitmq</literal>, a Pacemaker managed filesystem mounted to "
-"<literal>/var/lib/rabbitmq</literal> on whatever node currently runs the "
-"RabbitMQ service,"
-msgstr "<literal>p_fs_rabbitmq</literal>, 現在 RabbitMQ サービスを実行している、すべてのノードにおいて <literal>/var/lib/rabbitmq</literal> にマウントされている、Pacemaker が管理しているファイルシステム。"
-
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml199(simpara)
-msgid ""
-"<literal>ms_drbd_rabbitmq</literal>, the <emphasis>master/slave "
-"set</emphasis> managing the <literal>rabbitmq</literal> DRBD resource,"
-msgstr "<literal>ms_drbd_rabbitmq</literal>, <literal>rabbitmq</literal> DRBD リソースを管理している<emphasis>マスター/スレーブの組</emphasis>。"
-
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml210(simpara)
-msgid ""
-"<literal>crm configure</literal> supports batch input, so you may copy and "
-"paste the above into your live pacemaker configuration, and then make "
-"changes as required. For example, you may enter <literal>edit "
-"p_ip_rabbitmq</literal> from the <literal>crm configure</literal> menu and "
-"edit the resource to match your preferred virtual IP address."
-msgstr "<literal>crm configure</literal> はバッチ入力をサポートします。そのため、現在の pacemaker 設定の中に上をコピー・ペーストし、適宜変更を反映できます。たとえば、お好みの仮想 IP アドレスに一致させるために、<literal>crm configure</literal> メニューから <literal>edit p_ip_rabbitmq</literal> と入力し、リソースを編集できます。"
-
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml215(simpara)
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_metadata_agent.xml40(simpara)
 msgid ""
 "Once completed, commit your configuration changes by entering "
 "<literal>commit</literal> from the <literal>crm configure</literal> menu. "
-"Pacemaker will then start the RabbitMQ service, and its dependent resources,"
-" on one of your nodes."
-msgstr "完了すると、<literal>crm configure</literal> メニューから <literal>commit</literal> と入力し、設定の変更をコミットします。Pacemaker は RabbitMQ サービスおよび依存するリソースを同じノードに起動します。"
+"Pacemaker will then start the neutron metadata agent service, and its "
+"dependent resources, on one of your nodes."
+msgstr "完了すると、<literal>crm configure</literal> メニューから <literal>commit</literal> と入力し、設定の変更をコミットします。Pacemaker は Neutron Metadata Agent サービスおよび依存するリソースを同じノードに起動します。"
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml221(title)
-msgid "Configure OpenStack services for highly available RabbitMQ"
-msgstr "高可用性 RabbitMQ のための OpenStack サービスの設定"
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml6(title)
+msgid "Highly available neutron L3 agent"
+msgstr "高可用性 Neutron L3 エージェント"
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml223(simpara)
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml8(simpara)
 msgid ""
-"Your OpenStack services must now point their RabbitMQ configuration to the "
-"highly available, virtual cluster IP address — rather than a RabbitMQ "
-"server’s physical IP address as you normally would."
-msgstr "OpenStack サービスは、通常どおり RabbitMQ サーバーの物理 IP アドレスを指定する代わりに、RabbitMQ の設定が高可用性と仮想クラスター IP アドレスを指し示す必要があります。"
+"The neutron L3 agent provides L3/NAT forwarding to ensure external network "
+"access for VMs on tenant networks. High availability for the L3 agent is "
+"achieved by adopting Pacemaker."
+msgstr "Neutron L3 エージェントは、プロジェクトのネットワークにある仮想マシンが確実に外部ネットワークにアクセスできるように、L3/NAT 転送機能を提供します。"
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml226(simpara)
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml12(simpara)
 msgid ""
-"For OpenStack Image, for example, if your RabbitMQ service IP address is "
-"192.168.42.100 as in the configuration explained here, you would use the "
-"following line in your OpenStack Image API configuration file (<literal"
-">glance-api.conf</literal>):"
-msgstr "OpenStack Image の例として、RabbitMQ サーバーの IP アドレスがここで説明された設定にあるように 192.168.42.100 ならば、OpenStack Image API 定ファイル (<literal>glance-api.conf</literal>) で以下の行を使用する必要があります。"
+"Here is the <link href=\"http://docs.openstack.org/trunk/config-"
+"reference/content/section_adv_cfg_l3_agent.html\">documentation</link> for "
+"installing neutron L3 agent."
+msgstr "ここに Neutron L3 エージェントをインストールするための<link href=\"http://docs.openstack.org/trunk/config-reference/content/section_adv_cfg_l3_agent.html\">ドキュメント</link>があります。"
 
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml231(simpara)
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml16(title)
+msgid "Add neutron L3 agent resource to Pacemaker"
+msgstr "Neutron L3 Agent リソースの Pacemaker への追加"
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml22(simpara)
 msgid ""
-"No other changes are necessary to your OpenStack configuration. If the node "
-"currently hosting your RabbitMQ experiences a problem necessitating service "
-"failover, your OpenStack services may experience a brief RabbitMQ "
-"interruption, as they would in the event of a network hiccup, and then "
-"continue to run normally."
-msgstr "OpenStack の設定に他の変更は必要ありません。現在 RabbitMQ を稼働しているノードが、サービスのフェイルオーバーを必要とする問題に遭遇した場合、ネットワークの中断と通常どおりの動作継続により、OpenStack のサービスは MySQL の短時間の中断に遭遇するかもしれません。"
+"You may now proceed with adding the Pacemaker configuration for neutron L3 "
+"agent resource. Connect to the Pacemaker cluster with <literal>crm "
+"configure</literal>, and add the following cluster resources:"
+msgstr "Neutron L3 Agent リソース用の Pacemaker 設定を追加して、次に進むことができます。<literal>crm configure</literal> を用いて Pacemaker クラスターに接続し、以下のクラスターリソースを追加します。"
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml32(simpara)
+msgid ""
+"<literal>p_neutron-l3-agent</literal>, a resource for manage Neutron L3 "
+"Agent service"
+msgstr "<literal>p_neutron-l3-agent</literal>, Neutron L3 Agent サービスを管理するためのリソース。"
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml39(simpara)
+msgid ""
+"Once completed, commit your configuration changes by entering "
+"<literal>commit</literal> from the <literal>crm configure</literal> menu. "
+"Pacemaker will then start the neutron L3 agent service, and its dependent "
+"resources, on one of your nodes."
+msgstr "完了すると、<literal>crm configure</literal> メニューから <literal>commit</literal> と入力し、設定の変更をコミットします。Pacemaker は Neutron L3 Agent サービスおよび依存するリソースを同じノードに起動します。"
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_l3_agent.xml43(simpara)
+msgid ""
+"This method does not ensure a zero downtime since it has to recreate all the"
+" namespaces and virtual routers on the node."
+msgstr "この方法は、ノードですべての名前空間と仮想ルーターを再作成する必要があるため、無停止を保証しません。"
+
+#: ./doc/high-availability-guide/network/section_manage_network_resources.xml6(title)
+msgid "Manage network resources"
+msgstr "ネットワークリソースの管理"
+
+#: ./doc/high-availability-guide/network/section_manage_network_resources.xml8(simpara)
+msgid ""
+"You can now add the Pacemaker configuration for managing all network "
+"resources together with a group. Connect to the Pacemaker cluster with "
+"<literal>crm configure</literal>, and add the following cluster resources:"
+msgstr "すべてのネットワークリソースをグループと一緒に管理するための Pacemaker 設定を追加できます。<literal>crm configure</literal> を用いて Pacemaker クラスターに接続し、以下のクラスターリソースを追加します。"
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml6(title)
+msgid "Highly available neutron DHCP agent"
+msgstr "高可用性 Neutron DHCP Agent"
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml8(simpara)
+msgid ""
+"Neutron DHCP agent distributes IP addresses to the VMs with dnsmasq (by "
+"default). High availability for the DHCP agent is achieved by adopting "
+"Pacemaker."
+msgstr "Neutron DHCP エージェントは (デフォルトで) dnsmasq を用いて仮想マシンに IP アドレスを配布します。DHCP エージェントの高可用性は Pacemaker の適用により実現されます。"
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml12(simpara)
+msgid ""
+"Here is the <link href=\"http://docs.openstack.org/trunk/config-"
+"reference/content/section_adv_cfg_dhcp_agent.html\">documentation</link> for"
+" installing neutron DHCP agent."
+msgstr "ここに Neutron DHCP エージェントをインストールするための<link href=\"http://docs.openstack.org/trunk/config-reference/content/section_adv_cfg_dhcp_agent.html\">ドキュメント</link>があります。"
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml16(title)
+msgid "Add neutron DHCP agent resource to Pacemaker"
+msgstr "Neutron DHCP Agent リソースの Pacemaker への追加"
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml22(simpara)
+msgid ""
+"You may now proceed with adding the Pacemaker configuration for neutron DHCP"
+" agent resource. Connect to the Pacemaker cluster with <literal>crm "
+"configure</literal>, and add the following cluster resources:"
+msgstr "OpenStack DHCP Agent リソース用の Pacemaker 設定を追加して、次に進むことができます。<literal>crm configure</literal> を用いて Pacemaker クラスターに接続し、以下のクラスターリソースを追加します。"
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml32(simpara)
+msgid ""
+"<literal>p_neutron-dhcp-agent</literal>, a resource for manage Neutron DHCP "
+"Agent service"
+msgstr "<literal>p_neutron-dhcp-agent</literal>, Neutron DHCP Agent サービスを管理するためのリソース。"
+
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml40(simpara)
+msgid ""
+"Once completed, commit your configuration changes by entering "
+"<literal>commit</literal> from the <literal>crm configure</literal> menu. "
+"Pacemaker will then start the neutron DHCP agent service, and its dependent "
+"resources, on one of your nodes."
+msgstr "完了すると、<literal>crm configure</literal> メニューから <literal>commit</literal> と入力し、設定の変更をコミットします。Pacemaker は Neutron DHCP Agent サービスおよび依存するリソースを同じノードに起動します。"
 
 #. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
-#: ./doc/high-availability-guide/controller/section_rabbitmq.xml0(None)
+#: ./doc/high-availability-guide/network/section_highly_available_neutron_dhcp_agent.xml0(None)
 msgid "translator-credits"
 msgstr "Tomoyuki KATO <tomo@dream.daynight.jp>, 2012-2014"
diff --git a/doc/image-guide/locale/image-guide.pot b/doc/image-guide/locale/image-guide.pot
index cc29de2bb1..c07b7207d2 100644
--- a/doc/image-guide/locale/image-guide.pot
+++ b/doc/image-guide/locale/image-guide.pot
@@ -1,7 +1,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2014-05-16 06:34+0000\n"
+"POT-Creation-Date: 2014-06-03 06:11+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -9,6 +9,134 @@ msgstr ""
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
+#: ./doc/image-guide/section_windows-example.xml:8(title)
+msgid "Example: Microsoft Windows image"
+msgstr ""
+
+#: ./doc/image-guide/section_windows-example.xml:9(para)
+msgid "We do not yet have a fully documented example of how to create a Microsoft Windows image. You can use libvirt to install Windows from an installation DVD using the same approach as with the CentOS and Ubuntu examples. Once the initial install is done, you will need to perform some Windows-specific customizations."
+msgstr ""
+
+#: ./doc/image-guide/section_windows-example.xml:14(title)
+msgid "Install VirtIO drivers"
+msgstr ""
+
+#: ./doc/image-guide/section_windows-example.xml:15(para)
+msgid "Installing the <link href=\"http://www.linux-kvm.org/page/WindowsGuestDrivers/Download_Drivers\">VirtIO paravirtualizaion drivers for Windows</link> will improve virtual machine performance when using KVM as the hypervisor to run Windows."
+msgstr ""
+
+#: ./doc/image-guide/section_windows-example.xml:20(title)
+msgid "Sysprep"
+msgstr ""
+
+#: ./doc/image-guide/section_windows-example.xml:21(para)
+msgid "Microsoft has a special tool called <link href=\"http://technet.microsoft.com/en-us/library/cc766049(v=ws.10).aspx\">Sysprep</link> that must be run inside of a Windows guest to prepare it for use as a virtual machine image. On Windows 2012 server, invoke sysprep, as follows: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/image-guide/section_windows-example.xml:28(title)
+msgid "cloudbase-init"
+msgstr ""
+
+#: ./doc/image-guide/section_windows-example.xml:29(para)
+msgid "<link href=\"http://www.cloudbase.it/cloud-init-for-windows-instances/\">cloudbase-init</link> is a Windows port of cloud-init that should be installed inside of the guest. The <link href=\"https://github.com/cloudbase/cloudbase-init\">source code</link> is available on github."
+msgstr ""
+
+#: ./doc/image-guide/section_windows-example.xml:35(title)
+msgid "Jordan Rinke's OpenStack Windows resources"
+msgstr ""
+
+#: ./doc/image-guide/section_windows-example.xml:36(para)
+msgid "Jordan Rinke maintains <link href=\"https://github.com/jordanrinke/openstack\">a collection of resources</link> for managing OpenStack Windows virtual machine guests."
+msgstr ""
+
+#: ./doc/image-guide/section_windows-example.xml:41(title)
+msgid "Windows instances require the timezone to be \"localtime\""
+msgstr ""
+
+#: ./doc/image-guide/section_windows-example.xml:42(para)
+msgid "When uploading Windows images, you must set the <literal>os_type</literal> parameter to <literal>windows</literal>, which causes instances to use the local time zone. Failing to set this will cause the clock timezone to be UTC, which has unexpected side effects in Windows."
+msgstr ""
+
+#: ./doc/image-guide/section_glance_image-formats.xml:6(title)
+msgid "Disk and container formats for images"
+msgstr ""
+
+#: ./doc/image-guide/section_glance_image-formats.xml:8(para)
+msgid "When you add an image to the Image Service, you can specify its disk and container formats."
+msgstr ""
+
+#: ./doc/image-guide/section_glance_image-formats.xml:11(title)
+msgid "Disk formats"
+msgstr ""
+
+#: ./doc/image-guide/section_glance_image-formats.xml:12(para)
+msgid "The disk format of a virtual machine image is the format of the underlying disk image. Virtual appliance vendors have different formats for laying out the information contained in a virtual machine disk image."
+msgstr ""
+
+#: ./doc/image-guide/section_glance_image-formats.xml:16(para)
+msgid "Set the disk format for your image to one of the following values:"
+msgstr ""
+
+#: ./doc/image-guide/section_glance_image-formats.xml:20(para)
+msgid "<literal>raw</literal>. An unstructured disk image format; if you have a file without an extension it is possibly a raw format"
+msgstr ""
+
+#: ./doc/image-guide/section_glance_image-formats.xml:25(para)
+msgid "<literal>vhd</literal>. The VHD disk format, a common disk format used by virtual machine monitors from VMWare, Xen, Microsoft, VirtualBox, and others"
+msgstr ""
+
+#: ./doc/image-guide/section_glance_image-formats.xml:31(para)
+msgid "<literal>vmdk</literal>. Common disk format supported by many common virtual machine monitors"
+msgstr ""
+
+#: ./doc/image-guide/section_glance_image-formats.xml:36(para)
+msgid "<literal>vdi</literal>. Supported by VirtualBox virtual machine monitor and the QEMU emulator"
+msgstr ""
+
+#: ./doc/image-guide/section_glance_image-formats.xml:41(para)
+msgid "<literal>iso</literal>. An archive format for the data contents of an optical disc, such as CD-ROM."
+msgstr ""
+
+#: ./doc/image-guide/section_glance_image-formats.xml:46(para)
+msgid "<literal>qcow2</literal>. Supported by the QEMU emulator that can expand dynamically and supports Copy on Write"
+msgstr ""
+
+#: ./doc/image-guide/section_glance_image-formats.xml:51(para) ./doc/image-guide/section_glance_image-formats.xml:87(para)
+msgid "<literal>aki</literal>. An Amazon kernel image."
+msgstr ""
+
+#: ./doc/image-guide/section_glance_image-formats.xml:55(para) ./doc/image-guide/section_glance_image-formats.xml:91(para)
+msgid "<literal>ari</literal>. An Amazon ramdisk image."
+msgstr ""
+
+#: ./doc/image-guide/section_glance_image-formats.xml:59(para) ./doc/image-guide/section_glance_image-formats.xml:95(para)
+msgid "<literal>ami</literal>. An Amazon machine image."
+msgstr ""
+
+#: ./doc/image-guide/section_glance_image-formats.xml:65(title)
+msgid "Container formats"
+msgstr ""
+
+#: ./doc/image-guide/section_glance_image-formats.xml:66(para)
+msgid "The container format indicates whether the virtual machine image is in a file format that also contains metadata about the actual virtual machine."
+msgstr ""
+
+#: ./doc/image-guide/section_glance_image-formats.xml:70(para)
+msgid "The Image Service and other OpenStack projects do not currently support the container format. It is safe to specify <literal>bare</literal> as the container format if you are unsure."
+msgstr ""
+
+#: ./doc/image-guide/section_glance_image-formats.xml:75(para)
+msgid "You can set the container format for your image to one of the following values:"
+msgstr ""
+
+#: ./doc/image-guide/section_glance_image-formats.xml:79(para)
+msgid "<literal>bare</literal>. The image does not have a container or metadata envelope."
+msgstr ""
+
+#: ./doc/image-guide/section_glance_image-formats.xml:83(para)
+msgid "<literal>ovf</literal>. The OVF container format."
+msgstr ""
+
 #: ./doc/image-guide/ch_modifying_images.xml:10(title)
 msgid "Modify images"
 msgstr ""
@@ -241,6 +369,254 @@ msgstr ""
 msgid "When you're done, clean up:<placeholder-1/>"
 msgstr ""
 
+#: ./doc/image-guide/section_freebsd-example.xml:8(title)
+msgid "Example: FreeBSD image"
+msgstr ""
+
+#: ./doc/image-guide/section_freebsd-example.xml:9(para)
+msgid "We do not yet have a fully documented example of how to create a FreeBSD image."
+msgstr ""
+
+#: ./doc/image-guide/section_freebsd-example.xml:11(para)
+msgid "See the <link href=\"http://pellaeon.github.io/bsd-cloudinit/\">bsd-cloudinit</link> project for information on how to build a FreeBSD VM image that works with OpenStack."
+msgstr ""
+
+#: ./doc/image-guide/ch_converting.xml:4(title)
+msgid "Converting between image formats"
+msgstr ""
+
+#: ./doc/image-guide/ch_converting.xml:5(para)
+msgid "Converting images from one format to another is generally straightforward."
+msgstr ""
+
+#: ./doc/image-guide/ch_converting.xml:7(title)
+msgid "qemu-img convert: raw, qcow2, VDI, VMDK"
+msgstr ""
+
+#: ./doc/image-guide/ch_converting.xml:8(para)
+msgid "The <placeholder-1/> command can do conversion between multiple formats, including raw, qcow2, VDI (VirtualBox), VMDK (VMWare) and VHD (Hyper-V)."
+msgstr ""
+
+#: ./doc/image-guide/ch_converting.xml:12(caption)
+msgid "qemu-img format strings"
+msgstr ""
+
+#: ./doc/image-guide/ch_converting.xml:16(th)
+msgid "Image format"
+msgstr ""
+
+#: ./doc/image-guide/ch_converting.xml:17(th)
+msgid "Argument to qemu-img"
+msgstr ""
+
+#: ./doc/image-guide/ch_converting.xml:22(td) ./doc/image-guide/ch_converting.xml:23(literal)
+msgid "raw"
+msgstr ""
+
+#: ./doc/image-guide/ch_converting.xml:26(td) ./doc/image-guide/ch_converting.xml:27(literal) ./doc/image-guide/ch_introduction.xml:32(term)
+msgid "qcow2"
+msgstr ""
+
+#: ./doc/image-guide/ch_converting.xml:30(td)
+msgid "VDI (VirtualBox)"
+msgstr ""
+
+#: ./doc/image-guide/ch_converting.xml:31(literal)
+msgid "vdi"
+msgstr ""
+
+#: ./doc/image-guide/ch_converting.xml:34(td)
+msgid "VMDK (VMWare)"
+msgstr ""
+
+#: ./doc/image-guide/ch_converting.xml:35(literal)
+msgid "vmdk"
+msgstr ""
+
+#: ./doc/image-guide/ch_converting.xml:38(td)
+msgid "VHD (Hyper-V)"
+msgstr ""
+
+#: ./doc/image-guide/ch_converting.xml:39(literal)
+msgid "vpc"
+msgstr ""
+
+#: ./doc/image-guide/ch_converting.xml:43(para)
+msgid "This example will convert a raw image file named centos63.dsk to a qcow2 image file."
+msgstr ""
+
+#: ./doc/image-guide/ch_converting.xml:47(para)
+msgid "To convert from vmdk to raw, you would do: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/image-guide/ch_converting.xml:51(para)
+msgid "The <literal>-f <replaceable>format</replaceable></literal> flag is optional. If omitted, qemu-img will try to infer the image format."
+msgstr ""
+
+#: ./doc/image-guide/ch_converting.xml:57(title)
+msgid "VBoxManage: VDI (VirtualBox) to raw"
+msgstr ""
+
+#: ./doc/image-guide/ch_converting.xml:58(para)
+msgid "If you've created a VDI image using VirtualBox, you can convert it to raw format using the <placeholder-1/> command-line tool that ships with VirtualBox. On Mac OS X, VirtualBox stores images by default in the <filename>~/VirtualBox VMs/</filename> directory. The following example creates a raw image in the current directory from a VirtualBox VDI image.<placeholder-2/>"
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:6(title)
+msgid "Introduction"
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:7(para)
+msgid "An OpenStack Compute cloud is not very useful unless you have virtual machine images (which some people call \"virtual appliances\"). This guide describes how to obtain, create, and modify virtual machine images that are compatible with OpenStack."
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:10(para)
+msgid "To keep things brief, we'll sometimes use the term \"image\" instead of \"virtual machine image\"."
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:12(para)
+msgid "What is a virtual machine image?"
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:13(para)
+msgid "A virtual machine image is a single file which contains a virtual disk that has a bootable operating system installed on it."
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:15(para)
+msgid "Virtual machine images come in different formats, some of which are described below. In a later chapter, we'll describe how to convert between formats."
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:19(term)
+msgid "Raw"
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:26(para)
+msgid "We don't recommend creating raw images by dd'ing block device files, we discuss how to create raw images later."
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:20(para)
+msgid "The \"raw\" image format is the simplest one, and is natively supported by both KVM and Xen hypervisors. You can think of a raw image as being the bit-equivalent of a block device file, created as if somebody had copied, say, <filename>/dev/sda</filename> to a file using the <placeholder-1/> command. <placeholder-2/>"
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:37(para)
+msgid "Using sparse representation, so the image size is smaller"
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:40(para)
+msgid "Support for snapshots"
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:33(para)
+msgid "The <link href=\"http://en.wikibooks.org/wiki/QEMU/Images\">qcow2</link> (QEMU copy-on-write version 2) format is commonly used with the KVM hypervisor. It has some additional features over the raw format, such as:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:43(para)
+msgid "Because qcow2 is sparse, it's often faster to convert a raw image to qcow2 and upload it then to upload the raw file."
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:47(para)
+msgid "Because raw images don't support snapshots, OpenStack Compute will automatically convert raw image files to qcow2 as needed."
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:53(term)
+msgid "AMI/AKI/ARI"
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:59(para)
+msgid "AMI (Amazon Machine Image):"
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:60(para)
+msgid "This is a virtual machine image in raw format, as described above."
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:64(para)
+msgid "AKI (Amazon Kernel Image)"
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:65(para)
+msgid "A kernel file that the hypervisor will load initially to boot the image. For a Linux machine, this would be a <emphasis>vmlinuz</emphasis> file."
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:72(para)
+msgid "ARI (Amazon Ramdisk Image)"
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:73(para)
+msgid "An optional ramdisk file mounted at boot time. For a Linux machine, this would be an <emphasis>initrd</emphasis> file."
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:54(para)
+msgid "The <link href=\"http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AMIs.html\">AMI/AKI/ARI </link>format was the initial image format supported by Amazon EC2. The image consists of three files:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:81(term)
+msgid "UEC tarball"
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:84(para)
+msgid "Ubuntu Enterprise Cloud refers to a discontinued Eucalyptus-based Ubuntu cloud solution that has been replaced by the OpenStack-based Ubuntu Cloud Infrastructure."
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:82(para)
+msgid "A UEC (Ubuntu Enterprise Cloud) tarball is a gzipped tarfile that contains an AMI file, AKI file, and ARI file.<placeholder-1/>"
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:90(term)
+msgid "VMDK"
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:91(para)
+msgid "VMWare's ESXi hypervisor uses the <link href=\"http://www.vmware.com/technical-resources/interfaces/vmdk.html\">VMDK</link> (Virtual Machine Disk) format for images."
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:96(term)
+msgid "VDI"
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:97(para)
+msgid "VirtualBox uses the <link href=\"https://forums.virtualbox.org/viewtopic.php?t=8046\">VDI</link> (Virtual Disk Image) format for image files. None of the OpenStack Compute hypervisors support VDI directly, so you will need to convert these files to a different format to use them with OpenStack."
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:104(term)
+msgid "VHD"
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:105(para)
+msgid "Microsoft Hyper-V uses the VHD (Virtual Hard Disk) format for images."
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:108(term)
+msgid "VHDX"
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:109(para)
+msgid "The version of Hyper-V that ships with Microsoft Server 2012 uses the newer <link href=\"http://technet.microsoft.com/en-us/library/hh831446.aspx\">VHDX</link> format, which has some additional features over VHD such as support for larger disk sizes and protection against data corruption during power failures."
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:115(term)
+msgid "OVF"
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:116(para)
+msgid "<link href=\"http://www.dmtf.org/standards/ovf\">OVF</link> (Open Virtualization Format) is a packaging format for virtual machines, defined by the Distributed Management Task Force (DMTF) standards group. An OVF package contains one or more image files, a .ovf XML metadata file that contains information about the virtual machine, and possibly other files as well."
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:121(para)
+msgid "An OVF package can be distributed in different ways. For example, it could be distributed as a set of discrete files, or as a tar archive file with an .ova (open virtual appliance/application) extension."
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:124(para)
+msgid "OpenStack Compute does not currently have support for OVF packages, so you will need to extract the image file(s) from an OVF package if you wish to use it with OpenStack."
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:129(term)
+msgid "ISO"
+msgstr ""
+
+#: ./doc/image-guide/ch_introduction.xml:130(para)
+msgid "The <link href=\"http://www.ecma-international.org/publications/standards/Ecma-119.htm\">ISO</link> format is a disk image formatted with the read-only ISO 9660 (also known as ECMA-119) filesystem commonly used for CDs and DVDs. While we don't normally think of ISO as a virtual machine image format, since ISOs contain bootable filesystems with an installed operating system, you can treat them the same as you treat other virtual machine image files."
+msgstr ""
+
 #. When image changes, this message will be marked fuzzy or untranslated for you.
 #. It doesn't matter what you translate it to: it's not used at all.
 #: ./doc/image-guide/section_centos-example.xml:80(None) ./doc/image-guide/section_centos-example.xml:84(None)
@@ -615,6 +991,214 @@ msgstr ""
 msgid "Initial release of this guide."
 msgstr ""
 
+#: ./doc/image-guide/ch_creating_images_automatically.xml:6(title)
+msgid "Tool support for image creation"
+msgstr ""
+
+#: ./doc/image-guide/ch_creating_images_automatically.xml:8(para)
+msgid "There are several tools that are designed to automate image creation."
+msgstr ""
+
+#: ./doc/image-guide/ch_creating_images_automatically.xml:11(title)
+msgid "Oz"
+msgstr ""
+
+#: ./doc/image-guide/ch_creating_images_automatically.xml:22(para)
+msgid "As of this writing, there are no Oz packages for Ubuntu, so you will need to either install from source or build your own .deb file."
+msgstr ""
+
+#: ./doc/image-guide/ch_creating_images_automatically.xml:12(para)
+msgid "<link href=\"https://github.com/clalancette/oz/wiki\">Oz</link> is a command-line tool that automates the process of creating a virtual machine image file. Oz is a Python app that interacts with KVM to step through the process of installing a virtual machine. It uses a predefined set of kickstart (Red Hat-based systems) and preseed files (Debian-based systems) for operating systems that it supports, and it can also be used to create Microsoft Windows images. On Fedora, install Oz with yum:<placeholder-1/><placeholder-2/>"
+msgstr ""
+
+#: ./doc/image-guide/ch_creating_images_automatically.xml:26(para)
+msgid "A full treatment of Oz is beyond the scope of this document, but we will provide an example. You can find additional examples of Oz template files on github at <link href=\"https://github.com/rackerjoe/oz-image-build/tree/master/templates\">rackerjoe/oz-image-build/templates</link>. Here's how you would create a CentOS 6.4 image with Oz."
+msgstr ""
+
+#: ./doc/image-guide/ch_creating_images_automatically.xml:33(para)
+msgid "Create a template file (we'll call it <filename>centos64.tdl</filename>) with the following contents. The only entry you will need to change is the <literal>&lt;rootpw&gt;</literal> contents.<placeholder-1/>"
+msgstr ""
+
+#: ./doc/image-guide/ch_creating_images_automatically.xml:71(para)
+msgid "This Oz template specifies where to download the Centos 6.4 install ISO. Oz will use the version information to identify which kickstart file to use. In this case, it will be <link href=\"https://github.com/clalancette/oz/blob/master/oz/auto/RHEL6.auto\">RHEL6.auto</link>. It adds EPEL as a repository and install the <literal>epel-release</literal>, <literal>cloud-utils</literal>, and <literal>cloud-init</literal> packages, as specified in the <literal>packages</literal> section of the file."
+msgstr ""
+
+#: ./doc/image-guide/ch_creating_images_automatically.xml:82(para)
+msgid "After Oz does the initial OS install using the kickstart file, it customizes the image by doing an update. It also removes any reference to the eth0 device that libvirt creates while Oz does the customizing, as specified in the <literal>command</literal> section of the XML file."
+msgstr ""
+
+#: ./doc/image-guide/ch_creating_images_automatically.xml:88(para)
+msgid "To run this, do, as root:"
+msgstr ""
+
+#: ./doc/image-guide/ch_creating_images_automatically.xml:91(para)
+msgid "The <literal>-d3</literal> flag tells Oz to show status information as it runs."
+msgstr ""
+
+#: ./doc/image-guide/ch_creating_images_automatically.xml:95(para)
+msgid "The <literal>-u</literal> tells Oz to do the customization (install extra packages, run the commands) once it does the initial install."
+msgstr ""
+
+#: ./doc/image-guide/ch_creating_images_automatically.xml:101(para)
+msgid "The <literal>-x &lt;filename&gt;</literal> flag tells Oz what filename to use to write out a libvirt XML file (otherwise it will default to something like <filename>centos64Apr_03_2013-12:39:42</filename>."
+msgstr ""
+
+#: ./doc/image-guide/ch_creating_images_automatically.xml:89(para)
+msgid "<placeholder-1/><placeholder-2/>If you leave out the <literal>-u</literal> flag, or you want to edit the file to do additional customizations, you can use the <placeholder-3/> command, using the libvirt XML file that <placeholder-4/> creates. For example: <placeholder-5/> Oz will invoke libvirt to boot the image inside of KVM, then Oz will ssh into the instance and perform the customizations."
+msgstr ""
+
+#: ./doc/image-guide/ch_creating_images_automatically.xml:119(title)
+msgid "VMBuilder"
+msgstr ""
+
+#: ./doc/image-guide/ch_creating_images_automatically.xml:120(para)
+msgid "<link href=\"https://launchpad.net/vmbuilder\">VMBuilder</link> (Virtual Machine Builder) is a command-line tool that creates virtual machine images for different hypervisors. The version of VMBuilder that ships with Ubuntu can only create Ubuntu virtual machine guests. The version of VMBuilder that ships with Debian can create Ubuntu and Debian virtual machine guests."
+msgstr ""
+
+#: ./doc/image-guide/ch_creating_images_automatically.xml:127(para)
+msgid "The <link href=\"https://help.ubuntu.com/12.04/serverguide/jeos-and-vmbuilder.html\"><citetitle>Ubuntu Server Guide</citetitle></link> has documentation on how to use VMBuilder to create an Ubuntu image."
+msgstr ""
+
+#: ./doc/image-guide/ch_creating_images_automatically.xml:134(title)
+msgid "BoxGrinder"
+msgstr ""
+
+#: ./doc/image-guide/ch_creating_images_automatically.xml:135(para)
+msgid "<link href=\"http://boxgrinder.org/\">BoxGrinder</link> is another tool for creating virtual machine images, which it calls appliances. BoxGrinder can create Fedora, Red Hat Enterprise Linux, or CentOS images. BoxGrinder is currently only supported on Fedora."
+msgstr ""
+
+#: ./doc/image-guide/ch_creating_images_automatically.xml:144(title)
+msgid "VeeWee"
+msgstr ""
+
+#: ./doc/image-guide/ch_creating_images_automatically.xml:145(para)
+msgid "<link href=\"https://github.com/jedi4ever/veewee\"> VeeWee</link> is often used to build <link href=\"http://vagrantup.com\">Vagrant</link> boxes, but it can also be used to build KVM images."
+msgstr ""
+
+#: ./doc/image-guide/ch_creating_images_automatically.xml:151(title)
+msgid "Packer"
+msgstr ""
+
+#: ./doc/image-guide/ch_creating_images_automatically.xml:152(para)
+msgid "<link href=\"http://www.packer.io/\"> Packer</link> is a tool for creating machine images for multiple platforms from a single source configuration."
+msgstr ""
+
+#: ./doc/image-guide/ch_creating_images_automatically.xml:158(title)
+msgid "imagefactory"
+msgstr ""
+
+#: ./doc/image-guide/ch_creating_images_automatically.xml:159(para)
+msgid "<link href=\"http://imgfac.org/\">imagefactory</link> is a newer tool designed to automate the building, converting, and uploading images to different cloud providers. It uses Oz as its back-end and includes support for OpenStack-based clouds."
+msgstr ""
+
+#: ./doc/image-guide/ch_creating_images_automatically.xml:166(title)
+msgid "SUSE Studio"
+msgstr ""
+
+#: ./doc/image-guide/ch_creating_images_automatically.xml:167(para)
+msgid "<link href=\"http://susestudio.com\">SUSE Studio</link> is a web application for building and testing software applications in a web browser. It supports the creation of physical, virtual or cloud-based applications and includes support for building images for OpenStack based clouds using SUSE Linux Enterprise and openSUSE as distributions."
+msgstr ""
+
+#: ./doc/image-guide/ch_obtaining_images.xml:6(title)
+msgid "Get images"
+msgstr ""
+
+#: ./doc/image-guide/ch_obtaining_images.xml:8(para)
+msgid "The simplest way to obtain a virtual machine image that works with OpenStack is to download one that someone else has already created."
+msgstr ""
+
+#: ./doc/image-guide/ch_obtaining_images.xml:11(title)
+msgid "CirrOS (test) images"
+msgstr ""
+
+#: ./doc/image-guide/ch_obtaining_images.xml:12(para)
+msgid "CirrOS is a minimal Linux distribution that was designed for use as a test image on clouds such as OpenStack Compute. You can download a CirrOS image in various formats from the <link href=\"https://launchpad.net/cirros/+download\">CirrOS Launchpad download page</link>."
+msgstr ""
+
+#: ./doc/image-guide/ch_obtaining_images.xml:21(para)
+msgid "In a CirrOS image, the login account is <literal>cirros</literal>. The password is <literal>cubswin:)</literal>"
+msgstr ""
+
+#: ./doc/image-guide/ch_obtaining_images.xml:16(para)
+msgid "If your deployment uses QEMU or KVM, we recommend using the images in qcow2 format. The most recent 64-bit qcow2 image as of this writing is <link href=\"http://download.cirros-cloud.net/0.3.2/cirros-0.3.2-x86_64-disk.img\">cirros-0.3.2-x86_64-disk.img</link><placeholder-1/>"
+msgstr ""
+
+#: ./doc/image-guide/ch_obtaining_images.xml:27(title)
+msgid "Official Ubuntu images"
+msgstr ""
+
+#: ./doc/image-guide/ch_obtaining_images.xml:28(para)
+msgid "Canonical maintains an <link href=\"http://cloud-images.ubuntu.com/\">official set of Ubuntu-based images</link>."
+msgstr ""
+
+#: ./doc/image-guide/ch_obtaining_images.xml:30(para)
+msgid "Images are arranged by Ubuntu release, and by image release date, with \"current\" being the most recent. For example, the page that contains the most recently built image for Ubuntu 12.04 \"Precise Pangolin\" is <link href=\"http://cloud-images.ubuntu.com/precise/current/\">http://cloud-images.ubuntu.com/precise/current/</link>. Scroll to the bottom of the page for links to images that can be downloaded directly."
+msgstr ""
+
+#: ./doc/image-guide/ch_obtaining_images.xml:40(para)
+msgid "In an Ubuntu cloud image, the login account is <literal>ubuntu</literal>."
+msgstr ""
+
+#: ./doc/image-guide/ch_obtaining_images.xml:36(para)
+msgid "If your deployment uses QEMU or KVM, we recommend using the images in qcow2 format. The most recent version of the 64-bit QCOW2 image for Ubuntu 12.04 is <link href=\"http://uec-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64-disk1.img\">precise-server-cloudimg-amd64-disk1.img</link>.<placeholder-1/>"
+msgstr ""
+
+#: ./doc/image-guide/ch_obtaining_images.xml:45(title)
+msgid "Official Red Hat Enterprise Linux images"
+msgstr ""
+
+#: ./doc/image-guide/ch_obtaining_images.xml:46(para)
+msgid "Red Hat maintains an official Red Hat Enterprise Linux 6 cloud image. A valid Red Hat Enterprise Linux 6 subscription is required to download the <link href=\"https://rhn.redhat.com/rhn/software/channel/downloads/Download.do?cid=16952\">KVM Guest Image</link>."
+msgstr ""
+
+#: ./doc/image-guide/ch_obtaining_images.xml:53(para)
+msgid "A <link href=\"https://rhn.redhat.com/rhn/software/channel/downloads/Download.do?cid=10486\">boot.iso</link> image is also available. This is the same as the <literal>boot.iso</literal> file provided on the Red Hat Enterprise Linux installation DVD. It is a minimal image suitable for kickstarting operating system installation over a network."
+msgstr ""
+
+#: ./doc/image-guide/ch_obtaining_images.xml:63(title)
+msgid "Official Fedora images"
+msgstr ""
+
+#: ./doc/image-guide/ch_obtaining_images.xml:64(para)
+msgid "The Fedora project maintains a list of official cloud images at <link href=\"http://cloud.fedoraproject.org/\"/>. The images include the <systemitem class=\"process\">cloud-init</systemitem> utility to support key and user data injection. The default user name is <systemitem class=\"username\">fedora</systemitem>."
+msgstr ""
+
+#: ./doc/image-guide/ch_obtaining_images.xml:72(title)
+msgid "Official openSUSE and SLES images"
+msgstr ""
+
+#: ./doc/image-guide/ch_obtaining_images.xml:73(para)
+msgid "SUSE does not provide openSUSE or SUSE Linux Enterprise Server (SLES) images for direct download. Instead, they provide a web-based tool called <link href=\"http://susestudio.com\">SUSE Studio</link> that you can use to build openSUSE and SLES images."
+msgstr ""
+
+#: ./doc/image-guide/ch_obtaining_images.xml:79(para)
+msgid "For example, Christian Berendt used <link href=\"http://www.opensuse.org\">openSUSE</link> to create <link href=\"http://susestudio.com/a/YRUrwO/testing-instance-for-openstack-opensuse-12-3\"> a test openSUSE 12.3 image</link>."
+msgstr ""
+
+#: ./doc/image-guide/ch_obtaining_images.xml:84(title)
+msgid "Official images from other Linux distributions"
+msgstr ""
+
+#: ./doc/image-guide/ch_obtaining_images.xml:85(para)
+msgid "As of this writing, we are not aware of other distributions that provide images for download."
+msgstr ""
+
+#: ./doc/image-guide/ch_obtaining_images.xml:88(title)
+msgid "Rackspace Cloud Builders (multiple distros) images"
+msgstr ""
+
+#: ./doc/image-guide/ch_obtaining_images.xml:90(para)
+msgid "Rackspace Cloud Builders maintains a list of pre-built images from various distributions (Red Hat, CentOS, Fedora, Ubuntu). Links to these images can be found at <link href=\"https://github.com/rackerjoe/oz-image-build\">rackerjoe/oz-image-build on Github</link>."
+msgstr ""
+
+#: ./doc/image-guide/ch_obtaining_images.xml:96(title)
+msgid "Microsoft Windows images"
+msgstr ""
+
+#: ./doc/image-guide/ch_obtaining_images.xml:97(para)
+msgid "Cloudbase Solutions hosts an <link href=\"http://www.cloudbase.it/ws2012/\">OpenStack Windows Server 2012 Standard Evaluation image</link> that runs on Hyper-V, KVM, and XenServer/XCP."
+msgstr ""
+
 #. When image changes, this message will be marked fuzzy or untranslated for you.
 #. It doesn't matter what you translate it to: it's not used at all.
 #: ./doc/image-guide/section_ubuntu-example.xml:50(None)
@@ -759,272 +1343,36 @@ msgstr ""
 msgid "The underlying image file that you created with <placeholder-1/>, such as <filename>/tmp/precise.qcow2</filename>, is now ready for uploading to the OpenStack Image Service."
 msgstr ""
 
-#: ./doc/image-guide/ch_introduction.xml:6(title)
-msgid "Introduction"
+#: ./doc/image-guide/section_glance-image-metadata.xml:7(title)
+msgid "Image metadata"
 msgstr ""
 
-#: ./doc/image-guide/ch_introduction.xml:7(para)
-msgid "An OpenStack Compute cloud is not very useful unless you have virtual machine images (which some people call \"virtual appliances\"). This guide describes how to obtain, create, and modify virtual machine images that are compatible with OpenStack."
+#: ./doc/image-guide/section_glance-image-metadata.xml:9(para)
+msgid "Image metadata can help end users determine the nature of an image, and is used by associated OpenStack components and drivers which interface with the Image Service."
 msgstr ""
 
-#: ./doc/image-guide/ch_introduction.xml:10(para)
-msgid "To keep things brief, we'll sometimes use the term \"image\" instead of \"virtual machine image\"."
+#: ./doc/image-guide/section_glance-image-metadata.xml:11(para)
+msgid "Metadata can also determine the scheduling of hosts. If the <option>property</option> option is set on an image, and Compute is configured so that the <systemitem>ImagePropertiesFilter</systemitem> scheduler filter is enabled (default), then the scheduler only considers compute hosts that satisfy that property."
 msgstr ""
 
-#: ./doc/image-guide/ch_introduction.xml:12(para)
-msgid "What is a virtual machine image?"
+#: ./doc/image-guide/section_glance-image-metadata.xml:15(para)
+msgid "Compute's <systemitem>ImagePropertiesFilter</systemitem> value is specified in the <option>scheduler_default_filter</option> value in the <filename>/etc/nova/nova.conf</filename> file."
 msgstr ""
 
-#: ./doc/image-guide/ch_introduction.xml:13(para)
-msgid "A virtual machine image is a single file which contains a virtual disk that has a bootable operating system installed on it."
+#: ./doc/image-guide/section_glance-image-metadata.xml:18(para)
+msgid "You can add metadata to Image Service images by using the <option>--property <replaceable>key</replaceable>=<replaceable>value</replaceable></option> option with the <placeholder-1/> or <placeholder-2/> command. More than one property can be specified. For example:"
 msgstr ""
 
-#: ./doc/image-guide/ch_introduction.xml:15(para)
-msgid "Virtual machine images come in different formats, some of which are described below. In a later chapter, we'll describe how to convert between formats."
+#: ./doc/image-guide/section_glance-image-metadata.xml:22(replaceable)
+msgid "img-uuid"
 msgstr ""
 
-#: ./doc/image-guide/ch_introduction.xml:19(term)
-msgid "Raw"
+#: ./doc/image-guide/section_glance-image-metadata.xml:23(para)
+msgid "Common image properties are also specified in the <filename>/etc/glance/schema-image.json</filename> file. For a complete list of valid property keys and values, refer to the <link href=\"http://docs.openstack.org/cli-reference/content/\"><citetitle>OpenStack Command-Line Reference</citetitle></link>."
 msgstr ""
 
-#: ./doc/image-guide/ch_introduction.xml:26(para)
-msgid "We don't recommend creating raw images by dd'ing block device files, we discuss how to create raw images later."
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:20(para)
-msgid "The \"raw\" image format is the simplest one, and is natively supported by both KVM and Xen hypervisors. You can think of a raw image as being the bit-equivalent of a block device file, created as if somebody had copied, say, <filename>/dev/sda</filename> to a file using the <placeholder-1/> command. <placeholder-2/>"
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:32(term) ./doc/image-guide/ch_converting.xml:26(td) ./doc/image-guide/ch_converting.xml:27(literal)
-msgid "qcow2"
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:37(para)
-msgid "Using sparse representation, so the image size is smaller"
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:40(para)
-msgid "Support for snapshots"
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:33(para)
-msgid "The <link href=\"http://en.wikibooks.org/wiki/QEMU/Images\">qcow2</link> (QEMU copy-on-write version 2) format is commonly used with the KVM hypervisor. It has some additional features over the raw format, such as:<placeholder-1/>"
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:43(para)
-msgid "Because qcow2 is sparse, it's often faster to convert a raw image to qcow2 and upload it then to upload the raw file."
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:47(para)
-msgid "Because raw images don't support snapshots, OpenStack Compute will automatically convert raw image files to qcow2 as needed."
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:53(term)
-msgid "AMI/AKI/ARI"
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:59(para)
-msgid "AMI (Amazon Machine Image):"
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:60(para)
-msgid "This is a virtual machine image in raw format, as described above."
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:64(para)
-msgid "AKI (Amazon Kernel Image)"
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:65(para)
-msgid "A kernel file that the hypervisor will load initially to boot the image. For a Linux machine, this would be a <emphasis>vmlinuz</emphasis> file."
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:72(para)
-msgid "ARI (Amazon Ramdisk Image)"
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:73(para)
-msgid "An optional ramdisk file mounted at boot time. For a Linux machine, this would be an <emphasis>initrd</emphasis> file."
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:54(para)
-msgid "The <link href=\"http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AMIs.html\">AMI/AKI/ARI </link>format was the initial image format supported by Amazon EC2. The image consists of three files:<placeholder-1/>"
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:81(term)
-msgid "UEC tarball"
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:84(para)
-msgid "Ubuntu Enterprise Cloud refers to a discontinued Eucalyptus-based Ubuntu cloud solution that has been replaced by the OpenStack-based Ubuntu Cloud Infrastructure."
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:82(para)
-msgid "A UEC (Ubuntu Enterprise Cloud) tarball is a gzipped tarfile that contains an AMI file, AKI file, and ARI file.<placeholder-1/>"
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:90(term)
-msgid "VMDK"
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:91(para)
-msgid "VMWare's ESXi hypervisor uses the <link href=\"http://www.vmware.com/technical-resources/interfaces/vmdk.html\">VMDK</link> (Virtual Machine Disk) format for images."
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:96(term)
-msgid "VDI"
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:97(para)
-msgid "VirtualBox uses the <link href=\"https://forums.virtualbox.org/viewtopic.php?t=8046\">VDI</link> (Virtual Disk Image) format for image files. None of the OpenStack Compute hypervisors support VDI directly, so you will need to convert these files to a different format to use them with OpenStack."
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:104(term)
-msgid "VHD"
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:105(para)
-msgid "Microsoft Hyper-V uses the VHD (Virtual Hard Disk) format for images."
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:108(term)
-msgid "VHDX"
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:109(para)
-msgid "The version of Hyper-V that ships with Microsoft Server 2012 uses the newer <link href=\"http://technet.microsoft.com/en-us/library/hh831446.aspx\">VHDX</link> format, which has some additional features over VHD such as support for larger disk sizes and protection against data corruption during power failures."
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:115(term)
-msgid "OVF"
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:116(para)
-msgid "<link href=\"http://www.dmtf.org/standards/ovf\">OVF</link> (Open Virtualization Format) is a packaging format for virtual machines, defined by the Distributed Management Task Force (DMTF) standards group. An OVF package contains one or more image files, a .ovf XML metadata file that contains information about the virtual machine, and possibly other files as well."
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:121(para)
-msgid "An OVF package can be distributed in different ways. For example, it could be distributed as a set of discrete files, or as a tar archive file with an .ova (open virtual appliance/application) extension."
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:124(para)
-msgid "OpenStack Compute does not currently have support for OVF packages, so you will need to extract the image file(s) from an OVF package if you wish to use it with OpenStack."
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:129(term)
-msgid "ISO"
-msgstr ""
-
-#: ./doc/image-guide/ch_introduction.xml:130(para)
-msgid "The <link href=\"http://www.ecma-international.org/publications/standards/Ecma-119.htm\">ISO</link> format is a disk image formatted with the read-only ISO 9660 (also known as ECMA-119) filesystem commonly used for CDs and DVDs. While we don't normally think of ISO as a virtual machine image format, since ISOs contain bootable filesystems with an installed operating system, you can treat them the same as you treat other virtual machine image files."
-msgstr ""
-
-#: ./doc/image-guide/ch_creating_images_automatically.xml:6(title)
-msgid "Tool support for image creation"
-msgstr ""
-
-#: ./doc/image-guide/ch_creating_images_automatically.xml:8(para)
-msgid "There are several tools that are designed to automate image creation."
-msgstr ""
-
-#: ./doc/image-guide/ch_creating_images_automatically.xml:11(title)
-msgid "Oz"
-msgstr ""
-
-#: ./doc/image-guide/ch_creating_images_automatically.xml:22(para)
-msgid "As of this writing, there are no Oz packages for Ubuntu, so you will need to either install from source or build your own .deb file."
-msgstr ""
-
-#: ./doc/image-guide/ch_creating_images_automatically.xml:12(para)
-msgid "<link href=\"https://github.com/clalancette/oz/wiki\">Oz</link> is a command-line tool that automates the process of creating a virtual machine image file. Oz is a Python app that interacts with KVM to step through the process of installing a virtual machine. It uses a predefined set of kickstart (Red Hat-based systems) and preseed files (Debian-based systems) for operating systems that it supports, and it can also be used to create Microsoft Windows images. On Fedora, install Oz with yum:<placeholder-1/><placeholder-2/>"
-msgstr ""
-
-#: ./doc/image-guide/ch_creating_images_automatically.xml:26(para)
-msgid "A full treatment of Oz is beyond the scope of this document, but we will provide an example. You can find additional examples of Oz template files on github at <link href=\"https://github.com/rackerjoe/oz-image-build/tree/master/templates\">rackerjoe/oz-image-build/templates</link>. Here's how you would create a CentOS 6.4 image with Oz."
-msgstr ""
-
-#: ./doc/image-guide/ch_creating_images_automatically.xml:33(para)
-msgid "Create a template file (we'll call it <filename>centos64.tdl</filename>) with the following contents. The only entry you will need to change is the <literal>&lt;rootpw&gt;</literal> contents.<placeholder-1/>"
-msgstr ""
-
-#: ./doc/image-guide/ch_creating_images_automatically.xml:71(para)
-msgid "This Oz template specifies where to download the Centos 6.4 install ISO. Oz will use the version information to identify which kickstart file to use. In this case, it will be <link href=\"https://github.com/clalancette/oz/blob/master/oz/auto/RHEL6.auto\">RHEL6.auto</link>. It adds EPEL as a repository and install the <literal>epel-release</literal>, <literal>cloud-utils</literal>, and <literal>cloud-init</literal> packages, as specified in the <literal>packages</literal> section of the file."
-msgstr ""
-
-#: ./doc/image-guide/ch_creating_images_automatically.xml:82(para)
-msgid "After Oz does the initial OS install using the kickstart file, it customizes the image by doing an update. It also removes any reference to the eth0 device that libvirt creates while Oz does the customizing, as specified in the <literal>command</literal> section of the XML file."
-msgstr ""
-
-#: ./doc/image-guide/ch_creating_images_automatically.xml:88(para)
-msgid "To run this, do, as root:"
-msgstr ""
-
-#: ./doc/image-guide/ch_creating_images_automatically.xml:91(para)
-msgid "The <literal>-d3</literal> flag tells Oz to show status information as it runs."
-msgstr ""
-
-#: ./doc/image-guide/ch_creating_images_automatically.xml:95(para)
-msgid "The <literal>-u</literal> tells Oz to do the customization (install extra packages, run the commands) once it does the initial install."
-msgstr ""
-
-#: ./doc/image-guide/ch_creating_images_automatically.xml:101(para)
-msgid "The <literal>-x &lt;filename&gt;</literal> flag tells Oz what filename to use to write out a libvirt XML file (otherwise it will default to something like <filename>centos64Apr_03_2013-12:39:42</filename>."
-msgstr ""
-
-#: ./doc/image-guide/ch_creating_images_automatically.xml:89(para)
-msgid "<placeholder-1/><placeholder-2/>If you leave out the <literal>-u</literal> flag, or you want to edit the file to do additional customizations, you can use the <placeholder-3/> command, using the libvirt XML file that <placeholder-4/> creates. For example: <placeholder-5/> Oz will invoke libvirt to boot the image inside of KVM, then Oz will ssh into the instance and perform the customizations."
-msgstr ""
-
-#: ./doc/image-guide/ch_creating_images_automatically.xml:119(title)
-msgid "VMBuilder"
-msgstr ""
-
-#: ./doc/image-guide/ch_creating_images_automatically.xml:120(para)
-msgid "<link href=\"https://launchpad.net/vmbuilder\">VMBuilder</link> (Virtual Machine Builder) is a command-line tool that creates virtual machine images for different hypervisors. The version of VMBuilder that ships with Ubuntu can only create Ubuntu virtual machine guests. The version of VMBuilder that ships with Debian can create Ubuntu and Debian virtual machine guests."
-msgstr ""
-
-#: ./doc/image-guide/ch_creating_images_automatically.xml:127(para)
-msgid "The <link href=\"https://help.ubuntu.com/12.04/serverguide/jeos-and-vmbuilder.html\"><citetitle>Ubuntu Server Guide</citetitle></link> has documentation on how to use VMBuilder to create an Ubuntu image."
-msgstr ""
-
-#: ./doc/image-guide/ch_creating_images_automatically.xml:134(title)
-msgid "BoxGrinder"
-msgstr ""
-
-#: ./doc/image-guide/ch_creating_images_automatically.xml:135(para)
-msgid "<link href=\"http://boxgrinder.org/\">BoxGrinder</link> is another tool for creating virtual machine images, which it calls appliances. BoxGrinder can create Fedora, Red Hat Enterprise Linux, or CentOS images. BoxGrinder is currently only supported on Fedora."
-msgstr ""
-
-#: ./doc/image-guide/ch_creating_images_automatically.xml:144(title)
-msgid "VeeWee"
-msgstr ""
-
-#: ./doc/image-guide/ch_creating_images_automatically.xml:145(para)
-msgid "<link href=\"https://github.com/jedi4ever/veewee\"> VeeWee</link> is often used to build <link href=\"http://vagrantup.com\">Vagrant</link> boxes, but it can also be used to build KVM images."
-msgstr ""
-
-#: ./doc/image-guide/ch_creating_images_automatically.xml:151(title)
-msgid "Packer"
-msgstr ""
-
-#: ./doc/image-guide/ch_creating_images_automatically.xml:152(para)
-msgid "<link href=\"http://www.packer.io/\"> Packer</link> is a tool for creating machine images for multiple platforms from a single source configuration."
-msgstr ""
-
-#: ./doc/image-guide/ch_creating_images_automatically.xml:158(title)
-msgid "imagefactory"
-msgstr ""
-
-#: ./doc/image-guide/ch_creating_images_automatically.xml:159(para)
-msgid "<link href=\"http://imgfac.org/\">imagefactory</link> is a newer tool designed to automate the building, converting, and uploading images to different cloud providers. It uses Oz as its back-end and includes support for OpenStack-based clouds."
-msgstr ""
-
-#: ./doc/image-guide/ch_creating_images_automatically.xml:166(title)
-msgid "SUSE Studio"
-msgstr ""
-
-#: ./doc/image-guide/ch_creating_images_automatically.xml:167(para)
-msgid "<link href=\"http://susestudio.com\">SUSE Studio</link> is a web application for building and testing software applications in a web browser. It supports the creation of physical, virtual or cloud-based applications and includes support for building images for OpenStack based clouds using SUSE Linux Enterprise and openSUSE as distributions."
+#: ./doc/image-guide/section_glance-image-metadata.xml:28(para)
+msgid "All associated properties for an image can be displayed using the <placeholder-1/> command. For example:"
 msgstr ""
 
 #: ./doc/image-guide/ch_openstack_images.xml:10(title)
@@ -1395,66 +1743,6 @@ msgstr ""
 msgid "Because 86400 seconds (24 hours) is the default time for <literal>remove_unused_original_minimum_age_seconds</literal>, you can either wait for that time interval to see the base image removed, or set the value to a shorter time period in <filename>nova.conf</filename>. Restart all nova services after changing a setting in <filename>nova.conf</filename>."
 msgstr ""
 
-#: ./doc/image-guide/section_windows-example.xml:8(title)
-msgid "Example: Microsoft Windows image"
-msgstr ""
-
-#: ./doc/image-guide/section_windows-example.xml:9(para)
-msgid "We do not yet have a fully documented example of how to create a Microsoft Windows image. You can use libvirt to install Windows from an installation DVD using the same approach as with the CentOS and Ubuntu examples. Once the initial install is done, you will need to perform some Windows-specific customizations."
-msgstr ""
-
-#: ./doc/image-guide/section_windows-example.xml:14(title)
-msgid "Install VirtIO drivers"
-msgstr ""
-
-#: ./doc/image-guide/section_windows-example.xml:15(para)
-msgid "Installing the <link href=\"http://www.linux-kvm.org/page/WindowsGuestDrivers/Download_Drivers\">VirtIO paravirtualizaion drivers for Windows</link> will improve virtual machine performance when using KVM as the hypervisor to run Windows."
-msgstr ""
-
-#: ./doc/image-guide/section_windows-example.xml:20(title)
-msgid "Sysprep"
-msgstr ""
-
-#: ./doc/image-guide/section_windows-example.xml:21(para)
-msgid "Microsoft has a special tool called <link href=\"http://technet.microsoft.com/en-us/library/cc766049(v=ws.10).aspx\">Sysprep</link> that must be run inside of a Windows guest to prepare it for use as a virtual machine image. On Windows 2012 server, invoke sysprep, as follows: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/image-guide/section_windows-example.xml:28(title)
-msgid "cloudbase-init"
-msgstr ""
-
-#: ./doc/image-guide/section_windows-example.xml:29(para)
-msgid "<link href=\"http://www.cloudbase.it/cloud-init-for-windows-instances/\">cloudbase-init</link> is a Windows port of cloud-init that should be installed inside of the guest. The <link href=\"https://github.com/cloudbase/cloudbase-init\">source code</link> is available on github."
-msgstr ""
-
-#: ./doc/image-guide/section_windows-example.xml:35(title)
-msgid "Jordan Rinke's OpenStack Windows resources"
-msgstr ""
-
-#: ./doc/image-guide/section_windows-example.xml:36(para)
-msgid "Jordan Rinke maintains <link href=\"https://github.com/jordanrinke/openstack\">a collection of resources</link> for managing OpenStack Windows virtual machine guests."
-msgstr ""
-
-#: ./doc/image-guide/section_windows-example.xml:41(title)
-msgid "Windows instances require the timezone to be \"localtime\""
-msgstr ""
-
-#: ./doc/image-guide/section_windows-example.xml:42(para)
-msgid "When uploading Windows images, you must set the <literal>os_type</literal> parameter to <literal>windows</literal>, which causes instances to use the local time zone. Failing to set this will cause the clock timezone to be UTC, which has unexpected side effects in Windows."
-msgstr ""
-
-#: ./doc/image-guide/section_freebsd-example.xml:8(title)
-msgid "Example: FreeBSD image"
-msgstr ""
-
-#: ./doc/image-guide/section_freebsd-example.xml:9(para)
-msgid "We do not yet have a fully documented example of how to create a FreeBSD image."
-msgstr ""
-
-#: ./doc/image-guide/section_freebsd-example.xml:11(para)
-msgid "See the <link href=\"http://pellaeon.github.io/bsd-cloudinit/\">bsd-cloudinit</link> project for information on how to build a FreeBSD VM image that works with OpenStack."
-msgstr ""
-
 #. When image changes, this message will be marked fuzzy or untranslated for you.
 #. It doesn't matter what you translate it to: it's not used at all.
 #: ./doc/image-guide/ch_creating_images_manually.xml:82(None)
@@ -1561,296 +1849,8 @@ msgstr ""
 msgid "In the example above, the guest <literal>centos-6.4</literal> uses VNC display <literal>:1</literal>, which corresponds to tcp port <literal>5901</literal>. You should be able to connect to a VNC client running on your local machine to display :1 on the remote machine and step through the installation process."
 msgstr ""
 
-#: ./doc/image-guide/section_glance_image-formats.xml:6(title)
-msgid "Disk and container formats for images"
-msgstr ""
-
-#: ./doc/image-guide/section_glance_image-formats.xml:8(para)
-msgid "When you add an image to the Image Service, you can specify its disk and container formats."
-msgstr ""
-
-#: ./doc/image-guide/section_glance_image-formats.xml:11(title)
-msgid "Disk formats"
-msgstr ""
-
-#: ./doc/image-guide/section_glance_image-formats.xml:12(para)
-msgid "The disk format of a virtual machine image is the format of the underlying disk image. Virtual appliance vendors have different formats for laying out the information contained in a virtual machine disk image."
-msgstr ""
-
-#: ./doc/image-guide/section_glance_image-formats.xml:16(para)
-msgid "Set the disk format for your image to one of the following values:"
-msgstr ""
-
-#: ./doc/image-guide/section_glance_image-formats.xml:20(para)
-msgid "<literal>raw</literal>. An unstructured disk image format; if you have a file without an extension it is possibly a raw format"
-msgstr ""
-
-#: ./doc/image-guide/section_glance_image-formats.xml:25(para)
-msgid "<literal>vhd</literal>. The VHD disk format, a common disk format used by virtual machine monitors from VMWare, Xen, Microsoft, VirtualBox, and others"
-msgstr ""
-
-#: ./doc/image-guide/section_glance_image-formats.xml:31(para)
-msgid "<literal>vmdk</literal>. Common disk format supported by many common virtual machine monitors"
-msgstr ""
-
-#: ./doc/image-guide/section_glance_image-formats.xml:36(para)
-msgid "<literal>vdi</literal>. Supported by VirtualBox virtual machine monitor and the QEMU emulator"
-msgstr ""
-
-#: ./doc/image-guide/section_glance_image-formats.xml:41(para)
-msgid "<literal>iso</literal>. An archive format for the data contents of an optical disc, such as CD-ROM."
-msgstr ""
-
-#: ./doc/image-guide/section_glance_image-formats.xml:46(para)
-msgid "<literal>qcow2</literal>. Supported by the QEMU emulator that can expand dynamically and supports Copy on Write"
-msgstr ""
-
-#: ./doc/image-guide/section_glance_image-formats.xml:51(para) ./doc/image-guide/section_glance_image-formats.xml:87(para)
-msgid "<literal>aki</literal>. An Amazon kernel image."
-msgstr ""
-
-#: ./doc/image-guide/section_glance_image-formats.xml:55(para) ./doc/image-guide/section_glance_image-formats.xml:91(para)
-msgid "<literal>ari</literal>. An Amazon ramdisk image."
-msgstr ""
-
-#: ./doc/image-guide/section_glance_image-formats.xml:59(para) ./doc/image-guide/section_glance_image-formats.xml:95(para)
-msgid "<literal>ami</literal>. An Amazon machine image."
-msgstr ""
-
-#: ./doc/image-guide/section_glance_image-formats.xml:65(title)
-msgid "Container formats"
-msgstr ""
-
-#: ./doc/image-guide/section_glance_image-formats.xml:66(para)
-msgid "The container format indicates whether the virtual machine image is in a file format that also contains metadata about the actual virtual machine."
-msgstr ""
-
-#: ./doc/image-guide/section_glance_image-formats.xml:70(para)
-msgid "The Image Service and other OpenStack projects do not currently support the container format. It is safe to specify <literal>bare</literal> as the container format if you are unsure."
-msgstr ""
-
-#: ./doc/image-guide/section_glance_image-formats.xml:75(para)
-msgid "You can set the container format for your image to one of the following values:"
-msgstr ""
-
-#: ./doc/image-guide/section_glance_image-formats.xml:79(para)
-msgid "<literal>bare</literal>. The image does not have a container or metadata envelope."
-msgstr ""
-
-#: ./doc/image-guide/section_glance_image-formats.xml:83(para)
-msgid "<literal>ovf</literal>. The OVF container format."
-msgstr ""
-
-#: ./doc/image-guide/section_glance-image-metadata.xml:7(title)
-msgid "Image metadata"
-msgstr ""
-
-#: ./doc/image-guide/section_glance-image-metadata.xml:9(para)
-msgid "Image metadata can help end users determine the nature of an image, and is used by associated OpenStack components and drivers which interface with the Image Service."
-msgstr ""
-
-#: ./doc/image-guide/section_glance-image-metadata.xml:11(para)
-msgid "Metadata can also determine the scheduling of hosts. If the <option>property</option> option is set on an image, and Compute is configured so that the <systemitem>ImagePropertiesFilter</systemitem> scheduler filter is enabled (default), then the scheduler only considers compute hosts that satisfy that property."
-msgstr ""
-
-#: ./doc/image-guide/section_glance-image-metadata.xml:15(para)
-msgid "Compute's <systemitem>ImagePropertiesFilter</systemitem> value is specified in the <option>scheduler_default_filter</option> value in the <filename>/etc/nova/nova.conf</filename> file."
-msgstr ""
-
-#: ./doc/image-guide/section_glance-image-metadata.xml:18(para)
-msgid "You can add metadata to Image Service images by using the <option>--property <replaceable>key</replaceable>=<replaceable>value</replaceable></option> option with the <placeholder-1/> or <placeholder-2/> command. More than one property can be specified. For example:"
-msgstr ""
-
-#: ./doc/image-guide/section_glance-image-metadata.xml:22(replaceable)
-msgid "img-uuid"
-msgstr ""
-
-#: ./doc/image-guide/section_glance-image-metadata.xml:23(para)
-msgid "Common image properties are also specified in the <filename>/etc/glance/schema-image.json</filename> file. For a complete list of valid property keys and values, refer to the <link href=\"http://docs.openstack.org/cli-reference/content/\"><citetitle>OpenStack Command-Line Reference</citetitle></link>."
-msgstr ""
-
-#: ./doc/image-guide/section_glance-image-metadata.xml:28(para)
-msgid "All associated properties for an image can be displayed using the <placeholder-1/> command. For example:"
-msgstr ""
-
-#: ./doc/image-guide/ch_converting.xml:4(title)
-msgid "Converting between image formats"
-msgstr ""
-
-#: ./doc/image-guide/ch_converting.xml:5(para)
-msgid "Converting images from one format to another is generally straightforward."
-msgstr ""
-
-#: ./doc/image-guide/ch_converting.xml:7(title)
-msgid "qemu-img convert: raw, qcow2, VDI, VMDK"
-msgstr ""
-
-#: ./doc/image-guide/ch_converting.xml:8(para)
-msgid "The <placeholder-1/> command can do conversion between multiple formats, including raw, qcow2, VDI (VirtualBox), VMDK (VMWare) and VHD (Hyper-V)."
-msgstr ""
-
-#: ./doc/image-guide/ch_converting.xml:12(caption)
-msgid "qemu-img format strings"
-msgstr ""
-
-#: ./doc/image-guide/ch_converting.xml:16(th)
-msgid "Image format"
-msgstr ""
-
-#: ./doc/image-guide/ch_converting.xml:17(th)
-msgid "Argument to qemu-img"
-msgstr ""
-
-#: ./doc/image-guide/ch_converting.xml:22(td) ./doc/image-guide/ch_converting.xml:23(literal)
-msgid "raw"
-msgstr ""
-
-#: ./doc/image-guide/ch_converting.xml:30(td)
-msgid "VDI (VirtualBox)"
-msgstr ""
-
-#: ./doc/image-guide/ch_converting.xml:31(literal)
-msgid "vdi"
-msgstr ""
-
-#: ./doc/image-guide/ch_converting.xml:34(td)
-msgid "VMDK (VMWare)"
-msgstr ""
-
-#: ./doc/image-guide/ch_converting.xml:35(literal)
-msgid "vmdk"
-msgstr ""
-
-#: ./doc/image-guide/ch_converting.xml:38(td)
-msgid "VHD (Hyper-V)"
-msgstr ""
-
-#: ./doc/image-guide/ch_converting.xml:39(literal)
-msgid "vpc"
-msgstr ""
-
-#: ./doc/image-guide/ch_converting.xml:43(para)
-msgid "This example will convert a raw image file named centos63.dsk to a qcow2 image file."
-msgstr ""
-
-#: ./doc/image-guide/ch_converting.xml:47(para)
-msgid "To convert from vmdk to raw, you would do: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/image-guide/ch_converting.xml:51(para)
-msgid "The <literal>-f <replaceable>format</replaceable></literal> flag is optional. If omitted, qemu-img will try to infer the image format."
-msgstr ""
-
-#: ./doc/image-guide/ch_converting.xml:57(title)
-msgid "VBoxManage: VDI (VirtualBox) to raw"
-msgstr ""
-
-#: ./doc/image-guide/ch_converting.xml:58(para)
-msgid "If you've created a VDI image using VirtualBox, you can convert it to raw format using the <placeholder-1/> command-line tool that ships with VirtualBox. On Mac OS X, VirtualBox stores images by default in the <filename>~/VirtualBox VMs/</filename> directory. The following example creates a raw image in the current directory from a VirtualBox VDI image.<placeholder-2/>"
-msgstr ""
-
-#: ./doc/image-guide/ch_obtaining_images.xml:6(title)
-msgid "Get images"
-msgstr ""
-
-#: ./doc/image-guide/ch_obtaining_images.xml:8(para)
-msgid "The simplest way to obtain a virtual machine image that works with OpenStack is to download one that someone else has already created."
-msgstr ""
-
-#: ./doc/image-guide/ch_obtaining_images.xml:11(title)
-msgid "CirrOS (test) images"
-msgstr ""
-
-#: ./doc/image-guide/ch_obtaining_images.xml:12(para)
-msgid "CirrOS is a minimal Linux distribution that was designed for use as a test image on clouds such as OpenStack Compute. You can download a CirrOS image in various formats from the <link href=\"https://launchpad.net/cirros/+download\">CirrOS Launchpad download page</link>."
-msgstr ""
-
-#: ./doc/image-guide/ch_obtaining_images.xml:21(para)
-msgid "In a CirrOS image, the login account is <literal>cirros</literal>. The password is <literal>cubswin:)</literal>"
-msgstr ""
-
-#: ./doc/image-guide/ch_obtaining_images.xml:16(para)
-msgid "If your deployment uses QEMU or KVM, we recommend using the images in qcow2 format. The most recent 64-bit qcow2 image as of this writing is <link href=\"http://download.cirros-cloud.net/0.3.2/cirros-0.3.2-x86_64-disk.img\">cirros-0.3.2-x86_64-disk.img</link><placeholder-1/>"
-msgstr ""
-
-#: ./doc/image-guide/ch_obtaining_images.xml:27(title)
-msgid "Official Ubuntu images"
-msgstr ""
-
-#: ./doc/image-guide/ch_obtaining_images.xml:28(para)
-msgid "Canonical maintains an <link href=\"http://cloud-images.ubuntu.com/\">official set of Ubuntu-based images</link>."
-msgstr ""
-
-#: ./doc/image-guide/ch_obtaining_images.xml:30(para)
-msgid "Images are arranged by Ubuntu release, and by image release date, with \"current\" being the most recent. For example, the page that contains the most recently built image for Ubuntu 12.04 \"Precise Pangolin\" is <link href=\"http://cloud-images.ubuntu.com/precise/current/\">http://cloud-images.ubuntu.com/precise/current/</link>. Scroll to the bottom of the page for links to images that can be downloaded directly."
-msgstr ""
-
-#: ./doc/image-guide/ch_obtaining_images.xml:40(para)
-msgid "In an Ubuntu cloud image, the login account is <literal>ubuntu</literal>."
-msgstr ""
-
-#: ./doc/image-guide/ch_obtaining_images.xml:36(para)
-msgid "If your deployment uses QEMU or KVM, we recommend using the images in qcow2 format. The most recent version of the 64-bit QCOW2 image for Ubuntu 12.04 is <link href=\"http://uec-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64-disk1.img\">precise-server-cloudimg-amd64-disk1.img</link>.<placeholder-1/>"
-msgstr ""
-
-#: ./doc/image-guide/ch_obtaining_images.xml:45(title)
-msgid "Official Red Hat Enterprise Linux images"
-msgstr ""
-
-#: ./doc/image-guide/ch_obtaining_images.xml:46(para)
-msgid "Red Hat maintains an official Red Hat Enterprise Linux 6 cloud image. A valid Red Hat Enterprise Linux 6 subscription is required to download the <link href=\"https://rhn.redhat.com/rhn/software/channel/downloads/Download.do?cid=16952\">KVM Guest Image</link>."
-msgstr ""
-
-#: ./doc/image-guide/ch_obtaining_images.xml:53(para)
-msgid "A <link href=\"https://rhn.redhat.com/rhn/software/channel/downloads/Download.do?cid=10486\">boot.iso</link> image is also available. This is the same as the <literal>boot.iso</literal> file provided on the Red Hat Enterprise Linux installation DVD. It is a minimal image suitable for kickstarting operating system installation over a network."
-msgstr ""
-
-#: ./doc/image-guide/ch_obtaining_images.xml:63(title)
-msgid "Official Fedora images"
-msgstr ""
-
-#: ./doc/image-guide/ch_obtaining_images.xml:64(para)
-msgid "The Fedora project maintains a list of official cloud images at <link href=\"http://cloud.fedoraproject.org/\"/>. The images include the <systemitem class=\"process\">cloud-init</systemitem> utility to support key and user data injection. The default user name is <systemitem class=\"username\">fedora</systemitem>."
-msgstr ""
-
-#: ./doc/image-guide/ch_obtaining_images.xml:72(title)
-msgid "Official openSUSE and SLES images"
-msgstr ""
-
-#: ./doc/image-guide/ch_obtaining_images.xml:73(para)
-msgid "SUSE does not provide openSUSE or SUSE Linux Enterprise Server (SLES) images for direct download. Instead, they provide a web-based tool called <link href=\"http://susestudio.com\">SUSE Studio</link> that you can use to build openSUSE and SLES images."
-msgstr ""
-
-#: ./doc/image-guide/ch_obtaining_images.xml:79(para)
-msgid "For example, Christian Berendt used <link href=\"http://www.opensuse.org\">openSUSE</link> to create <link href=\"http://susestudio.com/a/YRUrwO/testing-instance-for-openstack-opensuse-12-3\"> a test openSUSE 12.3 image</link>."
-msgstr ""
-
-#: ./doc/image-guide/ch_obtaining_images.xml:84(title)
-msgid "Official images from other Linux distributions"
-msgstr ""
-
-#: ./doc/image-guide/ch_obtaining_images.xml:85(para)
-msgid "As of this writing, we are not aware of other distributions that provide images for download."
-msgstr ""
-
-#: ./doc/image-guide/ch_obtaining_images.xml:88(title)
-msgid "Rackspace Cloud Builders (multiple distros) images"
-msgstr ""
-
-#: ./doc/image-guide/ch_obtaining_images.xml:90(para)
-msgid "Rackspace Cloud Builders maintains a list of pre-built images from various distributions (Red Hat, CentOS, Fedora, Ubuntu). Links to these images can be found at <link href=\"https://github.com/rackerjoe/oz-image-build\">rackerjoe/oz-image-build on Github</link>."
-msgstr ""
-
-#: ./doc/image-guide/ch_obtaining_images.xml:96(title)
-msgid "Microsoft Windows images"
-msgstr ""
-
-#: ./doc/image-guide/ch_obtaining_images.xml:97(para)
-msgid "Cloudbase Solutions hosts an <link href=\"http://www.cloudbase.it/ws2012/\">OpenStack Windows Server 2012 Standard Evaluation image</link> that runs on Hyper-V, KVM, and XenServer/XCP."
-msgstr ""
-
 #. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
-#: ./doc/image-guide/ch_obtaining_images.xml:0(None)
+#: ./doc/image-guide/ch_creating_images_manually.xml:0(None)
 msgid "translator-credits"
 msgstr ""
 
diff --git a/doc/install-guide/locale/install-guide.pot b/doc/install-guide/locale/install-guide.pot
index f97d37880c..b88689e104 100644
--- a/doc/install-guide/locale/install-guide.pot
+++ b/doc/install-guide/locale/install-guide.pot
@@ -1,7 +1,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2014-06-02 06:10+0000\n"
+"POT-Creation-Date: 2014-06-03 06:11+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -9,6 +9,472 @@ msgstr ""
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_keystone-install.xml:79(None)
+msgid "@@image: 'figures/debconf-screenshots/keystone_1_admin_token.png'; md5=29a51caaf09c3d6e3f0fda73c256a17a"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_keystone-install.xml:104(None)
+msgid "@@image: 'figures/debconf-screenshots/keystone_2_register_admin_tenant_yes_no.png'; md5=25c9a90b1df2d979aae6ce9975c7285b"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_keystone-install.xml:113(None)
+msgid "@@image: 'figures/debconf-screenshots/keystone_3_admin_user_name.png'; md5=173cf7ed13252df1425109be588b2ad6"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_keystone-install.xml:122(None)
+msgid "@@image: 'figures/debconf-screenshots/keystone_4_admin_user_email.png'; md5=b7f0d34350ccc0aa9ae4e766b7ac80c1"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_keystone-install.xml:131(None)
+msgid "@@image: 'figures/debconf-screenshots/keystone_5_admin_user_pass.png'; md5=e6b32d8d80af90f07a66abc8fb256c84"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_keystone-install.xml:140(None)
+msgid "@@image: 'figures/debconf-screenshots/keystone_6_admin_user_pass_confirm.png'; md5=1fbf9223e4923c93030d53278d1771cc"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_keystone-install.xml:154(None)
+msgid "@@image: 'figures/debconf-screenshots/keystone_7_register_endpoint.png'; md5=d24d84133bfee936267e79631a2666e6"
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-install.xml:6(title)
+msgid "Install the Identity Service"
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-install.xml:9(para)
+msgid "Install the OpenStack Identity Service on the controller node, together with <application>python-keystoneclient</application> (which is a dependency):"
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-install.xml:17(para)
+msgid "Answer to the <systemitem class=\"library\">debconf</systemitem> and <systemitem class=\"library\">dbconfig-common</systemitem> questions for setting-up the database."
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-install.xml:23(para)
+msgid "The Identity Service uses a database to store information. Specify the location of the database in the configuration file. In this guide, we use a MySQL database on the controller node with the username <literal>keystone</literal>. Replace <literal><replaceable>KEYSTONE_DBPASS</replaceable></literal> with a suitable password for the database user."
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-install.xml:30(replaceable) ./doc/install-guide/section_keystone-install.xml:38(replaceable) ./doc/install-guide/section_keystone-install.xml:57(replaceable) ./doc/install-guide/section_keystone-install.xml:59(replaceable)
+msgid "KEYSTONE_DBPASS"
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-install.xml:30(replaceable) ./doc/install-guide/section_keystone-install.xml:38(replaceable) ./doc/install-guide/section_cinder-controller.xml:44(replaceable) ./doc/install-guide/section_cinder-controller.xml:47(replaceable) ./doc/install-guide/section_cinder-controller.xml:83(replaceable) ./doc/install-guide/section_cinder-controller.xml:85(replaceable) ./doc/install-guide/section_cinder-controller.xml:101(replaceable) ./doc/install-guide/section_cinder-controller.xml:102(replaceable) ./doc/install-guide/section_cinder-controller.xml:120(replaceable) ./doc/install-guide/section_cinder-controller.xml:153(replaceable) ./doc/install-guide/section_cinder-controller.xml:154(replaceable) ./doc/install-guide/section_cinder-controller.xml:155(replaceable) ./doc/install-guide/section_cinder-controller.xml:163(replaceable) ./doc/install-guide/section_cinder-controller.xml:164(replaceable) ./doc/install-guide/section_cinder-controller.xml:165(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:79(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:85(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:91(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:107(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:122(replaceable) ./doc/install-guide/section_nova-controller.xml:44(replaceable) ./doc/install-guide/section_nova-controller.xml:59(replaceable) ./doc/install-guide/section_nova-controller.xml:140(replaceable) ./doc/install-guide/section_nova-controller.xml:141(replaceable) ./doc/install-guide/section_nova-controller.xml:160(replaceable) ./doc/install-guide/section_nova-controller.xml:177(replaceable) ./doc/install-guide/section_nova-controller.xml:178(replaceable) ./doc/install-guide/section_nova-controller.xml:179(replaceable) ./doc/install-guide/section_basics-networking-neutron.xml:277(replaceable) ./doc/install-guide/section_basics-networking-neutron.xml:321(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:143(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:145(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:179(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:180(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:194(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:205(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:214(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:232(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:242(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:253(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:258(replaceable) ./doc/install-guide/section_ceilometer-install.xml:102(replaceable) ./doc/install-guide/section_ceilometer-install.xml:111(replaceable) ./doc/install-guide/section_ceilometer-install.xml:118(replaceable) ./doc/install-guide/section_ceilometer-install.xml:145(replaceable) ./doc/install-guide/section_ceilometer-install.xml:148(replaceable) ./doc/install-guide/section_ceilometer-install.xml:196(replaceable) ./doc/install-guide/section_ceilometer-install.xml:204(replaceable) ./doc/install-guide/section_ceilometer-install.xml:208(replaceable) ./doc/install-guide/section_ceilometer-install.xml:223(replaceable) ./doc/install-guide/section_ceilometer-install.xml:230(replaceable) ./doc/install-guide/section_ceilometer-install.xml:244(replaceable) ./doc/install-guide/section_ceilometer-install.xml:245(replaceable) ./doc/install-guide/section_ceilometer-install.xml:246(replaceable) ./doc/install-guide/section_basics-ntp.xml:72(replaceable) ./doc/install-guide/ch_clients.xml:42(replaceable) ./doc/install-guide/section_glance-install.xml:55(replaceable) ./doc/install-guide/section_glance-install.xml:57(replaceable) ./doc/install-guide/section_glance-install.xml:65(replaceable) ./doc/install-guide/section_glance-install.xml:74(replaceable) ./doc/install-guide/section_glance-install.xml:89(replaceable) ./doc/install-guide/section_glance-install.xml:102(replaceable) ./doc/install-guide/section_glance-install.xml:147(replaceable) ./doc/install-guide/section_glance-install.xml:149(replaceable) ./doc/install-guide/section_glance-install.xml:163(replaceable) ./doc/install-guide/section_glance-install.xml:165(replaceable) ./doc/install-guide/section_glance-install.xml:188(replaceable) ./doc/install-guide/section_glance-install.xml:189(replaceable) ./doc/install-guide/section_glance-install.xml:213(replaceable) ./doc/install-guide/section_glance-install.xml:214(replaceable) ./doc/install-guide/section_glance-install.xml:215(replaceable) ./doc/install-guide/section_cinder-node.xml:113(replaceable) ./doc/install-guide/section_cinder-node.xml:115(replaceable) ./doc/install-guide/section_cinder-node.xml:131(replaceable) ./doc/install-guide/section_cinder-node.xml:132(replaceable) ./doc/install-guide/section_cinder-node.xml:150(replaceable) ./doc/install-guide/section_cinder-node.xml:161(replaceable) ./doc/install-guide/section_cinder-node.xml:170(replaceable) ./doc/install-guide/section_cinder-node.xml:183(replaceable) ./doc/install-guide/section_cinder-node.xml:186(replaceable) ./doc/install-guide/section_cinder-node.xml:202(replaceable) ./doc/install-guide/section_cinder-node.xml:205(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:62(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:64(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:94(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:95(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:112(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:123(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:138(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:294(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:304(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:328(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:333(replaceable) ./doc/install-guide/section_basics-networking-nova.xml:202(replaceable) ./doc/install-guide/section_nova-compute.xml:74(replaceable) ./doc/install-guide/section_nova-compute.xml:75(replaceable) ./doc/install-guide/section_nova-compute.xml:93(replaceable) ./doc/install-guide/section_nova-compute.xml:94(replaceable) ./doc/install-guide/section_nova-compute.xml:106(replaceable) ./doc/install-guide/section_nova-compute.xml:131(replaceable) ./doc/install-guide/section_nova-compute.xml:143(replaceable) ./doc/install-guide/section_nova-compute.xml:151(replaceable) ./doc/install-guide/section_nova-compute.xml:154(replaceable) ./doc/install-guide/section_trove-install.xml:74(replaceable) ./doc/install-guide/section_trove-install.xml:75(replaceable) ./doc/install-guide/section_trove-install.xml:76(replaceable) ./doc/install-guide/section_trove-install.xml:77(replaceable) ./doc/install-guide/section_trove-install.xml:78(replaceable) ./doc/install-guide/section_trove-install.xml:79(replaceable) ./doc/install-guide/section_trove-install.xml:92(replaceable) ./doc/install-guide/section_trove-install.xml:94(replaceable) ./doc/install-guide/section_trove-install.xml:96(replaceable) ./doc/install-guide/section_trove-install.xml:119(replaceable) ./doc/install-guide/section_trove-install.xml:121(replaceable) ./doc/install-guide/section_trove-install.xml:123(replaceable) ./doc/install-guide/section_trove-install.xml:139(replaceable) ./doc/install-guide/section_trove-install.xml:220(replaceable) ./doc/install-guide/section_trove-install.xml:225(replaceable) ./doc/install-guide/section_trove-install.xml:227(replaceable) ./doc/install-guide/section_trove-install.xml:231(replaceable) ./doc/install-guide/section_trove-install.xml:252(replaceable) ./doc/install-guide/section_trove-install.xml:253(replaceable) ./doc/install-guide/section_trove-install.xml:254(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:49(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:50(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:51(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:113(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:126(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:139(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:141(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:171(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:172(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:200(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:215(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:228(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:236(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:255(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:259(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:376(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:386(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:410(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:415(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:55(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:56(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:57(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:81(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:98(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:100(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:133(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:134(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:161(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:179(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:229(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:239(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:250(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:255(replaceable) ./doc/install-guide/section_heat-install.xml:40(replaceable) ./doc/install-guide/section_heat-install.xml:46(replaceable) ./doc/install-guide/section_heat-install.xml:92(replaceable) ./doc/install-guide/section_heat-install.xml:95(replaceable) ./doc/install-guide/section_heat-install.xml:113(replaceable) ./doc/install-guide/section_heat-install.xml:116(replaceable) ./doc/install-guide/section_heat-install.xml:122(replaceable) ./doc/install-guide/section_heat-install.xml:133(replaceable) ./doc/install-guide/section_heat-install.xml:134(replaceable) ./doc/install-guide/section_heat-install.xml:135(replaceable) ./doc/install-guide/section_heat-install.xml:140(replaceable) ./doc/install-guide/section_heat-install.xml:141(replaceable) ./doc/install-guide/section_heat-install.xml:142(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:65(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:67(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:97(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:98(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:115(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:126(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:141(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:269(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:279(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:300(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:305(replaceable) ./doc/install-guide/section_ceilometer-glance.xml:17(replaceable) ./doc/install-guide/section_ceilometer-glance.xml:23(replaceable) ./doc/install-guide/section_keystone-services.xml:47(replaceable) ./doc/install-guide/section_keystone-services.xml:48(replaceable) ./doc/install-guide/section_keystone-services.xml:49(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:97(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:99(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:130(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:131(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:145(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:156(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:165(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:389(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:394(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:399(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:409(replaceable) ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:82(replaceable) ./doc/install-guide/object-storage/section_object-storage-install.xml:101(replaceable) ./doc/install-guide/object-storage/section_object-storage-install.xml:102(replaceable) ./doc/install-guide/object-storage/section_object-storage-install.xml:103(replaceable)
+msgid "controller"
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-install.xml:31(para)
+msgid "Edit <filename>/etc/keystone/keystone.conf</filename> and change the <literal>[database]</literal> section:"
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-install.xml:44(para)
+msgid "By default, the Ubuntu packages create a SQLite database. Delete the <filename>keystone.db</filename> file created in the <filename>/var/lib/keystone/</filename> directory so that it does not get used by mistake:"
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-install.xml:51(para)
+msgid "Use the password that you set previously to log in as root. Create a <literal>keystone</literal> database user:"
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-install.xml:63(para)
+msgid "Create the database tables for the Identity Service:"
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-install.xml:67(para)
+msgid "Define an authorization token to use as a shared secret between the Identity Service and other OpenStack services. Respond to the <package>debconf</package> prompt with the value in the <code>admin_token</code> directive in the <filename>keystone.conf</filename> file. Use the <placeholder-1/> command to generate this password."
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-install.xml:83(para)
+msgid "Later, you can verify that the <filename>/etc/keystone/keystone.conf</filename> file contains the password you have set using <package>debconf</package>: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-install.xml:91(para)
+msgid "If you omit a password (for example by pressing Enter at the <package>debconf</package> prompt, or installing Keystone using the Debconf non-interactive mode) the package generates a random <literal>ADMIN_TOKEN</literal> value."
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-install.xml:97(para)
+msgid "Respond to the prompts to create an administrative tenant:"
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-install.xml:146(para)
+msgid "If this is the first time you have installed the Identity Service, register the Identity Service in the service catalog:"
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-install.xml:160(para)
+msgid "Define an authorization token to use as a shared secret between the Identity Service and other OpenStack services. Use <placeholder-1/> to generate a random token and store it in the configuration file:"
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-install.xml:169(para)
+msgid "For SUSE Linux Enterprise use instead as first command:"
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-install.xml:172(para)
+msgid "Edit <filename>/etc/keystone/keystone.conf</filename> and change the <literal>[DEFAULT]</literal> section, replacing ADMIN_TOKEN with the results of the command:"
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-install.xml:182(para)
+msgid "By default, Keystone uses PKI tokens. Create the signing keys and certificates and restrict access to the generated data:"
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-install.xml:189(para)
+msgid "Configure the log directory. Edit the <filename>/etc/keystone/keystone.conf</filename> file and update the <literal>[DEFAULT]</literal> section:"
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-install.xml:197(para)
+msgid "Restart the Identity Service:"
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-install.xml:201(para)
+msgid "Start the Identity Service and enable it to start when the system boots:"
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-install.xml:207(para)
+msgid "By default, the Identity Service stores expired tokens in the database indefinitely. While potentially useful for auditing in production environments, the accumulation of expired tokens will considerably increase database size and may decrease service performance, particularly in test environments with limited resources. We recommend configuring a periodic task using <systemitem class=\"service\">cron</systemitem> to purge expired tokens hourly."
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-install.xml:217(para)
+msgid "Run the following command to purge expired tokens every hour and log the output to <filename>/var/log/keystone/keystone-tokenflush.log</filename>:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-database.xml:6(title)
+msgid "Database"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-database.xml:7(para)
+msgid "Most OpenStack services require a database to store information. These examples use a MySQL database that runs on the controller node. You must install the MySQL database on the controller node. You must install the MySQL Python library on any additional nodes that access MySQL."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-database.xml:13(para)
+msgid "Most OpenStack services require a database to store information. This guide uses a MySQL database on SUSE Linux Enterprise Server and a compatible database on openSUSE running on the controller node. This compatible database for openSUSE is MariaDB. You must install the MariaDB database on the controller node. You must install the MySQL Python library on any additional nodes that access MySQL or MariaDB."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-database.xml:22(title)
+msgid "Controller setup"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-database.xml:23(para)
+msgid "<phrase os=\"sles\">For SUSE Linux Enterprise Server: </phrase> On the controller node, install the MySQL client and server packages, and the Python library."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-database.xml:27(para)
+msgid "For openSUSE: On the controller node, install the MariaDB client and database server packages, and the MySQL Python library."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-database.xml:34(para)
+msgid "When you install the server package, you are prompted for the root password for the database. Choose a strong password and remember it."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-database.xml:38(para)
+msgid "The MySQL configuration requires some changes to work with OpenStack."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-database.xml:42(para)
+msgid "Edit the <filename>/etc/mysql/my.cnf</filename> file:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-database.xml:44(para)
+msgid "Edit the <filename>/etc/my.cnf</filename> file:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-database.xml:48(para)
+msgid "Under the <literal>[mysqld]</literal> section, set the <literal>bind-address</literal> key to the management IP address of the controller node to enable access by other nodes via the management network:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-database.xml:57(para)
+msgid "Under the <literal>[mysqld]</literal> section, set the following keys to enable InnoDB, UTF-8 character set, and UTF-8 collation by default:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-database.xml:71(para)
+msgid "Restart the MySQL service to apply the changes:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-database.xml:74(para)
+msgid "Start the <phrase os=\"rhel;fedora;centos\">MySQL</phrase><phrase os=\"opensuse;sles\">MariaDB or MySQL</phrase> database server and set it to start automatically when the system boots:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-database.xml:83(para)
+msgid "Finally, you should set a root password for your <phrase os=\"rhel;fedora;centos\">MySQL</phrase><phrase os=\"opensuse;sles\">MariaDB or MySQL</phrase> database. The OpenStack programs that set up databases and tables prompt you for this password if it is set."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-database.xml:89(para)
+msgid "You must delete the anonymous users that are created when the database is first started. Otherwise, database connection problems occur when you follow the instructions in this guide. To do this, use the <placeholder-1/> command. Note that if <placeholder-2/> fails you might need to use <placeholder-3/> first:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-database.xml:98(para)
+msgid "<phrase os=\"rhel;centos;fedora;opensuse;sles\">If you have not already set a root database password, press <keycap>ENTER</keycap> when you are prompted for the password.</phrase> This command presents a number of options for you to secure your database installation. Respond <placeholder-1/> to all prompts unless you have a good reason to do otherwise."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-database.xml:107(title)
+msgid "Node setup"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-database.xml:108(para)
+msgid "On all nodes other than the controller node, install the MySQL Python library:"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-controller.xml:5(title)
+msgid "Configure a Block Storage service controller"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-controller.xml:7(para)
+msgid "This scenario configures OpenStack Block Storage services on the <glossterm baseform=\"controller node\">Controller node</glossterm> and assumes that a second node provides storage through the <systemitem class=\"service\">cinder-volume</systemitem> service."
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-controller.xml:12(para)
+msgid "For instructions on how to configure the second node, see <xref linkend=\"cinder-node\"/>."
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-controller.xml:16(para) ./doc/install-guide/section_cinder-node.xml:10(para)
+msgid "You can configure OpenStack to use various storage systems. This example uses LVM."
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-controller.xml:20(para)
+msgid "Install the appropriate packages for the Block Storage service:"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-controller.xml:27(para)
+msgid "Respond to the prompts for database management, <literal>[keystone_authtoken]</literal> settings, RabbitMQ credentials and API endpoint registration."
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-controller.xml:31(para)
+msgid "Configure Block Storage to use your database."
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-controller.xml:32(para)
+msgid "Run the following command to set <literal>connection</literal> option in the <literal>[database]</literal> section, which is in the <filename>/etc/cinder/cinder.conf</filename> file, replace <replaceable>CINDER_DBPASS</replaceable> with the password for the Block Storage database that you will create in a later step:"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-controller.xml:38(para)
+msgid "In the <filename>/etc/cinder/cinder.conf</filename> file, set the <literal>connection</literal> option in the <literal>[database]</literal> section and replace <replaceable>CINDER_DBPASS</replaceable> with the password for the Block Storage database that you will create in a later step:"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-controller.xml:44(replaceable) ./doc/install-guide/section_cinder-controller.xml:47(replaceable) ./doc/install-guide/section_cinder-controller.xml:59(replaceable) ./doc/install-guide/section_cinder-controller.xml:61(replaceable) ./doc/install-guide/section_cinder-node.xml:183(replaceable) ./doc/install-guide/section_cinder-node.xml:186(replaceable)
+msgid "CINDER_DBPASS"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-controller.xml:48(para) ./doc/install-guide/section_cinder-node.xml:188(para)
+msgid "In some distributions, the <filename>/etc/cinder/cinder.conf</filename> file does not include the <literal>[database]</literal> section header. You must add this section header to the end of the file before you proceed."
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-controller.xml:54(para)
+msgid "Use the password that you set to log in as root to create a <literal>cinder</literal> database:"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-controller.xml:64(para)
+msgid "Create the database tables for the Block Storage service:"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-controller.xml:69(para)
+msgid "Create a <literal>cinder</literal> user."
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-controller.xml:70(para)
+msgid "The Block Storage service uses this user to authenticate with the Identity service."
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-controller.xml:72(para)
+msgid "Use the <literal>service</literal> tenant and give the user the <literal>admin</literal> role:"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-controller.xml:74(replaceable) ./doc/install-guide/section_cinder-controller.xml:95(replaceable) ./doc/install-guide/section_cinder-controller.xml:107(replaceable) ./doc/install-guide/section_cinder-node.xml:125(replaceable) ./doc/install-guide/section_cinder-node.xml:137(replaceable)
+msgid "CINDER_PASS"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-controller.xml:74(replaceable)
+msgid "cinder@example.com"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-controller.xml:78(para)
+msgid "Edit the <filename>/etc/cinder/cinder.conf</filename> configuration file:"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-controller.xml:96(para) ./doc/install-guide/section_cinder-node.xml:126(para)
+msgid "Edit the <filename>/etc/cinder/cinder.conf</filename> configuration file and add this section for keystone credentials:"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-controller.xml:110(para) ./doc/install-guide/section_cinder-controller.xml:134(para) ./doc/install-guide/section_cinder-node.xml:140(para)
+msgid "Configure Block Storage to use the RabbitMQ message broker."
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-controller.xml:112(para)
+msgid "In the <literal>[DEFAULT]</literal> section in the <filename>/etc/cinder/cinder.conf</filename> file, set these configuration keys and replace <replaceable>RABBIT_PASS</replaceable> with the password you chose for RabbitMQ:"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-controller.xml:123(replaceable) ./doc/install-guide/section_cinder-controller.xml:145(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:76(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:80(replaceable) ./doc/install-guide/section_nova-controller.xml:70(replaceable) ./doc/install-guide/section_nova-controller.xml:78(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:198(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:207(replaceable) ./doc/install-guide/section_ceilometer-install.xml:146(replaceable) ./doc/install-guide/section_ceilometer-install.xml:149(replaceable) ./doc/install-guide/section_glance-install.xml:90(replaceable) ./doc/install-guide/section_glance-install.xml:104(replaceable) ./doc/install-guide/section_cinder-node.xml:153(replaceable) ./doc/install-guide/section_cinder-node.xml:174(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:116(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:139(replaceable) ./doc/install-guide/section_nova-compute.xml:115(replaceable) ./doc/install-guide/section_nova-compute.xml:121(replaceable) ./doc/install-guide/section_trove-install.xml:105(replaceable) ./doc/install-guide/section_trove-install.xml:125(replaceable) ./doc/install-guide/section_trove-install.xml:127(replaceable) ./doc/install-guide/section_trove-install.xml:129(replaceable) ./doc/install-guide/section_trove-install.xml:221(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:193(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:216(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:153(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:180(replaceable) ./doc/install-guide/section_heat-install.xml:93(replaceable) ./doc/install-guide/section_heat-install.xml:96(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:119(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:142(replaceable) ./doc/install-guide/section_ceilometer-glance.xml:18(replaceable) ./doc/install-guide/section_ceilometer-glance.xml:24(replaceable) ./doc/install-guide/section_basics-queue.xml:77(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:149(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:158(replaceable)
+msgid "RABBIT_PASS"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-controller.xml:126(para) ./doc/install-guide/section_cinder-node.xml:156(para)
+msgid "Configure Block Storage to use the Qpid message broker:"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-controller.xml:136(para)
+msgid "Replace <replaceable>RABBIT_PASS</replaceable> with the password you chose for RabbitMQ:"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-controller.xml:148(para)
+msgid "Register the Block Storage service with the Identity service so that other OpenStack services can locate it:"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-controller.xml:158(para)
+msgid "Register a service and endpoint for version 2 of the Block Storage service API:"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-controller.xml:168(para) ./doc/install-guide/section_cinder-node.xml:208(para)
+msgid "Restart the Block Storage services with the new settings:"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-controller.xml:174(para) ./doc/install-guide/section_cinder-node.xml:221(para)
+msgid "Start and configure the Block Storage services to start when the system boots:"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml:30(None)
+msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_keep_admin_pass.png'; md5=01af4867c16e458306b8abd78a1fccc9"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml:39(None)
+msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_used_for_remote_db.png'; md5=c6ec966bbfdee18ad87456cf4d44a56f"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml:78(None)
+msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_1_configure-with-dbconfig-yes-no.png'; md5=4e9d7bce27cc6c7bd68ce8622c80b60f"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml:87(None)
+msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_2_db-types.png'; md5=a77beb7e13b487cf79716c2140f258c2"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml:96(None)
+msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_3_connection_method.png'; md5=6cc592e5dd5ea404ad7aad98b37a71f6"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml:105(None)
+msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_4_mysql_root_password.png'; md5=873ec338742e37305583e9e692bcfdc6"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml:114(None)
+msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_5_mysql_app_password.png'; md5=3651970770d05892f21d1b5741afbee6"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml:123(None)
+msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_6_mysql_app_password_confirm.png'; md5=060cc90aaf6f6fd5cea718064829c1b1"
+msgstr ""
+
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml:6(title)
+msgid "Configure the database with dbconfig-common"
+msgstr ""
+
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml:7(para)
+msgid "The <package>dbconfig-common</package> package provides a standard Debian interface that enables you to configure Debian database parameters. It includes localized prompts for many languages and it supports the OpenStack database back ends: SQLite, MySQL, and PostgreSQL."
+msgstr ""
+
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml:12(para)
+msgid "By default, the <package>dbconfig-common</package> package configures the OpenStack services to use SQLite3. So if you use <package>debconf</package> in non-interactive mode and without pre-seeding, the OpenStack services that you install use SQLite3."
+msgstr ""
+
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml:17(para)
+msgid "By default, <package>dbconfig-common</package> does not provide access to database servers over a network. If you want the <package>dbconfig-common</package> package to prompt for remote database servers that are accessed over a network and not through a UNIX socket file, reconfigure it, as follows:"
+msgstr ""
+
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml:23(para)
+msgid "These screens appear when you re-configure the <package>dbconfig-common</package> package:"
+msgstr ""
+
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml:43(para)
+msgid "Unlike other <package>debconf</package> prompts, you cannot pre-seed the responses for the <package>dbconfig-common</package> prompts by using <placeholder-1/>. Instead, you must create a file in <filename>/etc/dbconfig-common</filename>. For example, you might create a keystone configuration file for <package>dbconfig-common</package> that is located in <filename>/etc/dbconfig-common/keystone.conf</filename>, as follows:"
+msgstr ""
+
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml:66(para)
+msgid "After you create this file, run this command:"
+msgstr ""
+
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml:68(para)
+msgid "The Identity Service is installed with MySQL as the database back end, <literal>keystonedb</literal> as database name, and the localhost socket file."
+msgstr ""
+
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml:71(para)
+msgid "The <package>cinder-common</package> package displays these screens:"
+msgstr ""
+
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml:127(para)
+msgid "By default in Debian, the MySQL server is only accessible from localhost using the socket file, or 127.0.0.1. To access it over network, users must edit <filename>/etc/mysql/my.cnf</filename> and edit the <literal>mysql.user</literal> table. To do so, Debian provides a helper script located in the <package>openstack-deploy</package> package. To use it, install the package and run:"
+msgstr ""
+
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml:134(para)
+msgid "Alternatively, if you do not want to install this package, run this script to enable remote root access:"
+msgstr ""
+
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml:157(para)
+msgid "You must enable remote access before you install OpenStack services on multiple nodes."
+msgstr ""
+
+#: ./doc/install-guide/ch_launch-instance.xml:5(title)
+msgid "Launch an instance"
+msgstr ""
+
+#: ./doc/install-guide/ch_launch-instance.xml:6(para)
+msgid "An instance is a VM that OpenStack provisions on a compute node. This guide shows you how to launch a minimal instance using the <glossterm>CirrOS</glossterm> image that you added to your environment in the <xref linkend=\"ch_glance\"/> chapter. In these steps, you use the command-line interface (CLI) on your controller node or any system with the appropriate OpenStack client libraries. To use the dashboard, see the <link href=\"http://docs.openstack.org/user-guide/content/ch_dashboard.html\"><citetitle>OpenStack User Guide</citetitle></link>."
+msgstr ""
+
+#: ./doc/install-guide/ch_launch-instance.xml:15(para)
+msgid "Launch an instance using <link linkend=\"launch-instance-neutron\">OpenStack Networking (neutron) </link> or <link linkend=\"launch-instance-nova\">legacy networking (nova-network) </link>. For more information, see the <link href=\"http://docs.openstack.org/user-guide/content/cli_launch_instances.html\"><citetitle>OpenStack User Guide</citetitle></link>."
+msgstr ""
+
+#: ./doc/install-guide/ch_launch-instance.xml:25(para)
+msgid "These steps reference example components created in previous chapters. You must adjust certain values such as IP addresses to match your environment."
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-swift.xml:6(title)
+msgid "Configure the Object Storage service for Telemetry"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-swift.xml:9(para)
+msgid "To retrieve object store statistics, the Telemetry service needs access to Object Storage with the <literal>ResellerAdmin</literal> role. Give this role to your <literal>os_username</literal> user for the <literal>os_tenant_name</literal> tenant:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-swift.xml:23(replaceable)
+msgid "462fa46c13fd4798a95a3bfbe27b5e54"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-swift.xml:26(para)
+msgid "You must also add the Telemetry middleware to Object Storage to handle incoming and outgoing traffic. Add these lines to the <filename>/etc/swift/proxy-server.conf</filename> file:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-swift.xml:35(para)
+msgid "Add <literal>ceilometer</literal> to the <literal>pipeline</literal> parameter of that same file:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-swift.xml:41(para) ./doc/install-guide/section_ceilometer-nova.xml:137(para) ./doc/install-guide/section_heat-install.xml:180(para)
+msgid "Restart the service with its new settings:"
+msgstr ""
+
 #: ./doc/install-guide/section_keystone-users.xml:5(title)
 msgid "Define users, tenants, and roles"
 msgstr ""
@@ -45,7 +511,7 @@ msgstr ""
 msgid "Create the <literal>admin</literal> user:"
 msgstr ""
 
-#: ./doc/install-guide/section_keystone-users.xml:58(replaceable) ./doc/install-guide/section_trove-install.xml:143(replaceable) ./doc/install-guide/section_trove-install.xml:172(replaceable) ./doc/install-guide/section_trove-install.xml:223(replaceable) ./doc/install-guide/section_trove-install.xml:229(replaceable) ./doc/install-guide/section_keystone-verify.xml:25(replaceable) ./doc/install-guide/section_keystone-verify.xml:35(replaceable) ./doc/install-guide/section_keystone-verify.xml:49(replaceable)
+#: ./doc/install-guide/section_keystone-users.xml:58(replaceable) ./doc/install-guide/section_keystone-verify.xml:25(replaceable) ./doc/install-guide/section_keystone-verify.xml:35(replaceable) ./doc/install-guide/section_keystone-verify.xml:49(replaceable) ./doc/install-guide/section_trove-install.xml:143(replaceable) ./doc/install-guide/section_trove-install.xml:172(replaceable) ./doc/install-guide/section_trove-install.xml:223(replaceable) ./doc/install-guide/section_trove-install.xml:229(replaceable)
 msgid "ADMIN_PASS"
 msgstr ""
 
@@ -125,6 +591,588 @@ msgstr ""
 msgid "Create the <literal>service</literal> tenant:"
 msgstr ""
 
+#: ./doc/install-guide/section_ceilometer-nova.xml:7(title)
+msgid "Install the Compute agent for Telemetry"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-nova.xml:9(para)
+msgid "Telemetry provides an API service that provides a collector and a range of disparate agents. This procedure details how to install the agent that runs on the compute node."
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-nova.xml:14(para)
+msgid "Install the Telemetry service on the compute node:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-nova.xml:20(para)
+msgid "Set the following options in the <filename>/etc/nova/nova.conf</filename> file:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-nova.xml:30(para)
+msgid "The <option>notification_driver</option> option is a multi valued option, which <application>openstack-config</application> cannot set properly. See <xref linkend=\"basics-packages\"/>."
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-nova.xml:36(para)
+msgid "Edit the <filename>/etc/nova/nova.conf</filename> file and add the following lines to the <literal>[DEFAULT]</literal> section:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-nova.xml:53(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:378(para) ./doc/install-guide/section_nova-compute.xml:208(para)
+msgid "Restart the Compute service:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-nova.xml:58(para)
+msgid "You must set the secret key that you defined previously. The Telemetry service nodes share this key as a shared secret:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-nova.xml:62(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:70(replaceable) ./doc/install-guide/section_ceilometer-install.xml:140(replaceable)
+msgid "CEILOMETER_TOKEN"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-nova.xml:63(para)
+msgid "Edit the <filename>/etc/ceilometer/ceilometer.conf</filename> file and change these lines in the <literal>[publisher]</literal> section. Replace <replaceable>CEILOMETER_TOKEN</replaceable> with the ceilometer token that you created previously:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-nova.xml:74(para) ./doc/install-guide/section_ceilometer-install.xml:144(para)
+msgid "Configure the RabbitMQ access:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-nova.xml:77(para) ./doc/install-guide/section_ceilometer-nova.xml:130(para) ./doc/install-guide/section_ceilometer-install.xml:147(para) ./doc/install-guide/section_ceilometer-install.xml:166(para)
+msgid "Edit the <filename>/etc/ceilometer/ceilometer.conf</filename> file and update the <literal>[DEFAULT]</literal> section:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-nova.xml:84(para)
+msgid "Configure the QPid access:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-nova.xml:89(para)
+msgid "Add the Identity service credentials:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-nova.xml:99(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:105(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:118(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:125(replaceable) ./doc/install-guide/section_ceilometer-install.xml:177(replaceable) ./doc/install-guide/section_ceilometer-install.xml:206(replaceable) ./doc/install-guide/section_ceilometer-install.xml:214(replaceable) ./doc/install-guide/section_ceilometer-install.xml:226(replaceable) ./doc/install-guide/section_ceilometer-install.xml:233(replaceable)
+msgid "CEILOMETER_PASS"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-nova.xml:108(para) ./doc/install-guide/section_ceilometer-install.xml:215(para)
+msgid "Edit the <filename>/etc/ceilometer/ceilometer.conf</filename> file and change the <literal>[keystone_authtoken]</literal> section:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-nova.xml:119(para) ./doc/install-guide/section_ceilometer-install.xml:227(para)
+msgid "Also set the <literal>[service_credentials]</literal> section:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-nova.xml:129(para) ./doc/install-guide/section_ceilometer-install.xml:165(para)
+msgid "Configure the log directory."
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-nova.xml:141(para)
+msgid "Start the service and configure it to start when the system boots:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-controller.xml:5(title)
+msgid "Install Compute controller services"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-controller.xml:6(para)
+msgid "Compute is a collection of services that enable you to launch virtual machine instances. You can configure these services to run on separate nodes or the same node. In this guide, most services run on the controller node and the service that launches virtual machines runs on a dedicated compute node. This section shows you how to install and configure these services on the controller node."
+msgstr ""
+
+#: ./doc/install-guide/section_nova-controller.xml:15(para)
+msgid "Install the Compute packages necessary for the controller node."
+msgstr ""
+
+#: ./doc/install-guide/section_nova-controller.xml:27(para)
+msgid "Respond to the prompts for <link linkend=\"debconf-dbconfig-common\">database management</link>, <link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> settings</link>, <link linkend=\"debconf-rabbitqm\">RabbitMQ credentials</link>, and <link linkend=\"debconf-api-endpoints\">API endpoint</link> registration. The <placeholder-1/> command runs automatically."
+msgstr ""
+
+#: ./doc/install-guide/section_nova-controller.xml:38(para)
+msgid "Compute stores information in a database. In this guide, we use a MySQL database on the controller node. Configure Compute with the database location and credentials. Replace <replaceable>NOVA_DBPASS</replaceable> with the password for the database that you will create in a later step."
+msgstr ""
+
+#: ./doc/install-guide/section_nova-controller.xml:44(replaceable) ./doc/install-guide/section_nova-controller.xml:51(replaceable) ./doc/install-guide/section_nova-controller.xml:119(replaceable) ./doc/install-guide/section_nova-controller.xml:121(replaceable) ./doc/install-guide/section_nova-compute.xml:72(replaceable)
+msgid "NOVA_DBPASS"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-controller.xml:45(para)
+msgid "Edit the <literal>[database]</literal> section in the <filename>/etc/nova/nova.conf</filename> file, adding it if necessary, to modify this key:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-controller.xml:55(para)
+msgid "Set these configuration keys to configure Compute to use the Qpid message broker:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-controller.xml:62(para) ./doc/install-guide/section_nova-compute.xml:107(para)
+msgid "Configure the Compute service to use the RabbitMQ message broker by setting these configuration keys in the <literal>[DEFAULT]</literal> configuration group of the <filename>/etc/nova/nova.conf</filename> file:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-controller.xml:73(para)
+msgid "Set these configuration keys to configure Compute to use the RabbitMQ message broker:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-controller.xml:81(para)
+msgid "Set the <option>my_ip</option>, <option>vncserver_listen</option>, and <option>vncserver_proxyclient_address</option> configuration options to the management interface IP address of the controller node:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-controller.xml:89(para)
+msgid "Edit the <filename>/etc/nova/nova.conf</filename> file and add these lines to the <literal>[DEFAULT]</literal> section:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-controller.xml:92(para)
+msgid "In Debian, the <package>debconf</package> package automatically sets up <literal>my_ip</literal> parameter but you must edit the <filename>/etc/nova/nova.conf</filename> file to configure the <option>vncserver_listen</option> and <option>vncserver_proxyclient_address</option> options, which appear at the end of the file:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-controller.xml:107(para)
+msgid "By default, the Ubuntu packages create an SQLite database. Delete the <filename>nova.sqlite</filename> file created in the <filename>/var/lib/nova/</filename> directory so that it does not get used by mistake:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-controller.xml:114(para)
+msgid "Use the password you created previously to log in as root. Create a <literal>nova</literal> database user:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-controller.xml:124(para)
+msgid "Create the Compute service tables:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-controller.xml:128(para)
+msgid "Create a <literal>nova</literal> user that Compute uses to authenticate with the Identity Service. Use the <literal>service</literal> tenant and give the user the <literal>admin</literal> role:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-controller.xml:132(replaceable) ./doc/install-guide/section_nova-controller.xml:146(replaceable) ./doc/install-guide/section_nova-controller.xml:166(replaceable) ./doc/install-guide/section_nova-compute.xml:80(replaceable) ./doc/install-guide/section_nova-compute.xml:99(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:234(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:258(replaceable)
+msgid "NOVA_PASS"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-controller.xml:132(replaceable)
+msgid "nova@example.com"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-controller.xml:136(para)
+msgid "Configure Compute to use these credentials with the Identity Service running on the controller. Replace <replaceable>NOVA_PASS</replaceable> with your Compute password."
+msgstr ""
+
+#: ./doc/install-guide/section_nova-controller.xml:147(para)
+msgid "Edit the <literal>[DEFAULT]</literal> section in the <filename>/etc/nova/nova.conf</filename> file to add this key:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-controller.xml:155(para)
+msgid "Add these keys to the <literal>[keystone_authtoken]</literal> section:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-controller.xml:169(para)
+msgid "You must register Compute with the Identity Service so that other OpenStack services can locate it. Register the service and specify the endpoint:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-controller.xml:182(para)
+msgid "Start Compute services and configure them to start when the system boots:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-controller.xml:185(para)
+msgid "Restart Compute services:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-controller.xml:206(para)
+msgid "To verify your configuration, list available images:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-cinder.xml:7(title)
+msgid "Add the Block Storage service agent for Telemetry"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-cinder.xml:10(para)
+msgid "To retrieve volume samples, you must configure the Block Storage service to send notifications to the bus."
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-cinder.xml:13(para)
+msgid "Edit <filename>/etc/cinder/cinder.conf</filename> and add in the <literal>[DEFAULT]</literal> section on the controller and volume nodes:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-cinder.xml:19(para)
+msgid "Run the following commands on the controller and volume nodes:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-cinder.xml:26(para)
+msgid "Restart the Block Storage services with their new settings."
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-cinder.xml:28(para)
+msgid "On the controller node:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-cinder.xml:33(para)
+msgid "On the volume node:"
+msgstr ""
+
+#: ./doc/install-guide/section_glance-verify.xml:5(title)
+msgid "Verify the Image Service installation"
+msgstr ""
+
+#: ./doc/install-guide/section_glance-verify.xml:6(para)
+msgid "To test the Image Service installation, download at least one virtual machine image that is known to work with OpenStack. For example, CirrOS is a small test image that is often used for testing OpenStack deployments (<link href=\"http://download.cirros-cloud.net/\">CirrOS downloads</link>). This walk through uses the 64-bit CirrOS QCOW2 image."
+msgstr ""
+
+#: ./doc/install-guide/section_glance-verify.xml:13(para)
+msgid "For more information about how to download and build images, see <link href=\"http://docs.openstack.org/image-guide/content/index.html\"><citetitle>OpenStack Virtual Machine Image Guide</citetitle></link>. For information about how to manage images, see the <link href=\"http://docs.openstack.org/user-guide/content/index.html\"><citetitle>OpenStack User Guide</citetitle></link>."
+msgstr ""
+
+#: ./doc/install-guide/section_glance-verify.xml:24(para)
+msgid "Download the image into a dedicated directory using <placeholder-1/> or <placeholder-2/>:"
+msgstr ""
+
+#: ./doc/install-guide/section_glance-verify.xml:32(para)
+msgid "Upload the image to the Image Service:"
+msgstr ""
+
+#: ./doc/install-guide/section_glance-verify.xml:33(replaceable) ./doc/install-guide/section_glance-verify.xml:38(replaceable)
+msgid "IMAGELABEL"
+msgstr ""
+
+#: ./doc/install-guide/section_glance-verify.xml:33(replaceable) ./doc/install-guide/section_glance-verify.xml:45(replaceable)
+msgid "FILEFORMAT"
+msgstr ""
+
+#: ./doc/install-guide/section_glance-verify.xml:34(replaceable) ./doc/install-guide/section_glance-verify.xml:65(replaceable)
+msgid "CONTAINERFORMAT"
+msgstr ""
+
+#: ./doc/install-guide/section_glance-verify.xml:34(replaceable) ./doc/install-guide/section_glance-verify.xml:86(replaceable)
+msgid "ACCESSVALUE"
+msgstr ""
+
+#: ./doc/install-guide/section_glance-verify.xml:34(replaceable) ./doc/install-guide/section_glance-verify.xml:101(replaceable)
+msgid "IMAGEFILE"
+msgstr ""
+
+#: ./doc/install-guide/section_glance-verify.xml:35(para)
+msgid "Where:"
+msgstr ""
+
+#: ./doc/install-guide/section_glance-verify.xml:40(para)
+msgid "Arbitrary label. The name by which users refer to the image."
+msgstr ""
+
+#: ./doc/install-guide/section_glance-verify.xml:47(para)
+msgid "Specifies the format of the image file. Valid formats include <literal>qcow2</literal>, <literal>raw</literal>, <literal>vhd</literal>, <literal>vmdk</literal>, <literal>vdi</literal>, <literal>iso</literal>, <literal>aki</literal>, <literal>ari</literal>, and <literal>ami</literal>."
+msgstr ""
+
+#: ./doc/install-guide/section_glance-verify.xml:58(para)
+msgid "You can verify the format using the <placeholder-1/> command: <placeholder-2/>"
+msgstr ""
+
+#: ./doc/install-guide/section_glance-verify.xml:67(para)
+msgid "Specifies the container format. Valid formats include: <literal>bare</literal>, <literal>ovf</literal>, <literal>aki</literal>, <literal>ari</literal> and <literal>ami</literal>."
+msgstr ""
+
+#: ./doc/install-guide/section_glance-verify.xml:73(para)
+msgid "Specify <literal>bare</literal> to indicate that the image file is not in a file format that contains metadata about the virtual machine. Although this field is currently required, it is not actually used by any of the OpenStack services and has no effect on system behavior. Because the value is not used anywhere, it is safe to always specify <literal>bare</literal> as the container format."
+msgstr ""
+
+#: ./doc/install-guide/section_glance-verify.xml:90(para)
+msgid "true - All users can view and use the image."
+msgstr ""
+
+#: ./doc/install-guide/section_glance-verify.xml:94(para)
+msgid "false - Only administrators can view and use the image."
+msgstr ""
+
+#: ./doc/install-guide/section_glance-verify.xml:88(para)
+msgid "Specifies image access: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/install-guide/section_glance-verify.xml:103(para)
+msgid "Specifies the name of your downloaded image file."
+msgstr ""
+
+#: ./doc/install-guide/section_glance-verify.xml:108(para) ./doc/install-guide/section_glance-verify.xml:157(para)
+msgid "For example:"
+msgstr ""
+
+#: ./doc/install-guide/section_glance-verify.xml:133(para)
+msgid "Because the returned image ID is generated dynamically, your deployment generates a different ID than the one shown in this example."
+msgstr ""
+
+#: ./doc/install-guide/section_glance-verify.xml:139(para)
+msgid "Confirm that the image was uploaded and display its attributes:"
+msgstr ""
+
+#: ./doc/install-guide/section_glance-verify.xml:149(para)
+msgid "You can now remove the locally downloaded image, since it is stored and available through the Image Service."
+msgstr ""
+
+#: ./doc/install-guide/section_glance-verify.xml:156(para)
+msgid "Alternatively, the upload to the Image Service can be done without having to use local disk space to store the file, by use of the <parameter>--copy-from</parameter> parameter."
+msgstr ""
+
+#: ./doc/install-guide/ch_debconf.xml:6(title)
+msgid "Configure OpenStack with debconf"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_basics-networking-neutron.xml:29(None) ./doc/install-guide/ch_overview.xml:98(None)
+msgid "@@image: 'figures/installguide_arch-neutron.png'; md5=9b3d2f2e5f9d88d198511ecbca829c6d"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:6(title) ./doc/install-guide/ch_networking.xml:20(title)
+msgid "OpenStack Networking (neutron)"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:7(para)
+msgid "The example architecture with OpenStack Networking (neutron) requires one controller node, one network node, and at least one compute node. The controller node contains one network interface on the <glossterm>management network</glossterm>. The network node contains one network interface on the management network, one on the <glossterm>instance tunnels network</glossterm>, and one on the <glossterm>external network</glossterm>. The compute node contains one network interface on the management network and one on the instance tunnels network."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:17(para)
+msgid "Network interface names vary by distribution. Traditionally, interfaces use \"eth\" followed by a sequential number. To cover all variations, this guide simply refers to the first interface as the interface with the lowest number, the second interface as the interface with the middle number, and the third interface as the interface with the highest number."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:25(title) ./doc/install-guide/ch_overview.xml:94(title)
+msgid "Three-node architecture with OpenStack Networking (neutron)"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:33(para) ./doc/install-guide/section_basics-networking-nova.xml:29(para)
+msgid "Unless you intend to use the exact configuration provided in this example architecture, you must modify the networks in this procedure to match your environment. Also, each node must resolve the other nodes by name in addition to IP address. For example, the <replaceable>controller</replaceable> name must resolve to <literal>10.0.0.11</literal>, the IP address of the management interface on the controller node."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:41(para) ./doc/install-guide/section_basics-networking-nova.xml:37(para)
+msgid "Reconfiguring network interfaces will interrupt network connectivity. We recommend using a local terminal session for these procedures."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:46(title) ./doc/install-guide/section_basics-networking-nova.xml:42(title)
+msgid "Controller node"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:48(title) ./doc/install-guide/section_basics-networking-neutron.xml:83(title) ./doc/install-guide/section_basics-networking-neutron.xml:165(title) ./doc/install-guide/section_basics-networking-nova.xml:44(title) ./doc/install-guide/section_basics-networking-nova.xml:76(title)
+msgid "To configure networking:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:50(para) ./doc/install-guide/section_basics-networking-neutron.xml:85(para) ./doc/install-guide/section_basics-networking-neutron.xml:167(para) ./doc/install-guide/section_basics-networking-nova.xml:46(para) ./doc/install-guide/section_basics-networking-nova.xml:78(para)
+msgid "Configure the first interface as the management interface:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:51(para) ./doc/install-guide/section_basics-networking-nova.xml:47(para)
+msgid "IP address: 10.0.0.11"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:52(para) ./doc/install-guide/section_basics-networking-neutron.xml:87(para) ./doc/install-guide/section_basics-networking-neutron.xml:94(para) ./doc/install-guide/section_basics-networking-neutron.xml:169(para) ./doc/install-guide/section_basics-networking-neutron.xml:180(para) ./doc/install-guide/section_basics-networking-nova.xml:48(para) ./doc/install-guide/section_basics-networking-nova.xml:80(para)
+msgid "Network mask: 255.255.255.0 (or /24)"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:53(para) ./doc/install-guide/section_basics-networking-neutron.xml:88(para) ./doc/install-guide/section_basics-networking-neutron.xml:170(para) ./doc/install-guide/section_basics-networking-nova.xml:49(para) ./doc/install-guide/section_basics-networking-nova.xml:81(para)
+msgid "Default gateway: 10.0.0.1"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:57(title) ./doc/install-guide/section_basics-networking-neutron.xml:140(title) ./doc/install-guide/section_basics-networking-neutron.xml:188(title) ./doc/install-guide/section_basics-networking-nova.xml:53(title) ./doc/install-guide/section_basics-networking-nova.xml:131(title)
+msgid "To configure name resolution:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:59(para) ./doc/install-guide/section_basics-networking-nova.xml:55(para)
+msgid "Set the hostname of the node to <code><replaceable>controller</replaceable></code>."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:63(para) ./doc/install-guide/section_basics-networking-neutron.xml:145(para) ./doc/install-guide/section_basics-networking-neutron.xml:193(para) ./doc/install-guide/section_basics-networking-nova.xml:59(para) ./doc/install-guide/section_basics-networking-nova.xml:136(para)
+msgid "Edit the <filename>/etc/hosts</filename> file to contain the following:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:74(para) ./doc/install-guide/section_basics-networking-neutron.xml:156(para) ./doc/install-guide/section_basics-networking-neutron.xml:204(para) ./doc/install-guide/section_basics-networking-nova.xml:67(para) ./doc/install-guide/section_basics-networking-nova.xml:144(para)
+msgid "You must remove or comment the line beginning with <literal>127.0.1.1</literal>."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:81(title)
+msgid "Network node"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:86(para)
+msgid "IP address: 10.0.0.21"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:91(para) ./doc/install-guide/section_basics-networking-neutron.xml:177(para)
+msgid "Configure the second interface as the instance tunnels interface:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:93(para)
+msgid "IP address: 10.0.1.21"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:97(para)
+msgid "The external interface uses a special configuration without an IP address assigned to it. Configure the third interface as the external interface:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:100(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:458(para)
+msgid "Replace <replaceable>INTERFACE_NAME</replaceable> with the actual interface name. For example, <emphasis>eth2</emphasis> or <emphasis>ens256</emphasis>."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:105(para) ./doc/install-guide/section_basics-networking-nova.xml:96(para)
+msgid "Edit the <filename>/etc/network/interfaces</filename> file to contain the following:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:108(replaceable) ./doc/install-guide/section_basics-networking-neutron.xml:109(replaceable) ./doc/install-guide/section_basics-networking-neutron.xml:119(replaceable) ./doc/install-guide/section_nova-networking-compute-node.xml:50(replaceable) ./doc/install-guide/section_nova-networking-compute-node.xml:52(replaceable) ./doc/install-guide/section_nova-networking-compute-node.xml:73(replaceable) ./doc/install-guide/section_nova-networking-compute-node.xml:74(replaceable) ./doc/install-guide/section_basics-networking-nova.xml:99(replaceable) ./doc/install-guide/section_basics-networking-nova.xml:100(replaceable) ./doc/install-guide/section_basics-networking-nova.xml:110(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:461(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:469(replaceable)
+msgid "INTERFACE_NAME"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:114(para) ./doc/install-guide/section_basics-networking-nova.xml:105(para)
+msgid "Edit the <filename>/etc/sysconfig/network-scripts/ifcfg-<replaceable>INTERFACE_NAME</replaceable></filename> file to contain the following:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:117(para) ./doc/install-guide/section_basics-networking-nova.xml:108(para)
+msgid "Do not change the <literal>HWADDR</literal> and <literal>UUID</literal> keys."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:125(para) ./doc/install-guide/section_basics-networking-nova.xml:116(para)
+msgid "Edit the <filename>/etc/sysconfig/network/ifcfg-<replaceable>INTERFACE_NAME</replaceable></filename> file to contain the following:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:134(para) ./doc/install-guide/section_basics-networking-nova.xml:125(para)
+msgid "Restart networking:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:142(para)
+msgid "Set the hostname of the node to <code>network</code>."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:163(title) ./doc/install-guide/section_basics-networking-nova.xml:74(title)
+msgid "Compute node"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:168(para) ./doc/install-guide/section_basics-networking-nova.xml:79(para)
+msgid "IP address: 10.0.0.31"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:172(para) ./doc/install-guide/section_basics-networking-nova.xml:83(para)
+msgid "Additional compute nodes should use 10.0.0.32, 10.0.0.33, and so on."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:179(para)
+msgid "IP address: 10.0.1.31"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:182(para)
+msgid "Additional compute nodes should use 10.0.1.32, 10.0.1.33, and so on."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:190(para) ./doc/install-guide/section_basics-networking-nova.xml:133(para)
+msgid "Set the hostname of the node to <code>compute1</code>."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:211(title) ./doc/install-guide/section_neutron-initial-networks.xml:228(title) ./doc/install-guide/section_basics-networking-nova.xml:151(title)
+msgid "Verify connectivity"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:212(para) ./doc/install-guide/section_basics-networking-nova.xml:152(para)
+msgid "We recommend that you verify network connectivity to the internet and among the nodes before proceeding further."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:216(para) ./doc/install-guide/section_basics-networking-nova.xml:156(para)
+msgid "From the <emphasis>controller</emphasis> node, <placeholder-1/> a site on the internet:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:230(para)
+msgid "From the <emphasis>controller</emphasis> node, <placeholder-1/> the management interface on the <emphasis>network</emphasis> node:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:233(replaceable)
+msgid "network"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:245(para) ./doc/install-guide/section_basics-networking-nova.xml:170(para)
+msgid "From the <emphasis>controller</emphasis> node, <placeholder-1/> the management interface on the <emphasis>compute</emphasis> node:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:248(replaceable) ./doc/install-guide/section_basics-networking-nova.xml:173(replaceable)
+msgid "compute1"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:260(para)
+msgid "From the <emphasis>network</emphasis> node, <placeholder-1/> a site on the internet:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:274(para)
+msgid "From the <emphasis>network</emphasis> node, <placeholder-1/> the management interface on the <emphasis>controller</emphasis> node:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:289(para)
+msgid "From the <emphasis>network</emphasis> node, <placeholder-1/> the instance tunnels interface on the <emphasis>compute</emphasis> node:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:304(para) ./doc/install-guide/section_basics-networking-nova.xml:185(para)
+msgid "From the <emphasis>compute</emphasis> node, <placeholder-1/> a site on the internet:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:318(para) ./doc/install-guide/section_basics-networking-nova.xml:199(para)
+msgid "From the <emphasis>compute</emphasis> node, <placeholder-1/> the management interface on the <emphasis>controller</emphasis> node:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml:333(para)
+msgid "From the <emphasis>compute</emphasis> node, <placeholder-1/> the instance tunnels interface on the <emphasis>network</emphasis> node:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-passwords.xml:6(title)
+msgid "Passwords"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-passwords.xml:7(para)
+msgid "The various OpenStack services and the required software like the database and the messaging server have to be password protected. You use these passwords when configuring a service and then again to access the service. You have to choose a password while configuring the service and later remember to use the same password when accessing it. Optionally, you can generate random passwords with the <application>pwgen</application> program. Or, to create passwords one at a time, use the output of this command repeatedly: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-passwords.xml:17(para)
+msgid "This guide uses the convention that <literal><replaceable>SERVICE_PASS</replaceable></literal> is the password to access the service <literal>SERVICE</literal> and <literal><replaceable>SERVICE_DBPASS</replaceable></literal> is the database password used by the service SERVICE to access the database."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-passwords.xml:24(para)
+msgid "The complete list of passwords you need to define in this guide are: <table rules=\"all\"><caption>Passwords</caption><thead><tr><th>Password name</th><th>Description</th></tr></thead><tbody><tr><td>Database password (no variable used)</td><td>Root password for the database</td></tr><tr os=\"ubuntu;opensuse;sles\"><td><literal><replaceable>RABBIT_PASS</replaceable></literal></td><td>Password of user guest of RabbitMQ</td></tr><tr><td><literal><replaceable>KEYSTONE_DBPASS</replaceable></literal></td><td>Database password of Identity service</td></tr><tr><td><literal><replaceable>DEMO_PASS</replaceable></literal></td><td>Password of user <literal>demo</literal></td></tr><tr><td><literal><replaceable>ADMIN_PASS</replaceable></literal></td><td>Password of user <literal>admin</literal></td></tr><tr><td><literal><replaceable>GLANCE_DBPASS</replaceable></literal></td><td>Database password for Image Service</td></tr><tr><td><literal><replaceable>GLANCE_PASS</replaceable></literal></td><td>Password of Image Service user <literal>glance</literal></td></tr><tr><td><literal><replaceable>NOVA_DBPASS</replaceable></literal></td><td>Database password for Compute service</td></tr><tr><td><literal><replaceable>NOVA_PASS</replaceable></literal></td><td>Password of Compute service user <literal>nova</literal></td></tr><tr><td><literal><replaceable>DASH_DBPASS</replaceable></literal></td><td>Database password for the dashboard</td></tr><tr><td><literal><replaceable>CINDER_DBPASS</replaceable></literal></td><td>Database password for the Block Storage service</td></tr><tr><td><literal><replaceable>CINDER_PASS</replaceable></literal></td><td>Password of Block Storage service user <literal>cinder</literal></td></tr><tr><td><literal><replaceable>NEUTRON_DBPASS</replaceable></literal></td><td>Database password for the Networking service</td></tr><tr><td><literal><replaceable>NEUTRON_PASS</replaceable></literal></td><td>Password of Networking service user <literal>neutron</literal></td></tr><tr><td><literal><replaceable>HEAT_DBPASS</replaceable></literal></td><td>Database password for the Orchestration service</td></tr><tr><td><literal><replaceable>HEAT_PASS</replaceable></literal></td><td>Password of Orchestration service user <literal>heat</literal></td></tr><tr><td><literal><replaceable>CEILOMETER_DBPASS</replaceable></literal></td><td>Database password for the Telemetry service</td></tr><tr><td><literal><replaceable>CEILOMETER_PASS</replaceable></literal></td><td>Password of Telemetry service user <literal>ceilometer</literal></td></tr><tr><td><literal><replaceable>TROVE_DBPASS</replaceable></literal></td><td>Database password of Database service</td></tr><tr><td><literal><replaceable>TROVE_PASS</replaceable></literal></td><td>Password of Database Service user <literal>trove</literal></td></tr></tbody></table>"
+msgstr ""
+
+#: ./doc/install-guide/ch_keystone.xml:6(title)
+msgid "Configure the Identity Service"
+msgstr ""
+
+#: ./doc/install-guide/ch_swift.xml:6(title)
+msgid "Add Object Storage"
+msgstr ""
+
+#: ./doc/install-guide/ch_swift.xml:7(para)
+msgid "The OpenStack Object Storage services work together to provide object storage and retrieval through a REST API. For this example architecture, you must have already installed the Identity Service, also known as Keystone."
+msgstr ""
+
+#: ./doc/install-guide/ch_swift.xml:30(title) ./doc/install-guide/ch_horizon.xml:38(title) ./doc/install-guide/ch_heat.xml:14(title) ./doc/install-guide/ch_ceilometer.xml:18(title) ./doc/install-guide/ch_cinder.xml:20(title) ./doc/install-guide/ch_networking.xml:37(title)
+msgid "Next steps"
+msgstr ""
+
+#: ./doc/install-guide/ch_swift.xml:31(para)
+msgid "Your OpenStack environment now includes Object Storage. You can <link linkend=\"launch-instance\">launch an instance</link> or add more services to your environment in the following chapters."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-concepts.xml:6(title)
+msgid "Networking concepts"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-concepts.xml:7(para)
+msgid "OpenStack Networking (neutron) manages all of the networking facets for the Virtual Networking Infrastructure (VNI) and the access layer aspects of the Physical Networking Infrastructure (PNI) in your OpenStack environment. OpenStack Networking allows tenants to create advanced virtual network topologies including services such as <glossterm baseform=\"firewall\">firewalls</glossterm>, <glossterm baseform=\"load balancer\">load balancers</glossterm>, and <glossterm baseform=\"virtual private network (VPN)\"> virtual private networks (VPNs)</glossterm>."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-concepts.xml:16(para)
+msgid "Networking provides the following object abstractions: networks, subnets, and routers. Each has functionality that mimics its physical counterpart: networks contain subnets, and routers route traffic between different subnet and networks."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-concepts.xml:20(para)
+msgid "Any given Networking set up has at least one external network. This network, unlike the other networks, is not merely a virtually defined network. Instead, it represents the view into a slice of the external network that is accessible outside the OpenStack installation. IP addresses on the Networking external network are accessible by anybody physically on the outside network. Because this network merely represents a slice of the outside network, DHCP is disabled on this network."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-concepts.xml:28(para)
+msgid "In addition to external networks, any Networking set up has one or more internal networks. These software-defined networks connect directly to the VMs. Only the VMs on any given internal network, or those on subnets connected through interfaces to a similar router, can access VMs connected to that network directly."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-concepts.xml:33(para)
+msgid "For the outside network to access VMs, and vice versa, routers between the networks are needed. Each router has one gateway that is connected to a network and many interfaces that are connected to subnets. Like a physical router, subnets can access machines on other subnets that are connected to the same router, and machines can access the outside network through the gateway for the router."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-concepts.xml:40(para)
+msgid "Additionally, you can allocate IP addresses on external networks to ports on the internal network. Whenever something is connected to a subnet, that connection is called a port. You can associate external network IP addresses with ports to VMs. This way, entities on the outside network can access VMs."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-concepts.xml:45(para)
+msgid "Networking also supports <emphasis role=\"italic\">security groups</emphasis>. Security groups enable administrators to define firewall rules in groups. A VM can belong to one or more security groups, and Networking applies the rules in those security groups to block or unblock ports, port ranges, or traffic types for that VM."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-concepts.xml:51(para)
+msgid "Each plug-in that Networking uses has its own concepts. While not vital to operating Networking, understanding these concepts can help you set up Networking. All Networking installations use a core plug-in and a security group plug-in (or just the No-Op security group plug-in). Additionally, Firewall-as-a-service (FWaaS) and Load-balancing-as-a-service (LBaaS) plug-ins are available."
+msgstr ""
+
 #: ./doc/install-guide/section_nova-networking-initial-network.xml:5(title)
 msgid "Create initial network"
 msgstr ""
@@ -173,198 +1221,96 @@ msgstr ""
 msgid "Verify creation of the network:"
 msgstr ""
 
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-api-endpoints.xml:29(None)
-msgid "@@image: 'figures/debconf-screenshots/api-endpoint_1_register_endpoint.png'; md5=d534be231be4f725820a1050fbf44231"
+#: ./doc/install-guide/ch_horizon.xml:6(title)
+msgid "Add the dashboard"
 msgstr ""
 
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-api-endpoints.xml:40(None)
-msgid "@@image: 'figures/debconf-screenshots/api-endpoint_2_keystone_server_ip.png'; md5=d2c5a5b82dd433fcf9cde6f5ac34c30e"
+#: ./doc/install-guide/ch_horizon.xml:7(para)
+msgid "The OpenStack dashboard, also known as <link href=\"https://github.com/openstack/horizon/\">Horizon</link>, is a Web interface that enables cloud administrators and users to manage various OpenStack resources and services."
 msgstr ""
 
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-api-endpoints.xml:54(None)
-msgid "@@image: 'figures/debconf-screenshots/api-endpoint_3_keystone_authtoken.png'; md5=1f3b05ebe671f64d672ac70d246e4f39"
+#: ./doc/install-guide/ch_horizon.xml:12(para)
+msgid "The dashboard enables web-based interactions with the OpenStack Compute cloud controller through the OpenStack APIs."
 msgstr ""
 
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-api-endpoints.xml:69(None)
-msgid "@@image: 'figures/debconf-screenshots/api-endpoint_4_service_endpoint_ip_address.png'; md5=6853f0ae2ef8d5fddb22c466d465de15"
+#: ./doc/install-guide/ch_horizon.xml:15(para)
+msgid "These instructions show an example deployment configured with an Apache web server."
 msgstr ""
 
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-api-endpoints.xml:81(None)
-msgid "@@image: 'figures/debconf-screenshots/api-endpoint_5_region_name.png'; md5=a6bce0acf5a1cb85f161290f0cf30733"
+#: ./doc/install-guide/ch_horizon.xml:17(para)
+msgid "After you <link linkend=\"install_dashboard\">install and configure the dashboard</link>, you can complete the following tasks:"
 msgstr ""
 
-#: ./doc/install-guide/section_debconf-api-endpoints.xml:6(title)
-msgid "Register API endpoints"
+#: ./doc/install-guide/ch_horizon.xml:22(para)
+msgid "Customize your dashboard. See section <link href=\"http://docs.openstack.org/admin-guide-cloud/content/ch_install-dashboard.html#dashboard-custom-brand\">Customize the dashboard</link> in the <link href=\"http://docs.openstack.org/admin-guide-cloud/content/\"><citetitle>OpenStack Cloud Administrator Guide</citetitle></link>."
 msgstr ""
 
-#: ./doc/install-guide/section_debconf-api-endpoints.xml:7(para)
-msgid "All Debian packages for API services, except the <package>heat-api</package> package, register the service in the Identity Service catalog. This feature is helpful because API endpoints are difficult to remember."
+#: ./doc/install-guide/ch_horizon.xml:30(para)
+msgid "Set up session storage for the dashboard. See <xref linkend=\"dashboard-sessions\"/>."
 msgstr ""
 
-#: ./doc/install-guide/section_debconf-api-endpoints.xml:12(para)
-msgid "The <package>heat-common</package> package and not the <package>heat-api</package> package configures the Orchestration service."
+#: ./doc/install-guide/ch_horizon.xml:39(para)
+msgid "Your OpenStack environment now includes the dashboard. You can <link linkend=\"launch-instance\">launch an instance</link> or add more services to your environment in the following chapters."
 msgstr ""
 
-#: ./doc/install-guide/section_debconf-api-endpoints.xml:16(para)
-msgid "When you install a package for an API service, you are prompted to register that service. However, after you install or upgrade the package for an API service, Debian immediately removes your response to this prompt from the <package>debconf</package> database. Consequently, you are prompted to re-register the service with the Identity Service. If you already registered the API service, respond <literal>no</literal> when you upgrade."
+#: ./doc/install-guide/section_keystone-verify.xml:6(title)
+msgid "Verify the Identity Service installation"
 msgstr ""
 
-#: ./doc/install-guide/section_debconf-api-endpoints.xml:33(para)
-msgid "This screen registers packages in the Identity Service catalog:"
+#: ./doc/install-guide/section_keystone-verify.xml:9(para)
+msgid "To verify that the Identity Service is installed and configured correctly, clear the values in the <envar>OS_SERVICE_TOKEN</envar> and <envar>OS_SERVICE_ENDPOINT</envar> environment variables:"
 msgstr ""
 
-#: ./doc/install-guide/section_debconf-api-endpoints.xml:44(para)
-msgid "You are prompted for the Identity Service <literal>admin_token</literal> value. The Identity Service uses this value to register the API service. When you set up the <package>keystone</package> package, this value is configured automatically."
+#: ./doc/install-guide/section_keystone-verify.xml:15(para)
+msgid "These variables, which were used to bootstrap the administrative user and register the Identity Service, are no longer needed."
 msgstr ""
 
-#: ./doc/install-guide/section_debconf-api-endpoints.xml:58(para)
-msgid "This screen configures the IP addresses for the service. The configuration script automatically detects the IP address used by the interface that is connected to the default route (<code>/sbin/route</code> and <code>/sbin/ip</code>)."
+#: ./doc/install-guide/section_keystone-verify.xml:20(para)
+msgid "You can now use regular user name-based authentication."
 msgstr ""
 
-#: ./doc/install-guide/section_debconf-api-endpoints.xml:62(para)
-msgid "Unless you have a unique set up for your network, press <keycap>ENTER</keycap>."
+#: ./doc/install-guide/section_keystone-verify.xml:22(para)
+msgid "Request a authentication token by using the <literal>admin</literal> user and the password you chose for that user:"
 msgstr ""
 
-#: ./doc/install-guide/section_debconf-api-endpoints.xml:73(para)
-msgid "This screen configures the region name for the service. For example, <code>us-east-coast</code> or <code>europe-paris</code>."
+#: ./doc/install-guide/section_keystone-verify.xml:27(para)
+msgid "In response, you receive a token paired with your user ID. This verifies that the Identity Service is running on the expected endpoint and that your user account is established with the expected credentials."
 msgstr ""
 
-#: ./doc/install-guide/ch_glance.xml:6(title)
-msgid "Add the Image Service"
+#: ./doc/install-guide/section_keystone-verify.xml:33(para)
+msgid "Verify that authorization behaves as expected. To do so, request authorization on a tenant:"
 msgstr ""
 
-#: ./doc/install-guide/ch_glance.xml:7(para)
-msgid "The OpenStack Image Service (glance) enables users to discover, register, and retrieve virtual machine images. It offers a <glossterm baseform=\"RESTful\">REST</glossterm> API that enables you to query virtual machine image metadata and retrieve an actual image. You can store virtual machine images made available through the Image Service in a variety of locations, from simple file systems to object-storage systems like OpenStack Object Storage."
+#: ./doc/install-guide/section_keystone-verify.xml:38(para)
+msgid "In response, you receive a token that includes the ID of the tenant that you specified. This verifies that your user account has an explicitly defined role on the specified tenant and the tenant exists as expected."
 msgstr ""
 
-#: ./doc/install-guide/ch_glance.xml:15(para)
-msgid "For simplicity, this guide describes configuring the Image Service to use the <literal>file</literal> back end, which uploads and stores in a directory on the controller node hosting the Image Service. By default, this directory is <filename>/var/lib/glance/images/</filename>."
+#: ./doc/install-guide/section_keystone-verify.xml:44(para)
+msgid "You can also set your <literal>--os-*</literal> variables in your environment to simplify command-line usage. Set up a <filename>admin-openrc.sh</filename> file with the admin credentials and admin endpoint:"
 msgstr ""
 
-#: ./doc/install-guide/ch_glance.xml:20(para)
-msgid "Before you proceed, ensure that the controller node has at least several gigabytes of space available in this directory."
+#: ./doc/install-guide/section_keystone-verify.xml:54(para)
+msgid "Source this file to read in the environment variables:"
 msgstr ""
 
-#: ./doc/install-guide/ch_glance.xml:22(para)
-msgid "For information on requirements for other back ends, see <link href=\"http://docs.openstack.org/trunk/config-reference/content/ch_configuring-openstack-image-service.html\"><citetitle>Configuration Reference</citetitle></link>."
+#: ./doc/install-guide/section_keystone-verify.xml:59(para)
+msgid "Verify that your <filename>admin-openrc.sh</filename> file is configured correctly. Run the same command without the <literal>--os-*</literal> arguments:"
 msgstr ""
 
-#: ./doc/install-guide/ch_cinder.xml:6(title)
-msgid "Add the Block Storage service"
+#: ./doc/install-guide/section_keystone-verify.xml:63(para)
+msgid "The command returns a token and the ID of the specified tenant. This verifies that you have configured your environment variables correctly."
 msgstr ""
 
-#: ./doc/install-guide/ch_cinder.xml:7(para)
-msgid "The OpenStack Block Storage service works through the interaction of a series of daemon processes named <systemitem role=\"process\">cinder-*</systemitem> that reside persistently on the host machine or machines. You can run the binaries from a single node or across multiple nodes. You can also run them on the same node as other OpenStack services. The following sections introduce Block Storage service components and concepts and show you how to configure and install the Block Storage service."
+#: ./doc/install-guide/section_keystone-verify.xml:68(para)
+msgid "Verify that your admin account has authorization to perform administrative commands:"
 msgstr ""
 
-#: ./doc/install-guide/ch_cinder.xml:20(title) ./doc/install-guide/ch_swift.xml:30(title) ./doc/install-guide/ch_networking.xml:37(title) ./doc/install-guide/ch_horizon.xml:38(title) ./doc/install-guide/ch_ceilometer.xml:18(title) ./doc/install-guide/ch_heat.xml:14(title)
-msgid "Next steps"
+#: ./doc/install-guide/section_keystone-verify.xml:85(para)
+msgid "Seeing that the <literal>id</literal> in the output from the <placeholder-1/> command matches the <literal>user_id</literal> in the <placeholder-2/> command, and that the admin role is listed for that user, for the related tenant, this verifies that your user account has the <literal>admin</literal> role, which matches the role used in the Identity Service <filename>policy.json</filename> file."
 msgstr ""
 
-#: ./doc/install-guide/ch_cinder.xml:21(para)
-msgid "Your OpenStack environment now includes Block Storage. You can <link linkend=\"launch-instance\">launch an instance</link> or add more services to your environment in the following chapters."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-passwords.xml:6(title)
-msgid "Passwords"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-passwords.xml:7(para)
-msgid "The various OpenStack services and the required software like the database and the messaging server have to be password protected. You use these passwords when configuring a service and then again to access the service. You have to choose a password while configuring the service and later remember to use the same password when accessing it. Optionally, you can generate random passwords with the <application>pwgen</application> program. Or, to create passwords one at a time, use the output of this command repeatedly: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-passwords.xml:17(para)
-msgid "This guide uses the convention that <literal><replaceable>SERVICE_PASS</replaceable></literal> is the password to access the service <literal>SERVICE</literal> and <literal><replaceable>SERVICE_DBPASS</replaceable></literal> is the database password used by the service SERVICE to access the database."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-passwords.xml:24(para)
-msgid "The complete list of passwords you need to define in this guide are: <table rules=\"all\"><caption>Passwords</caption><thead><tr><th>Password name</th><th>Description</th></tr></thead><tbody><tr><td>Database password (no variable used)</td><td>Root password for the database</td></tr><tr os=\"ubuntu;opensuse;sles\"><td><literal><replaceable>RABBIT_PASS</replaceable></literal></td><td>Password of user guest of RabbitMQ</td></tr><tr><td><literal><replaceable>KEYSTONE_DBPASS</replaceable></literal></td><td>Database password of Identity service</td></tr><tr><td><literal><replaceable>DEMO_PASS</replaceable></literal></td><td>Password of user <literal>demo</literal></td></tr><tr><td><literal><replaceable>ADMIN_PASS</replaceable></literal></td><td>Password of user <literal>admin</literal></td></tr><tr><td><literal><replaceable>GLANCE_DBPASS</replaceable></literal></td><td>Database password for Image Service</td></tr><tr><td><literal><replaceable>GLANCE_PASS</replaceable></literal></td><td>Password of Image Service user <literal>glance</literal></td></tr><tr><td><literal><replaceable>NOVA_DBPASS</replaceable></literal></td><td>Database password for Compute service</td></tr><tr><td><literal><replaceable>NOVA_PASS</replaceable></literal></td><td>Password of Compute service user <literal>nova</literal></td></tr><tr><td><literal><replaceable>DASH_DBPASS</replaceable></literal></td><td>Database password for the dashboard</td></tr><tr><td><literal><replaceable>CINDER_DBPASS</replaceable></literal></td><td>Database password for the Block Storage service</td></tr><tr><td><literal><replaceable>CINDER_PASS</replaceable></literal></td><td>Password of Block Storage service user <literal>cinder</literal></td></tr><tr><td><literal><replaceable>NEUTRON_DBPASS</replaceable></literal></td><td>Database password for the Networking service</td></tr><tr><td><literal><replaceable>NEUTRON_PASS</replaceable></literal></td><td>Password of Networking service user <literal>neutron</literal></td></tr><tr><td><literal><replaceable>HEAT_DBPASS</replaceable></literal></td><td>Database password for the Orchestration service</td></tr><tr><td><literal><replaceable>HEAT_PASS</replaceable></literal></td><td>Password of Orchestration service user <literal>heat</literal></td></tr><tr><td><literal><replaceable>CEILOMETER_DBPASS</replaceable></literal></td><td>Database password for the Telemetry service</td></tr><tr><td><literal><replaceable>CEILOMETER_PASS</replaceable></literal></td><td>Password of Telemetry service user <literal>ceilometer</literal></td></tr><tr><td><literal><replaceable>TROVE_DBPASS</replaceable></literal></td><td>Database password of Database service</td></tr><tr><td><literal><replaceable>TROVE_PASS</replaceable></literal></td><td>Password of Database Service user <literal>trove</literal></td></tr></tbody></table>"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-database.xml:6(title)
-msgid "Database"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-database.xml:7(para)
-msgid "Most OpenStack services require a database to store information. These examples use a MySQL database that runs on the controller node. You must install the MySQL database on the controller node. You must install the MySQL Python library on any additional nodes that access MySQL."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-database.xml:13(para)
-msgid "Most OpenStack services require a database to store information. This guide uses a MySQL database on SUSE Linux Enterprise Server and a compatible database on openSUSE running on the controller node. This compatible database for openSUSE is MariaDB. You must install the MariaDB database on the controller node. You must install the MySQL Python library on any additional nodes that access MySQL or MariaDB."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-database.xml:22(title)
-msgid "Controller setup"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-database.xml:23(para)
-msgid "<phrase os=\"sles\">For SUSE Linux Enterprise Server: </phrase> On the controller node, install the MySQL client and server packages, and the Python library."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-database.xml:27(para)
-msgid "For openSUSE: On the controller node, install the MariaDB client and database server packages, and the MySQL Python library."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-database.xml:34(para)
-msgid "When you install the server package, you are prompted for the root password for the database. Choose a strong password and remember it."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-database.xml:38(para)
-msgid "The MySQL configuration requires some changes to work with OpenStack."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-database.xml:42(para)
-msgid "Edit the <filename>/etc/mysql/my.cnf</filename> file:"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-database.xml:44(para)
-msgid "Edit the <filename>/etc/my.cnf</filename> file:"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-database.xml:48(para)
-msgid "Under the <literal>[mysqld]</literal> section, set the <literal>bind-address</literal> key to the management IP address of the controller node to enable access by other nodes via the management network:"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-database.xml:57(para)
-msgid "Under the <literal>[mysqld]</literal> section, set the following keys to enable InnoDB, UTF-8 character set, and UTF-8 collation by default:"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-database.xml:71(para)
-msgid "Restart the MySQL service to apply the changes:"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-database.xml:74(para)
-msgid "Start the <phrase os=\"rhel;fedora;centos\">MySQL</phrase><phrase os=\"opensuse;sles\">MariaDB or MySQL</phrase> database server and set it to start automatically when the system boots:"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-database.xml:83(para)
-msgid "Finally, you should set a root password for your <phrase os=\"rhel;fedora;centos\">MySQL</phrase><phrase os=\"opensuse;sles\">MariaDB or MySQL</phrase> database. The OpenStack programs that set up databases and tables prompt you for this password if it is set."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-database.xml:89(para)
-msgid "You must delete the anonymous users that are created when the database is first started. Otherwise, database connection problems occur when you follow the instructions in this guide. To do this, use the <placeholder-1/> command. Note that if <placeholder-2/> fails you might need to use <placeholder-3/> first:"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-database.xml:98(para)
-msgid "<phrase os=\"rhel;centos;fedora;opensuse;sles\">If you have not already set a root database password, press <keycap>ENTER</keycap> when you are prompted for the password.</phrase> This command presents a number of options for you to secure your database installation. Respond <placeholder-1/> to all prompts unless you have a good reason to do otherwise."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-database.xml:107(title)
-msgid "Node setup"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-database.xml:108(para)
-msgid "On all nodes other than the controller node, install the MySQL Python library:"
+#: ./doc/install-guide/section_keystone-verify.xml:95(para)
+msgid "As long as you define your credentials and the Identity Service endpoint through the command line or environment variables, you can run all OpenStack client commands from any machine. For details, see <xref linkend=\"ch_clients\"/>."
 msgstr ""
 
 #: ./doc/install-guide/section_basics-packages.xml:6(title)
@@ -515,172 +1461,612 @@ msgstr ""
 msgid "This caveat applies to most OpenStack packages in Wheezy."
 msgstr ""
 
-#: ./doc/install-guide/section_basics-networking.xml:6(title)
-msgid "Networking"
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:6(title) ./doc/install-guide/section_nova-networking-compute-node.xml:5(title) ./doc/install-guide/section_neutron-ml2-compute-node.xml:6(title)
+msgid "Configure compute node"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-networking.xml:7(para)
-msgid "After installing the operating system on each node for the architecture that you choose to deploy, you must configure the network interfaces. We recommend that you disable any automated network management tools and manually edit the appropriate configuration files for your distribution. For more information on how to configure networking on your distribution, see the <link os=\"ubuntu\" href=\"https://help.ubuntu.com/lts/serverguide/network-configuration.html\">documentation.</link><link os=\"debian\" href=\"https://wiki.debian.org/NetworkConfiguration\">documentation.</link><link os=\"rhel;centos;fedora\" href=\"https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s1-networkscripts-interfaces.html\">documentation.</link><link os=\"sles;opensuse\" href=\"https://www.suse.com/documentation/sles11/book_sle_admin/data/sec_basicnet_manconf.html\">SLES 11</link><phrase os=\"sles;opensuse\"> or </phrase><link os=\"sles;opensuse\" href=\"http://activedoc.opensuse.org/book/opensuse-reference/chapter-13-basic-networking\">openSUSE documentation.</link>"
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:8(para)
+msgid "This section details set up for any node that runs the <literal>nova-compute</literal> component but does not run the full network stack."
 msgstr ""
 
-#: ./doc/install-guide/section_basics-networking.xml:30(title)
-msgid "To disable <systemitem class=\"service\">NetworkManager</systemitem> and enable the <systemitem class=\"service\">network</systemitem> service:"
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:13(para)
+msgid "By default, the <literal>system-config-firewall</literal> automated firewall configuration tool is in place on RHEL. This graphical interface (and a curses-style interface with <literal>-tui</literal> on the end of the name) enables you to configure IP tables as a basic firewall. You should disable it when you work with OpenStack Networking unless you are familiar with the underlying network technologies, as, by default, it blocks various types of network traffic that are important to neutron services. To disable it, launch the program and clear the <guilabel>Enabled</guilabel> check box."
 msgstr ""
 
-#: ./doc/install-guide/section_basics-networking.xml:41(title)
-msgid "To disable <systemitem class=\"service\">NetworkManager</systemitem>:"
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:22(para)
+msgid "After you successfully set up OpenStack Networking with Neutron, you can re-enable and configure the tool. However, during OpenStack Networking setup, disable the tool to make it easier to debug network issues."
 msgstr ""
 
-#: ./doc/install-guide/section_basics-networking.xml:43(para)
-msgid "Use the YaST network module:"
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:28(title) ./doc/install-guide/section_neutron-ml2-compute-node.xml:8(title) ./doc/install-guide/section_trove-install.xml:7(title) ./doc/install-guide/section_neutron-ml2-controller-node.xml:8(title) ./doc/install-guide/section_neutron-ovs-controller-node.xml:24(title) ./doc/install-guide/section_neutron-ml2-network-node.xml:8(title)
+msgid "Prerequisites"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-networking.xml:45(para)
-msgid "For more information, see the <link href=\"https://www.suse.com/documentation/sles11/book_sle_admin/data/sec_nm_activate.html\">SLES </link> or the <link href=\"http://activedoc.opensuse.org/book/opensuse-reference/chapter-13-basic-networking#sec.basicnet.yast.netcard.global\"> openSUSE documentation</link>."
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:30(para)
+msgid "Disable packet destination filtering (route verification) to let the networking services route traffic to the VMs. Edit the <filename>/etc/sysctl.conf</filename> file and run the following command to activate changes:"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-networking.xml:53(para)
-msgid "RHEL and derivatives including CentOS and Scientific Linux enable a restrictive <glossterm>firewall</glossterm> by default. During this installation, certain steps will fail unless you alter or disable the firewall. For further information about securing your installation, refer to the <link href=\"http://docs.openstack.org/sec/\"> OpenStack Security Guide</link>."
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:41(title)
+msgid "Install Open vSwitch plug-in"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-networking.xml:60(para)
-msgid "On Fedora, <literal>firewalld</literal> replaces <literal>iptables</literal> as the default firewall system. While you can use <literal>firewalld</literal> successfully, this guide references <literal>iptables</literal> for compatibility with other distributions."
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:42(para) ./doc/install-guide/section_neutron-ovs-controller-node.xml:185(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:176(para)
+msgid "OpenStack Networking supports a variety of plug-ins. For simplicity, we chose to cover the most common plug-in, Open vSwitch, and configure it to use basic GRE tunnels for tenant network traffic."
 msgstr ""
 
-#: ./doc/install-guide/section_basics-networking.xml:66(title)
-msgid "To disable <literal>firewalld</literal> and enable <literal>iptables</literal>:"
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:47(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:181(para)
+msgid "Install the Open vSwitch plug-in and its dependencies:"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-networking.xml:75(para)
-msgid "Proceed to network configuration for the example <link linkend=\"basics-networking-neutron\">OpenStack Networking (neutron) </link> or <link linkend=\"basics-networking-nova\">legacy networking (nova-network)</link> architecture."
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:54(para)
+msgid "Restart Open vSwitch:"
 msgstr ""
 
-#: ./doc/install-guide/section_cinder-verify.xml:5(title)
-msgid "Verify the Block Storage installation"
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:58(para)
+msgid "Start Open vSwitch and configure it to start when the system boots:"
 msgstr ""
 
-#: ./doc/install-guide/section_cinder-verify.xml:6(para)
-msgid "To verify that the Block Storage is installed and configured properly, create a new volume."
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:66(para)
+msgid "You must set some common configuration options no matter which networking technology you choose to use with Open vSwitch. You must add the <literal>br-int</literal> integration bridge, which connects to the VMs."
 msgstr ""
 
-#: ./doc/install-guide/section_cinder-verify.xml:8(para)
-msgid "For more information about how to manage volumes, see the <link href=\"http://docs.openstack.org/user-guide/content/index.html\"><citetitle>OpenStack User Guide</citetitle></link>."
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:74(para)
+msgid "You must set some common configuration options. You must configure Networking core to use <acronym>OVS</acronym>. Edit the <filename>/etc/neutron/neutron.conf</filename> file:"
 msgstr ""
 
-#: ./doc/install-guide/section_cinder-verify.xml:13(para)
-msgid "Source the <filename>demo-openrc.sh</filename> file:"
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:83(para)
+msgid "You must configure a firewall as well. You should use the same firewall plug-in that you chose to use when you set up the network node. To do this, edit <filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename> file and set the <literal>firewall_driver</literal> value under the <literal>securitygroup</literal> to the same value used on the network node. For instance, if you chose to use the Hybrid OVS-IPTables plug-in, your configuration looks like this:"
 msgstr ""
 
-#: ./doc/install-guide/section_cinder-verify.xml:18(para)
-msgid "Use the <placeholder-1/> command to create a new volume:"
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:96(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:313(para)
+msgid "You must use at least the No-Op firewall. Otherwise, Horizon and other OpenStack services cannot get and set required VM boot options."
 msgstr ""
 
-#: ./doc/install-guide/section_cinder-verify.xml:40(para)
-msgid "Make sure that the volume has been correctly created with the <placeholder-1/> command:"
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:102(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:319(para)
+msgid "Configure the <acronym>OVS</acronym> plug-in to start on boot."
 msgstr ""
 
-#: ./doc/install-guide/section_cinder-verify.xml:48(para)
-msgid "If the status value is not <literal>available</literal>, the volume creation failed. Check the log files in the <filename>/var/log/cinder/</filename> directory on the controller and volume nodes to get information about the failure."
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:108(para)
+msgid "Tell the <acronym>OVS</acronym> plug-in to use GRE tunneling with a <literal>br-int</literal> integration bridge, a <literal>br-tun</literal> tunneling bridge, and a local IP for the tunnel of <replaceable>DATA_INTERFACE</replaceable>'s IP Edit the <filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename> file:"
 msgstr ""
 
-#: ./doc/install-guide/section_glance-verify.xml:5(title)
-msgid "Verify the Image Service installation"
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:123(replaceable)
+msgid "DATA_INTERFACE_IP"
 msgstr ""
 
-#: ./doc/install-guide/section_glance-verify.xml:6(para)
-msgid "To test the Image Service installation, download at least one virtual machine image that is known to work with OpenStack. For example, CirrOS is a small test image that is often used for testing OpenStack deployments (<link href=\"http://download.cirros-cloud.net/\">CirrOS downloads</link>). This walk through uses the 64-bit CirrOS QCOW2 image."
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:127(title)
+msgid "Configure common components"
 msgstr ""
 
-#: ./doc/install-guide/section_glance-verify.xml:13(para)
-msgid "For more information about how to download and build images, see <link href=\"http://docs.openstack.org/image-guide/content/index.html\"><citetitle>OpenStack Virtual Machine Image Guide</citetitle></link>. For information about how to manage images, see the <link href=\"http://docs.openstack.org/user-guide/content/index.html\"><citetitle>OpenStack User Guide</citetitle></link>."
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:129(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:82(para)
+msgid "Configure Networking to use <systemitem class=\"service\">keystone</systemitem> for authentication:"
 msgstr ""
 
-#: ./doc/install-guide/section_glance-verify.xml:24(para)
-msgid "Download the image into a dedicated directory using <placeholder-1/> or <placeholder-2/>:"
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:132(para) ./doc/install-guide/section_neutron-ovs-compute-node.xml:166(para)
+msgid "Set the <literal>auth_strategy</literal> configuration key to <literal>keystone</literal> in the <literal>[DEFAULT]</literal> section of the file:"
 msgstr ""
 
-#: ./doc/install-guide/section_glance-verify.xml:32(para)
-msgid "Upload the image to the Image Service:"
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:138(para) ./doc/install-guide/section_neutron-ovs-controller-node.xml:95(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:91(para)
+msgid "Set the <systemitem class=\"service\">neutron</systemitem> configuration for <systemitem class=\"service\">keystone</systemitem> authentication:"
 msgstr ""
 
-#: ./doc/install-guide/section_glance-verify.xml:33(replaceable) ./doc/install-guide/section_glance-verify.xml:38(replaceable)
-msgid "IMAGELABEL"
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:155(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:185(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:240(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:257(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:74(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:100(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:302(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:332(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:33(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:151(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:177(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:384(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:414(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:46(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:110(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:139(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:237(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:254(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:77(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:103(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:277(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:304(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:109(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:136(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:393(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:407(replaceable)
+msgid "NEUTRON_PASS"
 msgstr ""
 
-#: ./doc/install-guide/section_glance-verify.xml:33(replaceable) ./doc/install-guide/section_glance-verify.xml:45(replaceable)
-msgid "FILEFORMAT"
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:160(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:113(para)
+msgid "To configure <systemitem class=\"service\">neutron</systemitem> to use <systemitem class=\"service\">keystone</systemitem> for authentication, edit the <filename>/etc/neutron/neutron.conf</filename> file."
 msgstr ""
 
-#: ./doc/install-guide/section_glance-verify.xml:34(replaceable) ./doc/install-guide/section_glance-verify.xml:65(replaceable)
-msgid "CONTAINERFORMAT"
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:174(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:125(para)
+msgid "Add these lines to the <literal>[keystone_authtoken]</literal> section of the file:"
 msgstr ""
 
-#: ./doc/install-guide/section_glance-verify.xml:34(replaceable) ./doc/install-guide/section_glance-verify.xml:86(replaceable)
-msgid "ACCESSVALUE"
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:190(para) ./doc/install-guide/section_neutron-ovs-controller-node.xml:144(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:141(para)
+msgid "Configure access to the <application>RabbitMQ</application> service:"
 msgstr ""
 
-#: ./doc/install-guide/section_glance-verify.xml:34(replaceable) ./doc/install-guide/section_glance-verify.xml:101(replaceable)
-msgid "IMAGEFILE"
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:201(para)
+msgid "Configure the <application>RabbitMQ</application> access. Edit the <filename>/etc/neutron/neutron.conf</filename> file to modify the following parameters in the <literal>[DEFAULT]</literal> section."
 msgstr ""
 
-#: ./doc/install-guide/section_glance-verify.xml:35(para)
-msgid "Where:"
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:210(para) ./doc/install-guide/section_neutron-ovs-controller-node.xml:156(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:161(para)
+msgid "Configure access to the <application>Qpid</application> message queue:"
 msgstr ""
 
-#: ./doc/install-guide/section_glance-verify.xml:40(para)
-msgid "Arbitrary label. The name by which users refer to the image."
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:218(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:220(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:165(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:167(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:169(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:171(replaceable)
+msgid "guest"
 msgstr ""
 
-#: ./doc/install-guide/section_glance-verify.xml:47(para)
-msgid "Specifies the format of the image file. Valid formats include <literal>qcow2</literal>, <literal>raw</literal>, <literal>vhd</literal>, <literal>vmdk</literal>, <literal>vdi</literal>, <literal>iso</literal>, <literal>aki</literal>, <literal>ari</literal>, and <literal>ami</literal>."
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:224(title) ./doc/install-guide/section_neutron-ovs-controller-node.xml:220(title)
+msgid "Configure Compute services for Networking"
 msgstr ""
 
-#: ./doc/install-guide/section_glance-verify.xml:58(para)
-msgid "You can verify the format using the <placeholder-1/> command: <placeholder-2/>"
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:226(para)
+msgid "Configure OpenStack Compute to use OpenStack Networking services. Configure the <filename>/etc/nova/nova.conf</filename> file as per instructions below:"
 msgstr ""
 
-#: ./doc/install-guide/section_glance-verify.xml:67(para)
-msgid "Specifies the container format. Valid formats include: <literal>bare</literal>, <literal>ovf</literal>, <literal>aki</literal>, <literal>ari</literal> and <literal>ami</literal>."
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:249(para)
+msgid "Configure OpenStack Compute to use OpenStack Networking services. Edit the <filename>/etc/nova/nova.conf</filename> file:"
 msgstr ""
 
-#: ./doc/install-guide/section_glance-verify.xml:73(para)
-msgid "Specify <literal>bare</literal> to indicate that the image file is not in a file format that contains metadata about the virtual machine. Although this field is currently required, it is not actually used by any of the OpenStack services and has no effect on system behavior. Because the value is not used anywhere, it is safe to always specify <literal>bare</literal> as the container format."
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:265(para)
+msgid "No matter which firewall driver you chose when you configured the network and compute nodes, you must edit the <filename>/etc/nova/nova.conf</filename> file to set the firewall driver to <literal>nova.virt.firewall.NoopFirewallDriver</literal>. Because OpenStack Networking handles the firewall, this statement instructs Compute to not use a firewall."
 msgstr ""
 
-#: ./doc/install-guide/section_glance-verify.xml:90(para)
-msgid "true - All users can view and use the image."
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:275(para)
+msgid "If you want Networking to handle the firewall, edit the <filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename> file to set the <code>firewall_driver</code> option to the firewall for the plug-in. For example, with <acronym>OVS</acronym>, edit the file as follows:"
 msgstr ""
 
-#: ./doc/install-guide/section_glance-verify.xml:94(para)
-msgid "false - Only administrators can view and use the image."
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:290(para)
+msgid "If you do not want to use a firewall in Compute or Networking, edit both configuration files and set <code>firewall_driver=nova.virt.firewall.NoopFirewallDriver</code>. Also, edit the <filename>/etc/nova/nova.conf</filename> file and comment out or remove the <code>security_group_api=neutron</code> statement."
 msgstr ""
 
-#: ./doc/install-guide/section_glance-verify.xml:88(para)
-msgid "Specifies image access: <placeholder-1/>"
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:298(para)
+msgid "Otherwise, when you issue <placeholder-1/> commands, the <errortext>ERROR: The server has either erred or is incapable of performing the requested operation. (HTTP 500)</errortext> error might be returned."
 msgstr ""
 
-#: ./doc/install-guide/section_glance-verify.xml:103(para)
-msgid "Specifies the name of your downloaded image file."
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:309(title) ./doc/install-guide/section_neutron-ovs-controller-node.xml:322(title) ./doc/install-guide/section_neutron-ovs-network-node.xml:432(title)
+msgid "Finalize installation"
 msgstr ""
 
-#: ./doc/install-guide/section_glance-verify.xml:108(para) ./doc/install-guide/section_glance-verify.xml:157(para)
-msgid "For example:"
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:311(para) ./doc/install-guide/section_neutron-ovs-controller-node.xml:298(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:434(para)
+msgid "The <systemitem class=\"service\">neutron-server</systemitem> initialization script expects a symbolic link <filename>/etc/neutron/plugin.ini</filename> pointing to the configuration file associated with your chosen plug-in. Using Open vSwitch, for example, the symbolic link must point to <filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename>. If this symbolic link does not exist, create it using the following commands:"
 msgstr ""
 
-#: ./doc/install-guide/section_glance-verify.xml:133(para)
-msgid "Because the returned image ID is generated dynamically, your deployment generates a different ID than the one shown in this example."
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:323(para) ./doc/install-guide/section_neutron-ovs-controller-node.xml:310(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:446(para)
+msgid "The <systemitem class=\"service\">openstack-neutron</systemitem> initialization script expects the variable <literal>NEUTRON_PLUGIN_CONF</literal> in file <filename>/etc/sysconfig/neutron</filename> to reference the configuration file associated with your chosen plug-in. Using Open vSwitch, for example, edit the <filename>/etc/sysconfig/neutron</filename> file and add the following:"
 msgstr ""
 
-#: ./doc/install-guide/section_glance-verify.xml:139(para)
-msgid "Confirm that the image was uploaded and display its attributes:"
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:334(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:457(para)
+msgid "Restart Networking services."
 msgstr ""
 
-#: ./doc/install-guide/section_glance-verify.xml:149(para)
-msgid "You can now remove the locally downloaded image, since it is stored and available through the Image Service."
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:340(para)
+msgid "Restart the Compute service."
 msgstr ""
 
-#: ./doc/install-guide/section_glance-verify.xml:156(para)
-msgid "Alternatively, the upload to the Image Service can be done without having to use local disk space to store the file, by use of the <parameter>--copy-from</parameter> parameter."
+#: ./doc/install-guide/section_debconf-preseeding.xml:6(title)
+msgid "Pre-seed debconf prompts"
+msgstr ""
+
+#: ./doc/install-guide/section_debconf-preseeding.xml:7(para)
+msgid "You can pre-seed all <systemitem class=\"library\">debconf</systemitem> prompts. To pre-seed means to store responses in the <package>debconf</package> database so that <package>debconf</package> does not prompt the user for responses. Pre-seeding enables a hands-free installation for users. The package maintainer creates scripts that automatically configure the services."
+msgstr ""
+
+#: ./doc/install-guide/section_debconf-preseeding.xml:14(para)
+msgid "The following example shows how to pre-seed an automated MySQL Server installation:"
+msgstr ""
+
+#: ./doc/install-guide/section_debconf-preseeding.xml:16(replaceable) ./doc/install-guide/section_debconf-preseeding.xml:17(replaceable) ./doc/install-guide/section_debconf-preseeding.xml:19(replaceable)
+msgid "MYSQL_PASSWORD"
+msgstr ""
+
+#: ./doc/install-guide/section_debconf-preseeding.xml:23(para)
+msgid "The <code>seen true</code> option tells <package>debconf</package> that a specified screen was already seen by the user so do not show it again. This option is useful for upgrades."
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:10(title)
+msgid "Install the Telemetry module"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:12(para)
+msgid "Telemetry provides an API service that provides a collector and a range of disparate agents. Before you can install these agents on nodes such as the compute node, you must use this procedure to install the core components on the controller node."
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:18(para)
+msgid "Install the Telemetry service on the controller node:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:30(para)
+msgid "Respond to the prompts for <link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> settings</link>, <link linkend=\"debconf-rabbitqm\">RabbitMQ credentials</link> and <link linkend=\"debconf-api-endpoints\">API endpoint</link> registration."
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:38(para)
+msgid "The Telemetry service uses a database to store information. Specify the location of the database in the configuration file. The examples use a MongoDB database on the controller node:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:46(para)
+msgid "By default MongoDB is configured to create several 1GB files in the /var/lib/mongodb/journal/ directory to support database journaling."
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:51(para)
+msgid "If you need to minimize the space allocated to support database journaling then set the <option>smallfiles</option> configuration key to <literal>true</literal> in the <filename>/etc/mongodb.conf</filename> configuration file. This configuration reduces the size of each journaling file to 512MB."
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:59(para)
+msgid "As the files are created the first time the MongoDB service starts you must stop the service and remove the files for this change to take effect:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:67(para)
+msgid "For more information on the <option>smallfiles</option> configuration key refer to the MongoDB documentation at <link href=\"http://docs.mongodb.org/manual/reference/configuration-options/#smallfiles\"/>."
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:72(para)
+msgid "For instructions detailing the steps to disable database journaling entirely refer to <link href=\"http://docs.mongodb.org/manual/tutorial/manage-journaling/\"/>."
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:80(para)
+msgid "Configure MongoDB to make it listen on the controller management IP address. Edit the <filename>/etc/mongodb.conf</filename> file and modify the <literal>bind_ip</literal> key:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:86(para)
+msgid "Restart the MongoDB service to apply the configuration change:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:90(para)
+msgid "Start the MongoDB server and configure it to start when the system boots:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:100(para)
+msgid "Create the database and a <literal>ceilometer</literal> database user:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:105(replaceable) ./doc/install-guide/section_ceilometer-install.xml:111(replaceable) ./doc/install-guide/section_ceilometer-install.xml:118(replaceable)
+msgid "CEILOMETER_DBPASS"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:109(para)
+msgid "Configure the Telemetry service to use the database:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:112(para)
+msgid "Edit the <filename>/etc/ceilometer/ceilometer.conf</filename> file and change the <literal>[database]</literal> section:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:122(para)
+msgid "You must define a secret key that is used as a shared secret among Telemetry service nodes. Use <placeholder-1/> to generate a random token and store it in the configuration file:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:129(para)
+msgid "For SUSE Linux Enterprise, run the following command:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:133(para)
+msgid "Edit the <filename>/etc/ceilometer/ceilometer.conf</filename> file and change the <literal>[publisher]</literal> section. Replace <replaceable>CEILOMETER_TOKEN</replaceable> with the results of the <literal>openssl</literal> command:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:153(para)
+msgid "Configure the Qpid access:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:159(para)
+msgid "Configure the collector dispatcher:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:173(para)
+msgid "Create a <literal>ceilometer</literal> user that the Telemetry service uses to authenticate with the Identity Service. Use the <literal>service</literal> tenant and give the user the <literal>admin</literal> role:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:177(replaceable)
+msgid "ceilometer@example.com"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:181(para)
+msgid "Configure the Telemetry service to authenticate with the Identity Service."
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:183(para)
+msgid "Set the <option>auth_strategy</option> value to <literal>keystone</literal> in the <filename>/etc/ceilometer/ceilometer.conf</filename> file:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:193(para)
+msgid "Add the credentials to the configuration files for the Telemetry service:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:236(para)
+msgid "Register the Telemetry service with the Identity Service so that other OpenStack services can locate it. Use the <placeholder-1/> command to register the service and specify the endpoint:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:249(para)
+msgid "Restart the services with their new settings:"
+msgstr ""
+
+#: ./doc/install-guide/section_ceilometer-install.xml:258(para)
+msgid "Start the <systemitem class=\"service\">openstack-ceilometer-api</systemitem>, <systemitem class=\"service\" os=\"opensuse;sles\">openstack-ceilometer-agent-central</systemitem><systemitem class=\"service\" os=\"rhel;fedora;centos\">openstack-ceilometer-central</systemitem>, <systemitem class=\"service\">openstack-ceilometer-collector</systemitem>, <systemitem class=\"service\" os=\"opensuse;sles\">openstack-ceilometer-alarm-evaluator</systemitem>, and <systemitem class=\"service\" os=\"opensuse;sles\">openstack-ceilometer-alarm-notifier</systemitem> services and configure them to start when the system boots:"
+msgstr ""
+
+#: ./doc/install-guide/section_heat-verify.xml:6(title)
+msgid "Verify the Orchestration service installation"
+msgstr ""
+
+#: ./doc/install-guide/section_heat-verify.xml:8(para)
+msgid "To verify that the Orchestration service is installed and configured correctly, make sure that your credentials are set up correctly in the <filename>demo-openrc.sh</filename> file. Source the file, as follows:"
+msgstr ""
+
+#: ./doc/install-guide/section_heat-verify.xml:14(para)
+msgid "The Orchestration Module uses templates to describe stacks. To learn about the template languages, see <link href=\"http://docs.openstack.org/developer/heat/template_guide/index.html\">the Template Guide</link> in the <link href=\"http://docs.openstack.org/developer/heat/\">Heat developer documentation</link>."
+msgstr ""
+
+#: ./doc/install-guide/section_heat-verify.xml:20(para)
+msgid "Create a test template in the <filename>test-stack.yml</filename> file with the following content:"
+msgstr ""
+
+#: ./doc/install-guide/section_heat-verify.xml:24(para)
+msgid "Use the <placeholder-1/> command to create a stack from this template:"
+msgstr ""
+
+#: ./doc/install-guide/section_heat-verify.xml:35(para)
+msgid "Verify that the stack was created successfully with the <placeholder-1/> command:"
+msgstr ""
+
+#: ./doc/install-guide/ch_heat.xml:6(title)
+msgid "Add the Orchestration service"
+msgstr ""
+
+#: ./doc/install-guide/ch_heat.xml:7(para)
+msgid "Use the Orchestration module to create cloud resources using a template language called HOT. The integrated project name is Heat."
+msgstr ""
+
+#: ./doc/install-guide/ch_heat.xml:15(para)
+msgid "Your OpenStack environment now includes Orchestration. You can <link linkend=\"launch-instance\">launch an instance</link> or add more services to your environment in the following chapters."
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-rabbitqm.xml:15(None)
+msgid "@@image: 'figures/debconf-screenshots/rabbitmq-host.png'; md5=5353ad857884a2d31847cf82efbdc6b6"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-rabbitqm.xml:22(None)
+msgid "@@image: 'figures/debconf-screenshots/rabbitmq-user.png'; md5=33a3c1182e79ed65f1b1b63f2156792c"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-rabbitqm.xml:29(None)
+msgid "@@image: 'figures/debconf-screenshots/rabbitmq-password.png'; md5=6385185200d20e96b6316ae15ae1255d"
+msgstr ""
+
+#: ./doc/install-guide/section_debconf-rabbitqm.xml:6(title)
+msgid "RabbitMQ credentials parameters"
+msgstr ""
+
+#: ./doc/install-guide/section_debconf-rabbitqm.xml:7(para)
+msgid "For every package that must connect to a Messaging Server, the Debian package enables you to configure the IP address for that server and the user name and password that is used to connect. The following example shows configuration with the <systemitem class=\"service\">ceilometer-common</systemitem> package:"
+msgstr ""
+
+#: ./doc/install-guide/section_debconf-rabbitqm.xml:33(para)
+msgid "These debconf screens appear in: <systemitem class=\"service\">ceilometer-common</systemitem>, <systemitem class=\"service\">cinder-common</systemitem>, <systemitem class=\"service\">glance-common</systemitem>, <systemitem class=\"service\">heat-common</systemitem>, <systemitem class=\"service\">neutron-common</systemitem> and <systemitem class=\"service\">nova-common</systemitem>."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-ntp.xml:6(title)
+msgid "Network Time Protocol (NTP)"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-ntp.xml:7(para)
+msgid "You must install <glossterm baseform=\"Network Time Protocol (NTP)\">NTP</glossterm> to properly synchronize services among nodes. We recommend that you configure the controller node to reference upstream servers and other nodes to reference the controller node."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-ntp.xml:13(title) ./doc/install-guide/section_nova-networking-controller-node.xml:5(title) ./doc/install-guide/section_neutron-ml2-controller-node.xml:6(title) ./doc/install-guide/section_neutron-ovs-controller-node.xml:6(title)
+msgid "Configure controller node"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-ntp.xml:15(title) ./doc/install-guide/section_basics-ntp.xml:57(title)
+msgid "To install the NTP service"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-ntp.xml:23(title) ./doc/install-guide/section_basics-ntp.xml:65(title)
+msgid "To configure the NTP service"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-ntp.xml:24(para)
+msgid "By default, the controller node synchronizes the time via a pool of public servers. However, you can optionally edit the <filename>/etc/ntp.conf</filename> file to configure alternative servers such as those provided by your organization."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-ntp.xml:29(para) ./doc/install-guide/section_basics-ntp.xml:69(para)
+msgid "Edit the <filename>/etc/ntp.conf</filename> file:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-ntp.xml:30(para)
+msgid "Add, change, or remove the <literal>server</literal> keys as necessary for your environment. Replace <replaceable>NTP_SERVER</replaceable> with the hostname or IP address of suitable NTP server."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-ntp.xml:34(replaceable)
+msgid "NTP_SERVER"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-ntp.xml:36(para) ./doc/install-guide/section_basics-ntp.xml:74(para)
+msgid "Remove the <filename>/var/lib/ntp/ntp.conf.dhcp</filename> file if it exists."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-ntp.xml:41(para) ./doc/install-guide/section_basics-ntp.xml:79(para)
+msgid "Restart the NTP service:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-ntp.xml:45(para) ./doc/install-guide/section_basics-ntp.xml:83(para)
+msgid "Start the NTP service and configure it to start when the system boots:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-ntp.xml:55(title)
+msgid "Configure other nodes"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-ntp.xml:66(para)
+msgid "Configure the network and compute nodes to reference the controller node."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-ntp.xml:70(para)
+msgid "Comment out or remove all but one <literal>server</literal> key and change it to reference the controller node."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-ntp.xml:93(title)
+msgid "Verify operation"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-ntp.xml:94(para)
+msgid "We recommend that you verify NTP synchronization before proceeding further. Some nodes, particularly those that reference the controller node, can take several minutes to synchronize."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-ntp.xml:98(title)
+msgid "To verify NTP synchronization"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-ntp.xml:100(para) ./doc/install-guide/section_basics-ntp.xml:115(para)
+msgid "Run this command on the <emphasis>controller</emphasis> node:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-ntp.xml:107(para)
+msgid "Contents in the <emphasis>remote</emphasis> column should indicate the hostname or IP address of one or more NTP servers."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-ntp.xml:110(para) ./doc/install-guide/section_basics-ntp.xml:134(para)
+msgid "Contents in the <emphasis>refid</emphasis> column typically reference IP addresses of upstream servers."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-ntp.xml:122(para)
+msgid "Contents in the <emphasis>condition</emphasis> column should indicate <literal>sys.peer</literal> for at least one server."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-ntp.xml:126(para) ./doc/install-guide/section_basics-ntp.xml:139(para)
+msgid "Run this command on <emphasis>all other</emphasis> nodes:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-ntp.xml:131(para)
+msgid "Contents in the <emphasis>remote</emphasis> column should indicate the hostname of the controller node."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-ntp.xml:145(para)
+msgid "Contents in the <emphasis>condition</emphasis> column should indicate <literal>sys.peer</literal>."
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_neutron-initial-networks.xml:23(None)
+msgid "@@image: 'figures/installguide_neutron-initial-networks.png'; md5=df1d74b6f91feefe5cfaf7824aac86e1"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:6(title)
+msgid "Create initial networks"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:7(para)
+msgid "Before launching your first instance, you must create the necessary virtual network infrastructure to which the instance will connect, including the <link linkend=\"neutron_initial-external-network\">external network</link> and <link linkend=\"neutron_initial-tenant-network\">tenant network</link>. See <xref linkend=\"neutron_figure-neutron-initial-networks\"/>. After creating this infrastructure, we recommend that you <link linkend=\"neutron_initial-networks-verify\">verify connectivity</link> and resolve any issues before proceeding further."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:19(title)
+msgid "Initial networks"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:28(title)
+msgid "External network"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:29(para)
+msgid "The external network typically provides internet access for your instances. By default, this network only allows internet access <emphasis>from</emphasis> instances using <glossterm>Network Address Translation (NAT)</glossterm>. You can enable internet access <emphasis>to</emphasis> individual instances using a <glossterm>floating IP address</glossterm> and suitable <glossterm>security group</glossterm> rules. The <literal>admin</literal> tenant owns this network because it provides external network access for multiple tenants. You must also enable sharing to allow access by those tenants."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:43(title)
+msgid "To create the external network"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:69(para)
+msgid "Like a physical network, a virtual network requires a <glossterm>subnet</glossterm> assigned to it. The external network shares the same subnet and <glossterm>gateway</glossterm> associated with the physical network connected to the external interface on the network node. You should specify an exclusive slice of this subnet for <glossterm>router</glossterm> and floating IP addresses to prevent interference with other devices on the external network."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:76(para)
+msgid "Replace <replaceable>FLOATING_IP_START</replaceable> and <replaceable>FLOATING_IP_END</replaceable> with the first and last IP addresses of the range that you want to allocate for floating IP addresses. Replace <replaceable>EXTERNAL_NETWORK_CIDR</replaceable> with the subnet associated with the physical network. Replace <replaceable>EXTERNAL_NETWORK_GATEWAY</replaceable> with the gateway associated with the physical network, typically the \".1\" IP address. You should disable <glossterm>DHCP</glossterm> on this subnet because instances do not connect directly to the external network and floating IP addresses require manual assignment."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:87(title)
+msgid "To create a subnet on the external network"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:89(para) ./doc/install-guide/section_neutron-initial-networks.xml:164(para)
+msgid "Create the subnet:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:91(replaceable)
+msgid "FLOATING_IP_START"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:91(replaceable)
+msgid "FLOATING_IP_END"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:92(replaceable)
+msgid "EXTERNAL_NETWORK_GATEWAY"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:92(replaceable)
+msgid "EXTERNAL_NETWORK_CIDR"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:93(para)
+msgid "For example, using <literal>203.0.113.0/24</literal> with floating IP address range <literal>203.0.113.101</literal> to <literal>203.0.113.200</literal>:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:121(title)
+msgid "Tenant network"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:122(para)
+msgid "The tenant network provides internal network access for instances. The architecture isolates this type of network from other tenants. The <literal>demo</literal> tenant owns this network because it only provides network access for instances within it."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:130(title)
+msgid "To create the tenant network"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:132(para) ./doc/install-guide/section_launch-instance-nova.xml:15(para) ./doc/install-guide/section_launch-instance-neutron.xml:15(para)
+msgid "Source the <literal>demo</literal> tenant credentials:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:152(para)
+msgid "Like the external network, your tenant network also requires a subnet attached to it. You can specify any valid subnet because the architecture isolates tenant networks. Replace <replaceable>TENANT_NETWORK_CIDR</replaceable> with the subnet you want to associate with the tenant network. Replace <replaceable>TENANT_NETWORK_GATEWAY</replaceable> with the gateway you want to associate with this network, typically the \".1\" IP address. By default, this subnet will use DHCP so your instances can obtain IP addresses."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:162(title)
+msgid "To create a subnet on the tenant network"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:166(replaceable)
+msgid "TENANT_NETWORK_GATEWAY"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:166(replaceable)
+msgid "TENANT_NETWORK_CIDR"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:167(para)
+msgid "Example using <literal>192.168.1.0/24</literal>:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:190(para)
+msgid "A virtual router passes network traffic between two or more virtual networks. Each router requires one or more <glossterm baseform=\"interface\">interfaces</glossterm> and/or gateways that provide access to specific networks. In this case, you will create a router and attach your tenant and external networks to it."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:196(title)
+msgid "To create a router on the tenant network and attach the external and tenant networks to it"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:199(para)
+msgid "Create the router:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:214(para)
+msgid "Attach the router to the <literal>demo</literal> tenant subnet:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:220(para)
+msgid "Attach the router to the external network by setting it as the gateway:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:229(para)
+msgid "We recommend that you verify network connectivity and resolve any issues before proceeding further. Following the external network subnet example using <literal>203.0.113.0/24</literal>, the tenant router gateway should occupy the lowest IP address in the floating IP address range, <literal>203.0.113.101</literal>. If you configured your external physical network and virtual networks correctly, you you should be able to <placeholder-1/> this IP address from any host on your external physical network."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:238(para)
+msgid "If you are building your OpenStack nodes as virtual machines, you must configure the hypervisor to permit promiscuous mode on the external network."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:243(title)
+msgid "To verify network connectivity"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml:245(para)
+msgid "Ping the tenant router gateway:"
 msgstr ""
 
 #: ./doc/install-guide/ch_clients.xml:6(title)
@@ -711,14 +2097,78 @@ msgstr ""
 msgid "<filename>admin-openrc.sh</filename> for the administrative user"
 msgstr ""
 
-#: ./doc/install-guide/ch_clients.xml:42(replaceable) ./doc/install-guide/section_ceilometer-install.xml:102(replaceable) ./doc/install-guide/section_ceilometer-install.xml:111(replaceable) ./doc/install-guide/section_ceilometer-install.xml:118(replaceable) ./doc/install-guide/section_ceilometer-install.xml:145(replaceable) ./doc/install-guide/section_ceilometer-install.xml:148(replaceable) ./doc/install-guide/section_ceilometer-install.xml:196(replaceable) ./doc/install-guide/section_ceilometer-install.xml:204(replaceable) ./doc/install-guide/section_ceilometer-install.xml:208(replaceable) ./doc/install-guide/section_ceilometer-install.xml:223(replaceable) ./doc/install-guide/section_ceilometer-install.xml:230(replaceable) ./doc/install-guide/section_ceilometer-install.xml:244(replaceable) ./doc/install-guide/section_ceilometer-install.xml:245(replaceable) ./doc/install-guide/section_ceilometer-install.xml:246(replaceable) ./doc/install-guide/section_trove-install.xml:74(replaceable) ./doc/install-guide/section_trove-install.xml:75(replaceable) ./doc/install-guide/section_trove-install.xml:76(replaceable) ./doc/install-guide/section_trove-install.xml:77(replaceable) ./doc/install-guide/section_trove-install.xml:78(replaceable) ./doc/install-guide/section_trove-install.xml:79(replaceable) ./doc/install-guide/section_trove-install.xml:92(replaceable) ./doc/install-guide/section_trove-install.xml:94(replaceable) ./doc/install-guide/section_trove-install.xml:96(replaceable) ./doc/install-guide/section_trove-install.xml:119(replaceable) ./doc/install-guide/section_trove-install.xml:121(replaceable) ./doc/install-guide/section_trove-install.xml:123(replaceable) ./doc/install-guide/section_trove-install.xml:139(replaceable) ./doc/install-guide/section_trove-install.xml:220(replaceable) ./doc/install-guide/section_trove-install.xml:225(replaceable) ./doc/install-guide/section_trove-install.xml:227(replaceable) ./doc/install-guide/section_trove-install.xml:231(replaceable) ./doc/install-guide/section_trove-install.xml:252(replaceable) ./doc/install-guide/section_trove-install.xml:253(replaceable) ./doc/install-guide/section_trove-install.xml:254(replaceable) ./doc/install-guide/section_nova-controller.xml:44(replaceable) ./doc/install-guide/section_nova-controller.xml:59(replaceable) ./doc/install-guide/section_nova-controller.xml:140(replaceable) ./doc/install-guide/section_nova-controller.xml:141(replaceable) ./doc/install-guide/section_nova-controller.xml:160(replaceable) ./doc/install-guide/section_nova-controller.xml:177(replaceable) ./doc/install-guide/section_nova-controller.xml:178(replaceable) ./doc/install-guide/section_nova-controller.xml:179(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:143(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:145(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:179(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:180(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:194(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:205(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:214(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:232(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:242(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:253(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:258(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:49(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:50(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:51(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:113(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:126(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:139(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:141(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:171(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:172(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:200(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:215(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:228(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:236(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:255(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:259(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:376(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:386(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:410(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:415(replaceable) ./doc/install-guide/section_keystone-services.xml:47(replaceable) ./doc/install-guide/section_keystone-services.xml:48(replaceable) ./doc/install-guide/section_keystone-services.xml:49(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:55(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:56(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:57(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:81(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:98(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:100(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:133(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:134(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:161(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:179(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:229(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:239(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:250(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:255(replaceable) ./doc/install-guide/section_basics-ntp.xml:72(replaceable) ./doc/install-guide/section_ceilometer-glance.xml:17(replaceable) ./doc/install-guide/section_ceilometer-glance.xml:23(replaceable) ./doc/install-guide/section_basics-networking-nova.xml:202(replaceable) ./doc/install-guide/section_basics-networking-neutron.xml:277(replaceable) ./doc/install-guide/section_basics-networking-neutron.xml:321(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:97(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:99(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:130(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:131(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:145(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:156(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:165(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:389(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:394(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:399(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:409(replaceable) ./doc/install-guide/section_cinder-node.xml:113(replaceable) ./doc/install-guide/section_cinder-node.xml:115(replaceable) ./doc/install-guide/section_cinder-node.xml:131(replaceable) ./doc/install-guide/section_cinder-node.xml:132(replaceable) ./doc/install-guide/section_cinder-node.xml:150(replaceable) ./doc/install-guide/section_cinder-node.xml:161(replaceable) ./doc/install-guide/section_cinder-node.xml:170(replaceable) ./doc/install-guide/section_cinder-node.xml:183(replaceable) ./doc/install-guide/section_cinder-node.xml:186(replaceable) ./doc/install-guide/section_cinder-node.xml:202(replaceable) ./doc/install-guide/section_cinder-node.xml:205(replaceable) ./doc/install-guide/section_cinder-controller.xml:44(replaceable) ./doc/install-guide/section_cinder-controller.xml:47(replaceable) ./doc/install-guide/section_cinder-controller.xml:83(replaceable) ./doc/install-guide/section_cinder-controller.xml:85(replaceable) ./doc/install-guide/section_cinder-controller.xml:101(replaceable) ./doc/install-guide/section_cinder-controller.xml:102(replaceable) ./doc/install-guide/section_cinder-controller.xml:120(replaceable) ./doc/install-guide/section_cinder-controller.xml:153(replaceable) ./doc/install-guide/section_cinder-controller.xml:154(replaceable) ./doc/install-guide/section_cinder-controller.xml:155(replaceable) ./doc/install-guide/section_cinder-controller.xml:163(replaceable) ./doc/install-guide/section_cinder-controller.xml:164(replaceable) ./doc/install-guide/section_cinder-controller.xml:165(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:65(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:67(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:97(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:98(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:115(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:126(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:141(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:269(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:279(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:300(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:305(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:62(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:64(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:94(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:95(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:112(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:123(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:138(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:294(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:304(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:328(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:333(replaceable) ./doc/install-guide/section_heat-install.xml:40(replaceable) ./doc/install-guide/section_heat-install.xml:46(replaceable) ./doc/install-guide/section_heat-install.xml:92(replaceable) ./doc/install-guide/section_heat-install.xml:95(replaceable) ./doc/install-guide/section_heat-install.xml:113(replaceable) ./doc/install-guide/section_heat-install.xml:116(replaceable) ./doc/install-guide/section_heat-install.xml:122(replaceable) ./doc/install-guide/section_heat-install.xml:133(replaceable) ./doc/install-guide/section_heat-install.xml:134(replaceable) ./doc/install-guide/section_heat-install.xml:135(replaceable) ./doc/install-guide/section_heat-install.xml:140(replaceable) ./doc/install-guide/section_heat-install.xml:141(replaceable) ./doc/install-guide/section_heat-install.xml:142(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:79(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:85(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:91(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:107(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:122(replaceable) ./doc/install-guide/section_nova-compute.xml:74(replaceable) ./doc/install-guide/section_nova-compute.xml:75(replaceable) ./doc/install-guide/section_nova-compute.xml:93(replaceable) ./doc/install-guide/section_nova-compute.xml:94(replaceable) ./doc/install-guide/section_nova-compute.xml:106(replaceable) ./doc/install-guide/section_nova-compute.xml:131(replaceable) ./doc/install-guide/section_nova-compute.xml:143(replaceable) ./doc/install-guide/section_nova-compute.xml:151(replaceable) ./doc/install-guide/section_nova-compute.xml:154(replaceable) ./doc/install-guide/section_glance-install.xml:55(replaceable) ./doc/install-guide/section_glance-install.xml:57(replaceable) ./doc/install-guide/section_glance-install.xml:65(replaceable) ./doc/install-guide/section_glance-install.xml:74(replaceable) ./doc/install-guide/section_glance-install.xml:89(replaceable) ./doc/install-guide/section_glance-install.xml:102(replaceable) ./doc/install-guide/section_glance-install.xml:147(replaceable) ./doc/install-guide/section_glance-install.xml:149(replaceable) ./doc/install-guide/section_glance-install.xml:163(replaceable) ./doc/install-guide/section_glance-install.xml:165(replaceable) ./doc/install-guide/section_glance-install.xml:188(replaceable) ./doc/install-guide/section_glance-install.xml:189(replaceable) ./doc/install-guide/section_glance-install.xml:213(replaceable) ./doc/install-guide/section_glance-install.xml:214(replaceable) ./doc/install-guide/section_glance-install.xml:215(replaceable) ./doc/install-guide/section_keystone-install.xml:30(replaceable) ./doc/install-guide/section_keystone-install.xml:38(replaceable) ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:82(replaceable) ./doc/install-guide/object-storage/section_object-storage-install.xml:101(replaceable) ./doc/install-guide/object-storage/section_object-storage-install.xml:102(replaceable) ./doc/install-guide/object-storage/section_object-storage-install.xml:103(replaceable)
-msgid "controller"
-msgstr ""
-
 #: ./doc/install-guide/ch_clients.xml:37(para)
 msgid "<filename>demo-openrc.sh</filename> for the normal user: <placeholder-1/>"
 msgstr ""
 
+#: ./doc/install-guide/ch_basics.xml:5(title)
+msgid "Basic environment configuration"
+msgstr ""
+
+#: ./doc/install-guide/ch_basics.xml:6(para)
+msgid "This chapter explains how to configure each node in the <link linkend=\"architecture_example-architectures\">example architectures</link> including the <link linkend=\"example-architecture-with-legacy-networking\"> two-node architecture with legacy networking</link> and <link linkend=\"example-architecture-with-neutron-networking\">three-node architecture with OpenStack Networking (neutron)</link>."
+msgstr ""
+
+#: ./doc/install-guide/ch_basics.xml:13(para)
+msgid "Although most environments include OpenStack Identity, Image Service, Compute, at least one networking service, and the dashboard, OpenStack Object Storage can operate independently of most other services. If your use case only involves Object Storage, you can skip to <xref linkend=\"object-storage-system-requirements\"/>. However, the dashboard will not work without at least OpenStack Image Service and Compute."
+msgstr ""
+
+#: ./doc/install-guide/ch_basics.xml:22(para)
+msgid "You must use an account with administrative privileges to configure each node. Either run the commands as the <literal>root</literal> user or configure the <literal>sudo</literal> utility."
+msgstr ""
+
+#: ./doc/install-guide/section_dashboard-system-reqs.xml:6(title)
+msgid "System requirements"
+msgstr ""
+
+#: ./doc/install-guide/section_dashboard-system-reqs.xml:7(para)
+msgid "Before you install the OpenStack dashboard, you must meet the following system requirements:"
+msgstr ""
+
+#: ./doc/install-guide/section_dashboard-system-reqs.xml:11(para)
+msgid "OpenStack Compute installation. Enable the Identity Service for user and project management."
+msgstr ""
+
+#: ./doc/install-guide/section_dashboard-system-reqs.xml:13(para)
+msgid "Note the URLs of the Identity Service and Compute endpoints."
+msgstr ""
+
+#: ./doc/install-guide/section_dashboard-system-reqs.xml:17(para)
+msgid "Identity Service user with sudo privileges. Because Apache does not serve content from a root user, users must run the dashboard as an Identity Service user with sudo privileges."
+msgstr ""
+
+#: ./doc/install-guide/section_dashboard-system-reqs.xml:23(para)
+msgid "Python 2.6 or 2.7. The Python version must support Django. The Python version should run on any system, including Mac OS X. Installation prerequisites might differ by platform."
+msgstr ""
+
+#: ./doc/install-guide/section_dashboard-system-reqs.xml:29(para)
+msgid "Then, install and configure the dashboard on a node that can contact the Identity Service."
+msgstr ""
+
+#: ./doc/install-guide/section_dashboard-system-reqs.xml:31(para)
+msgid "Provide users with the following information so that they can access the dashboard through a web browser on their local machine:"
+msgstr ""
+
+#: ./doc/install-guide/section_dashboard-system-reqs.xml:36(para)
+msgid "The public IP address from which they can access the dashboard"
+msgstr ""
+
+#: ./doc/install-guide/section_dashboard-system-reqs.xml:40(para)
+msgid "The user name and password with which they can access the dashboard"
+msgstr ""
+
+#: ./doc/install-guide/section_dashboard-system-reqs.xml:44(para)
+msgid "Your web browser, and that of your users, must support HTML5 and have cookies and JavaScript enabled."
+msgstr ""
+
+#: ./doc/install-guide/section_dashboard-system-reqs.xml:48(para)
+msgid "To use the VNC client with the dashboard, the browser must support HTML5 Canvas and HTML5 WebSockets."
+msgstr ""
+
+#: ./doc/install-guide/section_dashboard-system-reqs.xml:50(para)
+msgid "For details about browsers that support noVNC, see <link href=\"https://github.com/kanaka/noVNC/blob/master/README.md\">https://github.com/kanaka/noVNC/blob/master/README.md</link>, and <link href=\"https://github.com/kanaka/noVNC/wiki/Browser-support\">https://github.com/kanaka/noVNC/wiki/Browser-support</link>, respectively."
+msgstr ""
+
 #: ./doc/install-guide/section_launch-instance-nova.xml:6(title)
 msgid "Launch an instance with legacy networking (nova-network)"
 msgstr ""
@@ -731,10 +2181,6 @@ msgstr ""
 msgid "Most cloud images support <glossterm>public key authentication</glossterm> rather than conventional username/password authentication. Before launching an instance, you must generate a public/private key pair using <placeholder-1/> and add the public key to your OpenStack environment."
 msgstr ""
 
-#: ./doc/install-guide/section_launch-instance-nova.xml:15(para) ./doc/install-guide/section_launch-instance-neutron.xml:15(para) ./doc/install-guide/section_neutron-initial-networks.xml:132(para)
-msgid "Source the <literal>demo</literal> tenant credentials:"
-msgstr ""
-
 #: ./doc/install-guide/section_launch-instance-nova.xml:19(para) ./doc/install-guide/section_launch-instance-neutron.xml:19(para)
 msgid "Generate a key pair:"
 msgstr ""
@@ -875,256 +2321,422 @@ msgstr ""
 msgid "If your instance does not launch or seem to work as you expect, see the <link href=\"http://docs.openstack.org/ops\"><citetitle>OpenStack Operations Guide</citetitle></link> for more information or use one of the <link linkend=\"app_community_support\">many other options</link> to seek assistance. We want your environment to work!"
 msgstr ""
 
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:30(None)
-msgid "@@image: 'figures/debconf-screenshots/service_keystone_authtoken_server_hostname.png'; md5=aafd53894e1d960531d4901123952117"
+#: ./doc/install-guide/ch_trove.xml:6(title)
+msgid "Add the Database service"
+msgstr ""
+
+#: ./doc/install-guide/ch_trove.xml:7(para)
+msgid "Use the <glossterm baseform=\"Database Service\">Database module</glossterm> to create cloud database resources. The integrated project name is <glossterm>trove</glossterm>."
+msgstr ""
+
+#: ./doc/install-guide/ch_trove.xml:10(para)
+msgid "This chapter is a work in progress. It may contain incorrect information, and will be updated frequently."
+msgstr ""
+
+#: ./doc/install-guide/section_nova-networking-compute-node.xml:6(para)
+msgid "This section covers deployment of a simple <glossterm>flat network</glossterm> that provides IP addresses to your instances via <glossterm>DHCP</glossterm>. If your environment includes multiple compute nodes, the <glossterm>multi-host</glossterm> feature provides redundancy by spreading network functions across compute nodes."
+msgstr ""
+
+#: ./doc/install-guide/section_nova-networking-compute-node.xml:13(title)
+msgid "To install legacy networking components"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-networking-compute-node.xml:21(title) ./doc/install-guide/section_nova-networking-controller-node.xml:9(title)
+msgid "To configure legacy networking"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-networking-compute-node.xml:23(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:189(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:287(para) ./doc/install-guide/section_nova-networking-controller-node.xml:11(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:325(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:369(para) ./doc/install-guide/section_heat-install.xml:94(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:192(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:226(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:262(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:355(para) ./doc/install-guide/section_ceilometer-glance.xml:20(para)
+msgid "Run the following commands:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-networking-compute-node.xml:24(para) ./doc/install-guide/section_nova-networking-compute-node.xml:57(para)
+msgid "Replace <replaceable>INTERFACE_NAME</replaceable> with the actual interface name for the external network. For example, <emphasis>eth1</emphasis> or <emphasis>ens224</emphasis>."
+msgstr ""
+
+#: ./doc/install-guide/section_nova-networking-compute-node.xml:55(para) ./doc/install-guide/section_nova-networking-controller-node.xml:18(para)
+msgid "Edit the <filename>/etc/nova/nova.conf</filename> file and add the following keys to the <literal>[DEFAULT]</literal> section:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-networking-compute-node.xml:77(para)
+msgid "Restart the services:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-networking-compute-node.xml:80(para)
+msgid "Start the services and configure them to start when the system boots:"
 msgstr ""
 
 #. When image changes, this message will be marked fuzzy or untranslated for you.
 #. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:37(None)
-msgid "@@image: 'figures/debconf-screenshots/service_keystone_authtoken_admin_tenant_name.png'; md5=a935563e4fba9b00040e35cdcfffc732"
+#: ./doc/install-guide/section_glance-install.xml:38(None)
+msgid "@@image: 'figures/debconf-screenshots/glance-common_pipeline_flavor.png'; md5=78bef92c36a140ad042074f6345d8917"
 msgstr ""
 
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:44(None)
-msgid "@@image: 'figures/debconf-screenshots/service_keystone_authtoken_tenant_admin_user.png'; md5=fe3dc93c591b3e9783d4d05556efcf25"
+#: ./doc/install-guide/section_glance-install.xml:5(title)
+msgid "Install the Image Service"
 msgstr ""
 
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:51(None)
-msgid "@@image: 'figures/debconf-screenshots/service_keystone_authtoken_admin_password.png'; md5=0c30c80315d5e636dbe93a938fc2822b"
+#: ./doc/install-guide/section_glance-install.xml:6(para)
+msgid "The OpenStack Image Service acts as a registry for virtual disk images. Users can add new images or take a snapshot of an image from an existing server for immediate storage. Use snapshots for back up and as templates to launch new servers. You can store registered images in Object Storage or in other locations. For example, you can store images in simple file systems or external web servers."
 msgstr ""
 
-#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:6(title)
-msgid "Services and the [keystone_authtoken]"
+#: ./doc/install-guide/section_glance-install.xml:14(para)
+msgid "This procedure assumes you set the appropriate environment variables to your credentials as described in <xref linkend=\"keystone-verify\"/>."
 msgstr ""
 
-#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:7(para)
-msgid "Because most OpenStack services must access the Identity Service, you must configure the IP address of the <code>keystone</code> server to be able to access it. You must also configure the <code>admin_tenant_name</code>, <code>admin_user</code>, and <code>admin_password</code> options for each service to work."
+#: ./doc/install-guide/section_glance-install.xml:20(para)
+msgid "Install the Image Service on the controller node:"
 msgstr ""
 
-#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:13(para)
-msgid "Generally, this section looks like this:"
+#: ./doc/install-guide/section_glance-install.xml:27(para)
+msgid "Respond to prompts for <link linkend=\"debconf-dbconfig-common\">database management</link>, <link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> settings</link>, <link linkend=\"debconf-rabbitqm\">RabbitMQ credentials</link> and <link linkend=\"debconf-api-endpoints\">API endpoint</link> registration. You must also select the caching type:"
 msgstr ""
 
-#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:21(para)
-msgid "The debconf system helps users configure the <code>auth_host</code>, <code>admin_tenant_name</code>, <code>admin_user</code> and <code>admin_password</code> options."
+#: ./doc/install-guide/section_glance-install.xml:43(para)
+msgid "The Image Service stores information about images in a database. The examples in this guide use the MySQL database that is used by other OpenStack services."
 msgstr ""
 
-#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:25(para)
-msgid "The following screens show an example Image Service configuration:"
+#: ./doc/install-guide/section_glance-install.xml:46(para)
+msgid "Configure the location of the database. The Image Service provides the <systemitem class=\"service\">glance-api</systemitem> and <systemitem class=\"service\">glance-registry</systemitem> services, each with its own configuration file. You must update both configuration files throughout this section. Replace <replaceable>GLANCE_DBPASS</replaceable> with your Image Service database password."
 msgstr ""
 
-#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:55(para)
-msgid "This information is stored in the configuration file for each service. For example:"
+#: ./doc/install-guide/section_glance-install.xml:55(replaceable) ./doc/install-guide/section_glance-install.xml:57(replaceable) ./doc/install-guide/section_glance-install.xml:120(replaceable) ./doc/install-guide/section_glance-install.xml:122(replaceable)
+msgid "GLANCE_DBPASS"
 msgstr ""
 
-#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:63(para)
-msgid "The Debian OpenStack packages offer automation for this, so OpenStack users do not have to manually edit the configuration files."
+#: ./doc/install-guide/section_glance-install.xml:58(para)
+msgid "Edit <filename>/etc/glance/glance-api.conf</filename> and <filename>/etc/glance/glance-registry.conf</filename> and edit the <literal>[database]</literal> section of each file:"
 msgstr ""
 
-#: ./doc/install-guide/ch_swift.xml:6(title)
-msgid "Add Object Storage"
+#: ./doc/install-guide/section_glance-install.xml:70(para) ./doc/install-guide/section_glance-install.xml:77(para) ./doc/install-guide/section_glance-install.xml:95(para)
+msgid "Configure the Image Service to use the message broker:"
 msgstr ""
 
-#: ./doc/install-guide/ch_swift.xml:7(para)
-msgid "The OpenStack Object Storage services work together to provide object storage and retrieval through a REST API. For this example architecture, you must have already installed the Identity Service, also known as Keystone."
+#: ./doc/install-guide/section_glance-install.xml:80(para)
+msgid "Edit the <filename>/etc/glance/glance-api.conf</filename> file and add the following keys to the <literal>[DEFAULT]</literal> section:"
 msgstr ""
 
-#: ./doc/install-guide/ch_swift.xml:31(para)
-msgid "Your OpenStack environment now includes Object Storage. You can <link linkend=\"launch-instance\">launch an instance</link> or add more services to your environment in the following chapters."
+#: ./doc/install-guide/section_glance-install.xml:83(para) ./doc/install-guide/section_glance-install.xml:96(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:106(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:132(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:183(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:209(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:109(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:135(para)
+msgid "Replace <replaceable>RABBIT_PASS</replaceable> with the password you chose for the <literal>guest</literal> account in <application>RabbitMQ</application>."
 msgstr ""
 
-#: ./doc/install-guide/section_neutron-concepts.xml:6(title)
-msgid "Networking concepts"
+#: ./doc/install-guide/section_glance-install.xml:108(para)
+msgid "By default, the Ubuntu packages create an SQLite database. Delete the <filename>glance.sqlite</filename> file created in the <filename>/var/lib/glance/</filename> directory so that it does not get used by mistake:"
 msgstr ""
 
-#: ./doc/install-guide/section_neutron-concepts.xml:7(para)
-msgid "OpenStack Networking (neutron) manages all of the networking facets for the Virtual Networking Infrastructure (VNI) and the access layer aspects of the Physical Networking Infrastructure (PNI) in your OpenStack environment. OpenStack Networking allows tenants to create advanced virtual network topologies including services such as <glossterm baseform=\"firewall\">firewalls</glossterm>, <glossterm baseform=\"load balancer\">load balancers</glossterm>, and <glossterm baseform=\"virtual private network (VPN)\"> virtual private networks (VPNs)</glossterm>."
+#: ./doc/install-guide/section_glance-install.xml:115(para)
+msgid "Use the password you created to log in as root and create a <literal>glance</literal> database user:"
 msgstr ""
 
-#: ./doc/install-guide/section_neutron-concepts.xml:16(para)
-msgid "Networking provides the following object abstractions: networks, subnets, and routers. Each has functionality that mimics its physical counterpart: networks contain subnets, and routers route traffic between different subnet and networks."
+#: ./doc/install-guide/section_glance-install.xml:125(para)
+msgid "Create the database tables for the Image Service:"
 msgstr ""
 
-#: ./doc/install-guide/section_neutron-concepts.xml:20(para)
-msgid "Any given Networking set up has at least one external network. This network, unlike the other networks, is not merely a virtually defined network. Instead, it represents the view into a slice of the external network that is accessible outside the OpenStack installation. IP addresses on the Networking external network are accessible by anybody physically on the outside network. Because this network merely represents a slice of the outside network, DHCP is disabled on this network."
+#: ./doc/install-guide/section_glance-install.xml:129(para)
+msgid "Create a <literal>glance</literal> user that the Image Service can use to authenticate with the Identity service. Choose a password and specify an email address for the <literal>glance</literal> user. Use the <literal>service</literal> tenant and give the user the <literal>admin</literal> role:"
 msgstr ""
 
-#: ./doc/install-guide/section_neutron-concepts.xml:28(para)
-msgid "In addition to external networks, any Networking set up has one or more internal networks. These software-defined networks connect directly to the VMs. Only the VMs on any given internal network, or those on subnets connected through interfaces to a similar router, can access VMs connected to that network directly."
+#: ./doc/install-guide/section_glance-install.xml:135(replaceable) ./doc/install-guide/section_glance-install.xml:159(replaceable) ./doc/install-guide/section_glance-install.xml:175(replaceable) ./doc/install-guide/section_glance-install.xml:194(replaceable)
+msgid "GLANCE_PASS"
 msgstr ""
 
-#: ./doc/install-guide/section_neutron-concepts.xml:33(para)
-msgid "For the outside network to access VMs, and vice versa, routers between the networks are needed. Each router has one gateway that is connected to a network and many interfaces that are connected to subnets. Like a physical router, subnets can access machines on other subnets that are connected to the same router, and machines can access the outside network through the gateway for the router."
+#: ./doc/install-guide/section_glance-install.xml:136(replaceable)
+msgid "glance@example.com"
 msgstr ""
 
-#: ./doc/install-guide/section_neutron-concepts.xml:40(para)
-msgid "Additionally, you can allocate IP addresses on external networks to ports on the internal network. Whenever something is connected to a subnet, that connection is called a port. You can associate external network IP addresses with ports to VMs. This way, entities on the outside network can access VMs."
+#: ./doc/install-guide/section_glance-install.xml:140(para)
+msgid "Configure the Image Service to use the Identity Service for authentication."
 msgstr ""
 
-#: ./doc/install-guide/section_neutron-concepts.xml:45(para)
-msgid "Networking also supports <emphasis role=\"italic\">security groups</emphasis>. Security groups enable administrators to define firewall rules in groups. A VM can belong to one or more security groups, and Networking applies the rules in those security groups to block or unblock ports, port ranges, or traffic types for that VM."
+#: ./doc/install-guide/section_glance-install.xml:142(para)
+msgid "Run the following commands and replace <replaceable>GLANCE_PASS</replaceable> with the password you chose for the <literal>glance</literal> user in the Identity Service:"
 msgstr ""
 
-#: ./doc/install-guide/section_neutron-concepts.xml:51(para)
-msgid "Each plug-in that Networking uses has its own concepts. While not vital to operating Networking, understanding these concepts can help you set up Networking. All Networking installations use a core plug-in and a security group plug-in (or just the No-Op security group plug-in). Additionally, Firewall-as-a-service (FWaaS) and Load-balancing-as-a-service (LBaaS) plug-ins are available."
+#: ./doc/install-guide/section_glance-install.xml:178(para)
+msgid "Edit the <filename>/etc/glance/glance-api.conf</filename> and <filename>/etc/glance/glance-registry.conf</filename> files. Replace <replaceable>GLANCE_PASS</replaceable> with the password you chose for the <literal>glance</literal> user in the Identity service."
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:10(title)
-msgid "Install the Telemetry module"
+#: ./doc/install-guide/section_glance-install.xml:185(para)
+msgid "Add or modify the following keys under the <literal>[keystone_authtoken]</literal> section:"
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:12(para)
-msgid "Telemetry provides an API service that provides a collector and a range of disparate agents. Before you can install these agents on nodes such as the compute node, you must use this procedure to install the core components on the controller node."
+#: ./doc/install-guide/section_glance-install.xml:197(para)
+msgid "Modify the following key under the <literal>[paste_deploy]</literal> section:"
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:18(para)
-msgid "Install the Telemetry service on the controller node:"
+#: ./doc/install-guide/section_glance-install.xml:206(para)
+msgid "Register the Image Service with the Identity service so that other OpenStack services can locate it. Register the service and create the endpoint:"
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:30(para)
-msgid "Respond to the prompts for <link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> settings</link>, <link linkend=\"debconf-rabbitqm\">RabbitMQ credentials</link> and <link linkend=\"debconf-api-endpoints\">API endpoint</link> registration."
+#: ./doc/install-guide/section_glance-install.xml:218(para)
+msgid "Restart the <systemitem class=\"service\">glance</systemitem> service with its new settings:"
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:38(para)
-msgid "The Telemetry service uses a database to store information. Specify the location of the database in the configuration file. The examples use a MongoDB database on the controller node:"
+#: ./doc/install-guide/section_glance-install.xml:224(para)
+msgid "Start the <systemitem class=\"service\">glance-api</systemitem> and <systemitem class=\"service\">glance-registry</systemitem> services and configure them to start when the system boots:"
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:46(para)
-msgid "By default MongoDB is configured to create several 1GB files in the /var/lib/mongodb/journal/ directory to support database journaling."
+#: ./doc/install-guide/section_dashboard-install.xml:7(title)
+msgid "Install the dashboard"
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:51(para)
-msgid "If you need to minimize the space allocated to support database journaling then set the <option>smallfiles</option> configuration key to <literal>true</literal> in the <filename>/etc/mongodb.conf</filename> configuration file. This configuration reduces the size of each journaling file to 512MB."
+#: ./doc/install-guide/section_dashboard-install.xml:8(para)
+msgid "Before you can install and configure the dashboard, meet the requirements in <xref linkend=\"dashboard-system-requirements\"/>."
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:59(para)
-msgid "As the files are created the first time the MongoDB service starts you must stop the service and remove the files for this change to take effect:"
+#: ./doc/install-guide/section_dashboard-install.xml:12(para)
+msgid "When you install only Object Storage and the Identity Service, even if you install the dashboard, it does not pull up projects and is unusable."
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:67(para)
-msgid "For more information on the <option>smallfiles</option> configuration key refer to the MongoDB documentation at <link href=\"http://docs.mongodb.org/manual/reference/configuration-options/#smallfiles\"/>."
+#: ./doc/install-guide/section_dashboard-install.xml:16(para)
+msgid "For more information about how to deploy the dashboard, see <link href=\"http://docs.openstack.org/developer/horizon/topics/deployment.html\">deployment topics in the developer documentation</link>."
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:72(para)
-msgid "For instructions detailing the steps to disable database journaling entirely refer to <link href=\"http://docs.mongodb.org/manual/tutorial/manage-journaling/\"/>."
+#: ./doc/install-guide/section_dashboard-install.xml:22(para)
+msgid "Install the dashboard on the node that can contact the Identity Service as root:"
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:80(para)
-msgid "Configure MongoDB to make it listen on the controller management IP address. Edit the <filename>/etc/mongodb.conf</filename> file and modify the <literal>bind_ip</literal> key:"
+#: ./doc/install-guide/section_dashboard-install.xml:28(title)
+msgid "Note for Ubuntu users"
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:86(para)
-msgid "Restart the MongoDB service to apply the configuration change:"
+#: ./doc/install-guide/section_dashboard-install.xml:30(para)
+msgid "Remove the <literal>openstack-dashboard-ubuntu-theme</literal> package. This theme prevents translations, several menus as well as the network map from rendering correctly: <placeholder-1/>"
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:90(para)
-msgid "Start the MongoDB server and configure it to start when the system boots:"
+#: ./doc/install-guide/section_dashboard-install.xml:39(title)
+msgid "Note for Debian users"
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:100(para)
-msgid "Create the database and a <literal>ceilometer</literal> database user:"
+#: ./doc/install-guide/section_dashboard-install.xml:40(para)
+msgid "To install the Apache package:"
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:105(replaceable) ./doc/install-guide/section_ceilometer-install.xml:111(replaceable) ./doc/install-guide/section_ceilometer-install.xml:118(replaceable)
-msgid "CEILOMETER_DBPASS"
+#: ./doc/install-guide/section_dashboard-install.xml:42(para)
+msgid "This command installs and configures Apache correctly, provided that the user asks for it during the <package>debconf</package> prompts. The default SSL certificate is self-signed, and it is probably wise to have it signed by a root Certificate Authority (CA)."
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:109(para)
-msgid "Configure the Telemetry service to use the database:"
+#: ./doc/install-guide/section_dashboard-install.xml:51(para)
+msgid "Modify the value of <literal>CACHES['default']['LOCATION']</literal> in <filename os=\"ubuntu;debian\">/etc/openstack-dashboard/local_settings.py</filename><filename os=\"centos;fedora;rhel\">/etc/openstack-dashboard/local_settings</filename><filename os=\"opensuse;sles\">/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py</filename> to match the ones set in <filename os=\"ubuntu;debian\">/etc/memcached.conf</filename><filename os=\"centos;fedora;rhel;opensuse;sles\">/etc/sysconfig/memcached</filename>."
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:112(para)
-msgid "Edit the <filename>/etc/ceilometer/ceilometer.conf</filename> file and change the <literal>[database]</literal> section:"
+#: ./doc/install-guide/section_dashboard-install.xml:63(para)
+msgid "Open <filename os=\"ubuntu;debian\">/etc/openstack-dashboard/local_settings.py</filename><filename os=\"centos;fedora;rhel\">/etc/openstack-dashboard/local_settings</filename> and look for this line:"
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:122(para)
-msgid "You must define a secret key that is used as a shared secret among Telemetry service nodes. Use <placeholder-1/> to generate a random token and store it in the configuration file:"
+#: ./doc/install-guide/section_dashboard-install.xml:76(title) ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:29(td)
+msgid "Notes"
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:129(para)
-msgid "For SUSE Linux Enterprise, run the following command:"
+#: ./doc/install-guide/section_dashboard-install.xml:79(para)
+msgid "The address and port must match the ones set in <filename os=\"ubuntu;debian\">/etc/memcached.conf</filename><filename os=\"centos;fedora;rhel;opensuse;sles\">/etc/sysconfig/memcached</filename>."
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:133(para)
-msgid "Edit the <filename>/etc/ceilometer/ceilometer.conf</filename> file and change the <literal>[publisher]</literal> section. Replace <replaceable>CEILOMETER_TOKEN</replaceable> with the results of the <literal>openssl</literal> command:"
+#: ./doc/install-guide/section_dashboard-install.xml:84(para)
+msgid "If you change the memcached settings, you must restart the Apache web server for the changes to take effect."
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:140(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:62(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:70(replaceable)
-msgid "CEILOMETER_TOKEN"
+#: ./doc/install-guide/section_dashboard-install.xml:89(para)
+msgid "You can use options other than memcached option for session storage. Set the session back-end through the <parameter>SESSION_ENGINE</parameter> option."
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:144(para) ./doc/install-guide/section_ceilometer-nova.xml:74(para)
-msgid "Configure the RabbitMQ access:"
+#: ./doc/install-guide/section_dashboard-install.xml:96(para)
+msgid "To change the timezone, use the dashboard or edit the <filename os=\"centos;fedora;rhel\">/etc/openstack-dashboard/local_settings</filename><filename os=\"ubuntu;debian\">/etc/openstack-dashboard/local_settings.py</filename><filename os=\"opensuse;sles\">/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py</filename> file."
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:146(replaceable) ./doc/install-guide/section_ceilometer-install.xml:149(replaceable) ./doc/install-guide/section_trove-install.xml:105(replaceable) ./doc/install-guide/section_trove-install.xml:125(replaceable) ./doc/install-guide/section_trove-install.xml:127(replaceable) ./doc/install-guide/section_trove-install.xml:129(replaceable) ./doc/install-guide/section_trove-install.xml:221(replaceable) ./doc/install-guide/section_nova-controller.xml:70(replaceable) ./doc/install-guide/section_nova-controller.xml:78(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:198(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:207(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:193(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:216(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:153(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:180(replaceable) ./doc/install-guide/section_ceilometer-glance.xml:18(replaceable) ./doc/install-guide/section_ceilometer-glance.xml:24(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:149(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:158(replaceable) ./doc/install-guide/section_cinder-node.xml:153(replaceable) ./doc/install-guide/section_cinder-node.xml:174(replaceable) ./doc/install-guide/section_cinder-controller.xml:123(replaceable) ./doc/install-guide/section_cinder-controller.xml:145(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:119(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:142(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:116(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:139(replaceable) ./doc/install-guide/section_basics-queue.xml:77(replaceable) ./doc/install-guide/section_heat-install.xml:93(replaceable) ./doc/install-guide/section_heat-install.xml:96(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:76(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:80(replaceable) ./doc/install-guide/section_nova-compute.xml:115(replaceable) ./doc/install-guide/section_nova-compute.xml:121(replaceable) ./doc/install-guide/section_glance-install.xml:90(replaceable) ./doc/install-guide/section_glance-install.xml:104(replaceable)
-msgid "RABBIT_PASS"
+#: ./doc/install-guide/section_dashboard-install.xml:105(para)
+msgid "Change the following parameter: <code>TIME_ZONE = \"UTC\"</code>"
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:147(para) ./doc/install-guide/section_ceilometer-install.xml:166(para) ./doc/install-guide/section_ceilometer-nova.xml:77(para) ./doc/install-guide/section_ceilometer-nova.xml:130(para)
-msgid "Edit the <filename>/etc/ceilometer/ceilometer.conf</filename> file and update the <literal>[DEFAULT]</literal> section:"
+#: ./doc/install-guide/section_dashboard-install.xml:112(para)
+msgid "Update the <literal>ALLOWED_HOSTS</literal> in <filename>local_settings.py</filename> to include the addresses you wish to access the dashboard from."
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:153(para)
-msgid "Configure the Qpid access:"
+#: ./doc/install-guide/section_dashboard-install.xml:116(para)
+msgid "Edit <filename os=\"centos;fedora;rhel\">/etc/openstack-dashboard/local_settings</filename><filename os=\"ubuntu;debian\">/etc/openstack-dashboard/local_settings.py</filename><filename os=\"opensuse;sles\">/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py</filename>:"
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:159(para)
-msgid "Configure the collector dispatcher:"
+#: ./doc/install-guide/section_dashboard-install.xml:127(para)
+msgid "This guide assumes that you are running the Dashboard on the controller node. You can easily run the dashboard on a separate server, by changing the appropriate settings in <filename>local_settings.py</filename>."
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:165(para) ./doc/install-guide/section_ceilometer-nova.xml:129(para)
-msgid "Configure the log directory."
+#: ./doc/install-guide/section_dashboard-install.xml:132(para)
+msgid "Edit <filename os=\"centos;fedora;rhel\">/etc/openstack-dashboard/local_settings</filename><filename os=\"ubuntu;debian\">/etc/openstack-dashboard/local_settings.py</filename><filename os=\"opensuse;sles\">/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py</filename> and change <literal>OPENSTACK_HOST</literal> to the hostname of your Identity Service:"
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:173(para)
-msgid "Create a <literal>ceilometer</literal> user that the Telemetry service uses to authenticate with the Identity Service. Use the <literal>service</literal> tenant and give the user the <literal>admin</literal> role:"
+#: ./doc/install-guide/section_dashboard-install.xml:144(para)
+msgid "Setup Apache configuration: <placeholder-1/>"
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:177(replaceable) ./doc/install-guide/section_ceilometer-install.xml:206(replaceable) ./doc/install-guide/section_ceilometer-install.xml:214(replaceable) ./doc/install-guide/section_ceilometer-install.xml:226(replaceable) ./doc/install-guide/section_ceilometer-install.xml:233(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:99(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:105(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:118(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:125(replaceable)
-msgid "CEILOMETER_PASS"
+#: ./doc/install-guide/section_dashboard-install.xml:151(para)
+msgid "By default, the <systemitem>openstack-dashboard</systemitem> package enables a database as session store. Before you continue, either change the session store set up as described in <xref linkend=\"dashboard-sessions\"/> or finish the setup of the database session store as explained in <xref linkend=\"dashboard-session-database\"/>."
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:177(replaceable)
-msgid "ceilometer@example.com"
+#: ./doc/install-guide/section_dashboard-install.xml:161(para)
+msgid "Ensure that the SELinux policy of the system is configured to allow network connections to the HTTP server."
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:181(para)
-msgid "Configure the Telemetry service to authenticate with the Identity Service."
+#: ./doc/install-guide/section_dashboard-install.xml:168(para)
+msgid "Start the Apache web server and memcached:"
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:183(para)
-msgid "Set the <option>auth_strategy</option> value to <literal>keystone</literal> in the <filename>/etc/ceilometer/ceilometer.conf</filename> file:"
+#: ./doc/install-guide/section_dashboard-install.xml:181(para)
+msgid "You can now access the dashboard at <uri os=\"ubuntu\">http://controller/horizon</uri><uri os=\"debian\">https://controller/</uri><uri os=\"centos;fedora;rhel\">http://controller/dashboard</uri><uri os=\"opensuse;sles\">http://controller</uri>."
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:193(para)
-msgid "Add the credentials to the configuration files for the Telemetry service:"
+#: ./doc/install-guide/section_dashboard-install.xml:188(para)
+msgid "Login with credentials for any user that you created with the OpenStack Identity Service."
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:215(para) ./doc/install-guide/section_ceilometer-nova.xml:108(para)
-msgid "Edit the <filename>/etc/ceilometer/ceilometer.conf</filename> file and change the <literal>[keystone_authtoken]</literal> section:"
+#: ./doc/install-guide/section_basics-networking.xml:6(title)
+msgid "Networking"
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:227(para) ./doc/install-guide/section_ceilometer-nova.xml:119(para)
-msgid "Also set the <literal>[service_credentials]</literal> section:"
+#: ./doc/install-guide/section_basics-networking.xml:7(para)
+msgid "After installing the operating system on each node for the architecture that you choose to deploy, you must configure the network interfaces. We recommend that you disable any automated network management tools and manually edit the appropriate configuration files for your distribution. For more information on how to configure networking on your distribution, see the <link os=\"ubuntu\" href=\"https://help.ubuntu.com/lts/serverguide/network-configuration.html\">documentation.</link><link os=\"debian\" href=\"https://wiki.debian.org/NetworkConfiguration\">documentation.</link><link os=\"rhel;centos;fedora\" href=\"https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s1-networkscripts-interfaces.html\">documentation.</link><link os=\"sles;opensuse\" href=\"https://www.suse.com/documentation/sles11/book_sle_admin/data/sec_basicnet_manconf.html\">SLES 11</link><phrase os=\"sles;opensuse\"> or </phrase><link os=\"sles;opensuse\" href=\"http://activedoc.opensuse.org/book/opensuse-reference/chapter-13-basic-networking\">openSUSE documentation.</link>"
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:236(para)
-msgid "Register the Telemetry service with the Identity Service so that other OpenStack services can locate it. Use the <placeholder-1/> command to register the service and specify the endpoint:"
+#: ./doc/install-guide/section_basics-networking.xml:30(title)
+msgid "To disable <systemitem class=\"service\">NetworkManager</systemitem> and enable the <systemitem class=\"service\">network</systemitem> service:"
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:249(para)
-msgid "Restart the services with their new settings:"
+#: ./doc/install-guide/section_basics-networking.xml:41(title)
+msgid "To disable <systemitem class=\"service\">NetworkManager</systemitem>:"
 msgstr ""
 
-#: ./doc/install-guide/section_ceilometer-install.xml:258(para)
-msgid "Start the <systemitem class=\"service\">openstack-ceilometer-api</systemitem>, <systemitem class=\"service\" os=\"opensuse;sles\">openstack-ceilometer-agent-central</systemitem><systemitem class=\"service\" os=\"rhel;fedora;centos\">openstack-ceilometer-central</systemitem>, <systemitem class=\"service\">openstack-ceilometer-collector</systemitem>, <systemitem class=\"service\" os=\"opensuse;sles\">openstack-ceilometer-alarm-evaluator</systemitem>, and <systemitem class=\"service\" os=\"opensuse;sles\">openstack-ceilometer-alarm-notifier</systemitem> services and configure them to start when the system boots:"
+#: ./doc/install-guide/section_basics-networking.xml:43(para)
+msgid "Use the YaST network module:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking.xml:45(para)
+msgid "For more information, see the <link href=\"https://www.suse.com/documentation/sles11/book_sle_admin/data/sec_nm_activate.html\">SLES </link> or the <link href=\"http://activedoc.opensuse.org/book/opensuse-reference/chapter-13-basic-networking#sec.basicnet.yast.netcard.global\"> openSUSE documentation</link>."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking.xml:53(para)
+msgid "RHEL and derivatives including CentOS and Scientific Linux enable a restrictive <glossterm>firewall</glossterm> by default. During this installation, certain steps will fail unless you alter or disable the firewall. For further information about securing your installation, refer to the <link href=\"http://docs.openstack.org/sec/\"> OpenStack Security Guide</link>."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking.xml:60(para)
+msgid "On Fedora, <literal>firewalld</literal> replaces <literal>iptables</literal> as the default firewall system. While you can use <literal>firewalld</literal> successfully, this guide references <literal>iptables</literal> for compatibility with other distributions."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking.xml:66(title)
+msgid "To disable <literal>firewalld</literal> and enable <literal>iptables</literal>:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking.xml:75(para)
+msgid "Proceed to network configuration for the example <link linkend=\"basics-networking-neutron\">OpenStack Networking (neutron) </link> or <link linkend=\"basics-networking-nova\">legacy networking (nova-network)</link> architecture."
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-verify.xml:5(title)
+msgid "Verify the Block Storage installation"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-verify.xml:6(para)
+msgid "To verify that the Block Storage is installed and configured properly, create a new volume."
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-verify.xml:8(para)
+msgid "For more information about how to manage volumes, see the <link href=\"http://docs.openstack.org/user-guide/content/index.html\"><citetitle>OpenStack User Guide</citetitle></link>."
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-verify.xml:13(para)
+msgid "Source the <filename>demo-openrc.sh</filename> file:"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-verify.xml:18(para)
+msgid "Use the <placeholder-1/> command to create a new volume:"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-verify.xml:40(para)
+msgid "Make sure that the volume has been correctly created with the <placeholder-1/> command:"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-verify.xml:48(para)
+msgid "If the status value is not <literal>available</literal>, the volume creation failed. Check the log files in the <filename>/var/log/cinder/</filename> directory on the controller and volume nodes to get information about the failure."
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-node.xml:6(title)
+msgid "Configure a Block Storage service node"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-node.xml:7(para)
+msgid "After you configure the services on the controller node, configure a second system to be a Block Storage service node. This node contains the disk that serves volumes."
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-node.xml:14(para)
+msgid "Use the instructions in <xref linkend=\"ch_basics\"/> to configure the system. Note the following differences from the installation instructions for the controller node:"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-node.xml:19(para)
+msgid "Set the host name to <literal>block1</literal> and use <literal>10.0.0.41</literal> as IP address on the management network interface. Ensure that the IP addresses and host names for both controller node and Block Storage service node are listed in the <filename>/etc/hosts</filename> file on each system."
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-node.xml:27(para)
+msgid "Follow the instructions in <xref linkend=\"basics-ntp\"/> to synchronize from the controller node."
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-node.xml:33(para)
+msgid "Install the required LVM packages, if they are not already installed:"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-node.xml:38(para)
+msgid "Create the LVM physical and logical volumes. This guide assumes a second disk <literal>/dev/sdb</literal> that is used for this purpose:"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-node.xml:45(para)
+msgid "Add a filter entry to the <literal>devices</literal> section in the <filename>/etc/lvm/lvm.conf</filename> file to keep LVM from scanning devices used by virtual machines:"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-node.xml:55(para)
+msgid "You must add required physical volumes for LVM on the Block Storage host. Run the <placeholder-1/> command to get a list or required volumes."
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-node.xml:59(para)
+msgid "Each item in the filter array starts with either an <literal>a</literal> for accept, or an <literal>r</literal> for reject. The physical volumes that are required on the Block Storage host have names that begin with <literal>a</literal>. The array must end with \"<literal>r/.*/</literal>\" to reject any device not listed."
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-node.xml:66(para)
+msgid "In this example, <literal>/dev/sda1</literal> is the volume where the volumes for the operating system for the node reside, while <literal>/dev/sdb</literal> is the volume reserved for <literal>cinder-volumes</literal>."
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-node.xml:72(para)
+msgid "After you configure the operating system, install the appropriate packages for the Block Storage service:"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-node.xml:79(para)
+msgid "Respond to the <systemitem class=\"library\">debconf</systemitem> prompts about the <link linkend=\"debconf-dbconfig-common\">database management</link>, <link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> settings</link>, and <link linkend=\"debconf-rabbitqm\">RabbitMQ credentials</link>. Make sure to enter the same details as you did for your Block Storage service controller node."
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-node.xml:87(para)
+msgid "Another screen prompts you for the <systemitem class=\"library\">volume-group</systemitem> to use. The Debian package configuration script detects every active volume group and tries to use the first one it sees, provided that the <systemitem class=\"library\">lvm2</systemitem> package was installed before Block Storage. This should be the case if you configured the volume group first, as this guide recommends."
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-node.xml:94(para)
+msgid "If you have only one active volume group on your Block Storage service node, you do not need to manually enter its name when you install the <systemitem class=\"service\">cinder-volume</systemitem> package because it is detected automatically. If no <systemitem class=\"library\">volume-group</systemitem> is available when you install <systemitem class=\"service\">cinder-common</systemitem>, you must use <placeholder-1/> to manually configure or re-configure <systemitem class=\"service\">cinder-common</systemitem>."
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-node.xml:106(para)
+msgid "Copy the <filename>/etc/cinder/cinder.conf</filename> configuration file from the controller, or perform the following steps to set the keystone credentials:"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-node.xml:142(para)
+msgid "In the <literal>[DEFAULT]</literal> configuration section of the <filename>/etc/cinder/cinder.conf</filename> file, set these configuration keys and replace <replaceable>RABBIT_PASS</replaceable> with the password you chose for RabbitMQ:"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-node.xml:164(para)
+msgid "Configure Block Storage to use the RabbitMQ message broker. Replace <replaceable>RABBIT_PASS</replaceable> with the password you chose for RabbitMQ:"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-node.xml:177(para)
+msgid "Configure Block Storage to use your MySQL database. Edit the <filename>/etc/cinder/cinder.conf</filename> file and add the following key to the <literal>[database]</literal> section. Replace <replaceable>CINDER_DBPASS</replaceable> with the password you chose for the Block Storage database:"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-node.xml:196(para)
+msgid "Configure Block Storage to use the Image Service. Block Storage needs access to images to create bootable volumes. Edit the <filename>/etc/cinder/cinder.conf</filename> file and update the <option>glance_host</option> option in the <literal>[DEFAULT]</literal> section:"
+msgstr ""
+
+#: ./doc/install-guide/section_cinder-node.xml:214(para)
+msgid "Configure the iSCSI target service to discover Block Storage volumes. Add the following line to the beginning of the <filename>/etc/tgt/targets.conf</filename> file, if it is not already present:"
 msgstr ""
 
 #: ./doc/install-guide/section_ceilometer-verify.xml:5(title)
@@ -1151,6 +2763,329 @@ msgstr ""
 msgid "You can now get usage statistics for the various meters:"
 msgstr ""
 
+#: ./doc/install-guide/ch_ceilometer.xml:6(title)
+msgid "Add the Telemetry module"
+msgstr ""
+
+#: ./doc/install-guide/ch_ceilometer.xml:7(para)
+msgid "Telemetry provides a framework for monitoring and metering the OpenStack cloud. It is also known as the ceilometer project."
+msgstr ""
+
+#: ./doc/install-guide/ch_ceilometer.xml:19(para)
+msgid "Your OpenStack environment now includes Telemetry. You can <link linkend=\"launch-instance\">launch an instance</link> or add more services to your environment in the previous chapters."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:9(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:9(para)
+msgid "Before you configure OpenStack Networking, you must enable certain kernel networking functions."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:12(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:12(para)
+msgid "Edit <filename>/etc/sysctl.conf</filename> to contain the following:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:18(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:19(para)
+msgid "Implement the changes:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:23(title) ./doc/install-guide/section_neutron-ml2-controller-node.xml:57(title) ./doc/install-guide/section_neutron-ml2-network-node.xml:24(title)
+msgid "To install the Networking components"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:30(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:33(para)
+msgid "Ubuntu installations using Linux kernel version 3.11 or newer do not require the <emphasis>openvswitch-datapath-dkms</emphasis> package."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:35(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:64(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:38(para)
+msgid "SUSE does not use a separate ML2 plug-in package."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:40(title) ./doc/install-guide/section_neutron-ml2-network-node.xml:43(title)
+msgid "To configure the Networking common components"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:41(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:44(para)
+msgid "The Networking common component configuration includes the authentication mechanism, message broker, and plug-in."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:44(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:77(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:47(para)
+msgid "Respond to prompts for <link linkend=\"debconf-dbconfig-common\">database management</link>, <link linkend=\"debconf-keystone_authtoken\">Identity service credentials</link>, <link linkend=\"debconf-api-endpoints\">service endpoint registration</link>, and <link linkend=\"debconf-rabbitqm\">message broker credentials</link>."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:54(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:77(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:131(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:154(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:57(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:80(para)
+msgid "Configure Networking to use the Identity service for authentication:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:56(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:89(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:288(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:322(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:133(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:166(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:370(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:404(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:59(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:92(para)
+msgid "Replace <replaceable>NEUTRON_PASS</replaceable> with the password you chose for the <literal>neutron</literal> user in the Identity service."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:81(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:158(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:84(para)
+msgid "Edit the <filename>/etc/neutron/neutron.conf</filename> file and add the following key to the <literal>[DEFAULT]</literal> section:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:87(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:164(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:90(para)
+msgid "Add the following keys to the <literal>[keystone_authtoken]</literal> section:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:105(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:119(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:126(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:182(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:196(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:203(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:108(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:122(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:129(para)
+msgid "Configure Networking to use the message broker:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:129(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:162(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:206(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:248(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:296(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:132(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:165(para)
+msgid "Edit the <filename>/etc/neutron/neutron.conf</filename> file and add the following keys to the <literal>[DEFAULT]</literal> section:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:144(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:158(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:278(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:292(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:147(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:161(para)
+msgid "Configure Networking to use the Modular Layer 2 (ML2) plug-in and associated services:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:151(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:171(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:285(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:305(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:154(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:174(para)
+msgid "We recommend adding <literal>verbose = True</literal> to the <literal>[DEFAULT]</literal> section in <filename>/etc/neutron/neutron.conf</filename> to assist with troubleshooting."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:180(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:314(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:183(para)
+msgid "Comment out any lines in the <literal>[service_providers]</literal> section."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:185(title) ./doc/install-guide/section_neutron-ml2-controller-node.xml:319(title) ./doc/install-guide/section_neutron-ml2-network-node.xml:351(title)
+msgid "To configure the Modular Layer 2 (ML2) plug-in"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:186(para)
+msgid "The ML2 plug-in uses the Open vSwitch (OVS) mechanism (agent) to build the virtual networking framework for instances."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:190(para)
+msgid "Replace <replaceable>INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS</replaceable> with the IP address of the instance tunnels network interface on your compute node. This guide uses <literal>10.0.1.31</literal> for the IP address of the instance tunnels network interface on the first compute node."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:206(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:240(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:372(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:406(replaceable)
+msgid "INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:217(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:340(para)
+msgid "Edit the <filename>/etc/neutron/plugins/ml2/ml2_conf.ini</filename> file:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:220(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:343(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:386(para)
+msgid "Add the following keys to the <literal>[ml2]</literal> section:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:227(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:393(para)
+msgid "Add the following keys to the <literal>[ml2_type_gre]</literal> section:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:232(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:398(para)
+msgid "Add the <literal>[ovs]</literal> section and the following keys to it:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:234(para)
+msgid "Replace <replaceable>INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS</replaceable> with the IP address of the instance tunnels network interface on your compute node."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:243(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:355(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:409(para)
+msgid "Add the <literal>[securitygroup]</literal> section and the following keys to it:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:252(title) ./doc/install-guide/section_neutron-ml2-network-node.xml:418(title)
+msgid "To configure the Open vSwitch (OVS) service"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:253(para)
+msgid "The OVS service provides the underlying virtual networking framework for instances. The integration bridge <literal>br-int</literal> handles internal instance network traffic within OVS."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:257(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:263(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:428(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:434(para)
+msgid "Start the OVS service and configure it to start when the system boots:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:269(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:273(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:440(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:444(para)
+msgid "Restart the OVS service:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:277(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:448(para)
+msgid "Add the integration bridge:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:282(title) ./doc/install-guide/section_neutron-ml2-controller-node.xml:364(title)
+msgid "To configure Compute to use Networking"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:283(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:365(para)
+msgid "By default, most distributions configure Compute to use legacy networking. You must reconfigure Compute to manage networks through Networking."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:312(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:338(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:394(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:420(para)
+msgid "By default, Compute uses an internal firewall service. Since Networking includes a firewall service, you must disable the Compute firewall service by using the <literal>nova.virt.firewall.NoopFirewallDriver</literal> firewall driver."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:320(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:402(para)
+msgid "Edit the <filename>/etc/nova/nova.conf</filename> and add the following keys to the <literal>[DEFAULT]</literal> section:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:347(title) ./doc/install-guide/section_neutron-ml2-network-node.xml:474(title)
+msgid "To finalize the installation"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:349(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:476(para)
+msgid "The Networking service initialization scripts expect a symbolic link <filename>/etc/neutron/plugin.ini</filename> pointing to the configuration file associated with your chosen plug-in. Using the ML2 plug-in, for example, the symbolic link must point to <filename>/etc/neutron/plugins/ml2/ml2_conf.ini</filename>. If this symbolic link does not exist, create it using the following commands:"
+msgstr ""
+
+#. https://bugzilla.redhat.com/show_bug.cgi?id=1087647
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:358(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:485(para)
+msgid "Due to a packaging bug, the Open vSwitch agent initialization script explicitly looks for the Open vSwitch plug-in configuration file rather than a symbolic link <filename>/etc/neutron/plugin.ini</filename> pointing to the ML2 plug-in configuration file. Run the following commands to resolve this issue:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:368(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:495(para)
+msgid "The Networking service initialization scripts expect the variable <literal>NEUTRON_PLUGIN_CONF</literal> in the <filename>/etc/sysconfig/neutron</filename> file to reference the configuration file associated with your chosen plug-in. Using ML2, for example, edit the <filename>/etc/sysconfig/neutron</filename> file and add the following:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:383(para)
+msgid "Start the Open vSwitch (OVS) agent and configure it to start when the system boots:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:391(para)
+msgid "Restart the Open vSwitch (OVS) agent:"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_basics-networking-nova.xml:25(None) ./doc/install-guide/ch_overview.xml:147(None)
+msgid "@@image: 'figures/installguide_arch-nova.png'; md5=da24b356516c960a33ab2b4b72840774"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-nova.xml:6(title) ./doc/install-guide/ch_networking.xml:31(title)
+msgid "Legacy networking (nova-network)"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-nova.xml:7(para)
+msgid "The example architecture with legacy networking (nova-network) requires a controller node and at least one compute node. The controller node contains one network interface on the <glossterm>management network</glossterm>. The compute node contains one network interface on the management network and one on the <glossterm>external network</glossterm>."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-nova.xml:14(para)
+msgid "Network interface names vary by distribution. Traditionally, interfaces use \"eth\" followed by a sequential number. To cover all variations, this guide simply refers to the first interface as the interface with the lowest number and the second interface as the interface with the highest number."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-nova.xml:21(title) ./doc/install-guide/ch_overview.xml:143(title)
+msgid "Two-node architecture with legacy networking (nova-network)"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-nova.xml:88(para)
+msgid "The external interface uses a special configuration without an IP address assigned to it. Configure the second interface as the external interface:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-networking-nova.xml:91(para)
+msgid "Replace <replaceable>INTERFACE_NAME</replaceable> with the actual interface name. For example, <emphasis>eth1</emphasis> or <emphasis>ens224</emphasis>."
+msgstr ""
+
+#: ./doc/install-guide/section_nova-compute.xml:5(title)
+msgid "Configure a compute node"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-compute.xml:6(para)
+msgid "After you configure the Compute service on the controller node, you must configure another system as a compute node. The compute node receives requests from the controller node and hosts virtual machine instances. You can run all services on a single node, but the examples in this guide use separate systems. This makes it easy to scale horizontally by adding additional Compute nodes following the instructions in this section."
+msgstr ""
+
+#: ./doc/install-guide/section_nova-compute.xml:13(para)
+msgid "The Compute service relies on a hypervisor to run virtual machine instances. OpenStack can use various hypervisors, but this guide uses KVM."
+msgstr ""
+
+#: ./doc/install-guide/section_nova-compute.xml:18(para)
+msgid "Install the Compute packages:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-compute.xml:20(para)
+msgid "When prompted to create a <literal>supermin</literal> appliance, respond <placeholder-1/>."
+msgstr ""
+
+#: ./doc/install-guide/section_nova-compute.xml:25(para)
+msgid "To use the meta-packages and install other components on your compute node, such as OpenStack Networking and Telemetry agents, run this command:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-compute.xml:29(para)
+msgid "The controller node has the <package>openstack-proxy-node</package> and <package>openstack-toaster</package> meta-packages that install <package>openstack-proxy-node</package> and <package>openstack-toaster</package> at the same time."
+msgstr ""
+
+#: ./doc/install-guide/section_nova-compute.xml:41(para)
+msgid "Respond to the prompts for <link linkend=\"debconf-dbconfig-common\">database management</link>, <link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> settings</link>, <link linkend=\"debconf-rabbitqm\">RabbitMQ credentials</link>, and <link linkend=\"debconf-api-endpoints\">API endpoint</link> registration."
+msgstr ""
+
+#: ./doc/install-guide/section_nova-compute.xml:50(para)
+msgid "For security reasons, the Linux kernel is not readable by normal users which restricts hypervisor services such as qemu and libguestfs. For details, see <link href=\"https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725\">this bug</link>. To make the current kernel readable, run: <placeholder-1/> To also enable this override for all future kernel updates, create the file <filename>/etc/kernel/postinst.d/statoverride</filename> containing:<placeholder-2/> Remember to make the file executable: <placeholder-3/>"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-compute.xml:69(para)
+msgid "Edit the <filename>/etc/nova/nova.conf</filename> configuration file:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-compute.xml:81(para)
+msgid "Edit the <filename>/etc/nova/nova.conf</filename> configuration file and add these lines to the appropriate sections:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-compute.xml:102(para)
+msgid "Configure the Compute service to use the Qpid message broker by setting these configuration keys:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-compute.xml:116(para)
+msgid "Configure the Compute service to use the RabbitMQ message broker by setting these configuration keys:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-compute.xml:125(para)
+msgid "Configure Compute to provide remote console access to instances."
+msgstr ""
+
+#: ./doc/install-guide/section_nova-compute.xml:132(para)
+msgid "Edit <filename>/etc/nova/nova.conf</filename> and add the following keys under the <literal>[DEFAULT]</literal> section:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-compute.xml:146(para)
+msgid "Specify the host that runs the Image Service.<phrase os=\"ubuntu;debian\"> Edit <filename>/etc/nova/nova.conf</filename> file and add these lines to the <literal>[DEFAULT]</literal> section:</phrase>"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-compute.xml:157(para)
+msgid "You must determine whether your system's processor and/or hypervisor support hardware acceleration for virtual machines."
+msgstr ""
+
+#: ./doc/install-guide/section_nova-compute.xml:159(para) ./doc/install-guide/section_nova-compute.xml:178(para) ./doc/install-guide/section_basics-queue.xml:74(para)
+msgid "Run the following command:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-compute.xml:161(para)
+msgid "If this command returns a value of <emphasis>one or greater</emphasis>, your system supports hardware acceleration which typically requires no additional configuration."
+msgstr ""
+
+#: ./doc/install-guide/section_nova-compute.xml:165(para)
+msgid "If this command returns a value of <emphasis>zero</emphasis>, your system does not support hardware acceleration and you must configure <literal>libvirt</literal> to use QEMU instead of KVM."
+msgstr ""
+
+#: ./doc/install-guide/section_nova-compute.xml:170(para)
+msgid "Edit the <literal>[libvirt]</literal> section in the <filename>/etc/nova/nova-compute.conf</filename> file to modify this key:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-compute.xml:183(para)
+msgid "On Ubuntu 12.04, kernels backported from newer releases may not automatically load the KVM modules for hardware acceleration when the system boots. In this case, launching an instance will fail with the following message in the <filename>/var/log/nova/nova-compute.log</filename> file:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-compute.xml:189(para)
+msgid "As a workaround for this issue, you must add the appropriate module for your system to the <filename>/etc/modules</filename> file."
+msgstr ""
+
+#: ./doc/install-guide/section_nova-compute.xml:192(para)
+msgid "For systems with Intel processors, run the following command:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-compute.xml:195(para)
+msgid "For systems with AMD processors, run the following command:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-compute.xml:201(para)
+msgid "Remove the SQLite database created by the packages:"
+msgstr ""
+
+#: ./doc/install-guide/section_nova-compute.xml:205(para)
+msgid "Start the Compute service and configure it to start when the system boots:"
+msgstr ""
+
 #: ./doc/install-guide/section_trove-install.xml:3(title)
 msgid "Install the Database service"
 msgstr ""
@@ -1159,10 +3094,6 @@ msgstr ""
 msgid "This procedure installs the Database module on the controller node."
 msgstr ""
 
-#: ./doc/install-guide/section_trove-install.xml:7(title) ./doc/install-guide/section_neutron-ovs-compute-node.xml:28(title) ./doc/install-guide/section_neutron-ml2-controller-node.xml:8(title) ./doc/install-guide/section_neutron-ovs-controller-node.xml:24(title) ./doc/install-guide/section_neutron-ml2-network-node.xml:8(title) ./doc/install-guide/section_neutron-ml2-compute-node.xml:8(title)
-msgid "Prerequisites"
-msgstr ""
-
 #: ./doc/install-guide/section_trove-install.xml:8(para)
 msgid "This chapter assumes that you already have a working OpenStack environment with at least the following components installed: Compute, Image Service, Identity."
 msgstr ""
@@ -1311,444 +3242,104 @@ msgstr ""
 msgid "Restart Database services:"
 msgstr ""
 
-#: ./doc/install-guide/section_nova-networking-compute-node.xml:5(title) ./doc/install-guide/section_neutron-ovs-compute-node.xml:6(title) ./doc/install-guide/section_neutron-ml2-compute-node.xml:6(title)
-msgid "Configure compute node"
+#: ./doc/install-guide/ch_cinder.xml:6(title)
+msgid "Add the Block Storage service"
 msgstr ""
 
-#: ./doc/install-guide/section_nova-networking-compute-node.xml:6(para)
-msgid "This section covers deployment of a simple <glossterm>flat network</glossterm> that provides IP addresses to your instances via <glossterm>DHCP</glossterm>. If your environment includes multiple compute nodes, the <glossterm>multi-host</glossterm> feature provides redundancy by spreading network functions across compute nodes."
+#: ./doc/install-guide/ch_cinder.xml:7(para)
+msgid "The OpenStack Block Storage service works through the interaction of a series of daemon processes named <systemitem role=\"process\">cinder-*</systemitem> that reside persistently on the host machine or machines. You can run the binaries from a single node or across multiple nodes. You can also run them on the same node as other OpenStack services. The following sections introduce Block Storage service components and concepts and show you how to configure and install the Block Storage service."
 msgstr ""
 
-#: ./doc/install-guide/section_nova-networking-compute-node.xml:13(title)
-msgid "To install legacy networking components"
+#: ./doc/install-guide/ch_cinder.xml:21(para)
+msgid "Your OpenStack environment now includes Block Storage. You can <link linkend=\"launch-instance\">launch an instance</link> or add more services to your environment in the following chapters."
 msgstr ""
 
-#: ./doc/install-guide/section_nova-networking-compute-node.xml:21(title) ./doc/install-guide/section_nova-networking-controller-node.xml:9(title)
-msgid "To configure legacy networking"
+#: ./doc/install-guide/section_debconf-concepts.xml:7(title)
+msgid "debconf concepts"
 msgstr ""
 
-#: ./doc/install-guide/section_nova-networking-compute-node.xml:23(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:325(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:369(para) ./doc/install-guide/section_ceilometer-glance.xml:20(para) ./doc/install-guide/section_nova-networking-controller-node.xml:11(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:192(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:226(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:262(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:355(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:189(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:287(para) ./doc/install-guide/section_heat-install.xml:94(para)
-msgid "Run the following commands:"
+#: ./doc/install-guide/section_debconf-concepts.xml:8(para)
+msgid "This chapter explains how to use the Debian <systemitem class=\"library\">debconf</systemitem> and <systemitem class=\"library\">dbconfig-common</systemitem> packages to configure OpenStack services. These packages enable users to perform configuration tasks. When users install OpenStack packages, <package>debconf</package> prompts the user for responses, which seed the contents of configuration files associated with that package. After package installation, users can update the configuration of a package by using the <placeholder-1/> program."
 msgstr ""
 
-#: ./doc/install-guide/section_nova-networking-compute-node.xml:24(para) ./doc/install-guide/section_nova-networking-compute-node.xml:57(para)
-msgid "Replace <replaceable>INTERFACE_NAME</replaceable> with the actual interface name for the external network. For example, <emphasis>eth1</emphasis> or <emphasis>ens224</emphasis>."
+#: ./doc/install-guide/section_debconf-concepts.xml:18(para)
+msgid "If you are familiar with these packages and pre-seeding, you can proceed to <xref linkend=\"ch_keystone\"/>."
 msgstr ""
 
-#: ./doc/install-guide/section_nova-networking-compute-node.xml:50(replaceable) ./doc/install-guide/section_nova-networking-compute-node.xml:52(replaceable) ./doc/install-guide/section_nova-networking-compute-node.xml:73(replaceable) ./doc/install-guide/section_nova-networking-compute-node.xml:74(replaceable) ./doc/install-guide/section_basics-networking-nova.xml:99(replaceable) ./doc/install-guide/section_basics-networking-nova.xml:100(replaceable) ./doc/install-guide/section_basics-networking-nova.xml:110(replaceable) ./doc/install-guide/section_basics-networking-neutron.xml:108(replaceable) ./doc/install-guide/section_basics-networking-neutron.xml:109(replaceable) ./doc/install-guide/section_basics-networking-neutron.xml:119(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:461(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:469(replaceable)
-msgid "INTERFACE_NAME"
+#: ./doc/install-guide/section_debconf-concepts.xml:21(title)
+msgid "The Debian packages"
 msgstr ""
 
-#: ./doc/install-guide/section_nova-networking-compute-node.xml:55(para) ./doc/install-guide/section_nova-networking-controller-node.xml:18(para)
-msgid "Edit the <filename>/etc/nova/nova.conf</filename> file and add the following keys to the <literal>[DEFAULT]</literal> section:"
+#: ./doc/install-guide/section_debconf-concepts.xml:22(para)
+msgid "The rules described here are from the <link href=\"http://www.debian.org/doc/debian-policy/\"><citetitle>Debian Policy Manual</citetitle></link>. If any rule described in this chapter is not respected, you have found a serious bug that must be fixed."
 msgstr ""
 
-#: ./doc/install-guide/section_nova-networking-compute-node.xml:77(para)
-msgid "Restart the services:"
+#: ./doc/install-guide/section_debconf-concepts.xml:27(para)
+msgid "When you install or upgrade a Debian package, all configuration file values are preserved. Using the <systemitem class=\"library\">debconf</systemitem> database as a registry is considered a bug in Debian. If you edit something in any OpenStack configuration file, the <systemitem class=\"library\">debconf</systemitem> package reads that value when it prepares to prompt the user. For example, to change the log in name for the RabbitMQ messaging queue for a service, you can edit its value in the corresponding configuration file."
 msgstr ""
 
-#: ./doc/install-guide/section_nova-networking-compute-node.xml:80(para)
-msgid "Start the services and configure them to start when the system boots:"
+#: ./doc/install-guide/section_debconf-concepts.xml:36(para)
+msgid "To opt out of using the <systemitem class=\"library\">debconf</systemitem> package, run the <placeholder-1/> command and select non-interactive mode:"
 msgstr ""
 
-#: ./doc/install-guide/section_trove-verify.xml:5(title)
-msgid "Verify the Database service installation"
+#: ./doc/install-guide/section_debconf-concepts.xml:41(para)
+msgid "Then, <systemitem class=\"library\">debconf</systemitem> does not prompt you."
 msgstr ""
 
-#: ./doc/install-guide/section_trove-verify.xml:6(para)
-msgid "To verify that the Database service is installed and configured correctly, try executing a Trove command:"
+#: ./doc/install-guide/section_debconf-concepts.xml:43(para)
+msgid "Another way to disable the <systemitem class=\"library\">debconf</systemitem> package is to prefix the <placeholder-1/> command with <literal>DEBIAN_FRONTEND=noninteractive</literal>, as follows:"
 msgstr ""
 
-#: ./doc/install-guide/section_trove-verify.xml:10(para)
-msgid "Source the <filename>demo-openrc.sh</filename> file."
+#: ./doc/install-guide/section_debconf-concepts.xml:49(para)
+msgid "If you configure a package with <systemitem class=\"library\">debconf</systemitem> incorrectly, you can re-configure it, as follows:"
 msgstr ""
 
-#: ./doc/install-guide/section_trove-verify.xml:14(para)
-msgid "Retrieve the Trove instances list:"
+#: ./doc/install-guide/section_debconf-concepts.xml:52(replaceable)
+msgid "PACKAGE-NAME"
 msgstr ""
 
-#: ./doc/install-guide/section_trove-verify.xml:16(para)
-msgid "You should see output similar to this:"
+#: ./doc/install-guide/section_debconf-concepts.xml:53(para)
+msgid "This calls the post-installation script for the <replaceable>PACKAGE-NAME</replaceable> package after the user responds to all prompts. If you cannot install a Debian package in a non-interactive way, you have found a release-critical bug in Debian. Report it to the Debian bug tracking system."
 msgstr ""
 
-#: ./doc/install-guide/section_trove-verify.xml:23(para)
-msgid "Assuming you have created an image for the type of database you want, and have updated the datastore to use that image, you can now create a Trove instance (database). To do this, use the trove <placeholder-1/> command."
+#: ./doc/install-guide/section_debconf-concepts.xml:58(para)
+msgid "Generally, the <systemitem class=\"library\">-common</systemitem> packages install the configuration files. For example, the <literal>glance-common</literal> package installs the <filename>glance-api.conf</filename> and <filename>glance-registry.conf</filename> files. So, for the Image Service, you must re-configure the <literal>glance-common</literal> package. The same applies for <literal>cinder-common</literal>, <literal>nova-common</literal>, and <literal>heat-common</literal> packages."
 msgstr ""
 
-#: ./doc/install-guide/section_trove-verify.xml:30(para)
-msgid "This example shows you how to create a MySQL 5.5 database:"
+#: ./doc/install-guide/section_debconf-concepts.xml:68(para)
+msgid "In <systemitem class=\"library\">debconf</systemitem>, the higher the priority for a screen, the greater the chance that the user sees that screen. If a <systemitem class=\"library\">debconf</systemitem> screen has <literal>medium</literal> priority and you configure the Debian system to show only <literal>critical</literal> prompts, which is the default in Debian, the user does not see that <systemitem class=\"library\">debconf</systemitem> screen. Instead, the default for the related package is used. In the Debian OpenStack packages, a number of <systemitem class=\"library\">debconf</systemitem> screens are set with <literal>medium</literal> priority. Consequently, if you want to respond to all <systemitem class=\"library\">debconf</systemitem> screens from the Debian OpenStack packages, you must run the following command and select the <literal>medium</literal> priority before you install any packages:"
 msgstr ""
 
-#: ./doc/install-guide/section_trove-verify.xml:32(replaceable)
-msgid "name"
+#: ./doc/install-guide/section_debconf-concepts.xml:87(para)
+msgid "The packages do not require pre-depends. If <systemitem class=\"library\">dbconfig-common</systemitem> is already installed on the system, the user sees all prompts. However, you cannot define the order in which the <systemitem class=\"library\">debconf</systemitem> screens appear. The user must make sense of it even if the prompts appear in an illogical order."
 msgstr ""
 
-#: ./doc/install-guide/section_trove-verify.xml:32(replaceable)
-msgid "DBNAME"
+#: ./doc/install-guide/section_nova-networking-controller-node.xml:6(para)
+msgid "Legacy networking primarily involves compute nodes. However, you must configure the controller node to use it."
 msgstr ""
 
-#: ./doc/install-guide/section_trove-verify.xml:33(replaceable)
-msgid "USER"
+#: ./doc/install-guide/section_nova-networking-controller-node.xml:26(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:451(para) ./doc/install-guide/section_neutron-ovs-controller-node.xml:331(para)
+msgid "Restart the Compute services:"
 msgstr ""
 
-#: ./doc/install-guide/section_trove-verify.xml:33(replaceable)
-msgid "PASSWORD"
+#: ./doc/install-guide/ch_nova.xml:7(title)
+msgid "Configure Compute services"
 msgstr ""
 
-#: ./doc/install-guide/section_nova-controller.xml:5(title)
-msgid "Install Compute controller services"
+#: ./doc/install-guide/ch_networking.xml:6(title)
+msgid "Add a networking service"
 msgstr ""
 
-#: ./doc/install-guide/section_nova-controller.xml:6(para)
-msgid "Compute is a collection of services that enable you to launch virtual machine instances. You can configure these services to run on separate nodes or the same node. In this guide, most services run on the controller node and the service that launches virtual machines runs on a dedicated compute node. This section shows you how to install and configure these services on the controller node."
+#: ./doc/install-guide/ch_networking.xml:7(para)
+msgid "Configuring networking in OpenStack can be a bewildering experience. This guide provides step-by-step instructions for both OpenStack Networking (neutron) and the legacy networking (nova-network) service. If you are unsure which to use, we recommend trying OpenStack Networking because it offers a considerable number of features and flexibility including <glossterm baseform=\"plug-in\">plug-ins</glossterm> for a variety of emerging products supporting <glossterm>virtual networking</glossterm>. See the <link href=\"http://docs.openstack.org/admin-guide-cloud/content/ch_networking.html\">Networking</link> chapter of the <citetitle>OpenStack Cloud Administrator Guide</citetitle> for more information."
 msgstr ""
 
-#: ./doc/install-guide/section_nova-controller.xml:15(para)
-msgid "Install the Compute packages necessary for the controller node."
+#: ./doc/install-guide/ch_networking.xml:23(title)
+msgid "Modular Layer 2 (ML2) plug-in"
 msgstr ""
 
-#: ./doc/install-guide/section_nova-controller.xml:27(para)
-msgid "Respond to the prompts for <link linkend=\"debconf-dbconfig-common\">database management</link>, <link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> settings</link>, <link linkend=\"debconf-rabbitqm\">RabbitMQ credentials</link>, and <link linkend=\"debconf-api-endpoints\">API endpoint</link> registration. The <placeholder-1/> command runs automatically."
-msgstr ""
-
-#: ./doc/install-guide/section_nova-controller.xml:38(para)
-msgid "Compute stores information in a database. In this guide, we use a MySQL database on the controller node. Configure Compute with the database location and credentials. Replace <replaceable>NOVA_DBPASS</replaceable> with the password for the database that you will create in a later step."
-msgstr ""
-
-#: ./doc/install-guide/section_nova-controller.xml:44(replaceable) ./doc/install-guide/section_nova-controller.xml:51(replaceable) ./doc/install-guide/section_nova-controller.xml:119(replaceable) ./doc/install-guide/section_nova-controller.xml:121(replaceable) ./doc/install-guide/section_nova-compute.xml:72(replaceable)
-msgid "NOVA_DBPASS"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-controller.xml:45(para)
-msgid "Edit the <literal>[database]</literal> section in the <filename>/etc/nova/nova.conf</filename> file, adding it if necessary, to modify this key:"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-controller.xml:55(para)
-msgid "Set these configuration keys to configure Compute to use the Qpid message broker:"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-controller.xml:62(para) ./doc/install-guide/section_nova-compute.xml:107(para)
-msgid "Configure the Compute service to use the RabbitMQ message broker by setting these configuration keys in the <literal>[DEFAULT]</literal> configuration group of the <filename>/etc/nova/nova.conf</filename> file:"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-controller.xml:73(para)
-msgid "Set these configuration keys to configure Compute to use the RabbitMQ message broker:"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-controller.xml:81(para)
-msgid "Set the <option>my_ip</option>, <option>vncserver_listen</option>, and <option>vncserver_proxyclient_address</option> configuration options to the management interface IP address of the controller node:"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-controller.xml:89(para)
-msgid "Edit the <filename>/etc/nova/nova.conf</filename> file and add these lines to the <literal>[DEFAULT]</literal> section:"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-controller.xml:92(para)
-msgid "In Debian, the <package>debconf</package> package automatically sets up <literal>my_ip</literal> parameter but you must edit the <filename>/etc/nova/nova.conf</filename> file to configure the <option>vncserver_listen</option> and <option>vncserver_proxyclient_address</option> options, which appear at the end of the file:"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-controller.xml:107(para)
-msgid "By default, the Ubuntu packages create an SQLite database. Delete the <filename>nova.sqlite</filename> file created in the <filename>/var/lib/nova/</filename> directory so that it does not get used by mistake:"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-controller.xml:114(para)
-msgid "Use the password you created previously to log in as root. Create a <literal>nova</literal> database user:"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-controller.xml:124(para)
-msgid "Create the Compute service tables:"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-controller.xml:128(para)
-msgid "Create a <literal>nova</literal> user that Compute uses to authenticate with the Identity Service. Use the <literal>service</literal> tenant and give the user the <literal>admin</literal> role:"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-controller.xml:132(replaceable) ./doc/install-guide/section_nova-controller.xml:146(replaceable) ./doc/install-guide/section_nova-controller.xml:166(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:234(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:258(replaceable) ./doc/install-guide/section_nova-compute.xml:80(replaceable) ./doc/install-guide/section_nova-compute.xml:99(replaceable)
-msgid "NOVA_PASS"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-controller.xml:132(replaceable)
-msgid "nova@example.com"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-controller.xml:136(para)
-msgid "Configure Compute to use these credentials with the Identity Service running on the controller. Replace <replaceable>NOVA_PASS</replaceable> with your Compute password."
-msgstr ""
-
-#: ./doc/install-guide/section_nova-controller.xml:147(para)
-msgid "Edit the <literal>[DEFAULT]</literal> section in the <filename>/etc/nova/nova.conf</filename> file to add this key:"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-controller.xml:155(para)
-msgid "Add these keys to the <literal>[keystone_authtoken]</literal> section:"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-controller.xml:169(para)
-msgid "You must register Compute with the Identity Service so that other OpenStack services can locate it. Register the service and specify the endpoint:"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-controller.xml:182(para)
-msgid "Start Compute services and configure them to start when the system boots:"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-controller.xml:185(para)
-msgid "Restart Compute services:"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-controller.xml:206(para)
-msgid "To verify your configuration, list available images:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:8(para)
-msgid "This section details set up for any node that runs the <literal>nova-compute</literal> component but does not run the full network stack."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:13(para)
-msgid "By default, the <literal>system-config-firewall</literal> automated firewall configuration tool is in place on RHEL. This graphical interface (and a curses-style interface with <literal>-tui</literal> on the end of the name) enables you to configure IP tables as a basic firewall. You should disable it when you work with OpenStack Networking unless you are familiar with the underlying network technologies, as, by default, it blocks various types of network traffic that are important to neutron services. To disable it, launch the program and clear the <guilabel>Enabled</guilabel> check box."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:22(para)
-msgid "After you successfully set up OpenStack Networking with Neutron, you can re-enable and configure the tool. However, during OpenStack Networking setup, disable the tool to make it easier to debug network issues."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:30(para)
-msgid "Disable packet destination filtering (route verification) to let the networking services route traffic to the VMs. Edit the <filename>/etc/sysctl.conf</filename> file and run the following command to activate changes:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:41(title)
-msgid "Install Open vSwitch plug-in"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:42(para) ./doc/install-guide/section_neutron-ovs-controller-node.xml:185(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:176(para)
-msgid "OpenStack Networking supports a variety of plug-ins. For simplicity, we chose to cover the most common plug-in, Open vSwitch, and configure it to use basic GRE tunnels for tenant network traffic."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:47(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:181(para)
-msgid "Install the Open vSwitch plug-in and its dependencies:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:54(para)
-msgid "Restart Open vSwitch:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:58(para)
-msgid "Start Open vSwitch and configure it to start when the system boots:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:66(para)
-msgid "You must set some common configuration options no matter which networking technology you choose to use with Open vSwitch. You must add the <literal>br-int</literal> integration bridge, which connects to the VMs."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:74(para)
-msgid "You must set some common configuration options. You must configure Networking core to use <acronym>OVS</acronym>. Edit the <filename>/etc/neutron/neutron.conf</filename> file:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:83(para)
-msgid "You must configure a firewall as well. You should use the same firewall plug-in that you chose to use when you set up the network node. To do this, edit <filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename> file and set the <literal>firewall_driver</literal> value under the <literal>securitygroup</literal> to the same value used on the network node. For instance, if you chose to use the Hybrid OVS-IPTables plug-in, your configuration looks like this:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:96(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:313(para)
-msgid "You must use at least the No-Op firewall. Otherwise, Horizon and other OpenStack services cannot get and set required VM boot options."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:102(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:319(para)
-msgid "Configure the <acronym>OVS</acronym> plug-in to start on boot."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:108(para)
-msgid "Tell the <acronym>OVS</acronym> plug-in to use GRE tunneling with a <literal>br-int</literal> integration bridge, a <literal>br-tun</literal> tunneling bridge, and a local IP for the tunnel of <replaceable>DATA_INTERFACE</replaceable>'s IP Edit the <filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename> file:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:123(replaceable)
-msgid "DATA_INTERFACE_IP"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:127(title)
-msgid "Configure common components"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:129(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:82(para)
-msgid "Configure Networking to use <systemitem class=\"service\">keystone</systemitem> for authentication:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:132(para) ./doc/install-guide/section_neutron-ovs-compute-node.xml:166(para)
-msgid "Set the <literal>auth_strategy</literal> configuration key to <literal>keystone</literal> in the <literal>[DEFAULT]</literal> section of the file:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:138(para) ./doc/install-guide/section_neutron-ovs-controller-node.xml:95(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:91(para)
-msgid "Set the <systemitem class=\"service\">neutron</systemitem> configuration for <systemitem class=\"service\">keystone</systemitem> authentication:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:155(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:185(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:240(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:257(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:33(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:151(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:177(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:384(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:414(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:46(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:110(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:139(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:237(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:254(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:109(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:136(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:393(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:407(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:77(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:103(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:277(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:304(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:74(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:100(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:302(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:332(replaceable)
-msgid "NEUTRON_PASS"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:160(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:113(para)
-msgid "To configure <systemitem class=\"service\">neutron</systemitem> to use <systemitem class=\"service\">keystone</systemitem> for authentication, edit the <filename>/etc/neutron/neutron.conf</filename> file."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:174(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:125(para)
-msgid "Add these lines to the <literal>[keystone_authtoken]</literal> section of the file:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:190(para) ./doc/install-guide/section_neutron-ovs-controller-node.xml:144(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:141(para)
-msgid "Configure access to the <application>RabbitMQ</application> service:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:201(para)
-msgid "Configure the <application>RabbitMQ</application> access. Edit the <filename>/etc/neutron/neutron.conf</filename> file to modify the following parameters in the <literal>[DEFAULT]</literal> section."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:210(para) ./doc/install-guide/section_neutron-ovs-controller-node.xml:156(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:161(para)
-msgid "Configure access to the <application>Qpid</application> message queue:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:218(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:220(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:165(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:167(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:169(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:171(replaceable)
-msgid "guest"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:224(title) ./doc/install-guide/section_neutron-ovs-controller-node.xml:220(title)
-msgid "Configure Compute services for Networking"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:226(para)
-msgid "Configure OpenStack Compute to use OpenStack Networking services. Configure the <filename>/etc/nova/nova.conf</filename> file as per instructions below:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:249(para)
-msgid "Configure OpenStack Compute to use OpenStack Networking services. Edit the <filename>/etc/nova/nova.conf</filename> file:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:265(para)
-msgid "No matter which firewall driver you chose when you configured the network and compute nodes, you must edit the <filename>/etc/nova/nova.conf</filename> file to set the firewall driver to <literal>nova.virt.firewall.NoopFirewallDriver</literal>. Because OpenStack Networking handles the firewall, this statement instructs Compute to not use a firewall."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:275(para)
-msgid "If you want Networking to handle the firewall, edit the <filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename> file to set the <code>firewall_driver</code> option to the firewall for the plug-in. For example, with <acronym>OVS</acronym>, edit the file as follows:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:290(para)
-msgid "If you do not want to use a firewall in Compute or Networking, edit both configuration files and set <code>firewall_driver=nova.virt.firewall.NoopFirewallDriver</code>. Also, edit the <filename>/etc/nova/nova.conf</filename> file and comment out or remove the <code>security_group_api=neutron</code> statement."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:298(para)
-msgid "Otherwise, when you issue <placeholder-1/> commands, the <errortext>ERROR: The server has either erred or is incapable of performing the requested operation. (HTTP 500)</errortext> error might be returned."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:309(title) ./doc/install-guide/section_neutron-ovs-controller-node.xml:322(title) ./doc/install-guide/section_neutron-ovs-network-node.xml:432(title)
-msgid "Finalize installation"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:311(para) ./doc/install-guide/section_neutron-ovs-controller-node.xml:298(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:434(para)
-msgid "The <systemitem class=\"service\">neutron-server</systemitem> initialization script expects a symbolic link <filename>/etc/neutron/plugin.ini</filename> pointing to the configuration file associated with your chosen plug-in. Using Open vSwitch, for example, the symbolic link must point to <filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename>. If this symbolic link does not exist, create it using the following commands:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:323(para) ./doc/install-guide/section_neutron-ovs-controller-node.xml:310(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:446(para)
-msgid "The <systemitem class=\"service\">openstack-neutron</systemitem> initialization script expects the variable <literal>NEUTRON_PLUGIN_CONF</literal> in file <filename>/etc/sysconfig/neutron</filename> to reference the configuration file associated with your chosen plug-in. Using Open vSwitch, for example, edit the <filename>/etc/sysconfig/neutron</filename> file and add the following:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:334(para) ./doc/install-guide/section_neutron-ovs-network-node.xml:457(para)
-msgid "Restart Networking services."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:340(para)
-msgid "Restart the Compute service."
-msgstr ""
-
-#: ./doc/install-guide/section_dashboard-system-reqs.xml:6(title)
-msgid "System requirements"
-msgstr ""
-
-#: ./doc/install-guide/section_dashboard-system-reqs.xml:7(para)
-msgid "Before you install the OpenStack dashboard, you must meet the following system requirements:"
-msgstr ""
-
-#: ./doc/install-guide/section_dashboard-system-reqs.xml:11(para)
-msgid "OpenStack Compute installation. Enable the Identity Service for user and project management."
-msgstr ""
-
-#: ./doc/install-guide/section_dashboard-system-reqs.xml:13(para)
-msgid "Note the URLs of the Identity Service and Compute endpoints."
-msgstr ""
-
-#: ./doc/install-guide/section_dashboard-system-reqs.xml:17(para)
-msgid "Identity Service user with sudo privileges. Because Apache does not serve content from a root user, users must run the dashboard as an Identity Service user with sudo privileges."
-msgstr ""
-
-#: ./doc/install-guide/section_dashboard-system-reqs.xml:23(para)
-msgid "Python 2.6 or 2.7. The Python version must support Django. The Python version should run on any system, including Mac OS X. Installation prerequisites might differ by platform."
-msgstr ""
-
-#: ./doc/install-guide/section_dashboard-system-reqs.xml:29(para)
-msgid "Then, install and configure the dashboard on a node that can contact the Identity Service."
-msgstr ""
-
-#: ./doc/install-guide/section_dashboard-system-reqs.xml:31(para)
-msgid "Provide users with the following information so that they can access the dashboard through a web browser on their local machine:"
-msgstr ""
-
-#: ./doc/install-guide/section_dashboard-system-reqs.xml:36(para)
-msgid "The public IP address from which they can access the dashboard"
-msgstr ""
-
-#: ./doc/install-guide/section_dashboard-system-reqs.xml:40(para)
-msgid "The user name and password with which they can access the dashboard"
-msgstr ""
-
-#: ./doc/install-guide/section_dashboard-system-reqs.xml:44(para)
-msgid "Your web browser, and that of your users, must support HTML5 and have cookies and JavaScript enabled."
-msgstr ""
-
-#: ./doc/install-guide/section_dashboard-system-reqs.xml:48(para)
-msgid "To use the VNC client with the dashboard, the browser must support HTML5 Canvas and HTML5 WebSockets."
-msgstr ""
-
-#: ./doc/install-guide/section_dashboard-system-reqs.xml:50(para)
-msgid "For details about browsers that support noVNC, see <link href=\"https://github.com/kanaka/noVNC/blob/master/README.md\">https://github.com/kanaka/noVNC/blob/master/README.md</link>, and <link href=\"https://github.com/kanaka/noVNC/wiki/Browser-support\">https://github.com/kanaka/noVNC/wiki/Browser-support</link>, respectively."
-msgstr ""
-
-#: ./doc/install-guide/section_launch-instance-neutron.xml:6(title)
-msgid "Launch an instance with OpenStack Networking (neutron)"
-msgstr ""
-
-#: ./doc/install-guide/section_launch-instance-neutron.xml:95(para)
-msgid "Your first instance uses the <literal>default</literal> security group. By default, this security group implements a firewall that blocks remote access to instances. If you would like to permit remote access to your instance, launch it and then <link linkend=\"launch-instance-neutron-remoteaccess\"> configure remote access</link>."
-msgstr ""
-
-#: ./doc/install-guide/section_launch-instance-neutron.xml:173(para)
-msgid "Verify the <literal>demo-net</literal> tenant network gateway:"
-msgstr ""
-
-#: ./doc/install-guide/section_launch-instance-neutron.xml:185(para)
-msgid "Verify the <literal>ext-net</literal> external network:"
-msgstr ""
-
-#: ./doc/install-guide/section_launch-instance-neutron.xml:224(para)
-msgid "Create a <glossterm>floating IP address</glossterm> on the <literal>ext-net</literal> external network:"
-msgstr ""
-
-#: ./doc/install-guide/section_launch-instance-neutron.xml:242(para)
-msgid "Associate the floating IP address with your instance:"
-msgstr ""
-
-#: ./doc/install-guide/section_launch-instance-neutron.xml:249(para)
-msgid "Check the status of your floating IP address:"
-msgstr ""
-
-#: ./doc/install-guide/ch_launch-instance.xml:5(title)
-msgid "Launch an instance"
-msgstr ""
-
-#: ./doc/install-guide/ch_launch-instance.xml:6(para)
-msgid "An instance is a VM that OpenStack provisions on a compute node. This guide shows you how to launch a minimal instance using the <glossterm>CirrOS</glossterm> image that you added to your environment in the <xref linkend=\"ch_glance\"/> chapter. In these steps, you use the command-line interface (CLI) on your controller node or any system with the appropriate OpenStack client libraries. To use the dashboard, see the <link href=\"http://docs.openstack.org/user-guide/content/ch_dashboard.html\"><citetitle>OpenStack User Guide</citetitle></link>."
-msgstr ""
-
-#: ./doc/install-guide/ch_launch-instance.xml:15(para)
-msgid "Launch an instance using <link linkend=\"launch-instance-neutron\">OpenStack Networking (neutron) </link> or <link linkend=\"launch-instance-nova\">legacy networking (nova-network) </link>. For more information, see the <link href=\"http://docs.openstack.org/user-guide/content/cli_launch_instances.html\"><citetitle>OpenStack User Guide</citetitle></link>."
-msgstr ""
-
-#: ./doc/install-guide/ch_launch-instance.xml:25(para)
-msgid "These steps reference example components created in previous chapters. You must adjust certain values such as IP addresses to match your environment."
+#: ./doc/install-guide/ch_networking.xml:38(para)
+msgid "Your OpenStack environment now includes the core components necessary to launch a basic instance. You can <link linkend=\"launch-instance\">launch an instance</link> or add more services to your environment in the following chapters."
 msgstr ""
 
 #. When image changes, this message will be marked fuzzy or untranslated for you.
@@ -1757,10 +3348,6 @@ msgstr ""
 msgid "@@image: 'figures/debconf-screenshots/neutron_1_plugin_selection.png'; md5=adf41c33778a691a560b7098908792db"
 msgstr ""
 
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:6(title) ./doc/install-guide/section_neutron-ovs-controller-node.xml:6(title) ./doc/install-guide/section_basics-ntp.xml:13(title) ./doc/install-guide/section_nova-networking-controller-node.xml:5(title)
-msgid "Configure controller node"
-msgstr ""
-
 #: ./doc/install-guide/section_neutron-ml2-controller-node.xml:9(para)
 msgid "Before you configure OpenStack Networking (neutron), you must create a database and Identity service credentials including a user and service."
 msgstr ""
@@ -1805,14 +3392,6 @@ msgstr ""
 msgid "Create the service endpoint:"
 msgstr ""
 
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:57(title) ./doc/install-guide/section_neutron-ml2-network-node.xml:24(title) ./doc/install-guide/section_neutron-ml2-compute-node.xml:23(title)
-msgid "To install the Networking components"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:64(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:38(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:35(para)
-msgid "SUSE does not use a separate ML2 plug-in package."
-msgstr ""
-
 #: ./doc/install-guide/section_neutron-ml2-controller-node.xml:67(para)
 msgid "Debian does not use a separate ML2 plug-in package."
 msgstr ""
@@ -1825,10 +3404,6 @@ msgstr ""
 msgid "The Networking server component configuration includes the database, authentication mechanism, message broker, topology change notifier, and plug-in."
 msgstr ""
 
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:77(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:47(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:44(para)
-msgid "Respond to prompts for <link linkend=\"debconf-dbconfig-common\">database management</link>, <link linkend=\"debconf-keystone_authtoken\">Identity service credentials</link>, <link linkend=\"debconf-api-endpoints\">service endpoint registration</link>, and <link linkend=\"debconf-rabbitqm\">message broker credentials</link>."
-msgstr ""
-
 #: ./doc/install-guide/section_neutron-ml2-controller-node.xml:87(para)
 msgid "During the installation, you will also be prompted for which Networking plug-in to use. This will automatically fill the <option>core_plugin</option> directive in the <filename>/etc/neutron/neutron.conf</filename> file."
 msgstr ""
@@ -1849,34 +3424,6 @@ msgstr ""
 msgid "Replace <replaceable>NEUTRON_DBPASS</replaceable> with the password you chose for the database."
 msgstr ""
 
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:131(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:154(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:57(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:80(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:54(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:77(para)
-msgid "Configure Networking to use the Identity service for authentication:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:133(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:166(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:370(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:404(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:59(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:92(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:56(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:89(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:288(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:322(para)
-msgid "Replace <replaceable>NEUTRON_PASS</replaceable> with the password you chose for the <literal>neutron</literal> user in the Identity service."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:158(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:84(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:81(para)
-msgid "Edit the <filename>/etc/neutron/neutron.conf</filename> file and add the following key to the <literal>[DEFAULT]</literal> section:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:164(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:90(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:87(para)
-msgid "Add the following keys to the <literal>[keystone_authtoken]</literal> section:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:182(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:196(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:203(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:108(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:122(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:129(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:105(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:119(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:126(para)
-msgid "Configure Networking to use the message broker:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:183(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:209(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:109(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:135(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:106(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:132(para) ./doc/install-guide/section_glance-install.xml:83(para) ./doc/install-guide/section_glance-install.xml:96(para)
-msgid "Replace <replaceable>RABBIT_PASS</replaceable> with the password you chose for the <literal>guest</literal> account in <application>RabbitMQ</application>."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:206(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:248(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:296(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:132(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:165(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:129(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:162(para)
-msgid "Edit the <filename>/etc/neutron/neutron.conf</filename> file and add the following keys to the <literal>[DEFAULT]</literal> section:"
-msgstr ""
-
 #: ./doc/install-guide/section_neutron-ml2-controller-node.xml:221(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:239(para)
 msgid "Configure Networking to notify Compute about network topology changes:"
 msgstr ""
@@ -1893,58 +3440,14 @@ msgstr ""
 msgid "To obtain the <literal>service</literal> tenant identifier (id):"
 msgstr ""
 
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:278(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:292(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:147(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:161(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:144(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:158(para)
-msgid "Configure Networking to use the Modular Layer 2 (ML2) plug-in and associated services:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:285(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:305(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:154(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:174(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:151(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:171(para)
-msgid "We recommend adding <literal>verbose = True</literal> to the <literal>[DEFAULT]</literal> section in <filename>/etc/neutron/neutron.conf</filename> to assist with troubleshooting."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:314(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:183(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:180(para)
-msgid "Comment out any lines in the <literal>[service_providers]</literal> section."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:319(title) ./doc/install-guide/section_neutron-ml2-network-node.xml:351(title) ./doc/install-guide/section_neutron-ml2-compute-node.xml:185(title)
-msgid "To configure the Modular Layer 2 (ML2) plug-in"
-msgstr ""
-
 #: ./doc/install-guide/section_neutron-ml2-controller-node.xml:320(para)
 msgid "The ML2 plug-in uses the Open vSwitch (OVS) mechanism (agent) to build the virtual networking framework for instances. However, the controller node does not need the OVS agent or service because it does not handle instance network traffic."
 msgstr ""
 
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:340(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:217(para)
-msgid "Edit the <filename>/etc/neutron/plugins/ml2/ml2_conf.ini</filename> file:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:343(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:386(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:220(para)
-msgid "Add the following keys to the <literal>[ml2]</literal> section:"
-msgstr ""
-
 #: ./doc/install-guide/section_neutron-ml2-controller-node.xml:350(para)
 msgid "Add the following key to the <literal>[ml2_type_gre]</literal> section:"
 msgstr ""
 
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:355(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:409(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:243(para)
-msgid "Add the <literal>[securitygroup]</literal> section and the following keys to it:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:364(title) ./doc/install-guide/section_neutron-ml2-compute-node.xml:282(title)
-msgid "To configure Compute to use Networking"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:365(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:283(para)
-msgid "By default, most distributions configure Compute to use legacy networking. You must reconfigure Compute to manage networks through Networking."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:394(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:420(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:312(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:338(para)
-msgid "By default, Compute uses an internal firewall service. Since Networking includes a firewall service, you must disable the Compute firewall service by using the <literal>nova.virt.firewall.NoopFirewallDriver</literal> firewall driver."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:402(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:320(para)
-msgid "Edit the <filename>/etc/nova/nova.conf</filename> and add the following keys to the <literal>[DEFAULT]</literal> section:"
-msgstr ""
-
 #: ./doc/install-guide/section_neutron-ml2-controller-node.xml:429(title) ./doc/install-guide/section_basics-queue.xml:96(title)
 msgid "To finalize installation"
 msgstr ""
@@ -1957,10 +3460,6 @@ msgstr ""
 msgid "The Networking service initialization scripts expect the variable <literal>NEUTRON_PLUGIN_CONF</literal> in file <filename>/etc/sysconfig/neutron</filename> to reference the configuration file associated with your chosen plug-in. Using ML2, for example, edit the <filename>/etc/sysconfig/neutron</filename> file and add the following:"
 msgstr ""
 
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:451(para) ./doc/install-guide/section_neutron-ovs-controller-node.xml:331(para) ./doc/install-guide/section_nova-networking-controller-node.xml:26(para)
-msgid "Restart the Compute services:"
-msgstr ""
-
 #: ./doc/install-guide/section_neutron-ml2-controller-node.xml:460(para) ./doc/install-guide/section_neutron-ovs-controller-node.xml:337(para)
 msgid "Start the Networking service and configure it to start when the system boots:"
 msgstr ""
@@ -1969,270 +3468,104 @@ msgstr ""
 msgid "Restart the Networking service:"
 msgstr ""
 
-#: ./doc/install-guide/section_keystone-services.xml:4(title)
-msgid "Define services and API endpoints"
+#: ./doc/install-guide/section_launch-instance-neutron.xml:6(title)
+msgid "Launch an instance with OpenStack Networking (neutron)"
 msgstr ""
 
-#: ./doc/install-guide/section_keystone-services.xml:5(para)
-msgid "So that the Identity Service can track which OpenStack services are installed and where they are located on the network, you must register each service in your OpenStack installation. To register a service, run these commands:"
+#: ./doc/install-guide/section_launch-instance-neutron.xml:95(para)
+msgid "Your first instance uses the <literal>default</literal> security group. By default, this security group implements a firewall that blocks remote access to instances. If you would like to permit remote access to your instance, launch it and then <link linkend=\"launch-instance-neutron-remoteaccess\"> configure remote access</link>."
 msgstr ""
 
-#: ./doc/install-guide/section_keystone-services.xml:11(para)
-msgid "<placeholder-1/>. Describes the service."
+#: ./doc/install-guide/section_launch-instance-neutron.xml:173(para)
+msgid "Verify the <literal>demo-net</literal> tenant network gateway:"
 msgstr ""
 
-#: ./doc/install-guide/section_keystone-services.xml:15(para)
-msgid "<placeholder-1/>. Associates <glossterm baseform=\"API endpoint\">API endpoints</glossterm> with the service."
+#: ./doc/install-guide/section_launch-instance-neutron.xml:185(para)
+msgid "Verify the <literal>ext-net</literal> external network:"
 msgstr ""
 
-#: ./doc/install-guide/section_keystone-services.xml:20(para)
-msgid "You must also register the Identity Service itself. Use the <code>OS_SERVICE_TOKEN</code> environment variable, as set previously, for authentication."
+#: ./doc/install-guide/section_launch-instance-neutron.xml:224(para)
+msgid "Create a <glossterm>floating IP address</glossterm> on the <literal>ext-net</literal> external network:"
 msgstr ""
 
-#: ./doc/install-guide/section_keystone-services.xml:25(para)
-msgid "Create a service entry for the Identity Service:"
+#: ./doc/install-guide/section_launch-instance-neutron.xml:242(para)
+msgid "Associate the floating IP address with your instance:"
 msgstr ""
 
-#: ./doc/install-guide/section_keystone-services.xml:36(para) ./doc/install-guide/object-storage/section_object-storage-install.xml:89(para)
-msgid "The service ID is randomly generated and is different from the one shown here."
+#: ./doc/install-guide/section_launch-instance-neutron.xml:249(para)
+msgid "Check the status of your floating IP address:"
 msgstr ""
 
-#: ./doc/install-guide/section_keystone-services.xml:40(para)
-msgid "Specify an API endpoint for the Identity Service by using the returned service ID. When you specify an endpoint, you provide URLs for the public API, internal API, and admin API. In this guide, the <literal>controller</literal> host name is used. Note that the Identity Service uses a different port for the admin API."
+#: ./doc/install-guide/ch_glance.xml:6(title)
+msgid "Add the Image Service"
 msgstr ""
 
-#: ./doc/install-guide/section_keystone-services.xml:63(para)
-msgid "You will need to create an additional endpoint for each service added to your OpenStack environment. The sections of this guide associated with the installation of each service include the endpoint creation step specific to the service."
+#: ./doc/install-guide/ch_glance.xml:7(para)
+msgid "The OpenStack Image Service (glance) enables users to discover, register, and retrieve virtual machine images. It offers a <glossterm baseform=\"RESTful\">REST</glossterm> API that enables you to query virtual machine image metadata and retrieve an actual image. You can store virtual machine images made available through the Image Service in a variety of locations, from simple file systems to object-storage systems like OpenStack Object Storage."
 msgstr ""
 
-#: ./doc/install-guide/section_keystone-verify.xml:6(title)
-msgid "Verify the Identity Service installation"
+#: ./doc/install-guide/ch_glance.xml:15(para)
+msgid "For simplicity, this guide describes configuring the Image Service to use the <literal>file</literal> back end, which uploads and stores in a directory on the controller node hosting the Image Service. By default, this directory is <filename>/var/lib/glance/images/</filename>."
 msgstr ""
 
-#: ./doc/install-guide/section_keystone-verify.xml:9(para)
-msgid "To verify that the Identity Service is installed and configured correctly, clear the values in the <envar>OS_SERVICE_TOKEN</envar> and <envar>OS_SERVICE_ENDPOINT</envar> environment variables:"
+#: ./doc/install-guide/ch_glance.xml:20(para)
+msgid "Before you proceed, ensure that the controller node has at least several gigabytes of space available in this directory."
 msgstr ""
 
-#: ./doc/install-guide/section_keystone-verify.xml:15(para)
-msgid "These variables, which were used to bootstrap the administrative user and register the Identity Service, are no longer needed."
+#: ./doc/install-guide/ch_glance.xml:22(para)
+msgid "For information on requirements for other back ends, see <link href=\"http://docs.openstack.org/trunk/config-reference/content/ch_configuring-openstack-image-service.html\"><citetitle>Configuration Reference</citetitle></link>."
 msgstr ""
 
-#: ./doc/install-guide/section_keystone-verify.xml:20(para)
-msgid "You can now use regular user name-based authentication."
+#: ./doc/install-guide/section_basics-prerequisites.xml:6(title) ./doc/install-guide/object-storage/section_object-storage-install.xml:28(title)
+msgid "Before you begin"
 msgstr ""
 
-#: ./doc/install-guide/section_keystone-verify.xml:22(para)
-msgid "Request a authentication token by using the <literal>admin</literal> user and the password you chose for that user:"
+#: ./doc/install-guide/section_basics-prerequisites.xml:7(para)
+msgid "For a functional environment, OpenStack doesn't require a significant amount of resources. We recommend that your environment meets or exceeds the following minimum requirements which can support several minimal <glossterm>CirrOS</glossterm> instances:"
 msgstr ""
 
-#: ./doc/install-guide/section_keystone-verify.xml:27(para)
-msgid "In response, you receive a token paired with your user ID. This verifies that the Identity Service is running on the expected endpoint and that your user account is established with the expected credentials."
+#: ./doc/install-guide/section_basics-prerequisites.xml:13(para)
+msgid "Controller Node: 1 processor, 2 GB memory, and 5 GB storage"
 msgstr ""
 
-#: ./doc/install-guide/section_keystone-verify.xml:33(para)
-msgid "Verify that authorization behaves as expected. To do so, request authorization on a tenant:"
+#: ./doc/install-guide/section_basics-prerequisites.xml:17(para)
+msgid "Network Node: 1 processor, 512 MB memory, and 5 GB storage"
 msgstr ""
 
-#: ./doc/install-guide/section_keystone-verify.xml:38(para)
-msgid "In response, you receive a token that includes the ID of the tenant that you specified. This verifies that your user account has an explicitly defined role on the specified tenant and the tenant exists as expected."
+#: ./doc/install-guide/section_basics-prerequisites.xml:21(para)
+msgid "Compute Node: 1 processor, 2 GB memory, and 10 GB storage"
 msgstr ""
 
-#: ./doc/install-guide/section_keystone-verify.xml:44(para)
-msgid "You can also set your <literal>--os-*</literal> variables in your environment to simplify command-line usage. Set up a <filename>admin-openrc.sh</filename> file with the admin credentials and admin endpoint:"
+#: ./doc/install-guide/section_basics-prerequisites.xml:25(para)
+msgid "To minimize clutter and provide more resources for OpenStack, we recommend a minimal installation of your Linux distribution. Also, we strongly recommend that you install a 64-bit version of your distribution on at least the compute node. If you install a 32-bit version of your distribution on the compute node, attempting to start an instance using a 64-bit image will fail."
 msgstr ""
 
-#: ./doc/install-guide/section_keystone-verify.xml:54(para)
-msgid "Source this file to read in the environment variables:"
+#: ./doc/install-guide/section_basics-prerequisites.xml:32(para)
+msgid "A single disk partition on each node works for most basic installations. However, you should consider <glossterm>Logical Volume Manager (LVM)</glossterm> for installations with optional services such as Block Storage."
 msgstr ""
 
-#: ./doc/install-guide/section_keystone-verify.xml:59(para)
-msgid "Verify that your <filename>admin-openrc.sh</filename> file is configured correctly. Run the same command without the <literal>--os-*</literal> arguments:"
+#: ./doc/install-guide/section_basics-prerequisites.xml:37(para)
+msgid "Many users build their test environments on <glossterm baseform=\"virtual machine (VM)\">virtual machines (VMs)</glossterm>. The primary benefits of VMs include the following:"
 msgstr ""
 
-#: ./doc/install-guide/section_keystone-verify.xml:63(para)
-msgid "The command returns a token and the ID of the specified tenant. This verifies that you have configured your environment variables correctly."
+#: ./doc/install-guide/section_basics-prerequisites.xml:43(para)
+msgid "One physical server can support multiple nodes, each with almost any number of network interfaces."
 msgstr ""
 
-#: ./doc/install-guide/section_keystone-verify.xml:68(para)
-msgid "Verify that your admin account has authorization to perform administrative commands:"
+#: ./doc/install-guide/section_basics-prerequisites.xml:47(para)
+msgid "Ability to take periodic \"snap shots\" throughout the installation process and \"roll back\" to a working configuration in the event of a problem."
 msgstr ""
 
-#: ./doc/install-guide/section_keystone-verify.xml:85(para)
-msgid "Seeing that the <literal>id</literal> in the output from the <placeholder-1/> command matches the <literal>user_id</literal> in the <placeholder-2/> command, and that the admin role is listed for that user, for the related tenant, this verifies that your user account has the <literal>admin</literal> role, which matches the role used in the Identity Service <filename>policy.json</filename> file."
+#: ./doc/install-guide/section_basics-prerequisites.xml:52(para)
+msgid "However, VMs will reduce performance of your instances, particularly if your hypervisor and/or processor lacks support for hardware acceleration of nested VMs."
 msgstr ""
 
-#: ./doc/install-guide/section_keystone-verify.xml:95(para)
-msgid "As long as you define your credentials and the Identity Service endpoint through the command line or environment variables, you can run all OpenStack client commands from any machine. For details, see <xref linkend=\"ch_clients\"/>."
+#: ./doc/install-guide/section_basics-prerequisites.xml:56(para)
+msgid "If you choose to install on VMs, make sure your hypervisor permits <glossterm>promiscuous mode</glossterm> on the <glossterm>external network</glossterm>."
 msgstr ""
 
-#: ./doc/install-guide/ch_networking.xml:6(title)
-msgid "Add a networking service"
-msgstr ""
-
-#: ./doc/install-guide/ch_networking.xml:7(para)
-msgid "Configuring networking in OpenStack can be a bewildering experience. This guide provides step-by-step instructions for both OpenStack Networking (neutron) and the legacy networking (nova-network) service. If you are unsure which to use, we recommend trying OpenStack Networking because it offers a considerable number of features and flexibility including <glossterm baseform=\"plug-in\">plug-ins</glossterm> for a variety of emerging products supporting <glossterm>virtual networking</glossterm>. See the <link href=\"http://docs.openstack.org/admin-guide-cloud/content/ch_networking.html\">Networking</link> chapter of the <citetitle>OpenStack Cloud Administrator Guide</citetitle> for more information."
-msgstr ""
-
-#: ./doc/install-guide/ch_networking.xml:20(title) ./doc/install-guide/section_basics-networking-neutron.xml:6(title)
-msgid "OpenStack Networking (neutron)"
-msgstr ""
-
-#: ./doc/install-guide/ch_networking.xml:23(title)
-msgid "Modular Layer 2 (ML2) plug-in"
-msgstr ""
-
-#: ./doc/install-guide/ch_networking.xml:31(title) ./doc/install-guide/section_basics-networking-nova.xml:6(title)
-msgid "Legacy networking (nova-network)"
-msgstr ""
-
-#: ./doc/install-guide/ch_networking.xml:38(para)
-msgid "Your OpenStack environment now includes the core components necessary to launch a basic instance. You can <link linkend=\"launch-instance\">launch an instance</link> or add more services to your environment in the following chapters."
-msgstr ""
-
-#: ./doc/install-guide/ch_horizon.xml:6(title)
-msgid "Add the dashboard"
-msgstr ""
-
-#: ./doc/install-guide/ch_horizon.xml:7(para)
-msgid "The OpenStack dashboard, also known as <link href=\"https://github.com/openstack/horizon/\">Horizon</link>, is a Web interface that enables cloud administrators and users to manage various OpenStack resources and services."
-msgstr ""
-
-#: ./doc/install-guide/ch_horizon.xml:12(para)
-msgid "The dashboard enables web-based interactions with the OpenStack Compute cloud controller through the OpenStack APIs."
-msgstr ""
-
-#: ./doc/install-guide/ch_horizon.xml:15(para)
-msgid "These instructions show an example deployment configured with an Apache web server."
-msgstr ""
-
-#: ./doc/install-guide/ch_horizon.xml:17(para)
-msgid "After you <link linkend=\"install_dashboard\">install and configure the dashboard</link>, you can complete the following tasks:"
-msgstr ""
-
-#: ./doc/install-guide/ch_horizon.xml:22(para)
-msgid "Customize your dashboard. See section <link href=\"http://docs.openstack.org/admin-guide-cloud/content/ch_install-dashboard.html#dashboard-custom-brand\">Customize the dashboard</link> in the <link href=\"http://docs.openstack.org/admin-guide-cloud/content/\"><citetitle>OpenStack Cloud Administrator Guide</citetitle></link>."
-msgstr ""
-
-#: ./doc/install-guide/ch_horizon.xml:30(para)
-msgid "Set up session storage for the dashboard. See <xref linkend=\"dashboard-sessions\"/>."
-msgstr ""
-
-#: ./doc/install-guide/ch_horizon.xml:39(para)
-msgid "Your OpenStack environment now includes the dashboard. You can <link linkend=\"launch-instance\">launch an instance</link> or add more services to your environment in the following chapters."
-msgstr ""
-
-#: ./doc/install-guide/section_heat-verify.xml:6(title)
-msgid "Verify the Orchestration service installation"
-msgstr ""
-
-#: ./doc/install-guide/section_heat-verify.xml:8(para)
-msgid "To verify that the Orchestration service is installed and configured correctly, make sure that your credentials are set up correctly in the <filename>demo-openrc.sh</filename> file. Source the file, as follows:"
-msgstr ""
-
-#: ./doc/install-guide/section_heat-verify.xml:14(para)
-msgid "The Orchestration Module uses templates to describe stacks. To learn about the template languages, see <link href=\"http://docs.openstack.org/developer/heat/template_guide/index.html\">the Template Guide</link> in the <link href=\"http://docs.openstack.org/developer/heat/\">Heat developer documentation</link>."
-msgstr ""
-
-#: ./doc/install-guide/section_heat-verify.xml:20(para)
-msgid "Create a test template in the <filename>test-stack.yml</filename> file with the following content:"
-msgstr ""
-
-#: ./doc/install-guide/section_heat-verify.xml:24(para)
-msgid "Use the <placeholder-1/> command to create a stack from this template:"
-msgstr ""
-
-#: ./doc/install-guide/section_heat-verify.xml:35(para)
-msgid "Verify that the stack was created successfully with the <placeholder-1/> command:"
-msgstr ""
-
-#: ./doc/install-guide/ch_ceilometer.xml:6(title)
-msgid "Add the Telemetry module"
-msgstr ""
-
-#: ./doc/install-guide/ch_ceilometer.xml:7(para)
-msgid "Telemetry provides a framework for monitoring and metering the OpenStack cloud. It is also known as the ceilometer project."
-msgstr ""
-
-#: ./doc/install-guide/ch_ceilometer.xml:19(para)
-msgid "Your OpenStack environment now includes Telemetry. You can <link linkend=\"launch-instance\">launch an instance</link> or add more services to your environment in the previous chapters."
-msgstr ""
-
-#: ./doc/install-guide/ch_keystone.xml:6(title)
-msgid "Configure the Identity Service"
-msgstr ""
-
-#: ./doc/install-guide/ch_heat.xml:6(title)
-msgid "Add the Orchestration service"
-msgstr ""
-
-#: ./doc/install-guide/ch_heat.xml:7(para)
-msgid "Use the Orchestration module to create cloud resources using a template language called HOT. The integrated project name is Heat."
-msgstr ""
-
-#: ./doc/install-guide/ch_heat.xml:15(para)
-msgid "Your OpenStack environment now includes Orchestration. You can <link linkend=\"launch-instance\">launch an instance</link> or add more services to your environment in the following chapters."
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-rabbitqm.xml:15(None)
-msgid "@@image: 'figures/debconf-screenshots/rabbitmq-host.png'; md5=5353ad857884a2d31847cf82efbdc6b6"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-rabbitqm.xml:22(None)
-msgid "@@image: 'figures/debconf-screenshots/rabbitmq-user.png'; md5=33a3c1182e79ed65f1b1b63f2156792c"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-rabbitqm.xml:29(None)
-msgid "@@image: 'figures/debconf-screenshots/rabbitmq-password.png'; md5=6385185200d20e96b6316ae15ae1255d"
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-rabbitqm.xml:6(title)
-msgid "RabbitMQ credentials parameters"
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-rabbitqm.xml:7(para)
-msgid "For every package that must connect to a Messaging Server, the Debian package enables you to configure the IP address for that server and the user name and password that is used to connect. The following example shows configuration with the <systemitem class=\"service\">ceilometer-common</systemitem> package:"
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-rabbitqm.xml:33(para)
-msgid "These debconf screens appear in: <systemitem class=\"service\">ceilometer-common</systemitem>, <systemitem class=\"service\">cinder-common</systemitem>, <systemitem class=\"service\">glance-common</systemitem>, <systemitem class=\"service\">heat-common</systemitem>, <systemitem class=\"service\">neutron-common</systemitem> and <systemitem class=\"service\">nova-common</systemitem>."
-msgstr ""
-
-#: ./doc/install-guide/ch_nova.xml:7(title)
-msgid "Configure Compute services"
-msgstr ""
-
-#: ./doc/install-guide/section_ceilometer-cinder.xml:7(title)
-msgid "Add the Block Storage service agent for Telemetry"
-msgstr ""
-
-#: ./doc/install-guide/section_ceilometer-cinder.xml:10(para)
-msgid "To retrieve volume samples, you must configure the Block Storage service to send notifications to the bus."
-msgstr ""
-
-#: ./doc/install-guide/section_ceilometer-cinder.xml:13(para)
-msgid "Edit <filename>/etc/cinder/cinder.conf</filename> and add in the <literal>[DEFAULT]</literal> section on the controller and volume nodes:"
-msgstr ""
-
-#: ./doc/install-guide/section_ceilometer-cinder.xml:19(para)
-msgid "Run the following commands on the controller and volume nodes:"
-msgstr ""
-
-#: ./doc/install-guide/section_ceilometer-cinder.xml:26(para)
-msgid "Restart the Block Storage services with their new settings."
-msgstr ""
-
-#: ./doc/install-guide/section_ceilometer-cinder.xml:28(para)
-msgid "On the controller node:"
-msgstr ""
-
-#: ./doc/install-guide/section_ceilometer-cinder.xml:33(para)
-msgid "On the volume node:"
+#: ./doc/install-guide/section_basics-prerequisites.xml:60(para)
+msgid "For more information about system requirements, see the <link href=\"http://docs.openstack.org/ops/\">OpenStack Operations Guide</link>."
 msgstr ""
 
 #: ./doc/install-guide/app_reserved_uids.xml:6(title) ./doc/install-guide/app_reserved_uids.xml:24(caption)
@@ -2503,100 +3836,236 @@ msgstr ""
 msgid "Restart the Compute and Networking services:"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-ntp.xml:6(title)
-msgid "Network Time Protocol (NTP)"
+#: ./doc/install-guide/section_heat-install.xml:5(title)
+msgid "Install the Orchestration service"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-ntp.xml:7(para)
-msgid "You must install <glossterm baseform=\"Network Time Protocol (NTP)\">NTP</glossterm> to properly synchronize services among nodes. We recommend that you configure the controller node to reference upstream servers and other nodes to reference the controller node."
+#: ./doc/install-guide/section_heat-install.xml:8(para) ./doc/install-guide/section_heat-install.xml:24(para)
+msgid "Install the Orchestration module on the controller node:"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-ntp.xml:15(title) ./doc/install-guide/section_basics-ntp.xml:57(title)
-msgid "To install the NTP service"
+#: ./doc/install-guide/section_heat-install.xml:13(para)
+msgid "Respond to prompts for <link linkend=\"debconf-dbconfig-common\">database management</link>, <link linkend=\"debconf-keystone_authtoken\"><systemitem>[keystone_authtoken]</systemitem> settings</link>, <link linkend=\"debconf-rabbitqm\">RabbitMQ credentials</link> and <link linkend=\"debconf-api-endpoints\">API endpoint</link> registration."
 msgstr ""
 
-#: ./doc/install-guide/section_basics-ntp.xml:23(title) ./doc/install-guide/section_basics-ntp.xml:65(title)
-msgid "To configure the NTP service"
+#: ./doc/install-guide/section_heat-install.xml:33(para)
+msgid "In the configuration file, specify the location of the database where the Orchestration service stores data. These examples use a MySQL database with a <literal>heat</literal> user on the controller node. Replace <replaceable>HEAT_DBPASS</replaceable> with the password for the database user:"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-ntp.xml:24(para)
-msgid "By default, the controller node synchronizes the time via a pool of public servers. However, you can optionally edit the <filename>/etc/ntp.conf</filename> file to configure alternative servers such as those provided by your organization."
+#: ./doc/install-guide/section_heat-install.xml:40(replaceable) ./doc/install-guide/section_heat-install.xml:46(replaceable) ./doc/install-guide/section_heat-install.xml:61(replaceable) ./doc/install-guide/section_heat-install.xml:63(replaceable)
+msgid "HEAT_DBPASS"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-ntp.xml:29(para) ./doc/install-guide/section_basics-ntp.xml:69(para)
-msgid "Edit the <filename>/etc/ntp.conf</filename> file:"
+#: ./doc/install-guide/section_heat-install.xml:41(para)
+msgid "Edit <filename>/etc/heat/heat.conf</filename> and modify the <literal>[database]</literal> section:"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-ntp.xml:30(para)
-msgid "Add, change, or remove the <literal>server</literal> keys as necessary for your environment. Replace <replaceable>NTP_SERVER</replaceable> with the hostname or IP address of suitable NTP server."
+#: ./doc/install-guide/section_heat-install.xml:49(para)
+msgid "By default, the Ubuntu packages create an SQLite database. Delete the <filename>heat.sqlite</filename> file that was created in the <filename>/var/lib/heat/</filename> directory so that it does not get used by mistake:"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-ntp.xml:34(replaceable)
-msgid "NTP_SERVER"
+#: ./doc/install-guide/section_heat-install.xml:56(para)
+msgid "Use the password that you set previously to log in as <literal>root</literal> and create a <literal>heat</literal> database user:"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-ntp.xml:36(para) ./doc/install-guide/section_basics-ntp.xml:74(para)
-msgid "Remove the <filename>/var/lib/ntp/ntp.conf.dhcp</filename> file if it exists."
+#: ./doc/install-guide/section_heat-install.xml:66(para)
+msgid "Create the heat service tables:"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-ntp.xml:41(para) ./doc/install-guide/section_basics-ntp.xml:79(para)
-msgid "Restart the NTP service:"
+#: ./doc/install-guide/section_heat-install.xml:69(para)
+msgid "Ignore <errortext>DeprecationWarning</errortext> errors."
 msgstr ""
 
-#: ./doc/install-guide/section_basics-ntp.xml:45(para) ./doc/install-guide/section_basics-ntp.xml:83(para)
-msgid "Start the NTP service and configure it to start when the system boots:"
+#: ./doc/install-guide/section_heat-install.xml:74(para)
+msgid "The Ubuntu packages do not correctly set up logging. Edit the <filename>/etc/heat/heat.conf</filename> file and change the <literal>[DEFAULT]</literal> section:"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-ntp.xml:55(title)
-msgid "Configure other nodes"
+#: ./doc/install-guide/section_heat-install.xml:88(para)
+msgid "Configure the Orchestration Service to use the RabbitMQ message broker."
 msgstr ""
 
-#: ./doc/install-guide/section_basics-ntp.xml:66(para)
-msgid "Configure the network and compute nodes to reference the controller node."
+#: ./doc/install-guide/section_heat-install.xml:90(para)
+msgid "Edit <filename>/etc/heat/heat.conf</filename> and modify the <literal>[DEFAULT]</literal> section:"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-ntp.xml:70(para)
-msgid "Comment out or remove all but one <literal>server</literal> key and change it to reference the controller node."
+#: ./doc/install-guide/section_heat-install.xml:99(para)
+msgid "Create a <literal>heat</literal> user that the Orchestration service can use to authenticate with the Identity Service. Use the <literal>service</literal> tenant and give the user the <literal>admin</literal> role:"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-ntp.xml:93(title)
-msgid "Verify operation"
+#: ./doc/install-guide/section_heat-install.xml:103(replaceable) ./doc/install-guide/section_heat-install.xml:119(replaceable)
+msgid "HEAT_PASS"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-ntp.xml:94(para)
-msgid "We recommend that you verify NTP synchronization before proceeding further. Some nodes, particularly those that reference the controller node, can take several minutes to synchronize."
+#: ./doc/install-guide/section_heat-install.xml:104(replaceable)
+msgid "heat@example.com"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-ntp.xml:98(title)
-msgid "To verify NTP synchronization"
+#: ./doc/install-guide/section_heat-install.xml:108(para)
+msgid "Edit the <filename>/etc/heat/heat.conf</filename> file to change the <literal>[keystone_authtoken]</literal> and <literal>[ec2authtoken]</literal> sections to add credentials to the Orchestration Service:"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-ntp.xml:100(para) ./doc/install-guide/section_basics-ntp.xml:115(para)
-msgid "Run this command on the <emphasis>controller</emphasis> node:"
+#: ./doc/install-guide/section_heat-install.xml:125(para)
+msgid "Register the Heat and CloudFormation APIs with the Identity Service so that other OpenStack services can locate these APIs. Register the services and specify the endpoints:"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-ntp.xml:107(para)
-msgid "Contents in the <emphasis>remote</emphasis> column should indicate the hostname or IP address of one or more NTP servers."
+#: ./doc/install-guide/section_heat-install.xml:145(para)
+msgid "Create the <literal>heat_stack_user</literal> role."
 msgstr ""
 
-#: ./doc/install-guide/section_basics-ntp.xml:110(para) ./doc/install-guide/section_basics-ntp.xml:134(para)
-msgid "Contents in the <emphasis>refid</emphasis> column typically reference IP addresses of upstream servers."
+#: ./doc/install-guide/section_heat-install.xml:146(para)
+msgid "This role is used as the default role for users created by the Orchestration module."
 msgstr ""
 
-#: ./doc/install-guide/section_basics-ntp.xml:122(para)
-msgid "Contents in the <emphasis>condition</emphasis> column should indicate <literal>sys.peer</literal> for at least one server."
+#: ./doc/install-guide/section_heat-install.xml:148(para)
+msgid "Run the following command to create the <literal>heat_stack_user</literal> role:"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-ntp.xml:126(para) ./doc/install-guide/section_basics-ntp.xml:139(para)
-msgid "Run this command on <emphasis>all other</emphasis> nodes:"
+#: ./doc/install-guide/section_heat-install.xml:153(para)
+msgid "Configure the metadata and waitcondition servers' URLs."
 msgstr ""
 
-#: ./doc/install-guide/section_basics-ntp.xml:131(para)
-msgid "Contents in the <emphasis>remote</emphasis> column should indicate the hostname of the controller node."
+#: ./doc/install-guide/section_heat-install.xml:154(para)
+msgid "Edit the <filename>/etc/heat/heat.conf</filename> file and modify the following options in the <literal>[DEFAULT]</literal> section:"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-ntp.xml:145(para)
-msgid "Contents in the <emphasis>condition</emphasis> column should indicate <literal>sys.peer</literal>."
+#: ./doc/install-guide/section_heat-install.xml:160(replaceable) ./doc/install-guide/section_heat-install.xml:163(replaceable) ./doc/install-guide/section_heat-install.xml:168(replaceable) ./doc/install-guide/section_heat-install.xml:170(replaceable)
+msgid "10.0.0.11"
+msgstr ""
+
+#: ./doc/install-guide/section_heat-install.xml:164(para)
+msgid "Run the following commands to modify the <literal>[DEFAULT]</literal> section of the <filename>/etc/heat/heat.conf</filename> file:"
+msgstr ""
+
+#: ./doc/install-guide/section_heat-install.xml:172(para)
+msgid "The example uses the IP address of the controller (10.0.0.11) instead of the <literal>controller</literal> host name since our example architecture does not include a DNS setup. Make sure that the instances can resolve the controller host name if you choose to use it in the URLs."
+msgstr ""
+
+#: ./doc/install-guide/section_heat-install.xml:186(para)
+msgid "Start the <systemitem class=\"service\">heat-api</systemitem>, <systemitem class=\"service\">heat-api-cfn</systemitem> and <systemitem class=\"service\">heat-engine</systemitem> services and configure them to start when the system boots:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:6(title) ./doc/install-guide/section_neutron-ovs-network-node.xml:6(title)
+msgid "Configure network node"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:188(title)
+msgid "To configure the Layer-3 (L3) agent"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:189(para)
+msgid "The <glossterm>Layer-3 (L3) agent</glossterm> provides routing services for instance virtual networks."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:198(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:213(para)
+msgid "We recommend adding <literal>verbose = True</literal> to the <literal>[DEFAULT]</literal> section in <filename>/etc/neutron/l3_agent.ini</filename> to assist with troubleshooting."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:205(para)
+msgid "Edit the <filename>/etc/neutron/l3_agent.ini</filename> file and add the following keys to the <literal>[DEFAULT]</literal> section:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:221(title)
+msgid "To configure the DHCP agent"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:222(para)
+msgid "The <glossterm>DHCP agent</glossterm> provides <glossterm>DHCP</glossterm> services for instance virtual networks."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:234(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:250(para)
+msgid "We recommend adding <literal>verbose = True</literal> to the <literal>[DEFAULT]</literal> section in <filename>/etc/neutron/dhcp_agent.ini</filename> to assist with troubleshooting."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:241(para)
+msgid "Edit the <filename>/etc/neutron/dhcp_agent.ini</filename> file and add the following keys to the <literal>[DEFAULT]</literal> section:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:258(title)
+msgid "To configure the metadata agent"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:259(para)
+msgid "The <glossterm>metadata agent</glossterm> provides configuration information such as credentials for remote access to instances."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:263(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:293(para)
+msgid "Replace <replaceable>NEUTRON_PASS</replaceable> with the password you chose for the <literal>neutron</literal> user in the Identity service. Replace <replaceable>METADATA_SECRET</replaceable> with a suitable secret for the metadata proxy."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:281(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:306(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:329(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:341(replaceable)
+msgid "METADATA_SECRET"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:283(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:308(para)
+msgid "We recommend adding <literal>verbose = True</literal> to the <literal>[DEFAULT]</literal> section in <filename>/etc/neutron/metadata_agent.ini</filename> to assist with troubleshooting."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:290(para)
+msgid "Edit the <filename>/etc/neutron/metadata_agent.ini</filename> file and add the following keys to the <literal>[DEFAULT]</literal> section:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:316(para)
+msgid "Perform the next two steps on the <emphasis>controller</emphasis> node."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:321(para)
+msgid "On the <emphasis>controller</emphasis> node, configure Compute to use the metadata service:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:323(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:335(para)
+msgid "Replace <replaceable>METADATA_SECRET</replaceable> with the secret you chose for the metadata proxy."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:332(para)
+msgid "On the <emphasis>controller</emphasis> node, edit the <filename>/etc/nova/nova.conf</filename> file and add the following keys to the <literal>[DEFAULT]</literal> section:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:344(para)
+msgid "On the <emphasis>controller</emphasis> node, restart the Compute <glossterm>API</glossterm> service:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:352(para)
+msgid "The ML2 plug-in uses the Open vSwitch (OVS) mechanism (agent) to build virtual networking framework for instances."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:356(para)
+msgid "Replace <replaceable>INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS</replaceable> with the IP address of the instance tunnels network interface on your network node. This guide uses <literal>10.0.1.21</literal> for the IP address of the instance tunnels network interface on the network node."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:383(para)
+msgid "Edit the <filename>/etc/neutron/plugins/ml2/ml2_conf.ini</filename> file."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:400(para)
+msgid "Replace <replaceable>INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS</replaceable> with the IP address of the instance tunnels network interface on your network node."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:419(para)
+msgid "The OVS service provides the underlying virtual networking framework for instances. The integration bridge <literal>br-int</literal> handles internal instance network traffic within OVS. The external bridge <literal>br-ex</literal> handles external instance network traffic within OVS. The external bridge requires a port on the physical external network interface to provide instances with external network access. In essence, this port bridges the virtual and physical external networks in your environment."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:452(para)
+msgid "Add the external bridge:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:456(para)
+msgid "Add a port to the external bridge that connects to the physical external network interface:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:463(para)
+msgid "Depending on your network interface driver, you may need to disable <glossterm>Generic Receive Offload (GRO)</glossterm> to achieve suitable throughput between your instances and the external network."
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:467(para)
+msgid "To temporarily disable GRO on the external network interface while testing your environment:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:505(para)
+msgid "Start the Networking services and configure them to start when the system boots:"
+msgstr ""
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml:525(para)
+msgid "Restart the Networking services:"
 msgstr ""
 
 #: ./doc/install-guide/section_ceilometer-glance.xml:6(title)
@@ -2617,286 +4086,384 @@ msgstr ""
 
 #. When image changes, this message will be marked fuzzy or untranslated for you.
 #. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_basics-networking-nova.xml:25(None) ./doc/install-guide/ch_overview.xml:147(None)
-msgid "@@image: 'figures/installguide_arch-nova.png'; md5=da24b356516c960a33ab2b4b72840774"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:7(para)
-msgid "The example architecture with legacy networking (nova-network) requires a controller node and at least one compute node. The controller node contains one network interface on the <glossterm>management network</glossterm>. The compute node contains one network interface on the management network and one on the <glossterm>external network</glossterm>."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:14(para)
-msgid "Network interface names vary by distribution. Traditionally, interfaces use \"eth\" followed by a sequential number. To cover all variations, this guide simply refers to the first interface as the interface with the lowest number and the second interface as the interface with the highest number."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:21(title) ./doc/install-guide/ch_overview.xml:143(title)
-msgid "Two-node architecture with legacy networking (nova-network)"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:29(para) ./doc/install-guide/section_basics-networking-neutron.xml:33(para)
-msgid "Unless you intend to use the exact configuration provided in this example architecture, you must modify the networks in this procedure to match your environment. Also, each node must resolve the other nodes by name in addition to IP address. For example, the <replaceable>controller</replaceable> name must resolve to <literal>10.0.0.11</literal>, the IP address of the management interface on the controller node."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:37(para) ./doc/install-guide/section_basics-networking-neutron.xml:41(para)
-msgid "Reconfiguring network interfaces will interrupt network connectivity. We recommend using a local terminal session for these procedures."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:42(title) ./doc/install-guide/section_basics-networking-neutron.xml:46(title)
-msgid "Controller node"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:44(title) ./doc/install-guide/section_basics-networking-nova.xml:76(title) ./doc/install-guide/section_basics-networking-neutron.xml:48(title) ./doc/install-guide/section_basics-networking-neutron.xml:83(title) ./doc/install-guide/section_basics-networking-neutron.xml:165(title)
-msgid "To configure networking:"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:46(para) ./doc/install-guide/section_basics-networking-nova.xml:78(para) ./doc/install-guide/section_basics-networking-neutron.xml:50(para) ./doc/install-guide/section_basics-networking-neutron.xml:85(para) ./doc/install-guide/section_basics-networking-neutron.xml:167(para)
-msgid "Configure the first interface as the management interface:"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:47(para) ./doc/install-guide/section_basics-networking-neutron.xml:51(para)
-msgid "IP address: 10.0.0.11"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:48(para) ./doc/install-guide/section_basics-networking-nova.xml:80(para) ./doc/install-guide/section_basics-networking-neutron.xml:52(para) ./doc/install-guide/section_basics-networking-neutron.xml:87(para) ./doc/install-guide/section_basics-networking-neutron.xml:94(para) ./doc/install-guide/section_basics-networking-neutron.xml:169(para) ./doc/install-guide/section_basics-networking-neutron.xml:180(para)
-msgid "Network mask: 255.255.255.0 (or /24)"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:49(para) ./doc/install-guide/section_basics-networking-nova.xml:81(para) ./doc/install-guide/section_basics-networking-neutron.xml:53(para) ./doc/install-guide/section_basics-networking-neutron.xml:88(para) ./doc/install-guide/section_basics-networking-neutron.xml:170(para)
-msgid "Default gateway: 10.0.0.1"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:53(title) ./doc/install-guide/section_basics-networking-nova.xml:131(title) ./doc/install-guide/section_basics-networking-neutron.xml:57(title) ./doc/install-guide/section_basics-networking-neutron.xml:140(title) ./doc/install-guide/section_basics-networking-neutron.xml:188(title)
-msgid "To configure name resolution:"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:55(para) ./doc/install-guide/section_basics-networking-neutron.xml:59(para)
-msgid "Set the hostname of the node to <code><replaceable>controller</replaceable></code>."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:59(para) ./doc/install-guide/section_basics-networking-nova.xml:136(para) ./doc/install-guide/section_basics-networking-neutron.xml:63(para) ./doc/install-guide/section_basics-networking-neutron.xml:145(para) ./doc/install-guide/section_basics-networking-neutron.xml:193(para)
-msgid "Edit the <filename>/etc/hosts</filename> file to contain the following:"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:67(para) ./doc/install-guide/section_basics-networking-nova.xml:144(para) ./doc/install-guide/section_basics-networking-neutron.xml:74(para) ./doc/install-guide/section_basics-networking-neutron.xml:156(para) ./doc/install-guide/section_basics-networking-neutron.xml:204(para)
-msgid "You must remove or comment the line beginning with <literal>127.0.1.1</literal>."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:74(title) ./doc/install-guide/section_basics-networking-neutron.xml:163(title)
-msgid "Compute node"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:79(para) ./doc/install-guide/section_basics-networking-neutron.xml:168(para)
-msgid "IP address: 10.0.0.31"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:83(para) ./doc/install-guide/section_basics-networking-neutron.xml:172(para)
-msgid "Additional compute nodes should use 10.0.0.32, 10.0.0.33, and so on."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:88(para)
-msgid "The external interface uses a special configuration without an IP address assigned to it. Configure the second interface as the external interface:"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:91(para)
-msgid "Replace <replaceable>INTERFACE_NAME</replaceable> with the actual interface name. For example, <emphasis>eth1</emphasis> or <emphasis>ens224</emphasis>."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:96(para) ./doc/install-guide/section_basics-networking-neutron.xml:105(para)
-msgid "Edit the <filename>/etc/network/interfaces</filename> file to contain the following:"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:105(para) ./doc/install-guide/section_basics-networking-neutron.xml:114(para)
-msgid "Edit the <filename>/etc/sysconfig/network-scripts/ifcfg-<replaceable>INTERFACE_NAME</replaceable></filename> file to contain the following:"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:108(para) ./doc/install-guide/section_basics-networking-neutron.xml:117(para)
-msgid "Do not change the <literal>HWADDR</literal> and <literal>UUID</literal> keys."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:116(para) ./doc/install-guide/section_basics-networking-neutron.xml:125(para)
-msgid "Edit the <filename>/etc/sysconfig/network/ifcfg-<replaceable>INTERFACE_NAME</replaceable></filename> file to contain the following:"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:125(para) ./doc/install-guide/section_basics-networking-neutron.xml:134(para)
-msgid "Restart networking:"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:133(para) ./doc/install-guide/section_basics-networking-neutron.xml:190(para)
-msgid "Set the hostname of the node to <code>compute1</code>."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:151(title) ./doc/install-guide/section_basics-networking-neutron.xml:211(title) ./doc/install-guide/section_neutron-initial-networks.xml:228(title)
-msgid "Verify connectivity"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:152(para) ./doc/install-guide/section_basics-networking-neutron.xml:212(para)
-msgid "We recommend that you verify network connectivity to the internet and among the nodes before proceeding further."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:156(para) ./doc/install-guide/section_basics-networking-neutron.xml:216(para)
-msgid "From the <emphasis>controller</emphasis> node, <placeholder-1/> a site on the internet:"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:170(para) ./doc/install-guide/section_basics-networking-neutron.xml:245(para)
-msgid "From the <emphasis>controller</emphasis> node, <placeholder-1/> the management interface on the <emphasis>compute</emphasis> node:"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:173(replaceable) ./doc/install-guide/section_basics-networking-neutron.xml:248(replaceable)
-msgid "compute1"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:185(para) ./doc/install-guide/section_basics-networking-neutron.xml:304(para)
-msgid "From the <emphasis>compute</emphasis> node, <placeholder-1/> a site on the internet:"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-networking-nova.xml:199(para) ./doc/install-guide/section_basics-networking-neutron.xml:318(para)
-msgid "From the <emphasis>compute</emphasis> node, <placeholder-1/> the management interface on the <emphasis>controller</emphasis> node:"
+#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:30(None)
+msgid "@@image: 'figures/debconf-screenshots/service_keystone_authtoken_server_hostname.png'; md5=aafd53894e1d960531d4901123952117"
 msgstr ""
 
 #. When image changes, this message will be marked fuzzy or untranslated for you.
 #. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_basics-networking-neutron.xml:29(None) ./doc/install-guide/ch_overview.xml:98(None)
-msgid "@@image: 'figures/installguide_arch-neutron.png'; md5=9b3d2f2e5f9d88d198511ecbca829c6d"
+#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:37(None)
+msgid "@@image: 'figures/debconf-screenshots/service_keystone_authtoken_admin_tenant_name.png'; md5=a935563e4fba9b00040e35cdcfffc732"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-networking-neutron.xml:7(para)
-msgid "The example architecture with OpenStack Networking (neutron) requires one controller node, one network node, and at least one compute node. The controller node contains one network interface on the <glossterm>management network</glossterm>. The network node contains one network interface on the management network, one on the <glossterm>instance tunnels network</glossterm>, and one on the <glossterm>external network</glossterm>. The compute node contains one network interface on the management network and one on the instance tunnels network."
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:44(None)
+msgid "@@image: 'figures/debconf-screenshots/service_keystone_authtoken_tenant_admin_user.png'; md5=fe3dc93c591b3e9783d4d05556efcf25"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-networking-neutron.xml:17(para)
-msgid "Network interface names vary by distribution. Traditionally, interfaces use \"eth\" followed by a sequential number. To cover all variations, this guide simply refers to the first interface as the interface with the lowest number, the second interface as the interface with the middle number, and the third interface as the interface with the highest number."
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:51(None)
+msgid "@@image: 'figures/debconf-screenshots/service_keystone_authtoken_admin_password.png'; md5=0c30c80315d5e636dbe93a938fc2822b"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-networking-neutron.xml:25(title) ./doc/install-guide/ch_overview.xml:94(title)
-msgid "Three-node architecture with OpenStack Networking (neutron)"
+#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:6(title)
+msgid "Services and the [keystone_authtoken]"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-networking-neutron.xml:81(title)
-msgid "Network node"
+#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:7(para)
+msgid "Because most OpenStack services must access the Identity Service, you must configure the IP address of the <code>keystone</code> server to be able to access it. You must also configure the <code>admin_tenant_name</code>, <code>admin_user</code>, and <code>admin_password</code> options for each service to work."
 msgstr ""
 
-#: ./doc/install-guide/section_basics-networking-neutron.xml:86(para)
-msgid "IP address: 10.0.0.21"
+#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:13(para)
+msgid "Generally, this section looks like this:"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-networking-neutron.xml:91(para) ./doc/install-guide/section_basics-networking-neutron.xml:177(para)
-msgid "Configure the second interface as the instance tunnels interface:"
+#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:21(para)
+msgid "The debconf system helps users configure the <code>auth_host</code>, <code>admin_tenant_name</code>, <code>admin_user</code> and <code>admin_password</code> options."
 msgstr ""
 
-#: ./doc/install-guide/section_basics-networking-neutron.xml:93(para)
-msgid "IP address: 10.0.1.21"
+#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:25(para)
+msgid "The following screens show an example Image Service configuration:"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-networking-neutron.xml:97(para)
-msgid "The external interface uses a special configuration without an IP address assigned to it. Configure the third interface as the external interface:"
+#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:55(para)
+msgid "This information is stored in the configuration file for each service. For example:"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-networking-neutron.xml:100(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:458(para)
-msgid "Replace <replaceable>INTERFACE_NAME</replaceable> with the actual interface name. For example, <emphasis>eth2</emphasis> or <emphasis>ens256</emphasis>."
+#: ./doc/install-guide/section_debconf-keystone_authtoken.xml:63(para)
+msgid "The Debian OpenStack packages offer automation for this, so OpenStack users do not have to manually edit the configuration files."
 msgstr ""
 
-#: ./doc/install-guide/section_basics-networking-neutron.xml:142(para)
-msgid "Set the hostname of the node to <code>network</code>."
+#: ./doc/install-guide/bk-openstack-install-guide.xml:7(title)
+msgid "OpenStack Installation Guide for <phrase os=\"rhel;centos;fedora\">Red Hat Enterprise Linux, CentOS, and Fedora</phrase><phrase os=\"ubuntu\">Ubuntu 12.04/14.04 (LTS)</phrase><phrase os=\"debian\">Debian 7.0 (Wheezy)</phrase><phrase os=\"opensuse\">openSUSE and SUSE Linux Enterprise Server</phrase>"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-networking-neutron.xml:179(para)
-msgid "IP address: 10.0.1.31"
+#: ./doc/install-guide/bk-openstack-install-guide.xml:15(phrase)
+msgid "Red Hat Enterprise Linux, CentOS, and Fedora"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-networking-neutron.xml:182(para)
-msgid "Additional compute nodes should use 10.0.1.32, 10.0.1.33, and so on."
+#: ./doc/install-guide/bk-openstack-install-guide.xml:16(phrase)
+msgid "Ubuntu 12.04/14.04 (LTS)"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-networking-neutron.xml:230(para)
-msgid "From the <emphasis>controller</emphasis> node, <placeholder-1/> the management interface on the <emphasis>network</emphasis> node:"
+#: ./doc/install-guide/bk-openstack-install-guide.xml:17(phrase)
+msgid "openSUSE and SUSE Linux Enterprise Server"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-networking-neutron.xml:233(replaceable)
-msgid "network"
+#: ./doc/install-guide/bk-openstack-install-guide.xml:18(phrase)
+msgid "Debian 7.0 (Wheezy)"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-networking-neutron.xml:260(para)
-msgid "From the <emphasis>network</emphasis> node, <placeholder-1/> a site on the internet:"
+#: ./doc/install-guide/bk-openstack-install-guide.xml:14(titleabbrev)
+msgid "OpenStack Installation Guide for <placeholder-1/><placeholder-2/><placeholder-3/><placeholder-4/>"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-networking-neutron.xml:274(para)
-msgid "From the <emphasis>network</emphasis> node, <placeholder-1/> the management interface on the <emphasis>controller</emphasis> node:"
+#: ./doc/install-guide/bk-openstack-install-guide.xml:27(orgname)
+msgid "OpenStack"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-networking-neutron.xml:289(para)
-msgid "From the <emphasis>network</emphasis> node, <placeholder-1/> the instance tunnels interface on the <emphasis>compute</emphasis> node:"
+#: ./doc/install-guide/bk-openstack-install-guide.xml:31(year)
+msgid "2012"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-networking-neutron.xml:333(para)
-msgid "From the <emphasis>compute</emphasis> node, <placeholder-1/> the instance tunnels interface on the <emphasis>network</emphasis> node:"
+#: ./doc/install-guide/bk-openstack-install-guide.xml:32(year)
+msgid "2013"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-prerequisites.xml:6(title) ./doc/install-guide/object-storage/section_object-storage-install.xml:28(title)
-msgid "Before you begin"
+#: ./doc/install-guide/bk-openstack-install-guide.xml:33(holder)
+msgid "OpenStack Foundation"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-prerequisites.xml:7(para)
-msgid "For a functional environment, OpenStack doesn't require a significant amount of resources. We recommend that your environment meets or exceeds the following minimum requirements which can support several minimal <glossterm>CirrOS</glossterm> instances:"
+#: ./doc/install-guide/bk-openstack-install-guide.xml:35(releaseinfo)
+msgid "icehouse"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-prerequisites.xml:13(para)
-msgid "Controller Node: 1 processor, 2 GB memory, and 5 GB storage"
+#: ./doc/install-guide/bk-openstack-install-guide.xml:36(productname)
+msgid "OpenStack Installation Guide"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-prerequisites.xml:17(para)
-msgid "Network Node: 1 processor, 512 MB memory, and 5 GB storage"
+#: ./doc/install-guide/bk-openstack-install-guide.xml:40(remark)
+msgid "Copyright details are filled in by the template."
 msgstr ""
 
-#: ./doc/install-guide/section_basics-prerequisites.xml:21(para)
-msgid "Compute Node: 1 processor, 2 GB memory, and 10 GB storage"
+#: ./doc/install-guide/bk-openstack-install-guide.xml:45(para)
+msgid "The OpenStack® system consists of several key projects that you install separately but that work together depending on your cloud needs. These projects include Compute, Identity Service, Networking, Image Service, Block Storage, Object Storage, Telemetry, Orchestration, and Database. You can install any of these projects separately and configure them stand-alone or as connected entities. <phrase os=\"debian\">This guide walks through an installation by using packages available through Debian 7.0 (code name: Wheezy).</phrase><phrase os=\"ubuntu\">This guide walks through an installation by using packages available through Ubuntu 12.04 (LTS) or 14.04 (LTS).</phrase><phrase os=\"rhel;centos;fedora\">This guide shows you how to install OpenStack by using packages available through Fedora 20 as well as on Red Hat Enterprise Linux and its derivatives through the EPEL repository.</phrase><phrase os=\"opensuse\">This guide shows you how to install OpenStack by using packages on openSUSE through the Open Build Service Cloud repository.</phrase> Explanations of configuration options and sample configuration files are included."
 msgstr ""
 
-#: ./doc/install-guide/section_basics-prerequisites.xml:25(para)
-msgid "To minimize clutter and provide more resources for OpenStack, we recommend a minimal installation of your Linux distribution. Also, we strongly recommend that you install a 64-bit version of your distribution on at least the compute node. If you install a 32-bit version of your distribution on the compute node, attempting to start an instance using a 64-bit image will fail."
+#: ./doc/install-guide/bk-openstack-install-guide.xml:73(date)
+msgid "2014-04-16"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-prerequisites.xml:32(para)
-msgid "A single disk partition on each node works for most basic installations. However, you should consider <glossterm>Logical Volume Manager (LVM)</glossterm> for installations with optional services such as Block Storage."
+#: ./doc/install-guide/bk-openstack-install-guide.xml:77(para)
+msgid "Update for Icehouse, rework Networking setup to use ML2 as plugin, add new chapter for Database Service setup, improved basic configuration."
 msgstr ""
 
-#: ./doc/install-guide/section_basics-prerequisites.xml:37(para)
-msgid "Many users build their test environments on <glossterm baseform=\"virtual machine (VM)\">virtual machines (VMs)</glossterm>. The primary benefits of VMs include the following:"
+#: ./doc/install-guide/bk-openstack-install-guide.xml:86(date)
+msgid "2013-10-25"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-prerequisites.xml:43(para)
-msgid "One physical server can support multiple nodes, each with almost any number of network interfaces."
+#: ./doc/install-guide/bk-openstack-install-guide.xml:90(para)
+msgid "Added initial Debian support."
 msgstr ""
 
-#: ./doc/install-guide/section_basics-prerequisites.xml:47(para)
-msgid "Ability to take periodic \"snap shots\" throughout the installation process and \"roll back\" to a working configuration in the event of a problem."
+#: ./doc/install-guide/bk-openstack-install-guide.xml:96(date)
+msgid "2013-10-17"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-prerequisites.xml:52(para)
-msgid "However, VMs will reduce performance of your instances, particularly if your hypervisor and/or processor lacks support for hardware acceleration of nested VMs."
+#: ./doc/install-guide/bk-openstack-install-guide.xml:100(para)
+msgid "Havana release."
 msgstr ""
 
-#: ./doc/install-guide/section_basics-prerequisites.xml:56(para)
-msgid "If you choose to install on VMs, make sure your hypervisor permits <glossterm>promiscuous mode</glossterm> on the <glossterm>external network</glossterm>."
+#: ./doc/install-guide/bk-openstack-install-guide.xml:106(date)
+msgid "2013-10-16"
 msgstr ""
 
-#: ./doc/install-guide/section_basics-prerequisites.xml:60(para)
-msgid "For more information about system requirements, see the <link href=\"http://docs.openstack.org/ops/\">OpenStack Operations Guide</link>."
+#: ./doc/install-guide/bk-openstack-install-guide.xml:110(para)
+msgid "Add support for SUSE Linux Enterprise."
 msgstr ""
 
-#: ./doc/install-guide/ch_trove.xml:6(title)
-msgid "Add the Database service"
+#: ./doc/install-guide/bk-openstack-install-guide.xml:117(date)
+msgid "2013-10-08"
 msgstr ""
 
-#: ./doc/install-guide/ch_trove.xml:7(para)
-msgid "Use the <glossterm baseform=\"Database Service\">Database module</glossterm> to create cloud database resources. The integrated project name is <glossterm>trove</glossterm>."
+#: ./doc/install-guide/bk-openstack-install-guide.xml:121(para)
+msgid "Complete reorganization for Havana."
 msgstr ""
 
-#: ./doc/install-guide/ch_trove.xml:10(para)
-msgid "This chapter is a work in progress. It may contain incorrect information, and will be updated frequently."
+#: ./doc/install-guide/bk-openstack-install-guide.xml:128(date)
+msgid "2013-09-09"
 msgstr ""
 
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml:6(title) ./doc/install-guide/section_neutron-ml2-network-node.xml:6(title)
-msgid "Configure network node"
+#: ./doc/install-guide/bk-openstack-install-guide.xml:132(para)
+msgid "Build also for openSUSE."
+msgstr ""
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml:138(date)
+msgid "2013-08-01"
+msgstr ""
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml:142(para)
+msgid "Fixes to Object Storage verification steps. Fix bug <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/1207347\">1207347</link>."
+msgstr ""
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml:151(date)
+msgid "2013-07-25"
+msgstr ""
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml:155(para)
+msgid "Adds creation of cinder user and addition to the service tenant. Fix bug <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/1205057\">1205057</link>."
+msgstr ""
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml:165(date)
+msgid "2013-05-08"
+msgstr ""
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml:169(para)
+msgid "Updated the book title for consistency."
+msgstr ""
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml:176(date)
+msgid "2013-05-02"
+msgstr ""
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml:180(para)
+msgid "Updated cover and fixed small errors in appendix."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-queue.xml:6(title)
+msgid "Messaging server"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-queue.xml:7(para)
+msgid "OpenStack uses a <glossterm>message broker</glossterm> to coordinate operations and status information among services. The message broker service typically runs on the controller node. OpenStack supports several message brokers including <application>RabbitMQ</application>, <application>Qpid</application>, and <application>ZeroMQ</application>. However, most distributions that package OpenStack support a particular message broker. This guide covers the message broker supported by each distribution. If you prefer to implement a different message broker, consult the documentation associated with it."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-queue.xml:18(link)
+msgid "RabbitMQ"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-queue.xml:21(link)
+msgid "Qpid"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-queue.xml:24(link)
+msgid "ZeroMQ"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-queue.xml:28(title)
+msgid "To install the message broker service"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-queue.xml:30(para)
+msgid "Ubuntu and Debian use <application>RabbitMQ</application>."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-queue.xml:34(para)
+msgid "Red Hat Enterprise Linux (RHEL), CentOS, Scientific Linux, and Fedora use <application>Qpid</application>."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-queue.xml:40(para)
+msgid "SUSE Linux Enterprise Server (SLES) and openSUSE use <application>RabbitMQ</application>."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-queue.xml:46(title)
+msgid "To configure the message broker service"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-queue.xml:48(para)
+msgid "To simplify installation of your test environment, we recommend that you disable authentication."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-queue.xml:50(para)
+msgid "Edit the <filename>/etc/qpidd.conf</filename> file and change the following key:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-queue.xml:54(para)
+msgid "For production environments, you should enable authentication. For more information on securing the message broker, see the <link href=\"http://qpid.apache.org/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/chap-Messaging_User_Guide-Security.html\">documentation</link>."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-queue.xml:59(para)
+msgid "If you decide to enable authentication for your test environment, you must configure the <literal>qpid_username</literal> and <literal>qpid_password</literal> keys in the configuration file of each OpenStack service that uses the message broker."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-queue.xml:66(para)
+msgid "Start the message broker service:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-queue.xml:70(para)
+msgid "The message broker creates a default account that uses <literal>guest</literal> for the username and password. To simplify installation of your test environment, we recommend that you use this account, but change the password for it."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-queue.xml:75(para)
+msgid "Replace <replaceable>RABBIT_PASS</replaceable> with a suitable password."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-queue.xml:78(para)
+msgid "You must configure the <literal>rabbit_password</literal> key in the configuration file for each OpenStack service that uses the message broker."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-queue.xml:82(para)
+msgid "For production environments, you should create a unique account with suitable password. For more information on securing the message broker, see the <link href=\"https://www.rabbitmq.com/man/rabbitmqctl.1.man.html\">documentation</link>."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-queue.xml:87(para)
+msgid "If you decide to create a unique account with suitable password for your test environment, you must configure the <literal>rabbit_userid</literal> and <literal>rabbit_password</literal> keys in the configuration file of each OpenStack service that uses the message broker."
+msgstr ""
+
+#: ./doc/install-guide/section_basics-queue.xml:98(para)
+msgid "Start the message broker service and configure it to start when the system boots:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-queue.xml:104(para)
+msgid "Configure the message broker service to start when the system boots:"
+msgstr ""
+
+#: ./doc/install-guide/section_basics-queue.xml:109(para)
+msgid "Congratulations, now you are ready to install OpenStack services!"
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-services.xml:4(title)
+msgid "Define services and API endpoints"
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-services.xml:5(para)
+msgid "So that the Identity Service can track which OpenStack services are installed and where they are located on the network, you must register each service in your OpenStack installation. To register a service, run these commands:"
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-services.xml:11(para)
+msgid "<placeholder-1/>. Describes the service."
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-services.xml:15(para)
+msgid "<placeholder-1/>. Associates <glossterm baseform=\"API endpoint\">API endpoints</glossterm> with the service."
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-services.xml:20(para)
+msgid "You must also register the Identity Service itself. Use the <code>OS_SERVICE_TOKEN</code> environment variable, as set previously, for authentication."
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-services.xml:25(para)
+msgid "Create a service entry for the Identity Service:"
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-services.xml:36(para) ./doc/install-guide/object-storage/section_object-storage-install.xml:89(para)
+msgid "The service ID is randomly generated and is different from the one shown here."
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-services.xml:40(para)
+msgid "Specify an API endpoint for the Identity Service by using the returned service ID. When you specify an endpoint, you provide URLs for the public API, internal API, and admin API. In this guide, the <literal>controller</literal> host name is used. Note that the Identity Service uses a different port for the admin API."
+msgstr ""
+
+#: ./doc/install-guide/section_keystone-services.xml:63(para)
+msgid "You will need to create an additional endpoint for each service added to your OpenStack environment. The sections of this guide associated with the installation of each service include the endpoint creation step specific to the service."
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-api-endpoints.xml:29(None)
+msgid "@@image: 'figures/debconf-screenshots/api-endpoint_1_register_endpoint.png'; md5=d534be231be4f725820a1050fbf44231"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-api-endpoints.xml:40(None)
+msgid "@@image: 'figures/debconf-screenshots/api-endpoint_2_keystone_server_ip.png'; md5=d2c5a5b82dd433fcf9cde6f5ac34c30e"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-api-endpoints.xml:54(None)
+msgid "@@image: 'figures/debconf-screenshots/api-endpoint_3_keystone_authtoken.png'; md5=1f3b05ebe671f64d672ac70d246e4f39"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-api-endpoints.xml:69(None)
+msgid "@@image: 'figures/debconf-screenshots/api-endpoint_4_service_endpoint_ip_address.png'; md5=6853f0ae2ef8d5fddb22c466d465de15"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-api-endpoints.xml:81(None)
+msgid "@@image: 'figures/debconf-screenshots/api-endpoint_5_region_name.png'; md5=a6bce0acf5a1cb85f161290f0cf30733"
+msgstr ""
+
+#: ./doc/install-guide/section_debconf-api-endpoints.xml:6(title)
+msgid "Register API endpoints"
+msgstr ""
+
+#: ./doc/install-guide/section_debconf-api-endpoints.xml:7(para)
+msgid "All Debian packages for API services, except the <package>heat-api</package> package, register the service in the Identity Service catalog. This feature is helpful because API endpoints are difficult to remember."
+msgstr ""
+
+#: ./doc/install-guide/section_debconf-api-endpoints.xml:12(para)
+msgid "The <package>heat-common</package> package and not the <package>heat-api</package> package configures the Orchestration service."
+msgstr ""
+
+#: ./doc/install-guide/section_debconf-api-endpoints.xml:16(para)
+msgid "When you install a package for an API service, you are prompted to register that service. However, after you install or upgrade the package for an API service, Debian immediately removes your response to this prompt from the <package>debconf</package> database. Consequently, you are prompted to re-register the service with the Identity Service. If you already registered the API service, respond <literal>no</literal> when you upgrade."
+msgstr ""
+
+#: ./doc/install-guide/section_debconf-api-endpoints.xml:33(para)
+msgid "This screen registers packages in the Identity Service catalog:"
+msgstr ""
+
+#: ./doc/install-guide/section_debconf-api-endpoints.xml:44(para)
+msgid "You are prompted for the Identity Service <literal>admin_token</literal> value. The Identity Service uses this value to register the API service. When you set up the <package>keystone</package> package, this value is configured automatically."
+msgstr ""
+
+#: ./doc/install-guide/section_debconf-api-endpoints.xml:58(para)
+msgid "This screen configures the IP addresses for the service. The configuration script automatically detects the IP address used by the interface that is connected to the default route (<code>/sbin/route</code> and <code>/sbin/ip</code>)."
+msgstr ""
+
+#: ./doc/install-guide/section_debconf-api-endpoints.xml:62(para)
+msgid "Unless you have a unique set up for your network, press <keycap>ENTER</keycap>."
+msgstr ""
+
+#: ./doc/install-guide/section_debconf-api-endpoints.xml:73(para)
+msgid "This screen configures the region name for the service. For example, <code>us-east-coast</code> or <code>europe-paris</code>."
 msgstr ""
 
 #: ./doc/install-guide/section_neutron-ovs-network-node.xml:8(para)
@@ -3091,683 +4658,6 @@ msgstr ""
 msgid "Add this statement to the <literal>[DEFAULT]</literal> section:"
 msgstr ""
 
-#: ./doc/install-guide/section_nova-networking-controller-node.xml:6(para)
-msgid "Legacy networking primarily involves compute nodes. However, you must configure the controller node to use it."
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-concepts.xml:7(title)
-msgid "debconf concepts"
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-concepts.xml:8(para)
-msgid "This chapter explains how to use the Debian <systemitem class=\"library\">debconf</systemitem> and <systemitem class=\"library\">dbconfig-common</systemitem> packages to configure OpenStack services. These packages enable users to perform configuration tasks. When users install OpenStack packages, <package>debconf</package> prompts the user for responses, which seed the contents of configuration files associated with that package. After package installation, users can update the configuration of a package by using the <placeholder-1/> program."
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-concepts.xml:18(para)
-msgid "If you are familiar with these packages and pre-seeding, you can proceed to <xref linkend=\"ch_keystone\"/>."
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-concepts.xml:21(title)
-msgid "The Debian packages"
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-concepts.xml:22(para)
-msgid "The rules described here are from the <link href=\"http://www.debian.org/doc/debian-policy/\"><citetitle>Debian Policy Manual</citetitle></link>. If any rule described in this chapter is not respected, you have found a serious bug that must be fixed."
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-concepts.xml:27(para)
-msgid "When you install or upgrade a Debian package, all configuration file values are preserved. Using the <systemitem class=\"library\">debconf</systemitem> database as a registry is considered a bug in Debian. If you edit something in any OpenStack configuration file, the <systemitem class=\"library\">debconf</systemitem> package reads that value when it prepares to prompt the user. For example, to change the log in name for the RabbitMQ messaging queue for a service, you can edit its value in the corresponding configuration file."
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-concepts.xml:36(para)
-msgid "To opt out of using the <systemitem class=\"library\">debconf</systemitem> package, run the <placeholder-1/> command and select non-interactive mode:"
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-concepts.xml:41(para)
-msgid "Then, <systemitem class=\"library\">debconf</systemitem> does not prompt you."
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-concepts.xml:43(para)
-msgid "Another way to disable the <systemitem class=\"library\">debconf</systemitem> package is to prefix the <placeholder-1/> command with <literal>DEBIAN_FRONTEND=noninteractive</literal>, as follows:"
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-concepts.xml:49(para)
-msgid "If you configure a package with <systemitem class=\"library\">debconf</systemitem> incorrectly, you can re-configure it, as follows:"
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-concepts.xml:52(replaceable)
-msgid "PACKAGE-NAME"
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-concepts.xml:53(para)
-msgid "This calls the post-installation script for the <replaceable>PACKAGE-NAME</replaceable> package after the user responds to all prompts. If you cannot install a Debian package in a non-interactive way, you have found a release-critical bug in Debian. Report it to the Debian bug tracking system."
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-concepts.xml:58(para)
-msgid "Generally, the <systemitem class=\"library\">-common</systemitem> packages install the configuration files. For example, the <literal>glance-common</literal> package installs the <filename>glance-api.conf</filename> and <filename>glance-registry.conf</filename> files. So, for the Image Service, you must re-configure the <literal>glance-common</literal> package. The same applies for <literal>cinder-common</literal>, <literal>nova-common</literal>, and <literal>heat-common</literal> packages."
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-concepts.xml:68(para)
-msgid "In <systemitem class=\"library\">debconf</systemitem>, the higher the priority for a screen, the greater the chance that the user sees that screen. If a <systemitem class=\"library\">debconf</systemitem> screen has <literal>medium</literal> priority and you configure the Debian system to show only <literal>critical</literal> prompts, which is the default in Debian, the user does not see that <systemitem class=\"library\">debconf</systemitem> screen. Instead, the default for the related package is used. In the Debian OpenStack packages, a number of <systemitem class=\"library\">debconf</systemitem> screens are set with <literal>medium</literal> priority. Consequently, if you want to respond to all <systemitem class=\"library\">debconf</systemitem> screens from the Debian OpenStack packages, you must run the following command and select the <literal>medium</literal> priority before you install any packages:"
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-concepts.xml:87(para)
-msgid "The packages do not require pre-depends. If <systemitem class=\"library\">dbconfig-common</systemitem> is already installed on the system, the user sees all prompts. However, you cannot define the order in which the <systemitem class=\"library\">debconf</systemitem> screens appear. The user must make sense of it even if the prompts appear in an illogical order."
-msgstr ""
-
-#: ./doc/install-guide/section_ceilometer-swift.xml:6(title)
-msgid "Configure the Object Storage service for Telemetry"
-msgstr ""
-
-#: ./doc/install-guide/section_ceilometer-swift.xml:9(para)
-msgid "To retrieve object store statistics, the Telemetry service needs access to Object Storage with the <literal>ResellerAdmin</literal> role. Give this role to your <literal>os_username</literal> user for the <literal>os_tenant_name</literal> tenant:"
-msgstr ""
-
-#: ./doc/install-guide/section_ceilometer-swift.xml:23(replaceable)
-msgid "462fa46c13fd4798a95a3bfbe27b5e54"
-msgstr ""
-
-#: ./doc/install-guide/section_ceilometer-swift.xml:26(para)
-msgid "You must also add the Telemetry middleware to Object Storage to handle incoming and outgoing traffic. Add these lines to the <filename>/etc/swift/proxy-server.conf</filename> file:"
-msgstr ""
-
-#: ./doc/install-guide/section_ceilometer-swift.xml:35(para)
-msgid "Add <literal>ceilometer</literal> to the <literal>pipeline</literal> parameter of that same file:"
-msgstr ""
-
-#: ./doc/install-guide/section_ceilometer-swift.xml:41(para) ./doc/install-guide/section_heat-install.xml:180(para) ./doc/install-guide/section_ceilometer-nova.xml:137(para)
-msgid "Restart the service with its new settings:"
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-preseeding.xml:6(title)
-msgid "Pre-seed debconf prompts"
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-preseeding.xml:7(para)
-msgid "You can pre-seed all <systemitem class=\"library\">debconf</systemitem> prompts. To pre-seed means to store responses in the <package>debconf</package> database so that <package>debconf</package> does not prompt the user for responses. Pre-seeding enables a hands-free installation for users. The package maintainer creates scripts that automatically configure the services."
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-preseeding.xml:14(para)
-msgid "The following example shows how to pre-seed an automated MySQL Server installation:"
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-preseeding.xml:16(replaceable) ./doc/install-guide/section_debconf-preseeding.xml:17(replaceable) ./doc/install-guide/section_debconf-preseeding.xml:19(replaceable)
-msgid "MYSQL_PASSWORD"
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-preseeding.xml:23(para)
-msgid "The <code>seen true</code> option tells <package>debconf</package> that a specified screen was already seen by the user so do not show it again. This option is useful for upgrades."
-msgstr ""
-
-#: ./doc/install-guide/ch_basics.xml:5(title)
-msgid "Basic environment configuration"
-msgstr ""
-
-#: ./doc/install-guide/ch_basics.xml:6(para)
-msgid "This chapter explains how to configure each node in the <link linkend=\"architecture_example-architectures\">example architectures</link> including the <link linkend=\"example-architecture-with-legacy-networking\"> two-node architecture with legacy networking</link> and <link linkend=\"example-architecture-with-neutron-networking\">three-node architecture with OpenStack Networking (neutron)</link>."
-msgstr ""
-
-#: ./doc/install-guide/ch_basics.xml:13(para)
-msgid "Although most environments include OpenStack Identity, Image Service, Compute, at least one networking service, and the dashboard, OpenStack Object Storage can operate independently of most other services. If your use case only involves Object Storage, you can skip to <xref linkend=\"object-storage-system-requirements\"/>. However, the dashboard will not work without at least OpenStack Image Service and Compute."
-msgstr ""
-
-#: ./doc/install-guide/ch_basics.xml:22(para)
-msgid "You must use an account with administrative privileges to configure each node. Either run the commands as the <literal>root</literal> user or configure the <literal>sudo</literal> utility."
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:6(title)
-msgid "Configure a Block Storage service node"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:7(para)
-msgid "After you configure the services on the controller node, configure a second system to be a Block Storage service node. This node contains the disk that serves volumes."
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:10(para) ./doc/install-guide/section_cinder-controller.xml:16(para)
-msgid "You can configure OpenStack to use various storage systems. This example uses LVM."
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:14(para)
-msgid "Use the instructions in <xref linkend=\"ch_basics\"/> to configure the system. Note the following differences from the installation instructions for the controller node:"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:19(para)
-msgid "Set the host name to <literal>block1</literal> and use <literal>10.0.0.41</literal> as IP address on the management network interface. Ensure that the IP addresses and host names for both controller node and Block Storage service node are listed in the <filename>/etc/hosts</filename> file on each system."
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:27(para)
-msgid "Follow the instructions in <xref linkend=\"basics-ntp\"/> to synchronize from the controller node."
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:33(para)
-msgid "Install the required LVM packages, if they are not already installed:"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:38(para)
-msgid "Create the LVM physical and logical volumes. This guide assumes a second disk <literal>/dev/sdb</literal> that is used for this purpose:"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:45(para)
-msgid "Add a filter entry to the <literal>devices</literal> section in the <filename>/etc/lvm/lvm.conf</filename> file to keep LVM from scanning devices used by virtual machines:"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:55(para)
-msgid "You must add required physical volumes for LVM on the Block Storage host. Run the <placeholder-1/> command to get a list or required volumes."
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:59(para)
-msgid "Each item in the filter array starts with either an <literal>a</literal> for accept, or an <literal>r</literal> for reject. The physical volumes that are required on the Block Storage host have names that begin with <literal>a</literal>. The array must end with \"<literal>r/.*/</literal>\" to reject any device not listed."
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:66(para)
-msgid "In this example, <literal>/dev/sda1</literal> is the volume where the volumes for the operating system for the node reside, while <literal>/dev/sdb</literal> is the volume reserved for <literal>cinder-volumes</literal>."
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:72(para)
-msgid "After you configure the operating system, install the appropriate packages for the Block Storage service:"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:79(para)
-msgid "Respond to the <systemitem class=\"library\">debconf</systemitem> prompts about the <link linkend=\"debconf-dbconfig-common\">database management</link>, <link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> settings</link>, and <link linkend=\"debconf-rabbitqm\">RabbitMQ credentials</link>. Make sure to enter the same details as you did for your Block Storage service controller node."
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:87(para)
-msgid "Another screen prompts you for the <systemitem class=\"library\">volume-group</systemitem> to use. The Debian package configuration script detects every active volume group and tries to use the first one it sees, provided that the <systemitem class=\"library\">lvm2</systemitem> package was installed before Block Storage. This should be the case if you configured the volume group first, as this guide recommends."
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:94(para)
-msgid "If you have only one active volume group on your Block Storage service node, you do not need to manually enter its name when you install the <systemitem class=\"service\">cinder-volume</systemitem> package because it is detected automatically. If no <systemitem class=\"library\">volume-group</systemitem> is available when you install <systemitem class=\"service\">cinder-common</systemitem>, you must use <placeholder-1/> to manually configure or re-configure <systemitem class=\"service\">cinder-common</systemitem>."
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:106(para)
-msgid "Copy the <filename>/etc/cinder/cinder.conf</filename> configuration file from the controller, or perform the following steps to set the keystone credentials:"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:125(replaceable) ./doc/install-guide/section_cinder-node.xml:137(replaceable) ./doc/install-guide/section_cinder-controller.xml:74(replaceable) ./doc/install-guide/section_cinder-controller.xml:95(replaceable) ./doc/install-guide/section_cinder-controller.xml:107(replaceable)
-msgid "CINDER_PASS"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:126(para) ./doc/install-guide/section_cinder-controller.xml:96(para)
-msgid "Edit the <filename>/etc/cinder/cinder.conf</filename> configuration file and add this section for keystone credentials:"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:140(para) ./doc/install-guide/section_cinder-controller.xml:110(para) ./doc/install-guide/section_cinder-controller.xml:134(para)
-msgid "Configure Block Storage to use the RabbitMQ message broker."
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:142(para)
-msgid "In the <literal>[DEFAULT]</literal> configuration section of the <filename>/etc/cinder/cinder.conf</filename> file, set these configuration keys and replace <replaceable>RABBIT_PASS</replaceable> with the password you chose for RabbitMQ:"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:156(para) ./doc/install-guide/section_cinder-controller.xml:126(para)
-msgid "Configure Block Storage to use the Qpid message broker:"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:164(para)
-msgid "Configure Block Storage to use the RabbitMQ message broker. Replace <replaceable>RABBIT_PASS</replaceable> with the password you chose for RabbitMQ:"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:177(para)
-msgid "Configure Block Storage to use your MySQL database. Edit the <filename>/etc/cinder/cinder.conf</filename> file and add the following key to the <literal>[database]</literal> section. Replace <replaceable>CINDER_DBPASS</replaceable> with the password you chose for the Block Storage database:"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:183(replaceable) ./doc/install-guide/section_cinder-node.xml:186(replaceable) ./doc/install-guide/section_cinder-controller.xml:44(replaceable) ./doc/install-guide/section_cinder-controller.xml:47(replaceable) ./doc/install-guide/section_cinder-controller.xml:59(replaceable) ./doc/install-guide/section_cinder-controller.xml:61(replaceable)
-msgid "CINDER_DBPASS"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:188(para) ./doc/install-guide/section_cinder-controller.xml:48(para)
-msgid "In some distributions, the <filename>/etc/cinder/cinder.conf</filename> file does not include the <literal>[database]</literal> section header. You must add this section header to the end of the file before you proceed."
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:196(para)
-msgid "Configure Block Storage to use the Image Service. Block Storage needs access to images to create bootable volumes. Edit the <filename>/etc/cinder/cinder.conf</filename> file and update the <option>glance_host</option> option in the <literal>[DEFAULT]</literal> section:"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:208(para) ./doc/install-guide/section_cinder-controller.xml:168(para)
-msgid "Restart the Block Storage services with the new settings:"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:214(para)
-msgid "Configure the iSCSI target service to discover Block Storage volumes. Add the following line to the beginning of the <filename>/etc/tgt/targets.conf</filename> file, if it is not already present:"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-node.xml:221(para) ./doc/install-guide/section_cinder-controller.xml:174(para)
-msgid "Start and configure the Block Storage services to start when the system boots:"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-controller.xml:5(title)
-msgid "Configure a Block Storage service controller"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-controller.xml:7(para)
-msgid "This scenario configures OpenStack Block Storage services on the <glossterm baseform=\"controller node\">Controller node</glossterm> and assumes that a second node provides storage through the <systemitem class=\"service\">cinder-volume</systemitem> service."
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-controller.xml:12(para)
-msgid "For instructions on how to configure the second node, see <xref linkend=\"cinder-node\"/>."
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-controller.xml:20(para)
-msgid "Install the appropriate packages for the Block Storage service:"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-controller.xml:27(para)
-msgid "Respond to the prompts for database management, <literal>[keystone_authtoken]</literal> settings, RabbitMQ credentials and API endpoint registration."
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-controller.xml:31(para)
-msgid "Configure Block Storage to use your database."
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-controller.xml:32(para)
-msgid "Run the following command to set <literal>connection</literal> option in the <literal>[database]</literal> section, which is in the <filename>/etc/cinder/cinder.conf</filename> file, replace <replaceable>CINDER_DBPASS</replaceable> with the password for the Block Storage database that you will create in a later step:"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-controller.xml:38(para)
-msgid "In the <filename>/etc/cinder/cinder.conf</filename> file, set the <literal>connection</literal> option in the <literal>[database]</literal> section and replace <replaceable>CINDER_DBPASS</replaceable> with the password for the Block Storage database that you will create in a later step:"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-controller.xml:54(para)
-msgid "Use the password that you set to log in as root to create a <literal>cinder</literal> database:"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-controller.xml:64(para)
-msgid "Create the database tables for the Block Storage service:"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-controller.xml:69(para)
-msgid "Create a <literal>cinder</literal> user."
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-controller.xml:70(para)
-msgid "The Block Storage service uses this user to authenticate with the Identity service."
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-controller.xml:72(para)
-msgid "Use the <literal>service</literal> tenant and give the user the <literal>admin</literal> role:"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-controller.xml:74(replaceable)
-msgid "cinder@example.com"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-controller.xml:78(para)
-msgid "Edit the <filename>/etc/cinder/cinder.conf</filename> configuration file:"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-controller.xml:112(para)
-msgid "In the <literal>[DEFAULT]</literal> section in the <filename>/etc/cinder/cinder.conf</filename> file, set these configuration keys and replace <replaceable>RABBIT_PASS</replaceable> with the password you chose for RabbitMQ:"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-controller.xml:136(para)
-msgid "Replace <replaceable>RABBIT_PASS</replaceable> with the password you chose for RabbitMQ:"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-controller.xml:148(para)
-msgid "Register the Block Storage service with the Identity service so that other OpenStack services can locate it:"
-msgstr ""
-
-#: ./doc/install-guide/section_cinder-controller.xml:158(para)
-msgid "Register a service and endpoint for version 2 of the Block Storage service API:"
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:7(title)
-msgid "OpenStack Installation Guide for <phrase os=\"rhel;centos;fedora\">Red Hat Enterprise Linux, CentOS, and Fedora</phrase><phrase os=\"ubuntu\">Ubuntu 12.04/14.04 (LTS)</phrase><phrase os=\"debian\">Debian 7.0 (Wheezy)</phrase><phrase os=\"opensuse\">openSUSE and SUSE Linux Enterprise Server</phrase>"
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:15(phrase)
-msgid "Red Hat Enterprise Linux, CentOS, and Fedora"
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:16(phrase)
-msgid "Ubuntu 12.04/14.04 (LTS)"
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:17(phrase)
-msgid "openSUSE and SUSE Linux Enterprise Server"
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:18(phrase)
-msgid "Debian 7.0 (Wheezy)"
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:14(titleabbrev)
-msgid "OpenStack Installation Guide for <placeholder-1/><placeholder-2/><placeholder-3/><placeholder-4/>"
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:27(orgname)
-msgid "OpenStack"
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:31(year)
-msgid "2012"
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:32(year)
-msgid "2013"
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:33(holder)
-msgid "OpenStack Foundation"
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:35(releaseinfo)
-msgid "icehouse"
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:36(productname)
-msgid "OpenStack Installation Guide"
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:40(remark)
-msgid "Copyright details are filled in by the template."
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:45(para)
-msgid "The OpenStack® system consists of several key projects that you install separately but that work together depending on your cloud needs. These projects include Compute, Identity Service, Networking, Image Service, Block Storage, Object Storage, Telemetry, Orchestration, and Database. You can install any of these projects separately and configure them stand-alone or as connected entities. <phrase os=\"debian\">This guide walks through an installation by using packages available through Debian 7.0 (code name: Wheezy).</phrase><phrase os=\"ubuntu\">This guide walks through an installation by using packages available through Ubuntu 12.04 (LTS) or 14.04 (LTS).</phrase><phrase os=\"rhel;centos;fedora\">This guide shows you how to install OpenStack by using packages available through Fedora 20 as well as on Red Hat Enterprise Linux and its derivatives through the EPEL repository.</phrase><phrase os=\"opensuse\">This guide shows you how to install OpenStack by using packages on openSUSE through the Open Build Service Cloud repository.</phrase> Explanations of configuration options and sample configuration files are included."
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:73(date)
-msgid "2014-04-16"
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:77(para)
-msgid "Update for Icehouse, rework Networking setup to use ML2 as plugin, add new chapter for Database Service setup, improved basic configuration."
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:86(date)
-msgid "2013-10-25"
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:90(para)
-msgid "Added initial Debian support."
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:96(date)
-msgid "2013-10-17"
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:100(para)
-msgid "Havana release."
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:106(date)
-msgid "2013-10-16"
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:110(para)
-msgid "Add support for SUSE Linux Enterprise."
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:117(date)
-msgid "2013-10-08"
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:121(para)
-msgid "Complete reorganization for Havana."
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:128(date)
-msgid "2013-09-09"
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:132(para)
-msgid "Build also for openSUSE."
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:138(date)
-msgid "2013-08-01"
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:142(para)
-msgid "Fixes to Object Storage verification steps. Fix bug <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/1207347\">1207347</link>."
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:151(date)
-msgid "2013-07-25"
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:155(para)
-msgid "Adds creation of cinder user and addition to the service tenant. Fix bug <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/1205057\">1205057</link>."
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:165(date)
-msgid "2013-05-08"
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:169(para)
-msgid "Updated the book title for consistency."
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:176(date)
-msgid "2013-05-02"
-msgstr ""
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml:180(para)
-msgid "Updated cover and fixed small errors in appendix."
-msgstr ""
-
-#: ./doc/install-guide/ch_debconf.xml:6(title)
-msgid "Configure OpenStack with debconf"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:9(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:9(para)
-msgid "Before you configure OpenStack Networking, you must enable certain kernel networking functions."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:12(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:12(para)
-msgid "Edit <filename>/etc/sysctl.conf</filename> to contain the following:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:19(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:18(para)
-msgid "Implement the changes:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:33(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:30(para)
-msgid "Ubuntu installations using Linux kernel version 3.11 or newer do not require the <emphasis>openvswitch-datapath-dkms</emphasis> package."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:43(title) ./doc/install-guide/section_neutron-ml2-compute-node.xml:40(title)
-msgid "To configure the Networking common components"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:44(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:41(para)
-msgid "The Networking common component configuration includes the authentication mechanism, message broker, and plug-in."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:188(title)
-msgid "To configure the Layer-3 (L3) agent"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:189(para)
-msgid "The <glossterm>Layer-3 (L3) agent</glossterm> provides routing services for instance virtual networks."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:198(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:213(para)
-msgid "We recommend adding <literal>verbose = True</literal> to the <literal>[DEFAULT]</literal> section in <filename>/etc/neutron/l3_agent.ini</filename> to assist with troubleshooting."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:205(para)
-msgid "Edit the <filename>/etc/neutron/l3_agent.ini</filename> file and add the following keys to the <literal>[DEFAULT]</literal> section:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:221(title)
-msgid "To configure the DHCP agent"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:222(para)
-msgid "The <glossterm>DHCP agent</glossterm> provides <glossterm>DHCP</glossterm> services for instance virtual networks."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:234(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:250(para)
-msgid "We recommend adding <literal>verbose = True</literal> to the <literal>[DEFAULT]</literal> section in <filename>/etc/neutron/dhcp_agent.ini</filename> to assist with troubleshooting."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:241(para)
-msgid "Edit the <filename>/etc/neutron/dhcp_agent.ini</filename> file and add the following keys to the <literal>[DEFAULT]</literal> section:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:258(title)
-msgid "To configure the metadata agent"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:259(para)
-msgid "The <glossterm>metadata agent</glossterm> provides configuration information such as credentials for remote access to instances."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:263(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:293(para)
-msgid "Replace <replaceable>NEUTRON_PASS</replaceable> with the password you chose for the <literal>neutron</literal> user in the Identity service. Replace <replaceable>METADATA_SECRET</replaceable> with a suitable secret for the metadata proxy."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:281(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:306(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:329(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:341(replaceable)
-msgid "METADATA_SECRET"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:283(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:308(para)
-msgid "We recommend adding <literal>verbose = True</literal> to the <literal>[DEFAULT]</literal> section in <filename>/etc/neutron/metadata_agent.ini</filename> to assist with troubleshooting."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:290(para)
-msgid "Edit the <filename>/etc/neutron/metadata_agent.ini</filename> file and add the following keys to the <literal>[DEFAULT]</literal> section:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:316(para)
-msgid "Perform the next two steps on the <emphasis>controller</emphasis> node."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:321(para)
-msgid "On the <emphasis>controller</emphasis> node, configure Compute to use the metadata service:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:323(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:335(para)
-msgid "Replace <replaceable>METADATA_SECRET</replaceable> with the secret you chose for the metadata proxy."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:332(para)
-msgid "On the <emphasis>controller</emphasis> node, edit the <filename>/etc/nova/nova.conf</filename> file and add the following keys to the <literal>[DEFAULT]</literal> section:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:344(para)
-msgid "On the <emphasis>controller</emphasis> node, restart the Compute <glossterm>API</glossterm> service:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:352(para)
-msgid "The ML2 plug-in uses the Open vSwitch (OVS) mechanism (agent) to build virtual networking framework for instances."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:356(para)
-msgid "Replace <replaceable>INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS</replaceable> with the IP address of the instance tunnels network interface on your network node. This guide uses <literal>10.0.1.21</literal> for the IP address of the instance tunnels network interface on the network node."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:372(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:406(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:206(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:240(replaceable)
-msgid "INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:383(para)
-msgid "Edit the <filename>/etc/neutron/plugins/ml2/ml2_conf.ini</filename> file."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:393(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:227(para)
-msgid "Add the following keys to the <literal>[ml2_type_gre]</literal> section:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:398(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:232(para)
-msgid "Add the <literal>[ovs]</literal> section and the following keys to it:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:400(para)
-msgid "Replace <replaceable>INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS</replaceable> with the IP address of the instance tunnels network interface on your network node."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:418(title) ./doc/install-guide/section_neutron-ml2-compute-node.xml:252(title)
-msgid "To configure the Open vSwitch (OVS) service"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:419(para)
-msgid "The OVS service provides the underlying virtual networking framework for instances. The integration bridge <literal>br-int</literal> handles internal instance network traffic within OVS. The external bridge <literal>br-ex</literal> handles external instance network traffic within OVS. The external bridge requires a port on the physical external network interface to provide instances with external network access. In essence, this port bridges the virtual and physical external networks in your environment."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:428(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:434(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:257(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:263(para)
-msgid "Start the OVS service and configure it to start when the system boots:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:440(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:444(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:269(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:273(para)
-msgid "Restart the OVS service:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:448(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:277(para)
-msgid "Add the integration bridge:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:452(para)
-msgid "Add the external bridge:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:456(para)
-msgid "Add a port to the external bridge that connects to the physical external network interface:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:463(para)
-msgid "Depending on your network interface driver, you may need to disable <glossterm>Generic Receive Offload (GRO)</glossterm> to achieve suitable throughput between your instances and the external network."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:467(para)
-msgid "To temporarily disable GRO on the external network interface while testing your environment:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:474(title) ./doc/install-guide/section_neutron-ml2-compute-node.xml:347(title)
-msgid "To finalize the installation"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:476(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:349(para)
-msgid "The Networking service initialization scripts expect a symbolic link <filename>/etc/neutron/plugin.ini</filename> pointing to the configuration file associated with your chosen plug-in. Using the ML2 plug-in, for example, the symbolic link must point to <filename>/etc/neutron/plugins/ml2/ml2_conf.ini</filename>. If this symbolic link does not exist, create it using the following commands:"
-msgstr ""
-
-#. https://bugzilla.redhat.com/show_bug.cgi?id=1087647
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:485(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:358(para)
-msgid "Due to a packaging bug, the Open vSwitch agent initialization script explicitly looks for the Open vSwitch plug-in configuration file rather than a symbolic link <filename>/etc/neutron/plugin.ini</filename> pointing to the ML2 plug-in configuration file. Run the following commands to resolve this issue:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:495(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:368(para)
-msgid "The Networking service initialization scripts expect the variable <literal>NEUTRON_PLUGIN_CONF</literal> in the <filename>/etc/sysconfig/neutron</filename> file to reference the configuration file associated with your chosen plug-in. Using ML2, for example, edit the <filename>/etc/sysconfig/neutron</filename> file and add the following:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:505(para)
-msgid "Start the Networking services and configure them to start when the system boots:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml:525(para)
-msgid "Restart the Networking services:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:186(para)
-msgid "The ML2 plug-in uses the Open vSwitch (OVS) mechanism (agent) to build the virtual networking framework for instances."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:190(para)
-msgid "Replace <replaceable>INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS</replaceable> with the IP address of the instance tunnels network interface on your compute node. This guide uses <literal>10.0.1.31</literal> for the IP address of the instance tunnels network interface on the first compute node."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:234(para)
-msgid "Replace <replaceable>INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS</replaceable> with the IP address of the instance tunnels network interface on your compute node."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:253(para)
-msgid "The OVS service provides the underlying virtual networking framework for instances. The integration bridge <literal>br-int</literal> handles internal instance network traffic within OVS."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:378(para) ./doc/install-guide/section_ceilometer-nova.xml:53(para) ./doc/install-guide/section_nova-compute.xml:208(para)
-msgid "Restart the Compute service:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:383(para)
-msgid "Start the Open vSwitch (OVS) agent and configure it to start when the system boots:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:391(para)
-msgid "Restart the Open vSwitch (OVS) agent:"
-msgstr ""
-
 #. When image changes, this message will be marked fuzzy or untranslated for you.
 #. It doesn't matter what you translate it to: it's not used at all.
 #: ./doc/install-guide/ch_overview.xml:35(None)
@@ -3854,962 +4744,76 @@ msgstr ""
 msgid "When you implement this architecture, skip <xref linkend=\"section_neutron-networking\"/> in <xref linkend=\"ch_networking\"/>. To use optional services, you might need to install additional nodes, as described in subsequent chapters."
 msgstr ""
 
-#: ./doc/install-guide/section_dashboard-install.xml:7(title)
-msgid "Install the dashboard"
+#: ./doc/install-guide/section_trove-verify.xml:5(title)
+msgid "Verify the Database service installation"
 msgstr ""
 
-#: ./doc/install-guide/section_dashboard-install.xml:8(para)
-msgid "Before you can install and configure the dashboard, meet the requirements in <xref linkend=\"dashboard-system-requirements\"/>."
+#: ./doc/install-guide/section_trove-verify.xml:6(para)
+msgid "To verify that the Database service is installed and configured correctly, try executing a Trove command:"
 msgstr ""
 
-#: ./doc/install-guide/section_dashboard-install.xml:12(para)
-msgid "When you install only Object Storage and the Identity Service, even if you install the dashboard, it does not pull up projects and is unusable."
+#: ./doc/install-guide/section_trove-verify.xml:10(para)
+msgid "Source the <filename>demo-openrc.sh</filename> file."
 msgstr ""
 
-#: ./doc/install-guide/section_dashboard-install.xml:16(para)
-msgid "For more information about how to deploy the dashboard, see <link href=\"http://docs.openstack.org/developer/horizon/topics/deployment.html\">deployment topics in the developer documentation</link>."
+#: ./doc/install-guide/section_trove-verify.xml:14(para)
+msgid "Retrieve the Trove instances list:"
 msgstr ""
 
-#: ./doc/install-guide/section_dashboard-install.xml:22(para)
-msgid "Install the dashboard on the node that can contact the Identity Service as root:"
+#: ./doc/install-guide/section_trove-verify.xml:16(para)
+msgid "You should see output similar to this:"
 msgstr ""
 
-#: ./doc/install-guide/section_dashboard-install.xml:28(title)
-msgid "Note for Ubuntu users"
+#: ./doc/install-guide/section_trove-verify.xml:23(para)
+msgid "Assuming you have created an image for the type of database you want, and have updated the datastore to use that image, you can now create a Trove instance (database). To do this, use the trove <placeholder-1/> command."
 msgstr ""
 
-#: ./doc/install-guide/section_dashboard-install.xml:30(para)
-msgid "Remove the <literal>openstack-dashboard-ubuntu-theme</literal> package. This theme prevents translations, several menus as well as the network map from rendering correctly: <placeholder-1/>"
+#: ./doc/install-guide/section_trove-verify.xml:30(para)
+msgid "This example shows you how to create a MySQL 5.5 database:"
 msgstr ""
 
-#: ./doc/install-guide/section_dashboard-install.xml:39(title)
-msgid "Note for Debian users"
+#: ./doc/install-guide/section_trove-verify.xml:32(replaceable)
+msgid "name"
 msgstr ""
 
-#: ./doc/install-guide/section_dashboard-install.xml:40(para)
-msgid "To install the Apache package:"
+#: ./doc/install-guide/section_trove-verify.xml:32(replaceable)
+msgid "DBNAME"
 msgstr ""
 
-#: ./doc/install-guide/section_dashboard-install.xml:42(para)
-msgid "This command installs and configures Apache correctly, provided that the user asks for it during the <package>debconf</package> prompts. The default SSL certificate is self-signed, and it is probably wise to have it signed by a root Certificate Authority (CA)."
+#: ./doc/install-guide/section_trove-verify.xml:33(replaceable)
+msgid "USER"
 msgstr ""
 
-#: ./doc/install-guide/section_dashboard-install.xml:51(para)
-msgid "Modify the value of <literal>CACHES['default']['LOCATION']</literal> in <filename os=\"ubuntu;debian\">/etc/openstack-dashboard/local_settings.py</filename><filename os=\"centos;fedora;rhel\">/etc/openstack-dashboard/local_settings</filename><filename os=\"opensuse;sles\">/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py</filename> to match the ones set in <filename os=\"ubuntu;debian\">/etc/memcached.conf</filename><filename os=\"centos;fedora;rhel;opensuse;sles\">/etc/sysconfig/memcached</filename>."
+#: ./doc/install-guide/section_trove-verify.xml:33(replaceable)
+msgid "PASSWORD"
 msgstr ""
 
-#: ./doc/install-guide/section_dashboard-install.xml:63(para)
-msgid "Open <filename os=\"ubuntu;debian\">/etc/openstack-dashboard/local_settings.py</filename><filename os=\"centos;fedora;rhel\">/etc/openstack-dashboard/local_settings</filename> and look for this line:"
+#: ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml:6(title)
+msgid "Add another proxy server"
 msgstr ""
 
-#: ./doc/install-guide/section_dashboard-install.xml:76(title) ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:29(td)
-msgid "Notes"
+#: ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml:7(para)
+msgid "To provide additional reliability and bandwidth to your cluster, you can add proxy servers. You can set up an additional proxy node the same way that you set up the first proxy node but with additional configuration steps."
 msgstr ""
 
-#: ./doc/install-guide/section_dashboard-install.xml:79(para)
-msgid "The address and port must match the ones set in <filename os=\"ubuntu;debian\">/etc/memcached.conf</filename><filename os=\"centos;fedora;rhel;opensuse;sles\">/etc/sysconfig/memcached</filename>."
+#: ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml:12(para)
+msgid "After you have more than two proxies, you must load balance them; your storage endpoint (what clients use to connect to your storage) also changes. You can select from different strategies for load balancing. For example, you could use round-robin DNS, or a software or hardware load balancer (like pound) in front of the two proxies. You can then point your storage URL to the load balancer, configure an initial proxy node and complete these steps to add proxy servers."
 msgstr ""
 
-#: ./doc/install-guide/section_dashboard-install.xml:84(para)
-msgid "If you change the memcached settings, you must restart the Apache web server for the changes to take effect."
+#: ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml:25(para)
+msgid "Update the list of memcache servers in the <filename>/etc/swift/proxy-server.conf</filename> file for added proxy servers. If you run multiple memcache servers, use this pattern for the multiple IP:port listings in each proxy server configuration file:"
 msgstr ""
 
-#: ./doc/install-guide/section_dashboard-install.xml:89(para)
-msgid "You can use options other than memcached option for session storage. Set the session back-end through the <parameter>SESSION_ENGINE</parameter> option."
+#: ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml:36(replaceable) ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:31(replaceable) ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:37(replaceable) ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:38(replaceable)
+msgid "PROXY_LOCAL_NET_IP"
 msgstr ""
 
-#: ./doc/install-guide/section_dashboard-install.xml:96(para)
-msgid "To change the timezone, use the dashboard or edit the <filename os=\"centos;fedora;rhel\">/etc/openstack-dashboard/local_settings</filename><filename os=\"ubuntu;debian\">/etc/openstack-dashboard/local_settings.py</filename><filename os=\"opensuse;sles\">/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py</filename> file."
+#: ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml:39(para)
+msgid "Copy ring information to all nodes, including new proxy nodes. Also, ensure that the ring information gets to all storage nodes."
 msgstr ""
 
-#: ./doc/install-guide/section_dashboard-install.xml:105(para)
-msgid "Change the following parameter: <code>TIME_ZONE = \"UTC\"</code>"
-msgstr ""
-
-#: ./doc/install-guide/section_dashboard-install.xml:112(para)
-msgid "Update the <literal>ALLOWED_HOSTS</literal> in <filename>local_settings.py</filename> to include the addresses you wish to access the dashboard from."
-msgstr ""
-
-#: ./doc/install-guide/section_dashboard-install.xml:116(para)
-msgid "Edit <filename os=\"centos;fedora;rhel\">/etc/openstack-dashboard/local_settings</filename><filename os=\"ubuntu;debian\">/etc/openstack-dashboard/local_settings.py</filename><filename os=\"opensuse;sles\">/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py</filename>:"
-msgstr ""
-
-#: ./doc/install-guide/section_dashboard-install.xml:127(para)
-msgid "This guide assumes that you are running the Dashboard on the controller node. You can easily run the dashboard on a separate server, by changing the appropriate settings in <filename>local_settings.py</filename>."
-msgstr ""
-
-#: ./doc/install-guide/section_dashboard-install.xml:132(para)
-msgid "Edit <filename os=\"centos;fedora;rhel\">/etc/openstack-dashboard/local_settings</filename><filename os=\"ubuntu;debian\">/etc/openstack-dashboard/local_settings.py</filename><filename os=\"opensuse;sles\">/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py</filename> and change <literal>OPENSTACK_HOST</literal> to the hostname of your Identity Service:"
-msgstr ""
-
-#: ./doc/install-guide/section_dashboard-install.xml:144(para)
-msgid "Setup Apache configuration: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/install-guide/section_dashboard-install.xml:151(para)
-msgid "By default, the <systemitem>openstack-dashboard</systemitem> package enables a database as session store. Before you continue, either change the session store set up as described in <xref linkend=\"dashboard-sessions\"/> or finish the setup of the database session store as explained in <xref linkend=\"dashboard-session-database\"/>."
-msgstr ""
-
-#: ./doc/install-guide/section_dashboard-install.xml:161(para)
-msgid "Ensure that the SELinux policy of the system is configured to allow network connections to the HTTP server."
-msgstr ""
-
-#: ./doc/install-guide/section_dashboard-install.xml:168(para)
-msgid "Start the Apache web server and memcached:"
-msgstr ""
-
-#: ./doc/install-guide/section_dashboard-install.xml:181(para)
-msgid "You can now access the dashboard at <uri os=\"ubuntu\">http://controller/horizon</uri><uri os=\"debian\">https://controller/</uri><uri os=\"centos;fedora;rhel\">http://controller/dashboard</uri><uri os=\"opensuse;sles\">http://controller</uri>."
-msgstr ""
-
-#: ./doc/install-guide/section_dashboard-install.xml:188(para)
-msgid "Login with credentials for any user that you created with the OpenStack Identity Service."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-queue.xml:6(title)
-msgid "Messaging server"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-queue.xml:7(para)
-msgid "OpenStack uses a <glossterm>message broker</glossterm> to coordinate operations and status information among services. The message broker service typically runs on the controller node. OpenStack supports several message brokers including <application>RabbitMQ</application>, <application>Qpid</application>, and <application>ZeroMQ</application>. However, most distributions that package OpenStack support a particular message broker. This guide covers the message broker supported by each distribution. If you prefer to implement a different message broker, consult the documentation associated with it."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-queue.xml:18(link)
-msgid "RabbitMQ"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-queue.xml:21(link)
-msgid "Qpid"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-queue.xml:24(link)
-msgid "ZeroMQ"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-queue.xml:28(title)
-msgid "To install the message broker service"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-queue.xml:30(para)
-msgid "Ubuntu and Debian use <application>RabbitMQ</application>."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-queue.xml:34(para)
-msgid "Red Hat Enterprise Linux (RHEL), CentOS, Scientific Linux, and Fedora use <application>Qpid</application>."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-queue.xml:40(para)
-msgid "SUSE Linux Enterprise Server (SLES) and openSUSE use <application>RabbitMQ</application>."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-queue.xml:46(title)
-msgid "To configure the message broker service"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-queue.xml:48(para)
-msgid "To simplify installation of your test environment, we recommend that you disable authentication."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-queue.xml:50(para)
-msgid "Edit the <filename>/etc/qpidd.conf</filename> file and change the following key:"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-queue.xml:54(para)
-msgid "For production environments, you should enable authentication. For more information on securing the message broker, see the <link href=\"http://qpid.apache.org/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/chap-Messaging_User_Guide-Security.html\">documentation</link>."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-queue.xml:59(para)
-msgid "If you decide to enable authentication for your test environment, you must configure the <literal>qpid_username</literal> and <literal>qpid_password</literal> keys in the configuration file of each OpenStack service that uses the message broker."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-queue.xml:66(para)
-msgid "Start the message broker service:"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-queue.xml:70(para)
-msgid "The message broker creates a default account that uses <literal>guest</literal> for the username and password. To simplify installation of your test environment, we recommend that you use this account, but change the password for it."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-queue.xml:74(para) ./doc/install-guide/section_nova-compute.xml:159(para) ./doc/install-guide/section_nova-compute.xml:178(para)
-msgid "Run the following command:"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-queue.xml:75(para)
-msgid "Replace <replaceable>RABBIT_PASS</replaceable> with a suitable password."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-queue.xml:78(para)
-msgid "You must configure the <literal>rabbit_password</literal> key in the configuration file for each OpenStack service that uses the message broker."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-queue.xml:82(para)
-msgid "For production environments, you should create a unique account with suitable password. For more information on securing the message broker, see the <link href=\"https://www.rabbitmq.com/man/rabbitmqctl.1.man.html\">documentation</link>."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-queue.xml:87(para)
-msgid "If you decide to create a unique account with suitable password for your test environment, you must configure the <literal>rabbit_userid</literal> and <literal>rabbit_password</literal> keys in the configuration file of each OpenStack service that uses the message broker."
-msgstr ""
-
-#: ./doc/install-guide/section_basics-queue.xml:98(para)
-msgid "Start the message broker service and configure it to start when the system boots:"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-queue.xml:104(para)
-msgid "Configure the message broker service to start when the system boots:"
-msgstr ""
-
-#: ./doc/install-guide/section_basics-queue.xml:109(para)
-msgid "Congratulations, now you are ready to install OpenStack services!"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_neutron-initial-networks.xml:23(None)
-msgid "@@image: 'figures/installguide_neutron-initial-networks.png'; md5=df1d74b6f91feefe5cfaf7824aac86e1"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:6(title)
-msgid "Create initial networks"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:7(para)
-msgid "Before launching your first instance, you must create the necessary virtual network infrastructure to which the instance will connect, including the <link linkend=\"neutron_initial-external-network\">external network</link> and <link linkend=\"neutron_initial-tenant-network\">tenant network</link>. See <xref linkend=\"neutron_figure-neutron-initial-networks\"/>. After creating this infrastructure, we recommend that you <link linkend=\"neutron_initial-networks-verify\">verify connectivity</link> and resolve any issues before proceeding further."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:19(title)
-msgid "Initial networks"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:28(title)
-msgid "External network"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:29(para)
-msgid "The external network typically provides internet access for your instances. By default, this network only allows internet access <emphasis>from</emphasis> instances using <glossterm>Network Address Translation (NAT)</glossterm>. You can enable internet access <emphasis>to</emphasis> individual instances using a <glossterm>floating IP address</glossterm> and suitable <glossterm>security group</glossterm> rules. The <literal>admin</literal> tenant owns this network because it provides external network access for multiple tenants. You must also enable sharing to allow access by those tenants."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:43(title)
-msgid "To create the external network"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:69(para)
-msgid "Like a physical network, a virtual network requires a <glossterm>subnet</glossterm> assigned to it. The external network shares the same subnet and <glossterm>gateway</glossterm> associated with the physical network connected to the external interface on the network node. You should specify an exclusive slice of this subnet for <glossterm>router</glossterm> and floating IP addresses to prevent interference with other devices on the external network."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:76(para)
-msgid "Replace <replaceable>FLOATING_IP_START</replaceable> and <replaceable>FLOATING_IP_END</replaceable> with the first and last IP addresses of the range that you want to allocate for floating IP addresses. Replace <replaceable>EXTERNAL_NETWORK_CIDR</replaceable> with the subnet associated with the physical network. Replace <replaceable>EXTERNAL_NETWORK_GATEWAY</replaceable> with the gateway associated with the physical network, typically the \".1\" IP address. You should disable <glossterm>DHCP</glossterm> on this subnet because instances do not connect directly to the external network and floating IP addresses require manual assignment."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:87(title)
-msgid "To create a subnet on the external network"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:89(para) ./doc/install-guide/section_neutron-initial-networks.xml:164(para)
-msgid "Create the subnet:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:91(replaceable)
-msgid "FLOATING_IP_START"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:91(replaceable)
-msgid "FLOATING_IP_END"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:92(replaceable)
-msgid "EXTERNAL_NETWORK_GATEWAY"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:92(replaceable)
-msgid "EXTERNAL_NETWORK_CIDR"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:93(para)
-msgid "For example, using <literal>203.0.113.0/24</literal> with floating IP address range <literal>203.0.113.101</literal> to <literal>203.0.113.200</literal>:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:121(title)
-msgid "Tenant network"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:122(para)
-msgid "The tenant network provides internal network access for instances. The architecture isolates this type of network from other tenants. The <literal>demo</literal> tenant owns this network because it only provides network access for instances within it."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:130(title)
-msgid "To create the tenant network"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:152(para)
-msgid "Like the external network, your tenant network also requires a subnet attached to it. You can specify any valid subnet because the architecture isolates tenant networks. Replace <replaceable>TENANT_NETWORK_CIDR</replaceable> with the subnet you want to associate with the tenant network. Replace <replaceable>TENANT_NETWORK_GATEWAY</replaceable> with the gateway you want to associate with this network, typically the \".1\" IP address. By default, this subnet will use DHCP so your instances can obtain IP addresses."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:162(title)
-msgid "To create a subnet on the tenant network"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:166(replaceable)
-msgid "TENANT_NETWORK_GATEWAY"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:166(replaceable)
-msgid "TENANT_NETWORK_CIDR"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:167(para)
-msgid "Example using <literal>192.168.1.0/24</literal>:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:190(para)
-msgid "A virtual router passes network traffic between two or more virtual networks. Each router requires one or more <glossterm baseform=\"interface\">interfaces</glossterm> and/or gateways that provide access to specific networks. In this case, you will create a router and attach your tenant and external networks to it."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:196(title)
-msgid "To create a router on the tenant network and attach the external and tenant networks to it"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:199(para)
-msgid "Create the router:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:214(para)
-msgid "Attach the router to the <literal>demo</literal> tenant subnet:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:220(para)
-msgid "Attach the router to the external network by setting it as the gateway:"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:229(para)
-msgid "We recommend that you verify network connectivity and resolve any issues before proceeding further. Following the external network subnet example using <literal>203.0.113.0/24</literal>, the tenant router gateway should occupy the lowest IP address in the floating IP address range, <literal>203.0.113.101</literal>. If you configured your external physical network and virtual networks correctly, you you should be able to <placeholder-1/> this IP address from any host on your external physical network."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:238(para)
-msgid "If you are building your OpenStack nodes as virtual machines, you must configure the hypervisor to permit promiscuous mode on the external network."
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:243(title)
-msgid "To verify network connectivity"
-msgstr ""
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml:245(para)
-msgid "Ping the tenant router gateway:"
-msgstr ""
-
-#: ./doc/install-guide/section_heat-install.xml:5(title)
-msgid "Install the Orchestration service"
-msgstr ""
-
-#: ./doc/install-guide/section_heat-install.xml:8(para) ./doc/install-guide/section_heat-install.xml:24(para)
-msgid "Install the Orchestration module on the controller node:"
-msgstr ""
-
-#: ./doc/install-guide/section_heat-install.xml:13(para)
-msgid "Respond to prompts for <link linkend=\"debconf-dbconfig-common\">database management</link>, <link linkend=\"debconf-keystone_authtoken\"><systemitem>[keystone_authtoken]</systemitem> settings</link>, <link linkend=\"debconf-rabbitqm\">RabbitMQ credentials</link> and <link linkend=\"debconf-api-endpoints\">API endpoint</link> registration."
-msgstr ""
-
-#: ./doc/install-guide/section_heat-install.xml:33(para)
-msgid "In the configuration file, specify the location of the database where the Orchestration service stores data. These examples use a MySQL database with a <literal>heat</literal> user on the controller node. Replace <replaceable>HEAT_DBPASS</replaceable> with the password for the database user:"
-msgstr ""
-
-#: ./doc/install-guide/section_heat-install.xml:40(replaceable) ./doc/install-guide/section_heat-install.xml:46(replaceable) ./doc/install-guide/section_heat-install.xml:61(replaceable) ./doc/install-guide/section_heat-install.xml:63(replaceable)
-msgid "HEAT_DBPASS"
-msgstr ""
-
-#: ./doc/install-guide/section_heat-install.xml:41(para)
-msgid "Edit <filename>/etc/heat/heat.conf</filename> and modify the <literal>[database]</literal> section:"
-msgstr ""
-
-#: ./doc/install-guide/section_heat-install.xml:49(para)
-msgid "By default, the Ubuntu packages create an SQLite database. Delete the <filename>heat.sqlite</filename> file that was created in the <filename>/var/lib/heat/</filename> directory so that it does not get used by mistake:"
-msgstr ""
-
-#: ./doc/install-guide/section_heat-install.xml:56(para)
-msgid "Use the password that you set previously to log in as <literal>root</literal> and create a <literal>heat</literal> database user:"
-msgstr ""
-
-#: ./doc/install-guide/section_heat-install.xml:66(para)
-msgid "Create the heat service tables:"
-msgstr ""
-
-#: ./doc/install-guide/section_heat-install.xml:69(para)
-msgid "Ignore <errortext>DeprecationWarning</errortext> errors."
-msgstr ""
-
-#: ./doc/install-guide/section_heat-install.xml:74(para)
-msgid "The Ubuntu packages do not correctly set up logging. Edit the <filename>/etc/heat/heat.conf</filename> file and change the <literal>[DEFAULT]</literal> section:"
-msgstr ""
-
-#: ./doc/install-guide/section_heat-install.xml:88(para)
-msgid "Configure the Orchestration Service to use the RabbitMQ message broker."
-msgstr ""
-
-#: ./doc/install-guide/section_heat-install.xml:90(para)
-msgid "Edit <filename>/etc/heat/heat.conf</filename> and modify the <literal>[DEFAULT]</literal> section:"
-msgstr ""
-
-#: ./doc/install-guide/section_heat-install.xml:99(para)
-msgid "Create a <literal>heat</literal> user that the Orchestration service can use to authenticate with the Identity Service. Use the <literal>service</literal> tenant and give the user the <literal>admin</literal> role:"
-msgstr ""
-
-#: ./doc/install-guide/section_heat-install.xml:103(replaceable) ./doc/install-guide/section_heat-install.xml:119(replaceable)
-msgid "HEAT_PASS"
-msgstr ""
-
-#: ./doc/install-guide/section_heat-install.xml:104(replaceable)
-msgid "heat@example.com"
-msgstr ""
-
-#: ./doc/install-guide/section_heat-install.xml:108(para)
-msgid "Edit the <filename>/etc/heat/heat.conf</filename> file to change the <literal>[keystone_authtoken]</literal> and <literal>[ec2authtoken]</literal> sections to add credentials to the Orchestration Service:"
-msgstr ""
-
-#: ./doc/install-guide/section_heat-install.xml:125(para)
-msgid "Register the Heat and CloudFormation APIs with the Identity Service so that other OpenStack services can locate these APIs. Register the services and specify the endpoints:"
-msgstr ""
-
-#: ./doc/install-guide/section_heat-install.xml:145(para)
-msgid "Create the <literal>heat_stack_user</literal> role."
-msgstr ""
-
-#: ./doc/install-guide/section_heat-install.xml:146(para)
-msgid "This role is used as the default role for users created by the Orchestration module."
-msgstr ""
-
-#: ./doc/install-guide/section_heat-install.xml:148(para)
-msgid "Run the following command to create the <literal>heat_stack_user</literal> role:"
-msgstr ""
-
-#: ./doc/install-guide/section_heat-install.xml:153(para)
-msgid "Configure the metadata and waitcondition servers' URLs."
-msgstr ""
-
-#: ./doc/install-guide/section_heat-install.xml:154(para)
-msgid "Edit the <filename>/etc/heat/heat.conf</filename> file and modify the following options in the <literal>[DEFAULT]</literal> section:"
-msgstr ""
-
-#: ./doc/install-guide/section_heat-install.xml:160(replaceable) ./doc/install-guide/section_heat-install.xml:163(replaceable) ./doc/install-guide/section_heat-install.xml:168(replaceable) ./doc/install-guide/section_heat-install.xml:170(replaceable)
-msgid "10.0.0.11"
-msgstr ""
-
-#: ./doc/install-guide/section_heat-install.xml:164(para)
-msgid "Run the following commands to modify the <literal>[DEFAULT]</literal> section of the <filename>/etc/heat/heat.conf</filename> file:"
-msgstr ""
-
-#: ./doc/install-guide/section_heat-install.xml:172(para)
-msgid "The example uses the IP address of the controller (10.0.0.11) instead of the <literal>controller</literal> host name since our example architecture does not include a DNS setup. Make sure that the instances can resolve the controller host name if you choose to use it in the URLs."
-msgstr ""
-
-#: ./doc/install-guide/section_heat-install.xml:186(para)
-msgid "Start the <systemitem class=\"service\">heat-api</systemitem>, <systemitem class=\"service\">heat-api-cfn</systemitem> and <systemitem class=\"service\">heat-engine</systemitem> services and configure them to start when the system boots:"
-msgstr ""
-
-#: ./doc/install-guide/section_ceilometer-nova.xml:7(title)
-msgid "Install the Compute agent for Telemetry"
-msgstr ""
-
-#: ./doc/install-guide/section_ceilometer-nova.xml:9(para)
-msgid "Telemetry provides an API service that provides a collector and a range of disparate agents. This procedure details how to install the agent that runs on the compute node."
-msgstr ""
-
-#: ./doc/install-guide/section_ceilometer-nova.xml:14(para)
-msgid "Install the Telemetry service on the compute node:"
-msgstr ""
-
-#: ./doc/install-guide/section_ceilometer-nova.xml:20(para)
-msgid "Set the following options in the <filename>/etc/nova/nova.conf</filename> file:"
-msgstr ""
-
-#: ./doc/install-guide/section_ceilometer-nova.xml:30(para)
-msgid "The <option>notification_driver</option> option is a multi valued option, which <application>openstack-config</application> cannot set properly. See <xref linkend=\"basics-packages\"/>."
-msgstr ""
-
-#: ./doc/install-guide/section_ceilometer-nova.xml:36(para)
-msgid "Edit the <filename>/etc/nova/nova.conf</filename> file and add the following lines to the <literal>[DEFAULT]</literal> section:"
-msgstr ""
-
-#: ./doc/install-guide/section_ceilometer-nova.xml:58(para)
-msgid "You must set the secret key that you defined previously. The Telemetry service nodes share this key as a shared secret:"
-msgstr ""
-
-#: ./doc/install-guide/section_ceilometer-nova.xml:63(para)
-msgid "Edit the <filename>/etc/ceilometer/ceilometer.conf</filename> file and change these lines in the <literal>[publisher]</literal> section. Replace <replaceable>CEILOMETER_TOKEN</replaceable> with the ceilometer token that you created previously:"
-msgstr ""
-
-#: ./doc/install-guide/section_ceilometer-nova.xml:84(para)
-msgid "Configure the QPid access:"
-msgstr ""
-
-#: ./doc/install-guide/section_ceilometer-nova.xml:89(para)
-msgid "Add the Identity service credentials:"
-msgstr ""
-
-#: ./doc/install-guide/section_ceilometer-nova.xml:141(para)
-msgid "Start the service and configure it to start when the system boots:"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-compute.xml:5(title)
-msgid "Configure a compute node"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-compute.xml:6(para)
-msgid "After you configure the Compute service on the controller node, you must configure another system as a compute node. The compute node receives requests from the controller node and hosts virtual machine instances. You can run all services on a single node, but the examples in this guide use separate systems. This makes it easy to scale horizontally by adding additional Compute nodes following the instructions in this section."
-msgstr ""
-
-#: ./doc/install-guide/section_nova-compute.xml:13(para)
-msgid "The Compute service relies on a hypervisor to run virtual machine instances. OpenStack can use various hypervisors, but this guide uses KVM."
-msgstr ""
-
-#: ./doc/install-guide/section_nova-compute.xml:18(para)
-msgid "Install the Compute packages:"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-compute.xml:20(para)
-msgid "When prompted to create a <literal>supermin</literal> appliance, respond <placeholder-1/>."
-msgstr ""
-
-#: ./doc/install-guide/section_nova-compute.xml:25(para)
-msgid "To use the meta-packages and install other components on your compute node, such as OpenStack Networking and Telemetry agents, run this command:"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-compute.xml:29(para)
-msgid "The controller node has the <package>openstack-proxy-node</package> and <package>openstack-toaster</package> meta-packages that install <package>openstack-proxy-node</package> and <package>openstack-toaster</package> at the same time."
-msgstr ""
-
-#: ./doc/install-guide/section_nova-compute.xml:41(para)
-msgid "Respond to the prompts for <link linkend=\"debconf-dbconfig-common\">database management</link>, <link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> settings</link>, <link linkend=\"debconf-rabbitqm\">RabbitMQ credentials</link>, and <link linkend=\"debconf-api-endpoints\">API endpoint</link> registration."
-msgstr ""
-
-#: ./doc/install-guide/section_nova-compute.xml:50(para)
-msgid "For security reasons, the Linux kernel is not readable by normal users which restricts hypervisor services such as qemu and libguestfs. For details, see <link href=\"https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725\">this bug</link>. To make the current kernel readable, run: <placeholder-1/> To also enable this override for all future kernel updates, create the file <filename>/etc/kernel/postinst.d/statoverride</filename> containing:<placeholder-2/> Remember to make the file executable: <placeholder-3/>"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-compute.xml:69(para)
-msgid "Edit the <filename>/etc/nova/nova.conf</filename> configuration file:"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-compute.xml:81(para)
-msgid "Edit the <filename>/etc/nova/nova.conf</filename> configuration file and add these lines to the appropriate sections:"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-compute.xml:102(para)
-msgid "Configure the Compute service to use the Qpid message broker by setting these configuration keys:"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-compute.xml:116(para)
-msgid "Configure the Compute service to use the RabbitMQ message broker by setting these configuration keys:"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-compute.xml:125(para)
-msgid "Configure Compute to provide remote console access to instances."
-msgstr ""
-
-#: ./doc/install-guide/section_nova-compute.xml:132(para)
-msgid "Edit <filename>/etc/nova/nova.conf</filename> and add the following keys under the <literal>[DEFAULT]</literal> section:"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-compute.xml:146(para)
-msgid "Specify the host that runs the Image Service.<phrase os=\"ubuntu;debian\"> Edit <filename>/etc/nova/nova.conf</filename> file and add these lines to the <literal>[DEFAULT]</literal> section:</phrase>"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-compute.xml:157(para)
-msgid "You must determine whether your system's processor and/or hypervisor support hardware acceleration for virtual machines."
-msgstr ""
-
-#: ./doc/install-guide/section_nova-compute.xml:161(para)
-msgid "If this command returns a value of <emphasis>one or greater</emphasis>, your system supports hardware acceleration which typically requires no additional configuration."
-msgstr ""
-
-#: ./doc/install-guide/section_nova-compute.xml:165(para)
-msgid "If this command returns a value of <emphasis>zero</emphasis>, your system does not support hardware acceleration and you must configure <literal>libvirt</literal> to use QEMU instead of KVM."
-msgstr ""
-
-#: ./doc/install-guide/section_nova-compute.xml:170(para)
-msgid "Edit the <literal>[libvirt]</literal> section in the <filename>/etc/nova/nova-compute.conf</filename> file to modify this key:"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-compute.xml:183(para)
-msgid "On Ubuntu 12.04, kernels backported from newer releases may not automatically load the KVM modules for hardware acceleration when the system boots. In this case, launching an instance will fail with the following message in the <filename>/var/log/nova/nova-compute.log</filename> file:"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-compute.xml:189(para)
-msgid "As a workaround for this issue, you must add the appropriate module for your system to the <filename>/etc/modules</filename> file."
-msgstr ""
-
-#: ./doc/install-guide/section_nova-compute.xml:192(para)
-msgid "For systems with Intel processors, run the following command:"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-compute.xml:195(para)
-msgid "For systems with AMD processors, run the following command:"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-compute.xml:201(para)
-msgid "Remove the SQLite database created by the packages:"
-msgstr ""
-
-#: ./doc/install-guide/section_nova-compute.xml:205(para)
-msgid "Start the Compute service and configure it to start when the system boots:"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_glance-install.xml:38(None)
-msgid "@@image: 'figures/debconf-screenshots/glance-common_pipeline_flavor.png'; md5=78bef92c36a140ad042074f6345d8917"
-msgstr ""
-
-#: ./doc/install-guide/section_glance-install.xml:5(title)
-msgid "Install the Image Service"
-msgstr ""
-
-#: ./doc/install-guide/section_glance-install.xml:6(para)
-msgid "The OpenStack Image Service acts as a registry for virtual disk images. Users can add new images or take a snapshot of an image from an existing server for immediate storage. Use snapshots for back up and as templates to launch new servers. You can store registered images in Object Storage or in other locations. For example, you can store images in simple file systems or external web servers."
-msgstr ""
-
-#: ./doc/install-guide/section_glance-install.xml:14(para)
-msgid "This procedure assumes you set the appropriate environment variables to your credentials as described in <xref linkend=\"keystone-verify\"/>."
-msgstr ""
-
-#: ./doc/install-guide/section_glance-install.xml:20(para)
-msgid "Install the Image Service on the controller node:"
-msgstr ""
-
-#: ./doc/install-guide/section_glance-install.xml:27(para)
-msgid "Respond to prompts for <link linkend=\"debconf-dbconfig-common\">database management</link>, <link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> settings</link>, <link linkend=\"debconf-rabbitqm\">RabbitMQ credentials</link> and <link linkend=\"debconf-api-endpoints\">API endpoint</link> registration. You must also select the caching type:"
-msgstr ""
-
-#: ./doc/install-guide/section_glance-install.xml:43(para)
-msgid "The Image Service stores information about images in a database. The examples in this guide use the MySQL database that is used by other OpenStack services."
-msgstr ""
-
-#: ./doc/install-guide/section_glance-install.xml:46(para)
-msgid "Configure the location of the database. The Image Service provides the <systemitem class=\"service\">glance-api</systemitem> and <systemitem class=\"service\">glance-registry</systemitem> services, each with its own configuration file. You must update both configuration files throughout this section. Replace <replaceable>GLANCE_DBPASS</replaceable> with your Image Service database password."
-msgstr ""
-
-#: ./doc/install-guide/section_glance-install.xml:55(replaceable) ./doc/install-guide/section_glance-install.xml:57(replaceable) ./doc/install-guide/section_glance-install.xml:120(replaceable) ./doc/install-guide/section_glance-install.xml:122(replaceable)
-msgid "GLANCE_DBPASS"
-msgstr ""
-
-#: ./doc/install-guide/section_glance-install.xml:58(para)
-msgid "Edit <filename>/etc/glance/glance-api.conf</filename> and <filename>/etc/glance/glance-registry.conf</filename> and edit the <literal>[database]</literal> section of each file:"
-msgstr ""
-
-#: ./doc/install-guide/section_glance-install.xml:70(para) ./doc/install-guide/section_glance-install.xml:77(para) ./doc/install-guide/section_glance-install.xml:95(para)
-msgid "Configure the Image Service to use the message broker:"
-msgstr ""
-
-#: ./doc/install-guide/section_glance-install.xml:80(para)
-msgid "Edit the <filename>/etc/glance/glance-api.conf</filename> file and add the following keys to the <literal>[DEFAULT]</literal> section:"
-msgstr ""
-
-#: ./doc/install-guide/section_glance-install.xml:108(para)
-msgid "By default, the Ubuntu packages create an SQLite database. Delete the <filename>glance.sqlite</filename> file created in the <filename>/var/lib/glance/</filename> directory so that it does not get used by mistake:"
-msgstr ""
-
-#: ./doc/install-guide/section_glance-install.xml:115(para)
-msgid "Use the password you created to log in as root and create a <literal>glance</literal> database user:"
-msgstr ""
-
-#: ./doc/install-guide/section_glance-install.xml:125(para)
-msgid "Create the database tables for the Image Service:"
-msgstr ""
-
-#: ./doc/install-guide/section_glance-install.xml:129(para)
-msgid "Create a <literal>glance</literal> user that the Image Service can use to authenticate with the Identity service. Choose a password and specify an email address for the <literal>glance</literal> user. Use the <literal>service</literal> tenant and give the user the <literal>admin</literal> role:"
-msgstr ""
-
-#: ./doc/install-guide/section_glance-install.xml:135(replaceable) ./doc/install-guide/section_glance-install.xml:159(replaceable) ./doc/install-guide/section_glance-install.xml:175(replaceable) ./doc/install-guide/section_glance-install.xml:194(replaceable)
-msgid "GLANCE_PASS"
-msgstr ""
-
-#: ./doc/install-guide/section_glance-install.xml:136(replaceable)
-msgid "glance@example.com"
-msgstr ""
-
-#: ./doc/install-guide/section_glance-install.xml:140(para)
-msgid "Configure the Image Service to use the Identity Service for authentication."
-msgstr ""
-
-#: ./doc/install-guide/section_glance-install.xml:142(para)
-msgid "Run the following commands and replace <replaceable>GLANCE_PASS</replaceable> with the password you chose for the <literal>glance</literal> user in the Identity Service:"
-msgstr ""
-
-#: ./doc/install-guide/section_glance-install.xml:178(para)
-msgid "Edit the <filename>/etc/glance/glance-api.conf</filename> and <filename>/etc/glance/glance-registry.conf</filename> files. Replace <replaceable>GLANCE_PASS</replaceable> with the password you chose for the <literal>glance</literal> user in the Identity service."
-msgstr ""
-
-#: ./doc/install-guide/section_glance-install.xml:185(para)
-msgid "Add or modify the following keys under the <literal>[keystone_authtoken]</literal> section:"
-msgstr ""
-
-#: ./doc/install-guide/section_glance-install.xml:197(para)
-msgid "Modify the following key under the <literal>[paste_deploy]</literal> section:"
-msgstr ""
-
-#: ./doc/install-guide/section_glance-install.xml:206(para)
-msgid "Register the Image Service with the Identity service so that other OpenStack services can locate it. Register the service and create the endpoint:"
-msgstr ""
-
-#: ./doc/install-guide/section_glance-install.xml:218(para)
-msgid "Restart the <systemitem class=\"service\">glance</systemitem> service with its new settings:"
-msgstr ""
-
-#: ./doc/install-guide/section_glance-install.xml:224(para)
-msgid "Start the <systemitem class=\"service\">glance-api</systemitem> and <systemitem class=\"service\">glance-registry</systemitem> services and configure them to start when the system boots:"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml:30(None)
-msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_keep_admin_pass.png'; md5=01af4867c16e458306b8abd78a1fccc9"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml:39(None)
-msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_used_for_remote_db.png'; md5=c6ec966bbfdee18ad87456cf4d44a56f"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml:78(None)
-msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_1_configure-with-dbconfig-yes-no.png'; md5=4e9d7bce27cc6c7bd68ce8622c80b60f"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml:87(None)
-msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_2_db-types.png'; md5=a77beb7e13b487cf79716c2140f258c2"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml:96(None)
-msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_3_connection_method.png'; md5=6cc592e5dd5ea404ad7aad98b37a71f6"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml:105(None)
-msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_4_mysql_root_password.png'; md5=873ec338742e37305583e9e692bcfdc6"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml:114(None)
-msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_5_mysql_app_password.png'; md5=3651970770d05892f21d1b5741afbee6"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml:123(None)
-msgid "@@image: 'figures/debconf-screenshots/dbconfig-common_6_mysql_app_password_confirm.png'; md5=060cc90aaf6f6fd5cea718064829c1b1"
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml:6(title)
-msgid "Configure the database with dbconfig-common"
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml:7(para)
-msgid "The <package>dbconfig-common</package> package provides a standard Debian interface that enables you to configure Debian database parameters. It includes localized prompts for many languages and it supports the OpenStack database back ends: SQLite, MySQL, and PostgreSQL."
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml:12(para)
-msgid "By default, the <package>dbconfig-common</package> package configures the OpenStack services to use SQLite3. So if you use <package>debconf</package> in non-interactive mode and without pre-seeding, the OpenStack services that you install use SQLite3."
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml:17(para)
-msgid "By default, <package>dbconfig-common</package> does not provide access to database servers over a network. If you want the <package>dbconfig-common</package> package to prompt for remote database servers that are accessed over a network and not through a UNIX socket file, reconfigure it, as follows:"
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml:23(para)
-msgid "These screens appear when you re-configure the <package>dbconfig-common</package> package:"
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml:43(para)
-msgid "Unlike other <package>debconf</package> prompts, you cannot pre-seed the responses for the <package>dbconfig-common</package> prompts by using <placeholder-1/>. Instead, you must create a file in <filename>/etc/dbconfig-common</filename>. For example, you might create a keystone configuration file for <package>dbconfig-common</package> that is located in <filename>/etc/dbconfig-common/keystone.conf</filename>, as follows:"
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml:66(para)
-msgid "After you create this file, run this command:"
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml:68(para)
-msgid "The Identity Service is installed with MySQL as the database back end, <literal>keystonedb</literal> as database name, and the localhost socket file."
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml:71(para)
-msgid "The <package>cinder-common</package> package displays these screens:"
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml:127(para)
-msgid "To access a MySQL server remotely, you must make it accessible as root from a remote server. To do so, run the <package>openstack-proxy-node</package> package command:"
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml:131(para)
-msgid "Alternatively, if you do not want to install this package, run this script to enable remote root access:"
-msgstr ""
-
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml:154(para)
-msgid "You must enable remote access before you install OpenStack services."
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_keystone-install.xml:79(None)
-msgid "@@image: 'figures/debconf-screenshots/keystone_1_admin_token.png'; md5=29a51caaf09c3d6e3f0fda73c256a17a"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_keystone-install.xml:104(None)
-msgid "@@image: 'figures/debconf-screenshots/keystone_2_register_admin_tenant_yes_no.png'; md5=25c9a90b1df2d979aae6ce9975c7285b"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_keystone-install.xml:113(None)
-msgid "@@image: 'figures/debconf-screenshots/keystone_3_admin_user_name.png'; md5=173cf7ed13252df1425109be588b2ad6"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_keystone-install.xml:122(None)
-msgid "@@image: 'figures/debconf-screenshots/keystone_4_admin_user_email.png'; md5=b7f0d34350ccc0aa9ae4e766b7ac80c1"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_keystone-install.xml:131(None)
-msgid "@@image: 'figures/debconf-screenshots/keystone_5_admin_user_pass.png'; md5=e6b32d8d80af90f07a66abc8fb256c84"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_keystone-install.xml:140(None)
-msgid "@@image: 'figures/debconf-screenshots/keystone_6_admin_user_pass_confirm.png'; md5=1fbf9223e4923c93030d53278d1771cc"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_keystone-install.xml:154(None)
-msgid "@@image: 'figures/debconf-screenshots/keystone_7_register_endpoint.png'; md5=d24d84133bfee936267e79631a2666e6"
-msgstr ""
-
-#: ./doc/install-guide/section_keystone-install.xml:6(title)
-msgid "Install the Identity Service"
-msgstr ""
-
-#: ./doc/install-guide/section_keystone-install.xml:9(para)
-msgid "Install the OpenStack Identity Service on the controller node, together with <application>python-keystoneclient</application> (which is a dependency):"
-msgstr ""
-
-#: ./doc/install-guide/section_keystone-install.xml:17(para)
-msgid "Answer to the <systemitem class=\"library\">debconf</systemitem> and <systemitem class=\"library\">dbconfig-common</systemitem> questions for setting-up the database."
-msgstr ""
-
-#: ./doc/install-guide/section_keystone-install.xml:23(para)
-msgid "The Identity Service uses a database to store information. Specify the location of the database in the configuration file. In this guide, we use a MySQL database on the controller node with the username <literal>keystone</literal>. Replace <literal><replaceable>KEYSTONE_DBPASS</replaceable></literal> with a suitable password for the database user."
-msgstr ""
-
-#: ./doc/install-guide/section_keystone-install.xml:30(replaceable) ./doc/install-guide/section_keystone-install.xml:38(replaceable) ./doc/install-guide/section_keystone-install.xml:57(replaceable) ./doc/install-guide/section_keystone-install.xml:59(replaceable)
-msgid "KEYSTONE_DBPASS"
-msgstr ""
-
-#: ./doc/install-guide/section_keystone-install.xml:31(para)
-msgid "Edit <filename>/etc/keystone/keystone.conf</filename> and change the <literal>[database]</literal> section:"
-msgstr ""
-
-#: ./doc/install-guide/section_keystone-install.xml:44(para)
-msgid "By default, the Ubuntu packages create a SQLite database. Delete the <filename>keystone.db</filename> file created in the <filename>/var/lib/keystone/</filename> directory so that it does not get used by mistake:"
-msgstr ""
-
-#: ./doc/install-guide/section_keystone-install.xml:51(para)
-msgid "Use the password that you set previously to log in as root. Create a <literal>keystone</literal> database user:"
-msgstr ""
-
-#: ./doc/install-guide/section_keystone-install.xml:63(para)
-msgid "Create the database tables for the Identity Service:"
-msgstr ""
-
-#: ./doc/install-guide/section_keystone-install.xml:67(para)
-msgid "Define an authorization token to use as a shared secret between the Identity Service and other OpenStack services. Respond to the <package>debconf</package> prompt with the value in the <code>admin_token</code> directive in the <filename>keystone.conf</filename> file. Use the <placeholder-1/> command to generate this password."
-msgstr ""
-
-#: ./doc/install-guide/section_keystone-install.xml:83(para)
-msgid "Later, you can verify that the <filename>/etc/keystone/keystone.conf</filename> file contains the password you have set using <package>debconf</package>: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/install-guide/section_keystone-install.xml:91(para)
-msgid "If you omit a password (for example by pressing Enter at the <package>debconf</package> prompt, or installing Keystone using the Debconf non-interactive mode) the package generates a random <literal>ADMIN_TOKEN</literal> value."
-msgstr ""
-
-#: ./doc/install-guide/section_keystone-install.xml:97(para)
-msgid "Respond to the prompts to create an administrative tenant:"
-msgstr ""
-
-#: ./doc/install-guide/section_keystone-install.xml:146(para)
-msgid "If this is the first time you have installed the Identity Service, register the Identity Service in the service catalog:"
-msgstr ""
-
-#: ./doc/install-guide/section_keystone-install.xml:160(para)
-msgid "Define an authorization token to use as a shared secret between the Identity Service and other OpenStack services. Use <placeholder-1/> to generate a random token and store it in the configuration file:"
-msgstr ""
-
-#: ./doc/install-guide/section_keystone-install.xml:169(para)
-msgid "For SUSE Linux Enterprise use instead as first command:"
-msgstr ""
-
-#: ./doc/install-guide/section_keystone-install.xml:172(para)
-msgid "Edit <filename>/etc/keystone/keystone.conf</filename> and change the <literal>[DEFAULT]</literal> section, replacing ADMIN_TOKEN with the results of the command:"
-msgstr ""
-
-#: ./doc/install-guide/section_keystone-install.xml:182(para)
-msgid "By default, Keystone uses PKI tokens. Create the signing keys and certificates and restrict access to the generated data:"
-msgstr ""
-
-#: ./doc/install-guide/section_keystone-install.xml:189(para)
-msgid "Configure the log directory. Edit the <filename>/etc/keystone/keystone.conf</filename> file and update the <literal>[DEFAULT]</literal> section:"
-msgstr ""
-
-#: ./doc/install-guide/section_keystone-install.xml:197(para)
-msgid "Restart the Identity Service:"
-msgstr ""
-
-#: ./doc/install-guide/section_keystone-install.xml:201(para)
-msgid "Start the Identity Service and enable it to start when the system boots:"
-msgstr ""
-
-#: ./doc/install-guide/section_keystone-install.xml:207(para)
-msgid "By default, the Identity Service stores expired tokens in the database indefinitely. While potentially useful for auditing in production environments, the accumulation of expired tokens will considerably increase database size and may decrease service performance, particularly in test environments with limited resources. We recommend configuring a periodic task using <systemitem class=\"service\">cron</systemitem> to purge expired tokens hourly."
-msgstr ""
-
-#: ./doc/install-guide/section_keystone-install.xml:217(para)
-msgid "Run the following command to purge expired tokens every hour and log the output to <filename>/var/log/keystone/keystone-tokenflush.log</filename>:"
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml:6(title)
-msgid "Verify the installation"
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml:7(para)
-msgid "You can run these commands from the proxy server or any server that has access to the Identity Service."
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml:11(para)
-msgid "Make sure that your credentials are set up correctly in the <filename>admin-openrc.sh</filename> file and source it:"
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml:15(para)
-msgid "Run the following <placeholder-1/> command:"
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml:27(para)
-msgid "Run the following <placeholder-1/> commands to upload files to a container. Create the <filename>test.txt</filename> and <filename>test2.txt</filename> test files locally if needed."
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml:34(para)
-msgid "Run the following <placeholder-1/> command to download all files from the <literal>myfiles</literal> container:"
+#: ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml:46(para)
+msgid "After you sync all nodes, make sure that the admin has keys in <filename>/etc/swift</filename> and the ownership for the ring file is correct."
 msgstr ""
 
 #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:6(title)
@@ -4836,10 +4840,6 @@ msgstr ""
 msgid "Change it to:"
 msgstr ""
 
-#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:31(replaceable) ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:37(replaceable) ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:38(replaceable) ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml:36(replaceable)
-msgid "PROXY_LOCAL_NET_IP"
-msgstr ""
-
 #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:34(para)
 msgid "Modify memcached to listen on the default interface on a local, non-public network. Edit the <filename>/etc/sysconfig/memcached</filename> file:"
 msgstr ""
@@ -4936,28 +4936,80 @@ msgstr ""
 msgid "Start the Proxy service and configure it to start when the system boots:"
 msgstr ""
 
-#: ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml:6(title)
-msgid "Add another proxy server"
+#: ./doc/install-guide/object-storage/section_object-storage-install.xml:6(title)
+msgid "Install Object Storage"
 msgstr ""
 
-#: ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml:7(para)
-msgid "To provide additional reliability and bandwidth to your cluster, you can add proxy servers. You can set up an additional proxy node the same way that you set up the first proxy node but with additional configuration steps."
+#: ./doc/install-guide/object-storage/section_object-storage-install.xml:7(para)
+msgid "Though you can install OpenStack Object Storage for development or testing purposes on one server, a multiple-server installation enables the high availability and redundancy you want in a production distributed object storage system."
 msgstr ""
 
-#: ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml:12(para)
-msgid "After you have more than two proxies, you must load balance them; your storage endpoint (what clients use to connect to your storage) also changes. You can select from different strategies for load balancing. For example, you could use round-robin DNS, or a software or hardware load balancer (like pound) in front of the two proxies. You can then point your storage URL to the load balancer, configure an initial proxy node and complete these steps to add proxy servers."
+#: ./doc/install-guide/object-storage/section_object-storage-install.xml:11(para)
+msgid "To perform a single-node installation for development purposes from source code, use the Swift All In One instructions (Ubuntu) or DevStack (multiple distros). See <link href=\"http://swift.openstack.org/development_saio.html\">http://swift.openstack.org/development_saio.html</link> for manual instructions or <link href=\"http://devstack.org\">http://devstack.org</link> for all-in-one including authentication with the Identity Service (keystone) v2.0 API."
 msgstr ""
 
-#: ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml:25(para)
-msgid "Update the list of memcache servers in the <filename>/etc/swift/proxy-server.conf</filename> file for added proxy servers. If you run multiple memcache servers, use this pattern for the multiple IP:port listings in each proxy server configuration file:"
+#: ./doc/install-guide/object-storage/section_object-storage-install.xml:20(para)
+msgid "In this guide we recommend installing and configuring the Identity service so that it implements Identity API v2.0. The Object Storage service is unaware of domains when implementing Access Control Lists (ACLs), so you must use the v2.0 API to avoid having identical user names in different domains, which would enable two users to access the same objects."
 msgstr ""
 
-#: ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml:39(para)
-msgid "Copy ring information to all nodes, including new proxy nodes. Also, ensure that the ring information gets to all storage nodes."
+#: ./doc/install-guide/object-storage/section_object-storage-install.xml:29(para)
+msgid "Have a copy of the operating system installation media available if you are installing on a new server."
 msgstr ""
 
-#: ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml:46(para)
-msgid "After you sync all nodes, make sure that the admin has keys in <filename>/etc/swift</filename> and the ownership for the ring file is correct."
+#: ./doc/install-guide/object-storage/section_object-storage-install.xml:31(para)
+msgid "These steps assume you have set up repositories for packages for your operating system as shown in <link linkend=\"basics-packages\">OpenStack Packages</link>."
+msgstr ""
+
+#: ./doc/install-guide/object-storage/section_object-storage-install.xml:34(para)
+msgid "This document demonstrates how to install a cluster by using the following types of nodes:"
+msgstr ""
+
+#: ./doc/install-guide/object-storage/section_object-storage-install.xml:38(para)
+msgid "One proxy node which runs the <systemitem class=\"service\">swift-proxy-server</systemitem> processes. The proxy server proxies requests to the appropriate storage nodes."
+msgstr ""
+
+#: ./doc/install-guide/object-storage/section_object-storage-install.xml:44(para)
+msgid "Five storage nodes that run the <systemitem class=\"service\">swift-account-server</systemitem>, <systemitem class=\"service\">swift-container-server</systemitem>, and <systemitem class=\"service\">swift-object-server</systemitem> processes which control storage of the account databases, the container databases, as well as the actual stored objects."
+msgstr ""
+
+#: ./doc/install-guide/object-storage/section_object-storage-install.xml:57(para)
+msgid "Fewer storage nodes can be used initially, but a minimum of five is recommended for a production cluster."
+msgstr ""
+
+#: ./doc/install-guide/object-storage/section_object-storage-install.xml:62(title)
+msgid "General installation steps"
+msgstr ""
+
+#: ./doc/install-guide/object-storage/section_object-storage-install.xml:65(para)
+msgid "Create a <literal>swift</literal> user that the Object Storage Service can use to authenticate with the Identity Service. Choose a password and specify an email address for the <literal>swift</literal> user. Use the <literal>service</literal> tenant and give the user the <literal>admin</literal> role:"
+msgstr ""
+
+#: ./doc/install-guide/object-storage/section_object-storage-install.xml:72(replaceable)
+msgid "swift@example.com"
+msgstr ""
+
+#: ./doc/install-guide/object-storage/section_object-storage-install.xml:76(para)
+msgid "Create a service entry for the Object Storage Service:"
+msgstr ""
+
+#: ./doc/install-guide/object-storage/section_object-storage-install.xml:94(para)
+msgid "Specify an API endpoint for the Object Storage Service by using the returned service ID. When you specify an endpoint, you provide URLs for the public API, internal API, and admin API. In this guide, the <literal>controller</literal> host name is used:"
+msgstr ""
+
+#: ./doc/install-guide/object-storage/section_object-storage-install.xml:116(para)
+msgid "Create the configuration directory on all nodes:"
+msgstr ""
+
+#: ./doc/install-guide/object-storage/section_object-storage-install.xml:120(para)
+msgid "Create <filename>/etc/swift/swift.conf</filename> on all nodes:"
+msgstr ""
+
+#: ./doc/install-guide/object-storage/section_object-storage-install.xml:126(para)
+msgid "The suffix value in <filename>/etc/swift/swift.conf</filename> should be set to some random string of text to be used as a salt when hashing to determine mappings in the ring. This file must be the same on every node in the cluster!"
+msgstr ""
+
+#: ./doc/install-guide/object-storage/section_object-storage-install.xml:131(para)
+msgid "Next, set up your storage nodes and proxy node. This example uses the Identity Service for the common authentication piece."
 msgstr ""
 
 #. When image changes, this message will be marked fuzzy or untranslated for you.
@@ -5042,126 +5094,28 @@ msgstr ""
 msgid "Recommended size: as for <literal>STORAGE_LOCAL_NET</literal>."
 msgstr ""
 
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:52(None)
-msgid "@@image: '../figures/swift_install_arch.png'; md5=bbda527d20235d54a95eb29279ba2680"
+#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml:6(title)
+msgid "Verify the installation"
 msgstr ""
 
-#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:6(title)
-msgid "Example of Object Storage installation architecture"
+#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml:7(para)
+msgid "You can run these commands from the proxy server or any server that has access to the Identity Service."
 msgstr ""
 
-#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:9(para)
-msgid "Node: A host machine that runs one or more OpenStack Object Storage services."
+#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml:11(para)
+msgid "Make sure that your credentials are set up correctly in the <filename>admin-openrc.sh</filename> file and source it:"
 msgstr ""
 
-#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:13(para)
-msgid "Proxy node: Runs proxy services."
+#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml:15(para)
+msgid "Run the following <placeholder-1/> command:"
 msgstr ""
 
-#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:16(para)
-msgid "Storage node: Runs account, container, and object services. Contains the SQLite databases."
+#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml:27(para)
+msgid "Run the following <placeholder-1/> commands to upload files to a container. Create the <filename>test.txt</filename> and <filename>test2.txt</filename> test files locally if needed."
 msgstr ""
 
-#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:20(para)
-msgid "Ring: A set of mappings between OpenStack Object Storage data to physical devices."
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:24(para)
-msgid "Replica: A copy of an object. By default, three copies are maintained in the cluster."
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:28(para)
-msgid "Zone: A logically separate section of the cluster, related to independent failure characteristics."
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:32(para)
-msgid "Region (optional): A logically separate section of the cluster, representing distinct physical locations such as cities or countries. Similar to zones but representing physical locations of portions of the cluster rather than logical segments."
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:39(para)
-msgid "To increase reliability and performance, you can add additional proxy servers."
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:41(para)
-msgid "This document describes each storage node as a separate zone in the ring. At a minimum, five zones are recommended. A zone is a group of nodes that are as isolated as possible from other nodes (separate servers, network, power, even geography). The ring guarantees that every replica is stored in a separate zone. This diagram shows one possible configuration for a minimal installation:"
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-install.xml:6(title)
-msgid "Install Object Storage"
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-install.xml:7(para)
-msgid "Though you can install OpenStack Object Storage for development or testing purposes on one server, a multiple-server installation enables the high availability and redundancy you want in a production distributed object storage system."
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-install.xml:11(para)
-msgid "To perform a single-node installation for development purposes from source code, use the Swift All In One instructions (Ubuntu) or DevStack (multiple distros). See <link href=\"http://swift.openstack.org/development_saio.html\">http://swift.openstack.org/development_saio.html</link> for manual instructions or <link href=\"http://devstack.org\">http://devstack.org</link> for all-in-one including authentication with the Identity Service (keystone) v2.0 API."
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-install.xml:20(para)
-msgid "In this guide we recommend installing and configuring the Identity service so that it implements Identity API v2.0. The Object Storage service is unaware of domains when implementing Access Control Lists (ACLs), so you must use the v2.0 API to avoid having identical user names in different domains, which would enable two users to access the same objects."
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-install.xml:29(para)
-msgid "Have a copy of the operating system installation media available if you are installing on a new server."
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-install.xml:31(para)
-msgid "These steps assume you have set up repositories for packages for your operating system as shown in <link linkend=\"basics-packages\">OpenStack Packages</link>."
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-install.xml:34(para)
-msgid "This document demonstrates how to install a cluster by using the following types of nodes:"
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-install.xml:38(para)
-msgid "One proxy node which runs the <systemitem class=\"service\">swift-proxy-server</systemitem> processes. The proxy server proxies requests to the appropriate storage nodes."
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-install.xml:44(para)
-msgid "Five storage nodes that run the <systemitem class=\"service\">swift-account-server</systemitem>, <systemitem class=\"service\">swift-container-server</systemitem>, and <systemitem class=\"service\">swift-object-server</systemitem> processes which control storage of the account databases, the container databases, as well as the actual stored objects."
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-install.xml:57(para)
-msgid "Fewer storage nodes can be used initially, but a minimum of five is recommended for a production cluster."
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-install.xml:62(title)
-msgid "General installation steps"
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-install.xml:65(para)
-msgid "Create a <literal>swift</literal> user that the Object Storage Service can use to authenticate with the Identity Service. Choose a password and specify an email address for the <literal>swift</literal> user. Use the <literal>service</literal> tenant and give the user the <literal>admin</literal> role:"
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-install.xml:72(replaceable)
-msgid "swift@example.com"
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-install.xml:76(para)
-msgid "Create a service entry for the Object Storage Service:"
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-install.xml:94(para)
-msgid "Specify an API endpoint for the Object Storage Service by using the returned service ID. When you specify an endpoint, you provide URLs for the public API, internal API, and admin API. In this guide, the <literal>controller</literal> host name is used:"
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-install.xml:116(para)
-msgid "Create the configuration directory on all nodes:"
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-install.xml:120(para)
-msgid "Create <filename>/etc/swift/swift.conf</filename> on all nodes:"
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-install.xml:126(para)
-msgid "The suffix value in <filename>/etc/swift/swift.conf</filename> should be set to some random string of text to be used as a salt when hashing to determine mappings in the ring. This file must be the same on every node in the cluster!"
-msgstr ""
-
-#: ./doc/install-guide/object-storage/section_object-storage-install.xml:131(para)
-msgid "Next, set up your storage nodes and proxy node. This example uses the Identity Service for the common authentication piece."
+#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml:34(para)
+msgid "Run the following <placeholder-1/> command to download all files from the <literal>myfiles</literal> container:"
 msgstr ""
 
 #: ./doc/install-guide/object-storage/section_start-storage-node-services.xml:7(title)
@@ -5328,8 +5282,54 @@ msgstr ""
 msgid "<emphasis role=\"bold\">Permissions</emphasis>: You can install OpenStack Object Storage either as root or as a user with sudo permissions if you configure the sudoers file to enable all the permissions."
 msgstr ""
 
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:52(None)
+msgid "@@image: '../figures/swift_install_arch.png'; md5=bbda527d20235d54a95eb29279ba2680"
+msgstr ""
+
+#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:6(title)
+msgid "Example of Object Storage installation architecture"
+msgstr ""
+
+#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:9(para)
+msgid "Node: A host machine that runs one or more OpenStack Object Storage services."
+msgstr ""
+
+#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:13(para)
+msgid "Proxy node: Runs proxy services."
+msgstr ""
+
+#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:16(para)
+msgid "Storage node: Runs account, container, and object services. Contains the SQLite databases."
+msgstr ""
+
+#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:20(para)
+msgid "Ring: A set of mappings between OpenStack Object Storage data to physical devices."
+msgstr ""
+
+#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:24(para)
+msgid "Replica: A copy of an object. By default, three copies are maintained in the cluster."
+msgstr ""
+
+#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:28(para)
+msgid "Zone: A logically separate section of the cluster, related to independent failure characteristics."
+msgstr ""
+
+#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:32(para)
+msgid "Region (optional): A logically separate section of the cluster, representing distinct physical locations such as cities or countries. Similar to zones but representing physical locations of portions of the cluster rather than logical segments."
+msgstr ""
+
+#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:39(para)
+msgid "To increase reliability and performance, you can add additional proxy servers."
+msgstr ""
+
+#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:41(para)
+msgid "This document describes each storage node as a separate zone in the ring. At a minimum, five zones are recommended. A zone is a group of nodes that are as isolated as possible from other nodes (separate servers, network, power, even geography). The ring guarantees that every replica is stored in a separate zone. This diagram shows one possible configuration for a minimal installation:"
+msgstr ""
+
 #. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
-#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml:0(None)
+#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml:0(None)
 msgid "translator-credits"
 msgstr ""
 
diff --git a/doc/install-guide/locale/ja.po b/doc/install-guide/locale/ja.po
index 0c506f7255..7660b06c20 100644
--- a/doc/install-guide/locale/ja.po
+++ b/doc/install-guide/locale/ja.po
@@ -5,9 +5,9 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: OpenStack Manuals\n"
-"POT-Creation-Date: 2014-06-02 05:42+0000\n"
-"PO-Revision-Date: 2014-06-02 05:40+0000\n"
-"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
+"POT-Creation-Date: 2014-06-03 02:30+0000\n"
+"PO-Revision-Date: 2014-06-03 06:10+0000\n"
+"Last-Translator: Tomoyuki KATO <tomo@dream.daynight.jp>\n"
 "Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -15,501 +15,422 @@ msgstr ""
 "Language: ja\n"
 "Plural-Forms: nplurals=1; plural=0;\n"
 
-#: ./doc/install-guide/section_keystone-users.xml5(title)
-msgid "Define users, tenants, and roles"
-msgstr "ユーザー、プロジェクト、ロールの定義"
-
-#: ./doc/install-guide/section_keystone-users.xml7(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_keystone-install.xml79(None)
 msgid ""
-"After you install the Identity Service, set up <glossterm "
-"baseform=\"user\">users</glossterm>, <glossterm "
-"baseform=\"tenant\">tenants</glossterm>, and <glossterm "
-"baseform=\"role\">roles</glossterm> to authenticate against. These are used "
-"to allow access to services and <glossterm "
-"baseform=\"endpoint\">endpoints</glossterm>, described in the next section."
-msgstr "Identity Service をインストールした後、認証する<glossterm baseform=\"user\">ユーザー</glossterm>、<glossterm baseform=\"tenant\">プロジェクト</glossterm>、<glossterm baseform=\"role\">ロール</glossterm>をセットアップします。これらは次のセクションに記述されるサービスと<glossterm baseform=\"endpoint\">エンドポイント</glossterm>へのアクセスを許可するために使用されます。"
-
-#: ./doc/install-guide/section_keystone-users.xml26(replaceable)
-#: ./doc/install-guide/section_keystone-users.xml29(replaceable)
-#: ./doc/install-guide/section_trove-install.xml144(replaceable)
-msgid "ADMIN_TOKEN"
-msgstr "ADMIN_TOKEN"
-
-#: ./doc/install-guide/section_keystone-users.xml15(para)
-msgid ""
-"Typically, you would indicate a user and password to authenticate with the "
-"Identity Service. At this point, however, you have not created any users, so"
-" you have to use the authorization token created in an earlier step, see "
-"<xref linkend=\"keystone-install\"/> for further details. You can pass this "
-"with the <option>--os-token</option> option to the <placeholder-1/> command "
-"or set the <envar>OS_SERVICE_TOKEN</envar> environment variable. Set "
-"<envar>OS_SERVICE_TOKEN</envar>, as well as "
-"<envar>OS_SERVICE_ENDPOINT</envar> to specify where the Identity Service is "
-"running. Replace <placeholder-2/> with your authorization token."
-msgstr "一般的に Identity Service で認証するためにユーザーとパスワードを必要とします。しかしながら今のところ、何もユーザーを作成していないため、前の手順で作成した認可トークンを使用する必要があります。詳細は<xref linkend=\"keystone-install\"/>を参照してください。<option>--os-token</option> オプションを用いてこれを <placeholder-1/> コマンドに渡すことができます。または、<envar>OS_SERVICE_TOKEN</envar> 環境変数を設定します。Identity Service が動作している場所を指定するために <envar>OS_SERVICE_TOKEN</envar> だけでなく <envar>OS_SERVICE_ENDPOINT</envar> を設定します。<placeholder-2/> をお使いの認可トークンで置き換えます。"
-
-#: ./doc/install-guide/section_keystone-users.xml33(title)
-msgid "Create an administrative user"
-msgstr "管理ユーザーの作成"
-
-#: ./doc/install-guide/section_keystone-users.xml34(para)
-msgid ""
-"Follow these steps to create an administrative user, role, and tenant. You "
-"will use this account for administrative interaction with the OpenStack "
-"cloud."
-msgstr "管理ユーザー、ロール、プロジェクトを作成するために、以下の手順を実行します。OpenStack クラウドの管理操作のために、このアカウントを使用します。"
-
-#: ./doc/install-guide/section_keystone-users.xml39(para)
-msgid ""
-"By default, the Identity Service creates a special "
-"<literal>_member_</literal> role. The OpenStack dashboard automatically "
-"grants access to users with this role. You will give the "
-"<literal>admin</literal> user access to this role in addition to the "
-"<literal>admin</literal> role."
-msgstr "Identity Service は標準で特別な <literal>_member_</literal> ロールを作成します。OpenStack ダッシュボードは自動的にこのロールを持つユーザーにアクセス権を与えます。<literal>admin</literal> ユーザーのアクセス権に、このロールに加えて <literal>admin</literal> ロールを与えます。"
-
-#: ./doc/install-guide/section_keystone-users.xml47(para)
-msgid ""
-"Any role that you create must map to roles specified in the "
-"<filename>policy.json</filename> file included with each OpenStack service. "
-"The default policy file for most services grants administrative access to "
-"the <literal>admin</literal> role."
-msgstr "作成するすべてのロールは、各 OpenStack サービスに含まれる <filename>policy.json</filename> ファイルで指定されたロールにマップすべきです。多くのサービス用の標準ポリシーファイルは、管理アクセスを <literal>admin</literal> ロールに許可します。"
-
-#: ./doc/install-guide/section_keystone-users.xml55(para)
-msgid "Create the <literal>admin</literal> user:"
-msgstr "<literal>admin</literal> ユーザーを作成します。"
-
-#: ./doc/install-guide/section_keystone-users.xml58(replaceable)
-#: ./doc/install-guide/section_trove-install.xml143(replaceable)
-#: ./doc/install-guide/section_trove-install.xml172(replaceable)
-#: ./doc/install-guide/section_trove-install.xml223(replaceable)
-#: ./doc/install-guide/section_trove-install.xml229(replaceable)
-#: ./doc/install-guide/section_keystone-verify.xml25(replaceable)
-#: ./doc/install-guide/section_keystone-verify.xml35(replaceable)
-#: ./doc/install-guide/section_keystone-verify.xml49(replaceable)
-msgid "ADMIN_PASS"
-msgstr "ADMIN_PASS"
-
-#: ./doc/install-guide/section_keystone-users.xml58(replaceable)
-msgid "ADMIN_EMAIL"
-msgstr "ADMIN_EMAIL"
-
-#: ./doc/install-guide/section_keystone-users.xml59(para)
-msgid ""
-"Replace <replaceable>ADMIN_PASS</replaceable> with a secure password and "
-"replace <replaceable>ADMIN_EMAIL</replaceable> with an email address to "
-"associate with the account."
-msgstr "<replaceable>ADMIN_PASS</replaceable> を安全なパスワードに置き換え、<replaceable>ADMIN_EMAIL</replaceable> をこのアカウントに関連付ける電子メールアドレスに置き換えます。"
-
-#: ./doc/install-guide/section_keystone-users.xml66(para)
-msgid "Create the <literal>admin</literal> role:"
-msgstr "<literal>admin</literal> ロールを作成します。"
-
-#: ./doc/install-guide/section_keystone-users.xml72(para)
-msgid "Create the <literal>admin</literal> tenant:"
-msgstr "<literal>admin</literal> プロジェクトを作成します。"
-
-#: ./doc/install-guide/section_keystone-users.xml78(para)
-msgid ""
-"You must now link the <literal>admin</literal> user, "
-"<literal>admin</literal> role, and <literal>admin</literal> tenant together "
-"using the <option>user-role-add</option> option:"
-msgstr "ここで <option>user-role-add</option> オプションを使用して、<literal>admin</literal> ユーザー、<literal>admin</literal> ロール、<literal>admin</literal> プロジェクトをリンクする必要があります。"
-
-#: ./doc/install-guide/section_keystone-users.xml86(para)
-msgid ""
-"Link the <literal>admin</literal> user, <literal>_member_</literal> role, "
-"and <literal>admin</literal> tenant:"
-msgstr "<literal>admin</literal> ユーザー、<literal>_member_</literal> ロール、<literal>admin</literal> プロジェクトをリンクします。"
-
-#: ./doc/install-guide/section_keystone-users.xml94(title)
-msgid "Create a normal user"
-msgstr "一般ユーザーの作成"
-
-#: ./doc/install-guide/section_keystone-users.xml95(para)
-msgid ""
-"Follow these steps to create a normal user and tenant, and link them to the "
-"special <literal>_member_</literal> role. You will use this account for "
-"daily non-administrative interaction with the OpenStack cloud. You can also "
-"repeat this procedure to create additional cloud users with different "
-"usernames and passwords. Skip the tenant creation step when creating these "
-"users."
-msgstr "一般ユーザーとプロジェクトを作成し、それらと特別な <literal>_member_</literal> ロールをリンクするために、以下の手順を実行します。OpenStack クラウドの日々の非管理操作のために、このアカウントを使用します。別のユーザー名とパスワードを持つユーザーを作成するために、この手順を繰り返すことができます。これらのユーザーを作成するときに、プロジェクトを作成する手順を省略します。"
-
-#: ./doc/install-guide/section_keystone-users.xml104(para)
-msgid "Create the <literal>demo</literal> user:"
-msgstr "<literal>demo</literal> ユーザーを作成します。"
-
-#: ./doc/install-guide/section_keystone-users.xml107(replaceable)
-#: ./doc/install-guide/ch_clients.xml40(replaceable)
-msgid "DEMO_PASS"
-msgstr "DEMO_PASS"
-
-#: ./doc/install-guide/section_keystone-users.xml107(replaceable)
-msgid "DEMO_EMAIL"
-msgstr "DEMO_EMAIL"
-
-#: ./doc/install-guide/section_keystone-users.xml108(para)
-msgid ""
-"Replace <replaceable>DEMO_PASS</replaceable> with a secure password and "
-"replace <replaceable>DEMO_EMAIL</replaceable> with an email address to "
-"associate with the account."
-msgstr "<replaceable>DEMO_PASS</replaceable> を安全なパスワードに置き換え、<replaceable>DEMO_EMAIL</replaceable> をこのアカウントに関連付ける電子メールアドレスに置き換えます。"
-
-#: ./doc/install-guide/section_keystone-users.xml115(para)
-msgid "Create the <literal>demo</literal> tenant:"
-msgstr "<literal>demo</literal> プロジェクトを作成します。"
-
-#: ./doc/install-guide/section_keystone-users.xml120(para)
-msgid "Do not repeat this step when adding additional users."
-msgstr "別のユーザーを追加するときに、この手順を繰り返さないでください。"
-
-#: ./doc/install-guide/section_keystone-users.xml126(para)
-msgid ""
-"Link the <literal>demo</literal> user, <literal>_member_</literal> role, and"
-" <literal>demo</literal> tenant:"
-msgstr "<literal>demo</literal> ユーザー、<literal>_member_</literal> ロール、<literal>demo</literal> プロジェクトをリンクします。"
-
-#: ./doc/install-guide/section_keystone-users.xml134(title)
-msgid "Create a <literal>service</literal> tenant"
-msgstr "<literal>service</literal> プロジェクトの作成"
-
-#: ./doc/install-guide/section_keystone-users.xml135(para)
-msgid ""
-"OpenStack services also require a username, tenant, and role to access other"
-" OpenStack services. In a basic installation, OpenStack services typically "
-"share a single tenant named <literal>service</literal>."
-msgstr "OpenStack のサービスは、他の OpenStack のサービスにアクセスするために、ユーザー名、プロジェクト、ロールを必要とします。基本的なインストールでは、OpenStack のサービスは一般的に同じ <literal>service</literal> という名前のプロジェクトを共有します。"
-
-#: ./doc/install-guide/section_keystone-users.xml140(para)
-msgid ""
-"You will create additional usernames and roles under this tenant as you "
-"install and configure each service."
-msgstr "各サービスをインストールし、設定するので、このプロジェクトの下に追加のユーザー名とロールを作成します。"
-
-#: ./doc/install-guide/section_keystone-users.xml145(para)
-msgid "Create the <literal>service</literal> tenant:"
-msgstr "<literal>service</literal> プロジェクトを作成します。"
-
-#: ./doc/install-guide/section_nova-networking-initial-network.xml5(title)
-msgid "Create initial network"
-msgstr "初期ネットワークの作成"
-
-#: ./doc/install-guide/section_nova-networking-initial-network.xml6(para)
-msgid ""
-"Before launching your first instance, you must create the necessary virtual "
-"network infrastructure to which the instance will connect. This network "
-"typically provides internet access <emphasis>from</emphasis> instances. You "
-"can enable internet access <emphasis>to</emphasis> individual instances "
-"using a <glossterm>floating IP address</glossterm> and suitable "
-"<glossterm>security group</glossterm> rules. The <literal>admin</literal> "
-"tenant owns this network because it provides external network access for "
-"multiple tenants."
-msgstr "インスタンスの起動前に、インスタンスが接続するために必要な仮想ネットワークを作成する必要があります。このネットワークは、一般的にインスタンス<emphasis>から</emphasis>インターネットにアクセスできます。<glossterm baseform=\"floating IP address\">Floating IP アドレス</glossterm>と<glossterm baseform=\"security group\">セキュリティグループ</glossterm>ルールを使用して、個々のインスタンス<emphasis>へと</emphasis>インターネットからアクセス可能にできます。<literal>admin</literal> プロジェクトは、複数のプロジェクトに対して外部ネットワークを提供するため、このネットワークを所有します。"
-
-#: ./doc/install-guide/section_nova-networking-initial-network.xml15(para)
-msgid ""
-"This network shares the same <glossterm>subnet</glossterm> associated with "
-"the physical network connected to the external "
-"<glossterm>interface</glossterm> on the compute node. You should specify an "
-"exclusive slice of this subnet to prevent interference with other devices on"
-" the external network."
-msgstr "このネットワークは、コンピュートノードの外部<glossterm baseform=\"interface\">インターフェース</glossterm> に接続された物理ネットワークと関連づけられた、同じ<glossterm baseform=\"subnet\">サブネット</glossterm>を共有します。外部ネットワークの他のデバイスと競合しないよう、このサブネットの専用範囲を指定すべきです。"
-
-#: ./doc/install-guide/section_nova-networking-initial-network.xml21(para)
-#: ./doc/install-guide/section_neutron-initial-networks.xml40(para)
-#: ./doc/install-guide/section_neutron-initial-networks.xml127(para)
-msgid "Perform these commands on the controller node."
-msgstr "これらのコマンドをコントローラーノードで実行します。"
-
-#: ./doc/install-guide/section_nova-networking-initial-network.xml24(title)
-msgid "To create the network"
-msgstr "ネットワークの作成方法"
-
-#: ./doc/install-guide/section_nova-networking-initial-network.xml26(para)
-#: ./doc/install-guide/section_neutron-initial-networks.xml45(para)
-msgid "Source the <literal>admin</literal> tenant credentials:"
-msgstr "<literal>admin</literal> プロジェクトのクレデンシャルを読み込みます。"
-
-#: ./doc/install-guide/section_nova-networking-initial-network.xml30(para)
-#: ./doc/install-guide/section_neutron-initial-networks.xml49(para)
-#: ./doc/install-guide/section_neutron-initial-networks.xml136(para)
-msgid "Create the network:"
-msgstr "ネットワークを作成します。"
-
-#: ./doc/install-guide/section_nova-networking-initial-network.xml31(para)
-msgid ""
-"Replace <replaceable>NETWORK_CIDR</replaceable> with the subnet associated "
-"with the physical network."
-msgstr "<replaceable>NETWORK_CIDR</replaceable> を物理ネットワークのサブネットに置き換えます。"
-
-#: ./doc/install-guide/section_nova-networking-initial-network.xml34(replaceable)
-msgid "NETWORK_CIDR"
-msgstr "NETWORK_CIDR"
-
-#: ./doc/install-guide/section_nova-networking-initial-network.xml35(para)
-msgid ""
-"For example, using an exclusive slice of <literal>203.0.113.0/24</literal> "
-"with IP address range <literal>203.0.113.24</literal> to "
-"<literal>203.0.113.32</literal>:"
-msgstr "例えば、IP アドレス <literal>203.0.113.24</literal> ～ <literal>203.0.113.32</literal> を持つ <literal>203.0.113.0/24</literal> の専用範囲を使用する場合:"
-
-#: ./doc/install-guide/section_nova-networking-initial-network.xml42(para)
-#: ./doc/install-guide/section_launch-instance-nova.xml26(para)
-#: ./doc/install-guide/section_launch-instance-neutron.xml26(para)
-#: ./doc/install-guide/section_launch-instance-neutron.xml245(para)
-msgid "This command provides no output."
-msgstr "このコマンドは何も出力しません。"
-
-#: ./doc/install-guide/section_nova-networking-initial-network.xml46(para)
-msgid "Verify creation of the network:"
-msgstr "ネットワークの作成を検証します。"
+"@@image: 'figures/debconf-screenshots/keystone_1_admin_token.png'; "
+"md5=29a51caaf09c3d6e3f0fda73c256a17a"
+msgstr "@@image: 'figures/debconf-screenshots/keystone_1_admin_token.png'; md5=29a51caaf09c3d6e3f0fda73c256a17a"
 
 #. When image changes, this message will be marked fuzzy or untranslated for
 #. you.
 #. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-api-endpoints.xml29(None)
+#: ./doc/install-guide/section_keystone-install.xml104(None)
 msgid ""
-"@@image: 'figures/debconf-screenshots/api-endpoint_1_register_endpoint.png';"
-" md5=d534be231be4f725820a1050fbf44231"
-msgstr "@@image: 'figures/debconf-screenshots/api-endpoint_1_register_endpoint.png'; md5=d534be231be4f725820a1050fbf44231"
+"@@image: 'figures/debconf-"
+"screenshots/keystone_2_register_admin_tenant_yes_no.png'; "
+"md5=25c9a90b1df2d979aae6ce9975c7285b"
+msgstr "@@image: 'figures/debconf-screenshots/keystone_2_register_admin_tenant_yes_no.png'; md5=25c9a90b1df2d979aae6ce9975c7285b"
 
 #. When image changes, this message will be marked fuzzy or untranslated for
 #. you.
 #. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-api-endpoints.xml40(None)
+#: ./doc/install-guide/section_keystone-install.xml113(None)
 msgid ""
-"@@image: 'figures/debconf-screenshots/api-"
-"endpoint_2_keystone_server_ip.png'; md5=d2c5a5b82dd433fcf9cde6f5ac34c30e"
-msgstr "@@image: 'figures/debconf-screenshots/api-endpoint_2_keystone_server_ip.png'; md5=d2c5a5b82dd433fcf9cde6f5ac34c30e"
+"@@image: 'figures/debconf-screenshots/keystone_3_admin_user_name.png'; "
+"md5=173cf7ed13252df1425109be588b2ad6"
+msgstr "@@image: 'figures/debconf-screenshots/keystone_3_admin_user_name.png'; md5=173cf7ed13252df1425109be588b2ad6"
 
 #. When image changes, this message will be marked fuzzy or untranslated for
 #. you.
 #. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-api-endpoints.xml54(None)
+#: ./doc/install-guide/section_keystone-install.xml122(None)
 msgid ""
-"@@image: 'figures/debconf-screenshots/api-"
-"endpoint_3_keystone_authtoken.png'; md5=1f3b05ebe671f64d672ac70d246e4f39"
-msgstr "@@image: 'figures/debconf-screenshots/api-endpoint_3_keystone_authtoken.png'; md5=1f3b05ebe671f64d672ac70d246e4f39"
+"@@image: 'figures/debconf-screenshots/keystone_4_admin_user_email.png'; "
+"md5=b7f0d34350ccc0aa9ae4e766b7ac80c1"
+msgstr "@@image: 'figures/debconf-screenshots/keystone_4_admin_user_email.png'; md5=b7f0d34350ccc0aa9ae4e766b7ac80c1"
 
 #. When image changes, this message will be marked fuzzy or untranslated for
 #. you.
 #. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-api-endpoints.xml69(None)
+#: ./doc/install-guide/section_keystone-install.xml131(None)
 msgid ""
-"@@image: 'figures/debconf-screenshots/api-"
-"endpoint_4_service_endpoint_ip_address.png'; "
-"md5=6853f0ae2ef8d5fddb22c466d465de15"
-msgstr "@@image: 'figures/debconf-screenshots/api-endpoint_4_service_endpoint_ip_address.png'; md5=6853f0ae2ef8d5fddb22c466d465de15"
+"@@image: 'figures/debconf-screenshots/keystone_5_admin_user_pass.png'; "
+"md5=e6b32d8d80af90f07a66abc8fb256c84"
+msgstr "@@image: 'figures/debconf-screenshots/keystone_5_admin_user_pass.png'; md5=e6b32d8d80af90f07a66abc8fb256c84"
 
 #. When image changes, this message will be marked fuzzy or untranslated for
 #. you.
 #. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-api-endpoints.xml81(None)
+#: ./doc/install-guide/section_keystone-install.xml140(None)
 msgid ""
-"@@image: 'figures/debconf-screenshots/api-endpoint_5_region_name.png'; "
-"md5=a6bce0acf5a1cb85f161290f0cf30733"
-msgstr "@@image: 'figures/debconf-screenshots/api-endpoint_5_region_name.png'; md5=a6bce0acf5a1cb85f161290f0cf30733"
+"@@image: 'figures/debconf-"
+"screenshots/keystone_6_admin_user_pass_confirm.png'; "
+"md5=1fbf9223e4923c93030d53278d1771cc"
+msgstr "@@image: 'figures/debconf-screenshots/keystone_6_admin_user_pass_confirm.png'; md5=1fbf9223e4923c93030d53278d1771cc"
 
-#: ./doc/install-guide/section_debconf-api-endpoints.xml6(title)
-msgid "Register API endpoints"
-msgstr "API エンドポイントの登録"
-
-#: ./doc/install-guide/section_debconf-api-endpoints.xml7(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_keystone-install.xml154(None)
 msgid ""
-"All Debian packages for API services, except the <package>heat-api</package>"
-" package, register the service in the Identity Service catalog. This feature"
-" is helpful because API endpoints are difficult to remember."
-msgstr "すべての API サービス用の Debian パッケージは、<package>heat-api</package> パッケージを除き、Identity Service カタログにサービスを登録します。API エンドポイントは覚えにくいので、この機能は役に立ちます。"
+"@@image: 'figures/debconf-screenshots/keystone_7_register_endpoint.png'; "
+"md5=d24d84133bfee936267e79631a2666e6"
+msgstr "@@image: 'figures/debconf-screenshots/keystone_7_register_endpoint.png'; md5=d24d84133bfee936267e79631a2666e6"
 
-#: ./doc/install-guide/section_debconf-api-endpoints.xml12(para)
+#: ./doc/install-guide/section_keystone-install.xml6(title)
+msgid "Install the Identity Service"
+msgstr "Identity Service のインストール"
+
+#: ./doc/install-guide/section_keystone-install.xml9(para)
 msgid ""
-"The <package>heat-common</package> package and not the <package>heat-"
-"api</package> package configures the Orchestration service."
-msgstr "<package>heat-api</package> パッケージではなく、<package>heat-common</package> パッケージが Orchestration Service を設定します。"
+"Install the OpenStack Identity Service on the controller node, together with"
+" <application>python-keystoneclient</application> (which is a dependency):"
+msgstr "OpenStack Identity Service と <application>python-keystoneclient</application> (依存関係) をコントローラーノードにインストールします。"
 
-#: ./doc/install-guide/section_debconf-api-endpoints.xml16(para)
+#: ./doc/install-guide/section_keystone-install.xml17(para)
 msgid ""
-"When you install a package for an API service, you are prompted to register "
-"that service. However, after you install or upgrade the package for an API "
-"service, Debian immediately removes your response to this prompt from the "
-"<package>debconf</package> database. Consequently, you are prompted to re-"
-"register the service with the Identity Service. If you already registered "
-"the API service, respond <literal>no</literal> when you upgrade."
-msgstr "API サービス用のパッケージをインストールするとき、サービスを登録するために、プロンプトが表示されます。しかしながら、API サービス用のパッケージをインストールまたはアップグレードした後、Debian はこのプロンプトの内容を <package>debconf</package> データベースからすぐに削除します。その結果として、Identity Service でサービスを設定するためにプロンプトが表示されます。すでに API サービスを登録していれば、アップグレードするときに <literal>no</literal> と答えます。"
+"Answer to the <systemitem class=\"library\">debconf</systemitem> and "
+"<systemitem class=\"library\">dbconfig-common</systemitem> questions for "
+"setting-up the database."
+msgstr "データベースをセットアップするために <systemitem class=\"library\">debconf</systemitem> と <systemitem class=\"library\">dbconfig-common</systemitem> の質問に答えます。"
 
-#: ./doc/install-guide/section_debconf-api-endpoints.xml33(para)
-msgid "This screen registers packages in the Identity Service catalog:"
-msgstr "この画面は Identity Service カタログにパッケージを登録します。"
-
-#: ./doc/install-guide/section_debconf-api-endpoints.xml44(para)
+#: ./doc/install-guide/section_keystone-install.xml23(para)
 msgid ""
-"You are prompted for the Identity Service <literal>admin_token</literal> "
-"value. The Identity Service uses this value to register the API service. "
-"When you set up the <package>keystone</package> package, this value is "
-"configured automatically."
-msgstr "Identity Service の <literal>admin_token</literal> 値に対するプロンプトが表示されます。Identity Service が API サービスを登録するためにこの値を使用します。<package>keystone</package> パッケージをセットアップするとき、この値が自動的に設定されます。"
+"The Identity Service uses a database to store information. Specify the "
+"location of the database in the configuration file. In this guide, we use a "
+"MySQL database on the controller node with the username "
+"<literal>keystone</literal>. Replace "
+"<literal><replaceable>KEYSTONE_DBPASS</replaceable></literal> with a "
+"suitable password for the database user."
+msgstr "Identity Service は情報を保存するためにデータベースを使用します。設定ファイルでデータベースの場所を指定します。このガイドでは、コントローラーノードにユーザー名 <literal>keystone</literal> で MySQL データベースを使用します。<literal><replaceable>KEYSTONE_DBPASS</replaceable></literal> をデータベースのユーザーの適切なパスワードで置き換えます。"
 
-#: ./doc/install-guide/section_debconf-api-endpoints.xml58(para)
+#: ./doc/install-guide/section_keystone-install.xml30(replaceable)
+#: ./doc/install-guide/section_keystone-install.xml38(replaceable)
+#: ./doc/install-guide/section_keystone-install.xml57(replaceable)
+#: ./doc/install-guide/section_keystone-install.xml59(replaceable)
+msgid "KEYSTONE_DBPASS"
+msgstr "KEYSTONE_DBPASS"
+
+#: ./doc/install-guide/section_keystone-install.xml30(replaceable)
+#: ./doc/install-guide/section_keystone-install.xml38(replaceable)
+#: ./doc/install-guide/section_cinder-controller.xml44(replaceable)
+#: ./doc/install-guide/section_cinder-controller.xml47(replaceable)
+#: ./doc/install-guide/section_cinder-controller.xml83(replaceable)
+#: ./doc/install-guide/section_cinder-controller.xml85(replaceable)
+#: ./doc/install-guide/section_cinder-controller.xml101(replaceable)
+#: ./doc/install-guide/section_cinder-controller.xml102(replaceable)
+#: ./doc/install-guide/section_cinder-controller.xml120(replaceable)
+#: ./doc/install-guide/section_cinder-controller.xml153(replaceable)
+#: ./doc/install-guide/section_cinder-controller.xml154(replaceable)
+#: ./doc/install-guide/section_cinder-controller.xml155(replaceable)
+#: ./doc/install-guide/section_cinder-controller.xml163(replaceable)
+#: ./doc/install-guide/section_cinder-controller.xml164(replaceable)
+#: ./doc/install-guide/section_cinder-controller.xml165(replaceable)
+#: ./doc/install-guide/section_ceilometer-nova.xml79(replaceable)
+#: ./doc/install-guide/section_ceilometer-nova.xml85(replaceable)
+#: ./doc/install-guide/section_ceilometer-nova.xml91(replaceable)
+#: ./doc/install-guide/section_ceilometer-nova.xml107(replaceable)
+#: ./doc/install-guide/section_ceilometer-nova.xml122(replaceable)
+#: ./doc/install-guide/section_nova-controller.xml44(replaceable)
+#: ./doc/install-guide/section_nova-controller.xml59(replaceable)
+#: ./doc/install-guide/section_nova-controller.xml140(replaceable)
+#: ./doc/install-guide/section_nova-controller.xml141(replaceable)
+#: ./doc/install-guide/section_nova-controller.xml160(replaceable)
+#: ./doc/install-guide/section_nova-controller.xml177(replaceable)
+#: ./doc/install-guide/section_nova-controller.xml178(replaceable)
+#: ./doc/install-guide/section_nova-controller.xml179(replaceable)
+#: ./doc/install-guide/section_basics-networking-neutron.xml277(replaceable)
+#: ./doc/install-guide/section_basics-networking-neutron.xml321(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml143(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml145(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml179(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml180(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml194(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml205(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml214(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml232(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml242(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml253(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml258(replaceable)
+#: ./doc/install-guide/section_ceilometer-install.xml102(replaceable)
+#: ./doc/install-guide/section_ceilometer-install.xml111(replaceable)
+#: ./doc/install-guide/section_ceilometer-install.xml118(replaceable)
+#: ./doc/install-guide/section_ceilometer-install.xml145(replaceable)
+#: ./doc/install-guide/section_ceilometer-install.xml148(replaceable)
+#: ./doc/install-guide/section_ceilometer-install.xml196(replaceable)
+#: ./doc/install-guide/section_ceilometer-install.xml204(replaceable)
+#: ./doc/install-guide/section_ceilometer-install.xml208(replaceable)
+#: ./doc/install-guide/section_ceilometer-install.xml223(replaceable)
+#: ./doc/install-guide/section_ceilometer-install.xml230(replaceable)
+#: ./doc/install-guide/section_ceilometer-install.xml244(replaceable)
+#: ./doc/install-guide/section_ceilometer-install.xml245(replaceable)
+#: ./doc/install-guide/section_ceilometer-install.xml246(replaceable)
+#: ./doc/install-guide/section_basics-ntp.xml72(replaceable)
+#: ./doc/install-guide/ch_clients.xml42(replaceable)
+#: ./doc/install-guide/section_glance-install.xml55(replaceable)
+#: ./doc/install-guide/section_glance-install.xml57(replaceable)
+#: ./doc/install-guide/section_glance-install.xml65(replaceable)
+#: ./doc/install-guide/section_glance-install.xml74(replaceable)
+#: ./doc/install-guide/section_glance-install.xml89(replaceable)
+#: ./doc/install-guide/section_glance-install.xml102(replaceable)
+#: ./doc/install-guide/section_glance-install.xml147(replaceable)
+#: ./doc/install-guide/section_glance-install.xml149(replaceable)
+#: ./doc/install-guide/section_glance-install.xml163(replaceable)
+#: ./doc/install-guide/section_glance-install.xml165(replaceable)
+#: ./doc/install-guide/section_glance-install.xml188(replaceable)
+#: ./doc/install-guide/section_glance-install.xml189(replaceable)
+#: ./doc/install-guide/section_glance-install.xml213(replaceable)
+#: ./doc/install-guide/section_glance-install.xml214(replaceable)
+#: ./doc/install-guide/section_glance-install.xml215(replaceable)
+#: ./doc/install-guide/section_cinder-node.xml113(replaceable)
+#: ./doc/install-guide/section_cinder-node.xml115(replaceable)
+#: ./doc/install-guide/section_cinder-node.xml131(replaceable)
+#: ./doc/install-guide/section_cinder-node.xml132(replaceable)
+#: ./doc/install-guide/section_cinder-node.xml150(replaceable)
+#: ./doc/install-guide/section_cinder-node.xml161(replaceable)
+#: ./doc/install-guide/section_cinder-node.xml170(replaceable)
+#: ./doc/install-guide/section_cinder-node.xml183(replaceable)
+#: ./doc/install-guide/section_cinder-node.xml186(replaceable)
+#: ./doc/install-guide/section_cinder-node.xml202(replaceable)
+#: ./doc/install-guide/section_cinder-node.xml205(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml62(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml64(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml94(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml95(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml112(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml123(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml138(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml294(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml304(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml328(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml333(replaceable)
+#: ./doc/install-guide/section_basics-networking-nova.xml202(replaceable)
+#: ./doc/install-guide/section_nova-compute.xml74(replaceable)
+#: ./doc/install-guide/section_nova-compute.xml75(replaceable)
+#: ./doc/install-guide/section_nova-compute.xml93(replaceable)
+#: ./doc/install-guide/section_nova-compute.xml94(replaceable)
+#: ./doc/install-guide/section_nova-compute.xml106(replaceable)
+#: ./doc/install-guide/section_nova-compute.xml131(replaceable)
+#: ./doc/install-guide/section_nova-compute.xml143(replaceable)
+#: ./doc/install-guide/section_nova-compute.xml151(replaceable)
+#: ./doc/install-guide/section_nova-compute.xml154(replaceable)
+#: ./doc/install-guide/section_trove-install.xml74(replaceable)
+#: ./doc/install-guide/section_trove-install.xml75(replaceable)
+#: ./doc/install-guide/section_trove-install.xml76(replaceable)
+#: ./doc/install-guide/section_trove-install.xml77(replaceable)
+#: ./doc/install-guide/section_trove-install.xml78(replaceable)
+#: ./doc/install-guide/section_trove-install.xml79(replaceable)
+#: ./doc/install-guide/section_trove-install.xml92(replaceable)
+#: ./doc/install-guide/section_trove-install.xml94(replaceable)
+#: ./doc/install-guide/section_trove-install.xml96(replaceable)
+#: ./doc/install-guide/section_trove-install.xml119(replaceable)
+#: ./doc/install-guide/section_trove-install.xml121(replaceable)
+#: ./doc/install-guide/section_trove-install.xml123(replaceable)
+#: ./doc/install-guide/section_trove-install.xml139(replaceable)
+#: ./doc/install-guide/section_trove-install.xml220(replaceable)
+#: ./doc/install-guide/section_trove-install.xml225(replaceable)
+#: ./doc/install-guide/section_trove-install.xml227(replaceable)
+#: ./doc/install-guide/section_trove-install.xml231(replaceable)
+#: ./doc/install-guide/section_trove-install.xml252(replaceable)
+#: ./doc/install-guide/section_trove-install.xml253(replaceable)
+#: ./doc/install-guide/section_trove-install.xml254(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml49(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml50(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml51(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml113(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml126(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml139(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml141(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml171(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml172(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml200(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml215(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml228(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml236(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml255(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml259(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml376(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml386(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml410(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml415(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml55(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml56(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml57(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml81(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml98(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml100(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml133(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml134(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml161(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml179(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml229(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml239(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml250(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml255(replaceable)
+#: ./doc/install-guide/section_heat-install.xml40(replaceable)
+#: ./doc/install-guide/section_heat-install.xml46(replaceable)
+#: ./doc/install-guide/section_heat-install.xml92(replaceable)
+#: ./doc/install-guide/section_heat-install.xml95(replaceable)
+#: ./doc/install-guide/section_heat-install.xml113(replaceable)
+#: ./doc/install-guide/section_heat-install.xml116(replaceable)
+#: ./doc/install-guide/section_heat-install.xml122(replaceable)
+#: ./doc/install-guide/section_heat-install.xml133(replaceable)
+#: ./doc/install-guide/section_heat-install.xml134(replaceable)
+#: ./doc/install-guide/section_heat-install.xml135(replaceable)
+#: ./doc/install-guide/section_heat-install.xml140(replaceable)
+#: ./doc/install-guide/section_heat-install.xml141(replaceable)
+#: ./doc/install-guide/section_heat-install.xml142(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml65(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml67(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml97(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml98(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml115(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml126(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml141(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml269(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml279(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml300(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml305(replaceable)
+#: ./doc/install-guide/section_ceilometer-glance.xml17(replaceable)
+#: ./doc/install-guide/section_ceilometer-glance.xml23(replaceable)
+#: ./doc/install-guide/section_keystone-services.xml47(replaceable)
+#: ./doc/install-guide/section_keystone-services.xml48(replaceable)
+#: ./doc/install-guide/section_keystone-services.xml49(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml97(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml99(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml130(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml131(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml145(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml156(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml165(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml389(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml394(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml399(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml409(replaceable)
+#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml82(replaceable)
+#: ./doc/install-guide/object-storage/section_object-storage-install.xml101(replaceable)
+#: ./doc/install-guide/object-storage/section_object-storage-install.xml102(replaceable)
+#: ./doc/install-guide/object-storage/section_object-storage-install.xml103(replaceable)
+msgid "controller"
+msgstr "controller"
+
+#: ./doc/install-guide/section_keystone-install.xml31(para)
 msgid ""
-"This screen configures the IP addresses for the service. The configuration "
-"script automatically detects the IP address used by the interface that is "
-"connected to the default route (<code>/sbin/route</code> and "
-"<code>/sbin/ip</code>)."
-msgstr "この画面はサービスの IP アドレスを設定します。設定スクリプトは自動的に、デフォルトルートに接続されているインターフェースにより使用されている IP アドレスを検出します (<code>/sbin/route</code> と <code>/sbin/ip</code>)。"
+"Edit <filename>/etc/keystone/keystone.conf</filename> and change the "
+"<literal>[database]</literal> section:"
+msgstr "<filename>/etc/keystone/keystone.conf</filename> を編集し、<literal>[database]</literal> セクションを変更します。"
 
-#: ./doc/install-guide/section_debconf-api-endpoints.xml62(para)
+#: ./doc/install-guide/section_keystone-install.xml44(para)
 msgid ""
-"Unless you have a unique set up for your network, press "
-"<keycap>ENTER</keycap>."
-msgstr "お使いのネットワーク用に一意なセットアップをする必要がなければ、<keycap>ENTER</keycap> を押します。"
+"By default, the Ubuntu packages create a SQLite database. Delete the "
+"<filename>keystone.db</filename> file created in the "
+"<filename>/var/lib/keystone/</filename> directory so that it does not get "
+"used by mistake:"
+msgstr "Ubuntu パッケージはデフォルトで SQLite データベースを作成します。誤って使用されないように、<filename>/var/lib/keystone/</filename> ディレクトリに作成された <filename>keystone.db</filename> ファイルを削除します。"
 
-#: ./doc/install-guide/section_debconf-api-endpoints.xml73(para)
+#: ./doc/install-guide/section_keystone-install.xml51(para)
 msgid ""
-"This screen configures the region name for the service. For example, <code"
-">us-east-coast</code> or <code>europe-paris</code>."
-msgstr "この画面はサービス用のリージョン名を設定します。例えば、<code>us-east-coast</code> や <code>europe-paris</code> です。"
+"Use the password that you set previously to log in as root. Create a "
+"<literal>keystone</literal> database user:"
+msgstr "root としてログインするために、前に設定したパスワードを使用します。<literal>keystone</literal> データベースユーザーを作成します。"
 
-#: ./doc/install-guide/ch_glance.xml6(title)
-msgid "Add the Image Service"
-msgstr "Image Service の追加"
+#: ./doc/install-guide/section_keystone-install.xml63(para)
+msgid "Create the database tables for the Identity Service:"
+msgstr "Image Service 用のデータベーステーブルを作成します。"
 
-#: ./doc/install-guide/ch_glance.xml7(para)
+#: ./doc/install-guide/section_keystone-install.xml67(para)
 msgid ""
-"The OpenStack Image Service (glance) enables users to discover, register, "
-"and retrieve virtual machine images. It offers a <glossterm "
-"baseform=\"RESTful\">REST</glossterm> API that enables you to query virtual "
-"machine image metadata and retrieve an actual image. You can store virtual "
-"machine images made available through the Image Service in a variety of "
-"locations, from simple file systems to object-storage systems like OpenStack"
-" Object Storage."
-msgstr "OpenStack Image Service (glance) により、ユーザーが仮想マシンイメージを検索、登録、取得できるようになります。仮想マシンイメージを問い合わせ、実際のイメージを取得できるよう、<glossterm baseform=\"RESTful\">REST</glossterm> API を提供します。Image Service 経由で利用可能な仮想マシンイメージは、単なるファイルシステムから OpenStack Object Storage のようなオブジェクトストレージシステムまで、さまざまな場所に保存できます。"
+"Define an authorization token to use as a shared secret between the Identity"
+" Service and other OpenStack services. Respond to the "
+"<package>debconf</package> prompt with the value in the "
+"<code>admin_token</code> directive in the <filename>keystone.conf</filename>"
+" file. Use the <placeholder-1/> command to generate this password."
+msgstr "Identity Service と他の OpenStack サービスの間で共有するシークレットとして使用する認可トークンを定義します。<package>debconf</package> プロンプトで <filename>keystone.conf</filename> ファイルの <code>admin_token</code> ディレクティブにある値を答えます。このパスワードを生成するために <placeholder-1/> コマンドを使用します。"
 
-#: ./doc/install-guide/ch_glance.xml15(para)
+#: ./doc/install-guide/section_keystone-install.xml83(para)
 msgid ""
-"For simplicity, this guide describes configuring the Image Service to use "
-"the <literal>file</literal> back end, which uploads and stores in a "
-"directory on the controller node hosting the Image Service. By default, this"
-" directory is <filename>/var/lib/glance/images/</filename>."
-msgstr ""
+"Later, you can verify that the "
+"<filename>/etc/keystone/keystone.conf</filename> file contains the password "
+"you have set using <package>debconf</package>: <placeholder-1/>"
+msgstr "後から、<filename>/etc/keystone/keystone.conf</filename> ファイルが <package>debconf</package> を使用して設定したパスワードを含んでいることを検証できます。 <placeholder-1/>"
 
-#: ./doc/install-guide/ch_glance.xml20(para)
+#: ./doc/install-guide/section_keystone-install.xml91(para)
 msgid ""
-"Before you proceed, ensure that the controller node has at least several "
-"gigabytes of space available in this directory."
-msgstr ""
+"If you omit a password (for example by pressing Enter at the "
+"<package>debconf</package> prompt, or installing Keystone using the Debconf "
+"non-interactive mode) the package generates a random "
+"<literal>ADMIN_TOKEN</literal> value."
+msgstr "パスワードを省略した場合 (例えば、<package>debconf</package> プロンプトに単に Enter を押した場合や debconf の非対話モードを使用して Keystone をインストールした場合)、パッケージがランダムな <literal>ADMIN_TOKEN</literal> 値を生成します。"
 
-#: ./doc/install-guide/ch_glance.xml22(para)
+#: ./doc/install-guide/section_keystone-install.xml97(para)
+msgid "Respond to the prompts to create an administrative tenant:"
+msgstr "管理プロジェクトを作成するためにプロンプトに答えます。"
+
+#: ./doc/install-guide/section_keystone-install.xml146(para)
 msgid ""
-"For information on requirements for other back ends, see <link "
-"href=\"http://docs.openstack.org/trunk/config-reference/content"
-"/ch_configuring-openstack-image-service.html\"><citetitle>Configuration "
-"Reference</citetitle></link>."
-msgstr ""
+"If this is the first time you have installed the Identity Service, register "
+"the Identity Service in the service catalog:"
+msgstr "初めて Identity Service をインストールする場合、サービスカタログに Identity Service を登録します。"
 
-#: ./doc/install-guide/ch_cinder.xml6(title)
-msgid "Add the Block Storage service"
-msgstr "Block Storage Service の追加"
-
-#: ./doc/install-guide/ch_cinder.xml7(para)
+#: ./doc/install-guide/section_keystone-install.xml160(para)
 msgid ""
-"The OpenStack Block Storage service works through the interaction of a "
-"series of daemon processes named <systemitem "
-"role=\"process\">cinder-*</systemitem> that reside persistently on the host "
-"machine or machines. You can run the binaries from a single node or across "
-"multiple nodes. You can also run them on the same node as other OpenStack "
-"services. The following sections introduce Block Storage service components "
-"and concepts and show you how to configure and install the Block Storage "
-"service."
-msgstr "OpenStack Block Storage Service はホストマシンに永続的に存在する <systemitem role=\"process\">cinder-*</systemitem> という名前の一連のデーモンプロセスと通信して動作します。単一ノードや複数のノードに渡りバイナリを実行できます。他の OpenStack サービスのように同じノードで実行することもできます。以下のセクションは Block Storage Service のコンポーネントと概念について紹介し、Block Storage Service の設定方法とインストール方法を説明します。"
+"Define an authorization token to use as a shared secret between the Identity"
+" Service and other OpenStack services. Use <placeholder-1/> to generate a "
+"random token and store it in the configuration file:"
+msgstr "Identity Service と他の OpenStack サービスの間で共有するシークレットとして使用する認可トークンを定義します。ランダムなトークンを生成し、設定ファイルに保存するために <placeholder-1/> コマンドを使用します。"
 
-#: ./doc/install-guide/ch_cinder.xml20(title)
-#: ./doc/install-guide/ch_swift.xml30(title)
-#: ./doc/install-guide/ch_networking.xml37(title)
-#: ./doc/install-guide/ch_horizon.xml38(title)
-#: ./doc/install-guide/ch_ceilometer.xml18(title)
-#: ./doc/install-guide/ch_heat.xml14(title)
-msgid "Next steps"
-msgstr "次の手順"
+#: ./doc/install-guide/section_keystone-install.xml169(para)
+msgid "For SUSE Linux Enterprise use instead as first command:"
+msgstr "SUSE Linux Enterprise の場合、最初のコマンドの代わりとして以下を使用します。"
 
-#: ./doc/install-guide/ch_cinder.xml21(para)
+#: ./doc/install-guide/section_keystone-install.xml172(para)
 msgid ""
-"Your OpenStack environment now includes Block Storage. You can <link linkend"
-"=\"launch-instance\">launch an instance</link> or add more services to your "
-"environment in the following chapters."
-msgstr "OpenStack 環境に Block Storage が追加されました。<link linkend=\"launch-instance\">インスタンスの起動</link>、以降の章に記載されているサービスの環境への追加を実行できます。"
+"Edit <filename>/etc/keystone/keystone.conf</filename> and change the "
+"<literal>[DEFAULT]</literal> section, replacing ADMIN_TOKEN with the results"
+" of the command:"
+msgstr "<filename>/etc/keystone/keystone.conf</filename> を編集し、<literal>[DEFAULT]</literal> セクションを変更します。ADMIN_TOKEN をコマンドの結果で置き換えます。"
 
-#: ./doc/install-guide/section_basics-passwords.xml6(title)
-msgid "Passwords"
-msgstr "パスワード"
-
-#: ./doc/install-guide/section_basics-passwords.xml7(para)
+#: ./doc/install-guide/section_keystone-install.xml182(para)
 msgid ""
-"The various OpenStack services and the required software like the database "
-"and the messaging server have to be password protected. You use these "
-"passwords when configuring a service and then again to access the service. "
-"You have to choose a password while configuring the service and later "
-"remember to use the same password when accessing it. Optionally, you can "
-"generate random passwords with the <application>pwgen</application> program."
-" Or, to create passwords one at a time, use the output of this command "
-"repeatedly: <placeholder-1/>"
-msgstr "さまざまな OpenStack サービス、データベースやメッセージングサーバーのような必要ソフトウェアは、パスワードで保護する必要があります。サービスを設定するとき、後からサービスにアクセスするときに、これらのパスワードを使用します。サービスを設定するときにパスワードを選択する必要があります。後からサービスにアクセスするときに同じパスワードを使用するために覚えておきます。オプションとして、<application>pwgen</application> プログラムを用いてランダムなパスワードを生成できます。または、一度に 1 つのパスワードを作成するために、このコマンドを繰り返し使用します。<placeholder-1/>"
+"By default, Keystone uses PKI tokens. Create the signing keys and "
+"certificates and restrict access to the generated data:"
+msgstr "Keystone はデフォルトで PKI トークンを使用します。書名付きキーと証明書を作成し、作成されたデータへのアクセスを制限します。"
 
-#: ./doc/install-guide/section_basics-passwords.xml17(para)
+#: ./doc/install-guide/section_keystone-install.xml189(para)
 msgid ""
-"This guide uses the convention that "
-"<literal><replaceable>SERVICE_PASS</replaceable></literal> is the password "
-"to access the service <literal>SERVICE</literal> and "
-"<literal><replaceable>SERVICE_DBPASS</replaceable></literal> is the database"
-" password used by the service SERVICE to access the database."
-msgstr "このガイドは以下のとおり表記します。<literal><replaceable>SERVICE_PASS</replaceable></literal> が <literal>SERVICE</literal> にアクセスするためのパスワード、<literal><replaceable>SERVICE_DBPASS</replaceable></literal> がデータベースにアクセスするために SERVICE サービスにより使用されるデータベースのパスワードです。"
+"Configure the log directory. Edit the "
+"<filename>/etc/keystone/keystone.conf</filename> file and update the "
+"<literal>[DEFAULT]</literal> section:"
+msgstr "ログディレクトリを設定します。<filename>/etc/keystone/keystone.conf</filename> ファイルを編集し、<literal>[DEFAULT]</literal> セクションを更新します。"
 
-#: ./doc/install-guide/section_basics-passwords.xml24(para)
+#: ./doc/install-guide/section_keystone-install.xml197(para)
+msgid "Restart the Identity Service:"
+msgstr "Identity Service を再起動します。"
+
+#: ./doc/install-guide/section_keystone-install.xml201(para)
 msgid ""
-"The complete list of passwords you need to define in this guide are: <table "
-"rules=\"all\"><caption>Passwords</caption><thead><tr><th>Password "
-"name</th><th>Description</th></tr></thead><tbody><tr><td>Database password "
-"(no variable used)</td><td>Root password for the database</td></tr><tr "
-"os=\"ubuntu;opensuse;sles\"><td><literal><replaceable>RABBIT_PASS</replaceable></literal></td><td>Password"
-" of user guest of "
-"RabbitMQ</td></tr><tr><td><literal><replaceable>KEYSTONE_DBPASS</replaceable></literal></td><td>Database"
-" password of Identity "
-"service</td></tr><tr><td><literal><replaceable>DEMO_PASS</replaceable></literal></td><td>Password"
-" of user "
-"<literal>demo</literal></td></tr><tr><td><literal><replaceable>ADMIN_PASS</replaceable></literal></td><td>Password"
-" of user "
-"<literal>admin</literal></td></tr><tr><td><literal><replaceable>GLANCE_DBPASS</replaceable></literal></td><td>Database"
-" password for Image "
-"Service</td></tr><tr><td><literal><replaceable>GLANCE_PASS</replaceable></literal></td><td>Password"
-" of Image Service user "
-"<literal>glance</literal></td></tr><tr><td><literal><replaceable>NOVA_DBPASS</replaceable></literal></td><td>Database"
-" password for Compute "
-"service</td></tr><tr><td><literal><replaceable>NOVA_PASS</replaceable></literal></td><td>Password"
-" of Compute service user "
-"<literal>nova</literal></td></tr><tr><td><literal><replaceable>DASH_DBPASS</replaceable></literal></td><td>Database"
-" password for the "
-"dashboard</td></tr><tr><td><literal><replaceable>CINDER_DBPASS</replaceable></literal></td><td>Database"
-" password for the Block Storage "
-"service</td></tr><tr><td><literal><replaceable>CINDER_PASS</replaceable></literal></td><td>Password"
-" of Block Storage service user "
-"<literal>cinder</literal></td></tr><tr><td><literal><replaceable>NEUTRON_DBPASS</replaceable></literal></td><td>Database"
-" password for the Networking "
-"service</td></tr><tr><td><literal><replaceable>NEUTRON_PASS</replaceable></literal></td><td>Password"
-" of Networking service user "
-"<literal>neutron</literal></td></tr><tr><td><literal><replaceable>HEAT_DBPASS</replaceable></literal></td><td>Database"
-" password for the Orchestration "
-"service</td></tr><tr><td><literal><replaceable>HEAT_PASS</replaceable></literal></td><td>Password"
-" of Orchestration service user "
-"<literal>heat</literal></td></tr><tr><td><literal><replaceable>CEILOMETER_DBPASS</replaceable></literal></td><td>Database"
-" password for the Telemetry "
-"service</td></tr><tr><td><literal><replaceable>CEILOMETER_PASS</replaceable></literal></td><td>Password"
-" of Telemetry service user "
-"<literal>ceilometer</literal></td></tr><tr><td><literal><replaceable>TROVE_DBPASS</replaceable></literal></td><td>Database"
-" password of Database "
-"service</td></tr><tr><td><literal><replaceable>TROVE_PASS</replaceable></literal></td><td>Password"
-" of Database Service user <literal>trove</literal></td></tr></tbody></table>"
-msgstr "このガイドで定義する必要のあるパスワードの完全な一覧は以下です。 <table rules=\"all\"><caption>パスワード</caption><thead><tr><th>パスワード名</th><th>説明</th></tr></thead><tbody><tr><td>データベースパスワード (変数を使用しません)</td><td>データベースの root パスワード</td></tr><tr os=\"ubuntu;opensuse;sles\"><td><literal><replaceable>RABBIT_PASS</replaceable></literal></td><td>RabbitMQ の guest ユーザーのパスワード</td></tr><tr><td><literal><replaceable>KEYSTONE_DBPASS</replaceable></literal></td><td>Identity Service のデータベースのパスワード</td></tr><tr><td><literal><replaceable>DEMO_PASS</replaceable></literal></td><td><literal>demo</literal> ユーザーのパスワード</td></tr><tr><td><literal><replaceable>ADMIN_PASS</replaceable></literal></td><td><literal>admin</literal> ユーザーのパスワード</td></tr><tr><td><literal><replaceable>GLANCE_DBPASS</replaceable></literal></td><td>Image Service のデータベースのパスワード</td></tr><tr><td><literal><replaceable>GLANCE_PASS</replaceable></literal></td><td>Image Service の <literal>glance</literal> ユーザーのパスワード</td></tr><tr><td><literal><replaceable>NOVA_DBPASS</replaceable></literal></td><td>Compute Service のデータベースのパスワード</td></tr><tr><td><literal><replaceable>NOVA_PASS</replaceable></literal></td><td>Compute Service の <literal>nova</literal> ユーザーのパスワード</td></tr><tr><td><literal><replaceable>DASH_DBPASS</replaceable></literal></td><td>Dashboard のデータベースのパスワード</td></tr><tr><td><literal><replaceable>CINDER_DBPASS</replaceable></literal></td><td>Block Storage Service のデータベースのパスワード</td></tr><tr><td><literal><replaceable>CINDER_PASS</replaceable></literal></td><td>Block Storage Service の <literal>cinder</literal> ユーザーのパスワード</td></tr><tr><td><literal><replaceable>NEUTRON_DBPASS</replaceable></literal></td><td>Networking Service のデータベースのパスワード</td></tr><tr><td><literal><replaceable>NEUTRON_PASS</replaceable></literal></td><td>Networking Service の <literal>neutron</literal> ユーザーのパスワード</td></tr><tr><td><literal><replaceable>HEAT_DBPASS</replaceable></literal></td><td>Orchestration Service のデータベースのパスワード</td></tr><tr><td><literal><replaceable>HEAT_PASS</replaceable></literal></td><td>Orchestration Service の <literal>heat</literal> ユーザーのパスワード</td></tr><tr><td><literal><replaceable>CEILOMETER_DBPASS</replaceable></literal></td><td>Telemetry Service のデータベースのパスワード</td></tr><tr><td><literal><replaceable>CEILOMETER_PASS</replaceable></literal></td><td>Telemetry Service の <literal>ceilometer</literal> ユーザーのパスワード</td></tr><tr><td><literal><replaceable>TROVE_DBPASS</replaceable></literal></td><td>Database サービスのデータベースパスワード</td></tr><tr><td><literal><replaceable>TROVE_PASS</replaceable></literal></td><td>Database サービスのユーザー <literal>trove</literal> のパスワード</td></tr></tbody></table>"
+"Start the Identity Service and enable it to start when the system boots:"
+msgstr "Identity Service を起動し、システム起動時に起動するよう有効化します。"
+
+#: ./doc/install-guide/section_keystone-install.xml207(para)
+msgid ""
+"By default, the Identity Service stores expired tokens in the database "
+"indefinitely. While potentially useful for auditing in production "
+"environments, the accumulation of expired tokens will considerably increase "
+"database size and may decrease service performance, particularly in test "
+"environments with limited resources. We recommend configuring a periodic "
+"task using <systemitem class=\"service\">cron</systemitem> to purge expired "
+"tokens hourly."
+msgstr "Identity Service は標準で、期限切れトークンをデータベースに無期限に保存します。本番環境で監査のために有用であるかもしれませんが、期限切れトークンが蓄積すると、データベースの容量がかなり大きくなり、サービスの性能を劣化させるかもしれません。とくにリソースが限られたテスト環境で顕著かもしれません。期限切れトークンを 1 時間おきに削除するために、<systemitem class=\"service\">cron</systemitem> を使用して定期タスクを設定することを推奨します。"
+
+#: ./doc/install-guide/section_keystone-install.xml217(para)
+msgid ""
+"Run the following command to purge expired tokens every hour and log the "
+"output to <filename>/var/log/keystone/keystone-tokenflush.log</filename>:"
+msgstr "1 時間ごとに期限切れトークンを削除し、出力を <filename>/var/log/keystone/keystone-tokenflush.log</filename> に記録するために、以下のコマンドを実行します。"
 
 #: ./doc/install-guide/section_basics-database.xml6(title)
 msgid "Database"
@@ -628,6 +549,1818 @@ msgid ""
 "library:"
 msgstr "コントローラーノード以外のすべてのノードに MySQL Python ライブラリをインストールします。"
 
+#: ./doc/install-guide/section_cinder-controller.xml5(title)
+msgid "Configure a Block Storage service controller"
+msgstr "Block Storage Service コントローラーの設定"
+
+#: ./doc/install-guide/section_cinder-controller.xml7(para)
+msgid ""
+"This scenario configures OpenStack Block Storage services on the <glossterm "
+"baseform=\"controller node\">Controller node</glossterm> and assumes that a "
+"second node provides storage through the <systemitem class=\"service"
+"\">cinder-volume</systemitem> service."
+msgstr "このシナリオは、<glossterm baseform=\"controller node\">コントローラーノード</glossterm>に OpenStack Block Storage を設定します。2 番目のノードが <systemitem class=\"service\">cinder-volume</systemitem> サービス経由でストレージを提供すると仮定します。"
+
+#: ./doc/install-guide/section_cinder-controller.xml12(para)
+msgid ""
+"For instructions on how to configure the second node, see <xref linkend"
+"=\"cinder-node\"/>."
+msgstr "2 番目のノードを設定する方法は <xref linkend=\"cinder-node\"/> を参照してください。"
+
+#: ./doc/install-guide/section_cinder-controller.xml16(para)
+#: ./doc/install-guide/section_cinder-node.xml10(para)
+msgid ""
+"You can configure OpenStack to use various storage systems. This example "
+"uses LVM."
+msgstr "さまざまなストレージシステムを使用するよう OpenStack を設定できます。この例は LVM を使用します。"
+
+#: ./doc/install-guide/section_cinder-controller.xml20(para)
+msgid "Install the appropriate packages for the Block Storage service:"
+msgstr "Block Storage Service のために適切なパッケージをインストールします。"
+
+#: ./doc/install-guide/section_cinder-controller.xml27(para)
+msgid ""
+"Respond to the prompts for database management, "
+"<literal>[keystone_authtoken]</literal> settings, RabbitMQ credentials and "
+"API endpoint registration."
+msgstr "データベース管理、<literal>[keystone_authtoken]</literal> 設定、RabbitMQ クレデンシャル、API エンドポイントの登録に関するプロンプトに答えます。"
+
+#: ./doc/install-guide/section_cinder-controller.xml31(para)
+msgid "Configure Block Storage to use your database."
+msgstr "お使いのデータベースを使用するよう Block Storage を設定します。"
+
+#: ./doc/install-guide/section_cinder-controller.xml32(para)
+msgid ""
+"Run the following command to set <literal>connection</literal> option in the"
+" <literal>[database]</literal> section, which is in the "
+"<filename>/etc/cinder/cinder.conf</filename> file, replace "
+"<replaceable>CINDER_DBPASS</replaceable> with the password for the Block "
+"Storage database that you will create in a later step:"
+msgstr "<filename>/etc/cinder/cinder.conf</filename> ファイルにある、<literal>[database]</literal> セクションの <literal>connection</literal> オプションを設定するために、以下のコマンドを実行します。後の手順で作成する Block Storage データベース用のパスワードで <replaceable>CINDER_DBPASS</replaceable> を置き換えます。"
+
+#: ./doc/install-guide/section_cinder-controller.xml38(para)
+msgid ""
+"In the <filename>/etc/cinder/cinder.conf</filename> file, set the "
+"<literal>connection</literal> option in the <literal>[database]</literal> "
+"section and replace <replaceable>CINDER_DBPASS</replaceable> with the "
+"password for the Block Storage database that you will create in a later "
+"step:"
+msgstr "<filename>/etc/cinder/cinder.conf</filename> ファイルで、<literal>[database]</literal> セクションの <literal>connection</literal> オプションを設定します。後の手順で作成する Block Storage データベース用のパスワードで <replaceable>CINDER_DBPASS</replaceable> を置き換えます。"
+
+#: ./doc/install-guide/section_cinder-controller.xml44(replaceable)
+#: ./doc/install-guide/section_cinder-controller.xml47(replaceable)
+#: ./doc/install-guide/section_cinder-controller.xml59(replaceable)
+#: ./doc/install-guide/section_cinder-controller.xml61(replaceable)
+#: ./doc/install-guide/section_cinder-node.xml183(replaceable)
+#: ./doc/install-guide/section_cinder-node.xml186(replaceable)
+msgid "CINDER_DBPASS"
+msgstr "CINDER_DBPASS"
+
+#: ./doc/install-guide/section_cinder-controller.xml48(para)
+#: ./doc/install-guide/section_cinder-node.xml188(para)
+msgid ""
+"In some distributions, the <filename>/etc/cinder/cinder.conf</filename> file"
+" does not include the <literal>[database]</literal> section header. You must"
+" add this section header to the end of the file before you proceed."
+msgstr "いくつかのディストリビューションは、<filename>/etc/cinder/cinder.conf</filename> ファイルに <literal>[database]</literal> セクションヘッダーが含まれません。ここから進む前に、このセクションヘッダーをファイルの最後に追加する必要があります。"
+
+#: ./doc/install-guide/section_cinder-controller.xml54(para)
+msgid ""
+"Use the password that you set to log in as root to create a "
+"<literal>cinder</literal> database:"
+msgstr "<literal>cinder</literal> データベースを作成するために、root としてログインするために設定したパスワードを使用します。"
+
+#: ./doc/install-guide/section_cinder-controller.xml64(para)
+msgid "Create the database tables for the Block Storage service:"
+msgstr "Block Storage 用のデータベースのテーブルを作成します。"
+
+#: ./doc/install-guide/section_cinder-controller.xml69(para)
+msgid "Create a <literal>cinder</literal> user."
+msgstr "<literal>cinder</literal> ユーザーを作成します。"
+
+#: ./doc/install-guide/section_cinder-controller.xml70(para)
+msgid ""
+"The Block Storage service uses this user to authenticate with the Identity "
+"service."
+msgstr "Block Storage は、Identity で認証するために、このユーザーを使用します。"
+
+#: ./doc/install-guide/section_cinder-controller.xml72(para)
+msgid ""
+"Use the <literal>service</literal> tenant and give the user the "
+"<literal>admin</literal> role:"
+msgstr "<literal>service</literal> テナントを使用し、このユーザーに <literal>admin</literal> ロールを与えます。"
+
+#: ./doc/install-guide/section_cinder-controller.xml74(replaceable)
+#: ./doc/install-guide/section_cinder-controller.xml95(replaceable)
+#: ./doc/install-guide/section_cinder-controller.xml107(replaceable)
+#: ./doc/install-guide/section_cinder-node.xml125(replaceable)
+#: ./doc/install-guide/section_cinder-node.xml137(replaceable)
+msgid "CINDER_PASS"
+msgstr "CINDER_PASS"
+
+#: ./doc/install-guide/section_cinder-controller.xml74(replaceable)
+msgid "cinder@example.com"
+msgstr "cinder@example.com"
+
+#: ./doc/install-guide/section_cinder-controller.xml78(para)
+msgid ""
+"Edit the <filename>/etc/cinder/cinder.conf</filename> configuration file:"
+msgstr "<filename>/etc/cinder/cinder.conf</filename> 設定ファイルを編集します。"
+
+#: ./doc/install-guide/section_cinder-controller.xml96(para)
+#: ./doc/install-guide/section_cinder-node.xml126(para)
+msgid ""
+"Edit the <filename>/etc/cinder/cinder.conf</filename> configuration file and"
+" add this section for keystone credentials:"
+msgstr "<filename>/etc/cinder/cinder.conf</filename> 設定ファイルを編集し、keystone クレデンシャル用のこのセクションを追加します。"
+
+#: ./doc/install-guide/section_cinder-controller.xml110(para)
+#: ./doc/install-guide/section_cinder-controller.xml134(para)
+#: ./doc/install-guide/section_cinder-node.xml140(para)
+msgid "Configure Block Storage to use the RabbitMQ message broker."
+msgstr "Block Storage が RabbitMQ メッセージブローカーを使用するよう設定します。"
+
+#: ./doc/install-guide/section_cinder-controller.xml112(para)
+msgid ""
+"In the <literal>[DEFAULT]</literal> section in the "
+"<filename>/etc/cinder/cinder.conf</filename> file, set these configuration "
+"keys and replace <replaceable>RABBIT_PASS</replaceable> with the password "
+"you chose for RabbitMQ:"
+msgstr "<filename>/etc/cinder/cinder.conf</filename> ファイルの <literal>[DEFAULT]</literal> セクションで、これらの設定キーを設定し、<replaceable>RABBIT_PASS</replaceable> を RabbitMQ 用に選択したパスワードに置き換えます。"
+
+#: ./doc/install-guide/section_cinder-controller.xml123(replaceable)
+#: ./doc/install-guide/section_cinder-controller.xml145(replaceable)
+#: ./doc/install-guide/section_ceilometer-nova.xml76(replaceable)
+#: ./doc/install-guide/section_ceilometer-nova.xml80(replaceable)
+#: ./doc/install-guide/section_nova-controller.xml70(replaceable)
+#: ./doc/install-guide/section_nova-controller.xml78(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml198(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml207(replaceable)
+#: ./doc/install-guide/section_ceilometer-install.xml146(replaceable)
+#: ./doc/install-guide/section_ceilometer-install.xml149(replaceable)
+#: ./doc/install-guide/section_glance-install.xml90(replaceable)
+#: ./doc/install-guide/section_glance-install.xml104(replaceable)
+#: ./doc/install-guide/section_cinder-node.xml153(replaceable)
+#: ./doc/install-guide/section_cinder-node.xml174(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml116(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml139(replaceable)
+#: ./doc/install-guide/section_nova-compute.xml115(replaceable)
+#: ./doc/install-guide/section_nova-compute.xml121(replaceable)
+#: ./doc/install-guide/section_trove-install.xml105(replaceable)
+#: ./doc/install-guide/section_trove-install.xml125(replaceable)
+#: ./doc/install-guide/section_trove-install.xml127(replaceable)
+#: ./doc/install-guide/section_trove-install.xml129(replaceable)
+#: ./doc/install-guide/section_trove-install.xml221(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml193(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml216(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml153(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml180(replaceable)
+#: ./doc/install-guide/section_heat-install.xml93(replaceable)
+#: ./doc/install-guide/section_heat-install.xml96(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml119(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml142(replaceable)
+#: ./doc/install-guide/section_ceilometer-glance.xml18(replaceable)
+#: ./doc/install-guide/section_ceilometer-glance.xml24(replaceable)
+#: ./doc/install-guide/section_basics-queue.xml77(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml149(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml158(replaceable)
+msgid "RABBIT_PASS"
+msgstr "RABBIT_PASS"
+
+#: ./doc/install-guide/section_cinder-controller.xml126(para)
+#: ./doc/install-guide/section_cinder-node.xml156(para)
+msgid "Configure Block Storage to use the Qpid message broker:"
+msgstr "Qpid メッセージブローカーを使用するよう Block Storage を設定します。"
+
+#: ./doc/install-guide/section_cinder-controller.xml136(para)
+msgid ""
+"Replace <replaceable>RABBIT_PASS</replaceable> with the password you chose "
+"for RabbitMQ:"
+msgstr "<replaceable>RABBIT_PASS</replaceable> を RabbitMQ 用に選んだパスワードで置き換えます。"
+
+#: ./doc/install-guide/section_cinder-controller.xml148(para)
+msgid ""
+"Register the Block Storage service with the Identity service so that other "
+"OpenStack services can locate it:"
+msgstr "他の OpenStack サービスから使用できるように、Block Storage を Identity に登録します。"
+
+#: ./doc/install-guide/section_cinder-controller.xml158(para)
+msgid ""
+"Register a service and endpoint for version 2 of the Block Storage service "
+"API:"
+msgstr "Block Storage の API バージョン 2 用のサービスとエンドポイントを登録します。"
+
+#: ./doc/install-guide/section_cinder-controller.xml168(para)
+#: ./doc/install-guide/section_cinder-node.xml208(para)
+msgid "Restart the Block Storage services with the new settings:"
+msgstr "新しい設定を用いて Block Storage のサービスを再起動します。"
+
+#: ./doc/install-guide/section_cinder-controller.xml174(para)
+#: ./doc/install-guide/section_cinder-node.xml221(para)
+msgid ""
+"Start and configure the Block Storage services to start when the system "
+"boots:"
+msgstr "Block Storage のサービスを起動し、システム起動時に起動するよう設定します。"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml30(None)
+msgid ""
+"@@image: 'figures/debconf-screenshots/dbconfig-common_keep_admin_pass.png'; "
+"md5=01af4867c16e458306b8abd78a1fccc9"
+msgstr "@@image: 'figures/debconf-screenshots/dbconfig-common_keep_admin_pass.png'; md5=01af4867c16e458306b8abd78a1fccc9"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml39(None)
+msgid ""
+"@@image: 'figures/debconf-screenshots/dbconfig-"
+"common_used_for_remote_db.png'; md5=c6ec966bbfdee18ad87456cf4d44a56f"
+msgstr "@@image: 'figures/debconf-screenshots/dbconfig-common_used_for_remote_db.png'; md5=c6ec966bbfdee18ad87456cf4d44a56f"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml78(None)
+msgid ""
+"@@image: 'figures/debconf-screenshots/dbconfig-common_1_configure-with-"
+"dbconfig-yes-no.png'; md5=4e9d7bce27cc6c7bd68ce8622c80b60f"
+msgstr "@@image: 'figures/debconf-screenshots/dbconfig-common_1_configure-with-dbconfig-yes-no.png'; md5=4e9d7bce27cc6c7bd68ce8622c80b60f"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml87(None)
+msgid ""
+"@@image: 'figures/debconf-screenshots/dbconfig-common_2_db-types.png'; "
+"md5=a77beb7e13b487cf79716c2140f258c2"
+msgstr "@@image: 'figures/debconf-screenshots/dbconfig-common_2_db-types.png'; md5=a77beb7e13b487cf79716c2140f258c2"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml96(None)
+msgid ""
+"@@image: 'figures/debconf-screenshots/dbconfig-"
+"common_3_connection_method.png'; md5=6cc592e5dd5ea404ad7aad98b37a71f6"
+msgstr "@@image: 'figures/debconf-screenshots/dbconfig-common_3_connection_method.png'; md5=6cc592e5dd5ea404ad7aad98b37a71f6"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml105(None)
+msgid ""
+"@@image: 'figures/debconf-screenshots/dbconfig-"
+"common_4_mysql_root_password.png'; md5=873ec338742e37305583e9e692bcfdc6"
+msgstr "@@image: 'figures/debconf-screenshots/dbconfig-common_4_mysql_root_password.png'; md5=873ec338742e37305583e9e692bcfdc6"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml114(None)
+msgid ""
+"@@image: 'figures/debconf-screenshots/dbconfig-"
+"common_5_mysql_app_password.png'; md5=3651970770d05892f21d1b5741afbee6"
+msgstr "@@image: 'figures/debconf-screenshots/dbconfig-common_5_mysql_app_password.png'; md5=3651970770d05892f21d1b5741afbee6"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml123(None)
+msgid ""
+"@@image: 'figures/debconf-screenshots/dbconfig-"
+"common_6_mysql_app_password_confirm.png'; "
+"md5=060cc90aaf6f6fd5cea718064829c1b1"
+msgstr "@@image: 'figures/debconf-screenshots/dbconfig-common_6_mysql_app_password_confirm.png'; md5=060cc90aaf6f6fd5cea718064829c1b1"
+
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml6(title)
+msgid "Configure the database with dbconfig-common"
+msgstr "dbconfig-common を用いたデータベースの設定"
+
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml7(para)
+msgid ""
+"The <package>dbconfig-common</package> package provides a standard Debian "
+"interface that enables you to configure Debian database parameters. It "
+"includes localized prompts for many languages and it supports the OpenStack "
+"database back ends: SQLite, MySQL, and PostgreSQL."
+msgstr "<package>dbconfig-common</package> パッケージは、Debian のデータベースパラメーターを設定できる、標準的な Debian インターフェースを提供します。これは多くの言語に翻訳されたプロンプトを持ち、OpenStack のデータベースバックエンド SQLite、MySQL、PostgreSQL をサポートします。"
+
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml12(para)
+msgid ""
+"By default, the <package>dbconfig-common</package> package configures the "
+"OpenStack services to use SQLite3. So if you use <package>debconf</package> "
+"in non-interactive mode and without pre-seeding, the OpenStack services that"
+" you install use SQLite3."
+msgstr "<package>dbconfig-common</package> パッケージはデフォルトで、OpenStack サービスが SQLite3 を使用するよう設定します。そのため、<package>debconf</package> を非対話モードで事前シードせずに利用した場合、インストールした OpenStack サービスが SQLite3 を使用します。"
+
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml17(para)
+msgid ""
+"By default, <package>dbconfig-common</package> does not provide access to "
+"database servers over a network. If you want the <package>dbconfig-"
+"common</package> package to prompt for remote database servers that are "
+"accessed over a network and not through a UNIX socket file, reconfigure it, "
+"as follows:"
+msgstr "<package>dbconfig-common</package> はデフォルトで、ネットワーク経由でデータベースサーバーへのアクセスを提供しません。UNIX ソケットファイル経由ではなく、ネットワーク経由でアクセスさせるリモートデータベースサーバーに対して、<package>dbconfig-common</package> パッケージにプロンプトさせたい場合、以下のように再設定します。"
+
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml23(para)
+msgid ""
+"These screens appear when you re-configure the <package>dbconfig-"
+"common</package> package:"
+msgstr "これらの画面は <package>dbconfig-common</package> パッケージを再設定するときに表示されます。"
+
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml43(para)
+msgid ""
+"Unlike other <package>debconf</package> prompts, you cannot pre-seed the "
+"responses for the <package>dbconfig-common</package> prompts by using "
+"<placeholder-1/>. Instead, you must create a file in <filename>/etc"
+"/dbconfig-common</filename>. For example, you might create a keystone "
+"configuration file for <package>dbconfig-common</package> that is located in"
+" <filename>/etc/dbconfig-common/keystone.conf</filename>, as follows:"
+msgstr "他の <package>debconf</package> プロンプトと異なり、<placeholder-1/> を使用して <package>dbconfig-common</package> プロンプトに対する応答を事前シードできません。代わりに、<filename>/etc/dbconfig-common</filename> にファイルを作成する必要があります。例えば以下のように、<filename>/etc/dbconfig-common/keystone.conf</filename> にある <package>dbconfig-common</package> 用の Keystone 設定を作成することができます。"
+
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml66(para)
+msgid "After you create this file, run this command:"
+msgstr "このファイルを作成した後、このコマンドを実行します。"
+
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml68(para)
+msgid ""
+"The Identity Service is installed with MySQL as the database back end, "
+"<literal>keystonedb</literal> as database name, and the localhost socket "
+"file."
+msgstr "Identity Service は、データベースバックエンドとして MySQL、データベース名として <literal>keystonedb</literal>、ローカルホストのソケットファイルと一緒にインストールされます。"
+
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml71(para)
+msgid "The <package>cinder-common</package> package displays these screens:"
+msgstr "<package>cinder-common</package> パッケージはこれらの画面を表示します。"
+
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml127(para)
+msgid ""
+"By default in Debian, the MySQL server is only accessible from localhost "
+"using the socket file, or 127.0.0.1. To access it over network, users must "
+"edit <filename>/etc/mysql/my.cnf</filename> and edit the "
+"<literal>mysql.user</literal> table. To do so, Debian provides a helper "
+"script located in the <package>openstack-deploy</package> package. To use "
+"it, install the package and run:"
+msgstr ""
+
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml134(para)
+msgid ""
+"Alternatively, if you do not want to install this package, run this script "
+"to enable remote root access:"
+msgstr "代わりに、このパッケージをインストールしたくなければ、リモート root アクセスを有効化するために、このスクリプトを実行します。"
+
+#: ./doc/install-guide/section_debconf-dbconfig-common.xml157(para)
+msgid ""
+"You must enable remote access before you install OpenStack services on "
+"multiple nodes."
+msgstr "複数ノードに OpenStack サービスをインストールする前にリモートアクセスを有効化する必要があります。"
+
+#: ./doc/install-guide/ch_launch-instance.xml5(title)
+msgid "Launch an instance"
+msgstr "インスタンスの起動"
+
+#: ./doc/install-guide/ch_launch-instance.xml6(para)
+msgid ""
+"An instance is a VM that OpenStack provisions on a compute node. This guide "
+"shows you how to launch a minimal instance using the "
+"<glossterm>CirrOS</glossterm> image that you added to your environment in "
+"the <xref linkend=\"ch_glance\"/> chapter. In these steps, you use the "
+"command-line interface (CLI) on your controller node or any system with the "
+"appropriate OpenStack client libraries. To use the dashboard, see the <link "
+"href=\"http://docs.openstack.org/user-"
+"guide/content/ch_dashboard.html\"><citetitle>OpenStack User "
+"Guide</citetitle></link>."
+msgstr "インスタンスは、OpenStack がコンピュートノードに展開する仮想マシンです。このガイドは、<glossterm>CirrOS</glossterm> イメージを使用して、最小のインスタンスを起動する方法を示します。このイメージは、<xref linkend=\"ch_glance\"/>の章でお使いの環境に追加します。これらの手順で、コントローラーノード、または適切な OpenStack クライアントライブラリを持つシステムで CLI を使用します。ダッシュボードを使用する場合、<link href=\"http://docs.openstack.org/user-guide/content/ch_dashboard.html\"><citetitle>OpenStack User Guide</citetitle></link> を参照してください。"
+
+#: ./doc/install-guide/ch_launch-instance.xml15(para)
+msgid ""
+"Launch an instance using <link linkend=\"launch-instance-neutron\">OpenStack"
+" Networking (neutron) </link> or <link linkend=\"launch-instance-"
+"nova\">legacy networking (nova-network) </link>. For more information, see "
+"the <link href=\"http://docs.openstack.org/user-"
+"guide/content/cli_launch_instances.html\"><citetitle>OpenStack User "
+"Guide</citetitle></link>."
+msgstr "<link linkend=\"launch-instance-neutron\">OpenStack Networking (neutron) </link> または <link linkend=\"launch-instance-nova\">legacy networking (nova-network) </link> を使用して、インスタンスを起動します。詳細は <link href=\"http://docs.openstack.org/user-guide/content/cli_launch_instances.html\"><citetitle>OpenStack User Guide</citetitle></link> を参照してください。"
+
+#: ./doc/install-guide/ch_launch-instance.xml25(para)
+msgid ""
+"These steps reference example components created in previous chapters. You "
+"must adjust certain values such as IP addresses to match your environment."
+msgstr "これらの手順は、ここまでの章で作成したコンポーネント例を参照します。お使いの環境に合わせるために、IP アドレスなどの具体的な値を調整する必要があります。"
+
+#: ./doc/install-guide/section_ceilometer-swift.xml6(title)
+msgid "Configure the Object Storage service for Telemetry"
+msgstr "Telemetry 用 Object Storage Service の設定"
+
+#: ./doc/install-guide/section_ceilometer-swift.xml9(para)
+msgid ""
+"To retrieve object store statistics, the Telemetry service needs access to "
+"Object Storage with the <literal>ResellerAdmin</literal> role. Give this "
+"role to your <literal>os_username</literal> user for the "
+"<literal>os_tenant_name</literal> tenant:"
+msgstr "オブジェクトストアの統計情報を取得するためには、Telemetry Service が <literal>ResellerAdmin</literal> ロールで Object Storage にアクセスする必要があります。このロールを <literal>os_tenant_name</literal> プロジェクトの <literal>os_username</literal> ユーザーに与えます。"
+
+#: ./doc/install-guide/section_ceilometer-swift.xml23(replaceable)
+msgid "462fa46c13fd4798a95a3bfbe27b5e54"
+msgstr "462fa46c13fd4798a95a3bfbe27b5e54"
+
+#: ./doc/install-guide/section_ceilometer-swift.xml26(para)
+msgid ""
+"You must also add the Telemetry middleware to Object Storage to handle "
+"incoming and outgoing traffic. Add these lines to the <filename>/etc/swift"
+"/proxy-server.conf</filename> file:"
+msgstr "入力通信と出力通信を処理するために、Telemetry ミドルウェアを Object Storage に追加する必要もあります。これらの行を <filename>/etc/swift/proxy-server.conf</filename> ファイルに追加します。"
+
+#: ./doc/install-guide/section_ceilometer-swift.xml35(para)
+msgid ""
+"Add <literal>ceilometer</literal> to the <literal>pipeline</literal> "
+"parameter of that same file:"
+msgstr "<literal>ceilometer</literal> を同じファイルの <literal>pipeline</literal> パラメーターに追加します。"
+
+#: ./doc/install-guide/section_ceilometer-swift.xml41(para)
+#: ./doc/install-guide/section_ceilometer-nova.xml137(para)
+#: ./doc/install-guide/section_heat-install.xml180(para)
+msgid "Restart the service with its new settings:"
+msgstr "新しい設定を用いてサービスを再起動します。"
+
+#: ./doc/install-guide/section_keystone-users.xml5(title)
+msgid "Define users, tenants, and roles"
+msgstr "ユーザー、プロジェクト、ロールの定義"
+
+#: ./doc/install-guide/section_keystone-users.xml7(para)
+msgid ""
+"After you install the Identity Service, set up <glossterm "
+"baseform=\"user\">users</glossterm>, <glossterm "
+"baseform=\"tenant\">tenants</glossterm>, and <glossterm "
+"baseform=\"role\">roles</glossterm> to authenticate against. These are used "
+"to allow access to services and <glossterm "
+"baseform=\"endpoint\">endpoints</glossterm>, described in the next section."
+msgstr "Identity Service をインストールした後、認証する<glossterm baseform=\"user\">ユーザー</glossterm>、<glossterm baseform=\"tenant\">プロジェクト</glossterm>、<glossterm baseform=\"role\">ロール</glossterm>をセットアップします。これらは次のセクションに記述されるサービスと<glossterm baseform=\"endpoint\">エンドポイント</glossterm>へのアクセスを許可するために使用されます。"
+
+#: ./doc/install-guide/section_keystone-users.xml26(replaceable)
+#: ./doc/install-guide/section_keystone-users.xml29(replaceable)
+#: ./doc/install-guide/section_trove-install.xml144(replaceable)
+msgid "ADMIN_TOKEN"
+msgstr "ADMIN_TOKEN"
+
+#: ./doc/install-guide/section_keystone-users.xml15(para)
+msgid ""
+"Typically, you would indicate a user and password to authenticate with the "
+"Identity Service. At this point, however, you have not created any users, so"
+" you have to use the authorization token created in an earlier step, see "
+"<xref linkend=\"keystone-install\"/> for further details. You can pass this "
+"with the <option>--os-token</option> option to the <placeholder-1/> command "
+"or set the <envar>OS_SERVICE_TOKEN</envar> environment variable. Set "
+"<envar>OS_SERVICE_TOKEN</envar>, as well as "
+"<envar>OS_SERVICE_ENDPOINT</envar> to specify where the Identity Service is "
+"running. Replace <placeholder-2/> with your authorization token."
+msgstr "一般的に Identity Service で認証するためにユーザーとパスワードを必要とします。しかしながら今のところ、何もユーザーを作成していないため、前の手順で作成した認可トークンを使用する必要があります。詳細は<xref linkend=\"keystone-install\"/>を参照してください。<option>--os-token</option> オプションを用いてこれを <placeholder-1/> コマンドに渡すことができます。または、<envar>OS_SERVICE_TOKEN</envar> 環境変数を設定します。Identity Service が動作している場所を指定するために <envar>OS_SERVICE_TOKEN</envar> だけでなく <envar>OS_SERVICE_ENDPOINT</envar> を設定します。<placeholder-2/> をお使いの認可トークンで置き換えます。"
+
+#: ./doc/install-guide/section_keystone-users.xml33(title)
+msgid "Create an administrative user"
+msgstr "管理ユーザーの作成"
+
+#: ./doc/install-guide/section_keystone-users.xml34(para)
+msgid ""
+"Follow these steps to create an administrative user, role, and tenant. You "
+"will use this account for administrative interaction with the OpenStack "
+"cloud."
+msgstr "管理ユーザー、ロール、プロジェクトを作成するために、以下の手順を実行します。OpenStack クラウドの管理操作のために、このアカウントを使用します。"
+
+#: ./doc/install-guide/section_keystone-users.xml39(para)
+msgid ""
+"By default, the Identity Service creates a special "
+"<literal>_member_</literal> role. The OpenStack dashboard automatically "
+"grants access to users with this role. You will give the "
+"<literal>admin</literal> user access to this role in addition to the "
+"<literal>admin</literal> role."
+msgstr "Identity Service は標準で特別な <literal>_member_</literal> ロールを作成します。OpenStack ダッシュボードは自動的にこのロールを持つユーザーにアクセス権を与えます。<literal>admin</literal> ユーザーのアクセス権に、このロールに加えて <literal>admin</literal> ロールを与えます。"
+
+#: ./doc/install-guide/section_keystone-users.xml47(para)
+msgid ""
+"Any role that you create must map to roles specified in the "
+"<filename>policy.json</filename> file included with each OpenStack service. "
+"The default policy file for most services grants administrative access to "
+"the <literal>admin</literal> role."
+msgstr "作成するすべてのロールは、各 OpenStack サービスに含まれる <filename>policy.json</filename> ファイルで指定されたロールにマップすべきです。多くのサービス用の標準ポリシーファイルは、管理アクセスを <literal>admin</literal> ロールに許可します。"
+
+#: ./doc/install-guide/section_keystone-users.xml55(para)
+msgid "Create the <literal>admin</literal> user:"
+msgstr "<literal>admin</literal> ユーザーを作成します。"
+
+#: ./doc/install-guide/section_keystone-users.xml58(replaceable)
+#: ./doc/install-guide/section_keystone-verify.xml25(replaceable)
+#: ./doc/install-guide/section_keystone-verify.xml35(replaceable)
+#: ./doc/install-guide/section_keystone-verify.xml49(replaceable)
+#: ./doc/install-guide/section_trove-install.xml143(replaceable)
+#: ./doc/install-guide/section_trove-install.xml172(replaceable)
+#: ./doc/install-guide/section_trove-install.xml223(replaceable)
+#: ./doc/install-guide/section_trove-install.xml229(replaceable)
+msgid "ADMIN_PASS"
+msgstr "ADMIN_PASS"
+
+#: ./doc/install-guide/section_keystone-users.xml58(replaceable)
+msgid "ADMIN_EMAIL"
+msgstr "ADMIN_EMAIL"
+
+#: ./doc/install-guide/section_keystone-users.xml59(para)
+msgid ""
+"Replace <replaceable>ADMIN_PASS</replaceable> with a secure password and "
+"replace <replaceable>ADMIN_EMAIL</replaceable> with an email address to "
+"associate with the account."
+msgstr "<replaceable>ADMIN_PASS</replaceable> を安全なパスワードに置き換え、<replaceable>ADMIN_EMAIL</replaceable> をこのアカウントに関連付ける電子メールアドレスに置き換えます。"
+
+#: ./doc/install-guide/section_keystone-users.xml66(para)
+msgid "Create the <literal>admin</literal> role:"
+msgstr "<literal>admin</literal> ロールを作成します。"
+
+#: ./doc/install-guide/section_keystone-users.xml72(para)
+msgid "Create the <literal>admin</literal> tenant:"
+msgstr "<literal>admin</literal> プロジェクトを作成します。"
+
+#: ./doc/install-guide/section_keystone-users.xml78(para)
+msgid ""
+"You must now link the <literal>admin</literal> user, "
+"<literal>admin</literal> role, and <literal>admin</literal> tenant together "
+"using the <option>user-role-add</option> option:"
+msgstr "ここで <option>user-role-add</option> オプションを使用して、<literal>admin</literal> ユーザー、<literal>admin</literal> ロール、<literal>admin</literal> プロジェクトをリンクする必要があります。"
+
+#: ./doc/install-guide/section_keystone-users.xml86(para)
+msgid ""
+"Link the <literal>admin</literal> user, <literal>_member_</literal> role, "
+"and <literal>admin</literal> tenant:"
+msgstr "<literal>admin</literal> ユーザー、<literal>_member_</literal> ロール、<literal>admin</literal> プロジェクトをリンクします。"
+
+#: ./doc/install-guide/section_keystone-users.xml94(title)
+msgid "Create a normal user"
+msgstr "一般ユーザーの作成"
+
+#: ./doc/install-guide/section_keystone-users.xml95(para)
+msgid ""
+"Follow these steps to create a normal user and tenant, and link them to the "
+"special <literal>_member_</literal> role. You will use this account for "
+"daily non-administrative interaction with the OpenStack cloud. You can also "
+"repeat this procedure to create additional cloud users with different "
+"usernames and passwords. Skip the tenant creation step when creating these "
+"users."
+msgstr "一般ユーザーとプロジェクトを作成し、それらと特別な <literal>_member_</literal> ロールをリンクするために、以下の手順を実行します。OpenStack クラウドの日々の非管理操作のために、このアカウントを使用します。別のユーザー名とパスワードを持つユーザーを作成するために、この手順を繰り返すことができます。これらのユーザーを作成するときに、プロジェクトを作成する手順を省略します。"
+
+#: ./doc/install-guide/section_keystone-users.xml104(para)
+msgid "Create the <literal>demo</literal> user:"
+msgstr "<literal>demo</literal> ユーザーを作成します。"
+
+#: ./doc/install-guide/section_keystone-users.xml107(replaceable)
+#: ./doc/install-guide/ch_clients.xml40(replaceable)
+msgid "DEMO_PASS"
+msgstr "DEMO_PASS"
+
+#: ./doc/install-guide/section_keystone-users.xml107(replaceable)
+msgid "DEMO_EMAIL"
+msgstr "DEMO_EMAIL"
+
+#: ./doc/install-guide/section_keystone-users.xml108(para)
+msgid ""
+"Replace <replaceable>DEMO_PASS</replaceable> with a secure password and "
+"replace <replaceable>DEMO_EMAIL</replaceable> with an email address to "
+"associate with the account."
+msgstr "<replaceable>DEMO_PASS</replaceable> を安全なパスワードに置き換え、<replaceable>DEMO_EMAIL</replaceable> をこのアカウントに関連付ける電子メールアドレスに置き換えます。"
+
+#: ./doc/install-guide/section_keystone-users.xml115(para)
+msgid "Create the <literal>demo</literal> tenant:"
+msgstr "<literal>demo</literal> プロジェクトを作成します。"
+
+#: ./doc/install-guide/section_keystone-users.xml120(para)
+msgid "Do not repeat this step when adding additional users."
+msgstr "別のユーザーを追加するときに、この手順を繰り返さないでください。"
+
+#: ./doc/install-guide/section_keystone-users.xml126(para)
+msgid ""
+"Link the <literal>demo</literal> user, <literal>_member_</literal> role, and"
+" <literal>demo</literal> tenant:"
+msgstr "<literal>demo</literal> ユーザー、<literal>_member_</literal> ロール、<literal>demo</literal> プロジェクトをリンクします。"
+
+#: ./doc/install-guide/section_keystone-users.xml134(title)
+msgid "Create a <literal>service</literal> tenant"
+msgstr "<literal>service</literal> プロジェクトの作成"
+
+#: ./doc/install-guide/section_keystone-users.xml135(para)
+msgid ""
+"OpenStack services also require a username, tenant, and role to access other"
+" OpenStack services. In a basic installation, OpenStack services typically "
+"share a single tenant named <literal>service</literal>."
+msgstr "OpenStack のサービスは、他の OpenStack のサービスにアクセスするために、ユーザー名、プロジェクト、ロールを必要とします。基本的なインストールでは、OpenStack のサービスは一般的に同じ <literal>service</literal> という名前のプロジェクトを共有します。"
+
+#: ./doc/install-guide/section_keystone-users.xml140(para)
+msgid ""
+"You will create additional usernames and roles under this tenant as you "
+"install and configure each service."
+msgstr "各サービスをインストールし、設定するので、このプロジェクトの下に追加のユーザー名とロールを作成します。"
+
+#: ./doc/install-guide/section_keystone-users.xml145(para)
+msgid "Create the <literal>service</literal> tenant:"
+msgstr "<literal>service</literal> プロジェクトを作成します。"
+
+#: ./doc/install-guide/section_ceilometer-nova.xml7(title)
+msgid "Install the Compute agent for Telemetry"
+msgstr "Telemetry 用 Compute エージェントのインストール"
+
+#: ./doc/install-guide/section_ceilometer-nova.xml9(para)
+msgid ""
+"Telemetry provides an API service that provides a collector and a range of "
+"disparate agents. This procedure details how to install the agent that runs "
+"on the compute node."
+msgstr "Telemetry は情報収集機能とさまざまな種類のエージェントを提供する API サービスを提供します。この手順はコンピュートノードで実行するエージェントをインストールする方法を詳細に説明します。"
+
+#: ./doc/install-guide/section_ceilometer-nova.xml14(para)
+msgid "Install the Telemetry service on the compute node:"
+msgstr "コンピュートノードに Telemetry Service をインストールします。"
+
+#: ./doc/install-guide/section_ceilometer-nova.xml20(para)
+msgid ""
+"Set the following options in the <filename>/etc/nova/nova.conf</filename> "
+"file:"
+msgstr "<filename>/etc/nova/nova.conf</filename> ファイルに以下のオプションを設定します。"
+
+#: ./doc/install-guide/section_ceilometer-nova.xml30(para)
+msgid ""
+"The <option>notification_driver</option> option is a multi valued option, "
+"which <application>openstack-config</application> cannot set properly. See "
+"<xref linkend=\"basics-packages\"/>."
+msgstr "<option>notification_driver</option> オプションは複数の値を持つオプションです。<application>openstack-config</application> はこれを正しく設定できません。<xref linkend=\"basics-packages\"/>を参照してください。"
+
+#: ./doc/install-guide/section_ceilometer-nova.xml36(para)
+msgid ""
+"Edit the <filename>/etc/nova/nova.conf</filename> file and add the following"
+" lines to the <literal>[DEFAULT]</literal> section:"
+msgstr "<filename>/etc/nova/nova.conf</filename> ファイルを編集し、<literal>[DEFAULT]</literal> セクションに以下の行を追加します。"
+
+#: ./doc/install-guide/section_ceilometer-nova.xml53(para)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml378(para)
+#: ./doc/install-guide/section_nova-compute.xml208(para)
+msgid "Restart the Compute service:"
+msgstr "Compute Service を再起動します。"
+
+#: ./doc/install-guide/section_ceilometer-nova.xml58(para)
+msgid ""
+"You must set the secret key that you defined previously. The Telemetry "
+"service nodes share this key as a shared secret:"
+msgstr "前に設定したシークレットキーを設定する必要があります。Telemetry Service ノードは共有シークレットとしてこのキーを共有します。"
+
+#: ./doc/install-guide/section_ceilometer-nova.xml62(replaceable)
+#: ./doc/install-guide/section_ceilometer-nova.xml70(replaceable)
+#: ./doc/install-guide/section_ceilometer-install.xml140(replaceable)
+msgid "CEILOMETER_TOKEN"
+msgstr "CEILOMETER_TOKEN"
+
+#: ./doc/install-guide/section_ceilometer-nova.xml63(para)
+msgid ""
+"Edit the <filename>/etc/ceilometer/ceilometer.conf</filename> file and "
+"change these lines in the <literal>[publisher]</literal> section. Replace "
+"<replaceable>CEILOMETER_TOKEN</replaceable> with the ceilometer token that "
+"you created previously:"
+msgstr "<filename>/etc/ceilometer/ceilometer.conf</filename> ファイルを編集し、<literal>[publisher]</literal> セクションでこれらの行を変更します。<replaceable>CEILOMETER_TOKEN</replaceable> を前に作成した ceilometer トークンに置き換えます。"
+
+#: ./doc/install-guide/section_ceilometer-nova.xml74(para)
+#: ./doc/install-guide/section_ceilometer-install.xml144(para)
+msgid "Configure the RabbitMQ access:"
+msgstr "RabbitMQ のアクセス権を設定します。"
+
+#: ./doc/install-guide/section_ceilometer-nova.xml77(para)
+#: ./doc/install-guide/section_ceilometer-nova.xml130(para)
+#: ./doc/install-guide/section_ceilometer-install.xml147(para)
+#: ./doc/install-guide/section_ceilometer-install.xml166(para)
+msgid ""
+"Edit the <filename>/etc/ceilometer/ceilometer.conf</filename> file and "
+"update the <literal>[DEFAULT]</literal> section:"
+msgstr "<filename>/etc/ceilometer/ceilometer.conf</filename> ファイルを編集し、<literal>[DEFAULT]</literal> セクションを更新します。"
+
+#: ./doc/install-guide/section_ceilometer-nova.xml84(para)
+msgid "Configure the QPid access:"
+msgstr "Qpid のアクセス権を設定します。"
+
+#: ./doc/install-guide/section_ceilometer-nova.xml89(para)
+msgid "Add the Identity service credentials:"
+msgstr "Identity Service のクレデンシャルを追加します。"
+
+#: ./doc/install-guide/section_ceilometer-nova.xml99(replaceable)
+#: ./doc/install-guide/section_ceilometer-nova.xml105(replaceable)
+#: ./doc/install-guide/section_ceilometer-nova.xml118(replaceable)
+#: ./doc/install-guide/section_ceilometer-nova.xml125(replaceable)
+#: ./doc/install-guide/section_ceilometer-install.xml177(replaceable)
+#: ./doc/install-guide/section_ceilometer-install.xml206(replaceable)
+#: ./doc/install-guide/section_ceilometer-install.xml214(replaceable)
+#: ./doc/install-guide/section_ceilometer-install.xml226(replaceable)
+#: ./doc/install-guide/section_ceilometer-install.xml233(replaceable)
+msgid "CEILOMETER_PASS"
+msgstr "CEILOMETER_PASS"
+
+#: ./doc/install-guide/section_ceilometer-nova.xml108(para)
+#: ./doc/install-guide/section_ceilometer-install.xml215(para)
+msgid ""
+"Edit the <filename>/etc/ceilometer/ceilometer.conf</filename> file and "
+"change the <literal>[keystone_authtoken]</literal> section:"
+msgstr "<filename>/etc/ceilometer/ceilometer.conf</filename> ファイルを編集し、<literal>[keystone_authtoken]</literal> セクションを変更します。"
+
+#: ./doc/install-guide/section_ceilometer-nova.xml119(para)
+#: ./doc/install-guide/section_ceilometer-install.xml227(para)
+msgid "Also set the <literal>[service_credentials]</literal> section:"
+msgstr "<literal>[service_credentials]</literal> セクションも設定します。"
+
+#: ./doc/install-guide/section_ceilometer-nova.xml129(para)
+#: ./doc/install-guide/section_ceilometer-install.xml165(para)
+msgid "Configure the log directory."
+msgstr "ログディレクトリを設定します。"
+
+#: ./doc/install-guide/section_ceilometer-nova.xml141(para)
+msgid "Start the service and configure it to start when the system boots:"
+msgstr "サービスを起動し、システム起動時に起動するよう設定します。"
+
+#: ./doc/install-guide/section_nova-controller.xml5(title)
+msgid "Install Compute controller services"
+msgstr "Compute コントローラーサービスのインストール"
+
+#: ./doc/install-guide/section_nova-controller.xml6(para)
+msgid ""
+"Compute is a collection of services that enable you to launch virtual "
+"machine instances. You can configure these services to run on separate nodes"
+" or the same node. In this guide, most services run on the controller node "
+"and the service that launches virtual machines runs on a dedicated compute "
+"node. This section shows you how to install and configure these services on "
+"the controller node."
+msgstr "Compute は仮想マシンインスタンスを起動できるようにするためのサービス群です。これらのサービスを別々のノードで実行することも同じノードで実行することも設定できます。このガイドでは、多くのサービスはコントローラーノードで実行し、仮想マシンを起動するサービスはコンピュート専用ノードで実行します。このセクションは、コントローラーノードにこれらのサービスをインストールし、設定する方法を示します。"
+
+#: ./doc/install-guide/section_nova-controller.xml15(para)
+msgid "Install the Compute packages necessary for the controller node."
+msgstr "コントローラーノードに必要な Compute のパッケージをインストールします。"
+
+#: ./doc/install-guide/section_nova-controller.xml27(para)
+msgid ""
+"Respond to the prompts for <link linkend=\"debconf-dbconfig-"
+"common\">database management</link>, <link linkend=\"debconf-"
+"keystone_authtoken\"><literal>[keystone_authtoken]</literal> "
+"settings</link>, <link linkend=\"debconf-rabbitqm\">RabbitMQ "
+"credentials</link>, and <link linkend=\"debconf-api-endpoints\">API "
+"endpoint</link> registration. The <placeholder-1/> command runs "
+"automatically."
+msgstr "<link linkend=\"debconf-dbconfig-common\">データベース管理</link>、<link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> 設定</link>、<link linkend=\"debconf-rabbitqm\">RabbitMQ クレデンシャル</link>、<link linkend=\"debconf-api-endpoints\">API エンドポイント</link>登録に関するプロンプトに答えます。<placeholder-1/> コマンドが自動的に実行されます。"
+
+#: ./doc/install-guide/section_nova-controller.xml38(para)
+msgid ""
+"Compute stores information in a database. In this guide, we use a MySQL "
+"database on the controller node. Configure Compute with the database "
+"location and credentials. Replace <replaceable>NOVA_DBPASS</replaceable> "
+"with the password for the database that you will create in a later step."
+msgstr "Compute は情報を保存するためにデータベースを使用します。このガイドでは、コントローラーノードで MySQL データベースを使用します。Compute をデータベースの位置とクレデンシャルで設定します。<replaceable>NOVA_DBPASS</replaceable> を後のステップで作成するデータベース用パスワードで置き換えます。"
+
+#: ./doc/install-guide/section_nova-controller.xml44(replaceable)
+#: ./doc/install-guide/section_nova-controller.xml51(replaceable)
+#: ./doc/install-guide/section_nova-controller.xml119(replaceable)
+#: ./doc/install-guide/section_nova-controller.xml121(replaceable)
+#: ./doc/install-guide/section_nova-compute.xml72(replaceable)
+msgid "NOVA_DBPASS"
+msgstr "NOVA_DBPASS"
+
+#: ./doc/install-guide/section_nova-controller.xml45(para)
+msgid ""
+"Edit the <literal>[database]</literal> section in the "
+"<filename>/etc/nova/nova.conf</filename> file, adding it if necessary, to "
+"modify this key:"
+msgstr "<filename>/etc/nova/nova.conf</filename> ファイルの <literal>[database]</literal> セクションを編集し、このキーを変更します。必要に応じてセクションを追加します。"
+
+#: ./doc/install-guide/section_nova-controller.xml55(para)
+msgid ""
+"Set these configuration keys to configure Compute to use the Qpid message "
+"broker:"
+msgstr "Compute が Qpid メッセージブローカーを使用するよう設定するために、これらの設定キーを設定します。"
+
+#: ./doc/install-guide/section_nova-controller.xml62(para)
+#: ./doc/install-guide/section_nova-compute.xml107(para)
+msgid ""
+"Configure the Compute service to use the RabbitMQ message broker by setting "
+"these configuration keys in the <literal>[DEFAULT]</literal> configuration "
+"group of the <filename>/etc/nova/nova.conf</filename> file:"
+msgstr "<filename>/etc/nova/nova.conf</filename> ファイルの <literal>[DEFAULT]</literal> 設定グループにこれらの設定キーを設定することにより、Compute サービスが RabbitMQ メッセージブローカーを使用するよう設定します。"
+
+#: ./doc/install-guide/section_nova-controller.xml73(para)
+msgid ""
+"Set these configuration keys to configure Compute to use the RabbitMQ "
+"message broker:"
+msgstr "Compute が RabbitMQ メッセージブローカーを使用するよう設定するために、これらの設定キーを設定します。"
+
+#: ./doc/install-guide/section_nova-controller.xml81(para)
+msgid ""
+"Set the <option>my_ip</option>, <option>vncserver_listen</option>, and "
+"<option>vncserver_proxyclient_address</option> configuration options to the "
+"management interface IP address of the controller node:"
+msgstr "<option>my_ip</option>、<option>vncserver_listen</option>、<option>vncserver_proxyclient_address</option> 設定オプションをコントローラーノードの管理インターフェース IP アドレスに設定します。"
+
+#: ./doc/install-guide/section_nova-controller.xml89(para)
+msgid ""
+"Edit the <filename>/etc/nova/nova.conf</filename> file and add these lines "
+"to the <literal>[DEFAULT]</literal> section:"
+msgstr "<filename>/etc/nova/nova.conf</filename> ファイルを編集し、<literal>[DEFAULT]</literal> セクションにこれらの行を追加します。"
+
+#: ./doc/install-guide/section_nova-controller.xml92(para)
+msgid ""
+"In Debian, the <package>debconf</package> package automatically sets up "
+"<literal>my_ip</literal> parameter but you must edit the "
+"<filename>/etc/nova/nova.conf</filename> file to configure the "
+"<option>vncserver_listen</option> and "
+"<option>vncserver_proxyclient_address</option> options, which appear at the "
+"end of the file:"
+msgstr "Debian では、<package>debconf</package> パッケージが自動的に <literal>my_ip</literal> パラメーターをセットアップしますが、<filename>/etc/nova/nova.conf</filename> ファイルの最後にある <option>vncserver_listen</option> オプションと <option>vncserver_proxyclient_address</option> オプションを設定するために、このファイルを編集する必要があります。"
+
+#: ./doc/install-guide/section_nova-controller.xml107(para)
+msgid ""
+"By default, the Ubuntu packages create an SQLite database. Delete the "
+"<filename>nova.sqlite</filename> file created in the "
+"<filename>/var/lib/nova/</filename> directory so that it does not get used "
+"by mistake:"
+msgstr "Ubuntu パッケージはデフォルトで SQLite データベースを作成します。誤って使用されないように、<filename>/var/lib/nova/</filename> に作成された <filename>nova.sqlite</filename> ファイルを削除します。"
+
+#: ./doc/install-guide/section_nova-controller.xml114(para)
+msgid ""
+"Use the password you created previously to log in as root. Create a "
+"<literal>nova</literal> database user:"
+msgstr "root としてログインするために、前に作成したパスワードを使用します。<literal>nova</literal> データベースユーザーを作成します。"
+
+#: ./doc/install-guide/section_nova-controller.xml124(para)
+msgid "Create the Compute service tables:"
+msgstr "Compute サービスのテーブルを作成します。"
+
+#: ./doc/install-guide/section_nova-controller.xml128(para)
+msgid ""
+"Create a <literal>nova</literal> user that Compute uses to authenticate with"
+" the Identity Service. Use the <literal>service</literal> tenant and give "
+"the user the <literal>admin</literal> role:"
+msgstr "Compute が Identity Service で認証するために使用する <literal>nova</literal> ユーザーを作成します。<literal>service</literal> プロジェクトを使用し、ユーザーに <literal>admin</literal> ロールを与えます。"
+
+#: ./doc/install-guide/section_nova-controller.xml132(replaceable)
+#: ./doc/install-guide/section_nova-controller.xml146(replaceable)
+#: ./doc/install-guide/section_nova-controller.xml166(replaceable)
+#: ./doc/install-guide/section_nova-compute.xml80(replaceable)
+#: ./doc/install-guide/section_nova-compute.xml99(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml234(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml258(replaceable)
+msgid "NOVA_PASS"
+msgstr "NOVA_PASS"
+
+#: ./doc/install-guide/section_nova-controller.xml132(replaceable)
+msgid "nova@example.com"
+msgstr "nova@example.com"
+
+#: ./doc/install-guide/section_nova-controller.xml136(para)
+msgid ""
+"Configure Compute to use these credentials with the Identity Service running"
+" on the controller. Replace <replaceable>NOVA_PASS</replaceable> with your "
+"Compute password."
+msgstr "コントローラーで実行している Identity Service でこれらのクレデンシャルを使用するよう Compute を設定します。<replaceable>NOVA_PASS</replaceable> をお使いの Compute パスワードで置き換えます。"
+
+#: ./doc/install-guide/section_nova-controller.xml147(para)
+msgid ""
+"Edit the <literal>[DEFAULT]</literal> section in the "
+"<filename>/etc/nova/nova.conf</filename> file to add this key:"
+msgstr "このキーを追加するために <filename>/etc/nova/nova.conf</filename> ファイルの <literal>[DEFAULT]</literal> セクションを編集します。"
+
+#: ./doc/install-guide/section_nova-controller.xml155(para)
+msgid "Add these keys to the <literal>[keystone_authtoken]</literal> section:"
+msgstr "これらのキーを <literal>[keystone_authtoken]</literal> セクションに追加します。"
+
+#: ./doc/install-guide/section_nova-controller.xml169(para)
+msgid ""
+"You must register Compute with the Identity Service so that other OpenStack "
+"services can locate it. Register the service and specify the endpoint:"
+msgstr "他の OpenStack サービスから使用できるように、Compute を Identity Service に登録します。サービスを登録し、エンドポイントを指定します。"
+
+#: ./doc/install-guide/section_nova-controller.xml182(para)
+msgid ""
+"Start Compute services and configure them to start when the system boots:"
+msgstr "Compute サービスを起動し、システム起動時に起動するよう設定します。"
+
+#: ./doc/install-guide/section_nova-controller.xml185(para)
+msgid "Restart Compute services:"
+msgstr "Compute サービスを再起動します。"
+
+#: ./doc/install-guide/section_nova-controller.xml206(para)
+msgid "To verify your configuration, list available images:"
+msgstr "設定を検証するために、使用可能なイメージを一覧表示します。"
+
+#: ./doc/install-guide/section_ceilometer-cinder.xml7(title)
+msgid "Add the Block Storage service agent for Telemetry"
+msgstr "Telemetry 用 Block Storage Service エージェントの追加"
+
+#: ./doc/install-guide/section_ceilometer-cinder.xml10(para)
+msgid ""
+"To retrieve volume samples, you must configure the Block Storage service to "
+"send notifications to the bus."
+msgstr "ボリュームのサンプルを取得するために、Block Storage Service がバスに通知を送信するよう設定する必要があります。"
+
+#: ./doc/install-guide/section_ceilometer-cinder.xml13(para)
+msgid ""
+"Edit <filename>/etc/cinder/cinder.conf</filename> and add in the "
+"<literal>[DEFAULT]</literal> section on the controller and volume nodes:"
+msgstr "コントローラーノードとボリュームノードで、<filename>/etc/cinder/cinder.conf</filename> を編集し、<literal>[DEFAULT]</literal> セクションに追加します。"
+
+#: ./doc/install-guide/section_ceilometer-cinder.xml19(para)
+msgid "Run the following commands on the controller and volume nodes:"
+msgstr "コントローラーノードおよびボリュームノードで以下のコマンドを実行します。"
+
+#: ./doc/install-guide/section_ceilometer-cinder.xml26(para)
+msgid "Restart the Block Storage services with their new settings."
+msgstr "新しい設定を用いて Block Storage のサービスを再起動します。"
+
+#: ./doc/install-guide/section_ceilometer-cinder.xml28(para)
+msgid "On the controller node:"
+msgstr "コントローラーノードで:"
+
+#: ./doc/install-guide/section_ceilometer-cinder.xml33(para)
+msgid "On the volume node:"
+msgstr "ボリュームノードで:"
+
+#: ./doc/install-guide/section_glance-verify.xml5(title)
+msgid "Verify the Image Service installation"
+msgstr "Image Service のインストールの検証"
+
+#: ./doc/install-guide/section_glance-verify.xml6(para)
+msgid ""
+"To test the Image Service installation, download at least one virtual "
+"machine image that is known to work with OpenStack. For example, CirrOS is a"
+" small test image that is often used for testing OpenStack deployments "
+"(<link href=\"http://download.cirros-cloud.net/\">CirrOS downloads</link>). "
+"This walk through uses the 64-bit CirrOS QCOW2 image."
+msgstr "Image Service のインストールをテストするために、OpenStack で動作することが知られている仮想マシンイメージを何かしらダウンロードします。例えば、CirrOS  (<link href=\"http://download.cirros-cloud.net/\">CirrOS ダウンロード</link>) は OpenStack 環境をテストするためによく使用される小さなテストイメージです。ここでは  64 ビット CirrOS QCOW2 イメージを使用します。"
+
+#: ./doc/install-guide/section_glance-verify.xml13(para)
+msgid ""
+"For more information about how to download and build images, see <link "
+"href=\"http://docs.openstack.org/image-"
+"guide/content/index.html\"><citetitle>OpenStack Virtual Machine Image "
+"Guide</citetitle></link>. For information about how to manage images, see "
+"the <link href=\"http://docs.openstack.org/user-"
+"guide/content/index.html\"><citetitle>OpenStack User "
+"Guide</citetitle></link>."
+msgstr "ダウンロード方法とイメージ構築の詳細は<link href=\"http://docs.openstack.org/image-guide/content/index.html\"><citetitle>OpenStack 仮想マシンイメージガイド</citetitle></link>を参照してください。イメージの管理方法の詳細は<link href=\"http://docs.openstack.org/user-guide/content/index.html\"><citetitle>OpenStack ユーザーガイド</citetitle></link>を参照してください。"
+
+#: ./doc/install-guide/section_glance-verify.xml24(para)
+msgid ""
+"Download the image into a dedicated directory using <placeholder-1/> or "
+"<placeholder-2/>:"
+msgstr "<placeholder-1/> や <placeholder-2/> を使用して、イメージを専用のディレクトリにダウンロードします。"
+
+#: ./doc/install-guide/section_glance-verify.xml32(para)
+msgid "Upload the image to the Image Service:"
+msgstr "イメージを Image Service にアップロードします。"
+
+#: ./doc/install-guide/section_glance-verify.xml33(replaceable)
+#: ./doc/install-guide/section_glance-verify.xml38(replaceable)
+msgid "IMAGELABEL"
+msgstr "IMAGELABEL"
+
+#: ./doc/install-guide/section_glance-verify.xml33(replaceable)
+#: ./doc/install-guide/section_glance-verify.xml45(replaceable)
+msgid "FILEFORMAT"
+msgstr "FILEFORMAT"
+
+#: ./doc/install-guide/section_glance-verify.xml34(replaceable)
+#: ./doc/install-guide/section_glance-verify.xml65(replaceable)
+msgid "CONTAINERFORMAT"
+msgstr "CONTAINERFORMAT"
+
+#: ./doc/install-guide/section_glance-verify.xml34(replaceable)
+#: ./doc/install-guide/section_glance-verify.xml86(replaceable)
+msgid "ACCESSVALUE"
+msgstr "ACCESSVALUE"
+
+#: ./doc/install-guide/section_glance-verify.xml34(replaceable)
+#: ./doc/install-guide/section_glance-verify.xml101(replaceable)
+msgid "IMAGEFILE"
+msgstr "IMAGEFILE"
+
+#: ./doc/install-guide/section_glance-verify.xml35(para)
+msgid "Where:"
+msgstr "各項目:"
+
+#: ./doc/install-guide/section_glance-verify.xml40(para)
+msgid "Arbitrary label. The name by which users refer to the image."
+msgstr "任意のラベル。ユーザーがイメージを参照する名前。"
+
+#: ./doc/install-guide/section_glance-verify.xml47(para)
+msgid ""
+"Specifies the format of the image file. Valid formats include "
+"<literal>qcow2</literal>, <literal>raw</literal>, <literal>vhd</literal>, "
+"<literal>vmdk</literal>, <literal>vdi</literal>, <literal>iso</literal>, "
+"<literal>aki</literal>, <literal>ari</literal>, and <literal>ami</literal>."
+msgstr "イメージファイルの形式を指定します。有効な形式は <literal>qcow2</literal>, <literal>raw</literal>, <literal>vhd</literal>, <literal>vmdk</literal>, <literal>vdi</literal>, <literal>iso</literal>, <literal>aki</literal>, <literal>ari</literal>, <literal>ami</literal> です。"
+
+#: ./doc/install-guide/section_glance-verify.xml58(para)
+msgid ""
+"You can verify the format using the <placeholder-1/> command: "
+"<placeholder-2/>"
+msgstr "<placeholder-1/> コマンドを使用して形式を確認できます。 <placeholder-2/>"
+
+#: ./doc/install-guide/section_glance-verify.xml67(para)
+msgid ""
+"Specifies the container format. Valid formats include: "
+"<literal>bare</literal>, <literal>ovf</literal>, <literal>aki</literal>, "
+"<literal>ari</literal> and <literal>ami</literal>."
+msgstr "コンテナーの形式を指定します。有効な形式は <literal>bare</literal>, <literal>ovf</literal>, <literal>aki</literal>, <literal>ari</literal>, <literal>ami</literal> です。"
+
+#: ./doc/install-guide/section_glance-verify.xml73(para)
+msgid ""
+"Specify <literal>bare</literal> to indicate that the image file is not in a "
+"file format that contains metadata about the virtual machine. Although this "
+"field is currently required, it is not actually used by any of the OpenStack"
+" services and has no effect on system behavior. Because the value is not "
+"used anywhere, it is safe to always specify <literal>bare</literal> as the "
+"container format."
+msgstr "仮想マシンに関するメタデータを含むイメージファイルがファイル形式ではないことを示すために <literal>bare</literal> を指定します。この項目が現在必須となっていますが、実際はすべての OpenStack により使用されるわけではなく、システム動作に影響を与えません。この値がどこでも使用されないため、常に <literal>bare</literal> をコンテナー形式として指定すると安全です。"
+
+#: ./doc/install-guide/section_glance-verify.xml90(para)
+msgid "true - All users can view and use the image."
+msgstr "true - すべてのユーザーがイメージを表示および使用できます。"
+
+#: ./doc/install-guide/section_glance-verify.xml94(para)
+msgid "false - Only administrators can view and use the image."
+msgstr "false - 管理者のみがイメージを表示および使用できます。"
+
+#: ./doc/install-guide/section_glance-verify.xml88(para)
+msgid "Specifies image access: <placeholder-1/>"
+msgstr "イメージのアクセス権を指定します。 <placeholder-1/>"
+
+#: ./doc/install-guide/section_glance-verify.xml103(para)
+msgid "Specifies the name of your downloaded image file."
+msgstr "ダウンロードしたイメージファイルの名前を指定します。"
+
+#: ./doc/install-guide/section_glance-verify.xml108(para)
+#: ./doc/install-guide/section_glance-verify.xml157(para)
+msgid "For example:"
+msgstr "例:"
+
+#: ./doc/install-guide/section_glance-verify.xml133(para)
+msgid ""
+"Because the returned image ID is generated dynamically, your deployment "
+"generates a different ID than the one shown in this example."
+msgstr "返されたイメージ ID は動的に変更されるため、導入環境によりこの例で示されているものと異なる ID が生成されます。"
+
+#: ./doc/install-guide/section_glance-verify.xml139(para)
+msgid "Confirm that the image was uploaded and display its attributes:"
+msgstr "イメージがアップロードされたことを確認し、その属性を表示します。"
+
+#: ./doc/install-guide/section_glance-verify.xml149(para)
+msgid ""
+"You can now remove the locally downloaded image, since it is stored and "
+"available through the Image Service."
+msgstr "これで Image Service に保存され、そこから利用できるため、ローカルにダウンロードしたイメージを削除できます。"
+
+#: ./doc/install-guide/section_glance-verify.xml156(para)
+msgid ""
+"Alternatively, the upload to the Image Service can be done without having to"
+" use local disk space to store the file, by use of the <parameter>--copy-"
+"from</parameter> parameter."
+msgstr "代わりに、Image Service にアップロードしたものは、<parameter>--copy-from</parameter> パラメーターを使用することにより、ファイルを保存するためのローカルディスク領域を使用する必要なく実行できます。"
+
+#: ./doc/install-guide/ch_debconf.xml6(title)
+msgid "Configure OpenStack with debconf"
+msgstr "debconf を用いた OpenStack の設定"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_basics-networking-neutron.xml29(None)
+#: ./doc/install-guide/ch_overview.xml98(None)
+msgid ""
+"@@image: 'figures/installguide_arch-neutron.png'; "
+"md5=9b3d2f2e5f9d88d198511ecbca829c6d"
+msgstr "@@image: 'figures/installguide_arch-neutron.png'; md5=9b3d2f2e5f9d88d198511ecbca829c6d"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml6(title)
+#: ./doc/install-guide/ch_networking.xml20(title)
+msgid "OpenStack Networking (neutron)"
+msgstr "OpenStack Networking (neutron)"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml7(para)
+msgid ""
+"The example architecture with OpenStack Networking (neutron) requires one "
+"controller node, one network node, and at least one compute node. The "
+"controller node contains one network interface on the <glossterm>management "
+"network</glossterm>. The network node contains one network interface on the "
+"management network, one on the <glossterm>instance tunnels "
+"network</glossterm>, and one on the <glossterm>external network</glossterm>."
+" The compute node contains one network interface on the management network "
+"and one on the instance tunnels network."
+msgstr "この OpenStack Networking (neutron) を持つアーキテクチャ例は、1 つのコントローラーノード、1 つのネットワークノード、最低 1 つのコンピュートノードを必要とします。コントローラーノードは、<glossterm baseform=\"management network\">管理ネットワーク</glossterm>に 1 つのネットワークインターフェースを持ちます。ネットワークノードは、管理ネットワークに 1 つのネットワークインターフェースを、<glossterm baseform=\"instance tunnels network\">インスタンストンネルネットワーク</glossterm>に 1 つを、<glossterm baseform=\"external network\">外部ネットワーク</glossterm>に 1 つを持ちます。コンピュートノードは、管理ネットワークに 1 つのインターフェースを、インスタンストンネルネットワークに 1 つを持ちます。"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml17(para)
+msgid ""
+"Network interface names vary by distribution. Traditionally, interfaces use "
+"\"eth\" followed by a sequential number. To cover all variations, this guide"
+" simply refers to the first interface as the interface with the lowest "
+"number, the second interface as the interface with the middle number, and "
+"the third interface as the interface with the highest number."
+msgstr "ネットワークインターフェースの名前はディストリビューションにより異なります。伝統的に、インターフェースは、「eth」から始まり、数字が後ろにつきます。すべての種類を取り扱うために、このガイドは単に、最小の番号を持つインターフェースとして 1 番目のインターフェースを参照します。真ん中の番号を持つインターフェースとして 2 番目のインターフェースを、最大の番号を持つインターフェースとして 3 番目のインターフェースを参照します。"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml25(title)
+#: ./doc/install-guide/ch_overview.xml94(title)
+msgid "Three-node architecture with OpenStack Networking (neutron)"
+msgstr "OpenStack Networking (Neutron) を持つ 3 ノードアーキテクチャー"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml33(para)
+#: ./doc/install-guide/section_basics-networking-nova.xml29(para)
+msgid ""
+"Unless you intend to use the exact configuration provided in this example "
+"architecture, you must modify the networks in this procedure to match your "
+"environment. Also, each node must resolve the other nodes by name in "
+"addition to IP address. For example, the "
+"<replaceable>controller</replaceable> name must resolve to "
+"<literal>10.0.0.11</literal>, the IP address of the management interface on "
+"the controller node."
+msgstr "このアーキテクチャ例で提供される設定とまったく同じものを使用したくなければ、お使いの環境に合わせるために、この手順にあるネットワークを変更する必要があります。また、各ノードは、IP アドレスに加えて、名前により他のノードを名前解決する必要があります。例えば、<replaceable>controller</replaceable> という名前は、コントローラーノードの管理ネットワークの IP アドレス <literal>10.0.0.11</literal> に解決する必要があります。"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml41(para)
+#: ./doc/install-guide/section_basics-networking-nova.xml37(para)
+msgid ""
+"Reconfiguring network interfaces will interrupt network connectivity. We "
+"recommend using a local terminal session for these procedures."
+msgstr "ネットワークインターフェースを再設定すると、ネットワーク接続性が中断されます。これらの手順はローカルの端末セッションを使用することを推奨します。"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml46(title)
+#: ./doc/install-guide/section_basics-networking-nova.xml42(title)
+msgid "Controller node"
+msgstr "コントローラーノード"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml48(title)
+#: ./doc/install-guide/section_basics-networking-neutron.xml83(title)
+#: ./doc/install-guide/section_basics-networking-neutron.xml165(title)
+#: ./doc/install-guide/section_basics-networking-nova.xml44(title)
+#: ./doc/install-guide/section_basics-networking-nova.xml76(title)
+msgid "To configure networking:"
+msgstr "ネットワークを設定する方法:"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml50(para)
+#: ./doc/install-guide/section_basics-networking-neutron.xml85(para)
+#: ./doc/install-guide/section_basics-networking-neutron.xml167(para)
+#: ./doc/install-guide/section_basics-networking-nova.xml46(para)
+#: ./doc/install-guide/section_basics-networking-nova.xml78(para)
+msgid "Configure the first interface as the management interface:"
+msgstr "管理インターフェースとして 1 番目のインターフェースを設定します。"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml51(para)
+#: ./doc/install-guide/section_basics-networking-nova.xml47(para)
+msgid "IP address: 10.0.0.11"
+msgstr "IP アドレス: 10.0.0.11"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml52(para)
+#: ./doc/install-guide/section_basics-networking-neutron.xml87(para)
+#: ./doc/install-guide/section_basics-networking-neutron.xml94(para)
+#: ./doc/install-guide/section_basics-networking-neutron.xml169(para)
+#: ./doc/install-guide/section_basics-networking-neutron.xml180(para)
+#: ./doc/install-guide/section_basics-networking-nova.xml48(para)
+#: ./doc/install-guide/section_basics-networking-nova.xml80(para)
+msgid "Network mask: 255.255.255.0 (or /24)"
+msgstr "ネットマスク: 255.255.255.0 (または /24)"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml53(para)
+#: ./doc/install-guide/section_basics-networking-neutron.xml88(para)
+#: ./doc/install-guide/section_basics-networking-neutron.xml170(para)
+#: ./doc/install-guide/section_basics-networking-nova.xml49(para)
+#: ./doc/install-guide/section_basics-networking-nova.xml81(para)
+msgid "Default gateway: 10.0.0.1"
+msgstr "デフォルトゲートウェイ: 10.0.0.1"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml57(title)
+#: ./doc/install-guide/section_basics-networking-neutron.xml140(title)
+#: ./doc/install-guide/section_basics-networking-neutron.xml188(title)
+#: ./doc/install-guide/section_basics-networking-nova.xml53(title)
+#: ./doc/install-guide/section_basics-networking-nova.xml131(title)
+msgid "To configure name resolution:"
+msgstr "名前解決を設定する方法:"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml59(para)
+#: ./doc/install-guide/section_basics-networking-nova.xml55(para)
+msgid ""
+"Set the hostname of the node to "
+"<code><replaceable>controller</replaceable></code>."
+msgstr "ノードのホスト名を <code><replaceable>controller</replaceable></code> に設定します。"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml63(para)
+#: ./doc/install-guide/section_basics-networking-neutron.xml145(para)
+#: ./doc/install-guide/section_basics-networking-neutron.xml193(para)
+#: ./doc/install-guide/section_basics-networking-nova.xml59(para)
+#: ./doc/install-guide/section_basics-networking-nova.xml136(para)
+msgid ""
+"Edit the <filename>/etc/hosts</filename> file to contain the following:"
+msgstr "<filename>/etc/hosts</filename> ファイルを編集し、以下の内容を含めます。"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml74(para)
+#: ./doc/install-guide/section_basics-networking-neutron.xml156(para)
+#: ./doc/install-guide/section_basics-networking-neutron.xml204(para)
+#: ./doc/install-guide/section_basics-networking-nova.xml67(para)
+#: ./doc/install-guide/section_basics-networking-nova.xml144(para)
+msgid ""
+"You must remove or comment the line beginning with "
+"<literal>127.0.1.1</literal>."
+msgstr "<literal>127.0.1.1</literal> から始まる行を削除するかコメントアウトする必要があります。"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml81(title)
+msgid "Network node"
+msgstr "ネットワークノード"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml86(para)
+msgid "IP address: 10.0.0.21"
+msgstr "IP アドレス: 10.0.0.21"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml91(para)
+#: ./doc/install-guide/section_basics-networking-neutron.xml177(para)
+msgid "Configure the second interface as the instance tunnels interface:"
+msgstr "インスタンスのトンネルインターフェースとして 2 番目のインターフェースを設定します。"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml93(para)
+msgid "IP address: 10.0.1.21"
+msgstr "IP アドレス: 10.0.1.21"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml97(para)
+msgid ""
+"The external interface uses a special configuration without an IP address "
+"assigned to it. Configure the third interface as the external interface:"
+msgstr "外部インターフェースは、IP アドレスを割り当てない特別な設定を使用します。外部インターフェースとして 3 番目のインターフェースを設定します。"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml100(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml458(para)
+msgid ""
+"Replace <replaceable>INTERFACE_NAME</replaceable> with the actual interface "
+"name. For example, <emphasis>eth2</emphasis> or <emphasis>ens256</emphasis>."
+msgstr "<replaceable>INTERFACE_NAME</replaceable> を実際のインターフェース名で置き換えます。例えば、<emphasis>eth2</emphasis> や <emphasis>ens256</emphasis> です。"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml105(para)
+#: ./doc/install-guide/section_basics-networking-nova.xml96(para)
+msgid ""
+"Edit the <filename>/etc/network/interfaces</filename> file to contain the "
+"following:"
+msgstr "<filename>/etc/network/interfaces</filename> ファイルを編集し、以下の内容を含めます。"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml108(replaceable)
+#: ./doc/install-guide/section_basics-networking-neutron.xml109(replaceable)
+#: ./doc/install-guide/section_basics-networking-neutron.xml119(replaceable)
+#: ./doc/install-guide/section_nova-networking-compute-node.xml50(replaceable)
+#: ./doc/install-guide/section_nova-networking-compute-node.xml52(replaceable)
+#: ./doc/install-guide/section_nova-networking-compute-node.xml73(replaceable)
+#: ./doc/install-guide/section_nova-networking-compute-node.xml74(replaceable)
+#: ./doc/install-guide/section_basics-networking-nova.xml99(replaceable)
+#: ./doc/install-guide/section_basics-networking-nova.xml100(replaceable)
+#: ./doc/install-guide/section_basics-networking-nova.xml110(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml461(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml469(replaceable)
+msgid "INTERFACE_NAME"
+msgstr "INTERFACE_NAME"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml114(para)
+#: ./doc/install-guide/section_basics-networking-nova.xml105(para)
+msgid ""
+"Edit the <filename>/etc/sysconfig/network-"
+"scripts/ifcfg-<replaceable>INTERFACE_NAME</replaceable></filename> file to "
+"contain the following:"
+msgstr "<filename>/etc/sysconfig/network-scripts/ifcfg-<replaceable>INTERFACE_NAME</replaceable></filename> ファイルを編集し、以下の内容を含めます。"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml117(para)
+#: ./doc/install-guide/section_basics-networking-nova.xml108(para)
+msgid ""
+"Do not change the <literal>HWADDR</literal> and <literal>UUID</literal> "
+"keys."
+msgstr "<literal>HWADDR</literal> と <literal>UUID</literal> の項目を変更してはいけません。"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml125(para)
+#: ./doc/install-guide/section_basics-networking-nova.xml116(para)
+msgid ""
+"Edit the "
+"<filename>/etc/sysconfig/network/ifcfg-<replaceable>INTERFACE_NAME</replaceable></filename>"
+" file to contain the following:"
+msgstr "<filename>/etc/sysconfig/network/ifcfg-<replaceable>INTERFACE_NAME</replaceable></filename> ファイルを編集し、以下の内容を含めます。"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml134(para)
+#: ./doc/install-guide/section_basics-networking-nova.xml125(para)
+msgid "Restart networking:"
+msgstr "ネットワークを再起動します。"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml142(para)
+msgid "Set the hostname of the node to <code>network</code>."
+msgstr "ノードのホスト名を <code>network</code> に設定します。"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml163(title)
+#: ./doc/install-guide/section_basics-networking-nova.xml74(title)
+msgid "Compute node"
+msgstr "コンピュートノード"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml168(para)
+#: ./doc/install-guide/section_basics-networking-nova.xml79(para)
+msgid "IP address: 10.0.0.31"
+msgstr "IP アドレス: 10.0.0.31"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml172(para)
+#: ./doc/install-guide/section_basics-networking-nova.xml83(para)
+msgid "Additional compute nodes should use 10.0.0.32, 10.0.0.33, and so on."
+msgstr "追加のコンピュートノードは 10.0.0.32、10.0.0.33 などを使用すべきです。"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml179(para)
+msgid "IP address: 10.0.1.31"
+msgstr "IP アドレス: 10.0.1.31"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml182(para)
+msgid "Additional compute nodes should use 10.0.1.32, 10.0.1.33, and so on."
+msgstr "追加のコンピュートノードは 10.0.1.32、10.0.1.33 などを使用すべきです。"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml190(para)
+#: ./doc/install-guide/section_basics-networking-nova.xml133(para)
+msgid "Set the hostname of the node to <code>compute1</code>."
+msgstr "ノードのホスト名を <code>compute1</code> に設定します。"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml211(title)
+#: ./doc/install-guide/section_neutron-initial-networks.xml228(title)
+#: ./doc/install-guide/section_basics-networking-nova.xml151(title)
+msgid "Verify connectivity"
+msgstr "接続性の検証"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml212(para)
+#: ./doc/install-guide/section_basics-networking-nova.xml152(para)
+msgid ""
+"We recommend that you verify network connectivity to the internet and among "
+"the nodes before proceeding further."
+msgstr "続行する前に、インターネットとノード間のネットワーク接続性を検証することを推奨します。"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml216(para)
+#: ./doc/install-guide/section_basics-networking-nova.xml156(para)
+msgid ""
+"From the <emphasis>controller</emphasis> node, <placeholder-1/> a site on "
+"the internet:"
+msgstr "<emphasis>controller</emphasis> ノードから、インターネットのサイトに <placeholder-1/> します。"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml230(para)
+msgid ""
+"From the <emphasis>controller</emphasis> node, <placeholder-1/> the "
+"management interface on the <emphasis>network</emphasis> node:"
+msgstr "<emphasis>controller</emphasis> ノードから、<emphasis>network</emphasis> ノードの管理インターフェースに <placeholder-1/> します。"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml233(replaceable)
+msgid "network"
+msgstr "Network"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml245(para)
+#: ./doc/install-guide/section_basics-networking-nova.xml170(para)
+msgid ""
+"From the <emphasis>controller</emphasis> node, <placeholder-1/> the "
+"management interface on the <emphasis>compute</emphasis> node:"
+msgstr "<emphasis>controller</emphasis> ノードから、<emphasis>compute</emphasis> ノードの管理インターフェースに <placeholder-1/> します。"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml248(replaceable)
+#: ./doc/install-guide/section_basics-networking-nova.xml173(replaceable)
+msgid "compute1"
+msgstr "compute1"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml260(para)
+msgid ""
+"From the <emphasis>network</emphasis> node, <placeholder-1/> a site on the "
+"internet:"
+msgstr "<emphasis>network</emphasis> ノードから、インターネットのサイトに <placeholder-1/> します。"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml274(para)
+msgid ""
+"From the <emphasis>network</emphasis> node, <placeholder-1/> the management "
+"interface on the <emphasis>controller</emphasis> node:"
+msgstr "<emphasis>network</emphasis> ノードから、<emphasis>controller</emphasis> ノードの管理インターフェースに <placeholder-1/> します。"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml289(para)
+msgid ""
+"From the <emphasis>network</emphasis> node, <placeholder-1/> the instance "
+"tunnels interface on the <emphasis>compute</emphasis> node:"
+msgstr "<emphasis>network</emphasis> ノードから、<emphasis>compute</emphasis> ノードの管理インターフェースに <placeholder-1/> します。"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml304(para)
+#: ./doc/install-guide/section_basics-networking-nova.xml185(para)
+msgid ""
+"From the <emphasis>compute</emphasis> node, <placeholder-1/> a site on the "
+"internet:"
+msgstr "<emphasis>compute</emphasis> ノードから、インターネットのサイトに <placeholder-1/> します。"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml318(para)
+#: ./doc/install-guide/section_basics-networking-nova.xml199(para)
+msgid ""
+"From the <emphasis>compute</emphasis> node, <placeholder-1/> the management "
+"interface on the <emphasis>controller</emphasis> node:"
+msgstr "<emphasis>compute</emphasis> ノードから、<emphasis>controller</emphasis> ノードの管理インターフェースに <placeholder-1/> します。"
+
+#: ./doc/install-guide/section_basics-networking-neutron.xml333(para)
+msgid ""
+"From the <emphasis>compute</emphasis> node, <placeholder-1/> the instance "
+"tunnels interface on the <emphasis>network</emphasis> node:"
+msgstr "<emphasis>compute</emphasis> ノードから、<emphasis>network</emphasis> ノードの管理インターフェースに <placeholder-1/> します。"
+
+#: ./doc/install-guide/section_basics-passwords.xml6(title)
+msgid "Passwords"
+msgstr "パスワード"
+
+#: ./doc/install-guide/section_basics-passwords.xml7(para)
+msgid ""
+"The various OpenStack services and the required software like the database "
+"and the messaging server have to be password protected. You use these "
+"passwords when configuring a service and then again to access the service. "
+"You have to choose a password while configuring the service and later "
+"remember to use the same password when accessing it. Optionally, you can "
+"generate random passwords with the <application>pwgen</application> program."
+" Or, to create passwords one at a time, use the output of this command "
+"repeatedly: <placeholder-1/>"
+msgstr "さまざまな OpenStack サービス、データベースやメッセージングサーバーのような必要ソフトウェアは、パスワードで保護する必要があります。サービスを設定するとき、後からサービスにアクセスするときに、これらのパスワードを使用します。サービスを設定するときにパスワードを選択する必要があります。後からサービスにアクセスするときに同じパスワードを使用するために覚えておきます。オプションとして、<application>pwgen</application> プログラムを用いてランダムなパスワードを生成できます。または、一度に 1 つのパスワードを作成するために、このコマンドを繰り返し使用します。<placeholder-1/>"
+
+#: ./doc/install-guide/section_basics-passwords.xml17(para)
+msgid ""
+"This guide uses the convention that "
+"<literal><replaceable>SERVICE_PASS</replaceable></literal> is the password "
+"to access the service <literal>SERVICE</literal> and "
+"<literal><replaceable>SERVICE_DBPASS</replaceable></literal> is the database"
+" password used by the service SERVICE to access the database."
+msgstr "このガイドは以下のとおり表記します。<literal><replaceable>SERVICE_PASS</replaceable></literal> が <literal>SERVICE</literal> にアクセスするためのパスワード、<literal><replaceable>SERVICE_DBPASS</replaceable></literal> がデータベースにアクセスするために SERVICE サービスにより使用されるデータベースのパスワードです。"
+
+#: ./doc/install-guide/section_basics-passwords.xml24(para)
+msgid ""
+"The complete list of passwords you need to define in this guide are: <table "
+"rules=\"all\"><caption>Passwords</caption><thead><tr><th>Password "
+"name</th><th>Description</th></tr></thead><tbody><tr><td>Database password "
+"(no variable used)</td><td>Root password for the database</td></tr><tr "
+"os=\"ubuntu;opensuse;sles\"><td><literal><replaceable>RABBIT_PASS</replaceable></literal></td><td>Password"
+" of user guest of "
+"RabbitMQ</td></tr><tr><td><literal><replaceable>KEYSTONE_DBPASS</replaceable></literal></td><td>Database"
+" password of Identity "
+"service</td></tr><tr><td><literal><replaceable>DEMO_PASS</replaceable></literal></td><td>Password"
+" of user "
+"<literal>demo</literal></td></tr><tr><td><literal><replaceable>ADMIN_PASS</replaceable></literal></td><td>Password"
+" of user "
+"<literal>admin</literal></td></tr><tr><td><literal><replaceable>GLANCE_DBPASS</replaceable></literal></td><td>Database"
+" password for Image "
+"Service</td></tr><tr><td><literal><replaceable>GLANCE_PASS</replaceable></literal></td><td>Password"
+" of Image Service user "
+"<literal>glance</literal></td></tr><tr><td><literal><replaceable>NOVA_DBPASS</replaceable></literal></td><td>Database"
+" password for Compute "
+"service</td></tr><tr><td><literal><replaceable>NOVA_PASS</replaceable></literal></td><td>Password"
+" of Compute service user "
+"<literal>nova</literal></td></tr><tr><td><literal><replaceable>DASH_DBPASS</replaceable></literal></td><td>Database"
+" password for the "
+"dashboard</td></tr><tr><td><literal><replaceable>CINDER_DBPASS</replaceable></literal></td><td>Database"
+" password for the Block Storage "
+"service</td></tr><tr><td><literal><replaceable>CINDER_PASS</replaceable></literal></td><td>Password"
+" of Block Storage service user "
+"<literal>cinder</literal></td></tr><tr><td><literal><replaceable>NEUTRON_DBPASS</replaceable></literal></td><td>Database"
+" password for the Networking "
+"service</td></tr><tr><td><literal><replaceable>NEUTRON_PASS</replaceable></literal></td><td>Password"
+" of Networking service user "
+"<literal>neutron</literal></td></tr><tr><td><literal><replaceable>HEAT_DBPASS</replaceable></literal></td><td>Database"
+" password for the Orchestration "
+"service</td></tr><tr><td><literal><replaceable>HEAT_PASS</replaceable></literal></td><td>Password"
+" of Orchestration service user "
+"<literal>heat</literal></td></tr><tr><td><literal><replaceable>CEILOMETER_DBPASS</replaceable></literal></td><td>Database"
+" password for the Telemetry "
+"service</td></tr><tr><td><literal><replaceable>CEILOMETER_PASS</replaceable></literal></td><td>Password"
+" of Telemetry service user "
+"<literal>ceilometer</literal></td></tr><tr><td><literal><replaceable>TROVE_DBPASS</replaceable></literal></td><td>Database"
+" password of Database "
+"service</td></tr><tr><td><literal><replaceable>TROVE_PASS</replaceable></literal></td><td>Password"
+" of Database Service user <literal>trove</literal></td></tr></tbody></table>"
+msgstr "このガイドで定義する必要のあるパスワードの完全な一覧は以下です。 <table rules=\"all\"><caption>パスワード</caption><thead><tr><th>パスワード名</th><th>説明</th></tr></thead><tbody><tr><td>データベースパスワード (変数を使用しません)</td><td>データベースの root パスワード</td></tr><tr os=\"ubuntu;opensuse;sles\"><td><literal><replaceable>RABBIT_PASS</replaceable></literal></td><td>RabbitMQ の guest ユーザーのパスワード</td></tr><tr><td><literal><replaceable>KEYSTONE_DBPASS</replaceable></literal></td><td>Identity Service のデータベースのパスワード</td></tr><tr><td><literal><replaceable>DEMO_PASS</replaceable></literal></td><td><literal>demo</literal> ユーザーのパスワード</td></tr><tr><td><literal><replaceable>ADMIN_PASS</replaceable></literal></td><td><literal>admin</literal> ユーザーのパスワード</td></tr><tr><td><literal><replaceable>GLANCE_DBPASS</replaceable></literal></td><td>Image Service のデータベースのパスワード</td></tr><tr><td><literal><replaceable>GLANCE_PASS</replaceable></literal></td><td>Image Service の <literal>glance</literal> ユーザーのパスワード</td></tr><tr><td><literal><replaceable>NOVA_DBPASS</replaceable></literal></td><td>Compute Service のデータベースのパスワード</td></tr><tr><td><literal><replaceable>NOVA_PASS</replaceable></literal></td><td>Compute Service の <literal>nova</literal> ユーザーのパスワード</td></tr><tr><td><literal><replaceable>DASH_DBPASS</replaceable></literal></td><td>Dashboard のデータベースのパスワード</td></tr><tr><td><literal><replaceable>CINDER_DBPASS</replaceable></literal></td><td>Block Storage Service のデータベースのパスワード</td></tr><tr><td><literal><replaceable>CINDER_PASS</replaceable></literal></td><td>Block Storage Service の <literal>cinder</literal> ユーザーのパスワード</td></tr><tr><td><literal><replaceable>NEUTRON_DBPASS</replaceable></literal></td><td>Networking Service のデータベースのパスワード</td></tr><tr><td><literal><replaceable>NEUTRON_PASS</replaceable></literal></td><td>Networking Service の <literal>neutron</literal> ユーザーのパスワード</td></tr><tr><td><literal><replaceable>HEAT_DBPASS</replaceable></literal></td><td>Orchestration Service のデータベースのパスワード</td></tr><tr><td><literal><replaceable>HEAT_PASS</replaceable></literal></td><td>Orchestration Service の <literal>heat</literal> ユーザーのパスワード</td></tr><tr><td><literal><replaceable>CEILOMETER_DBPASS</replaceable></literal></td><td>Telemetry Service のデータベースのパスワード</td></tr><tr><td><literal><replaceable>CEILOMETER_PASS</replaceable></literal></td><td>Telemetry Service の <literal>ceilometer</literal> ユーザーのパスワード</td></tr><tr><td><literal><replaceable>TROVE_DBPASS</replaceable></literal></td><td>Database サービスのデータベースパスワード</td></tr><tr><td><literal><replaceable>TROVE_PASS</replaceable></literal></td><td>Database サービスのユーザー <literal>trove</literal> のパスワード</td></tr></tbody></table>"
+
+#: ./doc/install-guide/ch_keystone.xml6(title)
+msgid "Configure the Identity Service"
+msgstr "Identity Service の設定"
+
+#: ./doc/install-guide/ch_swift.xml6(title)
+msgid "Add Object Storage"
+msgstr "Object Storage の追加"
+
+#: ./doc/install-guide/ch_swift.xml7(para)
+msgid ""
+"The OpenStack Object Storage services work together to provide object "
+"storage and retrieval through a REST API. For this example architecture, you"
+" must have already installed the Identity Service, also known as Keystone."
+msgstr "OpenStack Object Storage Service はオブジェクトストレージと REST API 経由の取得を提供するために一緒に動作します。このアーキテクチャー例は、Keystone として知られる Identity Service がすでにインストールされている必要があります。"
+
+#: ./doc/install-guide/ch_swift.xml30(title)
+#: ./doc/install-guide/ch_horizon.xml38(title)
+#: ./doc/install-guide/ch_heat.xml14(title)
+#: ./doc/install-guide/ch_ceilometer.xml18(title)
+#: ./doc/install-guide/ch_cinder.xml20(title)
+#: ./doc/install-guide/ch_networking.xml37(title)
+msgid "Next steps"
+msgstr "次の手順"
+
+#: ./doc/install-guide/ch_swift.xml31(para)
+msgid ""
+"Your OpenStack environment now includes Object Storage. You can <link "
+"linkend=\"launch-instance\">launch an instance</link> or add more services "
+"to your environment in the following chapters."
+msgstr "OpenStack 環境に Object Storage が追加されました。<link linkend=\"launch-instance\">インスタンスの起動</link>、以降の章に記載されているサービスの環境への追加を実行できます。"
+
+#: ./doc/install-guide/section_neutron-concepts.xml6(title)
+msgid "Networking concepts"
+msgstr "Networking の概念"
+
+#: ./doc/install-guide/section_neutron-concepts.xml7(para)
+msgid ""
+"OpenStack Networking (neutron) manages all of the networking facets for the "
+"Virtual Networking Infrastructure (VNI) and the access layer aspects of the "
+"Physical Networking Infrastructure (PNI) in your OpenStack environment. "
+"OpenStack Networking allows tenants to create advanced virtual network "
+"topologies including services such as <glossterm "
+"baseform=\"firewall\">firewalls</glossterm>, <glossterm baseform=\"load "
+"balancer\">load balancers</glossterm>, and <glossterm baseform=\"virtual "
+"private network (VPN)\"> virtual private networks (VPNs)</glossterm>."
+msgstr "OpenStack Networking (neutron) は OpenStack 環境で、仮想ネットワークインフラストラクチャ (VNI) のすべてのネットワークファセット、物理ネットワークインフラストラクチャ (PNI) のアクセス層の側面を管理します。OpenStack Networking により、プロジェクトが<glossterm baseform=\"firewall\">ファイアウォール</glossterm>、<glossterm baseform=\"load balancer\">負荷分散装置</glossterm>、<glossterm baseform=\"virtual private network (VPN)\">VPN</glossterm> などの高度な仮想ネットワークトポロジーを作成できるようになります。"
+
+#: ./doc/install-guide/section_neutron-concepts.xml16(para)
+msgid ""
+"Networking provides the following object abstractions: networks, subnets, "
+"and routers. Each has functionality that mimics its physical counterpart: "
+"networks contain subnets, and routers route traffic between different subnet"
+" and networks."
+msgstr "Networking はネットワーク、サブネット、ルーターのオブジェクトの抽象化を提供します。それぞれ、対応する物理的なものの機能を模倣します。ネットワークがサブネットを含みます。ルーターがサブネットやネットワーク間の通信を中継します。"
+
+#: ./doc/install-guide/section_neutron-concepts.xml20(para)
+msgid ""
+"Any given Networking set up has at least one external network. This network,"
+" unlike the other networks, is not merely a virtually defined network. "
+"Instead, it represents the view into a slice of the external network that is"
+" accessible outside the OpenStack installation. IP addresses on the "
+"Networking external network are accessible by anybody physically on the "
+"outside network. Because this network merely represents a slice of the "
+"outside network, DHCP is disabled on this network."
+msgstr "すべての Networking 環境は少なくとも 1 つの外部ネットワークを持ちます。このネットワークは、他のネットワークと異なり、ほとんど仮想的に定義されたネットワークではありません。これは OpenStack インストール環境の外部からアクセス可能な外部ネットワークの一部のビューであることを意味します。Networking 外部ネットワークの IP アドレスは外部ネットワークにある何らかの物理的なものによりアクセスできます。このネットワークがほとんど外部ネットワークの一部を表すため、DHCP はこのネットワークで無効化されます。"
+
+#: ./doc/install-guide/section_neutron-concepts.xml28(para)
+msgid ""
+"In addition to external networks, any Networking set up has one or more "
+"internal networks. These software-defined networks connect directly to the "
+"VMs. Only the VMs on any given internal network, or those on subnets "
+"connected through interfaces to a similar router, can access VMs connected "
+"to that network directly."
+msgstr "外部ネットワークに加えて、あらゆる Networking のセットアップ環境は 1 つ以上の内部ネットワークを持ちます。これらの SDN は仮想マシンに直接接続します。あらゆる指定された内部ネットワークにある仮想マシン、またはインターフェース経由で同様のルーターに接続されたサブネットにある仮想マシンのみが、そのネットワークに接続された仮想マシンに直接アクセスできます。"
+
+#: ./doc/install-guide/section_neutron-concepts.xml33(para)
+msgid ""
+"For the outside network to access VMs, and vice versa, routers between the "
+"networks are needed. Each router has one gateway that is connected to a "
+"network and many interfaces that are connected to subnets. Like a physical "
+"router, subnets can access machines on other subnets that are connected to "
+"the same router, and machines can access the outside network through the "
+"gateway for the router."
+msgstr "外部ネットワークが仮想マシンにアクセスするため、またその逆のため、ネットワーク間のルーターが必要になります。各ルーターはネットワークに接続された 1 つのゲートウェイとサブネットに接続された多くのインターフェースを持ちます。物理ルーターのように、同じルーターに接続された他のサブネットにあるマシンにサブネットがアクセスできます。また、マシンはルーターに対するゲートウェイ経由で外部ネットワークにアクセスできます。"
+
+#: ./doc/install-guide/section_neutron-concepts.xml40(para)
+msgid ""
+"Additionally, you can allocate IP addresses on external networks to ports on"
+" the internal network. Whenever something is connected to a subnet, that "
+"connection is called a port. You can associate external network IP addresses"
+" with ports to VMs. This way, entities on the outside network can access "
+"VMs."
+msgstr "さらに、内部ネットワークにたどり着くために外部ネットワークに IP アドレスを割り当てることができます。何かがサブネットに接続されたとき必ず、その接続がポートと呼ばれます。外部ネットワークの IP アドレスを仮想マシンのポートに関連づけられます。このように、外部ネットワークのものが仮想マシンにアクセスできます。"
+
+#: ./doc/install-guide/section_neutron-concepts.xml45(para)
+msgid ""
+"Networking also supports <emphasis role=\"italic\">security "
+"groups</emphasis>. Security groups enable administrators to define firewall "
+"rules in groups. A VM can belong to one or more security groups, and "
+"Networking applies the rules in those security groups to block or unblock "
+"ports, port ranges, or traffic types for that VM."
+msgstr "Networking は <emphasis role=\"italic\">セキュリティグループ</emphasis> もサポートします。セキュリティグループにより、管理者がグループでファイアウォールルールを定義できます。仮想マシンは 1 つ以上のセキュリティグループに属します。Networking が、ポート、ポート範囲、または通信種別をブロックするかブロックしないかのために、これらのセキュリティグループにあるルールを仮想マシンに対して適用します。"
+
+#: ./doc/install-guide/section_neutron-concepts.xml51(para)
+msgid ""
+"Each plug-in that Networking uses has its own concepts. While not vital to "
+"operating Networking, understanding these concepts can help you set up "
+"Networking. All Networking installations use a core plug-in and a security "
+"group plug-in (or just the No-Op security group plug-in). Additionally, "
+"Firewall-as-a-service (FWaaS) and Load-balancing-as-a-service (LBaaS) plug-"
+"ins are available."
+msgstr "Networking が使用する各プラグインはそれぞれ独自の概念を持ちます。Networking を稼働されるために必須ではありませんが、これらの概念を理解することにより、Networking をセットアップする役に立つでしょう。すべての Networking インストール環境は、コアプラグインとセキュリティグループプラグイン (またはただの No-Op セキュリティグループプラグイン) を使用します。さらに、Firewall-as-a-service (FWaaS) と Load-balancing-as-a-service (LBaaS) プラグインが利用可能です。"
+
+#: ./doc/install-guide/section_nova-networking-initial-network.xml5(title)
+msgid "Create initial network"
+msgstr "初期ネットワークの作成"
+
+#: ./doc/install-guide/section_nova-networking-initial-network.xml6(para)
+msgid ""
+"Before launching your first instance, you must create the necessary virtual "
+"network infrastructure to which the instance will connect. This network "
+"typically provides internet access <emphasis>from</emphasis> instances. You "
+"can enable internet access <emphasis>to</emphasis> individual instances "
+"using a <glossterm>floating IP address</glossterm> and suitable "
+"<glossterm>security group</glossterm> rules. The <literal>admin</literal> "
+"tenant owns this network because it provides external network access for "
+"multiple tenants."
+msgstr "インスタンスの起動前に、インスタンスが接続するために必要な仮想ネットワークを作成する必要があります。このネットワークは、一般的にインスタンス<emphasis>から</emphasis>インターネットにアクセスできます。<glossterm baseform=\"floating IP address\">Floating IP アドレス</glossterm>と<glossterm baseform=\"security group\">セキュリティグループ</glossterm>ルールを使用して、個々のインスタンス<emphasis>へと</emphasis>インターネットからアクセス可能にできます。<literal>admin</literal> プロジェクトは、複数のプロジェクトに対して外部ネットワークを提供するため、このネットワークを所有します。"
+
+#: ./doc/install-guide/section_nova-networking-initial-network.xml15(para)
+msgid ""
+"This network shares the same <glossterm>subnet</glossterm> associated with "
+"the physical network connected to the external "
+"<glossterm>interface</glossterm> on the compute node. You should specify an "
+"exclusive slice of this subnet to prevent interference with other devices on"
+" the external network."
+msgstr "このネットワークは、コンピュートノードの外部<glossterm baseform=\"interface\">インターフェース</glossterm> に接続された物理ネットワークと関連づけられた、同じ<glossterm baseform=\"subnet\">サブネット</glossterm>を共有します。外部ネットワークの他のデバイスと競合しないよう、このサブネットの専用範囲を指定すべきです。"
+
+#: ./doc/install-guide/section_nova-networking-initial-network.xml21(para)
+#: ./doc/install-guide/section_neutron-initial-networks.xml40(para)
+#: ./doc/install-guide/section_neutron-initial-networks.xml127(para)
+msgid "Perform these commands on the controller node."
+msgstr "これらのコマンドをコントローラーノードで実行します。"
+
+#: ./doc/install-guide/section_nova-networking-initial-network.xml24(title)
+msgid "To create the network"
+msgstr "ネットワークの作成方法"
+
+#: ./doc/install-guide/section_nova-networking-initial-network.xml26(para)
+#: ./doc/install-guide/section_neutron-initial-networks.xml45(para)
+msgid "Source the <literal>admin</literal> tenant credentials:"
+msgstr "<literal>admin</literal> プロジェクトのクレデンシャルを読み込みます。"
+
+#: ./doc/install-guide/section_nova-networking-initial-network.xml30(para)
+#: ./doc/install-guide/section_neutron-initial-networks.xml49(para)
+#: ./doc/install-guide/section_neutron-initial-networks.xml136(para)
+msgid "Create the network:"
+msgstr "ネットワークを作成します。"
+
+#: ./doc/install-guide/section_nova-networking-initial-network.xml31(para)
+msgid ""
+"Replace <replaceable>NETWORK_CIDR</replaceable> with the subnet associated "
+"with the physical network."
+msgstr "<replaceable>NETWORK_CIDR</replaceable> を物理ネットワークのサブネットに置き換えます。"
+
+#: ./doc/install-guide/section_nova-networking-initial-network.xml34(replaceable)
+msgid "NETWORK_CIDR"
+msgstr "NETWORK_CIDR"
+
+#: ./doc/install-guide/section_nova-networking-initial-network.xml35(para)
+msgid ""
+"For example, using an exclusive slice of <literal>203.0.113.0/24</literal> "
+"with IP address range <literal>203.0.113.24</literal> to "
+"<literal>203.0.113.32</literal>:"
+msgstr "例えば、IP アドレス <literal>203.0.113.24</literal> ～ <literal>203.0.113.32</literal> を持つ <literal>203.0.113.0/24</literal> の専用範囲を使用する場合:"
+
+#: ./doc/install-guide/section_nova-networking-initial-network.xml42(para)
+#: ./doc/install-guide/section_launch-instance-nova.xml26(para)
+#: ./doc/install-guide/section_launch-instance-neutron.xml26(para)
+#: ./doc/install-guide/section_launch-instance-neutron.xml245(para)
+msgid "This command provides no output."
+msgstr "このコマンドは何も出力しません。"
+
+#: ./doc/install-guide/section_nova-networking-initial-network.xml46(para)
+msgid "Verify creation of the network:"
+msgstr "ネットワークの作成を検証します。"
+
+#: ./doc/install-guide/ch_horizon.xml6(title)
+msgid "Add the dashboard"
+msgstr "Dashboard の追加"
+
+#: ./doc/install-guide/ch_horizon.xml7(para)
+msgid ""
+"The OpenStack dashboard, also known as <link "
+"href=\"https://github.com/openstack/horizon/\">Horizon</link>, is a Web "
+"interface that enables cloud administrators and users to manage various "
+"OpenStack resources and services."
+msgstr "OpenStack Dashboard は <link href=\"https://github.com/openstack/horizon/\">Horizon</link> としても知られ、クラウド管理者やユーザーがさまざまな OpenStack のリソースとサービスを管理できるようになるウェブインターフェースです。"
+
+#: ./doc/install-guide/ch_horizon.xml12(para)
+msgid ""
+"The dashboard enables web-based interactions with the OpenStack Compute "
+"cloud controller through the OpenStack APIs."
+msgstr "Dashboard は OpenStack API を経由して OpenStack Compute クラウドコントローラーとウェブベースで操作できます。"
+
+#: ./doc/install-guide/ch_horizon.xml15(para)
+msgid ""
+"These instructions show an example deployment configured with an Apache web "
+"server."
+msgstr "ここからの説明は Apache ウェブサーバーを用いて設定する導入例を示します。"
+
+#: ./doc/install-guide/ch_horizon.xml17(para)
+msgid ""
+"After you <link linkend=\"install_dashboard\">install and configure the "
+"dashboard</link>, you can complete the following tasks:"
+msgstr "<link linkend=\"install_dashboard\">Dashboard のインストールと設定</link>をした後、以下の作業を完了できます。"
+
+#: ./doc/install-guide/ch_horizon.xml22(para)
+msgid ""
+"Customize your dashboard. See section <link href=\"http://docs.openstack.org"
+"/admin-guide-cloud/content/ch_install-dashboard.html#dashboard-custom-"
+"brand\">Customize the dashboard</link> in the <link "
+"href=\"http://docs.openstack.org/admin-guide-"
+"cloud/content/\"><citetitle>OpenStack Cloud Administrator "
+"Guide</citetitle></link>."
+msgstr "Dashboard のカスタマイズ。<link href=\"http://docs.openstack.org/admin-guide-cloud/content/\"><citetitle>OpenStack クラウド管理者ガイド</citetitle></link>の <link href=\"http://docs.openstack.org/admin-guide-cloud/content/ch_install-dashboard.html#dashboard-custom-brand\">Dashboard のカスタマイズ</link>セクション参照。"
+
+#: ./doc/install-guide/ch_horizon.xml30(para)
+msgid ""
+"Set up session storage for the dashboard. See <xref linkend=\"dashboard-"
+"sessions\"/>."
+msgstr "Dashboard 用セッションストレージのセットアップ。<xref linkend=\"dashboard-sessions\"/> 参照。"
+
+#: ./doc/install-guide/ch_horizon.xml39(para)
+msgid ""
+"Your OpenStack environment now includes the dashboard. You can <link linkend"
+"=\"launch-instance\">launch an instance</link> or add more services to your "
+"environment in the following chapters."
+msgstr "OpenStack 環境にダッシュボードが追加されました。<link linkend=\"launch-instance\">インスタンスの起動</link>、以降の章に記載されているサービスの環境への追加を実行できます。"
+
+#: ./doc/install-guide/section_keystone-verify.xml6(title)
+msgid "Verify the Identity Service installation"
+msgstr "Identity Service のインストールの検証"
+
+#: ./doc/install-guide/section_keystone-verify.xml9(para)
+msgid ""
+"To verify that the Identity Service is installed and configured correctly, "
+"clear the values in the <envar>OS_SERVICE_TOKEN</envar> and "
+"<envar>OS_SERVICE_ENDPOINT</envar> environment variables:"
+msgstr "Identity Service が正しくインストールされ、設定されていることを確認するためには、<envar>OS_SERVICE_TOKEN</envar> 環境変数と <envar>OS_SERVICE_ENDPOINT</envar> 環境変数にある値を削除します。"
+
+#: ./doc/install-guide/section_keystone-verify.xml15(para)
+msgid ""
+"These variables, which were used to bootstrap the administrative user and "
+"register the Identity Service, are no longer needed."
+msgstr "管理ユーザーをブートストラップし、Identity Service に登録するために使用された、これらの変数はもはや必要ありません。"
+
+#: ./doc/install-guide/section_keystone-verify.xml20(para)
+msgid "You can now use regular user name-based authentication."
+msgstr "これで通常のユーザー名による認証を使用できます。"
+
+#: ./doc/install-guide/section_keystone-verify.xml22(para)
+msgid ""
+"Request a authentication token by using the <literal>admin</literal> user "
+"and the password you chose for that user:"
+msgstr "<literal>admin</literal> ユーザーと、そのユーザー用に選択したパスワードを使用して認証トークンを要求します。"
+
+#: ./doc/install-guide/section_keystone-verify.xml27(para)
+msgid ""
+"In response, you receive a token paired with your user ID. This verifies "
+"that the Identity Service is running on the expected endpoint and that your "
+"user account is established with the expected credentials."
+msgstr "応答で、ユーザー ID とペアになったトークンを受け取ります。これにより、Identity Service が期待したエンドポイントで実行されていて、ユーザーアカウントが期待したクレデンシャルで確立されていることを検証できます。"
+
+#: ./doc/install-guide/section_keystone-verify.xml33(para)
+msgid ""
+"Verify that authorization behaves as expected. To do so, request "
+"authorization on a tenant:"
+msgstr "認可が期待したとおり動作することを検証します。そうするために、プロジェクトで認可を要求します。"
+
+#: ./doc/install-guide/section_keystone-verify.xml38(para)
+msgid ""
+"In response, you receive a token that includes the ID of the tenant that you"
+" specified. This verifies that your user account has an explicitly defined "
+"role on the specified tenant and the tenant exists as expected."
+msgstr "応答で、指定したプロジェクトの ID を含むトークンを受け取ります。これにより、ユーザーアカウントが指定したプロジェクトで明示的に定義したロールを持ち、プロジェクトが期待したとおりに存在することを検証します。"
+
+#: ./doc/install-guide/section_keystone-verify.xml44(para)
+msgid ""
+"You can also set your <literal>--os-*</literal> variables in your "
+"environment to simplify command-line usage. Set up a <filename>admin-"
+"openrc.sh</filename> file with the admin credentials and admin endpoint:"
+msgstr "コマンドラインの使用を簡単にするために、お使いの環境で <literal>--os-*</literal> 変数を設定することもできます。admin クレデンシャルと admin エンドポイントを用いて <filename>admin-openrc.sh</filename> ファイルをセットアップします。"
+
+#: ./doc/install-guide/section_keystone-verify.xml54(para)
+msgid "Source this file to read in the environment variables:"
+msgstr "環境変数を読み込むために、このファイルを source します。"
+
+#: ./doc/install-guide/section_keystone-verify.xml59(para)
+msgid ""
+"Verify that your <filename>admin-openrc.sh</filename> file is configured "
+"correctly. Run the same command without the <literal>--os-*</literal> "
+"arguments:"
+msgstr "<filename>admin-openrc.sh</filename> ファイルが正しく設定されていることを検証します。同じコマンドを <literal>--os-*</literal> 引数なしで実行します。"
+
+#: ./doc/install-guide/section_keystone-verify.xml63(para)
+msgid ""
+"The command returns a token and the ID of the specified tenant. This "
+"verifies that you have configured your environment variables correctly."
+msgstr "コマンドはトークンと指定されたプロジェクトの ID を返します。これにより、環境変数が正しく設定されていることを確認します。"
+
+#: ./doc/install-guide/section_keystone-verify.xml68(para)
+msgid ""
+"Verify that your admin account has authorization to perform administrative "
+"commands:"
+msgstr "admin アカウントが管理コマンドを実行する権限があることを検証します。"
+
+#: ./doc/install-guide/section_keystone-verify.xml85(para)
+msgid ""
+"Seeing that the <literal>id</literal> in the output from the "
+"<placeholder-1/> command matches the <literal>user_id</literal> in the "
+"<placeholder-2/> command, and that the admin role is listed for that user, "
+"for the related tenant, this verifies that your user account has the "
+"<literal>admin</literal> role, which matches the role used in the Identity "
+"Service <filename>policy.json</filename> file."
+msgstr "<placeholder-1/> コマンドの出力の <literal>id</literal> が <placeholder-2/> コマンドの <literal>user_id</literal> と同じであること、admin ロールがそのユーザー、その関連プロジェクトに対して表示されることを確認します。これにより、お使いのユーザーアカウントが <literal>admin</literal> ロールを持つことを確認します。このロールは Identity Service の <filename>policy.json</filename> ファイルで使用されるロールと対応します。"
+
+#: ./doc/install-guide/section_keystone-verify.xml95(para)
+msgid ""
+"As long as you define your credentials and the Identity Service endpoint "
+"through the command line or environment variables, you can run all OpenStack"
+" client commands from any machine. For details, see <xref "
+"linkend=\"ch_clients\"/>."
+msgstr "コマンドラインや環境変数経由でクレデンシャルと Identity Service エンドポイントを定義する限り、すべてのマシンからすべての OpenStack クライアントコマンドを実行できます。詳細は <xref linkend=\"ch_clients\"/> を参照してください。"
+
 #: ./doc/install-guide/section_basics-packages.xml6(title)
 msgid "OpenStack packages"
 msgstr "OpenStack パッケージ"
@@ -859,266 +2592,996 @@ msgstr "パッケージは <code>Provides: python-argparse</code> ディレク
 msgid "This caveat applies to most OpenStack packages in Wheezy."
 msgstr "この注意事項は Wheezy 上の多くの OpenStack パッケージに適用されます。"
 
-#: ./doc/install-guide/section_basics-networking.xml6(title)
-msgid "Networking"
-msgstr "ネットワーク"
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml6(title)
+#: ./doc/install-guide/section_nova-networking-compute-node.xml5(title)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml6(title)
+msgid "Configure compute node"
+msgstr "コンピュートノードの設定"
 
-#: ./doc/install-guide/section_basics-networking.xml7(para)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml8(para)
 msgid ""
-"After installing the operating system on each node for the architecture that"
-" you choose to deploy, you must configure the network interfaces. We "
-"recommend that you disable any automated network management tools and "
-"manually edit the appropriate configuration files for your distribution. For"
-" more information on how to configure networking on your distribution, see "
-"the <link os=\"ubuntu\" href=\"https://help.ubuntu.com/lts/serverguide"
-"/network-configuration.html\">documentation.</link><link os=\"debian\" "
-"href=\"https://wiki.debian.org/NetworkConfiguration\">documentation.</link><link"
-" os=\"rhel;centos;fedora\" "
-"href=\"https://access.redhat.com/site/documentation/en-"
-"US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s1-networkscripts-"
-"interfaces.html\">documentation.</link><link os=\"sles;opensuse\" "
-"href=\"https://www.suse.com/documentation/sles11/book_sle_admin/data/sec_basicnet_manconf.html\">SLES"
-" 11</link><phrase os=\"sles;opensuse\"> or </phrase><link "
-"os=\"sles;opensuse\" href=\"http://activedoc.opensuse.org/book/opensuse-"
-"reference/chapter-13-basic-networking\">openSUSE documentation.</link>"
-msgstr "導入するアーキテクチャーに合わせて、各ノードにオペレーティングシステムをインストールした後、ネットワークインターフェースを設定する必要があります。すべての自動ネットワーク管理ツールを無効化し、お使いのディストリビューションに合わせて適切な設定ファイルを手動で編集することを推奨します。お使いのディストリビューションでネットワークを設定する方法に関する詳細は、<link os=\"ubuntu\" href=\"https://help.ubuntu.com/lts/serverguide/network-configuration.html\">ドキュメント</link><link os=\"debian\" href=\"https://wiki.debian.org/NetworkConfiguration\">ドキュメント</link><link os=\"rhel;centos;fedora\" href=\"https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s1-networkscripts-interfaces.html\">ドキュメント</link><link os=\"sles;opensuse\" href=\"https://www.suse.com/documentation/sles11/book_sle_admin/data/sec_basicnet_manconf.html\">SLES 11</link><phrase os=\"sles;opensuse\"> または </phrase><link os=\"sles;opensuse\" href=\"http://activedoc.opensuse.org/book/opensuse-reference/chapter-13-basic-networking\">openSUSE のドキュメント</link>を参照してください。"
+"This section details set up for any node that runs the <literal>nova-"
+"compute</literal> component but does not run the full network stack."
+msgstr "このセクションは <literal>nova-compute</literal> コンポーネントを実行するあらゆるノードのセットアップについて詳細に説明しますが、すべてのネットワークスタックを実行しません。"
 
-#: ./doc/install-guide/section_basics-networking.xml30(title)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml13(para)
 msgid ""
-"To disable <systemitem class=\"service\">NetworkManager</systemitem> and "
-"enable the <systemitem class=\"service\">network</systemitem> service:"
-msgstr "<systemitem class=\"service\">NetworkManager</systemitem> を無効化し、<systemitem class=\"service\">network</systemitem> サービスを有効化する方法:"
+"By default, the <literal>system-config-firewall</literal> automated firewall"
+" configuration tool is in place on RHEL. This graphical interface (and a "
+"curses-style interface with <literal>-tui</literal> on the end of the name) "
+"enables you to configure IP tables as a basic firewall. You should disable "
+"it when you work with OpenStack Networking unless you are familiar with the "
+"underlying network technologies, as, by default, it blocks various types of "
+"network traffic that are important to neutron services. To disable it, "
+"launch the program and clear the <guilabel>Enabled</guilabel> check box."
+msgstr "<literal>system-config-firewall</literal> 自動ファイアウォール設定ツールが RHEL にデフォルトで入っています。このグラフィカルツール (および名前の最後に <literal>-tui</literal> を付けた端末スタイルのインターフェース) により、基本的なファイアウォールとして iptables を設定できます。基礎となるネットワーク技術に詳しくなければ、OpenStack Networking を利用しているときに、これを無効化すべきです。これは neutron サービスにとって重要であるさまざまな種類のネットワーク通信を遮断するためです。これを無効化する場合、プログラムを起動し、<guilabel>有効化</guilabel>チェックボックスを解除します。"
 
-#: ./doc/install-guide/section_basics-networking.xml41(title)
-msgid "To disable <systemitem class=\"service\">NetworkManager</systemitem>:"
-msgstr "<systemitem class=\"service\">NetworkManager</systemitem> を無効化する方法:"
-
-#: ./doc/install-guide/section_basics-networking.xml43(para)
-msgid "Use the YaST network module:"
-msgstr "YaST ネットワークモジュールを使用します。"
-
-#: ./doc/install-guide/section_basics-networking.xml45(para)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml22(para)
 msgid ""
-"For more information, see the <link "
-"href=\"https://www.suse.com/documentation/sles11/book_sle_admin/data/sec_nm_activate.html\">SLES"
-" </link> or the <link href=\"http://activedoc.opensuse.org/book/opensuse-"
-"reference/chapter-13-basic-networking#sec.basicnet.yast.netcard.global\"> "
-"openSUSE documentation</link>."
-msgstr "詳細は <link href=\"https://www.suse.com/documentation/sles11/book_sle_admin/data/sec_nm_activate.html\">SLES</link> または <link href=\"http://activedoc.opensuse.org/book/opensuse-reference/chapter-13-basic-networking#sec.basicnet.yast.netcard.global\">openSUSE</link> のドキュメントを参照してください。"
+"After you successfully set up OpenStack Networking with Neutron, you can re-"
+"enable and configure the tool. However, during OpenStack Networking setup, "
+"disable the tool to make it easier to debug network issues."
+msgstr "Neutron を用いて OpenStack Networking を正常にセットアップした後、ツールを再び有効化し、設定できます。しかしながら、OpenStack Networking のセットアップ中は、ネットワークの問題をデバッグしやすくするためにツールを無効化します。"
 
-#: ./doc/install-guide/section_basics-networking.xml53(para)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml28(title)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml8(title)
+#: ./doc/install-guide/section_trove-install.xml7(title)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml8(title)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml24(title)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml8(title)
+msgid "Prerequisites"
+msgstr "前提"
+
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml30(para)
 msgid ""
-"RHEL and derivatives including CentOS and Scientific Linux enable a "
-"restrictive <glossterm>firewall</glossterm> by default. During this "
-"installation, certain steps will fail unless you alter or disable the "
-"firewall. For further information about securing your installation, refer to"
-" the <link href=\"http://docs.openstack.org/sec/\"> OpenStack Security "
-"Guide</link>."
-msgstr "RHEL および、CentOS や Scientific Linux のような派生物は、標準で制限的な<glossterm baseform=\"firewall\">ファイアウォール</glossterm>を有効化しています。このインストール中に、この設定を変更するか、ファイアウォールを無効化しなければ、特定の手順が失敗します。インストール環境をセキュア化することに関する詳細は <link href=\"http://docs.openstack.org/sec/\">OpenStack セキュリティガイド</link> を参照してください。"
+"Disable packet destination filtering (route verification) to let the "
+"networking services route traffic to the VMs. Edit the "
+"<filename>/etc/sysctl.conf</filename> file and run the following command to "
+"activate changes:"
+msgstr "Networking Service が仮想マシンへの通信をルーティングできるように、パケット宛先フィルタリング (ルート検証) を無効化します。<filename>/etc/sysctl.conf</filename> を編集し、変更を有効化するために以下のコマンドを実行します。"
 
-#: ./doc/install-guide/section_basics-networking.xml60(para)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml41(title)
+msgid "Install Open vSwitch plug-in"
+msgstr "Open vSwitch プラグインのインストール"
+
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml42(para)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml185(para)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml176(para)
 msgid ""
-"On Fedora, <literal>firewalld</literal> replaces <literal>iptables</literal>"
-" as the default firewall system. While you can use "
-"<literal>firewalld</literal> successfully, this guide references "
-"<literal>iptables</literal> for compatibility with other distributions."
-msgstr "Fedora の場合、<literal>firewalld</literal> が標準のファイアウォールシステムとして <literal>iptables</literal> の代わりに使用されています。<literal>firewalld</literal> を正常に使用できている限り、このガイドは他のディストリビューションとの互換性のために <literal>iptables</literal> を参照しています。"
+"OpenStack Networking supports a variety of plug-ins. For simplicity, we "
+"chose to cover the most common plug-in, Open vSwitch, and configure it to "
+"use basic GRE tunnels for tenant network traffic."
+msgstr "OpenStack Networking はさまざまなプラグインをサポートします。簡単のために、最も一般的なプラグイン Open vSwitch を取り扱うことにし、プロジェクトのネットワーク通信のために基本的な GRE トンネルを使用するよう設定します。"
 
-#: ./doc/install-guide/section_basics-networking.xml66(title)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml47(para)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml181(para)
+msgid "Install the Open vSwitch plug-in and its dependencies:"
+msgstr "Open vSwitch プラグインと依存パッケージをインストールします。"
+
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml54(para)
+msgid "Restart Open vSwitch:"
+msgstr "Open vSwitch を再起動します。"
+
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml58(para)
+msgid "Start Open vSwitch and configure it to start when the system boots:"
+msgstr "Open vSwitch を起動し、システム起動時に起動するよう設定します。"
+
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml66(para)
 msgid ""
-"To disable <literal>firewalld</literal> and enable "
-"<literal>iptables</literal>:"
-msgstr "<literal>firewalld</literal> を無効化し、<literal>iptables</literal> を有効化する方法:"
+"You must set some common configuration options no matter which networking "
+"technology you choose to use with Open vSwitch. You must add the <literal"
+">br-int</literal> integration bridge, which connects to the VMs."
+msgstr "どのネットワーク技術を Open vSwitch と一緒に使用するかによらず、いくつかの共通設定オプションを設定する必要があります。仮想マシンを接続する <literal>br-int</literal> 統合ブリッジを追加する必要があります。"
 
-#: ./doc/install-guide/section_basics-networking.xml75(para)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml74(para)
 msgid ""
-"Proceed to network configuration for the example <link linkend=\"basics-"
-"networking-neutron\">OpenStack Networking (neutron) </link> or <link linkend"
-"=\"basics-networking-nova\">legacy networking (nova-network)</link> "
-"architecture."
-msgstr "<link linkend=\"basics-networking-neutron\">OpenStack Networking (neutron) </link> または <link linkend=\"basics-networking-nova\">レガシーネットワーク (nova-network)</link> のアーキテクチャ例のネットワーク設定に進みます。"
+"You must set some common configuration options. You must configure "
+"Networking core to use <acronym>OVS</acronym>. Edit the "
+"<filename>/etc/neutron/neutron.conf</filename> file:"
+msgstr "どのネットワーク技術を <acronym>OVS</acronym> と一緒に使用するかによらず、いくつかの共通設定オプションを設定する必要があります。<filename>/etc/neutron/neutron.conf</filename> ファイルを編集します。"
 
-#: ./doc/install-guide/section_cinder-verify.xml5(title)
-msgid "Verify the Block Storage installation"
-msgstr "Block Storage のインストールの検証"
-
-#: ./doc/install-guide/section_cinder-verify.xml6(para)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml83(para)
 msgid ""
-"To verify that the Block Storage is installed and configured properly, "
-"create a new volume."
-msgstr "Block Storage が正しくインストールされ、設定されたことを確認するために、新しいボリュームを作成します。"
+"You must configure a firewall as well. You should use the same firewall "
+"plug-in that you chose to use when you set up the network node. To do this, "
+"edit "
+"<filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename>"
+" file and set the <literal>firewall_driver</literal> value under the "
+"<literal>securitygroup</literal> to the same value used on the network node."
+" For instance, if you chose to use the Hybrid OVS-IPTables plug-in, your "
+"configuration looks like this:"
+msgstr "同様にファイアウォールを設定する必要があります。ネットワークノードをセットアップするときに選択したものと同じファイアウォールプラグインを使用すべきです。そうするために、<filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename> ファイルを編集し、<literal>securitygroup</literal> の下にある <literal>firewall_driver</literal> 値をネットワークノードで使用したものと同じ値に設定します。例えば、ハイブリッド OVS iptables プラグインを使用したい場合、設定はこのようになるでしょう。"
 
-#: ./doc/install-guide/section_cinder-verify.xml8(para)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml96(para)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml313(para)
 msgid ""
-"For more information about how to manage volumes, see the <link "
-"href=\"http://docs.openstack.org/user-"
-"guide/content/index.html\"><citetitle>OpenStack User "
-"Guide</citetitle></link>."
-msgstr "ボリュームの管理に関する詳細は、<link href=\"http://docs.openstack.org/user-guide/content/index.html\"><citetitle>OpenStack ユーザーガイド</citetitle></link>を参照してください。"
+"You must use at least the No-Op firewall. Otherwise, Horizon and other "
+"OpenStack services cannot get and set required VM boot options."
+msgstr "少なくとも No-Op ファイアウォールを使用する必要があります。そうでなければ、Horizon と他の OpenStack サービスが必要となる仮想マシンのブートオプションを取得および設定できません。"
 
-#: ./doc/install-guide/section_cinder-verify.xml13(para)
-msgid "Source the <filename>demo-openrc.sh</filename> file:"
-msgstr "<filename>demo-openrc.sh</filename> ファイルを読み込みます。"
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml102(para)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml319(para)
+msgid "Configure the <acronym>OVS</acronym> plug-in to start on boot."
+msgstr "<acronym>OVS</acronym> プラグインをシステム起動時に起動するよう設定します。"
 
-#: ./doc/install-guide/section_cinder-verify.xml18(para)
-msgid "Use the <placeholder-1/> command to create a new volume:"
-msgstr "新しいボリュームを作成するために、<placeholder-1/> コマンドを使用します。"
-
-#: ./doc/install-guide/section_cinder-verify.xml40(para)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml108(para)
 msgid ""
-"Make sure that the volume has been correctly created with the "
-"<placeholder-1/> command:"
-msgstr "ボリュームが正常に作成されたことを、<placeholder-1/> コマンドを用いて確認します。"
+"Tell the <acronym>OVS</acronym> plug-in to use GRE tunneling with a <literal"
+">br-int</literal> integration bridge, a <literal>br-tun</literal> tunneling "
+"bridge, and a local IP for the tunnel of "
+"<replaceable>DATA_INTERFACE</replaceable>'s IP Edit the "
+"<filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename>"
+" file:"
+msgstr "<literal>br-int</literal> 統合ブリッジを持つ GRE トンネリング、<literal>br-tun</literal> トンネリングブリッジ、<replaceable>DATA_INTERFACE</replaceable> の IP のトンネル用ローカル IP を使用するよう <acronym>OVS</acronym> プラグインに通知します。<filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename> ファイルを編集します。"
 
-#: ./doc/install-guide/section_cinder-verify.xml48(para)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml123(replaceable)
+msgid "DATA_INTERFACE_IP"
+msgstr "DATA_INTERFACE_IP"
+
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml127(title)
+msgid "Configure common components"
+msgstr "共通コンポーネントの設定"
+
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml129(para)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml82(para)
 msgid ""
-"If the status value is not <literal>available</literal>, the volume creation"
-" failed. Check the log files in the <filename>/var/log/cinder/</filename> "
-"directory on the controller and volume nodes to get information about the "
-"failure."
-msgstr "状態が「 <literal>利用可能 (available)</literal>」でなければ、ボリュームの作成が失敗しています。失敗に関する情報を取得するために、コントローラーノードとボリュームノードの <filename>/var/log/cinder/</filename> にあるログファイルを確認してください。"
+"Configure Networking to use <systemitem "
+"class=\"service\">keystone</systemitem> for authentication:"
+msgstr "Networking が認証用に <systemitem class=\"service\">keystone</systemitem> を使用するよう設定します。"
 
-#: ./doc/install-guide/section_glance-verify.xml5(title)
-msgid "Verify the Image Service installation"
-msgstr "Image Service のインストールの検証"
-
-#: ./doc/install-guide/section_glance-verify.xml6(para)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml132(para)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml166(para)
 msgid ""
-"To test the Image Service installation, download at least one virtual "
-"machine image that is known to work with OpenStack. For example, CirrOS is a"
-" small test image that is often used for testing OpenStack deployments "
-"(<link href=\"http://download.cirros-cloud.net/\">CirrOS downloads</link>). "
-"This walk through uses the 64-bit CirrOS QCOW2 image."
-msgstr "Image Service のインストールをテストするために、OpenStack で動作することが知られている仮想マシンイメージを何かしらダウンロードします。例えば、CirrOS  (<link href=\"http://download.cirros-cloud.net/\">CirrOS ダウンロード</link>) は OpenStack 環境をテストするためによく使用される小さなテストイメージです。ここでは  64 ビット CirrOS QCOW2 イメージを使用します。"
+"Set the <literal>auth_strategy</literal> configuration key to "
+"<literal>keystone</literal> in the <literal>[DEFAULT]</literal> section of "
+"the file:"
+msgstr "このファイルの <literal>[DEFAULT]</literal> セクションで <literal>auth_strategy</literal> 設定キーを <literal>keystone</literal> に設定します。"
 
-#: ./doc/install-guide/section_glance-verify.xml13(para)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml138(para)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml95(para)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml91(para)
 msgid ""
-"For more information about how to download and build images, see <link "
-"href=\"http://docs.openstack.org/image-"
-"guide/content/index.html\"><citetitle>OpenStack Virtual Machine Image "
-"Guide</citetitle></link>. For information about how to manage images, see "
-"the <link href=\"http://docs.openstack.org/user-"
-"guide/content/index.html\"><citetitle>OpenStack User "
-"Guide</citetitle></link>."
-msgstr "ダウンロード方法とイメージ構築の詳細は<link href=\"http://docs.openstack.org/image-guide/content/index.html\"><citetitle>OpenStack 仮想マシンイメージガイド</citetitle></link>を参照してください。イメージの管理方法の詳細は<link href=\"http://docs.openstack.org/user-guide/content/index.html\"><citetitle>OpenStack ユーザーガイド</citetitle></link>を参照してください。"
+"Set the <systemitem class=\"service\">neutron</systemitem> configuration for"
+" <systemitem class=\"service\">keystone</systemitem> authentication:"
+msgstr "<systemitem class=\"service\">keystone</systemitem> 認証用に <systemitem class=\"service\">neutron</systemitem> を設定します。"
 
-#: ./doc/install-guide/section_glance-verify.xml24(para)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml155(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml185(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml240(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml257(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml74(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml100(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml302(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml332(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml33(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml151(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml177(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml384(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml414(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml46(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml110(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml139(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml237(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml254(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml77(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml103(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml277(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml304(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml109(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml136(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml393(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml407(replaceable)
+msgid "NEUTRON_PASS"
+msgstr "NEUTRON_PASS"
+
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml160(para)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml113(para)
 msgid ""
-"Download the image into a dedicated directory using <placeholder-1/> or "
-"<placeholder-2/>:"
-msgstr "<placeholder-1/> や <placeholder-2/> を使用して、イメージを専用のディレクトリにダウンロードします。"
+"To configure <systemitem class=\"service\">neutron</systemitem> to use "
+"<systemitem class=\"service\">keystone</systemitem> for authentication, edit"
+" the <filename>/etc/neutron/neutron.conf</filename> file."
+msgstr "認証に <systemitem class=\"service\">keystone</systemitem> を使用するよう <systemitem class=\"service\">neutron</systemitem> を設定するために <filename>/etc/neutron/neutron.conf</filename> ファイルを編集します。"
 
-#: ./doc/install-guide/section_glance-verify.xml32(para)
-msgid "Upload the image to the Image Service:"
-msgstr "イメージを Image Service にアップロードします。"
-
-#: ./doc/install-guide/section_glance-verify.xml33(replaceable)
-#: ./doc/install-guide/section_glance-verify.xml38(replaceable)
-msgid "IMAGELABEL"
-msgstr "IMAGELABEL"
-
-#: ./doc/install-guide/section_glance-verify.xml33(replaceable)
-#: ./doc/install-guide/section_glance-verify.xml45(replaceable)
-msgid "FILEFORMAT"
-msgstr "FILEFORMAT"
-
-#: ./doc/install-guide/section_glance-verify.xml34(replaceable)
-#: ./doc/install-guide/section_glance-verify.xml65(replaceable)
-msgid "CONTAINERFORMAT"
-msgstr "CONTAINERFORMAT"
-
-#: ./doc/install-guide/section_glance-verify.xml34(replaceable)
-#: ./doc/install-guide/section_glance-verify.xml86(replaceable)
-msgid "ACCESSVALUE"
-msgstr "ACCESSVALUE"
-
-#: ./doc/install-guide/section_glance-verify.xml34(replaceable)
-#: ./doc/install-guide/section_glance-verify.xml101(replaceable)
-msgid "IMAGEFILE"
-msgstr "IMAGEFILE"
-
-#: ./doc/install-guide/section_glance-verify.xml35(para)
-msgid "Where:"
-msgstr "各項目:"
-
-#: ./doc/install-guide/section_glance-verify.xml40(para)
-msgid "Arbitrary label. The name by which users refer to the image."
-msgstr "任意のラベル。ユーザーがイメージを参照する名前。"
-
-#: ./doc/install-guide/section_glance-verify.xml47(para)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml174(para)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml125(para)
 msgid ""
-"Specifies the format of the image file. Valid formats include "
-"<literal>qcow2</literal>, <literal>raw</literal>, <literal>vhd</literal>, "
-"<literal>vmdk</literal>, <literal>vdi</literal>, <literal>iso</literal>, "
-"<literal>aki</literal>, <literal>ari</literal>, and <literal>ami</literal>."
-msgstr "イメージファイルの形式を指定します。有効な形式は <literal>qcow2</literal>, <literal>raw</literal>, <literal>vhd</literal>, <literal>vmdk</literal>, <literal>vdi</literal>, <literal>iso</literal>, <literal>aki</literal>, <literal>ari</literal>, <literal>ami</literal> です。"
+"Add these lines to the <literal>[keystone_authtoken]</literal> section of "
+"the file:"
+msgstr "このファイルの <literal>[keystone_authtoken]</literal> セクションにこれらの行を追加します。"
 
-#: ./doc/install-guide/section_glance-verify.xml58(para)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml190(para)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml144(para)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml141(para)
+msgid "Configure access to the <application>RabbitMQ</application> service:"
+msgstr "<application>RabbitMQ</application> サービスのアクセス権を設定します。"
+
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml201(para)
 msgid ""
-"You can verify the format using the <placeholder-1/> command: "
-"<placeholder-2/>"
-msgstr "<placeholder-1/> コマンドを使用して形式を確認できます。 <placeholder-2/>"
+"Configure the <application>RabbitMQ</application> access. Edit the "
+"<filename>/etc/neutron/neutron.conf</filename> file to modify the following "
+"parameters in the <literal>[DEFAULT]</literal> section."
+msgstr "<application>RabbitMQ</application> のアクセス権を設定します。<literal>[DEFAULT]</literal> セクションにある以下のパラメーターを変更するために、<filename>/etc/neutron/neutron.conf</filename> ファイルを編集します。"
 
-#: ./doc/install-guide/section_glance-verify.xml67(para)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml210(para)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml156(para)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml161(para)
+msgid "Configure access to the <application>Qpid</application> message queue:"
+msgstr "<application>Qpid</application> メッセージキューのアクセス権を設定します。"
+
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml218(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml220(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml165(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml167(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml169(replaceable)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml171(replaceable)
+msgid "guest"
+msgstr "guest"
+
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml224(title)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml220(title)
+msgid "Configure Compute services for Networking"
+msgstr "Compute サービスの Networking 用設定"
+
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml226(para)
 msgid ""
-"Specifies the container format. Valid formats include: "
-"<literal>bare</literal>, <literal>ovf</literal>, <literal>aki</literal>, "
-"<literal>ari</literal> and <literal>ami</literal>."
-msgstr "コンテナーの形式を指定します。有効な形式は <literal>bare</literal>, <literal>ovf</literal>, <literal>aki</literal>, <literal>ari</literal>, <literal>ami</literal> です。"
+"Configure OpenStack Compute to use OpenStack Networking services. Configure "
+"the <filename>/etc/nova/nova.conf</filename> file as per instructions below:"
+msgstr "OpenStack Compute が OpenStack Networking Service を使用するよう設定します。以下のそれぞれの説明にあるとおり、<filename>/etc/nova/nova.conf</filename> ファイルを編集します。"
 
-#: ./doc/install-guide/section_glance-verify.xml73(para)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml249(para)
 msgid ""
-"Specify <literal>bare</literal> to indicate that the image file is not in a "
-"file format that contains metadata about the virtual machine. Although this "
-"field is currently required, it is not actually used by any of the OpenStack"
-" services and has no effect on system behavior. Because the value is not "
-"used anywhere, it is safe to always specify <literal>bare</literal> as the "
-"container format."
-msgstr "仮想マシンに関するメタデータを含むイメージファイルがファイル形式ではないことを示すために <literal>bare</literal> を指定します。この項目が現在必須となっていますが、実際はすべての OpenStack により使用されるわけではなく、システム動作に影響を与えません。この値がどこでも使用されないため、常に <literal>bare</literal> をコンテナー形式として指定すると安全です。"
+"Configure OpenStack Compute to use OpenStack Networking services. Edit the "
+"<filename>/etc/nova/nova.conf</filename> file:"
+msgstr "OpenStack Compute が OpenStack Networking Service を使用するよう設定します。<filename>/etc/nova/nova.conf</filename> ファイルを編集します。"
 
-#: ./doc/install-guide/section_glance-verify.xml90(para)
-msgid "true - All users can view and use the image."
-msgstr "true - すべてのユーザーがイメージを表示および使用できます。"
-
-#: ./doc/install-guide/section_glance-verify.xml94(para)
-msgid "false - Only administrators can view and use the image."
-msgstr "false - 管理者のみがイメージを表示および使用できます。"
-
-#: ./doc/install-guide/section_glance-verify.xml88(para)
-msgid "Specifies image access: <placeholder-1/>"
-msgstr "イメージのアクセス権を指定します。 <placeholder-1/>"
-
-#: ./doc/install-guide/section_glance-verify.xml103(para)
-msgid "Specifies the name of your downloaded image file."
-msgstr "ダウンロードしたイメージファイルの名前を指定します。"
-
-#: ./doc/install-guide/section_glance-verify.xml108(para)
-#: ./doc/install-guide/section_glance-verify.xml157(para)
-msgid "For example:"
-msgstr "例:"
-
-#: ./doc/install-guide/section_glance-verify.xml133(para)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml265(para)
 msgid ""
-"Because the returned image ID is generated dynamically, your deployment "
-"generates a different ID than the one shown in this example."
-msgstr "返されたイメージ ID は動的に変更されるため、導入環境によりこの例で示されているものと異なる ID が生成されます。"
+"No matter which firewall driver you chose when you configured the network "
+"and compute nodes, you must edit the "
+"<filename>/etc/nova/nova.conf</filename> file to set the firewall driver to "
+"<literal>nova.virt.firewall.NoopFirewallDriver</literal>. Because OpenStack "
+"Networking handles the firewall, this statement instructs Compute to not use"
+" a firewall."
+msgstr "ネットワークとコンピュートノードを設定するときに、どのファイアウォールドライバーを選択しても、ファイアウォールドライバーを <literal>nova.virt.firewall.NoopFirewallDriver</literal> に設定するために、<filename>/etc/nova/nova.conf</filename> ファイルを編集する必要があります。OpenStack Networking はファイアウォールを取り扱うので、このステートメントは Compute がファイアウォールを使用しないことを指定します。"
 
-#: ./doc/install-guide/section_glance-verify.xml139(para)
-msgid "Confirm that the image was uploaded and display its attributes:"
-msgstr "イメージがアップロードされたことを確認し、その属性を表示します。"
-
-#: ./doc/install-guide/section_glance-verify.xml149(para)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml275(para)
 msgid ""
-"You can now remove the locally downloaded image, since it is stored and "
-"available through the Image Service."
-msgstr "これで Image Service に保存され、そこから利用できるため、ローカルにダウンロードしたイメージを削除できます。"
+"If you want Networking to handle the firewall, edit the "
+"<filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename>"
+" file to set the <code>firewall_driver</code> option to the firewall for the"
+" plug-in. For example, with <acronym>OVS</acronym>, edit the file as "
+"follows:"
+msgstr "Networking にファイアウォールを取り扱わせたい場合、<code>firewall_driver</code> オプションをプラグイン用のファイアウォールに設定するために、<filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename> ファイルを編集します。例えば、<acronym>OVS</acronym> を使用する場合、ファイルを次のとおり編集します。"
 
-#: ./doc/install-guide/section_glance-verify.xml156(para)
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml290(para)
 msgid ""
-"Alternatively, the upload to the Image Service can be done without having to"
-" use local disk space to store the file, by use of the <parameter>--copy-"
-"from</parameter> parameter."
-msgstr "代わりに、Image Service にアップロードしたものは、<parameter>--copy-from</parameter> パラメーターを使用することにより、ファイルを保存するためのローカルディスク領域を使用する必要なく実行できます。"
+"If you do not want to use a firewall in Compute or Networking, edit both "
+"configuration files and set "
+"<code>firewall_driver=nova.virt.firewall.NoopFirewallDriver</code>. Also, "
+"edit the <filename>/etc/nova/nova.conf</filename> file and comment out or "
+"remove the <code>security_group_api=neutron</code> statement."
+msgstr "Compute や Networking でファイアウォールを使用したくない場合、両方の設定ファイルを編集し、<code>firewall_driver=nova.virt.firewall.NoopFirewallDriver</code> を設定します。また、<filename>/etc/nova/nova.conf</filename> ファイルを編集し、<code>security_group_api=neutron</code> ステートメントをコメントアウトまたは削除します。"
+
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml298(para)
+msgid ""
+"Otherwise, when you issue <placeholder-1/> commands, the <errortext>ERROR: "
+"The server has either erred or is incapable of performing the requested "
+"operation. (HTTP 500)</errortext> error might be returned."
+msgstr "そうしなければ、<placeholder-1/> コマンドを実行したとき、<errortext>ERROR: The server has either erred or is incapable of performing the requested operation. (HTTP 500)</errortext> エラーが返されるでしょう。"
+
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml309(title)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml322(title)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml432(title)
+msgid "Finalize installation"
+msgstr "インストールの完了"
+
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml311(para)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml298(para)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml434(para)
+msgid ""
+"The <systemitem class=\"service\">neutron-server</systemitem> initialization"
+" script expects a symbolic link <filename>/etc/neutron/plugin.ini</filename>"
+" pointing to the configuration file associated with your chosen plug-in. "
+"Using Open vSwitch, for example, the symbolic link must point to "
+"<filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename>."
+" If this symbolic link does not exist, create it using the following "
+"commands:"
+msgstr "<systemitem class=\"service\">neutron-server</systemitem> 初期化スクリプトは、選択したプラグインと関連する設定ファイルを指し示すシンボリックリンク <filename>/etc/neutron/plugin.ini</filename> を予期しています。例えば、Open vSwitch を使用する場合、シンボリックリンクが <filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename> を指し示す必要があります。このシンボリックリンクが存在しなければ、以下のコマンドを使用して作成します。"
+
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml323(para)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml310(para)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml446(para)
+msgid ""
+"The <systemitem class=\"service\">openstack-neutron</systemitem> "
+"initialization script expects the variable "
+"<literal>NEUTRON_PLUGIN_CONF</literal> in file "
+"<filename>/etc/sysconfig/neutron</filename> to reference the configuration "
+"file associated with your chosen plug-in. Using Open vSwitch, for example, "
+"edit the <filename>/etc/sysconfig/neutron</filename> file and add the "
+"following:"
+msgstr "<systemitem class=\"service\">neutron-server</systemitem> 初期化スクリプトは、<filename>/etc/sysconfig/neutron</filename> の <literal>NEUTRON_PLUGIN_CONF</literal> 変数が、選択したプラグインと関連づけられた設定ファイルを参照していることを予期します。例えば、Open vSwitch を使用する場合、<filename>/etc/sysconfig/neutron</filename> ファイルを編集し、以下を追加します。"
+
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml334(para)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml457(para)
+msgid "Restart Networking services."
+msgstr "Networking サービスを再起動します。"
+
+#: ./doc/install-guide/section_neutron-ovs-compute-node.xml340(para)
+msgid "Restart the Compute service."
+msgstr "Compute Service を再起動します。"
+
+#: ./doc/install-guide/section_debconf-preseeding.xml6(title)
+msgid "Pre-seed debconf prompts"
+msgstr "事前シード debconf プロンプト"
+
+#: ./doc/install-guide/section_debconf-preseeding.xml7(para)
+msgid ""
+"You can pre-seed all <systemitem class=\"library\">debconf</systemitem> "
+"prompts. To pre-seed means to store responses in the "
+"<package>debconf</package> database so that <package>debconf</package> does "
+"not prompt the user for responses. Pre-seeding enables a hands-free "
+"installation for users. The package maintainer creates scripts that "
+"automatically configure the services."
+msgstr "すべての <systemitem class=\"library\">debconf</systemitem> プロンプトに事前シードできます。事前シードとは <package>debconf</package> がユーザーにプロンプトを表示しないよう、<package>debconf</package> データベースに応答を保存することを意味します。事前シードによりユーザーの手がかからないインストールをできるようになります。パッケージのメンテナーがサービスを自動的に設定できるスクリプトを作成します。"
+
+#: ./doc/install-guide/section_debconf-preseeding.xml14(para)
+msgid ""
+"The following example shows how to pre-seed an automated MySQL Server "
+"installation:"
+msgstr "以下の例は MySQL サーバーの自動インストールを事前シードする方法を示します。"
+
+#: ./doc/install-guide/section_debconf-preseeding.xml16(replaceable)
+#: ./doc/install-guide/section_debconf-preseeding.xml17(replaceable)
+#: ./doc/install-guide/section_debconf-preseeding.xml19(replaceable)
+msgid "MYSQL_PASSWORD"
+msgstr "MYSQL_PASSWORD"
+
+#: ./doc/install-guide/section_debconf-preseeding.xml23(para)
+msgid ""
+"The <code>seen true</code> option tells <package>debconf</package> that a "
+"specified screen was already seen by the user so do not show it again. This "
+"option is useful for upgrades."
+msgstr "<code>seen true</code> オプションにより、指定された画面がすでにユーザーにより参照されたことを <package>debconf</package> に通知します。そのため、それを再び表示しません。このオプションはアップグレードのために有用です。"
+
+#: ./doc/install-guide/section_ceilometer-install.xml10(title)
+msgid "Install the Telemetry module"
+msgstr "Telemetry モジュールのインストール"
+
+#: ./doc/install-guide/section_ceilometer-install.xml12(para)
+msgid ""
+"Telemetry provides an API service that provides a collector and a range of "
+"disparate agents. Before you can install these agents on nodes such as the "
+"compute node, you must use this procedure to install the core components on "
+"the controller node."
+msgstr "Telemetry は情報収集機能とさまざまな種類のエージェントを提供する API サービスです。コンピュートノードのようなノードにこれらのエージェントをインストールする前に、コントローラーノードにコアコンポーネントをインストールするために、この手順を使用する必要があります。"
+
+#: ./doc/install-guide/section_ceilometer-install.xml18(para)
+msgid "Install the Telemetry service on the controller node:"
+msgstr "コントローラーノードに Telemetry Service をインストールします。"
+
+#: ./doc/install-guide/section_ceilometer-install.xml30(para)
+msgid ""
+"Respond to the prompts for <link linkend=\"debconf-"
+"keystone_authtoken\"><literal>[keystone_authtoken]</literal> "
+"settings</link>, <link linkend=\"debconf-rabbitqm\">RabbitMQ "
+"credentials</link> and <link linkend=\"debconf-api-endpoints\">API "
+"endpoint</link> registration."
+msgstr "<link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> 設定</link>、<link linkend=\"debconf-rabbitqm\">RabbitMQ クレデンシャル</link>、<link linkend=\"debconf-api-endpoints\">API エンドポイント</link>の登録に関するプロンプトに答えます。"
+
+#: ./doc/install-guide/section_ceilometer-install.xml38(para)
+msgid ""
+"The Telemetry service uses a database to store information. Specify the "
+"location of the database in the configuration file. The examples use a "
+"MongoDB database on the controller node:"
+msgstr "Telemetry Service は情報を保存するためにデータベースを使用します。設定ファイルでデータベースの場所を指定します。この例はコントローラーノードで MongoDB データベースを使用します。"
+
+#: ./doc/install-guide/section_ceilometer-install.xml46(para)
+msgid ""
+"By default MongoDB is configured to create several 1GB files in the "
+"/var/lib/mongodb/journal/ directory to support database journaling."
+msgstr "MongoDB はデフォルトで、データベースのジャーナリングをサポートするために、/var/lib/mongodb/journal/  ディレクトリにいくつかの 1GB のファイルを作成するよう設定されます。"
+
+#: ./doc/install-guide/section_ceilometer-install.xml51(para)
+msgid ""
+"If you need to minimize the space allocated to support database journaling "
+"then set the <option>smallfiles</option> configuration key to "
+"<literal>true</literal> in the <filename>/etc/mongodb.conf</filename> "
+"configuration file. This configuration reduces the size of each journaling "
+"file to 512MB."
+msgstr "データベースのジャーナリングをサポートするために割り当てられる領域を最小化する必要がある場合、<filename>/etc/mongodb.conf</filename> 設定ファイルにある <option>smallfiles</option> 設定キーを <literal>true</literal> に設定します。この設定により、各ジャーナルファイルの容量が 512MB に減ります。"
+
+#: ./doc/install-guide/section_ceilometer-install.xml59(para)
+msgid ""
+"As the files are created the first time the MongoDB service starts you must "
+"stop the service and remove the files for this change to take effect:"
+msgstr "MongoDB サービスを初めて起動するときに、このファイルが作成されるので、この変更を反映するためにサービスを停止して、このファイルを削除する必要があります。"
+
+#: ./doc/install-guide/section_ceilometer-install.xml67(para)
+msgid ""
+"For more information on the <option>smallfiles</option> configuration key "
+"refer to the MongoDB documentation at <link "
+"href=\"http://docs.mongodb.org/manual/reference/configuration-"
+"options/#smallfiles\"/>."
+msgstr "<option>smallfiles</option> 設定キーの詳細は MongoDB のドキュメント <link href=\"http://docs.mongodb.org/manual/reference/configuration-options/#smallfiles\"/> を参照してください。"
+
+#: ./doc/install-guide/section_ceilometer-install.xml72(para)
+msgid ""
+"For instructions detailing the steps to disable database journaling entirely"
+" refer to <link href=\"http://docs.mongodb.org/manual/tutorial/manage-"
+"journaling/\"/>."
+msgstr "データベースのジャーナリング自体を無効化する手順の詳細は <link href=\"http://docs.mongodb.org/manual/tutorial/manage-journaling/\"/> を参照してください。"
+
+#: ./doc/install-guide/section_ceilometer-install.xml80(para)
+msgid ""
+"Configure MongoDB to make it listen on the controller management IP address."
+" Edit the <filename>/etc/mongodb.conf</filename> file and modify the "
+"<literal>bind_ip</literal> key:"
+msgstr "コントローラーの管理 IP アドレスをリッスンするよう MongoDB を設定します。<filename>/etc/mongodb.conf</filename> ファイルを編集し、<literal>bind_ip</literal> キーを変更します。"
+
+#: ./doc/install-guide/section_ceilometer-install.xml86(para)
+msgid "Restart the MongoDB service to apply the configuration change:"
+msgstr "設定の変更を適用するために MongoDB のサービスを再起動します。"
+
+#: ./doc/install-guide/section_ceilometer-install.xml90(para)
+msgid ""
+"Start the MongoDB server and configure it to start when the system boots:"
+msgstr "MongoDB サーバーを起動し、システム起動時に起動するよう設定します。"
+
+#: ./doc/install-guide/section_ceilometer-install.xml100(para)
+msgid "Create the database and a <literal>ceilometer</literal> database user:"
+msgstr "データベースと <literal>ceilometer</literal> データベースユーザーを作成します。"
+
+#: ./doc/install-guide/section_ceilometer-install.xml105(replaceable)
+#: ./doc/install-guide/section_ceilometer-install.xml111(replaceable)
+#: ./doc/install-guide/section_ceilometer-install.xml118(replaceable)
+msgid "CEILOMETER_DBPASS"
+msgstr "CEILOMETER_DBPASS"
+
+#: ./doc/install-guide/section_ceilometer-install.xml109(para)
+msgid "Configure the Telemetry service to use the database:"
+msgstr "Telemetry Service がデータベースを使用するよう設定します。"
+
+#: ./doc/install-guide/section_ceilometer-install.xml112(para)
+msgid ""
+"Edit the <filename>/etc/ceilometer/ceilometer.conf</filename> file and "
+"change the <literal>[database]</literal> section:"
+msgstr "<filename>/etc/ceilometer/ceilometer.conf</filename> ファイルを編集し、<literal>[database]</literal> セクションを変更します。"
+
+#: ./doc/install-guide/section_ceilometer-install.xml122(para)
+msgid ""
+"You must define a secret key that is used as a shared secret among Telemetry"
+" service nodes. Use <placeholder-1/> to generate a random token and store it"
+" in the configuration file:"
+msgstr "Telemetry Service のノード間で共有するシークレットとして使用するシークレットキーを定義する必要があります。ランダムなトークンを生成するために <placeholder-1/> を使用し、それを設定ファイルに保存します。"
+
+#: ./doc/install-guide/section_ceilometer-install.xml129(para)
+msgid "For SUSE Linux Enterprise, run the following command:"
+msgstr "SUSE Linux Enterprise の場合、以下のコマンドを実行します。"
+
+#: ./doc/install-guide/section_ceilometer-install.xml133(para)
+msgid ""
+"Edit the <filename>/etc/ceilometer/ceilometer.conf</filename> file and "
+"change the <literal>[publisher]</literal> section. Replace "
+"<replaceable>CEILOMETER_TOKEN</replaceable> with the results of the "
+"<literal>openssl</literal> command:"
+msgstr "<filename>/etc/ceilometer/ceilometer.conf</filename> ファイルを編集し、<literal>[publisher]</literal> セクションを変更します。<replaceable>CEILOMETER_TOKEN</replaceable> を <literal>openssl</literal> コマンドの出力で置き換えます。"
+
+#: ./doc/install-guide/section_ceilometer-install.xml153(para)
+msgid "Configure the Qpid access:"
+msgstr "Qpid のアクセス権を設定します。"
+
+#: ./doc/install-guide/section_ceilometer-install.xml159(para)
+msgid "Configure the collector dispatcher:"
+msgstr "コレクターディスパッチャーを設定します。"
+
+#: ./doc/install-guide/section_ceilometer-install.xml173(para)
+msgid ""
+"Create a <literal>ceilometer</literal> user that the Telemetry service uses "
+"to authenticate with the Identity Service. Use the "
+"<literal>service</literal> tenant and give the user the "
+"<literal>admin</literal> role:"
+msgstr "Telemetry Service が Identity Service で認証するために使用する <literal>ceilometer</literal> ユーザーを作成します。<literal>service</literal> プロジェクトを使用し、ユーザーに <literal>admin</literal> ロールを与えます。"
+
+#: ./doc/install-guide/section_ceilometer-install.xml177(replaceable)
+msgid "ceilometer@example.com"
+msgstr "ceilometer@example.com"
+
+#: ./doc/install-guide/section_ceilometer-install.xml181(para)
+msgid ""
+"Configure the Telemetry service to authenticate with the Identity Service."
+msgstr "Identity Service を用いて認証するよう Telemetry を設定します。"
+
+#: ./doc/install-guide/section_ceilometer-install.xml183(para)
+msgid ""
+"Set the <option>auth_strategy</option> value to <literal>keystone</literal> "
+"in the <filename>/etc/ceilometer/ceilometer.conf</filename> file:"
+msgstr "<filename>/etc/ceilometer/ceilometer.conf</filename> ファイルで <option>auth_strategy</option> の値を <literal>keystone</literal> に設定します。"
+
+#: ./doc/install-guide/section_ceilometer-install.xml193(para)
+msgid ""
+"Add the credentials to the configuration files for the Telemetry service:"
+msgstr "クレデンシャルを Telemetry Service の設定ファイルに追加します。"
+
+#: ./doc/install-guide/section_ceilometer-install.xml236(para)
+msgid ""
+"Register the Telemetry service with the Identity Service so that other "
+"OpenStack services can locate it. Use the <placeholder-1/> command to "
+"register the service and specify the endpoint:"
+msgstr "他の OpenStack サービスから使用できるように、Telemetry Service を Identity Service に登録します。サービスを登録し、エンドポイントを指定するために、<placeholder-1/> コマンドを使用します。"
+
+#: ./doc/install-guide/section_ceilometer-install.xml249(para)
+msgid "Restart the services with their new settings:"
+msgstr "新しい設定を用いてサービスを再起動します。"
+
+#: ./doc/install-guide/section_ceilometer-install.xml258(para)
+msgid ""
+"Start the <systemitem class=\"service\">openstack-ceilometer-"
+"api</systemitem>, <systemitem class=\"service\" os=\"opensuse;sles"
+"\">openstack-ceilometer-agent-central</systemitem><systemitem "
+"class=\"service\" os=\"rhel;fedora;centos\">openstack-ceilometer-"
+"central</systemitem>, <systemitem class=\"service\">openstack-ceilometer-"
+"collector</systemitem>, <systemitem class=\"service\" os=\"opensuse;sles"
+"\">openstack-ceilometer-alarm-evaluator</systemitem>, and <systemitem "
+"class=\"service\" os=\"opensuse;sles\">openstack-ceilometer-alarm-"
+"notifier</systemitem> services and configure them to start when the system "
+"boots:"
+msgstr " <systemitem class=\"service\">openstack-ceilometer-api</systemitem>、<systemitem class=\"service\" os=\"opensuse;sles\">openstack-ceilometer-agent-central</systemitem><systemitem class=\"service\" os=\"rhel;fedora;centos\">openstack-ceilometer-central</systemitem>、<systemitem class=\"service\">openstack-ceilometer-collector</systemitem>、<systemitem class=\"service\" os=\"opensuse;sles\">openstack-ceilometer-alarm-evaluator</systemitem>、<systemitem class=\"service\" os=\"opensuse;sles\">openstack-ceilometer-alarm-notifier</systemitem> サービスを起動し、システムの起動時にそれらが起動するよう設定します。"
+
+#: ./doc/install-guide/section_heat-verify.xml6(title)
+msgid "Verify the Orchestration service installation"
+msgstr "Orchestration Service のインストールの検証"
+
+#: ./doc/install-guide/section_heat-verify.xml8(para)
+msgid ""
+"To verify that the Orchestration service is installed and configured "
+"correctly, make sure that your credentials are set up correctly in the "
+"<filename>demo-openrc.sh</filename> file. Source the file, as follows:"
+msgstr "Orchestration Service が正しくインストールされ、設定されていることを検証するために、クレデンシャルが <filename>demo-openrc.sh</filename> ファイルに正しくセットアップされていることを確認します。このファイルを以下のように読み込みます。"
+
+#: ./doc/install-guide/section_heat-verify.xml14(para)
+msgid ""
+"The Orchestration Module uses templates to describe stacks. To learn about "
+"the template languages, see <link "
+"href=\"http://docs.openstack.org/developer/heat/template_guide/index.html\">the"
+" Template Guide</link> in the <link "
+"href=\"http://docs.openstack.org/developer/heat/\">Heat developer "
+"documentation</link>."
+msgstr "Orchestration モジュールは、スタックを記載するためにテンプレートを使用します。テンプレート言語を学習するために、<link href=\"http://docs.openstack.org/developer/heat/\">Heat 開発者ドキュメント</link>の <link href=\"http://docs.openstack.org/developer/heat/template_guide/index.html\">Template Guide</link> を参照してください。"
+
+#: ./doc/install-guide/section_heat-verify.xml20(para)
+msgid ""
+"Create a test template in the <filename>test-stack.yml</filename> file with "
+"the following content:"
+msgstr "以下の内容を持つ <filename>test-stack.yml</filename> ファイルにテストテンプレートを作成します。"
+
+#: ./doc/install-guide/section_heat-verify.xml24(para)
+msgid "Use the <placeholder-1/> command to create a stack from this template:"
+msgstr "このテンプレートからスタックを作成するために <placeholder-1/> コマンドを使用します。"
+
+#: ./doc/install-guide/section_heat-verify.xml35(para)
+msgid ""
+"Verify that the stack was created successfully with the <placeholder-1/> "
+"command:"
+msgstr "<placeholder-1/> コマンドを用いて、スタックが正常に作成されたことを検証します。"
+
+#: ./doc/install-guide/ch_heat.xml6(title)
+msgid "Add the Orchestration service"
+msgstr "Orchestration Service の追加"
+
+#: ./doc/install-guide/ch_heat.xml7(para)
+msgid ""
+"Use the Orchestration module to create cloud resources using a template "
+"language called HOT. The integrated project name is Heat."
+msgstr "HOT と呼ばれるテンプレート言語を使用してクラウドリソースを作成するために Orchestration モジュールを使用します。統合プロジェクト名は Heat です。"
+
+#: ./doc/install-guide/ch_heat.xml15(para)
+msgid ""
+"Your OpenStack environment now includes Orchestration. You can <link linkend"
+"=\"launch-instance\">launch an instance</link> or add more services to your "
+"environment in the following chapters."
+msgstr "OpenStack 環境に Orchestration が追加されました。<link linkend=\"launch-instance\">インスタンスの起動</link>、以降の章に記載されているサービスの環境への追加を実行できます。"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-rabbitqm.xml15(None)
+msgid ""
+"@@image: 'figures/debconf-screenshots/rabbitmq-host.png'; "
+"md5=5353ad857884a2d31847cf82efbdc6b6"
+msgstr "@@image: 'figures/debconf-screenshots/rabbitmq-host.png'; md5=5353ad857884a2d31847cf82efbdc6b6"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-rabbitqm.xml22(None)
+msgid ""
+"@@image: 'figures/debconf-screenshots/rabbitmq-user.png'; "
+"md5=33a3c1182e79ed65f1b1b63f2156792c"
+msgstr "@@image: 'figures/debconf-screenshots/rabbitmq-user.png'; md5=33a3c1182e79ed65f1b1b63f2156792c"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-rabbitqm.xml29(None)
+msgid ""
+"@@image: 'figures/debconf-screenshots/rabbitmq-password.png'; "
+"md5=6385185200d20e96b6316ae15ae1255d"
+msgstr "@@image: 'figures/debconf-screenshots/rabbitmq-password.png'; md5=6385185200d20e96b6316ae15ae1255d"
+
+#: ./doc/install-guide/section_debconf-rabbitqm.xml6(title)
+msgid "RabbitMQ credentials parameters"
+msgstr "RabbitMQ クレデンシャルパラメーター"
+
+#: ./doc/install-guide/section_debconf-rabbitqm.xml7(para)
+msgid ""
+"For every package that must connect to a Messaging Server, the Debian "
+"package enables you to configure the IP address for that server and the user"
+" name and password that is used to connect. The following example shows "
+"configuration with the <systemitem class=\"service\">ceilometer-"
+"common</systemitem> package:"
+msgstr "メッセージングサーバーに接続する必要があるすべてのパッケージの場合には、Debian パッケージにより、そのサーバーの IP アドレス、接続するために使用されるユーザー名とパスワードを設定できます。以下の例は <systemitem class=\"service\">ceilometer-common</systemitem> を用いた設定を示します。"
+
+#: ./doc/install-guide/section_debconf-rabbitqm.xml33(para)
+msgid ""
+"These debconf screens appear in: <systemitem class=\"service\">ceilometer-"
+"common</systemitem>, <systemitem class=\"service\">cinder-"
+"common</systemitem>, <systemitem class=\"service\">glance-"
+"common</systemitem>, <systemitem class=\"service\">heat-common</systemitem>,"
+" <systemitem class=\"service\">neutron-common</systemitem> and <systemitem "
+"class=\"service\">nova-common</systemitem>."
+msgstr "これらの debconf 画面が次のもので表示されます。<systemitem class=\"service\">ceilometer-common</systemitem>、<systemitem class=\"service\">cinder-common</systemitem>、<systemitem class=\"service\">glance-common</systemitem>、<systemitem class=\"service\">heat-common</systemitem>、<systemitem class=\"service\">neutron-common</systemitem>、<systemitem class=\"service\">nova-common</systemitem>。"
+
+#: ./doc/install-guide/section_basics-ntp.xml6(title)
+msgid "Network Time Protocol (NTP)"
+msgstr "Network Time Protocol (NTP)"
+
+#: ./doc/install-guide/section_basics-ntp.xml7(para)
+msgid ""
+"You must install <glossterm baseform=\"Network Time Protocol "
+"(NTP)\">NTP</glossterm> to properly synchronize services among nodes. We "
+"recommend that you configure the controller node to reference upstream "
+"servers and other nodes to reference the controller node."
+msgstr "サービスをノード間で適切に同期するために、<glossterm baseform=\"Network Time Protocol (NTP)\">NTP</glossterm> をインストールする必要があります。コントローラーノードが上位のサーバーを参照し、他のコードがコントローラーノードを参照するよう設定することを推奨します。"
+
+#: ./doc/install-guide/section_basics-ntp.xml13(title)
+#: ./doc/install-guide/section_nova-networking-controller-node.xml5(title)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml6(title)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml6(title)
+msgid "Configure controller node"
+msgstr "コントローラーノードの設定"
+
+#: ./doc/install-guide/section_basics-ntp.xml15(title)
+#: ./doc/install-guide/section_basics-ntp.xml57(title)
+msgid "To install the NTP service"
+msgstr "NTP サービスのインストール方法"
+
+#: ./doc/install-guide/section_basics-ntp.xml23(title)
+#: ./doc/install-guide/section_basics-ntp.xml65(title)
+msgid "To configure the NTP service"
+msgstr "NTP サービスの設定方法"
+
+#: ./doc/install-guide/section_basics-ntp.xml24(para)
+msgid ""
+"By default, the controller node synchronizes the time via a pool of public "
+"servers. However, you can optionally edit the "
+"<filename>/etc/ntp.conf</filename> file to configure alternative servers "
+"such as those provided by your organization."
+msgstr "コントローラーノードはデフォルトで、パブリックなサーバープール経由で時刻同期します。しかしながらオプションとして、自組織により提供されるサーバーを参照するために、<filename>/etc/ntp.conf</filename> ファイルを編集することもできます。"
+
+#: ./doc/install-guide/section_basics-ntp.xml29(para)
+#: ./doc/install-guide/section_basics-ntp.xml69(para)
+msgid "Edit the <filename>/etc/ntp.conf</filename> file:"
+msgstr "<filename>/etc/ntp.conf</filename> ファイルを編集します。"
+
+#: ./doc/install-guide/section_basics-ntp.xml30(para)
+msgid ""
+"Add, change, or remove the <literal>server</literal> keys as necessary for "
+"your environment. Replace <replaceable>NTP_SERVER</replaceable> with the "
+"hostname or IP address of suitable NTP server."
+msgstr "環境の必要に応じて、<literal>server</literal> を追加、変更、削除します。<replaceable>NTP_SERVER</replaceable を適切な NTP サーバーのホスト名や IP アドレスで置き換えます。"
+
+#: ./doc/install-guide/section_basics-ntp.xml34(replaceable)
+msgid "NTP_SERVER"
+msgstr "NTP_SERVER"
+
+#: ./doc/install-guide/section_basics-ntp.xml36(para)
+#: ./doc/install-guide/section_basics-ntp.xml74(para)
+msgid ""
+"Remove the <filename>/var/lib/ntp/ntp.conf.dhcp</filename> file if it "
+"exists."
+msgstr "<filename>/var/lib/ntp/ntp.conf.dhcp</filename> が存在すれば、削除します。"
+
+#: ./doc/install-guide/section_basics-ntp.xml41(para)
+#: ./doc/install-guide/section_basics-ntp.xml79(para)
+msgid "Restart the NTP service:"
+msgstr "NTP サービスを再起動します。"
+
+#: ./doc/install-guide/section_basics-ntp.xml45(para)
+#: ./doc/install-guide/section_basics-ntp.xml83(para)
+msgid "Start the NTP service and configure it to start when the system boots:"
+msgstr "NTP サービスを起動し、システム起動時に起動するよう設定します。"
+
+#: ./doc/install-guide/section_basics-ntp.xml55(title)
+msgid "Configure other nodes"
+msgstr "他のノードの設定"
+
+#: ./doc/install-guide/section_basics-ntp.xml66(para)
+msgid ""
+"Configure the network and compute nodes to reference the controller node."
+msgstr "ネットワークノードとコンピュートノードがコントローラーノードを参照するよう設定します。"
+
+#: ./doc/install-guide/section_basics-ntp.xml70(para)
+msgid ""
+"Comment out or remove all but one <literal>server</literal> key and change "
+"it to reference the controller node."
+msgstr "1 つの <literal>server</literal> キー以外をすべてコメントアウトまたは削除します。このキーは、コントローラーノードを参照するよう変更します。"
+
+#: ./doc/install-guide/section_basics-ntp.xml93(title)
+msgid "Verify operation"
+msgstr "運用の検証"
+
+#: ./doc/install-guide/section_basics-ntp.xml94(para)
+msgid ""
+"We recommend that you verify NTP synchronization before proceeding further. "
+"Some nodes, particularly those that reference the controller node, can take "
+"several minutes to synchronize."
+msgstr "続行する前に、NTP 同期について検証することを推奨します。いくつかのノード、とくにコントローラーノードを参照するノードは、同期に数分かかる可能性があります。"
+
+#: ./doc/install-guide/section_basics-ntp.xml98(title)
+msgid "To verify NTP synchronization"
+msgstr "NTP 同期の検証方法"
+
+#: ./doc/install-guide/section_basics-ntp.xml100(para)
+#: ./doc/install-guide/section_basics-ntp.xml115(para)
+msgid "Run this command on the <emphasis>controller</emphasis> node:"
+msgstr "このコマンドを<emphasis>コントローラー</emphasis>ノードで実行します。"
+
+#: ./doc/install-guide/section_basics-ntp.xml107(para)
+msgid ""
+"Contents in the <emphasis>remote</emphasis> column should indicate the "
+"hostname or IP address of one or more NTP servers."
+msgstr "<emphasis>remote</emphasis> 列の内容は、1 つ以上の NTP サーバーのホスト名や IP アドレスを意味するでしょう。"
+
+#: ./doc/install-guide/section_basics-ntp.xml110(para)
+#: ./doc/install-guide/section_basics-ntp.xml134(para)
+msgid ""
+"Contents in the <emphasis>refid</emphasis> column typically reference IP "
+"addresses of upstream servers."
+msgstr "<emphasis>refid</emphasis> 列の内容は、一般的に上位のサーバーの IP アドレスを参照します。"
+
+#: ./doc/install-guide/section_basics-ntp.xml122(para)
+msgid ""
+"Contents in the <emphasis>condition</emphasis> column should indicate "
+"<literal>sys.peer</literal> for at least one server."
+msgstr "<emphasis>condition</emphasis> 列の内容は、少なくとも 1 つのサーバーの <literal>sys.peer</literal> を意味するでしょう。"
+
+#: ./doc/install-guide/section_basics-ntp.xml126(para)
+#: ./doc/install-guide/section_basics-ntp.xml139(para)
+msgid "Run this command on <emphasis>all other</emphasis> nodes:"
+msgstr "このコマンドを<emphasis>他のすべての</emphasis>ノードで実行します。"
+
+#: ./doc/install-guide/section_basics-ntp.xml131(para)
+msgid ""
+"Contents in the <emphasis>remote</emphasis> column should indicate the "
+"hostname of the controller node."
+msgstr "<emphasis>remote</emphasis> 列の内容は、コントローラーノードのホスト名を意味するでしょう。"
+
+#: ./doc/install-guide/section_basics-ntp.xml145(para)
+msgid ""
+"Contents in the <emphasis>condition</emphasis> column should indicate "
+"<literal>sys.peer</literal>."
+msgstr "<emphasis>condition</emphasis> 列の内容は、<literal>sys.peer</literal> を意味するでしょう。"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_neutron-initial-networks.xml23(None)
+msgid ""
+"@@image: 'figures/installguide_neutron-initial-networks.png'; "
+"md5=df1d74b6f91feefe5cfaf7824aac86e1"
+msgstr "@@image: 'figures/installguide_neutron-initial-networks.png'; md5=df1d74b6f91feefe5cfaf7824aac86e1"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml6(title)
+msgid "Create initial networks"
+msgstr "初期ネットワークの作成"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml7(para)
+msgid ""
+"Before launching your first instance, you must create the necessary virtual "
+"network infrastructure to which the instance will connect, including the "
+"<link linkend=\"neutron_initial-external-network\">external network</link> "
+"and <link linkend=\"neutron_initial-tenant-network\">tenant network</link>. "
+"See <xref linkend=\"neutron_figure-neutron-initial-networks\"/>. After "
+"creating this infrastructure, we recommend that you <link linkend"
+"=\"neutron_initial-networks-verify\">verify connectivity</link> and resolve "
+"any issues before proceeding further."
+msgstr "初めてのインスタンスを起動する前に、インスタンスが接続するために必要な仮想ネットワークを作成する必要があります。これには、 <link linkend=\"neutron_initial-external-network\">外部ネットワーク</link>と<link linkend=\"neutron_initial-tenant-network\">プロジェクトネットワーク</link>があります。<xref linkend=\"neutron_figure-neutron-initial-networks\"/>を参照してください。このネットワークの作成後、<link linkend=\"neutron_initial-networks-verify\">接続性を検証し</link>、続行する前にすべての問題を解決することを推奨します。"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml19(title)
+msgid "Initial networks"
+msgstr "初期ネットワーク"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml28(title)
+msgid "External network"
+msgstr "外部ネットワーク"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml29(para)
+msgid ""
+"The external network typically provides internet access for your instances. "
+"By default, this network only allows internet access "
+"<emphasis>from</emphasis> instances using <glossterm>Network Address "
+"Translation (NAT)</glossterm>. You can enable internet access "
+"<emphasis>to</emphasis> individual instances using a <glossterm>floating IP "
+"address</glossterm> and suitable <glossterm>security group</glossterm> "
+"rules. The <literal>admin</literal> tenant owns this network because it "
+"provides external network access for multiple tenants. You must also enable "
+"sharing to allow access by those tenants."
+msgstr "一般的に外部ネットワークにより、インスタンスにインターネットアクセスが提供されます。デフォルトでこのネットワークのみにより、インスタンス<emphasis>から </emphasis><glossterm baseform=\"Network Address Translation (NAT)\">NAT</glossterm> を使用して、インターネットへのアクセスが許可されます。<glossterm baseform=\"floating IP address\">Floating IP アドレス</glossterm>と適切な<glossterm baseform=\"security group\">セキュリティグループ</glossterm>ルールを使用して、個々のインスタンス<emphasis>へと</emphasis>インターネットからアクセス可能にできます。<literal>admin</literal> プロジェクトは、複数のプロジェクトに対して外部ネットワークを提供するため、このネットワークを所有します。これらのプロジェクトによりアクセスを許可するために、共有を有効化する必要があります。"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml43(title)
+msgid "To create the external network"
+msgstr "外部ネットワークの作成方法"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml69(para)
+msgid ""
+"Like a physical network, a virtual network requires a "
+"<glossterm>subnet</glossterm> assigned to it. The external network shares "
+"the same subnet and <glossterm>gateway</glossterm> associated with the "
+"physical network connected to the external interface on the network node. "
+"You should specify an exclusive slice of this subnet for "
+"<glossterm>router</glossterm> and floating IP addresses to prevent "
+"interference with other devices on the external network."
+msgstr "物理ネットワーク同様、仮想ネットワークは関連づける<glossterm baseform=\"subnet\">サブネット</glossterm>が必要です。外部ネットワークは、ネットワークノードの外部インターフェースに接続された物理ネットワークと関連づけられた、同じサブネットと<glossterm baseform=\"gateway\">ゲートウェイ</glossterm>を共有します。外部ネットワークの他のデバイスと競合しないよう、このサブネットの<glossterm baseform=\"router\">ルーター</glossterm>専用範囲と Floating IP アドレスを指定すべきです。"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml76(para)
+msgid ""
+"Replace <replaceable>FLOATING_IP_START</replaceable> and "
+"<replaceable>FLOATING_IP_END</replaceable> with the first and last IP "
+"addresses of the range that you want to allocate for floating IP addresses. "
+"Replace <replaceable>EXTERNAL_NETWORK_CIDR</replaceable> with the subnet "
+"associated with the physical network. Replace "
+"<replaceable>EXTERNAL_NETWORK_GATEWAY</replaceable> with the gateway "
+"associated with the physical network, typically the \".1\" IP address. You "
+"should disable <glossterm>DHCP</glossterm> on this subnet because instances "
+"do not connect directly to the external network and floating IP addresses "
+"require manual assignment."
+msgstr "<replaceable>FLOATING_IP_START</replaceable> と <replaceable>FLOATING_IP_END</replaceable> を、Floating IP アドレスに割り当てたい IP アドレス範囲の開始アドレスと終了アドレスで置き換えます。<replaceable>EXTERNAL_NETWORK_CIDR</replaceable> を物理ネットワークに関連づけられたサブネットで置き換えます。<replaceable>EXTERNAL_NETWORK_GATEWAY</replaceable> を物理ネットワークに関連づけられたゲートウェイで置き換えます。一般的に「.1」の IP アドレスを使用します。インスタンスは外部ネットワークに直接接続せず、Floating IP アドレスは手動で割り当てる必要があるため、このサブネットで <glossterm>DHCP</glossterm> を無効化すべきです。"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml87(title)
+msgid "To create a subnet on the external network"
+msgstr "外部ネットワークへのサブネットの作成方法"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml89(para)
+#: ./doc/install-guide/section_neutron-initial-networks.xml164(para)
+msgid "Create the subnet:"
+msgstr "サブネットを作成します。"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml91(replaceable)
+msgid "FLOATING_IP_START"
+msgstr "FLOATING_IP_START"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml91(replaceable)
+msgid "FLOATING_IP_END"
+msgstr "FLOATING_IP_END"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml92(replaceable)
+msgid "EXTERNAL_NETWORK_GATEWAY"
+msgstr "EXTERNAL_NETWORK_GATEWAY"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml92(replaceable)
+msgid "EXTERNAL_NETWORK_CIDR"
+msgstr "EXTERNAL_NETWORK_CIDR"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml93(para)
+msgid ""
+"For example, using <literal>203.0.113.0/24</literal> with floating IP "
+"address range <literal>203.0.113.101</literal> to "
+"<literal>203.0.113.200</literal>:"
+msgstr "例えば、Floating IP アドレス範囲 <literal>203.0.113.101</literal> 〜 <literal>203.0.113.200</literal> を持つ <literal>203.0.113.0/24</literal> を使用する場合:"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml121(title)
+msgid "Tenant network"
+msgstr "テナントネットワーク"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml122(para)
+msgid ""
+"The tenant network provides internal network access for instances. The "
+"architecture isolates this type of network from other tenants. The "
+"<literal>demo</literal> tenant owns this network because it only provides "
+"network access for instances within it."
+msgstr "プロジェクトネットワークは、インスタンス用の内部ネットワークアクセスを提供します。このアーキテクチャは、この種のネットワークを他のプロジェクトと分離します。<literal>demo</literal> プロジェクトは、プロジェクト内のインスタンスのみにネットワークアクセスを提供するため、このネットワークを所有します。"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml130(title)
+msgid "To create the tenant network"
+msgstr "テナントネットワークの作成方法"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml132(para)
+#: ./doc/install-guide/section_launch-instance-nova.xml15(para)
+#: ./doc/install-guide/section_launch-instance-neutron.xml15(para)
+msgid "Source the <literal>demo</literal> tenant credentials:"
+msgstr "<literal>demo</literal> プロジェクトのクレデンシャルを読み込みます。"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml152(para)
+msgid ""
+"Like the external network, your tenant network also requires a subnet "
+"attached to it. You can specify any valid subnet because the architecture "
+"isolates tenant networks. Replace "
+"<replaceable>TENANT_NETWORK_CIDR</replaceable> with the subnet you want to "
+"associate with the tenant network. Replace "
+"<replaceable>TENANT_NETWORK_GATEWAY</replaceable> with the gateway you want "
+"to associate with this network, typically the \".1\" IP address. By default,"
+" this subnet will use DHCP so your instances can obtain IP addresses."
+msgstr "外部ネットワーク同様、プロジェクトネットワークも接続するサブネットが必要です。このアーキテクチャはプロジェクトネットワークを分離するため、任意の有効なサブネットを指定できます。プロジェクトネットワークに関連づけたいサブネットで <replaceable>TENANT_NETWORK_CIDR</replaceable> を置き換えます。このネットワークに関連づけたいゲートウェイで <replaceable>TENANT_NETWORK_GATEWAY</replaceable> を置き換えます。一般的に「.1」の IP アドレスを使用します。デフォルトで、このサブネットはDHCP を使用するため、インスタンスが IP アドレスを取得できます。"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml162(title)
+msgid "To create a subnet on the tenant network"
+msgstr "テナントネットワークへのサブネットの作成方法"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml166(replaceable)
+msgid "TENANT_NETWORK_GATEWAY"
+msgstr "TENANT_NETWORK_GATEWAY"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml166(replaceable)
+msgid "TENANT_NETWORK_CIDR"
+msgstr "TENANT_NETWORK_CIDR"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml167(para)
+msgid "Example using <literal>192.168.1.0/24</literal>:"
+msgstr "<literal>192.168.1.0/24</literal> を用いた例:"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml190(para)
+msgid ""
+"A virtual router passes network traffic between two or more virtual "
+"networks. Each router requires one or more <glossterm "
+"baseform=\"interface\">interfaces</glossterm> and/or gateways that provide "
+"access to specific networks. In this case, you will create a router and "
+"attach your tenant and external networks to it."
+msgstr "仮想ルーターは、複数の仮想ネットワーク間でネットワーク通信を転送します。各ルーターは、指定したネットワークにアクセスする、1 つ以上の<glossterm baseform=\"interface\">インターフェース</glossterm>とゲートウェイが必要です。今回、ルーターを作成し、プロジェクトネットワークと外部ネットワークを接続します。"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml196(title)
+msgid ""
+"To create a router on the tenant network and attach the external and tenant "
+"networks to it"
+msgstr "プロジェクトネットワークにルーターを作成し、外部ネットワークとプロジェクトネットワークを接続する方法"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml199(para)
+msgid "Create the router:"
+msgstr "ルーターを作成します。"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml214(para)
+msgid "Attach the router to the <literal>demo</literal> tenant subnet:"
+msgstr "ルーターを <literal>demo</literal> テナントサブネットに接続します。"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml220(para)
+msgid ""
+"Attach the router to the external network by setting it as the gateway:"
+msgstr "外部ネットワークをゲートウェイとして設定し、ルーターに接続します。"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml229(para)
+msgid ""
+"We recommend that you verify network connectivity and resolve any issues "
+"before proceeding further. Following the external network subnet example "
+"using <literal>203.0.113.0/24</literal>, the tenant router gateway should "
+"occupy the lowest IP address in the floating IP address range, "
+"<literal>203.0.113.101</literal>. If you configured your external physical "
+"network and virtual networks correctly, you you should be able to "
+"<placeholder-1/> this IP address from any host on your external physical "
+"network."
+msgstr "ネットワーク接続性を検証し、続行する前にすべての問題を解決することを推奨します。<literal>203.0.113.0/24</literal> を使用した例の外部ネットワークのサブネットに従うと、プロジェクトのルーターゲートウェイは Floating IP アドレス範囲の最小値 <literal>203.0.113.101</literal> を使用すべきです。外部物理ネットワークと仮想ネットワークを適切に設定した場合、外部物理ネットワークにあるホストから、この IP アドレスに <placeholder-1/> できるでしょう。"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml238(para)
+msgid ""
+"If you are building your OpenStack nodes as virtual machines, you must "
+"configure the hypervisor to permit promiscuous mode on the external network."
+msgstr "OpenStack のノードを仮想マシンとして構築する場合、外部ネットワークのプロミスキャスモードを許可するよう、ハイパーバイザーを設定する必要があります。"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml243(title)
+msgid "To verify network connectivity"
+msgstr "ネットワーク接続性の確認方法"
+
+#: ./doc/install-guide/section_neutron-initial-networks.xml245(para)
+msgid "Ping the tenant router gateway:"
+msgstr "プロジェクトのゲートウェイに ping します。"
 
 #: ./doc/install-guide/ch_clients.xml6(title)
 msgid "Install and configure the OpenStack clients"
@@ -1158,214 +3621,117 @@ msgstr "<xref linkend=\"openrc-create\"/> で説明したように、<phrase os=
 msgid "<filename>admin-openrc.sh</filename> for the administrative user"
 msgstr "管理ユーザー用の <filename>admin-openrc.sh</filename>"
 
-#: ./doc/install-guide/ch_clients.xml42(replaceable)
-#: ./doc/install-guide/section_ceilometer-install.xml102(replaceable)
-#: ./doc/install-guide/section_ceilometer-install.xml111(replaceable)
-#: ./doc/install-guide/section_ceilometer-install.xml118(replaceable)
-#: ./doc/install-guide/section_ceilometer-install.xml145(replaceable)
-#: ./doc/install-guide/section_ceilometer-install.xml148(replaceable)
-#: ./doc/install-guide/section_ceilometer-install.xml196(replaceable)
-#: ./doc/install-guide/section_ceilometer-install.xml204(replaceable)
-#: ./doc/install-guide/section_ceilometer-install.xml208(replaceable)
-#: ./doc/install-guide/section_ceilometer-install.xml223(replaceable)
-#: ./doc/install-guide/section_ceilometer-install.xml230(replaceable)
-#: ./doc/install-guide/section_ceilometer-install.xml244(replaceable)
-#: ./doc/install-guide/section_ceilometer-install.xml245(replaceable)
-#: ./doc/install-guide/section_ceilometer-install.xml246(replaceable)
-#: ./doc/install-guide/section_trove-install.xml74(replaceable)
-#: ./doc/install-guide/section_trove-install.xml75(replaceable)
-#: ./doc/install-guide/section_trove-install.xml76(replaceable)
-#: ./doc/install-guide/section_trove-install.xml77(replaceable)
-#: ./doc/install-guide/section_trove-install.xml78(replaceable)
-#: ./doc/install-guide/section_trove-install.xml79(replaceable)
-#: ./doc/install-guide/section_trove-install.xml92(replaceable)
-#: ./doc/install-guide/section_trove-install.xml94(replaceable)
-#: ./doc/install-guide/section_trove-install.xml96(replaceable)
-#: ./doc/install-guide/section_trove-install.xml119(replaceable)
-#: ./doc/install-guide/section_trove-install.xml121(replaceable)
-#: ./doc/install-guide/section_trove-install.xml123(replaceable)
-#: ./doc/install-guide/section_trove-install.xml139(replaceable)
-#: ./doc/install-guide/section_trove-install.xml220(replaceable)
-#: ./doc/install-guide/section_trove-install.xml225(replaceable)
-#: ./doc/install-guide/section_trove-install.xml227(replaceable)
-#: ./doc/install-guide/section_trove-install.xml231(replaceable)
-#: ./doc/install-guide/section_trove-install.xml252(replaceable)
-#: ./doc/install-guide/section_trove-install.xml253(replaceable)
-#: ./doc/install-guide/section_trove-install.xml254(replaceable)
-#: ./doc/install-guide/section_nova-controller.xml44(replaceable)
-#: ./doc/install-guide/section_nova-controller.xml59(replaceable)
-#: ./doc/install-guide/section_nova-controller.xml140(replaceable)
-#: ./doc/install-guide/section_nova-controller.xml141(replaceable)
-#: ./doc/install-guide/section_nova-controller.xml160(replaceable)
-#: ./doc/install-guide/section_nova-controller.xml177(replaceable)
-#: ./doc/install-guide/section_nova-controller.xml178(replaceable)
-#: ./doc/install-guide/section_nova-controller.xml179(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml143(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml145(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml179(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml180(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml194(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml205(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml214(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml232(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml242(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml253(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml258(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml49(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml50(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml51(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml113(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml126(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml139(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml141(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml171(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml172(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml200(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml215(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml228(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml236(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml255(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml259(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml376(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml386(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml410(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml415(replaceable)
-#: ./doc/install-guide/section_keystone-services.xml47(replaceable)
-#: ./doc/install-guide/section_keystone-services.xml48(replaceable)
-#: ./doc/install-guide/section_keystone-services.xml49(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml55(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml56(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml57(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml81(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml98(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml100(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml133(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml134(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml161(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml179(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml229(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml239(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml250(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml255(replaceable)
-#: ./doc/install-guide/section_basics-ntp.xml72(replaceable)
-#: ./doc/install-guide/section_ceilometer-glance.xml17(replaceable)
-#: ./doc/install-guide/section_ceilometer-glance.xml23(replaceable)
-#: ./doc/install-guide/section_basics-networking-nova.xml202(replaceable)
-#: ./doc/install-guide/section_basics-networking-neutron.xml277(replaceable)
-#: ./doc/install-guide/section_basics-networking-neutron.xml321(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml97(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml99(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml130(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml131(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml145(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml156(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml165(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml389(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml394(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml399(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml409(replaceable)
-#: ./doc/install-guide/section_cinder-node.xml113(replaceable)
-#: ./doc/install-guide/section_cinder-node.xml115(replaceable)
-#: ./doc/install-guide/section_cinder-node.xml131(replaceable)
-#: ./doc/install-guide/section_cinder-node.xml132(replaceable)
-#: ./doc/install-guide/section_cinder-node.xml150(replaceable)
-#: ./doc/install-guide/section_cinder-node.xml161(replaceable)
-#: ./doc/install-guide/section_cinder-node.xml170(replaceable)
-#: ./doc/install-guide/section_cinder-node.xml183(replaceable)
-#: ./doc/install-guide/section_cinder-node.xml186(replaceable)
-#: ./doc/install-guide/section_cinder-node.xml202(replaceable)
-#: ./doc/install-guide/section_cinder-node.xml205(replaceable)
-#: ./doc/install-guide/section_cinder-controller.xml44(replaceable)
-#: ./doc/install-guide/section_cinder-controller.xml47(replaceable)
-#: ./doc/install-guide/section_cinder-controller.xml83(replaceable)
-#: ./doc/install-guide/section_cinder-controller.xml85(replaceable)
-#: ./doc/install-guide/section_cinder-controller.xml101(replaceable)
-#: ./doc/install-guide/section_cinder-controller.xml102(replaceable)
-#: ./doc/install-guide/section_cinder-controller.xml120(replaceable)
-#: ./doc/install-guide/section_cinder-controller.xml153(replaceable)
-#: ./doc/install-guide/section_cinder-controller.xml154(replaceable)
-#: ./doc/install-guide/section_cinder-controller.xml155(replaceable)
-#: ./doc/install-guide/section_cinder-controller.xml163(replaceable)
-#: ./doc/install-guide/section_cinder-controller.xml164(replaceable)
-#: ./doc/install-guide/section_cinder-controller.xml165(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml65(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml67(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml97(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml98(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml115(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml126(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml141(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml269(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml279(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml300(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml305(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml62(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml64(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml94(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml95(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml112(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml123(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml138(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml294(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml304(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml328(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml333(replaceable)
-#: ./doc/install-guide/section_heat-install.xml40(replaceable)
-#: ./doc/install-guide/section_heat-install.xml46(replaceable)
-#: ./doc/install-guide/section_heat-install.xml92(replaceable)
-#: ./doc/install-guide/section_heat-install.xml95(replaceable)
-#: ./doc/install-guide/section_heat-install.xml113(replaceable)
-#: ./doc/install-guide/section_heat-install.xml116(replaceable)
-#: ./doc/install-guide/section_heat-install.xml122(replaceable)
-#: ./doc/install-guide/section_heat-install.xml133(replaceable)
-#: ./doc/install-guide/section_heat-install.xml134(replaceable)
-#: ./doc/install-guide/section_heat-install.xml135(replaceable)
-#: ./doc/install-guide/section_heat-install.xml140(replaceable)
-#: ./doc/install-guide/section_heat-install.xml141(replaceable)
-#: ./doc/install-guide/section_heat-install.xml142(replaceable)
-#: ./doc/install-guide/section_ceilometer-nova.xml79(replaceable)
-#: ./doc/install-guide/section_ceilometer-nova.xml85(replaceable)
-#: ./doc/install-guide/section_ceilometer-nova.xml91(replaceable)
-#: ./doc/install-guide/section_ceilometer-nova.xml107(replaceable)
-#: ./doc/install-guide/section_ceilometer-nova.xml122(replaceable)
-#: ./doc/install-guide/section_nova-compute.xml74(replaceable)
-#: ./doc/install-guide/section_nova-compute.xml75(replaceable)
-#: ./doc/install-guide/section_nova-compute.xml93(replaceable)
-#: ./doc/install-guide/section_nova-compute.xml94(replaceable)
-#: ./doc/install-guide/section_nova-compute.xml106(replaceable)
-#: ./doc/install-guide/section_nova-compute.xml131(replaceable)
-#: ./doc/install-guide/section_nova-compute.xml143(replaceable)
-#: ./doc/install-guide/section_nova-compute.xml151(replaceable)
-#: ./doc/install-guide/section_nova-compute.xml154(replaceable)
-#: ./doc/install-guide/section_glance-install.xml55(replaceable)
-#: ./doc/install-guide/section_glance-install.xml57(replaceable)
-#: ./doc/install-guide/section_glance-install.xml65(replaceable)
-#: ./doc/install-guide/section_glance-install.xml74(replaceable)
-#: ./doc/install-guide/section_glance-install.xml89(replaceable)
-#: ./doc/install-guide/section_glance-install.xml102(replaceable)
-#: ./doc/install-guide/section_glance-install.xml147(replaceable)
-#: ./doc/install-guide/section_glance-install.xml149(replaceable)
-#: ./doc/install-guide/section_glance-install.xml163(replaceable)
-#: ./doc/install-guide/section_glance-install.xml165(replaceable)
-#: ./doc/install-guide/section_glance-install.xml188(replaceable)
-#: ./doc/install-guide/section_glance-install.xml189(replaceable)
-#: ./doc/install-guide/section_glance-install.xml213(replaceable)
-#: ./doc/install-guide/section_glance-install.xml214(replaceable)
-#: ./doc/install-guide/section_glance-install.xml215(replaceable)
-#: ./doc/install-guide/section_keystone-install.xml30(replaceable)
-#: ./doc/install-guide/section_keystone-install.xml38(replaceable)
-#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml82(replaceable)
-#: ./doc/install-guide/object-storage/section_object-storage-install.xml101(replaceable)
-#: ./doc/install-guide/object-storage/section_object-storage-install.xml102(replaceable)
-#: ./doc/install-guide/object-storage/section_object-storage-install.xml103(replaceable)
-msgid "controller"
-msgstr "controller"
-
 #: ./doc/install-guide/ch_clients.xml37(para)
 msgid ""
 "<filename>demo-openrc.sh</filename> for the normal user: <placeholder-1/>"
 msgstr "一般ユーザー用の <filename>demo-openrc.sh</filename>: <placeholder-1/>"
 
+#: ./doc/install-guide/ch_basics.xml5(title)
+msgid "Basic environment configuration"
+msgstr "環境の基本設定"
+
+#: ./doc/install-guide/ch_basics.xml6(para)
+msgid ""
+"This chapter explains how to configure each node in the <link linkend"
+"=\"architecture_example-architectures\">example architectures</link> "
+"including the <link linkend=\"example-architecture-with-legacy-networking\">"
+" two-node architecture with legacy networking</link> and <link linkend"
+"=\"example-architecture-with-neutron-networking\">three-node architecture "
+"with OpenStack Networking (neutron)</link>."
+msgstr "本章は、<link linkend=\"architecture_example-architectures\">アーキテクチャー例</link>にある各ノードを設定する方法について説明します。<link linkend=\"example-architecture-with-legacy-networking\"> レガシーネットワークを持つ 2 ノードアーキテクチャー</link>と<link linkend=\"example-architecture-with-neutron-networking\">OpenStack Networking (neutron) を持つ 3 ノードアーキテクチャー</link>があります。"
+
+#: ./doc/install-guide/ch_basics.xml13(para)
+msgid ""
+"Although most environments include OpenStack Identity, Image Service, "
+"Compute, at least one networking service, and the dashboard, OpenStack "
+"Object Storage can operate independently of most other services. If your use"
+" case only involves Object Storage, you can skip to <xref linkend=\"object-"
+"storage-system-requirements\"/>. However, the dashboard will not work "
+"without at least OpenStack Image Service and Compute."
+msgstr "ほとんどの環境には、OpenStack Identity、Image Service、Compute、少なくとも 1 つのネットワークサービス、ダッシュボードがありますが、OpenStack Object Storage は他のほとんどのサービスと独立して動作できます。Object Storage のみを含むユースケースの場合、<xref linkend=\"object-storage-system-requirements\"/> まで進めます。しかしながらダッシュボードは、少なくとも OpenStack Image Service と Compute がないと動作しません。"
+
+#: ./doc/install-guide/ch_basics.xml22(para)
+msgid ""
+"You must use an account with administrative privileges to configure each "
+"node. Either run the commands as the <literal>root</literal> user or "
+"configure the <literal>sudo</literal> utility."
+msgstr "各ノードを設定するために、管理権限を持つアカウントを使用する必要があります。<literal>root</literal> ユーザーとしてコマンドを実行するか、<literal>sudo</literal> ユーティリティを設定します。"
+
+#: ./doc/install-guide/section_dashboard-system-reqs.xml6(title)
+msgid "System requirements"
+msgstr "システム要件"
+
+#: ./doc/install-guide/section_dashboard-system-reqs.xml7(para)
+msgid ""
+"Before you install the OpenStack dashboard, you must meet the following "
+"system requirements:"
+msgstr "OpenStack Dashboard をインストールする前に、以下のシステム要件を満たしている必要があります。"
+
+#: ./doc/install-guide/section_dashboard-system-reqs.xml11(para)
+msgid ""
+"OpenStack Compute installation. Enable the Identity Service for user and "
+"project management."
+msgstr "OpenStack Compute のインストール。ユーザーとプロジェクトの管理用の Identity Service の有効化。"
+
+#: ./doc/install-guide/section_dashboard-system-reqs.xml13(para)
+msgid "Note the URLs of the Identity Service and Compute endpoints."
+msgstr "Identity Service と Compute のエンドポイントの URL を記録します。"
+
+#: ./doc/install-guide/section_dashboard-system-reqs.xml17(para)
+msgid ""
+"Identity Service user with sudo privileges. Because Apache does not serve "
+"content from a root user, users must run the dashboard as an Identity "
+"Service user with sudo privileges."
+msgstr "sudo 権限を持つ Identity Service のユーザー。Apache は root ユーザーのコンテンツを処理しないため、ユーザーは sudo 権限を持つ Identity Service のユーザーとしてダッシュボードを実行する必要があります。"
+
+#: ./doc/install-guide/section_dashboard-system-reqs.xml23(para)
+msgid ""
+"Python 2.6 or 2.7. The Python version must support Django. The Python "
+"version should run on any system, including Mac OS X. Installation "
+"prerequisites might differ by platform."
+msgstr "Python 2.6 または 2.7。Python が Django をサポートするバージョンである必要があります。この Python のバージョンは Mac OS X を含め、あらゆるシステムで実行すべきです。インストールの前提条件はプラットフォームにより異なるかもしれません。"
+
+#: ./doc/install-guide/section_dashboard-system-reqs.xml29(para)
+msgid ""
+"Then, install and configure the dashboard on a node that can contact the "
+"Identity Service."
+msgstr "そして、Identity Service と通信できるノードに Dashboard をインストールし、設定します。"
+
+#: ./doc/install-guide/section_dashboard-system-reqs.xml31(para)
+msgid ""
+"Provide users with the following information so that they can access the "
+"dashboard through a web browser on their local machine:"
+msgstr "ユーザーのローカルマシンからウェブブラウザー経由で Dashboard にアクセスできるよう、以下の情報をユーザーに提供します。"
+
+#: ./doc/install-guide/section_dashboard-system-reqs.xml36(para)
+msgid "The public IP address from which they can access the dashboard"
+msgstr "Dashboard にアクセスできるパブリック IP アドレス。"
+
+#: ./doc/install-guide/section_dashboard-system-reqs.xml40(para)
+msgid "The user name and password with which they can access the dashboard"
+msgstr "Dashboard にアクセスできるユーザー名とパスワード。"
+
+#: ./doc/install-guide/section_dashboard-system-reqs.xml44(para)
+msgid ""
+"Your web browser, and that of your users, must support HTML5 and have "
+"cookies and JavaScript enabled."
+msgstr "お使いのウェブブラウザーが HTML5 をサポートし、クッキーと JavaScript を有効化されている必要があります。"
+
+#: ./doc/install-guide/section_dashboard-system-reqs.xml48(para)
+msgid ""
+"To use the VNC client with the dashboard, the browser must support HTML5 "
+"Canvas and HTML5 WebSockets."
+msgstr "Dashboard で VNC クライアントを使用する場合、ブラウザーが HTML5 Canvas と HTML5 WebSockets をサポートする必要があります。"
+
+#: ./doc/install-guide/section_dashboard-system-reqs.xml50(para)
+msgid ""
+"For details about browsers that support noVNC, see <link "
+"href=\"https://github.com/kanaka/noVNC/blob/master/README.md\">https://github.com/kanaka/noVNC/blob/master/README.md</link>,"
+" and <link href=\"https://github.com/kanaka/noVNC/wiki/Browser-"
+"support\">https://github.com/kanaka/noVNC/wiki/Browser-support</link>, "
+"respectively."
+msgstr "noVNC をサポートするブラウザーの詳細はそれぞれ <link href=\"https://github.com/kanaka/noVNC/blob/master/README.md\">https://github.com/kanaka/noVNC/blob/master/README.md</link> と <link href=\"https://github.com/kanaka/noVNC/wiki/Browser-support\">https://github.com/kanaka/noVNC/wiki/Browser-support</link> を参照してください。"
+
 #: ./doc/install-guide/section_launch-instance-nova.xml6(title)
 msgid "Launch an instance with legacy networking (nova-network)"
 msgstr "レガシーネットワーク (nova-network) を用いたインスタンスの起動"
@@ -1384,12 +3750,6 @@ msgid ""
 "<placeholder-1/> and add the public key to your OpenStack environment."
 msgstr "多くのクラウドイメージは、慣習的なユーザー名とパスワードによる認証ではなく、<glossterm baseform=\"public key authentication\">公開鍵認証</glossterm>をサポートします。インスタンスの起動前に、<placeholder-1/> を使用して公開鍵と秘密鍵のキーペアを生成し、OpenStack 環境に公開鍵を追加する必要があります。"
 
-#: ./doc/install-guide/section_launch-instance-nova.xml15(para)
-#: ./doc/install-guide/section_launch-instance-neutron.xml15(para)
-#: ./doc/install-guide/section_neutron-initial-networks.xml132(para)
-msgid "Source the <literal>demo</literal> tenant credentials:"
-msgstr "<literal>demo</literal> プロジェクトのクレデンシャルを読み込みます。"
-
 #: ./doc/install-guide/section_launch-instance-nova.xml19(para)
 #: ./doc/install-guide/section_launch-instance-neutron.xml19(para)
 msgid "Generate a key pair:"
@@ -1604,457 +3964,732 @@ msgid ""
 "assistance. We want your environment to work!"
 msgstr "インスタンスが起動しない、期待通り動作しない場合、詳細について <link href=\"http://docs.openstack.org/ops\"><citetitle>OpenStack Operations Guide</citetitle></link> を参照してください。または、支援を得るために<link linkend=\"app_community_support\">多くの他の選択肢</link>を利用してください。お使いの環境が動作することを期待しています。"
 
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-keystone_authtoken.xml30(None)
+#: ./doc/install-guide/ch_trove.xml6(title)
+msgid "Add the Database service"
+msgstr "Database サービスの追加"
+
+#: ./doc/install-guide/ch_trove.xml7(para)
 msgid ""
-"@@image: 'figures/debconf-"
-"screenshots/service_keystone_authtoken_server_hostname.png'; "
-"md5=aafd53894e1d960531d4901123952117"
-msgstr "@@image: 'figures/debconf-screenshots/service_keystone_authtoken_server_hostname.png'; md5=aafd53894e1d960531d4901123952117"
+"Use the <glossterm baseform=\"Database Service\">Database module</glossterm>"
+" to create cloud database resources. The integrated project name is "
+"<glossterm>trove</glossterm>."
+msgstr "クラウドデータベースリソースを作成するために、<glossterm baseform=\"Database Service\">Database モジュール</glossterm>を使用します。統合プロジェクトの名前は <glossterm>trove</glossterm> です。"
+
+#: ./doc/install-guide/ch_trove.xml10(para)
+msgid ""
+"This chapter is a work in progress. It may contain incorrect information, "
+"and will be updated frequently."
+msgstr "本章は作業中です。不正確な情報を含む可能性があり、頻繁に更新されます。"
+
+#: ./doc/install-guide/section_nova-networking-compute-node.xml6(para)
+msgid ""
+"This section covers deployment of a simple <glossterm>flat "
+"network</glossterm> that provides IP addresses to your instances via "
+"<glossterm>DHCP</glossterm>. If your environment includes multiple compute "
+"nodes, the <glossterm>multi-host</glossterm> feature provides redundancy by "
+"spreading network functions across compute nodes."
+msgstr "このセクションは、インスタンスに <glossterm>DHCP</glossterm> 経由で IP アドレスを提供する、シンプルな<glossterm baseform=\"flat network\">フラットネットワーク</glossterm>の導入について取り扱います。お使いの環境に複数のコンピュートノードがある場合、<glossterm>multi-host</glossterm> 機能により、コンピュートノードをまたがるネットワーク機能の分散により冗長性を提供します。"
+
+#: ./doc/install-guide/section_nova-networking-compute-node.xml13(title)
+msgid "To install legacy networking components"
+msgstr "レガシーネットワークのコンポーネントのインストール方法"
+
+#: ./doc/install-guide/section_nova-networking-compute-node.xml21(title)
+#: ./doc/install-guide/section_nova-networking-controller-node.xml9(title)
+msgid "To configure legacy networking"
+msgstr "レガシーネットワークの設定方法"
+
+#: ./doc/install-guide/section_nova-networking-compute-node.xml23(para)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml189(para)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml287(para)
+#: ./doc/install-guide/section_nova-networking-controller-node.xml11(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml325(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml369(para)
+#: ./doc/install-guide/section_heat-install.xml94(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml192(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml226(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml262(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml355(para)
+#: ./doc/install-guide/section_ceilometer-glance.xml20(para)
+msgid "Run the following commands:"
+msgstr "以下のコマンドを実行します。"
+
+#: ./doc/install-guide/section_nova-networking-compute-node.xml24(para)
+#: ./doc/install-guide/section_nova-networking-compute-node.xml57(para)
+msgid ""
+"Replace <replaceable>INTERFACE_NAME</replaceable> with the actual interface "
+"name for the external network. For example, <emphasis>eth1</emphasis> or "
+"<emphasis>ens224</emphasis>."
+msgstr "<replaceable>INTERFACE_NAME</replaceable> を外部ネットワーク用の実際のインターフェース名で置き換えます。例えば、<emphasis>eth1</emphasis> や <emphasis>ens224</emphasis> です。"
+
+#: ./doc/install-guide/section_nova-networking-compute-node.xml55(para)
+#: ./doc/install-guide/section_nova-networking-controller-node.xml18(para)
+msgid ""
+"Edit the <filename>/etc/nova/nova.conf</filename> file and add the following"
+" keys to the <literal>[DEFAULT]</literal> section:"
+msgstr "<filename>/etc/nova/nova.conf</filename> ファイルを編集し、以下のキーを <literal>[DEFAULT]</literal> セクションに追加します。"
+
+#: ./doc/install-guide/section_nova-networking-compute-node.xml77(para)
+msgid "Restart the services:"
+msgstr "サービスを再起動します。"
+
+#: ./doc/install-guide/section_nova-networking-compute-node.xml80(para)
+msgid "Start the services and configure them to start when the system boots:"
+msgstr "サービスを起動し、システム起動時に起動するよう設定します。"
 
 #. When image changes, this message will be marked fuzzy or untranslated for
 #. you.
 #. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-keystone_authtoken.xml37(None)
+#: ./doc/install-guide/section_glance-install.xml38(None)
 msgid ""
-"@@image: 'figures/debconf-"
-"screenshots/service_keystone_authtoken_admin_tenant_name.png'; "
-"md5=a935563e4fba9b00040e35cdcfffc732"
-msgstr "@@image: 'figures/debconf-screenshots/service_keystone_authtoken_admin_tenant_name.png'; md5=a935563e4fba9b00040e35cdcfffc732"
+"@@image: 'figures/debconf-screenshots/glance-common_pipeline_flavor.png'; "
+"md5=78bef92c36a140ad042074f6345d8917"
+msgstr "@@image: 'figures/debconf-screenshots/glance-common_pipeline_flavor.png'; md5=78bef92c36a140ad042074f6345d8917"
 
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-keystone_authtoken.xml44(None)
+#: ./doc/install-guide/section_glance-install.xml5(title)
+msgid "Install the Image Service"
+msgstr "Image Service のインストール"
+
+#: ./doc/install-guide/section_glance-install.xml6(para)
 msgid ""
-"@@image: 'figures/debconf-"
-"screenshots/service_keystone_authtoken_tenant_admin_user.png'; "
-"md5=fe3dc93c591b3e9783d4d05556efcf25"
-msgstr "@@image: 'figures/debconf-screenshots/service_keystone_authtoken_tenant_admin_user.png'; md5=fe3dc93c591b3e9783d4d05556efcf25"
+"The OpenStack Image Service acts as a registry for virtual disk images. "
+"Users can add new images or take a snapshot of an image from an existing "
+"server for immediate storage. Use snapshots for back up and as templates to "
+"launch new servers. You can store registered images in Object Storage or in "
+"other locations. For example, you can store images in simple file systems or"
+" external web servers."
+msgstr "OpenStack Image Service は仮想ディスクイメージの登録管理者として動作します。ユーザーは新しいイメージを追加できます。イメージのスナップショットを既存のサーバーの直接ストレージから取得できます。バックアップのため、または新しいサーバーを起動するためのテンプレートとしてスナップショットを使用します。登録済みイメージを Object Storage に保存できます。例えば、イメージをシンプルなファイルシステムや外部ウェブサーバーに保存できます。"
 
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-keystone_authtoken.xml51(None)
+#: ./doc/install-guide/section_glance-install.xml14(para)
 msgid ""
-"@@image: 'figures/debconf-"
-"screenshots/service_keystone_authtoken_admin_password.png'; "
-"md5=0c30c80315d5e636dbe93a938fc2822b"
-msgstr "@@image: 'figures/debconf-screenshots/service_keystone_authtoken_admin_password.png'; md5=0c30c80315d5e636dbe93a938fc2822b"
+"This procedure assumes you set the appropriate environment variables to your"
+" credentials as described in <xref linkend=\"keystone-verify\"/>."
+msgstr "この手順は <xref linkend=\"keystone-verify\"/> に記載されているとおり、適切な環境変数にクレデンシャルを設定していると仮定しています。"
 
-#: ./doc/install-guide/section_debconf-keystone_authtoken.xml6(title)
-msgid "Services and the [keystone_authtoken]"
-msgstr "サービスと [keystone_authtoken]"
+#: ./doc/install-guide/section_glance-install.xml20(para)
+msgid "Install the Image Service on the controller node:"
+msgstr "コントローラーノードに Image Service をインストールします。"
 
-#: ./doc/install-guide/section_debconf-keystone_authtoken.xml7(para)
+#: ./doc/install-guide/section_glance-install.xml27(para)
 msgid ""
-"Because most OpenStack services must access the Identity Service, you must "
-"configure the IP address of the <code>keystone</code> server to be able to "
-"access it. You must also configure the <code>admin_tenant_name</code>, "
-"<code>admin_user</code>, and <code>admin_password</code> options for each "
-"service to work."
-msgstr "多くの OpenStack サービスは Identity Service にアクセスする必要があるので、アクセスできるように <code>keystone</code> サーバーの IP アドレスを設定する必要があります。各サービスを動作させるために <code>admin_tenant_name</code>、<code>admin_user</code>、<code>admin_password</code> オプションも設定する必要があります。"
-
-#: ./doc/install-guide/section_debconf-keystone_authtoken.xml13(para)
-msgid "Generally, this section looks like this:"
-msgstr "一般的に、このセクションはこのようになります。"
-
-#: ./doc/install-guide/section_debconf-keystone_authtoken.xml21(para)
-msgid ""
-"The debconf system helps users configure the <code>auth_host</code>, "
-"<code>admin_tenant_name</code>, <code>admin_user</code> and "
-"<code>admin_password</code> options."
-msgstr "debconf システムはユーザーが <code>auth_host</code>、<code>admin_tenant_name</code>、<code>admin_user</code>、<code>admin_password</code> オプションを設定する支援をします。"
-
-#: ./doc/install-guide/section_debconf-keystone_authtoken.xml25(para)
-msgid "The following screens show an example Image Service configuration:"
-msgstr "以下の画面は Image Service 設定の例を示します。"
-
-#: ./doc/install-guide/section_debconf-keystone_authtoken.xml55(para)
-msgid ""
-"This information is stored in the configuration file for each service. For "
-"example:"
-msgstr "この情報は各サービスの設定ファイルに保存されます。例:"
-
-#: ./doc/install-guide/section_debconf-keystone_authtoken.xml63(para)
-msgid ""
-"The Debian OpenStack packages offer automation for this, so OpenStack users "
-"do not have to manually edit the configuration files."
-msgstr "Debian OpenStack パッケージがこれを自動化するため、OpenStack ユーザーは設定ファイルを手動で編集する必要がありません。"
-
-#: ./doc/install-guide/ch_swift.xml6(title)
-msgid "Add Object Storage"
-msgstr "Object Storage の追加"
-
-#: ./doc/install-guide/ch_swift.xml7(para)
-msgid ""
-"The OpenStack Object Storage services work together to provide object "
-"storage and retrieval through a REST API. For this example architecture, you"
-" must have already installed the Identity Service, also known as Keystone."
-msgstr "OpenStack Object Storage Service はオブジェクトストレージと REST API 経由の取得を提供するために一緒に動作します。このアーキテクチャー例は、Keystone として知られる Identity Service がすでにインストールされている必要があります。"
-
-#: ./doc/install-guide/ch_swift.xml31(para)
-msgid ""
-"Your OpenStack environment now includes Object Storage. You can <link "
-"linkend=\"launch-instance\">launch an instance</link> or add more services "
-"to your environment in the following chapters."
-msgstr "OpenStack 環境に Object Storage が追加されました。<link linkend=\"launch-instance\">インスタンスの起動</link>、以降の章に記載されているサービスの環境への追加を実行できます。"
-
-#: ./doc/install-guide/section_neutron-concepts.xml6(title)
-msgid "Networking concepts"
-msgstr "Networking の概念"
-
-#: ./doc/install-guide/section_neutron-concepts.xml7(para)
-msgid ""
-"OpenStack Networking (neutron) manages all of the networking facets for the "
-"Virtual Networking Infrastructure (VNI) and the access layer aspects of the "
-"Physical Networking Infrastructure (PNI) in your OpenStack environment. "
-"OpenStack Networking allows tenants to create advanced virtual network "
-"topologies including services such as <glossterm "
-"baseform=\"firewall\">firewalls</glossterm>, <glossterm baseform=\"load "
-"balancer\">load balancers</glossterm>, and <glossterm baseform=\"virtual "
-"private network (VPN)\"> virtual private networks (VPNs)</glossterm>."
-msgstr "OpenStack Networking (neutron) は OpenStack 環境で、仮想ネットワークインフラストラクチャ (VNI) のすべてのネットワークファセット、物理ネットワークインフラストラクチャ (PNI) のアクセス層の側面を管理します。OpenStack Networking により、プロジェクトが<glossterm baseform=\"firewall\">ファイアウォール</glossterm>、<glossterm baseform=\"load balancer\">負荷分散装置</glossterm>、<glossterm baseform=\"virtual private network (VPN)\">VPN</glossterm> などの高度な仮想ネットワークトポロジーを作成できるようになります。"
-
-#: ./doc/install-guide/section_neutron-concepts.xml16(para)
-msgid ""
-"Networking provides the following object abstractions: networks, subnets, "
-"and routers. Each has functionality that mimics its physical counterpart: "
-"networks contain subnets, and routers route traffic between different subnet"
-" and networks."
-msgstr "Networking はネットワーク、サブネット、ルーターのオブジェクトの抽象化を提供します。それぞれ、対応する物理的なものの機能を模倣します。ネットワークがサブネットを含みます。ルーターがサブネットやネットワーク間の通信を中継します。"
-
-#: ./doc/install-guide/section_neutron-concepts.xml20(para)
-msgid ""
-"Any given Networking set up has at least one external network. This network,"
-" unlike the other networks, is not merely a virtually defined network. "
-"Instead, it represents the view into a slice of the external network that is"
-" accessible outside the OpenStack installation. IP addresses on the "
-"Networking external network are accessible by anybody physically on the "
-"outside network. Because this network merely represents a slice of the "
-"outside network, DHCP is disabled on this network."
-msgstr "すべての Networking 環境は少なくとも 1 つの外部ネットワークを持ちます。このネットワークは、他のネットワークと異なり、ほとんど仮想的に定義されたネットワークではありません。これは OpenStack インストール環境の外部からアクセス可能な外部ネットワークの一部のビューであることを意味します。Networking 外部ネットワークの IP アドレスは外部ネットワークにある何らかの物理的なものによりアクセスできます。このネットワークがほとんど外部ネットワークの一部を表すため、DHCP はこのネットワークで無効化されます。"
-
-#: ./doc/install-guide/section_neutron-concepts.xml28(para)
-msgid ""
-"In addition to external networks, any Networking set up has one or more "
-"internal networks. These software-defined networks connect directly to the "
-"VMs. Only the VMs on any given internal network, or those on subnets "
-"connected through interfaces to a similar router, can access VMs connected "
-"to that network directly."
-msgstr "外部ネットワークに加えて、あらゆる Networking のセットアップ環境は 1 つ以上の内部ネットワークを持ちます。これらの SDN は仮想マシンに直接接続します。あらゆる指定された内部ネットワークにある仮想マシン、またはインターフェース経由で同様のルーターに接続されたサブネットにある仮想マシンのみが、そのネットワークに接続された仮想マシンに直接アクセスできます。"
-
-#: ./doc/install-guide/section_neutron-concepts.xml33(para)
-msgid ""
-"For the outside network to access VMs, and vice versa, routers between the "
-"networks are needed. Each router has one gateway that is connected to a "
-"network and many interfaces that are connected to subnets. Like a physical "
-"router, subnets can access machines on other subnets that are connected to "
-"the same router, and machines can access the outside network through the "
-"gateway for the router."
-msgstr "外部ネットワークが仮想マシンにアクセスするため、またその逆のため、ネットワーク間のルーターが必要になります。各ルーターはネットワークに接続された 1 つのゲートウェイとサブネットに接続された多くのインターフェースを持ちます。物理ルーターのように、同じルーターに接続された他のサブネットにあるマシンにサブネットがアクセスできます。また、マシンはルーターに対するゲートウェイ経由で外部ネットワークにアクセスできます。"
-
-#: ./doc/install-guide/section_neutron-concepts.xml40(para)
-msgid ""
-"Additionally, you can allocate IP addresses on external networks to ports on"
-" the internal network. Whenever something is connected to a subnet, that "
-"connection is called a port. You can associate external network IP addresses"
-" with ports to VMs. This way, entities on the outside network can access "
-"VMs."
-msgstr "さらに、内部ネットワークにたどり着くために外部ネットワークに IP アドレスを割り当てることができます。何かがサブネットに接続されたとき必ず、その接続がポートと呼ばれます。外部ネットワークの IP アドレスを仮想マシンのポートに関連づけられます。このように、外部ネットワークのものが仮想マシンにアクセスできます。"
-
-#: ./doc/install-guide/section_neutron-concepts.xml45(para)
-msgid ""
-"Networking also supports <emphasis role=\"italic\">security "
-"groups</emphasis>. Security groups enable administrators to define firewall "
-"rules in groups. A VM can belong to one or more security groups, and "
-"Networking applies the rules in those security groups to block or unblock "
-"ports, port ranges, or traffic types for that VM."
-msgstr "Networking は <emphasis role=\"italic\">セキュリティグループ</emphasis> もサポートします。セキュリティグループにより、管理者がグループでファイアウォールルールを定義できます。仮想マシンは 1 つ以上のセキュリティグループに属します。Networking が、ポート、ポート範囲、または通信種別をブロックするかブロックしないかのために、これらのセキュリティグループにあるルールを仮想マシンに対して適用します。"
-
-#: ./doc/install-guide/section_neutron-concepts.xml51(para)
-msgid ""
-"Each plug-in that Networking uses has its own concepts. While not vital to "
-"operating Networking, understanding these concepts can help you set up "
-"Networking. All Networking installations use a core plug-in and a security "
-"group plug-in (or just the No-Op security group plug-in). Additionally, "
-"Firewall-as-a-service (FWaaS) and Load-balancing-as-a-service (LBaaS) plug-"
-"ins are available."
-msgstr "Networking が使用する各プラグインはそれぞれ独自の概念を持ちます。Networking を稼働されるために必須ではありませんが、これらの概念を理解することにより、Networking をセットアップする役に立つでしょう。すべての Networking インストール環境は、コアプラグインとセキュリティグループプラグイン (またはただの No-Op セキュリティグループプラグイン) を使用します。さらに、Firewall-as-a-service (FWaaS) と Load-balancing-as-a-service (LBaaS) プラグインが利用可能です。"
-
-#: ./doc/install-guide/section_ceilometer-install.xml10(title)
-msgid "Install the Telemetry module"
-msgstr "Telemetry モジュールのインストール"
-
-#: ./doc/install-guide/section_ceilometer-install.xml12(para)
-msgid ""
-"Telemetry provides an API service that provides a collector and a range of "
-"disparate agents. Before you can install these agents on nodes such as the "
-"compute node, you must use this procedure to install the core components on "
-"the controller node."
-msgstr "Telemetry は情報収集機能とさまざまな種類のエージェントを提供する API サービスです。コンピュートノードのようなノードにこれらのエージェントをインストールする前に、コントローラーノードにコアコンポーネントをインストールするために、この手順を使用する必要があります。"
-
-#: ./doc/install-guide/section_ceilometer-install.xml18(para)
-msgid "Install the Telemetry service on the controller node:"
-msgstr "コントローラーノードに Telemetry Service をインストールします。"
-
-#: ./doc/install-guide/section_ceilometer-install.xml30(para)
-msgid ""
-"Respond to the prompts for <link linkend=\"debconf-"
+"Respond to prompts for <link linkend=\"debconf-dbconfig-common\">database "
+"management</link>, <link linkend=\"debconf-"
 "keystone_authtoken\"><literal>[keystone_authtoken]</literal> "
 "settings</link>, <link linkend=\"debconf-rabbitqm\">RabbitMQ "
 "credentials</link> and <link linkend=\"debconf-api-endpoints\">API "
-"endpoint</link> registration."
-msgstr "<link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> 設定</link>、<link linkend=\"debconf-rabbitqm\">RabbitMQ クレデンシャル</link>、<link linkend=\"debconf-api-endpoints\">API エンドポイント</link>の登録に関するプロンプトに答えます。"
+"endpoint</link> registration. You must also select the caching type:"
+msgstr "<link linkend=\"debconf-dbconfig-common\">データベース管理</link>、<link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> 設定</link>、<link linkend=\"debconf-rabbitqm\">RabbitMQ クレデンシャル</link>、<link linkend=\"debconf-api-endpoints\">API エンドポイント</link>登録に関するプロンプトに答えます。キャッシュタイプを選択する必要もあります。"
 
-#: ./doc/install-guide/section_ceilometer-install.xml38(para)
+#: ./doc/install-guide/section_glance-install.xml43(para)
 msgid ""
-"The Telemetry service uses a database to store information. Specify the "
-"location of the database in the configuration file. The examples use a "
-"MongoDB database on the controller node:"
-msgstr "Telemetry Service は情報を保存するためにデータベースを使用します。設定ファイルでデータベースの場所を指定します。この例はコントローラーノードで MongoDB データベースを使用します。"
+"The Image Service stores information about images in a database. The "
+"examples in this guide use the MySQL database that is used by other "
+"OpenStack services."
+msgstr "Image Service はイメージに関する情報をデータベースに保存します。このガイドの例は、他の OpenStack サービスにより使用されている MySQL データベースを使用します。"
 
-#: ./doc/install-guide/section_ceilometer-install.xml46(para)
+#: ./doc/install-guide/section_glance-install.xml46(para)
 msgid ""
-"By default MongoDB is configured to create several 1GB files in the "
-"/var/lib/mongodb/journal/ directory to support database journaling."
-msgstr "MongoDB はデフォルトで、データベースのジャーナリングをサポートするために、/var/lib/mongodb/journal/  ディレクトリにいくつかの 1GB のファイルを作成するよう設定されます。"
+"Configure the location of the database. The Image Service provides the "
+"<systemitem class=\"service\">glance-api</systemitem> and <systemitem "
+"class=\"service\">glance-registry</systemitem> services, each with its own "
+"configuration file. You must update both configuration files throughout this"
+" section. Replace <replaceable>GLANCE_DBPASS</replaceable> with your Image "
+"Service database password."
+msgstr "データベースの位置を設定します。Image Service はそれぞれの設定ファイルを用いて <systemitem class=\"service\">glance-api</systemitem> サービスと <systemitem class=\"service\">glance-registry</systemitem> サービスを提供します。このセクションを通して両方の設定ファイルを更新する必要があります。<replaceable>GLANCE_DBPASS</replaceable> をお使いの Image Service データベースのパスワードで置き換えます。"
 
-#: ./doc/install-guide/section_ceilometer-install.xml51(para)
+#: ./doc/install-guide/section_glance-install.xml55(replaceable)
+#: ./doc/install-guide/section_glance-install.xml57(replaceable)
+#: ./doc/install-guide/section_glance-install.xml120(replaceable)
+#: ./doc/install-guide/section_glance-install.xml122(replaceable)
+msgid "GLANCE_DBPASS"
+msgstr "GLANCE_DBPASS"
+
+#: ./doc/install-guide/section_glance-install.xml58(para)
 msgid ""
-"If you need to minimize the space allocated to support database journaling "
-"then set the <option>smallfiles</option> configuration key to "
-"<literal>true</literal> in the <filename>/etc/mongodb.conf</filename> "
-"configuration file. This configuration reduces the size of each journaling "
-"file to 512MB."
-msgstr "データベースのジャーナリングをサポートするために割り当てられる領域を最小化する必要がある場合、<filename>/etc/mongodb.conf</filename> 設定ファイルにある <option>smallfiles</option> 設定キーを <literal>true</literal> に設定します。この設定により、各ジャーナルファイルの容量が 512MB に減ります。"
+"Edit <filename>/etc/glance/glance-api.conf</filename> and "
+"<filename>/etc/glance/glance-registry.conf</filename> and edit the "
+"<literal>[database]</literal> section of each file:"
+msgstr "<filename>/etc/glance/glance-api.conf</filename> と <filename>/etc/glance/glance-registry.conf</filename> の <literal>[database]</literal> セクションを編集します。"
 
-#: ./doc/install-guide/section_ceilometer-install.xml59(para)
+#: ./doc/install-guide/section_glance-install.xml70(para)
+#: ./doc/install-guide/section_glance-install.xml77(para)
+#: ./doc/install-guide/section_glance-install.xml95(para)
+msgid "Configure the Image Service to use the message broker:"
+msgstr "Image Service がメッセージブローカーを使用するよう設定します。"
+
+#: ./doc/install-guide/section_glance-install.xml80(para)
 msgid ""
-"As the files are created the first time the MongoDB service starts you must "
-"stop the service and remove the files for this change to take effect:"
-msgstr "MongoDB サービスを初めて起動するときに、このファイルが作成されるので、この変更を反映するためにサービスを停止して、このファイルを削除する必要があります。"
+"Edit the <filename>/etc/glance/glance-api.conf</filename> file and add the "
+"following keys to the <literal>[DEFAULT]</literal> section:"
+msgstr "<filename>/etc/glance/glance-api.conf</filename> ファイルを編集し、以下のキーを <literal>[DEFAULT]</literal> セクションに追加します。"
 
-#: ./doc/install-guide/section_ceilometer-install.xml67(para)
+#: ./doc/install-guide/section_glance-install.xml83(para)
+#: ./doc/install-guide/section_glance-install.xml96(para)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml106(para)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml132(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml183(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml209(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml109(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml135(para)
 msgid ""
-"For more information on the <option>smallfiles</option> configuration key "
-"refer to the MongoDB documentation at <link "
-"href=\"http://docs.mongodb.org/manual/reference/configuration-"
-"options/#smallfiles\"/>."
-msgstr "<option>smallfiles</option> 設定キーの詳細は MongoDB のドキュメント <link href=\"http://docs.mongodb.org/manual/reference/configuration-options/#smallfiles\"/> を参照してください。"
+"Replace <replaceable>RABBIT_PASS</replaceable> with the password you chose "
+"for the <literal>guest</literal> account in "
+"<application>RabbitMQ</application>."
+msgstr "<replaceable>RABBIT_PASS</replaceable> を <application>RabbitMQ</application> の <literal>guest</literal> アカウント用に選んだパスワードで置き換えます。"
 
-#: ./doc/install-guide/section_ceilometer-install.xml72(para)
+#: ./doc/install-guide/section_glance-install.xml108(para)
 msgid ""
-"For instructions detailing the steps to disable database journaling entirely"
-" refer to <link href=\"http://docs.mongodb.org/manual/tutorial/manage-"
-"journaling/\"/>."
-msgstr "データベースのジャーナリング自体を無効化する手順の詳細は <link href=\"http://docs.mongodb.org/manual/tutorial/manage-journaling/\"/> を参照してください。"
+"By default, the Ubuntu packages create an SQLite database. Delete the "
+"<filename>glance.sqlite</filename> file created in the "
+"<filename>/var/lib/glance/</filename> directory so that it does not get used"
+" by mistake:"
+msgstr "Ubuntu パッケージはデフォルトで SQLite データベースを作成します。誤って使用されないように、<filename>/var/lib/glance/</filename> に作成された <filename>glance.sqlite</filename> ファイルを削除します。"
 
-#: ./doc/install-guide/section_ceilometer-install.xml80(para)
+#: ./doc/install-guide/section_glance-install.xml115(para)
 msgid ""
-"Configure MongoDB to make it listen on the controller management IP address."
-" Edit the <filename>/etc/mongodb.conf</filename> file and modify the "
-"<literal>bind_ip</literal> key:"
-msgstr "コントローラーの管理 IP アドレスをリッスンするよう MongoDB を設定します。<filename>/etc/mongodb.conf</filename> ファイルを編集し、<literal>bind_ip</literal> キーを変更します。"
+"Use the password you created to log in as root and create a "
+"<literal>glance</literal> database user:"
+msgstr "root としてログインするために、作成したパスワードを使用します。<literal>glance</literal> データベースユーザーを作成します。"
 
-#: ./doc/install-guide/section_ceilometer-install.xml86(para)
-msgid "Restart the MongoDB service to apply the configuration change:"
-msgstr "設定の変更を適用するために MongoDB のサービスを再起動します。"
+#: ./doc/install-guide/section_glance-install.xml125(para)
+msgid "Create the database tables for the Image Service:"
+msgstr "Image Service 用のデータベーステーブルを作成します。"
 
-#: ./doc/install-guide/section_ceilometer-install.xml90(para)
+#: ./doc/install-guide/section_glance-install.xml129(para)
 msgid ""
-"Start the MongoDB server and configure it to start when the system boots:"
-msgstr "MongoDB サーバーを起動し、システム起動時に起動するよう設定します。"
-
-#: ./doc/install-guide/section_ceilometer-install.xml100(para)
-msgid "Create the database and a <literal>ceilometer</literal> database user:"
-msgstr "データベースと <literal>ceilometer</literal> データベースユーザーを作成します。"
-
-#: ./doc/install-guide/section_ceilometer-install.xml105(replaceable)
-#: ./doc/install-guide/section_ceilometer-install.xml111(replaceable)
-#: ./doc/install-guide/section_ceilometer-install.xml118(replaceable)
-msgid "CEILOMETER_DBPASS"
-msgstr "CEILOMETER_DBPASS"
-
-#: ./doc/install-guide/section_ceilometer-install.xml109(para)
-msgid "Configure the Telemetry service to use the database:"
-msgstr "Telemetry Service がデータベースを使用するよう設定します。"
-
-#: ./doc/install-guide/section_ceilometer-install.xml112(para)
-msgid ""
-"Edit the <filename>/etc/ceilometer/ceilometer.conf</filename> file and "
-"change the <literal>[database]</literal> section:"
-msgstr "<filename>/etc/ceilometer/ceilometer.conf</filename> ファイルを編集し、<literal>[database]</literal> セクションを変更します。"
-
-#: ./doc/install-guide/section_ceilometer-install.xml122(para)
-msgid ""
-"You must define a secret key that is used as a shared secret among Telemetry"
-" service nodes. Use <placeholder-1/> to generate a random token and store it"
-" in the configuration file:"
-msgstr "Telemetry Service のノード間で共有するシークレットとして使用するシークレットキーを定義する必要があります。ランダムなトークンを生成するために <placeholder-1/> を使用し、それを設定ファイルに保存します。"
-
-#: ./doc/install-guide/section_ceilometer-install.xml129(para)
-msgid "For SUSE Linux Enterprise, run the following command:"
-msgstr "SUSE Linux Enterprise の場合、以下のコマンドを実行します。"
-
-#: ./doc/install-guide/section_ceilometer-install.xml133(para)
-msgid ""
-"Edit the <filename>/etc/ceilometer/ceilometer.conf</filename> file and "
-"change the <literal>[publisher]</literal> section. Replace "
-"<replaceable>CEILOMETER_TOKEN</replaceable> with the results of the "
-"<literal>openssl</literal> command:"
-msgstr "<filename>/etc/ceilometer/ceilometer.conf</filename> ファイルを編集し、<literal>[publisher]</literal> セクションを変更します。<replaceable>CEILOMETER_TOKEN</replaceable> を <literal>openssl</literal> コマンドの出力で置き換えます。"
-
-#: ./doc/install-guide/section_ceilometer-install.xml140(replaceable)
-#: ./doc/install-guide/section_ceilometer-nova.xml62(replaceable)
-#: ./doc/install-guide/section_ceilometer-nova.xml70(replaceable)
-msgid "CEILOMETER_TOKEN"
-msgstr "CEILOMETER_TOKEN"
-
-#: ./doc/install-guide/section_ceilometer-install.xml144(para)
-#: ./doc/install-guide/section_ceilometer-nova.xml74(para)
-msgid "Configure the RabbitMQ access:"
-msgstr "RabbitMQ のアクセス権を設定します。"
-
-#: ./doc/install-guide/section_ceilometer-install.xml146(replaceable)
-#: ./doc/install-guide/section_ceilometer-install.xml149(replaceable)
-#: ./doc/install-guide/section_trove-install.xml105(replaceable)
-#: ./doc/install-guide/section_trove-install.xml125(replaceable)
-#: ./doc/install-guide/section_trove-install.xml127(replaceable)
-#: ./doc/install-guide/section_trove-install.xml129(replaceable)
-#: ./doc/install-guide/section_trove-install.xml221(replaceable)
-#: ./doc/install-guide/section_nova-controller.xml70(replaceable)
-#: ./doc/install-guide/section_nova-controller.xml78(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml198(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml207(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml193(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml216(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml153(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml180(replaceable)
-#: ./doc/install-guide/section_ceilometer-glance.xml18(replaceable)
-#: ./doc/install-guide/section_ceilometer-glance.xml24(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml149(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml158(replaceable)
-#: ./doc/install-guide/section_cinder-node.xml153(replaceable)
-#: ./doc/install-guide/section_cinder-node.xml174(replaceable)
-#: ./doc/install-guide/section_cinder-controller.xml123(replaceable)
-#: ./doc/install-guide/section_cinder-controller.xml145(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml119(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml142(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml116(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml139(replaceable)
-#: ./doc/install-guide/section_basics-queue.xml77(replaceable)
-#: ./doc/install-guide/section_heat-install.xml93(replaceable)
-#: ./doc/install-guide/section_heat-install.xml96(replaceable)
-#: ./doc/install-guide/section_ceilometer-nova.xml76(replaceable)
-#: ./doc/install-guide/section_ceilometer-nova.xml80(replaceable)
-#: ./doc/install-guide/section_nova-compute.xml115(replaceable)
-#: ./doc/install-guide/section_nova-compute.xml121(replaceable)
-#: ./doc/install-guide/section_glance-install.xml90(replaceable)
-#: ./doc/install-guide/section_glance-install.xml104(replaceable)
-msgid "RABBIT_PASS"
-msgstr "RABBIT_PASS"
-
-#: ./doc/install-guide/section_ceilometer-install.xml147(para)
-#: ./doc/install-guide/section_ceilometer-install.xml166(para)
-#: ./doc/install-guide/section_ceilometer-nova.xml77(para)
-#: ./doc/install-guide/section_ceilometer-nova.xml130(para)
-msgid ""
-"Edit the <filename>/etc/ceilometer/ceilometer.conf</filename> file and "
-"update the <literal>[DEFAULT]</literal> section:"
-msgstr "<filename>/etc/ceilometer/ceilometer.conf</filename> ファイルを編集し、<literal>[DEFAULT]</literal> セクションを更新します。"
-
-#: ./doc/install-guide/section_ceilometer-install.xml153(para)
-msgid "Configure the Qpid access:"
-msgstr "Qpid のアクセス権を設定します。"
-
-#: ./doc/install-guide/section_ceilometer-install.xml159(para)
-msgid "Configure the collector dispatcher:"
-msgstr "コレクターディスパッチャーを設定します。"
-
-#: ./doc/install-guide/section_ceilometer-install.xml165(para)
-#: ./doc/install-guide/section_ceilometer-nova.xml129(para)
-msgid "Configure the log directory."
-msgstr "ログディレクトリを設定します。"
-
-#: ./doc/install-guide/section_ceilometer-install.xml173(para)
-msgid ""
-"Create a <literal>ceilometer</literal> user that the Telemetry service uses "
-"to authenticate with the Identity Service. Use the "
+"Create a <literal>glance</literal> user that the Image Service can use to "
+"authenticate with the Identity service. Choose a password and specify an "
+"email address for the <literal>glance</literal> user. Use the "
 "<literal>service</literal> tenant and give the user the "
 "<literal>admin</literal> role:"
-msgstr "Telemetry Service が Identity Service で認証するために使用する <literal>ceilometer</literal> ユーザーを作成します。<literal>service</literal> プロジェクトを使用し、ユーザーに <literal>admin</literal> ロールを与えます。"
+msgstr "Image Service が Identity Service で認証するために使用する <literal>glance</literal> ユーザーを作成します。<literal>service</literal> プロジェクトを使用し、ユーザーに <literal>admin</literal> ロールを与えます。"
 
-#: ./doc/install-guide/section_ceilometer-install.xml177(replaceable)
-#: ./doc/install-guide/section_ceilometer-install.xml206(replaceable)
-#: ./doc/install-guide/section_ceilometer-install.xml214(replaceable)
-#: ./doc/install-guide/section_ceilometer-install.xml226(replaceable)
-#: ./doc/install-guide/section_ceilometer-install.xml233(replaceable)
-#: ./doc/install-guide/section_ceilometer-nova.xml99(replaceable)
-#: ./doc/install-guide/section_ceilometer-nova.xml105(replaceable)
-#: ./doc/install-guide/section_ceilometer-nova.xml118(replaceable)
-#: ./doc/install-guide/section_ceilometer-nova.xml125(replaceable)
-msgid "CEILOMETER_PASS"
-msgstr "CEILOMETER_PASS"
+#: ./doc/install-guide/section_glance-install.xml135(replaceable)
+#: ./doc/install-guide/section_glance-install.xml159(replaceable)
+#: ./doc/install-guide/section_glance-install.xml175(replaceable)
+#: ./doc/install-guide/section_glance-install.xml194(replaceable)
+msgid "GLANCE_PASS"
+msgstr "GLANCE_PASS"
 
-#: ./doc/install-guide/section_ceilometer-install.xml177(replaceable)
-msgid "ceilometer@example.com"
-msgstr "ceilometer@example.com"
+#: ./doc/install-guide/section_glance-install.xml136(replaceable)
+msgid "glance@example.com"
+msgstr "glance@example.com"
 
-#: ./doc/install-guide/section_ceilometer-install.xml181(para)
+#: ./doc/install-guide/section_glance-install.xml140(para)
 msgid ""
-"Configure the Telemetry service to authenticate with the Identity Service."
-msgstr "Identity Service を用いて認証するよう Telemetry を設定します。"
+"Configure the Image Service to use the Identity Service for authentication."
+msgstr "Image Service が認証用に Identity Service を使用するよう設定します。"
 
-#: ./doc/install-guide/section_ceilometer-install.xml183(para)
+#: ./doc/install-guide/section_glance-install.xml142(para)
 msgid ""
-"Set the <option>auth_strategy</option> value to <literal>keystone</literal> "
-"in the <filename>/etc/ceilometer/ceilometer.conf</filename> file:"
-msgstr "<filename>/etc/ceilometer/ceilometer.conf</filename> ファイルで <option>auth_strategy</option> の値を <literal>keystone</literal> に設定します。"
+"Run the following commands and replace "
+"<replaceable>GLANCE_PASS</replaceable> with the password you chose for the "
+"<literal>glance</literal> user in the Identity Service:"
+msgstr "以下のコマンドを実行します。Identity Service で <literal>glance</literal> ユーザー用に選択したパスワードで <replaceable>GLANCE_PASS</replaceable> を置き換えます。"
 
-#: ./doc/install-guide/section_ceilometer-install.xml193(para)
+#: ./doc/install-guide/section_glance-install.xml178(para)
 msgid ""
-"Add the credentials to the configuration files for the Telemetry service:"
-msgstr "クレデンシャルを Telemetry Service の設定ファイルに追加します。"
+"Edit the <filename>/etc/glance/glance-api.conf</filename> and "
+"<filename>/etc/glance/glance-registry.conf</filename> files. Replace "
+"<replaceable>GLANCE_PASS</replaceable> with the password you chose for the "
+"<literal>glance</literal> user in the Identity service."
+msgstr "<filename>/etc/glance/glance-api.conf</filename> ファイルと <filename>/etc/glance/glance-registry.conf</filename> ファイルを編集します。Identity Service で <literal>glance</literal> ユーザー用に選択したパスワードで <replaceable>GLANCE_PASS</replaceable> を置き換えます。"
 
-#: ./doc/install-guide/section_ceilometer-install.xml215(para)
-#: ./doc/install-guide/section_ceilometer-nova.xml108(para)
+#: ./doc/install-guide/section_glance-install.xml185(para)
 msgid ""
-"Edit the <filename>/etc/ceilometer/ceilometer.conf</filename> file and "
-"change the <literal>[keystone_authtoken]</literal> section:"
-msgstr "<filename>/etc/ceilometer/ceilometer.conf</filename> ファイルを編集し、<literal>[keystone_authtoken]</literal> セクションを変更します。"
+"Add or modify the following keys under the "
+"<literal>[keystone_authtoken]</literal> section:"
+msgstr "以下のキーを <literal>[keystone_authtoken]</literal> セクションに追加または修正します。"
 
-#: ./doc/install-guide/section_ceilometer-install.xml227(para)
-#: ./doc/install-guide/section_ceilometer-nova.xml119(para)
-msgid "Also set the <literal>[service_credentials]</literal> section:"
-msgstr "<literal>[service_credentials]</literal> セクションも設定します。"
-
-#: ./doc/install-guide/section_ceilometer-install.xml236(para)
+#: ./doc/install-guide/section_glance-install.xml197(para)
 msgid ""
-"Register the Telemetry service with the Identity Service so that other "
-"OpenStack services can locate it. Use the <placeholder-1/> command to "
-"register the service and specify the endpoint:"
-msgstr "他の OpenStack サービスから使用できるように、Telemetry Service を Identity Service に登録します。サービスを登録し、エンドポイントを指定するために、<placeholder-1/> コマンドを使用します。"
+"Modify the following key under the <literal>[paste_deploy]</literal> "
+"section:"
+msgstr "以下のキーを <literal>[paste_deploy]</literal> セクションに修正します。"
 
-#: ./doc/install-guide/section_ceilometer-install.xml249(para)
-msgid "Restart the services with their new settings:"
-msgstr "新しい設定を用いてサービスを再起動します。"
-
-#: ./doc/install-guide/section_ceilometer-install.xml258(para)
+#: ./doc/install-guide/section_glance-install.xml206(para)
 msgid ""
-"Start the <systemitem class=\"service\">openstack-ceilometer-"
-"api</systemitem>, <systemitem class=\"service\" os=\"opensuse;sles"
-"\">openstack-ceilometer-agent-central</systemitem><systemitem "
-"class=\"service\" os=\"rhel;fedora;centos\">openstack-ceilometer-"
-"central</systemitem>, <systemitem class=\"service\">openstack-ceilometer-"
-"collector</systemitem>, <systemitem class=\"service\" os=\"opensuse;sles"
-"\">openstack-ceilometer-alarm-evaluator</systemitem>, and <systemitem "
-"class=\"service\" os=\"opensuse;sles\">openstack-ceilometer-alarm-"
-"notifier</systemitem> services and configure them to start when the system "
-"boots:"
-msgstr " <systemitem class=\"service\">openstack-ceilometer-api</systemitem>、<systemitem class=\"service\" os=\"opensuse;sles\">openstack-ceilometer-agent-central</systemitem><systemitem class=\"service\" os=\"rhel;fedora;centos\">openstack-ceilometer-central</systemitem>、<systemitem class=\"service\">openstack-ceilometer-collector</systemitem>、<systemitem class=\"service\" os=\"opensuse;sles\">openstack-ceilometer-alarm-evaluator</systemitem>、<systemitem class=\"service\" os=\"opensuse;sles\">openstack-ceilometer-alarm-notifier</systemitem> サービスを起動し、システムの起動時にそれらが起動するよう設定します。"
+"Register the Image Service with the Identity service so that other OpenStack"
+" services can locate it. Register the service and create the endpoint:"
+msgstr "他の OpenStack サービスから使用できるように、Image Service を Identity Service に登録します。サービスを登録し、エンドポイントを作成します。"
+
+#: ./doc/install-guide/section_glance-install.xml218(para)
+msgid ""
+"Restart the <systemitem class=\"service\">glance</systemitem> service with "
+"its new settings:"
+msgstr "新しい設定を用いて <systemitem class=\"service\">glance</systemitem> サービスを再起動します。"
+
+#: ./doc/install-guide/section_glance-install.xml224(para)
+msgid ""
+"Start the <systemitem class=\"service\">glance-api</systemitem> and "
+"<systemitem class=\"service\">glance-registry</systemitem> services and "
+"configure them to start when the system boots:"
+msgstr "<systemitem class=\"service\">glance-api</systemitem>、<systemitem class=\"service\">glance-registry</systemitem> サービスを起動し、システムの起動時にそれらが起動するよう設定します。"
+
+#: ./doc/install-guide/section_dashboard-install.xml7(title)
+msgid "Install the dashboard"
+msgstr "Dashboard のインストール"
+
+#: ./doc/install-guide/section_dashboard-install.xml8(para)
+msgid ""
+"Before you can install and configure the dashboard, meet the requirements in"
+" <xref linkend=\"dashboard-system-requirements\"/>."
+msgstr "Dashboard をインストールし、設定する前に <xref linkend=\"dashboard-system-requirements\"/> にある要件を満たしている必要があります。"
+
+#: ./doc/install-guide/section_dashboard-install.xml12(para)
+msgid ""
+"When you install only Object Storage and the Identity Service, even if you "
+"install the dashboard, it does not pull up projects and is unusable."
+msgstr "bject Storage と Identity Service のみをインストールしたとき、Dashboard をインストールしても、プロジェクトが表示されず、使用することもできません。"
+
+#: ./doc/install-guide/section_dashboard-install.xml16(para)
+msgid ""
+"For more information about how to deploy the dashboard, see <link "
+"href=\"http://docs.openstack.org/developer/horizon/topics/deployment.html\">deployment"
+" topics in the developer documentation</link>."
+msgstr "Dashboard の導入方法の詳細は <link href=\"http://docs.openstack.org/developer/horizon/topics/deployment.html\">deployment topics in the developer documentation</link> を参照してください。"
+
+#: ./doc/install-guide/section_dashboard-install.xml22(para)
+msgid ""
+"Install the dashboard on the node that can contact the Identity Service as "
+"root:"
+msgstr "Identity Service と通信できるノードに root として Dashboard をインストールします。"
+
+#: ./doc/install-guide/section_dashboard-install.xml28(title)
+msgid "Note for Ubuntu users"
+msgstr "Ubuntu ユーザー向け注記"
+
+#: ./doc/install-guide/section_dashboard-install.xml30(para)
+msgid ""
+"Remove the <literal>openstack-dashboard-ubuntu-theme</literal> package. This"
+" theme prevents translations, several menus as well as the network map from "
+"rendering correctly: <placeholder-1/>"
+msgstr "<literal>openstack-dashboard-ubuntu-theme</literal> パッケージを削除します。このテーマは翻訳、いくつかのメニュー、ネットワークマップが正しく表示されません。 <placeholder-1/>"
+
+#: ./doc/install-guide/section_dashboard-install.xml39(title)
+msgid "Note for Debian users"
+msgstr "Debian ユーザー向けの注記"
+
+#: ./doc/install-guide/section_dashboard-install.xml40(para)
+msgid "To install the Apache package:"
+msgstr "Apache のパッケージをインストールする方法:"
+
+#: ./doc/install-guide/section_dashboard-install.xml42(para)
+msgid ""
+"This command installs and configures Apache correctly, provided that the "
+"user asks for it during the <package>debconf</package> prompts. The default "
+"SSL certificate is self-signed, and it is probably wise to have it signed by"
+" a root Certificate Authority (CA)."
+msgstr "このコマンドはユーザーが <package>debconf</package> プロンプトに答えたとおりに Apache を正しくインストールし、設定します。標準の SSL 証明書は自己署名です。ルート認証局 (CA) により署名されたものを使用したほうが良いです。"
+
+#: ./doc/install-guide/section_dashboard-install.xml51(para)
+msgid ""
+"Modify the value of <literal>CACHES['default']['LOCATION']</literal> in "
+"<filename os=\"ubuntu;debian\">/etc/openstack-"
+"dashboard/local_settings.py</filename><filename "
+"os=\"centos;fedora;rhel\">/etc/openstack-"
+"dashboard/local_settings</filename><filename os=\"opensuse;sles\">/srv/www"
+"/openstack-dashboard/openstack_dashboard/local/local_settings.py</filename> "
+"to match the ones set in <filename "
+"os=\"ubuntu;debian\">/etc/memcached.conf</filename><filename "
+"os=\"centos;fedora;rhel;opensuse;sles\">/etc/sysconfig/memcached</filename>."
+msgstr "<filename os=\"ubuntu;debian\">/etc/memcached.conf</filename><filename os=\"centos;fedora;rhel;opensuse;sles\">/etc/sysconfig/memcached</filename> に設定したものと一致されるために、<filename os=\"ubuntu;debian\">/etc/openstack-dashboard/local_settings.py</filename><filename os=\"centos;fedora;rhel\">/etc/openstack-dashboard/local_settings</filename><filename os=\"opensuse;sles\">/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py</filename> の <literal>CACHES['default']['LOCATION']</literal> の値を変更します。"
+
+#: ./doc/install-guide/section_dashboard-install.xml63(para)
+msgid ""
+"Open <filename os=\"ubuntu;debian\">/etc/openstack-"
+"dashboard/local_settings.py</filename><filename "
+"os=\"centos;fedora;rhel\">/etc/openstack-dashboard/local_settings</filename>"
+" and look for this line:"
+msgstr "<filename os=\"ubuntu;debian\">/etc/openstack-dashboard/local_settings.py</filename><filename os=\"centos;fedora;rhel\">/etc/openstack-dashboard/local_settings</filename> を開き、この行を探します。"
+
+#: ./doc/install-guide/section_dashboard-install.xml76(title)
+#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml29(td)
+msgid "Notes"
+msgstr "注"
+
+#: ./doc/install-guide/section_dashboard-install.xml79(para)
+msgid ""
+"The address and port must match the ones set in <filename "
+"os=\"ubuntu;debian\">/etc/memcached.conf</filename><filename "
+"os=\"centos;fedora;rhel;opensuse;sles\">/etc/sysconfig/memcached</filename>."
+msgstr "アドレスとポートは <filename os=\"ubuntu;debian\">/etc/memcached.conf</filename><filename os=\"centos;fedora;rhel;opensuse;sles\">/etc/sysconfig/memcached</filename> に設定したものと一致する必要があります。"
+
+#: ./doc/install-guide/section_dashboard-install.xml84(para)
+msgid ""
+"If you change the memcached settings, you must restart the Apache web server"
+" for the changes to take effect."
+msgstr "memcached 設定を変更する場合、変更を反映するために Apache ウェブサーバーを再起動する必要があります。"
+
+#: ./doc/install-guide/section_dashboard-install.xml89(para)
+msgid ""
+"You can use options other than memcached option for session storage. Set the"
+" session back-end through the <parameter>SESSION_ENGINE</parameter> option."
+msgstr "セッションストレージのために memcached 以外のオプションを使用することもできます。<parameter>SESSION_ENGINE</parameter> オプションによりセッションバックエンドを設定します。"
+
+#: ./doc/install-guide/section_dashboard-install.xml96(para)
+msgid ""
+"To change the timezone, use the dashboard or edit the <filename "
+"os=\"centos;fedora;rhel\">/etc/openstack-"
+"dashboard/local_settings</filename><filename os=\"ubuntu;debian\">/etc"
+"/openstack-dashboard/local_settings.py</filename><filename "
+"os=\"opensuse;sles\">/srv/www/openstack-"
+"dashboard/openstack_dashboard/local/local_settings.py</filename> file."
+msgstr "タイムゾーンを変更する場合、ダッシュボードを使用します。または <filename os=\"centos;fedora;rhel\">/etc/openstack-dashboard/local_settings</filename><filename os=\"ubuntu;debian\">/etc/openstack-dashboard/local_settings.py</filename><filename os=\"opensuse;sles\">/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py</filename> ファイルを編集します。"
+
+#: ./doc/install-guide/section_dashboard-install.xml105(para)
+msgid "Change the following parameter: <code>TIME_ZONE = \"UTC\"</code>"
+msgstr "次のパラメーターを変更します。 <code>TIME_ZONE = \"UTC\"</code>"
+
+#: ./doc/install-guide/section_dashboard-install.xml112(para)
+msgid ""
+"Update the <literal>ALLOWED_HOSTS</literal> in "
+"<filename>local_settings.py</filename> to include the addresses you wish to "
+"access the dashboard from."
+msgstr "Dashboard にアクセスしたいアドレスを含めるために <filename>local_settings.py</filename> の <literal>ALLOWED_HOSTS</literal> を更新します。"
+
+#: ./doc/install-guide/section_dashboard-install.xml116(para)
+msgid ""
+"Edit <filename os=\"centos;fedora;rhel\">/etc/openstack-"
+"dashboard/local_settings</filename><filename os=\"ubuntu;debian\">/etc"
+"/openstack-dashboard/local_settings.py</filename><filename "
+"os=\"opensuse;sles\">/srv/www/openstack-"
+"dashboard/openstack_dashboard/local/local_settings.py</filename>:"
+msgstr "<filename os=\"centos;fedora;rhel\">/etc/openstack-dashboard/local_settings</filename><filename os=\"ubuntu;debian\">/etc/openstack-dashboard/local_settings.py</filename><filename os=\"opensuse;sles\">/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py</filename> を編集します。"
+
+#: ./doc/install-guide/section_dashboard-install.xml127(para)
+msgid ""
+"This guide assumes that you are running the Dashboard on the controller "
+"node. You can easily run the dashboard on a separate server, by changing the"
+" appropriate settings in <filename>local_settings.py</filename>."
+msgstr "このガイドはコントローラーノードで Dashboard を実行していると仮定します。<filename>local_settings.py</filename> の設定を適切に変更することにより、別のサーバーで Dashboard を簡単に実行できます。"
+
+#: ./doc/install-guide/section_dashboard-install.xml132(para)
+msgid ""
+"Edit <filename os=\"centos;fedora;rhel\">/etc/openstack-"
+"dashboard/local_settings</filename><filename os=\"ubuntu;debian\">/etc"
+"/openstack-dashboard/local_settings.py</filename><filename "
+"os=\"opensuse;sles\">/srv/www/openstack-"
+"dashboard/openstack_dashboard/local/local_settings.py</filename> and change "
+"<literal>OPENSTACK_HOST</literal> to the hostname of your Identity Service:"
+msgstr "<filename os=\"centos;fedora;rhel\">/etc/openstack-dashboard/local_settings</filename><filename os=\"ubuntu;debian\">/etc/openstack-dashboard/local_settings.py</filename><filename os=\"opensuse;sles\">/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py</filename> を編集し、<literal>OPENSTACK_HOST</literal> を Identity Service のホスト名に変更します。"
+
+#: ./doc/install-guide/section_dashboard-install.xml144(para)
+msgid "Setup Apache configuration: <placeholder-1/>"
+msgstr "Apache 設定をセットアップします。 <placeholder-1/>"
+
+#: ./doc/install-guide/section_dashboard-install.xml151(para)
+msgid ""
+"By default, the <systemitem>openstack-dashboard</systemitem> package enables"
+" a database as session store. Before you continue, either change the session"
+" store set up as described in <xref linkend=\"dashboard-sessions\"/> or "
+"finish the setup of the database session store as explained in <xref linkend"
+"=\"dashboard-session-database\"/>."
+msgstr "<systemitem>openstack-dashboard</systemitem> パッケージは標準でセッションストアとしてデータベースを有効化します。続行する前に、<xref linkend=\"dashboard-sessions\"/> に記載されているとおりセットアップしたセッションストアを変更します。または、<xref linkend=\"dashboard-session-database\"/> に記載されているとおりデータベースのセッションストアのセットアップを完了します。"
+
+#: ./doc/install-guide/section_dashboard-install.xml161(para)
+msgid ""
+"Ensure that the SELinux policy of the system is configured to allow network "
+"connections to the HTTP server."
+msgstr "システムの SELinux ポリシーが HTTP サーバーにネットワーク接続を許可するよう設定されていることを確認します。"
+
+#: ./doc/install-guide/section_dashboard-install.xml168(para)
+msgid "Start the Apache web server and memcached:"
+msgstr "Apache ウェブサーバーと memcached を起動します。"
+
+#: ./doc/install-guide/section_dashboard-install.xml181(para)
+msgid ""
+"You can now access the dashboard at <uri "
+"os=\"ubuntu\">http://controller/horizon</uri><uri "
+"os=\"debian\">https://controller/</uri><uri "
+"os=\"centos;fedora;rhel\">http://controller/dashboard</uri><uri "
+"os=\"opensuse;sles\">http://controller</uri>."
+msgstr "これで Dashboard に <uri os=\"ubuntu\">http://controller/horizon</uri><uri os=\"debian\">https://controller/</uri><uri os=\"centos;fedora;rhel\">http://controller/dashboard</uri><uri os=\"opensuse;sles\">http://controller</uri> からアクセスできます。"
+
+#: ./doc/install-guide/section_dashboard-install.xml188(para)
+msgid ""
+"Login with credentials for any user that you created with the OpenStack "
+"Identity Service."
+msgstr "OpenStack Identity Service で作成したどれかのユーザーのクレデンシャルでログインします。"
+
+#: ./doc/install-guide/section_basics-networking.xml6(title)
+msgid "Networking"
+msgstr "ネットワーク"
+
+#: ./doc/install-guide/section_basics-networking.xml7(para)
+msgid ""
+"After installing the operating system on each node for the architecture that"
+" you choose to deploy, you must configure the network interfaces. We "
+"recommend that you disable any automated network management tools and "
+"manually edit the appropriate configuration files for your distribution. For"
+" more information on how to configure networking on your distribution, see "
+"the <link os=\"ubuntu\" href=\"https://help.ubuntu.com/lts/serverguide"
+"/network-configuration.html\">documentation.</link><link os=\"debian\" "
+"href=\"https://wiki.debian.org/NetworkConfiguration\">documentation.</link><link"
+" os=\"rhel;centos;fedora\" "
+"href=\"https://access.redhat.com/site/documentation/en-"
+"US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s1-networkscripts-"
+"interfaces.html\">documentation.</link><link os=\"sles;opensuse\" "
+"href=\"https://www.suse.com/documentation/sles11/book_sle_admin/data/sec_basicnet_manconf.html\">SLES"
+" 11</link><phrase os=\"sles;opensuse\"> or </phrase><link "
+"os=\"sles;opensuse\" href=\"http://activedoc.opensuse.org/book/opensuse-"
+"reference/chapter-13-basic-networking\">openSUSE documentation.</link>"
+msgstr "導入するアーキテクチャーに合わせて、各ノードにオペレーティングシステムをインストールした後、ネットワークインターフェースを設定する必要があります。すべての自動ネットワーク管理ツールを無効化し、お使いのディストリビューションに合わせて適切な設定ファイルを手動で編集することを推奨します。お使いのディストリビューションでネットワークを設定する方法に関する詳細は、<link os=\"ubuntu\" href=\"https://help.ubuntu.com/lts/serverguide/network-configuration.html\">ドキュメント</link><link os=\"debian\" href=\"https://wiki.debian.org/NetworkConfiguration\">ドキュメント</link><link os=\"rhel;centos;fedora\" href=\"https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s1-networkscripts-interfaces.html\">ドキュメント</link><link os=\"sles;opensuse\" href=\"https://www.suse.com/documentation/sles11/book_sle_admin/data/sec_basicnet_manconf.html\">SLES 11</link><phrase os=\"sles;opensuse\"> または </phrase><link os=\"sles;opensuse\" href=\"http://activedoc.opensuse.org/book/opensuse-reference/chapter-13-basic-networking\">openSUSE のドキュメント</link>を参照してください。"
+
+#: ./doc/install-guide/section_basics-networking.xml30(title)
+msgid ""
+"To disable <systemitem class=\"service\">NetworkManager</systemitem> and "
+"enable the <systemitem class=\"service\">network</systemitem> service:"
+msgstr "<systemitem class=\"service\">NetworkManager</systemitem> を無効化し、<systemitem class=\"service\">network</systemitem> サービスを有効化する方法:"
+
+#: ./doc/install-guide/section_basics-networking.xml41(title)
+msgid "To disable <systemitem class=\"service\">NetworkManager</systemitem>:"
+msgstr "<systemitem class=\"service\">NetworkManager</systemitem> を無効化する方法:"
+
+#: ./doc/install-guide/section_basics-networking.xml43(para)
+msgid "Use the YaST network module:"
+msgstr "YaST ネットワークモジュールを使用します。"
+
+#: ./doc/install-guide/section_basics-networking.xml45(para)
+msgid ""
+"For more information, see the <link "
+"href=\"https://www.suse.com/documentation/sles11/book_sle_admin/data/sec_nm_activate.html\">SLES"
+" </link> or the <link href=\"http://activedoc.opensuse.org/book/opensuse-"
+"reference/chapter-13-basic-networking#sec.basicnet.yast.netcard.global\"> "
+"openSUSE documentation</link>."
+msgstr "詳細は <link href=\"https://www.suse.com/documentation/sles11/book_sle_admin/data/sec_nm_activate.html\">SLES</link> または <link href=\"http://activedoc.opensuse.org/book/opensuse-reference/chapter-13-basic-networking#sec.basicnet.yast.netcard.global\">openSUSE</link> のドキュメントを参照してください。"
+
+#: ./doc/install-guide/section_basics-networking.xml53(para)
+msgid ""
+"RHEL and derivatives including CentOS and Scientific Linux enable a "
+"restrictive <glossterm>firewall</glossterm> by default. During this "
+"installation, certain steps will fail unless you alter or disable the "
+"firewall. For further information about securing your installation, refer to"
+" the <link href=\"http://docs.openstack.org/sec/\"> OpenStack Security "
+"Guide</link>."
+msgstr "RHEL および、CentOS や Scientific Linux のような派生物は、標準で制限的な<glossterm baseform=\"firewall\">ファイアウォール</glossterm>を有効化しています。このインストール中に、この設定を変更するか、ファイアウォールを無効化しなければ、特定の手順が失敗します。インストール環境をセキュア化することに関する詳細は <link href=\"http://docs.openstack.org/sec/\">OpenStack セキュリティガイド</link> を参照してください。"
+
+#: ./doc/install-guide/section_basics-networking.xml60(para)
+msgid ""
+"On Fedora, <literal>firewalld</literal> replaces <literal>iptables</literal>"
+" as the default firewall system. While you can use "
+"<literal>firewalld</literal> successfully, this guide references "
+"<literal>iptables</literal> for compatibility with other distributions."
+msgstr "Fedora の場合、<literal>firewalld</literal> が標準のファイアウォールシステムとして <literal>iptables</literal> の代わりに使用されています。<literal>firewalld</literal> を正常に使用できている限り、このガイドは他のディストリビューションとの互換性のために <literal>iptables</literal> を参照しています。"
+
+#: ./doc/install-guide/section_basics-networking.xml66(title)
+msgid ""
+"To disable <literal>firewalld</literal> and enable "
+"<literal>iptables</literal>:"
+msgstr "<literal>firewalld</literal> を無効化し、<literal>iptables</literal> を有効化する方法:"
+
+#: ./doc/install-guide/section_basics-networking.xml75(para)
+msgid ""
+"Proceed to network configuration for the example <link linkend=\"basics-"
+"networking-neutron\">OpenStack Networking (neutron) </link> or <link linkend"
+"=\"basics-networking-nova\">legacy networking (nova-network)</link> "
+"architecture."
+msgstr "<link linkend=\"basics-networking-neutron\">OpenStack Networking (neutron) </link> または <link linkend=\"basics-networking-nova\">レガシーネットワーク (nova-network)</link> のアーキテクチャ例のネットワーク設定に進みます。"
+
+#: ./doc/install-guide/section_cinder-verify.xml5(title)
+msgid "Verify the Block Storage installation"
+msgstr "Block Storage のインストールの検証"
+
+#: ./doc/install-guide/section_cinder-verify.xml6(para)
+msgid ""
+"To verify that the Block Storage is installed and configured properly, "
+"create a new volume."
+msgstr "Block Storage が正しくインストールされ、設定されたことを確認するために、新しいボリュームを作成します。"
+
+#: ./doc/install-guide/section_cinder-verify.xml8(para)
+msgid ""
+"For more information about how to manage volumes, see the <link "
+"href=\"http://docs.openstack.org/user-"
+"guide/content/index.html\"><citetitle>OpenStack User "
+"Guide</citetitle></link>."
+msgstr "ボリュームの管理に関する詳細は、<link href=\"http://docs.openstack.org/user-guide/content/index.html\"><citetitle>OpenStack ユーザーガイド</citetitle></link>を参照してください。"
+
+#: ./doc/install-guide/section_cinder-verify.xml13(para)
+msgid "Source the <filename>demo-openrc.sh</filename> file:"
+msgstr "<filename>demo-openrc.sh</filename> ファイルを読み込みます。"
+
+#: ./doc/install-guide/section_cinder-verify.xml18(para)
+msgid "Use the <placeholder-1/> command to create a new volume:"
+msgstr "新しいボリュームを作成するために、<placeholder-1/> コマンドを使用します。"
+
+#: ./doc/install-guide/section_cinder-verify.xml40(para)
+msgid ""
+"Make sure that the volume has been correctly created with the "
+"<placeholder-1/> command:"
+msgstr "ボリュームが正常に作成されたことを、<placeholder-1/> コマンドを用いて確認します。"
+
+#: ./doc/install-guide/section_cinder-verify.xml48(para)
+msgid ""
+"If the status value is not <literal>available</literal>, the volume creation"
+" failed. Check the log files in the <filename>/var/log/cinder/</filename> "
+"directory on the controller and volume nodes to get information about the "
+"failure."
+msgstr "状態が「 <literal>利用可能 (available)</literal>」でなければ、ボリュームの作成が失敗しています。失敗に関する情報を取得するために、コントローラーノードとボリュームノードの <filename>/var/log/cinder/</filename> にあるログファイルを確認してください。"
+
+#: ./doc/install-guide/section_cinder-node.xml6(title)
+msgid "Configure a Block Storage service node"
+msgstr "Block Storage Service ノードの設定"
+
+#: ./doc/install-guide/section_cinder-node.xml7(para)
+msgid ""
+"After you configure the services on the controller node, configure a second "
+"system to be a Block Storage service node. This node contains the disk that "
+"serves volumes."
+msgstr "コントローラーノードでサービスを設定した後、Block Storage Service のノードとなる 2 番目のシステムを設定します。このノードはボリュームを取り扱うディスクを有します。"
+
+#: ./doc/install-guide/section_cinder-node.xml14(para)
+msgid ""
+"Use the instructions in <xref linkend=\"ch_basics\"/> to configure the "
+"system. Note the following differences from the installation instructions "
+"for the controller node:"
+msgstr "システムを設定するために <xref linkend=\"ch_basics\"/> にある方法を使用します。以下の項目はコントローラーノードのインストール説明と異なることに注意してください。"
+
+#: ./doc/install-guide/section_cinder-node.xml19(para)
+msgid ""
+"Set the host name to <literal>block1</literal> and use "
+"<literal>10.0.0.41</literal> as IP address on the management network "
+"interface. Ensure that the IP addresses and host names for both controller "
+"node and Block Storage service node are listed in the "
+"<filename>/etc/hosts</filename> file on each system."
+msgstr "ホスト名を <literal>block1</literal> に設定し、管理ネットワークのインターフェースの IP アドレスとして <literal>10.0.0.41</literal> を使用します。コントローラーノードと Block Storage サービスノードの IP アドレスとホスト名が各システムの <filename>/etc/hosts</filename> にあることを確認します。"
+
+#: ./doc/install-guide/section_cinder-node.xml27(para)
+msgid ""
+"Follow the instructions in <xref linkend=\"basics-ntp\"/> to synchronize "
+"from the controller node."
+msgstr "コントローラーノードから同期するために、<xref linkend=\"basics-ntp\"/> にある説明に従います。"
+
+#: ./doc/install-guide/section_cinder-node.xml33(para)
+msgid "Install the required LVM packages, if they are not already installed:"
+msgstr "必要となる LVM パッケージがまだインストールされていなければ、それらをインストールします。"
+
+#: ./doc/install-guide/section_cinder-node.xml38(para)
+msgid ""
+"Create the LVM physical and logical volumes. This guide assumes a second "
+"disk <literal>/dev/sdb</literal> that is used for this purpose:"
+msgstr "LVM の物理ボリュームと論理ボリュームを作成します。このガイドはこの目的のために使用される 2 番目のディスク <literal>/dev/sdb</literal> を仮定します。"
+
+#: ./doc/install-guide/section_cinder-node.xml45(para)
+msgid ""
+"Add a filter entry to the <literal>devices</literal> section in the "
+"<filename>/etc/lvm/lvm.conf</filename> file to keep LVM from scanning "
+"devices used by virtual machines:"
+msgstr "仮想マシンにより使用されるデバイスをスキャンすることから LVM を保護するために、<filename>/etc/lvm/lvm.conf</filename> ファイルの <literal>devices</literal> セクションにフィルター項目を追加します。"
+
+#: ./doc/install-guide/section_cinder-node.xml55(para)
+msgid ""
+"You must add required physical volumes for LVM on the Block Storage host. "
+"Run the <placeholder-1/> command to get a list or required volumes."
+msgstr "Block Storage のホストに LVM 用に必要となる物理ボリュームを追加する必要があります。必要となるボリュームの一覧を取得するために <placeholder-1/> コマンドを実行します。"
+
+#: ./doc/install-guide/section_cinder-node.xml59(para)
+msgid ""
+"Each item in the filter array starts with either an <literal>a</literal> for"
+" accept, or an <literal>r</literal> for reject. The physical volumes that "
+"are required on the Block Storage host have names that begin with "
+"<literal>a</literal>. The array must end with \"<literal>r/.*/</literal>\" "
+"to reject any device not listed."
+msgstr "フィルター配列にある各項目は、許可するために <literal>a</literal> から、拒否するために <literal>r</literal> から始まります。Block Storage のホストで必要となる物理ボリュームは <literal>a</literal> から始まる名前を持つ必要があります。配列は一覧に無いすべてのデバイスを拒否するために \"<literal>r/.*/</literal>\" で終わる必要があります。"
+
+#: ./doc/install-guide/section_cinder-node.xml66(para)
+msgid ""
+"In this example, <literal>/dev/sda1</literal> is the volume where the "
+"volumes for the operating system for the node reside, while "
+"<literal>/dev/sdb</literal> is the volume reserved for <literal>cinder-"
+"volumes</literal>."
+msgstr "この例では、<literal>/dev/sda1</literal> がノードのオペレーティングシステム用のボリュームが置かれるボリュームです。<literal>/dev/sdb</literal> は <literal>cinder-volumes</literal> のために予約されたボリュームです。"
+
+#: ./doc/install-guide/section_cinder-node.xml72(para)
+msgid ""
+"After you configure the operating system, install the appropriate packages "
+"for the Block Storage service:"
+msgstr "オペレーティングシステムの設定後、Block Storage Service 向けに適切なパッケージをインストールします。"
+
+#: ./doc/install-guide/section_cinder-node.xml79(para)
+msgid ""
+"Respond to the <systemitem class=\"library\">debconf</systemitem> prompts "
+"about the <link linkend=\"debconf-dbconfig-common\">database "
+"management</link>, <link linkend=\"debconf-"
+"keystone_authtoken\"><literal>[keystone_authtoken]</literal> "
+"settings</link>, and <link linkend=\"debconf-rabbitqm\">RabbitMQ "
+"credentials</link>. Make sure to enter the same details as you did for your "
+"Block Storage service controller node."
+msgstr "<link linkend=\"debconf-dbconfig-common\">データベース管理</link>、<link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> 設定</link>、<link linkend=\"debconf-rabbitqm\">RabbitMQ クレデンシャル</link>に関する <systemitem class=\"library\">debconf</systemitem> プロンプトに答えます。必ず Block Storage のコントローラーノードと同じように入力します。"
+
+#: ./doc/install-guide/section_cinder-node.xml87(para)
+msgid ""
+"Another screen prompts you for the <systemitem class=\"library\">volume-"
+"group</systemitem> to use. The Debian package configuration script detects "
+"every active volume group and tries to use the first one it sees, provided "
+"that the <systemitem class=\"library\">lvm2</systemitem> package was "
+"installed before Block Storage. This should be the case if you configured "
+"the volume group first, as this guide recommends."
+msgstr "使用する <systemitem class=\"library\">volume-group</systemitem> を選択するプロンプトが別の画面に表示されます。Debian パッケージの設定スクリプトは、すべての動作中のボリュームグループを検知し、最初に認識したものを使用しようとします。<systemitem class=\"library\">lvm2</systemitem> パッケージが Block Storage の前にインストールされます。このガイドが推奨しているとおり、ボリュームグループを最初に設定する場合、このようになります。"
+
+#: ./doc/install-guide/section_cinder-node.xml94(para)
+msgid ""
+"If you have only one active volume group on your Block Storage service node,"
+" you do not need to manually enter its name when you install the <systemitem"
+" class=\"service\">cinder-volume</systemitem> package because it is detected"
+" automatically. If no <systemitem class=\"library\">volume-"
+"group</systemitem> is available when you install <systemitem class=\"service"
+"\">cinder-common</systemitem>, you must use <placeholder-1/> to manually "
+"configure or re-configure <systemitem class=\"service\">cinder-"
+"common</systemitem>."
+msgstr "Block Storage のノードに動作中のボリュームグループが 1 つしかなければ、自動的に検出されるため、<systemitem class=\"service\">cinder-volume</systemitem> パッケージのインストール時にその名前を入力する必要がありません。<systemitem class=\"service\">cinder-common</systemitem> のインストール時に、<systemitem class=\"library\">volume-group</systemitem> が利用できなければ、手動で設定するか、<systemitem class=\"service\">cinder-common</systemitem> を再設定するために、<placeholder-1/> を使用する必要があります。"
+
+#: ./doc/install-guide/section_cinder-node.xml106(para)
+msgid ""
+"Copy the <filename>/etc/cinder/cinder.conf</filename> configuration file "
+"from the controller, or perform the following steps to set the keystone "
+"credentials:"
+msgstr "<filename>/etc/cinder/cinder.conf</filename> 設定ファイルをコントローラーからコピーします。または、keystone のクレデンシャルを設定するために、以下の手順を実行します。"
+
+#: ./doc/install-guide/section_cinder-node.xml142(para)
+msgid ""
+"In the <literal>[DEFAULT]</literal> configuration section of the "
+"<filename>/etc/cinder/cinder.conf</filename> file, set these configuration "
+"keys and replace <replaceable>RABBIT_PASS</replaceable> with the password "
+"you chose for RabbitMQ:"
+msgstr "<filename>/etc/cinder/cinder.conf</filename> ファイルの <literal>[DEFAULT]</literal> 設定セクションで、これらの設定キーを設定し、<replaceable>RABBIT_PASS</replaceable> を RabbitMQ 用に選択したパスワードに置き換えます。"
+
+#: ./doc/install-guide/section_cinder-node.xml164(para)
+msgid ""
+"Configure Block Storage to use the RabbitMQ message broker. Replace "
+"<replaceable>RABBIT_PASS</replaceable> with the password you chose for "
+"RabbitMQ:"
+msgstr "RabbitMQ メッセージブローカーを使用するよう Block Storage を設定します。<replaceable>RABBIT_PASS</replaceable> を RabbitMQ 用に選んだパスワードで置き換えます。"
+
+#: ./doc/install-guide/section_cinder-node.xml177(para)
+msgid ""
+"Configure Block Storage to use your MySQL database. Edit the "
+"<filename>/etc/cinder/cinder.conf</filename> file and add the following key "
+"to the <literal>[database]</literal> section. Replace "
+"<replaceable>CINDER_DBPASS</replaceable> with the password you chose for the"
+" Block Storage database:"
+msgstr "Block Storage が MySQL データベースを使用するよう設定します。<filename>/etc/cinder/cinder.conf</filename> ファイルを編集し、以下のキーを <literal>[database]</literal> セクションに追加します。Block Storage データベース用に選択したパスワードで <replaceable>CINDER_DBPASS</replaceable> を置き換えます。"
+
+#: ./doc/install-guide/section_cinder-node.xml196(para)
+msgid ""
+"Configure Block Storage to use the Image Service. Block Storage needs access"
+" to images to create bootable volumes. Edit the "
+"<filename>/etc/cinder/cinder.conf</filename> file and update the "
+"<option>glance_host</option> option in the <literal>[DEFAULT]</literal> "
+"section:"
+msgstr "Image Service を使用するよう Block Storage を設定します。Block Storage は、ブート可能なボリュームを作成するために、イメージにアクセスする必要があります。<filename>/etc/cinder/cinder.conf</filename> ファイルを編集し、<literal>[DEFAULT]</literal> セクションの <option>glance_host</option> オプションを更新します。"
+
+#: ./doc/install-guide/section_cinder-node.xml214(para)
+msgid ""
+"Configure the iSCSI target service to discover Block Storage volumes. Add "
+"the following line to the beginning of the "
+"<filename>/etc/tgt/targets.conf</filename> file, if it is not already "
+"present:"
+msgstr "Block Storage ボリュームを探索するよう iSCSI ターゲットサービスを設定します。まだ存在しなければ、以下の行を <filename>/etc/tgt/targets.conf</filename> の最初に追加します。"
 
 #: ./doc/install-guide/section_ceilometer-verify.xml5(title)
 msgid "Verify the Telemetry installation"
@@ -2086,6 +4721,569 @@ msgstr "このダウンロードが Telemetry により検知され、保存さ
 msgid "You can now get usage statistics for the various meters:"
 msgstr "さまざまなメーターの使用量の統計情報を取得できるようになりました。"
 
+#: ./doc/install-guide/ch_ceilometer.xml6(title)
+msgid "Add the Telemetry module"
+msgstr "Telemetry モジュールの追加"
+
+#: ./doc/install-guide/ch_ceilometer.xml7(para)
+msgid ""
+"Telemetry provides a framework for monitoring and metering the OpenStack "
+"cloud. It is also known as the ceilometer project."
+msgstr "Telemetry は OpenStack クラウドのモニタリングとメータリングのフレームワークを提供します。これは Ceilometer プロジェクトとしても知られています。"
+
+#: ./doc/install-guide/ch_ceilometer.xml19(para)
+msgid ""
+"Your OpenStack environment now includes Telemetry. You can <link linkend"
+"=\"launch-instance\">launch an instance</link> or add more services to your "
+"environment in the previous chapters."
+msgstr "OpenStack 環境に Telemetryが追加されました。<link linkend=\"launch-instance\">インスタンスの起動</link>、以前の章に記載されているサービスの環境への追加を実行できます。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml9(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml9(para)
+msgid ""
+"Before you configure OpenStack Networking, you must enable certain kernel "
+"networking functions."
+msgstr "OpenStack Networking を設定する前に、特定のカーネルネットワーク機能を有効化する必要があります。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml12(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml12(para)
+msgid "Edit <filename>/etc/sysctl.conf</filename> to contain the following:"
+msgstr "<filename>/etc/sysctl.conf</filename> を編集し、以下の内容を含めます。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml18(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml19(para)
+msgid "Implement the changes:"
+msgstr "変更を実装します。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml23(title)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml57(title)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml24(title)
+msgid "To install the Networking components"
+msgstr "Networking コンポーネントのインストール方法"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml30(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml33(para)
+msgid ""
+"Ubuntu installations using Linux kernel version 3.11 or newer do not require"
+" the <emphasis>openvswitch-datapath-dkms</emphasis> package."
+msgstr "Linux カーネル 3.11 以降の Ubuntu インストール環境は、<emphasis>openvswitch-datapath-dkms</emphasis> パッケージを必要としません。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml35(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml64(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml38(para)
+msgid "SUSE does not use a separate ML2 plug-in package."
+msgstr "SUSE は ML2 プラグイン固有のパッケージを使用しません。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml40(title)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml43(title)
+msgid "To configure the Networking common components"
+msgstr "Networking 共通コンポーネントの設定方法"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml41(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml44(para)
+msgid ""
+"The Networking common component configuration includes the authentication "
+"mechanism, message broker, and plug-in."
+msgstr "Networking 共通コンポーネントの設定には、認証機構、メッセージブローカー、プラグインがあります。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml44(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml77(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml47(para)
+msgid ""
+"Respond to prompts for <link linkend=\"debconf-dbconfig-common\">database "
+"management</link>, <link linkend=\"debconf-keystone_authtoken\">Identity "
+"service credentials</link>, <link linkend=\"debconf-api-endpoints\">service "
+"endpoint registration</link>, and <link linkend=\"debconf-rabbitqm\">message"
+" broker credentials</link>."
+msgstr "<link linkend=\"debconf-dbconfig-common\">データベース管理</link>、<link linkend=\"debconf-keystone_authtoken\">Identity のクレデンシャル</link>、<link linkend=\"debconf-api-endpoints\">サービスエンドポイント登録</link>、<link linkend=\"debconf-rabbitqm\">メッセージブローカーのクレデンシャル</link>に関するプロンプトに答えます。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml54(para)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml77(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml131(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml154(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml57(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml80(para)
+msgid "Configure Networking to use the Identity service for authentication:"
+msgstr "Networking が認証用に Identity Service を使用するよう設定します。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml56(para)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml89(para)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml288(para)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml322(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml133(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml166(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml370(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml404(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml59(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml92(para)
+msgid ""
+"Replace <replaceable>NEUTRON_PASS</replaceable> with the password you chose "
+"for the <literal>neutron</literal> user in the Identity service."
+msgstr "Identity で <literal>neutron</literal> ユーザー用に選択したパスワードで <replaceable>NEUTRON_PASS</replaceable> を置き換えます。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml81(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml158(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml84(para)
+msgid ""
+"Edit the <filename>/etc/neutron/neutron.conf</filename> file and add the "
+"following key to the <literal>[DEFAULT]</literal> section:"
+msgstr "<filename>/etc/neutron/neutron.conf</filename> ファイルを編集し、以下のキーを <literal>[DEFAULT]</literal> セクションに追加します。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml87(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml164(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml90(para)
+msgid ""
+"Add the following keys to the <literal>[keystone_authtoken]</literal> "
+"section:"
+msgstr "以下のキーを <literal>[keystone_authtoken]</literal> セクションに追加します。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml105(para)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml119(para)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml126(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml182(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml196(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml203(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml108(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml122(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml129(para)
+msgid "Configure Networking to use the message broker:"
+msgstr "Networking がメッセージブローカーを使用するよう設定します。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml129(para)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml162(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml206(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml248(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml296(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml132(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml165(para)
+msgid ""
+"Edit the <filename>/etc/neutron/neutron.conf</filename> file and add the "
+"following keys to the <literal>[DEFAULT]</literal> section:"
+msgstr "<filename>/etc/neutron/neutron.conf</filename> ファイルを編集し、以下のキーを <literal>[DEFAULT]</literal> セクションに追加します。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml144(para)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml158(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml278(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml292(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml147(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml161(para)
+msgid ""
+"Configure Networking to use the Modular Layer 2 (ML2) plug-in and associated"
+" services:"
+msgstr "Modular Layer 2 (ML2) プラグインと関連サービスを使用するよう Networking を設定します。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml151(para)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml171(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml285(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml305(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml154(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml174(para)
+msgid ""
+"We recommend adding <literal>verbose = True</literal> to the "
+"<literal>[DEFAULT]</literal> section in "
+"<filename>/etc/neutron/neutron.conf</filename> to assist with "
+"troubleshooting."
+msgstr "トラブルシューティングに役立てるため、<filename>/etc/neutron/neutron.conf</filename> の <literal>[DEFAULT]</literal> セクションに <literal>verbose = True</literal> を追加することを推奨します。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml180(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml314(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml183(para)
+msgid ""
+"Comment out any lines in the <literal>[service_providers]</literal> section."
+msgstr "<literal>[service_providers]</literal> セクションのすべての行をコメントアウトします。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml185(title)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml319(title)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml351(title)
+msgid "To configure the Modular Layer 2 (ML2) plug-in"
+msgstr "ML2 プラグインの設定方法"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml186(para)
+msgid ""
+"The ML2 plug-in uses the Open vSwitch (OVS) mechanism (agent) to build the "
+"virtual networking framework for instances."
+msgstr "ML2 プラグインは、インスタンスの仮想ネットワークフレームワークを構築するために、Open vSwitch 機能 (エージェント) を使用します。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml190(para)
+msgid ""
+"Replace <replaceable>INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS</replaceable> "
+"with the IP address of the instance tunnels network interface on your "
+"compute node. This guide uses <literal>10.0.1.31</literal> for the IP "
+"address of the instance tunnels network interface on the first compute node."
+msgstr "コンピュートノードのインスタンストンネルネットワークインターフェースの IP アドレスで <replaceable>INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS</replaceable> を置き換えます。このガイドは、最初のコンピュートノードのインスタンストンネルネットワークインターフェースの IP アドレスに <literal>10.0.1.31</literal> を使用します。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml206(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml240(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml372(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml406(replaceable)
+msgid "INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS"
+msgstr "INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml217(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml340(para)
+msgid ""
+"Edit the <filename>/etc/neutron/plugins/ml2/ml2_conf.ini</filename> file:"
+msgstr "<filename>/etc/neutron/plugins/ml2/ml2_conf.ini</filename> ファイルを編集します。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml220(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml343(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml386(para)
+msgid "Add the following keys to the <literal>[ml2]</literal> section:"
+msgstr "以下のキーを <literal>[ml2]</literal> セクションに追加します。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml227(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml393(para)
+msgid ""
+"Add the following keys to the <literal>[ml2_type_gre]</literal> section:"
+msgstr "以下のキーを <literal>[ml2_type_gre]</literal> セクションに追加します。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml232(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml398(para)
+msgid "Add the <literal>[ovs]</literal> section and the following keys to it:"
+msgstr "<literal>[ovs]</literal> セクションを追加し、そこに以下のキーを追加します。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml234(para)
+msgid ""
+"Replace <replaceable>INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS</replaceable> "
+"with the IP address of the instance tunnels network interface on your "
+"compute node."
+msgstr "コンピュートノードのインスタンストンネルネットワークインターフェースの IP アドレスで <replaceable>INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS</replaceable> を置き換えます。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml243(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml355(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml409(para)
+msgid ""
+"Add the <literal>[securitygroup]</literal> section and the following keys to"
+" it:"
+msgstr "<literal>[securitygroup]</literal> セクションを追加し、そこに以下のキーを追加します。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml252(title)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml418(title)
+msgid "To configure the Open vSwitch (OVS) service"
+msgstr "Open vSwitch (OVS) サービスの設定方法"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml253(para)
+msgid ""
+"The OVS service provides the underlying virtual networking framework for "
+"instances. The integration bridge <literal>br-int</literal> handles internal"
+" instance network traffic within OVS."
+msgstr "OVS サービスは、バックエンドの仮想ネットワークフレームワークをインスタンスに提供します。統合ブリッジ <literal>br-int</literal> が OVS 内の内部インスタンスネットワーク通信を処理します。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml257(para)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml263(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml428(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml434(para)
+msgid "Start the OVS service and configure it to start when the system boots:"
+msgstr "OVS サービスを起動し、システム起動時に起動するよう設定します。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml269(para)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml273(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml440(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml444(para)
+msgid "Restart the OVS service:"
+msgstr "OVS サービスを再起動します。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml277(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml448(para)
+msgid "Add the integration bridge:"
+msgstr "統合ブリッジを追加します。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml282(title)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml364(title)
+msgid "To configure Compute to use Networking"
+msgstr "Networking を使用するための Compute の設定方法"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml283(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml365(para)
+msgid ""
+"By default, most distributions configure Compute to use legacy networking. "
+"You must reconfigure Compute to manage networks through Networking."
+msgstr "多くのディストリビューションは標準で、レガシーネットワークを使用するよう Compute を設定します。Networking からネットワークを管理するよう、Compute を再設定する必要があります。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml312(para)
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml338(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml394(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml420(para)
+msgid ""
+"By default, Compute uses an internal firewall service. Since Networking "
+"includes a firewall service, you must disable the Compute firewall service "
+"by using the <literal>nova.virt.firewall.NoopFirewallDriver</literal> "
+"firewall driver."
+msgstr "デフォルトで、Compute は内部ファイアウォールサービスを使用します。Networking がファイアウォールサービスを含むため、<literal>nova.virt.firewall.NoopFirewallDriver</literal> ファイアウォールドライバーを使用して、Compute のファイアウォールサービスを無効化する必要があります。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml320(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml402(para)
+msgid ""
+"Edit the <filename>/etc/nova/nova.conf</filename> and add the following keys"
+" to the <literal>[DEFAULT]</literal> section:"
+msgstr "<filename>/etc/nova/nova.conf</filename> ファイルを編集し、以下のキーを <literal>[DEFAULT]</literal> セクションに追加します。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml347(title)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml474(title)
+msgid "To finalize the installation"
+msgstr "インストールの最終手順"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml349(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml476(para)
+msgid ""
+"The Networking service initialization scripts expect a symbolic link "
+"<filename>/etc/neutron/plugin.ini</filename> pointing to the configuration "
+"file associated with your chosen plug-in. Using the ML2 plug-in, for "
+"example, the symbolic link must point to "
+"<filename>/etc/neutron/plugins/ml2/ml2_conf.ini</filename>. If this symbolic"
+" link does not exist, create it using the following commands:"
+msgstr "Networking のサービス初期化スクリプトは、選択したプラグインと関連する設定ファイルを指し示すシンボリックリンク <filename>/etc/neutron/plugin.ini</filename> を予期しています。例えば、ML2 プラグインを使用する場合、シンボリックリンクが <filename>/etc/neutron/plugins/ml2/ml2_conf.ini</filename> を指し示す必要があります。このシンボリックリンクが存在しなければ、以下のコマンドを使用して作成します。"
+
+#. https://bugzilla.redhat.com/show_bug.cgi?id=1087647
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml358(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml485(para)
+msgid ""
+"Due to a packaging bug, the Open vSwitch agent initialization script "
+"explicitly looks for the Open vSwitch plug-in configuration file rather than"
+" a symbolic link <filename>/etc/neutron/plugin.ini</filename> pointing to "
+"the ML2 plug-in configuration file. Run the following commands to resolve "
+"this issue:"
+msgstr "パッケージ化のバグのため、Open vSwitch エージェントの初期化スクリプトは、ML2 プラグイン設定ファイルを指し示すシンボリックリンク <filename>/etc/neutron/plugin.ini</filename> ではなく、Open vSwitch プラグイン設定ファイルを明示的に検索します。この問題を解決するために、以下のコマンドを実行します。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml368(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml495(para)
+msgid ""
+"The Networking service initialization scripts expect the variable "
+"<literal>NEUTRON_PLUGIN_CONF</literal> in the "
+"<filename>/etc/sysconfig/neutron</filename> file to reference the "
+"configuration file associated with your chosen plug-in. Using ML2, for "
+"example, edit the <filename>/etc/sysconfig/neutron</filename> file and add "
+"the following:"
+msgstr "Networking のサービス初期化スクリプトは、<filename>/etc/sysconfig/neutron</filename> ファイルの <literal>NEUTRON_PLUGIN_CONF</literal> 変数が、使用するプラグインに関連する設定ファイルを参照していることを想定します。例えば、ML2 を使用する場合、<filename>/etc/sysconfig/neutron</filename> ファイルを編集し、以下を追加します。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml383(para)
+msgid ""
+"Start the Open vSwitch (OVS) agent and configure it to start when the system"
+" boots:"
+msgstr "Open vSwitch エージェントを起動し、システム起動時に起動するよう設定します。"
+
+#: ./doc/install-guide/section_neutron-ml2-compute-node.xml391(para)
+msgid "Restart the Open vSwitch (OVS) agent:"
+msgstr "Open vSwitch (OVS) エージェントを再起動します。"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_basics-networking-nova.xml25(None)
+#: ./doc/install-guide/ch_overview.xml147(None)
+msgid ""
+"@@image: 'figures/installguide_arch-nova.png'; "
+"md5=da24b356516c960a33ab2b4b72840774"
+msgstr "@@image: 'figures/installguide_arch-nova.png'; md5=da24b356516c960a33ab2b4b72840774"
+
+#: ./doc/install-guide/section_basics-networking-nova.xml6(title)
+#: ./doc/install-guide/ch_networking.xml31(title)
+msgid "Legacy networking (nova-network)"
+msgstr "レガシーネットワーク (nova-network)"
+
+#: ./doc/install-guide/section_basics-networking-nova.xml7(para)
+msgid ""
+"The example architecture with legacy networking (nova-network) requires a "
+"controller node and at least one compute node. The controller node contains "
+"one network interface on the <glossterm>management network</glossterm>. The "
+"compute node contains one network interface on the management network and "
+"one on the <glossterm>external network</glossterm>."
+msgstr "このレガシーネットワーク (nova-network) を持つアーキテクチャ例は、コントローラーと最低 1 つのコンピュートノードを必要とします。コントローラーノードは、<glossterm baseform=\"management network\">管理ネットワーク</glossterm>に 1 つのネットワークインターフェースを持ちます。コンピュートノードは、管理ネットワークに 1 つのネットワークインターフェースを、<glossterm baseform=\"external network\">外部ネットワーク</glossterm>に 1 つを持ちます。"
+
+#: ./doc/install-guide/section_basics-networking-nova.xml14(para)
+msgid ""
+"Network interface names vary by distribution. Traditionally, interfaces use "
+"\"eth\" followed by a sequential number. To cover all variations, this guide"
+" simply refers to the first interface as the interface with the lowest "
+"number and the second interface as the interface with the highest number."
+msgstr "ネットワークインターフェースの名前はディストリビューションにより異なります。伝統的に、インターフェースは、「eth」から始まり、数字が後ろにつきます。すべての種類を取り扱うために、このガイドは単に、最小の番号を持つインターフェースとして 1 番目のインターフェースを参照します。最大の番号を持つインターフェースとして 2 番目のインターフェースを参照します。"
+
+#: ./doc/install-guide/section_basics-networking-nova.xml21(title)
+#: ./doc/install-guide/ch_overview.xml143(title)
+msgid "Two-node architecture with legacy networking (nova-network)"
+msgstr "レガシーネットワーク (nova-network) を持つ 2 ノードアーキテクチャー"
+
+#: ./doc/install-guide/section_basics-networking-nova.xml88(para)
+msgid ""
+"The external interface uses a special configuration without an IP address "
+"assigned to it. Configure the second interface as the external interface:"
+msgstr "外部インターフェースは、IP アドレスを割り当てない特別な設定を使用します。外部インターフェースとして 2 番目のインターフェースを設定します。"
+
+#: ./doc/install-guide/section_basics-networking-nova.xml91(para)
+msgid ""
+"Replace <replaceable>INTERFACE_NAME</replaceable> with the actual interface "
+"name. For example, <emphasis>eth1</emphasis> or <emphasis>ens224</emphasis>."
+msgstr "<replaceable>INTERFACE_NAME</replaceable> を実際のインターフェース名で置き換えます。例えば、<emphasis>eth1</emphasis> や <emphasis>ens224</emphasis> です。"
+
+#: ./doc/install-guide/section_nova-compute.xml5(title)
+msgid "Configure a compute node"
+msgstr "コンピュートノードの設定"
+
+#: ./doc/install-guide/section_nova-compute.xml6(para)
+msgid ""
+"After you configure the Compute service on the controller node, you must "
+"configure another system as a compute node. The compute node receives "
+"requests from the controller node and hosts virtual machine instances. You "
+"can run all services on a single node, but the examples in this guide use "
+"separate systems. This makes it easy to scale horizontally by adding "
+"additional Compute nodes following the instructions in this section."
+msgstr "コントローラーノードで Compute サービスを設定した後、他のシステムをコンピュートノードとして設定する必要があります。コンピュートノードはコントローラーノードからリクエストを受け取り、仮想マシンインスタンスをホストします。単一ノードですべてのサービスを実行することもできます。しかし、このガイドの例では分離したシステムを使用します。これにより、このセクションにある説明に従って、追加のコンピュートノードを追加して、水平的にスケールさせることが容易になります。"
+
+#: ./doc/install-guide/section_nova-compute.xml13(para)
+msgid ""
+"The Compute service relies on a hypervisor to run virtual machine instances."
+" OpenStack can use various hypervisors, but this guide uses KVM."
+msgstr "Compute サービスは仮想マシンインスタンスを実行するためにハイパーバイザーに依存します。OpenStack はさまざまなハイパーバイザーを使用できますが、このガイドは KVM を使用します。"
+
+#: ./doc/install-guide/section_nova-compute.xml18(para)
+msgid "Install the Compute packages:"
+msgstr "Compute のパッケージをインストールします。"
+
+#: ./doc/install-guide/section_nova-compute.xml20(para)
+msgid ""
+"When prompted to create a <literal>supermin</literal> appliance, respond "
+"<placeholder-1/>."
+msgstr "<literal>supermin</literal> アプライアンスを作成するためのプロンプトが表示されたとき、<placeholder-1/> を答えます。"
+
+#: ./doc/install-guide/section_nova-compute.xml25(para)
+msgid ""
+"To use the meta-packages and install other components on your compute node, "
+"such as OpenStack Networking and Telemetry agents, run this command:"
+msgstr "メタパッケージを使用して、OpenStack Networking や Ceilometer のエージェントのような他のコンポーネントをコンピュートノードにインストールするために、このコマンドを実行します。"
+
+#: ./doc/install-guide/section_nova-compute.xml29(para)
+msgid ""
+"The controller node has the <package>openstack-proxy-node</package> and "
+"<package>openstack-toaster</package> meta-packages that install <package"
+">openstack-proxy-node</package> and <package>openstack-toaster</package> at "
+"the same time."
+msgstr "コントローラーノードは同時に、<package>openstack-proxy-node</package> と <package>openstack-toaster</package> をインストールする、<package>openstack-proxy-node</package> メタパッケージと <package>openstack-toaster</package> メタパッケージを持ちます。"
+
+#: ./doc/install-guide/section_nova-compute.xml41(para)
+msgid ""
+"Respond to the prompts for <link linkend=\"debconf-dbconfig-"
+"common\">database management</link>, <link linkend=\"debconf-"
+"keystone_authtoken\"><literal>[keystone_authtoken]</literal> "
+"settings</link>, <link linkend=\"debconf-rabbitqm\">RabbitMQ "
+"credentials</link>, and <link linkend=\"debconf-api-endpoints\">API "
+"endpoint</link> registration."
+msgstr "<link linkend=\"debconf-dbconfig-common\">データベース管理</link>、<link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> 設定</link>、<link linkend=\"debconf-rabbitqm\">RabbitMQ クレデンシャル</link>、<link linkend=\"debconf-api-endpoints\">API エンドポイント</link>登録に関するプロンプトに答えます。キャッシュタイプを選択する必要もあります。"
+
+#: ./doc/install-guide/section_nova-compute.xml50(para)
+msgid ""
+"For security reasons, the Linux kernel is not readable by normal users which"
+" restricts hypervisor services such as qemu and libguestfs. For details, see"
+" <link "
+"href=\"https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725\">this "
+"bug</link>. To make the current kernel readable, run: <placeholder-1/> To "
+"also enable this override for all future kernel updates, create the file "
+"<filename>/etc/kernel/postinst.d/statoverride</filename> "
+"containing:<placeholder-2/> Remember to make the file executable: "
+"<placeholder-3/>"
+msgstr "セキュリティの理由から、Linux カーネルは通常のユーザーにより読み取りできません。これにより QEMU や libguestfs のようなハイパーバイザーサービスを制限します。詳細は<link href=\"https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725\">このバグ</link>を参照してください。現在のカーネルを読み取り可能にするために、<placeholder-1/> を実行します。今後のすべてのカーネル更新でこの上書きを有効にするために、以下を含めた <filename>/etc/kernel/postinst.d/statoverride</filename> ファイルを作成します。<placeholder-2/> 忘れずに、ファイルを実行可能にします。<placeholder-3/>"
+
+#: ./doc/install-guide/section_nova-compute.xml69(para)
+msgid "Edit the <filename>/etc/nova/nova.conf</filename> configuration file:"
+msgstr "<filename>/etc/nova/nova.conf</filename> 設定ファイルを編集します。"
+
+#: ./doc/install-guide/section_nova-compute.xml81(para)
+msgid ""
+"Edit the <filename>/etc/nova/nova.conf</filename> configuration file and add"
+" these lines to the appropriate sections:"
+msgstr "<filename>/etc/nova/nova.conf</filename> 設定ファイルを編集し、これらの行を適切なセクションに追加します。"
+
+#: ./doc/install-guide/section_nova-compute.xml102(para)
+msgid ""
+"Configure the Compute service to use the Qpid message broker by setting "
+"these configuration keys:"
+msgstr "これらの設定キーを設定することにより、Compute サービスが Qpid メッセージブローカーを使用するよう設定します。"
+
+#: ./doc/install-guide/section_nova-compute.xml116(para)
+msgid ""
+"Configure the Compute service to use the RabbitMQ message broker by setting "
+"these configuration keys:"
+msgstr "これらの設定キーを設定することにより、Compute サービスが RabbitMQ メッセージブローカーを使用するよう設定します。"
+
+#: ./doc/install-guide/section_nova-compute.xml125(para)
+msgid "Configure Compute to provide remote console access to instances."
+msgstr "インスタンスへのリモートコンソールアクセスを提供するよう Compute を設定します。"
+
+#: ./doc/install-guide/section_nova-compute.xml132(para)
+msgid ""
+"Edit <filename>/etc/nova/nova.conf</filename> and add the following keys "
+"under the <literal>[DEFAULT]</literal> section:"
+msgstr "<filename>/etc/nova/nova.conf</filename> を編集し、以下のキーを <literal>[DEFAULT]</literal> セクションに追加します。"
+
+#: ./doc/install-guide/section_nova-compute.xml146(para)
+msgid ""
+"Specify the host that runs the Image Service.<phrase os=\"ubuntu;debian\"> "
+"Edit <filename>/etc/nova/nova.conf</filename> file and add these lines to "
+"the <literal>[DEFAULT]</literal> section:</phrase>"
+msgstr "Image Service を実行するホストを指定します。<phrase os=\"ubuntu;debian\"><filename>/etc/nova/nova.conf</filename> ファイルを編集し、これらの行を <literal>[DEFAULT]</literal> セクションに追加します。</phrase>"
+
+#: ./doc/install-guide/section_nova-compute.xml157(para)
+msgid ""
+"You must determine whether your system's processor and/or hypervisor support"
+" hardware acceleration for virtual machines."
+msgstr "お使いのシステムのプロセッサーとハイパーバイザーが仮想マシンのハードウェア支援機能をサポートするかどうか確認する必要があります。"
+
+#: ./doc/install-guide/section_nova-compute.xml159(para)
+#: ./doc/install-guide/section_nova-compute.xml178(para)
+#: ./doc/install-guide/section_basics-queue.xml74(para)
+msgid "Run the following command:"
+msgstr "以下のコマンドを実行します。"
+
+#: ./doc/install-guide/section_nova-compute.xml161(para)
+msgid ""
+"If this command returns a value of <emphasis>one or greater</emphasis>, your"
+" system supports hardware acceleration which typically requires no "
+"additional configuration."
+msgstr "このコマンドが <emphasis>1 以上</emphasis>の値を返したならば、お使いのシステムがハードウェア支援機能をサポートし、一般的に追加の設定は必要ありません。"
+
+#: ./doc/install-guide/section_nova-compute.xml165(para)
+msgid ""
+"If this command returns a value of <emphasis>zero</emphasis>, your system "
+"does not support hardware acceleration and you must configure "
+"<literal>libvirt</literal> to use QEMU instead of KVM."
+msgstr "このコマンドが <emphasis>0</emphasis> を返す場合、お使いのシステムはハードウェア支援機能をサポートしません。<literal>libvirt</literal> は KVM の代わりに QEMU を使用する必要があります。"
+
+#: ./doc/install-guide/section_nova-compute.xml170(para)
+msgid ""
+"Edit the <literal>[libvirt]</literal> section in the <filename>/etc/nova"
+"/nova-compute.conf</filename> file to modify this key:"
+msgstr "このキーを変更するために <filename>/etc/nova/nova-compute.conf</filename> ファイルの <literal>[libvirt]</literal> セクションを編集します。"
+
+#: ./doc/install-guide/section_nova-compute.xml183(para)
+msgid ""
+"On Ubuntu 12.04, kernels backported from newer releases may not "
+"automatically load the KVM modules for hardware acceleration when the system"
+" boots. In this case, launching an instance will fail with the following "
+"message in the <filename>/var/log/nova/nova-compute.log</filename> file:"
+msgstr "Ubuntu 12.04 の場合、新しいカーネルからバックポートされたカーネルは、システム起動時に KVM のハードウェア支援機能のモジュールを自動的に読み込まない可能性があります。この場合、インスタンスの起動に失敗し、以下のメッセージが <filename>/var/log/nova/nova-compute.log</filename> ファイルに記録されます。"
+
+#: ./doc/install-guide/section_nova-compute.xml189(para)
+msgid ""
+"As a workaround for this issue, you must add the appropriate module for your"
+" system to the <filename>/etc/modules</filename> file."
+msgstr "この問題の回避策として、お使いのシステム用の適切なモジュールを <filename>/etc/modules</filename> ファイルに追加する必要があります。"
+
+#: ./doc/install-guide/section_nova-compute.xml192(para)
+msgid "For systems with Intel processors, run the following command:"
+msgstr "Intel プロセッサーのシステムの場合、以下のコマンドを実行します。"
+
+#: ./doc/install-guide/section_nova-compute.xml195(para)
+msgid "For systems with AMD processors, run the following command:"
+msgstr "AMD プロセッサーのシステムの場合、以下のコマンドを実行します。"
+
+#: ./doc/install-guide/section_nova-compute.xml201(para)
+msgid "Remove the SQLite database created by the packages:"
+msgstr "パッケージにより作成された SQLite データベースを削除します。"
+
+#: ./doc/install-guide/section_nova-compute.xml205(para)
+msgid ""
+"Start the Compute service and configure it to start when the system boots:"
+msgstr "Compute サービスを起動し、システム起動時に起動するよう設定します。"
+
 #: ./doc/install-guide/section_trove-install.xml3(title)
 msgid "Install the Database service"
 msgstr "Database サービスのインストール"
@@ -2094,15 +5292,6 @@ msgstr "Database サービスのインストール"
 msgid "This procedure installs the Database module on the controller node."
 msgstr "この手順は、コントローラーノードに Database モジュールをインストールします。"
 
-#: ./doc/install-guide/section_trove-install.xml7(title)
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml28(title)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml8(title)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml24(title)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml8(title)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml8(title)
-msgid "Prerequisites"
-msgstr "前提"
-
 #: ./doc/install-guide/section_trove-install.xml8(para)
 msgid ""
 "This chapter assumes that you already have a working OpenStack environment "
@@ -2136,7 +5325,7 @@ msgid ""
 "settings</link>, and <link linkend=\"debconf-api-endpoints\">API "
 "endpoint</link> registration. The <placeholder-1/> command runs "
 "automatically."
-msgstr ""
+msgstr "<link linkend=\"debconf-dbconfig-common\">データベース管理</link>、<link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> 設定</link>、<link linkend=\"debconf-api-endpoints\">API エンドポイント</link>登録に関するプロンプトに答えます。<placeholder-1/> コマンドが自動的に実行されます。"
 
 #: ./doc/install-guide/section_trove-install.xml37(para)
 msgid "Prepare OpenStack:"
@@ -2301,747 +5490,197 @@ msgstr "Database サービスを起動し、システム起動時に起動する
 msgid "Restart Database services:"
 msgstr "Database サービスを再起動します。"
 
-#: ./doc/install-guide/section_nova-networking-compute-node.xml5(title)
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml6(title)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml6(title)
-msgid "Configure compute node"
-msgstr "コンピュートノードの設定"
+#: ./doc/install-guide/ch_cinder.xml6(title)
+msgid "Add the Block Storage service"
+msgstr "Block Storage Service の追加"
 
-#: ./doc/install-guide/section_nova-networking-compute-node.xml6(para)
+#: ./doc/install-guide/ch_cinder.xml7(para)
 msgid ""
-"This section covers deployment of a simple <glossterm>flat "
-"network</glossterm> that provides IP addresses to your instances via "
-"<glossterm>DHCP</glossterm>. If your environment includes multiple compute "
-"nodes, the <glossterm>multi-host</glossterm> feature provides redundancy by "
-"spreading network functions across compute nodes."
-msgstr "このセクションは、インスタンスに <glossterm>DHCP</glossterm> 経由で IP アドレスを提供する、シンプルな<glossterm baseform=\"flat network\">フラットネットワーク</glossterm>の導入について取り扱います。お使いの環境に複数のコンピュートノードがある場合、<glossterm>multi-host</glossterm> 機能により、コンピュートノードをまたがるネットワーク機能の分散により冗長性を提供します。"
+"The OpenStack Block Storage service works through the interaction of a "
+"series of daemon processes named <systemitem "
+"role=\"process\">cinder-*</systemitem> that reside persistently on the host "
+"machine or machines. You can run the binaries from a single node or across "
+"multiple nodes. You can also run them on the same node as other OpenStack "
+"services. The following sections introduce Block Storage service components "
+"and concepts and show you how to configure and install the Block Storage "
+"service."
+msgstr "OpenStack Block Storage Service はホストマシンに永続的に存在する <systemitem role=\"process\">cinder-*</systemitem> という名前の一連のデーモンプロセスと通信して動作します。単一ノードや複数のノードに渡りバイナリを実行できます。他の OpenStack サービスのように同じノードで実行することもできます。以下のセクションは Block Storage Service のコンポーネントと概念について紹介し、Block Storage Service の設定方法とインストール方法を説明します。"
 
-#: ./doc/install-guide/section_nova-networking-compute-node.xml13(title)
-msgid "To install legacy networking components"
-msgstr "レガシーネットワークのコンポーネントのインストール方法"
-
-#: ./doc/install-guide/section_nova-networking-compute-node.xml21(title)
-#: ./doc/install-guide/section_nova-networking-controller-node.xml9(title)
-msgid "To configure legacy networking"
-msgstr "レガシーネットワークの設定方法"
-
-#: ./doc/install-guide/section_nova-networking-compute-node.xml23(para)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml325(para)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml369(para)
-#: ./doc/install-guide/section_ceilometer-glance.xml20(para)
-#: ./doc/install-guide/section_nova-networking-controller-node.xml11(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml192(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml226(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml262(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml355(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml189(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml287(para)
-#: ./doc/install-guide/section_heat-install.xml94(para)
-msgid "Run the following commands:"
-msgstr "以下のコマンドを実行します。"
-
-#: ./doc/install-guide/section_nova-networking-compute-node.xml24(para)
-#: ./doc/install-guide/section_nova-networking-compute-node.xml57(para)
+#: ./doc/install-guide/ch_cinder.xml21(para)
 msgid ""
-"Replace <replaceable>INTERFACE_NAME</replaceable> with the actual interface "
-"name for the external network. For example, <emphasis>eth1</emphasis> or "
-"<emphasis>ens224</emphasis>."
-msgstr "<replaceable>INTERFACE_NAME</replaceable> を外部ネットワーク用の実際のインターフェース名で置き換えます。例えば、<emphasis>eth1</emphasis> や <emphasis>ens224</emphasis> です。"
+"Your OpenStack environment now includes Block Storage. You can <link linkend"
+"=\"launch-instance\">launch an instance</link> or add more services to your "
+"environment in the following chapters."
+msgstr "OpenStack 環境に Block Storage が追加されました。<link linkend=\"launch-instance\">インスタンスの起動</link>、以降の章に記載されているサービスの環境への追加を実行できます。"
 
-#: ./doc/install-guide/section_nova-networking-compute-node.xml50(replaceable)
-#: ./doc/install-guide/section_nova-networking-compute-node.xml52(replaceable)
-#: ./doc/install-guide/section_nova-networking-compute-node.xml73(replaceable)
-#: ./doc/install-guide/section_nova-networking-compute-node.xml74(replaceable)
-#: ./doc/install-guide/section_basics-networking-nova.xml99(replaceable)
-#: ./doc/install-guide/section_basics-networking-nova.xml100(replaceable)
-#: ./doc/install-guide/section_basics-networking-nova.xml110(replaceable)
-#: ./doc/install-guide/section_basics-networking-neutron.xml108(replaceable)
-#: ./doc/install-guide/section_basics-networking-neutron.xml109(replaceable)
-#: ./doc/install-guide/section_basics-networking-neutron.xml119(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml461(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml469(replaceable)
-msgid "INTERFACE_NAME"
-msgstr "INTERFACE_NAME"
+#: ./doc/install-guide/section_debconf-concepts.xml7(title)
+msgid "debconf concepts"
+msgstr "debconf の概念"
 
-#: ./doc/install-guide/section_nova-networking-compute-node.xml55(para)
-#: ./doc/install-guide/section_nova-networking-controller-node.xml18(para)
+#: ./doc/install-guide/section_debconf-concepts.xml8(para)
 msgid ""
-"Edit the <filename>/etc/nova/nova.conf</filename> file and add the following"
-" keys to the <literal>[DEFAULT]</literal> section:"
-msgstr "<filename>/etc/nova/nova.conf</filename> ファイルを編集し、以下のキーを <literal>[DEFAULT]</literal> セクションに追加します。"
+"This chapter explains how to use the Debian <systemitem "
+"class=\"library\">debconf</systemitem> and <systemitem class=\"library"
+"\">dbconfig-common</systemitem> packages to configure OpenStack services. "
+"These packages enable users to perform configuration tasks. When users "
+"install OpenStack packages, <package>debconf</package> prompts the user for "
+"responses, which seed the contents of configuration files associated with "
+"that package. After package installation, users can update the configuration"
+" of a package by using the <placeholder-1/> program."
+msgstr "本章は OpenStack サービスを設定するために Debian の <systemitem class=\"library\">debconf</systemitem> と <systemitem class=\"library\">dbconfig-common</systemitem> を使用する方法について説明します。これらのパッケージによりユーザーが設定作業を実行できます。ユーザーが OpenStack パッケージをインストールするとき、<package>debconf</package> がユーザーにプロンプトを表示します。これは、パッケージに関連づけられた設定ファイルの内容をシードします。パッケージのインストール後、ユーザーは <placeholder-1/> プログラムを使用することにより、パッケージの設定を更新できます。"
 
-#: ./doc/install-guide/section_nova-networking-compute-node.xml77(para)
-msgid "Restart the services:"
-msgstr "サービスを再起動します。"
-
-#: ./doc/install-guide/section_nova-networking-compute-node.xml80(para)
-msgid "Start the services and configure them to start when the system boots:"
-msgstr "サービスを起動し、システム起動時に起動するよう設定します。"
-
-#: ./doc/install-guide/section_trove-verify.xml5(title)
-msgid "Verify the Database service installation"
-msgstr "Database サービスのインストールを検証します。"
-
-#: ./doc/install-guide/section_trove-verify.xml6(para)
+#: ./doc/install-guide/section_debconf-concepts.xml18(para)
 msgid ""
-"To verify that the Database service is installed and configured correctly, "
-"try executing a Trove command:"
-msgstr "Database サービスがインストールされ、正しく設定されていることを検証するために、Trove コマンドを実行してみます。"
+"If you are familiar with these packages and pre-seeding, you can proceed to "
+"<xref linkend=\"ch_keystone\"/>."
+msgstr "これらのパッケージと事前シードに慣れている場合、<xref linkend=\"ch_keystone\"/> に進むことができます。"
 
-#: ./doc/install-guide/section_trove-verify.xml10(para)
-msgid "Source the <filename>demo-openrc.sh</filename> file."
-msgstr "<filename>demo-openrc.sh</filename> ファイルを読み込みます。"
+#: ./doc/install-guide/section_debconf-concepts.xml21(title)
+msgid "The Debian packages"
+msgstr "Debian パッケージ"
 
-#: ./doc/install-guide/section_trove-verify.xml14(para)
-msgid "Retrieve the Trove instances list:"
-msgstr "Trove インスタンスの一覧を取得します。"
-
-#: ./doc/install-guide/section_trove-verify.xml16(para)
-msgid "You should see output similar to this:"
-msgstr "このように出力されます。"
-
-#: ./doc/install-guide/section_trove-verify.xml23(para)
+#: ./doc/install-guide/section_debconf-concepts.xml22(para)
 msgid ""
-"Assuming you have created an image for the type of database you want, and "
-"have updated the datastore to use that image, you can now create a Trove "
-"instance (database). To do this, use the trove <placeholder-1/> command."
-msgstr "使用したいデータベースの種類に応じたイメージを作成し、そのイメージを使用するためにデータストアを更新したことを仮定すると、Trove インスタンス (データベース) を作成できます。このために、trove <placeholder-1/> コマンドを使用します。"
+"The rules described here are from the <link href=\"http://www.debian.org/doc"
+"/debian-policy/\"><citetitle>Debian Policy Manual</citetitle></link>. If any"
+" rule described in this chapter is not respected, you have found a serious "
+"bug that must be fixed."
+msgstr "ここに記載されたルールは <link href=\"http://www.debian.org/doc/debian-policy/\"><citetitle>Debian Policy Manual</citetitle></link> からのものです。本章に記載された何らかのルールが関係しなければ、修正すべき深刻なバグを見つけましたことになります。"
 
-#: ./doc/install-guide/section_trove-verify.xml30(para)
-msgid "This example shows you how to create a MySQL 5.5 database:"
-msgstr "この例は MySQL 5.5 データベースを作成する方法です。"
-
-#: ./doc/install-guide/section_trove-verify.xml32(replaceable)
-msgid "name"
-msgstr "名前"
-
-#: ./doc/install-guide/section_trove-verify.xml32(replaceable)
-msgid "DBNAME"
-msgstr "DBNAME"
-
-#: ./doc/install-guide/section_trove-verify.xml33(replaceable)
-msgid "USER"
-msgstr "USER"
-
-#: ./doc/install-guide/section_trove-verify.xml33(replaceable)
-msgid "PASSWORD"
-msgstr "PASSWORD"
-
-#: ./doc/install-guide/section_nova-controller.xml5(title)
-msgid "Install Compute controller services"
-msgstr "Compute コントローラーサービスのインストール"
-
-#: ./doc/install-guide/section_nova-controller.xml6(para)
+#: ./doc/install-guide/section_debconf-concepts.xml27(para)
 msgid ""
-"Compute is a collection of services that enable you to launch virtual "
-"machine instances. You can configure these services to run on separate nodes"
-" or the same node. In this guide, most services run on the controller node "
-"and the service that launches virtual machines runs on a dedicated compute "
-"node. This section shows you how to install and configure these services on "
-"the controller node."
-msgstr "Compute は仮想マシンインスタンスを起動できるようにするためのサービス群です。これらのサービスを別々のノードで実行することも同じノードで実行することも設定できます。このガイドでは、多くのサービスはコントローラーノードで実行し、仮想マシンを起動するサービスはコンピュート専用ノードで実行します。このセクションは、コントローラーノードにこれらのサービスをインストールし、設定する方法を示します。"
+"When you install or upgrade a Debian package, all configuration file values "
+"are preserved. Using the <systemitem class=\"library\">debconf</systemitem> "
+"database as a registry is considered a bug in Debian. If you edit something "
+"in any OpenStack configuration file, the <systemitem "
+"class=\"library\">debconf</systemitem> package reads that value when it "
+"prepares to prompt the user. For example, to change the log in name for the "
+"RabbitMQ messaging queue for a service, you can edit its value in the "
+"corresponding configuration file."
+msgstr "Debian パッケージをインストールまたはアップグレードするとき、すべての設定値は保護されます。レジストリとして <systemitem class=\"library\">debconf</systemitem> データベースを使用することは Debian でバグとみなされます。あらゆる OpenStack 設定ファイルで何かを編集する場合、ユーザーにプロンプトを表示するとき、<systemitem class=\"library\">debconf</systemitem> パッケージがその値を読み込みます。例えば、サービス用の RabbitMQ メッセージングキューの名前でログを変更するために、対応する設定ファイルでその値を編集できます。"
 
-#: ./doc/install-guide/section_nova-controller.xml15(para)
-msgid "Install the Compute packages necessary for the controller node."
-msgstr "コントローラーノードに必要な Compute のパッケージをインストールします。"
-
-#: ./doc/install-guide/section_nova-controller.xml27(para)
+#: ./doc/install-guide/section_debconf-concepts.xml36(para)
 msgid ""
-"Respond to the prompts for <link linkend=\"debconf-dbconfig-"
-"common\">database management</link>, <link linkend=\"debconf-"
-"keystone_authtoken\"><literal>[keystone_authtoken]</literal> "
-"settings</link>, <link linkend=\"debconf-rabbitqm\">RabbitMQ "
-"credentials</link>, and <link linkend=\"debconf-api-endpoints\">API "
-"endpoint</link> registration. The <placeholder-1/> command runs "
-"automatically."
-msgstr "<link linkend=\"debconf-dbconfig-common\">データベース管理</link>、<link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> 設定</link>、<link linkend=\"debconf-rabbitqm\">RabbitMQ クレデンシャル</link>、<link linkend=\"debconf-api-endpoints\">API エンドポイント</link>登録に関するプロンプトに答えます。<placeholder-1/> コマンドが自動的に実行されます。"
+"To opt out of using the <systemitem class=\"library\">debconf</systemitem> "
+"package, run the <placeholder-1/> command and select non-interactive mode:"
+msgstr "<systemitem class=\"library\">debconf</systemitem> パッケージを使用することを止めるために、<placeholder-1/> コマンドを実行し、非対話モードを選択します。"
 
-#: ./doc/install-guide/section_nova-controller.xml38(para)
+#: ./doc/install-guide/section_debconf-concepts.xml41(para)
 msgid ""
-"Compute stores information in a database. In this guide, we use a MySQL "
-"database on the controller node. Configure Compute with the database "
-"location and credentials. Replace <replaceable>NOVA_DBPASS</replaceable> "
-"with the password for the database that you will create in a later step."
-msgstr "Compute は情報を保存するためにデータベースを使用します。このガイドでは、コントローラーノードで MySQL データベースを使用します。Compute をデータベースの位置とクレデンシャルで設定します。<replaceable>NOVA_DBPASS</replaceable> を後のステップで作成するデータベース用パスワードで置き換えます。"
+"Then, <systemitem class=\"library\">debconf</systemitem> does not prompt "
+"you."
+msgstr "そして、<systemitem class=\"library\">debconf</systemitem> がプロンプトを表示しなくなります。"
 
-#: ./doc/install-guide/section_nova-controller.xml44(replaceable)
-#: ./doc/install-guide/section_nova-controller.xml51(replaceable)
-#: ./doc/install-guide/section_nova-controller.xml119(replaceable)
-#: ./doc/install-guide/section_nova-controller.xml121(replaceable)
-#: ./doc/install-guide/section_nova-compute.xml72(replaceable)
-msgid "NOVA_DBPASS"
-msgstr "NOVA_DBPASS"
-
-#: ./doc/install-guide/section_nova-controller.xml45(para)
+#: ./doc/install-guide/section_debconf-concepts.xml43(para)
 msgid ""
-"Edit the <literal>[database]</literal> section in the "
-"<filename>/etc/nova/nova.conf</filename> file, adding it if necessary, to "
-"modify this key:"
-msgstr "<filename>/etc/nova/nova.conf</filename> ファイルの <literal>[database]</literal> セクションを編集し、このキーを変更します。必要に応じてセクションを追加します。"
+"Another way to disable the <systemitem "
+"class=\"library\">debconf</systemitem> package is to prefix the "
+"<placeholder-1/> command with "
+"<literal>DEBIAN_FRONTEND=noninteractive</literal>, as follows:"
+msgstr "<systemitem class=\"library\">debconf</systemitem> を無効化する別の方法は、以下のように <placeholder-1/> コマンドに <literal>DEBIAN_FRONTEND=noninteractive</literal> を付けることです。"
 
-#: ./doc/install-guide/section_nova-controller.xml55(para)
+#: ./doc/install-guide/section_debconf-concepts.xml49(para)
 msgid ""
-"Set these configuration keys to configure Compute to use the Qpid message "
-"broker:"
-msgstr "Compute が Qpid メッセージブローカーを使用するよう設定するために、これらの設定キーを設定します。"
+"If you configure a package with <systemitem "
+"class=\"library\">debconf</systemitem> incorrectly, you can re-configure it,"
+" as follows:"
+msgstr "<systemitem class=\"library\">debconf</systemitem> を用いて誤って設定した場合、以下のように再設定できます。"
 
-#: ./doc/install-guide/section_nova-controller.xml62(para)
-#: ./doc/install-guide/section_nova-compute.xml107(para)
+#: ./doc/install-guide/section_debconf-concepts.xml52(replaceable)
+msgid "PACKAGE-NAME"
+msgstr "PACKAGE-NAME"
+
+#: ./doc/install-guide/section_debconf-concepts.xml53(para)
 msgid ""
-"Configure the Compute service to use the RabbitMQ message broker by setting "
-"these configuration keys in the <literal>[DEFAULT]</literal> configuration "
-"group of the <filename>/etc/nova/nova.conf</filename> file:"
-msgstr "<filename>/etc/nova/nova.conf</filename> ファイルの <literal>[DEFAULT]</literal> 設定グループにこれらの設定キーを設定することにより、Compute サービスが RabbitMQ メッセージブローカーを使用するよう設定します。"
+"This calls the post-installation script for the <replaceable>PACKAGE-"
+"NAME</replaceable> package after the user responds to all prompts. If you "
+"cannot install a Debian package in a non-interactive way, you have found a "
+"release-critical bug in Debian. Report it to the Debian bug tracking system."
+msgstr "これはユーザーがすべてのプロンプトに答えた後、<replaceable>PACKAGE-NAME</replaceable> パッケージ用のインストール後スクリプトを呼び出します。非対話的な方法で Debian パッケージをインストールできない場合、Debian で深刻なリリースのバグを見つけたことになります。Debian のバグ追跡システムに報告してください。"
 
-#: ./doc/install-guide/section_nova-controller.xml73(para)
+#: ./doc/install-guide/section_debconf-concepts.xml58(para)
 msgid ""
-"Set these configuration keys to configure Compute to use the RabbitMQ "
-"message broker:"
-msgstr "Compute が RabbitMQ メッセージブローカーを使用するよう設定するために、これらの設定キーを設定します。"
+"Generally, the <systemitem class=\"library\">-common</systemitem> packages "
+"install the configuration files. For example, the <literal>glance-"
+"common</literal> package installs the <filename>glance-api.conf</filename> "
+"and <filename>glance-registry.conf</filename> files. So, for the Image "
+"Service, you must re-configure the <literal>glance-common</literal> package."
+" The same applies for <literal>cinder-common</literal>, <literal>nova-"
+"common</literal>, and <literal>heat-common</literal> packages."
+msgstr "一般的に、<systemitem class=\"library\">-common</systemitem> パッケージが設定ファイルをインストールします。例えば、<literal>glance-common</literal> パッケージが <filename>glance-api.conf</filename> と <filename>glance-registry.conf</filename> ファイルをインストールします。そのため、Image Service 用に <literal>glance-common</literal> パッケージを再設定する必要があります。同じことを <literal>cinder-common</literal>、<literal>nova-common</literal>、<literal>heat-common</literal> パッケージに適用します。"
 
-#: ./doc/install-guide/section_nova-controller.xml81(para)
+#: ./doc/install-guide/section_debconf-concepts.xml68(para)
 msgid ""
-"Set the <option>my_ip</option>, <option>vncserver_listen</option>, and "
-"<option>vncserver_proxyclient_address</option> configuration options to the "
-"management interface IP address of the controller node:"
-msgstr "<option>my_ip</option>、<option>vncserver_listen</option>、<option>vncserver_proxyclient_address</option> 設定オプションをコントローラーノードの管理インターフェース IP アドレスに設定します。"
+"In <systemitem class=\"library\">debconf</systemitem>, the higher the "
+"priority for a screen, the greater the chance that the user sees that "
+"screen. If a <systemitem class=\"library\">debconf</systemitem> screen has "
+"<literal>medium</literal> priority and you configure the Debian system to "
+"show only <literal>critical</literal> prompts, which is the default in "
+"Debian, the user does not see that <systemitem "
+"class=\"library\">debconf</systemitem> screen. Instead, the default for the "
+"related package is used. In the Debian OpenStack packages, a number of "
+"<systemitem class=\"library\">debconf</systemitem> screens are set with "
+"<literal>medium</literal> priority. Consequently, if you want to respond to "
+"all <systemitem class=\"library\">debconf</systemitem> screens from the "
+"Debian OpenStack packages, you must run the following command and select the"
+" <literal>medium</literal> priority before you install any packages:"
+msgstr "<systemitem class=\"library\">debconf</systemitem> では、画面の優先度が高ければ高いほど、ユーザーがその画面を参照する機会が増えます。<systemitem class=\"library\">debconf</systemitem> 画面が <literal>medium</literal> (中) の優先度を持ち、Debian システムが <literal>critical</literal> (重要) のプロンプトのみを表示するよう設定している場合、その <systemitem class=\"library\">debconf</systemitem> 画面が表示されません。代わりに、関連パッケージのデフォルトが使用されます。Debian OpenStack パッケージの場合、数多くの <systemitem class=\"library\">debconf</systemitem> 画面が <literal>medium</literal> 優先度に設定されています。そのため、Debian OpenStack パッケージのすべての <systemitem class=\"library\">debconf</systemitem> 画面をプロンプト表示したい場合、何らかのパッケージをインストールする前に、以下のコマンドを実行し、<literal>medium</literal> 優先度を選択する必要があります。"
 
-#: ./doc/install-guide/section_nova-controller.xml89(para)
+#: ./doc/install-guide/section_debconf-concepts.xml87(para)
 msgid ""
-"Edit the <filename>/etc/nova/nova.conf</filename> file and add these lines "
-"to the <literal>[DEFAULT]</literal> section:"
-msgstr "<filename>/etc/nova/nova.conf</filename> ファイルを編集し、<literal>[DEFAULT]</literal> セクションにこれらの行を追加します。"
+"The packages do not require pre-depends. If <systemitem class=\"library"
+"\">dbconfig-common</systemitem> is already installed on the system, the user"
+" sees all prompts. However, you cannot define the order in which the "
+"<systemitem class=\"library\">debconf</systemitem> screens appear. The user "
+"must make sense of it even if the prompts appear in an illogical order."
+msgstr "パッケージは事前の依存関係を必要としません。<systemitem class=\"library\">dbconfig-common</systemitem> がすでにシステムにインストールされていれば、すべてのプロンプトが表示されます。しかしながら、<systemitem class=\"library\">debconf</systemitem> 画面が表示される順番を定義できません。プロンプトが非論理的な順番で表示されたときでさえ、ユーザーはその意味を理解する必要があります。"
 
-#: ./doc/install-guide/section_nova-controller.xml92(para)
+#: ./doc/install-guide/section_nova-networking-controller-node.xml6(para)
 msgid ""
-"In Debian, the <package>debconf</package> package automatically sets up "
-"<literal>my_ip</literal> parameter but you must edit the "
-"<filename>/etc/nova/nova.conf</filename> file to configure the "
-"<option>vncserver_listen</option> and "
-"<option>vncserver_proxyclient_address</option> options, which appear at the "
-"end of the file:"
-msgstr "Debian では、<package>debconf</package> パッケージが自動的に <literal>my_ip</literal> パラメーターをセットアップしますが、<filename>/etc/nova/nova.conf</filename> ファイルの最後にある <option>vncserver_listen</option> オプションと <option>vncserver_proxyclient_address</option> オプションを設定するために、このファイルを編集する必要があります。"
+"Legacy networking primarily involves compute nodes. However, you must "
+"configure the controller node to use it."
+msgstr "レガシーネットワークは、主にコンピュートノードを関係します。しかしながら、それを使用するために、コントローラーノードを設定する必要があります。"
 
-#: ./doc/install-guide/section_nova-controller.xml107(para)
+#: ./doc/install-guide/section_nova-networking-controller-node.xml26(para)
+#: ./doc/install-guide/section_neutron-ml2-controller-node.xml451(para)
+#: ./doc/install-guide/section_neutron-ovs-controller-node.xml331(para)
+msgid "Restart the Compute services:"
+msgstr "Compute のサービスを再起動します。"
+
+#: ./doc/install-guide/ch_nova.xml7(title)
+msgid "Configure Compute services"
+msgstr "Compute Service の設定"
+
+#: ./doc/install-guide/ch_networking.xml6(title)
+msgid "Add a networking service"
+msgstr "Networking Service の追加"
+
+#: ./doc/install-guide/ch_networking.xml7(para)
 msgid ""
-"By default, the Ubuntu packages create an SQLite database. Delete the "
-"<filename>nova.sqlite</filename> file created in the "
-"<filename>/var/lib/nova/</filename> directory so that it does not get used "
-"by mistake:"
-msgstr "Ubuntu パッケージはデフォルトで SQLite データベースを作成します。誤って使用されないように、<filename>/var/lib/nova/</filename> に作成された <filename>nova.sqlite</filename> ファイルを削除します。"
+"Configuring networking in OpenStack can be a bewildering experience. This "
+"guide provides step-by-step instructions for both OpenStack Networking "
+"(neutron) and the legacy networking (nova-network) service. If you are "
+"unsure which to use, we recommend trying OpenStack Networking because it "
+"offers a considerable number of features and flexibility including "
+"<glossterm baseform=\"plug-in\">plug-ins</glossterm> for a variety of "
+"emerging products supporting <glossterm>virtual networking</glossterm>. See "
+"the <link href=\"http://docs.openstack.org/admin-guide-"
+"cloud/content/ch_networking.html\">Networking</link> chapter of the "
+"<citetitle>OpenStack Cloud Administrator Guide</citetitle> for more "
+"information."
+msgstr "OpenStack でネットワークを設定することは、目の回るような経験になる可能性があります。このガイドは、OpenStack Networking (neutron) とレガシーネットワーク (nova-network) の両方をステップバイステップで説明します。どちらを使用するか決めていない場合、OpenStack Networking を試してみることを推奨します。これは、かなり数多くの機能を持ち、<glossterm baseform=\"virtual networking\">仮想ネットワーク</glossterm>をサポートするさまざまな最新製品向けの<glossterm baseform=\"plug-in\">プラグイン</glossterm>などの柔軟性があります。詳細は、<citetitle>OpenStack Cloud Administrator Guide</citetitle> の <link href=\"http://docs.openstack.org/admin-guide-cloud/content/ch_networking.html\">Networking</link> を参照してください。"
 
-#: ./doc/install-guide/section_nova-controller.xml114(para)
+#: ./doc/install-guide/ch_networking.xml23(title)
+msgid "Modular Layer 2 (ML2) plug-in"
+msgstr "Modular Layer 2 (ML2) プラグイン"
+
+#: ./doc/install-guide/ch_networking.xml38(para)
 msgid ""
-"Use the password you created previously to log in as root. Create a "
-"<literal>nova</literal> database user:"
-msgstr "root としてログインするために、前に作成したパスワードを使用します。<literal>nova</literal> データベースユーザーを作成します。"
-
-#: ./doc/install-guide/section_nova-controller.xml124(para)
-msgid "Create the Compute service tables:"
-msgstr "Compute サービスのテーブルを作成します。"
-
-#: ./doc/install-guide/section_nova-controller.xml128(para)
-msgid ""
-"Create a <literal>nova</literal> user that Compute uses to authenticate with"
-" the Identity Service. Use the <literal>service</literal> tenant and give "
-"the user the <literal>admin</literal> role:"
-msgstr "Compute が Identity Service で認証するために使用する <literal>nova</literal> ユーザーを作成します。<literal>service</literal> プロジェクトを使用し、ユーザーに <literal>admin</literal> ロールを与えます。"
-
-#: ./doc/install-guide/section_nova-controller.xml132(replaceable)
-#: ./doc/install-guide/section_nova-controller.xml146(replaceable)
-#: ./doc/install-guide/section_nova-controller.xml166(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml234(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml258(replaceable)
-#: ./doc/install-guide/section_nova-compute.xml80(replaceable)
-#: ./doc/install-guide/section_nova-compute.xml99(replaceable)
-msgid "NOVA_PASS"
-msgstr "NOVA_PASS"
-
-#: ./doc/install-guide/section_nova-controller.xml132(replaceable)
-msgid "nova@example.com"
-msgstr "nova@example.com"
-
-#: ./doc/install-guide/section_nova-controller.xml136(para)
-msgid ""
-"Configure Compute to use these credentials with the Identity Service running"
-" on the controller. Replace <replaceable>NOVA_PASS</replaceable> with your "
-"Compute password."
-msgstr "コントローラーで実行している Identity Service でこれらのクレデンシャルを使用するよう Compute を設定します。<replaceable>NOVA_PASS</replaceable> をお使いの Compute パスワードで置き換えます。"
-
-#: ./doc/install-guide/section_nova-controller.xml147(para)
-msgid ""
-"Edit the <literal>[DEFAULT]</literal> section in the "
-"<filename>/etc/nova/nova.conf</filename> file to add this key:"
-msgstr "このキーを追加するために <filename>/etc/nova/nova.conf</filename> ファイルの <literal>[DEFAULT]</literal> セクションを編集します。"
-
-#: ./doc/install-guide/section_nova-controller.xml155(para)
-msgid "Add these keys to the <literal>[keystone_authtoken]</literal> section:"
-msgstr "これらのキーを <literal>[keystone_authtoken]</literal> セクションに追加します。"
-
-#: ./doc/install-guide/section_nova-controller.xml169(para)
-msgid ""
-"You must register Compute with the Identity Service so that other OpenStack "
-"services can locate it. Register the service and specify the endpoint:"
-msgstr "他の OpenStack サービスから使用できるように、Compute を Identity Service に登録します。サービスを登録し、エンドポイントを指定します。"
-
-#: ./doc/install-guide/section_nova-controller.xml182(para)
-msgid ""
-"Start Compute services and configure them to start when the system boots:"
-msgstr "Compute サービスを起動し、システム起動時に起動するよう設定します。"
-
-#: ./doc/install-guide/section_nova-controller.xml185(para)
-msgid "Restart Compute services:"
-msgstr "Compute サービスを再起動します。"
-
-#: ./doc/install-guide/section_nova-controller.xml206(para)
-msgid "To verify your configuration, list available images:"
-msgstr "設定を検証するために、使用可能なイメージを一覧表示します。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml8(para)
-msgid ""
-"This section details set up for any node that runs the <literal>nova-"
-"compute</literal> component but does not run the full network stack."
-msgstr "このセクションは <literal>nova-compute</literal> コンポーネントを実行するあらゆるノードのセットアップについて詳細に説明しますが、すべてのネットワークスタックを実行しません。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml13(para)
-msgid ""
-"By default, the <literal>system-config-firewall</literal> automated firewall"
-" configuration tool is in place on RHEL. This graphical interface (and a "
-"curses-style interface with <literal>-tui</literal> on the end of the name) "
-"enables you to configure IP tables as a basic firewall. You should disable "
-"it when you work with OpenStack Networking unless you are familiar with the "
-"underlying network technologies, as, by default, it blocks various types of "
-"network traffic that are important to neutron services. To disable it, "
-"launch the program and clear the <guilabel>Enabled</guilabel> check box."
-msgstr "<literal>system-config-firewall</literal> 自動ファイアウォール設定ツールが RHEL にデフォルトで入っています。このグラフィカルツール (および名前の最後に <literal>-tui</literal> を付けた端末スタイルのインターフェース) により、基本的なファイアウォールとして iptables を設定できます。基礎となるネットワーク技術に詳しくなければ、OpenStack Networking を利用しているときに、これを無効化すべきです。これは neutron サービスにとって重要であるさまざまな種類のネットワーク通信を遮断するためです。これを無効化する場合、プログラムを起動し、<guilabel>有効化</guilabel>チェックボックスを解除します。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml22(para)
-msgid ""
-"After you successfully set up OpenStack Networking with Neutron, you can re-"
-"enable and configure the tool. However, during OpenStack Networking setup, "
-"disable the tool to make it easier to debug network issues."
-msgstr "Neutron を用いて OpenStack Networking を正常にセットアップした後、ツールを再び有効化し、設定できます。しかしながら、OpenStack Networking のセットアップ中は、ネットワークの問題をデバッグしやすくするためにツールを無効化します。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml30(para)
-msgid ""
-"Disable packet destination filtering (route verification) to let the "
-"networking services route traffic to the VMs. Edit the "
-"<filename>/etc/sysctl.conf</filename> file and run the following command to "
-"activate changes:"
-msgstr "Networking Service が仮想マシンへの通信をルーティングできるように、パケット宛先フィルタリング (ルート検証) を無効化します。<filename>/etc/sysctl.conf</filename> を編集し、変更を有効化するために以下のコマンドを実行します。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml41(title)
-msgid "Install Open vSwitch plug-in"
-msgstr "Open vSwitch プラグインのインストール"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml42(para)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml185(para)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml176(para)
-msgid ""
-"OpenStack Networking supports a variety of plug-ins. For simplicity, we "
-"chose to cover the most common plug-in, Open vSwitch, and configure it to "
-"use basic GRE tunnels for tenant network traffic."
-msgstr "OpenStack Networking はさまざまなプラグインをサポートします。簡単のために、最も一般的なプラグイン Open vSwitch を取り扱うことにし、プロジェクトのネットワーク通信のために基本的な GRE トンネルを使用するよう設定します。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml47(para)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml181(para)
-msgid "Install the Open vSwitch plug-in and its dependencies:"
-msgstr "Open vSwitch プラグインと依存パッケージをインストールします。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml54(para)
-msgid "Restart Open vSwitch:"
-msgstr "Open vSwitch を再起動します。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml58(para)
-msgid "Start Open vSwitch and configure it to start when the system boots:"
-msgstr "Open vSwitch を起動し、システム起動時に起動するよう設定します。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml66(para)
-msgid ""
-"You must set some common configuration options no matter which networking "
-"technology you choose to use with Open vSwitch. You must add the <literal"
-">br-int</literal> integration bridge, which connects to the VMs."
-msgstr "どのネットワーク技術を Open vSwitch と一緒に使用するかによらず、いくつかの共通設定オプションを設定する必要があります。仮想マシンを接続する <literal>br-int</literal> 統合ブリッジを追加する必要があります。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml74(para)
-msgid ""
-"You must set some common configuration options. You must configure "
-"Networking core to use <acronym>OVS</acronym>. Edit the "
-"<filename>/etc/neutron/neutron.conf</filename> file:"
-msgstr "どのネットワーク技術を <acronym>OVS</acronym> と一緒に使用するかによらず、いくつかの共通設定オプションを設定する必要があります。<filename>/etc/neutron/neutron.conf</filename> ファイルを編集します。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml83(para)
-msgid ""
-"You must configure a firewall as well. You should use the same firewall "
-"plug-in that you chose to use when you set up the network node. To do this, "
-"edit "
-"<filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename>"
-" file and set the <literal>firewall_driver</literal> value under the "
-"<literal>securitygroup</literal> to the same value used on the network node."
-" For instance, if you chose to use the Hybrid OVS-IPTables plug-in, your "
-"configuration looks like this:"
-msgstr "同様にファイアウォールを設定する必要があります。ネットワークノードをセットアップするときに選択したものと同じファイアウォールプラグインを使用すべきです。そうするために、<filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename> ファイルを編集し、<literal>securitygroup</literal> の下にある <literal>firewall_driver</literal> 値をネットワークノードで使用したものと同じ値に設定します。例えば、ハイブリッド OVS iptables プラグインを使用したい場合、設定はこのようになるでしょう。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml96(para)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml313(para)
-msgid ""
-"You must use at least the No-Op firewall. Otherwise, Horizon and other "
-"OpenStack services cannot get and set required VM boot options."
-msgstr "少なくとも No-Op ファイアウォールを使用する必要があります。そうでなければ、Horizon と他の OpenStack サービスが必要となる仮想マシンのブートオプションを取得および設定できません。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml102(para)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml319(para)
-msgid "Configure the <acronym>OVS</acronym> plug-in to start on boot."
-msgstr "<acronym>OVS</acronym> プラグインをシステム起動時に起動するよう設定します。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml108(para)
-msgid ""
-"Tell the <acronym>OVS</acronym> plug-in to use GRE tunneling with a <literal"
-">br-int</literal> integration bridge, a <literal>br-tun</literal> tunneling "
-"bridge, and a local IP for the tunnel of "
-"<replaceable>DATA_INTERFACE</replaceable>'s IP Edit the "
-"<filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename>"
-" file:"
-msgstr "<literal>br-int</literal> 統合ブリッジを持つ GRE トンネリング、<literal>br-tun</literal> トンネリングブリッジ、<replaceable>DATA_INTERFACE</replaceable> の IP のトンネル用ローカル IP を使用するよう <acronym>OVS</acronym> プラグインに通知します。<filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename> ファイルを編集します。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml123(replaceable)
-msgid "DATA_INTERFACE_IP"
-msgstr "DATA_INTERFACE_IP"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml127(title)
-msgid "Configure common components"
-msgstr "共通コンポーネントの設定"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml129(para)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml82(para)
-msgid ""
-"Configure Networking to use <systemitem "
-"class=\"service\">keystone</systemitem> for authentication:"
-msgstr "Networking が認証用に <systemitem class=\"service\">keystone</systemitem> を使用するよう設定します。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml132(para)
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml166(para)
-msgid ""
-"Set the <literal>auth_strategy</literal> configuration key to "
-"<literal>keystone</literal> in the <literal>[DEFAULT]</literal> section of "
-"the file:"
-msgstr "このファイルの <literal>[DEFAULT]</literal> セクションで <literal>auth_strategy</literal> 設定キーを <literal>keystone</literal> に設定します。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml138(para)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml95(para)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml91(para)
-msgid ""
-"Set the <systemitem class=\"service\">neutron</systemitem> configuration for"
-" <systemitem class=\"service\">keystone</systemitem> authentication:"
-msgstr "<systemitem class=\"service\">keystone</systemitem> 認証用に <systemitem class=\"service\">neutron</systemitem> を設定します。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml155(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml185(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml240(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml257(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml33(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml151(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml177(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml384(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml414(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml46(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml110(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml139(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml237(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml254(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml109(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml136(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml393(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml407(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml77(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml103(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml277(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml304(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml74(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml100(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml302(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml332(replaceable)
-msgid "NEUTRON_PASS"
-msgstr "NEUTRON_PASS"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml160(para)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml113(para)
-msgid ""
-"To configure <systemitem class=\"service\">neutron</systemitem> to use "
-"<systemitem class=\"service\">keystone</systemitem> for authentication, edit"
-" the <filename>/etc/neutron/neutron.conf</filename> file."
-msgstr "認証に <systemitem class=\"service\">keystone</systemitem> を使用するよう <systemitem class=\"service\">neutron</systemitem> を設定するために <filename>/etc/neutron/neutron.conf</filename> ファイルを編集します。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml174(para)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml125(para)
-msgid ""
-"Add these lines to the <literal>[keystone_authtoken]</literal> section of "
-"the file:"
-msgstr "このファイルの <literal>[keystone_authtoken]</literal> セクションにこれらの行を追加します。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml190(para)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml144(para)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml141(para)
-msgid "Configure access to the <application>RabbitMQ</application> service:"
-msgstr "<application>RabbitMQ</application> サービスのアクセス権を設定します。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml201(para)
-msgid ""
-"Configure the <application>RabbitMQ</application> access. Edit the "
-"<filename>/etc/neutron/neutron.conf</filename> file to modify the following "
-"parameters in the <literal>[DEFAULT]</literal> section."
-msgstr "<application>RabbitMQ</application> のアクセス権を設定します。<literal>[DEFAULT]</literal> セクションにある以下のパラメーターを変更するために、<filename>/etc/neutron/neutron.conf</filename> ファイルを編集します。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml210(para)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml156(para)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml161(para)
-msgid "Configure access to the <application>Qpid</application> message queue:"
-msgstr "<application>Qpid</application> メッセージキューのアクセス権を設定します。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml218(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml220(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml165(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml167(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml169(replaceable)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml171(replaceable)
-msgid "guest"
-msgstr "guest"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml224(title)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml220(title)
-msgid "Configure Compute services for Networking"
-msgstr "Compute サービスの Networking 用設定"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml226(para)
-msgid ""
-"Configure OpenStack Compute to use OpenStack Networking services. Configure "
-"the <filename>/etc/nova/nova.conf</filename> file as per instructions below:"
-msgstr "OpenStack Compute が OpenStack Networking Service を使用するよう設定します。以下のそれぞれの説明にあるとおり、<filename>/etc/nova/nova.conf</filename> ファイルを編集します。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml249(para)
-msgid ""
-"Configure OpenStack Compute to use OpenStack Networking services. Edit the "
-"<filename>/etc/nova/nova.conf</filename> file:"
-msgstr "OpenStack Compute が OpenStack Networking Service を使用するよう設定します。<filename>/etc/nova/nova.conf</filename> ファイルを編集します。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml265(para)
-msgid ""
-"No matter which firewall driver you chose when you configured the network "
-"and compute nodes, you must edit the "
-"<filename>/etc/nova/nova.conf</filename> file to set the firewall driver to "
-"<literal>nova.virt.firewall.NoopFirewallDriver</literal>. Because OpenStack "
-"Networking handles the firewall, this statement instructs Compute to not use"
-" a firewall."
-msgstr "ネットワークとコンピュートノードを設定するときに、どのファイアウォールドライバーを選択しても、ファイアウォールドライバーを <literal>nova.virt.firewall.NoopFirewallDriver</literal> に設定するために、<filename>/etc/nova/nova.conf</filename> ファイルを編集する必要があります。OpenStack Networking はファイアウォールを取り扱うので、このステートメントは Compute がファイアウォールを使用しないことを指定します。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml275(para)
-msgid ""
-"If you want Networking to handle the firewall, edit the "
-"<filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename>"
-" file to set the <code>firewall_driver</code> option to the firewall for the"
-" plug-in. For example, with <acronym>OVS</acronym>, edit the file as "
-"follows:"
-msgstr "Networking にファイアウォールを取り扱わせたい場合、<code>firewall_driver</code> オプションをプラグイン用のファイアウォールに設定するために、<filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename> ファイルを編集します。例えば、<acronym>OVS</acronym> を使用する場合、ファイルを次のとおり編集します。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml290(para)
-msgid ""
-"If you do not want to use a firewall in Compute or Networking, edit both "
-"configuration files and set "
-"<code>firewall_driver=nova.virt.firewall.NoopFirewallDriver</code>. Also, "
-"edit the <filename>/etc/nova/nova.conf</filename> file and comment out or "
-"remove the <code>security_group_api=neutron</code> statement."
-msgstr "Compute や Networking でファイアウォールを使用したくない場合、両方の設定ファイルを編集し、<code>firewall_driver=nova.virt.firewall.NoopFirewallDriver</code> を設定します。また、<filename>/etc/nova/nova.conf</filename> ファイルを編集し、<code>security_group_api=neutron</code> ステートメントをコメントアウトまたは削除します。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml298(para)
-msgid ""
-"Otherwise, when you issue <placeholder-1/> commands, the <errortext>ERROR: "
-"The server has either erred or is incapable of performing the requested "
-"operation. (HTTP 500)</errortext> error might be returned."
-msgstr "そうしなければ、<placeholder-1/> コマンドを実行したとき、<errortext>ERROR: The server has either erred or is incapable of performing the requested operation. (HTTP 500)</errortext> エラーが返されるでしょう。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml309(title)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml322(title)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml432(title)
-msgid "Finalize installation"
-msgstr "インストールの完了"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml311(para)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml298(para)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml434(para)
-msgid ""
-"The <systemitem class=\"service\">neutron-server</systemitem> initialization"
-" script expects a symbolic link <filename>/etc/neutron/plugin.ini</filename>"
-" pointing to the configuration file associated with your chosen plug-in. "
-"Using Open vSwitch, for example, the symbolic link must point to "
-"<filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename>."
-" If this symbolic link does not exist, create it using the following "
-"commands:"
-msgstr "<systemitem class=\"service\">neutron-server</systemitem> 初期化スクリプトは、選択したプラグインと関連する設定ファイルを指し示すシンボリックリンク <filename>/etc/neutron/plugin.ini</filename> を予期しています。例えば、Open vSwitch を使用する場合、シンボリックリンクが <filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename> を指し示す必要があります。このシンボリックリンクが存在しなければ、以下のコマンドを使用して作成します。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml323(para)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml310(para)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml446(para)
-msgid ""
-"The <systemitem class=\"service\">openstack-neutron</systemitem> "
-"initialization script expects the variable "
-"<literal>NEUTRON_PLUGIN_CONF</literal> in file "
-"<filename>/etc/sysconfig/neutron</filename> to reference the configuration "
-"file associated with your chosen plug-in. Using Open vSwitch, for example, "
-"edit the <filename>/etc/sysconfig/neutron</filename> file and add the "
-"following:"
-msgstr "<systemitem class=\"service\">neutron-server</systemitem> 初期化スクリプトは、<filename>/etc/sysconfig/neutron</filename> の <literal>NEUTRON_PLUGIN_CONF</literal> 変数が、選択したプラグインと関連づけられた設定ファイルを参照していることを予期します。例えば、Open vSwitch を使用する場合、<filename>/etc/sysconfig/neutron</filename> ファイルを編集し、以下を追加します。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml334(para)
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml457(para)
-msgid "Restart Networking services."
-msgstr "Networking サービスを再起動します。"
-
-#: ./doc/install-guide/section_neutron-ovs-compute-node.xml340(para)
-msgid "Restart the Compute service."
-msgstr "Compute Service を再起動します。"
-
-#: ./doc/install-guide/section_dashboard-system-reqs.xml6(title)
-msgid "System requirements"
-msgstr "システム要件"
-
-#: ./doc/install-guide/section_dashboard-system-reqs.xml7(para)
-msgid ""
-"Before you install the OpenStack dashboard, you must meet the following "
-"system requirements:"
-msgstr "OpenStack Dashboard をインストールする前に、以下のシステム要件を満たしている必要があります。"
-
-#: ./doc/install-guide/section_dashboard-system-reqs.xml11(para)
-msgid ""
-"OpenStack Compute installation. Enable the Identity Service for user and "
-"project management."
-msgstr "OpenStack Compute のインストール。ユーザーとプロジェクトの管理用の Identity Service の有効化。"
-
-#: ./doc/install-guide/section_dashboard-system-reqs.xml13(para)
-msgid "Note the URLs of the Identity Service and Compute endpoints."
-msgstr "Identity Service と Compute のエンドポイントの URL を記録します。"
-
-#: ./doc/install-guide/section_dashboard-system-reqs.xml17(para)
-msgid ""
-"Identity Service user with sudo privileges. Because Apache does not serve "
-"content from a root user, users must run the dashboard as an Identity "
-"Service user with sudo privileges."
-msgstr "sudo 権限を持つ Identity Service のユーザー。Apache は root ユーザーのコンテンツを処理しないため、ユーザーは sudo 権限を持つ Identity Service のユーザーとしてダッシュボードを実行する必要があります。"
-
-#: ./doc/install-guide/section_dashboard-system-reqs.xml23(para)
-msgid ""
-"Python 2.6 or 2.7. The Python version must support Django. The Python "
-"version should run on any system, including Mac OS X. Installation "
-"prerequisites might differ by platform."
-msgstr "Python 2.6 または 2.7。Python が Django をサポートするバージョンである必要があります。この Python のバージョンは Mac OS X を含め、あらゆるシステムで実行すべきです。インストールの前提条件はプラットフォームにより異なるかもしれません。"
-
-#: ./doc/install-guide/section_dashboard-system-reqs.xml29(para)
-msgid ""
-"Then, install and configure the dashboard on a node that can contact the "
-"Identity Service."
-msgstr "そして、Identity Service と通信できるノードに Dashboard をインストールし、設定します。"
-
-#: ./doc/install-guide/section_dashboard-system-reqs.xml31(para)
-msgid ""
-"Provide users with the following information so that they can access the "
-"dashboard through a web browser on their local machine:"
-msgstr "ユーザーのローカルマシンからウェブブラウザー経由で Dashboard にアクセスできるよう、以下の情報をユーザーに提供します。"
-
-#: ./doc/install-guide/section_dashboard-system-reqs.xml36(para)
-msgid "The public IP address from which they can access the dashboard"
-msgstr "Dashboard にアクセスできるパブリック IP アドレス。"
-
-#: ./doc/install-guide/section_dashboard-system-reqs.xml40(para)
-msgid "The user name and password with which they can access the dashboard"
-msgstr "Dashboard にアクセスできるユーザー名とパスワード。"
-
-#: ./doc/install-guide/section_dashboard-system-reqs.xml44(para)
-msgid ""
-"Your web browser, and that of your users, must support HTML5 and have "
-"cookies and JavaScript enabled."
-msgstr "お使いのウェブブラウザーが HTML5 をサポートし、クッキーと JavaScript を有効化されている必要があります。"
-
-#: ./doc/install-guide/section_dashboard-system-reqs.xml48(para)
-msgid ""
-"To use the VNC client with the dashboard, the browser must support HTML5 "
-"Canvas and HTML5 WebSockets."
-msgstr "Dashboard で VNC クライアントを使用する場合、ブラウザーが HTML5 Canvas と HTML5 WebSockets をサポートする必要があります。"
-
-#: ./doc/install-guide/section_dashboard-system-reqs.xml50(para)
-msgid ""
-"For details about browsers that support noVNC, see <link "
-"href=\"https://github.com/kanaka/noVNC/blob/master/README.md\">https://github.com/kanaka/noVNC/blob/master/README.md</link>,"
-" and <link href=\"https://github.com/kanaka/noVNC/wiki/Browser-"
-"support\">https://github.com/kanaka/noVNC/wiki/Browser-support</link>, "
-"respectively."
-msgstr "noVNC をサポートするブラウザーの詳細はそれぞれ <link href=\"https://github.com/kanaka/noVNC/blob/master/README.md\">https://github.com/kanaka/noVNC/blob/master/README.md</link> と <link href=\"https://github.com/kanaka/noVNC/wiki/Browser-support\">https://github.com/kanaka/noVNC/wiki/Browser-support</link> を参照してください。"
-
-#: ./doc/install-guide/section_launch-instance-neutron.xml6(title)
-msgid "Launch an instance with OpenStack Networking (neutron)"
-msgstr "OpenStack Networking (neutron) を用いたインスタンスの起動"
-
-#: ./doc/install-guide/section_launch-instance-neutron.xml95(para)
-msgid ""
-"Your first instance uses the <literal>default</literal> security group. By "
-"default, this security group implements a firewall that blocks remote access"
-" to instances. If you would like to permit remote access to your instance, "
-"launch it and then <link linkend=\"launch-instance-neutron-remoteaccess\"> "
-"configure remote access</link>."
-msgstr "初めてのインスタンスは、<literal>default</literal> セキュリティグループを使用します。デフォルトで、このセキュリティグループは、インスタンスへのリモートアクセスを遮断するファイアウォールを適用します。インスタンスへのリモートアクセスを許可したければ、インスタンスを起動し、<link linkend=\"launch-instance-neutron-remoteaccess\">リモートアクセスを設定</link>します。"
-
-#: ./doc/install-guide/section_launch-instance-neutron.xml173(para)
-msgid "Verify the <literal>demo-net</literal> tenant network gateway:"
-msgstr "<literal>demo-net</literal> テナントネットワークのゲートウェイを検証します。"
-
-#: ./doc/install-guide/section_launch-instance-neutron.xml185(para)
-msgid "Verify the <literal>ext-net</literal> external network:"
-msgstr "<literal>ext-net</literal> 外部ネットワークを検証します。"
-
-#: ./doc/install-guide/section_launch-instance-neutron.xml224(para)
-msgid ""
-"Create a <glossterm>floating IP address</glossterm> on the <literal>ext-"
-"net</literal> external network:"
-msgstr "<literal>ext-net</literal> 外部ネットワークに <glossterm baseform=\"floating IP address\">Floating IP アドレス</glossterm> を作成します。"
-
-#: ./doc/install-guide/section_launch-instance-neutron.xml242(para)
-msgid "Associate the floating IP address with your instance:"
-msgstr "Floating IP アドレスをインスタンスに割り当てます。"
-
-#: ./doc/install-guide/section_launch-instance-neutron.xml249(para)
-msgid "Check the status of your floating IP address:"
-msgstr "Floating IP アドレスの状態を確認します。"
-
-#: ./doc/install-guide/ch_launch-instance.xml5(title)
-msgid "Launch an instance"
-msgstr "インスタンスの起動"
-
-#: ./doc/install-guide/ch_launch-instance.xml6(para)
-msgid ""
-"An instance is a VM that OpenStack provisions on a compute node. This guide "
-"shows you how to launch a minimal instance using the "
-"<glossterm>CirrOS</glossterm> image that you added to your environment in "
-"the <xref linkend=\"ch_glance\"/> chapter. In these steps, you use the "
-"command-line interface (CLI) on your controller node or any system with the "
-"appropriate OpenStack client libraries. To use the dashboard, see the <link "
-"href=\"http://docs.openstack.org/user-"
-"guide/content/ch_dashboard.html\"><citetitle>OpenStack User "
-"Guide</citetitle></link>."
-msgstr "インスタンスは、OpenStack がコンピュートノードに展開する仮想マシンです。このガイドは、<glossterm>CirrOS</glossterm> イメージを使用して、最小のインスタンスを起動する方法を示します。このイメージは、<xref linkend=\"ch_glance\"/>の章でお使いの環境に追加します。これらの手順で、コントローラーノード、または適切な OpenStack クライアントライブラリを持つシステムで CLI を使用します。ダッシュボードを使用する場合、<link href=\"http://docs.openstack.org/user-guide/content/ch_dashboard.html\"><citetitle>OpenStack User Guide</citetitle></link> を参照してください。"
-
-#: ./doc/install-guide/ch_launch-instance.xml15(para)
-msgid ""
-"Launch an instance using <link linkend=\"launch-instance-neutron\">OpenStack"
-" Networking (neutron) </link> or <link linkend=\"launch-instance-"
-"nova\">legacy networking (nova-network) </link>. For more information, see "
-"the <link href=\"http://docs.openstack.org/user-"
-"guide/content/cli_launch_instances.html\"><citetitle>OpenStack User "
-"Guide</citetitle></link>."
-msgstr "<link linkend=\"launch-instance-neutron\">OpenStack Networking (neutron) </link> または <link linkend=\"launch-instance-nova\">legacy networking (nova-network) </link> を使用して、インスタンスを起動します。詳細は <link href=\"http://docs.openstack.org/user-guide/content/cli_launch_instances.html\"><citetitle>OpenStack User Guide</citetitle></link> を参照してください。"
-
-#: ./doc/install-guide/ch_launch-instance.xml25(para)
-msgid ""
-"These steps reference example components created in previous chapters. You "
-"must adjust certain values such as IP addresses to match your environment."
-msgstr "これらの手順は、ここまでの章で作成したコンポーネント例を参照します。お使いの環境に合わせるために、IP アドレスなどの具体的な値を調整する必要があります。"
+"Your OpenStack environment now includes the core components necessary to "
+"launch a basic instance. You can <link linkend=\"launch-instance\">launch an"
+" instance</link> or add more services to your environment in the following "
+"chapters."
+msgstr "基本的なインスタンスを起動するために必要なコンポーネントが OpenStack 環境に追加されました。<link linkend=\"launch-instance\">インスタンスの起動</link>、移行の章に記載されているサービスの環境への追加を実行できます。"
 
 #. When image changes, this message will be marked fuzzy or untranslated for
 #. you.
@@ -3052,13 +5691,6 @@ msgid ""
 "md5=adf41c33778a691a560b7098908792db"
 msgstr "@@image: 'figures/debconf-screenshots/neutron_1_plugin_selection.png'; md5=adf41c33778a691a560b7098908792db"
 
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml6(title)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml6(title)
-#: ./doc/install-guide/section_basics-ntp.xml13(title)
-#: ./doc/install-guide/section_nova-networking-controller-node.xml5(title)
-msgid "Configure controller node"
-msgstr "コントローラーノードの設定"
-
 #: ./doc/install-guide/section_neutron-ml2-controller-node.xml9(para)
 msgid ""
 "Before you configure OpenStack Networking (neutron), you must create a "
@@ -3122,18 +5754,6 @@ msgstr "<literal>neutron</literal> サービスを作成します。"
 msgid "Create the service endpoint:"
 msgstr "サービスエンドポイントを作成します。"
 
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml57(title)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml24(title)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml23(title)
-msgid "To install the Networking components"
-msgstr "Networking コンポーネントのインストール方法"
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml64(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml38(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml35(para)
-msgid "SUSE does not use a separate ML2 plug-in package."
-msgstr "SUSE は ML2 プラグイン固有のパッケージを使用しません。"
-
 #: ./doc/install-guide/section_neutron-ml2-controller-node.xml67(para)
 msgid "Debian does not use a separate ML2 plug-in package."
 msgstr "Debian は ML2 プラグイン固有のパッケージを使用しません。"
@@ -3149,24 +5769,13 @@ msgid ""
 "plug-in."
 msgstr "Networking サーバーコンポーネントの設定には、データベース、認証機構、メッセージブローカー、トポロジー変更通知、プラグインがあります。"
 
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml77(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml47(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml44(para)
-msgid ""
-"Respond to prompts for <link linkend=\"debconf-dbconfig-common\">database "
-"management</link>, <link linkend=\"debconf-keystone_authtoken\">Identity "
-"service credentials</link>, <link linkend=\"debconf-api-endpoints\">service "
-"endpoint registration</link>, and <link linkend=\"debconf-rabbitqm\">message"
-" broker credentials</link>."
-msgstr "<link linkend=\"debconf-dbconfig-common\">データベース管理</link>、<link linkend=\"debconf-keystone_authtoken\">Identity のクレデンシャル</link>、<link linkend=\"debconf-api-endpoints\">サービスエンドポイント登録</link>、<link linkend=\"debconf-rabbitqm\">メッセージブローカーのクレデンシャル</link>に関するプロンプトに答えます。"
-
 #: ./doc/install-guide/section_neutron-ml2-controller-node.xml87(para)
 msgid ""
 "During the installation, you will also be prompted for which Networking "
 "plug-in to use. This will automatically fill the "
 "<option>core_plugin</option> directive in the "
 "<filename>/etc/neutron/neutron.conf</filename> file."
-msgstr ""
+msgstr "インストール中に、使用する Networking プラグインのプロンプトが表示されるでしょう。これにより、<filename>/etc/neutron/neutron.conf</filename> ファイルの <option>core_plugin</option> ディレクティブが自動的に埋められます。"
 
 #: ./doc/install-guide/section_neutron-ml2-controller-node.xml100(para)
 msgid ""
@@ -3177,7 +5786,7 @@ msgid ""
 "names for the plug-ins. The <option>service_plugins</option> and "
 "<option>allow_overlapping_ips</option> options are filled with the "
 "appropriate values by default, so it is fine to not touch them."
-msgstr ""
+msgstr "ML2 プラグインを選択した場合、<option>core_plugin</option> オプションは <literal>neutron.plugins.ml2.plugin.Ml2Plugin</literal> になります。これは、ML2 プラグインの完全クラス名です。Debian の場合、今のところプラグインの短縮名を使用できません。<option>service_plugins</option> と <option>allow_overlapping_ips</option> のオプションは、デフォルトで適切な値が入力されるため、変更しないほうがいいです。"
 
 #: ./doc/install-guide/section_neutron-ml2-controller-node.xml109(para)
 #: ./doc/install-guide/section_neutron-ml2-controller-node.xml116(para)
@@ -3196,84 +5805,6 @@ msgid ""
 "chose for the database."
 msgstr "<replaceable>NEUTRON_PASS</replaceable> をデータベース用に選んだパスワードで置き換えます。"
 
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml131(para)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml154(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml57(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml80(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml54(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml77(para)
-msgid "Configure Networking to use the Identity service for authentication:"
-msgstr "Networking が認証用に Identity Service を使用するよう設定します。"
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml133(para)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml166(para)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml370(para)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml404(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml59(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml92(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml56(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml89(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml288(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml322(para)
-msgid ""
-"Replace <replaceable>NEUTRON_PASS</replaceable> with the password you chose "
-"for the <literal>neutron</literal> user in the Identity service."
-msgstr "Identity で <literal>neutron</literal> ユーザー用に選択したパスワードで <replaceable>NEUTRON_PASS</replaceable> を置き換えます。"
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml158(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml84(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml81(para)
-msgid ""
-"Edit the <filename>/etc/neutron/neutron.conf</filename> file and add the "
-"following key to the <literal>[DEFAULT]</literal> section:"
-msgstr "<filename>/etc/neutron/neutron.conf</filename> ファイルを編集し、以下のキーを <literal>[DEFAULT]</literal> セクションに追加します。"
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml164(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml90(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml87(para)
-msgid ""
-"Add the following keys to the <literal>[keystone_authtoken]</literal> "
-"section:"
-msgstr "以下のキーを <literal>[keystone_authtoken]</literal> セクションに追加します。"
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml182(para)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml196(para)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml203(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml108(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml122(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml129(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml105(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml119(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml126(para)
-msgid "Configure Networking to use the message broker:"
-msgstr "Networking がメッセージブローカーを使用するよう設定します。"
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml183(para)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml209(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml109(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml135(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml106(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml132(para)
-#: ./doc/install-guide/section_glance-install.xml83(para)
-#: ./doc/install-guide/section_glance-install.xml96(para)
-msgid ""
-"Replace <replaceable>RABBIT_PASS</replaceable> with the password you chose "
-"for the <literal>guest</literal> account in "
-"<application>RabbitMQ</application>."
-msgstr "<replaceable>RABBIT_PASS</replaceable> を <application>RabbitMQ</application> の <literal>guest</literal> アカウント用に選んだパスワードで置き換えます。"
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml206(para)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml248(para)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml296(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml132(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml165(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml129(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml162(para)
-msgid ""
-"Edit the <filename>/etc/neutron/neutron.conf</filename> file and add the "
-"following keys to the <literal>[DEFAULT]</literal> section:"
-msgstr "<filename>/etc/neutron/neutron.conf</filename> ファイルを編集し、以下のキーを <literal>[DEFAULT]</literal> セクションに追加します。"
-
 #: ./doc/install-guide/section_neutron-ml2-controller-node.xml221(para)
 #: ./doc/install-guide/section_neutron-ml2-controller-node.xml239(para)
 msgid "Configure Networking to notify Compute about network topology changes:"
@@ -3295,43 +5826,6 @@ msgstr "SERVICE_TENANT_ID"
 msgid "To obtain the <literal>service</literal> tenant identifier (id):"
 msgstr "<literal>service</literal> テナント ID の取得方法:"
 
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml278(para)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml292(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml147(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml161(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml144(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml158(para)
-msgid ""
-"Configure Networking to use the Modular Layer 2 (ML2) plug-in and associated"
-" services:"
-msgstr "Modular Layer 2 (ML2) プラグインと関連サービスを使用するよう Networking を設定します。"
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml285(para)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml305(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml154(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml174(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml151(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml171(para)
-msgid ""
-"We recommend adding <literal>verbose = True</literal> to the "
-"<literal>[DEFAULT]</literal> section in "
-"<filename>/etc/neutron/neutron.conf</filename> to assist with "
-"troubleshooting."
-msgstr "トラブルシューティングに役立てるため、<filename>/etc/neutron/neutron.conf</filename> の <literal>[DEFAULT]</literal> セクションに <literal>verbose = True</literal> を追加することを推奨します。"
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml314(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml183(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml180(para)
-msgid ""
-"Comment out any lines in the <literal>[service_providers]</literal> section."
-msgstr "<literal>[service_providers]</literal> セクションのすべての行をコメントアウトします。"
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml319(title)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml351(title)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml185(title)
-msgid "To configure the Modular Layer 2 (ML2) plug-in"
-msgstr "ML2 プラグインの設定方法"
-
 #: ./doc/install-guide/section_neutron-ml2-controller-node.xml320(para)
 msgid ""
 "The ML2 plug-in uses the Open vSwitch (OVS) mechanism (agent) to build the "
@@ -3340,61 +5834,11 @@ msgid ""
 "network traffic."
 msgstr "ML2 プラグインは、インスタンスの仮想ネットワークフレームワークを構築するために、Open vSwitch 機能 (エージェント) を使用します。しかしながら、コントローラーノードはインスタンスのネットワーク通信を処理しないため、OVS エージェントやサービスが必要ありません。"
 
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml340(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml217(para)
-msgid ""
-"Edit the <filename>/etc/neutron/plugins/ml2/ml2_conf.ini</filename> file:"
-msgstr "<filename>/etc/neutron/plugins/ml2/ml2_conf.ini</filename> ファイルを編集します。"
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml343(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml386(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml220(para)
-msgid "Add the following keys to the <literal>[ml2]</literal> section:"
-msgstr "以下のキーを <literal>[ml2]</literal> セクションに追加します。"
-
 #: ./doc/install-guide/section_neutron-ml2-controller-node.xml350(para)
 msgid ""
 "Add the following key to the <literal>[ml2_type_gre]</literal> section:"
 msgstr "以下のキーを <literal>[ml2_type_gre]</literal> セクションに追加します。"
 
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml355(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml409(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml243(para)
-msgid ""
-"Add the <literal>[securitygroup]</literal> section and the following keys to"
-" it:"
-msgstr "<literal>[securitygroup]</literal> セクションを追加し、そこに以下のキーを追加します。"
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml364(title)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml282(title)
-msgid "To configure Compute to use Networking"
-msgstr "Networking を使用するための Compute の設定方法"
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml365(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml283(para)
-msgid ""
-"By default, most distributions configure Compute to use legacy networking. "
-"You must reconfigure Compute to manage networks through Networking."
-msgstr "多くのディストリビューションは標準で、レガシーネットワークを使用するよう Compute を設定します。Networking からネットワークを管理するよう、Compute を再設定する必要があります。"
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml394(para)
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml420(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml312(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml338(para)
-msgid ""
-"By default, Compute uses an internal firewall service. Since Networking "
-"includes a firewall service, you must disable the Compute firewall service "
-"by using the <literal>nova.virt.firewall.NoopFirewallDriver</literal> "
-"firewall driver."
-msgstr "デフォルトで、Compute は内部ファイアウォールサービスを使用します。Networking がファイアウォールサービスを含むため、<literal>nova.virt.firewall.NoopFirewallDriver</literal> ファイアウォールドライバーを使用して、Compute のファイアウォールサービスを無効化する必要があります。"
-
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml402(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml320(para)
-msgid ""
-"Edit the <filename>/etc/nova/nova.conf</filename> and add the following keys"
-" to the <literal>[DEFAULT]</literal> section:"
-msgstr "<filename>/etc/nova/nova.conf</filename> ファイルを編集し、以下のキーを <literal>[DEFAULT]</literal> セクションに追加します。"
-
 #: ./doc/install-guide/section_neutron-ml2-controller-node.xml429(title)
 #: ./doc/install-guide/section_basics-queue.xml96(title)
 msgid "To finalize installation"
@@ -3419,12 +5863,6 @@ msgid ""
 "<filename>/etc/sysconfig/neutron</filename> file and add the following:"
 msgstr "Networking のサービス初期化スクリプトは、<filename>/etc/sysconfig/neutron</filename> ファイルの <literal>NEUTRON_PLUGIN_CONF</literal> 変数が、使用するプラグインに関連する設定ファイルを参照していることを想定します。例えば、ML2 を使用する場合、<filename>/etc/sysconfig/neutron</filename> ファイルを編集し、以下を追加します。"
 
-#: ./doc/install-guide/section_neutron-ml2-controller-node.xml451(para)
-#: ./doc/install-guide/section_neutron-ovs-controller-node.xml331(para)
-#: ./doc/install-guide/section_nova-networking-controller-node.xml26(para)
-msgid "Restart the Compute services:"
-msgstr "Compute のサービスを再起動します。"
-
 #: ./doc/install-guide/section_neutron-ml2-controller-node.xml460(para)
 #: ./doc/install-guide/section_neutron-ovs-controller-node.xml337(para)
 msgid ""
@@ -3436,412 +5874,159 @@ msgstr "Networking サービスを起動し、システム起動時に起動す
 msgid "Restart the Networking service:"
 msgstr "Networking のサービスを再起動します。"
 
-#: ./doc/install-guide/section_keystone-services.xml4(title)
-msgid "Define services and API endpoints"
-msgstr "サービスと API エンドポイントの定義"
+#: ./doc/install-guide/section_launch-instance-neutron.xml6(title)
+msgid "Launch an instance with OpenStack Networking (neutron)"
+msgstr "OpenStack Networking (neutron) を用いたインスタンスの起動"
 
-#: ./doc/install-guide/section_keystone-services.xml5(para)
+#: ./doc/install-guide/section_launch-instance-neutron.xml95(para)
 msgid ""
-"So that the Identity Service can track which OpenStack services are "
-"installed and where they are located on the network, you must register each "
-"service in your OpenStack installation. To register a service, run these "
-"commands:"
-msgstr "Identity Service が、どの OpenStack サービスがインストールされているか、それらがネットワークのどこにあるかを追跡できるよう、OpenStack インストール環境の各サービスを登録する必要があります。サービスを登録するために、これらのコマンドを実行します。"
+"Your first instance uses the <literal>default</literal> security group. By "
+"default, this security group implements a firewall that blocks remote access"
+" to instances. If you would like to permit remote access to your instance, "
+"launch it and then <link linkend=\"launch-instance-neutron-remoteaccess\"> "
+"configure remote access</link>."
+msgstr "初めてのインスタンスは、<literal>default</literal> セキュリティグループを使用します。デフォルトで、このセキュリティグループは、インスタンスへのリモートアクセスを遮断するファイアウォールを適用します。インスタンスへのリモートアクセスを許可したければ、インスタンスを起動し、<link linkend=\"launch-instance-neutron-remoteaccess\">リモートアクセスを設定</link>します。"
 
-#: ./doc/install-guide/section_keystone-services.xml11(para)
-msgid "<placeholder-1/>. Describes the service."
-msgstr "<placeholder-1/>。サービスを定義します。"
+#: ./doc/install-guide/section_launch-instance-neutron.xml173(para)
+msgid "Verify the <literal>demo-net</literal> tenant network gateway:"
+msgstr "<literal>demo-net</literal> テナントネットワークのゲートウェイを検証します。"
 
-#: ./doc/install-guide/section_keystone-services.xml15(para)
+#: ./doc/install-guide/section_launch-instance-neutron.xml185(para)
+msgid "Verify the <literal>ext-net</literal> external network:"
+msgstr "<literal>ext-net</literal> 外部ネットワークを検証します。"
+
+#: ./doc/install-guide/section_launch-instance-neutron.xml224(para)
 msgid ""
-"<placeholder-1/>. Associates <glossterm baseform=\"API endpoint\">API "
-"endpoints</glossterm> with the service."
-msgstr "<placeholder-1/>。<glossterm baseform=\"API endpoint\">API エンドポイント</glossterm>とサービスを関連付けます。"
+"Create a <glossterm>floating IP address</glossterm> on the <literal>ext-"
+"net</literal> external network:"
+msgstr "<literal>ext-net</literal> 外部ネットワークに <glossterm baseform=\"floating IP address\">Floating IP アドレス</glossterm> を作成します。"
 
-#: ./doc/install-guide/section_keystone-services.xml20(para)
+#: ./doc/install-guide/section_launch-instance-neutron.xml242(para)
+msgid "Associate the floating IP address with your instance:"
+msgstr "Floating IP アドレスをインスタンスに割り当てます。"
+
+#: ./doc/install-guide/section_launch-instance-neutron.xml249(para)
+msgid "Check the status of your floating IP address:"
+msgstr "Floating IP アドレスの状態を確認します。"
+
+#: ./doc/install-guide/ch_glance.xml6(title)
+msgid "Add the Image Service"
+msgstr "Image Service の追加"
+
+#: ./doc/install-guide/ch_glance.xml7(para)
 msgid ""
-"You must also register the Identity Service itself. Use the "
-"<code>OS_SERVICE_TOKEN</code> environment variable, as set previously, for "
-"authentication."
-msgstr "Identity Service 自身も登録する必要があります。前に設定した <code>OS_SERVICE_TOKEN</code> 環境変数を認証のために使用します。"
+"The OpenStack Image Service (glance) enables users to discover, register, "
+"and retrieve virtual machine images. It offers a <glossterm "
+"baseform=\"RESTful\">REST</glossterm> API that enables you to query virtual "
+"machine image metadata and retrieve an actual image. You can store virtual "
+"machine images made available through the Image Service in a variety of "
+"locations, from simple file systems to object-storage systems like OpenStack"
+" Object Storage."
+msgstr "OpenStack Image Service (glance) により、ユーザーが仮想マシンイメージを検索、登録、取得できるようになります。仮想マシンイメージを問い合わせ、実際のイメージを取得できるよう、<glossterm baseform=\"RESTful\">REST</glossterm> API を提供します。Image Service 経由で利用可能な仮想マシンイメージは、単なるファイルシステムから OpenStack Object Storage のようなオブジェクトストレージシステムまで、さまざまな場所に保存できます。"
 
-#: ./doc/install-guide/section_keystone-services.xml25(para)
-msgid "Create a service entry for the Identity Service:"
-msgstr "Identity Service のサービスエントリーを作成します。"
-
-#: ./doc/install-guide/section_keystone-services.xml36(para)
-#: ./doc/install-guide/object-storage/section_object-storage-install.xml89(para)
+#: ./doc/install-guide/ch_glance.xml15(para)
 msgid ""
-"The service ID is randomly generated and is different from the one shown "
-"here."
-msgstr "サービス ID はランダムに生成され、ここに表示されているものとは異なります。"
+"For simplicity, this guide describes configuring the Image Service to use "
+"the <literal>file</literal> back end, which uploads and stores in a "
+"directory on the controller node hosting the Image Service. By default, this"
+" directory is <filename>/var/lib/glance/images/</filename>."
+msgstr "簡単のため、このガイドは Image Service が <literal>file</literal> バックエンドを使用するよう設定します。これは、Image Service をホストしているシステムにあるディレクトリにアップロードされ、保存されることを意味します。このディレクトリはデフォルトで <filename>/var/lib/glance/images/</filename> です。"
 
-#: ./doc/install-guide/section_keystone-services.xml40(para)
+#: ./doc/install-guide/ch_glance.xml20(para)
 msgid ""
-"Specify an API endpoint for the Identity Service by using the returned "
-"service ID. When you specify an endpoint, you provide URLs for the public "
-"API, internal API, and admin API. In this guide, the "
-"<literal>controller</literal> host name is used. Note that the Identity "
-"Service uses a different port for the admin API."
-msgstr "返されたサービス ID を使用することにより、Identity Service の API エンドポイントを指定します。エンドポイントを指定するとき、パブリック API、内部 API、管理 API の URL を指定します。このガイドでは、<literal>controller</literal> というホスト名を使用します。Identity Service は管理 API 用に異なるポートを使用することに注意してください。"
+"Before you proceed, ensure that the controller node has at least several "
+"gigabytes of space available in this directory."
+msgstr "続行する前に、コントローラーノードがこのディレクトリに少なくとも数ギガバイトの空き容量を持っていることを確認します。"
 
-#: ./doc/install-guide/section_keystone-services.xml63(para)
+#: ./doc/install-guide/ch_glance.xml22(para)
 msgid ""
-"You will need to create an additional endpoint for each service added to "
-"your OpenStack environment. The sections of this guide associated with the "
-"installation of each service include the endpoint creation step specific to "
-"the service."
-msgstr "お使いの OpenStack 環境に追加した各サービス用の追加のエンドポイントを作成することが必要になります。各サービスのインストールと関連したこのガイドのセクションに、サービスへのエンドポイントの具体的な作成手順があります。"
+"For information on requirements for other back ends, see <link "
+"href=\"http://docs.openstack.org/trunk/config-reference/content"
+"/ch_configuring-openstack-image-service.html\"><citetitle>Configuration "
+"Reference</citetitle></link>."
+msgstr "他のバックエンドの要件は、<link href=\"http://docs.openstack.org/trunk/config-reference/content/ch_configuring-openstack-image-service.html\"><citetitle>設定リファレンス</citetitle></link>を参照してください。"
 
-#: ./doc/install-guide/section_keystone-verify.xml6(title)
-msgid "Verify the Identity Service installation"
-msgstr "Identity Service のインストールの検証"
+#: ./doc/install-guide/section_basics-prerequisites.xml6(title)
+#: ./doc/install-guide/object-storage/section_object-storage-install.xml28(title)
+msgid "Before you begin"
+msgstr "始める前に"
 
-#: ./doc/install-guide/section_keystone-verify.xml9(para)
+#: ./doc/install-guide/section_basics-prerequisites.xml7(para)
 msgid ""
-"To verify that the Identity Service is installed and configured correctly, "
-"clear the values in the <envar>OS_SERVICE_TOKEN</envar> and "
-"<envar>OS_SERVICE_ENDPOINT</envar> environment variables:"
-msgstr "Identity Service が正しくインストールされ、設定されていることを確認するためには、<envar>OS_SERVICE_TOKEN</envar> 環境変数と <envar>OS_SERVICE_ENDPOINT</envar> 環境変数にある値を削除します。"
+"For a functional environment, OpenStack doesn't require a significant amount"
+" of resources. We recommend that your environment meets or exceeds the "
+"following minimum requirements which can support several minimal "
+"<glossterm>CirrOS</glossterm> instances:"
+msgstr "機能検証環境の場合、OpenStack はあまりリソースを必要としません。いくつかの最小の <glossterm>CirrOS</glossterm> インスタンスをサポートできる、以下の最小要件を満たすことを推奨します。"
 
-#: ./doc/install-guide/section_keystone-verify.xml15(para)
+#: ./doc/install-guide/section_basics-prerequisites.xml13(para)
+msgid "Controller Node: 1 processor, 2 GB memory, and 5 GB storage"
+msgstr "コントローラーノード: 1 CPU、2 GB メモリ、5 GB ストレージ"
+
+#: ./doc/install-guide/section_basics-prerequisites.xml17(para)
+msgid "Network Node: 1 processor, 512 MB memory, and 5 GB storage"
+msgstr "ネットワークノード: 1 CPU、512 MB メモリ、5 GB ストレージ"
+
+#: ./doc/install-guide/section_basics-prerequisites.xml21(para)
+msgid "Compute Node: 1 processor, 2 GB memory, and 10 GB storage"
+msgstr "コンピュートノード: 1 CPU、2 GB メモリ、10 GB ストレージ"
+
+#: ./doc/install-guide/section_basics-prerequisites.xml25(para)
 msgid ""
-"These variables, which were used to bootstrap the administrative user and "
-"register the Identity Service, are no longer needed."
-msgstr "管理ユーザーをブートストラップし、Identity Service に登録するために使用された、これらの変数はもはや必要ありません。"
+"To minimize clutter and provide more resources for OpenStack, we recommend a"
+" minimal installation of your Linux distribution. Also, we strongly "
+"recommend that you install a 64-bit version of your distribution on at least"
+" the compute node. If you install a 32-bit version of your distribution on "
+"the compute node, attempting to start an instance using a 64-bit image will "
+"fail."
+msgstr "散らかりを最小化し、OpenStack のためによりリソースを提供するために、Linux ディストリビューションの最小インストールを推奨します。また、少なくともコンピュートノードは、ディストリビューションの 64 ビット版のインストールを強く推奨します。コンピュートノードにディストリビューションの 32 ビット版をインストールする場合、64 ビット版のイメージを使用したインスタンスの起動に失敗します。"
 
-#: ./doc/install-guide/section_keystone-verify.xml20(para)
-msgid "You can now use regular user name-based authentication."
-msgstr "これで通常のユーザー名による認証を使用できます。"
-
-#: ./doc/install-guide/section_keystone-verify.xml22(para)
+#: ./doc/install-guide/section_basics-prerequisites.xml32(para)
 msgid ""
-"Request a authentication token by using the <literal>admin</literal> user "
-"and the password you chose for that user:"
-msgstr "<literal>admin</literal> ユーザーと、そのユーザー用に選択したパスワードを使用して認証トークンを要求します。"
+"A single disk partition on each node works for most basic installations. "
+"However, you should consider <glossterm>Logical Volume Manager "
+"(LVM)</glossterm> for installations with optional services such as Block "
+"Storage."
+msgstr "最も基本的なインストールの場合、各ノードで単一のディスクパーティションが動作します。しかしながら、Block Storage のようなオプションサービスのインストールに <glossterm>Logical Volume Manager (LVM)</glossterm> を検討すべきです。"
 
-#: ./doc/install-guide/section_keystone-verify.xml27(para)
+#: ./doc/install-guide/section_basics-prerequisites.xml37(para)
 msgid ""
-"In response, you receive a token paired with your user ID. This verifies "
-"that the Identity Service is running on the expected endpoint and that your "
-"user account is established with the expected credentials."
-msgstr "応答で、ユーザー ID とペアになったトークンを受け取ります。これにより、Identity Service が期待したエンドポイントで実行されていて、ユーザーアカウントが期待したクレデンシャルで確立されていることを検証できます。"
+"Many users build their test environments on <glossterm baseform=\"virtual "
+"machine (VM)\">virtual machines (VMs)</glossterm>. The primary benefits of "
+"VMs include the following:"
+msgstr "多くのユーザーは、<glossterm baseform=\"virtual machine (VM)\">仮想マシン (VM)</glossterm> にテスト環境を構築します。仮想マシンの主な利点は以下のとおりです。"
 
-#: ./doc/install-guide/section_keystone-verify.xml33(para)
+#: ./doc/install-guide/section_basics-prerequisites.xml43(para)
 msgid ""
-"Verify that authorization behaves as expected. To do so, request "
-"authorization on a tenant:"
-msgstr "認可が期待したとおり動作することを検証します。そうするために、プロジェクトで認可を要求します。"
+"One physical server can support multiple nodes, each with almost any number "
+"of network interfaces."
+msgstr "1 台の物理サーバーが複数のノードをサポートできます。それぞれ複数のネットワークインターフェースを持てます。"
 
-#: ./doc/install-guide/section_keystone-verify.xml38(para)
+#: ./doc/install-guide/section_basics-prerequisites.xml47(para)
 msgid ""
-"In response, you receive a token that includes the ID of the tenant that you"
-" specified. This verifies that your user account has an explicitly defined "
-"role on the specified tenant and the tenant exists as expected."
-msgstr "応答で、指定したプロジェクトの ID を含むトークンを受け取ります。これにより、ユーザーアカウントが指定したプロジェクトで明示的に定義したロールを持ち、プロジェクトが期待したとおりに存在することを検証します。"
+"Ability to take periodic \"snap shots\" throughout the installation process "
+"and \"roll back\" to a working configuration in the event of a problem."
+msgstr "インストールプロセス以降、定期的な「スナップショット」を取得する機能、および問題発生時に動作する設定に「ロールバック」する機能があります。"
 
-#: ./doc/install-guide/section_keystone-verify.xml44(para)
+#: ./doc/install-guide/section_basics-prerequisites.xml52(para)
 msgid ""
-"You can also set your <literal>--os-*</literal> variables in your "
-"environment to simplify command-line usage. Set up a <filename>admin-"
-"openrc.sh</filename> file with the admin credentials and admin endpoint:"
-msgstr "コマンドラインの使用を簡単にするために、お使いの環境で <literal>--os-*</literal> 変数を設定することもできます。admin クレデンシャルと admin エンドポイントを用いて <filename>admin-openrc.sh</filename> ファイルをセットアップします。"
+"However, VMs will reduce performance of your instances, particularly if your"
+" hypervisor and/or processor lacks support for hardware acceleration of "
+"nested VMs."
+msgstr "しかしながら、仮想マシンはインスタンスのパフォーマンスを劣化させます。とくに、ハイパーバイザーとプロセッサーがネステッド仮想マシンのハードウェア支援機能をサポートしない場合です。"
 
-#: ./doc/install-guide/section_keystone-verify.xml54(para)
-msgid "Source this file to read in the environment variables:"
-msgstr "環境変数を読み込むために、このファイルを source します。"
-
-#: ./doc/install-guide/section_keystone-verify.xml59(para)
+#: ./doc/install-guide/section_basics-prerequisites.xml56(para)
 msgid ""
-"Verify that your <filename>admin-openrc.sh</filename> file is configured "
-"correctly. Run the same command without the <literal>--os-*</literal> "
-"arguments:"
-msgstr "<filename>admin-openrc.sh</filename> ファイルが正しく設定されていることを検証します。同じコマンドを <literal>--os-*</literal> 引数なしで実行します。"
+"If you choose to install on VMs, make sure your hypervisor permits "
+"<glossterm>promiscuous mode</glossterm> on the <glossterm>external "
+"network</glossterm>."
+msgstr "仮想マシンにインストールする場合、お使いのハイパーバイザーが<glossterm baseform=\"external network\">外部ネットワーク</glossterm>で<glossterm baseform=\"promiscuous mode\">プロミスキャスモード</glossterm>を許可することを確認します。"
 
-#: ./doc/install-guide/section_keystone-verify.xml63(para)
+#: ./doc/install-guide/section_basics-prerequisites.xml60(para)
 msgid ""
-"The command returns a token and the ID of the specified tenant. This "
-"verifies that you have configured your environment variables correctly."
-msgstr "コマンドはトークンと指定されたプロジェクトの ID を返します。これにより、環境変数が正しく設定されていることを確認します。"
-
-#: ./doc/install-guide/section_keystone-verify.xml68(para)
-msgid ""
-"Verify that your admin account has authorization to perform administrative "
-"commands:"
-msgstr "admin アカウントが管理コマンドを実行する権限があることを検証します。"
-
-#: ./doc/install-guide/section_keystone-verify.xml85(para)
-msgid ""
-"Seeing that the <literal>id</literal> in the output from the "
-"<placeholder-1/> command matches the <literal>user_id</literal> in the "
-"<placeholder-2/> command, and that the admin role is listed for that user, "
-"for the related tenant, this verifies that your user account has the "
-"<literal>admin</literal> role, which matches the role used in the Identity "
-"Service <filename>policy.json</filename> file."
-msgstr "<placeholder-1/> コマンドの出力の <literal>id</literal> が <placeholder-2/> コマンドの <literal>user_id</literal> と同じであること、admin ロールがそのユーザー、その関連プロジェクトに対して表示されることを確認します。これにより、お使いのユーザーアカウントが <literal>admin</literal> ロールを持つことを確認します。このロールは Identity Service の <filename>policy.json</filename> ファイルで使用されるロールと対応します。"
-
-#: ./doc/install-guide/section_keystone-verify.xml95(para)
-msgid ""
-"As long as you define your credentials and the Identity Service endpoint "
-"through the command line or environment variables, you can run all OpenStack"
-" client commands from any machine. For details, see <xref "
-"linkend=\"ch_clients\"/>."
-msgstr "コマンドラインや環境変数経由でクレデンシャルと Identity Service エンドポイントを定義する限り、すべてのマシンからすべての OpenStack クライアントコマンドを実行できます。詳細は <xref linkend=\"ch_clients\"/> を参照してください。"
-
-#: ./doc/install-guide/ch_networking.xml6(title)
-msgid "Add a networking service"
-msgstr "Networking Service の追加"
-
-#: ./doc/install-guide/ch_networking.xml7(para)
-msgid ""
-"Configuring networking in OpenStack can be a bewildering experience. This "
-"guide provides step-by-step instructions for both OpenStack Networking "
-"(neutron) and the legacy networking (nova-network) service. If you are "
-"unsure which to use, we recommend trying OpenStack Networking because it "
-"offers a considerable number of features and flexibility including "
-"<glossterm baseform=\"plug-in\">plug-ins</glossterm> for a variety of "
-"emerging products supporting <glossterm>virtual networking</glossterm>. See "
-"the <link href=\"http://docs.openstack.org/admin-guide-"
-"cloud/content/ch_networking.html\">Networking</link> chapter of the "
-"<citetitle>OpenStack Cloud Administrator Guide</citetitle> for more "
-"information."
-msgstr "OpenStack でネットワークを設定することは、目の回るような経験になる可能性があります。このガイドは、OpenStack Networking (neutron) とレガシーネットワーク (nova-network) の両方をステップバイステップで説明します。どちらを使用するか決めていない場合、OpenStack Networking を試してみることを推奨します。これは、かなり数多くの機能を持ち、<glossterm baseform=\"virtual networking\">仮想ネットワーク</glossterm>をサポートするさまざまな最新製品向けの<glossterm baseform=\"plug-in\">プラグイン</glossterm>などの柔軟性があります。詳細は、<citetitle>OpenStack Cloud Administrator Guide</citetitle> の <link href=\"http://docs.openstack.org/admin-guide-cloud/content/ch_networking.html\">Networking</link> を参照してください。"
-
-#: ./doc/install-guide/ch_networking.xml20(title)
-#: ./doc/install-guide/section_basics-networking-neutron.xml6(title)
-msgid "OpenStack Networking (neutron)"
-msgstr "OpenStack Networking (neutron)"
-
-#: ./doc/install-guide/ch_networking.xml23(title)
-msgid "Modular Layer 2 (ML2) plug-in"
-msgstr "Modular Layer 2 (ML2) プラグイン"
-
-#: ./doc/install-guide/ch_networking.xml31(title)
-#: ./doc/install-guide/section_basics-networking-nova.xml6(title)
-msgid "Legacy networking (nova-network)"
-msgstr "レガシーネットワーク (nova-network)"
-
-#: ./doc/install-guide/ch_networking.xml38(para)
-msgid ""
-"Your OpenStack environment now includes the core components necessary to "
-"launch a basic instance. You can <link linkend=\"launch-instance\">launch an"
-" instance</link> or add more services to your environment in the following "
-"chapters."
-msgstr "基本的なインスタンスを起動するために必要なコンポーネントが OpenStack 環境に追加されました。<link linkend=\"launch-instance\">インスタンスの起動</link>、移行の章に記載されているサービスの環境への追加を実行できます。"
-
-#: ./doc/install-guide/ch_horizon.xml6(title)
-msgid "Add the dashboard"
-msgstr "Dashboard の追加"
-
-#: ./doc/install-guide/ch_horizon.xml7(para)
-msgid ""
-"The OpenStack dashboard, also known as <link "
-"href=\"https://github.com/openstack/horizon/\">Horizon</link>, is a Web "
-"interface that enables cloud administrators and users to manage various "
-"OpenStack resources and services."
-msgstr "OpenStack Dashboard は <link href=\"https://github.com/openstack/horizon/\">Horizon</link> としても知られ、クラウド管理者やユーザーがさまざまな OpenStack のリソースとサービスを管理できるようになるウェブインターフェースです。"
-
-#: ./doc/install-guide/ch_horizon.xml12(para)
-msgid ""
-"The dashboard enables web-based interactions with the OpenStack Compute "
-"cloud controller through the OpenStack APIs."
-msgstr "Dashboard は OpenStack API を経由して OpenStack Compute クラウドコントローラーとウェブベースで操作できます。"
-
-#: ./doc/install-guide/ch_horizon.xml15(para)
-msgid ""
-"These instructions show an example deployment configured with an Apache web "
-"server."
-msgstr "ここからの説明は Apache ウェブサーバーを用いて設定する導入例を示します。"
-
-#: ./doc/install-guide/ch_horizon.xml17(para)
-msgid ""
-"After you <link linkend=\"install_dashboard\">install and configure the "
-"dashboard</link>, you can complete the following tasks:"
-msgstr "<link linkend=\"install_dashboard\">Dashboard のインストールと設定</link>をした後、以下の作業を完了できます。"
-
-#: ./doc/install-guide/ch_horizon.xml22(para)
-msgid ""
-"Customize your dashboard. See section <link href=\"http://docs.openstack.org"
-"/admin-guide-cloud/content/ch_install-dashboard.html#dashboard-custom-"
-"brand\">Customize the dashboard</link> in the <link "
-"href=\"http://docs.openstack.org/admin-guide-"
-"cloud/content/\"><citetitle>OpenStack Cloud Administrator "
-"Guide</citetitle></link>."
-msgstr "Dashboard のカスタマイズ。<link href=\"http://docs.openstack.org/admin-guide-cloud/content/\"><citetitle>OpenStack クラウド管理者ガイド</citetitle></link>の <link href=\"http://docs.openstack.org/admin-guide-cloud/content/ch_install-dashboard.html#dashboard-custom-brand\">Dashboard のカスタマイズ</link>セクション参照。"
-
-#: ./doc/install-guide/ch_horizon.xml30(para)
-msgid ""
-"Set up session storage for the dashboard. See <xref linkend=\"dashboard-"
-"sessions\"/>."
-msgstr "Dashboard 用セッションストレージのセットアップ。<xref linkend=\"dashboard-sessions\"/> 参照。"
-
-#: ./doc/install-guide/ch_horizon.xml39(para)
-msgid ""
-"Your OpenStack environment now includes the dashboard. You can <link linkend"
-"=\"launch-instance\">launch an instance</link> or add more services to your "
-"environment in the following chapters."
-msgstr "OpenStack 環境にダッシュボードが追加されました。<link linkend=\"launch-instance\">インスタンスの起動</link>、以降の章に記載されているサービスの環境への追加を実行できます。"
-
-#: ./doc/install-guide/section_heat-verify.xml6(title)
-msgid "Verify the Orchestration service installation"
-msgstr "Orchestration Service のインストールの検証"
-
-#: ./doc/install-guide/section_heat-verify.xml8(para)
-msgid ""
-"To verify that the Orchestration service is installed and configured "
-"correctly, make sure that your credentials are set up correctly in the "
-"<filename>demo-openrc.sh</filename> file. Source the file, as follows:"
-msgstr "Orchestration Service が正しくインストールされ、設定されていることを検証するために、クレデンシャルが <filename>demo-openrc.sh</filename> ファイルに正しくセットアップされていることを確認します。このファイルを以下のように読み込みます。"
-
-#: ./doc/install-guide/section_heat-verify.xml14(para)
-msgid ""
-"The Orchestration Module uses templates to describe stacks. To learn about "
-"the template languages, see <link "
-"href=\"http://docs.openstack.org/developer/heat/template_guide/index.html\">the"
-" Template Guide</link> in the <link "
-"href=\"http://docs.openstack.org/developer/heat/\">Heat developer "
-"documentation</link>."
-msgstr "Orchestration モジュールは、スタックを記載するためにテンプレートを使用します。テンプレート言語を学習するために、<link href=\"http://docs.openstack.org/developer/heat/\">Heat 開発者ドキュメント</link>の <link href=\"http://docs.openstack.org/developer/heat/template_guide/index.html\">Template Guide</link> を参照してください。"
-
-#: ./doc/install-guide/section_heat-verify.xml20(para)
-msgid ""
-"Create a test template in the <filename>test-stack.yml</filename> file with "
-"the following content:"
-msgstr "以下の内容を持つ <filename>test-stack.yml</filename> ファイルにテストテンプレートを作成します。"
-
-#: ./doc/install-guide/section_heat-verify.xml24(para)
-msgid "Use the <placeholder-1/> command to create a stack from this template:"
-msgstr "このテンプレートからスタックを作成するために <placeholder-1/> コマンドを使用します。"
-
-#: ./doc/install-guide/section_heat-verify.xml35(para)
-msgid ""
-"Verify that the stack was created successfully with the <placeholder-1/> "
-"command:"
-msgstr "<placeholder-1/> コマンドを用いて、スタックが正常に作成されたことを検証します。"
-
-#: ./doc/install-guide/ch_ceilometer.xml6(title)
-msgid "Add the Telemetry module"
-msgstr "Telemetry モジュールの追加"
-
-#: ./doc/install-guide/ch_ceilometer.xml7(para)
-msgid ""
-"Telemetry provides a framework for monitoring and metering the OpenStack "
-"cloud. It is also known as the ceilometer project."
-msgstr "Telemetry は OpenStack クラウドのモニタリングとメータリングのフレームワークを提供します。これは Ceilometer プロジェクトとしても知られています。"
-
-#: ./doc/install-guide/ch_ceilometer.xml19(para)
-msgid ""
-"Your OpenStack environment now includes Telemetry. You can <link linkend"
-"=\"launch-instance\">launch an instance</link> or add more services to your "
-"environment in the previous chapters."
-msgstr "OpenStack 環境に Telemetryが追加されました。<link linkend=\"launch-instance\">インスタンスの起動</link>、以前の章に記載されているサービスの環境への追加を実行できます。"
-
-#: ./doc/install-guide/ch_keystone.xml6(title)
-msgid "Configure the Identity Service"
-msgstr "Identity Service の設定"
-
-#: ./doc/install-guide/ch_heat.xml6(title)
-msgid "Add the Orchestration service"
-msgstr "Orchestration Service の追加"
-
-#: ./doc/install-guide/ch_heat.xml7(para)
-msgid ""
-"Use the Orchestration module to create cloud resources using a template "
-"language called HOT. The integrated project name is Heat."
-msgstr "HOT と呼ばれるテンプレート言語を使用してクラウドリソースを作成するために Orchestration モジュールを使用します。統合プロジェクト名は Heat です。"
-
-#: ./doc/install-guide/ch_heat.xml15(para)
-msgid ""
-"Your OpenStack environment now includes Orchestration. You can <link linkend"
-"=\"launch-instance\">launch an instance</link> or add more services to your "
-"environment in the following chapters."
-msgstr "OpenStack 環境に Orchestration が追加されました。<link linkend=\"launch-instance\">インスタンスの起動</link>、以降の章に記載されているサービスの環境への追加を実行できます。"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-rabbitqm.xml15(None)
-msgid ""
-"@@image: 'figures/debconf-screenshots/rabbitmq-host.png'; "
-"md5=5353ad857884a2d31847cf82efbdc6b6"
-msgstr "@@image: 'figures/debconf-screenshots/rabbitmq-host.png'; md5=5353ad857884a2d31847cf82efbdc6b6"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-rabbitqm.xml22(None)
-msgid ""
-"@@image: 'figures/debconf-screenshots/rabbitmq-user.png'; "
-"md5=33a3c1182e79ed65f1b1b63f2156792c"
-msgstr "@@image: 'figures/debconf-screenshots/rabbitmq-user.png'; md5=33a3c1182e79ed65f1b1b63f2156792c"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-rabbitqm.xml29(None)
-msgid ""
-"@@image: 'figures/debconf-screenshots/rabbitmq-password.png'; "
-"md5=6385185200d20e96b6316ae15ae1255d"
-msgstr "@@image: 'figures/debconf-screenshots/rabbitmq-password.png'; md5=6385185200d20e96b6316ae15ae1255d"
-
-#: ./doc/install-guide/section_debconf-rabbitqm.xml6(title)
-msgid "RabbitMQ credentials parameters"
-msgstr "RabbitMQ クレデンシャルパラメーター"
-
-#: ./doc/install-guide/section_debconf-rabbitqm.xml7(para)
-msgid ""
-"For every package that must connect to a Messaging Server, the Debian "
-"package enables you to configure the IP address for that server and the user"
-" name and password that is used to connect. The following example shows "
-"configuration with the <systemitem class=\"service\">ceilometer-"
-"common</systemitem> package:"
-msgstr "メッセージングサーバーに接続する必要があるすべてのパッケージの場合には、Debian パッケージにより、そのサーバーの IP アドレス、接続するために使用されるユーザー名とパスワードを設定できます。以下の例は <systemitem class=\"service\">ceilometer-common</systemitem> を用いた設定を示します。"
-
-#: ./doc/install-guide/section_debconf-rabbitqm.xml33(para)
-msgid ""
-"These debconf screens appear in: <systemitem class=\"service\">ceilometer-"
-"common</systemitem>, <systemitem class=\"service\">cinder-"
-"common</systemitem>, <systemitem class=\"service\">glance-"
-"common</systemitem>, <systemitem class=\"service\">heat-common</systemitem>,"
-" <systemitem class=\"service\">neutron-common</systemitem> and <systemitem "
-"class=\"service\">nova-common</systemitem>."
-msgstr "これらの debconf 画面が次のもので表示されます。<systemitem class=\"service\">ceilometer-common</systemitem>、<systemitem class=\"service\">cinder-common</systemitem>、<systemitem class=\"service\">glance-common</systemitem>、<systemitem class=\"service\">heat-common</systemitem>、<systemitem class=\"service\">neutron-common</systemitem>、<systemitem class=\"service\">nova-common</systemitem>。"
-
-#: ./doc/install-guide/ch_nova.xml7(title)
-msgid "Configure Compute services"
-msgstr "Compute Service の設定"
-
-#: ./doc/install-guide/section_ceilometer-cinder.xml7(title)
-msgid "Add the Block Storage service agent for Telemetry"
-msgstr "Telemetry 用 Block Storage Service エージェントの追加"
-
-#: ./doc/install-guide/section_ceilometer-cinder.xml10(para)
-msgid ""
-"To retrieve volume samples, you must configure the Block Storage service to "
-"send notifications to the bus."
-msgstr "ボリュームのサンプルを取得するために、Block Storage Service がバスに通知を送信するよう設定する必要があります。"
-
-#: ./doc/install-guide/section_ceilometer-cinder.xml13(para)
-msgid ""
-"Edit <filename>/etc/cinder/cinder.conf</filename> and add in the "
-"<literal>[DEFAULT]</literal> section on the controller and volume nodes:"
-msgstr "コントローラーノードとボリュームノードで、<filename>/etc/cinder/cinder.conf</filename> を編集し、<literal>[DEFAULT]</literal> セクションに追加します。"
-
-#: ./doc/install-guide/section_ceilometer-cinder.xml19(para)
-msgid "Run the following commands on the controller and volume nodes:"
-msgstr "コントローラーノードおよびボリュームノードで以下のコマンドを実行します。"
-
-#: ./doc/install-guide/section_ceilometer-cinder.xml26(para)
-msgid "Restart the Block Storage services with their new settings."
-msgstr "新しい設定を用いて Block Storage のサービスを再起動します。"
-
-#: ./doc/install-guide/section_ceilometer-cinder.xml28(para)
-msgid "On the controller node:"
-msgstr "コントローラーノードで:"
-
-#: ./doc/install-guide/section_ceilometer-cinder.xml33(para)
-msgid "On the volume node:"
-msgstr "ボリュームノードで:"
+"For more information about system requirements, see the <link "
+"href=\"http://docs.openstack.org/ops/\">OpenStack Operations Guide</link>."
+msgstr "システム要件の詳細は <link href=\"http://docs.openstack.org/ops/\">OpenStack 運用ガイド</link>を参照してください。"
 
 #: ./doc/install-guide/app_reserved_uids.xml6(title)
 #: ./doc/install-guide/app_reserved_uids.xml24(caption)
@@ -4205,139 +6390,370 @@ msgstr "Compute や Networking でファイアウォールを使用したくな
 msgid "Restart the Compute and Networking services:"
 msgstr "Compute と Networking のサービスを再起動します。"
 
-#: ./doc/install-guide/section_basics-ntp.xml6(title)
-msgid "Network Time Protocol (NTP)"
-msgstr "Network Time Protocol (NTP)"
+#: ./doc/install-guide/section_heat-install.xml5(title)
+msgid "Install the Orchestration service"
+msgstr "Orchestration Service のインストール"
 
-#: ./doc/install-guide/section_basics-ntp.xml7(para)
+#: ./doc/install-guide/section_heat-install.xml8(para)
+#: ./doc/install-guide/section_heat-install.xml24(para)
+msgid "Install the Orchestration module on the controller node:"
+msgstr "コントローラーノードに Orchestration モジュールをインストールします。"
+
+#: ./doc/install-guide/section_heat-install.xml13(para)
 msgid ""
-"You must install <glossterm baseform=\"Network Time Protocol "
-"(NTP)\">NTP</glossterm> to properly synchronize services among nodes. We "
-"recommend that you configure the controller node to reference upstream "
-"servers and other nodes to reference the controller node."
-msgstr "サービスをノード間で適切に同期するために、<glossterm baseform=\"Network Time Protocol (NTP)\">NTP</glossterm> をインストールする必要があります。コントローラーノードが上位のサーバーを参照し、他のコードがコントローラーノードを参照するよう設定することを推奨します。"
+"Respond to prompts for <link linkend=\"debconf-dbconfig-common\">database "
+"management</link>, <link linkend=\"debconf-"
+"keystone_authtoken\"><systemitem>[keystone_authtoken]</systemitem> "
+"settings</link>, <link linkend=\"debconf-rabbitqm\">RabbitMQ "
+"credentials</link> and <link linkend=\"debconf-api-endpoints\">API "
+"endpoint</link> registration."
+msgstr "<link linkend=\"debconf-dbconfig-common\">データベース管理</link>、<link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> 設定</link>、<link linkend=\"debconf-rabbitqm\">RabbitMQ クレデンシャル</link>、<link linkend=\"debconf-api-endpoints\">API エンドポイント</link>の登録に関するプロンプトに答えます。"
 
-#: ./doc/install-guide/section_basics-ntp.xml15(title)
-#: ./doc/install-guide/section_basics-ntp.xml57(title)
-msgid "To install the NTP service"
-msgstr "NTP サービスのインストール方法"
-
-#: ./doc/install-guide/section_basics-ntp.xml23(title)
-#: ./doc/install-guide/section_basics-ntp.xml65(title)
-msgid "To configure the NTP service"
-msgstr "NTP サービスの設定方法"
-
-#: ./doc/install-guide/section_basics-ntp.xml24(para)
+#: ./doc/install-guide/section_heat-install.xml33(para)
 msgid ""
-"By default, the controller node synchronizes the time via a pool of public "
-"servers. However, you can optionally edit the "
-"<filename>/etc/ntp.conf</filename> file to configure alternative servers "
-"such as those provided by your organization."
-msgstr "コントローラーノードはデフォルトで、パブリックなサーバープール経由で時刻同期します。しかしながらオプションとして、自組織により提供されるサーバーを参照するために、<filename>/etc/ntp.conf</filename> ファイルを編集することもできます。"
+"In the configuration file, specify the location of the database where the "
+"Orchestration service stores data. These examples use a MySQL database with "
+"a <literal>heat</literal> user on the controller node. Replace "
+"<replaceable>HEAT_DBPASS</replaceable> with the password for the database "
+"user:"
+msgstr "Orchestration Service がデータを保存するデータベースの場所を設定ファイルで指定します。これらの例はコントローラーノードにユーザー名 <literal>heat</literal> で MySQL データベースを使用します。<literal><replaceable>HEAT_DBPASS</replaceable></literal> をデータベースのユーザーの適切なパスワードで置き換えます。"
 
-#: ./doc/install-guide/section_basics-ntp.xml29(para)
-#: ./doc/install-guide/section_basics-ntp.xml69(para)
-msgid "Edit the <filename>/etc/ntp.conf</filename> file:"
-msgstr "<filename>/etc/ntp.conf</filename> ファイルを編集します。"
+#: ./doc/install-guide/section_heat-install.xml40(replaceable)
+#: ./doc/install-guide/section_heat-install.xml46(replaceable)
+#: ./doc/install-guide/section_heat-install.xml61(replaceable)
+#: ./doc/install-guide/section_heat-install.xml63(replaceable)
+msgid "HEAT_DBPASS"
+msgstr "HEAT_DBPASS"
 
-#: ./doc/install-guide/section_basics-ntp.xml30(para)
+#: ./doc/install-guide/section_heat-install.xml41(para)
 msgid ""
-"Add, change, or remove the <literal>server</literal> keys as necessary for "
-"your environment. Replace <replaceable>NTP_SERVER</replaceable> with the "
-"hostname or IP address of suitable NTP server."
-msgstr "環境の必要に応じて、<literal>server</literal> を追加、変更、削除します。<replaceable>NTP_SERVER</replaceable を適切な NTP サーバーのホスト名や IP アドレスで置き換えます。"
+"Edit <filename>/etc/heat/heat.conf</filename> and modify the "
+"<literal>[database]</literal> section:"
+msgstr "<filename>/etc/heat/heat.conf</filename> を編集し、<literal>[database]</literal> セクションを変更します。"
 
-#: ./doc/install-guide/section_basics-ntp.xml34(replaceable)
-msgid "NTP_SERVER"
-msgstr "NTP_SERVER"
-
-#: ./doc/install-guide/section_basics-ntp.xml36(para)
-#: ./doc/install-guide/section_basics-ntp.xml74(para)
+#: ./doc/install-guide/section_heat-install.xml49(para)
 msgid ""
-"Remove the <filename>/var/lib/ntp/ntp.conf.dhcp</filename> file if it "
-"exists."
-msgstr "<filename>/var/lib/ntp/ntp.conf.dhcp</filename> が存在すれば、削除します。"
+"By default, the Ubuntu packages create an SQLite database. Delete the "
+"<filename>heat.sqlite</filename> file that was created in the "
+"<filename>/var/lib/heat/</filename> directory so that it does not get used "
+"by mistake:"
+msgstr "Ubuntu パッケージはデフォルトで SQLite データベースを作成します。誤って使用されないように、<filename>/var/lib/heat/</filename> に作成された <filename>heat.sqlite</filename> ファイルを削除します。"
 
-#: ./doc/install-guide/section_basics-ntp.xml41(para)
-#: ./doc/install-guide/section_basics-ntp.xml79(para)
-msgid "Restart the NTP service:"
-msgstr "NTP サービスを再起動します。"
-
-#: ./doc/install-guide/section_basics-ntp.xml45(para)
-#: ./doc/install-guide/section_basics-ntp.xml83(para)
-msgid "Start the NTP service and configure it to start when the system boots:"
-msgstr "NTP サービスを起動し、システム起動時に起動するよう設定します。"
-
-#: ./doc/install-guide/section_basics-ntp.xml55(title)
-msgid "Configure other nodes"
-msgstr "他のノードの設定"
-
-#: ./doc/install-guide/section_basics-ntp.xml66(para)
+#: ./doc/install-guide/section_heat-install.xml56(para)
 msgid ""
-"Configure the network and compute nodes to reference the controller node."
-msgstr "ネットワークノードとコンピュートノードがコントローラーノードを参照するよう設定します。"
+"Use the password that you set previously to log in as "
+"<literal>root</literal> and create a <literal>heat</literal> database user:"
+msgstr "<literal>root</literal> としてログインするために前に設定したパスワードを使用し、<literal>heat</literal> データベースユーザーを作成します。"
 
-#: ./doc/install-guide/section_basics-ntp.xml70(para)
+#: ./doc/install-guide/section_heat-install.xml66(para)
+msgid "Create the heat service tables:"
+msgstr "heat サービスのテーブルを作成します。"
+
+#: ./doc/install-guide/section_heat-install.xml69(para)
+msgid "Ignore <errortext>DeprecationWarning</errortext> errors."
+msgstr "<errortext>DeprecationWarning</errortext> エラーを無視します。"
+
+#: ./doc/install-guide/section_heat-install.xml74(para)
 msgid ""
-"Comment out or remove all but one <literal>server</literal> key and change "
-"it to reference the controller node."
-msgstr "1 つの <literal>server</literal> キー以外をすべてコメントアウトまたは削除します。このキーは、コントローラーノードを参照するよう変更します。"
+"The Ubuntu packages do not correctly set up logging. Edit the "
+"<filename>/etc/heat/heat.conf</filename> file and change the "
+"<literal>[DEFAULT]</literal> section:"
+msgstr "Ubuntu パッケージはロギングを正しくセットアップしません。<filename>/etc/heat/heat.conf</filename> ファイルを編集し、<literal>[DEFAULT]</literal> セクションを変更します。"
 
-#: ./doc/install-guide/section_basics-ntp.xml93(title)
-msgid "Verify operation"
-msgstr "運用の検証"
-
-#: ./doc/install-guide/section_basics-ntp.xml94(para)
+#: ./doc/install-guide/section_heat-install.xml88(para)
 msgid ""
-"We recommend that you verify NTP synchronization before proceeding further. "
-"Some nodes, particularly those that reference the controller node, can take "
-"several minutes to synchronize."
-msgstr "続行する前に、NTP 同期について検証することを推奨します。いくつかのノード、とくにコントローラーノードを参照するノードは、同期に数分かかる可能性があります。"
+"Configure the Orchestration Service to use the RabbitMQ message broker."
+msgstr "Orchestration Service が RabbitMQ メッセージブローカーを使用するよう設定します。"
 
-#: ./doc/install-guide/section_basics-ntp.xml98(title)
-msgid "To verify NTP synchronization"
-msgstr "NTP 同期の検証方法"
-
-#: ./doc/install-guide/section_basics-ntp.xml100(para)
-#: ./doc/install-guide/section_basics-ntp.xml115(para)
-msgid "Run this command on the <emphasis>controller</emphasis> node:"
-msgstr "このコマンドを<emphasis>コントローラー</emphasis>ノードで実行します。"
-
-#: ./doc/install-guide/section_basics-ntp.xml107(para)
+#: ./doc/install-guide/section_heat-install.xml90(para)
 msgid ""
-"Contents in the <emphasis>remote</emphasis> column should indicate the "
-"hostname or IP address of one or more NTP servers."
-msgstr "<emphasis>remote</emphasis> 列の内容は、1 つ以上の NTP サーバーのホスト名や IP アドレスを意味するでしょう。"
+"Edit <filename>/etc/heat/heat.conf</filename> and modify the "
+"<literal>[DEFAULT]</literal> section:"
+msgstr "<filename>/etc/heat/heat.conf</filename> を編集し、<literal>[DEFAULT]</literal> セクションを変更します。"
 
-#: ./doc/install-guide/section_basics-ntp.xml110(para)
-#: ./doc/install-guide/section_basics-ntp.xml134(para)
+#: ./doc/install-guide/section_heat-install.xml99(para)
 msgid ""
-"Contents in the <emphasis>refid</emphasis> column typically reference IP "
-"addresses of upstream servers."
-msgstr "<emphasis>refid</emphasis> 列の内容は、一般的に上位のサーバーの IP アドレスを参照します。"
+"Create a <literal>heat</literal> user that the Orchestration service can use"
+" to authenticate with the Identity Service. Use the "
+"<literal>service</literal> tenant and give the user the "
+"<literal>admin</literal> role:"
+msgstr "Orchestration サービスが Identity Service で認証するために使用する <literal>heat</literal> ユーザーを作成します。<literal>service</literal> プロジェクトを使用し、ユーザーに <literal>admin</literal> ロールを与えます。"
 
-#: ./doc/install-guide/section_basics-ntp.xml122(para)
+#: ./doc/install-guide/section_heat-install.xml103(replaceable)
+#: ./doc/install-guide/section_heat-install.xml119(replaceable)
+msgid "HEAT_PASS"
+msgstr "HEAT_PASS"
+
+#: ./doc/install-guide/section_heat-install.xml104(replaceable)
+msgid "heat@example.com"
+msgstr "heat@example.com"
+
+#: ./doc/install-guide/section_heat-install.xml108(para)
 msgid ""
-"Contents in the <emphasis>condition</emphasis> column should indicate "
-"<literal>sys.peer</literal> for at least one server."
-msgstr "<emphasis>condition</emphasis> 列の内容は、少なくとも 1 つのサーバーの <literal>sys.peer</literal> を意味するでしょう。"
+"Edit the <filename>/etc/heat/heat.conf</filename> file to change the "
+"<literal>[keystone_authtoken]</literal> and "
+"<literal>[ec2authtoken]</literal> sections to add credentials to the "
+"Orchestration Service:"
+msgstr "Orchestration Service のクレデンシャルを追加するために、<filename>/etc/heat/heat.conf</filename> ファイルを編集し、<literal>[keystone_authtoken]</literal> セクションと <literal>[ec2authtoken]</literal> セクションを変更します。"
 
-#: ./doc/install-guide/section_basics-ntp.xml126(para)
-#: ./doc/install-guide/section_basics-ntp.xml139(para)
-msgid "Run this command on <emphasis>all other</emphasis> nodes:"
-msgstr "このコマンドを<emphasis>他のすべての</emphasis>ノードで実行します。"
-
-#: ./doc/install-guide/section_basics-ntp.xml131(para)
+#: ./doc/install-guide/section_heat-install.xml125(para)
 msgid ""
-"Contents in the <emphasis>remote</emphasis> column should indicate the "
-"hostname of the controller node."
-msgstr "<emphasis>remote</emphasis> 列の内容は、コントローラーノードのホスト名を意味するでしょう。"
+"Register the Heat and CloudFormation APIs with the Identity Service so that "
+"other OpenStack services can locate these APIs. Register the services and "
+"specify the endpoints:"
+msgstr "他の OpenStack サービスから使用できるように、Heat と CloudFormation API を Identity Service に登録します。サービスを登録し、エンドポイントを指定します。"
 
-#: ./doc/install-guide/section_basics-ntp.xml145(para)
+#: ./doc/install-guide/section_heat-install.xml145(para)
+msgid "Create the <literal>heat_stack_user</literal> role."
+msgstr "<literal>heat_stack_user</literal> ロールを作成します。"
+
+#: ./doc/install-guide/section_heat-install.xml146(para)
 msgid ""
-"Contents in the <emphasis>condition</emphasis> column should indicate "
-"<literal>sys.peer</literal>."
-msgstr "<emphasis>condition</emphasis> 列の内容は、<literal>sys.peer</literal> を意味するでしょう。"
+"This role is used as the default role for users created by the Orchestration"
+" module."
+msgstr "このロールは、Orchestration モジュールにより作成されたユーザーのデフォルトのロールとして使用されます。"
+
+#: ./doc/install-guide/section_heat-install.xml148(para)
+msgid ""
+"Run the following command to create the <literal>heat_stack_user</literal> "
+"role:"
+msgstr "<literal>heat_stack_user</literal> ロールを作成するために、以下のコマンドを実行します。"
+
+#: ./doc/install-guide/section_heat-install.xml153(para)
+msgid "Configure the metadata and waitcondition servers' URLs."
+msgstr "メタデータと待機条件のサーバーの URL を設定します。"
+
+#: ./doc/install-guide/section_heat-install.xml154(para)
+msgid ""
+"Edit the <filename>/etc/heat/heat.conf</filename> file and modify the "
+"following options in the <literal>[DEFAULT]</literal> section:"
+msgstr "<filename>/etc/heat/heat.conf</filename> ファイルを編集し、<literal>[DEFAULT]</literal> セクションの以下のオプションを変更します。"
+
+#: ./doc/install-guide/section_heat-install.xml160(replaceable)
+#: ./doc/install-guide/section_heat-install.xml163(replaceable)
+#: ./doc/install-guide/section_heat-install.xml168(replaceable)
+#: ./doc/install-guide/section_heat-install.xml170(replaceable)
+msgid "10.0.0.11"
+msgstr "10.0.0.11"
+
+#: ./doc/install-guide/section_heat-install.xml164(para)
+msgid ""
+"Run the following commands to modify the <literal>[DEFAULT]</literal> "
+"section of the <filename>/etc/heat/heat.conf</filename> file:"
+msgstr "<filename>/etc/heat/heat.conf</filename> ファイルの <literal>[DEFAULT]</literal> セクションを変更するために、以下のコマンドを実行します。"
+
+#: ./doc/install-guide/section_heat-install.xml172(para)
+msgid ""
+"The example uses the IP address of the controller (10.0.0.11) instead of the"
+" <literal>controller</literal> host name since our example architecture does"
+" not include a DNS setup. Make sure that the instances can resolve the "
+"controller host name if you choose to use it in the URLs."
+msgstr "このアーキテクチャー例は DNS サーバーを持たないため、この例は <literal>controller</literal> というホスト名の代わりに IP アドレス (10.0.0.11) を使用します。URL にホスト名を使用する場合、インスタンスがコントローラーのホスト名を名前解決できることを確認してください。"
+
+#: ./doc/install-guide/section_heat-install.xml186(para)
+msgid ""
+"Start the <systemitem class=\"service\">heat-api</systemitem>, <systemitem "
+"class=\"service\">heat-api-cfn</systemitem> and <systemitem class=\"service"
+"\">heat-engine</systemitem> services and configure them to start when the "
+"system boots:"
+msgstr "<systemitem class=\"service\">heat-api</systemitem>、<systemitem class=\"service\">heat-api-cfn</systemitem>、<systemitem class=\"service\">heat-engine</systemitem> サービスを起動し、システムの起動時にそれらが起動するよう設定します。"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml6(title)
+#: ./doc/install-guide/section_neutron-ovs-network-node.xml6(title)
+msgid "Configure network node"
+msgstr "ネットワークノードの設定"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml188(title)
+msgid "To configure the Layer-3 (L3) agent"
+msgstr "L3 エージェントの設定方法"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml189(para)
+msgid ""
+"The <glossterm>Layer-3 (L3) agent</glossterm> provides routing services for "
+"instance virtual networks."
+msgstr "<glossterm baseform=\"Layer-3 (L3) agent\">L3 エージェント</glossterm> は、インスタンスの仮想ネットワーク向けルーティングサービスを提供します。"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml198(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml213(para)
+msgid ""
+"We recommend adding <literal>verbose = True</literal> to the "
+"<literal>[DEFAULT]</literal> section in "
+"<filename>/etc/neutron/l3_agent.ini</filename> to assist with "
+"troubleshooting."
+msgstr "トラブルシューティングに役立てるため、<filename>/etc/neutron/l3_agent.ini</filename> の <literal>[DEFAULT]</literal> セクションに <literal>verbose = True</literal> を追加することを推奨します。"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml205(para)
+msgid ""
+"Edit the <filename>/etc/neutron/l3_agent.ini</filename> file and add the "
+"following keys to the <literal>[DEFAULT]</literal> section:"
+msgstr "<filename>/etc/neutron/l3_agent.ini</filename> ファイルを編集し、以下のキーを <literal>[DEFAULT]</literal> セクションに追加します。"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml221(title)
+msgid "To configure the DHCP agent"
+msgstr "DHCP エージェントの設定方法"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml222(para)
+msgid ""
+"The <glossterm>DHCP agent</glossterm> provides <glossterm>DHCP</glossterm> "
+"services for instance virtual networks."
+msgstr "<glossterm baseform=\"DHCP agent\">DHCP エージェント</glossterm> はインスタンスの仮想ネットワーク向け <glossterm>DHCP</glossterm> サービスを提供します。"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml234(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml250(para)
+msgid ""
+"We recommend adding <literal>verbose = True</literal> to the "
+"<literal>[DEFAULT]</literal> section in "
+"<filename>/etc/neutron/dhcp_agent.ini</filename> to assist with "
+"troubleshooting."
+msgstr "トラブルシューティングに役立てるため、<filename>/etc/neutron/dhcp_agent.ini</filename> の <literal>[DEFAULT]</literal> セクションに <literal>verbose = True</literal> を追加することを推奨します。"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml241(para)
+msgid ""
+"Edit the <filename>/etc/neutron/dhcp_agent.ini</filename> file and add the "
+"following keys to the <literal>[DEFAULT]</literal> section:"
+msgstr "<filename>/etc/neutron/dhcp_agent.ini</filename> ファイルを編集し、以下のキーを <literal>[DEFAULT]</literal> セクションに追加します。"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml258(title)
+msgid "To configure the metadata agent"
+msgstr "メタデータエージェントの設定方法"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml259(para)
+msgid ""
+"The <glossterm>metadata agent</glossterm> provides configuration information"
+" such as credentials for remote access to instances."
+msgstr "<glossterm baseform=\"metadata agent\">メタデータエージェント</glossterm>は、インスタンスへのリモートアクセス用の設定情報を提供します。"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml263(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml293(para)
+msgid ""
+"Replace <replaceable>NEUTRON_PASS</replaceable> with the password you chose "
+"for the <literal>neutron</literal> user in the Identity service. Replace "
+"<replaceable>METADATA_SECRET</replaceable> with a suitable secret for the "
+"metadata proxy."
+msgstr "Identity で <literal>neutron</literal> ユーザー用に選択したパスワードで <replaceable>NEUTRON_PASS</replaceable> を置き換えます。<replaceable>METADATA_SECRET</replaceable> をメタデータプロキシ用の適切なシークレットで置き換えます。"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml281(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml306(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml329(replaceable)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml341(replaceable)
+msgid "METADATA_SECRET"
+msgstr "METADATA_SECRET"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml283(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml308(para)
+msgid ""
+"We recommend adding <literal>verbose = True</literal> to the "
+"<literal>[DEFAULT]</literal> section in "
+"<filename>/etc/neutron/metadata_agent.ini</filename> to assist with "
+"troubleshooting."
+msgstr "トラブルシューティングに役立てるため、<filename>/etc/neutron/metadata_agent.ini</filename> の <literal>[DEFAULT]</literal> セクションに <literal>verbose = True</literal> を追加することを推奨します。"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml290(para)
+msgid ""
+"Edit the <filename>/etc/neutron/metadata_agent.ini</filename> file and add "
+"the following keys to the <literal>[DEFAULT]</literal> section:"
+msgstr "<filename>/etc/neutron/metadata_agent.ini</filename> ファイルを編集し、以下のキーを <literal>[DEFAULT]</literal> セクションに追加します。"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml316(para)
+msgid ""
+"Perform the next two steps on the <emphasis>controller</emphasis> node."
+msgstr "<emphasis>コントローラー</emphasis>ノードで次の 2 つの手順を実行します。"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml321(para)
+msgid ""
+"On the <emphasis>controller</emphasis> node, configure Compute to use the "
+"metadata service:"
+msgstr "<emphasis>コントローラー</emphasis>ノードで、メタデータサービスを使用するよう Compute を設定します。"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml323(para)
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml335(para)
+msgid ""
+"Replace <replaceable>METADATA_SECRET</replaceable> with the secret you chose"
+" for the metadata proxy."
+msgstr "メタデータプロキシ用に選択した適切なシークレットで <replaceable>METADATA_SECRET</replaceable> を置き換えます。"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml332(para)
+msgid ""
+"On the <emphasis>controller</emphasis> node, edit the "
+"<filename>/etc/nova/nova.conf</filename> file and add the following keys to "
+"the <literal>[DEFAULT]</literal> section:"
+msgstr "<emphasis>コントローラー</emphasis>ノードで、<filename>/etc/nova/nova.conf</filename> ファイルを編集し、以下のキーを <literal>[DEFAULT]</literal> セクションに追加します。"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml344(para)
+msgid ""
+"On the <emphasis>controller</emphasis> node, restart the Compute "
+"<glossterm>API</glossterm> service:"
+msgstr "<emphasis>コントローラー</emphasis>ノードで、Compute <glossterm>API</glossterm> サービスを再起動します。"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml352(para)
+msgid ""
+"The ML2 plug-in uses the Open vSwitch (OVS) mechanism (agent) to build "
+"virtual networking framework for instances."
+msgstr "ML2 プラグインは、インスタンスの仮想ネットワークフレームワークを構築するために、Open vSwitch 機能 (エージェント) を使用します。"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml356(para)
+msgid ""
+"Replace <replaceable>INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS</replaceable> "
+"with the IP address of the instance tunnels network interface on your "
+"network node. This guide uses <literal>10.0.1.21</literal> for the IP "
+"address of the instance tunnels network interface on the network node."
+msgstr "ネットワークノードのインスタンストンネルネットワークインターフェースの IP アドレスで <replaceable>INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS</replaceable> を置き換えます。このガイドは、ネットワークノードのインスタンストンネルネットワークインターフェースの IP アドレスに <literal>10.0.1.21</literal> を使用します。"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml383(para)
+msgid ""
+"Edit the <filename>/etc/neutron/plugins/ml2/ml2_conf.ini</filename> file."
+msgstr "<filename>/etc/neutron/plugins/ml2/ml2_conf.ini</filename> ファイルを編集します。"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml400(para)
+msgid ""
+"Replace <replaceable>INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS</replaceable> "
+"with the IP address of the instance tunnels network interface on your "
+"network node."
+msgstr "ネットワークノードのインスタンストンネルネットワークインターフェースの IP アドレスで <replaceable>INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS</replaceable> を置き換えます。"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml419(para)
+msgid ""
+"The OVS service provides the underlying virtual networking framework for "
+"instances. The integration bridge <literal>br-int</literal> handles internal"
+" instance network traffic within OVS. The external bridge <literal>br-"
+"ex</literal> handles external instance network traffic within OVS. The "
+"external bridge requires a port on the physical external network interface "
+"to provide instances with external network access. In essence, this port "
+"bridges the virtual and physical external networks in your environment."
+msgstr "OVS サービスは、バックエンドの仮想ネットワークフレームワークをインスタンスに提供します。統合ブリッジ <literal>br-int</literal> は OVS 内のインスタンスの内部ネットワーク通信を処理します。外部ブリッジ <literal>br-ex</literal> は OVS 内のインスタンスの外部ネットワーク通信を処理します。外部ブリッジは、インスタンスに外部ネットワークアクセスを提供するために、外部物理ネットワークインターフェースにポートが必要です。このポートは本質的に、お使いの環境で仮想外部ネットワークと物理外部ネットワークをブリッジします。"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml452(para)
+msgid "Add the external bridge:"
+msgstr "外部ブリッジを追加します。"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml456(para)
+msgid ""
+"Add a port to the external bridge that connects to the physical external "
+"network interface:"
+msgstr "外部ネットワークの物理インターフェースに接続する外部ブリッジに、ポートを追加します。"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml463(para)
+msgid ""
+"Depending on your network interface driver, you may need to disable "
+"<glossterm>Generic Receive Offload (GRO)</glossterm> to achieve suitable "
+"throughput between your instances and the external network."
+msgstr "お使いのネットワークインターフェースドライバーによっては、インスタンスと外部ネットワーク間の適切なスループットを達成するために、<glossterm baseform=\"Generic Receive Offload (GRO)\">GRO</glossterm> を無効化する必要があるかもしれません。"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml467(para)
+msgid ""
+"To temporarily disable GRO on the external network interface while testing "
+"your environment:"
+msgstr "環境のテスト中、外部ネットワークインターフェースで一時的に GRO を無効化する場合:"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml505(para)
+msgid ""
+"Start the Networking services and configure them to start when the system "
+"boots:"
+msgstr "Networking サービスを起動し、システム起動時に起動するよう設定します。"
+
+#: ./doc/install-guide/section_neutron-ml2-network-node.xml525(para)
+msgid "Restart the Networking services:"
+msgstr "Networking サービスを再起動します。"
 
 #: ./doc/install-guide/section_ceilometer-glance.xml6(title)
 msgid "Configure the Image Service for Telemetry"
@@ -4362,460 +6778,545 @@ msgstr "新しい設定を用いて Image サービスを再起動します。"
 #. When image changes, this message will be marked fuzzy or untranslated for
 #. you.
 #. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_basics-networking-nova.xml25(None)
-#: ./doc/install-guide/ch_overview.xml147(None)
+#: ./doc/install-guide/section_debconf-keystone_authtoken.xml30(None)
 msgid ""
-"@@image: 'figures/installguide_arch-nova.png'; "
-"md5=da24b356516c960a33ab2b4b72840774"
-msgstr "@@image: 'figures/installguide_arch-nova.png'; md5=da24b356516c960a33ab2b4b72840774"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml7(para)
-msgid ""
-"The example architecture with legacy networking (nova-network) requires a "
-"controller node and at least one compute node. The controller node contains "
-"one network interface on the <glossterm>management network</glossterm>. The "
-"compute node contains one network interface on the management network and "
-"one on the <glossterm>external network</glossterm>."
-msgstr "このレガシーネットワーク (nova-network) を持つアーキテクチャ例は、コントローラーと最低 1 つのコンピュートノードを必要とします。コントローラーノードは、<glossterm baseform=\"management network\">管理ネットワーク</glossterm>に 1 つのネットワークインターフェースを持ちます。コンピュートノードは、管理ネットワークに 1 つのネットワークインターフェースを、<glossterm baseform=\"external network\">外部ネットワーク</glossterm>に 1 つを持ちます。"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml14(para)
-msgid ""
-"Network interface names vary by distribution. Traditionally, interfaces use "
-"\"eth\" followed by a sequential number. To cover all variations, this guide"
-" simply refers to the first interface as the interface with the lowest "
-"number and the second interface as the interface with the highest number."
-msgstr "ネットワークインターフェースの名前はディストリビューションにより異なります。伝統的に、インターフェースは、「eth」から始まり、数字が後ろにつきます。すべての種類を取り扱うために、このガイドは単に、最小の番号を持つインターフェースとして 1 番目のインターフェースを参照します。最大の番号を持つインターフェースとして 2 番目のインターフェースを参照します。"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml21(title)
-#: ./doc/install-guide/ch_overview.xml143(title)
-msgid "Two-node architecture with legacy networking (nova-network)"
-msgstr "レガシーネットワーク (nova-network) を持つ 2 ノードアーキテクチャー"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml29(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml33(para)
-msgid ""
-"Unless you intend to use the exact configuration provided in this example "
-"architecture, you must modify the networks in this procedure to match your "
-"environment. Also, each node must resolve the other nodes by name in "
-"addition to IP address. For example, the "
-"<replaceable>controller</replaceable> name must resolve to "
-"<literal>10.0.0.11</literal>, the IP address of the management interface on "
-"the controller node."
-msgstr "このアーキテクチャ例で提供される設定とまったく同じものを使用したくなければ、お使いの環境に合わせるために、この手順にあるネットワークを変更する必要があります。また、各ノードは、IP アドレスに加えて、名前により他のノードを名前解決する必要があります。例えば、<replaceable>controller</replaceable> という名前は、コントローラーノードの管理ネットワークの IP アドレス <literal>10.0.0.11</literal> に解決する必要があります。"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml37(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml41(para)
-msgid ""
-"Reconfiguring network interfaces will interrupt network connectivity. We "
-"recommend using a local terminal session for these procedures."
-msgstr "ネットワークインターフェースを再設定すると、ネットワーク接続性が中断されます。これらの手順はローカルの端末セッションを使用することを推奨します。"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml42(title)
-#: ./doc/install-guide/section_basics-networking-neutron.xml46(title)
-msgid "Controller node"
-msgstr "コントローラーノード"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml44(title)
-#: ./doc/install-guide/section_basics-networking-nova.xml76(title)
-#: ./doc/install-guide/section_basics-networking-neutron.xml48(title)
-#: ./doc/install-guide/section_basics-networking-neutron.xml83(title)
-#: ./doc/install-guide/section_basics-networking-neutron.xml165(title)
-msgid "To configure networking:"
-msgstr "ネットワークを設定する方法:"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml46(para)
-#: ./doc/install-guide/section_basics-networking-nova.xml78(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml50(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml85(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml167(para)
-msgid "Configure the first interface as the management interface:"
-msgstr "管理インターフェースとして 1 番目のインターフェースを設定します。"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml47(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml51(para)
-msgid "IP address: 10.0.0.11"
-msgstr "IP アドレス: 10.0.0.11"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml48(para)
-#: ./doc/install-guide/section_basics-networking-nova.xml80(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml52(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml87(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml94(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml169(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml180(para)
-msgid "Network mask: 255.255.255.0 (or /24)"
-msgstr "ネットマスク: 255.255.255.0 (または /24)"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml49(para)
-#: ./doc/install-guide/section_basics-networking-nova.xml81(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml53(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml88(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml170(para)
-msgid "Default gateway: 10.0.0.1"
-msgstr "デフォルトゲートウェイ: 10.0.0.1"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml53(title)
-#: ./doc/install-guide/section_basics-networking-nova.xml131(title)
-#: ./doc/install-guide/section_basics-networking-neutron.xml57(title)
-#: ./doc/install-guide/section_basics-networking-neutron.xml140(title)
-#: ./doc/install-guide/section_basics-networking-neutron.xml188(title)
-msgid "To configure name resolution:"
-msgstr "名前解決を設定する方法:"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml55(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml59(para)
-msgid ""
-"Set the hostname of the node to "
-"<code><replaceable>controller</replaceable></code>."
-msgstr "ノードのホスト名を <code><replaceable>controller</replaceable></code> に設定します。"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml59(para)
-#: ./doc/install-guide/section_basics-networking-nova.xml136(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml63(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml145(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml193(para)
-msgid ""
-"Edit the <filename>/etc/hosts</filename> file to contain the following:"
-msgstr "<filename>/etc/hosts</filename> ファイルを編集し、以下の内容を含めます。"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml67(para)
-#: ./doc/install-guide/section_basics-networking-nova.xml144(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml74(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml156(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml204(para)
-msgid ""
-"You must remove or comment the line beginning with "
-"<literal>127.0.1.1</literal>."
-msgstr "<literal>127.0.1.1</literal> から始まる行を削除するかコメントアウトする必要があります。"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml74(title)
-#: ./doc/install-guide/section_basics-networking-neutron.xml163(title)
-msgid "Compute node"
-msgstr "コンピュートノード"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml79(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml168(para)
-msgid "IP address: 10.0.0.31"
-msgstr "IP アドレス: 10.0.0.31"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml83(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml172(para)
-msgid "Additional compute nodes should use 10.0.0.32, 10.0.0.33, and so on."
-msgstr "追加のコンピュートノードは 10.0.0.32、10.0.0.33 などを使用すべきです。"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml88(para)
-msgid ""
-"The external interface uses a special configuration without an IP address "
-"assigned to it. Configure the second interface as the external interface:"
-msgstr "外部インターフェースは、IP アドレスを割り当てない特別な設定を使用します。外部インターフェースとして 2 番目のインターフェースを設定します。"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml91(para)
-msgid ""
-"Replace <replaceable>INTERFACE_NAME</replaceable> with the actual interface "
-"name. For example, <emphasis>eth1</emphasis> or <emphasis>ens224</emphasis>."
-msgstr "<replaceable>INTERFACE_NAME</replaceable> を実際のインターフェース名で置き換えます。例えば、<emphasis>eth1</emphasis> や <emphasis>ens224</emphasis> です。"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml96(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml105(para)
-msgid ""
-"Edit the <filename>/etc/network/interfaces</filename> file to contain the "
-"following:"
-msgstr "<filename>/etc/network/interfaces</filename> ファイルを編集し、以下の内容を含めます。"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml105(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml114(para)
-msgid ""
-"Edit the <filename>/etc/sysconfig/network-"
-"scripts/ifcfg-<replaceable>INTERFACE_NAME</replaceable></filename> file to "
-"contain the following:"
-msgstr "<filename>/etc/sysconfig/network-scripts/ifcfg-<replaceable>INTERFACE_NAME</replaceable></filename> ファイルを編集し、以下の内容を含めます。"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml108(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml117(para)
-msgid ""
-"Do not change the <literal>HWADDR</literal> and <literal>UUID</literal> "
-"keys."
-msgstr "<literal>HWADDR</literal> と <literal>UUID</literal> の項目を変更してはいけません。"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml116(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml125(para)
-msgid ""
-"Edit the "
-"<filename>/etc/sysconfig/network/ifcfg-<replaceable>INTERFACE_NAME</replaceable></filename>"
-" file to contain the following:"
-msgstr "<filename>/etc/sysconfig/network/ifcfg-<replaceable>INTERFACE_NAME</replaceable></filename> ファイルを編集し、以下の内容を含めます。"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml125(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml134(para)
-msgid "Restart networking:"
-msgstr "ネットワークを再起動します。"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml133(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml190(para)
-msgid "Set the hostname of the node to <code>compute1</code>."
-msgstr "ノードのホスト名を <code>compute1</code> に設定します。"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml151(title)
-#: ./doc/install-guide/section_basics-networking-neutron.xml211(title)
-#: ./doc/install-guide/section_neutron-initial-networks.xml228(title)
-msgid "Verify connectivity"
-msgstr "接続性の検証"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml152(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml212(para)
-msgid ""
-"We recommend that you verify network connectivity to the internet and among "
-"the nodes before proceeding further."
-msgstr "続行する前に、インターネットとノード間のネットワーク接続性を検証することを推奨します。"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml156(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml216(para)
-msgid ""
-"From the <emphasis>controller</emphasis> node, <placeholder-1/> a site on "
-"the internet:"
-msgstr "<emphasis>controller</emphasis> ノードから、インターネットのサイトに <placeholder-1/> します。"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml170(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml245(para)
-msgid ""
-"From the <emphasis>controller</emphasis> node, <placeholder-1/> the "
-"management interface on the <emphasis>compute</emphasis> node:"
-msgstr "<emphasis>controller</emphasis> ノードから、<emphasis>compute</emphasis> ノードの管理インターフェースに <placeholder-1/> します。"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml173(replaceable)
-#: ./doc/install-guide/section_basics-networking-neutron.xml248(replaceable)
-msgid "compute1"
-msgstr "compute1"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml185(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml304(para)
-msgid ""
-"From the <emphasis>compute</emphasis> node, <placeholder-1/> a site on the "
-"internet:"
-msgstr "<emphasis>compute</emphasis> ノードから、インターネットのサイトに <placeholder-1/> します。"
-
-#: ./doc/install-guide/section_basics-networking-nova.xml199(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml318(para)
-msgid ""
-"From the <emphasis>compute</emphasis> node, <placeholder-1/> the management "
-"interface on the <emphasis>controller</emphasis> node:"
-msgstr "<emphasis>compute</emphasis> ノードから、<emphasis>controller</emphasis> ノードの管理インターフェースに <placeholder-1/> します。"
+"@@image: 'figures/debconf-"
+"screenshots/service_keystone_authtoken_server_hostname.png'; "
+"md5=aafd53894e1d960531d4901123952117"
+msgstr "@@image: 'figures/debconf-screenshots/service_keystone_authtoken_server_hostname.png'; md5=aafd53894e1d960531d4901123952117"
 
 #. When image changes, this message will be marked fuzzy or untranslated for
 #. you.
 #. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_basics-networking-neutron.xml29(None)
-#: ./doc/install-guide/ch_overview.xml98(None)
+#: ./doc/install-guide/section_debconf-keystone_authtoken.xml37(None)
 msgid ""
-"@@image: 'figures/installguide_arch-neutron.png'; "
-"md5=9b3d2f2e5f9d88d198511ecbca829c6d"
-msgstr "@@image: 'figures/installguide_arch-neutron.png'; md5=9b3d2f2e5f9d88d198511ecbca829c6d"
+"@@image: 'figures/debconf-"
+"screenshots/service_keystone_authtoken_admin_tenant_name.png'; "
+"md5=a935563e4fba9b00040e35cdcfffc732"
+msgstr "@@image: 'figures/debconf-screenshots/service_keystone_authtoken_admin_tenant_name.png'; md5=a935563e4fba9b00040e35cdcfffc732"
 
-#: ./doc/install-guide/section_basics-networking-neutron.xml7(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-keystone_authtoken.xml44(None)
 msgid ""
-"The example architecture with OpenStack Networking (neutron) requires one "
-"controller node, one network node, and at least one compute node. The "
-"controller node contains one network interface on the <glossterm>management "
-"network</glossterm>. The network node contains one network interface on the "
-"management network, one on the <glossterm>instance tunnels "
-"network</glossterm>, and one on the <glossterm>external network</glossterm>."
-" The compute node contains one network interface on the management network "
-"and one on the instance tunnels network."
-msgstr "この OpenStack Networking (neutron) を持つアーキテクチャ例は、1 つのコントローラーノード、1 つのネットワークノード、最低 1 つのコンピュートノードを必要とします。コントローラーノードは、<glossterm baseform=\"management network\">管理ネットワーク</glossterm>に 1 つのネットワークインターフェースを持ちます。ネットワークノードは、管理ネットワークに 1 つのネットワークインターフェースを、<glossterm baseform=\"instance tunnels network\">インスタンストンネルネットワーク</glossterm>に 1 つを、<glossterm baseform=\"external network\">外部ネットワーク</glossterm>に 1 つを持ちます。コンピュートノードは、管理ネットワークに 1 つのインターフェースを、インスタンストンネルネットワークに 1 つを持ちます。"
+"@@image: 'figures/debconf-"
+"screenshots/service_keystone_authtoken_tenant_admin_user.png'; "
+"md5=fe3dc93c591b3e9783d4d05556efcf25"
+msgstr "@@image: 'figures/debconf-screenshots/service_keystone_authtoken_tenant_admin_user.png'; md5=fe3dc93c591b3e9783d4d05556efcf25"
 
-#: ./doc/install-guide/section_basics-networking-neutron.xml17(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-keystone_authtoken.xml51(None)
 msgid ""
-"Network interface names vary by distribution. Traditionally, interfaces use "
-"\"eth\" followed by a sequential number. To cover all variations, this guide"
-" simply refers to the first interface as the interface with the lowest "
-"number, the second interface as the interface with the middle number, and "
-"the third interface as the interface with the highest number."
-msgstr "ネットワークインターフェースの名前はディストリビューションにより異なります。伝統的に、インターフェースは、「eth」から始まり、数字が後ろにつきます。すべての種類を取り扱うために、このガイドは単に、最小の番号を持つインターフェースとして 1 番目のインターフェースを参照します。真ん中の番号を持つインターフェースとして 2 番目のインターフェースを、最大の番号を持つインターフェースとして 3 番目のインターフェースを参照します。"
+"@@image: 'figures/debconf-"
+"screenshots/service_keystone_authtoken_admin_password.png'; "
+"md5=0c30c80315d5e636dbe93a938fc2822b"
+msgstr "@@image: 'figures/debconf-screenshots/service_keystone_authtoken_admin_password.png'; md5=0c30c80315d5e636dbe93a938fc2822b"
 
-#: ./doc/install-guide/section_basics-networking-neutron.xml25(title)
-#: ./doc/install-guide/ch_overview.xml94(title)
-msgid "Three-node architecture with OpenStack Networking (neutron)"
-msgstr "OpenStack Networking (Neutron) を持つ 3 ノードアーキテクチャー"
+#: ./doc/install-guide/section_debconf-keystone_authtoken.xml6(title)
+msgid "Services and the [keystone_authtoken]"
+msgstr "サービスと [keystone_authtoken]"
 
-#: ./doc/install-guide/section_basics-networking-neutron.xml81(title)
-msgid "Network node"
-msgstr "ネットワークノード"
-
-#: ./doc/install-guide/section_basics-networking-neutron.xml86(para)
-msgid "IP address: 10.0.0.21"
-msgstr "IP アドレス: 10.0.0.21"
-
-#: ./doc/install-guide/section_basics-networking-neutron.xml91(para)
-#: ./doc/install-guide/section_basics-networking-neutron.xml177(para)
-msgid "Configure the second interface as the instance tunnels interface:"
-msgstr "インスタンスのトンネルインターフェースとして 2 番目のインターフェースを設定します。"
-
-#: ./doc/install-guide/section_basics-networking-neutron.xml93(para)
-msgid "IP address: 10.0.1.21"
-msgstr "IP アドレス: 10.0.1.21"
-
-#: ./doc/install-guide/section_basics-networking-neutron.xml97(para)
+#: ./doc/install-guide/section_debconf-keystone_authtoken.xml7(para)
 msgid ""
-"The external interface uses a special configuration without an IP address "
-"assigned to it. Configure the third interface as the external interface:"
-msgstr "外部インターフェースは、IP アドレスを割り当てない特別な設定を使用します。外部インターフェースとして 3 番目のインターフェースを設定します。"
+"Because most OpenStack services must access the Identity Service, you must "
+"configure the IP address of the <code>keystone</code> server to be able to "
+"access it. You must also configure the <code>admin_tenant_name</code>, "
+"<code>admin_user</code>, and <code>admin_password</code> options for each "
+"service to work."
+msgstr "多くの OpenStack サービスは Identity Service にアクセスする必要があるので、アクセスできるように <code>keystone</code> サーバーの IP アドレスを設定する必要があります。各サービスを動作させるために <code>admin_tenant_name</code>、<code>admin_user</code>、<code>admin_password</code> オプションも設定する必要があります。"
 
-#: ./doc/install-guide/section_basics-networking-neutron.xml100(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml458(para)
+#: ./doc/install-guide/section_debconf-keystone_authtoken.xml13(para)
+msgid "Generally, this section looks like this:"
+msgstr "一般的に、このセクションはこのようになります。"
+
+#: ./doc/install-guide/section_debconf-keystone_authtoken.xml21(para)
 msgid ""
-"Replace <replaceable>INTERFACE_NAME</replaceable> with the actual interface "
-"name. For example, <emphasis>eth2</emphasis> or <emphasis>ens256</emphasis>."
-msgstr "<replaceable>INTERFACE_NAME</replaceable> を実際のインターフェース名で置き換えます。例えば、<emphasis>eth2</emphasis> や <emphasis>ens256</emphasis> です。"
+"The debconf system helps users configure the <code>auth_host</code>, "
+"<code>admin_tenant_name</code>, <code>admin_user</code> and "
+"<code>admin_password</code> options."
+msgstr "debconf システムはユーザーが <code>auth_host</code>、<code>admin_tenant_name</code>、<code>admin_user</code>、<code>admin_password</code> オプションを設定する支援をします。"
 
-#: ./doc/install-guide/section_basics-networking-neutron.xml142(para)
-msgid "Set the hostname of the node to <code>network</code>."
-msgstr "ノードのホスト名を <code>network</code> に設定します。"
+#: ./doc/install-guide/section_debconf-keystone_authtoken.xml25(para)
+msgid "The following screens show an example Image Service configuration:"
+msgstr "以下の画面は Image Service 設定の例を示します。"
 
-#: ./doc/install-guide/section_basics-networking-neutron.xml179(para)
-msgid "IP address: 10.0.1.31"
-msgstr "IP アドレス: 10.0.1.31"
-
-#: ./doc/install-guide/section_basics-networking-neutron.xml182(para)
-msgid "Additional compute nodes should use 10.0.1.32, 10.0.1.33, and so on."
-msgstr "追加のコンピュートノードは 10.0.1.32、10.0.1.33 などを使用すべきです。"
-
-#: ./doc/install-guide/section_basics-networking-neutron.xml230(para)
+#: ./doc/install-guide/section_debconf-keystone_authtoken.xml55(para)
 msgid ""
-"From the <emphasis>controller</emphasis> node, <placeholder-1/> the "
-"management interface on the <emphasis>network</emphasis> node:"
-msgstr "<emphasis>controller</emphasis> ノードから、<emphasis>network</emphasis> ノードの管理インターフェースに <placeholder-1/> します。"
+"This information is stored in the configuration file for each service. For "
+"example:"
+msgstr "この情報は各サービスの設定ファイルに保存されます。例:"
 
-#: ./doc/install-guide/section_basics-networking-neutron.xml233(replaceable)
-msgid "network"
-msgstr "Network"
-
-#: ./doc/install-guide/section_basics-networking-neutron.xml260(para)
+#: ./doc/install-guide/section_debconf-keystone_authtoken.xml63(para)
 msgid ""
-"From the <emphasis>network</emphasis> node, <placeholder-1/> a site on the "
-"internet:"
-msgstr "<emphasis>network</emphasis> ノードから、インターネットのサイトに <placeholder-1/> します。"
+"The Debian OpenStack packages offer automation for this, so OpenStack users "
+"do not have to manually edit the configuration files."
+msgstr "Debian OpenStack パッケージがこれを自動化するため、OpenStack ユーザーは設定ファイルを手動で編集する必要がありません。"
 
-#: ./doc/install-guide/section_basics-networking-neutron.xml274(para)
+#: ./doc/install-guide/bk-openstack-install-guide.xml7(title)
 msgid ""
-"From the <emphasis>network</emphasis> node, <placeholder-1/> the management "
-"interface on the <emphasis>controller</emphasis> node:"
-msgstr "<emphasis>network</emphasis> ノードから、<emphasis>controller</emphasis> ノードの管理インターフェースに <placeholder-1/> します。"
+"OpenStack Installation Guide for <phrase os=\"rhel;centos;fedora\">Red Hat "
+"Enterprise Linux, CentOS, and Fedora</phrase><phrase os=\"ubuntu\">Ubuntu "
+"12.04/14.04 (LTS)</phrase><phrase os=\"debian\">Debian 7.0 "
+"(Wheezy)</phrase><phrase os=\"opensuse\">openSUSE and SUSE Linux Enterprise "
+"Server</phrase>"
+msgstr "OpenStack インストールガイド <phrase os=\"rhel;centos;fedora\">Red Hat Enterprise Linux、CentOS、Fedora</phrase><phrase os=\"ubuntu\">Ubuntu 12.04/14.04 (LTS)</phrase><phrase os=\"debian\">Debian 7.0 (Wheezy)</phrase><phrase os=\"opensuse\">openSUSE、SUSE Linux Enterprise Server</phrase> 版"
 
-#: ./doc/install-guide/section_basics-networking-neutron.xml289(para)
+#: ./doc/install-guide/bk-openstack-install-guide.xml15(phrase)
+msgid "Red Hat Enterprise Linux, CentOS, and Fedora"
+msgstr "Red Hat Enterprise Linux、CentOS、Fedora"
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml16(phrase)
+msgid "Ubuntu 12.04/14.04 (LTS)"
+msgstr "Ubuntu 12.04/14.04 (LTS)"
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml17(phrase)
+msgid "openSUSE and SUSE Linux Enterprise Server"
+msgstr "openSUSE、SUSE Linux Enterprise Server"
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml18(phrase)
+msgid "Debian 7.0 (Wheezy)"
+msgstr "Debian 7.0 (Wheezy)"
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml14(titleabbrev)
 msgid ""
-"From the <emphasis>network</emphasis> node, <placeholder-1/> the instance "
-"tunnels interface on the <emphasis>compute</emphasis> node:"
-msgstr "<emphasis>network</emphasis> ノードから、<emphasis>compute</emphasis> ノードの管理インターフェースに <placeholder-1/> します。"
+"OpenStack Installation Guide for "
+"<placeholder-1/><placeholder-2/><placeholder-3/><placeholder-4/>"
+msgstr "OpenStack インストールガイド <placeholder-1/><placeholder-2/><placeholder-3/><placeholder-4/> 版"
 
-#: ./doc/install-guide/section_basics-networking-neutron.xml333(para)
+#: ./doc/install-guide/bk-openstack-install-guide.xml27(orgname)
+msgid "OpenStack"
+msgstr "OpenStack"
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml31(year)
+msgid "2012"
+msgstr "2012"
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml32(year)
+msgid "2013"
+msgstr "2013"
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml33(holder)
+msgid "OpenStack Foundation"
+msgstr "OpenStack Foundation"
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml35(releaseinfo)
+msgid "icehouse"
+msgstr "icehouse"
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml36(productname)
+msgid "OpenStack Installation Guide"
+msgstr "OpenStack インストールガイド"
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml40(remark)
+msgid "Copyright details are filled in by the template."
+msgstr "Copyright details are filled in by the template."
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml45(para)
 msgid ""
-"From the <emphasis>compute</emphasis> node, <placeholder-1/> the instance "
-"tunnels interface on the <emphasis>network</emphasis> node:"
-msgstr "<emphasis>compute</emphasis> ノードから、<emphasis>network</emphasis> ノードの管理インターフェースに <placeholder-1/> します。"
+"The OpenStack® system consists of several key projects that you install "
+"separately but that work together depending on your cloud needs. These "
+"projects include Compute, Identity Service, Networking, Image Service, Block"
+" Storage, Object Storage, Telemetry, Orchestration, and Database. You can "
+"install any of these projects separately and configure them stand-alone or "
+"as connected entities. <phrase os=\"debian\">This guide walks through an "
+"installation by using packages available through Debian 7.0 (code name: "
+"Wheezy).</phrase><phrase os=\"ubuntu\">This guide walks through an "
+"installation by using packages available through Ubuntu 12.04 (LTS) or 14.04"
+" (LTS).</phrase><phrase os=\"rhel;centos;fedora\">This guide shows you how "
+"to install OpenStack by using packages available through Fedora 20 as well "
+"as on Red Hat Enterprise Linux and its derivatives through the EPEL "
+"repository.</phrase><phrase os=\"opensuse\">This guide shows you how to "
+"install OpenStack by using packages on openSUSE through the Open Build "
+"Service Cloud repository.</phrase> Explanations of configuration options and"
+" sample configuration files are included."
+msgstr "OpenStack® システムはいくつかの主要なプロジェクトから構成されます。これらは別々にインストールできますが、クラウドの要件に応じて一緒に使用できます。Compute、Identity Service、Networking、Image Service、Block Storage、Object Storage、Telemetry、Orchestration、Database があります。これらのプロジェクトを別々にインストールできます。スタンドアローンまたは全体を接続するよう設定できます。<phrase os=\"debian\">このガイドは Debian 7.0 (コード名: Wheezy) で利用可能なパッケージを使用してインストールしていきます。</phrase><phrase os=\"ubuntu\">このガイドは Ubuntu 12.04 (LTS)、14.04 (LTS) で利用可能なパッケージを使用してインストールしていきます。</phrase><phrase os=\"rhel;centos;fedora\">このガイドは EPEL リポジトリから Fedora 20、Red Hat Enterprise Linux、その派生物で利用可能なパッケージを使用して OpenStack をインストールする方法を説明します。</phrase><phrase os=\"opensuse\">Open Build Service Cloud リポジトリから openSUSE で利用可能なパッケージを使用して OpenStack をインストールする方法を説明します。</phrase>設定オプションの説明とサンプル設定ファイルが含まれます。"
 
-#: ./doc/install-guide/section_basics-prerequisites.xml6(title)
-#: ./doc/install-guide/object-storage/section_object-storage-install.xml28(title)
-msgid "Before you begin"
-msgstr "始める前に"
+#: ./doc/install-guide/bk-openstack-install-guide.xml73(date)
+msgid "2014-04-16"
+msgstr "2014-04-16"
 
-#: ./doc/install-guide/section_basics-prerequisites.xml7(para)
+#: ./doc/install-guide/bk-openstack-install-guide.xml77(para)
 msgid ""
-"For a functional environment, OpenStack doesn't require a significant amount"
-" of resources. We recommend that your environment meets or exceeds the "
-"following minimum requirements which can support several minimal "
-"<glossterm>CirrOS</glossterm> instances:"
-msgstr "機能検証環境の場合、OpenStack はあまりリソースを必要としません。いくつかの最小の <glossterm>CirrOS</glossterm> インスタンスをサポートできる、以下の最小要件を満たすことを推奨します。"
+"Update for Icehouse, rework Networking setup to use ML2 as plugin, add new "
+"chapter for Database Service setup, improved basic configuration."
+msgstr "Icehouse 向け更新。Networking のセットアップを ML2 プラグインを使用するよう再構成。Database Service のセットアップに関する章の追加。基本的な設定の改善。"
 
-#: ./doc/install-guide/section_basics-prerequisites.xml13(para)
-msgid "Controller Node: 1 processor, 2 GB memory, and 5 GB storage"
-msgstr "コントローラーノード: 1 CPU、2 GB メモリ、5 GB ストレージ"
+#: ./doc/install-guide/bk-openstack-install-guide.xml86(date)
+msgid "2013-10-25"
+msgstr "2013-10-25"
 
-#: ./doc/install-guide/section_basics-prerequisites.xml17(para)
-msgid "Network Node: 1 processor, 512 MB memory, and 5 GB storage"
-msgstr "ネットワークノード: 1 CPU、512 MB メモリ、5 GB ストレージ"
+#: ./doc/install-guide/bk-openstack-install-guide.xml90(para)
+msgid "Added initial Debian support."
+msgstr "Debian の初期サポートの追加。"
 
-#: ./doc/install-guide/section_basics-prerequisites.xml21(para)
-msgid "Compute Node: 1 processor, 2 GB memory, and 10 GB storage"
-msgstr "コンピュートノード: 1 CPU、2 GB メモリ、10 GB ストレージ"
+#: ./doc/install-guide/bk-openstack-install-guide.xml96(date)
+msgid "2013-10-17"
+msgstr "2013-10-17"
 
-#: ./doc/install-guide/section_basics-prerequisites.xml25(para)
+#: ./doc/install-guide/bk-openstack-install-guide.xml100(para)
+msgid "Havana release."
+msgstr "Havana リリース。"
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml106(date)
+msgid "2013-10-16"
+msgstr "2013-10-16"
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml110(para)
+msgid "Add support for SUSE Linux Enterprise."
+msgstr "SUSE Linux Enterprise のサポートの追加。"
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml117(date)
+msgid "2013-10-08"
+msgstr "2013-10-08"
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml121(para)
+msgid "Complete reorganization for Havana."
+msgstr "Havana 向け再構成の完了。"
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml128(date)
+msgid "2013-09-09"
+msgstr "2013-09-09"
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml132(para)
+msgid "Build also for openSUSE."
+msgstr "openSUSE 版の作成。"
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml138(date)
+msgid "2013-08-01"
+msgstr "2013-08-01"
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml142(para)
 msgid ""
-"To minimize clutter and provide more resources for OpenStack, we recommend a"
-" minimal installation of your Linux distribution. Also, we strongly "
-"recommend that you install a 64-bit version of your distribution on at least"
-" the compute node. If you install a 32-bit version of your distribution on "
-"the compute node, attempting to start an instance using a 64-bit image will "
-"fail."
-msgstr "散らかりを最小化し、OpenStack のためによりリソースを提供するために、Linux ディストリビューションの最小インストールを推奨します。また、少なくともコンピュートノードは、ディストリビューションの 64 ビット版のインストールを強く推奨します。コンピュートノードにディストリビューションの 32 ビット版をインストールする場合、64 ビット版のイメージを使用したインスタンスの起動に失敗します。"
+"Fixes to Object Storage verification steps. Fix bug <link "
+"href=\"https://bugs.launchpad.net/openstack-"
+"manuals/+bug/1207347\">1207347</link>."
+msgstr "Object Storage 検証手順の修正。バグ <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/1207347\">1207347</link> の修正。"
 
-#: ./doc/install-guide/section_basics-prerequisites.xml32(para)
+#: ./doc/install-guide/bk-openstack-install-guide.xml151(date)
+msgid "2013-07-25"
+msgstr "2013-07-25"
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml155(para)
 msgid ""
-"A single disk partition on each node works for most basic installations. "
-"However, you should consider <glossterm>Logical Volume Manager "
-"(LVM)</glossterm> for installations with optional services such as Block "
-"Storage."
-msgstr "最も基本的なインストールの場合、各ノードで単一のディスクパーティションが動作します。しかしながら、Block Storage のようなオプションサービスのインストールに <glossterm>Logical Volume Manager (LVM)</glossterm> を検討すべきです。"
+"Adds creation of cinder user and addition to the service tenant. Fix bug "
+"<link href=\"https://bugs.launchpad.net/openstack-"
+"manuals/+bug/1205057\">1205057</link>."
+msgstr "cinder ユーザーの作成と service プロジェクトへの追加。バグ <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/1205057\">1205057</link> の修正。"
 
-#: ./doc/install-guide/section_basics-prerequisites.xml37(para)
+#: ./doc/install-guide/bk-openstack-install-guide.xml165(date)
+msgid "2013-05-08"
+msgstr "2013-05-08"
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml169(para)
+msgid "Updated the book title for consistency."
+msgstr "一貫性のために文書名の更新。"
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml176(date)
+msgid "2013-05-02"
+msgstr "2013-05-02"
+
+#: ./doc/install-guide/bk-openstack-install-guide.xml180(para)
+msgid "Updated cover and fixed small errors in appendix."
+msgstr "表紙の更新と付録の小さなミスの修正。"
+
+#: ./doc/install-guide/section_basics-queue.xml6(title)
+msgid "Messaging server"
+msgstr "メッセージングサーバー"
+
+#: ./doc/install-guide/section_basics-queue.xml7(para)
 msgid ""
-"Many users build their test environments on <glossterm baseform=\"virtual "
-"machine (VM)\">virtual machines (VMs)</glossterm>. The primary benefits of "
-"VMs include the following:"
-msgstr "多くのユーザーは、<glossterm baseform=\"virtual machine (VM)\">仮想マシン (VM)</glossterm> にテスト環境を構築します。仮想マシンの主な利点は以下のとおりです。"
+"OpenStack uses a <glossterm>message broker</glossterm> to coordinate "
+"operations and status information among services. The message broker service"
+" typically runs on the controller node. OpenStack supports several message "
+"brokers including <application>RabbitMQ</application>, "
+"<application>Qpid</application>, and <application>ZeroMQ</application>. "
+"However, most distributions that package OpenStack support a particular "
+"message broker. This guide covers the message broker supported by each "
+"distribution. If you prefer to implement a different message broker, consult"
+" the documentation associated with it."
+msgstr "OpenStack は、サービス間の操作と状態を調整するために、<glossterm baseform=\"message broker\">メッセージブローカー</glossterm>を使用します。メッセージブローカーサービスは、一般的にコントローラーノードで動作します。OpenStack は、<application>RabbitMQ</application>、<application>Qpid</application>、<application>ZeroMQ</application> などのメッセージブローカーをサポートします。しかしながら、OpenStack をパッケージ化している多くのディストリビューションは、特定のメッセージブローカーをサポートします。このガイドは、各ディストリビューションによりサポートされるメッセージブローカーを取り扱います。別のメッセージブローカーを導入したければ、関連ドキュメントを確認してください。"
 
-#: ./doc/install-guide/section_basics-prerequisites.xml43(para)
+#: ./doc/install-guide/section_basics-queue.xml18(link)
+msgid "RabbitMQ"
+msgstr "RabbitMQ"
+
+#: ./doc/install-guide/section_basics-queue.xml21(link)
+msgid "Qpid"
+msgstr "Qpid"
+
+#: ./doc/install-guide/section_basics-queue.xml24(link)
+msgid "ZeroMQ"
+msgstr "ZeroMQ"
+
+#: ./doc/install-guide/section_basics-queue.xml28(title)
+msgid "To install the message broker service"
+msgstr "メッセージブローカーサービスのインストール方法"
+
+#: ./doc/install-guide/section_basics-queue.xml30(para)
+msgid "Ubuntu and Debian use <application>RabbitMQ</application>."
+msgstr "Ubuntu および Debian は <application>RabbitMQ</application> を使用します。"
+
+#: ./doc/install-guide/section_basics-queue.xml34(para)
 msgid ""
-"One physical server can support multiple nodes, each with almost any number "
-"of network interfaces."
-msgstr "1 台の物理サーバーが複数のノードをサポートできます。それぞれ複数のネットワークインターフェースを持てます。"
+"Red Hat Enterprise Linux (RHEL), CentOS, Scientific Linux, and Fedora use "
+"<application>Qpid</application>."
+msgstr "Red Hat Enterprise Linux (RHEL)、CentOS、Scientific Linux、Fedora は <application>Qpid</application> を使用します。"
 
-#: ./doc/install-guide/section_basics-prerequisites.xml47(para)
+#: ./doc/install-guide/section_basics-queue.xml40(para)
 msgid ""
-"Ability to take periodic \"snap shots\" throughout the installation process "
-"and \"roll back\" to a working configuration in the event of a problem."
-msgstr "インストールプロセス以降、定期的な「スナップショット」を取得する機能、および問題発生時に動作する設定に「ロールバック」する機能があります。"
+"SUSE Linux Enterprise Server (SLES) and openSUSE use "
+"<application>RabbitMQ</application>."
+msgstr "SUSE Linux Enterprise Server (SLES) および openSUSE は <application>RabbitMQ</application> を使用します。"
 
-#: ./doc/install-guide/section_basics-prerequisites.xml52(para)
+#: ./doc/install-guide/section_basics-queue.xml46(title)
+msgid "To configure the message broker service"
+msgstr "メッセージブローカーサービスの設定方法"
+
+#: ./doc/install-guide/section_basics-queue.xml48(para)
 msgid ""
-"However, VMs will reduce performance of your instances, particularly if your"
-" hypervisor and/or processor lacks support for hardware acceleration of "
-"nested VMs."
-msgstr "しかしながら、仮想マシンはインスタンスのパフォーマンスを劣化させます。とくに、ハイパーバイザーとプロセッサーがネステッド仮想マシンのハードウェア支援機能をサポートしない場合です。"
+"To simplify installation of your test environment, we recommend that you "
+"disable authentication."
+msgstr "テスト完了のインストールを簡単にするため、認証の無効化を推奨します。"
 
-#: ./doc/install-guide/section_basics-prerequisites.xml56(para)
+#: ./doc/install-guide/section_basics-queue.xml50(para)
 msgid ""
-"If you choose to install on VMs, make sure your hypervisor permits "
-"<glossterm>promiscuous mode</glossterm> on the <glossterm>external "
-"network</glossterm>."
-msgstr "仮想マシンにインストールする場合、お使いのハイパーバイザーが<glossterm baseform=\"external network\">外部ネットワーク</glossterm>で<glossterm baseform=\"promiscuous mode\">プロミスキャスモード</glossterm>を許可することを確認します。"
+"Edit the <filename>/etc/qpidd.conf</filename> file and change the following "
+"key:"
+msgstr "<filename>/etc/qpidd.conf</filename> ファイルを編集し、以下のキーを変更します。"
 
-#: ./doc/install-guide/section_basics-prerequisites.xml60(para)
+#: ./doc/install-guide/section_basics-queue.xml54(para)
 msgid ""
-"For more information about system requirements, see the <link "
-"href=\"http://docs.openstack.org/ops/\">OpenStack Operations Guide</link>."
-msgstr "システム要件の詳細は <link href=\"http://docs.openstack.org/ops/\">OpenStack 運用ガイド</link>を参照してください。"
+"For production environments, you should enable authentication. For more "
+"information on securing the message broker, see the <link "
+"href=\"http://qpid.apache.org/books/trunk/AMQP-Messaging-Broker-CPP-"
+"Book/html/chap-Messaging_User_Guide-Security.html\">documentation</link>."
+msgstr "本番環境では認証を有効化することを強く推奨します。メッセージブローカーのセキュア化に関する詳細は、<link href=\"http://qpid.apache.org/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/chap-Messaging_User_Guide-Security.html\">ドキュメント</link>を参照してください。"
 
-#: ./doc/install-guide/ch_trove.xml6(title)
-msgid "Add the Database service"
-msgstr "Database サービスの追加"
-
-#: ./doc/install-guide/ch_trove.xml7(para)
+#: ./doc/install-guide/section_basics-queue.xml59(para)
 msgid ""
-"Use the <glossterm baseform=\"Database Service\">Database module</glossterm>"
-" to create cloud database resources. The integrated project name is "
-"<glossterm>trove</glossterm>."
-msgstr "クラウドデータベースリソースを作成するために、<glossterm baseform=\"Database Service\">Database モジュール</glossterm>を使用します。統合プロジェクトの名前は <glossterm>trove</glossterm> です。"
+"If you decide to enable authentication for your test environment, you must "
+"configure the <literal>qpid_username</literal> and "
+"<literal>qpid_password</literal> keys in the configuration file of each "
+"OpenStack service that uses the message broker."
+msgstr "テスト環境向けに認証を有効化することにした場合、メッセージブローカーを使用する各 OpenStack サービスの設定ファイルで <literal>qpid_username</literal> と <literal>qpid_password</literal> を設定する必要があります。"
 
-#: ./doc/install-guide/ch_trove.xml10(para)
+#: ./doc/install-guide/section_basics-queue.xml66(para)
+msgid "Start the message broker service:"
+msgstr "メッセージブローカーサービスを起動します。"
+
+#: ./doc/install-guide/section_basics-queue.xml70(para)
 msgid ""
-"This chapter is a work in progress. It may contain incorrect information, "
-"and will be updated frequently."
-msgstr "本章は作業中です。不正確な情報を含む可能性があり、頻繁に更新されます。"
+"The message broker creates a default account that uses "
+"<literal>guest</literal> for the username and password. To simplify "
+"installation of your test environment, we recommend that you use this "
+"account, but change the password for it."
+msgstr "メッセージブローカーは、ユーザー名とパスワードに <literal>guest</literal> を使用するデフォルトアカウントを作成します。テスト環境のインストールを簡単にするために、このアカウントを使用し、そのパスワードを変更しないことを推奨します。"
 
-#: ./doc/install-guide/section_neutron-ovs-network-node.xml6(title)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml6(title)
-msgid "Configure network node"
-msgstr "ネットワークノードの設定"
+#: ./doc/install-guide/section_basics-queue.xml75(para)
+msgid ""
+"Replace <replaceable>RABBIT_PASS</replaceable> with a suitable password."
+msgstr "<replaceable>RABBIT_PASS</replaceable> を適切なパスワードに置き換えます。"
+
+#: ./doc/install-guide/section_basics-queue.xml78(para)
+msgid ""
+"You must configure the <literal>rabbit_password</literal> key in the "
+"configuration file for each OpenStack service that uses the message broker."
+msgstr "メッセージブローカーを使用する各 OpenStack サービスの設定ファイルで <literal>rabbit_password</literal> キーを設定する必要があります。"
+
+#: ./doc/install-guide/section_basics-queue.xml82(para)
+msgid ""
+"For production environments, you should create a unique account with "
+"suitable password. For more information on securing the message broker, see "
+"the <link "
+"href=\"https://www.rabbitmq.com/man/rabbitmqctl.1.man.html\">documentation</link>."
+msgstr "本番環境では、適切なパスワードを持つ独自のアカウントを作成すべきです。メッセージブローカーのセキュア化に関する詳細は、<link href=\"https://www.rabbitmq.com/man/rabbitmqctl.1.man.html\">ドキュメント</link>を参照してください。"
+
+#: ./doc/install-guide/section_basics-queue.xml87(para)
+msgid ""
+"If you decide to create a unique account with suitable password for your "
+"test environment, you must configure the <literal>rabbit_userid</literal> "
+"and <literal>rabbit_password</literal> keys in the configuration file of "
+"each OpenStack service that uses the message broker."
+msgstr "テスト環境向けに適切なパスワードを持つ独自のアカウントを作成することにした場合、メッセージブローカーを使用する各 OpenStack サービスの設定ファイルで <literal>rabbit_userid</literal> と <literal>rabbit_password</literal> を設定する必要があります。"
+
+#: ./doc/install-guide/section_basics-queue.xml98(para)
+msgid ""
+"Start the message broker service and configure it to start when the system "
+"boots:"
+msgstr "メッセージブローカーサービスを起動し、システム起動時に起動するよう設定します。"
+
+#: ./doc/install-guide/section_basics-queue.xml104(para)
+msgid "Configure the message broker service to start when the system boots:"
+msgstr "システム起動時にメッセージブローカーサービスが起動するよう設定します。"
+
+#: ./doc/install-guide/section_basics-queue.xml109(para)
+msgid "Congratulations, now you are ready to install OpenStack services!"
+msgstr "おめでとうございます。これで OpenStack サービスをインストールする準備ができました。"
+
+#: ./doc/install-guide/section_keystone-services.xml4(title)
+msgid "Define services and API endpoints"
+msgstr "サービスと API エンドポイントの定義"
+
+#: ./doc/install-guide/section_keystone-services.xml5(para)
+msgid ""
+"So that the Identity Service can track which OpenStack services are "
+"installed and where they are located on the network, you must register each "
+"service in your OpenStack installation. To register a service, run these "
+"commands:"
+msgstr "Identity Service が、どの OpenStack サービスがインストールされているか、それらがネットワークのどこにあるかを追跡できるよう、OpenStack インストール環境の各サービスを登録する必要があります。サービスを登録するために、これらのコマンドを実行します。"
+
+#: ./doc/install-guide/section_keystone-services.xml11(para)
+msgid "<placeholder-1/>. Describes the service."
+msgstr "<placeholder-1/>。サービスを定義します。"
+
+#: ./doc/install-guide/section_keystone-services.xml15(para)
+msgid ""
+"<placeholder-1/>. Associates <glossterm baseform=\"API endpoint\">API "
+"endpoints</glossterm> with the service."
+msgstr "<placeholder-1/>。<glossterm baseform=\"API endpoint\">API エンドポイント</glossterm>とサービスを関連付けます。"
+
+#: ./doc/install-guide/section_keystone-services.xml20(para)
+msgid ""
+"You must also register the Identity Service itself. Use the "
+"<code>OS_SERVICE_TOKEN</code> environment variable, as set previously, for "
+"authentication."
+msgstr "Identity Service 自身も登録する必要があります。前に設定した <code>OS_SERVICE_TOKEN</code> 環境変数を認証のために使用します。"
+
+#: ./doc/install-guide/section_keystone-services.xml25(para)
+msgid "Create a service entry for the Identity Service:"
+msgstr "Identity Service のサービスエントリーを作成します。"
+
+#: ./doc/install-guide/section_keystone-services.xml36(para)
+#: ./doc/install-guide/object-storage/section_object-storage-install.xml89(para)
+msgid ""
+"The service ID is randomly generated and is different from the one shown "
+"here."
+msgstr "サービス ID はランダムに生成され、ここに表示されているものとは異なります。"
+
+#: ./doc/install-guide/section_keystone-services.xml40(para)
+msgid ""
+"Specify an API endpoint for the Identity Service by using the returned "
+"service ID. When you specify an endpoint, you provide URLs for the public "
+"API, internal API, and admin API. In this guide, the "
+"<literal>controller</literal> host name is used. Note that the Identity "
+"Service uses a different port for the admin API."
+msgstr "返されたサービス ID を使用することにより、Identity Service の API エンドポイントを指定します。エンドポイントを指定するとき、パブリック API、内部 API、管理 API の URL を指定します。このガイドでは、<literal>controller</literal> というホスト名を使用します。Identity Service は管理 API 用に異なるポートを使用することに注意してください。"
+
+#: ./doc/install-guide/section_keystone-services.xml63(para)
+msgid ""
+"You will need to create an additional endpoint for each service added to "
+"your OpenStack environment. The sections of this guide associated with the "
+"installation of each service include the endpoint creation step specific to "
+"the service."
+msgstr "お使いの OpenStack 環境に追加した各サービス用の追加のエンドポイントを作成することが必要になります。各サービスのインストールと関連したこのガイドのセクションに、サービスへのエンドポイントの具体的な作成手順があります。"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-api-endpoints.xml29(None)
+msgid ""
+"@@image: 'figures/debconf-screenshots/api-endpoint_1_register_endpoint.png';"
+" md5=d534be231be4f725820a1050fbf44231"
+msgstr "@@image: 'figures/debconf-screenshots/api-endpoint_1_register_endpoint.png'; md5=d534be231be4f725820a1050fbf44231"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-api-endpoints.xml40(None)
+msgid ""
+"@@image: 'figures/debconf-screenshots/api-"
+"endpoint_2_keystone_server_ip.png'; md5=d2c5a5b82dd433fcf9cde6f5ac34c30e"
+msgstr "@@image: 'figures/debconf-screenshots/api-endpoint_2_keystone_server_ip.png'; md5=d2c5a5b82dd433fcf9cde6f5ac34c30e"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-api-endpoints.xml54(None)
+msgid ""
+"@@image: 'figures/debconf-screenshots/api-"
+"endpoint_3_keystone_authtoken.png'; md5=1f3b05ebe671f64d672ac70d246e4f39"
+msgstr "@@image: 'figures/debconf-screenshots/api-endpoint_3_keystone_authtoken.png'; md5=1f3b05ebe671f64d672ac70d246e4f39"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-api-endpoints.xml69(None)
+msgid ""
+"@@image: 'figures/debconf-screenshots/api-"
+"endpoint_4_service_endpoint_ip_address.png'; "
+"md5=6853f0ae2ef8d5fddb22c466d465de15"
+msgstr "@@image: 'figures/debconf-screenshots/api-endpoint_4_service_endpoint_ip_address.png'; md5=6853f0ae2ef8d5fddb22c466d465de15"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/section_debconf-api-endpoints.xml81(None)
+msgid ""
+"@@image: 'figures/debconf-screenshots/api-endpoint_5_region_name.png'; "
+"md5=a6bce0acf5a1cb85f161290f0cf30733"
+msgstr "@@image: 'figures/debconf-screenshots/api-endpoint_5_region_name.png'; md5=a6bce0acf5a1cb85f161290f0cf30733"
+
+#: ./doc/install-guide/section_debconf-api-endpoints.xml6(title)
+msgid "Register API endpoints"
+msgstr "API エンドポイントの登録"
+
+#: ./doc/install-guide/section_debconf-api-endpoints.xml7(para)
+msgid ""
+"All Debian packages for API services, except the <package>heat-api</package>"
+" package, register the service in the Identity Service catalog. This feature"
+" is helpful because API endpoints are difficult to remember."
+msgstr "すべての API サービス用の Debian パッケージは、<package>heat-api</package> パッケージを除き、Identity Service カタログにサービスを登録します。API エンドポイントは覚えにくいので、この機能は役に立ちます。"
+
+#: ./doc/install-guide/section_debconf-api-endpoints.xml12(para)
+msgid ""
+"The <package>heat-common</package> package and not the <package>heat-"
+"api</package> package configures the Orchestration service."
+msgstr "<package>heat-api</package> パッケージではなく、<package>heat-common</package> パッケージが Orchestration Service を設定します。"
+
+#: ./doc/install-guide/section_debconf-api-endpoints.xml16(para)
+msgid ""
+"When you install a package for an API service, you are prompted to register "
+"that service. However, after you install or upgrade the package for an API "
+"service, Debian immediately removes your response to this prompt from the "
+"<package>debconf</package> database. Consequently, you are prompted to re-"
+"register the service with the Identity Service. If you already registered "
+"the API service, respond <literal>no</literal> when you upgrade."
+msgstr "API サービス用のパッケージをインストールするとき、サービスを登録するために、プロンプトが表示されます。しかしながら、API サービス用のパッケージをインストールまたはアップグレードした後、Debian はこのプロンプトの内容を <package>debconf</package> データベースからすぐに削除します。その結果として、Identity Service でサービスを設定するためにプロンプトが表示されます。すでに API サービスを登録していれば、アップグレードするときに <literal>no</literal> と答えます。"
+
+#: ./doc/install-guide/section_debconf-api-endpoints.xml33(para)
+msgid "This screen registers packages in the Identity Service catalog:"
+msgstr "この画面は Identity Service カタログにパッケージを登録します。"
+
+#: ./doc/install-guide/section_debconf-api-endpoints.xml44(para)
+msgid ""
+"You are prompted for the Identity Service <literal>admin_token</literal> "
+"value. The Identity Service uses this value to register the API service. "
+"When you set up the <package>keystone</package> package, this value is "
+"configured automatically."
+msgstr "Identity Service の <literal>admin_token</literal> 値に対するプロンプトが表示されます。Identity Service が API サービスを登録するためにこの値を使用します。<package>keystone</package> パッケージをセットアップするとき、この値が自動的に設定されます。"
+
+#: ./doc/install-guide/section_debconf-api-endpoints.xml58(para)
+msgid ""
+"This screen configures the IP addresses for the service. The configuration "
+"script automatically detects the IP address used by the interface that is "
+"connected to the default route (<code>/sbin/route</code> and "
+"<code>/sbin/ip</code>)."
+msgstr "この画面はサービスの IP アドレスを設定します。設定スクリプトは自動的に、デフォルトルートに接続されているインターフェースにより使用されている IP アドレスを検出します (<code>/sbin/route</code> と <code>/sbin/ip</code>)。"
+
+#: ./doc/install-guide/section_debconf-api-endpoints.xml62(para)
+msgid ""
+"Unless you have a unique set up for your network, press "
+"<keycap>ENTER</keycap>."
+msgstr "お使いのネットワーク用に一意なセットアップをする必要がなければ、<keycap>ENTER</keycap> を押します。"
+
+#: ./doc/install-guide/section_debconf-api-endpoints.xml73(para)
+msgid ""
+"This screen configures the region name for the service. For example, <code"
+">us-east-coast</code> or <code>europe-paris</code>."
+msgstr "この画面はサービス用のリージョン名を設定します。例えば、<code>us-east-coast</code> や <code>europe-paris</code> です。"
 
 #: ./doc/install-guide/section_neutron-ovs-network-node.xml8(para)
 msgid ""
@@ -5128,1090 +7629,6 @@ msgstr "自己署名証明書を用いた HTTPS 経由で OpenStack Networking A
 msgid "Add this statement to the <literal>[DEFAULT]</literal> section:"
 msgstr "このステートメントを <literal>[DEFAULT]</literal> セクションに追加します。"
 
-#: ./doc/install-guide/section_nova-networking-controller-node.xml6(para)
-msgid ""
-"Legacy networking primarily involves compute nodes. However, you must "
-"configure the controller node to use it."
-msgstr "レガシーネットワークは、主にコンピュートノードを関係します。しかしながら、それを使用するために、コントローラーノードを設定する必要があります。"
-
-#: ./doc/install-guide/section_debconf-concepts.xml7(title)
-msgid "debconf concepts"
-msgstr "debconf の概念"
-
-#: ./doc/install-guide/section_debconf-concepts.xml8(para)
-msgid ""
-"This chapter explains how to use the Debian <systemitem "
-"class=\"library\">debconf</systemitem> and <systemitem class=\"library"
-"\">dbconfig-common</systemitem> packages to configure OpenStack services. "
-"These packages enable users to perform configuration tasks. When users "
-"install OpenStack packages, <package>debconf</package> prompts the user for "
-"responses, which seed the contents of configuration files associated with "
-"that package. After package installation, users can update the configuration"
-" of a package by using the <placeholder-1/> program."
-msgstr "本章は OpenStack サービスを設定するために Debian の <systemitem class=\"library\">debconf</systemitem> と <systemitem class=\"library\">dbconfig-common</systemitem> を使用する方法について説明します。これらのパッケージによりユーザーが設定作業を実行できます。ユーザーが OpenStack パッケージをインストールするとき、<package>debconf</package> がユーザーにプロンプトを表示します。これは、パッケージに関連づけられた設定ファイルの内容をシードします。パッケージのインストール後、ユーザーは <placeholder-1/> プログラムを使用することにより、パッケージの設定を更新できます。"
-
-#: ./doc/install-guide/section_debconf-concepts.xml18(para)
-msgid ""
-"If you are familiar with these packages and pre-seeding, you can proceed to "
-"<xref linkend=\"ch_keystone\"/>."
-msgstr "これらのパッケージと事前シードに慣れている場合、<xref linkend=\"ch_keystone\"/> に進むことができます。"
-
-#: ./doc/install-guide/section_debconf-concepts.xml21(title)
-msgid "The Debian packages"
-msgstr "Debian パッケージ"
-
-#: ./doc/install-guide/section_debconf-concepts.xml22(para)
-msgid ""
-"The rules described here are from the <link href=\"http://www.debian.org/doc"
-"/debian-policy/\"><citetitle>Debian Policy Manual</citetitle></link>. If any"
-" rule described in this chapter is not respected, you have found a serious "
-"bug that must be fixed."
-msgstr "ここに記載されたルールは <link href=\"http://www.debian.org/doc/debian-policy/\"><citetitle>Debian Policy Manual</citetitle></link> からのものです。本章に記載された何らかのルールが関係しなければ、修正すべき深刻なバグを見つけましたことになります。"
-
-#: ./doc/install-guide/section_debconf-concepts.xml27(para)
-msgid ""
-"When you install or upgrade a Debian package, all configuration file values "
-"are preserved. Using the <systemitem class=\"library\">debconf</systemitem> "
-"database as a registry is considered a bug in Debian. If you edit something "
-"in any OpenStack configuration file, the <systemitem "
-"class=\"library\">debconf</systemitem> package reads that value when it "
-"prepares to prompt the user. For example, to change the log in name for the "
-"RabbitMQ messaging queue for a service, you can edit its value in the "
-"corresponding configuration file."
-msgstr "Debian パッケージをインストールまたはアップグレードするとき、すべての設定値は保護されます。レジストリとして <systemitem class=\"library\">debconf</systemitem> データベースを使用することは Debian でバグとみなされます。あらゆる OpenStack 設定ファイルで何かを編集する場合、ユーザーにプロンプトを表示するとき、<systemitem class=\"library\">debconf</systemitem> パッケージがその値を読み込みます。例えば、サービス用の RabbitMQ メッセージングキューの名前でログを変更するために、対応する設定ファイルでその値を編集できます。"
-
-#: ./doc/install-guide/section_debconf-concepts.xml36(para)
-msgid ""
-"To opt out of using the <systemitem class=\"library\">debconf</systemitem> "
-"package, run the <placeholder-1/> command and select non-interactive mode:"
-msgstr "<systemitem class=\"library\">debconf</systemitem> パッケージを使用することを止めるために、<placeholder-1/> コマンドを実行し、非対話モードを選択します。"
-
-#: ./doc/install-guide/section_debconf-concepts.xml41(para)
-msgid ""
-"Then, <systemitem class=\"library\">debconf</systemitem> does not prompt "
-"you."
-msgstr "そして、<systemitem class=\"library\">debconf</systemitem> がプロンプトを表示しなくなります。"
-
-#: ./doc/install-guide/section_debconf-concepts.xml43(para)
-msgid ""
-"Another way to disable the <systemitem "
-"class=\"library\">debconf</systemitem> package is to prefix the "
-"<placeholder-1/> command with "
-"<literal>DEBIAN_FRONTEND=noninteractive</literal>, as follows:"
-msgstr "<systemitem class=\"library\">debconf</systemitem> を無効化する別の方法は、以下のように <placeholder-1/> コマンドに <literal>DEBIAN_FRONTEND=noninteractive</literal> を付けることです。"
-
-#: ./doc/install-guide/section_debconf-concepts.xml49(para)
-msgid ""
-"If you configure a package with <systemitem "
-"class=\"library\">debconf</systemitem> incorrectly, you can re-configure it,"
-" as follows:"
-msgstr "<systemitem class=\"library\">debconf</systemitem> を用いて誤って設定した場合、以下のように再設定できます。"
-
-#: ./doc/install-guide/section_debconf-concepts.xml52(replaceable)
-msgid "PACKAGE-NAME"
-msgstr "PACKAGE-NAME"
-
-#: ./doc/install-guide/section_debconf-concepts.xml53(para)
-msgid ""
-"This calls the post-installation script for the <replaceable>PACKAGE-"
-"NAME</replaceable> package after the user responds to all prompts. If you "
-"cannot install a Debian package in a non-interactive way, you have found a "
-"release-critical bug in Debian. Report it to the Debian bug tracking system."
-msgstr "これはユーザーがすべてのプロンプトに答えた後、<replaceable>PACKAGE-NAME</replaceable> パッケージ用のインストール後スクリプトを呼び出します。非対話的な方法で Debian パッケージをインストールできない場合、Debian で深刻なリリースのバグを見つけたことになります。Debian のバグ追跡システムに報告してください。"
-
-#: ./doc/install-guide/section_debconf-concepts.xml58(para)
-msgid ""
-"Generally, the <systemitem class=\"library\">-common</systemitem> packages "
-"install the configuration files. For example, the <literal>glance-"
-"common</literal> package installs the <filename>glance-api.conf</filename> "
-"and <filename>glance-registry.conf</filename> files. So, for the Image "
-"Service, you must re-configure the <literal>glance-common</literal> package."
-" The same applies for <literal>cinder-common</literal>, <literal>nova-"
-"common</literal>, and <literal>heat-common</literal> packages."
-msgstr "一般的に、<systemitem class=\"library\">-common</systemitem> パッケージが設定ファイルをインストールします。例えば、<literal>glance-common</literal> パッケージが <filename>glance-api.conf</filename> と <filename>glance-registry.conf</filename> ファイルをインストールします。そのため、Image Service 用に <literal>glance-common</literal> パッケージを再設定する必要があります。同じことを <literal>cinder-common</literal>、<literal>nova-common</literal>、<literal>heat-common</literal> パッケージに適用します。"
-
-#: ./doc/install-guide/section_debconf-concepts.xml68(para)
-msgid ""
-"In <systemitem class=\"library\">debconf</systemitem>, the higher the "
-"priority for a screen, the greater the chance that the user sees that "
-"screen. If a <systemitem class=\"library\">debconf</systemitem> screen has "
-"<literal>medium</literal> priority and you configure the Debian system to "
-"show only <literal>critical</literal> prompts, which is the default in "
-"Debian, the user does not see that <systemitem "
-"class=\"library\">debconf</systemitem> screen. Instead, the default for the "
-"related package is used. In the Debian OpenStack packages, a number of "
-"<systemitem class=\"library\">debconf</systemitem> screens are set with "
-"<literal>medium</literal> priority. Consequently, if you want to respond to "
-"all <systemitem class=\"library\">debconf</systemitem> screens from the "
-"Debian OpenStack packages, you must run the following command and select the"
-" <literal>medium</literal> priority before you install any packages:"
-msgstr "<systemitem class=\"library\">debconf</systemitem> では、画面の優先度が高ければ高いほど、ユーザーがその画面を参照する機会が増えます。<systemitem class=\"library\">debconf</systemitem> 画面が <literal>medium</literal> (中) の優先度を持ち、Debian システムが <literal>critical</literal> (重要) のプロンプトのみを表示するよう設定している場合、その <systemitem class=\"library\">debconf</systemitem> 画面が表示されません。代わりに、関連パッケージのデフォルトが使用されます。Debian OpenStack パッケージの場合、数多くの <systemitem class=\"library\">debconf</systemitem> 画面が <literal>medium</literal> 優先度に設定されています。そのため、Debian OpenStack パッケージのすべての <systemitem class=\"library\">debconf</systemitem> 画面をプロンプト表示したい場合、何らかのパッケージをインストールする前に、以下のコマンドを実行し、<literal>medium</literal> 優先度を選択する必要があります。"
-
-#: ./doc/install-guide/section_debconf-concepts.xml87(para)
-msgid ""
-"The packages do not require pre-depends. If <systemitem class=\"library"
-"\">dbconfig-common</systemitem> is already installed on the system, the user"
-" sees all prompts. However, you cannot define the order in which the "
-"<systemitem class=\"library\">debconf</systemitem> screens appear. The user "
-"must make sense of it even if the prompts appear in an illogical order."
-msgstr "パッケージは事前の依存関係を必要としません。<systemitem class=\"library\">dbconfig-common</systemitem> がすでにシステムにインストールされていれば、すべてのプロンプトが表示されます。しかしながら、<systemitem class=\"library\">debconf</systemitem> 画面が表示される順番を定義できません。プロンプトが非論理的な順番で表示されたときでさえ、ユーザーはその意味を理解する必要があります。"
-
-#: ./doc/install-guide/section_ceilometer-swift.xml6(title)
-msgid "Configure the Object Storage service for Telemetry"
-msgstr "Telemetry 用 Object Storage Service の設定"
-
-#: ./doc/install-guide/section_ceilometer-swift.xml9(para)
-msgid ""
-"To retrieve object store statistics, the Telemetry service needs access to "
-"Object Storage with the <literal>ResellerAdmin</literal> role. Give this "
-"role to your <literal>os_username</literal> user for the "
-"<literal>os_tenant_name</literal> tenant:"
-msgstr "オブジェクトストアの統計情報を取得するためには、Telemetry Service が <literal>ResellerAdmin</literal> ロールで Object Storage にアクセスする必要があります。このロールを <literal>os_tenant_name</literal> プロジェクトの <literal>os_username</literal> ユーザーに与えます。"
-
-#: ./doc/install-guide/section_ceilometer-swift.xml23(replaceable)
-msgid "462fa46c13fd4798a95a3bfbe27b5e54"
-msgstr "462fa46c13fd4798a95a3bfbe27b5e54"
-
-#: ./doc/install-guide/section_ceilometer-swift.xml26(para)
-msgid ""
-"You must also add the Telemetry middleware to Object Storage to handle "
-"incoming and outgoing traffic. Add these lines to the <filename>/etc/swift"
-"/proxy-server.conf</filename> file:"
-msgstr "入力通信と出力通信を処理するために、Telemetry ミドルウェアを Object Storage に追加する必要もあります。これらの行を <filename>/etc/swift/proxy-server.conf</filename> ファイルに追加します。"
-
-#: ./doc/install-guide/section_ceilometer-swift.xml35(para)
-msgid ""
-"Add <literal>ceilometer</literal> to the <literal>pipeline</literal> "
-"parameter of that same file:"
-msgstr "<literal>ceilometer</literal> を同じファイルの <literal>pipeline</literal> パラメーターに追加します。"
-
-#: ./doc/install-guide/section_ceilometer-swift.xml41(para)
-#: ./doc/install-guide/section_heat-install.xml180(para)
-#: ./doc/install-guide/section_ceilometer-nova.xml137(para)
-msgid "Restart the service with its new settings:"
-msgstr "新しい設定を用いてサービスを再起動します。"
-
-#: ./doc/install-guide/section_debconf-preseeding.xml6(title)
-msgid "Pre-seed debconf prompts"
-msgstr "事前シード debconf プロンプト"
-
-#: ./doc/install-guide/section_debconf-preseeding.xml7(para)
-msgid ""
-"You can pre-seed all <systemitem class=\"library\">debconf</systemitem> "
-"prompts. To pre-seed means to store responses in the "
-"<package>debconf</package> database so that <package>debconf</package> does "
-"not prompt the user for responses. Pre-seeding enables a hands-free "
-"installation for users. The package maintainer creates scripts that "
-"automatically configure the services."
-msgstr "すべての <systemitem class=\"library\">debconf</systemitem> プロンプトに事前シードできます。事前シードとは <package>debconf</package> がユーザーにプロンプトを表示しないよう、<package>debconf</package> データベースに応答を保存することを意味します。事前シードによりユーザーの手がかからないインストールをできるようになります。パッケージのメンテナーがサービスを自動的に設定できるスクリプトを作成します。"
-
-#: ./doc/install-guide/section_debconf-preseeding.xml14(para)
-msgid ""
-"The following example shows how to pre-seed an automated MySQL Server "
-"installation:"
-msgstr "以下の例は MySQL サーバーの自動インストールを事前シードする方法を示します。"
-
-#: ./doc/install-guide/section_debconf-preseeding.xml16(replaceable)
-#: ./doc/install-guide/section_debconf-preseeding.xml17(replaceable)
-#: ./doc/install-guide/section_debconf-preseeding.xml19(replaceable)
-msgid "MYSQL_PASSWORD"
-msgstr "MYSQL_PASSWORD"
-
-#: ./doc/install-guide/section_debconf-preseeding.xml23(para)
-msgid ""
-"The <code>seen true</code> option tells <package>debconf</package> that a "
-"specified screen was already seen by the user so do not show it again. This "
-"option is useful for upgrades."
-msgstr "<code>seen true</code> オプションにより、指定された画面がすでにユーザーにより参照されたことを <package>debconf</package> に通知します。そのため、それを再び表示しません。このオプションはアップグレードのために有用です。"
-
-#: ./doc/install-guide/ch_basics.xml5(title)
-msgid "Basic environment configuration"
-msgstr "環境の基本設定"
-
-#: ./doc/install-guide/ch_basics.xml6(para)
-msgid ""
-"This chapter explains how to configure each node in the <link linkend"
-"=\"architecture_example-architectures\">example architectures</link> "
-"including the <link linkend=\"example-architecture-with-legacy-networking\">"
-" two-node architecture with legacy networking</link> and <link linkend"
-"=\"example-architecture-with-neutron-networking\">three-node architecture "
-"with OpenStack Networking (neutron)</link>."
-msgstr "本章は、<link linkend=\"architecture_example-architectures\">アーキテクチャー例</link>にある各ノードを設定する方法について説明します。<link linkend=\"example-architecture-with-legacy-networking\"> レガシーネットワークを持つ 2 ノードアーキテクチャー</link>と<link linkend=\"example-architecture-with-neutron-networking\">OpenStack Networking (neutron) を持つ 3 ノードアーキテクチャー</link>があります。"
-
-#: ./doc/install-guide/ch_basics.xml13(para)
-msgid ""
-"Although most environments include OpenStack Identity, Image Service, "
-"Compute, at least one networking service, and the dashboard, OpenStack "
-"Object Storage can operate independently of most other services. If your use"
-" case only involves Object Storage, you can skip to <xref linkend=\"object-"
-"storage-system-requirements\"/>. However, the dashboard will not work "
-"without at least OpenStack Image Service and Compute."
-msgstr "ほとんどの環境には、OpenStack Identity、Image Service、Compute、少なくとも 1 つのネットワークサービス、ダッシュボードがありますが、OpenStack Object Storage は他のほとんどのサービスと独立して動作できます。Object Storage のみを含むユースケースの場合、<xref linkend=\"object-storage-system-requirements\"/> まで進めます。しかしながらダッシュボードは、少なくとも OpenStack Image Service と Compute がないと動作しません。"
-
-#: ./doc/install-guide/ch_basics.xml22(para)
-msgid ""
-"You must use an account with administrative privileges to configure each "
-"node. Either run the commands as the <literal>root</literal> user or "
-"configure the <literal>sudo</literal> utility."
-msgstr "各ノードを設定するために、管理権限を持つアカウントを使用する必要があります。<literal>root</literal> ユーザーとしてコマンドを実行するか、<literal>sudo</literal> ユーティリティを設定します。"
-
-#: ./doc/install-guide/section_cinder-node.xml6(title)
-msgid "Configure a Block Storage service node"
-msgstr "Block Storage Service ノードの設定"
-
-#: ./doc/install-guide/section_cinder-node.xml7(para)
-msgid ""
-"After you configure the services on the controller node, configure a second "
-"system to be a Block Storage service node. This node contains the disk that "
-"serves volumes."
-msgstr "コントローラーノードでサービスを設定した後、Block Storage Service のノードとなる 2 番目のシステムを設定します。このノードはボリュームを取り扱うディスクを有します。"
-
-#: ./doc/install-guide/section_cinder-node.xml10(para)
-#: ./doc/install-guide/section_cinder-controller.xml16(para)
-msgid ""
-"You can configure OpenStack to use various storage systems. This example "
-"uses LVM."
-msgstr "さまざまなストレージシステムを使用するよう OpenStack を設定できます。この例は LVM を使用します。"
-
-#: ./doc/install-guide/section_cinder-node.xml14(para)
-msgid ""
-"Use the instructions in <xref linkend=\"ch_basics\"/> to configure the "
-"system. Note the following differences from the installation instructions "
-"for the controller node:"
-msgstr "システムを設定するために <xref linkend=\"ch_basics\"/> にある方法を使用します。以下の項目はコントローラーノードのインストール説明と異なることに注意してください。"
-
-#: ./doc/install-guide/section_cinder-node.xml19(para)
-msgid ""
-"Set the host name to <literal>block1</literal> and use "
-"<literal>10.0.0.41</literal> as IP address on the management network "
-"interface. Ensure that the IP addresses and host names for both controller "
-"node and Block Storage service node are listed in the "
-"<filename>/etc/hosts</filename> file on each system."
-msgstr "ホスト名を <literal>block1</literal> に設定し、管理ネットワークのインターフェースの IP アドレスとして <literal>10.0.0.41</literal> を使用します。コントローラーノードと Block Storage サービスノードの IP アドレスとホスト名が各システムの <filename>/etc/hosts</filename> にあることを確認します。"
-
-#: ./doc/install-guide/section_cinder-node.xml27(para)
-msgid ""
-"Follow the instructions in <xref linkend=\"basics-ntp\"/> to synchronize "
-"from the controller node."
-msgstr "コントローラーノードから同期するために、<xref linkend=\"basics-ntp\"/> にある説明に従います。"
-
-#: ./doc/install-guide/section_cinder-node.xml33(para)
-msgid "Install the required LVM packages, if they are not already installed:"
-msgstr "必要となる LVM パッケージがまだインストールされていなければ、それらをインストールします。"
-
-#: ./doc/install-guide/section_cinder-node.xml38(para)
-msgid ""
-"Create the LVM physical and logical volumes. This guide assumes a second "
-"disk <literal>/dev/sdb</literal> that is used for this purpose:"
-msgstr "LVM の物理ボリュームと論理ボリュームを作成します。このガイドはこの目的のために使用される 2 番目のディスク <literal>/dev/sdb</literal> を仮定します。"
-
-#: ./doc/install-guide/section_cinder-node.xml45(para)
-msgid ""
-"Add a filter entry to the <literal>devices</literal> section in the "
-"<filename>/etc/lvm/lvm.conf</filename> file to keep LVM from scanning "
-"devices used by virtual machines:"
-msgstr "仮想マシンにより使用されるデバイスをスキャンすることから LVM を保護するために、<filename>/etc/lvm/lvm.conf</filename> ファイルの <literal>devices</literal> セクションにフィルター項目を追加します。"
-
-#: ./doc/install-guide/section_cinder-node.xml55(para)
-msgid ""
-"You must add required physical volumes for LVM on the Block Storage host. "
-"Run the <placeholder-1/> command to get a list or required volumes."
-msgstr "Block Storage のホストに LVM 用に必要となる物理ボリュームを追加する必要があります。必要となるボリュームの一覧を取得するために <placeholder-1/> コマンドを実行します。"
-
-#: ./doc/install-guide/section_cinder-node.xml59(para)
-msgid ""
-"Each item in the filter array starts with either an <literal>a</literal> for"
-" accept, or an <literal>r</literal> for reject. The physical volumes that "
-"are required on the Block Storage host have names that begin with "
-"<literal>a</literal>. The array must end with \"<literal>r/.*/</literal>\" "
-"to reject any device not listed."
-msgstr "フィルター配列にある各項目は、許可するために <literal>a</literal> から、拒否するために <literal>r</literal> から始まります。Block Storage のホストで必要となる物理ボリュームは <literal>a</literal> から始まる名前を持つ必要があります。配列は一覧に無いすべてのデバイスを拒否するために \"<literal>r/.*/</literal>\" で終わる必要があります。"
-
-#: ./doc/install-guide/section_cinder-node.xml66(para)
-msgid ""
-"In this example, <literal>/dev/sda1</literal> is the volume where the "
-"volumes for the operating system for the node reside, while "
-"<literal>/dev/sdb</literal> is the volume reserved for <literal>cinder-"
-"volumes</literal>."
-msgstr "この例では、<literal>/dev/sda1</literal> がノードのオペレーティングシステム用のボリュームが置かれるボリュームです。<literal>/dev/sdb</literal> は <literal>cinder-volumes</literal> のために予約されたボリュームです。"
-
-#: ./doc/install-guide/section_cinder-node.xml72(para)
-msgid ""
-"After you configure the operating system, install the appropriate packages "
-"for the Block Storage service:"
-msgstr "オペレーティングシステムの設定後、Block Storage Service 向けに適切なパッケージをインストールします。"
-
-#: ./doc/install-guide/section_cinder-node.xml79(para)
-msgid ""
-"Respond to the <systemitem class=\"library\">debconf</systemitem> prompts "
-"about the <link linkend=\"debconf-dbconfig-common\">database "
-"management</link>, <link linkend=\"debconf-"
-"keystone_authtoken\"><literal>[keystone_authtoken]</literal> "
-"settings</link>, and <link linkend=\"debconf-rabbitqm\">RabbitMQ "
-"credentials</link>. Make sure to enter the same details as you did for your "
-"Block Storage service controller node."
-msgstr "<link linkend=\"debconf-dbconfig-common\">データベース管理</link>、<link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> 設定</link>、<link linkend=\"debconf-rabbitqm\">RabbitMQ クレデンシャル</link>に関する <systemitem class=\"library\">debconf</systemitem> プロンプトに答えます。必ず Block Storage のコントローラーノードと同じように入力します。"
-
-#: ./doc/install-guide/section_cinder-node.xml87(para)
-msgid ""
-"Another screen prompts you for the <systemitem class=\"library\">volume-"
-"group</systemitem> to use. The Debian package configuration script detects "
-"every active volume group and tries to use the first one it sees, provided "
-"that the <systemitem class=\"library\">lvm2</systemitem> package was "
-"installed before Block Storage. This should be the case if you configured "
-"the volume group first, as this guide recommends."
-msgstr "使用する <systemitem class=\"library\">volume-group</systemitem> を選択するプロンプトが別の画面に表示されます。Debian パッケージの設定スクリプトは、すべての動作中のボリュームグループを検知し、最初に認識したものを使用しようとします。<systemitem class=\"library\">lvm2</systemitem> パッケージが Block Storage の前にインストールされます。このガイドが推奨しているとおり、ボリュームグループを最初に設定する場合、このようになります。"
-
-#: ./doc/install-guide/section_cinder-node.xml94(para)
-msgid ""
-"If you have only one active volume group on your Block Storage service node,"
-" you do not need to manually enter its name when you install the <systemitem"
-" class=\"service\">cinder-volume</systemitem> package because it is detected"
-" automatically. If no <systemitem class=\"library\">volume-"
-"group</systemitem> is available when you install <systemitem class=\"service"
-"\">cinder-common</systemitem>, you must use <placeholder-1/> to manually "
-"configure or re-configure <systemitem class=\"service\">cinder-"
-"common</systemitem>."
-msgstr "Block Storage のノードに動作中のボリュームグループが 1 つしかなければ、自動的に検出されるため、<systemitem class=\"service\">cinder-volume</systemitem> パッケージのインストール時にその名前を入力する必要がありません。<systemitem class=\"service\">cinder-common</systemitem> のインストール時に、<systemitem class=\"library\">volume-group</systemitem> が利用できなければ、手動で設定するか、<systemitem class=\"service\">cinder-common</systemitem> を再設定するために、<placeholder-1/> を使用する必要があります。"
-
-#: ./doc/install-guide/section_cinder-node.xml106(para)
-msgid ""
-"Copy the <filename>/etc/cinder/cinder.conf</filename> configuration file "
-"from the controller, or perform the following steps to set the keystone "
-"credentials:"
-msgstr "<filename>/etc/cinder/cinder.conf</filename> 設定ファイルをコントローラーからコピーします。または、keystone のクレデンシャルを設定するために、以下の手順を実行します。"
-
-#: ./doc/install-guide/section_cinder-node.xml125(replaceable)
-#: ./doc/install-guide/section_cinder-node.xml137(replaceable)
-#: ./doc/install-guide/section_cinder-controller.xml74(replaceable)
-#: ./doc/install-guide/section_cinder-controller.xml95(replaceable)
-#: ./doc/install-guide/section_cinder-controller.xml107(replaceable)
-msgid "CINDER_PASS"
-msgstr "CINDER_PASS"
-
-#: ./doc/install-guide/section_cinder-node.xml126(para)
-#: ./doc/install-guide/section_cinder-controller.xml96(para)
-msgid ""
-"Edit the <filename>/etc/cinder/cinder.conf</filename> configuration file and"
-" add this section for keystone credentials:"
-msgstr "<filename>/etc/cinder/cinder.conf</filename> 設定ファイルを編集し、keystone クレデンシャル用のこのセクションを追加します。"
-
-#: ./doc/install-guide/section_cinder-node.xml140(para)
-#: ./doc/install-guide/section_cinder-controller.xml110(para)
-#: ./doc/install-guide/section_cinder-controller.xml134(para)
-msgid "Configure Block Storage to use the RabbitMQ message broker."
-msgstr "Block Storage が RabbitMQ メッセージブローカーを使用するよう設定します。"
-
-#: ./doc/install-guide/section_cinder-node.xml142(para)
-msgid ""
-"In the <literal>[DEFAULT]</literal> configuration section of the "
-"<filename>/etc/cinder/cinder.conf</filename> file, set these configuration "
-"keys and replace <replaceable>RABBIT_PASS</replaceable> with the password "
-"you chose for RabbitMQ:"
-msgstr "<filename>/etc/cinder/cinder.conf</filename> ファイルの <literal>[DEFAULT]</literal> 設定セクションで、これらの設定キーを設定し、<replaceable>RABBIT_PASS</replaceable> を RabbitMQ 用に選択したパスワードに置き換えます。"
-
-#: ./doc/install-guide/section_cinder-node.xml156(para)
-#: ./doc/install-guide/section_cinder-controller.xml126(para)
-msgid "Configure Block Storage to use the Qpid message broker:"
-msgstr "Qpid メッセージブローカーを使用するよう Block Storage を設定します。"
-
-#: ./doc/install-guide/section_cinder-node.xml164(para)
-msgid ""
-"Configure Block Storage to use the RabbitMQ message broker. Replace "
-"<replaceable>RABBIT_PASS</replaceable> with the password you chose for "
-"RabbitMQ:"
-msgstr "RabbitMQ メッセージブローカーを使用するよう Block Storage を設定します。<replaceable>RABBIT_PASS</replaceable> を RabbitMQ 用に選んだパスワードで置き換えます。"
-
-#: ./doc/install-guide/section_cinder-node.xml177(para)
-msgid ""
-"Configure Block Storage to use your MySQL database. Edit the "
-"<filename>/etc/cinder/cinder.conf</filename> file and add the following key "
-"to the <literal>[database]</literal> section. Replace "
-"<replaceable>CINDER_DBPASS</replaceable> with the password you chose for the"
-" Block Storage database:"
-msgstr "Block Storage が MySQL データベースを使用するよう設定します。<filename>/etc/cinder/cinder.conf</filename> ファイルを編集し、以下のキーを <literal>[database]</literal> セクションに追加します。Block Storage データベース用に選択したパスワードで <replaceable>CINDER_DBPASS</replaceable> を置き換えます。"
-
-#: ./doc/install-guide/section_cinder-node.xml183(replaceable)
-#: ./doc/install-guide/section_cinder-node.xml186(replaceable)
-#: ./doc/install-guide/section_cinder-controller.xml44(replaceable)
-#: ./doc/install-guide/section_cinder-controller.xml47(replaceable)
-#: ./doc/install-guide/section_cinder-controller.xml59(replaceable)
-#: ./doc/install-guide/section_cinder-controller.xml61(replaceable)
-msgid "CINDER_DBPASS"
-msgstr "CINDER_DBPASS"
-
-#: ./doc/install-guide/section_cinder-node.xml188(para)
-#: ./doc/install-guide/section_cinder-controller.xml48(para)
-msgid ""
-"In some distributions, the <filename>/etc/cinder/cinder.conf</filename> file"
-" does not include the <literal>[database]</literal> section header. You must"
-" add this section header to the end of the file before you proceed."
-msgstr "いくつかのディストリビューションは、<filename>/etc/cinder/cinder.conf</filename> ファイルに <literal>[database]</literal> セクションヘッダーが含まれません。ここから進む前に、このセクションヘッダーをファイルの最後に追加する必要があります。"
-
-#: ./doc/install-guide/section_cinder-node.xml196(para)
-msgid ""
-"Configure Block Storage to use the Image Service. Block Storage needs access"
-" to images to create bootable volumes. Edit the "
-"<filename>/etc/cinder/cinder.conf</filename> file and update the "
-"<option>glance_host</option> option in the <literal>[DEFAULT]</literal> "
-"section:"
-msgstr "Image Service を使用するよう Block Storage を設定します。Block Storage は、ブート可能なボリュームを作成するために、イメージにアクセスする必要があります。<filename>/etc/cinder/cinder.conf</filename> ファイルを編集し、<literal>[DEFAULT]</literal> セクションの <option>glance_host</option> オプションを更新します。"
-
-#: ./doc/install-guide/section_cinder-node.xml208(para)
-#: ./doc/install-guide/section_cinder-controller.xml168(para)
-msgid "Restart the Block Storage services with the new settings:"
-msgstr "新しい設定を用いて Block Storage のサービスを再起動します。"
-
-#: ./doc/install-guide/section_cinder-node.xml214(para)
-msgid ""
-"Configure the iSCSI target service to discover Block Storage volumes. Add "
-"the following line to the beginning of the "
-"<filename>/etc/tgt/targets.conf</filename> file, if it is not already "
-"present:"
-msgstr "Block Storage ボリュームを探索するよう iSCSI ターゲットサービスを設定します。まだ存在しなければ、以下の行を <filename>/etc/tgt/targets.conf</filename> の最初に追加します。"
-
-#: ./doc/install-guide/section_cinder-node.xml221(para)
-#: ./doc/install-guide/section_cinder-controller.xml174(para)
-msgid ""
-"Start and configure the Block Storage services to start when the system "
-"boots:"
-msgstr "Block Storage のサービスを起動し、システム起動時に起動するよう設定します。"
-
-#: ./doc/install-guide/section_cinder-controller.xml5(title)
-msgid "Configure a Block Storage service controller"
-msgstr "Block Storage Service コントローラーの設定"
-
-#: ./doc/install-guide/section_cinder-controller.xml7(para)
-msgid ""
-"This scenario configures OpenStack Block Storage services on the <glossterm "
-"baseform=\"controller node\">Controller node</glossterm> and assumes that a "
-"second node provides storage through the <systemitem class=\"service"
-"\">cinder-volume</systemitem> service."
-msgstr "このシナリオは、<glossterm baseform=\"controller node\">コントローラーノード</glossterm>に OpenStack Block Storage を設定します。2 番目のノードが <systemitem class=\"service\">cinder-volume</systemitem> サービス経由でストレージを提供すると仮定します。"
-
-#: ./doc/install-guide/section_cinder-controller.xml12(para)
-msgid ""
-"For instructions on how to configure the second node, see <xref linkend"
-"=\"cinder-node\"/>."
-msgstr "2 番目のノードを設定する方法は <xref linkend=\"cinder-node\"/> を参照してください。"
-
-#: ./doc/install-guide/section_cinder-controller.xml20(para)
-msgid "Install the appropriate packages for the Block Storage service:"
-msgstr "Block Storage Service のために適切なパッケージをインストールします。"
-
-#: ./doc/install-guide/section_cinder-controller.xml27(para)
-msgid ""
-"Respond to the prompts for database management, "
-"<literal>[keystone_authtoken]</literal> settings, RabbitMQ credentials and "
-"API endpoint registration."
-msgstr "データベース管理、<literal>[keystone_authtoken]</literal> 設定、RabbitMQ クレデンシャル、API エンドポイントの登録に関するプロンプトに答えます。"
-
-#: ./doc/install-guide/section_cinder-controller.xml31(para)
-msgid "Configure Block Storage to use your database."
-msgstr "お使いのデータベースを使用するよう Block Storage を設定します。"
-
-#: ./doc/install-guide/section_cinder-controller.xml32(para)
-msgid ""
-"Run the following command to set <literal>connection</literal> option in the"
-" <literal>[database]</literal> section, which is in the "
-"<filename>/etc/cinder/cinder.conf</filename> file, replace "
-"<replaceable>CINDER_DBPASS</replaceable> with the password for the Block "
-"Storage database that you will create in a later step:"
-msgstr "<filename>/etc/cinder/cinder.conf</filename> ファイルにある、<literal>[database]</literal> セクションの <literal>connection</literal> オプションを設定するために、以下のコマンドを実行します。後の手順で作成する Block Storage データベース用のパスワードで <replaceable>CINDER_DBPASS</replaceable> を置き換えます。"
-
-#: ./doc/install-guide/section_cinder-controller.xml38(para)
-msgid ""
-"In the <filename>/etc/cinder/cinder.conf</filename> file, set the "
-"<literal>connection</literal> option in the <literal>[database]</literal> "
-"section and replace <replaceable>CINDER_DBPASS</replaceable> with the "
-"password for the Block Storage database that you will create in a later "
-"step:"
-msgstr "<filename>/etc/cinder/cinder.conf</filename> ファイルで、<literal>[database]</literal> セクションの <literal>connection</literal> オプションを設定します。後の手順で作成する Block Storage データベース用のパスワードで <replaceable>CINDER_DBPASS</replaceable> を置き換えます。"
-
-#: ./doc/install-guide/section_cinder-controller.xml54(para)
-msgid ""
-"Use the password that you set to log in as root to create a "
-"<literal>cinder</literal> database:"
-msgstr "<literal>cinder</literal> データベースを作成するために、root としてログインするために設定したパスワードを使用します。"
-
-#: ./doc/install-guide/section_cinder-controller.xml64(para)
-msgid "Create the database tables for the Block Storage service:"
-msgstr "Block Storage 用のデータベースのテーブルを作成します。"
-
-#: ./doc/install-guide/section_cinder-controller.xml69(para)
-msgid "Create a <literal>cinder</literal> user."
-msgstr "<literal>cinder</literal> ユーザーを作成します。"
-
-#: ./doc/install-guide/section_cinder-controller.xml70(para)
-msgid ""
-"The Block Storage service uses this user to authenticate with the Identity "
-"service."
-msgstr "Block Storage は、Identity で認証するために、このユーザーを使用します。"
-
-#: ./doc/install-guide/section_cinder-controller.xml72(para)
-msgid ""
-"Use the <literal>service</literal> tenant and give the user the "
-"<literal>admin</literal> role:"
-msgstr "<literal>service</literal> テナントを使用し、このユーザーに <literal>admin</literal> ロールを与えます。"
-
-#: ./doc/install-guide/section_cinder-controller.xml74(replaceable)
-msgid "cinder@example.com"
-msgstr "cinder@example.com"
-
-#: ./doc/install-guide/section_cinder-controller.xml78(para)
-msgid ""
-"Edit the <filename>/etc/cinder/cinder.conf</filename> configuration file:"
-msgstr "<filename>/etc/cinder/cinder.conf</filename> 設定ファイルを編集します。"
-
-#: ./doc/install-guide/section_cinder-controller.xml112(para)
-msgid ""
-"In the <literal>[DEFAULT]</literal> section in the "
-"<filename>/etc/cinder/cinder.conf</filename> file, set these configuration "
-"keys and replace <replaceable>RABBIT_PASS</replaceable> with the password "
-"you chose for RabbitMQ:"
-msgstr "<filename>/etc/cinder/cinder.conf</filename> ファイルの <literal>[DEFAULT]</literal> セクションで、これらの設定キーを設定し、<replaceable>RABBIT_PASS</replaceable> を RabbitMQ 用に選択したパスワードに置き換えます。"
-
-#: ./doc/install-guide/section_cinder-controller.xml136(para)
-msgid ""
-"Replace <replaceable>RABBIT_PASS</replaceable> with the password you chose "
-"for RabbitMQ:"
-msgstr "<replaceable>RABBIT_PASS</replaceable> を RabbitMQ 用に選んだパスワードで置き換えます。"
-
-#: ./doc/install-guide/section_cinder-controller.xml148(para)
-msgid ""
-"Register the Block Storage service with the Identity service so that other "
-"OpenStack services can locate it:"
-msgstr "他の OpenStack サービスから使用できるように、Block Storage を Identity に登録します。"
-
-#: ./doc/install-guide/section_cinder-controller.xml158(para)
-msgid ""
-"Register a service and endpoint for version 2 of the Block Storage service "
-"API:"
-msgstr "Block Storage の API バージョン 2 用のサービスとエンドポイントを登録します。"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml7(title)
-msgid ""
-"OpenStack Installation Guide for <phrase os=\"rhel;centos;fedora\">Red Hat "
-"Enterprise Linux, CentOS, and Fedora</phrase><phrase os=\"ubuntu\">Ubuntu "
-"12.04/14.04 (LTS)</phrase><phrase os=\"debian\">Debian 7.0 "
-"(Wheezy)</phrase><phrase os=\"opensuse\">openSUSE and SUSE Linux Enterprise "
-"Server</phrase>"
-msgstr "OpenStack インストールガイド <phrase os=\"rhel;centos;fedora\">Red Hat Enterprise Linux、CentOS、Fedora</phrase><phrase os=\"ubuntu\">Ubuntu 12.04/14.04 (LTS)</phrase><phrase os=\"debian\">Debian 7.0 (Wheezy)</phrase><phrase os=\"opensuse\">openSUSE、SUSE Linux Enterprise Server</phrase> 版"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml15(phrase)
-msgid "Red Hat Enterprise Linux, CentOS, and Fedora"
-msgstr "Red Hat Enterprise Linux、CentOS、Fedora"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml16(phrase)
-msgid "Ubuntu 12.04/14.04 (LTS)"
-msgstr "Ubuntu 12.04/14.04 (LTS)"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml17(phrase)
-msgid "openSUSE and SUSE Linux Enterprise Server"
-msgstr "openSUSE、SUSE Linux Enterprise Server"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml18(phrase)
-msgid "Debian 7.0 (Wheezy)"
-msgstr "Debian 7.0 (Wheezy)"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml14(titleabbrev)
-msgid ""
-"OpenStack Installation Guide for "
-"<placeholder-1/><placeholder-2/><placeholder-3/><placeholder-4/>"
-msgstr "OpenStack インストールガイド <placeholder-1/><placeholder-2/><placeholder-3/><placeholder-4/> 版"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml27(orgname)
-msgid "OpenStack"
-msgstr "OpenStack"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml31(year)
-msgid "2012"
-msgstr "2012"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml32(year)
-msgid "2013"
-msgstr "2013"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml33(holder)
-msgid "OpenStack Foundation"
-msgstr "OpenStack Foundation"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml35(releaseinfo)
-msgid "icehouse"
-msgstr "icehouse"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml36(productname)
-msgid "OpenStack Installation Guide"
-msgstr "OpenStack インストールガイド"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml40(remark)
-msgid "Copyright details are filled in by the template."
-msgstr "Copyright details are filled in by the template."
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml45(para)
-msgid ""
-"The OpenStack® system consists of several key projects that you install "
-"separately but that work together depending on your cloud needs. These "
-"projects include Compute, Identity Service, Networking, Image Service, Block"
-" Storage, Object Storage, Telemetry, Orchestration, and Database. You can "
-"install any of these projects separately and configure them stand-alone or "
-"as connected entities. <phrase os=\"debian\">This guide walks through an "
-"installation by using packages available through Debian 7.0 (code name: "
-"Wheezy).</phrase><phrase os=\"ubuntu\">This guide walks through an "
-"installation by using packages available through Ubuntu 12.04 (LTS) or 14.04"
-" (LTS).</phrase><phrase os=\"rhel;centos;fedora\">This guide shows you how "
-"to install OpenStack by using packages available through Fedora 20 as well "
-"as on Red Hat Enterprise Linux and its derivatives through the EPEL "
-"repository.</phrase><phrase os=\"opensuse\">This guide shows you how to "
-"install OpenStack by using packages on openSUSE through the Open Build "
-"Service Cloud repository.</phrase> Explanations of configuration options and"
-" sample configuration files are included."
-msgstr "OpenStack® システムはいくつかの主要なプロジェクトから構成されます。これらは別々にインストールできますが、クラウドの要件に応じて一緒に使用できます。Compute、Identity Service、Networking、Image Service、Block Storage、Object Storage、Telemetry、Orchestration、Database があります。これらのプロジェクトを別々にインストールできます。スタンドアローンまたは全体を接続するよう設定できます。<phrase os=\"debian\">このガイドは Debian 7.0 (コード名: Wheezy) で利用可能なパッケージを使用してインストールしていきます。</phrase><phrase os=\"ubuntu\">このガイドは Ubuntu 12.04 (LTS)、14.04 (LTS) で利用可能なパッケージを使用してインストールしていきます。</phrase><phrase os=\"rhel;centos;fedora\">このガイドは EPEL リポジトリから Fedora 20、Red Hat Enterprise Linux、その派生物で利用可能なパッケージを使用して OpenStack をインストールする方法を説明します。</phrase><phrase os=\"opensuse\">Open Build Service Cloud リポジトリから openSUSE で利用可能なパッケージを使用して OpenStack をインストールする方法を説明します。</phrase>設定オプションの説明とサンプル設定ファイルが含まれます。"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml73(date)
-msgid "2014-04-16"
-msgstr "2014-04-16"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml77(para)
-msgid ""
-"Update for Icehouse, rework Networking setup to use ML2 as plugin, add new "
-"chapter for Database Service setup, improved basic configuration."
-msgstr "Icehouse 向け更新。Networking のセットアップを ML2 プラグインを使用するよう再構成。Database Service のセットアップに関する章の追加。基本的な設定の改善。"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml86(date)
-msgid "2013-10-25"
-msgstr "2013-10-25"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml90(para)
-msgid "Added initial Debian support."
-msgstr "Debian の初期サポートの追加。"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml96(date)
-msgid "2013-10-17"
-msgstr "2013-10-17"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml100(para)
-msgid "Havana release."
-msgstr "Havana リリース。"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml106(date)
-msgid "2013-10-16"
-msgstr "2013-10-16"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml110(para)
-msgid "Add support for SUSE Linux Enterprise."
-msgstr "SUSE Linux Enterprise のサポートの追加。"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml117(date)
-msgid "2013-10-08"
-msgstr "2013-10-08"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml121(para)
-msgid "Complete reorganization for Havana."
-msgstr "Havana 向け再構成の完了。"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml128(date)
-msgid "2013-09-09"
-msgstr "2013-09-09"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml132(para)
-msgid "Build also for openSUSE."
-msgstr "openSUSE 版の作成。"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml138(date)
-msgid "2013-08-01"
-msgstr "2013-08-01"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml142(para)
-msgid ""
-"Fixes to Object Storage verification steps. Fix bug <link "
-"href=\"https://bugs.launchpad.net/openstack-"
-"manuals/+bug/1207347\">1207347</link>."
-msgstr "Object Storage 検証手順の修正。バグ <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/1207347\">1207347</link> の修正。"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml151(date)
-msgid "2013-07-25"
-msgstr "2013-07-25"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml155(para)
-msgid ""
-"Adds creation of cinder user and addition to the service tenant. Fix bug "
-"<link href=\"https://bugs.launchpad.net/openstack-"
-"manuals/+bug/1205057\">1205057</link>."
-msgstr "cinder ユーザーの作成と service プロジェクトへの追加。バグ <link href=\"https://bugs.launchpad.net/openstack-manuals/+bug/1205057\">1205057</link> の修正。"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml165(date)
-msgid "2013-05-08"
-msgstr "2013-05-08"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml169(para)
-msgid "Updated the book title for consistency."
-msgstr "一貫性のために文書名の更新。"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml176(date)
-msgid "2013-05-02"
-msgstr "2013-05-02"
-
-#: ./doc/install-guide/bk_openstackinstallguide.xml180(para)
-msgid "Updated cover and fixed small errors in appendix."
-msgstr "表紙の更新と付録の小さなミスの修正。"
-
-#: ./doc/install-guide/ch_debconf.xml6(title)
-msgid "Configure OpenStack with debconf"
-msgstr "debconf を用いた OpenStack の設定"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml9(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml9(para)
-msgid ""
-"Before you configure OpenStack Networking, you must enable certain kernel "
-"networking functions."
-msgstr "OpenStack Networking を設定する前に、特定のカーネルネットワーク機能を有効化する必要があります。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml12(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml12(para)
-msgid "Edit <filename>/etc/sysctl.conf</filename> to contain the following:"
-msgstr "<filename>/etc/sysctl.conf</filename> を編集し、以下の内容を含めます。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml19(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml18(para)
-msgid "Implement the changes:"
-msgstr "変更を実装します。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml33(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml30(para)
-msgid ""
-"Ubuntu installations using Linux kernel version 3.11 or newer do not require"
-" the <emphasis>openvswitch-datapath-dkms</emphasis> package."
-msgstr "Linux カーネル 3.11 以降の Ubuntu インストール環境は、<emphasis>openvswitch-datapath-dkms</emphasis> パッケージを必要としません。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml43(title)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml40(title)
-msgid "To configure the Networking common components"
-msgstr "Networking 共通コンポーネントの設定方法"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml44(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml41(para)
-msgid ""
-"The Networking common component configuration includes the authentication "
-"mechanism, message broker, and plug-in."
-msgstr "Networking 共通コンポーネントの設定には、認証機構、メッセージブローカー、プラグインがあります。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml188(title)
-msgid "To configure the Layer-3 (L3) agent"
-msgstr "L3 エージェントの設定方法"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml189(para)
-msgid ""
-"The <glossterm>Layer-3 (L3) agent</glossterm> provides routing services for "
-"instance virtual networks."
-msgstr "<glossterm baseform=\"Layer-3 (L3) agent\">L3 エージェント</glossterm> は、インスタンスの仮想ネットワーク向けルーティングサービスを提供します。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml198(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml213(para)
-msgid ""
-"We recommend adding <literal>verbose = True</literal> to the "
-"<literal>[DEFAULT]</literal> section in "
-"<filename>/etc/neutron/l3_agent.ini</filename> to assist with "
-"troubleshooting."
-msgstr "トラブルシューティングに役立てるため、<filename>/etc/neutron/l3_agent.ini</filename> の <literal>[DEFAULT]</literal> セクションに <literal>verbose = True</literal> を追加することを推奨します。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml205(para)
-msgid ""
-"Edit the <filename>/etc/neutron/l3_agent.ini</filename> file and add the "
-"following keys to the <literal>[DEFAULT]</literal> section:"
-msgstr "<filename>/etc/neutron/l3_agent.ini</filename> ファイルを編集し、以下のキーを <literal>[DEFAULT]</literal> セクションに追加します。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml221(title)
-msgid "To configure the DHCP agent"
-msgstr "DHCP エージェントの設定方法"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml222(para)
-msgid ""
-"The <glossterm>DHCP agent</glossterm> provides <glossterm>DHCP</glossterm> "
-"services for instance virtual networks."
-msgstr "<glossterm baseform=\"DHCP agent\">DHCP エージェント</glossterm> はインスタンスの仮想ネットワーク向け <glossterm>DHCP</glossterm> サービスを提供します。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml234(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml250(para)
-msgid ""
-"We recommend adding <literal>verbose = True</literal> to the "
-"<literal>[DEFAULT]</literal> section in "
-"<filename>/etc/neutron/dhcp_agent.ini</filename> to assist with "
-"troubleshooting."
-msgstr "トラブルシューティングに役立てるため、<filename>/etc/neutron/dhcp_agent.ini</filename> の <literal>[DEFAULT]</literal> セクションに <literal>verbose = True</literal> を追加することを推奨します。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml241(para)
-msgid ""
-"Edit the <filename>/etc/neutron/dhcp_agent.ini</filename> file and add the "
-"following keys to the <literal>[DEFAULT]</literal> section:"
-msgstr "<filename>/etc/neutron/dhcp_agent.ini</filename> ファイルを編集し、以下のキーを <literal>[DEFAULT]</literal> セクションに追加します。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml258(title)
-msgid "To configure the metadata agent"
-msgstr "メタデータエージェントの設定方法"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml259(para)
-msgid ""
-"The <glossterm>metadata agent</glossterm> provides configuration information"
-" such as credentials for remote access to instances."
-msgstr "<glossterm baseform=\"metadata agent\">メタデータエージェント</glossterm>は、インスタンスへのリモートアクセス用の設定情報を提供します。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml263(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml293(para)
-msgid ""
-"Replace <replaceable>NEUTRON_PASS</replaceable> with the password you chose "
-"for the <literal>neutron</literal> user in the Identity service. Replace "
-"<replaceable>METADATA_SECRET</replaceable> with a suitable secret for the "
-"metadata proxy."
-msgstr "Identity で <literal>neutron</literal> ユーザー用に選択したパスワードで <replaceable>NEUTRON_PASS</replaceable> を置き換えます。<replaceable>METADATA_SECRET</replaceable> をメタデータプロキシ用の適切なシークレットで置き換えます。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml281(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml306(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml329(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml341(replaceable)
-msgid "METADATA_SECRET"
-msgstr "METADATA_SECRET"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml283(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml308(para)
-msgid ""
-"We recommend adding <literal>verbose = True</literal> to the "
-"<literal>[DEFAULT]</literal> section in "
-"<filename>/etc/neutron/metadata_agent.ini</filename> to assist with "
-"troubleshooting."
-msgstr "トラブルシューティングに役立てるため、<filename>/etc/neutron/metadata_agent.ini</filename> の <literal>[DEFAULT]</literal> セクションに <literal>verbose = True</literal> を追加することを推奨します。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml290(para)
-msgid ""
-"Edit the <filename>/etc/neutron/metadata_agent.ini</filename> file and add "
-"the following keys to the <literal>[DEFAULT]</literal> section:"
-msgstr "<filename>/etc/neutron/metadata_agent.ini</filename> ファイルを編集し、以下のキーを <literal>[DEFAULT]</literal> セクションに追加します。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml316(para)
-msgid ""
-"Perform the next two steps on the <emphasis>controller</emphasis> node."
-msgstr "<emphasis>コントローラー</emphasis>ノードで次の 2 つの手順を実行します。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml321(para)
-msgid ""
-"On the <emphasis>controller</emphasis> node, configure Compute to use the "
-"metadata service:"
-msgstr "<emphasis>コントローラー</emphasis>ノードで、メタデータサービスを使用するよう Compute を設定します。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml323(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml335(para)
-msgid ""
-"Replace <replaceable>METADATA_SECRET</replaceable> with the secret you chose"
-" for the metadata proxy."
-msgstr "メタデータプロキシ用に選択した適切なシークレットで <replaceable>METADATA_SECRET</replaceable> を置き換えます。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml332(para)
-msgid ""
-"On the <emphasis>controller</emphasis> node, edit the "
-"<filename>/etc/nova/nova.conf</filename> file and add the following keys to "
-"the <literal>[DEFAULT]</literal> section:"
-msgstr "<emphasis>コントローラー</emphasis>ノードで、<filename>/etc/nova/nova.conf</filename> ファイルを編集し、以下のキーを <literal>[DEFAULT]</literal> セクションに追加します。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml344(para)
-msgid ""
-"On the <emphasis>controller</emphasis> node, restart the Compute "
-"<glossterm>API</glossterm> service:"
-msgstr "<emphasis>コントローラー</emphasis>ノードで、Compute <glossterm>API</glossterm> サービスを再起動します。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml352(para)
-msgid ""
-"The ML2 plug-in uses the Open vSwitch (OVS) mechanism (agent) to build "
-"virtual networking framework for instances."
-msgstr "ML2 プラグインは、インスタンスの仮想ネットワークフレームワークを構築するために、Open vSwitch 機能 (エージェント) を使用します。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml356(para)
-msgid ""
-"Replace <replaceable>INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS</replaceable> "
-"with the IP address of the instance tunnels network interface on your "
-"network node. This guide uses <literal>10.0.1.21</literal> for the IP "
-"address of the instance tunnels network interface on the network node."
-msgstr "ネットワークノードのインスタンストンネルネットワークインターフェースの IP アドレスで <replaceable>INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS</replaceable> を置き換えます。このガイドは、ネットワークノードのインスタンストンネルネットワークインターフェースの IP アドレスに <literal>10.0.1.21</literal> を使用します。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml372(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml406(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml206(replaceable)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml240(replaceable)
-msgid "INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS"
-msgstr "INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml383(para)
-msgid ""
-"Edit the <filename>/etc/neutron/plugins/ml2/ml2_conf.ini</filename> file."
-msgstr "<filename>/etc/neutron/plugins/ml2/ml2_conf.ini</filename> ファイルを編集します。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml393(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml227(para)
-msgid ""
-"Add the following keys to the <literal>[ml2_type_gre]</literal> section:"
-msgstr "以下のキーを <literal>[ml2_type_gre]</literal> セクションに追加します。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml398(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml232(para)
-msgid "Add the <literal>[ovs]</literal> section and the following keys to it:"
-msgstr "<literal>[ovs]</literal> セクションを追加し、そこに以下のキーを追加します。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml400(para)
-msgid ""
-"Replace <replaceable>INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS</replaceable> "
-"with the IP address of the instance tunnels network interface on your "
-"network node."
-msgstr "ネットワークノードのインスタンストンネルネットワークインターフェースの IP アドレスで <replaceable>INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS</replaceable> を置き換えます。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml418(title)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml252(title)
-msgid "To configure the Open vSwitch (OVS) service"
-msgstr "Open vSwitch (OVS) サービスの設定方法"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml419(para)
-msgid ""
-"The OVS service provides the underlying virtual networking framework for "
-"instances. The integration bridge <literal>br-int</literal> handles internal"
-" instance network traffic within OVS. The external bridge <literal>br-"
-"ex</literal> handles external instance network traffic within OVS. The "
-"external bridge requires a port on the physical external network interface "
-"to provide instances with external network access. In essence, this port "
-"bridges the virtual and physical external networks in your environment."
-msgstr "OVS サービスは、バックエンドの仮想ネットワークフレームワークをインスタンスに提供します。統合ブリッジ <literal>br-int</literal> は OVS 内のインスタンスの内部ネットワーク通信を処理します。外部ブリッジ <literal>br-ex</literal> は OVS 内のインスタンスの外部ネットワーク通信を処理します。外部ブリッジは、インスタンスに外部ネットワークアクセスを提供するために、外部物理ネットワークインターフェースにポートが必要です。このポートは本質的に、お使いの環境で仮想外部ネットワークと物理外部ネットワークをブリッジします。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml428(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml434(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml257(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml263(para)
-msgid "Start the OVS service and configure it to start when the system boots:"
-msgstr "OVS サービスを起動し、システム起動時に起動するよう設定します。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml440(para)
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml444(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml269(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml273(para)
-msgid "Restart the OVS service:"
-msgstr "OVS サービスを再起動します。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml448(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml277(para)
-msgid "Add the integration bridge:"
-msgstr "統合ブリッジを追加します。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml452(para)
-msgid "Add the external bridge:"
-msgstr "外部ブリッジを追加します。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml456(para)
-msgid ""
-"Add a port to the external bridge that connects to the physical external "
-"network interface:"
-msgstr "外部ネットワークの物理インターフェースに接続する外部ブリッジに、ポートを追加します。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml463(para)
-msgid ""
-"Depending on your network interface driver, you may need to disable "
-"<glossterm>Generic Receive Offload (GRO)</glossterm> to achieve suitable "
-"throughput between your instances and the external network."
-msgstr "お使いのネットワークインターフェースドライバーによっては、インスタンスと外部ネットワーク間の適切なスループットを達成するために、<glossterm baseform=\"Generic Receive Offload (GRO)\">GRO</glossterm> を無効化する必要があるかもしれません。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml467(para)
-msgid ""
-"To temporarily disable GRO on the external network interface while testing "
-"your environment:"
-msgstr "環境のテスト中、外部ネットワークインターフェースで一時的に GRO を無効化する場合:"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml474(title)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml347(title)
-msgid "To finalize the installation"
-msgstr "インストールの最終手順"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml476(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml349(para)
-msgid ""
-"The Networking service initialization scripts expect a symbolic link "
-"<filename>/etc/neutron/plugin.ini</filename> pointing to the configuration "
-"file associated with your chosen plug-in. Using the ML2 plug-in, for "
-"example, the symbolic link must point to "
-"<filename>/etc/neutron/plugins/ml2/ml2_conf.ini</filename>. If this symbolic"
-" link does not exist, create it using the following commands:"
-msgstr "Networking のサービス初期化スクリプトは、選択したプラグインと関連する設定ファイルを指し示すシンボリックリンク <filename>/etc/neutron/plugin.ini</filename> を予期しています。例えば、ML2 プラグインを使用する場合、シンボリックリンクが <filename>/etc/neutron/plugins/ml2/ml2_conf.ini</filename> を指し示す必要があります。このシンボリックリンクが存在しなければ、以下のコマンドを使用して作成します。"
-
-#. https://bugzilla.redhat.com/show_bug.cgi?id=1087647
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml485(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml358(para)
-msgid ""
-"Due to a packaging bug, the Open vSwitch agent initialization script "
-"explicitly looks for the Open vSwitch plug-in configuration file rather than"
-" a symbolic link <filename>/etc/neutron/plugin.ini</filename> pointing to "
-"the ML2 plug-in configuration file. Run the following commands to resolve "
-"this issue:"
-msgstr "パッケージ化のバグのため、Open vSwitch エージェントの初期化スクリプトは、ML2 プラグイン設定ファイルを指し示すシンボリックリンク <filename>/etc/neutron/plugin.ini</filename> ではなく、Open vSwitch プラグイン設定ファイルを明示的に検索します。この問題を解決するために、以下のコマンドを実行します。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml495(para)
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml368(para)
-msgid ""
-"The Networking service initialization scripts expect the variable "
-"<literal>NEUTRON_PLUGIN_CONF</literal> in the "
-"<filename>/etc/sysconfig/neutron</filename> file to reference the "
-"configuration file associated with your chosen plug-in. Using ML2, for "
-"example, edit the <filename>/etc/sysconfig/neutron</filename> file and add "
-"the following:"
-msgstr "Networking のサービス初期化スクリプトは、<filename>/etc/sysconfig/neutron</filename> ファイルの <literal>NEUTRON_PLUGIN_CONF</literal> 変数が、使用するプラグインに関連する設定ファイルを参照していることを想定します。例えば、ML2 を使用する場合、<filename>/etc/sysconfig/neutron</filename> ファイルを編集し、以下を追加します。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml505(para)
-msgid ""
-"Start the Networking services and configure them to start when the system "
-"boots:"
-msgstr "Networking サービスを起動し、システム起動時に起動するよう設定します。"
-
-#: ./doc/install-guide/section_neutron-ml2-network-node.xml525(para)
-msgid "Restart the Networking services:"
-msgstr "Networking サービスを再起動します。"
-
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml186(para)
-msgid ""
-"The ML2 plug-in uses the Open vSwitch (OVS) mechanism (agent) to build the "
-"virtual networking framework for instances."
-msgstr "ML2 プラグインは、インスタンスの仮想ネットワークフレームワークを構築するために、Open vSwitch 機能 (エージェント) を使用します。"
-
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml190(para)
-msgid ""
-"Replace <replaceable>INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS</replaceable> "
-"with the IP address of the instance tunnels network interface on your "
-"compute node. This guide uses <literal>10.0.1.31</literal> for the IP "
-"address of the instance tunnels network interface on the first compute node."
-msgstr "コンピュートノードのインスタンストンネルネットワークインターフェースの IP アドレスで <replaceable>INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS</replaceable> を置き換えます。このガイドは、最初のコンピュートノードのインスタンストンネルネットワークインターフェースの IP アドレスに <literal>10.0.1.31</literal> を使用します。"
-
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml234(para)
-msgid ""
-"Replace <replaceable>INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS</replaceable> "
-"with the IP address of the instance tunnels network interface on your "
-"compute node."
-msgstr "コンピュートノードのインスタンストンネルネットワークインターフェースの IP アドレスで <replaceable>INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS</replaceable> を置き換えます。"
-
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml253(para)
-msgid ""
-"The OVS service provides the underlying virtual networking framework for "
-"instances. The integration bridge <literal>br-int</literal> handles internal"
-" instance network traffic within OVS."
-msgstr "OVS サービスは、バックエンドの仮想ネットワークフレームワークをインスタンスに提供します。統合ブリッジ <literal>br-int</literal> が OVS 内の内部インスタンスネットワーク通信を処理します。"
-
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml378(para)
-#: ./doc/install-guide/section_ceilometer-nova.xml53(para)
-#: ./doc/install-guide/section_nova-compute.xml208(para)
-msgid "Restart the Compute service:"
-msgstr "Compute Service を再起動します。"
-
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml383(para)
-msgid ""
-"Start the Open vSwitch (OVS) agent and configure it to start when the system"
-" boots:"
-msgstr "Open vSwitch エージェントを起動し、システム起動時に起動するよう設定します。"
-
-#: ./doc/install-guide/section_neutron-ml2-compute-node.xml391(para)
-msgid "Restart the Open vSwitch (OVS) agent:"
-msgstr "Open vSwitch (OVS) エージェントを再起動します。"
-
 #. When image changes, this message will be marked fuzzy or untranslated for
 #. you.
 #. It doesn't matter what you translate it to: it's not used at all.
@@ -6371,1499 +7788,104 @@ msgid ""
 "subsequent chapters."
 msgstr "このアーキテクチャーを導入する場合、<xref linkend=\"ch_networking\"/>の<xref linkend=\"section_neutron-networking\"/>を飛ばしてください。オプションのサービスを使用するために、後続の章に記載されている、追加ノードをインストールする必要があるかもしれません。"
 
-#: ./doc/install-guide/section_dashboard-install.xml7(title)
-msgid "Install the dashboard"
-msgstr "Dashboard のインストール"
+#: ./doc/install-guide/section_trove-verify.xml5(title)
+msgid "Verify the Database service installation"
+msgstr "Database サービスのインストールを検証します。"
 
-#: ./doc/install-guide/section_dashboard-install.xml8(para)
+#: ./doc/install-guide/section_trove-verify.xml6(para)
 msgid ""
-"Before you can install and configure the dashboard, meet the requirements in"
-" <xref linkend=\"dashboard-system-requirements\"/>."
-msgstr "Dashboard をインストールし、設定する前に <xref linkend=\"dashboard-system-requirements\"/> にある要件を満たしている必要があります。"
+"To verify that the Database service is installed and configured correctly, "
+"try executing a Trove command:"
+msgstr "Database サービスがインストールされ、正しく設定されていることを検証するために、Trove コマンドを実行してみます。"
 
-#: ./doc/install-guide/section_dashboard-install.xml12(para)
-msgid ""
-"When you install only Object Storage and the Identity Service, even if you "
-"install the dashboard, it does not pull up projects and is unusable."
-msgstr "bject Storage と Identity Service のみをインストールしたとき、Dashboard をインストールしても、プロジェクトが表示されず、使用することもできません。"
-
-#: ./doc/install-guide/section_dashboard-install.xml16(para)
-msgid ""
-"For more information about how to deploy the dashboard, see <link "
-"href=\"http://docs.openstack.org/developer/horizon/topics/deployment.html\">deployment"
-" topics in the developer documentation</link>."
-msgstr "Dashboard の導入方法の詳細は <link href=\"http://docs.openstack.org/developer/horizon/topics/deployment.html\">deployment topics in the developer documentation</link> を参照してください。"
-
-#: ./doc/install-guide/section_dashboard-install.xml22(para)
-msgid ""
-"Install the dashboard on the node that can contact the Identity Service as "
-"root:"
-msgstr "Identity Service と通信できるノードに root として Dashboard をインストールします。"
-
-#: ./doc/install-guide/section_dashboard-install.xml28(title)
-msgid "Note for Ubuntu users"
-msgstr "Ubuntu ユーザー向け注記"
-
-#: ./doc/install-guide/section_dashboard-install.xml30(para)
-msgid ""
-"Remove the <literal>openstack-dashboard-ubuntu-theme</literal> package. This"
-" theme prevents translations, several menus as well as the network map from "
-"rendering correctly: <placeholder-1/>"
-msgstr "<literal>openstack-dashboard-ubuntu-theme</literal> パッケージを削除します。このテーマは翻訳、いくつかのメニュー、ネットワークマップが正しく表示されません。 <placeholder-1/>"
-
-#: ./doc/install-guide/section_dashboard-install.xml39(title)
-msgid "Note for Debian users"
-msgstr "Debian ユーザー向けの注記"
-
-#: ./doc/install-guide/section_dashboard-install.xml40(para)
-msgid "To install the Apache package:"
-msgstr "Apache のパッケージをインストールする方法:"
-
-#: ./doc/install-guide/section_dashboard-install.xml42(para)
-msgid ""
-"This command installs and configures Apache correctly, provided that the "
-"user asks for it during the <package>debconf</package> prompts. The default "
-"SSL certificate is self-signed, and it is probably wise to have it signed by"
-" a root Certificate Authority (CA)."
-msgstr "このコマンドはユーザーが <package>debconf</package> プロンプトに答えたとおりに Apache を正しくインストールし、設定します。標準の SSL 証明書は自己署名です。ルート認証局 (CA) により署名されたものを使用したほうが良いです。"
-
-#: ./doc/install-guide/section_dashboard-install.xml51(para)
-msgid ""
-"Modify the value of <literal>CACHES['default']['LOCATION']</literal> in "
-"<filename os=\"ubuntu;debian\">/etc/openstack-"
-"dashboard/local_settings.py</filename><filename "
-"os=\"centos;fedora;rhel\">/etc/openstack-"
-"dashboard/local_settings</filename><filename os=\"opensuse;sles\">/srv/www"
-"/openstack-dashboard/openstack_dashboard/local/local_settings.py</filename> "
-"to match the ones set in <filename "
-"os=\"ubuntu;debian\">/etc/memcached.conf</filename><filename "
-"os=\"centos;fedora;rhel;opensuse;sles\">/etc/sysconfig/memcached</filename>."
-msgstr "<filename os=\"ubuntu;debian\">/etc/memcached.conf</filename><filename os=\"centos;fedora;rhel;opensuse;sles\">/etc/sysconfig/memcached</filename> に設定したものと一致されるために、<filename os=\"ubuntu;debian\">/etc/openstack-dashboard/local_settings.py</filename><filename os=\"centos;fedora;rhel\">/etc/openstack-dashboard/local_settings</filename><filename os=\"opensuse;sles\">/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py</filename> の <literal>CACHES['default']['LOCATION']</literal> の値を変更します。"
-
-#: ./doc/install-guide/section_dashboard-install.xml63(para)
-msgid ""
-"Open <filename os=\"ubuntu;debian\">/etc/openstack-"
-"dashboard/local_settings.py</filename><filename "
-"os=\"centos;fedora;rhel\">/etc/openstack-dashboard/local_settings</filename>"
-" and look for this line:"
-msgstr "<filename os=\"ubuntu;debian\">/etc/openstack-dashboard/local_settings.py</filename><filename os=\"centos;fedora;rhel\">/etc/openstack-dashboard/local_settings</filename> を開き、この行を探します。"
-
-#: ./doc/install-guide/section_dashboard-install.xml76(title)
-#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml29(td)
-msgid "Notes"
-msgstr "注"
-
-#: ./doc/install-guide/section_dashboard-install.xml79(para)
-msgid ""
-"The address and port must match the ones set in <filename "
-"os=\"ubuntu;debian\">/etc/memcached.conf</filename><filename "
-"os=\"centos;fedora;rhel;opensuse;sles\">/etc/sysconfig/memcached</filename>."
-msgstr "アドレスとポートは <filename os=\"ubuntu;debian\">/etc/memcached.conf</filename><filename os=\"centos;fedora;rhel;opensuse;sles\">/etc/sysconfig/memcached</filename> に設定したものと一致する必要があります。"
-
-#: ./doc/install-guide/section_dashboard-install.xml84(para)
-msgid ""
-"If you change the memcached settings, you must restart the Apache web server"
-" for the changes to take effect."
-msgstr "memcached 設定を変更する場合、変更を反映するために Apache ウェブサーバーを再起動する必要があります。"
-
-#: ./doc/install-guide/section_dashboard-install.xml89(para)
-msgid ""
-"You can use options other than memcached option for session storage. Set the"
-" session back-end through the <parameter>SESSION_ENGINE</parameter> option."
-msgstr "セッションストレージのために memcached 以外のオプションを使用することもできます。<parameter>SESSION_ENGINE</parameter> オプションによりセッションバックエンドを設定します。"
-
-#: ./doc/install-guide/section_dashboard-install.xml96(para)
-msgid ""
-"To change the timezone, use the dashboard or edit the <filename "
-"os=\"centos;fedora;rhel\">/etc/openstack-"
-"dashboard/local_settings</filename><filename os=\"ubuntu;debian\">/etc"
-"/openstack-dashboard/local_settings.py</filename><filename "
-"os=\"opensuse;sles\">/srv/www/openstack-"
-"dashboard/openstack_dashboard/local/local_settings.py</filename> file."
-msgstr "タイムゾーンを変更する場合、ダッシュボードを使用します。または <filename os=\"centos;fedora;rhel\">/etc/openstack-dashboard/local_settings</filename><filename os=\"ubuntu;debian\">/etc/openstack-dashboard/local_settings.py</filename><filename os=\"opensuse;sles\">/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py</filename> ファイルを編集します。"
-
-#: ./doc/install-guide/section_dashboard-install.xml105(para)
-msgid "Change the following parameter: <code>TIME_ZONE = \"UTC\"</code>"
-msgstr "次のパラメーターを変更します。 <code>TIME_ZONE = \"UTC\"</code>"
-
-#: ./doc/install-guide/section_dashboard-install.xml112(para)
-msgid ""
-"Update the <literal>ALLOWED_HOSTS</literal> in "
-"<filename>local_settings.py</filename> to include the addresses you wish to "
-"access the dashboard from."
-msgstr "Dashboard にアクセスしたいアドレスを含めるために <filename>local_settings.py</filename> の <literal>ALLOWED_HOSTS</literal> を更新します。"
-
-#: ./doc/install-guide/section_dashboard-install.xml116(para)
-msgid ""
-"Edit <filename os=\"centos;fedora;rhel\">/etc/openstack-"
-"dashboard/local_settings</filename><filename os=\"ubuntu;debian\">/etc"
-"/openstack-dashboard/local_settings.py</filename><filename "
-"os=\"opensuse;sles\">/srv/www/openstack-"
-"dashboard/openstack_dashboard/local/local_settings.py</filename>:"
-msgstr "<filename os=\"centos;fedora;rhel\">/etc/openstack-dashboard/local_settings</filename><filename os=\"ubuntu;debian\">/etc/openstack-dashboard/local_settings.py</filename><filename os=\"opensuse;sles\">/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py</filename> を編集します。"
-
-#: ./doc/install-guide/section_dashboard-install.xml127(para)
-msgid ""
-"This guide assumes that you are running the Dashboard on the controller "
-"node. You can easily run the dashboard on a separate server, by changing the"
-" appropriate settings in <filename>local_settings.py</filename>."
-msgstr "このガイドはコントローラーノードで Dashboard を実行していると仮定します。<filename>local_settings.py</filename> の設定を適切に変更することにより、別のサーバーで Dashboard を簡単に実行できます。"
-
-#: ./doc/install-guide/section_dashboard-install.xml132(para)
-msgid ""
-"Edit <filename os=\"centos;fedora;rhel\">/etc/openstack-"
-"dashboard/local_settings</filename><filename os=\"ubuntu;debian\">/etc"
-"/openstack-dashboard/local_settings.py</filename><filename "
-"os=\"opensuse;sles\">/srv/www/openstack-"
-"dashboard/openstack_dashboard/local/local_settings.py</filename> and change "
-"<literal>OPENSTACK_HOST</literal> to the hostname of your Identity Service:"
-msgstr "<filename os=\"centos;fedora;rhel\">/etc/openstack-dashboard/local_settings</filename><filename os=\"ubuntu;debian\">/etc/openstack-dashboard/local_settings.py</filename><filename os=\"opensuse;sles\">/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py</filename> を編集し、<literal>OPENSTACK_HOST</literal> を Identity Service のホスト名に変更します。"
-
-#: ./doc/install-guide/section_dashboard-install.xml144(para)
-msgid "Setup Apache configuration: <placeholder-1/>"
-msgstr "Apache 設定をセットアップします。 <placeholder-1/>"
-
-#: ./doc/install-guide/section_dashboard-install.xml151(para)
-msgid ""
-"By default, the <systemitem>openstack-dashboard</systemitem> package enables"
-" a database as session store. Before you continue, either change the session"
-" store set up as described in <xref linkend=\"dashboard-sessions\"/> or "
-"finish the setup of the database session store as explained in <xref linkend"
-"=\"dashboard-session-database\"/>."
-msgstr "<systemitem>openstack-dashboard</systemitem> パッケージは標準でセッションストアとしてデータベースを有効化します。続行する前に、<xref linkend=\"dashboard-sessions\"/> に記載されているとおりセットアップしたセッションストアを変更します。または、<xref linkend=\"dashboard-session-database\"/> に記載されているとおりデータベースのセッションストアのセットアップを完了します。"
-
-#: ./doc/install-guide/section_dashboard-install.xml161(para)
-msgid ""
-"Ensure that the SELinux policy of the system is configured to allow network "
-"connections to the HTTP server."
-msgstr "システムの SELinux ポリシーが HTTP サーバーにネットワーク接続を許可するよう設定されていることを確認します。"
-
-#: ./doc/install-guide/section_dashboard-install.xml168(para)
-msgid "Start the Apache web server and memcached:"
-msgstr "Apache ウェブサーバーと memcached を起動します。"
-
-#: ./doc/install-guide/section_dashboard-install.xml181(para)
-msgid ""
-"You can now access the dashboard at <uri "
-"os=\"ubuntu\">http://controller/horizon</uri><uri "
-"os=\"debian\">https://controller/</uri><uri "
-"os=\"centos;fedora;rhel\">http://controller/dashboard</uri><uri "
-"os=\"opensuse;sles\">http://controller</uri>."
-msgstr "これで Dashboard に <uri os=\"ubuntu\">http://controller/horizon</uri><uri os=\"debian\">https://controller/</uri><uri os=\"centos;fedora;rhel\">http://controller/dashboard</uri><uri os=\"opensuse;sles\">http://controller</uri> からアクセスできます。"
-
-#: ./doc/install-guide/section_dashboard-install.xml188(para)
-msgid ""
-"Login with credentials for any user that you created with the OpenStack "
-"Identity Service."
-msgstr "OpenStack Identity Service で作成したどれかのユーザーのクレデンシャルでログインします。"
-
-#: ./doc/install-guide/section_basics-queue.xml6(title)
-msgid "Messaging server"
-msgstr "メッセージングサーバー"
+#: ./doc/install-guide/section_trove-verify.xml10(para)
+msgid "Source the <filename>demo-openrc.sh</filename> file."
+msgstr "<filename>demo-openrc.sh</filename> ファイルを読み込みます。"
 
-#: ./doc/install-guide/section_basics-queue.xml7(para)
-msgid ""
-"OpenStack uses a <glossterm>message broker</glossterm> to coordinate "
-"operations and status information among services. The message broker service"
-" typically runs on the controller node. OpenStack supports several message "
-"brokers including <application>RabbitMQ</application>, "
-"<application>Qpid</application>, and <application>ZeroMQ</application>. "
-"However, most distributions that package OpenStack support a particular "
-"message broker. This guide covers the message broker supported by each "
-"distribution. If you prefer to implement a different message broker, consult"
-" the documentation associated with it."
-msgstr "OpenStack は、サービス間の操作と状態を調整するために、<glossterm baseform=\"message broker\">メッセージブローカー</glossterm>を使用します。メッセージブローカーサービスは、一般的にコントローラーノードで動作します。OpenStack は、<application>RabbitMQ</application>、<application>Qpid</application>、<application>ZeroMQ</application> などのメッセージブローカーをサポートします。しかしながら、OpenStack をパッケージ化している多くのディストリビューションは、特定のメッセージブローカーをサポートします。このガイドは、各ディストリビューションによりサポートされるメッセージブローカーを取り扱います。別のメッセージブローカーを導入したければ、関連ドキュメントを確認してください。"
-
-#: ./doc/install-guide/section_basics-queue.xml18(link)
-msgid "RabbitMQ"
-msgstr "RabbitMQ"
-
-#: ./doc/install-guide/section_basics-queue.xml21(link)
-msgid "Qpid"
-msgstr "Qpid"
-
-#: ./doc/install-guide/section_basics-queue.xml24(link)
-msgid "ZeroMQ"
-msgstr "ZeroMQ"
-
-#: ./doc/install-guide/section_basics-queue.xml28(title)
-msgid "To install the message broker service"
-msgstr "メッセージブローカーサービスのインストール方法"
-
-#: ./doc/install-guide/section_basics-queue.xml30(para)
-msgid "Ubuntu and Debian use <application>RabbitMQ</application>."
-msgstr "Ubuntu および Debian は <application>RabbitMQ</application> を使用します。"
+#: ./doc/install-guide/section_trove-verify.xml14(para)
+msgid "Retrieve the Trove instances list:"
+msgstr "Trove インスタンスの一覧を取得します。"
 
-#: ./doc/install-guide/section_basics-queue.xml34(para)
-msgid ""
-"Red Hat Enterprise Linux (RHEL), CentOS, Scientific Linux, and Fedora use "
-"<application>Qpid</application>."
-msgstr "Red Hat Enterprise Linux (RHEL)、CentOS、Scientific Linux、Fedora は <application>Qpid</application> を使用します。"
-
-#: ./doc/install-guide/section_basics-queue.xml40(para)
-msgid ""
-"SUSE Linux Enterprise Server (SLES) and openSUSE use "
-"<application>RabbitMQ</application>."
-msgstr "SUSE Linux Enterprise Server (SLES) および openSUSE は <application>RabbitMQ</application> を使用します。"
-
-#: ./doc/install-guide/section_basics-queue.xml46(title)
-msgid "To configure the message broker service"
-msgstr "メッセージブローカーサービスの設定方法"
-
-#: ./doc/install-guide/section_basics-queue.xml48(para)
-msgid ""
-"To simplify installation of your test environment, we recommend that you "
-"disable authentication."
-msgstr "テスト完了のインストールを簡単にするため、認証の無効化を推奨します。"
+#: ./doc/install-guide/section_trove-verify.xml16(para)
+msgid "You should see output similar to this:"
+msgstr "このように出力されます。"
 
-#: ./doc/install-guide/section_basics-queue.xml50(para)
+#: ./doc/install-guide/section_trove-verify.xml23(para)
 msgid ""
-"Edit the <filename>/etc/qpidd.conf</filename> file and change the following "
-"key:"
-msgstr "<filename>/etc/qpidd.conf</filename> ファイルを編集し、以下のキーを変更します。"
+"Assuming you have created an image for the type of database you want, and "
+"have updated the datastore to use that image, you can now create a Trove "
+"instance (database). To do this, use the trove <placeholder-1/> command."
+msgstr "使用したいデータベースの種類に応じたイメージを作成し、そのイメージを使用するためにデータストアを更新したことを仮定すると、Trove インスタンス (データベース) を作成できます。このために、trove <placeholder-1/> コマンドを使用します。"
 
-#: ./doc/install-guide/section_basics-queue.xml54(para)
-msgid ""
-"For production environments, you should enable authentication. For more "
-"information on securing the message broker, see the <link "
-"href=\"http://qpid.apache.org/books/trunk/AMQP-Messaging-Broker-CPP-"
-"Book/html/chap-Messaging_User_Guide-Security.html\">documentation</link>."
-msgstr "本番環境では認証を有効化することを強く推奨します。メッセージブローカーのセキュア化に関する詳細は、<link href=\"http://qpid.apache.org/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/chap-Messaging_User_Guide-Security.html\">ドキュメント</link>を参照してください。"
-
-#: ./doc/install-guide/section_basics-queue.xml59(para)
-msgid ""
-"If you decide to enable authentication for your test environment, you must "
-"configure the <literal>qpid_username</literal> and "
-"<literal>qpid_password</literal> keys in the configuration file of each "
-"OpenStack service that uses the message broker."
-msgstr "テスト環境向けに認証を有効化することにした場合、メッセージブローカーを使用する各 OpenStack サービスの設定ファイルで <literal>qpid_username</literal> と <literal>qpid_password</literal> を設定する必要があります。"
-
-#: ./doc/install-guide/section_basics-queue.xml66(para)
-msgid "Start the message broker service:"
-msgstr "メッセージブローカーサービスを起動します。"
-
-#: ./doc/install-guide/section_basics-queue.xml70(para)
-msgid ""
-"The message broker creates a default account that uses "
-"<literal>guest</literal> for the username and password. To simplify "
-"installation of your test environment, we recommend that you use this "
-"account, but change the password for it."
-msgstr "メッセージブローカーは、ユーザー名とパスワードに <literal>guest</literal> を使用するデフォルトアカウントを作成します。テスト環境のインストールを簡単にするために、このアカウントを使用し、そのパスワードを変更しないことを推奨します。"
-
-#: ./doc/install-guide/section_basics-queue.xml74(para)
-#: ./doc/install-guide/section_nova-compute.xml159(para)
-#: ./doc/install-guide/section_nova-compute.xml178(para)
-msgid "Run the following command:"
-msgstr "以下のコマンドを実行します。"
-
-#: ./doc/install-guide/section_basics-queue.xml75(para)
-msgid ""
-"Replace <replaceable>RABBIT_PASS</replaceable> with a suitable password."
-msgstr "<replaceable>RABBIT_PASS</replaceable> を適切なパスワードに置き換えます。"
-
-#: ./doc/install-guide/section_basics-queue.xml78(para)
-msgid ""
-"You must configure the <literal>rabbit_password</literal> key in the "
-"configuration file for each OpenStack service that uses the message broker."
-msgstr "メッセージブローカーを使用する各 OpenStack サービスの設定ファイルで <literal>rabbit_password</literal> キーを設定する必要があります。"
-
-#: ./doc/install-guide/section_basics-queue.xml82(para)
-msgid ""
-"For production environments, you should create a unique account with "
-"suitable password. For more information on securing the message broker, see "
-"the <link "
-"href=\"https://www.rabbitmq.com/man/rabbitmqctl.1.man.html\">documentation</link>."
-msgstr "本番環境では、適切なパスワードを持つ独自のアカウントを作成すべきです。メッセージブローカーのセキュア化に関する詳細は、<link href=\"https://www.rabbitmq.com/man/rabbitmqctl.1.man.html\">ドキュメント</link>を参照してください。"
-
-#: ./doc/install-guide/section_basics-queue.xml87(para)
-msgid ""
-"If you decide to create a unique account with suitable password for your "
-"test environment, you must configure the <literal>rabbit_userid</literal> "
-"and <literal>rabbit_password</literal> keys in the configuration file of "
-"each OpenStack service that uses the message broker."
-msgstr "テスト環境向けに適切なパスワードを持つ独自のアカウントを作成することにした場合、メッセージブローカーを使用する各 OpenStack サービスの設定ファイルで <literal>rabbit_userid</literal> と <literal>rabbit_password</literal> を設定する必要があります。"
-
-#: ./doc/install-guide/section_basics-queue.xml98(para)
-msgid ""
-"Start the message broker service and configure it to start when the system "
-"boots:"
-msgstr "メッセージブローカーサービスを起動し、システム起動時に起動するよう設定します。"
-
-#: ./doc/install-guide/section_basics-queue.xml104(para)
-msgid "Configure the message broker service to start when the system boots:"
-msgstr "システム起動時にメッセージブローカーサービスが起動するよう設定します。"
-
-#: ./doc/install-guide/section_basics-queue.xml109(para)
-msgid "Congratulations, now you are ready to install OpenStack services!"
-msgstr "おめでとうございます。これで OpenStack サービスをインストールする準備ができました。"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_neutron-initial-networks.xml23(None)
-msgid ""
-"@@image: 'figures/installguide_neutron-initial-networks.png'; "
-"md5=df1d74b6f91feefe5cfaf7824aac86e1"
-msgstr "@@image: 'figures/installguide_neutron-initial-networks.png'; md5=df1d74b6f91feefe5cfaf7824aac86e1"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml6(title)
-msgid "Create initial networks"
-msgstr "初期ネットワークの作成"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml7(para)
-msgid ""
-"Before launching your first instance, you must create the necessary virtual "
-"network infrastructure to which the instance will connect, including the "
-"<link linkend=\"neutron_initial-external-network\">external network</link> "
-"and <link linkend=\"neutron_initial-tenant-network\">tenant network</link>. "
-"See <xref linkend=\"neutron_figure-neutron-initial-networks\"/>. After "
-"creating this infrastructure, we recommend that you <link linkend"
-"=\"neutron_initial-networks-verify\">verify connectivity</link> and resolve "
-"any issues before proceeding further."
-msgstr "初めてのインスタンスを起動する前に、インスタンスが接続するために必要な仮想ネットワークを作成する必要があります。これには、 <link linkend=\"neutron_initial-external-network\">外部ネットワーク</link>と<link linkend=\"neutron_initial-tenant-network\">プロジェクトネットワーク</link>があります。<xref linkend=\"neutron_figure-neutron-initial-networks\"/>を参照してください。このネットワークの作成後、<link linkend=\"neutron_initial-networks-verify\">接続性を検証し</link>、続行する前にすべての問題を解決することを推奨します。"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml19(title)
-msgid "Initial networks"
-msgstr "初期ネットワーク"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml28(title)
-msgid "External network"
-msgstr "外部ネットワーク"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml29(para)
-msgid ""
-"The external network typically provides internet access for your instances. "
-"By default, this network only allows internet access "
-"<emphasis>from</emphasis> instances using <glossterm>Network Address "
-"Translation (NAT)</glossterm>. You can enable internet access "
-"<emphasis>to</emphasis> individual instances using a <glossterm>floating IP "
-"address</glossterm> and suitable <glossterm>security group</glossterm> "
-"rules. The <literal>admin</literal> tenant owns this network because it "
-"provides external network access for multiple tenants. You must also enable "
-"sharing to allow access by those tenants."
-msgstr "一般的に外部ネットワークにより、インスタンスにインターネットアクセスが提供されます。デフォルトでこのネットワークのみにより、インスタンス<emphasis>から </emphasis><glossterm baseform=\"Network Address Translation (NAT)\">NAT</glossterm> を使用して、インターネットへのアクセスが許可されます。<glossterm baseform=\"floating IP address\">Floating IP アドレス</glossterm>と適切な<glossterm baseform=\"security group\">セキュリティグループ</glossterm>ルールを使用して、個々のインスタンス<emphasis>へと</emphasis>インターネットからアクセス可能にできます。<literal>admin</literal> プロジェクトは、複数のプロジェクトに対して外部ネットワークを提供するため、このネットワークを所有します。これらのプロジェクトによりアクセスを許可するために、共有を有効化する必要があります。"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml43(title)
-msgid "To create the external network"
-msgstr "外部ネットワークの作成方法"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml69(para)
-msgid ""
-"Like a physical network, a virtual network requires a "
-"<glossterm>subnet</glossterm> assigned to it. The external network shares "
-"the same subnet and <glossterm>gateway</glossterm> associated with the "
-"physical network connected to the external interface on the network node. "
-"You should specify an exclusive slice of this subnet for "
-"<glossterm>router</glossterm> and floating IP addresses to prevent "
-"interference with other devices on the external network."
-msgstr "物理ネットワーク同様、仮想ネットワークは関連づける<glossterm baseform=\"subnet\">サブネット</glossterm>が必要です。外部ネットワークは、ネットワークノードの外部インターフェースに接続された物理ネットワークと関連づけられた、同じサブネットと<glossterm baseform=\"gateway\">ゲートウェイ</glossterm>を共有します。外部ネットワークの他のデバイスと競合しないよう、このサブネットの<glossterm baseform=\"router\">ルーター</glossterm>専用範囲と Floating IP アドレスを指定すべきです。"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml76(para)
-msgid ""
-"Replace <replaceable>FLOATING_IP_START</replaceable> and "
-"<replaceable>FLOATING_IP_END</replaceable> with the first and last IP "
-"addresses of the range that you want to allocate for floating IP addresses. "
-"Replace <replaceable>EXTERNAL_NETWORK_CIDR</replaceable> with the subnet "
-"associated with the physical network. Replace "
-"<replaceable>EXTERNAL_NETWORK_GATEWAY</replaceable> with the gateway "
-"associated with the physical network, typically the \".1\" IP address. You "
-"should disable <glossterm>DHCP</glossterm> on this subnet because instances "
-"do not connect directly to the external network and floating IP addresses "
-"require manual assignment."
-msgstr "<replaceable>FLOATING_IP_START</replaceable> と <replaceable>FLOATING_IP_END</replaceable> を、Floating IP アドレスに割り当てたい IP アドレス範囲の開始アドレスと終了アドレスで置き換えます。<replaceable>EXTERNAL_NETWORK_CIDR</replaceable> を物理ネットワークに関連づけられたサブネットで置き換えます。<replaceable>EXTERNAL_NETWORK_GATEWAY</replaceable> を物理ネットワークに関連づけられたゲートウェイで置き換えます。一般的に「.1」の IP アドレスを使用します。インスタンスは外部ネットワークに直接接続せず、Floating IP アドレスは手動で割り当てる必要があるため、このサブネットで <glossterm>DHCP</glossterm> を無効化すべきです。"
+#: ./doc/install-guide/section_trove-verify.xml30(para)
+msgid "This example shows you how to create a MySQL 5.5 database:"
+msgstr "この例は MySQL 5.5 データベースを作成する方法です。"
 
-#: ./doc/install-guide/section_neutron-initial-networks.xml87(title)
-msgid "To create a subnet on the external network"
-msgstr "外部ネットワークへのサブネットの作成方法"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml89(para)
-#: ./doc/install-guide/section_neutron-initial-networks.xml164(para)
-msgid "Create the subnet:"
-msgstr "サブネットを作成します。"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml91(replaceable)
-msgid "FLOATING_IP_START"
-msgstr "FLOATING_IP_START"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml91(replaceable)
-msgid "FLOATING_IP_END"
-msgstr "FLOATING_IP_END"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml92(replaceable)
-msgid "EXTERNAL_NETWORK_GATEWAY"
-msgstr "EXTERNAL_NETWORK_GATEWAY"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml92(replaceable)
-msgid "EXTERNAL_NETWORK_CIDR"
-msgstr "EXTERNAL_NETWORK_CIDR"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml93(para)
-msgid ""
-"For example, using <literal>203.0.113.0/24</literal> with floating IP "
-"address range <literal>203.0.113.101</literal> to "
-"<literal>203.0.113.200</literal>:"
-msgstr "例えば、Floating IP アドレス範囲 <literal>203.0.113.101</literal> 〜 <literal>203.0.113.200</literal> を持つ <literal>203.0.113.0/24</literal> を使用する場合:"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml121(title)
-msgid "Tenant network"
-msgstr "テナントネットワーク"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml122(para)
-msgid ""
-"The tenant network provides internal network access for instances. The "
-"architecture isolates this type of network from other tenants. The "
-"<literal>demo</literal> tenant owns this network because it only provides "
-"network access for instances within it."
-msgstr "プロジェクトネットワークは、インスタンス用の内部ネットワークアクセスを提供します。このアーキテクチャは、この種のネットワークを他のプロジェクトと分離します。<literal>demo</literal> プロジェクトは、プロジェクト内のインスタンスのみにネットワークアクセスを提供するため、このネットワークを所有します。"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml130(title)
-msgid "To create the tenant network"
-msgstr "テナントネットワークの作成方法"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml152(para)
-msgid ""
-"Like the external network, your tenant network also requires a subnet "
-"attached to it. You can specify any valid subnet because the architecture "
-"isolates tenant networks. Replace "
-"<replaceable>TENANT_NETWORK_CIDR</replaceable> with the subnet you want to "
-"associate with the tenant network. Replace "
-"<replaceable>TENANT_NETWORK_GATEWAY</replaceable> with the gateway you want "
-"to associate with this network, typically the \".1\" IP address. By default,"
-" this subnet will use DHCP so your instances can obtain IP addresses."
-msgstr "外部ネットワーク同様、プロジェクトネットワークも接続するサブネットが必要です。このアーキテクチャはプロジェクトネットワークを分離するため、任意の有効なサブネットを指定できます。プロジェクトネットワークに関連づけたいサブネットで <replaceable>TENANT_NETWORK_CIDR</replaceable> を置き換えます。このネットワークに関連づけたいゲートウェイで <replaceable>TENANT_NETWORK_GATEWAY</replaceable> を置き換えます。一般的に「.1」の IP アドレスを使用します。デフォルトで、このサブネットはDHCP を使用するため、インスタンスが IP アドレスを取得できます。"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml162(title)
-msgid "To create a subnet on the tenant network"
-msgstr "テナントネットワークへのサブネットの作成方法"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml166(replaceable)
-msgid "TENANT_NETWORK_GATEWAY"
-msgstr "TENANT_NETWORK_GATEWAY"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml166(replaceable)
-msgid "TENANT_NETWORK_CIDR"
-msgstr "TENANT_NETWORK_CIDR"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml167(para)
-msgid "Example using <literal>192.168.1.0/24</literal>:"
-msgstr "<literal>192.168.1.0/24</literal> を用いた例:"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml190(para)
-msgid ""
-"A virtual router passes network traffic between two or more virtual "
-"networks. Each router requires one or more <glossterm "
-"baseform=\"interface\">interfaces</glossterm> and/or gateways that provide "
-"access to specific networks. In this case, you will create a router and "
-"attach your tenant and external networks to it."
-msgstr "仮想ルーターは、複数の仮想ネットワーク間でネットワーク通信を転送します。各ルーターは、指定したネットワークにアクセスする、1 つ以上の<glossterm baseform=\"interface\">インターフェース</glossterm>とゲートウェイが必要です。今回、ルーターを作成し、プロジェクトネットワークと外部ネットワークを接続します。"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml196(title)
-msgid ""
-"To create a router on the tenant network and attach the external and tenant "
-"networks to it"
-msgstr "プロジェクトネットワークにルーターを作成し、外部ネットワークとプロジェクトネットワークを接続する方法"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml199(para)
-msgid "Create the router:"
-msgstr "ルーターを作成します。"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml214(para)
-msgid "Attach the router to the <literal>demo</literal> tenant subnet:"
-msgstr "ルーターを <literal>demo</literal> テナントサブネットに接続します。"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml220(para)
-msgid ""
-"Attach the router to the external network by setting it as the gateway:"
-msgstr "外部ネットワークをゲートウェイとして設定し、ルーターに接続します。"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml229(para)
-msgid ""
-"We recommend that you verify network connectivity and resolve any issues "
-"before proceeding further. Following the external network subnet example "
-"using <literal>203.0.113.0/24</literal>, the tenant router gateway should "
-"occupy the lowest IP address in the floating IP address range, "
-"<literal>203.0.113.101</literal>. If you configured your external physical "
-"network and virtual networks correctly, you you should be able to "
-"<placeholder-1/> this IP address from any host on your external physical "
-"network."
-msgstr "ネットワーク接続性を検証し、続行する前にすべての問題を解決することを推奨します。<literal>203.0.113.0/24</literal> を使用した例の外部ネットワークのサブネットに従うと、プロジェクトのルーターゲートウェイは Floating IP アドレス範囲の最小値 <literal>203.0.113.101</literal> を使用すべきです。外部物理ネットワークと仮想ネットワークを適切に設定した場合、外部物理ネットワークにあるホストから、この IP アドレスに <placeholder-1/> できるでしょう。"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml238(para)
-msgid ""
-"If you are building your OpenStack nodes as virtual machines, you must "
-"configure the hypervisor to permit promiscuous mode on the external network."
-msgstr "OpenStack のノードを仮想マシンとして構築する場合、外部ネットワークのプロミスキャスモードを許可するよう、ハイパーバイザーを設定する必要があります。"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml243(title)
-msgid "To verify network connectivity"
-msgstr "ネットワーク接続性の確認方法"
-
-#: ./doc/install-guide/section_neutron-initial-networks.xml245(para)
-msgid "Ping the tenant router gateway:"
-msgstr "プロジェクトのゲートウェイに ping します。"
-
-#: ./doc/install-guide/section_heat-install.xml5(title)
-msgid "Install the Orchestration service"
-msgstr "Orchestration Service のインストール"
-
-#: ./doc/install-guide/section_heat-install.xml8(para)
-#: ./doc/install-guide/section_heat-install.xml24(para)
-msgid "Install the Orchestration module on the controller node:"
-msgstr "コントローラーノードに Orchestration モジュールをインストールします。"
-
-#: ./doc/install-guide/section_heat-install.xml13(para)
-msgid ""
-"Respond to prompts for <link linkend=\"debconf-dbconfig-common\">database "
-"management</link>, <link linkend=\"debconf-"
-"keystone_authtoken\"><systemitem>[keystone_authtoken]</systemitem> "
-"settings</link>, <link linkend=\"debconf-rabbitqm\">RabbitMQ "
-"credentials</link> and <link linkend=\"debconf-api-endpoints\">API "
-"endpoint</link> registration."
-msgstr "<link linkend=\"debconf-dbconfig-common\">データベース管理</link>、<link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> 設定</link>、<link linkend=\"debconf-rabbitqm\">RabbitMQ クレデンシャル</link>、<link linkend=\"debconf-api-endpoints\">API エンドポイント</link>の登録に関するプロンプトに答えます。"
-
-#: ./doc/install-guide/section_heat-install.xml33(para)
-msgid ""
-"In the configuration file, specify the location of the database where the "
-"Orchestration service stores data. These examples use a MySQL database with "
-"a <literal>heat</literal> user on the controller node. Replace "
-"<replaceable>HEAT_DBPASS</replaceable> with the password for the database "
-"user:"
-msgstr "Orchestration Service がデータを保存するデータベースの場所を設定ファイルで指定します。これらの例はコントローラーノードにユーザー名 <literal>heat</literal> で MySQL データベースを使用します。<literal><replaceable>HEAT_DBPASS</replaceable></literal> をデータベースのユーザーの適切なパスワードで置き換えます。"
-
-#: ./doc/install-guide/section_heat-install.xml40(replaceable)
-#: ./doc/install-guide/section_heat-install.xml46(replaceable)
-#: ./doc/install-guide/section_heat-install.xml61(replaceable)
-#: ./doc/install-guide/section_heat-install.xml63(replaceable)
-msgid "HEAT_DBPASS"
-msgstr "HEAT_DBPASS"
-
-#: ./doc/install-guide/section_heat-install.xml41(para)
-msgid ""
-"Edit <filename>/etc/heat/heat.conf</filename> and modify the "
-"<literal>[database]</literal> section:"
-msgstr "<filename>/etc/heat/heat.conf</filename> を編集し、<literal>[database]</literal> セクションを変更します。"
-
-#: ./doc/install-guide/section_heat-install.xml49(para)
-msgid ""
-"By default, the Ubuntu packages create an SQLite database. Delete the "
-"<filename>heat.sqlite</filename> file that was created in the "
-"<filename>/var/lib/heat/</filename> directory so that it does not get used "
-"by mistake:"
-msgstr "Ubuntu パッケージはデフォルトで SQLite データベースを作成します。誤って使用されないように、<filename>/var/lib/heat/</filename> に作成された <filename>heat.sqlite</filename> ファイルを削除します。"
-
-#: ./doc/install-guide/section_heat-install.xml56(para)
-msgid ""
-"Use the password that you set previously to log in as "
-"<literal>root</literal> and create a <literal>heat</literal> database user:"
-msgstr "<literal>root</literal> としてログインするために前に設定したパスワードを使用し、<literal>heat</literal> データベースユーザーを作成します。"
-
-#: ./doc/install-guide/section_heat-install.xml66(para)
-msgid "Create the heat service tables:"
-msgstr "heat サービスのテーブルを作成します。"
-
-#: ./doc/install-guide/section_heat-install.xml69(para)
-msgid "Ignore <errortext>DeprecationWarning</errortext> errors."
-msgstr "<errortext>DeprecationWarning</errortext> エラーを無視します。"
-
-#: ./doc/install-guide/section_heat-install.xml74(para)
-msgid ""
-"The Ubuntu packages do not correctly set up logging. Edit the "
-"<filename>/etc/heat/heat.conf</filename> file and change the "
-"<literal>[DEFAULT]</literal> section:"
-msgstr "Ubuntu パッケージはロギングを正しくセットアップしません。<filename>/etc/heat/heat.conf</filename> ファイルを編集し、<literal>[DEFAULT]</literal> セクションを変更します。"
-
-#: ./doc/install-guide/section_heat-install.xml88(para)
-msgid ""
-"Configure the Orchestration Service to use the RabbitMQ message broker."
-msgstr "Orchestration Service が RabbitMQ メッセージブローカーを使用するよう設定します。"
-
-#: ./doc/install-guide/section_heat-install.xml90(para)
-msgid ""
-"Edit <filename>/etc/heat/heat.conf</filename> and modify the "
-"<literal>[DEFAULT]</literal> section:"
-msgstr "<filename>/etc/heat/heat.conf</filename> を編集し、<literal>[DEFAULT]</literal> セクションを変更します。"
-
-#: ./doc/install-guide/section_heat-install.xml99(para)
-msgid ""
-"Create a <literal>heat</literal> user that the Orchestration service can use"
-" to authenticate with the Identity Service. Use the "
-"<literal>service</literal> tenant and give the user the "
-"<literal>admin</literal> role:"
-msgstr "Orchestration サービスが Identity Service で認証するために使用する <literal>heat</literal> ユーザーを作成します。<literal>service</literal> プロジェクトを使用し、ユーザーに <literal>admin</literal> ロールを与えます。"
-
-#: ./doc/install-guide/section_heat-install.xml103(replaceable)
-#: ./doc/install-guide/section_heat-install.xml119(replaceable)
-msgid "HEAT_PASS"
-msgstr "HEAT_PASS"
-
-#: ./doc/install-guide/section_heat-install.xml104(replaceable)
-msgid "heat@example.com"
-msgstr "heat@example.com"
-
-#: ./doc/install-guide/section_heat-install.xml108(para)
-msgid ""
-"Edit the <filename>/etc/heat/heat.conf</filename> file to change the "
-"<literal>[keystone_authtoken]</literal> and "
-"<literal>[ec2authtoken]</literal> sections to add credentials to the "
-"Orchestration Service:"
-msgstr "Orchestration Service のクレデンシャルを追加するために、<filename>/etc/heat/heat.conf</filename> ファイルを編集し、<literal>[keystone_authtoken]</literal> セクションと <literal>[ec2authtoken]</literal> セクションを変更します。"
-
-#: ./doc/install-guide/section_heat-install.xml125(para)
-msgid ""
-"Register the Heat and CloudFormation APIs with the Identity Service so that "
-"other OpenStack services can locate these APIs. Register the services and "
-"specify the endpoints:"
-msgstr "他の OpenStack サービスから使用できるように、Heat と CloudFormation API を Identity Service に登録します。サービスを登録し、エンドポイントを指定します。"
-
-#: ./doc/install-guide/section_heat-install.xml145(para)
-msgid "Create the <literal>heat_stack_user</literal> role."
-msgstr "<literal>heat_stack_user</literal> ロールを作成します。"
-
-#: ./doc/install-guide/section_heat-install.xml146(para)
-msgid ""
-"This role is used as the default role for users created by the Orchestration"
-" module."
-msgstr "このロールは、Orchestration モジュールにより作成されたユーザーのデフォルトのロールとして使用されます。"
-
-#: ./doc/install-guide/section_heat-install.xml148(para)
-msgid ""
-"Run the following command to create the <literal>heat_stack_user</literal> "
-"role:"
-msgstr "<literal>heat_stack_user</literal> ロールを作成するために、以下のコマンドを実行します。"
-
-#: ./doc/install-guide/section_heat-install.xml153(para)
-msgid "Configure the metadata and waitcondition servers' URLs."
-msgstr "メタデータと待機条件のサーバーの URL を設定します。"
-
-#: ./doc/install-guide/section_heat-install.xml154(para)
-msgid ""
-"Edit the <filename>/etc/heat/heat.conf</filename> file and modify the "
-"following options in the <literal>[DEFAULT]</literal> section:"
-msgstr "<filename>/etc/heat/heat.conf</filename> ファイルを編集し、<literal>[DEFAULT]</literal> セクションの以下のオプションを変更します。"
-
-#: ./doc/install-guide/section_heat-install.xml160(replaceable)
-#: ./doc/install-guide/section_heat-install.xml163(replaceable)
-#: ./doc/install-guide/section_heat-install.xml168(replaceable)
-#: ./doc/install-guide/section_heat-install.xml170(replaceable)
-msgid "10.0.0.11"
-msgstr "10.0.0.11"
-
-#: ./doc/install-guide/section_heat-install.xml164(para)
-msgid ""
-"Run the following commands to modify the <literal>[DEFAULT]</literal> "
-"section of the <filename>/etc/heat/heat.conf</filename> file:"
-msgstr "<filename>/etc/heat/heat.conf</filename> ファイルの <literal>[DEFAULT]</literal> セクションを変更するために、以下のコマンドを実行します。"
-
-#: ./doc/install-guide/section_heat-install.xml172(para)
-msgid ""
-"The example uses the IP address of the controller (10.0.0.11) instead of the"
-" <literal>controller</literal> host name since our example architecture does"
-" not include a DNS setup. Make sure that the instances can resolve the "
-"controller host name if you choose to use it in the URLs."
-msgstr "このアーキテクチャー例は DNS サーバーを持たないため、この例は <literal>controller</literal> というホスト名の代わりに IP アドレス (10.0.0.11) を使用します。URL にホスト名を使用する場合、インスタンスがコントローラーのホスト名を名前解決できることを確認してください。"
-
-#: ./doc/install-guide/section_heat-install.xml186(para)
-msgid ""
-"Start the <systemitem class=\"service\">heat-api</systemitem>, <systemitem "
-"class=\"service\">heat-api-cfn</systemitem> and <systemitem class=\"service"
-"\">heat-engine</systemitem> services and configure them to start when the "
-"system boots:"
-msgstr "<systemitem class=\"service\">heat-api</systemitem>、<systemitem class=\"service\">heat-api-cfn</systemitem>、<systemitem class=\"service\">heat-engine</systemitem> サービスを起動し、システムの起動時にそれらが起動するよう設定します。"
-
-#: ./doc/install-guide/section_ceilometer-nova.xml7(title)
-msgid "Install the Compute agent for Telemetry"
-msgstr "Telemetry 用 Compute エージェントのインストール"
-
-#: ./doc/install-guide/section_ceilometer-nova.xml9(para)
-msgid ""
-"Telemetry provides an API service that provides a collector and a range of "
-"disparate agents. This procedure details how to install the agent that runs "
-"on the compute node."
-msgstr "Telemetry は情報収集機能とさまざまな種類のエージェントを提供する API サービスを提供します。この手順はコンピュートノードで実行するエージェントをインストールする方法を詳細に説明します。"
-
-#: ./doc/install-guide/section_ceilometer-nova.xml14(para)
-msgid "Install the Telemetry service on the compute node:"
-msgstr "コンピュートノードに Telemetry Service をインストールします。"
-
-#: ./doc/install-guide/section_ceilometer-nova.xml20(para)
-msgid ""
-"Set the following options in the <filename>/etc/nova/nova.conf</filename> "
-"file:"
-msgstr "<filename>/etc/nova/nova.conf</filename> ファイルに以下のオプションを設定します。"
-
-#: ./doc/install-guide/section_ceilometer-nova.xml30(para)
-msgid ""
-"The <option>notification_driver</option> option is a multi valued option, "
-"which <application>openstack-config</application> cannot set properly. See "
-"<xref linkend=\"basics-packages\"/>."
-msgstr "<option>notification_driver</option> オプションは複数の値を持つオプションです。<application>openstack-config</application> はこれを正しく設定できません。<xref linkend=\"basics-packages\"/>を参照してください。"
-
-#: ./doc/install-guide/section_ceilometer-nova.xml36(para)
-msgid ""
-"Edit the <filename>/etc/nova/nova.conf</filename> file and add the following"
-" lines to the <literal>[DEFAULT]</literal> section:"
-msgstr "<filename>/etc/nova/nova.conf</filename> ファイルを編集し、<literal>[DEFAULT]</literal> セクションに以下の行を追加します。"
-
-#: ./doc/install-guide/section_ceilometer-nova.xml58(para)
-msgid ""
-"You must set the secret key that you defined previously. The Telemetry "
-"service nodes share this key as a shared secret:"
-msgstr "前に設定したシークレットキーを設定する必要があります。Telemetry Service ノードは共有シークレットとしてこのキーを共有します。"
-
-#: ./doc/install-guide/section_ceilometer-nova.xml63(para)
-msgid ""
-"Edit the <filename>/etc/ceilometer/ceilometer.conf</filename> file and "
-"change these lines in the <literal>[publisher]</literal> section. Replace "
-"<replaceable>CEILOMETER_TOKEN</replaceable> with the ceilometer token that "
-"you created previously:"
-msgstr "<filename>/etc/ceilometer/ceilometer.conf</filename> ファイルを編集し、<literal>[publisher]</literal> セクションでこれらの行を変更します。<replaceable>CEILOMETER_TOKEN</replaceable> を前に作成した ceilometer トークンに置き換えます。"
+#: ./doc/install-guide/section_trove-verify.xml32(replaceable)
+msgid "name"
+msgstr "名前"
 
-#: ./doc/install-guide/section_ceilometer-nova.xml84(para)
-msgid "Configure the QPid access:"
-msgstr "Qpid のアクセス権を設定します。"
+#: ./doc/install-guide/section_trove-verify.xml32(replaceable)
+msgid "DBNAME"
+msgstr "DBNAME"
 
-#: ./doc/install-guide/section_ceilometer-nova.xml89(para)
-msgid "Add the Identity service credentials:"
-msgstr "Identity Service のクレデンシャルを追加します。"
+#: ./doc/install-guide/section_trove-verify.xml33(replaceable)
+msgid "USER"
+msgstr "USER"
 
-#: ./doc/install-guide/section_ceilometer-nova.xml141(para)
-msgid "Start the service and configure it to start when the system boots:"
-msgstr "サービスを起動し、システム起動時に起動するよう設定します。"
+#: ./doc/install-guide/section_trove-verify.xml33(replaceable)
+msgid "PASSWORD"
+msgstr "PASSWORD"
 
-#: ./doc/install-guide/section_nova-compute.xml5(title)
-msgid "Configure a compute node"
-msgstr "コンピュートノードの設定"
+#: ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml6(title)
+msgid "Add another proxy server"
+msgstr "プロキシサーバーの追加"
 
-#: ./doc/install-guide/section_nova-compute.xml6(para)
+#: ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml7(para)
 msgid ""
-"After you configure the Compute service on the controller node, you must "
-"configure another system as a compute node. The compute node receives "
-"requests from the controller node and hosts virtual machine instances. You "
-"can run all services on a single node, but the examples in this guide use "
-"separate systems. This makes it easy to scale horizontally by adding "
-"additional Compute nodes following the instructions in this section."
-msgstr "コントローラーノードで Compute サービスを設定した後、他のシステムをコンピュートノードとして設定する必要があります。コンピュートノードはコントローラーノードからリクエストを受け取り、仮想マシンインスタンスをホストします。単一ノードですべてのサービスを実行することもできます。しかし、このガイドの例では分離したシステムを使用します。これにより、このセクションにある説明に従って、追加のコンピュートノードを追加して、水平的にスケールさせることが容易になります。"
-
-#: ./doc/install-guide/section_nova-compute.xml13(para)
-msgid ""
-"The Compute service relies on a hypervisor to run virtual machine instances."
-" OpenStack can use various hypervisors, but this guide uses KVM."
-msgstr "Compute サービスは仮想マシンインスタンスを実行するためにハイパーバイザーに依存します。OpenStack はさまざまなハイパーバイザーを使用できますが、このガイドは KVM を使用します。"
-
-#: ./doc/install-guide/section_nova-compute.xml18(para)
-msgid "Install the Compute packages:"
-msgstr "Compute のパッケージをインストールします。"
-
-#: ./doc/install-guide/section_nova-compute.xml20(para)
-msgid ""
-"When prompted to create a <literal>supermin</literal> appliance, respond "
-"<placeholder-1/>."
-msgstr "<literal>supermin</literal> アプライアンスを作成するためのプロンプトが表示されたとき、<placeholder-1/> を答えます。"
-
-#: ./doc/install-guide/section_nova-compute.xml25(para)
-msgid ""
-"To use the meta-packages and install other components on your compute node, "
-"such as OpenStack Networking and Telemetry agents, run this command:"
-msgstr "メタパッケージを使用して、OpenStack Networking や Ceilometer のエージェントのような他のコンポーネントをコンピュートノードにインストールするために、このコマンドを実行します。"
-
-#: ./doc/install-guide/section_nova-compute.xml29(para)
-msgid ""
-"The controller node has the <package>openstack-proxy-node</package> and "
-"<package>openstack-toaster</package> meta-packages that install <package"
-">openstack-proxy-node</package> and <package>openstack-toaster</package> at "
-"the same time."
-msgstr "コントローラーノードは同時に、<package>openstack-proxy-node</package> と <package>openstack-toaster</package> をインストールする、<package>openstack-proxy-node</package> メタパッケージと <package>openstack-toaster</package> メタパッケージを持ちます。"
-
-#: ./doc/install-guide/section_nova-compute.xml41(para)
-msgid ""
-"Respond to the prompts for <link linkend=\"debconf-dbconfig-"
-"common\">database management</link>, <link linkend=\"debconf-"
-"keystone_authtoken\"><literal>[keystone_authtoken]</literal> "
-"settings</link>, <link linkend=\"debconf-rabbitqm\">RabbitMQ "
-"credentials</link>, and <link linkend=\"debconf-api-endpoints\">API "
-"endpoint</link> registration."
-msgstr "<link linkend=\"debconf-dbconfig-common\">データベース管理</link>、<link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> 設定</link>、<link linkend=\"debconf-rabbitqm\">RabbitMQ クレデンシャル</link>、<link linkend=\"debconf-api-endpoints\">API エンドポイント</link>登録に関するプロンプトに答えます。キャッシュタイプを選択する必要もあります。"
-
-#: ./doc/install-guide/section_nova-compute.xml50(para)
-msgid ""
-"For security reasons, the Linux kernel is not readable by normal users which"
-" restricts hypervisor services such as qemu and libguestfs. For details, see"
-" <link "
-"href=\"https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725\">this "
-"bug</link>. To make the current kernel readable, run: <placeholder-1/> To "
-"also enable this override for all future kernel updates, create the file "
-"<filename>/etc/kernel/postinst.d/statoverride</filename> "
-"containing:<placeholder-2/> Remember to make the file executable: "
-"<placeholder-3/>"
-msgstr "セキュリティの理由から、Linux カーネルは通常のユーザーにより読み取りできません。これにより QEMU や libguestfs のようなハイパーバイザーサービスを制限します。詳細は<link href=\"https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725\">このバグ</link>を参照してください。現在のカーネルを読み取り可能にするために、<placeholder-1/> を実行します。今後のすべてのカーネル更新でこの上書きを有効にするために、以下を含めた <filename>/etc/kernel/postinst.d/statoverride</filename> ファイルを作成します。<placeholder-2/> 忘れずに、ファイルを実行可能にします。<placeholder-3/>"
-
-#: ./doc/install-guide/section_nova-compute.xml69(para)
-msgid "Edit the <filename>/etc/nova/nova.conf</filename> configuration file:"
-msgstr "<filename>/etc/nova/nova.conf</filename> 設定ファイルを編集します。"
-
-#: ./doc/install-guide/section_nova-compute.xml81(para)
-msgid ""
-"Edit the <filename>/etc/nova/nova.conf</filename> configuration file and add"
-" these lines to the appropriate sections:"
-msgstr "<filename>/etc/nova/nova.conf</filename> 設定ファイルを編集し、これらの行を適切なセクションに追加します。"
-
-#: ./doc/install-guide/section_nova-compute.xml102(para)
-msgid ""
-"Configure the Compute service to use the Qpid message broker by setting "
-"these configuration keys:"
-msgstr "これらの設定キーを設定することにより、Compute サービスが Qpid メッセージブローカーを使用するよう設定します。"
-
-#: ./doc/install-guide/section_nova-compute.xml116(para)
-msgid ""
-"Configure the Compute service to use the RabbitMQ message broker by setting "
-"these configuration keys:"
-msgstr "これらの設定キーを設定することにより、Compute サービスが RabbitMQ メッセージブローカーを使用するよう設定します。"
-
-#: ./doc/install-guide/section_nova-compute.xml125(para)
-msgid "Configure Compute to provide remote console access to instances."
-msgstr "インスタンスへのリモートコンソールアクセスを提供するよう Compute を設定します。"
-
-#: ./doc/install-guide/section_nova-compute.xml132(para)
-msgid ""
-"Edit <filename>/etc/nova/nova.conf</filename> and add the following keys "
-"under the <literal>[DEFAULT]</literal> section:"
-msgstr "<filename>/etc/nova/nova.conf</filename> を編集し、以下のキーを <literal>[DEFAULT]</literal> セクションに追加します。"
-
-#: ./doc/install-guide/section_nova-compute.xml146(para)
-msgid ""
-"Specify the host that runs the Image Service.<phrase os=\"ubuntu;debian\"> "
-"Edit <filename>/etc/nova/nova.conf</filename> file and add these lines to "
-"the <literal>[DEFAULT]</literal> section:</phrase>"
-msgstr "Image Service を実行するホストを指定します。<phrase os=\"ubuntu;debian\"><filename>/etc/nova/nova.conf</filename> ファイルを編集し、これらの行を <literal>[DEFAULT]</literal> セクションに追加します。</phrase>"
-
-#: ./doc/install-guide/section_nova-compute.xml157(para)
-msgid ""
-"You must determine whether your system's processor and/or hypervisor support"
-" hardware acceleration for virtual machines."
-msgstr "お使いのシステムのプロセッサーとハイパーバイザーが仮想マシンのハードウェア支援機能をサポートするかどうか確認する必要があります。"
-
-#: ./doc/install-guide/section_nova-compute.xml161(para)
-msgid ""
-"If this command returns a value of <emphasis>one or greater</emphasis>, your"
-" system supports hardware acceleration which typically requires no "
-"additional configuration."
-msgstr "このコマンドが <emphasis>1 以上</emphasis>の値を返したならば、お使いのシステムがハードウェア支援機能をサポートし、一般的に追加の設定は必要ありません。"
-
-#: ./doc/install-guide/section_nova-compute.xml165(para)
-msgid ""
-"If this command returns a value of <emphasis>zero</emphasis>, your system "
-"does not support hardware acceleration and you must configure "
-"<literal>libvirt</literal> to use QEMU instead of KVM."
-msgstr "このコマンドが <emphasis>0</emphasis> を返す場合、お使いのシステムはハードウェア支援機能をサポートしません。<literal>libvirt</literal> は KVM の代わりに QEMU を使用する必要があります。"
-
-#: ./doc/install-guide/section_nova-compute.xml170(para)
-msgid ""
-"Edit the <literal>[libvirt]</literal> section in the <filename>/etc/nova"
-"/nova-compute.conf</filename> file to modify this key:"
-msgstr "このキーを変更するために <filename>/etc/nova/nova-compute.conf</filename> ファイルの <literal>[libvirt]</literal> セクションを編集します。"
-
-#: ./doc/install-guide/section_nova-compute.xml183(para)
-msgid ""
-"On Ubuntu 12.04, kernels backported from newer releases may not "
-"automatically load the KVM modules for hardware acceleration when the system"
-" boots. In this case, launching an instance will fail with the following "
-"message in the <filename>/var/log/nova/nova-compute.log</filename> file:"
-msgstr "Ubuntu 12.04 の場合、新しいカーネルからバックポートされたカーネルは、システム起動時に KVM のハードウェア支援機能のモジュールを自動的に読み込まない可能性があります。この場合、インスタンスの起動に失敗し、以下のメッセージが <filename>/var/log/nova/nova-compute.log</filename> ファイルに記録されます。"
-
-#: ./doc/install-guide/section_nova-compute.xml189(para)
-msgid ""
-"As a workaround for this issue, you must add the appropriate module for your"
-" system to the <filename>/etc/modules</filename> file."
-msgstr "この問題の回避策として、お使いのシステム用の適切なモジュールを <filename>/etc/modules</filename> ファイルに追加する必要があります。"
-
-#: ./doc/install-guide/section_nova-compute.xml192(para)
-msgid "For systems with Intel processors, run the following command:"
-msgstr "Intel プロセッサーのシステムの場合、以下のコマンドを実行します。"
-
-#: ./doc/install-guide/section_nova-compute.xml195(para)
-msgid "For systems with AMD processors, run the following command:"
-msgstr "AMD プロセッサーのシステムの場合、以下のコマンドを実行します。"
-
-#: ./doc/install-guide/section_nova-compute.xml201(para)
-msgid "Remove the SQLite database created by the packages:"
-msgstr "パッケージにより作成された SQLite データベースを削除します。"
-
-#: ./doc/install-guide/section_nova-compute.xml205(para)
-msgid ""
-"Start the Compute service and configure it to start when the system boots:"
-msgstr "Compute サービスを起動し、システム起動時に起動するよう設定します。"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_glance-install.xml38(None)
-msgid ""
-"@@image: 'figures/debconf-screenshots/glance-common_pipeline_flavor.png'; "
-"md5=78bef92c36a140ad042074f6345d8917"
-msgstr "@@image: 'figures/debconf-screenshots/glance-common_pipeline_flavor.png'; md5=78bef92c36a140ad042074f6345d8917"
-
-#: ./doc/install-guide/section_glance-install.xml5(title)
-msgid "Install the Image Service"
-msgstr "Image Service のインストール"
-
-#: ./doc/install-guide/section_glance-install.xml6(para)
-msgid ""
-"The OpenStack Image Service acts as a registry for virtual disk images. "
-"Users can add new images or take a snapshot of an image from an existing "
-"server for immediate storage. Use snapshots for back up and as templates to "
-"launch new servers. You can store registered images in Object Storage or in "
-"other locations. For example, you can store images in simple file systems or"
-" external web servers."
-msgstr "OpenStack Image Service は仮想ディスクイメージの登録管理者として動作します。ユーザーは新しいイメージを追加できます。イメージのスナップショットを既存のサーバーの直接ストレージから取得できます。バックアップのため、または新しいサーバーを起動するためのテンプレートとしてスナップショットを使用します。登録済みイメージを Object Storage に保存できます。例えば、イメージをシンプルなファイルシステムや外部ウェブサーバーに保存できます。"
-
-#: ./doc/install-guide/section_glance-install.xml14(para)
-msgid ""
-"This procedure assumes you set the appropriate environment variables to your"
-" credentials as described in <xref linkend=\"keystone-verify\"/>."
-msgstr "この手順は <xref linkend=\"keystone-verify\"/> に記載されているとおり、適切な環境変数にクレデンシャルを設定していると仮定しています。"
-
-#: ./doc/install-guide/section_glance-install.xml20(para)
-msgid "Install the Image Service on the controller node:"
-msgstr "コントローラーノードに Image Service をインストールします。"
-
-#: ./doc/install-guide/section_glance-install.xml27(para)
-msgid ""
-"Respond to prompts for <link linkend=\"debconf-dbconfig-common\">database "
-"management</link>, <link linkend=\"debconf-"
-"keystone_authtoken\"><literal>[keystone_authtoken]</literal> "
-"settings</link>, <link linkend=\"debconf-rabbitqm\">RabbitMQ "
-"credentials</link> and <link linkend=\"debconf-api-endpoints\">API "
-"endpoint</link> registration. You must also select the caching type:"
-msgstr "<link linkend=\"debconf-dbconfig-common\">データベース管理</link>、<link linkend=\"debconf-keystone_authtoken\"><literal>[keystone_authtoken]</literal> 設定</link>、<link linkend=\"debconf-rabbitqm\">RabbitMQ クレデンシャル</link>、<link linkend=\"debconf-api-endpoints\">API エンドポイント</link>登録に関するプロンプトに答えます。キャッシュタイプを選択する必要もあります。"
-
-#: ./doc/install-guide/section_glance-install.xml43(para)
-msgid ""
-"The Image Service stores information about images in a database. The "
-"examples in this guide use the MySQL database that is used by other "
-"OpenStack services."
-msgstr "Image Service はイメージに関する情報をデータベースに保存します。このガイドの例は、他の OpenStack サービスにより使用されている MySQL データベースを使用します。"
-
-#: ./doc/install-guide/section_glance-install.xml46(para)
-msgid ""
-"Configure the location of the database. The Image Service provides the "
-"<systemitem class=\"service\">glance-api</systemitem> and <systemitem "
-"class=\"service\">glance-registry</systemitem> services, each with its own "
-"configuration file. You must update both configuration files throughout this"
-" section. Replace <replaceable>GLANCE_DBPASS</replaceable> with your Image "
-"Service database password."
-msgstr "データベースの位置を設定します。Image Service はそれぞれの設定ファイルを用いて <systemitem class=\"service\">glance-api</systemitem> サービスと <systemitem class=\"service\">glance-registry</systemitem> サービスを提供します。このセクションを通して両方の設定ファイルを更新する必要があります。<replaceable>GLANCE_DBPASS</replaceable> をお使いの Image Service データベースのパスワードで置き換えます。"
-
-#: ./doc/install-guide/section_glance-install.xml55(replaceable)
-#: ./doc/install-guide/section_glance-install.xml57(replaceable)
-#: ./doc/install-guide/section_glance-install.xml120(replaceable)
-#: ./doc/install-guide/section_glance-install.xml122(replaceable)
-msgid "GLANCE_DBPASS"
-msgstr "GLANCE_DBPASS"
-
-#: ./doc/install-guide/section_glance-install.xml58(para)
-msgid ""
-"Edit <filename>/etc/glance/glance-api.conf</filename> and "
-"<filename>/etc/glance/glance-registry.conf</filename> and edit the "
-"<literal>[database]</literal> section of each file:"
-msgstr "<filename>/etc/glance/glance-api.conf</filename> と <filename>/etc/glance/glance-registry.conf</filename> の <literal>[database]</literal> セクションを編集します。"
-
-#: ./doc/install-guide/section_glance-install.xml70(para)
-#: ./doc/install-guide/section_glance-install.xml77(para)
-#: ./doc/install-guide/section_glance-install.xml95(para)
-msgid "Configure the Image Service to use the message broker:"
-msgstr "Image Service がメッセージブローカーを使用するよう設定します。"
-
-#: ./doc/install-guide/section_glance-install.xml80(para)
-msgid ""
-"Edit the <filename>/etc/glance/glance-api.conf</filename> file and add the "
-"following keys to the <literal>[DEFAULT]</literal> section:"
-msgstr "<filename>/etc/glance/glance-api.conf</filename> ファイルを編集し、以下のキーを <literal>[DEFAULT]</literal> セクションに追加します。"
-
-#: ./doc/install-guide/section_glance-install.xml108(para)
-msgid ""
-"By default, the Ubuntu packages create an SQLite database. Delete the "
-"<filename>glance.sqlite</filename> file created in the "
-"<filename>/var/lib/glance/</filename> directory so that it does not get used"
-" by mistake:"
-msgstr "Ubuntu パッケージはデフォルトで SQLite データベースを作成します。誤って使用されないように、<filename>/var/lib/glance/</filename> に作成された <filename>glance.sqlite</filename> ファイルを削除します。"
-
-#: ./doc/install-guide/section_glance-install.xml115(para)
-msgid ""
-"Use the password you created to log in as root and create a "
-"<literal>glance</literal> database user:"
-msgstr "root としてログインするために、作成したパスワードを使用します。<literal>glance</literal> データベースユーザーを作成します。"
-
-#: ./doc/install-guide/section_glance-install.xml125(para)
-msgid "Create the database tables for the Image Service:"
-msgstr "Image Service 用のデータベーステーブルを作成します。"
-
-#: ./doc/install-guide/section_glance-install.xml129(para)
-msgid ""
-"Create a <literal>glance</literal> user that the Image Service can use to "
-"authenticate with the Identity service. Choose a password and specify an "
-"email address for the <literal>glance</literal> user. Use the "
-"<literal>service</literal> tenant and give the user the "
-"<literal>admin</literal> role:"
-msgstr "Image Service が Identity Service で認証するために使用する <literal>glance</literal> ユーザーを作成します。<literal>service</literal> プロジェクトを使用し、ユーザーに <literal>admin</literal> ロールを与えます。"
-
-#: ./doc/install-guide/section_glance-install.xml135(replaceable)
-#: ./doc/install-guide/section_glance-install.xml159(replaceable)
-#: ./doc/install-guide/section_glance-install.xml175(replaceable)
-#: ./doc/install-guide/section_glance-install.xml194(replaceable)
-msgid "GLANCE_PASS"
-msgstr "GLANCE_PASS"
-
-#: ./doc/install-guide/section_glance-install.xml136(replaceable)
-msgid "glance@example.com"
-msgstr "glance@example.com"
-
-#: ./doc/install-guide/section_glance-install.xml140(para)
-msgid ""
-"Configure the Image Service to use the Identity Service for authentication."
-msgstr "Image Service が認証用に Identity Service を使用するよう設定します。"
-
-#: ./doc/install-guide/section_glance-install.xml142(para)
-msgid ""
-"Run the following commands and replace "
-"<replaceable>GLANCE_PASS</replaceable> with the password you chose for the "
-"<literal>glance</literal> user in the Identity Service:"
-msgstr "以下のコマンドを実行します。Identity Service で <literal>glance</literal> ユーザー用に選択したパスワードで <replaceable>GLANCE_PASS</replaceable> を置き換えます。"
-
-#: ./doc/install-guide/section_glance-install.xml178(para)
-msgid ""
-"Edit the <filename>/etc/glance/glance-api.conf</filename> and "
-"<filename>/etc/glance/glance-registry.conf</filename> files. Replace "
-"<replaceable>GLANCE_PASS</replaceable> with the password you chose for the "
-"<literal>glance</literal> user in the Identity service."
-msgstr "<filename>/etc/glance/glance-api.conf</filename> ファイルと <filename>/etc/glance/glance-registry.conf</filename> ファイルを編集します。Identity Service で <literal>glance</literal> ユーザー用に選択したパスワードで <replaceable>GLANCE_PASS</replaceable> を置き換えます。"
-
-#: ./doc/install-guide/section_glance-install.xml185(para)
-msgid ""
-"Add or modify the following keys under the "
-"<literal>[keystone_authtoken]</literal> section:"
-msgstr "以下のキーを <literal>[keystone_authtoken]</literal> セクションに追加または修正します。"
-
-#: ./doc/install-guide/section_glance-install.xml197(para)
-msgid ""
-"Modify the following key under the <literal>[paste_deploy]</literal> "
-"section:"
-msgstr "以下のキーを <literal>[paste_deploy]</literal> セクションに修正します。"
-
-#: ./doc/install-guide/section_glance-install.xml206(para)
-msgid ""
-"Register the Image Service with the Identity service so that other OpenStack"
-" services can locate it. Register the service and create the endpoint:"
-msgstr "他の OpenStack サービスから使用できるように、Image Service を Identity Service に登録します。サービスを登録し、エンドポイントを作成します。"
-
-#: ./doc/install-guide/section_glance-install.xml218(para)
-msgid ""
-"Restart the <systemitem class=\"service\">glance</systemitem> service with "
-"its new settings:"
-msgstr "新しい設定を用いて <systemitem class=\"service\">glance</systemitem> サービスを再起動します。"
-
-#: ./doc/install-guide/section_glance-install.xml224(para)
-msgid ""
-"Start the <systemitem class=\"service\">glance-api</systemitem> and "
-"<systemitem class=\"service\">glance-registry</systemitem> services and "
-"configure them to start when the system boots:"
-msgstr "<systemitem class=\"service\">glance-api</systemitem>、<systemitem class=\"service\">glance-registry</systemitem> サービスを起動し、システムの起動時にそれらが起動するよう設定します。"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml30(None)
-msgid ""
-"@@image: 'figures/debconf-screenshots/dbconfig-common_keep_admin_pass.png'; "
-"md5=01af4867c16e458306b8abd78a1fccc9"
-msgstr "@@image: 'figures/debconf-screenshots/dbconfig-common_keep_admin_pass.png'; md5=01af4867c16e458306b8abd78a1fccc9"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml39(None)
-msgid ""
-"@@image: 'figures/debconf-screenshots/dbconfig-"
-"common_used_for_remote_db.png'; md5=c6ec966bbfdee18ad87456cf4d44a56f"
-msgstr "@@image: 'figures/debconf-screenshots/dbconfig-common_used_for_remote_db.png'; md5=c6ec966bbfdee18ad87456cf4d44a56f"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml78(None)
-msgid ""
-"@@image: 'figures/debconf-screenshots/dbconfig-common_1_configure-with-"
-"dbconfig-yes-no.png'; md5=4e9d7bce27cc6c7bd68ce8622c80b60f"
-msgstr "@@image: 'figures/debconf-screenshots/dbconfig-common_1_configure-with-dbconfig-yes-no.png'; md5=4e9d7bce27cc6c7bd68ce8622c80b60f"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml87(None)
-msgid ""
-"@@image: 'figures/debconf-screenshots/dbconfig-common_2_db-types.png'; "
-"md5=a77beb7e13b487cf79716c2140f258c2"
-msgstr "@@image: 'figures/debconf-screenshots/dbconfig-common_2_db-types.png'; md5=a77beb7e13b487cf79716c2140f258c2"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml96(None)
-msgid ""
-"@@image: 'figures/debconf-screenshots/dbconfig-"
-"common_3_connection_method.png'; md5=6cc592e5dd5ea404ad7aad98b37a71f6"
-msgstr "@@image: 'figures/debconf-screenshots/dbconfig-common_3_connection_method.png'; md5=6cc592e5dd5ea404ad7aad98b37a71f6"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml105(None)
-msgid ""
-"@@image: 'figures/debconf-screenshots/dbconfig-"
-"common_4_mysql_root_password.png'; md5=873ec338742e37305583e9e692bcfdc6"
-msgstr "@@image: 'figures/debconf-screenshots/dbconfig-common_4_mysql_root_password.png'; md5=873ec338742e37305583e9e692bcfdc6"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml114(None)
-msgid ""
-"@@image: 'figures/debconf-screenshots/dbconfig-"
-"common_5_mysql_app_password.png'; md5=3651970770d05892f21d1b5741afbee6"
-msgstr "@@image: 'figures/debconf-screenshots/dbconfig-common_5_mysql_app_password.png'; md5=3651970770d05892f21d1b5741afbee6"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml123(None)
-msgid ""
-"@@image: 'figures/debconf-screenshots/dbconfig-"
-"common_6_mysql_app_password_confirm.png'; "
-"md5=060cc90aaf6f6fd5cea718064829c1b1"
-msgstr "@@image: 'figures/debconf-screenshots/dbconfig-common_6_mysql_app_password_confirm.png'; md5=060cc90aaf6f6fd5cea718064829c1b1"
-
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml6(title)
-msgid "Configure the database with dbconfig-common"
-msgstr "dbconfig-common を用いたデータベースの設定"
-
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml7(para)
-msgid ""
-"The <package>dbconfig-common</package> package provides a standard Debian "
-"interface that enables you to configure Debian database parameters. It "
-"includes localized prompts for many languages and it supports the OpenStack "
-"database back ends: SQLite, MySQL, and PostgreSQL."
-msgstr "<package>dbconfig-common</package> パッケージは、Debian のデータベースパラメーターを設定できる、標準的な Debian インターフェースを提供します。これは多くの言語に翻訳されたプロンプトを持ち、OpenStack のデータベースバックエンド SQLite、MySQL、PostgreSQL をサポートします。"
-
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml12(para)
-msgid ""
-"By default, the <package>dbconfig-common</package> package configures the "
-"OpenStack services to use SQLite3. So if you use <package>debconf</package> "
-"in non-interactive mode and without pre-seeding, the OpenStack services that"
-" you install use SQLite3."
-msgstr "<package>dbconfig-common</package> パッケージはデフォルトで、OpenStack サービスが SQLite3 を使用するよう設定します。そのため、<package>debconf</package> を非対話モードで事前シードせずに利用した場合、インストールした OpenStack サービスが SQLite3 を使用します。"
-
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml17(para)
-msgid ""
-"By default, <package>dbconfig-common</package> does not provide access to "
-"database servers over a network. If you want the <package>dbconfig-"
-"common</package> package to prompt for remote database servers that are "
-"accessed over a network and not through a UNIX socket file, reconfigure it, "
-"as follows:"
-msgstr "<package>dbconfig-common</package> はデフォルトで、ネットワーク経由でデータベースサーバーへのアクセスを提供しません。UNIX ソケットファイル経由ではなく、ネットワーク経由でアクセスさせるリモートデータベースサーバーに対して、<package>dbconfig-common</package> パッケージにプロンプトさせたい場合、以下のように再設定します。"
-
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml23(para)
-msgid ""
-"These screens appear when you re-configure the <package>dbconfig-"
-"common</package> package:"
-msgstr "これらの画面は <package>dbconfig-common</package> パッケージを再設定するときに表示されます。"
-
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml43(para)
-msgid ""
-"Unlike other <package>debconf</package> prompts, you cannot pre-seed the "
-"responses for the <package>dbconfig-common</package> prompts by using "
-"<placeholder-1/>. Instead, you must create a file in <filename>/etc"
-"/dbconfig-common</filename>. For example, you might create a keystone "
-"configuration file for <package>dbconfig-common</package> that is located in"
-" <filename>/etc/dbconfig-common/keystone.conf</filename>, as follows:"
-msgstr "他の <package>debconf</package> プロンプトと異なり、<placeholder-1/> を使用して <package>dbconfig-common</package> プロンプトに対する応答を事前シードできません。代わりに、<filename>/etc/dbconfig-common</filename> にファイルを作成する必要があります。例えば以下のように、<filename>/etc/dbconfig-common/keystone.conf</filename> にある <package>dbconfig-common</package> 用の Keystone 設定を作成することができます。"
-
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml66(para)
-msgid "After you create this file, run this command:"
-msgstr "このファイルを作成した後、このコマンドを実行します。"
-
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml68(para)
-msgid ""
-"The Identity Service is installed with MySQL as the database back end, "
-"<literal>keystonedb</literal> as database name, and the localhost socket "
-"file."
-msgstr "Identity Service は、データベースバックエンドとして MySQL、データベース名として <literal>keystonedb</literal>、ローカルホストのソケットファイルと一緒にインストールされます。"
-
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml71(para)
-msgid "The <package>cinder-common</package> package displays these screens:"
-msgstr "<package>cinder-common</package> パッケージはこれらの画面を表示します。"
-
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml127(para)
-msgid ""
-"To access a MySQL server remotely, you must make it accessible as root from "
-"a remote server. To do so, run the <package>openstack-proxy-node</package> "
-"package command:"
-msgstr "MySQL サーバーにリモートアクセスするために、リモートサーバーから root としてアクセス可能にする必要があります。そうするために、<package>openstack-proxy-node</package> パッケージコマンドを実行します。"
-
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml131(para)
-msgid ""
-"Alternatively, if you do not want to install this package, run this script "
-"to enable remote root access:"
-msgstr "代わりに、このパッケージをインストールしたくなければ、リモート root アクセスを有効化するために、このスクリプトを実行します。"
-
-#: ./doc/install-guide/section_debconf-dbconfig-common.xml154(para)
-msgid "You must enable remote access before you install OpenStack services."
-msgstr "OpenStack サービスをインストールする前にリモートアクセスを有効化する必要があります。"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_keystone-install.xml79(None)
-msgid ""
-"@@image: 'figures/debconf-screenshots/keystone_1_admin_token.png'; "
-"md5=29a51caaf09c3d6e3f0fda73c256a17a"
-msgstr "@@image: 'figures/debconf-screenshots/keystone_1_admin_token.png'; md5=29a51caaf09c3d6e3f0fda73c256a17a"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_keystone-install.xml104(None)
-msgid ""
-"@@image: 'figures/debconf-"
-"screenshots/keystone_2_register_admin_tenant_yes_no.png'; "
-"md5=25c9a90b1df2d979aae6ce9975c7285b"
-msgstr "@@image: 'figures/debconf-screenshots/keystone_2_register_admin_tenant_yes_no.png'; md5=25c9a90b1df2d979aae6ce9975c7285b"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_keystone-install.xml113(None)
-msgid ""
-"@@image: 'figures/debconf-screenshots/keystone_3_admin_user_name.png'; "
-"md5=173cf7ed13252df1425109be588b2ad6"
-msgstr "@@image: 'figures/debconf-screenshots/keystone_3_admin_user_name.png'; md5=173cf7ed13252df1425109be588b2ad6"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_keystone-install.xml122(None)
-msgid ""
-"@@image: 'figures/debconf-screenshots/keystone_4_admin_user_email.png'; "
-"md5=b7f0d34350ccc0aa9ae4e766b7ac80c1"
-msgstr "@@image: 'figures/debconf-screenshots/keystone_4_admin_user_email.png'; md5=b7f0d34350ccc0aa9ae4e766b7ac80c1"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_keystone-install.xml131(None)
-msgid ""
-"@@image: 'figures/debconf-screenshots/keystone_5_admin_user_pass.png'; "
-"md5=e6b32d8d80af90f07a66abc8fb256c84"
-msgstr "@@image: 'figures/debconf-screenshots/keystone_5_admin_user_pass.png'; md5=e6b32d8d80af90f07a66abc8fb256c84"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_keystone-install.xml140(None)
-msgid ""
-"@@image: 'figures/debconf-"
-"screenshots/keystone_6_admin_user_pass_confirm.png'; "
-"md5=1fbf9223e4923c93030d53278d1771cc"
-msgstr "@@image: 'figures/debconf-screenshots/keystone_6_admin_user_pass_confirm.png'; md5=1fbf9223e4923c93030d53278d1771cc"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/section_keystone-install.xml154(None)
-msgid ""
-"@@image: 'figures/debconf-screenshots/keystone_7_register_endpoint.png'; "
-"md5=d24d84133bfee936267e79631a2666e6"
-msgstr "@@image: 'figures/debconf-screenshots/keystone_7_register_endpoint.png'; md5=d24d84133bfee936267e79631a2666e6"
-
-#: ./doc/install-guide/section_keystone-install.xml6(title)
-msgid "Install the Identity Service"
-msgstr "Identity Service のインストール"
-
-#: ./doc/install-guide/section_keystone-install.xml9(para)
-msgid ""
-"Install the OpenStack Identity Service on the controller node, together with"
-" <application>python-keystoneclient</application> (which is a dependency):"
-msgstr "OpenStack Identity Service と <application>python-keystoneclient</application> (依存関係) をコントローラーノードにインストールします。"
-
-#: ./doc/install-guide/section_keystone-install.xml17(para)
-msgid ""
-"Answer to the <systemitem class=\"library\">debconf</systemitem> and "
-"<systemitem class=\"library\">dbconfig-common</systemitem> questions for "
-"setting-up the database."
-msgstr "データベースをセットアップするために <systemitem class=\"library\">debconf</systemitem> と <systemitem class=\"library\">dbconfig-common</systemitem> の質問に答えます。"
-
-#: ./doc/install-guide/section_keystone-install.xml23(para)
-msgid ""
-"The Identity Service uses a database to store information. Specify the "
-"location of the database in the configuration file. In this guide, we use a "
-"MySQL database on the controller node with the username "
-"<literal>keystone</literal>. Replace "
-"<literal><replaceable>KEYSTONE_DBPASS</replaceable></literal> with a "
-"suitable password for the database user."
-msgstr "Identity Service は情報を保存するためにデータベースを使用します。設定ファイルでデータベースの場所を指定します。このガイドでは、コントローラーノードにユーザー名 <literal>keystone</literal> で MySQL データベースを使用します。<literal><replaceable>KEYSTONE_DBPASS</replaceable></literal> をデータベースのユーザーの適切なパスワードで置き換えます。"
-
-#: ./doc/install-guide/section_keystone-install.xml30(replaceable)
-#: ./doc/install-guide/section_keystone-install.xml38(replaceable)
-#: ./doc/install-guide/section_keystone-install.xml57(replaceable)
-#: ./doc/install-guide/section_keystone-install.xml59(replaceable)
-msgid "KEYSTONE_DBPASS"
-msgstr "KEYSTONE_DBPASS"
-
-#: ./doc/install-guide/section_keystone-install.xml31(para)
-msgid ""
-"Edit <filename>/etc/keystone/keystone.conf</filename> and change the "
-"<literal>[database]</literal> section:"
-msgstr "<filename>/etc/keystone/keystone.conf</filename> を編集し、<literal>[database]</literal> セクションを変更します。"
-
-#: ./doc/install-guide/section_keystone-install.xml44(para)
-msgid ""
-"By default, the Ubuntu packages create a SQLite database. Delete the "
-"<filename>keystone.db</filename> file created in the "
-"<filename>/var/lib/keystone/</filename> directory so that it does not get "
-"used by mistake:"
-msgstr "Ubuntu パッケージはデフォルトで SQLite データベースを作成します。誤って使用されないように、<filename>/var/lib/keystone/</filename> ディレクトリに作成された <filename>keystone.db</filename> ファイルを削除します。"
-
-#: ./doc/install-guide/section_keystone-install.xml51(para)
-msgid ""
-"Use the password that you set previously to log in as root. Create a "
-"<literal>keystone</literal> database user:"
-msgstr "root としてログインするために、前に設定したパスワードを使用します。<literal>keystone</literal> データベースユーザーを作成します。"
-
-#: ./doc/install-guide/section_keystone-install.xml63(para)
-msgid "Create the database tables for the Identity Service:"
-msgstr "Image Service 用のデータベーステーブルを作成します。"
-
-#: ./doc/install-guide/section_keystone-install.xml67(para)
-msgid ""
-"Define an authorization token to use as a shared secret between the Identity"
-" Service and other OpenStack services. Respond to the "
-"<package>debconf</package> prompt with the value in the "
-"<code>admin_token</code> directive in the <filename>keystone.conf</filename>"
-" file. Use the <placeholder-1/> command to generate this password."
-msgstr "Identity Service と他の OpenStack サービスの間で共有するシークレットとして使用する認可トークンを定義します。<package>debconf</package> プロンプトで <filename>keystone.conf</filename> ファイルの <code>admin_token</code> ディレクティブにある値を答えます。このパスワードを生成するために <placeholder-1/> コマンドを使用します。"
-
-#: ./doc/install-guide/section_keystone-install.xml83(para)
-msgid ""
-"Later, you can verify that the "
-"<filename>/etc/keystone/keystone.conf</filename> file contains the password "
-"you have set using <package>debconf</package>: <placeholder-1/>"
-msgstr "後から、<filename>/etc/keystone/keystone.conf</filename> ファイルが <package>debconf</package> を使用して設定したパスワードを含んでいることを検証できます。 <placeholder-1/>"
-
-#: ./doc/install-guide/section_keystone-install.xml91(para)
-msgid ""
-"If you omit a password (for example by pressing Enter at the "
-"<package>debconf</package> prompt, or installing Keystone using the Debconf "
-"non-interactive mode) the package generates a random "
-"<literal>ADMIN_TOKEN</literal> value."
-msgstr "パスワードを省略した場合 (例えば、<package>debconf</package> プロンプトに単に Enter を押した場合や debconf の非対話モードを使用して Keystone をインストールした場合)、パッケージがランダムな <literal>ADMIN_TOKEN</literal> 値を生成します。"
-
-#: ./doc/install-guide/section_keystone-install.xml97(para)
-msgid "Respond to the prompts to create an administrative tenant:"
-msgstr "管理プロジェクトを作成するためにプロンプトに答えます。"
-
-#: ./doc/install-guide/section_keystone-install.xml146(para)
-msgid ""
-"If this is the first time you have installed the Identity Service, register "
-"the Identity Service in the service catalog:"
-msgstr "初めて Identity Service をインストールする場合、サービスカタログに Identity Service を登録します。"
-
-#: ./doc/install-guide/section_keystone-install.xml160(para)
-msgid ""
-"Define an authorization token to use as a shared secret between the Identity"
-" Service and other OpenStack services. Use <placeholder-1/> to generate a "
-"random token and store it in the configuration file:"
-msgstr "Identity Service と他の OpenStack サービスの間で共有するシークレットとして使用する認可トークンを定義します。ランダムなトークンを生成し、設定ファイルに保存するために <placeholder-1/> コマンドを使用します。"
-
-#: ./doc/install-guide/section_keystone-install.xml169(para)
-msgid "For SUSE Linux Enterprise use instead as first command:"
-msgstr "SUSE Linux Enterprise の場合、最初のコマンドの代わりとして以下を使用します。"
-
-#: ./doc/install-guide/section_keystone-install.xml172(para)
-msgid ""
-"Edit <filename>/etc/keystone/keystone.conf</filename> and change the "
-"<literal>[DEFAULT]</literal> section, replacing ADMIN_TOKEN with the results"
-" of the command:"
-msgstr "<filename>/etc/keystone/keystone.conf</filename> を編集し、<literal>[DEFAULT]</literal> セクションを変更します。ADMIN_TOKEN をコマンドの結果で置き換えます。"
-
-#: ./doc/install-guide/section_keystone-install.xml182(para)
-msgid ""
-"By default, Keystone uses PKI tokens. Create the signing keys and "
-"certificates and restrict access to the generated data:"
-msgstr "Keystone はデフォルトで PKI トークンを使用します。書名付きキーと証明書を作成し、作成されたデータへのアクセスを制限します。"
-
-#: ./doc/install-guide/section_keystone-install.xml189(para)
-msgid ""
-"Configure the log directory. Edit the "
-"<filename>/etc/keystone/keystone.conf</filename> file and update the "
-"<literal>[DEFAULT]</literal> section:"
-msgstr "ログディレクトリを設定します。<filename>/etc/keystone/keystone.conf</filename> ファイルを編集し、<literal>[DEFAULT]</literal> セクションを更新します。"
-
-#: ./doc/install-guide/section_keystone-install.xml197(para)
-msgid "Restart the Identity Service:"
-msgstr "Identity Service を再起動します。"
-
-#: ./doc/install-guide/section_keystone-install.xml201(para)
-msgid ""
-"Start the Identity Service and enable it to start when the system boots:"
-msgstr "Identity Service を起動し、システム起動時に起動するよう有効化します。"
-
-#: ./doc/install-guide/section_keystone-install.xml207(para)
-msgid ""
-"By default, the Identity Service stores expired tokens in the database "
-"indefinitely. While potentially useful for auditing in production "
-"environments, the accumulation of expired tokens will considerably increase "
-"database size and may decrease service performance, particularly in test "
-"environments with limited resources. We recommend configuring a periodic "
-"task using <systemitem class=\"service\">cron</systemitem> to purge expired "
-"tokens hourly."
-msgstr "Identity Service は標準で、期限切れトークンをデータベースに無期限に保存します。本番環境で監査のために有用であるかもしれませんが、期限切れトークンが蓄積すると、データベースの容量がかなり大きくなり、サービスの性能を劣化させるかもしれません。とくにリソースが限られたテスト環境で顕著かもしれません。期限切れトークンを 1 時間おきに削除するために、<systemitem class=\"service\">cron</systemitem> を使用して定期タスクを設定することを推奨します。"
-
-#: ./doc/install-guide/section_keystone-install.xml217(para)
-msgid ""
-"Run the following command to purge expired tokens every hour and log the "
-"output to <filename>/var/log/keystone/keystone-tokenflush.log</filename>:"
-msgstr "1 時間ごとに期限切れトークンを削除し、出力を <filename>/var/log/keystone/keystone-tokenflush.log</filename> に記録するために、以下のコマンドを実行します。"
-
-#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml6(title)
-msgid "Verify the installation"
-msgstr "インストールの検証"
+"To provide additional reliability and bandwidth to your cluster, you can add"
+" proxy servers. You can set up an additional proxy node the same way that "
+"you set up the first proxy node but with additional configuration steps."
+msgstr "クラスターにさらなる信頼性と帯域を提供するために、プロキシサーバーを追加できます。最初のプロキシノードをセットアップした方法と同じように追加のプロキシノードをセットアップできますが、追加の設定手順があります。"
 
-#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml7(para)
+#: ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml12(para)
 msgid ""
-"You can run these commands from the proxy server or any server that has "
-"access to the Identity Service."
-msgstr "プロキシサーバー、または Identity Service にアクセスできるすべてのサーバーから、これらのコマンドを実行できます。"
+"After you have more than two proxies, you must load balance them; your "
+"storage endpoint (what clients use to connect to your storage) also changes."
+" You can select from different strategies for load balancing. For example, "
+"you could use round-robin DNS, or a software or hardware load balancer (like"
+" pound) in front of the two proxies. You can then point your storage URL to "
+"the load balancer, configure an initial proxy node and complete these steps "
+"to add proxy servers."
+msgstr "複数のプロキシを導入した後、それらを負荷分散する必要があります。ストレージエンドポイント (クライアントがストレージに接続するために使用するもの) も変更します。負荷分散のために複数の方式から選択できます。たとえば、ラウンドロビン DNS を使用できます。また、ソフトウェアやハードウェアの負荷分散装置 (pound など) をプロキシの前で使用できます。ストレージ URL を負荷分散装置に向け、初期プロキシノードを設定し、プロキシサーバーを追加するためのこれらの手順を完了できます。"
 
-#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml11(para)
+#: ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml25(para)
 msgid ""
-"Make sure that your credentials are set up correctly in the <filename>admin-"
-"openrc.sh</filename> file and source it:"
-msgstr "クレデンシャルが <filename>admin-openrc.sh</filename> ファイルに正しくセットアップされていることを確認します。このファイルを以下のように読み込みます。"
+"Update the list of memcache servers in the <filename>/etc/swift/proxy-"
+"server.conf</filename> file for added proxy servers. If you run multiple "
+"memcache servers, use this pattern for the multiple IP:port listings in each"
+" proxy server configuration file:"
+msgstr "追加のプロキシサーバーのために <filename>/etc/swift/proxy-server.conf</filename> ファイルにある memcache サーバーの一覧を更新します。複数の memcache サーバーを実行している場合、各プロキシサーバー設定ファイルで複数の IP:port の一覧に対してこのパターンを使用します。"
 
-#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml15(para)
-msgid "Run the following <placeholder-1/> command:"
-msgstr "以下の <placeholder-1/> コマンドを実行します。"
+#: ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml36(replaceable)
+#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml31(replaceable)
+#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml37(replaceable)
+#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml38(replaceable)
+msgid "PROXY_LOCAL_NET_IP"
+msgstr "PROXY_LOCAL_NET_IP"
 
-#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml27(para)
+#: ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml39(para)
 msgid ""
-"Run the following <placeholder-1/> commands to upload files to a container. "
-"Create the <filename>test.txt</filename> and <filename>test2.txt</filename> "
-"test files locally if needed."
-msgstr "ファイルをコンテナーにアップロードするために、以下の <placeholder-1/> コマンドを実行します。必要に応じてローカルに <filename>test.txt</filename> と <filename>test2.txt</filename> テストファイルを作成します。"
+"Copy ring information to all nodes, including new proxy nodes. Also, ensure "
+"that the ring information gets to all storage nodes."
+msgstr "新しいプロキシノードを含め、すべてのノードにリング情報をコピーします。また、リング情報がすべてのストレージノードに到達していることを確認します。"
 
-#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml34(para)
+#: ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml46(para)
 msgid ""
-"Run the following <placeholder-1/> command to download all files from the "
-"<literal>myfiles</literal> container:"
-msgstr "<literal>myfiles</literal> コンテナーからすべてのファイルをダウンロードするために、以下の <placeholder-1/> コマンドを実行します。"
+"After you sync all nodes, make sure that the admin has keys in "
+"<filename>/etc/swift</filename> and the ownership for the ring file is "
+"correct."
+msgstr "すべてのノードを同期した後、管理者が <filename>/etc/swift</filename> にあるキーを持ち、リングファイルの所有者が正しいことを確認します。"
 
 #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml6(title)
 msgid "Install and configure the proxy node"
@@ -7899,13 +7921,6 @@ msgstr "memcached が標準のインターフェースでローカルの非パ
 msgid "Change it to:"
 msgstr "これを次のように変更します。"
 
-#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml31(replaceable)
-#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml37(replaceable)
-#: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml38(replaceable)
-#: ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml36(replaceable)
-msgid "PROXY_LOCAL_NET_IP"
-msgstr "PROXY_LOCAL_NET_IP"
-
 #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml34(para)
 msgid ""
 "Modify memcached to listen on the default interface on a local, non-public "
@@ -8042,233 +8057,6 @@ msgid ""
 "Start the Proxy service and configure it to start when the system boots:"
 msgstr "プロキシサービスを起動し、システム起動時に起動するよう設定します。"
 
-#: ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml6(title)
-msgid "Add another proxy server"
-msgstr "プロキシサーバーの追加"
-
-#: ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml7(para)
-msgid ""
-"To provide additional reliability and bandwidth to your cluster, you can add"
-" proxy servers. You can set up an additional proxy node the same way that "
-"you set up the first proxy node but with additional configuration steps."
-msgstr "クラスターにさらなる信頼性と帯域を提供するために、プロキシサーバーを追加できます。最初のプロキシノードをセットアップした方法と同じように追加のプロキシノードをセットアップできますが、追加の設定手順があります。"
-
-#: ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml12(para)
-msgid ""
-"After you have more than two proxies, you must load balance them; your "
-"storage endpoint (what clients use to connect to your storage) also changes."
-" You can select from different strategies for load balancing. For example, "
-"you could use round-robin DNS, or a software or hardware load balancer (like"
-" pound) in front of the two proxies. You can then point your storage URL to "
-"the load balancer, configure an initial proxy node and complete these steps "
-"to add proxy servers."
-msgstr "複数のプロキシを導入した後、それらを負荷分散する必要があります。ストレージエンドポイント (クライアントがストレージに接続するために使用するもの) も変更します。負荷分散のために複数の方式から選択できます。たとえば、ラウンドロビン DNS を使用できます。また、ソフトウェアやハードウェアの負荷分散装置 (pound など) をプロキシの前で使用できます。ストレージ URL を負荷分散装置に向け、初期プロキシノードを設定し、プロキシサーバーを追加するためのこれらの手順を完了できます。"
-
-#: ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml25(para)
-msgid ""
-"Update the list of memcache servers in the <filename>/etc/swift/proxy-"
-"server.conf</filename> file for added proxy servers. If you run multiple "
-"memcache servers, use this pattern for the multiple IP:port listings in each"
-" proxy server configuration file:"
-msgstr "追加のプロキシサーバーのために <filename>/etc/swift/proxy-server.conf</filename> ファイルにある memcache サーバーの一覧を更新します。複数の memcache サーバーを実行している場合、各プロキシサーバー設定ファイルで複数の IP:port の一覧に対してこのパターンを使用します。"
-
-#: ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml39(para)
-msgid ""
-"Copy ring information to all nodes, including new proxy nodes. Also, ensure "
-"that the ring information gets to all storage nodes."
-msgstr "新しいプロキシノードを含め、すべてのノードにリング情報をコピーします。また、リング情報がすべてのストレージノードに到達していることを確認します。"
-
-#: ./doc/install-guide/object-storage/section_object-storage-adding-proxy-server.xml46(para)
-msgid ""
-"After you sync all nodes, make sure that the admin has keys in "
-"<filename>/etc/swift</filename> and the ownership for the ring file is "
-"correct."
-msgstr "すべてのノードを同期した後、管理者が <filename>/etc/swift</filename> にあるキーを持ち、リングファイルの所有者が正しいことを確認します。"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml35(None)
-msgid ""
-"@@image: '../figures/networking-interactions-swift.png'; "
-"md5=2190892da42f344e407b4cef71b8f3cf"
-msgstr "@@image: '../figures/networking-interactions-swift.png'; md5=2190892da42f344e407b4cef71b8f3cf"
-
-#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml6(title)
-msgid "Plan networking for Object Storage"
-msgstr "Object Storage 用ネットワークの計画"
-
-#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml7(para)
-msgid ""
-"For both conserving network resources and ensuring that network "
-"administrators understand the needs for networks and public IP addresses for"
-" providing access to the APIs and storage network as necessary, this section"
-" offers recommendations and required minimum sizes. Throughput of at least "
-"1000 Mbps is suggested."
-msgstr "ネットワークリソースの節約のため、およびネットワーク管理者が必要に応じて API とストレージのネットワークへのアクセスを提供するためのネットワークとパブリック IP アドレスの必要性について確実に理解するために、このセクションは推奨量と必須の最小量を提供します。少なくとも 1000 Mbps のスループットが推奨されます。"
-
-#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml15(para)
-msgid "A mandatory public network. Connects to the proxy server."
-msgstr "必須のパブリックネットワーク。プロキシサーバーに接続します。"
-
-#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml19(para)
-msgid ""
-"A mandatory storage network. Not accessible from outside the cluster. All "
-"nodes connect to this network."
-msgstr "必須のストレージネットワーク。クラスターの外部からアクセスできません。すべてのノードがこのネットワークに接続されます。"
-
-#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml23(para)
-msgid ""
-"An optional replication network. Not accessible from outside the cluster. "
-"Dedicated to replication traffic among storage nodes. Must be configured in "
-"the Ring."
-msgstr "オプションの複製ネットワーク。クラスターの外部からアクセスできません。ストレージノード間の複製通信専用です。リングで設定される必要があります。"
-
-#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml13(para)
-msgid "This guide describes the following networks:<placeholder-1/>"
-msgstr "このガイドは以下のネットワークを記載します。 <placeholder-1/>"
-
-#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml28(para)
-msgid ""
-"This figure shows the basic architecture for the public network, the storage"
-" network, and the optional replication network."
-msgstr "この図は、パブリックネットワーク、ストレージネットワーク、オプションのレプリケーションネットワークの基本的なアーキテクチャを表します。"
-
-#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml38(para)
-msgid ""
-"By default, all of the OpenStack Object Storage services, as well as the "
-"rsync daemon on the storage nodes, are configured to listen on their "
-"<literal>STORAGE_LOCAL_NET</literal> IP addresses."
-msgstr "すべての OpenStack Object Storage サービスとストレージノードの rsync デーモンは、デフォルトで <literal>STORAGE_LOCAL_NET</literal> IP アドレスをリッスンするよう設定されます。"
-
-#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml42(para)
-msgid ""
-"If you configure a replication network in the Ring, the Account, Container "
-"and Object servers listen on both the <literal>STORAGE_LOCAL_NET</literal> "
-"and <literal>STORAGE_REPLICATION_NET</literal> IP addresses. The rsync "
-"daemon only listens on the <literal>STORAGE_REPLICATION_NET</literal> IP "
-"address."
-msgstr "リングで複製ネットワークを設定する場合、アカウントサーバー、コンテナーサーバー、オブジェクトサーバーが <literal>STORAGE_LOCAL_NET</literal> と <literal>STORAGE_REPLICATION_NET</literal> の IP アドレスをリッスンします。rsync デーモンは <literal>STORAGE_REPLICATION_NET</literal> IP アドレスのみをリッスンします。"
-
-#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml50(term)
-msgid "Public Network (Publicly routable IP range)"
-msgstr "パブリックネットワーク (パブリックにルーティング可能な IP 範囲)"
-
-#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml52(para)
-msgid ""
-"Provides public IP accessibility to the API endpoints within the cloud "
-"infrastructure."
-msgstr "クラウドインフラストラクチャーの中で API エンドポイントにアクセス可能なパブリック IP を提供します。"
-
-#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml54(para)
-msgid "Minimum size: one IP address for each proxy server."
-msgstr "最小量: 各プロキシサーバーに対して IP アドレス 1 つ。"
-
-#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml59(term)
-msgid "Storage Network (RFC1918 IP Range, not publicly routable)"
-msgstr "ストレージネットワーク (RFC1918 IP 範囲、パブリックにルーティングできません)"
-
-#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml62(para)
-msgid ""
-"Manages all inter-server communications within the Object Storage "
-"infrastructure."
-msgstr "Object Storage インフラストラクチャーの中ですべてのサーバー間通信を管理します。"
-
-#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml64(para)
-msgid "Minimum size: one IP address for each storage node and proxy server."
-msgstr "最小量: 各ストレージノードとプロキシサーバーに対して IP アドレス 1 つ。"
-
-#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml66(para)
-msgid ""
-"Recommended size: as above, with room for expansion to the largest your "
-"cluster size. For example, 255 or CIDR /24."
-msgstr "推奨量: 上のとおり、クラスターの最大量に拡張するための余地を持ちます。例えば、255 や CIDR /24 です。"
-
-#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml72(term)
-msgid "Replication Network (RFC1918 IP Range, not publicly routable)"
-msgstr "複製ネットワーク (RFC1918 IP 範囲、パブリックにルーティングできません)"
-
-#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml75(para)
-msgid ""
-"Manages replication-related communications among storage servers within the "
-"Object Storage infrastructure."
-msgstr "Object Storage インフラストラクチャーの中でストレージサーバー間の複製関連の通信を管理します。"
-
-#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml77(para)
-msgid "Recommended size: as for <literal>STORAGE_LOCAL_NET</literal>."
-msgstr "推奨量: <literal>STORAGE_LOCAL_NET</literal> に限ります。"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml52(None)
-msgid ""
-"@@image: '../figures/swift_install_arch.png'; "
-"md5=bbda527d20235d54a95eb29279ba2680"
-msgstr "@@image: '../figures/swift_install_arch.png'; md5=bbda527d20235d54a95eb29279ba2680"
-
-#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml6(title)
-msgid "Example of Object Storage installation architecture"
-msgstr "Object Storage インストールアーキテクチャー例"
-
-#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml9(para)
-msgid ""
-"Node: A host machine that runs one or more OpenStack Object Storage "
-"services."
-msgstr "ノード。1 つ以上の OpenStack Object Storage サービスを実行するホストマシン。"
-
-#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml13(para)
-msgid "Proxy node: Runs proxy services."
-msgstr "プロキシノード。プロキシサービスを実行します。"
-
-#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml16(para)
-msgid ""
-"Storage node: Runs account, container, and object services. Contains the "
-"SQLite databases."
-msgstr "ストレージノード。アカウントサービス、コンテナーサービス、オブジェクトサービスを実行します。SQLite データベースを持ちます。"
-
-#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml20(para)
-msgid ""
-"Ring: A set of mappings between OpenStack Object Storage data to physical "
-"devices."
-msgstr "リング。OpenStack Object Storage のデータと物理デバイスの一組のマッピング。"
-
-#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml24(para)
-msgid ""
-"Replica: A copy of an object. By default, three copies are maintained in the"
-" cluster."
-msgstr "レプリカ。オブジェクトのコピー。デフォルトで 3 つのコピーがクラスターに維持されます。"
-
-#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml28(para)
-msgid ""
-"Zone: A logically separate section of the cluster, related to independent "
-"failure characteristics."
-msgstr "ゾーン。独立した障害特性に関連した、クラスターの論理的な分離部分。"
-
-#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml32(para)
-msgid ""
-"Region (optional): A logically separate section of the cluster, representing"
-" distinct physical locations such as cities or countries. Similar to zones "
-"but representing physical locations of portions of the cluster rather than "
-"logical segments."
-msgstr "リージョン (オプション): 都市や国のような物理位置を区別して表現する、クラスターの論理的に分割されたセクション。ゾーンと似ていますが、論理的な区切りではなく、クラスターのメンバーの物理的な位置を表現します。"
-
-#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml39(para)
-msgid ""
-"To increase reliability and performance, you can add additional proxy "
-"servers."
-msgstr "信頼性とパフォーマンスを向上させるために、追加のプロキシノードを追加できます。"
-
-#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml41(para)
-msgid ""
-"This document describes each storage node as a separate zone in the ring. At"
-" a minimum, five zones are recommended. A zone is a group of nodes that are "
-"as isolated as possible from other nodes (separate servers, network, power, "
-"even geography). The ring guarantees that every replica is stored in a "
-"separate zone. This diagram shows one possible configuration for a minimal "
-"installation:"
-msgstr "このドキュメントは、リングで別々のゾーンとして各ストレージノードについて記載します。最低限、5 つのゾーンが推奨されます。ゾーンは他のノードから独立したノード (別々のサーバー、ネットワーク、電力、設置場所さえ) のグループです。リングはすべての複製が別々のゾーンに保存されていることを保証します。この図は最小インストールに対する設定の可能性の 1 つを示します。"
-
 #: ./doc/install-guide/object-storage/section_object-storage-install.xml6(title)
 msgid "Install Object Storage"
 msgstr "Object Storage のインストール"
@@ -8393,6 +8181,152 @@ msgid ""
 "Identity Service for the common authentication piece."
 msgstr "次にストレージノードとプロキシノードをセットアップします。この例では、共通の認証部品として Identity Service を使用します。"
 
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml35(None)
+msgid ""
+"@@image: '../figures/networking-interactions-swift.png'; "
+"md5=2190892da42f344e407b4cef71b8f3cf"
+msgstr "@@image: '../figures/networking-interactions-swift.png'; md5=2190892da42f344e407b4cef71b8f3cf"
+
+#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml6(title)
+msgid "Plan networking for Object Storage"
+msgstr "Object Storage 用ネットワークの計画"
+
+#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml7(para)
+msgid ""
+"For both conserving network resources and ensuring that network "
+"administrators understand the needs for networks and public IP addresses for"
+" providing access to the APIs and storage network as necessary, this section"
+" offers recommendations and required minimum sizes. Throughput of at least "
+"1000 Mbps is suggested."
+msgstr "ネットワークリソースの節約のため、およびネットワーク管理者が必要に応じて API とストレージのネットワークへのアクセスを提供するためのネットワークとパブリック IP アドレスの必要性について確実に理解するために、このセクションは推奨量と必須の最小量を提供します。少なくとも 1000 Mbps のスループットが推奨されます。"
+
+#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml15(para)
+msgid "A mandatory public network. Connects to the proxy server."
+msgstr "必須のパブリックネットワーク。プロキシサーバーに接続します。"
+
+#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml19(para)
+msgid ""
+"A mandatory storage network. Not accessible from outside the cluster. All "
+"nodes connect to this network."
+msgstr "必須のストレージネットワーク。クラスターの外部からアクセスできません。すべてのノードがこのネットワークに接続されます。"
+
+#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml23(para)
+msgid ""
+"An optional replication network. Not accessible from outside the cluster. "
+"Dedicated to replication traffic among storage nodes. Must be configured in "
+"the Ring."
+msgstr "オプションの複製ネットワーク。クラスターの外部からアクセスできません。ストレージノード間の複製通信専用です。リングで設定される必要があります。"
+
+#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml13(para)
+msgid "This guide describes the following networks:<placeholder-1/>"
+msgstr "このガイドは以下のネットワークを記載します。 <placeholder-1/>"
+
+#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml28(para)
+msgid ""
+"This figure shows the basic architecture for the public network, the storage"
+" network, and the optional replication network."
+msgstr "この図は、パブリックネットワーク、ストレージネットワーク、オプションのレプリケーションネットワークの基本的なアーキテクチャを表します。"
+
+#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml38(para)
+msgid ""
+"By default, all of the OpenStack Object Storage services, as well as the "
+"rsync daemon on the storage nodes, are configured to listen on their "
+"<literal>STORAGE_LOCAL_NET</literal> IP addresses."
+msgstr "すべての OpenStack Object Storage サービスとストレージノードの rsync デーモンは、デフォルトで <literal>STORAGE_LOCAL_NET</literal> IP アドレスをリッスンするよう設定されます。"
+
+#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml42(para)
+msgid ""
+"If you configure a replication network in the Ring, the Account, Container "
+"and Object servers listen on both the <literal>STORAGE_LOCAL_NET</literal> "
+"and <literal>STORAGE_REPLICATION_NET</literal> IP addresses. The rsync "
+"daemon only listens on the <literal>STORAGE_REPLICATION_NET</literal> IP "
+"address."
+msgstr "リングで複製ネットワークを設定する場合、アカウントサーバー、コンテナーサーバー、オブジェクトサーバーが <literal>STORAGE_LOCAL_NET</literal> と <literal>STORAGE_REPLICATION_NET</literal> の IP アドレスをリッスンします。rsync デーモンは <literal>STORAGE_REPLICATION_NET</literal> IP アドレスのみをリッスンします。"
+
+#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml50(term)
+msgid "Public Network (Publicly routable IP range)"
+msgstr "パブリックネットワーク (パブリックにルーティング可能な IP 範囲)"
+
+#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml52(para)
+msgid ""
+"Provides public IP accessibility to the API endpoints within the cloud "
+"infrastructure."
+msgstr "クラウドインフラストラクチャーの中で API エンドポイントにアクセス可能なパブリック IP を提供します。"
+
+#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml54(para)
+msgid "Minimum size: one IP address for each proxy server."
+msgstr "最小量: 各プロキシサーバーに対して IP アドレス 1 つ。"
+
+#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml59(term)
+msgid "Storage Network (RFC1918 IP Range, not publicly routable)"
+msgstr "ストレージネットワーク (RFC1918 IP 範囲、パブリックにルーティングできません)"
+
+#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml62(para)
+msgid ""
+"Manages all inter-server communications within the Object Storage "
+"infrastructure."
+msgstr "Object Storage インフラストラクチャーの中ですべてのサーバー間通信を管理します。"
+
+#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml64(para)
+msgid "Minimum size: one IP address for each storage node and proxy server."
+msgstr "最小量: 各ストレージノードとプロキシサーバーに対して IP アドレス 1 つ。"
+
+#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml66(para)
+msgid ""
+"Recommended size: as above, with room for expansion to the largest your "
+"cluster size. For example, 255 or CIDR /24."
+msgstr "推奨量: 上のとおり、クラスターの最大量に拡張するための余地を持ちます。例えば、255 や CIDR /24 です。"
+
+#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml72(term)
+msgid "Replication Network (RFC1918 IP Range, not publicly routable)"
+msgstr "複製ネットワーク (RFC1918 IP 範囲、パブリックにルーティングできません)"
+
+#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml75(para)
+msgid ""
+"Manages replication-related communications among storage servers within the "
+"Object Storage infrastructure."
+msgstr "Object Storage インフラストラクチャーの中でストレージサーバー間の複製関連の通信を管理します。"
+
+#: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml77(para)
+msgid "Recommended size: as for <literal>STORAGE_LOCAL_NET</literal>."
+msgstr "推奨量: <literal>STORAGE_LOCAL_NET</literal> に限ります。"
+
+#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml6(title)
+msgid "Verify the installation"
+msgstr "インストールの検証"
+
+#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml7(para)
+msgid ""
+"You can run these commands from the proxy server or any server that has "
+"access to the Identity Service."
+msgstr "プロキシサーバー、または Identity Service にアクセスできるすべてのサーバーから、これらのコマンドを実行できます。"
+
+#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml11(para)
+msgid ""
+"Make sure that your credentials are set up correctly in the <filename>admin-"
+"openrc.sh</filename> file and source it:"
+msgstr "クレデンシャルが <filename>admin-openrc.sh</filename> ファイルに正しくセットアップされていることを確認します。このファイルを以下のように読み込みます。"
+
+#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml15(para)
+msgid "Run the following <placeholder-1/> command:"
+msgstr "以下の <placeholder-1/> コマンドを実行します。"
+
+#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml27(para)
+msgid ""
+"Run the following <placeholder-1/> commands to upload files to a container. "
+"Create the <filename>test.txt</filename> and <filename>test2.txt</filename> "
+"test files locally if needed."
+msgstr "ファイルをコンテナーにアップロードするために、以下の <placeholder-1/> コマンドを実行します。必要に応じてローカルに <filename>test.txt</filename> と <filename>test2.txt</filename> テストファイルを作成します。"
+
+#: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml34(para)
+msgid ""
+"Run the following <placeholder-1/> command to download all files from the "
+"<literal>myfiles</literal> container:"
+msgstr "<literal>myfiles</literal> コンテナーからすべてのファイルをダウンロードするために、以下の <placeholder-1/> コマンドを実行します。"
+
 #: ./doc/install-guide/object-storage/section_start-storage-node-services.xml7(title)
 msgid "Start services on the storage nodes"
 msgstr "ストレージノードでのサービスの起動"
@@ -8617,7 +8551,78 @@ msgid ""
 "configure the sudoers file to enable all the permissions."
 msgstr "<emphasis role=\"bold\">権限</emphasis>: OpenStack Object Storage を root としてインストールできます。または、すべての権限を有効化するよう sudoers ファイルを設定する場合、sudo 権限を持つユーザーとしてインストールできます。"
 
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml52(None)
+msgid ""
+"@@image: '../figures/swift_install_arch.png'; "
+"md5=bbda527d20235d54a95eb29279ba2680"
+msgstr "@@image: '../figures/swift_install_arch.png'; md5=bbda527d20235d54a95eb29279ba2680"
+
+#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml6(title)
+msgid "Example of Object Storage installation architecture"
+msgstr "Object Storage インストールアーキテクチャー例"
+
+#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml9(para)
+msgid ""
+"Node: A host machine that runs one or more OpenStack Object Storage "
+"services."
+msgstr "ノード。1 つ以上の OpenStack Object Storage サービスを実行するホストマシン。"
+
+#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml13(para)
+msgid "Proxy node: Runs proxy services."
+msgstr "プロキシノード。プロキシサービスを実行します。"
+
+#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml16(para)
+msgid ""
+"Storage node: Runs account, container, and object services. Contains the "
+"SQLite databases."
+msgstr "ストレージノード。アカウントサービス、コンテナーサービス、オブジェクトサービスを実行します。SQLite データベースを持ちます。"
+
+#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml20(para)
+msgid ""
+"Ring: A set of mappings between OpenStack Object Storage data to physical "
+"devices."
+msgstr "リング。OpenStack Object Storage のデータと物理デバイスの一組のマッピング。"
+
+#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml24(para)
+msgid ""
+"Replica: A copy of an object. By default, three copies are maintained in the"
+" cluster."
+msgstr "レプリカ。オブジェクトのコピー。デフォルトで 3 つのコピーがクラスターに維持されます。"
+
+#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml28(para)
+msgid ""
+"Zone: A logically separate section of the cluster, related to independent "
+"failure characteristics."
+msgstr "ゾーン。独立した障害特性に関連した、クラスターの論理的な分離部分。"
+
+#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml32(para)
+msgid ""
+"Region (optional): A logically separate section of the cluster, representing"
+" distinct physical locations such as cities or countries. Similar to zones "
+"but representing physical locations of portions of the cluster rather than "
+"logical segments."
+msgstr "リージョン (オプション): 都市や国のような物理位置を区別して表現する、クラスターの論理的に分割されたセクション。ゾーンと似ていますが、論理的な区切りではなく、クラスターのメンバーの物理的な位置を表現します。"
+
+#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml39(para)
+msgid ""
+"To increase reliability and performance, you can add additional proxy "
+"servers."
+msgstr "信頼性とパフォーマンスを向上させるために、追加のプロキシノードを追加できます。"
+
+#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml41(para)
+msgid ""
+"This document describes each storage node as a separate zone in the ring. At"
+" a minimum, five zones are recommended. A zone is a group of nodes that are "
+"as isolated as possible from other nodes (separate servers, network, power, "
+"even geography). The ring guarantees that every replica is stored in a "
+"separate zone. This diagram shows one possible configuration for a minimal "
+"installation:"
+msgstr "このドキュメントは、リングで別々のゾーンとして各ストレージノードについて記載します。最低限、5 つのゾーンが推奨されます。ゾーンは他のノードから独立したノード (別々のサーバー、ネットワーク、電力、設置場所さえ) のグループです。リングはすべての複製が別々のゾーンに保存されていることを保証します。この図は最小インストールに対する設定の可能性の 1 つを示します。"
+
 #. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
-#: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml0(None)
+#: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml0(None)
 msgid "translator-credits"
 msgstr "Akihiro MOTOKI <amotoki@gmail.com>, 2013\nthatsdone <masanori.itoh@gmail.com>, 2013\ndoki701 <tokidokidokidoki@gmail.com>, 2013\nTomoyuki KATO <tomo@dream.daynight.jp>, 2012-2014"
diff --git a/doc/security-guide/locale/ja.po b/doc/security-guide/locale/ja.po
index 2d9d9d9704..df2cace4de 100644
--- a/doc/security-guide/locale/ja.po
+++ b/doc/security-guide/locale/ja.po
@@ -12,8 +12,8 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: OpenStack Manuals\n"
-"POT-Creation-Date: 2014-05-29 03:47+0000\n"
-"PO-Revision-Date: 2014-05-28 16:07+0000\n"
+"POT-Creation-Date: 2014-06-03 02:30+0000\n"
+"PO-Revision-Date: 2014-05-30 08:32+0000\n"
 "Last-Translator: Tomoyuki KATO <tomo@dream.daynight.jp>\n"
 "Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n"
 "MIME-Version: 1.0\n"
@@ -22,6 +22,1494 @@ msgstr ""
 "Language: ja\n"
 "Plural-Forms: nplurals=1; plural=0;\n"
 
+#: ./doc/security-guide/ch020_ssl-everywhere.xml8(title)
+msgid "SSL proxies and HTTP services"
+msgstr "SSLプロキシとHTTPサービス"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml9(para)
+msgid ""
+"OpenStack endpoints are HTTP services providing APIs to both end-users on "
+"public networks and to other OpenStack services within the same deployment "
+"operating over the management network. It is highly recommended these "
+"requests, both those internal and external, operate over SSL."
+msgstr "OpenStack エンドポイントは、パブリックネットワーク上のエンドユーザーと、管理ネットワークを介して操作する同じデプロイ中の他 OpenStack サービスの両方に対して API を提供する HTTP サービスです。これらのリクエスト（内部と外部の両方）を SSL 上で操作する事を強く推奨します。"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml10(para)
+msgid ""
+"In order for API requests to be encrypted by SSL it's necessary to position "
+"the API services behind a proxy that will establish and terminate SSL "
+"sessions. The following table offers a non-exhaustive list of software "
+"services that can proxy SSL traffic for API requests:"
+msgstr "API リクエストを SSL で暗号化する為に、APIサービスはSSLセッションを確立・切断するプロキシの後ろに位置する必要があります。下記の表はAPIリクエスト用にSSLトラフィックをプロキシ可能なソフトウェアサービスの（あまり厳密でない）一覧を示しています。"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml12(link)
+msgid "Pound"
+msgstr "Pound"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml15(link)
+#: ./doc/security-guide/ch020_ssl-everywhere.xml153(title)
+msgid "Stud"
+msgstr "Stud"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml18(link)
+#: ./doc/security-guide/ch020_ssl-everywhere.xml191(title)
+msgid "nginx"
+msgstr "nginx"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml21(link)
+msgid "Apache httpd"
+msgstr "Apache httpd"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml24(para)
+msgid "Hardware appliance SSL acceleration proxies"
+msgstr "ハードウェアアプライアンス SSLアクセラレーションプロキシ"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml27(para)
+msgid ""
+"It is important to be mindful of the size of requests that will be processed"
+" by any chosen SSL proxy."
+msgstr "選択したSSLプロキシによって処理されるリクエストのサイズを気にする事は重要です。"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml29(title)
+msgid "Examples"
+msgstr "例"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml30(para)
+msgid ""
+"Below we provide some sample recommended configuration settings for enabling"
+" SSL in some of the more popular web servers/SSL terminators. Note that we "
+"have SSL v3 enabled in some of these examples as this will be required in "
+"many deployments for client compatibility."
+msgstr "以下に、幾つかの主な有名 Web サーバ／SSL 終端でSSLを有効にする為の幾つかの推奨設定例を示します。クライアント互換性の為に多くのデプロイで必要になる筈なので、幾つかの例ではSSL v3 が有効になっている点に注意して下さい。"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml31(para)
+msgid ""
+"Before we delve into the configurations, we briefly discuss the ciphers' "
+"configuration element and its format. A more exhaustive treatment on "
+"available ciphers and the OpenSSL cipher list format can be found at: <link "
+"href=\"https://www.openssl.org/docs/apps/ciphers.html\">ciphers</link>."
+msgstr "設定を掘り下げる前に、暗号の設定要素とその形式について簡単に議論します。利用可能な暗号におけるより包括的な使い方、および OpenSSL 暗号一覧形式が <link href=\"https://www.openssl.org/docs/apps/ciphers.html\">ciphers</link> にあります。"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml35(para)
+msgid "or"
+msgstr "または"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml39(para)
+msgid ""
+"Cipher string options are separated by \":\", while \"!\" provides negation "
+"of the immediately following element. Element order indicates preference "
+"unless overridden by qualifiers such as HIGH. Let us take a closer look at "
+"the elements in the above sample strings."
+msgstr "暗号オプションの文字列は「:」で区切られます。「!」は直後の要素の否定を意味します。要素の順番は、HIGH のような修飾語句により上書きされない限り、優先度を意味します。上のサンプル文字列の要素をもう少し具体的に見ていきましょう。"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml42(code)
+msgid "kEECDH:kEDH"
+msgstr "kEECDH:kEDH"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml44(para)
+msgid ""
+"Ephemeral Elliptic Curve Diffie-Hellman (abbreviated as EECDH and ECDHE)."
+msgstr "楕円曲線ディフィー・ヘルマン (EECDH や ECDHE と略す)"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml45(para)
+msgid ""
+"Ephemeral Diffie-Hellman (abbreviated either as EDH or DHE) uses prime field"
+" groups."
+msgstr "一時ディフィー・ヘルマン (EDH や DHE と略す) は素体グループを使用します。"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml46(para)
+msgid ""
+"Both approaches provide <link "
+"href=\"http://en.wikipedia.org/wiki/Forward_secrecy\">Perfect Forward "
+"Secrecy (PFS)</link>."
+msgstr "どちらの方法も <link href=\"http://en.wikipedia.org/wiki/Forward_secrecy\">Perfect Forward Secrecy (PFS)</link> を提供します。"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml47(para)
+msgid ""
+"Ephemeral Elliptic Curves require the server to be configured with a named "
+"curve, and provide better security than prime field groups and at lower "
+"computational cost. However, prime field groups are more widely implemented,"
+" and thus typically both are included in list."
+msgstr "一時楕円曲線はサーバーが名前付き曲線を用いて設定されている必要があります。素体グループよりセキュリティが高く、計算コストが低いです。しかしながら、素体グループはより幅広く実装されているので、一般的にどちらも一覧に含まれます。"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml51(code)
+msgid "kRSA"
+msgstr "kRSA"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml53(para)
+msgid ""
+"Cipher suites using the <link "
+"href=\"http://en.wikipedia.org/wiki/RSA_%28cryptosystem%29\">RSA</link> "
+"exchange, authentication or either respectively."
+msgstr "<link href=\"http://en.wikipedia.org/wiki/RSA_%28cryptosystem%29\">RSA</link> の鍵交換、認証、またはその両方を使用する暗号スイート。"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml57(code)
+msgid "HIGH"
+msgstr "HIGH"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml59(para)
+msgid ""
+"Selects highest possible security cipher in the negotiation phase. These "
+"typically have keys of length 128 bits or longer."
+msgstr "ネゴシエーション段階で利用可能な最高のセキュリティ暗号を選択します。これらは一般的に 128 ビット以上の鍵を持ちます。"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml63(code)
+msgid "!RC4"
+msgstr "!RC4"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml65(para)
+msgid ""
+"No RC4. RC4 has flaws in the context of TLS/SSL V3. See <link "
+"href=\"cr.yp.to/streamciphers/rc4biases-20130708.pdf\"> On the Security of "
+"RC4 in TLS and WPA</link>."
+msgstr "RC4 使用不可。RC4 は TLS/SSL V3 の文脈で欠陥があります。<link href=\"cr.yp.to/streamciphers/rc4biases-20130708.pdf\"> On the Security of RC4 in TLS and WPA</link> を参照してください。"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml69(code)
+msgid "!MD5"
+msgstr "!MD5"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml71(para)
+msgid ""
+"No MD5. MD5 is not collision resistant, and thus not acceptable for Message "
+"Authentication Codes (MAC) or signatures."
+msgstr "MD5 使用不可。MD5 は衝突耐性がないため、メッセージ認証コード (MAC) や署名に利用できません。"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml75(code)
+msgid "!aNULL:!eNULL"
+msgstr "!aNULL:!eNULL"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml77(para)
+msgid "Disallows clear text"
+msgstr "平文を禁止します。"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml81(code)
+msgid "!EXP"
+msgstr "!EXP"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml83(para)
+msgid ""
+"Disallows export encryption algorithms, which by design tend to were weak, "
+"typically using 40 and 56 bit keys."
+msgstr "export 暗号アルゴリズムを無効化します。これは、設計として弱く、一般的に 40 ビットか 56 ビットの鍵を使用しています。"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml84(para)
+msgid ""
+"US Export restrictions on cryptography systems have been lifted and no "
+"longer need to be supported."
+msgstr "暗号システムにおけるアメリカ輸出規制を解かれていて、もはやサポートする必要がありません。"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml88(code)
+msgid "!LOW:!MEDIUM"
+msgstr "!LOW:!MEDIUM"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml90(para)
+msgid ""
+"Disallows low (keys 56 or 64 bits long) and medium (128 bit long keys) "
+"ciphers because of their vulnerability to brute force attacks (example "
+"2-DES). This constraint leaves acceptable Triple Data Encryption Standard "
+"(Triple DES) also known as Triple Data Encryption Algorithm (TDEA) and the "
+"Advanced Encryption Standard (AES), each of which has keys greater than "
+"equal to 128 bits and thus more secure."
+msgstr "総当たり攻撃への脆弱性のため、低度 (56/64 ビット長の鍵) と中程度 (128 ビット長の鍵) の暗号を無効化します (例: 2-DES)。この制限は、Triple Data Encryption Algorithm (TDEA) としても知られている Triple Data Encryption Standard (3-DES)、Advanced Encryption Standard (AES) を利用できる状態にします。このどちらも 128 ビット以上の鍵を持つため、よりセキュアです。"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml94(code)
+msgid "Protocols"
+msgstr "プロトコル"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml96(para)
+msgid ""
+"Protocols are enabled/disabled through SSL_CTX_set_options. We recommend "
+"disabling SSLv2 and enabling TLS or SSLv3 (which was standardised as TLS "
+"with a few changes)."
+msgstr "プロトコルは SSL_CTX_set_options により有効化、無効化できます。SSLv2 を無効化し、TLS や SSLv3 (いくつか変更をして TLS として標準化されました) を有効化することを推奨します。"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml101(title)
+msgid "Pound - with AES-NI acceleration"
+msgstr "Pound（AES-NI アクセラレーション付き）"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml154(para)
+msgid ""
+"This stud example enables SSL v3 for client compatibility. The ciphers line "
+"can be tweaked based on your needs, however this is a reasonable starting "
+"place."
+msgstr "この Stud の例は、クライアント互換性の為に SSL v3 を有効にしています。ciphers 行は必要に応じていじる事が出来ますが、しかしながらこの例の値は合理的な初期値です。"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml192(para)
+msgid ""
+"This nginx example requires TLS v1.1 or v1.2 for maximum security. The "
+"ssl_ciphers line can be tweaked based on your needs, however this is a "
+"reasonable starting place."
+msgstr "この nginx の例は、セキュリティを最大化する為に TLS v1.1 又は v1.2 を必要とします。ssl_ciphers 行は必要に応じて変更可能ですが、しかしながらこの例の値は合理的な初期値です。"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml208(title)
+msgid "Apache"
+msgstr "Apache"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml233(para)
+msgid ""
+"Compute API SSL endpoint in Apache, which you must pair with a short WSGI "
+"script."
+msgstr "Apache 中の Compute API SSL エンドポイント (短い WSGI スクリプトと組み合わせる必要あり)"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml257(title)
+msgid "HTTP strict transport security"
+msgstr "HTTP Strict Transport Security"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml258(para)
+msgid ""
+"We recommend that all production deployments use HSTS. This header prevents "
+"browsers from making insecure connections after they have made a single "
+"secure one. If you have deployed your HTTP services on a public or an "
+"untrusted domain, HSTS is especially important. To enable HSTS, configure "
+"your web server to send a header like this with all requests:"
+msgstr "全ての製品で HSTS を使用する事を推奨します。このヘッダは、ブラウザが単一のセキュアな接続を確立した後に、セキュアでない接続を確立する事を防止します。パブリック上あるいは信用出来ないドメイン上の HTTP サービスをデプロイした場合、HSTS は特に重要です。HSTS を有効にするためには、全リクエストでこのようなヘッダを送信するよう Web サーバを設定します。"
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml260(para)
+msgid ""
+"Start with a short timeout of 1 day during testing, and raise it to one year"
+" after testing has shown that you haven't introduced problems for users. "
+"Note that once this header is set to a large timeout, it is (by design) very"
+" difficult to disable."
+msgstr "テストでは1日の短いタイムアウトで始め、テストでユーザーに問題が発生しなかった事を確認した後で設定を１年まで増やします。一旦このヘッダーに大きなタイムアウトを設定してしまうと、無効化する事は (設計上) 非常に困難です。"
+
+#: ./doc/security-guide/bk-openstack-sec-guide.xml6(title)
+msgid "OpenStack Security Guide"
+msgstr "OpenStack セキュリティガイド"
+
+#: ./doc/security-guide/bk-openstack-sec-guide.xml14(orgname)
+#: ./doc/security-guide/bk-openstack-sec-guide.xml19(holder)
+msgid "OpenStack Foundation"
+msgstr "OpenStack Foundation"
+
+#: ./doc/security-guide/bk-openstack-sec-guide.xml18(year)
+msgid "2013"
+msgstr "2013"
+
+#: ./doc/security-guide/bk-openstack-sec-guide.xml21(releaseinfo)
+msgid "current"
+msgstr "カレント"
+
+#: ./doc/security-guide/bk-openstack-sec-guide.xml22(productname)
+msgid "OpenStack"
+msgstr "OpenStack"
+
+#: ./doc/security-guide/bk-openstack-sec-guide.xml26(remark)
+msgid "Copyright details are filled in by the template."
+msgstr "Copyright details are filled in by the template."
+
+#: ./doc/security-guide/bk-openstack-sec-guide.xml31(para)
+msgid ""
+"This book provides best practices and conceptual information about securing "
+"an OpenStack cloud."
+msgstr "本書は OpenStack クラウドを安全にするためのベストプラクティスと基本的な考え方について書かれています。"
+
+#: ./doc/security-guide/bk-openstack-sec-guide.xml38(date)
+msgid "2013-12-02"
+msgstr "2013-12-02"
+
+#: ./doc/security-guide/bk-openstack-sec-guide.xml42(para)
+msgid "Chapter on Object Storage added."
+msgstr "Object Storage に関する章を追加しました。"
+
+#: ./doc/security-guide/bk-openstack-sec-guide.xml48(date)
+msgid "2013-10-17"
+msgstr "2013-10-17"
+
+#: ./doc/security-guide/bk-openstack-sec-guide.xml52(para)
+msgid "Havana release."
+msgstr "Havana リリース。"
+
+#: ./doc/security-guide/bk-openstack-sec-guide.xml58(date)
+msgid "2013-07-02"
+msgstr "2013-07-02"
+
+#: ./doc/security-guide/bk-openstack-sec-guide.xml62(para)
+msgid "Initial creation..."
+msgstr "初版作成..."
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch033_securing-neutron-services.xml40(None)
+#: ./doc/security-guide/ch033_securing-neutron-services.xml45(None)
+msgid ""
+"@@image: 'static/1aa-logical-neutron-flow.png'; "
+"md5=3589a1ef10ea2bbe189ca90e3c932df2"
+msgstr "@@image: 'static/1aa-logical-neutron-flow.png'; md5=3589a1ef10ea2bbe189ca90e3c932df2"
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml8(title)
+msgid "Securing OpenStack Networking services"
+msgstr "OpenStack Networking サービスのセキュリティ強化"
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml9(para)
+msgid ""
+"To secure OpenStack Networking, you must understand how the workflow process"
+" for tenant instance creation needs to be mapped to security domains."
+msgstr "OpenStack Networking のセキュリティを強化する為に、どの程度テナントインスタンス作成用のワークフロープロセスをセキュリティドメインにマッピングさせる必要があることを理解しなくてはいけません。"
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml13(para)
+msgid ""
+"There are four main services that interact with OpenStack Networking. In a "
+"typical OpenStack deployment these services map to the following security "
+"domains:"
+msgstr "OpenStack Networking と交信する主要なサービスが４つあります。典型的な OpenStack デプロイでは、これらのサービスは以下のセキュリティドメインにマッピングされます。"
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml18(para)
+msgid "OpenStack dashboard: Public and management"
+msgstr "OpenStack Dashboard: パブリック、管理"
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml21(para)
+msgid "OpenStack Identity: Management"
+msgstr "OpenStack Identity: 管理"
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml24(para)
+msgid "OpenStack compute node: Management and guest"
+msgstr "OpenStack Compute ノード: 管理、ゲスト"
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml27(para)
+msgid ""
+"OpenStack network node: Management, guest, and possibly public depending "
+"upon neutron-plugin in use."
+msgstr "OpenStack ネットワークノード: 管理、ゲスト（使用する neutron プラグインによってはパブリックも可能性あり）"
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml31(para)
+msgid ""
+"SDN services node: Management, guest and possibly public depending upon "
+"product used."
+msgstr "SDB サービスノード：管理、ゲスト （使用する製品によってはパブリックも可能性あり）"
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml49(para)
+msgid ""
+"To isolate sensitive data communication between the OpenStack Networking "
+"services and other OpenStack core services, configure these communication "
+"channels to only allow communication over an isolated management network."
+msgstr "OpenStack Networking サービスと他の OpenStack コアサービス間の扱いの難しいデータ通信を分離する為、通信を独立した管理ネットワーク上でのみ行うように通信路を設定します。"
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml54(title)
+msgid "OpenStack Networking service configuration"
+msgstr "OpenStack Networking サービス設定"
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml56(title)
+msgid "Restrict bind address of the API server: neutron-server"
+msgstr "API サーバがバインドするアドレスの制限: neutron-server"
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml57(para)
+msgid ""
+"To restrict the interface or IP address on which the OpenStack Networking "
+"API service binds a network socket for incoming client connections, specify "
+"the bind_host and bind_port in the neutron.conf file as shown:"
+msgstr "OpenStack Networking API サービスが外からのクライアント通信用にネットワークソケットをバインドするネットワークインターフェース又は IP アドレスを制限する為、neutron.conf ファイル中の bind_host と bind_port を以下のように指定します。"
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml64(replaceable)
+msgid "IP ADDRESS OF SERVER"
+msgstr "IP ADDRESS OF SERVER"
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml70(title)
+msgid "Restrict DB and RPC communication of the OpenStack Networking services"
+msgstr "OpenStack Networking サービス群の DB と RPC 通信の制限"
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml72(para)
+msgid ""
+"Various components of the OpenStack Networking services use either the "
+"messaging queue or database connections to communicate with other components"
+" in OpenStack Networking."
+msgstr "OpenStack Networking サービスの様々なコンポーネントは、OpenStack Networking 中の他のコンポーネントとの通信にメッセージキュー又はデータベース接続のいずれかを使用します。"
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml77(para)
+msgid ""
+"It is recommended that you follow the guidelines provided in the Database "
+"Authentication and Access Control chapter in the Database section for all "
+"components that require direct DB connections."
+msgstr "DB への直接接続を必要とする全てのコンポーネントに対し、データベースの章のデータベース認証とアクセスコントロールの節で示されたガイドラインに従う事を推奨します。"
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml82(para)
+msgid ""
+"It is recommended that you follow the guidelines provided in the Queue "
+"Authentication and Access Control chapter in the Messaging section for all "
+"components that require RPC communication."
+msgstr "RPC 通信を必要とする全てのコンポーネントに対し、メッセージングの章のキュー認証とアクセスコントロールの節中で示されたガイドラインに従う事を推奨します。"
+
+#: ./doc/security-guide/ch063_compliance-activities.xml8(title)
+msgid "Compliance activities"
+msgstr "コンプライアンス活動"
+
+#: ./doc/security-guide/ch063_compliance-activities.xml9(para)
+msgid ""
+"There are a number of standard activities that will greatly assist with the "
+"compliance process. In this chapter we outline some of the most common "
+"compliance activities. These are not specific to OpenStack, however we "
+"provide references to relevant sections in this book as useful context."
+msgstr "コンプライアンスのプロセスを大きく推進する、標準的な活動は数多くあります。この章ではいくつかの代表的なコンプライアンス活動を紹介します。これらはOpenStack固有ではありませんが、関係がわかるよう、このガイドの関連する節への参照も記載します。"
+
+#: ./doc/security-guide/ch063_compliance-activities.xml11(title)
+msgid "Information Security Management system (ISMS)"
+msgstr "Information Security Management System (ISMS)"
+
+#: ./doc/security-guide/ch063_compliance-activities.xml12(para)
+msgid ""
+"An Information Security Management System (ISMS) is a comprehensive set of "
+"policies and processes that an organization creates and maintains to manage "
+"risk to information assets. The most common ISMS for cloud deployments is "
+"<link href=\"http://www.27000.org/iso-27001.htm\">ISO/IEC 27001/2</link>, "
+"which creates a solid foundation of security controls and practices for "
+"achieving more stringent compliance certifications."
+msgstr "Information Security Management System (ISMS)は包括的なポリシーとポロセスの集合です。組織が情報資産に関するリスクを管理するため、作成、維持します。もっとも一般的なクラウド向けISMSは<link href=\"http://www.27000.org/iso-27001.htm\">ISO/IEC 27001/2</link>です。より厳格なコンプライアンス認証取得に向けて、セキュリティ統制と実践の確かな基盤を構築します。 "
+
+#: ./doc/security-guide/ch063_compliance-activities.xml15(title)
+msgid "Risk assessment"
+msgstr "リスク評価"
+
+#: ./doc/security-guide/ch063_compliance-activities.xml16(para)
+msgid ""
+"A risk assessment framework identifies risks within an organization or "
+"service, and specifies ownership of these risks, along with implementation "
+"and mitigation strategies. Risks apply to all areas of the service, from "
+"technical controls to environmental disaster scenarios and human elements, "
+"for example a malicious insider (or rogue employee). Risks can be rated "
+"using a variety of mechanisms, for example likelihood vs impact. An "
+"OpenStack deployment risk assessment can include control gaps that are "
+"described in this book."
+msgstr "リスク評価フレームワークは、組織やサービス内のリスクを特定します。また、それらのリスク、実装と緩和戦略の責任者を明確にします。リスクは全てのサービスに適用され、その範囲は技術統制から環境災害、人的要因にわたります。人的要因の例は、悪意ある内部監視者(や不良社員)などです。リスクは発生確率や影響度など、多様な指標を使って評価されます。OpenStack環境のリスク評価はこのガイドで触れられている統制のギャップを含みます。"
+
+#: ./doc/security-guide/ch063_compliance-activities.xml19(title)
+msgid "Access and log reviews"
+msgstr "アクセスとログのレビュー"
+
+#: ./doc/security-guide/ch063_compliance-activities.xml20(para)
+msgid ""
+"Periodic access and log reviews are required to ensure authentication, "
+"authorization, and accountability in a service deployment. Specific guidance"
+" for OpenStack on these topics are discussed in-depth in the logging "
+"section."
+msgstr "定期的なアクセスとログの検査は、認証、認可とサービス配備における責任を明確にするため、必要です。これらのトピックに関するOpenStack向けのガイダンスは、ロギングの節で詳細に説明します。"
+
+#: ./doc/security-guide/ch063_compliance-activities.xml23(title)
+msgid "Backup and disaster recovery"
+msgstr "バックアップと災害対策"
+
+#: ./doc/security-guide/ch063_compliance-activities.xml24(para)
+msgid ""
+"Disaster Recovery (DR) and Business Continuity Planning (BCP) plans are "
+"common requirements for ISMS and compliance activities. These plans must be "
+"periodically tested as well as documented. In OpenStack key areas are found "
+"in the management security domain, and anywhere that single points of "
+"failure (SPOFs) can be identified. See the section on secure backup and "
+"recovery for additional details."
+msgstr "災害対策(Disaster Recovery, DR)とビジネス継続計画(Business Continuity Planning, BCP)はISMSとコンプライアンス活動で共通の要件です。それらの計画は定期的な検査と文書化が必要とします。OpenStackの主要領域はマネジメントセキュリティ領域にあたり、すべての単一障害点(Single Point of Failures, SPOFs)が特定されなければいけません。詳細は、安全なバックアップとリカバリーの節を参照してください。"
+
+#: ./doc/security-guide/ch063_compliance-activities.xml27(title)
+msgid "Security training"
+msgstr "セキュリティトレーニング"
+
+#: ./doc/security-guide/ch063_compliance-activities.xml28(para)
+msgid ""
+"Annual, role-specific, security training is a mandatory requirement for "
+"almost all compliance certifications and attestations. To optimise the "
+"effectiveness of security training, a common method is to provide role "
+"specific training, for example to developers, operational personnel, and "
+"non-technical employees. Additional cloud security or OpenStack security "
+"training based on this hardening guide would be ideal."
+msgstr "年次でのロール別セキュリティトレーニングは、ほぼすべてのコンプライアンス認証、認定で必須の要件です。セキュリティトレーニングの効果を最適化するため、一般的にはロール別に実施します。例えば開発者、運用担当者、非技術者別、などです。加えて、このガイドにもとづくクラウド、OpenStackセキュリティに関するトレーニングの実施が理想的でしょう。"
+
+#: ./doc/security-guide/ch063_compliance-activities.xml31(title)
+msgid "Security reviews"
+msgstr "セキュリティの検査"
+
+#: ./doc/security-guide/ch063_compliance-activities.xml32(para)
+msgid ""
+"As OpenStack is a popular open source project, much of the codebase and "
+"architecture has been scrutinized by individual contributors, organizations "
+"and enterprises. This can be advantageous from a security perspective, "
+"however the need for security reviews is still a critical consideration for "
+"service providers, as deployments vary, and security is not always the "
+"primary concern for contributors. A comprehensive security review process "
+"may include architectural review, threat modelling, source code analysis and"
+" penetration testing. There are many techniques and recommendations for "
+"conducting security reviews that can be found publicly posted. A well-tested"
+" example is the <link "
+"href=\"http://www.microsoft.com/security/sdl/process/release.aspx\">Microsoft"
+" SDL</link>, created as part of the Microsoft Trustworthy Computing "
+"Initiative."
+msgstr "OpenStackは人気のあるオープンソースプロジェクトです。多くのソースコードとアーキテクチャはデベロッパー、組織、企業によって精査されています。これはセキュリティの観点から大きな利点ですが、セキュリティ検査はサービスプロバイダーにとって、それでもなお重大な懸念事項です。環境は変化しつづけますが、セキュリティは必ずしも開発者の一番の関心事ではないからです。包括的なセキュリティ検査プロセスとして、アーキテクチャ検査、脅威のモデリング、ソースコード分析と侵入テストなどが挙げられます。そして、セキュリティ検査には広く公開されている多くのテクニックと推奨があります。よくテストされた例として、Microsoft Trustworthy Computing Initiativeのとりくみとして作成された、<link href=\"http://www.microsoft.com/security/sdl/process/release.aspx\">Microsoft SDL</link>があります。"
+
+#: ./doc/security-guide/ch063_compliance-activities.xml48(title)
+#: ./doc/security-guide/ch012_configuration-management.xml16(title)
+msgid "Vulnerability management"
+msgstr "脆弱性管理"
+
+#: ./doc/security-guide/ch063_compliance-activities.xml49(para)
+msgid ""
+"Security updates are critical to any IaaS deployment, whether private or "
+"public. Vulnerable systems expand attack surfaces, and are obvious targets "
+"for attackers. Common scanning technologies and vulnerability notification "
+"services can help mitigate this threat. It is important that scans are "
+"authenticated and that mitigation strategies extend beyond simple perimeter "
+"hardening. Multi-tenant architectures such as OpenStack are particularly "
+"prone to hypervisor vulnerabilities, making this a critical part of the "
+"system for vulnerability management. See the section on instance isolation "
+"for additional details."
+msgstr "セキュリティアップデートはプライベート、パブリックを問わず、あらゆるIaaS環境において重要です。脆弱なシステムは攻撃面を広げ、攻撃者にターゲットをさらしてしまいます。一般的なスキャニング技術と脆弱性検知サービスはこの脅威を和らげるのに役立ちます。スキャンが認証されたものであり、その緩和戦略が単なる境界線の防御力向上にとどまらないことが重要です。OpenStackのようなマルチテナントアーキテクチャは特にハイパーバイザーの脆弱性に影響されやすく、それはシステムの脆弱性管理の重点項目です。詳細はインスタンス隔離の節を参照してください。"
+
+#: ./doc/security-guide/ch063_compliance-activities.xml52(title)
+msgid "Data classification"
+msgstr "データの分類"
+
+#: ./doc/security-guide/ch063_compliance-activities.xml53(para)
+msgid ""
+"Data Classification defines a method for classifying and handling "
+"information, often to protect customer information from accidental or "
+"deliberate theft, loss, or inappropriate disclosure. Most commonly this "
+"involves classifying information as sensitive or non-sensitive, or as "
+"personally identifiable information (PII). Depending on the context of the "
+"deployment various other classifying criteria may be used (government, "
+"health-care etc). The underlying principle is that data classifications are "
+"clearly defined and in-use. The most common protective mechanisms include "
+"industry standard encryption technologies. See the data security section for"
+" additional details."
+msgstr "データの分類作業は、多くの場合、顧客情報を事故、故意の窃盗、損失、不適切な公開から保護するため、情報の分類と扱いの方法を定義します。一般的にこの作業は、情報を機密性の有無、個人識別の可不可(Personally Identifiable Information, PII)による分類を含みます。使用される基準はその環境、背景によって様々です(政府、ヘルスケアなど)。そして根本的な原則は、そのデータ分類が明確に定義され、通常利用されていることです。もっとも一般的な保護メカニズムには、業界標準の暗号化技術が挙げられます。詳細はデータセキュリティの節を参照してください。"
+
+#: ./doc/security-guide/ch063_compliance-activities.xml56(title)
+msgid "Exception process"
+msgstr "例外プロセス"
+
+#: ./doc/security-guide/ch063_compliance-activities.xml57(para)
+msgid ""
+"An exception process is an important component of an ISMS. When certain "
+"actions are not compliant with security policies that an organization has "
+"defined, they must be logged. Appropriate justification, description and "
+"mitigation details need to be included, and signed off by appropriate "
+"authorities. OpenStack default configurations may vary in meeting various "
+"compliance criteria, areas that fail to meet compliance requirements should "
+"be logged, with potential fixes considered for contribution to the "
+"community."
+msgstr "例外プロセスはISMSの重要な要素です。とある行動が組織の定義したセキュリティポリシーに準拠していない場合、それは記録されなければいけません。適正な理由と緩和策の詳細が含まれ、関係当局に認められる必要があります。OpenStackのデフォルト構成は、様々なコンプライアンス基準、記録されるべきコンプライアンス基準を満たすべく、変化していくでしょう。またそれは、コミュニティへの貢献によって修正されていく可能性があります。"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch004_book-introduction.xml113(None)
+#: ./doc/security-guide/ch004_book-introduction.xml118(None)
+msgid ""
+"@@image: 'static/marketecture-diagram.png'; "
+"md5=4ab13a64f80c210be3120abc5c7aee8a"
+msgstr "@@image: 'static/marketecture-diagram.png'; md5=4ab13a64f80c210be3120abc5c7aee8a"
+
+#: ./doc/security-guide/ch004_book-introduction.xml8(title)
+msgid "Introduction to OpenStack"
+msgstr "OpenStack の概要"
+
+#: ./doc/security-guide/ch004_book-introduction.xml9(para)
+msgid ""
+"This guide provides security insight into OpenStack deployments. The "
+"intended audience is cloud architects, deployers, and administrators. In "
+"addition, cloud users will find the guide both educational and helpful in "
+"provider selection, while auditors will find it useful as a reference "
+"document to support their compliance certification efforts. This guide is "
+"also recommended for anyone interested in cloud security."
+msgstr "本ガイドは、OpenStack のデプロイメントにおけるセキュリティに関する知見を提供します。クラウドアーキテクト、デプロイ担当者、管理者などを対象読者としています。また、クラウドユーザーには、プロバイダー選択にあたって参照することのできる有用な情報を記載している一方、監査担当者には、コンプライアンス認証に伴う作業を支援する参考資料としてご利用いただくことができます。本ガイドは、クラウドのセキュリティに関心を持つ読者全般にもお奨めします。"
+
+#: ./doc/security-guide/ch004_book-introduction.xml16(para)
+msgid ""
+"Each OpenStack deployment embraces a wide variety of technologies, spanning "
+"Linux distributions, database systems, messaging queues, OpenStack "
+"components themselves, access control policies, logging services, security "
+"monitoring tools, and much more. It should come as no surprise that the "
+"security issues involved are equally diverse, and their in-depth analysis "
+"would require several guides. We strive to find a balance, providing enough "
+"context to understand OpenStack security issues and their handling, and "
+"provide external references for further information. The guide could be read"
+" from start to finish or sampled as necessary like a reference."
+msgstr "OpenStack の各デプロイメントには、Linux ディストリビューション、データベースシステム、メッセージキュー、OpenStack のコンポーネント自体、アクセス制御ポリシー、ログサービス、セキュリティ監視ツールなどに及ぶ、多種多様なテクノロジーが採用されます。このため、デプロイに伴うセキュリティ問題が、同じように多様となることは当然です。それらの内容を奥深く分析するには、マニュアルが数冊必要となります。 本ガイドでは、OpenStack のセキュリティ問題とその対処方法を理解するために十分な情報を提供しつつ、さらなる情報の外部参照先を掲載することにより、バランスを図っています。本書は、全体を通読する方法または参考資料として必要箇所のみを参照する方法のいずれでもご利用いただくことができます。"
+
+#: ./doc/security-guide/ch004_book-introduction.xml27(para)
+msgid ""
+"We briefly introduce the kinds of clouds: private, public, and hybrid before"
+" presenting an overview of the OpenStack components and their related "
+"security concerns in the remainder of the chapter."
+msgstr "本章では、プライベート、パブリック、ハイブリッドというクラウドの各種類について簡単に説明した後、後半に OpenStack のコンポーネントおよびそれらに関連するセキュリティ課題について概説します。"
+
+#: ./doc/security-guide/ch004_book-introduction.xml32(title)
+msgid "Cloud types"
+msgstr "クラウドのタイプ"
+
+#: ./doc/security-guide/ch004_book-introduction.xml33(para)
+msgid ""
+"OpenStack is a key enabler in adoption of cloud technology and has several "
+"common deployment use cases. These are commonly known as Public, Private, "
+"and Hybrid models. The following sections use the National Institute of "
+"Standards and Technology (NIST) <link "
+"href=\"http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf\">definition"
+" of cloud</link> to introduce these different types of cloud as they apply "
+"to OpenStack."
+msgstr "OpenStack は、クラウドテクノロジーの導入における重要なイネーブラーであり、一般的なデプロイメントユースケースがいくつかあります。これらは、パブリック、プライベート、およびハイブリッドモデルとして一般に知られています。以下のセクションでは、National Institute of Standards and Technology (NIST) <link href=\"http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf\"> のクラウドの定義</link> を取り上げ、OpenStack に適用するクラウドの異なるタイプについて説明します。"
+
+#: ./doc/security-guide/ch004_book-introduction.xml42(title)
+msgid "Public cloud"
+msgstr "パブリッククラウド"
+
+#: ./doc/security-guide/ch004_book-introduction.xml43(para)
+msgid ""
+"According to NIST, a public cloud is one in which the infrastructure is open"
+" to the general public for consumption. OpenStack public clouds are "
+"typically run by a service provider and can be consumed by individuals, "
+"corporations, or any paying customer. A public cloud provider may expose a "
+"full set of features such as software-defined networking, block storage, in "
+"addition to multiple instance types. Due to the nature of public clouds, "
+"they are exposed to a higher degree of risk. As a consumer of a public cloud"
+" you should validate that your selected provider has the necessary "
+"certifications, attestations, and other regulatory considerations. As a "
+"public cloud provider, depending on your target customers, you may be "
+"subject to one or more regulations. Additionally, even if not required to "
+"meet regulatory requirements, a provider should ensure tenant isolation as "
+"well as protecting management infrastructure from external attacks."
+msgstr "NIST によると、パブリッククラウドは、一般市民が利用できるようにインフラストラクチャーが公開されているクラウドと定義されています。OpenStack のパブリッククラウドは、通常サービスプロバイダーによって運用され、個人、法人、または料金を支払っている顧客が利用することができます。パブリッククラウドプロバイダーは、複数のインスタンスタイプに加えて、ソフトウェア定義ネットワーク、ブロックストレージなどの各種機能を公開することができます。パブリッククラウドはその性質上、より高いレベルのリスクにさらされます。パブリッククラウドの利用者は、選択したプロバイダーが必要な認定および認証を取得しているか、その他の法規制に関する考慮事項に対応しているかなどの点を確認しておく必要があります。パブリッククラウドプロバイダーは、ターゲット顧客に応じて、1 つまたは複数の法規制の影響を受ける場合があります。また、プロバイダーは、法規制の要件を満たす必要がない場合でも、管理インフラストラクチャーを外部の攻撃から保護するために、テナントの分離を確実に行う必要があります。"
+
+#: ./doc/security-guide/ch004_book-introduction.xml61(title)
+msgid "Private cloud"
+msgstr "プライベートクラウド"
+
+#: ./doc/security-guide/ch004_book-introduction.xml62(para)
+msgid ""
+"At the opposite end of the spectrum is the private cloud. As NIST defines "
+"it, a private cloud is provisioned for exclusive use by a single "
+"organization comprising multiple consumers, such as business units. It may "
+"be owned, managed, and operated by the organization, a third-party, or some "
+"combination of them, and it may exist on or off premises. Private cloud use "
+"cases are diverse, as such, their individual security concerns vary."
+msgstr "パブリッククラウドの対極にあるのがプライベートクラウドです。NIST は、プライベートクラウドを、事業組織などの複数の利用者から成る単一の組織の専用使用のために提供されるクラウドと定義しています。プライベートクラウドの所有、管理、および運用は、その組織、第三者、もしくはそれらの組み合わせにより行われ、存在場所としては、その組織の施設内または外部の場合があります。プライベートクラウドのユースケースは多様であるため、セキュリティ課題もそれぞれで異なります。"
+
+#: ./doc/security-guide/ch004_book-introduction.xml72(title)
+msgid "Community cloud"
+msgstr "コミュニティクラウド"
+
+#: ./doc/security-guide/ch004_book-introduction.xml73(para)
+msgid ""
+"NIST defines a community cloud as one whose infrastructure is provisioned "
+"for the exclusive use by a specific community of consumers from "
+"organizations that have shared concerns. For example, mission, security "
+"requirements, policy, and compliance considerations. It may be owned, "
+"managed, and operated by one or more of the organizations in the community, "
+"a third-party, or some combination of them, and it may exist on or off "
+"premises."
+msgstr "NIST では、コミュニティクラウドを、共通の関心事 (例えば、任務、セキュリティの必要、ポリシー、法令順守に関わる考慮事項 ) を持つ複数の組織から成る特定の利用者の共同体の専用使用のために提供されるクラウドと定義しています。コミュニティクラウドの所有、管理、および運用は、共同体内の 1 つまたは複数の組織、第三者、もしくはそれらの組み合わせにより行われ、存在場所はその組織の施設内または外部の場合があります。"
+
+#: ./doc/security-guide/ch004_book-introduction.xml83(title)
+msgid "Hybrid cloud"
+msgstr "ハイブリッドクラウド"
+
+#: ./doc/security-guide/ch004_book-introduction.xml84(para)
+msgid ""
+"A hybrid cloud is defined by NIST as a composition of two or more distinct "
+"cloud infrastructures, such as private, community, or public, that remain "
+"unique entities, but are bound together by standardized or proprietary "
+"technology that enables data and application portability, such as cloud "
+"bursting for load balancing between clouds. For example an online retailer "
+"may have their advertising and catalogue presented on a public cloud that "
+"allows for elastic provisioning. This would enable them to handle seasonal "
+"loads in a flexible, cost-effective fashion. Once a customer begins to "
+"process their order, they are transferred to the more secure private cloud "
+"backend that is PCI compliant."
+msgstr "NIST では、ハイブリッドクラウドを、2 つ以上の異なるクラウドインフラストラクチャー (プライベート、コミュニティ、パブリック) を組み合わせたクラウドと定義しています。各クラウドは、依然として独自のエンティティですが、データおよびアプリケーションの移植性を提供するスタンダードまたはプロプライエタリな技術 (例: クラウド間のロードバランスのためのクラウドバーストなど) により結合されます。例えば、オンライン小売業者は、柔軟なプロビジョニングが可能なパブリッククラウドに広告やカタログを掲示している場合があります。これにより、柔軟かつ費用対効果の高い方法で季節的な負荷に対応することが可能となります。顧客が発注処理を開始すると、よりセキュアなプライベートクラウドのバックエンドに転送されます。"
+
+#: ./doc/security-guide/ch004_book-introduction.xml96(para)
+msgid ""
+"For the purposes of this document, we treat Community and Hybrid similarly, "
+"dealing explicitly only with the extremes of Public and Private clouds from "
+"a security perspective. Your security measures depend where your deployment "
+"falls upon the private public continuum."
+msgstr "本ガイドにおいては、コミュニティクラウドとハイブリッドクラウドを同様に扱い、パブリッククラウドとプライベートクラウドの両極のみをセキュリティ面から明確に説明します。セキュリティ対策は、デプロイメントがプライベートクラウド/パブリッククラウドの連続体のどこに位置するかによって異なります。"
+
+#: ./doc/security-guide/ch004_book-introduction.xml104(title)
+msgid "OpenStack service overview"
+msgstr "OpenStack サービスの概観"
+
+#: ./doc/security-guide/ch004_book-introduction.xml105(para)
+msgid ""
+"OpenStack embraces a modular architecture to provide a set of core services "
+"that facilitates scalability and elasticity as core design tenets. This "
+"chapter briefly reviews OpenStack components, their use cases and security "
+"considerations."
+msgstr "OpenStack は、モジュール型アーキテクチャを採用し、中核的な設計理念としてスケーラビリティと柔軟性を促進する一式のコアサービスを提供します。本章では、OpenStack のコンポーネントとそれらのユースケースおよびセキュリティに関する考慮事項を簡単に説明します。"
+
+#: ./doc/security-guide/ch004_book-introduction.xml122(title)
+#: ./doc/security-guide/ch026_compute.xml8(title)
+msgid "Compute"
+msgstr "Compute"
+
+#: ./doc/security-guide/ch004_book-introduction.xml123(para)
+msgid ""
+"OpenStack Compute service (nova) provides services to support the management"
+" of virtual machine instances at scale, instances that host multi-tiered "
+"applications, dev/test environments, \"Big Data\" crunching Hadoop clusters,"
+" and/or high performance computing."
+msgstr "OpenStack Compute サービス (Nova) は、多層アプリケーション、開発/テスト環境、「ビッグデータ」を処理する Hadoop のクラスター、ハイパフォーマンスコンピューティングなどをホストする、大規模な仮想マシンインスタンスの管理をサポートするサービスを提供します。"
+
+#: ./doc/security-guide/ch004_book-introduction.xml128(para)
+msgid ""
+"The Compute service facilitates this management through an abstraction layer"
+" that interfaces with supported hypervisors, which we address later on in "
+"more detail."
+msgstr "Compute は、サポート対象のハイパーバイザーと連動する抽象化レイヤーを介してこのような管理を行います。ハイパーバイザーについては、後半で詳しく説明します。"
+
+#: ./doc/security-guide/ch004_book-introduction.xml131(para)
+msgid ""
+"Later in the guide, we focus generically on the virtualization stack as it "
+"relates to hypervisors."
+msgstr "本ガイドの後半では、ハイパーバイザーと関連する仮想化スタックに焦点をあてて、包括的に解説します。"
+
+#: ./doc/security-guide/ch004_book-introduction.xml133(para)
+msgid ""
+"For information about the current state of feature support, see <link "
+"href=\"https://wiki.openstack.org/wiki/HypervisorSupportMatrix\">OpenStack "
+"Hypervisor Support Matrix</link>."
+msgstr "機能サポートの現在の状況に関する情報は、 <link href=\"https://wiki.openstack.org/wiki/HypervisorSupportMatrix\">OpenStack Hypervisor Support Matrix</link> を参照してください。"
+
+#: ./doc/security-guide/ch004_book-introduction.xml137(para)
+msgid ""
+"The security of Compute is critical for an OpenStack deployment. Hardening "
+"techniques should include support for strong instance isolation, secure "
+"communication between Compute sub-components, and resiliency of public-"
+"facing <glossterm>API</glossterm> endpoints."
+msgstr "OpenStack のデプロイメントでは、Compute のセキュリティが極めて重要となります。セキュリティ強化のテクニックには、頑強なインスタンスの隔離、Compute のサブコンポーネント間におけるセキュアな通信、一般向けの  <glossterm>API</glossterm> エンドポイントの弾力性などがあげられます。"
+
+#: ./doc/security-guide/ch004_book-introduction.xml144(title)
+#: ./doc/security-guide/ch027_storage.xml8(title)
+msgid "Object Storage"
+msgstr "Object Storage"
+
+#: ./doc/security-guide/ch004_book-introduction.xml145(para)
+msgid ""
+"The OpenStack Object Storage service (swift) provides support for storing "
+"and retrieving arbitrary data in the cloud. The Object Storage service "
+"provides both a native API and an Amazon Web Services S3 compatible API. The"
+" service provides a high degree of resiliency through data replication and "
+"can handle petabytes of data."
+msgstr "OpenStack Object Storage Service (swift) は、クラウド内の任意データの保管/取得機能のサポートを提供します。Object Storage Service  はネイティブ API および Amazon Web Services S3 互換の API の両方を提供します。このサービスは、データレプリケーションにより高度な回復性を提供し、ペタバイト規模のデータの処理が可能です。"
+
+#: ./doc/security-guide/ch004_book-introduction.xml151(para)
+msgid ""
+"It is important to understand that object storage differs from traditional "
+"file system storage. It is best used for static data such as media files "
+"(MP3s, images, videos), virtual machine images, and backup files."
+msgstr "オブジェクトストレージは、従来のファイルシステムストレージと異なる点を理解しておくことが重要です。メディアファイル (MP3、画像、ビデオ) や仮想マシンイメージ、バックアップファイルなどの静的データに使用するのに最適です。"
+
+#: ./doc/security-guide/ch004_book-introduction.xml155(para)
+msgid ""
+"Object security should focus on access control and encryption of data in "
+"transit and at rest. Other concerns may relate to system abuse, illegal or "
+"malicious content storage, and cross authentication attack vectors."
+msgstr "オブジェクトのセキュリティは、アクセス制御と、伝送中および静止中のデータの暗号化に重点を置くべきです。その他の懸念事項には、システムの悪用、不法または悪意のあるコンテンツの保管、クロス認証の攻撃ベクトルなどに関する問題があげられます。"
+
+#: ./doc/security-guide/ch004_book-introduction.xml161(title)
+msgid "Block Storage"
+msgstr "Block Storage"
+
+#: ./doc/security-guide/ch004_book-introduction.xml162(para)
+msgid ""
+"The OpenStack Block Storage service (cinder) provides persistent block "
+"storage for compute instances. The Block Storage service is responsible for "
+"managing the life-cycle of block devices, from the creation and attachment "
+"of volumes to instances, to their release."
+msgstr "OpenStack Block Storage Service (cinder) は、Compute インスタンス用に永続的なブロックストレージを提供します。Block Storage Service はブロックデバイスの作成からインスタンスへのボリュームの接続、それらの解放にいたるまでのライフサイクルを管理する役割を果たします。"
+
+#: ./doc/security-guide/ch004_book-introduction.xml167(para)
+msgid ""
+"Security considerations for block storage are similar to that of object "
+"storage."
+msgstr "Block Storage のセキュリティ課題は、Object Storage の場合と同様です。"
+
+#: ./doc/security-guide/ch004_book-introduction.xml171(title)
+msgid "OpenStack Networking"
+msgstr "OpenStack Networking"
+
+#: ./doc/security-guide/ch004_book-introduction.xml172(para)
+msgid ""
+"The OpenStack Networking service (neutron, previously called quantum) "
+"provides various networking services to cloud users (tenants) such as IP "
+"address management, <glossterm>DNS</glossterm>, <glossterm>DHCP</glossterm>,"
+" load balancing, and security groups (network access rules, like firewall "
+"policies). It provides a framework for software defined networking (SDN) "
+"that allows for pluggable integration with various networking solutions."
+msgstr "OpenStack Networking (neutron、旧称 quantum) はIP アドレス管理、<glossterm>DNS</glossterm>、<glossterm>DHCP</glossterm>、負荷分散、セキュリティグループ (ファイアウォールのポリシーなど、ネットワークのアクセスルール) など、さまざまなネットワークサービスをクラウドユーザー (テナント) に提供します。また、各種ネットワークソリューションとのプラグ可能な統合を可能にするソフトウェア定義ネットワーク(SDN) のフレームワークを提供します。"
+
+#: ./doc/security-guide/ch004_book-introduction.xml180(para)
+msgid ""
+"OpenStack Networking allows cloud tenants to manage their guest network "
+"configurations. Security concerns with the networking service include "
+"network traffic isolation, availability, integrity and confidentiality."
+msgstr "OpenStack Networking により、クラウドテナントはゲストのネットワーク設定を管理することができます。ネットワークサービスに伴うセキュリティ上の問題には、 ネットワークトラフィックの隔離、可用性、完全性、機密性などがあげられます。"
+
+#: ./doc/security-guide/ch004_book-introduction.xml186(title)
+#: ./doc/security-guide/ch025_web-dashboard.xml8(title)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml33(title)
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml120(para)
+msgid "Dashboard"
+msgstr "Dashboard"
+
+#: ./doc/security-guide/ch004_book-introduction.xml187(para)
+msgid ""
+"The OpenStack dashboard (horizon) provides a web-based interface for both "
+"cloud administrators and cloud tenants. Through this interface "
+"administrators and tenants can provision, manage, and monitor cloud "
+"resources. Horizon is commonly deployed in a public facing manner with all "
+"the usual security concerns of public web portals."
+msgstr "OpenStack ダッシュボードサービス (Horizon) は、クラウド管理者とクラウドテナントの両方に向けた Web ベースのインターフェースを提供します。このインターフェースにより、管理者およびテナントは、クラウドリソースのプロビジョニング、管理、監視を行うことができます。Horizon は通常、一般i向けにデプロイされ、パブリック Web ポータルの一般的なセキュリティ問題が伴います。"
+
+#: ./doc/security-guide/ch004_book-introduction.xml195(title)
+msgid "Identity service"
+msgstr "Identity"
+
+#: ./doc/security-guide/ch004_book-introduction.xml196(para)
+msgid ""
+"The OpenStack Identity service (keystone) is a <emphasis "
+"role=\"bold\">shared service</emphasis> that provides authentication and "
+"authorization services throughout the entire cloud infrastructure. The "
+"Identity service has pluggable support for multiple forms of authentication."
+msgstr "OpenStack Identity (keystone) は、クラウドインフラストラクチャー全体にわたる認証および承認サービスを提供する<emphasis role=\"bold\">共有サービス</emphasis>です。Identity には、複数形式の認証に対するプラグ可能なサポートを採用しています。"
+
+#: ./doc/security-guide/ch004_book-introduction.xml201(para)
+msgid ""
+"Security concerns here pertain to trust in authentication, management of "
+"authorization tokens, and secure communication."
+msgstr "ここでのセキュリティ課題には、認証の信頼、承認トークンの管理、セキュリティ保護された通信などがあげられます。"
+
+#: ./doc/security-guide/ch004_book-introduction.xml206(title)
+msgid "Image Service"
+msgstr "Image Service"
+
+#: ./doc/security-guide/ch004_book-introduction.xml207(para)
+msgid ""
+"The OpenStack Image Service (glance) provides disk image management "
+"services. The Image Service provides image discovery, registration, and "
+"delivery services to the Compute service, as needed."
+msgstr "OpenStack Image Service (glance) は、ディスクイメージ管理サービスを提供します。Image Service は、必要に応じて、イメージの検索、登録、デリバリサービスを Compute サービスに提供します。"
+
+#: ./doc/security-guide/ch004_book-introduction.xml211(para)
+msgid ""
+"Trusted processes for managing the life cycle of disk images are required, "
+"as are all the previously mentioned issues with respect to data security."
+msgstr "前述したデータセキュリティに関する問題と同様に、ディスクイメージのライフサイクル管理には信頼されたプロセスが必要です。"
+
+#: ./doc/security-guide/ch004_book-introduction.xml216(title)
+msgid "Other supporting technology"
+msgstr "その他の支援技術"
+
+#: ./doc/security-guide/ch004_book-introduction.xml217(para)
+msgid ""
+"OpenStack relies on messaging for internal communication between several of "
+"its services. By default, OpenStack uses message queues based on the "
+"Advanced Message Queue Protocol (<glossterm baseform=\"Advanced Message "
+"Queuing Protocol (AMQP)\">AMQP </glossterm>). Similar to most OpenStack "
+"services, it supports pluggable components. Today the implementation backend"
+" could be <glossterm>RabbitMQ</glossterm>, <glossterm>Qpid</glossterm>, or "
+"<glossterm>ZeroMQ</glossterm>."
+msgstr "OpenStack は複数のサービス間の内部通信のメッセージングに依存しています。デフォルトでは、OpenStack は Advanced Message Queue Protocol (<glossterm baseform=\"Advanced Message Queuing Protocol (AMQP)\">AMQP</glossterm>) をベースとするメッセージキューを使用します。 大半の OpenStack サービスと同様に、プラグ可能なコンポーネントをサポートしています。現在は、<glossterm>RabbitMQ</glossterm>、 <glossterm>Qpid</glossterm>、または  <glossterm>ZeroMQ</glossterm> を実装バックエンドにすることができます。"
+
+#: ./doc/security-guide/ch004_book-introduction.xml226(para)
+msgid ""
+"As most management commands flow through the message queueing system, it is "
+"a primary security concern for any OpenStack deployment. Message queueing "
+"security is discussed in detail later in this guide."
+msgstr "メッセージキューシステムは、大半の管理コマンドが通過するので、OpenStack のデプロイメントにおける重要なセキュリティ課題です。メッセージキューのセキュリティについては、本ガイドの後半で詳述します。"
+
+#: ./doc/security-guide/ch004_book-introduction.xml230(para)
+msgid ""
+"Several of the components use databases though it is not explicitly called "
+"out. Securing the access to the databases and their contents is yet another "
+"security concern, and consequently discussed in more detail later in this "
+"guide."
+msgstr "一部のコンポーネントは、間接的にデータベースを使用します。データベースおよびそのコンテンツへのアクセスのセキュリティ保護は、もう一つのセキュリティ課題であるため、本ガイドの後半でさらに詳しく説明します。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml8(title)
+msgid "Certification and compliance statements"
+msgstr "認証とコンプライアンスの報告書"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml9(para)
+msgid ""
+"Compliance and security are not exclusive, and must be addressed together. "
+"OpenStack deployments are unlikely to satisfy compliance requirements "
+"without security hardening. The listing below provides an OpenStack "
+"architect foundational knowledge and guidance to achieve compliance against "
+"commercial and government certifications and standards."
+msgstr "コンプライアンスとセキュリティは排他的でなく、あわせて取り組むべきものです。OpenStack環境は、セキュリティの強化なしに、コンプライアンス要件を充足することができないでしょう。以下のリストは、OpenStackアーキテクト向けの、商業規格および政府機関の認証を得るための基本的な知識とガイダンスです。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml17(title)
+msgid "Commercial standards"
+msgstr "商業規格"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml18(para)
+msgid ""
+"For commercial deployments of OpenStack, it is recommended that SOC 1/2 "
+"combined with ISO 2700 1/2 be considered as a starting point for OpenStack "
+"certification activities. The required security activities mandated by these"
+" certifications facilitate a foundation of security best practices and "
+"common control criteria that can assist in achieving more stringent "
+"compliance activities, including government attestations and certifications."
+msgstr "OpenStackの商用環境向けには、まずは開始点として、SOC 1/2とISO 27001/2の検討を推奨します。そこで要求されるセキュリティ活動を確実に実行することで、セキュリティのベストプラクティスと共通統制基準を導入を促進し、政府系認定などの、より厳格なコンプライアンス活動の取得にも役立ちます。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml26(para)
+msgid ""
+"After completing these initial certifications, the remaining certifications "
+"are more deployment specific. For example, clouds processing credit card "
+"transactions will need PCI-DSS, clouds storing health care information "
+"require HIPAA, and clouds within the federal government may require "
+"FedRAMP/FISMA, and ITAR, certifications."
+msgstr "これらの基本的認証を取得したのち、より環境特有の認証を検討します。たとえば、クラウドがクレジットカードのトランザクションを扱うのであればPCI-DSSが必要ですし、ヘルスケア情報を保持するならHIPPAが、連邦政府向けにはFedRAMP/FISMA、ITAR認証が必要となるでしょう。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml34(title)
+msgid "SOC 1 (SSAE 16) / ISAE 3402"
+msgstr "SOC 1 (SSAE 16) / ISAE 3402"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml35(para)
+msgid ""
+"Service Organization Controls (SOC) criteria are defined by the <link "
+"href=\"http://www.aicpa.org/\">American Institute of Certified Public "
+"Accountants</link> (AICPA). SOC controls assess relevant financial "
+"statements and assertions of a service provider, such as compliance with the"
+" Sarbanes-Oxley Act. SOC 1 is a replacement for Statement on Auditing "
+"Standards No. 70 (SAS 70) Type II report. These controls commonly include "
+"physical data centers in scope."
+msgstr "Service Organization Controls (SOC)基準は米国公認会計士協会 - <link href=\"http://www.aicpa.org/\">American Institute of Certified Public Accountants</link> (AICPA)によって定められています。SOC統制はサービスプロバイダーの関連財務諸表と主張を評価します。例えばSarbanes-Oxley法への準拠などです。SOC 1 はStatement on Auditing Standards No. 70 (SAS 70) Type II 報告書を代替します。これらの統制は物理的なデータセンターを評価範囲に含みます。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml44(para)
+msgid "There are two types of SOC 1 reports:"
+msgstr "SOC 1報告書には二つの種類があります。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml47(para)
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml84(para)
+msgid ""
+"Type 1 – report on the fairness of the presentation of management's "
+"description of the service organization's system and the suitability of the "
+"design of the controls to achieve the related control objectives included in"
+" the description as of a specified date."
+msgstr "Type 1 - サービス提供組織がその管理について説明し、その公正さをレポートします。特定時点で関連する管理対象を統制できているか、その設計の持続可能性も報告します。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml54(para)
+msgid ""
+"Type 2 – report on the fairness of the presentation of management's "
+"description of the service organization's system and the suitability of the "
+"design and operating effectiveness of the controls to achieve the related "
+"control objectives included in the description throughout a specified period"
+msgstr "Type 2 - サービス組織が統制対象を統制するために使用するシステム、設計の持続性、および運用効率性に関する管理者の説明内容が公正かをレポートします。特定期間を通しての説明も必要です。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml62(para)
+msgid ""
+"For more details see the <link "
+"href=\"http://www.aicpa.org/InterestAreas/FRC/AssuranceAdvisoryServices/Pages/AICPASOC1Report.aspx\">AICPA"
+" Report on Controls at a Service Organization Relevant to User Entities’ "
+"Internal Control over Financial Reporting</link>."
+msgstr "詳細は<link href=\"http://www.aicpa.org/InterestAreas/FRC/AssuranceAdvisoryServices/Pages/AICPASOC1Report.aspx\">AICPA Report on Controls at a Service Organization Relevant to User Entities’ Internal Control over Financial Reporting</link>を参照してください。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml70(title)
+msgid "SOC 2"
+msgstr "SOC 2"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml71(para)
+msgid ""
+"Service Organization Controls (SOC) 2 is a self attestation of controls that"
+" affect the security, availability, and processing integrity of the systems "
+"a service organization uses to process users' data and the confidentiality "
+"and privacy of information processed by these system. Examples of users are "
+"those responsible for governance of the service organization; customers of "
+"the service organization; regulators; business partners; suppliers and "
+"others who have an understanding of the service organization and its "
+"controls."
+msgstr "Service Organization Controls (SOC) 2は、サービス提供組織がユーザーデータとその情報の機密性とプライバシーを制御するために使っているシステムのセキュリティ、可用性、および処理の完全性に関する統制の自己証明です。ユーザーの例は、サービス組織を統制する人、サービス組織の顧客、監視当局、ビジネスパートナー、サプライヤー、およびサービス組織の理解者やそれを統制する人です。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml81(para)
+msgid "There are two types of SOC 2 reports:"
+msgstr "SOC 2報告書には二つの種類があります。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml91(para)
+msgid ""
+"Type 2 – report on the fairness of the presentation of management's "
+"description of the service organization's system and the suitability of the "
+"design and operating effectiveness of the controls to achieve the related "
+"control objectives included in the description throughout a specified "
+"period."
+msgstr "Type 2 - サービス組織が統制対象を統制するために使用するシステム、設計の持続性、および運用効率性に関する管理者の説明内容が公正かをレポートします。特定期間を通しての説明も必要です。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml99(para)
+msgid ""
+"For more details see the <link "
+"href=\"http://www.aicpa.org/InterestAreas/FRC/AssuranceAdvisoryServices/Pages/AICPASOC2Report.aspx\">AICPA"
+" Report on Controls at a Service Organization Relevant to Security, "
+"Availability, Processing Integrity, Confidentiality or Privacy</link>."
+msgstr "詳細は<link href=\"http://www.aicpa.org/InterestAreas/FRC/AssuranceAdvisoryServices/Pages/AICPASOC2Report.aspx\">AICPA Report on Controls at a Service Organization Relevant to Security, Availability, Processing Integrity, Confidentiality or Privacy</link>を参照してください。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml108(title)
+msgid "SOC 3"
+msgstr "SOC 3"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml109(para)
+msgid ""
+"Service Organization Controls (SOC) 3 is a trust services report for service"
+" organizations. These reports are designed to meet the needs of users who "
+"want assurance on the controls at a service organization related to "
+"security, availability, processing integrity, confidentiality, or privacy "
+"but do not have the need for or the knowledge necessary to make effective "
+"use of a SOC 2 Report. These reports are prepared using the AICPA/Canadian "
+"Institute of Chartered Accountants (CICA) Trust Services Principles, "
+"Criteria, and Illustrations for Security, Availability, Processing "
+"Integrity, Confidentiality, and Privacy. Because they are general use "
+"reports, SOC 3 Reports can be freely distributed or posted on a website as a"
+" seal."
+msgstr "Service Organization Controls (SOC) 3はサービス提供組織のための公的なサービス報告書です。これらのレポートはサービス組織のセキュリティ、可用性、処理の完全性、機密性、またはプライバシーに関する統制の保証を求めるユーザーニーズを満たすためのレポートです。ただし、SOC 2報告書ほどの情報は必要ありません。SOC 3報告書はAICPA/Canadian Institute of Chartered Accountants (CICA)のTrust Services Principles, Criteria, and Illustrations for Security, Availability, Processing Integrity, Confidentiality, and Privacyをもって作成されています。SOC 3は一般的に使われる報告書であり、Webサイト上で証明書として自由に配布できます。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml121(para)
+msgid ""
+"For more details see the <link "
+"href=\"http://www.aicpa.org/InterestAreas/FRC/AssuranceAdvisoryServices/Pages/AICPASOC3Report.aspx\">AICPA"
+" Trust Services Report for Service Organizations</link>."
+msgstr "詳細は<link href=\"http://www.aicpa.org/InterestAreas/FRC/AssuranceAdvisoryServices/Pages/AICPASOC3Report.aspx\">AICPA Trust Services Report for Service Organizations</link>を参照してください。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml128(title)
+msgid "ISO 27001/2"
+msgstr "ISO 27001/2"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml129(para)
+msgid ""
+"The ISO/IEC 27001/2 standards replace BS7799-2, and are specifications for "
+"an Information Security Management System (ISMS). An ISMS is a comprehensive"
+" set of policies and processes that an organization creates and maintains to"
+" manage risk to information assets. These risks are based upon the "
+"confidentiality, integrity, and availability (CIA) of user information. The "
+"CIA security triad has been used as a foundation for much of the chapters in"
+" this book."
+msgstr "ISO/IEC 27001/2はBS7799-2の後継標準で、Information Security Management System (ISMS)の要件です。ISMSは組織が情報資産のリスクを管理するために作成、維持する、ポリシーとプロセスの包括的なセットです。それらのリスクはユーザー情報のConfidentiality - 機密性、Integrity - 完全性、および Availability - 可用性 (CIA)に深く関係しています。CIAセキュリティの三要素は、このガイドの多くの章で基本となっています。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml137(para)
+msgid ""
+"For more details see <link href=\"http://www.27000.org/iso-27001.htm\">ISO "
+"27001</link>."
+msgstr "詳細は<link href=\"http://www.27000.org/iso-27001.htm\">ISO 27001</link>を参照してください。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml143(title)
+msgid "HIPAA / HITECH"
+msgstr "HIPAA / HITECH"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml144(para)
+msgid ""
+"The Health Insurance Portability and Accountability Act (HIPAA) is a United "
+"States congressional act that governs the collection, storage, use and "
+"destruction of patient health records. The act states that Protected Health "
+"Information (PHI) must be rendered \"unusable, unreadable, or "
+"indecipherable\" to unauthorized persons and that encryption for data 'at-"
+"rest' and 'inflight' should be addressed."
+msgstr "Health Insurance Portability and Accountability Act (HIPAA)は米国の健康保険における可搬性と責任に関する法律で、カルテ情報の収集、保存、および廃棄に関するルールを定めています。この法律は、保護医療情報 (Protected Health Information, PHI)は、権限のない人が\"利用できない、読めない、複合できない\"ように変換されなければいけないこと、また、データが保存中でも、処理中でも、暗号化するべきであることに言及しています。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml151(para)
+msgid ""
+"HIPAA is not a certification, rather a guide for protecting healthcare data."
+" Similar to the PCI-DSS, the most important issues with both PCI and HIPPA "
+"is that a breach of credit card information, and health data, does not "
+"occur. In the instance of a breach the cloud provider will be scrutinized "
+"for compliance with PCI and HIPPA controls. If proven compliant, the "
+"provider can be expected to immediately implement remedial controls, breach "
+"notification responsibilities, and significant expenditure on additional "
+"compliance activities. If not compliant, the cloud provider can expect on-"
+"site audit teams, fines, potential loss of merchant ID (PCI), and massive "
+"reputation impact."
+msgstr "HIPPAは認証ではなく、カルテ情報の保護に関するガイドラインです。PCI-DSSと似ています。PCIとHIPAAの両方でもっとも重要な課題は、クレジットカード情報とカルテ情報が流出しないようにすることです。クラウドプロバイダーによる流出があった場合、PCIとHIPAAの統制下において検査されます。その内容が遵守に足るものであれば、そのプロバイダーはすみやかに是正措置の実行と情報流出の通知、およびコンプライアンス活動予算の大幅な追加を期待されます。もし足るものでなければ、現地での査察、罰金、merchant ID (PCI)の失効、および評判に大きな傷がつくことが予想されます。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml163(para)
+msgid ""
+"Users or organizations that possess PHI must support HIPAA requirements and "
+"are HIPAA covered entities. If an entity intends to use a service, or in "
+"this case, an OpenStack cloud that might use, store or have access to that "
+"PHI, then a Business Associate Agreement must be signed. The BAA is a "
+"contract between the HIPAA covered entity and the OpenStack service provider"
+" that requires the provider to handle that PHI in accordance with HIPAA "
+"requirements. If the service provider does not handle the PHI, such as with "
+"security controls and hardening, then they are subject to HIPAA fines and "
+"penalties."
+msgstr "カルテ情報を所有するユーザーや組織はHIPPAの要件をサポートし、HIPAA対象事業者となる必要があります。もしこの事業者がサービスを、この場合は対象のOpenStackクラウドがカルテ情報を利用、保存、アクセスしうるのであれば、HIPAA Business Associate Agreement - BAAの締結が必要です。BAAはHIPAA対象事業者と、HIPAA要件に従ってカルテ情報を扱っているOpenStackサービスプロバイダーの間で締結されます。もしサービスプロバイダーがセキュリティ統制、強化を怠るなど、カルテ情報を要件通りに扱っていなければHIPAAの罰金や罰則が適用されることがあります。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml174(para)
+msgid ""
+"OpenStack architects interpret and respond to HIPAA statements, with data "
+"encryption remaining a core practice. Currently this would require any "
+"protected health information contained within an OpenStack deployment to be "
+"encrypted with industry standard encryption algorithms. Potential future "
+"OpenStack projects such as object encryption will facilitate HIPAA "
+"guidelines for compliance with the act."
+msgstr "OpenStackアーキテクトはHIPAAの条項を解釈し、対応します。データ暗号化はその中核となる活動です。現在、OpenStack環境に保存される、いかなる保護カルテ情報にも暗号化を要求され、業界標準の暗号化アルゴリズムの採用が期待されます。なお、将来予定されている、例えばオブジェクト暗号化などのOpenStackプロジェクトは、法令遵守のためHPAAガイドラインの適用を促進するでしょう。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml181(para)
+msgid ""
+"For more details see the <link href=\"https://www.cms.gov/Regulations-and-"
+"Guidance/HIPAA-Administrative-"
+"Simplification/HIPAAGenInfo/downloads/HIPAALaw.pdf\">Health Insurance "
+"Portability And Accountability Act</link>."
+msgstr "詳細は<link href=\"https://www.cms.gov/Regulations-and-Guidance/HIPAA-Administrative-Simplification/HIPAAGenInfo/downloads/HIPAALaw.pdf\">Health Insurance Portability And Accountability Act</link>を参照してください。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml187(title)
+msgid "PCI-DSS"
+msgstr "PCI-DSS"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml188(para)
+msgid ""
+"The Payment Card Industry Data Security Standard (PCI DSS) is defined by the"
+" Payment Card Industry Standards Council, and created to increase controls "
+"around card holder data to reduce credit card fraud. Annual compliance "
+"validation is assessed by an external Qualified Security Assessor (QSA) who "
+"creates a Report on Compliance (ROC), or by a Self-Assessment Questionnaire "
+"(SAQ) dependent on volume of card-holder transactions."
+msgstr "Payment Card Industry Data Security Standard (PCI DSS)はPayment Card Industry Standards Councilで定義されました。目的は、クレジットカード不正の防止のため、カード所有者情報に関する統制度を向上することです。コンプライアンス検査は年次で、外部のコンプライアンス評価報告書(Report on Compliance, ROC)を作成する認定評価機関 (Qualified Security Assessor, QSA)、もしくは、自己評価問診票(Self-Assessment Questionnaire, SAQ)によって実施されます。これはカード所有者のトランザクション量に依存します。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml196(para)
+msgid ""
+"OpenStack deployments which stores, processes, or transmits payment card "
+"details are in scope for the PCI-DSS. All OpenStack components that are not "
+"properly segmented from systems or networks that handle payment data fall "
+"under the guidelines of the PCI-DSS. Segmentation in the context of PCI-DSS "
+"does not support multi-tenancy, but rather physical separation "
+"(host/network)."
+msgstr "カード情報を保存、処理、転送するOpenStack環境は、PCI-DSSの対象です。カード情報を扱うシステムやネットワークが正しく分離されていないすべてのOpenStackコンポーネントは、PCI-DSSのガイドラインに適合しません。PCI-DSSでいう分離は、マルチ手ナンシーを認めておらず、(サーバーおよびネットワークの)物理的な分離が必要です。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml203(para)
+msgid ""
+"For more details see <link "
+"href=\"https://www.pcisecuritystandards.org/security_standards/\">PCI "
+"security standards</link>."
+msgstr "詳細は<link href=\"https://www.pcisecuritystandards.org/security_standards/\">PCI security standards</link>を参照してください。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml209(title)
+msgid "Government standards"
+msgstr "政府標準"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml212(title)
+msgid "FedRAMP"
+msgstr "FedRAMP"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml213(para)
+msgid ""
+"\"The <link href=\"http://www.fedramp.gov\">Federal Risk and Authorization "
+"Management Program</link> (FedRAMP) is a government-wide program that "
+"provides a standardized approach to security assessment, authorization, and "
+"continuous monitoring for cloud products and services\". NIST 800-53 is the "
+"basis for both FISMA and FedRAMP which mandates security controls "
+"specifically selected to provide protection in cloud environments. FedRAMP "
+"can be extremely intensive from specificity around security controls, and "
+"the volume of documentation required to meet government standards."
+msgstr "\"<link href=\"http://www.fedramp.gov\">Federal Risk and Authorization Management Program</link> (FedRAMP)は米国連邦政府全体のプログラムであり、クラウド製品とサービスのセキュリティ評価、認証、および継続的モニタリングの、標準化された手順を提供します\" NIST 800-53はFISMAとRedRAMPの両方の基礎であり、特にクラウド環境における保護を提供するために選択されたセキュリティ統制を強制します。セキュリティ統制に関する具体性と政府標準を満たすための文書量を、FedRAMPは徹底しています。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml223(para)
+msgid ""
+"For more details see <link "
+"href=\"http://www.gsa.gov/portal/category/102371\">http://www.gsa.gov/portal/category/102371</link>."
+msgstr "詳細は<link href=\"http://www.gsa.gov/portal/category/102371\">http://www.gsa.gov/portal/category/102371</link>を参照してください。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml229(title)
+msgid "ITAR"
+msgstr "ITAR"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml230(para)
+msgid ""
+"The International Traffic in Arms Regulations (ITAR) is a set of United "
+"States government regulations that control the export and import of defense-"
+"related articles and services on the United States Munitions List (USML) and"
+" related technical data. ITAR is often approached by cloud providers as an "
+"\"operational alignment\" rather than a formal certification. This typically"
+" involves implementing a segregated cloud environment following practices "
+"based on the NIST 800-53 framework, as per FISMA requirements, complemented "
+"with additional controls restricting access to \"U.S. Persons\" only and "
+"background screening."
+msgstr "International Traffic in Arms Regulations (ITAR)は米国政府規制の集合であり、米国軍需品リスト(United States Munitions List, USML)と関連技術情報に関係する防衛物品・サービスの輸出入を統制します。ITARは正式な認証というより、\"軍事活動支援\"の位置づけでクラウドプロバイダーから提示されます。この統制は一般的に、NIST 800-53フレームワークにもとづき、分離されたクラウド環境の実装を意味します。FISMA要件により、米国民かつ身元審査された人のみがアクセスできるよう、追加の統制で補完します。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml241(para)
+msgid ""
+"For more details see <link "
+"href=\"http://pmddtc.state.gov/regulations_laws/itar_official.html\">http://pmddtc.state.gov/regulations_laws/itar_official.html</link>."
+msgstr "詳細は<link href=\"http://pmddtc.state.gov/regulations_laws/itar_official.html\">http://pmddtc.state.gov/regulations_laws/itar_official.html</link>を参照してください。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml247(title)
+msgid "FISMA"
+msgstr "FISMA"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml248(para)
+msgid ""
+"The Federal Information Security Management Act requires that government "
+"agencies create a comprehensive plan to implement numerous government "
+"security standards, and was enacted within the E-Government Act of 2002. "
+"FISMA outlines a process, which utilizing multiple NIST publications, "
+"prepares an information system to store and process government data."
+msgstr "米国連邦情報セキュリティマネジメント法 - Federal Information Security Management Act requires、FISMAは、政府機関は多数の政府セキュリティ標準を実装するために、包括的な計画を作成する必要があるとして、2002年 電子政府法 - E-Government Act of 2002 内で制定されました。FISMAは多数のNIST公表文献を活用し、政府のデータを保存、処理する情報システムを作成するためのプロセスを説明しています。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml255(para)
+msgid "This process is broken apart into three primary categories:"
+msgstr "このプロセスは三つの主要カテゴリに分割されています。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml259(para)
+msgid ""
+"<emphasis role=\"bold\">System categorization:</emphasis> The information "
+"system will receive a security category as defined in Federal Information "
+"Processing Standards Publication 199 (FIPS 199). These categories reflect "
+"the potential impact of system compromise."
+msgstr "<emphasis role=\"bold\">システムのカテゴリ分け</emphasis> 情報システムは連邦情報処理規格( Federal Information Processing Standards Publication 199, FIPS 199)で定められたセキュリティカテゴリに分類されます。これらのカテゴリはシステムの情報漏洩の潜在的な影響を反映しています。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml267(para)
+msgid ""
+"<emphasis role=\"bold\">Control selection:</emphasis>Based upon system "
+"security category as defined in FIPS 199, an organization utilizes FIPS 200 "
+"to identify specific security control requirements for the information "
+"system. For example, if a system is categorized as “moderate” a requirement "
+"may be introduced to mandate “secure passwords.”"
+msgstr "<emphasis role=\"bold\">統制の選択</emphasis> FIPS 199で定められたシステムセキュリティのカテゴリにもとづき、組織は情報システムのための特定のセキュリティ統制要求を特定すべく、FIPS 200を活用します 。たとえば、もしシステムが\"中程度\"と分類されているのであれば、安全なパスワードの強制が求められるでしょう。"
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml276(para)
+msgid ""
+"<emphasis role=\"bold\">Control tailoring:</emphasis> Once system security "
+"controls are identified, an OpenStack architect will utilize NIST 800-53 to "
+"extract tailored control selection. For example, specification of what "
+"constitutes a “secure password.”"
+msgstr "<emphasis role=\"bold\">統制の適用</emphasis> システムのセキュリティが特定されれば、OpenStackアーキテクトは選択した統制を適用するために、NIST 800-53を活用します。たとえば、安全なパスワードの構成を仕様化するなど。"
+
+#: ./doc/security-guide/ch065_privacy.xml7(title)
+msgid "Privacy"
+msgstr "プライバシー"
+
+#: ./doc/security-guide/ch065_privacy.xml8(para)
+msgid ""
+"Privacy is an increasingly important element of a compliance program. "
+"Businesses are being held to a higher standard by their customers, who have "
+"increased interest in understanding how their data is treated from a privacy"
+" perspective."
+msgstr "プライバシーはコンプライアンスプログラムの重要な要素になりつつあります。顧客はプライバシーの観点から、データがいかに扱われているか関心を高めており、データを扱う企業はより高い基準を期待されています。"
+
+#: ./doc/security-guide/ch065_privacy.xml9(para)
+msgid ""
+"An OpenStack deployment will likely need to demonstrate compliance with an "
+"organization’s Privacy Policy, with the U.S. – E.U. Safe Harbor framework, "
+"the ISO/IEC 29100:2011 privacy framework or with other privacy-specific "
+"guidelines. In the U.S. the AICPA has <link "
+"href=\"http://www.aicpa.org/interestareas/informationtechnology/resources/privacy/generallyacceptedprivacyprinciples/\">defined"
+" 10 privacy areas of focus</link>, OpenStack deployments within a commercial"
+" environment may desire to attest to some or all of these principles."
+msgstr "OpenStack環境では、組織のプライバシーポリシー、米国 - EU間のセーフハーバーフレームワーク、ISO/IEC 29100:2011 プライバシーフレームワークなど、プライバシー特化ガイドライン遵守の証明を求められることが多いです。米国ではAICPAが<link href=\"http://www.aicpa.org/interestareas/informationtechnology/resources/privacy/generallyacceptedprivacyprinciples/\">重視すべき10のプライバシー項目</link>を公表しており、ビジネス用途のOpenStack環境はそのうちのいくつか、もしくは全原則の立証を期待されます。"
+
+#: ./doc/security-guide/ch065_privacy.xml10(para)
+msgid ""
+"To aid OpenStack architects in the protection of personal data, it is "
+"recommended that OpenStack architects review the NIST publication 800-122, "
+"titled \"<emphasis>Guide to Protecting the Confidentiality of Personally "
+"Identifiable Information (PII)</emphasis>.\" This guide steps through the "
+"process of protecting:"
+msgstr "個人情報の保護に取り組むOpenStackアーキテクトを支援するため、OpenStackアーキテクトには、NIST刊行 800-122 \"<emphasis>Guide to Protecting the Confidentiality of Personally Identifiable Information (PII)</emphasis>.をおすすめします。このガイドは以下を保護するプロセスについて述べています。"
+
+#: ./doc/security-guide/ch065_privacy.xml12(para)
+msgid ""
+"\"<emphasis>any information about an individual maintained by an agency, "
+"including (1) any information that can be used to distinguish or trace an "
+"individual‘s identity, such as name, social security number, date and place "
+"of birth, mother‘s maiden name, or biometric records; and (2) any other "
+"information that is linked or linkable to an individual, such as medical, "
+"educational, financial, and employment information</emphasis>\""
+msgstr "\"<emphasis>政府機関が保有するあらゆる個人情報、(1)個人を特定、追跡しうるあらゆる情報、例えば氏名、社会保障番号、出生年月日、出生地、母の旧姓、生体情報など。および、(2)個人に結びつく、結びつけられるあらゆる情報、例えば医療、教育、金融、雇用情報など</emphasis>\""
+
+#: ./doc/security-guide/ch065_privacy.xml14(para)
+msgid ""
+"Comprehensive privacy management requires significant preparation, thought "
+"and investment. Additional complications are introduced when building global"
+" OpenStack clouds, for example navigating the differences between U.S. and "
+"more restrictive E.U. privacy laws. In addition, extra care needs to be "
+"taken when dealing with sensitive PII that may include information such as "
+"credit card numbers or medical records. This sensitive data is not only "
+"subject to privacy laws but also regulatory and governmental regulations. By"
+" deferring to established best practices, including those published by "
+"governments, a holistic privacy management policy may be created and "
+"practiced for OpenStack deployments."
+msgstr "包括的なプライバシー管理には、十分な準備、考慮と投資が必要です。また、グローバルなOpenStackクラウドの構築時には、さらなる複雑さに気づくでしょう。米国および、それより厳しいEUのプライバシー法令の違いが良い例です。加えて、クレジットカード番号や医療情報など、機密性の高い個人情報を扱う場合にはさらなる注意が必要です。これら機密性の高い情報はプライバシー法令だけでなく、監視当局や政府規制にも関連します。政府によって発行されたものなど、ベストプラクティスに従うことで、OpenStack環境向けの総合的なプライバシー管理ポリシーが確立、実践されていくでしょう。"
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml12(title)
+msgid "Networking services security best practices"
+msgstr "Networking サービス セキュリティベストプラクティス"
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml13(para)
+msgid ""
+"This section discusses OpenStack Networking configuration best practices as "
+"they apply to tenant network security within your OpenStack deployment."
+msgstr "この章では、あなたの OpenStack デプロイの中でテナントネットワークセキュリティを適用する為に、OpenStack Networking の設定のベストプラクティスについて議論します。"
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml15(title)
+msgid "Tenant network services workflow"
+msgstr "テナントネットワークサービスのワークフロー"
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml16(para)
+msgid ""
+"OpenStack Networking provides users real self services of network resources "
+"and configurations. It is important that cloud architects and operators "
+"evaluate their design use cases in providing users the ability to create, "
+"update, and destroy available network resources."
+msgstr "OpenStack Networking は、ネットワークリソースと設定の本物のセルフサービスをユーザに提供します。クラウドアーキテクトとオペレータが、利用可能なネットワークリソースの作成・更新・削除機能をユーザに提供する際の彼らの設計ユースケースを評価する事は重要です。"
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml19(title)
+msgid "Networking resource policy engine"
+msgstr "Networking リソースポリシーエンジン"
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml20(para)
+msgid ""
+"A policy engine and its configuration file, "
+"<filename>policy.json</filename>, within OpenStack Networking provides a "
+"method to provide finer grained authorization of users on tenant networking "
+"methods and objects. It is important that cloud architects and operators "
+"evaluate their design and use cases in providing users and tenants the "
+"ability to create, update, and destroy available network resources as it has"
+" a tangible effect on tenant network availability, network security, and "
+"overall OpenStack security. For a more detailed explanation of OpenStack "
+"Networking policy definition, please refer to the <link "
+"href=\"http://docs.openstack.org/admin-guide-"
+"cloud/content/section_networking_auth.html\">Authentication and "
+"authorization section</link> in the <citetitle>OpenStack Cloud Administrator"
+" Guide</citetitle>."
+msgstr "OpenStack Networking 中のポリシーエンジンとその設定ファイル（<filename>policy.json</filename>）は、テナントネットワークメソッドとオブジェクト上のユーザのきめ細かな許可を提供する方法を提供します。クラウドアーキテクトとオペレータが、ユーザとテナントに利用可能なネットワークリソースを作成・交信・削除する機能を提供するにあたって、かれらの設計とユースケースを評価する事は重要です。なぜなら、テナントネットワークの可用性、ネットワークセキュリティ、全般的な OpenStack セキュリティ上でこれらが実際の効果を持つからです。OpenStack Networking ポリシー定義のより詳細な説明は、<citetitle>OpenStack クラウド管理者ガイド</citetitle> 中の <link href=\"http://docs.openstack.org/admin-guide-cloud/content/section_networking_auth.html\">認証と認可の章</link>を参照して下さい。"
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml34(para)
+msgid ""
+"It is important to review the default networking resource policy and modify "
+"the policy appropriately for your security posture."
+msgstr "デフォルトの Networking リソースポリシーをレビューする事と、あなたのセキュリティ姿勢に向けてポリシーを適切に修正する事は重要です。"
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml37(para)
+msgid ""
+"If your deployment of OpenStack provides multiple external access points "
+"into different security domains it is important that you limit the tenant's "
+"ability to attach multiple vNICs to multiple external access pointsthis "
+"would bridge these security domains and could lead to unforeseen security "
+"compromise. It is possible mitigate this risk by utilizing the host "
+"aggregates functionality provided by OpenStack Compute or through splitting "
+"the tenant VMs into multiple tenant projects with different virtual network "
+"configurations."
+msgstr "あなたの OpenStack のデプロイが異なるセキュリティドメインに向けて複数の外部アクセスポイントを提供する場合、複数の外部アクセスポイントへ複数の仮想NICをアタッチするテナントの機能を制限する事は重要です。これは、これらのセキュリティドメインのブリッジになり、思いがけないセキュリティの妥協を導くかも知れません。OpenStack Compute が提供するホストアグリゲート機能の活用や、異なる仮想ネットワーク設定を持つ複数のテナントプロジェクトにテナントVMを分割する事で、リスクを緩和する事が可能です。"
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml48(title)
+msgid "Security groups"
+msgstr "セキュリティグループ"
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml49(para)
+msgid ""
+"The OpenStack Networking Service provides security group functionality using"
+" a mechanism that is more flexible and powerful than the security group "
+"capabilities built into OpenStack Compute. Thus, when using OpenStack "
+"Networking, <filename>nova.conf</filename> should always disable built-in "
+"security groups and proxy all security group calls to the OpenStack "
+"Networking API. Failure to do so will result in conflicting security "
+"policies being simultaneously applied by both services. To proxy security "
+"groups to OpenStack Networking, use the following configuration values:"
+msgstr "OpenStack Networking サービスは、OpenStack Compute 上に構築されたセキュリティグループ機能より柔軟で協力な機能を用いたセキュリティグループ機能を提供します。このように、OpenStack Networking を用いる場合、<filename>nova.conf</filename> は常にビルトインのセキュリティグループを無効化し、全てのセキュリティグループ要求を OpenStack Networking API にプロキシする必要があります。これを怠った場合、セキュリティポリシーが両サービスに同時に適用されて衝突を起こす結果となります。OpenStack Networking にセキュリティグループをプロキシする為に、以下の設定値を用いて下さい。"
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml61(para)
+msgid ""
+"<option>firewall_driver</option> must be set to "
+"<literal>nova.virt.firewall.NoopFirewallDriver</literal> so that <systemitem"
+" class=\"service\">nova-compute</systemitem> does not perform iptables-based"
+" filtering itself."
+msgstr "<option>firewall_driver</option> は、<systemitem class=\"service\">nova-compute</systemitem> が自身で iptables ベースのフィルタリングを実行しないよう、<literal>nova.virt.firewall.NoopFirewallDriver</literal> に設定しなければなりません。"
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml67(para)
+msgid ""
+"<option>security_group_api</option> must be set to "
+"<literal>neutron</literal> so that all security group requests are proxied "
+"to the OpenStack Networking service."
+msgstr "<option>security_group_api</option> は、全てのセキュリティグループ要求が OpenStack Networking サービスを経由するよう、<literal>neutron</literal> に設定しなければなりません。"
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml73(para)
+msgid ""
+"Security groups and security group rules allow administrators and tenants "
+"the ability to specify the type of traffic and direction (ingress/egress) "
+"that is allowed to pass through a virtual interface port. A security group "
+"is a container for security group rules. When a virtual interface port is "
+"created in OpenStack Networking it is associated with a security group. If a"
+" security group is not specified, the port will be associated with a "
+"'default' security group. By default this group will drop all ingress "
+"traffic and allow all egress. Rules can be added to this group in order to "
+"change the behaviour."
+msgstr "セキュリティグループとセキュリティグループルールは、管理者とテナントが仮想インターフェースポートの通過を許可する通信のタイプと通信方向 (内向き／外向き) を指定できるようにしています。セキュリティグループはセキュリティグループルールの入れ物です。OpenStack Networking 中で仮想インターフェースポートが作成された場合、ポートはセキュリティグループに紐付けられます。セキュリティグループが指定されない場合、ポートは「default」セキュリティグループに紐付けられます。デフォルトでは、このグループは内向きの通信を全てドロップし、外向きの通信を全て許可します。挙動を変える為に、このグループにルールを追加する事が出来ます。"
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml74(para)
+msgid ""
+"When using the security group API through OpenStack Compute, security groups"
+" are applied to all virtual interface ports on an instance. The reason for "
+"this is that OpenStack Compute security group APIs are instance based and "
+"not virtual interface port based as OpenStack Networking."
+msgstr "OpenStack Compute のセキュリティグループ API を使用する場合、セキュリティグループは１インスタンス上の全仮想インターフェースポートに適用されます。この理由は、OpenStack Compute のセキュリティグループ API がインスタンスベースであり、OpenStack Networking のような仮想インターフェースポートベースではないからです。"
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml77(title)
+msgid "Quotas"
+msgstr "クォータ"
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml79(para)
+msgid ""
+"Quotas provide the ability to limit the number of network resources "
+"available to tenants. You can enforce default quotas for all tenants. The "
+"<filename>/etc/neutron/neutron.conf</filename> includes these options for "
+"quota:"
+msgstr "クォータは、テナントに対して利用可能なネットワークリソース数を制限する機能を提供します。全てのテナントに対してデフォルトのクォータを強制する事が出来ます。<filename>/etc/neutron/neutron.conf</filename> にクォータに関するこれらのオプションがあります。"
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml108(para)
+msgid ""
+"OpenStack Networking also supports per-tenant quotas limit through a quota "
+"extension API. To enable per-tenant quotas, you must set the "
+"<literal>quota_driver</literal> option in <filename>neutron.conf</filename>."
+msgstr "OpenStack Networking はまた、クォータ拡張 API 経由で、テナント単位のクォータをサポートしています。テナント単位クォータを有効にするためには、<filename>neutron.conf</filename> 中の <literal>quota_driver</literal> を設定する必要があります。"
+
+#: ./doc/security-guide/ch037_risks.xml8(title)
+msgid "Message queuing architecture"
+msgstr "メッセージキューイングアーキテクチャー"
+
+#: ./doc/security-guide/ch037_risks.xml9(para)
+msgid ""
+"Message queuing services facilitate inter-process communication in "
+"OpenStack. OpenStack supports these message queuing service back ends:"
+msgstr "メッセージキューイングサービスは、OpenStack 内におけるプロセス間通信を担います。OpenStack は次のキューイングサービスをサポートしています。"
+
+#: ./doc/security-guide/ch037_risks.xml14(para)
+msgid "RabbitMQ"
+msgstr "RabbitMQ"
+
+#: ./doc/security-guide/ch037_risks.xml17(para)
+msgid "Qpid"
+msgstr "Qpid"
+
+#: ./doc/security-guide/ch037_risks.xml20(para)
+msgid "ZeroMQ or 0MQ"
+msgstr "ZeroMQ、または、0MQ"
+
+#: ./doc/security-guide/ch037_risks.xml23(para)
+msgid ""
+"Both RabbitMQ and Qpid are Advanced Message Queuing Protocol (AMQP) "
+"frameworks, which provide message queues for peer-to-peer communication. "
+"Queue implementations are typically deployed as a centralized or "
+"decentralized pool of queue servers. ZeroMQ provides direct peer-to-peer "
+"communication through TCP sockets."
+msgstr "RabbitMQ と Qpid は両方とも、Advanced Message Queuing Protocol (AMQP)  フレームワークであり、ピアツーピア通信にメッセージキューを提供する仕組みです。\nキューの実装は通常、キューサーバのプールを集中型か分散型で展開します。\nZeroMQ はピア間の通信に直接 TCP ソケットを使うところが異なっています。"
+
+#: ./doc/security-guide/ch037_risks.xml29(para)
+msgid ""
+"Message queues effectively facilitate command and control functions across "
+"OpenStack deployments. Once access to the queue is permitted no further "
+"authorization checks are performed. Services accessible through the queue do"
+" validate the contexts and tokens within the actual message payload. "
+"However, you must note the expiration date of the token because tokens are "
+"potentially re-playable and can authorize other services in the "
+"infrastructure."
+msgstr "メッセージキューは、OpenStack 内における指揮系統の機能を担います。一度キューへのアクセスが許可されると、その後の認証チェックは行われません。キューを使用するサービスがメッセージペイロード内のコンテキストとトークンのチェックを行います。\nとはいえ、トークンの期限切れには注意を払う必要があります。これは、トークンが潜在的に再発行可能であり、インフラストラクチャ内の他のサービスを許可する可能性があるためです。"
+
+#: ./doc/security-guide/ch037_risks.xml37(para)
+msgid ""
+"OpenStack does not support message-level confidence, such as message "
+"signing. Consequently, you must secure and authenticate the message "
+"transport itself. For high-availability (HA) configurations, you must "
+"perform queue-to-queue authentication and encryption."
+msgstr "OpenStack は、メッセージへの署名のようなメッセージレベルのコンフィデンスはサポートしていません。そのため、メッセージの通信路そのものがセキュア化され、かつ、キューサーバーへのアクセスの際に認証が行なわれる必要があります。\nまた、HA 設定の際には、キュー間の認証と暗号化も同様に実施するべきです。"
+
+#: ./doc/security-guide/ch037_risks.xml42(para)
+msgid ""
+"With ZeroMQ messaging, IPC sockets are used on individual machines. Because "
+"these sockets are vulnerable to attack, ensure that the cloud operator has "
+"secured them."
+msgstr "ZeroMQ メッセージングでは、IPC ソケットが各マシンで使用されます。これらのソケットは管理者がセキュア化しない限り、ローカルメッセージインジェクションやスヌーピングの攻撃に脆弱な可能性があります。"
+
 #. When image changes, this message will be marked fuzzy or untranslated for
 #. you.
 #. It doesn't matter what you translate it to: it's not used at all.
@@ -348,6 +1836,2972 @@ msgid ""
 "href=\"http://wiki.openstack.org/Documentation/HowTo\">http://wiki.openstack.org/Documentation/HowTo</link>."
 msgstr "OpenStack ドキュメントに貢献する方法について: <link href=\"http://wiki.openstack.org/Documentation/HowTo\">http://wiki.openstack.org/Documentation/HowTo</link>"
 
+#: ./doc/security-guide/ch012_configuration-management.xml8(title)
+msgid "Continuous systems management"
+msgstr "継続的なシステム管理"
+
+#: ./doc/security-guide/ch012_configuration-management.xml9(para)
+msgid ""
+"A cloud will always have bugs. Some of these will be security problems. For "
+"this reason, it is critically important to be prepared to apply security "
+"updates and general software updates. This involves smart use of "
+"configuration management tools, which are discussed below. This also "
+"involves knowing when an upgrade is necessary."
+msgstr "クラウドには必ずバグがあります。その中にはセキュリティの問題も含まれています。このような理由から、セキュリティ更新や一般的なソフトウェア更新の適用準備を行うことが極めて重要です。例えば、構成管理ツールを賢く利用していくことになります。これについては以下で説明しています。また、アップグレードが必要な時期を把握することも重要です。"
+
+#: ./doc/security-guide/ch012_configuration-management.xml17(para)
+msgid ""
+"For announcements regarding security relevant changes, subscribe to the "
+"<link href=\"http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-"
+"announce\">OpenStack Announce mailing list</link>. The security "
+"notifications are also posted through the downstream packages for example "
+"through Linux distributions that you may be subscribed to as part of the "
+"package updates."
+msgstr "セキュリティ関連の変更に関するお知らせは、<link href=\"http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-announce\">OpenStack Announce mailing list</link> を購読してください。このセキュリティの通知は、Linux ディストリビューションなどのダウンストリームのパッケージでも掲載されます。これはパッケージ更新の一部として購読しているかもしれません。"
+
+#: ./doc/security-guide/ch012_configuration-management.xml24(para)
+msgid ""
+"The OpenStack components are only a small fraction of the software in a "
+"cloud. It is important to keep up to date with all of these other "
+"components, too. While the specific data sources will be deployment "
+"specific, the key idea is to ensure that a cloud administrator subscribes to"
+" the necessary mailing lists for receiving notification of any related "
+"security updates. Often this is as simple as tracking an upstream Linux "
+"distribution."
+msgstr "OpenStack のコンポーネントは、クラウドにあるソフトウェアのごく一部です。これらだけではなく他のコンポーネントすべてを最新の状態に保つことが重要です。データソースはそれぞれデプロイメント固有となりますが、クラウド管理者は必要なメーリングリストを購読して、関連するセキュリティ更新の通知を受信できるようにすることが重要です。通常、Linux のアップストリームディストリビューションをチェックするのと同じくらいシンプルです。"
+
+#: ./doc/security-guide/ch012_configuration-management.xml36(para)
+msgid ""
+"OpenStack Security Advisories (OSSA) are created by the OpenStack "
+"Vulnerability Management Team (VMT). They pertain to security holes in core "
+"OpenStack services. More information on the VMT can be found here: <link "
+"href=\"https://wiki.openstack.org/wiki/Vulnerability_Management\">https://wiki.openstack.org/wiki/Vulnerability_Management</link>"
+msgstr "OpenStack セキュリティアドバイザリ (OSSA: OpenStack Security Advisories) は、OpenStack 脆弱性管理チーム (VMT: Vulnerability Management Team) が作成しています。コアとなる OpenStack サービスのセキュリティホールに関連するものです。VMT に関する詳細情報は、<link href=\"https://wiki.openstack.org/wiki/Vulnerability_Management\">https://wiki.openstack.org/wiki/Vulnerability_Management</link> を参照してください。"
+
+#: ./doc/security-guide/ch012_configuration-management.xml44(para)
+msgid ""
+"OpenStack Security Notes (OSSN) were created by the OpenStack Security Group"
+" (OSSG) to support the work of the VMT. OSSN address issues in supporting "
+"software and common deployment configurations. They're referenced throughout"
+" this guide. Security Notes are archived at <link "
+"href=\"https://launchpad.net/ossn/\">https://launchpad.net/ossn/</link>"
+msgstr "OpenStack セキュリティノート (OSSN: OpenStack Security Notes) は、VMT の作業をサポートする OpenStack セキュリティグループ (OSSG: OpenStack Security Group) が 作成しています。OSSN はソフトウェアや一般的なデプロイメント設定のサポートにおける問題に対応しています。本書でも OSSN については全体的に参照しています。セキュリティノートは <link href=\"https://launchpad.net/ossn/\">https://launchpad.net/ossn/</link> でアーカイブされています。"
+
+#: ./doc/security-guide/ch012_configuration-management.xml33(para)
+msgid ""
+"OpenStack releases security information through two channels. "
+"<placeholder-1/>"
+msgstr "OpenStack は 2 つのチャネルからセキュリティ情報を発信しています。 <placeholder-1/>"
+
+#: ./doc/security-guide/ch012_configuration-management.xml56(title)
+msgid "Triage"
+msgstr "トリアージ"
+
+#: ./doc/security-guide/ch012_configuration-management.xml57(para)
+msgid ""
+"After you are notified of a security update, the next step is to determine "
+"how critical this update is to a given cloud deployment. In this case, it is"
+" useful to have a pre-defined policy. Existing vulnerability rating systems "
+"such as the common vulnerability scoring system (CVSS) v2 do not properly "
+"account for cloud deployments."
+msgstr "セキュリティ更新を通知された後、次のステップとして、指定のクラウドデプロイメントにとって、この更新がどの程度重要かを判断します。このような場合、ポリシーを事前定義しておくと便利です。共通脆弱性評価システム (CVSS) v2 などの既存の脆弱性評価システムは、クラウドデプロイメントに正しく対応していません。"
+
+#: ./doc/security-guide/ch012_configuration-management.xml63(para)
+msgid ""
+"In this example we introduce a scoring matrix that places vulnerabilities in"
+" three categories: Privilege Escalation, Denial of Service and Information "
+"Disclosure. Understanding the type of vulnerability and where it occurs in "
+"your infrastructure will enable you to make reasoned response decisions."
+msgstr "以下の例では、権限昇格、DoS (サービス妨害)、情報開示の 3 つのカテゴリーに脆弱性を分類した評価一覧表を紹介しています。脆弱性の種類やインフラストラクチャー内での発生箇所を理解することで、裏付けに基いた対応意思決定を下すことができます。"
+
+#: ./doc/security-guide/ch012_configuration-management.xml69(para)
+msgid ""
+"Privilege Escalation describes the ability of a user to act with the "
+"privileges of some other user in a system, bypassing appropriate "
+"authorization checks. For example, a standard Linux user running code or "
+"performing an operation that allows them to conduct further operations with "
+"the privileges of the root users on the system."
+msgstr "権限昇格とは、適切な認証チェックをすり抜けてシステム内の他のユーザーの権限を行使するユーザーの能力のことを指します。例えば、標準の Linux ユーザーがシステム上の root ユーザーの権限で自分の権限以上の操作を可能にするオペレーションを実行したり、コードを実行したりするなどです。"
+
+#: ./doc/security-guide/ch012_configuration-management.xml75(para)
+msgid ""
+"Denial of Service refers to an exploited vulnerability that may cause "
+"service or system disruption. This includes both distributed attacks to "
+"overwhelm network resources, and single-user attacks that are typically "
+"caused through resource allocation bugs or input induced system failure "
+"flaws."
+msgstr "サービス妨害 (DoS) とは、サービスやシステムの中断を引き起こす脆弱性を悪用することを指します。これには、ネットワークリソースを大量に使用する分散型攻撃や、リソース割り当てのバグや誘導型でのシステム障害の問題などで一般的に引き起こされるシングルユーザー攻撃の両方が含まれます。"
+
+#: ./doc/security-guide/ch012_configuration-management.xml80(para)
+msgid ""
+"Information Disclosure vulnerabilities reveal information about your system "
+"or operations. These vulnerabilities range from debugging information "
+"disclosure, to exposure of critical security data, such as authentication "
+"credentials and passwords."
+msgstr "情報開示の脆弱性は、システムや操作の情報を公開します。これらの脆弱性は、情報開示のデバッグから認証情報やパスワードなどの重要なセキュリティデータの公開などが当てはまります。"
+
+#: ./doc/security-guide/ch012_configuration-management.xml96(emphasis)
+msgid "Attacker position / Privilege level"
+msgstr "攻撃者の位置付け/権限レベル"
+
+#: ./doc/security-guide/ch012_configuration-management.xml102(emphasis)
+msgid "External"
+msgstr "外部"
+
+#: ./doc/security-guide/ch012_configuration-management.xml103(emphasis)
+msgid "Cloud user"
+msgstr "クラウドユーザー"
+
+#: ./doc/security-guide/ch012_configuration-management.xml105(emphasis)
+msgid "Cloud admin"
+msgstr "クラウドの管理者"
+
+#: ./doc/security-guide/ch012_configuration-management.xml107(emphasis)
+msgid "Control plane"
+msgstr "制御プレーン"
+
+#: ./doc/security-guide/ch012_configuration-management.xml111(emphasis)
+msgid "Privilege elevation (3 levels)"
+msgstr "権限昇格 (3 つのレベル)"
+
+#: ./doc/security-guide/ch012_configuration-management.xml113(para)
+#: ./doc/security-guide/ch012_configuration-management.xml121(para)
+#: ./doc/security-guide/ch012_configuration-management.xml122(para)
+#: ./doc/security-guide/ch012_configuration-management.xml129(para)
+#: ./doc/security-guide/ch012_configuration-management.xml130(para)
+#: ./doc/security-guide/ch012_configuration-management.xml131(para)
+msgid "Critical"
+msgstr "重要"
+
+#: ./doc/security-guide/ch012_configuration-management.xml114(para)
+#: ./doc/security-guide/ch012_configuration-management.xml115(para)
+#: ./doc/security-guide/ch012_configuration-management.xml116(para)
+#: ./doc/security-guide/ch012_configuration-management.xml123(para)
+#: ./doc/security-guide/ch012_configuration-management.xml124(para)
+#: ./doc/security-guide/ch012_configuration-management.xml132(para)
+msgid "n/a"
+msgstr "なし"
+
+#: ./doc/security-guide/ch012_configuration-management.xml119(emphasis)
+msgid "Privilege elevation (2 levels)"
+msgstr "権限昇格 (2 つのレベル)"
+
+#: ./doc/security-guide/ch012_configuration-management.xml127(emphasis)
+msgid "Privilege elevation (1 level)"
+msgstr "権限昇格 (1つのレベル)"
+
+#: ./doc/security-guide/ch012_configuration-management.xml135(emphasis)
+msgid "Denial of service"
+msgstr "サービス妨害 (DoS)"
+
+#: ./doc/security-guide/ch012_configuration-management.xml137(para)
+msgid "High"
+msgstr "高"
+
+#: ./doc/security-guide/ch012_configuration-management.xml138(para)
+msgid "Medium"
+msgstr "中"
+
+#: ./doc/security-guide/ch012_configuration-management.xml139(para)
+#: ./doc/security-guide/ch012_configuration-management.xml140(para)
+#: ./doc/security-guide/ch012_configuration-management.xml148(para)
+msgid "Low"
+msgstr "低"
+
+#: ./doc/security-guide/ch012_configuration-management.xml143(emphasis)
+msgid "Information disclosure"
+msgstr "情報開示"
+
+#: ./doc/security-guide/ch012_configuration-management.xml145(para)
+#: ./doc/security-guide/ch012_configuration-management.xml146(para)
+msgid "Critical / high"
+msgstr "重要/高"
+
+#: ./doc/security-guide/ch012_configuration-management.xml147(para)
+msgid "Medium / low"
+msgstr "中/低"
+
+#: ./doc/security-guide/ch012_configuration-management.xml152(para)
+msgid ""
+"This table illustrates a generic approach to measuring the impact of a "
+"vulnerability based on where it occurs in your deployment and the effect. "
+"For example, a single level privilege escalation on a Compute API node "
+"potentially allows a standard user of the API to escalate to have the same "
+"privileges as the root user on the node."
+msgstr "この表は、デプロイメントの発生箇所や影響をもとに脆弱性から受ける影響レベルを測定するための一般的な手法を示しています。例えば、Compute API ノードで権限レベルを 1 つ昇格すると、API の標準ユーザーはこのノード上の root ユーザーと同等の権限にまで昇格することが可能です。"
+
+#: ./doc/security-guide/ch012_configuration-management.xml158(para)
+msgid ""
+"We suggest that cloud administrators use this table as a model to help "
+"define which actions to take for the various security levels. For example, a"
+" critical-level security update might require the cloud to be upgraded on a "
+"specified time line, whereas a low-level update might be more relaxed."
+msgstr "クラウド管理者が、さまざまなセキュリティレベルに合わせて実行するアクションを定義する役に立てるために、この表をモデルとして使用することを推奨します。例えば、レベルが「重要」であるセキュリティ更新では、指定のスケジュールでクラウドのアップグレードが必要となる可能性がありますが、レベルが「低」の更新ではそこまで厳しくないでしょう。"
+
+#: ./doc/security-guide/ch012_configuration-management.xml165(title)
+msgid "Testing the updates"
+msgstr "更新のテスト"
+
+#: ./doc/security-guide/ch012_configuration-management.xml166(para)
+msgid ""
+"You should test any update before you deploy it in a production environment."
+" Typically this requires having a separate test cloud setup that first "
+"receives the update. This cloud should be as close to the production cloud "
+"as possible, in terms of software and hardware. Updates should be tested "
+"thoroughly in terms of performance impact, stability, application impact, "
+"and more. Especially important is to verify that the problem theoretically "
+"addressed by the update, such as a specific vulnerability, is actually "
+"fixed."
+msgstr "何らかの更新を本番環境にデプロイする前に、それらをテストするようにしてください。一般的に、更新を最初に受信するテスト用のクラウド設定が別途必要になります。このクラウドのソフトウェアやハードウェアはできるだけ実稼働クラウドと同じ環境にする必要があります。パフォーマンスの影響、安定性、アプリケーションへの影響など、更新全体をテストする必要があります。特に重要なのは、更新で理論上対応されている問題 (例: 特定の脆弱性) が実際に修正されているかどうかを確認することです。"
+
+#: ./doc/security-guide/ch012_configuration-management.xml177(title)
+msgid "Deploying the updates"
+msgstr "更新のデプロイ"
+
+#: ./doc/security-guide/ch012_configuration-management.xml178(para)
+msgid ""
+"Once the updates are fully tested, they can be deployed to the production "
+"environment. This deployment should be fully automated using the "
+"configuration management tools described below."
+msgstr "更新の完全なテストが終了すると、実稼働環境にデプロイすることができます。このデプロイメントは、以下に記載の構成管理ツールで完全に自動的に行われます。"
+
+#: ./doc/security-guide/ch012_configuration-management.xml185(title)
+msgid "Configuration management"
+msgstr "設定管理"
+
+#: ./doc/security-guide/ch012_configuration-management.xml186(para)
+msgid ""
+"A production quality cloud should always use tools to automate configuration"
+" and deployment. This eliminates human error, and allows the cloud to scale "
+"much more rapidly. Automation also helps with continuous integration and "
+"testing."
+msgstr "実稼働環境の品質を持つクラウドは設定とデプロイメントの自動化ツールを必ず使用しています。こうすることで、人的ミスをなくし、クラウドの迅速なスケールアウトが可能になります。自動化により、継続的な統合やテストが行いやすくなります。"
+
+#: ./doc/security-guide/ch012_configuration-management.xml191(para)
+msgid ""
+"When building an OpenStack cloud it is strongly recommended to approach your"
+" design and implementation with a configuration management tool or framework"
+" in mind. Configuration management allows you to avoid the many pitfalls "
+"inherent in building, managing, and maintaining an infrastructure as complex"
+" as OpenStack. By producing the manifests, cookbooks, or templates required "
+"for a configuration management utility, you are able to satisfy a number of "
+"documentation and regulatory reporting requirements. Further, configuration "
+"management can also function as part of your BCP and DR plans wherein you "
+"can rebuild a node or service back to a known state in a DR event or given a"
+" compromise."
+msgstr "OpenStack クラウドの構築時は、構成管理ツールまたはフレームワークを念頭に設計、実装に着手するように強く推奨します。構成管理により、OpenStack のように複雑なインフラストラクチャーの構築、管理、維持において陥りやすい多くの問題を回避することができます。構成管理ユーティリティに必要なマニフェスト、クックブック、テンプレートを作成することで、多くの文書や監督機関へのレポート要件を満たすことができます。さらに、構成管理は、BCP および DR プランの一部としても機能する可能性もあります。その場合、DR やセキュリティ侵害があった場合にノードやサービスを既知の状態へ再構築することができます。"
+
+#: ./doc/security-guide/ch012_configuration-management.xml203(para)
+msgid ""
+"Additionally, when combined with a version control system such as Git or "
+"SVN, you can track changes to your environment over time and re-mediate "
+"unauthorized changes that may occur. For example, a "
+"<filename>nova.conf</filename> file or other configuration file falls out of"
+" compliance with your standard, your configuration management tool can "
+"revert or replace the file and bring your configuration back into a known "
+"state. Finally a configuration management tool can also be used to deploy "
+"updates; simplifying the security patch process. These tools have a broad "
+"range of capabilities that are useful in this space. The key point for "
+"securing your cloud is to choose a tool for configuration management and use"
+" it."
+msgstr "さらに、Git や SVN などのバージョン管理システムと統合すると、経年の環境の変化をチェックして、発生する可能性のある未認証の変更を修正することができます。例えば、<filename>nova.conf</filename> ファイルやその他の設定ファイルが規格に準拠しなくなった場合、既知の状態に構成管理ツールはファイルを復元または置き換えることができるでしょう。最後に、構成管理ツールを使用して、更新のデプロイも可能で、セキュリティパッチのプロセスを簡素化します。これらのツールには、この項において便利な機能が幅広く含まれています。クラウドのセキュリティ確保の主な目的は、構成管理のツールを選択して使用することです。"
+
+#: ./doc/security-guide/ch012_configuration-management.xml215(para)
+msgid ""
+"There are many configuration management solutions; at the time of this "
+"writing there are two in the marketplace that are robust in their support of"
+" OpenStack environments: <glossterm>Chef</glossterm> and "
+"<glossterm>Puppet</glossterm>. A non-exhaustive listing of tools in this "
+"space is provided below:"
+msgstr "構成管理ソリューションは多数存在しますが、本書の作成時点で市場にあるソリューションで OpenStack 環境のサポートが強力なものは <glossterm>Chef</glossterm> と <glossterm>Puppet</glossterm> の 2 種類となっています。以下に完全ではありませんが、ツールのリストを示しています。"
+
+#: ./doc/security-guide/ch012_configuration-management.xml223(para)
+msgid "Chef"
+msgstr "Chef"
+
+#: ./doc/security-guide/ch012_configuration-management.xml226(para)
+msgid "Puppet"
+msgstr "Puppet"
+
+#: ./doc/security-guide/ch012_configuration-management.xml229(para)
+msgid "Salt Stack"
+msgstr "Salt Stack"
+
+#: ./doc/security-guide/ch012_configuration-management.xml232(para)
+msgid "Ansible"
+msgstr "Ansible"
+
+#: ./doc/security-guide/ch012_configuration-management.xml236(title)
+msgid "Policy changes"
+msgstr "ポリシーの変更"
+
+#: ./doc/security-guide/ch012_configuration-management.xml237(para)
+msgid ""
+"Whenever a policy or configuration management is changed, it is good "
+"practice to log the activity, and backup a copy of the new set. Often, such "
+"policies and configurations are stored in a version controlled repository "
+"such as git."
+msgstr "ポリシーや構成管理が変更されると、そのアクティビティをロギングして、新しいセットのコピーをバックアップすると慣習として良いでしょう。通常、このようなポリシーや設定は Git などのバージョン管理リポジトリに保存されています。"
+
+#: ./doc/security-guide/ch012_configuration-management.xml244(title)
+msgid "Secure backup and recovery"
+msgstr "セキュアなバックアップとリカバリ"
+
+#: ./doc/security-guide/ch012_configuration-management.xml245(para)
+msgid ""
+"It is important to include Backup procedures and policies in the overall "
+"System Security Plan. For a good overview of OpenStack's Backup and Recovery"
+" capabilities and procedures, please refer to the OpenStack Operations "
+"Guide."
+msgstr "全体的なシステムセキュリティプランにバックアップ手順とポリシーを含めることは重要です。OpenStack のバックアップ／リカバリー機能や手順についての適切な概要は、OpenStack 運用ガイドを参照してください。"
+
+#: ./doc/security-guide/ch012_configuration-management.xml250(title)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml60(title)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml117(title)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml150(title)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml174(title)
+#: ./doc/security-guide/ch026_compute.xml45(title)
+#: ./doc/security-guide/ch026_compute.xml90(title)
+msgid "Security considerations"
+msgstr "セキュリティの課題"
+
+#: ./doc/security-guide/ch012_configuration-management.xml253(para)
+msgid ""
+"Ensure only authenticated users and backup clients have access to the backup"
+" server."
+msgstr "認証済みのユーザーおよびバックアップクライアントのみがバックアップサーバーにアクセスできるようにすること"
+
+#: ./doc/security-guide/ch012_configuration-management.xml257(para)
+msgid "Use data encryption options for storage and transmission of backups."
+msgstr "バックアップの保存や送信にはデータ暗号化オプションを使用すること"
+
+#: ./doc/security-guide/ch012_configuration-management.xml261(para)
+msgid ""
+"Use a dedicated and hardened backup servers. The logs for the backup server "
+"must be monitored daily and accessible by only few individuals."
+msgstr "セキュリティが強化された専用のバックアップサーバーを使用すること。バックアップサーバーのログは日次で監査し、ほんの一握りの人だけがこのログにアクセスできるようにしなければいけません。"
+
+#: ./doc/security-guide/ch012_configuration-management.xml266(para)
+msgid ""
+"Test data recovery options regularly. One of the things that can be restored"
+" from secured backups is the images. In case of a compromise, the best "
+"practice would be to terminate running instances immediately and then "
+"relaunch the instances from the images in the secured backup repository."
+msgstr "データのリカバリーオプションを定期的にテストすること。セキュアなバックアップからリストアが可能なものの 1 つにイメージがあります。情報漏洩などが発生した場合のベストプラクティスは、すぐに実行中のインスタンスを終了して、セキュアなバックアップリポジトリにあるイメージからインスタンスを再起動することです。"
+
+#: ./doc/security-guide/ch012_configuration-management.xml276(title)
+#: ./doc/security-guide/ch058_forensicsincident-response.xml48(title)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml90(title)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml160(title)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml199(title)
+#: ./doc/security-guide/ch026_compute.xml60(title)
+#: ./doc/security-guide/ch026_compute.xml106(title)
+msgid "References"
+msgstr "参考資料"
+
+#: ./doc/security-guide/ch012_configuration-management.xml279(para)
+msgid ""
+"<citetitle>OpenStack Operations Guide</citetitle> on <link "
+"href=\"http://docs.openstack.org/trunk/openstack-"
+"ops/content/backup_and_recovery.html\">backup and recovery</link>"
+msgstr "<citetitle>OpenStack 運用ガイド</citetitle> の <link href=\"http://docs.openstack.org/trunk/openstack-ops/content/backup_and_recovery.html\">バックアップとリカバリー</link>"
+
+#: ./doc/security-guide/ch012_configuration-management.xml287(link)
+msgid ""
+"http://www.sans.org/reading_room/whitepapers/backup/security-considerations-"
+"enterprise-level-backups_515"
+msgstr "http://www.sans.org/reading_room/whitepapers/backup/security-considerations-enterprise-level-backups_515"
+
+#: ./doc/security-guide/ch012_configuration-management.xml291(link)
+msgid "OpenStack Security Primer"
+msgstr "OpenStack セキュリティ入門"
+
+#: ./doc/security-guide/ch012_configuration-management.xml297(title)
+msgid "Security auditing tools"
+msgstr "セキュリティ監査ツール"
+
+#: ./doc/security-guide/ch012_configuration-management.xml298(para)
+msgid ""
+"Security auditing tools can complement the configuration management tools. "
+"Security auditing tools automate the process of verifying that a large "
+"number of security controls are satisfied for a given system configuration. "
+"These tools help to bridge the gap from security configuration guidance "
+"documentation (for example, the STIG and NSA Guides) to a specific system "
+"installation. For example, <link href=\"https://fedorahosted.org/scap-"
+"security-guide/\">SCAP</link> can compare a running system to a pre-defined "
+"profile. SCAP outputs a report detailing which controls in the profile were "
+"satisfied, which ones failed, and which ones were not checked."
+msgstr "セキュリティ監査ツールは、構成管理ツールを補完することができます。セキュリティ監査ツールは、セキュリティ制御の多くが指定のシステム設定を満たしていることを確認するプロセスを自動化します。これらのツールは、セキュリティ設定方針文書 (例: STIG  および NSA ガイド) から個別のシステムインストール環境のギャップを埋めるサポートをします。例えば、<link href=\"https://fedorahosted.org/scap-security-guide/\">SCAP</link> は実行中のシステムと事前定義済みのプロファイルを比較することができます。SCAP はプロファイル内のどの制御に対応しているか、問題があるものはどれか、確認されていないものはどれかを詳細にまとめたレポートを出力します。"
+
+#: ./doc/security-guide/ch012_configuration-management.xml310(para)
+msgid ""
+"Combining configuration management and security auditing tools creates a "
+"powerful combination. The auditing tools will highlight deployment concerns."
+" And the configuration management tools simplify the process of changing "
+"each system to address the audit concerns. Used together in this fashion, "
+"these tools help to maintain a cloud that satisfies security requirements "
+"ranging from basic hardening to compliance validation."
+msgstr "構成管理とセキュリティ監査ツールを組み合わせることで強力になります。監査ツールはデプロイメントの課題をハイライトし、構成管理ツールは各システムの変更プロセスを簡素化して監査の課題に対応していきます。このような方法で組み合わせて使用することで、これらのツールは、基本的なセキュリティの強化からコンプライアンスのバリデーションに至るまで、このようなセキュリティ要件を満たすクラウドを維持できるようにします。"
+
+#: ./doc/security-guide/ch012_configuration-management.xml317(para)
+msgid ""
+"Configuration management and security auditing tools will introduce another "
+"layer of complexity into the cloud. This complexity brings additional "
+"security concerns with it. We view this as an acceptable risk trade-off, "
+"given their security benefits. Securing the operational use of these tools "
+"is beyond the scope of this guide."
+msgstr "構成管理およびセキュリティ監査ツールは、もう１つのレベルで複雑性をクラウドにもたらします。この複雑性により、新たなセキュリティの課題が出てきます。これについては、セキュリティの利点もあるため、許容範囲のリスクのトレードオフという見解を持っています。これらのツールの運用におけるセキュリティ確保については、本書の対象外となっています。"
+
+#: ./doc/security-guide/ch047_data-encryption.xml8(title)
+msgid "Data encryption"
+msgstr "データ暗号化"
+
+#: ./doc/security-guide/ch047_data-encryption.xml9(para)
+msgid ""
+"The option exists for implementors to encrypt tenant data wherever it is "
+"stored on disk or transported over a network. This is above and beyond the "
+"general recommendation that users encrypt their own data before sending it "
+"to their provider."
+msgstr "このオプションは、データをディスクに保存する箇所やデータをネットワーク経由で転送する箇所でテナントデータを暗号化する実装者用です。ユーザが自分自身のデータをプロバイダに送信する前にデータを暗号化するという一般的な推奨の上またはその先にあるものです。"
+
+#: ./doc/security-guide/ch047_data-encryption.xml10(para)
+msgid ""
+"The importance of encrypting data on behalf of tenants is largely related to"
+" the risk assumed by a provider that an attacker could access tenant data. "
+"There may be requirements here in government, as well as requirements per-"
+"policy, in private contract, or even in case law in regard to private "
+"contracts for public cloud providers. It is recommended that a risk "
+"assessment and legal consul advised before choosing tenant encryption "
+"policies."
+msgstr "テナントの為のデータ暗号化の重要性は、攻撃者がテナントデータにアクセスできる事をプロバイダが想定するリスクに広く関係しています。政府での要件があるかも知れませんし、（ポリシー単位の要件と同様）パブリッククラウド提供者用の随意契約に関しては、随意契約の中、あるいは判例法の中でさえ要求されるかも知れません。テナント暗号化ポリシーを選択する前に、リスク分析と法務コンサルの忠告を受ける事をお勧めします。"
+
+#: ./doc/security-guide/ch047_data-encryption.xml11(para)
+msgid ""
+"Per-instance or per-object encryption is preferable over, in descending "
+"order, over per-project, per-tenant, per-host, and per-cloud aggregations. "
+"This recommendation is inverse to the complexity and difficulty of "
+"implementation. Presently, in some projects it is difficult or impossible to"
+" implement encryption as loosely granular as even per-tenant. We recommend "
+"implementors make a best-effort in encrypting tenant data."
+msgstr "暗号化の単位は、好ましい方から順にインスタンス単位又はオブジェクト単位、プロジェクト単位、テナント単位、ホスト単位、クラウド集合単位です。この推奨順は、実装の複雑さと困難さの順序の逆です。現在、いくつかのプロジェクトでは、テナント単位ですら粒度の荒い暗号化の実装が困難又は不可能です。実装者がテナントデータの暗号化を最善策とする事をお勧めします。"
+
+#: ./doc/security-guide/ch047_data-encryption.xml12(para)
+msgid ""
+"Often, data encryption relates positively to the ability to reliably destroy"
+" tenant and per-instance data, simply by throwing away the keys. It should "
+"be noted that in doing so, it becomes of great importance to destroy those "
+"keys in a reliable and secure manner."
+msgstr "時々、データ暗号化は単に暗号鍵を捨てるという事による、信頼できるテナントやインスタンス単位のデータ削除可能性と明確に関係があります。そうするよう記述すべきですし、信頼できる安全な方法でこれらの鍵を破壊する事が従来になります。"
+
+#: ./doc/security-guide/ch047_data-encryption.xml13(para)
+msgid "Opportunities to encrypt data for users are present:"
+msgstr "ユーザ用のデータ暗号化をする機会は現存します。"
+
+#: ./doc/security-guide/ch047_data-encryption.xml15(para)
+#: ./doc/security-guide/ch047_data-encryption.xml25(title)
+#: ./doc/security-guide/ch046_data-residency.xml31(para)
+msgid "Object Storage objects"
+msgstr "Object Storage オブジェクト"
+
+#: ./doc/security-guide/ch047_data-encryption.xml18(para)
+#: ./doc/security-guide/ch047_data-encryption.xml31(title)
+msgid "Block Storage volumes and instance ephemeral filesystems"
+msgstr "Block Storage ボリュームとインスタンスの一時ファイルシステム"
+
+#: ./doc/security-guide/ch047_data-encryption.xml21(para)
+#: ./doc/security-guide/ch047_data-encryption.xml37(title)
+msgid "Network data"
+msgstr "ネットワークデータ"
+
+#: ./doc/security-guide/ch047_data-encryption.xml26(para)
+msgid ""
+"The ability to encrypt objects in Object Storage is presently limited to "
+"disk-level encryption per node. However, there does exist third-party "
+"extensions and modules for per-object encryption. These modules have been "
+"proposed upstream, but have not per this writing been formally accepted. "
+"Below are some pointers:"
+msgstr "Object Storage 中のオブジェクトの暗号化の可能性は、現時点ではノード単位のディスクレベル暗号化に限定されています。しかしながら、オブジェクト単位の暗号化用のサードパーティ拡張やモジュールが存在します。これらのモジュールはアップストリームに提案されていますが、この文書を書いている時点では公式に認可されていません。下記はそれらの幾つかへのポインタです。"
+
+#: ./doc/security-guide/ch047_data-encryption.xml27(link)
+msgid "https://github.com/Mirantis/swift-encrypt"
+msgstr "https://github.com/Mirantis/swift-encrypt"
+
+#: ./doc/security-guide/ch047_data-encryption.xml28(link)
+msgid ""
+"http://www.mirantis.com/blog/on-disk-encryption-prototype-for-openstack-"
+"swift/"
+msgstr "http://www.mirantis.com/blog/on-disk-encryption-prototype-for-openstack-swift/"
+
+#: ./doc/security-guide/ch047_data-encryption.xml32(para)
+msgid ""
+"The ability to encrypt volumes depends on the service backends chosen. Some "
+"backends may not support this at all."
+msgstr "暗号化ボリュームの可否は選択したサービスバックエンドに依存します。いくつかのバックエンドは暗号化を全くサポートしないかも知れません。"
+
+#: ./doc/security-guide/ch047_data-encryption.xml33(para)
+msgid ""
+"As both block storage and compute support LVM backed storage, we can easily "
+"provide an example applicable to both systems. In deployments using LVM, "
+"encryption may be performed against the backing physical volumes. An "
+"encrypted block device would be created using the standard Linux tools, with"
+" the LVM physical volume (PV) created on top of the decrypted block device "
+"using pvcreate. Then, the vgcreate or vgmodify tool may be used to add the "
+"encrypted physical volume to an LVM volume group (VG)."
+msgstr "Block Storage と Compute は両方、LVM ベースのストレージをサポートしているので、両システムに簡単に適用可能な例を提供します。LVM を用いたデプロイでは、暗号化はベースの物理ボリュームに対して実施できます。暗号化ブロックデバイスは、pvcreate を使用して復号化したブロックデバイスの上に作成した LVM 物理ボリューム (PV) を用いて、標準の Linux ツールを使用して作成する事ができます。それから、vgcreate 又は vgmodify ツールを使用して、暗号化した物理ボリュームを LVM のボリュームグループ (VG) に追加できます。"
+
+#: ./doc/security-guide/ch047_data-encryption.xml34(para)
+msgid ""
+"A feature aimed for the Havana release provides encryption of the VM's data "
+"before it is written to disk. This allows the privacy of data to be "
+"maintained while residing on the storage device. The idea is similar to how "
+"self-encrypting drives work. This feature presents a normal block storage "
+"device to the VM but encrypts the bytes in the virtualization host before "
+"writing them to the disk. The block server operates exactly as it does when "
+"reading and writing unencrypted blocks, except special handling will be "
+"required for Block Storage features such as snapshots and live migration. "
+"Note that this feature uses an independent key manager."
+msgstr "Havana リリース向けの１機能が、ディスクに書き込まれる前の VM データの暗号化を提供しています。これは、ストレージデバイス上でもデータのプライバシーが管理される事を可能にします。このアイデアは自己暗号化ドライブが機能する方法と同様です。この機能は、VM には通常のブロックストレージデバイスとして見えますが、仮想化ホストではディスクにデータが書き込まれる前にデータが暗号化されます。ブロックサーバは、特別な処理がスナップショットやライブマイグレーションといった Block Storage の機能に向けて要求される事を除いて、暗号化されていないブロックを読み書きする場合と全く同様に処理が行われます。この機能は独立した鍵管理を使用する事に注意して下さい。"
+
+#: ./doc/security-guide/ch047_data-encryption.xml38(para)
+msgid ""
+"Tenant data for compute could be encrypted over IPSec or other tunnels. This"
+" is not functionality common or standard in OpenStack, but is an option "
+"available to motivated and interested implementors."
+msgstr "compute のテナントデータは IPSec 又は他のトンネルで暗号化できます。OpenStack での共通または標準の機能ではありませんが、やる気と興味がある実装者に１つの選択肢が利用できます。"
+
+#: ./doc/security-guide/ch047_data-encryption.xml42(para)
+msgid ""
+"Block storage supports a variety of mechanisms for supplying mountable "
+"volumes. It is outside the scope of this guide to specify recommendations "
+"for each Block Storage backend driver. For the purpose of performance, many "
+"storage protocols are unencrypted. Some protocols such as iSCSI can provide "
+"authentication and encrypted sessions, it is our recommendation to enable "
+"these features."
+msgstr "Block Storage は、マウント可能なボリュームの提供に向けた様々な機構をサポートします。Block Storage の各バックエンドドライバ用に推奨を指定する事はこのガイドの範囲外です。性能の為に、多くのストレージプロトコルは暗号化されていません。iSCSI のような幾つかのプロトコルは、認証と暗号化セッションを提供できます。これらの機能を有効にする事を推奨します。"
+
+#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml8(title)
+msgid "Case studies: API endpoints"
+msgstr "ケーススタディ: API エンドポイント"
+
+#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml9(para)
+msgid ""
+"In this case study we discuss how Alice and Bob would address endpoint "
+"configuration to secure their private and public clouds. Alice's cloud is "
+"not publicly accessible, but she is still concerned about securing the "
+"endpoints against improper use. Bob's cloud, being public, must take "
+"measures to reduce the risk of attacks by external adversaries."
+msgstr "このケーススタディでは、アリスとボブがどうやってプライベートクラウドとパブリッククラウドのエンドポイント設定を堅牢化するかについて議論します。\nアリスのプライベートクラウドは公開されたものではありませんが、不適切な使い方からエンドポイントを守る方法について憂慮しています。ボブのパブリッククラウドは、外部からの攻撃に対してリスクを低減する措置を講じなければいけません。"
+
+#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml11(title)
+#: ./doc/security-guide/ch066_case-studies-compliance.xml11(title)
+#: ./doc/security-guide/ch015_case-studies-management.xml28(title)
+#: ./doc/security-guide/ch056_case-studies-instance-management.xml11(title)
+#: ./doc/security-guide/ch035_case-studies-networking.xml11(title)
+#: ./doc/security-guide/ch028_case-studies-identity-management.xml18(title)
+#: ./doc/security-guide/ch059_case-studies-monitoring-logging.xml11(title)
+#: ./doc/security-guide/ch018_case-studies-pkissl.xml11(title)
+#: ./doc/security-guide/ch039_case-studies-messaging.xml11(title)
+#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml11(title)
+#: ./doc/security-guide/ch009_case-studies.xml11(title)
+#: ./doc/security-guide/ch049_case-studies-tenant-data.xml17(title)
+#: ./doc/security-guide/ch044_case-studies-database.xml11(title)
+msgid "Alice's private cloud"
+msgstr "アリスのプライベートクラウド"
+
+#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml12(para)
+msgid ""
+"Alice's organization requires that the security architecture protect the "
+"access to the public and private endpoints, so she elects to use the Apache "
+"SSL proxy on both public and internal services. Alice's organization has "
+"implemented its own certificate authority. Alice contacts the PKI office in "
+"her agency that manages her PKI and certificate issuance. Alice obtains "
+"certificates issued by this CA and configures the services within both the "
+"public and management security domains to use these certificates. Since "
+"Alice's OpenStack deployment exists entirely on a disconnected from the "
+"Internet network, she makes sure to remove all default CA bundles that "
+"contain external public CA providers to ensure the OpenStack services only "
+"accept client certificates issued by her agency's CA. Alice has registered "
+"all of the services in the Identity service's catalog, using the internal "
+"URLs for access by internal services. She has installed host-based intrusion"
+" detection on all of the API endpoints."
+msgstr "アリスは所属する組織から、パブリックとプライベートのエンドポイントへのアクセスに対してセキュリティ対策を講じるように命じられました。そこで彼女は、パブリックとプライベートのサービスに対して Apache SSL Proxy を構築しました。アリスの組織では、自前の認証局を用意しています。アリスは、彼女の PKI と証明書発行を管理する PKI 担当部門に連絡します。アリスはこのCAによって発行された証明書を入手し、これらの証明書を使用するようパブリックと管理セキュリティドメインの両方のサービスを設定します。アリスの OpenStack デプロイが完全にインターネットから独立して存在するので、OpenStack サービスが彼女の組織の CA から発行されたクライアント証明書のみ許可するよう、外部のパブリックな CA プロバイダを含むデフォルトの全 CA バンドルが削除されている事を確認しています。アリスは、内部サービスのアクセス用の内部 URL を利用して、Identity のサービスカタログに全サービスを登録しました。彼女は、すべての API エンドポイントにホストベース IDS をインストールしました。"
+
+#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml33(title)
+#: ./doc/security-guide/ch066_case-studies-compliance.xml18(title)
+#: ./doc/security-guide/ch015_case-studies-management.xml33(title)
+#: ./doc/security-guide/ch056_case-studies-instance-management.xml17(title)
+#: ./doc/security-guide/ch035_case-studies-networking.xml29(title)
+#: ./doc/security-guide/ch028_case-studies-identity-management.xml43(title)
+#: ./doc/security-guide/ch059_case-studies-monitoring-logging.xml15(title)
+#: ./doc/security-guide/ch018_case-studies-pkissl.xml15(title)
+#: ./doc/security-guide/ch039_case-studies-messaging.xml15(title)
+#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml17(title)
+#: ./doc/security-guide/ch009_case-studies.xml16(title)
+#: ./doc/security-guide/ch049_case-studies-tenant-data.xml50(title)
+#: ./doc/security-guide/ch044_case-studies-database.xml15(title)
+msgid "Bob's public cloud"
+msgstr "ボブのパブリッククラウド"
+
+#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml34(para)
+msgid ""
+"Bob must also protect the access to the public and private endpoints, so he "
+"elects to use the Apache SSL proxy on both public and internal services. On "
+"the public services, he has configured the certificate key files with "
+"certificates signed by a well-known Certificate Authority. He has used his "
+"organization's self-signed CA to sign certificates in the internal services "
+"on the Management network. Bob has registered his services in the Identity "
+"service's catalog, using the internal URLs for access by internal services. "
+"Bob's public cloud runs services on SELinux, which he has configured with a "
+"mandatory access control policy to reduce the impact of any publicly "
+"accessible services that may be compromised. He has also configured the "
+"endpoints with a host-based IDS."
+msgstr "ボブもまた、パブリックとプライベートエンドポイントを守るひつようがあるため、 Apache SSL proxy をパブリックサービスと内部サービスの両方に構築しました。\nパブリックサービス側には、よく知られている認証局が署名した証明書キーファイルを、内部サービス側には、自己署名証明書を管理ネットワーク上のサービスに設定しました。\n内部アクセス用の Internal URL 越しに、サービスを Identity のサービスカタログに登録し、また、ホストベースの侵入検知システムを全 API エンドポイントに設定しました。"
+
+#: ./doc/security-guide/ch066_case-studies-compliance.xml8(title)
+msgid "Case studies: compliance"
+msgstr "ケーススタディ: コンプライアンス"
+
+#: ./doc/security-guide/ch066_case-studies-compliance.xml9(para)
+msgid ""
+"In this case study we discuss how Alice and Bob would address common "
+"compliance requirements. The preceding chapter refers to a wide variety of "
+"compliance certifications and standards. Alice will address compliance in a "
+"private cloud, while Bob will be focused on compliance for a public cloud."
+msgstr "このケーススタディでは、アリスとボブがどのように一般的なコンプライアンス要件に対応するかを説明します。これまでの章で、さまざまなコンプライアンス認証と標準について言及しました。アリスはプライベートクラウドでコンプライアンスに取り組み、いっぽうボブはパブリッククラウド向けのコンプライアンスに注力します。"
+
+#: ./doc/security-guide/ch066_case-studies-compliance.xml12(para)
+msgid ""
+"Alice is building an OpenStack private cloud for the United States "
+"government, specifically to provide elastic compute environments for signal "
+"processing. Alice has researched government compliance requirements, and has"
+" identified that her private cloud will be required to certify against FISMA"
+" and follow the FedRAMP accreditation process, which is required for all "
+"federal agencies, departments and contractors to become a Certified Cloud "
+"Provider (CCP). In this particular scenario for signal processing, the FISMA"
+" controls required will most likely be FISMA High, which indicates possible "
+"\"severe or catastrophic adverse effects\" should the information system "
+"become compromised. In addition to FISMA Moderate controls Alice must ensure"
+" her private cloud is FedRAMP certified, as this is a requirement for all "
+"agencies that currently utilize, or host federal information within a cloud "
+"environment."
+msgstr "アリスはOpenStackプライベートクラウドを米国政府向けに構築しています。具体的には、信号処理向けの柔軟なコンピューティング環境です。アリスは政府向けコンプライアンス要件を調査した結果、これから構築しようとしているプライベートクラウドはFISMAおよびFedRAMP認定が必要であると判断しました。これは政府系機関、行政部、および契約者、どのような立場であっても、認定クラウドプロバイダー(Certified Cloud Provider, CCP)になるために必要な手続きです。特に信号処理は、FISMAはそれを\"深刻で壊滅的な影響\"をシステムに与えうるとしているため、FISMA影響度が\"高\"となりがちです。加えてFISMA Moderateレベルにおいて、アリスはそのプライベートクラウドを確実にFedRAMP認証としなければいけません。これはクラウド内に政府の情報を保有する、全ての機関に求められてる条件です。"
+
+#: ./doc/security-guide/ch066_case-studies-compliance.xml13(para)
+msgid ""
+"To meet these strict government regulations Alice undertakes a number of "
+"activities. Scoping of requirements is particularly important due to the "
+"volume of controls that must be implemented, which will be defined in NIST "
+"Publication 800-53."
+msgstr "これらの厳しい政府規制の要件を満たすため、アリスは多くの活動を行います。範囲の決定作業は、実装すべき統制の量に影響するため、特に重要です。これはNIST刊行 800-53で定められています。"
+
+#: ./doc/security-guide/ch066_case-studies-compliance.xml14(para)
+msgid ""
+"All technology within her private cloud must be FIPS certified technology, "
+"as mandated within NIST 800-53 and FedRAMP. As the U.S. Department of "
+"Defense is involved, Security Technical Implementation Guides (STIGs) will "
+"come into play, which are the configuration standards for DOD IA and IA-"
+"enabled devices / systems. Alice notices a number of complications here as "
+"there is no STIG for OpenStack, so she must address several underlying "
+"requirements for each OpenStack service; for example, the networking SRG and"
+" Application SRG will both be applicable (<link "
+"href=\"http://iase.disa.mil/srgs/index.html\">list of SRGs</link>). Other "
+"critical controls include ensuring that all identities in the cloud use PKI,"
+" that SELinux is enabled, that encryption exists for all wire-level "
+"communications, and that continuous monitoring is in place and clearly "
+"documented. Alice is not concerned with object encryption, as this will be "
+"the tenants responsibility rather than the provider."
+msgstr "彼女のプライベートクラウドで使われる全ての技術は、NIST 800-53とFedRAMPに従い、FIPS認証技術であることが求められます。米国国防省が関わる場合、国防省のIA - Information AssuranceおよびIA-enabled対象機器/システムの構成標準であるSecurity Technical Implementation Guides (STIGs) も関係します。OpenStack向けのSTIGが無くとも、アリスはさまざまな要素を考慮し、各OpenStackサービス毎に、いくつかの潜在的な要件を考慮しなければいけません。例えば、networking SRG - Security Requirements GuidesとApplication SRGはどちらも対象です(<link href=\"http://iase.disa.mil/srgs/index.html\">list of SRGs</link>)。他の重要な統制として、クラウド内の全てのIDではPKIが使われ、SELinuxが有効であり、すべての全ての通信経路が暗号化でき、持続的に監視が行われ、かつ明快に文書化されていること、などが挙げられます。なお、アリスはオブジェクトの暗号化を考慮しませんでしたが、これはプロバイダーというよりは、テナントの責任であるからです。"
+
+#: ./doc/security-guide/ch066_case-studies-compliance.xml15(para)
+msgid ""
+"If Alice has adequately scoped and executed these compliance activities, she"
+" may begin the process to become FedRAMP compliant by hiring an approved "
+"third-party auditor. Typically this process takes up to 6 months, after "
+"which she will receive an Authority to Operate and can offer OpenStack cloud"
+" services to the government."
+msgstr "もしアリスが十分な範囲を定義し、それらのコンプライアンス活動を実施できたのであれば、次は認定外部監査人によるFedRAMP認証の取得プロセスに移ります。一般的にこのプロセスは最長6ヶ月を要します。このステップを経て、Authority to Operate - 注意影響レベル認定 を取得し、OpenStackクラウドサービスを政府に提案できるようになります。"
+
+#: ./doc/security-guide/ch066_case-studies-compliance.xml19(para)
+msgid ""
+"Bob is tasked with compliance for a new OpenStack public cloud deployment, "
+"that is focused on providing cloud services to both small developers and "
+"startups, as well as large enterprises. Bob recognizes that individual "
+"developers are not necessarily concerned with compliance certifications, but"
+" to larger enterprises certifications are critical. Specifically Bob desires"
+" to achieve SOC 1, SOC 2 Security, as well as ISO 27001/2 as quickly as "
+"possible. Bob references the Cloud Security Alliance Cloud Control Matrix "
+"(CCM) to assist in identifying common controls across these three "
+"certifications (such as periodic access reviews, auditable logging and "
+"monitoring services, risk assessment activities, security reviews, etc). Bob"
+" then engages an experienced audit team to conduct a gap analysis on the "
+"public cloud deployment, reviews the results and fills any gaps identified. "
+"Bob works with other team members to ensure that these security controls and"
+" activities are regularly conducted for a typical audit period (~6-12 "
+"months)."
+msgstr "ボブは新たなOpenStackクラウド環境のコンプライアンス活動を任されています。このクラウドは小規模の開発者やスタートアップだけでなく、大規模企業向けにも注力しています。ボブは個人開発者はコンプライアンス認証を意識することが多くないが、いっぽうで大規模企業向けには認証が重要であることを認識しています。ボブは特にSOC 1、SOC 2、およびISO 27001/2認証を早急に取得したいと考えています。そこでボブは3つの認証に共通する統制を特定するため、Cloud Security Alliance Cloud Control Matrix (CCM)を参考にしました (例えば、定期的なアクセス検査、監査可能なロギングや監視サービス、リスク評価活動、セキュリティレビューなど)。それからボブは、パブリッククラウドのギャップ評価、結果のレビュー、そして特定されたギャップを埋めるため、経験ある監査人チームと契約します。ボブは他のチームメンバーとともに、それらのセキュリティ統制と活動が一般的な監査期間(〜6-12ヶ月)において、定期的に、確実に機能するようにします。"
+
+#: ./doc/security-guide/ch066_case-studies-compliance.xml36(para)
+msgid ""
+"At the end of the audit period Bob has arranged for an external audit team "
+"to review in-scope security controls at randomly sampled points of time over"
+" a 6 month period. The audit team provides Bob with an official report for "
+"SOC 1 and SOC 2, and separately for ISO 27001/2. As Bob has been diligent in"
+" ensuring security controls are in place for his OpenStack public cloud, "
+"there are no additional gaps exposed on the report. Bob can now provide "
+"these official reports to his customers under NDA, and advertise that he is "
+"SOC 1, SOC 2 and ISO 27001/2 compliant on his website."
+msgstr "監査期間の最後にボブは外部監査人チームとの調整を行います。目的は、6ヶ月以上にわたって無作為なタイミングで実施した、セキュリティ統制のレビューです。そして、監査人チームはボブにSOC 1とSOC 2、また別途ISO 27001/2向けの公式な報告書を提供します。ボブのパブリッククラウド採用における勤勉な取り組みの結果、指摘されるような追加のギャップはありませんでした。ボブは正式な報告書を彼の顧客にNDA下で提供でき、また、SOC 1、SOC 2、およびISO 27001/2に準拠していることを彼のウェブサイトでアピールできるようになりました。"
+
+#: ./doc/security-guide/ch015_case-studies-management.xml8(title)
+msgid "Case studies: management interfaces"
+msgstr "ケーススタディ: 管理インターフェース"
+
+#: ./doc/security-guide/ch015_case-studies-management.xml9(para)
+msgid ""
+"Previously we discussed typical OpenStack management interfaces and "
+"associated backplane issues. We will now approach these issues by returning "
+"to our Alice and Bob case study. Specifically, we will look into how both "
+"Alice and Bob will address:"
+msgstr "一般的な OpenStack 管理インターフェースと関連のバックプレーンの問題について、ここまでに議論しました。再度、アリスとボブのケーススタディに戻って、これらの問題を見ていきます。特に、アリスとボブが以下の点をどのように対応したかを確認していきます。"
+
+#: ./doc/security-guide/ch015_case-studies-management.xml15(para)
+msgid "Cloud administration"
+msgstr "クラウド管理"
+
+#: ./doc/security-guide/ch015_case-studies-management.xml18(para)
+msgid "Self service"
+msgstr "セルフサービス"
+
+#: ./doc/security-guide/ch015_case-studies-management.xml21(para)
+msgid "Data replication and recovery"
+msgstr "データの複製およびリカバリー"
+
+#: ./doc/security-guide/ch015_case-studies-management.xml24(para)
+msgid "SLA and security monitoring"
+msgstr "SLA およびセキュリティの監視"
+
+#: ./doc/security-guide/ch015_case-studies-management.xml29(para)
+msgid ""
+"When building her private cloud, while air-gapped, Alice still needs to "
+"consider her service management interfaces. Before deploying her private "
+"cloud, Alice has completed her system documentation. Specifically she has "
+"identified which OpenStack services will exist in each security domain. From"
+" there Alice has further restricted access to management interfaces by "
+"deploying a combination of IDS, SSL encryption, and physical network "
+"isolation. Additionally, Alice requires high availability and redundant "
+"services. Thus, Alice sets up redundant infrastructure for various OpenStack"
+" API services."
+msgstr "プライベートクラウドを構築する際、ネットワークが物理的に分離されていますが、アリスはサービス管理インターフェースを検討する必要があります。プライベートクラウドをデプロイする前に、システム文書を書き上げました。特に、どの OpenStack サービスが各セキュリティドメインに存在するかを特定しました。そこから、アリスは、IDS、SSL、暗号化、物理的なネットワークの分離を組み合わせてデプロイすることで、管理インターフェースへのアクセスをさらに制限しました。また、高可用性や冗長サービスも必要とするため、様々な OpenStack API サービスに対してインフラストラクチャーの冗長設定を行いました。"
+
+#: ./doc/security-guide/ch015_case-studies-management.xml30(para)
+msgid ""
+"Alice also needs to provide assurances that the physical servers and "
+"hypervisors have been built from a known secure state into a well-defined "
+"configuration. To enable this, Alice uses a combination of a Configuration "
+"Management platform to configure each machine according to the standards and"
+" regulations she must comply with. It will also enable Alice to report "
+"periodically on the state of her cloud and perform remediation to a known "
+"state should anything be out of the ordinary. Additionally, Alice provides "
+"hardware assurances by using a PXE system to build her nodes from a known "
+"set of base images. During the boot process, Alice provides further "
+"assurances by enabling Intel TXT and related trusted boot technologies "
+"provided by the hardware."
+msgstr "また、物理サーバーとハイパーバイザーは既知のセキュアな状態から十分に定義された設定へと確実に構築されるようにする必要があります。これを可能にするには、構成管理プラットフォームを合わせて使用して、準拠する必要のある規格や規定に従い各マシンを設定していきます。また、構成管理プラットフォームは、クラウドの状態を定期的に報告して、通常以外のことが発生した場合に既知の状態に修正することができます。さらに、PXE システムを使用することで、既知のベースイメージからノードを構築してハードウェア保証を提供することができます。ブートプロセス時に、そのハードウェアから提供される Intel TXT や関連の信頼できるブート技術を有効にすることでさらなる保証を確保できます。"
+
+#: ./doc/security-guide/ch015_case-studies-management.xml34(para)
+msgid ""
+"As a public cloud provider, Bob is concerned with both the continuous "
+"availability of management interfaces and the security of transactions to "
+"the management interfaces. To that end Bob implements multiple redundant "
+"OpenStack API endpoints for the services his cloud will run. Additionally on"
+" the public network Bob uses SSL to encrypt all transactions between his "
+"customers and his cloud interfaces. To isolate his cloud operations Bob has "
+"physically isolated his management, instance migration, and storage "
+"networks."
+msgstr "パブリッククラウドのプロバイダーとして、ボブは管理インターフェースの継続的な可用性と、管理インターフェースへのトランザクションのセキュリティの両方を考慮しています。このように、ボブは、クラウドが実行するサービスに対して、冗長化された OpenStack API エンドポイントを実装します。さらに、パブリックネットワークでは、SSL を使用して、顧客とクラウドインターフェースの間のトランザクションをすべて暗号化します。クラウドの運用を分離するために、ボブは管理、インスタンスマイグレーション、ストレージネットワークを物理的に分離しました。"
+
+#: ./doc/security-guide/ch015_case-studies-management.xml35(para)
+msgid ""
+"To ease scaling and reduce management overhead Bob implements a "
+"configuration management system. For customer data assurances, Bob offers a "
+"backup as a service product as requirements will vary between customers. "
+"Finally, Bob does not provide a \"baremetal\" or the ability to schedule an "
+"entire node, so to reduce management overhead and increase operational "
+"efficiency Bob does not implement any node boot time security."
+msgstr "管理オーバーヘッドのスケーリングや削減を簡単にするため、構成管理システムを実装します。顧客のデータ保証に対しては、顧客ごとに要件が変わるためサービス商品としてバックアップを提供します。最後に、「ベアメタル」やノード全体のスケジュール機能を提供せず、管理オーバーヘッドの削減、運用効率の向上を図るため、ノードのブート時におけるセキュリティは実装しません。"
+
+#: ./doc/security-guide/ch006_introduction-to-case-studies.xml8(title)
+msgid "Introduction to case studies"
+msgstr "ケーススタディの概要"
+
+#: ./doc/security-guide/ch006_introduction-to-case-studies.xml9(para)
+msgid ""
+"This guide refers to two running case studies, which are introduced here and"
+" referred to at the end of each chapter."
+msgstr "本ガイドでは、全体を通して、2 つの運用事例を参照しています。ここでは、これらを概要を説明し、各章末で参照します。"
+
+#: ./doc/security-guide/ch006_introduction-to-case-studies.xml12(title)
+msgid "Case study: Alice, the private cloud builder"
+msgstr "事例: プライベートクラウド構築者のアリス"
+
+#: ./doc/security-guide/ch006_introduction-to-case-studies.xml13(para)
+msgid ""
+"Alice deploys a private cloud for use by a government department in the US. "
+"The cloud must comply with relevant standards, such as FedRAMP. The security"
+" paperwork requirements for this cloud are very high. It must have no direct"
+" access to the internet: its API endpoints, compute instances, and other "
+"resources must be exposed to only systems within the department's network, "
+"which is entirely air-gapped from all other networks. The cloud can access "
+"other network services on the organization's intranet such as the "
+"authentication and logging services."
+msgstr "アリスは、米国のある政府機関で使用するクラウドをデプロイしています。このクラウドは、FedRAMP などの関連基準に準拠する必要があり、またセキュリティ関連の文書業務を行う必要性が非常に高くなっています。クラウドは、インターネットには直接アクセスしてはなりません。API エンドポイント、Compute インスタンス、およびその他のリソースは、その政府機関のネットワーク内のシステムに対してのみ公開される必要があります。このネットワークは、他の全ネットワークから完全に隔離されています。クラウドは、この機関のイントラネット上で、認証/ロギングサービスなどの他のネットワークサービスにアクセスすることが可能です。"
+
+#: ./doc/security-guide/ch006_introduction-to-case-studies.xml25(title)
+msgid "Case study: Bob, the public cloud provider"
+msgstr "事例: パブリッククラウドプロバイダーのボブ"
+
+#: ./doc/security-guide/ch006_introduction-to-case-studies.xml26(para)
+msgid ""
+"Bob is a lead architect for a company that deploys a large greenfield public"
+" cloud. This cloud provides IaaS for the masses and enables any consumer "
+"with a valid credit card access to utility computing and storage, but the "
+"primary focus is enterprise customers. Data privacy concerns are a big "
+"priority for Bob as they are seen as a major barrier to large-scale adoption"
+" of the cloud by organizations."
+msgstr "ボブは、新規展開の大規模なパブリッククラウドのデプロイを行う会社のリードアーキテクトです。このクラウドは、有効なクレジットカードを持つ消費者が、ユーティリティコンピューティングやストレージに使用できる一般大衆向けの IaaS を提供しますが、第一のターゲットは 企業顧客です。企業の間では、データプライバシー問題は、大規模なクラウド導入の大きな障害とみなされているため、ボブにとって優先課題となっています。"
+
+#: ./doc/security-guide/ch048_key-management.xml8(title)
+msgid "Key management"
+msgstr "キーマネージメント"
+
+#: ./doc/security-guide/ch048_key-management.xml9(para)
+msgid ""
+"To address the often mentioned concern of tenant data privacy and limiting "
+"cloud provider liability, there is greater interest within the OpenStack "
+"community to make data encryption more ubiquitous. It is relatively easy for"
+" an end-user to encrypt their data prior to saving it to the cloud, and this"
+" is a viable path for tenant objects such as media files, database archives "
+"among others. However, when client side encryption is used for virtual "
+"machine images, block storage etc, client intervention is necessary in the "
+"form of presenting keys to unlock the data for further use. To seamlessly "
+"secure the data and yet have it accessible without burdening the client with"
+" having to manage their keys and interactively provide them calls for a key "
+"management service within OpenStack. Providing encryption and key management"
+" services as part of OpenStack eases data-at-rest security adoption, "
+"addresses customer concerns about the privacy and misuse of their data with "
+"the added advantage of limiting cloud provider liability. Provider liability"
+" is of concern in multi-tenant public clouds with respect to handing over "
+"tenant data during a misuse investigation."
+msgstr "頻繁に触れられるテナントデータのプライバシーとクラウドプロバイダーの法的責任の限度についての懸念に対処するために、OpenStack コミュニティはデーターの暗号化を様々な個所へ適用することに興味を持っています。エンドユーザーがクラウドにデータをセーブする前にそれらを暗号化することは比較的に簡単で、メディアファイル、データベースアーカイブなどテナントオブジェクトに実行可能な方法です。しかし、クライアント側の暗号化が仮想マシンのイメージを使用する場合、ブロックストレージなどクライアントの介入では、データの更なる利用のために解除する鍵を提示する形式が必要です。しかし、クライアント側の暗号化が仮想マシンのイメージを使用する場合、ブロックストレージなどクライアントの介入では、データの更なる利用のために解除する鍵を提示する形式が必要です。シームレスにデータを保護し、クライアントの鍵を管理し対話的に鍵を提供することで負担をかけることなく、それがアクセスできるようにするには、OpenStack 内に鍵管理サービスを求められます。OpenStack の一環として、暗号化と鍵管理サービスの提供は、データ保存セキュリティ導入を容易にし、クラウド·プロバイダーの法的責任を制限する追加の利点と、プライバシーとデータの誤使用に関する顧客の懸念に対処しています。プロバイダの法的責任は、マルチテナントのパブリッククラウドで誤った調査によってテナントデータを引き渡す事が懸念されています。"
+
+#: ./doc/security-guide/ch048_key-management.xml10(para)
+msgid ""
+"A key management service is in the early stages of being developed and has a"
+" way to go before becoming an official component of OpenStack. Refer to "
+"<link "
+"href=\"https://github.com/cloudkeep/barbican/wiki/_pages\">https://github.com/cloudkeep/barbican/wiki/_pages</link>"
+" for details."
+msgstr "鍵管理は、まだ開発の初期段階で、OpenStack の正式コンポーネントになる過程の途中です。詳細は、<link href=\"https://github.com/cloudkeep/barbican/wiki/_pages\">https://github.com/cloudkeep/barbican/wiki/_pages</link>を参照してください。"
+
+#: ./doc/security-guide/ch048_key-management.xml11(para)
+msgid ""
+"It shall support the creation of keys, and their secure saving (with a "
+"service master-key). Some of the design questions still being debated are "
+"how much of the Key Management Interchange Protocol (KMIP) to support, key "
+"formats, and certificate management. The key manager will be pluggable to "
+"facilitate deployments that need a third-party Hardware Security Module "
+"(HSM)."
+msgstr "鍵管理は、鍵の作成と安全な保存'（'サービスマスター鍵付き'）'をサポートしなければなりません。いくつかの鍵管理における相互運用性プロトコル"
+
+#: ./doc/security-guide/ch048_key-management.xml12(para)
+msgid ""
+"OpenStack Block Storage, cinder, is the first service looking to integrate "
+"with the key manager to provide volume encryption."
+msgstr "OpenStack Block Storage (cinder) は、ボリュームの暗号化を提供するためにキーマネージャーとの統合を検討した最初のサービスです。"
+
+#: ./doc/security-guide/ch048_key-management.xml14(title)
+msgid "References:"
+msgstr "参考資料："
+
+#: ./doc/security-guide/ch048_key-management.xml16(link)
+msgid "Barbican"
+msgstr "Barbican"
+
+#: ./doc/security-guide/ch048_key-management.xml19(link)
+msgid "KMIP"
+msgstr "KMIP"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch013_node-bootstrapping.xml64(None)
+#: ./doc/security-guide/ch013_node-bootstrapping.xml69(None)
+msgid ""
+"@@image: 'static/node-provisioning-pxe.png'; "
+"md5=51b76c5aced74f935490b37ba921dc43"
+msgstr "@@image: 'static/node-provisioning-pxe.png'; md5=51b76c5aced74f935490b37ba921dc43"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml12(title)
+msgid "Integrity life-cycle"
+msgstr "完全性ライフサイクル"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml13(para)
+msgid ""
+"We define integrity life cycle as a deliberate process that provides "
+"assurance that we are always running the expected software with the expected"
+" configurations throughout the cloud. This process begins with secure "
+"bootstrapping and is maintained through configuration management and "
+"security monitoring. This chapter provides recommendations on how to "
+"approach the integrity life-cycle process."
+msgstr "OpenStack では、完全性ライフサイクルを「クラウド全体にわたって想定されているソフトウェアが想定されている設定で常に実行されることを保証する計画的なプロセス」と定義しています。このプロセスは、セキュアなブートストラッピングで開始し、設定管理およびセキュリティ監視の機能により維持されます。本章では、完全性ライフサイクルプロセスのアプローチ方法について説明します。"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml21(title)
+msgid "Secure bootstrapping"
+msgstr "セキュアブートストラップ"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml22(para)
+msgid ""
+"Nodes in the cloudincluding compute, storage, network, service, and hybrid "
+"nodesshould have an automated provisioning process. This ensures that nodes "
+"are provisioned consistently and correctly. This also facilitates security "
+"patching, upgrading, bug fixing, and other critical changes. Since this "
+"process installs new software that runs at the highest privilege levels in "
+"the cloud, it is important to verify that the correct software is installed."
+" This includes the earliest stages of the boot process."
+msgstr "クラウド内のノード (コンピュート、ストレージ、ネットワーク、サービス、およびハイブリッドのノードを含む) には、自動プロビジョニングプロセスを使用すべきです。このプロセスにより、ノードが一貫して正しくプロビジョニングされます。また、セキュリティパッチの適用、アップグレード、バグ修正、その他の重要な変更が円滑に行われます。このプロセスにより、クラウド内において最高権限で実行される新規ソフトウェアがインストールされるので、正しいソフトウェアがインストールされることを検証することが重要となります。これには、ブートプロセスの最初期段階が含まれます。"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml31(para)
+msgid ""
+"There are a variety of technologies that enable verification of these early "
+"boot stages. These typically require hardware support such as the trusted "
+"platform module (TPM), Intel Trusted Execution Technology (TXT), dynamic "
+"root of trust measurement (DRTM), and Unified Extensible Firmware Interface "
+"(UEFI) secure boot. In this book, we will refer to all of these collectively"
+" as <emphasis>secure boot technologies</emphasis>. We recommend using secure"
+" boot, while acknowledging that many of the pieces necessary to deploy this "
+"require advanced technical skills in order to customize the tools for each "
+"environment. Utilizing secure boot will require deeper integration and "
+"customization than many of the other recommendations in this guide. TPM "
+"technology, while common in most business class laptops and desktops for "
+"several years, and is now becoming available in servers together with "
+"supporting BIOS. Proper planning is essential to a successful secure boot "
+"deployment."
+msgstr "このような初期ブート段階の検証を可能にするさまざまな技術があります。通常は、Trusted Platform Module (TPM)、Intel Trusted Execution Technology (TXT)、Dynamic Root of Trust Measurement (DRTM)、Unified Extensible Firmware Interface (UEFI) などによるセキュアブートのハードウェアサポートが必要です。本ガイドでは、これらを総称して<emphasis>セキュアブートテクノロジー</emphasis>と呼びます。OpenStack ではセキュアブートの使用を推奨していますが、このデプロイに必要な諸作業には、各環境用にツールをカスタマイズするための高度の技術的スキルが必要である点を認識しています。セキュアブートの活用には、本ガイドに記載しているその他多くの推奨事項よりも深い統合とカスタマイズが必要になります。TPM テクノロジーはこの数年、大半のビジネスクラスのラップトップおよびデスクトップに通常搭載されていますが、BIOS のサポートとともにサーバーでも提供されるようになってきています。セキュアブートのデプロイには、適切な計画が不可欠です。"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml47(para)
+msgid ""
+"A complete tutorial on secure boot deployment is beyond the scope of this "
+"book. Instead, here we provide a framework for how to integrate secure boot "
+"technologies with the typical node provisioning process. For additional "
+"details, cloud architects should refer to the related specifications and "
+"software configuration manuals."
+msgstr "セキュアブートのデプロイに関する完全なチュートリアルは、本書の範囲外なので、その代わりとして、標準的なノードプロビジョニングプロセスにセキュアブートテクノロジーを統合する方法の枠組みを提供します。クラウドアーキテクトが更に詳しい情報を確認するには、関連する仕様およびソフトウェア設定のマニュアルを参照することをお勧めします。"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml54(title)
+msgid "Node provisioning"
+msgstr "ノードのプロビジョニング"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml55(para)
+msgid ""
+"Nodes should use Preboot eXecution Environment (PXE) for provisioning. This "
+"significantly reduces the effort required for redeploying nodes. The typical"
+" process involves the node receiving various boot stagesthat is "
+"progressively more complex software to execute from a server."
+msgstr "ノードは、プロビジョニングに Preboot eXecution Environment (PXE) を使用すべきです。これにより、ノードの再デプロイに必要な作業が大幅に軽減されます。標準的なプロセスでは、ノードがサーバーからさまざまなブート段階 (実行するソフトウェアが徐々に複雑化) を受信する必要があります。"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml72(para)
+msgid ""
+"We recommend using a separate, isolated network within the management "
+"security domain for provisioning. This network will handle all PXE traffic, "
+"along with the subsequent boot stage downloads depicted above. Note that the"
+" node boot process begins with two insecure operations: DHCP and TFTP. Then "
+"the boot process downloads over SSL the remaining information required to "
+"deploy the node. This information might include an initramfs and a kernel. "
+"This concludes by downloading the remaining information needed to deploy the"
+" node. This may be an operating system installer, a basic install managed by"
+" <link href=\"http://www.opscode.com/chef/\">Chef</link> or <link "
+"href=\"https://puppetlabs.com/\">Puppet</link>, or even a complete file "
+"system image that is written directly to disk."
+msgstr "プロビジョニングには、管理セキュリティドメイン内の別個の分離したネットワークを使用することを推奨します。このネットワークは、上記に示した後続のブート段階のダウンロードに加えて、すべての PXE トラフィックを処理します。 ノードのブートプロセスは、安全性の低い DHCP および TFTP の 2 つの操作で開始する点に注意してください。次にブートプロセスは、ノードのデプロイに必要な残りの情報を SSL を介してダウンロードします。この情報には、initramfs とカーネルが含まれる場合があります。このプロセスは、ノードのデプロイに必要な残りの情報のダウンロードで終了します。これは、オペレーティングシステムのインストーラー、<link href=\"http://www.opscode.com/chef/\">Chef</link> または <link href=\"https://puppetlabs.com/\">Puppet</link> によって管理される基本インストール、またはディスクに直接書き込まれた完全なファイルシステムイメージの場合もあります。"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml86(para)
+msgid ""
+"While utilizing SSL during the PXE boot process is somewhat more "
+"challenging, common PXE firmware projects, such as iPXE, provide this "
+"support. Typically this involves building the PXE firmware with knowledge of"
+" the allowed SSL certificate chain(s) so that it can properly validate the "
+"server certificate. This raises the bar for an attacker by limiting the "
+"number of insecure, plain text network operations."
+msgstr "PXE ブートプロセス中に SSL を活用するのは若干困難ですが、iPXE などの一般的な PXE ファームウェアプロジェクトは、この機能をサポートしています。通常、この作業には、サーバーの証明書を適切に検証するための許可済み SSL 証明書チェーンについての知識を活用した PXE ファームウェア構築が伴います。これにより、安全性の低いプレーンテキストのネットワーク操作数が制限されるので、攻撃者に対するセキュリティレベルが高くなります。."
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml96(title)
+msgid "Verified boot"
+msgstr "検証済みブート"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml97(para)
+msgid ""
+"In general, there are two different strategies for verifying the boot "
+"process. Traditional <emphasis>secure boot</emphasis> will validate the code"
+" run at each step in the process, and stop the boot if code is incorrect. "
+"<emphasis>Boot attestation</emphasis> will record which code is run at each "
+"step, and provide this information to another machine as proof that the boot"
+" process completed as expected. In both cases, the first step is to measure "
+"each piece of code before it is run. In this context, a measurement is "
+"effectively a SHA-1 hash of the code, taken before it is executed. The hash "
+"is stored in a platform configuration register (PCR) in the TPM."
+msgstr "ブートプロセスの検証には、通常 2 つの異なる戦略があります。従来の<emphasis>セキュアブート</emphasis>は、プロセスの各ステップに実行されるコードを検証し、コードが正しくない場合にはブートを中止します。<emphasis>ブートアテステーション</emphasis>は、どのステップでどのコードが実行されるかを記録し、ブートプロセスが想定通りに完了した証拠として、この情報を別のマシンに提供します。いずれのケースにおいても、第 1 のステップでは、実行前にコードの各要素を計測します。この場合、計測値は実質的にはコードの SHA-1 ハッシュで、実行前に取得されます。 このハッシュは、TPM 内の Platform Configuration Register (PCR) に保管されます。"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml109(para)
+msgid "Note: SHA-1 is used here because this is what the TPM chips support."
+msgstr "注記:  ここで SHA-1 を使用するのは、TPM チップが対応しているためです。"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml111(para)
+msgid ""
+"Each TPM has at least 24 PCRs. The TCG Generic Server Specification, v1.0, "
+"March 2005, defines the PCR assignments for boot-time integrity "
+"measurements. The table below shows a typical PCR configuration. The context"
+" indicates if the values are determined based on the node hardware "
+"(firmware) or the software provisioned onto the node. Some values are "
+"influenced by firmware versions, disk sizes, and other low-level "
+"information. Therefore, it is important to have good practices in place "
+"around configuration management to ensure that each system deployed is "
+"configured exactly as desired."
+msgstr "各 TPM には少なくとも 24 の PCR が含まれます。TCG Generic Server Specification ( v1.0、2005 年 3 月版) には、ブート時の完全性計測のための PCR の割り当てが定義されています。以下の表には、標準的な PCR 設定を記載しています。コンテキストには、その値がノードのハードウェア (ファームウェア) をベースに決定されるか、ノードにプロビジョニングされているソフトウェアをベースに決定されるかを示しています。一部の値は、ファームウェアのバージョンやディスクサイズ、その他の低レベルの情報によって影響を受けます。このため、設定管理の適切なプラクティスを整備し、デプロイするシステムが要望通りに設定されるようにしておくことが重要となります。"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml131(emphasis)
+msgid "Register"
+msgstr "レジスター"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml132(emphasis)
+msgid "What is measured"
+msgstr "計測の対象"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml135(emphasis)
+msgid "Context"
+msgstr "コンテキスト"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml138(para)
+msgid "PCR-00"
+msgstr "PCR-00"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml139(para)
+msgid ""
+"Core Root of Trust Measurement (CRTM), BIOS code, Host platform extensions"
+msgstr "Core Root of Trust Measurement (CRTM)、 BIOS コード、ホストプラットフォームの拡張機能"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml141(para)
+#: ./doc/security-guide/ch013_node-bootstrapping.xml146(para)
+#: ./doc/security-guide/ch013_node-bootstrapping.xml151(para)
+#: ./doc/security-guide/ch013_node-bootstrapping.xml156(para)
+msgid "Hardware"
+msgstr "ハードウェア"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml144(para)
+msgid "PCR-01"
+msgstr "PCR-01"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml145(para)
+msgid "Host platform configuration"
+msgstr "ハードウェアプラットフォームの設定"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml149(para)
+msgid "PCR-02"
+msgstr "PCR-02"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml150(para)
+msgid "Option ROM code"
+msgstr "オプションの ROM コード"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml154(para)
+msgid "PCR-03"
+msgstr "PCR-03"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml155(para)
+msgid "Option ROM configuration and data"
+msgstr "オプションの ROM 設定およびデータ"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml159(para)
+msgid "PCR-04"
+msgstr "PCR-04"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml160(para)
+msgid "Initial Program Loader (IPL) code. For example, master boot record."
+msgstr "Initial Program Loader (IPL) コード (例: マスターブートレコード) "
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml162(para)
+#: ./doc/security-guide/ch013_node-bootstrapping.xml167(para)
+#: ./doc/security-guide/ch013_node-bootstrapping.xml172(para)
+#: ./doc/security-guide/ch013_node-bootstrapping.xml177(para)
+#: ./doc/security-guide/ch013_node-bootstrapping.xml183(para)
+#: ./doc/security-guide/ch013_node-bootstrapping.xml188(para)
+#: ./doc/security-guide/ch013_node-bootstrapping.xml193(para)
+msgid "Software"
+msgstr "ソフトウェア"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml165(para)
+msgid "PCR-05"
+msgstr "PCR-05"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml166(para)
+msgid "IPL code configuration and data"
+msgstr "IPL コードの設定およびデータ"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml170(para)
+msgid "PCR-06"
+msgstr "PCR-06"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml171(para)
+msgid "State transition and wake events"
+msgstr "状態遷移とウェイクイベント"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml175(para)
+msgid "PCR-07"
+msgstr "PCR-07"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml176(para)
+msgid "Host platform manufacturer control"
+msgstr "ホストプラットフォームのメーカーによる制御"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml180(para)
+msgid "PCR-08"
+msgstr "PCR-08"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml181(para)
+msgid "Platform specific, often kernel, kernel extensions, and drivers"
+msgstr "プラットフォーム固有、多くの場合はカーネル、カーネル拡張機能、ドライバー"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml186(para)
+msgid "PCR-09"
+msgstr "PCR-09"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml187(para)
+msgid "Platform specific, often Initramfs"
+msgstr "プラットフォーム固有、多くの場合は  Initramfs"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml191(para)
+msgid "PCR-10 to PCR-23"
+msgstr "PCR-10 から PCR-23"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml192(para)
+msgid "Platform specific"
+msgstr "プラットフォーム固有"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml198(para)
+msgid ""
+"At the time of this writing, very few clouds are using secure boot "
+"technologies in a production environment. As a result, these technologies "
+"are still somewhat immature. We recommend planning carefully in terms of "
+"hardware selection. For example, ensure that you have a TPM and Intel TXT "
+"support. Then verify how the node hardware vendor populates the PCR values. "
+"For example, which values will be available for validation. Typically the "
+"PCR values listed under the software context in the table above are the ones"
+" that a cloud architect has direct control over. But even these may change "
+"as the software in the cloud is upgraded. Configuration management should be"
+" linked into the PCR policy engine to ensure that the validation is always "
+"up to date."
+msgstr "本ガイドの執筆時点では、実稼働環境でセキュアブートテクノロジーを使用するクラウドはほとんどありませんでした。このため、これらのテクノロジーはまだ若干未成熟な状態です。ハードウェアは、慎重に計画した上で選択することを推奨します (例: TPM および Intel TXT の対応を確認するなど)。次に、ノードのハードウェアベンダーが PCR 値をどのように事前設定しているかを検証します (例: どの値を検証できるか)。上記の表のコンテキストにソフトウェアと記載されている PCR 値は通常、クラウドアーキテクトが直接コントロールできます。ただし、これらの値は、クラウド内のソフトウェアをアップグレードすると変更される場合があります。設定管理は、PCR ポリシーエンジン内にリンクして、検証を常に最新の状態 に確保すべきです。"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml211(para)
+msgid ""
+"Each manufacturer must provide the BIOS and firmware code for their servers."
+" Different servers, hypervisors, and operating systems will choose to "
+"populate different PCRs. In most real world deployments, it will be "
+"impossible to validate every PCR against a known good quantity (\"golden "
+"measurement\"). Experience has shown that, even within a single vendor's "
+"product line, the measurement process for a given PCR may not be consistent."
+" We recommend establishing a baseline for each server and monitoring the PCR"
+" values for unexpected changes. Third-party software may be available to "
+"assist in the TPM provisioning and monitoring process, depending upon your "
+"chosen hypervisor solution."
+msgstr "各メーカーは、サーバーの BIOS とファームウェアのコードを提供する必要があります。サーバー、ハイパーバイザー、オペレーティングシステムによって、事前設定される PCR 値の選択が異なります。実際のデプロイメントではほとんどの場合、既知の適切な量 (「黄金の計測値」) と対照して各 PCR を検証することは不可能です。単一のベンダー の製品ラインの場合でも、一定の PCR の計測プロセスに一貫性がない場合があることが、経験により実証されています。各サーバーに基準値を定め、 PCR 値の予期せぬ変化を監視することを推奨します。選択したハイパーバイザーソリューションによっては、TPM プロビジョニングおよび監視プロセスを支援する サードパーティー製のソフトウェアが提供されている可能性があります。"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml223(para)
+msgid ""
+"The initial program loader (IPL) code will most likely be the PXE firmware, "
+"assuming the node deployment strategy outlined above. Therefore, the secure "
+"boot or boot attestation process can measure all of the early stage boot "
+"code, such as, bios, firmware, and the like, the PXE firmware, and the node "
+"kernel. Ensuring that each node has the correct versions of these pieces "
+"installed provides a solid foundation on which to build the rest of the node"
+" software stack."
+msgstr "上記のノードデプロイメントの戦略を前提とすると、Initial Program Loader (IPL) コードは、PXE ファームウェアである可能性が最も高く、このため、セキュアブートまたはブートアテステーションプロセスで、すべての初期段階のブートコード  (例: BIOS、ファームウェアなど)、PXE ファームウェア、およびノードのカーネルを計測することができます。各ノードにこれらの正しいバージョンがインストールされていることを確認することにより、残りのノードソフトウェアスタックを構築する土台となる強固な基盤が提供されます。"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml231(para)
+msgid ""
+"Depending on the strategy selected, in the event of a failure the node will "
+"either fail to boot or it can report the failure back to another entity in "
+"the cloud. For secure boot, the node will fail to boot and a provisioning "
+"service within the management security domain must recognize this and log "
+"the event. For boot attestation, the node will already be running when the "
+"failure is detected. In this case the node should be immediately quarantined"
+" by disabling its network access. Then the event should be analyzed for the "
+"root cause. In either case, policy should dictate how to proceed after a "
+"failure. A cloud may automatically attempt to re-provision a node a certain "
+"number of times. Or it may immediately notify a cloud administrator to "
+"investigate the problem. The right policy here will be deployment and "
+"failure mode specific."
+msgstr "選択した戦略に応じて、障害発生時にノードがブートに失敗するか、クラウド内の別のエンティティに障害を報告することができます。セキュアブートの場合には、ノードがブートに失敗し、管理セキュリティドメイン内のプロビジョニングサービスがこの問題を認識してイベントログを記録する必要があります。ブートアテステーションの場合には、障害検出時にはノードがすでに稼働している状態です。この場合、ネットワークアクセスを無効にすることによってノードの検疫を直ちに行った後に、イベントを解析して根本原因を特定するべきです。いずれの場合も、ポリシーにより、障害発生後の対処方法を指示する必要があります。クラウドが、特定の回数、ノードの再プロビジョニングを自動的に試みるようにしたり、問題を調査するようにクラウド管理者に直ちに通知するようにすることができます。この場合に適正となるポリシーは、デプロイメントと障害のモードによって異なります。 "
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml247(title)
+msgid "Node hardening"
+msgstr "ノードのセキュリティ強化機能"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml248(para)
+msgid ""
+"At this point we know that the node has booted with the correct kernel and "
+"underlying components. There are many paths for hardening a given operating "
+"system deployment. The specifics on these steps are outside of the scope of "
+"this book. We recommend following the guidance from a hardening guide "
+"specific to your operating system. For example, the <link "
+"href=\"http://iase.disa.mil/stigs/\">security technical implementation "
+"guides</link> (STIG) and the <link "
+"href=\"http://www.nsa.gov/ia/mitigation_guidance/security_configuration_guides/\">NSA"
+" guides</link> are useful starting places."
+msgstr "この時点で、ノードが正しいカーネルと配下のコンポーネントでブートしていることが分かります。オペレーティングシステムのデプロイメントのセキュリティを強化するには、数多くの方法があります。これらの手順についての詳しい説明は本書の範囲外です。お使いのオペレーティングシステム固有のセキュリティ強化ガイドのアドバイスに従うことを推奨します。例えば、<link href=\"http://iase.disa.mil/stigs/\">security technical implementation guides</link> (STIG) や <link href=\"http://www.nsa.gov/ia/mitigation_guidance/security_configuration_guides/\">NSA guides</link> を最初に参考にすると役立ちます。"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml258(para)
+msgid ""
+"The nature of the nodes makes additional hardening possible. We recommend "
+"the following additional steps for production nodes:"
+msgstr "ノードはその性質上、追加のセキュリティ強化が可能です。実稼働用のノードには、次の追加手順に従うことを推奨します。"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml263(para)
+msgid ""
+"Use a read-only file system where possible. Ensure that writeable file "
+"systems do not permit execution. This can be handled through the mount "
+"options provided in <filename>/etc/fstab</filename>."
+msgstr "可能な場合には、読み取り専用のファイルシステムを使用します。書き込みが可能なファイルシステムでは、実行が許可されないようにします。これは、<filename>/etc/fstab</filename> で指定するマウントオプションを使用して対処することが可能です。"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml269(para)
+msgid ""
+"Use a mandatory access control policy to contain the instances, the node "
+"services, and any other critical processes and data on the node. See the "
+"discussions on sVirt / SELinux and AppArmor below."
+msgstr "強制アクセス制御ポリシーを使用して、インスタンス、ノードサービス、その他の重要なプロセスおよびノード上のデータが含まれるようにします。以下に記載の sVirt / SELinux および AppArmor についての説明を参照してください。"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml275(para)
+msgid ""
+"Remove any unnecessary software packages. This should result in a very "
+"stripped down installation because a compute node has a relatively small "
+"number of dependencies."
+msgstr "不要なソフトウェアパッケージは削除します。これにより、コンピュートノードの依存関係が比較的少なくなるので、インストールを小さく絞ることができます。"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml281(para)
+msgid ""
+"Finally, the node kernel should have a mechanism to validate that the rest "
+"of the node starts in a known good state. This provides the necessary link "
+"from the boot validation process to validating the entire system. The steps "
+"for doing this will be deployment specific. As an example, a kernel module "
+"could verify a hash over the blocks comprising the file system before "
+"mounting it using <link "
+"href=\"https://code.google.com/p/cryptsetup/wiki/DMVerity\">dm-"
+"verity</link>."
+msgstr "最後に、ノードのカーネルには、残りのノードが既知の良好な状態で起動することを検証するメカニズムを取り入れるべきです。これにより、ブート検証プロセスからシステム全体の検証に至るまでの必要なリンクが提供されます。手順はデプロイメントによって異なります。例えば、カーネルモジュールは、<link href=\"https://code.google.com/p/cryptsetup/wiki/DMVerity\">dm-verity</link> を使用して、ファイルシステムをマウントする前に、そのファイルシステムを構成するブロック上のハッシュを検証することができます。"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml293(title)
+msgid "Runtime verification"
+msgstr "ランタイムの検証"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml294(para)
+msgid ""
+"Once the node is running, we need to ensure that it remains in a good state "
+"over time. Broadly speaking, this includes both configuration management and"
+" security monitoring. The goals for each of these areas are different. By "
+"checking both, we achieve higher assurance that the system is operating as "
+"desired. We discuss configuration management in the management section, and "
+"security monitoring below."
+msgstr "ノードが稼働したら、長時間にわたって良好な状態で稼働を継続するように確保する必要があります。大まかに言うと、これには設定管理とセキュリティ監視が含まれます。これらの各領域の目標は異なります。両方を確認することにより、システムが希望通りに稼働していることをより確実に保証します。設定管理については、管理のセクションおよび次のセキュリティ監視で説明します。"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml302(title)
+msgid "Intrusion detection system"
+msgstr "侵入検知システム"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml303(para)
+msgid ""
+"Host-based intrusion detection tools are also useful for automated "
+"validation of the cloud internals. There are a wide variety of host-based "
+"intrusion detection tools available. Some are open source projects that are "
+"freely available, while others are commercial. Typically these tools analyze"
+" data from a variety of sources and produce security alerts based on rule "
+"sets and/or training. Typical capabilities include log analysis, file "
+"integrity checking, policy monitoring, and rootkit detection. More advanced "
+"-- often custom -- tools can validate that in-memory process images match "
+"the on-disk executable and validate the execution state of a running "
+"process."
+msgstr "ホストベースの侵入検知ツールは、クラウド内部の検証の自動化にも役立ちます。ホストベースの侵入検知ツールにはさまざまな種類があります。オープンソースで自由に利用できるツールもあれば、商用のツールもあります。通常、これらのツールは、さまざまなソースからデータを分析し、ルールセットやトレーニングに基づいてセキュリティ警告を出します。標準的な機能には、ログ解析、ファイルの完全性チェック、ポリシー監視、ルートキット検出などがあります。また、より高度なツール (カスタムの場合が多い) を使用すると、インメモリープロセスイメージがオンディスクの実行可能ファイルと一致するかどうかを確認して、実行中のプロセスの実行状態を検証することができます。"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml315(para)
+msgid ""
+"One critical policy decision for a cloud architect is what to do with the "
+"output from a security monitoring tool. There are effectively two options. "
+"The first is to alert a human to investigate and/or take corrective action. "
+"This could be done by including the security alert in a log or events feed "
+"for cloud administrators. The second option is to have the cloud take some "
+"form of remedial action automatically, in addition to logging the event. "
+"Remedial actions could include anything from re-installing a node to "
+"performing a minor service configuration. However, automated remedial action"
+" can be challenging due to the possibility of false positives."
+msgstr "セキュリティ監視ツールの出力の処理方法は、クラウドアーキテクトにとっての重要なポリシー決定の一つです。オプションは実質的に 2 つあります。第 1 のオプションは、問題を調査して修正措置を取るように、人間に警告を発する方法です。これは、クラウド管理者向けのログまたはイベントのフィードにセキュリティ警告を組み込むことによって可能となります。第 2 のオプションは、イベントのログ記録に加えて、クラウドが何らかの形の修復措置を自動的に実行するように設定する方法です。修復措置にはノードの再インストールから、マイナーなサービス設定の実行まで含めることができます。ただし、自動修復措置は、誤検知の可能性があるため、困難となる場合があります。"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml326(para)
+msgid ""
+"False positives occur when the security monitoring tool produces a security "
+"alert for a benign event. Due to the nature of security monitoring tools, "
+"false positives will most certainly occur from time to time. Typically a "
+"cloud administrator can tune security monitoring tools to reduce the false "
+"positives, but this may also reduce the overall detection rate at the same "
+"time. These classic trade-offs must be understood and accounted for when "
+"setting up a security monitoring system in the cloud."
+msgstr "誤検知は、セキュリティ監視ツールが害のないイベントのセキュリティ警告を出した場合に発生します。セキュリティ警告ツールの性質上、時々誤検知が発生することは間違いありません。通常、クラウド管理者は、セキュリティ監視ツールを微調整して、誤検知を少なくすることができますが、これにより、全体的な検知率も同時に下がる場合があります。このような典型的トレードオフを理解し、クラウドにセキュリティ管理システムをセットアップする際には考慮に入れる必要があります。"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml335(para)
+msgid ""
+"The selection and configuration of a host-based intrusion detection tool is "
+"highly deployment specific. We recommend starting by exploring the following"
+" open source projects which implement a variety of host-based intrusion "
+"detection and file monitoring features."
+msgstr "ホストベースの侵入検知ツールの選択と設定はデプロイメントによって大幅に異なります。多様なホストベースの侵入検知/ファイル監視機能を実装する以下のオープンソースプロジェクトの検討から開始することをお勧めします。"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml343(link)
+msgid "OSSEC"
+msgstr "OSSEC"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml347(link)
+msgid "Samhain"
+msgstr "Samhain"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml352(link)
+msgid "Tripwire"
+msgstr "Tripwire"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml356(link)
+msgid "AIDE"
+msgstr "AIDE"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml359(para)
+msgid ""
+"Network intrusion detection tools complement the host-based tools. OpenStack"
+" doesn't have a specific network IDS built-in, but OpenStack Networking "
+"provides a plug-in mechanism to enable different technologies through the "
+"Networking API. This plug-in architecture will allow tenants to develop API "
+"extensions to insert and configure their own advanced networking services "
+"like a firewall, an intrusion detection system, or a VPN between the VMs."
+msgstr "ネットワーク侵入検知ツールは、ホストベースのツールを補完します。OpenStack には、特定のネットワーク IDS は組み込まれていませんが、OpenStack Networking は、Networking API を使用して異なるテクノロジーを有効にするプラグインメカニズムを提供しています。このプラグインのアーキテクチャーにより、テナントは API 拡張機能を開発して、ファイアウォール、侵入検知システム、仮想マシン間の VPN などの独自の高度なネットワークサービスを挿入/設定することができます。"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml367(para)
+msgid ""
+"Similar to host-based tools, the selection and configuration of a network-"
+"based intrusion detection tool is deployment specific. <link "
+"href=\"http://www.snort.org/\">Snort</link> is the leading open source "
+"networking intrusion detection tool, and a good starting place to learn "
+"more."
+msgstr "ホストベースのツールと同様に、ネットワークベースの侵入検知ツールはデプロイメントによって異なります。 <link href=\"http://www.snort.org/\">Snort</link> は、先進的なオープンソースのネットワーク侵入検知ツールです。このツールを起点として、更に知識を深めてゆくとよいでしょう。"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml373(para)
+msgid ""
+"There are a few important security considerations for network and host-based"
+" intrusion detection systems."
+msgstr "ネットワークおよびホストベースの侵入検知システムには、いくつかの重要なセキュリティ課題があります。"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml377(para)
+msgid ""
+"It is important to consider the placement of the Network IDS on the cloud "
+"(for example, adding it to the network boundary and/or around sensitive "
+"networks). The placement depends on your network environment but make sure "
+"to monitor the impact the IDS may have on your services depending on where "
+"you choose to add it. Encrypted traffic, such as SSL, cannot generally be "
+"inspected for content by a Network IDS. However, the Network IDS may still "
+"provide some benefit in identifying anomalous unencrypted traffic on the "
+"network."
+msgstr "クラウドにネットワーク IDS の配置を検討することは重要です  (例: ネットワーク境界や機密性の高いのネットワークに追加するなど)。 配置はネットワーク環境によって異なりますが、追加する場所によって IDS がサービスにもたらす可能性のある影響を確実に監視するようにしてください。通常 ネットワーク IDS は、SSL などの暗号化トラフィックを調査することはできませんが、ネットワーク上の異常な非暗号化トラフィックを特定するメリットを提供することができます。"
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml389(para)
+msgid ""
+"In some deployments it may be required to add host-based IDS on sensitive "
+"components on security domain bridges. A host-based IDS may detect anomalous"
+" activity by compromised or unauthorized processes on the component. The IDS"
+" should transmit alert and log information on the Management network."
+msgstr "一部のデプロイメントでは、ホストベースの IDS をセキュリティドメインブリッジ上の機密性の高いコンポーネントに追加する必要がある場合があります。ホストベースの IDS は、そのコンポーネント上の侵害された、あるいは許可されていないプロセスによる異常なアクティビティを検知することができます。IDS は管理ネットワーク上で警告およびログ情報を伝送すべきです。"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml8(title)
+msgid "Networking services"
+msgstr "ネットワークサービス"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml9(para)
+msgid ""
+"In the initial architectural phases of designing your OpenStack Network "
+"infrastructure it is important to ensure appropriate expertise is available "
+"to assist with the design of the physical networking infrastructure, to "
+"identify proper security controls and auditing mechanisms."
+msgstr "あなたの OpenStack ネットワークインフラデザインの概要設計段階では、適切なセキュリティ管理・監査機構を確認する為、物理ネットワークインフラ設計で支援する適切な専門技術が間違いなく利用できる事は重要です。"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml10(para)
+msgid ""
+"OpenStack Networking adds a layer of virtualized network services - giving "
+"tenants the capability to architect their own, virtual networks. These "
+"virtualized services are not as currently as mature as their traditional "
+"networking counterparts. It is important to be aware of the current state of"
+" these virtualized services and what controls may need to be implemented at "
+"the virtualized and traditional network boundary."
+msgstr "OpenStack Networking は（テナントに自身の仮想ネットワークを設計する為の機能を提供する）仮想ネットワークサービスのレイヤを追加します。これらの仮想化サービスは、現時点で従来のネットワークコンポーネントのように成熟していません。これらの仮想化技術の現状と、仮想ネットワークと従来のネットワーク境界でどのコントロールを実装する必要があるだろうというを知っておく事は重要です。"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml12(title)
+msgid "L2 isolation using VLANs and tunneling"
+msgstr "VLAN とトンネリングを使用した L2 分断"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml13(para)
+msgid ""
+"OpenStack networking can employ two different mechanisms for traffic "
+"segregation on a per tenant/network combination: VLANs (IEEE 802.1Q tagging)"
+" or L2 tunnels using GRE encapsulation. Which method you choose for traffic "
+"segregation and isolation is determined by the scope and scale of your "
+"OpenStack deployment."
+msgstr "OpenStack Networking はテナント／ネットワークの組合せ単位で通信を分断する為の、 VLANs (IEEE 802.1Q タギング) 又は GRE カプセル化を使用した L2 トンネルという２つの異なる機構を使用する事が出来ます。通信の分断と独立用にあなたが選択する方式は、あなたの OpenStack デプロイの範囲と規模に依存します。"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml15(title)
+msgid "VLANs"
+msgstr "VLAN"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml16(para)
+msgid ""
+"VLANs are realized as packets on a specific physical network containing IEEE"
+" 802.1Q headers with a specific VLAN ID (VID) field value. VLAN networks "
+"sharing the same physical network are isolated from each other at L2, and "
+"can even have overlapping IP address spaces. Each distinct physical network "
+"supporting VLAN networks is treated as a separate VLAN trunk, with a "
+"distinct space of VID values. Valid VID values are 1 through 4094."
+msgstr "VLAN は特別な VLAN ID (VID) フィールド値を持つ IEEE 802.1Q ヘッダを含む特別な物理ネットワーク上のパケットを実現します。同じ物理ネットワークを共有する VLAN ネットワーク群は、L2 において相互から独立しており、重複する IP アドレス空間を持つ事すら可能です。VLAN ネットワークに対応した各個別の物理ネットワークは、独自の VID 値を持つ独立した VLAN トランクとして扱われます。有効な VID 値は1～4094です。"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml17(para)
+msgid ""
+"VLAN configuration complexity depends on your OpenStack design requirements."
+" In order to allow OpenStack Networking to efficiently use VLANs, you must "
+"allocate a VLAN range (one for each tenant) and turn each compute node "
+"physical switch port into a VLAN trunk port."
+msgstr "VLAN 設定の複雑さはあなたの OpenStack 設計要件に依存します。OpenStack Networking がVLAN を効率良く使用できるようにする為に、VLAN 範囲を (各テナントに１つ) 割り当てて、各 compute ノードの物理スイッチポートを VLAN トランクポートに変更する必要があります。"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml19(para)
+msgid ""
+"NOTE: If you intend for your network to support more than 4094 tenants VLAN "
+"is probably not the correct option for you as multiple 'hacks' are required "
+"to extend the VLAN tags to more than 4094 tenants."
+msgstr "注意：あなたのネットワークを4095 以上のテナントに対応するようにしたい場合、VLAN はあなたにとって多分正しい選択肢ではありません。なぜなら、4095 以上に VLAN タグを拡張する為の複数の「改造」が必要だからです。"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml23(title)
+msgid "L2 tunneling"
+msgstr "L2 トンネリング"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml24(para)
+msgid ""
+"Network tunneling encapsulates each tenant/network combination with a unique"
+" \"tunnel-id\" that is used to identify the network traffic belonging to "
+"that combination. The tenant's L2 network connectivity is independent of "
+"physical locality or underlying network design. By encapsulating traffic "
+"inside IP packets, that traffic can cross Layer-3 boundaries, removing the "
+"need for preconfigured VLANs and VLAN trunking. Tunneling adds a layer of "
+"obfuscation to network data traffic, reducing the visibility of individual "
+"tenant traffic from a monitoring point of view."
+msgstr "Network tunneling encapsulates each tenant/network combination with a unique \"tunnel-id\" \nネットワークトンネリングは、固有の「トンネルID」を用いてテナント／ネットワークの各組合せをカプセル化します。これは、上記の組合せに属するネットワーク通信を独立させる為に使用されます。テナントの L2 ネットワーク接続は、物理的配置や下層のネットワーク設計から独立しています。IP パケット内で通信をカプセル化する事により、通信はレイヤ３境界を越える事ができ、VLAN や VLAN とランキングの事前設定の必要が無くなります。トンネリングはネットワークのデータ通信に不明瞭なレイヤを追加し、監視の観点で個々のテナント通信の可視性を低下させます。"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml25(para)
+msgid ""
+"OpenStack Networking currently only supports GRE encapsulation with planned "
+"future support of VXLAN due in the Havana release."
+msgstr "OpenStack Networking は現在 GRE カプセル化のみサポートしており、Havana リリースで VXLAN をサポートする計画があります。"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml26(para)
+msgid ""
+"The choice of technology to provide L2 isolation is dependent upon the scope"
+" and size of tenant networks that will be created in your deployment. If "
+"your environment has limited VLAN ID availability or will have a large "
+"number of L2 networks, it is our recommendation that you utilize tunneling."
+msgstr "L2 分断を提供する技術の選択は、あなたのデプロイで作成される予定のテナントネットワークの範囲とサイズに依存します。あなたの環境が VLAN ID の利用で制限がある場合や、大多数の L2 ネットワークが見込まれる場合、トンネリングの使用を推奨します。"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml30(title)
+msgid "Network services"
+msgstr "ネットワークサービス"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml31(para)
+msgid ""
+"The choice of tenant network isolation affects how the network security and "
+"control boundary is implemented for tenant services. The following "
+"additional network services are either available or currently under "
+"development to enhance the security posture of the OpenStack network "
+"architecture."
+msgstr "テナントネットワーク分断の選択はネットワークセキュリティと制御境界をどのように実装するかに影響します。\n以下の追加ネットワークサービスは利用可能か、OpenStack ネットワークアーキテクチャのセキュリティポーズを拡張する為の開発中かのいずれかです。"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml33(title)
+msgid "Access control lists"
+msgstr "アクセス制御リスト"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml34(para)
+msgid ""
+"OpenStack Compute supports tenant network traffic access controls directly "
+"when deployed with the legacy nova-network service, or may defer access "
+"control to the OpenStack Networking service."
+msgstr "OpenStack Compute は、旧式の nova-network サービスでデプロイする場合、テナントネットワーク通信のアクセス制御を直接サポートします。又は、OpenStack Networking サービスにアクセス制御を任せる事も出来ます。"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml35(para)
+msgid ""
+"Note, legacy nova-network security groups are applied to all virtual "
+"interface ports on an instance using IPTables."
+msgstr "注：旧式の nova-network セキュリティグループは、Iptables を使用してインスタンス上の全ての仮想インターフェースポートに適用されます。"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml36(para)
+msgid ""
+"Security groups allow administrators and tenants the ability to specify the "
+"type of traffic, and direction (ingress/egress) that is allowed to pass "
+"through a virtual interface port. Security groups rules are stateful L2-L4 "
+"traffic filters."
+msgstr "セキュリティグループでは、管理者とテナントが仮想インターフェースポート通過を許可する通信のタイプと方向（内向き／外向き）を指定できるようになっています。"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml37(para)
+msgid ""
+"It is our recommendation that you enable security groups through OpenStack "
+"Networking."
+msgstr "OpenStack Networking 経由でセキュリティグループを有効にする事をお勧めします。"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml41(title)
+msgid "L3 routing and NAT"
+msgstr "L3 ルーティングおよび NAT"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml42(para)
+msgid ""
+"OpenStack Networking routers can connect multiple L2 networks, and can also "
+"provide a <emphasis>gateway</emphasis> that connects one or more private L2 "
+"networks to a shared <emphasis>external</emphasis> network, such as a public"
+" network for access to the Internet."
+msgstr "OpenStack Networking のルータは複数の L2 ネットワークを接続でき、１つ以上のプライベート L2 ネットワークを共有<emphasis>外部</emphasis>ネットワーク（インターネットアクセス用のパブリックネットワーク等）に接続する<emphasis>ゲートウェイ</emphasis>を提供する事も出来ます。"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml43(para)
+msgid ""
+"The L3 router provides basic Network Address Translation (NAT) capabilities "
+"on <emphasis>gateway</emphasis> ports that uplink the router to external "
+"networks. This router SNATs (Static NAT) all traffic by default, and "
+"supports floating IPs, which creates a static one-to-one mapping from a "
+"public IP on the external network to a private IP on one of the other "
+"subnets attached to the router."
+msgstr "L3 ルータは、外部ネットワークへのルータに接続する<emphasis>ゲートウェイ</emphasis>ポート上の基本的なネットワークアドレス変換 (NAT) 機能を提供します。このルータはデフォルトで全てのネットワークの SNAT (静的 NAT) を行います。これは、外部ネットワーク上のパブリック IP アドレスから、ルータにアタッチされた他の１サブネットのプライベート IP アドレスへ変換する静的な１対１マッピングを作成します。"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml44(para)
+msgid ""
+"It is our recommendation to leverage per tenant L3 routing and Floating IPs "
+"for more granular connectivity of tenant VMs."
+msgstr "テナント VM のより粒度の細かいテナント L3 ルーティングとフローティング IP 単位で設定する事をお勧めします。"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml47(title)
+msgid "Quality of Service (QoS)"
+msgstr "サービス品質(QoS)"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml48(para)
+msgid ""
+"The ability to set QoS on the virtual interface ports of tenant instances is"
+" a current deficiency for OpenStack Networking. The application of QoS for "
+"traffic shaping and rate-limiting at the physical network edge device is "
+"insufficient due to the dynamic nature of workloads in an OpenStack "
+"deployment and can not be leveraged in the traditional way. QoS-as-a-Service"
+" (QoSaaS) is currently in development for the OpenStack Networking Havana "
+"release as an experimental feature. QoSaaS is planning to provide the "
+"following services:"
+msgstr "現在の OpenStack Networking にはテナントインスタンスの仮想インターフェースポート上の QoS 設定機能が欠如しています。物理ネットワークエッジデバイスにおけるトラフィックシェーピングやレートリミットの為の QoS 活用は、OpenStack デプロイ中のワークロードの動的な性質の為に実装されておらず、従来の方法では設定できません。QoS-as-a-Service (QoSaaS) は実験的な機能として現在 OpenStack Networking Havana リリース用に開発中です。QoSaaS は以下のサービスを提供する計画です。"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml50(para)
+msgid "Traffic shaping through DSCP markings"
+msgstr "DSCP マーキングによるトラフィックシェーピング"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml53(para)
+msgid "Rate-limiting on a per port/network/tenant basis."
+msgstr "ポート・ネットワーク・テナント単位のレートリミット"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml56(para)
+msgid "Port mirroring (through open source or third-party plug-ins)"
+msgstr "ポートミラーリング (オープンソースのサードパーティ製プラグイン使用)"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml59(para)
+msgid "Flow analysis (through open source or third-party plug-ins)"
+msgstr "フロー分析 (オープンソースのサードパーティプラグイン使用)"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml62(para)
+msgid ""
+"Tenant traffic port mirroring or Network Flow monitoring is currently not an"
+" exposed feature in OpenStack Networking. There are third-party plug-in "
+"extensions that do provide Port Mirroring on a per port/network/tenant "
+"basis. If Open vSwitch is used on the networking hypervisor, it is possible "
+"to enable sFlow and port mirroring, however it will require some operational"
+" effort to implement."
+msgstr "テナントトラフィックポートミラーリング又はNetwork Flow モニタリングは現在、OpenStack Networking の機能として公開されていません。ポート／ネットワーク／テナント単位でポートミラーリングを行うサードパーティ製のプラグイン拡張があります。ハイパーバイザー上で Open vSwitch を使用する場合、sFlow とポートミラーリングを有効にできますが、実装には幾つかの運用操作が必要になるでしょう。"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml65(title)
+msgid "Load balancing"
+msgstr "負荷分散"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml66(para)
+msgid ""
+"An experimental feature in the Grizzly release of OpenStack Networking is "
+"Load-Balancer-as-a-service (LBaaS). The LBaaS API gives early adopters and "
+"vendors a chance to build implementations of the technology. The reference "
+"implementation however, is still experimental and should likely not be run "
+"in a production environment. The current reference implementation is based "
+"on HA-Proxy. There are third-party plug-ins in development for extensions in"
+" OpenStack Networking to provide extensive L4-L7 functionality for virtual "
+"interface ports."
+msgstr "OpenStack Networking の Grizzly リリースにおける実験的機能の１つが Load-Balancer-as-a-service (LBaaS) です。LBaaS API は、アーリーアダプターやベンダーに LBaaS 技術の実装を行う機会を提供します。しかしながら、リファレンス実装は未だ実験段階で、商用環境で使用されているという話は聞きません。現在のリファレンス実装は HAProxy をベースにしています。仮想インターフェースポート用の拡張可能な L4-L7 機能を提供する OpenStack Networking 中の拡張用に開発中のサードパーティプラグインがあります。"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml69(title)
+msgid "Firewalls"
+msgstr "ファイアウォール"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml70(para)
+msgid ""
+"FW-as-a-Service (FWaaS) is currently in development for the OpenStack "
+"Networking Havana release as an experimental feature. FWaaS will address the"
+" need to manage and leverage the rich set of security features provided by "
+"typical firewall products which are typically far more comprehensive than "
+"what is currently provided by security groups. There are third-party plug-"
+"ins in development for extensions in OpenStack Networking to support this."
+msgstr "FW-as-a-Service (FWaaS) は実験的機能として OpenStack Networking Havana リリースに向けて現在開発中です。FWaaS は現在セキュリティグループにより提供されるものより一般にはかなり広い典型的なファイアウォール製品により提供される豊富なセキュリティ機能を管理・設定する為に呼ばれます。現在、FWaaS をサポートするために、OpenStack ネットワーキングの拡張用サードパーティプラグインが開発されているところです。"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml71(para)
+msgid ""
+"It is critical during the design of an OpenStack Networking infrastructure "
+"to understand the current features and limitations of network services that "
+"are available. Understanding where the boundaries of your virtual and "
+"physical networks will help you add the required security controls in your "
+"environment."
+msgstr "利用可能なネットワークサービスの現在の機能と制限を理解する事は OpenStack Networking の設計上極めて重要です。仮想／物理ネットワークの境界がどこかを理解する事は、あなたの環境で要求されたセキュリティコントロールを追加する際の助けになるでしょう。"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml75(title)
+msgid "Network services extensions"
+msgstr "ネットワークサービス拡張"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml76(para)
+msgid ""
+"Here is a list of known plug-ins provided by the open source community or by"
+" SDN companies that work with OpenStack Networking:"
+msgstr "以下はオープンソースコミュニティ又はSDN企業によって提供された、 OpenStack Networking で動作する既知のプラグインの一覧です。"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml77(para)
+msgid ""
+"Big Switch Controller plug-in, Brocade neutron plug-in Brocade neutron plug-"
+"in, Cisco UCS/Nexus plug-in, Cloudbase Hyper-V plug-in, Extreme Networks "
+"plug-in, Juniper Networks neutron plug-in, Linux Bridge plug-in, Mellanox "
+"neutron plug-in, MidoNet plug-in, NEC OpenFlow plug-in, Open vSwitch plug-"
+"in, PLUMgrid plug-in, Ruijie Networks plug-in, Ryu OpenFlow Controller plug-"
+"in, VMware NSX plug-in."
+msgstr "Big Switch Controller プラグイン、Brocade neutron プラグイン、Brocade neutron プラグイン、Cisco UCS/Nexus プラグイン、Cloudbase Hyper-V プラグイン、Extreme Networks プラグイン、Juniper Networks neutron プラグイン、Linux Bridge プラグイン、Mellanox neutron プラグイン、MidoNet プラグイン、NEC OpenFlow プラグイン、Open vSwitch プラグイン、PLUMgrid プラグイン、Ruijie Networks プラグイン、Ryu OpenFlow Controller プラグイン、VMware NSX プラグイン。"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml86(title)
+msgid "Networking services limitations"
+msgstr "Networking サービスの制限事項"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml87(para)
+msgid "OpenStack Networking has the following known limitations:"
+msgstr "OpenStack Networking は以下の制限があります。"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml90(term)
+msgid "Overlapping IP addresses"
+msgstr "IP アドレスの重複"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml92(para)
+msgid ""
+"If nodes that run either <systemitem "
+"class=\"service\">neutron-l3-agent</systemitem> or <systemitem "
+"class=\"service\">neutron-dhcp-agent</systemitem> use overlapping IP "
+"addresses, those nodes must use Linux network namespaces. By default, the "
+"DHCP and L3 agents use Linux network namespaces. However, if the host does "
+"not support these namespaces, run the DHCP and L3 agents on different hosts."
+msgstr "<systemitem class=\"service\">neutron-l3-agent</systemitem> か <systemitem class=\"service\">neutron-dhcp-agent</systemitem> のいずれかを実行するノードが重複した IP アドレスを使用する場合、これらのノード群は Linux のネットワークネームスペースを使用する必要があります。デフォルトでは、DHCP と L3 エージェントは Linux ネットワークネームスペースを使用しています。しかしながら、ホストがこのネームスペースをサポートしていない場合、DHCP と L3 エージェントは異なるホストで実行して下さい。"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml102(para)
+msgid ""
+"If network namespace support is not present, a further limitation of the L3 "
+"agent is that only a single logical router is supported."
+msgstr "ネットワークネームスペースサポートがない場合、L3エージェントでは追加の制限事項として単一の論理ルータのみサポートされます。"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml109(term)
+msgid "Multi-host DHCP-agent"
+msgstr "マルチホスト DHCP エージェント"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml111(para)
+msgid ""
+"OpenStack Networking supports multiple L3 and DHCP agents with load "
+"balancing. However, tight coupling of the location of the virtual machine is"
+" not supported."
+msgstr "OpenStack Networking は複数の L3 エージェントと DHCP エージェントによる負荷分散をサポートしています。しかしながら、（訳注：nova-network がサポートしていた）仮想マシンとの配置上の強い紐付けはサポートされていません。"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml119(term)
+msgid "No IPv6 support for L3 agents"
+msgstr "L3 エージェントの IPv6 未対応"
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml121(para)
+msgid ""
+"The neutron-l3-agent, used by many plug-ins to implement L3 forwarding, "
+"supports only IPv4 forwarding."
+msgstr "neutron-l3-agent （L3 転送の実装用に多くのプラグインが使用）は IPv4 転送のみサポートしています。"
+
+#: ./doc/security-guide/ch030_state-of-networking.xml8(title)
+msgid "State of networking"
+msgstr "ネットワークの状態"
+
+#: ./doc/security-guide/ch030_state-of-networking.xml9(para)
+msgid ""
+"OpenStack Networking in the Grizzly release enables the end-user or tenant "
+"to define, utilize, and consume networking resources in new ways that had "
+"not been possible in previous OpenStack Networking releases. OpenStack "
+"Networking provides a tenant-facing API for defining network connectivity "
+"and IP addressing for instances in the cloud in addition to orchestrating "
+"the network configuration. With the transition to an API-centric networking "
+"service, cloud architects and administrators should take into consideration "
+"best practices to secure physical and virtual network infrastructure and "
+"services."
+msgstr "Grizzly リリースの OpenStack Networking により、エンドユーザーまたはテナントは、以前の OpenStack Networking リリースではできなかった新しい方法でネットワークリソースを定義、利用、消費することが可能です。OpenStack Networking は、ネットワーク設定のオーケストレーションに加えて、クラウド内のインスタンスを対象としたネットワーク接続の定義と IP アドレス指定用の対テナント API を提供します。API 中心のネットワークサービスへの移行にあたっては、クラウドのアーキテクトや管理者が、物理/仮想ネットワークのインフラストラクチャーとサービスをセキュリティ保護するためのベストプラクティスを考慮すべきです。"
+
+#: ./doc/security-guide/ch030_state-of-networking.xml10(para)
+msgid ""
+"OpenStack Networking was designed with a plug-in architecture that provides "
+"extensibility of the API through open source community or third-party "
+"services. As you evaluate your architectural design requirements, it is "
+"important to determine what features are available in OpenStack Networking "
+"core services, any additional services that are provided by third-party "
+"products, and what supplemental services are required to be implemented in "
+"the physical infrastructure."
+msgstr "OpenStack Networking は、オープンソースコミュニティやサードパーティーのサービスによる API の拡張性を提供するプラグインアーキテクチャーで設計されました。アーキテクチャーの設計要件を評価するにあたっては、OpenStack Networking のコアサービスではどのような機能が提供されているか、サードパーティの製品によって提供される追加のサービスがあるかどうか、物理インフラストラクチャーにはどのような補足サービスを実装する必要があるかを判断することが重要です。"
+
+#: ./doc/security-guide/ch030_state-of-networking.xml20(para)
+msgid ""
+"This section is a high-level overview of what processes and best practices "
+"should be considered when implementing OpenStack Networking. We will talk "
+"about the current state of services that are available, what future services"
+" will be implemented, and the current limitations in this project."
+msgstr "本項には、OpenStack Networking を実装する際に検討すべきプロセスとベストプラクティスについての大まかな概要をまとめています。提供されているサービスの現在の状況 、将来実装されるサービス、本プロジェクトにおける現在の制限事項などについて説明します。"
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml8(title)
+msgid "Forensics and incident response"
+msgstr "フォレンジングとインシデント対応"
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml9(para)
+msgid ""
+"A lot of activity goes on within a cloud environment. It is a mix of "
+"hardware, operating systems, virtual machine managers, the OpenStack "
+"services, cloud-user activity such as creating instances and attaching "
+"storage, the network underlying the whole, and finally end-users using the "
+"applications running on the various instances."
+msgstr "多数の活動がクラウド環境内で行われます。これはハードウェア、オペレーティングシステム、仮想マシンマネージャ、OpenStackサービス群、インスタンス作成やストレージアタッチのようなクラウド⇔ユーザ活動、全体の土台であるネットワーク、最後に様々なインスタンス上で実行されるアプリケーションを使用するエンドユーザのミックスです。"
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml10(para)
+msgid ""
+"The generation and collection of logs is an important component of securely "
+"monitoring an OpenStack infrastructure. Logs provide visibility into the "
+"day-to-day actions of administrators, tenants, and guests, in addition to "
+"the activity in the compute, networking, and storage and other components "
+"that comprise your OpenStack deployment."
+msgstr "ログの生成と収集は OpenStack インフラのセキュリティ監視の重要なコンポーネントです。ログは日々の管理者・テナント・ゲストの行動に加え、あなたの OpenStack デプロイを構成する Compute、Networking、ストレージ、他のコンポーネントの活動の可視性を提供します。"
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml11(para)
+msgid ""
+"The basics of logging: configuration, setting log level, location of the log"
+" files, and how to use and customize logs, as well as how to do centralized "
+"collections of logs is well covered in the <link "
+"href=\"http://docs.openstack.org/ops/\"><citetitle>OpenStack Operations "
+"Guide</citetitle></link>."
+msgstr "ロギングの基本: ログを集中収集する方法と同様、設定、ログレベル設定、ログファイルの位置、ログの使用とカスタマイズ方法は、<link href=\"http://docs.openstack.org/ops/\"><citetitle>OpenStack Operations Guide</citetitle></link> で充分にカバーされています。"
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml12(para)
+msgid ""
+"Logs are not only valuable for proactive security and continuous compliance "
+"activities, but they are also a valuable information source for "
+"investigating and responding to incidents."
+msgstr "ログは率先したセキュリティや継続的なコンプライアンス活動に有用であるのみならず、インシデントの調査と対応の為の情報源としても有用です。"
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml13(para)
+msgid ""
+"For instance, analyzing the access logs of Identity Service or its "
+"replacement authentication system would alert us to failed logins, their "
+"frequency, origin IP, whether the events are restricted to select accounts "
+"etc. Log analysis supports detection."
+msgstr "例えば、Identity サービスまたはその代替認証システムへのアクセスログ解析は、アカウント等を選択してイベントを制限する／しないで、失敗したログイン、それらの頻度、アクセス元IPアドレスを警告します。ログ解析は検知をサポートします。"
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml14(para)
+msgid ""
+"On detection, further action may be to black list an IP, or recommend "
+"strengthening user passwords, or even de-activating a user account if it is "
+"deemed dormant."
+msgstr "検知時、追加のアクションになるのは、IP のブラックリストだったり、ユーザのパスワードを補強する事を推奨したり、ユーザアカウントが休眠状態である場合はその無効化でさえあったりします。"
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml16(title)
+msgid "Monitoring use cases"
+msgstr "監視ユースケース"
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml17(para)
+msgid ""
+"Monitoring events is more pro-active and provides real-time detection and "
+"response. There are several tools to aid in monitoring."
+msgstr "イベントの監視はより率先的で、リアルタイムの検知と対応を提供します。監視の助けとなるいくつかのツールがあります。"
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml18(para)
+msgid ""
+"In the case of an OpenStack cloud instance, we need to monitor the hardware,"
+" the OpenStack services, and the cloud resource usage. The last stems from "
+"wanting to be elastic, to scale to the dynamic needs of the users."
+msgstr "OpenStack クラウドインスタンスの場合、ハードウェア、OpenStack サービス、クラウドリソース使用量を監視する必要があります。最後は、柔軟性、ユーザの変化するニーズへのスケール性への要求から生じるものです。"
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml19(para)
+msgid ""
+"Here are a few important use cases to consider when implementing log "
+"aggregation, analysis and monitoring. These use cases can be implemented and"
+" monitored through various commercial and open source tools, homegrown "
+"scripts, etc. These tools and scripts can generate events that can then be "
+"sent to the administrators through email or integrated dashboard. It is "
+"important to consider additional use cases that may apply to your specific "
+"network and what you may consider anomalous behavior."
+msgstr "ここで、ログ収集、解析、監視を実装する際に考慮すべき重要なユースケースがいくつかあります。これらのユースケースは、様々な商用やオープンソースのツール、自作のスクリプト等を通じて実装・監視できます。これらのツールとスクリプトは、電子メールや組み込まれたダッシュボードで管理者に送信されるイベントを生成できます。あなたの場合のネットワークに適用できる追加のユースケースや、変則的な挙動を考慮できるようにするものを考慮する事は重要です。"
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml21(para)
+msgid ""
+"Detecting the absence of log generation is an event of high value. Such an "
+"event would indicate a service failure or even an intruder who has "
+"temporarily switched off logging or modified the log level to hide their "
+"tracks."
+msgstr "ログ生成無しの検知は価値の高いイベントです。このようなイベントはサービス障害、または一時的にログをオフにしたり、監視者から隠れるためにログレベルを変更した侵入者を示している可能性があります。"
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml25(para)
+msgid ""
+"Application events such as start and/or stop that were unscheduled would "
+"also be events to monitor and examine for possible security implications."
+msgstr "スケジュール外の start/stop のようなアプリケーションイベントは、潜在的なセキュリティ的なウラについての監視と確認作業を行うイベントでもあるでしょう。"
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml29(para)
+msgid ""
+"OS events on the OpenStack service machines such as user logins, restarts "
+"also provide valuable insight into use/misuse"
+msgstr "ユーザログイン、再起動のような OpenStack サービスマシン上の OS イベントもまた、使用／誤用への価値ある洞察を与えます。"
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml33(para)
+msgid ""
+"Being able to detect the load on the OpenStack servers also enables "
+"responding by way of introducing additional servers for load balancing to "
+"ensure high availability."
+msgstr "OpenStack サーバ群の負荷を検知可能にする事はまた、高可用化対応の為に負荷分散用追加サーバを導入する為の対応を可能にする事でもあります。"
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml37(para)
+msgid ""
+"Other events that are actionable are networking bridges going down, ip "
+"tables being flushed on compute nodes and consequential loss of access to "
+"instances resulting in unhappy customers."
+msgstr "行動可能な他のイベントはネットワークブリッジがダウンした事です。compute ノード上で設定がクリアされた iptables や、インスタンスへのアクセスの重大なロスはユーザを不幸にします。"
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml41(para)
+msgid ""
+"To reduce security risks from orphan instances on a user/tenant/domain "
+"deletion in the Identity service there is discussion to generate "
+"notifications in the system and have OpenStack components respond to these "
+"events as appropriate such as terminating instances, disconnecting attached "
+"volumes, reclaiming CPU and storage resources etc."
+msgstr "identity サービス中のユーザ／テナント／ドメイン削除に伴う見捨てられたインスタンスかあのセキュリティリスクを低減する為、システム中で通知を生成する事と、インスタンス削除、アタッチしたボリュームの切断、CPU やストレージリソースの回収等のイベントに適切に対応する OpenStack コンポーネントを用意する事について議論があります。"
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml44(para)
+msgid ""
+"A cloud will host many virtual instances, and monitoring these instances "
+"goes beyond hardware monitoring and log files which may just contain CRUD "
+"events."
+msgstr "クラウドには多数の仮想インスタンスがあり、これらのインスタンスの監視はハードウェア監視と CRUD イベントのみ含むログファイルの背後にあります。"
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml45(para)
+msgid ""
+"Security monitoring controls such as intrusion detection software, antivirus"
+" software, and spyware detection and removal utilities can generate logs "
+"that show when and how an attack or intrusion took place. Deploying these "
+"tools on the cloud machines provides value and protection. Cloud users, "
+"those running instances on the cloud may also want to run such tools on "
+"their instances."
+msgstr "侵入検知ソフトウェア、アンチウイルスソフトウェア、スパイウェア検知・削除ユーティリティのようなセキュリティ監視制御は、攻撃や侵入が発生した時と方法を示すログを生成できます。クラウドマシン上にこれらのツールをデプロイする事は、価値と保護を提供します。（クラウド上でインスタンスを実行する）クラウドユーザも自身のインスタンス上でこのようなツールを実行したいかも知れません。"
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml49(link)
+msgid "http://www.mirantis.com/blog/openstack-monitoring/"
+msgstr "http://www.mirantis.com/blog/openstack-monitoring/"
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml50(link)
+msgid "http://blog.sflow.com/2012/01/host-sflow-distributed-agent.html"
+msgstr "http://blog.sflow.com/2012/01/host-sflow-distributed-agent.html"
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml51(link)
+msgid "http://blog.sflow.com/2009/09/lan-and-wan.html"
+msgstr "http://blog.sflow.com/2009/09/lan-and-wan.html"
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml52(link)
+msgid ""
+"http://blog.sflow.com/2013/01/rapidly-detecting-large-flows-sflow-vs.html"
+msgstr "http://blog.sflow.com/2013/01/rapidly-detecting-large-flows-sflow-vs.html"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml9(para)
+msgid ""
+"Horizon is the OpenStack dashboard that provides users a self-service portal"
+" to provision their own resources within the limits set by administrators. "
+"These include provisioning users, defining instance flavors, uploading VM "
+"images, managing networks, setting up security groups, starting instances, "
+"and accessing the instances through a console."
+msgstr "Horizon は OpenStack のダッシュボードです。管理者により設定された制限の範囲内でユーザー自身のリソースを展開できるセルフサービスポータルをユーザーに提供します。これらには、ユーザーの管理、インスタンスのフレーバーの定義、仮想マシンイメージのアップロード、ネットワークの管理、セキュリティグループのセットアップ、インスタンスの起動、インスタンスへのコンソール経由のアクセスなどがあります。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml14(para)
+msgid ""
+"The dashboard is based on the Django web framework, therefore secure "
+"deployment practices for Django apply directly to horizon. This guide "
+"provides a popular set of Django security recommendations, further "
+"information can be found by reading the <link "
+"href=\"https://docs.djangoproject.com/en/1.5/#security\">Django deployment "
+"and security documentation</link>."
+msgstr "ダッシュボードは Django ウェブフレームワークに基づいています。そのため、Django のセキュアな導入プラクティスをそのまま Horizon に適用できます。このガイドは Django のセキュリティ推奨事項の一般的なものを提供します。さらなる情報は <link href=\"https://docs.djangoproject.com/en/1.5/#security\">Django deployment and security documentation</link> を読むことにより得られます。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml21(para)
+msgid ""
+"The dashboard ships with reasonable default security settings, and has good "
+"<link "
+"href=\"http://docs.openstack.org/developer/horizon/topics/deployment.html\">deployment"
+" and configuration documentation</link>."
+msgstr "ダッシュボードは適度なデフォルトのセキュリティ設定をしてあります。また、素晴らしい <link href=\"http://docs.openstack.org/developer/horizon/topics/deployment.html\">deployment and configuration documentation</link> (導入と設定のドキュメント) があります。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml26(title)
+msgid "Basic web server configuration"
+msgstr "基本的なウェブサーバーの設定"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml27(para)
+msgid ""
+"The dashboard should be deployed as a Web Services Gateway Interface (WSGI) "
+"application behind an HTTPS proxy such as Apache or nginx. If Apache is not "
+"already in use, we recommend nginx since it is lighter weight and easier to "
+"configure correctly."
+msgstr "ダッシュボードは、Apache や nginx のような HTTPS プロキシの後ろに Web Services Gateway Interface (WSGI) アプリケーションとして導入すべきです。まだ Apache を使用していなければ、nginx を推奨します。こちらのほうが軽量かつ正しく設定しやすいです。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml32(para)
+msgid ""
+"When using nginx, we recommend <link "
+"href=\"http://docs.gunicorn.org/en/latest/deploy.html\">gunicorn</link> as "
+"the wsgi host with an appropriate number of synchronous workers. We strongly"
+" advise against deployments using fastcgi, scgi, or uWSGI. We strongly "
+"advise against the use of synthetic performance benchmarks when choosing a "
+"wsgi server."
+msgstr "nginx を使用している場合、適切な数の同期ワーカーを持つ WSGI ホストとして <link href=\"http://docs.gunicorn.org/en/latest/deploy.html\">gunicorn</link> を推奨します。fastcgi、scgi、uWSGI 等の使用を強く推奨します。WSGI サーバーを選択するとき、統合パフォーマンスベンチマークの使用を強く推奨します。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml39(para)
+msgid ""
+"When using Apache, we recommend <link "
+"href=\"https://docs.djangoproject.com/en/1.5/howto/deployment/wsgi/modwsgi/\">mod_wsgi</link>"
+" to host dashboard."
+msgstr "Apache を使用しているとき、ダッシュボードをホストするために <link href=\"https://docs.djangoproject.com/en/1.5/howto/deployment/wsgi/modwsgi/\">mod_wsgi</link> を推奨します。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml44(title)
+msgid "HTTPS"
+msgstr "HTTPS"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml45(para)
+msgid ""
+"Deploy the dashboard behind a secure <glossterm>HTTPS</glossterm> server by "
+"using a valid, trusted certificate from a recognized certificate authority "
+"(CA). Private organization-issued certificates are only appropriate when the"
+" root of trust is pre-installed in all user browsers."
+msgstr "ダッシュボードは、認知されている認証局 (CA) から発行された有効かつ信頼できる証明書を使用しているセキュアな <glossterm>HTTPS</glossterm> サーバーの後ろに導入します。プライベートな組織で発行された証明書は、ルート証明機関がお使いのすべてのブラウザーに事前インストールされているときのみ、適切に動作します。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml52(para)
+msgid ""
+"Configure HTTP requests to the dashboard domain to redirect to the fully "
+"qualified HTTPS URL."
+msgstr "ダッシュボードのドメインに対する HTTP リクエストは、完全修飾された HTTPS URL にリダイレクトされるよう設定します。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml56(title)
+msgid "HTTP Strict Transport Security (HSTS)"
+msgstr "HTTP Strict Transport Security (HSTS)"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml57(para)
+msgid "It is highly recommended to use HTTP Strict Transport Security (HSTS)."
+msgstr "HTTP Strict Transport Security (HSTS) の使用が強く推奨されます。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml60(para)
+msgid ""
+"If you are using an HTTPS proxy in front of your web server, rather than "
+"using an HTTP server with HTTPS functionality, follow the <link "
+"href=\"https://docs.djangoproject.com/en/1.5/ref/settings/#secure-proxy-ssl-"
+"header\">Django documentation on modifying the SECURE_PROXY_SSL_HEADER "
+"variable</link>."
+msgstr "ウェブブラウザーの前で HTTPS プロキシを使用している場合、HTTPS 機能を持つ HTTP サーバーを使用するより、<link href=\"https://docs.djangoproject.com/en/1.5/ref/settings/#secure-proxy-ssl-header\">Django documentation on modifying the SECURE_PROXY_SSL_HEADER variable</link> に従うほうが良いです。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml67(para)
+msgid ""
+"See the chapter on PKI/SSL Everywhere for more specific recommendations and "
+"server configurations for HTTPS configurations, including the configuration "
+"of HSTS."
+msgstr "HSTS の設定を含め、HTTPS の設定に関するより具体的な推奨事項とサーバー設定は、PKI/SSL の章全体を参照してください。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml72(title)
+msgid "Front end caching"
+msgstr "フロントエンドキャッシュ"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml73(para)
+msgid ""
+"Since dashboard is rendering dynamic content passed directly from OpenStack "
+"API requests, we do not recommend front end caching layers such as varnish. "
+"In Django, static media is directly served from Apache or nginx and already "
+"benefits from web host caching."
+msgstr "ダッシュボードは OpenStack API リクエストから渡された動的コンテンツをそのまま描画するため、varnish のようなフロントエンドキャッシュ層を推奨しません。Django では、静的なメディアは直接 Apache や nginx から処理され、すでに Web ホストのキャッシュの恩恵を受けています。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml80(title)
+msgid "Domain names"
+msgstr "ドメイン名"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml81(para)
+msgid ""
+"Many organizations typically deploy web applications at subdomains of an "
+"overarching organization domain. It is natural for users to expect a domain "
+"of the form <uri>openstack.example.org</uri>. In this context, there are "
+"often many other applications deployed in the same second-level namespace, "
+"often serving user-controlled content. This name structure is convenient and"
+" simplifies name server maintenance."
+msgstr "多くの組織は一般的に、組織全体のドメインのサブドメインに Web アプリケーションを配備します。ユーザーが <uri>openstack.example.org</uri> 形式のドメインを期待することは自然です。これに関連して、しばしば同じセカンドレベルの名前空間に配備された、ユーザーが管理できるコンテンツを取り扱う他の多くのアプリケーションがあります。この名前の構造は便利であり、ネームサーバーのメンテナンスを簡単にします。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml89(para)
+msgid ""
+"We strongly recommend deploying horizon to a <emphasis>second-level "
+"domain</emphasis>, such as <uri>https://example.com</uri>, and advise "
+"against deploying horizon on a <emphasis>shared subdomain</emphasis> of any "
+"level, for example <uri>https://openstack.example.org</uri> or "
+"<uri>https://horizon.openstack.example.org</uri>. We also advise against "
+"deploying to bare internal domains like <uri>https://horizon/</uri>."
+msgstr "Horizon を<emphasis>セカンドレベルドメイン</emphasis>に導入することを強く推奨します。例えば、<uri>https://example.com</uri> です。また、Horizon を<emphasis>共有サブドメイン</emphasis>に導入しないことをお奨めします。例えば、<uri>https://openstack.example.org</uri> や <uri>https://horizon.openstack.example.org</uri> です。<uri>https://horizon/</uri> のようなそのままの内部ドメインに導入しないこともお奨めします。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml97(para)
+msgid ""
+"This recommendation is based on the limitations browser same-origin-policy. "
+"The recommendations in this guide cannot effectively protect users against "
+"known attacks if dashboard is deployed on a domain which also hosts user-"
+"generated content, such as scripts, images, or uploads of any kind, even if "
+"the user-generated content is on a different subdomain. This approach is "
+"used by most major web presences, such as googleusercontent.com, fbcdn.com, "
+"github.io, and twimg.com, to ensure that user generated content stays "
+"separate from cookies and security tokens."
+msgstr "この推奨事項はブラウザーの同一オリジンポリシーの制限に基づいています。このガイドにある推奨事項は、次のような場合によく知られている攻撃からユーザーを効率的に保護できません。ユーザーが生成したコンテンツ (例: スクリプト、イメージ、あらゆる種類のアップロード) もホストしているドメインにダッシュボードを導入した場合です。ユーザーが生成したコンテンツが別のサブドメインにある場合もです。この方法は、ユーザーが生成したコンテンツをクッキーやセキュリティトークンから確実に分離するために、多くの有名な Web サイト (例:  googleusercontent.com、fbcdn.com、github.io、twimg.com) により使用されています。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml107(para)
+msgid ""
+"Additionally, if you decline to follow this recommendation above about "
+"second-level domains, it is vital that you avoid the cookie backed session "
+"store and employ HTTP Strict Transport Security (HSTS). When deployed on a "
+"subdomain, dashboard's security is only as strong as the weakest application"
+" deployed on the same second-level domain."
+msgstr "さらに、セカンドレベルドメインに関する上の推奨事項に従わない場合、クッキーによるバックエンドセッションを避け、HTTP Strict Transport Security (HSTS) を採用することがきわめて重要です。サブドメインに導入するとき、ダッシュボードのセキュリティは同じレベルのドメインに導入されているアプリケーションの中で最も弱いレベルと同じ強度になります。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml115(title)
+msgid "Static media"
+msgstr "静的メディア"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml116(para)
+msgid ""
+"Dashboard's static media should be deployed to a subdomain of the dashboard "
+"domain and served by the web server. The use of an external content delivery"
+" network (CDN) is also acceptable. This subdomain should not set cookies or "
+"serve user-provided content. The media should also be served with HTTPS."
+msgstr "ダッシュボードの静的メディアは、ダッシュボードのドメインのサブドメインに導入し、Web サーバーにより処理されるべきです。外部の CDN (content delivery network) の使用も問題ありません。このサブドメインは、クッキーを設定すべきではなく、ユーザーが提供したコンテンツを処理すべきではありません。メディアも HTTPS で提供されるべきです。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml121(para)
+msgid ""
+"Django media settings are documented at <link "
+"href=\"https://docs.djangoproject.com/en/1.5/ref/settings/#static-"
+"root\">https://docs.djangoproject.com/en/1.5/ref/settings/#static-"
+"root</link>."
+msgstr "Django のメディア設定は <link href=\"https://docs.djangoproject.com/en/1.5/ref/settings/#static-root\">https://docs.djangoproject.com/en/1.5/ref/settings/#static-root</link> にドキュメント化されています。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml124(para)
+msgid ""
+"Dashboard's default configuration uses <link href=\"http://django-"
+"compressor.readthedocs.org/\">django_compressor</link> to compress and "
+"minify css and JavaScript content before serving it. This process should be "
+"statically done before deploying dashboard, rather than using the default "
+"in-request dynamic compression and copying the resulting files along with "
+"deployed code or to the CDN server. Compression should be done in a non-"
+"production build environment. If this is not practical, we recommend "
+"disabling resource compression entirely. Online compression dependencies "
+"(less, nodejs) should not be installed on production machines."
+msgstr "ダッシュボードのデフォルトの設定は、CSS と JavaScript のコンテンツを処理する前に圧縮して最小化するために <link href=\"http://django-compressor.readthedocs.org/\">django_compressor</link> を使用します。このプロセスは、デフォルトのリクエストごとに動的な圧縮を使用する代わりに、ダッシュボードを導入して、導入されたコードと一緒に結果のファイルを CDN サーバーにコピーする前に静的に実行されるべきです。圧縮は本番環境以外で実行すべきです。これが実践的でなければ、すべてのリソースの圧縮を無効化することを推奨します。オンライン圧縮の依存物 (less や nodejs) は本番環境にインストールするべきではありません。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml138(title)
+msgid "Secret key"
+msgstr "シークレットキー"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml139(para)
+msgid ""
+"Dashboard depends on a shared SECRET_KEY setting for some security "
+"functions. It should be a randomly generated string at least 64 characters "
+"long. It must be shared across all active dashboard instances. Compromise of"
+" this key may allow a remote attacker to execute arbitrary code. Rotating "
+"this key invalidates existing user sessions and caching. Do not commit this "
+"key to public repositories."
+msgstr "ダッシュボードはいくつかのセキュリティ機能に関する共有 SECRET_KEY 設定に依存します。これはランダムに生成された最小 64 文字の文字列です。すべてのダッシュボードインスタンスで共有する必要があります。このキーが漏洩すると、リモートの攻撃者が任意のコードを実行できる可能性があります。このキーのローテーションにより、既存のユーザーセッションとキャッシュを無効化します。このキーを公開リポジトリにコミットしないでください。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml148(title)
+msgid "Session back-end"
+msgstr "セッションバックエンド"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml149(para)
+msgid ""
+"Horizon's default session back-end "
+"(<emphasis>django.contrib.sessions.backends.signed_cookies</emphasis>) "
+"stores user data in <emphasis>signed</emphasis> but <emphasis>unencrypted "
+"</emphasis>cookies stored in the browser. This approach allows the most "
+"simple session backend scaling since each dashboard instance is stateless, "
+"but it comes at the cost of <emphasis>storing sensitive access tokens in the"
+" client browser</emphasis> and transmitting them with every request. This "
+"backend ensures that session data has not been tampered with, but the data "
+"itself is not encrypted other than the encryption provided by HTTPS."
+msgstr "Horizon の標準のセッションバックエンド (<emphasis>django.contrib.sessions.backends.signed_cookies</emphasis>) は、ブラウザに保存される、<emphasis>署名付き</emphasis>ですが<emphasis>暗号化されていない</emphasis>クッキーにユーザーデータを保存します。この方法により、各ダッシュボードインスタンスがステートレスになるため、最も簡単なセッションバックエンドがスケールできるようになります。しかし、<emphasis>機微なアクセストークンをクライアントのブラウザーに保存</emphasis>し、それらをリクエストごとに送信するという犠牲を払うことになります。このバックエンドは、セッションデータが改ざんされていないことを保証しますが、データ自身は HTTPS で提供されるような暗号化以外には暗号化されていません。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml160(para)
+msgid ""
+"If your architecture allows it, we recommend using "
+"<emphasis>django.contrib.sessions.backends.cache</emphasis> as your session "
+"backend with memcache as the cache. Memcache must not be exposed publicly, "
+"and should communicate over a secured private channel. If you choose to use "
+"the signed cookies backend, refer to the Django documentation understand the"
+" security trade-offs."
+msgstr "お使いのアーキテクチャが許容できる場合、セッションバックエンドとして <emphasis>django.contrib.sessions.backends.cache</emphasis> を、キャッシュとして memcache を一緒に使用することを推奨します。memcache はパブリックにアクセスされてはいけません。セキュアなプライベートチャネル経由で通信すべきです。署名付きクッキーバックエンドを使用することにした場合、セキュリティのトレードオフを理解するために Django のドキュメントを参照してください。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml167(para)
+msgid ""
+"For further details, consult the <link "
+"href=\"https://docs.djangoproject.com/en/1.5/topics/http/sessions"
+"/#configuring-the-session-engine\">Django session backend "
+"documentation</link>."
+msgstr "さらなる詳細は <link href=\"https://docs.djangoproject.com/en/1.5/topics/http/sessions/#configuring-the-session-engine\">Django session backend documentation</link> を参照してください。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml172(title)
+msgid "Allowed hosts"
+msgstr "許可されたホスト"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml173(para)
+msgid ""
+"Configure the ALLOWED_HOSTS setting with the domain or domains where the "
+"dashboard is available. Failure to configure this setting (especially if not"
+" following the recommendation above regarding second level domains) opens "
+"the dashboard to a number of serious attacks. Wild card domains should be "
+"avoided."
+msgstr "ダッシュボードが利用可能なドメインを ALLOWED_HOSTS に設定します。この設定を失敗すると (とくに第 2 レベルドメインに関する上の推奨に従わなかった場合)、ダッシュボードがさまざまな深刻な攻撃にさらされます。ワイルドカードを使用したドメインは避けるべきです。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml178(para)
+msgid ""
+"For further details, see the <link "
+"href=\"https://docs.djangoproject.com/en/1.5/ref/settings/#allowed-"
+"hosts\">Django documentation on settings</link>."
+msgstr "さらなる詳細は <link href=\"https://docs.djangoproject.com/en/1.5/ref/settings/#allowed-hosts\">Django documentation on settings</link> を参照してください。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml183(title)
+msgid "Cookies"
+msgstr "クッキー"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml184(para)
+msgid "Session Cookies should be set to HTTPONLY:"
+msgstr "セッションクッキーは HTTPONLY に設定すべきです。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml186(para)
+msgid ""
+"Never configure CSRF or session cookies to have a wild card domain with a "
+"leading dot. Horizon's session and CSRF cookie should be secured when "
+"deployed with HTTPS:"
+msgstr "ドットから始まるワイルドカードドメインを持つよう、CSRF やセッションクッキーを設定してはいけません。Horizon のセッションクッキーと CSRF クッキーは HTTPS を使用した環境のときにセキュア化すべきです。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml193(title)
+msgid "Password auto complete"
+msgstr "パスワード自動補完"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml194(para)
+msgid ""
+"We recommend that implementers do not change the default password auto "
+"complete behavior. Users choose stronger passwords in environments that "
+"allow them to use the secure browser password manager. Organizations which "
+"forbid the browser password manager should enforce this policy at the "
+"desktop level."
+msgstr "実装者は標準のパスワードオートコンプリート機能を変更しないことを推奨します。ユーザーはセキュアなブラウザのパスワードマネージャーを使用できる環境で、より強力なパスワードを選択します。ブラウザのパスワードマネージャーを禁止している組織は、デスクトップレベルでこのポリシーを強制すべきです。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml202(title)
+msgid "Cross Site Request Forgery (CSRF)"
+msgstr "クロスサイトリクエストフォージェリ (CSRF)"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml203(para)
+msgid ""
+"Django has a dedicated middleware for <link "
+"href=\"https://docs.djangoproject.com/en/1.5/ref/contrib/csrf/#how-it-works"
+"\">cross-site request forgery</link> (CSRF)."
+msgstr "Django は<link href=\"https://docs.djangoproject.com/en/1.5/ref/contrib/csrf/#how-it-works\">cross-site request forgery</link> (CSRF) 用の専用ミドルウェアを持ちます。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml206(para)
+msgid ""
+"Dashboard is designed to discourage developers from introducing cross-site "
+"scripting vulnerabilities with custom dashboards. However, it is important "
+"to audit custom dashboards, especially ones that are javascript-heavy for "
+"inappropriate use of the @csrf_exempt decorator. Dashboards which do not "
+"follow these recommended security settings should be carefully evaluated "
+"before restrictions are relaxed."
+msgstr "ダッシュボードは、カスタマイズしたダッシュボードでクロスサイトスクリプティングの脆弱性が含まれることから、開発者を守るよう設計されています。しかしながら、カスタマイズしたダッシュボード、とくに、@csrf_exempt デコレーターを不適切に使用して javascript を多用しているものを監査することは重要です。これらのセキュリティ設定の推奨事項に従わないダッシュボードは、制限を緩和する前に注意深く評価されるべきです。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml215(title)
+msgid "Cross Site Scripting (XSS)"
+msgstr "クロスサイトスクリプティング (XSS)"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml216(para)
+msgid ""
+"Unlike many similar systems, OpenStack dashboard allows the entire Unicode "
+"character set in most fields. This means developers have less latitude to "
+"make escaping mistakes that open attack vectors for cross-site scripting "
+"(XSS)."
+msgstr "多くの似たようなシステムと異なり、OpenStack のダッシュボードは多くの項目にすべての Unicode 文字を許可します。このことは、開発者が XSS 攻撃の余地を残すエスケープミスをする範囲が少なくなることを意味します。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml220(para)
+msgid ""
+"Dashboard provides tools for developers to avoid creating XSS "
+"vulnerabilities, but they only work if developers use them correctly. Audit "
+"any custom dashboards, paying particular attention to use of the mark_safe "
+"function, use of is_safe with custom template tags, the safe template tag, "
+"anywhere auto escape is turned off, and any JavaScript which might evaluate "
+"improperly escaped data."
+msgstr "ダッシュボードは開発者が XSS 脆弱性を作ることを防ぐためのツールを提供します。しかし、それらは開発者が適切に使用するときのみ機能します。mark_safe 関数の使用、カスタムテンプレートタグを持つ  is_safe の使用、safe テンプレートタグ、自動エスケープが無効化されているすべての場所、不適切にエスケープされたデータを評価するすべての javaScript にとくに注意して、すべてのカスタムダッシュボードを監視します。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml229(title)
+msgid "Cross Origin Resource Sharing (CORS)"
+msgstr "クロスオリジンリソースシェアリング (CORS)"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml230(para)
+msgid ""
+"Configure your web server to send a restrictive CORS header with each "
+"response, allowing only the dashboard domain and protocol:"
+msgstr "ウェブブラウザが各レスポンスに限定的な CORS ヘッダーを付けて送信するよう設定します。ダッシュボードのドメインとプロトコルのみを許可します。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml234(para)
+msgid "Never allow the wild card origin."
+msgstr "ワイルドカードオリジンを許可してはいけません。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml237(title)
+msgid "Horizon image upload"
+msgstr "Horizon のイメージのアップロード"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml238(para)
+msgid ""
+"We recommend that implementers <link "
+"href=\"http://docs.openstack.org/developer/horizon/topics/deployment.html"
+"#file-uploads\">disable HORIZON_IMAGES_ALLOW_UPLOAD</link> unless they have "
+"implemented a plan to prevent resource exhaustion and denial of service."
+msgstr "導入者はリソース枯渇とサービス妨害を防ぐ計画を実装していなければ、<link href=\"http://docs.openstack.org/developer/horizon/topics/deployment.html#file-uploads\">HORIZON_IMAGES_ALLOW_UPLOAD を無効化</link> することを強く推奨します。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml245(title)
+msgid "Upgrading"
+msgstr "アップグレード"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml246(para)
+msgid ""
+"Django security releases are generally well tested and aggressively "
+"backwards compatible. In almost all cases, new major releases of Django are "
+"also fully backwards compatible with previous releases. Dashboard "
+"implementers are strongly encouraged to run the latest stable release of "
+"Django with up-to-date security releases."
+msgstr "Django セキュリティリリースは、一般的に十分にテストされ、積極的に後方互換性を確保しています。ほぼすべての場合、Django の新しいメジャーリリースも前のリリースと後方互換性があります。ダッシュボードの実装者は、最新のセキュリティリリースを持つ最新の安定リリースの Django を実行することを強く推奨されます。"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml254(title)
+msgid "Debug"
+msgstr "デバッグ"
+
+#: ./doc/security-guide/ch025_web-dashboard.xml255(para)
+msgid ""
+"Make sure DEBUG is set to False in production. In Django, DEBUG displays "
+"stack traces and sensitive web server state information on any exception."
+msgstr "本番環境で DEBUG が False に設定されていることを確認します。Django では DEBUG により、あらゆる例外の発生時にスタックトレースとセキュリティ上問題のある Web サーバーの状態情報が表示されます。"
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml8(title)
+msgid "API endpoint configuration recommendations"
+msgstr "APIエンドポイント構成に関する推奨事項"
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml9(para)
+msgid ""
+"This chapter provides recommendations security enhancements for both public "
+"and private-facing API endpoints."
+msgstr "この章では外部と内部の API エンドポイントのセキュリティを改善するための推奨事項を提供します。"
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml13(title)
+msgid "Internal API communications"
+msgstr "内部API通信"
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml14(para)
+msgid ""
+"OpenStack provides both public facing and private API endpoints. By default,"
+" OpenStack components use the publicly defined endpoints. The recommendation"
+" is to configure these components to use the API endpoint within the proper "
+"security domain."
+msgstr "OpenStackはパブリックとプライベート両方のAPIエンドポイントを提供します。デフォルトではOpenStackコンポーネントはパブリックとして定義されたエンドポイントを使用します。推奨はこれらのコンポーネントを適切なセキュリティドメイン内で使用するよう構成することです。"
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml20(para)
+msgid ""
+"Services select their respective API endpoints based on the OpenStack "
+"service catalog. These services might not obey the listed public or internal"
+" API end point values. This can lead to internal management traffic being "
+"routed to external API endpoints."
+msgstr "サービスはOpenStackサービスカタログに基づいて、それぞれのAPIエンドポイントを選択します。これらのサービスは、リストされた外部もしくは内部APIエンドポイントの値に従わないことがあります。これは内部管理トラフィックが外部APIエンドポイントへルーティングされる可能性があります。"
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml27(title)
+msgid "Configure internal URLs in Identity service catalog"
+msgstr "認証サービスのカタログ内の内部URL構成"
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml28(para)
+msgid ""
+"The Identity service catalog should be aware of your internal URLs. While "
+"this feature is not utilized by default, it may be leveraged through "
+"configuration. Additionally, it should be forward-compatible with expectant "
+"changes once this behavior becomes the default."
+msgstr "Identity のカタログは内部 URL を認識できるようにすべきです。この機能はデフォルトで利用されませんが、設定により有効化できます。さらに、この動作が標準になると、予期される変更と前方互換性があるべきです。"
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml35(para)
+msgid "To register an internal URL for an endpoint:"
+msgstr "エンドポイント用の内部URL登録"
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml44(title)
+msgid "Configure applications for internal URLs"
+msgstr "内部URL用のアプリケーション構成"
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml45(para)
+msgid ""
+"You can force some services to use specific API endpoints. Therefore, it is "
+"recommended that each OpenStack service communicating to the API of another "
+"service must be explicitly configured to access the proper internal API "
+"endpoint."
+msgstr "いくつかのサービスは特定のAPIエンドポイントの仕様を強制することができます。従って、それぞれのOpenStackサービスと他サービスとの通信は明示的に適切な内部APIエンドポイントへアクセスするよう構成する必要があります。"
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml51(para)
+msgid ""
+"Each project may present an inconsistent way of defining target API "
+"endpoints. Future releases of OpenStack seek to resolve these "
+"inconsistencies through consistent use of the Identity Service catalog."
+msgstr "各プロジェクトで一貫性の無いAPIエンドポイントを提供しています。将来のリリースにおいてこれらの不一致を認証サービスカタログを使った一貫性で解決しようとしています。"
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml57(title)
+msgid "Configuration example #1: nova"
+msgstr "構成例#1: nova"
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml67(title)
+msgid "Configuration example #2: cinder"
+msgstr "構成例#2: cinder"
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml73(title)
+msgid "Paste and middleware"
+msgstr "Paste と ミドルウェア"
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml74(para)
+msgid ""
+"Most API endpoints and other HTTP services in OpenStack use the Python Paste"
+" Deploy library. From a securtiy perspective, this library enables "
+"manipulation of the request filter pipeline through the application's "
+"configuration. Each element in this chain is referred to as "
+"<emphasis>middleware</emphasis>. Changing the order of filters in the "
+"pipeline or adding additional middleware might have unpredictable security "
+"impact."
+msgstr "OpenStack内のほぼ全てのAPIエンドポイントと他のHTTPサービスはPythonのPaste Deployライブラリを利用しています。このライブラリにより、アプリケーションの設定によってはリクエストフィルターのパイプラインが操作が可能だと理解することがセキュリティの観点から重要になります。このパイプライン連鎖の中のそれぞれの要素は<emphasis>ミドルウェア</emphasis>として呼ばれています。パイプラインの中でフィルター順序を変更したり、ミドルウェアを追加すると予期しないセキュリティ上の影響が発生する可能性があります。"
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml83(para)
+msgid ""
+"Commonly, implementers add middleware to extend OpenStack's base "
+"functionality. We recommend implementers make careful consideration of the "
+"potential exposure introduced by the addition of non-standard software "
+"components to their HTTP request pipeline."
+msgstr "実装者がOpenStackの基本機能を拡張するためにミドルウェアを追加することは一般的です。私たちは非標準のソフトウェアコンポーネントをHTTPリクエストパイプラインへ追加することによって生じる潜在的なセキュリティについて慎重に検討する事を推奨しています。"
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml89(para)
+msgid ""
+"For more information about Paste Deploy, see <link "
+"href=\"http://pythonpaste.org/deploy/\">http://pythonpaste.org/deploy/</link>."
+msgstr "Paste Deployに関する追加情報は  <link href=\"http://pythonpaste.org/deploy/\">http://pythonpaste.org/deploy/</link> を参照してください。"
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml94(title)
+msgid "API endpoint process isolation and policy"
+msgstr "APIエンドポイントのプロセス分離とポリシー"
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml95(para)
+msgid ""
+"As much as possible, you should isolate API endpoint processes, especially "
+"those that reside within the public security domain should be isolated as "
+"much as possible. Where deployments allow, API endpoints should be deployed "
+"on separate hosts for increased isolation."
+msgstr "特にパブリックなセキュリティドメインに属するAPIエンドポイントプロセスは可能な限り分離すべきです。ディプロイメント可能であれば、APIエンドポイントは分離のために増設されたホスト上に構成すべきです。"
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml102(title)
+#: ./doc/security-guide/ch038_transport-security.xml133(title)
+msgid "Namespaces"
+msgstr "名前空間"
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml103(para)
+msgid ""
+"Many operating systems now provide compartmentalization support. Linux "
+"supports namespaces to assign processes into independent domains. Other "
+"parts of this guide cover system compartmentalization in more detail."
+msgstr "多くのOSは現在コンパートメント化をサポートしています。Linuxではプロセスに独立したドメインを割り当てる名前空間をサポートしています。システムのコンパートメント化についてはこのマニュアルの別の部分で詳しく説明されています。"
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml110(title)
+#: ./doc/security-guide/ch038_transport-security.xml144(title)
+msgid "Network policy"
+msgstr "ネットワークポリシー"
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml111(para)
+msgid ""
+"Because API endpoints typically bridge multiple security domains, you must "
+"pay particular attention to the compartmentalization of the API processes. "
+"See <xref linkend=\"ch005_security-domains-idp61360\"/> for additional "
+"information in this area."
+msgstr "APIエンドポイントは一般的に複数のセキュリティドメインをまたがるため、APIプロセスのコンパートメント化には特別の注意を払うべきです。この話題の詳細は <xref linkend=\"ch005_security-domains-idp61360\"/> を参照してください。"
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml117(para)
+msgid ""
+"With careful modeling, you can use network ACLs and IDS technologies to "
+"enforce explicit point to point communication between network services. As "
+"critical cross domain service, this type of explicit enforcement works well "
+"for OpenStack's message queue service."
+msgstr "慎重なデザインを行えば、ネットワークACLとIDS技術をネットワークサービス間の特定の通信に摘要する事が出来ます。重要なドメインをまたがるサービスとして、OpenStackのメッセージキューにこの手の明示的な強制は適しています。"
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml123(para)
+msgid ""
+"To enforce policies, you can configure services, host-based firewalls (such "
+"as iptables), local policy (SELinux or AppArmor), and optionally global "
+"network policy."
+msgstr "ポリシーを強制するために、サービス、ホストベースのファイアウォール(例えばiptables)、ローカルポリシー(SELinuxやAppArmor)、オプションとしてグローバルネットワークポリシーを設定できます。"
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml129(title)
+#: ./doc/security-guide/ch052_devices.xml238(title)
+#: ./doc/security-guide/ch038_transport-security.xml149(title)
+msgid "Mandatory access controls"
+msgstr "強制アクセス制御"
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml130(para)
+msgid ""
+"You should isolate API endpoint processes from each other and other "
+"processes on a machine. The configuration for those processes should be "
+"restricted to those processes not only by Discretionary Access Controls, but"
+" through Mandatory Access Controls. The goal of these enhanced access "
+"control is to aid in the containment and escalation of API endpoint security"
+" breaches. With mandatory access controls, such breaches severely limit "
+"access to resources and provide earlier alerting on such events."
+msgstr "APIエンドポイントのプロセスはマシン上の他のプロセスと分離すべきです。これらのプロセスの構成は任意のアクセス制御方法ではなく、強制アクセス制御によって制限されるべきです。これらのアクセス制御の目的はAPIエンドポイントのセキュリティ侵害の抑制と、特権侵害の防止です。強制アクセス制御を利用する事で、禁止されたリソースへのアクセスが厳しく制限され、早期の警告が得られるようになります。"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch052_devices.xml305(None)
+#: ./doc/security-guide/ch052_devices.xml309(None)
+msgid ""
+"@@image: 'static/sVirt Diagram 1.png'; md5=ffcdbb45d9054670ad4c270a7c7d3925"
+msgstr "@@image: 'static/sVirt Diagram 1.png'; md5=ffcdbb45d9054670ad4c270a7c7d3925"
+
+#: ./doc/security-guide/ch052_devices.xml12(title)
+msgid "Hardening the virtualization layers"
+msgstr "仮想化層のセキュリティ強化"
+
+#: ./doc/security-guide/ch052_devices.xml13(para)
+msgid ""
+"In the beginning of this chapter we discuss the use of both physical and "
+"virtual hardware by instances, the associated security risks, and some "
+"recommendations for mitigating those risks. We conclude the chapter with a "
+"discussion of sVirt, an open source project for integrating SELinux "
+"mandatory access controls with the virtualization components."
+msgstr "本章の初めに、インスタンスによる物理ハードウェアと仮想ハードウェアの両方の使用、関連するセキュリティリスク、それらのリスクを軽減するためのいくつかの推奨事項について議論します。SELinux 強制アクセス制御を仮想化コンポーネントと統合するためのオープンソースプロジェクトである sVirt の議論で本章を終わります。"
+
+#: ./doc/security-guide/ch052_devices.xml21(title)
+msgid "Physical hardware (PCI passthrough)"
+msgstr "物理ハードウェア (PCI パススルー)"
+
+#: ./doc/security-guide/ch052_devices.xml22(para)
+msgid ""
+"Many hypervisors offer a functionality known as PCI passthrough. This allows"
+" an instance to have direct access to a piece of hardware on the node. For "
+"example, this could be used to allow instances to access video cards "
+"offering the compute unified device architecture (CUDA) for high performance"
+" computation. This feature carries two types of security risks: direct "
+"memory access and hardware infection."
+msgstr "多くのハイパーバイザーは PCI パススルーとして知られる機能を提供します。これにより、インスタンスがノードにあるハードウェアの一部に直接アクセスできます。例えば、インスタンスがハイパフォーマンスコンピューティング用の compute unified device architecture (CUDA) を提供するビデオカードにアクセスするために使用されます。この機能は 2 種類のセキュリティリスクをもたらします。ダイレクトメモリアクセスとハードウェア感染です。"
+
+#: ./doc/security-guide/ch052_devices.xml31(para)
+msgid ""
+"Direct memory access (DMA) is a feature that permits certain hardware "
+"devices to access arbitrary physical memory addresses in the host computer. "
+"Often video cards have this capability. However, an instance should not be "
+"given arbitrary physical memory access because this would give it full view "
+"of both the host system and other instances running on the same node. "
+"Hardware vendors use an input/output memory management unit (IOMMU) to "
+"manage DMA access in these situations. Therefore, cloud architects should "
+"ensure that the hypervisor is configured to utilize this hardware feature."
+msgstr "ダイレクトメモリアクセス (DMA) は、特定のハードウェアがホストコンピューターで任意の物理メモリアドレスにアクセスできる機能です。ビデオカードはときどきこの機能を有しています。しかしながら、インスタンスは指定された任意の物理メモリアクセスをすべきではありません。なぜなら、これはホストシステムと同じノードで実行している他のインスタンスを完全に表示できるかもしれないからです。ハードウェアベンダーはこれらの状況で DMA アクセスを管理するために input/output memory management unit (IOMMU) を使用します。そのため、クラウドアーキテクトは、ハイパーバイザーがこのハードウェア機能を使用するよう設定されていることを確実にすべきです。"
+
+#: ./doc/security-guide/ch052_devices.xml45(para)
+msgid ""
+"KVM: <link href=\"http://www.linux-kvm.org/page"
+"/How_to_assign_devices_with_VT-d_in_KVM\">How to assign devices with VT-d in"
+" KVM</link>"
+msgstr "KVM: <link href=\"http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM\">How to assign devices with VT-d in KVM</link>"
+
+#: ./doc/security-guide/ch052_devices.xml50(para)
+msgid "Xen: <link href=\"http://wiki.xen.org/wiki/VTd_HowTo\">VTd Howto</link>"
+msgstr "Xen: <link href=\"http://wiki.xen.org/wiki/VTd_HowTo\">VTd Howto</link>"
+
+#: ./doc/security-guide/ch052_devices.xml55(para)
+msgid "The IOMMU feature is marketed as VT-d by Intel and AMD-Vi by AMD."
+msgstr "IOMMU 機能は、Intel により VT-d、AMD により AMD-Vi として提供されています。"
+
+#: ./doc/security-guide/ch052_devices.xml59(para)
+msgid ""
+"A hardware infection occurs when an instance makes a malicious modification "
+"to the firmware or some other part of a device. As this device is used by "
+"other instances, or even the host OS, the malicious code can spread into "
+"these systems. The end result is that one instance can run code outside of "
+"its security domain. This is a potential problem in any hardware sharing "
+"scenario. The problem is specific to this scenario because it is harder to "
+"reset the state of physical hardware than virtual hardware."
+msgstr "ハードウェア感染は、インスタンスが悪意のある変更をファームウェアやデバイスの他の部分に行うときに発生します。このデバイスは他のインスタンス、またはホスト OS により使用されるため、悪意のあるコードはこれらのシステムの中に拡散する可能性があります。最終的な結果として、あるインスタンスがセキュリティドメインの範囲外で実行できます。これは何らかのハードウェアを共有している状況における潜在的な問題です。仮想ハードウェアよりも物理ハードウェアの状態をリセットすることが難しいため、この問題はこの状況に特有のものです。"
+
+#: ./doc/security-guide/ch052_devices.xml69(para)
+msgid ""
+"Solutions to the hardware infection problem are domain specific. The "
+"strategy is to identify how an instance can modify hardware state then "
+"determine how to reset any modifications when the instance is done using the"
+" hardware. For example, one option could be to re-flash the firmware after "
+"use. Clearly there is a need to balance hardware longevity with security as "
+"some firmwares will fail after a large number of writes. TPM technology, "
+"described in <xref linkend=\"ch013_node-bootstrapping-idp44768\"/>, provides"
+" a solution for detecting unauthorized firmware changes. Regardless of the "
+"strategy selected, it is important to understand the risks associated with "
+"this kind of hardware sharing so that they can be properly mitigated for a "
+"given deployment scenario."
+msgstr "ハードウェア感染問題の解決策はドメイン固有です。戦略はインスタンスがどのようにしてハードウェア状態を修正可能かを特定する事、その後インスタンスがハードウェアを使用している際に修正をリセットする方法を検知する事です。例えば、使用後のファームウェアの再度フラッシュが挙げられます。明らかに、いくつかのファームウェアは多数の書き込み後に故障するので、上記の作業はハードウェア寿命とセキュリティを天秤にかける必要があります。TPM 技術（<xref linkend=\"ch013_node-bootstrapping-idp44768\"/>で説明）は未承認のファームウェア変更を検知する解決策を提供します。選択した戦略に関わらず、この種のハードウェア共有に関するリスクを理解する事は、与えられたデプロイシナリオ用に適切にリスクを軽減する上で重要です。"
+
+#: ./doc/security-guide/ch052_devices.xml85(para)
+msgid ""
+"Additionally, due to the risk and complexities associated with PCI "
+"passthrough, it should be disabled by default. If enabled for a specific "
+"need, you will need to have appropriate processes in place to ensure the "
+"hardware is clean before re-issue."
+msgstr "加えて、PCI パススルーに関連したリスクと複雑性のため、これはデフォルトで無効化されるべきです。特定の用途のために有効化する場合、ハードウェアが再発行される前に確実にクリアするために、適切なプロセスを実行する必要があります。"
+
+#: ./doc/security-guide/ch052_devices.xml93(title)
+msgid "Virtual hardware (QEMU)"
+msgstr "仮想ハードウェア (QEMU)"
+
+#: ./doc/security-guide/ch052_devices.xml94(para)
+msgid ""
+"When running a virtual machine, virtual hardware is a software layer that "
+"provides the hardware interface for the virtual machine. Instances use this "
+"functionality to provide network, storage, video, and other devices that may"
+" be needed. With this in mind, most instances in your environment will "
+"exclusively use virtual hardware, with a minority that will require direct "
+"hardware access. The major open source hypervisors use QEMU for this "
+"functionality. While QEMU fills an important need for virtualization "
+"platforms, it has proven to be a very challenging software project to write "
+"and maintain. Much of the functionality in QEMU is implemented with low-"
+"level code that is difficult for most developers to comprehend. Furthermore,"
+" the hardware virtualized by QEMU includes many legacy devices that have "
+"their own set of quirks. Putting all of this together, QEMU has been the "
+"source of many security problems, including hypervisor breakout attacks."
+msgstr "仮想マシンの実行時、仮想ハードウェアは仮想マシンにハードウェアインターフェースを提供するソフトウェア層です。インスタンスは必要となるネットワーク、ストレージ、ビデオ、他のデバイスを提供するためにこの機能を使用します。これで覚えておくことは、お使いのほとんどのインスタンスは排他的に仮想ハードウェアを使用することです。一部はハードウェアに直接アクセスする必要があります。主要なオープンソースのハイパーバイザーはこの機能のために QEMU を使用します。QEMU は仮想化プラットフォームのニーズを満たしますが、作成と維持することが非常に挑戦的なソフトウェアプロジェクトであるとわかってきました。QEMU の機能のほとんどは、多くの開発者が理解しにくい低レベルなコードで実装されています。さらに、QEMU により仮想化されるハードウェアには、独自の癖を持つレガシーデバイスが数多くあります。これを一括りにするので、QEMU はハイパーバイザー突破攻撃を含む多くのセキュリティ問題の元になってきました。"
+
+#: ./doc/security-guide/ch052_devices.xml112(para)
+msgid ""
+"For the reasons stated above, it is important to take proactive steps to "
+"harden QEMU. We recommend three specific steps: minimizing the code base, "
+"using compiler hardening, and using mandatory access controls, such as "
+"sVirt, SELinux, or AppArmor."
+msgstr "上記の理由として、QEMU 堅牢化の率先したステップの実行が重要である事が挙げられます。我々は３つの特定のステップを推奨しています。コードベースの最小化、コンパイラーの堅牢化、sVirt・SELinux・AppArmor 等の強制アクセス制御の使用です。"
+
+#: ./doc/security-guide/ch052_devices.xml119(title)
+msgid "Minimizing the QEMU code base"
+msgstr "QEMU コードベースの最小化"
+
+#: ./doc/security-guide/ch052_devices.xml120(para)
+msgid ""
+"One classic security principle is to remove any unused components from your "
+"system. QEMU provides support for many different virtual hardware devices. "
+"However, only a small number of devices are needed for a given instance. "
+"Most instances will use the virtio devices. However, some legacy instances "
+"will need access to specific hardware, which can be specified using glance "
+"metadata:"
+msgstr "古くからある 1 つのセキュリティ原則は、システムから未使用のコンポーネントを削除することです。QEMU はさまざまな種類の仮想ハードウェアデバイスをサポートします。しかしながら、少しのデバイスだけが指定されたインスタンスに必要になります。多くのインスタンスは virtio デバイスを使用します。しかし、いくつかのレガシーなインスタンスは、glance メタデータを使用して指定できる、特定のハードウェアにアクセスする必要があります。"
+
+#: ./doc/security-guide/ch052_devices.xml133(para)
+msgid ""
+"A cloud architect should decide what devices to make available to cloud "
+"users. Anything that is not needed should be removed from QEMU. This step "
+"requires recompiling QEMU after modifying the options passed to the QEMU "
+"configure script. For a complete list of up-to-date options simply run "
+"<placeholder-1/> from within the QEMU source directory. Decide what is "
+"needed for your deployment, and disable the remaining options."
+msgstr "クラウドアーキテクトは、どのデバイスがクラウドユーザーに利用可能であるかを判断すべきです。必要ないすべてのデバイスは QEMU から削除すべきです。この手順は、QEMU 設定スクリプトに渡されるオプションを変更した後で、QEMU を再コンパイルする必要があります。最新の完全なオプション一覧は、QEMU ソースディレクトリの中で <placeholder-1/> を単に実行します。お使いの環境に必要なものを判断し、残りのオプションを無効化します。"
+
+#: ./doc/security-guide/ch052_devices.xml144(title)
+msgid "Compiler hardening"
+msgstr "コンパイラーのセキュリティ強化機能"
+
+#: ./doc/security-guide/ch052_devices.xml145(para)
+msgid ""
+"The next step is to harden QEMU using compiler hardening options. Modern "
+"compilers provide a variety of compile time options to improve the security "
+"of the resulting binaries. These features, which we will describe in more "
+"detail below, include relocation read-only (RELRO), stack canaries, never "
+"execute (NX), position independent executable (PIE), and address space "
+"layout randomization (ASLR)."
+msgstr "次の手順は、コンパイラーのセキュリティ強化オプションを使用して QEMU をセキュリティ強化することです。最近のコンパイラーは、出力バイナリのセキュリティを改善するために、さまざまなコンパイル時オプションを提供します。これらの機能には、より詳細を以下で説明しますが、relocation read-only (RELRO)、Stack Canaries、never execute (NX)、position independent executable (PIE)、address space layout randomization (ASLR) があります。"
+
+#: ./doc/security-guide/ch052_devices.xml154(para)
+msgid ""
+"Many modern linux distributions already build QEMU with compiler hardening "
+"enabled, so you may want to verify your existing executable before "
+"proceeding with the information below. One tool that can assist you with "
+"this verification is called <link "
+"href=\"http://www.trapkit.de/tools/checksec.html\"><literal>checksec.sh</literal></link>."
+msgstr "ほとんどの最近の Linux ディストリビューションは、すでにコンパイラーのセキュリティ強化を有効化して QEMU をビルドしています。そのため、以下の情報を続ける前に、既存のバイナリを確認したいでしょう。この確認を手助けできるツールの 1 つは <link href=\"http://www.trapkit.de/tools/checksec.html\"><literal>checksec.sh</literal></link> と呼ばれます。"
+
+#: ./doc/security-guide/ch052_devices.xml163(term)
+msgid "RELocation Read-Only (RELRO)"
+msgstr "RELocation Read-Only (RELRO)"
+
+#: ./doc/security-guide/ch052_devices.xml165(para)
+msgid ""
+"Hardens the data sections of an executable. Both full and partial RELRO "
+"modes are supported by gcc. For QEMU full RELRO is your best choice. This "
+"will make the global offset table read-only and place various internal data "
+"sections before the program data section in the resulting executable."
+msgstr "実行ファイルのデータ部分をセキュリティ強化します。全体 RELRO モードと部分 RELRO モードが gcc によりサポートされます。QEMU 完全 RELRO が最善の選択肢です。これにより、グローバルオフセットテーブルが読み込み専用になり、出力実行ファイルのプログラムデータセクションの前にさまざまな内部データ部分が置かれます。"
+
+#: ./doc/security-guide/ch052_devices.xml175(term)
+msgid "Stack canaries"
+msgstr "スタックカナリア"
+
+#: ./doc/security-guide/ch052_devices.xml177(para)
+msgid ""
+"Places values on the stack and verifies their presence to help prevent "
+"buffer overflow attacks."
+msgstr "バッファーオーバーフロー攻撃を防ぐ役に立てるために、スタックに値を置き、それらの存在を検証します。"
+
+#: ./doc/security-guide/ch052_devices.xml183(term)
+msgid "Never eXecute (NX)"
+msgstr "Never eXecute (NX)"
+
+#: ./doc/security-guide/ch052_devices.xml185(para)
+msgid ""
+"Also known as Data Execution Prevention (DEP), ensures that data sections of"
+" the executable can not be executed."
+msgstr "Data Execution Prevention (DEP) としても知られています。実行ファイルのデータ部分を必ず実行できなくします。"
+
+#: ./doc/security-guide/ch052_devices.xml192(term)
+msgid "Position Independent Executable (PIE)"
+msgstr "Position Independent Executable (PIE)"
+
+#: ./doc/security-guide/ch052_devices.xml194(para)
+msgid ""
+"Produces a position independent executable, which is necessary for ASLR."
+msgstr "位置に依存しない実行ファイルを生成します。ASLR のために必要です。"
+
+#: ./doc/security-guide/ch052_devices.xml200(term)
+msgid "Address Space Layout Randomization (ASLR)"
+msgstr "Address Space Layout Randomization (ASLR)"
+
+#: ./doc/security-guide/ch052_devices.xml202(para)
+msgid ""
+"This ensures that placement of both code and data regions will be "
+"randomized. Enabled by the kernel (all modern linux kernels support ASLR), "
+"when the executable is built with PIE."
+msgstr "コード領域とデータ領域の配置を確実にランダム化します。実行ファイルが PIE を用いてビルドされるとき、カーネルにより有効化されます (最近の Linux カーネルはすべて ASLR をサポートします)。"
+
+#: ./doc/security-guide/ch052_devices.xml210(para)
+msgid ""
+"Putting this all together, and adding in some additional useful protections,"
+" we recommend the following compiler options for GCC when compiling QEMU:"
+msgstr "すべてを一緒に利用し、いくつか追加の有用な保護を追加して、QEMU コンパイル時に以下の GCC コンパイラーオプションを推奨します。"
+
+#: ./doc/security-guide/ch052_devices.xml217(para)
+msgid ""
+"We recommend testing your QEMU executable file after it is compiled to "
+"ensure that the compiler hardening worked properly."
+msgstr "コンパイラーが確実に適切なセキュリティ強化を動作させるようコンパイルした後で、お使いの QEMU 実行ファイルをテストすることを推奨します。"
+
+#: ./doc/security-guide/ch052_devices.xml221(para)
+msgid ""
+"Most cloud deployments will not want to build software such as QEMU by hand."
+" It is better to use packaging to ensure that the process is repeatable and "
+"to ensure that the end result can be easily deployed throughout the cloud. "
+"The references below provide some additional details on applying compiler "
+"hardening options to existing packages."
+msgstr "ほとんどのクラウド環境は QEMU のようなソフトウェアを手動でビルドしたくないでしょう。プロセスが確実に繰り返し可能であり、最終結果を簡単にクラウドにデプロイできるようにするために、パッケージを使用するほうが良いでしょう。以下の参考情報は、既存のパッケージにコンパイラーのセキュリティ強化オプションを適用することの詳細を提供します。"
+
+#: ./doc/security-guide/ch052_devices.xml230(para)
+msgid ""
+"DEB packages: <link "
+"href=\"http://wiki.debian.org/HardeningWalkthrough\">Hardening "
+"Walkthrough</link>"
+msgstr "DEB パッケージ: <link href=\"http://wiki.debian.org/HardeningWalkthrough\">Hardening Walkthrough</link>"
+
+#: ./doc/security-guide/ch052_devices.xml233(para)
+msgid ""
+"RPM packages: <link "
+"href=\"http://fedoraproject.org/wiki/How_to_create_an_RPM_package\">How to "
+"create an RPM package</link>"
+msgstr "RPM パッケージ: <link href=\"http://fedoraproject.org/wiki/How_to_create_an_RPM_package\">How to create an RPM package</link>"
+
+#: ./doc/security-guide/ch052_devices.xml239(para)
+msgid ""
+"Compiler hardening makes it more difficult to attack the QEMU process. "
+"However, if an attacker does succeed, we would like to limit the impact of "
+"the attack. Mandatory access controls accomplish this by restricting the "
+"privileges on QEMU process to only what is needed. This can be accomplished "
+"using sVirt / SELinux or AppArmor. When using sVirt, SELinux is configured "
+"to run every QEMU process under a different security context. AppArmor can "
+"be configured to provide similar functionality. We provide more details on "
+"sVirt in the instance isolation section below."
+msgstr "コンパイラーのセキュリティ強化機能により、QEMU プロセスへの攻撃をより難しくできます。しかし、攻撃者が成功すると、攻撃の影響範囲を抑えたいでしょう。強制アクセス制御は、QEMU プロセスの権限を必要な範囲に制限することにより、これを実現します。これは sVirt / SELinux または AppArmor により実現できます。sVirt 利用時、SELinux はすべての QEMU プロセスが別々のセキュリティドメインで動作するよう設定されます。AppArmor は同様の機能を提供するよう設定できます。以下のインスタンス分離のセクションで sVirt の詳細を示します。"
+
+#: ./doc/security-guide/ch052_devices.xml253(title)
+msgid "sVirt: SELinux and virtualization"
+msgstr "sVirt: SELinux と 仮想化"
+
+#: ./doc/security-guide/ch052_devices.xml254(para)
+msgid ""
+"With unique kernel-level architecture and National Security Agency (NSA) "
+"developed security mechanisms, KVM provides foundational isolation "
+"technologies for multi tenancy. With developmental origins dating back to "
+"2002, the Secure Virtualization (sVirt) technology is the application of "
+"SELinux against modern day virtualization. SELinux, which was designed to "
+"apply separation control based upon labels, has been extended to provide "
+"isolation between virtual machine processes, devices, data files and system "
+"processes acting upon their behalf."
+msgstr "KVM は複数のテナントを分離する基本技術を提供します。カーネルレベルの独特のアーキテクチャを用いて、National Security Agency (NSA) により開発されたセキュリティ機構です。開発の起源は 2002 年までさかのぼり、Secure Virtualization (sVirt) 技術は最近の仮想化向けの SELinux の応用技術です。SELinux は、ラベルに基づいた分離制御を適用するために設計され、仮想マシンのプロセス、デバイス、データファイル、それらの上で動作するシステムプロセス間の分離を提供するために拡張されました。"
+
+#: ./doc/security-guide/ch052_devices.xml265(para)
+msgid ""
+"OpenStack's sVirt implementation aspires to protect hypervisor hosts and "
+"virtual machines against two primary threat vectors:"
+msgstr "OpenStack の sVirt 実装は、2 種類の主要な脅威ベクターに対して、ハイパーバイザーホストと仮想マシンを保護することを目指しています。"
+
+#: ./doc/security-guide/ch052_devices.xml270(para)
+msgid ""
+"<emphasis role=\"bold\">Hypervisor threats</emphasis> A compromised "
+"application running within a virtual machine attacks the hypervisor to "
+"access underlying resources. For example, the host OS, applications, or "
+"devices within the physical machine. This is a threat vector unique to "
+"virtualization and represents considerable risk as the underlying real "
+"machine can be compromised due to vulnerability in a single virtual "
+"application."
+msgstr "<emphasis role=\"bold\">ハイパーバイザーの脅威</emphasis> 仮想マシンの中で動作している侵入されたアプリケーションは、バックエンドのリソースにアクセスするためにハイパーバイザーを攻撃します。例えば、ホスト OS、アプリケーション、物理マシンにあるデバイスです。バックエンドの物理マシンが単一の仮想アプリケーションにある脆弱性のために侵入されうるため、これは仮想化に特有の脅威ベクターであり、考慮すべきリスクを表します。"
+
+#: ./doc/security-guide/ch052_devices.xml280(para)
+msgid ""
+"<emphasis role=\"bold\">Virtual Machine (multi-tenant) threats</emphasis> A "
+"compromised application running within a VM attacks the hypervisor to "
+"access/control another virtual machine and its resources. This is a threat "
+"vector unique to virtualization and represents considerable risk as a "
+"multitude of virtual machine file images could be compromised due to "
+"vulnerability in a single application. This virtual network attack is a "
+"major concern as the administrative techniques for protecting real networks "
+"do not directly apply to the virtual environment."
+msgstr "<emphasis role=\"bold\">仮想マシン (マルチテナント) の脅威</emphasis> 仮想マシンの中で動作している侵入されたアプリケーションは、他の仮想マシンとそのリソースにアクセスし、制御するためにハイパーバイザーを攻撃します。仮想マシンのイメージファイルの集合が単一のアプリケーションにある脆弱性のために侵入されうるため、これは仮想化に特有の脅威ベクターであり、考慮すべきリスクを表します。実ネットワークを保護するための管理技術が仮想マシン環境にそのまま適用できないため、この仮想ネットワークへの攻撃はおもな関心事です。"
+
+#: ./doc/security-guide/ch052_devices.xml293(para)
+msgid ""
+"Each KVM-based virtual machine is a process which is labeled by SELinux, "
+"effectively establishing a security boundary around each virtual machine. "
+"This security boundary is monitored and enforced by the Linux kernel, "
+"restricting the virtual machine's access to resources outside of its "
+"boundary such as host machine data files or other VMs."
+msgstr "各 KVM ベースの仮想マシンは SELinux によりラベル付けされているプロセスです。これは各仮想マシンのセキュリティ境界を効率的に確立します。このセキュリティ境界は、Linux カーネルにより監視され、強制されます。ホストマシンのデータファイルや他の仮想マシンのような、仮想マシンの境界外のリソースへのアクセスは制限されます。"
+
+#: ./doc/security-guide/ch052_devices.xml313(para)
+msgid ""
+"As shown above, sVirt isolation is provided regardless of the guest "
+"Operating System running inside the virtual machineLinux or Windows VMs can "
+"be used. Additionally, many Linux distributions provide SELinux within the "
+"operating system, allowing the virtual machine to protect internal virtual "
+"resources from threats."
+msgstr "上に示したとおり、sVirt による分離は仮想マシン内で動作しているゲストオペレーティングシステムに関わらず提供されます。Linux や Windows の仮想マシンを使用できます。さらに、多くの Linux ディストリビューションはオペレーティングシステム内の SELinux を提供しています。仮想マシンが内部の仮想リソースを脅威から保護できます。"
+
+#: ./doc/security-guide/ch052_devices.xml322(title)
+msgid "Labels and categories"
+msgstr "ラベルとカテゴリ"
+
+#: ./doc/security-guide/ch052_devices.xml323(para)
+msgid ""
+"KVM-based virtual machine instances are labelled with their own SELinux data"
+" type, known as svirt_image_t. Kernel level protections prevent unauthorized"
+" system processes, such as malware, from manipulating the virtual machine "
+"image files on disk. When virtual machines are powered off, images are "
+"stored as svirt_image_t as shown below:"
+msgstr "KVM ベースの仮想マシンインスタンスは、svirt_image_t として知られる、独自の SELinux データタイプでラベル付けされています。カーネルレベルの保護により、悪意のあるソフトウェアのような権限のないシステムプロセスが、ディスクにある仮想マシンのイメージファイルを操作することを防ぎます。仮想マシンが電源オフのとき、イメージは以下のように svirt_image_t として保存されます。"
+
+#: ./doc/security-guide/ch052_devices.xml334(para)
+msgid ""
+"The <literal>svirt_image_t</literal> label uniquely identifies image files "
+"on disk, allowing for the SELinux policy to restrict access. When a KVM-"
+"based Compute image is powered on, sVirt appends a random numerical "
+"identifier to the image. sVirt is technically capable of assigning numerical"
+" identifiers to 524,288 virtual machines per hypervisor node, however "
+"OpenStack deployments are highly unlikely to encounter this limitation."
+msgstr "<literal>svirt_image_t</literal> ラベルは独自にディスク上のイメージファイルを識別し、SELinux ポリシーがアクセス制限できるようにします。KVM ベースの Compute イメージが電源投入された際、sVirt はイメージに乱数のIDを付与します。sVirt は技術的には１ハイパーバイザーノードあたり 524,288 個の仮想マシンに数字IDを付与する事ができますが、OpenStack デプロイでこの制限に遭遇する事はまずないでしょう。"
+
+#: ./doc/security-guide/ch052_devices.xml343(para)
+msgid "This example shows the sVirt category identifier:"
+msgstr "この例は sVirt カテゴリー識別子を示します。"
+
+#: ./doc/security-guide/ch052_devices.xml348(title)
+msgid "Booleans"
+msgstr "ブーリアン"
+
+#: ./doc/security-guide/ch052_devices.xml349(para)
+msgid ""
+"To ease the administrative burden of managing SELinux, many enterprise Linux"
+" platforms utilize SELinux Booleans to quickly change the security posture "
+"of sVirt."
+msgstr "SELinux の管理負担を減らすために、多くのエンタープライズ Linux プラットフォームは sVirt のセキュリティ設定を簡単に変更するために、SELinux ブーリアンを利用します。"
+
+#: ./doc/security-guide/ch052_devices.xml353(para)
+msgid ""
+"Red Hat Enterprise Linux-based KVM deployments utilize the following sVirt "
+"booleans:"
+msgstr "Red Hat Enterprise Linux ベースの KVM 環境は以下の sVirt ブーリアンを利用します。"
+
+#: ./doc/security-guide/ch052_devices.xml361(emphasis)
+msgid "sVirt SELinux Boolean"
+msgstr "sVirt SELinux ブーリアン"
+
+#: ./doc/security-guide/ch052_devices.xml362(emphasis)
+#: ./doc/security-guide/ch051_vss-intro.xml484(td)
+msgid "Description"
+msgstr "記述"
+
+#: ./doc/security-guide/ch052_devices.xml367(para)
+msgid "virt_use_common"
+msgstr "virt_use_common"
+
+#: ./doc/security-guide/ch052_devices.xml368(para)
+msgid "Allow virt to use serial/parallel communication ports."
+msgstr "仮想化がシリアル通信ポートとパラレル通信ポートを使用することを許可します。"
+
+#: ./doc/security-guide/ch052_devices.xml371(para)
+msgid "virt_use_fusefs"
+msgstr "virt_use_fusefs"
+
+#: ./doc/security-guide/ch052_devices.xml372(para)
+msgid "Allow virt to read FUSE mounted files."
+msgstr "仮想化が FUSE マウントされたファイルを読み取ることを許可します。"
+
+#: ./doc/security-guide/ch052_devices.xml375(para)
+msgid "virt_use_nfs"
+msgstr "virt_use_nfs"
+
+#: ./doc/security-guide/ch052_devices.xml376(para)
+msgid "Allow virt to manage NFS mounted files."
+msgstr "仮想化が NFS マウントされたファイルを管理することを許可します。"
+
+#: ./doc/security-guide/ch052_devices.xml379(para)
+msgid "virt_use_samba"
+msgstr "virt_use_samba"
+
+#: ./doc/security-guide/ch052_devices.xml380(para)
+msgid "Allow virt to manage CIFS mounted files."
+msgstr "仮想化が CIFS マウントされたファイルを管理することを許可します。"
+
+#: ./doc/security-guide/ch052_devices.xml383(para)
+msgid "virt_use_sanlock"
+msgstr "virt_use_sanlock"
+
+#: ./doc/security-guide/ch052_devices.xml384(para)
+msgid "Allow confined virtual guests to interact with the sanlock."
+msgstr "制限された仮想マシンが sanlock を操作することを許可します。"
+
+#: ./doc/security-guide/ch052_devices.xml387(para)
+msgid "virt_use_sysfs"
+msgstr "virt_use_sysfs"
+
+#: ./doc/security-guide/ch052_devices.xml388(para)
+msgid "Allow virt to manage device configuration (PCI)."
+msgstr "仮想マシンがデバイス設定 (PCI) を管理することを許可します。"
+
+#: ./doc/security-guide/ch052_devices.xml391(para)
+msgid "virt_use_usb"
+msgstr "virt_use_usb"
+
+#: ./doc/security-guide/ch052_devices.xml392(para)
+msgid "Allow virt to use USB devices."
+msgstr "仮想化が USB デバイスを使用することを許可します。"
+
+#: ./doc/security-guide/ch052_devices.xml395(para)
+msgid "virt_use_xserver"
+msgstr "virt_use_xserver"
+
+#: ./doc/security-guide/ch052_devices.xml396(para)
+msgid "Allow virtual machine to interact with the X Window System."
+msgstr "仮想マシンが X Window System と通信することを許可します。"
+
+#: ./doc/security-guide/ch056_case-studies-instance-management.xml8(title)
+msgid "Case studies: instance management"
+msgstr "ケーススタディ：インスタンス管理"
+
+#: ./doc/security-guide/ch056_case-studies-instance-management.xml9(para)
+msgid ""
+"In this case study we discuss how Alice and Bob would architect their clouds"
+" with respect to instance entropy, scheduling instances, trusted images, and"
+" instance migrations."
+msgstr "このケーススタディでは、アリスとボブがインスタンスのエントロピー、インスタンスのスケジューリング、信頼できるイメージ、インスタンスのマイグレーションを尊重しつつ、彼らのクラウドを設計する方法について議論します。"
+
+#: ./doc/security-guide/ch056_case-studies-instance-management.xml12(para)
+msgid ""
+"Alice has a need for lots of high quality entropy in the instances. For this"
+" reason, she decides to purchase hardware with Intel Ivy Bridge chip sets "
+"that support the RdRand instruction on each compute node. Using the entropy "
+"gathering daemon (EGD) and LibVirt's EGD support, Alice ensures that this "
+"entropy pool is distributed to the instances on each compute node."
+msgstr "アリスはインスタンス群に高い品質の多くのエントロピーに対するニーズがあります。このため、彼女は各 compute ノード上で RdRand 命令をサポートする Intel Ivy Bridge チップセットを持つハードウェアの購入を決めました。エントロピー収集デーモン (EGD) と LibVirt の EGD サポートを使用して、Alice はこのエントロピープールが各 compute ノード上のインスタンスに配信されるようにします。"
+
+#: ./doc/security-guide/ch056_case-studies-instance-management.xml13(para)
+msgid ""
+"For instance scheduling, Alice uses the trusted compute pools to ensure that"
+" all cloud workloads are deployed to nodes that presented a proper boot time"
+" attestation. Alice decides to disable user permissions for image uploading "
+"to help ensure that the images used in the cloud are generated in a known "
+"and trusted manner by the cloud administrators."
+msgstr "インスタンススケジューリングでは、全てのクラウド負荷が適切な起動時間保証を示すノードにデプロイされるようにする為、アリスは信頼できる compute プールを使用します。クラウド中で使用されるイメージがクラウド管理者に既知で信頼できる方法で作成されたものである事を保証するため、アリスはユーザにイメージをアップロードする権限を与えない事を決めました。"
+
+#: ./doc/security-guide/ch056_case-studies-instance-management.xml14(para)
+msgid ""
+"Finally, Alice disables instance migrations as this feature is less critical"
+" for the high performance application workloads expected to run in this "
+"cloud. This helps avoid the various security concerns related to instance "
+"migrations."
+msgstr "最後に、アリスはインスタンスのマイグレーションを無効化しました。この機能はこのクラウドで実行される予定の高パフォーマンスアプリケーション負荷にはほとんど不要だからです。これにより、インスタンスマイグレーションにまつわる様々なセキュリティ関連を避ける事ができます。"
+
+#: ./doc/security-guide/ch056_case-studies-instance-management.xml18(para)
+msgid ""
+"Bob is aware that entropy will be a concern for some of his customers, such "
+"as those in the financial industry. However, due to the added cost and "
+"complexity, Bob has decided to forgo integrating hardware entropy into the "
+"first iteration of his cloud. He adds hardware entropy as a fast-follow to "
+"do for a later improvement for the second generation of his cloud "
+"architecture."
+msgstr "ボブは、金融業界の企業ユーザの幾つかにとってエントロピーが重要となる事を理解しています。しかしながら、費用と複雑さが増える為、ボブは彼のクラウドの初回導入分にハードウェアエントロピーの導入を見送る事を決めました。彼は自分の２世代目のクラウドアーキテクチャに向けた後の改善では、早期のフォローとしてハードウェアエントロピーを追加します。"
+
+#: ./doc/security-guide/ch056_case-studies-instance-management.xml19(para)
+msgid ""
+"Bob is interested in ensuring that customers receive a high quality of "
+"service. He is concerned that providing too much explicit user control over "
+"instance scheduling could negatively impact the quality of service. So he "
+"disables this feature. Bob provides images in the cloud from a known trusted"
+" source for users to use. Additionally, he also allows users to upload their"
+" own images. However, users cannot generally share their images. This helps "
+"prevent a user from sharing a malicious image, which could negatively impact"
+" the security of other users in the cloud."
+msgstr "ボブは、顧客が高品質なサービスを受けられるようにする事に興味があります。彼は、インスタンススケジューリングを超えた過剰なほど明確なユーザコントロールの提供が、サービス品質（QoS）にマイナス影響を与える事を心配しています。ですので、この機能を無効化しました。ボブは使用するユーザに対して既知の信頼できるソースからのクラウド中のイメージを提供します。加えて、彼はまた、ユーザに自分のイメージアップロードを許可します。しかしながら、ユーザは一般に自分のイメージを共有できません。これは、クラウド中の他のユーザのセキュリティにマイナスインパクトを与えかねない、悪意あるイメージを共有する事からユーザを守る助けになります。"
+
+#: ./doc/security-guide/ch056_case-studies-instance-management.xml20(para)
+msgid ""
+"For migrations, Bob wants to enable secure instance migrations in order to "
+"support rolling upgrades with minimal user downtime. Bob ensures that all "
+"migrations occur on an isolated VLAN. He plans to defer implementing "
+"encrypted migrations until this is better supported in <placeholder-1/> "
+"client tools. However, he makes a note to track this carefully and switch to"
+" encrypted migrations as soon as possible."
+msgstr "マイグレーションでは、ボブは最小のユーザダウンタイムでのローリングアップデートをサポートする為に、安全なインスタンスマイグレーションを有効にしたいと思っています。ボブは、全てのマイグレーションが独立した VLAN 上で実行されるようにします。彼は、<placeholder-1/> クライアントツールが暗号化マイグレーションをより良くサポートするまで暗号化マイグレーションの実装を遅らせる計画を立てています。"
+
 #: ./doc/security-guide/ch051_vss-intro.xml11(title)
 msgid "Hypervisor selection"
 msgstr "ハイパーバイザーの選択"
@@ -970,11 +5424,6 @@ msgid ""
 "technologies are important from a security perspective."
 msgstr "さらに、ハイパーバイザープラットフォームの評価時、ハイパーバイザーを実行するハイパーバイザーを考慮すべきです。加えて、ハードウェアで利用可能な追加機能を評価します。また、それらの機能が OpenStack 環境の一部として選択したハイパーバイザーによりどのようにサポートされるかを考慮します。そのためにも、ハイパーバイザーはそれぞれ自身のハードウェア互換性リスト (HCL) を持つでしょう。互換性のあるハードウェアの選択時、まずどのハードウェア仮想化技術がセキュリティの観点から重要であるかを理解することが重要です。"
 
-#: ./doc/security-guide/ch051_vss-intro.xml484(td)
-#: ./doc/security-guide/ch052_devices.xml362(emphasis)
-msgid "Description"
-msgstr "記述"
-
 #: ./doc/security-guide/ch051_vss-intro.xml485(td)
 msgid "Technology"
 msgstr "技術"
@@ -1241,676 +5690,809 @@ msgid ""
 "directly mappable between hypervisors."
 msgstr "* この表にある機能はすべてのハイパーバイザーに適用できないかもしれません。また、ハイパーバイザー間で直接対応付けできないかもしれません。"
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml8(title)
-msgid "Introduction to SSL/TLS"
-msgstr "SSL/TLSの導入"
+#: ./doc/security-guide/ch035_case-studies-networking.xml8(title)
+msgid "Case studies: Networking"
+msgstr "ケーススタディ: Networking"
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml9(para)
+#: ./doc/security-guide/ch035_case-studies-networking.xml9(para)
 msgid ""
-"OpenStack services receive requests on behalf of users on public networks as"
-" well as from other internal services over management networks. Inter-"
-"service communications can also occur over public networks depending on "
-"deployment and architecture choices."
-msgstr "OpenStack のサービスは、管理ネットワーク経由の他の内部サービスからのリクエストと同様、パブリックネットワーク上のユーザによるリクエストを受信します。サービス間通信は、デプロイメントとアーキテクチャ選択によってはパブリックネットワーク経由で行われる事もあります。"
+"In this case study we discuss how Alice and Bob would address providing "
+"networking services to the user."
+msgstr "このケーススタディでは、アリスとボブがどのようにユーザに対してネットワーク提供を扱うかを議論します。"
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml10(para)
+#: ./doc/security-guide/ch035_case-studies-networking.xml12(para)
 msgid ""
-"While it is commonly accepted that data over public networks should be "
-"secured using cryptographic measures, such as Secure Sockets Layer or "
-"Transport Layer Security (SSL/TLS) protocols, it is insufficient to rely on "
-"security domain separation to protect internal traffic. Using a security-in-"
-"depth approach, we recommend securing all domains with SSL/TLS, including "
-"the management domain services. It is important that should a tenant escape "
-"their VM isolation and gain access to the hypervisor or host resources, "
-"compromise an API endpoint, or any other service, they must not be able to "
-"easily inject or capture messages, commands, or otherwise affect or control "
-"management capabilities of the cloud. SSL/TLS provides the mechanisms to "
-"ensure authentication, non-repudiation, confidentiality, and integrity of "
-"user communications to the OpenStack services and between the OpenStack "
-"services themselves."
-msgstr "パブリックネット上のデータは Secure Sockets Layer や Transport Layer Security (SSL/TLS)プロトコルのような暗号化方式を使用してセキュリティを確保すべきであるという事は一般に認識されている一方で、内部トラフィックの保護の為セキュリティドメイン分割に依存する事は不十分です。security-in-depth アプローチを用いて、管理ドメインサービスを含め、SSL/TLSを用いて全ドメインをセキュリティ確保する事を推奨します。テナントがVM分割を回避して、ハイパーバイザーやホストリソースへのアクセスを得て、APIエンドポイントやあらゆる他のサービスを妥協させる事は重大です。テナントが容易にインジェクトしたり、メッセージ・コマンド・その他クラウド上の管理機能に影響を与える又は制御する事が出来るようにすべきではありません。SSL/TLS は、OpenStack サービスへのユーザ通信や OpenStack サービス自体の相互間通信の認証、回避不能、秘密性、完全性を確保する仕組みを提供します。"
+"A key objective of Alice's cloud is to integrate with the existing auth "
+"services and security resources. The key design parameters for this private "
+"cloud are a limited scope of tenants, networks and workload type. This "
+"environment can be designed to limit what available network resources are "
+"available to the tenant and what are the various default quotas and security"
+" policies are available. The network policy engine can be modified to "
+"restrict creation and changes to network resources. In this environment, "
+"Alice might want to leverage nova-network in the application of security "
+"group polices on a per instance basis vs. neutron's application of security "
+"group polices on a per port basis. L2 isolation in this environment would "
+"leverage VLAN tagging. The use of VLAN tags will allow great visibility of "
+"tenant traffic by leveraging existing features and tools of the physical "
+"infrastructure."
+msgstr "アリスのクラウドの主目的は、既存の認証サービスとセキュリティリソースを用いたインテグレーションです。このプライベートクラウドのキーとなる設計パラメータは、テナント・ネットワーク・ワークロードタイプの限定されたスコープです。この環境は、どの利用可能なネットワークリソースがテナントから利用可能であり、どの様々なデフォルトクォータとセキュリティポリシーが利用可能かを制限するために設計される可能性があります。ネットワークポリシーエンジンは、ネットワークリソースの作成と変更を制限する為に修正される可能性があります。この環境では、アリスはインスタンス単位のセキュリティグループポリシーの適用における nova-network か、neutron のポートベースのセキュリティグループポリシーの適用のいずれを希望するかも知れません。この環境における L2 アイソレーションは VLAN タギングを用います。VLAN タグの利用は、物理インフラの既存の機能やツールの利用によるテナントトラフィックの素晴らしい可視性が得られます。"
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml11(para)
+#: ./doc/security-guide/ch035_case-studies-networking.xml30(para)
 msgid ""
-"Public Key Infrastructure (PKI) is a set of hardware, software, policies, "
-"and procedures required to operate a secure system that provides "
-"authentication, non-repudiation, confidentiality, and integrity. The core "
-"components of PKI are:"
-msgstr "Public Key Infrastructure (PKI)は認証、偽証不可、秘匿性、完全性を提供するセキュアなシステムを運用するために必要となるハードウェア、ソフトウェア、ポリシーのセットです。PKIのコアコンポーネントは以下の通り。"
+"A major business driver for Bob is to provide an advanced networking "
+"services to his customers. Bob's customers would like to deploy multi-tiered"
+" application stacks. This multi-tiered application are either existing "
+"enterprise application or newly deployed applications. Since Bob's public "
+"cloud is a multi-tenancy enterprise service, the choice to use for L2 "
+"isolation in this environment is to use overlay networking. Another aspect "
+"of Bob's cloud is the self-service aspect where the customer can provision "
+"available networking services as needed. These networking services encompass"
+" L2 networks, L3 Routing, Network <glossterm>ACL</glossterm> and NAT. It is "
+"important that per-tenant quota's be implemented in this environment."
+msgstr "ボブの主要なビジネス目的は彼の顧客に先進的なネットワークサービスを提供する事です。ボブの顧客はマルチタイアのアプリケーションスタックをデプロイしようとしています。マルチタイアのアプリケーションは、既存の商用アプリケーションや新しくデプロイされるアプリケーションのいずれかです。ボブのパブリッククラウドはマルチテナントの商用サービスである為、この環境の L2 アイソレーションに使用する選択肢は、オーバレイネットワークです。ボブのクラウドの他の側面は、必要に応じて顧客が利用可能なネットワークサービスをプロビジョンできるセルフサービス指向です。これらのネットワークサービスは、L2 ネットワーク、L3 ルーティング、ネットワーク<glossterm>ACL</glossterm>、NAT を含みます。\n\nIt is important that per-tenant quota's be implemented in this environment."
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml18(term)
-msgid "End entity"
-msgstr "エンドエンティティ"
-
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml20(para)
-msgid "User, process, or system that is the subject of a certificate."
-msgstr "証明対象のユーザ、プロセス、システム。"
-
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml25(term)
-msgid "Certification Authority (<glossterm>CA</glossterm>)"
-msgstr "認証局 (<glossterm>CA</glossterm>)"
-
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml27(para)
+#: ./doc/security-guide/ch035_case-studies-networking.xml43(para)
 msgid ""
-"Defines certificate policies, management, and issuance of certificates."
-msgstr "証明ポリシーの定義、管理、証明書の発行。"
+"An added benefit with utilizing OpenStack Networking is when new advanced "
+"networking services become available, these new features can be easily "
+"provided to the end customers."
+msgstr "OpenStack Networking 利用の追加的な利点は、新しい先進的なネットワークサービスが利用可能になった場合、これらの新しい機能をエンドユーザに簡単に提供できる事です。"
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml32(term)
-msgid "Registration Authority (RA)"
-msgstr "登録局 (RA)"
+#: ./doc/security-guide/ch028_case-studies-identity-management.xml8(title)
+msgid "Case studies: Identity management"
+msgstr "ケーススタディ: ID 管理"
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml34(para)
+#: ./doc/security-guide/ch028_case-studies-identity-management.xml9(para)
 msgid ""
-"An optional system to which a CA delegates certain management functions."
-msgstr "CAが一定の管理機能を委任する追加システム。"
+"In this case study we discuss how Alice and Bob would address configuration "
+"of OpenStack core services. These include the Identity service, dashboard, "
+"and Compute services. Alice will be concerned with integration into the "
+"existing government directory services, while Bob will need to provide "
+"access to the public."
+msgstr "このケーススタディでは、アリスとボブが OpenStack コアサービスの設定をどのように取り扱うかを議論します。これらには、Identity Service、Dashboard、Compute が含まれます。アリスは既存の政府ディレクトリサービスに統合することに関心があります。ボブはパブリックにアクセス権を提供する必要があります。"
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml39(term)
-msgid "Repository"
-msgstr "リポジトリ"
-
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml41(para)
+#: ./doc/security-guide/ch028_case-studies-identity-management.xml19(para)
 msgid ""
-"Where the end entity certificates and certificate revocation lists are "
-"stored and looked up - sometimes referred to as the <emphasis "
-"role=\"italic\">certificate bundle</emphasis>."
-msgstr "エンドエンティティが証明され、証明書の廃止リストが保存・参照される場所 - 時々<emphasis role=\"italic\">証明バンドル(Certificate bundle)</emphasis>と呼ばれます。"
+"Alice's enterprise has a well-established directory service with two-factor "
+"authentication for all users. She configures the Identity service to support"
+" an external authentication service supporting authentication with "
+"government-issued access cards. She also uses an external LDAP server to "
+"provide role information for the users that is integrated with the access "
+"control policy. Due to FedRAMP compliance requirements, Alice implements "
+"two-factor authentication on the management network for all administrator "
+"access."
+msgstr "アリスの企業はすべてのユーザーに対して 2 要素認証を持つディレクトリサービスが十分に確立されています。彼女は政府発行のアクセスカードを用いた認証をサポートする外部認証サービスをサポートするよう Identity を設定します。アクセス制御ポリシーと統合されたユーザー用ロール情報を提供するために、外部 LDAP サービスも使用します。FedRAMP コンプライアンス要件のため、アリスはすべての管理アクセスに対して管理ネットワークで 2 要素認証を導入します。"
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml49(term)
-msgid "Relying party"
-msgstr "信頼機関"
-
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml51(para)
-msgid "The endpoint that is trusting that the CA is valid."
-msgstr "CAが有効であると証明するエンドポイント"
-
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml56(para)
+#: ./doc/security-guide/ch028_case-studies-identity-management.xml30(para)
 msgid ""
-"PKI builds the framework on which to provide encryption algorithms, cipher "
-"modes, and protocols for securing data and authentication. We strongly "
-"recommend securing all services with Public Key Infrastructure (PKI), "
-"including the use of SSL/TLS for API endpoints. It is impossible for the "
-"encryption or signing of transports or messages alone to solve all these "
-"problems. Hosts themselves must be secure and implement policy, namespaces, "
-"and other controls to protect their private credentials and keys. However, "
-"the challenges of key management and protection do not reduce the necessity "
-"of these controls, or lessen their importance."
-msgstr "PKIはデータと認証をセキュアにする暗号アルゴリズム、暗号モード(cipher mode)、プロトコルの\nフレームワークをバンドルしています。APIエンドポイントの為のSSL/TLS 使用を含み、Public Key Infrastructure (PKI)を用いて、全サービスをセキュアにする事をお勧めします。暗号化や通信路・メッセージの署名の為に、これら全ての問題を解決する事は重要です。プライベート証明と鍵の保護の為、ホスト自身がセキュアで、ポリシー、ネームスペース、その他の制御を実装しなければなりません。しかし、キー管理や保護のチャレンジはこれらの制御の必要性を削減したり、その重要性を失ったりはしません。"
+"Alice also deploys the dashboard to manage many aspects of the cloud. She "
+"deploys the dashboard with HSTS to ensure that only HTTPS is used. The "
+"dashboard resides within an internal subdomain of the private network domain"
+" name system."
+msgstr "アリスはクラウドのさまざまな観点を管理するために Dashboard も導入します。必ず HTTPS のみを使用するために HSTS と共に Dashboard を導入します。Dashboard はプライベートネットワークの DNS の内部サブドメインの中にあります。"
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml58(title)
-msgid "Certification authorities"
-msgstr "認証局(CA)"
-
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml59(para)
+#: ./doc/security-guide/ch028_case-studies-identity-management.xml36(para)
 msgid ""
-"Many organizations have an established Public Key Infrastructure with their "
-"own certification authority (CA), certificate policies, and management for "
-"which they should use to issue certificates for internal OpenStack users or "
-"services. Organizations in which the public security domain is Internet "
-"facing will additionally need certificates signed by a widely recognized "
-"public CA. For cryptographic communications over the management network, it "
-"is recommended one not use a public CA. Instead, we expect and recommend "
-"most deployments deploy their own internal CA."
-msgstr "多くの組織には、内部のOpenStackユーザやサービス用に証明書を発行する為に使用されるべき場所用の自身の認証局(CA)、証明ポリシー、管理を備えたPublic Key Infrastructure (PKI)が設置されています\n。加えて、パブリックセキュリティドメインがインターネットに面している所の組織は、幅広く認識された公共のCAにより署名された証明書が必要になるでしょう。管理ネットワーク上の暗号化通信用には、パブリックCAを使用しない事をお勧めします。代わりに、多くのデプロイでは自身の内部CAを設置していると思われますし、推奨します。"
+"Alice decides to use SPICE instead of VNC for the virtual console. She wants"
+" to take advantage of the emerging capabilities in SPICE."
+msgstr "アリスは仮想コンソールに VNC の代わりに SPICE を使用することを決めました。SPICE の先進的な機能の利点を得ようと思います。"
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml60(para)
+#: ./doc/security-guide/ch028_case-studies-identity-management.xml44(para)
 msgid ""
-"It is recommended that the OpenStack cloud architect consider using separate"
-" PKI deployments for internal systems and customer facing services. This "
-"allows the cloud deployer to maintain control of their PKI infrastructure "
-"and among other things makes requesting, signing and deploying certificates "
-"for internal systems easier. Advanced configurations may use separate PKI "
-"deployments for different security domains. This allows deployers to "
-"maintain cryptographic separation of environments, ensuring that "
-"certificates issued to one are not recognised by another."
-msgstr "OpenStackクラウドアーキテクトには、内部のシステムと顧客が接するサービス用に、分断されたPKIデプロイの使用を検討する事をお勧めします。これは、クラウドをデプロイする人が他の物が内部のシステム用に証明書を要求・署名・デプロイする事を容易にするPKIインフラを制御できるようにします。異なる設定は異なるセキュリティドメイン用にPKIデプロイを分割使用しても構いません。これは、デプロイする人が環境の暗号の分断を管理できるようにし、一方で発行された証明書が他方で認証されない事を保証します。"
+"Because Bob must support authentication for the general public, he decides "
+"to use use user name and password authentication. He has concerns about "
+"brute force attacks attempting to crack user passwords, so he also uses an "
+"external authentication extension that throttles the number of failed login "
+"attempts. Bob's management network is separate from the other networks "
+"within his cloud, but can be reached from his corporate network through ssh."
+" As recommended earlier, Bob requires administrators to use two-factor "
+"authentication on the Management network to reduce the risk from compromised"
+" administrator passwords."
+msgstr "ボブは一般的なパブリックによる認証をサポートする必要があるため、ユーザー名とパスワードによる認証を提供することを選択します。彼はユーザーのパスワードを解析しようとするブルートフォース攻撃について心配します。そのため、ログイン試行回数の失敗数を制限する外部認証拡張も使用します。ボブの管理ネットワークは彼のクラウドの中で他のネットワークと分離しています。しかし、彼の企業ネットワークから SSH 経由でアクセスできます。これまでに推奨しているとおり、ボブは管理者のパスワードが漏洩するリスクを減らすために、管理者が管理ネットワークで 2 要素認証を使用することを要求します。"
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml61(para)
+#: ./doc/security-guide/ch028_case-studies-identity-management.xml56(para)
 msgid ""
-"Certificates used to support SSL/TLS on internet facing cloud endpoints (or "
-"customer interfaces where the customer is not expected to have installed "
-"anything other than standard operating system provided certificate bundles) "
-"should be provisioned using Certificate Authorities that are installed in "
-"the operating system certificate bundle. Typical well known vendors include "
-"Verisign and Thawte but many others exist."
-msgstr "インターネットに面したクラウドのエンドポイント(あるいは証明書をバンドルした標準的なOS以外の何かがインストールされていると顧客が想定していない顧客インターフェース)上のSSL/TLSに対応に使用される証明書はOSの証明書バンドル中にインストールされるCAを用いてプロビジョニングされるべきです。通常、有名ベンダーにはベリサインやThawteを含みますが、他の多くのベンダーもあります。"
+"Bob also deploys the dashboard to manage many aspects of the cloud. He "
+"deploys the dashboard with HSTS to ensure that only HTTPS is used. He has "
+"ensured that the dashboard is deployed on a second-level domain due to the "
+"limitations of the same-origin policy. He also disables "
+"<option>HORIZON_IMAGES_ALLOW_UPLOAD</option> to prevent resource exhaustion."
+msgstr "ボブはクラウドのさまざまな観点を管理するために Dashboard も導入します。必ず HTTPS のみを使用するために HSTS と共に Dashboard を導入します。Dashboard が同一オリジンポリシーの制限のため必ず第 2 レベルドメインに導入されるようにしました。また、リソース枯渇を防ぐために <option>HORIZON_IMAGES_ALLOW_UPLOAD</option> を無効化します。"
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml62(para)
+#: ./doc/security-guide/ch028_case-studies-identity-management.xml63(para)
 msgid ""
-"There are many management, policy, and technical challenges around creating "
-"and signing certificates as such is an area where cloud architects or "
-"operators may wish to seek the advice of industry leaders and vendors in "
-"addition to the guidance recommended here."
-msgstr "証明書の作成・署名については多数の管理・ポリシー・技術的ハードルがあるため、証明書は、\nここで推奨されたガイドに加え、クラウドアーキテクトや運用者が工業リーダーやベンダのアドバイスを望みうる所です。"
+"Bob decides to use VNC for his virtual console for its maturity and security"
+" features."
+msgstr "ボブはその成熟度とセキュリティ機能から仮想コンソールに VNC を使用することを決めました。"
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml65(title)
-msgid "SSL/TLS libraries"
-msgstr "SSL/TLSライブラリ"
+#: ./doc/security-guide/ch038_transport-security.xml8(title)
+msgid "Messaging security"
+msgstr "メッセージングのセキュリティ"
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml66(para)
+#: ./doc/security-guide/ch038_transport-security.xml9(para)
 msgid ""
-"Various components, services, and applications within the OpenStack "
-"ecosystem or dependencies of OpenStack are implemented and can be configured"
-" to use SSL/TLS libraries. The SSL/TLS and HTTP services within OpenStack "
-"are typically implemented using OpenSSL which has been proven to be fairly "
-"secure and has a module that has been validated for FIPS 140-2. However, "
-"keep in mind that each application or service can still introduce weaknesses"
-" in how they use the OpenSSL libraries."
-msgstr "OpenStackエコシステムやOpenStackが依存する様々なコンポーネント、サービス、アプリケーションはSSL/TLSライブラリを使用するよう実装され、設定ができるようになっています。OpenStack中のSSL/TLSとHTTPサービスは通常、非常にセキュアである事が証明され、FIPS 140-2用に検証されてきたOpenSSLを使用して実装されています。しかし、各アプリケーション又はサービスは、OpenSSLライブラリをどのように使用するかという点で、未だ脆弱性を招きうるという事を忘れないで下さい。"
+"This chapter discusses security hardening approaches for the three most "
+"common message queuing solutions use in OpenStack: RabbitMQ, Qpid, and "
+"ZeroMQ."
+msgstr "この章では、OpenStack で使用される最も一般的なメッセージキュー製品である、Rabbit MQ、Qpid、ZeroMQ の堅牢化アプローチについて説明します。"
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml69(title)
-msgid "Cryptographic algorithms, cipher modes, and protocols"
-msgstr "暗号化アルゴリズム、暗号モード、プロトコル"
+#: ./doc/security-guide/ch038_transport-security.xml11(title)
+msgid "Messaging transport security"
+msgstr "メッセージ通信路のセキュリティ"
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml70(para)
+#: ./doc/security-guide/ch038_transport-security.xml12(para)
 msgid ""
-"We recommend only using TLS v1.1 or v1.2. SSLv3 and TLSv1.0 may be used for "
-"compatibility but we recommend using caution and only enabling these "
-"protocols if you have a strong requirement to do so. Other SSL/TLS versions,"
-" explicitly older versions, should not be used. These older versions include"
-" SSLv1 and SSLv2. As this book does not intend to be a thorough reference on"
-" cryptography we do not wish to be prescriptive about what specific "
-"algorithms or cipher modes you should enable or disable in your OpenStack "
-"services. However, there are some authoritative references we would like to "
-"recommend for further information:"
-msgstr "我々は TLS v1.1 又は v1.2 の使用のみ推奨します。SSL v3 と TLS v1.0 は互換性目的で使用出来ますが、我々は、注意深く、これらのプロトコルの有効化が強い要望としてある場合にのみ有効にする事をお勧めします。他のSSL/TLSバージョン(はっきり言えば古いバージョン)は使用すべきではありません。これらの古いバージョンには SSL v1 と v2 が含まれます。本書では暗号方式の初めから終わりまでの参考書を目指していない為、我々はあなたのOpenStackサービス中でどの特定アルゴリズムや暗号モードを有効・無効にすべきかについて指図する事を望みません。しかしながら、今後の情報としてお勧めしたい権威ある参考文献があります。"
+"AMQP based solutions (Qpid and RabbitMQ) support transport-level security "
+"using SSL. ZeroMQ messaging does not natively support SSL, but transport-"
+"level security is possible using labelled IPSec or CIPSO network labels."
+msgstr "AMQP ベースの製品 (Qpid, RabbitMQ) は SSL を用いた通信路レベルのセキュリティに対応しています。ZeroMQ はSSL をネイティブでサポートしていませんが、Labeled-IPSec や CIPSO ネットワークラベルを用いた通信路レベルのセキュア化に対応しています。"
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml72(link)
-msgid "National Security Agency, Suite B Cryptography"
-msgstr "国家安全保障局、Suite B 暗号化"
-
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml75(link)
-msgid "OWASP Guide to Cryptography"
-msgstr "OWASP Guide to Cryptography"
-
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml78(link)
-msgid "OWASP Transport Layer Protection Cheat Sheet"
-msgstr "OWASP Transport Layer Protection Cheat Sheet"
-
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml81(link)
+#: ./doc/security-guide/ch038_transport-security.xml13(para)
 msgid ""
-"SoK: SSL and HTTPS: Revisiting past challenges and evaluating certificate "
-"trust model enhancements"
-msgstr "SoK: SSL and HTTPS: Revisiting past challenges and evaluating certificate trust model enhancements"
+"We highly recommend enabling transport-level cryptography for your message "
+"queue. Using SSL for the messaging client connections provides protection of"
+" the communications from tampering and eavesdropping in-transit to the "
+"messaging server. Below is guidance on how SSL is typically configured for "
+"the two popular messaging servers Qpid and RabbitMQ. When configuring the "
+"trusted certificate authority (CA) bundle that your messaging server uses to"
+" verify client connections, it is recommended that this be limited to only "
+"the CA used for your nodes, preferably an internally managed CA. The bundle "
+"of trusted CAs will determine which client certificates will be authorized "
+"and pass the client-server verification step of the setting up the SSL "
+"connection. Note, when installing the certificate and key files, ensure that"
+" the file permissions are restricted, for example chmod 0600, and the "
+"ownership is restricted to the messaging server daemon user to prevent "
+"unauthorized access by other processes and users on the messaging server."
+msgstr "メッセージキューには、通信路レベルでの暗号化を強く推奨します。メッセージクライアントとの接続に SSL を用いることで、メッセージサーバとの通信路における通信の改ざんや傍受を防ぐことが可能です。以下、よく使われる 2 種類のメッセージサーバ Qpid、および、RabbitMQ における一般的な SSL の設定について説明します。\nクライアント接続の正当性を保証する目的でメッセージサーバに証明機関 (CA) バンドルを設定する場合、該当ノードに限定した CA の使用を、またなるべくなら組織内部で管理している CA の使用を推奨します。\n信頼された CA バンドルは許可を与えるクライアント接続証明書を決定し、SSL 接続を張るためのクライアントサーバ検証のステップを通過させます。\n証明書とキーのファイルをインストールする際は、chmod 0600 などでファイルのパーミッションを限定させ、所有者をメッセージサーバのデーモンユーザに限定させるようにしてください。こうすることで、メッセージサーバ上の許可を与えていない他プロセスやユーザによるアクセスを防ぐことできます。"
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml84(link)
+#: ./doc/security-guide/ch038_transport-security.xml15(title)
+msgid "RabbitMQ server SSL configuration"
+msgstr "RabbitMQ サーバにおける SSL 設定"
+
+#: ./doc/security-guide/ch038_transport-security.xml16(para)
 msgid ""
-"The Most Dangerous Code in the World: Validating SSL Certificates in Non-"
-"Browser Software"
-msgstr "The Most Dangerous Code in the World: Validating SSL Certificates in Non-Browser Software"
+"The following lines should be added to the system-wide RabbitMQ "
+"configuration file, typically "
+"<filename>/etc/rabbitmq/rabbitmq.config</filename>:"
+msgstr "下記の設定を RabbitMQ のシステム設定ファイルに追加します。通常、<filename>/etc/rabbitmq/rabbitmq.config</filename> に保存されています。"
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml87(link)
-msgid "OpenSSL and FIPS 140-2"
-msgstr "OpenSSL and FIPS 140-2"
-
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml92(title)
-msgid "Summary"
-msgstr "概要"
-
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml93(para)
+#: ./doc/security-guide/ch038_transport-security.xml31(para)
 msgid ""
-"Given the complexity of the OpenStack components and the number of "
-"deployment possibilities, you must take care to ensure that each component "
-"gets the appropriate configuration of SSL certificates, keys, and CAs. "
-"Subsequent sections discuss the following services:"
-msgstr "OpenStack コンポーネントの複雑さとデプロイの発展性を考慮すると、確実に各コンポーネントがSSL証明書・鍵・CAを適切に設定されている事に注意を払う必要があります。以下のサービスは、本書の後の章で議論します。"
+"Note, the <literal>tcp_listeners</literal> option is set to "
+"<literal>[]</literal> to prevent it from listening an on non-SSL port. The "
+"<literal>ssl_listeners</literal> option should be restricted to only listen "
+"on the management network for the services."
+msgstr "<literal>tcp_listeners</literal> オプションを <literal>[]</literal> に指定し、非 SSL ポートの接続を受け付けない設定にしていることに注意してください。 <literal>ssl_listeners</literal> オプションはサービスの管理ネットワークのみ受け付けるよう限定すべきです。"
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml102(para)
-msgid "Compute API endpoints"
-msgstr "Compute APIエンドポイント"
+#: ./doc/security-guide/ch038_transport-security.xml36(para)
+msgid "For more information on RabbitMQ SSL configuration see:"
+msgstr "RabbitMQ の SSL 設定に関する詳細は、以下を参照してください。"
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml105(para)
-msgid "Identity API endpoints"
-msgstr "Identity APIエンドポイント"
+#: ./doc/security-guide/ch038_transport-security.xml39(link)
+msgid "RabbitMQ Configuration"
+msgstr "RabbitMQ 設定"
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml108(para)
-msgid "Networking API endpoints"
-msgstr "Networking APIエンドポイント"
+#: ./doc/security-guide/ch038_transport-security.xml43(link)
+msgid "RabbitMQ SSL"
+msgstr "RabbitMQ SSL"
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml111(para)
-msgid "Storage API endpoints"
-msgstr "ストレージAPIエンドポイント"
+#: ./doc/security-guide/ch038_transport-security.xml48(title)
+msgid "Qpid server SSL configuration"
+msgstr "Qpid サーバ SSL 設定"
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml114(para)
-msgid "Messaging server"
-msgstr "メッセージングサーバー"
+#: ./doc/security-guide/ch038_transport-security.xml49(para)
+msgid "The Apache Foundation has a messaging security guide for Qpid. See:"
+msgstr "Apache Foundation が Qpid のメッセージングセキュリティガイドを発行しています。"
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml117(para)
-msgid "Database server"
-msgstr "データベースサーバー"
+#: ./doc/security-guide/ch038_transport-security.xml51(link)
+msgid "Apache Qpid SSL"
+msgstr "Apache Qpid SSL"
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml120(para)
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml33(title)
-#: ./doc/security-guide/ch004_book-introduction.xml186(title)
-#: ./doc/security-guide/ch025_web-dashboard.xml8(title)
-msgid "Dashboard"
-msgstr "Dashboard"
+#: ./doc/security-guide/ch038_transport-security.xml57(title)
+msgid "Queue authentication and access control"
+msgstr "キューの認証およびアクセス制御"
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml123(para)
+#: ./doc/security-guide/ch038_transport-security.xml58(para)
 msgid ""
-"This guide uses the term SSL as a shorthand to refer to these "
-"recommendations for SSL/TLS protocols."
-msgstr "このガイドは、SSL/TLSプロトコルに関する推奨を示す略称として、SSL という言葉を使用します。"
+"RabbitMQ and Qpid offer authentication and access control mechanisms for "
+"controlling access to queues. ZeroMQ offers no such mechanisms."
+msgstr "RabbitMQ と Qpid はキューへのアクセス制御を目的とした、認証およびアクセス制御の仕組みを持っています。ZeroMQ にはこのような仕組みは備わっていません。"
 
-#: ./doc/security-guide/ch012_configuration-management.xml8(title)
-msgid "Continuous systems management"
-msgstr "継続的なシステム管理"
-
-#: ./doc/security-guide/ch012_configuration-management.xml9(para)
+#: ./doc/security-guide/ch038_transport-security.xml59(para)
 msgid ""
-"A cloud will always have bugs. Some of these will be security problems. For "
-"this reason, it is critically important to be prepared to apply security "
-"updates and general software updates. This involves smart use of "
-"configuration management tools, which are discussed below. This also "
-"involves knowing when an upgrade is necessary."
-msgstr "クラウドには必ずバグがあります。その中にはセキュリティの問題も含まれています。このような理由から、セキュリティ更新や一般的なソフトウェア更新の適用準備を行うことが極めて重要です。例えば、構成管理ツールを賢く利用していくことになります。これについては以下で説明しています。また、アップグレードが必要な時期を把握することも重要です。"
+"Simple Authentication and Security Layer (SASL) is a framework for "
+"authentication and data security in Internet protocols. Both RabbitMQ and "
+"Qpid offer SASL and other pluggable authentication mechanisms beyond simple "
+"usernames and passwords that allow for increased authentication security. "
+"While RabbitMQ supports SASL, support in OpenStack does not currently allow "
+"for requesting a specific SASL authentication mechanism. RabbitMQ support in"
+" OpenStack allows for either username and password authentication over an "
+"unencrypted connection or username and password in conjunction with X.509 "
+"client certificates to establish the secure SSL connection."
+msgstr "Simple Authentication and Security Layer (SASL) はインターネットプロトコルにおける認証とデータセキュリティのフレームワークです。RabbitMQ と Qpid は SASL の他、プラグイン形式の認証メカニズムを提供しており、単純なユーザ名とパスワードよりもセキュアな認証が可能になっています。RabbitMQ は SASL をサポートしているものの、現在の OpenStack は特定の SASL 認証メカニズムの使用を許可していません。RabbitMQ では、非暗号化接続でのユーザ名とパスワード認証か、X.509 クライアント証明書を用いたセキュアな SSL 接続でのユーザ名とパスワード認証がサポートされています。"
 
-#: ./doc/security-guide/ch012_configuration-management.xml16(title)
-#: ./doc/security-guide/ch063_compliance-activities.xml48(title)
-msgid "Vulnerability management"
-msgstr "脆弱性管理"
-
-#: ./doc/security-guide/ch012_configuration-management.xml17(para)
+#: ./doc/security-guide/ch038_transport-security.xml60(para)
 msgid ""
-"For announcements regarding security relevant changes, subscribe to the "
-"<link href=\"http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-"
-"announce\">OpenStack Announce mailing list</link>. The security "
-"notifications are also posted through the downstream packages for example "
-"through Linux distributions that you may be subscribed to as part of the "
-"package updates."
-msgstr "セキュリティ関連の変更に関するお知らせは、<link href=\"http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-announce\">OpenStack Announce mailing list</link> を購読してください。このセキュリティの通知は、Linux ディストリビューションなどのダウンストリームのパッケージでも掲載されます。これはパッケージ更新の一部として購読しているかもしれません。"
+"We recommend configuring X.509 client certificates on all the OpenStack "
+"service nodes for client connections to the messaging queue and where "
+"possible (currently only Qpid) perform authentication with X.509 client "
+"certificates. When using usernames and passwords, accounts should be created"
+" per-service and node for finer grained auditability of access to the queue."
+msgstr "全ての OpenStack サービスノードにおいて、メッセージキューへのクライアント接続に X.509 クライアント証明書を設定することを推奨します。また可能なら、X.509 クライアント証明書での認証も推奨します。(現在、Qpid のみがサポート)\nユーザ名とパスワードを用いる場合、キューに対するアクセスの監査の粒度を細かくする目的で、アカウントはサービス毎、ノード毎に作成するべきです。"
 
-#: ./doc/security-guide/ch012_configuration-management.xml24(para)
+#: ./doc/security-guide/ch038_transport-security.xml61(para)
 msgid ""
-"The OpenStack components are only a small fraction of the software in a "
-"cloud. It is important to keep up to date with all of these other "
-"components, too. While the specific data sources will be deployment "
-"specific, the key idea is to ensure that a cloud administrator subscribes to"
-" the necessary mailing lists for receiving notification of any related "
-"security updates. Often this is as simple as tracking an upstream Linux "
-"distribution."
-msgstr "OpenStack のコンポーネントは、クラウドにあるソフトウェアのごく一部です。これらだけではなく他のコンポーネントすべてを最新の状態に保つことが重要です。データソースはそれぞれデプロイメント固有となりますが、クラウド管理者は必要なメーリングリストを購読して、関連するセキュリティ更新の通知を受信できるようにすることが重要です。通常、Linux のアップストリームディストリビューションをチェックするのと同じくらいシンプルです。"
+"Before deployment, consider the SSL libraries that the queuing servers use. "
+"Qpid uses Mozilla's NSS library, whereas RabbitMQ uses Erlang's SSL module "
+"which uses OpenSSL."
+msgstr "導入前に、キューサーバが使用する SSL ライブラリについて考慮します。Qpid はMozilla の NSS ライブラリを、RabbitMQ は OpenSSL を使う Erlang の SSL モジュールを用いています。"
 
-#: ./doc/security-guide/ch012_configuration-management.xml36(para)
+#: ./doc/security-guide/ch038_transport-security.xml66(title)
+msgid "Authentication configuration example: RabbitMQ"
+msgstr "認証設定例: RabbitMQ"
+
+#: ./doc/security-guide/ch038_transport-security.xml67(para)
 msgid ""
-"OpenStack Security Advisories (OSSA) are created by the OpenStack "
-"Vulnerability Management Team (VMT). They pertain to security holes in core "
-"OpenStack services. More information on the VMT can be found here: <link "
-"href=\"https://wiki.openstack.org/wiki/Vulnerability_Management\">https://wiki.openstack.org/wiki/Vulnerability_Management</link>"
-msgstr "OpenStack セキュリティアドバイザリ (OSSA: OpenStack Security Advisories) は、OpenStack 脆弱性管理チーム (VMT: Vulnerability Management Team) が作成しています。コアとなる OpenStack サービスのセキュリティホールに関連するものです。VMT に関する詳細情報は、<link href=\"https://wiki.openstack.org/wiki/Vulnerability_Management\">https://wiki.openstack.org/wiki/Vulnerability_Management</link> を参照してください。"
+"On the RabbitMQ server, delete the default <literal>guest</literal> user:"
+msgstr "RabbitMQ サーバで、デフォルトの <literal>guest</literal> ユーザを削除します。"
 
-#: ./doc/security-guide/ch012_configuration-management.xml44(para)
+#: ./doc/security-guide/ch038_transport-security.xml70(para)
 msgid ""
-"OpenStack Security Notes (OSSN) were created by the OpenStack Security Group"
-" (OSSG) to support the work of the VMT. OSSN address issues in supporting "
-"software and common deployment configurations. They're referenced throughout"
-" this guide. Security Notes are archived at <link "
-"href=\"https://launchpad.net/ossn/\">https://launchpad.net/ossn/</link>"
-msgstr "OpenStack セキュリティノート (OSSN: OpenStack Security Notes) は、VMT の作業をサポートする OpenStack セキュリティグループ (OSSG: OpenStack Security Group) が 作成しています。OSSN はソフトウェアや一般的なデプロイメント設定のサポートにおける問題に対応しています。本書でも OSSN については全体的に参照しています。セキュリティノートは <link href=\"https://launchpad.net/ossn/\">https://launchpad.net/ossn/</link> でアーカイブされています。"
+"On the RabbitMQ server, for each OpenStack service or node that communicates"
+" with the message queue set up user accounts and privileges:"
+msgstr "RabbitMQ サーバにて、メッセージキューを使用する各 OpenStack サービス、または、ノード毎にユーザアカウントと権限を設定します。"
 
-#: ./doc/security-guide/ch012_configuration-management.xml33(para)
+#: ./doc/security-guide/ch038_transport-security.xml75(para)
+msgid "For additional configuration information see:"
+msgstr "追加の設定情報は以下を参照してください。"
+
+#: ./doc/security-guide/ch038_transport-security.xml77(link)
+msgid "RabbitMQ Access Control"
+msgstr "RabbitMQ アクセス制御"
+
+#: ./doc/security-guide/ch038_transport-security.xml80(link)
+msgid "RabbitMQ Authentication"
+msgstr "RabbitMQ 認証"
+
+#: ./doc/security-guide/ch038_transport-security.xml83(link)
+msgid "RabbitMQ Plugins"
+msgstr "RabbitMQ プラグイン"
+
+#: ./doc/security-guide/ch038_transport-security.xml86(link)
+msgid "RabbitMQ SASL External Auth"
+msgstr "RabbitMQ SASL 外部認証"
+
+#: ./doc/security-guide/ch038_transport-security.xml91(title)
+msgid "OpenStack service configuration: RabbitMQ"
+msgstr "OpenStack サービス設定: RabbitMQ"
+
+#: ./doc/security-guide/ch038_transport-security.xml104(title)
+msgid "Authentication configuration example: Qpid"
+msgstr "認証設定例: Qpid"
+
+#: ./doc/security-guide/ch038_transport-security.xml105(para)
+msgid "For configuration information see:"
+msgstr "設定情報は以下を参照してください。"
+
+#: ./doc/security-guide/ch038_transport-security.xml107(link)
+msgid "Apache Qpid Authentication"
+msgstr "Apache Qpid 認証"
+
+#: ./doc/security-guide/ch038_transport-security.xml110(link)
+msgid "Apache Qpid Authorization"
+msgstr "Apache Qpid 認可"
+
+#: ./doc/security-guide/ch038_transport-security.xml115(title)
+msgid "OpenStack service configuration: Qpid"
+msgstr "OpenStack サービス設定: Qpid"
+
+#: ./doc/security-guide/ch038_transport-security.xml124(para)
 msgid ""
-"OpenStack releases security information through two channels. "
-"<placeholder-1/>"
-msgstr "OpenStack は 2 つのチャネルからセキュリティ情報を発信しています。 <placeholder-1/>"
+"Optionally, if using SASL with Qpid specify the SASL mechanisms in use by "
+"adding:"
+msgstr "オプションとして Qpid で SASL を使用する場合は、下記のように SASL メカニズムを指定します。"
 
-#: ./doc/security-guide/ch012_configuration-management.xml56(title)
-msgid "Triage"
-msgstr "トリアージ"
+#: ./doc/security-guide/ch038_transport-security.xml129(title)
+msgid "Message queue process isolation and policy"
+msgstr "メッセージキュープロセスのアイソレーションとポリシー"
 
-#: ./doc/security-guide/ch012_configuration-management.xml57(para)
+#: ./doc/security-guide/ch038_transport-security.xml130(para)
 msgid ""
-"After you are notified of a security update, the next step is to determine "
-"how critical this update is to a given cloud deployment. In this case, it is"
-" useful to have a pre-defined policy. Existing vulnerability rating systems "
-"such as the common vulnerability scoring system (CVSS) v2 do not properly "
-"account for cloud deployments."
-msgstr "セキュリティ更新を通知された後、次のステップとして、指定のクラウドデプロイメントにとって、この更新がどの程度重要かを判断します。このような場合、ポリシーを事前定義しておくと便利です。共通脆弱性評価システム (CVSS) v2 などの既存の脆弱性評価システムは、クラウドデプロイメントに正しく対応していません。"
+"Each project provides a number of services which send and consume messages. "
+"Each binary which sends a message is expected to consume messages, if only "
+"replies, from the queue."
+msgstr "各プロジェクトは多数のサービスを提供し、それぞれがメッセージを送信、消費します。メッセージを送信した各バイナリは、リプライのみの場合、該当キューからメッセージを消費するはずです。"
 
-#: ./doc/security-guide/ch012_configuration-management.xml63(para)
+#: ./doc/security-guide/ch038_transport-security.xml131(para)
 msgid ""
-"In this example we introduce a scoring matrix that places vulnerabilities in"
-" three categories: Privilege Escalation, Denial of Service and Information "
-"Disclosure. Understanding the type of vulnerability and where it occurs in "
-"your infrastructure will enable you to make reasoned response decisions."
-msgstr "以下の例では、権限昇格、DoS (サービス妨害)、情報開示の 3 つのカテゴリーに脆弱性を分類した評価一覧表を紹介しています。脆弱性の種類やインフラストラクチャー内での発生箇所を理解することで、裏付けに基いた対応意思決定を下すことができます。"
+"Message queue service processes should be isolated from each other and other"
+" processes on a machine."
+msgstr "メッセージキューサービスのプロセスは、他のキューサービスのプロセスや、同一マシン上の他プロセスと分離すべきです。"
 
-#: ./doc/security-guide/ch012_configuration-management.xml69(para)
+#: ./doc/security-guide/ch038_transport-security.xml134(para)
 msgid ""
-"Privilege Escalation describes the ability of a user to act with the "
-"privileges of some other user in a system, bypassing appropriate "
-"authorization checks. For example, a standard Linux user running code or "
-"performing an operation that allows them to conduct further operations with "
-"the privileges of the root users on the system."
-msgstr "権限昇格とは、適切な認証チェックをすり抜けてシステム内の他のユーザーの権限を行使するユーザーの能力のことを指します。例えば、標準の Linux ユーザーがシステム上の root ユーザーの権限で自分の権限以上の操作を可能にするオペレーションを実行したり、コードを実行したりするなどです。"
+"Network namespaces are highly recommended for all services running on "
+"OpenStack Compute Hypervisors. This will help prevent against the bridging "
+"of network traffic between VM guests and the management network."
+msgstr "ネットワーク名前空間の設定は、OpenStack コンピュートハイパーバイザを動作させる全てのサービスで強く推奨します。ネットワーク名前空間を用いることで、VM ゲストと管理ネットワークのトラフィックがブリッジングされることを防ぎます。"
 
-#: ./doc/security-guide/ch012_configuration-management.xml75(para)
+#: ./doc/security-guide/ch038_transport-security.xml135(para)
 msgid ""
-"Denial of Service refers to an exploited vulnerability that may cause "
-"service or system disruption. This includes both distributed attacks to "
-"overwhelm network resources, and single-user attacks that are typically "
-"caused through resource allocation bugs or input induced system failure "
-"flaws."
-msgstr "サービス妨害 (DoS) とは、サービスやシステムの中断を引き起こす脆弱性を悪用することを指します。これには、ネットワークリソースを大量に使用する分散型攻撃や、リソース割り当てのバグや誘導型でのシステム障害の問題などで一般的に引き起こされるシングルユーザー攻撃の両方が含まれます。"
+"When using ZeroMQ messaging, each host must run at least one ZeroMQ message "
+"receiver to receive messages from the network and forward messages to local "
+"processes through IPC. It is possible and advisable to run an independent "
+"message receiver per project within an IPC namespace, along with other "
+"services within the same project."
+msgstr "ZeroMQ メッセージングを使用する場合、ネットワーク経由のメッセージ受信と、IPC経由によるローカルプロセスへのメッセージ送信のために、各ホストに最低 1 つの ZeroMQ メッセージレシーバーを走らせる必要があります。IPC 名前空間内にプロジェクト毎で独立したメッセージレシーバーを構築することが可能であり望ましいです。また同様に、同一プロジェクト内でも異なるサービスごとに独立したメッセージレシーバーを構築することが望ましいです。"
 
-#: ./doc/security-guide/ch012_configuration-management.xml80(para)
+#: ./doc/security-guide/ch038_transport-security.xml145(para)
 msgid ""
-"Information Disclosure vulnerabilities reveal information about your system "
-"or operations. These vulnerabilities range from debugging information "
-"disclosure, to exposure of critical security data, such as authentication "
-"credentials and passwords."
-msgstr "情報開示の脆弱性は、システムや操作の情報を公開します。これらの脆弱性は、情報開示のデバッグから認証情報やパスワードなどの重要なセキュリティデータの公開などが当てはまります。"
+"Queue servers should only accept connections from the management network. "
+"This applies to all implementations. This should be implemented through "
+"configuration of services and optionally enforced through global network "
+"policy."
+msgstr "キューサーバーは管理ネットワークからの接続のみを受け付けるべきであり、この方針はあらゆる実装に適用されます。サービスの設定を通して実装し、任意でグローバルネットワークポリシーを追加で実装します。"
 
-#: ./doc/security-guide/ch012_configuration-management.xml96(emphasis)
-msgid "Attacker position / Privilege level"
-msgstr "攻撃者の位置付け/権限レベル"
-
-#: ./doc/security-guide/ch012_configuration-management.xml102(emphasis)
-msgid "External"
-msgstr "外部"
-
-#: ./doc/security-guide/ch012_configuration-management.xml103(emphasis)
-msgid "Cloud user"
-msgstr "クラウドユーザー"
-
-#: ./doc/security-guide/ch012_configuration-management.xml105(emphasis)
-msgid "Cloud admin"
-msgstr "クラウドの管理者"
-
-#: ./doc/security-guide/ch012_configuration-management.xml107(emphasis)
-msgid "Control plane"
-msgstr "制御プレーン"
-
-#: ./doc/security-guide/ch012_configuration-management.xml111(emphasis)
-msgid "Privilege elevation (3 levels)"
-msgstr "権限昇格 (3 つのレベル)"
-
-#: ./doc/security-guide/ch012_configuration-management.xml113(para)
-#: ./doc/security-guide/ch012_configuration-management.xml121(para)
-#: ./doc/security-guide/ch012_configuration-management.xml122(para)
-#: ./doc/security-guide/ch012_configuration-management.xml129(para)
-#: ./doc/security-guide/ch012_configuration-management.xml130(para)
-#: ./doc/security-guide/ch012_configuration-management.xml131(para)
-msgid "Critical"
-msgstr "重要"
-
-#: ./doc/security-guide/ch012_configuration-management.xml114(para)
-#: ./doc/security-guide/ch012_configuration-management.xml115(para)
-#: ./doc/security-guide/ch012_configuration-management.xml116(para)
-#: ./doc/security-guide/ch012_configuration-management.xml123(para)
-#: ./doc/security-guide/ch012_configuration-management.xml124(para)
-#: ./doc/security-guide/ch012_configuration-management.xml132(para)
-msgid "n/a"
-msgstr "なし"
-
-#: ./doc/security-guide/ch012_configuration-management.xml119(emphasis)
-msgid "Privilege elevation (2 levels)"
-msgstr "権限昇格 (2 つのレベル)"
-
-#: ./doc/security-guide/ch012_configuration-management.xml127(emphasis)
-msgid "Privilege elevation (1 level)"
-msgstr "権限昇格 (1つのレベル)"
-
-#: ./doc/security-guide/ch012_configuration-management.xml135(emphasis)
-msgid "Denial of service"
-msgstr "サービス妨害 (DoS)"
-
-#: ./doc/security-guide/ch012_configuration-management.xml137(para)
-msgid "High"
-msgstr "高"
-
-#: ./doc/security-guide/ch012_configuration-management.xml138(para)
-msgid "Medium"
-msgstr "中"
-
-#: ./doc/security-guide/ch012_configuration-management.xml139(para)
-#: ./doc/security-guide/ch012_configuration-management.xml140(para)
-#: ./doc/security-guide/ch012_configuration-management.xml148(para)
-msgid "Low"
-msgstr "低"
-
-#: ./doc/security-guide/ch012_configuration-management.xml143(emphasis)
-msgid "Information disclosure"
-msgstr "情報開示"
-
-#: ./doc/security-guide/ch012_configuration-management.xml145(para)
-#: ./doc/security-guide/ch012_configuration-management.xml146(para)
-msgid "Critical / high"
-msgstr "重要/高"
-
-#: ./doc/security-guide/ch012_configuration-management.xml147(para)
-msgid "Medium / low"
-msgstr "中/低"
-
-#: ./doc/security-guide/ch012_configuration-management.xml152(para)
+#: ./doc/security-guide/ch038_transport-security.xml146(para)
 msgid ""
-"This table illustrates a generic approach to measuring the impact of a "
-"vulnerability based on where it occurs in your deployment and the effect. "
-"For example, a single level privilege escalation on a Compute API node "
-"potentially allows a standard user of the API to escalate to have the same "
-"privileges as the root user on the node."
-msgstr "この表は、デプロイメントの発生箇所や影響をもとに脆弱性から受ける影響レベルを測定するための一般的な手法を示しています。例えば、Compute API ノードで権限レベルを 1 つ昇格すると、API の標準ユーザーはこのノード上の root ユーザーと同等の権限にまで昇格することが可能です。"
+"When using ZeroMQ messaging, each project should run a separate ZeroMQ "
+"receiver process on a port dedicated to services belonging to that project. "
+"This is equivalent to the AMQP concept of control exchanges."
+msgstr "ZeroMQ を使用するのであれば、各プロジェクトで独立した専用のポート上で動作する ZeroMQ レシーバープロセスを用意すべきです。これは、AMQP のコントロール exchange の概念に相当します。"
 
-#: ./doc/security-guide/ch012_configuration-management.xml158(para)
+#: ./doc/security-guide/ch038_transport-security.xml150(para)
 msgid ""
-"We suggest that cloud administrators use this table as a model to help "
-"define which actions to take for the various security levels. For example, a"
-" critical-level security update might require the cloud to be upgraded on a "
-"specified time line, whereas a low-level update might be more relaxed."
-msgstr "クラウド管理者が、さまざまなセキュリティレベルに合わせて実行するアクションを定義する役に立てるために、この表をモデルとして使用することを推奨します。例えば、レベルが「重要」であるセキュリティ更新では、指定のスケジュールでクラウドのアップグレードが必要となる可能性がありますが、レベルが「低」の更新ではそこまで厳しくないでしょう。"
+"The configuration for these processes should be restricted to those "
+"processes, not only by Directory Access Controls, but through Mandatory "
+"Access Controls. The goal of such restrictions is to prevent isolation from "
+"other processes running on the same machine(s)."
+msgstr "各プロセスに行なった設定は、他プロセスに影響を与えないよう制限をかけるべきです。そのためには、ダイレクトアクセス制御のみではなく、強制アクセス制御を使用します。このような制限をかけるのは、同一マシンで動作する他プロセスとの隔離を防ぐことが目的です。"
 
-#: ./doc/security-guide/ch012_configuration-management.xml165(title)
-msgid "Testing the updates"
-msgstr "更新のテスト"
+#: ./doc/security-guide/ch024_authentication.xml8(title)
+msgid "Identity"
+msgstr "Identity"
 
-#: ./doc/security-guide/ch012_configuration-management.xml166(para)
+#: ./doc/security-guide/ch024_authentication.xml9(para)
 msgid ""
-"You should test any update before you deploy it in a production environment."
-" Typically this requires having a separate test cloud setup that first "
-"receives the update. This cloud should be as close to the production cloud "
-"as possible, in terms of software and hardware. Updates should be tested "
-"thoroughly in terms of performance impact, stability, application impact, "
-"and more. Especially important is to verify that the problem theoretically "
-"addressed by the update, such as a specific vulnerability, is actually "
-"fixed."
-msgstr "何らかの更新を本番環境にデプロイする前に、それらをテストするようにしてください。一般的に、更新を最初に受信するテスト用のクラウド設定が別途必要になります。このクラウドのソフトウェアやハードウェアはできるだけ実稼働クラウドと同じ環境にする必要があります。パフォーマンスの影響、安定性、アプリケーションへの影響など、更新全体をテストする必要があります。特に重要なのは、更新で理論上対応されている問題 (例: 特定の脆弱性) が実際に修正されているかどうかを確認することです。"
+"The OpenStack Identity service (keystone) supports multiple methods of "
+"authentication, including username &amp; password, LDAP, and external "
+"authentication methods. Upon successful authentication, The Identity Service"
+" provides the user with an authorization token used for subsequent service "
+"requests."
+msgstr "OpenStack Identity Service (keystone) は、ユーザー名・パスワード、LDAP、外部認証方式など、複数の認証方式をサポートします。認証に成功すると、Identity Service は後続のサービスリクエストに使用する認可トークンをユーザーに返します。"
 
-#: ./doc/security-guide/ch012_configuration-management.xml177(title)
-msgid "Deploying the updates"
-msgstr "更新のデプロイ"
-
-#: ./doc/security-guide/ch012_configuration-management.xml178(para)
+#: ./doc/security-guide/ch024_authentication.xml14(para)
 msgid ""
-"Once the updates are fully tested, they can be deployed to the production "
-"environment. This deployment should be fully automated using the "
-"configuration management tools described below."
-msgstr "更新の完全なテストが終了すると、実稼働環境にデプロイすることができます。このデプロイメントは、以下に記載の構成管理ツールで完全に自動的に行われます。"
+"Transport Layer Security TLS/SSL provides authentication between services "
+"and persons using X.509 certificates. Although the default mode for SSL is "
+"server-side only authentication, certificates may also be used for client "
+"authentication."
+msgstr "Transport Layer Security TLS/SSL は、サービスと人の間で X.509 を使用した認証を提供します。SSL の規定のモードはサーバーのみを認証しますが、証明書はクライアント認証にも使用できます。"
 
-#: ./doc/security-guide/ch012_configuration-management.xml185(title)
-msgid "Configuration management"
-msgstr "設定管理"
+#: ./doc/security-guide/ch024_authentication.xml19(title)
+msgid "Authentication"
+msgstr "認証"
 
-#: ./doc/security-guide/ch012_configuration-management.xml186(para)
+#: ./doc/security-guide/ch024_authentication.xml21(title)
+msgid "Invalid login attempts"
+msgstr "無効なログイン試行"
+
+#: ./doc/security-guide/ch024_authentication.xml22(para)
 msgid ""
-"A production quality cloud should always use tools to automate configuration"
-" and deployment. This eliminates human error, and allows the cloud to scale "
-"much more rapidly. Automation also helps with continuous integration and "
-"testing."
-msgstr "実稼働環境の品質を持つクラウドは設定とデプロイメントの自動化ツールを必ず使用しています。こうすることで、人的ミスをなくし、クラウドの迅速なスケールアウトが可能になります。自動化により、継続的な統合やテストが行いやすくなります。"
+"The Identity Service does not provide a method to limit access to accounts "
+"after repeated unsuccessful login attempts. Repeated failed login attempts "
+"are likely brute-force attacks (Refer figure Attack-types). This is a more "
+"significant issue in Public clouds."
+msgstr "Identity は、ログイン試行が連続して失敗した後に、アカウントへのアクセスを制限する方法を提供していません。何度も失敗するログイン試行は総当たり攻撃 (図「攻撃の種類」参照) のようなものです。これは、パブリッククラウドでは、より重要な問題です。"
 
-#: ./doc/security-guide/ch012_configuration-management.xml191(para)
+#: ./doc/security-guide/ch024_authentication.xml27(para)
 msgid ""
-"When building an OpenStack cloud it is strongly recommended to approach your"
-" design and implementation with a configuration management tool or framework"
-" in mind. Configuration management allows you to avoid the many pitfalls "
-"inherent in building, managing, and maintaining an infrastructure as complex"
-" as OpenStack. By producing the manifests, cookbooks, or templates required "
-"for a configuration management utility, you are able to satisfy a number of "
-"documentation and regulatory reporting requirements. Further, configuration "
-"management can also function as part of your BCP and DR plans wherein you "
-"can rebuild a node or service back to a known state in a DR event or given a"
-" compromise."
-msgstr "OpenStack クラウドの構築時は、構成管理ツールまたはフレームワークを念頭に設計、実装に着手するように強く推奨します。構成管理により、OpenStack のように複雑なインフラストラクチャーの構築、管理、維持において陥りやすい多くの問題を回避することができます。構成管理ユーティリティに必要なマニフェスト、クックブック、テンプレートを作成することで、多くの文書や監督機関へのレポート要件を満たすことができます。さらに、構成管理は、BCP および DR プランの一部としても機能する可能性もあります。その場合、DR やセキュリティ侵害があった場合にノードやサービスを既知の状態へ再構築することができます。"
+"Prevention is possible by using an external authentication system that "
+"blocks out an account after some configured number of failed login attempts."
+" The account then may only be unlocked with further side-channel "
+"intervention."
+msgstr "ログイン試行を指定した回数だけ失敗すると、アカウントをブロックするような外部認証システムを使用することにより、防止することができます。アカウントは、別の連絡手段を介してのみ、ロック解除するようにできます。"
 
-#: ./doc/security-guide/ch012_configuration-management.xml203(para)
+#: ./doc/security-guide/ch024_authentication.xml31(para)
 msgid ""
-"Additionally, when combined with a version control system such as Git or "
-"SVN, you can track changes to your environment over time and re-mediate "
-"unauthorized changes that may occur. For example, a "
-"<filename>nova.conf</filename> file or other configuration file falls out of"
-" compliance with your standard, your configuration management tool can "
-"revert or replace the file and bring your configuration back into a known "
-"state. Finally a configuration management tool can also be used to deploy "
-"updates; simplifying the security patch process. These tools have a broad "
-"range of capabilities that are useful in this space. The key point for "
-"securing your cloud is to choose a tool for configuration management and use"
-" it."
-msgstr "さらに、Git や SVN などのバージョン管理システムと統合すると、経年の環境の変化をチェックして、発生する可能性のある未認証の変更を修正することができます。例えば、<filename>nova.conf</filename> ファイルやその他の設定ファイルが規格に準拠しなくなった場合、既知の状態に構成管理ツールはファイルを復元または置き換えることができるでしょう。最後に、構成管理ツールを使用して、更新のデプロイも可能で、セキュリティパッチのプロセスを簡素化します。これらのツールには、この項において便利な機能が幅広く含まれています。クラウドのセキュリティ確保の主な目的は、構成管理のツールを選択して使用することです。"
+"If prevention is not an option, detection can be used to mitigate "
+"damage.Detection involves frequent review of access control logs to identify"
+" unauthorized attempts to access accounts. Possible remediation would "
+"include reviewing the strength of the user password, or blocking the network"
+" source of the attack through firewall rules. Firewall rules on the keystone"
+" server that restrict the number of connections could be used to reduce the "
+"attack effectiveness, and thus dissuade the attacker."
+msgstr "もし防止することが選択肢になければ、被害を減らすために、検知することができます。検知は、アカウントへの権限のないアクセスを特定するために、アクセス制御ログを頻繁にレビューすることを意味します。その他の改善法としては、ユーザーパスワードの強度のレビュー、ファイアウォールルールで攻撃のネットワーク送信元のブロックなどがあります。接続数を制限するという、Keystone サーバのファイアウォールルールは、攻撃の効率を悪くし、攻撃者をあきらめさせるために使用できます。"
 
-#: ./doc/security-guide/ch012_configuration-management.xml215(para)
+#: ./doc/security-guide/ch024_authentication.xml40(para)
 msgid ""
-"There are many configuration management solutions; at the time of this "
-"writing there are two in the marketplace that are robust in their support of"
-" OpenStack environments: <glossterm>Chef</glossterm> and "
-"<glossterm>Puppet</glossterm>. A non-exhaustive listing of tools in this "
-"space is provided below:"
-msgstr "構成管理ソリューションは多数存在しますが、本書の作成時点で市場にあるソリューションで OpenStack 環境のサポートが強力なものは <glossterm>Chef</glossterm> と <glossterm>Puppet</glossterm> の 2 種類となっています。以下に完全ではありませんが、ツールのリストを示しています。"
+"In addition, it is useful to examine account activity for unusual login "
+"times and suspicious actions, with possibly disable the account. Oftentimes "
+"this approach is taken by credit card providers for fraud detection and "
+"alert."
+msgstr "さらに、普通でないログイン回数や疑わしいアクションに対して、アカウントの活動状況を確認することは有用です。可能ならば、アカウントを無効化します。しばしば、このアプローチはクレジットカード提供者により、詐欺の検出や警告のために使用されます。"
 
-#: ./doc/security-guide/ch012_configuration-management.xml223(para)
-msgid "Chef"
-msgstr "Chef"
+#: ./doc/security-guide/ch024_authentication.xml46(title)
+msgid "Multi-factor authentication"
+msgstr "多要素認証"
 
-#: ./doc/security-guide/ch012_configuration-management.xml226(para)
-msgid "Puppet"
-msgstr "Puppet"
-
-#: ./doc/security-guide/ch012_configuration-management.xml229(para)
-msgid "Salt Stack"
-msgstr "Salt Stack"
-
-#: ./doc/security-guide/ch012_configuration-management.xml232(para)
-msgid "Ansible"
-msgstr "Ansible"
-
-#: ./doc/security-guide/ch012_configuration-management.xml236(title)
-msgid "Policy changes"
-msgstr "ポリシーの変更"
-
-#: ./doc/security-guide/ch012_configuration-management.xml237(para)
+#: ./doc/security-guide/ch024_authentication.xml47(para)
 msgid ""
-"Whenever a policy or configuration management is changed, it is good "
-"practice to log the activity, and backup a copy of the new set. Often, such "
-"policies and configurations are stored in a version controlled repository "
-"such as git."
-msgstr "ポリシーや構成管理が変更されると、そのアクティビティをロギングして、新しいセットのコピーをバックアップすると慣習として良いでしょう。通常、このようなポリシーや設定は Git などのバージョン管理リポジトリに保存されています。"
+"Employ multi-factor authentication for network access to privileged user "
+"accounts. The Identity Service supports external authentication services "
+"through the Apache web server that can provide this functionality. Servers "
+"may also enforce client-side authentication using certificates."
+msgstr "権限のあるユーザーアカウントにネットワークアクセス用の多要素認証を使用します。Identity はこの機能を提供できる Apache Web サーバーを通して外部認証サービスをサポートします。サーバーは証明書を使用したクライアント認証を強制することもできます。"
 
-#: ./doc/security-guide/ch012_configuration-management.xml244(title)
-msgid "Secure backup and recovery"
-msgstr "セキュアなバックアップとリカバリ"
-
-#: ./doc/security-guide/ch012_configuration-management.xml245(para)
+#: ./doc/security-guide/ch024_authentication.xml52(para)
 msgid ""
-"It is important to include Backup procedures and policies in the overall "
-"System Security Plan. For a good overview of OpenStack's Backup and Recovery"
-" capabilities and procedures, please refer to the OpenStack Operations "
-"Guide."
-msgstr "全体的なシステムセキュリティプランにバックアップ手順とポリシーを含めることは重要です。OpenStack のバックアップ／リカバリー機能や手順についての適切な概要は、OpenStack 運用ガイドを参照してください。"
+"This recommendation provides insulation from brute force, social "
+"engineering, and both spear and mass phishing attacks that may compromise "
+"administrator passwords."
+msgstr "このお勧めの方式は、管理者パスワードを流出させる可能性のある、総当たり、ソーシャルエンジニアリング、標的型と無差別のフィッシング攻撃に対する防御になります。"
 
-#: ./doc/security-guide/ch012_configuration-management.xml250(title)
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml60(title)
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml117(title)
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml150(title)
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml174(title)
-#: ./doc/security-guide/ch026_compute.xml45(title)
-#: ./doc/security-guide/ch026_compute.xml90(title)
-msgid "Security considerations"
-msgstr "セキュリティの課題"
+#: ./doc/security-guide/ch024_authentication.xml58(title)
+msgid "Authentication methods"
+msgstr "認証方式"
 
-#: ./doc/security-guide/ch012_configuration-management.xml253(para)
+#: ./doc/security-guide/ch024_authentication.xml60(title)
+msgid "Internally implemented authentication methods"
+msgstr "内部実装認証方式"
+
+#: ./doc/security-guide/ch024_authentication.xml61(para)
 msgid ""
-"Ensure only authenticated users and backup clients have access to the backup"
-" server."
-msgstr "認証済みのユーザーおよびバックアップクライアントのみがバックアップサーバーにアクセスできるようにすること"
+"The Identity Service can store user credentials in an SQL Database, or may "
+"use an LDAP-compliant directory server. The Identity database may be "
+"separate from databases used by other OpenStack services to reduce the risk "
+"of a compromise of the stored credentials."
+msgstr "Identity はユーザーのクレデンシャルを SQL データベースに保存できます。または、LDAP 対応のディレクトリサーバーを使用できます。Identity のデータベースは、保存されているクレデンシャルが漏洩するリスクを減らすために、他の OpenStack サービスが使用するデータベースと分離することもできます。"
 
-#: ./doc/security-guide/ch012_configuration-management.xml257(para)
-msgid "Use data encryption options for storage and transmission of backups."
-msgstr "バックアップの保存や送信にはデータ暗号化オプションを使用すること"
-
-#: ./doc/security-guide/ch012_configuration-management.xml261(para)
+#: ./doc/security-guide/ch024_authentication.xml66(para)
 msgid ""
-"Use a dedicated and hardened backup servers. The logs for the backup server "
-"must be monitored daily and accessible by only few individuals."
-msgstr "セキュリティが強化された専用のバックアップサーバーを使用すること。バックアップサーバーのログは日次で監査し、ほんの一握りの人だけがこのログにアクセスできるようにしなければいけません。"
+"When you use a user name and password to authenticate, Identity does not "
+"enforce policies on password strength, expiration, or failed authentication "
+"attempts as recommended by NIST Special Publication 800-118 (draft). "
+"Organizations that desire to enforce stronger password policies should "
+"consider using Identity extensions or external authentication services."
+msgstr "認証のためにユーザー名とパスワードを使用する場合、Identity は NIST Special Publication 800-118 (draft) により推奨されている、パスワード強度、有効期限、ログイン試行回数制限に関するポリシーを強制できません。より強固なパスワードポリシーを強制したい組織は、Identity 拡張や外部認証サービスの使用を検討すべきです。"
 
-#: ./doc/security-guide/ch012_configuration-management.xml266(para)
+#: ./doc/security-guide/ch024_authentication.xml74(para)
 msgid ""
-"Test data recovery options regularly. One of the things that can be restored"
-" from secured backups is the images. In case of a compromise, the best "
-"practice would be to terminate running instances immediately and then "
-"relaunch the instances from the images in the secured backup repository."
-msgstr "データのリカバリーオプションを定期的にテストすること。セキュアなバックアップからリストアが可能なものの 1 つにイメージがあります。情報漏洩などが発生した場合のベストプラクティスは、すぐに実行中のインスタンスを終了して、セキュアなバックアップリポジトリにあるイメージからインスタンスを再起動することです。"
+"LDAP simplifies integration of Identity authentication into an "
+"organization's existing directory service and user account management "
+"processes."
+msgstr "LDAP により、組織の既存のディレクトリサービスやユーザーアカウント管理プロセスに Identity 認証をシンプルに統合できます。"
 
-#: ./doc/security-guide/ch012_configuration-management.xml276(title)
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml90(title)
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml160(title)
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml199(title)
-#: ./doc/security-guide/ch026_compute.xml60(title)
-#: ./doc/security-guide/ch026_compute.xml106(title)
-#: ./doc/security-guide/ch058_forensicsincident-response.xml48(title)
-msgid "References"
-msgstr "参考資料"
-
-#: ./doc/security-guide/ch012_configuration-management.xml279(para)
+#: ./doc/security-guide/ch024_authentication.xml77(para)
 msgid ""
-"<citetitle>OpenStack Operations Guide</citetitle> on <link "
-"href=\"http://docs.openstack.org/trunk/openstack-"
-"ops/content/backup_and_recovery.html\">backup and recovery</link>"
-msgstr "<citetitle>OpenStack 運用ガイド</citetitle> の <link href=\"http://docs.openstack.org/trunk/openstack-ops/content/backup_and_recovery.html\">バックアップとリカバリー</link>"
+"Authentication and authorization policy in OpenStack may be delegated to an "
+"external LDAP server. A typical use case is an organization that seeks to "
+"deploy a private cloud and already has a database of employees, the users. "
+"This may be in an LDAP system. Using LDAP as a source of authority "
+"authentication, requests to Identity Service are delegated to the LDAP "
+"service, which will authorize or deny requests based on locally set "
+"policies. A token is generated on successful authentication."
+msgstr "OpenStack の認証と認可のポリシーは、外部 LDAP サーバーに権限委譲することができます。一般的なユースケースは、プライベートクラウドの導入を検討していて、すでに従業員とユーザーのデーターベースを持っている組織です。これは LDAP システムにあるかもしれません。権限のある認証のソースとして LDAP を使用することが、LDAP サービスに権限委譲している Identity に要求されます。このサービスがローカルに設定されたポリシーに基づいて認可または拒否します。トークンは認証が成功した場合に生成されます。"
 
-#: ./doc/security-guide/ch012_configuration-management.xml287(link)
+#: ./doc/security-guide/ch024_authentication.xml86(para)
 msgid ""
-"http://www.sans.org/reading_room/whitepapers/backup/security-considerations-"
-"enterprise-level-backups_515"
-msgstr "http://www.sans.org/reading_room/whitepapers/backup/security-considerations-enterprise-level-backups_515"
+"Note that if the LDAP system has attributes defined for the user such as "
+"admin, finance, HR etc, these must be mapped into roles and groups within "
+"Identity for use by the various OpenStack services. The "
+"<filename>/etc/keystone.conf</filename> file maps LDAP attributes to "
+"Identity attributes."
+msgstr "LDAP システムがユーザーに対して定義された、幹部社員、経理、人事などのような属性を持っている場合、これらはさまざまな OpenStack サービスにより使用するために Identity の中でロールとグループにマッピングされる必要があります。<filename>/etc/keystone.conf</filename> ファイルは、LDAP の属性をIdentity の属性にマッピングします。"
 
-#: ./doc/security-guide/ch012_configuration-management.xml291(link)
-msgid "OpenStack Security Primer"
-msgstr "OpenStack セキュリティ入門"
-
-#: ./doc/security-guide/ch012_configuration-management.xml297(title)
-msgid "Security auditing tools"
-msgstr "セキュリティ監査ツール"
-
-#: ./doc/security-guide/ch012_configuration-management.xml298(para)
+#: ./doc/security-guide/ch024_authentication.xml91(para)
 msgid ""
-"Security auditing tools can complement the configuration management tools. "
-"Security auditing tools automate the process of verifying that a large "
-"number of security controls are satisfied for a given system configuration. "
-"These tools help to bridge the gap from security configuration guidance "
-"documentation (for example, the STIG and NSA Guides) to a specific system "
-"installation. For example, <link href=\"https://fedorahosted.org/scap-"
-"security-guide/\">SCAP</link> can compare a running system to a pre-defined "
-"profile. SCAP outputs a report detailing which controls in the profile were "
-"satisfied, which ones failed, and which ones were not checked."
-msgstr "セキュリティ監査ツールは、構成管理ツールを補完することができます。セキュリティ監査ツールは、セキュリティ制御の多くが指定のシステム設定を満たしていることを確認するプロセスを自動化します。これらのツールは、セキュリティ設定方針文書 (例: STIG  および NSA ガイド) から個別のシステムインストール環境のギャップを埋めるサポートをします。例えば、<link href=\"https://fedorahosted.org/scap-security-guide/\">SCAP</link> は実行中のシステムと事前定義済みのプロファイルを比較することができます。SCAP はプロファイル内のどの制御に対応しているか、問題があるものはどれか、確認されていないものはどれかを詳細にまとめたレポートを出力します。"
+"The Identity Service <emphasis role=\"bold\">MUST NOT</emphasis> be allowed "
+"to write to LDAP services used for authentication outside of the OpenStack "
+"deployment as this would allow a sufficiently privileged keystone user to "
+"make changes to the LDAP directory. This would allow privilege escalation "
+"within the wider organization or facilitate unauthorized access to other "
+"information and resources. In such a deployment, user provisioning would be "
+"out of the realm of the OpenStack deployment."
+msgstr "Identity Service は OpenStack の外部にある認証用 LDAP サービスに書き込みを許可<emphasis role=\"bold\">してはいけません</emphasis>。十分な権限を持つ keystone ユーザーが LDAP ディレクトリに変更を加えられるようになるからです。これにより、より広い範囲の組織に権限が増えたり、他の情報やリソースに権限のアクセスが容易になったりするかもしれません。このような環境では、ユーザーの払い出しが OpenStack 環境のレルムの範囲外になるかもしれません。"
 
-#: ./doc/security-guide/ch012_configuration-management.xml310(para)
+#: ./doc/security-guide/ch024_authentication.xml101(para)
 msgid ""
-"Combining configuration management and security auditing tools creates a "
-"powerful combination. The auditing tools will highlight deployment concerns."
-" And the configuration management tools simplify the process of changing "
-"each system to address the audit concerns. Used together in this fashion, "
-"these tools help to maintain a cloud that satisfies security requirements "
-"ranging from basic hardening to compliance validation."
-msgstr "構成管理とセキュリティ監査ツールを組み合わせることで強力になります。監査ツールはデプロイメントの課題をハイライトし、構成管理ツールは各システムの変更プロセスを簡素化して監査の課題に対応していきます。このような方法で組み合わせて使用することで、これらのツールは、基本的なセキュリティの強化からコンプライアンスのバリデーションに至るまで、このようなセキュリティ要件を満たすクラウドを維持できるようにします。"
+"There is an <link "
+"href=\"https://bugs.launchpad.net/ossn/+bug/1168252\">OpenStack Security "
+"Note (OSSN) regarding keystone.conf permissions</link>."
+msgstr "<link href=\"https://bugs.launchpad.net/ossn/+bug/1168252\">keystone.conf のパーミッションに関する OpenStack Security Note (OSSN)</link> があります。"
 
-#: ./doc/security-guide/ch012_configuration-management.xml317(para)
+#: ./doc/security-guide/ch024_authentication.xml105(para)
 msgid ""
-"Configuration management and security auditing tools will introduce another "
-"layer of complexity into the cloud. This complexity brings additional "
-"security concerns with it. We view this as an acceptable risk trade-off, "
-"given their security benefits. Securing the operational use of these tools "
-"is beyond the scope of this guide."
-msgstr "構成管理およびセキュリティ監査ツールは、もう１つのレベルで複雑性をクラウドにもたらします。この複雑性により、新たなセキュリティの課題が出てきます。これについては、セキュリティの利点もあるため、許容範囲のリスクのトレードオフという見解を持っています。これらのツールの運用におけるセキュリティ確保については、本書の対象外となっています。"
+"There is an <link "
+"href=\"https://bugs.launchpad.net/ossn/+bug/1155566\">OpenStack Security "
+"Note (OSSN) regarding potential DoS attacks</link>."
+msgstr "<link href=\"https://bugs.launchpad.net/ossn/+bug/1155566\">潜在的な DoS 攻撃に関する OpenStack Security Note (OSSN)</link> があります。"
+
+#: ./doc/security-guide/ch024_authentication.xml112(title)
+msgid "External authentication methods"
+msgstr "外部認証方式"
+
+#: ./doc/security-guide/ch024_authentication.xml113(para)
+msgid ""
+"Organizations may desire to implement external authentication for "
+"compatibility with existing authentication services or to enforce stronger "
+"authentication policy requirements. Although passwords are the most common "
+"form of authentication, they can be compromised through numerous methods, "
+"including keystroke logging and password compromise. External authentication"
+" services can provide alternative forms of authentication that minimize the "
+"risk from weak passwords."
+msgstr "組織は、既存の認証サービスとの互換性のために外部認証を実装したいかもしれません。または、より強固な認証ポリシー要件を強制するためかもしれません。パスワードが認証のもっとも一般的な形式ですが、キー入力ロギングやパスワード推測など、さまざまな方法で破られる可能性があります。外部認証サービスにより、弱いパスワードのリスクを最小化する他の認証形式を提供できます。"
+
+#: ./doc/security-guide/ch024_authentication.xml122(para)
+msgid "These include:"
+msgstr "これらは以下のものが含まれます。"
+
+#: ./doc/security-guide/ch024_authentication.xml125(para)
+msgid ""
+"Password policy enforcement: Requires user passwords to conform to minimum "
+"standards for length, diversity of characters, expiration, or failed login "
+"attempts."
+msgstr "パスワードポリシー強制: ユーザーパスワードが、長さ、文字種の量、有効期限、失敗試行回数の最低基準を満たしていることを要求します。"
+
+#: ./doc/security-guide/ch024_authentication.xml130(para)
+msgid ""
+"Multi-factor authentication: The authentication service requires the user to"
+" provide information based on something they have, such as a one-time "
+"password token or X.509 certificate, and something they know, such as a "
+"password."
+msgstr "多要素認証: 認証サービスが、ユーザーが持っているもの (例: ワンタイムパスワードトークン、X.509 証明書) と知っていること (例: パスワード) に基づいた情報を提示するよう要求します。"
+
+#: ./doc/security-guide/ch024_authentication.xml137(para)
+msgid "Kerberos"
+msgstr "Kerberos"
+
+#: ./doc/security-guide/ch024_authentication.xml143(title)
+msgid "Authorization"
+msgstr "認可"
+
+#: ./doc/security-guide/ch024_authentication.xml144(para)
+msgid ""
+"The Identity Service supports the notion of groups and roles. Users belong "
+"to groups. A group has a list of roles. OpenStack services reference the "
+"roles of the user attempting to access the service. The OpenStack policy "
+"enforcer middleware takes into consideration the policy rule associated with"
+" each resource and the user's group/roles and tenant association to "
+"determine if he/she has access to the requested resource."
+msgstr "Identity はグループとロールの概念をサポートします。ユーザーはグループに所属します。グループはロールの一覧を持ちます。OpenStack サービスはユーザーがサービスにアクセスしようとしているロールを参照します。OpenStack ポリシー判定ミドルウェアにより、各リソースに関連付けられたポリシールール、ユーザーのグループとロール、テナント割り当てを考慮して、要求されたリソースへのアクセスが判断されます。"
+
+#: ./doc/security-guide/ch024_authentication.xml151(para)
+msgid ""
+"The Policy enforcement middleware enables fine-grained access control to "
+"OpenStack resources. Only admin users can provision new users and have "
+"access to various management functionality. The cloud tenant would be able "
+"to only spin up instances, attach volumes, etc."
+msgstr "ポリシー強制ミドルウェアにより OpenStack リソースに細かなアクセス制御を実現できます。管理ユーザーのみが新しいユーザーを作成でき、さまざまな管理機能にアクセスできます。クラウドのテナントはインスタンスの稼動、ボリュームの接続などのみが実行できます。"
+
+#: ./doc/security-guide/ch024_authentication.xml157(title)
+msgid "Establish formal access control policies"
+msgstr "公式なアクセス制御ポリシーの確立"
+
+#: ./doc/security-guide/ch024_authentication.xml158(para)
+msgid ""
+"Prior to configuring roles, groups, and users, document your required access"
+" control policies for the OpenStack installation. The policies should be "
+"consistent with any regulatory or legal requirements for the organization. "
+"Future modifications to access control configuration should be done "
+"consistently with the formal policies. The policies should include the "
+"conditions and processes for creating, deleting, disabling, and enabling "
+"accounts, and for assigning privileges to the accounts. Periodically review "
+"the policies and ensure that configuration is in compliance with approved "
+"policies."
+msgstr "ロール、グループ、ユーザーを設定する前に、OpenStack に必要なアクセス制御ポリシーをドキュメント化します。ポリシーは組織に対するあらゆる規制や法令の要求事項に沿っているべきです。アクセス制御設定のさらなる変更は公式なポリシーに従って実行されるべきです。ポリシーは、アカウントの作成、削除、無効化、有効化、および権限の割り当てに関する条件とプロセスを含めるべきです。定期的にポリシーをレビューし、設定が承認されたポリシーに従っていることを確認します。"
+
+#: ./doc/security-guide/ch024_authentication.xml171(title)
+msgid "Service authorization"
+msgstr "サービス認可"
+
+#: ./doc/security-guide/ch024_authentication.xml172(para)
+msgid ""
+"As described in the <link href=\"http://docs.openstack.org/admin-guide-"
+"cloud/content/index.html\"><citetitle>OpenStack Cloud Administrator "
+"Guide</citetitle></link>, cloud administrators must define a user for each "
+"service, with a role of Admin. This service user account provides the "
+"service with the authorization to authenticate users."
+msgstr "<link href=\"http://docs.openstack.org/admin-guide-cloud/content/index.html\"><citetitle>OpenStack Cloud Administrator Guide</citetitle></link> に記載されているとおり、クラウド管理者は各サービスに対して Admin ロールを持つユーザーを定義する必要があります。このサービスユーザーアカウントは、サービスがユーザーを認証するための権限を提供します。"
+
+#: ./doc/security-guide/ch024_authentication.xml179(para)
+msgid ""
+"The Compute and Object Storage services can be configured to use either the "
+"\"tempAuth\" file or Identity Service to store authentication information. "
+"The \"tempAuth\" solution MUST NOT be deployed in a production environment "
+"since it stores passwords in plain text."
+msgstr "Nova と Swift のサービスは認証情報を保存するために \"tempAuth\" ファイルと Identity を使用するよう設定できます。\"tempAuth\" ソリューションは、パスワードを平文で保存するため、本番環境で使用してはいけません。"
+
+#: ./doc/security-guide/ch024_authentication.xml184(para)
+msgid ""
+"The Identity Service supports client authentication for SSL which may be "
+"enabled. SSL client authentication provides an additional authentication "
+"factor, in addition to the username / password, that provides greater "
+"reliability on user identification. It reduces the risk of unauthorized "
+"access when user names and passwords may be compromised. However, there is "
+"additional administrative overhead and cost to issue certificates to users "
+"that may not be feasible in every deployment."
+msgstr "Identity は SSL のクライアント認証を有効化していると、それをサポートします。SSL クライアント認証はユーザー名、パスワードに加えて、ユーザー識別により信頼性を与えるために追加の認証要素を提供します。ユーザー名とパスワードが漏えいした場合に、権限のないアクセスのリスクを減らすことができます。しかしながら、証明書をユーザーに発行する追加の管理作業とコストが発生します。これはすべての環境で実現できるとは限りません。"
+
+#: ./doc/security-guide/ch024_authentication.xml194(para)
+msgid ""
+"We recommend that you use client authentication with SSL for the "
+"authentication of services to the Identity Service."
+msgstr "Identity にサービスの認証をするとき、SSL を使用したクライアント認証を使用することを推奨します。"
+
+#: ./doc/security-guide/ch024_authentication.xml198(para)
+msgid ""
+"The cloud administrator should protect sensitive configuration files for "
+"unauthorized modification. This can be achieved with mandatory access "
+"control frameworks such as SELinux, including "
+"<filename>/etc/keystone.conf</filename> and X.509 certificates."
+msgstr "クラウド管理者は権限のない変更から重要な設定ファイルを保護すべきです。これは SELinux のような強制アクセス制御のフレームワークで実現できます。これらには <filename>/etc/keystone.conf</filename> や X.509 証明書などがあります。"
+
+#: ./doc/security-guide/ch024_authentication.xml204(para)
+msgid ""
+"For client authentication with SSL, you need to issue certificates. These "
+"certificates can be signed by an external authority or by the cloud "
+"administrator. OpenStack services by default check the signatures of "
+"certificates and connections fail if the signature cannot be checked. If the"
+" administrator uses self-signed certificates, the check might need to be "
+"disabled. To disable these certificates, set <code>insecure=False</code> in "
+"the <code>[filter:authtoken]</code> section in the "
+"<filename>/etc/nova/api.paste.ini</filename> file. This setting also "
+"disables certificates for other components."
+msgstr "SSL を用いたクライアント認証のために、証明書を発行する必要があります。これらの証明書は外部の認証局やクラウド管理者により署名できます。OpenStack のサービスはデフォルトで証明書の署名を確認します。証明が確認できなければ、接続に失敗します。管理者が自己署名証明書を使用している場合、確認を無効化する必要があるかもしれません。これらの証明書を無効化するために、<filename>/etc/nova/api.paste.ini</filename> の <code>[filter:authtoken]</code> セクションに <code>insecure=False</code> を設定します。これらの設定は他のコンポーネントの証明書も無効化します。"
+
+#: ./doc/security-guide/ch024_authentication.xml218(title)
+msgid "Administrative users"
+msgstr "管理ユーザー"
+
+#: ./doc/security-guide/ch024_authentication.xml219(para)
+msgid ""
+"We recommend that admin users authenticate using Identity Service and an "
+"external authentication service that supports 2-factor authentication, such "
+"as a certificate. This reduces the risk from passwords that may be "
+"compromised. This recommendation is in compliance with NIST 800-53 IA-2(1) "
+"guidance in the use of multi factor authentication for network access to "
+"privileged accounts."
+msgstr "管理ユーザーは Identity や証明書のような 2 要素認証をサポートする外部認証サービスを使用して認証することを推奨します。これにより、パスワード推測によるリスクを減らすことができます。この推奨事項は特権アカウントへのネットワークアクセスに多要素認証を使用するという NIST 800-53 IA-2(1) ガイドに適合しています。"
+
+#: ./doc/security-guide/ch024_authentication.xml228(title)
+msgid "End users"
+msgstr "エンドユーザー"
+
+#: ./doc/security-guide/ch024_authentication.xml229(para)
+msgid ""
+"The Identity Service can directly provide end-user authentication, or can be"
+" configured to use external authentication methods to conform to an "
+"organization's security policies and requirements."
+msgstr "Identity は直接エンドユーザー認証を提供できます。または、組織のセキュリティポリシーや要求事項を確認するために外部認証方式を使用するよう設定できます。"
+
+#: ./doc/security-guide/ch024_authentication.xml236(title)
+msgid "Policies"
+msgstr "ポリシー"
+
+#: ./doc/security-guide/ch024_authentication.xml237(para)
+msgid ""
+"Each OpenStack service has a policy file in JSON format, called "
+"<filename>policy.json</filename>. The policy file specifies rules, and the "
+"rule that governs each resource. A resource could be API access, the ability"
+" to attach to a volume, or to fire up instances."
+msgstr "各 OpenStack サービスは <filename>policy.json</filename> という JSON 形式のポリシーファイルを持ちます。ポリシーファイルはルールを指定します。ルールは各リソースを決定します。リソースは API アクセスできます。ボリュームの接続やインスタンスの起動などです。"
+
+#: ./doc/security-guide/ch024_authentication.xml242(para)
+msgid ""
+"The policies can be updated by the cloud administrator to further control "
+"access to the various resources. The middleware could also be further "
+"customized. Note that your users must be assigned to groups/roles that you "
+"refer to in your policies."
+msgstr "さまざまなリソースへのアクセス権をさらに制御するために、クラウド管理者がポリシーを更新できます。ミドルウェアによりさらにカスタマイズすることもできます。そのポリシーを参照しているグループやロールにユーザーを割り当てる必要があることに注意してください。"
+
+#: ./doc/security-guide/ch024_authentication.xml247(para)
+msgid ""
+"Below is a snippet of the Block Storage service "
+"<filename>policy.json</filename> file."
+msgstr "以下は Block Storage Service の <filename>policy.json</filename> ファイルの抜粋です。"
+
+#: ./doc/security-guide/ch024_authentication.xml250(para)
+msgid ""
+"Note the <emphasis role=\"bold\">default</emphasis> rule specifies that the "
+"user must be either an admin or the owner of the volume. It essentially says"
+" only the owner of a volume or the admin may create/delete/update volumes. "
+"Certain other operations such as managing volume types are accessible only "
+"to admin users."
+msgstr "<emphasis role=\"bold\">デフォルト</emphasis>のルールは、ユーザーが管理者であるか、ボリュームの所有者である必要があることを指定しています。つまり、ボリュームの所有者と管理者のみがボリュームを作成、削除、更新できます。ボリューム形式の管理など、他の特定の操作は管理ユーザーのみがアクセス可能です。"
+
+#: ./doc/security-guide/ch024_authentication.xml258(title)
+msgid "Tokens"
+msgstr "トークン"
+
+#: ./doc/security-guide/ch024_authentication.xml259(para)
+msgid ""
+"Once a user is authenticated, a token is generated and used internally in "
+"OpenStack for authorization and access. The default token <emphasis "
+"role=\"bold\">lifespan</emphasis> is<emphasis role=\"bold\"> 24 "
+"hours</emphasis>. It is recommended that this value be set lower but caution"
+" needs to be taken as some internal services will need sufficient time to "
+"complete their work. The cloud may not provide services if tokens expire too"
+" early. An example of this would be the time needed by the Compute service "
+"to transfer a disk image onto the hypervisor for local caching."
+msgstr "ユーザーが認証されると、トークンが生成され、認可とアクセスのために OpenStack で内部的に使用されます。デフォルトのトークンの<emphasis role=\"bold\">有効期間</emphasis>は <emphasis role=\"bold\">24 時間</emphasis>です。この値はより短く設定することが推奨されますが、いくつかの内部サービスが処理を完了するために十分な時間が必要であるので注意する必要があります。トークンがすぐに失効すると、クラウドがサービスを提供できないかもしれません。これの例は、Compute Service がディスクイメージをハイパーバイザーのローカルキャッシュに転送するために必要な時間です。"
+
+#: ./doc/security-guide/ch024_authentication.xml269(para)
+msgid ""
+"The following example shows a PKI token. Note that, in practice, the token "
+"id value is about 3500 bytes. We shorten it in this example."
+msgstr "以下は PKI トークンの例です。実際は token id の値が約3500バイトであることに注意してください。この例では短くしています。"
+
+#: ./doc/security-guide/ch024_authentication.xml273(para)
+msgid ""
+"Note that the token is often passed within the structure of a larger context"
+" of an Identity Service response. These responses also provide a catalog of "
+"the various OpenStack services. Each service is listed with its name, access"
+" endpoints for internal, admin, and public access."
+msgstr "トークンは Identity の応答のより大きなコンテキスト構造の中で渡されることに注意してください。これらの応答はさまざまな OpenStack サービスのカタログも提供しています。各サービスはその名前と、内部、管理、パブリックなアクセス用のエンドポイントを一覧にします。"
+
+#: ./doc/security-guide/ch024_authentication.xml278(para)
+msgid ""
+"The Identity Service supports token revocation. This manifests as an API to "
+"revoke a token, to list revoked tokens and individual OpenStack services "
+"that cache tokens to query for the revoked tokens and remove them from their"
+" cache and append the same to their list of cached revoked tokens."
+msgstr "Identity はトークン失効をサポートします。これは、トークンを失効するため、失効済みトークンを一覧表示するために API として宣言されます。また、トークンをキャッシュしている各 OpenStack サービスが失効済みトークンを問い合わせるため、それらのキャッシュから失効済みトークンを削除するため、キャッシュした失効済みトークンの一覧に追加するためにもあります。"
+
+#: ./doc/security-guide/ch024_authentication.xml285(title)
+msgid "Future"
+msgstr "将来"
+
+#: ./doc/security-guide/ch024_authentication.xml286(para)
+msgid ""
+"Domains are high-level containers for projects, users and groups. As such, "
+"they can be used to centrally manage all keystone-based identity components."
+" With the introduction of account domains, server, storage and other "
+"resources can now be logically grouped into multiple projects (previously "
+"called tenants) which can themselves be grouped under a master account-like "
+"container. In addition, multiple users can be managed within an account "
+"domain and assigned roles that vary for each project."
+msgstr "ドメインはプロジェクト、ユーザー、グループの高いレベルでのコンテナーです。そのように、すべての keystone ベースの識別コンポーネントを一元的に管理するために使用されます。アカウントドメインを導入すると、サーバー、ストレージ、他のリソースは複数のプロジェクト (以前はテナントと呼ばれていました) の中で論理的にグループ化できます。これは、アカウントのようなマスターコンテナーの下でグループ化できます。さらに、複数のユーザーがアカウントドメインの中で管理でき、各プロジェクトで変化するロールを割り当てられます。"
+
+#: ./doc/security-guide/ch024_authentication.xml295(para)
+msgid ""
+"The Identity V3 API supports multiple domains. Users of different domains "
+"may be represented in different authentication backends and even have "
+"different attributes that must be mapped to a single set of roles and "
+"privileges, that are used in the policy definitions to access the various "
+"service resources."
+msgstr "Identity V3 API はマルチドメインをサポートします。異なるドメインのユーザーは、異なる認証バックエンドで表現され、単一セットのロールと権限にマッピングされる異なる属性を持ちます。これらはさまざまなサービスリソースにアクセスするために、ポリシー定義で使用されます。"
+
+#: ./doc/security-guide/ch024_authentication.xml301(para)
+msgid ""
+"Where a rule may specify access to only admin users and users belonging to "
+"the tenant, the mapping may be trivial. In other scenarios the cloud "
+"administrator may need to approve the mapping routines per tenant."
+msgstr "ルールにより管理ユーザーとテナントに所属するユーザーのみにアクセス権を設定されるかもしれないため、マッピングは些細なことかもしれません。他のシナリオの場合、クラウド管理者がテナントごとのマッピング作業を承認する必要があるかもしれません。"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch001_acknowledgements.xml12(None)
+#: ./doc/security-guide/ch001_acknowledgements.xml15(None)
+msgid ""
+"@@image: 'static/book-sprint-all-logos.png'; "
+"md5=f2d97c3130c32f31412f5af41ad72d39"
+msgstr "@@image: 'static/book-sprint-all-logos.png'; md5=f2d97c3130c32f31412f5af41ad72d39"
+
+#: ./doc/security-guide/ch001_acknowledgements.xml7(title)
+msgid "Acknowledgments"
+msgstr "謝辞"
+
+#: ./doc/security-guide/ch001_acknowledgements.xml8(para)
+msgid ""
+"The OpenStack Security Group would like to acknowledge contributions from "
+"the following organizations who were instrumental in making this book "
+"possible. These are:"
+msgstr "OpenStack Security Group は、このドキュメントの作成を支援していただいた以下の組織の貢献に感謝いたします。"
 
 #: ./doc/security-guide/ch059_case-studies-monitoring-logging.xml8(title)
 msgid "Case studies: monitoring and logging"
@@ -1926,22 +6508,6 @@ msgid ""
 " to generate actionable events."
 msgstr "このケーススタディでは、アリスとボブがパブリッククラウドとプライベートクラウドの中で監視とロギングを実行する方法を議論します。どちらのインスタンスでも、時間同期とログの集中保存が適切なアセスメントの実施と変則的な事のトラブル対応に極めて重要となります。単なるログの収集はそれほど有用ではなく、利用できるイベントを生成する為のロバストな監視システムを構築する必要があります。"
 
-#: ./doc/security-guide/ch059_case-studies-monitoring-logging.xml11(title)
-#: ./doc/security-guide/ch039_case-studies-messaging.xml11(title)
-#: ./doc/security-guide/ch066_case-studies-compliance.xml11(title)
-#: ./doc/security-guide/ch028_case-studies-identity-management.xml18(title)
-#: ./doc/security-guide/ch044_case-studies-database.xml11(title)
-#: ./doc/security-guide/ch009_case-studies.xml11(title)
-#: ./doc/security-guide/ch056_case-studies-instance-management.xml11(title)
-#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml11(title)
-#: ./doc/security-guide/ch015_case-studies-management.xml28(title)
-#: ./doc/security-guide/ch018_case-studies-pkissl.xml11(title)
-#: ./doc/security-guide/ch035_case-studies-networking.xml11(title)
-#: ./doc/security-guide/ch049_case-studies-tenant-data.xml17(title)
-#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml11(title)
-msgid "Alice's private cloud"
-msgstr "アリスのプライベートクラウド"
-
 #: ./doc/security-guide/ch059_case-studies-monitoring-logging.xml12(para)
 msgid ""
 "In the private cloud, Alice has a better understanding of the tenants "
@@ -1957,22 +6523,6 @@ msgid ""
 "over time."
 msgstr "プライベートクラウドでは、アリスはテナントの要件についてより深く理解しており、そのため監視やログ採取上で適切な全景や法令遵守を追加できます。アリスは重要なサービスとデータを認識し、少なくともこれらのサービス上でログが採取されるようにし、中央ログサーバにログが集約されるようにする必要があります。また、障害可能性の数を制限する為、相互関係・警告を実装する必要があります。相互関係と警告を実装するために、アリスはログデータを彼女の組織の既存の SIEM ツールに送信します。セキュリティ監視は継続プロセスであり、ネットワークトラフィック活動と使用量についてより深く理解する為に、アリスはユースケースと警告の定義を継続する必要があります。"
 
-#: ./doc/security-guide/ch059_case-studies-monitoring-logging.xml15(title)
-#: ./doc/security-guide/ch039_case-studies-messaging.xml15(title)
-#: ./doc/security-guide/ch066_case-studies-compliance.xml18(title)
-#: ./doc/security-guide/ch028_case-studies-identity-management.xml43(title)
-#: ./doc/security-guide/ch044_case-studies-database.xml15(title)
-#: ./doc/security-guide/ch009_case-studies.xml16(title)
-#: ./doc/security-guide/ch056_case-studies-instance-management.xml17(title)
-#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml33(title)
-#: ./doc/security-guide/ch015_case-studies-management.xml33(title)
-#: ./doc/security-guide/ch018_case-studies-pkissl.xml15(title)
-#: ./doc/security-guide/ch035_case-studies-networking.xml29(title)
-#: ./doc/security-guide/ch049_case-studies-tenant-data.xml50(title)
-#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml17(title)
-msgid "Bob's public cloud"
-msgstr "ボブのパブリッククラウド"
-
 #: ./doc/security-guide/ch059_case-studies-monitoring-logging.xml16(para)
 msgid ""
 "When it comes to logging, as a public cloud provider, Bob is interested in "
@@ -1988,432 +6538,428 @@ msgid ""
 "operational awareness to both customers and cloud administrators."
 msgstr "ログが作成された際、（パブリッククラウドプロバイダとして）法律順守と状況判断の両方で、ボブはログ採取に興味があります。これはつまり、ボブの顧客のコンプライアンス監査の為、彼らの代わりにタイムリーかつ関連のあるログ又はレポートを提供する為の彼の能力と同様、コンプライアンスはプロバイダとしてのボブが従うべきものであるという事です。それを念頭に置いて、ボブは彼のインスタンス、ノード、インフラデバイス全てで外部の良好と知られている時間デバイスを用いて時間同期を実行するよう設定しています。加えて、ボブのチームは彼の顧客用に、ボブの SIEM ツールからセルフサービスでログ取得を実行する為の Django ベースの Web アプリケーションを構築しています。ボブは、顧客とクラウド管理者の双方に運用判断を提供する為、ロバストな警告セットがあり、彼の CMDB インテグレーションを持つSIEM ツールも使用します。"
 
-#: ./doc/security-guide/bk_openstack-sec-guide.xml6(title)
-msgid "OpenStack Security Guide"
-msgstr "OpenStack セキュリティガイド"
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml8(title)
+msgid "Management interfaces"
+msgstr "管理インターフェース"
 
-#: ./doc/security-guide/bk_openstack-sec-guide.xml14(orgname)
-#: ./doc/security-guide/bk_openstack-sec-guide.xml19(holder)
-msgid "OpenStack Foundation"
-msgstr "OpenStack Foundation"
-
-#: ./doc/security-guide/bk_openstack-sec-guide.xml18(year)
-msgid "2013"
-msgstr "2013"
-
-#: ./doc/security-guide/bk_openstack-sec-guide.xml21(releaseinfo)
-msgid "current"
-msgstr "カレント"
-
-#: ./doc/security-guide/bk_openstack-sec-guide.xml22(productname)
-msgid "OpenStack"
-msgstr "OpenStack"
-
-#: ./doc/security-guide/bk_openstack-sec-guide.xml26(remark)
-msgid "Copyright details are filled in by the template."
-msgstr "Copyright details are filled in by the template."
-
-#: ./doc/security-guide/bk_openstack-sec-guide.xml31(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml9(para)
 msgid ""
-"This book provides best practices and conceptual information about securing "
-"an OpenStack cloud."
-msgstr "本書は OpenStack クラウドを安全にするためのベストプラクティスと基本的な考え方について書かれています。"
+"It is necessary for administrators to perform command and control over the "
+"cloud for various operational functions. It is important these command and "
+"control facilities are understood and secured."
+msgstr "管理者は、様々な運用機能に対してクラウドの管理統制を行う必要があります。また、これらの管理統制機能を理解して、セキュリティの確保を行うことが重要です。"
 
-#: ./doc/security-guide/bk_openstack-sec-guide.xml38(date)
-msgid "2013-12-02"
-msgstr "2013-12-02"
-
-#: ./doc/security-guide/bk_openstack-sec-guide.xml42(para)
-msgid "Chapter on Object Storage added."
-msgstr "Object Storage に関する章を追加しました。"
-
-#: ./doc/security-guide/bk_openstack-sec-guide.xml48(date)
-msgid "2013-10-17"
-msgstr "2013-10-17"
-
-#: ./doc/security-guide/bk_openstack-sec-guide.xml52(para)
-msgid "Havana release."
-msgstr "Havana リリース。"
-
-#: ./doc/security-guide/bk_openstack-sec-guide.xml58(date)
-msgid "2013-07-02"
-msgstr "2013-07-02"
-
-#: ./doc/security-guide/bk_openstack-sec-guide.xml62(para)
-msgid "Initial creation..."
-msgstr "初版作成..."
-
-#: ./doc/security-guide/ch065_privacy.xml7(title)
-msgid "Privacy"
-msgstr "プライバシー"
-
-#: ./doc/security-guide/ch065_privacy.xml8(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml13(para)
 msgid ""
-"Privacy is an increasingly important element of a compliance program. "
-"Businesses are being held to a higher standard by their customers, who have "
-"increased interest in understanding how their data is treated from a privacy"
-" perspective."
-msgstr "プライバシーはコンプライアンスプログラムの重要な要素になりつつあります。顧客はプライバシーの観点から、データがいかに扱われているか関心を高めており、データを扱う企業はより高い基準を期待されています。"
+"OpenStack provides several management interfaces for operators and tenants:"
+msgstr "OpenStack は、オペレーターやプロジェクト向けに複数の管理インターフェースを提供しています。"
 
-#: ./doc/security-guide/ch065_privacy.xml9(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml15(para)
+msgid "OpenStack dashboard (horizon)"
+msgstr "OpenStack dashboard (horizon)"
+
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml18(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml95(title)
+msgid "OpenStack API"
+msgstr "OpenStack API"
+
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml21(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml128(title)
+msgid "Secure shell (SSH)"
+msgstr "secure shell (SSH)"
+
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml24(para)
 msgid ""
-"An OpenStack deployment will likely need to demonstrate compliance with an "
-"organization’s Privacy Policy, with the U.S. – E.U. Safe Harbor framework, "
-"the ISO/IEC 29100:2011 privacy framework or with other privacy-specific "
-"guidelines. In the U.S. the AICPA has <link "
-"href=\"http://www.aicpa.org/interestareas/informationtechnology/resources/privacy/generallyacceptedprivacyprinciples/\">defined"
-" 10 privacy areas of focus</link>, OpenStack deployments within a commercial"
-" environment may desire to attest to some or all of these principles."
-msgstr "OpenStack環境では、組織のプライバシーポリシー、米国 - EU間のセーフハーバーフレームワーク、ISO/IEC 29100:2011 プライバシーフレームワークなど、プライバシー特化ガイドライン遵守の証明を求められることが多いです。米国ではAICPAが<link href=\"http://www.aicpa.org/interestareas/informationtechnology/resources/privacy/generallyacceptedprivacyprinciples/\">重視すべき10のプライバシー項目</link>を公表しており、ビジネス用途のOpenStack環境はそのうちのいくつか、もしくは全原則の立証を期待されます。"
+"OpenStack management utilities such as <systemitem class=\"service\">nova-"
+"manage</systemitem> and <systemitem class=\"service\">glance-"
+"manage</systemitem>"
+msgstr "<systemitem class=\"service\">nova-manage</systemitem>、<systemitem class=\"service\">glance-manage</systemitem> などの OpenStack 管理ユーティリティ"
 
-#: ./doc/security-guide/ch065_privacy.xml10(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml29(para)
+msgid "Out-of-band management interfaces, such as IPMI"
+msgstr "帯域外管理インターフェース (IPMI など)"
+
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml34(para)
 msgid ""
-"To aid OpenStack architects in the protection of personal data, it is "
-"recommended that OpenStack architects review the NIST publication 800-122, "
-"titled \"<emphasis>Guide to Protecting the Confidentiality of Personally "
-"Identifiable Information (PII)</emphasis>.\" This guide steps through the "
-"process of protecting:"
-msgstr "個人情報の保護に取り組むOpenStackアーキテクトを支援するため、OpenStackアーキテクトには、NIST刊行 800-122 \"<emphasis>Guide to Protecting the Confidentiality of Personally Identifiable Information (PII)</emphasis>.をおすすめします。このガイドは以下を保護するプロセスについて述べています。"
+"The OpenStack dashboard (horizon) provides administrators and tenants with a"
+" web-based graphical interface to provision and access cloud-based "
+"resources. The dashboard communicates with the back-end services through "
+"calls to the OpenStack API."
+msgstr "OpenStack dashboard (horizon) は、管理者やプロジェクトに対して、クラウドベースのリソースのプロビジョンやアクセスができるように  Web ベースのグラフィカルインターフェースを提供します。ダッシュボードは、OpenStack API に呼び出しを行うことでバックエンドサービスと対話します。"
 
-#: ./doc/security-guide/ch065_privacy.xml12(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml41(title)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml103(title)
+#: ./doc/security-guide/ch026_compute.xml22(title)
+#: ./doc/security-guide/ch026_compute.xml67(title)
+msgid "Capabilities"
+msgstr "機能"
+
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml43(para)
 msgid ""
-"\"<emphasis>any information about an individual maintained by an agency, "
-"including (1) any information that can be used to distinguish or trace an "
-"individual‘s identity, such as name, social security number, date and place "
-"of birth, mother‘s maiden name, or biometric records; and (2) any other "
-"information that is linked or linkable to an individual, such as medical, "
-"educational, financial, and employment information</emphasis>\""
-msgstr "\"<emphasis>政府機関が保有するあらゆる個人情報、(1)個人を特定、追跡しうるあらゆる情報、例えば氏名、社会保障番号、出生年月日、出生地、母の旧姓、生体情報など。および、(2)個人に結びつく、結びつけられるあらゆる情報、例えば医療、教育、金融、雇用情報など</emphasis>\""
+"As a cloud administrator, the dashboard provides an overall view of the size"
+" and state of your cloud. You can create users and tenants/projects, assign "
+"users to tenant/projects and set limits on the resources available for them."
+msgstr "クラウド管理者として、ダッシュボードはクラウドのサイズや状態の俯瞰図を確認できます。また、ユーザーやプロジェクト (テナント) の作成、プロジェクトへのユーザーの割り当て、ユーザーやプロジェクトで利用可能なリソースの制限設定が可能です。 "
 
-#: ./doc/security-guide/ch065_privacy.xml14(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml46(para)
 msgid ""
-"Comprehensive privacy management requires significant preparation, thought "
-"and investment. Additional complications are introduced when building global"
-" OpenStack clouds, for example navigating the differences between U.S. and "
-"more restrictive E.U. privacy laws. In addition, extra care needs to be "
-"taken when dealing with sensitive PII that may include information such as "
-"credit card numbers or medical records. This sensitive data is not only "
-"subject to privacy laws but also regulatory and governmental regulations. By"
-" deferring to established best practices, including those published by "
-"governments, a holistic privacy management policy may be created and "
-"practiced for OpenStack deployments."
-msgstr "包括的なプライバシー管理には、十分な準備、考慮と投資が必要です。また、グローバルなOpenStackクラウドの構築時には、さらなる複雑さに気づくでしょう。米国および、それより厳しいEUのプライバシー法令の違いが良い例です。加えて、クレジットカード番号や医療情報など、機密性の高い個人情報を扱う場合にはさらなる注意が必要です。これら機密性の高い情報はプライバシー法令だけでなく、監視当局や政府規制にも関連します。政府によって発行されたものなど、ベストプラクティスに従うことで、OpenStack環境向けの総合的なプライバシー管理ポリシーが確立、実践されていくでしょう。"
+"The dashboard provides tenant-users a self-service portal to provision their"
+" own resources within the limits set by administrators."
+msgstr "ダッシュボードでは、プロジェクト/ユーザーに対して、管理者が設定した制限値内で自身のリソースをプロビジョニングするためのセルフサービスポータルを提供します。"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml8(title)
-msgid "Networking services"
-msgstr "ネットワークサービス"
-
-#: ./doc/security-guide/ch032_networking-best-practices.xml9(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml49(para)
 msgid ""
-"In the initial architectural phases of designing your OpenStack Network "
-"infrastructure it is important to ensure appropriate expertise is available "
-"to assist with the design of the physical networking infrastructure, to "
-"identify proper security controls and auditing mechanisms."
-msgstr "あなたの OpenStack ネットワークインフラデザインの概要設計段階では、適切なセキュリティ管理・監査機構を確認する為、物理ネットワークインフラ設計で支援する適切な専門技術が間違いなく利用できる事は重要です。"
+"The dashboard provides GUI support for routers and load-balancers. For "
+"example, the dashboard now implements all of the main Networking features."
+msgstr "また、ダッシュボードではルーターやロードバランサーにも GUI 対応しています。例えば、ダッシュボードは主な Networking 機能をすべて実装するようになりました。"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml10(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml52(para)
 msgid ""
-"OpenStack Networking adds a layer of virtualized network services - giving "
-"tenants the capability to architect their own, virtual networks. These "
-"virtualized services are not as currently as mature as their traditional "
-"networking counterparts. It is important to be aware of the current state of"
-" these virtualized services and what controls may need to be implemented at "
-"the virtualized and traditional network boundary."
-msgstr "OpenStack Networking は（テナントに自身の仮想ネットワークを設計する為の機能を提供する）仮想ネットワークサービスのレイヤを追加します。これらの仮想化サービスは、現時点で従来のネットワークコンポーネントのように成熟していません。これらの仮想化技術の現状と、仮想ネットワークと従来のネットワーク境界でどのコントロールを実装する必要があるだろうというを知っておく事は重要です。"
+"It is an extensible <glossterm>Django</glossterm> web application that "
+"allows easy plug-in of third-party products and services, such as billing, "
+"monitoring, and additional management tools."
+msgstr "Hirozon は拡張可能な <glossterm>Django</glossterm> Web アプリケーションで、請求、監視、追加管理ツールなど、サードパーティーの製品やサービスを簡単にプラグインできるようにします。"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml12(title)
-msgid "L2 isolation using VLANs and tunneling"
-msgstr "VLAN とトンネリングを使用した L2 分断"
-
-#: ./doc/security-guide/ch032_networking-best-practices.xml13(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml55(para)
 msgid ""
-"OpenStack networking can employ two different mechanisms for traffic "
-"segregation on a per tenant/network combination: VLANs (IEEE 802.1Q tagging)"
-" or L2 tunnels using GRE encapsulation. Which method you choose for traffic "
-"segregation and isolation is determined by the scope and scale of your "
-"OpenStack deployment."
-msgstr "OpenStack Networking はテナント／ネットワークの組合せ単位で通信を分断する為の、 VLANs (IEEE 802.1Q タギング) 又は GRE カプセル化を使用した L2 トンネルという２つの異なる機構を使用する事が出来ます。通信の分断と独立用にあなたが選択する方式は、あなたの OpenStack デプロイの範囲と規模に依存します。"
+"The dashboard can also be branded for service providers and other commercial"
+" vendors."
+msgstr "また、ダッシュボードはサービスプロバイダーや他の商業ベンダー向けにブランディングすることも可能です。"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml15(title)
-msgid "VLANs"
-msgstr "VLAN"
-
-#: ./doc/security-guide/ch032_networking-best-practices.xml16(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml62(para)
 msgid ""
-"VLANs are realized as packets on a specific physical network containing IEEE"
-" 802.1Q headers with a specific VLAN ID (VID) field value. VLAN networks "
-"sharing the same physical network are isolated from each other at L2, and "
-"can even have overlapping IP address spaces. Each distinct physical network "
-"supporting VLAN networks is treated as a separate VLAN trunk, with a "
-"distinct space of VID values. Valid VID values are 1 through 4094."
-msgstr "VLAN は特別な VLAN ID (VID) フィールド値を持つ IEEE 802.1Q ヘッダを含む特別な物理ネットワーク上のパケットを実現します。同じ物理ネットワークを共有する VLAN ネットワーク群は、L2 において相互から独立しており、重複する IP アドレス空間を持つ事すら可能です。VLAN ネットワークに対応した各個別の物理ネットワークは、独自の VID 値を持つ独立した VLAN トランクとして扱われます。有効な VID 値は1～4094です。"
+"The dashboard requires cookies and JavaScript to be enabled in the web "
+"browser."
+msgstr "ダッシュボードは Web ブラウザーのクッキーと JavaScript を有効にする必要があります。"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml17(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml65(para)
 msgid ""
-"VLAN configuration complexity depends on your OpenStack design requirements."
-" In order to allow OpenStack Networking to efficiently use VLANs, you must "
-"allocate a VLAN range (one for each tenant) and turn each compute node "
-"physical switch port into a VLAN trunk port."
-msgstr "VLAN 設定の複雑さはあなたの OpenStack 設計要件に依存します。OpenStack Networking がVLAN を効率良く使用できるようにする為に、VLAN 範囲を (各テナントに１つ) 割り当てて、各 compute ノードの物理スイッチポートを VLAN トランクポートに変更する必要があります。"
+"The web server that hosts dashboard should be configured for SSL to ensure "
+"data is encrypted."
+msgstr "ダッシュボードをホストする Web サーバーは、データの暗号化が確実に行われるように SSL の設定をしてください。"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml19(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml68(para)
 msgid ""
-"NOTE: If you intend for your network to support more than 4094 tenants VLAN "
-"is probably not the correct option for you as multiple 'hacks' are required "
-"to extend the VLAN tags to more than 4094 tenants."
-msgstr "注意：あなたのネットワークを4095 以上のテナントに対応するようにしたい場合、VLAN はあなたにとって多分正しい選択肢ではありません。なぜなら、4095 以上に VLAN タグを拡張する為の複数の「改造」が必要だからです。"
+"Both the horizon web service and the OpenStack API it uses to communicate "
+"with the back-end are susceptible to web attack vectors such as denial of "
+"service and must be monitored."
+msgstr "バックエンドとの対話に使用する horizon Web サービスおよび OpenStack API はいずれも、サービス妨害 (DoS) などの Web 攻撃ベクトルからの影響を受けるため、必ず監視が必要です。"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml23(title)
-msgid "L2 tunneling"
-msgstr "L2 トンネリング"
-
-#: ./doc/security-guide/ch032_networking-best-practices.xml24(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml71(para)
 msgid ""
-"Network tunneling encapsulates each tenant/network combination with a unique"
-" \"tunnel-id\" that is used to identify the network traffic belonging to "
-"that combination. The tenant's L2 network connectivity is independent of "
-"physical locality or underlying network design. By encapsulating traffic "
-"inside IP packets, that traffic can cross Layer-3 boundaries, removing the "
-"need for preconfigured VLANs and VLAN trunking. Tunneling adds a layer of "
-"obfuscation to network data traffic, reducing the visibility of individual "
-"tenant traffic from a monitoring point of view."
-msgstr "Network tunneling encapsulates each tenant/network combination with a unique \"tunnel-id\" \nネットワークトンネリングは、固有の「トンネルID」を用いてテナント／ネットワークの各組合せをカプセル化します。これは、上記の組合せに属するネットワーク通信を独立させる為に使用されます。テナントの L2 ネットワーク接続は、物理的配置や下層のネットワーク設計から独立しています。IP パケット内で通信をカプセル化する事により、通信はレイヤ３境界を越える事ができ、VLAN や VLAN とランキングの事前設定の必要が無くなります。トンネリングはネットワークのデータ通信に不明瞭なレイヤを追加し、監視の観点で個々のテナント通信の可視性を低下させます。"
+"It is now possible (though there are numerous deployment/security "
+"implications) to upload an image file directly from a user’s hard disk to "
+"OpenStack Image Service through the dashboard. For multi-gigabyte images it "
+"is still strongly recommended that the upload be done using the "
+"<placeholder-1/> CLI."
+msgstr "(デプロイメント/セキュリティ関連の問題は多数ありますが) ダッシュボードでユーザーのハードディスクから OpenStack Image Service に直接イメージファイルをアップロードすることができるようになりました。サイズが GB レベルのイメージについては、<placeholder-1/> CLI を使用してイメージをアップロードするよう強く推奨しています。"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml25(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml81(para)
 msgid ""
-"OpenStack Networking currently only supports GRE encapsulation with planned "
-"future support of VXLAN due in the Havana release."
-msgstr "OpenStack Networking は現在 GRE カプセル化のみサポートしており、Havana リリースで VXLAN をサポートする計画があります。"
+"Create and manage security groups through dashboard. The security groups "
+"allows L3-L4 packet filtering for security policies to protect virtual "
+"machines."
+msgstr "ダッシュボードからセキュリティグループを作成・管理します。セキュリティグループにより、セキュリティポリシーに関する L3-L4 パケットをフィルダリングして仮想マシンの保護が可能になります。"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml26(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml91(citetitle)
+msgid "Grizzly Release Notes"
+msgstr "Grizzly リリースノート"
+
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml96(para)
 msgid ""
-"The choice of technology to provide L2 isolation is dependent upon the scope"
-" and size of tenant networks that will be created in your deployment. If "
-"your environment has limited VLAN ID availability or will have a large "
-"number of L2 networks, it is our recommendation that you utilize tunneling."
-msgstr "L2 分断を提供する技術の選択は、あなたのデプロイで作成される予定のテナントネットワークの範囲とサイズに依存します。あなたの環境が VLAN ID の利用で制限がある場合や、大多数の L2 ネットワークが見込まれる場合、トンネリングの使用を推奨します。"
+"The OpenStack API is a RESTful web service endpoint to access, provision and"
+" automate cloud-based resources. Operators and users typically access the "
+"API through command-line utilities (for example, <placeholder-1/> or "
+"<placeholder-2/>), language-specific libraries, or third-party tools."
+msgstr "OpenStack API はクラウドベースのリソースのアクセス、プロビジョニング、自動化を行う RESTful Web サービスのエンドポイントです。オペレーターやユーザーは通常、コマンドラインユーティリティ (<placeholder-1/>、<placeholder-2/> など)、言語固有のライブラリ、またはサードパーティのツールで API にアクセスします。"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml30(title)
-msgid "Network services"
-msgstr "ネットワークサービス"
-
-#: ./doc/security-guide/ch032_networking-best-practices.xml31(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml105(para)
 msgid ""
-"The choice of tenant network isolation affects how the network security and "
-"control boundary is implemented for tenant services. The following "
-"additional network services are either available or currently under "
-"development to enhance the security posture of the OpenStack network "
-"architecture."
-msgstr "テナントネットワーク分断の選択はネットワークセキュリティと制御境界をどのように実装するかに影響します。\n以下の追加ネットワークサービスは利用可能か、OpenStack ネットワークアーキテクチャのセキュリティポーズを拡張する為の開発中かのいずれかです。"
+"To the cloud administrator, the API provides an overall view of the size and"
+" state of the cloud deployment and allows the creation of users, "
+"tenants/projects, assigning users to tenants/projects, and specifying "
+"resource quotas on a per tenant/project basis."
+msgstr "API はクラウド管理者がクラウドデプロイメントのサイズや状態の概要を把握できるようにするだけでなく、ユーザー、プロジェクトの作成、プロジェクトへのユーザーの割り当て、プロジェクトベースのリソースクォータの指定などができるようにします。"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml33(title)
-msgid "Access control lists"
-msgstr "アクセス制御リスト"
-
-#: ./doc/security-guide/ch032_networking-best-practices.xml34(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml112(para)
 msgid ""
-"OpenStack Compute supports tenant network traffic access controls directly "
-"when deployed with the legacy nova-network service, or may defer access "
-"control to the OpenStack Networking service."
-msgstr "OpenStack Compute は、旧式の nova-network サービスでデプロイする場合、テナントネットワーク通信のアクセス制御を直接サポートします。又は、OpenStack Networking サービスにアクセス制御を任せる事も出来ます。"
+"The API provides a tenant interface for provisioning, managing, and "
+"accessing their resources."
+msgstr "API はリソースのプロビジョニング、管理、アクセスに使用するプロジェクトインターフェースを提供します。"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml35(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml119(para)
 msgid ""
-"Note, legacy nova-network security groups are applied to all virtual "
-"interface ports on an instance using IPTables."
-msgstr "注：旧式の nova-network セキュリティグループは、Iptables を使用してインスタンス上の全ての仮想インターフェースポートに適用されます。"
+"The API service should be configured for SSL to ensure data is encrypted."
+msgstr "API サービスはデータが確実に暗号化されるように SSL の設定が必要です。"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml36(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml122(para)
 msgid ""
-"Security groups allow administrators and tenants the ability to specify the "
-"type of traffic, and direction (ingress/egress) that is allowed to pass "
-"through a virtual interface port. Security groups rules are stateful L2-L4 "
-"traffic filters."
-msgstr "セキュリティグループでは、管理者とテナントが仮想インターフェースポート通過を許可する通信のタイプと方向（内向き／外向き）を指定できるようになっています。"
+"As a web service, OpenStack API is susceptible to familiar web site attack "
+"vectors such as denial of service attacks."
+msgstr "Web サービスとして OpenStack API は、サービス妨害 (DoS) 攻撃など、よく知られている Web サイト攻撃ベクトルからの影響を受けます。"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml37(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml129(para)
 msgid ""
-"It is our recommendation that you enable security groups through OpenStack "
-"Networking."
-msgstr "OpenStack Networking 経由でセキュリティグループを有効にする事をお勧めします。"
+"It has become industry practice to use secure shell (SSH) access for the "
+"management of Linux and Unix systems. SSH uses secure cryptographic "
+"primitives for communication. With the scope and importance of SSH in "
+"typical OpenStack deployments, it is important to understand best practices "
+"for deploying SSH."
+msgstr "Linux や Unix システムの管理にはセキュアシェル (SSH) を使用するのが業界の慣習となっています。SSH は通信にセキュアな暗号化機能を使用します。一般的な OpenStack デプロイメントでの SSH の範囲や重要性において、SSH デプロイメントのベストプラクティスを把握することが重要です。"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml41(title)
-msgid "L3 routing and NAT"
-msgstr "L3 ルーティングおよび NAT"
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml131(title)
+msgid "Host key fingerprints"
+msgstr "ホストキーのフィンガープリント"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml42(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml132(para)
 msgid ""
-"OpenStack Networking routers can connect multiple L2 networks, and can also "
-"provide a <emphasis>gateway</emphasis> that connects one or more private L2 "
-"networks to a shared <emphasis>external</emphasis> network, such as a public"
-" network for access to the Internet."
-msgstr "OpenStack Networking のルータは複数の L2 ネットワークを接続でき、１つ以上のプライベート L2 ネットワークを共有<emphasis>外部</emphasis>ネットワーク（インターネットアクセス用のパブリックネットワーク等）に接続する<emphasis>ゲートウェイ</emphasis>を提供する事も出来ます。"
+"Often overlooked is the need for key management for SSH hosts. As most or "
+"all hosts in an OpenStack deployment will provide an SSH service, it is "
+"important to have confidence in connections to these hosts. It cannot be "
+"understated that failing to provide a reasonably secure and accessible "
+"method to verify SSH host key fingerprints is ripe for abuse and "
+"exploitation."
+msgstr "頻繁に見逃されるのが SSH ホストのキー管理の必要性です。OpenStack デプロイメントホストのすべてまたは多くが SSH サービスを提供します。このようなホストへの接続の信頼性を確保することが重要です。SSH ホストキーのフィンガープリントの検証に関して比較的セキュアでアクセス可能なメソッドを提供できないと、悪用やエクスプロイトの温床となるといっても過言ではありません。"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml43(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml133(para)
 msgid ""
-"The L3 router provides basic Network Address Translation (NAT) capabilities "
-"on <emphasis>gateway</emphasis> ports that uplink the router to external "
-"networks. This router SNATs (Static NAT) all traffic by default, and "
-"supports floating IPs, which creates a static one-to-one mapping from a "
-"public IP on the external network to a private IP on one of the other "
-"subnets attached to the router."
-msgstr "L3 ルータは、外部ネットワークへのルータに接続する<emphasis>ゲートウェイ</emphasis>ポート上の基本的なネットワークアドレス変換 (NAT) 機能を提供します。このルータはデフォルトで全てのネットワークの SNAT (静的 NAT) を行います。これは、外部ネットワーク上のパブリック IP アドレスから、ルータにアタッチされた他の１サブネットのプライベート IP アドレスへ変換する静的な１対１マッピングを作成します。"
+"All SSH daemons have private host keys and, upon connection, offer a host "
+"key fingerprint. This host key fingerprint is the hash of an unsigned public"
+" key. It is important these host key fingerprints are known in advance of "
+"making SSH connections to those hosts. Verification of host key fingerprints"
+" is instrumental in detecting man-in-the-middle attacks."
+msgstr "SSH デーモンにはすべてプライベートのホストキーがあり、接続するとホストキーのフィンガープリントが提供されます。このホストキーのフィンガープリントは未署名のパブリックキーのハッシュです。これらのホストに SSH  接続する前に、ホストキーのフィンガープリントを把握しておくことが重要です。ホストキーのフィンガープリントの検証は中間者攻撃の検出に役立ちます。"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml44(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml134(para)
 msgid ""
-"It is our recommendation to leverage per tenant L3 routing and Floating IPs "
-"for more granular connectivity of tenant VMs."
-msgstr "テナント VM のより粒度の細かいテナント L3 ルーティングとフローティング IP 単位で設定する事をお勧めします。"
+"Typically, when an SSH daemon is installed, host keys will be generated. It "
+"is necessary that the hosts have sufficient entropy during host key "
+"generation. Insufficient entropy during host key generation can result in "
+"the possibility to eavesdrop on SSH sessions."
+msgstr "通常、SSH デーモンがインストールされると、ホストキーが生成されます。ホストキーの生成時に、ホストには十分なエントロピーが必要になります。ホストキーの生成時にエントロピーが十分にないと、SSH セッションの傍受が発生してしまう可能性があります。"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml47(title)
-msgid "Quality of Service (QoS)"
-msgstr "サービス品質(QoS)"
-
-#: ./doc/security-guide/ch032_networking-best-practices.xml48(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml135(para)
 msgid ""
-"The ability to set QoS on the virtual interface ports of tenant instances is"
-" a current deficiency for OpenStack Networking. The application of QoS for "
-"traffic shaping and rate-limiting at the physical network edge device is "
-"insufficient due to the dynamic nature of workloads in an OpenStack "
-"deployment and can not be leveraged in the traditional way. QoS-as-a-Service"
-" (QoSaaS) is currently in development for the OpenStack Networking Havana "
-"release as an experimental feature. QoSaaS is planning to provide the "
-"following services:"
-msgstr "現在の OpenStack Networking にはテナントインスタンスの仮想インターフェースポート上の QoS 設定機能が欠如しています。物理ネットワークエッジデバイスにおけるトラフィックシェーピングやレートリミットの為の QoS 活用は、OpenStack デプロイ中のワークロードの動的な性質の為に実装されておらず、従来の方法では設定できません。QoS-as-a-Service (QoSaaS) は実験的な機能として現在 OpenStack Networking Havana リリース用に開発中です。QoSaaS は以下のサービスを提供する計画です。"
+"Once the SSH host key is generated, the host key fingerprint should be "
+"stored in a secure and queriable location. One particularly convenient "
+"solution is DNS using SSHFP resource records as defined in RFC-4255. For "
+"this to be secure, it is necessary that DNSSEC be deployed."
+msgstr "SSH ホストキーが生成されると、ホストキーのフィンガープリントはセキュアでクエリ可能な場所に保存されるはずです。特に有用なソリューションは、RFC-4255 で定義されているように SSHFP リソースレコードを使用した DNS です。これをセキュアにするには、DNSSEC のデプロイメントが必要になります。"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml50(para)
-msgid "Traffic shaping through DSCP markings"
-msgstr "DSCP マーキングによるトラフィックシェーピング"
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml139(title)
+msgid "Management utilities"
+msgstr "管理ユーティリティ"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml53(para)
-msgid "Rate-limiting on a per port/network/tenant basis."
-msgstr "ポート・ネットワーク・テナント単位のレートリミット"
-
-#: ./doc/security-guide/ch032_networking-best-practices.xml56(para)
-msgid "Port mirroring (through open source or third-party plug-ins)"
-msgstr "ポートミラーリング (オープンソースのサードパーティ製プラグイン使用)"
-
-#: ./doc/security-guide/ch032_networking-best-practices.xml59(para)
-msgid "Flow analysis (through open source or third-party plug-ins)"
-msgstr "フロー分析 (オープンソースのサードパーティプラグイン使用)"
-
-#: ./doc/security-guide/ch032_networking-best-practices.xml62(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml140(para)
 msgid ""
-"Tenant traffic port mirroring or Network Flow monitoring is currently not an"
-" exposed feature in OpenStack Networking. There are third-party plug-in "
-"extensions that do provide Port Mirroring on a per port/network/tenant "
-"basis. If Open vSwitch is used on the networking hypervisor, it is possible "
-"to enable sFlow and port mirroring, however it will require some operational"
-" effort to implement."
-msgstr "テナントトラフィックポートミラーリング又はNetwork Flow モニタリングは現在、OpenStack Networking の機能として公開されていません。ポート／ネットワーク／テナント単位でポートミラーリングを行うサードパーティ製のプラグイン拡張があります。ハイパーバイザー上で Open vSwitch を使用する場合、sFlow とポートミラーリングを有効にできますが、実装には幾つかの運用操作が必要になるでしょう。"
+"The OpenStack Management Utilities are open-source Python command-line "
+"clients that make API calls. There is a client for each OpenStack service "
+"(for example, <systemitem class=\"service\">nova</systemitem>, <systemitem "
+"class=\"service\">glance</systemitem>). In addition to the standard CLI "
+"client, most of the services have a management command-line utility which "
+"makes direct calls to the database. These dedicated management utilities are"
+" slowly being deprecated."
+msgstr "OpenStack 管理ユーテリティは、API 呼び出しを行う、オープンソースの Python のコマンドラインクライアントです。OpenStack サービス (<systemitem class=\"service\">nova</systemitem>、<systemitem class=\"service\">glance</systemitem> など) 毎にクライアントがあります。標準の CLI クライアントに加え、サービスの多くには管理コマンドラインがあり、データベースへ直接呼び出しを行います。これらの専用の管理ユーテリティは徐々に廃止予定となっています。"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml65(title)
-msgid "Load balancing"
-msgstr "負荷分散"
-
-#: ./doc/security-guide/ch032_networking-best-practices.xml66(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml152(para)
 msgid ""
-"An experimental feature in the Grizzly release of OpenStack Networking is "
-"Load-Balancer-as-a-service (LBaaS). The LBaaS API gives early adopters and "
-"vendors a chance to build implementations of the technology. The reference "
-"implementation however, is still experimental and should likely not be run "
-"in a production environment. The current reference implementation is based "
-"on HA-Proxy. There are third-party plug-ins in development for extensions in"
-" OpenStack Networking to provide extensive L4-L7 functionality for virtual "
-"interface ports."
-msgstr "OpenStack Networking の Grizzly リリースにおける実験的機能の１つが Load-Balancer-as-a-service (LBaaS) です。LBaaS API は、アーリーアダプターやベンダーに LBaaS 技術の実装を行う機会を提供します。しかしながら、リファレンス実装は未だ実験段階で、商用環境で使用されているという話は聞きません。現在のリファレンス実装は HAProxy をベースにしています。仮想インターフェースポート用の拡張可能な L4-L7 機能を提供する OpenStack Networking 中の拡張用に開発中のサードパーティプラグインがあります。"
+"The dedicated management utilities (*-manage) in some cases use the direct "
+"database connection."
+msgstr "場合によっては専用の管理ユーテリティ (*-manage) は直接データベースへの接続を使用することがあります。"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml69(title)
-msgid "Firewalls"
-msgstr "ファイアウォール"
-
-#: ./doc/security-guide/ch032_networking-best-practices.xml70(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml155(para)
 msgid ""
-"FW-as-a-Service (FWaaS) is currently in development for the OpenStack "
-"Networking Havana release as an experimental feature. FWaaS will address the"
-" need to manage and leverage the rich set of security features provided by "
-"typical firewall products which are typically far more comprehensive than "
-"what is currently provided by security groups. There are third-party plug-"
-"ins in development for extensions in OpenStack Networking to support this."
-msgstr "FW-as-a-Service (FWaaS) は実験的機能として OpenStack Networking Havana リリースに向けて現在開発中です。FWaaS は現在セキュリティグループにより提供されるものより一般にはかなり広い典型的なファイアウォール製品により提供される豊富なセキュリティ機能を管理・設定する為に呼ばれます。現在、FWaaS をサポートするために、OpenStack ネットワーキングの拡張用サードパーティプラグインが開発されているところです。"
+"Ensure that the .rc file which has your credential information is secured."
+msgstr "認証情報が含まれている .rc ファイルのセキュリティが確保されているようにします。"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml71(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml161(para)
 msgid ""
-"It is critical during the design of an OpenStack Networking infrastructure "
-"to understand the current features and limitations of network services that "
-"are available. Understanding where the boundaries of your virtual and "
-"physical networks will help you add the required security controls in your "
-"environment."
-msgstr "利用可能なネットワークサービスの現在の機能と制限を理解する事は OpenStack Networking の設計上極めて重要です。仮想／物理ネットワークの境界がどこかを理解する事は、あなたの環境で要求されたセキュリティコントロールを追加する際の助けになるでしょう。"
+"<citetitle>OpenStack End User Guide</citetitle> section <link "
+"href=\"http://docs.openstack.org/user-"
+"guide/content/section_cli_overview.html\">command-line clients "
+"overview</link>"
+msgstr "<citetitle>OpenStack エンドユーザーガイド</citetitle> の項: <link href=\"http://docs.openstack.org/user-guide/content/section_cli_overview.html\">コマンドラインクライアントの概要</link>"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml75(title)
-msgid "Network services extensions"
-msgstr "ネットワークサービス拡張"
-
-#: ./doc/security-guide/ch032_networking-best-practices.xml76(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml162(para)
 msgid ""
-"Here is a list of known plug-ins provided by the open source community or by"
-" SDN companies that work with OpenStack Networking:"
-msgstr "以下はオープンソースコミュニティ又はSDN企業によって提供された、 OpenStack Networking で動作する既知のプラグインの一覧です。"
+"<citetitle>OpenStack End User Guide</citetitle> section <link "
+"href=\"http://docs.openstack.org/user-"
+"guide/content/cli_openrc.html\">Download and source the OpenStack RC "
+"file</link>"
+msgstr "<citetitle>OpenStack エンドユーザーガイド</citetitle> の項 <link href=\"http://docs.openstack.org/user-guide/content/cli_openrc.html\">OpenStack RC ファイルのダウンロードとソース</link>"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml77(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml166(title)
+msgid "Out-of-band management interface"
+msgstr "帯域外管理インターフェース"
+
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml167(para)
 msgid ""
-"Big Switch Controller plug-in, Brocade neutron plug-in Brocade neutron plug-"
-"in, Cisco UCS/Nexus plug-in, Cloudbase Hyper-V plug-in, Extreme Networks "
-"plug-in, Juniper Networks neutron plug-in, Linux Bridge plug-in, Mellanox "
-"neutron plug-in, MidoNet plug-in, NEC OpenFlow plug-in, Open vSwitch plug-"
-"in, PLUMgrid plug-in, Ruijie Networks plug-in, Ryu OpenFlow Controller plug-"
-"in, VMware NSX plug-in."
-msgstr "Big Switch Controller プラグイン、Brocade neutron プラグイン、Brocade neutron プラグイン、Cisco UCS/Nexus プラグイン、Cloudbase Hyper-V プラグイン、Extreme Networks プラグイン、Juniper Networks neutron プラグイン、Linux Bridge プラグイン、Mellanox neutron プラグイン、MidoNet プラグイン、NEC OpenFlow プラグイン、Open vSwitch プラグイン、PLUMgrid プラグイン、Ruijie Networks プラグイン、Ryu OpenFlow Controller プラグイン、VMware NSX プラグイン。"
+"OpenStack management relies on out-of-band management interfaces such as the"
+" IPMI protocol to access into nodes running OpenStack components. IPMI is a "
+"very popular specification to remotely manage, diagnose, and reboot servers "
+"whether the operating system is running or the system has crashed."
+msgstr "OpenStack コンポーネントを実行するノードにアクセスする場合、OpenStack の管理は IPMI プロトコルなどのアウトオブバンド管理インターフェースに依存します。IPMI は非常に有名な仕様で、オペレーティングシステムが実行中である場合やシステムがクラッシュした場合でもリモートでのサーバー管理、診断、リブートを行えます。"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml86(title)
-msgid "Networking services limitations"
-msgstr "Networking サービスの制限事項"
-
-#: ./doc/security-guide/ch032_networking-best-practices.xml87(para)
-msgid "OpenStack Networking has the following known limitations:"
-msgstr "OpenStack Networking は以下の制限があります。"
-
-#: ./doc/security-guide/ch032_networking-best-practices.xml90(term)
-msgid "Overlapping IP addresses"
-msgstr "IP アドレスの重複"
-
-#: ./doc/security-guide/ch032_networking-best-practices.xml92(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml176(para)
 msgid ""
-"If nodes that run either <systemitem "
-"class=\"service\">neutron-l3-agent</systemitem> or <systemitem "
-"class=\"service\">neutron-dhcp-agent</systemitem> use overlapping IP "
-"addresses, those nodes must use Linux network namespaces. By default, the "
-"DHCP and L3 agents use Linux network namespaces. However, if the host does "
-"not support these namespaces, run the DHCP and L3 agents on different hosts."
-msgstr "<systemitem class=\"service\">neutron-l3-agent</systemitem> か <systemitem class=\"service\">neutron-dhcp-agent</systemitem> のいずれかを実行するノードが重複した IP アドレスを使用する場合、これらのノード群は Linux のネットワークネームスペースを使用する必要があります。デフォルトでは、DHCP と L3 エージェントは Linux ネットワークネームスペースを使用しています。しかしながら、ホストがこのネームスペースをサポートしていない場合、DHCP と L3 エージェントは異なるホストで実行して下さい。"
+"Use strong passwords and safeguard them, or use client-side SSL "
+"authentication."
+msgstr "強力なパスワードを使用してセーフガードするか、クライアント側の SSL 認証を使用してください。"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml102(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml179(para)
 msgid ""
-"If network namespace support is not present, a further limitation of the L3 "
-"agent is that only a single logical router is supported."
-msgstr "ネットワークネームスペースサポートがない場合、L3エージェントでは追加の制限事項として単一の論理ルータのみサポートされます。"
+"Ensure that the network interfaces are on their own private(management or a "
+"separate) network. Segregate management domains with firewalls or other "
+"network gear."
+msgstr "ネットワークインターフェースはプライベート  (管理または個別) ネットワークに設定されていることを確認します。管理ドメインはファイアウォールか他のネットワーク機器で分離してください。"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml109(term)
-msgid "Multi-host DHCP-agent"
-msgstr "マルチホスト DHCP エージェント"
-
-#: ./doc/security-guide/ch032_networking-best-practices.xml111(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml182(para)
 msgid ""
-"OpenStack Networking supports multiple L3 and DHCP agents with load "
-"balancing. However, tight coupling of the location of the virtual machine is"
-" not supported."
-msgstr "OpenStack Networking は複数の L3 エージェントと DHCP エージェントによる負荷分散をサポートしています。しかしながら、（訳注：nova-network がサポートしていた）仮想マシンとの配置上の強い紐付けはサポートされていません。"
+"If you use a web interface to interact with the "
+"<glossterm>BMC</glossterm>/IPMI, always use the SSL interface, such as https"
+" or port 443. This SSL interface should <emphasis "
+"role=\"bold\">NOT</emphasis> use self-signed certificates, as is often "
+"default, but should have trusted certificates using the correctly defined "
+"fully qualified domain names (FQDNs)."
+msgstr "Web インターフェースを使用して <glossterm>BMC</glossterm>/IPMI と対話する場合、常に SSL インターフェースを使用するようにしてください (例: https またはポート 443)。この SSL インターフェースは自己署名証明書を使用<emphasis role=\"bold\">しない</emphasis>ようにしてください。通常、これがデフォルトとなっていますが、正しく定義された完全修飾ドメイン名 (FQDN) を使用して信頼済みの証明書を使用するようにしてください。"
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml119(term)
-msgid "No IPv6 support for L3 agents"
-msgstr "L3 エージェントの IPv6 未対応"
-
-#: ./doc/security-guide/ch032_networking-best-practices.xml121(para)
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml191(para)
 msgid ""
-"The neutron-l3-agent, used by many plug-ins to implement L3 forwarding, "
-"supports only IPv4 forwarding."
-msgstr "neutron-l3-agent （L3 転送の実装用に多くのプラグインが使用）は IPv4 転送のみサポートしています。"
+"Monitor the traffic on the management network. The anomalies might be easier"
+" to track than on the busier compute nodes."
+msgstr "管理ネットワークのトラフィックを監視します。トラフィックの多いコンピュートノードよりも例外のトラッキングが簡単になる場合があります。"
+
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml196(para)
+msgid ""
+"Out of band management interfaces also often include graphical machine "
+"console access. It is often possible, although not necessarily default, that"
+" these interfaces are encrypted. Consult with your system software "
+"documentation for encrypting these interfaces."
+msgstr "また、アウトオブバンド管理インターフェースはグラフィカルのコンソールアクセスが可能な場合が多くあります。デフォルトではない可能性もありますが、これらのインターフェースは暗号化されていることがあります。これらのインターフェースの暗号化については、お使いのシステムのソフトウェア文書を確認してください。"
+
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml200(link)
+msgid "Hacking servers that are turned off"
+msgstr "オフ状態のサーバーのハッキング"
+
+#: ./doc/security-guide/ch043_database-transport-security.xml8(title)
+msgid "Database transport security"
+msgstr "データベース通信セキュリティ"
+
+#: ./doc/security-guide/ch043_database-transport-security.xml9(para)
+msgid ""
+"This chapter covers issues related to network communications to and from the"
+" database server. This includes IP address bindings and encrypting network "
+"traffic with SSL."
+msgstr "本章はデータベースとのネットワーク通信に関連する問題を取り扱います。これには、IP アドレスのバインドや SSL を用いた暗号化ネットワーク通信を含みます。"
+
+#: ./doc/security-guide/ch043_database-transport-security.xml14(title)
+msgid "Database server IP address binding"
+msgstr "データベースサーバーの IP アドレスバインド"
+
+#: ./doc/security-guide/ch043_database-transport-security.xml15(para)
+msgid ""
+"To isolate sensitive database communications between the services and the "
+"database, we strongly recommend that the database server(s) be configured to"
+" only allow communications to and from the database over an isolated "
+"management network. This is achieved by restricting the interface or IP "
+"address on which the database server binds a network socket for incoming "
+"client connections."
+msgstr "サービスとデータベース間の機微なデータベース通信を隔離するために、データベースサーバーが隔離された管理ネットワーク経由のみでデータベースと通信できるように設定することを強く推奨します。データベースサーバーがクライアントからの通信用のネットワークソケットをバインドするインターフェースまたは IP アドレスを制限することにより、これを実現できます。"
+
+#: ./doc/security-guide/ch043_database-transport-security.xml24(title)
+msgid "Restricting bind address for MySQL"
+msgstr "MySQL のバインドアドレスの制限"
+
+#: ./doc/security-guide/ch043_database-transport-security.xml25(para)
+#: ./doc/security-guide/ch043_database-transport-security.xml63(para)
+msgid "In <filename>my.cnf</filename>:"
+msgstr "<filename>my.cnf</filename>:"
+
+#: ./doc/security-guide/ch043_database-transport-security.xml31(title)
+msgid "Restricting listen address for PostgreSQL"
+msgstr "PostgreSQL のバインドアドレスの制限"
+
+#: ./doc/security-guide/ch043_database-transport-security.xml32(para)
+msgid "In <filename>postgresql.conf</filename>:"
+msgstr "<filename>postgresql.conf</filename>:"
+
+#: ./doc/security-guide/ch043_database-transport-security.xml37(title)
+msgid "Database transport"
+msgstr "データベース通信"
+
+#: ./doc/security-guide/ch043_database-transport-security.xml38(para)
+msgid ""
+"In addition to restricting database communications to the management "
+"network, we also strongly recommend that the cloud administrator configure "
+"their database backend to require SSL. Using SSL for the database client "
+"connections protects the communications from tampering and eavesdropping. As"
+" will be discussed in the next section, using SSL also provides the "
+"framework for doing database user authentication through X.509 certificates "
+"(commonly referred to as PKI). Below is guidance on how SSL is typically "
+"configured for the two popular database backends MySQL and PostgreSQL."
+msgstr "データベース通信を管理ネットワークに制限することに加えて、クラウド管理者がそれらのデータベースのバックエンドに SSL を要求するように設定することを強く推奨します。データベースのクライアント接続に SSL を使用することにより、改ざんや盗聴から通信を保護できます。次のセクションで議論するように、SSL を使用することにより、データベースのユーザー認証に X.509 証明書 (一般的に PKI として参照されます) を使用するフレームワークも提供できます。以下は、2 つの有名なデータベースバックエンド MySQL と PostgreSQL に SSL を典型的に設定する方法について示します。"
+
+#: ./doc/security-guide/ch043_database-transport-security.xml50(para)
+msgid ""
+"When installing the certificate and key files, ensure that the file "
+"permissions are restricted, for example <placeholder-1/>, and the ownership "
+"is restricted to the database daemon user to prevent unauthorized access by "
+"other processes and users on the database server."
+msgstr "証明書と鍵ファイルをインストールするとき、ファイルのパーミッションが制限されていることを確認します。たとえば、<placeholder-1/> を実行すると、データベースサーバー上の他のプロセスやユーザーによる権限のないアクセスを防ぐために、所有者がデータベースデーモンのユーザーに制限されます。"
+
+#: ./doc/security-guide/ch043_database-transport-security.xml60(title)
+msgid "MySQL SSL configuration"
+msgstr "MySQL SSL 設定"
+
+#: ./doc/security-guide/ch043_database-transport-security.xml61(para)
+msgid ""
+"The following lines should be added in the system-wide MySQL configuration "
+"file:"
+msgstr "以下の行をシステム全体の MySQL 設定ファイルに追加する必要があります。"
+
+#: ./doc/security-guide/ch043_database-transport-security.xml69(para)
+#: ./doc/security-guide/ch043_database-transport-security.xml80(para)
+msgid ""
+"Optionally, if you wish to restrict the set of SSL ciphers used for the "
+"encrypted connection. See <link "
+"href=\"http://www.openssl.org/docs/apps/ciphers.html\">http://www.openssl.org/docs/apps/ciphers.html</link>"
+" for a list of ciphers and the syntax for specifying the cipher string:"
+msgstr "オプションとして、暗号化通信に使用される SSL 暗号を制限したい場合、暗号の一覧と暗号文字列を設定するための構文は <link href=\"http://www.openssl.org/docs/apps/ciphers.html\">http://www.openssl.org/docs/apps/ciphers.html</link> を参照してください。"
+
+#: ./doc/security-guide/ch043_database-transport-security.xml74(title)
+msgid "PostgreSQL SSL configuration"
+msgstr "PostgreSQL SSL 設定"
+
+#: ./doc/security-guide/ch043_database-transport-security.xml75(para)
+msgid ""
+"The following lines should be added in the system-wide PostgreSQL "
+"configuration file, <filename>postgresql.conf</filename>."
+msgstr "以下の行をシステム全体の PostgreSQL 設定ファイル <filename>postgresql.conf</filename> に追加する必要があります。"
+
+#: ./doc/security-guide/ch043_database-transport-security.xml82(para)
+msgid ""
+"The server certificate, key, and certificate authority (CA) files should be "
+"placed in the $PGDATA directory in the following files:"
+msgstr "サーバー証明書、鍵、認証局 (CA) のファイルを $PGDATA ディレクトリの以下のファイルに置く必要があります。"
+
+#: ./doc/security-guide/ch043_database-transport-security.xml86(para)
+msgid "<filename>$PGDATA/server.crt</filename> - Server certificate"
+msgstr "<filename>$PGDATA/server.crt</filename> - サーバー証明書"
+
+#: ./doc/security-guide/ch043_database-transport-security.xml90(para)
+msgid ""
+"<filename>$PGDATA/server.key</filename> - Private key corresponding to "
+"<filename>server.crt</filename>"
+msgstr "<filename>$PGDATA/server.key</filename> - <filename>server.crt</filename> に対応する秘密鍵"
+
+#: ./doc/security-guide/ch043_database-transport-security.xml94(para)
+msgid ""
+"<filename>$PGDATA/root.crt</filename> - Trusted certificate authorities"
+msgstr "<filename>$PGDATA/root.crt</filename> - 信頼された認証局"
+
+#: ./doc/security-guide/ch043_database-transport-security.xml98(para)
+msgid "<filename>$PGDATA/root.crl</filename> - Certificate revocation list"
+msgstr "<filename>$PGDATA/root.crl</filename> - 証明書失効リスト"
 
 #. When image changes, this message will be marked fuzzy or untranslated for
 #. you.
@@ -2886,6 +7432,859 @@ msgid ""
 "underlying hypervisor."
 msgstr "あなたのユースケースでライブマイグレーションが有効な場合、libvirtdによるトンネル化、暗号化されたライブマイグレーションが行えます。ただし、この機能は現在のOpenStackダッシュボードやnova-clientコマンドで実装されておらず、libvirtdの手動設定のみでしか利用できません。暗号化されたライブマイグレーションと通常のライブマイグレーションの違いは、次のとおりです。最初に、稼働しているハイパーバイザーからインスタンスのデータをlibvirtdへコピーします。次に、両ホストのlibvirtdプロセス間に暗号化されたトンネルが作成されます。最後に、目的先libvirtdプロセスがインスタンスを下層のハイパーバイザーへコピーします。"
 
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch008_system-roles-types.xml101(None)
+#: ./doc/security-guide/ch008_system-roles-types.xml106(None)
+msgid ""
+"@@image: 'static/services-protocols-ports.png'; "
+"md5=fb1e9f47d969127b7a5ca683d38cfe20"
+msgstr "@@image: 'static/services-protocols-ports.png'; md5=fb1e9f47d969127b7a5ca683d38cfe20"
+
+#: ./doc/security-guide/ch008_system-roles-types.xml8(title)
+msgid "System documentation requirements"
+msgstr "システムの文書化における要件"
+
+#: ./doc/security-guide/ch008_system-roles-types.xml9(para)
+msgid ""
+"The system documentation for an OpenStack cloud deployment should follow the"
+" templates and best practices for the Enterprise Information Technology "
+"System in your organization. Organizations often have compliance "
+"requirements which may require an overall System Security Plan to inventory "
+"and document the architecture of a given system. There are common challenges"
+" across the industry related to documenting the dynamic cloud infrastructure"
+" and keeping the information up-to-date."
+msgstr "OpenStack クラウドデプロイメントのシステム文書化は、その組織のエンタープライズ IT システムを対象とするテンプレートとベストプラクティスに従って行うべきです。組織には大抵、コンプライアンス要件が設定されており、それによって対象システムのインベントリ作成とアーキテクチャの文書化を行う全体的なシステムセキュリティ計画が義務付けられている場合があります。動的なクラウドインフラストラクチャーを文書化し、情報を最新の状態に維持するのあたっては、業界全体の共通課題があります。 "
+
+#: ./doc/security-guide/ch008_system-roles-types.xml18(title)
+msgid "System roles and types"
+msgstr "システムのロールとタイプ"
+
+#: ./doc/security-guide/ch008_system-roles-types.xml19(para)
+msgid ""
+"The two broadly defined types of nodes that generally make up an OpenStack "
+"installation are:"
+msgstr "通常 OpenStack のインストールを構成している、広く定義された 2 つのノードタイプは次のとおりです。"
+
+#: ./doc/security-guide/ch008_system-roles-types.xml23(para)
+msgid ""
+"Infrastructure nodes. The nodes that run the cloud related services such as "
+"the OpenStack Identity Service, the message queuing service, storage, "
+"networking, and other services required to support the operation of the "
+"cloud."
+msgstr "インフラストラクチャーノード。OpenStack Identity、メッセージキューサービス、ストレージ、ネットワーク、およびクラウドの運用をサポートするために必要なその他のサービスなどのクラウド関連サービスを実行するノードです。"
+
+#: ./doc/security-guide/ch008_system-roles-types.xml30(para)
+msgid ""
+"Compute, storage, or other resource nodes. Provide storage capacity or "
+"virtual machines for your cloud."
+msgstr "コンピュート、ストレージ、その他のリソースのノード。クラウド用のストレージ容量や仮想マシンを提供するノードです。"
+
+#: ./doc/security-guide/ch008_system-roles-types.xml37(title)
+msgid "System inventory"
+msgstr "システムインベントリ"
+
+#: ./doc/security-guide/ch008_system-roles-types.xml38(para)
+msgid ""
+"Documentation should provide a general description of the OpenStack "
+"environment and cover all systems used (production, development, test, "
+"etc.). Documenting system components, networks, services, and software often"
+" provides the bird's-eye view needed to thoroughly cover and consider "
+"security concerns, attack vectors and possible security domain bridging "
+"points. A system inventory may need to capture ephemeral resources such as "
+"virtual machines or virtual disk volumes that would otherwise be persistent "
+"resources in a traditional IT system."
+msgstr "文書には、OpenStack 環境の概要を記載し、使用する全システム (実稼働、開発、テストなど)  を対象とするべきです。多くの場合、システムコンポーネント、ネットワーク、サービス、およびソフトウェアについて文書化することにより、セキュリティ課題、攻撃ベクトル、考えられるセキュリティドメインのブリッジングポイントを完全に網羅して検討するにあたって必要な概観が提供されます。システムインベントリには、従来の IT システムでは永続的なリソースとされている、仮想マシンや仮想ディスクボリュームなどの一時的なリソースを取り込む必要がある場合があります。"
+
+#: ./doc/security-guide/ch008_system-roles-types.xml48(title)
+msgid "Hardware inventory"
+msgstr "ハードウェアインベントリ"
+
+#: ./doc/security-guide/ch008_system-roles-types.xml49(para)
+msgid ""
+"Clouds without stringent compliance requirements for written documentation "
+"might benefit from having a Configuration Management Database "
+"(<glossterm>CMDB</glossterm>). CMDBs are normally used for hardware asset "
+"tracking and overall life-cycle management. By leveraging a CMDB, an "
+"organization can quickly identify cloud infrastructure hardware. For "
+"example, compute nodes, storage nodes, and network devices that exist on the"
+" network but that might not be adequately protected and/or forgotten. "
+"OpenStack provisioning system might provide some CMDB-like functions "
+"especially if auto-discovery features of hardware attributes are available."
+msgstr "文書化に対する厳密なコンプライアンス要件のないクラウドの場合は、少なくとも構成管理データベース (<glossterm>CMDB</glossterm>) を使用することによってメリットが得られる可能性があります。CMDB は通常、ハードウェア資産の追跡や全般的なライフサイクル管理に使用されます。CMDB を活用することにより、組織はネットワーク上に存在するクラウドインフラストラクチャーハードウェア (例: コンピュートノード、ストレージノード、ネットワークデバイスなど) の中で適切に保護されていないハードウェアや忘れられているハードウェアを迅速に特定することができます。OpenStack のプロビジョニングシステムは、ハードウェア属性の自動検出機能が利用できる場合は特に、CMDB のような機能を一部提供することが可能です。"
+
+#: ./doc/security-guide/ch008_system-roles-types.xml63(title)
+msgid "Software inventory"
+msgstr "ソフトウェアインベントリ"
+
+#: ./doc/security-guide/ch008_system-roles-types.xml64(para)
+msgid ""
+"Just as with hardware, all software components within the OpenStack "
+"deployment should be documented. Components here should include system "
+"databases; OpenStack software components and supporting sub-components; and,"
+" supporting infrastructure software such as load-balancers, reverse proxies,"
+" and network address translators. Having an authoritative list like this may"
+" be critical toward understanding total system impact due to a compromise or"
+" vulnerability of a specific class of software."
+msgstr "ハードウェアと同様に、OpenStack デプロイメント内のソフトウェアコンポーネントはすべて文書化しておくべきです。このコンポーネントには、システムデータベース、OpenStack ソフトウェアコンポーネントおよびサポートサブコンポーネント、ロードバランサー/リバースプロキシ/ネットワークアドレストランスレーターなどのサポートインフラストラクチャーソフトウェアなどが含まれます。このような信頼できる一覧を用意しておくことは、ソフトウェアの特定のクラスの侵害や脆弱性によってシステムが受ける全体的な影響を把握するために極めて重要となります。"
+
+#: ./doc/security-guide/ch008_system-roles-types.xml76(title)
+msgid "Network topology"
+msgstr "ネットワークトポロジー"
+
+#: ./doc/security-guide/ch008_system-roles-types.xml77(para)
+msgid ""
+"A network topology should be provided with highlights specifically calling "
+"out the data flows and bridging points between the security domains. Network"
+" ingress and egress points should be identified along with any OpenStack "
+"logical system boundaries. Multiple diagrams may be needed to provide "
+"complete visual coverage of the system. A network topology document should "
+"include virtual networks created on behalf of tenants by the system along "
+"with virtual machine instances and gateways created by OpenStack."
+msgstr "ネットワークトポロジーは、セキュリティドメイン間のデータフローとブリッジングポイントをはっきりと識別して強調するようにして作成すべきです。OpenStack の論理的なシステム境界とともに、ネットワークの受信および送信ポイントを明確にすることを推奨します。システムを完全に視覚的に網羅するには、図を複数作成する必要がある場合があります。また、ネットワークトポロジーの文書には、テナントに代わってシステムが作成した仮想ネットワークや、OpenStack によって作成された仮想マシンインスタンスとゲートウェイを含めるべきです。"
+
+#: ./doc/security-guide/ch008_system-roles-types.xml88(title)
+msgid "Services, protocols and ports"
+msgstr "サービス、プロトコル、およびポート"
+
+#: ./doc/security-guide/ch008_system-roles-types.xml89(para)
+msgid ""
+"The service, protocols and ports table provides important additional detail "
+"of an OpenStack deployment. A table view of all services running within the "
+"cloud infrastructure can immediately inform, guide, and help check security "
+"procedures. Firewall configuration, service port conflicts, security "
+"remediation areas, and compliance requirements become easier to manage when "
+"you have concise information available. Consider the following table:"
+msgstr "サービス、プロトコル、ポートの表には OpenStack デプロイメントの重要な追加情報を記載します。クラウドインフラストラクチャー内で稼働中の全サービスを表にまとめると、情報や指針を直ちに確認することができ、セキュリティプロシージャーをチェックするのに役立ちます。簡潔な情報が提供されると、ファイアウォールの設定やサービスポートの競合、セキュリティ修復領域、コンプライアンス要件をより容易に管理できるようになります。以下の表を検討してください。 "
+
+#: ./doc/security-guide/ch008_system-roles-types.xml109(para)
+msgid ""
+"Referencing a table of services, protocols and ports can help in "
+"understanding the relationship between OpenStack components. It is highly "
+"recommended that OpenStack deployments have information similar to this on "
+"record."
+msgstr "サービス、プロトコル、ポートの表を参照すると、OpenStack のコンポーネント間の関係を理解するのに役立ちます。OpenStack のデプロイメントには、これと同様の情報を記録することを強く推奨します。"
+
+#: ./doc/security-guide/ch018_case-studies-pkissl.xml8(title)
+msgid "Case studies: PKI and certificate management"
+msgstr "ケーススタディ: PKI と証明書管理"
+
+#: ./doc/security-guide/ch018_case-studies-pkissl.xml9(para)
+msgid ""
+"In this case study we discuss how Alice and Bob would address deployment of "
+"PKI certification authorities (CA) and certificate management."
+msgstr "このケーススタディでは、アリスとボグがPKI認証局(CA)の構築と証明書管理をどのように行うのかについて解説します。"
+
+#: ./doc/security-guide/ch018_case-studies-pkissl.xml12(para)
+msgid ""
+"Alice as a cloud architect within a government agency knows that her agency "
+"operates its own certification authority. Alice contacts the PKI office in "
+"her agency that manages her PKI and certificate issuance. Alice obtains "
+"certificates issued by this CA and configures the services within both the "
+"public and management security domains to use these certificates. Since "
+"Alice's OpenStack deployment exists entirely on a disconnected from the "
+"Internet network, she makes sure to remove all default CA bundles that "
+"contain external public CA providers to ensure the OpenStack services only "
+"accept client certificates issued by her agency's CA."
+msgstr "アリスは政府機関のクラウドアーキテクトで、彼女の機関が独自のCAを運用している事を知っています。アリスは、彼女のPKIを管理して証明書を発行する職場の PKI オフィスにコンタクトします。アリスはこのCAによって発行された証明書を入手し、これらの証明書を使用するようパブリックと管理セキュリティドメインの両方のサービスを設定します。アリスの OpenStack デプロイが完全にインターネットから独立して存在するので、OpenStack サービスが彼女の組織の CA から発行されたクライアント証明書のみ許可するよう、外部のパブリックな CA プロバイダを含むデフォルトの全 CA バンドルが削除されている事を確認しています。"
+
+#: ./doc/security-guide/ch018_case-studies-pkissl.xml16(para)
+msgid ""
+"Bob is architecting a public cloud and needs to ensure that the publicly "
+"facing OpenStack services are using certificates issued by a major public "
+"CA. Bob acquires certificates for his public OpenStack services and "
+"configures the services to use PKI and SSL and includes the public CAs in "
+"his trust bundle for the services. Additionally, Bob also wants to further "
+"isolate the internal communications amongst the services within the "
+"management security domain. Bob contacts the team within his organization "
+"that is responsible for managing his organizations PKI and issuance of "
+"certificates using their own internal CA. Bob obtains certificates issued by"
+" this internal CA and configures the services that communicate within the "
+"management security domain to use these certificates and configures the "
+"services to only accept client certificates issued by his internal CA."
+msgstr "ボブはパブリッククラウドのアーキテクトで、インターネットに接続された OpenStack サービスが主要な公的 CA から発行された証明書をちゃんと使用する必要があります。ボブは彼のパブリックな OpenStack サービス用の証明書を受領し、PKI と SSL を使用するようサービスを設定し、彼のサービス用の信用バンドル中に公的CAが含まれるようにします。更に、ボブはセキュリティ管理ドメイン内でサービス間の内部通信の更なる分断をしたいとも思っています。ボブは、彼の組織中で、内部CAを使用して彼の組織の PKI 管理と証明書の発行を担当しているチームにコンタクトします。ボブはこの内部CAが発行した証明書を入手し、これらの証明書を使用するよう管理セキュリティドメイン中での通信を行うサービスを設定し、内部CAが発行したクライアント証明書のみ許可するようサービスを設定します。"
+
+#: ./doc/security-guide/ch041_database-backend-considerations.xml7(title)
+msgid "Database back-end considerations"
+msgstr "データベースバックエンドの考慮事項"
+
+#: ./doc/security-guide/ch041_database-backend-considerations.xml8(para)
+msgid ""
+"The choice of database server is an important consideration in the security "
+"of an OpenStack deployment. While security considerations are not the only "
+"basis on which a database server must be chosen, security considerations are"
+" the only ones within the scope of this book. In practice, OpenStack only "
+"supports two database types: PostgreSQL and MySQL."
+msgstr "データベースサーバーの選択は OpenStack 環境のセキュリティにおける重要な考慮事項です。セキュリティの考慮事項はデータベースサーバーの選択における唯一の基準ではありませんが、このドキュメントではこれらのみを取り扱います。実際のところ、OpenStack は 2 種類のデータベース PostgreSQL と MySQL のみをサポートします。"
+
+#: ./doc/security-guide/ch041_database-backend-considerations.xml9(para)
+msgid ""
+"PostgreSQL has a number of desirable security features such as Kerberos "
+"authentication, object-level security, and encryption support. The "
+"PostgreSQL community has done well to provide solid guidance, documentation,"
+" and tooling to promote positive security practices."
+msgstr "PostgreSQL は、Kerberos 認証、オブジェクトレベルのセキュリティ、暗号化のサポートなど、数多くの望ましいセキュリティ機能を有します。PostgreSQL コミュニティは実用的なセキュリティ実践を推進するために、わかりやすいガイダンス、ドキュメント、ツールを十分に提供してきました。"
+
+#: ./doc/security-guide/ch041_database-backend-considerations.xml10(para)
+msgid ""
+"MySQL has a large community, widespread adoption, and provides high "
+"availability options. MySQL also has the ability to provide enhanced client "
+"authentication by way of plug-in authentication mechanisms. Forked "
+"distributions in the MySQL community provide many options for consideration."
+" It is important to choose a specific implementation of MySQL based on a "
+"thorough evaluation of the security posture and the level of support "
+"provided for the given distribution."
+msgstr "MySQL は大規模なコミュニティを持ち、幅広く適用され、高可用性のオプションを提供しています。MySQL も、プラグイン認証機構の方法により高度なクライアント認証を提供する機能があります。MySQL コミュニティから派生したディストリビューションは、考慮事項に対する多くのオプションを提供しています。セキュリティの考え方やディストリビューションに提供されるサポートレベルの評価に基づいて、特定の MySQL ディストリビューションを選択することが重要です。"
+
+#: ./doc/security-guide/ch041_database-backend-considerations.xml12(title)
+msgid "Security references for database back-ends"
+msgstr "データベースバックエンドのセキュリティ参考資料"
+
+#: ./doc/security-guide/ch041_database-backend-considerations.xml13(para)
+msgid ""
+"Those deploying MySQL or PostgreSQL are advised to refer to existing "
+"security guidance. Some references are listed below:"
+msgstr "MySQL や PostgreSQL を導入する人は、既存のセキュリティガイダンスを参照することが推奨されます。いくつかの参考資料を以下に一覧化します。"
+
+#: ./doc/security-guide/ch041_database-backend-considerations.xml14(para)
+msgid "MySQL:"
+msgstr "MySQL:"
+
+#: ./doc/security-guide/ch041_database-backend-considerations.xml16(link)
+msgid "OWASP MySQL Hardening"
+msgstr "OWASP MySQL Hardening"
+
+#: ./doc/security-guide/ch041_database-backend-considerations.xml19(link)
+msgid "MySQL Pluggable Authentication"
+msgstr "MySQL Pluggable Authentication"
+
+#: ./doc/security-guide/ch041_database-backend-considerations.xml22(link)
+msgid "Security in MySQL"
+msgstr "Security in MySQL"
+
+#: ./doc/security-guide/ch041_database-backend-considerations.xml25(para)
+msgid "PostgreSQL:"
+msgstr "PostgreSQL:"
+
+#: ./doc/security-guide/ch041_database-backend-considerations.xml27(link)
+msgid "OWASP PostgreSQL Hardening"
+msgstr "OWASP PostgreSQL Hardening"
+
+#: ./doc/security-guide/ch041_database-backend-considerations.xml30(link)
+msgid "Total security in a PostgreSQL database"
+msgstr "Total security in a PostgreSQL database"
+
+#: ./doc/security-guide/ch039_case-studies-messaging.xml8(title)
+msgid "Case studies: messaging"
+msgstr "ケーススタディ: メッセージング"
+
+#: ./doc/security-guide/ch039_case-studies-messaging.xml9(para)
+msgid ""
+"The message queue is a critical piece of infrastructure that supports a "
+"number of OpenStack services but is most strongly associated with the "
+"Compute service. Due to the nature of the message queue service, Alice and "
+"Bob have similar security concerns. One of the larger concerns that remains "
+"is that many systems have access to this queue and there is no way for a "
+"consumer of the queue messages to verify which host or service placed the "
+"messages on the queue. An attacker who is able to successfully place "
+"messages on the queue is able to create and delete VM instances, attach the "
+"block storage of any tenant and a myriad of other malicious actions. There "
+"are a number of solutions on the horizon to fix this, with several proposals"
+" for message signing and encryption making their way through the OpenStack "
+"development process."
+msgstr "メッセージキューは、多数の OpenStack サービスを支える重要なインフラストラクチャであり、特にコンピュートサービスと強く結びついています。メッセージキューサービスの性質上、アリスとボブが抱えるセキュリティ上の懸念はよく似ています。特に大きな残課題は、数多くのシステムがキューにアクセスしているものの、キューメッセージのコンシューマーには、キューを発行したホストやサービスを確かめる手立てがないことです。攻撃者がキューの発行に成功すると、仮想マシンの作成や削除をしたり、あらゆるテナントのブロックストレージに接続するなど、他にも無数の悪意のある攻撃が可能になってしまいます。\nこれを防ぐためのソリューションが出始めており、いくつかはメッセージへの署名と暗号化を使ったものが OpenStack の開発プロセスで進んでいます。"
+
+#: ./doc/security-guide/ch039_case-studies-messaging.xml12(para)
+msgid ""
+"In this case Alice's controls mimic those Bob has deployed for the public "
+"cloud."
+msgstr "このケースでは、アリスの方法はボブがパブリッククラウドに展開した方法と同じものを使用します。"
+
+#: ./doc/security-guide/ch039_case-studies-messaging.xml16(para)
+msgid ""
+"Bob assumes that at some point infrastructure or networks underpinning the "
+"Compute service may become compromised. Due to this, he recognizes the "
+"importance of locking down access to the message queue. To do this Bob "
+"deploys his RabbitMQ servers with SSL and X.509 client auth for access "
+"control. This in turn limits the capabilities of an attacker who has "
+"compromised a system that does not have queue access."
+msgstr "ボブは、コンピュートサービスを支えるインフラストラクチャとネットワークがある時点でセキュリティ侵害に会うと仮定します。そして、メッセージキューへのアクセス制限の重要性に気づきました。\nそこで、RabbitMQ サーバーに SSL と X.509 クライアントアクセス制御を適用することにします。これにより、キューアクセスを持たないシステムを乗っ取られても、攻撃者の能力を制限することができます。"
+
+#: ./doc/security-guide/ch039_case-studies-messaging.xml17(para)
+msgid ""
+"Additionally, Bob adds strong network ACL rulesets to enforce which "
+"endpoints can communicate with the message servers. This second control "
+"provides some additional assurance should the other protections fail."
+msgstr "さらにボブは、メッセージサーバーと通信できるエンドポイントを、強力なネットワークの ACL ルールセットで制限することにしました。この2個目の制限が、他の防御が失敗した場合の保険として機能します。"
+
+#: ./doc/security-guide/ch062_audit-guidance.xml8(title)
+msgid "Understanding the audit process"
+msgstr "監査プロセスを理解する"
+
+#: ./doc/security-guide/ch062_audit-guidance.xml9(para)
+msgid ""
+"Information system security compliance is reliant on the completion of two "
+"foundational processes:"
+msgstr "情報システムのセキュリティコンプライアンスは、二つの基本的なプロセスの完了を前提としています。"
+
+#: ./doc/security-guide/ch062_audit-guidance.xml13(para)
+msgid ""
+"<emphasis role=\"bold\">Implementation and operation of security "
+"controls.</emphasis> Aligning the information system with in-scope standards"
+" and regulations involves internal tasks which must be conducted before a "
+"formal assessment. Auditors may be involved at this state to conduct gap "
+"analysis, provide guidance, and increase the likelihood of successful "
+"certification."
+msgstr "<emphasis role=\"bold\">セキュリティコントロールの実装と運用。</emphasis>情報システムを標準と規制の範囲内で運用しつづけること、それは、正式なアセスメント前でも行うべき内部タスクです。なお監査人はこの時点で、ギャップ分析、助言、認証取得の可能性向上のために関与することがあります。"
+
+#: ./doc/security-guide/ch062_audit-guidance.xml23(para)
+msgid ""
+"<emphasis role=\"bold\">Independent verification and validation.</emphasis> "
+"Demonstration to a neutral third-party that system security controls are "
+"implemented and operating effectively, in compliance with in-scope standards"
+" and regulations, is required before many information systems achieve "
+"certified status. Many certifications require periodic audits to ensure "
+"continued certification, considered part of an overarching continuous "
+"monitoring practice."
+msgstr "<emphasis role=\"bold\">独立した検査と検証。</emphasis>システムのセキュリティコントロールが標準と規制の範囲に従って実装され、効率的に運用されているか。これを中立的な第三者へ、認証を得る以前に証明しなければなりません。多くの認証は、その継続を保証するため、包括的な継続監視の一部として、定期的な監査を必要とします。"
+
+#: ./doc/security-guide/ch062_audit-guidance.xml36(title)
+msgid "Determining audit scope"
+msgstr "監査の範囲を決定する"
+
+#: ./doc/security-guide/ch062_audit-guidance.xml37(para)
+msgid ""
+"Determining audit scope, specifically what controls are needed and how to "
+"design or modify an OpenStack deployment to satisfy them, should be the "
+"initial planning step."
+msgstr "何をコントロールするのか、OpenStack環境をいかにデザイン、変更していくかを明確にするため、監査範囲は初期の計画段階で決定すべきです。"
+
+#: ./doc/security-guide/ch062_audit-guidance.xml38(para)
+msgid ""
+"When scoping OpenStack deployments for compliance purposes, consider "
+"prioritizing controls around sensitive services, such as command and control"
+" functions and the base virtualization technology. Compromises of these "
+"facilities may impact an OpenStack environment in its entirety."
+msgstr "OpenStack環境の範囲をコンプライアンス目的で明確化する際は、制御機能や仮想化技術など、慎重に扱うべきサービスの周辺を優先するよう、考慮すべきです。それらを妥協することは、OpenStack環境全体に影響を与えかねません。"
+
+#: ./doc/security-guide/ch062_audit-guidance.xml39(para)
+msgid ""
+"Scope reduction helps ensure OpenStack architects establish high quality "
+"security controls which are tailored to a particular deployment, however it "
+"is paramount to ensure these practices do not omit areas or features from "
+"security hardening. A common example is applicable to PCI-DSS guidelines, "
+"where payment related infrastructure may be scrutinized for security issues,"
+" but supporting services are left ignored, and vulnerable to attack."
+msgstr "範囲を限定することで、限定された環境に対し、OpenStackの設計者は高いセキュリティ品質を確立しやすくなります。しかしその取り組みの中で、セキュリティ強化の範囲や機能を不当に省かないことが重要です。典型的な例はPCI-DSSガイドラインです。決済に関わるインフラはセキュリティを精査されるでしょう。が、その影でその周辺サービスが放置されれば、そこが攻撃に対し無防備となります。"
+
+#: ./doc/security-guide/ch062_audit-guidance.xml40(para)
+msgid ""
+"When addressing compliance, you can increase efficiency and reduce work "
+"effort by identifying common areas and criteria that apply across multiple "
+"certifications. Much of the audit principles and guidelines discussed in "
+"this book will assist in identifying these controls, additionally a number "
+"of external entities provide comprehensive lists. The following are some "
+"examples:"
+msgstr "コンプライアンスに取り組む際、複数の認証で共通の領域と基準を明確にできれば、効率的に手間を減らすことができます。この本で取り上げている監査原則とガイドラインの多くは、それらを特定するのに役立ちます。加えて、総合的なリストを提供するガイドラインが多くあります。以下に例を挙げます。"
+
+#: ./doc/security-guide/ch062_audit-guidance.xml41(para)
+msgid ""
+"The <link href=\"https://cloudsecurityalliance.org/research/ccm/\">Cloud "
+"Security Alliance Cloud Controls Matrix</link> (CCM) assists both cloud "
+"providers and consumers in assessing the overall security of a cloud "
+"provider. The CSA CMM provides a controls framework that map to many "
+"industry-accepted standards and regulations including the ISO 27001/2, "
+"ISACA, COBIT, PCI, NIST, Jericho Forum and NERC CIP."
+msgstr "<link href=\"https://cloudsecurityalliance.org/research/ccm/\">Cloud Security Alliance Cloud Controls Matrix</link> (CCM)はクラウドプロバイダーのセキュリティを総合的に評価するにあたって、プロバイダーとユーザーの両方に役立ちます。CSA CCMはISO 27001/2、ISACA、COBIT、PIC、NIST、Jericho Forum、NERC CIPといった、多くの業界で認められた標準、規制をひも付けた統制フレームワークを提供します。"
+
+#: ./doc/security-guide/ch062_audit-guidance.xml42(para)
+msgid ""
+"The <link href=\"https://fedorahosted.org/scap-security-guide/\">SCAP "
+"Security Guide</link> is another useful reference. This is still an emerging"
+" source, but we anticipate that this will grow into a tool with controls "
+"mappings that are more focused on the US federal government certifications "
+"and recommendations. For example, the SCAP Security Guide currently has some"
+" mappings for security technical implementation guides (STIGs) and "
+"NIST-800-53."
+msgstr "<link href=\"https://fedorahosted.org/scap-security-guide/\">SCAP Security Guide</link>はもうひとつの有用なリファレンスです。まだ出来たばかりですが、米国連邦政府の認証、推奨への対応に重点を絞ったツールとして普及すると予想されます。例えば、SCAP Security Guideは現在、security technical implementation guides (STIGs)とNIST-800-53にある程度対応しています。"
+
+#: ./doc/security-guide/ch062_audit-guidance.xml43(para)
+msgid ""
+"These control mappings will help identify common control criteria across "
+"certifications, and provide visibility to both auditors and auditees on "
+"problem areas within control sets for particular compliance certifications "
+"and attestations."
+msgstr "これらのコントロールマッピングは、認証間で共通の統制基準を特定します。また、監査人と被監査者両方にとって問題となる、特定のコンプライアンス認証、認定に必要なコントロールセットを可視化するのに役立ちます。"
+
+#: ./doc/security-guide/ch062_audit-guidance.xml46(title)
+msgid "Internal audit"
+msgstr "内部監査"
+
+#: ./doc/security-guide/ch062_audit-guidance.xml47(para)
+msgid ""
+"Once a cloud is deployed, it is time for an internal audit. This is the time"
+" compare the controls you identified above with the design, features, and "
+"deployment strategies utilized in your cloud. The goal is to understand how "
+"each control is handled and where gaps exist. Document all of the findings "
+"for future reference."
+msgstr "クラウドが導入されたのであれば、内部監査が必要です。あなたが採用を決めた統制基準と、あなたのクラウドの設計、機能、配備戦略を比較する時です。目的はそれぞれの統制がどのように扱われているか、ギャップがどこに存在するか、理解することです。そして、その全てを将来のために文書化します。"
+
+#: ./doc/security-guide/ch062_audit-guidance.xml48(para)
+msgid ""
+"When auditing an OpenStack cloud it is important to appreciate the multi-"
+"tenant environment inherent in the OpenStack architecture. Some critical "
+"areas for concern include data disposal, hypervisor security, node "
+"hardening, and authentication mechanisms."
+msgstr "OpenStackクラウドを監査するとき、OpenStackアーキテクチャ固有のマルチテナント環境を理解することが重要です。データの廃棄、ハイパーバイザーのセキュリティ、ノードの強化、および認証メカニズムなど、いくつか重要な部分があります。"
+
+#: ./doc/security-guide/ch062_audit-guidance.xml51(title)
+msgid "Prepare for external audit"
+msgstr "外部監査に備える"
+
+#: ./doc/security-guide/ch062_audit-guidance.xml52(para)
+msgid ""
+"Once the internal audit results look good, it is time to prepare for an "
+"external audit. There are several key actions to take at this stage, these "
+"are outlined below:"
+msgstr "内部監査の結果が良好であれば、いよいよ外部監査の準備です。この段階では、いくつかの鍵となる活動があります。概要は以下です。"
+
+#: ./doc/security-guide/ch062_audit-guidance.xml54(para)
+msgid ""
+"Maintain good records from your internal audit. These will prove useful "
+"during the external audit so you can be prepared to answer questions about "
+"mapping the compliance controls to a particular deployment."
+msgstr "内部監査での良好な状態を維持してください。それらは外部監査の実施期間に証明として役立ちます。またそれは、コンプライアンス統制に関する詳細な質疑応答の備えとなります。"
+
+#: ./doc/security-guide/ch062_audit-guidance.xml57(para)
+msgid ""
+"Deploy automated testing tools to ensure that the cloud remains compliant "
+"over time."
+msgstr "クラウドがコンプライアンスを維持し続けるために、自動テストツールを導入してください。"
+
+#: ./doc/security-guide/ch062_audit-guidance.xml60(para)
+msgid "Select an auditor."
+msgstr "監査人を選ぶ"
+
+#: ./doc/security-guide/ch062_audit-guidance.xml63(para)
+msgid ""
+"Selecting an auditor can be challenging. Ideally, you are looking for "
+"someone with experience in cloud compliance audits. OpenStack experience is "
+"another big plus. Often it is best to consult with people who have been "
+"through this process for referrals. Cost can vary greatly depending on the "
+"scope of the engagement and the audit firm considered."
+msgstr "監査人の選定は困難を伴うことがあります。クラウドのコンプライアンス監査経験がある人を見つけてくるのが理想です。OpenStackの経験があれば、なお良しです。このプロセスを経験している人に相談するのがベストでしょう。なお、費用は契約の範囲と監査法人に大きく依存します。"
+
+#: ./doc/security-guide/ch062_audit-guidance.xml66(title)
+msgid "External audit"
+msgstr "外部監査"
+
+#: ./doc/security-guide/ch062_audit-guidance.xml67(para)
+msgid ""
+"This is the formal audit process. Auditors will test security controls in "
+"scope for a specific certification, and demand evidentiary requirements to "
+"prove that these controls were also in place for the audit window (for "
+"example SOC 2 audits generally evaluate security controls over a 6-12 months"
+" period). Any control failures are logged, and will be documented in the "
+"external auditors final report. Dependent on the type of OpenStack "
+"deployment, these reports may be viewed by customers, so it is important to "
+"avoid control failures. This is why audit preparation is so important."
+msgstr "これが正式な監査プロセスです。監査人は、特定の認定向けのセキュリティ統制を確認し、これらの統制が監査期間において整っているか証明する根拠を要求します (たとえば、SOC 2監査は一般的に6-12ヶ月のセキュリティ統制を評価します)。どのような統制上の不具合も記録され、外部監査の最終報告書で文書化されます。OpenStack環境の種別に依存しますが、これらの報告書は顧客に公開されるでしょう。それゆえ統制上の不具合を避けることは重要です。これが監査への準備が重要であることの理由です。"
+
+#: ./doc/security-guide/ch062_audit-guidance.xml70(title)
+msgid "Compliance maintenance"
+msgstr "コンプライアンスの維持"
+
+#: ./doc/security-guide/ch062_audit-guidance.xml71(para)
+msgid ""
+"The process doesn't end with a single external audit. Most certifications "
+"require continual compliance activities which means repeating the audit "
+"process periodically. We recommend integrating automated compliance "
+"verification tools into a cloud to ensure that it is compliant at all times."
+" This should be in done in addition to other security monitoring tools. "
+"Remember that the goal is both security <emphasis>and</emphasis> compliance."
+" Failing on either of these fronts will significantly complicate future "
+"audits."
+msgstr "このプロセスは一度の外部監査で終わることがありません。多くの認証は継続的なコンプライアンス活動、すなわち、定期的な監査を要求します。わたしたちは、常に準拠を確実にするために、自動化されたコンプライアンス検証ツールをクラウド内に作ることをおすすめします。これは他のセキュリティ監視ツールに加え実装されるべきです。このゴールがセキュリティ<emphasis>および</emphasis>コンプライアンスであることを忘れないでください。これらのどちらかに不具合があれば、将来の監査において非常に面倒なことになります。"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch005_security-domains.xml29(None)
+#: ./doc/security-guide/ch005_security-domains.xml32(None)
+msgid ""
+"@@image: 'static/untrusted_trusted.png'; "
+"md5=a582dac2ad0b3f439fd4b08386853056"
+msgstr "@@image: 'static/untrusted_trusted.png'; md5=a582dac2ad0b3f439fd4b08386853056"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch005_security-domains.xml60(None)
+#: ./doc/security-guide/ch005_security-domains.xml63(None)
+msgid ""
+"@@image: 'static/bridging_security_domains_1.png'; "
+"md5=0d5ca26c51882ce3253405e91a597715"
+msgstr "@@image: 'static/bridging_security_domains_1.png'; md5=0d5ca26c51882ce3253405e91a597715"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch005_security-domains.xml68(None)
+#: ./doc/security-guide/ch005_security-domains.xml71(None)
+msgid ""
+"@@image: 'static/bridging_domains_clouduser.png'; "
+"md5=17c8a233ee7de17d2f600c7f6f6afe24"
+msgstr "@@image: 'static/bridging_domains_clouduser.png'; md5=17c8a233ee7de17d2f600c7f6f6afe24"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch005_security-domains.xml134(None)
+#: ./doc/security-guide/ch005_security-domains.xml137(None)
+msgid ""
+"@@image: 'static/threat_actors.png'; md5=114c2f9bd9d0319bdd83f9e229d44649"
+msgstr "@@image: 'static/threat_actors.png'; md5=114c2f9bd9d0319bdd83f9e229d44649"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch005_security-domains.xml171(None)
+#: ./doc/security-guide/ch005_security-domains.xml174(None)
+msgid ""
+"@@image: 'static/high-capability.png'; md5=b7ab599c8b40558a52c0ca86aad89741"
+msgstr "@@image: 'static/high-capability.png'; md5=b7ab599c8b40558a52c0ca86aad89741"
+
+#: ./doc/security-guide/ch005_security-domains.xml8(title)
+msgid "Security boundaries and threats"
+msgstr "セキュリティ境界と脅威"
+
+#: ./doc/security-guide/ch005_security-domains.xml9(para)
+msgid ""
+"A cloud can be abstracted as a collection of logical components by virtue of"
+" their function, users, and shared security concerns, which we call security"
+" domains. Threat actors and vectors are classified based on their motivation"
+" and access to resources. Our goal is to provide you a sense of the security"
+" concerns with respect to each domain depending on your risk/vulnerability "
+"protection objectives."
+msgstr "クラウドとは、セキュリティドメインと呼ばれる、機能やユーザー、共有セキュリティの懸念点に基づいた論理コンポーネントの集まりであると要約できます。脅威に関するアクターやベクトルは、リソースへのアクセスや動機をベースに分類されます。OpenStack の目標は、リスクや脆弱性保護の目的にあわせてドメインごとにセキュリティの懸念点に関する判断材料を提供することです。"
+
+#: ./doc/security-guide/ch005_security-domains.xml11(title)
+msgid "Security domains"
+msgstr "セキュリティドメイン"
+
+#: ./doc/security-guide/ch005_security-domains.xml12(para)
+msgid ""
+"A security domain comprises users, applications, servers or networks that "
+"share common trust requirements and expectations within a system. Typically "
+"they have the same authentication and authorization (AuthN/Z) requirements "
+"and users."
+msgstr "セキュリティドメインは、システム内の信頼性に関する共通の要件や期待を共有するユーザー、アプリケーション、サーバー、ネットワークのいずれかで構成されています。通常、これらのドメインには、同じ認証と承認  (AuthN/Z) 要件およびユーザーが指定されています。"
+
+#: ./doc/security-guide/ch005_security-domains.xml13(para)
+msgid ""
+"Although you may desire to break these domains down further (we later "
+"discuss where this may be appropriate), we generally refer to four distinct "
+"security domains which form the bare minimum that is required to deploy any "
+"OpenStack cloud securely. These security domains are:"
+msgstr "これらのドメインをさらに分類する場合もありますが (該当箇所で説明)、一般的に OpenStack クラウドをセキュアにデプロイしていく上で最低限必要な部分を構成する、4 つの異なるセキュリティドメインのことを指します。以下に、これらのセキュリティドメインを示しています。"
+
+#: ./doc/security-guide/ch005_security-domains.xml15(para)
+#: ./doc/security-guide/ch005_security-domains.xml36(title)
+msgid "Public"
+msgstr "パブリック"
+
+#: ./doc/security-guide/ch005_security-domains.xml18(para)
+#: ./doc/security-guide/ch005_security-domains.xml41(title)
+msgid "Guest"
+msgstr "ゲスト"
+
+#: ./doc/security-guide/ch005_security-domains.xml21(para)
+#: ./doc/security-guide/ch005_security-domains.xml46(title)
+msgid "Management"
+msgstr "管理"
+
+#: ./doc/security-guide/ch005_security-domains.xml24(para)
+#: ./doc/security-guide/ch005_security-domains.xml51(title)
+msgid "Data"
+msgstr "データ"
+
+#: ./doc/security-guide/ch005_security-domains.xml27(para)
+msgid ""
+"We selected these security domains because they can be mapped independently "
+"or combined to represent the majority of the possible areas of trust within "
+"a given OpenStack deployment. For example, some deployment topologies "
+"combine both guest and data domains onto one physical network versus others,"
+" which have these networks physically separated. In each case, the cloud "
+"operator should be aware of the appropriate security concerns. Security "
+"domains should be mapped out against your specific OpenStack deployment "
+"topology. The domains and their trust requirements depend upon whether the "
+"cloud instance is public, private, or hybrid."
+msgstr "上記のセキュリティドメインを選択したのは、個別にマッピング可能であること、または組み合わせると指定の OpenStack デプロイメントで存在する可能性のある信頼エリアの大部分を表すことができるためです。例えば、デプロイメントトポロジによっては、物理ネットワーク 1 つ vs 他のネットワークとなるように、ゲストとデータドメインの両方を組みわせて、ネットワークを物理的に分割するものもあります。いずれの場合も、クラウドオペレーターは、適切なセキュリティの関心事を認識する必要があります。これらのドメインや信頼性に関する要件は、クラウドインスタンスがパブリック、プライベート、ハイブリッドのいずれであるかによって変わってきます。"
+
+#: ./doc/security-guide/ch005_security-domains.xml37(para)
+msgid ""
+"The public security domain is an entirely untrusted area of the cloud "
+"infrastructure. It can refer to the Internet as a whole or simply to "
+"networks over which you have no authority. Any data that transits this "
+"domain with confidentiality or integrity requirements should be protected "
+"using compensating controls."
+msgstr "パブリックのセキュリティドメインとは、クラウドインフラストラクチャーの中で完全に信頼できないエリアのことです。インターネット全体を指す場合や、単に権限を持たないネットワークを指す場合があります。機密性や完全性の要件を持つデータがこのドメインを通過する場合には、補完コントロールを使用してこのデータを保護する必要があります。"
+
+#: ./doc/security-guide/ch005_security-domains.xml38(para)
+msgid ""
+"This domain should always be considered <emphasis>untrusted</emphasis>."
+msgstr "このドメインは常に、<emphasis>信頼できない</emphasis>と考えなければなりません。 "
+
+#: ./doc/security-guide/ch005_security-domains.xml42(para)
+msgid ""
+"Typically used for compute instance-to-instance traffic, the guest security "
+"domain handles compute data generated by instances on the cloud but not "
+"services that support the operation of the cloud, such as API calls."
+msgstr "ゲストのセキュリティドメインは、Compute のインスタンス間通信に通常使用されますが、API の呼び出しなどクラウドのオペレーションをサポートするサービスではなく、クラウド上のインスタンスが生成する Compute データを処理します。"
+
+#: ./doc/security-guide/ch005_security-domains.xml43(para)
+msgid ""
+"Public cloud providers and private cloud providers who do not have stringent"
+" controls on instance use or who allow unrestricted internet access to VMs "
+"should consider this domain to be <emphasis>untrusted</emphasis>. Private "
+"cloud providers may want to consider this network as internal and therefore "
+"<emphasis>trusted</emphasis> only if they have controls in place to assert "
+"that they trust instances and all their tenants."
+msgstr "インスタンスの使用に関する厳密な制御がない、または制限なしに仮想マシンへインターネットアクセスが可能なパブリッククラウドのプロバイダーやプライベートクラウドのプロバイダーは、このドメインを <emphasis>untrusted</emphasis> であると見なすべきです。プライベートクライドプロバイダーは、インスタンスおよびすべてのテナントを確実に信頼できるように制御が設定されている場合のみ、このネットワークを内部、つまり <emphasis>trusted</emphasis> であると考えるようにしてください。"
+
+#: ./doc/security-guide/ch005_security-domains.xml47(para)
+msgid ""
+"The management security domain is where services interact. Sometimes "
+"referred to as the \"control plane\", the networks in this domain transport "
+"confidential data such as configuration parameters, usernames, and "
+"passwords. Command and Control traffic typically resides in this domain, "
+"which necessitates strong integrity requirements. Access to this domain "
+"should be highly restricted and monitored. At the same time, this domain "
+"should still employ all of the security best practices described in this "
+"guide."
+msgstr "管理セキュリティドメインは、サービスがやりとりをする場所です。このドメインは時に「コントロールプレーン」と呼ばれることもあり、このドメイン内のネットワークは設定パラメーター、ユーザー名、パスワードなどの機密データを送信します。コマンドやコントロールトラフィックは通常このドメインに常駐し、完全性に関する強い要件が必要となります。このドメインへのアクセスについては非常に制限されたものでなくてはならず、さらに監視も必要です。また、このセキュリティドメインでは、本ガイドで記載されているセキュリティのベストプラクティスすべてを採用するようにしてください。"
+
+#: ./doc/security-guide/ch005_security-domains.xml48(para)
+msgid ""
+"In most deployments this domain is considered <emphasis>trusted</emphasis>. "
+"However, when considering an OpenStack deployment, there are many systems "
+"that bridge this domain with others, potentially reducing the level of trust"
+" you can place on this domain. See <xref linkend=\"ch005_security-domains-"
+"idp61360\"/> for more information."
+msgstr "多くのデプロイメントでは、この管理セキュリティドメインは<emphasis>信頼できる</emphasis>と考えられています。しかし、OpenStack のデプロイメントの場合、このドメインと他のものをブリッジするシステムが多数あるため、このドメインの信頼レベルは下がります。詳細は、<xref linkend=\"ch005_security-domains-idp61360\"/>を参照してください。"
+
+#: ./doc/security-guide/ch005_security-domains.xml52(para)
+msgid ""
+"The data security domain is concerned primarily with information pertaining "
+"to the storage services within OpenStack. Much of the data that crosses this"
+" network has high integrity and confidentiality requirements and depending "
+"on the type of deployment there may also be strong availability "
+"requirements."
+msgstr "データセキュリティドメインは主に、OpenStack ではストレージサービスの情報に関係します。このネットワークを通過するデータの多くは、完全性や機密性に関する強い要件を持ち、デプロイメントの種類によっては強い可用性要件が出てくる場合があります。"
+
+#: ./doc/security-guide/ch005_security-domains.xml53(para)
+msgid ""
+"The trust level of this network is heavily dependent on deployment decisions"
+" and as such we do not assign this any default level of trust."
+msgstr "このネットワークの信頼レベルは、デプロイメントの意思決定により左右されるため、デフォルトの信頼レベルは割り当てていません。"
+
+#: ./doc/security-guide/ch005_security-domains.xml57(title)
+msgid "Bridging security domains"
+msgstr "セキュリティドメインのブリッジ"
+
+#: ./doc/security-guide/ch005_security-domains.xml58(para)
+msgid ""
+"A <emphasis>bridge</emphasis> is a component that exists inside more than "
+"one security domain. Any component that bridges security domains with "
+"different trust levels or authentication requirements must be carefully "
+"configured. These bridges are often the weak points in network architecture."
+" A bridge should always be configured to meet the security requirements of "
+"the highest trust level of any of the domains it is bridging. In many cases "
+"the security controls for bridges should be a primary concern due to the "
+"likelihood of attack."
+msgstr "<emphasis>ブリッジ</emphasis>とは、複数のセキュリティドメイン内に存在するコンポーネントです。異なる信頼レベルまたは認証要件が指定されたセキュリテイドメイン間をブリッジするコンポーネントは、慎重に設定する必要があります。ネットワークアーキテクチャの中で、これらのブリッジは弱点となることが多くなっています。常に、ブリッジするドメインの中で最も高い信頼レベルのセキュリティ要件を満たすように、ブリッジを設定するようにしてください。多くの場合、攻撃の可能性の高さから、主にブリッジのセキュリティ制御について考慮する必要があります。"
+
+#: ./doc/security-guide/ch005_security-domains.xml66(para)
+msgid ""
+"The diagram above shows a compute node bridging the data and management "
+"domains, as such the compute node should be configured to meet the security "
+"requirements of the management domain. Similarly the API Endpoint in this "
+"diagram is bridging the untrusted public domain and the management domain, "
+"and should be configured to protect against attacks from the public domain "
+"propagating through to the management domain."
+msgstr "上記の図は、データドメインと管理ドメインをブリッジするコンピュートノードです。このように、コンピュートノードは管理ドメインのセキュリティ要件に見合うように設定する必要があります。同様に、この図の API エンドポイントは信頼できないパブリックドメインと管理ドメインをブリッジしており、パブリックドメインから管理ドメインに伝搬しないように攻撃から保護されるように設定する必要があります。"
+
+#: ./doc/security-guide/ch005_security-domains.xml74(para)
+msgid ""
+"In some cases deployers may want to consider securing a bridge to a higher "
+"standard than any of the domains in which it resides. Given the above "
+"example of an API endpoint, an adversary could potentially target the API "
+"endpoint from the public domain, leveraging it in the hopes of compromising "
+"or gaining access to the management domain."
+msgstr "デプロイ担当者は、ブリッジするどのドメインよりも高い基準でブリッジのセキュリティを確保するように考えるようにしてください。API エンドポイントの上記の例では、攻撃者はパブリックドメインから API エンドポイントをターゲットにして、情報漏洩や管理ドメインへアクセス権の獲得を期待しつつこのエンドポイントを利用するのです。"
+
+#: ./doc/security-guide/ch005_security-domains.xml75(para)
+msgid ""
+"The design of OpenStack is such that separation of security domains is "
+"difficult - as core services will usually bridge at least two domains, "
+"special consideration must be given when applying security controls to them."
+msgstr "OpenStack のデザインではセキュリティドメインの分離が困難です。コアサービスは通常少なくとも 2 つのドメインをブリッジしているため、ドメインのセキュリティ制御を適用する場合、細心の注意を払う必要があります。"
+
+#: ./doc/security-guide/ch005_security-domains.xml78(title)
+msgid "Threat classification, actors and attack vectors"
+msgstr "脅威の分類、アクター、攻撃ベクトル"
+
+#: ./doc/security-guide/ch005_security-domains.xml79(para)
+msgid ""
+"Most types of cloud deployment, public or private, are exposed to some form "
+"of attack. In this chapter we categorize attackers and summarize potential "
+"types of attacks in each security domain."
+msgstr "クラウドデプロイメントの種類の多く (パブリックまたはプライベート) は、なんらかの攻撃にさらされています。本章では、攻撃者を分類して、各セキュリティドメインで考えられる攻撃の種類をまとめていきます。"
+
+#: ./doc/security-guide/ch005_security-domains.xml81(title)
+msgid "Threat actors"
+msgstr "脅威のアクター"
+
+#: ./doc/security-guide/ch005_security-domains.xml82(para)
+msgid ""
+"A threat actor is an abstract way to refer to a class of adversary that you "
+"may attempt to defend against. The more capable the actor, the more "
+"expensive the security controls that are required for successful attack "
+"mitigation and prevention. Security is a tradeoff between cost, usability "
+"and defense. In some cases it will not be possible to secure a cloud "
+"deployment against all of the threat actors we describe here. Those "
+"deploying an OpenStack cloud will have to decide where the balance lies for "
+"their deployment / usage."
+msgstr "脅威のアクターとは、防御の対象となりえる攻撃者のクラスを抽象的に表したものです。アクターの技術が高くなるにつれ、攻撃の軽減や防止を成功させるために必要なセキュリティ制御にかかるコストが嵩みます。セキュリティはコスト、使いやすさ、防御の間でのトレードオフということになります。ここで記載した脅威のアクターすべてから、クラウドのデプロイメントを保護することはできません。OpenStack クラウドをデプロイする方は、デプロイメントと用途の間でバランスが確保できるポイントを決定する必要が出てきます。"
+
+#: ./doc/security-guide/ch005_security-domains.xml92(para)
+msgid ""
+"<emphasis role=\"bold\">Intelligence services</emphasis> — Considered by "
+"this guide as the most capable adversary. Intelligence Services and other "
+"state actors can bring tremendous resources to bear on a target. They have "
+"capabilities beyond that of any other actor. It is very difficult to defend "
+"against these actors without incredibly stringent controls in place, both "
+"human and technical."
+msgstr "<emphasis role=\"bold\">インテリジェンスサービス</emphasis> — このガイドでは最も有能な攻撃者とされています。インテリジェンスサービスやその他の国家主体は、ターゲットに圧力をかけるために莫大なリソースを費やすことができます。他のどのアクターよりも能力があります。人や技術両方の面で非常に厳しい制御なしでは、これらのアクターから防御することは極めて困難です。"
+
+#: ./doc/security-guide/ch005_security-domains.xml102(para)
+msgid ""
+"<emphasis role=\"bold\">Serious organized crime</emphasis> — Highly capable "
+"and financially driven groups of attackers. Able to fund in-house exploit "
+"development and target research. In recent years the rise of organizations "
+"such as the Russian Business Network, a massive cyber-criminal enterprise "
+"has demonstrated how cyber attacks have become a commodity. Industrial "
+"espionage falls within the SOC group."
+msgstr "<emphasis role=\"bold\">重大組織犯罪</emphasis> — 極めて有能で金銭で動く攻撃者グループ。エクスポロイと開発やターゲットのリサーチに対する資金を組織内で調達できます。最近、ロシアンビジネスネットワーク (RBN) などの組織が登場し、大規模なサイバー犯罪企業がサイバー攻撃がどのようにして商品として成り立ったかを証明しました。産業スパイ活動は、SOC グループに分類されます。"
+
+#: ./doc/security-guide/ch005_security-domains.xml112(para)
+msgid ""
+"<emphasis role=\"bold\">Highly capable groups</emphasis> — This refers to "
+"'Hacktivist' type organizations who are not typically commercially funded "
+"but can pose a serious threat to service providers and cloud operators."
+msgstr "<emphasis role=\"bold\">非常に有能な組織</emphasis> — これは通常ビジネスから資金を調達しているのではありませんが、サービスプロバイダーやクラウドオペレーターに対して重大な脅威をもたらす可能性のある「ハクティビスト」タイプの組織のことを指します。"
+
+#: ./doc/security-guide/ch005_security-domains.xml119(para)
+msgid ""
+"<emphasis role=\"bold\">Motivated individuals</emphasis> — Acting alone, "
+"these attackers come in many guises, such as rogue or malicious employees, "
+"disaffected customers, or small-scale industrial espionage."
+msgstr "<emphasis role=\"bold\">動機のある個人</emphasis> — 一人で行動するこれらの攻撃者は、詐欺師または悪意のある従業員、不満を持った顧客、小規模の産業スパイなど多くのものに扮して攻撃します。"
+
+#: ./doc/security-guide/ch005_security-domains.xml126(para)
+msgid ""
+"<emphasis role=\"bold\">Script kiddies</emphasis> — Automated vulnerability "
+"scanning/exploitation. Non-targeted attacks. Often only a nuisance, "
+"compromise by one of these actors presents a major risk to an organization's"
+" reputation."
+msgstr "<emphasis role=\"bold\">スクリプトキディ</emphasis> — 自動化された脆弱性のスキャンやエクスプロイト。非標的型の攻撃。単なるいたずらの場合が多く、上記のアクターのいずれかによる情報漏洩により組織の評判に大きなリスクを与えます。"
+
+#: ./doc/security-guide/ch005_security-domains.xml142(title)
+msgid "Public and private cloud considerations"
+msgstr "パブリッククラウドとプライベートクラウドの考慮点"
+
+#: ./doc/security-guide/ch005_security-domains.xml143(para)
+msgid ""
+"Private clouds are typically deployed by enterprises or institutions inside "
+"their networks and behind their firewalls. Enterprises will have strict "
+"policies on what data is allowed to exit their network and may even have "
+"different clouds for specific purposes. Users of a private cloud are "
+"typically employees of the organization that owns the cloud and are able to "
+"be held accountable for their actions. Employees often attend training "
+"sessions before accessing the cloud and will likely take part in regular "
+"scheduled security awareness training. Public clouds by contrast cannot make"
+" any assertions about their users, cloud use-cases or user motivations. This"
+" immediately pushes the guest security domain into a completely "
+"<emphasis>untrusted</emphasis> state for public cloud providers."
+msgstr "通常プライベートクラウドは企業や組織により、内部のネットワークやファイアウォールの内側にデプロイされます。企業は、社内のネットワークから出すことのできるデータが何であるか、厳密な方針が設定されており、特定の目的ごとに別のクラウドを設定する場合さえもあります。プライベートクラウドのユーザーは通常、クラウドを所有して各自の行動に責任を課される組織内の従業員です。このような従業員は、クラウドにアクセスする前にトレーニングセッションに出席することもしばしばあり、定期的に予定されるセキュリティ認識トレーニングに参加する場合も多くあります。反対に、パブリッククラウドはユーザー、クラウドのユースケース、ユーザーの動機を断定することができません。このように、すぐにゲストのセキュリティドメインは、パブリッククラウドプロバイダーにとっては完全に <emphasis>untrusted</emphasis> な状態となります。"
+
+#: ./doc/security-guide/ch005_security-domains.xml144(para)
+msgid ""
+"A notable difference in the attack surface of public clouds is that they "
+"must provide internet access to their services. Instance connectivity, "
+"access to files over the internet and the ability to interact with the cloud"
+" controlling fabric such as the API endpoints and dashboard are must-haves "
+"for the public cloud."
+msgstr "パブリッククラウドの攻撃対象領域での顕著な相違点は、サービスに対してインターネットアクセスを提供しなければならない点です。API エンドポイントやダッシュボードなど、インスタンスの接続性、インターネット経由でのファイルアクセス、クラウド制御のファブリックとの対話機能は、パブリッククラウドで必須アイテムなのです。"
+
+#: ./doc/security-guide/ch005_security-domains.xml145(para)
+msgid ""
+"Privacy concerns for public and private cloud users are typically "
+"diametrically opposed. The data generated and stored in private clouds is "
+"normally owned by the operator of the cloud, who is able to deploy "
+"technologies such as data loss prevention (DLP) protection, file inspection,"
+" deep packet inspection and prescriptive firewalling. In contrast, privacy "
+"is one of the primary barriers to adoption for the public cloud, as many of "
+"these controls do not exist."
+msgstr "プライバシーの課題は、パブリッククラウドのユーザーとプライベートクラウドのユーザーとでは全く正反対になっています。プライベートクラウドで生成・格納されているデータは通常、データ損失防止 (DLP)、ファイルの検査、ディープパケットインスペクション、ルールベースのファイアウォールなどの技術をデプロイ可能なクラウドのオペレーターが所有します。反対に、パブリッククラウドには上記の様な制御の多くが存在しないため、プライバシーは、パブリッククラウドを採用する際の主な障害の 1 つとなっています。"
+
+#: ./doc/security-guide/ch005_security-domains.xml148(title)
+msgid "Outbound attacks and reputational risk"
+msgstr "アウトバウンド攻撃とレピュテーションリスク"
+
+#: ./doc/security-guide/ch005_security-domains.xml149(para)
+msgid ""
+"Careful consideration should be given to potential outbound abuse from a "
+"cloud deployment. Whether public or private, clouds tend to have lots of "
+"resource available. An attacker who has established a point of presence "
+"within the cloud, either through hacking or entitled access, such as rogue "
+"employee, can bring these resources to bear against the internet at large. "
+"Clouds with Compute services make for ideal DDoS and brute force engines. "
+"The issue is more pressing for public clouds as their users are largely "
+"unaccountable, and can quickly spin up numerous disposable instances for "
+"outbound attacks. Major damage can be inflicted upon a company's reputation "
+"if it becomes known for hosting malicious software or launching attacks on "
+"other networks. Methods of prevention include egress security groups, "
+"outbound traffic inspection, customer education and awareness, and fraud and"
+" abuse mitigation strategies."
+msgstr "クラウドデプロイメントからアウトバウンド方向で起こりえる不正使用に対して、十分な配慮が必要です。パブリックでも、プライベートでも、クラウドは多くのリソースが使用出来る状態になっている傾向にあります。悪意のある従業員など、ハッキングや与えられているアクセス権限のいずれかによりクラウド内に攻撃ポイントを設定した攻撃者は、これらのリソースにインターネット全体の負荷をかけることができます。Compute サービスがあるクラウドは、理想的な DDoS や総当り攻撃エンジンを作り出します。パブリッククラウドのユーザーは多くの場合、責任を負う必要がなく、自由に使用できるインスタンスをすぐにアウトバウンドの攻撃として作り出すことができるため、パブリッククラウドにとっては、この点はより差し迫った課題でしょう。悪意のあるソフトウェアをホストしたり、他のネットワークへ攻撃していたりしたことが判明すると、企業の評判に大きな打撃を与えることでしょう。防止の方法には、egress セキュリティグループ、アウトバウンドトラフィックの検査、顧客の教育・認識、詐欺や悪用軽減戦略などがあります。"
+
+#: ./doc/security-guide/ch005_security-domains.xml168(title)
+msgid "Attack types"
+msgstr "攻撃の種類"
+
+#: ./doc/security-guide/ch005_security-domains.xml169(para)
+msgid ""
+"The diagram shows the types of attacks that may be expected from the actors "
+"described in the previous section. Note that there will always be exceptions"
+" to this diagram but in general, this describes the sorts of attack that "
+"could be typical for each actor."
+msgstr "以下の図は、前項で説明したアクターから出される可能性のある攻撃の種類を記載しています。このような図では常に例外が存在しますが、アクター毎に典型的であると考えられる攻撃の種類を一般論として記述しています。"
+
+#: ./doc/security-guide/ch005_security-domains.xml177(para)
+msgid ""
+"The prescriptive defense for each form of attack is beyond the scope of this"
+" document. The above diagram can assist you in making an informed decision "
+"about which types of threats, and threat actors, should be protected "
+"against. For commercial public cloud deployments this might include "
+"prevention against serious crime. For those deploying private clouds for "
+"government use, more stringent protective mechanisms should be in place, "
+"including carefully protected facilities and supply chains. In contrast "
+"those standing up basic development or test environments will likely require"
+" less restrictive controls (middle of the spectrum)."
+msgstr "攻撃の形式ごとの規範的な防御については、本書の対象範囲外となっています。上記の図は、対策を行うべき脅威の種類、脅威のアクターについて詳細な情報を得た状態で意思決定ができるように支援します。商業的なパブリッククラウドのデプロイに関しては重大な犯罪の防止などが含まれる場合があります。 政府で使用するプライベートクラウドをデプロイする方は、細心の注意を払って設置された対策施設やサプライチェーンなど、より厳密な保護メカニズムを設置する必要があります。反対に、基本的なデプロイメントやテスト環境を設定する方は、制御に関する制約が少なくて済むでしょう。"
+
 #: ./doc/security-guide/ch061_compliance-overview.xml8(title)
 msgid "Compliance overview"
 msgstr "コンプライアンス概要"
@@ -3009,1161 +8408,63 @@ msgid ""
 " records in most countries."
 msgstr "適切なロギングは、不正利用の監視や障害対応、証拠収集に役立ちます。多くの国において、それを再度証明する必要が無い、Common Criteria認定をうけた監査サブシステムの採用を強くおすすめします。"
 
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml8(title)
-msgid "Certification and compliance statements"
-msgstr "認証とコンプライアンスの報告書"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml9(para)
-msgid ""
-"Compliance and security are not exclusive, and must be addressed together. "
-"OpenStack deployments are unlikely to satisfy compliance requirements "
-"without security hardening. The listing below provides an OpenStack "
-"architect foundational knowledge and guidance to achieve compliance against "
-"commercial and government certifications and standards."
-msgstr "コンプライアンスとセキュリティは排他的でなく、あわせて取り組むべきものです。OpenStack環境は、セキュリティの強化なしに、コンプライアンス要件を充足することができないでしょう。以下のリストは、OpenStackアーキテクト向けの、商業規格および政府機関の認証を得るための基本的な知識とガイダンスです。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml17(title)
-msgid "Commercial standards"
-msgstr "商業規格"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml18(para)
-msgid ""
-"For commercial deployments of OpenStack, it is recommended that SOC 1/2 "
-"combined with ISO 2700 1/2 be considered as a starting point for OpenStack "
-"certification activities. The required security activities mandated by these"
-" certifications facilitate a foundation of security best practices and "
-"common control criteria that can assist in achieving more stringent "
-"compliance activities, including government attestations and certifications."
-msgstr "OpenStackの商用環境向けには、まずは開始点として、SOC 1/2とISO 27001/2の検討を推奨します。そこで要求されるセキュリティ活動を確実に実行することで、セキュリティのベストプラクティスと共通統制基準を導入を促進し、政府系認定などの、より厳格なコンプライアンス活動の取得にも役立ちます。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml26(para)
-msgid ""
-"After completing these initial certifications, the remaining certifications "
-"are more deployment specific. For example, clouds processing credit card "
-"transactions will need PCI-DSS, clouds storing health care information "
-"require HIPAA, and clouds within the federal government may require "
-"FedRAMP/FISMA, and ITAR, certifications."
-msgstr "これらの基本的認証を取得したのち、より環境特有の認証を検討します。たとえば、クラウドがクレジットカードのトランザクションを扱うのであればPCI-DSSが必要ですし、ヘルスケア情報を保持するならHIPPAが、連邦政府向けにはFedRAMP/FISMA、ITAR認証が必要となるでしょう。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml34(title)
-msgid "SOC 1 (SSAE 16) / ISAE 3402"
-msgstr "SOC 1 (SSAE 16) / ISAE 3402"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml35(para)
-msgid ""
-"Service Organization Controls (SOC) criteria are defined by the <link "
-"href=\"http://www.aicpa.org/\">American Institute of Certified Public "
-"Accountants</link> (AICPA). SOC controls assess relevant financial "
-"statements and assertions of a service provider, such as compliance with the"
-" Sarbanes-Oxley Act. SOC 1 is a replacement for Statement on Auditing "
-"Standards No. 70 (SAS 70) Type II report. These controls commonly include "
-"physical data centers in scope."
-msgstr "Service Organization Controls (SOC)基準は米国公認会計士協会 - <link href=\"http://www.aicpa.org/\">American Institute of Certified Public Accountants</link> (AICPA)によって定められています。SOC統制はサービスプロバイダーの関連財務諸表と主張を評価します。例えばSarbanes-Oxley法への準拠などです。SOC 1 はStatement on Auditing Standards No. 70 (SAS 70) Type II 報告書を代替します。これらの統制は物理的なデータセンターを評価範囲に含みます。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml44(para)
-msgid "There are two types of SOC 1 reports:"
-msgstr "SOC 1報告書には二つの種類があります。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml47(para)
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml84(para)
-msgid ""
-"Type 1 – report on the fairness of the presentation of management's "
-"description of the service organization's system and the suitability of the "
-"design of the controls to achieve the related control objectives included in"
-" the description as of a specified date."
-msgstr "Type 1 - サービス提供組織がその管理について説明し、その公正さをレポートします。特定時点で関連する管理対象を統制できているか、その設計の持続可能性も報告します。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml54(para)
-msgid ""
-"Type 2 – report on the fairness of the presentation of management's "
-"description of the service organization's system and the suitability of the "
-"design and operating effectiveness of the controls to achieve the related "
-"control objectives included in the description throughout a specified period"
-msgstr "Type 2 - サービス組織が統制対象を統制するために使用するシステム、設計の持続性、および運用効率性に関する管理者の説明内容が公正かをレポートします。特定期間を通しての説明も必要です。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml62(para)
-msgid ""
-"For more details see the <link "
-"href=\"http://www.aicpa.org/InterestAreas/FRC/AssuranceAdvisoryServices/Pages/AICPASOC1Report.aspx\">AICPA"
-" Report on Controls at a Service Organization Relevant to User Entities’ "
-"Internal Control over Financial Reporting</link>."
-msgstr "詳細は<link href=\"http://www.aicpa.org/InterestAreas/FRC/AssuranceAdvisoryServices/Pages/AICPASOC1Report.aspx\">AICPA Report on Controls at a Service Organization Relevant to User Entities’ Internal Control over Financial Reporting</link>を参照してください。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml70(title)
-msgid "SOC 2"
-msgstr "SOC 2"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml71(para)
-msgid ""
-"Service Organization Controls (SOC) 2 is a self attestation of controls that"
-" affect the security, availability, and processing integrity of the systems "
-"a service organization uses to process users' data and the confidentiality "
-"and privacy of information processed by these system. Examples of users are "
-"those responsible for governance of the service organization; customers of "
-"the service organization; regulators; business partners; suppliers and "
-"others who have an understanding of the service organization and its "
-"controls."
-msgstr "Service Organization Controls (SOC) 2は、サービス提供組織がユーザーデータとその情報の機密性とプライバシーを制御するために使っているシステムのセキュリティ、可用性、および処理の完全性に関する統制の自己証明です。ユーザーの例は、サービス組織を統制する人、サービス組織の顧客、監視当局、ビジネスパートナー、サプライヤー、およびサービス組織の理解者やそれを統制する人です。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml81(para)
-msgid "There are two types of SOC 2 reports:"
-msgstr "SOC 2報告書には二つの種類があります。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml91(para)
-msgid ""
-"Type 2 – report on the fairness of the presentation of management's "
-"description of the service organization's system and the suitability of the "
-"design and operating effectiveness of the controls to achieve the related "
-"control objectives included in the description throughout a specified "
-"period."
-msgstr "Type 2 - サービス組織が統制対象を統制するために使用するシステム、設計の持続性、および運用効率性に関する管理者の説明内容が公正かをレポートします。特定期間を通しての説明も必要です。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml99(para)
-msgid ""
-"For more details see the <link "
-"href=\"http://www.aicpa.org/InterestAreas/FRC/AssuranceAdvisoryServices/Pages/AICPASOC2Report.aspx\">AICPA"
-" Report on Controls at a Service Organization Relevant to Security, "
-"Availability, Processing Integrity, Confidentiality or Privacy</link>."
-msgstr "詳細は<link href=\"http://www.aicpa.org/InterestAreas/FRC/AssuranceAdvisoryServices/Pages/AICPASOC2Report.aspx\">AICPA Report on Controls at a Service Organization Relevant to Security, Availability, Processing Integrity, Confidentiality or Privacy</link>を参照してください。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml108(title)
-msgid "SOC 3"
-msgstr "SOC 3"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml109(para)
-msgid ""
-"Service Organization Controls (SOC) 3 is a trust services report for service"
-" organizations. These reports are designed to meet the needs of users who "
-"want assurance on the controls at a service organization related to "
-"security, availability, processing integrity, confidentiality, or privacy "
-"but do not have the need for or the knowledge necessary to make effective "
-"use of a SOC 2 Report. These reports are prepared using the AICPA/Canadian "
-"Institute of Chartered Accountants (CICA) Trust Services Principles, "
-"Criteria, and Illustrations for Security, Availability, Processing "
-"Integrity, Confidentiality, and Privacy. Because they are general use "
-"reports, SOC 3 Reports can be freely distributed or posted on a website as a"
-" seal."
-msgstr "Service Organization Controls (SOC) 3はサービス提供組織のための公的なサービス報告書です。これらのレポートはサービス組織のセキュリティ、可用性、処理の完全性、機密性、またはプライバシーに関する統制の保証を求めるユーザーニーズを満たすためのレポートです。ただし、SOC 2報告書ほどの情報は必要ありません。SOC 3報告書はAICPA/Canadian Institute of Chartered Accountants (CICA)のTrust Services Principles, Criteria, and Illustrations for Security, Availability, Processing Integrity, Confidentiality, and Privacyをもって作成されています。SOC 3は一般的に使われる報告書であり、Webサイト上で証明書として自由に配布できます。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml121(para)
-msgid ""
-"For more details see the <link "
-"href=\"http://www.aicpa.org/InterestAreas/FRC/AssuranceAdvisoryServices/Pages/AICPASOC3Report.aspx\">AICPA"
-" Trust Services Report for Service Organizations</link>."
-msgstr "詳細は<link href=\"http://www.aicpa.org/InterestAreas/FRC/AssuranceAdvisoryServices/Pages/AICPASOC3Report.aspx\">AICPA Trust Services Report for Service Organizations</link>を参照してください。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml128(title)
-msgid "ISO 27001/2"
-msgstr "ISO 27001/2"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml129(para)
-msgid ""
-"The ISO/IEC 27001/2 standards replace BS7799-2, and are specifications for "
-"an Information Security Management System (ISMS). An ISMS is a comprehensive"
-" set of policies and processes that an organization creates and maintains to"
-" manage risk to information assets. These risks are based upon the "
-"confidentiality, integrity, and availability (CIA) of user information. The "
-"CIA security triad has been used as a foundation for much of the chapters in"
-" this book."
-msgstr "ISO/IEC 27001/2はBS7799-2の後継標準で、Information Security Management System (ISMS)の要件です。ISMSは組織が情報資産のリスクを管理するために作成、維持する、ポリシーとプロセスの包括的なセットです。それらのリスクはユーザー情報のConfidentiality - 機密性、Integrity - 完全性、および Availability - 可用性 (CIA)に深く関係しています。CIAセキュリティの三要素は、このガイドの多くの章で基本となっています。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml137(para)
-msgid ""
-"For more details see <link href=\"http://www.27000.org/iso-27001.htm\">ISO "
-"27001</link>."
-msgstr "詳細は<link href=\"http://www.27000.org/iso-27001.htm\">ISO 27001</link>を参照してください。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml143(title)
-msgid "HIPAA / HITECH"
-msgstr "HIPAA / HITECH"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml144(para)
-msgid ""
-"The Health Insurance Portability and Accountability Act (HIPAA) is a United "
-"States congressional act that governs the collection, storage, use and "
-"destruction of patient health records. The act states that Protected Health "
-"Information (PHI) must be rendered \"unusable, unreadable, or "
-"indecipherable\" to unauthorized persons and that encryption for data 'at-"
-"rest' and 'inflight' should be addressed."
-msgstr "Health Insurance Portability and Accountability Act (HIPAA)は米国の健康保険における可搬性と責任に関する法律で、カルテ情報の収集、保存、および廃棄に関するルールを定めています。この法律は、保護医療情報 (Protected Health Information, PHI)は、権限のない人が\"利用できない、読めない、複合できない\"ように変換されなければいけないこと、また、データが保存中でも、処理中でも、暗号化するべきであることに言及しています。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml151(para)
-msgid ""
-"HIPAA is not a certification, rather a guide for protecting healthcare data."
-" Similar to the PCI-DSS, the most important issues with both PCI and HIPPA "
-"is that a breach of credit card information, and health data, does not "
-"occur. In the instance of a breach the cloud provider will be scrutinized "
-"for compliance with PCI and HIPPA controls. If proven compliant, the "
-"provider can be expected to immediately implement remedial controls, breach "
-"notification responsibilities, and significant expenditure on additional "
-"compliance activities. If not compliant, the cloud provider can expect on-"
-"site audit teams, fines, potential loss of merchant ID (PCI), and massive "
-"reputation impact."
-msgstr "HIPPAは認証ではなく、カルテ情報の保護に関するガイドラインです。PCI-DSSと似ています。PCIとHIPAAの両方でもっとも重要な課題は、クレジットカード情報とカルテ情報が流出しないようにすることです。クラウドプロバイダーによる流出があった場合、PCIとHIPAAの統制下において検査されます。その内容が遵守に足るものであれば、そのプロバイダーはすみやかに是正措置の実行と情報流出の通知、およびコンプライアンス活動予算の大幅な追加を期待されます。もし足るものでなければ、現地での査察、罰金、merchant ID (PCI)の失効、および評判に大きな傷がつくことが予想されます。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml163(para)
-msgid ""
-"Users or organizations that possess PHI must support HIPAA requirements and "
-"are HIPAA covered entities. If an entity intends to use a service, or in "
-"this case, an OpenStack cloud that might use, store or have access to that "
-"PHI, then a Business Associate Agreement must be signed. The BAA is a "
-"contract between the HIPAA covered entity and the OpenStack service provider"
-" that requires the provider to handle that PHI in accordance with HIPAA "
-"requirements. If the service provider does not handle the PHI, such as with "
-"security controls and hardening, then they are subject to HIPAA fines and "
-"penalties."
-msgstr "カルテ情報を所有するユーザーや組織はHIPPAの要件をサポートし、HIPAA対象事業者となる必要があります。もしこの事業者がサービスを、この場合は対象のOpenStackクラウドがカルテ情報を利用、保存、アクセスしうるのであれば、HIPAA Business Associate Agreement - BAAの締結が必要です。BAAはHIPAA対象事業者と、HIPAA要件に従ってカルテ情報を扱っているOpenStackサービスプロバイダーの間で締結されます。もしサービスプロバイダーがセキュリティ統制、強化を怠るなど、カルテ情報を要件通りに扱っていなければHIPAAの罰金や罰則が適用されることがあります。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml174(para)
-msgid ""
-"OpenStack architects interpret and respond to HIPAA statements, with data "
-"encryption remaining a core practice. Currently this would require any "
-"protected health information contained within an OpenStack deployment to be "
-"encrypted with industry standard encryption algorithms. Potential future "
-"OpenStack projects such as object encryption will facilitate HIPAA "
-"guidelines for compliance with the act."
-msgstr "OpenStackアーキテクトはHIPAAの条項を解釈し、対応します。データ暗号化はその中核となる活動です。現在、OpenStack環境に保存される、いかなる保護カルテ情報にも暗号化を要求され、業界標準の暗号化アルゴリズムの採用が期待されます。なお、将来予定されている、例えばオブジェクト暗号化などのOpenStackプロジェクトは、法令遵守のためHPAAガイドラインの適用を促進するでしょう。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml181(para)
-msgid ""
-"For more details see the <link href=\"https://www.cms.gov/Regulations-and-"
-"Guidance/HIPAA-Administrative-"
-"Simplification/HIPAAGenInfo/downloads/HIPAALaw.pdf\">Health Insurance "
-"Portability And Accountability Act</link>."
-msgstr "詳細は<link href=\"https://www.cms.gov/Regulations-and-Guidance/HIPAA-Administrative-Simplification/HIPAAGenInfo/downloads/HIPAALaw.pdf\">Health Insurance Portability And Accountability Act</link>を参照してください。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml187(title)
-msgid "PCI-DSS"
-msgstr "PCI-DSS"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml188(para)
-msgid ""
-"The Payment Card Industry Data Security Standard (PCI DSS) is defined by the"
-" Payment Card Industry Standards Council, and created to increase controls "
-"around card holder data to reduce credit card fraud. Annual compliance "
-"validation is assessed by an external Qualified Security Assessor (QSA) who "
-"creates a Report on Compliance (ROC), or by a Self-Assessment Questionnaire "
-"(SAQ) dependent on volume of card-holder transactions."
-msgstr "Payment Card Industry Data Security Standard (PCI DSS)はPayment Card Industry Standards Councilで定義されました。目的は、クレジットカード不正の防止のため、カード所有者情報に関する統制度を向上することです。コンプライアンス検査は年次で、外部のコンプライアンス評価報告書(Report on Compliance, ROC)を作成する認定評価機関 (Qualified Security Assessor, QSA)、もしくは、自己評価問診票(Self-Assessment Questionnaire, SAQ)によって実施されます。これはカード所有者のトランザクション量に依存します。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml196(para)
-msgid ""
-"OpenStack deployments which stores, processes, or transmits payment card "
-"details are in scope for the PCI-DSS. All OpenStack components that are not "
-"properly segmented from systems or networks that handle payment data fall "
-"under the guidelines of the PCI-DSS. Segmentation in the context of PCI-DSS "
-"does not support multi-tenancy, but rather physical separation "
-"(host/network)."
-msgstr "カード情報を保存、処理、転送するOpenStack環境は、PCI-DSSの対象です。カード情報を扱うシステムやネットワークが正しく分離されていないすべてのOpenStackコンポーネントは、PCI-DSSのガイドラインに適合しません。PCI-DSSでいう分離は、マルチ手ナンシーを認めておらず、(サーバーおよびネットワークの)物理的な分離が必要です。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml203(para)
-msgid ""
-"For more details see <link "
-"href=\"https://www.pcisecuritystandards.org/security_standards/\">PCI "
-"security standards</link>."
-msgstr "詳細は<link href=\"https://www.pcisecuritystandards.org/security_standards/\">PCI security standards</link>を参照してください。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml209(title)
-msgid "Government standards"
-msgstr "政府標準"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml212(title)
-msgid "FedRAMP"
-msgstr "FedRAMP"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml213(para)
-msgid ""
-"\"The <link href=\"http://www.fedramp.gov\">Federal Risk and Authorization "
-"Management Program</link> (FedRAMP) is a government-wide program that "
-"provides a standardized approach to security assessment, authorization, and "
-"continuous monitoring for cloud products and services\". NIST 800-53 is the "
-"basis for both FISMA and FedRAMP which mandates security controls "
-"specifically selected to provide protection in cloud environments. FedRAMP "
-"can be extremely intensive from specificity around security controls, and "
-"the volume of documentation required to meet government standards."
-msgstr "\"<link href=\"http://www.fedramp.gov\">Federal Risk and Authorization Management Program</link> (FedRAMP)は米国連邦政府全体のプログラムであり、クラウド製品とサービスのセキュリティ評価、認証、および継続的モニタリングの、標準化された手順を提供します\" NIST 800-53はFISMAとRedRAMPの両方の基礎であり、特にクラウド環境における保護を提供するために選択されたセキュリティ統制を強制します。セキュリティ統制に関する具体性と政府標準を満たすための文書量を、FedRAMPは徹底しています。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml223(para)
-msgid ""
-"For more details see <link "
-"href=\"http://www.gsa.gov/portal/category/102371\">http://www.gsa.gov/portal/category/102371</link>."
-msgstr "詳細は<link href=\"http://www.gsa.gov/portal/category/102371\">http://www.gsa.gov/portal/category/102371</link>を参照してください。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml229(title)
-msgid "ITAR"
-msgstr "ITAR"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml230(para)
-msgid ""
-"The International Traffic in Arms Regulations (ITAR) is a set of United "
-"States government regulations that control the export and import of defense-"
-"related articles and services on the United States Munitions List (USML) and"
-" related technical data. ITAR is often approached by cloud providers as an "
-"\"operational alignment\" rather than a formal certification. This typically"
-" involves implementing a segregated cloud environment following practices "
-"based on the NIST 800-53 framework, as per FISMA requirements, complemented "
-"with additional controls restricting access to \"U.S. Persons\" only and "
-"background screening."
-msgstr "International Traffic in Arms Regulations (ITAR)は米国政府規制の集合であり、米国軍需品リスト(United States Munitions List, USML)と関連技術情報に関係する防衛物品・サービスの輸出入を統制します。ITARは正式な認証というより、\"軍事活動支援\"の位置づけでクラウドプロバイダーから提示されます。この統制は一般的に、NIST 800-53フレームワークにもとづき、分離されたクラウド環境の実装を意味します。FISMA要件により、米国民かつ身元審査された人のみがアクセスできるよう、追加の統制で補完します。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml241(para)
-msgid ""
-"For more details see <link "
-"href=\"http://pmddtc.state.gov/regulations_laws/itar_official.html\">http://pmddtc.state.gov/regulations_laws/itar_official.html</link>."
-msgstr "詳細は<link href=\"http://pmddtc.state.gov/regulations_laws/itar_official.html\">http://pmddtc.state.gov/regulations_laws/itar_official.html</link>を参照してください。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml247(title)
-msgid "FISMA"
-msgstr "FISMA"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml248(para)
-msgid ""
-"The Federal Information Security Management Act requires that government "
-"agencies create a comprehensive plan to implement numerous government "
-"security standards, and was enacted within the E-Government Act of 2002. "
-"FISMA outlines a process, which utilizing multiple NIST publications, "
-"prepares an information system to store and process government data."
-msgstr "米国連邦情報セキュリティマネジメント法 - Federal Information Security Management Act requires、FISMAは、政府機関は多数の政府セキュリティ標準を実装するために、包括的な計画を作成する必要があるとして、2002年 電子政府法 - E-Government Act of 2002 内で制定されました。FISMAは多数のNIST公表文献を活用し、政府のデータを保存、処理する情報システムを作成するためのプロセスを説明しています。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml255(para)
-msgid "This process is broken apart into three primary categories:"
-msgstr "このプロセスは三つの主要カテゴリに分割されています。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml259(para)
-msgid ""
-"<emphasis role=\"bold\">System categorization:</emphasis> The information "
-"system will receive a security category as defined in Federal Information "
-"Processing Standards Publication 199 (FIPS 199). These categories reflect "
-"the potential impact of system compromise."
-msgstr "<emphasis role=\"bold\">システムのカテゴリ分け</emphasis> 情報システムは連邦情報処理規格( Federal Information Processing Standards Publication 199, FIPS 199)で定められたセキュリティカテゴリに分類されます。これらのカテゴリはシステムの情報漏洩の潜在的な影響を反映しています。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml267(para)
-msgid ""
-"<emphasis role=\"bold\">Control selection:</emphasis>Based upon system "
-"security category as defined in FIPS 199, an organization utilizes FIPS 200 "
-"to identify specific security control requirements for the information "
-"system. For example, if a system is categorized as “moderate” a requirement "
-"may be introduced to mandate “secure passwords.”"
-msgstr "<emphasis role=\"bold\">統制の選択</emphasis> FIPS 199で定められたシステムセキュリティのカテゴリにもとづき、組織は情報システムのための特定のセキュリティ統制要求を特定すべく、FIPS 200を活用します 。たとえば、もしシステムが\"中程度\"と分類されているのであれば、安全なパスワードの強制が求められるでしょう。"
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml276(para)
-msgid ""
-"<emphasis role=\"bold\">Control tailoring:</emphasis> Once system security "
-"controls are identified, an OpenStack architect will utilize NIST 800-53 to "
-"extract tailored control selection. For example, specification of what "
-"constitutes a “secure password.”"
-msgstr "<emphasis role=\"bold\">統制の適用</emphasis> システムのセキュリティが特定されれば、OpenStackアーキテクトは選択した統制を適用するために、NIST 800-53を活用します。たとえば、安全なパスワードの構成を仕様化するなど。"
-
-#: ./doc/security-guide/ch039_case-studies-messaging.xml8(title)
-msgid "Case studies: messaging"
-msgstr "ケーススタディ: メッセージング"
-
-#: ./doc/security-guide/ch039_case-studies-messaging.xml9(para)
-msgid ""
-"The message queue is a critical piece of infrastructure that supports a "
-"number of OpenStack services but is most strongly associated with the "
-"Compute service. Due to the nature of the message queue service, Alice and "
-"Bob have similar security concerns. One of the larger concerns that remains "
-"is that many systems have access to this queue and there is no way for a "
-"consumer of the queue messages to verify which host or service placed the "
-"messages on the queue. An attacker who is able to successfully place "
-"messages on the queue is able to create and delete VM instances, attach the "
-"block storage of any tenant and a myriad of other malicious actions. There "
-"are a number of solutions on the horizon to fix this, with several proposals"
-" for message signing and encryption making their way through the OpenStack "
-"development process."
-msgstr "メッセージキューは、多数の OpenStack サービスを支える重要なインフラストラクチャであり、特にコンピュートサービスと強く結びついています。メッセージキューサービスの性質上、アリスとボブが抱えるセキュリティ上の懸念はよく似ています。特に大きな残課題は、数多くのシステムがキューにアクセスしているものの、キューメッセージのコンシューマーには、キューを発行したホストやサービスを確かめる手立てがないことです。攻撃者がキューの発行に成功すると、仮想マシンの作成や削除をしたり、あらゆるテナントのブロックストレージに接続するなど、他にも無数の悪意のある攻撃が可能になってしまいます。\nこれを防ぐためのソリューションが出始めており、いくつかはメッセージへの署名と暗号化を使ったものが OpenStack の開発プロセスで進んでいます。"
-
-#: ./doc/security-guide/ch039_case-studies-messaging.xml12(para)
-msgid ""
-"In this case Alice's controls mimic those Bob has deployed for the public "
-"cloud."
-msgstr "このケースでは、アリスの方法はボブがパブリッククラウドに展開した方法と同じものを使用します。"
-
-#: ./doc/security-guide/ch039_case-studies-messaging.xml16(para)
-msgid ""
-"Bob assumes that at some point infrastructure or networks underpinning the "
-"Compute service may become compromised. Due to this, he recognizes the "
-"importance of locking down access to the message queue. To do this Bob "
-"deploys his RabbitMQ servers with SSL and X.509 client auth for access "
-"control. This in turn limits the capabilities of an attacker who has "
-"compromised a system that does not have queue access."
-msgstr "ボブは、コンピュートサービスを支えるインフラストラクチャとネットワークがある時点でセキュリティ侵害に会うと仮定します。そして、メッセージキューへのアクセス制限の重要性に気づきました。\nそこで、RabbitMQ サーバーに SSL と X.509 クライアントアクセス制御を適用することにします。これにより、キューアクセスを持たないシステムを乗っ取られても、攻撃者の能力を制限することができます。"
-
-#: ./doc/security-guide/ch039_case-studies-messaging.xml17(para)
-msgid ""
-"Additionally, Bob adds strong network ACL rulesets to enforce which "
-"endpoints can communicate with the message servers. This second control "
-"provides some additional assurance should the other protections fail."
-msgstr "さらにボブは、メッセージサーバーと通信できるエンドポイントを、強力なネットワークの ACL ルールセットで制限することにしました。この2個目の制限が、他の防御が失敗した場合の保険として機能します。"
-
-#: ./doc/security-guide/ch066_case-studies-compliance.xml8(title)
-msgid "Case studies: compliance"
-msgstr "ケーススタディ: コンプライアンス"
-
-#: ./doc/security-guide/ch066_case-studies-compliance.xml9(para)
-msgid ""
-"In this case study we discuss how Alice and Bob would address common "
-"compliance requirements. The preceding chapter refers to a wide variety of "
-"compliance certifications and standards. Alice will address compliance in a "
-"private cloud, while Bob will be focused on compliance for a public cloud."
-msgstr "このケーススタディでは、アリスとボブがどのように一般的なコンプライアンス要件に対応するかを説明します。これまでの章で、さまざまなコンプライアンス認証と標準について言及しました。アリスはプライベートクラウドでコンプライアンスに取り組み、いっぽうボブはパブリッククラウド向けのコンプライアンスに注力します。"
-
-#: ./doc/security-guide/ch066_case-studies-compliance.xml12(para)
-msgid ""
-"Alice is building an OpenStack private cloud for the United States "
-"government, specifically to provide elastic compute environments for signal "
-"processing. Alice has researched government compliance requirements, and has"
-" identified that her private cloud will be required to certify against FISMA"
-" and follow the FedRAMP accreditation process, which is required for all "
-"federal agencies, departments and contractors to become a Certified Cloud "
-"Provider (CCP). In this particular scenario for signal processing, the FISMA"
-" controls required will most likely be FISMA High, which indicates possible "
-"\"severe or catastrophic adverse effects\" should the information system "
-"become compromised. In addition to FISMA Moderate controls Alice must ensure"
-" her private cloud is FedRAMP certified, as this is a requirement for all "
-"agencies that currently utilize, or host federal information within a cloud "
-"environment."
-msgstr "アリスはOpenStackプライベートクラウドを米国政府向けに構築しています。具体的には、信号処理向けの柔軟なコンピューティング環境です。アリスは政府向けコンプライアンス要件を調査した結果、これから構築しようとしているプライベートクラウドはFISMAおよびFedRAMP認定が必要であると判断しました。これは政府系機関、行政部、および契約者、どのような立場であっても、認定クラウドプロバイダー(Certified Cloud Provider, CCP)になるために必要な手続きです。特に信号処理は、FISMAはそれを\"深刻で壊滅的な影響\"をシステムに与えうるとしているため、FISMA影響度が\"高\"となりがちです。加えてFISMA Moderateレベルにおいて、アリスはそのプライベートクラウドを確実にFedRAMP認証としなければいけません。これはクラウド内に政府の情報を保有する、全ての機関に求められてる条件です。"
-
-#: ./doc/security-guide/ch066_case-studies-compliance.xml13(para)
-msgid ""
-"To meet these strict government regulations Alice undertakes a number of "
-"activities. Scoping of requirements is particularly important due to the "
-"volume of controls that must be implemented, which will be defined in NIST "
-"Publication 800-53."
-msgstr "これらの厳しい政府規制の要件を満たすため、アリスは多くの活動を行います。範囲の決定作業は、実装すべき統制の量に影響するため、特に重要です。これはNIST刊行 800-53で定められています。"
-
-#: ./doc/security-guide/ch066_case-studies-compliance.xml14(para)
-msgid ""
-"All technology within her private cloud must be FIPS certified technology, "
-"as mandated within NIST 800-53 and FedRAMP. As the U.S. Department of "
-"Defense is involved, Security Technical Implementation Guides (STIGs) will "
-"come into play, which are the configuration standards for DOD IA and IA-"
-"enabled devices / systems. Alice notices a number of complications here as "
-"there is no STIG for OpenStack, so she must address several underlying "
-"requirements for each OpenStack service; for example, the networking SRG and"
-" Application SRG will both be applicable (<link "
-"href=\"http://iase.disa.mil/srgs/index.html\">list of SRGs</link>). Other "
-"critical controls include ensuring that all identities in the cloud use PKI,"
-" that SELinux is enabled, that encryption exists for all wire-level "
-"communications, and that continuous monitoring is in place and clearly "
-"documented. Alice is not concerned with object encryption, as this will be "
-"the tenants responsibility rather than the provider."
-msgstr "彼女のプライベートクラウドで使われる全ての技術は、NIST 800-53とFedRAMPに従い、FIPS認証技術であることが求められます。米国国防省が関わる場合、国防省のIA - Information AssuranceおよびIA-enabled対象機器/システムの構成標準であるSecurity Technical Implementation Guides (STIGs) も関係します。OpenStack向けのSTIGが無くとも、アリスはさまざまな要素を考慮し、各OpenStackサービス毎に、いくつかの潜在的な要件を考慮しなければいけません。例えば、networking SRG - Security Requirements GuidesとApplication SRGはどちらも対象です(<link href=\"http://iase.disa.mil/srgs/index.html\">list of SRGs</link>)。他の重要な統制として、クラウド内の全てのIDではPKIが使われ、SELinuxが有効であり、すべての全ての通信経路が暗号化でき、持続的に監視が行われ、かつ明快に文書化されていること、などが挙げられます。なお、アリスはオブジェクトの暗号化を考慮しませんでしたが、これはプロバイダーというよりは、テナントの責任であるからです。"
-
-#: ./doc/security-guide/ch066_case-studies-compliance.xml15(para)
-msgid ""
-"If Alice has adequately scoped and executed these compliance activities, she"
-" may begin the process to become FedRAMP compliant by hiring an approved "
-"third-party auditor. Typically this process takes up to 6 months, after "
-"which she will receive an Authority to Operate and can offer OpenStack cloud"
-" services to the government."
-msgstr "もしアリスが十分な範囲を定義し、それらのコンプライアンス活動を実施できたのであれば、次は認定外部監査人によるFedRAMP認証の取得プロセスに移ります。一般的にこのプロセスは最長6ヶ月を要します。このステップを経て、Authority to Operate - 注意影響レベル認定 を取得し、OpenStackクラウドサービスを政府に提案できるようになります。"
-
-#: ./doc/security-guide/ch066_case-studies-compliance.xml19(para)
-msgid ""
-"Bob is tasked with compliance for a new OpenStack public cloud deployment, "
-"that is focused on providing cloud services to both small developers and "
-"startups, as well as large enterprises. Bob recognizes that individual "
-"developers are not necessarily concerned with compliance certifications, but"
-" to larger enterprises certifications are critical. Specifically Bob desires"
-" to achieve SOC 1, SOC 2 Security, as well as ISO 27001/2 as quickly as "
-"possible. Bob references the Cloud Security Alliance Cloud Control Matrix "
-"(CCM) to assist in identifying common controls across these three "
-"certifications (such as periodic access reviews, auditable logging and "
-"monitoring services, risk assessment activities, security reviews, etc). Bob"
-" then engages an experienced audit team to conduct a gap analysis on the "
-"public cloud deployment, reviews the results and fills any gaps identified. "
-"Bob works with other team members to ensure that these security controls and"
-" activities are regularly conducted for a typical audit period (~6-12 "
-"months)."
-msgstr "ボブは新たなOpenStackクラウド環境のコンプライアンス活動を任されています。このクラウドは小規模の開発者やスタートアップだけでなく、大規模企業向けにも注力しています。ボブは個人開発者はコンプライアンス認証を意識することが多くないが、いっぽうで大規模企業向けには認証が重要であることを認識しています。ボブは特にSOC 1、SOC 2、およびISO 27001/2認証を早急に取得したいと考えています。そこでボブは3つの認証に共通する統制を特定するため、Cloud Security Alliance Cloud Control Matrix (CCM)を参考にしました (例えば、定期的なアクセス検査、監査可能なロギングや監視サービス、リスク評価活動、セキュリティレビューなど)。それからボブは、パブリッククラウドのギャップ評価、結果のレビュー、そして特定されたギャップを埋めるため、経験ある監査人チームと契約します。ボブは他のチームメンバーとともに、それらのセキュリティ統制と活動が一般的な監査期間(〜6-12ヶ月)において、定期的に、確実に機能するようにします。"
-
-#: ./doc/security-guide/ch066_case-studies-compliance.xml36(para)
-msgid ""
-"At the end of the audit period Bob has arranged for an external audit team "
-"to review in-scope security controls at randomly sampled points of time over"
-" a 6 month period. The audit team provides Bob with an official report for "
-"SOC 1 and SOC 2, and separately for ISO 27001/2. As Bob has been diligent in"
-" ensuring security controls are in place for his OpenStack public cloud, "
-"there are no additional gaps exposed on the report. Bob can now provide "
-"these official reports to his customers under NDA, and advertise that he is "
-"SOC 1, SOC 2 and ISO 27001/2 compliant on his website."
-msgstr "監査期間の最後にボブは外部監査人チームとの調整を行います。目的は、6ヶ月以上にわたって無作為なタイミングで実施した、セキュリティ統制のレビューです。そして、監査人チームはボブにSOC 1とSOC 2、また別途ISO 27001/2向けの公式な報告書を提供します。ボブのパブリッククラウド採用における勤勉な取り組みの結果、指摘されるような追加のギャップはありませんでした。ボブは正式な報告書を彼の顧客にNDA下で提供でき、また、SOC 1、SOC 2、およびISO 27001/2に準拠していることを彼のウェブサイトでアピールできるようになりました。"
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml8(title)
-msgid "API endpoint configuration recommendations"
-msgstr "APIエンドポイント構成に関する推奨事項"
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml9(para)
-msgid ""
-"This chapter provides recommendations security enhancements for both public "
-"and private-facing API endpoints."
-msgstr "この章では外部と内部の API エンドポイントのセキュリティを改善するための推奨事項を提供します。"
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml13(title)
-msgid "Internal API communications"
-msgstr "内部API通信"
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml14(para)
-msgid ""
-"OpenStack provides both public facing and private API endpoints. By default,"
-" OpenStack components use the publicly defined endpoints. The recommendation"
-" is to configure these components to use the API endpoint within the proper "
-"security domain."
-msgstr "OpenStackはパブリックとプライベート両方のAPIエンドポイントを提供します。デフォルトではOpenStackコンポーネントはパブリックとして定義されたエンドポイントを使用します。推奨はこれらのコンポーネントを適切なセキュリティドメイン内で使用するよう構成することです。"
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml20(para)
-msgid ""
-"Services select their respective API endpoints based on the OpenStack "
-"service catalog. These services might not obey the listed public or internal"
-" API end point values. This can lead to internal management traffic being "
-"routed to external API endpoints."
-msgstr "サービスはOpenStackサービスカタログに基づいて、それぞれのAPIエンドポイントを選択します。これらのサービスは、リストされた外部もしくは内部APIエンドポイントの値に従わないことがあります。これは内部管理トラフィックが外部APIエンドポイントへルーティングされる可能性があります。"
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml27(title)
-msgid "Configure internal URLs in Identity service catalog"
-msgstr "認証サービスのカタログ内の内部URL構成"
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml28(para)
-msgid ""
-"The Identity service catalog should be aware of your internal URLs. While "
-"this feature is not utilized by default, it may be leveraged through "
-"configuration. Additionally, it should be forward-compatible with expectant "
-"changes once this behavior becomes the default."
-msgstr "Identity のカタログは内部 URL を認識できるようにすべきです。この機能はデフォルトで利用されませんが、設定により有効化できます。さらに、この動作が標準になると、予期される変更と前方互換性があるべきです。"
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml35(para)
-msgid "To register an internal URL for an endpoint:"
-msgstr "エンドポイント用の内部URL登録"
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml44(title)
-msgid "Configure applications for internal URLs"
-msgstr "内部URL用のアプリケーション構成"
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml45(para)
-msgid ""
-"You can force some services to use specific API endpoints. Therefore, it is "
-"recommended that each OpenStack service communicating to the API of another "
-"service must be explicitly configured to access the proper internal API "
-"endpoint."
-msgstr "いくつかのサービスは特定のAPIエンドポイントの仕様を強制することができます。従って、それぞれのOpenStackサービスと他サービスとの通信は明示的に適切な内部APIエンドポイントへアクセスするよう構成する必要があります。"
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml51(para)
-msgid ""
-"Each project may present an inconsistent way of defining target API "
-"endpoints. Future releases of OpenStack seek to resolve these "
-"inconsistencies through consistent use of the Identity Service catalog."
-msgstr "各プロジェクトで一貫性の無いAPIエンドポイントを提供しています。将来のリリースにおいてこれらの不一致を認証サービスカタログを使った一貫性で解決しようとしています。"
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml57(title)
-msgid "Configuration example #1: nova"
-msgstr "構成例#1: nova"
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml67(title)
-msgid "Configuration example #2: cinder"
-msgstr "構成例#2: cinder"
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml73(title)
-msgid "Paste and middleware"
-msgstr "Paste と ミドルウェア"
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml74(para)
-msgid ""
-"Most API endpoints and other HTTP services in OpenStack use the Python Paste"
-" Deploy library. From a securtiy perspective, this library enables "
-"manipulation of the request filter pipeline through the application's "
-"configuration. Each element in this chain is referred to as "
-"<emphasis>middleware</emphasis>. Changing the order of filters in the "
-"pipeline or adding additional middleware might have unpredictable security "
-"impact."
-msgstr "OpenStack内のほぼ全てのAPIエンドポイントと他のHTTPサービスはPythonのPaste Deployライブラリを利用しています。このライブラリにより、アプリケーションの設定によってはリクエストフィルターのパイプラインが操作が可能だと理解することがセキュリティの観点から重要になります。このパイプライン連鎖の中のそれぞれの要素は<emphasis>ミドルウェア</emphasis>として呼ばれています。パイプラインの中でフィルター順序を変更したり、ミドルウェアを追加すると予期しないセキュリティ上の影響が発生する可能性があります。"
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml83(para)
-msgid ""
-"Commonly, implementers add middleware to extend OpenStack's base "
-"functionality. We recommend implementers make careful consideration of the "
-"potential exposure introduced by the addition of non-standard software "
-"components to their HTTP request pipeline."
-msgstr "実装者がOpenStackの基本機能を拡張するためにミドルウェアを追加することは一般的です。私たちは非標準のソフトウェアコンポーネントをHTTPリクエストパイプラインへ追加することによって生じる潜在的なセキュリティについて慎重に検討する事を推奨しています。"
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml89(para)
-msgid ""
-"For more information about Paste Deploy, see <link "
-"href=\"http://pythonpaste.org/deploy/\">http://pythonpaste.org/deploy/</link>."
-msgstr "Paste Deployに関する追加情報は  <link href=\"http://pythonpaste.org/deploy/\">http://pythonpaste.org/deploy/</link> を参照してください。"
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml94(title)
-msgid "API endpoint process isolation and policy"
-msgstr "APIエンドポイントのプロセス分離とポリシー"
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml95(para)
-msgid ""
-"As much as possible, you should isolate API endpoint processes, especially "
-"those that reside within the public security domain should be isolated as "
-"much as possible. Where deployments allow, API endpoints should be deployed "
-"on separate hosts for increased isolation."
-msgstr "特にパブリックなセキュリティドメインに属するAPIエンドポイントプロセスは可能な限り分離すべきです。ディプロイメント可能であれば、APIエンドポイントは分離のために増設されたホスト上に構成すべきです。"
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml102(title)
-#: ./doc/security-guide/ch038_transport-security.xml133(title)
-msgid "Namespaces"
-msgstr "名前空間"
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml103(para)
-msgid ""
-"Many operating systems now provide compartmentalization support. Linux "
-"supports namespaces to assign processes into independent domains. Other "
-"parts of this guide cover system compartmentalization in more detail."
-msgstr "多くのOSは現在コンパートメント化をサポートしています。Linuxではプロセスに独立したドメインを割り当てる名前空間をサポートしています。システムのコンパートメント化についてはこのマニュアルの別の部分で詳しく説明されています。"
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml110(title)
-#: ./doc/security-guide/ch038_transport-security.xml144(title)
-msgid "Network policy"
-msgstr "ネットワークポリシー"
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml111(para)
-msgid ""
-"Because API endpoints typically bridge multiple security domains, you must "
-"pay particular attention to the compartmentalization of the API processes. "
-"See <xref linkend=\"ch005_security-domains-idp61360\"/> for additional "
-"information in this area."
-msgstr "APIエンドポイントは一般的に複数のセキュリティドメインをまたがるため、APIプロセスのコンパートメント化には特別の注意を払うべきです。この話題の詳細は <xref linkend=\"ch005_security-domains-idp61360\"/> を参照してください。"
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml117(para)
-msgid ""
-"With careful modeling, you can use network ACLs and IDS technologies to "
-"enforce explicit point to point communication between network services. As "
-"critical cross domain service, this type of explicit enforcement works well "
-"for OpenStack's message queue service."
-msgstr "慎重なデザインを行えば、ネットワークACLとIDS技術をネットワークサービス間の特定の通信に摘要する事が出来ます。重要なドメインをまたがるサービスとして、OpenStackのメッセージキューにこの手の明示的な強制は適しています。"
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml123(para)
-msgid ""
-"To enforce policies, you can configure services, host-based firewalls (such "
-"as iptables), local policy (SELinux or AppArmor), and optionally global "
-"network policy."
-msgstr "ポリシーを強制するために、サービス、ホストベースのファイアウォール(例えばiptables)、ローカルポリシー(SELinuxやAppArmor)、オプションとしてグローバルネットワークポリシーを設定できます。"
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml129(title)
-#: ./doc/security-guide/ch038_transport-security.xml149(title)
-#: ./doc/security-guide/ch052_devices.xml238(title)
-msgid "Mandatory access controls"
-msgstr "強制アクセス制御"
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml130(para)
-msgid ""
-"You should isolate API endpoint processes from each other and other "
-"processes on a machine. The configuration for those processes should be "
-"restricted to those processes not only by Discretionary Access Controls, but"
-" through Mandatory Access Controls. The goal of these enhanced access "
-"control is to aid in the containment and escalation of API endpoint security"
-" breaches. With mandatory access controls, such breaches severely limit "
-"access to resources and provide earlier alerting on such events."
-msgstr "APIエンドポイントのプロセスはマシン上の他のプロセスと分離すべきです。これらのプロセスの構成は任意のアクセス制御方法ではなく、強制アクセス制御によって制限されるべきです。これらのアクセス制御の目的はAPIエンドポイントのセキュリティ侵害の抑制と、特権侵害の防止です。強制アクセス制御を利用する事で、禁止されたリソースへのアクセスが厳しく制限され、早期の警告が得られるようになります。"
-
-#: ./doc/security-guide/ch041_database-backend-considerations.xml7(title)
-msgid "Database back-end considerations"
-msgstr "データベースバックエンドの考慮事項"
-
-#: ./doc/security-guide/ch041_database-backend-considerations.xml8(para)
-msgid ""
-"The choice of database server is an important consideration in the security "
-"of an OpenStack deployment. While security considerations are not the only "
-"basis on which a database server must be chosen, security considerations are"
-" the only ones within the scope of this book. In practice, OpenStack only "
-"supports two database types: PostgreSQL and MySQL."
-msgstr "データベースサーバーの選択は OpenStack 環境のセキュリティにおける重要な考慮事項です。セキュリティの考慮事項はデータベースサーバーの選択における唯一の基準ではありませんが、このドキュメントではこれらのみを取り扱います。実際のところ、OpenStack は 2 種類のデータベース PostgreSQL と MySQL のみをサポートします。"
-
-#: ./doc/security-guide/ch041_database-backend-considerations.xml9(para)
-msgid ""
-"PostgreSQL has a number of desirable security features such as Kerberos "
-"authentication, object-level security, and encryption support. The "
-"PostgreSQL community has done well to provide solid guidance, documentation,"
-" and tooling to promote positive security practices."
-msgstr "PostgreSQL は、Kerberos 認証、オブジェクトレベルのセキュリティ、暗号化のサポートなど、数多くの望ましいセキュリティ機能を有します。PostgreSQL コミュニティは実用的なセキュリティ実践を推進するために、わかりやすいガイダンス、ドキュメント、ツールを十分に提供してきました。"
-
-#: ./doc/security-guide/ch041_database-backend-considerations.xml10(para)
-msgid ""
-"MySQL has a large community, widespread adoption, and provides high "
-"availability options. MySQL also has the ability to provide enhanced client "
-"authentication by way of plug-in authentication mechanisms. Forked "
-"distributions in the MySQL community provide many options for consideration."
-" It is important to choose a specific implementation of MySQL based on a "
-"thorough evaluation of the security posture and the level of support "
-"provided for the given distribution."
-msgstr "MySQL は大規模なコミュニティを持ち、幅広く適用され、高可用性のオプションを提供しています。MySQL も、プラグイン認証機構の方法により高度なクライアント認証を提供する機能があります。MySQL コミュニティから派生したディストリビューションは、考慮事項に対する多くのオプションを提供しています。セキュリティの考え方やディストリビューションに提供されるサポートレベルの評価に基づいて、特定の MySQL ディストリビューションを選択することが重要です。"
-
-#: ./doc/security-guide/ch041_database-backend-considerations.xml12(title)
-msgid "Security references for database back-ends"
-msgstr "データベースバックエンドのセキュリティ参考資料"
-
-#: ./doc/security-guide/ch041_database-backend-considerations.xml13(para)
-msgid ""
-"Those deploying MySQL or PostgreSQL are advised to refer to existing "
-"security guidance. Some references are listed below:"
-msgstr "MySQL や PostgreSQL を導入する人は、既存のセキュリティガイダンスを参照することが推奨されます。いくつかの参考資料を以下に一覧化します。"
-
-#: ./doc/security-guide/ch041_database-backend-considerations.xml14(para)
-msgid "MySQL:"
-msgstr "MySQL:"
-
-#: ./doc/security-guide/ch041_database-backend-considerations.xml16(link)
-msgid "OWASP MySQL Hardening"
-msgstr "OWASP MySQL Hardening"
-
-#: ./doc/security-guide/ch041_database-backend-considerations.xml19(link)
-msgid "MySQL Pluggable Authentication"
-msgstr "MySQL Pluggable Authentication"
-
-#: ./doc/security-guide/ch041_database-backend-considerations.xml22(link)
-msgid "Security in MySQL"
-msgstr "Security in MySQL"
-
-#: ./doc/security-guide/ch041_database-backend-considerations.xml25(para)
-msgid "PostgreSQL:"
-msgstr "PostgreSQL:"
-
-#: ./doc/security-guide/ch041_database-backend-considerations.xml27(link)
-msgid "OWASP PostgreSQL Hardening"
-msgstr "OWASP PostgreSQL Hardening"
-
-#: ./doc/security-guide/ch041_database-backend-considerations.xml30(link)
-msgid "Total security in a PostgreSQL database"
-msgstr "Total security in a PostgreSQL database"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml8(title)
-msgid "Management interfaces"
-msgstr "管理インターフェース"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml9(para)
-msgid ""
-"It is necessary for administrators to perform command and control over the "
-"cloud for various operational functions. It is important these command and "
-"control facilities are understood and secured."
-msgstr "管理者は、様々な運用機能に対してクラウドの管理統制を行う必要があります。また、これらの管理統制機能を理解して、セキュリティの確保を行うことが重要です。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml13(para)
-msgid ""
-"OpenStack provides several management interfaces for operators and tenants:"
-msgstr "OpenStack は、オペレーターやプロジェクト向けに複数の管理インターフェースを提供しています。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml15(para)
-msgid "OpenStack dashboard (horizon)"
-msgstr "OpenStack dashboard (horizon)"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml18(para)
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml95(title)
-msgid "OpenStack API"
-msgstr "OpenStack API"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml21(para)
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml128(title)
-msgid "Secure shell (SSH)"
-msgstr "secure shell (SSH)"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml24(para)
-msgid ""
-"OpenStack management utilities such as <systemitem class=\"service\">nova-"
-"manage</systemitem> and <systemitem class=\"service\">glance-"
-"manage</systemitem>"
-msgstr "<systemitem class=\"service\">nova-manage</systemitem>、<systemitem class=\"service\">glance-manage</systemitem> などの OpenStack 管理ユーティリティ"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml29(para)
-msgid "Out-of-band management interfaces, such as IPMI"
-msgstr "帯域外管理インターフェース (IPMI など)"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml34(para)
-msgid ""
-"The OpenStack dashboard (horizon) provides administrators and tenants with a"
-" web-based graphical interface to provision and access cloud-based "
-"resources. The dashboard communicates with the back-end services through "
-"calls to the OpenStack API."
-msgstr "OpenStack dashboard (horizon) は、管理者やプロジェクトに対して、クラウドベースのリソースのプロビジョンやアクセスができるように  Web ベースのグラフィカルインターフェースを提供します。ダッシュボードは、OpenStack API に呼び出しを行うことでバックエンドサービスと対話します。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml41(title)
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml103(title)
-#: ./doc/security-guide/ch026_compute.xml22(title)
-#: ./doc/security-guide/ch026_compute.xml67(title)
-msgid "Capabilities"
-msgstr "機能"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml43(para)
-msgid ""
-"As a cloud administrator, the dashboard provides an overall view of the size"
-" and state of your cloud. You can create users and tenants/projects, assign "
-"users to tenant/projects and set limits on the resources available for them."
-msgstr "クラウド管理者として、ダッシュボードはクラウドのサイズや状態の俯瞰図を確認できます。また、ユーザーやプロジェクト (テナント) の作成、プロジェクトへのユーザーの割り当て、ユーザーやプロジェクトで利用可能なリソースの制限設定が可能です。 "
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml46(para)
-msgid ""
-"The dashboard provides tenant-users a self-service portal to provision their"
-" own resources within the limits set by administrators."
-msgstr "ダッシュボードでは、プロジェクト/ユーザーに対して、管理者が設定した制限値内で自身のリソースをプロビジョニングするためのセルフサービスポータルを提供します。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml49(para)
-msgid ""
-"The dashboard provides GUI support for routers and load-balancers. For "
-"example, the dashboard now implements all of the main Networking features."
-msgstr "また、ダッシュボードではルーターやロードバランサーにも GUI 対応しています。例えば、ダッシュボードは主な Networking 機能をすべて実装するようになりました。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml52(para)
-msgid ""
-"It is an extensible <glossterm>Django</glossterm> web application that "
-"allows easy plug-in of third-party products and services, such as billing, "
-"monitoring, and additional management tools."
-msgstr "Hirozon は拡張可能な <glossterm>Django</glossterm> Web アプリケーションで、請求、監視、追加管理ツールなど、サードパーティーの製品やサービスを簡単にプラグインできるようにします。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml55(para)
-msgid ""
-"The dashboard can also be branded for service providers and other commercial"
-" vendors."
-msgstr "また、ダッシュボードはサービスプロバイダーや他の商業ベンダー向けにブランディングすることも可能です。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml62(para)
-msgid ""
-"The dashboard requires cookies and JavaScript to be enabled in the web "
-"browser."
-msgstr "ダッシュボードは Web ブラウザーのクッキーと JavaScript を有効にする必要があります。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml65(para)
-msgid ""
-"The web server that hosts dashboard should be configured for SSL to ensure "
-"data is encrypted."
-msgstr "ダッシュボードをホストする Web サーバーは、データの暗号化が確実に行われるように SSL の設定をしてください。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml68(para)
-msgid ""
-"Both the horizon web service and the OpenStack API it uses to communicate "
-"with the back-end are susceptible to web attack vectors such as denial of "
-"service and must be monitored."
-msgstr "バックエンドとの対話に使用する horizon Web サービスおよび OpenStack API はいずれも、サービス妨害 (DoS) などの Web 攻撃ベクトルからの影響を受けるため、必ず監視が必要です。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml71(para)
-msgid ""
-"It is now possible (though there are numerous deployment/security "
-"implications) to upload an image file directly from a user’s hard disk to "
-"OpenStack Image Service through the dashboard. For multi-gigabyte images it "
-"is still strongly recommended that the upload be done using the "
-"<placeholder-1/> CLI."
-msgstr "(デプロイメント/セキュリティ関連の問題は多数ありますが) ダッシュボードでユーザーのハードディスクから OpenStack Image Service に直接イメージファイルをアップロードすることができるようになりました。サイズが GB レベルのイメージについては、<placeholder-1/> CLI を使用してイメージをアップロードするよう強く推奨しています。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml81(para)
-msgid ""
-"Create and manage security groups through dashboard. The security groups "
-"allows L3-L4 packet filtering for security policies to protect virtual "
-"machines."
-msgstr "ダッシュボードからセキュリティグループを作成・管理します。セキュリティグループにより、セキュリティポリシーに関する L3-L4 パケットをフィルダリングして仮想マシンの保護が可能になります。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml91(citetitle)
-msgid "Grizzly Release Notes"
-msgstr "Grizzly リリースノート"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml96(para)
-msgid ""
-"The OpenStack API is a RESTful web service endpoint to access, provision and"
-" automate cloud-based resources. Operators and users typically access the "
-"API through command-line utilities (for example, <placeholder-1/> or "
-"<placeholder-2/>), language-specific libraries, or third-party tools."
-msgstr "OpenStack API はクラウドベースのリソースのアクセス、プロビジョニング、自動化を行う RESTful Web サービスのエンドポイントです。オペレーターやユーザーは通常、コマンドラインユーティリティ (<placeholder-1/>、<placeholder-2/> など)、言語固有のライブラリ、またはサードパーティのツールで API にアクセスします。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml105(para)
-msgid ""
-"To the cloud administrator, the API provides an overall view of the size and"
-" state of the cloud deployment and allows the creation of users, "
-"tenants/projects, assigning users to tenants/projects, and specifying "
-"resource quotas on a per tenant/project basis."
-msgstr "API はクラウド管理者がクラウドデプロイメントのサイズや状態の概要を把握できるようにするだけでなく、ユーザー、プロジェクトの作成、プロジェクトへのユーザーの割り当て、プロジェクトベースのリソースクォータの指定などができるようにします。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml112(para)
-msgid ""
-"The API provides a tenant interface for provisioning, managing, and "
-"accessing their resources."
-msgstr "API はリソースのプロビジョニング、管理、アクセスに使用するプロジェクトインターフェースを提供します。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml119(para)
-msgid ""
-"The API service should be configured for SSL to ensure data is encrypted."
-msgstr "API サービスはデータが確実に暗号化されるように SSL の設定が必要です。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml122(para)
-msgid ""
-"As a web service, OpenStack API is susceptible to familiar web site attack "
-"vectors such as denial of service attacks."
-msgstr "Web サービスとして OpenStack API は、サービス妨害 (DoS) 攻撃など、よく知られている Web サイト攻撃ベクトルからの影響を受けます。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml129(para)
-msgid ""
-"It has become industry practice to use secure shell (SSH) access for the "
-"management of Linux and Unix systems. SSH uses secure cryptographic "
-"primitives for communication. With the scope and importance of SSH in "
-"typical OpenStack deployments, it is important to understand best practices "
-"for deploying SSH."
-msgstr "Linux や Unix システムの管理にはセキュアシェル (SSH) を使用するのが業界の慣習となっています。SSH は通信にセキュアな暗号化機能を使用します。一般的な OpenStack デプロイメントでの SSH の範囲や重要性において、SSH デプロイメントのベストプラクティスを把握することが重要です。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml131(title)
-msgid "Host key fingerprints"
-msgstr "ホストキーのフィンガープリント"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml132(para)
-msgid ""
-"Often overlooked is the need for key management for SSH hosts. As most or "
-"all hosts in an OpenStack deployment will provide an SSH service, it is "
-"important to have confidence in connections to these hosts. It cannot be "
-"understated that failing to provide a reasonably secure and accessible "
-"method to verify SSH host key fingerprints is ripe for abuse and "
-"exploitation."
-msgstr "頻繁に見逃されるのが SSH ホストのキー管理の必要性です。OpenStack デプロイメントホストのすべてまたは多くが SSH サービスを提供します。このようなホストへの接続の信頼性を確保することが重要です。SSH ホストキーのフィンガープリントの検証に関して比較的セキュアでアクセス可能なメソッドを提供できないと、悪用やエクスプロイトの温床となるといっても過言ではありません。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml133(para)
-msgid ""
-"All SSH daemons have private host keys and, upon connection, offer a host "
-"key fingerprint. This host key fingerprint is the hash of an unsigned public"
-" key. It is important these host key fingerprints are known in advance of "
-"making SSH connections to those hosts. Verification of host key fingerprints"
-" is instrumental in detecting man-in-the-middle attacks."
-msgstr "SSH デーモンにはすべてプライベートのホストキーがあり、接続するとホストキーのフィンガープリントが提供されます。このホストキーのフィンガープリントは未署名のパブリックキーのハッシュです。これらのホストに SSH  接続する前に、ホストキーのフィンガープリントを把握しておくことが重要です。ホストキーのフィンガープリントの検証は中間者攻撃の検出に役立ちます。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml134(para)
-msgid ""
-"Typically, when an SSH daemon is installed, host keys will be generated. It "
-"is necessary that the hosts have sufficient entropy during host key "
-"generation. Insufficient entropy during host key generation can result in "
-"the possibility to eavesdrop on SSH sessions."
-msgstr "通常、SSH デーモンがインストールされると、ホストキーが生成されます。ホストキーの生成時に、ホストには十分なエントロピーが必要になります。ホストキーの生成時にエントロピーが十分にないと、SSH セッションの傍受が発生してしまう可能性があります。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml135(para)
-msgid ""
-"Once the SSH host key is generated, the host key fingerprint should be "
-"stored in a secure and queriable location. One particularly convenient "
-"solution is DNS using SSHFP resource records as defined in RFC-4255. For "
-"this to be secure, it is necessary that DNSSEC be deployed."
-msgstr "SSH ホストキーが生成されると、ホストキーのフィンガープリントはセキュアでクエリ可能な場所に保存されるはずです。特に有用なソリューションは、RFC-4255 で定義されているように SSHFP リソースレコードを使用した DNS です。これをセキュアにするには、DNSSEC のデプロイメントが必要になります。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml139(title)
-msgid "Management utilities"
-msgstr "管理ユーティリティ"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml140(para)
-msgid ""
-"The OpenStack Management Utilities are open-source Python command-line "
-"clients that make API calls. There is a client for each OpenStack service "
-"(for example, <systemitem class=\"service\">nova</systemitem>, <systemitem "
-"class=\"service\">glance</systemitem>). In addition to the standard CLI "
-"client, most of the services have a management command-line utility which "
-"makes direct calls to the database. These dedicated management utilities are"
-" slowly being deprecated."
-msgstr "OpenStack 管理ユーテリティは、API 呼び出しを行う、オープンソースの Python のコマンドラインクライアントです。OpenStack サービス (<systemitem class=\"service\">nova</systemitem>、<systemitem class=\"service\">glance</systemitem> など) 毎にクライアントがあります。標準の CLI クライアントに加え、サービスの多くには管理コマンドラインがあり、データベースへ直接呼び出しを行います。これらの専用の管理ユーテリティは徐々に廃止予定となっています。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml152(para)
-msgid ""
-"The dedicated management utilities (*-manage) in some cases use the direct "
-"database connection."
-msgstr "場合によっては専用の管理ユーテリティ (*-manage) は直接データベースへの接続を使用することがあります。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml155(para)
-msgid ""
-"Ensure that the .rc file which has your credential information is secured."
-msgstr "認証情報が含まれている .rc ファイルのセキュリティが確保されているようにします。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml161(para)
-msgid ""
-"<citetitle>OpenStack End User Guide</citetitle> section <link "
-"href=\"http://docs.openstack.org/user-"
-"guide/content/section_cli_overview.html\">command-line clients "
-"overview</link>"
-msgstr "<citetitle>OpenStack エンドユーザーガイド</citetitle> の項: <link href=\"http://docs.openstack.org/user-guide/content/section_cli_overview.html\">コマンドラインクライアントの概要</link>"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml162(para)
-msgid ""
-"<citetitle>OpenStack End User Guide</citetitle> section <link "
-"href=\"http://docs.openstack.org/user-"
-"guide/content/cli_openrc.html\">Download and source the OpenStack RC "
-"file</link>"
-msgstr "<citetitle>OpenStack エンドユーザーガイド</citetitle> の項 <link href=\"http://docs.openstack.org/user-guide/content/cli_openrc.html\">OpenStack RC ファイルのダウンロードとソース</link>"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml166(title)
-msgid "Out-of-band management interface"
-msgstr "帯域外管理インターフェース"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml167(para)
-msgid ""
-"OpenStack management relies on out-of-band management interfaces such as the"
-" IPMI protocol to access into nodes running OpenStack components. IPMI is a "
-"very popular specification to remotely manage, diagnose, and reboot servers "
-"whether the operating system is running or the system has crashed."
-msgstr "OpenStack コンポーネントを実行するノードにアクセスする場合、OpenStack の管理は IPMI プロトコルなどのアウトオブバンド管理インターフェースに依存します。IPMI は非常に有名な仕様で、オペレーティングシステムが実行中である場合やシステムがクラッシュした場合でもリモートでのサーバー管理、診断、リブートを行えます。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml176(para)
-msgid ""
-"Use strong passwords and safeguard them, or use client-side SSL "
-"authentication."
-msgstr "強力なパスワードを使用してセーフガードするか、クライアント側の SSL 認証を使用してください。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml179(para)
-msgid ""
-"Ensure that the network interfaces are on their own private(management or a "
-"separate) network. Segregate management domains with firewalls or other "
-"network gear."
-msgstr "ネットワークインターフェースはプライベート  (管理または個別) ネットワークに設定されていることを確認します。管理ドメインはファイアウォールか他のネットワーク機器で分離してください。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml182(para)
-msgid ""
-"If you use a web interface to interact with the "
-"<glossterm>BMC</glossterm>/IPMI, always use the SSL interface, such as https"
-" or port 443. This SSL interface should <emphasis "
-"role=\"bold\">NOT</emphasis> use self-signed certificates, as is often "
-"default, but should have trusted certificates using the correctly defined "
-"fully qualified domain names (FQDNs)."
-msgstr "Web インターフェースを使用して <glossterm>BMC</glossterm>/IPMI と対話する場合、常に SSL インターフェースを使用するようにしてください (例: https またはポート 443)。この SSL インターフェースは自己署名証明書を使用<emphasis role=\"bold\">しない</emphasis>ようにしてください。通常、これがデフォルトとなっていますが、正しく定義された完全修飾ドメイン名 (FQDN) を使用して信頼済みの証明書を使用するようにしてください。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml191(para)
-msgid ""
-"Monitor the traffic on the management network. The anomalies might be easier"
-" to track than on the busier compute nodes."
-msgstr "管理ネットワークのトラフィックを監視します。トラフィックの多いコンピュートノードよりも例外のトラッキングが簡単になる場合があります。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml196(para)
-msgid ""
-"Out of band management interfaces also often include graphical machine "
-"console access. It is often possible, although not necessarily default, that"
-" these interfaces are encrypted. Consult with your system software "
-"documentation for encrypting these interfaces."
-msgstr "また、アウトオブバンド管理インターフェースはグラフィカルのコンソールアクセスが可能な場合が多くあります。デフォルトではない可能性もありますが、これらのインターフェースは暗号化されていることがあります。これらのインターフェースの暗号化については、お使いのシステムのソフトウェア文書を確認してください。"
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml200(link)
-msgid "Hacking servers that are turned off"
-msgstr "オフ状態のサーバーのハッキング"
-
-#: ./doc/security-guide/ch028_case-studies-identity-management.xml8(title)
-msgid "Case studies: Identity management"
-msgstr "ケーススタディ: ID 管理"
-
-#: ./doc/security-guide/ch028_case-studies-identity-management.xml9(para)
-msgid ""
-"In this case study we discuss how Alice and Bob would address configuration "
-"of OpenStack core services. These include the Identity service, dashboard, "
-"and Compute services. Alice will be concerned with integration into the "
-"existing government directory services, while Bob will need to provide "
-"access to the public."
-msgstr "このケーススタディでは、アリスとボブが OpenStack コアサービスの設定をどのように取り扱うかを議論します。これらには、Identity Service、Dashboard、Compute が含まれます。アリスは既存の政府ディレクトリサービスに統合することに関心があります。ボブはパブリックにアクセス権を提供する必要があります。"
-
-#: ./doc/security-guide/ch028_case-studies-identity-management.xml19(para)
-msgid ""
-"Alice's enterprise has a well-established directory service with two-factor "
-"authentication for all users. She configures the Identity service to support"
-" an external authentication service supporting authentication with "
-"government-issued access cards. She also uses an external LDAP server to "
-"provide role information for the users that is integrated with the access "
-"control policy. Due to FedRAMP compliance requirements, Alice implements "
-"two-factor authentication on the management network for all administrator "
-"access."
-msgstr "アリスの企業はすべてのユーザーに対して 2 要素認証を持つディレクトリサービスが十分に確立されています。彼女は政府発行のアクセスカードを用いた認証をサポートする外部認証サービスをサポートするよう Identity を設定します。アクセス制御ポリシーと統合されたユーザー用ロール情報を提供するために、外部 LDAP サービスも使用します。FedRAMP コンプライアンス要件のため、アリスはすべての管理アクセスに対して管理ネットワークで 2 要素認証を導入します。"
-
-#: ./doc/security-guide/ch028_case-studies-identity-management.xml30(para)
-msgid ""
-"Alice also deploys the dashboard to manage many aspects of the cloud. She "
-"deploys the dashboard with HSTS to ensure that only HTTPS is used. The "
-"dashboard resides within an internal subdomain of the private network domain"
-" name system."
-msgstr "アリスはクラウドのさまざまな観点を管理するために Dashboard も導入します。必ず HTTPS のみを使用するために HSTS と共に Dashboard を導入します。Dashboard はプライベートネットワークの DNS の内部サブドメインの中にあります。"
-
-#: ./doc/security-guide/ch028_case-studies-identity-management.xml36(para)
-msgid ""
-"Alice decides to use SPICE instead of VNC for the virtual console. She wants"
-" to take advantage of the emerging capabilities in SPICE."
-msgstr "アリスは仮想コンソールに VNC の代わりに SPICE を使用することを決めました。SPICE の先進的な機能の利点を得ようと思います。"
-
-#: ./doc/security-guide/ch028_case-studies-identity-management.xml44(para)
-msgid ""
-"Because Bob must support authentication for the general public, he decides "
-"to use use user name and password authentication. He has concerns about "
-"brute force attacks attempting to crack user passwords, so he also uses an "
-"external authentication extension that throttles the number of failed login "
-"attempts. Bob's management network is separate from the other networks "
-"within his cloud, but can be reached from his corporate network through ssh."
-" As recommended earlier, Bob requires administrators to use two-factor "
-"authentication on the Management network to reduce the risk from compromised"
-" administrator passwords."
-msgstr "ボブは一般的なパブリックによる認証をサポートする必要があるため、ユーザー名とパスワードによる認証を提供することを選択します。彼はユーザーのパスワードを解析しようとするブルートフォース攻撃について心配します。そのため、ログイン試行回数の失敗数を制限する外部認証拡張も使用します。ボブの管理ネットワークは彼のクラウドの中で他のネットワークと分離しています。しかし、彼の企業ネットワークから SSH 経由でアクセスできます。これまでに推奨しているとおり、ボブは管理者のパスワードが漏洩するリスクを減らすために、管理者が管理ネットワークで 2 要素認証を使用することを要求します。"
-
-#: ./doc/security-guide/ch028_case-studies-identity-management.xml56(para)
-msgid ""
-"Bob also deploys the dashboard to manage many aspects of the cloud. He "
-"deploys the dashboard with HSTS to ensure that only HTTPS is used. He has "
-"ensured that the dashboard is deployed on a second-level domain due to the "
-"limitations of the same-origin policy. He also disables "
-"<option>HORIZON_IMAGES_ALLOW_UPLOAD</option> to prevent resource exhaustion."
-msgstr "ボブはクラウドのさまざまな観点を管理するために Dashboard も導入します。必ず HTTPS のみを使用するために HSTS と共に Dashboard を導入します。Dashboard が同一オリジンポリシーの制限のため必ず第 2 レベルドメインに導入されるようにしました。また、リソース枯渇を防ぐために <option>HORIZON_IMAGES_ALLOW_UPLOAD</option> を無効化します。"
-
-#: ./doc/security-guide/ch028_case-studies-identity-management.xml63(para)
-msgid ""
-"Bob decides to use VNC for his virtual console for its maturity and security"
-" features."
-msgstr "ボブはその成熟度とセキュリティ機能から仮想コンソールに VNC を使用することを決めました。"
-
-#: ./doc/security-guide/ch037_risks.xml8(title)
-msgid "Message queuing architecture"
-msgstr "メッセージキューイングアーキテクチャー"
-
-#: ./doc/security-guide/ch037_risks.xml9(para)
-msgid ""
-"Message queuing services facilitate inter-process communication in "
-"OpenStack. OpenStack supports these message queuing service back ends:"
-msgstr "メッセージキューイングサービスは、OpenStack 内におけるプロセス間通信を担います。OpenStack は次のキューイングサービスをサポートしています。"
-
-#: ./doc/security-guide/ch037_risks.xml14(para)
-msgid "RabbitMQ"
-msgstr "RabbitMQ"
-
-#: ./doc/security-guide/ch037_risks.xml17(para)
-msgid "Qpid"
-msgstr "Qpid"
-
-#: ./doc/security-guide/ch037_risks.xml20(para)
-msgid "ZeroMQ or 0MQ"
-msgstr "ZeroMQ、または、0MQ"
-
-#: ./doc/security-guide/ch037_risks.xml23(para)
-msgid ""
-"Both RabbitMQ and Qpid are Advanced Message Queuing Protocol (AMQP) "
-"frameworks, which provide message queues for peer-to-peer communication. "
-"Queue implementations are typically deployed as a centralized or "
-"decentralized pool of queue servers. ZeroMQ provides direct peer-to-peer "
-"communication through TCP sockets."
-msgstr "RabbitMQ と Qpid は両方とも、Advanced Message Queuing Protocol (AMQP)  フレームワークであり、ピアツーピア通信にメッセージキューを提供する仕組みです。\nキューの実装は通常、キューサーバのプールを集中型か分散型で展開します。\nZeroMQ はピア間の通信に直接 TCP ソケットを使うところが異なっています。"
-
-#: ./doc/security-guide/ch037_risks.xml29(para)
-msgid ""
-"Message queues effectively facilitate command and control functions across "
-"OpenStack deployments. Once access to the queue is permitted no further "
-"authorization checks are performed. Services accessible through the queue do"
-" validate the contexts and tokens within the actual message payload. "
-"However, you must note the expiration date of the token because tokens are "
-"potentially re-playable and can authorize other services in the "
-"infrastructure."
-msgstr "メッセージキューは、OpenStack 内における指揮系統の機能を担います。一度キューへのアクセスが許可されると、その後の認証チェックは行われません。キューを使用するサービスがメッセージペイロード内のコンテキストとトークンのチェックを行います。\nとはいえ、トークンの期限切れには注意を払う必要があります。これは、トークンが潜在的に再発行可能であり、インフラストラクチャ内の他のサービスを許可する可能性があるためです。"
-
-#: ./doc/security-guide/ch037_risks.xml37(para)
-msgid ""
-"OpenStack does not support message-level confidence, such as message "
-"signing. Consequently, you must secure and authenticate the message "
-"transport itself. For high-availability (HA) configurations, you must "
-"perform queue-to-queue authentication and encryption."
-msgstr "OpenStack は、メッセージへの署名のようなメッセージレベルのコンフィデンスはサポートしていません。そのため、メッセージの通信路そのものがセキュア化され、かつ、キューサーバーへのアクセスの際に認証が行なわれる必要があります。\nまた、HA 設定の際には、キュー間の認証と暗号化も同様に実施するべきです。"
-
-#: ./doc/security-guide/ch037_risks.xml42(para)
-msgid ""
-"With ZeroMQ messaging, IPC sockets are used on individual machines. Because "
-"these sockets are vulnerable to attack, ensure that the cloud operator has "
-"secured them."
-msgstr "ZeroMQ メッセージングでは、IPC ソケットが各マシンで使用されます。これらのソケットは管理者がセキュア化しない限り、ローカルメッセージインジェクションやスヌーピングの攻撃に脆弱な可能性があります。"
-
-#: ./doc/security-guide/ch026_compute.xml8(title)
-#: ./doc/security-guide/ch004_book-introduction.xml122(title)
-msgid "Compute"
-msgstr "Compute"
+#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml8(title)
+msgid "Case studies: instance isolation"
+msgstr "ケーススタディ：インスタンス分離"
+
+#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml9(para)
+msgid ""
+"In this case study we discuss how Alice and Bob would ensure that their "
+"instances are properly isolated. First we consider hypervisor selection, and"
+" then techniques for hardening QEMU and applying mandatory access controls."
+msgstr "このケーススタディでは、アリスとボブが所有するインスタンスが正しく分離されていることを確認する方法について説明します。まずはハイパーバイザーの選択とQEMUの強化、強制アクセスコントロールの適用について検討します。"
+
+#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml12(para)
+msgid ""
+"Alice chooses Xen for the hypervisor in her cloud due to a strong internal "
+"knowledge base and a desire to use the Xen security modules (XSM) for fine-"
+"grained policy enforcement."
+msgstr "アリスは豊富な知識を持っている上、細かいポリシー強制のためにXen security module(XSM)を採用したいため、Xenをハイパーバイザーに選択します。"
+
+#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml13(para)
+msgid ""
+"Alice is willing to apply a relatively large amount of resources to software"
+" packaging and maintenance. She will use these resources to build a highly "
+"customized version of QEMU that has many components removed, thereby "
+"reducing the attack surface. She will also ensure that all compiler "
+"hardening options are enabled for QEMU. Alice accepts that these decisions "
+"will increase long-term maintenance costs."
+msgstr "アリスはソフトウェアパッケージングとメンテナンスにそれなりのリソースを割り当てる予定です。これらのリソースを活用し、QEMUから多数コンポーネントを取り除くなど大幅カスタマイズをします。コンポーネントを取り除くことで、攻撃可能な部分は削減されます。また、QEMUのコンパイラ強化オプションがすべて有効になっていることも確認します。長期メンテナンスコストが増えてしまうことを理解した上でこれらの作業や設定を選択しています。"
+
+#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml14(para)
+msgid ""
+"Alice writes XSM policies (for Xen) and SELinux policies (for Linux domain "
+"0, and device domains) to provide stronger isolation between the instances. "
+"Alice also uses the Intel TXT support in Xen to measure the hypervisor "
+"launch in the TPM."
+msgstr "インスタンス間の分離を強めるため、アリスはXSMポリシー(Xen向け)とSELinuxポリシー(Linux domain0とデバイスドメイン向け)を作成しています。また、TPMのハイパーバイザーの起動を計測するためにXenに含まれるIntel TXTサポートを採用しています。"
+
+#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml18(para)
+msgid ""
+"Bob is very concerned about instance isolation since the users in a public "
+"cloud represent anyone with a credit card, meaning they are inherently "
+"untrusted. Bob has just started hiring the team that will deploy the cloud, "
+"so he can tailor his candidate search for specific areas of expertise. With "
+"this in mind, Bob chooses a hypervisor based on its technical features, "
+"certifications, and community support. KVM has an EAL 4+ common criteria "
+"rating, with a labeled security protection profile (LSPP) to provide added "
+"assurance for instance isolation. This, combined with the strong support for"
+" KVM within the OpenStack community drives Bob's decision to use KVM."
+msgstr "パブリッククラウドではクレジットカードを所持していればユーザーになれるため、本質的に信頼性が低いことからボブはインスタンス分離に非常に気を遣っています。ボブはクラウドを配備するチームのメンバーの採用を開始したばかりなので、メンバー候補の検索条件として任意の特定スキルを指定できます。それを踏まえ、ボブは技術的な特徴、所持する証明等、コミュニティサポートを基準にハイパーバイザーを選択します。KVMはEAL 4+共通項目評価とラベル化されたセキュリティ保護プロフィール(LSPP)によってインスタンス分離を保証しています。これらの強みとOpenStackコミュニティのKVMへの豊富なサポートを総合して考えた結果、ボブはKVMを採用することにします。"
+
+#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml19(para)
+msgid ""
+"Bob weighs the added cost of repackaging QEMU and decides that he cannot "
+"commit those resources to the project. Fortunately, his Linux distribution "
+"has already enabled the compiler hardening options. So he decides to use "
+"this QEMU package. Finally, Bob leverages sVirt to manage the SELinux "
+"polices associated with the virtualization stack."
+msgstr "ボブはQEMUを再パッケージするために発生するコストを検討し、そのためのリソースをプロジェクトに割くことはできないと判断します。幸い、彼の使用しているLinuxのディストリビューションではコンパイラ強化オプションが有効になっているため、そのQEMUパッケージを採用します。最後に、仮想スタックに関わるSELinuxポリシーを管理するためにsVirtを利用します。"
 
 #: ./doc/security-guide/ch026_compute.xml9(para)
 msgid ""
@@ -4300,740 +8601,1142 @@ msgstr "Red Hat bug 913607"
 msgid "SPICE support in RDO Grizzly"
 msgstr "RDO Grizzly における SPICE のサポート"
 
+#: ./doc/security-guide/ch046_data-residency.xml8(title)
+msgid "Data privacy concerns"
+msgstr "データプライバシ関連"
+
+#: ./doc/security-guide/ch046_data-residency.xml9(para)
+msgid ""
+"OpenStack is designed to support multitenancy and those tenants will most "
+"probably have different data requirements. As a cloud builder and operator "
+"you need to ensure your OpenStack environment can address various data "
+"privacy concerns and regulations. In this chapter we will address the "
+"following topics around Data Privacy as it pertains to OpenStack "
+"implementations:"
+msgstr "OpenStack はマルチテナンシーをサポートするよう設計されており、これらのテナントには、まず間違いなく異なるデータ要件があるでしょう。クラウド構築者とオペレータとして、あなたは自身の OpenStack 環境が様々なデータプライバシー関連と規制を扱える事を確認する必要があります。OpenStack 実装に関連するので、本章ではデータプライバシーにまつわる以下のトピックを扱います。"
+
+#: ./doc/security-guide/ch046_data-residency.xml19(para)
+#: ./doc/security-guide/ch046_data-residency.xml26(title)
+msgid "Data residency"
+msgstr "データの所在"
+
+#: ./doc/security-guide/ch046_data-residency.xml22(para)
+#: ./doc/security-guide/ch046_data-residency.xml77(title)
+msgid "Data disposal"
+msgstr "データの処分"
+
+#: ./doc/security-guide/ch046_data-residency.xml27(para)
+msgid ""
+"The privacy and isolation of data has consistently been cited as the primary"
+" barrier to cloud adoption over the past few years. Concerns over who owns "
+"data in the cloud and whether the cloud operator can be ultimately trusted "
+"as a custodian of this data have been significant issues in the past."
+msgstr "データのプライバシーと分割は、ここ数年クラウド採用の最初の障壁としてずっと言及されてきました。クラウド中でデータを所有するのは誰か、このデータの管理人としてクラウドオペレータは結局信用できるのか否かという事は、これまで重要な問題でした。"
+
+#: ./doc/security-guide/ch046_data-residency.xml28(para)
+msgid ""
+"Numerous OpenStack services maintain data and metadata belonging to tenants "
+"or reference tenant information."
+msgstr "多数の OpenStack サービス群は、テナントやテナント情報の所在に属するデータとメタデータを管理します。"
+
+#: ./doc/security-guide/ch046_data-residency.xml29(para)
+msgid ""
+"Tenant data stored in an OpenStack cloud may include the following items:"
+msgstr "OpenStack クラウドに保存されたテナントデータは以下の項目を含まれます："
+
+#: ./doc/security-guide/ch046_data-residency.xml34(para)
+msgid "Compute instance ephemeral filesystem storage"
+msgstr "Compute のインスタンスの一時的ファイルシステムストレージ"
+
+#: ./doc/security-guide/ch046_data-residency.xml37(para)
+msgid "Compute instance memory"
+msgstr "Compute インスタンスのメモリ"
+
+#: ./doc/security-guide/ch046_data-residency.xml40(para)
+#: ./doc/security-guide/ch046_data-residency.xml105(para)
+msgid "Block Storage volume data"
+msgstr "ブロックストレージボリュームデータ"
+
+#: ./doc/security-guide/ch046_data-residency.xml43(para)
+msgid "Public keys for Compute Access"
+msgstr "Comptue アクセス用パブリックキー"
+
+#: ./doc/security-guide/ch046_data-residency.xml46(para)
+msgid "Virtual Machine Images in the Image Service"
+msgstr "Image Service 中の仮想マシンイメージ"
+
+#: ./doc/security-guide/ch046_data-residency.xml49(para)
+msgid "Machine snapshots"
+msgstr "マシンのスナップショット"
+
+#: ./doc/security-guide/ch046_data-residency.xml52(para)
+msgid "Data passed to OpenStack Compute's configuration-drive extension"
+msgstr "OpenStack Compute の設定用ドライブ拡張に渡されたデータ"
+
+#: ./doc/security-guide/ch046_data-residency.xml55(para)
+msgid ""
+"Metadata stored by an OpenStack cloud includes the following non-exhaustive "
+"items:"
+msgstr "以下の不完全な一覧を含む、OpenStack クラウドが保存したメタデータ:"
+
+#: ./doc/security-guide/ch046_data-residency.xml57(para)
+msgid "Organization name"
+msgstr "組織名"
+
+#: ./doc/security-guide/ch046_data-residency.xml60(para)
+msgid "User's \"Real Name\""
+msgstr "ユーザの「実名」"
+
+#: ./doc/security-guide/ch046_data-residency.xml63(para)
+msgid ""
+"Number or size of running instances, buckets, objects, volumes, and other "
+"quota-related items"
+msgstr "実行中のインスタンスのサイズ、バケット、オブジェクト、ボリューム、その他クォータ関連の項目"
+
+#: ./doc/security-guide/ch046_data-residency.xml66(para)
+msgid "Number of hours running instances or storing data"
+msgstr "実行中のインスタンス又は保存されたデータの経過時間"
+
+#: ./doc/security-guide/ch046_data-residency.xml69(para)
+msgid "IP addresses of users"
+msgstr "ユーザの IP アドレス"
+
+#: ./doc/security-guide/ch046_data-residency.xml72(para)
+msgid "Internally generated private keys for compute image bundling"
+msgstr "Compute イメージ作成用に内部で生成されたプライベートキー"
+
+#: ./doc/security-guide/ch046_data-residency.xml78(para)
+msgid ""
+"OpenStack operators should strive to provide a certain level of tenant data "
+"disposal assurance. Best practices suggest that the operator sanitize cloud "
+"system media (digital and non-digital) prior to disposal, release out of "
+"organization control or release for reuse. Sanitization methods should "
+"implement an appropriate level of strength and integrity given the specific "
+"security domain and sensitivity of the information."
+msgstr "OpenStack オペレータは、ある一定レベルのテナントデータ破棄保証が提供できるよう努力しなければんりません。ベストプラクティスは、クラウドシステムメディア (デジタル・非デジタル) を破棄、組織コントロール外へのリリース、再利用の為の開放より前にオペレータがメディアをクリアする事を推奨しています。メディアのクリア方法は、特定のセキュリティドメインと情報のデリケートさが与えられた、適切なレベルの強度と完全性を実装すべきです。"
+
+#: ./doc/security-guide/ch046_data-residency.xml80(para)
+msgid ""
+"\"Sanitization is the process used to remove information from system media "
+"such that there is reasonable assurance that the information cannot be "
+"retrieved or reconstructed. Sanitization techniques, including clearing, "
+"purging, and destroying media information, prevent the disclosure of "
+"organizational information to unauthorized individuals when such media is "
+"reused or released for disposal.\" [NIST Special Publication 800-53 Revision"
+" 3]"
+msgstr "「データのサニタイズは、情報が取得あるいは再構築できない事の合理的な保証が得られるよう、システム媒体から情報を削除する為に使用されるプロセスです。サニタイズ技術（媒体の情報のクリア、破棄、破壊を含む）は、こうした媒体が再利用・譲渡・破棄された際に、組織の情報が閲覧権限のない個人に開示される事を防ぎます。」 [NIST Special Publication 800-53 Revision 3]"
+
+#: ./doc/security-guide/ch046_data-residency.xml82(para)
+msgid ""
+"General data disposal and sanitization guidelines as adopted from NIST "
+"recommended security controls. Cloud operators should:"
+msgstr "NIST が採用した汎用のデータ破棄とサニタイズのガイドラインは、セキュリティ制御を推奨しています。クラウドオペレータは以下のことをすべきです。"
+
+#: ./doc/security-guide/ch046_data-residency.xml84(para)
+msgid "Track, document and verify media sanitization and disposal actions."
+msgstr "媒体サニタイズと破棄行為の追跡・文書化・検証を行うこと。"
+
+#: ./doc/security-guide/ch046_data-residency.xml87(para)
+msgid "Test sanitation equipment and procedures to verify proper performance."
+msgstr "適切なパフォーマンスを検証する為、サニタイズ設備と過程の評価を行うこと。"
+
+#: ./doc/security-guide/ch046_data-residency.xml91(para)
+msgid ""
+"Sanitize portable, removable storage devices prior to connecting such "
+"devices to the cloud infrastructure."
+msgstr "持ち運び可能なリムーバルストレージデバイスをクラウドインフラに接続する前にサニタイズすること。"
+
+#: ./doc/security-guide/ch046_data-residency.xml94(para)
+msgid "Destroy cloud system media that cannot be sanitized."
+msgstr "サニタイズできないクラウドシステム媒体を破壊すること。"
+
+#: ./doc/security-guide/ch046_data-residency.xml97(para)
+msgid "In an OpenStack deployment you will need to address the following:"
+msgstr "OpenStack デプロイでは、以下の事も実施する必要があるでしょう。"
+
+#: ./doc/security-guide/ch046_data-residency.xml99(para)
+msgid "Secure data erasure"
+msgstr "安全なデータの消去"
+
+#: ./doc/security-guide/ch046_data-residency.xml102(para)
+#: ./doc/security-guide/ch046_data-residency.xml119(title)
+msgid "Instance memory scrubbing"
+msgstr "インスタンスメモリの消去"
+
+#: ./doc/security-guide/ch046_data-residency.xml108(para)
+#: ./doc/security-guide/ch046_data-residency.xml132(title)
+msgid "Compute instance ephemeral storage"
+msgstr "Compute インスタンスの一時ストレージ"
+
+#: ./doc/security-guide/ch046_data-residency.xml111(para)
+#: ./doc/security-guide/ch046_data-residency.xml139(title)
+msgid "Bare metal server sanitization"
+msgstr "物理サーバのサニタイズ"
+
+#: ./doc/security-guide/ch046_data-residency.xml115(title)
+msgid "Data not securely erased"
+msgstr "安全に消去されなかったデータ"
+
+#: ./doc/security-guide/ch046_data-residency.xml116(para)
+msgid ""
+"Within OpenStack some data may be deleted, but not securely erased in the "
+"context of the NIST standards outlined above. This is generally applicable "
+"to most or all of the above-defined metadata and information stored in the "
+"database. This may be remediated with database and/or system configuration "
+"for auto vacuuming and periodic free-space wiping."
+msgstr "OpenStack 中でいくつかのデータは削除されるかも知れませんが、上記で触れた NIST 標準の文脈における安全な消去ではありません。これは一般に、データベースに保存された上記で定義したメタデータと情報の大半又は全てに当てはまります。これは、データベースとシステム設定のどちらか又は両方で、自動バキュームと定期的な空き領域のクリアを実施する事で解決する事ができるかも知れません。"
+
+#: ./doc/security-guide/ch046_data-residency.xml120(para)
+msgid ""
+"Specific to various hypervisors is the treatment of instance memory. This "
+"behavior is not defined in OpenStack Compute, although it is generally "
+"expected of hypervisors that they will make a best effort to scrub memory "
+"either upon deletion of an instance, upon creation of an instance, or both."
+msgstr "様々なハイパーバイザの特色はインスタンスメモリの扱いにあります。\n\nThis behavior is not defined in OpenStack Compute, although it is generally expected of hypervisors that they will make a best effort to scrub memory either upon deletion of an instance, upon creation of an instance, or both.\n\nこの挙動は OpenStack Compute で定義されておらず、ハイパーバイザがインスタンス作成時または削除時、あるいはその両方において、ベストエフォートでメモリのクリンアップを行うだろうと一般に考えられています。"
+
+#: ./doc/security-guide/ch046_data-residency.xml121(para)
+msgid ""
+"Xen explicitly assigns dedicated memory regions to instances and scrubs data"
+" upon the destruction of instances (or domains in Xen parlance). KVM depends"
+" more greatly on Linux page management; A complex set of rules related to "
+"KVM paging is defined in the <link href=\"http://www.linux-"
+"kvm.org/page/Memory\">KVM documentation</link>."
+msgstr "Xen は、専用のメモリ範囲をインスタンスに明確に割り当て、インスタンス (又は Xen の用語でドメイン) 破棄時にそのデータをクリンアップします。KVM はより大いに Linux のページ管理に依存しています。 KVM のページングに関する複雑なルールセットは、<link href=\"http://www.linux-kvm.org/page/Memory\">KVM の文書</link>で定義されています。"
+
+#: ./doc/security-guide/ch046_data-residency.xml122(para)
+msgid ""
+"It is important to note that use of the Xen memory balloon feature is likely"
+" to result in information disclosure. We strongly recommended to avoid use "
+"of this feature."
+msgstr "Xen のメモリバルーン機能の使用は情報漏えいの結果になりかねないという事への注意は重要です。"
+
+#: ./doc/security-guide/ch046_data-residency.xml123(para)
+msgid ""
+"For these and other hypervisors, we recommend referring to hypervisor-"
+"specific documentation."
+msgstr "これらや他のハイパーバイザでは、ハイパーバイザ毎のドキュメントを参照すると良いでしょう。"
+
+#: ./doc/security-guide/ch046_data-residency.xml126(title)
+msgid "Cinder volume data"
+msgstr "Cinder のボリュームデータ"
+
+#: ./doc/security-guide/ch046_data-residency.xml127(para)
+msgid ""
+"Plugins to OpenStack Block Storage will store data in a variety of ways. "
+"Many plug-ins are specific to a vendor or technology, whereas others are "
+"more DIY solutions around filesystems such as LVM or ZFS. Methods to "
+"securely destroy data will vary from one plugin to another, from one "
+"vendor's solution to another, and from one filesystem to another."
+msgstr "OpenStack Block Storage のプラグインは様々な方法でデータの保存を行います。多くのプラグインはベンダー又はストレージ技術に特化していますが、その他は LVM や ZFS といったファイルシステム辺りのより手作りのソリューションです。安全にデータを破壊する方法はプラグイン毎、ベンダーのソリューション毎、ファイルシステム毎に異なるでしょう。"
+
+#: ./doc/security-guide/ch046_data-residency.xml128(para)
+msgid ""
+"Some backends such as ZFS will support copy-on-write to prevent data "
+"exposure. In these cases, reads from unwritten blocks will always return "
+"zero. Other backends such as LVM may not natively support this, thus the "
+"Block Storage plug-in takes the responsibility to override previously "
+"written blocks before handing them to users. It is important to review what "
+"assurances your chosen volume backend provides and to see what mediations "
+"may be available for those assurances not provided."
+msgstr "ZFS のようないくつかのバックエンドは、データの漏洩を防ぐために copy-on-write に対応しています。この場合、まだ書き込まれていないブロックからの読み込みは常にゼロを返します。LVM のような他のバックエンドでは copy-on-write を標準でサポートしておらず、よって Block Storage プラグインが以前に書き込まれたブロックをユーザがアクセスする前に上書きする役割を担います。あなたが選択したボリュームバックエンドが提供する機能をレビューし、これらの機能が提供しない事についての回避策が利用できるかを調べる事は重要です。"
+
+#: ./doc/security-guide/ch046_data-residency.xml129(para)
+msgid ""
+"Finally, while not a feature of OpenStack, vendors and implementors may "
+"choose to add or support encryption of volumes. In this case, destruction of"
+" data is as simple as throwing away the key."
+msgstr "最後に、これは OpenStack の機能ではありませんが、ベンダーと開発者がボリュームの暗号化機能をサポートするか、あるいは追加可能であるかも知れません。この場合、データの破壊は単にキーを破棄するだけです。"
+
+#: ./doc/security-guide/ch046_data-residency.xml133(para)
+msgid ""
+"The creation and destruction of ephemeral storage will be somewhat dependent"
+" on the chosen hypervisor and the OpenStack Compute plug-in."
+msgstr "一時ストレージの作成・削除は選択したハイパーバイザや OpenStack Compute プラグインに依存するでしょう。"
+
+#: ./doc/security-guide/ch046_data-residency.xml134(para)
+msgid ""
+"The libvirt plug-in for compute may maintain ephemeral storage directly on a"
+" filesystem, or in LVM. Filesystem storage generally will not overwrite data"
+" when it is removed, although there is a guarantee that dirty extents are "
+"not provisioned to users."
+msgstr "compute 用の libvirt プラグインは、ファイルシステム又は LVM 上の一時ストレージを直接管理出来ます。ファイルシステムストレージは一般にデータを削除する際に上書きはしませんが、ユーザに対して汚れたエクステンドが用意されないという保証があります。"
+
+#: ./doc/security-guide/ch046_data-residency.xml135(para)
+msgid ""
+"When using LVM backed ephemeral storage, which is block-based, it is "
+"necessary that the OpenStack Compute software securely erases blocks to "
+"prevent information disclosure. There have in the past been information "
+"disclosure vulnerabilities related to improperly erased ephemeral block "
+"storage devices."
+msgstr "ブロックデバイスベースである LVM をバックエンドにした一時ストレージを使用する場合、OpenStack Compute は情報漏えいを防ぐために、安全にブロックを削除する必要があります。これらには、過去において、不適切な一時ブロックストレージデバイスの削除に関連する情報漏洩の脆弱性がありました。"
+
+#: ./doc/security-guide/ch046_data-residency.xml136(para)
+msgid ""
+"Filesystem storage is a more secure solution for ephemeral block storage "
+"devices than LVM as dirty extents cannot be provisioned to users. However, "
+"it is important to be mindful that user data is not destroyed, so it is "
+"suggested to encrypt the backing filesystem."
+msgstr "データが含まれたエクステンドがユーザに用意されないので、一時ブロックストレージデバイス用としてファイルシステムストレージは LVM より安全なソリューションです。しかしながら、ユーザデータが破壊されない事を覚えておく事は重要であり、このためバックエンドのファイルシステムの暗号化が提案されています。"
+
+#: ./doc/security-guide/ch046_data-residency.xml140(para)
+msgid ""
+"A bare metal server driver for Compute was under development and has since "
+"moved into a separate project called <link "
+"href=\"https://wiki.openstack.org/wiki/Ironic\">ironic</link>. At the time "
+"of this writing, ironic does not appear to address sanitization of tenant "
+"data resident the physical hardware."
+msgstr "Compute の物理サーバドライバは開発中だったのですが、<link href=\"https://wiki.openstack.org/wiki/Ironic\">ironic</link>と呼ばれる独立したプロジェクトに移管される事になりました。この文書の執筆時点では、ironic には物理ハードウェア上にあるテナントデータのサニタイズ機能はまだありません。"
+
+#: ./doc/security-guide/ch046_data-residency.xml147(para)
+msgid ""
+"Additionally, it is possible for tenants of a bare metal system to modify "
+"system firmware. TPM technology, described in <xref linkend=\"ch013_node-"
+"bootstrapping-idp44768\"/>, provides a solution for detecting unauthorized "
+"firmware changes."
+msgstr "加えて、物理マシンのテナントでは、システムファームウェアの修正が可能です。<xref linkend=\"ch013_node-bootstrapping-idp44768\"/>で説明されている TPM 技術は、許可されていないファームウェアの変更を検知する解決策を提供します。"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml8(title)
+msgid "Introduction to SSL/TLS"
+msgstr "SSL/TLSの導入"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml9(para)
+msgid ""
+"OpenStack services receive requests on behalf of users on public networks as"
+" well as from other internal services over management networks. Inter-"
+"service communications can also occur over public networks depending on "
+"deployment and architecture choices."
+msgstr "OpenStack のサービスは、管理ネットワーク経由の他の内部サービスからのリクエストと同様、パブリックネットワーク上のユーザによるリクエストを受信します。サービス間通信は、デプロイメントとアーキテクチャ選択によってはパブリックネットワーク経由で行われる事もあります。"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml10(para)
+msgid ""
+"While it is commonly accepted that data over public networks should be "
+"secured using cryptographic measures, such as Secure Sockets Layer or "
+"Transport Layer Security (SSL/TLS) protocols, it is insufficient to rely on "
+"security domain separation to protect internal traffic. Using a security-in-"
+"depth approach, we recommend securing all domains with SSL/TLS, including "
+"the management domain services. It is important that should a tenant escape "
+"their VM isolation and gain access to the hypervisor or host resources, "
+"compromise an API endpoint, or any other service, they must not be able to "
+"easily inject or capture messages, commands, or otherwise affect or control "
+"management capabilities of the cloud. SSL/TLS provides the mechanisms to "
+"ensure authentication, non-repudiation, confidentiality, and integrity of "
+"user communications to the OpenStack services and between the OpenStack "
+"services themselves."
+msgstr "パブリックネット上のデータは Secure Sockets Layer や Transport Layer Security (SSL/TLS)プロトコルのような暗号化方式を使用してセキュリティを確保すべきであるという事は一般に認識されている一方で、内部トラフィックの保護の為セキュリティドメイン分割に依存する事は不十分です。security-in-depth アプローチを用いて、管理ドメインサービスを含め、SSL/TLSを用いて全ドメインをセキュリティ確保する事を推奨します。テナントがVM分割を回避して、ハイパーバイザーやホストリソースへのアクセスを得て、APIエンドポイントやあらゆる他のサービスを妥協させる事は重大です。テナントが容易にインジェクトしたり、メッセージ・コマンド・その他クラウド上の管理機能に影響を与える又は制御する事が出来るようにすべきではありません。SSL/TLS は、OpenStack サービスへのユーザ通信や OpenStack サービス自体の相互間通信の認証、回避不能、秘密性、完全性を確保する仕組みを提供します。"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml11(para)
+msgid ""
+"Public Key Infrastructure (PKI) is a set of hardware, software, policies, "
+"and procedures required to operate a secure system that provides "
+"authentication, non-repudiation, confidentiality, and integrity. The core "
+"components of PKI are:"
+msgstr "Public Key Infrastructure (PKI)は認証、偽証不可、秘匿性、完全性を提供するセキュアなシステムを運用するために必要となるハードウェア、ソフトウェア、ポリシーのセットです。PKIのコアコンポーネントは以下の通り。"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml18(term)
+msgid "End entity"
+msgstr "エンドエンティティ"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml20(para)
+msgid "User, process, or system that is the subject of a certificate."
+msgstr "証明対象のユーザ、プロセス、システム。"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml25(term)
+msgid "Certification Authority (<glossterm>CA</glossterm>)"
+msgstr "認証局 (<glossterm>CA</glossterm>)"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml27(para)
+msgid ""
+"Defines certificate policies, management, and issuance of certificates."
+msgstr "証明ポリシーの定義、管理、証明書の発行。"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml32(term)
+msgid "Registration Authority (RA)"
+msgstr "登録局 (RA)"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml34(para)
+msgid ""
+"An optional system to which a CA delegates certain management functions."
+msgstr "CAが一定の管理機能を委任する追加システム。"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml39(term)
+msgid "Repository"
+msgstr "リポジトリ"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml41(para)
+msgid ""
+"Where the end entity certificates and certificate revocation lists are "
+"stored and looked up - sometimes referred to as the <emphasis "
+"role=\"italic\">certificate bundle</emphasis>."
+msgstr "エンドエンティティが証明され、証明書の廃止リストが保存・参照される場所 - 時々<emphasis role=\"italic\">証明バンドル(Certificate bundle)</emphasis>と呼ばれます。"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml49(term)
+msgid "Relying party"
+msgstr "信頼機関"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml51(para)
+msgid "The endpoint that is trusting that the CA is valid."
+msgstr "CAが有効であると証明するエンドポイント"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml56(para)
+msgid ""
+"PKI builds the framework on which to provide encryption algorithms, cipher "
+"modes, and protocols for securing data and authentication. We strongly "
+"recommend securing all services with Public Key Infrastructure (PKI), "
+"including the use of SSL/TLS for API endpoints. It is impossible for the "
+"encryption or signing of transports or messages alone to solve all these "
+"problems. Hosts themselves must be secure and implement policy, namespaces, "
+"and other controls to protect their private credentials and keys. However, "
+"the challenges of key management and protection do not reduce the necessity "
+"of these controls, or lessen their importance."
+msgstr "PKIはデータと認証をセキュアにする暗号アルゴリズム、暗号モード(cipher mode)、プロトコルの\nフレームワークをバンドルしています。APIエンドポイントの為のSSL/TLS 使用を含み、Public Key Infrastructure (PKI)を用いて、全サービスをセキュアにする事をお勧めします。暗号化や通信路・メッセージの署名の為に、これら全ての問題を解決する事は重要です。プライベート証明と鍵の保護の為、ホスト自身がセキュアで、ポリシー、ネームスペース、その他の制御を実装しなければなりません。しかし、キー管理や保護のチャレンジはこれらの制御の必要性を削減したり、その重要性を失ったりはしません。"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml58(title)
+msgid "Certification authorities"
+msgstr "認証局(CA)"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml59(para)
+msgid ""
+"Many organizations have an established Public Key Infrastructure with their "
+"own certification authority (CA), certificate policies, and management for "
+"which they should use to issue certificates for internal OpenStack users or "
+"services. Organizations in which the public security domain is Internet "
+"facing will additionally need certificates signed by a widely recognized "
+"public CA. For cryptographic communications over the management network, it "
+"is recommended one not use a public CA. Instead, we expect and recommend "
+"most deployments deploy their own internal CA."
+msgstr "多くの組織には、内部のOpenStackユーザやサービス用に証明書を発行する為に使用されるべき場所用の自身の認証局(CA)、証明ポリシー、管理を備えたPublic Key Infrastructure (PKI)が設置されています\n。加えて、パブリックセキュリティドメインがインターネットに面している所の組織は、幅広く認識された公共のCAにより署名された証明書が必要になるでしょう。管理ネットワーク上の暗号化通信用には、パブリックCAを使用しない事をお勧めします。代わりに、多くのデプロイでは自身の内部CAを設置していると思われますし、推奨します。"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml60(para)
+msgid ""
+"It is recommended that the OpenStack cloud architect consider using separate"
+" PKI deployments for internal systems and customer facing services. This "
+"allows the cloud deployer to maintain control of their PKI infrastructure "
+"and among other things makes requesting, signing and deploying certificates "
+"for internal systems easier. Advanced configurations may use separate PKI "
+"deployments for different security domains. This allows deployers to "
+"maintain cryptographic separation of environments, ensuring that "
+"certificates issued to one are not recognised by another."
+msgstr "OpenStackクラウドアーキテクトには、内部のシステムと顧客が接するサービス用に、分断されたPKIデプロイの使用を検討する事をお勧めします。これは、クラウドをデプロイする人が他の物が内部のシステム用に証明書を要求・署名・デプロイする事を容易にするPKIインフラを制御できるようにします。異なる設定は異なるセキュリティドメイン用にPKIデプロイを分割使用しても構いません。これは、デプロイする人が環境の暗号の分断を管理できるようにし、一方で発行された証明書が他方で認証されない事を保証します。"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml61(para)
+msgid ""
+"Certificates used to support SSL/TLS on internet facing cloud endpoints (or "
+"customer interfaces where the customer is not expected to have installed "
+"anything other than standard operating system provided certificate bundles) "
+"should be provisioned using Certificate Authorities that are installed in "
+"the operating system certificate bundle. Typical well known vendors include "
+"Verisign and Thawte but many others exist."
+msgstr "インターネットに面したクラウドのエンドポイント(あるいは証明書をバンドルした標準的なOS以外の何かがインストールされていると顧客が想定していない顧客インターフェース)上のSSL/TLSに対応に使用される証明書はOSの証明書バンドル中にインストールされるCAを用いてプロビジョニングされるべきです。通常、有名ベンダーにはベリサインやThawteを含みますが、他の多くのベンダーもあります。"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml62(para)
+msgid ""
+"There are many management, policy, and technical challenges around creating "
+"and signing certificates as such is an area where cloud architects or "
+"operators may wish to seek the advice of industry leaders and vendors in "
+"addition to the guidance recommended here."
+msgstr "証明書の作成・署名については多数の管理・ポリシー・技術的ハードルがあるため、証明書は、\nここで推奨されたガイドに加え、クラウドアーキテクトや運用者が工業リーダーやベンダのアドバイスを望みうる所です。"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml65(title)
+msgid "SSL/TLS libraries"
+msgstr "SSL/TLSライブラリ"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml66(para)
+msgid ""
+"Various components, services, and applications within the OpenStack "
+"ecosystem or dependencies of OpenStack are implemented and can be configured"
+" to use SSL/TLS libraries. The SSL/TLS and HTTP services within OpenStack "
+"are typically implemented using OpenSSL which has been proven to be fairly "
+"secure and has a module that has been validated for FIPS 140-2. However, "
+"keep in mind that each application or service can still introduce weaknesses"
+" in how they use the OpenSSL libraries."
+msgstr "OpenStackエコシステムやOpenStackが依存する様々なコンポーネント、サービス、アプリケーションはSSL/TLSライブラリを使用するよう実装され、設定ができるようになっています。OpenStack中のSSL/TLSとHTTPサービスは通常、非常にセキュアである事が証明され、FIPS 140-2用に検証されてきたOpenSSLを使用して実装されています。しかし、各アプリケーション又はサービスは、OpenSSLライブラリをどのように使用するかという点で、未だ脆弱性を招きうるという事を忘れないで下さい。"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml69(title)
+msgid "Cryptographic algorithms, cipher modes, and protocols"
+msgstr "暗号化アルゴリズム、暗号モード、プロトコル"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml70(para)
+msgid ""
+"We recommend only using TLS v1.1 or v1.2. SSLv3 and TLSv1.0 may be used for "
+"compatibility but we recommend using caution and only enabling these "
+"protocols if you have a strong requirement to do so. Other SSL/TLS versions,"
+" explicitly older versions, should not be used. These older versions include"
+" SSLv1 and SSLv2. As this book does not intend to be a thorough reference on"
+" cryptography we do not wish to be prescriptive about what specific "
+"algorithms or cipher modes you should enable or disable in your OpenStack "
+"services. However, there are some authoritative references we would like to "
+"recommend for further information:"
+msgstr "我々は TLS v1.1 又は v1.2 の使用のみ推奨します。SSL v3 と TLS v1.0 は互換性目的で使用出来ますが、我々は、注意深く、これらのプロトコルの有効化が強い要望としてある場合にのみ有効にする事をお勧めします。他のSSL/TLSバージョン(はっきり言えば古いバージョン)は使用すべきではありません。これらの古いバージョンには SSL v1 と v2 が含まれます。本書では暗号方式の初めから終わりまでの参考書を目指していない為、我々はあなたのOpenStackサービス中でどの特定アルゴリズムや暗号モードを有効・無効にすべきかについて指図する事を望みません。しかしながら、今後の情報としてお勧めしたい権威ある参考文献があります。"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml72(link)
+msgid "National Security Agency, Suite B Cryptography"
+msgstr "国家安全保障局、Suite B 暗号化"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml75(link)
+msgid "OWASP Guide to Cryptography"
+msgstr "OWASP Guide to Cryptography"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml78(link)
+msgid "OWASP Transport Layer Protection Cheat Sheet"
+msgstr "OWASP Transport Layer Protection Cheat Sheet"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml81(link)
+msgid ""
+"SoK: SSL and HTTPS: Revisiting past challenges and evaluating certificate "
+"trust model enhancements"
+msgstr "SoK: SSL and HTTPS: Revisiting past challenges and evaluating certificate trust model enhancements"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml84(link)
+msgid ""
+"The Most Dangerous Code in the World: Validating SSL Certificates in Non-"
+"Browser Software"
+msgstr "The Most Dangerous Code in the World: Validating SSL Certificates in Non-Browser Software"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml87(link)
+msgid "OpenSSL and FIPS 140-2"
+msgstr "OpenSSL and FIPS 140-2"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml92(title)
+msgid "Summary"
+msgstr "概要"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml93(para)
+msgid ""
+"Given the complexity of the OpenStack components and the number of "
+"deployment possibilities, you must take care to ensure that each component "
+"gets the appropriate configuration of SSL certificates, keys, and CAs. "
+"Subsequent sections discuss the following services:"
+msgstr "OpenStack コンポーネントの複雑さとデプロイの発展性を考慮すると、確実に各コンポーネントがSSL証明書・鍵・CAを適切に設定されている事に注意を払う必要があります。以下のサービスは、本書の後の章で議論します。"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml102(para)
+msgid "Compute API endpoints"
+msgstr "Compute APIエンドポイント"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml105(para)
+msgid "Identity API endpoints"
+msgstr "Identity APIエンドポイント"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml108(para)
+msgid "Networking API endpoints"
+msgstr "Networking APIエンドポイント"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml111(para)
+msgid "Storage API endpoints"
+msgstr "ストレージAPIエンドポイント"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml114(para)
+msgid "Messaging server"
+msgstr "メッセージングサーバー"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml117(para)
+msgid "Database server"
+msgstr "データベースサーバー"
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml123(para)
+msgid ""
+"This guide uses the term SSL as a shorthand to refer to these "
+"recommendations for SSL/TLS protocols."
+msgstr "このガイドは、SSL/TLSプロトコルに関する推奨を示す略称として、SSL という言葉を使用します。"
+
+#: ./doc/security-guide/ch009_case-studies.xml8(title)
+msgid "Case studies: system documentation"
+msgstr "ケーススタディ: システムのドキュメント"
+
+#: ./doc/security-guide/ch009_case-studies.xml9(para)
+msgid ""
+"In this case study we discuss how Alice and Bob would address their system "
+"documentation requirements. The documentation suggested above includes "
+"hardware and software records, network diagrams, and system configuration "
+"details."
+msgstr "今回のケーススタディでは、アリスとボブがシステムの文書要件にどのように対処していくか見ていきます。上記で述べた文書には、ハードウェアおよびソフトウェアの記録、ネットワーク図、システム設定の詳細などが含まれます。"
+
+#: ./doc/security-guide/ch009_case-studies.xml12(para)
+msgid ""
+"Alice needs detailed documentation to satisfy FedRamp requirements. She sets"
+" up a configuration management database (CMDB) to store information "
+"regarding all of the hardware, firmware, and software versions used "
+"throughout the cloud. She also creates a network diagram detailing the cloud"
+" architecture, paying careful attention to the security domains and the "
+"services that span multiple security domains."
+msgstr "アリスは、FedRam 要件を満たす詳細文書が必要です。構成管理データベース (CMDB) を設定して、クラウド全体で使用されるハードウェア、ファームウェア、ソフトウェアバージョンの情報を格納していきます。また、セキュリティドメインや、複数のセキュリティドメインにまたがるサービスに細心の注意を払い、クラウドアーキテクチャーの詳細を示したネットワーク図も作成します。"
+
+#: ./doc/security-guide/ch009_case-studies.xml13(para)
+msgid ""
+"Alice also needs to record each network service running in the cloud, what "
+"interfaces and ports it binds to, the security domains for each service, and"
+" why the service is needed. Alice decides to build automated tools to log "
+"into each system in the cloud over secure shell (SSH) using the <link "
+"href=\"http://fabfile.org\">Python Fabric library</link>. The tools collect "
+"and store the information in the CMDB, which simplifies the audit process."
+msgstr "アリスは、クラウドで実行中の各ネットワークサービス、バインド先のインターフェースやポート、各サービスに対するセキュリティドメイン、そのサービスが必要な理由を記録する必要があります。 <link href=\"http://fabfile.org\">Python Fabric ライブラリ</link>を使用して、セキュアシェル (SSH) でクラウド内の各システムにログインする自動化ツールを構築することにしました。このツールは、CMDB の情報を収集・格納して監査プロセスを簡素化します。"
+
+#: ./doc/security-guide/ch009_case-studies.xml17(para)
+msgid "In this case, Bob will approach these steps the same as Alice."
+msgstr "今回のケーススタディでは、ボブはアリスと同様の手段を取ります。"
+
 #. When image changes, this message will be marked fuzzy or untranslated for
 #. you.
 #. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch013_node-bootstrapping.xml64(None)
-#: ./doc/security-guide/ch013_node-bootstrapping.xml69(None)
+#: ./doc/security-guide/ch031_neutron-architecture.xml87(None)
+#: ./doc/security-guide/ch031_neutron-architecture.xml92(None)
 msgid ""
-"@@image: 'static/node-provisioning-pxe.png'; "
-"md5=51b76c5aced74f935490b37ba921dc43"
-msgstr "@@image: 'static/node-provisioning-pxe.png'; md5=51b76c5aced74f935490b37ba921dc43"
+"@@image: 'static/sdn-connections.png'; md5=1de9169834b34c83f574f2a1225b27f0"
+msgstr "@@image: 'static/sdn-connections.png'; md5=1de9169834b34c83f574f2a1225b27f0"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml12(title)
-msgid "Integrity life-cycle"
-msgstr "完全性ライフサイクル"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml13(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch031_neutron-architecture.xml109(None)
+#: ./doc/security-guide/ch031_neutron-architecture.xml114(None)
 msgid ""
-"We define integrity life cycle as a deliberate process that provides "
-"assurance that we are always running the expected software with the expected"
-" configurations throughout the cloud. This process begins with secure "
-"bootstrapping and is maintained through configuration management and "
-"security monitoring. This chapter provides recommendations on how to "
-"approach the integrity life-cycle process."
-msgstr "OpenStack では、完全性ライフサイクルを「クラウド全体にわたって想定されているソフトウェアが想定されている設定で常に実行されることを保証する計画的なプロセス」と定義しています。このプロセスは、セキュアなブートストラッピングで開始し、設定管理およびセキュリティ監視の機能により維持されます。本章では、完全性ライフサイクルプロセスのアプローチ方法について説明します。"
+"@@image: 'static/1aa-network-domains-diagram.png'; "
+"md5=135806775939d9e5e750264d8a5fe8de"
+msgstr "@@image: 'static/1aa-network-domains-diagram.png'; md5=135806775939d9e5e750264d8a5fe8de"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml21(title)
-msgid "Secure bootstrapping"
-msgstr "セキュアブートストラップ"
+#: ./doc/security-guide/ch031_neutron-architecture.xml8(title)
+msgid "Networking architecture"
+msgstr "Networking アーキテクチャ"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml22(para)
+#: ./doc/security-guide/ch031_neutron-architecture.xml9(para)
 msgid ""
-"Nodes in the cloudincluding compute, storage, network, service, and hybrid "
-"nodesshould have an automated provisioning process. This ensures that nodes "
-"are provisioned consistently and correctly. This also facilitates security "
-"patching, upgrading, bug fixing, and other critical changes. Since this "
-"process installs new software that runs at the highest privilege levels in "
-"the cloud, it is important to verify that the correct software is installed."
-" This includes the earliest stages of the boot process."
-msgstr "クラウド内のノード (コンピュート、ストレージ、ネットワーク、サービス、およびハイブリッドのノードを含む) には、自動プロビジョニングプロセスを使用すべきです。このプロセスにより、ノードが一貫して正しくプロビジョニングされます。また、セキュリティパッチの適用、アップグレード、バグ修正、その他の重要な変更が円滑に行われます。このプロセスにより、クラウド内において最高権限で実行される新規ソフトウェアがインストールされるので、正しいソフトウェアがインストールされることを検証することが重要となります。これには、ブートプロセスの最初期段階が含まれます。"
+"OpenStack Networking is a standalone service that often deploys several "
+"processes across a number of nodes. These processes interact with each other"
+" and other OpenStack services. The main process of the OpenStack Networking "
+"service is <systemitem class=\"service\">neutron-server</systemitem>, a "
+"Python daemon that exposes the OpenStack Networking API and passes tenant "
+"requests to a suite of plug-ins for additional processing."
+msgstr "OpenStack Networking は多数ノード間において幾つかのプロセスのデプロイにしばしば含まれる独立サービスです。OpenStack Networking サービスのメインプロセスは <systemitem class=\"service\">neutron-server</systemitem> で、これは OpenStack Networking API を提供し、追加処理用の適切なプラグインにテナントのリクエストを渡します。"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml31(para)
+#: ./doc/security-guide/ch031_neutron-architecture.xml17(para)
+msgid "The OpenStack Networking components are:"
+msgstr "OpenStack Networking のコンポーネントは以下のとおりです。"
+
+#: ./doc/security-guide/ch031_neutron-architecture.xml21(term)
 msgid ""
-"There are a variety of technologies that enable verification of these early "
-"boot stages. These typically require hardware support such as the trusted "
-"platform module (TPM), Intel Trusted Execution Technology (TXT), dynamic "
-"root of trust measurement (DRTM), and Unified Extensible Firmware Interface "
-"(UEFI) secure boot. In this book, we will refer to all of these collectively"
-" as <emphasis>secure boot technologies</emphasis>. We recommend using secure"
-" boot, while acknowledging that many of the pieces necessary to deploy this "
-"require advanced technical skills in order to customize the tools for each "
-"environment. Utilizing secure boot will require deeper integration and "
-"customization than many of the other recommendations in this guide. TPM "
-"technology, while common in most business class laptops and desktops for "
-"several years, and is now becoming available in servers together with "
-"supporting BIOS. Proper planning is essential to a successful secure boot "
-"deployment."
-msgstr "このような初期ブート段階の検証を可能にするさまざまな技術があります。通常は、Trusted Platform Module (TPM)、Intel Trusted Execution Technology (TXT)、Dynamic Root of Trust Measurement (DRTM)、Unified Extensible Firmware Interface (UEFI) などによるセキュアブートのハードウェアサポートが必要です。本ガイドでは、これらを総称して<emphasis>セキュアブートテクノロジー</emphasis>と呼びます。OpenStack ではセキュアブートの使用を推奨していますが、このデプロイに必要な諸作業には、各環境用にツールをカスタマイズするための高度の技術的スキルが必要である点を認識しています。セキュアブートの活用には、本ガイドに記載しているその他多くの推奨事項よりも深い統合とカスタマイズが必要になります。TPM テクノロジーはこの数年、大半のビジネスクラスのラップトップおよびデスクトップに通常搭載されていますが、BIOS のサポートとともにサーバーでも提供されるようになってきています。セキュアブートのデプロイには、適切な計画が不可欠です。"
+"neutron server (<systemitem class=\"service\">neutron-server</systemitem> "
+"and <systemitem class=\"service\">neutron-*-plugin</systemitem>)"
+msgstr "neutron サーバー (<systemitem class=\"service\">neutron-server</systemitem>、<systemitem class=\"service\">neutron-*-plugin</systemitem>)"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml47(para)
+#: ./doc/security-guide/ch031_neutron-architecture.xml25(para)
 msgid ""
-"A complete tutorial on secure boot deployment is beyond the scope of this "
-"book. Instead, here we provide a framework for how to integrate secure boot "
-"technologies with the typical node provisioning process. For additional "
-"details, cloud architects should refer to the related specifications and "
-"software configuration manuals."
-msgstr "セキュアブートのデプロイに関する完全なチュートリアルは、本書の範囲外なので、その代わりとして、標準的なノードプロビジョニングプロセスにセキュアブートテクノロジーを統合する方法の枠組みを提供します。クラウドアーキテクトが更に詳しい情報を確認するには、関連する仕様およびソフトウェア設定のマニュアルを参照することをお勧めします。"
+"This service runs on the network node to service the Networking API and its "
+"extensions. It also enforces the network model and IP addressing of each "
+"port. The neutron-server and plugin agents require access to a database for "
+"persistent storage and access to a message queue for inter-communication."
+msgstr "このサービスはネットワークノード上で実行され、Networking API とその拡張を提供します。これはまた、各ポートのネットワークモデルと IP アドレスを管理します。neutron-server とプラグインエージェントは、永続ストレージ用のデータベースへのアクセスと、内部通信用のメッセージキューへのアクセスを要求します。"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml54(title)
-msgid "Node provisioning"
-msgstr "ノードのプロビジョニング"
+#: ./doc/security-guide/ch031_neutron-architecture.xml35(term)
+msgid "plugin agent (<systemitem class=\"service\">neutron-*-agent</systemitem>)"
+msgstr "プラグインエージェント (<systemitem class=\"service\">neutron-*-agent</systemitem>)"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml55(para)
+#: ./doc/security-guide/ch031_neutron-architecture.xml38(para)
 msgid ""
-"Nodes should use Preboot eXecution Environment (PXE) for provisioning. This "
-"significantly reduces the effort required for redeploying nodes. The typical"
-" process involves the node receiving various boot stagesthat is "
-"progressively more complex software to execute from a server."
-msgstr "ノードは、プロビジョニングに Preboot eXecution Environment (PXE) を使用すべきです。これにより、ノードの再デプロイに必要な作業が大幅に軽減されます。標準的なプロセスでは、ノードがサーバーからさまざまなブート段階 (実行するソフトウェアが徐々に複雑化) を受信する必要があります。"
+"Runs on each compute node to manage local virtual switch (vswitch) "
+"configuration. The plug-in that you use determine which agents run. This "
+"service requires message queue access. <emphasis>Optional depending on "
+"plugin.</emphasis>"
+msgstr "ローカルの仮想スイッチ（vswitch）設定を管理する為に各 compute ノード上で実行されます。使用するプラグインにより、どのエージェントを実行するか決まります。このサービスはメッセージキューへのアクセスを必要とします。<emphasis>オプションのプラグインに依存します。</emphasis>"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml72(para)
+#: ./doc/security-guide/ch031_neutron-architecture.xml46(term)
+msgid "DHCP agent (<systemitem class=\"service\">neutron-dhcp-agent</systemitem>)"
+msgstr "DHCP エージェント (<systemitem class=\"service\">neutron-dhcp-agent</systemitem>)"
+
+#: ./doc/security-guide/ch031_neutron-architecture.xml49(para)
 msgid ""
-"We recommend using a separate, isolated network within the management "
-"security domain for provisioning. This network will handle all PXE traffic, "
-"along with the subsequent boot stage downloads depicted above. Note that the"
-" node boot process begins with two insecure operations: DHCP and TFTP. Then "
-"the boot process downloads over SSL the remaining information required to "
-"deploy the node. This information might include an initramfs and a kernel. "
-"This concludes by downloading the remaining information needed to deploy the"
-" node. This may be an operating system installer, a basic install managed by"
-" <link href=\"http://www.opscode.com/chef/\">Chef</link> or <link "
-"href=\"https://puppetlabs.com/\">Puppet</link>, or even a complete file "
-"system image that is written directly to disk."
-msgstr "プロビジョニングには、管理セキュリティドメイン内の別個の分離したネットワークを使用することを推奨します。このネットワークは、上記に示した後続のブート段階のダウンロードに加えて、すべての PXE トラフィックを処理します。 ノードのブートプロセスは、安全性の低い DHCP および TFTP の 2 つの操作で開始する点に注意してください。次にブートプロセスは、ノードのデプロイに必要な残りの情報を SSL を介してダウンロードします。この情報には、initramfs とカーネルが含まれる場合があります。このプロセスは、ノードのデプロイに必要な残りの情報のダウンロードで終了します。これは、オペレーティングシステムのインストーラー、<link href=\"http://www.opscode.com/chef/\">Chef</link> または <link href=\"https://puppetlabs.com/\">Puppet</link> によって管理される基本インストール、またはディスクに直接書き込まれた完全なファイルシステムイメージの場合もあります。"
+"Provides DHCP services to tenant networks. This agent is the same across all"
+" plug-ins and is responsible for maintaining DHCP configuration. The "
+"<systemitem class=\"service\">neutron-dhcp-agent</systemitem> requires "
+"message queue access."
+msgstr "テナントネットワークに DHCP サービスを提供します。このエージェントは全てのプラグインと同様で、DHCP 設定の管理を担当します。<systemitem class=\"service\">neutron-dhcp-agent</systemitem> はメッセージキューアクセスが必要です。"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml86(para)
+#: ./doc/security-guide/ch031_neutron-architecture.xml58(term)
+msgid "L3 agent (<systemitem class=\"service\">neutron-l3-agent</systemitem>)"
+msgstr "L3 エージェント (<systemitem class=\"service\">neutron-l3-agent</systemitem>)"
+
+#: ./doc/security-guide/ch031_neutron-architecture.xml61(para)
 msgid ""
-"While utilizing SSL during the PXE boot process is somewhat more "
-"challenging, common PXE firmware projects, such as iPXE, provide this "
-"support. Typically this involves building the PXE firmware with knowledge of"
-" the allowed SSL certificate chain(s) so that it can properly validate the "
-"server certificate. This raises the bar for an attacker by limiting the "
-"number of insecure, plain text network operations."
-msgstr "PXE ブートプロセス中に SSL を活用するのは若干困難ですが、iPXE などの一般的な PXE ファームウェアプロジェクトは、この機能をサポートしています。通常、この作業には、サーバーの証明書を適切に検証するための許可済み SSL 証明書チェーンについての知識を活用した PXE ファームウェア構築が伴います。これにより、安全性の低いプレーンテキストのネットワーク操作数が制限されるので、攻撃者に対するセキュリティレベルが高くなります。."
+"Provides L3/NAT forwarding for external network access of VMs on tenant "
+"networks. Requires message queue access. <emphasis>Optional depending on "
+"plug-in.</emphasis>"
+msgstr "テナントネットワーク上の VM において外部ネットワーク用 L3/NAT 転送を提供します。メッセージキューが必要です。<emphasis>プラグイン次第では別の物が必要になります。</emphasis>"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml96(title)
-msgid "Verified boot"
-msgstr "検証済みブート"
+#: ./doc/security-guide/ch031_neutron-architecture.xml69(term)
+msgid "network provider services (SDN server/services)"
+msgstr "ネットワークプロバイダーサービス (SDN サーバー/サービス)"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml97(para)
+#: ./doc/security-guide/ch031_neutron-architecture.xml71(para)
 msgid ""
-"In general, there are two different strategies for verifying the boot "
-"process. Traditional <emphasis>secure boot</emphasis> will validate the code"
-" run at each step in the process, and stop the boot if code is incorrect. "
-"<emphasis>Boot attestation</emphasis> will record which code is run at each "
-"step, and provide this information to another machine as proof that the boot"
-" process completed as expected. In both cases, the first step is to measure "
-"each piece of code before it is run. In this context, a measurement is "
-"effectively a SHA-1 hash of the code, taken before it is executed. The hash "
-"is stored in a platform configuration register (PCR) in the TPM."
-msgstr "ブートプロセスの検証には、通常 2 つの異なる戦略があります。従来の<emphasis>セキュアブート</emphasis>は、プロセスの各ステップに実行されるコードを検証し、コードが正しくない場合にはブートを中止します。<emphasis>ブートアテステーション</emphasis>は、どのステップでどのコードが実行されるかを記録し、ブートプロセスが想定通りに完了した証拠として、この情報を別のマシンに提供します。いずれのケースにおいても、第 1 のステップでは、実行前にコードの各要素を計測します。この場合、計測値は実質的にはコードの SHA-1 ハッシュで、実行前に取得されます。 このハッシュは、TPM 内の Platform Configuration Register (PCR) に保管されます。"
+"Provide additional networking services to tenant networks. These SDN "
+"services might interact with the <systemitem class=\"service\">neutron-"
+"server</systemitem>, <systemitem class=\"service\">neutron-"
+"plugin</systemitem>, and/or plugin-agents through REST APIs or other "
+"communication channels."
+msgstr "テナントネットワークを提供する追加のネットワークサービスを提供します。これらの SDN サービスは REST API  又は他の通信チャネルを介して、<systemitem class=\"service\">neutron-server</systemitem>、<systemitem class=\"service\">neutron-plugin</systemitem>、プラグインエージェントと交信するかも知れません。"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml109(para)
-msgid "Note: SHA-1 is used here because this is what the TPM chips support."
-msgstr "注記:  ここで SHA-1 を使用するのは、TPM チップが対応しているためです。"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml111(para)
+#: ./doc/security-guide/ch031_neutron-architecture.xml81(para)
 msgid ""
-"Each TPM has at least 24 PCRs. The TCG Generic Server Specification, v1.0, "
-"March 2005, defines the PCR assignments for boot-time integrity "
-"measurements. The table below shows a typical PCR configuration. The context"
-" indicates if the values are determined based on the node hardware "
-"(firmware) or the software provisioned onto the node. Some values are "
-"influenced by firmware versions, disk sizes, and other low-level "
-"information. Therefore, it is important to have good practices in place "
-"around configuration management to ensure that each system deployed is "
-"configured exactly as desired."
-msgstr "各 TPM には少なくとも 24 の PCR が含まれます。TCG Generic Server Specification ( v1.0、2005 年 3 月版) には、ブート時の完全性計測のための PCR の割り当てが定義されています。以下の表には、標準的な PCR 設定を記載しています。コンテキストには、その値がノードのハードウェア (ファームウェア) をベースに決定されるか、ノードにプロビジョニングされているソフトウェアをベースに決定されるかを示しています。一部の値は、ファームウェアのバージョンやディスクサイズ、その他の低レベルの情報によって影響を受けます。このため、設定管理の適切なプラクティスを整備し、デプロイするシステムが要望通りに設定されるようにしておくことが重要となります。"
+"The following figure shows an architectural and networking flow diagram of "
+"the OpenStack Networking components:"
+msgstr "以下の図は OpenStack Networking コンポーネント群の構造・ネットワークフローダイアグラムを示しています。"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml131(emphasis)
-msgid "Register"
-msgstr "レジスター"
+#: ./doc/security-guide/ch031_neutron-architecture.xml97(title)
+msgid "OpenStack Networking service placement on physical servers"
+msgstr "OpenStack Networking の配置と物理サービス"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml132(emphasis)
-msgid "What is measured"
-msgstr "計測の対象"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml135(emphasis)
-msgid "Context"
-msgstr "コンテキスト"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml138(para)
-msgid "PCR-00"
-msgstr "PCR-00"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml139(para)
+#: ./doc/security-guide/ch031_neutron-architecture.xml98(para)
 msgid ""
-"Core Root of Trust Measurement (CRTM), BIOS code, Host platform extensions"
-msgstr "Core Root of Trust Measurement (CRTM)、 BIOS コード、ホストプラットフォームの拡張機能"
+"This guide focuses on a standard architecture that includes a "
+"<emphasis>cloud controller</emphasis> host, a <emphasis>network</emphasis> "
+"host, and a set of <emphasis>compute</emphasis> hypervisors for running VMs."
+msgstr "このガイドは、<emphasis>クラウドコントローラ</emphasis>ホスト１台、<emphasis>ネットワーク</emphasis>ホスト１台、VMを実行する<emphasis>compute</emphasis>ハイパーバイザーの集合を含む標準的なアーキテクチャにフォーカスします。"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml141(para)
-#: ./doc/security-guide/ch013_node-bootstrapping.xml146(para)
-#: ./doc/security-guide/ch013_node-bootstrapping.xml151(para)
-#: ./doc/security-guide/ch013_node-bootstrapping.xml156(para)
-msgid "Hardware"
-msgstr "ハードウェア"
+#: ./doc/security-guide/ch031_neutron-architecture.xml105(title)
+msgid "Network connectivity of physical servers"
+msgstr "物理サーバのネットワーク接続性"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml144(para)
-msgid "PCR-01"
-msgstr "PCR-01"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml145(para)
-msgid "Host platform configuration"
-msgstr "ハードウェアプラットフォームの設定"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml149(para)
-msgid "PCR-02"
-msgstr "PCR-02"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml150(para)
-msgid "Option ROM code"
-msgstr "オプションの ROM コード"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml154(para)
-msgid "PCR-03"
-msgstr "PCR-03"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml155(para)
-msgid "Option ROM configuration and data"
-msgstr "オプションの ROM 設定およびデータ"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml159(para)
-msgid "PCR-04"
-msgstr "PCR-04"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml160(para)
-msgid "Initial Program Loader (IPL) code. For example, master boot record."
-msgstr "Initial Program Loader (IPL) コード (例: マスターブートレコード) "
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml162(para)
-#: ./doc/security-guide/ch013_node-bootstrapping.xml167(para)
-#: ./doc/security-guide/ch013_node-bootstrapping.xml172(para)
-#: ./doc/security-guide/ch013_node-bootstrapping.xml177(para)
-#: ./doc/security-guide/ch013_node-bootstrapping.xml183(para)
-#: ./doc/security-guide/ch013_node-bootstrapping.xml188(para)
-#: ./doc/security-guide/ch013_node-bootstrapping.xml193(para)
-msgid "Software"
-msgstr "ソフトウェア"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml165(para)
-msgid "PCR-05"
-msgstr "PCR-05"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml166(para)
-msgid "IPL code configuration and data"
-msgstr "IPL コードの設定およびデータ"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml170(para)
-msgid "PCR-06"
-msgstr "PCR-06"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml171(para)
-msgid "State transition and wake events"
-msgstr "状態遷移とウェイクイベント"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml175(para)
-msgid "PCR-07"
-msgstr "PCR-07"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml176(para)
-msgid "Host platform manufacturer control"
-msgstr "ホストプラットフォームのメーカーによる制御"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml180(para)
-msgid "PCR-08"
-msgstr "PCR-08"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml181(para)
-msgid "Platform specific, often kernel, kernel extensions, and drivers"
-msgstr "プラットフォーム固有、多くの場合はカーネル、カーネル拡張機能、ドライバー"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml186(para)
-msgid "PCR-09"
-msgstr "PCR-09"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml187(para)
-msgid "Platform specific, often Initramfs"
-msgstr "プラットフォーム固有、多くの場合は  Initramfs"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml191(para)
-msgid "PCR-10 to PCR-23"
-msgstr "PCR-10 から PCR-23"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml192(para)
-msgid "Platform specific"
-msgstr "プラットフォーム固有"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml198(para)
+#: ./doc/security-guide/ch031_neutron-architecture.xml118(para)
 msgid ""
-"At the time of this writing, very few clouds are using secure boot "
-"technologies in a production environment. As a result, these technologies "
-"are still somewhat immature. We recommend planning carefully in terms of "
-"hardware selection. For example, ensure that you have a TPM and Intel TXT "
-"support. Then verify how the node hardware vendor populates the PCR values. "
-"For example, which values will be available for validation. Typically the "
-"PCR values listed under the software context in the table above are the ones"
-" that a cloud architect has direct control over. But even these may change "
-"as the software in the cloud is upgraded. Configuration management should be"
-" linked into the PCR policy engine to ensure that the validation is always "
-"up to date."
-msgstr "本ガイドの執筆時点では、実稼働環境でセキュアブートテクノロジーを使用するクラウドはほとんどありませんでした。このため、これらのテクノロジーはまだ若干未成熟な状態です。ハードウェアは、慎重に計画した上で選択することを推奨します (例: TPM および Intel TXT の対応を確認するなど)。次に、ノードのハードウェアベンダーが PCR 値をどのように事前設定しているかを検証します (例: どの値を検証できるか)。上記の表のコンテキストにソフトウェアと記載されている PCR 値は通常、クラウドアーキテクトが直接コントロールできます。ただし、これらの値は、クラウド内のソフトウェアをアップグレードすると変更される場合があります。設定管理は、PCR ポリシーエンジン内にリンクして、検証を常に最新の状態 に確保すべきです。"
+"A standard OpenStack Networking setup has up to four distinct physical data "
+"center networks:"
+msgstr "標準的な OpenStack Networking セットアップは最大４つの物理データセンターネットワークがあります。"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml211(para)
+#: ./doc/security-guide/ch031_neutron-architecture.xml122(term)
+msgid "Management network"
+msgstr "管理ネットワーク"
+
+#: ./doc/security-guide/ch031_neutron-architecture.xml124(para)
 msgid ""
-"Each manufacturer must provide the BIOS and firmware code for their servers."
-" Different servers, hypervisors, and operating systems will choose to "
-"populate different PCRs. In most real world deployments, it will be "
-"impossible to validate every PCR against a known good quantity (\"golden "
-"measurement\"). Experience has shown that, even within a single vendor's "
-"product line, the measurement process for a given PCR may not be consistent."
-" We recommend establishing a baseline for each server and monitoring the PCR"
-" values for unexpected changes. Third-party software may be available to "
-"assist in the TPM provisioning and monitoring process, depending upon your "
-"chosen hypervisor solution."
-msgstr "各メーカーは、サーバーの BIOS とファームウェアのコードを提供する必要があります。サーバー、ハイパーバイザー、オペレーティングシステムによって、事前設定される PCR 値の選択が異なります。実際のデプロイメントではほとんどの場合、既知の適切な量 (「黄金の計測値」) と対照して各 PCR を検証することは不可能です。単一のベンダー の製品ラインの場合でも、一定の PCR の計測プロセスに一貫性がない場合があることが、経験により実証されています。各サーバーに基準値を定め、 PCR 値の予期せぬ変化を監視することを推奨します。選択したハイパーバイザーソリューションによっては、TPM プロビジョニングおよび監視プロセスを支援する サードパーティー製のソフトウェアが提供されている可能性があります。"
+"Used for internal communication between OpenStack Components. The IP "
+"addresses on this network should be reachable only within the data center "
+"and is considered the Management Security Domain."
+msgstr "OpenStack コンポーネント間の内部通信に使用されます。このネットワークの IP アドレスはデータセンター内でのみ到達可能であるべきです。管理セキュリティドメインで検討します。"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml223(para)
+#: ./doc/security-guide/ch031_neutron-architecture.xml132(term)
+msgid "Guest network"
+msgstr "ゲストネットワーク"
+
+#: ./doc/security-guide/ch031_neutron-architecture.xml134(para)
 msgid ""
-"The initial program loader (IPL) code will most likely be the PXE firmware, "
-"assuming the node deployment strategy outlined above. Therefore, the secure "
-"boot or boot attestation process can measure all of the early stage boot "
-"code, such as, bios, firmware, and the like, the PXE firmware, and the node "
-"kernel. Ensuring that each node has the correct versions of these pieces "
-"installed provides a solid foundation on which to build the rest of the node"
-" software stack."
-msgstr "上記のノードデプロイメントの戦略を前提とすると、Initial Program Loader (IPL) コードは、PXE ファームウェアである可能性が最も高く、このため、セキュアブートまたはブートアテステーションプロセスで、すべての初期段階のブートコード  (例: BIOS、ファームウェアなど)、PXE ファームウェア、およびノードのカーネルを計測することができます。各ノードにこれらの正しいバージョンがインストールされていることを確認することにより、残りのノードソフトウェアスタックを構築する土台となる強固な基盤が提供されます。"
+"Used for VM data communication within the cloud deployment. The IP "
+"addressing requirements of this network depend on the OpenStack Networking "
+"plug-in in use and the network configuration choices of the virtual networks"
+" made by the tenant. This network is considered the Guest Security Domain."
+msgstr "クラウドデプロイ中の VM データ通信に使用されます。このネットワークの IP アドレス要件は、使用中の OpenStack Networking プラグインとテナントにより作成される仮想ネットワークのネットワーク設定の選定に依存します。このネットワークはゲストセキュリティドメインで検討します。"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml231(para)
+#: ./doc/security-guide/ch031_neutron-architecture.xml144(term)
+msgid "External network"
+msgstr "外部ネットワーク"
+
+#: ./doc/security-guide/ch031_neutron-architecture.xml146(para)
 msgid ""
-"Depending on the strategy selected, in the event of a failure the node will "
-"either fail to boot or it can report the failure back to another entity in "
-"the cloud. For secure boot, the node will fail to boot and a provisioning "
-"service within the management security domain must recognize this and log "
-"the event. For boot attestation, the node will already be running when the "
-"failure is detected. In this case the node should be immediately quarantined"
-" by disabling its network access. Then the event should be analyzed for the "
-"root cause. In either case, policy should dictate how to proceed after a "
-"failure. A cloud may automatically attempt to re-provision a node a certain "
-"number of times. Or it may immediately notify a cloud administrator to "
-"investigate the problem. The right policy here will be deployment and "
-"failure mode specific."
-msgstr "選択した戦略に応じて、障害発生時にノードがブートに失敗するか、クラウド内の別のエンティティに障害を報告することができます。セキュアブートの場合には、ノードがブートに失敗し、管理セキュリティドメイン内のプロビジョニングサービスがこの問題を認識してイベントログを記録する必要があります。ブートアテステーションの場合には、障害検出時にはノードがすでに稼働している状態です。この場合、ネットワークアクセスを無効にすることによってノードの検疫を直ちに行った後に、イベントを解析して根本原因を特定するべきです。いずれの場合も、ポリシーにより、障害発生後の対処方法を指示する必要があります。クラウドが、特定の回数、ノードの再プロビジョニングを自動的に試みるようにしたり、問題を調査するようにクラウド管理者に直ちに通知するようにすることができます。この場合に適正となるポリシーは、デプロイメントと障害のモードによって異なります。 "
+"Used to provide VMs with Internet access in some deployment scenarios. The "
+"IP addresses on this network should be reachable by anyone on the Internet "
+"and is considered to be in the Public Security Domain."
+msgstr "幾つかのデプロイシナリオ中のインターネットアクセスを持つVMを提供する為に使用されます。このネットワーク上の IP アドレスはインターネット上の誰もが通信可能です。パブリックセキュリティドメインで検討します。"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml247(title)
-msgid "Node hardening"
-msgstr "ノードのセキュリティ強化機能"
+#: ./doc/security-guide/ch031_neutron-architecture.xml154(term)
+msgid "API network"
+msgstr "API ネットワーク"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml248(para)
+#: ./doc/security-guide/ch031_neutron-architecture.xml156(para)
 msgid ""
-"At this point we know that the node has booted with the correct kernel and "
-"underlying components. There are many paths for hardening a given operating "
-"system deployment. The specifics on these steps are outside of the scope of "
-"this book. We recommend following the guidance from a hardening guide "
-"specific to your operating system. For example, the <link "
-"href=\"http://iase.disa.mil/stigs/\">security technical implementation "
-"guides</link> (STIG) and the <link "
-"href=\"http://www.nsa.gov/ia/mitigation_guidance/security_configuration_guides/\">NSA"
-" guides</link> are useful starting places."
-msgstr "この時点で、ノードが正しいカーネルと配下のコンポーネントでブートしていることが分かります。オペレーティングシステムのデプロイメントのセキュリティを強化するには、数多くの方法があります。これらの手順についての詳しい説明は本書の範囲外です。お使いのオペレーティングシステム固有のセキュリティ強化ガイドのアドバイスに従うことを推奨します。例えば、<link href=\"http://iase.disa.mil/stigs/\">security technical implementation guides</link> (STIG) や <link href=\"http://www.nsa.gov/ia/mitigation_guidance/security_configuration_guides/\">NSA guides</link> を最初に参考にすると役立ちます。"
+"Exposes all OpenStack APIs, including the OpenStack Networking API, to "
+"tenants. The IP addresses on this network should be reachable by anyone on "
+"the Internet. This may be the same network as the external network, as it is"
+" possible to create a subnet for the external network that uses IP "
+"allocation ranges to use only less than the full range of IP addresses in an"
+" IP block. This network is considered the Public Security Domain."
+msgstr "テナントに OpenStack Networking API を含む全 OpenStack API を晒します。このネットワーク上の IP アドレスはインターネット上の誰もがアクセス可能であるべきです。これは外部ネットワークと同じネットワークであっても構いません。外部ネットワーク用に、IP ブロック中の全 IP アドレス範囲より少ない部分を使う為の IP 割当範囲を使用するサブネットを作成する事が出来るからです。このネットワークはパブロックセキュリティドメインで検討します。"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml258(para)
+#: ./doc/security-guide/ch031_neutron-architecture.xml169(para)
 msgid ""
-"The nature of the nodes makes additional hardening possible. We recommend "
-"the following additional steps for production nodes:"
-msgstr "ノードはその性質上、追加のセキュリティ強化が可能です。実稼働用のノードには、次の追加手順に従うことを推奨します。"
+"For additional information see the <link href=\"http://docs.openstack.org"
+"/admin-guide-cloud/content/ch_networking.html\">Networking chapter</link> in"
+" the <citetitle>OpenStack Cloud Administrator Guide</citetitle>."
+msgstr "更なる情報は、<citetitle>OpenStack Cloud Administrator Guide</citetitle> 中の <link href=\"http://docs.openstack.org/admin-guide-cloud/content/ch_networking.html\">Networking</link> の章を参照して下さい。"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml263(para)
+#: ./doc/security-guide/ch011_management-introduction.xml8(title)
+msgid "Management introduction"
+msgstr "管理の概要"
+
+#: ./doc/security-guide/ch011_management-introduction.xml9(para)
 msgid ""
-"Use a read-only file system where possible. Ensure that writeable file "
-"systems do not permit execution. This can be handled through the mount "
-"options provided in <filename>/etc/fstab</filename>."
-msgstr "可能な場合には、読み取り専用のファイルシステムを使用します。書き込みが可能なファイルシステムでは、実行が許可されないようにします。これは、<filename>/etc/fstab</filename> で指定するマウントオプションを使用して対処することが可能です。"
+"A cloud deployment is a living system. Machines age and fail, software "
+"becomes outdated, vulnerabilities are discovered. When errors or omissions "
+"are made in configuration, or when software fixes must be applied, these "
+"changes must be made in a secure, but convenient, fashion. These changes are"
+" typically solved through configuration management."
+msgstr "クラウドデプロイメントは生きているシステムです。機械は老朽化して障害が発生し、ソフトウェアは古くなり、脆弱性が発見されます。設定にエラーや抜けがあった場合、ソフトウェアの修正を適用する必要が出た場合、セキュアかつ利便的に、これらの変更を加える必要があります。通常、これらの変更は構成管理などで解決されます。"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml269(para)
+#: ./doc/security-guide/ch011_management-introduction.xml10(para)
 msgid ""
-"Use a mandatory access control policy to contain the instances, the node "
-"services, and any other critical processes and data on the node. See the "
-"discussions on sVirt / SELinux and AppArmor below."
-msgstr "強制アクセス制御ポリシーを使用して、インスタンス、ノードサービス、その他の重要なプロセスおよびノード上のデータが含まれるようにします。以下に記載の sVirt / SELinux および AppArmor についての説明を参照してください。"
+"Likewise, it is important to protect the cloud deployment from being "
+"configured or manipulated by malicious entities. With many systems in a "
+"cloud employing compute and networking virtualization, there are distinct "
+"challenges applicable to OpenStack which must be addressed through integrity"
+" lifecycle management."
+msgstr "同様に、悪意のある組織により設定または操作されないように、クラウドデプロイメントを保護することが重要です。コンピュートやネットワークの仮想化を採用するクラウド内の多くのシステムでは、OpenStack に適用される問題が明らかに存在し、整合性のライフサイクル管理で対応していく必要があります。"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml275(para)
+#: ./doc/security-guide/ch011_management-introduction.xml11(para)
 msgid ""
-"Remove any unnecessary software packages. This should result in a very "
-"stripped down installation because a compute node has a relatively small "
-"number of dependencies."
-msgstr "不要なソフトウェアパッケージは削除します。これにより、コンピュートノードの依存関係が比較的少なくなるので、インストールを小さく絞ることができます。"
+"Finally, administrators must perform command and control over the cloud for "
+"various operational functions. It is important these command and control "
+"facilities are understood and secured."
+msgstr "最後に、管理者は様々なオペレーション機能に対してクラウド上で指揮統制を行う必要があります。これらの指揮統制機能を理解、確保することが重要です。"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml281(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch042_database-overview.xml18(None)
+#: ./doc/security-guide/ch042_database-overview.xml21(None)
 msgid ""
-"Finally, the node kernel should have a mechanism to validate that the rest "
-"of the node starts in a known good state. This provides the necessary link "
-"from the boot validation process to validating the entire system. The steps "
-"for doing this will be deployment specific. As an example, a kernel module "
-"could verify a hash over the blocks comprising the file system before "
-"mounting it using <link "
-"href=\"https://code.google.com/p/cryptsetup/wiki/DMVerity\">dm-"
-"verity</link>."
-msgstr "最後に、ノードのカーネルには、残りのノードが既知の良好な状態で起動することを検証するメカニズムを取り入れるべきです。これにより、ブート検証プロセスからシステム全体の検証に至るまでの必要なリンクが提供されます。手順はデプロイメントによって異なります。例えば、カーネルモジュールは、<link href=\"https://code.google.com/p/cryptsetup/wiki/DMVerity\">dm-verity</link> を使用して、ファイルシステムをマウントする前に、そのファイルシステムを構成するブロック上のハッシュを検証することができます。"
+"@@image: 'static/databaseusername.png'; md5=a6a5dadedbc1517069ca388c7ac5940a"
+msgstr "@@image: 'static/databaseusername.png'; md5=a6a5dadedbc1517069ca388c7ac5940a"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml293(title)
-msgid "Runtime verification"
-msgstr "ランタイムの検証"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml294(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch042_database-overview.xml42(None)
+#: ./doc/security-guide/ch042_database-overview.xml45(None)
 msgid ""
-"Once the node is running, we need to ensure that it remains in a good state "
-"over time. Broadly speaking, this includes both configuration management and"
-" security monitoring. The goals for each of these areas are different. By "
-"checking both, we achieve higher assurance that the system is operating as "
-"desired. We discuss configuration management in the management section, and "
-"security monitoring below."
-msgstr "ノードが稼働したら、長時間にわたって良好な状態で稼働を継続するように確保する必要があります。大まかに言うと、これには設定管理とセキュリティ監視が含まれます。これらの各領域の目標は異なります。両方を確認することにより、システムが希望通りに稼働していることをより確実に保証します。設定管理については、管理のセクションおよび次のセキュリティ監視で説明します。"
+"@@image: 'static/databaseusernamessl.png'; "
+"md5=9c43242c47eb159b6f61ac41f3d8bced"
+msgstr "@@image: 'static/databaseusernamessl.png'; md5=9c43242c47eb159b6f61ac41f3d8bced"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml302(title)
-msgid "Intrusion detection system"
-msgstr "侵入検知システム"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml303(para)
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch042_database-overview.xml104(None)
+#: ./doc/security-guide/ch042_database-overview.xml107(None)
 msgid ""
-"Host-based intrusion detection tools are also useful for automated "
-"validation of the cloud internals. There are a wide variety of host-based "
-"intrusion detection tools available. Some are open source projects that are "
-"freely available, while others are commercial. Typically these tools analyze"
-" data from a variety of sources and produce security alerts based on rule "
-"sets and/or training. Typical capabilities include log analysis, file "
-"integrity checking, policy monitoring, and rootkit detection. More advanced "
-"-- often custom -- tools can validate that in-memory process images match "
-"the on-disk executable and validate the execution state of a running "
-"process."
-msgstr "ホストベースの侵入検知ツールは、クラウド内部の検証の自動化にも役立ちます。ホストベースの侵入検知ツールにはさまざまな種類があります。オープンソースで自由に利用できるツールもあれば、商用のツールもあります。通常、これらのツールは、さまざまなソースからデータを分析し、ルールセットやトレーニングに基づいてセキュリティ警告を出します。標準的な機能には、ログ解析、ファイルの完全性チェック、ポリシー監視、ルートキット検出などがあります。また、より高度なツール (カスタムの場合が多い) を使用すると、インメモリープロセスイメージがオンディスクの実行可能ファイルと一致するかどうかを確認して、実行中のプロセスの実行状態を検証することができます。"
+"@@image: 'static/novaconductor.png'; md5=dbc1ba139bd1af333f0415bb48704843"
+msgstr "@@image: 'static/novaconductor.png'; md5=dbc1ba139bd1af333f0415bb48704843"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml315(para)
+#: ./doc/security-guide/ch042_database-overview.xml8(title)
+msgid "Database access control"
+msgstr "データベースアクセス制御"
+
+#: ./doc/security-guide/ch042_database-overview.xml9(para)
 msgid ""
-"One critical policy decision for a cloud architect is what to do with the "
-"output from a security monitoring tool. There are effectively two options. "
-"The first is to alert a human to investigate and/or take corrective action. "
-"This could be done by including the security alert in a log or events feed "
-"for cloud administrators. The second option is to have the cloud take some "
-"form of remedial action automatically, in addition to logging the event. "
-"Remedial actions could include anything from re-installing a node to "
-"performing a minor service configuration. However, automated remedial action"
-" can be challenging due to the possibility of false positives."
-msgstr "セキュリティ監視ツールの出力の処理方法は、クラウドアーキテクトにとっての重要なポリシー決定の一つです。オプションは実質的に 2 つあります。第 1 のオプションは、問題を調査して修正措置を取るように、人間に警告を発する方法です。これは、クラウド管理者向けのログまたはイベントのフィードにセキュリティ警告を組み込むことによって可能となります。第 2 のオプションは、イベントのログ記録に加えて、クラウドが何らかの形の修復措置を自動的に実行するように設定する方法です。修復措置にはノードの再インストールから、マイナーなサービス設定の実行まで含めることができます。ただし、自動修復措置は、誤検知の可能性があるため、困難となる場合があります。"
+"Each of the core OpenStack services (Compute, Identity, Networking, Block "
+"Storage) store state and configuration information in databases. In this "
+"chapter, we discuss how databases are used currently in OpenStack. We also "
+"explore security concerns, and the security ramifications of database "
+"backend choices."
+msgstr "それぞれの OpenStack コアサービス (Compute, Identity, Networking, Block Storage) は、状態や設定に関する情報をデータベースに保存します。本章では、データベースが現在 OpenStack でどのように使用されているのかを議論します。セキュリティの考慮事項、データベースバックエンドの選択によるセキュリティへの影響についても説明します。"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml326(para)
+#: ./doc/security-guide/ch042_database-overview.xml11(title)
+msgid "OpenStack database access model"
+msgstr "OpenStack データベースアクセスモデル"
+
+#: ./doc/security-guide/ch042_database-overview.xml12(para)
 msgid ""
-"False positives occur when the security monitoring tool produces a security "
-"alert for a benign event. Due to the nature of security monitoring tools, "
-"false positives will most certainly occur from time to time. Typically a "
-"cloud administrator can tune security monitoring tools to reduce the false "
-"positives, but this may also reduce the overall detection rate at the same "
-"time. These classic trade-offs must be understood and accounted for when "
-"setting up a security monitoring system in the cloud."
-msgstr "誤検知は、セキュリティ監視ツールが害のないイベントのセキュリティ警告を出した場合に発生します。セキュリティ警告ツールの性質上、時々誤検知が発生することは間違いありません。通常、クラウド管理者は、セキュリティ監視ツールを微調整して、誤検知を少なくすることができますが、これにより、全体的な検知率も同時に下がる場合があります。このような典型的トレードオフを理解し、クラウドにセキュリティ管理システムをセットアップする際には考慮に入れる必要があります。"
+"All of the services within an OpenStack project access a single database. "
+"There are presently no reference policies for creating table or row based "
+"access restrictions to the database."
+msgstr "OpenStack プロジェクトの中にあるすべてのサービスは単一のデータベースにアクセスします。データベースへのテーブルの作成や行単位のアクセス制限に関する明確なポリシーは今のところありません。"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml335(para)
+#: ./doc/security-guide/ch042_database-overview.xml13(para)
 msgid ""
-"The selection and configuration of a host-based intrusion detection tool is "
-"highly deployment specific. We recommend starting by exploring the following"
-" open source projects which implement a variety of host-based intrusion "
-"detection and file monitoring features."
-msgstr "ホストベースの侵入検知ツールの選択と設定はデプロイメントによって大幅に異なります。多様なホストベースの侵入検知/ファイル監視機能を実装する以下のオープンソースプロジェクトの検討から開始することをお勧めします。"
+"There are no general provisions for granular control of database operations "
+"in OpenStack. Access and privileges are granted simply based on whether a "
+"node has access to the database or not. In this scenario, nodes with access "
+"to the database may have full privileges to DROP, INSERT, or UPDATE "
+"functions."
+msgstr "OpenStack には、データベース操作の詳細な制御に関する一般的な決まりがありません。アクセス権と権限は単にノードがデータベースにアクセスするかしないかに基づいて与えられます。このシナリオでは、データベースにアクセスするノードは、DROP、INSERT、UPDATE 関数の完全な権限を持っているでしょう。"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml343(link)
-msgid "OSSEC"
-msgstr "OSSEC"
+#: ./doc/security-guide/ch042_database-overview.xml15(title)
+msgid "Granular access control"
+msgstr "精細なアクセス制御"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml347(link)
-msgid "Samhain"
-msgstr "Samhain"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml352(link)
-msgid "Tripwire"
-msgstr "Tripwire"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml356(link)
-msgid "AIDE"
-msgstr "AIDE"
-
-#: ./doc/security-guide/ch013_node-bootstrapping.xml359(para)
+#: ./doc/security-guide/ch042_database-overview.xml16(para)
 msgid ""
-"Network intrusion detection tools complement the host-based tools. OpenStack"
-" doesn't have a specific network IDS built-in, but OpenStack Networking "
-"provides a plug-in mechanism to enable different technologies through the "
-"Networking API. This plug-in architecture will allow tenants to develop API "
-"extensions to insert and configure their own advanced networking services "
-"like a firewall, an intrusion detection system, or a VPN between the VMs."
-msgstr "ネットワーク侵入検知ツールは、ホストベースのツールを補完します。OpenStack には、特定のネットワーク IDS は組み込まれていませんが、OpenStack Networking は、Networking API を使用して異なるテクノロジーを有効にするプラグインメカニズムを提供しています。このプラグインのアーキテクチャーにより、テナントは API 拡張機能を開発して、ファイアウォール、侵入検知システム、仮想マシン間の VPN などの独自の高度なネットワークサービスを挿入/設定することができます。"
+"By default, each of the OpenStack services and their processes access the "
+"database using a shared set of credentials. This makes auditing database "
+"operations and revoking access privileges from a service and its processes "
+"to the database particularly difficult."
+msgstr "OpenStack の各サービスとそれらのプロセスはデフォルトで、共有クレデンシャルを使用してデータベースにアクセスします。これにより、データベース操作の監査および、サービスとそのプロセスからデータベースへのアクセス権の剥奪が特に難しくなります。"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml367(para)
+#: ./doc/security-guide/ch042_database-overview.xml26(title)
+#: ./doc/security-guide/ch042_database-overview.xml99(title)
+msgid "Nova-conductor"
+msgstr "Nova-conductor"
+
+#: ./doc/security-guide/ch042_database-overview.xml27(para)
 msgid ""
-"Similar to host-based tools, the selection and configuration of a network-"
-"based intrusion detection tool is deployment specific. <link "
-"href=\"http://www.snort.org/\">Snort</link> is the leading open source "
-"networking intrusion detection tool, and a good starting place to learn "
-"more."
-msgstr "ホストベースのツールと同様に、ネットワークベースの侵入検知ツールはデプロイメントによって異なります。 <link href=\"http://www.snort.org/\">Snort</link> は、先進的なオープンソースのネットワーク侵入検知ツールです。このツールを起点として、更に知識を深めてゆくとよいでしょう。"
+"The compute nodes are the least trusted of the services in OpenStack because"
+" they host tenant instances. The <systemitem class=\"service\">nova-"
+"conductor</systemitem> service has been introduced to serve as a database "
+"proxy, acting as an intermediary between the compute nodes and the database."
+" We discuss its ramifications later in this chapter."
+msgstr "コンピュートノードは、プロジェクトのインスタンスをホストするため、OpenStack で最も信頼できないサービスです。<systemitem class=\"service\">nova-conductor</systemitem> サービスは、コンピュートノードとデータベースの中継役として動作する、データベースプロキシとして処理するために導入されました。その結果について本章で後ほど議論します。"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml373(para)
+#: ./doc/security-guide/ch042_database-overview.xml28(para)
+msgid "We strongly recommend:"
+msgstr "以下の事項を強く推奨します。"
+
+#: ./doc/security-guide/ch042_database-overview.xml30(para)
+msgid "All database communications be isolated to a management network"
+msgstr "すべてのデータベース通信の管理ネットワークへの分離"
+
+#: ./doc/security-guide/ch042_database-overview.xml33(para)
+msgid "Securing communications using SSL"
+msgstr "SSL を使用したセキュア通信"
+
+#: ./doc/security-guide/ch042_database-overview.xml36(para)
 msgid ""
-"There are a few important security considerations for network and host-based"
-" intrusion detection systems."
-msgstr "ネットワークおよびホストベースの侵入検知システムには、いくつかの重要なセキュリティ課題があります。"
+"Creating unique database user accounts per OpenStack service endpoint "
+"(illustrated below)"
+msgstr "OpenStack サービスのエンドポイントごとに一意なデータベースユーザーアカウントの作成 (下図)"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml377(para)
+#: ./doc/security-guide/ch042_database-overview.xml52(title)
+msgid "Database authentication and access control"
+msgstr "データベースの認証とアクセス制御"
+
+#: ./doc/security-guide/ch042_database-overview.xml53(para)
 msgid ""
-"It is important to consider the placement of the Network IDS on the cloud "
-"(for example, adding it to the network boundary and/or around sensitive "
-"networks). The placement depends on your network environment but make sure "
-"to monitor the impact the IDS may have on your services depending on where "
-"you choose to add it. Encrypted traffic, such as SSL, cannot generally be "
-"inspected for content by a Network IDS. However, the Network IDS may still "
-"provide some benefit in identifying anomalous unencrypted traffic on the "
-"network."
-msgstr "クラウドにネットワーク IDS の配置を検討することは重要です  (例: ネットワーク境界や機密性の高いのネットワークに追加するなど)。 配置はネットワーク環境によって異なりますが、追加する場所によって IDS がサービスにもたらす可能性のある影響を確実に監視するようにしてください。通常 ネットワーク IDS は、SSL などの暗号化トラフィックを調査することはできませんが、ネットワーク上の異常な非暗号化トラフィックを特定するメリットを提供することができます。"
+"Given the risks around access to the database, we strongly recommend that "
+"unique database user accounts be created per node needing access to the "
+"database. Doing this facilitates better analysis and auditing for ensuring "
+"compliance or in the event of a compromise of a node allows you to isolate "
+"the compromised host by removing access for that node to the database upon "
+"detection. When creating these per service endpoint database user accounts, "
+"care should be taken to ensure that they are configured to require SSL. "
+"Alternatively, for increased security it is recommended that the database "
+"accounts be configured using X.509 certificate authentication in addition to"
+" usernames and passwords."
+msgstr "データベースにアクセスする辺りにリスクがあるため、データベースにアクセスする必要があるノードごとに一意なデータベースユーザーアカウントを作成することを強く推奨します。この機能を実行することにより、コンプライアンスを保証するため、またはノードのセキュリティ被害にあった際に分析および監査をより良くできます。また、検知した際に被害にあったノードからデータベースへのアクセス権を削除することにより、被害にあったホストを分離できます。サービスのエンドポイントのデータベースユーザーアカウントごとにこれらを作成するとき、これらに SSL を要求するよう確実に設定することに注意してください。代わりに、セキュリティを向上させるために、データベースアカウントがユーザー名とパスワードに加えて X.509 証明書認証を使用するよう設定することを推奨します。"
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml389(para)
+#: ./doc/security-guide/ch042_database-overview.xml55(title)
+msgid "Privileges"
+msgstr "権限"
+
+#: ./doc/security-guide/ch042_database-overview.xml56(para)
 msgid ""
-"In some deployments it may be required to add host-based IDS on sensitive "
-"components on security domain bridges. A host-based IDS may detect anomalous"
-" activity by compromised or unauthorized processes on the component. The IDS"
-" should transmit alert and log information on the Management network."
-msgstr "一部のデプロイメントでは、ホストベースの IDS をセキュリティドメインブリッジ上の機密性の高いコンポーネントに追加する必要がある場合があります。ホストベースの IDS は、そのコンポーネント上の侵害された、あるいは許可されていないプロセスによる異常なアクティビティを検知することができます。IDS は管理ネットワーク上で警告およびログ情報を伝送すべきです。"
+"A separate database administrator (DBA) account should be created and "
+"protected that has full privileges to create/drop databases, create user "
+"accounts, and update user privileges. This simple means of separation of "
+"responsibility helps prevent accidental misconfiguration, lowers risk and "
+"lowers scope of compromise."
+msgstr "データベースの作成と削除、ユーザーアカウントの作成、ユーザーの権限の更新に関する完全な権限を持つ、別々のデータベース管理者 (DBA) アカウントが作成され、保護されるべきです。これは、不注意な設定ミスを防ぎ、リスクを減らし、被害の範囲を小さくする、責任の分離を実現する簡単な方法です。"
 
-#: ./doc/security-guide/ch038_transport-security.xml8(title)
-msgid "Messaging security"
-msgstr "メッセージングのセキュリティ"
-
-#: ./doc/security-guide/ch038_transport-security.xml9(para)
+#: ./doc/security-guide/ch042_database-overview.xml57(para)
 msgid ""
-"This chapter discusses security hardening approaches for the three most "
-"common message queuing solutions use in OpenStack: RabbitMQ, Qpid, and "
-"ZeroMQ."
-msgstr "この章では、OpenStack で使用される最も一般的なメッセージキュー製品である、Rabbit MQ、Qpid、ZeroMQ の堅牢化アプローチについて説明します。"
+"The database user accounts created for the OpenStack services and for each "
+"node should have privileges limited to just the database relevant to the "
+"service where the node is a member."
+msgstr "データベースユーザーアカウントは OpenStack サービスのために作成され、ノードがメンバーであるサービスに関連するデータベースだけに制限された権限を持つ各ノードのために作成されます。"
 
-#: ./doc/security-guide/ch038_transport-security.xml11(title)
-msgid "Messaging transport security"
-msgstr "メッセージ通信路のセキュリティ"
+#: ./doc/security-guide/ch042_database-overview.xml61(title)
+msgid "Require user accounts to require SSL transport"
+msgstr "SSL 通信利用のための必須ユーザーアカウント"
 
-#: ./doc/security-guide/ch038_transport-security.xml12(para)
+#: ./doc/security-guide/ch042_database-overview.xml63(title)
+#: ./doc/security-guide/ch042_database-overview.xml81(title)
+msgid "Configuration example #1: (MySQL)"
+msgstr "設定例 #1: (MySQL)"
+
+#: ./doc/security-guide/ch042_database-overview.xml67(title)
+#: ./doc/security-guide/ch042_database-overview.xml87(title)
+msgid "Configuration example #2: (PostgreSQL)"
+msgstr "設定例 #2: (PostgreSQL)"
+
+#: ./doc/security-guide/ch042_database-overview.xml68(para)
+msgid "In file <filename>pg_hba.conf</filename>:"
+msgstr "<filename>pg_hba.conf</filename> ファイル:"
+
+#: ./doc/security-guide/ch042_database-overview.xml70(para)
 msgid ""
-"AMQP based solutions (Qpid and RabbitMQ) support transport-level security "
-"using SSL. ZeroMQ messaging does not natively support SSL, but transport-"
-"level security is possible using labelled IPSec or CIPSO network labels."
-msgstr "AMQP ベースの製品 (Qpid, RabbitMQ) は SSL を用いた通信路レベルのセキュリティに対応しています。ZeroMQ はSSL をネイティブでサポートしていませんが、Labeled-IPSec や CIPSO ネットワークラベルを用いた通信路レベルのセキュア化に対応しています。"
+"Note this command only adds the ability to communicate over SSL and is non-"
+"exclusive. Other access methods that may allow unencrypted transport should "
+"be disabled so that SSL is the sole access method."
+msgstr "このコマンドは SSL 経由で通信する機能を追加するのみであり、排他的ではないことに注意してください。SSL を唯一のアクセス方法にするために、暗号化されていない通信を許可するかもしれない他のアクセス方法は無効化されるべきです。"
 
-#: ./doc/security-guide/ch038_transport-security.xml13(para)
+#: ./doc/security-guide/ch042_database-overview.xml71(para)
 msgid ""
-"We highly recommend enabling transport-level cryptography for your message "
-"queue. Using SSL for the messaging client connections provides protection of"
-" the communications from tampering and eavesdropping in-transit to the "
-"messaging server. Below is guidance on how SSL is typically configured for "
-"the two popular messaging servers Qpid and RabbitMQ. When configuring the "
-"trusted certificate authority (CA) bundle that your messaging server uses to"
-" verify client connections, it is recommended that this be limited to only "
-"the CA used for your nodes, preferably an internally managed CA. The bundle "
-"of trusted CAs will determine which client certificates will be authorized "
-"and pass the client-server verification step of the setting up the SSL "
-"connection. Note, when installing the certificate and key files, ensure that"
-" the file permissions are restricted, for example chmod 0600, and the "
-"ownership is restricted to the messaging server daemon user to prevent "
-"unauthorized access by other processes and users on the messaging server."
-msgstr "メッセージキューには、通信路レベルでの暗号化を強く推奨します。メッセージクライアントとの接続に SSL を用いることで、メッセージサーバとの通信路における通信の改ざんや傍受を防ぐことが可能です。以下、よく使われる 2 種類のメッセージサーバ Qpid、および、RabbitMQ における一般的な SSL の設定について説明します。\nクライアント接続の正当性を保証する目的でメッセージサーバに証明機関 (CA) バンドルを設定する場合、該当ノードに限定した CA の使用を、またなるべくなら組織内部で管理している CA の使用を推奨します。\n信頼された CA バンドルは許可を与えるクライアント接続証明書を決定し、SSL 接続を張るためのクライアントサーバ検証のステップを通過させます。\n証明書とキーのファイルをインストールする際は、chmod 0600 などでファイルのパーミッションを限定させ、所有者をメッセージサーバのデーモンユーザに限定させるようにしてください。こうすることで、メッセージサーバ上の許可を与えていない他プロセスやユーザによるアクセスを防ぐことできます。"
+"The <literal>md5</literal> parameter defines the authentication method as a "
+"hashed password. We provide a secure authentication example in the section "
+"below."
+msgstr "<literal>md5</literal> パラメーターは認証方式をハッシュ化パスワードとして定義します。以下のセクションでセキュアな認証例を提供します。"
 
-#: ./doc/security-guide/ch038_transport-security.xml15(title)
-msgid "RabbitMQ server SSL configuration"
-msgstr "RabbitMQ サーバにおける SSL 設定"
+#: ./doc/security-guide/ch042_database-overview.xml78(title)
+msgid "Authentication with X.509 certificates"
+msgstr "X.509 証明書を用いた認証"
 
-#: ./doc/security-guide/ch038_transport-security.xml16(para)
+#: ./doc/security-guide/ch042_database-overview.xml79(para)
 msgid ""
-"The following lines should be added to the system-wide RabbitMQ "
-"configuration file, typically "
-"<filename>/etc/rabbitmq/rabbitmq.config</filename>:"
-msgstr "下記の設定を RabbitMQ のシステム設定ファイルに追加します。通常、<filename>/etc/rabbitmq/rabbitmq.config</filename> に保存されています。"
+"Security may be enhanced by requiring X.509 client certificates for "
+"authentication. Authenticating to the database in this manner provides "
+"greater identity assurance of the client making the connection to the "
+"database and ensures that the communications are encrypted."
+msgstr "認証に X.509 クライアント証明書を要求することにより、セキュリティを向上させられるかもしれません。この方法でデータベースに認証することにより、データベースに接続しているクライアントの ID 確認をより強力にでき、通信が確実に暗号化されます。"
 
-#: ./doc/security-guide/ch038_transport-security.xml31(para)
+#: ./doc/security-guide/ch042_database-overview.xml92(title)
+msgid "OpenStack service database configuration"
+msgstr "OpenStack サービスのデータベース設定"
+
+#: ./doc/security-guide/ch042_database-overview.xml93(para)
 msgid ""
-"Note, the <literal>tcp_listeners</literal> option is set to "
-"<literal>[]</literal> to prevent it from listening an on non-SSL port. The "
-"<literal>ssl_listeners</literal> option should be restricted to only listen "
-"on the management network for the services."
-msgstr "<literal>tcp_listeners</literal> オプションを <literal>[]</literal> に指定し、非 SSL ポートの接続を受け付けない設定にしていることに注意してください。 <literal>ssl_listeners</literal> オプションはサービスの管理ネットワークのみ受け付けるよう限定すべきです。"
+"If your database server is configured to require X.509 certificates for "
+"authentication you will need to specify the appropriate SQLAlchemy query "
+"parameters for the database backend. These parameters specify the "
+"certificate, private key, and certificate authority information for use with"
+" the initial connection string."
+msgstr "お使いのデータベースサーバーが認証に X.509 証明書を要求するよう設定している場合、データベースバックエンドのために適切な SQLAlchemy クエリーパラメーターを指定する必要があります。これらのパラメーターは初期接続文字列に用いる証明書、秘密鍵、認証局の情報を指定します。"
 
-#: ./doc/security-guide/ch038_transport-security.xml36(para)
-msgid "For more information on RabbitMQ SSL configuration see:"
-msgstr "RabbitMQ の SSL 設定に関する詳細は、以下を参照してください。"
-
-#: ./doc/security-guide/ch038_transport-security.xml39(link)
-msgid "RabbitMQ Configuration"
-msgstr "RabbitMQ 設定"
-
-#: ./doc/security-guide/ch038_transport-security.xml43(link)
-msgid "RabbitMQ SSL"
-msgstr "RabbitMQ SSL"
-
-#: ./doc/security-guide/ch038_transport-security.xml48(title)
-msgid "Qpid server SSL configuration"
-msgstr "Qpid サーバ SSL 設定"
-
-#: ./doc/security-guide/ch038_transport-security.xml49(para)
-msgid "The Apache Foundation has a messaging security guide for Qpid. See:"
-msgstr "Apache Foundation が Qpid のメッセージングセキュリティガイドを発行しています。"
-
-#: ./doc/security-guide/ch038_transport-security.xml51(link)
-msgid "Apache Qpid SSL"
-msgstr "Apache Qpid SSL"
-
-#: ./doc/security-guide/ch038_transport-security.xml57(title)
-msgid "Queue authentication and access control"
-msgstr "キューの認証およびアクセス制御"
-
-#: ./doc/security-guide/ch038_transport-security.xml58(para)
+#: ./doc/security-guide/ch042_database-overview.xml94(para)
 msgid ""
-"RabbitMQ and Qpid offer authentication and access control mechanisms for "
-"controlling access to queues. ZeroMQ offers no such mechanisms."
-msgstr "RabbitMQ と Qpid はキューへのアクセス制御を目的とした、認証およびアクセス制御の仕組みを持っています。ZeroMQ にはこのような仕組みは備わっていません。"
+"Example of an <literal>:sql_connection</literal> string for X.509 "
+"certificate authentication to MySQL:"
+msgstr "MySQL への X.509 証明書認証の <literal>:sql_connection</literal> 文字列の例:"
 
-#: ./doc/security-guide/ch038_transport-security.xml59(para)
+#: ./doc/security-guide/ch042_database-overview.xml100(para)
 msgid ""
-"Simple Authentication and Security Layer (SASL) is a framework for "
-"authentication and data security in Internet protocols. Both RabbitMQ and "
-"Qpid offer SASL and other pluggable authentication mechanisms beyond simple "
-"usernames and passwords that allow for increased authentication security. "
-"While RabbitMQ supports SASL, support in OpenStack does not currently allow "
-"for requesting a specific SASL authentication mechanism. RabbitMQ support in"
-" OpenStack allows for either username and password authentication over an "
-"unencrypted connection or username and password in conjunction with X.509 "
-"client certificates to establish the secure SSL connection."
-msgstr "Simple Authentication and Security Layer (SASL) はインターネットプロトコルにおける認証とデータセキュリティのフレームワークです。RabbitMQ と Qpid は SASL の他、プラグイン形式の認証メカニズムを提供しており、単純なユーザ名とパスワードよりもセキュアな認証が可能になっています。RabbitMQ は SASL をサポートしているものの、現在の OpenStack は特定の SASL 認証メカニズムの使用を許可していません。RabbitMQ では、非暗号化接続でのユーザ名とパスワード認証か、X.509 クライアント証明書を用いたセキュアな SSL 接続でのユーザ名とパスワード認証がサポートされています。"
+"OpenStack Compute offers a sub-service called <systemitem class=\"service"
+"\">nova-conductor</systemitem> which proxies database connections, with the "
+"primary purpose of having the nova compute nodes interfacing with "
+"<systemitem class=\"service\">nova-conductor</systemitem> to meet data "
+"persistence needs as opposed to directly communicating with the database."
+msgstr "OpenStack Compute は <systemitem class=\"service\">nova-conductor</systemitem> というサブサービスを提供します。これは、<systemitem class=\"service\">nova-conductor</systemitem> と直接接する nova コンピュートノードがデータ永続性の要求を満たすことを主目的として、それらがデータベースと直接通信する代わりにデータベース接続を中継します。"
 
-#: ./doc/security-guide/ch038_transport-security.xml60(para)
+#: ./doc/security-guide/ch042_database-overview.xml101(para)
 msgid ""
-"We recommend configuring X.509 client certificates on all the OpenStack "
-"service nodes for client connections to the messaging queue and where "
-"possible (currently only Qpid) perform authentication with X.509 client "
-"certificates. When using usernames and passwords, accounts should be created"
-" per-service and node for finer grained auditability of access to the queue."
-msgstr "全ての OpenStack サービスノードにおいて、メッセージキューへのクライアント接続に X.509 クライアント証明書を設定することを推奨します。また可能なら、X.509 クライアント証明書での認証も推奨します。(現在、Qpid のみがサポート)\nユーザ名とパスワードを用いる場合、キューに対するアクセスの監査の粒度を細かくする目的で、アカウントはサービス毎、ノード毎に作成するべきです。"
+"Nova-conductor receives requests over RPC and performs actions on behalf of "
+"the calling service without granting granular access to the database, its "
+"tables, or data within. Nova-conductor essentially abstracts direct database"
+" access away from compute nodes."
+msgstr "Nova-conductor は RPC 経由でリクエストを受信します。そして、データベース、テーブル、データへの精細なアクセス権なしでサービスを呼び出す動作を実行します。Nova-conductor は本質的にコンピュートノードがデータベースに直接アクセスすることを抽象化します。"
 
-#: ./doc/security-guide/ch038_transport-security.xml61(para)
+#: ./doc/security-guide/ch042_database-overview.xml102(para)
 msgid ""
-"Before deployment, consider the SSL libraries that the queuing servers use. "
-"Qpid uses Mozilla's NSS library, whereas RabbitMQ uses Erlang's SSL module "
-"which uses OpenSSL."
-msgstr "導入前に、キューサーバが使用する SSL ライブラリについて考慮します。Qpid はMozilla の NSS ライブラリを、RabbitMQ は OpenSSL を使う Erlang の SSL モジュールを用いています。"
+"This abstraction offers the advantage of restricting services to executing "
+"methods with parameters, similar to stored procedures, preventing a large "
+"number of systems from directly accessing or modifying database data. This "
+"is accomplished without having these procedures stored or executed within "
+"the context or scope of the database itself, a frequent criticism of typical"
+" stored procedures."
+msgstr "この抽象化は、サービスがパラメーター、ストアドプロシージャーのようなものを用いたメソッドの実行を制限し、数多くのシステムがデータベースのデータに直接アクセスしたり変更したりすることを防ぐという利点を提供します。これは、一般的なストアドプロシージャーという頻繁に批判される、データベース自体の文脈や範囲の中で、これらの手順を保存して実行することなく実現されます。"
 
-#: ./doc/security-guide/ch038_transport-security.xml66(title)
-msgid "Authentication configuration example: RabbitMQ"
-msgstr "認証設定例: RabbitMQ"
-
-#: ./doc/security-guide/ch038_transport-security.xml67(para)
+#: ./doc/security-guide/ch042_database-overview.xml110(para)
 msgid ""
-"On the RabbitMQ server, delete the default <literal>guest</literal> user:"
-msgstr "RabbitMQ サーバで、デフォルトの <literal>guest</literal> ユーザを削除します。"
+"Unfortunately, this solution complicates the task of more fine-grained "
+"access control and the ability to audit data access. Because the <systemitem"
+" class=\"service\">nova-conductor</systemitem> service receives requests "
+"over RPC, it highlights the importance of improving the security of "
+"messaging. Any node with access to the message queue may execute these "
+"methods provided by the <systemitem class=\"service\">nova-"
+"conductor</systemitem> and effectively modifying the database."
+msgstr "残念なことに、このソリューションはより詳細なアクセス制御とデータアクセスの監査機能を複雑にします。<systemitem class=\"service\">nova-conductor</systemitem> サービスは RPC 経由でリクエストを受信するため、メッセージングのセキュリティを改善する重要性を強調させます。メッセージキューにアクセスするすべてのノードは、<systemitem class=\"service\">nova-conductor</systemitem> により提供されるこれらの方式を実行し、データベースを効率的に変更するかもしれません。"
 
-#: ./doc/security-guide/ch038_transport-security.xml70(para)
+#: ./doc/security-guide/ch042_database-overview.xml111(para)
 msgid ""
-"On the RabbitMQ server, for each OpenStack service or node that communicates"
-" with the message queue set up user accounts and privileges:"
-msgstr "RabbitMQ サーバにて、メッセージキューを使用する各 OpenStack サービス、または、ノード毎にユーザアカウントと権限を設定します。"
+"Finally, it should be noted that as of the Grizzly release, gaps exist where"
+" <systemitem class=\"service\">nova-conductor</systemitem> is not used "
+"throughout OpenStack Compute. Depending on one's configuration, the use of "
+"<systemitem class=\"service\">nova-conductor</systemitem> may not allow "
+"deployers to avoid the necessity of providing database GRANTs to individual "
+"compute host systems."
+msgstr "最後に、Grizzly リリース時点では、<systemitem class=\"service\">nova-conductor</systemitem> が OpenStack Compute 全体で使用されないというギャップが存在することに注意してください。その設定に依存して、<systemitem class=\"service\">nova-conductor</systemitem> を使用しても、導入者が個々のコンピュートホストにデータベースの権限を与える必要性を避けられないかもしれません。"
 
-#: ./doc/security-guide/ch038_transport-security.xml75(para)
-msgid "For additional configuration information see:"
-msgstr "追加の設定情報は以下を参照してください。"
-
-#: ./doc/security-guide/ch038_transport-security.xml77(link)
-msgid "RabbitMQ Access Control"
-msgstr "RabbitMQ アクセス制御"
-
-#: ./doc/security-guide/ch038_transport-security.xml80(link)
-msgid "RabbitMQ Authentication"
-msgstr "RabbitMQ 認証"
-
-#: ./doc/security-guide/ch038_transport-security.xml83(link)
-msgid "RabbitMQ Plugins"
-msgstr "RabbitMQ プラグイン"
-
-#: ./doc/security-guide/ch038_transport-security.xml86(link)
-msgid "RabbitMQ SASL External Auth"
-msgstr "RabbitMQ SASL 外部認証"
-
-#: ./doc/security-guide/ch038_transport-security.xml91(title)
-msgid "OpenStack service configuration: RabbitMQ"
-msgstr "OpenStack サービス設定: RabbitMQ"
-
-#: ./doc/security-guide/ch038_transport-security.xml104(title)
-msgid "Authentication configuration example: Qpid"
-msgstr "認証設定例: Qpid"
-
-#: ./doc/security-guide/ch038_transport-security.xml105(para)
-msgid "For configuration information see:"
-msgstr "設定情報は以下を参照してください。"
-
-#: ./doc/security-guide/ch038_transport-security.xml107(link)
-msgid "Apache Qpid Authentication"
-msgstr "Apache Qpid 認証"
-
-#: ./doc/security-guide/ch038_transport-security.xml110(link)
-msgid "Apache Qpid Authorization"
-msgstr "Apache Qpid 認可"
-
-#: ./doc/security-guide/ch038_transport-security.xml115(title)
-msgid "OpenStack service configuration: Qpid"
-msgstr "OpenStack サービス設定: Qpid"
-
-#: ./doc/security-guide/ch038_transport-security.xml124(para)
+#: ./doc/security-guide/ch042_database-overview.xml112(para)
 msgid ""
-"Optionally, if using SASL with Qpid specify the SASL mechanisms in use by "
-"adding:"
-msgstr "オプションとして Qpid で SASL を使用する場合は、下記のように SASL メカニズムを指定します。"
+"Note, as <systemitem class=\"service\">nova-conductor</systemitem> only "
+"applies to OpenStack Compute, direct database access from compute hosts may "
+"still be necessary for the operation of other OpenStack components such as "
+"Telemetry (ceilometer), Networking, and Block Storage."
+msgstr "<systemitem class=\"service\">nova-conductor</systemitem> は OpenStack Compute のみに適用されるので、Telemetry (ceilometer)、Networking、Block Storage のような他の OpenStack コンポーネントの動作のために、コンピュートホストから直接データベースにアクセスする必要があるかもしれないことに注意してください。"
 
-#: ./doc/security-guide/ch038_transport-security.xml129(title)
-msgid "Message queue process isolation and policy"
-msgstr "メッセージキュープロセスのアイソレーションとポリシー"
-
-#: ./doc/security-guide/ch038_transport-security.xml130(para)
+#: ./doc/security-guide/ch042_database-overview.xml118(para)
 msgid ""
-"Each project provides a number of services which send and consume messages. "
-"Each binary which sends a message is expected to consume messages, if only "
-"replies, from the queue."
-msgstr "各プロジェクトは多数のサービスを提供し、それぞれがメッセージを送信、消費します。メッセージを送信した各バイナリは、リプライのみの場合、該当キューからメッセージを消費するはずです。"
+"Implementors should weigh the benefits and risks of both configurations "
+"before enabling or disabling the <systemitem class=\"service\">nova-"
+"conductor</systemitem> service. We are not yet prepared to recommend the use"
+" of <systemitem class=\"service\">nova-conductor</systemitem> in the Grizzly"
+" release. However, we do believe that this recommendation will change as "
+"additional features are added into OpenStack."
+msgstr "導入者は <systemitem class=\"service\">nova-conductor</systemitem> を有効化または無効化する前に両方の設定の利点とリスクを比較検討すべきです。Grizzly リリースでは <systemitem class=\"service\">nova-conductor</systemitem> の利用を推奨する準備ができていません。しかしながら、追加の機能が OpenStack にもたらされるので、この推奨について変更されると確信しています。"
 
-#: ./doc/security-guide/ch038_transport-security.xml131(para)
+#: ./doc/security-guide/ch042_database-overview.xml119(para)
 msgid ""
-"Message queue service processes should be isolated from each other and other"
-" processes on a machine."
-msgstr "メッセージキューサービスのプロセスは、他のキューサービスのプロセスや、同一マシン上の他プロセスと分離すべきです。"
+"To disable the <systemitem class=\"service\">nova-conductor</systemitem>, "
+"place the following into your <filename>nova.conf</filename> file (on your "
+"compute hosts):"
+msgstr "<systemitem class=\"service\">nova-conductor</systemitem> を無効化するために、以下の事項を (コンピュートホストの) <filename>nova.conf</filename> ファイルに記入します。"
 
-#: ./doc/security-guide/ch038_transport-security.xml134(para)
-msgid ""
-"Network namespaces are highly recommended for all services running on "
-"OpenStack Compute Hypervisors. This will help prevent against the bridging "
-"of network traffic between VM guests and the management network."
-msgstr "ネットワーク名前空間の設定は、OpenStack コンピュートハイパーバイザを動作させる全てのサービスで強く推奨します。ネットワーク名前空間を用いることで、VM ゲストと管理ネットワークのトラフィックがブリッジングされることを防ぎます。"
+#: ./doc/security-guide/ch049_case-studies-tenant-data.xml8(title)
+msgid "Case studies: tenant data"
+msgstr "ケーススタディ: テナントデータ"
 
-#: ./doc/security-guide/ch038_transport-security.xml135(para)
+#: ./doc/security-guide/ch049_case-studies-tenant-data.xml9(para)
 msgid ""
-"When using ZeroMQ messaging, each host must run at least one ZeroMQ message "
-"receiver to receive messages from the network and forward messages to local "
-"processes through IPC. It is possible and advisable to run an independent "
-"message receiver per project within an IPC namespace, along with other "
-"services within the same project."
-msgstr "ZeroMQ メッセージングを使用する場合、ネットワーク経由のメッセージ受信と、IPC経由によるローカルプロセスへのメッセージ送信のために、各ホストに最低 1 つの ZeroMQ メッセージレシーバーを走らせる必要があります。IPC 名前空間内にプロジェクト毎で独立したメッセージレシーバーを構築することが可能であり望ましいです。また同様に、同一プロジェクト内でも異なるサービスごとに独立したメッセージレシーバーを構築することが望ましいです。"
+"Returning to Alice and Bob, we will use this section to dive into their "
+"particular tenant data privacy requirements. Specifically, we will look into"
+" how Alice and Bob both handle tenant data, data destruction, and data "
+"encryption."
+msgstr "アリスとボブの話に戻ると、このセクションでは、彼らの特定のテナントのデータのプライバシー要件についてより詳細に説明します。具体的には、アリスとボブの両者がテナントのデータ、データの破壊、データの暗号化をどのように対処するかを見てみます。"
 
-#: ./doc/security-guide/ch038_transport-security.xml145(para)
+#: ./doc/security-guide/ch049_case-studies-tenant-data.xml18(para)
 msgid ""
-"Queue servers should only accept connections from the management network. "
-"This applies to all implementations. This should be implemented through "
-"configuration of services and optionally enforced through global network "
-"policy."
-msgstr "キューサーバーは管理ネットワークからの接続のみを受け付けるべきであり、この方針はあらゆる実装に適用されます。サービスの設定を通して実装し、任意でグローバルネットワークポリシーを追加で実装します。"
+"As stated during the introduction to Alice's case study, data protection is "
+"of an extremely high priority. She needs to ensure that a compromise of one "
+"tenant's data does not cause loss of other tenant data. She also has strong "
+"regulator requirements that require documentation of data destruction "
+"activities. Alice does this using the following:"
+msgstr "アリスのケーススタディで説明したように、データ保護は非常に重要です。アリスは、あるテナントのデータの情報漏洩が、他のテナントデータの損害を引き起こさないように、保証することが必要です。アリスはまた、データ破壊の文書化を必要とする強い規制上の要件を持っています。アリスは、以下の方法でこれを提供します："
 
-#: ./doc/security-guide/ch038_transport-security.xml146(para)
+#: ./doc/security-guide/ch049_case-studies-tenant-data.xml28(para)
 msgid ""
-"When using ZeroMQ messaging, each project should run a separate ZeroMQ "
-"receiver process on a port dedicated to services belonging to that project. "
-"This is equivalent to the AMQP concept of control exchanges."
-msgstr "ZeroMQ を使用するのであれば、各プロジェクトで独立した専用のポート上で動作する ZeroMQ レシーバープロセスを用意すべきです。これは、AMQP のコントロール exchange の概念に相当します。"
+"Establishing procedures to sanitize tenant data when a program or project "
+"ends."
+msgstr "プログラムやプロジェクトが終了する際に、好ましくないテナントデータを削除するための手順を確立すること。"
 
-#: ./doc/security-guide/ch038_transport-security.xml150(para)
+#: ./doc/security-guide/ch049_case-studies-tenant-data.xml32(para)
 msgid ""
-"The configuration for these processes should be restricted to those "
-"processes, not only by Directory Access Controls, but through Mandatory "
-"Access Controls. The goal of such restrictions is to prevent isolation from "
-"other processes running on the same machine(s)."
-msgstr "各プロセスに行なった設定は、他プロセスに影響を与えないよう制限をかけるべきです。そのためには、ダイレクトアクセス制御のみではなく、強制アクセス制御を使用します。このような制限をかけるのは、同一マシンで動作する他プロセスとの隔離を防ぐことが目的です。"
+"Track the destruction of both the tenant data and metadata through ticketing"
+" in a CMDB."
+msgstr "CMDBのチケット発行を使用して、顧客データとメタデータの両方の破壊を追跡する。"
+
+#: ./doc/security-guide/ch049_case-studies-tenant-data.xml35(para)
+#: ./doc/security-guide/ch049_case-studies-tenant-data.xml69(para)
+msgid "For Volume storage:"
+msgstr "ボリュームストレージ"
+
+#: ./doc/security-guide/ch049_case-studies-tenant-data.xml38(para)
+#: ./doc/security-guide/ch049_case-studies-tenant-data.xml72(para)
+msgid "Physical server issues"
+msgstr "物理サーバーの問題"
+
+#: ./doc/security-guide/ch049_case-studies-tenant-data.xml41(para)
+msgid ""
+"To provide secure ephemeral instance storage, Alice implements qcow2 files "
+"on an encrypted filesystem."
+msgstr "安全な一時ディスクを提供するために、アリスは暗号化ファイルシステム上に qcow2 のファイルを実装しています。"
+
+#: ./doc/security-guide/ch049_case-studies-tenant-data.xml51(para)
+msgid ""
+"As stated during the introduction to Bob's case study, tenant privacy is of "
+"an extremely high priority. In addition to the requirements and actions Bob "
+"will take to isolate tenants from one another at the infrastructure layer, "
+"Bob also needs to provide assurances for tenant data privacy. Bob does this "
+"using the following:"
+msgstr "ボブのケーススタディの最初で説明したように、テナントのプライバシーは非常に重要です。ボブはインフラレイヤーで相互にテナントを分離する要件およびアクションに加えて、ボブはまたテナントデータのプライバシーを保する必要があります。 ボブは以下を用いて、これを提供します："
+
+#: ./doc/security-guide/ch049_case-studies-tenant-data.xml61(para)
+msgid ""
+"Establishing procedures to sanitize customer data when a customer churns."
+msgstr "顧客が不適切な顧客データを大量生産する時に、削除するための手順を確立する。"
+
+#: ./doc/security-guide/ch049_case-studies-tenant-data.xml65(para)
+msgid ""
+"Track the destruction of both the customer data and metadata through "
+"ticketing in a CMDB."
+msgstr "CMDBのチケット発行を使用して、顧客データとメタデータの両方の破壊を追跡します。"
+
+#: ./doc/security-guide/ch049_case-studies-tenant-data.xml75(para)
+msgid ""
+"To provide secure ephemeral instance storage, Bob implements qcow2 files on "
+"an encrypted filesystems."
+msgstr "安全な一時ディスクを提供するために、ボブは暗号化ファイルシステム上に qcow2 のファイルを実装しています。"
 
 #: ./doc/security-guide/ch044_case-studies-database.xml8(title)
 msgid "Case studies: database"
@@ -5074,603 +9777,6 @@ msgid ""
 "for fine-grained access control."
 msgstr "ボブはプロジェクトのデータの確実な分離に関心があります。そのため、彼はより強力なセキュリティ機能が知られている Postgres データベースを使用することにしました。データベースは管理ネットワークに置かれ、サービス間の相互認証とともに SSL を使用します。データベースは管理ネットワークにあるので、組織の自己署名ルート証明書で署名した証明書を使用します。ボブは各データベースユーザーに対して別々のユーザーアカウントを作成し、認証のためにパスワードと X.509 証明書の両方を使用するようデータベースを設定します。高精細なアクセス制御をしたいので、<systemitem class=\"service\">nova-conductor</systemitem> サブサービスを使用しないことにします。"
 
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch001_acknowledgements.xml12(None)
-#: ./doc/security-guide/ch001_acknowledgements.xml15(None)
-msgid ""
-"@@image: 'static/book-sprint-all-logos.png'; "
-"md5=f2d97c3130c32f31412f5af41ad72d39"
-msgstr "@@image: 'static/book-sprint-all-logos.png'; md5=f2d97c3130c32f31412f5af41ad72d39"
-
-#: ./doc/security-guide/ch001_acknowledgements.xml7(title)
-msgid "Acknowledgments"
-msgstr "謝辞"
-
-#: ./doc/security-guide/ch001_acknowledgements.xml8(para)
-msgid ""
-"The OpenStack Security Group would like to acknowledge contributions from "
-"the following organizations who were instrumental in making this book "
-"possible. These are:"
-msgstr "OpenStack Security Group は、このドキュメントの作成を支援していただいた以下の組織の貢献に感謝いたします。"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch033_securing-neutron-services.xml40(None)
-#: ./doc/security-guide/ch033_securing-neutron-services.xml45(None)
-msgid ""
-"@@image: 'static/1aa-logical-neutron-flow.png'; "
-"md5=3589a1ef10ea2bbe189ca90e3c932df2"
-msgstr "@@image: 'static/1aa-logical-neutron-flow.png'; md5=3589a1ef10ea2bbe189ca90e3c932df2"
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml8(title)
-msgid "Securing OpenStack Networking services"
-msgstr "OpenStack Networking サービスのセキュリティ強化"
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml9(para)
-msgid ""
-"To secure OpenStack Networking, you must understand how the workflow process"
-" for tenant instance creation needs to be mapped to security domains."
-msgstr "OpenStack Networking のセキュリティを強化する為に、どの程度テナントインスタンス作成用のワークフロープロセスをセキュリティドメインにマッピングさせる必要があることを理解しなくてはいけません。"
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml13(para)
-msgid ""
-"There are four main services that interact with OpenStack Networking. In a "
-"typical OpenStack deployment these services map to the following security "
-"domains:"
-msgstr "OpenStack Networking と交信する主要なサービスが４つあります。典型的な OpenStack デプロイでは、これらのサービスは以下のセキュリティドメインにマッピングされます。"
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml18(para)
-msgid "OpenStack dashboard: Public and management"
-msgstr "OpenStack Dashboard: パブリック、管理"
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml21(para)
-msgid "OpenStack Identity: Management"
-msgstr "OpenStack Identity: 管理"
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml24(para)
-msgid "OpenStack compute node: Management and guest"
-msgstr "OpenStack Compute ノード: 管理、ゲスト"
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml27(para)
-msgid ""
-"OpenStack network node: Management, guest, and possibly public depending "
-"upon neutron-plugin in use."
-msgstr "OpenStack ネットワークノード: 管理、ゲスト（使用する neutron プラグインによってはパブリックも可能性あり）"
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml31(para)
-msgid ""
-"SDN services node: Management, guest and possibly public depending upon "
-"product used."
-msgstr "SDB サービスノード：管理、ゲスト （使用する製品によってはパブリックも可能性あり）"
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml49(para)
-msgid ""
-"To isolate sensitive data communication between the OpenStack Networking "
-"services and other OpenStack core services, configure these communication "
-"channels to only allow communication over an isolated management network."
-msgstr "OpenStack Networking サービスと他の OpenStack コアサービス間の扱いの難しいデータ通信を分離する為、通信を独立した管理ネットワーク上でのみ行うように通信路を設定します。"
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml54(title)
-msgid "OpenStack Networking service configuration"
-msgstr "OpenStack Networking サービス設定"
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml56(title)
-msgid "Restrict bind address of the API server: neutron-server"
-msgstr "API サーバがバインドするアドレスの制限: neutron-server"
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml57(para)
-msgid ""
-"To restrict the interface or IP address on which the OpenStack Networking "
-"API service binds a network socket for incoming client connections, specify "
-"the bind_host and bind_port in the neutron.conf file as shown:"
-msgstr "OpenStack Networking API サービスが外からのクライアント通信用にネットワークソケットをバインドするネットワークインターフェース又は IP アドレスを制限する為、neutron.conf ファイル中の bind_host と bind_port を以下のように指定します。"
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml64(replaceable)
-msgid "IP ADDRESS OF SERVER"
-msgstr "IP ADDRESS OF SERVER"
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml70(title)
-msgid "Restrict DB and RPC communication of the OpenStack Networking services"
-msgstr "OpenStack Networking サービス群の DB と RPC 通信の制限"
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml72(para)
-msgid ""
-"Various components of the OpenStack Networking services use either the "
-"messaging queue or database connections to communicate with other components"
-" in OpenStack Networking."
-msgstr "OpenStack Networking サービスの様々なコンポーネントは、OpenStack Networking 中の他のコンポーネントとの通信にメッセージキュー又はデータベース接続のいずれかを使用します。"
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml77(para)
-msgid ""
-"It is recommended that you follow the guidelines provided in the Database "
-"Authentication and Access Control chapter in the Database section for all "
-"components that require direct DB connections."
-msgstr "DB への直接接続を必要とする全てのコンポーネントに対し、データベースの章のデータベース認証とアクセスコントロールの節で示されたガイドラインに従う事を推奨します。"
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml82(para)
-msgid ""
-"It is recommended that you follow the guidelines provided in the Queue "
-"Authentication and Access Control chapter in the Messaging section for all "
-"components that require RPC communication."
-msgstr "RPC 通信を必要とする全てのコンポーネントに対し、メッセージングの章のキュー認証とアクセスコントロールの節中で示されたガイドラインに従う事を推奨します。"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch004_book-introduction.xml113(None)
-#: ./doc/security-guide/ch004_book-introduction.xml118(None)
-msgid ""
-"@@image: 'static/marketecture-diagram.png'; "
-"md5=4ab13a64f80c210be3120abc5c7aee8a"
-msgstr "@@image: 'static/marketecture-diagram.png'; md5=4ab13a64f80c210be3120abc5c7aee8a"
-
-#: ./doc/security-guide/ch004_book-introduction.xml8(title)
-msgid "Introduction to OpenStack"
-msgstr "OpenStack の概要"
-
-#: ./doc/security-guide/ch004_book-introduction.xml9(para)
-msgid ""
-"This guide provides security insight into OpenStack deployments. The "
-"intended audience is cloud architects, deployers, and administrators. In "
-"addition, cloud users will find the guide both educational and helpful in "
-"provider selection, while auditors will find it useful as a reference "
-"document to support their compliance certification efforts. This guide is "
-"also recommended for anyone interested in cloud security."
-msgstr "本ガイドは、OpenStack のデプロイメントにおけるセキュリティに関する知見を提供します。クラウドアーキテクト、デプロイ担当者、管理者などを対象読者としています。また、クラウドユーザーには、プロバイダー選択にあたって参照することのできる有用な情報を記載している一方、監査担当者には、コンプライアンス認証に伴う作業を支援する参考資料としてご利用いただくことができます。本ガイドは、クラウドのセキュリティに関心を持つ読者全般にもお奨めします。"
-
-#: ./doc/security-guide/ch004_book-introduction.xml16(para)
-msgid ""
-"Each OpenStack deployment embraces a wide variety of technologies, spanning "
-"Linux distributions, database systems, messaging queues, OpenStack "
-"components themselves, access control policies, logging services, security "
-"monitoring tools, and much more. It should come as no surprise that the "
-"security issues involved are equally diverse, and their in-depth analysis "
-"would require several guides. We strive to find a balance, providing enough "
-"context to understand OpenStack security issues and their handling, and "
-"provide external references for further information. The guide could be read"
-" from start to finish or sampled as necessary like a reference."
-msgstr "OpenStack の各デプロイメントには、Linux ディストリビューション、データベースシステム、メッセージキュー、OpenStack のコンポーネント自体、アクセス制御ポリシー、ログサービス、セキュリティ監視ツールなどに及ぶ、多種多様なテクノロジーが採用されます。このため、デプロイに伴うセキュリティ問題が、同じように多様となることは当然です。それらの内容を奥深く分析するには、マニュアルが数冊必要となります。 本ガイドでは、OpenStack のセキュリティ問題とその対処方法を理解するために十分な情報を提供しつつ、さらなる情報の外部参照先を掲載することにより、バランスを図っています。本書は、全体を通読する方法または参考資料として必要箇所のみを参照する方法のいずれでもご利用いただくことができます。"
-
-#: ./doc/security-guide/ch004_book-introduction.xml27(para)
-msgid ""
-"We briefly introduce the kinds of clouds: private, public, and hybrid before"
-" presenting an overview of the OpenStack components and their related "
-"security concerns in the remainder of the chapter."
-msgstr "本章では、プライベート、パブリック、ハイブリッドというクラウドの各種類について簡単に説明した後、後半に OpenStack のコンポーネントおよびそれらに関連するセキュリティ課題について概説します。"
-
-#: ./doc/security-guide/ch004_book-introduction.xml32(title)
-msgid "Cloud types"
-msgstr "クラウドのタイプ"
-
-#: ./doc/security-guide/ch004_book-introduction.xml33(para)
-msgid ""
-"OpenStack is a key enabler in adoption of cloud technology and has several "
-"common deployment use cases. These are commonly known as Public, Private, "
-"and Hybrid models. The following sections use the National Institute of "
-"Standards and Technology (NIST) <link "
-"href=\"http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf\">definition"
-" of cloud</link> to introduce these different types of cloud as they apply "
-"to OpenStack."
-msgstr "OpenStack は、クラウドテクノロジーの導入における重要なイネーブラーであり、一般的なデプロイメントユースケースがいくつかあります。これらは、パブリック、プライベート、およびハイブリッドモデルとして一般に知られています。以下のセクションでは、National Institute of Standards and Technology (NIST) <link href=\"http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf\"> のクラウドの定義</link> を取り上げ、OpenStack に適用するクラウドの異なるタイプについて説明します。"
-
-#: ./doc/security-guide/ch004_book-introduction.xml42(title)
-msgid "Public cloud"
-msgstr "パブリッククラウド"
-
-#: ./doc/security-guide/ch004_book-introduction.xml43(para)
-msgid ""
-"According to NIST, a public cloud is one in which the infrastructure is open"
-" to the general public for consumption. OpenStack public clouds are "
-"typically run by a service provider and can be consumed by individuals, "
-"corporations, or any paying customer. A public cloud provider may expose a "
-"full set of features such as software-defined networking, block storage, in "
-"addition to multiple instance types. Due to the nature of public clouds, "
-"they are exposed to a higher degree of risk. As a consumer of a public cloud"
-" you should validate that your selected provider has the necessary "
-"certifications, attestations, and other regulatory considerations. As a "
-"public cloud provider, depending on your target customers, you may be "
-"subject to one or more regulations. Additionally, even if not required to "
-"meet regulatory requirements, a provider should ensure tenant isolation as "
-"well as protecting management infrastructure from external attacks."
-msgstr "NIST によると、パブリッククラウドは、一般市民が利用できるようにインフラストラクチャーが公開されているクラウドと定義されています。OpenStack のパブリッククラウドは、通常サービスプロバイダーによって運用され、個人、法人、または料金を支払っている顧客が利用することができます。パブリッククラウドプロバイダーは、複数のインスタンスタイプに加えて、ソフトウェア定義ネットワーク、ブロックストレージなどの各種機能を公開することができます。パブリッククラウドはその性質上、より高いレベルのリスクにさらされます。パブリッククラウドの利用者は、選択したプロバイダーが必要な認定および認証を取得しているか、その他の法規制に関する考慮事項に対応しているかなどの点を確認しておく必要があります。パブリッククラウドプロバイダーは、ターゲット顧客に応じて、1 つまたは複数の法規制の影響を受ける場合があります。また、プロバイダーは、法規制の要件を満たす必要がない場合でも、管理インフラストラクチャーを外部の攻撃から保護するために、テナントの分離を確実に行う必要があります。"
-
-#: ./doc/security-guide/ch004_book-introduction.xml61(title)
-msgid "Private cloud"
-msgstr "プライベートクラウド"
-
-#: ./doc/security-guide/ch004_book-introduction.xml62(para)
-msgid ""
-"At the opposite end of the spectrum is the private cloud. As NIST defines "
-"it, a private cloud is provisioned for exclusive use by a single "
-"organization comprising multiple consumers, such as business units. It may "
-"be owned, managed, and operated by the organization, a third-party, or some "
-"combination of them, and it may exist on or off premises. Private cloud use "
-"cases are diverse, as such, their individual security concerns vary."
-msgstr "パブリッククラウドの対極にあるのがプライベートクラウドです。NIST は、プライベートクラウドを、事業組織などの複数の利用者から成る単一の組織の専用使用のために提供されるクラウドと定義しています。プライベートクラウドの所有、管理、および運用は、その組織、第三者、もしくはそれらの組み合わせにより行われ、存在場所としては、その組織の施設内または外部の場合があります。プライベートクラウドのユースケースは多様であるため、セキュリティ課題もそれぞれで異なります。"
-
-#: ./doc/security-guide/ch004_book-introduction.xml72(title)
-msgid "Community cloud"
-msgstr "コミュニティクラウド"
-
-#: ./doc/security-guide/ch004_book-introduction.xml73(para)
-msgid ""
-"NIST defines a community cloud as one whose infrastructure is provisioned "
-"for the exclusive use by a specific community of consumers from "
-"organizations that have shared concerns. For example, mission, security "
-"requirements, policy, and compliance considerations. It may be owned, "
-"managed, and operated by one or more of the organizations in the community, "
-"a third-party, or some combination of them, and it may exist on or off "
-"premises."
-msgstr "NIST では、コミュニティクラウドを、共通の関心事 (例えば、任務、セキュリティの必要、ポリシー、法令順守に関わる考慮事項 ) を持つ複数の組織から成る特定の利用者の共同体の専用使用のために提供されるクラウドと定義しています。コミュニティクラウドの所有、管理、および運用は、共同体内の 1 つまたは複数の組織、第三者、もしくはそれらの組み合わせにより行われ、存在場所はその組織の施設内または外部の場合があります。"
-
-#: ./doc/security-guide/ch004_book-introduction.xml83(title)
-msgid "Hybrid cloud"
-msgstr "ハイブリッドクラウド"
-
-#: ./doc/security-guide/ch004_book-introduction.xml84(para)
-msgid ""
-"A hybrid cloud is defined by NIST as a composition of two or more distinct "
-"cloud infrastructures, such as private, community, or public, that remain "
-"unique entities, but are bound together by standardized or proprietary "
-"technology that enables data and application portability, such as cloud "
-"bursting for load balancing between clouds. For example an online retailer "
-"may have their advertising and catalogue presented on a public cloud that "
-"allows for elastic provisioning. This would enable them to handle seasonal "
-"loads in a flexible, cost-effective fashion. Once a customer begins to "
-"process their order, they are transferred to the more secure private cloud "
-"backend that is PCI compliant."
-msgstr "NIST では、ハイブリッドクラウドを、2 つ以上の異なるクラウドインフラストラクチャー (プライベート、コミュニティ、パブリック) を組み合わせたクラウドと定義しています。各クラウドは、依然として独自のエンティティですが、データおよびアプリケーションの移植性を提供するスタンダードまたはプロプライエタリな技術 (例: クラウド間のロードバランスのためのクラウドバーストなど) により結合されます。例えば、オンライン小売業者は、柔軟なプロビジョニングが可能なパブリッククラウドに広告やカタログを掲示している場合があります。これにより、柔軟かつ費用対効果の高い方法で季節的な負荷に対応することが可能となります。顧客が発注処理を開始すると、よりセキュアなプライベートクラウドのバックエンドに転送されます。"
-
-#: ./doc/security-guide/ch004_book-introduction.xml96(para)
-msgid ""
-"For the purposes of this document, we treat Community and Hybrid similarly, "
-"dealing explicitly only with the extremes of Public and Private clouds from "
-"a security perspective. Your security measures depend where your deployment "
-"falls upon the private public continuum."
-msgstr "本ガイドにおいては、コミュニティクラウドとハイブリッドクラウドを同様に扱い、パブリッククラウドとプライベートクラウドの両極のみをセキュリティ面から明確に説明します。セキュリティ対策は、デプロイメントがプライベートクラウド/パブリッククラウドの連続体のどこに位置するかによって異なります。"
-
-#: ./doc/security-guide/ch004_book-introduction.xml104(title)
-msgid "OpenStack service overview"
-msgstr "OpenStack サービスの概観"
-
-#: ./doc/security-guide/ch004_book-introduction.xml105(para)
-msgid ""
-"OpenStack embraces a modular architecture to provide a set of core services "
-"that facilitates scalability and elasticity as core design tenets. This "
-"chapter briefly reviews OpenStack components, their use cases and security "
-"considerations."
-msgstr "OpenStack は、モジュール型アーキテクチャを採用し、中核的な設計理念としてスケーラビリティと柔軟性を促進する一式のコアサービスを提供します。本章では、OpenStack のコンポーネントとそれらのユースケースおよびセキュリティに関する考慮事項を簡単に説明します。"
-
-#: ./doc/security-guide/ch004_book-introduction.xml123(para)
-msgid ""
-"OpenStack Compute service (nova) provides services to support the management"
-" of virtual machine instances at scale, instances that host multi-tiered "
-"applications, dev/test environments, \"Big Data\" crunching Hadoop clusters,"
-" and/or high performance computing."
-msgstr "OpenStack Compute サービス (Nova) は、多層アプリケーション、開発/テスト環境、「ビッグデータ」を処理する Hadoop のクラスター、ハイパフォーマンスコンピューティングなどをホストする、大規模な仮想マシンインスタンスの管理をサポートするサービスを提供します。"
-
-#: ./doc/security-guide/ch004_book-introduction.xml128(para)
-msgid ""
-"The Compute service facilitates this management through an abstraction layer"
-" that interfaces with supported hypervisors, which we address later on in "
-"more detail."
-msgstr "Compute は、サポート対象のハイパーバイザーと連動する抽象化レイヤーを介してこのような管理を行います。ハイパーバイザーについては、後半で詳しく説明します。"
-
-#: ./doc/security-guide/ch004_book-introduction.xml131(para)
-msgid ""
-"Later in the guide, we focus generically on the virtualization stack as it "
-"relates to hypervisors."
-msgstr "本ガイドの後半では、ハイパーバイザーと関連する仮想化スタックに焦点をあてて、包括的に解説します。"
-
-#: ./doc/security-guide/ch004_book-introduction.xml133(para)
-msgid ""
-"For information about the current state of feature support, see <link "
-"href=\"https://wiki.openstack.org/wiki/HypervisorSupportMatrix\">OpenStack "
-"Hypervisor Support Matrix</link>."
-msgstr "機能サポートの現在の状況に関する情報は、 <link href=\"https://wiki.openstack.org/wiki/HypervisorSupportMatrix\">OpenStack Hypervisor Support Matrix</link> を参照してください。"
-
-#: ./doc/security-guide/ch004_book-introduction.xml137(para)
-msgid ""
-"The security of Compute is critical for an OpenStack deployment. Hardening "
-"techniques should include support for strong instance isolation, secure "
-"communication between Compute sub-components, and resiliency of public-"
-"facing <glossterm>API</glossterm> endpoints."
-msgstr "OpenStack のデプロイメントでは、Compute のセキュリティが極めて重要となります。セキュリティ強化のテクニックには、頑強なインスタンスの隔離、Compute のサブコンポーネント間におけるセキュアな通信、一般向けの  <glossterm>API</glossterm> エンドポイントの弾力性などがあげられます。"
-
-#: ./doc/security-guide/ch004_book-introduction.xml144(title)
-#: ./doc/security-guide/ch027_storage.xml8(title)
-msgid "Object Storage"
-msgstr "Object Storage"
-
-#: ./doc/security-guide/ch004_book-introduction.xml145(para)
-msgid ""
-"The OpenStack Object Storage service (swift) provides support for storing "
-"and retrieving arbitrary data in the cloud. The Object Storage service "
-"provides both a native API and an Amazon Web Services S3 compatible API. The"
-" service provides a high degree of resiliency through data replication and "
-"can handle petabytes of data."
-msgstr "OpenStack Object Storage Service (swift) は、クラウド内の任意データの保管/取得機能のサポートを提供します。Object Storage Service  はネイティブ API および Amazon Web Services S3 互換の API の両方を提供します。このサービスは、データレプリケーションにより高度な回復性を提供し、ペタバイト規模のデータの処理が可能です。"
-
-#: ./doc/security-guide/ch004_book-introduction.xml151(para)
-msgid ""
-"It is important to understand that object storage differs from traditional "
-"file system storage. It is best used for static data such as media files "
-"(MP3s, images, videos), virtual machine images, and backup files."
-msgstr "オブジェクトストレージは、従来のファイルシステムストレージと異なる点を理解しておくことが重要です。メディアファイル (MP3、画像、ビデオ) や仮想マシンイメージ、バックアップファイルなどの静的データに使用するのに最適です。"
-
-#: ./doc/security-guide/ch004_book-introduction.xml155(para)
-msgid ""
-"Object security should focus on access control and encryption of data in "
-"transit and at rest. Other concerns may relate to system abuse, illegal or "
-"malicious content storage, and cross authentication attack vectors."
-msgstr "オブジェクトのセキュリティは、アクセス制御と、伝送中および静止中のデータの暗号化に重点を置くべきです。その他の懸念事項には、システムの悪用、不法または悪意のあるコンテンツの保管、クロス認証の攻撃ベクトルなどに関する問題があげられます。"
-
-#: ./doc/security-guide/ch004_book-introduction.xml161(title)
-msgid "Block Storage"
-msgstr "Block Storage"
-
-#: ./doc/security-guide/ch004_book-introduction.xml162(para)
-msgid ""
-"The OpenStack Block Storage service (cinder) provides persistent block "
-"storage for compute instances. The Block Storage service is responsible for "
-"managing the life-cycle of block devices, from the creation and attachment "
-"of volumes to instances, to their release."
-msgstr "OpenStack Block Storage Service (cinder) は、Compute インスタンス用に永続的なブロックストレージを提供します。Block Storage Service はブロックデバイスの作成からインスタンスへのボリュームの接続、それらの解放にいたるまでのライフサイクルを管理する役割を果たします。"
-
-#: ./doc/security-guide/ch004_book-introduction.xml167(para)
-msgid ""
-"Security considerations for block storage are similar to that of object "
-"storage."
-msgstr "Block Storage のセキュリティ課題は、Object Storage の場合と同様です。"
-
-#: ./doc/security-guide/ch004_book-introduction.xml171(title)
-msgid "OpenStack Networking"
-msgstr "OpenStack Networking"
-
-#: ./doc/security-guide/ch004_book-introduction.xml172(para)
-msgid ""
-"The OpenStack Networking service (neutron, previously called quantum) "
-"provides various networking services to cloud users (tenants) such as IP "
-"address management, <glossterm>DNS</glossterm>, <glossterm>DHCP</glossterm>,"
-" load balancing, and security groups (network access rules, like firewall "
-"policies). It provides a framework for software defined networking (SDN) "
-"that allows for pluggable integration with various networking solutions."
-msgstr "OpenStack Networking (neutron、旧称 quantum) はIP アドレス管理、<glossterm>DNS</glossterm>、<glossterm>DHCP</glossterm>、負荷分散、セキュリティグループ (ファイアウォールのポリシーなど、ネットワークのアクセスルール) など、さまざまなネットワークサービスをクラウドユーザー (テナント) に提供します。また、各種ネットワークソリューションとのプラグ可能な統合を可能にするソフトウェア定義ネットワーク(SDN) のフレームワークを提供します。"
-
-#: ./doc/security-guide/ch004_book-introduction.xml180(para)
-msgid ""
-"OpenStack Networking allows cloud tenants to manage their guest network "
-"configurations. Security concerns with the networking service include "
-"network traffic isolation, availability, integrity and confidentiality."
-msgstr "OpenStack Networking により、クラウドテナントはゲストのネットワーク設定を管理することができます。ネットワークサービスに伴うセキュリティ上の問題には、 ネットワークトラフィックの隔離、可用性、完全性、機密性などがあげられます。"
-
-#: ./doc/security-guide/ch004_book-introduction.xml187(para)
-msgid ""
-"The OpenStack dashboard (horizon) provides a web-based interface for both "
-"cloud administrators and cloud tenants. Through this interface "
-"administrators and tenants can provision, manage, and monitor cloud "
-"resources. Horizon is commonly deployed in a public facing manner with all "
-"the usual security concerns of public web portals."
-msgstr "OpenStack ダッシュボードサービス (Horizon) は、クラウド管理者とクラウドテナントの両方に向けた Web ベースのインターフェースを提供します。このインターフェースにより、管理者およびテナントは、クラウドリソースのプロビジョニング、管理、監視を行うことができます。Horizon は通常、一般i向けにデプロイされ、パブリック Web ポータルの一般的なセキュリティ問題が伴います。"
-
-#: ./doc/security-guide/ch004_book-introduction.xml195(title)
-msgid "Identity service"
-msgstr "Identity"
-
-#: ./doc/security-guide/ch004_book-introduction.xml196(para)
-msgid ""
-"The OpenStack Identity service (keystone) is a <emphasis "
-"role=\"bold\">shared service</emphasis> that provides authentication and "
-"authorization services throughout the entire cloud infrastructure. The "
-"Identity service has pluggable support for multiple forms of authentication."
-msgstr "OpenStack Identity (keystone) は、クラウドインフラストラクチャー全体にわたる認証および承認サービスを提供する<emphasis role=\"bold\">共有サービス</emphasis>です。Identity には、複数形式の認証に対するプラグ可能なサポートを採用しています。"
-
-#: ./doc/security-guide/ch004_book-introduction.xml201(para)
-msgid ""
-"Security concerns here pertain to trust in authentication, management of "
-"authorization tokens, and secure communication."
-msgstr "ここでのセキュリティ課題には、認証の信頼、承認トークンの管理、セキュリティ保護された通信などがあげられます。"
-
-#: ./doc/security-guide/ch004_book-introduction.xml206(title)
-msgid "Image Service"
-msgstr "Image Service"
-
-#: ./doc/security-guide/ch004_book-introduction.xml207(para)
-msgid ""
-"The OpenStack Image Service (glance) provides disk image management "
-"services. The Image Service provides image discovery, registration, and "
-"delivery services to the Compute service, as needed."
-msgstr "OpenStack Image Service (glance) は、ディスクイメージ管理サービスを提供します。Image Service は、必要に応じて、イメージの検索、登録、デリバリサービスを Compute サービスに提供します。"
-
-#: ./doc/security-guide/ch004_book-introduction.xml211(para)
-msgid ""
-"Trusted processes for managing the life cycle of disk images are required, "
-"as are all the previously mentioned issues with respect to data security."
-msgstr "前述したデータセキュリティに関する問題と同様に、ディスクイメージのライフサイクル管理には信頼されたプロセスが必要です。"
-
-#: ./doc/security-guide/ch004_book-introduction.xml216(title)
-msgid "Other supporting technology"
-msgstr "その他の支援技術"
-
-#: ./doc/security-guide/ch004_book-introduction.xml217(para)
-msgid ""
-"OpenStack relies on messaging for internal communication between several of "
-"its services. By default, OpenStack uses message queues based on the "
-"Advanced Message Queue Protocol (<glossterm baseform=\"Advanced Message "
-"Queuing Protocol (AMQP)\">AMQP </glossterm>). Similar to most OpenStack "
-"services, it supports pluggable components. Today the implementation backend"
-" could be <glossterm>RabbitMQ</glossterm>, <glossterm>Qpid</glossterm>, or "
-"<glossterm>ZeroMQ</glossterm>."
-msgstr "OpenStack は複数のサービス間の内部通信のメッセージングに依存しています。デフォルトでは、OpenStack は Advanced Message Queue Protocol (<glossterm baseform=\"Advanced Message Queuing Protocol (AMQP)\">AMQP</glossterm>) をベースとするメッセージキューを使用します。 大半の OpenStack サービスと同様に、プラグ可能なコンポーネントをサポートしています。現在は、<glossterm>RabbitMQ</glossterm>、 <glossterm>Qpid</glossterm>、または  <glossterm>ZeroMQ</glossterm> を実装バックエンドにすることができます。"
-
-#: ./doc/security-guide/ch004_book-introduction.xml226(para)
-msgid ""
-"As most management commands flow through the message queueing system, it is "
-"a primary security concern for any OpenStack deployment. Message queueing "
-"security is discussed in detail later in this guide."
-msgstr "メッセージキューシステムは、大半の管理コマンドが通過するので、OpenStack のデプロイメントにおける重要なセキュリティ課題です。メッセージキューのセキュリティについては、本ガイドの後半で詳述します。"
-
-#: ./doc/security-guide/ch004_book-introduction.xml230(para)
-msgid ""
-"Several of the components use databases though it is not explicitly called "
-"out. Securing the access to the databases and their contents is yet another "
-"security concern, and consequently discussed in more detail later in this "
-"guide."
-msgstr "一部のコンポーネントは、間接的にデータベースを使用します。データベースおよびそのコンテンツへのアクセスのセキュリティ保護は、もう一つのセキュリティ課題であるため、本ガイドの後半でさらに詳しく説明します。"
-
-#: ./doc/security-guide/ch063_compliance-activities.xml8(title)
-msgid "Compliance activities"
-msgstr "コンプライアンス活動"
-
-#: ./doc/security-guide/ch063_compliance-activities.xml9(para)
-msgid ""
-"There are a number of standard activities that will greatly assist with the "
-"compliance process. In this chapter we outline some of the most common "
-"compliance activities. These are not specific to OpenStack, however we "
-"provide references to relevant sections in this book as useful context."
-msgstr "コンプライアンスのプロセスを大きく推進する、標準的な活動は数多くあります。この章ではいくつかの代表的なコンプライアンス活動を紹介します。これらはOpenStack固有ではありませんが、関係がわかるよう、このガイドの関連する節への参照も記載します。"
-
-#: ./doc/security-guide/ch063_compliance-activities.xml11(title)
-msgid "Information Security Management system (ISMS)"
-msgstr "Information Security Management System (ISMS)"
-
-#: ./doc/security-guide/ch063_compliance-activities.xml12(para)
-msgid ""
-"An Information Security Management System (ISMS) is a comprehensive set of "
-"policies and processes that an organization creates and maintains to manage "
-"risk to information assets. The most common ISMS for cloud deployments is "
-"<link href=\"http://www.27000.org/iso-27001.htm\">ISO/IEC 27001/2</link>, "
-"which creates a solid foundation of security controls and practices for "
-"achieving more stringent compliance certifications."
-msgstr "Information Security Management System (ISMS)は包括的なポリシーとポロセスの集合です。組織が情報資産に関するリスクを管理するため、作成、維持します。もっとも一般的なクラウド向けISMSは<link href=\"http://www.27000.org/iso-27001.htm\">ISO/IEC 27001/2</link>です。より厳格なコンプライアンス認証取得に向けて、セキュリティ統制と実践の確かな基盤を構築します。 "
-
-#: ./doc/security-guide/ch063_compliance-activities.xml15(title)
-msgid "Risk assessment"
-msgstr "リスク評価"
-
-#: ./doc/security-guide/ch063_compliance-activities.xml16(para)
-msgid ""
-"A risk assessment framework identifies risks within an organization or "
-"service, and specifies ownership of these risks, along with implementation "
-"and mitigation strategies. Risks apply to all areas of the service, from "
-"technical controls to environmental disaster scenarios and human elements, "
-"for example a malicious insider (or rogue employee). Risks can be rated "
-"using a variety of mechanisms, for example likelihood vs impact. An "
-"OpenStack deployment risk assessment can include control gaps that are "
-"described in this book."
-msgstr "リスク評価フレームワークは、組織やサービス内のリスクを特定します。また、それらのリスク、実装と緩和戦略の責任者を明確にします。リスクは全てのサービスに適用され、その範囲は技術統制から環境災害、人的要因にわたります。人的要因の例は、悪意ある内部監視者(や不良社員)などです。リスクは発生確率や影響度など、多様な指標を使って評価されます。OpenStack環境のリスク評価はこのガイドで触れられている統制のギャップを含みます。"
-
-#: ./doc/security-guide/ch063_compliance-activities.xml19(title)
-msgid "Access and log reviews"
-msgstr "アクセスとログのレビュー"
-
-#: ./doc/security-guide/ch063_compliance-activities.xml20(para)
-msgid ""
-"Periodic access and log reviews are required to ensure authentication, "
-"authorization, and accountability in a service deployment. Specific guidance"
-" for OpenStack on these topics are discussed in-depth in the logging "
-"section."
-msgstr "定期的なアクセスとログの検査は、認証、認可とサービス配備における責任を明確にするため、必要です。これらのトピックに関するOpenStack向けのガイダンスは、ロギングの節で詳細に説明します。"
-
-#: ./doc/security-guide/ch063_compliance-activities.xml23(title)
-msgid "Backup and disaster recovery"
-msgstr "バックアップと災害対策"
-
-#: ./doc/security-guide/ch063_compliance-activities.xml24(para)
-msgid ""
-"Disaster Recovery (DR) and Business Continuity Planning (BCP) plans are "
-"common requirements for ISMS and compliance activities. These plans must be "
-"periodically tested as well as documented. In OpenStack key areas are found "
-"in the management security domain, and anywhere that single points of "
-"failure (SPOFs) can be identified. See the section on secure backup and "
-"recovery for additional details."
-msgstr "災害対策(Disaster Recovery, DR)とビジネス継続計画(Business Continuity Planning, BCP)はISMSとコンプライアンス活動で共通の要件です。それらの計画は定期的な検査と文書化が必要とします。OpenStackの主要領域はマネジメントセキュリティ領域にあたり、すべての単一障害点(Single Point of Failures, SPOFs)が特定されなければいけません。詳細は、安全なバックアップとリカバリーの節を参照してください。"
-
-#: ./doc/security-guide/ch063_compliance-activities.xml27(title)
-msgid "Security training"
-msgstr "セキュリティトレーニング"
-
-#: ./doc/security-guide/ch063_compliance-activities.xml28(para)
-msgid ""
-"Annual, role-specific, security training is a mandatory requirement for "
-"almost all compliance certifications and attestations. To optimise the "
-"effectiveness of security training, a common method is to provide role "
-"specific training, for example to developers, operational personnel, and "
-"non-technical employees. Additional cloud security or OpenStack security "
-"training based on this hardening guide would be ideal."
-msgstr "年次でのロール別セキュリティトレーニングは、ほぼすべてのコンプライアンス認証、認定で必須の要件です。セキュリティトレーニングの効果を最適化するため、一般的にはロール別に実施します。例えば開発者、運用担当者、非技術者別、などです。加えて、このガイドにもとづくクラウド、OpenStackセキュリティに関するトレーニングの実施が理想的でしょう。"
-
-#: ./doc/security-guide/ch063_compliance-activities.xml31(title)
-msgid "Security reviews"
-msgstr "セキュリティの検査"
-
-#: ./doc/security-guide/ch063_compliance-activities.xml32(para)
-msgid ""
-"As OpenStack is a popular open source project, much of the codebase and "
-"architecture has been scrutinized by individual contributors, organizations "
-"and enterprises. This can be advantageous from a security perspective, "
-"however the need for security reviews is still a critical consideration for "
-"service providers, as deployments vary, and security is not always the "
-"primary concern for contributors. A comprehensive security review process "
-"may include architectural review, threat modelling, source code analysis and"
-" penetration testing. There are many techniques and recommendations for "
-"conducting security reviews that can be found publicly posted. A well-tested"
-" example is the <link "
-"href=\"http://www.microsoft.com/security/sdl/process/release.aspx\">Microsoft"
-" SDL</link>, created as part of the Microsoft Trustworthy Computing "
-"Initiative."
-msgstr "OpenStackは人気のあるオープンソースプロジェクトです。多くのソースコードとアーキテクチャはデベロッパー、組織、企業によって精査されています。これはセキュリティの観点から大きな利点ですが、セキュリティ検査はサービスプロバイダーにとって、それでもなお重大な懸念事項です。環境は変化しつづけますが、セキュリティは必ずしも開発者の一番の関心事ではないからです。包括的なセキュリティ検査プロセスとして、アーキテクチャ検査、脅威のモデリング、ソースコード分析と侵入テストなどが挙げられます。そして、セキュリティ検査には広く公開されている多くのテクニックと推奨があります。よくテストされた例として、Microsoft Trustworthy Computing Initiativeのとりくみとして作成された、<link href=\"http://www.microsoft.com/security/sdl/process/release.aspx\">Microsoft SDL</link>があります。"
-
-#: ./doc/security-guide/ch063_compliance-activities.xml49(para)
-msgid ""
-"Security updates are critical to any IaaS deployment, whether private or "
-"public. Vulnerable systems expand attack surfaces, and are obvious targets "
-"for attackers. Common scanning technologies and vulnerability notification "
-"services can help mitigate this threat. It is important that scans are "
-"authenticated and that mitigation strategies extend beyond simple perimeter "
-"hardening. Multi-tenant architectures such as OpenStack are particularly "
-"prone to hypervisor vulnerabilities, making this a critical part of the "
-"system for vulnerability management. See the section on instance isolation "
-"for additional details."
-msgstr "セキュリティアップデートはプライベート、パブリックを問わず、あらゆるIaaS環境において重要です。脆弱なシステムは攻撃面を広げ、攻撃者にターゲットをさらしてしまいます。一般的なスキャニング技術と脆弱性検知サービスはこの脅威を和らげるのに役立ちます。スキャンが認証されたものであり、その緩和戦略が単なる境界線の防御力向上にとどまらないことが重要です。OpenStackのようなマルチテナントアーキテクチャは特にハイパーバイザーの脆弱性に影響されやすく、それはシステムの脆弱性管理の重点項目です。詳細はインスタンス隔離の節を参照してください。"
-
-#: ./doc/security-guide/ch063_compliance-activities.xml52(title)
-msgid "Data classification"
-msgstr "データの分類"
-
-#: ./doc/security-guide/ch063_compliance-activities.xml53(para)
-msgid ""
-"Data Classification defines a method for classifying and handling "
-"information, often to protect customer information from accidental or "
-"deliberate theft, loss, or inappropriate disclosure. Most commonly this "
-"involves classifying information as sensitive or non-sensitive, or as "
-"personally identifiable information (PII). Depending on the context of the "
-"deployment various other classifying criteria may be used (government, "
-"health-care etc). The underlying principle is that data classifications are "
-"clearly defined and in-use. The most common protective mechanisms include "
-"industry standard encryption technologies. See the data security section for"
-" additional details."
-msgstr "データの分類作業は、多くの場合、顧客情報を事故、故意の窃盗、損失、不適切な公開から保護するため、情報の分類と扱いの方法を定義します。一般的にこの作業は、情報を機密性の有無、個人識別の可不可(Personally Identifiable Information, PII)による分類を含みます。使用される基準はその環境、背景によって様々です(政府、ヘルスケアなど)。そして根本的な原則は、そのデータ分類が明確に定義され、通常利用されていることです。もっとも一般的な保護メカニズムには、業界標準の暗号化技術が挙げられます。詳細はデータセキュリティの節を参照してください。"
-
-#: ./doc/security-guide/ch063_compliance-activities.xml56(title)
-msgid "Exception process"
-msgstr "例外プロセス"
-
-#: ./doc/security-guide/ch063_compliance-activities.xml57(para)
-msgid ""
-"An exception process is an important component of an ISMS. When certain "
-"actions are not compliant with security policies that an organization has "
-"defined, they must be logged. Appropriate justification, description and "
-"mitigation details need to be included, and signed off by appropriate "
-"authorities. OpenStack default configurations may vary in meeting various "
-"compliance criteria, areas that fail to meet compliance requirements should "
-"be logged, with potential fixes considered for contribution to the "
-"community."
-msgstr "例外プロセスはISMSの重要な要素です。とある行動が組織の定義したセキュリティポリシーに準拠していない場合、それは記録されなければいけません。適正な理由と緩和策の詳細が含まれ、関係当局に認められる必要があります。OpenStackのデフォルト構成は、様々なコンプライアンス基準、記録されるべきコンプライアンス基準を満たすべく、変化していくでしょう。またそれは、コミュニティへの貢献によって修正されていく可能性があります。"
-
 #. When image changes, this message will be marked fuzzy or untranslated for
 #. you.
 #. It doesn't matter what you translate it to: it's not used at all.
@@ -6130,4113 +10236,7 @@ msgid ""
 "loss."
 msgstr "この値は、暗号学的に安全な乱数生成器を用いて初期設定され、すべてのサービスノードにわたり一貫性を持つべきです。適切な ACL を用いて確実に保護され、データ損失を避けるためにバックアップコピーを必ず持つべきです。"
 
-#: ./doc/security-guide/ch006_introduction-to-case-studies.xml8(title)
-msgid "Introduction to case studies"
-msgstr "ケーススタディの概要"
-
-#: ./doc/security-guide/ch006_introduction-to-case-studies.xml9(para)
-msgid ""
-"This guide refers to two running case studies, which are introduced here and"
-" referred to at the end of each chapter."
-msgstr "本ガイドでは、全体を通して、2 つの運用事例を参照しています。ここでは、これらを概要を説明し、各章末で参照します。"
-
-#: ./doc/security-guide/ch006_introduction-to-case-studies.xml12(title)
-msgid "Case study: Alice, the private cloud builder"
-msgstr "事例: プライベートクラウド構築者のアリス"
-
-#: ./doc/security-guide/ch006_introduction-to-case-studies.xml13(para)
-msgid ""
-"Alice deploys a private cloud for use by a government department in the US. "
-"The cloud must comply with relevant standards, such as FedRAMP. The security"
-" paperwork requirements for this cloud are very high. It must have no direct"
-" access to the internet: its API endpoints, compute instances, and other "
-"resources must be exposed to only systems within the department's network, "
-"which is entirely air-gapped from all other networks. The cloud can access "
-"other network services on the organization's intranet such as the "
-"authentication and logging services."
-msgstr "アリスは、米国のある政府機関で使用するクラウドをデプロイしています。このクラウドは、FedRAMP などの関連基準に準拠する必要があり、またセキュリティ関連の文書業務を行う必要性が非常に高くなっています。クラウドは、インターネットには直接アクセスしてはなりません。API エンドポイント、Compute インスタンス、およびその他のリソースは、その政府機関のネットワーク内のシステムに対してのみ公開される必要があります。このネットワークは、他の全ネットワークから完全に隔離されています。クラウドは、この機関のイントラネット上で、認証/ロギングサービスなどの他のネットワークサービスにアクセスすることが可能です。"
-
-#: ./doc/security-guide/ch006_introduction-to-case-studies.xml25(title)
-msgid "Case study: Bob, the public cloud provider"
-msgstr "事例: パブリッククラウドプロバイダーのボブ"
-
-#: ./doc/security-guide/ch006_introduction-to-case-studies.xml26(para)
-msgid ""
-"Bob is a lead architect for a company that deploys a large greenfield public"
-" cloud. This cloud provides IaaS for the masses and enables any consumer "
-"with a valid credit card access to utility computing and storage, but the "
-"primary focus is enterprise customers. Data privacy concerns are a big "
-"priority for Bob as they are seen as a major barrier to large-scale adoption"
-" of the cloud by organizations."
-msgstr "ボブは、新規展開の大規模なパブリッククラウドのデプロイを行う会社のリードアーキテクトです。このクラウドは、有効なクレジットカードを持つ消費者が、ユーティリティコンピューティングやストレージに使用できる一般大衆向けの IaaS を提供しますが、第一のターゲットは 企業顧客です。企業の間では、データプライバシー問題は、大規模なクラウド導入の大きな障害とみなされているため、ボブにとって優先課題となっています。"
-
-#: ./doc/security-guide/ch030_state-of-networking.xml8(title)
-msgid "State of networking"
-msgstr "ネットワークの状態"
-
-#: ./doc/security-guide/ch030_state-of-networking.xml9(para)
-msgid ""
-"OpenStack Networking in the Grizzly release enables the end-user or tenant "
-"to define, utilize, and consume networking resources in new ways that had "
-"not been possible in previous OpenStack Networking releases. OpenStack "
-"Networking provides a tenant-facing API for defining network connectivity "
-"and IP addressing for instances in the cloud in addition to orchestrating "
-"the network configuration. With the transition to an API-centric networking "
-"service, cloud architects and administrators should take into consideration "
-"best practices to secure physical and virtual network infrastructure and "
-"services."
-msgstr "Grizzly リリースの OpenStack Networking により、エンドユーザーまたはテナントは、以前の OpenStack Networking リリースではできなかった新しい方法でネットワークリソースを定義、利用、消費することが可能です。OpenStack Networking は、ネットワーク設定のオーケストレーションに加えて、クラウド内のインスタンスを対象としたネットワーク接続の定義と IP アドレス指定用の対テナント API を提供します。API 中心のネットワークサービスへの移行にあたっては、クラウドのアーキテクトや管理者が、物理/仮想ネットワークのインフラストラクチャーとサービスをセキュリティ保護するためのベストプラクティスを考慮すべきです。"
-
-#: ./doc/security-guide/ch030_state-of-networking.xml10(para)
-msgid ""
-"OpenStack Networking was designed with a plug-in architecture that provides "
-"extensibility of the API through open source community or third-party "
-"services. As you evaluate your architectural design requirements, it is "
-"important to determine what features are available in OpenStack Networking "
-"core services, any additional services that are provided by third-party "
-"products, and what supplemental services are required to be implemented in "
-"the physical infrastructure."
-msgstr "OpenStack Networking は、オープンソースコミュニティやサードパーティーのサービスによる API の拡張性を提供するプラグインアーキテクチャーで設計されました。アーキテクチャーの設計要件を評価するにあたっては、OpenStack Networking のコアサービスではどのような機能が提供されているか、サードパーティの製品によって提供される追加のサービスがあるかどうか、物理インフラストラクチャーにはどのような補足サービスを実装する必要があるかを判断することが重要です。"
-
-#: ./doc/security-guide/ch030_state-of-networking.xml20(para)
-msgid ""
-"This section is a high-level overview of what processes and best practices "
-"should be considered when implementing OpenStack Networking. We will talk "
-"about the current state of services that are available, what future services"
-" will be implemented, and the current limitations in this project."
-msgstr "本項には、OpenStack Networking を実装する際に検討すべきプロセスとベストプラクティスについての大まかな概要をまとめています。提供されているサービスの現在の状況 、将来実装されるサービス、本プロジェクトにおける現在の制限事項などについて説明します。"
-
-#: ./doc/security-guide/ch043_database-transport-security.xml8(title)
-msgid "Database transport security"
-msgstr "データベース通信セキュリティ"
-
-#: ./doc/security-guide/ch043_database-transport-security.xml9(para)
-msgid ""
-"This chapter covers issues related to network communications to and from the"
-" database server. This includes IP address bindings and encrypting network "
-"traffic with SSL."
-msgstr "本章はデータベースとのネットワーク通信に関連する問題を取り扱います。これには、IP アドレスのバインドや SSL を用いた暗号化ネットワーク通信を含みます。"
-
-#: ./doc/security-guide/ch043_database-transport-security.xml14(title)
-msgid "Database server IP address binding"
-msgstr "データベースサーバーの IP アドレスバインド"
-
-#: ./doc/security-guide/ch043_database-transport-security.xml15(para)
-msgid ""
-"To isolate sensitive database communications between the services and the "
-"database, we strongly recommend that the database server(s) be configured to"
-" only allow communications to and from the database over an isolated "
-"management network. This is achieved by restricting the interface or IP "
-"address on which the database server binds a network socket for incoming "
-"client connections."
-msgstr "サービスとデータベース間の機微なデータベース通信を隔離するために、データベースサーバーが隔離された管理ネットワーク経由のみでデータベースと通信できるように設定することを強く推奨します。データベースサーバーがクライアントからの通信用のネットワークソケットをバインドするインターフェースまたは IP アドレスを制限することにより、これを実現できます。"
-
-#: ./doc/security-guide/ch043_database-transport-security.xml24(title)
-msgid "Restricting bind address for MySQL"
-msgstr "MySQL のバインドアドレスの制限"
-
-#: ./doc/security-guide/ch043_database-transport-security.xml25(para)
-#: ./doc/security-guide/ch043_database-transport-security.xml63(para)
-msgid "In <filename>my.cnf</filename>:"
-msgstr "<filename>my.cnf</filename>:"
-
-#: ./doc/security-guide/ch043_database-transport-security.xml31(title)
-msgid "Restricting listen address for PostgreSQL"
-msgstr "PostgreSQL のバインドアドレスの制限"
-
-#: ./doc/security-guide/ch043_database-transport-security.xml32(para)
-msgid "In <filename>postgresql.conf</filename>:"
-msgstr "<filename>postgresql.conf</filename>:"
-
-#: ./doc/security-guide/ch043_database-transport-security.xml37(title)
-msgid "Database transport"
-msgstr "データベース通信"
-
-#: ./doc/security-guide/ch043_database-transport-security.xml38(para)
-msgid ""
-"In addition to restricting database communications to the management "
-"network, we also strongly recommend that the cloud administrator configure "
-"their database backend to require SSL. Using SSL for the database client "
-"connections protects the communications from tampering and eavesdropping. As"
-" will be discussed in the next section, using SSL also provides the "
-"framework for doing database user authentication through X.509 certificates "
-"(commonly referred to as PKI). Below is guidance on how SSL is typically "
-"configured for the two popular database backends MySQL and PostgreSQL."
-msgstr "データベース通信を管理ネットワークに制限することに加えて、クラウド管理者がそれらのデータベースのバックエンドに SSL を要求するように設定することを強く推奨します。データベースのクライアント接続に SSL を使用することにより、改ざんや盗聴から通信を保護できます。次のセクションで議論するように、SSL を使用することにより、データベースのユーザー認証に X.509 証明書 (一般的に PKI として参照されます) を使用するフレームワークも提供できます。以下は、2 つの有名なデータベースバックエンド MySQL と PostgreSQL に SSL を典型的に設定する方法について示します。"
-
-#: ./doc/security-guide/ch043_database-transport-security.xml50(para)
-msgid ""
-"When installing the certificate and key files, ensure that the file "
-"permissions are restricted, for example <placeholder-1/>, and the ownership "
-"is restricted to the database daemon user to prevent unauthorized access by "
-"other processes and users on the database server."
-msgstr "証明書と鍵ファイルをインストールするとき、ファイルのパーミッションが制限されていることを確認します。たとえば、<placeholder-1/> を実行すると、データベースサーバー上の他のプロセスやユーザーによる権限のないアクセスを防ぐために、所有者がデータベースデーモンのユーザーに制限されます。"
-
-#: ./doc/security-guide/ch043_database-transport-security.xml60(title)
-msgid "MySQL SSL configuration"
-msgstr "MySQL SSL 設定"
-
-#: ./doc/security-guide/ch043_database-transport-security.xml61(para)
-msgid ""
-"The following lines should be added in the system-wide MySQL configuration "
-"file:"
-msgstr "以下の行をシステム全体の MySQL 設定ファイルに追加する必要があります。"
-
-#: ./doc/security-guide/ch043_database-transport-security.xml69(para)
-#: ./doc/security-guide/ch043_database-transport-security.xml80(para)
-msgid ""
-"Optionally, if you wish to restrict the set of SSL ciphers used for the "
-"encrypted connection. See <link "
-"href=\"http://www.openssl.org/docs/apps/ciphers.html\">http://www.openssl.org/docs/apps/ciphers.html</link>"
-" for a list of ciphers and the syntax for specifying the cipher string:"
-msgstr "オプションとして、暗号化通信に使用される SSL 暗号を制限したい場合、暗号の一覧と暗号文字列を設定するための構文は <link href=\"http://www.openssl.org/docs/apps/ciphers.html\">http://www.openssl.org/docs/apps/ciphers.html</link> を参照してください。"
-
-#: ./doc/security-guide/ch043_database-transport-security.xml74(title)
-msgid "PostgreSQL SSL configuration"
-msgstr "PostgreSQL SSL 設定"
-
-#: ./doc/security-guide/ch043_database-transport-security.xml75(para)
-msgid ""
-"The following lines should be added in the system-wide PostgreSQL "
-"configuration file, <filename>postgresql.conf</filename>."
-msgstr "以下の行をシステム全体の PostgreSQL 設定ファイル <filename>postgresql.conf</filename> に追加する必要があります。"
-
-#: ./doc/security-guide/ch043_database-transport-security.xml82(para)
-msgid ""
-"The server certificate, key, and certificate authority (CA) files should be "
-"placed in the $PGDATA directory in the following files:"
-msgstr "サーバー証明書、鍵、認証局 (CA) のファイルを $PGDATA ディレクトリの以下のファイルに置く必要があります。"
-
-#: ./doc/security-guide/ch043_database-transport-security.xml86(para)
-msgid "<filename>$PGDATA/server.crt</filename> - Server certificate"
-msgstr "<filename>$PGDATA/server.crt</filename> - サーバー証明書"
-
-#: ./doc/security-guide/ch043_database-transport-security.xml90(para)
-msgid ""
-"<filename>$PGDATA/server.key</filename> - Private key corresponding to "
-"<filename>server.crt</filename>"
-msgstr "<filename>$PGDATA/server.key</filename> - <filename>server.crt</filename> に対応する秘密鍵"
-
-#: ./doc/security-guide/ch043_database-transport-security.xml94(para)
-msgid ""
-"<filename>$PGDATA/root.crt</filename> - Trusted certificate authorities"
-msgstr "<filename>$PGDATA/root.crt</filename> - 信頼された認証局"
-
-#: ./doc/security-guide/ch043_database-transport-security.xml98(para)
-msgid "<filename>$PGDATA/root.crl</filename> - Certificate revocation list"
-msgstr "<filename>$PGDATA/root.crl</filename> - 証明書失効リスト"
-
-#: ./doc/security-guide/ch048_key-management.xml8(title)
-msgid "Key management"
-msgstr "キーマネージメント"
-
-#: ./doc/security-guide/ch048_key-management.xml9(para)
-msgid ""
-"To address the often mentioned concern of tenant data privacy and limiting "
-"cloud provider liability, there is greater interest within the OpenStack "
-"community to make data encryption more ubiquitous. It is relatively easy for"
-" an end-user to encrypt their data prior to saving it to the cloud, and this"
-" is a viable path for tenant objects such as media files, database archives "
-"among others. However, when client side encryption is used for virtual "
-"machine images, block storage etc, client intervention is necessary in the "
-"form of presenting keys to unlock the data for further use. To seamlessly "
-"secure the data and yet have it accessible without burdening the client with"
-" having to manage their keys and interactively provide them calls for a key "
-"management service within OpenStack. Providing encryption and key management"
-" services as part of OpenStack eases data-at-rest security adoption, "
-"addresses customer concerns about the privacy and misuse of their data with "
-"the added advantage of limiting cloud provider liability. Provider liability"
-" is of concern in multi-tenant public clouds with respect to handing over "
-"tenant data during a misuse investigation."
-msgstr "頻繁に触れられるテナントデータのプライバシーとクラウドプロバイダーの法的責任の限度についての懸念に対処するために、OpenStack コミュニティはデーターの暗号化を様々な個所へ適用することに興味を持っています。エンドユーザーがクラウドにデータをセーブする前にそれらを暗号化することは比較的に簡単で、メディアファイル、データベースアーカイブなどテナントオブジェクトに実行可能な方法です。しかし、クライアント側の暗号化が仮想マシンのイメージを使用する場合、ブロックストレージなどクライアントの介入では、データの更なる利用のために解除する鍵を提示する形式が必要です。しかし、クライアント側の暗号化が仮想マシンのイメージを使用する場合、ブロックストレージなどクライアントの介入では、データの更なる利用のために解除する鍵を提示する形式が必要です。シームレスにデータを保護し、クライアントの鍵を管理し対話的に鍵を提供することで負担をかけることなく、それがアクセスできるようにするには、OpenStack 内に鍵管理サービスを求められます。OpenStack の一環として、暗号化と鍵管理サービスの提供は、データ保存セキュリティ導入を容易にし、クラウド·プロバイダーの法的責任を制限する追加の利点と、プライバシーとデータの誤使用に関する顧客の懸念に対処しています。プロバイダの法的責任は、マルチテナントのパブリッククラウドで誤った調査によってテナントデータを引き渡す事が懸念されています。"
-
-#: ./doc/security-guide/ch048_key-management.xml10(para)
-msgid ""
-"A key management service is in the early stages of being developed and has a"
-" way to go before becoming an official component of OpenStack. Refer to "
-"<link "
-"href=\"https://github.com/cloudkeep/barbican/wiki/_pages\">https://github.com/cloudkeep/barbican/wiki/_pages</link>"
-" for details."
-msgstr "鍵管理は、まだ開発の初期段階で、OpenStack の正式コンポーネントになる過程の途中です。詳細は、<link href=\"https://github.com/cloudkeep/barbican/wiki/_pages\">https://github.com/cloudkeep/barbican/wiki/_pages</link>を参照してください。"
-
-#: ./doc/security-guide/ch048_key-management.xml11(para)
-msgid ""
-"It shall support the creation of keys, and their secure saving (with a "
-"service master-key). Some of the design questions still being debated are "
-"how much of the Key Management Interchange Protocol (KMIP) to support, key "
-"formats, and certificate management. The key manager will be pluggable to "
-"facilitate deployments that need a third-party Hardware Security Module "
-"(HSM)."
-msgstr "鍵管理は、鍵の作成と安全な保存'（'サービスマスター鍵付き'）'をサポートしなければなりません。いくつかの鍵管理における相互運用性プロトコル"
-
-#: ./doc/security-guide/ch048_key-management.xml12(para)
-msgid ""
-"OpenStack Block Storage, cinder, is the first service looking to integrate "
-"with the key manager to provide volume encryption."
-msgstr "OpenStack Block Storage (cinder) は、ボリュームの暗号化を提供するためにキーマネージャーとの統合を検討した最初のサービスです。"
-
-#: ./doc/security-guide/ch048_key-management.xml14(title)
-msgid "References:"
-msgstr "参考資料："
-
-#: ./doc/security-guide/ch048_key-management.xml16(link)
-msgid "Barbican"
-msgstr "Barbican"
-
-#: ./doc/security-guide/ch048_key-management.xml19(link)
-msgid "KMIP"
-msgstr "KMIP"
-
-#: ./doc/security-guide/ch009_case-studies.xml8(title)
-msgid "Case studies: system documentation"
-msgstr "ケーススタディ: システムのドキュメント"
-
-#: ./doc/security-guide/ch009_case-studies.xml9(para)
-msgid ""
-"In this case study we discuss how Alice and Bob would address their system "
-"documentation requirements. The documentation suggested above includes "
-"hardware and software records, network diagrams, and system configuration "
-"details."
-msgstr "今回のケーススタディでは、アリスとボブがシステムの文書要件にどのように対処していくか見ていきます。上記で述べた文書には、ハードウェアおよびソフトウェアの記録、ネットワーク図、システム設定の詳細などが含まれます。"
-
-#: ./doc/security-guide/ch009_case-studies.xml12(para)
-msgid ""
-"Alice needs detailed documentation to satisfy FedRamp requirements. She sets"
-" up a configuration management database (CMDB) to store information "
-"regarding all of the hardware, firmware, and software versions used "
-"throughout the cloud. She also creates a network diagram detailing the cloud"
-" architecture, paying careful attention to the security domains and the "
-"services that span multiple security domains."
-msgstr "アリスは、FedRam 要件を満たす詳細文書が必要です。構成管理データベース (CMDB) を設定して、クラウド全体で使用されるハードウェア、ファームウェア、ソフトウェアバージョンの情報を格納していきます。また、セキュリティドメインや、複数のセキュリティドメインにまたがるサービスに細心の注意を払い、クラウドアーキテクチャーの詳細を示したネットワーク図も作成します。"
-
-#: ./doc/security-guide/ch009_case-studies.xml13(para)
-msgid ""
-"Alice also needs to record each network service running in the cloud, what "
-"interfaces and ports it binds to, the security domains for each service, and"
-" why the service is needed. Alice decides to build automated tools to log "
-"into each system in the cloud over secure shell (SSH) using the <link "
-"href=\"http://fabfile.org\">Python Fabric library</link>. The tools collect "
-"and store the information in the CMDB, which simplifies the audit process."
-msgstr "アリスは、クラウドで実行中の各ネットワークサービス、バインド先のインターフェースやポート、各サービスに対するセキュリティドメイン、そのサービスが必要な理由を記録する必要があります。 <link href=\"http://fabfile.org\">Python Fabric ライブラリ</link>を使用して、セキュアシェル (SSH) でクラウド内の各システムにログインする自動化ツールを構築することにしました。このツールは、CMDB の情報を収集・格納して監査プロセスを簡素化します。"
-
-#: ./doc/security-guide/ch009_case-studies.xml17(para)
-msgid "In this case, Bob will approach these steps the same as Alice."
-msgstr "今回のケーススタディでは、ボブはアリスと同様の手段を取ります。"
-
-#: ./doc/security-guide/ch056_case-studies-instance-management.xml8(title)
-msgid "Case studies: instance management"
-msgstr "ケーススタディ：インスタンス管理"
-
-#: ./doc/security-guide/ch056_case-studies-instance-management.xml9(para)
-msgid ""
-"In this case study we discuss how Alice and Bob would architect their clouds"
-" with respect to instance entropy, scheduling instances, trusted images, and"
-" instance migrations."
-msgstr "このケーススタディでは、アリスとボブがインスタンスのエントロピー、インスタンスのスケジューリング、信頼できるイメージ、インスタンスのマイグレーションを尊重しつつ、彼らのクラウドを設計する方法について議論します。"
-
-#: ./doc/security-guide/ch056_case-studies-instance-management.xml12(para)
-msgid ""
-"Alice has a need for lots of high quality entropy in the instances. For this"
-" reason, she decides to purchase hardware with Intel Ivy Bridge chip sets "
-"that support the RdRand instruction on each compute node. Using the entropy "
-"gathering daemon (EGD) and LibVirt's EGD support, Alice ensures that this "
-"entropy pool is distributed to the instances on each compute node."
-msgstr "アリスはインスタンス群に高い品質の多くのエントロピーに対するニーズがあります。このため、彼女は各 compute ノード上で RdRand 命令をサポートする Intel Ivy Bridge チップセットを持つハードウェアの購入を決めました。エントロピー収集デーモン (EGD) と LibVirt の EGD サポートを使用して、Alice はこのエントロピープールが各 compute ノード上のインスタンスに配信されるようにします。"
-
-#: ./doc/security-guide/ch056_case-studies-instance-management.xml13(para)
-msgid ""
-"For instance scheduling, Alice uses the trusted compute pools to ensure that"
-" all cloud workloads are deployed to nodes that presented a proper boot time"
-" attestation. Alice decides to disable user permissions for image uploading "
-"to help ensure that the images used in the cloud are generated in a known "
-"and trusted manner by the cloud administrators."
-msgstr "インスタンススケジューリングでは、全てのクラウド負荷が適切な起動時間保証を示すノードにデプロイされるようにする為、アリスは信頼できる compute プールを使用します。クラウド中で使用されるイメージがクラウド管理者に既知で信頼できる方法で作成されたものである事を保証するため、アリスはユーザにイメージをアップロードする権限を与えない事を決めました。"
-
-#: ./doc/security-guide/ch056_case-studies-instance-management.xml14(para)
-msgid ""
-"Finally, Alice disables instance migrations as this feature is less critical"
-" for the high performance application workloads expected to run in this "
-"cloud. This helps avoid the various security concerns related to instance "
-"migrations."
-msgstr "最後に、アリスはインスタンスのマイグレーションを無効化しました。この機能はこのクラウドで実行される予定の高パフォーマンスアプリケーション負荷にはほとんど不要だからです。これにより、インスタンスマイグレーションにまつわる様々なセキュリティ関連を避ける事ができます。"
-
-#: ./doc/security-guide/ch056_case-studies-instance-management.xml18(para)
-msgid ""
-"Bob is aware that entropy will be a concern for some of his customers, such "
-"as those in the financial industry. However, due to the added cost and "
-"complexity, Bob has decided to forgo integrating hardware entropy into the "
-"first iteration of his cloud. He adds hardware entropy as a fast-follow to "
-"do for a later improvement for the second generation of his cloud "
-"architecture."
-msgstr "ボブは、金融業界の企業ユーザの幾つかにとってエントロピーが重要となる事を理解しています。しかしながら、費用と複雑さが増える為、ボブは彼のクラウドの初回導入分にハードウェアエントロピーの導入を見送る事を決めました。彼は自分の２世代目のクラウドアーキテクチャに向けた後の改善では、早期のフォローとしてハードウェアエントロピーを追加します。"
-
-#: ./doc/security-guide/ch056_case-studies-instance-management.xml19(para)
-msgid ""
-"Bob is interested in ensuring that customers receive a high quality of "
-"service. He is concerned that providing too much explicit user control over "
-"instance scheduling could negatively impact the quality of service. So he "
-"disables this feature. Bob provides images in the cloud from a known trusted"
-" source for users to use. Additionally, he also allows users to upload their"
-" own images. However, users cannot generally share their images. This helps "
-"prevent a user from sharing a malicious image, which could negatively impact"
-" the security of other users in the cloud."
-msgstr "ボブは、顧客が高品質なサービスを受けられるようにする事に興味があります。彼は、インスタンススケジューリングを超えた過剰なほど明確なユーザコントロールの提供が、サービス品質（QoS）にマイナス影響を与える事を心配しています。ですので、この機能を無効化しました。ボブは使用するユーザに対して既知の信頼できるソースからのクラウド中のイメージを提供します。加えて、彼はまた、ユーザに自分のイメージアップロードを許可します。しかしながら、ユーザは一般に自分のイメージを共有できません。これは、クラウド中の他のユーザのセキュリティにマイナスインパクトを与えかねない、悪意あるイメージを共有する事からユーザを守る助けになります。"
-
-#: ./doc/security-guide/ch056_case-studies-instance-management.xml20(para)
-msgid ""
-"For migrations, Bob wants to enable secure instance migrations in order to "
-"support rolling upgrades with minimal user downtime. Bob ensures that all "
-"migrations occur on an isolated VLAN. He plans to defer implementing "
-"encrypted migrations until this is better supported in <placeholder-1/> "
-"client tools. However, he makes a note to track this carefully and switch to"
-" encrypted migrations as soon as possible."
-msgstr "マイグレーションでは、ボブは最小のユーザダウンタイムでのローリングアップデートをサポートする為に、安全なインスタンスマイグレーションを有効にしたいと思っています。ボブは、全てのマイグレーションが独立した VLAN 上で実行されるようにします。彼は、<placeholder-1/> クライアントツールが暗号化マイグレーションをより良くサポートするまで暗号化マイグレーションの実装を遅らせる計画を立てています。"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch008_system-roles-types.xml101(None)
-#: ./doc/security-guide/ch008_system-roles-types.xml106(None)
-msgid ""
-"@@image: 'static/services-protocols-ports.png'; "
-"md5=fb1e9f47d969127b7a5ca683d38cfe20"
-msgstr "@@image: 'static/services-protocols-ports.png'; md5=fb1e9f47d969127b7a5ca683d38cfe20"
-
-#: ./doc/security-guide/ch008_system-roles-types.xml8(title)
-msgid "System documentation requirements"
-msgstr "システムの文書化における要件"
-
-#: ./doc/security-guide/ch008_system-roles-types.xml9(para)
-msgid ""
-"The system documentation for an OpenStack cloud deployment should follow the"
-" templates and best practices for the Enterprise Information Technology "
-"System in your organization. Organizations often have compliance "
-"requirements which may require an overall System Security Plan to inventory "
-"and document the architecture of a given system. There are common challenges"
-" across the industry related to documenting the dynamic cloud infrastructure"
-" and keeping the information up-to-date."
-msgstr "OpenStack クラウドデプロイメントのシステム文書化は、その組織のエンタープライズ IT システムを対象とするテンプレートとベストプラクティスに従って行うべきです。組織には大抵、コンプライアンス要件が設定されており、それによって対象システムのインベントリ作成とアーキテクチャの文書化を行う全体的なシステムセキュリティ計画が義務付けられている場合があります。動的なクラウドインフラストラクチャーを文書化し、情報を最新の状態に維持するのあたっては、業界全体の共通課題があります。 "
-
-#: ./doc/security-guide/ch008_system-roles-types.xml18(title)
-msgid "System roles and types"
-msgstr "システムのロールとタイプ"
-
-#: ./doc/security-guide/ch008_system-roles-types.xml19(para)
-msgid ""
-"The two broadly defined types of nodes that generally make up an OpenStack "
-"installation are:"
-msgstr "通常 OpenStack のインストールを構成している、広く定義された 2 つのノードタイプは次のとおりです。"
-
-#: ./doc/security-guide/ch008_system-roles-types.xml23(para)
-msgid ""
-"Infrastructure nodes. The nodes that run the cloud related services such as "
-"the OpenStack Identity Service, the message queuing service, storage, "
-"networking, and other services required to support the operation of the "
-"cloud."
-msgstr "インフラストラクチャーノード。OpenStack Identity、メッセージキューサービス、ストレージ、ネットワーク、およびクラウドの運用をサポートするために必要なその他のサービスなどのクラウド関連サービスを実行するノードです。"
-
-#: ./doc/security-guide/ch008_system-roles-types.xml30(para)
-msgid ""
-"Compute, storage, or other resource nodes. Provide storage capacity or "
-"virtual machines for your cloud."
-msgstr "コンピュート、ストレージ、その他のリソースのノード。クラウド用のストレージ容量や仮想マシンを提供するノードです。"
-
-#: ./doc/security-guide/ch008_system-roles-types.xml37(title)
-msgid "System inventory"
-msgstr "システムインベントリ"
-
-#: ./doc/security-guide/ch008_system-roles-types.xml38(para)
-msgid ""
-"Documentation should provide a general description of the OpenStack "
-"environment and cover all systems used (production, development, test, "
-"etc.). Documenting system components, networks, services, and software often"
-" provides the bird's-eye view needed to thoroughly cover and consider "
-"security concerns, attack vectors and possible security domain bridging "
-"points. A system inventory may need to capture ephemeral resources such as "
-"virtual machines or virtual disk volumes that would otherwise be persistent "
-"resources in a traditional IT system."
-msgstr "文書には、OpenStack 環境の概要を記載し、使用する全システム (実稼働、開発、テストなど)  を対象とするべきです。多くの場合、システムコンポーネント、ネットワーク、サービス、およびソフトウェアについて文書化することにより、セキュリティ課題、攻撃ベクトル、考えられるセキュリティドメインのブリッジングポイントを完全に網羅して検討するにあたって必要な概観が提供されます。システムインベントリには、従来の IT システムでは永続的なリソースとされている、仮想マシンや仮想ディスクボリュームなどの一時的なリソースを取り込む必要がある場合があります。"
-
-#: ./doc/security-guide/ch008_system-roles-types.xml48(title)
-msgid "Hardware inventory"
-msgstr "ハードウェアインベントリ"
-
-#: ./doc/security-guide/ch008_system-roles-types.xml49(para)
-msgid ""
-"Clouds without stringent compliance requirements for written documentation "
-"might benefit from having a Configuration Management Database "
-"(<glossterm>CMDB</glossterm>). CMDBs are normally used for hardware asset "
-"tracking and overall life-cycle management. By leveraging a CMDB, an "
-"organization can quickly identify cloud infrastructure hardware. For "
-"example, compute nodes, storage nodes, and network devices that exist on the"
-" network but that might not be adequately protected and/or forgotten. "
-"OpenStack provisioning system might provide some CMDB-like functions "
-"especially if auto-discovery features of hardware attributes are available."
-msgstr "文書化に対する厳密なコンプライアンス要件のないクラウドの場合は、少なくとも構成管理データベース (<glossterm>CMDB</glossterm>) を使用することによってメリットが得られる可能性があります。CMDB は通常、ハードウェア資産の追跡や全般的なライフサイクル管理に使用されます。CMDB を活用することにより、組織はネットワーク上に存在するクラウドインフラストラクチャーハードウェア (例: コンピュートノード、ストレージノード、ネットワークデバイスなど) の中で適切に保護されていないハードウェアや忘れられているハードウェアを迅速に特定することができます。OpenStack のプロビジョニングシステムは、ハードウェア属性の自動検出機能が利用できる場合は特に、CMDB のような機能を一部提供することが可能です。"
-
-#: ./doc/security-guide/ch008_system-roles-types.xml63(title)
-msgid "Software inventory"
-msgstr "ソフトウェアインベントリ"
-
-#: ./doc/security-guide/ch008_system-roles-types.xml64(para)
-msgid ""
-"Just as with hardware, all software components within the OpenStack "
-"deployment should be documented. Components here should include system "
-"databases; OpenStack software components and supporting sub-components; and,"
-" supporting infrastructure software such as load-balancers, reverse proxies,"
-" and network address translators. Having an authoritative list like this may"
-" be critical toward understanding total system impact due to a compromise or"
-" vulnerability of a specific class of software."
-msgstr "ハードウェアと同様に、OpenStack デプロイメント内のソフトウェアコンポーネントはすべて文書化しておくべきです。このコンポーネントには、システムデータベース、OpenStack ソフトウェアコンポーネントおよびサポートサブコンポーネント、ロードバランサー/リバースプロキシ/ネットワークアドレストランスレーターなどのサポートインフラストラクチャーソフトウェアなどが含まれます。このような信頼できる一覧を用意しておくことは、ソフトウェアの特定のクラスの侵害や脆弱性によってシステムが受ける全体的な影響を把握するために極めて重要となります。"
-
-#: ./doc/security-guide/ch008_system-roles-types.xml76(title)
-msgid "Network topology"
-msgstr "ネットワークトポロジー"
-
-#: ./doc/security-guide/ch008_system-roles-types.xml77(para)
-msgid ""
-"A network topology should be provided with highlights specifically calling "
-"out the data flows and bridging points between the security domains. Network"
-" ingress and egress points should be identified along with any OpenStack "
-"logical system boundaries. Multiple diagrams may be needed to provide "
-"complete visual coverage of the system. A network topology document should "
-"include virtual networks created on behalf of tenants by the system along "
-"with virtual machine instances and gateways created by OpenStack."
-msgstr "ネットワークトポロジーは、セキュリティドメイン間のデータフローとブリッジングポイントをはっきりと識別して強調するようにして作成すべきです。OpenStack の論理的なシステム境界とともに、ネットワークの受信および送信ポイントを明確にすることを推奨します。システムを完全に視覚的に網羅するには、図を複数作成する必要がある場合があります。また、ネットワークトポロジーの文書には、テナントに代わってシステムが作成した仮想ネットワークや、OpenStack によって作成された仮想マシンインスタンスとゲートウェイを含めるべきです。"
-
-#: ./doc/security-guide/ch008_system-roles-types.xml88(title)
-msgid "Services, protocols and ports"
-msgstr "サービス、プロトコル、およびポート"
-
-#: ./doc/security-guide/ch008_system-roles-types.xml89(para)
-msgid ""
-"The service, protocols and ports table provides important additional detail "
-"of an OpenStack deployment. A table view of all services running within the "
-"cloud infrastructure can immediately inform, guide, and help check security "
-"procedures. Firewall configuration, service port conflicts, security "
-"remediation areas, and compliance requirements become easier to manage when "
-"you have concise information available. Consider the following table:"
-msgstr "サービス、プロトコル、ポートの表には OpenStack デプロイメントの重要な追加情報を記載します。クラウドインフラストラクチャー内で稼働中の全サービスを表にまとめると、情報や指針を直ちに確認することができ、セキュリティプロシージャーをチェックするのに役立ちます。簡潔な情報が提供されると、ファイアウォールの設定やサービスポートの競合、セキュリティ修復領域、コンプライアンス要件をより容易に管理できるようになります。以下の表を検討してください。 "
-
-#: ./doc/security-guide/ch008_system-roles-types.xml109(para)
-msgid ""
-"Referencing a table of services, protocols and ports can help in "
-"understanding the relationship between OpenStack components. It is highly "
-"recommended that OpenStack deployments have information similar to this on "
-"record."
-msgstr "サービス、プロトコル、ポートの表を参照すると、OpenStack のコンポーネント間の関係を理解するのに役立ちます。OpenStack のデプロイメントには、これと同様の情報を記録することを強く推奨します。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml9(para)
-msgid ""
-"Horizon is the OpenStack dashboard that provides users a self-service portal"
-" to provision their own resources within the limits set by administrators. "
-"These include provisioning users, defining instance flavors, uploading VM "
-"images, managing networks, setting up security groups, starting instances, "
-"and accessing the instances through a console."
-msgstr "Horizon は OpenStack のダッシュボードです。管理者により設定された制限の範囲内でユーザー自身のリソースを展開できるセルフサービスポータルをユーザーに提供します。これらには、ユーザーの管理、インスタンスのフレーバーの定義、仮想マシンイメージのアップロード、ネットワークの管理、セキュリティグループのセットアップ、インスタンスの起動、インスタンスへのコンソール経由のアクセスなどがあります。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml14(para)
-msgid ""
-"The dashboard is based on the Django web framework, therefore secure "
-"deployment practices for Django apply directly to horizon. This guide "
-"provides a popular set of Django security recommendations, further "
-"information can be found by reading the <link "
-"href=\"https://docs.djangoproject.com/en/1.5/#security\">Django deployment "
-"and security documentation</link>."
-msgstr "ダッシュボードは Django ウェブフレームワークに基づいています。そのため、Django のセキュアな導入プラクティスをそのまま Horizon に適用できます。このガイドは Django のセキュリティ推奨事項の一般的なものを提供します。さらなる情報は <link href=\"https://docs.djangoproject.com/en/1.5/#security\">Django deployment and security documentation</link> を読むことにより得られます。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml21(para)
-msgid ""
-"The dashboard ships with reasonable default security settings, and has good "
-"<link "
-"href=\"http://docs.openstack.org/developer/horizon/topics/deployment.html\">deployment"
-" and configuration documentation</link>."
-msgstr "ダッシュボードは適度なデフォルトのセキュリティ設定をしてあります。また、素晴らしい <link href=\"http://docs.openstack.org/developer/horizon/topics/deployment.html\">deployment and configuration documentation</link> (導入と設定のドキュメント) があります。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml26(title)
-msgid "Basic web server configuration"
-msgstr "基本的なウェブサーバーの設定"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml27(para)
-msgid ""
-"The dashboard should be deployed as a Web Services Gateway Interface (WSGI) "
-"application behind an HTTPS proxy such as Apache or nginx. If Apache is not "
-"already in use, we recommend nginx since it is lighter weight and easier to "
-"configure correctly."
-msgstr "ダッシュボードは、Apache や nginx のような HTTPS プロキシの後ろに Web Services Gateway Interface (WSGI) アプリケーションとして導入すべきです。まだ Apache を使用していなければ、nginx を推奨します。こちらのほうが軽量かつ正しく設定しやすいです。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml32(para)
-msgid ""
-"When using nginx, we recommend <link "
-"href=\"http://docs.gunicorn.org/en/latest/deploy.html\">gunicorn</link> as "
-"the wsgi host with an appropriate number of synchronous workers. We strongly"
-" advise against deployments using fastcgi, scgi, or uWSGI. We strongly "
-"advise against the use of synthetic performance benchmarks when choosing a "
-"wsgi server."
-msgstr "nginx を使用している場合、適切な数の同期ワーカーを持つ WSGI ホストとして <link href=\"http://docs.gunicorn.org/en/latest/deploy.html\">gunicorn</link> を推奨します。fastcgi、scgi、uWSGI 等の使用を強く推奨します。WSGI サーバーを選択するとき、統合パフォーマンスベンチマークの使用を強く推奨します。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml39(para)
-msgid ""
-"When using Apache, we recommend <link "
-"href=\"https://docs.djangoproject.com/en/1.5/howto/deployment/wsgi/modwsgi/\">mod_wsgi</link>"
-" to host dashboard."
-msgstr "Apache を使用しているとき、ダッシュボードをホストするために <link href=\"https://docs.djangoproject.com/en/1.5/howto/deployment/wsgi/modwsgi/\">mod_wsgi</link> を推奨します。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml44(title)
-msgid "HTTPS"
-msgstr "HTTPS"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml45(para)
-msgid ""
-"Deploy the dashboard behind a secure <glossterm>HTTPS</glossterm> server by "
-"using a valid, trusted certificate from a recognized certificate authority "
-"(CA). Private organization-issued certificates are only appropriate when the"
-" root of trust is pre-installed in all user browsers."
-msgstr "ダッシュボードは、認知されている認証局 (CA) から発行された有効かつ信頼できる証明書を使用しているセキュアな <glossterm>HTTPS</glossterm> サーバーの後ろに導入します。プライベートな組織で発行された証明書は、ルート証明機関がお使いのすべてのブラウザーに事前インストールされているときのみ、適切に動作します。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml52(para)
-msgid ""
-"Configure HTTP requests to the dashboard domain to redirect to the fully "
-"qualified HTTPS URL."
-msgstr "ダッシュボードのドメインに対する HTTP リクエストは、完全修飾された HTTPS URL にリダイレクトされるよう設定します。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml56(title)
-msgid "HTTP Strict Transport Security (HSTS)"
-msgstr "HTTP Strict Transport Security (HSTS)"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml57(para)
-msgid "It is highly recommended to use HTTP Strict Transport Security (HSTS)."
-msgstr "HTTP Strict Transport Security (HSTS) の使用が強く推奨されます。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml60(para)
-msgid ""
-"If you are using an HTTPS proxy in front of your web server, rather than "
-"using an HTTP server with HTTPS functionality, follow the <link "
-"href=\"https://docs.djangoproject.com/en/1.5/ref/settings/#secure-proxy-ssl-"
-"header\">Django documentation on modifying the SECURE_PROXY_SSL_HEADER "
-"variable</link>."
-msgstr "ウェブブラウザーの前で HTTPS プロキシを使用している場合、HTTPS 機能を持つ HTTP サーバーを使用するより、<link href=\"https://docs.djangoproject.com/en/1.5/ref/settings/#secure-proxy-ssl-header\">Django documentation on modifying the SECURE_PROXY_SSL_HEADER variable</link> に従うほうが良いです。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml67(para)
-msgid ""
-"See the chapter on PKI/SSL Everywhere for more specific recommendations and "
-"server configurations for HTTPS configurations, including the configuration "
-"of HSTS."
-msgstr "HSTS の設定を含め、HTTPS の設定に関するより具体的な推奨事項とサーバー設定は、PKI/SSL の章全体を参照してください。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml72(title)
-msgid "Front end caching"
-msgstr "フロントエンドキャッシュ"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml73(para)
-msgid ""
-"Since dashboard is rendering dynamic content passed directly from OpenStack "
-"API requests, we do not recommend front end caching layers such as varnish. "
-"In Django, static media is directly served from Apache or nginx and already "
-"benefits from web host caching."
-msgstr "ダッシュボードは OpenStack API リクエストから渡された動的コンテンツをそのまま描画するため、varnish のようなフロントエンドキャッシュ層を推奨しません。Django では、静的なメディアは直接 Apache や nginx から処理され、すでに Web ホストのキャッシュの恩恵を受けています。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml80(title)
-msgid "Domain names"
-msgstr "ドメイン名"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml81(para)
-msgid ""
-"Many organizations typically deploy web applications at subdomains of an "
-"overarching organization domain. It is natural for users to expect a domain "
-"of the form <uri>openstack.example.org</uri>. In this context, there are "
-"often many other applications deployed in the same second-level namespace, "
-"often serving user-controlled content. This name structure is convenient and"
-" simplifies name server maintenance."
-msgstr "多くの組織は一般的に、組織全体のドメインのサブドメインに Web アプリケーションを配備します。ユーザーが <uri>openstack.example.org</uri> 形式のドメインを期待することは自然です。これに関連して、しばしば同じセカンドレベルの名前空間に配備された、ユーザーが管理できるコンテンツを取り扱う他の多くのアプリケーションがあります。この名前の構造は便利であり、ネームサーバーのメンテナンスを簡単にします。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml89(para)
-msgid ""
-"We strongly recommend deploying horizon to a <emphasis>second-level "
-"domain</emphasis>, such as <uri>https://example.com</uri>, and advise "
-"against deploying horizon on a <emphasis>shared subdomain</emphasis> of any "
-"level, for example <uri>https://openstack.example.org</uri> or "
-"<uri>https://horizon.openstack.example.org</uri>. We also advise against "
-"deploying to bare internal domains like <uri>https://horizon/</uri>."
-msgstr "Horizon を<emphasis>セカンドレベルドメイン</emphasis>に導入することを強く推奨します。例えば、<uri>https://example.com</uri> です。また、Horizon を<emphasis>共有サブドメイン</emphasis>に導入しないことをお奨めします。例えば、<uri>https://openstack.example.org</uri> や <uri>https://horizon.openstack.example.org</uri> です。<uri>https://horizon/</uri> のようなそのままの内部ドメインに導入しないこともお奨めします。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml97(para)
-msgid ""
-"This recommendation is based on the limitations browser same-origin-policy. "
-"The recommendations in this guide cannot effectively protect users against "
-"known attacks if dashboard is deployed on a domain which also hosts user-"
-"generated content, such as scripts, images, or uploads of any kind, even if "
-"the user-generated content is on a different subdomain. This approach is "
-"used by most major web presences, such as googleusercontent.com, fbcdn.com, "
-"github.io, and twimg.com, to ensure that user generated content stays "
-"separate from cookies and security tokens."
-msgstr "この推奨事項はブラウザーの同一オリジンポリシーの制限に基づいています。このガイドにある推奨事項は、次のような場合によく知られている攻撃からユーザーを効率的に保護できません。ユーザーが生成したコンテンツ (例: スクリプト、イメージ、あらゆる種類のアップロード) もホストしているドメインにダッシュボードを導入した場合です。ユーザーが生成したコンテンツが別のサブドメインにある場合もです。この方法は、ユーザーが生成したコンテンツをクッキーやセキュリティトークンから確実に分離するために、多くの有名な Web サイト (例:  googleusercontent.com、fbcdn.com、github.io、twimg.com) により使用されています。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml107(para)
-msgid ""
-"Additionally, if you decline to follow this recommendation above about "
-"second-level domains, it is vital that you avoid the cookie backed session "
-"store and employ HTTP Strict Transport Security (HSTS). When deployed on a "
-"subdomain, dashboard's security is only as strong as the weakest application"
-" deployed on the same second-level domain."
-msgstr "さらに、セカンドレベルドメインに関する上の推奨事項に従わない場合、クッキーによるバックエンドセッションを避け、HTTP Strict Transport Security (HSTS) を採用することがきわめて重要です。サブドメインに導入するとき、ダッシュボードのセキュリティは同じレベルのドメインに導入されているアプリケーションの中で最も弱いレベルと同じ強度になります。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml115(title)
-msgid "Static media"
-msgstr "静的メディア"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml116(para)
-msgid ""
-"Dashboard's static media should be deployed to a subdomain of the dashboard "
-"domain and served by the web server. The use of an external content delivery"
-" network (CDN) is also acceptable. This subdomain should not set cookies or "
-"serve user-provided content. The media should also be served with HTTPS."
-msgstr "ダッシュボードの静的メディアは、ダッシュボードのドメインのサブドメインに導入し、Web サーバーにより処理されるべきです。外部の CDN (content delivery network) の使用も問題ありません。このサブドメインは、クッキーを設定すべきではなく、ユーザーが提供したコンテンツを処理すべきではありません。メディアも HTTPS で提供されるべきです。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml121(para)
-msgid ""
-"Django media settings are documented at <link "
-"href=\"https://docs.djangoproject.com/en/1.5/ref/settings/#static-"
-"root\">https://docs.djangoproject.com/en/1.5/ref/settings/#static-"
-"root</link>."
-msgstr "Django のメディア設定は <link href=\"https://docs.djangoproject.com/en/1.5/ref/settings/#static-root\">https://docs.djangoproject.com/en/1.5/ref/settings/#static-root</link> にドキュメント化されています。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml124(para)
-msgid ""
-"Dashboard's default configuration uses <link href=\"http://django-"
-"compressor.readthedocs.org/\">django_compressor</link> to compress and "
-"minify css and JavaScript content before serving it. This process should be "
-"statically done before deploying dashboard, rather than using the default "
-"in-request dynamic compression and copying the resulting files along with "
-"deployed code or to the CDN server. Compression should be done in a non-"
-"production build environment. If this is not practical, we recommend "
-"disabling resource compression entirely. Online compression dependencies "
-"(less, nodejs) should not be installed on production machines."
-msgstr "ダッシュボードのデフォルトの設定は、CSS と JavaScript のコンテンツを処理する前に圧縮して最小化するために <link href=\"http://django-compressor.readthedocs.org/\">django_compressor</link> を使用します。このプロセスは、デフォルトのリクエストごとに動的な圧縮を使用する代わりに、ダッシュボードを導入して、導入されたコードと一緒に結果のファイルを CDN サーバーにコピーする前に静的に実行されるべきです。圧縮は本番環境以外で実行すべきです。これが実践的でなければ、すべてのリソースの圧縮を無効化することを推奨します。オンライン圧縮の依存物 (less や nodejs) は本番環境にインストールするべきではありません。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml138(title)
-msgid "Secret key"
-msgstr "シークレットキー"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml139(para)
-msgid ""
-"Dashboard depends on a shared SECRET_KEY setting for some security "
-"functions. It should be a randomly generated string at least 64 characters "
-"long. It must be shared across all active dashboard instances. Compromise of"
-" this key may allow a remote attacker to execute arbitrary code. Rotating "
-"this key invalidates existing user sessions and caching. Do not commit this "
-"key to public repositories."
-msgstr "ダッシュボードはいくつかのセキュリティ機能に関する共有 SECRET_KEY 設定に依存します。これはランダムに生成された最小 64 文字の文字列です。すべてのダッシュボードインスタンスで共有する必要があります。このキーが漏洩すると、リモートの攻撃者が任意のコードを実行できる可能性があります。このキーのローテーションにより、既存のユーザーセッションとキャッシュを無効化します。このキーを公開リポジトリにコミットしないでください。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml148(title)
-msgid "Session back-end"
-msgstr "セッションバックエンド"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml149(para)
-msgid ""
-"Horizon's default session back-end "
-"(<emphasis>django.contrib.sessions.backends.signed_cookies</emphasis>) "
-"stores user data in <emphasis>signed</emphasis> but <emphasis>unencrypted "
-"</emphasis>cookies stored in the browser. This approach allows the most "
-"simple session backend scaling since each dashboard instance is stateless, "
-"but it comes at the cost of <emphasis>storing sensitive access tokens in the"
-" client browser</emphasis> and transmitting them with every request. This "
-"backend ensures that session data has not been tampered with, but the data "
-"itself is not encrypted other than the encryption provided by HTTPS."
-msgstr "Horizon の標準のセッションバックエンド (<emphasis>django.contrib.sessions.backends.signed_cookies</emphasis>) は、ブラウザに保存される、<emphasis>署名付き</emphasis>ですが<emphasis>暗号化されていない</emphasis>クッキーにユーザーデータを保存します。この方法により、各ダッシュボードインスタンスがステートレスになるため、最も簡単なセッションバックエンドがスケールできるようになります。しかし、<emphasis>機微なアクセストークンをクライアントのブラウザーに保存</emphasis>し、それらをリクエストごとに送信するという犠牲を払うことになります。このバックエンドは、セッションデータが改ざんされていないことを保証しますが、データ自身は HTTPS で提供されるような暗号化以外には暗号化されていません。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml160(para)
-msgid ""
-"If your architecture allows it, we recommend using "
-"<emphasis>django.contrib.sessions.backends.cache</emphasis> as your session "
-"backend with memcache as the cache. Memcache must not be exposed publicly, "
-"and should communicate over a secured private channel. If you choose to use "
-"the signed cookies backend, refer to the Django documentation understand the"
-" security trade-offs."
-msgstr "お使いのアーキテクチャが許容できる場合、セッションバックエンドとして <emphasis>django.contrib.sessions.backends.cache</emphasis> を、キャッシュとして memcache を一緒に使用することを推奨します。memcache はパブリックにアクセスされてはいけません。セキュアなプライベートチャネル経由で通信すべきです。署名付きクッキーバックエンドを使用することにした場合、セキュリティのトレードオフを理解するために Django のドキュメントを参照してください。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml167(para)
-msgid ""
-"For further details, consult the <link "
-"href=\"https://docs.djangoproject.com/en/1.5/topics/http/sessions"
-"/#configuring-the-session-engine\">Django session backend "
-"documentation</link>."
-msgstr "さらなる詳細は <link href=\"https://docs.djangoproject.com/en/1.5/topics/http/sessions/#configuring-the-session-engine\">Django session backend documentation</link> を参照してください。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml172(title)
-msgid "Allowed hosts"
-msgstr "許可されたホスト"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml173(para)
-msgid ""
-"Configure the ALLOWED_HOSTS setting with the domain or domains where the "
-"dashboard is available. Failure to configure this setting (especially if not"
-" following the recommendation above regarding second level domains) opens "
-"the dashboard to a number of serious attacks. Wild card domains should be "
-"avoided."
-msgstr "ダッシュボードが利用可能なドメインを ALLOWED_HOSTS に設定します。この設定を失敗すると (とくに第 2 レベルドメインに関する上の推奨に従わなかった場合)、ダッシュボードがさまざまな深刻な攻撃にさらされます。ワイルドカードを使用したドメインは避けるべきです。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml178(para)
-msgid ""
-"For further details, see the <link "
-"href=\"https://docs.djangoproject.com/en/1.5/ref/settings/#allowed-"
-"hosts\">Django documentation on settings</link>."
-msgstr "さらなる詳細は <link href=\"https://docs.djangoproject.com/en/1.5/ref/settings/#allowed-hosts\">Django documentation on settings</link> を参照してください。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml183(title)
-msgid "Cookies"
-msgstr "クッキー"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml184(para)
-msgid "Session Cookies should be set to HTTPONLY:"
-msgstr "セッションクッキーは HTTPONLY に設定すべきです。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml186(para)
-msgid ""
-"Never configure CSRF or session cookies to have a wild card domain with a "
-"leading dot. Horizon's session and CSRF cookie should be secured when "
-"deployed with HTTPS:"
-msgstr "ドットから始まるワイルドカードドメインを持つよう、CSRF やセッションクッキーを設定してはいけません。Horizon のセッションクッキーと CSRF クッキーは HTTPS を使用した環境のときにセキュア化すべきです。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml193(title)
-msgid "Password auto complete"
-msgstr "パスワード自動補完"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml194(para)
-msgid ""
-"We recommend that implementers do not change the default password auto "
-"complete behavior. Users choose stronger passwords in environments that "
-"allow them to use the secure browser password manager. Organizations which "
-"forbid the browser password manager should enforce this policy at the "
-"desktop level."
-msgstr "実装者は標準のパスワードオートコンプリート機能を変更しないことを推奨します。ユーザーはセキュアなブラウザのパスワードマネージャーを使用できる環境で、より強力なパスワードを選択します。ブラウザのパスワードマネージャーを禁止している組織は、デスクトップレベルでこのポリシーを強制すべきです。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml202(title)
-msgid "Cross Site Request Forgery (CSRF)"
-msgstr "クロスサイトリクエストフォージェリ (CSRF)"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml203(para)
-msgid ""
-"Django has a dedicated middleware for <link "
-"href=\"https://docs.djangoproject.com/en/1.5/ref/contrib/csrf/#how-it-works"
-"\">cross-site request forgery</link> (CSRF)."
-msgstr "Django は<link href=\"https://docs.djangoproject.com/en/1.5/ref/contrib/csrf/#how-it-works\">cross-site request forgery</link> (CSRF) 用の専用ミドルウェアを持ちます。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml206(para)
-msgid ""
-"Dashboard is designed to discourage developers from introducing cross-site "
-"scripting vulnerabilities with custom dashboards. However, it is important "
-"to audit custom dashboards, especially ones that are javascript-heavy for "
-"inappropriate use of the @csrf_exempt decorator. Dashboards which do not "
-"follow these recommended security settings should be carefully evaluated "
-"before restrictions are relaxed."
-msgstr "ダッシュボードは、カスタマイズしたダッシュボードでクロスサイトスクリプティングの脆弱性が含まれることから、開発者を守るよう設計されています。しかしながら、カスタマイズしたダッシュボード、とくに、@csrf_exempt デコレーターを不適切に使用して javascript を多用しているものを監査することは重要です。これらのセキュリティ設定の推奨事項に従わないダッシュボードは、制限を緩和する前に注意深く評価されるべきです。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml215(title)
-msgid "Cross Site Scripting (XSS)"
-msgstr "クロスサイトスクリプティング (XSS)"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml216(para)
-msgid ""
-"Unlike many similar systems, OpenStack dashboard allows the entire Unicode "
-"character set in most fields. This means developers have less latitude to "
-"make escaping mistakes that open attack vectors for cross-site scripting "
-"(XSS)."
-msgstr "多くの似たようなシステムと異なり、OpenStack のダッシュボードは多くの項目にすべての Unicode 文字を許可します。このことは、開発者が XSS 攻撃の余地を残すエスケープミスをする範囲が少なくなることを意味します。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml220(para)
-msgid ""
-"Dashboard provides tools for developers to avoid creating XSS "
-"vulnerabilities, but they only work if developers use them correctly. Audit "
-"any custom dashboards, paying particular attention to use of the mark_safe "
-"function, use of is_safe with custom template tags, the safe template tag, "
-"anywhere auto escape is turned off, and any JavaScript which might evaluate "
-"improperly escaped data."
-msgstr "ダッシュボードは開発者が XSS 脆弱性を作ることを防ぐためのツールを提供します。しかし、それらは開発者が適切に使用するときのみ機能します。mark_safe 関数の使用、カスタムテンプレートタグを持つ  is_safe の使用、safe テンプレートタグ、自動エスケープが無効化されているすべての場所、不適切にエスケープされたデータを評価するすべての javaScript にとくに注意して、すべてのカスタムダッシュボードを監視します。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml229(title)
-msgid "Cross Origin Resource Sharing (CORS)"
-msgstr "クロスオリジンリソースシェアリング (CORS)"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml230(para)
-msgid ""
-"Configure your web server to send a restrictive CORS header with each "
-"response, allowing only the dashboard domain and protocol:"
-msgstr "ウェブブラウザが各レスポンスに限定的な CORS ヘッダーを付けて送信するよう設定します。ダッシュボードのドメインとプロトコルのみを許可します。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml234(para)
-msgid "Never allow the wild card origin."
-msgstr "ワイルドカードオリジンを許可してはいけません。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml237(title)
-msgid "Horizon image upload"
-msgstr "Horizon のイメージのアップロード"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml238(para)
-msgid ""
-"We recommend that implementers <link "
-"href=\"http://docs.openstack.org/developer/horizon/topics/deployment.html"
-"#file-uploads\">disable HORIZON_IMAGES_ALLOW_UPLOAD</link> unless they have "
-"implemented a plan to prevent resource exhaustion and denial of service."
-msgstr "導入者はリソース枯渇とサービス妨害を防ぐ計画を実装していなければ、<link href=\"http://docs.openstack.org/developer/horizon/topics/deployment.html#file-uploads\">HORIZON_IMAGES_ALLOW_UPLOAD を無効化</link> することを強く推奨します。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml245(title)
-msgid "Upgrading"
-msgstr "アップグレード"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml246(para)
-msgid ""
-"Django security releases are generally well tested and aggressively "
-"backwards compatible. In almost all cases, new major releases of Django are "
-"also fully backwards compatible with previous releases. Dashboard "
-"implementers are strongly encouraged to run the latest stable release of "
-"Django with up-to-date security releases."
-msgstr "Django セキュリティリリースは、一般的に十分にテストされ、積極的に後方互換性を確保しています。ほぼすべての場合、Django の新しいメジャーリリースも前のリリースと後方互換性があります。ダッシュボードの実装者は、最新のセキュリティリリースを持つ最新の安定リリースの Django を実行することを強く推奨されます。"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml254(title)
-msgid "Debug"
-msgstr "デバッグ"
-
-#: ./doc/security-guide/ch025_web-dashboard.xml255(para)
-msgid ""
-"Make sure DEBUG is set to False in production. In Django, DEBUG displays "
-"stack traces and sensitive web server state information on any exception."
-msgstr "本番環境で DEBUG が False に設定されていることを確認します。Django では DEBUG により、あらゆる例外の発生時にスタックトレースとセキュリティ上問題のある Web サーバーの状態情報が表示されます。"
-
-#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml8(title)
-msgid "Case studies: API endpoints"
-msgstr "ケーススタディ: API エンドポイント"
-
-#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml9(para)
-msgid ""
-"In this case study we discuss how Alice and Bob would address endpoint "
-"configuration to secure their private and public clouds. Alice's cloud is "
-"not publicly accessible, but she is still concerned about securing the "
-"endpoints against improper use. Bob's cloud, being public, must take "
-"measures to reduce the risk of attacks by external adversaries."
-msgstr "このケーススタディでは、アリスとボブがどうやってプライベートクラウドとパブリッククラウドのエンドポイント設定を堅牢化するかについて議論します。\nアリスのプライベートクラウドは公開されたものではありませんが、不適切な使い方からエンドポイントを守る方法について憂慮しています。ボブのパブリッククラウドは、外部からの攻撃に対してリスクを低減する措置を講じなければいけません。"
-
-#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml12(para)
-msgid ""
-"Alice's organization requires that the security architecture protect the "
-"access to the public and private endpoints, so she elects to use the Apache "
-"SSL proxy on both public and internal services. Alice's organization has "
-"implemented its own certificate authority. Alice contacts the PKI office in "
-"her agency that manages her PKI and certificate issuance. Alice obtains "
-"certificates issued by this CA and configures the services within both the "
-"public and management security domains to use these certificates. Since "
-"Alice's OpenStack deployment exists entirely on a disconnected from the "
-"Internet network, she makes sure to remove all default CA bundles that "
-"contain external public CA providers to ensure the OpenStack services only "
-"accept client certificates issued by her agency's CA. Alice has registered "
-"all of the services in the Identity service's catalog, using the internal "
-"URLs for access by internal services. She has installed host-based intrusion"
-" detection on all of the API endpoints."
-msgstr "アリスは所属する組織から、パブリックとプライベートのエンドポイントへのアクセスに対してセキュリティ対策を講じるように命じられました。そこで彼女は、パブリックとプライベートのサービスに対して Apache SSL Proxy を構築しました。アリスの組織では、自前の認証局を用意しています。アリスは、彼女の PKI と証明書発行を管理する PKI 担当部門に連絡します。アリスはこのCAによって発行された証明書を入手し、これらの証明書を使用するようパブリックと管理セキュリティドメインの両方のサービスを設定します。アリスの OpenStack デプロイが完全にインターネットから独立して存在するので、OpenStack サービスが彼女の組織の CA から発行されたクライアント証明書のみ許可するよう、外部のパブリックな CA プロバイダを含むデフォルトの全 CA バンドルが削除されている事を確認しています。アリスは、内部サービスのアクセス用の内部 URL を利用して、Identity のサービスカタログに全サービスを登録しました。彼女は、すべての API エンドポイントにホストベース IDS をインストールしました。"
-
-#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml34(para)
-msgid ""
-"Bob must also protect the access to the public and private endpoints, so he "
-"elects to use the Apache SSL proxy on both public and internal services. On "
-"the public services, he has configured the certificate key files with "
-"certificates signed by a well-known Certificate Authority. He has used his "
-"organization's self-signed CA to sign certificates in the internal services "
-"on the Management network. Bob has registered his services in the Identity "
-"service's catalog, using the internal URLs for access by internal services. "
-"Bob's public cloud runs services on SELinux, which he has configured with a "
-"mandatory access control policy to reduce the impact of any publicly "
-"accessible services that may be compromised. He has also configured the "
-"endpoints with a host-based IDS."
-msgstr "ボブもまた、パブリックとプライベートエンドポイントを守るひつようがあるため、 Apache SSL proxy をパブリックサービスと内部サービスの両方に構築しました。\nパブリックサービス側には、よく知られている認証局が署名した証明書キーファイルを、内部サービス側には、自己署名証明書を管理ネットワーク上のサービスに設定しました。\n内部アクセス用の Internal URL 越しに、サービスを Identity のサービスカタログに登録し、また、ホストベースの侵入検知システムを全 API エンドポイントに設定しました。"
-
-#: ./doc/security-guide/ch046_data-residency.xml8(title)
-msgid "Data privacy concerns"
-msgstr "データプライバシ関連"
-
-#: ./doc/security-guide/ch046_data-residency.xml9(para)
-msgid ""
-"OpenStack is designed to support multitenancy and those tenants will most "
-"probably have different data requirements. As a cloud builder and operator "
-"you need to ensure your OpenStack environment can address various data "
-"privacy concerns and regulations. In this chapter we will address the "
-"following topics around Data Privacy as it pertains to OpenStack "
-"implementations:"
-msgstr "OpenStack はマルチテナンシーをサポートするよう設計されており、これらのテナントには、まず間違いなく異なるデータ要件があるでしょう。クラウド構築者とオペレータとして、あなたは自身の OpenStack 環境が様々なデータプライバシー関連と規制を扱える事を確認する必要があります。OpenStack 実装に関連するので、本章ではデータプライバシーにまつわる以下のトピックを扱います。"
-
-#: ./doc/security-guide/ch046_data-residency.xml19(para)
-#: ./doc/security-guide/ch046_data-residency.xml26(title)
-msgid "Data residency"
-msgstr "データの所在"
-
-#: ./doc/security-guide/ch046_data-residency.xml22(para)
-#: ./doc/security-guide/ch046_data-residency.xml77(title)
-msgid "Data disposal"
-msgstr "データの処分"
-
-#: ./doc/security-guide/ch046_data-residency.xml27(para)
-msgid ""
-"The privacy and isolation of data has consistently been cited as the primary"
-" barrier to cloud adoption over the past few years. Concerns over who owns "
-"data in the cloud and whether the cloud operator can be ultimately trusted "
-"as a custodian of this data have been significant issues in the past."
-msgstr "データのプライバシーと分割は、ここ数年クラウド採用の最初の障壁としてずっと言及されてきました。クラウド中でデータを所有するのは誰か、このデータの管理人としてクラウドオペレータは結局信用できるのか否かという事は、これまで重要な問題でした。"
-
-#: ./doc/security-guide/ch046_data-residency.xml28(para)
-msgid ""
-"Numerous OpenStack services maintain data and metadata belonging to tenants "
-"or reference tenant information."
-msgstr "多数の OpenStack サービス群は、テナントやテナント情報の所在に属するデータとメタデータを管理します。"
-
-#: ./doc/security-guide/ch046_data-residency.xml29(para)
-msgid ""
-"Tenant data stored in an OpenStack cloud may include the following items:"
-msgstr "OpenStack クラウドに保存されたテナントデータは以下の項目を含まれます："
-
-#: ./doc/security-guide/ch046_data-residency.xml31(para)
-#: ./doc/security-guide/ch047_data-encryption.xml15(para)
-#: ./doc/security-guide/ch047_data-encryption.xml25(title)
-msgid "Object Storage objects"
-msgstr "Object Storage オブジェクト"
-
-#: ./doc/security-guide/ch046_data-residency.xml34(para)
-msgid "Compute instance ephemeral filesystem storage"
-msgstr "Compute のインスタンスの一時的ファイルシステムストレージ"
-
-#: ./doc/security-guide/ch046_data-residency.xml37(para)
-msgid "Compute instance memory"
-msgstr "Compute インスタンスのメモリ"
-
-#: ./doc/security-guide/ch046_data-residency.xml40(para)
-#: ./doc/security-guide/ch046_data-residency.xml105(para)
-msgid "Block Storage volume data"
-msgstr "ブロックストレージボリュームデータ"
-
-#: ./doc/security-guide/ch046_data-residency.xml43(para)
-msgid "Public keys for Compute Access"
-msgstr "Comptue アクセス用パブリックキー"
-
-#: ./doc/security-guide/ch046_data-residency.xml46(para)
-msgid "Virtual Machine Images in the Image Service"
-msgstr "Image Service 中の仮想マシンイメージ"
-
-#: ./doc/security-guide/ch046_data-residency.xml49(para)
-msgid "Machine snapshots"
-msgstr "マシンのスナップショット"
-
-#: ./doc/security-guide/ch046_data-residency.xml52(para)
-msgid "Data passed to OpenStack Compute's configuration-drive extension"
-msgstr "OpenStack Compute の設定用ドライブ拡張に渡されたデータ"
-
-#: ./doc/security-guide/ch046_data-residency.xml55(para)
-msgid ""
-"Metadata stored by an OpenStack cloud includes the following non-exhaustive "
-"items:"
-msgstr "以下の不完全な一覧を含む、OpenStack クラウドが保存したメタデータ:"
-
-#: ./doc/security-guide/ch046_data-residency.xml57(para)
-msgid "Organization name"
-msgstr "組織名"
-
-#: ./doc/security-guide/ch046_data-residency.xml60(para)
-msgid "User's \"Real Name\""
-msgstr "ユーザの「実名」"
-
-#: ./doc/security-guide/ch046_data-residency.xml63(para)
-msgid ""
-"Number or size of running instances, buckets, objects, volumes, and other "
-"quota-related items"
-msgstr "実行中のインスタンスのサイズ、バケット、オブジェクト、ボリューム、その他クォータ関連の項目"
-
-#: ./doc/security-guide/ch046_data-residency.xml66(para)
-msgid "Number of hours running instances or storing data"
-msgstr "実行中のインスタンス又は保存されたデータの経過時間"
-
-#: ./doc/security-guide/ch046_data-residency.xml69(para)
-msgid "IP addresses of users"
-msgstr "ユーザの IP アドレス"
-
-#: ./doc/security-guide/ch046_data-residency.xml72(para)
-msgid "Internally generated private keys for compute image bundling"
-msgstr "Compute イメージ作成用に内部で生成されたプライベートキー"
-
-#: ./doc/security-guide/ch046_data-residency.xml78(para)
-msgid ""
-"OpenStack operators should strive to provide a certain level of tenant data "
-"disposal assurance. Best practices suggest that the operator sanitize cloud "
-"system media (digital and non-digital) prior to disposal, release out of "
-"organization control or release for reuse. Sanitization methods should "
-"implement an appropriate level of strength and integrity given the specific "
-"security domain and sensitivity of the information."
-msgstr "OpenStack オペレータは、ある一定レベルのテナントデータ破棄保証が提供できるよう努力しなければんりません。ベストプラクティスは、クラウドシステムメディア (デジタル・非デジタル) を破棄、組織コントロール外へのリリース、再利用の為の開放より前にオペレータがメディアをクリアする事を推奨しています。メディアのクリア方法は、特定のセキュリティドメインと情報のデリケートさが与えられた、適切なレベルの強度と完全性を実装すべきです。"
-
-#: ./doc/security-guide/ch046_data-residency.xml80(para)
-msgid ""
-"\"Sanitization is the process used to remove information from system media "
-"such that there is reasonable assurance that the information cannot be "
-"retrieved or reconstructed. Sanitization techniques, including clearing, "
-"purging, and destroying media information, prevent the disclosure of "
-"organizational information to unauthorized individuals when such media is "
-"reused or released for disposal.\" [NIST Special Publication 800-53 Revision"
-" 3]"
-msgstr "「データのサニタイズは、情報が取得あるいは再構築できない事の合理的な保証が得られるよう、システム媒体から情報を削除する為に使用されるプロセスです。サニタイズ技術（媒体の情報のクリア、破棄、破壊を含む）は、こうした媒体が再利用・譲渡・破棄された際に、組織の情報が閲覧権限のない個人に開示される事を防ぎます。」 [NIST Special Publication 800-53 Revision 3]"
-
-#: ./doc/security-guide/ch046_data-residency.xml82(para)
-msgid ""
-"General data disposal and sanitization guidelines as adopted from NIST "
-"recommended security controls. Cloud operators should:"
-msgstr "NIST が採用した汎用のデータ破棄とサニタイズのガイドラインは、セキュリティ制御を推奨しています。クラウドオペレータは以下のことをすべきです。"
-
-#: ./doc/security-guide/ch046_data-residency.xml84(para)
-msgid "Track, document and verify media sanitization and disposal actions."
-msgstr "媒体サニタイズと破棄行為の追跡・文書化・検証を行うこと。"
-
-#: ./doc/security-guide/ch046_data-residency.xml87(para)
-msgid "Test sanitation equipment and procedures to verify proper performance."
-msgstr "適切なパフォーマンスを検証する為、サニタイズ設備と過程の評価を行うこと。"
-
-#: ./doc/security-guide/ch046_data-residency.xml91(para)
-msgid ""
-"Sanitize portable, removable storage devices prior to connecting such "
-"devices to the cloud infrastructure."
-msgstr "持ち運び可能なリムーバルストレージデバイスをクラウドインフラに接続する前にサニタイズすること。"
-
-#: ./doc/security-guide/ch046_data-residency.xml94(para)
-msgid "Destroy cloud system media that cannot be sanitized."
-msgstr "サニタイズできないクラウドシステム媒体を破壊すること。"
-
-#: ./doc/security-guide/ch046_data-residency.xml97(para)
-msgid "In an OpenStack deployment you will need to address the following:"
-msgstr "OpenStack デプロイでは、以下の事も実施する必要があるでしょう。"
-
-#: ./doc/security-guide/ch046_data-residency.xml99(para)
-msgid "Secure data erasure"
-msgstr "安全なデータの消去"
-
-#: ./doc/security-guide/ch046_data-residency.xml102(para)
-#: ./doc/security-guide/ch046_data-residency.xml119(title)
-msgid "Instance memory scrubbing"
-msgstr "インスタンスメモリの消去"
-
-#: ./doc/security-guide/ch046_data-residency.xml108(para)
-#: ./doc/security-guide/ch046_data-residency.xml132(title)
-msgid "Compute instance ephemeral storage"
-msgstr "Compute インスタンスの一時ストレージ"
-
-#: ./doc/security-guide/ch046_data-residency.xml111(para)
-#: ./doc/security-guide/ch046_data-residency.xml139(title)
-msgid "Bare metal server sanitization"
-msgstr "物理サーバのサニタイズ"
-
-#: ./doc/security-guide/ch046_data-residency.xml115(title)
-msgid "Data not securely erased"
-msgstr "安全に消去されなかったデータ"
-
-#: ./doc/security-guide/ch046_data-residency.xml116(para)
-msgid ""
-"Within OpenStack some data may be deleted, but not securely erased in the "
-"context of the NIST standards outlined above. This is generally applicable "
-"to most or all of the above-defined metadata and information stored in the "
-"database. This may be remediated with database and/or system configuration "
-"for auto vacuuming and periodic free-space wiping."
-msgstr "OpenStack 中でいくつかのデータは削除されるかも知れませんが、上記で触れた NIST 標準の文脈における安全な消去ではありません。これは一般に、データベースに保存された上記で定義したメタデータと情報の大半又は全てに当てはまります。これは、データベースとシステム設定のどちらか又は両方で、自動バキュームと定期的な空き領域のクリアを実施する事で解決する事ができるかも知れません。"
-
-#: ./doc/security-guide/ch046_data-residency.xml120(para)
-msgid ""
-"Specific to various hypervisors is the treatment of instance memory. This "
-"behavior is not defined in OpenStack Compute, although it is generally "
-"expected of hypervisors that they will make a best effort to scrub memory "
-"either upon deletion of an instance, upon creation of an instance, or both."
-msgstr "様々なハイパーバイザの特色はインスタンスメモリの扱いにあります。\n\nThis behavior is not defined in OpenStack Compute, although it is generally expected of hypervisors that they will make a best effort to scrub memory either upon deletion of an instance, upon creation of an instance, or both.\n\nこの挙動は OpenStack Compute で定義されておらず、ハイパーバイザがインスタンス作成時または削除時、あるいはその両方において、ベストエフォートでメモリのクリンアップを行うだろうと一般に考えられています。"
-
-#: ./doc/security-guide/ch046_data-residency.xml121(para)
-msgid ""
-"Xen explicitly assigns dedicated memory regions to instances and scrubs data"
-" upon the destruction of instances (or domains in Xen parlance). KVM depends"
-" more greatly on Linux page management; A complex set of rules related to "
-"KVM paging is defined in the <link href=\"http://www.linux-"
-"kvm.org/page/Memory\">KVM documentation</link>."
-msgstr "Xen は、専用のメモリ範囲をインスタンスに明確に割り当て、インスタンス (又は Xen の用語でドメイン) 破棄時にそのデータをクリンアップします。KVM はより大いに Linux のページ管理に依存しています。 KVM のページングに関する複雑なルールセットは、<link href=\"http://www.linux-kvm.org/page/Memory\">KVM の文書</link>で定義されています。"
-
-#: ./doc/security-guide/ch046_data-residency.xml122(para)
-msgid ""
-"It is important to note that use of the Xen memory balloon feature is likely"
-" to result in information disclosure. We strongly recommended to avoid use "
-"of this feature."
-msgstr "Xen のメモリバルーン機能の使用は情報漏えいの結果になりかねないという事への注意は重要です。"
-
-#: ./doc/security-guide/ch046_data-residency.xml123(para)
-msgid ""
-"For these and other hypervisors, we recommend referring to hypervisor-"
-"specific documentation."
-msgstr "これらや他のハイパーバイザでは、ハイパーバイザ毎のドキュメントを参照すると良いでしょう。"
-
-#: ./doc/security-guide/ch046_data-residency.xml126(title)
-msgid "Cinder volume data"
-msgstr "Cinder のボリュームデータ"
-
-#: ./doc/security-guide/ch046_data-residency.xml127(para)
-msgid ""
-"Plugins to OpenStack Block Storage will store data in a variety of ways. "
-"Many plug-ins are specific to a vendor or technology, whereas others are "
-"more DIY solutions around filesystems such as LVM or ZFS. Methods to "
-"securely destroy data will vary from one plugin to another, from one "
-"vendor's solution to another, and from one filesystem to another."
-msgstr "OpenStack Block Storage のプラグインは様々な方法でデータの保存を行います。多くのプラグインはベンダー又はストレージ技術に特化していますが、その他は LVM や ZFS といったファイルシステム辺りのより手作りのソリューションです。安全にデータを破壊する方法はプラグイン毎、ベンダーのソリューション毎、ファイルシステム毎に異なるでしょう。"
-
-#: ./doc/security-guide/ch046_data-residency.xml128(para)
-msgid ""
-"Some backends such as ZFS will support copy-on-write to prevent data "
-"exposure. In these cases, reads from unwritten blocks will always return "
-"zero. Other backends such as LVM may not natively support this, thus the "
-"Block Storage plug-in takes the responsibility to override previously "
-"written blocks before handing them to users. It is important to review what "
-"assurances your chosen volume backend provides and to see what mediations "
-"may be available for those assurances not provided."
-msgstr "ZFS のようないくつかのバックエンドは、データの漏洩を防ぐために copy-on-write に対応しています。この場合、まだ書き込まれていないブロックからの読み込みは常にゼロを返します。LVM のような他のバックエンドでは copy-on-write を標準でサポートしておらず、よって Block Storage プラグインが以前に書き込まれたブロックをユーザがアクセスする前に上書きする役割を担います。あなたが選択したボリュームバックエンドが提供する機能をレビューし、これらの機能が提供しない事についての回避策が利用できるかを調べる事は重要です。"
-
-#: ./doc/security-guide/ch046_data-residency.xml129(para)
-msgid ""
-"Finally, while not a feature of OpenStack, vendors and implementors may "
-"choose to add or support encryption of volumes. In this case, destruction of"
-" data is as simple as throwing away the key."
-msgstr "最後に、これは OpenStack の機能ではありませんが、ベンダーと開発者がボリュームの暗号化機能をサポートするか、あるいは追加可能であるかも知れません。この場合、データの破壊は単にキーを破棄するだけです。"
-
-#: ./doc/security-guide/ch046_data-residency.xml133(para)
-msgid ""
-"The creation and destruction of ephemeral storage will be somewhat dependent"
-" on the chosen hypervisor and the OpenStack Compute plug-in."
-msgstr "一時ストレージの作成・削除は選択したハイパーバイザや OpenStack Compute プラグインに依存するでしょう。"
-
-#: ./doc/security-guide/ch046_data-residency.xml134(para)
-msgid ""
-"The libvirt plug-in for compute may maintain ephemeral storage directly on a"
-" filesystem, or in LVM. Filesystem storage generally will not overwrite data"
-" when it is removed, although there is a guarantee that dirty extents are "
-"not provisioned to users."
-msgstr "compute 用の libvirt プラグインは、ファイルシステム又は LVM 上の一時ストレージを直接管理出来ます。ファイルシステムストレージは一般にデータを削除する際に上書きはしませんが、ユーザに対して汚れたエクステンドが用意されないという保証があります。"
-
-#: ./doc/security-guide/ch046_data-residency.xml135(para)
-msgid ""
-"When using LVM backed ephemeral storage, which is block-based, it is "
-"necessary that the OpenStack Compute software securely erases blocks to "
-"prevent information disclosure. There have in the past been information "
-"disclosure vulnerabilities related to improperly erased ephemeral block "
-"storage devices."
-msgstr "ブロックデバイスベースである LVM をバックエンドにした一時ストレージを使用する場合、OpenStack Compute は情報漏えいを防ぐために、安全にブロックを削除する必要があります。これらには、過去において、不適切な一時ブロックストレージデバイスの削除に関連する情報漏洩の脆弱性がありました。"
-
-#: ./doc/security-guide/ch046_data-residency.xml136(para)
-msgid ""
-"Filesystem storage is a more secure solution for ephemeral block storage "
-"devices than LVM as dirty extents cannot be provisioned to users. However, "
-"it is important to be mindful that user data is not destroyed, so it is "
-"suggested to encrypt the backing filesystem."
-msgstr "データが含まれたエクステンドがユーザに用意されないので、一時ブロックストレージデバイス用としてファイルシステムストレージは LVM より安全なソリューションです。しかしながら、ユーザデータが破壊されない事を覚えておく事は重要であり、このためバックエンドのファイルシステムの暗号化が提案されています。"
-
-#: ./doc/security-guide/ch046_data-residency.xml140(para)
-msgid ""
-"A bare metal server driver for Compute was under development and has since "
-"moved into a separate project called <link "
-"href=\"https://wiki.openstack.org/wiki/Ironic\">ironic</link>. At the time "
-"of this writing, ironic does not appear to address sanitization of tenant "
-"data resident the physical hardware."
-msgstr "Compute の物理サーバドライバは開発中だったのですが、<link href=\"https://wiki.openstack.org/wiki/Ironic\">ironic</link>と呼ばれる独立したプロジェクトに移管される事になりました。この文書の執筆時点では、ironic には物理ハードウェア上にあるテナントデータのサニタイズ機能はまだありません。"
-
-#: ./doc/security-guide/ch046_data-residency.xml147(para)
-msgid ""
-"Additionally, it is possible for tenants of a bare metal system to modify "
-"system firmware. TPM technology, described in <xref linkend=\"ch013_node-"
-"bootstrapping-idp44768\"/>, provides a solution for detecting unauthorized "
-"firmware changes."
-msgstr "加えて、物理マシンのテナントでは、システムファームウェアの修正が可能です。<xref linkend=\"ch013_node-bootstrapping-idp44768\"/>で説明されている TPM 技術は、許可されていないファームウェアの変更を検知する解決策を提供します。"
-
-#: ./doc/security-guide/ch062_audit-guidance.xml8(title)
-msgid "Understanding the audit process"
-msgstr "監査プロセスを理解する"
-
-#: ./doc/security-guide/ch062_audit-guidance.xml9(para)
-msgid ""
-"Information system security compliance is reliant on the completion of two "
-"foundational processes:"
-msgstr "情報システムのセキュリティコンプライアンスは、二つの基本的なプロセスの完了を前提としています。"
-
-#: ./doc/security-guide/ch062_audit-guidance.xml13(para)
-msgid ""
-"<emphasis role=\"bold\">Implementation and operation of security "
-"controls.</emphasis> Aligning the information system with in-scope standards"
-" and regulations involves internal tasks which must be conducted before a "
-"formal assessment. Auditors may be involved at this state to conduct gap "
-"analysis, provide guidance, and increase the likelihood of successful "
-"certification."
-msgstr "<emphasis role=\"bold\">セキュリティコントロールの実装と運用。</emphasis>情報システムを標準と規制の範囲内で運用しつづけること、それは、正式なアセスメント前でも行うべき内部タスクです。なお監査人はこの時点で、ギャップ分析、助言、認証取得の可能性向上のために関与することがあります。"
-
-#: ./doc/security-guide/ch062_audit-guidance.xml23(para)
-msgid ""
-"<emphasis role=\"bold\">Independent verification and validation.</emphasis> "
-"Demonstration to a neutral third-party that system security controls are "
-"implemented and operating effectively, in compliance with in-scope standards"
-" and regulations, is required before many information systems achieve "
-"certified status. Many certifications require periodic audits to ensure "
-"continued certification, considered part of an overarching continuous "
-"monitoring practice."
-msgstr "<emphasis role=\"bold\">独立した検査と検証。</emphasis>システムのセキュリティコントロールが標準と規制の範囲に従って実装され、効率的に運用されているか。これを中立的な第三者へ、認証を得る以前に証明しなければなりません。多くの認証は、その継続を保証するため、包括的な継続監視の一部として、定期的な監査を必要とします。"
-
-#: ./doc/security-guide/ch062_audit-guidance.xml36(title)
-msgid "Determining audit scope"
-msgstr "監査の範囲を決定する"
-
-#: ./doc/security-guide/ch062_audit-guidance.xml37(para)
-msgid ""
-"Determining audit scope, specifically what controls are needed and how to "
-"design or modify an OpenStack deployment to satisfy them, should be the "
-"initial planning step."
-msgstr "何をコントロールするのか、OpenStack環境をいかにデザイン、変更していくかを明確にするため、監査範囲は初期の計画段階で決定すべきです。"
-
-#: ./doc/security-guide/ch062_audit-guidance.xml38(para)
-msgid ""
-"When scoping OpenStack deployments for compliance purposes, consider "
-"prioritizing controls around sensitive services, such as command and control"
-" functions and the base virtualization technology. Compromises of these "
-"facilities may impact an OpenStack environment in its entirety."
-msgstr "OpenStack環境の範囲をコンプライアンス目的で明確化する際は、制御機能や仮想化技術など、慎重に扱うべきサービスの周辺を優先するよう、考慮すべきです。それらを妥協することは、OpenStack環境全体に影響を与えかねません。"
-
-#: ./doc/security-guide/ch062_audit-guidance.xml39(para)
-msgid ""
-"Scope reduction helps ensure OpenStack architects establish high quality "
-"security controls which are tailored to a particular deployment, however it "
-"is paramount to ensure these practices do not omit areas or features from "
-"security hardening. A common example is applicable to PCI-DSS guidelines, "
-"where payment related infrastructure may be scrutinized for security issues,"
-" but supporting services are left ignored, and vulnerable to attack."
-msgstr "範囲を限定することで、限定された環境に対し、OpenStackの設計者は高いセキュリティ品質を確立しやすくなります。しかしその取り組みの中で、セキュリティ強化の範囲や機能を不当に省かないことが重要です。典型的な例はPCI-DSSガイドラインです。決済に関わるインフラはセキュリティを精査されるでしょう。が、その影でその周辺サービスが放置されれば、そこが攻撃に対し無防備となります。"
-
-#: ./doc/security-guide/ch062_audit-guidance.xml40(para)
-msgid ""
-"When addressing compliance, you can increase efficiency and reduce work "
-"effort by identifying common areas and criteria that apply across multiple "
-"certifications. Much of the audit principles and guidelines discussed in "
-"this book will assist in identifying these controls, additionally a number "
-"of external entities provide comprehensive lists. The following are some "
-"examples:"
-msgstr "コンプライアンスに取り組む際、複数の認証で共通の領域と基準を明確にできれば、効率的に手間を減らすことができます。この本で取り上げている監査原則とガイドラインの多くは、それらを特定するのに役立ちます。加えて、総合的なリストを提供するガイドラインが多くあります。以下に例を挙げます。"
-
-#: ./doc/security-guide/ch062_audit-guidance.xml41(para)
-msgid ""
-"The <link href=\"https://cloudsecurityalliance.org/research/ccm/\">Cloud "
-"Security Alliance Cloud Controls Matrix</link> (CCM) assists both cloud "
-"providers and consumers in assessing the overall security of a cloud "
-"provider. The CSA CMM provides a controls framework that map to many "
-"industry-accepted standards and regulations including the ISO 27001/2, "
-"ISACA, COBIT, PCI, NIST, Jericho Forum and NERC CIP."
-msgstr "<link href=\"https://cloudsecurityalliance.org/research/ccm/\">Cloud Security Alliance Cloud Controls Matrix</link> (CCM)はクラウドプロバイダーのセキュリティを総合的に評価するにあたって、プロバイダーとユーザーの両方に役立ちます。CSA CCMはISO 27001/2、ISACA、COBIT、PIC、NIST、Jericho Forum、NERC CIPといった、多くの業界で認められた標準、規制をひも付けた統制フレームワークを提供します。"
-
-#: ./doc/security-guide/ch062_audit-guidance.xml42(para)
-msgid ""
-"The <link href=\"https://fedorahosted.org/scap-security-guide/\">SCAP "
-"Security Guide</link> is another useful reference. This is still an emerging"
-" source, but we anticipate that this will grow into a tool with controls "
-"mappings that are more focused on the US federal government certifications "
-"and recommendations. For example, the SCAP Security Guide currently has some"
-" mappings for security technical implementation guides (STIGs) and "
-"NIST-800-53."
-msgstr "<link href=\"https://fedorahosted.org/scap-security-guide/\">SCAP Security Guide</link>はもうひとつの有用なリファレンスです。まだ出来たばかりですが、米国連邦政府の認証、推奨への対応に重点を絞ったツールとして普及すると予想されます。例えば、SCAP Security Guideは現在、security technical implementation guides (STIGs)とNIST-800-53にある程度対応しています。"
-
-#: ./doc/security-guide/ch062_audit-guidance.xml43(para)
-msgid ""
-"These control mappings will help identify common control criteria across "
-"certifications, and provide visibility to both auditors and auditees on "
-"problem areas within control sets for particular compliance certifications "
-"and attestations."
-msgstr "これらのコントロールマッピングは、認証間で共通の統制基準を特定します。また、監査人と被監査者両方にとって問題となる、特定のコンプライアンス認証、認定に必要なコントロールセットを可視化するのに役立ちます。"
-
-#: ./doc/security-guide/ch062_audit-guidance.xml46(title)
-msgid "Internal audit"
-msgstr "内部監査"
-
-#: ./doc/security-guide/ch062_audit-guidance.xml47(para)
-msgid ""
-"Once a cloud is deployed, it is time for an internal audit. This is the time"
-" compare the controls you identified above with the design, features, and "
-"deployment strategies utilized in your cloud. The goal is to understand how "
-"each control is handled and where gaps exist. Document all of the findings "
-"for future reference."
-msgstr "クラウドが導入されたのであれば、内部監査が必要です。あなたが採用を決めた統制基準と、あなたのクラウドの設計、機能、配備戦略を比較する時です。目的はそれぞれの統制がどのように扱われているか、ギャップがどこに存在するか、理解することです。そして、その全てを将来のために文書化します。"
-
-#: ./doc/security-guide/ch062_audit-guidance.xml48(para)
-msgid ""
-"When auditing an OpenStack cloud it is important to appreciate the multi-"
-"tenant environment inherent in the OpenStack architecture. Some critical "
-"areas for concern include data disposal, hypervisor security, node "
-"hardening, and authentication mechanisms."
-msgstr "OpenStackクラウドを監査するとき、OpenStackアーキテクチャ固有のマルチテナント環境を理解することが重要です。データの廃棄、ハイパーバイザーのセキュリティ、ノードの強化、および認証メカニズムなど、いくつか重要な部分があります。"
-
-#: ./doc/security-guide/ch062_audit-guidance.xml51(title)
-msgid "Prepare for external audit"
-msgstr "外部監査に備える"
-
-#: ./doc/security-guide/ch062_audit-guidance.xml52(para)
-msgid ""
-"Once the internal audit results look good, it is time to prepare for an "
-"external audit. There are several key actions to take at this stage, these "
-"are outlined below:"
-msgstr "内部監査の結果が良好であれば、いよいよ外部監査の準備です。この段階では、いくつかの鍵となる活動があります。概要は以下です。"
-
-#: ./doc/security-guide/ch062_audit-guidance.xml54(para)
-msgid ""
-"Maintain good records from your internal audit. These will prove useful "
-"during the external audit so you can be prepared to answer questions about "
-"mapping the compliance controls to a particular deployment."
-msgstr "内部監査での良好な状態を維持してください。それらは外部監査の実施期間に証明として役立ちます。またそれは、コンプライアンス統制に関する詳細な質疑応答の備えとなります。"
-
-#: ./doc/security-guide/ch062_audit-guidance.xml57(para)
-msgid ""
-"Deploy automated testing tools to ensure that the cloud remains compliant "
-"over time."
-msgstr "クラウドがコンプライアンスを維持し続けるために、自動テストツールを導入してください。"
-
-#: ./doc/security-guide/ch062_audit-guidance.xml60(para)
-msgid "Select an auditor."
-msgstr "監査人を選ぶ"
-
-#: ./doc/security-guide/ch062_audit-guidance.xml63(para)
-msgid ""
-"Selecting an auditor can be challenging. Ideally, you are looking for "
-"someone with experience in cloud compliance audits. OpenStack experience is "
-"another big plus. Often it is best to consult with people who have been "
-"through this process for referrals. Cost can vary greatly depending on the "
-"scope of the engagement and the audit firm considered."
-msgstr "監査人の選定は困難を伴うことがあります。クラウドのコンプライアンス監査経験がある人を見つけてくるのが理想です。OpenStackの経験があれば、なお良しです。このプロセスを経験している人に相談するのがベストでしょう。なお、費用は契約の範囲と監査法人に大きく依存します。"
-
-#: ./doc/security-guide/ch062_audit-guidance.xml66(title)
-msgid "External audit"
-msgstr "外部監査"
-
-#: ./doc/security-guide/ch062_audit-guidance.xml67(para)
-msgid ""
-"This is the formal audit process. Auditors will test security controls in "
-"scope for a specific certification, and demand evidentiary requirements to "
-"prove that these controls were also in place for the audit window (for "
-"example SOC 2 audits generally evaluate security controls over a 6-12 months"
-" period). Any control failures are logged, and will be documented in the "
-"external auditors final report. Dependent on the type of OpenStack "
-"deployment, these reports may be viewed by customers, so it is important to "
-"avoid control failures. This is why audit preparation is so important."
-msgstr "これが正式な監査プロセスです。監査人は、特定の認定向けのセキュリティ統制を確認し、これらの統制が監査期間において整っているか証明する根拠を要求します (たとえば、SOC 2監査は一般的に6-12ヶ月のセキュリティ統制を評価します)。どのような統制上の不具合も記録され、外部監査の最終報告書で文書化されます。OpenStack環境の種別に依存しますが、これらの報告書は顧客に公開されるでしょう。それゆえ統制上の不具合を避けることは重要です。これが監査への準備が重要であることの理由です。"
-
-#: ./doc/security-guide/ch062_audit-guidance.xml70(title)
-msgid "Compliance maintenance"
-msgstr "コンプライアンスの維持"
-
-#: ./doc/security-guide/ch062_audit-guidance.xml71(para)
-msgid ""
-"The process doesn't end with a single external audit. Most certifications "
-"require continual compliance activities which means repeating the audit "
-"process periodically. We recommend integrating automated compliance "
-"verification tools into a cloud to ensure that it is compliant at all times."
-" This should be in done in addition to other security monitoring tools. "
-"Remember that the goal is both security <emphasis>and</emphasis> compliance."
-" Failing on either of these fronts will significantly complicate future "
-"audits."
-msgstr "このプロセスは一度の外部監査で終わることがありません。多くの認証は継続的なコンプライアンス活動、すなわち、定期的な監査を要求します。わたしたちは、常に準拠を確実にするために、自動化されたコンプライアンス検証ツールをクラウド内に作ることをおすすめします。これは他のセキュリティ監視ツールに加え実装されるべきです。このゴールがセキュリティ<emphasis>および</emphasis>コンプライアンスであることを忘れないでください。これらのどちらかに不具合があれば、将来の監査において非常に面倒なことになります。"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch042_database-overview.xml18(None)
-#: ./doc/security-guide/ch042_database-overview.xml21(None)
-msgid ""
-"@@image: 'static/databaseusername.png'; md5=a6a5dadedbc1517069ca388c7ac5940a"
-msgstr "@@image: 'static/databaseusername.png'; md5=a6a5dadedbc1517069ca388c7ac5940a"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch042_database-overview.xml42(None)
-#: ./doc/security-guide/ch042_database-overview.xml45(None)
-msgid ""
-"@@image: 'static/databaseusernamessl.png'; "
-"md5=9c43242c47eb159b6f61ac41f3d8bced"
-msgstr "@@image: 'static/databaseusernamessl.png'; md5=9c43242c47eb159b6f61ac41f3d8bced"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch042_database-overview.xml104(None)
-#: ./doc/security-guide/ch042_database-overview.xml107(None)
-msgid ""
-"@@image: 'static/novaconductor.png'; md5=dbc1ba139bd1af333f0415bb48704843"
-msgstr "@@image: 'static/novaconductor.png'; md5=dbc1ba139bd1af333f0415bb48704843"
-
-#: ./doc/security-guide/ch042_database-overview.xml8(title)
-msgid "Database access control"
-msgstr "データベースアクセス制御"
-
-#: ./doc/security-guide/ch042_database-overview.xml9(para)
-msgid ""
-"Each of the core OpenStack services (Compute, Identity, Networking, Block "
-"Storage) store state and configuration information in databases. In this "
-"chapter, we discuss how databases are used currently in OpenStack. We also "
-"explore security concerns, and the security ramifications of database "
-"backend choices."
-msgstr "それぞれの OpenStack コアサービス (Compute, Identity, Networking, Block Storage) は、状態や設定に関する情報をデータベースに保存します。本章では、データベースが現在 OpenStack でどのように使用されているのかを議論します。セキュリティの考慮事項、データベースバックエンドの選択によるセキュリティへの影響についても説明します。"
-
-#: ./doc/security-guide/ch042_database-overview.xml11(title)
-msgid "OpenStack database access model"
-msgstr "OpenStack データベースアクセスモデル"
-
-#: ./doc/security-guide/ch042_database-overview.xml12(para)
-msgid ""
-"All of the services within an OpenStack project access a single database. "
-"There are presently no reference policies for creating table or row based "
-"access restrictions to the database."
-msgstr "OpenStack プロジェクトの中にあるすべてのサービスは単一のデータベースにアクセスします。データベースへのテーブルの作成や行単位のアクセス制限に関する明確なポリシーは今のところありません。"
-
-#: ./doc/security-guide/ch042_database-overview.xml13(para)
-msgid ""
-"There are no general provisions for granular control of database operations "
-"in OpenStack. Access and privileges are granted simply based on whether a "
-"node has access to the database or not. In this scenario, nodes with access "
-"to the database may have full privileges to DROP, INSERT, or UPDATE "
-"functions."
-msgstr "OpenStack には、データベース操作の詳細な制御に関する一般的な決まりがありません。アクセス権と権限は単にノードがデータベースにアクセスするかしないかに基づいて与えられます。このシナリオでは、データベースにアクセスするノードは、DROP、INSERT、UPDATE 関数の完全な権限を持っているでしょう。"
-
-#: ./doc/security-guide/ch042_database-overview.xml15(title)
-msgid "Granular access control"
-msgstr "精細なアクセス制御"
-
-#: ./doc/security-guide/ch042_database-overview.xml16(para)
-msgid ""
-"By default, each of the OpenStack services and their processes access the "
-"database using a shared set of credentials. This makes auditing database "
-"operations and revoking access privileges from a service and its processes "
-"to the database particularly difficult."
-msgstr "OpenStack の各サービスとそれらのプロセスはデフォルトで、共有クレデンシャルを使用してデータベースにアクセスします。これにより、データベース操作の監査および、サービスとそのプロセスからデータベースへのアクセス権の剥奪が特に難しくなります。"
-
-#: ./doc/security-guide/ch042_database-overview.xml26(title)
-#: ./doc/security-guide/ch042_database-overview.xml99(title)
-msgid "Nova-conductor"
-msgstr "Nova-conductor"
-
-#: ./doc/security-guide/ch042_database-overview.xml27(para)
-msgid ""
-"The compute nodes are the least trusted of the services in OpenStack because"
-" they host tenant instances. The <systemitem class=\"service\">nova-"
-"conductor</systemitem> service has been introduced to serve as a database "
-"proxy, acting as an intermediary between the compute nodes and the database."
-" We discuss its ramifications later in this chapter."
-msgstr "コンピュートノードは、プロジェクトのインスタンスをホストするため、OpenStack で最も信頼できないサービスです。<systemitem class=\"service\">nova-conductor</systemitem> サービスは、コンピュートノードとデータベースの中継役として動作する、データベースプロキシとして処理するために導入されました。その結果について本章で後ほど議論します。"
-
-#: ./doc/security-guide/ch042_database-overview.xml28(para)
-msgid "We strongly recommend:"
-msgstr "以下の事項を強く推奨します。"
-
-#: ./doc/security-guide/ch042_database-overview.xml30(para)
-msgid "All database communications be isolated to a management network"
-msgstr "すべてのデータベース通信の管理ネットワークへの分離"
-
-#: ./doc/security-guide/ch042_database-overview.xml33(para)
-msgid "Securing communications using SSL"
-msgstr "SSL を使用したセキュア通信"
-
-#: ./doc/security-guide/ch042_database-overview.xml36(para)
-msgid ""
-"Creating unique database user accounts per OpenStack service endpoint "
-"(illustrated below)"
-msgstr "OpenStack サービスのエンドポイントごとに一意なデータベースユーザーアカウントの作成 (下図)"
-
-#: ./doc/security-guide/ch042_database-overview.xml52(title)
-msgid "Database authentication and access control"
-msgstr "データベースの認証とアクセス制御"
-
-#: ./doc/security-guide/ch042_database-overview.xml53(para)
-msgid ""
-"Given the risks around access to the database, we strongly recommend that "
-"unique database user accounts be created per node needing access to the "
-"database. Doing this facilitates better analysis and auditing for ensuring "
-"compliance or in the event of a compromise of a node allows you to isolate "
-"the compromised host by removing access for that node to the database upon "
-"detection. When creating these per service endpoint database user accounts, "
-"care should be taken to ensure that they are configured to require SSL. "
-"Alternatively, for increased security it is recommended that the database "
-"accounts be configured using X.509 certificate authentication in addition to"
-" usernames and passwords."
-msgstr "データベースにアクセスする辺りにリスクがあるため、データベースにアクセスする必要があるノードごとに一意なデータベースユーザーアカウントを作成することを強く推奨します。この機能を実行することにより、コンプライアンスを保証するため、またはノードのセキュリティ被害にあった際に分析および監査をより良くできます。また、検知した際に被害にあったノードからデータベースへのアクセス権を削除することにより、被害にあったホストを分離できます。サービスのエンドポイントのデータベースユーザーアカウントごとにこれらを作成するとき、これらに SSL を要求するよう確実に設定することに注意してください。代わりに、セキュリティを向上させるために、データベースアカウントがユーザー名とパスワードに加えて X.509 証明書認証を使用するよう設定することを推奨します。"
-
-#: ./doc/security-guide/ch042_database-overview.xml55(title)
-msgid "Privileges"
-msgstr "権限"
-
-#: ./doc/security-guide/ch042_database-overview.xml56(para)
-msgid ""
-"A separate database administrator (DBA) account should be created and "
-"protected that has full privileges to create/drop databases, create user "
-"accounts, and update user privileges. This simple means of separation of "
-"responsibility helps prevent accidental misconfiguration, lowers risk and "
-"lowers scope of compromise."
-msgstr "データベースの作成と削除、ユーザーアカウントの作成、ユーザーの権限の更新に関する完全な権限を持つ、別々のデータベース管理者 (DBA) アカウントが作成され、保護されるべきです。これは、不注意な設定ミスを防ぎ、リスクを減らし、被害の範囲を小さくする、責任の分離を実現する簡単な方法です。"
-
-#: ./doc/security-guide/ch042_database-overview.xml57(para)
-msgid ""
-"The database user accounts created for the OpenStack services and for each "
-"node should have privileges limited to just the database relevant to the "
-"service where the node is a member."
-msgstr "データベースユーザーアカウントは OpenStack サービスのために作成され、ノードがメンバーであるサービスに関連するデータベースだけに制限された権限を持つ各ノードのために作成されます。"
-
-#: ./doc/security-guide/ch042_database-overview.xml61(title)
-msgid "Require user accounts to require SSL transport"
-msgstr "SSL 通信利用のための必須ユーザーアカウント"
-
-#: ./doc/security-guide/ch042_database-overview.xml63(title)
-#: ./doc/security-guide/ch042_database-overview.xml81(title)
-msgid "Configuration example #1: (MySQL)"
-msgstr "設定例 #1: (MySQL)"
-
-#: ./doc/security-guide/ch042_database-overview.xml67(title)
-#: ./doc/security-guide/ch042_database-overview.xml87(title)
-msgid "Configuration example #2: (PostgreSQL)"
-msgstr "設定例 #2: (PostgreSQL)"
-
-#: ./doc/security-guide/ch042_database-overview.xml68(para)
-msgid "In file <filename>pg_hba.conf</filename>:"
-msgstr "<filename>pg_hba.conf</filename> ファイル:"
-
-#: ./doc/security-guide/ch042_database-overview.xml70(para)
-msgid ""
-"Note this command only adds the ability to communicate over SSL and is non-"
-"exclusive. Other access methods that may allow unencrypted transport should "
-"be disabled so that SSL is the sole access method."
-msgstr "このコマンドは SSL 経由で通信する機能を追加するのみであり、排他的ではないことに注意してください。SSL を唯一のアクセス方法にするために、暗号化されていない通信を許可するかもしれない他のアクセス方法は無効化されるべきです。"
-
-#: ./doc/security-guide/ch042_database-overview.xml71(para)
-msgid ""
-"The <literal>md5</literal> parameter defines the authentication method as a "
-"hashed password. We provide a secure authentication example in the section "
-"below."
-msgstr "<literal>md5</literal> パラメーターは認証方式をハッシュ化パスワードとして定義します。以下のセクションでセキュアな認証例を提供します。"
-
-#: ./doc/security-guide/ch042_database-overview.xml78(title)
-msgid "Authentication with X.509 certificates"
-msgstr "X.509 証明書を用いた認証"
-
-#: ./doc/security-guide/ch042_database-overview.xml79(para)
-msgid ""
-"Security may be enhanced by requiring X.509 client certificates for "
-"authentication. Authenticating to the database in this manner provides "
-"greater identity assurance of the client making the connection to the "
-"database and ensures that the communications are encrypted."
-msgstr "認証に X.509 クライアント証明書を要求することにより、セキュリティを向上させられるかもしれません。この方法でデータベースに認証することにより、データベースに接続しているクライアントの ID 確認をより強力にでき、通信が確実に暗号化されます。"
-
-#: ./doc/security-guide/ch042_database-overview.xml92(title)
-msgid "OpenStack service database configuration"
-msgstr "OpenStack サービスのデータベース設定"
-
-#: ./doc/security-guide/ch042_database-overview.xml93(para)
-msgid ""
-"If your database server is configured to require X.509 certificates for "
-"authentication you will need to specify the appropriate SQLAlchemy query "
-"parameters for the database backend. These parameters specify the "
-"certificate, private key, and certificate authority information for use with"
-" the initial connection string."
-msgstr "お使いのデータベースサーバーが認証に X.509 証明書を要求するよう設定している場合、データベースバックエンドのために適切な SQLAlchemy クエリーパラメーターを指定する必要があります。これらのパラメーターは初期接続文字列に用いる証明書、秘密鍵、認証局の情報を指定します。"
-
-#: ./doc/security-guide/ch042_database-overview.xml94(para)
-msgid ""
-"Example of an <literal>:sql_connection</literal> string for X.509 "
-"certificate authentication to MySQL:"
-msgstr "MySQL への X.509 証明書認証の <literal>:sql_connection</literal> 文字列の例:"
-
-#: ./doc/security-guide/ch042_database-overview.xml100(para)
-msgid ""
-"OpenStack Compute offers a sub-service called <systemitem class=\"service"
-"\">nova-conductor</systemitem> which proxies database connections, with the "
-"primary purpose of having the nova compute nodes interfacing with "
-"<systemitem class=\"service\">nova-conductor</systemitem> to meet data "
-"persistence needs as opposed to directly communicating with the database."
-msgstr "OpenStack Compute は <systemitem class=\"service\">nova-conductor</systemitem> というサブサービスを提供します。これは、<systemitem class=\"service\">nova-conductor</systemitem> と直接接する nova コンピュートノードがデータ永続性の要求を満たすことを主目的として、それらがデータベースと直接通信する代わりにデータベース接続を中継します。"
-
-#: ./doc/security-guide/ch042_database-overview.xml101(para)
-msgid ""
-"Nova-conductor receives requests over RPC and performs actions on behalf of "
-"the calling service without granting granular access to the database, its "
-"tables, or data within. Nova-conductor essentially abstracts direct database"
-" access away from compute nodes."
-msgstr "Nova-conductor は RPC 経由でリクエストを受信します。そして、データベース、テーブル、データへの精細なアクセス権なしでサービスを呼び出す動作を実行します。Nova-conductor は本質的にコンピュートノードがデータベースに直接アクセスすることを抽象化します。"
-
-#: ./doc/security-guide/ch042_database-overview.xml102(para)
-msgid ""
-"This abstraction offers the advantage of restricting services to executing "
-"methods with parameters, similar to stored procedures, preventing a large "
-"number of systems from directly accessing or modifying database data. This "
-"is accomplished without having these procedures stored or executed within "
-"the context or scope of the database itself, a frequent criticism of typical"
-" stored procedures."
-msgstr "この抽象化は、サービスがパラメーター、ストアドプロシージャーのようなものを用いたメソッドの実行を制限し、数多くのシステムがデータベースのデータに直接アクセスしたり変更したりすることを防ぐという利点を提供します。これは、一般的なストアドプロシージャーという頻繁に批判される、データベース自体の文脈や範囲の中で、これらの手順を保存して実行することなく実現されます。"
-
-#: ./doc/security-guide/ch042_database-overview.xml110(para)
-msgid ""
-"Unfortunately, this solution complicates the task of more fine-grained "
-"access control and the ability to audit data access. Because the <systemitem"
-" class=\"service\">nova-conductor</systemitem> service receives requests "
-"over RPC, it highlights the importance of improving the security of "
-"messaging. Any node with access to the message queue may execute these "
-"methods provided by the <systemitem class=\"service\">nova-"
-"conductor</systemitem> and effectively modifying the database."
-msgstr "残念なことに、このソリューションはより詳細なアクセス制御とデータアクセスの監査機能を複雑にします。<systemitem class=\"service\">nova-conductor</systemitem> サービスは RPC 経由でリクエストを受信するため、メッセージングのセキュリティを改善する重要性を強調させます。メッセージキューにアクセスするすべてのノードは、<systemitem class=\"service\">nova-conductor</systemitem> により提供されるこれらの方式を実行し、データベースを効率的に変更するかもしれません。"
-
-#: ./doc/security-guide/ch042_database-overview.xml111(para)
-msgid ""
-"Finally, it should be noted that as of the Grizzly release, gaps exist where"
-" <systemitem class=\"service\">nova-conductor</systemitem> is not used "
-"throughout OpenStack Compute. Depending on one's configuration, the use of "
-"<systemitem class=\"service\">nova-conductor</systemitem> may not allow "
-"deployers to avoid the necessity of providing database GRANTs to individual "
-"compute host systems."
-msgstr "最後に、Grizzly リリース時点では、<systemitem class=\"service\">nova-conductor</systemitem> が OpenStack Compute 全体で使用されないというギャップが存在することに注意してください。その設定に依存して、<systemitem class=\"service\">nova-conductor</systemitem> を使用しても、導入者が個々のコンピュートホストにデータベースの権限を与える必要性を避けられないかもしれません。"
-
-#: ./doc/security-guide/ch042_database-overview.xml112(para)
-msgid ""
-"Note, as <systemitem class=\"service\">nova-conductor</systemitem> only "
-"applies to OpenStack Compute, direct database access from compute hosts may "
-"still be necessary for the operation of other OpenStack components such as "
-"Telemetry (ceilometer), Networking, and Block Storage."
-msgstr "<systemitem class=\"service\">nova-conductor</systemitem> は OpenStack Compute のみに適用されるので、Telemetry (ceilometer)、Networking、Block Storage のような他の OpenStack コンポーネントの動作のために、コンピュートホストから直接データベースにアクセスする必要があるかもしれないことに注意してください。"
-
-#: ./doc/security-guide/ch042_database-overview.xml118(para)
-msgid ""
-"Implementors should weigh the benefits and risks of both configurations "
-"before enabling or disabling the <systemitem class=\"service\">nova-"
-"conductor</systemitem> service. We are not yet prepared to recommend the use"
-" of <systemitem class=\"service\">nova-conductor</systemitem> in the Grizzly"
-" release. However, we do believe that this recommendation will change as "
-"additional features are added into OpenStack."
-msgstr "導入者は <systemitem class=\"service\">nova-conductor</systemitem> を有効化または無効化する前に両方の設定の利点とリスクを比較検討すべきです。Grizzly リリースでは <systemitem class=\"service\">nova-conductor</systemitem> の利用を推奨する準備ができていません。しかしながら、追加の機能が OpenStack にもたらされるので、この推奨について変更されると確信しています。"
-
-#: ./doc/security-guide/ch042_database-overview.xml119(para)
-msgid ""
-"To disable the <systemitem class=\"service\">nova-conductor</systemitem>, "
-"place the following into your <filename>nova.conf</filename> file (on your "
-"compute hosts):"
-msgstr "<systemitem class=\"service\">nova-conductor</systemitem> を無効化するために、以下の事項を (コンピュートホストの) <filename>nova.conf</filename> ファイルに記入します。"
-
-#: ./doc/security-guide/ch024_authentication.xml8(title)
-msgid "Identity"
-msgstr "Identity"
-
-#: ./doc/security-guide/ch024_authentication.xml9(para)
-msgid ""
-"The OpenStack Identity service (keystone) supports multiple methods of "
-"authentication, including username &amp; password, LDAP, and external "
-"authentication methods. Upon successful authentication, The Identity Service"
-" provides the user with an authorization token used for subsequent service "
-"requests."
-msgstr "OpenStack Identity Service (keystone) は、ユーザー名・パスワード、LDAP、外部認証方式など、複数の認証方式をサポートします。認証に成功すると、Identity Service は後続のサービスリクエストに使用する認可トークンをユーザーに返します。"
-
-#: ./doc/security-guide/ch024_authentication.xml14(para)
-msgid ""
-"Transport Layer Security TLS/SSL provides authentication between services "
-"and persons using X.509 certificates. Although the default mode for SSL is "
-"server-side only authentication, certificates may also be used for client "
-"authentication."
-msgstr "Transport Layer Security TLS/SSL は、サービスと人の間で X.509 を使用した認証を提供します。SSL の規定のモードはサーバーのみを認証しますが、証明書はクライアント認証にも使用できます。"
-
-#: ./doc/security-guide/ch024_authentication.xml19(title)
-msgid "Authentication"
-msgstr "認証"
-
-#: ./doc/security-guide/ch024_authentication.xml21(title)
-msgid "Invalid login attempts"
-msgstr "無効なログイン試行"
-
-#: ./doc/security-guide/ch024_authentication.xml22(para)
-msgid ""
-"The Identity Service does not provide a method to limit access to accounts "
-"after repeated unsuccessful login attempts. Repeated failed login attempts "
-"are likely brute-force attacks (Refer figure Attack-types). This is a more "
-"significant issue in Public clouds."
-msgstr "Identity は、ログイン試行が連続して失敗した後に、アカウントへのアクセスを制限する方法を提供していません。何度も失敗するログイン試行は総当たり攻撃 (図「攻撃の種類」参照) のようなものです。これは、パブリッククラウドでは、より重要な問題です。"
-
-#: ./doc/security-guide/ch024_authentication.xml27(para)
-msgid ""
-"Prevention is possible by using an external authentication system that "
-"blocks out an account after some configured number of failed login attempts."
-" The account then may only be unlocked with further side-channel "
-"intervention."
-msgstr "ログイン試行を指定した回数だけ失敗すると、アカウントをブロックするような外部認証システムを使用することにより、防止することができます。アカウントは、別の連絡手段を介してのみ、ロック解除するようにできます。"
-
-#: ./doc/security-guide/ch024_authentication.xml31(para)
-msgid ""
-"If prevention is not an option, detection can be used to mitigate "
-"damage.Detection involves frequent review of access control logs to identify"
-" unauthorized attempts to access accounts. Possible remediation would "
-"include reviewing the strength of the user password, or blocking the network"
-" source of the attack through firewall rules. Firewall rules on the keystone"
-" server that restrict the number of connections could be used to reduce the "
-"attack effectiveness, and thus dissuade the attacker."
-msgstr "もし防止することが選択肢になければ、被害を減らすために、検知することができます。検知は、アカウントへの権限のないアクセスを特定するために、アクセス制御ログを頻繁にレビューすることを意味します。その他の改善法としては、ユーザーパスワードの強度のレビュー、ファイアウォールルールで攻撃のネットワーク送信元のブロックなどがあります。接続数を制限するという、Keystone サーバのファイアウォールルールは、攻撃の効率を悪くし、攻撃者をあきらめさせるために使用できます。"
-
-#: ./doc/security-guide/ch024_authentication.xml40(para)
-msgid ""
-"In addition, it is useful to examine account activity for unusual login "
-"times and suspicious actions, with possibly disable the account. Oftentimes "
-"this approach is taken by credit card providers for fraud detection and "
-"alert."
-msgstr "さらに、普通でないログイン回数や疑わしいアクションに対して、アカウントの活動状況を確認することは有用です。可能ならば、アカウントを無効化します。しばしば、このアプローチはクレジットカード提供者により、詐欺の検出や警告のために使用されます。"
-
-#: ./doc/security-guide/ch024_authentication.xml46(title)
-msgid "Multi-factor authentication"
-msgstr "多要素認証"
-
-#: ./doc/security-guide/ch024_authentication.xml47(para)
-msgid ""
-"Employ multi-factor authentication for network access to privileged user "
-"accounts. The Identity Service supports external authentication services "
-"through the Apache web server that can provide this functionality. Servers "
-"may also enforce client-side authentication using certificates."
-msgstr "権限のあるユーザーアカウントにネットワークアクセス用の多要素認証を使用します。Identity はこの機能を提供できる Apache Web サーバーを通して外部認証サービスをサポートします。サーバーは証明書を使用したクライアント認証を強制することもできます。"
-
-#: ./doc/security-guide/ch024_authentication.xml52(para)
-msgid ""
-"This recommendation provides insulation from brute force, social "
-"engineering, and both spear and mass phishing attacks that may compromise "
-"administrator passwords."
-msgstr "このお勧めの方式は、管理者パスワードを流出させる可能性のある、総当たり、ソーシャルエンジニアリング、標的型と無差別のフィッシング攻撃に対する防御になります。"
-
-#: ./doc/security-guide/ch024_authentication.xml58(title)
-msgid "Authentication methods"
-msgstr "認証方式"
-
-#: ./doc/security-guide/ch024_authentication.xml60(title)
-msgid "Internally implemented authentication methods"
-msgstr "内部実装認証方式"
-
-#: ./doc/security-guide/ch024_authentication.xml61(para)
-msgid ""
-"The Identity Service can store user credentials in an SQL Database, or may "
-"use an LDAP-compliant directory server. The Identity database may be "
-"separate from databases used by other OpenStack services to reduce the risk "
-"of a compromise of the stored credentials."
-msgstr "Identity はユーザーのクレデンシャルを SQL データベースに保存できます。または、LDAP 対応のディレクトリサーバーを使用できます。Identity のデータベースは、保存されているクレデンシャルが漏洩するリスクを減らすために、他の OpenStack サービスが使用するデータベースと分離することもできます。"
-
-#: ./doc/security-guide/ch024_authentication.xml66(para)
-msgid ""
-"When you use a user name and password to authenticate, Identity does not "
-"enforce policies on password strength, expiration, or failed authentication "
-"attempts as recommended by NIST Special Publication 800-118 (draft). "
-"Organizations that desire to enforce stronger password policies should "
-"consider using Identity extensions or external authentication services."
-msgstr "認証のためにユーザー名とパスワードを使用する場合、Identity は NIST Special Publication 800-118 (draft) により推奨されている、パスワード強度、有効期限、ログイン試行回数制限に関するポリシーを強制できません。より強固なパスワードポリシーを強制したい組織は、Identity 拡張や外部認証サービスの使用を検討すべきです。"
-
-#: ./doc/security-guide/ch024_authentication.xml74(para)
-msgid ""
-"LDAP simplifies integration of Identity authentication into an "
-"organization's existing directory service and user account management "
-"processes."
-msgstr "LDAP により、組織の既存のディレクトリサービスやユーザーアカウント管理プロセスに Identity 認証をシンプルに統合できます。"
-
-#: ./doc/security-guide/ch024_authentication.xml77(para)
-msgid ""
-"Authentication and authorization policy in OpenStack may be delegated to an "
-"external LDAP server. A typical use case is an organization that seeks to "
-"deploy a private cloud and already has a database of employees, the users. "
-"This may be in an LDAP system. Using LDAP as a source of authority "
-"authentication, requests to Identity Service are delegated to the LDAP "
-"service, which will authorize or deny requests based on locally set "
-"policies. A token is generated on successful authentication."
-msgstr "OpenStack の認証と認可のポリシーは、外部 LDAP サーバーに権限委譲することができます。一般的なユースケースは、プライベートクラウドの導入を検討していて、すでに従業員とユーザーのデーターベースを持っている組織です。これは LDAP システムにあるかもしれません。権限のある認証のソースとして LDAP を使用することが、LDAP サービスに権限委譲している Identity に要求されます。このサービスがローカルに設定されたポリシーに基づいて認可または拒否します。トークンは認証が成功した場合に生成されます。"
-
-#: ./doc/security-guide/ch024_authentication.xml86(para)
-msgid ""
-"Note that if the LDAP system has attributes defined for the user such as "
-"admin, finance, HR etc, these must be mapped into roles and groups within "
-"Identity for use by the various OpenStack services. The "
-"<filename>/etc/keystone.conf</filename> file maps LDAP attributes to "
-"Identity attributes."
-msgstr "LDAP システムがユーザーに対して定義された、幹部社員、経理、人事などのような属性を持っている場合、これらはさまざまな OpenStack サービスにより使用するために Identity の中でロールとグループにマッピングされる必要があります。<filename>/etc/keystone.conf</filename> ファイルは、LDAP の属性をIdentity の属性にマッピングします。"
-
-#: ./doc/security-guide/ch024_authentication.xml91(para)
-msgid ""
-"The Identity Service <emphasis role=\"bold\">MUST NOT</emphasis> be allowed "
-"to write to LDAP services used for authentication outside of the OpenStack "
-"deployment as this would allow a sufficiently privileged keystone user to "
-"make changes to the LDAP directory. This would allow privilege escalation "
-"within the wider organization or facilitate unauthorized access to other "
-"information and resources. In such a deployment, user provisioning would be "
-"out of the realm of the OpenStack deployment."
-msgstr "Identity Service は OpenStack の外部にある認証用 LDAP サービスに書き込みを許可<emphasis role=\"bold\">してはいけません</emphasis>。十分な権限を持つ keystone ユーザーが LDAP ディレクトリに変更を加えられるようになるからです。これにより、より広い範囲の組織に権限が増えたり、他の情報やリソースに権限のアクセスが容易になったりするかもしれません。このような環境では、ユーザーの払い出しが OpenStack 環境のレルムの範囲外になるかもしれません。"
-
-#: ./doc/security-guide/ch024_authentication.xml101(para)
-msgid ""
-"There is an <link "
-"href=\"https://bugs.launchpad.net/ossn/+bug/1168252\">OpenStack Security "
-"Note (OSSN) regarding keystone.conf permissions</link>."
-msgstr "<link href=\"https://bugs.launchpad.net/ossn/+bug/1168252\">keystone.conf のパーミッションに関する OpenStack Security Note (OSSN)</link> があります。"
-
-#: ./doc/security-guide/ch024_authentication.xml105(para)
-msgid ""
-"There is an <link "
-"href=\"https://bugs.launchpad.net/ossn/+bug/1155566\">OpenStack Security "
-"Note (OSSN) regarding potential DoS attacks</link>."
-msgstr "<link href=\"https://bugs.launchpad.net/ossn/+bug/1155566\">潜在的な DoS 攻撃に関する OpenStack Security Note (OSSN)</link> があります。"
-
-#: ./doc/security-guide/ch024_authentication.xml112(title)
-msgid "External authentication methods"
-msgstr "外部認証方式"
-
-#: ./doc/security-guide/ch024_authentication.xml113(para)
-msgid ""
-"Organizations may desire to implement external authentication for "
-"compatibility with existing authentication services or to enforce stronger "
-"authentication policy requirements. Although passwords are the most common "
-"form of authentication, they can be compromised through numerous methods, "
-"including keystroke logging and password compromise. External authentication"
-" services can provide alternative forms of authentication that minimize the "
-"risk from weak passwords."
-msgstr "組織は、既存の認証サービスとの互換性のために外部認証を実装したいかもしれません。または、より強固な認証ポリシー要件を強制するためかもしれません。パスワードが認証のもっとも一般的な形式ですが、キー入力ロギングやパスワード推測など、さまざまな方法で破られる可能性があります。外部認証サービスにより、弱いパスワードのリスクを最小化する他の認証形式を提供できます。"
-
-#: ./doc/security-guide/ch024_authentication.xml122(para)
-msgid "These include:"
-msgstr "これらは以下のものが含まれます。"
-
-#: ./doc/security-guide/ch024_authentication.xml125(para)
-msgid ""
-"Password policy enforcement: Requires user passwords to conform to minimum "
-"standards for length, diversity of characters, expiration, or failed login "
-"attempts."
-msgstr "パスワードポリシー強制: ユーザーパスワードが、長さ、文字種の量、有効期限、失敗試行回数の最低基準を満たしていることを要求します。"
-
-#: ./doc/security-guide/ch024_authentication.xml130(para)
-msgid ""
-"Multi-factor authentication: The authentication service requires the user to"
-" provide information based on something they have, such as a one-time "
-"password token or X.509 certificate, and something they know, such as a "
-"password."
-msgstr "多要素認証: 認証サービスが、ユーザーが持っているもの (例: ワンタイムパスワードトークン、X.509 証明書) と知っていること (例: パスワード) に基づいた情報を提示するよう要求します。"
-
-#: ./doc/security-guide/ch024_authentication.xml137(para)
-msgid "Kerberos"
-msgstr "Kerberos"
-
-#: ./doc/security-guide/ch024_authentication.xml143(title)
-msgid "Authorization"
-msgstr "認可"
-
-#: ./doc/security-guide/ch024_authentication.xml144(para)
-msgid ""
-"The Identity Service supports the notion of groups and roles. Users belong "
-"to groups. A group has a list of roles. OpenStack services reference the "
-"roles of the user attempting to access the service. The OpenStack policy "
-"enforcer middleware takes into consideration the policy rule associated with"
-" each resource and the user's group/roles and tenant association to "
-"determine if he/she has access to the requested resource."
-msgstr "Identity はグループとロールの概念をサポートします。ユーザーはグループに所属します。グループはロールの一覧を持ちます。OpenStack サービスはユーザーがサービスにアクセスしようとしているロールを参照します。OpenStack ポリシー判定ミドルウェアにより、各リソースに関連付けられたポリシールール、ユーザーのグループとロール、テナント割り当てを考慮して、要求されたリソースへのアクセスが判断されます。"
-
-#: ./doc/security-guide/ch024_authentication.xml151(para)
-msgid ""
-"The Policy enforcement middleware enables fine-grained access control to "
-"OpenStack resources. Only admin users can provision new users and have "
-"access to various management functionality. The cloud tenant would be able "
-"to only spin up instances, attach volumes, etc."
-msgstr "ポリシー強制ミドルウェアにより OpenStack リソースに細かなアクセス制御を実現できます。管理ユーザーのみが新しいユーザーを作成でき、さまざまな管理機能にアクセスできます。クラウドのテナントはインスタンスの稼動、ボリュームの接続などのみが実行できます。"
-
-#: ./doc/security-guide/ch024_authentication.xml157(title)
-msgid "Establish formal access control policies"
-msgstr "公式なアクセス制御ポリシーの確立"
-
-#: ./doc/security-guide/ch024_authentication.xml158(para)
-msgid ""
-"Prior to configuring roles, groups, and users, document your required access"
-" control policies for the OpenStack installation. The policies should be "
-"consistent with any regulatory or legal requirements for the organization. "
-"Future modifications to access control configuration should be done "
-"consistently with the formal policies. The policies should include the "
-"conditions and processes for creating, deleting, disabling, and enabling "
-"accounts, and for assigning privileges to the accounts. Periodically review "
-"the policies and ensure that configuration is in compliance with approved "
-"policies."
-msgstr "ロール、グループ、ユーザーを設定する前に、OpenStack に必要なアクセス制御ポリシーをドキュメント化します。ポリシーは組織に対するあらゆる規制や法令の要求事項に沿っているべきです。アクセス制御設定のさらなる変更は公式なポリシーに従って実行されるべきです。ポリシーは、アカウントの作成、削除、無効化、有効化、および権限の割り当てに関する条件とプロセスを含めるべきです。定期的にポリシーをレビューし、設定が承認されたポリシーに従っていることを確認します。"
-
-#: ./doc/security-guide/ch024_authentication.xml171(title)
-msgid "Service authorization"
-msgstr "サービス認可"
-
-#: ./doc/security-guide/ch024_authentication.xml172(para)
-msgid ""
-"As described in the <link href=\"http://docs.openstack.org/admin-guide-"
-"cloud/content/index.html\"><citetitle>OpenStack Cloud Administrator "
-"Guide</citetitle></link>, cloud administrators must define a user for each "
-"service, with a role of Admin. This service user account provides the "
-"service with the authorization to authenticate users."
-msgstr "<link href=\"http://docs.openstack.org/admin-guide-cloud/content/index.html\"><citetitle>OpenStack Cloud Administrator Guide</citetitle></link> に記載されているとおり、クラウド管理者は各サービスに対して Admin ロールを持つユーザーを定義する必要があります。このサービスユーザーアカウントは、サービスがユーザーを認証するための権限を提供します。"
-
-#: ./doc/security-guide/ch024_authentication.xml179(para)
-msgid ""
-"The Compute and Object Storage services can be configured to use either the "
-"\"tempAuth\" file or Identity Service to store authentication information. "
-"The \"tempAuth\" solution MUST NOT be deployed in a production environment "
-"since it stores passwords in plain text."
-msgstr "Nova と Swift のサービスは認証情報を保存するために \"tempAuth\" ファイルと Identity を使用するよう設定できます。\"tempAuth\" ソリューションは、パスワードを平文で保存するため、本番環境で使用してはいけません。"
-
-#: ./doc/security-guide/ch024_authentication.xml184(para)
-msgid ""
-"The Identity Service supports client authentication for SSL which may be "
-"enabled. SSL client authentication provides an additional authentication "
-"factor, in addition to the username / password, that provides greater "
-"reliability on user identification. It reduces the risk of unauthorized "
-"access when user names and passwords may be compromised. However, there is "
-"additional administrative overhead and cost to issue certificates to users "
-"that may not be feasible in every deployment."
-msgstr "Identity は SSL のクライアント認証を有効化していると、それをサポートします。SSL クライアント認証はユーザー名、パスワードに加えて、ユーザー識別により信頼性を与えるために追加の認証要素を提供します。ユーザー名とパスワードが漏えいした場合に、権限のないアクセスのリスクを減らすことができます。しかしながら、証明書をユーザーに発行する追加の管理作業とコストが発生します。これはすべての環境で実現できるとは限りません。"
-
-#: ./doc/security-guide/ch024_authentication.xml194(para)
-msgid ""
-"We recommend that you use client authentication with SSL for the "
-"authentication of services to the Identity Service."
-msgstr "Identity にサービスの認証をするとき、SSL を使用したクライアント認証を使用することを推奨します。"
-
-#: ./doc/security-guide/ch024_authentication.xml198(para)
-msgid ""
-"The cloud administrator should protect sensitive configuration files for "
-"unauthorized modification. This can be achieved with mandatory access "
-"control frameworks such as SELinux, including "
-"<filename>/etc/keystone.conf</filename> and X.509 certificates."
-msgstr "クラウド管理者は権限のない変更から重要な設定ファイルを保護すべきです。これは SELinux のような強制アクセス制御のフレームワークで実現できます。これらには <filename>/etc/keystone.conf</filename> や X.509 証明書などがあります。"
-
-#: ./doc/security-guide/ch024_authentication.xml204(para)
-msgid ""
-"For client authentication with SSL, you need to issue certificates. These "
-"certificates can be signed by an external authority or by the cloud "
-"administrator. OpenStack services by default check the signatures of "
-"certificates and connections fail if the signature cannot be checked. If the"
-" administrator uses self-signed certificates, the check might need to be "
-"disabled. To disable these certificates, set <code>insecure=False</code> in "
-"the <code>[filter:authtoken]</code> section in the "
-"<filename>/etc/nova/api.paste.ini</filename> file. This setting also "
-"disables certificates for other components."
-msgstr "SSL を用いたクライアント認証のために、証明書を発行する必要があります。これらの証明書は外部の認証局やクラウド管理者により署名できます。OpenStack のサービスはデフォルトで証明書の署名を確認します。証明が確認できなければ、接続に失敗します。管理者が自己署名証明書を使用している場合、確認を無効化する必要があるかもしれません。これらの証明書を無効化するために、<filename>/etc/nova/api.paste.ini</filename> の <code>[filter:authtoken]</code> セクションに <code>insecure=False</code> を設定します。これらの設定は他のコンポーネントの証明書も無効化します。"
-
-#: ./doc/security-guide/ch024_authentication.xml218(title)
-msgid "Administrative users"
-msgstr "管理ユーザー"
-
-#: ./doc/security-guide/ch024_authentication.xml219(para)
-msgid ""
-"We recommend that admin users authenticate using Identity Service and an "
-"external authentication service that supports 2-factor authentication, such "
-"as a certificate. This reduces the risk from passwords that may be "
-"compromised. This recommendation is in compliance with NIST 800-53 IA-2(1) "
-"guidance in the use of multi factor authentication for network access to "
-"privileged accounts."
-msgstr "管理ユーザーは Identity や証明書のような 2 要素認証をサポートする外部認証サービスを使用して認証することを推奨します。これにより、パスワード推測によるリスクを減らすことができます。この推奨事項は特権アカウントへのネットワークアクセスに多要素認証を使用するという NIST 800-53 IA-2(1) ガイドに適合しています。"
-
-#: ./doc/security-guide/ch024_authentication.xml228(title)
-msgid "End users"
-msgstr "エンドユーザー"
-
-#: ./doc/security-guide/ch024_authentication.xml229(para)
-msgid ""
-"The Identity Service can directly provide end-user authentication, or can be"
-" configured to use external authentication methods to conform to an "
-"organization's security policies and requirements."
-msgstr "Identity は直接エンドユーザー認証を提供できます。または、組織のセキュリティポリシーや要求事項を確認するために外部認証方式を使用するよう設定できます。"
-
-#: ./doc/security-guide/ch024_authentication.xml236(title)
-msgid "Policies"
-msgstr "ポリシー"
-
-#: ./doc/security-guide/ch024_authentication.xml237(para)
-msgid ""
-"Each OpenStack service has a policy file in JSON format, called "
-"<filename>policy.json</filename>. The policy file specifies rules, and the "
-"rule that governs each resource. A resource could be API access, the ability"
-" to attach to a volume, or to fire up instances."
-msgstr "各 OpenStack サービスは <filename>policy.json</filename> という JSON 形式のポリシーファイルを持ちます。ポリシーファイルはルールを指定します。ルールは各リソースを決定します。リソースは API アクセスできます。ボリュームの接続やインスタンスの起動などです。"
-
-#: ./doc/security-guide/ch024_authentication.xml242(para)
-msgid ""
-"The policies can be updated by the cloud administrator to further control "
-"access to the various resources. The middleware could also be further "
-"customized. Note that your users must be assigned to groups/roles that you "
-"refer to in your policies."
-msgstr "さまざまなリソースへのアクセス権をさらに制御するために、クラウド管理者がポリシーを更新できます。ミドルウェアによりさらにカスタマイズすることもできます。そのポリシーを参照しているグループやロールにユーザーを割り当てる必要があることに注意してください。"
-
-#: ./doc/security-guide/ch024_authentication.xml247(para)
-msgid ""
-"Below is a snippet of the Block Storage service "
-"<filename>policy.json</filename> file."
-msgstr "以下は Block Storage Service の <filename>policy.json</filename> ファイルの抜粋です。"
-
-#: ./doc/security-guide/ch024_authentication.xml250(para)
-msgid ""
-"Note the <emphasis role=\"bold\">default</emphasis> rule specifies that the "
-"user must be either an admin or the owner of the volume. It essentially says"
-" only the owner of a volume or the admin may create/delete/update volumes. "
-"Certain other operations such as managing volume types are accessible only "
-"to admin users."
-msgstr "<emphasis role=\"bold\">デフォルト</emphasis>のルールは、ユーザーが管理者であるか、ボリュームの所有者である必要があることを指定しています。つまり、ボリュームの所有者と管理者のみがボリュームを作成、削除、更新できます。ボリューム形式の管理など、他の特定の操作は管理ユーザーのみがアクセス可能です。"
-
-#: ./doc/security-guide/ch024_authentication.xml258(title)
-msgid "Tokens"
-msgstr "トークン"
-
-#: ./doc/security-guide/ch024_authentication.xml259(para)
-msgid ""
-"Once a user is authenticated, a token is generated and used internally in "
-"OpenStack for authorization and access. The default token <emphasis "
-"role=\"bold\">lifespan</emphasis> is<emphasis role=\"bold\"> 24 "
-"hours</emphasis>. It is recommended that this value be set lower but caution"
-" needs to be taken as some internal services will need sufficient time to "
-"complete their work. The cloud may not provide services if tokens expire too"
-" early. An example of this would be the time needed by the Compute service "
-"to transfer a disk image onto the hypervisor for local caching."
-msgstr "ユーザーが認証されると、トークンが生成され、認可とアクセスのために OpenStack で内部的に使用されます。デフォルトのトークンの<emphasis role=\"bold\">有効期間</emphasis>は <emphasis role=\"bold\">24 時間</emphasis>です。この値はより短く設定することが推奨されますが、いくつかの内部サービスが処理を完了するために十分な時間が必要であるので注意する必要があります。トークンがすぐに失効すると、クラウドがサービスを提供できないかもしれません。これの例は、Compute Service がディスクイメージをハイパーバイザーのローカルキャッシュに転送するために必要な時間です。"
-
-#: ./doc/security-guide/ch024_authentication.xml269(para)
-msgid ""
-"The following example shows a PKI token. Note that, in practice, the token "
-"id value is about 3500 bytes. We shorten it in this example."
-msgstr "以下は PKI トークンの例です。実際は token id の値が約3500バイトであることに注意してください。この例では短くしています。"
-
-#: ./doc/security-guide/ch024_authentication.xml273(para)
-msgid ""
-"Note that the token is often passed within the structure of a larger context"
-" of an Identity Service response. These responses also provide a catalog of "
-"the various OpenStack services. Each service is listed with its name, access"
-" endpoints for internal, admin, and public access."
-msgstr "トークンは Identity の応答のより大きなコンテキスト構造の中で渡されることに注意してください。これらの応答はさまざまな OpenStack サービスのカタログも提供しています。各サービスはその名前と、内部、管理、パブリックなアクセス用のエンドポイントを一覧にします。"
-
-#: ./doc/security-guide/ch024_authentication.xml278(para)
-msgid ""
-"The Identity Service supports token revocation. This manifests as an API to "
-"revoke a token, to list revoked tokens and individual OpenStack services "
-"that cache tokens to query for the revoked tokens and remove them from their"
-" cache and append the same to their list of cached revoked tokens."
-msgstr "Identity はトークン失効をサポートします。これは、トークンを失効するため、失効済みトークンを一覧表示するために API として宣言されます。また、トークンをキャッシュしている各 OpenStack サービスが失効済みトークンを問い合わせるため、それらのキャッシュから失効済みトークンを削除するため、キャッシュした失効済みトークンの一覧に追加するためにもあります。"
-
-#: ./doc/security-guide/ch024_authentication.xml285(title)
-msgid "Future"
-msgstr "将来"
-
-#: ./doc/security-guide/ch024_authentication.xml286(para)
-msgid ""
-"Domains are high-level containers for projects, users and groups. As such, "
-"they can be used to centrally manage all keystone-based identity components."
-" With the introduction of account domains, server, storage and other "
-"resources can now be logically grouped into multiple projects (previously "
-"called tenants) which can themselves be grouped under a master account-like "
-"container. In addition, multiple users can be managed within an account "
-"domain and assigned roles that vary for each project."
-msgstr "ドメインはプロジェクト、ユーザー、グループの高いレベルでのコンテナーです。そのように、すべての keystone ベースの識別コンポーネントを一元的に管理するために使用されます。アカウントドメインを導入すると、サーバー、ストレージ、他のリソースは複数のプロジェクト (以前はテナントと呼ばれていました) の中で論理的にグループ化できます。これは、アカウントのようなマスターコンテナーの下でグループ化できます。さらに、複数のユーザーがアカウントドメインの中で管理でき、各プロジェクトで変化するロールを割り当てられます。"
-
-#: ./doc/security-guide/ch024_authentication.xml295(para)
-msgid ""
-"The Identity V3 API supports multiple domains. Users of different domains "
-"may be represented in different authentication backends and even have "
-"different attributes that must be mapped to a single set of roles and "
-"privileges, that are used in the policy definitions to access the various "
-"service resources."
-msgstr "Identity V3 API はマルチドメインをサポートします。異なるドメインのユーザーは、異なる認証バックエンドで表現され、単一セットのロールと権限にマッピングされる異なる属性を持ちます。これらはさまざまなサービスリソースにアクセスするために、ポリシー定義で使用されます。"
-
-#: ./doc/security-guide/ch024_authentication.xml301(para)
-msgid ""
-"Where a rule may specify access to only admin users and users belonging to "
-"the tenant, the mapping may be trivial. In other scenarios the cloud "
-"administrator may need to approve the mapping routines per tenant."
-msgstr "ルールにより管理ユーザーとテナントに所属するユーザーのみにアクセス権を設定されるかもしれないため、マッピングは些細なことかもしれません。他のシナリオの場合、クラウド管理者がテナントごとのマッピング作業を承認する必要があるかもしれません。"
-
-#: ./doc/security-guide/ch015_case-studies-management.xml8(title)
-msgid "Case studies: management interfaces"
-msgstr "ケーススタディ: 管理インターフェース"
-
-#: ./doc/security-guide/ch015_case-studies-management.xml9(para)
-msgid ""
-"Previously we discussed typical OpenStack management interfaces and "
-"associated backplane issues. We will now approach these issues by returning "
-"to our Alice and Bob case study. Specifically, we will look into how both "
-"Alice and Bob will address:"
-msgstr "一般的な OpenStack 管理インターフェースと関連のバックプレーンの問題について、ここまでに議論しました。再度、アリスとボブのケーススタディに戻って、これらの問題を見ていきます。特に、アリスとボブが以下の点をどのように対応したかを確認していきます。"
-
-#: ./doc/security-guide/ch015_case-studies-management.xml15(para)
-msgid "Cloud administration"
-msgstr "クラウド管理"
-
-#: ./doc/security-guide/ch015_case-studies-management.xml18(para)
-msgid "Self service"
-msgstr "セルフサービス"
-
-#: ./doc/security-guide/ch015_case-studies-management.xml21(para)
-msgid "Data replication and recovery"
-msgstr "データの複製およびリカバリー"
-
-#: ./doc/security-guide/ch015_case-studies-management.xml24(para)
-msgid "SLA and security monitoring"
-msgstr "SLA およびセキュリティの監視"
-
-#: ./doc/security-guide/ch015_case-studies-management.xml29(para)
-msgid ""
-"When building her private cloud, while air-gapped, Alice still needs to "
-"consider her service management interfaces. Before deploying her private "
-"cloud, Alice has completed her system documentation. Specifically she has "
-"identified which OpenStack services will exist in each security domain. From"
-" there Alice has further restricted access to management interfaces by "
-"deploying a combination of IDS, SSL encryption, and physical network "
-"isolation. Additionally, Alice requires high availability and redundant "
-"services. Thus, Alice sets up redundant infrastructure for various OpenStack"
-" API services."
-msgstr "プライベートクラウドを構築する際、ネットワークが物理的に分離されていますが、アリスはサービス管理インターフェースを検討する必要があります。プライベートクラウドをデプロイする前に、システム文書を書き上げました。特に、どの OpenStack サービスが各セキュリティドメインに存在するかを特定しました。そこから、アリスは、IDS、SSL、暗号化、物理的なネットワークの分離を組み合わせてデプロイすることで、管理インターフェースへのアクセスをさらに制限しました。また、高可用性や冗長サービスも必要とするため、様々な OpenStack API サービスに対してインフラストラクチャーの冗長設定を行いました。"
-
-#: ./doc/security-guide/ch015_case-studies-management.xml30(para)
-msgid ""
-"Alice also needs to provide assurances that the physical servers and "
-"hypervisors have been built from a known secure state into a well-defined "
-"configuration. To enable this, Alice uses a combination of a Configuration "
-"Management platform to configure each machine according to the standards and"
-" regulations she must comply with. It will also enable Alice to report "
-"periodically on the state of her cloud and perform remediation to a known "
-"state should anything be out of the ordinary. Additionally, Alice provides "
-"hardware assurances by using a PXE system to build her nodes from a known "
-"set of base images. During the boot process, Alice provides further "
-"assurances by enabling Intel TXT and related trusted boot technologies "
-"provided by the hardware."
-msgstr "また、物理サーバーとハイパーバイザーは既知のセキュアな状態から十分に定義された設定へと確実に構築されるようにする必要があります。これを可能にするには、構成管理プラットフォームを合わせて使用して、準拠する必要のある規格や規定に従い各マシンを設定していきます。また、構成管理プラットフォームは、クラウドの状態を定期的に報告して、通常以外のことが発生した場合に既知の状態に修正することができます。さらに、PXE システムを使用することで、既知のベースイメージからノードを構築してハードウェア保証を提供することができます。ブートプロセス時に、そのハードウェアから提供される Intel TXT や関連の信頼できるブート技術を有効にすることでさらなる保証を確保できます。"
-
-#: ./doc/security-guide/ch015_case-studies-management.xml34(para)
-msgid ""
-"As a public cloud provider, Bob is concerned with both the continuous "
-"availability of management interfaces and the security of transactions to "
-"the management interfaces. To that end Bob implements multiple redundant "
-"OpenStack API endpoints for the services his cloud will run. Additionally on"
-" the public network Bob uses SSL to encrypt all transactions between his "
-"customers and his cloud interfaces. To isolate his cloud operations Bob has "
-"physically isolated his management, instance migration, and storage "
-"networks."
-msgstr "パブリッククラウドのプロバイダーとして、ボブは管理インターフェースの継続的な可用性と、管理インターフェースへのトランザクションのセキュリティの両方を考慮しています。このように、ボブは、クラウドが実行するサービスに対して、冗長化された OpenStack API エンドポイントを実装します。さらに、パブリックネットワークでは、SSL を使用して、顧客とクラウドインターフェースの間のトランザクションをすべて暗号化します。クラウドの運用を分離するために、ボブは管理、インスタンスマイグレーション、ストレージネットワークを物理的に分離しました。"
-
-#: ./doc/security-guide/ch015_case-studies-management.xml35(para)
-msgid ""
-"To ease scaling and reduce management overhead Bob implements a "
-"configuration management system. For customer data assurances, Bob offers a "
-"backup as a service product as requirements will vary between customers. "
-"Finally, Bob does not provide a \"baremetal\" or the ability to schedule an "
-"entire node, so to reduce management overhead and increase operational "
-"efficiency Bob does not implement any node boot time security."
-msgstr "管理オーバーヘッドのスケーリングや削減を簡単にするため、構成管理システムを実装します。顧客のデータ保証に対しては、顧客ごとに要件が変わるためサービス商品としてバックアップを提供します。最後に、「ベアメタル」やノード全体のスケジュール機能を提供せず、管理オーバーヘッドの削減、運用効率の向上を図るため、ノードのブート時におけるセキュリティは実装しません。"
-
-#: ./doc/security-guide/ch018_case-studies-pkissl.xml8(title)
-msgid "Case studies: PKI and certificate management"
-msgstr "ケーススタディ: PKI と証明書管理"
-
-#: ./doc/security-guide/ch018_case-studies-pkissl.xml9(para)
-msgid ""
-"In this case study we discuss how Alice and Bob would address deployment of "
-"PKI certification authorities (CA) and certificate management."
-msgstr "このケーススタディでは、アリスとボグがPKI認証局(CA)の構築と証明書管理をどのように行うのかについて解説します。"
-
-#: ./doc/security-guide/ch018_case-studies-pkissl.xml12(para)
-msgid ""
-"Alice as a cloud architect within a government agency knows that her agency "
-"operates its own certification authority. Alice contacts the PKI office in "
-"her agency that manages her PKI and certificate issuance. Alice obtains "
-"certificates issued by this CA and configures the services within both the "
-"public and management security domains to use these certificates. Since "
-"Alice's OpenStack deployment exists entirely on a disconnected from the "
-"Internet network, she makes sure to remove all default CA bundles that "
-"contain external public CA providers to ensure the OpenStack services only "
-"accept client certificates issued by her agency's CA."
-msgstr "アリスは政府機関のクラウドアーキテクトで、彼女の機関が独自のCAを運用している事を知っています。アリスは、彼女のPKIを管理して証明書を発行する職場の PKI オフィスにコンタクトします。アリスはこのCAによって発行された証明書を入手し、これらの証明書を使用するようパブリックと管理セキュリティドメインの両方のサービスを設定します。アリスの OpenStack デプロイが完全にインターネットから独立して存在するので、OpenStack サービスが彼女の組織の CA から発行されたクライアント証明書のみ許可するよう、外部のパブリックな CA プロバイダを含むデフォルトの全 CA バンドルが削除されている事を確認しています。"
-
-#: ./doc/security-guide/ch018_case-studies-pkissl.xml16(para)
-msgid ""
-"Bob is architecting a public cloud and needs to ensure that the publicly "
-"facing OpenStack services are using certificates issued by a major public "
-"CA. Bob acquires certificates for his public OpenStack services and "
-"configures the services to use PKI and SSL and includes the public CAs in "
-"his trust bundle for the services. Additionally, Bob also wants to further "
-"isolate the internal communications amongst the services within the "
-"management security domain. Bob contacts the team within his organization "
-"that is responsible for managing his organizations PKI and issuance of "
-"certificates using their own internal CA. Bob obtains certificates issued by"
-" this internal CA and configures the services that communicate within the "
-"management security domain to use these certificates and configures the "
-"services to only accept client certificates issued by his internal CA."
-msgstr "ボブはパブリッククラウドのアーキテクトで、インターネットに接続された OpenStack サービスが主要な公的 CA から発行された証明書をちゃんと使用する必要があります。ボブは彼のパブリックな OpenStack サービス用の証明書を受領し、PKI と SSL を使用するようサービスを設定し、彼のサービス用の信用バンドル中に公的CAが含まれるようにします。更に、ボブはセキュリティ管理ドメイン内でサービス間の内部通信の更なる分断をしたいとも思っています。ボブは、彼の組織中で、内部CAを使用して彼の組織の PKI 管理と証明書の発行を担当しているチームにコンタクトします。ボブはこの内部CAが発行した証明書を入手し、これらの証明書を使用するよう管理セキュリティドメイン中での通信を行うサービスを設定し、内部CAが発行したクライアント証明書のみ許可するようサービスを設定します。"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch031_neutron-architecture.xml87(None)
-#: ./doc/security-guide/ch031_neutron-architecture.xml92(None)
-msgid ""
-"@@image: 'static/sdn-connections.png'; md5=1de9169834b34c83f574f2a1225b27f0"
-msgstr "@@image: 'static/sdn-connections.png'; md5=1de9169834b34c83f574f2a1225b27f0"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch031_neutron-architecture.xml109(None)
-#: ./doc/security-guide/ch031_neutron-architecture.xml114(None)
-msgid ""
-"@@image: 'static/1aa-network-domains-diagram.png'; "
-"md5=135806775939d9e5e750264d8a5fe8de"
-msgstr "@@image: 'static/1aa-network-domains-diagram.png'; md5=135806775939d9e5e750264d8a5fe8de"
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml8(title)
-msgid "Networking architecture"
-msgstr "Networking アーキテクチャ"
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml9(para)
-msgid ""
-"OpenStack Networking is a standalone service that often deploys several "
-"processes across a number of nodes. These processes interact with each other"
-" and other OpenStack services. The main process of the OpenStack Networking "
-"service is <systemitem class=\"service\">neutron-server</systemitem>, a "
-"Python daemon that exposes the OpenStack Networking API and passes tenant "
-"requests to a suite of plug-ins for additional processing."
-msgstr "OpenStack Networking は多数ノード間において幾つかのプロセスのデプロイにしばしば含まれる独立サービスです。OpenStack Networking サービスのメインプロセスは <systemitem class=\"service\">neutron-server</systemitem> で、これは OpenStack Networking API を提供し、追加処理用の適切なプラグインにテナントのリクエストを渡します。"
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml17(para)
-msgid "The OpenStack Networking components are:"
-msgstr "OpenStack Networking のコンポーネントは以下のとおりです。"
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml21(term)
-msgid ""
-"neutron server (<systemitem class=\"service\">neutron-server</systemitem> "
-"and <systemitem class=\"service\">neutron-*-plugin</systemitem>)"
-msgstr "neutron サーバー (<systemitem class=\"service\">neutron-server</systemitem>、<systemitem class=\"service\">neutron-*-plugin</systemitem>)"
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml25(para)
-msgid ""
-"This service runs on the network node to service the Networking API and its "
-"extensions. It also enforces the network model and IP addressing of each "
-"port. The neutron-server and plugin agents require access to a database for "
-"persistent storage and access to a message queue for inter-communication."
-msgstr "このサービスはネットワークノード上で実行され、Networking API とその拡張を提供します。これはまた、各ポートのネットワークモデルと IP アドレスを管理します。neutron-server とプラグインエージェントは、永続ストレージ用のデータベースへのアクセスと、内部通信用のメッセージキューへのアクセスを要求します。"
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml35(term)
-msgid "plugin agent (<systemitem class=\"service\">neutron-*-agent</systemitem>)"
-msgstr "プラグインエージェント (<systemitem class=\"service\">neutron-*-agent</systemitem>)"
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml38(para)
-msgid ""
-"Runs on each compute node to manage local virtual switch (vswitch) "
-"configuration. The plug-in that you use determine which agents run. This "
-"service requires message queue access. <emphasis>Optional depending on "
-"plugin.</emphasis>"
-msgstr "ローカルの仮想スイッチ（vswitch）設定を管理する為に各 compute ノード上で実行されます。使用するプラグインにより、どのエージェントを実行するか決まります。このサービスはメッセージキューへのアクセスを必要とします。<emphasis>オプションのプラグインに依存します。</emphasis>"
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml46(term)
-msgid "DHCP agent (<systemitem class=\"service\">neutron-dhcp-agent</systemitem>)"
-msgstr "DHCP エージェント (<systemitem class=\"service\">neutron-dhcp-agent</systemitem>)"
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml49(para)
-msgid ""
-"Provides DHCP services to tenant networks. This agent is the same across all"
-" plug-ins and is responsible for maintaining DHCP configuration. The "
-"<systemitem class=\"service\">neutron-dhcp-agent</systemitem> requires "
-"message queue access."
-msgstr "テナントネットワークに DHCP サービスを提供します。このエージェントは全てのプラグインと同様で、DHCP 設定の管理を担当します。<systemitem class=\"service\">neutron-dhcp-agent</systemitem> はメッセージキューアクセスが必要です。"
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml58(term)
-msgid "L3 agent (<systemitem class=\"service\">neutron-l3-agent</systemitem>)"
-msgstr "L3 エージェント (<systemitem class=\"service\">neutron-l3-agent</systemitem>)"
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml61(para)
-msgid ""
-"Provides L3/NAT forwarding for external network access of VMs on tenant "
-"networks. Requires message queue access. <emphasis>Optional depending on "
-"plug-in.</emphasis>"
-msgstr "テナントネットワーク上の VM において外部ネットワーク用 L3/NAT 転送を提供します。メッセージキューが必要です。<emphasis>プラグイン次第では別の物が必要になります。</emphasis>"
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml69(term)
-msgid "network provider services (SDN server/services)"
-msgstr "ネットワークプロバイダーサービス (SDN サーバー/サービス)"
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml71(para)
-msgid ""
-"Provide additional networking services to tenant networks. These SDN "
-"services might interact with the <systemitem class=\"service\">neutron-"
-"server</systemitem>, <systemitem class=\"service\">neutron-"
-"plugin</systemitem>, and/or plugin-agents through REST APIs or other "
-"communication channels."
-msgstr "テナントネットワークを提供する追加のネットワークサービスを提供します。これらの SDN サービスは REST API  又は他の通信チャネルを介して、<systemitem class=\"service\">neutron-server</systemitem>、<systemitem class=\"service\">neutron-plugin</systemitem>、プラグインエージェントと交信するかも知れません。"
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml81(para)
-msgid ""
-"The following figure shows an architectural and networking flow diagram of "
-"the OpenStack Networking components:"
-msgstr "以下の図は OpenStack Networking コンポーネント群の構造・ネットワークフローダイアグラムを示しています。"
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml97(title)
-msgid "OpenStack Networking service placement on physical servers"
-msgstr "OpenStack Networking の配置と物理サービス"
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml98(para)
-msgid ""
-"This guide focuses on a standard architecture that includes a "
-"<emphasis>cloud controller</emphasis> host, a <emphasis>network</emphasis> "
-"host, and a set of <emphasis>compute</emphasis> hypervisors for running VMs."
-msgstr "このガイドは、<emphasis>クラウドコントローラ</emphasis>ホスト１台、<emphasis>ネットワーク</emphasis>ホスト１台、VMを実行する<emphasis>compute</emphasis>ハイパーバイザーの集合を含む標準的なアーキテクチャにフォーカスします。"
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml105(title)
-msgid "Network connectivity of physical servers"
-msgstr "物理サーバのネットワーク接続性"
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml118(para)
-msgid ""
-"A standard OpenStack Networking setup has up to four distinct physical data "
-"center networks:"
-msgstr "標準的な OpenStack Networking セットアップは最大４つの物理データセンターネットワークがあります。"
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml122(term)
-msgid "Management network"
-msgstr "管理ネットワーク"
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml124(para)
-msgid ""
-"Used for internal communication between OpenStack Components. The IP "
-"addresses on this network should be reachable only within the data center "
-"and is considered the Management Security Domain."
-msgstr "OpenStack コンポーネント間の内部通信に使用されます。このネットワークの IP アドレスはデータセンター内でのみ到達可能であるべきです。管理セキュリティドメインで検討します。"
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml132(term)
-msgid "Guest network"
-msgstr "ゲストネットワーク"
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml134(para)
-msgid ""
-"Used for VM data communication within the cloud deployment. The IP "
-"addressing requirements of this network depend on the OpenStack Networking "
-"plug-in in use and the network configuration choices of the virtual networks"
-" made by the tenant. This network is considered the Guest Security Domain."
-msgstr "クラウドデプロイ中の VM データ通信に使用されます。このネットワークの IP アドレス要件は、使用中の OpenStack Networking プラグインとテナントにより作成される仮想ネットワークのネットワーク設定の選定に依存します。このネットワークはゲストセキュリティドメインで検討します。"
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml144(term)
-msgid "External network"
-msgstr "外部ネットワーク"
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml146(para)
-msgid ""
-"Used to provide VMs with Internet access in some deployment scenarios. The "
-"IP addresses on this network should be reachable by anyone on the Internet "
-"and is considered to be in the Public Security Domain."
-msgstr "幾つかのデプロイシナリオ中のインターネットアクセスを持つVMを提供する為に使用されます。このネットワーク上の IP アドレスはインターネット上の誰もが通信可能です。パブリックセキュリティドメインで検討します。"
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml154(term)
-msgid "API network"
-msgstr "API ネットワーク"
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml156(para)
-msgid ""
-"Exposes all OpenStack APIs, including the OpenStack Networking API, to "
-"tenants. The IP addresses on this network should be reachable by anyone on "
-"the Internet. This may be the same network as the external network, as it is"
-" possible to create a subnet for the external network that uses IP "
-"allocation ranges to use only less than the full range of IP addresses in an"
-" IP block. This network is considered the Public Security Domain."
-msgstr "テナントに OpenStack Networking API を含む全 OpenStack API を晒します。このネットワーク上の IP アドレスはインターネット上の誰もがアクセス可能であるべきです。これは外部ネットワークと同じネットワークであっても構いません。外部ネットワーク用に、IP ブロック中の全 IP アドレス範囲より少ない部分を使う為の IP 割当範囲を使用するサブネットを作成する事が出来るからです。このネットワークはパブロックセキュリティドメインで検討します。"
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml169(para)
-msgid ""
-"For additional information see the <link href=\"http://docs.openstack.org"
-"/admin-guide-cloud/content/ch_networking.html\">Networking chapter</link> in"
-" the <citetitle>OpenStack Cloud Administrator Guide</citetitle>."
-msgstr "更なる情報は、<citetitle>OpenStack Cloud Administrator Guide</citetitle> 中の <link href=\"http://docs.openstack.org/admin-guide-cloud/content/ch_networking.html\">Networking</link> の章を参照して下さい。"
-
-#: ./doc/security-guide/ch047_data-encryption.xml8(title)
-msgid "Data encryption"
-msgstr "データ暗号化"
-
-#: ./doc/security-guide/ch047_data-encryption.xml9(para)
-msgid ""
-"The option exists for implementors to encrypt tenant data wherever it is "
-"stored on disk or transported over a network. This is above and beyond the "
-"general recommendation that users encrypt their own data before sending it "
-"to their provider."
-msgstr "このオプションは、データをディスクに保存する箇所やデータをネットワーク経由で転送する箇所でテナントデータを暗号化する実装者用です。ユーザが自分自身のデータをプロバイダに送信する前にデータを暗号化するという一般的な推奨の上またはその先にあるものです。"
-
-#: ./doc/security-guide/ch047_data-encryption.xml10(para)
-msgid ""
-"The importance of encrypting data on behalf of tenants is largely related to"
-" the risk assumed by a provider that an attacker could access tenant data. "
-"There may be requirements here in government, as well as requirements per-"
-"policy, in private contract, or even in case law in regard to private "
-"contracts for public cloud providers. It is recommended that a risk "
-"assessment and legal consul advised before choosing tenant encryption "
-"policies."
-msgstr "テナントの為のデータ暗号化の重要性は、攻撃者がテナントデータにアクセスできる事をプロバイダが想定するリスクに広く関係しています。政府での要件があるかも知れませんし、（ポリシー単位の要件と同様）パブリッククラウド提供者用の随意契約に関しては、随意契約の中、あるいは判例法の中でさえ要求されるかも知れません。テナント暗号化ポリシーを選択する前に、リスク分析と法務コンサルの忠告を受ける事をお勧めします。"
-
-#: ./doc/security-guide/ch047_data-encryption.xml11(para)
-msgid ""
-"Per-instance or per-object encryption is preferable over, in descending "
-"order, over per-project, per-tenant, per-host, and per-cloud aggregations. "
-"This recommendation is inverse to the complexity and difficulty of "
-"implementation. Presently, in some projects it is difficult or impossible to"
-" implement encryption as loosely granular as even per-tenant. We recommend "
-"implementors make a best-effort in encrypting tenant data."
-msgstr "暗号化の単位は、好ましい方から順にインスタンス単位又はオブジェクト単位、プロジェクト単位、テナント単位、ホスト単位、クラウド集合単位です。この推奨順は、実装の複雑さと困難さの順序の逆です。現在、いくつかのプロジェクトでは、テナント単位ですら粒度の荒い暗号化の実装が困難又は不可能です。実装者がテナントデータの暗号化を最善策とする事をお勧めします。"
-
-#: ./doc/security-guide/ch047_data-encryption.xml12(para)
-msgid ""
-"Often, data encryption relates positively to the ability to reliably destroy"
-" tenant and per-instance data, simply by throwing away the keys. It should "
-"be noted that in doing so, it becomes of great importance to destroy those "
-"keys in a reliable and secure manner."
-msgstr "時々、データ暗号化は単に暗号鍵を捨てるという事による、信頼できるテナントやインスタンス単位のデータ削除可能性と明確に関係があります。そうするよう記述すべきですし、信頼できる安全な方法でこれらの鍵を破壊する事が従来になります。"
-
-#: ./doc/security-guide/ch047_data-encryption.xml13(para)
-msgid "Opportunities to encrypt data for users are present:"
-msgstr "ユーザ用のデータ暗号化をする機会は現存します。"
-
-#: ./doc/security-guide/ch047_data-encryption.xml18(para)
-#: ./doc/security-guide/ch047_data-encryption.xml31(title)
-msgid "Block Storage volumes and instance ephemeral filesystems"
-msgstr "Block Storage ボリュームとインスタンスの一時ファイルシステム"
-
-#: ./doc/security-guide/ch047_data-encryption.xml21(para)
-#: ./doc/security-guide/ch047_data-encryption.xml37(title)
-msgid "Network data"
-msgstr "ネットワークデータ"
-
-#: ./doc/security-guide/ch047_data-encryption.xml26(para)
-msgid ""
-"The ability to encrypt objects in Object Storage is presently limited to "
-"disk-level encryption per node. However, there does exist third-party "
-"extensions and modules for per-object encryption. These modules have been "
-"proposed upstream, but have not per this writing been formally accepted. "
-"Below are some pointers:"
-msgstr "Object Storage 中のオブジェクトの暗号化の可能性は、現時点ではノード単位のディスクレベル暗号化に限定されています。しかしながら、オブジェクト単位の暗号化用のサードパーティ拡張やモジュールが存在します。これらのモジュールはアップストリームに提案されていますが、この文書を書いている時点では公式に認可されていません。下記はそれらの幾つかへのポインタです。"
-
-#: ./doc/security-guide/ch047_data-encryption.xml27(link)
-msgid "https://github.com/Mirantis/swift-encrypt"
-msgstr "https://github.com/Mirantis/swift-encrypt"
-
-#: ./doc/security-guide/ch047_data-encryption.xml28(link)
-msgid ""
-"http://www.mirantis.com/blog/on-disk-encryption-prototype-for-openstack-"
-"swift/"
-msgstr "http://www.mirantis.com/blog/on-disk-encryption-prototype-for-openstack-swift/"
-
-#: ./doc/security-guide/ch047_data-encryption.xml32(para)
-msgid ""
-"The ability to encrypt volumes depends on the service backends chosen. Some "
-"backends may not support this at all."
-msgstr "暗号化ボリュームの可否は選択したサービスバックエンドに依存します。いくつかのバックエンドは暗号化を全くサポートしないかも知れません。"
-
-#: ./doc/security-guide/ch047_data-encryption.xml33(para)
-msgid ""
-"As both block storage and compute support LVM backed storage, we can easily "
-"provide an example applicable to both systems. In deployments using LVM, "
-"encryption may be performed against the backing physical volumes. An "
-"encrypted block device would be created using the standard Linux tools, with"
-" the LVM physical volume (PV) created on top of the decrypted block device "
-"using pvcreate. Then, the vgcreate or vgmodify tool may be used to add the "
-"encrypted physical volume to an LVM volume group (VG)."
-msgstr "Block Storage と Compute は両方、LVM ベースのストレージをサポートしているので、両システムに簡単に適用可能な例を提供します。LVM を用いたデプロイでは、暗号化はベースの物理ボリュームに対して実施できます。暗号化ブロックデバイスは、pvcreate を使用して復号化したブロックデバイスの上に作成した LVM 物理ボリューム (PV) を用いて、標準の Linux ツールを使用して作成する事ができます。それから、vgcreate 又は vgmodify ツールを使用して、暗号化した物理ボリュームを LVM のボリュームグループ (VG) に追加できます。"
-
-#: ./doc/security-guide/ch047_data-encryption.xml34(para)
-msgid ""
-"A feature aimed for the Havana release provides encryption of the VM's data "
-"before it is written to disk. This allows the privacy of data to be "
-"maintained while residing on the storage device. The idea is similar to how "
-"self-encrypting drives work. This feature presents a normal block storage "
-"device to the VM but encrypts the bytes in the virtualization host before "
-"writing them to the disk. The block server operates exactly as it does when "
-"reading and writing unencrypted blocks, except special handling will be "
-"required for Block Storage features such as snapshots and live migration. "
-"Note that this feature uses an independent key manager."
-msgstr "Havana リリース向けの１機能が、ディスクに書き込まれる前の VM データの暗号化を提供しています。これは、ストレージデバイス上でもデータのプライバシーが管理される事を可能にします。このアイデアは自己暗号化ドライブが機能する方法と同様です。この機能は、VM には通常のブロックストレージデバイスとして見えますが、仮想化ホストではディスクにデータが書き込まれる前にデータが暗号化されます。ブロックサーバは、特別な処理がスナップショットやライブマイグレーションといった Block Storage の機能に向けて要求される事を除いて、暗号化されていないブロックを読み書きする場合と全く同様に処理が行われます。この機能は独立した鍵管理を使用する事に注意して下さい。"
-
-#: ./doc/security-guide/ch047_data-encryption.xml38(para)
-msgid ""
-"Tenant data for compute could be encrypted over IPSec or other tunnels. This"
-" is not functionality common or standard in OpenStack, but is an option "
-"available to motivated and interested implementors."
-msgstr "compute のテナントデータは IPSec 又は他のトンネルで暗号化できます。OpenStack での共通または標準の機能ではありませんが、やる気と興味がある実装者に１つの選択肢が利用できます。"
-
-#: ./doc/security-guide/ch047_data-encryption.xml42(para)
-msgid ""
-"Block storage supports a variety of mechanisms for supplying mountable "
-"volumes. It is outside the scope of this guide to specify recommendations "
-"for each Block Storage backend driver. For the purpose of performance, many "
-"storage protocols are unencrypted. Some protocols such as iSCSI can provide "
-"authentication and encrypted sessions, it is our recommendation to enable "
-"these features."
-msgstr "Block Storage は、マウント可能なボリュームの提供に向けた様々な機構をサポートします。Block Storage の各バックエンドドライバ用に推奨を指定する事はこのガイドの範囲外です。性能の為に、多くのストレージプロトコルは暗号化されていません。iSCSI のような幾つかのプロトコルは、認証と暗号化セッションを提供できます。これらの機能を有効にする事を推奨します。"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch005_security-domains.xml29(None)
-#: ./doc/security-guide/ch005_security-domains.xml32(None)
-msgid ""
-"@@image: 'static/untrusted_trusted.png'; "
-"md5=a582dac2ad0b3f439fd4b08386853056"
-msgstr "@@image: 'static/untrusted_trusted.png'; md5=a582dac2ad0b3f439fd4b08386853056"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch005_security-domains.xml60(None)
-#: ./doc/security-guide/ch005_security-domains.xml63(None)
-msgid ""
-"@@image: 'static/bridging_security_domains_1.png'; "
-"md5=0d5ca26c51882ce3253405e91a597715"
-msgstr "@@image: 'static/bridging_security_domains_1.png'; md5=0d5ca26c51882ce3253405e91a597715"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch005_security-domains.xml68(None)
-#: ./doc/security-guide/ch005_security-domains.xml71(None)
-msgid ""
-"@@image: 'static/bridging_domains_clouduser.png'; "
-"md5=17c8a233ee7de17d2f600c7f6f6afe24"
-msgstr "@@image: 'static/bridging_domains_clouduser.png'; md5=17c8a233ee7de17d2f600c7f6f6afe24"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch005_security-domains.xml134(None)
-#: ./doc/security-guide/ch005_security-domains.xml137(None)
-msgid ""
-"@@image: 'static/threat_actors.png'; md5=114c2f9bd9d0319bdd83f9e229d44649"
-msgstr "@@image: 'static/threat_actors.png'; md5=114c2f9bd9d0319bdd83f9e229d44649"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch005_security-domains.xml171(None)
-#: ./doc/security-guide/ch005_security-domains.xml174(None)
-msgid ""
-"@@image: 'static/high-capability.png'; md5=b7ab599c8b40558a52c0ca86aad89741"
-msgstr "@@image: 'static/high-capability.png'; md5=b7ab599c8b40558a52c0ca86aad89741"
-
-#: ./doc/security-guide/ch005_security-domains.xml8(title)
-msgid "Security boundaries and threats"
-msgstr "セキュリティ境界と脅威"
-
-#: ./doc/security-guide/ch005_security-domains.xml9(para)
-msgid ""
-"A cloud can be abstracted as a collection of logical components by virtue of"
-" their function, users, and shared security concerns, which we call security"
-" domains. Threat actors and vectors are classified based on their motivation"
-" and access to resources. Our goal is to provide you a sense of the security"
-" concerns with respect to each domain depending on your risk/vulnerability "
-"protection objectives."
-msgstr "クラウドとは、セキュリティドメインと呼ばれる、機能やユーザー、共有セキュリティの懸念点に基づいた論理コンポーネントの集まりであると要約できます。脅威に関するアクターやベクトルは、リソースへのアクセスや動機をベースに分類されます。OpenStack の目標は、リスクや脆弱性保護の目的にあわせてドメインごとにセキュリティの懸念点に関する判断材料を提供することです。"
-
-#: ./doc/security-guide/ch005_security-domains.xml11(title)
-msgid "Security domains"
-msgstr "セキュリティドメイン"
-
-#: ./doc/security-guide/ch005_security-domains.xml12(para)
-msgid ""
-"A security domain comprises users, applications, servers or networks that "
-"share common trust requirements and expectations within a system. Typically "
-"they have the same authentication and authorization (AuthN/Z) requirements "
-"and users."
-msgstr "セキュリティドメインは、システム内の信頼性に関する共通の要件や期待を共有するユーザー、アプリケーション、サーバー、ネットワークのいずれかで構成されています。通常、これらのドメインには、同じ認証と承認  (AuthN/Z) 要件およびユーザーが指定されています。"
-
-#: ./doc/security-guide/ch005_security-domains.xml13(para)
-msgid ""
-"Although you may desire to break these domains down further (we later "
-"discuss where this may be appropriate), we generally refer to four distinct "
-"security domains which form the bare minimum that is required to deploy any "
-"OpenStack cloud securely. These security domains are:"
-msgstr "これらのドメインをさらに分類する場合もありますが (該当箇所で説明)、一般的に OpenStack クラウドをセキュアにデプロイしていく上で最低限必要な部分を構成する、4 つの異なるセキュリティドメインのことを指します。以下に、これらのセキュリティドメインを示しています。"
-
-#: ./doc/security-guide/ch005_security-domains.xml15(para)
-#: ./doc/security-guide/ch005_security-domains.xml36(title)
-msgid "Public"
-msgstr "パブリック"
-
-#: ./doc/security-guide/ch005_security-domains.xml18(para)
-#: ./doc/security-guide/ch005_security-domains.xml41(title)
-msgid "Guest"
-msgstr "ゲスト"
-
-#: ./doc/security-guide/ch005_security-domains.xml21(para)
-#: ./doc/security-guide/ch005_security-domains.xml46(title)
-msgid "Management"
-msgstr "管理"
-
-#: ./doc/security-guide/ch005_security-domains.xml24(para)
-#: ./doc/security-guide/ch005_security-domains.xml51(title)
-msgid "Data"
-msgstr "データ"
-
-#: ./doc/security-guide/ch005_security-domains.xml27(para)
-msgid ""
-"We selected these security domains because they can be mapped independently "
-"or combined to represent the majority of the possible areas of trust within "
-"a given OpenStack deployment. For example, some deployment topologies "
-"combine both guest and data domains onto one physical network versus others,"
-" which have these networks physically separated. In each case, the cloud "
-"operator should be aware of the appropriate security concerns. Security "
-"domains should be mapped out against your specific OpenStack deployment "
-"topology. The domains and their trust requirements depend upon whether the "
-"cloud instance is public, private, or hybrid."
-msgstr "上記のセキュリティドメインを選択したのは、個別にマッピング可能であること、または組み合わせると指定の OpenStack デプロイメントで存在する可能性のある信頼エリアの大部分を表すことができるためです。例えば、デプロイメントトポロジによっては、物理ネットワーク 1 つ vs 他のネットワークとなるように、ゲストとデータドメインの両方を組みわせて、ネットワークを物理的に分割するものもあります。いずれの場合も、クラウドオペレーターは、適切なセキュリティの関心事を認識する必要があります。これらのドメインや信頼性に関する要件は、クラウドインスタンスがパブリック、プライベート、ハイブリッドのいずれであるかによって変わってきます。"
-
-#: ./doc/security-guide/ch005_security-domains.xml37(para)
-msgid ""
-"The public security domain is an entirely untrusted area of the cloud "
-"infrastructure. It can refer to the Internet as a whole or simply to "
-"networks over which you have no authority. Any data that transits this "
-"domain with confidentiality or integrity requirements should be protected "
-"using compensating controls."
-msgstr "パブリックのセキュリティドメインとは、クラウドインフラストラクチャーの中で完全に信頼できないエリアのことです。インターネット全体を指す場合や、単に権限を持たないネットワークを指す場合があります。機密性や完全性の要件を持つデータがこのドメインを通過する場合には、補完コントロールを使用してこのデータを保護する必要があります。"
-
-#: ./doc/security-guide/ch005_security-domains.xml38(para)
-msgid ""
-"This domain should always be considered <emphasis>untrusted</emphasis>."
-msgstr "このドメインは常に、<emphasis>信頼できない</emphasis>と考えなければなりません。 "
-
-#: ./doc/security-guide/ch005_security-domains.xml42(para)
-msgid ""
-"Typically used for compute instance-to-instance traffic, the guest security "
-"domain handles compute data generated by instances on the cloud but not "
-"services that support the operation of the cloud, such as API calls."
-msgstr "ゲストのセキュリティドメインは、Compute のインスタンス間通信に通常使用されますが、API の呼び出しなどクラウドのオペレーションをサポートするサービスではなく、クラウド上のインスタンスが生成する Compute データを処理します。"
-
-#: ./doc/security-guide/ch005_security-domains.xml43(para)
-msgid ""
-"Public cloud providers and private cloud providers who do not have stringent"
-" controls on instance use or who allow unrestricted internet access to VMs "
-"should consider this domain to be <emphasis>untrusted</emphasis>. Private "
-"cloud providers may want to consider this network as internal and therefore "
-"<emphasis>trusted</emphasis> only if they have controls in place to assert "
-"that they trust instances and all their tenants."
-msgstr "インスタンスの使用に関する厳密な制御がない、または制限なしに仮想マシンへインターネットアクセスが可能なパブリッククラウドのプロバイダーやプライベートクラウドのプロバイダーは、このドメインを <emphasis>untrusted</emphasis> であると見なすべきです。プライベートクライドプロバイダーは、インスタンスおよびすべてのテナントを確実に信頼できるように制御が設定されている場合のみ、このネットワークを内部、つまり <emphasis>trusted</emphasis> であると考えるようにしてください。"
-
-#: ./doc/security-guide/ch005_security-domains.xml47(para)
-msgid ""
-"The management security domain is where services interact. Sometimes "
-"referred to as the \"control plane\", the networks in this domain transport "
-"confidential data such as configuration parameters, usernames, and "
-"passwords. Command and Control traffic typically resides in this domain, "
-"which necessitates strong integrity requirements. Access to this domain "
-"should be highly restricted and monitored. At the same time, this domain "
-"should still employ all of the security best practices described in this "
-"guide."
-msgstr "管理セキュリティドメインは、サービスがやりとりをする場所です。このドメインは時に「コントロールプレーン」と呼ばれることもあり、このドメイン内のネットワークは設定パラメーター、ユーザー名、パスワードなどの機密データを送信します。コマンドやコントロールトラフィックは通常このドメインに常駐し、完全性に関する強い要件が必要となります。このドメインへのアクセスについては非常に制限されたものでなくてはならず、さらに監視も必要です。また、このセキュリティドメインでは、本ガイドで記載されているセキュリティのベストプラクティスすべてを採用するようにしてください。"
-
-#: ./doc/security-guide/ch005_security-domains.xml48(para)
-msgid ""
-"In most deployments this domain is considered <emphasis>trusted</emphasis>. "
-"However, when considering an OpenStack deployment, there are many systems "
-"that bridge this domain with others, potentially reducing the level of trust"
-" you can place on this domain. See <xref linkend=\"ch005_security-domains-"
-"idp61360\"/> for more information."
-msgstr "多くのデプロイメントでは、この管理セキュリティドメインは<emphasis>信頼できる</emphasis>と考えられています。しかし、OpenStack のデプロイメントの場合、このドメインと他のものをブリッジするシステムが多数あるため、このドメインの信頼レベルは下がります。詳細は、<xref linkend=\"ch005_security-domains-idp61360\"/>を参照してください。"
-
-#: ./doc/security-guide/ch005_security-domains.xml52(para)
-msgid ""
-"The data security domain is concerned primarily with information pertaining "
-"to the storage services within OpenStack. Much of the data that crosses this"
-" network has high integrity and confidentiality requirements and depending "
-"on the type of deployment there may also be strong availability "
-"requirements."
-msgstr "データセキュリティドメインは主に、OpenStack ではストレージサービスの情報に関係します。このネットワークを通過するデータの多くは、完全性や機密性に関する強い要件を持ち、デプロイメントの種類によっては強い可用性要件が出てくる場合があります。"
-
-#: ./doc/security-guide/ch005_security-domains.xml53(para)
-msgid ""
-"The trust level of this network is heavily dependent on deployment decisions"
-" and as such we do not assign this any default level of trust."
-msgstr "このネットワークの信頼レベルは、デプロイメントの意思決定により左右されるため、デフォルトの信頼レベルは割り当てていません。"
-
-#: ./doc/security-guide/ch005_security-domains.xml57(title)
-msgid "Bridging security domains"
-msgstr "セキュリティドメインのブリッジ"
-
-#: ./doc/security-guide/ch005_security-domains.xml58(para)
-msgid ""
-"A <emphasis>bridge</emphasis> is a component that exists inside more than "
-"one security domain. Any component that bridges security domains with "
-"different trust levels or authentication requirements must be carefully "
-"configured. These bridges are often the weak points in network architecture."
-" A bridge should always be configured to meet the security requirements of "
-"the highest trust level of any of the domains it is bridging. In many cases "
-"the security controls for bridges should be a primary concern due to the "
-"likelihood of attack."
-msgstr "<emphasis>ブリッジ</emphasis>とは、複数のセキュリティドメイン内に存在するコンポーネントです。異なる信頼レベルまたは認証要件が指定されたセキュリテイドメイン間をブリッジするコンポーネントは、慎重に設定する必要があります。ネットワークアーキテクチャの中で、これらのブリッジは弱点となることが多くなっています。常に、ブリッジするドメインの中で最も高い信頼レベルのセキュリティ要件を満たすように、ブリッジを設定するようにしてください。多くの場合、攻撃の可能性の高さから、主にブリッジのセキュリティ制御について考慮する必要があります。"
-
-#: ./doc/security-guide/ch005_security-domains.xml66(para)
-msgid ""
-"The diagram above shows a compute node bridging the data and management "
-"domains, as such the compute node should be configured to meet the security "
-"requirements of the management domain. Similarly the API Endpoint in this "
-"diagram is bridging the untrusted public domain and the management domain, "
-"and should be configured to protect against attacks from the public domain "
-"propagating through to the management domain."
-msgstr "上記の図は、データドメインと管理ドメインをブリッジするコンピュートノードです。このように、コンピュートノードは管理ドメインのセキュリティ要件に見合うように設定する必要があります。同様に、この図の API エンドポイントは信頼できないパブリックドメインと管理ドメインをブリッジしており、パブリックドメインから管理ドメインに伝搬しないように攻撃から保護されるように設定する必要があります。"
-
-#: ./doc/security-guide/ch005_security-domains.xml74(para)
-msgid ""
-"In some cases deployers may want to consider securing a bridge to a higher "
-"standard than any of the domains in which it resides. Given the above "
-"example of an API endpoint, an adversary could potentially target the API "
-"endpoint from the public domain, leveraging it in the hopes of compromising "
-"or gaining access to the management domain."
-msgstr "デプロイ担当者は、ブリッジするどのドメインよりも高い基準でブリッジのセキュリティを確保するように考えるようにしてください。API エンドポイントの上記の例では、攻撃者はパブリックドメインから API エンドポイントをターゲットにして、情報漏洩や管理ドメインへアクセス権の獲得を期待しつつこのエンドポイントを利用するのです。"
-
-#: ./doc/security-guide/ch005_security-domains.xml75(para)
-msgid ""
-"The design of OpenStack is such that separation of security domains is "
-"difficult - as core services will usually bridge at least two domains, "
-"special consideration must be given when applying security controls to them."
-msgstr "OpenStack のデザインではセキュリティドメインの分離が困難です。コアサービスは通常少なくとも 2 つのドメインをブリッジしているため、ドメインのセキュリティ制御を適用する場合、細心の注意を払う必要があります。"
-
-#: ./doc/security-guide/ch005_security-domains.xml78(title)
-msgid "Threat classification, actors and attack vectors"
-msgstr "脅威の分類、アクター、攻撃ベクトル"
-
-#: ./doc/security-guide/ch005_security-domains.xml79(para)
-msgid ""
-"Most types of cloud deployment, public or private, are exposed to some form "
-"of attack. In this chapter we categorize attackers and summarize potential "
-"types of attacks in each security domain."
-msgstr "クラウドデプロイメントの種類の多く (パブリックまたはプライベート) は、なんらかの攻撃にさらされています。本章では、攻撃者を分類して、各セキュリティドメインで考えられる攻撃の種類をまとめていきます。"
-
-#: ./doc/security-guide/ch005_security-domains.xml81(title)
-msgid "Threat actors"
-msgstr "脅威のアクター"
-
-#: ./doc/security-guide/ch005_security-domains.xml82(para)
-msgid ""
-"A threat actor is an abstract way to refer to a class of adversary that you "
-"may attempt to defend against. The more capable the actor, the more "
-"expensive the security controls that are required for successful attack "
-"mitigation and prevention. Security is a tradeoff between cost, usability "
-"and defense. In some cases it will not be possible to secure a cloud "
-"deployment against all of the threat actors we describe here. Those "
-"deploying an OpenStack cloud will have to decide where the balance lies for "
-"their deployment / usage."
-msgstr "脅威のアクターとは、防御の対象となりえる攻撃者のクラスを抽象的に表したものです。アクターの技術が高くなるにつれ、攻撃の軽減や防止を成功させるために必要なセキュリティ制御にかかるコストが嵩みます。セキュリティはコスト、使いやすさ、防御の間でのトレードオフということになります。ここで記載した脅威のアクターすべてから、クラウドのデプロイメントを保護することはできません。OpenStack クラウドをデプロイする方は、デプロイメントと用途の間でバランスが確保できるポイントを決定する必要が出てきます。"
-
-#: ./doc/security-guide/ch005_security-domains.xml92(para)
-msgid ""
-"<emphasis role=\"bold\">Intelligence services</emphasis> — Considered by "
-"this guide as the most capable adversary. Intelligence Services and other "
-"state actors can bring tremendous resources to bear on a target. They have "
-"capabilities beyond that of any other actor. It is very difficult to defend "
-"against these actors without incredibly stringent controls in place, both "
-"human and technical."
-msgstr "<emphasis role=\"bold\">インテリジェンスサービス</emphasis> — このガイドでは最も有能な攻撃者とされています。インテリジェンスサービスやその他の国家主体は、ターゲットに圧力をかけるために莫大なリソースを費やすことができます。他のどのアクターよりも能力があります。人や技術両方の面で非常に厳しい制御なしでは、これらのアクターから防御することは極めて困難です。"
-
-#: ./doc/security-guide/ch005_security-domains.xml102(para)
-msgid ""
-"<emphasis role=\"bold\">Serious organized crime</emphasis> — Highly capable "
-"and financially driven groups of attackers. Able to fund in-house exploit "
-"development and target research. In recent years the rise of organizations "
-"such as the Russian Business Network, a massive cyber-criminal enterprise "
-"has demonstrated how cyber attacks have become a commodity. Industrial "
-"espionage falls within the SOC group."
-msgstr "<emphasis role=\"bold\">重大組織犯罪</emphasis> — 極めて有能で金銭で動く攻撃者グループ。エクスポロイと開発やターゲットのリサーチに対する資金を組織内で調達できます。最近、ロシアンビジネスネットワーク (RBN) などの組織が登場し、大規模なサイバー犯罪企業がサイバー攻撃がどのようにして商品として成り立ったかを証明しました。産業スパイ活動は、SOC グループに分類されます。"
-
-#: ./doc/security-guide/ch005_security-domains.xml112(para)
-msgid ""
-"<emphasis role=\"bold\">Highly capable groups</emphasis> — This refers to "
-"'Hacktivist' type organizations who are not typically commercially funded "
-"but can pose a serious threat to service providers and cloud operators."
-msgstr "<emphasis role=\"bold\">非常に有能な組織</emphasis> — これは通常ビジネスから資金を調達しているのではありませんが、サービスプロバイダーやクラウドオペレーターに対して重大な脅威をもたらす可能性のある「ハクティビスト」タイプの組織のことを指します。"
-
-#: ./doc/security-guide/ch005_security-domains.xml119(para)
-msgid ""
-"<emphasis role=\"bold\">Motivated individuals</emphasis> — Acting alone, "
-"these attackers come in many guises, such as rogue or malicious employees, "
-"disaffected customers, or small-scale industrial espionage."
-msgstr "<emphasis role=\"bold\">動機のある個人</emphasis> — 一人で行動するこれらの攻撃者は、詐欺師または悪意のある従業員、不満を持った顧客、小規模の産業スパイなど多くのものに扮して攻撃します。"
-
-#: ./doc/security-guide/ch005_security-domains.xml126(para)
-msgid ""
-"<emphasis role=\"bold\">Script kiddies</emphasis> — Automated vulnerability "
-"scanning/exploitation. Non-targeted attacks. Often only a nuisance, "
-"compromise by one of these actors presents a major risk to an organization's"
-" reputation."
-msgstr "<emphasis role=\"bold\">スクリプトキディ</emphasis> — 自動化された脆弱性のスキャンやエクスプロイト。非標的型の攻撃。単なるいたずらの場合が多く、上記のアクターのいずれかによる情報漏洩により組織の評判に大きなリスクを与えます。"
-
-#: ./doc/security-guide/ch005_security-domains.xml142(title)
-msgid "Public and private cloud considerations"
-msgstr "パブリッククラウドとプライベートクラウドの考慮点"
-
-#: ./doc/security-guide/ch005_security-domains.xml143(para)
-msgid ""
-"Private clouds are typically deployed by enterprises or institutions inside "
-"their networks and behind their firewalls. Enterprises will have strict "
-"policies on what data is allowed to exit their network and may even have "
-"different clouds for specific purposes. Users of a private cloud are "
-"typically employees of the organization that owns the cloud and are able to "
-"be held accountable for their actions. Employees often attend training "
-"sessions before accessing the cloud and will likely take part in regular "
-"scheduled security awareness training. Public clouds by contrast cannot make"
-" any assertions about their users, cloud use-cases or user motivations. This"
-" immediately pushes the guest security domain into a completely "
-"<emphasis>untrusted</emphasis> state for public cloud providers."
-msgstr "通常プライベートクラウドは企業や組織により、内部のネットワークやファイアウォールの内側にデプロイされます。企業は、社内のネットワークから出すことのできるデータが何であるか、厳密な方針が設定されており、特定の目的ごとに別のクラウドを設定する場合さえもあります。プライベートクラウドのユーザーは通常、クラウドを所有して各自の行動に責任を課される組織内の従業員です。このような従業員は、クラウドにアクセスする前にトレーニングセッションに出席することもしばしばあり、定期的に予定されるセキュリティ認識トレーニングに参加する場合も多くあります。反対に、パブリッククラウドはユーザー、クラウドのユースケース、ユーザーの動機を断定することができません。このように、すぐにゲストのセキュリティドメインは、パブリッククラウドプロバイダーにとっては完全に <emphasis>untrusted</emphasis> な状態となります。"
-
-#: ./doc/security-guide/ch005_security-domains.xml144(para)
-msgid ""
-"A notable difference in the attack surface of public clouds is that they "
-"must provide internet access to their services. Instance connectivity, "
-"access to files over the internet and the ability to interact with the cloud"
-" controlling fabric such as the API endpoints and dashboard are must-haves "
-"for the public cloud."
-msgstr "パブリッククラウドの攻撃対象領域での顕著な相違点は、サービスに対してインターネットアクセスを提供しなければならない点です。API エンドポイントやダッシュボードなど、インスタンスの接続性、インターネット経由でのファイルアクセス、クラウド制御のファブリックとの対話機能は、パブリッククラウドで必須アイテムなのです。"
-
-#: ./doc/security-guide/ch005_security-domains.xml145(para)
-msgid ""
-"Privacy concerns for public and private cloud users are typically "
-"diametrically opposed. The data generated and stored in private clouds is "
-"normally owned by the operator of the cloud, who is able to deploy "
-"technologies such as data loss prevention (DLP) protection, file inspection,"
-" deep packet inspection and prescriptive firewalling. In contrast, privacy "
-"is one of the primary barriers to adoption for the public cloud, as many of "
-"these controls do not exist."
-msgstr "プライバシーの課題は、パブリッククラウドのユーザーとプライベートクラウドのユーザーとでは全く正反対になっています。プライベートクラウドで生成・格納されているデータは通常、データ損失防止 (DLP)、ファイルの検査、ディープパケットインスペクション、ルールベースのファイアウォールなどの技術をデプロイ可能なクラウドのオペレーターが所有します。反対に、パブリッククラウドには上記の様な制御の多くが存在しないため、プライバシーは、パブリッククラウドを採用する際の主な障害の 1 つとなっています。"
-
-#: ./doc/security-guide/ch005_security-domains.xml148(title)
-msgid "Outbound attacks and reputational risk"
-msgstr "アウトバウンド攻撃とレピュテーションリスク"
-
-#: ./doc/security-guide/ch005_security-domains.xml149(para)
-msgid ""
-"Careful consideration should be given to potential outbound abuse from a "
-"cloud deployment. Whether public or private, clouds tend to have lots of "
-"resource available. An attacker who has established a point of presence "
-"within the cloud, either through hacking or entitled access, such as rogue "
-"employee, can bring these resources to bear against the internet at large. "
-"Clouds with Compute services make for ideal DDoS and brute force engines. "
-"The issue is more pressing for public clouds as their users are largely "
-"unaccountable, and can quickly spin up numerous disposable instances for "
-"outbound attacks. Major damage can be inflicted upon a company's reputation "
-"if it becomes known for hosting malicious software or launching attacks on "
-"other networks. Methods of prevention include egress security groups, "
-"outbound traffic inspection, customer education and awareness, and fraud and"
-" abuse mitigation strategies."
-msgstr "クラウドデプロイメントからアウトバウンド方向で起こりえる不正使用に対して、十分な配慮が必要です。パブリックでも、プライベートでも、クラウドは多くのリソースが使用出来る状態になっている傾向にあります。悪意のある従業員など、ハッキングや与えられているアクセス権限のいずれかによりクラウド内に攻撃ポイントを設定した攻撃者は、これらのリソースにインターネット全体の負荷をかけることができます。Compute サービスがあるクラウドは、理想的な DDoS や総当り攻撃エンジンを作り出します。パブリッククラウドのユーザーは多くの場合、責任を負う必要がなく、自由に使用できるインスタンスをすぐにアウトバウンドの攻撃として作り出すことができるため、パブリッククラウドにとっては、この点はより差し迫った課題でしょう。悪意のあるソフトウェアをホストしたり、他のネットワークへ攻撃していたりしたことが判明すると、企業の評判に大きな打撃を与えることでしょう。防止の方法には、egress セキュリティグループ、アウトバウンドトラフィックの検査、顧客の教育・認識、詐欺や悪用軽減戦略などがあります。"
-
-#: ./doc/security-guide/ch005_security-domains.xml168(title)
-msgid "Attack types"
-msgstr "攻撃の種類"
-
-#: ./doc/security-guide/ch005_security-domains.xml169(para)
-msgid ""
-"The diagram shows the types of attacks that may be expected from the actors "
-"described in the previous section. Note that there will always be exceptions"
-" to this diagram but in general, this describes the sorts of attack that "
-"could be typical for each actor."
-msgstr "以下の図は、前項で説明したアクターから出される可能性のある攻撃の種類を記載しています。このような図では常に例外が存在しますが、アクター毎に典型的であると考えられる攻撃の種類を一般論として記述しています。"
-
-#: ./doc/security-guide/ch005_security-domains.xml177(para)
-msgid ""
-"The prescriptive defense for each form of attack is beyond the scope of this"
-" document. The above diagram can assist you in making an informed decision "
-"about which types of threats, and threat actors, should be protected "
-"against. For commercial public cloud deployments this might include "
-"prevention against serious crime. For those deploying private clouds for "
-"government use, more stringent protective mechanisms should be in place, "
-"including carefully protected facilities and supply chains. In contrast "
-"those standing up basic development or test environments will likely require"
-" less restrictive controls (middle of the spectrum)."
-msgstr "攻撃の形式ごとの規範的な防御については、本書の対象範囲外となっています。上記の図は、対策を行うべき脅威の種類、脅威のアクターについて詳細な情報を得た状態で意思決定ができるように支援します。商業的なパブリッククラウドのデプロイに関しては重大な犯罪の防止などが含まれる場合があります。 政府で使用するプライベートクラウドをデプロイする方は、細心の注意を払って設置された対策施設やサプライチェーンなど、より厳密な保護メカニズムを設置する必要があります。反対に、基本的なデプロイメントやテスト環境を設定する方は、制御に関する制約が少なくて済むでしょう。"
-
-#: ./doc/security-guide/ch035_case-studies-networking.xml8(title)
-msgid "Case studies: Networking"
-msgstr "ケーススタディ: Networking"
-
-#: ./doc/security-guide/ch035_case-studies-networking.xml9(para)
-msgid ""
-"In this case study we discuss how Alice and Bob would address providing "
-"networking services to the user."
-msgstr "このケーススタディでは、アリスとボブがどのようにユーザに対してネットワーク提供を扱うかを議論します。"
-
-#: ./doc/security-guide/ch035_case-studies-networking.xml12(para)
-msgid ""
-"A key objective of Alice's cloud is to integrate with the existing auth "
-"services and security resources. The key design parameters for this private "
-"cloud are a limited scope of tenants, networks and workload type. This "
-"environment can be designed to limit what available network resources are "
-"available to the tenant and what are the various default quotas and security"
-" policies are available. The network policy engine can be modified to "
-"restrict creation and changes to network resources. In this environment, "
-"Alice might want to leverage nova-network in the application of security "
-"group polices on a per instance basis vs. neutron's application of security "
-"group polices on a per port basis. L2 isolation in this environment would "
-"leverage VLAN tagging. The use of VLAN tags will allow great visibility of "
-"tenant traffic by leveraging existing features and tools of the physical "
-"infrastructure."
-msgstr "アリスのクラウドの主目的は、既存の認証サービスとセキュリティリソースを用いたインテグレーションです。このプライベートクラウドのキーとなる設計パラメータは、テナント・ネットワーク・ワークロードタイプの限定されたスコープです。この環境は、どの利用可能なネットワークリソースがテナントから利用可能であり、どの様々なデフォルトクォータとセキュリティポリシーが利用可能かを制限するために設計される可能性があります。ネットワークポリシーエンジンは、ネットワークリソースの作成と変更を制限する為に修正される可能性があります。この環境では、アリスはインスタンス単位のセキュリティグループポリシーの適用における nova-network か、neutron のポートベースのセキュリティグループポリシーの適用のいずれを希望するかも知れません。この環境における L2 アイソレーションは VLAN タギングを用います。VLAN タグの利用は、物理インフラの既存の機能やツールの利用によるテナントトラフィックの素晴らしい可視性が得られます。"
-
-#: ./doc/security-guide/ch035_case-studies-networking.xml30(para)
-msgid ""
-"A major business driver for Bob is to provide an advanced networking "
-"services to his customers. Bob's customers would like to deploy multi-tiered"
-" application stacks. This multi-tiered application are either existing "
-"enterprise application or newly deployed applications. Since Bob's public "
-"cloud is a multi-tenancy enterprise service, the choice to use for L2 "
-"isolation in this environment is to use overlay networking. Another aspect "
-"of Bob's cloud is the self-service aspect where the customer can provision "
-"available networking services as needed. These networking services encompass"
-" L2 networks, L3 Routing, Network <glossterm>ACL</glossterm> and NAT. It is "
-"important that per-tenant quota's be implemented in this environment."
-msgstr "ボブの主要なビジネス目的は彼の顧客に先進的なネットワークサービスを提供する事です。ボブの顧客はマルチタイアのアプリケーションスタックをデプロイしようとしています。マルチタイアのアプリケーションは、既存の商用アプリケーションや新しくデプロイされるアプリケーションのいずれかです。ボブのパブリッククラウドはマルチテナントの商用サービスである為、この環境の L2 アイソレーションに使用する選択肢は、オーバレイネットワークです。ボブのクラウドの他の側面は、必要に応じて顧客が利用可能なネットワークサービスをプロビジョンできるセルフサービス指向です。これらのネットワークサービスは、L2 ネットワーク、L3 ルーティング、ネットワーク<glossterm>ACL</glossterm>、NAT を含みます。\n\nIt is important that per-tenant quota's be implemented in this environment."
-
-#: ./doc/security-guide/ch035_case-studies-networking.xml43(para)
-msgid ""
-"An added benefit with utilizing OpenStack Networking is when new advanced "
-"networking services become available, these new features can be easily "
-"provided to the end customers."
-msgstr "OpenStack Networking 利用の追加的な利点は、新しい先進的なネットワークサービスが利用可能になった場合、これらの新しい機能をエンドユーザに簡単に提供できる事です。"
-
-#: ./doc/security-guide/ch011_management-introduction.xml8(title)
-msgid "Management introduction"
-msgstr "管理の概要"
-
-#: ./doc/security-guide/ch011_management-introduction.xml9(para)
-msgid ""
-"A cloud deployment is a living system. Machines age and fail, software "
-"becomes outdated, vulnerabilities are discovered. When errors or omissions "
-"are made in configuration, or when software fixes must be applied, these "
-"changes must be made in a secure, but convenient, fashion. These changes are"
-" typically solved through configuration management."
-msgstr "クラウドデプロイメントは生きているシステムです。機械は老朽化して障害が発生し、ソフトウェアは古くなり、脆弱性が発見されます。設定にエラーや抜けがあった場合、ソフトウェアの修正を適用する必要が出た場合、セキュアかつ利便的に、これらの変更を加える必要があります。通常、これらの変更は構成管理などで解決されます。"
-
-#: ./doc/security-guide/ch011_management-introduction.xml10(para)
-msgid ""
-"Likewise, it is important to protect the cloud deployment from being "
-"configured or manipulated by malicious entities. With many systems in a "
-"cloud employing compute and networking virtualization, there are distinct "
-"challenges applicable to OpenStack which must be addressed through integrity"
-" lifecycle management."
-msgstr "同様に、悪意のある組織により設定または操作されないように、クラウドデプロイメントを保護することが重要です。コンピュートやネットワークの仮想化を採用するクラウド内の多くのシステムでは、OpenStack に適用される問題が明らかに存在し、整合性のライフサイクル管理で対応していく必要があります。"
-
-#: ./doc/security-guide/ch011_management-introduction.xml11(para)
-msgid ""
-"Finally, administrators must perform command and control over the cloud for "
-"various operational functions. It is important these command and control "
-"facilities are understood and secured."
-msgstr "最後に、管理者は様々なオペレーション機能に対してクラウド上で指揮統制を行う必要があります。これらの指揮統制機能を理解、確保することが重要です。"
-
-#: ./doc/security-guide/ch049_case-studies-tenant-data.xml8(title)
-msgid "Case studies: tenant data"
-msgstr "ケーススタディ: テナントデータ"
-
-#: ./doc/security-guide/ch049_case-studies-tenant-data.xml9(para)
-msgid ""
-"Returning to Alice and Bob, we will use this section to dive into their "
-"particular tenant data privacy requirements. Specifically, we will look into"
-" how Alice and Bob both handle tenant data, data destruction, and data "
-"encryption."
-msgstr "アリスとボブの話に戻ると、このセクションでは、彼らの特定のテナントのデータのプライバシー要件についてより詳細に説明します。具体的には、アリスとボブの両者がテナントのデータ、データの破壊、データの暗号化をどのように対処するかを見てみます。"
-
-#: ./doc/security-guide/ch049_case-studies-tenant-data.xml18(para)
-msgid ""
-"As stated during the introduction to Alice's case study, data protection is "
-"of an extremely high priority. She needs to ensure that a compromise of one "
-"tenant's data does not cause loss of other tenant data. She also has strong "
-"regulator requirements that require documentation of data destruction "
-"activities. Alice does this using the following:"
-msgstr "アリスのケーススタディで説明したように、データ保護は非常に重要です。アリスは、あるテナントのデータの情報漏洩が、他のテナントデータの損害を引き起こさないように、保証することが必要です。アリスはまた、データ破壊の文書化を必要とする強い規制上の要件を持っています。アリスは、以下の方法でこれを提供します："
-
-#: ./doc/security-guide/ch049_case-studies-tenant-data.xml28(para)
-msgid ""
-"Establishing procedures to sanitize tenant data when a program or project "
-"ends."
-msgstr "プログラムやプロジェクトが終了する際に、好ましくないテナントデータを削除するための手順を確立すること。"
-
-#: ./doc/security-guide/ch049_case-studies-tenant-data.xml32(para)
-msgid ""
-"Track the destruction of both the tenant data and metadata through ticketing"
-" in a CMDB."
-msgstr "CMDBのチケット発行を使用して、顧客データとメタデータの両方の破壊を追跡する。"
-
-#: ./doc/security-guide/ch049_case-studies-tenant-data.xml35(para)
-#: ./doc/security-guide/ch049_case-studies-tenant-data.xml69(para)
-msgid "For Volume storage:"
-msgstr "ボリュームストレージ"
-
-#: ./doc/security-guide/ch049_case-studies-tenant-data.xml38(para)
-#: ./doc/security-guide/ch049_case-studies-tenant-data.xml72(para)
-msgid "Physical server issues"
-msgstr "物理サーバーの問題"
-
-#: ./doc/security-guide/ch049_case-studies-tenant-data.xml41(para)
-msgid ""
-"To provide secure ephemeral instance storage, Alice implements qcow2 files "
-"on an encrypted filesystem."
-msgstr "安全な一時ディスクを提供するために、アリスは暗号化ファイルシステム上に qcow2 のファイルを実装しています。"
-
-#: ./doc/security-guide/ch049_case-studies-tenant-data.xml51(para)
-msgid ""
-"As stated during the introduction to Bob's case study, tenant privacy is of "
-"an extremely high priority. In addition to the requirements and actions Bob "
-"will take to isolate tenants from one another at the infrastructure layer, "
-"Bob also needs to provide assurances for tenant data privacy. Bob does this "
-"using the following:"
-msgstr "ボブのケーススタディの最初で説明したように、テナントのプライバシーは非常に重要です。ボブはインフラレイヤーで相互にテナントを分離する要件およびアクションに加えて、ボブはまたテナントデータのプライバシーを保する必要があります。 ボブは以下を用いて、これを提供します："
-
-#: ./doc/security-guide/ch049_case-studies-tenant-data.xml61(para)
-msgid ""
-"Establishing procedures to sanitize customer data when a customer churns."
-msgstr "顧客が不適切な顧客データを大量生産する時に、削除するための手順を確立する。"
-
-#: ./doc/security-guide/ch049_case-studies-tenant-data.xml65(para)
-msgid ""
-"Track the destruction of both the customer data and metadata through "
-"ticketing in a CMDB."
-msgstr "CMDBのチケット発行を使用して、顧客データとメタデータの両方の破壊を追跡します。"
-
-#: ./doc/security-guide/ch049_case-studies-tenant-data.xml75(para)
-msgid ""
-"To provide secure ephemeral instance storage, Bob implements qcow2 files on "
-"an encrypted filesystems."
-msgstr "安全な一時ディスクを提供するために、ボブは暗号化ファイルシステム上に qcow2 のファイルを実装しています。"
-
-#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml8(title)
-msgid "Case studies: instance isolation"
-msgstr "ケーススタディ：インスタンス分離"
-
-#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml9(para)
-msgid ""
-"In this case study we discuss how Alice and Bob would ensure that their "
-"instances are properly isolated. First we consider hypervisor selection, and"
-" then techniques for hardening QEMU and applying mandatory access controls."
-msgstr "このケーススタディでは、アリスとボブが所有するインスタンスが正しく分離されていることを確認する方法について説明します。まずはハイパーバイザーの選択とQEMUの強化、強制アクセスコントロールの適用について検討します。"
-
-#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml12(para)
-msgid ""
-"Alice chooses Xen for the hypervisor in her cloud due to a strong internal "
-"knowledge base and a desire to use the Xen security modules (XSM) for fine-"
-"grained policy enforcement."
-msgstr "アリスは豊富な知識を持っている上、細かいポリシー強制のためにXen security module(XSM)を採用したいため、Xenをハイパーバイザーに選択します。"
-
-#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml13(para)
-msgid ""
-"Alice is willing to apply a relatively large amount of resources to software"
-" packaging and maintenance. She will use these resources to build a highly "
-"customized version of QEMU that has many components removed, thereby "
-"reducing the attack surface. She will also ensure that all compiler "
-"hardening options are enabled for QEMU. Alice accepts that these decisions "
-"will increase long-term maintenance costs."
-msgstr "アリスはソフトウェアパッケージングとメンテナンスにそれなりのリソースを割り当てる予定です。これらのリソースを活用し、QEMUから多数コンポーネントを取り除くなど大幅カスタマイズをします。コンポーネントを取り除くことで、攻撃可能な部分は削減されます。また、QEMUのコンパイラ強化オプションがすべて有効になっていることも確認します。長期メンテナンスコストが増えてしまうことを理解した上でこれらの作業や設定を選択しています。"
-
-#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml14(para)
-msgid ""
-"Alice writes XSM policies (for Xen) and SELinux policies (for Linux domain "
-"0, and device domains) to provide stronger isolation between the instances. "
-"Alice also uses the Intel TXT support in Xen to measure the hypervisor "
-"launch in the TPM."
-msgstr "インスタンス間の分離を強めるため、アリスはXSMポリシー(Xen向け)とSELinuxポリシー(Linux domain0とデバイスドメイン向け)を作成しています。また、TPMのハイパーバイザーの起動を計測するためにXenに含まれるIntel TXTサポートを採用しています。"
-
-#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml18(para)
-msgid ""
-"Bob is very concerned about instance isolation since the users in a public "
-"cloud represent anyone with a credit card, meaning they are inherently "
-"untrusted. Bob has just started hiring the team that will deploy the cloud, "
-"so he can tailor his candidate search for specific areas of expertise. With "
-"this in mind, Bob chooses a hypervisor based on its technical features, "
-"certifications, and community support. KVM has an EAL 4+ common criteria "
-"rating, with a labeled security protection profile (LSPP) to provide added "
-"assurance for instance isolation. This, combined with the strong support for"
-" KVM within the OpenStack community drives Bob's decision to use KVM."
-msgstr "パブリッククラウドではクレジットカードを所持していればユーザーになれるため、本質的に信頼性が低いことからボブはインスタンス分離に非常に気を遣っています。ボブはクラウドを配備するチームのメンバーの採用を開始したばかりなので、メンバー候補の検索条件として任意の特定スキルを指定できます。それを踏まえ、ボブは技術的な特徴、所持する証明等、コミュニティサポートを基準にハイパーバイザーを選択します。KVMはEAL 4+共通項目評価とラベル化されたセキュリティ保護プロフィール(LSPP)によってインスタンス分離を保証しています。これらの強みとOpenStackコミュニティのKVMへの豊富なサポートを総合して考えた結果、ボブはKVMを採用することにします。"
-
-#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml19(para)
-msgid ""
-"Bob weighs the added cost of repackaging QEMU and decides that he cannot "
-"commit those resources to the project. Fortunately, his Linux distribution "
-"has already enabled the compiler hardening options. So he decides to use "
-"this QEMU package. Finally, Bob leverages sVirt to manage the SELinux "
-"polices associated with the virtualization stack."
-msgstr "ボブはQEMUを再パッケージするために発生するコストを検討し、そのためのリソースをプロジェクトに割くことはできないと判断します。幸い、彼の使用しているLinuxのディストリビューションではコンパイラ強化オプションが有効になっているため、そのQEMUパッケージを採用します。最後に、仮想スタックに関わるSELinuxポリシーを管理するためにsVirtを利用します。"
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml12(title)
-msgid "Networking services security best practices"
-msgstr "Networking サービス セキュリティベストプラクティス"
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml13(para)
-msgid ""
-"This section discusses OpenStack Networking configuration best practices as "
-"they apply to tenant network security within your OpenStack deployment."
-msgstr "この章では、あなたの OpenStack デプロイの中でテナントネットワークセキュリティを適用する為に、OpenStack Networking の設定のベストプラクティスについて議論します。"
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml15(title)
-msgid "Tenant network services workflow"
-msgstr "テナントネットワークサービスのワークフロー"
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml16(para)
-msgid ""
-"OpenStack Networking provides users real self services of network resources "
-"and configurations. It is important that cloud architects and operators "
-"evaluate their design use cases in providing users the ability to create, "
-"update, and destroy available network resources."
-msgstr "OpenStack Networking は、ネットワークリソースと設定の本物のセルフサービスをユーザに提供します。クラウドアーキテクトとオペレータが、利用可能なネットワークリソースの作成・更新・削除機能をユーザに提供する際の彼らの設計ユースケースを評価する事は重要です。"
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml19(title)
-msgid "Networking resource policy engine"
-msgstr "Networking リソースポリシーエンジン"
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml20(para)
-msgid ""
-"A policy engine and its configuration file, "
-"<filename>policy.json</filename>, within OpenStack Networking provides a "
-"method to provide finer grained authorization of users on tenant networking "
-"methods and objects. It is important that cloud architects and operators "
-"evaluate their design and use cases in providing users and tenants the "
-"ability to create, update, and destroy available network resources as it has"
-" a tangible effect on tenant network availability, network security, and "
-"overall OpenStack security. For a more detailed explanation of OpenStack "
-"Networking policy definition, please refer to the <link "
-"href=\"http://docs.openstack.org/admin-guide-"
-"cloud/content/section_networking_auth.html\">Authentication and "
-"authorization section</link> in the <citetitle>OpenStack Cloud Administrator"
-" Guide</citetitle>."
-msgstr "OpenStack Networking 中のポリシーエンジンとその設定ファイル（<filename>policy.json</filename>）は、テナントネットワークメソッドとオブジェクト上のユーザのきめ細かな許可を提供する方法を提供します。クラウドアーキテクトとオペレータが、ユーザとテナントに利用可能なネットワークリソースを作成・交信・削除する機能を提供するにあたって、かれらの設計とユースケースを評価する事は重要です。なぜなら、テナントネットワークの可用性、ネットワークセキュリティ、全般的な OpenStack セキュリティ上でこれらが実際の効果を持つからです。OpenStack Networking ポリシー定義のより詳細な説明は、<citetitle>OpenStack クラウド管理者ガイド</citetitle> 中の <link href=\"http://docs.openstack.org/admin-guide-cloud/content/section_networking_auth.html\">認証と認可の章</link>を参照して下さい。"
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml34(para)
-msgid ""
-"It is important to review the default networking resource policy and modify "
-"the policy appropriately for your security posture."
-msgstr "デフォルトの Networking リソースポリシーをレビューする事と、あなたのセキュリティ姿勢に向けてポリシーを適切に修正する事は重要です。"
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml37(para)
-msgid ""
-"If your deployment of OpenStack provides multiple external access points "
-"into different security domains it is important that you limit the tenant's "
-"ability to attach multiple vNICs to multiple external access pointsthis "
-"would bridge these security domains and could lead to unforeseen security "
-"compromise. It is possible mitigate this risk by utilizing the host "
-"aggregates functionality provided by OpenStack Compute or through splitting "
-"the tenant VMs into multiple tenant projects with different virtual network "
-"configurations."
-msgstr "あなたの OpenStack のデプロイが異なるセキュリティドメインに向けて複数の外部アクセスポイントを提供する場合、複数の外部アクセスポイントへ複数の仮想NICをアタッチするテナントの機能を制限する事は重要です。これは、これらのセキュリティドメインのブリッジになり、思いがけないセキュリティの妥協を導くかも知れません。OpenStack Compute が提供するホストアグリゲート機能の活用や、異なる仮想ネットワーク設定を持つ複数のテナントプロジェクトにテナントVMを分割する事で、リスクを緩和する事が可能です。"
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml48(title)
-msgid "Security groups"
-msgstr "セキュリティグループ"
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml49(para)
-msgid ""
-"The OpenStack Networking Service provides security group functionality using"
-" a mechanism that is more flexible and powerful than the security group "
-"capabilities built into OpenStack Compute. Thus, when using OpenStack "
-"Networking, <filename>nova.conf</filename> should always disable built-in "
-"security groups and proxy all security group calls to the OpenStack "
-"Networking API. Failure to do so will result in conflicting security "
-"policies being simultaneously applied by both services. To proxy security "
-"groups to OpenStack Networking, use the following configuration values:"
-msgstr "OpenStack Networking サービスは、OpenStack Compute 上に構築されたセキュリティグループ機能より柔軟で協力な機能を用いたセキュリティグループ機能を提供します。このように、OpenStack Networking を用いる場合、<filename>nova.conf</filename> は常にビルトインのセキュリティグループを無効化し、全てのセキュリティグループ要求を OpenStack Networking API にプロキシする必要があります。これを怠った場合、セキュリティポリシーが両サービスに同時に適用されて衝突を起こす結果となります。OpenStack Networking にセキュリティグループをプロキシする為に、以下の設定値を用いて下さい。"
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml61(para)
-msgid ""
-"<option>firewall_driver</option> must be set to "
-"<literal>nova.virt.firewall.NoopFirewallDriver</literal> so that <systemitem"
-" class=\"service\">nova-compute</systemitem> does not perform iptables-based"
-" filtering itself."
-msgstr "<option>firewall_driver</option> は、<systemitem class=\"service\">nova-compute</systemitem> が自身で iptables ベースのフィルタリングを実行しないよう、<literal>nova.virt.firewall.NoopFirewallDriver</literal> に設定しなければなりません。"
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml67(para)
-msgid ""
-"<option>security_group_api</option> must be set to "
-"<literal>neutron</literal> so that all security group requests are proxied "
-"to the OpenStack Networking service."
-msgstr "<option>security_group_api</option> は、全てのセキュリティグループ要求が OpenStack Networking サービスを経由するよう、<literal>neutron</literal> に設定しなければなりません。"
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml73(para)
-msgid ""
-"Security groups and security group rules allow administrators and tenants "
-"the ability to specify the type of traffic and direction (ingress/egress) "
-"that is allowed to pass through a virtual interface port. A security group "
-"is a container for security group rules. When a virtual interface port is "
-"created in OpenStack Networking it is associated with a security group. If a"
-" security group is not specified, the port will be associated with a "
-"'default' security group. By default this group will drop all ingress "
-"traffic and allow all egress. Rules can be added to this group in order to "
-"change the behaviour."
-msgstr "セキュリティグループとセキュリティグループルールは、管理者とテナントが仮想インターフェースポートの通過を許可する通信のタイプと通信方向 (内向き／外向き) を指定できるようにしています。セキュリティグループはセキュリティグループルールの入れ物です。OpenStack Networking 中で仮想インターフェースポートが作成された場合、ポートはセキュリティグループに紐付けられます。セキュリティグループが指定されない場合、ポートは「default」セキュリティグループに紐付けられます。デフォルトでは、このグループは内向きの通信を全てドロップし、外向きの通信を全て許可します。挙動を変える為に、このグループにルールを追加する事が出来ます。"
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml74(para)
-msgid ""
-"When using the security group API through OpenStack Compute, security groups"
-" are applied to all virtual interface ports on an instance. The reason for "
-"this is that OpenStack Compute security group APIs are instance based and "
-"not virtual interface port based as OpenStack Networking."
-msgstr "OpenStack Compute のセキュリティグループ API を使用する場合、セキュリティグループは１インスタンス上の全仮想インターフェースポートに適用されます。この理由は、OpenStack Compute のセキュリティグループ API がインスタンスベースであり、OpenStack Networking のような仮想インターフェースポートベースではないからです。"
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml77(title)
-msgid "Quotas"
-msgstr "クォータ"
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml79(para)
-msgid ""
-"Quotas provide the ability to limit the number of network resources "
-"available to tenants. You can enforce default quotas for all tenants. The "
-"<filename>/etc/neutron/neutron.conf</filename> includes these options for "
-"quota:"
-msgstr "クォータは、テナントに対して利用可能なネットワークリソース数を制限する機能を提供します。全てのテナントに対してデフォルトのクォータを強制する事が出来ます。<filename>/etc/neutron/neutron.conf</filename> にクォータに関するこれらのオプションがあります。"
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml108(para)
-msgid ""
-"OpenStack Networking also supports per-tenant quotas limit through a quota "
-"extension API. To enable per-tenant quotas, you must set the "
-"<literal>quota_driver</literal> option in <filename>neutron.conf</filename>."
-msgstr "OpenStack Networking はまた、クォータ拡張 API 経由で、テナント単位のクォータをサポートしています。テナント単位クォータを有効にするためには、<filename>neutron.conf</filename> 中の <literal>quota_driver</literal> を設定する必要があります。"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch052_devices.xml305(None)
-#: ./doc/security-guide/ch052_devices.xml309(None)
-msgid ""
-"@@image: 'static/sVirt Diagram 1.png'; md5=ffcdbb45d9054670ad4c270a7c7d3925"
-msgstr "@@image: 'static/sVirt Diagram 1.png'; md5=ffcdbb45d9054670ad4c270a7c7d3925"
-
-#: ./doc/security-guide/ch052_devices.xml12(title)
-msgid "Hardening the virtualization layers"
-msgstr "仮想化層のセキュリティ強化"
-
-#: ./doc/security-guide/ch052_devices.xml13(para)
-msgid ""
-"In the beginning of this chapter we discuss the use of both physical and "
-"virtual hardware by instances, the associated security risks, and some "
-"recommendations for mitigating those risks. We conclude the chapter with a "
-"discussion of sVirt, an open source project for integrating SELinux "
-"mandatory access controls with the virtualization components."
-msgstr "本章の初めに、インスタンスによる物理ハードウェアと仮想ハードウェアの両方の使用、関連するセキュリティリスク、それらのリスクを軽減するためのいくつかの推奨事項について議論します。SELinux 強制アクセス制御を仮想化コンポーネントと統合するためのオープンソースプロジェクトである sVirt の議論で本章を終わります。"
-
-#: ./doc/security-guide/ch052_devices.xml21(title)
-msgid "Physical hardware (PCI passthrough)"
-msgstr "物理ハードウェア (PCI パススルー)"
-
-#: ./doc/security-guide/ch052_devices.xml22(para)
-msgid ""
-"Many hypervisors offer a functionality known as PCI passthrough. This allows"
-" an instance to have direct access to a piece of hardware on the node. For "
-"example, this could be used to allow instances to access video cards "
-"offering the compute unified device architecture (CUDA) for high performance"
-" computation. This feature carries two types of security risks: direct "
-"memory access and hardware infection."
-msgstr "多くのハイパーバイザーは PCI パススルーとして知られる機能を提供します。これにより、インスタンスがノードにあるハードウェアの一部に直接アクセスできます。例えば、インスタンスがハイパフォーマンスコンピューティング用の compute unified device architecture (CUDA) を提供するビデオカードにアクセスするために使用されます。この機能は 2 種類のセキュリティリスクをもたらします。ダイレクトメモリアクセスとハードウェア感染です。"
-
-#: ./doc/security-guide/ch052_devices.xml31(para)
-msgid ""
-"Direct memory access (DMA) is a feature that permits certain hardware "
-"devices to access arbitrary physical memory addresses in the host computer. "
-"Often video cards have this capability. However, an instance should not be "
-"given arbitrary physical memory access because this would give it full view "
-"of both the host system and other instances running on the same node. "
-"Hardware vendors use an input/output memory management unit (IOMMU) to "
-"manage DMA access in these situations. Therefore, cloud architects should "
-"ensure that the hypervisor is configured to utilize this hardware feature."
-msgstr "ダイレクトメモリアクセス (DMA) は、特定のハードウェアがホストコンピューターで任意の物理メモリアドレスにアクセスできる機能です。ビデオカードはときどきこの機能を有しています。しかしながら、インスタンスは指定された任意の物理メモリアクセスをすべきではありません。なぜなら、これはホストシステムと同じノードで実行している他のインスタンスを完全に表示できるかもしれないからです。ハードウェアベンダーはこれらの状況で DMA アクセスを管理するために input/output memory management unit (IOMMU) を使用します。そのため、クラウドアーキテクトは、ハイパーバイザーがこのハードウェア機能を使用するよう設定されていることを確実にすべきです。"
-
-#: ./doc/security-guide/ch052_devices.xml45(para)
-msgid ""
-"KVM: <link href=\"http://www.linux-kvm.org/page"
-"/How_to_assign_devices_with_VT-d_in_KVM\">How to assign devices with VT-d in"
-" KVM</link>"
-msgstr "KVM: <link href=\"http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM\">How to assign devices with VT-d in KVM</link>"
-
-#: ./doc/security-guide/ch052_devices.xml50(para)
-msgid "Xen: <link href=\"http://wiki.xen.org/wiki/VTd_HowTo\">VTd Howto</link>"
-msgstr "Xen: <link href=\"http://wiki.xen.org/wiki/VTd_HowTo\">VTd Howto</link>"
-
-#: ./doc/security-guide/ch052_devices.xml55(para)
-msgid "The IOMMU feature is marketed as VT-d by Intel and AMD-Vi by AMD."
-msgstr "IOMMU 機能は、Intel により VT-d、AMD により AMD-Vi として提供されています。"
-
-#: ./doc/security-guide/ch052_devices.xml59(para)
-msgid ""
-"A hardware infection occurs when an instance makes a malicious modification "
-"to the firmware or some other part of a device. As this device is used by "
-"other instances, or even the host OS, the malicious code can spread into "
-"these systems. The end result is that one instance can run code outside of "
-"its security domain. This is a potential problem in any hardware sharing "
-"scenario. The problem is specific to this scenario because it is harder to "
-"reset the state of physical hardware than virtual hardware."
-msgstr "ハードウェア感染は、インスタンスが悪意のある変更をファームウェアやデバイスの他の部分に行うときに発生します。このデバイスは他のインスタンス、またはホスト OS により使用されるため、悪意のあるコードはこれらのシステムの中に拡散する可能性があります。最終的な結果として、あるインスタンスがセキュリティドメインの範囲外で実行できます。これは何らかのハードウェアを共有している状況における潜在的な問題です。仮想ハードウェアよりも物理ハードウェアの状態をリセットすることが難しいため、この問題はこの状況に特有のものです。"
-
-#: ./doc/security-guide/ch052_devices.xml69(para)
-msgid ""
-"Solutions to the hardware infection problem are domain specific. The "
-"strategy is to identify how an instance can modify hardware state then "
-"determine how to reset any modifications when the instance is done using the"
-" hardware. For example, one option could be to re-flash the firmware after "
-"use. Clearly there is a need to balance hardware longevity with security as "
-"some firmwares will fail after a large number of writes. TPM technology, "
-"described in <xref linkend=\"ch013_node-bootstrapping-idp44768\"/>, provides"
-" a solution for detecting unauthorized firmware changes. Regardless of the "
-"strategy selected, it is important to understand the risks associated with "
-"this kind of hardware sharing so that they can be properly mitigated for a "
-"given deployment scenario."
-msgstr "ハードウェア感染問題の解決策はドメイン固有です。戦略はインスタンスがどのようにしてハードウェア状態を修正可能かを特定する事、その後インスタンスがハードウェアを使用している際に修正をリセットする方法を検知する事です。例えば、使用後のファームウェアの再度フラッシュが挙げられます。明らかに、いくつかのファームウェアは多数の書き込み後に故障するので、上記の作業はハードウェア寿命とセキュリティを天秤にかける必要があります。TPM 技術（<xref linkend=\"ch013_node-bootstrapping-idp44768\"/>で説明）は未承認のファームウェア変更を検知する解決策を提供します。選択した戦略に関わらず、この種のハードウェア共有に関するリスクを理解する事は、与えられたデプロイシナリオ用に適切にリスクを軽減する上で重要です。"
-
-#: ./doc/security-guide/ch052_devices.xml85(para)
-msgid ""
-"Additionally, due to the risk and complexities associated with PCI "
-"passthrough, it should be disabled by default. If enabled for a specific "
-"need, you will need to have appropriate processes in place to ensure the "
-"hardware is clean before re-issue."
-msgstr "加えて、PCI パススルーに関連したリスクと複雑性のため、これはデフォルトで無効化されるべきです。特定の用途のために有効化する場合、ハードウェアが再発行される前に確実にクリアするために、適切なプロセスを実行する必要があります。"
-
-#: ./doc/security-guide/ch052_devices.xml93(title)
-msgid "Virtual hardware (QEMU)"
-msgstr "仮想ハードウェア (QEMU)"
-
-#: ./doc/security-guide/ch052_devices.xml94(para)
-msgid ""
-"When running a virtual machine, virtual hardware is a software layer that "
-"provides the hardware interface for the virtual machine. Instances use this "
-"functionality to provide network, storage, video, and other devices that may"
-" be needed. With this in mind, most instances in your environment will "
-"exclusively use virtual hardware, with a minority that will require direct "
-"hardware access. The major open source hypervisors use QEMU for this "
-"functionality. While QEMU fills an important need for virtualization "
-"platforms, it has proven to be a very challenging software project to write "
-"and maintain. Much of the functionality in QEMU is implemented with low-"
-"level code that is difficult for most developers to comprehend. Furthermore,"
-" the hardware virtualized by QEMU includes many legacy devices that have "
-"their own set of quirks. Putting all of this together, QEMU has been the "
-"source of many security problems, including hypervisor breakout attacks."
-msgstr "仮想マシンの実行時、仮想ハードウェアは仮想マシンにハードウェアインターフェースを提供するソフトウェア層です。インスタンスは必要となるネットワーク、ストレージ、ビデオ、他のデバイスを提供するためにこの機能を使用します。これで覚えておくことは、お使いのほとんどのインスタンスは排他的に仮想ハードウェアを使用することです。一部はハードウェアに直接アクセスする必要があります。主要なオープンソースのハイパーバイザーはこの機能のために QEMU を使用します。QEMU は仮想化プラットフォームのニーズを満たしますが、作成と維持することが非常に挑戦的なソフトウェアプロジェクトであるとわかってきました。QEMU の機能のほとんどは、多くの開発者が理解しにくい低レベルなコードで実装されています。さらに、QEMU により仮想化されるハードウェアには、独自の癖を持つレガシーデバイスが数多くあります。これを一括りにするので、QEMU はハイパーバイザー突破攻撃を含む多くのセキュリティ問題の元になってきました。"
-
-#: ./doc/security-guide/ch052_devices.xml112(para)
-msgid ""
-"For the reasons stated above, it is important to take proactive steps to "
-"harden QEMU. We recommend three specific steps: minimizing the code base, "
-"using compiler hardening, and using mandatory access controls, such as "
-"sVirt, SELinux, or AppArmor."
-msgstr "上記の理由として、QEMU 堅牢化の率先したステップの実行が重要である事が挙げられます。我々は３つの特定のステップを推奨しています。コードベースの最小化、コンパイラーの堅牢化、sVirt・SELinux・AppArmor 等の強制アクセス制御の使用です。"
-
-#: ./doc/security-guide/ch052_devices.xml119(title)
-msgid "Minimizing the QEMU code base"
-msgstr "QEMU コードベースの最小化"
-
-#: ./doc/security-guide/ch052_devices.xml120(para)
-msgid ""
-"One classic security principle is to remove any unused components from your "
-"system. QEMU provides support for many different virtual hardware devices. "
-"However, only a small number of devices are needed for a given instance. "
-"Most instances will use the virtio devices. However, some legacy instances "
-"will need access to specific hardware, which can be specified using glance "
-"metadata:"
-msgstr "古くからある 1 つのセキュリティ原則は、システムから未使用のコンポーネントを削除することです。QEMU はさまざまな種類の仮想ハードウェアデバイスをサポートします。しかしながら、少しのデバイスだけが指定されたインスタンスに必要になります。多くのインスタンスは virtio デバイスを使用します。しかし、いくつかのレガシーなインスタンスは、glance メタデータを使用して指定できる、特定のハードウェアにアクセスする必要があります。"
-
-#: ./doc/security-guide/ch052_devices.xml133(para)
-msgid ""
-"A cloud architect should decide what devices to make available to cloud "
-"users. Anything that is not needed should be removed from QEMU. This step "
-"requires recompiling QEMU after modifying the options passed to the QEMU "
-"configure script. For a complete list of up-to-date options simply run "
-"<placeholder-1/> from within the QEMU source directory. Decide what is "
-"needed for your deployment, and disable the remaining options."
-msgstr "クラウドアーキテクトは、どのデバイスがクラウドユーザーに利用可能であるかを判断すべきです。必要ないすべてのデバイスは QEMU から削除すべきです。この手順は、QEMU 設定スクリプトに渡されるオプションを変更した後で、QEMU を再コンパイルする必要があります。最新の完全なオプション一覧は、QEMU ソースディレクトリの中で <placeholder-1/> を単に実行します。お使いの環境に必要なものを判断し、残りのオプションを無効化します。"
-
-#: ./doc/security-guide/ch052_devices.xml144(title)
-msgid "Compiler hardening"
-msgstr "コンパイラーのセキュリティ強化機能"
-
-#: ./doc/security-guide/ch052_devices.xml145(para)
-msgid ""
-"The next step is to harden QEMU using compiler hardening options. Modern "
-"compilers provide a variety of compile time options to improve the security "
-"of the resulting binaries. These features, which we will describe in more "
-"detail below, include relocation read-only (RELRO), stack canaries, never "
-"execute (NX), position independent executable (PIE), and address space "
-"layout randomization (ASLR)."
-msgstr "次の手順は、コンパイラーのセキュリティ強化オプションを使用して QEMU をセキュリティ強化することです。最近のコンパイラーは、出力バイナリのセキュリティを改善するために、さまざまなコンパイル時オプションを提供します。これらの機能には、より詳細を以下で説明しますが、relocation read-only (RELRO)、Stack Canaries、never execute (NX)、position independent executable (PIE)、address space layout randomization (ASLR) があります。"
-
-#: ./doc/security-guide/ch052_devices.xml154(para)
-msgid ""
-"Many modern linux distributions already build QEMU with compiler hardening "
-"enabled, so you may want to verify your existing executable before "
-"proceeding with the information below. One tool that can assist you with "
-"this verification is called <link "
-"href=\"http://www.trapkit.de/tools/checksec.html\"><literal>checksec.sh</literal></link>."
-msgstr "ほとんどの最近の Linux ディストリビューションは、すでにコンパイラーのセキュリティ強化を有効化して QEMU をビルドしています。そのため、以下の情報を続ける前に、既存のバイナリを確認したいでしょう。この確認を手助けできるツールの 1 つは <link href=\"http://www.trapkit.de/tools/checksec.html\"><literal>checksec.sh</literal></link> と呼ばれます。"
-
-#: ./doc/security-guide/ch052_devices.xml163(term)
-msgid "RELocation Read-Only (RELRO)"
-msgstr "RELocation Read-Only (RELRO)"
-
-#: ./doc/security-guide/ch052_devices.xml165(para)
-msgid ""
-"Hardens the data sections of an executable. Both full and partial RELRO "
-"modes are supported by gcc. For QEMU full RELRO is your best choice. This "
-"will make the global offset table read-only and place various internal data "
-"sections before the program data section in the resulting executable."
-msgstr "実行ファイルのデータ部分をセキュリティ強化します。全体 RELRO モードと部分 RELRO モードが gcc によりサポートされます。QEMU 完全 RELRO が最善の選択肢です。これにより、グローバルオフセットテーブルが読み込み専用になり、出力実行ファイルのプログラムデータセクションの前にさまざまな内部データ部分が置かれます。"
-
-#: ./doc/security-guide/ch052_devices.xml175(term)
-msgid "Stack canaries"
-msgstr "スタックカナリア"
-
-#: ./doc/security-guide/ch052_devices.xml177(para)
-msgid ""
-"Places values on the stack and verifies their presence to help prevent "
-"buffer overflow attacks."
-msgstr "バッファーオーバーフロー攻撃を防ぐ役に立てるために、スタックに値を置き、それらの存在を検証します。"
-
-#: ./doc/security-guide/ch052_devices.xml183(term)
-msgid "Never eXecute (NX)"
-msgstr "Never eXecute (NX)"
-
-#: ./doc/security-guide/ch052_devices.xml185(para)
-msgid ""
-"Also known as Data Execution Prevention (DEP), ensures that data sections of"
-" the executable can not be executed."
-msgstr "Data Execution Prevention (DEP) としても知られています。実行ファイルのデータ部分を必ず実行できなくします。"
-
-#: ./doc/security-guide/ch052_devices.xml192(term)
-msgid "Position Independent Executable (PIE)"
-msgstr "Position Independent Executable (PIE)"
-
-#: ./doc/security-guide/ch052_devices.xml194(para)
-msgid ""
-"Produces a position independent executable, which is necessary for ASLR."
-msgstr "位置に依存しない実行ファイルを生成します。ASLR のために必要です。"
-
-#: ./doc/security-guide/ch052_devices.xml200(term)
-msgid "Address Space Layout Randomization (ASLR)"
-msgstr "Address Space Layout Randomization (ASLR)"
-
-#: ./doc/security-guide/ch052_devices.xml202(para)
-msgid ""
-"This ensures that placement of both code and data regions will be "
-"randomized. Enabled by the kernel (all modern linux kernels support ASLR), "
-"when the executable is built with PIE."
-msgstr "コード領域とデータ領域の配置を確実にランダム化します。実行ファイルが PIE を用いてビルドされるとき、カーネルにより有効化されます (最近の Linux カーネルはすべて ASLR をサポートします)。"
-
-#: ./doc/security-guide/ch052_devices.xml210(para)
-msgid ""
-"Putting this all together, and adding in some additional useful protections,"
-" we recommend the following compiler options for GCC when compiling QEMU:"
-msgstr "すべてを一緒に利用し、いくつか追加の有用な保護を追加して、QEMU コンパイル時に以下の GCC コンパイラーオプションを推奨します。"
-
-#: ./doc/security-guide/ch052_devices.xml217(para)
-msgid ""
-"We recommend testing your QEMU executable file after it is compiled to "
-"ensure that the compiler hardening worked properly."
-msgstr "コンパイラーが確実に適切なセキュリティ強化を動作させるようコンパイルした後で、お使いの QEMU 実行ファイルをテストすることを推奨します。"
-
-#: ./doc/security-guide/ch052_devices.xml221(para)
-msgid ""
-"Most cloud deployments will not want to build software such as QEMU by hand."
-" It is better to use packaging to ensure that the process is repeatable and "
-"to ensure that the end result can be easily deployed throughout the cloud. "
-"The references below provide some additional details on applying compiler "
-"hardening options to existing packages."
-msgstr "ほとんどのクラウド環境は QEMU のようなソフトウェアを手動でビルドしたくないでしょう。プロセスが確実に繰り返し可能であり、最終結果を簡単にクラウドにデプロイできるようにするために、パッケージを使用するほうが良いでしょう。以下の参考情報は、既存のパッケージにコンパイラーのセキュリティ強化オプションを適用することの詳細を提供します。"
-
-#: ./doc/security-guide/ch052_devices.xml230(para)
-msgid ""
-"DEB packages: <link "
-"href=\"http://wiki.debian.org/HardeningWalkthrough\">Hardening "
-"Walkthrough</link>"
-msgstr "DEB パッケージ: <link href=\"http://wiki.debian.org/HardeningWalkthrough\">Hardening Walkthrough</link>"
-
-#: ./doc/security-guide/ch052_devices.xml233(para)
-msgid ""
-"RPM packages: <link "
-"href=\"http://fedoraproject.org/wiki/How_to_create_an_RPM_package\">How to "
-"create an RPM package</link>"
-msgstr "RPM パッケージ: <link href=\"http://fedoraproject.org/wiki/How_to_create_an_RPM_package\">How to create an RPM package</link>"
-
-#: ./doc/security-guide/ch052_devices.xml239(para)
-msgid ""
-"Compiler hardening makes it more difficult to attack the QEMU process. "
-"However, if an attacker does succeed, we would like to limit the impact of "
-"the attack. Mandatory access controls accomplish this by restricting the "
-"privileges on QEMU process to only what is needed. This can be accomplished "
-"using sVirt / SELinux or AppArmor. When using sVirt, SELinux is configured "
-"to run every QEMU process under a different security context. AppArmor can "
-"be configured to provide similar functionality. We provide more details on "
-"sVirt in the instance isolation section below."
-msgstr "コンパイラーのセキュリティ強化機能により、QEMU プロセスへの攻撃をより難しくできます。しかし、攻撃者が成功すると、攻撃の影響範囲を抑えたいでしょう。強制アクセス制御は、QEMU プロセスの権限を必要な範囲に制限することにより、これを実現します。これは sVirt / SELinux または AppArmor により実現できます。sVirt 利用時、SELinux はすべての QEMU プロセスが別々のセキュリティドメインで動作するよう設定されます。AppArmor は同様の機能を提供するよう設定できます。以下のインスタンス分離のセクションで sVirt の詳細を示します。"
-
-#: ./doc/security-guide/ch052_devices.xml253(title)
-msgid "sVirt: SELinux and virtualization"
-msgstr "sVirt: SELinux と 仮想化"
-
-#: ./doc/security-guide/ch052_devices.xml254(para)
-msgid ""
-"With unique kernel-level architecture and National Security Agency (NSA) "
-"developed security mechanisms, KVM provides foundational isolation "
-"technologies for multi tenancy. With developmental origins dating back to "
-"2002, the Secure Virtualization (sVirt) technology is the application of "
-"SELinux against modern day virtualization. SELinux, which was designed to "
-"apply separation control based upon labels, has been extended to provide "
-"isolation between virtual machine processes, devices, data files and system "
-"processes acting upon their behalf."
-msgstr "KVM は複数のテナントを分離する基本技術を提供します。カーネルレベルの独特のアーキテクチャを用いて、National Security Agency (NSA) により開発されたセキュリティ機構です。開発の起源は 2002 年までさかのぼり、Secure Virtualization (sVirt) 技術は最近の仮想化向けの SELinux の応用技術です。SELinux は、ラベルに基づいた分離制御を適用するために設計され、仮想マシンのプロセス、デバイス、データファイル、それらの上で動作するシステムプロセス間の分離を提供するために拡張されました。"
-
-#: ./doc/security-guide/ch052_devices.xml265(para)
-msgid ""
-"OpenStack's sVirt implementation aspires to protect hypervisor hosts and "
-"virtual machines against two primary threat vectors:"
-msgstr "OpenStack の sVirt 実装は、2 種類の主要な脅威ベクターに対して、ハイパーバイザーホストと仮想マシンを保護することを目指しています。"
-
-#: ./doc/security-guide/ch052_devices.xml270(para)
-msgid ""
-"<emphasis role=\"bold\">Hypervisor threats</emphasis> A compromised "
-"application running within a virtual machine attacks the hypervisor to "
-"access underlying resources. For example, the host OS, applications, or "
-"devices within the physical machine. This is a threat vector unique to "
-"virtualization and represents considerable risk as the underlying real "
-"machine can be compromised due to vulnerability in a single virtual "
-"application."
-msgstr "<emphasis role=\"bold\">ハイパーバイザーの脅威</emphasis> 仮想マシンの中で動作している侵入されたアプリケーションは、バックエンドのリソースにアクセスするためにハイパーバイザーを攻撃します。例えば、ホスト OS、アプリケーション、物理マシンにあるデバイスです。バックエンドの物理マシンが単一の仮想アプリケーションにある脆弱性のために侵入されうるため、これは仮想化に特有の脅威ベクターであり、考慮すべきリスクを表します。"
-
-#: ./doc/security-guide/ch052_devices.xml280(para)
-msgid ""
-"<emphasis role=\"bold\">Virtual Machine (multi-tenant) threats</emphasis> A "
-"compromised application running within a VM attacks the hypervisor to "
-"access/control another virtual machine and its resources. This is a threat "
-"vector unique to virtualization and represents considerable risk as a "
-"multitude of virtual machine file images could be compromised due to "
-"vulnerability in a single application. This virtual network attack is a "
-"major concern as the administrative techniques for protecting real networks "
-"do not directly apply to the virtual environment."
-msgstr "<emphasis role=\"bold\">仮想マシン (マルチテナント) の脅威</emphasis> 仮想マシンの中で動作している侵入されたアプリケーションは、他の仮想マシンとそのリソースにアクセスし、制御するためにハイパーバイザーを攻撃します。仮想マシンのイメージファイルの集合が単一のアプリケーションにある脆弱性のために侵入されうるため、これは仮想化に特有の脅威ベクターであり、考慮すべきリスクを表します。実ネットワークを保護するための管理技術が仮想マシン環境にそのまま適用できないため、この仮想ネットワークへの攻撃はおもな関心事です。"
-
-#: ./doc/security-guide/ch052_devices.xml293(para)
-msgid ""
-"Each KVM-based virtual machine is a process which is labeled by SELinux, "
-"effectively establishing a security boundary around each virtual machine. "
-"This security boundary is monitored and enforced by the Linux kernel, "
-"restricting the virtual machine's access to resources outside of its "
-"boundary such as host machine data files or other VMs."
-msgstr "各 KVM ベースの仮想マシンは SELinux によりラベル付けされているプロセスです。これは各仮想マシンのセキュリティ境界を効率的に確立します。このセキュリティ境界は、Linux カーネルにより監視され、強制されます。ホストマシンのデータファイルや他の仮想マシンのような、仮想マシンの境界外のリソースへのアクセスは制限されます。"
-
-#: ./doc/security-guide/ch052_devices.xml313(para)
-msgid ""
-"As shown above, sVirt isolation is provided regardless of the guest "
-"Operating System running inside the virtual machineLinux or Windows VMs can "
-"be used. Additionally, many Linux distributions provide SELinux within the "
-"operating system, allowing the virtual machine to protect internal virtual "
-"resources from threats."
-msgstr "上に示したとおり、sVirt による分離は仮想マシン内で動作しているゲストオペレーティングシステムに関わらず提供されます。Linux や Windows の仮想マシンを使用できます。さらに、多くの Linux ディストリビューションはオペレーティングシステム内の SELinux を提供しています。仮想マシンが内部の仮想リソースを脅威から保護できます。"
-
-#: ./doc/security-guide/ch052_devices.xml322(title)
-msgid "Labels and categories"
-msgstr "ラベルとカテゴリ"
-
-#: ./doc/security-guide/ch052_devices.xml323(para)
-msgid ""
-"KVM-based virtual machine instances are labelled with their own SELinux data"
-" type, known as svirt_image_t. Kernel level protections prevent unauthorized"
-" system processes, such as malware, from manipulating the virtual machine "
-"image files on disk. When virtual machines are powered off, images are "
-"stored as svirt_image_t as shown below:"
-msgstr "KVM ベースの仮想マシンインスタンスは、svirt_image_t として知られる、独自の SELinux データタイプでラベル付けされています。カーネルレベルの保護により、悪意のあるソフトウェアのような権限のないシステムプロセスが、ディスクにある仮想マシンのイメージファイルを操作することを防ぎます。仮想マシンが電源オフのとき、イメージは以下のように svirt_image_t として保存されます。"
-
-#: ./doc/security-guide/ch052_devices.xml334(para)
-msgid ""
-"The <literal>svirt_image_t</literal> label uniquely identifies image files "
-"on disk, allowing for the SELinux policy to restrict access. When a KVM-"
-"based Compute image is powered on, sVirt appends a random numerical "
-"identifier to the image. sVirt is technically capable of assigning numerical"
-" identifiers to 524,288 virtual machines per hypervisor node, however "
-"OpenStack deployments are highly unlikely to encounter this limitation."
-msgstr "<literal>svirt_image_t</literal> ラベルは独自にディスク上のイメージファイルを識別し、SELinux ポリシーがアクセス制限できるようにします。KVM ベースの Compute イメージが電源投入された際、sVirt はイメージに乱数のIDを付与します。sVirt は技術的には１ハイパーバイザーノードあたり 524,288 個の仮想マシンに数字IDを付与する事ができますが、OpenStack デプロイでこの制限に遭遇する事はまずないでしょう。"
-
-#: ./doc/security-guide/ch052_devices.xml343(para)
-msgid "This example shows the sVirt category identifier:"
-msgstr "この例は sVirt カテゴリー識別子を示します。"
-
-#: ./doc/security-guide/ch052_devices.xml348(title)
-msgid "Booleans"
-msgstr "ブーリアン"
-
-#: ./doc/security-guide/ch052_devices.xml349(para)
-msgid ""
-"To ease the administrative burden of managing SELinux, many enterprise Linux"
-" platforms utilize SELinux Booleans to quickly change the security posture "
-"of sVirt."
-msgstr "SELinux の管理負担を減らすために、多くのエンタープライズ Linux プラットフォームは sVirt のセキュリティ設定を簡単に変更するために、SELinux ブーリアンを利用します。"
-
-#: ./doc/security-guide/ch052_devices.xml353(para)
-msgid ""
-"Red Hat Enterprise Linux-based KVM deployments utilize the following sVirt "
-"booleans:"
-msgstr "Red Hat Enterprise Linux ベースの KVM 環境は以下の sVirt ブーリアンを利用します。"
-
-#: ./doc/security-guide/ch052_devices.xml361(emphasis)
-msgid "sVirt SELinux Boolean"
-msgstr "sVirt SELinux ブーリアン"
-
-#: ./doc/security-guide/ch052_devices.xml367(para)
-msgid "virt_use_common"
-msgstr "virt_use_common"
-
-#: ./doc/security-guide/ch052_devices.xml368(para)
-msgid "Allow virt to use serial/parallel communication ports."
-msgstr "仮想化がシリアル通信ポートとパラレル通信ポートを使用することを許可します。"
-
-#: ./doc/security-guide/ch052_devices.xml371(para)
-msgid "virt_use_fusefs"
-msgstr "virt_use_fusefs"
-
-#: ./doc/security-guide/ch052_devices.xml372(para)
-msgid "Allow virt to read FUSE mounted files."
-msgstr "仮想化が FUSE マウントされたファイルを読み取ることを許可します。"
-
-#: ./doc/security-guide/ch052_devices.xml375(para)
-msgid "virt_use_nfs"
-msgstr "virt_use_nfs"
-
-#: ./doc/security-guide/ch052_devices.xml376(para)
-msgid "Allow virt to manage NFS mounted files."
-msgstr "仮想化が NFS マウントされたファイルを管理することを許可します。"
-
-#: ./doc/security-guide/ch052_devices.xml379(para)
-msgid "virt_use_samba"
-msgstr "virt_use_samba"
-
-#: ./doc/security-guide/ch052_devices.xml380(para)
-msgid "Allow virt to manage CIFS mounted files."
-msgstr "仮想化が CIFS マウントされたファイルを管理することを許可します。"
-
-#: ./doc/security-guide/ch052_devices.xml383(para)
-msgid "virt_use_sanlock"
-msgstr "virt_use_sanlock"
-
-#: ./doc/security-guide/ch052_devices.xml384(para)
-msgid "Allow confined virtual guests to interact with the sanlock."
-msgstr "制限された仮想マシンが sanlock を操作することを許可します。"
-
-#: ./doc/security-guide/ch052_devices.xml387(para)
-msgid "virt_use_sysfs"
-msgstr "virt_use_sysfs"
-
-#: ./doc/security-guide/ch052_devices.xml388(para)
-msgid "Allow virt to manage device configuration (PCI)."
-msgstr "仮想マシンがデバイス設定 (PCI) を管理することを許可します。"
-
-#: ./doc/security-guide/ch052_devices.xml391(para)
-msgid "virt_use_usb"
-msgstr "virt_use_usb"
-
-#: ./doc/security-guide/ch052_devices.xml392(para)
-msgid "Allow virt to use USB devices."
-msgstr "仮想化が USB デバイスを使用することを許可します。"
-
-#: ./doc/security-guide/ch052_devices.xml395(para)
-msgid "virt_use_xserver"
-msgstr "virt_use_xserver"
-
-#: ./doc/security-guide/ch052_devices.xml396(para)
-msgid "Allow virtual machine to interact with the X Window System."
-msgstr "仮想マシンが X Window System と通信することを許可します。"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml8(title)
-msgid "SSL proxies and HTTP services"
-msgstr "SSLプロキシとHTTPサービス"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml9(para)
-msgid ""
-"OpenStack endpoints are HTTP services providing APIs to both end-users on "
-"public networks and to other OpenStack services within the same deployment "
-"operating over the management network. It is highly recommended these "
-"requests, both those internal and external, operate over SSL."
-msgstr "OpenStack エンドポイントは、パブリックネットワーク上のエンドユーザーと、管理ネットワークを介して操作する同じデプロイ中の他 OpenStack サービスの両方に対して API を提供する HTTP サービスです。これらのリクエスト（内部と外部の両方）を SSL 上で操作する事を強く推奨します。"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml10(para)
-msgid ""
-"In order for API requests to be encrypted by SSL it's necessary to position "
-"the API services behind a proxy that will establish and terminate SSL "
-"sessions. The following table offers a non-exhaustive list of software "
-"services that can proxy SSL traffic for API requests:"
-msgstr "API リクエストを SSL で暗号化する為に、APIサービスはSSLセッションを確立・切断するプロキシの後ろに位置する必要があります。下記の表はAPIリクエスト用にSSLトラフィックをプロキシ可能なソフトウェアサービスの（あまり厳密でない）一覧を示しています。"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml12(link)
-msgid "Pound"
-msgstr "Pound"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml15(link)
-#: ./doc/security-guide/ch020_ssl-everywhere.xml153(title)
-msgid "Stud"
-msgstr "Stud"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml18(link)
-#: ./doc/security-guide/ch020_ssl-everywhere.xml191(title)
-msgid "nginx"
-msgstr "nginx"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml21(link)
-msgid "Apache httpd"
-msgstr "Apache httpd"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml24(para)
-msgid "Hardware appliance SSL acceleration proxies"
-msgstr "ハードウェアアプライアンス SSLアクセラレーションプロキシ"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml27(para)
-msgid ""
-"It is important to be mindful of the size of requests that will be processed"
-" by any chosen SSL proxy."
-msgstr "選択したSSLプロキシによって処理されるリクエストのサイズを気にする事は重要です。"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml29(title)
-msgid "Examples"
-msgstr "例"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml30(para)
-msgid ""
-"Below we provide some sample recommended configuration settings for enabling"
-" SSL in some of the more popular web servers/SSL terminators. Note that we "
-"have SSL v3 enabled in some of these examples as this will be required in "
-"many deployments for client compatibility."
-msgstr "以下に、幾つかの主な有名 Web サーバ／SSL 終端でSSLを有効にする為の幾つかの推奨設定例を示します。クライアント互換性の為に多くのデプロイで必要になる筈なので、幾つかの例ではSSL v3 が有効になっている点に注意して下さい。"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml31(para)
-msgid ""
-"Before we delve into the configurations, we briefly discuss the ciphers' "
-"configuration element and its format. A more exhaustive treatment on "
-"available ciphers and the OpenSSL cipher list format can be found at: <link "
-"href=\"https://www.openssl.org/docs/apps/ciphers.html\">ciphers</link>."
-msgstr "設定を掘り下げる前に、暗号の設定要素とその形式について簡単に議論します。利用可能な暗号におけるより包括的な使い方、および OpenSSL 暗号一覧形式が <link href=\"https://www.openssl.org/docs/apps/ciphers.html\">ciphers</link> にあります。"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml35(para)
-msgid "or"
-msgstr "または"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml39(para)
-msgid ""
-"Cipher string options are separated by \":\", while \"!\" provides negation "
-"of the immediately following element. Element order indicates preference "
-"unless overridden by qualifiers such as HIGH. Let us take a closer look at "
-"the elements in the above sample strings."
-msgstr "暗号オプションの文字列は「:」で区切られます。「!」は直後の要素の否定を意味します。要素の順番は、HIGH のような修飾語句により上書きされない限り、優先度を意味します。上のサンプル文字列の要素をもう少し具体的に見ていきましょう。"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml42(code)
-msgid "kEECDH:kEDH"
-msgstr "kEECDH:kEDH"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml44(para)
-msgid ""
-"Ephemeral Elliptic Curve Diffie-Hellman (abbreviated as EECDH and ECDHE)."
-msgstr "楕円曲線ディフィー・ヘルマン (EECDH や ECDHE と略す)"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml45(para)
-msgid ""
-"Ephemeral Diffie-Hellman (abbreviated either as EDH or DHE) uses prime field"
-" groups."
-msgstr "一時ディフィー・ヘルマン (EDH や DHE と略す) は素体グループを使用します。"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml46(para)
-msgid ""
-"Both approaches provide <link "
-"href=\"http://en.wikipedia.org/wiki/Forward_secrecy\">Perfect Forward "
-"Secrecy (PFS)</link>."
-msgstr "どちらの方法も <link href=\"http://en.wikipedia.org/wiki/Forward_secrecy\">Perfect Forward Secrecy (PFS)</link> を提供します。"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml47(para)
-msgid ""
-"Ephemeral Elliptic Curves require the server to be configured with a named "
-"curve, and provide better security than prime field groups and at lower "
-"computational cost. However, prime field groups are more widely implemented,"
-" and thus typically both are included in list."
-msgstr "一時楕円曲線はサーバーが名前付き曲線を用いて設定されている必要があります。素体グループよりセキュリティが高く、計算コストが低いです。しかしながら、素体グループはより幅広く実装されているので、一般的にどちらも一覧に含まれます。"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml51(code)
-msgid "kRSA"
-msgstr "kRSA"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml53(para)
-msgid ""
-"Cipher suites using the <link "
-"href=\"http://en.wikipedia.org/wiki/RSA_%28cryptosystem%29\">RSA</link> "
-"exchange, authentication or either respectively."
-msgstr "<link href=\"http://en.wikipedia.org/wiki/RSA_%28cryptosystem%29\">RSA</link> の鍵交換、認証、またはその両方を使用する暗号スイート。"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml57(code)
-msgid "HIGH"
-msgstr "HIGH"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml59(para)
-msgid ""
-"Selects highest possible security cipher in the negotiation phase. These "
-"typically have keys of length 128 bits or longer."
-msgstr "ネゴシエーション段階で利用可能な最高のセキュリティ暗号を選択します。これらは一般的に 128 ビット以上の鍵を持ちます。"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml63(code)
-msgid "!RC4"
-msgstr "!RC4"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml65(para)
-msgid ""
-"No RC4. RC4 has flaws in the context of TLS/SSL V3. See <link "
-"href=\"cr.yp.to/streamciphers/rc4biases-20130708.pdf\"> On the Security of "
-"RC4 in TLS and WPA</link>."
-msgstr "RC4 使用不可。RC4 は TLS/SSL V3 の文脈で欠陥があります。<link href=\"cr.yp.to/streamciphers/rc4biases-20130708.pdf\"> On the Security of RC4 in TLS and WPA</link> を参照してください。"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml69(code)
-msgid "!MD5"
-msgstr "!MD5"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml71(para)
-msgid ""
-"No MD5. MD5 is not collision resistant, and thus not acceptable for Message "
-"Authentication Codes (MAC) or signatures."
-msgstr "MD5 使用不可。MD5 は衝突耐性がないため、メッセージ認証コード (MAC) や署名に利用できません。"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml75(code)
-msgid "!aNULL:!eNULL"
-msgstr "!aNULL:!eNULL"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml77(para)
-msgid "Disallows clear text"
-msgstr "平文を禁止します。"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml81(code)
-msgid "!EXP"
-msgstr "!EXP"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml83(para)
-msgid ""
-"Disallows export encryption algorithms, which by design tend to were weak, "
-"typically using 40 and 56 bit keys."
-msgstr "export 暗号アルゴリズムを無効化します。これは、設計として弱く、一般的に 40 ビットか 56 ビットの鍵を使用しています。"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml84(para)
-msgid ""
-"US Export restrictions on cryptography systems have been lifted and no "
-"longer need to be supported."
-msgstr "暗号システムにおけるアメリカ輸出規制を解かれていて、もはやサポートする必要がありません。"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml88(code)
-msgid "!LOW:!MEDIUM"
-msgstr "!LOW:!MEDIUM"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml90(para)
-msgid ""
-"Disallows low (keys 56 or 64 bits long) and medium (128 bit long keys) "
-"ciphers because of their vulnerability to brute force attacks (example "
-"2-DES). This constraint leaves acceptable Triple Data Encryption Standard "
-"(Triple DES) also known as Triple Data Encryption Algorithm (TDEA) and the "
-"Advanced Encryption Standard (AES), each of which has keys greater than "
-"equal to 128 bits and thus more secure."
-msgstr "総当たり攻撃への脆弱性のため、低度 (56/64 ビット長の鍵) と中程度 (128 ビット長の鍵) の暗号を無効化します (例: 2-DES)。この制限は、Triple Data Encryption Algorithm (TDEA) としても知られている Triple Data Encryption Standard (3-DES)、Advanced Encryption Standard (AES) を利用できる状態にします。このどちらも 128 ビット以上の鍵を持つため、よりセキュアです。"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml94(code)
-msgid "Protocols"
-msgstr "プロトコル"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml96(para)
-msgid ""
-"Protocols are enabled/disabled through SSL_CTX_set_options. We recommend "
-"disabling SSLv2 and enabling TLS or SSLv3 (which was standardised as TLS "
-"with a few changes)."
-msgstr "プロトコルは SSL_CTX_set_options により有効化、無効化できます。SSLv2 を無効化し、TLS や SSLv3 (いくつか変更をして TLS として標準化されました) を有効化することを推奨します。"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml101(title)
-msgid "Pound - with AES-NI acceleration"
-msgstr "Pound（AES-NI アクセラレーション付き）"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml154(para)
-msgid ""
-"This stud example enables SSL v3 for client compatibility. The ciphers line "
-"can be tweaked based on your needs, however this is a reasonable starting "
-"place."
-msgstr "この Stud の例は、クライアント互換性の為に SSL v3 を有効にしています。ciphers 行は必要に応じていじる事が出来ますが、しかしながらこの例の値は合理的な初期値です。"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml192(para)
-msgid ""
-"This nginx example requires TLS v1.1 or v1.2 for maximum security. The "
-"ssl_ciphers line can be tweaked based on your needs, however this is a "
-"reasonable starting place."
-msgstr "この nginx の例は、セキュリティを最大化する為に TLS v1.1 又は v1.2 を必要とします。ssl_ciphers 行は必要に応じて変更可能ですが、しかしながらこの例の値は合理的な初期値です。"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml208(title)
-msgid "Apache"
-msgstr "Apache"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml233(para)
-msgid ""
-"Compute API SSL endpoint in Apache, which you must pair with a short WSGI "
-"script."
-msgstr "Apache 中の Compute API SSL エンドポイント (短い WSGI スクリプトと組み合わせる必要あり)"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml257(title)
-msgid "HTTP strict transport security"
-msgstr "HTTP Strict Transport Security"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml258(para)
-msgid ""
-"We recommend that all production deployments use HSTS. This header prevents "
-"browsers from making insecure connections after they have made a single "
-"secure one. If you have deployed your HTTP services on a public or an "
-"untrusted domain, HSTS is especially important. To enable HSTS, configure "
-"your web server to send a header like this with all requests:"
-msgstr "全ての製品で HSTS を使用する事を推奨します。このヘッダは、ブラウザが単一のセキュアな接続を確立した後に、セキュアでない接続を確立する事を防止します。パブリック上あるいは信用出来ないドメイン上の HTTP サービスをデプロイした場合、HSTS は特に重要です。HSTS を有効にするためには、全リクエストでこのようなヘッダを送信するよう Web サーバを設定します。"
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml260(para)
-msgid ""
-"Start with a short timeout of 1 day during testing, and raise it to one year"
-" after testing has shown that you haven't introduced problems for users. "
-"Note that once this header is set to a large timeout, it is (by design) very"
-" difficult to disable."
-msgstr "テストでは1日の短いタイムアウトで始め、テストでユーザーに問題が発生しなかった事を確認した後で設定を１年まで増やします。一旦このヘッダーに大きなタイムアウトを設定してしまうと、無効化する事は (設計上) 非常に困難です。"
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml8(title)
-msgid "Forensics and incident response"
-msgstr "フォレンジングとインシデント対応"
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml9(para)
-msgid ""
-"A lot of activity goes on within a cloud environment. It is a mix of "
-"hardware, operating systems, virtual machine managers, the OpenStack "
-"services, cloud-user activity such as creating instances and attaching "
-"storage, the network underlying the whole, and finally end-users using the "
-"applications running on the various instances."
-msgstr "多数の活動がクラウド環境内で行われます。これはハードウェア、オペレーティングシステム、仮想マシンマネージャ、OpenStackサービス群、インスタンス作成やストレージアタッチのようなクラウド⇔ユーザ活動、全体の土台であるネットワーク、最後に様々なインスタンス上で実行されるアプリケーションを使用するエンドユーザのミックスです。"
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml10(para)
-msgid ""
-"The generation and collection of logs is an important component of securely "
-"monitoring an OpenStack infrastructure. Logs provide visibility into the "
-"day-to-day actions of administrators, tenants, and guests, in addition to "
-"the activity in the compute, networking, and storage and other components "
-"that comprise your OpenStack deployment."
-msgstr "ログの生成と収集は OpenStack インフラのセキュリティ監視の重要なコンポーネントです。ログは日々の管理者・テナント・ゲストの行動に加え、あなたの OpenStack デプロイを構成する Compute、Networking、ストレージ、他のコンポーネントの活動の可視性を提供します。"
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml11(para)
-msgid ""
-"The basics of logging: configuration, setting log level, location of the log"
-" files, and how to use and customize logs, as well as how to do centralized "
-"collections of logs is well covered in the <link "
-"href=\"http://docs.openstack.org/ops/\"><citetitle>OpenStack Operations "
-"Guide</citetitle></link>."
-msgstr "ロギングの基本: ログを集中収集する方法と同様、設定、ログレベル設定、ログファイルの位置、ログの使用とカスタマイズ方法は、<link href=\"http://docs.openstack.org/ops/\"><citetitle>OpenStack Operations Guide</citetitle></link> で充分にカバーされています。"
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml12(para)
-msgid ""
-"Logs are not only valuable for proactive security and continuous compliance "
-"activities, but they are also a valuable information source for "
-"investigating and responding to incidents."
-msgstr "ログは率先したセキュリティや継続的なコンプライアンス活動に有用であるのみならず、インシデントの調査と対応の為の情報源としても有用です。"
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml13(para)
-msgid ""
-"For instance, analyzing the access logs of Identity Service or its "
-"replacement authentication system would alert us to failed logins, their "
-"frequency, origin IP, whether the events are restricted to select accounts "
-"etc. Log analysis supports detection."
-msgstr "例えば、Identity サービスまたはその代替認証システムへのアクセスログ解析は、アカウント等を選択してイベントを制限する／しないで、失敗したログイン、それらの頻度、アクセス元IPアドレスを警告します。ログ解析は検知をサポートします。"
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml14(para)
-msgid ""
-"On detection, further action may be to black list an IP, or recommend "
-"strengthening user passwords, or even de-activating a user account if it is "
-"deemed dormant."
-msgstr "検知時、追加のアクションになるのは、IP のブラックリストだったり、ユーザのパスワードを補強する事を推奨したり、ユーザアカウントが休眠状態である場合はその無効化でさえあったりします。"
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml16(title)
-msgid "Monitoring use cases"
-msgstr "監視ユースケース"
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml17(para)
-msgid ""
-"Monitoring events is more pro-active and provides real-time detection and "
-"response. There are several tools to aid in monitoring."
-msgstr "イベントの監視はより率先的で、リアルタイムの検知と対応を提供します。監視の助けとなるいくつかのツールがあります。"
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml18(para)
-msgid ""
-"In the case of an OpenStack cloud instance, we need to monitor the hardware,"
-" the OpenStack services, and the cloud resource usage. The last stems from "
-"wanting to be elastic, to scale to the dynamic needs of the users."
-msgstr "OpenStack クラウドインスタンスの場合、ハードウェア、OpenStack サービス、クラウドリソース使用量を監視する必要があります。最後は、柔軟性、ユーザの変化するニーズへのスケール性への要求から生じるものです。"
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml19(para)
-msgid ""
-"Here are a few important use cases to consider when implementing log "
-"aggregation, analysis and monitoring. These use cases can be implemented and"
-" monitored through various commercial and open source tools, homegrown "
-"scripts, etc. These tools and scripts can generate events that can then be "
-"sent to the administrators through email or integrated dashboard. It is "
-"important to consider additional use cases that may apply to your specific "
-"network and what you may consider anomalous behavior."
-msgstr "ここで、ログ収集、解析、監視を実装する際に考慮すべき重要なユースケースがいくつかあります。これらのユースケースは、様々な商用やオープンソースのツール、自作のスクリプト等を通じて実装・監視できます。これらのツールとスクリプトは、電子メールや組み込まれたダッシュボードで管理者に送信されるイベントを生成できます。あなたの場合のネットワークに適用できる追加のユースケースや、変則的な挙動を考慮できるようにするものを考慮する事は重要です。"
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml21(para)
-msgid ""
-"Detecting the absence of log generation is an event of high value. Such an "
-"event would indicate a service failure or even an intruder who has "
-"temporarily switched off logging or modified the log level to hide their "
-"tracks."
-msgstr "ログ生成無しの検知は価値の高いイベントです。このようなイベントはサービス障害、または一時的にログをオフにしたり、監視者から隠れるためにログレベルを変更した侵入者を示している可能性があります。"
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml25(para)
-msgid ""
-"Application events such as start and/or stop that were unscheduled would "
-"also be events to monitor and examine for possible security implications."
-msgstr "スケジュール外の start/stop のようなアプリケーションイベントは、潜在的なセキュリティ的なウラについての監視と確認作業を行うイベントでもあるでしょう。"
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml29(para)
-msgid ""
-"OS events on the OpenStack service machines such as user logins, restarts "
-"also provide valuable insight into use/misuse"
-msgstr "ユーザログイン、再起動のような OpenStack サービスマシン上の OS イベントもまた、使用／誤用への価値ある洞察を与えます。"
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml33(para)
-msgid ""
-"Being able to detect the load on the OpenStack servers also enables "
-"responding by way of introducing additional servers for load balancing to "
-"ensure high availability."
-msgstr "OpenStack サーバ群の負荷を検知可能にする事はまた、高可用化対応の為に負荷分散用追加サーバを導入する為の対応を可能にする事でもあります。"
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml37(para)
-msgid ""
-"Other events that are actionable are networking bridges going down, ip "
-"tables being flushed on compute nodes and consequential loss of access to "
-"instances resulting in unhappy customers."
-msgstr "行動可能な他のイベントはネットワークブリッジがダウンした事です。compute ノード上で設定がクリアされた iptables や、インスタンスへのアクセスの重大なロスはユーザを不幸にします。"
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml41(para)
-msgid ""
-"To reduce security risks from orphan instances on a user/tenant/domain "
-"deletion in the Identity service there is discussion to generate "
-"notifications in the system and have OpenStack components respond to these "
-"events as appropriate such as terminating instances, disconnecting attached "
-"volumes, reclaiming CPU and storage resources etc."
-msgstr "identity サービス中のユーザ／テナント／ドメイン削除に伴う見捨てられたインスタンスかあのセキュリティリスクを低減する為、システム中で通知を生成する事と、インスタンス削除、アタッチしたボリュームの切断、CPU やストレージリソースの回収等のイベントに適切に対応する OpenStack コンポーネントを用意する事について議論があります。"
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml44(para)
-msgid ""
-"A cloud will host many virtual instances, and monitoring these instances "
-"goes beyond hardware monitoring and log files which may just contain CRUD "
-"events."
-msgstr "クラウドには多数の仮想インスタンスがあり、これらのインスタンスの監視はハードウェア監視と CRUD イベントのみ含むログファイルの背後にあります。"
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml45(para)
-msgid ""
-"Security monitoring controls such as intrusion detection software, antivirus"
-" software, and spyware detection and removal utilities can generate logs "
-"that show when and how an attack or intrusion took place. Deploying these "
-"tools on the cloud machines provides value and protection. Cloud users, "
-"those running instances on the cloud may also want to run such tools on "
-"their instances."
-msgstr "侵入検知ソフトウェア、アンチウイルスソフトウェア、スパイウェア検知・削除ユーティリティのようなセキュリティ監視制御は、攻撃や侵入が発生した時と方法を示すログを生成できます。クラウドマシン上にこれらのツールをデプロイする事は、価値と保護を提供します。（クラウド上でインスタンスを実行する）クラウドユーザも自身のインスタンス上でこのようなツールを実行したいかも知れません。"
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml49(link)
-msgid "http://www.mirantis.com/blog/openstack-monitoring/"
-msgstr "http://www.mirantis.com/blog/openstack-monitoring/"
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml50(link)
-msgid "http://blog.sflow.com/2012/01/host-sflow-distributed-agent.html"
-msgstr "http://blog.sflow.com/2012/01/host-sflow-distributed-agent.html"
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml51(link)
-msgid "http://blog.sflow.com/2009/09/lan-and-wan.html"
-msgstr "http://blog.sflow.com/2009/09/lan-and-wan.html"
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml52(link)
-msgid ""
-"http://blog.sflow.com/2013/01/rapidly-detecting-large-flows-sflow-vs.html"
-msgstr "http://blog.sflow.com/2013/01/rapidly-detecting-large-flows-sflow-vs.html"
-
 #. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
-#: ./doc/security-guide/ch058_forensicsincident-response.xml0(None)
+#: ./doc/security-guide/ch027_storage.xml0(None)
 msgid "translator-credits"
 msgstr "Akihiro MOTOKI <amotoki@gmail.com>, 2013\nAkira Yoshiyama <akirayoshiyama@gmail.com>, 2013-2014\nyfukuda <fukuda.yuko@jp.fujitsu.com>, 2014\nMasanori Itoh <masanori.itoh@gmail.com>, 2013\nmasayukig <masayuki.igawa@gmail.com>, 2013\nmittjp1129 <mittjp1129@gmail.com>, 2014\nmyamamot <myamamot@redhat.com>, 2013-2014\n*はたらくpokotan* <>, 2013-2014\nTsutomu TAKEKAWA <takekawa@gmail.com>, 2013\ndoki701 <tokidokidokidoki@gmail.com>, 2013\nTomoyuki KATO <tomo@dream.daynight.jp>, 2012-2014\ntomoya.goto <tomoyan777@gmail.com>, 2013-2014\ntmak <t.makabe@gmail.com>, 2013-2014\nykatabam <ykatabam@redhat.com>, 2013-2014"
diff --git a/doc/security-guide/locale/security-guide.pot b/doc/security-guide/locale/security-guide.pot
index 5fac51345e..6a6f03206c 100644
--- a/doc/security-guide/locale/security-guide.pot
+++ b/doc/security-guide/locale/security-guide.pot
@@ -1,7 +1,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2014-05-29 06:09+0000\n"
+"POT-Creation-Date: 2014-06-03 06:11+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -9,6 +9,882 @@ msgstr ""
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:8(title)
+msgid "SSL proxies and HTTP services"
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:9(para)
+msgid "OpenStack endpoints are HTTP services providing APIs to both end-users on public networks and to other OpenStack services within the same deployment operating over the management network. It is highly recommended these requests, both those internal and external, operate over SSL."
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:10(para)
+msgid "In order for API requests to be encrypted by SSL it's necessary to position the API services behind a proxy that will establish and terminate SSL sessions. The following table offers a non-exhaustive list of software services that can proxy SSL traffic for API requests:"
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:12(link)
+msgid "Pound"
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:15(link) ./doc/security-guide/ch020_ssl-everywhere.xml:153(title)
+msgid "Stud"
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:18(link) ./doc/security-guide/ch020_ssl-everywhere.xml:191(title)
+msgid "nginx"
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:21(link)
+msgid "Apache httpd"
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:24(para)
+msgid "Hardware appliance SSL acceleration proxies"
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:27(para)
+msgid "It is important to be mindful of the size of requests that will be processed by any chosen SSL proxy."
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:29(title)
+msgid "Examples"
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:30(para)
+msgid "Below we provide some sample recommended configuration settings for enabling SSL in some of the more popular web servers/SSL terminators. Note that we have SSL v3 enabled in some of these examples as this will be required in many deployments for client compatibility."
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:31(para)
+msgid "Before we delve into the configurations, we briefly discuss the ciphers' configuration element and its format. A more exhaustive treatment on available ciphers and the OpenSSL cipher list format can be found at: <link href=\"https://www.openssl.org/docs/apps/ciphers.html\">ciphers</link>."
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:35(para)
+msgid "or"
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:39(para)
+msgid "Cipher string options are separated by \":\", while \"!\" provides negation of the immediately following element. Element order indicates preference unless overridden by qualifiers such as HIGH. Let us take a closer look at the elements in the above sample strings."
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:42(code)
+msgid "kEECDH:kEDH"
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:44(para)
+msgid "Ephemeral Elliptic Curve Diffie-Hellman (abbreviated as EECDH and ECDHE)."
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:45(para)
+msgid "Ephemeral Diffie-Hellman (abbreviated either as EDH or DHE) uses prime field groups."
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:46(para)
+msgid "Both approaches provide <link href=\"http://en.wikipedia.org/wiki/Forward_secrecy\">Perfect Forward Secrecy (PFS)</link>."
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:47(para)
+msgid "Ephemeral Elliptic Curves require the server to be configured with a named curve, and provide better security than prime field groups and at lower computational cost. However, prime field groups are more widely implemented, and thus typically both are included in list."
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:51(code)
+msgid "kRSA"
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:53(para)
+msgid "Cipher suites using the <link href=\"http://en.wikipedia.org/wiki/RSA_%28cryptosystem%29\">RSA</link> exchange, authentication or either respectively."
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:57(code)
+msgid "HIGH"
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:59(para)
+msgid "Selects highest possible security cipher in the negotiation phase. These typically have keys of length 128 bits or longer."
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:63(code)
+msgid "!RC4"
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:65(para)
+msgid "No RC4. RC4 has flaws in the context of TLS/SSL V3. See <link href=\"cr.yp.to/streamciphers/rc4biases-20130708.pdf\"> On the Security of RC4 in TLS and WPA</link>."
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:69(code)
+msgid "!MD5"
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:71(para)
+msgid "No MD5. MD5 is not collision resistant, and thus not acceptable for Message Authentication Codes (MAC) or signatures."
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:75(code)
+msgid "!aNULL:!eNULL"
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:77(para)
+msgid "Disallows clear text"
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:81(code)
+msgid "!EXP"
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:83(para)
+msgid "Disallows export encryption algorithms, which by design tend to were weak, typically using 40 and 56 bit keys."
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:84(para)
+msgid "US Export restrictions on cryptography systems have been lifted and no longer need to be supported."
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:88(code)
+msgid "!LOW:!MEDIUM"
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:90(para)
+msgid "Disallows low (keys 56 or 64 bits long) and medium (128 bit long keys) ciphers because of their vulnerability to brute force attacks (example 2-DES). This constraint leaves acceptable Triple Data Encryption Standard (Triple DES) also known as Triple Data Encryption Algorithm (TDEA) and the Advanced Encryption Standard (AES), each of which has keys greater than equal to 128 bits and thus more secure."
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:94(code)
+msgid "Protocols"
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:96(para)
+msgid "Protocols are enabled/disabled through SSL_CTX_set_options. We recommend disabling SSLv2 and enabling TLS or SSLv3 (which was standardised as TLS with a few changes)."
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:101(title)
+msgid "Pound - with AES-NI acceleration"
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:154(para)
+msgid "This stud example enables SSL v3 for client compatibility. The ciphers line can be tweaked based on your needs, however this is a reasonable starting place."
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:192(para)
+msgid "This nginx example requires TLS v1.1 or v1.2 for maximum security. The ssl_ciphers line can be tweaked based on your needs, however this is a reasonable starting place."
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:208(title)
+msgid "Apache"
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:233(para)
+msgid "Compute API SSL endpoint in Apache, which you must pair with a short WSGI script."
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:257(title)
+msgid "HTTP strict transport security"
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:258(para)
+msgid "We recommend that all production deployments use HSTS. This header prevents browsers from making insecure connections after they have made a single secure one. If you have deployed your HTTP services on a public or an untrusted domain, HSTS is especially important. To enable HSTS, configure your web server to send a header like this with all requests:"
+msgstr ""
+
+#: ./doc/security-guide/ch020_ssl-everywhere.xml:260(para)
+msgid "Start with a short timeout of 1 day during testing, and raise it to one year after testing has shown that you haven't introduced problems for users. Note that once this header is set to a large timeout, it is (by design) very difficult to disable."
+msgstr ""
+
+#: ./doc/security-guide/bk-openstack-sec-guide.xml:6(title)
+msgid "OpenStack Security Guide"
+msgstr ""
+
+#: ./doc/security-guide/bk-openstack-sec-guide.xml:14(orgname) ./doc/security-guide/bk-openstack-sec-guide.xml:19(holder)
+msgid "OpenStack Foundation"
+msgstr ""
+
+#: ./doc/security-guide/bk-openstack-sec-guide.xml:18(year)
+msgid "2013"
+msgstr ""
+
+#: ./doc/security-guide/bk-openstack-sec-guide.xml:21(releaseinfo)
+msgid "current"
+msgstr ""
+
+#: ./doc/security-guide/bk-openstack-sec-guide.xml:22(productname)
+msgid "OpenStack"
+msgstr ""
+
+#: ./doc/security-guide/bk-openstack-sec-guide.xml:26(remark)
+msgid "Copyright details are filled in by the template."
+msgstr ""
+
+#: ./doc/security-guide/bk-openstack-sec-guide.xml:31(para)
+msgid "This book provides best practices and conceptual information about securing an OpenStack cloud."
+msgstr ""
+
+#: ./doc/security-guide/bk-openstack-sec-guide.xml:38(date)
+msgid "2013-12-02"
+msgstr ""
+
+#: ./doc/security-guide/bk-openstack-sec-guide.xml:42(para)
+msgid "Chapter on Object Storage added."
+msgstr ""
+
+#: ./doc/security-guide/bk-openstack-sec-guide.xml:48(date)
+msgid "2013-10-17"
+msgstr ""
+
+#: ./doc/security-guide/bk-openstack-sec-guide.xml:52(para)
+msgid "Havana release."
+msgstr ""
+
+#: ./doc/security-guide/bk-openstack-sec-guide.xml:58(date)
+msgid "2013-07-02"
+msgstr ""
+
+#: ./doc/security-guide/bk-openstack-sec-guide.xml:62(para)
+msgid "Initial creation..."
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch033_securing-neutron-services.xml:40(None) ./doc/security-guide/ch033_securing-neutron-services.xml:45(None)
+msgid "@@image: 'static/1aa-logical-neutron-flow.png'; md5=3589a1ef10ea2bbe189ca90e3c932df2"
+msgstr ""
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml:8(title)
+msgid "Securing OpenStack Networking services"
+msgstr ""
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml:9(para)
+msgid "To secure OpenStack Networking, you must understand how the workflow process for tenant instance creation needs to be mapped to security domains."
+msgstr ""
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml:13(para)
+msgid "There are four main services that interact with OpenStack Networking. In a typical OpenStack deployment these services map to the following security domains:"
+msgstr ""
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml:18(para)
+msgid "OpenStack dashboard: Public and management"
+msgstr ""
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml:21(para)
+msgid "OpenStack Identity: Management"
+msgstr ""
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml:24(para)
+msgid "OpenStack compute node: Management and guest"
+msgstr ""
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml:27(para)
+msgid "OpenStack network node: Management, guest, and possibly public depending upon neutron-plugin in use."
+msgstr ""
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml:31(para)
+msgid "SDN services node: Management, guest and possibly public depending upon product used."
+msgstr ""
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml:49(para)
+msgid "To isolate sensitive data communication between the OpenStack Networking services and other OpenStack core services, configure these communication channels to only allow communication over an isolated management network."
+msgstr ""
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml:54(title)
+msgid "OpenStack Networking service configuration"
+msgstr ""
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml:56(title)
+msgid "Restrict bind address of the API server: neutron-server"
+msgstr ""
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml:57(para)
+msgid "To restrict the interface or IP address on which the OpenStack Networking API service binds a network socket for incoming client connections, specify the bind_host and bind_port in the neutron.conf file as shown:"
+msgstr ""
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml:64(replaceable)
+msgid "IP ADDRESS OF SERVER"
+msgstr ""
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml:70(title)
+msgid "Restrict DB and RPC communication of the OpenStack Networking services"
+msgstr ""
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml:72(para)
+msgid "Various components of the OpenStack Networking services use either the messaging queue or database connections to communicate with other components in OpenStack Networking."
+msgstr ""
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml:77(para)
+msgid "It is recommended that you follow the guidelines provided in the Database Authentication and Access Control chapter in the Database section for all components that require direct DB connections."
+msgstr ""
+
+#: ./doc/security-guide/ch033_securing-neutron-services.xml:82(para)
+msgid "It is recommended that you follow the guidelines provided in the Queue Authentication and Access Control chapter in the Messaging section for all components that require RPC communication."
+msgstr ""
+
+#: ./doc/security-guide/ch063_compliance-activities.xml:8(title)
+msgid "Compliance activities"
+msgstr ""
+
+#: ./doc/security-guide/ch063_compliance-activities.xml:9(para)
+msgid "There are a number of standard activities that will greatly assist with the compliance process. In this chapter we outline some of the most common compliance activities. These are not specific to OpenStack, however we provide references to relevant sections in this book as useful context."
+msgstr ""
+
+#: ./doc/security-guide/ch063_compliance-activities.xml:11(title)
+msgid "Information Security Management system (ISMS)"
+msgstr ""
+
+#: ./doc/security-guide/ch063_compliance-activities.xml:12(para)
+msgid "An Information Security Management System (ISMS) is a comprehensive set of policies and processes that an organization creates and maintains to manage risk to information assets. The most common ISMS for cloud deployments is <link href=\"http://www.27000.org/iso-27001.htm\">ISO/IEC 27001/2</link>, which creates a solid foundation of security controls and practices for achieving more stringent compliance certifications."
+msgstr ""
+
+#: ./doc/security-guide/ch063_compliance-activities.xml:15(title)
+msgid "Risk assessment"
+msgstr ""
+
+#: ./doc/security-guide/ch063_compliance-activities.xml:16(para)
+msgid "A risk assessment framework identifies risks within an organization or service, and specifies ownership of these risks, along with implementation and mitigation strategies. Risks apply to all areas of the service, from technical controls to environmental disaster scenarios and human elements, for example a malicious insider (or rogue employee). Risks can be rated using a variety of mechanisms, for example likelihood vs impact. An OpenStack deployment risk assessment can include control gaps that are described in this book."
+msgstr ""
+
+#: ./doc/security-guide/ch063_compliance-activities.xml:19(title)
+msgid "Access and log reviews"
+msgstr ""
+
+#: ./doc/security-guide/ch063_compliance-activities.xml:20(para)
+msgid "Periodic access and log reviews are required to ensure authentication, authorization, and accountability in a service deployment. Specific guidance for OpenStack on these topics are discussed in-depth in the logging section."
+msgstr ""
+
+#: ./doc/security-guide/ch063_compliance-activities.xml:23(title)
+msgid "Backup and disaster recovery"
+msgstr ""
+
+#: ./doc/security-guide/ch063_compliance-activities.xml:24(para)
+msgid "Disaster Recovery (DR) and Business Continuity Planning (BCP) plans are common requirements for ISMS and compliance activities. These plans must be periodically tested as well as documented. In OpenStack key areas are found in the management security domain, and anywhere that single points of failure (SPOFs) can be identified. See the section on secure backup and recovery for additional details."
+msgstr ""
+
+#: ./doc/security-guide/ch063_compliance-activities.xml:27(title)
+msgid "Security training"
+msgstr ""
+
+#: ./doc/security-guide/ch063_compliance-activities.xml:28(para)
+msgid "Annual, role-specific, security training is a mandatory requirement for almost all compliance certifications and attestations. To optimise the effectiveness of security training, a common method is to provide role specific training, for example to developers, operational personnel, and non-technical employees. Additional cloud security or OpenStack security training based on this hardening guide would be ideal."
+msgstr ""
+
+#: ./doc/security-guide/ch063_compliance-activities.xml:31(title)
+msgid "Security reviews"
+msgstr ""
+
+#: ./doc/security-guide/ch063_compliance-activities.xml:32(para)
+msgid "As OpenStack is a popular open source project, much of the codebase and architecture has been scrutinized by individual contributors, organizations and enterprises. This can be advantageous from a security perspective, however the need for security reviews is still a critical consideration for service providers, as deployments vary, and security is not always the primary concern for contributors. A comprehensive security review process may include architectural review, threat modelling, source code analysis and penetration testing. There are many techniques and recommendations for conducting security reviews that can be found publicly posted. A well-tested example is the <link href=\"http://www.microsoft.com/security/sdl/process/release.aspx\">Microsoft SDL</link>, created as part of the Microsoft Trustworthy Computing Initiative."
+msgstr ""
+
+#: ./doc/security-guide/ch063_compliance-activities.xml:48(title) ./doc/security-guide/ch012_configuration-management.xml:16(title)
+msgid "Vulnerability management"
+msgstr ""
+
+#: ./doc/security-guide/ch063_compliance-activities.xml:49(para)
+msgid "Security updates are critical to any IaaS deployment, whether private or public. Vulnerable systems expand attack surfaces, and are obvious targets for attackers. Common scanning technologies and vulnerability notification services can help mitigate this threat. It is important that scans are authenticated and that mitigation strategies extend beyond simple perimeter hardening. Multi-tenant architectures such as OpenStack are particularly prone to hypervisor vulnerabilities, making this a critical part of the system for vulnerability management. See the section on instance isolation for additional details."
+msgstr ""
+
+#: ./doc/security-guide/ch063_compliance-activities.xml:52(title)
+msgid "Data classification"
+msgstr ""
+
+#: ./doc/security-guide/ch063_compliance-activities.xml:53(para)
+msgid "Data Classification defines a method for classifying and handling information, often to protect customer information from accidental or deliberate theft, loss, or inappropriate disclosure. Most commonly this involves classifying information as sensitive or non-sensitive, or as personally identifiable information (PII). Depending on the context of the deployment various other classifying criteria may be used (government, health-care etc). The underlying principle is that data classifications are clearly defined and in-use. The most common protective mechanisms include industry standard encryption technologies. See the data security section for additional details."
+msgstr ""
+
+#: ./doc/security-guide/ch063_compliance-activities.xml:56(title)
+msgid "Exception process"
+msgstr ""
+
+#: ./doc/security-guide/ch063_compliance-activities.xml:57(para)
+msgid "An exception process is an important component of an ISMS. When certain actions are not compliant with security policies that an organization has defined, they must be logged. Appropriate justification, description and mitigation details need to be included, and signed off by appropriate authorities. OpenStack default configurations may vary in meeting various compliance criteria, areas that fail to meet compliance requirements should be logged, with potential fixes considered for contribution to the community."
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch004_book-introduction.xml:113(None) ./doc/security-guide/ch004_book-introduction.xml:118(None)
+msgid "@@image: 'static/marketecture-diagram.png'; md5=4ab13a64f80c210be3120abc5c7aee8a"
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:8(title)
+msgid "Introduction to OpenStack"
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:9(para)
+msgid "This guide provides security insight into OpenStack deployments. The intended audience is cloud architects, deployers, and administrators. In addition, cloud users will find the guide both educational and helpful in provider selection, while auditors will find it useful as a reference document to support their compliance certification efforts. This guide is also recommended for anyone interested in cloud security."
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:16(para)
+msgid "Each OpenStack deployment embraces a wide variety of technologies, spanning Linux distributions, database systems, messaging queues, OpenStack components themselves, access control policies, logging services, security monitoring tools, and much more. It should come as no surprise that the security issues involved are equally diverse, and their in-depth analysis would require several guides. We strive to find a balance, providing enough context to understand OpenStack security issues and their handling, and provide external references for further information. The guide could be read from start to finish or sampled as necessary like a reference."
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:27(para)
+msgid "We briefly introduce the kinds of clouds: private, public, and hybrid before presenting an overview of the OpenStack components and their related security concerns in the remainder of the chapter."
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:32(title)
+msgid "Cloud types"
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:33(para)
+msgid "OpenStack is a key enabler in adoption of cloud technology and has several common deployment use cases. These are commonly known as Public, Private, and Hybrid models. The following sections use the National Institute of Standards and Technology (NIST) <link href=\"http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf\">definition of cloud</link> to introduce these different types of cloud as they apply to OpenStack."
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:42(title)
+msgid "Public cloud"
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:43(para)
+msgid "According to NIST, a public cloud is one in which the infrastructure is open to the general public for consumption. OpenStack public clouds are typically run by a service provider and can be consumed by individuals, corporations, or any paying customer. A public cloud provider may expose a full set of features such as software-defined networking, block storage, in addition to multiple instance types. Due to the nature of public clouds, they are exposed to a higher degree of risk. As a consumer of a public cloud you should validate that your selected provider has the necessary certifications, attestations, and other regulatory considerations. As a public cloud provider, depending on your target customers, you may be subject to one or more regulations. Additionally, even if not required to meet regulatory requirements, a provider should ensure tenant isolation as well as protecting management infrastructure from external attacks."
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:61(title)
+msgid "Private cloud"
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:62(para)
+msgid "At the opposite end of the spectrum is the private cloud. As NIST defines it, a private cloud is provisioned for exclusive use by a single organization comprising multiple consumers, such as business units. It may be owned, managed, and operated by the organization, a third-party, or some combination of them, and it may exist on or off premises. Private cloud use cases are diverse, as such, their individual security concerns vary."
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:72(title)
+msgid "Community cloud"
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:73(para)
+msgid "NIST defines a community cloud as one whose infrastructure is provisioned for the exclusive use by a specific community of consumers from organizations that have shared concerns. For example, mission, security requirements, policy, and compliance considerations. It may be owned, managed, and operated by one or more of the organizations in the community, a third-party, or some combination of them, and it may exist on or off premises."
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:83(title)
+msgid "Hybrid cloud"
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:84(para)
+msgid "A hybrid cloud is defined by NIST as a composition of two or more distinct cloud infrastructures, such as private, community, or public, that remain unique entities, but are bound together by standardized or proprietary technology that enables data and application portability, such as cloud bursting for load balancing between clouds. For example an online retailer may have their advertising and catalogue presented on a public cloud that allows for elastic provisioning. This would enable them to handle seasonal loads in a flexible, cost-effective fashion. Once a customer begins to process their order, they are transferred to the more secure private cloud backend that is PCI compliant."
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:96(para)
+msgid "For the purposes of this document, we treat Community and Hybrid similarly, dealing explicitly only with the extremes of Public and Private clouds from a security perspective. Your security measures depend where your deployment falls upon the private public continuum."
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:104(title)
+msgid "OpenStack service overview"
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:105(para)
+msgid "OpenStack embraces a modular architecture to provide a set of core services that facilitates scalability and elasticity as core design tenets. This chapter briefly reviews OpenStack components, their use cases and security considerations."
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:122(title) ./doc/security-guide/ch026_compute.xml:8(title)
+msgid "Compute"
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:123(para)
+msgid "OpenStack Compute service (nova) provides services to support the management of virtual machine instances at scale, instances that host multi-tiered applications, dev/test environments, \"Big Data\" crunching Hadoop clusters, and/or high performance computing."
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:128(para)
+msgid "The Compute service facilitates this management through an abstraction layer that interfaces with supported hypervisors, which we address later on in more detail."
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:131(para)
+msgid "Later in the guide, we focus generically on the virtualization stack as it relates to hypervisors."
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:133(para)
+msgid "For information about the current state of feature support, see <link href=\"https://wiki.openstack.org/wiki/HypervisorSupportMatrix\">OpenStack Hypervisor Support Matrix</link>."
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:137(para)
+msgid "The security of Compute is critical for an OpenStack deployment. Hardening techniques should include support for strong instance isolation, secure communication between Compute sub-components, and resiliency of public-facing <glossterm>API</glossterm> endpoints."
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:144(title) ./doc/security-guide/ch027_storage.xml:8(title)
+msgid "Object Storage"
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:145(para)
+msgid "The OpenStack Object Storage service (swift) provides support for storing and retrieving arbitrary data in the cloud. The Object Storage service provides both a native API and an Amazon Web Services S3 compatible API. The service provides a high degree of resiliency through data replication and can handle petabytes of data."
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:151(para)
+msgid "It is important to understand that object storage differs from traditional file system storage. It is best used for static data such as media files (MP3s, images, videos), virtual machine images, and backup files."
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:155(para)
+msgid "Object security should focus on access control and encryption of data in transit and at rest. Other concerns may relate to system abuse, illegal or malicious content storage, and cross authentication attack vectors."
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:161(title)
+msgid "Block Storage"
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:162(para)
+msgid "The OpenStack Block Storage service (cinder) provides persistent block storage for compute instances. The Block Storage service is responsible for managing the life-cycle of block devices, from the creation and attachment of volumes to instances, to their release."
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:167(para)
+msgid "Security considerations for block storage are similar to that of object storage."
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:171(title)
+msgid "OpenStack Networking"
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:172(para)
+msgid "The OpenStack Networking service (neutron, previously called quantum) provides various networking services to cloud users (tenants) such as IP address management, <glossterm>DNS</glossterm>, <glossterm>DHCP</glossterm>, load balancing, and security groups (network access rules, like firewall policies). It provides a framework for software defined networking (SDN) that allows for pluggable integration with various networking solutions."
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:180(para)
+msgid "OpenStack Networking allows cloud tenants to manage their guest network configurations. Security concerns with the networking service include network traffic isolation, availability, integrity and confidentiality."
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:186(title) ./doc/security-guide/ch025_web-dashboard.xml:8(title) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:33(title) ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:120(para)
+msgid "Dashboard"
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:187(para)
+msgid "The OpenStack dashboard (horizon) provides a web-based interface for both cloud administrators and cloud tenants. Through this interface administrators and tenants can provision, manage, and monitor cloud resources. Horizon is commonly deployed in a public facing manner with all the usual security concerns of public web portals."
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:195(title)
+msgid "Identity service"
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:196(para)
+msgid "The OpenStack Identity service (keystone) is a <emphasis role=\"bold\">shared service</emphasis> that provides authentication and authorization services throughout the entire cloud infrastructure. The Identity service has pluggable support for multiple forms of authentication."
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:201(para)
+msgid "Security concerns here pertain to trust in authentication, management of authorization tokens, and secure communication."
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:206(title)
+msgid "Image Service"
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:207(para)
+msgid "The OpenStack Image Service (glance) provides disk image management services. The Image Service provides image discovery, registration, and delivery services to the Compute service, as needed."
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:211(para)
+msgid "Trusted processes for managing the life cycle of disk images are required, as are all the previously mentioned issues with respect to data security."
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:216(title)
+msgid "Other supporting technology"
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:217(para)
+msgid "OpenStack relies on messaging for internal communication between several of its services. By default, OpenStack uses message queues based on the Advanced Message Queue Protocol (<glossterm baseform=\"Advanced Message Queuing Protocol (AMQP)\">AMQP </glossterm>). Similar to most OpenStack services, it supports pluggable components. Today the implementation backend could be <glossterm>RabbitMQ</glossterm>, <glossterm>Qpid</glossterm>, or <glossterm>ZeroMQ</glossterm>."
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:226(para)
+msgid "As most management commands flow through the message queueing system, it is a primary security concern for any OpenStack deployment. Message queueing security is discussed in detail later in this guide."
+msgstr ""
+
+#: ./doc/security-guide/ch004_book-introduction.xml:230(para)
+msgid "Several of the components use databases though it is not explicitly called out. Securing the access to the databases and their contents is yet another security concern, and consequently discussed in more detail later in this guide."
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:8(title)
+msgid "Certification and compliance statements"
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:9(para)
+msgid "Compliance and security are not exclusive, and must be addressed together. OpenStack deployments are unlikely to satisfy compliance requirements without security hardening. The listing below provides an OpenStack architect foundational knowledge and guidance to achieve compliance against commercial and government certifications and standards."
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:17(title)
+msgid "Commercial standards"
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:18(para)
+msgid "For commercial deployments of OpenStack, it is recommended that SOC 1/2 combined with ISO 2700 1/2 be considered as a starting point for OpenStack certification activities. The required security activities mandated by these certifications facilitate a foundation of security best practices and common control criteria that can assist in achieving more stringent compliance activities, including government attestations and certifications."
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:26(para)
+msgid "After completing these initial certifications, the remaining certifications are more deployment specific. For example, clouds processing credit card transactions will need PCI-DSS, clouds storing health care information require HIPAA, and clouds within the federal government may require FedRAMP/FISMA, and ITAR, certifications."
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:34(title)
+msgid "SOC 1 (SSAE 16) / ISAE 3402"
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:35(para)
+msgid "Service Organization Controls (SOC) criteria are defined by the <link href=\"http://www.aicpa.org/\">American Institute of Certified Public Accountants</link> (AICPA). SOC controls assess relevant financial statements and assertions of a service provider, such as compliance with the Sarbanes-Oxley Act. SOC 1 is a replacement for Statement on Auditing Standards No. 70 (SAS 70) Type II report. These controls commonly include physical data centers in scope."
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:44(para)
+msgid "There are two types of SOC 1 reports:"
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:47(para) ./doc/security-guide/ch064_certifications-compliance-statements.xml:84(para)
+msgid "Type 1 – report on the fairness of the presentation of management's description of the service organization's system and the suitability of the design of the controls to achieve the related control objectives included in the description as of a specified date."
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:54(para)
+msgid "Type 2 – report on the fairness of the presentation of management's description of the service organization's system and the suitability of the design and operating effectiveness of the controls to achieve the related control objectives included in the description throughout a specified period"
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:62(para)
+msgid "For more details see the <link href=\"http://www.aicpa.org/InterestAreas/FRC/AssuranceAdvisoryServices/Pages/AICPASOC1Report.aspx\">AICPA Report on Controls at a Service Organization Relevant to User Entities’ Internal Control over Financial Reporting</link>."
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:70(title)
+msgid "SOC 2"
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:71(para)
+msgid "Service Organization Controls (SOC) 2 is a self attestation of controls that affect the security, availability, and processing integrity of the systems a service organization uses to process users' data and the confidentiality and privacy of information processed by these system. Examples of users are those responsible for governance of the service organization; customers of the service organization; regulators; business partners; suppliers and others who have an understanding of the service organization and its controls."
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:81(para)
+msgid "There are two types of SOC 2 reports:"
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:91(para)
+msgid "Type 2 – report on the fairness of the presentation of management's description of the service organization's system and the suitability of the design and operating effectiveness of the controls to achieve the related control objectives included in the description throughout a specified period."
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:99(para)
+msgid "For more details see the <link href=\"http://www.aicpa.org/InterestAreas/FRC/AssuranceAdvisoryServices/Pages/AICPASOC2Report.aspx\">AICPA Report on Controls at a Service Organization Relevant to Security, Availability, Processing Integrity, Confidentiality or Privacy</link>."
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:108(title)
+msgid "SOC 3"
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:109(para)
+msgid "Service Organization Controls (SOC) 3 is a trust services report for service organizations. These reports are designed to meet the needs of users who want assurance on the controls at a service organization related to security, availability, processing integrity, confidentiality, or privacy but do not have the need for or the knowledge necessary to make effective use of a SOC 2 Report. These reports are prepared using the AICPA/Canadian Institute of Chartered Accountants (CICA) Trust Services Principles, Criteria, and Illustrations for Security, Availability, Processing Integrity, Confidentiality, and Privacy. Because they are general use reports, SOC 3 Reports can be freely distributed or posted on a website as a seal."
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:121(para)
+msgid "For more details see the <link href=\"http://www.aicpa.org/InterestAreas/FRC/AssuranceAdvisoryServices/Pages/AICPASOC3Report.aspx\">AICPA Trust Services Report for Service Organizations</link>."
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:128(title)
+msgid "ISO 27001/2"
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:129(para)
+msgid "The ISO/IEC 27001/2 standards replace BS7799-2, and are specifications for an Information Security Management System (ISMS). An ISMS is a comprehensive set of policies and processes that an organization creates and maintains to manage risk to information assets. These risks are based upon the confidentiality, integrity, and availability (CIA) of user information. The CIA security triad has been used as a foundation for much of the chapters in this book."
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:137(para)
+msgid "For more details see <link href=\"http://www.27000.org/iso-27001.htm\">ISO 27001</link>."
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:143(title)
+msgid "HIPAA / HITECH"
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:144(para)
+msgid "The Health Insurance Portability and Accountability Act (HIPAA) is a United States congressional act that governs the collection, storage, use and destruction of patient health records. The act states that Protected Health Information (PHI) must be rendered \"unusable, unreadable, or indecipherable\" to unauthorized persons and that encryption for data 'at-rest' and 'inflight' should be addressed."
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:151(para)
+msgid "HIPAA is not a certification, rather a guide for protecting healthcare data. Similar to the PCI-DSS, the most important issues with both PCI and HIPPA is that a breach of credit card information, and health data, does not occur. In the instance of a breach the cloud provider will be scrutinized for compliance with PCI and HIPPA controls. If proven compliant, the provider can be expected to immediately implement remedial controls, breach notification responsibilities, and significant expenditure on additional compliance activities. If not compliant, the cloud provider can expect on-site audit teams, fines, potential loss of merchant ID (PCI), and massive reputation impact."
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:163(para)
+msgid "Users or organizations that possess PHI must support HIPAA requirements and are HIPAA covered entities. If an entity intends to use a service, or in this case, an OpenStack cloud that might use, store or have access to that PHI, then a Business Associate Agreement must be signed. The BAA is a contract between the HIPAA covered entity and the OpenStack service provider that requires the provider to handle that PHI in accordance with HIPAA requirements. If the service provider does not handle the PHI, such as with security controls and hardening, then they are subject to HIPAA fines and penalties."
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:174(para)
+msgid "OpenStack architects interpret and respond to HIPAA statements, with data encryption remaining a core practice. Currently this would require any protected health information contained within an OpenStack deployment to be encrypted with industry standard encryption algorithms. Potential future OpenStack projects such as object encryption will facilitate HIPAA guidelines for compliance with the act."
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:181(para)
+msgid "For more details see the <link href=\"https://www.cms.gov/Regulations-and-Guidance/HIPAA-Administrative-Simplification/HIPAAGenInfo/downloads/HIPAALaw.pdf\">Health Insurance Portability And Accountability Act</link>."
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:187(title)
+msgid "PCI-DSS"
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:188(para)
+msgid "The Payment Card Industry Data Security Standard (PCI DSS) is defined by the Payment Card Industry Standards Council, and created to increase controls around card holder data to reduce credit card fraud. Annual compliance validation is assessed by an external Qualified Security Assessor (QSA) who creates a Report on Compliance (ROC), or by a Self-Assessment Questionnaire (SAQ) dependent on volume of card-holder transactions."
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:196(para)
+msgid "OpenStack deployments which stores, processes, or transmits payment card details are in scope for the PCI-DSS. All OpenStack components that are not properly segmented from systems or networks that handle payment data fall under the guidelines of the PCI-DSS. Segmentation in the context of PCI-DSS does not support multi-tenancy, but rather physical separation (host/network)."
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:203(para)
+msgid "For more details see <link href=\"https://www.pcisecuritystandards.org/security_standards/\">PCI security standards</link>."
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:209(title)
+msgid "Government standards"
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:212(title)
+msgid "FedRAMP"
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:213(para)
+msgid "\"The <link href=\"http://www.fedramp.gov\">Federal Risk and Authorization Management Program</link> (FedRAMP) is a government-wide program that provides a standardized approach to security assessment, authorization, and continuous monitoring for cloud products and services\". NIST 800-53 is the basis for both FISMA and FedRAMP which mandates security controls specifically selected to provide protection in cloud environments. FedRAMP can be extremely intensive from specificity around security controls, and the volume of documentation required to meet government standards."
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:223(para)
+msgid "For more details see <link href=\"http://www.gsa.gov/portal/category/102371\">http://www.gsa.gov/portal/category/102371</link>."
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:229(title)
+msgid "ITAR"
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:230(para)
+msgid "The International Traffic in Arms Regulations (ITAR) is a set of United States government regulations that control the export and import of defense-related articles and services on the United States Munitions List (USML) and related technical data. ITAR is often approached by cloud providers as an \"operational alignment\" rather than a formal certification. This typically involves implementing a segregated cloud environment following practices based on the NIST 800-53 framework, as per FISMA requirements, complemented with additional controls restricting access to \"U.S. Persons\" only and background screening."
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:241(para)
+msgid "For more details see <link href=\"http://pmddtc.state.gov/regulations_laws/itar_official.html\">http://pmddtc.state.gov/regulations_laws/itar_official.html</link>."
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:247(title)
+msgid "FISMA"
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:248(para)
+msgid "The Federal Information Security Management Act requires that government agencies create a comprehensive plan to implement numerous government security standards, and was enacted within the E-Government Act of 2002. FISMA outlines a process, which utilizing multiple NIST publications, prepares an information system to store and process government data."
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:255(para)
+msgid "This process is broken apart into three primary categories:"
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:259(para)
+msgid "<emphasis role=\"bold\">System categorization:</emphasis> The information system will receive a security category as defined in Federal Information Processing Standards Publication 199 (FIPS 199). These categories reflect the potential impact of system compromise."
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:267(para)
+msgid "<emphasis role=\"bold\">Control selection:</emphasis>Based upon system security category as defined in FIPS 199, an organization utilizes FIPS 200 to identify specific security control requirements for the information system. For example, if a system is categorized as “moderate” a requirement may be introduced to mandate “secure passwords.”"
+msgstr ""
+
+#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:276(para)
+msgid "<emphasis role=\"bold\">Control tailoring:</emphasis> Once system security controls are identified, an OpenStack architect will utilize NIST 800-53 to extract tailored control selection. For example, specification of what constitutes a “secure password.”"
+msgstr ""
+
+#: ./doc/security-guide/ch065_privacy.xml:7(title)
+msgid "Privacy"
+msgstr ""
+
+#: ./doc/security-guide/ch065_privacy.xml:8(para)
+msgid "Privacy is an increasingly important element of a compliance program. Businesses are being held to a higher standard by their customers, who have increased interest in understanding how their data is treated from a privacy perspective."
+msgstr ""
+
+#: ./doc/security-guide/ch065_privacy.xml:9(para)
+msgid "An OpenStack deployment will likely need to demonstrate compliance with an organization’s Privacy Policy, with the U.S. – E.U. Safe Harbor framework, the ISO/IEC 29100:2011 privacy framework or with other privacy-specific guidelines. In the U.S. the AICPA has <link href=\"http://www.aicpa.org/interestareas/informationtechnology/resources/privacy/generallyacceptedprivacyprinciples/\">defined 10 privacy areas of focus</link>, OpenStack deployments within a commercial environment may desire to attest to some or all of these principles."
+msgstr ""
+
+#: ./doc/security-guide/ch065_privacy.xml:10(para)
+msgid "To aid OpenStack architects in the protection of personal data, it is recommended that OpenStack architects review the NIST publication 800-122, titled \"<emphasis>Guide to Protecting the Confidentiality of Personally Identifiable Information (PII)</emphasis>.\" This guide steps through the process of protecting:"
+msgstr ""
+
+#: ./doc/security-guide/ch065_privacy.xml:12(para)
+msgid "\"<emphasis>any information about an individual maintained by an agency, including (1) any information that can be used to distinguish or trace an individual‘s identity, such as name, social security number, date and place of birth, mother‘s maiden name, or biometric records; and (2) any other information that is linked or linkable to an individual, such as medical, educational, financial, and employment information</emphasis>\""
+msgstr ""
+
+#: ./doc/security-guide/ch065_privacy.xml:14(para)
+msgid "Comprehensive privacy management requires significant preparation, thought and investment. Additional complications are introduced when building global OpenStack clouds, for example navigating the differences between U.S. and more restrictive E.U. privacy laws. In addition, extra care needs to be taken when dealing with sensitive PII that may include information such as credit card numbers or medical records. This sensitive data is not only subject to privacy laws but also regulatory and governmental regulations. By deferring to established best practices, including those published by governments, a holistic privacy management policy may be created and practiced for OpenStack deployments."
+msgstr ""
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:12(title)
+msgid "Networking services security best practices"
+msgstr ""
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:13(para)
+msgid "This section discusses OpenStack Networking configuration best practices as they apply to tenant network security within your OpenStack deployment."
+msgstr ""
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:15(title)
+msgid "Tenant network services workflow"
+msgstr ""
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:16(para)
+msgid "OpenStack Networking provides users real self services of network resources and configurations. It is important that cloud architects and operators evaluate their design use cases in providing users the ability to create, update, and destroy available network resources."
+msgstr ""
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:19(title)
+msgid "Networking resource policy engine"
+msgstr ""
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:20(para)
+msgid "A policy engine and its configuration file, <filename>policy.json</filename>, within OpenStack Networking provides a method to provide finer grained authorization of users on tenant networking methods and objects. It is important that cloud architects and operators evaluate their design and use cases in providing users and tenants the ability to create, update, and destroy available network resources as it has a tangible effect on tenant network availability, network security, and overall OpenStack security. For a more detailed explanation of OpenStack Networking policy definition, please refer to the <link href=\"http://docs.openstack.org/admin-guide-cloud/content/section_networking_auth.html\">Authentication and authorization section</link> in the <citetitle>OpenStack Cloud Administrator Guide</citetitle>."
+msgstr ""
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:34(para)
+msgid "It is important to review the default networking resource policy and modify the policy appropriately for your security posture."
+msgstr ""
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:37(para)
+msgid "If your deployment of OpenStack provides multiple external access points into different security domains it is important that you limit the tenant's ability to attach multiple vNICs to multiple external access pointsthis would bridge these security domains and could lead to unforeseen security compromise. It is possible mitigate this risk by utilizing the host aggregates functionality provided by OpenStack Compute or through splitting the tenant VMs into multiple tenant projects with different virtual network configurations."
+msgstr ""
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:48(title)
+msgid "Security groups"
+msgstr ""
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:49(para)
+msgid "The OpenStack Networking Service provides security group functionality using a mechanism that is more flexible and powerful than the security group capabilities built into OpenStack Compute. Thus, when using OpenStack Networking, <filename>nova.conf</filename> should always disable built-in security groups and proxy all security group calls to the OpenStack Networking API. Failure to do so will result in conflicting security policies being simultaneously applied by both services. To proxy security groups to OpenStack Networking, use the following configuration values:"
+msgstr ""
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:61(para)
+msgid "<option>firewall_driver</option> must be set to <literal>nova.virt.firewall.NoopFirewallDriver</literal> so that <systemitem class=\"service\">nova-compute</systemitem> does not perform iptables-based filtering itself."
+msgstr ""
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:67(para)
+msgid "<option>security_group_api</option> must be set to <literal>neutron</literal> so that all security group requests are proxied to the OpenStack Networking service."
+msgstr ""
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:73(para)
+msgid "Security groups and security group rules allow administrators and tenants the ability to specify the type of traffic and direction (ingress/egress) that is allowed to pass through a virtual interface port. A security group is a container for security group rules. When a virtual interface port is created in OpenStack Networking it is associated with a security group. If a security group is not specified, the port will be associated with a 'default' security group. By default this group will drop all ingress traffic and allow all egress. Rules can be added to this group in order to change the behaviour."
+msgstr ""
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:74(para)
+msgid "When using the security group API through OpenStack Compute, security groups are applied to all virtual interface ports on an instance. The reason for this is that OpenStack Compute security group APIs are instance based and not virtual interface port based as OpenStack Networking."
+msgstr ""
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:77(title)
+msgid "Quotas"
+msgstr ""
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:79(para)
+msgid "Quotas provide the ability to limit the number of network resources available to tenants. You can enforce default quotas for all tenants. The <filename>/etc/neutron/neutron.conf</filename> includes these options for quota:"
+msgstr ""
+
+#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:108(para)
+msgid "OpenStack Networking also supports per-tenant quotas limit through a quota extension API. To enable per-tenant quotas, you must set the <literal>quota_driver</literal> option in <filename>neutron.conf</filename>."
+msgstr ""
+
+#: ./doc/security-guide/ch037_risks.xml:8(title)
+msgid "Message queuing architecture"
+msgstr ""
+
+#: ./doc/security-guide/ch037_risks.xml:9(para)
+msgid "Message queuing services facilitate inter-process communication in OpenStack. OpenStack supports these message queuing service back ends:"
+msgstr ""
+
+#: ./doc/security-guide/ch037_risks.xml:14(para)
+msgid "RabbitMQ"
+msgstr ""
+
+#: ./doc/security-guide/ch037_risks.xml:17(para)
+msgid "Qpid"
+msgstr ""
+
+#: ./doc/security-guide/ch037_risks.xml:20(para)
+msgid "ZeroMQ or 0MQ"
+msgstr ""
+
+#: ./doc/security-guide/ch037_risks.xml:23(para)
+msgid "Both RabbitMQ and Qpid are Advanced Message Queuing Protocol (AMQP) frameworks, which provide message queues for peer-to-peer communication. Queue implementations are typically deployed as a centralized or decentralized pool of queue servers. ZeroMQ provides direct peer-to-peer communication through TCP sockets."
+msgstr ""
+
+#: ./doc/security-guide/ch037_risks.xml:29(para)
+msgid "Message queues effectively facilitate command and control functions across OpenStack deployments. Once access to the queue is permitted no further authorization checks are performed. Services accessible through the queue do validate the contexts and tokens within the actual message payload. However, you must note the expiration date of the token because tokens are potentially re-playable and can authorize other services in the infrastructure."
+msgstr ""
+
+#: ./doc/security-guide/ch037_risks.xml:37(para)
+msgid "OpenStack does not support message-level confidence, such as message signing. Consequently, you must secure and authenticate the message transport itself. For high-availability (HA) configurations, you must perform queue-to-queue authentication and encryption."
+msgstr ""
+
+#: ./doc/security-guide/ch037_risks.xml:42(para)
+msgid "With ZeroMQ messaging, IPC sockets are used on individual machines. Because these sockets are vulnerable to attack, ensure that the cloud operator has secured them."
+msgstr ""
+
 #. When image changes, this message will be marked fuzzy or untranslated for you.
 #. It doesn't matter what you translate it to: it's not used at all.
 #: ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:35(None) ./doc/security-guide/ch002_why-and-how-we-wrote-this-book.xml:38(None)
@@ -211,6 +1087,1686 @@ msgstr ""
 msgid "Learn more about how to contribute to the OpenStack docs: <link href=\"http://wiki.openstack.org/Documentation/HowTo\">http://wiki.openstack.org/Documentation/HowTo</link>."
 msgstr ""
 
+#: ./doc/security-guide/ch012_configuration-management.xml:8(title)
+msgid "Continuous systems management"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:9(para)
+msgid "A cloud will always have bugs. Some of these will be security problems. For this reason, it is critically important to be prepared to apply security updates and general software updates. This involves smart use of configuration management tools, which are discussed below. This also involves knowing when an upgrade is necessary."
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:17(para)
+msgid "For announcements regarding security relevant changes, subscribe to the <link href=\"http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-announce\">OpenStack Announce mailing list</link>. The security notifications are also posted through the downstream packages for example through Linux distributions that you may be subscribed to as part of the package updates."
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:24(para)
+msgid "The OpenStack components are only a small fraction of the software in a cloud. It is important to keep up to date with all of these other components, too. While the specific data sources will be deployment specific, the key idea is to ensure that a cloud administrator subscribes to the necessary mailing lists for receiving notification of any related security updates. Often this is as simple as tracking an upstream Linux distribution."
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:36(para)
+msgid "OpenStack Security Advisories (OSSA) are created by the OpenStack Vulnerability Management Team (VMT). They pertain to security holes in core OpenStack services. More information on the VMT can be found here: <link href=\"https://wiki.openstack.org/wiki/Vulnerability_Management\">https://wiki.openstack.org/wiki/Vulnerability_Management</link>"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:44(para)
+msgid "OpenStack Security Notes (OSSN) were created by the OpenStack Security Group (OSSG) to support the work of the VMT. OSSN address issues in supporting software and common deployment configurations. They're referenced throughout this guide. Security Notes are archived at <link href=\"https://launchpad.net/ossn/\">https://launchpad.net/ossn/</link>"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:33(para)
+msgid "OpenStack releases security information through two channels. <placeholder-1/>"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:56(title)
+msgid "Triage"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:57(para)
+msgid "After you are notified of a security update, the next step is to determine how critical this update is to a given cloud deployment. In this case, it is useful to have a pre-defined policy. Existing vulnerability rating systems such as the common vulnerability scoring system (CVSS) v2 do not properly account for cloud deployments."
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:63(para)
+msgid "In this example we introduce a scoring matrix that places vulnerabilities in three categories: Privilege Escalation, Denial of Service and Information Disclosure. Understanding the type of vulnerability and where it occurs in your infrastructure will enable you to make reasoned response decisions."
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:69(para)
+msgid "Privilege Escalation describes the ability of a user to act with the privileges of some other user in a system, bypassing appropriate authorization checks. For example, a standard Linux user running code or performing an operation that allows them to conduct further operations with the privileges of the root users on the system."
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:75(para)
+msgid "Denial of Service refers to an exploited vulnerability that may cause service or system disruption. This includes both distributed attacks to overwhelm network resources, and single-user attacks that are typically caused through resource allocation bugs or input induced system failure flaws."
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:80(para)
+msgid "Information Disclosure vulnerabilities reveal information about your system or operations. These vulnerabilities range from debugging information disclosure, to exposure of critical security data, such as authentication credentials and passwords."
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:96(emphasis)
+msgid "Attacker position / Privilege level"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:102(emphasis)
+msgid "External"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:103(emphasis)
+msgid "Cloud user"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:105(emphasis)
+msgid "Cloud admin"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:107(emphasis)
+msgid "Control plane"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:111(emphasis)
+msgid "Privilege elevation (3 levels)"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:113(para) ./doc/security-guide/ch012_configuration-management.xml:121(para) ./doc/security-guide/ch012_configuration-management.xml:122(para) ./doc/security-guide/ch012_configuration-management.xml:129(para) ./doc/security-guide/ch012_configuration-management.xml:130(para) ./doc/security-guide/ch012_configuration-management.xml:131(para)
+msgid "Critical"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:114(para) ./doc/security-guide/ch012_configuration-management.xml:115(para) ./doc/security-guide/ch012_configuration-management.xml:116(para) ./doc/security-guide/ch012_configuration-management.xml:123(para) ./doc/security-guide/ch012_configuration-management.xml:124(para) ./doc/security-guide/ch012_configuration-management.xml:132(para)
+msgid "n/a"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:119(emphasis)
+msgid "Privilege elevation (2 levels)"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:127(emphasis)
+msgid "Privilege elevation (1 level)"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:135(emphasis)
+msgid "Denial of service"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:137(para)
+msgid "High"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:138(para)
+msgid "Medium"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:139(para) ./doc/security-guide/ch012_configuration-management.xml:140(para) ./doc/security-guide/ch012_configuration-management.xml:148(para)
+msgid "Low"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:143(emphasis)
+msgid "Information disclosure"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:145(para) ./doc/security-guide/ch012_configuration-management.xml:146(para)
+msgid "Critical / high"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:147(para)
+msgid "Medium / low"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:152(para)
+msgid "This table illustrates a generic approach to measuring the impact of a vulnerability based on where it occurs in your deployment and the effect. For example, a single level privilege escalation on a Compute API node potentially allows a standard user of the API to escalate to have the same privileges as the root user on the node."
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:158(para)
+msgid "We suggest that cloud administrators use this table as a model to help define which actions to take for the various security levels. For example, a critical-level security update might require the cloud to be upgraded on a specified time line, whereas a low-level update might be more relaxed."
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:165(title)
+msgid "Testing the updates"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:166(para)
+msgid "You should test any update before you deploy it in a production environment. Typically this requires having a separate test cloud setup that first receives the update. This cloud should be as close to the production cloud as possible, in terms of software and hardware. Updates should be tested thoroughly in terms of performance impact, stability, application impact, and more. Especially important is to verify that the problem theoretically addressed by the update, such as a specific vulnerability, is actually fixed."
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:177(title)
+msgid "Deploying the updates"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:178(para)
+msgid "Once the updates are fully tested, they can be deployed to the production environment. This deployment should be fully automated using the configuration management tools described below."
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:185(title)
+msgid "Configuration management"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:186(para)
+msgid "A production quality cloud should always use tools to automate configuration and deployment. This eliminates human error, and allows the cloud to scale much more rapidly. Automation also helps with continuous integration and testing."
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:191(para)
+msgid "When building an OpenStack cloud it is strongly recommended to approach your design and implementation with a configuration management tool or framework in mind. Configuration management allows you to avoid the many pitfalls inherent in building, managing, and maintaining an infrastructure as complex as OpenStack. By producing the manifests, cookbooks, or templates required for a configuration management utility, you are able to satisfy a number of documentation and regulatory reporting requirements. Further, configuration management can also function as part of your BCP and DR plans wherein you can rebuild a node or service back to a known state in a DR event or given a compromise."
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:203(para)
+msgid "Additionally, when combined with a version control system such as Git or SVN, you can track changes to your environment over time and re-mediate unauthorized changes that may occur. For example, a <filename>nova.conf</filename> file or other configuration file falls out of compliance with your standard, your configuration management tool can revert or replace the file and bring your configuration back into a known state. Finally a configuration management tool can also be used to deploy updates; simplifying the security patch process. These tools have a broad range of capabilities that are useful in this space. The key point for securing your cloud is to choose a tool for configuration management and use it."
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:215(para)
+msgid "There are many configuration management solutions; at the time of this writing there are two in the marketplace that are robust in their support of OpenStack environments: <glossterm>Chef</glossterm> and <glossterm>Puppet</glossterm>. A non-exhaustive listing of tools in this space is provided below:"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:223(para)
+msgid "Chef"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:226(para)
+msgid "Puppet"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:229(para)
+msgid "Salt Stack"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:232(para)
+msgid "Ansible"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:236(title)
+msgid "Policy changes"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:237(para)
+msgid "Whenever a policy or configuration management is changed, it is good practice to log the activity, and backup a copy of the new set. Often, such policies and configurations are stored in a version controlled repository such as git."
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:244(title)
+msgid "Secure backup and recovery"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:245(para)
+msgid "It is important to include Backup procedures and policies in the overall System Security Plan. For a good overview of OpenStack's Backup and Recovery capabilities and procedures, please refer to the OpenStack Operations Guide."
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:250(title) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:60(title) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:117(title) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:150(title) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:174(title) ./doc/security-guide/ch026_compute.xml:45(title) ./doc/security-guide/ch026_compute.xml:90(title)
+msgid "Security considerations"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:253(para)
+msgid "Ensure only authenticated users and backup clients have access to the backup server."
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:257(para)
+msgid "Use data encryption options for storage and transmission of backups."
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:261(para)
+msgid "Use a dedicated and hardened backup servers. The logs for the backup server must be monitored daily and accessible by only few individuals."
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:266(para)
+msgid "Test data recovery options regularly. One of the things that can be restored from secured backups is the images. In case of a compromise, the best practice would be to terminate running instances immediately and then relaunch the instances from the images in the secured backup repository."
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:276(title) ./doc/security-guide/ch058_forensicsincident-response.xml:48(title) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:90(title) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:160(title) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:199(title) ./doc/security-guide/ch026_compute.xml:60(title) ./doc/security-guide/ch026_compute.xml:106(title)
+msgid "References"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:279(para)
+msgid "<citetitle>OpenStack Operations Guide</citetitle> on <link href=\"http://docs.openstack.org/trunk/openstack-ops/content/backup_and_recovery.html\">backup and recovery</link>"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:287(link)
+msgid "http://www.sans.org/reading_room/whitepapers/backup/security-considerations-enterprise-level-backups_515"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:291(link)
+msgid "OpenStack Security Primer"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:297(title)
+msgid "Security auditing tools"
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:298(para)
+msgid "Security auditing tools can complement the configuration management tools. Security auditing tools automate the process of verifying that a large number of security controls are satisfied for a given system configuration. These tools help to bridge the gap from security configuration guidance documentation (for example, the STIG and NSA Guides) to a specific system installation. For example, <link href=\"https://fedorahosted.org/scap-security-guide/\">SCAP</link> can compare a running system to a pre-defined profile. SCAP outputs a report detailing which controls in the profile were satisfied, which ones failed, and which ones were not checked."
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:310(para)
+msgid "Combining configuration management and security auditing tools creates a powerful combination. The auditing tools will highlight deployment concerns. And the configuration management tools simplify the process of changing each system to address the audit concerns. Used together in this fashion, these tools help to maintain a cloud that satisfies security requirements ranging from basic hardening to compliance validation."
+msgstr ""
+
+#: ./doc/security-guide/ch012_configuration-management.xml:317(para)
+msgid "Configuration management and security auditing tools will introduce another layer of complexity into the cloud. This complexity brings additional security concerns with it. We view this as an acceptable risk trade-off, given their security benefits. Securing the operational use of these tools is beyond the scope of this guide."
+msgstr ""
+
+#: ./doc/security-guide/ch047_data-encryption.xml:8(title)
+msgid "Data encryption"
+msgstr ""
+
+#: ./doc/security-guide/ch047_data-encryption.xml:9(para)
+msgid "The option exists for implementors to encrypt tenant data wherever it is stored on disk or transported over a network. This is above and beyond the general recommendation that users encrypt their own data before sending it to their provider."
+msgstr ""
+
+#: ./doc/security-guide/ch047_data-encryption.xml:10(para)
+msgid "The importance of encrypting data on behalf of tenants is largely related to the risk assumed by a provider that an attacker could access tenant data. There may be requirements here in government, as well as requirements per-policy, in private contract, or even in case law in regard to private contracts for public cloud providers. It is recommended that a risk assessment and legal consul advised before choosing tenant encryption policies."
+msgstr ""
+
+#: ./doc/security-guide/ch047_data-encryption.xml:11(para)
+msgid "Per-instance or per-object encryption is preferable over, in descending order, over per-project, per-tenant, per-host, and per-cloud aggregations. This recommendation is inverse to the complexity and difficulty of implementation. Presently, in some projects it is difficult or impossible to implement encryption as loosely granular as even per-tenant. We recommend implementors make a best-effort in encrypting tenant data."
+msgstr ""
+
+#: ./doc/security-guide/ch047_data-encryption.xml:12(para)
+msgid "Often, data encryption relates positively to the ability to reliably destroy tenant and per-instance data, simply by throwing away the keys. It should be noted that in doing so, it becomes of great importance to destroy those keys in a reliable and secure manner."
+msgstr ""
+
+#: ./doc/security-guide/ch047_data-encryption.xml:13(para)
+msgid "Opportunities to encrypt data for users are present:"
+msgstr ""
+
+#: ./doc/security-guide/ch047_data-encryption.xml:15(para) ./doc/security-guide/ch047_data-encryption.xml:25(title) ./doc/security-guide/ch046_data-residency.xml:31(para)
+msgid "Object Storage objects"
+msgstr ""
+
+#: ./doc/security-guide/ch047_data-encryption.xml:18(para) ./doc/security-guide/ch047_data-encryption.xml:31(title)
+msgid "Block Storage volumes and instance ephemeral filesystems"
+msgstr ""
+
+#: ./doc/security-guide/ch047_data-encryption.xml:21(para) ./doc/security-guide/ch047_data-encryption.xml:37(title)
+msgid "Network data"
+msgstr ""
+
+#: ./doc/security-guide/ch047_data-encryption.xml:26(para)
+msgid "The ability to encrypt objects in Object Storage is presently limited to disk-level encryption per node. However, there does exist third-party extensions and modules for per-object encryption. These modules have been proposed upstream, but have not per this writing been formally accepted. Below are some pointers:"
+msgstr ""
+
+#: ./doc/security-guide/ch047_data-encryption.xml:27(link)
+msgid "https://github.com/Mirantis/swift-encrypt"
+msgstr ""
+
+#: ./doc/security-guide/ch047_data-encryption.xml:28(link)
+msgid "http://www.mirantis.com/blog/on-disk-encryption-prototype-for-openstack-swift/"
+msgstr ""
+
+#: ./doc/security-guide/ch047_data-encryption.xml:32(para)
+msgid "The ability to encrypt volumes depends on the service backends chosen. Some backends may not support this at all."
+msgstr ""
+
+#: ./doc/security-guide/ch047_data-encryption.xml:33(para)
+msgid "As both block storage and compute support LVM backed storage, we can easily provide an example applicable to both systems. In deployments using LVM, encryption may be performed against the backing physical volumes. An encrypted block device would be created using the standard Linux tools, with the LVM physical volume (PV) created on top of the decrypted block device using pvcreate. Then, the vgcreate or vgmodify tool may be used to add the encrypted physical volume to an LVM volume group (VG)."
+msgstr ""
+
+#: ./doc/security-guide/ch047_data-encryption.xml:34(para)
+msgid "A feature aimed for the Havana release provides encryption of the VM's data before it is written to disk. This allows the privacy of data to be maintained while residing on the storage device. The idea is similar to how self-encrypting drives work. This feature presents a normal block storage device to the VM but encrypts the bytes in the virtualization host before writing them to the disk. The block server operates exactly as it does when reading and writing unencrypted blocks, except special handling will be required for Block Storage features such as snapshots and live migration. Note that this feature uses an independent key manager."
+msgstr ""
+
+#: ./doc/security-guide/ch047_data-encryption.xml:38(para)
+msgid "Tenant data for compute could be encrypted over IPSec or other tunnels. This is not functionality common or standard in OpenStack, but is an option available to motivated and interested implementors."
+msgstr ""
+
+#: ./doc/security-guide/ch047_data-encryption.xml:42(para)
+msgid "Block storage supports a variety of mechanisms for supplying mountable volumes. It is outside the scope of this guide to specify recommendations for each Block Storage backend driver. For the purpose of performance, many storage protocols are unencrypted. Some protocols such as iSCSI can provide authentication and encrypted sessions, it is our recommendation to enable these features."
+msgstr ""
+
+#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml:8(title)
+msgid "Case studies: API endpoints"
+msgstr ""
+
+#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml:9(para)
+msgid "In this case study we discuss how Alice and Bob would address endpoint configuration to secure their private and public clouds. Alice's cloud is not publicly accessible, but she is still concerned about securing the endpoints against improper use. Bob's cloud, being public, must take measures to reduce the risk of attacks by external adversaries."
+msgstr ""
+
+#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml:11(title) ./doc/security-guide/ch066_case-studies-compliance.xml:11(title) ./doc/security-guide/ch015_case-studies-management.xml:28(title) ./doc/security-guide/ch056_case-studies-instance-management.xml:11(title) ./doc/security-guide/ch035_case-studies-networking.xml:11(title) ./doc/security-guide/ch028_case-studies-identity-management.xml:18(title) ./doc/security-guide/ch059_case-studies-monitoring-logging.xml:11(title) ./doc/security-guide/ch018_case-studies-pkissl.xml:11(title) ./doc/security-guide/ch039_case-studies-messaging.xml:11(title) ./doc/security-guide/ch053_case-studies-instance-isolation.xml:11(title) ./doc/security-guide/ch009_case-studies.xml:11(title) ./doc/security-guide/ch049_case-studies-tenant-data.xml:17(title) ./doc/security-guide/ch044_case-studies-database.xml:11(title)
+msgid "Alice's private cloud"
+msgstr ""
+
+#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml:12(para)
+msgid "Alice's organization requires that the security architecture protect the access to the public and private endpoints, so she elects to use the Apache SSL proxy on both public and internal services. Alice's organization has implemented its own certificate authority. Alice contacts the PKI office in her agency that manages her PKI and certificate issuance. Alice obtains certificates issued by this CA and configures the services within both the public and management security domains to use these certificates. Since Alice's OpenStack deployment exists entirely on a disconnected from the Internet network, she makes sure to remove all default CA bundles that contain external public CA providers to ensure the OpenStack services only accept client certificates issued by her agency's CA. Alice has registered all of the services in the Identity service's catalog, using the internal URLs for access by internal services. She has installed host-based intrusion detection on all of the API endpoints."
+msgstr ""
+
+#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml:33(title) ./doc/security-guide/ch066_case-studies-compliance.xml:18(title) ./doc/security-guide/ch015_case-studies-management.xml:33(title) ./doc/security-guide/ch056_case-studies-instance-management.xml:17(title) ./doc/security-guide/ch035_case-studies-networking.xml:29(title) ./doc/security-guide/ch028_case-studies-identity-management.xml:43(title) ./doc/security-guide/ch059_case-studies-monitoring-logging.xml:15(title) ./doc/security-guide/ch018_case-studies-pkissl.xml:15(title) ./doc/security-guide/ch039_case-studies-messaging.xml:15(title) ./doc/security-guide/ch053_case-studies-instance-isolation.xml:17(title) ./doc/security-guide/ch009_case-studies.xml:16(title) ./doc/security-guide/ch049_case-studies-tenant-data.xml:50(title) ./doc/security-guide/ch044_case-studies-database.xml:15(title)
+msgid "Bob's public cloud"
+msgstr ""
+
+#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml:34(para)
+msgid "Bob must also protect the access to the public and private endpoints, so he elects to use the Apache SSL proxy on both public and internal services. On the public services, he has configured the certificate key files with certificates signed by a well-known Certificate Authority. He has used his organization's self-signed CA to sign certificates in the internal services on the Management network. Bob has registered his services in the Identity service's catalog, using the internal URLs for access by internal services. Bob's public cloud runs services on SELinux, which he has configured with a mandatory access control policy to reduce the impact of any publicly accessible services that may be compromised. He has also configured the endpoints with a host-based IDS."
+msgstr ""
+
+#: ./doc/security-guide/ch066_case-studies-compliance.xml:8(title)
+msgid "Case studies: compliance"
+msgstr ""
+
+#: ./doc/security-guide/ch066_case-studies-compliance.xml:9(para)
+msgid "In this case study we discuss how Alice and Bob would address common compliance requirements. The preceding chapter refers to a wide variety of compliance certifications and standards. Alice will address compliance in a private cloud, while Bob will be focused on compliance for a public cloud."
+msgstr ""
+
+#: ./doc/security-guide/ch066_case-studies-compliance.xml:12(para)
+msgid "Alice is building an OpenStack private cloud for the United States government, specifically to provide elastic compute environments for signal processing. Alice has researched government compliance requirements, and has identified that her private cloud will be required to certify against FISMA and follow the FedRAMP accreditation process, which is required for all federal agencies, departments and contractors to become a Certified Cloud Provider (CCP). In this particular scenario for signal processing, the FISMA controls required will most likely be FISMA High, which indicates possible \"severe or catastrophic adverse effects\" should the information system become compromised. In addition to FISMA Moderate controls Alice must ensure her private cloud is FedRAMP certified, as this is a requirement for all agencies that currently utilize, or host federal information within a cloud environment."
+msgstr ""
+
+#: ./doc/security-guide/ch066_case-studies-compliance.xml:13(para)
+msgid "To meet these strict government regulations Alice undertakes a number of activities. Scoping of requirements is particularly important due to the volume of controls that must be implemented, which will be defined in NIST Publication 800-53."
+msgstr ""
+
+#: ./doc/security-guide/ch066_case-studies-compliance.xml:14(para)
+msgid "All technology within her private cloud must be FIPS certified technology, as mandated within NIST 800-53 and FedRAMP. As the U.S. Department of Defense is involved, Security Technical Implementation Guides (STIGs) will come into play, which are the configuration standards for DOD IA and IA-enabled devices / systems. Alice notices a number of complications here as there is no STIG for OpenStack, so she must address several underlying requirements for each OpenStack service; for example, the networking SRG and Application SRG will both be applicable (<link href=\"http://iase.disa.mil/srgs/index.html\">list of SRGs</link>). Other critical controls include ensuring that all identities in the cloud use PKI, that SELinux is enabled, that encryption exists for all wire-level communications, and that continuous monitoring is in place and clearly documented. Alice is not concerned with object encryption, as this will be the tenants responsibility rather than the provider."
+msgstr ""
+
+#: ./doc/security-guide/ch066_case-studies-compliance.xml:15(para)
+msgid "If Alice has adequately scoped and executed these compliance activities, she may begin the process to become FedRAMP compliant by hiring an approved third-party auditor. Typically this process takes up to 6 months, after which she will receive an Authority to Operate and can offer OpenStack cloud services to the government."
+msgstr ""
+
+#: ./doc/security-guide/ch066_case-studies-compliance.xml:19(para)
+msgid "Bob is tasked with compliance for a new OpenStack public cloud deployment, that is focused on providing cloud services to both small developers and startups, as well as large enterprises. Bob recognizes that individual developers are not necessarily concerned with compliance certifications, but to larger enterprises certifications are critical. Specifically Bob desires to achieve SOC 1, SOC 2 Security, as well as ISO 27001/2 as quickly as possible. Bob references the Cloud Security Alliance Cloud Control Matrix (CCM) to assist in identifying common controls across these three certifications (such as periodic access reviews, auditable logging and monitoring services, risk assessment activities, security reviews, etc). Bob then engages an experienced audit team to conduct a gap analysis on the public cloud deployment, reviews the results and fills any gaps identified. Bob works with other team members to ensure that these security controls and activities are regularly conducted for a typical audit period (~6-12 months)."
+msgstr ""
+
+#: ./doc/security-guide/ch066_case-studies-compliance.xml:36(para)
+msgid "At the end of the audit period Bob has arranged for an external audit team to review in-scope security controls at randomly sampled points of time over a 6 month period. The audit team provides Bob with an official report for SOC 1 and SOC 2, and separately for ISO 27001/2. As Bob has been diligent in ensuring security controls are in place for his OpenStack public cloud, there are no additional gaps exposed on the report. Bob can now provide these official reports to his customers under NDA, and advertise that he is SOC 1, SOC 2 and ISO 27001/2 compliant on his website."
+msgstr ""
+
+#: ./doc/security-guide/ch015_case-studies-management.xml:8(title)
+msgid "Case studies: management interfaces"
+msgstr ""
+
+#: ./doc/security-guide/ch015_case-studies-management.xml:9(para)
+msgid "Previously we discussed typical OpenStack management interfaces and associated backplane issues. We will now approach these issues by returning to our Alice and Bob case study. Specifically, we will look into how both Alice and Bob will address:"
+msgstr ""
+
+#: ./doc/security-guide/ch015_case-studies-management.xml:15(para)
+msgid "Cloud administration"
+msgstr ""
+
+#: ./doc/security-guide/ch015_case-studies-management.xml:18(para)
+msgid "Self service"
+msgstr ""
+
+#: ./doc/security-guide/ch015_case-studies-management.xml:21(para)
+msgid "Data replication and recovery"
+msgstr ""
+
+#: ./doc/security-guide/ch015_case-studies-management.xml:24(para)
+msgid "SLA and security monitoring"
+msgstr ""
+
+#: ./doc/security-guide/ch015_case-studies-management.xml:29(para)
+msgid "When building her private cloud, while air-gapped, Alice still needs to consider her service management interfaces. Before deploying her private cloud, Alice has completed her system documentation. Specifically she has identified which OpenStack services will exist in each security domain. From there Alice has further restricted access to management interfaces by deploying a combination of IDS, SSL encryption, and physical network isolation. Additionally, Alice requires high availability and redundant services. Thus, Alice sets up redundant infrastructure for various OpenStack API services."
+msgstr ""
+
+#: ./doc/security-guide/ch015_case-studies-management.xml:30(para)
+msgid "Alice also needs to provide assurances that the physical servers and hypervisors have been built from a known secure state into a well-defined configuration. To enable this, Alice uses a combination of a Configuration Management platform to configure each machine according to the standards and regulations she must comply with. It will also enable Alice to report periodically on the state of her cloud and perform remediation to a known state should anything be out of the ordinary. Additionally, Alice provides hardware assurances by using a PXE system to build her nodes from a known set of base images. During the boot process, Alice provides further assurances by enabling Intel TXT and related trusted boot technologies provided by the hardware."
+msgstr ""
+
+#: ./doc/security-guide/ch015_case-studies-management.xml:34(para)
+msgid "As a public cloud provider, Bob is concerned with both the continuous availability of management interfaces and the security of transactions to the management interfaces. To that end Bob implements multiple redundant OpenStack API endpoints for the services his cloud will run. Additionally on the public network Bob uses SSL to encrypt all transactions between his customers and his cloud interfaces. To isolate his cloud operations Bob has physically isolated his management, instance migration, and storage networks."
+msgstr ""
+
+#: ./doc/security-guide/ch015_case-studies-management.xml:35(para)
+msgid "To ease scaling and reduce management overhead Bob implements a configuration management system. For customer data assurances, Bob offers a backup as a service product as requirements will vary between customers. Finally, Bob does not provide a \"baremetal\" or the ability to schedule an entire node, so to reduce management overhead and increase operational efficiency Bob does not implement any node boot time security."
+msgstr ""
+
+#: ./doc/security-guide/ch006_introduction-to-case-studies.xml:8(title)
+msgid "Introduction to case studies"
+msgstr ""
+
+#: ./doc/security-guide/ch006_introduction-to-case-studies.xml:9(para)
+msgid "This guide refers to two running case studies, which are introduced here and referred to at the end of each chapter."
+msgstr ""
+
+#: ./doc/security-guide/ch006_introduction-to-case-studies.xml:12(title)
+msgid "Case study: Alice, the private cloud builder"
+msgstr ""
+
+#: ./doc/security-guide/ch006_introduction-to-case-studies.xml:13(para)
+msgid "Alice deploys a private cloud for use by a government department in the US. The cloud must comply with relevant standards, such as FedRAMP. The security paperwork requirements for this cloud are very high. It must have no direct access to the internet: its API endpoints, compute instances, and other resources must be exposed to only systems within the department's network, which is entirely air-gapped from all other networks. The cloud can access other network services on the organization's intranet such as the authentication and logging services."
+msgstr ""
+
+#: ./doc/security-guide/ch006_introduction-to-case-studies.xml:25(title)
+msgid "Case study: Bob, the public cloud provider"
+msgstr ""
+
+#: ./doc/security-guide/ch006_introduction-to-case-studies.xml:26(para)
+msgid "Bob is a lead architect for a company that deploys a large greenfield public cloud. This cloud provides IaaS for the masses and enables any consumer with a valid credit card access to utility computing and storage, but the primary focus is enterprise customers. Data privacy concerns are a big priority for Bob as they are seen as a major barrier to large-scale adoption of the cloud by organizations."
+msgstr ""
+
+#: ./doc/security-guide/ch048_key-management.xml:8(title)
+msgid "Key management"
+msgstr ""
+
+#: ./doc/security-guide/ch048_key-management.xml:9(para)
+msgid "To address the often mentioned concern of tenant data privacy and limiting cloud provider liability, there is greater interest within the OpenStack community to make data encryption more ubiquitous. It is relatively easy for an end-user to encrypt their data prior to saving it to the cloud, and this is a viable path for tenant objects such as media files, database archives among others. However, when client side encryption is used for virtual machine images, block storage etc, client intervention is necessary in the form of presenting keys to unlock the data for further use. To seamlessly secure the data and yet have it accessible without burdening the client with having to manage their keys and interactively provide them calls for a key management service within OpenStack. Providing encryption and key management services as part of OpenStack eases data-at-rest security adoption, addresses customer concerns about the privacy and misuse of their data with the added advantage of limiting cloud provider liability. Provider liability is of concern in multi-tenant public clouds with respect to handing over tenant data during a misuse investigation."
+msgstr ""
+
+#: ./doc/security-guide/ch048_key-management.xml:10(para)
+msgid "A key management service is in the early stages of being developed and has a way to go before becoming an official component of OpenStack. Refer to <link href=\"https://github.com/cloudkeep/barbican/wiki/_pages\">https://github.com/cloudkeep/barbican/wiki/_pages</link> for details."
+msgstr ""
+
+#: ./doc/security-guide/ch048_key-management.xml:11(para)
+msgid "It shall support the creation of keys, and their secure saving (with a service master-key). Some of the design questions still being debated are how much of the Key Management Interchange Protocol (KMIP) to support, key formats, and certificate management. The key manager will be pluggable to facilitate deployments that need a third-party Hardware Security Module (HSM)."
+msgstr ""
+
+#: ./doc/security-guide/ch048_key-management.xml:12(para)
+msgid "OpenStack Block Storage, cinder, is the first service looking to integrate with the key manager to provide volume encryption."
+msgstr ""
+
+#: ./doc/security-guide/ch048_key-management.xml:14(title)
+msgid "References:"
+msgstr ""
+
+#: ./doc/security-guide/ch048_key-management.xml:16(link)
+msgid "Barbican"
+msgstr ""
+
+#: ./doc/security-guide/ch048_key-management.xml:19(link)
+msgid "KMIP"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:64(None) ./doc/security-guide/ch013_node-bootstrapping.xml:69(None)
+msgid "@@image: 'static/node-provisioning-pxe.png'; md5=51b76c5aced74f935490b37ba921dc43"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:12(title)
+msgid "Integrity life-cycle"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:13(para)
+msgid "We define integrity life cycle as a deliberate process that provides assurance that we are always running the expected software with the expected configurations throughout the cloud. This process begins with secure bootstrapping and is maintained through configuration management and security monitoring. This chapter provides recommendations on how to approach the integrity life-cycle process."
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:21(title)
+msgid "Secure bootstrapping"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:22(para)
+msgid "Nodes in the cloudincluding compute, storage, network, service, and hybrid nodesshould have an automated provisioning process. This ensures that nodes are provisioned consistently and correctly. This also facilitates security patching, upgrading, bug fixing, and other critical changes. Since this process installs new software that runs at the highest privilege levels in the cloud, it is important to verify that the correct software is installed. This includes the earliest stages of the boot process."
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:31(para)
+msgid "There are a variety of technologies that enable verification of these early boot stages. These typically require hardware support such as the trusted platform module (TPM), Intel Trusted Execution Technology (TXT), dynamic root of trust measurement (DRTM), and Unified Extensible Firmware Interface (UEFI) secure boot. In this book, we will refer to all of these collectively as <emphasis>secure boot technologies</emphasis>. We recommend using secure boot, while acknowledging that many of the pieces necessary to deploy this require advanced technical skills in order to customize the tools for each environment. Utilizing secure boot will require deeper integration and customization than many of the other recommendations in this guide. TPM technology, while common in most business class laptops and desktops for several years, and is now becoming available in servers together with supporting BIOS. Proper planning is essential to a successful secure boot deployment."
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:47(para)
+msgid "A complete tutorial on secure boot deployment is beyond the scope of this book. Instead, here we provide a framework for how to integrate secure boot technologies with the typical node provisioning process. For additional details, cloud architects should refer to the related specifications and software configuration manuals."
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:54(title)
+msgid "Node provisioning"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:55(para)
+msgid "Nodes should use Preboot eXecution Environment (PXE) for provisioning. This significantly reduces the effort required for redeploying nodes. The typical process involves the node receiving various boot stagesthat is progressively more complex software to execute from a server."
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:72(para)
+msgid "We recommend using a separate, isolated network within the management security domain for provisioning. This network will handle all PXE traffic, along with the subsequent boot stage downloads depicted above. Note that the node boot process begins with two insecure operations: DHCP and TFTP. Then the boot process downloads over SSL the remaining information required to deploy the node. This information might include an initramfs and a kernel. This concludes by downloading the remaining information needed to deploy the node. This may be an operating system installer, a basic install managed by <link href=\"http://www.opscode.com/chef/\">Chef</link> or <link href=\"https://puppetlabs.com/\">Puppet</link>, or even a complete file system image that is written directly to disk."
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:86(para)
+msgid "While utilizing SSL during the PXE boot process is somewhat more challenging, common PXE firmware projects, such as iPXE, provide this support. Typically this involves building the PXE firmware with knowledge of the allowed SSL certificate chain(s) so that it can properly validate the server certificate. This raises the bar for an attacker by limiting the number of insecure, plain text network operations."
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:96(title)
+msgid "Verified boot"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:97(para)
+msgid "In general, there are two different strategies for verifying the boot process. Traditional <emphasis>secure boot</emphasis> will validate the code run at each step in the process, and stop the boot if code is incorrect. <emphasis>Boot attestation</emphasis> will record which code is run at each step, and provide this information to another machine as proof that the boot process completed as expected. In both cases, the first step is to measure each piece of code before it is run. In this context, a measurement is effectively a SHA-1 hash of the code, taken before it is executed. The hash is stored in a platform configuration register (PCR) in the TPM."
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:109(para)
+msgid "Note: SHA-1 is used here because this is what the TPM chips support."
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:111(para)
+msgid "Each TPM has at least 24 PCRs. The TCG Generic Server Specification, v1.0, March 2005, defines the PCR assignments for boot-time integrity measurements. The table below shows a typical PCR configuration. The context indicates if the values are determined based on the node hardware (firmware) or the software provisioned onto the node. Some values are influenced by firmware versions, disk sizes, and other low-level information. Therefore, it is important to have good practices in place around configuration management to ensure that each system deployed is configured exactly as desired."
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:131(emphasis)
+msgid "Register"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:132(emphasis)
+msgid "What is measured"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:135(emphasis)
+msgid "Context"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:138(para)
+msgid "PCR-00"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:139(para)
+msgid "Core Root of Trust Measurement (CRTM), BIOS code, Host platform extensions"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:141(para) ./doc/security-guide/ch013_node-bootstrapping.xml:146(para) ./doc/security-guide/ch013_node-bootstrapping.xml:151(para) ./doc/security-guide/ch013_node-bootstrapping.xml:156(para)
+msgid "Hardware"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:144(para)
+msgid "PCR-01"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:145(para)
+msgid "Host platform configuration"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:149(para)
+msgid "PCR-02"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:150(para)
+msgid "Option ROM code"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:154(para)
+msgid "PCR-03"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:155(para)
+msgid "Option ROM configuration and data"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:159(para)
+msgid "PCR-04"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:160(para)
+msgid "Initial Program Loader (IPL) code. For example, master boot record."
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:162(para) ./doc/security-guide/ch013_node-bootstrapping.xml:167(para) ./doc/security-guide/ch013_node-bootstrapping.xml:172(para) ./doc/security-guide/ch013_node-bootstrapping.xml:177(para) ./doc/security-guide/ch013_node-bootstrapping.xml:183(para) ./doc/security-guide/ch013_node-bootstrapping.xml:188(para) ./doc/security-guide/ch013_node-bootstrapping.xml:193(para)
+msgid "Software"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:165(para)
+msgid "PCR-05"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:166(para)
+msgid "IPL code configuration and data"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:170(para)
+msgid "PCR-06"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:171(para)
+msgid "State transition and wake events"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:175(para)
+msgid "PCR-07"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:176(para)
+msgid "Host platform manufacturer control"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:180(para)
+msgid "PCR-08"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:181(para)
+msgid "Platform specific, often kernel, kernel extensions, and drivers"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:186(para)
+msgid "PCR-09"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:187(para)
+msgid "Platform specific, often Initramfs"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:191(para)
+msgid "PCR-10 to PCR-23"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:192(para)
+msgid "Platform specific"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:198(para)
+msgid "At the time of this writing, very few clouds are using secure boot technologies in a production environment. As a result, these technologies are still somewhat immature. We recommend planning carefully in terms of hardware selection. For example, ensure that you have a TPM and Intel TXT support. Then verify how the node hardware vendor populates the PCR values. For example, which values will be available for validation. Typically the PCR values listed under the software context in the table above are the ones that a cloud architect has direct control over. But even these may change as the software in the cloud is upgraded. Configuration management should be linked into the PCR policy engine to ensure that the validation is always up to date."
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:211(para)
+msgid "Each manufacturer must provide the BIOS and firmware code for their servers. Different servers, hypervisors, and operating systems will choose to populate different PCRs. In most real world deployments, it will be impossible to validate every PCR against a known good quantity (\"golden measurement\"). Experience has shown that, even within a single vendor's product line, the measurement process for a given PCR may not be consistent. We recommend establishing a baseline for each server and monitoring the PCR values for unexpected changes. Third-party software may be available to assist in the TPM provisioning and monitoring process, depending upon your chosen hypervisor solution."
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:223(para)
+msgid "The initial program loader (IPL) code will most likely be the PXE firmware, assuming the node deployment strategy outlined above. Therefore, the secure boot or boot attestation process can measure all of the early stage boot code, such as, bios, firmware, and the like, the PXE firmware, and the node kernel. Ensuring that each node has the correct versions of these pieces installed provides a solid foundation on which to build the rest of the node software stack."
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:231(para)
+msgid "Depending on the strategy selected, in the event of a failure the node will either fail to boot or it can report the failure back to another entity in the cloud. For secure boot, the node will fail to boot and a provisioning service within the management security domain must recognize this and log the event. For boot attestation, the node will already be running when the failure is detected. In this case the node should be immediately quarantined by disabling its network access. Then the event should be analyzed for the root cause. In either case, policy should dictate how to proceed after a failure. A cloud may automatically attempt to re-provision a node a certain number of times. Or it may immediately notify a cloud administrator to investigate the problem. The right policy here will be deployment and failure mode specific."
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:247(title)
+msgid "Node hardening"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:248(para)
+msgid "At this point we know that the node has booted with the correct kernel and underlying components. There are many paths for hardening a given operating system deployment. The specifics on these steps are outside of the scope of this book. We recommend following the guidance from a hardening guide specific to your operating system. For example, the <link href=\"http://iase.disa.mil/stigs/\">security technical implementation guides</link> (STIG) and the <link href=\"http://www.nsa.gov/ia/mitigation_guidance/security_configuration_guides/\">NSA guides</link> are useful starting places."
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:258(para)
+msgid "The nature of the nodes makes additional hardening possible. We recommend the following additional steps for production nodes:"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:263(para)
+msgid "Use a read-only file system where possible. Ensure that writeable file systems do not permit execution. This can be handled through the mount options provided in <filename>/etc/fstab</filename>."
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:269(para)
+msgid "Use a mandatory access control policy to contain the instances, the node services, and any other critical processes and data on the node. See the discussions on sVirt / SELinux and AppArmor below."
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:275(para)
+msgid "Remove any unnecessary software packages. This should result in a very stripped down installation because a compute node has a relatively small number of dependencies."
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:281(para)
+msgid "Finally, the node kernel should have a mechanism to validate that the rest of the node starts in a known good state. This provides the necessary link from the boot validation process to validating the entire system. The steps for doing this will be deployment specific. As an example, a kernel module could verify a hash over the blocks comprising the file system before mounting it using <link href=\"https://code.google.com/p/cryptsetup/wiki/DMVerity\">dm-verity</link>."
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:293(title)
+msgid "Runtime verification"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:294(para)
+msgid "Once the node is running, we need to ensure that it remains in a good state over time. Broadly speaking, this includes both configuration management and security monitoring. The goals for each of these areas are different. By checking both, we achieve higher assurance that the system is operating as desired. We discuss configuration management in the management section, and security monitoring below."
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:302(title)
+msgid "Intrusion detection system"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:303(para)
+msgid "Host-based intrusion detection tools are also useful for automated validation of the cloud internals. There are a wide variety of host-based intrusion detection tools available. Some are open source projects that are freely available, while others are commercial. Typically these tools analyze data from a variety of sources and produce security alerts based on rule sets and/or training. Typical capabilities include log analysis, file integrity checking, policy monitoring, and rootkit detection. More advanced -- often custom -- tools can validate that in-memory process images match the on-disk executable and validate the execution state of a running process."
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:315(para)
+msgid "One critical policy decision for a cloud architect is what to do with the output from a security monitoring tool. There are effectively two options. The first is to alert a human to investigate and/or take corrective action. This could be done by including the security alert in a log or events feed for cloud administrators. The second option is to have the cloud take some form of remedial action automatically, in addition to logging the event. Remedial actions could include anything from re-installing a node to performing a minor service configuration. However, automated remedial action can be challenging due to the possibility of false positives."
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:326(para)
+msgid "False positives occur when the security monitoring tool produces a security alert for a benign event. Due to the nature of security monitoring tools, false positives will most certainly occur from time to time. Typically a cloud administrator can tune security monitoring tools to reduce the false positives, but this may also reduce the overall detection rate at the same time. These classic trade-offs must be understood and accounted for when setting up a security monitoring system in the cloud."
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:335(para)
+msgid "The selection and configuration of a host-based intrusion detection tool is highly deployment specific. We recommend starting by exploring the following open source projects which implement a variety of host-based intrusion detection and file monitoring features."
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:343(link)
+msgid "OSSEC"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:347(link)
+msgid "Samhain"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:352(link)
+msgid "Tripwire"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:356(link)
+msgid "AIDE"
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:359(para)
+msgid "Network intrusion detection tools complement the host-based tools. OpenStack doesn't have a specific network IDS built-in, but OpenStack Networking provides a plug-in mechanism to enable different technologies through the Networking API. This plug-in architecture will allow tenants to develop API extensions to insert and configure their own advanced networking services like a firewall, an intrusion detection system, or a VPN between the VMs."
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:367(para)
+msgid "Similar to host-based tools, the selection and configuration of a network-based intrusion detection tool is deployment specific. <link href=\"http://www.snort.org/\">Snort</link> is the leading open source networking intrusion detection tool, and a good starting place to learn more."
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:373(para)
+msgid "There are a few important security considerations for network and host-based intrusion detection systems."
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:377(para)
+msgid "It is important to consider the placement of the Network IDS on the cloud (for example, adding it to the network boundary and/or around sensitive networks). The placement depends on your network environment but make sure to monitor the impact the IDS may have on your services depending on where you choose to add it. Encrypted traffic, such as SSL, cannot generally be inspected for content by a Network IDS. However, the Network IDS may still provide some benefit in identifying anomalous unencrypted traffic on the network."
+msgstr ""
+
+#: ./doc/security-guide/ch013_node-bootstrapping.xml:389(para)
+msgid "In some deployments it may be required to add host-based IDS on sensitive components on security domain bridges. A host-based IDS may detect anomalous activity by compromised or unauthorized processes on the component. The IDS should transmit alert and log information on the Management network."
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:8(title)
+msgid "Networking services"
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:9(para)
+msgid "In the initial architectural phases of designing your OpenStack Network infrastructure it is important to ensure appropriate expertise is available to assist with the design of the physical networking infrastructure, to identify proper security controls and auditing mechanisms."
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:10(para)
+msgid "OpenStack Networking adds a layer of virtualized network services - giving tenants the capability to architect their own, virtual networks. These virtualized services are not as currently as mature as their traditional networking counterparts. It is important to be aware of the current state of these virtualized services and what controls may need to be implemented at the virtualized and traditional network boundary."
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:12(title)
+msgid "L2 isolation using VLANs and tunneling"
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:13(para)
+msgid "OpenStack networking can employ two different mechanisms for traffic segregation on a per tenant/network combination: VLANs (IEEE 802.1Q tagging) or L2 tunnels using GRE encapsulation. Which method you choose for traffic segregation and isolation is determined by the scope and scale of your OpenStack deployment."
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:15(title)
+msgid "VLANs"
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:16(para)
+msgid "VLANs are realized as packets on a specific physical network containing IEEE 802.1Q headers with a specific VLAN ID (VID) field value. VLAN networks sharing the same physical network are isolated from each other at L2, and can even have overlapping IP address spaces. Each distinct physical network supporting VLAN networks is treated as a separate VLAN trunk, with a distinct space of VID values. Valid VID values are 1 through 4094."
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:17(para)
+msgid "VLAN configuration complexity depends on your OpenStack design requirements. In order to allow OpenStack Networking to efficiently use VLANs, you must allocate a VLAN range (one for each tenant) and turn each compute node physical switch port into a VLAN trunk port."
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:19(para)
+msgid "NOTE: If you intend for your network to support more than 4094 tenants VLAN is probably not the correct option for you as multiple 'hacks' are required to extend the VLAN tags to more than 4094 tenants."
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:23(title)
+msgid "L2 tunneling"
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:24(para)
+msgid "Network tunneling encapsulates each tenant/network combination with a unique \"tunnel-id\" that is used to identify the network traffic belonging to that combination. The tenant's L2 network connectivity is independent of physical locality or underlying network design. By encapsulating traffic inside IP packets, that traffic can cross Layer-3 boundaries, removing the need for preconfigured VLANs and VLAN trunking. Tunneling adds a layer of obfuscation to network data traffic, reducing the visibility of individual tenant traffic from a monitoring point of view."
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:25(para)
+msgid "OpenStack Networking currently only supports GRE encapsulation with planned future support of VXLAN due in the Havana release."
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:26(para)
+msgid "The choice of technology to provide L2 isolation is dependent upon the scope and size of tenant networks that will be created in your deployment. If your environment has limited VLAN ID availability or will have a large number of L2 networks, it is our recommendation that you utilize tunneling."
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:30(title)
+msgid "Network services"
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:31(para)
+msgid "The choice of tenant network isolation affects how the network security and control boundary is implemented for tenant services. The following additional network services are either available or currently under development to enhance the security posture of the OpenStack network architecture."
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:33(title)
+msgid "Access control lists"
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:34(para)
+msgid "OpenStack Compute supports tenant network traffic access controls directly when deployed with the legacy nova-network service, or may defer access control to the OpenStack Networking service."
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:35(para)
+msgid "Note, legacy nova-network security groups are applied to all virtual interface ports on an instance using IPTables."
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:36(para)
+msgid "Security groups allow administrators and tenants the ability to specify the type of traffic, and direction (ingress/egress) that is allowed to pass through a virtual interface port. Security groups rules are stateful L2-L4 traffic filters."
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:37(para)
+msgid "It is our recommendation that you enable security groups through OpenStack Networking."
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:41(title)
+msgid "L3 routing and NAT"
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:42(para)
+msgid "OpenStack Networking routers can connect multiple L2 networks, and can also provide a <emphasis>gateway</emphasis> that connects one or more private L2 networks to a shared <emphasis>external</emphasis> network, such as a public network for access to the Internet."
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:43(para)
+msgid "The L3 router provides basic Network Address Translation (NAT) capabilities on <emphasis>gateway</emphasis> ports that uplink the router to external networks. This router SNATs (Static NAT) all traffic by default, and supports floating IPs, which creates a static one-to-one mapping from a public IP on the external network to a private IP on one of the other subnets attached to the router."
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:44(para)
+msgid "It is our recommendation to leverage per tenant L3 routing and Floating IPs for more granular connectivity of tenant VMs."
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:47(title)
+msgid "Quality of Service (QoS)"
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:48(para)
+msgid "The ability to set QoS on the virtual interface ports of tenant instances is a current deficiency for OpenStack Networking. The application of QoS for traffic shaping and rate-limiting at the physical network edge device is insufficient due to the dynamic nature of workloads in an OpenStack deployment and can not be leveraged in the traditional way. QoS-as-a-Service (QoSaaS) is currently in development for the OpenStack Networking Havana release as an experimental feature. QoSaaS is planning to provide the following services:"
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:50(para)
+msgid "Traffic shaping through DSCP markings"
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:53(para)
+msgid "Rate-limiting on a per port/network/tenant basis."
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:56(para)
+msgid "Port mirroring (through open source or third-party plug-ins)"
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:59(para)
+msgid "Flow analysis (through open source or third-party plug-ins)"
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:62(para)
+msgid "Tenant traffic port mirroring or Network Flow monitoring is currently not an exposed feature in OpenStack Networking. There are third-party plug-in extensions that do provide Port Mirroring on a per port/network/tenant basis. If Open vSwitch is used on the networking hypervisor, it is possible to enable sFlow and port mirroring, however it will require some operational effort to implement."
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:65(title)
+msgid "Load balancing"
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:66(para)
+msgid "An experimental feature in the Grizzly release of OpenStack Networking is Load-Balancer-as-a-service (LBaaS). The LBaaS API gives early adopters and vendors a chance to build implementations of the technology. The reference implementation however, is still experimental and should likely not be run in a production environment. The current reference implementation is based on HA-Proxy. There are third-party plug-ins in development for extensions in OpenStack Networking to provide extensive L4-L7 functionality for virtual interface ports."
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:69(title)
+msgid "Firewalls"
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:70(para)
+msgid "FW-as-a-Service (FWaaS) is currently in development for the OpenStack Networking Havana release as an experimental feature. FWaaS will address the need to manage and leverage the rich set of security features provided by typical firewall products which are typically far more comprehensive than what is currently provided by security groups. There are third-party plug-ins in development for extensions in OpenStack Networking to support this."
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:71(para)
+msgid "It is critical during the design of an OpenStack Networking infrastructure to understand the current features and limitations of network services that are available. Understanding where the boundaries of your virtual and physical networks will help you add the required security controls in your environment."
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:75(title)
+msgid "Network services extensions"
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:76(para)
+msgid "Here is a list of known plug-ins provided by the open source community or by SDN companies that work with OpenStack Networking:"
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:77(para)
+msgid "Big Switch Controller plug-in, Brocade neutron plug-in Brocade neutron plug-in, Cisco UCS/Nexus plug-in, Cloudbase Hyper-V plug-in, Extreme Networks plug-in, Juniper Networks neutron plug-in, Linux Bridge plug-in, Mellanox neutron plug-in, MidoNet plug-in, NEC OpenFlow plug-in, Open vSwitch plug-in, PLUMgrid plug-in, Ruijie Networks plug-in, Ryu OpenFlow Controller plug-in, VMware NSX plug-in."
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:86(title)
+msgid "Networking services limitations"
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:87(para)
+msgid "OpenStack Networking has the following known limitations:"
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:90(term)
+msgid "Overlapping IP addresses"
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:92(para)
+msgid "If nodes that run either <systemitem class=\"service\">neutron-l3-agent</systemitem> or <systemitem class=\"service\">neutron-dhcp-agent</systemitem> use overlapping IP addresses, those nodes must use Linux network namespaces. By default, the DHCP and L3 agents use Linux network namespaces. However, if the host does not support these namespaces, run the DHCP and L3 agents on different hosts."
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:102(para)
+msgid "If network namespace support is not present, a further limitation of the L3 agent is that only a single logical router is supported."
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:109(term)
+msgid "Multi-host DHCP-agent"
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:111(para)
+msgid "OpenStack Networking supports multiple L3 and DHCP agents with load balancing. However, tight coupling of the location of the virtual machine is not supported."
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:119(term)
+msgid "No IPv6 support for L3 agents"
+msgstr ""
+
+#: ./doc/security-guide/ch032_networking-best-practices.xml:121(para)
+msgid "The neutron-l3-agent, used by many plug-ins to implement L3 forwarding, supports only IPv4 forwarding."
+msgstr ""
+
+#: ./doc/security-guide/ch030_state-of-networking.xml:8(title)
+msgid "State of networking"
+msgstr ""
+
+#: ./doc/security-guide/ch030_state-of-networking.xml:9(para)
+msgid "OpenStack Networking in the Grizzly release enables the end-user or tenant to define, utilize, and consume networking resources in new ways that had not been possible in previous OpenStack Networking releases. OpenStack Networking provides a tenant-facing API for defining network connectivity and IP addressing for instances in the cloud in addition to orchestrating the network configuration. With the transition to an API-centric networking service, cloud architects and administrators should take into consideration best practices to secure physical and virtual network infrastructure and services."
+msgstr ""
+
+#: ./doc/security-guide/ch030_state-of-networking.xml:10(para)
+msgid "OpenStack Networking was designed with a plug-in architecture that provides extensibility of the API through open source community or third-party services. As you evaluate your architectural design requirements, it is important to determine what features are available in OpenStack Networking core services, any additional services that are provided by third-party products, and what supplemental services are required to be implemented in the physical infrastructure."
+msgstr ""
+
+#: ./doc/security-guide/ch030_state-of-networking.xml:20(para)
+msgid "This section is a high-level overview of what processes and best practices should be considered when implementing OpenStack Networking. We will talk about the current state of services that are available, what future services will be implemented, and the current limitations in this project."
+msgstr ""
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml:8(title)
+msgid "Forensics and incident response"
+msgstr ""
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml:9(para)
+msgid "A lot of activity goes on within a cloud environment. It is a mix of hardware, operating systems, virtual machine managers, the OpenStack services, cloud-user activity such as creating instances and attaching storage, the network underlying the whole, and finally end-users using the applications running on the various instances."
+msgstr ""
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml:10(para)
+msgid "The generation and collection of logs is an important component of securely monitoring an OpenStack infrastructure. Logs provide visibility into the day-to-day actions of administrators, tenants, and guests, in addition to the activity in the compute, networking, and storage and other components that comprise your OpenStack deployment."
+msgstr ""
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml:11(para)
+msgid "The basics of logging: configuration, setting log level, location of the log files, and how to use and customize logs, as well as how to do centralized collections of logs is well covered in the <link href=\"http://docs.openstack.org/ops/\"><citetitle>OpenStack Operations Guide</citetitle></link>."
+msgstr ""
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml:12(para)
+msgid "Logs are not only valuable for proactive security and continuous compliance activities, but they are also a valuable information source for investigating and responding to incidents."
+msgstr ""
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml:13(para)
+msgid "For instance, analyzing the access logs of Identity Service or its replacement authentication system would alert us to failed logins, their frequency, origin IP, whether the events are restricted to select accounts etc. Log analysis supports detection."
+msgstr ""
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml:14(para)
+msgid "On detection, further action may be to black list an IP, or recommend strengthening user passwords, or even de-activating a user account if it is deemed dormant."
+msgstr ""
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml:16(title)
+msgid "Monitoring use cases"
+msgstr ""
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml:17(para)
+msgid "Monitoring events is more pro-active and provides real-time detection and response. There are several tools to aid in monitoring."
+msgstr ""
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml:18(para)
+msgid "In the case of an OpenStack cloud instance, we need to monitor the hardware, the OpenStack services, and the cloud resource usage. The last stems from wanting to be elastic, to scale to the dynamic needs of the users."
+msgstr ""
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml:19(para)
+msgid "Here are a few important use cases to consider when implementing log aggregation, analysis and monitoring. These use cases can be implemented and monitored through various commercial and open source tools, homegrown scripts, etc. These tools and scripts can generate events that can then be sent to the administrators through email or integrated dashboard. It is important to consider additional use cases that may apply to your specific network and what you may consider anomalous behavior."
+msgstr ""
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml:21(para)
+msgid "Detecting the absence of log generation is an event of high value. Such an event would indicate a service failure or even an intruder who has temporarily switched off logging or modified the log level to hide their tracks."
+msgstr ""
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml:25(para)
+msgid "Application events such as start and/or stop that were unscheduled would also be events to monitor and examine for possible security implications."
+msgstr ""
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml:29(para)
+msgid "OS events on the OpenStack service machines such as user logins, restarts also provide valuable insight into use/misuse"
+msgstr ""
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml:33(para)
+msgid "Being able to detect the load on the OpenStack servers also enables responding by way of introducing additional servers for load balancing to ensure high availability."
+msgstr ""
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml:37(para)
+msgid "Other events that are actionable are networking bridges going down, ip tables being flushed on compute nodes and consequential loss of access to instances resulting in unhappy customers."
+msgstr ""
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml:41(para)
+msgid "To reduce security risks from orphan instances on a user/tenant/domain deletion in the Identity service there is discussion to generate notifications in the system and have OpenStack components respond to these events as appropriate such as terminating instances, disconnecting attached volumes, reclaiming CPU and storage resources etc."
+msgstr ""
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml:44(para)
+msgid "A cloud will host many virtual instances, and monitoring these instances goes beyond hardware monitoring and log files which may just contain CRUD events."
+msgstr ""
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml:45(para)
+msgid "Security monitoring controls such as intrusion detection software, antivirus software, and spyware detection and removal utilities can generate logs that show when and how an attack or intrusion took place. Deploying these tools on the cloud machines provides value and protection. Cloud users, those running instances on the cloud may also want to run such tools on their instances."
+msgstr ""
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml:49(link)
+msgid "http://www.mirantis.com/blog/openstack-monitoring/"
+msgstr ""
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml:50(link)
+msgid "http://blog.sflow.com/2012/01/host-sflow-distributed-agent.html"
+msgstr ""
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml:51(link)
+msgid "http://blog.sflow.com/2009/09/lan-and-wan.html"
+msgstr ""
+
+#: ./doc/security-guide/ch058_forensicsincident-response.xml:52(link)
+msgid "http://blog.sflow.com/2013/01/rapidly-detecting-large-flows-sflow-vs.html"
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:9(para)
+msgid "Horizon is the OpenStack dashboard that provides users a self-service portal to provision their own resources within the limits set by administrators. These include provisioning users, defining instance flavors, uploading VM images, managing networks, setting up security groups, starting instances, and accessing the instances through a console."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:14(para)
+msgid "The dashboard is based on the Django web framework, therefore secure deployment practices for Django apply directly to horizon. This guide provides a popular set of Django security recommendations, further information can be found by reading the <link href=\"https://docs.djangoproject.com/en/1.5/#security\">Django deployment and security documentation</link>."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:21(para)
+msgid "The dashboard ships with reasonable default security settings, and has good <link href=\"http://docs.openstack.org/developer/horizon/topics/deployment.html\">deployment and configuration documentation</link>."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:26(title)
+msgid "Basic web server configuration"
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:27(para)
+msgid "The dashboard should be deployed as a Web Services Gateway Interface (WSGI) application behind an HTTPS proxy such as Apache or nginx. If Apache is not already in use, we recommend nginx since it is lighter weight and easier to configure correctly."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:32(para)
+msgid "When using nginx, we recommend <link href=\"http://docs.gunicorn.org/en/latest/deploy.html\">gunicorn</link> as the wsgi host with an appropriate number of synchronous workers. We strongly advise against deployments using fastcgi, scgi, or uWSGI. We strongly advise against the use of synthetic performance benchmarks when choosing a wsgi server."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:39(para)
+msgid "When using Apache, we recommend <link href=\"https://docs.djangoproject.com/en/1.5/howto/deployment/wsgi/modwsgi/\">mod_wsgi</link> to host dashboard."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:44(title)
+msgid "HTTPS"
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:45(para)
+msgid "Deploy the dashboard behind a secure <glossterm>HTTPS</glossterm> server by using a valid, trusted certificate from a recognized certificate authority (CA). Private organization-issued certificates are only appropriate when the root of trust is pre-installed in all user browsers."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:52(para)
+msgid "Configure HTTP requests to the dashboard domain to redirect to the fully qualified HTTPS URL."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:56(title)
+msgid "HTTP Strict Transport Security (HSTS)"
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:57(para)
+msgid "It is highly recommended to use HTTP Strict Transport Security (HSTS)."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:60(para)
+msgid "If you are using an HTTPS proxy in front of your web server, rather than using an HTTP server with HTTPS functionality, follow the <link href=\"https://docs.djangoproject.com/en/1.5/ref/settings/#secure-proxy-ssl-header\">Django documentation on modifying the SECURE_PROXY_SSL_HEADER variable</link>."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:67(para)
+msgid "See the chapter on PKI/SSL Everywhere for more specific recommendations and server configurations for HTTPS configurations, including the configuration of HSTS."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:72(title)
+msgid "Front end caching"
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:73(para)
+msgid "Since dashboard is rendering dynamic content passed directly from OpenStack API requests, we do not recommend front end caching layers such as varnish. In Django, static media is directly served from Apache or nginx and already benefits from web host caching."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:80(title)
+msgid "Domain names"
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:81(para)
+msgid "Many organizations typically deploy web applications at subdomains of an overarching organization domain. It is natural for users to expect a domain of the form <uri>openstack.example.org</uri>. In this context, there are often many other applications deployed in the same second-level namespace, often serving user-controlled content. This name structure is convenient and simplifies name server maintenance."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:89(para)
+msgid "We strongly recommend deploying horizon to a <emphasis>second-level domain</emphasis>, such as <uri>https://example.com</uri>, and advise against deploying horizon on a <emphasis>shared subdomain</emphasis> of any level, for example <uri>https://openstack.example.org</uri> or <uri>https://horizon.openstack.example.org</uri>. We also advise against deploying to bare internal domains like <uri>https://horizon/</uri>."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:97(para)
+msgid "This recommendation is based on the limitations browser same-origin-policy. The recommendations in this guide cannot effectively protect users against known attacks if dashboard is deployed on a domain which also hosts user-generated content, such as scripts, images, or uploads of any kind, even if the user-generated content is on a different subdomain. This approach is used by most major web presences, such as googleusercontent.com, fbcdn.com, github.io, and twimg.com, to ensure that user generated content stays separate from cookies and security tokens."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:107(para)
+msgid "Additionally, if you decline to follow this recommendation above about second-level domains, it is vital that you avoid the cookie backed session store and employ HTTP Strict Transport Security (HSTS). When deployed on a subdomain, dashboard's security is only as strong as the weakest application deployed on the same second-level domain."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:115(title)
+msgid "Static media"
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:116(para)
+msgid "Dashboard's static media should be deployed to a subdomain of the dashboard domain and served by the web server. The use of an external content delivery network (CDN) is also acceptable. This subdomain should not set cookies or serve user-provided content. The media should also be served with HTTPS."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:121(para)
+msgid "Django media settings are documented at <link href=\"https://docs.djangoproject.com/en/1.5/ref/settings/#static-root\">https://docs.djangoproject.com/en/1.5/ref/settings/#static-root</link>."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:124(para)
+msgid "Dashboard's default configuration uses <link href=\"http://django-compressor.readthedocs.org/\">django_compressor</link> to compress and minify css and JavaScript content before serving it. This process should be statically done before deploying dashboard, rather than using the default in-request dynamic compression and copying the resulting files along with deployed code or to the CDN server. Compression should be done in a non-production build environment. If this is not practical, we recommend disabling resource compression entirely. Online compression dependencies (less, nodejs) should not be installed on production machines."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:138(title)
+msgid "Secret key"
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:139(para)
+msgid "Dashboard depends on a shared SECRET_KEY setting for some security functions. It should be a randomly generated string at least 64 characters long. It must be shared across all active dashboard instances. Compromise of this key may allow a remote attacker to execute arbitrary code. Rotating this key invalidates existing user sessions and caching. Do not commit this key to public repositories."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:148(title)
+msgid "Session back-end"
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:149(para)
+msgid "Horizon's default session back-end (<emphasis>django.contrib.sessions.backends.signed_cookies</emphasis>) stores user data in <emphasis>signed</emphasis> but <emphasis>unencrypted </emphasis>cookies stored in the browser. This approach allows the most simple session backend scaling since each dashboard instance is stateless, but it comes at the cost of <emphasis>storing sensitive access tokens in the client browser</emphasis> and transmitting them with every request. This backend ensures that session data has not been tampered with, but the data itself is not encrypted other than the encryption provided by HTTPS."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:160(para)
+msgid "If your architecture allows it, we recommend using <emphasis>django.contrib.sessions.backends.cache</emphasis> as your session backend with memcache as the cache. Memcache must not be exposed publicly, and should communicate over a secured private channel. If you choose to use the signed cookies backend, refer to the Django documentation understand the security trade-offs."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:167(para)
+msgid "For further details, consult the <link href=\"https://docs.djangoproject.com/en/1.5/topics/http/sessions/#configuring-the-session-engine\">Django session backend documentation</link>."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:172(title)
+msgid "Allowed hosts"
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:173(para)
+msgid "Configure the ALLOWED_HOSTS setting with the domain or domains where the dashboard is available. Failure to configure this setting (especially if not following the recommendation above regarding second level domains) opens the dashboard to a number of serious attacks. Wild card domains should be avoided."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:178(para)
+msgid "For further details, see the <link href=\"https://docs.djangoproject.com/en/1.5/ref/settings/#allowed-hosts\">Django documentation on settings</link>."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:183(title)
+msgid "Cookies"
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:184(para)
+msgid "Session Cookies should be set to HTTPONLY:"
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:186(para)
+msgid "Never configure CSRF or session cookies to have a wild card domain with a leading dot. Horizon's session and CSRF cookie should be secured when deployed with HTTPS:"
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:193(title)
+msgid "Password auto complete"
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:194(para)
+msgid "We recommend that implementers do not change the default password auto complete behavior. Users choose stronger passwords in environments that allow them to use the secure browser password manager. Organizations which forbid the browser password manager should enforce this policy at the desktop level."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:202(title)
+msgid "Cross Site Request Forgery (CSRF)"
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:203(para)
+msgid "Django has a dedicated middleware for <link href=\"https://docs.djangoproject.com/en/1.5/ref/contrib/csrf/#how-it-works\">cross-site request forgery</link> (CSRF)."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:206(para)
+msgid "Dashboard is designed to discourage developers from introducing cross-site scripting vulnerabilities with custom dashboards. However, it is important to audit custom dashboards, especially ones that are javascript-heavy for inappropriate use of the @csrf_exempt decorator. Dashboards which do not follow these recommended security settings should be carefully evaluated before restrictions are relaxed."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:215(title)
+msgid "Cross Site Scripting (XSS)"
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:216(para)
+msgid "Unlike many similar systems, OpenStack dashboard allows the entire Unicode character set in most fields. This means developers have less latitude to make escaping mistakes that open attack vectors for cross-site scripting (XSS)."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:220(para)
+msgid "Dashboard provides tools for developers to avoid creating XSS vulnerabilities, but they only work if developers use them correctly. Audit any custom dashboards, paying particular attention to use of the mark_safe function, use of is_safe with custom template tags, the safe template tag, anywhere auto escape is turned off, and any JavaScript which might evaluate improperly escaped data."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:229(title)
+msgid "Cross Origin Resource Sharing (CORS)"
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:230(para)
+msgid "Configure your web server to send a restrictive CORS header with each response, allowing only the dashboard domain and protocol:"
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:234(para)
+msgid "Never allow the wild card origin."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:237(title)
+msgid "Horizon image upload"
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:238(para)
+msgid "We recommend that implementers <link href=\"http://docs.openstack.org/developer/horizon/topics/deployment.html#file-uploads\">disable HORIZON_IMAGES_ALLOW_UPLOAD</link> unless they have implemented a plan to prevent resource exhaustion and denial of service."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:245(title)
+msgid "Upgrading"
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:246(para)
+msgid "Django security releases are generally well tested and aggressively backwards compatible. In almost all cases, new major releases of Django are also fully backwards compatible with previous releases. Dashboard implementers are strongly encouraged to run the latest stable release of Django with up-to-date security releases."
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:254(title)
+msgid "Debug"
+msgstr ""
+
+#: ./doc/security-guide/ch025_web-dashboard.xml:255(para)
+msgid "Make sure DEBUG is set to False in production. In Django, DEBUG displays stack traces and sensitive web server state information on any exception."
+msgstr ""
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml:8(title)
+msgid "API endpoint configuration recommendations"
+msgstr ""
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml:9(para)
+msgid "This chapter provides recommendations security enhancements for both public and private-facing API endpoints."
+msgstr ""
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml:13(title)
+msgid "Internal API communications"
+msgstr ""
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml:14(para)
+msgid "OpenStack provides both public facing and private API endpoints. By default, OpenStack components use the publicly defined endpoints. The recommendation is to configure these components to use the API endpoint within the proper security domain."
+msgstr ""
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml:20(para)
+msgid "Services select their respective API endpoints based on the OpenStack service catalog. These services might not obey the listed public or internal API end point values. This can lead to internal management traffic being routed to external API endpoints."
+msgstr ""
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml:27(title)
+msgid "Configure internal URLs in Identity service catalog"
+msgstr ""
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml:28(para)
+msgid "The Identity service catalog should be aware of your internal URLs. While this feature is not utilized by default, it may be leveraged through configuration. Additionally, it should be forward-compatible with expectant changes once this behavior becomes the default."
+msgstr ""
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml:35(para)
+msgid "To register an internal URL for an endpoint:"
+msgstr ""
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml:44(title)
+msgid "Configure applications for internal URLs"
+msgstr ""
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml:45(para)
+msgid "You can force some services to use specific API endpoints. Therefore, it is recommended that each OpenStack service communicating to the API of another service must be explicitly configured to access the proper internal API endpoint."
+msgstr ""
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml:51(para)
+msgid "Each project may present an inconsistent way of defining target API endpoints. Future releases of OpenStack seek to resolve these inconsistencies through consistent use of the Identity Service catalog."
+msgstr ""
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml:57(title)
+msgid "Configuration example #1: nova"
+msgstr ""
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml:67(title)
+msgid "Configuration example #2: cinder"
+msgstr ""
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml:73(title)
+msgid "Paste and middleware"
+msgstr ""
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml:74(para)
+msgid "Most API endpoints and other HTTP services in OpenStack use the Python Paste Deploy library. From a securtiy perspective, this library enables manipulation of the request filter pipeline through the application's configuration. Each element in this chain is referred to as <emphasis>middleware</emphasis>. Changing the order of filters in the pipeline or adding additional middleware might have unpredictable security impact."
+msgstr ""
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml:83(para)
+msgid "Commonly, implementers add middleware to extend OpenStack's base functionality. We recommend implementers make careful consideration of the potential exposure introduced by the addition of non-standard software components to their HTTP request pipeline."
+msgstr ""
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml:89(para)
+msgid "For more information about Paste Deploy, see <link href=\"http://pythonpaste.org/deploy/\">http://pythonpaste.org/deploy/</link>."
+msgstr ""
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml:94(title)
+msgid "API endpoint process isolation and policy"
+msgstr ""
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml:95(para)
+msgid "As much as possible, you should isolate API endpoint processes, especially those that reside within the public security domain should be isolated as much as possible. Where deployments allow, API endpoints should be deployed on separate hosts for increased isolation."
+msgstr ""
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml:102(title) ./doc/security-guide/ch038_transport-security.xml:133(title)
+msgid "Namespaces"
+msgstr ""
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml:103(para)
+msgid "Many operating systems now provide compartmentalization support. Linux supports namespaces to assign processes into independent domains. Other parts of this guide cover system compartmentalization in more detail."
+msgstr ""
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml:110(title) ./doc/security-guide/ch038_transport-security.xml:144(title)
+msgid "Network policy"
+msgstr ""
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml:111(para)
+msgid "Because API endpoints typically bridge multiple security domains, you must pay particular attention to the compartmentalization of the API processes. See <xref linkend=\"ch005_security-domains-idp61360\"/> for additional information in this area."
+msgstr ""
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml:117(para)
+msgid "With careful modeling, you can use network ACLs and IDS technologies to enforce explicit point to point communication between network services. As critical cross domain service, this type of explicit enforcement works well for OpenStack's message queue service."
+msgstr ""
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml:123(para)
+msgid "To enforce policies, you can configure services, host-based firewalls (such as iptables), local policy (SELinux or AppArmor), and optionally global network policy."
+msgstr ""
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml:129(title) ./doc/security-guide/ch052_devices.xml:238(title) ./doc/security-guide/ch038_transport-security.xml:149(title)
+msgid "Mandatory access controls"
+msgstr ""
+
+#: ./doc/security-guide/ch021_paste-and-middleware.xml:130(para)
+msgid "You should isolate API endpoint processes from each other and other processes on a machine. The configuration for those processes should be restricted to those processes not only by Discretionary Access Controls, but through Mandatory Access Controls. The goal of these enhanced access control is to aid in the containment and escalation of API endpoint security breaches. With mandatory access controls, such breaches severely limit access to resources and provide earlier alerting on such events."
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch052_devices.xml:305(None) ./doc/security-guide/ch052_devices.xml:309(None)
+msgid "@@image: 'static/sVirt Diagram 1.png'; md5=ffcdbb45d9054670ad4c270a7c7d3925"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:12(title)
+msgid "Hardening the virtualization layers"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:13(para)
+msgid "In the beginning of this chapter we discuss the use of both physical and virtual hardware by instances, the associated security risks, and some recommendations for mitigating those risks. We conclude the chapter with a discussion of sVirt, an open source project for integrating SELinux mandatory access controls with the virtualization components."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:21(title)
+msgid "Physical hardware (PCI passthrough)"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:22(para)
+msgid "Many hypervisors offer a functionality known as PCI passthrough. This allows an instance to have direct access to a piece of hardware on the node. For example, this could be used to allow instances to access video cards offering the compute unified device architecture (CUDA) for high performance computation. This feature carries two types of security risks: direct memory access and hardware infection."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:31(para)
+msgid "Direct memory access (DMA) is a feature that permits certain hardware devices to access arbitrary physical memory addresses in the host computer. Often video cards have this capability. However, an instance should not be given arbitrary physical memory access because this would give it full view of both the host system and other instances running on the same node. Hardware vendors use an input/output memory management unit (IOMMU) to manage DMA access in these situations. Therefore, cloud architects should ensure that the hypervisor is configured to utilize this hardware feature."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:45(para)
+msgid "KVM: <link href=\"http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM\">How to assign devices with VT-d in KVM</link>"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:50(para)
+msgid "Xen: <link href=\"http://wiki.xen.org/wiki/VTd_HowTo\">VTd Howto</link>"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:55(para)
+msgid "The IOMMU feature is marketed as VT-d by Intel and AMD-Vi by AMD."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:59(para)
+msgid "A hardware infection occurs when an instance makes a malicious modification to the firmware or some other part of a device. As this device is used by other instances, or even the host OS, the malicious code can spread into these systems. The end result is that one instance can run code outside of its security domain. This is a potential problem in any hardware sharing scenario. The problem is specific to this scenario because it is harder to reset the state of physical hardware than virtual hardware."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:69(para)
+msgid "Solutions to the hardware infection problem are domain specific. The strategy is to identify how an instance can modify hardware state then determine how to reset any modifications when the instance is done using the hardware. For example, one option could be to re-flash the firmware after use. Clearly there is a need to balance hardware longevity with security as some firmwares will fail after a large number of writes. TPM technology, described in <xref linkend=\"ch013_node-bootstrapping-idp44768\"/>, provides a solution for detecting unauthorized firmware changes. Regardless of the strategy selected, it is important to understand the risks associated with this kind of hardware sharing so that they can be properly mitigated for a given deployment scenario."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:85(para)
+msgid "Additionally, due to the risk and complexities associated with PCI passthrough, it should be disabled by default. If enabled for a specific need, you will need to have appropriate processes in place to ensure the hardware is clean before re-issue."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:93(title)
+msgid "Virtual hardware (QEMU)"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:94(para)
+msgid "When running a virtual machine, virtual hardware is a software layer that provides the hardware interface for the virtual machine. Instances use this functionality to provide network, storage, video, and other devices that may be needed. With this in mind, most instances in your environment will exclusively use virtual hardware, with a minority that will require direct hardware access. The major open source hypervisors use QEMU for this functionality. While QEMU fills an important need for virtualization platforms, it has proven to be a very challenging software project to write and maintain. Much of the functionality in QEMU is implemented with low-level code that is difficult for most developers to comprehend. Furthermore, the hardware virtualized by QEMU includes many legacy devices that have their own set of quirks. Putting all of this together, QEMU has been the source of many security problems, including hypervisor breakout attacks."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:112(para)
+msgid "For the reasons stated above, it is important to take proactive steps to harden QEMU. We recommend three specific steps: minimizing the code base, using compiler hardening, and using mandatory access controls, such as sVirt, SELinux, or AppArmor."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:119(title)
+msgid "Minimizing the QEMU code base"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:120(para)
+msgid "One classic security principle is to remove any unused components from your system. QEMU provides support for many different virtual hardware devices. However, only a small number of devices are needed for a given instance. Most instances will use the virtio devices. However, some legacy instances will need access to specific hardware, which can be specified using glance metadata:"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:133(para)
+msgid "A cloud architect should decide what devices to make available to cloud users. Anything that is not needed should be removed from QEMU. This step requires recompiling QEMU after modifying the options passed to the QEMU configure script. For a complete list of up-to-date options simply run <placeholder-1/> from within the QEMU source directory. Decide what is needed for your deployment, and disable the remaining options."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:144(title)
+msgid "Compiler hardening"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:145(para)
+msgid "The next step is to harden QEMU using compiler hardening options. Modern compilers provide a variety of compile time options to improve the security of the resulting binaries. These features, which we will describe in more detail below, include relocation read-only (RELRO), stack canaries, never execute (NX), position independent executable (PIE), and address space layout randomization (ASLR)."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:154(para)
+msgid "Many modern linux distributions already build QEMU with compiler hardening enabled, so you may want to verify your existing executable before proceeding with the information below. One tool that can assist you with this verification is called <link href=\"http://www.trapkit.de/tools/checksec.html\"><literal>checksec.sh</literal></link>."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:163(term)
+msgid "RELocation Read-Only (RELRO)"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:165(para)
+msgid "Hardens the data sections of an executable. Both full and partial RELRO modes are supported by gcc. For QEMU full RELRO is your best choice. This will make the global offset table read-only and place various internal data sections before the program data section in the resulting executable."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:175(term)
+msgid "Stack canaries"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:177(para)
+msgid "Places values on the stack and verifies their presence to help prevent buffer overflow attacks."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:183(term)
+msgid "Never eXecute (NX)"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:185(para)
+msgid "Also known as Data Execution Prevention (DEP), ensures that data sections of the executable can not be executed."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:192(term)
+msgid "Position Independent Executable (PIE)"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:194(para)
+msgid "Produces a position independent executable, which is necessary for ASLR."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:200(term)
+msgid "Address Space Layout Randomization (ASLR)"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:202(para)
+msgid "This ensures that placement of both code and data regions will be randomized. Enabled by the kernel (all modern linux kernels support ASLR), when the executable is built with PIE."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:210(para)
+msgid "Putting this all together, and adding in some additional useful protections, we recommend the following compiler options for GCC when compiling QEMU:"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:217(para)
+msgid "We recommend testing your QEMU executable file after it is compiled to ensure that the compiler hardening worked properly."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:221(para)
+msgid "Most cloud deployments will not want to build software such as QEMU by hand. It is better to use packaging to ensure that the process is repeatable and to ensure that the end result can be easily deployed throughout the cloud. The references below provide some additional details on applying compiler hardening options to existing packages."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:230(para)
+msgid "DEB packages: <link href=\"http://wiki.debian.org/HardeningWalkthrough\">Hardening Walkthrough</link>"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:233(para)
+msgid "RPM packages: <link href=\"http://fedoraproject.org/wiki/How_to_create_an_RPM_package\">How to create an RPM package</link>"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:239(para)
+msgid "Compiler hardening makes it more difficult to attack the QEMU process. However, if an attacker does succeed, we would like to limit the impact of the attack. Mandatory access controls accomplish this by restricting the privileges on QEMU process to only what is needed. This can be accomplished using sVirt / SELinux or AppArmor. When using sVirt, SELinux is configured to run every QEMU process under a different security context. AppArmor can be configured to provide similar functionality. We provide more details on sVirt in the instance isolation section below."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:253(title)
+msgid "sVirt: SELinux and virtualization"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:254(para)
+msgid "With unique kernel-level architecture and National Security Agency (NSA) developed security mechanisms, KVM provides foundational isolation technologies for multi tenancy. With developmental origins dating back to 2002, the Secure Virtualization (sVirt) technology is the application of SELinux against modern day virtualization. SELinux, which was designed to apply separation control based upon labels, has been extended to provide isolation between virtual machine processes, devices, data files and system processes acting upon their behalf."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:265(para)
+msgid "OpenStack's sVirt implementation aspires to protect hypervisor hosts and virtual machines against two primary threat vectors:"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:270(para)
+msgid "<emphasis role=\"bold\">Hypervisor threats</emphasis> A compromised application running within a virtual machine attacks the hypervisor to access underlying resources. For example, the host OS, applications, or devices within the physical machine. This is a threat vector unique to virtualization and represents considerable risk as the underlying real machine can be compromised due to vulnerability in a single virtual application."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:280(para)
+msgid "<emphasis role=\"bold\">Virtual Machine (multi-tenant) threats</emphasis> A compromised application running within a VM attacks the hypervisor to access/control another virtual machine and its resources. This is a threat vector unique to virtualization and represents considerable risk as a multitude of virtual machine file images could be compromised due to vulnerability in a single application. This virtual network attack is a major concern as the administrative techniques for protecting real networks do not directly apply to the virtual environment."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:293(para)
+msgid "Each KVM-based virtual machine is a process which is labeled by SELinux, effectively establishing a security boundary around each virtual machine. This security boundary is monitored and enforced by the Linux kernel, restricting the virtual machine's access to resources outside of its boundary such as host machine data files or other VMs."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:313(para)
+msgid "As shown above, sVirt isolation is provided regardless of the guest Operating System running inside the virtual machineLinux or Windows VMs can be used. Additionally, many Linux distributions provide SELinux within the operating system, allowing the virtual machine to protect internal virtual resources from threats."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:322(title)
+msgid "Labels and categories"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:323(para)
+msgid "KVM-based virtual machine instances are labelled with their own SELinux data type, known as svirt_image_t. Kernel level protections prevent unauthorized system processes, such as malware, from manipulating the virtual machine image files on disk. When virtual machines are powered off, images are stored as svirt_image_t as shown below:"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:334(para)
+msgid "The <literal>svirt_image_t</literal> label uniquely identifies image files on disk, allowing for the SELinux policy to restrict access. When a KVM-based Compute image is powered on, sVirt appends a random numerical identifier to the image. sVirt is technically capable of assigning numerical identifiers to 524,288 virtual machines per hypervisor node, however OpenStack deployments are highly unlikely to encounter this limitation."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:343(para)
+msgid "This example shows the sVirt category identifier:"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:348(title)
+msgid "Booleans"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:349(para)
+msgid "To ease the administrative burden of managing SELinux, many enterprise Linux platforms utilize SELinux Booleans to quickly change the security posture of sVirt."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:353(para)
+msgid "Red Hat Enterprise Linux-based KVM deployments utilize the following sVirt booleans:"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:361(emphasis)
+msgid "sVirt SELinux Boolean"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:362(emphasis) ./doc/security-guide/ch051_vss-intro.xml:484(td)
+msgid "Description"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:367(para)
+msgid "virt_use_common"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:368(para)
+msgid "Allow virt to use serial/parallel communication ports."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:371(para)
+msgid "virt_use_fusefs"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:372(para)
+msgid "Allow virt to read FUSE mounted files."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:375(para)
+msgid "virt_use_nfs"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:376(para)
+msgid "Allow virt to manage NFS mounted files."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:379(para)
+msgid "virt_use_samba"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:380(para)
+msgid "Allow virt to manage CIFS mounted files."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:383(para)
+msgid "virt_use_sanlock"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:384(para)
+msgid "Allow confined virtual guests to interact with the sanlock."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:387(para)
+msgid "virt_use_sysfs"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:388(para)
+msgid "Allow virt to manage device configuration (PCI)."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:391(para)
+msgid "virt_use_usb"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:392(para)
+msgid "Allow virt to use USB devices."
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:395(para)
+msgid "virt_use_xserver"
+msgstr ""
+
+#: ./doc/security-guide/ch052_devices.xml:396(para)
+msgid "Allow virtual machine to interact with the X Window System."
+msgstr ""
+
+#: ./doc/security-guide/ch056_case-studies-instance-management.xml:8(title)
+msgid "Case studies: instance management"
+msgstr ""
+
+#: ./doc/security-guide/ch056_case-studies-instance-management.xml:9(para)
+msgid "In this case study we discuss how Alice and Bob would architect their clouds with respect to instance entropy, scheduling instances, trusted images, and instance migrations."
+msgstr ""
+
+#: ./doc/security-guide/ch056_case-studies-instance-management.xml:12(para)
+msgid "Alice has a need for lots of high quality entropy in the instances. For this reason, she decides to purchase hardware with Intel Ivy Bridge chip sets that support the RdRand instruction on each compute node. Using the entropy gathering daemon (EGD) and LibVirt's EGD support, Alice ensures that this entropy pool is distributed to the instances on each compute node."
+msgstr ""
+
+#: ./doc/security-guide/ch056_case-studies-instance-management.xml:13(para)
+msgid "For instance scheduling, Alice uses the trusted compute pools to ensure that all cloud workloads are deployed to nodes that presented a proper boot time attestation. Alice decides to disable user permissions for image uploading to help ensure that the images used in the cloud are generated in a known and trusted manner by the cloud administrators."
+msgstr ""
+
+#: ./doc/security-guide/ch056_case-studies-instance-management.xml:14(para)
+msgid "Finally, Alice disables instance migrations as this feature is less critical for the high performance application workloads expected to run in this cloud. This helps avoid the various security concerns related to instance migrations."
+msgstr ""
+
+#: ./doc/security-guide/ch056_case-studies-instance-management.xml:18(para)
+msgid "Bob is aware that entropy will be a concern for some of his customers, such as those in the financial industry. However, due to the added cost and complexity, Bob has decided to forgo integrating hardware entropy into the first iteration of his cloud. He adds hardware entropy as a fast-follow to do for a later improvement for the second generation of his cloud architecture."
+msgstr ""
+
+#: ./doc/security-guide/ch056_case-studies-instance-management.xml:19(para)
+msgid "Bob is interested in ensuring that customers receive a high quality of service. He is concerned that providing too much explicit user control over instance scheduling could negatively impact the quality of service. So he disables this feature. Bob provides images in the cloud from a known trusted source for users to use. Additionally, he also allows users to upload their own images. However, users cannot generally share their images. This helps prevent a user from sharing a malicious image, which could negatively impact the security of other users in the cloud."
+msgstr ""
+
+#: ./doc/security-guide/ch056_case-studies-instance-management.xml:20(para)
+msgid "For migrations, Bob wants to enable secure instance migrations in order to support rolling upgrades with minimal user downtime. Bob ensures that all migrations occur on an isolated VLAN. He plans to defer implementing encrypted migrations until this is better supported in <placeholder-1/> client tools. However, he makes a note to track this carefully and switch to encrypted migrations as soon as possible."
+msgstr ""
+
 #: ./doc/security-guide/ch051_vss-intro.xml:11(title)
 msgid "Hypervisor selection"
 msgstr ""
@@ -623,10 +3179,6 @@ msgstr ""
 msgid "Further, when you evaluate a hypervisor platform, consider the supportability of the hardware on which the hypervisor will run. Additionally, consider the additional features available in the hardware and how those features are supported by the hypervisor you chose as part of the OpenStack deployment. To that end, hypervisors each have their own hardware compatibility lists (HCLs). When selecting compatible hardware it is important to know in advance which hardware-based virtualization technologies are important from a security perspective."
 msgstr ""
 
-#: ./doc/security-guide/ch051_vss-intro.xml:484(td) ./doc/security-guide/ch052_devices.xml:362(emphasis)
-msgid "Description"
-msgstr ""
-
 #: ./doc/security-guide/ch051_vss-intro.xml:485(td)
 msgid "Technology"
 msgstr ""
@@ -831,416 +3383,470 @@ msgstr ""
 msgid "* Features in this table might not be applicable to all hypervisors or directly mappable between hypervisors."
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:8(title)
-msgid "Introduction to SSL/TLS"
+#: ./doc/security-guide/ch035_case-studies-networking.xml:8(title)
+msgid "Case studies: Networking"
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:9(para)
-msgid "OpenStack services receive requests on behalf of users on public networks as well as from other internal services over management networks. Inter-service communications can also occur over public networks depending on deployment and architecture choices."
+#: ./doc/security-guide/ch035_case-studies-networking.xml:9(para)
+msgid "In this case study we discuss how Alice and Bob would address providing networking services to the user."
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:10(para)
-msgid "While it is commonly accepted that data over public networks should be secured using cryptographic measures, such as Secure Sockets Layer or Transport Layer Security (SSL/TLS) protocols, it is insufficient to rely on security domain separation to protect internal traffic. Using a security-in-depth approach, we recommend securing all domains with SSL/TLS, including the management domain services. It is important that should a tenant escape their VM isolation and gain access to the hypervisor or host resources, compromise an API endpoint, or any other service, they must not be able to easily inject or capture messages, commands, or otherwise affect or control management capabilities of the cloud. SSL/TLS provides the mechanisms to ensure authentication, non-repudiation, confidentiality, and integrity of user communications to the OpenStack services and between the OpenStack services themselves."
+#: ./doc/security-guide/ch035_case-studies-networking.xml:12(para)
+msgid "A key objective of Alice's cloud is to integrate with the existing auth services and security resources. The key design parameters for this private cloud are a limited scope of tenants, networks and workload type. This environment can be designed to limit what available network resources are available to the tenant and what are the various default quotas and security policies are available. The network policy engine can be modified to restrict creation and changes to network resources. In this environment, Alice might want to leverage nova-network in the application of security group polices on a per instance basis vs. neutron's application of security group polices on a per port basis. L2 isolation in this environment would leverage VLAN tagging. The use of VLAN tags will allow great visibility of tenant traffic by leveraging existing features and tools of the physical infrastructure."
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:11(para)
-msgid "Public Key Infrastructure (PKI) is a set of hardware, software, policies, and procedures required to operate a secure system that provides authentication, non-repudiation, confidentiality, and integrity. The core components of PKI are:"
+#: ./doc/security-guide/ch035_case-studies-networking.xml:30(para)
+msgid "A major business driver for Bob is to provide an advanced networking services to his customers. Bob's customers would like to deploy multi-tiered application stacks. This multi-tiered application are either existing enterprise application or newly deployed applications. Since Bob's public cloud is a multi-tenancy enterprise service, the choice to use for L2 isolation in this environment is to use overlay networking. Another aspect of Bob's cloud is the self-service aspect where the customer can provision available networking services as needed. These networking services encompass L2 networks, L3 Routing, Network <glossterm>ACL</glossterm> and NAT. It is important that per-tenant quota's be implemented in this environment."
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:18(term)
-msgid "End entity"
+#: ./doc/security-guide/ch035_case-studies-networking.xml:43(para)
+msgid "An added benefit with utilizing OpenStack Networking is when new advanced networking services become available, these new features can be easily provided to the end customers."
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:20(para)
-msgid "User, process, or system that is the subject of a certificate."
+#: ./doc/security-guide/ch028_case-studies-identity-management.xml:8(title)
+msgid "Case studies: Identity management"
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:25(term)
-msgid "Certification Authority (<glossterm>CA</glossterm>)"
+#: ./doc/security-guide/ch028_case-studies-identity-management.xml:9(para)
+msgid "In this case study we discuss how Alice and Bob would address configuration of OpenStack core services. These include the Identity service, dashboard, and Compute services. Alice will be concerned with integration into the existing government directory services, while Bob will need to provide access to the public."
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:27(para)
-msgid "Defines certificate policies, management, and issuance of certificates."
+#: ./doc/security-guide/ch028_case-studies-identity-management.xml:19(para)
+msgid "Alice's enterprise has a well-established directory service with two-factor authentication for all users. She configures the Identity service to support an external authentication service supporting authentication with government-issued access cards. She also uses an external LDAP server to provide role information for the users that is integrated with the access control policy. Due to FedRAMP compliance requirements, Alice implements two-factor authentication on the management network for all administrator access."
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:32(term)
-msgid "Registration Authority (RA)"
+#: ./doc/security-guide/ch028_case-studies-identity-management.xml:30(para)
+msgid "Alice also deploys the dashboard to manage many aspects of the cloud. She deploys the dashboard with HSTS to ensure that only HTTPS is used. The dashboard resides within an internal subdomain of the private network domain name system."
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:34(para)
-msgid "An optional system to which a CA delegates certain management functions."
+#: ./doc/security-guide/ch028_case-studies-identity-management.xml:36(para)
+msgid "Alice decides to use SPICE instead of VNC for the virtual console. She wants to take advantage of the emerging capabilities in SPICE."
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:39(term)
-msgid "Repository"
+#: ./doc/security-guide/ch028_case-studies-identity-management.xml:44(para)
+msgid "Because Bob must support authentication for the general public, he decides to use use user name and password authentication. He has concerns about brute force attacks attempting to crack user passwords, so he also uses an external authentication extension that throttles the number of failed login attempts. Bob's management network is separate from the other networks within his cloud, but can be reached from his corporate network through ssh. As recommended earlier, Bob requires administrators to use two-factor authentication on the Management network to reduce the risk from compromised administrator passwords."
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:41(para)
-msgid "Where the end entity certificates and certificate revocation lists are stored and looked up - sometimes referred to as the <emphasis role=\"italic\">certificate bundle</emphasis>."
+#: ./doc/security-guide/ch028_case-studies-identity-management.xml:56(para)
+msgid "Bob also deploys the dashboard to manage many aspects of the cloud. He deploys the dashboard with HSTS to ensure that only HTTPS is used. He has ensured that the dashboard is deployed on a second-level domain due to the limitations of the same-origin policy. He also disables <option>HORIZON_IMAGES_ALLOW_UPLOAD</option> to prevent resource exhaustion."
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:49(term)
-msgid "Relying party"
+#: ./doc/security-guide/ch028_case-studies-identity-management.xml:63(para)
+msgid "Bob decides to use VNC for his virtual console for its maturity and security features."
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:51(para)
-msgid "The endpoint that is trusting that the CA is valid."
+#: ./doc/security-guide/ch038_transport-security.xml:8(title)
+msgid "Messaging security"
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:56(para)
-msgid "PKI builds the framework on which to provide encryption algorithms, cipher modes, and protocols for securing data and authentication. We strongly recommend securing all services with Public Key Infrastructure (PKI), including the use of SSL/TLS for API endpoints. It is impossible for the encryption or signing of transports or messages alone to solve all these problems. Hosts themselves must be secure and implement policy, namespaces, and other controls to protect their private credentials and keys. However, the challenges of key management and protection do not reduce the necessity of these controls, or lessen their importance."
+#: ./doc/security-guide/ch038_transport-security.xml:9(para)
+msgid "This chapter discusses security hardening approaches for the three most common message queuing solutions use in OpenStack: RabbitMQ, Qpid, and ZeroMQ."
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:58(title)
-msgid "Certification authorities"
+#: ./doc/security-guide/ch038_transport-security.xml:11(title)
+msgid "Messaging transport security"
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:59(para)
-msgid "Many organizations have an established Public Key Infrastructure with their own certification authority (CA), certificate policies, and management for which they should use to issue certificates for internal OpenStack users or services. Organizations in which the public security domain is Internet facing will additionally need certificates signed by a widely recognized public CA. For cryptographic communications over the management network, it is recommended one not use a public CA. Instead, we expect and recommend most deployments deploy their own internal CA."
+#: ./doc/security-guide/ch038_transport-security.xml:12(para)
+msgid "AMQP based solutions (Qpid and RabbitMQ) support transport-level security using SSL. ZeroMQ messaging does not natively support SSL, but transport-level security is possible using labelled IPSec or CIPSO network labels."
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:60(para)
-msgid "It is recommended that the OpenStack cloud architect consider using separate PKI deployments for internal systems and customer facing services. This allows the cloud deployer to maintain control of their PKI infrastructure and among other things makes requesting, signing and deploying certificates for internal systems easier. Advanced configurations may use separate PKI deployments for different security domains. This allows deployers to maintain cryptographic separation of environments, ensuring that certificates issued to one are not recognised by another."
+#: ./doc/security-guide/ch038_transport-security.xml:13(para)
+msgid "We highly recommend enabling transport-level cryptography for your message queue. Using SSL for the messaging client connections provides protection of the communications from tampering and eavesdropping in-transit to the messaging server. Below is guidance on how SSL is typically configured for the two popular messaging servers Qpid and RabbitMQ. When configuring the trusted certificate authority (CA) bundle that your messaging server uses to verify client connections, it is recommended that this be limited to only the CA used for your nodes, preferably an internally managed CA. The bundle of trusted CAs will determine which client certificates will be authorized and pass the client-server verification step of the setting up the SSL connection. Note, when installing the certificate and key files, ensure that the file permissions are restricted, for example chmod 0600, and the ownership is restricted to the messaging server daemon user to prevent unauthorized access by other processes and users on the messaging server."
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:61(para)
-msgid "Certificates used to support SSL/TLS on internet facing cloud endpoints (or customer interfaces where the customer is not expected to have installed anything other than standard operating system provided certificate bundles) should be provisioned using Certificate Authorities that are installed in the operating system certificate bundle. Typical well known vendors include Verisign and Thawte but many others exist."
+#: ./doc/security-guide/ch038_transport-security.xml:15(title)
+msgid "RabbitMQ server SSL configuration"
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:62(para)
-msgid "There are many management, policy, and technical challenges around creating and signing certificates as such is an area where cloud architects or operators may wish to seek the advice of industry leaders and vendors in addition to the guidance recommended here."
+#: ./doc/security-guide/ch038_transport-security.xml:16(para)
+msgid "The following lines should be added to the system-wide RabbitMQ configuration file, typically <filename>/etc/rabbitmq/rabbitmq.config</filename>:"
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:65(title)
-msgid "SSL/TLS libraries"
+#: ./doc/security-guide/ch038_transport-security.xml:31(para)
+msgid "Note, the <literal>tcp_listeners</literal> option is set to <literal>[]</literal> to prevent it from listening an on non-SSL port. The <literal>ssl_listeners</literal> option should be restricted to only listen on the management network for the services."
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:66(para)
-msgid "Various components, services, and applications within the OpenStack ecosystem or dependencies of OpenStack are implemented and can be configured to use SSL/TLS libraries. The SSL/TLS and HTTP services within OpenStack are typically implemented using OpenSSL which has been proven to be fairly secure and has a module that has been validated for FIPS 140-2. However, keep in mind that each application or service can still introduce weaknesses in how they use the OpenSSL libraries."
+#: ./doc/security-guide/ch038_transport-security.xml:36(para)
+msgid "For more information on RabbitMQ SSL configuration see:"
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:69(title)
-msgid "Cryptographic algorithms, cipher modes, and protocols"
+#: ./doc/security-guide/ch038_transport-security.xml:39(link)
+msgid "RabbitMQ Configuration"
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:70(para)
-msgid "We recommend only using TLS v1.1 or v1.2. SSLv3 and TLSv1.0 may be used for compatibility but we recommend using caution and only enabling these protocols if you have a strong requirement to do so. Other SSL/TLS versions, explicitly older versions, should not be used. These older versions include SSLv1 and SSLv2. As this book does not intend to be a thorough reference on cryptography we do not wish to be prescriptive about what specific algorithms or cipher modes you should enable or disable in your OpenStack services. However, there are some authoritative references we would like to recommend for further information:"
+#: ./doc/security-guide/ch038_transport-security.xml:43(link)
+msgid "RabbitMQ SSL"
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:72(link)
-msgid "National Security Agency, Suite B Cryptography"
+#: ./doc/security-guide/ch038_transport-security.xml:48(title)
+msgid "Qpid server SSL configuration"
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:75(link)
-msgid "OWASP Guide to Cryptography"
+#: ./doc/security-guide/ch038_transport-security.xml:49(para)
+msgid "The Apache Foundation has a messaging security guide for Qpid. See:"
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:78(link)
-msgid "OWASP Transport Layer Protection Cheat Sheet"
+#: ./doc/security-guide/ch038_transport-security.xml:51(link)
+msgid "Apache Qpid SSL"
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:81(link)
-msgid "SoK: SSL and HTTPS: Revisiting past challenges and evaluating certificate trust model enhancements"
+#: ./doc/security-guide/ch038_transport-security.xml:57(title)
+msgid "Queue authentication and access control"
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:84(link)
-msgid "The Most Dangerous Code in the World: Validating SSL Certificates in Non-Browser Software"
+#: ./doc/security-guide/ch038_transport-security.xml:58(para)
+msgid "RabbitMQ and Qpid offer authentication and access control mechanisms for controlling access to queues. ZeroMQ offers no such mechanisms."
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:87(link)
-msgid "OpenSSL and FIPS 140-2"
+#: ./doc/security-guide/ch038_transport-security.xml:59(para)
+msgid "Simple Authentication and Security Layer (SASL) is a framework for authentication and data security in Internet protocols. Both RabbitMQ and Qpid offer SASL and other pluggable authentication mechanisms beyond simple usernames and passwords that allow for increased authentication security. While RabbitMQ supports SASL, support in OpenStack does not currently allow for requesting a specific SASL authentication mechanism. RabbitMQ support in OpenStack allows for either username and password authentication over an unencrypted connection or username and password in conjunction with X.509 client certificates to establish the secure SSL connection."
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:92(title)
-msgid "Summary"
+#: ./doc/security-guide/ch038_transport-security.xml:60(para)
+msgid "We recommend configuring X.509 client certificates on all the OpenStack service nodes for client connections to the messaging queue and where possible (currently only Qpid) perform authentication with X.509 client certificates. When using usernames and passwords, accounts should be created per-service and node for finer grained auditability of access to the queue."
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:93(para)
-msgid "Given the complexity of the OpenStack components and the number of deployment possibilities, you must take care to ensure that each component gets the appropriate configuration of SSL certificates, keys, and CAs. Subsequent sections discuss the following services:"
+#: ./doc/security-guide/ch038_transport-security.xml:61(para)
+msgid "Before deployment, consider the SSL libraries that the queuing servers use. Qpid uses Mozilla's NSS library, whereas RabbitMQ uses Erlang's SSL module which uses OpenSSL."
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:102(para)
-msgid "Compute API endpoints"
+#: ./doc/security-guide/ch038_transport-security.xml:66(title)
+msgid "Authentication configuration example: RabbitMQ"
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:105(para)
-msgid "Identity API endpoints"
+#: ./doc/security-guide/ch038_transport-security.xml:67(para)
+msgid "On the RabbitMQ server, delete the default <literal>guest</literal> user:"
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:108(para)
-msgid "Networking API endpoints"
+#: ./doc/security-guide/ch038_transport-security.xml:70(para)
+msgid "On the RabbitMQ server, for each OpenStack service or node that communicates with the message queue set up user accounts and privileges:"
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:111(para)
-msgid "Storage API endpoints"
+#: ./doc/security-guide/ch038_transport-security.xml:75(para)
+msgid "For additional configuration information see:"
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:114(para)
-msgid "Messaging server"
+#: ./doc/security-guide/ch038_transport-security.xml:77(link)
+msgid "RabbitMQ Access Control"
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:117(para)
-msgid "Database server"
+#: ./doc/security-guide/ch038_transport-security.xml:80(link)
+msgid "RabbitMQ Authentication"
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:120(para) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:33(title) ./doc/security-guide/ch004_book-introduction.xml:186(title) ./doc/security-guide/ch025_web-dashboard.xml:8(title)
-msgid "Dashboard"
+#: ./doc/security-guide/ch038_transport-security.xml:83(link)
+msgid "RabbitMQ Plugins"
 msgstr ""
 
-#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:123(para)
-msgid "This guide uses the term SSL as a shorthand to refer to these recommendations for SSL/TLS protocols."
+#: ./doc/security-guide/ch038_transport-security.xml:86(link)
+msgid "RabbitMQ SASL External Auth"
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:8(title)
-msgid "Continuous systems management"
+#: ./doc/security-guide/ch038_transport-security.xml:91(title)
+msgid "OpenStack service configuration: RabbitMQ"
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:9(para)
-msgid "A cloud will always have bugs. Some of these will be security problems. For this reason, it is critically important to be prepared to apply security updates and general software updates. This involves smart use of configuration management tools, which are discussed below. This also involves knowing when an upgrade is necessary."
+#: ./doc/security-guide/ch038_transport-security.xml:104(title)
+msgid "Authentication configuration example: Qpid"
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:16(title) ./doc/security-guide/ch063_compliance-activities.xml:48(title)
-msgid "Vulnerability management"
+#: ./doc/security-guide/ch038_transport-security.xml:105(para)
+msgid "For configuration information see:"
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:17(para)
-msgid "For announcements regarding security relevant changes, subscribe to the <link href=\"http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-announce\">OpenStack Announce mailing list</link>. The security notifications are also posted through the downstream packages for example through Linux distributions that you may be subscribed to as part of the package updates."
+#: ./doc/security-guide/ch038_transport-security.xml:107(link)
+msgid "Apache Qpid Authentication"
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:24(para)
-msgid "The OpenStack components are only a small fraction of the software in a cloud. It is important to keep up to date with all of these other components, too. While the specific data sources will be deployment specific, the key idea is to ensure that a cloud administrator subscribes to the necessary mailing lists for receiving notification of any related security updates. Often this is as simple as tracking an upstream Linux distribution."
+#: ./doc/security-guide/ch038_transport-security.xml:110(link)
+msgid "Apache Qpid Authorization"
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:36(para)
-msgid "OpenStack Security Advisories (OSSA) are created by the OpenStack Vulnerability Management Team (VMT). They pertain to security holes in core OpenStack services. More information on the VMT can be found here: <link href=\"https://wiki.openstack.org/wiki/Vulnerability_Management\">https://wiki.openstack.org/wiki/Vulnerability_Management</link>"
+#: ./doc/security-guide/ch038_transport-security.xml:115(title)
+msgid "OpenStack service configuration: Qpid"
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:44(para)
-msgid "OpenStack Security Notes (OSSN) were created by the OpenStack Security Group (OSSG) to support the work of the VMT. OSSN address issues in supporting software and common deployment configurations. They're referenced throughout this guide. Security Notes are archived at <link href=\"https://launchpad.net/ossn/\">https://launchpad.net/ossn/</link>"
+#: ./doc/security-guide/ch038_transport-security.xml:124(para)
+msgid "Optionally, if using SASL with Qpid specify the SASL mechanisms in use by adding:"
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:33(para)
-msgid "OpenStack releases security information through two channels. <placeholder-1/>"
+#: ./doc/security-guide/ch038_transport-security.xml:129(title)
+msgid "Message queue process isolation and policy"
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:56(title)
-msgid "Triage"
+#: ./doc/security-guide/ch038_transport-security.xml:130(para)
+msgid "Each project provides a number of services which send and consume messages. Each binary which sends a message is expected to consume messages, if only replies, from the queue."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:57(para)
-msgid "After you are notified of a security update, the next step is to determine how critical this update is to a given cloud deployment. In this case, it is useful to have a pre-defined policy. Existing vulnerability rating systems such as the common vulnerability scoring system (CVSS) v2 do not properly account for cloud deployments."
+#: ./doc/security-guide/ch038_transport-security.xml:131(para)
+msgid "Message queue service processes should be isolated from each other and other processes on a machine."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:63(para)
-msgid "In this example we introduce a scoring matrix that places vulnerabilities in three categories: Privilege Escalation, Denial of Service and Information Disclosure. Understanding the type of vulnerability and where it occurs in your infrastructure will enable you to make reasoned response decisions."
+#: ./doc/security-guide/ch038_transport-security.xml:134(para)
+msgid "Network namespaces are highly recommended for all services running on OpenStack Compute Hypervisors. This will help prevent against the bridging of network traffic between VM guests and the management network."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:69(para)
-msgid "Privilege Escalation describes the ability of a user to act with the privileges of some other user in a system, bypassing appropriate authorization checks. For example, a standard Linux user running code or performing an operation that allows them to conduct further operations with the privileges of the root users on the system."
+#: ./doc/security-guide/ch038_transport-security.xml:135(para)
+msgid "When using ZeroMQ messaging, each host must run at least one ZeroMQ message receiver to receive messages from the network and forward messages to local processes through IPC. It is possible and advisable to run an independent message receiver per project within an IPC namespace, along with other services within the same project."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:75(para)
-msgid "Denial of Service refers to an exploited vulnerability that may cause service or system disruption. This includes both distributed attacks to overwhelm network resources, and single-user attacks that are typically caused through resource allocation bugs or input induced system failure flaws."
+#: ./doc/security-guide/ch038_transport-security.xml:145(para)
+msgid "Queue servers should only accept connections from the management network. This applies to all implementations. This should be implemented through configuration of services and optionally enforced through global network policy."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:80(para)
-msgid "Information Disclosure vulnerabilities reveal information about your system or operations. These vulnerabilities range from debugging information disclosure, to exposure of critical security data, such as authentication credentials and passwords."
+#: ./doc/security-guide/ch038_transport-security.xml:146(para)
+msgid "When using ZeroMQ messaging, each project should run a separate ZeroMQ receiver process on a port dedicated to services belonging to that project. This is equivalent to the AMQP concept of control exchanges."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:96(emphasis)
-msgid "Attacker position / Privilege level"
+#: ./doc/security-guide/ch038_transport-security.xml:150(para)
+msgid "The configuration for these processes should be restricted to those processes, not only by Directory Access Controls, but through Mandatory Access Controls. The goal of such restrictions is to prevent isolation from other processes running on the same machine(s)."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:102(emphasis)
-msgid "External"
+#: ./doc/security-guide/ch024_authentication.xml:8(title)
+msgid "Identity"
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:103(emphasis)
-msgid "Cloud user"
+#: ./doc/security-guide/ch024_authentication.xml:9(para)
+msgid "The OpenStack Identity service (keystone) supports multiple methods of authentication, including username &amp; password, LDAP, and external authentication methods. Upon successful authentication, The Identity Service provides the user with an authorization token used for subsequent service requests."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:105(emphasis)
-msgid "Cloud admin"
+#: ./doc/security-guide/ch024_authentication.xml:14(para)
+msgid "Transport Layer Security TLS/SSL provides authentication between services and persons using X.509 certificates. Although the default mode for SSL is server-side only authentication, certificates may also be used for client authentication."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:107(emphasis)
-msgid "Control plane"
+#: ./doc/security-guide/ch024_authentication.xml:19(title)
+msgid "Authentication"
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:111(emphasis)
-msgid "Privilege elevation (3 levels)"
+#: ./doc/security-guide/ch024_authentication.xml:21(title)
+msgid "Invalid login attempts"
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:113(para) ./doc/security-guide/ch012_configuration-management.xml:121(para) ./doc/security-guide/ch012_configuration-management.xml:122(para) ./doc/security-guide/ch012_configuration-management.xml:129(para) ./doc/security-guide/ch012_configuration-management.xml:130(para) ./doc/security-guide/ch012_configuration-management.xml:131(para)
-msgid "Critical"
+#: ./doc/security-guide/ch024_authentication.xml:22(para)
+msgid "The Identity Service does not provide a method to limit access to accounts after repeated unsuccessful login attempts. Repeated failed login attempts are likely brute-force attacks (Refer figure Attack-types). This is a more significant issue in Public clouds."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:114(para) ./doc/security-guide/ch012_configuration-management.xml:115(para) ./doc/security-guide/ch012_configuration-management.xml:116(para) ./doc/security-guide/ch012_configuration-management.xml:123(para) ./doc/security-guide/ch012_configuration-management.xml:124(para) ./doc/security-guide/ch012_configuration-management.xml:132(para)
-msgid "n/a"
+#: ./doc/security-guide/ch024_authentication.xml:27(para)
+msgid "Prevention is possible by using an external authentication system that blocks out an account after some configured number of failed login attempts. The account then may only be unlocked with further side-channel intervention."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:119(emphasis)
-msgid "Privilege elevation (2 levels)"
+#: ./doc/security-guide/ch024_authentication.xml:31(para)
+msgid "If prevention is not an option, detection can be used to mitigate damage.Detection involves frequent review of access control logs to identify unauthorized attempts to access accounts. Possible remediation would include reviewing the strength of the user password, or blocking the network source of the attack through firewall rules. Firewall rules on the keystone server that restrict the number of connections could be used to reduce the attack effectiveness, and thus dissuade the attacker."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:127(emphasis)
-msgid "Privilege elevation (1 level)"
+#: ./doc/security-guide/ch024_authentication.xml:40(para)
+msgid "In addition, it is useful to examine account activity for unusual login times and suspicious actions, with possibly disable the account. Oftentimes this approach is taken by credit card providers for fraud detection and alert."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:135(emphasis)
-msgid "Denial of service"
+#: ./doc/security-guide/ch024_authentication.xml:46(title)
+msgid "Multi-factor authentication"
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:137(para)
-msgid "High"
+#: ./doc/security-guide/ch024_authentication.xml:47(para)
+msgid "Employ multi-factor authentication for network access to privileged user accounts. The Identity Service supports external authentication services through the Apache web server that can provide this functionality. Servers may also enforce client-side authentication using certificates."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:138(para)
-msgid "Medium"
+#: ./doc/security-guide/ch024_authentication.xml:52(para)
+msgid "This recommendation provides insulation from brute force, social engineering, and both spear and mass phishing attacks that may compromise administrator passwords."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:139(para) ./doc/security-guide/ch012_configuration-management.xml:140(para) ./doc/security-guide/ch012_configuration-management.xml:148(para)
-msgid "Low"
+#: ./doc/security-guide/ch024_authentication.xml:58(title)
+msgid "Authentication methods"
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:143(emphasis)
-msgid "Information disclosure"
+#: ./doc/security-guide/ch024_authentication.xml:60(title)
+msgid "Internally implemented authentication methods"
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:145(para) ./doc/security-guide/ch012_configuration-management.xml:146(para)
-msgid "Critical / high"
+#: ./doc/security-guide/ch024_authentication.xml:61(para)
+msgid "The Identity Service can store user credentials in an SQL Database, or may use an LDAP-compliant directory server. The Identity database may be separate from databases used by other OpenStack services to reduce the risk of a compromise of the stored credentials."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:147(para)
-msgid "Medium / low"
+#: ./doc/security-guide/ch024_authentication.xml:66(para)
+msgid "When you use a user name and password to authenticate, Identity does not enforce policies on password strength, expiration, or failed authentication attempts as recommended by NIST Special Publication 800-118 (draft). Organizations that desire to enforce stronger password policies should consider using Identity extensions or external authentication services."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:152(para)
-msgid "This table illustrates a generic approach to measuring the impact of a vulnerability based on where it occurs in your deployment and the effect. For example, a single level privilege escalation on a Compute API node potentially allows a standard user of the API to escalate to have the same privileges as the root user on the node."
+#: ./doc/security-guide/ch024_authentication.xml:74(para)
+msgid "LDAP simplifies integration of Identity authentication into an organization's existing directory service and user account management processes."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:158(para)
-msgid "We suggest that cloud administrators use this table as a model to help define which actions to take for the various security levels. For example, a critical-level security update might require the cloud to be upgraded on a specified time line, whereas a low-level update might be more relaxed."
+#: ./doc/security-guide/ch024_authentication.xml:77(para)
+msgid "Authentication and authorization policy in OpenStack may be delegated to an external LDAP server. A typical use case is an organization that seeks to deploy a private cloud and already has a database of employees, the users. This may be in an LDAP system. Using LDAP as a source of authority authentication, requests to Identity Service are delegated to the LDAP service, which will authorize or deny requests based on locally set policies. A token is generated on successful authentication."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:165(title)
-msgid "Testing the updates"
+#: ./doc/security-guide/ch024_authentication.xml:86(para)
+msgid "Note that if the LDAP system has attributes defined for the user such as admin, finance, HR etc, these must be mapped into roles and groups within Identity for use by the various OpenStack services. The <filename>/etc/keystone.conf</filename> file maps LDAP attributes to Identity attributes."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:166(para)
-msgid "You should test any update before you deploy it in a production environment. Typically this requires having a separate test cloud setup that first receives the update. This cloud should be as close to the production cloud as possible, in terms of software and hardware. Updates should be tested thoroughly in terms of performance impact, stability, application impact, and more. Especially important is to verify that the problem theoretically addressed by the update, such as a specific vulnerability, is actually fixed."
+#: ./doc/security-guide/ch024_authentication.xml:91(para)
+msgid "The Identity Service <emphasis role=\"bold\">MUST NOT</emphasis> be allowed to write to LDAP services used for authentication outside of the OpenStack deployment as this would allow a sufficiently privileged keystone user to make changes to the LDAP directory. This would allow privilege escalation within the wider organization or facilitate unauthorized access to other information and resources. In such a deployment, user provisioning would be out of the realm of the OpenStack deployment."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:177(title)
-msgid "Deploying the updates"
+#: ./doc/security-guide/ch024_authentication.xml:101(para)
+msgid "There is an <link href=\"https://bugs.launchpad.net/ossn/+bug/1168252\">OpenStack Security Note (OSSN) regarding keystone.conf permissions</link>."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:178(para)
-msgid "Once the updates are fully tested, they can be deployed to the production environment. This deployment should be fully automated using the configuration management tools described below."
+#: ./doc/security-guide/ch024_authentication.xml:105(para)
+msgid "There is an <link href=\"https://bugs.launchpad.net/ossn/+bug/1155566\">OpenStack Security Note (OSSN) regarding potential DoS attacks</link>."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:185(title)
-msgid "Configuration management"
+#: ./doc/security-guide/ch024_authentication.xml:112(title)
+msgid "External authentication methods"
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:186(para)
-msgid "A production quality cloud should always use tools to automate configuration and deployment. This eliminates human error, and allows the cloud to scale much more rapidly. Automation also helps with continuous integration and testing."
+#: ./doc/security-guide/ch024_authentication.xml:113(para)
+msgid "Organizations may desire to implement external authentication for compatibility with existing authentication services or to enforce stronger authentication policy requirements. Although passwords are the most common form of authentication, they can be compromised through numerous methods, including keystroke logging and password compromise. External authentication services can provide alternative forms of authentication that minimize the risk from weak passwords."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:191(para)
-msgid "When building an OpenStack cloud it is strongly recommended to approach your design and implementation with a configuration management tool or framework in mind. Configuration management allows you to avoid the many pitfalls inherent in building, managing, and maintaining an infrastructure as complex as OpenStack. By producing the manifests, cookbooks, or templates required for a configuration management utility, you are able to satisfy a number of documentation and regulatory reporting requirements. Further, configuration management can also function as part of your BCP and DR plans wherein you can rebuild a node or service back to a known state in a DR event or given a compromise."
+#: ./doc/security-guide/ch024_authentication.xml:122(para)
+msgid "These include:"
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:203(para)
-msgid "Additionally, when combined with a version control system such as Git or SVN, you can track changes to your environment over time and re-mediate unauthorized changes that may occur. For example, a <filename>nova.conf</filename> file or other configuration file falls out of compliance with your standard, your configuration management tool can revert or replace the file and bring your configuration back into a known state. Finally a configuration management tool can also be used to deploy updates; simplifying the security patch process. These tools have a broad range of capabilities that are useful in this space. The key point for securing your cloud is to choose a tool for configuration management and use it."
+#: ./doc/security-guide/ch024_authentication.xml:125(para)
+msgid "Password policy enforcement: Requires user passwords to conform to minimum standards for length, diversity of characters, expiration, or failed login attempts."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:215(para)
-msgid "There are many configuration management solutions; at the time of this writing there are two in the marketplace that are robust in their support of OpenStack environments: <glossterm>Chef</glossterm> and <glossterm>Puppet</glossterm>. A non-exhaustive listing of tools in this space is provided below:"
+#: ./doc/security-guide/ch024_authentication.xml:130(para)
+msgid "Multi-factor authentication: The authentication service requires the user to provide information based on something they have, such as a one-time password token or X.509 certificate, and something they know, such as a password."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:223(para)
-msgid "Chef"
+#: ./doc/security-guide/ch024_authentication.xml:137(para)
+msgid "Kerberos"
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:226(para)
-msgid "Puppet"
+#: ./doc/security-guide/ch024_authentication.xml:143(title)
+msgid "Authorization"
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:229(para)
-msgid "Salt Stack"
+#: ./doc/security-guide/ch024_authentication.xml:144(para)
+msgid "The Identity Service supports the notion of groups and roles. Users belong to groups. A group has a list of roles. OpenStack services reference the roles of the user attempting to access the service. The OpenStack policy enforcer middleware takes into consideration the policy rule associated with each resource and the user's group/roles and tenant association to determine if he/she has access to the requested resource."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:232(para)
-msgid "Ansible"
+#: ./doc/security-guide/ch024_authentication.xml:151(para)
+msgid "The Policy enforcement middleware enables fine-grained access control to OpenStack resources. Only admin users can provision new users and have access to various management functionality. The cloud tenant would be able to only spin up instances, attach volumes, etc."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:236(title)
-msgid "Policy changes"
+#: ./doc/security-guide/ch024_authentication.xml:157(title)
+msgid "Establish formal access control policies"
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:237(para)
-msgid "Whenever a policy or configuration management is changed, it is good practice to log the activity, and backup a copy of the new set. Often, such policies and configurations are stored in a version controlled repository such as git."
+#: ./doc/security-guide/ch024_authentication.xml:158(para)
+msgid "Prior to configuring roles, groups, and users, document your required access control policies for the OpenStack installation. The policies should be consistent with any regulatory or legal requirements for the organization. Future modifications to access control configuration should be done consistently with the formal policies. The policies should include the conditions and processes for creating, deleting, disabling, and enabling accounts, and for assigning privileges to the accounts. Periodically review the policies and ensure that configuration is in compliance with approved policies."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:244(title)
-msgid "Secure backup and recovery"
+#: ./doc/security-guide/ch024_authentication.xml:171(title)
+msgid "Service authorization"
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:245(para)
-msgid "It is important to include Backup procedures and policies in the overall System Security Plan. For a good overview of OpenStack's Backup and Recovery capabilities and procedures, please refer to the OpenStack Operations Guide."
+#: ./doc/security-guide/ch024_authentication.xml:172(para)
+msgid "As described in the <link href=\"http://docs.openstack.org/admin-guide-cloud/content/index.html\"><citetitle>OpenStack Cloud Administrator Guide</citetitle></link>, cloud administrators must define a user for each service, with a role of Admin. This service user account provides the service with the authorization to authenticate users."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:250(title) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:60(title) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:117(title) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:150(title) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:174(title) ./doc/security-guide/ch026_compute.xml:45(title) ./doc/security-guide/ch026_compute.xml:90(title)
-msgid "Security considerations"
+#: ./doc/security-guide/ch024_authentication.xml:179(para)
+msgid "The Compute and Object Storage services can be configured to use either the \"tempAuth\" file or Identity Service to store authentication information. The \"tempAuth\" solution MUST NOT be deployed in a production environment since it stores passwords in plain text."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:253(para)
-msgid "Ensure only authenticated users and backup clients have access to the backup server."
+#: ./doc/security-guide/ch024_authentication.xml:184(para)
+msgid "The Identity Service supports client authentication for SSL which may be enabled. SSL client authentication provides an additional authentication factor, in addition to the username / password, that provides greater reliability on user identification. It reduces the risk of unauthorized access when user names and passwords may be compromised. However, there is additional administrative overhead and cost to issue certificates to users that may not be feasible in every deployment."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:257(para)
-msgid "Use data encryption options for storage and transmission of backups."
+#: ./doc/security-guide/ch024_authentication.xml:194(para)
+msgid "We recommend that you use client authentication with SSL for the authentication of services to the Identity Service."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:261(para)
-msgid "Use a dedicated and hardened backup servers. The logs for the backup server must be monitored daily and accessible by only few individuals."
+#: ./doc/security-guide/ch024_authentication.xml:198(para)
+msgid "The cloud administrator should protect sensitive configuration files for unauthorized modification. This can be achieved with mandatory access control frameworks such as SELinux, including <filename>/etc/keystone.conf</filename> and X.509 certificates."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:266(para)
-msgid "Test data recovery options regularly. One of the things that can be restored from secured backups is the images. In case of a compromise, the best practice would be to terminate running instances immediately and then relaunch the instances from the images in the secured backup repository."
+#: ./doc/security-guide/ch024_authentication.xml:204(para)
+msgid "For client authentication with SSL, you need to issue certificates. These certificates can be signed by an external authority or by the cloud administrator. OpenStack services by default check the signatures of certificates and connections fail if the signature cannot be checked. If the administrator uses self-signed certificates, the check might need to be disabled. To disable these certificates, set <code>insecure=False</code> in the <code>[filter:authtoken]</code> section in the <filename>/etc/nova/api.paste.ini</filename> file. This setting also disables certificates for other components."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:276(title) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:90(title) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:160(title) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:199(title) ./doc/security-guide/ch026_compute.xml:60(title) ./doc/security-guide/ch026_compute.xml:106(title) ./doc/security-guide/ch058_forensicsincident-response.xml:48(title)
-msgid "References"
+#: ./doc/security-guide/ch024_authentication.xml:218(title)
+msgid "Administrative users"
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:279(para)
-msgid "<citetitle>OpenStack Operations Guide</citetitle> on <link href=\"http://docs.openstack.org/trunk/openstack-ops/content/backup_and_recovery.html\">backup and recovery</link>"
+#: ./doc/security-guide/ch024_authentication.xml:219(para)
+msgid "We recommend that admin users authenticate using Identity Service and an external authentication service that supports 2-factor authentication, such as a certificate. This reduces the risk from passwords that may be compromised. This recommendation is in compliance with NIST 800-53 IA-2(1) guidance in the use of multi factor authentication for network access to privileged accounts."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:287(link)
-msgid "http://www.sans.org/reading_room/whitepapers/backup/security-considerations-enterprise-level-backups_515"
+#: ./doc/security-guide/ch024_authentication.xml:228(title)
+msgid "End users"
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:291(link)
-msgid "OpenStack Security Primer"
+#: ./doc/security-guide/ch024_authentication.xml:229(para)
+msgid "The Identity Service can directly provide end-user authentication, or can be configured to use external authentication methods to conform to an organization's security policies and requirements."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:297(title)
-msgid "Security auditing tools"
+#: ./doc/security-guide/ch024_authentication.xml:236(title)
+msgid "Policies"
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:298(para)
-msgid "Security auditing tools can complement the configuration management tools. Security auditing tools automate the process of verifying that a large number of security controls are satisfied for a given system configuration. These tools help to bridge the gap from security configuration guidance documentation (for example, the STIG and NSA Guides) to a specific system installation. For example, <link href=\"https://fedorahosted.org/scap-security-guide/\">SCAP</link> can compare a running system to a pre-defined profile. SCAP outputs a report detailing which controls in the profile were satisfied, which ones failed, and which ones were not checked."
+#: ./doc/security-guide/ch024_authentication.xml:237(para)
+msgid "Each OpenStack service has a policy file in JSON format, called <filename>policy.json</filename>. The policy file specifies rules, and the rule that governs each resource. A resource could be API access, the ability to attach to a volume, or to fire up instances."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:310(para)
-msgid "Combining configuration management and security auditing tools creates a powerful combination. The auditing tools will highlight deployment concerns. And the configuration management tools simplify the process of changing each system to address the audit concerns. Used together in this fashion, these tools help to maintain a cloud that satisfies security requirements ranging from basic hardening to compliance validation."
+#: ./doc/security-guide/ch024_authentication.xml:242(para)
+msgid "The policies can be updated by the cloud administrator to further control access to the various resources. The middleware could also be further customized. Note that your users must be assigned to groups/roles that you refer to in your policies."
 msgstr ""
 
-#: ./doc/security-guide/ch012_configuration-management.xml:317(para)
-msgid "Configuration management and security auditing tools will introduce another layer of complexity into the cloud. This complexity brings additional security concerns with it. We view this as an acceptable risk trade-off, given their security benefits. Securing the operational use of these tools is beyond the scope of this guide."
+#: ./doc/security-guide/ch024_authentication.xml:247(para)
+msgid "Below is a snippet of the Block Storage service <filename>policy.json</filename> file."
+msgstr ""
+
+#: ./doc/security-guide/ch024_authentication.xml:250(para)
+msgid "Note the <emphasis role=\"bold\">default</emphasis> rule specifies that the user must be either an admin or the owner of the volume. It essentially says only the owner of a volume or the admin may create/delete/update volumes. Certain other operations such as managing volume types are accessible only to admin users."
+msgstr ""
+
+#: ./doc/security-guide/ch024_authentication.xml:258(title)
+msgid "Tokens"
+msgstr ""
+
+#: ./doc/security-guide/ch024_authentication.xml:259(para)
+msgid "Once a user is authenticated, a token is generated and used internally in OpenStack for authorization and access. The default token <emphasis role=\"bold\">lifespan</emphasis> is<emphasis role=\"bold\"> 24 hours</emphasis>. It is recommended that this value be set lower but caution needs to be taken as some internal services will need sufficient time to complete their work. The cloud may not provide services if tokens expire too early. An example of this would be the time needed by the Compute service to transfer a disk image onto the hypervisor for local caching."
+msgstr ""
+
+#: ./doc/security-guide/ch024_authentication.xml:269(para)
+msgid "The following example shows a PKI token. Note that, in practice, the token id value is about 3500 bytes. We shorten it in this example."
+msgstr ""
+
+#: ./doc/security-guide/ch024_authentication.xml:273(para)
+msgid "Note that the token is often passed within the structure of a larger context of an Identity Service response. These responses also provide a catalog of the various OpenStack services. Each service is listed with its name, access endpoints for internal, admin, and public access."
+msgstr ""
+
+#: ./doc/security-guide/ch024_authentication.xml:278(para)
+msgid "The Identity Service supports token revocation. This manifests as an API to revoke a token, to list revoked tokens and individual OpenStack services that cache tokens to query for the revoked tokens and remove them from their cache and append the same to their list of cached revoked tokens."
+msgstr ""
+
+#: ./doc/security-guide/ch024_authentication.xml:285(title)
+msgid "Future"
+msgstr ""
+
+#: ./doc/security-guide/ch024_authentication.xml:286(para)
+msgid "Domains are high-level containers for projects, users and groups. As such, they can be used to centrally manage all keystone-based identity components. With the introduction of account domains, server, storage and other resources can now be logically grouped into multiple projects (previously called tenants) which can themselves be grouped under a master account-like container. In addition, multiple users can be managed within an account domain and assigned roles that vary for each project."
+msgstr ""
+
+#: ./doc/security-guide/ch024_authentication.xml:295(para)
+msgid "The Identity V3 API supports multiple domains. Users of different domains may be represented in different authentication backends and even have different attributes that must be mapped to a single set of roles and privileges, that are used in the policy definitions to access the various service resources."
+msgstr ""
+
+#: ./doc/security-guide/ch024_authentication.xml:301(para)
+msgid "Where a rule may specify access to only admin users and users belonging to the tenant, the mapping may be trivial. In other scenarios the cloud administrator may need to approve the mapping routines per tenant."
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch001_acknowledgements.xml:12(None) ./doc/security-guide/ch001_acknowledgements.xml:15(None)
+msgid "@@image: 'static/book-sprint-all-logos.png'; md5=f2d97c3130c32f31412f5af41ad72d39"
+msgstr ""
+
+#: ./doc/security-guide/ch001_acknowledgements.xml:7(title)
+msgid "Acknowledgments"
+msgstr ""
+
+#: ./doc/security-guide/ch001_acknowledgements.xml:8(para)
+msgid "The OpenStack Security Group would like to acknowledge contributions from the following organizations who were instrumental in making this book possible. These are:"
 msgstr ""
 
 #: ./doc/security-guide/ch059_case-studies-monitoring-logging.xml:8(title)
@@ -1251,288 +3857,280 @@ msgstr ""
 msgid "In this case study we discuss how Alice and Bob would address monitoring and logging in the public vs a private cloud. In both instances, time synchronization and a centralized store of logs become extremely important for performing proper assessments and troubleshooting of anomalies. Just collecting logs is not very useful, a robust monitoring system must be built to generate actionable events."
 msgstr ""
 
-#: ./doc/security-guide/ch059_case-studies-monitoring-logging.xml:11(title) ./doc/security-guide/ch039_case-studies-messaging.xml:11(title) ./doc/security-guide/ch066_case-studies-compliance.xml:11(title) ./doc/security-guide/ch028_case-studies-identity-management.xml:18(title) ./doc/security-guide/ch044_case-studies-database.xml:11(title) ./doc/security-guide/ch009_case-studies.xml:11(title) ./doc/security-guide/ch056_case-studies-instance-management.xml:11(title) ./doc/security-guide/ch022_case-studies-api-endpoints.xml:11(title) ./doc/security-guide/ch015_case-studies-management.xml:28(title) ./doc/security-guide/ch018_case-studies-pkissl.xml:11(title) ./doc/security-guide/ch035_case-studies-networking.xml:11(title) ./doc/security-guide/ch049_case-studies-tenant-data.xml:17(title) ./doc/security-guide/ch053_case-studies-instance-isolation.xml:11(title)
-msgid "Alice's private cloud"
-msgstr ""
-
 #: ./doc/security-guide/ch059_case-studies-monitoring-logging.xml:12(para)
 msgid "In the private cloud, Alice has a better understanding of the tenants requirements and accordingly can add appropriate oversight and compliance on monitoring and logging. Alice should identify critical services and data and ensure that logging is turned at least on those services and is being aggregated to a central log server. She should start with simple and known use cases and implement correlation and alerting to limit the number of false positives. To implement correlation and alerting, she sends the log data to her organization's existing SIEM tool. Security monitoring should be an ongoing process and she should continue to define use cases and alerts as she has better understanding of the network traffic activity and usage over time."
 msgstr ""
 
-#: ./doc/security-guide/ch059_case-studies-monitoring-logging.xml:15(title) ./doc/security-guide/ch039_case-studies-messaging.xml:15(title) ./doc/security-guide/ch066_case-studies-compliance.xml:18(title) ./doc/security-guide/ch028_case-studies-identity-management.xml:43(title) ./doc/security-guide/ch044_case-studies-database.xml:15(title) ./doc/security-guide/ch009_case-studies.xml:16(title) ./doc/security-guide/ch056_case-studies-instance-management.xml:17(title) ./doc/security-guide/ch022_case-studies-api-endpoints.xml:33(title) ./doc/security-guide/ch015_case-studies-management.xml:33(title) ./doc/security-guide/ch018_case-studies-pkissl.xml:15(title) ./doc/security-guide/ch035_case-studies-networking.xml:29(title) ./doc/security-guide/ch049_case-studies-tenant-data.xml:50(title) ./doc/security-guide/ch053_case-studies-instance-isolation.xml:17(title)
-msgid "Bob's public cloud"
-msgstr ""
-
 #: ./doc/security-guide/ch059_case-studies-monitoring-logging.xml:16(para)
 msgid "When it comes to logging, as a public cloud provider, Bob is interested in logging both for situational awareness as well as compliance. That is, compliance that Bob as a provider is subject to as well as his ability to provide timely and relevant logs or reports on the behalf of his customers for their compliance audits. With that in mind, Bob configures all of his instances, nodes, and infrastructure devices to perform time synchronization with an external, known good time device. Additionally, Bob's team has built a Django based web applications for his customers to perform self-service log retrieval from Bob's SIEM tool. Bob also uses this SIEM tool along with a robust set of alerts and integration with his CMDB to provide operational awareness to both customers and cloud administrators."
 msgstr ""
 
-#: ./doc/security-guide/bk_openstack-sec-guide.xml:6(title)
-msgid "OpenStack Security Guide"
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:8(title)
+msgid "Management interfaces"
 msgstr ""
 
-#: ./doc/security-guide/bk_openstack-sec-guide.xml:14(orgname) ./doc/security-guide/bk_openstack-sec-guide.xml:19(holder)
-msgid "OpenStack Foundation"
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:9(para)
+msgid "It is necessary for administrators to perform command and control over the cloud for various operational functions. It is important these command and control facilities are understood and secured."
 msgstr ""
 
-#: ./doc/security-guide/bk_openstack-sec-guide.xml:18(year)
-msgid "2013"
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:13(para)
+msgid "OpenStack provides several management interfaces for operators and tenants:"
 msgstr ""
 
-#: ./doc/security-guide/bk_openstack-sec-guide.xml:21(releaseinfo)
-msgid "current"
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:15(para)
+msgid "OpenStack dashboard (horizon)"
 msgstr ""
 
-#: ./doc/security-guide/bk_openstack-sec-guide.xml:22(productname)
-msgid "OpenStack"
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:18(para) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:95(title)
+msgid "OpenStack API"
 msgstr ""
 
-#: ./doc/security-guide/bk_openstack-sec-guide.xml:26(remark)
-msgid "Copyright details are filled in by the template."
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:21(para) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:128(title)
+msgid "Secure shell (SSH)"
 msgstr ""
 
-#: ./doc/security-guide/bk_openstack-sec-guide.xml:31(para)
-msgid "This book provides best practices and conceptual information about securing an OpenStack cloud."
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:24(para)
+msgid "OpenStack management utilities such as <systemitem class=\"service\">nova-manage</systemitem> and <systemitem class=\"service\">glance-manage</systemitem>"
 msgstr ""
 
-#: ./doc/security-guide/bk_openstack-sec-guide.xml:38(date)
-msgid "2013-12-02"
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:29(para)
+msgid "Out-of-band management interfaces, such as IPMI"
 msgstr ""
 
-#: ./doc/security-guide/bk_openstack-sec-guide.xml:42(para)
-msgid "Chapter on Object Storage added."
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:34(para)
+msgid "The OpenStack dashboard (horizon) provides administrators and tenants with a web-based graphical interface to provision and access cloud-based resources. The dashboard communicates with the back-end services through calls to the OpenStack API."
 msgstr ""
 
-#: ./doc/security-guide/bk_openstack-sec-guide.xml:48(date)
-msgid "2013-10-17"
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:41(title) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:103(title) ./doc/security-guide/ch026_compute.xml:22(title) ./doc/security-guide/ch026_compute.xml:67(title)
+msgid "Capabilities"
 msgstr ""
 
-#: ./doc/security-guide/bk_openstack-sec-guide.xml:52(para)
-msgid "Havana release."
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:43(para)
+msgid "As a cloud administrator, the dashboard provides an overall view of the size and state of your cloud. You can create users and tenants/projects, assign users to tenant/projects and set limits on the resources available for them."
 msgstr ""
 
-#: ./doc/security-guide/bk_openstack-sec-guide.xml:58(date)
-msgid "2013-07-02"
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:46(para)
+msgid "The dashboard provides tenant-users a self-service portal to provision their own resources within the limits set by administrators."
 msgstr ""
 
-#: ./doc/security-guide/bk_openstack-sec-guide.xml:62(para)
-msgid "Initial creation..."
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:49(para)
+msgid "The dashboard provides GUI support for routers and load-balancers. For example, the dashboard now implements all of the main Networking features."
 msgstr ""
 
-#: ./doc/security-guide/ch065_privacy.xml:7(title)
-msgid "Privacy"
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:52(para)
+msgid "It is an extensible <glossterm>Django</glossterm> web application that allows easy plug-in of third-party products and services, such as billing, monitoring, and additional management tools."
 msgstr ""
 
-#: ./doc/security-guide/ch065_privacy.xml:8(para)
-msgid "Privacy is an increasingly important element of a compliance program. Businesses are being held to a higher standard by their customers, who have increased interest in understanding how their data is treated from a privacy perspective."
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:55(para)
+msgid "The dashboard can also be branded for service providers and other commercial vendors."
 msgstr ""
 
-#: ./doc/security-guide/ch065_privacy.xml:9(para)
-msgid "An OpenStack deployment will likely need to demonstrate compliance with an organization’s Privacy Policy, with the U.S. – E.U. Safe Harbor framework, the ISO/IEC 29100:2011 privacy framework or with other privacy-specific guidelines. In the U.S. the AICPA has <link href=\"http://www.aicpa.org/interestareas/informationtechnology/resources/privacy/generallyacceptedprivacyprinciples/\">defined 10 privacy areas of focus</link>, OpenStack deployments within a commercial environment may desire to attest to some or all of these principles."
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:62(para)
+msgid "The dashboard requires cookies and JavaScript to be enabled in the web browser."
 msgstr ""
 
-#: ./doc/security-guide/ch065_privacy.xml:10(para)
-msgid "To aid OpenStack architects in the protection of personal data, it is recommended that OpenStack architects review the NIST publication 800-122, titled \"<emphasis>Guide to Protecting the Confidentiality of Personally Identifiable Information (PII)</emphasis>.\" This guide steps through the process of protecting:"
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:65(para)
+msgid "The web server that hosts dashboard should be configured for SSL to ensure data is encrypted."
 msgstr ""
 
-#: ./doc/security-guide/ch065_privacy.xml:12(para)
-msgid "\"<emphasis>any information about an individual maintained by an agency, including (1) any information that can be used to distinguish or trace an individual‘s identity, such as name, social security number, date and place of birth, mother‘s maiden name, or biometric records; and (2) any other information that is linked or linkable to an individual, such as medical, educational, financial, and employment information</emphasis>\""
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:68(para)
+msgid "Both the horizon web service and the OpenStack API it uses to communicate with the back-end are susceptible to web attack vectors such as denial of service and must be monitored."
 msgstr ""
 
-#: ./doc/security-guide/ch065_privacy.xml:14(para)
-msgid "Comprehensive privacy management requires significant preparation, thought and investment. Additional complications are introduced when building global OpenStack clouds, for example navigating the differences between U.S. and more restrictive E.U. privacy laws. In addition, extra care needs to be taken when dealing with sensitive PII that may include information such as credit card numbers or medical records. This sensitive data is not only subject to privacy laws but also regulatory and governmental regulations. By deferring to established best practices, including those published by governments, a holistic privacy management policy may be created and practiced for OpenStack deployments."
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:71(para)
+msgid "It is now possible (though there are numerous deployment/security implications) to upload an image file directly from a user’s hard disk to OpenStack Image Service through the dashboard. For multi-gigabyte images it is still strongly recommended that the upload be done using the <placeholder-1/> CLI."
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:8(title)
-msgid "Networking services"
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:81(para)
+msgid "Create and manage security groups through dashboard. The security groups allows L3-L4 packet filtering for security policies to protect virtual machines."
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:9(para)
-msgid "In the initial architectural phases of designing your OpenStack Network infrastructure it is important to ensure appropriate expertise is available to assist with the design of the physical networking infrastructure, to identify proper security controls and auditing mechanisms."
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:91(citetitle)
+msgid "Grizzly Release Notes"
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:10(para)
-msgid "OpenStack Networking adds a layer of virtualized network services - giving tenants the capability to architect their own, virtual networks. These virtualized services are not as currently as mature as their traditional networking counterparts. It is important to be aware of the current state of these virtualized services and what controls may need to be implemented at the virtualized and traditional network boundary."
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:96(para)
+msgid "The OpenStack API is a RESTful web service endpoint to access, provision and automate cloud-based resources. Operators and users typically access the API through command-line utilities (for example, <placeholder-1/> or <placeholder-2/>), language-specific libraries, or third-party tools."
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:12(title)
-msgid "L2 isolation using VLANs and tunneling"
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:105(para)
+msgid "To the cloud administrator, the API provides an overall view of the size and state of the cloud deployment and allows the creation of users, tenants/projects, assigning users to tenants/projects, and specifying resource quotas on a per tenant/project basis."
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:13(para)
-msgid "OpenStack networking can employ two different mechanisms for traffic segregation on a per tenant/network combination: VLANs (IEEE 802.1Q tagging) or L2 tunnels using GRE encapsulation. Which method you choose for traffic segregation and isolation is determined by the scope and scale of your OpenStack deployment."
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:112(para)
+msgid "The API provides a tenant interface for provisioning, managing, and accessing their resources."
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:15(title)
-msgid "VLANs"
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:119(para)
+msgid "The API service should be configured for SSL to ensure data is encrypted."
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:16(para)
-msgid "VLANs are realized as packets on a specific physical network containing IEEE 802.1Q headers with a specific VLAN ID (VID) field value. VLAN networks sharing the same physical network are isolated from each other at L2, and can even have overlapping IP address spaces. Each distinct physical network supporting VLAN networks is treated as a separate VLAN trunk, with a distinct space of VID values. Valid VID values are 1 through 4094."
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:122(para)
+msgid "As a web service, OpenStack API is susceptible to familiar web site attack vectors such as denial of service attacks."
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:17(para)
-msgid "VLAN configuration complexity depends on your OpenStack design requirements. In order to allow OpenStack Networking to efficiently use VLANs, you must allocate a VLAN range (one for each tenant) and turn each compute node physical switch port into a VLAN trunk port."
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:129(para)
+msgid "It has become industry practice to use secure shell (SSH) access for the management of Linux and Unix systems. SSH uses secure cryptographic primitives for communication. With the scope and importance of SSH in typical OpenStack deployments, it is important to understand best practices for deploying SSH."
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:19(para)
-msgid "NOTE: If you intend for your network to support more than 4094 tenants VLAN is probably not the correct option for you as multiple 'hacks' are required to extend the VLAN tags to more than 4094 tenants."
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:131(title)
+msgid "Host key fingerprints"
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:23(title)
-msgid "L2 tunneling"
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:132(para)
+msgid "Often overlooked is the need for key management for SSH hosts. As most or all hosts in an OpenStack deployment will provide an SSH service, it is important to have confidence in connections to these hosts. It cannot be understated that failing to provide a reasonably secure and accessible method to verify SSH host key fingerprints is ripe for abuse and exploitation."
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:24(para)
-msgid "Network tunneling encapsulates each tenant/network combination with a unique \"tunnel-id\" that is used to identify the network traffic belonging to that combination. The tenant's L2 network connectivity is independent of physical locality or underlying network design. By encapsulating traffic inside IP packets, that traffic can cross Layer-3 boundaries, removing the need for preconfigured VLANs and VLAN trunking. Tunneling adds a layer of obfuscation to network data traffic, reducing the visibility of individual tenant traffic from a monitoring point of view."
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:133(para)
+msgid "All SSH daemons have private host keys and, upon connection, offer a host key fingerprint. This host key fingerprint is the hash of an unsigned public key. It is important these host key fingerprints are known in advance of making SSH connections to those hosts. Verification of host key fingerprints is instrumental in detecting man-in-the-middle attacks."
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:25(para)
-msgid "OpenStack Networking currently only supports GRE encapsulation with planned future support of VXLAN due in the Havana release."
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:134(para)
+msgid "Typically, when an SSH daemon is installed, host keys will be generated. It is necessary that the hosts have sufficient entropy during host key generation. Insufficient entropy during host key generation can result in the possibility to eavesdrop on SSH sessions."
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:26(para)
-msgid "The choice of technology to provide L2 isolation is dependent upon the scope and size of tenant networks that will be created in your deployment. If your environment has limited VLAN ID availability or will have a large number of L2 networks, it is our recommendation that you utilize tunneling."
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:135(para)
+msgid "Once the SSH host key is generated, the host key fingerprint should be stored in a secure and queriable location. One particularly convenient solution is DNS using SSHFP resource records as defined in RFC-4255. For this to be secure, it is necessary that DNSSEC be deployed."
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:30(title)
-msgid "Network services"
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:139(title)
+msgid "Management utilities"
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:31(para)
-msgid "The choice of tenant network isolation affects how the network security and control boundary is implemented for tenant services. The following additional network services are either available or currently under development to enhance the security posture of the OpenStack network architecture."
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:140(para)
+msgid "The OpenStack Management Utilities are open-source Python command-line clients that make API calls. There is a client for each OpenStack service (for example, <systemitem class=\"service\">nova</systemitem>, <systemitem class=\"service\">glance</systemitem>). In addition to the standard CLI client, most of the services have a management command-line utility which makes direct calls to the database. These dedicated management utilities are slowly being deprecated."
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:33(title)
-msgid "Access control lists"
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:152(para)
+msgid "The dedicated management utilities (*-manage) in some cases use the direct database connection."
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:34(para)
-msgid "OpenStack Compute supports tenant network traffic access controls directly when deployed with the legacy nova-network service, or may defer access control to the OpenStack Networking service."
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:155(para)
+msgid "Ensure that the .rc file which has your credential information is secured."
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:35(para)
-msgid "Note, legacy nova-network security groups are applied to all virtual interface ports on an instance using IPTables."
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:161(para)
+msgid "<citetitle>OpenStack End User Guide</citetitle> section <link href=\"http://docs.openstack.org/user-guide/content/section_cli_overview.html\">command-line clients overview</link>"
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:36(para)
-msgid "Security groups allow administrators and tenants the ability to specify the type of traffic, and direction (ingress/egress) that is allowed to pass through a virtual interface port. Security groups rules are stateful L2-L4 traffic filters."
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:162(para)
+msgid "<citetitle>OpenStack End User Guide</citetitle> section <link href=\"http://docs.openstack.org/user-guide/content/cli_openrc.html\">Download and source the OpenStack RC file</link>"
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:37(para)
-msgid "It is our recommendation that you enable security groups through OpenStack Networking."
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:166(title)
+msgid "Out-of-band management interface"
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:41(title)
-msgid "L3 routing and NAT"
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:167(para)
+msgid "OpenStack management relies on out-of-band management interfaces such as the IPMI protocol to access into nodes running OpenStack components. IPMI is a very popular specification to remotely manage, diagnose, and reboot servers whether the operating system is running or the system has crashed."
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:42(para)
-msgid "OpenStack Networking routers can connect multiple L2 networks, and can also provide a <emphasis>gateway</emphasis> that connects one or more private L2 networks to a shared <emphasis>external</emphasis> network, such as a public network for access to the Internet."
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:176(para)
+msgid "Use strong passwords and safeguard them, or use client-side SSL authentication."
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:43(para)
-msgid "The L3 router provides basic Network Address Translation (NAT) capabilities on <emphasis>gateway</emphasis> ports that uplink the router to external networks. This router SNATs (Static NAT) all traffic by default, and supports floating IPs, which creates a static one-to-one mapping from a public IP on the external network to a private IP on one of the other subnets attached to the router."
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:179(para)
+msgid "Ensure that the network interfaces are on their own private(management or a separate) network. Segregate management domains with firewalls or other network gear."
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:44(para)
-msgid "It is our recommendation to leverage per tenant L3 routing and Floating IPs for more granular connectivity of tenant VMs."
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:182(para)
+msgid "If you use a web interface to interact with the <glossterm>BMC</glossterm>/IPMI, always use the SSL interface, such as https or port 443. This SSL interface should <emphasis role=\"bold\">NOT</emphasis> use self-signed certificates, as is often default, but should have trusted certificates using the correctly defined fully qualified domain names (FQDNs)."
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:47(title)
-msgid "Quality of Service (QoS)"
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:191(para)
+msgid "Monitor the traffic on the management network. The anomalies might be easier to track than on the busier compute nodes."
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:48(para)
-msgid "The ability to set QoS on the virtual interface ports of tenant instances is a current deficiency for OpenStack Networking. The application of QoS for traffic shaping and rate-limiting at the physical network edge device is insufficient due to the dynamic nature of workloads in an OpenStack deployment and can not be leveraged in the traditional way. QoS-as-a-Service (QoSaaS) is currently in development for the OpenStack Networking Havana release as an experimental feature. QoSaaS is planning to provide the following services:"
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:196(para)
+msgid "Out of band management interfaces also often include graphical machine console access. It is often possible, although not necessarily default, that these interfaces are encrypted. Consult with your system software documentation for encrypting these interfaces."
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:50(para)
-msgid "Traffic shaping through DSCP markings"
+#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:200(link)
+msgid "Hacking servers that are turned off"
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:53(para)
-msgid "Rate-limiting on a per port/network/tenant basis."
+#: ./doc/security-guide/ch043_database-transport-security.xml:8(title)
+msgid "Database transport security"
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:56(para)
-msgid "Port mirroring (through open source or third-party plug-ins)"
+#: ./doc/security-guide/ch043_database-transport-security.xml:9(para)
+msgid "This chapter covers issues related to network communications to and from the database server. This includes IP address bindings and encrypting network traffic with SSL."
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:59(para)
-msgid "Flow analysis (through open source or third-party plug-ins)"
+#: ./doc/security-guide/ch043_database-transport-security.xml:14(title)
+msgid "Database server IP address binding"
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:62(para)
-msgid "Tenant traffic port mirroring or Network Flow monitoring is currently not an exposed feature in OpenStack Networking. There are third-party plug-in extensions that do provide Port Mirroring on a per port/network/tenant basis. If Open vSwitch is used on the networking hypervisor, it is possible to enable sFlow and port mirroring, however it will require some operational effort to implement."
+#: ./doc/security-guide/ch043_database-transport-security.xml:15(para)
+msgid "To isolate sensitive database communications between the services and the database, we strongly recommend that the database server(s) be configured to only allow communications to and from the database over an isolated management network. This is achieved by restricting the interface or IP address on which the database server binds a network socket for incoming client connections."
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:65(title)
-msgid "Load balancing"
+#: ./doc/security-guide/ch043_database-transport-security.xml:24(title)
+msgid "Restricting bind address for MySQL"
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:66(para)
-msgid "An experimental feature in the Grizzly release of OpenStack Networking is Load-Balancer-as-a-service (LBaaS). The LBaaS API gives early adopters and vendors a chance to build implementations of the technology. The reference implementation however, is still experimental and should likely not be run in a production environment. The current reference implementation is based on HA-Proxy. There are third-party plug-ins in development for extensions in OpenStack Networking to provide extensive L4-L7 functionality for virtual interface ports."
+#: ./doc/security-guide/ch043_database-transport-security.xml:25(para) ./doc/security-guide/ch043_database-transport-security.xml:63(para)
+msgid "In <filename>my.cnf</filename>:"
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:69(title)
-msgid "Firewalls"
+#: ./doc/security-guide/ch043_database-transport-security.xml:31(title)
+msgid "Restricting listen address for PostgreSQL"
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:70(para)
-msgid "FW-as-a-Service (FWaaS) is currently in development for the OpenStack Networking Havana release as an experimental feature. FWaaS will address the need to manage and leverage the rich set of security features provided by typical firewall products which are typically far more comprehensive than what is currently provided by security groups. There are third-party plug-ins in development for extensions in OpenStack Networking to support this."
+#: ./doc/security-guide/ch043_database-transport-security.xml:32(para)
+msgid "In <filename>postgresql.conf</filename>:"
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:71(para)
-msgid "It is critical during the design of an OpenStack Networking infrastructure to understand the current features and limitations of network services that are available. Understanding where the boundaries of your virtual and physical networks will help you add the required security controls in your environment."
+#: ./doc/security-guide/ch043_database-transport-security.xml:37(title)
+msgid "Database transport"
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:75(title)
-msgid "Network services extensions"
+#: ./doc/security-guide/ch043_database-transport-security.xml:38(para)
+msgid "In addition to restricting database communications to the management network, we also strongly recommend that the cloud administrator configure their database backend to require SSL. Using SSL for the database client connections protects the communications from tampering and eavesdropping. As will be discussed in the next section, using SSL also provides the framework for doing database user authentication through X.509 certificates (commonly referred to as PKI). Below is guidance on how SSL is typically configured for the two popular database backends MySQL and PostgreSQL."
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:76(para)
-msgid "Here is a list of known plug-ins provided by the open source community or by SDN companies that work with OpenStack Networking:"
+#: ./doc/security-guide/ch043_database-transport-security.xml:50(para)
+msgid "When installing the certificate and key files, ensure that the file permissions are restricted, for example <placeholder-1/>, and the ownership is restricted to the database daemon user to prevent unauthorized access by other processes and users on the database server."
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:77(para)
-msgid "Big Switch Controller plug-in, Brocade neutron plug-in Brocade neutron plug-in, Cisco UCS/Nexus plug-in, Cloudbase Hyper-V plug-in, Extreme Networks plug-in, Juniper Networks neutron plug-in, Linux Bridge plug-in, Mellanox neutron plug-in, MidoNet plug-in, NEC OpenFlow plug-in, Open vSwitch plug-in, PLUMgrid plug-in, Ruijie Networks plug-in, Ryu OpenFlow Controller plug-in, VMware NSX plug-in."
+#: ./doc/security-guide/ch043_database-transport-security.xml:60(title)
+msgid "MySQL SSL configuration"
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:86(title)
-msgid "Networking services limitations"
+#: ./doc/security-guide/ch043_database-transport-security.xml:61(para)
+msgid "The following lines should be added in the system-wide MySQL configuration file:"
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:87(para)
-msgid "OpenStack Networking has the following known limitations:"
+#: ./doc/security-guide/ch043_database-transport-security.xml:69(para) ./doc/security-guide/ch043_database-transport-security.xml:80(para)
+msgid "Optionally, if you wish to restrict the set of SSL ciphers used for the encrypted connection. See <link href=\"http://www.openssl.org/docs/apps/ciphers.html\">http://www.openssl.org/docs/apps/ciphers.html</link> for a list of ciphers and the syntax for specifying the cipher string:"
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:90(term)
-msgid "Overlapping IP addresses"
+#: ./doc/security-guide/ch043_database-transport-security.xml:74(title)
+msgid "PostgreSQL SSL configuration"
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:92(para)
-msgid "If nodes that run either <systemitem class=\"service\">neutron-l3-agent</systemitem> or <systemitem class=\"service\">neutron-dhcp-agent</systemitem> use overlapping IP addresses, those nodes must use Linux network namespaces. By default, the DHCP and L3 agents use Linux network namespaces. However, if the host does not support these namespaces, run the DHCP and L3 agents on different hosts."
+#: ./doc/security-guide/ch043_database-transport-security.xml:75(para)
+msgid "The following lines should be added in the system-wide PostgreSQL configuration file, <filename>postgresql.conf</filename>."
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:102(para)
-msgid "If network namespace support is not present, a further limitation of the L3 agent is that only a single logical router is supported."
+#: ./doc/security-guide/ch043_database-transport-security.xml:82(para)
+msgid "The server certificate, key, and certificate authority (CA) files should be placed in the $PGDATA directory in the following files:"
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:109(term)
-msgid "Multi-host DHCP-agent"
+#: ./doc/security-guide/ch043_database-transport-security.xml:86(para)
+msgid "<filename>$PGDATA/server.crt</filename> - Server certificate"
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:111(para)
-msgid "OpenStack Networking supports multiple L3 and DHCP agents with load balancing. However, tight coupling of the location of the virtual machine is not supported."
+#: ./doc/security-guide/ch043_database-transport-security.xml:90(para)
+msgid "<filename>$PGDATA/server.key</filename> - Private key corresponding to <filename>server.crt</filename>"
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:119(term)
-msgid "No IPv6 support for L3 agents"
+#: ./doc/security-guide/ch043_database-transport-security.xml:94(para)
+msgid "<filename>$PGDATA/root.crt</filename> - Trusted certificate authorities"
 msgstr ""
 
-#: ./doc/security-guide/ch032_networking-best-practices.xml:121(para)
-msgid "The neutron-l3-agent, used by many plug-ins to implement L3 forwarding, supports only IPv4 forwarding."
+#: ./doc/security-guide/ch043_database-transport-security.xml:98(para)
+msgid "<filename>$PGDATA/root.crl</filename> - Certificate revocation list"
 msgstr ""
 
 #. When image changes, this message will be marked fuzzy or untranslated for you.
@@ -1793,6 +4391,462 @@ msgstr ""
 msgid "If your use case involves keeping live migration enabled, then libvirtd can provide tunneled, encrypted live migrations. That said, this feature is not currently exposed in OpenStack Dashboard, nor the nova-client commands and can only be accessed through manual configuration of libvirtd. Encrypted live migration modifies the live migration process by first copying the instance data from the running hypervisor to libvirtd. From there an encrypted tunnel is created between the libvirtd processes on both hosts. Finally, the destination libvirtd process copies the instance back to the underlying hypervisor."
 msgstr ""
 
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch008_system-roles-types.xml:101(None) ./doc/security-guide/ch008_system-roles-types.xml:106(None)
+msgid "@@image: 'static/services-protocols-ports.png'; md5=fb1e9f47d969127b7a5ca683d38cfe20"
+msgstr ""
+
+#: ./doc/security-guide/ch008_system-roles-types.xml:8(title)
+msgid "System documentation requirements"
+msgstr ""
+
+#: ./doc/security-guide/ch008_system-roles-types.xml:9(para)
+msgid "The system documentation for an OpenStack cloud deployment should follow the templates and best practices for the Enterprise Information Technology System in your organization. Organizations often have compliance requirements which may require an overall System Security Plan to inventory and document the architecture of a given system. There are common challenges across the industry related to documenting the dynamic cloud infrastructure and keeping the information up-to-date."
+msgstr ""
+
+#: ./doc/security-guide/ch008_system-roles-types.xml:18(title)
+msgid "System roles and types"
+msgstr ""
+
+#: ./doc/security-guide/ch008_system-roles-types.xml:19(para)
+msgid "The two broadly defined types of nodes that generally make up an OpenStack installation are:"
+msgstr ""
+
+#: ./doc/security-guide/ch008_system-roles-types.xml:23(para)
+msgid "Infrastructure nodes. The nodes that run the cloud related services such as the OpenStack Identity Service, the message queuing service, storage, networking, and other services required to support the operation of the cloud."
+msgstr ""
+
+#: ./doc/security-guide/ch008_system-roles-types.xml:30(para)
+msgid "Compute, storage, or other resource nodes. Provide storage capacity or virtual machines for your cloud."
+msgstr ""
+
+#: ./doc/security-guide/ch008_system-roles-types.xml:37(title)
+msgid "System inventory"
+msgstr ""
+
+#: ./doc/security-guide/ch008_system-roles-types.xml:38(para)
+msgid "Documentation should provide a general description of the OpenStack environment and cover all systems used (production, development, test, etc.). Documenting system components, networks, services, and software often provides the bird's-eye view needed to thoroughly cover and consider security concerns, attack vectors and possible security domain bridging points. A system inventory may need to capture ephemeral resources such as virtual machines or virtual disk volumes that would otherwise be persistent resources in a traditional IT system."
+msgstr ""
+
+#: ./doc/security-guide/ch008_system-roles-types.xml:48(title)
+msgid "Hardware inventory"
+msgstr ""
+
+#: ./doc/security-guide/ch008_system-roles-types.xml:49(para)
+msgid "Clouds without stringent compliance requirements for written documentation might benefit from having a Configuration Management Database (<glossterm>CMDB</glossterm>). CMDBs are normally used for hardware asset tracking and overall life-cycle management. By leveraging a CMDB, an organization can quickly identify cloud infrastructure hardware. For example, compute nodes, storage nodes, and network devices that exist on the network but that might not be adequately protected and/or forgotten. OpenStack provisioning system might provide some CMDB-like functions especially if auto-discovery features of hardware attributes are available."
+msgstr ""
+
+#: ./doc/security-guide/ch008_system-roles-types.xml:63(title)
+msgid "Software inventory"
+msgstr ""
+
+#: ./doc/security-guide/ch008_system-roles-types.xml:64(para)
+msgid "Just as with hardware, all software components within the OpenStack deployment should be documented. Components here should include system databases; OpenStack software components and supporting sub-components; and, supporting infrastructure software such as load-balancers, reverse proxies, and network address translators. Having an authoritative list like this may be critical toward understanding total system impact due to a compromise or vulnerability of a specific class of software."
+msgstr ""
+
+#: ./doc/security-guide/ch008_system-roles-types.xml:76(title)
+msgid "Network topology"
+msgstr ""
+
+#: ./doc/security-guide/ch008_system-roles-types.xml:77(para)
+msgid "A network topology should be provided with highlights specifically calling out the data flows and bridging points between the security domains. Network ingress and egress points should be identified along with any OpenStack logical system boundaries. Multiple diagrams may be needed to provide complete visual coverage of the system. A network topology document should include virtual networks created on behalf of tenants by the system along with virtual machine instances and gateways created by OpenStack."
+msgstr ""
+
+#: ./doc/security-guide/ch008_system-roles-types.xml:88(title)
+msgid "Services, protocols and ports"
+msgstr ""
+
+#: ./doc/security-guide/ch008_system-roles-types.xml:89(para)
+msgid "The service, protocols and ports table provides important additional detail of an OpenStack deployment. A table view of all services running within the cloud infrastructure can immediately inform, guide, and help check security procedures. Firewall configuration, service port conflicts, security remediation areas, and compliance requirements become easier to manage when you have concise information available. Consider the following table:"
+msgstr ""
+
+#: ./doc/security-guide/ch008_system-roles-types.xml:109(para)
+msgid "Referencing a table of services, protocols and ports can help in understanding the relationship between OpenStack components. It is highly recommended that OpenStack deployments have information similar to this on record."
+msgstr ""
+
+#: ./doc/security-guide/ch018_case-studies-pkissl.xml:8(title)
+msgid "Case studies: PKI and certificate management"
+msgstr ""
+
+#: ./doc/security-guide/ch018_case-studies-pkissl.xml:9(para)
+msgid "In this case study we discuss how Alice and Bob would address deployment of PKI certification authorities (CA) and certificate management."
+msgstr ""
+
+#: ./doc/security-guide/ch018_case-studies-pkissl.xml:12(para)
+msgid "Alice as a cloud architect within a government agency knows that her agency operates its own certification authority. Alice contacts the PKI office in her agency that manages her PKI and certificate issuance. Alice obtains certificates issued by this CA and configures the services within both the public and management security domains to use these certificates. Since Alice's OpenStack deployment exists entirely on a disconnected from the Internet network, she makes sure to remove all default CA bundles that contain external public CA providers to ensure the OpenStack services only accept client certificates issued by her agency's CA."
+msgstr ""
+
+#: ./doc/security-guide/ch018_case-studies-pkissl.xml:16(para)
+msgid "Bob is architecting a public cloud and needs to ensure that the publicly facing OpenStack services are using certificates issued by a major public CA. Bob acquires certificates for his public OpenStack services and configures the services to use PKI and SSL and includes the public CAs in his trust bundle for the services. Additionally, Bob also wants to further isolate the internal communications amongst the services within the management security domain. Bob contacts the team within his organization that is responsible for managing his organizations PKI and issuance of certificates using their own internal CA. Bob obtains certificates issued by this internal CA and configures the services that communicate within the management security domain to use these certificates and configures the services to only accept client certificates issued by his internal CA."
+msgstr ""
+
+#: ./doc/security-guide/ch041_database-backend-considerations.xml:7(title)
+msgid "Database back-end considerations"
+msgstr ""
+
+#: ./doc/security-guide/ch041_database-backend-considerations.xml:8(para)
+msgid "The choice of database server is an important consideration in the security of an OpenStack deployment. While security considerations are not the only basis on which a database server must be chosen, security considerations are the only ones within the scope of this book. In practice, OpenStack only supports two database types: PostgreSQL and MySQL."
+msgstr ""
+
+#: ./doc/security-guide/ch041_database-backend-considerations.xml:9(para)
+msgid "PostgreSQL has a number of desirable security features such as Kerberos authentication, object-level security, and encryption support. The PostgreSQL community has done well to provide solid guidance, documentation, and tooling to promote positive security practices."
+msgstr ""
+
+#: ./doc/security-guide/ch041_database-backend-considerations.xml:10(para)
+msgid "MySQL has a large community, widespread adoption, and provides high availability options. MySQL also has the ability to provide enhanced client authentication by way of plug-in authentication mechanisms. Forked distributions in the MySQL community provide many options for consideration. It is important to choose a specific implementation of MySQL based on a thorough evaluation of the security posture and the level of support provided for the given distribution."
+msgstr ""
+
+#: ./doc/security-guide/ch041_database-backend-considerations.xml:12(title)
+msgid "Security references for database back-ends"
+msgstr ""
+
+#: ./doc/security-guide/ch041_database-backend-considerations.xml:13(para)
+msgid "Those deploying MySQL or PostgreSQL are advised to refer to existing security guidance. Some references are listed below:"
+msgstr ""
+
+#: ./doc/security-guide/ch041_database-backend-considerations.xml:14(para)
+msgid "MySQL:"
+msgstr ""
+
+#: ./doc/security-guide/ch041_database-backend-considerations.xml:16(link)
+msgid "OWASP MySQL Hardening"
+msgstr ""
+
+#: ./doc/security-guide/ch041_database-backend-considerations.xml:19(link)
+msgid "MySQL Pluggable Authentication"
+msgstr ""
+
+#: ./doc/security-guide/ch041_database-backend-considerations.xml:22(link)
+msgid "Security in MySQL"
+msgstr ""
+
+#: ./doc/security-guide/ch041_database-backend-considerations.xml:25(para)
+msgid "PostgreSQL:"
+msgstr ""
+
+#: ./doc/security-guide/ch041_database-backend-considerations.xml:27(link)
+msgid "OWASP PostgreSQL Hardening"
+msgstr ""
+
+#: ./doc/security-guide/ch041_database-backend-considerations.xml:30(link)
+msgid "Total security in a PostgreSQL database"
+msgstr ""
+
+#: ./doc/security-guide/ch039_case-studies-messaging.xml:8(title)
+msgid "Case studies: messaging"
+msgstr ""
+
+#: ./doc/security-guide/ch039_case-studies-messaging.xml:9(para)
+msgid "The message queue is a critical piece of infrastructure that supports a number of OpenStack services but is most strongly associated with the Compute service. Due to the nature of the message queue service, Alice and Bob have similar security concerns. One of the larger concerns that remains is that many systems have access to this queue and there is no way for a consumer of the queue messages to verify which host or service placed the messages on the queue. An attacker who is able to successfully place messages on the queue is able to create and delete VM instances, attach the block storage of any tenant and a myriad of other malicious actions. There are a number of solutions on the horizon to fix this, with several proposals for message signing and encryption making their way through the OpenStack development process."
+msgstr ""
+
+#: ./doc/security-guide/ch039_case-studies-messaging.xml:12(para)
+msgid "In this case Alice's controls mimic those Bob has deployed for the public cloud."
+msgstr ""
+
+#: ./doc/security-guide/ch039_case-studies-messaging.xml:16(para)
+msgid "Bob assumes that at some point infrastructure or networks underpinning the Compute service may become compromised. Due to this, he recognizes the importance of locking down access to the message queue. To do this Bob deploys his RabbitMQ servers with SSL and X.509 client auth for access control. This in turn limits the capabilities of an attacker who has compromised a system that does not have queue access."
+msgstr ""
+
+#: ./doc/security-guide/ch039_case-studies-messaging.xml:17(para)
+msgid "Additionally, Bob adds strong network ACL rulesets to enforce which endpoints can communicate with the message servers. This second control provides some additional assurance should the other protections fail."
+msgstr ""
+
+#: ./doc/security-guide/ch062_audit-guidance.xml:8(title)
+msgid "Understanding the audit process"
+msgstr ""
+
+#: ./doc/security-guide/ch062_audit-guidance.xml:9(para)
+msgid "Information system security compliance is reliant on the completion of two foundational processes:"
+msgstr ""
+
+#: ./doc/security-guide/ch062_audit-guidance.xml:13(para)
+msgid "<emphasis role=\"bold\">Implementation and operation of security controls.</emphasis> Aligning the information system with in-scope standards and regulations involves internal tasks which must be conducted before a formal assessment. Auditors may be involved at this state to conduct gap analysis, provide guidance, and increase the likelihood of successful certification."
+msgstr ""
+
+#: ./doc/security-guide/ch062_audit-guidance.xml:23(para)
+msgid "<emphasis role=\"bold\">Independent verification and validation.</emphasis> Demonstration to a neutral third-party that system security controls are implemented and operating effectively, in compliance with in-scope standards and regulations, is required before many information systems achieve certified status. Many certifications require periodic audits to ensure continued certification, considered part of an overarching continuous monitoring practice."
+msgstr ""
+
+#: ./doc/security-guide/ch062_audit-guidance.xml:36(title)
+msgid "Determining audit scope"
+msgstr ""
+
+#: ./doc/security-guide/ch062_audit-guidance.xml:37(para)
+msgid "Determining audit scope, specifically what controls are needed and how to design or modify an OpenStack deployment to satisfy them, should be the initial planning step."
+msgstr ""
+
+#: ./doc/security-guide/ch062_audit-guidance.xml:38(para)
+msgid "When scoping OpenStack deployments for compliance purposes, consider prioritizing controls around sensitive services, such as command and control functions and the base virtualization technology. Compromises of these facilities may impact an OpenStack environment in its entirety."
+msgstr ""
+
+#: ./doc/security-guide/ch062_audit-guidance.xml:39(para)
+msgid "Scope reduction helps ensure OpenStack architects establish high quality security controls which are tailored to a particular deployment, however it is paramount to ensure these practices do not omit areas or features from security hardening. A common example is applicable to PCI-DSS guidelines, where payment related infrastructure may be scrutinized for security issues, but supporting services are left ignored, and vulnerable to attack."
+msgstr ""
+
+#: ./doc/security-guide/ch062_audit-guidance.xml:40(para)
+msgid "When addressing compliance, you can increase efficiency and reduce work effort by identifying common areas and criteria that apply across multiple certifications. Much of the audit principles and guidelines discussed in this book will assist in identifying these controls, additionally a number of external entities provide comprehensive lists. The following are some examples:"
+msgstr ""
+
+#: ./doc/security-guide/ch062_audit-guidance.xml:41(para)
+msgid "The <link href=\"https://cloudsecurityalliance.org/research/ccm/\">Cloud Security Alliance Cloud Controls Matrix</link> (CCM) assists both cloud providers and consumers in assessing the overall security of a cloud provider. The CSA CMM provides a controls framework that map to many industry-accepted standards and regulations including the ISO 27001/2, ISACA, COBIT, PCI, NIST, Jericho Forum and NERC CIP."
+msgstr ""
+
+#: ./doc/security-guide/ch062_audit-guidance.xml:42(para)
+msgid "The <link href=\"https://fedorahosted.org/scap-security-guide/\">SCAP Security Guide</link> is another useful reference. This is still an emerging source, but we anticipate that this will grow into a tool with controls mappings that are more focused on the US federal government certifications and recommendations. For example, the SCAP Security Guide currently has some mappings for security technical implementation guides (STIGs) and NIST-800-53."
+msgstr ""
+
+#: ./doc/security-guide/ch062_audit-guidance.xml:43(para)
+msgid "These control mappings will help identify common control criteria across certifications, and provide visibility to both auditors and auditees on problem areas within control sets for particular compliance certifications and attestations."
+msgstr ""
+
+#: ./doc/security-guide/ch062_audit-guidance.xml:46(title)
+msgid "Internal audit"
+msgstr ""
+
+#: ./doc/security-guide/ch062_audit-guidance.xml:47(para)
+msgid "Once a cloud is deployed, it is time for an internal audit. This is the time compare the controls you identified above with the design, features, and deployment strategies utilized in your cloud. The goal is to understand how each control is handled and where gaps exist. Document all of the findings for future reference."
+msgstr ""
+
+#: ./doc/security-guide/ch062_audit-guidance.xml:48(para)
+msgid "When auditing an OpenStack cloud it is important to appreciate the multi-tenant environment inherent in the OpenStack architecture. Some critical areas for concern include data disposal, hypervisor security, node hardening, and authentication mechanisms."
+msgstr ""
+
+#: ./doc/security-guide/ch062_audit-guidance.xml:51(title)
+msgid "Prepare for external audit"
+msgstr ""
+
+#: ./doc/security-guide/ch062_audit-guidance.xml:52(para)
+msgid "Once the internal audit results look good, it is time to prepare for an external audit. There are several key actions to take at this stage, these are outlined below:"
+msgstr ""
+
+#: ./doc/security-guide/ch062_audit-guidance.xml:54(para)
+msgid "Maintain good records from your internal audit. These will prove useful during the external audit so you can be prepared to answer questions about mapping the compliance controls to a particular deployment."
+msgstr ""
+
+#: ./doc/security-guide/ch062_audit-guidance.xml:57(para)
+msgid "Deploy automated testing tools to ensure that the cloud remains compliant over time."
+msgstr ""
+
+#: ./doc/security-guide/ch062_audit-guidance.xml:60(para)
+msgid "Select an auditor."
+msgstr ""
+
+#: ./doc/security-guide/ch062_audit-guidance.xml:63(para)
+msgid "Selecting an auditor can be challenging. Ideally, you are looking for someone with experience in cloud compliance audits. OpenStack experience is another big plus. Often it is best to consult with people who have been through this process for referrals. Cost can vary greatly depending on the scope of the engagement and the audit firm considered."
+msgstr ""
+
+#: ./doc/security-guide/ch062_audit-guidance.xml:66(title)
+msgid "External audit"
+msgstr ""
+
+#: ./doc/security-guide/ch062_audit-guidance.xml:67(para)
+msgid "This is the formal audit process. Auditors will test security controls in scope for a specific certification, and demand evidentiary requirements to prove that these controls were also in place for the audit window (for example SOC 2 audits generally evaluate security controls over a 6-12 months period). Any control failures are logged, and will be documented in the external auditors final report. Dependent on the type of OpenStack deployment, these reports may be viewed by customers, so it is important to avoid control failures. This is why audit preparation is so important."
+msgstr ""
+
+#: ./doc/security-guide/ch062_audit-guidance.xml:70(title)
+msgid "Compliance maintenance"
+msgstr ""
+
+#: ./doc/security-guide/ch062_audit-guidance.xml:71(para)
+msgid "The process doesn't end with a single external audit. Most certifications require continual compliance activities which means repeating the audit process periodically. We recommend integrating automated compliance verification tools into a cloud to ensure that it is compliant at all times. This should be in done in addition to other security monitoring tools. Remember that the goal is both security <emphasis>and</emphasis> compliance. Failing on either of these fronts will significantly complicate future audits."
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch005_security-domains.xml:29(None) ./doc/security-guide/ch005_security-domains.xml:32(None)
+msgid "@@image: 'static/untrusted_trusted.png'; md5=a582dac2ad0b3f439fd4b08386853056"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch005_security-domains.xml:60(None) ./doc/security-guide/ch005_security-domains.xml:63(None)
+msgid "@@image: 'static/bridging_security_domains_1.png'; md5=0d5ca26c51882ce3253405e91a597715"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch005_security-domains.xml:68(None) ./doc/security-guide/ch005_security-domains.xml:71(None)
+msgid "@@image: 'static/bridging_domains_clouduser.png'; md5=17c8a233ee7de17d2f600c7f6f6afe24"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch005_security-domains.xml:134(None) ./doc/security-guide/ch005_security-domains.xml:137(None)
+msgid "@@image: 'static/threat_actors.png'; md5=114c2f9bd9d0319bdd83f9e229d44649"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch005_security-domains.xml:171(None) ./doc/security-guide/ch005_security-domains.xml:174(None)
+msgid "@@image: 'static/high-capability.png'; md5=b7ab599c8b40558a52c0ca86aad89741"
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:8(title)
+msgid "Security boundaries and threats"
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:9(para)
+msgid "A cloud can be abstracted as a collection of logical components by virtue of their function, users, and shared security concerns, which we call security domains. Threat actors and vectors are classified based on their motivation and access to resources. Our goal is to provide you a sense of the security concerns with respect to each domain depending on your risk/vulnerability protection objectives."
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:11(title)
+msgid "Security domains"
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:12(para)
+msgid "A security domain comprises users, applications, servers or networks that share common trust requirements and expectations within a system. Typically they have the same authentication and authorization (AuthN/Z) requirements and users."
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:13(para)
+msgid "Although you may desire to break these domains down further (we later discuss where this may be appropriate), we generally refer to four distinct security domains which form the bare minimum that is required to deploy any OpenStack cloud securely. These security domains are:"
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:15(para) ./doc/security-guide/ch005_security-domains.xml:36(title)
+msgid "Public"
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:18(para) ./doc/security-guide/ch005_security-domains.xml:41(title)
+msgid "Guest"
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:21(para) ./doc/security-guide/ch005_security-domains.xml:46(title)
+msgid "Management"
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:24(para) ./doc/security-guide/ch005_security-domains.xml:51(title)
+msgid "Data"
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:27(para)
+msgid "We selected these security domains because they can be mapped independently or combined to represent the majority of the possible areas of trust within a given OpenStack deployment. For example, some deployment topologies combine both guest and data domains onto one physical network versus others, which have these networks physically separated. In each case, the cloud operator should be aware of the appropriate security concerns. Security domains should be mapped out against your specific OpenStack deployment topology. The domains and their trust requirements depend upon whether the cloud instance is public, private, or hybrid."
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:37(para)
+msgid "The public security domain is an entirely untrusted area of the cloud infrastructure. It can refer to the Internet as a whole or simply to networks over which you have no authority. Any data that transits this domain with confidentiality or integrity requirements should be protected using compensating controls."
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:38(para)
+msgid "This domain should always be considered <emphasis>untrusted</emphasis>."
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:42(para)
+msgid "Typically used for compute instance-to-instance traffic, the guest security domain handles compute data generated by instances on the cloud but not services that support the operation of the cloud, such as API calls."
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:43(para)
+msgid "Public cloud providers and private cloud providers who do not have stringent controls on instance use or who allow unrestricted internet access to VMs should consider this domain to be <emphasis>untrusted</emphasis>. Private cloud providers may want to consider this network as internal and therefore <emphasis>trusted</emphasis> only if they have controls in place to assert that they trust instances and all their tenants."
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:47(para)
+msgid "The management security domain is where services interact. Sometimes referred to as the \"control plane\", the networks in this domain transport confidential data such as configuration parameters, usernames, and passwords. Command and Control traffic typically resides in this domain, which necessitates strong integrity requirements. Access to this domain should be highly restricted and monitored. At the same time, this domain should still employ all of the security best practices described in this guide."
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:48(para)
+msgid "In most deployments this domain is considered <emphasis>trusted</emphasis>. However, when considering an OpenStack deployment, there are many systems that bridge this domain with others, potentially reducing the level of trust you can place on this domain. See <xref linkend=\"ch005_security-domains-idp61360\"/> for more information."
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:52(para)
+msgid "The data security domain is concerned primarily with information pertaining to the storage services within OpenStack. Much of the data that crosses this network has high integrity and confidentiality requirements and depending on the type of deployment there may also be strong availability requirements."
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:53(para)
+msgid "The trust level of this network is heavily dependent on deployment decisions and as such we do not assign this any default level of trust."
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:57(title)
+msgid "Bridging security domains"
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:58(para)
+msgid "A <emphasis>bridge</emphasis> is a component that exists inside more than one security domain. Any component that bridges security domains with different trust levels or authentication requirements must be carefully configured. These bridges are often the weak points in network architecture. A bridge should always be configured to meet the security requirements of the highest trust level of any of the domains it is bridging. In many cases the security controls for bridges should be a primary concern due to the likelihood of attack."
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:66(para)
+msgid "The diagram above shows a compute node bridging the data and management domains, as such the compute node should be configured to meet the security requirements of the management domain. Similarly the API Endpoint in this diagram is bridging the untrusted public domain and the management domain, and should be configured to protect against attacks from the public domain propagating through to the management domain."
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:74(para)
+msgid "In some cases deployers may want to consider securing a bridge to a higher standard than any of the domains in which it resides. Given the above example of an API endpoint, an adversary could potentially target the API endpoint from the public domain, leveraging it in the hopes of compromising or gaining access to the management domain."
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:75(para)
+msgid "The design of OpenStack is such that separation of security domains is difficult - as core services will usually bridge at least two domains, special consideration must be given when applying security controls to them."
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:78(title)
+msgid "Threat classification, actors and attack vectors"
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:79(para)
+msgid "Most types of cloud deployment, public or private, are exposed to some form of attack. In this chapter we categorize attackers and summarize potential types of attacks in each security domain."
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:81(title)
+msgid "Threat actors"
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:82(para)
+msgid "A threat actor is an abstract way to refer to a class of adversary that you may attempt to defend against. The more capable the actor, the more expensive the security controls that are required for successful attack mitigation and prevention. Security is a tradeoff between cost, usability and defense. In some cases it will not be possible to secure a cloud deployment against all of the threat actors we describe here. Those deploying an OpenStack cloud will have to decide where the balance lies for their deployment / usage."
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:92(para)
+msgid "<emphasis role=\"bold\">Intelligence services</emphasis> — Considered by this guide as the most capable adversary. Intelligence Services and other state actors can bring tremendous resources to bear on a target. They have capabilities beyond that of any other actor. It is very difficult to defend against these actors without incredibly stringent controls in place, both human and technical."
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:102(para)
+msgid "<emphasis role=\"bold\">Serious organized crime</emphasis> — Highly capable and financially driven groups of attackers. Able to fund in-house exploit development and target research. In recent years the rise of organizations such as the Russian Business Network, a massive cyber-criminal enterprise has demonstrated how cyber attacks have become a commodity. Industrial espionage falls within the SOC group."
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:112(para)
+msgid "<emphasis role=\"bold\">Highly capable groups</emphasis> — This refers to 'Hacktivist' type organizations who are not typically commercially funded but can pose a serious threat to service providers and cloud operators."
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:119(para)
+msgid "<emphasis role=\"bold\">Motivated individuals</emphasis> — Acting alone, these attackers come in many guises, such as rogue or malicious employees, disaffected customers, or small-scale industrial espionage."
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:126(para)
+msgid "<emphasis role=\"bold\">Script kiddies</emphasis> — Automated vulnerability scanning/exploitation. Non-targeted attacks. Often only a nuisance, compromise by one of these actors presents a major risk to an organization's reputation."
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:142(title)
+msgid "Public and private cloud considerations"
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:143(para)
+msgid "Private clouds are typically deployed by enterprises or institutions inside their networks and behind their firewalls. Enterprises will have strict policies on what data is allowed to exit their network and may even have different clouds for specific purposes. Users of a private cloud are typically employees of the organization that owns the cloud and are able to be held accountable for their actions. Employees often attend training sessions before accessing the cloud and will likely take part in regular scheduled security awareness training. Public clouds by contrast cannot make any assertions about their users, cloud use-cases or user motivations. This immediately pushes the guest security domain into a completely <emphasis>untrusted</emphasis> state for public cloud providers."
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:144(para)
+msgid "A notable difference in the attack surface of public clouds is that they must provide internet access to their services. Instance connectivity, access to files over the internet and the ability to interact with the cloud controlling fabric such as the API endpoints and dashboard are must-haves for the public cloud."
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:145(para)
+msgid "Privacy concerns for public and private cloud users are typically diametrically opposed. The data generated and stored in private clouds is normally owned by the operator of the cloud, who is able to deploy technologies such as data loss prevention (DLP) protection, file inspection, deep packet inspection and prescriptive firewalling. In contrast, privacy is one of the primary barriers to adoption for the public cloud, as many of these controls do not exist."
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:148(title)
+msgid "Outbound attacks and reputational risk"
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:149(para)
+msgid "Careful consideration should be given to potential outbound abuse from a cloud deployment. Whether public or private, clouds tend to have lots of resource available. An attacker who has established a point of presence within the cloud, either through hacking or entitled access, such as rogue employee, can bring these resources to bear against the internet at large. Clouds with Compute services make for ideal DDoS and brute force engines. The issue is more pressing for public clouds as their users are largely unaccountable, and can quickly spin up numerous disposable instances for outbound attacks. Major damage can be inflicted upon a company's reputation if it becomes known for hosting malicious software or launching attacks on other networks. Methods of prevention include egress security groups, outbound traffic inspection, customer education and awareness, and fraud and abuse mitigation strategies."
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:168(title)
+msgid "Attack types"
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:169(para)
+msgid "The diagram shows the types of attacks that may be expected from the actors described in the previous section. Note that there will always be exceptions to this diagram but in general, this describes the sorts of attack that could be typical for each actor."
+msgstr ""
+
+#: ./doc/security-guide/ch005_security-domains.xml:177(para)
+msgid "The prescriptive defense for each form of attack is beyond the scope of this document. The above diagram can assist you in making an informed decision about which types of threats, and threat actors, should be protected against. For commercial public cloud deployments this might include prevention against serious crime. For those deploying private clouds for government use, more stringent protective mechanisms should be in place, including carefully protected facilities and supply chains. In contrast those standing up basic development or test environments will likely require less restrictive controls (middle of the spectrum)."
+msgstr ""
+
 #: ./doc/security-guide/ch061_compliance-overview.xml:8(title)
 msgid "Compliance overview"
 msgstr ""
@@ -1873,652 +4927,32 @@ msgstr ""
 msgid "Appropriate logging is implemented to monitor for unauthorized use, incident response and forensics. It is highly recommended that selected audit subsystems be Common Criteria certified, which provides non-attestable event records in most countries."
 msgstr ""
 
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:8(title)
-msgid "Certification and compliance statements"
+#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml:8(title)
+msgid "Case studies: instance isolation"
 msgstr ""
 
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:9(para)
-msgid "Compliance and security are not exclusive, and must be addressed together. OpenStack deployments are unlikely to satisfy compliance requirements without security hardening. The listing below provides an OpenStack architect foundational knowledge and guidance to achieve compliance against commercial and government certifications and standards."
+#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml:9(para)
+msgid "In this case study we discuss how Alice and Bob would ensure that their instances are properly isolated. First we consider hypervisor selection, and then techniques for hardening QEMU and applying mandatory access controls."
 msgstr ""
 
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:17(title)
-msgid "Commercial standards"
+#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml:12(para)
+msgid "Alice chooses Xen for the hypervisor in her cloud due to a strong internal knowledge base and a desire to use the Xen security modules (XSM) for fine-grained policy enforcement."
 msgstr ""
 
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:18(para)
-msgid "For commercial deployments of OpenStack, it is recommended that SOC 1/2 combined with ISO 2700 1/2 be considered as a starting point for OpenStack certification activities. The required security activities mandated by these certifications facilitate a foundation of security best practices and common control criteria that can assist in achieving more stringent compliance activities, including government attestations and certifications."
+#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml:13(para)
+msgid "Alice is willing to apply a relatively large amount of resources to software packaging and maintenance. She will use these resources to build a highly customized version of QEMU that has many components removed, thereby reducing the attack surface. She will also ensure that all compiler hardening options are enabled for QEMU. Alice accepts that these decisions will increase long-term maintenance costs."
 msgstr ""
 
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:26(para)
-msgid "After completing these initial certifications, the remaining certifications are more deployment specific. For example, clouds processing credit card transactions will need PCI-DSS, clouds storing health care information require HIPAA, and clouds within the federal government may require FedRAMP/FISMA, and ITAR, certifications."
+#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml:14(para)
+msgid "Alice writes XSM policies (for Xen) and SELinux policies (for Linux domain 0, and device domains) to provide stronger isolation between the instances. Alice also uses the Intel TXT support in Xen to measure the hypervisor launch in the TPM."
 msgstr ""
 
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:34(title)
-msgid "SOC 1 (SSAE 16) / ISAE 3402"
+#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml:18(para)
+msgid "Bob is very concerned about instance isolation since the users in a public cloud represent anyone with a credit card, meaning they are inherently untrusted. Bob has just started hiring the team that will deploy the cloud, so he can tailor his candidate search for specific areas of expertise. With this in mind, Bob chooses a hypervisor based on its technical features, certifications, and community support. KVM has an EAL 4+ common criteria rating, with a labeled security protection profile (LSPP) to provide added assurance for instance isolation. This, combined with the strong support for KVM within the OpenStack community drives Bob's decision to use KVM."
 msgstr ""
 
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:35(para)
-msgid "Service Organization Controls (SOC) criteria are defined by the <link href=\"http://www.aicpa.org/\">American Institute of Certified Public Accountants</link> (AICPA). SOC controls assess relevant financial statements and assertions of a service provider, such as compliance with the Sarbanes-Oxley Act. SOC 1 is a replacement for Statement on Auditing Standards No. 70 (SAS 70) Type II report. These controls commonly include physical data centers in scope."
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:44(para)
-msgid "There are two types of SOC 1 reports:"
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:47(para) ./doc/security-guide/ch064_certifications-compliance-statements.xml:84(para)
-msgid "Type 1 – report on the fairness of the presentation of management's description of the service organization's system and the suitability of the design of the controls to achieve the related control objectives included in the description as of a specified date."
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:54(para)
-msgid "Type 2 – report on the fairness of the presentation of management's description of the service organization's system and the suitability of the design and operating effectiveness of the controls to achieve the related control objectives included in the description throughout a specified period"
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:62(para)
-msgid "For more details see the <link href=\"http://www.aicpa.org/InterestAreas/FRC/AssuranceAdvisoryServices/Pages/AICPASOC1Report.aspx\">AICPA Report on Controls at a Service Organization Relevant to User Entities’ Internal Control over Financial Reporting</link>."
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:70(title)
-msgid "SOC 2"
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:71(para)
-msgid "Service Organization Controls (SOC) 2 is a self attestation of controls that affect the security, availability, and processing integrity of the systems a service organization uses to process users' data and the confidentiality and privacy of information processed by these system. Examples of users are those responsible for governance of the service organization; customers of the service organization; regulators; business partners; suppliers and others who have an understanding of the service organization and its controls."
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:81(para)
-msgid "There are two types of SOC 2 reports:"
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:91(para)
-msgid "Type 2 – report on the fairness of the presentation of management's description of the service organization's system and the suitability of the design and operating effectiveness of the controls to achieve the related control objectives included in the description throughout a specified period."
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:99(para)
-msgid "For more details see the <link href=\"http://www.aicpa.org/InterestAreas/FRC/AssuranceAdvisoryServices/Pages/AICPASOC2Report.aspx\">AICPA Report on Controls at a Service Organization Relevant to Security, Availability, Processing Integrity, Confidentiality or Privacy</link>."
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:108(title)
-msgid "SOC 3"
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:109(para)
-msgid "Service Organization Controls (SOC) 3 is a trust services report for service organizations. These reports are designed to meet the needs of users who want assurance on the controls at a service organization related to security, availability, processing integrity, confidentiality, or privacy but do not have the need for or the knowledge necessary to make effective use of a SOC 2 Report. These reports are prepared using the AICPA/Canadian Institute of Chartered Accountants (CICA) Trust Services Principles, Criteria, and Illustrations for Security, Availability, Processing Integrity, Confidentiality, and Privacy. Because they are general use reports, SOC 3 Reports can be freely distributed or posted on a website as a seal."
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:121(para)
-msgid "For more details see the <link href=\"http://www.aicpa.org/InterestAreas/FRC/AssuranceAdvisoryServices/Pages/AICPASOC3Report.aspx\">AICPA Trust Services Report for Service Organizations</link>."
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:128(title)
-msgid "ISO 27001/2"
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:129(para)
-msgid "The ISO/IEC 27001/2 standards replace BS7799-2, and are specifications for an Information Security Management System (ISMS). An ISMS is a comprehensive set of policies and processes that an organization creates and maintains to manage risk to information assets. These risks are based upon the confidentiality, integrity, and availability (CIA) of user information. The CIA security triad has been used as a foundation for much of the chapters in this book."
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:137(para)
-msgid "For more details see <link href=\"http://www.27000.org/iso-27001.htm\">ISO 27001</link>."
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:143(title)
-msgid "HIPAA / HITECH"
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:144(para)
-msgid "The Health Insurance Portability and Accountability Act (HIPAA) is a United States congressional act that governs the collection, storage, use and destruction of patient health records. The act states that Protected Health Information (PHI) must be rendered \"unusable, unreadable, or indecipherable\" to unauthorized persons and that encryption for data 'at-rest' and 'inflight' should be addressed."
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:151(para)
-msgid "HIPAA is not a certification, rather a guide for protecting healthcare data. Similar to the PCI-DSS, the most important issues with both PCI and HIPPA is that a breach of credit card information, and health data, does not occur. In the instance of a breach the cloud provider will be scrutinized for compliance with PCI and HIPPA controls. If proven compliant, the provider can be expected to immediately implement remedial controls, breach notification responsibilities, and significant expenditure on additional compliance activities. If not compliant, the cloud provider can expect on-site audit teams, fines, potential loss of merchant ID (PCI), and massive reputation impact."
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:163(para)
-msgid "Users or organizations that possess PHI must support HIPAA requirements and are HIPAA covered entities. If an entity intends to use a service, or in this case, an OpenStack cloud that might use, store or have access to that PHI, then a Business Associate Agreement must be signed. The BAA is a contract between the HIPAA covered entity and the OpenStack service provider that requires the provider to handle that PHI in accordance with HIPAA requirements. If the service provider does not handle the PHI, such as with security controls and hardening, then they are subject to HIPAA fines and penalties."
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:174(para)
-msgid "OpenStack architects interpret and respond to HIPAA statements, with data encryption remaining a core practice. Currently this would require any protected health information contained within an OpenStack deployment to be encrypted with industry standard encryption algorithms. Potential future OpenStack projects such as object encryption will facilitate HIPAA guidelines for compliance with the act."
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:181(para)
-msgid "For more details see the <link href=\"https://www.cms.gov/Regulations-and-Guidance/HIPAA-Administrative-Simplification/HIPAAGenInfo/downloads/HIPAALaw.pdf\">Health Insurance Portability And Accountability Act</link>."
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:187(title)
-msgid "PCI-DSS"
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:188(para)
-msgid "The Payment Card Industry Data Security Standard (PCI DSS) is defined by the Payment Card Industry Standards Council, and created to increase controls around card holder data to reduce credit card fraud. Annual compliance validation is assessed by an external Qualified Security Assessor (QSA) who creates a Report on Compliance (ROC), or by a Self-Assessment Questionnaire (SAQ) dependent on volume of card-holder transactions."
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:196(para)
-msgid "OpenStack deployments which stores, processes, or transmits payment card details are in scope for the PCI-DSS. All OpenStack components that are not properly segmented from systems or networks that handle payment data fall under the guidelines of the PCI-DSS. Segmentation in the context of PCI-DSS does not support multi-tenancy, but rather physical separation (host/network)."
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:203(para)
-msgid "For more details see <link href=\"https://www.pcisecuritystandards.org/security_standards/\">PCI security standards</link>."
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:209(title)
-msgid "Government standards"
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:212(title)
-msgid "FedRAMP"
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:213(para)
-msgid "\"The <link href=\"http://www.fedramp.gov\">Federal Risk and Authorization Management Program</link> (FedRAMP) is a government-wide program that provides a standardized approach to security assessment, authorization, and continuous monitoring for cloud products and services\". NIST 800-53 is the basis for both FISMA and FedRAMP which mandates security controls specifically selected to provide protection in cloud environments. FedRAMP can be extremely intensive from specificity around security controls, and the volume of documentation required to meet government standards."
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:223(para)
-msgid "For more details see <link href=\"http://www.gsa.gov/portal/category/102371\">http://www.gsa.gov/portal/category/102371</link>."
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:229(title)
-msgid "ITAR"
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:230(para)
-msgid "The International Traffic in Arms Regulations (ITAR) is a set of United States government regulations that control the export and import of defense-related articles and services on the United States Munitions List (USML) and related technical data. ITAR is often approached by cloud providers as an \"operational alignment\" rather than a formal certification. This typically involves implementing a segregated cloud environment following practices based on the NIST 800-53 framework, as per FISMA requirements, complemented with additional controls restricting access to \"U.S. Persons\" only and background screening."
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:241(para)
-msgid "For more details see <link href=\"http://pmddtc.state.gov/regulations_laws/itar_official.html\">http://pmddtc.state.gov/regulations_laws/itar_official.html</link>."
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:247(title)
-msgid "FISMA"
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:248(para)
-msgid "The Federal Information Security Management Act requires that government agencies create a comprehensive plan to implement numerous government security standards, and was enacted within the E-Government Act of 2002. FISMA outlines a process, which utilizing multiple NIST publications, prepares an information system to store and process government data."
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:255(para)
-msgid "This process is broken apart into three primary categories:"
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:259(para)
-msgid "<emphasis role=\"bold\">System categorization:</emphasis> The information system will receive a security category as defined in Federal Information Processing Standards Publication 199 (FIPS 199). These categories reflect the potential impact of system compromise."
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:267(para)
-msgid "<emphasis role=\"bold\">Control selection:</emphasis>Based upon system security category as defined in FIPS 199, an organization utilizes FIPS 200 to identify specific security control requirements for the information system. For example, if a system is categorized as “moderate” a requirement may be introduced to mandate “secure passwords.”"
-msgstr ""
-
-#: ./doc/security-guide/ch064_certifications-compliance-statements.xml:276(para)
-msgid "<emphasis role=\"bold\">Control tailoring:</emphasis> Once system security controls are identified, an OpenStack architect will utilize NIST 800-53 to extract tailored control selection. For example, specification of what constitutes a “secure password.”"
-msgstr ""
-
-#: ./doc/security-guide/ch039_case-studies-messaging.xml:8(title)
-msgid "Case studies: messaging"
-msgstr ""
-
-#: ./doc/security-guide/ch039_case-studies-messaging.xml:9(para)
-msgid "The message queue is a critical piece of infrastructure that supports a number of OpenStack services but is most strongly associated with the Compute service. Due to the nature of the message queue service, Alice and Bob have similar security concerns. One of the larger concerns that remains is that many systems have access to this queue and there is no way for a consumer of the queue messages to verify which host or service placed the messages on the queue. An attacker who is able to successfully place messages on the queue is able to create and delete VM instances, attach the block storage of any tenant and a myriad of other malicious actions. There are a number of solutions on the horizon to fix this, with several proposals for message signing and encryption making their way through the OpenStack development process."
-msgstr ""
-
-#: ./doc/security-guide/ch039_case-studies-messaging.xml:12(para)
-msgid "In this case Alice's controls mimic those Bob has deployed for the public cloud."
-msgstr ""
-
-#: ./doc/security-guide/ch039_case-studies-messaging.xml:16(para)
-msgid "Bob assumes that at some point infrastructure or networks underpinning the Compute service may become compromised. Due to this, he recognizes the importance of locking down access to the message queue. To do this Bob deploys his RabbitMQ servers with SSL and X.509 client auth for access control. This in turn limits the capabilities of an attacker who has compromised a system that does not have queue access."
-msgstr ""
-
-#: ./doc/security-guide/ch039_case-studies-messaging.xml:17(para)
-msgid "Additionally, Bob adds strong network ACL rulesets to enforce which endpoints can communicate with the message servers. This second control provides some additional assurance should the other protections fail."
-msgstr ""
-
-#: ./doc/security-guide/ch066_case-studies-compliance.xml:8(title)
-msgid "Case studies: compliance"
-msgstr ""
-
-#: ./doc/security-guide/ch066_case-studies-compliance.xml:9(para)
-msgid "In this case study we discuss how Alice and Bob would address common compliance requirements. The preceding chapter refers to a wide variety of compliance certifications and standards. Alice will address compliance in a private cloud, while Bob will be focused on compliance for a public cloud."
-msgstr ""
-
-#: ./doc/security-guide/ch066_case-studies-compliance.xml:12(para)
-msgid "Alice is building an OpenStack private cloud for the United States government, specifically to provide elastic compute environments for signal processing. Alice has researched government compliance requirements, and has identified that her private cloud will be required to certify against FISMA and follow the FedRAMP accreditation process, which is required for all federal agencies, departments and contractors to become a Certified Cloud Provider (CCP). In this particular scenario for signal processing, the FISMA controls required will most likely be FISMA High, which indicates possible \"severe or catastrophic adverse effects\" should the information system become compromised. In addition to FISMA Moderate controls Alice must ensure her private cloud is FedRAMP certified, as this is a requirement for all agencies that currently utilize, or host federal information within a cloud environment."
-msgstr ""
-
-#: ./doc/security-guide/ch066_case-studies-compliance.xml:13(para)
-msgid "To meet these strict government regulations Alice undertakes a number of activities. Scoping of requirements is particularly important due to the volume of controls that must be implemented, which will be defined in NIST Publication 800-53."
-msgstr ""
-
-#: ./doc/security-guide/ch066_case-studies-compliance.xml:14(para)
-msgid "All technology within her private cloud must be FIPS certified technology, as mandated within NIST 800-53 and FedRAMP. As the U.S. Department of Defense is involved, Security Technical Implementation Guides (STIGs) will come into play, which are the configuration standards for DOD IA and IA-enabled devices / systems. Alice notices a number of complications here as there is no STIG for OpenStack, so she must address several underlying requirements for each OpenStack service; for example, the networking SRG and Application SRG will both be applicable (<link href=\"http://iase.disa.mil/srgs/index.html\">list of SRGs</link>). Other critical controls include ensuring that all identities in the cloud use PKI, that SELinux is enabled, that encryption exists for all wire-level communications, and that continuous monitoring is in place and clearly documented. Alice is not concerned with object encryption, as this will be the tenants responsibility rather than the provider."
-msgstr ""
-
-#: ./doc/security-guide/ch066_case-studies-compliance.xml:15(para)
-msgid "If Alice has adequately scoped and executed these compliance activities, she may begin the process to become FedRAMP compliant by hiring an approved third-party auditor. Typically this process takes up to 6 months, after which she will receive an Authority to Operate and can offer OpenStack cloud services to the government."
-msgstr ""
-
-#: ./doc/security-guide/ch066_case-studies-compliance.xml:19(para)
-msgid "Bob is tasked with compliance for a new OpenStack public cloud deployment, that is focused on providing cloud services to both small developers and startups, as well as large enterprises. Bob recognizes that individual developers are not necessarily concerned with compliance certifications, but to larger enterprises certifications are critical. Specifically Bob desires to achieve SOC 1, SOC 2 Security, as well as ISO 27001/2 as quickly as possible. Bob references the Cloud Security Alliance Cloud Control Matrix (CCM) to assist in identifying common controls across these three certifications (such as periodic access reviews, auditable logging and monitoring services, risk assessment activities, security reviews, etc). Bob then engages an experienced audit team to conduct a gap analysis on the public cloud deployment, reviews the results and fills any gaps identified. Bob works with other team members to ensure that these security controls and activities are regularly conducted for a typical audit period (~6-12 months)."
-msgstr ""
-
-#: ./doc/security-guide/ch066_case-studies-compliance.xml:36(para)
-msgid "At the end of the audit period Bob has arranged for an external audit team to review in-scope security controls at randomly sampled points of time over a 6 month period. The audit team provides Bob with an official report for SOC 1 and SOC 2, and separately for ISO 27001/2. As Bob has been diligent in ensuring security controls are in place for his OpenStack public cloud, there are no additional gaps exposed on the report. Bob can now provide these official reports to his customers under NDA, and advertise that he is SOC 1, SOC 2 and ISO 27001/2 compliant on his website."
-msgstr ""
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml:8(title)
-msgid "API endpoint configuration recommendations"
-msgstr ""
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml:9(para)
-msgid "This chapter provides recommendations security enhancements for both public and private-facing API endpoints."
-msgstr ""
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml:13(title)
-msgid "Internal API communications"
-msgstr ""
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml:14(para)
-msgid "OpenStack provides both public facing and private API endpoints. By default, OpenStack components use the publicly defined endpoints. The recommendation is to configure these components to use the API endpoint within the proper security domain."
-msgstr ""
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml:20(para)
-msgid "Services select their respective API endpoints based on the OpenStack service catalog. These services might not obey the listed public or internal API end point values. This can lead to internal management traffic being routed to external API endpoints."
-msgstr ""
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml:27(title)
-msgid "Configure internal URLs in Identity service catalog"
-msgstr ""
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml:28(para)
-msgid "The Identity service catalog should be aware of your internal URLs. While this feature is not utilized by default, it may be leveraged through configuration. Additionally, it should be forward-compatible with expectant changes once this behavior becomes the default."
-msgstr ""
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml:35(para)
-msgid "To register an internal URL for an endpoint:"
-msgstr ""
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml:44(title)
-msgid "Configure applications for internal URLs"
-msgstr ""
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml:45(para)
-msgid "You can force some services to use specific API endpoints. Therefore, it is recommended that each OpenStack service communicating to the API of another service must be explicitly configured to access the proper internal API endpoint."
-msgstr ""
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml:51(para)
-msgid "Each project may present an inconsistent way of defining target API endpoints. Future releases of OpenStack seek to resolve these inconsistencies through consistent use of the Identity Service catalog."
-msgstr ""
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml:57(title)
-msgid "Configuration example #1: nova"
-msgstr ""
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml:67(title)
-msgid "Configuration example #2: cinder"
-msgstr ""
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml:73(title)
-msgid "Paste and middleware"
-msgstr ""
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml:74(para)
-msgid "Most API endpoints and other HTTP services in OpenStack use the Python Paste Deploy library. From a securtiy perspective, this library enables manipulation of the request filter pipeline through the application's configuration. Each element in this chain is referred to as <emphasis>middleware</emphasis>. Changing the order of filters in the pipeline or adding additional middleware might have unpredictable security impact."
-msgstr ""
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml:83(para)
-msgid "Commonly, implementers add middleware to extend OpenStack's base functionality. We recommend implementers make careful consideration of the potential exposure introduced by the addition of non-standard software components to their HTTP request pipeline."
-msgstr ""
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml:89(para)
-msgid "For more information about Paste Deploy, see <link href=\"http://pythonpaste.org/deploy/\">http://pythonpaste.org/deploy/</link>."
-msgstr ""
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml:94(title)
-msgid "API endpoint process isolation and policy"
-msgstr ""
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml:95(para)
-msgid "As much as possible, you should isolate API endpoint processes, especially those that reside within the public security domain should be isolated as much as possible. Where deployments allow, API endpoints should be deployed on separate hosts for increased isolation."
-msgstr ""
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml:102(title) ./doc/security-guide/ch038_transport-security.xml:133(title)
-msgid "Namespaces"
-msgstr ""
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml:103(para)
-msgid "Many operating systems now provide compartmentalization support. Linux supports namespaces to assign processes into independent domains. Other parts of this guide cover system compartmentalization in more detail."
-msgstr ""
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml:110(title) ./doc/security-guide/ch038_transport-security.xml:144(title)
-msgid "Network policy"
-msgstr ""
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml:111(para)
-msgid "Because API endpoints typically bridge multiple security domains, you must pay particular attention to the compartmentalization of the API processes. See <xref linkend=\"ch005_security-domains-idp61360\"/> for additional information in this area."
-msgstr ""
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml:117(para)
-msgid "With careful modeling, you can use network ACLs and IDS technologies to enforce explicit point to point communication between network services. As critical cross domain service, this type of explicit enforcement works well for OpenStack's message queue service."
-msgstr ""
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml:123(para)
-msgid "To enforce policies, you can configure services, host-based firewalls (such as iptables), local policy (SELinux or AppArmor), and optionally global network policy."
-msgstr ""
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml:129(title) ./doc/security-guide/ch038_transport-security.xml:149(title) ./doc/security-guide/ch052_devices.xml:238(title)
-msgid "Mandatory access controls"
-msgstr ""
-
-#: ./doc/security-guide/ch021_paste-and-middleware.xml:130(para)
-msgid "You should isolate API endpoint processes from each other and other processes on a machine. The configuration for those processes should be restricted to those processes not only by Discretionary Access Controls, but through Mandatory Access Controls. The goal of these enhanced access control is to aid in the containment and escalation of API endpoint security breaches. With mandatory access controls, such breaches severely limit access to resources and provide earlier alerting on such events."
-msgstr ""
-
-#: ./doc/security-guide/ch041_database-backend-considerations.xml:7(title)
-msgid "Database back-end considerations"
-msgstr ""
-
-#: ./doc/security-guide/ch041_database-backend-considerations.xml:8(para)
-msgid "The choice of database server is an important consideration in the security of an OpenStack deployment. While security considerations are not the only basis on which a database server must be chosen, security considerations are the only ones within the scope of this book. In practice, OpenStack only supports two database types: PostgreSQL and MySQL."
-msgstr ""
-
-#: ./doc/security-guide/ch041_database-backend-considerations.xml:9(para)
-msgid "PostgreSQL has a number of desirable security features such as Kerberos authentication, object-level security, and encryption support. The PostgreSQL community has done well to provide solid guidance, documentation, and tooling to promote positive security practices."
-msgstr ""
-
-#: ./doc/security-guide/ch041_database-backend-considerations.xml:10(para)
-msgid "MySQL has a large community, widespread adoption, and provides high availability options. MySQL also has the ability to provide enhanced client authentication by way of plug-in authentication mechanisms. Forked distributions in the MySQL community provide many options for consideration. It is important to choose a specific implementation of MySQL based on a thorough evaluation of the security posture and the level of support provided for the given distribution."
-msgstr ""
-
-#: ./doc/security-guide/ch041_database-backend-considerations.xml:12(title)
-msgid "Security references for database back-ends"
-msgstr ""
-
-#: ./doc/security-guide/ch041_database-backend-considerations.xml:13(para)
-msgid "Those deploying MySQL or PostgreSQL are advised to refer to existing security guidance. Some references are listed below:"
-msgstr ""
-
-#: ./doc/security-guide/ch041_database-backend-considerations.xml:14(para)
-msgid "MySQL:"
-msgstr ""
-
-#: ./doc/security-guide/ch041_database-backend-considerations.xml:16(link)
-msgid "OWASP MySQL Hardening"
-msgstr ""
-
-#: ./doc/security-guide/ch041_database-backend-considerations.xml:19(link)
-msgid "MySQL Pluggable Authentication"
-msgstr ""
-
-#: ./doc/security-guide/ch041_database-backend-considerations.xml:22(link)
-msgid "Security in MySQL"
-msgstr ""
-
-#: ./doc/security-guide/ch041_database-backend-considerations.xml:25(para)
-msgid "PostgreSQL:"
-msgstr ""
-
-#: ./doc/security-guide/ch041_database-backend-considerations.xml:27(link)
-msgid "OWASP PostgreSQL Hardening"
-msgstr ""
-
-#: ./doc/security-guide/ch041_database-backend-considerations.xml:30(link)
-msgid "Total security in a PostgreSQL database"
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:8(title)
-msgid "Management interfaces"
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:9(para)
-msgid "It is necessary for administrators to perform command and control over the cloud for various operational functions. It is important these command and control facilities are understood and secured."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:13(para)
-msgid "OpenStack provides several management interfaces for operators and tenants:"
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:15(para)
-msgid "OpenStack dashboard (horizon)"
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:18(para) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:95(title)
-msgid "OpenStack API"
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:21(para) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:128(title)
-msgid "Secure shell (SSH)"
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:24(para)
-msgid "OpenStack management utilities such as <systemitem class=\"service\">nova-manage</systemitem> and <systemitem class=\"service\">glance-manage</systemitem>"
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:29(para)
-msgid "Out-of-band management interfaces, such as IPMI"
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:34(para)
-msgid "The OpenStack dashboard (horizon) provides administrators and tenants with a web-based graphical interface to provision and access cloud-based resources. The dashboard communicates with the back-end services through calls to the OpenStack API."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:41(title) ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:103(title) ./doc/security-guide/ch026_compute.xml:22(title) ./doc/security-guide/ch026_compute.xml:67(title)
-msgid "Capabilities"
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:43(para)
-msgid "As a cloud administrator, the dashboard provides an overall view of the size and state of your cloud. You can create users and tenants/projects, assign users to tenant/projects and set limits on the resources available for them."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:46(para)
-msgid "The dashboard provides tenant-users a self-service portal to provision their own resources within the limits set by administrators."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:49(para)
-msgid "The dashboard provides GUI support for routers and load-balancers. For example, the dashboard now implements all of the main Networking features."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:52(para)
-msgid "It is an extensible <glossterm>Django</glossterm> web application that allows easy plug-in of third-party products and services, such as billing, monitoring, and additional management tools."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:55(para)
-msgid "The dashboard can also be branded for service providers and other commercial vendors."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:62(para)
-msgid "The dashboard requires cookies and JavaScript to be enabled in the web browser."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:65(para)
-msgid "The web server that hosts dashboard should be configured for SSL to ensure data is encrypted."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:68(para)
-msgid "Both the horizon web service and the OpenStack API it uses to communicate with the back-end are susceptible to web attack vectors such as denial of service and must be monitored."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:71(para)
-msgid "It is now possible (though there are numerous deployment/security implications) to upload an image file directly from a user’s hard disk to OpenStack Image Service through the dashboard. For multi-gigabyte images it is still strongly recommended that the upload be done using the <placeholder-1/> CLI."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:81(para)
-msgid "Create and manage security groups through dashboard. The security groups allows L3-L4 packet filtering for security policies to protect virtual machines."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:91(citetitle)
-msgid "Grizzly Release Notes"
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:96(para)
-msgid "The OpenStack API is a RESTful web service endpoint to access, provision and automate cloud-based resources. Operators and users typically access the API through command-line utilities (for example, <placeholder-1/> or <placeholder-2/>), language-specific libraries, or third-party tools."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:105(para)
-msgid "To the cloud administrator, the API provides an overall view of the size and state of the cloud deployment and allows the creation of users, tenants/projects, assigning users to tenants/projects, and specifying resource quotas on a per tenant/project basis."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:112(para)
-msgid "The API provides a tenant interface for provisioning, managing, and accessing their resources."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:119(para)
-msgid "The API service should be configured for SSL to ensure data is encrypted."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:122(para)
-msgid "As a web service, OpenStack API is susceptible to familiar web site attack vectors such as denial of service attacks."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:129(para)
-msgid "It has become industry practice to use secure shell (SSH) access for the management of Linux and Unix systems. SSH uses secure cryptographic primitives for communication. With the scope and importance of SSH in typical OpenStack deployments, it is important to understand best practices for deploying SSH."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:131(title)
-msgid "Host key fingerprints"
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:132(para)
-msgid "Often overlooked is the need for key management for SSH hosts. As most or all hosts in an OpenStack deployment will provide an SSH service, it is important to have confidence in connections to these hosts. It cannot be understated that failing to provide a reasonably secure and accessible method to verify SSH host key fingerprints is ripe for abuse and exploitation."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:133(para)
-msgid "All SSH daemons have private host keys and, upon connection, offer a host key fingerprint. This host key fingerprint is the hash of an unsigned public key. It is important these host key fingerprints are known in advance of making SSH connections to those hosts. Verification of host key fingerprints is instrumental in detecting man-in-the-middle attacks."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:134(para)
-msgid "Typically, when an SSH daemon is installed, host keys will be generated. It is necessary that the hosts have sufficient entropy during host key generation. Insufficient entropy during host key generation can result in the possibility to eavesdrop on SSH sessions."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:135(para)
-msgid "Once the SSH host key is generated, the host key fingerprint should be stored in a secure and queriable location. One particularly convenient solution is DNS using SSHFP resource records as defined in RFC-4255. For this to be secure, it is necessary that DNSSEC be deployed."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:139(title)
-msgid "Management utilities"
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:140(para)
-msgid "The OpenStack Management Utilities are open-source Python command-line clients that make API calls. There is a client for each OpenStack service (for example, <systemitem class=\"service\">nova</systemitem>, <systemitem class=\"service\">glance</systemitem>). In addition to the standard CLI client, most of the services have a management command-line utility which makes direct calls to the database. These dedicated management utilities are slowly being deprecated."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:152(para)
-msgid "The dedicated management utilities (*-manage) in some cases use the direct database connection."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:155(para)
-msgid "Ensure that the .rc file which has your credential information is secured."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:161(para)
-msgid "<citetitle>OpenStack End User Guide</citetitle> section <link href=\"http://docs.openstack.org/user-guide/content/section_cli_overview.html\">command-line clients overview</link>"
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:162(para)
-msgid "<citetitle>OpenStack End User Guide</citetitle> section <link href=\"http://docs.openstack.org/user-guide/content/cli_openrc.html\">Download and source the OpenStack RC file</link>"
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:166(title)
-msgid "Out-of-band management interface"
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:167(para)
-msgid "OpenStack management relies on out-of-band management interfaces such as the IPMI protocol to access into nodes running OpenStack components. IPMI is a very popular specification to remotely manage, diagnose, and reboot servers whether the operating system is running or the system has crashed."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:176(para)
-msgid "Use strong passwords and safeguard them, or use client-side SSL authentication."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:179(para)
-msgid "Ensure that the network interfaces are on their own private(management or a separate) network. Segregate management domains with firewalls or other network gear."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:182(para)
-msgid "If you use a web interface to interact with the <glossterm>BMC</glossterm>/IPMI, always use the SSL interface, such as https or port 443. This SSL interface should <emphasis role=\"bold\">NOT</emphasis> use self-signed certificates, as is often default, but should have trusted certificates using the correctly defined fully qualified domain names (FQDNs)."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:191(para)
-msgid "Monitor the traffic on the management network. The anomalies might be easier to track than on the busier compute nodes."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:196(para)
-msgid "Out of band management interfaces also often include graphical machine console access. It is often possible, although not necessarily default, that these interfaces are encrypted. Consult with your system software documentation for encrypting these interfaces."
-msgstr ""
-
-#: ./doc/security-guide/ch014_best-practices-for-operator-mode-access.xml:200(link)
-msgid "Hacking servers that are turned off"
-msgstr ""
-
-#: ./doc/security-guide/ch028_case-studies-identity-management.xml:8(title)
-msgid "Case studies: Identity management"
-msgstr ""
-
-#: ./doc/security-guide/ch028_case-studies-identity-management.xml:9(para)
-msgid "In this case study we discuss how Alice and Bob would address configuration of OpenStack core services. These include the Identity service, dashboard, and Compute services. Alice will be concerned with integration into the existing government directory services, while Bob will need to provide access to the public."
-msgstr ""
-
-#: ./doc/security-guide/ch028_case-studies-identity-management.xml:19(para)
-msgid "Alice's enterprise has a well-established directory service with two-factor authentication for all users. She configures the Identity service to support an external authentication service supporting authentication with government-issued access cards. She also uses an external LDAP server to provide role information for the users that is integrated with the access control policy. Due to FedRAMP compliance requirements, Alice implements two-factor authentication on the management network for all administrator access."
-msgstr ""
-
-#: ./doc/security-guide/ch028_case-studies-identity-management.xml:30(para)
-msgid "Alice also deploys the dashboard to manage many aspects of the cloud. She deploys the dashboard with HSTS to ensure that only HTTPS is used. The dashboard resides within an internal subdomain of the private network domain name system."
-msgstr ""
-
-#: ./doc/security-guide/ch028_case-studies-identity-management.xml:36(para)
-msgid "Alice decides to use SPICE instead of VNC for the virtual console. She wants to take advantage of the emerging capabilities in SPICE."
-msgstr ""
-
-#: ./doc/security-guide/ch028_case-studies-identity-management.xml:44(para)
-msgid "Because Bob must support authentication for the general public, he decides to use use user name and password authentication. He has concerns about brute force attacks attempting to crack user passwords, so he also uses an external authentication extension that throttles the number of failed login attempts. Bob's management network is separate from the other networks within his cloud, but can be reached from his corporate network through ssh. As recommended earlier, Bob requires administrators to use two-factor authentication on the Management network to reduce the risk from compromised administrator passwords."
-msgstr ""
-
-#: ./doc/security-guide/ch028_case-studies-identity-management.xml:56(para)
-msgid "Bob also deploys the dashboard to manage many aspects of the cloud. He deploys the dashboard with HSTS to ensure that only HTTPS is used. He has ensured that the dashboard is deployed on a second-level domain due to the limitations of the same-origin policy. He also disables <option>HORIZON_IMAGES_ALLOW_UPLOAD</option> to prevent resource exhaustion."
-msgstr ""
-
-#: ./doc/security-guide/ch028_case-studies-identity-management.xml:63(para)
-msgid "Bob decides to use VNC for his virtual console for its maturity and security features."
-msgstr ""
-
-#: ./doc/security-guide/ch037_risks.xml:8(title)
-msgid "Message queuing architecture"
-msgstr ""
-
-#: ./doc/security-guide/ch037_risks.xml:9(para)
-msgid "Message queuing services facilitate inter-process communication in OpenStack. OpenStack supports these message queuing service back ends:"
-msgstr ""
-
-#: ./doc/security-guide/ch037_risks.xml:14(para)
-msgid "RabbitMQ"
-msgstr ""
-
-#: ./doc/security-guide/ch037_risks.xml:17(para)
-msgid "Qpid"
-msgstr ""
-
-#: ./doc/security-guide/ch037_risks.xml:20(para)
-msgid "ZeroMQ or 0MQ"
-msgstr ""
-
-#: ./doc/security-guide/ch037_risks.xml:23(para)
-msgid "Both RabbitMQ and Qpid are Advanced Message Queuing Protocol (AMQP) frameworks, which provide message queues for peer-to-peer communication. Queue implementations are typically deployed as a centralized or decentralized pool of queue servers. ZeroMQ provides direct peer-to-peer communication through TCP sockets."
-msgstr ""
-
-#: ./doc/security-guide/ch037_risks.xml:29(para)
-msgid "Message queues effectively facilitate command and control functions across OpenStack deployments. Once access to the queue is permitted no further authorization checks are performed. Services accessible through the queue do validate the contexts and tokens within the actual message payload. However, you must note the expiration date of the token because tokens are potentially re-playable and can authorize other services in the infrastructure."
-msgstr ""
-
-#: ./doc/security-guide/ch037_risks.xml:37(para)
-msgid "OpenStack does not support message-level confidence, such as message signing. Consequently, you must secure and authenticate the message transport itself. For high-availability (HA) configurations, you must perform queue-to-queue authentication and encryption."
-msgstr ""
-
-#: ./doc/security-guide/ch037_risks.xml:42(para)
-msgid "With ZeroMQ messaging, IPC sockets are used on individual machines. Because these sockets are vulnerable to attack, ensure that the cloud operator has secured them."
-msgstr ""
-
-#: ./doc/security-guide/ch026_compute.xml:8(title) ./doc/security-guide/ch004_book-introduction.xml:122(title)
-msgid "Compute"
+#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml:19(para)
+msgid "Bob weighs the added cost of repackaging QEMU and decides that he cannot commit those resources to the project. Fortunately, his Linux distribution has already enabled the compiler hardening options. So he decides to use this QEMU package. Finally, Bob leverages sVirt to manage the SELinux polices associated with the virtualization stack."
 msgstr ""
 
 #: ./doc/security-guide/ch026_compute.xml:9(para)
@@ -2610,450 +5044,726 @@ msgstr ""
 msgid "SPICE support in RDO Grizzly"
 msgstr ""
 
+#: ./doc/security-guide/ch046_data-residency.xml:8(title)
+msgid "Data privacy concerns"
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:9(para)
+msgid "OpenStack is designed to support multitenancy and those tenants will most probably have different data requirements. As a cloud builder and operator you need to ensure your OpenStack environment can address various data privacy concerns and regulations. In this chapter we will address the following topics around Data Privacy as it pertains to OpenStack implementations:"
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:19(para) ./doc/security-guide/ch046_data-residency.xml:26(title)
+msgid "Data residency"
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:22(para) ./doc/security-guide/ch046_data-residency.xml:77(title)
+msgid "Data disposal"
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:27(para)
+msgid "The privacy and isolation of data has consistently been cited as the primary barrier to cloud adoption over the past few years. Concerns over who owns data in the cloud and whether the cloud operator can be ultimately trusted as a custodian of this data have been significant issues in the past."
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:28(para)
+msgid "Numerous OpenStack services maintain data and metadata belonging to tenants or reference tenant information."
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:29(para)
+msgid "Tenant data stored in an OpenStack cloud may include the following items:"
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:34(para)
+msgid "Compute instance ephemeral filesystem storage"
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:37(para)
+msgid "Compute instance memory"
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:40(para) ./doc/security-guide/ch046_data-residency.xml:105(para)
+msgid "Block Storage volume data"
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:43(para)
+msgid "Public keys for Compute Access"
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:46(para)
+msgid "Virtual Machine Images in the Image Service"
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:49(para)
+msgid "Machine snapshots"
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:52(para)
+msgid "Data passed to OpenStack Compute's configuration-drive extension"
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:55(para)
+msgid "Metadata stored by an OpenStack cloud includes the following non-exhaustive items:"
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:57(para)
+msgid "Organization name"
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:60(para)
+msgid "User's \"Real Name\""
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:63(para)
+msgid "Number or size of running instances, buckets, objects, volumes, and other quota-related items"
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:66(para)
+msgid "Number of hours running instances or storing data"
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:69(para)
+msgid "IP addresses of users"
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:72(para)
+msgid "Internally generated private keys for compute image bundling"
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:78(para)
+msgid "OpenStack operators should strive to provide a certain level of tenant data disposal assurance. Best practices suggest that the operator sanitize cloud system media (digital and non-digital) prior to disposal, release out of organization control or release for reuse. Sanitization methods should implement an appropriate level of strength and integrity given the specific security domain and sensitivity of the information."
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:80(para)
+msgid "\"Sanitization is the process used to remove information from system media such that there is reasonable assurance that the information cannot be retrieved or reconstructed. Sanitization techniques, including clearing, purging, and destroying media information, prevent the disclosure of organizational information to unauthorized individuals when such media is reused or released for disposal.\" [NIST Special Publication 800-53 Revision 3]"
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:82(para)
+msgid "General data disposal and sanitization guidelines as adopted from NIST recommended security controls. Cloud operators should:"
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:84(para)
+msgid "Track, document and verify media sanitization and disposal actions."
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:87(para)
+msgid "Test sanitation equipment and procedures to verify proper performance."
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:91(para)
+msgid "Sanitize portable, removable storage devices prior to connecting such devices to the cloud infrastructure."
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:94(para)
+msgid "Destroy cloud system media that cannot be sanitized."
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:97(para)
+msgid "In an OpenStack deployment you will need to address the following:"
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:99(para)
+msgid "Secure data erasure"
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:102(para) ./doc/security-guide/ch046_data-residency.xml:119(title)
+msgid "Instance memory scrubbing"
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:108(para) ./doc/security-guide/ch046_data-residency.xml:132(title)
+msgid "Compute instance ephemeral storage"
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:111(para) ./doc/security-guide/ch046_data-residency.xml:139(title)
+msgid "Bare metal server sanitization"
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:115(title)
+msgid "Data not securely erased"
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:116(para)
+msgid "Within OpenStack some data may be deleted, but not securely erased in the context of the NIST standards outlined above. This is generally applicable to most or all of the above-defined metadata and information stored in the database. This may be remediated with database and/or system configuration for auto vacuuming and periodic free-space wiping."
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:120(para)
+msgid "Specific to various hypervisors is the treatment of instance memory. This behavior is not defined in OpenStack Compute, although it is generally expected of hypervisors that they will make a best effort to scrub memory either upon deletion of an instance, upon creation of an instance, or both."
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:121(para)
+msgid "Xen explicitly assigns dedicated memory regions to instances and scrubs data upon the destruction of instances (or domains in Xen parlance). KVM depends more greatly on Linux page management; A complex set of rules related to KVM paging is defined in the <link href=\"http://www.linux-kvm.org/page/Memory\">KVM documentation</link>."
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:122(para)
+msgid "It is important to note that use of the Xen memory balloon feature is likely to result in information disclosure. We strongly recommended to avoid use of this feature."
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:123(para)
+msgid "For these and other hypervisors, we recommend referring to hypervisor-specific documentation."
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:126(title)
+msgid "Cinder volume data"
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:127(para)
+msgid "Plugins to OpenStack Block Storage will store data in a variety of ways. Many plug-ins are specific to a vendor or technology, whereas others are more DIY solutions around filesystems such as LVM or ZFS. Methods to securely destroy data will vary from one plugin to another, from one vendor's solution to another, and from one filesystem to another."
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:128(para)
+msgid "Some backends such as ZFS will support copy-on-write to prevent data exposure. In these cases, reads from unwritten blocks will always return zero. Other backends such as LVM may not natively support this, thus the Block Storage plug-in takes the responsibility to override previously written blocks before handing them to users. It is important to review what assurances your chosen volume backend provides and to see what mediations may be available for those assurances not provided."
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:129(para)
+msgid "Finally, while not a feature of OpenStack, vendors and implementors may choose to add or support encryption of volumes. In this case, destruction of data is as simple as throwing away the key."
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:133(para)
+msgid "The creation and destruction of ephemeral storage will be somewhat dependent on the chosen hypervisor and the OpenStack Compute plug-in."
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:134(para)
+msgid "The libvirt plug-in for compute may maintain ephemeral storage directly on a filesystem, or in LVM. Filesystem storage generally will not overwrite data when it is removed, although there is a guarantee that dirty extents are not provisioned to users."
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:135(para)
+msgid "When using LVM backed ephemeral storage, which is block-based, it is necessary that the OpenStack Compute software securely erases blocks to prevent information disclosure. There have in the past been information disclosure vulnerabilities related to improperly erased ephemeral block storage devices."
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:136(para)
+msgid "Filesystem storage is a more secure solution for ephemeral block storage devices than LVM as dirty extents cannot be provisioned to users. However, it is important to be mindful that user data is not destroyed, so it is suggested to encrypt the backing filesystem."
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:140(para)
+msgid "A bare metal server driver for Compute was under development and has since moved into a separate project called <link href=\"https://wiki.openstack.org/wiki/Ironic\">ironic</link>. At the time of this writing, ironic does not appear to address sanitization of tenant data resident the physical hardware."
+msgstr ""
+
+#: ./doc/security-guide/ch046_data-residency.xml:147(para)
+msgid "Additionally, it is possible for tenants of a bare metal system to modify system firmware. TPM technology, described in <xref linkend=\"ch013_node-bootstrapping-idp44768\"/>, provides a solution for detecting unauthorized firmware changes."
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:8(title)
+msgid "Introduction to SSL/TLS"
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:9(para)
+msgid "OpenStack services receive requests on behalf of users on public networks as well as from other internal services over management networks. Inter-service communications can also occur over public networks depending on deployment and architecture choices."
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:10(para)
+msgid "While it is commonly accepted that data over public networks should be secured using cryptographic measures, such as Secure Sockets Layer or Transport Layer Security (SSL/TLS) protocols, it is insufficient to rely on security domain separation to protect internal traffic. Using a security-in-depth approach, we recommend securing all domains with SSL/TLS, including the management domain services. It is important that should a tenant escape their VM isolation and gain access to the hypervisor or host resources, compromise an API endpoint, or any other service, they must not be able to easily inject or capture messages, commands, or otherwise affect or control management capabilities of the cloud. SSL/TLS provides the mechanisms to ensure authentication, non-repudiation, confidentiality, and integrity of user communications to the OpenStack services and between the OpenStack services themselves."
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:11(para)
+msgid "Public Key Infrastructure (PKI) is a set of hardware, software, policies, and procedures required to operate a secure system that provides authentication, non-repudiation, confidentiality, and integrity. The core components of PKI are:"
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:18(term)
+msgid "End entity"
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:20(para)
+msgid "User, process, or system that is the subject of a certificate."
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:25(term)
+msgid "Certification Authority (<glossterm>CA</glossterm>)"
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:27(para)
+msgid "Defines certificate policies, management, and issuance of certificates."
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:32(term)
+msgid "Registration Authority (RA)"
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:34(para)
+msgid "An optional system to which a CA delegates certain management functions."
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:39(term)
+msgid "Repository"
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:41(para)
+msgid "Where the end entity certificates and certificate revocation lists are stored and looked up - sometimes referred to as the <emphasis role=\"italic\">certificate bundle</emphasis>."
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:49(term)
+msgid "Relying party"
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:51(para)
+msgid "The endpoint that is trusting that the CA is valid."
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:56(para)
+msgid "PKI builds the framework on which to provide encryption algorithms, cipher modes, and protocols for securing data and authentication. We strongly recommend securing all services with Public Key Infrastructure (PKI), including the use of SSL/TLS for API endpoints. It is impossible for the encryption or signing of transports or messages alone to solve all these problems. Hosts themselves must be secure and implement policy, namespaces, and other controls to protect their private credentials and keys. However, the challenges of key management and protection do not reduce the necessity of these controls, or lessen their importance."
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:58(title)
+msgid "Certification authorities"
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:59(para)
+msgid "Many organizations have an established Public Key Infrastructure with their own certification authority (CA), certificate policies, and management for which they should use to issue certificates for internal OpenStack users or services. Organizations in which the public security domain is Internet facing will additionally need certificates signed by a widely recognized public CA. For cryptographic communications over the management network, it is recommended one not use a public CA. Instead, we expect and recommend most deployments deploy their own internal CA."
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:60(para)
+msgid "It is recommended that the OpenStack cloud architect consider using separate PKI deployments for internal systems and customer facing services. This allows the cloud deployer to maintain control of their PKI infrastructure and among other things makes requesting, signing and deploying certificates for internal systems easier. Advanced configurations may use separate PKI deployments for different security domains. This allows deployers to maintain cryptographic separation of environments, ensuring that certificates issued to one are not recognised by another."
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:61(para)
+msgid "Certificates used to support SSL/TLS on internet facing cloud endpoints (or customer interfaces where the customer is not expected to have installed anything other than standard operating system provided certificate bundles) should be provisioned using Certificate Authorities that are installed in the operating system certificate bundle. Typical well known vendors include Verisign and Thawte but many others exist."
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:62(para)
+msgid "There are many management, policy, and technical challenges around creating and signing certificates as such is an area where cloud architects or operators may wish to seek the advice of industry leaders and vendors in addition to the guidance recommended here."
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:65(title)
+msgid "SSL/TLS libraries"
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:66(para)
+msgid "Various components, services, and applications within the OpenStack ecosystem or dependencies of OpenStack are implemented and can be configured to use SSL/TLS libraries. The SSL/TLS and HTTP services within OpenStack are typically implemented using OpenSSL which has been proven to be fairly secure and has a module that has been validated for FIPS 140-2. However, keep in mind that each application or service can still introduce weaknesses in how they use the OpenSSL libraries."
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:69(title)
+msgid "Cryptographic algorithms, cipher modes, and protocols"
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:70(para)
+msgid "We recommend only using TLS v1.1 or v1.2. SSLv3 and TLSv1.0 may be used for compatibility but we recommend using caution and only enabling these protocols if you have a strong requirement to do so. Other SSL/TLS versions, explicitly older versions, should not be used. These older versions include SSLv1 and SSLv2. As this book does not intend to be a thorough reference on cryptography we do not wish to be prescriptive about what specific algorithms or cipher modes you should enable or disable in your OpenStack services. However, there are some authoritative references we would like to recommend for further information:"
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:72(link)
+msgid "National Security Agency, Suite B Cryptography"
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:75(link)
+msgid "OWASP Guide to Cryptography"
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:78(link)
+msgid "OWASP Transport Layer Protection Cheat Sheet"
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:81(link)
+msgid "SoK: SSL and HTTPS: Revisiting past challenges and evaluating certificate trust model enhancements"
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:84(link)
+msgid "The Most Dangerous Code in the World: Validating SSL Certificates in Non-Browser Software"
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:87(link)
+msgid "OpenSSL and FIPS 140-2"
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:92(title)
+msgid "Summary"
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:93(para)
+msgid "Given the complexity of the OpenStack components and the number of deployment possibilities, you must take care to ensure that each component gets the appropriate configuration of SSL certificates, keys, and CAs. Subsequent sections discuss the following services:"
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:102(para)
+msgid "Compute API endpoints"
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:105(para)
+msgid "Identity API endpoints"
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:108(para)
+msgid "Networking API endpoints"
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:111(para)
+msgid "Storage API endpoints"
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:114(para)
+msgid "Messaging server"
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:117(para)
+msgid "Database server"
+msgstr ""
+
+#: ./doc/security-guide/ch017_threat-models-confidence-and-confidentiality.xml:123(para)
+msgid "This guide uses the term SSL as a shorthand to refer to these recommendations for SSL/TLS protocols."
+msgstr ""
+
+#: ./doc/security-guide/ch009_case-studies.xml:8(title)
+msgid "Case studies: system documentation"
+msgstr ""
+
+#: ./doc/security-guide/ch009_case-studies.xml:9(para)
+msgid "In this case study we discuss how Alice and Bob would address their system documentation requirements. The documentation suggested above includes hardware and software records, network diagrams, and system configuration details."
+msgstr ""
+
+#: ./doc/security-guide/ch009_case-studies.xml:12(para)
+msgid "Alice needs detailed documentation to satisfy FedRamp requirements. She sets up a configuration management database (CMDB) to store information regarding all of the hardware, firmware, and software versions used throughout the cloud. She also creates a network diagram detailing the cloud architecture, paying careful attention to the security domains and the services that span multiple security domains."
+msgstr ""
+
+#: ./doc/security-guide/ch009_case-studies.xml:13(para)
+msgid "Alice also needs to record each network service running in the cloud, what interfaces and ports it binds to, the security domains for each service, and why the service is needed. Alice decides to build automated tools to log into each system in the cloud over secure shell (SSH) using the <link href=\"http://fabfile.org\">Python Fabric library</link>. The tools collect and store the information in the CMDB, which simplifies the audit process."
+msgstr ""
+
+#: ./doc/security-guide/ch009_case-studies.xml:17(para)
+msgid "In this case, Bob will approach these steps the same as Alice."
+msgstr ""
+
 #. When image changes, this message will be marked fuzzy or untranslated for you.
 #. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:64(None) ./doc/security-guide/ch013_node-bootstrapping.xml:69(None)
-msgid "@@image: 'static/node-provisioning-pxe.png'; md5=51b76c5aced74f935490b37ba921dc43"
+#: ./doc/security-guide/ch031_neutron-architecture.xml:87(None) ./doc/security-guide/ch031_neutron-architecture.xml:92(None)
+msgid "@@image: 'static/sdn-connections.png'; md5=1de9169834b34c83f574f2a1225b27f0"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:12(title)
-msgid "Integrity life-cycle"
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch031_neutron-architecture.xml:109(None) ./doc/security-guide/ch031_neutron-architecture.xml:114(None)
+msgid "@@image: 'static/1aa-network-domains-diagram.png'; md5=135806775939d9e5e750264d8a5fe8de"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:13(para)
-msgid "We define integrity life cycle as a deliberate process that provides assurance that we are always running the expected software with the expected configurations throughout the cloud. This process begins with secure bootstrapping and is maintained through configuration management and security monitoring. This chapter provides recommendations on how to approach the integrity life-cycle process."
+#: ./doc/security-guide/ch031_neutron-architecture.xml:8(title)
+msgid "Networking architecture"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:21(title)
-msgid "Secure bootstrapping"
+#: ./doc/security-guide/ch031_neutron-architecture.xml:9(para)
+msgid "OpenStack Networking is a standalone service that often deploys several processes across a number of nodes. These processes interact with each other and other OpenStack services. The main process of the OpenStack Networking service is <systemitem class=\"service\">neutron-server</systemitem>, a Python daemon that exposes the OpenStack Networking API and passes tenant requests to a suite of plug-ins for additional processing."
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:22(para)
-msgid "Nodes in the cloudincluding compute, storage, network, service, and hybrid nodesshould have an automated provisioning process. This ensures that nodes are provisioned consistently and correctly. This also facilitates security patching, upgrading, bug fixing, and other critical changes. Since this process installs new software that runs at the highest privilege levels in the cloud, it is important to verify that the correct software is installed. This includes the earliest stages of the boot process."
+#: ./doc/security-guide/ch031_neutron-architecture.xml:17(para)
+msgid "The OpenStack Networking components are:"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:31(para)
-msgid "There are a variety of technologies that enable verification of these early boot stages. These typically require hardware support such as the trusted platform module (TPM), Intel Trusted Execution Technology (TXT), dynamic root of trust measurement (DRTM), and Unified Extensible Firmware Interface (UEFI) secure boot. In this book, we will refer to all of these collectively as <emphasis>secure boot technologies</emphasis>. We recommend using secure boot, while acknowledging that many of the pieces necessary to deploy this require advanced technical skills in order to customize the tools for each environment. Utilizing secure boot will require deeper integration and customization than many of the other recommendations in this guide. TPM technology, while common in most business class laptops and desktops for several years, and is now becoming available in servers together with supporting BIOS. Proper planning is essential to a successful secure boot deployment."
+#: ./doc/security-guide/ch031_neutron-architecture.xml:21(term)
+msgid "neutron server (<systemitem class=\"service\">neutron-server</systemitem> and <systemitem class=\"service\">neutron-*-plugin</systemitem>)"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:47(para)
-msgid "A complete tutorial on secure boot deployment is beyond the scope of this book. Instead, here we provide a framework for how to integrate secure boot technologies with the typical node provisioning process. For additional details, cloud architects should refer to the related specifications and software configuration manuals."
+#: ./doc/security-guide/ch031_neutron-architecture.xml:25(para)
+msgid "This service runs on the network node to service the Networking API and its extensions. It also enforces the network model and IP addressing of each port. The neutron-server and plugin agents require access to a database for persistent storage and access to a message queue for inter-communication."
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:54(title)
-msgid "Node provisioning"
+#: ./doc/security-guide/ch031_neutron-architecture.xml:35(term)
+msgid "plugin agent (<systemitem class=\"service\">neutron-*-agent</systemitem>)"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:55(para)
-msgid "Nodes should use Preboot eXecution Environment (PXE) for provisioning. This significantly reduces the effort required for redeploying nodes. The typical process involves the node receiving various boot stagesthat is progressively more complex software to execute from a server."
+#: ./doc/security-guide/ch031_neutron-architecture.xml:38(para)
+msgid "Runs on each compute node to manage local virtual switch (vswitch) configuration. The plug-in that you use determine which agents run. This service requires message queue access. <emphasis>Optional depending on plugin.</emphasis>"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:72(para)
-msgid "We recommend using a separate, isolated network within the management security domain for provisioning. This network will handle all PXE traffic, along with the subsequent boot stage downloads depicted above. Note that the node boot process begins with two insecure operations: DHCP and TFTP. Then the boot process downloads over SSL the remaining information required to deploy the node. This information might include an initramfs and a kernel. This concludes by downloading the remaining information needed to deploy the node. This may be an operating system installer, a basic install managed by <link href=\"http://www.opscode.com/chef/\">Chef</link> or <link href=\"https://puppetlabs.com/\">Puppet</link>, or even a complete file system image that is written directly to disk."
+#: ./doc/security-guide/ch031_neutron-architecture.xml:46(term)
+msgid "DHCP agent (<systemitem class=\"service\">neutron-dhcp-agent</systemitem>)"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:86(para)
-msgid "While utilizing SSL during the PXE boot process is somewhat more challenging, common PXE firmware projects, such as iPXE, provide this support. Typically this involves building the PXE firmware with knowledge of the allowed SSL certificate chain(s) so that it can properly validate the server certificate. This raises the bar for an attacker by limiting the number of insecure, plain text network operations."
+#: ./doc/security-guide/ch031_neutron-architecture.xml:49(para)
+msgid "Provides DHCP services to tenant networks. This agent is the same across all plug-ins and is responsible for maintaining DHCP configuration. The <systemitem class=\"service\">neutron-dhcp-agent</systemitem> requires message queue access."
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:96(title)
-msgid "Verified boot"
+#: ./doc/security-guide/ch031_neutron-architecture.xml:58(term)
+msgid "L3 agent (<systemitem class=\"service\">neutron-l3-agent</systemitem>)"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:97(para)
-msgid "In general, there are two different strategies for verifying the boot process. Traditional <emphasis>secure boot</emphasis> will validate the code run at each step in the process, and stop the boot if code is incorrect. <emphasis>Boot attestation</emphasis> will record which code is run at each step, and provide this information to another machine as proof that the boot process completed as expected. In both cases, the first step is to measure each piece of code before it is run. In this context, a measurement is effectively a SHA-1 hash of the code, taken before it is executed. The hash is stored in a platform configuration register (PCR) in the TPM."
+#: ./doc/security-guide/ch031_neutron-architecture.xml:61(para)
+msgid "Provides L3/NAT forwarding for external network access of VMs on tenant networks. Requires message queue access. <emphasis>Optional depending on plug-in.</emphasis>"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:109(para)
-msgid "Note: SHA-1 is used here because this is what the TPM chips support."
+#: ./doc/security-guide/ch031_neutron-architecture.xml:69(term)
+msgid "network provider services (SDN server/services)"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:111(para)
-msgid "Each TPM has at least 24 PCRs. The TCG Generic Server Specification, v1.0, March 2005, defines the PCR assignments for boot-time integrity measurements. The table below shows a typical PCR configuration. The context indicates if the values are determined based on the node hardware (firmware) or the software provisioned onto the node. Some values are influenced by firmware versions, disk sizes, and other low-level information. Therefore, it is important to have good practices in place around configuration management to ensure that each system deployed is configured exactly as desired."
+#: ./doc/security-guide/ch031_neutron-architecture.xml:71(para)
+msgid "Provide additional networking services to tenant networks. These SDN services might interact with the <systemitem class=\"service\">neutron-server</systemitem>, <systemitem class=\"service\">neutron-plugin</systemitem>, and/or plugin-agents through REST APIs or other communication channels."
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:131(emphasis)
-msgid "Register"
+#: ./doc/security-guide/ch031_neutron-architecture.xml:81(para)
+msgid "The following figure shows an architectural and networking flow diagram of the OpenStack Networking components:"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:132(emphasis)
-msgid "What is measured"
+#: ./doc/security-guide/ch031_neutron-architecture.xml:97(title)
+msgid "OpenStack Networking service placement on physical servers"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:135(emphasis)
-msgid "Context"
+#: ./doc/security-guide/ch031_neutron-architecture.xml:98(para)
+msgid "This guide focuses on a standard architecture that includes a <emphasis>cloud controller</emphasis> host, a <emphasis>network</emphasis> host, and a set of <emphasis>compute</emphasis> hypervisors for running VMs."
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:138(para)
-msgid "PCR-00"
+#: ./doc/security-guide/ch031_neutron-architecture.xml:105(title)
+msgid "Network connectivity of physical servers"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:139(para)
-msgid "Core Root of Trust Measurement (CRTM), BIOS code, Host platform extensions"
+#: ./doc/security-guide/ch031_neutron-architecture.xml:118(para)
+msgid "A standard OpenStack Networking setup has up to four distinct physical data center networks:"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:141(para) ./doc/security-guide/ch013_node-bootstrapping.xml:146(para) ./doc/security-guide/ch013_node-bootstrapping.xml:151(para) ./doc/security-guide/ch013_node-bootstrapping.xml:156(para)
-msgid "Hardware"
+#: ./doc/security-guide/ch031_neutron-architecture.xml:122(term)
+msgid "Management network"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:144(para)
-msgid "PCR-01"
+#: ./doc/security-guide/ch031_neutron-architecture.xml:124(para)
+msgid "Used for internal communication between OpenStack Components. The IP addresses on this network should be reachable only within the data center and is considered the Management Security Domain."
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:145(para)
-msgid "Host platform configuration"
+#: ./doc/security-guide/ch031_neutron-architecture.xml:132(term)
+msgid "Guest network"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:149(para)
-msgid "PCR-02"
+#: ./doc/security-guide/ch031_neutron-architecture.xml:134(para)
+msgid "Used for VM data communication within the cloud deployment. The IP addressing requirements of this network depend on the OpenStack Networking plug-in in use and the network configuration choices of the virtual networks made by the tenant. This network is considered the Guest Security Domain."
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:150(para)
-msgid "Option ROM code"
+#: ./doc/security-guide/ch031_neutron-architecture.xml:144(term)
+msgid "External network"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:154(para)
-msgid "PCR-03"
+#: ./doc/security-guide/ch031_neutron-architecture.xml:146(para)
+msgid "Used to provide VMs with Internet access in some deployment scenarios. The IP addresses on this network should be reachable by anyone on the Internet and is considered to be in the Public Security Domain."
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:155(para)
-msgid "Option ROM configuration and data"
+#: ./doc/security-guide/ch031_neutron-architecture.xml:154(term)
+msgid "API network"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:159(para)
-msgid "PCR-04"
+#: ./doc/security-guide/ch031_neutron-architecture.xml:156(para)
+msgid "Exposes all OpenStack APIs, including the OpenStack Networking API, to tenants. The IP addresses on this network should be reachable by anyone on the Internet. This may be the same network as the external network, as it is possible to create a subnet for the external network that uses IP allocation ranges to use only less than the full range of IP addresses in an IP block. This network is considered the Public Security Domain."
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:160(para)
-msgid "Initial Program Loader (IPL) code. For example, master boot record."
+#: ./doc/security-guide/ch031_neutron-architecture.xml:169(para)
+msgid "For additional information see the <link href=\"http://docs.openstack.org/admin-guide-cloud/content/ch_networking.html\">Networking chapter</link> in the <citetitle>OpenStack Cloud Administrator Guide</citetitle>."
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:162(para) ./doc/security-guide/ch013_node-bootstrapping.xml:167(para) ./doc/security-guide/ch013_node-bootstrapping.xml:172(para) ./doc/security-guide/ch013_node-bootstrapping.xml:177(para) ./doc/security-guide/ch013_node-bootstrapping.xml:183(para) ./doc/security-guide/ch013_node-bootstrapping.xml:188(para) ./doc/security-guide/ch013_node-bootstrapping.xml:193(para)
-msgid "Software"
+#: ./doc/security-guide/ch011_management-introduction.xml:8(title)
+msgid "Management introduction"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:165(para)
-msgid "PCR-05"
+#: ./doc/security-guide/ch011_management-introduction.xml:9(para)
+msgid "A cloud deployment is a living system. Machines age and fail, software becomes outdated, vulnerabilities are discovered. When errors or omissions are made in configuration, or when software fixes must be applied, these changes must be made in a secure, but convenient, fashion. These changes are typically solved through configuration management."
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:166(para)
-msgid "IPL code configuration and data"
+#: ./doc/security-guide/ch011_management-introduction.xml:10(para)
+msgid "Likewise, it is important to protect the cloud deployment from being configured or manipulated by malicious entities. With many systems in a cloud employing compute and networking virtualization, there are distinct challenges applicable to OpenStack which must be addressed through integrity lifecycle management."
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:170(para)
-msgid "PCR-06"
+#: ./doc/security-guide/ch011_management-introduction.xml:11(para)
+msgid "Finally, administrators must perform command and control over the cloud for various operational functions. It is important these command and control facilities are understood and secured."
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:171(para)
-msgid "State transition and wake events"
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch042_database-overview.xml:18(None) ./doc/security-guide/ch042_database-overview.xml:21(None)
+msgid "@@image: 'static/databaseusername.png'; md5=a6a5dadedbc1517069ca388c7ac5940a"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:175(para)
-msgid "PCR-07"
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch042_database-overview.xml:42(None) ./doc/security-guide/ch042_database-overview.xml:45(None)
+msgid "@@image: 'static/databaseusernamessl.png'; md5=9c43242c47eb159b6f61ac41f3d8bced"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:176(para)
-msgid "Host platform manufacturer control"
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/security-guide/ch042_database-overview.xml:104(None) ./doc/security-guide/ch042_database-overview.xml:107(None)
+msgid "@@image: 'static/novaconductor.png'; md5=dbc1ba139bd1af333f0415bb48704843"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:180(para)
-msgid "PCR-08"
+#: ./doc/security-guide/ch042_database-overview.xml:8(title)
+msgid "Database access control"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:181(para)
-msgid "Platform specific, often kernel, kernel extensions, and drivers"
+#: ./doc/security-guide/ch042_database-overview.xml:9(para)
+msgid "Each of the core OpenStack services (Compute, Identity, Networking, Block Storage) store state and configuration information in databases. In this chapter, we discuss how databases are used currently in OpenStack. We also explore security concerns, and the security ramifications of database backend choices."
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:186(para)
-msgid "PCR-09"
+#: ./doc/security-guide/ch042_database-overview.xml:11(title)
+msgid "OpenStack database access model"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:187(para)
-msgid "Platform specific, often Initramfs"
+#: ./doc/security-guide/ch042_database-overview.xml:12(para)
+msgid "All of the services within an OpenStack project access a single database. There are presently no reference policies for creating table or row based access restrictions to the database."
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:191(para)
-msgid "PCR-10 to PCR-23"
+#: ./doc/security-guide/ch042_database-overview.xml:13(para)
+msgid "There are no general provisions for granular control of database operations in OpenStack. Access and privileges are granted simply based on whether a node has access to the database or not. In this scenario, nodes with access to the database may have full privileges to DROP, INSERT, or UPDATE functions."
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:192(para)
-msgid "Platform specific"
+#: ./doc/security-guide/ch042_database-overview.xml:15(title)
+msgid "Granular access control"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:198(para)
-msgid "At the time of this writing, very few clouds are using secure boot technologies in a production environment. As a result, these technologies are still somewhat immature. We recommend planning carefully in terms of hardware selection. For example, ensure that you have a TPM and Intel TXT support. Then verify how the node hardware vendor populates the PCR values. For example, which values will be available for validation. Typically the PCR values listed under the software context in the table above are the ones that a cloud architect has direct control over. But even these may change as the software in the cloud is upgraded. Configuration management should be linked into the PCR policy engine to ensure that the validation is always up to date."
+#: ./doc/security-guide/ch042_database-overview.xml:16(para)
+msgid "By default, each of the OpenStack services and their processes access the database using a shared set of credentials. This makes auditing database operations and revoking access privileges from a service and its processes to the database particularly difficult."
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:211(para)
-msgid "Each manufacturer must provide the BIOS and firmware code for their servers. Different servers, hypervisors, and operating systems will choose to populate different PCRs. In most real world deployments, it will be impossible to validate every PCR against a known good quantity (\"golden measurement\"). Experience has shown that, even within a single vendor's product line, the measurement process for a given PCR may not be consistent. We recommend establishing a baseline for each server and monitoring the PCR values for unexpected changes. Third-party software may be available to assist in the TPM provisioning and monitoring process, depending upon your chosen hypervisor solution."
+#: ./doc/security-guide/ch042_database-overview.xml:26(title) ./doc/security-guide/ch042_database-overview.xml:99(title)
+msgid "Nova-conductor"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:223(para)
-msgid "The initial program loader (IPL) code will most likely be the PXE firmware, assuming the node deployment strategy outlined above. Therefore, the secure boot or boot attestation process can measure all of the early stage boot code, such as, bios, firmware, and the like, the PXE firmware, and the node kernel. Ensuring that each node has the correct versions of these pieces installed provides a solid foundation on which to build the rest of the node software stack."
+#: ./doc/security-guide/ch042_database-overview.xml:27(para)
+msgid "The compute nodes are the least trusted of the services in OpenStack because they host tenant instances. The <systemitem class=\"service\">nova-conductor</systemitem> service has been introduced to serve as a database proxy, acting as an intermediary between the compute nodes and the database. We discuss its ramifications later in this chapter."
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:231(para)
-msgid "Depending on the strategy selected, in the event of a failure the node will either fail to boot or it can report the failure back to another entity in the cloud. For secure boot, the node will fail to boot and a provisioning service within the management security domain must recognize this and log the event. For boot attestation, the node will already be running when the failure is detected. In this case the node should be immediately quarantined by disabling its network access. Then the event should be analyzed for the root cause. In either case, policy should dictate how to proceed after a failure. A cloud may automatically attempt to re-provision a node a certain number of times. Or it may immediately notify a cloud administrator to investigate the problem. The right policy here will be deployment and failure mode specific."
+#: ./doc/security-guide/ch042_database-overview.xml:28(para)
+msgid "We strongly recommend:"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:247(title)
-msgid "Node hardening"
+#: ./doc/security-guide/ch042_database-overview.xml:30(para)
+msgid "All database communications be isolated to a management network"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:248(para)
-msgid "At this point we know that the node has booted with the correct kernel and underlying components. There are many paths for hardening a given operating system deployment. The specifics on these steps are outside of the scope of this book. We recommend following the guidance from a hardening guide specific to your operating system. For example, the <link href=\"http://iase.disa.mil/stigs/\">security technical implementation guides</link> (STIG) and the <link href=\"http://www.nsa.gov/ia/mitigation_guidance/security_configuration_guides/\">NSA guides</link> are useful starting places."
+#: ./doc/security-guide/ch042_database-overview.xml:33(para)
+msgid "Securing communications using SSL"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:258(para)
-msgid "The nature of the nodes makes additional hardening possible. We recommend the following additional steps for production nodes:"
+#: ./doc/security-guide/ch042_database-overview.xml:36(para)
+msgid "Creating unique database user accounts per OpenStack service endpoint (illustrated below)"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:263(para)
-msgid "Use a read-only file system where possible. Ensure that writeable file systems do not permit execution. This can be handled through the mount options provided in <filename>/etc/fstab</filename>."
+#: ./doc/security-guide/ch042_database-overview.xml:52(title)
+msgid "Database authentication and access control"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:269(para)
-msgid "Use a mandatory access control policy to contain the instances, the node services, and any other critical processes and data on the node. See the discussions on sVirt / SELinux and AppArmor below."
+#: ./doc/security-guide/ch042_database-overview.xml:53(para)
+msgid "Given the risks around access to the database, we strongly recommend that unique database user accounts be created per node needing access to the database. Doing this facilitates better analysis and auditing for ensuring compliance or in the event of a compromise of a node allows you to isolate the compromised host by removing access for that node to the database upon detection. When creating these per service endpoint database user accounts, care should be taken to ensure that they are configured to require SSL. Alternatively, for increased security it is recommended that the database accounts be configured using X.509 certificate authentication in addition to usernames and passwords."
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:275(para)
-msgid "Remove any unnecessary software packages. This should result in a very stripped down installation because a compute node has a relatively small number of dependencies."
+#: ./doc/security-guide/ch042_database-overview.xml:55(title)
+msgid "Privileges"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:281(para)
-msgid "Finally, the node kernel should have a mechanism to validate that the rest of the node starts in a known good state. This provides the necessary link from the boot validation process to validating the entire system. The steps for doing this will be deployment specific. As an example, a kernel module could verify a hash over the blocks comprising the file system before mounting it using <link href=\"https://code.google.com/p/cryptsetup/wiki/DMVerity\">dm-verity</link>."
+#: ./doc/security-guide/ch042_database-overview.xml:56(para)
+msgid "A separate database administrator (DBA) account should be created and protected that has full privileges to create/drop databases, create user accounts, and update user privileges. This simple means of separation of responsibility helps prevent accidental misconfiguration, lowers risk and lowers scope of compromise."
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:293(title)
-msgid "Runtime verification"
+#: ./doc/security-guide/ch042_database-overview.xml:57(para)
+msgid "The database user accounts created for the OpenStack services and for each node should have privileges limited to just the database relevant to the service where the node is a member."
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:294(para)
-msgid "Once the node is running, we need to ensure that it remains in a good state over time. Broadly speaking, this includes both configuration management and security monitoring. The goals for each of these areas are different. By checking both, we achieve higher assurance that the system is operating as desired. We discuss configuration management in the management section, and security monitoring below."
+#: ./doc/security-guide/ch042_database-overview.xml:61(title)
+msgid "Require user accounts to require SSL transport"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:302(title)
-msgid "Intrusion detection system"
+#: ./doc/security-guide/ch042_database-overview.xml:63(title) ./doc/security-guide/ch042_database-overview.xml:81(title)
+msgid "Configuration example #1: (MySQL)"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:303(para)
-msgid "Host-based intrusion detection tools are also useful for automated validation of the cloud internals. There are a wide variety of host-based intrusion detection tools available. Some are open source projects that are freely available, while others are commercial. Typically these tools analyze data from a variety of sources and produce security alerts based on rule sets and/or training. Typical capabilities include log analysis, file integrity checking, policy monitoring, and rootkit detection. More advanced -- often custom -- tools can validate that in-memory process images match the on-disk executable and validate the execution state of a running process."
+#: ./doc/security-guide/ch042_database-overview.xml:67(title) ./doc/security-guide/ch042_database-overview.xml:87(title)
+msgid "Configuration example #2: (PostgreSQL)"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:315(para)
-msgid "One critical policy decision for a cloud architect is what to do with the output from a security monitoring tool. There are effectively two options. The first is to alert a human to investigate and/or take corrective action. This could be done by including the security alert in a log or events feed for cloud administrators. The second option is to have the cloud take some form of remedial action automatically, in addition to logging the event. Remedial actions could include anything from re-installing a node to performing a minor service configuration. However, automated remedial action can be challenging due to the possibility of false positives."
+#: ./doc/security-guide/ch042_database-overview.xml:68(para)
+msgid "In file <filename>pg_hba.conf</filename>:"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:326(para)
-msgid "False positives occur when the security monitoring tool produces a security alert for a benign event. Due to the nature of security monitoring tools, false positives will most certainly occur from time to time. Typically a cloud administrator can tune security monitoring tools to reduce the false positives, but this may also reduce the overall detection rate at the same time. These classic trade-offs must be understood and accounted for when setting up a security monitoring system in the cloud."
+#: ./doc/security-guide/ch042_database-overview.xml:70(para)
+msgid "Note this command only adds the ability to communicate over SSL and is non-exclusive. Other access methods that may allow unencrypted transport should be disabled so that SSL is the sole access method."
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:335(para)
-msgid "The selection and configuration of a host-based intrusion detection tool is highly deployment specific. We recommend starting by exploring the following open source projects which implement a variety of host-based intrusion detection and file monitoring features."
+#: ./doc/security-guide/ch042_database-overview.xml:71(para)
+msgid "The <literal>md5</literal> parameter defines the authentication method as a hashed password. We provide a secure authentication example in the section below."
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:343(link)
-msgid "OSSEC"
+#: ./doc/security-guide/ch042_database-overview.xml:78(title)
+msgid "Authentication with X.509 certificates"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:347(link)
-msgid "Samhain"
+#: ./doc/security-guide/ch042_database-overview.xml:79(para)
+msgid "Security may be enhanced by requiring X.509 client certificates for authentication. Authenticating to the database in this manner provides greater identity assurance of the client making the connection to the database and ensures that the communications are encrypted."
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:352(link)
-msgid "Tripwire"
+#: ./doc/security-guide/ch042_database-overview.xml:92(title)
+msgid "OpenStack service database configuration"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:356(link)
-msgid "AIDE"
+#: ./doc/security-guide/ch042_database-overview.xml:93(para)
+msgid "If your database server is configured to require X.509 certificates for authentication you will need to specify the appropriate SQLAlchemy query parameters for the database backend. These parameters specify the certificate, private key, and certificate authority information for use with the initial connection string."
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:359(para)
-msgid "Network intrusion detection tools complement the host-based tools. OpenStack doesn't have a specific network IDS built-in, but OpenStack Networking provides a plug-in mechanism to enable different technologies through the Networking API. This plug-in architecture will allow tenants to develop API extensions to insert and configure their own advanced networking services like a firewall, an intrusion detection system, or a VPN between the VMs."
+#: ./doc/security-guide/ch042_database-overview.xml:94(para)
+msgid "Example of an <literal>:sql_connection</literal> string for X.509 certificate authentication to MySQL:"
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:367(para)
-msgid "Similar to host-based tools, the selection and configuration of a network-based intrusion detection tool is deployment specific. <link href=\"http://www.snort.org/\">Snort</link> is the leading open source networking intrusion detection tool, and a good starting place to learn more."
+#: ./doc/security-guide/ch042_database-overview.xml:100(para)
+msgid "OpenStack Compute offers a sub-service called <systemitem class=\"service\">nova-conductor</systemitem> which proxies database connections, with the primary purpose of having the nova compute nodes interfacing with <systemitem class=\"service\">nova-conductor</systemitem> to meet data persistence needs as opposed to directly communicating with the database."
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:373(para)
-msgid "There are a few important security considerations for network and host-based intrusion detection systems."
+#: ./doc/security-guide/ch042_database-overview.xml:101(para)
+msgid "Nova-conductor receives requests over RPC and performs actions on behalf of the calling service without granting granular access to the database, its tables, or data within. Nova-conductor essentially abstracts direct database access away from compute nodes."
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:377(para)
-msgid "It is important to consider the placement of the Network IDS on the cloud (for example, adding it to the network boundary and/or around sensitive networks). The placement depends on your network environment but make sure to monitor the impact the IDS may have on your services depending on where you choose to add it. Encrypted traffic, such as SSL, cannot generally be inspected for content by a Network IDS. However, the Network IDS may still provide some benefit in identifying anomalous unencrypted traffic on the network."
+#: ./doc/security-guide/ch042_database-overview.xml:102(para)
+msgid "This abstraction offers the advantage of restricting services to executing methods with parameters, similar to stored procedures, preventing a large number of systems from directly accessing or modifying database data. This is accomplished without having these procedures stored or executed within the context or scope of the database itself, a frequent criticism of typical stored procedures."
 msgstr ""
 
-#: ./doc/security-guide/ch013_node-bootstrapping.xml:389(para)
-msgid "In some deployments it may be required to add host-based IDS on sensitive components on security domain bridges. A host-based IDS may detect anomalous activity by compromised or unauthorized processes on the component. The IDS should transmit alert and log information on the Management network."
+#: ./doc/security-guide/ch042_database-overview.xml:110(para)
+msgid "Unfortunately, this solution complicates the task of more fine-grained access control and the ability to audit data access. Because the <systemitem class=\"service\">nova-conductor</systemitem> service receives requests over RPC, it highlights the importance of improving the security of messaging. Any node with access to the message queue may execute these methods provided by the <systemitem class=\"service\">nova-conductor</systemitem> and effectively modifying the database."
 msgstr ""
 
-#: ./doc/security-guide/ch038_transport-security.xml:8(title)
-msgid "Messaging security"
+#: ./doc/security-guide/ch042_database-overview.xml:111(para)
+msgid "Finally, it should be noted that as of the Grizzly release, gaps exist where <systemitem class=\"service\">nova-conductor</systemitem> is not used throughout OpenStack Compute. Depending on one's configuration, the use of <systemitem class=\"service\">nova-conductor</systemitem> may not allow deployers to avoid the necessity of providing database GRANTs to individual compute host systems."
 msgstr ""
 
-#: ./doc/security-guide/ch038_transport-security.xml:9(para)
-msgid "This chapter discusses security hardening approaches for the three most common message queuing solutions use in OpenStack: RabbitMQ, Qpid, and ZeroMQ."
+#: ./doc/security-guide/ch042_database-overview.xml:112(para)
+msgid "Note, as <systemitem class=\"service\">nova-conductor</systemitem> only applies to OpenStack Compute, direct database access from compute hosts may still be necessary for the operation of other OpenStack components such as Telemetry (ceilometer), Networking, and Block Storage."
 msgstr ""
 
-#: ./doc/security-guide/ch038_transport-security.xml:11(title)
-msgid "Messaging transport security"
+#: ./doc/security-guide/ch042_database-overview.xml:118(para)
+msgid "Implementors should weigh the benefits and risks of both configurations before enabling or disabling the <systemitem class=\"service\">nova-conductor</systemitem> service. We are not yet prepared to recommend the use of <systemitem class=\"service\">nova-conductor</systemitem> in the Grizzly release. However, we do believe that this recommendation will change as additional features are added into OpenStack."
 msgstr ""
 
-#: ./doc/security-guide/ch038_transport-security.xml:12(para)
-msgid "AMQP based solutions (Qpid and RabbitMQ) support transport-level security using SSL. ZeroMQ messaging does not natively support SSL, but transport-level security is possible using labelled IPSec or CIPSO network labels."
+#: ./doc/security-guide/ch042_database-overview.xml:119(para)
+msgid "To disable the <systemitem class=\"service\">nova-conductor</systemitem>, place the following into your <filename>nova.conf</filename> file (on your compute hosts):"
 msgstr ""
 
-#: ./doc/security-guide/ch038_transport-security.xml:13(para)
-msgid "We highly recommend enabling transport-level cryptography for your message queue. Using SSL for the messaging client connections provides protection of the communications from tampering and eavesdropping in-transit to the messaging server. Below is guidance on how SSL is typically configured for the two popular messaging servers Qpid and RabbitMQ. When configuring the trusted certificate authority (CA) bundle that your messaging server uses to verify client connections, it is recommended that this be limited to only the CA used for your nodes, preferably an internally managed CA. The bundle of trusted CAs will determine which client certificates will be authorized and pass the client-server verification step of the setting up the SSL connection. Note, when installing the certificate and key files, ensure that the file permissions are restricted, for example chmod 0600, and the ownership is restricted to the messaging server daemon user to prevent unauthorized access by other processes and users on the messaging server."
+#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:8(title)
+msgid "Case studies: tenant data"
 msgstr ""
 
-#: ./doc/security-guide/ch038_transport-security.xml:15(title)
-msgid "RabbitMQ server SSL configuration"
+#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:9(para)
+msgid "Returning to Alice and Bob, we will use this section to dive into their particular tenant data privacy requirements. Specifically, we will look into how Alice and Bob both handle tenant data, data destruction, and data encryption."
 msgstr ""
 
-#: ./doc/security-guide/ch038_transport-security.xml:16(para)
-msgid "The following lines should be added to the system-wide RabbitMQ configuration file, typically <filename>/etc/rabbitmq/rabbitmq.config</filename>:"
+#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:18(para)
+msgid "As stated during the introduction to Alice's case study, data protection is of an extremely high priority. She needs to ensure that a compromise of one tenant's data does not cause loss of other tenant data. She also has strong regulator requirements that require documentation of data destruction activities. Alice does this using the following:"
 msgstr ""
 
-#: ./doc/security-guide/ch038_transport-security.xml:31(para)
-msgid "Note, the <literal>tcp_listeners</literal> option is set to <literal>[]</literal> to prevent it from listening an on non-SSL port. The <literal>ssl_listeners</literal> option should be restricted to only listen on the management network for the services."
+#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:28(para)
+msgid "Establishing procedures to sanitize tenant data when a program or project ends."
 msgstr ""
 
-#: ./doc/security-guide/ch038_transport-security.xml:36(para)
-msgid "For more information on RabbitMQ SSL configuration see:"
+#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:32(para)
+msgid "Track the destruction of both the tenant data and metadata through ticketing in a CMDB."
 msgstr ""
 
-#: ./doc/security-guide/ch038_transport-security.xml:39(link)
-msgid "RabbitMQ Configuration"
+#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:35(para) ./doc/security-guide/ch049_case-studies-tenant-data.xml:69(para)
+msgid "For Volume storage:"
 msgstr ""
 
-#: ./doc/security-guide/ch038_transport-security.xml:43(link)
-msgid "RabbitMQ SSL"
+#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:38(para) ./doc/security-guide/ch049_case-studies-tenant-data.xml:72(para)
+msgid "Physical server issues"
 msgstr ""
 
-#: ./doc/security-guide/ch038_transport-security.xml:48(title)
-msgid "Qpid server SSL configuration"
+#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:41(para)
+msgid "To provide secure ephemeral instance storage, Alice implements qcow2 files on an encrypted filesystem."
 msgstr ""
 
-#: ./doc/security-guide/ch038_transport-security.xml:49(para)
-msgid "The Apache Foundation has a messaging security guide for Qpid. See:"
+#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:51(para)
+msgid "As stated during the introduction to Bob's case study, tenant privacy is of an extremely high priority. In addition to the requirements and actions Bob will take to isolate tenants from one another at the infrastructure layer, Bob also needs to provide assurances for tenant data privacy. Bob does this using the following:"
 msgstr ""
 
-#: ./doc/security-guide/ch038_transport-security.xml:51(link)
-msgid "Apache Qpid SSL"
+#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:61(para)
+msgid "Establishing procedures to sanitize customer data when a customer churns."
 msgstr ""
 
-#: ./doc/security-guide/ch038_transport-security.xml:57(title)
-msgid "Queue authentication and access control"
+#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:65(para)
+msgid "Track the destruction of both the customer data and metadata through ticketing in a CMDB."
 msgstr ""
 
-#: ./doc/security-guide/ch038_transport-security.xml:58(para)
-msgid "RabbitMQ and Qpid offer authentication and access control mechanisms for controlling access to queues. ZeroMQ offers no such mechanisms."
-msgstr ""
-
-#: ./doc/security-guide/ch038_transport-security.xml:59(para)
-msgid "Simple Authentication and Security Layer (SASL) is a framework for authentication and data security in Internet protocols. Both RabbitMQ and Qpid offer SASL and other pluggable authentication mechanisms beyond simple usernames and passwords that allow for increased authentication security. While RabbitMQ supports SASL, support in OpenStack does not currently allow for requesting a specific SASL authentication mechanism. RabbitMQ support in OpenStack allows for either username and password authentication over an unencrypted connection or username and password in conjunction with X.509 client certificates to establish the secure SSL connection."
-msgstr ""
-
-#: ./doc/security-guide/ch038_transport-security.xml:60(para)
-msgid "We recommend configuring X.509 client certificates on all the OpenStack service nodes for client connections to the messaging queue and where possible (currently only Qpid) perform authentication with X.509 client certificates. When using usernames and passwords, accounts should be created per-service and node for finer grained auditability of access to the queue."
-msgstr ""
-
-#: ./doc/security-guide/ch038_transport-security.xml:61(para)
-msgid "Before deployment, consider the SSL libraries that the queuing servers use. Qpid uses Mozilla's NSS library, whereas RabbitMQ uses Erlang's SSL module which uses OpenSSL."
-msgstr ""
-
-#: ./doc/security-guide/ch038_transport-security.xml:66(title)
-msgid "Authentication configuration example: RabbitMQ"
-msgstr ""
-
-#: ./doc/security-guide/ch038_transport-security.xml:67(para)
-msgid "On the RabbitMQ server, delete the default <literal>guest</literal> user:"
-msgstr ""
-
-#: ./doc/security-guide/ch038_transport-security.xml:70(para)
-msgid "On the RabbitMQ server, for each OpenStack service or node that communicates with the message queue set up user accounts and privileges:"
-msgstr ""
-
-#: ./doc/security-guide/ch038_transport-security.xml:75(para)
-msgid "For additional configuration information see:"
-msgstr ""
-
-#: ./doc/security-guide/ch038_transport-security.xml:77(link)
-msgid "RabbitMQ Access Control"
-msgstr ""
-
-#: ./doc/security-guide/ch038_transport-security.xml:80(link)
-msgid "RabbitMQ Authentication"
-msgstr ""
-
-#: ./doc/security-guide/ch038_transport-security.xml:83(link)
-msgid "RabbitMQ Plugins"
-msgstr ""
-
-#: ./doc/security-guide/ch038_transport-security.xml:86(link)
-msgid "RabbitMQ SASL External Auth"
-msgstr ""
-
-#: ./doc/security-guide/ch038_transport-security.xml:91(title)
-msgid "OpenStack service configuration: RabbitMQ"
-msgstr ""
-
-#: ./doc/security-guide/ch038_transport-security.xml:104(title)
-msgid "Authentication configuration example: Qpid"
-msgstr ""
-
-#: ./doc/security-guide/ch038_transport-security.xml:105(para)
-msgid "For configuration information see:"
-msgstr ""
-
-#: ./doc/security-guide/ch038_transport-security.xml:107(link)
-msgid "Apache Qpid Authentication"
-msgstr ""
-
-#: ./doc/security-guide/ch038_transport-security.xml:110(link)
-msgid "Apache Qpid Authorization"
-msgstr ""
-
-#: ./doc/security-guide/ch038_transport-security.xml:115(title)
-msgid "OpenStack service configuration: Qpid"
-msgstr ""
-
-#: ./doc/security-guide/ch038_transport-security.xml:124(para)
-msgid "Optionally, if using SASL with Qpid specify the SASL mechanisms in use by adding:"
-msgstr ""
-
-#: ./doc/security-guide/ch038_transport-security.xml:129(title)
-msgid "Message queue process isolation and policy"
-msgstr ""
-
-#: ./doc/security-guide/ch038_transport-security.xml:130(para)
-msgid "Each project provides a number of services which send and consume messages. Each binary which sends a message is expected to consume messages, if only replies, from the queue."
-msgstr ""
-
-#: ./doc/security-guide/ch038_transport-security.xml:131(para)
-msgid "Message queue service processes should be isolated from each other and other processes on a machine."
-msgstr ""
-
-#: ./doc/security-guide/ch038_transport-security.xml:134(para)
-msgid "Network namespaces are highly recommended for all services running on OpenStack Compute Hypervisors. This will help prevent against the bridging of network traffic between VM guests and the management network."
-msgstr ""
-
-#: ./doc/security-guide/ch038_transport-security.xml:135(para)
-msgid "When using ZeroMQ messaging, each host must run at least one ZeroMQ message receiver to receive messages from the network and forward messages to local processes through IPC. It is possible and advisable to run an independent message receiver per project within an IPC namespace, along with other services within the same project."
-msgstr ""
-
-#: ./doc/security-guide/ch038_transport-security.xml:145(para)
-msgid "Queue servers should only accept connections from the management network. This applies to all implementations. This should be implemented through configuration of services and optionally enforced through global network policy."
-msgstr ""
-
-#: ./doc/security-guide/ch038_transport-security.xml:146(para)
-msgid "When using ZeroMQ messaging, each project should run a separate ZeroMQ receiver process on a port dedicated to services belonging to that project. This is equivalent to the AMQP concept of control exchanges."
-msgstr ""
-
-#: ./doc/security-guide/ch038_transport-security.xml:150(para)
-msgid "The configuration for these processes should be restricted to those processes, not only by Directory Access Controls, but through Mandatory Access Controls. The goal of such restrictions is to prevent isolation from other processes running on the same machine(s)."
+#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:75(para)
+msgid "To provide secure ephemeral instance storage, Bob implements qcow2 files on an encrypted filesystems."
 msgstr ""
 
 #: ./doc/security-guide/ch044_case-studies-database.xml:8(title)
@@ -3072,348 +5782,6 @@ msgstr ""
 msgid "Bob is concerned about strong separation of his tenants' data, so he has elected to use the Postgres database , known for its stronger security features. The database resides on the Management network and uses SSL with mutual authentication with the services. Since the database is on the Management network, the database uses certificates signed with the company's self-signed root certificate. Bob creates separate user accounts for each database user, and configures the database to use both passwords and X.509 certificates for authentication. He elects not to use the <systemitem class=\"service\">nova-conductor</systemitem> sub-service due to a desire for fine-grained access control."
 msgstr ""
 
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch001_acknowledgements.xml:12(None) ./doc/security-guide/ch001_acknowledgements.xml:15(None)
-msgid "@@image: 'static/book-sprint-all-logos.png'; md5=f2d97c3130c32f31412f5af41ad72d39"
-msgstr ""
-
-#: ./doc/security-guide/ch001_acknowledgements.xml:7(title)
-msgid "Acknowledgments"
-msgstr ""
-
-#: ./doc/security-guide/ch001_acknowledgements.xml:8(para)
-msgid "The OpenStack Security Group would like to acknowledge contributions from the following organizations who were instrumental in making this book possible. These are:"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch033_securing-neutron-services.xml:40(None) ./doc/security-guide/ch033_securing-neutron-services.xml:45(None)
-msgid "@@image: 'static/1aa-logical-neutron-flow.png'; md5=3589a1ef10ea2bbe189ca90e3c932df2"
-msgstr ""
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml:8(title)
-msgid "Securing OpenStack Networking services"
-msgstr ""
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml:9(para)
-msgid "To secure OpenStack Networking, you must understand how the workflow process for tenant instance creation needs to be mapped to security domains."
-msgstr ""
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml:13(para)
-msgid "There are four main services that interact with OpenStack Networking. In a typical OpenStack deployment these services map to the following security domains:"
-msgstr ""
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml:18(para)
-msgid "OpenStack dashboard: Public and management"
-msgstr ""
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml:21(para)
-msgid "OpenStack Identity: Management"
-msgstr ""
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml:24(para)
-msgid "OpenStack compute node: Management and guest"
-msgstr ""
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml:27(para)
-msgid "OpenStack network node: Management, guest, and possibly public depending upon neutron-plugin in use."
-msgstr ""
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml:31(para)
-msgid "SDN services node: Management, guest and possibly public depending upon product used."
-msgstr ""
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml:49(para)
-msgid "To isolate sensitive data communication between the OpenStack Networking services and other OpenStack core services, configure these communication channels to only allow communication over an isolated management network."
-msgstr ""
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml:54(title)
-msgid "OpenStack Networking service configuration"
-msgstr ""
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml:56(title)
-msgid "Restrict bind address of the API server: neutron-server"
-msgstr ""
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml:57(para)
-msgid "To restrict the interface or IP address on which the OpenStack Networking API service binds a network socket for incoming client connections, specify the bind_host and bind_port in the neutron.conf file as shown:"
-msgstr ""
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml:64(replaceable)
-msgid "IP ADDRESS OF SERVER"
-msgstr ""
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml:70(title)
-msgid "Restrict DB and RPC communication of the OpenStack Networking services"
-msgstr ""
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml:72(para)
-msgid "Various components of the OpenStack Networking services use either the messaging queue or database connections to communicate with other components in OpenStack Networking."
-msgstr ""
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml:77(para)
-msgid "It is recommended that you follow the guidelines provided in the Database Authentication and Access Control chapter in the Database section for all components that require direct DB connections."
-msgstr ""
-
-#: ./doc/security-guide/ch033_securing-neutron-services.xml:82(para)
-msgid "It is recommended that you follow the guidelines provided in the Queue Authentication and Access Control chapter in the Messaging section for all components that require RPC communication."
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch004_book-introduction.xml:113(None) ./doc/security-guide/ch004_book-introduction.xml:118(None)
-msgid "@@image: 'static/marketecture-diagram.png'; md5=4ab13a64f80c210be3120abc5c7aee8a"
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:8(title)
-msgid "Introduction to OpenStack"
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:9(para)
-msgid "This guide provides security insight into OpenStack deployments. The intended audience is cloud architects, deployers, and administrators. In addition, cloud users will find the guide both educational and helpful in provider selection, while auditors will find it useful as a reference document to support their compliance certification efforts. This guide is also recommended for anyone interested in cloud security."
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:16(para)
-msgid "Each OpenStack deployment embraces a wide variety of technologies, spanning Linux distributions, database systems, messaging queues, OpenStack components themselves, access control policies, logging services, security monitoring tools, and much more. It should come as no surprise that the security issues involved are equally diverse, and their in-depth analysis would require several guides. We strive to find a balance, providing enough context to understand OpenStack security issues and their handling, and provide external references for further information. The guide could be read from start to finish or sampled as necessary like a reference."
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:27(para)
-msgid "We briefly introduce the kinds of clouds: private, public, and hybrid before presenting an overview of the OpenStack components and their related security concerns in the remainder of the chapter."
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:32(title)
-msgid "Cloud types"
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:33(para)
-msgid "OpenStack is a key enabler in adoption of cloud technology and has several common deployment use cases. These are commonly known as Public, Private, and Hybrid models. The following sections use the National Institute of Standards and Technology (NIST) <link href=\"http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf\">definition of cloud</link> to introduce these different types of cloud as they apply to OpenStack."
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:42(title)
-msgid "Public cloud"
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:43(para)
-msgid "According to NIST, a public cloud is one in which the infrastructure is open to the general public for consumption. OpenStack public clouds are typically run by a service provider and can be consumed by individuals, corporations, or any paying customer. A public cloud provider may expose a full set of features such as software-defined networking, block storage, in addition to multiple instance types. Due to the nature of public clouds, they are exposed to a higher degree of risk. As a consumer of a public cloud you should validate that your selected provider has the necessary certifications, attestations, and other regulatory considerations. As a public cloud provider, depending on your target customers, you may be subject to one or more regulations. Additionally, even if not required to meet regulatory requirements, a provider should ensure tenant isolation as well as protecting management infrastructure from external attacks."
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:61(title)
-msgid "Private cloud"
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:62(para)
-msgid "At the opposite end of the spectrum is the private cloud. As NIST defines it, a private cloud is provisioned for exclusive use by a single organization comprising multiple consumers, such as business units. It may be owned, managed, and operated by the organization, a third-party, or some combination of them, and it may exist on or off premises. Private cloud use cases are diverse, as such, their individual security concerns vary."
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:72(title)
-msgid "Community cloud"
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:73(para)
-msgid "NIST defines a community cloud as one whose infrastructure is provisioned for the exclusive use by a specific community of consumers from organizations that have shared concerns. For example, mission, security requirements, policy, and compliance considerations. It may be owned, managed, and operated by one or more of the organizations in the community, a third-party, or some combination of them, and it may exist on or off premises."
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:83(title)
-msgid "Hybrid cloud"
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:84(para)
-msgid "A hybrid cloud is defined by NIST as a composition of two or more distinct cloud infrastructures, such as private, community, or public, that remain unique entities, but are bound together by standardized or proprietary technology that enables data and application portability, such as cloud bursting for load balancing between clouds. For example an online retailer may have their advertising and catalogue presented on a public cloud that allows for elastic provisioning. This would enable them to handle seasonal loads in a flexible, cost-effective fashion. Once a customer begins to process their order, they are transferred to the more secure private cloud backend that is PCI compliant."
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:96(para)
-msgid "For the purposes of this document, we treat Community and Hybrid similarly, dealing explicitly only with the extremes of Public and Private clouds from a security perspective. Your security measures depend where your deployment falls upon the private public continuum."
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:104(title)
-msgid "OpenStack service overview"
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:105(para)
-msgid "OpenStack embraces a modular architecture to provide a set of core services that facilitates scalability and elasticity as core design tenets. This chapter briefly reviews OpenStack components, their use cases and security considerations."
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:123(para)
-msgid "OpenStack Compute service (nova) provides services to support the management of virtual machine instances at scale, instances that host multi-tiered applications, dev/test environments, \"Big Data\" crunching Hadoop clusters, and/or high performance computing."
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:128(para)
-msgid "The Compute service facilitates this management through an abstraction layer that interfaces with supported hypervisors, which we address later on in more detail."
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:131(para)
-msgid "Later in the guide, we focus generically on the virtualization stack as it relates to hypervisors."
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:133(para)
-msgid "For information about the current state of feature support, see <link href=\"https://wiki.openstack.org/wiki/HypervisorSupportMatrix\">OpenStack Hypervisor Support Matrix</link>."
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:137(para)
-msgid "The security of Compute is critical for an OpenStack deployment. Hardening techniques should include support for strong instance isolation, secure communication between Compute sub-components, and resiliency of public-facing <glossterm>API</glossterm> endpoints."
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:144(title) ./doc/security-guide/ch027_storage.xml:8(title)
-msgid "Object Storage"
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:145(para)
-msgid "The OpenStack Object Storage service (swift) provides support for storing and retrieving arbitrary data in the cloud. The Object Storage service provides both a native API and an Amazon Web Services S3 compatible API. The service provides a high degree of resiliency through data replication and can handle petabytes of data."
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:151(para)
-msgid "It is important to understand that object storage differs from traditional file system storage. It is best used for static data such as media files (MP3s, images, videos), virtual machine images, and backup files."
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:155(para)
-msgid "Object security should focus on access control and encryption of data in transit and at rest. Other concerns may relate to system abuse, illegal or malicious content storage, and cross authentication attack vectors."
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:161(title)
-msgid "Block Storage"
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:162(para)
-msgid "The OpenStack Block Storage service (cinder) provides persistent block storage for compute instances. The Block Storage service is responsible for managing the life-cycle of block devices, from the creation and attachment of volumes to instances, to their release."
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:167(para)
-msgid "Security considerations for block storage are similar to that of object storage."
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:171(title)
-msgid "OpenStack Networking"
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:172(para)
-msgid "The OpenStack Networking service (neutron, previously called quantum) provides various networking services to cloud users (tenants) such as IP address management, <glossterm>DNS</glossterm>, <glossterm>DHCP</glossterm>, load balancing, and security groups (network access rules, like firewall policies). It provides a framework for software defined networking (SDN) that allows for pluggable integration with various networking solutions."
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:180(para)
-msgid "OpenStack Networking allows cloud tenants to manage their guest network configurations. Security concerns with the networking service include network traffic isolation, availability, integrity and confidentiality."
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:187(para)
-msgid "The OpenStack dashboard (horizon) provides a web-based interface for both cloud administrators and cloud tenants. Through this interface administrators and tenants can provision, manage, and monitor cloud resources. Horizon is commonly deployed in a public facing manner with all the usual security concerns of public web portals."
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:195(title)
-msgid "Identity service"
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:196(para)
-msgid "The OpenStack Identity service (keystone) is a <emphasis role=\"bold\">shared service</emphasis> that provides authentication and authorization services throughout the entire cloud infrastructure. The Identity service has pluggable support for multiple forms of authentication."
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:201(para)
-msgid "Security concerns here pertain to trust in authentication, management of authorization tokens, and secure communication."
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:206(title)
-msgid "Image Service"
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:207(para)
-msgid "The OpenStack Image Service (glance) provides disk image management services. The Image Service provides image discovery, registration, and delivery services to the Compute service, as needed."
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:211(para)
-msgid "Trusted processes for managing the life cycle of disk images are required, as are all the previously mentioned issues with respect to data security."
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:216(title)
-msgid "Other supporting technology"
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:217(para)
-msgid "OpenStack relies on messaging for internal communication between several of its services. By default, OpenStack uses message queues based on the Advanced Message Queue Protocol (<glossterm baseform=\"Advanced Message Queuing Protocol (AMQP)\">AMQP </glossterm>). Similar to most OpenStack services, it supports pluggable components. Today the implementation backend could be <glossterm>RabbitMQ</glossterm>, <glossterm>Qpid</glossterm>, or <glossterm>ZeroMQ</glossterm>."
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:226(para)
-msgid "As most management commands flow through the message queueing system, it is a primary security concern for any OpenStack deployment. Message queueing security is discussed in detail later in this guide."
-msgstr ""
-
-#: ./doc/security-guide/ch004_book-introduction.xml:230(para)
-msgid "Several of the components use databases though it is not explicitly called out. Securing the access to the databases and their contents is yet another security concern, and consequently discussed in more detail later in this guide."
-msgstr ""
-
-#: ./doc/security-guide/ch063_compliance-activities.xml:8(title)
-msgid "Compliance activities"
-msgstr ""
-
-#: ./doc/security-guide/ch063_compliance-activities.xml:9(para)
-msgid "There are a number of standard activities that will greatly assist with the compliance process. In this chapter we outline some of the most common compliance activities. These are not specific to OpenStack, however we provide references to relevant sections in this book as useful context."
-msgstr ""
-
-#: ./doc/security-guide/ch063_compliance-activities.xml:11(title)
-msgid "Information Security Management system (ISMS)"
-msgstr ""
-
-#: ./doc/security-guide/ch063_compliance-activities.xml:12(para)
-msgid "An Information Security Management System (ISMS) is a comprehensive set of policies and processes that an organization creates and maintains to manage risk to information assets. The most common ISMS for cloud deployments is <link href=\"http://www.27000.org/iso-27001.htm\">ISO/IEC 27001/2</link>, which creates a solid foundation of security controls and practices for achieving more stringent compliance certifications."
-msgstr ""
-
-#: ./doc/security-guide/ch063_compliance-activities.xml:15(title)
-msgid "Risk assessment"
-msgstr ""
-
-#: ./doc/security-guide/ch063_compliance-activities.xml:16(para)
-msgid "A risk assessment framework identifies risks within an organization or service, and specifies ownership of these risks, along with implementation and mitigation strategies. Risks apply to all areas of the service, from technical controls to environmental disaster scenarios and human elements, for example a malicious insider (or rogue employee). Risks can be rated using a variety of mechanisms, for example likelihood vs impact. An OpenStack deployment risk assessment can include control gaps that are described in this book."
-msgstr ""
-
-#: ./doc/security-guide/ch063_compliance-activities.xml:19(title)
-msgid "Access and log reviews"
-msgstr ""
-
-#: ./doc/security-guide/ch063_compliance-activities.xml:20(para)
-msgid "Periodic access and log reviews are required to ensure authentication, authorization, and accountability in a service deployment. Specific guidance for OpenStack on these topics are discussed in-depth in the logging section."
-msgstr ""
-
-#: ./doc/security-guide/ch063_compliance-activities.xml:23(title)
-msgid "Backup and disaster recovery"
-msgstr ""
-
-#: ./doc/security-guide/ch063_compliance-activities.xml:24(para)
-msgid "Disaster Recovery (DR) and Business Continuity Planning (BCP) plans are common requirements for ISMS and compliance activities. These plans must be periodically tested as well as documented. In OpenStack key areas are found in the management security domain, and anywhere that single points of failure (SPOFs) can be identified. See the section on secure backup and recovery for additional details."
-msgstr ""
-
-#: ./doc/security-guide/ch063_compliance-activities.xml:27(title)
-msgid "Security training"
-msgstr ""
-
-#: ./doc/security-guide/ch063_compliance-activities.xml:28(para)
-msgid "Annual, role-specific, security training is a mandatory requirement for almost all compliance certifications and attestations. To optimise the effectiveness of security training, a common method is to provide role specific training, for example to developers, operational personnel, and non-technical employees. Additional cloud security or OpenStack security training based on this hardening guide would be ideal."
-msgstr ""
-
-#: ./doc/security-guide/ch063_compliance-activities.xml:31(title)
-msgid "Security reviews"
-msgstr ""
-
-#: ./doc/security-guide/ch063_compliance-activities.xml:32(para)
-msgid "As OpenStack is a popular open source project, much of the codebase and architecture has been scrutinized by individual contributors, organizations and enterprises. This can be advantageous from a security perspective, however the need for security reviews is still a critical consideration for service providers, as deployments vary, and security is not always the primary concern for contributors. A comprehensive security review process may include architectural review, threat modelling, source code analysis and penetration testing. There are many techniques and recommendations for conducting security reviews that can be found publicly posted. A well-tested example is the <link href=\"http://www.microsoft.com/security/sdl/process/release.aspx\">Microsoft SDL</link>, created as part of the Microsoft Trustworthy Computing Initiative."
-msgstr ""
-
-#: ./doc/security-guide/ch063_compliance-activities.xml:49(para)
-msgid "Security updates are critical to any IaaS deployment, whether private or public. Vulnerable systems expand attack surfaces, and are obvious targets for attackers. Common scanning technologies and vulnerability notification services can help mitigate this threat. It is important that scans are authenticated and that mitigation strategies extend beyond simple perimeter hardening. Multi-tenant architectures such as OpenStack are particularly prone to hypervisor vulnerabilities, making this a critical part of the system for vulnerability management. See the section on instance isolation for additional details."
-msgstr ""
-
-#: ./doc/security-guide/ch063_compliance-activities.xml:52(title)
-msgid "Data classification"
-msgstr ""
-
-#: ./doc/security-guide/ch063_compliance-activities.xml:53(para)
-msgid "Data Classification defines a method for classifying and handling information, often to protect customer information from accidental or deliberate theft, loss, or inappropriate disclosure. Most commonly this involves classifying information as sensitive or non-sensitive, or as personally identifiable information (PII). Depending on the context of the deployment various other classifying criteria may be used (government, health-care etc). The underlying principle is that data classifications are clearly defined and in-use. The most common protective mechanisms include industry standard encryption technologies. See the data security section for additional details."
-msgstr ""
-
-#: ./doc/security-guide/ch063_compliance-activities.xml:56(title)
-msgid "Exception process"
-msgstr ""
-
-#: ./doc/security-guide/ch063_compliance-activities.xml:57(para)
-msgid "An exception process is an important component of an ISMS. When certain actions are not compliant with security policies that an organization has defined, they must be logged. Appropriate justification, description and mitigation details need to be included, and signed off by appropriate authorities. OpenStack default configurations may vary in meeting various compliance criteria, areas that fail to meet compliance requirements should be logged, with potential fixes considered for contribution to the community."
-msgstr ""
-
 #. When image changes, this message will be marked fuzzy or untranslated for you.
 #. It doesn't matter what you translate it to: it's not used at all.
 #: ./doc/security-guide/ch027_storage.xml:53(None)
@@ -3718,2376 +6086,8 @@ msgstr ""
 msgid "This value should be initially set with a cryptographically secure random number generator and consistent across all service nodes. Ensure that it is protected with proper ACLs and that you have a backup copy to avoid data loss."
 msgstr ""
 
-#: ./doc/security-guide/ch006_introduction-to-case-studies.xml:8(title)
-msgid "Introduction to case studies"
-msgstr ""
-
-#: ./doc/security-guide/ch006_introduction-to-case-studies.xml:9(para)
-msgid "This guide refers to two running case studies, which are introduced here and referred to at the end of each chapter."
-msgstr ""
-
-#: ./doc/security-guide/ch006_introduction-to-case-studies.xml:12(title)
-msgid "Case study: Alice, the private cloud builder"
-msgstr ""
-
-#: ./doc/security-guide/ch006_introduction-to-case-studies.xml:13(para)
-msgid "Alice deploys a private cloud for use by a government department in the US. The cloud must comply with relevant standards, such as FedRAMP. The security paperwork requirements for this cloud are very high. It must have no direct access to the internet: its API endpoints, compute instances, and other resources must be exposed to only systems within the department's network, which is entirely air-gapped from all other networks. The cloud can access other network services on the organization's intranet such as the authentication and logging services."
-msgstr ""
-
-#: ./doc/security-guide/ch006_introduction-to-case-studies.xml:25(title)
-msgid "Case study: Bob, the public cloud provider"
-msgstr ""
-
-#: ./doc/security-guide/ch006_introduction-to-case-studies.xml:26(para)
-msgid "Bob is a lead architect for a company that deploys a large greenfield public cloud. This cloud provides IaaS for the masses and enables any consumer with a valid credit card access to utility computing and storage, but the primary focus is enterprise customers. Data privacy concerns are a big priority for Bob as they are seen as a major barrier to large-scale adoption of the cloud by organizations."
-msgstr ""
-
-#: ./doc/security-guide/ch030_state-of-networking.xml:8(title)
-msgid "State of networking"
-msgstr ""
-
-#: ./doc/security-guide/ch030_state-of-networking.xml:9(para)
-msgid "OpenStack Networking in the Grizzly release enables the end-user or tenant to define, utilize, and consume networking resources in new ways that had not been possible in previous OpenStack Networking releases. OpenStack Networking provides a tenant-facing API for defining network connectivity and IP addressing for instances in the cloud in addition to orchestrating the network configuration. With the transition to an API-centric networking service, cloud architects and administrators should take into consideration best practices to secure physical and virtual network infrastructure and services."
-msgstr ""
-
-#: ./doc/security-guide/ch030_state-of-networking.xml:10(para)
-msgid "OpenStack Networking was designed with a plug-in architecture that provides extensibility of the API through open source community or third-party services. As you evaluate your architectural design requirements, it is important to determine what features are available in OpenStack Networking core services, any additional services that are provided by third-party products, and what supplemental services are required to be implemented in the physical infrastructure."
-msgstr ""
-
-#: ./doc/security-guide/ch030_state-of-networking.xml:20(para)
-msgid "This section is a high-level overview of what processes and best practices should be considered when implementing OpenStack Networking. We will talk about the current state of services that are available, what future services will be implemented, and the current limitations in this project."
-msgstr ""
-
-#: ./doc/security-guide/ch043_database-transport-security.xml:8(title)
-msgid "Database transport security"
-msgstr ""
-
-#: ./doc/security-guide/ch043_database-transport-security.xml:9(para)
-msgid "This chapter covers issues related to network communications to and from the database server. This includes IP address bindings and encrypting network traffic with SSL."
-msgstr ""
-
-#: ./doc/security-guide/ch043_database-transport-security.xml:14(title)
-msgid "Database server IP address binding"
-msgstr ""
-
-#: ./doc/security-guide/ch043_database-transport-security.xml:15(para)
-msgid "To isolate sensitive database communications between the services and the database, we strongly recommend that the database server(s) be configured to only allow communications to and from the database over an isolated management network. This is achieved by restricting the interface or IP address on which the database server binds a network socket for incoming client connections."
-msgstr ""
-
-#: ./doc/security-guide/ch043_database-transport-security.xml:24(title)
-msgid "Restricting bind address for MySQL"
-msgstr ""
-
-#: ./doc/security-guide/ch043_database-transport-security.xml:25(para) ./doc/security-guide/ch043_database-transport-security.xml:63(para)
-msgid "In <filename>my.cnf</filename>:"
-msgstr ""
-
-#: ./doc/security-guide/ch043_database-transport-security.xml:31(title)
-msgid "Restricting listen address for PostgreSQL"
-msgstr ""
-
-#: ./doc/security-guide/ch043_database-transport-security.xml:32(para)
-msgid "In <filename>postgresql.conf</filename>:"
-msgstr ""
-
-#: ./doc/security-guide/ch043_database-transport-security.xml:37(title)
-msgid "Database transport"
-msgstr ""
-
-#: ./doc/security-guide/ch043_database-transport-security.xml:38(para)
-msgid "In addition to restricting database communications to the management network, we also strongly recommend that the cloud administrator configure their database backend to require SSL. Using SSL for the database client connections protects the communications from tampering and eavesdropping. As will be discussed in the next section, using SSL also provides the framework for doing database user authentication through X.509 certificates (commonly referred to as PKI). Below is guidance on how SSL is typically configured for the two popular database backends MySQL and PostgreSQL."
-msgstr ""
-
-#: ./doc/security-guide/ch043_database-transport-security.xml:50(para)
-msgid "When installing the certificate and key files, ensure that the file permissions are restricted, for example <placeholder-1/>, and the ownership is restricted to the database daemon user to prevent unauthorized access by other processes and users on the database server."
-msgstr ""
-
-#: ./doc/security-guide/ch043_database-transport-security.xml:60(title)
-msgid "MySQL SSL configuration"
-msgstr ""
-
-#: ./doc/security-guide/ch043_database-transport-security.xml:61(para)
-msgid "The following lines should be added in the system-wide MySQL configuration file:"
-msgstr ""
-
-#: ./doc/security-guide/ch043_database-transport-security.xml:69(para) ./doc/security-guide/ch043_database-transport-security.xml:80(para)
-msgid "Optionally, if you wish to restrict the set of SSL ciphers used for the encrypted connection. See <link href=\"http://www.openssl.org/docs/apps/ciphers.html\">http://www.openssl.org/docs/apps/ciphers.html</link> for a list of ciphers and the syntax for specifying the cipher string:"
-msgstr ""
-
-#: ./doc/security-guide/ch043_database-transport-security.xml:74(title)
-msgid "PostgreSQL SSL configuration"
-msgstr ""
-
-#: ./doc/security-guide/ch043_database-transport-security.xml:75(para)
-msgid "The following lines should be added in the system-wide PostgreSQL configuration file, <filename>postgresql.conf</filename>."
-msgstr ""
-
-#: ./doc/security-guide/ch043_database-transport-security.xml:82(para)
-msgid "The server certificate, key, and certificate authority (CA) files should be placed in the $PGDATA directory in the following files:"
-msgstr ""
-
-#: ./doc/security-guide/ch043_database-transport-security.xml:86(para)
-msgid "<filename>$PGDATA/server.crt</filename> - Server certificate"
-msgstr ""
-
-#: ./doc/security-guide/ch043_database-transport-security.xml:90(para)
-msgid "<filename>$PGDATA/server.key</filename> - Private key corresponding to <filename>server.crt</filename>"
-msgstr ""
-
-#: ./doc/security-guide/ch043_database-transport-security.xml:94(para)
-msgid "<filename>$PGDATA/root.crt</filename> - Trusted certificate authorities"
-msgstr ""
-
-#: ./doc/security-guide/ch043_database-transport-security.xml:98(para)
-msgid "<filename>$PGDATA/root.crl</filename> - Certificate revocation list"
-msgstr ""
-
-#: ./doc/security-guide/ch048_key-management.xml:8(title)
-msgid "Key management"
-msgstr ""
-
-#: ./doc/security-guide/ch048_key-management.xml:9(para)
-msgid "To address the often mentioned concern of tenant data privacy and limiting cloud provider liability, there is greater interest within the OpenStack community to make data encryption more ubiquitous. It is relatively easy for an end-user to encrypt their data prior to saving it to the cloud, and this is a viable path for tenant objects such as media files, database archives among others. However, when client side encryption is used for virtual machine images, block storage etc, client intervention is necessary in the form of presenting keys to unlock the data for further use. To seamlessly secure the data and yet have it accessible without burdening the client with having to manage their keys and interactively provide them calls for a key management service within OpenStack. Providing encryption and key management services as part of OpenStack eases data-at-rest security adoption, addresses customer concerns about the privacy and misuse of their data with the added advantage of limiting cloud provider liability. Provider liability is of concern in multi-tenant public clouds with respect to handing over tenant data during a misuse investigation."
-msgstr ""
-
-#: ./doc/security-guide/ch048_key-management.xml:10(para)
-msgid "A key management service is in the early stages of being developed and has a way to go before becoming an official component of OpenStack. Refer to <link href=\"https://github.com/cloudkeep/barbican/wiki/_pages\">https://github.com/cloudkeep/barbican/wiki/_pages</link> for details."
-msgstr ""
-
-#: ./doc/security-guide/ch048_key-management.xml:11(para)
-msgid "It shall support the creation of keys, and their secure saving (with a service master-key). Some of the design questions still being debated are how much of the Key Management Interchange Protocol (KMIP) to support, key formats, and certificate management. The key manager will be pluggable to facilitate deployments that need a third-party Hardware Security Module (HSM)."
-msgstr ""
-
-#: ./doc/security-guide/ch048_key-management.xml:12(para)
-msgid "OpenStack Block Storage, cinder, is the first service looking to integrate with the key manager to provide volume encryption."
-msgstr ""
-
-#: ./doc/security-guide/ch048_key-management.xml:14(title)
-msgid "References:"
-msgstr ""
-
-#: ./doc/security-guide/ch048_key-management.xml:16(link)
-msgid "Barbican"
-msgstr ""
-
-#: ./doc/security-guide/ch048_key-management.xml:19(link)
-msgid "KMIP"
-msgstr ""
-
-#: ./doc/security-guide/ch009_case-studies.xml:8(title)
-msgid "Case studies: system documentation"
-msgstr ""
-
-#: ./doc/security-guide/ch009_case-studies.xml:9(para)
-msgid "In this case study we discuss how Alice and Bob would address their system documentation requirements. The documentation suggested above includes hardware and software records, network diagrams, and system configuration details."
-msgstr ""
-
-#: ./doc/security-guide/ch009_case-studies.xml:12(para)
-msgid "Alice needs detailed documentation to satisfy FedRamp requirements. She sets up a configuration management database (CMDB) to store information regarding all of the hardware, firmware, and software versions used throughout the cloud. She also creates a network diagram detailing the cloud architecture, paying careful attention to the security domains and the services that span multiple security domains."
-msgstr ""
-
-#: ./doc/security-guide/ch009_case-studies.xml:13(para)
-msgid "Alice also needs to record each network service running in the cloud, what interfaces and ports it binds to, the security domains for each service, and why the service is needed. Alice decides to build automated tools to log into each system in the cloud over secure shell (SSH) using the <link href=\"http://fabfile.org\">Python Fabric library</link>. The tools collect and store the information in the CMDB, which simplifies the audit process."
-msgstr ""
-
-#: ./doc/security-guide/ch009_case-studies.xml:17(para)
-msgid "In this case, Bob will approach these steps the same as Alice."
-msgstr ""
-
-#: ./doc/security-guide/ch056_case-studies-instance-management.xml:8(title)
-msgid "Case studies: instance management"
-msgstr ""
-
-#: ./doc/security-guide/ch056_case-studies-instance-management.xml:9(para)
-msgid "In this case study we discuss how Alice and Bob would architect their clouds with respect to instance entropy, scheduling instances, trusted images, and instance migrations."
-msgstr ""
-
-#: ./doc/security-guide/ch056_case-studies-instance-management.xml:12(para)
-msgid "Alice has a need for lots of high quality entropy in the instances. For this reason, she decides to purchase hardware with Intel Ivy Bridge chip sets that support the RdRand instruction on each compute node. Using the entropy gathering daemon (EGD) and LibVirt's EGD support, Alice ensures that this entropy pool is distributed to the instances on each compute node."
-msgstr ""
-
-#: ./doc/security-guide/ch056_case-studies-instance-management.xml:13(para)
-msgid "For instance scheduling, Alice uses the trusted compute pools to ensure that all cloud workloads are deployed to nodes that presented a proper boot time attestation. Alice decides to disable user permissions for image uploading to help ensure that the images used in the cloud are generated in a known and trusted manner by the cloud administrators."
-msgstr ""
-
-#: ./doc/security-guide/ch056_case-studies-instance-management.xml:14(para)
-msgid "Finally, Alice disables instance migrations as this feature is less critical for the high performance application workloads expected to run in this cloud. This helps avoid the various security concerns related to instance migrations."
-msgstr ""
-
-#: ./doc/security-guide/ch056_case-studies-instance-management.xml:18(para)
-msgid "Bob is aware that entropy will be a concern for some of his customers, such as those in the financial industry. However, due to the added cost and complexity, Bob has decided to forgo integrating hardware entropy into the first iteration of his cloud. He adds hardware entropy as a fast-follow to do for a later improvement for the second generation of his cloud architecture."
-msgstr ""
-
-#: ./doc/security-guide/ch056_case-studies-instance-management.xml:19(para)
-msgid "Bob is interested in ensuring that customers receive a high quality of service. He is concerned that providing too much explicit user control over instance scheduling could negatively impact the quality of service. So he disables this feature. Bob provides images in the cloud from a known trusted source for users to use. Additionally, he also allows users to upload their own images. However, users cannot generally share their images. This helps prevent a user from sharing a malicious image, which could negatively impact the security of other users in the cloud."
-msgstr ""
-
-#: ./doc/security-guide/ch056_case-studies-instance-management.xml:20(para)
-msgid "For migrations, Bob wants to enable secure instance migrations in order to support rolling upgrades with minimal user downtime. Bob ensures that all migrations occur on an isolated VLAN. He plans to defer implementing encrypted migrations until this is better supported in <placeholder-1/> client tools. However, he makes a note to track this carefully and switch to encrypted migrations as soon as possible."
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch008_system-roles-types.xml:101(None) ./doc/security-guide/ch008_system-roles-types.xml:106(None)
-msgid "@@image: 'static/services-protocols-ports.png'; md5=fb1e9f47d969127b7a5ca683d38cfe20"
-msgstr ""
-
-#: ./doc/security-guide/ch008_system-roles-types.xml:8(title)
-msgid "System documentation requirements"
-msgstr ""
-
-#: ./doc/security-guide/ch008_system-roles-types.xml:9(para)
-msgid "The system documentation for an OpenStack cloud deployment should follow the templates and best practices for the Enterprise Information Technology System in your organization. Organizations often have compliance requirements which may require an overall System Security Plan to inventory and document the architecture of a given system. There are common challenges across the industry related to documenting the dynamic cloud infrastructure and keeping the information up-to-date."
-msgstr ""
-
-#: ./doc/security-guide/ch008_system-roles-types.xml:18(title)
-msgid "System roles and types"
-msgstr ""
-
-#: ./doc/security-guide/ch008_system-roles-types.xml:19(para)
-msgid "The two broadly defined types of nodes that generally make up an OpenStack installation are:"
-msgstr ""
-
-#: ./doc/security-guide/ch008_system-roles-types.xml:23(para)
-msgid "Infrastructure nodes. The nodes that run the cloud related services such as the OpenStack Identity Service, the message queuing service, storage, networking, and other services required to support the operation of the cloud."
-msgstr ""
-
-#: ./doc/security-guide/ch008_system-roles-types.xml:30(para)
-msgid "Compute, storage, or other resource nodes. Provide storage capacity or virtual machines for your cloud."
-msgstr ""
-
-#: ./doc/security-guide/ch008_system-roles-types.xml:37(title)
-msgid "System inventory"
-msgstr ""
-
-#: ./doc/security-guide/ch008_system-roles-types.xml:38(para)
-msgid "Documentation should provide a general description of the OpenStack environment and cover all systems used (production, development, test, etc.). Documenting system components, networks, services, and software often provides the bird's-eye view needed to thoroughly cover and consider security concerns, attack vectors and possible security domain bridging points. A system inventory may need to capture ephemeral resources such as virtual machines or virtual disk volumes that would otherwise be persistent resources in a traditional IT system."
-msgstr ""
-
-#: ./doc/security-guide/ch008_system-roles-types.xml:48(title)
-msgid "Hardware inventory"
-msgstr ""
-
-#: ./doc/security-guide/ch008_system-roles-types.xml:49(para)
-msgid "Clouds without stringent compliance requirements for written documentation might benefit from having a Configuration Management Database (<glossterm>CMDB</glossterm>). CMDBs are normally used for hardware asset tracking and overall life-cycle management. By leveraging a CMDB, an organization can quickly identify cloud infrastructure hardware. For example, compute nodes, storage nodes, and network devices that exist on the network but that might not be adequately protected and/or forgotten. OpenStack provisioning system might provide some CMDB-like functions especially if auto-discovery features of hardware attributes are available."
-msgstr ""
-
-#: ./doc/security-guide/ch008_system-roles-types.xml:63(title)
-msgid "Software inventory"
-msgstr ""
-
-#: ./doc/security-guide/ch008_system-roles-types.xml:64(para)
-msgid "Just as with hardware, all software components within the OpenStack deployment should be documented. Components here should include system databases; OpenStack software components and supporting sub-components; and, supporting infrastructure software such as load-balancers, reverse proxies, and network address translators. Having an authoritative list like this may be critical toward understanding total system impact due to a compromise or vulnerability of a specific class of software."
-msgstr ""
-
-#: ./doc/security-guide/ch008_system-roles-types.xml:76(title)
-msgid "Network topology"
-msgstr ""
-
-#: ./doc/security-guide/ch008_system-roles-types.xml:77(para)
-msgid "A network topology should be provided with highlights specifically calling out the data flows and bridging points between the security domains. Network ingress and egress points should be identified along with any OpenStack logical system boundaries. Multiple diagrams may be needed to provide complete visual coverage of the system. A network topology document should include virtual networks created on behalf of tenants by the system along with virtual machine instances and gateways created by OpenStack."
-msgstr ""
-
-#: ./doc/security-guide/ch008_system-roles-types.xml:88(title)
-msgid "Services, protocols and ports"
-msgstr ""
-
-#: ./doc/security-guide/ch008_system-roles-types.xml:89(para)
-msgid "The service, protocols and ports table provides important additional detail of an OpenStack deployment. A table view of all services running within the cloud infrastructure can immediately inform, guide, and help check security procedures. Firewall configuration, service port conflicts, security remediation areas, and compliance requirements become easier to manage when you have concise information available. Consider the following table:"
-msgstr ""
-
-#: ./doc/security-guide/ch008_system-roles-types.xml:109(para)
-msgid "Referencing a table of services, protocols and ports can help in understanding the relationship between OpenStack components. It is highly recommended that OpenStack deployments have information similar to this on record."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:9(para)
-msgid "Horizon is the OpenStack dashboard that provides users a self-service portal to provision their own resources within the limits set by administrators. These include provisioning users, defining instance flavors, uploading VM images, managing networks, setting up security groups, starting instances, and accessing the instances through a console."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:14(para)
-msgid "The dashboard is based on the Django web framework, therefore secure deployment practices for Django apply directly to horizon. This guide provides a popular set of Django security recommendations, further information can be found by reading the <link href=\"https://docs.djangoproject.com/en/1.5/#security\">Django deployment and security documentation</link>."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:21(para)
-msgid "The dashboard ships with reasonable default security settings, and has good <link href=\"http://docs.openstack.org/developer/horizon/topics/deployment.html\">deployment and configuration documentation</link>."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:26(title)
-msgid "Basic web server configuration"
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:27(para)
-msgid "The dashboard should be deployed as a Web Services Gateway Interface (WSGI) application behind an HTTPS proxy such as Apache or nginx. If Apache is not already in use, we recommend nginx since it is lighter weight and easier to configure correctly."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:32(para)
-msgid "When using nginx, we recommend <link href=\"http://docs.gunicorn.org/en/latest/deploy.html\">gunicorn</link> as the wsgi host with an appropriate number of synchronous workers. We strongly advise against deployments using fastcgi, scgi, or uWSGI. We strongly advise against the use of synthetic performance benchmarks when choosing a wsgi server."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:39(para)
-msgid "When using Apache, we recommend <link href=\"https://docs.djangoproject.com/en/1.5/howto/deployment/wsgi/modwsgi/\">mod_wsgi</link> to host dashboard."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:44(title)
-msgid "HTTPS"
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:45(para)
-msgid "Deploy the dashboard behind a secure <glossterm>HTTPS</glossterm> server by using a valid, trusted certificate from a recognized certificate authority (CA). Private organization-issued certificates are only appropriate when the root of trust is pre-installed in all user browsers."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:52(para)
-msgid "Configure HTTP requests to the dashboard domain to redirect to the fully qualified HTTPS URL."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:56(title)
-msgid "HTTP Strict Transport Security (HSTS)"
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:57(para)
-msgid "It is highly recommended to use HTTP Strict Transport Security (HSTS)."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:60(para)
-msgid "If you are using an HTTPS proxy in front of your web server, rather than using an HTTP server with HTTPS functionality, follow the <link href=\"https://docs.djangoproject.com/en/1.5/ref/settings/#secure-proxy-ssl-header\">Django documentation on modifying the SECURE_PROXY_SSL_HEADER variable</link>."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:67(para)
-msgid "See the chapter on PKI/SSL Everywhere for more specific recommendations and server configurations for HTTPS configurations, including the configuration of HSTS."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:72(title)
-msgid "Front end caching"
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:73(para)
-msgid "Since dashboard is rendering dynamic content passed directly from OpenStack API requests, we do not recommend front end caching layers such as varnish. In Django, static media is directly served from Apache or nginx and already benefits from web host caching."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:80(title)
-msgid "Domain names"
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:81(para)
-msgid "Many organizations typically deploy web applications at subdomains of an overarching organization domain. It is natural for users to expect a domain of the form <uri>openstack.example.org</uri>. In this context, there are often many other applications deployed in the same second-level namespace, often serving user-controlled content. This name structure is convenient and simplifies name server maintenance."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:89(para)
-msgid "We strongly recommend deploying horizon to a <emphasis>second-level domain</emphasis>, such as <uri>https://example.com</uri>, and advise against deploying horizon on a <emphasis>shared subdomain</emphasis> of any level, for example <uri>https://openstack.example.org</uri> or <uri>https://horizon.openstack.example.org</uri>. We also advise against deploying to bare internal domains like <uri>https://horizon/</uri>."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:97(para)
-msgid "This recommendation is based on the limitations browser same-origin-policy. The recommendations in this guide cannot effectively protect users against known attacks if dashboard is deployed on a domain which also hosts user-generated content, such as scripts, images, or uploads of any kind, even if the user-generated content is on a different subdomain. This approach is used by most major web presences, such as googleusercontent.com, fbcdn.com, github.io, and twimg.com, to ensure that user generated content stays separate from cookies and security tokens."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:107(para)
-msgid "Additionally, if you decline to follow this recommendation above about second-level domains, it is vital that you avoid the cookie backed session store and employ HTTP Strict Transport Security (HSTS). When deployed on a subdomain, dashboard's security is only as strong as the weakest application deployed on the same second-level domain."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:115(title)
-msgid "Static media"
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:116(para)
-msgid "Dashboard's static media should be deployed to a subdomain of the dashboard domain and served by the web server. The use of an external content delivery network (CDN) is also acceptable. This subdomain should not set cookies or serve user-provided content. The media should also be served with HTTPS."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:121(para)
-msgid "Django media settings are documented at <link href=\"https://docs.djangoproject.com/en/1.5/ref/settings/#static-root\">https://docs.djangoproject.com/en/1.5/ref/settings/#static-root</link>."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:124(para)
-msgid "Dashboard's default configuration uses <link href=\"http://django-compressor.readthedocs.org/\">django_compressor</link> to compress and minify css and JavaScript content before serving it. This process should be statically done before deploying dashboard, rather than using the default in-request dynamic compression and copying the resulting files along with deployed code or to the CDN server. Compression should be done in a non-production build environment. If this is not practical, we recommend disabling resource compression entirely. Online compression dependencies (less, nodejs) should not be installed on production machines."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:138(title)
-msgid "Secret key"
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:139(para)
-msgid "Dashboard depends on a shared SECRET_KEY setting for some security functions. It should be a randomly generated string at least 64 characters long. It must be shared across all active dashboard instances. Compromise of this key may allow a remote attacker to execute arbitrary code. Rotating this key invalidates existing user sessions and caching. Do not commit this key to public repositories."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:148(title)
-msgid "Session back-end"
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:149(para)
-msgid "Horizon's default session back-end (<emphasis>django.contrib.sessions.backends.signed_cookies</emphasis>) stores user data in <emphasis>signed</emphasis> but <emphasis>unencrypted </emphasis>cookies stored in the browser. This approach allows the most simple session backend scaling since each dashboard instance is stateless, but it comes at the cost of <emphasis>storing sensitive access tokens in the client browser</emphasis> and transmitting them with every request. This backend ensures that session data has not been tampered with, but the data itself is not encrypted other than the encryption provided by HTTPS."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:160(para)
-msgid "If your architecture allows it, we recommend using <emphasis>django.contrib.sessions.backends.cache</emphasis> as your session backend with memcache as the cache. Memcache must not be exposed publicly, and should communicate over a secured private channel. If you choose to use the signed cookies backend, refer to the Django documentation understand the security trade-offs."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:167(para)
-msgid "For further details, consult the <link href=\"https://docs.djangoproject.com/en/1.5/topics/http/sessions/#configuring-the-session-engine\">Django session backend documentation</link>."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:172(title)
-msgid "Allowed hosts"
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:173(para)
-msgid "Configure the ALLOWED_HOSTS setting with the domain or domains where the dashboard is available. Failure to configure this setting (especially if not following the recommendation above regarding second level domains) opens the dashboard to a number of serious attacks. Wild card domains should be avoided."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:178(para)
-msgid "For further details, see the <link href=\"https://docs.djangoproject.com/en/1.5/ref/settings/#allowed-hosts\">Django documentation on settings</link>."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:183(title)
-msgid "Cookies"
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:184(para)
-msgid "Session Cookies should be set to HTTPONLY:"
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:186(para)
-msgid "Never configure CSRF or session cookies to have a wild card domain with a leading dot. Horizon's session and CSRF cookie should be secured when deployed with HTTPS:"
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:193(title)
-msgid "Password auto complete"
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:194(para)
-msgid "We recommend that implementers do not change the default password auto complete behavior. Users choose stronger passwords in environments that allow them to use the secure browser password manager. Organizations which forbid the browser password manager should enforce this policy at the desktop level."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:202(title)
-msgid "Cross Site Request Forgery (CSRF)"
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:203(para)
-msgid "Django has a dedicated middleware for <link href=\"https://docs.djangoproject.com/en/1.5/ref/contrib/csrf/#how-it-works\">cross-site request forgery</link> (CSRF)."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:206(para)
-msgid "Dashboard is designed to discourage developers from introducing cross-site scripting vulnerabilities with custom dashboards. However, it is important to audit custom dashboards, especially ones that are javascript-heavy for inappropriate use of the @csrf_exempt decorator. Dashboards which do not follow these recommended security settings should be carefully evaluated before restrictions are relaxed."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:215(title)
-msgid "Cross Site Scripting (XSS)"
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:216(para)
-msgid "Unlike many similar systems, OpenStack dashboard allows the entire Unicode character set in most fields. This means developers have less latitude to make escaping mistakes that open attack vectors for cross-site scripting (XSS)."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:220(para)
-msgid "Dashboard provides tools for developers to avoid creating XSS vulnerabilities, but they only work if developers use them correctly. Audit any custom dashboards, paying particular attention to use of the mark_safe function, use of is_safe with custom template tags, the safe template tag, anywhere auto escape is turned off, and any JavaScript which might evaluate improperly escaped data."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:229(title)
-msgid "Cross Origin Resource Sharing (CORS)"
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:230(para)
-msgid "Configure your web server to send a restrictive CORS header with each response, allowing only the dashboard domain and protocol:"
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:234(para)
-msgid "Never allow the wild card origin."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:237(title)
-msgid "Horizon image upload"
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:238(para)
-msgid "We recommend that implementers <link href=\"http://docs.openstack.org/developer/horizon/topics/deployment.html#file-uploads\">disable HORIZON_IMAGES_ALLOW_UPLOAD</link> unless they have implemented a plan to prevent resource exhaustion and denial of service."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:245(title)
-msgid "Upgrading"
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:246(para)
-msgid "Django security releases are generally well tested and aggressively backwards compatible. In almost all cases, new major releases of Django are also fully backwards compatible with previous releases. Dashboard implementers are strongly encouraged to run the latest stable release of Django with up-to-date security releases."
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:254(title)
-msgid "Debug"
-msgstr ""
-
-#: ./doc/security-guide/ch025_web-dashboard.xml:255(para)
-msgid "Make sure DEBUG is set to False in production. In Django, DEBUG displays stack traces and sensitive web server state information on any exception."
-msgstr ""
-
-#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml:8(title)
-msgid "Case studies: API endpoints"
-msgstr ""
-
-#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml:9(para)
-msgid "In this case study we discuss how Alice and Bob would address endpoint configuration to secure their private and public clouds. Alice's cloud is not publicly accessible, but she is still concerned about securing the endpoints against improper use. Bob's cloud, being public, must take measures to reduce the risk of attacks by external adversaries."
-msgstr ""
-
-#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml:12(para)
-msgid "Alice's organization requires that the security architecture protect the access to the public and private endpoints, so she elects to use the Apache SSL proxy on both public and internal services. Alice's organization has implemented its own certificate authority. Alice contacts the PKI office in her agency that manages her PKI and certificate issuance. Alice obtains certificates issued by this CA and configures the services within both the public and management security domains to use these certificates. Since Alice's OpenStack deployment exists entirely on a disconnected from the Internet network, she makes sure to remove all default CA bundles that contain external public CA providers to ensure the OpenStack services only accept client certificates issued by her agency's CA. Alice has registered all of the services in the Identity service's catalog, using the internal URLs for access by internal services. She has installed host-based intrusion detection on all of the API endpoints."
-msgstr ""
-
-#: ./doc/security-guide/ch022_case-studies-api-endpoints.xml:34(para)
-msgid "Bob must also protect the access to the public and private endpoints, so he elects to use the Apache SSL proxy on both public and internal services. On the public services, he has configured the certificate key files with certificates signed by a well-known Certificate Authority. He has used his organization's self-signed CA to sign certificates in the internal services on the Management network. Bob has registered his services in the Identity service's catalog, using the internal URLs for access by internal services. Bob's public cloud runs services on SELinux, which he has configured with a mandatory access control policy to reduce the impact of any publicly accessible services that may be compromised. He has also configured the endpoints with a host-based IDS."
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:8(title)
-msgid "Data privacy concerns"
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:9(para)
-msgid "OpenStack is designed to support multitenancy and those tenants will most probably have different data requirements. As a cloud builder and operator you need to ensure your OpenStack environment can address various data privacy concerns and regulations. In this chapter we will address the following topics around Data Privacy as it pertains to OpenStack implementations:"
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:19(para) ./doc/security-guide/ch046_data-residency.xml:26(title)
-msgid "Data residency"
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:22(para) ./doc/security-guide/ch046_data-residency.xml:77(title)
-msgid "Data disposal"
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:27(para)
-msgid "The privacy and isolation of data has consistently been cited as the primary barrier to cloud adoption over the past few years. Concerns over who owns data in the cloud and whether the cloud operator can be ultimately trusted as a custodian of this data have been significant issues in the past."
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:28(para)
-msgid "Numerous OpenStack services maintain data and metadata belonging to tenants or reference tenant information."
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:29(para)
-msgid "Tenant data stored in an OpenStack cloud may include the following items:"
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:31(para) ./doc/security-guide/ch047_data-encryption.xml:15(para) ./doc/security-guide/ch047_data-encryption.xml:25(title)
-msgid "Object Storage objects"
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:34(para)
-msgid "Compute instance ephemeral filesystem storage"
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:37(para)
-msgid "Compute instance memory"
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:40(para) ./doc/security-guide/ch046_data-residency.xml:105(para)
-msgid "Block Storage volume data"
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:43(para)
-msgid "Public keys for Compute Access"
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:46(para)
-msgid "Virtual Machine Images in the Image Service"
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:49(para)
-msgid "Machine snapshots"
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:52(para)
-msgid "Data passed to OpenStack Compute's configuration-drive extension"
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:55(para)
-msgid "Metadata stored by an OpenStack cloud includes the following non-exhaustive items:"
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:57(para)
-msgid "Organization name"
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:60(para)
-msgid "User's \"Real Name\""
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:63(para)
-msgid "Number or size of running instances, buckets, objects, volumes, and other quota-related items"
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:66(para)
-msgid "Number of hours running instances or storing data"
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:69(para)
-msgid "IP addresses of users"
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:72(para)
-msgid "Internally generated private keys for compute image bundling"
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:78(para)
-msgid "OpenStack operators should strive to provide a certain level of tenant data disposal assurance. Best practices suggest that the operator sanitize cloud system media (digital and non-digital) prior to disposal, release out of organization control or release for reuse. Sanitization methods should implement an appropriate level of strength and integrity given the specific security domain and sensitivity of the information."
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:80(para)
-msgid "\"Sanitization is the process used to remove information from system media such that there is reasonable assurance that the information cannot be retrieved or reconstructed. Sanitization techniques, including clearing, purging, and destroying media information, prevent the disclosure of organizational information to unauthorized individuals when such media is reused or released for disposal.\" [NIST Special Publication 800-53 Revision 3]"
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:82(para)
-msgid "General data disposal and sanitization guidelines as adopted from NIST recommended security controls. Cloud operators should:"
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:84(para)
-msgid "Track, document and verify media sanitization and disposal actions."
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:87(para)
-msgid "Test sanitation equipment and procedures to verify proper performance."
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:91(para)
-msgid "Sanitize portable, removable storage devices prior to connecting such devices to the cloud infrastructure."
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:94(para)
-msgid "Destroy cloud system media that cannot be sanitized."
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:97(para)
-msgid "In an OpenStack deployment you will need to address the following:"
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:99(para)
-msgid "Secure data erasure"
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:102(para) ./doc/security-guide/ch046_data-residency.xml:119(title)
-msgid "Instance memory scrubbing"
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:108(para) ./doc/security-guide/ch046_data-residency.xml:132(title)
-msgid "Compute instance ephemeral storage"
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:111(para) ./doc/security-guide/ch046_data-residency.xml:139(title)
-msgid "Bare metal server sanitization"
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:115(title)
-msgid "Data not securely erased"
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:116(para)
-msgid "Within OpenStack some data may be deleted, but not securely erased in the context of the NIST standards outlined above. This is generally applicable to most or all of the above-defined metadata and information stored in the database. This may be remediated with database and/or system configuration for auto vacuuming and periodic free-space wiping."
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:120(para)
-msgid "Specific to various hypervisors is the treatment of instance memory. This behavior is not defined in OpenStack Compute, although it is generally expected of hypervisors that they will make a best effort to scrub memory either upon deletion of an instance, upon creation of an instance, or both."
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:121(para)
-msgid "Xen explicitly assigns dedicated memory regions to instances and scrubs data upon the destruction of instances (or domains in Xen parlance). KVM depends more greatly on Linux page management; A complex set of rules related to KVM paging is defined in the <link href=\"http://www.linux-kvm.org/page/Memory\">KVM documentation</link>."
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:122(para)
-msgid "It is important to note that use of the Xen memory balloon feature is likely to result in information disclosure. We strongly recommended to avoid use of this feature."
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:123(para)
-msgid "For these and other hypervisors, we recommend referring to hypervisor-specific documentation."
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:126(title)
-msgid "Cinder volume data"
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:127(para)
-msgid "Plugins to OpenStack Block Storage will store data in a variety of ways. Many plug-ins are specific to a vendor or technology, whereas others are more DIY solutions around filesystems such as LVM or ZFS. Methods to securely destroy data will vary from one plugin to another, from one vendor's solution to another, and from one filesystem to another."
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:128(para)
-msgid "Some backends such as ZFS will support copy-on-write to prevent data exposure. In these cases, reads from unwritten blocks will always return zero. Other backends such as LVM may not natively support this, thus the Block Storage plug-in takes the responsibility to override previously written blocks before handing them to users. It is important to review what assurances your chosen volume backend provides and to see what mediations may be available for those assurances not provided."
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:129(para)
-msgid "Finally, while not a feature of OpenStack, vendors and implementors may choose to add or support encryption of volumes. In this case, destruction of data is as simple as throwing away the key."
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:133(para)
-msgid "The creation and destruction of ephemeral storage will be somewhat dependent on the chosen hypervisor and the OpenStack Compute plug-in."
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:134(para)
-msgid "The libvirt plug-in for compute may maintain ephemeral storage directly on a filesystem, or in LVM. Filesystem storage generally will not overwrite data when it is removed, although there is a guarantee that dirty extents are not provisioned to users."
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:135(para)
-msgid "When using LVM backed ephemeral storage, which is block-based, it is necessary that the OpenStack Compute software securely erases blocks to prevent information disclosure. There have in the past been information disclosure vulnerabilities related to improperly erased ephemeral block storage devices."
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:136(para)
-msgid "Filesystem storage is a more secure solution for ephemeral block storage devices than LVM as dirty extents cannot be provisioned to users. However, it is important to be mindful that user data is not destroyed, so it is suggested to encrypt the backing filesystem."
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:140(para)
-msgid "A bare metal server driver for Compute was under development and has since moved into a separate project called <link href=\"https://wiki.openstack.org/wiki/Ironic\">ironic</link>. At the time of this writing, ironic does not appear to address sanitization of tenant data resident the physical hardware."
-msgstr ""
-
-#: ./doc/security-guide/ch046_data-residency.xml:147(para)
-msgid "Additionally, it is possible for tenants of a bare metal system to modify system firmware. TPM technology, described in <xref linkend=\"ch013_node-bootstrapping-idp44768\"/>, provides a solution for detecting unauthorized firmware changes."
-msgstr ""
-
-#: ./doc/security-guide/ch062_audit-guidance.xml:8(title)
-msgid "Understanding the audit process"
-msgstr ""
-
-#: ./doc/security-guide/ch062_audit-guidance.xml:9(para)
-msgid "Information system security compliance is reliant on the completion of two foundational processes:"
-msgstr ""
-
-#: ./doc/security-guide/ch062_audit-guidance.xml:13(para)
-msgid "<emphasis role=\"bold\">Implementation and operation of security controls.</emphasis> Aligning the information system with in-scope standards and regulations involves internal tasks which must be conducted before a formal assessment. Auditors may be involved at this state to conduct gap analysis, provide guidance, and increase the likelihood of successful certification."
-msgstr ""
-
-#: ./doc/security-guide/ch062_audit-guidance.xml:23(para)
-msgid "<emphasis role=\"bold\">Independent verification and validation.</emphasis> Demonstration to a neutral third-party that system security controls are implemented and operating effectively, in compliance with in-scope standards and regulations, is required before many information systems achieve certified status. Many certifications require periodic audits to ensure continued certification, considered part of an overarching continuous monitoring practice."
-msgstr ""
-
-#: ./doc/security-guide/ch062_audit-guidance.xml:36(title)
-msgid "Determining audit scope"
-msgstr ""
-
-#: ./doc/security-guide/ch062_audit-guidance.xml:37(para)
-msgid "Determining audit scope, specifically what controls are needed and how to design or modify an OpenStack deployment to satisfy them, should be the initial planning step."
-msgstr ""
-
-#: ./doc/security-guide/ch062_audit-guidance.xml:38(para)
-msgid "When scoping OpenStack deployments for compliance purposes, consider prioritizing controls around sensitive services, such as command and control functions and the base virtualization technology. Compromises of these facilities may impact an OpenStack environment in its entirety."
-msgstr ""
-
-#: ./doc/security-guide/ch062_audit-guidance.xml:39(para)
-msgid "Scope reduction helps ensure OpenStack architects establish high quality security controls which are tailored to a particular deployment, however it is paramount to ensure these practices do not omit areas or features from security hardening. A common example is applicable to PCI-DSS guidelines, where payment related infrastructure may be scrutinized for security issues, but supporting services are left ignored, and vulnerable to attack."
-msgstr ""
-
-#: ./doc/security-guide/ch062_audit-guidance.xml:40(para)
-msgid "When addressing compliance, you can increase efficiency and reduce work effort by identifying common areas and criteria that apply across multiple certifications. Much of the audit principles and guidelines discussed in this book will assist in identifying these controls, additionally a number of external entities provide comprehensive lists. The following are some examples:"
-msgstr ""
-
-#: ./doc/security-guide/ch062_audit-guidance.xml:41(para)
-msgid "The <link href=\"https://cloudsecurityalliance.org/research/ccm/\">Cloud Security Alliance Cloud Controls Matrix</link> (CCM) assists both cloud providers and consumers in assessing the overall security of a cloud provider. The CSA CMM provides a controls framework that map to many industry-accepted standards and regulations including the ISO 27001/2, ISACA, COBIT, PCI, NIST, Jericho Forum and NERC CIP."
-msgstr ""
-
-#: ./doc/security-guide/ch062_audit-guidance.xml:42(para)
-msgid "The <link href=\"https://fedorahosted.org/scap-security-guide/\">SCAP Security Guide</link> is another useful reference. This is still an emerging source, but we anticipate that this will grow into a tool with controls mappings that are more focused on the US federal government certifications and recommendations. For example, the SCAP Security Guide currently has some mappings for security technical implementation guides (STIGs) and NIST-800-53."
-msgstr ""
-
-#: ./doc/security-guide/ch062_audit-guidance.xml:43(para)
-msgid "These control mappings will help identify common control criteria across certifications, and provide visibility to both auditors and auditees on problem areas within control sets for particular compliance certifications and attestations."
-msgstr ""
-
-#: ./doc/security-guide/ch062_audit-guidance.xml:46(title)
-msgid "Internal audit"
-msgstr ""
-
-#: ./doc/security-guide/ch062_audit-guidance.xml:47(para)
-msgid "Once a cloud is deployed, it is time for an internal audit. This is the time compare the controls you identified above with the design, features, and deployment strategies utilized in your cloud. The goal is to understand how each control is handled and where gaps exist. Document all of the findings for future reference."
-msgstr ""
-
-#: ./doc/security-guide/ch062_audit-guidance.xml:48(para)
-msgid "When auditing an OpenStack cloud it is important to appreciate the multi-tenant environment inherent in the OpenStack architecture. Some critical areas for concern include data disposal, hypervisor security, node hardening, and authentication mechanisms."
-msgstr ""
-
-#: ./doc/security-guide/ch062_audit-guidance.xml:51(title)
-msgid "Prepare for external audit"
-msgstr ""
-
-#: ./doc/security-guide/ch062_audit-guidance.xml:52(para)
-msgid "Once the internal audit results look good, it is time to prepare for an external audit. There are several key actions to take at this stage, these are outlined below:"
-msgstr ""
-
-#: ./doc/security-guide/ch062_audit-guidance.xml:54(para)
-msgid "Maintain good records from your internal audit. These will prove useful during the external audit so you can be prepared to answer questions about mapping the compliance controls to a particular deployment."
-msgstr ""
-
-#: ./doc/security-guide/ch062_audit-guidance.xml:57(para)
-msgid "Deploy automated testing tools to ensure that the cloud remains compliant over time."
-msgstr ""
-
-#: ./doc/security-guide/ch062_audit-guidance.xml:60(para)
-msgid "Select an auditor."
-msgstr ""
-
-#: ./doc/security-guide/ch062_audit-guidance.xml:63(para)
-msgid "Selecting an auditor can be challenging. Ideally, you are looking for someone with experience in cloud compliance audits. OpenStack experience is another big plus. Often it is best to consult with people who have been through this process for referrals. Cost can vary greatly depending on the scope of the engagement and the audit firm considered."
-msgstr ""
-
-#: ./doc/security-guide/ch062_audit-guidance.xml:66(title)
-msgid "External audit"
-msgstr ""
-
-#: ./doc/security-guide/ch062_audit-guidance.xml:67(para)
-msgid "This is the formal audit process. Auditors will test security controls in scope for a specific certification, and demand evidentiary requirements to prove that these controls were also in place for the audit window (for example SOC 2 audits generally evaluate security controls over a 6-12 months period). Any control failures are logged, and will be documented in the external auditors final report. Dependent on the type of OpenStack deployment, these reports may be viewed by customers, so it is important to avoid control failures. This is why audit preparation is so important."
-msgstr ""
-
-#: ./doc/security-guide/ch062_audit-guidance.xml:70(title)
-msgid "Compliance maintenance"
-msgstr ""
-
-#: ./doc/security-guide/ch062_audit-guidance.xml:71(para)
-msgid "The process doesn't end with a single external audit. Most certifications require continual compliance activities which means repeating the audit process periodically. We recommend integrating automated compliance verification tools into a cloud to ensure that it is compliant at all times. This should be in done in addition to other security monitoring tools. Remember that the goal is both security <emphasis>and</emphasis> compliance. Failing on either of these fronts will significantly complicate future audits."
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch042_database-overview.xml:18(None) ./doc/security-guide/ch042_database-overview.xml:21(None)
-msgid "@@image: 'static/databaseusername.png'; md5=a6a5dadedbc1517069ca388c7ac5940a"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch042_database-overview.xml:42(None) ./doc/security-guide/ch042_database-overview.xml:45(None)
-msgid "@@image: 'static/databaseusernamessl.png'; md5=9c43242c47eb159b6f61ac41f3d8bced"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch042_database-overview.xml:104(None) ./doc/security-guide/ch042_database-overview.xml:107(None)
-msgid "@@image: 'static/novaconductor.png'; md5=dbc1ba139bd1af333f0415bb48704843"
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:8(title)
-msgid "Database access control"
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:9(para)
-msgid "Each of the core OpenStack services (Compute, Identity, Networking, Block Storage) store state and configuration information in databases. In this chapter, we discuss how databases are used currently in OpenStack. We also explore security concerns, and the security ramifications of database backend choices."
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:11(title)
-msgid "OpenStack database access model"
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:12(para)
-msgid "All of the services within an OpenStack project access a single database. There are presently no reference policies for creating table or row based access restrictions to the database."
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:13(para)
-msgid "There are no general provisions for granular control of database operations in OpenStack. Access and privileges are granted simply based on whether a node has access to the database or not. In this scenario, nodes with access to the database may have full privileges to DROP, INSERT, or UPDATE functions."
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:15(title)
-msgid "Granular access control"
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:16(para)
-msgid "By default, each of the OpenStack services and their processes access the database using a shared set of credentials. This makes auditing database operations and revoking access privileges from a service and its processes to the database particularly difficult."
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:26(title) ./doc/security-guide/ch042_database-overview.xml:99(title)
-msgid "Nova-conductor"
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:27(para)
-msgid "The compute nodes are the least trusted of the services in OpenStack because they host tenant instances. The <systemitem class=\"service\">nova-conductor</systemitem> service has been introduced to serve as a database proxy, acting as an intermediary between the compute nodes and the database. We discuss its ramifications later in this chapter."
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:28(para)
-msgid "We strongly recommend:"
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:30(para)
-msgid "All database communications be isolated to a management network"
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:33(para)
-msgid "Securing communications using SSL"
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:36(para)
-msgid "Creating unique database user accounts per OpenStack service endpoint (illustrated below)"
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:52(title)
-msgid "Database authentication and access control"
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:53(para)
-msgid "Given the risks around access to the database, we strongly recommend that unique database user accounts be created per node needing access to the database. Doing this facilitates better analysis and auditing for ensuring compliance or in the event of a compromise of a node allows you to isolate the compromised host by removing access for that node to the database upon detection. When creating these per service endpoint database user accounts, care should be taken to ensure that they are configured to require SSL. Alternatively, for increased security it is recommended that the database accounts be configured using X.509 certificate authentication in addition to usernames and passwords."
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:55(title)
-msgid "Privileges"
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:56(para)
-msgid "A separate database administrator (DBA) account should be created and protected that has full privileges to create/drop databases, create user accounts, and update user privileges. This simple means of separation of responsibility helps prevent accidental misconfiguration, lowers risk and lowers scope of compromise."
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:57(para)
-msgid "The database user accounts created for the OpenStack services and for each node should have privileges limited to just the database relevant to the service where the node is a member."
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:61(title)
-msgid "Require user accounts to require SSL transport"
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:63(title) ./doc/security-guide/ch042_database-overview.xml:81(title)
-msgid "Configuration example #1: (MySQL)"
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:67(title) ./doc/security-guide/ch042_database-overview.xml:87(title)
-msgid "Configuration example #2: (PostgreSQL)"
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:68(para)
-msgid "In file <filename>pg_hba.conf</filename>:"
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:70(para)
-msgid "Note this command only adds the ability to communicate over SSL and is non-exclusive. Other access methods that may allow unencrypted transport should be disabled so that SSL is the sole access method."
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:71(para)
-msgid "The <literal>md5</literal> parameter defines the authentication method as a hashed password. We provide a secure authentication example in the section below."
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:78(title)
-msgid "Authentication with X.509 certificates"
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:79(para)
-msgid "Security may be enhanced by requiring X.509 client certificates for authentication. Authenticating to the database in this manner provides greater identity assurance of the client making the connection to the database and ensures that the communications are encrypted."
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:92(title)
-msgid "OpenStack service database configuration"
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:93(para)
-msgid "If your database server is configured to require X.509 certificates for authentication you will need to specify the appropriate SQLAlchemy query parameters for the database backend. These parameters specify the certificate, private key, and certificate authority information for use with the initial connection string."
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:94(para)
-msgid "Example of an <literal>:sql_connection</literal> string for X.509 certificate authentication to MySQL:"
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:100(para)
-msgid "OpenStack Compute offers a sub-service called <systemitem class=\"service\">nova-conductor</systemitem> which proxies database connections, with the primary purpose of having the nova compute nodes interfacing with <systemitem class=\"service\">nova-conductor</systemitem> to meet data persistence needs as opposed to directly communicating with the database."
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:101(para)
-msgid "Nova-conductor receives requests over RPC and performs actions on behalf of the calling service without granting granular access to the database, its tables, or data within. Nova-conductor essentially abstracts direct database access away from compute nodes."
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:102(para)
-msgid "This abstraction offers the advantage of restricting services to executing methods with parameters, similar to stored procedures, preventing a large number of systems from directly accessing or modifying database data. This is accomplished without having these procedures stored or executed within the context or scope of the database itself, a frequent criticism of typical stored procedures."
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:110(para)
-msgid "Unfortunately, this solution complicates the task of more fine-grained access control and the ability to audit data access. Because the <systemitem class=\"service\">nova-conductor</systemitem> service receives requests over RPC, it highlights the importance of improving the security of messaging. Any node with access to the message queue may execute these methods provided by the <systemitem class=\"service\">nova-conductor</systemitem> and effectively modifying the database."
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:111(para)
-msgid "Finally, it should be noted that as of the Grizzly release, gaps exist where <systemitem class=\"service\">nova-conductor</systemitem> is not used throughout OpenStack Compute. Depending on one's configuration, the use of <systemitem class=\"service\">nova-conductor</systemitem> may not allow deployers to avoid the necessity of providing database GRANTs to individual compute host systems."
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:112(para)
-msgid "Note, as <systemitem class=\"service\">nova-conductor</systemitem> only applies to OpenStack Compute, direct database access from compute hosts may still be necessary for the operation of other OpenStack components such as Telemetry (ceilometer), Networking, and Block Storage."
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:118(para)
-msgid "Implementors should weigh the benefits and risks of both configurations before enabling or disabling the <systemitem class=\"service\">nova-conductor</systemitem> service. We are not yet prepared to recommend the use of <systemitem class=\"service\">nova-conductor</systemitem> in the Grizzly release. However, we do believe that this recommendation will change as additional features are added into OpenStack."
-msgstr ""
-
-#: ./doc/security-guide/ch042_database-overview.xml:119(para)
-msgid "To disable the <systemitem class=\"service\">nova-conductor</systemitem>, place the following into your <filename>nova.conf</filename> file (on your compute hosts):"
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:8(title)
-msgid "Identity"
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:9(para)
-msgid "The OpenStack Identity service (keystone) supports multiple methods of authentication, including username &amp; password, LDAP, and external authentication methods. Upon successful authentication, The Identity Service provides the user with an authorization token used for subsequent service requests."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:14(para)
-msgid "Transport Layer Security TLS/SSL provides authentication between services and persons using X.509 certificates. Although the default mode for SSL is server-side only authentication, certificates may also be used for client authentication."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:19(title)
-msgid "Authentication"
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:21(title)
-msgid "Invalid login attempts"
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:22(para)
-msgid "The Identity Service does not provide a method to limit access to accounts after repeated unsuccessful login attempts. Repeated failed login attempts are likely brute-force attacks (Refer figure Attack-types). This is a more significant issue in Public clouds."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:27(para)
-msgid "Prevention is possible by using an external authentication system that blocks out an account after some configured number of failed login attempts. The account then may only be unlocked with further side-channel intervention."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:31(para)
-msgid "If prevention is not an option, detection can be used to mitigate damage.Detection involves frequent review of access control logs to identify unauthorized attempts to access accounts. Possible remediation would include reviewing the strength of the user password, or blocking the network source of the attack through firewall rules. Firewall rules on the keystone server that restrict the number of connections could be used to reduce the attack effectiveness, and thus dissuade the attacker."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:40(para)
-msgid "In addition, it is useful to examine account activity for unusual login times and suspicious actions, with possibly disable the account. Oftentimes this approach is taken by credit card providers for fraud detection and alert."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:46(title)
-msgid "Multi-factor authentication"
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:47(para)
-msgid "Employ multi-factor authentication for network access to privileged user accounts. The Identity Service supports external authentication services through the Apache web server that can provide this functionality. Servers may also enforce client-side authentication using certificates."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:52(para)
-msgid "This recommendation provides insulation from brute force, social engineering, and both spear and mass phishing attacks that may compromise administrator passwords."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:58(title)
-msgid "Authentication methods"
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:60(title)
-msgid "Internally implemented authentication methods"
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:61(para)
-msgid "The Identity Service can store user credentials in an SQL Database, or may use an LDAP-compliant directory server. The Identity database may be separate from databases used by other OpenStack services to reduce the risk of a compromise of the stored credentials."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:66(para)
-msgid "When you use a user name and password to authenticate, Identity does not enforce policies on password strength, expiration, or failed authentication attempts as recommended by NIST Special Publication 800-118 (draft). Organizations that desire to enforce stronger password policies should consider using Identity extensions or external authentication services."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:74(para)
-msgid "LDAP simplifies integration of Identity authentication into an organization's existing directory service and user account management processes."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:77(para)
-msgid "Authentication and authorization policy in OpenStack may be delegated to an external LDAP server. A typical use case is an organization that seeks to deploy a private cloud and already has a database of employees, the users. This may be in an LDAP system. Using LDAP as a source of authority authentication, requests to Identity Service are delegated to the LDAP service, which will authorize or deny requests based on locally set policies. A token is generated on successful authentication."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:86(para)
-msgid "Note that if the LDAP system has attributes defined for the user such as admin, finance, HR etc, these must be mapped into roles and groups within Identity for use by the various OpenStack services. The <filename>/etc/keystone.conf</filename> file maps LDAP attributes to Identity attributes."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:91(para)
-msgid "The Identity Service <emphasis role=\"bold\">MUST NOT</emphasis> be allowed to write to LDAP services used for authentication outside of the OpenStack deployment as this would allow a sufficiently privileged keystone user to make changes to the LDAP directory. This would allow privilege escalation within the wider organization or facilitate unauthorized access to other information and resources. In such a deployment, user provisioning would be out of the realm of the OpenStack deployment."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:101(para)
-msgid "There is an <link href=\"https://bugs.launchpad.net/ossn/+bug/1168252\">OpenStack Security Note (OSSN) regarding keystone.conf permissions</link>."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:105(para)
-msgid "There is an <link href=\"https://bugs.launchpad.net/ossn/+bug/1155566\">OpenStack Security Note (OSSN) regarding potential DoS attacks</link>."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:112(title)
-msgid "External authentication methods"
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:113(para)
-msgid "Organizations may desire to implement external authentication for compatibility with existing authentication services or to enforce stronger authentication policy requirements. Although passwords are the most common form of authentication, they can be compromised through numerous methods, including keystroke logging and password compromise. External authentication services can provide alternative forms of authentication that minimize the risk from weak passwords."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:122(para)
-msgid "These include:"
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:125(para)
-msgid "Password policy enforcement: Requires user passwords to conform to minimum standards for length, diversity of characters, expiration, or failed login attempts."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:130(para)
-msgid "Multi-factor authentication: The authentication service requires the user to provide information based on something they have, such as a one-time password token or X.509 certificate, and something they know, such as a password."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:137(para)
-msgid "Kerberos"
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:143(title)
-msgid "Authorization"
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:144(para)
-msgid "The Identity Service supports the notion of groups and roles. Users belong to groups. A group has a list of roles. OpenStack services reference the roles of the user attempting to access the service. The OpenStack policy enforcer middleware takes into consideration the policy rule associated with each resource and the user's group/roles and tenant association to determine if he/she has access to the requested resource."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:151(para)
-msgid "The Policy enforcement middleware enables fine-grained access control to OpenStack resources. Only admin users can provision new users and have access to various management functionality. The cloud tenant would be able to only spin up instances, attach volumes, etc."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:157(title)
-msgid "Establish formal access control policies"
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:158(para)
-msgid "Prior to configuring roles, groups, and users, document your required access control policies for the OpenStack installation. The policies should be consistent with any regulatory or legal requirements for the organization. Future modifications to access control configuration should be done consistently with the formal policies. The policies should include the conditions and processes for creating, deleting, disabling, and enabling accounts, and for assigning privileges to the accounts. Periodically review the policies and ensure that configuration is in compliance with approved policies."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:171(title)
-msgid "Service authorization"
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:172(para)
-msgid "As described in the <link href=\"http://docs.openstack.org/admin-guide-cloud/content/index.html\"><citetitle>OpenStack Cloud Administrator Guide</citetitle></link>, cloud administrators must define a user for each service, with a role of Admin. This service user account provides the service with the authorization to authenticate users."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:179(para)
-msgid "The Compute and Object Storage services can be configured to use either the \"tempAuth\" file or Identity Service to store authentication information. The \"tempAuth\" solution MUST NOT be deployed in a production environment since it stores passwords in plain text."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:184(para)
-msgid "The Identity Service supports client authentication for SSL which may be enabled. SSL client authentication provides an additional authentication factor, in addition to the username / password, that provides greater reliability on user identification. It reduces the risk of unauthorized access when user names and passwords may be compromised. However, there is additional administrative overhead and cost to issue certificates to users that may not be feasible in every deployment."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:194(para)
-msgid "We recommend that you use client authentication with SSL for the authentication of services to the Identity Service."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:198(para)
-msgid "The cloud administrator should protect sensitive configuration files for unauthorized modification. This can be achieved with mandatory access control frameworks such as SELinux, including <filename>/etc/keystone.conf</filename> and X.509 certificates."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:204(para)
-msgid "For client authentication with SSL, you need to issue certificates. These certificates can be signed by an external authority or by the cloud administrator. OpenStack services by default check the signatures of certificates and connections fail if the signature cannot be checked. If the administrator uses self-signed certificates, the check might need to be disabled. To disable these certificates, set <code>insecure=False</code> in the <code>[filter:authtoken]</code> section in the <filename>/etc/nova/api.paste.ini</filename> file. This setting also disables certificates for other components."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:218(title)
-msgid "Administrative users"
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:219(para)
-msgid "We recommend that admin users authenticate using Identity Service and an external authentication service that supports 2-factor authentication, such as a certificate. This reduces the risk from passwords that may be compromised. This recommendation is in compliance with NIST 800-53 IA-2(1) guidance in the use of multi factor authentication for network access to privileged accounts."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:228(title)
-msgid "End users"
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:229(para)
-msgid "The Identity Service can directly provide end-user authentication, or can be configured to use external authentication methods to conform to an organization's security policies and requirements."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:236(title)
-msgid "Policies"
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:237(para)
-msgid "Each OpenStack service has a policy file in JSON format, called <filename>policy.json</filename>. The policy file specifies rules, and the rule that governs each resource. A resource could be API access, the ability to attach to a volume, or to fire up instances."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:242(para)
-msgid "The policies can be updated by the cloud administrator to further control access to the various resources. The middleware could also be further customized. Note that your users must be assigned to groups/roles that you refer to in your policies."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:247(para)
-msgid "Below is a snippet of the Block Storage service <filename>policy.json</filename> file."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:250(para)
-msgid "Note the <emphasis role=\"bold\">default</emphasis> rule specifies that the user must be either an admin or the owner of the volume. It essentially says only the owner of a volume or the admin may create/delete/update volumes. Certain other operations such as managing volume types are accessible only to admin users."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:258(title)
-msgid "Tokens"
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:259(para)
-msgid "Once a user is authenticated, a token is generated and used internally in OpenStack for authorization and access. The default token <emphasis role=\"bold\">lifespan</emphasis> is<emphasis role=\"bold\"> 24 hours</emphasis>. It is recommended that this value be set lower but caution needs to be taken as some internal services will need sufficient time to complete their work. The cloud may not provide services if tokens expire too early. An example of this would be the time needed by the Compute service to transfer a disk image onto the hypervisor for local caching."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:269(para)
-msgid "The following example shows a PKI token. Note that, in practice, the token id value is about 3500 bytes. We shorten it in this example."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:273(para)
-msgid "Note that the token is often passed within the structure of a larger context of an Identity Service response. These responses also provide a catalog of the various OpenStack services. Each service is listed with its name, access endpoints for internal, admin, and public access."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:278(para)
-msgid "The Identity Service supports token revocation. This manifests as an API to revoke a token, to list revoked tokens and individual OpenStack services that cache tokens to query for the revoked tokens and remove them from their cache and append the same to their list of cached revoked tokens."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:285(title)
-msgid "Future"
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:286(para)
-msgid "Domains are high-level containers for projects, users and groups. As such, they can be used to centrally manage all keystone-based identity components. With the introduction of account domains, server, storage and other resources can now be logically grouped into multiple projects (previously called tenants) which can themselves be grouped under a master account-like container. In addition, multiple users can be managed within an account domain and assigned roles that vary for each project."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:295(para)
-msgid "The Identity V3 API supports multiple domains. Users of different domains may be represented in different authentication backends and even have different attributes that must be mapped to a single set of roles and privileges, that are used in the policy definitions to access the various service resources."
-msgstr ""
-
-#: ./doc/security-guide/ch024_authentication.xml:301(para)
-msgid "Where a rule may specify access to only admin users and users belonging to the tenant, the mapping may be trivial. In other scenarios the cloud administrator may need to approve the mapping routines per tenant."
-msgstr ""
-
-#: ./doc/security-guide/ch015_case-studies-management.xml:8(title)
-msgid "Case studies: management interfaces"
-msgstr ""
-
-#: ./doc/security-guide/ch015_case-studies-management.xml:9(para)
-msgid "Previously we discussed typical OpenStack management interfaces and associated backplane issues. We will now approach these issues by returning to our Alice and Bob case study. Specifically, we will look into how both Alice and Bob will address:"
-msgstr ""
-
-#: ./doc/security-guide/ch015_case-studies-management.xml:15(para)
-msgid "Cloud administration"
-msgstr ""
-
-#: ./doc/security-guide/ch015_case-studies-management.xml:18(para)
-msgid "Self service"
-msgstr ""
-
-#: ./doc/security-guide/ch015_case-studies-management.xml:21(para)
-msgid "Data replication and recovery"
-msgstr ""
-
-#: ./doc/security-guide/ch015_case-studies-management.xml:24(para)
-msgid "SLA and security monitoring"
-msgstr ""
-
-#: ./doc/security-guide/ch015_case-studies-management.xml:29(para)
-msgid "When building her private cloud, while air-gapped, Alice still needs to consider her service management interfaces. Before deploying her private cloud, Alice has completed her system documentation. Specifically she has identified which OpenStack services will exist in each security domain. From there Alice has further restricted access to management interfaces by deploying a combination of IDS, SSL encryption, and physical network isolation. Additionally, Alice requires high availability and redundant services. Thus, Alice sets up redundant infrastructure for various OpenStack API services."
-msgstr ""
-
-#: ./doc/security-guide/ch015_case-studies-management.xml:30(para)
-msgid "Alice also needs to provide assurances that the physical servers and hypervisors have been built from a known secure state into a well-defined configuration. To enable this, Alice uses a combination of a Configuration Management platform to configure each machine according to the standards and regulations she must comply with. It will also enable Alice to report periodically on the state of her cloud and perform remediation to a known state should anything be out of the ordinary. Additionally, Alice provides hardware assurances by using a PXE system to build her nodes from a known set of base images. During the boot process, Alice provides further assurances by enabling Intel TXT and related trusted boot technologies provided by the hardware."
-msgstr ""
-
-#: ./doc/security-guide/ch015_case-studies-management.xml:34(para)
-msgid "As a public cloud provider, Bob is concerned with both the continuous availability of management interfaces and the security of transactions to the management interfaces. To that end Bob implements multiple redundant OpenStack API endpoints for the services his cloud will run. Additionally on the public network Bob uses SSL to encrypt all transactions between his customers and his cloud interfaces. To isolate his cloud operations Bob has physically isolated his management, instance migration, and storage networks."
-msgstr ""
-
-#: ./doc/security-guide/ch015_case-studies-management.xml:35(para)
-msgid "To ease scaling and reduce management overhead Bob implements a configuration management system. For customer data assurances, Bob offers a backup as a service product as requirements will vary between customers. Finally, Bob does not provide a \"baremetal\" or the ability to schedule an entire node, so to reduce management overhead and increase operational efficiency Bob does not implement any node boot time security."
-msgstr ""
-
-#: ./doc/security-guide/ch018_case-studies-pkissl.xml:8(title)
-msgid "Case studies: PKI and certificate management"
-msgstr ""
-
-#: ./doc/security-guide/ch018_case-studies-pkissl.xml:9(para)
-msgid "In this case study we discuss how Alice and Bob would address deployment of PKI certification authorities (CA) and certificate management."
-msgstr ""
-
-#: ./doc/security-guide/ch018_case-studies-pkissl.xml:12(para)
-msgid "Alice as a cloud architect within a government agency knows that her agency operates its own certification authority. Alice contacts the PKI office in her agency that manages her PKI and certificate issuance. Alice obtains certificates issued by this CA and configures the services within both the public and management security domains to use these certificates. Since Alice's OpenStack deployment exists entirely on a disconnected from the Internet network, she makes sure to remove all default CA bundles that contain external public CA providers to ensure the OpenStack services only accept client certificates issued by her agency's CA."
-msgstr ""
-
-#: ./doc/security-guide/ch018_case-studies-pkissl.xml:16(para)
-msgid "Bob is architecting a public cloud and needs to ensure that the publicly facing OpenStack services are using certificates issued by a major public CA. Bob acquires certificates for his public OpenStack services and configures the services to use PKI and SSL and includes the public CAs in his trust bundle for the services. Additionally, Bob also wants to further isolate the internal communications amongst the services within the management security domain. Bob contacts the team within his organization that is responsible for managing his organizations PKI and issuance of certificates using their own internal CA. Bob obtains certificates issued by this internal CA and configures the services that communicate within the management security domain to use these certificates and configures the services to only accept client certificates issued by his internal CA."
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch031_neutron-architecture.xml:87(None) ./doc/security-guide/ch031_neutron-architecture.xml:92(None)
-msgid "@@image: 'static/sdn-connections.png'; md5=1de9169834b34c83f574f2a1225b27f0"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch031_neutron-architecture.xml:109(None) ./doc/security-guide/ch031_neutron-architecture.xml:114(None)
-msgid "@@image: 'static/1aa-network-domains-diagram.png'; md5=135806775939d9e5e750264d8a5fe8de"
-msgstr ""
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml:8(title)
-msgid "Networking architecture"
-msgstr ""
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml:9(para)
-msgid "OpenStack Networking is a standalone service that often deploys several processes across a number of nodes. These processes interact with each other and other OpenStack services. The main process of the OpenStack Networking service is <systemitem class=\"service\">neutron-server</systemitem>, a Python daemon that exposes the OpenStack Networking API and passes tenant requests to a suite of plug-ins for additional processing."
-msgstr ""
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml:17(para)
-msgid "The OpenStack Networking components are:"
-msgstr ""
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml:21(term)
-msgid "neutron server (<systemitem class=\"service\">neutron-server</systemitem> and <systemitem class=\"service\">neutron-*-plugin</systemitem>)"
-msgstr ""
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml:25(para)
-msgid "This service runs on the network node to service the Networking API and its extensions. It also enforces the network model and IP addressing of each port. The neutron-server and plugin agents require access to a database for persistent storage and access to a message queue for inter-communication."
-msgstr ""
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml:35(term)
-msgid "plugin agent (<systemitem class=\"service\">neutron-*-agent</systemitem>)"
-msgstr ""
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml:38(para)
-msgid "Runs on each compute node to manage local virtual switch (vswitch) configuration. The plug-in that you use determine which agents run. This service requires message queue access. <emphasis>Optional depending on plugin.</emphasis>"
-msgstr ""
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml:46(term)
-msgid "DHCP agent (<systemitem class=\"service\">neutron-dhcp-agent</systemitem>)"
-msgstr ""
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml:49(para)
-msgid "Provides DHCP services to tenant networks. This agent is the same across all plug-ins and is responsible for maintaining DHCP configuration. The <systemitem class=\"service\">neutron-dhcp-agent</systemitem> requires message queue access."
-msgstr ""
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml:58(term)
-msgid "L3 agent (<systemitem class=\"service\">neutron-l3-agent</systemitem>)"
-msgstr ""
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml:61(para)
-msgid "Provides L3/NAT forwarding for external network access of VMs on tenant networks. Requires message queue access. <emphasis>Optional depending on plug-in.</emphasis>"
-msgstr ""
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml:69(term)
-msgid "network provider services (SDN server/services)"
-msgstr ""
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml:71(para)
-msgid "Provide additional networking services to tenant networks. These SDN services might interact with the <systemitem class=\"service\">neutron-server</systemitem>, <systemitem class=\"service\">neutron-plugin</systemitem>, and/or plugin-agents through REST APIs or other communication channels."
-msgstr ""
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml:81(para)
-msgid "The following figure shows an architectural and networking flow diagram of the OpenStack Networking components:"
-msgstr ""
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml:97(title)
-msgid "OpenStack Networking service placement on physical servers"
-msgstr ""
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml:98(para)
-msgid "This guide focuses on a standard architecture that includes a <emphasis>cloud controller</emphasis> host, a <emphasis>network</emphasis> host, and a set of <emphasis>compute</emphasis> hypervisors for running VMs."
-msgstr ""
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml:105(title)
-msgid "Network connectivity of physical servers"
-msgstr ""
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml:118(para)
-msgid "A standard OpenStack Networking setup has up to four distinct physical data center networks:"
-msgstr ""
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml:122(term)
-msgid "Management network"
-msgstr ""
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml:124(para)
-msgid "Used for internal communication between OpenStack Components. The IP addresses on this network should be reachable only within the data center and is considered the Management Security Domain."
-msgstr ""
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml:132(term)
-msgid "Guest network"
-msgstr ""
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml:134(para)
-msgid "Used for VM data communication within the cloud deployment. The IP addressing requirements of this network depend on the OpenStack Networking plug-in in use and the network configuration choices of the virtual networks made by the tenant. This network is considered the Guest Security Domain."
-msgstr ""
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml:144(term)
-msgid "External network"
-msgstr ""
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml:146(para)
-msgid "Used to provide VMs with Internet access in some deployment scenarios. The IP addresses on this network should be reachable by anyone on the Internet and is considered to be in the Public Security Domain."
-msgstr ""
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml:154(term)
-msgid "API network"
-msgstr ""
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml:156(para)
-msgid "Exposes all OpenStack APIs, including the OpenStack Networking API, to tenants. The IP addresses on this network should be reachable by anyone on the Internet. This may be the same network as the external network, as it is possible to create a subnet for the external network that uses IP allocation ranges to use only less than the full range of IP addresses in an IP block. This network is considered the Public Security Domain."
-msgstr ""
-
-#: ./doc/security-guide/ch031_neutron-architecture.xml:169(para)
-msgid "For additional information see the <link href=\"http://docs.openstack.org/admin-guide-cloud/content/ch_networking.html\">Networking chapter</link> in the <citetitle>OpenStack Cloud Administrator Guide</citetitle>."
-msgstr ""
-
-#: ./doc/security-guide/ch047_data-encryption.xml:8(title)
-msgid "Data encryption"
-msgstr ""
-
-#: ./doc/security-guide/ch047_data-encryption.xml:9(para)
-msgid "The option exists for implementors to encrypt tenant data wherever it is stored on disk or transported over a network. This is above and beyond the general recommendation that users encrypt their own data before sending it to their provider."
-msgstr ""
-
-#: ./doc/security-guide/ch047_data-encryption.xml:10(para)
-msgid "The importance of encrypting data on behalf of tenants is largely related to the risk assumed by a provider that an attacker could access tenant data. There may be requirements here in government, as well as requirements per-policy, in private contract, or even in case law in regard to private contracts for public cloud providers. It is recommended that a risk assessment and legal consul advised before choosing tenant encryption policies."
-msgstr ""
-
-#: ./doc/security-guide/ch047_data-encryption.xml:11(para)
-msgid "Per-instance or per-object encryption is preferable over, in descending order, over per-project, per-tenant, per-host, and per-cloud aggregations. This recommendation is inverse to the complexity and difficulty of implementation. Presently, in some projects it is difficult or impossible to implement encryption as loosely granular as even per-tenant. We recommend implementors make a best-effort in encrypting tenant data."
-msgstr ""
-
-#: ./doc/security-guide/ch047_data-encryption.xml:12(para)
-msgid "Often, data encryption relates positively to the ability to reliably destroy tenant and per-instance data, simply by throwing away the keys. It should be noted that in doing so, it becomes of great importance to destroy those keys in a reliable and secure manner."
-msgstr ""
-
-#: ./doc/security-guide/ch047_data-encryption.xml:13(para)
-msgid "Opportunities to encrypt data for users are present:"
-msgstr ""
-
-#: ./doc/security-guide/ch047_data-encryption.xml:18(para) ./doc/security-guide/ch047_data-encryption.xml:31(title)
-msgid "Block Storage volumes and instance ephemeral filesystems"
-msgstr ""
-
-#: ./doc/security-guide/ch047_data-encryption.xml:21(para) ./doc/security-guide/ch047_data-encryption.xml:37(title)
-msgid "Network data"
-msgstr ""
-
-#: ./doc/security-guide/ch047_data-encryption.xml:26(para)
-msgid "The ability to encrypt objects in Object Storage is presently limited to disk-level encryption per node. However, there does exist third-party extensions and modules for per-object encryption. These modules have been proposed upstream, but have not per this writing been formally accepted. Below are some pointers:"
-msgstr ""
-
-#: ./doc/security-guide/ch047_data-encryption.xml:27(link)
-msgid "https://github.com/Mirantis/swift-encrypt"
-msgstr ""
-
-#: ./doc/security-guide/ch047_data-encryption.xml:28(link)
-msgid "http://www.mirantis.com/blog/on-disk-encryption-prototype-for-openstack-swift/"
-msgstr ""
-
-#: ./doc/security-guide/ch047_data-encryption.xml:32(para)
-msgid "The ability to encrypt volumes depends on the service backends chosen. Some backends may not support this at all."
-msgstr ""
-
-#: ./doc/security-guide/ch047_data-encryption.xml:33(para)
-msgid "As both block storage and compute support LVM backed storage, we can easily provide an example applicable to both systems. In deployments using LVM, encryption may be performed against the backing physical volumes. An encrypted block device would be created using the standard Linux tools, with the LVM physical volume (PV) created on top of the decrypted block device using pvcreate. Then, the vgcreate or vgmodify tool may be used to add the encrypted physical volume to an LVM volume group (VG)."
-msgstr ""
-
-#: ./doc/security-guide/ch047_data-encryption.xml:34(para)
-msgid "A feature aimed for the Havana release provides encryption of the VM's data before it is written to disk. This allows the privacy of data to be maintained while residing on the storage device. The idea is similar to how self-encrypting drives work. This feature presents a normal block storage device to the VM but encrypts the bytes in the virtualization host before writing them to the disk. The block server operates exactly as it does when reading and writing unencrypted blocks, except special handling will be required for Block Storage features such as snapshots and live migration. Note that this feature uses an independent key manager."
-msgstr ""
-
-#: ./doc/security-guide/ch047_data-encryption.xml:38(para)
-msgid "Tenant data for compute could be encrypted over IPSec or other tunnels. This is not functionality common or standard in OpenStack, but is an option available to motivated and interested implementors."
-msgstr ""
-
-#: ./doc/security-guide/ch047_data-encryption.xml:42(para)
-msgid "Block storage supports a variety of mechanisms for supplying mountable volumes. It is outside the scope of this guide to specify recommendations for each Block Storage backend driver. For the purpose of performance, many storage protocols are unencrypted. Some protocols such as iSCSI can provide authentication and encrypted sessions, it is our recommendation to enable these features."
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch005_security-domains.xml:29(None) ./doc/security-guide/ch005_security-domains.xml:32(None)
-msgid "@@image: 'static/untrusted_trusted.png'; md5=a582dac2ad0b3f439fd4b08386853056"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch005_security-domains.xml:60(None) ./doc/security-guide/ch005_security-domains.xml:63(None)
-msgid "@@image: 'static/bridging_security_domains_1.png'; md5=0d5ca26c51882ce3253405e91a597715"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch005_security-domains.xml:68(None) ./doc/security-guide/ch005_security-domains.xml:71(None)
-msgid "@@image: 'static/bridging_domains_clouduser.png'; md5=17c8a233ee7de17d2f600c7f6f6afe24"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch005_security-domains.xml:134(None) ./doc/security-guide/ch005_security-domains.xml:137(None)
-msgid "@@image: 'static/threat_actors.png'; md5=114c2f9bd9d0319bdd83f9e229d44649"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch005_security-domains.xml:171(None) ./doc/security-guide/ch005_security-domains.xml:174(None)
-msgid "@@image: 'static/high-capability.png'; md5=b7ab599c8b40558a52c0ca86aad89741"
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:8(title)
-msgid "Security boundaries and threats"
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:9(para)
-msgid "A cloud can be abstracted as a collection of logical components by virtue of their function, users, and shared security concerns, which we call security domains. Threat actors and vectors are classified based on their motivation and access to resources. Our goal is to provide you a sense of the security concerns with respect to each domain depending on your risk/vulnerability protection objectives."
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:11(title)
-msgid "Security domains"
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:12(para)
-msgid "A security domain comprises users, applications, servers or networks that share common trust requirements and expectations within a system. Typically they have the same authentication and authorization (AuthN/Z) requirements and users."
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:13(para)
-msgid "Although you may desire to break these domains down further (we later discuss where this may be appropriate), we generally refer to four distinct security domains which form the bare minimum that is required to deploy any OpenStack cloud securely. These security domains are:"
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:15(para) ./doc/security-guide/ch005_security-domains.xml:36(title)
-msgid "Public"
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:18(para) ./doc/security-guide/ch005_security-domains.xml:41(title)
-msgid "Guest"
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:21(para) ./doc/security-guide/ch005_security-domains.xml:46(title)
-msgid "Management"
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:24(para) ./doc/security-guide/ch005_security-domains.xml:51(title)
-msgid "Data"
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:27(para)
-msgid "We selected these security domains because they can be mapped independently or combined to represent the majority of the possible areas of trust within a given OpenStack deployment. For example, some deployment topologies combine both guest and data domains onto one physical network versus others, which have these networks physically separated. In each case, the cloud operator should be aware of the appropriate security concerns. Security domains should be mapped out against your specific OpenStack deployment topology. The domains and their trust requirements depend upon whether the cloud instance is public, private, or hybrid."
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:37(para)
-msgid "The public security domain is an entirely untrusted area of the cloud infrastructure. It can refer to the Internet as a whole or simply to networks over which you have no authority. Any data that transits this domain with confidentiality or integrity requirements should be protected using compensating controls."
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:38(para)
-msgid "This domain should always be considered <emphasis>untrusted</emphasis>."
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:42(para)
-msgid "Typically used for compute instance-to-instance traffic, the guest security domain handles compute data generated by instances on the cloud but not services that support the operation of the cloud, such as API calls."
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:43(para)
-msgid "Public cloud providers and private cloud providers who do not have stringent controls on instance use or who allow unrestricted internet access to VMs should consider this domain to be <emphasis>untrusted</emphasis>. Private cloud providers may want to consider this network as internal and therefore <emphasis>trusted</emphasis> only if they have controls in place to assert that they trust instances and all their tenants."
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:47(para)
-msgid "The management security domain is where services interact. Sometimes referred to as the \"control plane\", the networks in this domain transport confidential data such as configuration parameters, usernames, and passwords. Command and Control traffic typically resides in this domain, which necessitates strong integrity requirements. Access to this domain should be highly restricted and monitored. At the same time, this domain should still employ all of the security best practices described in this guide."
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:48(para)
-msgid "In most deployments this domain is considered <emphasis>trusted</emphasis>. However, when considering an OpenStack deployment, there are many systems that bridge this domain with others, potentially reducing the level of trust you can place on this domain. See <xref linkend=\"ch005_security-domains-idp61360\"/> for more information."
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:52(para)
-msgid "The data security domain is concerned primarily with information pertaining to the storage services within OpenStack. Much of the data that crosses this network has high integrity and confidentiality requirements and depending on the type of deployment there may also be strong availability requirements."
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:53(para)
-msgid "The trust level of this network is heavily dependent on deployment decisions and as such we do not assign this any default level of trust."
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:57(title)
-msgid "Bridging security domains"
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:58(para)
-msgid "A <emphasis>bridge</emphasis> is a component that exists inside more than one security domain. Any component that bridges security domains with different trust levels or authentication requirements must be carefully configured. These bridges are often the weak points in network architecture. A bridge should always be configured to meet the security requirements of the highest trust level of any of the domains it is bridging. In many cases the security controls for bridges should be a primary concern due to the likelihood of attack."
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:66(para)
-msgid "The diagram above shows a compute node bridging the data and management domains, as such the compute node should be configured to meet the security requirements of the management domain. Similarly the API Endpoint in this diagram is bridging the untrusted public domain and the management domain, and should be configured to protect against attacks from the public domain propagating through to the management domain."
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:74(para)
-msgid "In some cases deployers may want to consider securing a bridge to a higher standard than any of the domains in which it resides. Given the above example of an API endpoint, an adversary could potentially target the API endpoint from the public domain, leveraging it in the hopes of compromising or gaining access to the management domain."
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:75(para)
-msgid "The design of OpenStack is such that separation of security domains is difficult - as core services will usually bridge at least two domains, special consideration must be given when applying security controls to them."
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:78(title)
-msgid "Threat classification, actors and attack vectors"
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:79(para)
-msgid "Most types of cloud deployment, public or private, are exposed to some form of attack. In this chapter we categorize attackers and summarize potential types of attacks in each security domain."
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:81(title)
-msgid "Threat actors"
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:82(para)
-msgid "A threat actor is an abstract way to refer to a class of adversary that you may attempt to defend against. The more capable the actor, the more expensive the security controls that are required for successful attack mitigation and prevention. Security is a tradeoff between cost, usability and defense. In some cases it will not be possible to secure a cloud deployment against all of the threat actors we describe here. Those deploying an OpenStack cloud will have to decide where the balance lies for their deployment / usage."
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:92(para)
-msgid "<emphasis role=\"bold\">Intelligence services</emphasis> — Considered by this guide as the most capable adversary. Intelligence Services and other state actors can bring tremendous resources to bear on a target. They have capabilities beyond that of any other actor. It is very difficult to defend against these actors without incredibly stringent controls in place, both human and technical."
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:102(para)
-msgid "<emphasis role=\"bold\">Serious organized crime</emphasis> — Highly capable and financially driven groups of attackers. Able to fund in-house exploit development and target research. In recent years the rise of organizations such as the Russian Business Network, a massive cyber-criminal enterprise has demonstrated how cyber attacks have become a commodity. Industrial espionage falls within the SOC group."
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:112(para)
-msgid "<emphasis role=\"bold\">Highly capable groups</emphasis> — This refers to 'Hacktivist' type organizations who are not typically commercially funded but can pose a serious threat to service providers and cloud operators."
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:119(para)
-msgid "<emphasis role=\"bold\">Motivated individuals</emphasis> — Acting alone, these attackers come in many guises, such as rogue or malicious employees, disaffected customers, or small-scale industrial espionage."
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:126(para)
-msgid "<emphasis role=\"bold\">Script kiddies</emphasis> — Automated vulnerability scanning/exploitation. Non-targeted attacks. Often only a nuisance, compromise by one of these actors presents a major risk to an organization's reputation."
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:142(title)
-msgid "Public and private cloud considerations"
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:143(para)
-msgid "Private clouds are typically deployed by enterprises or institutions inside their networks and behind their firewalls. Enterprises will have strict policies on what data is allowed to exit their network and may even have different clouds for specific purposes. Users of a private cloud are typically employees of the organization that owns the cloud and are able to be held accountable for their actions. Employees often attend training sessions before accessing the cloud and will likely take part in regular scheduled security awareness training. Public clouds by contrast cannot make any assertions about their users, cloud use-cases or user motivations. This immediately pushes the guest security domain into a completely <emphasis>untrusted</emphasis> state for public cloud providers."
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:144(para)
-msgid "A notable difference in the attack surface of public clouds is that they must provide internet access to their services. Instance connectivity, access to files over the internet and the ability to interact with the cloud controlling fabric such as the API endpoints and dashboard are must-haves for the public cloud."
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:145(para)
-msgid "Privacy concerns for public and private cloud users are typically diametrically opposed. The data generated and stored in private clouds is normally owned by the operator of the cloud, who is able to deploy technologies such as data loss prevention (DLP) protection, file inspection, deep packet inspection and prescriptive firewalling. In contrast, privacy is one of the primary barriers to adoption for the public cloud, as many of these controls do not exist."
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:148(title)
-msgid "Outbound attacks and reputational risk"
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:149(para)
-msgid "Careful consideration should be given to potential outbound abuse from a cloud deployment. Whether public or private, clouds tend to have lots of resource available. An attacker who has established a point of presence within the cloud, either through hacking or entitled access, such as rogue employee, can bring these resources to bear against the internet at large. Clouds with Compute services make for ideal DDoS and brute force engines. The issue is more pressing for public clouds as their users are largely unaccountable, and can quickly spin up numerous disposable instances for outbound attacks. Major damage can be inflicted upon a company's reputation if it becomes known for hosting malicious software or launching attacks on other networks. Methods of prevention include egress security groups, outbound traffic inspection, customer education and awareness, and fraud and abuse mitigation strategies."
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:168(title)
-msgid "Attack types"
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:169(para)
-msgid "The diagram shows the types of attacks that may be expected from the actors described in the previous section. Note that there will always be exceptions to this diagram but in general, this describes the sorts of attack that could be typical for each actor."
-msgstr ""
-
-#: ./doc/security-guide/ch005_security-domains.xml:177(para)
-msgid "The prescriptive defense for each form of attack is beyond the scope of this document. The above diagram can assist you in making an informed decision about which types of threats, and threat actors, should be protected against. For commercial public cloud deployments this might include prevention against serious crime. For those deploying private clouds for government use, more stringent protective mechanisms should be in place, including carefully protected facilities and supply chains. In contrast those standing up basic development or test environments will likely require less restrictive controls (middle of the spectrum)."
-msgstr ""
-
-#: ./doc/security-guide/ch035_case-studies-networking.xml:8(title)
-msgid "Case studies: Networking"
-msgstr ""
-
-#: ./doc/security-guide/ch035_case-studies-networking.xml:9(para)
-msgid "In this case study we discuss how Alice and Bob would address providing networking services to the user."
-msgstr ""
-
-#: ./doc/security-guide/ch035_case-studies-networking.xml:12(para)
-msgid "A key objective of Alice's cloud is to integrate with the existing auth services and security resources. The key design parameters for this private cloud are a limited scope of tenants, networks and workload type. This environment can be designed to limit what available network resources are available to the tenant and what are the various default quotas and security policies are available. The network policy engine can be modified to restrict creation and changes to network resources. In this environment, Alice might want to leverage nova-network in the application of security group polices on a per instance basis vs. neutron's application of security group polices on a per port basis. L2 isolation in this environment would leverage VLAN tagging. The use of VLAN tags will allow great visibility of tenant traffic by leveraging existing features and tools of the physical infrastructure."
-msgstr ""
-
-#: ./doc/security-guide/ch035_case-studies-networking.xml:30(para)
-msgid "A major business driver for Bob is to provide an advanced networking services to his customers. Bob's customers would like to deploy multi-tiered application stacks. This multi-tiered application are either existing enterprise application or newly deployed applications. Since Bob's public cloud is a multi-tenancy enterprise service, the choice to use for L2 isolation in this environment is to use overlay networking. Another aspect of Bob's cloud is the self-service aspect where the customer can provision available networking services as needed. These networking services encompass L2 networks, L3 Routing, Network <glossterm>ACL</glossterm> and NAT. It is important that per-tenant quota's be implemented in this environment."
-msgstr ""
-
-#: ./doc/security-guide/ch035_case-studies-networking.xml:43(para)
-msgid "An added benefit with utilizing OpenStack Networking is when new advanced networking services become available, these new features can be easily provided to the end customers."
-msgstr ""
-
-#: ./doc/security-guide/ch011_management-introduction.xml:8(title)
-msgid "Management introduction"
-msgstr ""
-
-#: ./doc/security-guide/ch011_management-introduction.xml:9(para)
-msgid "A cloud deployment is a living system. Machines age and fail, software becomes outdated, vulnerabilities are discovered. When errors or omissions are made in configuration, or when software fixes must be applied, these changes must be made in a secure, but convenient, fashion. These changes are typically solved through configuration management."
-msgstr ""
-
-#: ./doc/security-guide/ch011_management-introduction.xml:10(para)
-msgid "Likewise, it is important to protect the cloud deployment from being configured or manipulated by malicious entities. With many systems in a cloud employing compute and networking virtualization, there are distinct challenges applicable to OpenStack which must be addressed through integrity lifecycle management."
-msgstr ""
-
-#: ./doc/security-guide/ch011_management-introduction.xml:11(para)
-msgid "Finally, administrators must perform command and control over the cloud for various operational functions. It is important these command and control facilities are understood and secured."
-msgstr ""
-
-#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:8(title)
-msgid "Case studies: tenant data"
-msgstr ""
-
-#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:9(para)
-msgid "Returning to Alice and Bob, we will use this section to dive into their particular tenant data privacy requirements. Specifically, we will look into how Alice and Bob both handle tenant data, data destruction, and data encryption."
-msgstr ""
-
-#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:18(para)
-msgid "As stated during the introduction to Alice's case study, data protection is of an extremely high priority. She needs to ensure that a compromise of one tenant's data does not cause loss of other tenant data. She also has strong regulator requirements that require documentation of data destruction activities. Alice does this using the following:"
-msgstr ""
-
-#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:28(para)
-msgid "Establishing procedures to sanitize tenant data when a program or project ends."
-msgstr ""
-
-#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:32(para)
-msgid "Track the destruction of both the tenant data and metadata through ticketing in a CMDB."
-msgstr ""
-
-#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:35(para) ./doc/security-guide/ch049_case-studies-tenant-data.xml:69(para)
-msgid "For Volume storage:"
-msgstr ""
-
-#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:38(para) ./doc/security-guide/ch049_case-studies-tenant-data.xml:72(para)
-msgid "Physical server issues"
-msgstr ""
-
-#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:41(para)
-msgid "To provide secure ephemeral instance storage, Alice implements qcow2 files on an encrypted filesystem."
-msgstr ""
-
-#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:51(para)
-msgid "As stated during the introduction to Bob's case study, tenant privacy is of an extremely high priority. In addition to the requirements and actions Bob will take to isolate tenants from one another at the infrastructure layer, Bob also needs to provide assurances for tenant data privacy. Bob does this using the following:"
-msgstr ""
-
-#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:61(para)
-msgid "Establishing procedures to sanitize customer data when a customer churns."
-msgstr ""
-
-#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:65(para)
-msgid "Track the destruction of both the customer data and metadata through ticketing in a CMDB."
-msgstr ""
-
-#: ./doc/security-guide/ch049_case-studies-tenant-data.xml:75(para)
-msgid "To provide secure ephemeral instance storage, Bob implements qcow2 files on an encrypted filesystems."
-msgstr ""
-
-#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml:8(title)
-msgid "Case studies: instance isolation"
-msgstr ""
-
-#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml:9(para)
-msgid "In this case study we discuss how Alice and Bob would ensure that their instances are properly isolated. First we consider hypervisor selection, and then techniques for hardening QEMU and applying mandatory access controls."
-msgstr ""
-
-#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml:12(para)
-msgid "Alice chooses Xen for the hypervisor in her cloud due to a strong internal knowledge base and a desire to use the Xen security modules (XSM) for fine-grained policy enforcement."
-msgstr ""
-
-#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml:13(para)
-msgid "Alice is willing to apply a relatively large amount of resources to software packaging and maintenance. She will use these resources to build a highly customized version of QEMU that has many components removed, thereby reducing the attack surface. She will also ensure that all compiler hardening options are enabled for QEMU. Alice accepts that these decisions will increase long-term maintenance costs."
-msgstr ""
-
-#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml:14(para)
-msgid "Alice writes XSM policies (for Xen) and SELinux policies (for Linux domain 0, and device domains) to provide stronger isolation between the instances. Alice also uses the Intel TXT support in Xen to measure the hypervisor launch in the TPM."
-msgstr ""
-
-#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml:18(para)
-msgid "Bob is very concerned about instance isolation since the users in a public cloud represent anyone with a credit card, meaning they are inherently untrusted. Bob has just started hiring the team that will deploy the cloud, so he can tailor his candidate search for specific areas of expertise. With this in mind, Bob chooses a hypervisor based on its technical features, certifications, and community support. KVM has an EAL 4+ common criteria rating, with a labeled security protection profile (LSPP) to provide added assurance for instance isolation. This, combined with the strong support for KVM within the OpenStack community drives Bob's decision to use KVM."
-msgstr ""
-
-#: ./doc/security-guide/ch053_case-studies-instance-isolation.xml:19(para)
-msgid "Bob weighs the added cost of repackaging QEMU and decides that he cannot commit those resources to the project. Fortunately, his Linux distribution has already enabled the compiler hardening options. So he decides to use this QEMU package. Finally, Bob leverages sVirt to manage the SELinux polices associated with the virtualization stack."
-msgstr ""
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:12(title)
-msgid "Networking services security best practices"
-msgstr ""
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:13(para)
-msgid "This section discusses OpenStack Networking configuration best practices as they apply to tenant network security within your OpenStack deployment."
-msgstr ""
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:15(title)
-msgid "Tenant network services workflow"
-msgstr ""
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:16(para)
-msgid "OpenStack Networking provides users real self services of network resources and configurations. It is important that cloud architects and operators evaluate their design use cases in providing users the ability to create, update, and destroy available network resources."
-msgstr ""
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:19(title)
-msgid "Networking resource policy engine"
-msgstr ""
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:20(para)
-msgid "A policy engine and its configuration file, <filename>policy.json</filename>, within OpenStack Networking provides a method to provide finer grained authorization of users on tenant networking methods and objects. It is important that cloud architects and operators evaluate their design and use cases in providing users and tenants the ability to create, update, and destroy available network resources as it has a tangible effect on tenant network availability, network security, and overall OpenStack security. For a more detailed explanation of OpenStack Networking policy definition, please refer to the <link href=\"http://docs.openstack.org/admin-guide-cloud/content/section_networking_auth.html\">Authentication and authorization section</link> in the <citetitle>OpenStack Cloud Administrator Guide</citetitle>."
-msgstr ""
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:34(para)
-msgid "It is important to review the default networking resource policy and modify the policy appropriately for your security posture."
-msgstr ""
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:37(para)
-msgid "If your deployment of OpenStack provides multiple external access points into different security domains it is important that you limit the tenant's ability to attach multiple vNICs to multiple external access pointsthis would bridge these security domains and could lead to unforeseen security compromise. It is possible mitigate this risk by utilizing the host aggregates functionality provided by OpenStack Compute or through splitting the tenant VMs into multiple tenant projects with different virtual network configurations."
-msgstr ""
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:48(title)
-msgid "Security groups"
-msgstr ""
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:49(para)
-msgid "The OpenStack Networking Service provides security group functionality using a mechanism that is more flexible and powerful than the security group capabilities built into OpenStack Compute. Thus, when using OpenStack Networking, <filename>nova.conf</filename> should always disable built-in security groups and proxy all security group calls to the OpenStack Networking API. Failure to do so will result in conflicting security policies being simultaneously applied by both services. To proxy security groups to OpenStack Networking, use the following configuration values:"
-msgstr ""
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:61(para)
-msgid "<option>firewall_driver</option> must be set to <literal>nova.virt.firewall.NoopFirewallDriver</literal> so that <systemitem class=\"service\">nova-compute</systemitem> does not perform iptables-based filtering itself."
-msgstr ""
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:67(para)
-msgid "<option>security_group_api</option> must be set to <literal>neutron</literal> so that all security group requests are proxied to the OpenStack Networking service."
-msgstr ""
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:73(para)
-msgid "Security groups and security group rules allow administrators and tenants the ability to specify the type of traffic and direction (ingress/egress) that is allowed to pass through a virtual interface port. A security group is a container for security group rules. When a virtual interface port is created in OpenStack Networking it is associated with a security group. If a security group is not specified, the port will be associated with a 'default' security group. By default this group will drop all ingress traffic and allow all egress. Rules can be added to this group in order to change the behaviour."
-msgstr ""
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:74(para)
-msgid "When using the security group API through OpenStack Compute, security groups are applied to all virtual interface ports on an instance. The reason for this is that OpenStack Compute security group APIs are instance based and not virtual interface port based as OpenStack Networking."
-msgstr ""
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:77(title)
-msgid "Quotas"
-msgstr ""
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:79(para)
-msgid "Quotas provide the ability to limit the number of network resources available to tenants. You can enforce default quotas for all tenants. The <filename>/etc/neutron/neutron.conf</filename> includes these options for quota:"
-msgstr ""
-
-#: ./doc/security-guide/ch034_tenant-secure-networking-best-practices.xml:108(para)
-msgid "OpenStack Networking also supports per-tenant quotas limit through a quota extension API. To enable per-tenant quotas, you must set the <literal>quota_driver</literal> option in <filename>neutron.conf</filename>."
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/security-guide/ch052_devices.xml:305(None) ./doc/security-guide/ch052_devices.xml:309(None)
-msgid "@@image: 'static/sVirt Diagram 1.png'; md5=ffcdbb45d9054670ad4c270a7c7d3925"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:12(title)
-msgid "Hardening the virtualization layers"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:13(para)
-msgid "In the beginning of this chapter we discuss the use of both physical and virtual hardware by instances, the associated security risks, and some recommendations for mitigating those risks. We conclude the chapter with a discussion of sVirt, an open source project for integrating SELinux mandatory access controls with the virtualization components."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:21(title)
-msgid "Physical hardware (PCI passthrough)"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:22(para)
-msgid "Many hypervisors offer a functionality known as PCI passthrough. This allows an instance to have direct access to a piece of hardware on the node. For example, this could be used to allow instances to access video cards offering the compute unified device architecture (CUDA) for high performance computation. This feature carries two types of security risks: direct memory access and hardware infection."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:31(para)
-msgid "Direct memory access (DMA) is a feature that permits certain hardware devices to access arbitrary physical memory addresses in the host computer. Often video cards have this capability. However, an instance should not be given arbitrary physical memory access because this would give it full view of both the host system and other instances running on the same node. Hardware vendors use an input/output memory management unit (IOMMU) to manage DMA access in these situations. Therefore, cloud architects should ensure that the hypervisor is configured to utilize this hardware feature."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:45(para)
-msgid "KVM: <link href=\"http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM\">How to assign devices with VT-d in KVM</link>"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:50(para)
-msgid "Xen: <link href=\"http://wiki.xen.org/wiki/VTd_HowTo\">VTd Howto</link>"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:55(para)
-msgid "The IOMMU feature is marketed as VT-d by Intel and AMD-Vi by AMD."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:59(para)
-msgid "A hardware infection occurs when an instance makes a malicious modification to the firmware or some other part of a device. As this device is used by other instances, or even the host OS, the malicious code can spread into these systems. The end result is that one instance can run code outside of its security domain. This is a potential problem in any hardware sharing scenario. The problem is specific to this scenario because it is harder to reset the state of physical hardware than virtual hardware."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:69(para)
-msgid "Solutions to the hardware infection problem are domain specific. The strategy is to identify how an instance can modify hardware state then determine how to reset any modifications when the instance is done using the hardware. For example, one option could be to re-flash the firmware after use. Clearly there is a need to balance hardware longevity with security as some firmwares will fail after a large number of writes. TPM technology, described in <xref linkend=\"ch013_node-bootstrapping-idp44768\"/>, provides a solution for detecting unauthorized firmware changes. Regardless of the strategy selected, it is important to understand the risks associated with this kind of hardware sharing so that they can be properly mitigated for a given deployment scenario."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:85(para)
-msgid "Additionally, due to the risk and complexities associated with PCI passthrough, it should be disabled by default. If enabled for a specific need, you will need to have appropriate processes in place to ensure the hardware is clean before re-issue."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:93(title)
-msgid "Virtual hardware (QEMU)"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:94(para)
-msgid "When running a virtual machine, virtual hardware is a software layer that provides the hardware interface for the virtual machine. Instances use this functionality to provide network, storage, video, and other devices that may be needed. With this in mind, most instances in your environment will exclusively use virtual hardware, with a minority that will require direct hardware access. The major open source hypervisors use QEMU for this functionality. While QEMU fills an important need for virtualization platforms, it has proven to be a very challenging software project to write and maintain. Much of the functionality in QEMU is implemented with low-level code that is difficult for most developers to comprehend. Furthermore, the hardware virtualized by QEMU includes many legacy devices that have their own set of quirks. Putting all of this together, QEMU has been the source of many security problems, including hypervisor breakout attacks."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:112(para)
-msgid "For the reasons stated above, it is important to take proactive steps to harden QEMU. We recommend three specific steps: minimizing the code base, using compiler hardening, and using mandatory access controls, such as sVirt, SELinux, or AppArmor."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:119(title)
-msgid "Minimizing the QEMU code base"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:120(para)
-msgid "One classic security principle is to remove any unused components from your system. QEMU provides support for many different virtual hardware devices. However, only a small number of devices are needed for a given instance. Most instances will use the virtio devices. However, some legacy instances will need access to specific hardware, which can be specified using glance metadata:"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:133(para)
-msgid "A cloud architect should decide what devices to make available to cloud users. Anything that is not needed should be removed from QEMU. This step requires recompiling QEMU after modifying the options passed to the QEMU configure script. For a complete list of up-to-date options simply run <placeholder-1/> from within the QEMU source directory. Decide what is needed for your deployment, and disable the remaining options."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:144(title)
-msgid "Compiler hardening"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:145(para)
-msgid "The next step is to harden QEMU using compiler hardening options. Modern compilers provide a variety of compile time options to improve the security of the resulting binaries. These features, which we will describe in more detail below, include relocation read-only (RELRO), stack canaries, never execute (NX), position independent executable (PIE), and address space layout randomization (ASLR)."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:154(para)
-msgid "Many modern linux distributions already build QEMU with compiler hardening enabled, so you may want to verify your existing executable before proceeding with the information below. One tool that can assist you with this verification is called <link href=\"http://www.trapkit.de/tools/checksec.html\"><literal>checksec.sh</literal></link>."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:163(term)
-msgid "RELocation Read-Only (RELRO)"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:165(para)
-msgid "Hardens the data sections of an executable. Both full and partial RELRO modes are supported by gcc. For QEMU full RELRO is your best choice. This will make the global offset table read-only and place various internal data sections before the program data section in the resulting executable."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:175(term)
-msgid "Stack canaries"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:177(para)
-msgid "Places values on the stack and verifies their presence to help prevent buffer overflow attacks."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:183(term)
-msgid "Never eXecute (NX)"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:185(para)
-msgid "Also known as Data Execution Prevention (DEP), ensures that data sections of the executable can not be executed."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:192(term)
-msgid "Position Independent Executable (PIE)"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:194(para)
-msgid "Produces a position independent executable, which is necessary for ASLR."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:200(term)
-msgid "Address Space Layout Randomization (ASLR)"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:202(para)
-msgid "This ensures that placement of both code and data regions will be randomized. Enabled by the kernel (all modern linux kernels support ASLR), when the executable is built with PIE."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:210(para)
-msgid "Putting this all together, and adding in some additional useful protections, we recommend the following compiler options for GCC when compiling QEMU:"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:217(para)
-msgid "We recommend testing your QEMU executable file after it is compiled to ensure that the compiler hardening worked properly."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:221(para)
-msgid "Most cloud deployments will not want to build software such as QEMU by hand. It is better to use packaging to ensure that the process is repeatable and to ensure that the end result can be easily deployed throughout the cloud. The references below provide some additional details on applying compiler hardening options to existing packages."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:230(para)
-msgid "DEB packages: <link href=\"http://wiki.debian.org/HardeningWalkthrough\">Hardening Walkthrough</link>"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:233(para)
-msgid "RPM packages: <link href=\"http://fedoraproject.org/wiki/How_to_create_an_RPM_package\">How to create an RPM package</link>"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:239(para)
-msgid "Compiler hardening makes it more difficult to attack the QEMU process. However, if an attacker does succeed, we would like to limit the impact of the attack. Mandatory access controls accomplish this by restricting the privileges on QEMU process to only what is needed. This can be accomplished using sVirt / SELinux or AppArmor. When using sVirt, SELinux is configured to run every QEMU process under a different security context. AppArmor can be configured to provide similar functionality. We provide more details on sVirt in the instance isolation section below."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:253(title)
-msgid "sVirt: SELinux and virtualization"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:254(para)
-msgid "With unique kernel-level architecture and National Security Agency (NSA) developed security mechanisms, KVM provides foundational isolation technologies for multi tenancy. With developmental origins dating back to 2002, the Secure Virtualization (sVirt) technology is the application of SELinux against modern day virtualization. SELinux, which was designed to apply separation control based upon labels, has been extended to provide isolation between virtual machine processes, devices, data files and system processes acting upon their behalf."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:265(para)
-msgid "OpenStack's sVirt implementation aspires to protect hypervisor hosts and virtual machines against two primary threat vectors:"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:270(para)
-msgid "<emphasis role=\"bold\">Hypervisor threats</emphasis> A compromised application running within a virtual machine attacks the hypervisor to access underlying resources. For example, the host OS, applications, or devices within the physical machine. This is a threat vector unique to virtualization and represents considerable risk as the underlying real machine can be compromised due to vulnerability in a single virtual application."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:280(para)
-msgid "<emphasis role=\"bold\">Virtual Machine (multi-tenant) threats</emphasis> A compromised application running within a VM attacks the hypervisor to access/control another virtual machine and its resources. This is a threat vector unique to virtualization and represents considerable risk as a multitude of virtual machine file images could be compromised due to vulnerability in a single application. This virtual network attack is a major concern as the administrative techniques for protecting real networks do not directly apply to the virtual environment."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:293(para)
-msgid "Each KVM-based virtual machine is a process which is labeled by SELinux, effectively establishing a security boundary around each virtual machine. This security boundary is monitored and enforced by the Linux kernel, restricting the virtual machine's access to resources outside of its boundary such as host machine data files or other VMs."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:313(para)
-msgid "As shown above, sVirt isolation is provided regardless of the guest Operating System running inside the virtual machineLinux or Windows VMs can be used. Additionally, many Linux distributions provide SELinux within the operating system, allowing the virtual machine to protect internal virtual resources from threats."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:322(title)
-msgid "Labels and categories"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:323(para)
-msgid "KVM-based virtual machine instances are labelled with their own SELinux data type, known as svirt_image_t. Kernel level protections prevent unauthorized system processes, such as malware, from manipulating the virtual machine image files on disk. When virtual machines are powered off, images are stored as svirt_image_t as shown below:"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:334(para)
-msgid "The <literal>svirt_image_t</literal> label uniquely identifies image files on disk, allowing for the SELinux policy to restrict access. When a KVM-based Compute image is powered on, sVirt appends a random numerical identifier to the image. sVirt is technically capable of assigning numerical identifiers to 524,288 virtual machines per hypervisor node, however OpenStack deployments are highly unlikely to encounter this limitation."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:343(para)
-msgid "This example shows the sVirt category identifier:"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:348(title)
-msgid "Booleans"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:349(para)
-msgid "To ease the administrative burden of managing SELinux, many enterprise Linux platforms utilize SELinux Booleans to quickly change the security posture of sVirt."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:353(para)
-msgid "Red Hat Enterprise Linux-based KVM deployments utilize the following sVirt booleans:"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:361(emphasis)
-msgid "sVirt SELinux Boolean"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:367(para)
-msgid "virt_use_common"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:368(para)
-msgid "Allow virt to use serial/parallel communication ports."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:371(para)
-msgid "virt_use_fusefs"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:372(para)
-msgid "Allow virt to read FUSE mounted files."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:375(para)
-msgid "virt_use_nfs"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:376(para)
-msgid "Allow virt to manage NFS mounted files."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:379(para)
-msgid "virt_use_samba"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:380(para)
-msgid "Allow virt to manage CIFS mounted files."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:383(para)
-msgid "virt_use_sanlock"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:384(para)
-msgid "Allow confined virtual guests to interact with the sanlock."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:387(para)
-msgid "virt_use_sysfs"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:388(para)
-msgid "Allow virt to manage device configuration (PCI)."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:391(para)
-msgid "virt_use_usb"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:392(para)
-msgid "Allow virt to use USB devices."
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:395(para)
-msgid "virt_use_xserver"
-msgstr ""
-
-#: ./doc/security-guide/ch052_devices.xml:396(para)
-msgid "Allow virtual machine to interact with the X Window System."
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:8(title)
-msgid "SSL proxies and HTTP services"
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:9(para)
-msgid "OpenStack endpoints are HTTP services providing APIs to both end-users on public networks and to other OpenStack services within the same deployment operating over the management network. It is highly recommended these requests, both those internal and external, operate over SSL."
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:10(para)
-msgid "In order for API requests to be encrypted by SSL it's necessary to position the API services behind a proxy that will establish and terminate SSL sessions. The following table offers a non-exhaustive list of software services that can proxy SSL traffic for API requests:"
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:12(link)
-msgid "Pound"
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:15(link) ./doc/security-guide/ch020_ssl-everywhere.xml:153(title)
-msgid "Stud"
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:18(link) ./doc/security-guide/ch020_ssl-everywhere.xml:191(title)
-msgid "nginx"
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:21(link)
-msgid "Apache httpd"
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:24(para)
-msgid "Hardware appliance SSL acceleration proxies"
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:27(para)
-msgid "It is important to be mindful of the size of requests that will be processed by any chosen SSL proxy."
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:29(title)
-msgid "Examples"
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:30(para)
-msgid "Below we provide some sample recommended configuration settings for enabling SSL in some of the more popular web servers/SSL terminators. Note that we have SSL v3 enabled in some of these examples as this will be required in many deployments for client compatibility."
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:31(para)
-msgid "Before we delve into the configurations, we briefly discuss the ciphers' configuration element and its format. A more exhaustive treatment on available ciphers and the OpenSSL cipher list format can be found at: <link href=\"https://www.openssl.org/docs/apps/ciphers.html\">ciphers</link>."
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:35(para)
-msgid "or"
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:39(para)
-msgid "Cipher string options are separated by \":\", while \"!\" provides negation of the immediately following element. Element order indicates preference unless overridden by qualifiers such as HIGH. Let us take a closer look at the elements in the above sample strings."
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:42(code)
-msgid "kEECDH:kEDH"
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:44(para)
-msgid "Ephemeral Elliptic Curve Diffie-Hellman (abbreviated as EECDH and ECDHE)."
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:45(para)
-msgid "Ephemeral Diffie-Hellman (abbreviated either as EDH or DHE) uses prime field groups."
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:46(para)
-msgid "Both approaches provide <link href=\"http://en.wikipedia.org/wiki/Forward_secrecy\">Perfect Forward Secrecy (PFS)</link>."
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:47(para)
-msgid "Ephemeral Elliptic Curves require the server to be configured with a named curve, and provide better security than prime field groups and at lower computational cost. However, prime field groups are more widely implemented, and thus typically both are included in list."
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:51(code)
-msgid "kRSA"
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:53(para)
-msgid "Cipher suites using the <link href=\"http://en.wikipedia.org/wiki/RSA_%28cryptosystem%29\">RSA</link> exchange, authentication or either respectively."
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:57(code)
-msgid "HIGH"
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:59(para)
-msgid "Selects highest possible security cipher in the negotiation phase. These typically have keys of length 128 bits or longer."
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:63(code)
-msgid "!RC4"
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:65(para)
-msgid "No RC4. RC4 has flaws in the context of TLS/SSL V3. See <link href=\"cr.yp.to/streamciphers/rc4biases-20130708.pdf\"> On the Security of RC4 in TLS and WPA</link>."
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:69(code)
-msgid "!MD5"
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:71(para)
-msgid "No MD5. MD5 is not collision resistant, and thus not acceptable for Message Authentication Codes (MAC) or signatures."
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:75(code)
-msgid "!aNULL:!eNULL"
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:77(para)
-msgid "Disallows clear text"
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:81(code)
-msgid "!EXP"
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:83(para)
-msgid "Disallows export encryption algorithms, which by design tend to were weak, typically using 40 and 56 bit keys."
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:84(para)
-msgid "US Export restrictions on cryptography systems have been lifted and no longer need to be supported."
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:88(code)
-msgid "!LOW:!MEDIUM"
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:90(para)
-msgid "Disallows low (keys 56 or 64 bits long) and medium (128 bit long keys) ciphers because of their vulnerability to brute force attacks (example 2-DES). This constraint leaves acceptable Triple Data Encryption Standard (Triple DES) also known as Triple Data Encryption Algorithm (TDEA) and the Advanced Encryption Standard (AES), each of which has keys greater than equal to 128 bits and thus more secure."
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:94(code)
-msgid "Protocols"
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:96(para)
-msgid "Protocols are enabled/disabled through SSL_CTX_set_options. We recommend disabling SSLv2 and enabling TLS or SSLv3 (which was standardised as TLS with a few changes)."
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:101(title)
-msgid "Pound - with AES-NI acceleration"
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:154(para)
-msgid "This stud example enables SSL v3 for client compatibility. The ciphers line can be tweaked based on your needs, however this is a reasonable starting place."
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:192(para)
-msgid "This nginx example requires TLS v1.1 or v1.2 for maximum security. The ssl_ciphers line can be tweaked based on your needs, however this is a reasonable starting place."
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:208(title)
-msgid "Apache"
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:233(para)
-msgid "Compute API SSL endpoint in Apache, which you must pair with a short WSGI script."
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:257(title)
-msgid "HTTP strict transport security"
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:258(para)
-msgid "We recommend that all production deployments use HSTS. This header prevents browsers from making insecure connections after they have made a single secure one. If you have deployed your HTTP services on a public or an untrusted domain, HSTS is especially important. To enable HSTS, configure your web server to send a header like this with all requests:"
-msgstr ""
-
-#: ./doc/security-guide/ch020_ssl-everywhere.xml:260(para)
-msgid "Start with a short timeout of 1 day during testing, and raise it to one year after testing has shown that you haven't introduced problems for users. Note that once this header is set to a large timeout, it is (by design) very difficult to disable."
-msgstr ""
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml:8(title)
-msgid "Forensics and incident response"
-msgstr ""
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml:9(para)
-msgid "A lot of activity goes on within a cloud environment. It is a mix of hardware, operating systems, virtual machine managers, the OpenStack services, cloud-user activity such as creating instances and attaching storage, the network underlying the whole, and finally end-users using the applications running on the various instances."
-msgstr ""
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml:10(para)
-msgid "The generation and collection of logs is an important component of securely monitoring an OpenStack infrastructure. Logs provide visibility into the day-to-day actions of administrators, tenants, and guests, in addition to the activity in the compute, networking, and storage and other components that comprise your OpenStack deployment."
-msgstr ""
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml:11(para)
-msgid "The basics of logging: configuration, setting log level, location of the log files, and how to use and customize logs, as well as how to do centralized collections of logs is well covered in the <link href=\"http://docs.openstack.org/ops/\"><citetitle>OpenStack Operations Guide</citetitle></link>."
-msgstr ""
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml:12(para)
-msgid "Logs are not only valuable for proactive security and continuous compliance activities, but they are also a valuable information source for investigating and responding to incidents."
-msgstr ""
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml:13(para)
-msgid "For instance, analyzing the access logs of Identity Service or its replacement authentication system would alert us to failed logins, their frequency, origin IP, whether the events are restricted to select accounts etc. Log analysis supports detection."
-msgstr ""
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml:14(para)
-msgid "On detection, further action may be to black list an IP, or recommend strengthening user passwords, or even de-activating a user account if it is deemed dormant."
-msgstr ""
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml:16(title)
-msgid "Monitoring use cases"
-msgstr ""
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml:17(para)
-msgid "Monitoring events is more pro-active and provides real-time detection and response. There are several tools to aid in monitoring."
-msgstr ""
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml:18(para)
-msgid "In the case of an OpenStack cloud instance, we need to monitor the hardware, the OpenStack services, and the cloud resource usage. The last stems from wanting to be elastic, to scale to the dynamic needs of the users."
-msgstr ""
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml:19(para)
-msgid "Here are a few important use cases to consider when implementing log aggregation, analysis and monitoring. These use cases can be implemented and monitored through various commercial and open source tools, homegrown scripts, etc. These tools and scripts can generate events that can then be sent to the administrators through email or integrated dashboard. It is important to consider additional use cases that may apply to your specific network and what you may consider anomalous behavior."
-msgstr ""
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml:21(para)
-msgid "Detecting the absence of log generation is an event of high value. Such an event would indicate a service failure or even an intruder who has temporarily switched off logging or modified the log level to hide their tracks."
-msgstr ""
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml:25(para)
-msgid "Application events such as start and/or stop that were unscheduled would also be events to monitor and examine for possible security implications."
-msgstr ""
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml:29(para)
-msgid "OS events on the OpenStack service machines such as user logins, restarts also provide valuable insight into use/misuse"
-msgstr ""
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml:33(para)
-msgid "Being able to detect the load on the OpenStack servers also enables responding by way of introducing additional servers for load balancing to ensure high availability."
-msgstr ""
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml:37(para)
-msgid "Other events that are actionable are networking bridges going down, ip tables being flushed on compute nodes and consequential loss of access to instances resulting in unhappy customers."
-msgstr ""
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml:41(para)
-msgid "To reduce security risks from orphan instances on a user/tenant/domain deletion in the Identity service there is discussion to generate notifications in the system and have OpenStack components respond to these events as appropriate such as terminating instances, disconnecting attached volumes, reclaiming CPU and storage resources etc."
-msgstr ""
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml:44(para)
-msgid "A cloud will host many virtual instances, and monitoring these instances goes beyond hardware monitoring and log files which may just contain CRUD events."
-msgstr ""
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml:45(para)
-msgid "Security monitoring controls such as intrusion detection software, antivirus software, and spyware detection and removal utilities can generate logs that show when and how an attack or intrusion took place. Deploying these tools on the cloud machines provides value and protection. Cloud users, those running instances on the cloud may also want to run such tools on their instances."
-msgstr ""
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml:49(link)
-msgid "http://www.mirantis.com/blog/openstack-monitoring/"
-msgstr ""
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml:50(link)
-msgid "http://blog.sflow.com/2012/01/host-sflow-distributed-agent.html"
-msgstr ""
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml:51(link)
-msgid "http://blog.sflow.com/2009/09/lan-and-wan.html"
-msgstr ""
-
-#: ./doc/security-guide/ch058_forensicsincident-response.xml:52(link)
-msgid "http://blog.sflow.com/2013/01/rapidly-detecting-large-flows-sflow-vs.html"
-msgstr ""
-
 #. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
-#: ./doc/security-guide/ch058_forensicsincident-response.xml:0(None)
+#: ./doc/security-guide/ch027_storage.xml:0(None)
 msgid "translator-credits"
 msgstr ""
 
diff --git a/doc/training-guides/locale/training-guides.pot b/doc/training-guides/locale/training-guides.pot
index 5cfb44fe4c..0edc2da913 100644
--- a/doc/training-guides/locale/training-guides.pot
+++ b/doc/training-guides/locale/training-guides.pot
@@ -1,7 +1,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2014-05-24 06:11+0000\n"
+"POT-Creation-Date: 2014-06-03 06:11+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -9,77 +9,41 @@ msgstr ""
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
-#: ./doc/training-guides/module002-ch005-floating-ips.xml:7(title)
-msgid "Floating IP Addresses And Security Rules"
+#: ./doc/training-guides/bk003-ch003-developer-getting-started-quiz.xml:6(title) ./doc/training-guides/bk002-ch003-operator-getting-started-quiz.xml:6(title) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:6(title)
+msgid "Getting Started Quiz"
 msgstr ""
 
-#: ./doc/training-guides/module002-ch005-floating-ips.xml:8(para)
-msgid "OpenStack Networking has the concept of Fixed IPs and Floating IPs. Fixed IPs are assigned to an instance on creation and stay the same until the instance is explicitly terminated. Floating ips are ip addresses that can be dynamically associated with an instance. This address can be disassociated and associated with another instance at any time."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch005-floating-ips.xml:15(para)
-msgid "Various tasks carried out by Floating IP's as of now."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch005-floating-ips.xml:19(para)
-msgid "create IP ranges under a certain group, only available for admin role."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch005-floating-ips.xml:23(para)
-msgid "allocate an floating IP to a certain tenant, only available for admin role."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch005-floating-ips.xml:27(para)
-msgid "deallocate an floating IP from a certain tenant"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch005-floating-ips.xml:31(para)
-msgid "associate an floating IP to a given instance"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch005-floating-ips.xml:35(para)
-msgid "disassociate an floating IP from a certain instance"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch005-floating-ips.xml:39(para)
-msgid "Just as shown by the above figure, we will have nova-network-api to support nova client floating commands. nova-network-api will invoke neutron cli lib to interactive with neutron server via API. The data about floating IPs will be stored in to neutron DB. Neutron Agent, which is running on compute host will enforce the floating IP."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch005-floating-ips.xml:46(guilabel)
-msgid "Multiple Floating IP Pools"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch005-floating-ips.xml:48(para)
-msgid "The L3 API in OpenStack Networking supports multiple floating IP pools. In OpenStack Networking, a floating IP pool is represented as an external network and a floating IP is allocated from a subnet associated with the external network. Since each L3 agent can be associated with at most one external network, we need to invoke multiple L3 agent to define multiple floating IP pools. 'gateway_external_network_id'in L3 agent configuration file indicates the external network that the L3 agent handles. You can run multiple L3 agent instances on one host."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch005-floating-ips.xml:59(para)
-msgid "In addition, when you run multiple L3 agents, make sure that handle_internal_only_routers is set to Trueonly for one L3 agent in an OpenStack Networking deployment and set to Falsefor all other L3 agents. Since the default value of this parameter is True, you need to configure it carefully."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch005-floating-ips.xml:65(para)
-msgid "Before starting L3 agents, you need to create routers and external networks, then update the configuration files with UUID of external networks and start L3 agents."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch005-floating-ips.xml:69(para)
-msgid "For the first agent, invoke it with the following l3_agent.ini where handle_internal_only_routers is True."
-msgstr ""
-
-#: ./doc/training-guides/bk002-ch009-operator-compute-node-quiz.xml:6(title) ./doc/training-guides/bk001-ch006-associate-compute-node-quiz.xml:6(title)
-msgid "Compute Node Quiz"
-msgstr ""
-
-#: ./doc/training-guides/bk002-ch009-operator-compute-node-quiz.xml:8(title)
-msgid "Days 5 to 6, 16:40 to 17:00"
+#: ./doc/training-guides/bk003-ch003-developer-getting-started-quiz.xml:8(title) ./doc/training-guides/bk002-ch003-operator-getting-started-quiz.xml:8(title) ./doc/training-guides/bk001-ch006-associate-compute-node-quiz.xml:8(title)
+msgid "Day 1, 16:40 to 17:00"
 msgstr ""
 
 #. When image changes, this message will be marked fuzzy or untranslated for you.
 #. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/training-guides/bk003-ch001-developer-getting-started.xml:25(None) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:32(None) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:39(None) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:46(None) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:53(None) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:15(None) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:22(None) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:29(None) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:36(None) ./doc/training-guides/card074-horizon-snapshots.xml:12(None) ./doc/training-guides/card071-create-cinder-horizon.xml:11(None) ./doc/training-guides/card071-create-cinder-horizon.xml:15(None) ./doc/training-guides/card071-create-cinder-horizon.xml:19(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:17(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:24(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:31(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:40(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:47(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:54(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:61(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:68(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:75(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:82(None) ./doc/training-guides/bk002-ch010-operator-network-node.xml:17(None) ./doc/training-guides/bk002-ch010-operator-network-node.xml:24(None) ./doc/training-guides/bk002-ch010-operator-network-node.xml:35(None) ./doc/training-guides/bk002-ch010-operator-network-node.xml:42(None) ./doc/training-guides/bk002-ch010-operator-network-node.xml:49(None) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:17(None) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:24(None) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:33(None) ./doc/training-guides/card072-cinder-attach-volume.xml:11(None) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:17(None) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:24(None) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:31(None) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:15(None) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:22(None) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:29(None) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:36(None) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:43(None) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:17(None) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:24(None) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:31(None) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:17(None) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:32(None) ./doc/training-guides/bk002-ch011-operator-network-node-lab.xml:15(None) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:25(None) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:32(None) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:39(None) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:46(None) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:53(None) ./doc/training-guides/card008.xml:11(None) ./doc/training-guides/bk000-preface.xml:133(None) ./doc/training-guides/bk000-preface.xml:140(None) ./doc/training-guides/bk000-preface.xml:147(None) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:27(None) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:34(None) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:41(None) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:48(None) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:55(None) ./doc/training-guides/card073-control-state-instance.xml:12(None) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:17(None) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:24(None) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:31(None) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:40(None) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:47(None) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:54(None) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:61(None) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:68(None) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:75(None) ./doc/training-guides/bk002-ch005-operator-controller-node-lab.xml:15(None) ./doc/training-guides/card128-swift.xml:11(None) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:15(None) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:22(None) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:29(None) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:36(None) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:43(None) ./doc/training-guides/bk002-ch008-operator-compute-node-lab.xml:15(None) ./doc/training-guides/bk001-ch007-associate-network-node.xml:17(None) ./doc/training-guides/bk001-ch007-associate-network-node.xml:24(None) ./doc/training-guides/bk001-ch007-associate-network-node.xml:33(None) ./doc/training-guides/bk001-ch007-associate-network-node.xml:40(None) ./doc/training-guides/card070-create-floating-ips.xml:11(None) ./doc/training-guides/card070-create-floating-ips.xml:16(None) ./doc/training-guides/card070-create-floating-ips.xml:21(None)
+#: ./doc/training-guides/card071-create-cinder-horizon.xml:11(None) ./doc/training-guides/card071-create-cinder-horizon.xml:15(None) ./doc/training-guides/card071-create-cinder-horizon.xml:19(None) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:25(None) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:32(None) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:39(None) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:46(None) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:53(None) ./doc/training-guides/card070-create-floating-ips.xml:11(None) ./doc/training-guides/card070-create-floating-ips.xml:16(None) ./doc/training-guides/card070-create-floating-ips.xml:21(None) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:17(None) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:24(None) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:31(None) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:40(None) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:47(None) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:54(None) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:61(None) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:68(None) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:75(None) ./doc/training-guides/card073-control-state-instance.xml:12(None) ./doc/training-guides/bk001-ch007-associate-network-node.xml:17(None) ./doc/training-guides/bk001-ch007-associate-network-node.xml:24(None) ./doc/training-guides/bk001-ch007-associate-network-node.xml:33(None) ./doc/training-guides/bk001-ch007-associate-network-node.xml:40(None) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:17(None) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:24(None) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:31(None) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:17(None) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:32(None) ./doc/training-guides/card128-swift.xml:11(None) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:17(None) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:24(None) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:31(None) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:15(None) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:22(None) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:29(None) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:36(None) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:43(None) ./doc/training-guides/bk002-ch011-operator-network-node-lab.xml:15(None) ./doc/training-guides/bk002-ch010-operator-network-node.xml:17(None) ./doc/training-guides/bk002-ch010-operator-network-node.xml:24(None) ./doc/training-guides/bk002-ch010-operator-network-node.xml:35(None) ./doc/training-guides/bk002-ch010-operator-network-node.xml:42(None) ./doc/training-guides/bk002-ch010-operator-network-node.xml:49(None) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:27(None) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:34(None) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:41(None) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:48(None) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:55(None) ./doc/training-guides/card072-cinder-attach-volume.xml:11(None) ./doc/training-guides/bk002-ch005-operator-controller-node-lab.xml:15(None) ./doc/training-guides/card074-horizon-snapshots.xml:12(None) ./doc/training-guides/card008.xml:11(None) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:15(None) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:22(None) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:29(None) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:36(None) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:43(None) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:25(None) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:32(None) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:39(None) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:46(None) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:53(None) ./doc/training-guides/bk002-ch008-operator-compute-node-lab.xml:15(None) ./doc/training-guides/bk000-preface.xml:133(None) ./doc/training-guides/bk000-preface.xml:140(None) ./doc/training-guides/bk000-preface.xml:147(None) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:15(None) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:22(None) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:29(None) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:36(None) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:17(None) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:24(None) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:33(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:17(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:24(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:31(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:40(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:47(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:54(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:61(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:68(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:75(None) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:82(None)
 msgid "@@image: 'figures/openstack-training-remote-content-not-available.png'; md5=f2583b37e01220460a55b8c255c987c3"
 msgstr ""
 
-#: ./doc/training-guides/bk003-ch001-developer-getting-started.xml:6(title) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:6(title) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:6(title) ./doc/training-guides/lab000-virtualbox-basics.xml:12(guilabel)
+#: ./doc/training-guides/card071-create-cinder-horizon.xml:7(title)
+msgid "Creating and Deleting Volumes"
+msgstr ""
+
+#: ./doc/training-guides/card071-create-cinder-horizon.xml:11(para) ./doc/training-guides/card071-create-cinder-horizon.xml:15(para) ./doc/training-guides/card071-create-cinder-horizon.xml:19(para) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:25(para) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:32(para) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:39(para) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:46(para) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:53(para) ./doc/training-guides/card070-create-floating-ips.xml:11(para) ./doc/training-guides/card070-create-floating-ips.xml:16(para) ./doc/training-guides/card070-create-floating-ips.xml:21(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:17(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:24(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:31(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:40(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:47(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:54(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:61(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:68(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:75(para) ./doc/training-guides/card073-control-state-instance.xml:12(para) ./doc/training-guides/bk001-ch007-associate-network-node.xml:17(para) ./doc/training-guides/bk001-ch007-associate-network-node.xml:24(para) ./doc/training-guides/bk001-ch007-associate-network-node.xml:33(para) ./doc/training-guides/bk001-ch007-associate-network-node.xml:40(para) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:17(para) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:24(para) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:31(para) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:17(para) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:32(para) ./doc/training-guides/card128-swift.xml:11(para) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:17(para) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:24(para) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:31(para) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:15(para) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:22(para) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:29(para) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:36(para) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:43(para) ./doc/training-guides/bk002-ch011-operator-network-node-lab.xml:15(para) ./doc/training-guides/bk002-ch010-operator-network-node.xml:17(para) ./doc/training-guides/bk002-ch010-operator-network-node.xml:24(para) ./doc/training-guides/bk002-ch010-operator-network-node.xml:35(para) ./doc/training-guides/bk002-ch010-operator-network-node.xml:42(para) ./doc/training-guides/bk002-ch010-operator-network-node.xml:49(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:27(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:34(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:41(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:48(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:55(para) ./doc/training-guides/card072-cinder-attach-volume.xml:11(para) ./doc/training-guides/bk002-ch005-operator-controller-node-lab.xml:15(para) ./doc/training-guides/card074-horizon-snapshots.xml:12(para) ./doc/training-guides/card008.xml:11(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:15(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:22(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:29(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:36(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:43(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:25(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:32(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:39(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:46(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:53(para) ./doc/training-guides/bk002-ch008-operator-compute-node-lab.xml:15(para) ./doc/training-guides/bk000-preface.xml:133(para) ./doc/training-guides/bk000-preface.xml:140(para) ./doc/training-guides/bk000-preface.xml:147(para) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:15(para) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:22(para) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:29(para) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:36(para) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:17(para) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:24(para) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:33(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:17(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:24(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:31(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:40(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:47(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:54(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:61(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:68(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:75(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:82(para)
+msgid "<placeholder-1/>Remote content not available"
+msgstr ""
+
+#: ./doc/training-guides/card071-create-cinder-horizon.xml:11(para) ./doc/training-guides/card071-create-cinder-horizon.xml:15(para) ./doc/training-guides/card071-create-cinder-horizon.xml:19(para) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:25(para) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:32(para) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:39(para) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:46(para) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:53(para) ./doc/training-guides/card070-create-floating-ips.xml:11(para) ./doc/training-guides/card070-create-floating-ips.xml:16(para) ./doc/training-guides/card070-create-floating-ips.xml:21(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:17(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:24(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:31(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:40(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:47(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:54(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:61(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:68(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:75(para) ./doc/training-guides/card073-control-state-instance.xml:12(para) ./doc/training-guides/bk001-ch007-associate-network-node.xml:17(para) ./doc/training-guides/bk001-ch007-associate-network-node.xml:24(para) ./doc/training-guides/bk001-ch007-associate-network-node.xml:33(para) ./doc/training-guides/bk001-ch007-associate-network-node.xml:40(para) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:17(para) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:24(para) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:31(para) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:17(para) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:32(para) ./doc/training-guides/card128-swift.xml:11(para) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:17(para) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:24(para) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:31(para) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:15(para) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:22(para) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:29(para) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:36(para) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:43(para) ./doc/training-guides/user-story-includes-template.xml:22(para) ./doc/training-guides/bk002-ch011-operator-network-node-lab.xml:15(para) ./doc/training-guides/bk002-ch010-operator-network-node.xml:17(para) ./doc/training-guides/bk002-ch010-operator-network-node.xml:24(para) ./doc/training-guides/bk002-ch010-operator-network-node.xml:35(para) ./doc/training-guides/bk002-ch010-operator-network-node.xml:42(para) ./doc/training-guides/bk002-ch010-operator-network-node.xml:49(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:27(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:34(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:41(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:48(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:55(para) ./doc/training-guides/card072-cinder-attach-volume.xml:11(para) ./doc/training-guides/bk002-ch005-operator-controller-node-lab.xml:15(para) ./doc/training-guides/card074-horizon-snapshots.xml:12(para) ./doc/training-guides/card008.xml:11(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:15(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:22(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:29(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:36(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:43(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:25(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:32(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:39(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:46(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:53(para) ./doc/training-guides/bk002-ch008-operator-compute-node-lab.xml:15(para) ./doc/training-guides/bk000-preface.xml:133(para) ./doc/training-guides/bk000-preface.xml:140(para) ./doc/training-guides/bk000-preface.xml:147(para) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:15(para) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:22(para) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:29(para) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:36(para) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:17(para) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:24(para) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:33(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:17(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:24(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:31(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:40(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:47(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:54(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:61(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:68(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:75(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:82(para)
+msgid "image source"
+msgstr ""
+
+#: ./doc/training-guides/card071-create-cinder-horizon.xml:11(link) ./doc/training-guides/card071-create-cinder-horizon.xml:15(link) ./doc/training-guides/card071-create-cinder-horizon.xml:19(link) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:25(link) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:32(link) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:39(link) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:46(link) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:53(link) ./doc/training-guides/card070-create-floating-ips.xml:11(link) ./doc/training-guides/card070-create-floating-ips.xml:16(link) ./doc/training-guides/card070-create-floating-ips.xml:21(link) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:17(link) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:24(link) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:31(link) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:40(link) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:47(link) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:54(link) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:61(link) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:68(link) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:75(link) ./doc/training-guides/card073-control-state-instance.xml:12(link) ./doc/training-guides/bk001-ch007-associate-network-node.xml:17(link) ./doc/training-guides/bk001-ch007-associate-network-node.xml:24(link) ./doc/training-guides/bk001-ch007-associate-network-node.xml:33(link) ./doc/training-guides/bk001-ch007-associate-network-node.xml:40(link) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:17(link) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:24(link) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:31(link) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:17(link) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:32(link) ./doc/training-guides/card128-swift.xml:11(link) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:17(link) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:24(link) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:31(link) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:15(link) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:22(link) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:29(link) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:36(link) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:43(link) ./doc/training-guides/bk002-ch011-operator-network-node-lab.xml:15(link) ./doc/training-guides/bk002-ch010-operator-network-node.xml:17(link) ./doc/training-guides/bk002-ch010-operator-network-node.xml:24(link) ./doc/training-guides/bk002-ch010-operator-network-node.xml:35(link) ./doc/training-guides/bk002-ch010-operator-network-node.xml:42(link) ./doc/training-guides/bk002-ch010-operator-network-node.xml:49(link) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:27(link) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:34(link) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:41(link) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:48(link) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:55(link) ./doc/training-guides/card072-cinder-attach-volume.xml:11(link) ./doc/training-guides/bk002-ch005-operator-controller-node-lab.xml:15(link) ./doc/training-guides/card074-horizon-snapshots.xml:12(link) ./doc/training-guides/card008.xml:11(link) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:15(link) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:22(link) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:29(link) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:36(link) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:43(link) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:25(link) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:32(link) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:39(link) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:46(link) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:53(link) ./doc/training-guides/bk002-ch008-operator-compute-node-lab.xml:15(link) ./doc/training-guides/bk000-preface.xml:133(link) ./doc/training-guides/bk000-preface.xml:140(link) ./doc/training-guides/bk000-preface.xml:147(link) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:15(link) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:22(link) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:29(link) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:36(link) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:17(link) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:24(link) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:33(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:17(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:24(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:31(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:40(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:47(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:54(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:61(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:68(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:75(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:82(link)
+msgid "https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing"
+msgstr ""
+
+#: ./doc/training-guides/card071-create-cinder-horizon.xml:21(link) ./doc/training-guides/card070-create-floating-ips.xml:23(link) ./doc/training-guides/card127-glance.xml:14(link) ./doc/training-guides/card073-control-state-instance.xml:14(link) ./doc/training-guides/card040-cinder.xml:15(link) ./doc/training-guides/card039-nova.xml:14(link) ./doc/training-guides/card044-install-and-configure-neutron-network-node.xml:14(link) ./doc/training-guides/card126-horizon.xml:13(link) ./doc/training-guides/card128-swift.xml:13(link) ./doc/training-guides/card026-network-node-architecture.xml:14(link) ./doc/training-guides/card047-install-nova-compute.xml:14(link) ./doc/training-guides/user-story-includes-template.xml:33(link) ./doc/training-guides/card041-neutron.xml:22(link) ./doc/training-guides/card007-core-overview.xml:14(link) ./doc/training-guides/card072-cinder-attach-volume.xml:13(link) ./doc/training-guides/card011.xml:14(link) ./doc/training-guides/card074-horizon-snapshots.xml:14(link) ./doc/training-guides/card046-L3_Configuration_in_the_Network_Node.xml:14(link) ./doc/training-guides/card008.xml:13(link) ./doc/training-guides/card045-configure-virtual-networking.xml:20(link) ./doc/training-guides/card009.xml:16(link) ./doc/training-guides/card038.xml:13(link) ./doc/training-guides/card025.xml:13(link) ./doc/training-guides/card043-ovs-in-network-node.xml:15(link)
+msgid "Submit a bug on the section above. Short description for the bug summary. Paragraph for the description and then tag with training-manuals."
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch001-developer-getting-started.xml:6(title) ./doc/training-guides/lab000-virtualbox-basics.xml:12(guilabel) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:6(title) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:6(title)
 msgid "Getting Started"
 msgstr ""
 
@@ -87,7 +51,7 @@ msgstr ""
 msgid "Day 1, 09:00 to 11:00, 11:15 to 12:30"
 msgstr ""
 
-#: ./doc/training-guides/bk003-ch001-developer-getting-started.xml:12(title) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:33(guilabel) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:119(emphasis) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:828(guilabel) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:12(title) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:12(title) ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:12(title)
+#: ./doc/training-guides/bk003-ch001-developer-getting-started.xml:12(title) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:33(guilabel) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:119(emphasis) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:828(guilabel) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:12(title) ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:12(title) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:12(title)
 msgid "Overview"
 msgstr ""
 
@@ -95,7 +59,7 @@ msgstr ""
 msgid "Training would take 2.5 months self paced, (5) 2 week periods with a user group meeting, or 40 hours instructor led with 40 hours of self paced lab time."
 msgstr ""
 
-#: ./doc/training-guides/bk003-ch001-developer-getting-started.xml:15(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:15(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:15(para) ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:14(para)
+#: ./doc/training-guides/bk003-ch001-developer-getting-started.xml:15(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:15(para) ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:14(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:15(para)
 msgid "Prerequisites"
 msgstr ""
 
@@ -111,18 +75,6 @@ msgstr ""
 msgid "Review Operator Introduction"
 msgstr ""
 
-#: ./doc/training-guides/bk003-ch001-developer-getting-started.xml:25(para) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:32(para) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:39(para) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:46(para) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:53(para) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:15(para) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:22(para) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:29(para) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:36(para) ./doc/training-guides/card074-horizon-snapshots.xml:12(para) ./doc/training-guides/card071-create-cinder-horizon.xml:11(para) ./doc/training-guides/card071-create-cinder-horizon.xml:15(para) ./doc/training-guides/card071-create-cinder-horizon.xml:19(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:17(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:24(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:31(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:40(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:47(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:54(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:61(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:68(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:75(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:82(para) ./doc/training-guides/bk002-ch010-operator-network-node.xml:17(para) ./doc/training-guides/bk002-ch010-operator-network-node.xml:24(para) ./doc/training-guides/bk002-ch010-operator-network-node.xml:35(para) ./doc/training-guides/bk002-ch010-operator-network-node.xml:42(para) ./doc/training-guides/bk002-ch010-operator-network-node.xml:49(para) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:17(para) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:24(para) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:33(para) ./doc/training-guides/card072-cinder-attach-volume.xml:11(para) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:17(para) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:24(para) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:31(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:15(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:22(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:29(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:36(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:43(para) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:17(para) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:24(para) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:31(para) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:17(para) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:32(para) ./doc/training-guides/bk002-ch011-operator-network-node-lab.xml:15(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:25(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:32(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:39(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:46(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:53(para) ./doc/training-guides/card008.xml:11(para) ./doc/training-guides/bk000-preface.xml:133(para) ./doc/training-guides/bk000-preface.xml:140(para) ./doc/training-guides/bk000-preface.xml:147(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:27(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:34(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:41(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:48(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:55(para) ./doc/training-guides/card073-control-state-instance.xml:12(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:17(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:24(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:31(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:40(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:47(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:54(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:61(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:68(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:75(para) ./doc/training-guides/bk002-ch005-operator-controller-node-lab.xml:15(para) ./doc/training-guides/card128-swift.xml:11(para) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:15(para) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:22(para) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:29(para) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:36(para) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:43(para) ./doc/training-guides/bk002-ch008-operator-compute-node-lab.xml:15(para) ./doc/training-guides/bk001-ch007-associate-network-node.xml:17(para) ./doc/training-guides/bk001-ch007-associate-network-node.xml:24(para) ./doc/training-guides/bk001-ch007-associate-network-node.xml:33(para) ./doc/training-guides/bk001-ch007-associate-network-node.xml:40(para) ./doc/training-guides/card070-create-floating-ips.xml:11(para) ./doc/training-guides/card070-create-floating-ips.xml:16(para) ./doc/training-guides/card070-create-floating-ips.xml:21(para)
-msgid "<placeholder-1/>Remote content not available"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch001-developer-getting-started.xml:25(para) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:32(para) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:39(para) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:46(para) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:53(para) ./doc/training-guides/user-story-includes-template.xml:22(para) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:15(para) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:22(para) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:29(para) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:36(para) ./doc/training-guides/card074-horizon-snapshots.xml:12(para) ./doc/training-guides/card071-create-cinder-horizon.xml:11(para) ./doc/training-guides/card071-create-cinder-horizon.xml:15(para) ./doc/training-guides/card071-create-cinder-horizon.xml:19(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:17(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:24(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:31(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:40(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:47(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:54(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:61(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:68(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:75(para) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:82(para) ./doc/training-guides/bk002-ch010-operator-network-node.xml:17(para) ./doc/training-guides/bk002-ch010-operator-network-node.xml:24(para) ./doc/training-guides/bk002-ch010-operator-network-node.xml:35(para) ./doc/training-guides/bk002-ch010-operator-network-node.xml:42(para) ./doc/training-guides/bk002-ch010-operator-network-node.xml:49(para) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:17(para) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:24(para) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:33(para) ./doc/training-guides/card072-cinder-attach-volume.xml:11(para) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:17(para) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:24(para) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:31(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:15(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:22(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:29(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:36(para) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:43(para) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:17(para) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:24(para) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:31(para) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:17(para) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:32(para) ./doc/training-guides/bk002-ch011-operator-network-node-lab.xml:15(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:25(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:32(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:39(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:46(para) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:53(para) ./doc/training-guides/card008.xml:11(para) ./doc/training-guides/bk000-preface.xml:133(para) ./doc/training-guides/bk000-preface.xml:140(para) ./doc/training-guides/bk000-preface.xml:147(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:27(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:34(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:41(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:48(para) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:55(para) ./doc/training-guides/card073-control-state-instance.xml:12(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:17(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:24(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:31(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:40(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:47(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:54(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:61(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:68(para) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:75(para) ./doc/training-guides/bk002-ch005-operator-controller-node-lab.xml:15(para) ./doc/training-guides/card128-swift.xml:11(para) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:15(para) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:22(para) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:29(para) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:36(para) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:43(para) ./doc/training-guides/bk002-ch008-operator-compute-node-lab.xml:15(para) ./doc/training-guides/bk001-ch007-associate-network-node.xml:17(para) ./doc/training-guides/bk001-ch007-associate-network-node.xml:24(para) ./doc/training-guides/bk001-ch007-associate-network-node.xml:33(para) ./doc/training-guides/bk001-ch007-associate-network-node.xml:40(para) ./doc/training-guides/card070-create-floating-ips.xml:11(para) ./doc/training-guides/card070-create-floating-ips.xml:16(para) ./doc/training-guides/card070-create-floating-ips.xml:21(para)
-msgid "image source"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch001-developer-getting-started.xml:25(link) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:32(link) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:39(link) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:46(link) ./doc/training-guides/bk003-ch001-developer-getting-started.xml:53(link) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:15(link) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:22(link) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:29(link) ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:36(link) ./doc/training-guides/card074-horizon-snapshots.xml:12(link) ./doc/training-guides/card071-create-cinder-horizon.xml:11(link) ./doc/training-guides/card071-create-cinder-horizon.xml:15(link) ./doc/training-guides/card071-create-cinder-horizon.xml:19(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:17(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:24(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:31(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:40(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:47(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:54(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:61(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:68(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:75(link) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:82(link) ./doc/training-guides/bk002-ch010-operator-network-node.xml:17(link) ./doc/training-guides/bk002-ch010-operator-network-node.xml:24(link) ./doc/training-guides/bk002-ch010-operator-network-node.xml:35(link) ./doc/training-guides/bk002-ch010-operator-network-node.xml:42(link) ./doc/training-guides/bk002-ch010-operator-network-node.xml:49(link) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:17(link) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:24(link) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:33(link) ./doc/training-guides/card072-cinder-attach-volume.xml:11(link) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:17(link) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:24(link) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:31(link) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:15(link) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:22(link) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:29(link) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:36(link) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:43(link) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:17(link) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:24(link) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:31(link) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:17(link) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:32(link) ./doc/training-guides/bk002-ch011-operator-network-node-lab.xml:15(link) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:25(link) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:32(link) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:39(link) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:46(link) ./doc/training-guides/bk002-ch001-operator-getting-started.xml:53(link) ./doc/training-guides/card008.xml:11(link) ./doc/training-guides/bk000-preface.xml:133(link) ./doc/training-guides/bk000-preface.xml:140(link) ./doc/training-guides/bk000-preface.xml:147(link) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:27(link) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:34(link) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:41(link) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:48(link) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:55(link) ./doc/training-guides/card073-control-state-instance.xml:12(link) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:17(link) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:24(link) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:31(link) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:40(link) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:47(link) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:54(link) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:61(link) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:68(link) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:75(link) ./doc/training-guides/bk002-ch005-operator-controller-node-lab.xml:15(link) ./doc/training-guides/card128-swift.xml:11(link) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:15(link) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:22(link) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:29(link) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:36(link) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:43(link) ./doc/training-guides/bk002-ch008-operator-compute-node-lab.xml:15(link) ./doc/training-guides/bk001-ch007-associate-network-node.xml:17(link) ./doc/training-guides/bk001-ch007-associate-network-node.xml:24(link) ./doc/training-guides/bk001-ch007-associate-network-node.xml:33(link) ./doc/training-guides/bk001-ch007-associate-network-node.xml:40(link) ./doc/training-guides/card070-create-floating-ips.xml:11(link) ./doc/training-guides/card070-create-floating-ips.xml:16(link) ./doc/training-guides/card070-create-floating-ips.xml:21(link)
-msgid "https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing"
-msgstr ""
-
 #: ./doc/training-guides/bk003-ch001-developer-getting-started.xml:29(title)
 msgid "Review Operator Brief Overview"
 msgstr ""
@@ -139,1105 +91,28 @@ msgstr ""
 msgid "Review Operator Virtual Machine Provisioning Walk-Through"
 msgstr ""
 
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:11(title)
-msgid "A Bit More On Swift"
+#: ./doc/training-guides/card070-create-floating-ips.xml:7(title)
+msgid "Create floating ip"
 msgstr ""
 
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:12(guilabel)
-msgid "Containers and Objects"
+#: ./doc/training-guides/bk002-ch012-operator-network-node-quiz.xml:6(title) ./doc/training-guides/bk001-ch008-associate-network-node-quiz.xml:6(title)
+msgid "Network Node Quiz"
 msgstr ""
 
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:13(para)
-msgid "A container is a storage compartment for your data and provides a way for you to organize your data. You can think of a container as a folder in Windows or a directory in UNIX. The primary difference between a container and these other file system concepts is that containers cannot be nested. You can, however, create an unlimited number of containers within your account. Data must be stored in a container so you must have at least one container defined in your account prior to uploading data."
+#: ./doc/training-guides/bk002-ch012-operator-network-node-quiz.xml:8(title)
+msgid "Days 7 to 8, 16:40 to 17:00"
 msgstr ""
 
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:23(para)
-msgid "The only restrictions on container names is that they cannot contain a forward slash (/) or an ascii null (%00) and must be less than 257 bytes in length. Please note that the length restriction applies to the name after it has been URL encoded. For example, a container name of Course Docs would be URL encoded as Course%20Docs and therefore be 13 bytes in length rather than the expected 11."
+#: ./doc/training-guides/card127-glance.xml:7(title)
+msgid "Install Glance"
 msgstr ""
 
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:31(para)
-msgid "An object is the basic storage entity and any optional metadata that represents the files you store in the OpenStack Object Storage system. When you upload data to OpenStack Object Storage, the data is stored as-is (no compression or encryption) and consists of a location (container), the object's name, and any metadata consisting of key/value pairs. For instance, you may chose to store a backup of your digital photos and organize them into albums. In this case, each object could be tagged with metadata such as Album : Caribbean Cruise or Album : Aspen Ski Trip."
+#: ./doc/training-guides/bk003-ch007-developer-apis-day-three-lab.xml:6(title)
+msgid "Developer APIs in Depth Lab Day Three"
 msgstr ""
 
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:42(para)
-msgid "The only restriction on object names is that they must be less than 1024 bytes in length after URL encoding. For example, an object name of C++final(v2).txt should be URL encoded as C%2B%2Bfinal%28v2%29.txt and therefore be 24 bytes in length rather than the expected 16."
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:47(para)
-msgid "The maximum allowable size for a storage object upon upload is 5GB and the minimum is zero bytes. You can use the built-in large object support and the swift utility to retrieve objects larger than 5GB."
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:51(para)
-msgid "For metadata, you should not exceed 90 individual key/value pairs for any one object and the total byte length of all key/value pairs should not exceed 4KB (4096bytes)."
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:55(guilabel)
-msgid "Language-Specific API Bindings"
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:57(para)
-msgid "A set of supported API bindings in several popular languages are available from the Rackspace Cloud Files product, which uses OpenStack Object Storage code for its implementation. These bindings provide a layer of abstraction on top of the base REST API, allowing programmers to work with a container and object model instead of working directly with HTTP requests and responses. These bindings are free (as in beer and as in speech) to download, use, and modify. They are all licensed under the MIT License as described in the COPYING file packaged with each binding. If you do make any improvements to an API, you are encouraged (but not required) to submit those changes back to us."
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:70(para)
-msgid "The API bindings for Rackspace Cloud Files are hosted at<link href=\"http://github.com/rackspace\"/><link href=\"http://github.com/rackspace\">http://github.com/rackspace</link>. Feel free to coordinate your changes through github or, if you prefer, send your changes to cloudfiles@rackspacecloud.com. Just make sure to indicate which language and version you modified and send a unified diff."
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:79(para)
-msgid "Each binding includes its own documentation (either HTML, PDF, or CHM). They also include code snippets and examples to help you get started. The currently supported API binding for OpenStack Object Storage are:"
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:85(para)
-msgid "PHP (requires 5.x and the modules: cURL, FileInfo, mbstring)"
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:89(para)
-msgid "Python (requires 2.4 or newer)"
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:92(para)
-msgid "Java (requires JRE v1.5 or newer)"
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:95(para)
-msgid "C#/.NET (requires .NET Framework v3.5)"
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:98(para)
-msgid "Ruby (requires 1.8 or newer and mime-tools module)"
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:102(para)
-msgid "There are no other supported language-specific bindings at this time. You are welcome to create your own language API bindings and we can help answer any questions during development, host your code if you like, and give you full credit for your work."
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:107(guilabel)
-msgid "Proxy Server"
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:108(para)
-msgid "The Proxy Server is responsible for tying together the rest of the OpenStack Object Storage architecture. For each request, it will look up the location of the account, container, or object in the ring (see below) and route the request accordingly. The public API is also exposed through the Proxy Server."
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:114(para)
-msgid "A large number of failures are also handled in the Proxy Server. For example, if a server is unavailable for an object PUT, it will ask the ring for a hand-off server and route there instead."
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:118(para)
-msgid "When objects are streamed to or from an object server, they are streamed directly through the proxy server to or from the user – the proxy server does not spool them."
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:122(para)
-msgid "You can use a proxy server with account management enabled by configuring it in the proxy server configuration file."
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:125(guilabel)
-msgid "Object Server"
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:126(para)
-msgid "The Object Server is a very simple blob storage server that can store, retrieve and delete objects stored on local devices. Objects are stored as binary files on the filesystem with metadata stored in the file’s extended attributes (xattrs). This requires that the underlying filesystem choice for object servers support xattrs on files. Some filesystems, like ext3, have xattrs turned off by default."
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:134(para)
-msgid "Each object is stored using a path derived from the object name’s hash and the operation’s timestamp. Last write always wins, and ensures that the latest object version will be served. A deletion is also treated as a version of the file (a 0 byte file ending with “.ts”, which stands for tombstone). This ensures that deleted files are replicated correctly and older versions don’t magically reappear due to failure scenarios."
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:143(guilabel)
-msgid "Container Server"
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:144(para)
-msgid "The Container Server’s primary job is to handle listings of objects. It does not know where those objects are, just what objects are in a specific container. The listings are stored as SQLite database files, and replicated across the cluster similar to how objects are. Statistics are also tracked that include the total number of objects, and total storage usage for that container."
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:152(guilabel)
-msgid "Account Server"
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:153(para)
-msgid "The Account Server is very similar to the Container Server, excepting that it is responsible for listings of containers rather than objects."
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:156(guilabel)
-msgid "Replication"
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:157(para)
-msgid "Replication is designed to keep the system in a consistent state in the face of temporary error conditions like network outages or drive failures."
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:161(para)
-msgid "The replication processes compare local data with each remote copy to ensure they all contain the latest version. Object replication uses a hash list to quickly compare subsections of each partition, and container and account replication use a combination of hashes and shared high water marks."
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:167(para)
-msgid "Replication updates are push based. For object replication, updating is just a matter of rsyncing files to the peer. Account and container replication push missing records over HTTP or rsync whole database files."
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:172(para)
-msgid "The replicator also ensures that data is removed from the system. When an item (object, container, or account) is deleted, a tombstone is set as the latest version of the item. The replicator will see the tombstone and ensure that the item is removed from the entire system."
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:178(para)
-msgid "To separate the cluster-internal replication traffic from client traffic, separate replication servers can be used. These replication servers are based on the standard storage servers, but they listen on the replication IP and only respond to REPLICATE requests. Storage servers can serve REPLICATE requests, so an operator can transition to using a separate replication network with no cluster downtime."
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:186(para)
-msgid "Replication IP and port information is stored in the ring on a per-node basis. These parameters will be used if they are present, but they are not required. If this information does not exist or is empty for a particular node, the node's standard IP and port will be used for replication."
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:192(guilabel)
-msgid "Updaters"
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:193(para)
-msgid "There are times when container or account data can not be immediately updated. This usually occurs during failure scenarios or periods of high load. If an update fails, the update is queued locally on the file system, and the updater will process the failed updates. This is where an eventual consistency window will most likely come in to play. For example, suppose a container server is under load and a new object is put in to the system. The object will be immediately available for reads as soon as the proxy server responds to the client with success. However, the container server did not update the object listing, and so the update would be queued for a later update. Container listings, therefore, may not immediately contain the object."
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:208(para)
-msgid "In practice, the consistency window is only as large as the frequency at which the updater runs and may not even be noticed as the proxy server will route listing requests to the first container server which responds. The server under load may not be the one that serves subsequent listing requests – one of the other two replicas may handle the listing."
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:215(guilabel)
-msgid "Auditors"
-msgstr ""
-
-#: ./doc/training-guides/module003-ch006-more-concepts.xml:216(para)
-msgid "Auditors crawl the local server checking the integrity of the objects, containers, and accounts. If corruption is found (in the case of bit rot, for example), the file is quarantined, and replication will replace the bad file from another replica. If other errors are found they are logged. For example, an object’s listing cannot be found on any container server it should be."
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:231(None)
-msgid "@@image: 'figures/image33.png'; md5=e9843f38c9b2555e709357a724fc710d"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:7(title) ./doc/training-guides/module002-ch001-networking-in-openstack.xml:8(guilabel) ./doc/training-guides/bk001-ch007-associate-network-node.xml:14(title)
-msgid "Networking in OpenStack"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:9(para)
-msgid "OpenStack Networking provides a rich tenant-facing API for defining network connectivity and addressing in the cloud. The OpenStack Networking project gives operators the ability to leverage different networking technologies to power their cloud networking. It is a virtual network service that provides a powerful API to define the network connectivity and addressing used by devices from other services, such as OpenStack Compute. It has a rich API which consists of the following components."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:20(para)
-msgid "<emphasis role=\"bold\">Network:</emphasis> An isolated L2 segment, analogous to VLAN in the physical networking world."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:25(para)
-msgid "<emphasis role=\"bold\">Subnet:</emphasis> A block of v4 or v6 IP addresses and associated configuration state."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:30(para)
-msgid "<emphasis role=\"bold\">Port:</emphasis> A connection point for attaching a single device, such as the NIC of a virtual server, to a virtual network. Also describes the associated network configuration, such as the MAC and IP addresses to be used on that port."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:38(para)
-msgid "You can configure rich network topologies by creating and configuring networks and subnets, and then instructing other OpenStack services like OpenStack Compute to attach virtual devices to ports on these networks. In particular, OpenStack Networking supports each tenant having multiple private networks, and allows tenants to choose their own IP addressing scheme, even if those IP addresses overlap with those used by other tenants. This enables very advanced cloud networking use cases, such as building multi-tiered web applications and allowing applications to be migrated to the cloud without changing IP addresses."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:50(guilabel)
-msgid "Plugin Architecture: Flexibility to Choose Different Network Technologies"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:52(para)
-msgid "Enhancing traditional networking solutions to provide rich cloud networking is challenging. Traditional networking is not designed to scale to cloud proportions or to configure automatically."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:56(para)
-msgid "The original OpenStack Compute network implementation assumed a very basic model of performing all isolation through Linux VLANs and IP tables. OpenStack Networking introduces the concept of a plug-in, which is a pluggable back-end implementation of the OpenStack Networking API. A plug-in can use a variety of technologies to implement the logical API requests. Some OpenStack Networking plug-ins might use basic Linux VLANs and IP tables, while others might use more advanced technologies, such as L2-in-L3 tunneling or OpenFlow, to provide similar benefits."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:66(para)
-msgid "The current set of plug-ins include:"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:69(emphasis)
-msgid "Big Switch, Floodlight REST Proxy:"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:73(link)
-msgid "http://www.openflowhub.org/display/floodlightcontroller/Quantum+REST+Proxy+Plugin"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:76(emphasis)
-msgid "Brocade Plugin"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:80(para)
-msgid "<emphasis role=\"bold\">Cisco:</emphasis> Documented externally at: <link href=\"http://wiki.openstack.org/cisco-quantum\">http://wiki.openstack.org/cisco-quantum</link>"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:86(emphasis)
-msgid "Hyper-V Plugin"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:90(para)
-msgid "<emphasis role=\"bold\">Linux Bridge:</emphasis> Documentation included in this guide and <link href=\"http://wiki.openstack.org/Quantum-Linux-Bridge-Plugin\">http://wiki.openstack.org/Quantum-Linux-Bridge-Plugin</link>"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:97(emphasis)
-msgid "Midonet Plugin"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:101(emphasis)
-msgid "NEC OpenFlow:"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:104(link)
-msgid "http://wiki.openstack.org/Quantum-NEC-OpenFlow-Plugin"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:107(para)
-msgid "<emphasis role=\"bold\">Open vSwitch:</emphasis> Documentation included in this guide."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:111(emphasis)
-msgid "PLUMgrid:"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:114(link)
-msgid "https://wiki.openstack.org/wiki/Plumgrid-quantum"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:117(emphasis)
-msgid "Ryu:"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:120(link)
-msgid "https://github.com/osrg/ryu/wiki/OpenStack"
-msgstr ""
-
-#. TODO: Update support link, when available
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:124(para)
-msgid "<emphasis role=\"bold\">VMware NSX:</emphasis> Documentation include in this guide, <link href=\"http://www.vmware.com/products/nsx\">NSX Product Overview </link>, and <link href=\"http://www.nicira.com/support\">NSX Product Support</link>."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:132(para)
-msgid "Plugins can have different properties in terms of hardware requirements, features, performance, scale, operator tools, etc. Supporting many plug-ins enables the cloud administrator to weigh different options and decide which networking technology is right for the deployment."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:137(para)
-msgid "Components of OpenStack Networking"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:138(para)
-msgid "To deploy OpenStack Networking, it is useful to understand the different components that make up the solution and how those components interact with each other and with other OpenStack services."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:142(para)
-msgid "OpenStack Networking is a standalone service, just like other OpenStack services such as OpenStack Compute, OpenStack Image Service, OpenStack Identity service, and the OpenStack Dashboard. Like those services, a deployment of OpenStack Networking often involves deploying several processes on a variety of hosts."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:148(para)
-msgid "The main process of the OpenStack Networking server is quantum-server, which is a Python daemon that exposes the OpenStack Networking API and passes user requests to the configured OpenStack Networking plug-in for additional processing. Typically, the plug-in requires access to a database for persistent storage, similar to other OpenStack services."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:155(para)
-msgid "If your deployment uses a controller host to run centralized OpenStack Compute components, you can deploy the OpenStack Networking server on that same host. However, OpenStack Networking is entirely standalone and can be deployed on its own server as well. OpenStack Networking also includes additional agents that might be required depending on your deployment:"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:164(para)
-msgid "<emphasis role=\"bold\">plugin agent (quantum-*-agent):</emphasis>Runs on each hypervisor to perform local vswitch configuration. Agent to be run depends on which plug-in you are using, as some plug-ins do not require an agent."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:171(para)
-msgid "<emphasis role=\"bold\">dhcp agent (quantum-dhcp-agent):</emphasis>Provides DHCP services to tenant networks. This agent is the same across all plug-ins."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:177(para)
-msgid "<emphasis role=\"bold\">l3 agent (quantum-l3-agent):</emphasis>Provides L3/NAT forwarding to provide external network access for VMs on tenant networks. This agent is the same across all plug-ins."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:184(para)
-msgid "These agents interact with the main quantum-server process in the following ways:"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:188(para)
-msgid "Through RPC. For example, rabbitmq or qpid."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:191(para)
-msgid "Through the standard OpenStack Networking API."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:195(para)
-msgid "OpenStack Networking relies on the OpenStack Identity Project (Keystone) for authentication and authorization of all API request."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:198(para)
-msgid "OpenStack Compute interacts with OpenStack Networking through calls to its standard API. As part of creating a VM, nova-compute communicates with the OpenStack Networking API to plug each virtual NIC on the VM into a particular network."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:203(para)
-msgid "The OpenStack Dashboard (Horizon) has integration with the OpenStack Networking API, allowing administrators and tenant users, to create and manage network services through the Horizon GUI."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:207(emphasis)
-msgid "Place Services on Physical Hosts"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:209(para)
-msgid "Like other OpenStack services, OpenStack Networking provides cloud administrators with significant flexibility in deciding which individual services should run on which physical devices. On one extreme, all service daemons can be run on a single physical host for evaluation purposes. On the other, each service could have its own physical hosts, and some cases be replicated across multiple hosts for redundancy."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:216(para)
-msgid "In this guide, we focus primarily on a standard architecture that includes a “cloud controller” host, a “network gateway” host, and a set of hypervisors for running VMs. The \"cloud controller\" and \"network gateway\" can be combined in simple deployments, though if you expect VMs to send significant amounts of traffic to or from the Internet, a dedicated network gateway host is suggested to avoid potential CPU contention between packet forwarding performed by the quantum-l3-agent and other OpenStack services."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:225(emphasis)
-msgid "Network Connectivity for Physical Hosts"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:228(title) ./doc/training-guides/lab002-network-node.xml:11(title) ./doc/training-guides/lab003-compute-node.xml:14(title) ./doc/training-guides/lab001-control-node.xml:9(title)
-msgid "Network Diagram"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:235(para)
-msgid "A standard OpenStack Networking setup has up to four distinct physical data center networks:"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:239(para)
-msgid "<emphasis role=\"bold\">Management network:</emphasis>Used for internal communication between OpenStack Components. The IP addresses on this network should be reachable only within the data center."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:246(para)
-msgid "<emphasis role=\"bold\">Data network:</emphasis>Used for VM data communication within the cloud deployment. The IP addressing requirements of this network depend on the OpenStack Networking plug-in in use."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:252(para)
-msgid "<emphasis role=\"bold\">External network:</emphasis>Used to provide VMs with Internet access in some deployment scenarios. The IP addresses on this network should be reachable by anyone on the Internet."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:259(para)
-msgid "<emphasis role=\"bold\">API network:</emphasis>Exposes all OpenStack APIs, including the OpenStack Networking API, to tenants. The IP addresses on this network should be reachable by anyone on the Internet. This may be the same network as the external network, as it is possible to create a subnet for the external network that uses IP allocation ranges to use only less than the full range of IP addresses in an IP block."
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/training-guides/user-story-includes-template.xml:19(None)
-msgid "@@image: 'figures/openstack-training-example-image.png'; md5=87bf110d5b53b2168680e1370176ef02"
-msgstr ""
-
-#: ./doc/training-guides/user-story-includes-template.xml:7(title)
-msgid "Including external content for user stories, version 1.3"
-msgstr ""
-
-#: ./doc/training-guides/user-story-includes-template.xml:8(para)
-msgid "Save your user story file as associate-my-user-story-name, operator-my-user-story, etc. For example, the user story that I assigned myself is operator bug fix so the file name would be operator-fix-documentation-bug.xml. See the operator-fix-documentation-bug.xml file in the repository for more details."
-msgstr ""
-
-#: ./doc/training-guides/user-story-includes-template.xml:12(para)
-msgid "The include statements below are meant to help you tell and teach the user story. Include as much content as necessary and use examples."
-msgstr ""
-
-#: ./doc/training-guides/user-story-includes-template.xml:14(para)
-msgid "Create diagrams through gdraw and export as png. Reference as local file in the /figures/ director. Share as 'Anyone With the Link' can 'Edit' and add URL to the description so anyone else can update the original."
-msgstr ""
-
-#: ./doc/training-guides/user-story-includes-template.xml:17(para)
-msgid "<placeholder-1/> big dummy example image"
-msgstr ""
-
-#: ./doc/training-guides/user-story-includes-template.xml:23(link)
-msgid "https://docs.google.com/drawings/d/1Tdn4SZLBdvQybW_nK_lO380YRIe5T6PsI0IyLH5XE3M/edit?usp=sharing"
-msgstr ""
-
-#: ./doc/training-guides/user-story-includes-template.xml:25(emphasis)
-msgid "Including a whole file. Include as much description about what is being taught here."
-msgstr ""
-
-#: ./doc/training-guides/user-story-includes-template.xml:33(link) ./doc/training-guides/card007-core-overview.xml:14(link) ./doc/training-guides/card025.xml:13(link) ./doc/training-guides/card074-horizon-snapshots.xml:14(link) ./doc/training-guides/card071-create-cinder-horizon.xml:21(link) ./doc/training-guides/card009.xml:16(link) ./doc/training-guides/card043-ovs-in-network-node.xml:15(link) ./doc/training-guides/card072-cinder-attach-volume.xml:13(link) ./doc/training-guides/card126-horizon.xml:13(link) ./doc/training-guides/card039-nova.xml:14(link) ./doc/training-guides/card047-install-nova-compute.xml:14(link) ./doc/training-guides/card045-configure-virtual-networking.xml:20(link) ./doc/training-guides/card041-neutron.xml:22(link) ./doc/training-guides/card008.xml:13(link) ./doc/training-guides/card040-cinder.xml:15(link) ./doc/training-guides/card046-L3_Configuration_in_the_Network_Node.xml:14(link) ./doc/training-guides/card127-glance.xml:14(link) ./doc/training-guides/card026-network-node-architecture.xml:14(link) ./doc/training-guides/card044-install-and-configure-neutron-network-node.xml:14(link) ./doc/training-guides/card073-control-state-instance.xml:14(link) ./doc/training-guides/card128-swift.xml:13(link) ./doc/training-guides/card011.xml:14(link) ./doc/training-guides/card070-create-floating-ips.xml:23(link) ./doc/training-guides/card038.xml:13(link)
-msgid "Submit a bug on the section above. Short description for the bug summary. Paragraph for the description and then tag with training-manuals."
-msgstr ""
-
-#: ./doc/training-guides/user-story-includes-template.xml:37(emphasis)
-msgid "Including a section of a file. Include as much description about what is being taught here."
-msgstr ""
-
-#: ./doc/training-guides/user-story-includes-template.xml:45(link)
-msgid "Submit a bug on the section above. Leave a short description for the bug summary, a paragraph for the description and then tag with training-manuals."
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch022-developer-assessment.xml:6(title) ./doc/training-guides/bk001-ch011-associate-assessment.xml:6(title)
-msgid "Assessment"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch022-developer-assessment.xml:8(title)
-msgid "Day 10, 9:00 to 11:00, 11:15 to 12:30, hands on lab 13:30 to 14:45, 15:00 to 17:00"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch022-developer-assessment.xml:12(title) ./doc/training-guides/bk001-ch011-associate-assessment.xml:12(title)
-msgid "Questions"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch022-developer-assessment.xml:14(caption) ./doc/training-guides/bk001-ch011-associate-assessment.xml:14(caption)
-msgid "Assessment Question 1"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch022-developer-assessment.xml:19(th) ./doc/training-guides/bk003-ch022-developer-assessment.xml:40(th) ./doc/training-guides/bk001-ch011-associate-assessment.xml:19(th) ./doc/training-guides/bk001-ch011-associate-assessment.xml:40(th)
-msgid "Task"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch022-developer-assessment.xml:20(th) ./doc/training-guides/bk003-ch022-developer-assessment.xml:41(th) ./doc/training-guides/bk001-ch011-associate-assessment.xml:20(th) ./doc/training-guides/bk001-ch011-associate-assessment.xml:41(th)
-msgid "Completed?"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch022-developer-assessment.xml:26(para) ./doc/training-guides/bk003-ch022-developer-assessment.xml:47(para) ./doc/training-guides/bk001-ch011-associate-assessment.xml:26(para) ./doc/training-guides/bk001-ch011-associate-assessment.xml:47(para)
-msgid "Configure a ...."
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch022-developer-assessment.xml:35(caption) ./doc/training-guides/bk001-ch011-associate-assessment.xml:35(caption)
-msgid "Assessment Question 2"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:6(title) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:28(title)
-msgid "OpenStack Block Storage"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:7(emphasis)
-msgid "Block Storage and OpenStack Compute"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:9(para)
-msgid "OpenStack provides two classes of block storage, \"ephemeral\" storage and persistent \"volumes\". Ephemeral storage exists only for the life of an instance, it will persist across reboots of the guest operating system but when the instance is deleted so is the associated storage. All instances have some ephemeral storage. Volumes are persistent virtualized block devices independent of any particular instance. Volumes may be attached to a single instance at a time, but may be detached or reattached to a different instance while retaining all data, much like a USB drive."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:19(guilabel)
-msgid "Ephemeral Storage"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:20(para)
-msgid "Ephemeral storage is associated with a single unique instance. Its size is defined by the flavor of the instance."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:22(para)
-msgid "Data on ephemeral storage ceases to exist when the instance it is associated with is terminated. Rebooting the VM or restarting the host server, however, will not destroy ephemeral data. In the typical use case an instance's root filesystem is stored on ephemeral storage. This is often an unpleasant surprise for people unfamiliar with the cloud model of computing."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:28(para)
-msgid "In addition to the ephemeral root volume all flavors except the smallest, m1.tiny, provide an additional ephemeral block device varying from 20G for the m1.small through 160G for the m1.xlarge by default - these sizes are configurable. This is presented as a raw block device with no partition table or filesystem. Cloud aware operating system images may discover, format, and mount this device. For example the cloud-init package included in Ubuntu's stock cloud images will format this space as an ext3 filesystem and mount it on /mnt. It is important to note this a feature of the guest operating system. OpenStack only provisions the raw storage."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:39(guilabel)
-msgid "Volume Storage"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:40(para)
-msgid "Volume storage is independent of any particular instance and is persistent. Volumes are user created and within quota and availability limits may be of any arbitrary size."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:43(para)
-msgid "When first created volumes are raw block devices with no partition table and no filesystem. They must be attached to an instance to be partitioned and/or formatted. Once this is done they may be used much like an external disk drive. Volumes may attached to only one instance at a time, but may be detached and reattached to either the same or different instances."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:49(para)
-msgid "It is possible to configure a volume so that it is bootable and provides a persistent virtual instance similar to traditional non-cloud based virtualization systems. In this use case the resulting instance may still have ephemeral storage depending on the flavor selected, but the root filesystem (and possibly others) will be on the persistent volume and thus state will be maintained even if the instance is shutdown. Details of this configuration are discussed in the<link href=\"http://docs.openstack.org/user-guide/content/\">OpenStack End User Guide</link>."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:59(para)
-msgid "Volumes do not provide concurrent access from multiple instances. For that you need either a traditional network filesystem like NFS or CIFS or a cluster filesystem such as GlusterFS. These may be built within an OpenStack cluster or provisioned outside of it, but are not features provided by the OpenStack software."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:65(para)
-msgid "The OpenStack Block Storage service works via the interaction of a series of daemon processes named cinder-* that reside persistently on the host machine or machines. The binaries can all be run from a single node, or spread across multiple nodes. They can also be run on the same node as other OpenStack services."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:71(guilabel)
-msgid "The current services available in OpenStack Block Storage are:"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:75(para)
-msgid "<emphasis role=\"bold\">cinder-api</emphasis> - The cinder-api service is a WSGI app that authenticates and routes requests throughout the Block Storage system. It supports the OpenStack API's only, although there is a translation that can be done via Nova's EC2 interface which calls in to the cinderclient."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:85(para)
-msgid "<emphasis role=\"bold\">cinder-scheduler</emphasis> - The cinder-scheduler is responsible for scheduling/routing requests to the appropriate volume service. As of Grizzly; depending upon your configuration this may be simple round-robin scheduling to the running volume services, or it can be more sophisticated through the use of the Filter Scheduler. The Filter Scheduler is the default in Grizzly and enables filter on things like Capacity, Availability Zone, Volume Types and Capabilities as well as custom filters."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:99(para)
-msgid "<emphasis role=\"bold\">cinder-volume</emphasis> - The cinder-volume service is responsible for managing Block Storage devices, specifically the back-end devices themselves."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:107(para)
-msgid "<emphasis role=\"bold\">cinder-backup</emphasis> - The cinder-backup service provides a means to back up a Cinder Volume to OpenStack Object Store (SWIFT)."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:112(guilabel)
-msgid "Introduction to OpenStack Block Storage"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:114(para)
-msgid "OpenStack Block Storage provides persistent High Performance Block Storage resources that can be consumed by OpenStack Compute instances. This includes secondary attached storage similar to Amazon's Elastic Block Storage (EBS). In addition images can be written to a Block Storage device and specified for OpenStack Compute to use a bootable persistent instance."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:120(para)
-msgid "There are some differences from Amazon's EBS that one should be aware of. OpenStack Block Storage is not a shared storage solution like NFS, but currently is designed so that the device is attached and in use by a single instance at a time."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:124(guilabel)
-msgid "Backend Storage Devices"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:125(para)
-msgid "OpenStack Block Storage requires some form of back-end storage that the service is built on. The default implementation is to use LVM on a local Volume Group named \"cinder-volumes\". In addition to the base driver implementation, OpenStack Block Storage also provides the means to add support for other storage devices to be utilized such as external Raid Arrays or other Storage appliances."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:132(guilabel) ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:73(guilabel)
-msgid "Users and Tenants (Projects)"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:133(para)
-msgid "The OpenStack Block Storage system is designed to be used by many different cloud computing consumers or customers, basically tenants on a shared system, using role-based access assignments. Roles control the actions that a user is allowed to perform. In the default configuration, most actions do not require a particular role, but this is configurable by the system administrator editing the appropriate policy.json file that maintains the rules. A user's access to particular volumes is limited by tenant, but the username and password are assigned per user. Key pairs granting access to a volume are enabled per user, but quotas to control resource consumption across available hardware resources are per tenant."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:145(guilabel) ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:98(para)
-msgid "For tenants, quota controls are available to limit the:"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:149(para) ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:102(para)
-msgid "Number of volumes which may be created"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:152(para)
-msgid "Number of snapshots which may be created"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:155(para)
-msgid "Total number of Giga Bytes allowed per tenant (shared between snapshots and volumes)"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:159(guilabel)
-msgid "Volumes Snapshots and Backups"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:160(para)
-msgid "This introduction provides a high level overview of the two basic resources offered by the OpenStack Block Storage service. The first is Volumes and the second is Snapshots which are derived from Volumes."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:164(guilabel) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:127(emphasis)
-msgid "Volumes"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:165(para)
-msgid "Volumes are allocated block storage resources that can be attached to instances as secondary storage or they can be used as the root store to boot instances. Volumes are persistent R/W Block Storage devices most commonly attached to the compute node via iSCSI."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:170(guilabel)
-msgid "Snapshots"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:171(para)
-msgid "A Snapshot in OpenStack Block Storage is a read-only point in time copy of a Volume. The Snapshot can be created from a Volume that is currently in use (via the use of '--force True') or in an available state. The Snapshot can then be used to create a new volume via create from snapshot."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:176(guilabel)
-msgid "Backups"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:177(para)
-msgid "A Backup is an archived copy of a Volume currently stored in Object Storage (Swift)."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:179(guilabel)
-msgid "Managing Volumes"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:180(para)
-msgid "Cinder is the OpenStack service that allows you to give extra block level storage to your OpenStack Compute instances. You may recognize this as a similar offering from Amazon EC2 known as Elastic Block Storage (EBS). The default Cinder implementation is an iSCSI solution that employs the use of Logical Volume Manager (LVM) for Linux. Note that a volume may only be attached to one instance at a time. This is not a ‘shared storage’ solution like a SAN of NFS on which multiple servers can attach to. It's also important to note that Cinder also includes a number of drivers to allow you to use a number of other vendor's back-end storage devices in addition to or instead of the base LVM implementation."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:192(para)
-msgid "Here is brief walk-through of a simple create/attach sequence, keep in mind this requires proper configuration of both OpenStack Compute via cinder.conf and OpenStack Block Storage via cinder.conf."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:198(para)
-msgid "The volume is created via cinder create; which creates an LV into the volume group (VG) \"cinder-volumes\""
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:202(para)
-msgid "The volume is attached to an instance via nova volume-attach; which creates a unique iSCSI IQN that will be exposed to the compute node"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:207(para)
-msgid "The compute node which run the concerned instance has now an active ISCSI session; and a new local storage (usually a /dev/sdX disk)"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:212(para)
-msgid "libvirt uses that local storage as a storage for the instance; the instance get a new disk (usually a /dev/vdX disk)"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:217(guilabel)
-msgid "Block Storage Capabilities"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:220(para) ./doc/training-guides/module001-ch003-core-projects.xml:374(para)
-msgid "OpenStack provides persistent block level storage devices for use with OpenStack compute instances."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:224(para) ./doc/training-guides/module001-ch003-core-projects.xml:378(para)
-msgid "The block storage system manages the creation, attaching and detaching of the block devices to servers. Block storage volumes are fully integrated into OpenStack Compute and the Dashboard allowing for cloud users to manage their own storage needs."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:231(para) ./doc/training-guides/module001-ch003-core-projects.xml:385(para)
-msgid "In addition to using simple Linux server storage, it has unified storage support for numerous storage platforms including Ceph, NetApp, Nexenta, SolidFire, and Zadara."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:237(para) ./doc/training-guides/module001-ch003-core-projects.xml:391(para)
-msgid "Block storage is appropriate for performance sensitive scenarios such as database storage, expandable file systems, or providing a server with access to raw block level storage."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch011-block-storage.xml:243(para) ./doc/training-guides/module001-ch003-core-projects.xml:397(para)
-msgid "Snapshot management provides powerful functionality for backing up data stored on block storage volumes. Snapshots can be restored or used to create a new block storage volume."
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch008-developer-apis-day-three-quiz.xml:6(title)
-msgid "Developer APIs in Depth Day Three Quiz"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch008-developer-apis-day-three-quiz.xml:8(title)
-msgid "Day 3, 16:40 to 17:00"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch003-developer-getting-started-quiz.xml:6(title) ./doc/training-guides/bk002-ch003-operator-getting-started-quiz.xml:6(title) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:6(title)
-msgid "Getting Started Quiz"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch003-developer-getting-started-quiz.xml:8(title) ./doc/training-guides/bk002-ch003-operator-getting-started-quiz.xml:8(title) ./doc/training-guides/bk001-ch006-associate-compute-node-quiz.xml:8(title)
-msgid "Day 1, 16:40 to 17:00"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch012-associate-review-concept.xml:6(title)
-msgid "Review of Concepts"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch012-associate-review-concept.xml:8(title)
-msgid "Day 2, 16:00 to 17:00"
-msgstr ""
-
-#: ./doc/training-guides/bk002-ch015-operator-object-storage-node-quiz.xml:6(title) ./doc/training-guides/bk001-bk010-associate-object-storage-node-quiz.xml:5(title)
-msgid "Object Storage Node Quiz"
-msgstr ""
-
-#: ./doc/training-guides/bk002-ch015-operator-object-storage-node-quiz.xml:8(title) ./doc/training-guides/bk003-ch021-developer-how-to-participate-day-nine-quiz.xml:8(title)
-msgid "Day 9, 16:40 to 17:00"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/training-guides/module001-ch001-intro-text.xml:102(None)
-msgid "@@image: 'figures/image11.png'; md5=e7c8929df3b2e7037fa3a032a7e8370e"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch001-intro-text.xml:6(title)
-msgid "Introduction to OpenStack"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch001-intro-text.xml:7(para)
-msgid "OpenStack is a cloud operating system that controls large pools of compute, storage, and networking resources throughout a data center, all managed through a dashboard that gives administrators control while empowering users to provision resources through a web interface."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch001-intro-text.xml:12(para)
-msgid "Cloud computing provides users with access to a shared collection of computing resources: networks for transfer, servers for storage, and applications or services for completing tasks."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch001-intro-text.xml:16(para)
-msgid "The compelling features of a cloud are:"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch001-intro-text.xml:19(para)
-msgid "On-demand self-service: Users can automatically provision needed computing capabilities, such as server time and network storage, without requiring human interaction with each service provider."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch001-intro-text.xml:25(para)
-msgid "Network access: Any computing capabilities are available over the network. Many different devices are allowed access through standardized mechanisms."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch001-intro-text.xml:30(para)
-msgid "Resource pooling: Multiple users can access clouds that serve other consumers according to demand."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch001-intro-text.xml:34(para)
-msgid "Elasticity: Provisioning is rapid and scales out or is based on need."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch001-intro-text.xml:38(para)
-msgid "Metered or measured service: Cloud systems can optimize and control resource use at the level that is appropriate for the service. Services include storage, processing, bandwidth, and active user accounts. Monitoring and reporting of resource usage provides transparency for both the provider and consumer of the utilized service."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch001-intro-text.xml:46(para)
-msgid "Cloud computing offers different service models depending on the capabilities a consumer may require."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch001-intro-text.xml:50(para)
-msgid "SaaS: Software-as-a-Service. Provides the consumer the ability to use the software in a cloud environment, such as web-based email for example."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch001-intro-text.xml:55(para)
-msgid "PaaS: Platform-as-a-Service. Provides the consumer the ability to deploy applications through a programming language or tools supported by the cloud platform provider. An example of Platform-as-a-service is an Eclipse/Java programming platform provided with no downloads required."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch001-intro-text.xml:62(para)
-msgid "IaaS: Infrastructure-as-a-Service. Provides infrastructure such as computer instances, network connections, and storage so that people can run any software or operating system."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch001-intro-text.xml:68(para)
-msgid "Terms such as public cloud or private cloud refer to the deployment model for the cloud. A private cloud operates for a single organization, but can be managed on-premise or off-premise. A public cloud has an infrastructure that is available to the general public or a large industry group and is likely owned by a cloud services company."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch001-intro-text.xml:74(para)
-msgid "Clouds can also be described as hybrid. A hybrid cloud can be a deployment model, as a composition of both public and private clouds, or a hybrid model for cloud computing may involve both virtual and physical servers."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch001-intro-text.xml:78(para)
-msgid "Cloud computing can help with large-scale computing needs or can lead consolidation efforts by virtualizing servers to make more use of existing hardware and potentially release old hardware from service. Cloud computing is also used for collaboration because of its high availability through networked computers. Productivity suites for word processing, number crunching, and email communications, and more are also available through cloud computing. Cloud computing also avails additional storage to the cloud user, avoiding the need for additional hard drives on each user's desktop and enabling access to huge data storage capacity online in the cloud."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch001-intro-text.xml:89(para)
-msgid "When you explore OpenStack and see what it means technically, you can see its reach and impact on the entire world."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch001-intro-text.xml:91(para)
-msgid "OpenStack is an open source software for building private and public clouds which delivers a massively scalable cloud operating system."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch001-intro-text.xml:97(td)
-msgid "OpenStack is backed up by a global community of technologists, developers, researchers, corporations and cloud computing experts."
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch015-developer-how-to-participate-day-six-quiz.xml:6(title)
-msgid "Developer How To Participate Day Six Quiz"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch015-developer-how-to-participate-day-six-quiz.xml:8(title)
-msgid "Day 6, 16:40 to 17:00"
-msgstr ""
-
-#: ./doc/training-guides/lab000-important-terms.xml:6(title)
-msgid "Important terms"
-msgstr ""
-
-#: ./doc/training-guides/lab000-important-terms.xml:8(title)
-msgid "Host Operating System (Host)"
-msgstr ""
-
-#: ./doc/training-guides/lab000-important-terms.xml:9(para)
-msgid "The operating system that is installed on your laptop or desktop that hosts virtual machines. This is commonly referred to as the host OS or <glossterm>host</glossterm>. In short, the machine where your Virtual Box is installed."
-msgstr ""
-
-#: ./doc/training-guides/lab000-important-terms.xml:16(title)
-msgid "Guest Operating System (Guest)"
-msgstr ""
-
-#: ./doc/training-guides/lab000-important-terms.xml:17(para)
-msgid "The operating system that is installed on your Virtual Box Virtual Machine. This virtual instance is independent of the host OS. It is commonly referred to as <glossterm>guest OS</glossterm> or guest."
-msgstr ""
-
-#: ./doc/training-guides/lab000-important-terms.xml:23(title)
-msgid "Node"
-msgstr ""
-
-#: ./doc/training-guides/lab000-important-terms.xml:24(para)
-msgid "In this context, refers specifically to servers. Each OpenStack server is a node."
-msgstr ""
-
-#: ./doc/training-guides/lab000-important-terms.xml:28(title) ./doc/training-guides/lab001-control-node.xml:6(title)
-msgid "Control Node"
-msgstr ""
-
-#: ./doc/training-guides/lab000-important-terms.xml:29(para)
-msgid "Hosts the database, Keystone (Middleware), and the servers for the scope of the current OpenStack deployment. It acts as the brains behind OpenStack and drives services such as authentication, database, and so on."
-msgstr ""
-
-#: ./doc/training-guides/lab000-important-terms.xml:35(title) ./doc/training-guides/lab003-compute-node.xml:7(title) ./doc/training-guides/lab003-compute-node.xml:32(guilabel) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:8(title) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:8(title)
-msgid "Compute Node"
-msgstr ""
-
-#: ./doc/training-guides/lab000-important-terms.xml:36(para)
-msgid "Has the required Hypervisor (Qemu/KVM) and is your Virtual Machine host."
-msgstr ""
-
-#: ./doc/training-guides/lab000-important-terms.xml:40(title) ./doc/training-guides/lab002-network-node.xml:4(title) ./doc/training-guides/lab002-network-node.xml:27(guilabel) ./doc/training-guides/bk002-ch010-operator-network-node.xml:8(title) ./doc/training-guides/bk001-ch007-associate-network-node.xml:8(title)
-msgid "Network Node"
-msgstr ""
-
-#: ./doc/training-guides/lab000-important-terms.xml:41(para)
-msgid "Provides Network-as-a-Service and virtual networks for OpenStack."
-msgstr ""
-
-#: ./doc/training-guides/lab000-important-terms.xml:45(title)
-msgid "Using OpenSSH"
-msgstr ""
-
-#: ./doc/training-guides/lab000-important-terms.xml:46(para)
-msgid "After the network interfaces file has been setup, you can switch to an SSH session by using an OpenSSH client to log in remotely to the required server node (Control, Network, Compute). Open a terminal on your host machine and run the following command: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/training-guides/card007-core-overview.xml:7(title)
-msgid "Core Project Overview"
-msgstr ""
-
-#: ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:6(title)
-msgid "Object Storage Node Lab"
-msgstr ""
-
-#: ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:8(title)
-msgid "Day 9, 13:30 to 14:45, 15:00 to 17:00"
-msgstr ""
-
-#: ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:12(title)
-msgid "Installing Object Node"
-msgstr ""
-
-#: ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:19(title)
-msgid "Configuring Object Node"
-msgstr ""
-
-#: ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:26(title)
-msgid "Configuring Object Proxy"
-msgstr ""
-
-#: ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:33(title)
-msgid "Start Object Node Services"
-msgstr ""
-
-#: ./doc/training-guides/st-training-guides.xml:7(title) ./doc/training-guides/st-training-guides.xml:9(titleabbrev) ./doc/training-guides/st-training-guides.xml:15(productname)
-msgid "OpenStack Training Guides"
-msgstr ""
-
-#: ./doc/training-guides/st-training-guides.xml:12(year)
-msgid "2013"
-msgstr ""
-
-#: ./doc/training-guides/st-training-guides.xml:13(holder)
-msgid "OpenStack Foundation"
-msgstr ""
-
-#: ./doc/training-guides/st-training-guides.xml:18(remark) ./doc/training-guides/st-training-guides.xml:22(remark)
-msgid "Copyright details are filled in by the template."
-msgstr ""
-
-#: ./doc/training-guides/st-training-guides.xml:26(para)
-msgid "OpenStack™ Training Guides offer the open source community software training for cloud administration and management for any organization."
-msgstr ""
-
-#: ./doc/training-guides/st-training-guides.xml:33(date)
-msgid "2013-11-04"
-msgstr ""
-
-#: ./doc/training-guides/st-training-guides.xml:37(para)
-msgid "major restructure of guides"
-msgstr ""
-
-#: ./doc/training-guides/st-training-guides.xml:43(date)
-msgid "2013-09-11"
-msgstr ""
-
-#: ./doc/training-guides/st-training-guides.xml:47(para)
-msgid "first training guides sprint held"
-msgstr ""
-
-#: ./doc/training-guides/st-training-guides.xml:53(date)
-msgid "2013-08-07"
-msgstr ""
-
-#: ./doc/training-guides/st-training-guides.xml:57(para)
-msgid "rough draft published to the web"
-msgstr ""
-
-#: ./doc/training-guides/st-training-guides.xml:63(date)
-msgid "2013-07-09"
-msgstr ""
-
-#: ./doc/training-guides/st-training-guides.xml:67(para)
-msgid "first draft released"
-msgstr ""
-
-#: ./doc/training-guides/st-training-guides.xml:73(date)
-msgid "2013-06-18"
-msgstr ""
-
-#: ./doc/training-guides/st-training-guides.xml:77(para)
-msgid "blueprint created"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:178(None)
-msgid "@@image: 'figures/image21.png'; md5=77049345dd5d86f8f7abe03c0497b1f2"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:197(None)
-msgid "@@image: 'figures/image09.png'; md5=69ea6c4853c189bd8c387bb4e534f6a2"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:234(None)
-msgid "@@image: 'figures/image22.png'; md5=d92dca8de8639d5a26cef1c8fcc592ed"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:7(title)
-msgid "VM Provisioning Walk Through"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:8(para)
-msgid "More Content To be Added ..."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:9(para)
-msgid "OpenStack Compute gives you a tool to orchestrate a cloud, including running instances, managing networks, and controlling access to the cloud through users and projects. The underlying open source project's name is Nova, and it provides the software that can control an Infrastructure-as-a-Service (IaaS) cloud computing platform. It is similar in scope to Amazon EC2 and Rackspace Cloud Servers. OpenStack Compute does not include any virtualization software; rather it defines drivers that interact with underlying virtualization mechanisms that run on your host operating system, and exposes functionality over a web-based API."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:20(guilabel)
-msgid "Hypervisors"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:21(para)
-msgid "OpenStack Compute requires a hypervisor and Compute controls the hypervisors through an API server. The process for selecting a hypervisor usually means prioritizing and making decisions based on budget and resource constraints as well as the inevitable list of supported features and required technical specifications. The majority of development is done with the KVM and Xen-based hypervisors. Refer to <link href=\"http://wiki.openstack.org/HypervisorSupportMatrix\"/><link href=\"http://goo.gl/n7AXnC\"> http://goo.gl/n7AXnC</link> for a detailed list of features and support across the hypervisors."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:32(para)
-msgid "With OpenStack Compute, you can orchestrate clouds using multiple hypervisors in different zones. The types of virtualization standards that may be used with Compute include:"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:38(para)
-msgid "KVM- Kernel-based Virtual Machine (visit <link href=\"http://goo.gl/70dvRb\">http://goo.gl/70dvRb</link>)"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:43(para)
-msgid "LXC- Linux Containers (through libvirt) (visit <link href=\"http://goo.gl/Ous3ly\">http://goo.gl/Ous3ly</link>)"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:48(para)
-msgid "QEMU- Quick EMUlator (visit <link href=\"http://goo.gl/WWV9lL\">http://goo.gl/WWV9lL</link>)"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:53(para)
-msgid "UML- User Mode Linux (visit <link href=\"http://goo.gl/4HAkJj\">http://goo.gl/4HAkJj</link>)"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:58(para)
-msgid "VMWare vSphere4.1 update 1 and newer (visit <link href=\"http://goo.gl/0DBeo5\">http://goo.gl/0DBeo5</link>)"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:63(para)
-msgid "Xen- Xen, Citrix XenServer and Xen Cloud Platform (XCP) (visit <link href=\"http://goo.gl/yXP9t1\">http://goo.gl/yXP9t1</link>)"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:68(para)
-msgid "Bare Metal- Provisions physical hardware via pluggable sub-drivers. (visit <link href=\"http://goo.gl/exfeSg\">http://goo.gl/exfeSg</link>)"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:74(para)
-msgid "The OpenStack Compute system is designed to be used by many different cloud computing consumers or customers, basically tenants on a shared system, using role-based access assignments. Roles control the actions that a user is allowed to perform. In the default configuration, most actions do not require a particular role, but this is configurable by the system administrator editing the appropriate <filename>policy.json</filename> file that maintains the rules. For example, a rule can be defined so that a user cannot allocate a public IP without the admin role. A user's access to particular images is limited by tenant, but the username and password are assigned per user. Key pairs granting access to an instance are enabled per user, but quotas to control resource consumption across available hardware resources are per tenant."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:89(para)
-msgid "While the original EC2 API supports users, OpenStack Compute adds the concept of tenants. Tenants are isolated resource containers forming the principal organizational structure within the Compute service. They consist of a separate VLAN, volumes, instances, images, keys, and users. A user can specify which tenant he or she wishes to be known as by appending :project_id to his or her access key. If no tenant is specified in the API request, Compute attempts to use a tenant with the same ID as the user"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:105(para)
-msgid "Total size of all volumes within a project as measured in GB"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:109(para)
-msgid "Number of instances which may be launched"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:112(para)
-msgid "Number of processor cores which may be allocated"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:115(para)
-msgid "Floating IP addresses (assigned to any instance when it launches so the instance has the same publicly accessible IP addresses)"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:120(para)
-msgid "Fixed IP addresses (assigned to the same instance each time it boots, publicly or privately accessible, typically private for management purposes)"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:125(guilabel) ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:163(guilabel)
-msgid "Images and Instances"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:126(para)
-msgid "This introduction provides a high level overview of what images and instances are and description of the life-cycle of a typical virtual system within the cloud. There are many ways to configure the details of an OpenStack cloud and many ways to implement a virtual system within that cloud. These configuration details as well as the specific command-line utilities and API calls to perform the actions described are presented in the Image Management and Volume Management chapters."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:135(para)
-msgid "Images are disk images which are templates for virtual machine file systems. The OpenStack Image Service is responsible for the storage and management of images within OpenStack."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:139(para)
-msgid "Instances are the individual virtual machines running on physical compute nodes. The OpenStack Compute service manages instances. Any number of instances maybe started from the same image. Each instance is run from a copy of the base image so runtime changes made by an instance do not change the image it is based on. Snapshots of running instances may be taken which create a new image based on the current disk state of a particular instance."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:147(para)
-msgid "When starting an instance a set of virtual resources known as a flavor must be selected. Flavors define how many virtual CPUs an instance has and the amount of RAM and size of its ephemeral disks. OpenStack provides a number of predefined flavors which cloud administrators may edit or add to. Users must select from the set of available flavors defined on their cloud."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:154(para)
-msgid "Additional resources such as persistent volume storage and public IP address may be added to and removed from running instances. The examples below show the cinder-volume service which provide persistent block storage as opposed to the ephemeral storage provided by the instance flavor."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:159(para)
-msgid "Here is an example of the life cycle of a typical virtual system within an OpenStack cloud to illustrate these concepts."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:162(guilabel) ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:175(title)
-msgid "Initial State"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:164(para)
-msgid "The following diagram shows the system state prior to launching an instance. The image store fronted by the Image Service has some number of predefined images. In the cloud, there is an available compute node with available vCPU, memory and local disk resources. Plus there are a number of predefined volumes in the <systemitem class=\"service\">cinder-volume</systemitem> service."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:172(para)
-msgid "Figure 2.1. Base image state with no running instances"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:182(guilabel)
-msgid "Launching an instance"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:183(para)
-msgid "To launch an instance, the user selects an image, a flavor, and other optional attributes. In this case the selected flavor provides a root volume (as all flavors do) labeled vda in the diagram and additional ephemeral storage labeled vdb in the diagram. The user has also opted to map a volume from the <systemitem class=\"service\">cinder-volume</systemitem> store to the third virtual disk, vdc, on this instance."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:191(para)
-msgid "Figure 2.2. Instance creation from image and run time state"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:194(title)
-msgid "Launch VM Instance"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:201(para)
-msgid "The OpenStack system copies the base image from the image store to local disk which is used as the first disk of the instance (vda). Having small images will result in faster start up of your instances as less data needs to be copied across the network. The system also creates a new empty disk image to present as the second disk (vdb). Be aware that the second disk is an empty disk with an emphemeral life as it is destroyed when you delete the instance. The compute node attaches to the requested <systemitem class=\"service\">cinder-volume</systemitem> using iSCSI and maps this to the third disk (vdc) as requested. The vCPU and memory resources are provisioned and the instance is booted from the first drive. The instance runs and changes data on the disks indicated in red in the diagram."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:215(para)
-msgid "There are many possible variations in the details of the scenario, particularly in terms of what the backing storage is and the network protocols used to attach and move storage. One variant worth mentioning here is that the ephemeral storage used for volumes vda and vdb in this example may be backed by network storage rather than local disk. The details are left for later chapters."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:222(guilabel) ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:231(title)
-msgid "End State"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:223(para)
-msgid "Once the instance has served its purpose and is deleted all state is reclaimed, except the persistent volume. The ephemeral storage is purged. Memory and vCPU resources are released. And of course the image has remained unchanged throughout."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:228(para)
-msgid "Figure 2.3. End state of image and volume after instance exits"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:238(para)
-msgid "Once you launch a VM in OpenStack, there's something more going on in the background. To understand what's happening behind the dashboard, lets take a deeper dive into OpenStack’s VM provisioning. For launching a VM, you can either use the command-line interfaces or the OpenStack dashboard."
+#: ./doc/training-guides/bk003-ch007-developer-apis-day-three-lab.xml:8(title)
+msgid "Day 3, 13:30 to 14:45, 15:00 to 16:30"
 msgstr ""
 
 #: ./doc/training-guides/operator-editing-code.xml:6(title)
@@ -1420,7 +295,7 @@ msgstr ""
 msgid "Then, enter your Launchpad account information."
 msgstr ""
 
-#: ./doc/training-guides/operator-editing-code.xml:240(title) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:19(title) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:19(title)
+#: ./doc/training-guides/operator-editing-code.xml:240(title) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:19(title) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:19(title)
 msgid "Fix a Documentation Bug"
 msgstr ""
 
@@ -1580,7 +455,7 @@ msgstr ""
 msgid "Follow the instructions for fixing a bug in the Fix a Documentation Bug section."
 msgstr ""
 
-#: ./doc/training-guides/operator-editing-code.xml:433(title) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:33(title) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:33(title)
+#: ./doc/training-guides/operator-editing-code.xml:433(title) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:33(title) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:33(title)
 msgid "Create a Branch"
 msgstr ""
 
@@ -1688,408 +563,324 @@ msgstr ""
 msgid "Move the card from Doing to Done."
 msgstr ""
 
-#: ./doc/training-guides/card025.xml:6(title)
-msgid "Role of the Controller Node"
+#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml:8(title) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:8(title) ./doc/training-guides/lab000-important-terms.xml:35(title) ./doc/training-guides/lab003-compute-node.xml:7(title) ./doc/training-guides/lab003-compute-node.xml:32(guilabel)
+msgid "Compute Node"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml:10(title)
+msgid "Day 1, 15:00 to 17:00"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml:14(title) ./doc/training-guides/module001-ch009-vm-placement.xml:7(title)
+msgid "VM Placement"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml:21(title) ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:7(title)
+msgid "VM provisioning in-depth"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml:28(title) ./doc/training-guides/module001-ch011-block-storage.xml:6(title)
+msgid "OpenStack Block Storage"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml:35(title) ./doc/training-guides/bk001-ch007-associate-network-node.xml:28(title) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:28(title) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:35(title)
+msgid "Administration Tasks"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml:37(title)
+msgid "Block Storage CLI Commands"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml:44(title)
+msgid "Block Storage Manage Volumes"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml:51(title)
+msgid "Compute CLI Commands"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml:58(title)
+msgid "Compute Image creation"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml:65(title)
+msgid "Compute Boot Instance"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml:72(title)
+msgid "Compute Terminate Instance"
 msgstr ""
 
 #. When image changes, this message will be marked fuzzy or untranslated for you.
 #. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:11(None)
-msgid "@@image: 'figures/image04.png'; md5=dd0c42b457e2b17fd94e4f62c16b9c37"
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:178(None)
+msgid "@@image: 'figures/image21.png'; md5=77049345dd5d86f8f7abe03c0497b1f2"
 msgstr ""
 
 #. When image changes, this message will be marked fuzzy or untranslated for you.
 #. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:47(None)
-msgid "@@image: 'figures/image24.png'; md5=aea2956c5e4f01e06171d8d5e1de49b5"
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:197(None)
+msgid "@@image: 'figures/image09.png'; md5=69ea6c4853c189bd8c387bb4e534f6a2"
 msgstr ""
 
 #. When image changes, this message will be marked fuzzy or untranslated for you.
 #. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:149(None) ./doc/training-guides/module001-ch008-queues-messaging.xml:207(None)
-msgid "@@image: 'figures/image20.png'; md5=c2cab17b6ee560943403c1d998d7a9d7"
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:234(None)
+msgid "@@image: 'figures/image22.png'; md5=d92dca8de8639d5a26cef1c8fcc592ed"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:7(title)
+msgid "VM Provisioning Walk Through"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:8(para)
+msgid "More Content To be Added ..."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:9(para)
+msgid "OpenStack Compute gives you a tool to orchestrate a cloud, including running instances, managing networks, and controlling access to the cloud through users and projects. The underlying open source project's name is Nova, and it provides the software that can control an Infrastructure-as-a-Service (IaaS) cloud computing platform. It is similar in scope to Amazon EC2 and Rackspace Cloud Servers. OpenStack Compute does not include any virtualization software; rather it defines drivers that interact with underlying virtualization mechanisms that run on your host operating system, and exposes functionality over a web-based API."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:20(guilabel)
+msgid "Hypervisors"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:21(para)
+msgid "OpenStack Compute requires a hypervisor and Compute controls the hypervisors through an API server. The process for selecting a hypervisor usually means prioritizing and making decisions based on budget and resource constraints as well as the inevitable list of supported features and required technical specifications. The majority of development is done with the KVM and Xen-based hypervisors. Refer to <link href=\"http://wiki.openstack.org/HypervisorSupportMatrix\"/><link href=\"http://goo.gl/n7AXnC\"> http://goo.gl/n7AXnC</link> for a detailed list of features and support across the hypervisors."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:32(para)
+msgid "With OpenStack Compute, you can orchestrate clouds using multiple hypervisors in different zones. The types of virtualization standards that may be used with Compute include:"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:38(para)
+msgid "KVM- Kernel-based Virtual Machine (visit <link href=\"http://goo.gl/70dvRb\">http://goo.gl/70dvRb</link>)"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:43(para)
+msgid "LXC- Linux Containers (through libvirt) (visit <link href=\"http://goo.gl/Ous3ly\">http://goo.gl/Ous3ly</link>)"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:48(para)
+msgid "QEMU- Quick EMUlator (visit <link href=\"http://goo.gl/WWV9lL\">http://goo.gl/WWV9lL</link>)"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:53(para)
+msgid "UML- User Mode Linux (visit <link href=\"http://goo.gl/4HAkJj\">http://goo.gl/4HAkJj</link>)"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:58(para)
+msgid "VMWare vSphere4.1 update 1 and newer (visit <link href=\"http://goo.gl/0DBeo5\">http://goo.gl/0DBeo5</link>)"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:63(para)
+msgid "Xen- Xen, Citrix XenServer and Xen Cloud Platform (XCP) (visit <link href=\"http://goo.gl/yXP9t1\">http://goo.gl/yXP9t1</link>)"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:68(para)
+msgid "Bare Metal- Provisions physical hardware via pluggable sub-drivers. (visit <link href=\"http://goo.gl/exfeSg\">http://goo.gl/exfeSg</link>)"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:73(guilabel) ./doc/training-guides/module001-ch011-block-storage.xml:132(guilabel)
+msgid "Users and Tenants (Projects)"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:74(para)
+msgid "The OpenStack Compute system is designed to be used by many different cloud computing consumers or customers, basically tenants on a shared system, using role-based access assignments. Roles control the actions that a user is allowed to perform. In the default configuration, most actions do not require a particular role, but this is configurable by the system administrator editing the appropriate <filename>policy.json</filename> file that maintains the rules. For example, a rule can be defined so that a user cannot allocate a public IP without the admin role. A user's access to particular images is limited by tenant, but the username and password are assigned per user. Key pairs granting access to an instance are enabled per user, but quotas to control resource consumption across available hardware resources are per tenant."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:89(para)
+msgid "While the original EC2 API supports users, OpenStack Compute adds the concept of tenants. Tenants are isolated resource containers forming the principal organizational structure within the Compute service. They consist of a separate VLAN, volumes, instances, images, keys, and users. A user can specify which tenant he or she wishes to be known as by appending :project_id to his or her access key. If no tenant is specified in the API request, Compute attempts to use a tenant with the same ID as the user"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:98(para) ./doc/training-guides/module001-ch011-block-storage.xml:145(guilabel)
+msgid "For tenants, quota controls are available to limit the:"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:102(para) ./doc/training-guides/module001-ch011-block-storage.xml:149(para)
+msgid "Number of volumes which may be created"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:105(para)
+msgid "Total size of all volumes within a project as measured in GB"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:109(para)
+msgid "Number of instances which may be launched"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:112(para)
+msgid "Number of processor cores which may be allocated"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:115(para)
+msgid "Floating IP addresses (assigned to any instance when it launches so the instance has the same publicly accessible IP addresses)"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:120(para)
+msgid "Fixed IP addresses (assigned to the same instance each time it boots, publicly or privately accessible, typically private for management purposes)"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:125(guilabel) ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:163(guilabel)
+msgid "Images and Instances"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:126(para)
+msgid "This introduction provides a high level overview of what images and instances are and description of the life-cycle of a typical virtual system within the cloud. There are many ways to configure the details of an OpenStack cloud and many ways to implement a virtual system within that cloud. These configuration details as well as the specific command-line utilities and API calls to perform the actions described are presented in the Image Management and Volume Management chapters."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:135(para)
+msgid "Images are disk images which are templates for virtual machine file systems. The OpenStack Image Service is responsible for the storage and management of images within OpenStack."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:139(para)
+msgid "Instances are the individual virtual machines running on physical compute nodes. The OpenStack Compute service manages instances. Any number of instances maybe started from the same image. Each instance is run from a copy of the base image so runtime changes made by an instance do not change the image it is based on. Snapshots of running instances may be taken which create a new image based on the current disk state of a particular instance."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:147(para)
+msgid "When starting an instance a set of virtual resources known as a flavor must be selected. Flavors define how many virtual CPUs an instance has and the amount of RAM and size of its ephemeral disks. OpenStack provides a number of predefined flavors which cloud administrators may edit or add to. Users must select from the set of available flavors defined on their cloud."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:154(para)
+msgid "Additional resources such as persistent volume storage and public IP address may be added to and removed from running instances. The examples below show the cinder-volume service which provide persistent block storage as opposed to the ephemeral storage provided by the instance flavor."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:159(para)
+msgid "Here is an example of the life cycle of a typical virtual system within an OpenStack cloud to illustrate these concepts."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:162(guilabel) ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:175(title)
+msgid "Initial State"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:164(para)
+msgid "The following diagram shows the system state prior to launching an instance. The image store fronted by the Image Service has some number of predefined images. In the cloud, there is an available compute node with available vCPU, memory and local disk resources. Plus there are a number of predefined volumes in the <systemitem class=\"service\">cinder-volume</systemitem> service."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:172(para)
+msgid "Figure 2.1. Base image state with no running instances"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:182(guilabel)
+msgid "Launching an instance"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:183(para)
+msgid "To launch an instance, the user selects an image, a flavor, and other optional attributes. In this case the selected flavor provides a root volume (as all flavors do) labeled vda in the diagram and additional ephemeral storage labeled vdb in the diagram. The user has also opted to map a volume from the <systemitem class=\"service\">cinder-volume</systemitem> store to the third virtual disk, vdc, on this instance."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:191(para)
+msgid "Figure 2.2. Instance creation from image and run time state"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:194(title)
+msgid "Launch VM Instance"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:201(para)
+msgid "The OpenStack system copies the base image from the image store to local disk which is used as the first disk of the instance (vda). Having small images will result in faster start up of your instances as less data needs to be copied across the network. The system also creates a new empty disk image to present as the second disk (vdb). Be aware that the second disk is an empty disk with an emphemeral life as it is destroyed when you delete the instance. The compute node attaches to the requested <systemitem class=\"service\">cinder-volume</systemitem> using iSCSI and maps this to the third disk (vdc) as requested. The vCPU and memory resources are provisioned and the instance is booted from the first drive. The instance runs and changes data on the disks indicated in red in the diagram."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:215(para)
+msgid "There are many possible variations in the details of the scenario, particularly in terms of what the backing storage is and the network protocols used to attach and move storage. One variant worth mentioning here is that the ephemeral storage used for volumes vda and vdb in this example may be backed by network storage rather than local disk. The details are left for later chapters."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:222(guilabel) ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:231(title)
+msgid "End State"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:223(para)
+msgid "Once the instance has served its purpose and is deleted all state is reclaimed, except the persistent volume. The ephemeral storage is purged. Memory and vCPU resources are released. And of course the image has remained unchanged throughout."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:228(para)
+msgid "Figure 2.3. End state of image and volume after instance exits"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml:238(para)
+msgid "Once you launch a VM in OpenStack, there's something more going on in the background. To understand what's happening behind the dashboard, lets take a deeper dive into OpenStack’s VM provisioning. For launching a VM, you can either use the command-line interfaces or the OpenStack dashboard."
 msgstr ""
 
 #. When image changes, this message will be marked fuzzy or untranslated for you.
 #. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:184(None)
-msgid "@@image: 'figures/image28.png'; md5=c813069a23d72a7a3f519d896270a62a"
+#: ./doc/training-guides/module001-ch001-intro-text.xml:102(None)
+msgid "@@image: 'figures/image11.png'; md5=e7c8929df3b2e7037fa3a032a7e8370e"
 msgstr ""
 
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:6(title) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:28(title)
-msgid "OpenStack Messaging and Queues"
+#: ./doc/training-guides/module001-ch001-intro-text.xml:6(title)
+msgid "Introduction to OpenStack"
 msgstr ""
 
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:8(title)
-msgid "Messaging in OpenStack"
+#: ./doc/training-guides/module001-ch001-intro-text.xml:7(para)
+msgid "OpenStack is a cloud operating system that controls large pools of compute, storage, and networking resources throughout a data center, all managed through a dashboard that gives administrators control while empowering users to provision resources through a web interface."
 msgstr ""
 
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:15(para)
-msgid "AMQP is the messaging technology chosen by the OpenStack cloud. The AMQP broker, either RabbitMQ or Qpid, sits between any two Nova components and allows them to communicate in a loosely coupled fashion. More precisely, Nova components (the compute fabric of OpenStack) use Remote Procedure Calls (RPC hereinafter) to communicate to one another; however such a paradigm is built atop the publish/subscribe paradigm so that the following benefits can be achieved:"
+#: ./doc/training-guides/module001-ch001-intro-text.xml:12(para)
+msgid "Cloud computing provides users with access to a shared collection of computing resources: networks for transfer, servers for storage, and applications or services for completing tasks."
 msgstr ""
 
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:25(para)
-msgid "Decoupling between client and servant (such as the client does not need to know where the servant reference is)."
+#: ./doc/training-guides/module001-ch001-intro-text.xml:16(para)
+msgid "The compelling features of a cloud are:"
 msgstr ""
 
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:30(para)
-msgid "Full a-synchronism between client and servant (such as the client does not need the servant to run at the same time of the remote call)."
+#: ./doc/training-guides/module001-ch001-intro-text.xml:19(para)
+msgid "On-demand self-service: Users can automatically provision needed computing capabilities, such as server time and network storage, without requiring human interaction with each service provider."
 msgstr ""
 
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:35(para)
-msgid "Random balancing of remote calls (such as if more servants are up and running, one-way calls are transparently dispatched to the first available servant)."
+#: ./doc/training-guides/module001-ch001-intro-text.xml:25(para)
+msgid "Network access: Any computing capabilities are available over the network. Many different devices are allowed access through standardized mechanisms."
 msgstr ""
 
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:40(para)
-msgid "Nova uses direct, fanout, and topic-based exchanges. The architecture looks like the one depicted in the figure below:"
+#: ./doc/training-guides/module001-ch001-intro-text.xml:30(para)
+msgid "Resource pooling: Multiple users can access clouds that serve other consumers according to demand."
 msgstr ""
 
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:44(title)
-msgid "AMQP"
+#: ./doc/training-guides/module001-ch001-intro-text.xml:34(para)
+msgid "Elasticity: Provisioning is rapid and scales out or is based on need."
 msgstr ""
 
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:51(para)
-msgid "Nova implements RPC (both request+response, and one-way, respectively nicknamed ‘rpc.call’ and ‘rpc.cast’) over AMQP by providing an adapter class which take cares of marshaling and un-marshaling of messages into function calls. Each Nova service, such as Compute, Scheduler, and so on, creates two queues at the initialization time, one which accepts messages with routing keys ‘NODE-TYPE.NODE-ID’, for example, compute.hostname, and another, which accepts messages with routing keys as generic ‘NODE-TYPE’, for example compute. The former is used specifically when Nova-API needs to redirect commands to a specific node like ‘euca-terminate instance’. In this case, only the compute node whose host’s hypervisor is running the virtual machine can kill the instance. The API acts as a consumer when RPC calls are request/response, otherwise is acts as publisher only."
+#: ./doc/training-guides/module001-ch001-intro-text.xml:38(para)
+msgid "Metered or measured service: Cloud systems can optimize and control resource use at the level that is appropriate for the service. Services include storage, processing, bandwidth, and active user accounts. Monitoring and reporting of resource usage provides transparency for both the provider and consumer of the utilized service."
 msgstr ""
 
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:64(guilabel)
-msgid "Nova RPC Mappings"
+#: ./doc/training-guides/module001-ch001-intro-text.xml:46(para)
+msgid "Cloud computing offers different service models depending on the capabilities a consumer may require."
 msgstr ""
 
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:65(para)
-msgid "The figure below shows the internals of a message broker node (referred to as a RabbitMQ node in the diagrams) when a single instance is deployed and shared in an OpenStack cloud. Every component within Nova connects to the message broker and, depending on its personality, such as a compute node or a network node, may use the queue either as an Invoker (such as API or Scheduler) or a Worker (such as Compute or Network). Invokers and Workers do not actually exist in the Nova object model, but in this example they are used as an abstraction for the sake of clarity. An Invoker is a component that sends messages in the queuing system using <placeholder-1/> and <placeholder-2/>. A worker is a component that receives messages from the queuing system and replies accordingly to rcp.call operations."
+#: ./doc/training-guides/module001-ch001-intro-text.xml:50(para)
+msgid "SaaS: Software-as-a-Service. Provides the consumer the ability to use the software in a cloud environment, such as web-based email for example."
 msgstr ""
 
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:78(para)
-msgid "Figure 2 shows the following internal elements:"
+#: ./doc/training-guides/module001-ch001-intro-text.xml:55(para)
+msgid "PaaS: Platform-as-a-Service. Provides the consumer the ability to deploy applications through a programming language or tools supported by the cloud platform provider. An example of Platform-as-a-service is an Eclipse/Java programming platform provided with no downloads required."
 msgstr ""
 
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:81(para)
-msgid "<emphasis role=\"bold\">Topic Publisher:</emphasis> A Topic Publisher comes to life when an rpc.call or an rpc.cast operation is executed; this object is instantiated and used to push a message to the queuing system. Every publisher connects always to the same topic-based exchange; its life-cycle is limited to the message delivery."
+#: ./doc/training-guides/module001-ch001-intro-text.xml:62(para)
+msgid "IaaS: Infrastructure-as-a-Service. Provides infrastructure such as computer instances, network connections, and storage so that people can run any software or operating system."
 msgstr ""
 
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:89(para)
-msgid "<emphasis role=\"bold\">Direct Consumer:</emphasis> A Direct Consumer comes to life if (an only if) a rpc.call operation is executed; this object is instantiated and used to receive a response message from the queuing system; Every consumer connects to a unique direct-based exchange via a unique exclusive queue; its life-cycle is limited to the message delivery; the exchange and queue identifiers are determined by a UUID generator, and are marshaled in the message sent by the Topic Publisher (only rpc.call operations)."
+#: ./doc/training-guides/module001-ch001-intro-text.xml:68(para)
+msgid "Terms such as public cloud or private cloud refer to the deployment model for the cloud. A private cloud operates for a single organization, but can be managed on-premise or off-premise. A public cloud has an infrastructure that is available to the general public or a large industry group and is likely owned by a cloud services company."
 msgstr ""
 
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:100(para)
-msgid "<emphasis role=\"bold\">Topic Consumer:</emphasis> A Topic Consumer comes to life as soon as a Worker is instantiated and exists throughout its life-cycle; this object is used to receive messages from the queue and it invokes the appropriate action as defined by the Worker role. A Topic Consumer connects to the same topic-based exchange either via a shared queue or via a unique exclusive queue. Every Worker has two topic consumers, one that is addressed only during rpc.cast operations (and it connects to a shared queue whose exchange key is ‘topic’) and the other that is addressed only during rpc.call operations (and it connects to a unique queue whose exchange key is ‘topic.host’)."
+#: ./doc/training-guides/module001-ch001-intro-text.xml:74(para)
+msgid "Clouds can also be described as hybrid. A hybrid cloud can be a deployment model, as a composition of both public and private clouds, or a hybrid model for cloud computing may involve both virtual and physical servers."
 msgstr ""
 
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:114(para)
-msgid "<emphasis role=\"bold\">Direct Publisher:</emphasis> A Direct Publisher comes to life only during rpc.call operations and it is instantiated to return the message required by the request/response operation. The object connects to a direct-based exchange whose identity is dictated by the incoming message."
+#: ./doc/training-guides/module001-ch001-intro-text.xml:78(para)
+msgid "Cloud computing can help with large-scale computing needs or can lead consolidation efforts by virtualizing servers to make more use of existing hardware and potentially release old hardware from service. Cloud computing is also used for collaboration because of its high availability through networked computers. Productivity suites for word processing, number crunching, and email communications, and more are also available through cloud computing. Cloud computing also avails additional storage to the cloud user, avoiding the need for additional hard drives on each user's desktop and enabling access to huge data storage capacity online in the cloud."
 msgstr ""
 
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:122(para)
-msgid "<emphasis role=\"bold\">Topic Exchange:</emphasis> The Exchange is a routing table that exists in the context of a virtual host (the multi-tenancy mechanism provided by Qpid or RabbitMQ); its type (such as topic vs. direct) determines the routing policy; a message broker node will have only one topic-based exchange for every topic in Nova."
+#: ./doc/training-guides/module001-ch001-intro-text.xml:89(para)
+msgid "When you explore OpenStack and see what it means technically, you can see its reach and impact on the entire world."
 msgstr ""
 
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:130(para)
-msgid "<emphasis role=\"bold\">Direct Exchange:</emphasis> This is a routing table that is created during rpc.call operations; there are many instances of this kind of exchange throughout the life-cycle of a message broker node, one for each rpc.call invoked."
+#: ./doc/training-guides/module001-ch001-intro-text.xml:91(para)
+msgid "OpenStack is an open source software for building private and public clouds which delivers a massively scalable cloud operating system."
 msgstr ""
 
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:137(para)
-msgid "<emphasis role=\"bold\">Queue Element:</emphasis> A Queue is a message bucket. Messages are kept in the queue until a Consumer (either Topic or Direct Consumer) connects to the queue and fetch it. Queues can be shared or can be exclusive. Queues whose routing key is ‘topic’ are shared amongst Workers of the same personality."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:146(title) ./doc/training-guides/module001-ch008-queues-messaging.xml:181(title) ./doc/training-guides/module001-ch008-queues-messaging.xml:204(title) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:280(para) ./doc/training-guides/lab001-control-node.xml:146(emphasis)
-msgid "RabbitMQ"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:153(guilabel)
-msgid "RPC Calls"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:154(para)
-msgid "The diagram below shows the message flow during an rp.call operation:"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:158(para)
-msgid "A Topic Publisher is instantiated to send the message request to the queuing system; immediately before the publishing operation. A Direct Consumer is instantiated to wait for the response message."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:164(para)
-msgid "Once the message is dispatched by the exchange, it is fetched by the Topic Consumer dictated by the routing key (such as ‘topic.host’) and passed to the Worker in charge of the task."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:170(para)
-msgid "Once the task is completed, a Direct Publisher is allocated to send the response message to the queuing system."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:175(para)
-msgid "Once the message is dispatched by the exchange, it is fetched by the Direct Consumer dictated by the routing key (such as ‘msg_id’) and passed to the Invoker."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:188(guilabel)
-msgid "RPC Casts"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:189(para)
-msgid "The diagram below the message flow during an rp.cast operation:"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:193(para)
-msgid "A Topic Publisher is instantiated to send the message request to the queuing system."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:197(para)
-msgid "Once the message is dispatched by the exchange, it is fetched by the Topic Consumer dictated by the routing key (such as ‘topic’) and passed to the Worker in charge of the task."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:211(guilabel)
-msgid "AMQP Broker Load"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:212(para)
-msgid "At any given time the load of a message broker node running either Qpid or RabbitMQ is a function of the following parameters:"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:217(para)
-msgid "Throughput of API calls: the number of API calls (more precisely rpc.call ops) being served by the OpenStack cloud dictates the number of direct-based exchanges, related queues and direct consumers connected to them."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:223(para)
-msgid "Number of Workers: there is one queue shared amongst workers with the same personality; however there are as many exclusive queues as the number of workers; the number of workers dictates also the number of routing keys within the topic-based exchange, which is shared amongst all workers."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:231(para)
-msgid "The figure below shows the status of a RabbitMQ node after Nova components’ bootstrap in a test environment. Exchanges and queues being created by Nova components are:"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:236(para)
-msgid "Exchanges"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:241(para)
-msgid "nova (topic exchange)"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:246(para)
-msgid "Queues"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:251(para)
-msgid "compute.phantom (phantom is the hostname)"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:254(para)
-msgid "compute"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:257(para)
-msgid "network.phantom (phantom is the hostname)"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:260(para)
-msgid "network"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:263(para)
-msgid "scheduler.phantom (phantom is the hostname)"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:266(para)
-msgid "scheduler"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:269(guilabel)
-msgid "RabbitMQ Gotchas"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:270(para)
-msgid "Nova uses Kombu to connect to the RabbitMQ environment. Kombu is a Python library that in turn uses AMQPLib, a library that implements the standard AMQP 0.8 at the time of writing. When using Kombu, Invokers and Workers need the following parameters in order to instantiate a Connection object that connects to the RabbitMQ server (please note that most of the following material can be also found in the Kombu documentation; it has been summarized and revised here for the sake of clarity):"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:280(para)
-msgid "<emphasis role=\"bold\">Hostname:</emphasis> The hostname to the AMQP server."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:284(para)
-msgid "<emphasis role=\"bold\">Userid:</emphasis> A valid username used to authenticate to the server."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:288(para)
-msgid "<emphasis role=\"bold\">Password:</emphasis> The password used to authenticate to the server."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:292(para)
-msgid "<emphasis role=\"bold\">Virtual_host:</emphasis> The name of the virtual host to work with. This virtual host must exist on the server, and the user must have access to it. Default is “/”."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:298(para)
-msgid "<emphasis role=\"bold\">Port:</emphasis> The port of the AMQP server. Default is 5672 (amqp)."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:302(para)
-msgid "The following parameters are default:"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:305(para)
-msgid "<emphasis role=\"bold\">Insist:</emphasis> Insist on connecting to a server. In a configuration with multiple load-sharing servers, the Insist option tells the server that the client is insisting on a connection to the specified server. Default is False."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:312(para)
-msgid "<emphasis role=\"bold\">Connect_timeout:</emphasis> The timeout in seconds before the client gives up connecting to the server. The default is no timeout."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:317(para)
-msgid "<emphasis role=\"bold\">SSL:</emphasis> Use SSL to connect to the server. The default is False."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:321(para)
-msgid "More precisely consumers need the following parameters:"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:324(para)
-msgid "<emphasis role=\"bold\">Connection:</emphasis> The above mentioned Connection object."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:328(para)
-msgid "<emphasis role=\"bold\">Queue:</emphasis> Name of the queue."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:332(para)
-msgid "<emphasis role=\"bold\">Exchange:</emphasis> Name of the exchange the queue binds to."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:336(para)
-msgid "<emphasis role=\"bold\">Routing_key:</emphasis> The interpretation of the routing key depends on the value of the exchange_type attribute."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:343(para)
-msgid "<emphasis role=\"bold\">Direct exchange:</emphasis> If the routing key property of the message and the routing_key attribute of the queue are identical, then the message is forwarded to the queue."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:349(para)
-msgid "<emphasis role=\"bold\">Fanout exchange:</emphasis> Messages are forwarded to the queues bound the exchange, even if the binding does not have a key."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:354(para)
-msgid "<emphasis role=\"bold\">Topic exchange:</emphasis> If the routing key property of the message matches the routing key of the key according to a primitive pattern matching scheme, then the message is forwarded to the queue. The message routing key then consists of words separated by dots (”.”, like domain names), and two special characters are available; star (“”) and hash (“#”). The star matches any word, and the hash matches zero or more words. For example ”.stock.#” matches the routing keys “usd.stock” and “eur.stock.db” but not “stock.nasdaq”."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:368(para)
-msgid "<emphasis role=\"bold\">Durable:</emphasis> This flag determines the durability of both exchanges and queues; durable exchanges and queues remain active when a RabbitMQ server restarts. Non-durable exchanges/queues (transient exchanges/queues) are purged when a server restarts. It is worth noting that AMQP specifies that durable queues cannot bind to transient exchanges. Default is True."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:377(para)
-msgid "<emphasis role=\"bold\">Auto_delete:</emphasis> If set, the exchange is deleted when all queues have finished using it. Default is False."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:382(para)
-msgid "<emphasis role=\"bold\">Exclusive:</emphasis> Exclusive queues (such as non-shared) may only be consumed from by the current connection. When exclusive is on, this also implies auto_delete. Default is False."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:388(para)
-msgid "<emphasis role=\"bold\">Exchange_type:</emphasis> AMQP defines several default exchange types (routing algorithms) that covers most of the common messaging use cases."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:393(para)
-msgid "<emphasis role=\"bold\">Auto_ack:</emphasis> Acknowledgement is handled automatically once messages are received. By default auto_ack is set to False, and the receiver is required to manually handle acknowledgment."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:399(para)
-msgid "<emphasis role=\"bold\">No_ack:</emphasis> It disables acknowledgement on the server-side. This is different from auto_ack in that acknowledgement is turned off altogether. This functionality increases performance but at the cost of reliability. Messages can get lost if a client dies before it can deliver them to the application."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:407(para)
-msgid "<emphasis role=\"bold\">Auto_declare:</emphasis> If this is True and the exchange name is set, the exchange will be automatically declared at instantiation. Auto declare is on by default. Publishers specify most the parameters of consumers (they do not specify a queue name), but they can also specify the following:"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:415(para)
-msgid "<emphasis role=\"bold\">Delivery_mode:</emphasis> The default delivery mode used for messages. The value is an integer. The following delivery modes are supported by RabbitMQ:"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:422(para)
-msgid "<emphasis role=\"bold\">1 or “transient”:</emphasis> The message is transient. Which means it is stored in memory only, and is lost if the server dies or restarts."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:427(para)
-msgid "<emphasis role=\"bold\">2 or “persistent”:</emphasis> The message is persistent. Which means the message is stored both in-memory, and on disk, and therefore preserved if the server dies or restarts."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch008-queues-messaging.xml:433(para)
-msgid "The default value is 2 (persistent). During a send operation, Publishers can override the delivery mode of messages so that, for example, transient messages can be sent over a durable queue."
-msgstr ""
-
-#: ./doc/training-guides/bk001-associate-training-guide.xml:5(title)
-msgid "Associate Training Guide"
-msgstr ""
-
-#: ./doc/training-guides/training-cluster-by-script.xml:6(title)
-msgid "Build the Training Cluster, Scripted"
-msgstr ""
-
-#: ./doc/training-guides/training-cluster-by-script.xml:9(link)
-msgid "Extract the scripts locally by downloading and running the scripts tar file."
-msgstr ""
-
-#: ./doc/training-guides/training-cluster-by-script.xml:11(para)
-msgid "Currently, only <filename>*/Scripts/</filename> folders content are being tested. Run the <filename>~/Scripts/test_scripts.sh</filename> file to test all scripts at once."
-msgstr ""
-
-#: ./doc/training-guides/training-cluster-by-script.xml:16(title)
-msgid "To test scripts"
-msgstr ""
-
-#: ./doc/training-guides/training-cluster-by-script.xml:18(title)
-msgid "Set up the test environment"
-msgstr ""
-
-#: ./doc/training-guides/training-cluster-by-script.xml:19(para)
-msgid "To use Virtual Box as test environment, you must attach the following network adapters:"
-msgstr ""
-
-#: ./doc/training-guides/training-cluster-by-script.xml:23(para)
-msgid "Host-Only/ Bridged -- 10.10.10.51 (Guest) -- 10.10.10.xx (Host IP for Host-Only)"
-msgstr ""
-
-#: ./doc/training-guides/training-cluster-by-script.xml:27(para)
-msgid "Host-Only/ Bridged -- 192.168.100.51 (Guest) -- 192.168.100.xx (Host IP for Host-Only)"
-msgstr ""
-
-#: ./doc/training-guides/training-cluster-by-script.xml:31(para)
-msgid "Bridged/NAT -- DHCP -- These Scripts should be run without internet connection after Pre-Install.sh. The Templates/* should be changed to the required IP Addresses for custom networks."
-msgstr ""
-
-#: ./doc/training-guides/training-cluster-by-script.xml:39(title)
-msgid "Test scripts individually"
-msgstr ""
-
-#: ./doc/training-guides/training-cluster-by-script.xml:40(para)
-msgid "Run the shell scripts in the <filename>Scripts</filename> folder to verify they run correctly. Do not install Virtual Box, although it is recommended because your host machine might fail."
-msgstr ""
-
-#: ./doc/training-guides/training-cluster-by-script.xml:43(para)
-msgid "To test the scripts, run them. Some scripts require input parameters. If you do not want to run them manually, run the <filename>Scripts/test_scripts.sh</filename> file. Virtual Box guest add-ons are not required to test the scripts as units."
-msgstr ""
-
-#: ./doc/training-guides/training-cluster-by-script.xml:50(title)
-msgid "Test the entire system"
-msgstr ""
-
-#: ./doc/training-guides/training-cluster-by-script.xml:51(para)
-msgid "You must install Virtual Box, Ubuntu Server 12.04 or 13.04, and the Virtual Box guest add-ons."
-msgstr ""
-
-#: ./doc/training-guides/training-cluster-by-script.xml:53(para)
-msgid "To install Virtual Box guest add-ons, complete one of these steps:"
-msgstr ""
-
-#: ./doc/training-guides/training-cluster-by-script.xml:57(para)
-msgid "Install the Virtual Box guest add-ons through ISO:"
-msgstr ""
-
-#: ./doc/training-guides/training-cluster-by-script.xml:65(para)
-msgid "Install the Virtual Box guest add-ons through Ubuntu repositories:"
-msgstr ""
-
-#: ./doc/training-guides/card074-horizon-snapshots.xml:7(title)
-msgid "Creating Snapshots"
-msgstr ""
-
-#: ./doc/training-guides/card074-horizon-snapshots.xml:8(emphasis)
-msgid "Creating image snapshots using Horizon"
+#: ./doc/training-guides/module001-ch001-intro-text.xml:97(td)
+msgid "OpenStack is backed up by a global community of technologists, developers, researchers, corporations and cloud computing experts."
 msgstr ""
 
 #: ./doc/training-guides/bk003-ch013-developer-how-to-participate-day-five-quiz.xml:6(title)
@@ -2100,166 +891,155 @@ msgstr ""
 msgid "Day 5, 16:40 to 17:00"
 msgstr ""
 
-#: ./doc/training-guides/card071-create-cinder-horizon.xml:7(title)
-msgid "Creating and Deleting Volumes"
+#: ./doc/training-guides/bk003-ch006-developer-apis-day-two-quiz.xml:6(title)
+msgid "Developer APIs in Depth Day Two Quiz"
 msgstr ""
 
-#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:8(title) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:8(title)
-msgid "Controller Node"
+#: ./doc/training-guides/bk003-ch006-developer-apis-day-two-quiz.xml:8(title)
+msgid "Day 2, 16:40 to 17:00"
 msgstr ""
 
-#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:10(title)
-msgid "Day 1, 11:15 to 12:30, 13:30 to 14:45"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:14(title) ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:7(title)
-msgid "Overview Horizon and OpenStack CLI"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:21(title) ./doc/training-guides/module001-ch007-keystone-arch.xml:6(title)
-msgid "Keystone Architecture"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:35(title) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:28(title) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:35(title) ./doc/training-guides/bk001-ch007-associate-network-node.xml:28(title)
-msgid "Administration Tasks"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:37(title)
-msgid "Identity CI Commands"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:44(title)
-msgid "Identity User Management"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:51(title)
-msgid "Image CLI Commands"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:58(title)
-msgid "Image List Images"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:65(title)
-msgid "Image Adding Images"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:72(title)
-msgid "Image Manage Images"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:79(title)
-msgid "Message Queue Configuration"
+#: ./doc/training-guides/card073-control-state-instance.xml:7(title) ./doc/training-guides/card073-control-state-instance.xml:8(emphasis)
+msgid "Controlling instance state"
 msgstr ""
 
 #. When image changes, this message will be marked fuzzy or untranslated for you.
 #. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/training-guides/lab002-network-node.xml:15(None) ./doc/training-guides/lab003-compute-node.xml:18(None) ./doc/training-guides/lab001-control-node.xml:13(None) ./doc/training-guides/lab000-virtualbox-basics.xml:126(None)
-msgid "@@image: 'figures/lab000-virtual-box/image03.png'; md5=2f79252a8c2f058f103df5346c9cd6fb"
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:213(None)
+msgid "@@image: 'figures/image02.png'; md5=9568a4bc836fe6a413f5ea2a5297d475"
 msgstr ""
 
-#: ./doc/training-guides/lab002-network-node.xml:7(emphasis) ./doc/training-guides/lab003-compute-node.xml:10(emphasis) ./doc/training-guides/lab001-control-node.xml:7(emphasis)
-msgid "Network Diagram :"
+#. <para>More content to be added...</para>
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:11(para)
+msgid "The request flow for provisioning an instance goes like this:"
 msgstr ""
 
-#: ./doc/training-guides/lab002-network-node.xml:19(para) ./doc/training-guides/lab003-compute-node.xml:22(para) ./doc/training-guides/lab001-control-node.xml:17(para)
-msgid "Publicly editable image source at <link href=\"https://docs.google.com/drawings/d/1GX3FXmkz3c_tUDpZXUVMpyIxicWuHs5fNsHvYNjwNNk/edit?usp=sharing\">https://docs.google.com/drawings/d/1GX3FXmkz3c_tUDpZXUVMpyIxicWuHs5fNsHvYNjwNNk/edit?usp=sharing</link>"
+#. 1
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:21(para)
+msgid "The dashboard or CLI gets the user credentials and authenticates with the Identity Service via REST API."
 msgstr ""
 
-#: ./doc/training-guides/lab002-network-node.xml:22(para) ./doc/training-guides/lab003-compute-node.xml:25(para)
-msgid "<emphasis role=\"bold\">Vboxnet0</emphasis>, <emphasis role=\"bold\">Vboxnet1</emphasis>, <emphasis role=\"bold\">Vboxnet2</emphasis> - are virtual networks setup up by virtual box with your host machine. This is the way your host can communicate with the virtual machines. These networks are in turn used by virtual box VM’s for OpenStack networks, so that OpenStack’s services can communicate with each other."
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:24(para)
+msgid "The Identity Service authenticates the user with the user credentials, and then generates and sends back an auth-token which will be used for sending the request to other components through REST-call."
 msgstr ""
 
-#: ./doc/training-guides/lab002-network-node.xml:28(para)
-msgid "Start your Controller Node the one you setup in previous section."
+#. 2
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:33(para)
+msgid "The dashboard or CLI converts the new instance request specified in <guilabel>launch instance</guilabel> or <placeholder-1/> form to a REST API request and sends it to <systemitem class=\"service\">nova-api</systemitem>."
 msgstr ""
 
-#: ./doc/training-guides/lab002-network-node.xml:29(emphasis) ./doc/training-guides/lab003-compute-node.xml:35(emphasis)
-msgid "Preparing Ubuntu 12.04"
+#. 3
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:42(para)
+msgid "<systemitem class=\"service\">nova-api</systemitem> receives the request and sends a request to the Identity Service for validation of the auth-token and access permission."
 msgstr ""
 
-#: ./doc/training-guides/lab002-network-node.xml:32(para) ./doc/training-guides/lab003-compute-node.xml:38(para) ./doc/training-guides/lab001-control-node.xml:53(para)
-msgid "After you install Ubuntu Server, go in sudo mode"
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:47(para)
+msgid "The Identity Service validates the token and sends updated authentication headers with roles and permissions."
 msgstr ""
 
-#: ./doc/training-guides/lab002-network-node.xml:38(para) ./doc/training-guides/lab003-compute-node.xml:44(para) ./doc/training-guides/lab001-control-node.xml:57(para)
-msgid "Add Icehouse repositories:"
+#. 4
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:54(para)
+msgid "<systemitem class=\"service\">nova-api</systemitem> checks for conflicts with <systemitem class=\"service\">nova-database</systemitem>."
 msgstr ""
 
-#: ./doc/training-guides/lab002-network-node.xml:45(para) ./doc/training-guides/lab002-network-node.xml:227(para) ./doc/training-guides/lab003-compute-node.xml:51(para) ./doc/training-guides/lab001-control-node.xml:62(para)
-msgid "Update your system:"
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:59(para)
+msgid "<systemitem class=\"service\">nova-api</systemitem> creates initial database entry for a new instance."
 msgstr ""
 
-#: ./doc/training-guides/lab002-network-node.xml:53(para) ./doc/training-guides/lab003-compute-node.xml:59(para)
-msgid "Install NTP and other services:"
+#. 5
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:66(para)
+msgid "<systemitem class=\"service\">nova-api</systemitem> sends the rpc.call request to <systemitem class=\"service\">nova-scheduler</systemitem> expecting to get updated instance entry with host ID specified."
 msgstr ""
 
-#: ./doc/training-guides/lab002-network-node.xml:59(para) ./doc/training-guides/lab003-compute-node.xml:65(para)
-msgid "Configure NTP Server to Controller Node:"
+#. 6
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:75(para)
+msgid "<systemitem class=\"service\">nova-scheduler</systemitem> picks up the request from the queue."
 msgstr ""
 
-#: ./doc/training-guides/lab002-network-node.xml:68(para)
-msgid "Enable IP Forwarding by adding the following to <filename>/etc/sysctl.conf</filename>:"
+#. 7
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:82(para)
+msgid "<systemitem class=\"service\">nova-scheduler</systemitem> interacts with <systemitem class=\"service\">nova-database</systemitem> to find an appropriate host via filtering and weighing."
 msgstr ""
 
-#: ./doc/training-guides/lab002-network-node.xml:76(para) ./doc/training-guides/lab003-compute-node.xml:82(para)
-msgid "Run the following commands:"
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:88(para)
+msgid "<systemitem class=\"service\">nova-scheduler</systemitem> returns the updated instance entry with the appropriate host ID after filtering and weighing."
 msgstr ""
 
-#: ./doc/training-guides/lab002-network-node.xml:85(emphasis)
-msgid "Open vSwitch"
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:93(para)
+msgid "<systemitem class=\"service\">nova-scheduler</systemitem> sends the rpc.cast request to <systemitem class=\"service\">nova-compute</systemitem> for launching an instance on the appropriate host."
 msgstr ""
 
-#: ./doc/training-guides/lab002-network-node.xml:88(para)
-msgid "Install Open vSwitch Packages:"
+#. 8
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:102(para)
+msgid "<systemitem class=\"service\">nova-compute</systemitem> picks up the request from the queue."
 msgstr ""
 
-#: ./doc/training-guides/lab002-network-node.xml:94(para)
-msgid "Create the bridges:"
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:108(para)
+msgid "<systemitem class=\"service\">nova-compute</systemitem> sends the rpc.call request to <systemitem class=\"service\">nova-conductor</systemitem> to fetch the instance information such as host ID and flavor (RAM, CPU, Disk)."
 msgstr ""
 
-#: ./doc/training-guides/lab002-network-node.xml:101(emphasis) ./doc/training-guides/lab003-compute-node.xml:150(para) ./doc/training-guides/lab001-control-node.xml:367(emphasis)
-msgid "Neutron"
+#. 10
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:119(para)
+msgid "<systemitem class=\"service\">nova-conductor</systemitem> picks up the request from the queue."
 msgstr ""
 
-#: ./doc/training-guides/lab002-network-node.xml:104(para)
-msgid "Neutron:"
+#. 11
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:126(para)
+msgid "<systemitem class=\"service\">nova-conductor</systemitem> interacts with <systemitem class=\"service\">nova-database</systemitem>."
 msgstr ""
 
-#: ./doc/training-guides/lab002-network-node.xml:110(para)
-msgid "Edit <filename>/etc/neutron/api-paste.ini</filename>:"
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:131(para)
+msgid "<systemitem class=\"service\">nova-conductor</systemitem> returns the instance information."
 msgstr ""
 
-#: ./doc/training-guides/lab002-network-node.xml:123(para)
-msgid "Edit <filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename>:"
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:135(para)
+msgid "<systemitem class=\"service\">nova-compute</systemitem> picks up the instance information from the queue."
 msgstr ""
 
-#: ./doc/training-guides/lab002-network-node.xml:147(para)
-msgid "Edit <filename>/etc/neutron/metadata_agent.ini</filename>:"
+#. 12
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:142(para)
+msgid "<systemitem class=\"service\">nova-compute</systemitem> performs the REST call by passing the auth-token to <systemitem class=\"service\">glance-api</systemitem>. Then, <systemitem class=\"service\">nova-compute</systemitem> uses the Image ID to retrieve the Image URI from the Image Service, and loads the image from the image storage."
 msgstr ""
 
-#: ./doc/training-guides/lab002-network-node.xml:163(para)
-msgid "Edit <filename>/etc/neutron/dhcp_agent.ini</filename>:"
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:152(para)
+msgid "<systemitem class=\"service\">glance-api</systemitem> validates the auth-token with keystone."
 msgstr ""
 
-#: ./doc/training-guides/lab002-network-node.xml:169(para)
-msgid "Edit <filename>/etc/neutron/l3_agent.ini</filename>:"
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:157(para)
+msgid "<systemitem class=\"service\">nova-compute</systemitem> gets the image metadata."
 msgstr ""
 
-#: ./doc/training-guides/lab002-network-node.xml:177(para)
-msgid "Edit <filename>/etc/neutron/neutron.conf</filename>:"
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:163(para)
+msgid "<systemitem class=\"service\">nova-compute</systemitem> performs the REST-call by passing the auth-token to Network API to allocate and configure the network so that the instance gets the IP address."
 msgstr ""
 
-#: ./doc/training-guides/lab002-network-node.xml:194(para)
-msgid "Edit <filename>/etc/sudoers.d/neutron_sudoers:</filename>:"
+#. 15
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:173(para)
+msgid "<systemitem class=\"service\">neutron-server</systemitem> validates the auth-token with keystone."
 msgstr ""
 
-#: ./doc/training-guides/lab002-network-node.xml:201(para)
-msgid "Restart Services:"
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:177(para)
+msgid "<systemitem class=\"service\">nova-compute</systemitem> retrieves the network info."
 msgstr ""
 
-#: ./doc/training-guides/lab002-network-node.xml:209(para)
-msgid "Edit Network Interfaces file <filename>/etc/network/interfaces</filename>:"
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:183(para)
+msgid "<systemitem class=\"service\">nova-compute</systemitem> performs the REST call by passing the auth-token to Volume API to attach volumes to the instance."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:191(para)
+msgid "<systemitem class=\"service\">cinder-api</systemitem> validates the auth-token with keystone."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:196(para)
+msgid "<systemitem class=\"service\">nova-compute</systemitem> retrieves the block storage info."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:202(para)
+msgid "<systemitem class=\"service\">nova-compute</systemitem> generates data for the hypervisor driver and executes the request on the hypervisor (via libvirt or API)."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:210(title)
+msgid "Nova VM provisioning"
 msgstr ""
 
 #. When image changes, this message will be marked fuzzy or untranslated for you.
@@ -2678,6 +1458,26 @@ msgstr ""
 msgid "A few points on OpenStack Block Storage:"
 msgstr ""
 
+#: ./doc/training-guides/module001-ch003-core-projects.xml:374(para) ./doc/training-guides/module001-ch011-block-storage.xml:220(para)
+msgid "OpenStack provides persistent block level storage devices for use with OpenStack compute instances."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch003-core-projects.xml:378(para) ./doc/training-guides/module001-ch011-block-storage.xml:224(para)
+msgid "The block storage system manages the creation, attaching and detaching of the block devices to servers. Block storage volumes are fully integrated into OpenStack Compute and the Dashboard allowing for cloud users to manage their own storage needs."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch003-core-projects.xml:385(para) ./doc/training-guides/module001-ch011-block-storage.xml:231(para)
+msgid "In addition to using simple Linux server storage, it has unified storage support for numerous storage platforms including Ceph, NetApp, Nexenta, SolidFire, and Zadara."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch003-core-projects.xml:391(para) ./doc/training-guides/module001-ch011-block-storage.xml:237(para)
+msgid "Block storage is appropriate for performance sensitive scenarios such as database storage, expandable file systems, or providing a server with access to raw block level storage."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch003-core-projects.xml:397(para) ./doc/training-guides/module001-ch011-block-storage.xml:243(para)
+msgid "Snapshot management provides powerful functionality for backing up data stored on block storage volumes. Snapshots can be restored or used to create a new block storage volume."
+msgstr ""
+
 #: ./doc/training-guides/module001-ch003-core-projects.xml:403(guisubmenu)
 msgid "Networking(Neutron)"
 msgstr ""
@@ -2866,44 +1666,526 @@ msgstr ""
 msgid "The foundation's stated mission is by providing shared resources to help achieve the OpenStack Mission by Protecting, Empowering, and Promoting OpenStack software and the community around it, including users, developers and the entire ecosystem. Though, it has little to do with the development of the software, which is managed by the technical committee - an elected group that represents the contributors to the project, and has oversight on all technical matters."
 msgstr ""
 
-#: ./doc/training-guides/card009.xml:6(title)
-msgid "Install Ubuntu"
+#: ./doc/training-guides/card040-cinder.xml:7(title)
+msgid "Install Cinder"
 msgstr ""
 
-#: ./doc/training-guides/card043-ovs-in-network-node.xml:7(title)
-msgid "OVS Installation and Configuration in Network node"
+#: ./doc/training-guides/bk001-ch007-associate-network-node.xml:8(title) ./doc/training-guides/bk002-ch010-operator-network-node.xml:8(title) ./doc/training-guides/lab000-important-terms.xml:40(title) ./doc/training-guides/lab002-network-node.xml:4(title) ./doc/training-guides/lab002-network-node.xml:27(guilabel)
+msgid "Network Node"
 msgstr ""
 
-#: ./doc/training-guides/bk002-ch010-operator-network-node.xml:10(title)
-msgid "Days 7 to 8, 09:00 to 11:00, 11:15 to 12:30"
+#: ./doc/training-guides/bk001-ch007-associate-network-node.xml:10(title)
+msgid "Day 2, 09:00 to 11:00"
 msgstr ""
 
-#: ./doc/training-guides/bk002-ch010-operator-network-node.xml:14(title)
-msgid "Review Associate Networking in OpenStack"
+#: ./doc/training-guides/bk001-ch007-associate-network-node.xml:14(title) ./doc/training-guides/module002-ch001-networking-in-openstack.xml:7(title) ./doc/training-guides/module002-ch001-networking-in-openstack.xml:8(guilabel)
+msgid "Networking in OpenStack"
 msgstr ""
 
-#: ./doc/training-guides/bk002-ch010-operator-network-node.xml:21(title)
-msgid "Review Associate OpenStack Networking Concepts"
+#: ./doc/training-guides/bk001-ch007-associate-network-node.xml:21(title) ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:7(title)
+msgid "OpenStack Networking Concepts"
 msgstr ""
 
-#: ./doc/training-guides/bk002-ch010-operator-network-node.xml:28(title) ./doc/training-guides/bk002-ch004-operator-controller-node.xml:35(title) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:35(title) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:22(title)
+#: ./doc/training-guides/bk001-ch007-associate-network-node.xml:30(title)
+msgid "Network CLI Commands"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch007-associate-network-node.xml:37(title)
+msgid "Manage Networks"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/training-guides/lab001-control-node.xml:13(None) ./doc/training-guides/lab000-virtualbox-basics.xml:126(None) ./doc/training-guides/lab003-compute-node.xml:18(None) ./doc/training-guides/lab002-network-node.xml:15(None)
+msgid "@@image: 'figures/lab000-virtual-box/image03.png'; md5=2f79252a8c2f058f103df5346c9cd6fb"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:6(title) ./doc/training-guides/lab000-important-terms.xml:28(title)
+msgid "Control Node"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:7(emphasis) ./doc/training-guides/lab003-compute-node.xml:10(emphasis) ./doc/training-guides/lab002-network-node.xml:7(emphasis)
+msgid "Network Diagram :"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:9(title) ./doc/training-guides/lab003-compute-node.xml:14(title) ./doc/training-guides/lab002-network-node.xml:11(title) ./doc/training-guides/module002-ch001-networking-in-openstack.xml:228(title)
+msgid "Network Diagram"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:17(para) ./doc/training-guides/lab003-compute-node.xml:22(para) ./doc/training-guides/lab002-network-node.xml:19(para)
+msgid "Publicly editable image source at <link href=\"https://docs.google.com/drawings/d/1GX3FXmkz3c_tUDpZXUVMpyIxicWuHs5fNsHvYNjwNNk/edit?usp=sharing\">https://docs.google.com/drawings/d/1GX3FXmkz3c_tUDpZXUVMpyIxicWuHs5fNsHvYNjwNNk/edit?usp=sharing</link>"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:20(para)
+msgid "<emphasis role=\"bold\">Vboxnet0</emphasis>, <emphasis role=\"bold\">Vboxnet1</emphasis>, <emphasis role=\"bold\">Vboxnet2</emphasis> - are virtual networks setup up by virtual box with your host machine. This is the way your host can communicate with the virtual machines. These networks are in turn used by VirtualBox virtual machines for OpenStack networks, so that OpenStack’s services can communicate with each other."
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:28(para)
+msgid "When you reboot the controller node on the VirtualBox virtual machine, you might lose Internet and network connectivity. Restart the networking service and use the <placeholder-1/> command to check whether the network interfaces can communicate over the given networks."
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:35(para)
+msgid "To avoid issues on the VirtualBox virtual machine (controller node), <emphasis role=\"bold\">save the virtual machine</emphasis> state instead of completing a reboot or shut down."
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:41(para)
+msgid "It is advised to take regular snapshots of the Virtual Box Virtual Machines (controller node) after each section. This will help you to save your session and revert back to it in case you break something while deploying OpenStack."
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:46(guilabel)
+msgid "controller node"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:47(para)
+msgid "Start your controller node the one you setup in previous section."
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:49(emphasis)
+msgid "Preparing Ubuntu 13.04/12.04"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:53(para) ./doc/training-guides/lab003-compute-node.xml:38(para) ./doc/training-guides/lab002-network-node.xml:32(para)
+msgid "After you install Ubuntu Server, go in sudo mode"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:57(para) ./doc/training-guides/lab003-compute-node.xml:44(para) ./doc/training-guides/lab002-network-node.xml:38(para)
+msgid "Add Icehouse repositories:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:62(para) ./doc/training-guides/lab003-compute-node.xml:51(para) ./doc/training-guides/lab002-network-node.xml:45(para) ./doc/training-guides/lab002-network-node.xml:227(para)
+msgid "Update your system:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:68(emphasis)
+msgid "Networking :"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:69(para)
+msgid "Configure your network by editing <filename>/etc/network/interfaces</filename> file"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:73(para)
+msgid "Open <filename>/etc/network/interfaces</filename> and edit file as mentioned:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:107(para)
+msgid "After saving the interfaces file, restart the networking service:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:113(para)
+msgid "You should see the expected network interface cards having the required IP Addresses."
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:117(emphasis)
+msgid "SSH from HOST"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:120(para)
+msgid "Create an SSH key pair for your Control Node. Follow the same steps as you did in the starting section of the article for your host machine."
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:125(para)
+msgid "To SSH into the Control Node from the Host Machine type the below command."
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:131(para)
+msgid "Now you can have access to your host clipboard."
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:134(emphasis)
+msgid "My SQL"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:137(para)
+msgid "Install MySQL:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:141(para)
+msgid "Configure mysql to accept all incoming requests:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:146(emphasis) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:280(para) ./doc/training-guides/module001-ch008-queues-messaging.xml:146(title) ./doc/training-guides/module001-ch008-queues-messaging.xml:181(title) ./doc/training-guides/module001-ch008-queues-messaging.xml:204(title)
+msgid "RabbitMQ"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:149(para)
+msgid "Install RabbitMQ:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:153(para)
+msgid "Install NTP service:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:157(para)
+msgid "Create these databases:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:172(emphasis)
+msgid "Other"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:175(para)
+msgid "Install other services:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:179(para)
+msgid "Enable IP_Forwarding:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:183(para)
+msgid "Also add the following two lines into<filename>/etc/sysctl.conf</filename>:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:189(para)
+msgid "To save you from reboot, perform the following"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:196(emphasis)
+msgid "Keystone"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:197(para)
+msgid "Keystone is an OpenStack project that provides Identity, Token, Catalog and Policy services for use specifically by projects in the OpenStack family. It implements OpenStack’s Identity API."
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:203(para)
+msgid "Install Keystone packages:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:207(para)
+msgid "Adapt the connection attribute in the <filename>/etc/keystone/keystone.conf</filename> to the new database:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:213(para)
+msgid "Restart the identity service then synchronize the database:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:219(para)
+msgid "Fill up the keystone database using the following scripts:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:224(filename)
+msgid "keystone_basic.sh"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:229(filename)
+msgid "keystone_endpoints_basic.sh"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:233(para)
+msgid "Run scripts:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:240(para)
+msgid "Create a simple credentials file"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:244(para)
+msgid "Paste the following:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:251(para)
+msgid "Load the above credentials:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:255(para)
+msgid "To test Keystone, we use a simple CLI command:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:259(emphasis)
+msgid "Glance"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:260(para)
+msgid "The OpenStack Glance project provides services for discovering, registering, and retrieving virtual machine images. Glance has a RESTful API that allows querying of VM image metadata as well as retrieval of the actual image."
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:264(para)
+msgid "VM images made available through Glance can be stored in a variety of locations from simple file systems to object-storage systems like the OpenStack Swift project."
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:267(para)
+msgid "Glance, as with all OpenStack projects, is written with the following design guidelines in mind:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:271(para)
+msgid "Component based architecture: Quickly adds new behaviors"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:275(para)
+msgid "Highly available: Scales to very serious workloads"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:278(para)
+msgid "Fault tolerant: Isolated processes avoid cascading failures"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:282(para)
+msgid "Recoverable: Failures should be easy to diagnose, debug, and rectify"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:286(para)
+msgid "Open standards: Be a reference implementation for a community-driven api"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:290(para)
+msgid "Install Glance:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:294(para)
+msgid "Update <filename>/etc/glance/glance-api-paste.ini</filename>:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:307(para)
+msgid "Update the <filename>/etc/glance/glance-registry-paste.ini</filename>:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:319(para)
+msgid "Update the <filename>/etc/glance/glance-api.conf</filename>:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:334(para)
+msgid "Update the <filename>/etc/glance/glance-registry.conf</filename>:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:349(para)
+msgid "Restart the glance-api and glance-registry services:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:354(para)
+msgid "Synchronize the Glance database:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:358(para)
+msgid "To test Glance, upload the “cirros cloud image” directly from the internet:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:363(para)
+msgid "Check if the image is successfully uploaded:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:367(emphasis) ./doc/training-guides/lab003-compute-node.xml:150(para) ./doc/training-guides/lab002-network-node.xml:101(emphasis)
+msgid "Neutron"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:368(para)
+msgid "Neutron is an OpenStack project to provide “network connectivity as a service\" between interface devices (e.g., vNICs) managed by other OpenStack services (e.g., nova)."
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:373(para)
+msgid "Install the Neutron Server and the Open vSwitch package collection:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:378(para)
+msgid "Edit the <filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename>:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:397(para)
+msgid "Edit the <filename>/etc/neutron/api-paste.ini</filename>:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:411(para)
+msgid "Edit the <filename>/etc/neutron/neutron.conf</filename>:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:427(para)
+msgid "Restart Neutron services:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:431(emphasis) ./doc/training-guides/lab003-compute-node.xml:199(emphasis) ./doc/training-guides/module001-ch009-vm-placement.xml:16(title)
+msgid "Nova"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:432(para)
+msgid "Nova is the project name for OpenStack Compute, a cloud computing fabric controller, the main part of an IaaS system. Individuals and organizations can use Nova to host and manage their own cloud computing systems. Nova originated as a project out of NASA Ames Research Laboratory."
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:437(para)
+msgid "Nova is written with the following design guidelines in mind:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:441(para)
+msgid "Component based architecture: Quickly adds new behaviors."
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:445(para) ./doc/training-guides/lab001-control-node.xml:564(para)
+msgid "Highly available: Scales to very serious workloads."
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:448(para) ./doc/training-guides/lab001-control-node.xml:567(para)
+msgid "Fault-Tolerant: Isolated processes avoid cascading failures."
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:452(para)
+msgid "Recoverable: Failures should be easy to diagnose, debug, and rectify."
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:456(para)
+msgid "Open standards: Be a reference implementation for a community-driven api."
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:460(para)
+msgid "API compatibility: Nova strives to be API-compatible with popular systems like Amazon EC2."
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:464(para)
+msgid "Install nova components:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:468(para) ./doc/training-guides/lab003-compute-node.xml:209(para)
+msgid "Edit <filename>/etc/nova/api-paste.ini</filename>"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:483(para) ./doc/training-guides/lab003-compute-node.xml:232(para)
+msgid "Edit <filename>/etc/nova/nova.conf</filename>"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:541(para)
+msgid "Synchronize your database:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:545(para)
+msgid "Restart nova-* services (all nova services):"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:549(para)
+msgid "Check for the smiling faces on <systemitem class=\"service\">nova-*</systemitem> services to confirm your installation:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:555(emphasis)
+msgid "Cinder"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:556(para)
+msgid "Cinder is an OpenStack project to provide “block storage as a service”."
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:560(para)
+msgid "Component based architecture: Quickly adds new behavior."
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:571(para)
+msgid "Recoverable: Failures should be easy to diagnose, debug and rectify."
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:575(para)
+msgid "Open standards: Be a reference implementation for a community-driven API."
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:579(para)
+msgid "API compatibility: Cinder strives to be API-compatible with popular systems like Amazon EC2."
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:583(para)
+msgid "Install Cinder components:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:587(para)
+msgid "Configure the iSCSI services:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:591(para)
+msgid "Restart the services:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:596(para)
+msgid "Edit <filename>/etc/cinder/api-paste.ini</filename>:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:612(para)
+msgid "Edit <filename>/etc/cinder/cinder.conf</filename>:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:628(para)
+msgid "Then, synchronize Cinder database:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:632(para)
+msgid "Finally, create a volume group and name it <literal>cinder-volumes</literal>:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:645(para)
+msgid "Proceed to create the physical volume then the volume group:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:652(para)
+msgid "Be aware that this volume group gets lost after a system reboot. If you do not want to perform this step again, make sure that you save the machine state and do not shut it down."
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:659(para)
+msgid "Restart the Cinder services:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:663(para)
+msgid "Verify if Cinder services are running:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:667(emphasis)
+msgid "Horizon"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:668(para)
+msgid "Horizon is the canonical implementation of OpenStack’s dashboard, which provides a web-based user interface to OpenStack services including Nova, Swift, Keystone, etc."
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:673(para)
+msgid "To install Horizon, complete these steps:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:677(para)
+msgid "If you do not like the OpenStack Ubuntu Theme, you can remove it with the below command:"
+msgstr ""
+
+#: ./doc/training-guides/lab001-control-node.xml:682(para)
+msgid "Reload Apache and memcached:"
+msgstr ""
+
+#: ./doc/training-guides/card039-nova.xml:7(title) ./doc/training-guides/lab003-compute-node.xml:202(para)
+msgid "Install Nova"
+msgstr ""
+
+#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml:8(title) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:8(title)
+msgid "Controller Node"
+msgstr ""
+
+#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml:10(title) ./doc/training-guides/bk003-ch004-developer-apis-in-depth.xml:10(title)
+msgid "Day 2 to 4, 09:00 to 11:00, 11:15 to 12:30"
+msgstr ""
+
+#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml:14(title)
+msgid "Review Associate Overview Horizon and OpenStack CLI"
+msgstr ""
+
+#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml:21(title)
+msgid "Review Associate Keystone Architecture"
+msgstr ""
+
+#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml:28(title)
+msgid "Review Associate OpenStack Messaging and Queues"
+msgstr ""
+
+#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml:35(title) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:22(title) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:35(title) ./doc/training-guides/bk002-ch010-operator-network-node.xml:28(title)
 msgid "Review Associate Administration Tasks"
 msgstr ""
 
-#: ./doc/training-guides/bk002-ch010-operator-network-node.xml:29(para) ./doc/training-guides/bk004-architect-training-guide.xml:8(para) ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:51(para) ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:72(para)
-msgid "TBD"
+#: ./doc/training-guides/card044-install-and-configure-neutron-network-node.xml:7(title)
+msgid "Neutron Installation and Configuration in Network node"
 msgstr ""
 
-#: ./doc/training-guides/bk002-ch010-operator-network-node.xml:32(title)
-msgid "Operator OpenStack Neutron Use Cases"
+#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:8(title) ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:8(title)
+msgid "Object Storage Node"
 msgstr ""
 
-#: ./doc/training-guides/bk002-ch010-operator-network-node.xml:39(title)
-msgid "Operator OpenStack Neutron Security"
+#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:10(title)
+msgid "Day 9, 09:00 to 11:00, 11:15 to 12:30"
 msgstr ""
 
-#: ./doc/training-guides/bk002-ch010-operator-network-node.xml:46(title)
-msgid "Operator OpenStack Neutron Floating IPs"
+#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:14(title)
+msgid "Review Associate Introduction to Object Storage"
+msgstr ""
+
+#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:29(title)
+msgid "More Swift Concepts"
 msgstr ""
 
 #. When image changes, this message will be marked fuzzy or untranslated for you.
@@ -2936,6 +2218,10 @@ msgstr ""
 msgid "@@image: 'figures/image30.png'; md5=d9eef0f7a1f99eee18a99e677c7c710b"
 msgstr ""
 
+#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:7(title) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:14(title)
+msgid "Overview Horizon and OpenStack CLI"
+msgstr ""
+
 #: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:8(guilabel)
 msgid "How can I use an OpenStack cloud?"
 msgstr ""
@@ -3064,6 +2350,10 @@ msgstr ""
 msgid "From here, you can stop, pause, or reboot any instances or connect to them through virtual network computing (VNC)."
 msgstr ""
 
+#: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:127(emphasis) ./doc/training-guides/module001-ch011-block-storage.xml:164(guilabel)
+msgid "Volumes"
+msgstr ""
+
 #: ./doc/training-guides/module001-ch006-overview-horizon-cli.xml:128(para)
 msgid "Lists volumes created by users of the project."
 msgstr ""
@@ -5488,530 +4778,6 @@ msgstr ""
 msgid "Some resources are updated in-place, while others are replaced with new resources."
 msgstr ""
 
-#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:8(title) ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:8(title)
-msgid "Object Storage Node"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:10(title)
-msgid "Day 2, 11:30 to 12:30, 13:30 to 14:45"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:14(title)
-msgid "Introduction to Object Storage"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:21(title)
-msgid "Features and Benefits"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:30(title)
-msgid "Object Storage CLI Commands"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:37(title)
-msgid "Manage Object Storage"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:38(para)
-msgid "Will be included from the swift developer reference"
-msgstr ""
-
-#: ./doc/training-guides/card072-cinder-attach-volume.xml:7(title)
-msgid "Attaching volumes to an instance"
-msgstr ""
-
-#: ./doc/training-guides/card126-horizon.xml:7(title)
-msgid "Install Horizon"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:27(None)
-msgid "@@image: 'figures/image13.jpg'; md5=94fd9b9a3b33574d85bec7e1ea1675e2"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:71(None)
-msgid "@@image: 'figures/openstack-arch-havana-logical-v1.jpg'; md5=e7acaaee72722626b045eda3fae81841"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:102(None)
-msgid "@@image: 'figures/image10.jpg'; md5=9471047adf0d93713be7f54b9db2b53c"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:7(title) ./doc/training-guides/bk001-ch001-associate-getting-started.xml:45(title)
-msgid "OpenStack Architecture"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:8(guilabel)
-msgid "Conceptual Architecture"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:9(para)
-msgid "The OpenStack project as a whole is designed to deliver a massively scalable cloud operating system. To achieve this, each of the constituent services are designed to work together to provide a complete Infrastructure-as-a-Service (IaaS). This integration is facilitated through public application programming interfaces (APIs) that each service offers (and in turn can consume). While these APIs allow each of the services to use another service, it also allows an implementer to switch out any service as long as they maintain the API. These are (mostly) the same APIs that are available to end users of the cloud."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:20(para)
-msgid "Conceptually, you can picture the relationships between the services as so:"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:23(title)
-msgid "Conceptual Diagram"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:33(para)
-msgid "Dashboard (\"Horizon\") provides a web front end to the other OpenStack services"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:37(para)
-msgid "Compute (\"Nova\") stores and retrieves virtual disks (\"images\") and associated metadata in Image (\"Glance\")"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:42(para)
-msgid "Network (\"Neutron\") provides virtual networking for Compute."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:46(para)
-msgid "Block Storage (\"Cinder\") provides storage volumes for Compute."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:50(para)
-msgid "Image (\"Glance\") can store the actual virtual disk files in the Object Store(\"Swift\")"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:54(para)
-msgid "All the services authenticate with Identity (\"Keystone\")"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:58(para)
-msgid "The conceptual diagram is a stylized and simplified view of the architecture. It assumes that the implementer uses all services in the most common configuration. It also shows only the operator side of the cloud; it does not show how consumers might use the cloud. For example, many users directly and heavily access object storage."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:63(guilabel)
-msgid "Logical Architecture"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:64(para)
-msgid "The following diagram is consistent with the conceptual architecture as previously described:"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:67(title)
-msgid "Logical diagram"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:77(para)
-msgid "End users can interact through a common web interface (Horizon) or directly to each service through their API"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:82(para)
-msgid "All services authenticate through a common source (facilitated through keystone)"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:86(para)
-msgid "Individual services interact with each other through their public APIs (except where privileged administrator commands are necessary)"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:91(para)
-msgid "In the sections below, we'll delve into the architecture for each of the services."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:93(guilabel)
-msgid "Dashboard"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:94(para)
-msgid "Horizon is a modular Django web application that provides an end user and administrator interface to OpenStack services."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:98(title)
-msgid "Horizon Dashboard"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:106(para)
-msgid "As with most web applications, the architecture is fairly simple:"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:110(para)
-msgid "Horizon is usually deployed via mod_wsgi in Apache. The code itself is separated into a reusable python module with most of the logic (interactions with various OpenStack APIs) and presentation (to make it easily customizable for different sites)."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:117(para)
-msgid "A database (configurable as to which one) which relies mostly on the other services for data. It also stores very little data of its own."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:122(para)
-msgid "From a network architecture point of view, this service will need to be customer accessible as well as be able to talk to each service's public APIs. If you wish to use the administrator functionality (i.e. for other services), it will also need connectivity to their Admin API endpoints (which should be non-customer accessible)."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:128(guilabel)
-msgid "Compute"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:129(para)
-msgid "Nova is the most complicated and distributed component of OpenStack. A large number of processes cooperate to turn end user API requests into running virtual machines. Below is a list of these processes and their functions:"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:135(para)
-msgid "nova-api accepts and responds to end user compute API calls. It supports OpenStack Compute API, Amazon's EC2 API and a special Admin API (for privileged users to perform administrative actions). It also initiates most of the orchestration activities (such as running an instance) as well as enforces some policy (mostly quota checks)."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:143(para)
-msgid "The nova-compute process is primarily a worker daemon that creates and terminates virtual machine instances via hypervisor's APIs (XenAPI for XenServer/XCP, libvirt for KVM or QEMU, VMwareAPI for VMware, etc.). The process by which it does so is fairly complex but the basics are simple: accept actions from the queue and then perform a series of system commands (like launching a KVM instance) to carry them out while updating state in the database."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:154(para)
-msgid "nova-volume manages the creation, attaching and detaching of z volumes to compute instances (similar functionality to Amazon’s Elastic Block Storage). It can use volumes from a variety of providers such as iSCSI or Rados Block Device in Ceph. A new OpenStack project, Cinder, will eventually replace nova-volume functionality. In the Folsom release, nova-volume and the Block Storage service will have similar functionality."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:164(para)
-msgid "The nova-network worker daemon is very similar to nova-compute and nova-volume. It accepts networking tasks from the queue and then performs tasks to manipulate the network (such as setting up bridging interfaces or changing iptables rules). This functionality is being migrated to Neutron, a separate OpenStack project. In the Folsom release, much of the functionality will be duplicated between nova-network and Neutron."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:174(para)
-msgid "The nova-schedule process is conceptually the simplest piece of code in OpenStack Nova: it takes a virtual machine instance request from the queue and determines where it should run (specifically, which compute server host it should run on)."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:181(para)
-msgid "The queue provides a central hub for passing messages between daemons. This is usually implemented with RabbitMQ today, but could be any AMQP message queue (such as Apache Qpid). New to the Folsom release is support for Zero MQ."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:188(para)
-msgid "The SQL database stores most of the build-time and runtime state for a cloud infrastructure. This includes the instance types that are available for use, instances in use, networks available and projects. Theoretically, OpenStack Nova can support any database supported by SQL-Alchemy but the only databases currently being widely used are SQLite3 (only appropriate for test and development work), MySQL and PostgreSQL."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:198(para)
-msgid "Nova also provides console services to allow end users to access their virtual instance's console through a proxy. This involves several daemons (nova-console, nova-novncproxy and nova-consoleauth)."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:204(para)
-msgid "Nova interacts with many other OpenStack services: Keystone for authentication, Glance for images and Horizon for web interface. The Glance interactions are central. The API process can upload and query Glance while nova-compute will download images for use in launching images."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:209(guilabel)
-msgid "Object Store"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:210(para)
-msgid "The swift architecture is very distributed to prevent any single point of failure as well as to scale horizontally. It includes the following components:"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:215(para)
-msgid "Proxy server (swift-proxy-server) accepts incoming requests via the OpenStack Object API or just raw HTTP. It accepts files to upload, modifications to metadata or container creation. In addition, it will also serve files or container listing to web browsers. The proxy server may utilize an optional cache (usually deployed with memcache) to improve performance."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:224(para)
-msgid "Account servers manage accounts defined with the object storage service."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:228(para)
-msgid "Container servers manage a mapping of containers (i.e folders) within the object store service."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:232(para)
-msgid "Object servers manage actual objects (i.e. files) on the storage nodes."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:236(para)
-msgid "There are also a number of periodic processes which run to perform housekeeping tasks on the large data store. The most important of these is the replication services, which ensures consistency and availability through the cluster. Other periodic processes include auditors, updaters and reapers."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:244(para)
-msgid "Authentication is handled through configurable WSGI middleware (which will usually be Keystone)."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:246(guilabel)
-msgid "Image Store"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:247(para)
-msgid "The Glance architecture has stayed relatively stable since the Cactus release. The biggest architectural change has been the addition of authentication, which was added in the Diablo release. Just as a quick reminder, Glance has four main parts to it:"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:254(para)
-msgid "glance-api accepts Image API calls for image discovery, image retrieval and image storage."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:258(para)
-msgid "glance-registry stores, processes and retrieves metadata about images (size, type, etc.)."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:262(para)
-msgid "A database to store the image metadata. Like Nova, you can choose your database depending on your preference (but most people use MySQL or SQLite)."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:267(para)
-msgid "A storage repository for the actual image files. In the diagram above, Swift is shown as the image repository, but this is configurable. In addition to Swift, Glance supports normal filesystems, RADOS block devices, Amazon S3 and HTTP. Be aware that some of these choices are limited to read-only usage."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:275(para)
-msgid "There are also a number of periodic processes which run on Glance to support caching. The most important of these is the replication services, which ensures consistency and availability through the cluster. Other periodic processes include auditors, updaters and reapers."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:280(para)
-msgid "As you can see from the diagram in the Conceptual Architecture section, Glance serves a central role to the overall IaaS picture. It accepts API requests for images (or image metadata) from end users or Nova components and can store its disk files in the object storage service, Swift."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:286(guilabel)
-msgid "Identity"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:287(para)
-msgid "Keystone provides a single point of integration for OpenStack policy, catalog, token and authentication."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:291(para)
-msgid "Keystone handles API requests as well as providing configurable catalog, policy, token and identity services."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:296(para)
-msgid "Each Keystone function has a pluggable backend which allows different ways to use the particular service. Most support standard backends like LDAP or SQL, as well as Key Value Stores (KVS)."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:302(para)
-msgid "Most people will use this as a point of customization for their current authentication services."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:304(guilabel)
-msgid "Network"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:305(para)
-msgid "Neutron provides \"network connectivity as a service\" between interface devices managed by other OpenStack services (most likely Nova). The service works by allowing users to create their own networks and then attach interfaces to them. Like many of the OpenStack services, Neutron is highly configurable due to its plug-in architecture. These plug-ins accommodate different networking equipment and software. As such, the architecture and deployment can vary dramatically. In the above architecture, a simple Linux networking plug-in is shown."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:317(para)
-msgid "neutron-server accepts API requests and then routes them to the appropriate Neutron plug-in for action."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:321(para)
-msgid "Neutron plug-ins and agents perform the actual actions such as plugging and unplugging ports, creating networks or subnets and IP addressing. These plug-ins and agents differ depending on the vendor and technologies used in the particular cloud. Neutron ships with plug-ins and agents for: Cisco virtual and physical switches, NEC OpenFlow products, Open vSwitch, Linux bridging, the Ryu Network Operating System, and VMware NSX."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:331(para)
-msgid "The common agents are L3 (layer 3), DHCP (dynamic host IP addressing) and the specific plug-in agent."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:335(para)
-msgid "Most Neutron installations will also make use of a messaging queue to route information between the neutron-server and various agents as well as a database to store networking state for particular plug-ins."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:341(para)
-msgid "Neutron will interact mainly with Nova, where it will provide networks and connectivity for its instances."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:343(guilabel)
-msgid "Block Storage"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:344(para)
-msgid "Cinder separates out the persistent block storage functionality that was previously part of OpenStack Compute (in the form of nova-volume) into its own service. The OpenStack Block Storage API allows for manipulation of volumes, volume types (similar to compute flavors) and volume snapshots."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:352(para)
-msgid "cinder-api accepts API requests and routes them to cinder-volume for action."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:356(para)
-msgid "cinder-volume acts upon the requests by reading or writing to the Cinder database to maintain state, interacting with other processes (like cinder-scheduler) through a message queue and directly upon block storage providing hardware or software. It can interact with a variety of storage providers through a driver architecture. Currently, there are drivers for IBM, SolidFire, NetApp, Nexenta, Zadara, linux iSCSI and other storage providers."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:367(para)
-msgid "Much like nova-scheduler, the cinder-scheduler daemon picks the optimal block storage provider node to create the volume on."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:372(para)
-msgid "Cinder deployments will also make use of a messaging queue to route information between the cinder processes as well as a database to store volume state."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:377(para)
-msgid "Like Neutron, Cinder will mainly interact with Nova, providing volumes for its instances."
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:19(None)
-msgid "@@image: 'figures/image29.png'; md5=ce788bfd80e615104fa1e3257065824a"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:59(None)
-msgid "@@image: 'figures/image27.png'; md5=c144af5cbdee1bd17a7bde0bea5b5fe7"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:200(None)
-msgid "@@image: '../common/figures/nova-weighting-hosts.png'; md5=000eab4cf0deb1da2e692e023065a6ae"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:7(title) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:14(title)
-msgid "VM Placement"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:8(para)
-msgid "Compute uses the nova-scheduler service to determine how to dispatch compute and volume requests. For example, the nova-scheduler service determines which host a VM should launch on. The term host in the context of filters means a physical node that has a <systemitem class=\"service\">nova-compute</systemitem> service running on it. You can configure the scheduler through a variety of options."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:16(title) ./doc/training-guides/lab003-compute-node.xml:199(emphasis) ./doc/training-guides/lab001-control-node.xml:431(emphasis)
-msgid "Nova"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:23(para)
-msgid "Just as shown by above figure, nova-scheduler interacts with other components through queue and central database repo. For scheduling, queue is the essential communications hub."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:26(para)
-msgid "All compute nodes (also known as hosts in terms of OpenStack) periodically publish their status, resources available and hardware capabilities to nova-scheduler through the queue. nova-scheduler then collects this data and uses it to make decisions when a request comes in."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:31(para)
-msgid "By default, the compute scheduler is configured as a filter scheduler, as described in the next section. In the default configuration, this scheduler considers hosts that meet all the following criteria:"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:37(para)
-msgid "Are in the requested availability zone (AvailabilityZoneFilter)."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:41(para)
-msgid "Have sufficient RAM available (RamFilter)."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:44(para)
-msgid "Are capable of servicing the request (ComputeFilter)."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:49(guilabel)
-msgid "Filter Scheduler"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:50(para)
-msgid "The Filter Scheduler supports filtering and weighting to make informed decisions on where a new instance should be created. This Scheduler supports only working with Compute Nodes."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:54(guilabel) ./doc/training-guides/module001-ch009-vm-placement.xml:56(title)
-msgid "Filtering"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:63(para)
-msgid "During its work, Filter Scheduler first makes a dictionary of unfiltered hosts, then filters them using filter properties and finally chooses hosts for the requested number of instances (each time it chooses the most weighed host and appends it to the list of selected hosts)."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:68(para)
-msgid "If it turns up, that it can’t find candidates for the next instance, it means that there are no more appropriate hosts where the instance could be scheduled."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:71(para)
-msgid "If we speak about filtering and weighting, their work is quite flexible in the Filter Scheduler. There are a lot of filtering strategies for the Scheduler to support. Also you can even implement your own algorithm of filtering."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:75(para)
-msgid "There are some standard filter classes to use (nova.scheduler.filters):"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:79(para)
-msgid "AllHostsFilter - frankly speaking, this filter does no operation. It passes all the available hosts."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:83(para)
-msgid "ImagePropertiesFilter - filters hosts based on properties defined on the instance’s image. It passes hosts that can support the specified image properties contained in the instance."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:89(para)
-msgid "AvailabilityZoneFilter - filters hosts by availability zone. It passes hosts matching the availability zone specified in the instance properties."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:94(para)
-msgid "ComputeCapabilitiesFilter - checks that the capabilities provided by the host Compute service satisfy any extra specifications associated with the instance type. It passes hosts that can create the specified instance type."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:101(para)
-msgid "The extra specifications can have a scope at the beginning of the key string of a key/value pair. The scope format is scope:key and can be nested, i.e. key_string := scope:key_string. Example like capabilities:cpu_info: features is valid scope format. A key string without any : is non-scope format. Each filter defines its valid scope, and not all filters accept non-scope format."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:110(para)
-msgid "The extra specifications can have an operator at the beginning of the value string of a key/value pair. If there is no operator specified, then a default operator of s== is used. Valid operators are:"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:116(para)
-msgid "* = (equal to or greater than as a number; same as vcpus case)* == (equal to as a number)* != (not equal to as a number)* &gt;= (greater than or equal to as a number)* &lt;= (less than or equal to as a number)* s== (equal to as a string)* s!= (not equal to as a string)* s&gt;= (greater than or equal to as a string)* s&gt; (greater than as a string)* s&lt;= (less than or equal to as a string)* s&lt; (less than as a string)* &lt;in&gt; (substring)* &lt;or&gt; (find one of these)Examples are: \"&gt;= 5\", \"s== 2.1.0\", \"&lt;in&gt; gcc\", and \"&lt;or&gt; fpu &lt;or&gt; gpu\""
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:138(para)
-msgid "Here ram_allocation_ratio means the virtual RAM to physical RAM allocation ratio (it is 1.5 by default). Really, nice and simple."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:141(para)
-msgid "Next standard filter to describe is AvailabilityZoneFilter and it isn’t difficult too. This filter just looks at the availability zone of compute node and availability zone from the properties of the request. Each Compute service has its own availability zone. So deployment engineers have an option to run scheduler with availability zones support and can configure availability zones on each compute host. This classes method host_passes returns True if availability zone mentioned in request is the same on the current compute host."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:151(para)
-msgid "The ImagePropertiesFilter filters hosts based on the architecture, hypervisor type, and virtual machine mode specified in the instance. E.g., an instance might require a host that supports the arm architecture on a qemu compute host. The ImagePropertiesFilter will only pass hosts that can satisfy this request. These instance properties are populated from properties define on the instance’s image. E.g. an image can be decorated with these properties using glance image-update img-uuid --property architecture=arm --property hypervisor_type=qemu Only hosts that satisfy these requirements will pass the ImagePropertiesFilter."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:162(para)
-msgid "ComputeCapabilitiesFilter checks if the host satisfies any extra_specs specified on the instance type. The extra_specs can contain key/value pairs. The key for the filter is either non-scope format (i.e. no : contained), or scope format in capabilities scope (i.e. capabilities:xxx:yyy). One example of capabilities scope is capabilities:cpu_info:features, which will match host’s cpu features capabilities. The ComputeCapabilitiesFilter will only pass hosts whose capabilities satisfy the requested specifications. All hosts are passed if no extra_specs are specified."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:172(para)
-msgid "ComputeFilter is quite simple and passes any host whose Compute service is enabled and operational."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:174(para)
-msgid "Now we are going to IsolatedHostsFilter. There can be some special hosts reserved for specific images. These hosts are called isolated. So the images to run on the isolated hosts are also called isolated. This Scheduler checks if image_isolated flag named in instance specifications is the same that the host has."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:181(guilabel) ./doc/training-guides/module001-ch009-vm-placement.xml:196(title)
-msgid "Weights"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:182(para)
-msgid "Filter Scheduler uses so-called weights during its work."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:184(para)
-msgid "The Filter Scheduler weights hosts based on the config option scheduler_weight_classes, this defaults to nova.scheduler.weights.all_weighers, which selects the only weigher available – the RamWeigher. Hosts are then weighted and sorted with the largest weight winning."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:189(para)
-msgid "Filter Scheduler finds local list of acceptable hosts by repeated filtering and weighing. Each time it chooses a host, it virtually consumes resources on it, so subsequent selections can adjust accordingly. It is useful if the customer asks for the same large amount of instances, because weight is computed for each instance requested."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch009-vm-placement.xml:204(para)
-msgid "In the end Filter Scheduler sorts selected hosts by their weight and provisions instances on them."
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch019-developer-how-to-participate-day-eight-quiz.xml:6(title)
-msgid "Developer How To Participate Day Eight Quiz"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch019-developer-how-to-participate-day-eight-quiz.xml:8(title)
-msgid "Day 8, 16:40 to 17:00"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch016-developer-how-to-participate-day-seven-lab.xml:6(title)
-msgid "Developer How To Participate Lab Day Seven"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch016-developer-how-to-participate-day-seven-lab.xml:8(title)
-msgid "Day 7, 13:30 to 14:45, 15:00 to 16:30"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch009-developer-apis-day-four-lab.xml:6(title)
-msgid "Developer How To Participate Lab Day Four"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch009-developer-apis-day-four-lab.xml:8(title)
-msgid "Day 4, 13:30 to 14:45, 15:00 to 16:30"
-msgstr ""
-
-#: ./doc/training-guides/card039-nova.xml:7(title) ./doc/training-guides/lab003-compute-node.xml:202(para)
-msgid "Install Nova"
-msgstr ""
-
 #: ./doc/training-guides/bk003-ch012-developer-how-to-participate-day-five-lab.xml:6(title)
 msgid "Developer How To Participate Lab Day Five"
 msgstr ""
@@ -6020,632 +4786,84 @@ msgstr ""
 msgid "Day 5, 13:30 to 14:45, 15:00 to 16:30"
 msgstr ""
 
-#: ./doc/training-guides/bk004-architect-training-guide.xml:5(title)
-msgid "Architect Training Guide"
+#: ./doc/training-guides/training-cluster-by-script.xml:6(title)
+msgid "Build the Training Cluster, Scripted"
 msgstr ""
 
-#: ./doc/training-guides/bk004-architect-training-guide.xml:7(title)
-msgid "Architect Training Guide Coming Soon"
+#: ./doc/training-guides/training-cluster-by-script.xml:9(link)
+msgid "Extract the scripts locally by downloading and running the scripts tar file."
 msgstr ""
 
-#: ./doc/training-guides/card047-install-nova-compute.xml:7(title)
-msgid "Installing Nova"
+#: ./doc/training-guides/training-cluster-by-script.xml:11(para)
+msgid "Currently, only <filename>*/Scripts/</filename> folders content are being tested. Run the <filename>~/Scripts/test_scripts.sh</filename> file to test all scripts at once."
 msgstr ""
 
-#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml:10(title) ./doc/training-guides/bk003-ch004-developer-apis-in-depth.xml:10(title)
-msgid "Day 2 to 4, 09:00 to 11:00, 11:15 to 12:30"
+#: ./doc/training-guides/training-cluster-by-script.xml:16(title)
+msgid "To test scripts"
 msgstr ""
 
-#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml:14(title)
-msgid "Review Associate Overview Horizon and OpenStack CLI"
+#: ./doc/training-guides/training-cluster-by-script.xml:18(title)
+msgid "Set up the test environment"
 msgstr ""
 
-#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml:21(title)
-msgid "Review Associate Keystone Architecture"
+#: ./doc/training-guides/training-cluster-by-script.xml:19(para)
+msgid "To use Virtual Box as test environment, you must attach the following network adapters:"
 msgstr ""
 
-#: ./doc/training-guides/bk002-ch004-operator-controller-node.xml:28(title)
-msgid "Review Associate OpenStack Messaging and Queues"
+#: ./doc/training-guides/training-cluster-by-script.xml:23(para)
+msgid "Host-Only/ Bridged -- 10.10.10.51 (Guest) -- 10.10.10.xx (Host IP for Host-Only)"
 msgstr ""
 
-#: ./doc/training-guides/bk003-ch006-developer-apis-day-two-quiz.xml:6(title)
-msgid "Developer APIs in Depth Day Two Quiz"
+#: ./doc/training-guides/training-cluster-by-script.xml:27(para)
+msgid "Host-Only/ Bridged -- 192.168.100.51 (Guest) -- 192.168.100.xx (Host IP for Host-Only)"
 msgstr ""
 
-#: ./doc/training-guides/bk003-ch006-developer-apis-day-two-quiz.xml:8(title)
-msgid "Day 2, 16:40 to 17:00"
+#: ./doc/training-guides/training-cluster-by-script.xml:31(para)
+msgid "Bridged/NAT -- DHCP -- These Scripts should be run without internet connection after Pre-Install.sh. The Templates/* should be changed to the required IP Addresses for custom networks."
 msgstr ""
 
-#: ./doc/training-guides/lab003-compute-node.xml:33(para)
-msgid "Start your Controller Node (the one you setup in the previous section)."
+#: ./doc/training-guides/training-cluster-by-script.xml:39(title)
+msgid "Test scripts individually"
 msgstr ""
 
-#: ./doc/training-guides/lab003-compute-node.xml:74(para)
-msgid "Enable IP Forwarding by adding the following to <filename>/etc/sysctl.conf</filename>"
+#: ./doc/training-guides/training-cluster-by-script.xml:40(para)
+msgid "Run the shell scripts in the <filename>Scripts</filename> folder to verify they run correctly. Do not install Virtual Box, although it is recommended because your host machine might fail."
 msgstr ""
 
-#: ./doc/training-guides/lab003-compute-node.xml:91(emphasis) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:190(para)
-msgid "KVM"
+#: ./doc/training-guides/training-cluster-by-script.xml:43(para)
+msgid "To test the scripts, run them. Some scripts require input parameters. If you do not want to run them manually, run the <filename>Scripts/test_scripts.sh</filename> file. Virtual Box guest add-ons are not required to test the scripts as units."
 msgstr ""
 
-#: ./doc/training-guides/lab003-compute-node.xml:94(para)
-msgid "Install KVM:"
+#: ./doc/training-guides/training-cluster-by-script.xml:50(title)
+msgid "Test the entire system"
 msgstr ""
 
-#: ./doc/training-guides/lab003-compute-node.xml:100(para)
-msgid "Edit <filename>/etc/libvirt/qemu.conf</filename>"
+#: ./doc/training-guides/training-cluster-by-script.xml:51(para)
+msgid "You must install Virtual Box, Ubuntu Server 12.04 or 13.04, and the Virtual Box guest add-ons."
 msgstr ""
 
-#: ./doc/training-guides/lab003-compute-node.xml:109(para)
-msgid "Delete Default Virtual Bridge"
+#: ./doc/training-guides/training-cluster-by-script.xml:53(para)
+msgid "To install Virtual Box guest add-ons, complete one of these steps:"
 msgstr ""
 
-#: ./doc/training-guides/lab003-compute-node.xml:116(para)
-msgid "To Enable Live Migration Edit <filename>/etc/libvirt/libvirtd.conf</filename>"
+#: ./doc/training-guides/training-cluster-by-script.xml:57(para)
+msgid "Install the Virtual Box guest add-ons through ISO:"
 msgstr ""
 
-#: ./doc/training-guides/lab003-compute-node.xml:122(para)
-msgid "Edit <filename>/etc/init/libvirt-bin.conf</filename>"
+#: ./doc/training-guides/training-cluster-by-script.xml:65(para)
+msgid "Install the Virtual Box guest add-ons through Ubuntu repositories:"
 msgstr ""
 
-#: ./doc/training-guides/lab003-compute-node.xml:126(para)
-msgid "Edit <filename>/etc/default/libvirt-bin</filename>"
+#: ./doc/training-guides/bk003-ch008-developer-apis-day-three-quiz.xml:6(title)
+msgid "Developer APIs in Depth Day Three Quiz"
 msgstr ""
 
-#: ./doc/training-guides/lab003-compute-node.xml:130(para)
-msgid "Restart libvirt"
+#: ./doc/training-guides/bk003-ch008-developer-apis-day-three-quiz.xml:8(title)
+msgid "Day 3, 16:40 to 17:00"
 msgstr ""
 
-#: ./doc/training-guides/lab003-compute-node.xml:137(emphasis)
-msgid "Neutron and OVS"
-msgstr ""
-
-#: ./doc/training-guides/lab003-compute-node.xml:140(para) ./doc/training-guides/card041-neutron.xml:9(emphasis)
-msgid "Install Open vSwitch"
-msgstr ""
-
-#: ./doc/training-guides/lab003-compute-node.xml:144(para)
-msgid "Create bridges:"
-msgstr ""
-
-#: ./doc/training-guides/lab003-compute-node.xml:151(para)
-msgid "Install the Neutron Open vSwitch agent:"
-msgstr ""
-
-#: ./doc/training-guides/lab003-compute-node.xml:157(para)
-msgid "Edit <filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename>"
-msgstr ""
-
-#: ./doc/training-guides/lab003-compute-node.xml:178(para)
-msgid "Edit <filename>/etc/neutron/neutron.conf</filename>"
-msgstr ""
-
-#: ./doc/training-guides/lab003-compute-node.xml:193(para)
-msgid "Restart all the services:"
-msgstr ""
-
-#: ./doc/training-guides/lab003-compute-node.xml:209(para) ./doc/training-guides/lab001-control-node.xml:468(para)
-msgid "Edit <filename>/etc/nova/api-paste.ini</filename>"
-msgstr ""
-
-#: ./doc/training-guides/lab003-compute-node.xml:223(para)
-msgid "Edit <filename>/etc/nova/nova-compute.conf</filename>"
-msgstr ""
-
-#: ./doc/training-guides/lab003-compute-node.xml:232(para) ./doc/training-guides/lab001-control-node.xml:483(para)
-msgid "Edit <filename>/etc/nova/nova.conf</filename>"
-msgstr ""
-
-#: ./doc/training-guides/lab003-compute-node.xml:282(para)
-msgid "Restart nova services"
-msgstr ""
-
-#: ./doc/training-guides/lab003-compute-node.xml:286(para)
-msgid "List nova services (Check for the Smiley Faces to know if the services are running):"
-msgstr ""
-
-#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:6(title) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:6(title)
-msgid "Getting Started Lab"
-msgstr ""
-
-#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:8(title) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:8(title)
-msgid "Day 1, 13:30 to 14:45, 15:00 to 17:00"
-msgstr ""
-
-#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:12(title) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:12(title)
-msgid "Getting the Tools and Accounts for Committing Code"
-msgstr ""
-
-#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:26(title) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:26(title)
-msgid "Submit a Documentation Bug"
-msgstr ""
-
-#: ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:40(title) ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:40(title)
-msgid "Optional: Add to the Training Guide Documentation"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch018-developer-how-to-participate-day-eight-lab.xml:6(title)
-msgid "Developer How To Participate Lab Day Eight"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch018-developer-how-to-participate-day-eight-lab.xml:8(title)
-msgid "Day 8, 13:30 to 14:45, 15:00 to 16:30"
-msgstr ""
-
-#: ./doc/training-guides/card045-configure-virtual-networking.xml:7(title)
-msgid "Configure Virtual Networking"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:6(title) ./doc/training-guides/bk002-ch006-operator-controller-node-quiz.xml:6(title)
-msgid "Controller Node Quiz"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:8(title)
-msgid "Day 1, 14:25 to 14:45"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:10(title)
-msgid "Associate Training Guide, Controller Node Quiz Questions"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:15(title)
-msgid "When managing images for OpenStack you can complete all those tasks with the OpenStack dashboard. (True or False)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:20(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:36(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:101(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:118(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:159(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:174(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:238(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:301(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:91(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:106(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:121(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:160(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:175(para)
-msgid "True"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:23(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:39(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:104(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:121(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:162(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:177(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:241(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:304(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:94(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:109(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:124(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:163(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:178(para)
-msgid "False"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:31(title)
-msgid "When setting up access and security, SSH credentials (keypairs) must be injected into images after they are launched with a script. (True or False)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:47(title)
-msgid "You can track monthly costs with metrics like: (choose all that apply)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:51(para)
-msgid "VCPU"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:54(para)
-msgid "QoS"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:57(para)
-msgid "Uptime"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:60(para)
-msgid "Disks"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:63(para)
-msgid "RAM"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:71(title)
-msgid "The following OpenStack command-line clients are available. (choose all that apply)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:75(para)
-msgid "python-keystoneclient"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:78(para)
-msgid "python-hypervisorclient"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:81(para)
-msgid "python-imageclient"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:84(para)
-msgid "python-cinderclient"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:87(para)
-msgid "python-novaclient"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:95(title)
-msgid "To install a client package"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:96(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:113(para)
-msgid "Run this command: <placeholder-1/><placeholder-2/>"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:112(title)
-msgid "To list images"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:129(title)
-msgid "When troubleshooting image creation you will need to look at which of the following log files for errors? (choose all that apply)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:134(para)
-msgid "Examine the /var/log/nova-api.log"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:137(para)
-msgid "Examine the /var/log/nova-compute.log"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:140(para)
-msgid "Examine the /var/log/nova-error.log"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:143(para)
-msgid "Examine the /var/log/nova-status.log"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:146(para)
-msgid "Examine the /var/log/nova-image.log"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:154(title)
-msgid "To generate a keypair use the following command syntax: $ nova keypair-add --pub_key ~/.ssh/id_rsa.pub KEY_NAME"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:170(title)
-msgid "When you want to launch an instance you can only do that from an image. (True or False)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:185(title)
-msgid "An instance has a Private IP address which has the following properties? (choose all that apply)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:189(para)
-msgid "Used for communication between instances"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:192(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:193(para)
-msgid "VMware vShpere 4.1, update 1 or greater"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:195(para)
-msgid "Stays the same, even after reboots"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:198(para)
-msgid "Stays allocated, even if you terminate the instance"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:201(para)
-msgid "To see the status of the Private IP addresses you use the following command: $ nova floating-ip-pool-list"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:210(title)
-msgid "To start and stop and instance you can use the following options: (choose all that apply)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:214(para)
-msgid "Pause/Un-pause"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:217(para)
-msgid "Suspend/Resume"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:220(para)
-msgid "Reboot"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:223(para)
-msgid "Evacuate"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:226(para)
-msgid "Shutdown/Restart"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:234(title)
-msgid "To create a network in OpenStack use the following command: $ neutron net-create net1 (True or False)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:249(title)
-msgid "Identity Service provides the following functions: (choose all that apply)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:253(para)
-msgid "Group policy objects"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:256(para)
-msgid "Message queuing"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:259(para) ./doc/training-guides/module001-ch007-keystone-arch.xml:139(emphasis)
-msgid "User management"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:262(para)
-msgid "Publishing"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:265(para)
-msgid "Service catalog"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:273(title)
-msgid "The AMQP supports the following messaging bus options: (choose all that apply)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:277(para)
-msgid "ZeroMQ"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:283(para)
-msgid "Tibco Rendezvous"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:286(para)
-msgid "IBM WebSphere Message Broker"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:289(para)
-msgid "Qpid"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:297(title)
-msgid "OpenStack uses the term tenant but in earlier versions it used the term customer. (True or False)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:314(title)
-msgid "Associate Training Guide, Controller Node Quiz Answers"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:318(para)
-msgid "B (False) - you can manage images through only the glance and nova clients or the Image Service and Compute APIs."
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:322(para)
-msgid "B (False) - Keypairs are SSH credentials that are injected into images when they are launched. For this to work, the image must contain the cloud-init package"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:326(para)
-msgid "A, C, D, E - You can track costs per month by showing metrics like number of VCPUs, disks, RAM, and uptime of all your instances"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:330(para)
-msgid "A, D, E - The following command-line clients are available for the respective services' APIs: cinder(python-cinderclient) Client for the Block Storage service API. Use to create and manage volumes. glance(python-glanceclient) Client for the Image Service API. Use to create and manage images. keystone(python-keystoneclient) Client for the Identity Service API. Use to create and manage users, tenants, roles, endpoints, and credentials. nova(python-novaclient) Client for the Compute API and its extensions. Use to create and manage images, instances, and flavors. neutron(python-neutronclient) Client for the Networking API. Use to configure networks for guest servers. This client was previously known as neutron. swift(python-swiftclient) Client for the Object Storage API. Use to gather statistics, list items, update metadata, upload, download and delete files stored by the object storage service. Provides access to a swift installation for ad hoc processing. heat(python-heatclient)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:346(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:349(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:367(para)
-msgid "A (True)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:352(para)
-msgid "A, B"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:355(para)
-msgid "B (False) - $ nova keypair-add KEY_NAME &gt; MY_KEY.pem"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:358(para)
-msgid "B (False) - you can launch and instance from an image or a volume"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:361(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:222(para)
-msgid "A, B, C"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:364(para)
-msgid "A, B, C, D"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:370(para)
-msgid "C, E"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:373(para)
-msgid "A, B, E"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:376(para)
-msgid "B (False) - Because the term project was used instead of tenant in earlier versions of OpenStack Compute, some command-line tools use --project_id instead of --tenant-id or --os-tenant-id to refer to a tenant ID."
-msgstr ""
-
-#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml:10(title)
-msgid "Days 5 to 6, 09:00 to 11:00, 11:15 to 12:30"
-msgstr ""
-
-#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml:14(title)
-msgid "Review Associate VM Placement"
-msgstr ""
-
-#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml:21(title)
-msgid "Review Associate VM Provisioning Indepth"
-msgstr ""
-
-#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml:28(title)
-msgid "Review Associate OpenStack Block Storage"
-msgstr ""
-
-#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:10(title)
-msgid "Day 9, 09:00 to 11:00, 11:15 to 12:30"
-msgstr ""
-
-#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:14(title)
-msgid "Review Associate Introduction to Object Storage"
-msgstr ""
-
-#: ./doc/training-guides/bk002-ch013-operator-object-storage-node.xml:29(title)
-msgid "More Swift Concepts"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:8(title)
-msgid "Day 1, 10:40 to 11:00"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:10(title)
-msgid "Associate Training Guide, Getting Started Quiz Questions"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:15(title)
-msgid "What are some of the compelling features of a cloud? (choose all that apply)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:19(para)
-msgid "On-demand self-service"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:22(para)
-msgid "Resource pooling"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:25(para)
-msgid "Metered or measured service"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:28(para)
-msgid "Elasticity"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:31(para)
-msgid "Network access"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:39(title)
-msgid "What three service models does cloud computing provide? (choose all that apply)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:43(para)
-msgid "Software-as-a-Service (SaaS)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:46(para)
-msgid "Applications-as-a-Service (AaaS)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:49(para)
-msgid "Hardware-as-a-Service (HaaS)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:52(para)
-msgid "Infrastructure-as-a-Service (IaaS)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:55(para)
-msgid "Platform-as-a-Service (PaaS)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:63(title)
-msgid "What does the OpenStack project aim to deliver? (choose all that apply)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:67(para)
-msgid "Simple to implement cloud solution"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:70(para)
-msgid "Massively scalable cloud solution"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:73(para)
-msgid "Feature rich cloud solution"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:76(para)
-msgid "Multi-vendor interoperability cloud solution"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:79(para)
-msgid "A new hypervisor cloud solution"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:87(title)
-msgid "OpenStack code is freely available via the FreeBSD license. (True or False)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:102(title)
-msgid "OpenStack Swift is Object Storage. (True or False)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:117(title)
-msgid "OpenStack Networking is now called Quantum. (True or False)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:132(title)
-msgid "The Image Service (Glance) in OpenStack provides: (Choose all that apply)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:136(para)
-msgid "Base Templates which users can start new compute instances"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:139(para)
-msgid "Configuration of centralized policies across users and systems"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:142(para)
-msgid "Available images for users to choose from or create their own from existing servers"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:145(para)
-msgid "A central directory of users"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:148(para)
-msgid "Ability to take store snapshots in the Image Service for backup"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:156(title)
-msgid "OpenStack APIs are compatible with Amazon EC2 and Amazon S3. (True or False)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:171(title)
-msgid "Horizon is the OpenStack name for Compute. (True or False)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:186(title)
-msgid "Which Hypervisors can be supported in OpenStack? (Choose all that apply)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:196(para)
-msgid "bhyve (BSD)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:199(para)
-msgid "Xen"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:202(para)
-msgid "LXC"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:212(title)
-msgid "Associate Training Guide, Getting Started Quiz Answers"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:216(para)
-msgid "A, B, C, D, E"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:219(para)
-msgid "A, D, E"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:225(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:231(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:240(para)
-msgid "B"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:228(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:237(para)
-msgid "A"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:234(para)
-msgid "A, C, E"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:243(para)
-msgid "A, B, D, E"
+#: ./doc/training-guides/card126-horizon.xml:7(title)
+msgid "Install Horizon"
 msgstr ""
 
 #. When image changes, this message will be marked fuzzy or untranslated for you.
@@ -6654,6 +4872,10 @@ msgstr ""
 msgid "@@image: 'figures/image19.png'; md5=28fcef570d8132ed0c1db9336e463b4b"
 msgstr ""
 
+#: ./doc/training-guides/module001-ch007-keystone-arch.xml:6(title) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:21(title)
+msgid "Keystone Architecture"
+msgstr ""
+
 #. <para>More Content To be Added ...</para>
 #.   <section xml:id="module001-ch007-keystone-arch-concepts">
 #.     <title>Identity Service Concepts</title>
@@ -6761,6 +4983,10 @@ msgstr ""
 msgid "Keystone Authentication"
 msgstr ""
 
+#: ./doc/training-guides/module001-ch007-keystone-arch.xml:139(emphasis) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:259(para)
+msgid "User management"
+msgstr ""
+
 #: ./doc/training-guides/module001-ch007-keystone-arch.xml:141(para)
 msgid "The main components of Identity user management are:"
 msgstr ""
@@ -6837,167 +5063,326 @@ msgstr ""
 msgid "The commands for creating services and endpoints are described in a later section."
 msgstr ""
 
-#: ./doc/training-guides/bk003-ch021-developer-how-to-participate-day-nine-quiz.xml:6(title)
-msgid "Developer How To Participate Day Nine Quiz"
+#: ./doc/training-guides/card128-swift.xml:7(title)
+msgid "Install Swift"
 msgstr ""
 
-#: ./doc/training-guides/card041-neutron.xml:7(title) ./doc/training-guides/card041-neutron.xml:16(emphasis)
-msgid "Install Neutron"
+#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml:10(title)
+msgid "Days 5 to 6, 09:00 to 11:00, 11:15 to 12:30"
 msgstr ""
 
-#: ./doc/training-guides/card041-neutron.xml:10(para)
-msgid "Open vSwitch is one of many options, but for now we will stick with OVS."
+#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml:14(title)
+msgid "Review Associate VM Placement"
 msgstr ""
 
-#: ./doc/training-guides/bk001-ch011-associate-assessment.xml:8(title)
-msgid "Day 2, 15:00 to 16:00"
+#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml:21(title)
+msgid "Review Associate VM Provisioning Indepth"
 msgstr ""
 
-#: ./doc/training-guides/bk003-ch004-developer-apis-in-depth.xml:8(title)
-msgid "Developer APIs in Depth"
+#: ./doc/training-guides/bk002-ch007-operator-compute-node.xml:28(title)
+msgid "Review Associate OpenStack Block Storage"
+msgstr ""
+
+#: ./doc/training-guides/card026-network-node-architecture.xml:7(title)
+msgid "Network Node Overview"
+msgstr ""
+
+#: ./doc/training-guides/card047-install-nova-compute.xml:7(title)
+msgid "Installing Nova"
+msgstr ""
+
+#: ./doc/training-guides/card037-rabbitmq.xml:7(title)
+msgid "Installing RabbitMQ"
+msgstr ""
+
+#: ./doc/training-guides/card037-rabbitmq.xml:14(link)
+msgid "Submit a bug on the section above. Add a short description for the bug summary. Add a paragraph for the description and then tag with training-manuals."
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:6(title) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:6(title)
+msgid "Getting Started Lab"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:8(title) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:8(title)
+msgid "Day 1, 13:30 to 14:45, 15:00 to 17:00"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:12(title) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:12(title)
+msgid "Getting the Tools and Accounts for Committing Code"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:26(title) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:26(title)
+msgid "Submit a Documentation Bug"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch002-developer-getting-started-lab.xml:40(title) ./doc/training-guides/bk002-ch002-operator-getting-started-lab.xml:40(title)
+msgid "Optional: Add to the Training Guide Documentation"
+msgstr ""
+
+#: ./doc/training-guides/st-training-guides.xml:7(title) ./doc/training-guides/st-training-guides.xml:9(titleabbrev) ./doc/training-guides/st-training-guides.xml:15(productname)
+msgid "OpenStack Training Guides"
+msgstr ""
+
+#: ./doc/training-guides/st-training-guides.xml:12(year)
+msgid "2013"
+msgstr ""
+
+#: ./doc/training-guides/st-training-guides.xml:13(holder)
+msgid "OpenStack Foundation"
+msgstr ""
+
+#: ./doc/training-guides/st-training-guides.xml:18(remark) ./doc/training-guides/st-training-guides.xml:22(remark)
+msgid "Copyright details are filled in by the template."
+msgstr ""
+
+#: ./doc/training-guides/st-training-guides.xml:26(para)
+msgid "OpenStack™ Training Guides offer the open source community software training for cloud administration and management for any organization."
+msgstr ""
+
+#: ./doc/training-guides/st-training-guides.xml:33(date)
+msgid "2013-11-04"
+msgstr ""
+
+#: ./doc/training-guides/st-training-guides.xml:37(para)
+msgid "major restructure of guides"
+msgstr ""
+
+#: ./doc/training-guides/st-training-guides.xml:43(date)
+msgid "2013-09-11"
+msgstr ""
+
+#: ./doc/training-guides/st-training-guides.xml:47(para)
+msgid "first training guides sprint held"
+msgstr ""
+
+#: ./doc/training-guides/st-training-guides.xml:53(date)
+msgid "2013-08-07"
+msgstr ""
+
+#: ./doc/training-guides/st-training-guides.xml:57(para)
+msgid "rough draft published to the web"
+msgstr ""
+
+#: ./doc/training-guides/st-training-guides.xml:63(date)
+msgid "2013-07-09"
+msgstr ""
+
+#: ./doc/training-guides/st-training-guides.xml:67(para)
+msgid "first draft released"
+msgstr ""
+
+#: ./doc/training-guides/st-training-guides.xml:73(date)
+msgid "2013-06-18"
+msgstr ""
+
+#: ./doc/training-guides/st-training-guides.xml:77(para)
+msgid "blueprint created"
 msgstr ""
 
 #. When image changes, this message will be marked fuzzy or untranslated for you.
 #. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:213(None)
-msgid "@@image: 'figures/image02.png'; md5=9568a4bc836fe6a413f5ea2a5297d475"
+#: ./doc/training-guides/user-story-includes-template.xml:19(None)
+msgid "@@image: 'figures/openstack-training-example-image.png'; md5=87bf110d5b53b2168680e1370176ef02"
 msgstr ""
 
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:7(title) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:21(title)
-msgid "VM provisioning in-depth"
+#: ./doc/training-guides/user-story-includes-template.xml:7(title)
+msgid "Including external content for user stories, version 1.3"
 msgstr ""
 
-#. <para>More content to be added...</para>
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:11(para)
-msgid "The request flow for provisioning an instance goes like this:"
+#: ./doc/training-guides/user-story-includes-template.xml:8(para)
+msgid "Save your user story file as associate-my-user-story-name, operator-my-user-story, etc. For example, the user story that I assigned myself is operator bug fix so the file name would be operator-fix-documentation-bug.xml. See the operator-fix-documentation-bug.xml file in the repository for more details."
 msgstr ""
 
-#. 1
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:21(para)
-msgid "The dashboard or CLI gets the user credentials and authenticates with the Identity Service via REST API."
+#: ./doc/training-guides/user-story-includes-template.xml:12(para)
+msgid "The include statements below are meant to help you tell and teach the user story. Include as much content as necessary and use examples."
 msgstr ""
 
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:24(para)
-msgid "The Identity Service authenticates the user with the user credentials, and then generates and sends back an auth-token which will be used for sending the request to other components through REST-call."
+#: ./doc/training-guides/user-story-includes-template.xml:14(para)
+msgid "Create diagrams through gdraw and export as png. Reference as local file in the /figures/ director. Share as 'Anyone With the Link' can 'Edit' and add URL to the description so anyone else can update the original."
 msgstr ""
 
-#. 2
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:33(para)
-msgid "The dashboard or CLI converts the new instance request specified in <guilabel>launch instance</guilabel> or <placeholder-1/> form to a REST API request and sends it to <systemitem class=\"service\">nova-api</systemitem>."
+#: ./doc/training-guides/user-story-includes-template.xml:17(para)
+msgid "<placeholder-1/> big dummy example image"
 msgstr ""
 
-#. 3
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:42(para)
-msgid "<systemitem class=\"service\">nova-api</systemitem> receives the request and sends a request to the Identity Service for validation of the auth-token and access permission."
+#: ./doc/training-guides/user-story-includes-template.xml:23(link)
+msgid "https://docs.google.com/drawings/d/1Tdn4SZLBdvQybW_nK_lO380YRIe5T6PsI0IyLH5XE3M/edit?usp=sharing"
 msgstr ""
 
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:47(para)
-msgid "The Identity Service validates the token and sends updated authentication headers with roles and permissions."
+#: ./doc/training-guides/user-story-includes-template.xml:25(emphasis)
+msgid "Including a whole file. Include as much description about what is being taught here."
 msgstr ""
 
-#. 4
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:54(para)
-msgid "<systemitem class=\"service\">nova-api</systemitem> checks for conflicts with <systemitem class=\"service\">nova-database</systemitem>."
+#: ./doc/training-guides/user-story-includes-template.xml:37(emphasis)
+msgid "Including a section of a file. Include as much description about what is being taught here."
 msgstr ""
 
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:59(para)
-msgid "<systemitem class=\"service\">nova-api</systemitem> creates initial database entry for a new instance."
+#: ./doc/training-guides/user-story-includes-template.xml:45(link)
+msgid "Submit a bug on the section above. Leave a short description for the bug summary, a paragraph for the description and then tag with training-manuals."
 msgstr ""
 
-#. 5
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:66(para)
-msgid "<systemitem class=\"service\">nova-api</systemitem> sends the rpc.call request to <systemitem class=\"service\">nova-scheduler</systemitem> expecting to get updated instance entry with host ID specified."
+#: ./doc/training-guides/bk002-ch006-operator-controller-node-quiz.xml:6(title) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:6(title)
+msgid "Controller Node Quiz"
 msgstr ""
 
-#. 6
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:75(para)
-msgid "<systemitem class=\"service\">nova-scheduler</systemitem> picks up the request from the queue."
+#: ./doc/training-guides/bk002-ch006-operator-controller-node-quiz.xml:8(title)
+msgid "Days 2 to 4, 16:40 to 17:00"
 msgstr ""
 
-#. 7
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:82(para)
-msgid "<systemitem class=\"service\">nova-scheduler</systemitem> interacts with <systemitem class=\"service\">nova-database</systemitem> to find an appropriate host via filtering and weighing."
+#: ./doc/training-guides/module002-ch005-floating-ips.xml:7(title)
+msgid "Floating IP Addresses And Security Rules"
 msgstr ""
 
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:88(para)
-msgid "<systemitem class=\"service\">nova-scheduler</systemitem> returns the updated instance entry with the appropriate host ID after filtering and weighing."
+#: ./doc/training-guides/module002-ch005-floating-ips.xml:8(para)
+msgid "OpenStack Networking has the concept of Fixed IPs and Floating IPs. Fixed IPs are assigned to an instance on creation and stay the same until the instance is explicitly terminated. Floating ips are ip addresses that can be dynamically associated with an instance. This address can be disassociated and associated with another instance at any time."
 msgstr ""
 
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:93(para)
-msgid "<systemitem class=\"service\">nova-scheduler</systemitem> sends the rpc.cast request to <systemitem class=\"service\">nova-compute</systemitem> for launching an instance on the appropriate host."
+#: ./doc/training-guides/module002-ch005-floating-ips.xml:15(para)
+msgid "Various tasks carried out by Floating IP's as of now."
 msgstr ""
 
-#. 8
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:102(para)
-msgid "<systemitem class=\"service\">nova-compute</systemitem> picks up the request from the queue."
+#: ./doc/training-guides/module002-ch005-floating-ips.xml:19(para)
+msgid "create IP ranges under a certain group, only available for admin role."
 msgstr ""
 
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:108(para)
-msgid "<systemitem class=\"service\">nova-compute</systemitem> sends the rpc.call request to <systemitem class=\"service\">nova-conductor</systemitem> to fetch the instance information such as host ID and flavor (RAM, CPU, Disk)."
+#: ./doc/training-guides/module002-ch005-floating-ips.xml:23(para)
+msgid "allocate an floating IP to a certain tenant, only available for admin role."
 msgstr ""
 
-#. 10
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:119(para)
-msgid "<systemitem class=\"service\">nova-conductor</systemitem> picks up the request from the queue."
+#: ./doc/training-guides/module002-ch005-floating-ips.xml:27(para)
+msgid "deallocate an floating IP from a certain tenant"
 msgstr ""
 
-#. 11
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:126(para)
-msgid "<systemitem class=\"service\">nova-conductor</systemitem> interacts with <systemitem class=\"service\">nova-database</systemitem>."
+#: ./doc/training-guides/module002-ch005-floating-ips.xml:31(para)
+msgid "associate an floating IP to a given instance"
 msgstr ""
 
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:131(para)
-msgid "<systemitem class=\"service\">nova-conductor</systemitem> returns the instance information."
+#: ./doc/training-guides/module002-ch005-floating-ips.xml:35(para)
+msgid "disassociate an floating IP from a certain instance"
 msgstr ""
 
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:135(para)
-msgid "<systemitem class=\"service\">nova-compute</systemitem> picks up the instance information from the queue."
+#: ./doc/training-guides/module002-ch005-floating-ips.xml:39(para)
+msgid "Just as shown by the above figure, we will have nova-network-api to support nova client floating commands. nova-network-api will invoke neutron cli lib to interactive with neutron server via API. The data about floating IPs will be stored in to neutron DB. Neutron Agent, which is running on compute host will enforce the floating IP."
 msgstr ""
 
-#. 12
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:142(para)
-msgid "<systemitem class=\"service\">nova-compute</systemitem> performs the REST call by passing the auth-token to <systemitem class=\"service\">glance-api</systemitem>. Then, <systemitem class=\"service\">nova-compute</systemitem> uses the Image ID to retrieve the Image URI from the Image Service, and loads the image from the image storage."
+#: ./doc/training-guides/module002-ch005-floating-ips.xml:46(guilabel)
+msgid "Multiple Floating IP Pools"
 msgstr ""
 
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:152(para)
-msgid "<systemitem class=\"service\">glance-api</systemitem> validates the auth-token with keystone."
+#: ./doc/training-guides/module002-ch005-floating-ips.xml:48(para)
+msgid "The L3 API in OpenStack Networking supports multiple floating IP pools. In OpenStack Networking, a floating IP pool is represented as an external network and a floating IP is allocated from a subnet associated with the external network. Since each L3 agent can be associated with at most one external network, we need to invoke multiple L3 agent to define multiple floating IP pools. 'gateway_external_network_id'in L3 agent configuration file indicates the external network that the L3 agent handles. You can run multiple L3 agent instances on one host."
 msgstr ""
 
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:157(para)
-msgid "<systemitem class=\"service\">nova-compute</systemitem> gets the image metadata."
+#: ./doc/training-guides/module002-ch005-floating-ips.xml:59(para)
+msgid "In addition, when you run multiple L3 agents, make sure that handle_internal_only_routers is set to Trueonly for one L3 agent in an OpenStack Networking deployment and set to Falsefor all other L3 agents. Since the default value of this parameter is True, you need to configure it carefully."
 msgstr ""
 
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:163(para)
-msgid "<systemitem class=\"service\">nova-compute</systemitem> performs the REST-call by passing the auth-token to Network API to allocate and configure the network so that the instance gets the IP address."
+#: ./doc/training-guides/module002-ch005-floating-ips.xml:65(para)
+msgid "Before starting L3 agents, you need to create routers and external networks, then update the configuration files with UUID of external networks and start L3 agents."
 msgstr ""
 
-#. 15
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:173(para)
-msgid "<systemitem class=\"service\">neutron-server</systemitem> validates the auth-token with keystone."
+#: ./doc/training-guides/module002-ch005-floating-ips.xml:69(para)
+msgid "For the first agent, invoke it with the following l3_agent.ini where handle_internal_only_routers is True."
 msgstr ""
 
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:177(para)
-msgid "<systemitem class=\"service\">nova-compute</systemitem> retrieves the network info."
+#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:7(title)
+msgid "Security in Neutron"
 msgstr ""
 
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:183(para)
-msgid "<systemitem class=\"service\">nova-compute</systemitem> performs the REST call by passing the auth-token to Volume API to attach volumes to the instance."
+#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:8(guilabel)
+msgid "Security Groups"
 msgstr ""
 
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:191(para)
-msgid "<systemitem class=\"service\">cinder-api</systemitem> validates the auth-token with keystone."
+#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:9(para)
+msgid "Security groups and security group rules allow administrators and tenants the ability to specify the type of traffic and direction (ingress/egress) that is allowed to pass through a port. A security group is a container for security group rules."
 msgstr ""
 
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:196(para)
-msgid "<systemitem class=\"service\">nova-compute</systemitem> retrieves the block storage info."
+#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:14(para)
+msgid "When a port is created in OpenStack Networking it is associated with a security group. If a security group is not specified the port will be associated with a 'default' security group. By default this group will drop all ingress traffic and allow all egress traffic. Rules can be added to this group in order to change this behaviour."
 msgstr ""
 
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:202(para)
-msgid "<systemitem class=\"service\">nova-compute</systemitem> generates data for the hypervisor driver and executes the request on the hypervisor (via libvirt or API)."
+#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:20(para)
+msgid "If one desires to use the OpenStack Compute security group APIs and/or have OpenStack Compute orchestrate the creation of new ports for instances on specific security groups, additional configuration is needed. To enable this, one must configure the following file /etc/nova/nova.conf and set the config option security_group_api=neutron on every node running nova-compute and nova-api. After this change is made, restart nova-api and nova-compute in order to pick up this change. After this change is made, the user will be able to use both the OpenStack Compute and OpenStack Network security group API at the same time."
 msgstr ""
 
-#: ./doc/training-guides/module001-ch010-vm-provisioning-indepth.xml:210(title)
-msgid "Nova VM provisioning"
+#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:32(guilabel)
+msgid "Authentication and Authorization"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:33(para)
+msgid "OpenStack Networking uses the OpenStack Identity service (project name keystone) as the default authentication service. When OpenStack Identity is enabled, users submitting requests to the OpenStack Networking service must provide an authentication token in X-Auth-Token request header. The aforementioned token should have been obtained by authenticating with the OpenStack Identity endpoint. For more information concerning authentication with OpenStack Identity, please refer to the OpenStack Identity documentation. When OpenStack Identity is enabled, it is not mandatory to specify tenant_id for resources in create requests, as the tenant identifier will be derived from the Authentication token. Please note that the default authorization settings only allow administrative users to create resources on behalf of a different tenant. OpenStack Networking uses information received from OpenStack Identity to authorize user requests. OpenStack Networking handles two kind of authorization policies:"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:54(para)
+msgid "<emphasis role=\"bold\">Operation-based:</emphasis> policies specify access criteria for specific operations, possibly with fine-grained control over specific attributes."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:60(para)
+msgid "<emphasis role=\"bold\">Resource-based:</emphasis>whether access to specific resource might be granted or not according to the permissions configured for the resource (currently available only for the network resource). The actual authorization policies enforced in OpenStack Networking might vary from deployment to deployment."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:70(para)
+msgid "The policy engine reads entries from the policy.json file. The actual location of this file might vary from distribution to distribution. Entries can be updated while the system is running, and no service restart is required. That is to say, every time the policy file is updated, the policies will be automatically reloaded. Currently the only way of updating such policies is to edit the policy file. Please note that in this section we will use both the terms \"policy\" and \"rule\" to refer to objects which are specified in the same way in the policy file; in other words, there are no syntax differences between a rule and a policy. We will define a policy something which is matched directly from the OpenStack Networking policy engine, whereas we will define a rule as the elements of such policies which are then evaluated. For instance in create_subnet: [[\"admin_or_network_owner\"]], create_subnet is regarded as a policy, whereas admin_or_network_owner is regarded as a rule."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:88(para)
+msgid "Policies are triggered by the OpenStack Networking policy engine whenever one of them matches an OpenStack Networking API operation or a specific attribute being used in a given operation. For instance the create_subnet policy is triggered every time a POST /v2.0/subnets request is sent to the OpenStack Networking server; on the other hand create_network:shared is triggered every time the shared attribute is explicitly specified (and set to a value different from its default) in a POST /v2.0/networks request. It is also worth mentioning that policies can be also related to specific API extensions; for instance extension:provider_network:set will be triggered if the attributes defined by the Provider Network extensions are specified in an API request."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:102(para)
+msgid "An authorization policy can be composed by one or more rules. If more rules are specified, evaluation policy will be successful if any of the rules evaluates successfully; if an API operation matches multiple policies, then all the policies must evaluate successfully. Also, authorization rules are recursive. Once a rule is matched, the rule(s) can be resolved to another rule, until a terminal rule is reached."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:110(para)
+msgid "The OpenStack Networking policy engine currently defines the following kinds of terminal rules:"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:114(para)
+msgid "<emphasis role=\"bold\">Role-based rules:</emphasis> evaluate successfully if the user submitting the request has the specified role. For instance \"role:admin\"is successful if the user submitting the request is an administrator."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:121(para)
+msgid "<emphasis role=\"bold\">Field-based rules:</emphasis> evaluate successfully if a field of the resource specified in the current request matches a specific value. For instance \"field:networks:shared=True\" is successful if the attribute shared of the network resource is set to true."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:130(para)
+msgid "<emphasis role=\"bold\">Generic rules:</emphasis>compare an attribute in the resource with an attribute extracted from the user's security credentials and evaluates successfully if the comparison is successful. For instance \"tenant_id:%(tenant_id)s\" is successful if the tenant identifier in the resource is equal to the tenant identifier of the user submitting the request."
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch008-associate-network-node-quiz.xml:8(title)
+msgid "Day 2, 10:40 to 11:00"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch015-developer-how-to-participate-day-six-quiz.xml:6(title)
+msgid "Developer How To Participate Day Six Quiz"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch015-developer-how-to-participate-day-six-quiz.xml:8(title)
+msgid "Day 6, 16:40 to 17:00"
+msgstr ""
+
+#: ./doc/training-guides/bk001-bk010-associate-object-storage-node-quiz.xml:5(title) ./doc/training-guides/bk002-ch015-operator-object-storage-node-quiz.xml:6(title)
+msgid "Object Storage Node Quiz"
+msgstr ""
+
+#: ./doc/training-guides/bk001-bk010-associate-object-storage-node-quiz.xml:7(title)
+msgid "Day 2, 14:25 to 14:45"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch020-developer-how-to-participate-day-nine-lab.xml:6(title)
+msgid "Developer How To Participate Lab Day Nine"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch020-developer-how-to-participate-day-nine-lab.xml:8(title)
+msgid "Day 9, 13:30 to 14:45, 15:00 to 16:30"
+msgstr ""
+
+#: ./doc/training-guides/lab004-openstack-production.xml:7(title)
+msgid "OpenStack In Production"
+msgstr ""
+
+#: ./doc/training-guides/lab004-openstack-production.xml:8(para)
+msgid "More Content To be Added."
 msgstr ""
 
 #: ./doc/training-guides/bk002-ch011-operator-network-node-lab.xml:6(title) ./doc/training-guides/bk002-ch011-operator-network-node-lab.xml:12(title)
@@ -7008,88 +5393,88 @@ msgstr ""
 msgid "Days 7 to 8, 13:30 to 14:45, 15:00 to 17:00"
 msgstr ""
 
-#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml:22(title)
-msgid "Review Associate Introduction"
+#: ./doc/training-guides/bk002-ch010-operator-network-node.xml:10(title)
+msgid "Days 7 to 8, 09:00 to 11:00, 11:15 to 12:30"
 msgstr ""
 
-#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml:29(title)
-msgid "Review Associate Brief Overview"
+#: ./doc/training-guides/bk002-ch010-operator-network-node.xml:14(title)
+msgid "Review Associate Networking in OpenStack"
 msgstr ""
 
-#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml:36(title)
-msgid "Review Associate Core Projects"
+#: ./doc/training-guides/bk002-ch010-operator-network-node.xml:21(title)
+msgid "Review Associate OpenStack Networking Concepts"
 msgstr ""
 
-#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml:43(title)
-msgid "Review Associate OpenStack Architecture"
+#: ./doc/training-guides/bk002-ch010-operator-network-node.xml:29(para) ./doc/training-guides/bk004-architect-training-guide.xml:8(para) ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:51(para) ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:72(para)
+msgid "TBD"
 msgstr ""
 
-#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml:50(title)
-msgid "Review Associate Virtual Machine Provisioning Walk-Through"
+#: ./doc/training-guides/bk002-ch010-operator-network-node.xml:32(title)
+msgid "Operator OpenStack Neutron Use Cases"
 msgstr ""
 
-#: ./doc/training-guides/card008.xml:7(title)
-msgid "Understanding the RefStack Architecture"
+#: ./doc/training-guides/bk002-ch010-operator-network-node.xml:39(title)
+msgid "Operator OpenStack Neutron Security"
 msgstr ""
 
-#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:7(title) ./doc/training-guides/bk001-ch007-associate-network-node.xml:21(title)
-msgid "OpenStack Networking Concepts"
+#: ./doc/training-guides/bk002-ch010-operator-network-node.xml:46(title)
+msgid "Operator OpenStack Neutron Floating IPs"
 msgstr ""
 
-#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:8(emphasis)
-msgid "Network Types"
+#: ./doc/training-guides/lab000-important-terms.xml:6(title)
+msgid "Important terms"
 msgstr ""
 
-#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:9(para)
-msgid "The OpenStack Networking configuration provided by the Rackspace Private Cloud cookbooks allows you to choose between VLAN or GRE isolated networks, both provider- and tenant-specific. From the provider side, an administrator can also create a flat network."
+#: ./doc/training-guides/lab000-important-terms.xml:8(title)
+msgid "Host Operating System (Host)"
 msgstr ""
 
-#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:14(para)
-msgid "The type of network that is used for private tenant networks is determined by the network_type attribute, which can be edited in the Chef override_attributes. This attribute sets both the default provider network type and the only type of network that tenants are able to create. Administrators can always create flat and VLAN networks. GRE networks of any type require the network_type to be set to gre."
+#: ./doc/training-guides/lab000-important-terms.xml:9(para)
+msgid "The operating system that is installed on your laptop or desktop that hosts virtual machines. This is commonly referred to as the host OS or <glossterm>host</glossterm>. In short, the machine where your Virtual Box is installed."
 msgstr ""
 
-#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:21(emphasis)
-msgid "Namespaces"
+#: ./doc/training-guides/lab000-important-terms.xml:16(title)
+msgid "Guest Operating System (Guest)"
 msgstr ""
 
-#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:22(para)
-msgid "For each network you create, the Network node (or Controller node, if combined) will have a unique network namespace (netns) created by the DHCP and Metadata agents. The netns hosts an interface and IP addresses for dnsmasq and the quantum-ns-metadata-proxy. You can view the namespaces with the ip netns [list], and can interact with the namespaces with the ip netns exec &lt;namespace&gt; &lt;command&gt; command."
+#: ./doc/training-guides/lab000-important-terms.xml:17(para)
+msgid "The operating system that is installed on your Virtual Box Virtual Machine. This virtual instance is independent of the host OS. It is commonly referred to as <glossterm>guest OS</glossterm> or guest."
 msgstr ""
 
-#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:30(emphasis)
-msgid "Metadata"
+#: ./doc/training-guides/lab000-important-terms.xml:23(title)
+msgid "Node"
 msgstr ""
 
-#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:31(para)
-msgid "Not all networks or VMs need metadata access. Rackspace recommends that you use metadata if you are using a single network. If you need metadata, you may also need a default route. (If you don't need a default route, no-gateway will do.)"
+#: ./doc/training-guides/lab000-important-terms.xml:24(para)
+msgid "In this context, refers specifically to servers. Each OpenStack server is a node."
 msgstr ""
 
-#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:36(para)
-msgid "To communicate with the metadata IP address inside the namespace, instances need a route for the metadata network that points to the dnsmasq IP address on the same namespaced interface. OpenStack Networking only injects a route when you do not specify a gateway-ip in the subnet."
+#: ./doc/training-guides/lab000-important-terms.xml:29(para)
+msgid "Hosts the database, Keystone (Middleware), and the servers for the scope of the current OpenStack deployment. It acts as the brains behind OpenStack and drives services such as authentication, database, and so on."
 msgstr ""
 
-#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:41(para)
-msgid "If you need to use a default route and provide instances with access to the metadata route, create the subnet without specifying a gateway IP and with a static route from 0.0.0.0/0 to your gateway IP address. Adjust the DHCP allocation pool so that it will not assign the gateway IP. With this configuration, dnsmasq will pass both routes to instances. This way, metadata will be routed correctly without any changes on the external gateway."
+#: ./doc/training-guides/lab000-important-terms.xml:36(para)
+msgid "Has the required Hypervisor (Qemu/KVM) and is your Virtual Machine host."
 msgstr ""
 
-#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:49(emphasis)
-msgid "OVS Bridges"
+#: ./doc/training-guides/lab000-important-terms.xml:41(para)
+msgid "Provides Network-as-a-Service and virtual networks for OpenStack."
 msgstr ""
 
-#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:50(para)
-msgid "An OVS bridge for provider traffic is created and configured on the nodes where single-network-node and single-compute are applied. Bridges are created, but physical interfaces are not added. An OVS bridge is not created on a Controller-only node."
+#: ./doc/training-guides/lab000-important-terms.xml:45(title)
+msgid "Using OpenSSH"
 msgstr ""
 
-#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:55(para)
-msgid "When creating networks, you can specify the type and properties, such as Flat vs. VLAN, Shared vs. Tenant, or Provider vs. Overlay. These properties identify and determine the behavior and resources of instances attached to the network. The cookbooks will create bridges for the configuration that you specify, although they do not add physical interfaces to provider bridges. For example, if you specify a network type of GRE, a br-tun tunnel bridge will be created to handle overlay traffic."
+#: ./doc/training-guides/lab000-important-terms.xml:46(para)
+msgid "After the network interfaces file has been setup, you can switch to an SSH session by using an OpenSSH client to log in remotely to the required server node (Control, Network, Compute). Open a terminal on your host machine and run the following command: <placeholder-1/>"
 msgstr ""
 
-#: ./doc/training-guides/card037-rabbitmq.xml:7(title)
-msgid "Installing RabbitMQ"
+#: ./doc/training-guides/bk004-architect-training-guide.xml:5(title)
+msgid "Architect Training Guide"
 msgstr ""
 
-#: ./doc/training-guides/card037-rabbitmq.xml:14(link)
-msgid "Submit a bug on the section above. Add a short description for the bug summary. Add a paragraph for the description and then tag with training-manuals."
+#: ./doc/training-guides/bk004-architect-training-guide.xml:7(title)
+msgid "Architect Training Guide Coming Soon"
 msgstr ""
 
 #. When image changes, this message will be marked fuzzy or untranslated for you.
@@ -7202,1004 +5587,6 @@ msgstr ""
 msgid "Per-tenant Routers with Private Networks"
 msgstr ""
 
-#: ./doc/training-guides/card040-cinder.xml:7(title)
-msgid "Install Cinder"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:20(para)
-msgid "<emphasis role=\"bold\">Vboxnet0</emphasis>, <emphasis role=\"bold\">Vboxnet1</emphasis>, <emphasis role=\"bold\">Vboxnet2</emphasis> - are virtual networks setup up by virtual box with your host machine. This is the way your host can communicate with the virtual machines. These networks are in turn used by VirtualBox virtual machines for OpenStack networks, so that OpenStack’s services can communicate with each other."
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:28(para)
-msgid "When you reboot the controller node on the VirtualBox virtual machine, you might lose Internet and network connectivity. Restart the networking service and use the <placeholder-1/> command to check whether the network interfaces can communicate over the given networks."
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:35(para)
-msgid "To avoid issues on the VirtualBox virtual machine (controller node), <emphasis role=\"bold\">save the virtual machine</emphasis> state instead of completing a reboot or shut down."
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:41(para)
-msgid "It is advised to take regular snapshots of the Virtual Box Virtual Machines (controller node) after each section. This will help you to save your session and revert back to it in case you break something while deploying OpenStack."
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:46(guilabel)
-msgid "controller node"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:47(para)
-msgid "Start your controller node the one you setup in previous section."
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:49(emphasis)
-msgid "Preparing Ubuntu 13.04/12.04"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:68(emphasis)
-msgid "Networking :"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:69(para)
-msgid "Configure your network by editing <filename>/etc/network/interfaces</filename> file"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:73(para)
-msgid "Open <filename>/etc/network/interfaces</filename> and edit file as mentioned:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:107(para)
-msgid "After saving the interfaces file, restart the networking service:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:113(para)
-msgid "You should see the expected network interface cards having the required IP Addresses."
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:117(emphasis)
-msgid "SSH from HOST"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:120(para)
-msgid "Create an SSH key pair for your Control Node. Follow the same steps as you did in the starting section of the article for your host machine."
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:125(para)
-msgid "To SSH into the Control Node from the Host Machine type the below command."
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:131(para)
-msgid "Now you can have access to your host clipboard."
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:134(emphasis)
-msgid "My SQL"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:137(para)
-msgid "Install MySQL:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:141(para)
-msgid "Configure mysql to accept all incoming requests:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:149(para)
-msgid "Install RabbitMQ:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:153(para)
-msgid "Install NTP service:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:157(para)
-msgid "Create these databases:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:172(emphasis)
-msgid "Other"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:175(para)
-msgid "Install other services:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:179(para)
-msgid "Enable IP_Forwarding:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:183(para)
-msgid "Also add the following two lines into<filename>/etc/sysctl.conf</filename>:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:189(para)
-msgid "To save you from reboot, perform the following"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:196(emphasis)
-msgid "Keystone"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:197(para)
-msgid "Keystone is an OpenStack project that provides Identity, Token, Catalog and Policy services for use specifically by projects in the OpenStack family. It implements OpenStack’s Identity API."
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:203(para)
-msgid "Install Keystone packages:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:207(para)
-msgid "Adapt the connection attribute in the <filename>/etc/keystone/keystone.conf</filename> to the new database:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:213(para)
-msgid "Restart the identity service then synchronize the database:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:219(para)
-msgid "Fill up the keystone database using the following scripts:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:224(filename)
-msgid "keystone_basic.sh"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:229(filename)
-msgid "keystone_endpoints_basic.sh"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:233(para)
-msgid "Run scripts:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:240(para)
-msgid "Create a simple credentials file"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:244(para)
-msgid "Paste the following:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:251(para)
-msgid "Load the above credentials:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:255(para)
-msgid "To test Keystone, we use a simple CLI command:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:259(emphasis)
-msgid "Glance"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:260(para)
-msgid "The OpenStack Glance project provides services for discovering, registering, and retrieving virtual machine images. Glance has a RESTful API that allows querying of VM image metadata as well as retrieval of the actual image."
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:264(para)
-msgid "VM images made available through Glance can be stored in a variety of locations from simple file systems to object-storage systems like the OpenStack Swift project."
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:267(para)
-msgid "Glance, as with all OpenStack projects, is written with the following design guidelines in mind:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:271(para)
-msgid "Component based architecture: Quickly adds new behaviors"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:275(para)
-msgid "Highly available: Scales to very serious workloads"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:278(para)
-msgid "Fault tolerant: Isolated processes avoid cascading failures"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:282(para)
-msgid "Recoverable: Failures should be easy to diagnose, debug, and rectify"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:286(para)
-msgid "Open standards: Be a reference implementation for a community-driven api"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:290(para)
-msgid "Install Glance:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:294(para)
-msgid "Update <filename>/etc/glance/glance-api-paste.ini</filename>:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:307(para)
-msgid "Update the <filename>/etc/glance/glance-registry-paste.ini</filename>:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:319(para)
-msgid "Update the <filename>/etc/glance/glance-api.conf</filename>:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:334(para)
-msgid "Update the <filename>/etc/glance/glance-registry.conf</filename>:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:349(para)
-msgid "Restart the glance-api and glance-registry services:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:354(para)
-msgid "Synchronize the Glance database:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:358(para)
-msgid "To test Glance, upload the “cirros cloud image” directly from the internet:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:363(para)
-msgid "Check if the image is successfully uploaded:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:368(para)
-msgid "Neutron is an OpenStack project to provide “network connectivity as a service\" between interface devices (e.g., vNICs) managed by other OpenStack services (e.g., nova)."
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:373(para)
-msgid "Install the Neutron Server and the Open vSwitch package collection:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:378(para)
-msgid "Edit the <filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename>:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:397(para)
-msgid "Edit the <filename>/etc/neutron/api-paste.ini</filename>:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:411(para)
-msgid "Edit the <filename>/etc/neutron/neutron.conf</filename>:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:427(para)
-msgid "Restart Neutron services:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:432(para)
-msgid "Nova is the project name for OpenStack Compute, a cloud computing fabric controller, the main part of an IaaS system. Individuals and organizations can use Nova to host and manage their own cloud computing systems. Nova originated as a project out of NASA Ames Research Laboratory."
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:437(para)
-msgid "Nova is written with the following design guidelines in mind:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:441(para)
-msgid "Component based architecture: Quickly adds new behaviors."
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:445(para) ./doc/training-guides/lab001-control-node.xml:564(para)
-msgid "Highly available: Scales to very serious workloads."
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:448(para) ./doc/training-guides/lab001-control-node.xml:567(para)
-msgid "Fault-Tolerant: Isolated processes avoid cascading failures."
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:452(para)
-msgid "Recoverable: Failures should be easy to diagnose, debug, and rectify."
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:456(para)
-msgid "Open standards: Be a reference implementation for a community-driven api."
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:460(para)
-msgid "API compatibility: Nova strives to be API-compatible with popular systems like Amazon EC2."
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:464(para)
-msgid "Install nova components:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:541(para)
-msgid "Synchronize your database:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:545(para)
-msgid "Restart nova-* services (all nova services):"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:549(para)
-msgid "Check for the smiling faces on <systemitem class=\"service\">nova-*</systemitem> services to confirm your installation:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:555(emphasis)
-msgid "Cinder"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:556(para)
-msgid "Cinder is an OpenStack project to provide “block storage as a service”."
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:560(para)
-msgid "Component based architecture: Quickly adds new behavior."
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:571(para)
-msgid "Recoverable: Failures should be easy to diagnose, debug and rectify."
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:575(para)
-msgid "Open standards: Be a reference implementation for a community-driven API."
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:579(para)
-msgid "API compatibility: Cinder strives to be API-compatible with popular systems like Amazon EC2."
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:583(para)
-msgid "Install Cinder components:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:587(para)
-msgid "Configure the iSCSI services:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:591(para)
-msgid "Restart the services:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:596(para)
-msgid "Edit <filename>/etc/cinder/api-paste.ini</filename>:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:612(para)
-msgid "Edit <filename>/etc/cinder/cinder.conf</filename>:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:628(para)
-msgid "Then, synchronize Cinder database:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:632(para)
-msgid "Finally, create a volume group and name it <literal>cinder-volumes</literal>:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:645(para)
-msgid "Proceed to create the physical volume then the volume group:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:652(para)
-msgid "Be aware that this volume group gets lost after a system reboot. If you do not want to perform this step again, make sure that you save the machine state and do not shut it down."
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:659(para)
-msgid "Restart the Cinder services:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:663(para)
-msgid "Verify if Cinder services are running:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:667(emphasis)
-msgid "Horizon"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:668(para)
-msgid "Horizon is the canonical implementation of OpenStack’s dashboard, which provides a web-based user interface to OpenStack services including Nova, Swift, Keystone, etc."
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:673(para)
-msgid "To install Horizon, complete these steps:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:677(para)
-msgid "If you do not like the OpenStack Ubuntu Theme, you can remove it with the below command:"
-msgstr ""
-
-#: ./doc/training-guides/lab001-control-node.xml:682(para)
-msgid "Reload Apache and memcached:"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch017-developer-how-to-participate-day-seven-quiz.xml:6(title)
-msgid "Developer How To Participate Day Seven Quiz"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch017-developer-how-to-participate-day-seven-quiz.xml:8(title)
-msgid "Day 7, 16:40 to 17:00"
-msgstr ""
-
-#: ./doc/training-guides/card046-L3_Configuration_in_the_Network_Node.xml:7(title)
-msgid "L3 Configuration in the Network Node"
-msgstr ""
-
-#: ./doc/training-guides/bk000-preface.xml:6(title)
-msgid "Start Here"
-msgstr ""
-
-#: ./doc/training-guides/bk000-preface.xml:8(title)
-msgid "Preface"
-msgstr ""
-
-#: ./doc/training-guides/bk000-preface.xml:13(title)
-msgid "OpenStack Training Guides Are Under Construction"
-msgstr ""
-
-#: ./doc/training-guides/bk000-preface.xml:14(para)
-msgid "We need your help! This is a community driven project to provide the user group community access to OpenStack training materials. We cannot make this work without your help."
-msgstr ""
-
-#: ./doc/training-guides/bk000-preface.xml:16(para)
-msgid "There are a few ways to get involved. The easiest way is to use the training guides. Look at the end of each section and you will see the Submit a Bug link. When you find something that can be improved or fixed, submit a bug by clicking on the link."
-msgstr ""
-
-#: ./doc/training-guides/bk000-preface.xml:19(para)
-msgid "If you want to get involved with the effort around OpenStack community training, read on, here are the options:"
-msgstr ""
-
-#: ./doc/training-guides/bk000-preface.xml:24(title)
-msgid "Attending a user group using the training materials"
-msgstr ""
-
-#: ./doc/training-guides/bk000-preface.xml:25(para)
-msgid "The OpenStack community training started at the SFBay OpenStack User Group. More information on this user group and others using the training guides on the <link href=\"https://wiki.openstack.org/wiki/OpenStackUserGroups\">OpenStack User Groups page</link>."
-msgstr ""
-
-#: ./doc/training-guides/bk000-preface.xml:32(title)
-msgid "Teach / Lead a user group using the training materials"
-msgstr ""
-
-#: ./doc/training-guides/bk000-preface.xml:33(para)
-msgid "Awesome! Your experience will not only give you more experience with OpenStack, but you will help some people find new jobs. We have put all the information about <link href=\"https://wiki.openstack.org/wiki/OpenStackUserGroups/HowTo#Running_a_Hackathon\">How To Run An OpenStack Hackathon</link> here."
-msgstr ""
-
-#: ./doc/training-guides/bk000-preface.xml:40(title)
-msgid "Help create the training pages"
-msgstr ""
-
-#: ./doc/training-guides/bk000-preface.xml:44(para)
-msgid "We are currently working on creating the Associate Training Guide. It is the first of four training guides. We are using the Install Guide, Administration Guides, Developer Documentation, and Aptira supplied content as the sources for most of the Associate Training Guide. The basic idea is that we use XML include statements to actually use the source content to create new pages. We aim to use as much of the material as possible from existing documentation. By doing this we reuse and improve the existing docs. The topics in the Associate Training Guide are in a bunch of KanBan story board cards. Each card in the story board represents something that an Associate trainee needs to learn. But first things first, you need to get some basic tools and accounts installed and configured before you can really start."
-msgstr ""
-
-#: ./doc/training-guides/bk000-preface.xml:57(para)
-msgid "<emphasis role=\"bold\">Getting Accounts and Tools:</emphasis> We can't do this without operators and developers using and creating the content. Anyone can contribute content. You will need the tools to get started. Go to the <link href=\"operator-getting-started-lab.html#getting-tools-and-accounts\">Getting Tools and Accounts</link> page."
-msgstr ""
-
-#: ./doc/training-guides/bk000-preface.xml:64(para)
-msgid "<emphasis role=\"bold\">Pick a Card:</emphasis> Once you have your tools ready to go, you can assign some work to yourself. Go to the <link href=\"https://trello.com/board/openstack-training/51d6e5fee37248fd5b003de9\">Training Trello/KanBan storyboard</link> and assign a card / user story from the Sprint Backlog to yourself. If you do not have a Trello account, no problem, just create one. Email seanrob@yahoo-inc.com and you will have access."
-msgstr ""
-
-#: ./doc/training-guides/bk000-preface.xml:72(para)
-msgid "<emphasis role=\"bold\">Create the Content:</emphasis> Each card / user story from the KanBan story board will be a separate chunk of content that you will add to the openstack-manuals repository openstack-training sub-project. <link href=\"operator-getting-started-lab.html#operator-add-training-content\"> More details on creating training content here.</link>"
-msgstr ""
-
-#: ./doc/training-guides/bk000-preface.xml:82(para)
-msgid "Here are more details on committing changes to OpenStack <link href=\"operator-getting-started-lab.html#submit-doc-bug\">fixing a documentation bug</link> , <link href=\"https://wiki.openstack.org/wiki/Gerrit_Workflow\">OpenStack Gerrit Workflow</link>, <link href=\"https://wiki.openstack.org/wiki/Documentation/HowTo\">OpenStack Documentation HowTo</link> and , <link href=\"http://git-scm.com/doc\">Git Documentation</link>"
-msgstr ""
-
-#: ./doc/training-guides/bk000-preface.xml:91(para)
-msgid "More details on the OpenStack Training project."
-msgstr ""
-
-#: ./doc/training-guides/bk000-preface.xml:95(para)
-msgid "<link href=\"https://wiki.openstack.org/wiki/Training-manuals\">OpenStack Training Wiki</link> (describes the project in detail)"
-msgstr ""
-
-#: ./doc/training-guides/bk000-preface.xml:99(para)
-msgid "<link href=\"https://blueprints.launchpad.net/openstack-manuals/+spec/training-manuals\">OpenStack Training blueprint</link>(this is the key project page)"
-msgstr ""
-
-#: ./doc/training-guides/bk000-preface.xml:104(para)
-msgid "<link href=\"http://www.meetup.com/openstack/\">Bi-Weekly SFBay Hackathon meetup page</link>(we discuss project details with all team members)"
-msgstr ""
-
-#: ./doc/training-guides/bk000-preface.xml:108(para)
-msgid "<link href=\"https://etherpad.openstack.org/sfbay-openstack\">Bi-Weekly SFBay Hackathon Etherpad</link>(meetup notes)"
-msgstr ""
-
-#: ./doc/training-guides/bk000-preface.xml:112(para)
-msgid "<link href=\"https://wiki.openstack.org/wiki/Meetings/training-manuals\">Core Training Weekly Meeting Agenda</link>(we review project action items here)"
-msgstr ""
-
-#: ./doc/training-guides/bk000-preface.xml:116(para)
-msgid "<link href=\"https://trello.com/board/openstack-training/51d6e5fee37248fd5b003de9\">Training Trello/KanBan storyboard</link>(we develop high level project action items here)"
-msgstr ""
-
-#: ./doc/training-guides/bk000-preface.xml:123(link)
-msgid "Submit a bug. Enter the summary as \"Training, \" with a few words. Be descriptive as possible in the description field. Open the tag pull-down and enter training-manuals."
-msgstr ""
-
-#: ./doc/training-guides/bk000-preface.xml:127(title)
-msgid "Building the Training Cluster"
-msgstr ""
-
-#: ./doc/training-guides/bk000-preface.xml:130(title)
-msgid "Important Terms"
-msgstr ""
-
-#: ./doc/training-guides/bk000-preface.xml:137(title)
-msgid "Building the Training Cluster, Scripted"
-msgstr ""
-
-#: ./doc/training-guides/bk000-preface.xml:144(title)
-msgid "Building the Training Cluster, Manually"
-msgstr ""
-
-#: ./doc/training-guides/card127-glance.xml:7(title)
-msgid "Install Glance"
-msgstr ""
-
-#: ./doc/training-guides/card026-network-node-architecture.xml:7(title)
-msgid "Network Node Overview"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml:8(title)
-msgid "Day 1, 09:00 to 11:00"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml:13(para)
-msgid "Training will take 1 month self paced, (2) 2 week periods with a user group meeting, or 16 hours instructor led."
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml:17(para)
-msgid "Working knowledge of Linux CLI, basic Linux SysAdmin skills (directory structure, vi, ssh, installing software)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml:19(para)
-msgid "Basic networking knowledge (Ethernet, VLAN, IP addressing)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml:20(para)
-msgid "Laptop with VirtualBox installed (highly recommended)"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml:24(title)
-msgid "Introduction Text"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml:31(title) ./doc/training-guides/module001-ch002-brief-overview.xml:7(title)
-msgid "Brief Overview"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml:38(title)
-msgid "Core Projects"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml:52(title)
-msgid "Virtual Machine Provisioning Walk-Through"
-msgstr ""
-
-#: ./doc/training-guides/card044-install-and-configure-neutron-network-node.xml:7(title)
-msgid "Neutron Installation and Configuration in Network node"
-msgstr ""
-
-#: ./doc/training-guides/card073-control-state-instance.xml:7(title) ./doc/training-guides/card073-control-state-instance.xml:8(emphasis)
-msgid "Controlling instance state"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml:10(title)
-msgid "Day 1, 15:00 to 17:00"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml:37(title)
-msgid "Block Storage CLI Commands"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml:44(title)
-msgid "Block Storage Manage Volumes"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml:51(title)
-msgid "Compute CLI Commands"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml:58(title)
-msgid "Compute Image creation"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml:65(title)
-msgid "Compute Boot Instance"
-msgstr ""
-
-#: ./doc/training-guides/bk001-ch005-associate-compute-node.xml:72(title)
-msgid "Compute Terminate Instance"
-msgstr ""
-
-#: ./doc/training-guides/bk002-ch005-operator-controller-node-lab.xml:6(title)
-msgid "Controller Node Lab"
-msgstr ""
-
-#: ./doc/training-guides/bk002-ch005-operator-controller-node-lab.xml:8(title)
-msgid "Days 2 to 4, 13:30 to 14:45, 15:00 to 16:30, 16:45 to 18:15"
-msgstr ""
-
-#: ./doc/training-guides/bk002-ch005-operator-controller-node-lab.xml:12(title)
-msgid "Control Node Lab"
-msgstr ""
-
-#: ./doc/training-guides/card128-swift.xml:7(title)
-msgid "Install Swift"
-msgstr ""
-
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/training-guides/module001-ch002-brief-overview.xml:54(None)
-msgid "@@image: 'figures/image23.jpg'; md5=6b259da45f404aa65ac2388e600f30b3"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch002-brief-overview.xml:8(para)
-msgid "OpenStack is a cloud operating system that controls large pools of compute, storage, and networking resources throughout a datacenter. It is all managed through a dashboard that gives administrators control while empowering their users to provision resources through a web interface."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch002-brief-overview.xml:13(para)
-msgid "OpenStack is a global collaboration of developers and cloud computing technologists producing the ubiquitous open source cloud computing platform for public and private clouds. The project aims to deliver solutions for all types of clouds by being"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch002-brief-overview.xml:19(para)
-msgid "simple to implement"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch002-brief-overview.xml:22(para)
-msgid "massively scalable"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch002-brief-overview.xml:25(para)
-msgid "feature rich."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch002-brief-overview.xml:28(para)
-msgid "To check out more information on OpenStack visit <link href=\"http://goo.gl/Ye9DFT\">http://goo.gl/Ye9DFT</link>"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch002-brief-overview.xml:31(guilabel)
-msgid "OpenStack Foundation:"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch002-brief-overview.xml:32(para)
-msgid "The OpenStack Foundation, established September 2012, is an independent body providing shared resources to help achieve the OpenStack Mission by protecting, empowering, and promoting OpenStack software and the community around it. This includes users, developers and the entire ecosystem. For more information visit http://goo.gl/3uvmNX."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch002-brief-overview.xml:38(guilabel)
-msgid "Who's behind OpenStack?"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch002-brief-overview.xml:39(para)
-msgid "Founded by Rackspace Hosting and NASA, OpenStack has grown to be a global software community of developers collaborating on a standard and massively scalable open source cloud operating system. The OpenStack Foundation promotes the development, distribution and adoption of the OpenStack cloud operating system. As the independent home for OpenStack, the Foundation has already attracted more than 7,000 individual members from 100 countries and 850 different organizations. It has also secured more than $10 million in funding and is ready to fulfill the OpenStack mission of becoming the ubiquitous cloud computing platform. Checkout <link href=\"http://goo.gl/BZHJKd\">http://goo.gl/BZHJKd</link>for more on the same."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch002-brief-overview.xml:51(title)
-msgid "Nebula (NASA)"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch002-brief-overview.xml:58(para)
-msgid "The goal of the OpenStack Foundation is to serve developers, users, and the entire ecosystem by providing a set of shared resources to grow the footprint of public and private OpenStack clouds, enable technology vendors targeting the platform and assist developers in producing the best cloud software in the industry."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch002-brief-overview.xml:64(guilabel)
-msgid "Who uses OpenStack?"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch002-brief-overview.xml:65(para)
-msgid "Corporations, service providers, VARS, SMBs, researchers, and global data centers looking to deploy large-scale cloud deployments for private or public clouds leveraging the support and resulting technology of a global open source community. This is just three years into OpenStack, it's new, it's yet to mature and has immense possibilities. How do I say that? All these ‘buzz words’ will fall into a properly solved jigsaw puzzle as you go through this article."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch002-brief-overview.xml:73(guilabel)
-msgid "It's Open Source:"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch002-brief-overview.xml:74(para)
-msgid "All of the code for OpenStack is freely available under the Apache 2.0 license. Anyone can run it, build on it, or submit changes back to the project. This open development model is one of the best ways to foster badly-needed cloud standards, remove the fear of proprietary lock-in for cloud customers, and create a large ecosystem that spans cloud providers."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch002-brief-overview.xml:80(guilabel)
-msgid "Who it's for:"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch002-brief-overview.xml:81(para)
-msgid "Enterprises, service providers, government and academic institutions with physical hardware that would like to build a public or private cloud."
-msgstr ""
-
-#: ./doc/training-guides/module001-ch002-brief-overview.xml:84(guilabel)
-msgid "How it's being used today:"
-msgstr ""
-
-#: ./doc/training-guides/module001-ch002-brief-overview.xml:85(para)
-msgid "Organizations like CERN, Cisco WebEx, DreamHost, eBay, The Gap, HP, MercadoLibre, NASA, PayPal, Rackspace and University of Melbourne have deployed OpenStack clouds to achieve control, business agility and cost savings without the licensing fees and terms of proprietary software. For complete user stories visit <link href=\"http://goo.gl/aF4lsL\">http://goo.gl/aF4lsL</link>, this should give you a good idea about the importance of OpenStack."
-msgstr ""
-
-#: ./doc/training-guides/bk002-operator-training-guide.xml:5(title)
-msgid "Operator Training Guide"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch020-developer-how-to-participate-day-nine-lab.xml:6(title)
-msgid "Developer How To Participate Lab Day Nine"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch020-developer-how-to-participate-day-nine-lab.xml:8(title)
-msgid "Day 9, 13:30 to 14:45, 15:00 to 16:30"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:6(title)
-msgid "Developer How To Participate Bootcamp"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:8(title)
-msgid "One Day with Focus on Contribution"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:13(para)
-msgid "Training will take 6 hours with labs and quizzes."
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:16(para)
-msgid "Some knowledge of Python and/or Perl"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:17(para)
-msgid "Editor on a self-supplied laptop with either Eclipse with pydev, vim, emacs, or pycharm"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:18(para)
-msgid "Run through the Operator Training Guide Getting Started Lab in full. This will walk each trainee through installing the accounts and tools required for the bootcamp."
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:22(title)
-msgid "Morning Classroom 10:00 to 11:15"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:23(para)
-msgid "Understanding the local tools in-depth"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:25(para)
-msgid "Pycharm editor"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:26(para)
-msgid "Git"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:27(para)
-msgid "Sourcetree"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:28(para)
-msgid "Maven"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:30(para)
-msgid "Understanding the remote tools in-depth"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:32(para)
-msgid "git-review"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:33(para)
-msgid "github"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:34(para)
-msgid "gerrit"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:35(para)
-msgid "jenkins"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:36(para)
-msgid "gearman"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:37(para)
-msgid "jeepy"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:38(para)
-msgid "zuul"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:39(para)
-msgid "launchpad"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:41(para)
-msgid "CI Pipeline Workflow Overview"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:43(para)
-msgid "Understanding the submission process in-depth"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:44(para)
-msgid "Review submission syntax"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:45(para)
-msgid "Gerrit etiquette"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:46(para)
-msgid "Resubmission"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:50(title)
-msgid "Morning Lab 11:30 to 12:30"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:54(title)
-msgid "Morning Quiz 12:30 to 12:50"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:55(para) ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:76(para)
-msgid "Online moodle test for theory, bit of syntax and terms, retake until 100%"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:56(para) ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:77(para)
-msgid "Content TBD"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:59(title)
-msgid "Afternoon Classroom 13:30 to 14:45"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:60(para)
-msgid "Understanding the CI Pipeline in-depth"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:62(para)
-msgid "Gerrit Workflow"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:63(para)
-msgid "Common jenkins tests"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:64(para)
-msgid "Reviewing and understanding zuul"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:65(para)
-msgid "Understanding jenkins output"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:66(para)
-msgid "Understanding jenkins system manual (devstack)"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:67(para)
-msgid "automated (tempest) integration tests"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:71(title)
-msgid "Afternoon Lab 15:00 to 17:00"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:75(title)
-msgid "Afternoon Quiz 17:00 to 17:20"
-msgstr ""
-
-#: ./doc/training-guides/bk002-ch008-operator-compute-node-lab.xml:6(title) ./doc/training-guides/bk002-ch008-operator-compute-node-lab.xml:12(title)
-msgid "Compute Node Lab"
-msgstr ""
-
-#: ./doc/training-guides/bk002-ch008-operator-compute-node-lab.xml:8(title)
-msgid "Days 5 to 6, 13:30 to 14:45, 15:00 to 17:00"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:7(title)
-msgid "Security in Neutron"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:8(guilabel)
-msgid "Security Groups"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:9(para)
-msgid "Security groups and security group rules allow administrators and tenants the ability to specify the type of traffic and direction (ingress/egress) that is allowed to pass through a port. A security group is a container for security group rules."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:14(para)
-msgid "When a port is created in OpenStack Networking it is associated with a security group. If a security group is not specified the port will be associated with a 'default' security group. By default this group will drop all ingress traffic and allow all egress traffic. Rules can be added to this group in order to change this behaviour."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:20(para)
-msgid "If one desires to use the OpenStack Compute security group APIs and/or have OpenStack Compute orchestrate the creation of new ports for instances on specific security groups, additional configuration is needed. To enable this, one must configure the following file /etc/nova/nova.conf and set the config option security_group_api=neutron on every node running nova-compute and nova-api. After this change is made, restart nova-api and nova-compute in order to pick up this change. After this change is made, the user will be able to use both the OpenStack Compute and OpenStack Network security group API at the same time."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:32(guilabel)
-msgid "Authentication and Authorization"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:33(para)
-msgid "OpenStack Networking uses the OpenStack Identity service (project name keystone) as the default authentication service. When OpenStack Identity is enabled, users submitting requests to the OpenStack Networking service must provide an authentication token in X-Auth-Token request header. The aforementioned token should have been obtained by authenticating with the OpenStack Identity endpoint. For more information concerning authentication with OpenStack Identity, please refer to the OpenStack Identity documentation. When OpenStack Identity is enabled, it is not mandatory to specify tenant_id for resources in create requests, as the tenant identifier will be derived from the Authentication token. Please note that the default authorization settings only allow administrative users to create resources on behalf of a different tenant. OpenStack Networking uses information received from OpenStack Identity to authorize user requests. OpenStack Networking handles two kind of authorization policies:"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:54(para)
-msgid "<emphasis role=\"bold\">Operation-based:</emphasis> policies specify access criteria for specific operations, possibly with fine-grained control over specific attributes."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:60(para)
-msgid "<emphasis role=\"bold\">Resource-based:</emphasis>whether access to specific resource might be granted or not according to the permissions configured for the resource (currently available only for the network resource). The actual authorization policies enforced in OpenStack Networking might vary from deployment to deployment."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:70(para)
-msgid "The policy engine reads entries from the policy.json file. The actual location of this file might vary from distribution to distribution. Entries can be updated while the system is running, and no service restart is required. That is to say, every time the policy file is updated, the policies will be automatically reloaded. Currently the only way of updating such policies is to edit the policy file. Please note that in this section we will use both the terms \"policy\" and \"rule\" to refer to objects which are specified in the same way in the policy file; in other words, there are no syntax differences between a rule and a policy. We will define a policy something which is matched directly from the OpenStack Networking policy engine, whereas we will define a rule as the elements of such policies which are then evaluated. For instance in create_subnet: [[\"admin_or_network_owner\"]], create_subnet is regarded as a policy, whereas admin_or_network_owner is regarded as a rule."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:88(para)
-msgid "Policies are triggered by the OpenStack Networking policy engine whenever one of them matches an OpenStack Networking API operation or a specific attribute being used in a given operation. For instance the create_subnet policy is triggered every time a POST /v2.0/subnets request is sent to the OpenStack Networking server; on the other hand create_network:shared is triggered every time the shared attribute is explicitly specified (and set to a value different from its default) in a POST /v2.0/networks request. It is also worth mentioning that policies can be also related to specific API extensions; for instance extension:provider_network:set will be triggered if the attributes defined by the Provider Network extensions are specified in an API request."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:102(para)
-msgid "An authorization policy can be composed by one or more rules. If more rules are specified, evaluation policy will be successful if any of the rules evaluates successfully; if an API operation matches multiple policies, then all the policies must evaluate successfully. Also, authorization rules are recursive. Once a rule is matched, the rule(s) can be resolved to another rule, until a terminal rule is reached."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:110(para)
-msgid "The OpenStack Networking policy engine currently defines the following kinds of terminal rules:"
-msgstr ""
-
-#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:114(para)
-msgid "<emphasis role=\"bold\">Role-based rules:</emphasis> evaluate successfully if the user submitting the request has the specified role. For instance \"role:admin\"is successful if the user submitting the request is an administrator."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:121(para)
-msgid "<emphasis role=\"bold\">Field-based rules:</emphasis> evaluate successfully if a field of the resource specified in the current request matches a specific value. For instance \"field:networks:shared=True\" is successful if the attribute shared of the network resource is set to true."
-msgstr ""
-
-#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:130(para)
-msgid "<emphasis role=\"bold\">Generic rules:</emphasis>compare an attribute in the resource with an attribute extracted from the user's security credentials and evaluates successfully if the comparison is successful. For instance \"tenant_id:%(tenant_id)s\" is successful if the tenant identifier in the resource is equal to the tenant identifier of the user submitting the request."
-msgstr ""
-
-#: ./doc/training-guides/bk003-developer-training-guide.xml:5(title)
-msgid "Developer Training Guide"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch011-developer-how-to-partipate.xml:8(title)
-msgid "Developer How To Participate"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch011-developer-how-to-partipate.xml:10(title)
-msgid "Day 5 to 9, 09:00 to 11:00, 11:15 to 12:30"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch014-developer-how-to-participate-day-six-lab.xml:6(title)
-msgid "Developer How To Participate Lab Day Six"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch014-developer-how-to-participate-day-six-lab.xml:8(title)
-msgid "Day 6, 13:30 to 14:45, 15:00 to 16:30"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch010-developer-apis-day-four-quiz.xml:6(title)
-msgid "Developer APIs in Depth Day Four Quiz"
-msgstr ""
-
-#: ./doc/training-guides/bk003-ch010-developer-apis-day-four-quiz.xml:8(title)
-msgid "Day 4, 16:40 to 17:00"
-msgstr ""
-
-#: ./doc/training-guides/card011.xml:7(title)
-msgid "Installing MySQL"
-msgstr ""
-
-#: ./doc/training-guides/bk001-bk010-associate-object-storage-node-quiz.xml:7(title)
-msgid "Day 2, 14:25 to 14:45"
-msgstr ""
-
-#: ./doc/training-guides/lab004-openstack-production.xml:7(title)
-msgid "OpenStack In Production"
-msgstr ""
-
-#: ./doc/training-guides/lab004-openstack-production.xml:8(para)
-msgid "More Content To be Added."
-msgstr ""
-
-#: ./doc/training-guides/bk002-ch012-operator-network-node-quiz.xml:6(title) ./doc/training-guides/bk001-ch008-associate-network-node-quiz.xml:6(title)
-msgid "Network Node Quiz"
-msgstr ""
-
-#: ./doc/training-guides/bk002-ch012-operator-network-node-quiz.xml:8(title)
-msgid "Days 7 to 8, 16:40 to 17:00"
-msgstr ""
-
 #. When image changes, this message will be marked fuzzy or untranslated for you.
 #. It doesn't matter what you translate it to: it's not used at all.
 #: ./doc/training-guides/lab000-virtualbox-basics.xml:206(None)
@@ -8841,36 +6228,1944 @@ msgstr ""
 msgid "Congrats, you are ready with the infrastructure for deploying OpenStack. Just make sure that you have installed Ubuntu Server on the above setup Virtual Box instances. In the next section we will go through deploying OpenStack using the above created Virtual Box instances."
 msgstr ""
 
-#: ./doc/training-guides/bk001-ch007-associate-network-node.xml:10(title)
-msgid "Day 2, 09:00 to 11:00"
+#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml:8(title)
+msgid "Day 1, 09:00 to 11:00"
 msgstr ""
 
-#: ./doc/training-guides/bk001-ch007-associate-network-node.xml:30(title)
-msgid "Network CLI Commands"
+#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml:13(para)
+msgid "Training will take 1 month self paced, (2) 2 week periods with a user group meeting, or 16 hours instructor led."
 msgstr ""
 
-#: ./doc/training-guides/bk001-ch007-associate-network-node.xml:37(title)
-msgid "Manage Networks"
+#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml:17(para)
+msgid "Working knowledge of Linux CLI, basic Linux SysAdmin skills (directory structure, vi, ssh, installing software)"
 msgstr ""
 
-#: ./doc/training-guides/bk001-ch008-associate-network-node-quiz.xml:8(title)
-msgid "Day 2, 10:40 to 11:00"
+#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml:19(para)
+msgid "Basic networking knowledge (Ethernet, VLAN, IP addressing)"
 msgstr ""
 
-#: ./doc/training-guides/bk002-ch006-operator-controller-node-quiz.xml:8(title)
-msgid "Days 2 to 4, 16:40 to 17:00"
+#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml:20(para)
+msgid "Laptop with VirtualBox installed (highly recommended)"
 msgstr ""
 
-#: ./doc/training-guides/bk003-ch007-developer-apis-day-three-lab.xml:6(title)
-msgid "Developer APIs in Depth Lab Day Three"
+#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml:24(title)
+msgid "Introduction Text"
 msgstr ""
 
-#: ./doc/training-guides/bk003-ch007-developer-apis-day-three-lab.xml:8(title)
-msgid "Day 3, 13:30 to 14:45, 15:00 to 16:30"
+#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml:31(title) ./doc/training-guides/module001-ch002-brief-overview.xml:7(title)
+msgid "Brief Overview"
 msgstr ""
 
-#: ./doc/training-guides/card070-create-floating-ips.xml:7(title)
-msgid "Create floating ip"
+#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml:38(title)
+msgid "Core Projects"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml:45(title) ./doc/training-guides/module001-ch004-openstack-architecture.xml:7(title)
+msgid "OpenStack Architecture"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch001-associate-getting-started.xml:52(title)
+msgid "Virtual Machine Provisioning Walk-Through"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/training-guides/module001-ch002-brief-overview.xml:54(None)
+msgid "@@image: 'figures/image23.jpg'; md5=6b259da45f404aa65ac2388e600f30b3"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch002-brief-overview.xml:8(para)
+msgid "OpenStack is a cloud operating system that controls large pools of compute, storage, and networking resources throughout a datacenter. It is all managed through a dashboard that gives administrators control while empowering their users to provision resources through a web interface."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch002-brief-overview.xml:13(para)
+msgid "OpenStack is a global collaboration of developers and cloud computing technologists producing the ubiquitous open source cloud computing platform for public and private clouds. The project aims to deliver solutions for all types of clouds by being"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch002-brief-overview.xml:19(para)
+msgid "simple to implement"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch002-brief-overview.xml:22(para)
+msgid "massively scalable"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch002-brief-overview.xml:25(para)
+msgid "feature rich."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch002-brief-overview.xml:28(para)
+msgid "To check out more information on OpenStack visit <link href=\"http://goo.gl/Ye9DFT\">http://goo.gl/Ye9DFT</link>"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch002-brief-overview.xml:31(guilabel)
+msgid "OpenStack Foundation:"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch002-brief-overview.xml:32(para)
+msgid "The OpenStack Foundation, established September 2012, is an independent body providing shared resources to help achieve the OpenStack Mission by protecting, empowering, and promoting OpenStack software and the community around it. This includes users, developers and the entire ecosystem. For more information visit http://goo.gl/3uvmNX."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch002-brief-overview.xml:38(guilabel)
+msgid "Who's behind OpenStack?"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch002-brief-overview.xml:39(para)
+msgid "Founded by Rackspace Hosting and NASA, OpenStack has grown to be a global software community of developers collaborating on a standard and massively scalable open source cloud operating system. The OpenStack Foundation promotes the development, distribution and adoption of the OpenStack cloud operating system. As the independent home for OpenStack, the Foundation has already attracted more than 7,000 individual members from 100 countries and 850 different organizations. It has also secured more than $10 million in funding and is ready to fulfill the OpenStack mission of becoming the ubiquitous cloud computing platform. Checkout <link href=\"http://goo.gl/BZHJKd\">http://goo.gl/BZHJKd</link>for more on the same."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch002-brief-overview.xml:51(title)
+msgid "Nebula (NASA)"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch002-brief-overview.xml:58(para)
+msgid "The goal of the OpenStack Foundation is to serve developers, users, and the entire ecosystem by providing a set of shared resources to grow the footprint of public and private OpenStack clouds, enable technology vendors targeting the platform and assist developers in producing the best cloud software in the industry."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch002-brief-overview.xml:64(guilabel)
+msgid "Who uses OpenStack?"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch002-brief-overview.xml:65(para)
+msgid "Corporations, service providers, VARS, SMBs, researchers, and global data centers looking to deploy large-scale cloud deployments for private or public clouds leveraging the support and resulting technology of a global open source community. This is just three years into OpenStack, it's new, it's yet to mature and has immense possibilities. How do I say that? All these ‘buzz words’ will fall into a properly solved jigsaw puzzle as you go through this article."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch002-brief-overview.xml:73(guilabel)
+msgid "It's Open Source:"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch002-brief-overview.xml:74(para)
+msgid "All of the code for OpenStack is freely available under the Apache 2.0 license. Anyone can run it, build on it, or submit changes back to the project. This open development model is one of the best ways to foster badly-needed cloud standards, remove the fear of proprietary lock-in for cloud customers, and create a large ecosystem that spans cloud providers."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch002-brief-overview.xml:80(guilabel)
+msgid "Who it's for:"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch002-brief-overview.xml:81(para)
+msgid "Enterprises, service providers, government and academic institutions with physical hardware that would like to build a public or private cloud."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch002-brief-overview.xml:84(guilabel)
+msgid "How it's being used today:"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch002-brief-overview.xml:85(para)
+msgid "Organizations like CERN, Cisco WebEx, DreamHost, eBay, The Gap, HP, MercadoLibre, NASA, PayPal, Rackspace and University of Melbourne have deployed OpenStack clouds to achieve control, business agility and cost savings without the licensing fees and terms of proprietary software. For complete user stories visit <link href=\"http://goo.gl/aF4lsL\">http://goo.gl/aF4lsL</link>, this should give you a good idea about the importance of OpenStack."
+msgstr ""
+
+#: ./doc/training-guides/card041-neutron.xml:7(title) ./doc/training-guides/card041-neutron.xml:16(emphasis)
+msgid "Install Neutron"
+msgstr ""
+
+#: ./doc/training-guides/card041-neutron.xml:9(emphasis) ./doc/training-guides/lab003-compute-node.xml:140(para)
+msgid "Install Open vSwitch"
+msgstr ""
+
+#: ./doc/training-guides/card041-neutron.xml:10(para)
+msgid "Open vSwitch is one of many options, but for now we will stick with OVS."
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:11(title)
+msgid "A Bit More On Swift"
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:12(guilabel)
+msgid "Containers and Objects"
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:13(para)
+msgid "A container is a storage compartment for your data and provides a way for you to organize your data. You can think of a container as a folder in Windows or a directory in UNIX. The primary difference between a container and these other file system concepts is that containers cannot be nested. You can, however, create an unlimited number of containers within your account. Data must be stored in a container so you must have at least one container defined in your account prior to uploading data."
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:23(para)
+msgid "The only restrictions on container names is that they cannot contain a forward slash (/) or an ascii null (%00) and must be less than 257 bytes in length. Please note that the length restriction applies to the name after it has been URL encoded. For example, a container name of Course Docs would be URL encoded as Course%20Docs and therefore be 13 bytes in length rather than the expected 11."
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:31(para)
+msgid "An object is the basic storage entity and any optional metadata that represents the files you store in the OpenStack Object Storage system. When you upload data to OpenStack Object Storage, the data is stored as-is (no compression or encryption) and consists of a location (container), the object's name, and any metadata consisting of key/value pairs. For instance, you may chose to store a backup of your digital photos and organize them into albums. In this case, each object could be tagged with metadata such as Album : Caribbean Cruise or Album : Aspen Ski Trip."
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:42(para)
+msgid "The only restriction on object names is that they must be less than 1024 bytes in length after URL encoding. For example, an object name of C++final(v2).txt should be URL encoded as C%2B%2Bfinal%28v2%29.txt and therefore be 24 bytes in length rather than the expected 16."
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:47(para)
+msgid "The maximum allowable size for a storage object upon upload is 5GB and the minimum is zero bytes. You can use the built-in large object support and the swift utility to retrieve objects larger than 5GB."
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:51(para)
+msgid "For metadata, you should not exceed 90 individual key/value pairs for any one object and the total byte length of all key/value pairs should not exceed 4KB (4096bytes)."
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:55(guilabel)
+msgid "Language-Specific API Bindings"
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:57(para)
+msgid "A set of supported API bindings in several popular languages are available from the Rackspace Cloud Files product, which uses OpenStack Object Storage code for its implementation. These bindings provide a layer of abstraction on top of the base REST API, allowing programmers to work with a container and object model instead of working directly with HTTP requests and responses. These bindings are free (as in beer and as in speech) to download, use, and modify. They are all licensed under the MIT License as described in the COPYING file packaged with each binding. If you do make any improvements to an API, you are encouraged (but not required) to submit those changes back to us."
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:70(para)
+msgid "The API bindings for Rackspace Cloud Files are hosted at<link href=\"http://github.com/rackspace\"/><link href=\"http://github.com/rackspace\">http://github.com/rackspace</link>. Feel free to coordinate your changes through github or, if you prefer, send your changes to cloudfiles@rackspacecloud.com. Just make sure to indicate which language and version you modified and send a unified diff."
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:79(para)
+msgid "Each binding includes its own documentation (either HTML, PDF, or CHM). They also include code snippets and examples to help you get started. The currently supported API binding for OpenStack Object Storage are:"
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:85(para)
+msgid "PHP (requires 5.x and the modules: cURL, FileInfo, mbstring)"
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:89(para)
+msgid "Python (requires 2.4 or newer)"
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:92(para)
+msgid "Java (requires JRE v1.5 or newer)"
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:95(para)
+msgid "C#/.NET (requires .NET Framework v3.5)"
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:98(para)
+msgid "Ruby (requires 1.8 or newer and mime-tools module)"
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:102(para)
+msgid "There are no other supported language-specific bindings at this time. You are welcome to create your own language API bindings and we can help answer any questions during development, host your code if you like, and give you full credit for your work."
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:107(guilabel)
+msgid "Proxy Server"
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:108(para)
+msgid "The Proxy Server is responsible for tying together the rest of the OpenStack Object Storage architecture. For each request, it will look up the location of the account, container, or object in the ring (see below) and route the request accordingly. The public API is also exposed through the Proxy Server."
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:114(para)
+msgid "A large number of failures are also handled in the Proxy Server. For example, if a server is unavailable for an object PUT, it will ask the ring for a hand-off server and route there instead."
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:118(para)
+msgid "When objects are streamed to or from an object server, they are streamed directly through the proxy server to or from the user – the proxy server does not spool them."
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:122(para)
+msgid "You can use a proxy server with account management enabled by configuring it in the proxy server configuration file."
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:125(guilabel)
+msgid "Object Server"
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:126(para)
+msgid "The Object Server is a very simple blob storage server that can store, retrieve and delete objects stored on local devices. Objects are stored as binary files on the filesystem with metadata stored in the file’s extended attributes (xattrs). This requires that the underlying filesystem choice for object servers support xattrs on files. Some filesystems, like ext3, have xattrs turned off by default."
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:134(para)
+msgid "Each object is stored using a path derived from the object name’s hash and the operation’s timestamp. Last write always wins, and ensures that the latest object version will be served. A deletion is also treated as a version of the file (a 0 byte file ending with “.ts”, which stands for tombstone). This ensures that deleted files are replicated correctly and older versions don’t magically reappear due to failure scenarios."
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:143(guilabel)
+msgid "Container Server"
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:144(para)
+msgid "The Container Server’s primary job is to handle listings of objects. It does not know where those objects are, just what objects are in a specific container. The listings are stored as SQLite database files, and replicated across the cluster similar to how objects are. Statistics are also tracked that include the total number of objects, and total storage usage for that container."
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:152(guilabel)
+msgid "Account Server"
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:153(para)
+msgid "The Account Server is very similar to the Container Server, excepting that it is responsible for listings of containers rather than objects."
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:156(guilabel)
+msgid "Replication"
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:157(para)
+msgid "Replication is designed to keep the system in a consistent state in the face of temporary error conditions like network outages or drive failures."
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:161(para)
+msgid "The replication processes compare local data with each remote copy to ensure they all contain the latest version. Object replication uses a hash list to quickly compare subsections of each partition, and container and account replication use a combination of hashes and shared high water marks."
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:167(para)
+msgid "Replication updates are push based. For object replication, updating is just a matter of rsyncing files to the peer. Account and container replication push missing records over HTTP or rsync whole database files."
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:172(para)
+msgid "The replicator also ensures that data is removed from the system. When an item (object, container, or account) is deleted, a tombstone is set as the latest version of the item. The replicator will see the tombstone and ensure that the item is removed from the entire system."
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:178(para)
+msgid "To separate the cluster-internal replication traffic from client traffic, separate replication servers can be used. These replication servers are based on the standard storage servers, but they listen on the replication IP and only respond to REPLICATE requests. Storage servers can serve REPLICATE requests, so an operator can transition to using a separate replication network with no cluster downtime."
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:186(para)
+msgid "Replication IP and port information is stored in the ring on a per-node basis. These parameters will be used if they are present, but they are not required. If this information does not exist or is empty for a particular node, the node's standard IP and port will be used for replication."
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:192(guilabel)
+msgid "Updaters"
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:193(para)
+msgid "There are times when container or account data can not be immediately updated. This usually occurs during failure scenarios or periods of high load. If an update fails, the update is queued locally on the file system, and the updater will process the failed updates. This is where an eventual consistency window will most likely come in to play. For example, suppose a container server is under load and a new object is put in to the system. The object will be immediately available for reads as soon as the proxy server responds to the client with success. However, the container server did not update the object listing, and so the update would be queued for a later update. Container listings, therefore, may not immediately contain the object."
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:208(para)
+msgid "In practice, the consistency window is only as large as the frequency at which the updater runs and may not even be noticed as the proxy server will route listing requests to the first container server which responds. The server under load may not be the one that serves subsequent listing requests – one of the other two replicas may handle the listing."
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:215(guilabel)
+msgid "Auditors"
+msgstr ""
+
+#: ./doc/training-guides/module003-ch006-more-concepts.xml:216(para)
+msgid "Auditors crawl the local server checking the integrity of the objects, containers, and accounts. If corruption is found (in the case of bit rot, for example), the file is quarantined, and replication will replace the bad file from another replica. If other errors are found they are logged. For example, an object’s listing cannot be found on any container server it should be."
+msgstr ""
+
+#: ./doc/training-guides/card007-core-overview.xml:7(title)
+msgid "Core Project Overview"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:8(title)
+msgid "Day 1, 14:25 to 14:45"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:10(title)
+msgid "Associate Training Guide, Controller Node Quiz Questions"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:15(title)
+msgid "When managing images for OpenStack you can complete all those tasks with the OpenStack dashboard. (True or False)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:20(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:36(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:101(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:118(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:159(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:174(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:238(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:301(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:91(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:106(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:121(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:160(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:175(para)
+msgid "True"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:23(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:39(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:104(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:121(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:162(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:177(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:241(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:304(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:94(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:109(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:124(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:163(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:178(para)
+msgid "False"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:31(title)
+msgid "When setting up access and security, SSH credentials (keypairs) must be injected into images after they are launched with a script. (True or False)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:47(title)
+msgid "You can track monthly costs with metrics like: (choose all that apply)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:51(para)
+msgid "VCPU"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:54(para)
+msgid "QoS"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:57(para)
+msgid "Uptime"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:60(para)
+msgid "Disks"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:63(para)
+msgid "RAM"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:71(title)
+msgid "The following OpenStack command-line clients are available. (choose all that apply)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:75(para)
+msgid "python-keystoneclient"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:78(para)
+msgid "python-hypervisorclient"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:81(para)
+msgid "python-imageclient"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:84(para)
+msgid "python-cinderclient"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:87(para)
+msgid "python-novaclient"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:95(title)
+msgid "To install a client package"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:96(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:113(para)
+msgid "Run this command: <placeholder-1/><placeholder-2/>"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:112(title)
+msgid "To list images"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:129(title)
+msgid "When troubleshooting image creation you will need to look at which of the following log files for errors? (choose all that apply)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:134(para)
+msgid "Examine the /var/log/nova-api.log"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:137(para)
+msgid "Examine the /var/log/nova-compute.log"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:140(para)
+msgid "Examine the /var/log/nova-error.log"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:143(para)
+msgid "Examine the /var/log/nova-status.log"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:146(para)
+msgid "Examine the /var/log/nova-image.log"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:154(title)
+msgid "To generate a keypair use the following command syntax: $ nova keypair-add --pub_key ~/.ssh/id_rsa.pub KEY_NAME"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:170(title)
+msgid "When you want to launch an instance you can only do that from an image. (True or False)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:185(title)
+msgid "An instance has a Private IP address which has the following properties? (choose all that apply)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:189(para)
+msgid "Used for communication between instances"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:192(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:193(para)
+msgid "VMware vShpere 4.1, update 1 or greater"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:195(para)
+msgid "Stays the same, even after reboots"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:198(para)
+msgid "Stays allocated, even if you terminate the instance"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:201(para)
+msgid "To see the status of the Private IP addresses you use the following command: $ nova floating-ip-pool-list"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:210(title)
+msgid "To start and stop and instance you can use the following options: (choose all that apply)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:214(para)
+msgid "Pause/Un-pause"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:217(para)
+msgid "Suspend/Resume"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:220(para)
+msgid "Reboot"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:223(para)
+msgid "Evacuate"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:226(para)
+msgid "Shutdown/Restart"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:234(title)
+msgid "To create a network in OpenStack use the following command: $ neutron net-create net1 (True or False)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:249(title)
+msgid "Identity Service provides the following functions: (choose all that apply)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:253(para)
+msgid "Group policy objects"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:256(para)
+msgid "Message queuing"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:262(para)
+msgid "Publishing"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:265(para)
+msgid "Service catalog"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:273(title)
+msgid "The AMQP supports the following messaging bus options: (choose all that apply)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:277(para)
+msgid "ZeroMQ"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:283(para)
+msgid "Tibco Rendezvous"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:286(para)
+msgid "IBM WebSphere Message Broker"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:289(para)
+msgid "Qpid"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:297(title)
+msgid "OpenStack uses the term tenant but in earlier versions it used the term customer. (True or False)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:314(title)
+msgid "Associate Training Guide, Controller Node Quiz Answers"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:318(para)
+msgid "B (False) - you can manage images through only the glance and nova clients or the Image Service and Compute APIs."
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:322(para)
+msgid "B (False) - Keypairs are SSH credentials that are injected into images when they are launched. For this to work, the image must contain the cloud-init package"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:326(para)
+msgid "A, C, D, E - You can track costs per month by showing metrics like number of VCPUs, disks, RAM, and uptime of all your instances"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:330(para)
+msgid "A, D, E - The following command-line clients are available for the respective services' APIs: cinder(python-cinderclient) Client for the Block Storage service API. Use to create and manage volumes. glance(python-glanceclient) Client for the Image Service API. Use to create and manage images. keystone(python-keystoneclient) Client for the Identity Service API. Use to create and manage users, tenants, roles, endpoints, and credentials. nova(python-novaclient) Client for the Compute API and its extensions. Use to create and manage images, instances, and flavors. neutron(python-neutronclient) Client for the Networking API. Use to configure networks for guest servers. This client was previously known as neutron. swift(python-swiftclient) Client for the Object Storage API. Use to gather statistics, list items, update metadata, upload, download and delete files stored by the object storage service. Provides access to a swift installation for ad hoc processing. heat(python-heatclient)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:346(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:349(para) ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:367(para)
+msgid "A (True)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:352(para)
+msgid "A, B"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:355(para)
+msgid "B (False) - $ nova keypair-add KEY_NAME &gt; MY_KEY.pem"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:358(para)
+msgid "B (False) - you can launch and instance from an image or a volume"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:361(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:222(para)
+msgid "A, B, C"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:364(para)
+msgid "A, B, C, D"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:370(para)
+msgid "C, E"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:373(para)
+msgid "A, B, E"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch004-associate-controller-node-quiz.xml:376(para)
+msgid "B (False) - Because the term project was used instead of tenant in earlier versions of OpenStack Compute, some command-line tools use --project_id instead of --tenant-id or --os-tenant-id to refer to a tenant ID."
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch004-developer-apis-in-depth.xml:8(title)
+msgid "Developer APIs in Depth"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch009-developer-apis-day-four-lab.xml:6(title)
+msgid "Developer How To Participate Lab Day Four"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch009-developer-apis-day-four-lab.xml:8(title)
+msgid "Day 4, 13:30 to 14:45, 15:00 to 16:30"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch021-developer-how-to-participate-day-nine-quiz.xml:6(title)
+msgid "Developer How To Participate Day Nine Quiz"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch021-developer-how-to-participate-day-nine-quiz.xml:8(title) ./doc/training-guides/bk002-ch015-operator-object-storage-node-quiz.xml:8(title)
+msgid "Day 9, 16:40 to 17:00"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:6(title)
+msgid "Developer How To Participate Bootcamp"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:8(title)
+msgid "One Day with Focus on Contribution"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:13(para)
+msgid "Training will take 6 hours with labs and quizzes."
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:16(para)
+msgid "Some knowledge of Python and/or Perl"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:17(para)
+msgid "Editor on a self-supplied laptop with either Eclipse with pydev, vim, emacs, or pycharm"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:18(para)
+msgid "Run through the Operator Training Guide Getting Started Lab in full. This will walk each trainee through installing the accounts and tools required for the bootcamp."
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:22(title)
+msgid "Morning Classroom 10:00 to 11:15"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:23(para)
+msgid "Understanding the local tools in-depth"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:25(para)
+msgid "Pycharm editor"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:26(para)
+msgid "Git"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:27(para)
+msgid "Sourcetree"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:28(para)
+msgid "Maven"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:30(para)
+msgid "Understanding the remote tools in-depth"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:32(para)
+msgid "git-review"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:33(para)
+msgid "github"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:34(para)
+msgid "gerrit"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:35(para)
+msgid "jenkins"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:36(para)
+msgid "gearman"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:37(para)
+msgid "jeepy"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:38(para)
+msgid "zuul"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:39(para)
+msgid "launchpad"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:41(para)
+msgid "CI Pipeline Workflow Overview"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:43(para)
+msgid "Understanding the submission process in-depth"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:44(para)
+msgid "Review submission syntax"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:45(para)
+msgid "Gerrit etiquette"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:46(para)
+msgid "Resubmission"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:50(title)
+msgid "Morning Lab 11:30 to 12:30"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:54(title)
+msgid "Morning Quiz 12:30 to 12:50"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:55(para) ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:76(para)
+msgid "Online moodle test for theory, bit of syntax and terms, retake until 100%"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:56(para) ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:77(para)
+msgid "Content TBD"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:59(title)
+msgid "Afternoon Classroom 13:30 to 14:45"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:60(para)
+msgid "Understanding the CI Pipeline in-depth"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:62(para)
+msgid "Gerrit Workflow"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:63(para)
+msgid "Common jenkins tests"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:64(para)
+msgid "Reviewing and understanding zuul"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:65(para)
+msgid "Understanding jenkins output"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:66(para)
+msgid "Understanding jenkins system manual (devstack)"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:67(para)
+msgid "automated (tempest) integration tests"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:71(title)
+msgid "Afternoon Lab 15:00 to 17:00"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch023-developer-how-to-participate-bootcamp.xml:75(title)
+msgid "Afternoon Quiz 17:00 to 17:20"
+msgstr ""
+
+#: ./doc/training-guides/card072-cinder-attach-volume.xml:7(title)
+msgid "Attaching volumes to an instance"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:11(None)
+msgid "@@image: 'figures/image04.png'; md5=dd0c42b457e2b17fd94e4f62c16b9c37"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:47(None)
+msgid "@@image: 'figures/image24.png'; md5=aea2956c5e4f01e06171d8d5e1de49b5"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:149(None) ./doc/training-guides/module001-ch008-queues-messaging.xml:207(None)
+msgid "@@image: 'figures/image20.png'; md5=c2cab17b6ee560943403c1d998d7a9d7"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:184(None)
+msgid "@@image: 'figures/image28.png'; md5=c813069a23d72a7a3f519d896270a62a"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:6(title) ./doc/training-guides/bk001-ch003-associate-controller-node.xml:28(title)
+msgid "OpenStack Messaging and Queues"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:8(title)
+msgid "Messaging in OpenStack"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:15(para)
+msgid "AMQP is the messaging technology chosen by the OpenStack cloud. The AMQP broker, either RabbitMQ or Qpid, sits between any two Nova components and allows them to communicate in a loosely coupled fashion. More precisely, Nova components (the compute fabric of OpenStack) use Remote Procedure Calls (RPC hereinafter) to communicate to one another; however such a paradigm is built atop the publish/subscribe paradigm so that the following benefits can be achieved:"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:25(para)
+msgid "Decoupling between client and servant (such as the client does not need to know where the servant reference is)."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:30(para)
+msgid "Full a-synchronism between client and servant (such as the client does not need the servant to run at the same time of the remote call)."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:35(para)
+msgid "Random balancing of remote calls (such as if more servants are up and running, one-way calls are transparently dispatched to the first available servant)."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:40(para)
+msgid "Nova uses direct, fanout, and topic-based exchanges. The architecture looks like the one depicted in the figure below:"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:44(title)
+msgid "AMQP"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:51(para)
+msgid "Nova implements RPC (both request+response, and one-way, respectively nicknamed ‘rpc.call’ and ‘rpc.cast’) over AMQP by providing an adapter class which take cares of marshaling and un-marshaling of messages into function calls. Each Nova service, such as Compute, Scheduler, and so on, creates two queues at the initialization time, one which accepts messages with routing keys ‘NODE-TYPE.NODE-ID’, for example, compute.hostname, and another, which accepts messages with routing keys as generic ‘NODE-TYPE’, for example compute. The former is used specifically when Nova-API needs to redirect commands to a specific node like ‘euca-terminate instance’. In this case, only the compute node whose host’s hypervisor is running the virtual machine can kill the instance. The API acts as a consumer when RPC calls are request/response, otherwise is acts as publisher only."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:64(guilabel)
+msgid "Nova RPC Mappings"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:65(para)
+msgid "The figure below shows the internals of a message broker node (referred to as a RabbitMQ node in the diagrams) when a single instance is deployed and shared in an OpenStack cloud. Every component within Nova connects to the message broker and, depending on its personality, such as a compute node or a network node, may use the queue either as an Invoker (such as API or Scheduler) or a Worker (such as Compute or Network). Invokers and Workers do not actually exist in the Nova object model, but in this example they are used as an abstraction for the sake of clarity. An Invoker is a component that sends messages in the queuing system using <placeholder-1/> and <placeholder-2/>. A worker is a component that receives messages from the queuing system and replies accordingly to rcp.call operations."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:78(para)
+msgid "Figure 2 shows the following internal elements:"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:81(para)
+msgid "<emphasis role=\"bold\">Topic Publisher:</emphasis> A Topic Publisher comes to life when an rpc.call or an rpc.cast operation is executed; this object is instantiated and used to push a message to the queuing system. Every publisher connects always to the same topic-based exchange; its life-cycle is limited to the message delivery."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:89(para)
+msgid "<emphasis role=\"bold\">Direct Consumer:</emphasis> A Direct Consumer comes to life if (an only if) a rpc.call operation is executed; this object is instantiated and used to receive a response message from the queuing system; Every consumer connects to a unique direct-based exchange via a unique exclusive queue; its life-cycle is limited to the message delivery; the exchange and queue identifiers are determined by a UUID generator, and are marshaled in the message sent by the Topic Publisher (only rpc.call operations)."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:100(para)
+msgid "<emphasis role=\"bold\">Topic Consumer:</emphasis> A Topic Consumer comes to life as soon as a Worker is instantiated and exists throughout its life-cycle; this object is used to receive messages from the queue and it invokes the appropriate action as defined by the Worker role. A Topic Consumer connects to the same topic-based exchange either via a shared queue or via a unique exclusive queue. Every Worker has two topic consumers, one that is addressed only during rpc.cast operations (and it connects to a shared queue whose exchange key is ‘topic’) and the other that is addressed only during rpc.call operations (and it connects to a unique queue whose exchange key is ‘topic.host’)."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:114(para)
+msgid "<emphasis role=\"bold\">Direct Publisher:</emphasis> A Direct Publisher comes to life only during rpc.call operations and it is instantiated to return the message required by the request/response operation. The object connects to a direct-based exchange whose identity is dictated by the incoming message."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:122(para)
+msgid "<emphasis role=\"bold\">Topic Exchange:</emphasis> The Exchange is a routing table that exists in the context of a virtual host (the multi-tenancy mechanism provided by Qpid or RabbitMQ); its type (such as topic vs. direct) determines the routing policy; a message broker node will have only one topic-based exchange for every topic in Nova."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:130(para)
+msgid "<emphasis role=\"bold\">Direct Exchange:</emphasis> This is a routing table that is created during rpc.call operations; there are many instances of this kind of exchange throughout the life-cycle of a message broker node, one for each rpc.call invoked."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:137(para)
+msgid "<emphasis role=\"bold\">Queue Element:</emphasis> A Queue is a message bucket. Messages are kept in the queue until a Consumer (either Topic or Direct Consumer) connects to the queue and fetch it. Queues can be shared or can be exclusive. Queues whose routing key is ‘topic’ are shared amongst Workers of the same personality."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:153(guilabel)
+msgid "RPC Calls"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:154(para)
+msgid "The diagram below shows the message flow during an rp.call operation:"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:158(para)
+msgid "A Topic Publisher is instantiated to send the message request to the queuing system; immediately before the publishing operation. A Direct Consumer is instantiated to wait for the response message."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:164(para)
+msgid "Once the message is dispatched by the exchange, it is fetched by the Topic Consumer dictated by the routing key (such as ‘topic.host’) and passed to the Worker in charge of the task."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:170(para)
+msgid "Once the task is completed, a Direct Publisher is allocated to send the response message to the queuing system."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:175(para)
+msgid "Once the message is dispatched by the exchange, it is fetched by the Direct Consumer dictated by the routing key (such as ‘msg_id’) and passed to the Invoker."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:188(guilabel)
+msgid "RPC Casts"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:189(para)
+msgid "The diagram below the message flow during an rp.cast operation:"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:193(para)
+msgid "A Topic Publisher is instantiated to send the message request to the queuing system."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:197(para)
+msgid "Once the message is dispatched by the exchange, it is fetched by the Topic Consumer dictated by the routing key (such as ‘topic’) and passed to the Worker in charge of the task."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:211(guilabel)
+msgid "AMQP Broker Load"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:212(para)
+msgid "At any given time the load of a message broker node running either Qpid or RabbitMQ is a function of the following parameters:"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:217(para)
+msgid "Throughput of API calls: the number of API calls (more precisely rpc.call ops) being served by the OpenStack cloud dictates the number of direct-based exchanges, related queues and direct consumers connected to them."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:223(para)
+msgid "Number of Workers: there is one queue shared amongst workers with the same personality; however there are as many exclusive queues as the number of workers; the number of workers dictates also the number of routing keys within the topic-based exchange, which is shared amongst all workers."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:231(para)
+msgid "The figure below shows the status of a RabbitMQ node after Nova components’ bootstrap in a test environment. Exchanges and queues being created by Nova components are:"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:236(para)
+msgid "Exchanges"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:241(para)
+msgid "nova (topic exchange)"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:246(para)
+msgid "Queues"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:251(para)
+msgid "compute.phantom (phantom is the hostname)"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:254(para)
+msgid "compute"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:257(para)
+msgid "network.phantom (phantom is the hostname)"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:260(para)
+msgid "network"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:263(para)
+msgid "scheduler.phantom (phantom is the hostname)"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:266(para)
+msgid "scheduler"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:269(guilabel)
+msgid "RabbitMQ Gotchas"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:270(para)
+msgid "Nova uses Kombu to connect to the RabbitMQ environment. Kombu is a Python library that in turn uses AMQPLib, a library that implements the standard AMQP 0.8 at the time of writing. When using Kombu, Invokers and Workers need the following parameters in order to instantiate a Connection object that connects to the RabbitMQ server (please note that most of the following material can be also found in the Kombu documentation; it has been summarized and revised here for the sake of clarity):"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:280(para)
+msgid "<emphasis role=\"bold\">Hostname:</emphasis> The hostname to the AMQP server."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:284(para)
+msgid "<emphasis role=\"bold\">Userid:</emphasis> A valid username used to authenticate to the server."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:288(para)
+msgid "<emphasis role=\"bold\">Password:</emphasis> The password used to authenticate to the server."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:292(para)
+msgid "<emphasis role=\"bold\">Virtual_host:</emphasis> The name of the virtual host to work with. This virtual host must exist on the server, and the user must have access to it. Default is “/”."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:298(para)
+msgid "<emphasis role=\"bold\">Port:</emphasis> The port of the AMQP server. Default is 5672 (amqp)."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:302(para)
+msgid "The following parameters are default:"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:305(para)
+msgid "<emphasis role=\"bold\">Insist:</emphasis> Insist on connecting to a server. In a configuration with multiple load-sharing servers, the Insist option tells the server that the client is insisting on a connection to the specified server. Default is False."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:312(para)
+msgid "<emphasis role=\"bold\">Connect_timeout:</emphasis> The timeout in seconds before the client gives up connecting to the server. The default is no timeout."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:317(para)
+msgid "<emphasis role=\"bold\">SSL:</emphasis> Use SSL to connect to the server. The default is False."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:321(para)
+msgid "More precisely consumers need the following parameters:"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:324(para)
+msgid "<emphasis role=\"bold\">Connection:</emphasis> The above mentioned Connection object."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:328(para)
+msgid "<emphasis role=\"bold\">Queue:</emphasis> Name of the queue."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:332(para)
+msgid "<emphasis role=\"bold\">Exchange:</emphasis> Name of the exchange the queue binds to."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:336(para)
+msgid "<emphasis role=\"bold\">Routing_key:</emphasis> The interpretation of the routing key depends on the value of the exchange_type attribute."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:343(para)
+msgid "<emphasis role=\"bold\">Direct exchange:</emphasis> If the routing key property of the message and the routing_key attribute of the queue are identical, then the message is forwarded to the queue."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:349(para)
+msgid "<emphasis role=\"bold\">Fanout exchange:</emphasis> Messages are forwarded to the queues bound the exchange, even if the binding does not have a key."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:354(para)
+msgid "<emphasis role=\"bold\">Topic exchange:</emphasis> If the routing key property of the message matches the routing key of the key according to a primitive pattern matching scheme, then the message is forwarded to the queue. The message routing key then consists of words separated by dots (”.”, like domain names), and two special characters are available; star (“”) and hash (“#”). The star matches any word, and the hash matches zero or more words. For example ”.stock.#” matches the routing keys “usd.stock” and “eur.stock.db” but not “stock.nasdaq”."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:368(para)
+msgid "<emphasis role=\"bold\">Durable:</emphasis> This flag determines the durability of both exchanges and queues; durable exchanges and queues remain active when a RabbitMQ server restarts. Non-durable exchanges/queues (transient exchanges/queues) are purged when a server restarts. It is worth noting that AMQP specifies that durable queues cannot bind to transient exchanges. Default is True."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:377(para)
+msgid "<emphasis role=\"bold\">Auto_delete:</emphasis> If set, the exchange is deleted when all queues have finished using it. Default is False."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:382(para)
+msgid "<emphasis role=\"bold\">Exclusive:</emphasis> Exclusive queues (such as non-shared) may only be consumed from by the current connection. When exclusive is on, this also implies auto_delete. Default is False."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:388(para)
+msgid "<emphasis role=\"bold\">Exchange_type:</emphasis> AMQP defines several default exchange types (routing algorithms) that covers most of the common messaging use cases."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:393(para)
+msgid "<emphasis role=\"bold\">Auto_ack:</emphasis> Acknowledgement is handled automatically once messages are received. By default auto_ack is set to False, and the receiver is required to manually handle acknowledgment."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:399(para)
+msgid "<emphasis role=\"bold\">No_ack:</emphasis> It disables acknowledgement on the server-side. This is different from auto_ack in that acknowledgement is turned off altogether. This functionality increases performance but at the cost of reliability. Messages can get lost if a client dies before it can deliver them to the application."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:407(para)
+msgid "<emphasis role=\"bold\">Auto_declare:</emphasis> If this is True and the exchange name is set, the exchange will be automatically declared at instantiation. Auto declare is on by default. Publishers specify most the parameters of consumers (they do not specify a queue name), but they can also specify the following:"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:415(para)
+msgid "<emphasis role=\"bold\">Delivery_mode:</emphasis> The default delivery mode used for messages. The value is an integer. The following delivery modes are supported by RabbitMQ:"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:422(para)
+msgid "<emphasis role=\"bold\">1 or “transient”:</emphasis> The message is transient. Which means it is stored in memory only, and is lost if the server dies or restarts."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:427(para)
+msgid "<emphasis role=\"bold\">2 or “persistent”:</emphasis> The message is persistent. Which means the message is stored both in-memory, and on disk, and therefore preserved if the server dies or restarts."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch008-queues-messaging.xml:433(para)
+msgid "The default value is 2 (persistent). During a send operation, Publishers can override the delivery mode of messages so that, for example, transient messages can be sent over a durable queue."
+msgstr ""
+
+#: ./doc/training-guides/bk002-ch005-operator-controller-node-lab.xml:6(title)
+msgid "Controller Node Lab"
+msgstr ""
+
+#: ./doc/training-guides/bk002-ch005-operator-controller-node-lab.xml:8(title)
+msgid "Days 2 to 4, 13:30 to 14:45, 15:00 to 16:30, 16:45 to 18:15"
+msgstr ""
+
+#: ./doc/training-guides/bk002-ch005-operator-controller-node-lab.xml:12(title)
+msgid "Control Node Lab"
+msgstr ""
+
+#: ./doc/training-guides/lab003-compute-node.xml:25(para) ./doc/training-guides/lab002-network-node.xml:22(para)
+msgid "<emphasis role=\"bold\">Vboxnet0</emphasis>, <emphasis role=\"bold\">Vboxnet1</emphasis>, <emphasis role=\"bold\">Vboxnet2</emphasis> - are virtual networks setup up by virtual box with your host machine. This is the way your host can communicate with the virtual machines. These networks are in turn used by virtual box VM’s for OpenStack networks, so that OpenStack’s services can communicate with each other."
+msgstr ""
+
+#: ./doc/training-guides/lab003-compute-node.xml:33(para)
+msgid "Start your Controller Node (the one you setup in the previous section)."
+msgstr ""
+
+#: ./doc/training-guides/lab003-compute-node.xml:35(emphasis) ./doc/training-guides/lab002-network-node.xml:29(emphasis)
+msgid "Preparing Ubuntu 12.04"
+msgstr ""
+
+#: ./doc/training-guides/lab003-compute-node.xml:59(para) ./doc/training-guides/lab002-network-node.xml:53(para)
+msgid "Install NTP and other services:"
+msgstr ""
+
+#: ./doc/training-guides/lab003-compute-node.xml:65(para) ./doc/training-guides/lab002-network-node.xml:59(para)
+msgid "Configure NTP Server to Controller Node:"
+msgstr ""
+
+#: ./doc/training-guides/lab003-compute-node.xml:74(para)
+msgid "Enable IP Forwarding by adding the following to <filename>/etc/sysctl.conf</filename>"
+msgstr ""
+
+#: ./doc/training-guides/lab003-compute-node.xml:82(para) ./doc/training-guides/lab002-network-node.xml:76(para)
+msgid "Run the following commands:"
+msgstr ""
+
+#: ./doc/training-guides/lab003-compute-node.xml:91(emphasis) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:190(para)
+msgid "KVM"
+msgstr ""
+
+#: ./doc/training-guides/lab003-compute-node.xml:94(para)
+msgid "Install KVM:"
+msgstr ""
+
+#: ./doc/training-guides/lab003-compute-node.xml:100(para)
+msgid "Edit <filename>/etc/libvirt/qemu.conf</filename>"
+msgstr ""
+
+#: ./doc/training-guides/lab003-compute-node.xml:109(para)
+msgid "Delete Default Virtual Bridge"
+msgstr ""
+
+#: ./doc/training-guides/lab003-compute-node.xml:116(para)
+msgid "To Enable Live Migration Edit <filename>/etc/libvirt/libvirtd.conf</filename>"
+msgstr ""
+
+#: ./doc/training-guides/lab003-compute-node.xml:122(para)
+msgid "Edit <filename>/etc/init/libvirt-bin.conf</filename>"
+msgstr ""
+
+#: ./doc/training-guides/lab003-compute-node.xml:126(para)
+msgid "Edit <filename>/etc/default/libvirt-bin</filename>"
+msgstr ""
+
+#: ./doc/training-guides/lab003-compute-node.xml:130(para)
+msgid "Restart libvirt"
+msgstr ""
+
+#: ./doc/training-guides/lab003-compute-node.xml:137(emphasis)
+msgid "Neutron and OVS"
+msgstr ""
+
+#: ./doc/training-guides/lab003-compute-node.xml:144(para)
+msgid "Create bridges:"
+msgstr ""
+
+#: ./doc/training-guides/lab003-compute-node.xml:151(para)
+msgid "Install the Neutron Open vSwitch agent:"
+msgstr ""
+
+#: ./doc/training-guides/lab003-compute-node.xml:157(para)
+msgid "Edit <filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename>"
+msgstr ""
+
+#: ./doc/training-guides/lab003-compute-node.xml:178(para)
+msgid "Edit <filename>/etc/neutron/neutron.conf</filename>"
+msgstr ""
+
+#: ./doc/training-guides/lab003-compute-node.xml:193(para)
+msgid "Restart all the services:"
+msgstr ""
+
+#: ./doc/training-guides/lab003-compute-node.xml:223(para)
+msgid "Edit <filename>/etc/nova/nova-compute.conf</filename>"
+msgstr ""
+
+#: ./doc/training-guides/lab003-compute-node.xml:282(para)
+msgid "Restart nova services"
+msgstr ""
+
+#: ./doc/training-guides/lab003-compute-node.xml:286(para)
+msgid "List nova services (Check for the Smiley Faces to know if the services are running):"
+msgstr ""
+
+#: ./doc/training-guides/bk001-associate-training-guide.xml:5(title)
+msgid "Associate Training Guide"
+msgstr ""
+
+#: ./doc/training-guides/card011.xml:7(title)
+msgid "Installing MySQL"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch019-developer-how-to-participate-day-eight-quiz.xml:6(title)
+msgid "Developer How To Participate Day Eight Quiz"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch019-developer-how-to-participate-day-eight-quiz.xml:8(title)
+msgid "Day 8, 16:40 to 17:00"
+msgstr ""
+
+#: ./doc/training-guides/card074-horizon-snapshots.xml:7(title)
+msgid "Creating Snapshots"
+msgstr ""
+
+#: ./doc/training-guides/card074-horizon-snapshots.xml:8(emphasis)
+msgid "Creating image snapshots using Horizon"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch014-developer-how-to-participate-day-six-lab.xml:6(title)
+msgid "Developer How To Participate Lab Day Six"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch014-developer-how-to-participate-day-six-lab.xml:8(title)
+msgid "Day 6, 13:30 to 14:45, 15:00 to 16:30"
+msgstr ""
+
+#: ./doc/training-guides/card046-L3_Configuration_in_the_Network_Node.xml:7(title)
+msgid "L3 Configuration in the Network Node"
+msgstr ""
+
+#: ./doc/training-guides/card008.xml:7(title)
+msgid "Understanding the RefStack Architecture"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch011-developer-how-to-partipate.xml:8(title)
+msgid "Developer How To Participate"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch011-developer-how-to-partipate.xml:10(title)
+msgid "Day 5 to 9, 09:00 to 11:00, 11:15 to 12:30"
+msgstr ""
+
+#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml:22(title)
+msgid "Review Associate Introduction"
+msgstr ""
+
+#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml:29(title)
+msgid "Review Associate Brief Overview"
+msgstr ""
+
+#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml:36(title)
+msgid "Review Associate Core Projects"
+msgstr ""
+
+#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml:43(title)
+msgid "Review Associate OpenStack Architecture"
+msgstr ""
+
+#: ./doc/training-guides/bk002-ch001-operator-getting-started.xml:50(title)
+msgid "Review Associate Virtual Machine Provisioning Walk-Through"
+msgstr ""
+
+#: ./doc/training-guides/bk002-ch008-operator-compute-node-lab.xml:6(title) ./doc/training-guides/bk002-ch008-operator-compute-node-lab.xml:12(title)
+msgid "Compute Node Lab"
+msgstr ""
+
+#: ./doc/training-guides/bk002-ch008-operator-compute-node-lab.xml:8(title)
+msgid "Days 5 to 6, 13:30 to 14:45, 15:00 to 17:00"
+msgstr ""
+
+#: ./doc/training-guides/card045-configure-virtual-networking.xml:7(title)
+msgid "Configure Virtual Networking"
+msgstr ""
+
+#: ./doc/training-guides/bk000-preface.xml:6(title)
+msgid "Start Here"
+msgstr ""
+
+#: ./doc/training-guides/bk000-preface.xml:8(title)
+msgid "Preface"
+msgstr ""
+
+#: ./doc/training-guides/bk000-preface.xml:13(title)
+msgid "OpenStack Training Guides Are Under Construction"
+msgstr ""
+
+#: ./doc/training-guides/bk000-preface.xml:14(para)
+msgid "We need your help! This is a community driven project to provide the user group community access to OpenStack training materials. We cannot make this work without your help."
+msgstr ""
+
+#: ./doc/training-guides/bk000-preface.xml:16(para)
+msgid "There are a few ways to get involved. The easiest way is to use the training guides. Look at the end of each section and you will see the Submit a Bug link. When you find something that can be improved or fixed, submit a bug by clicking on the link."
+msgstr ""
+
+#: ./doc/training-guides/bk000-preface.xml:19(para)
+msgid "If you want to get involved with the effort around OpenStack community training, read on, here are the options:"
+msgstr ""
+
+#: ./doc/training-guides/bk000-preface.xml:24(title)
+msgid "Attending a user group using the training materials"
+msgstr ""
+
+#: ./doc/training-guides/bk000-preface.xml:25(para)
+msgid "The OpenStack community training started at the SFBay OpenStack User Group. More information on this user group and others using the training guides on the <link href=\"https://wiki.openstack.org/wiki/OpenStackUserGroups\">OpenStack User Groups page</link>."
+msgstr ""
+
+#: ./doc/training-guides/bk000-preface.xml:32(title)
+msgid "Teach / Lead a user group using the training materials"
+msgstr ""
+
+#: ./doc/training-guides/bk000-preface.xml:33(para)
+msgid "Awesome! Your experience will not only give you more experience with OpenStack, but you will help some people find new jobs. We have put all the information about <link href=\"https://wiki.openstack.org/wiki/OpenStackUserGroups/HowTo#Running_a_Hackathon\">How To Run An OpenStack Hackathon</link> here."
+msgstr ""
+
+#: ./doc/training-guides/bk000-preface.xml:40(title)
+msgid "Help create the training pages"
+msgstr ""
+
+#: ./doc/training-guides/bk000-preface.xml:44(para)
+msgid "We are currently working on creating the Associate Training Guide. It is the first of four training guides. We are using the Install Guide, Administration Guides, Developer Documentation, and Aptira supplied content as the sources for most of the Associate Training Guide. The basic idea is that we use XML include statements to actually use the source content to create new pages. We aim to use as much of the material as possible from existing documentation. By doing this we reuse and improve the existing docs. The topics in the Associate Training Guide are in a bunch of KanBan story board cards. Each card in the story board represents something that an Associate trainee needs to learn. But first things first, you need to get some basic tools and accounts installed and configured before you can really start."
+msgstr ""
+
+#: ./doc/training-guides/bk000-preface.xml:57(para)
+msgid "<emphasis role=\"bold\">Getting Accounts and Tools:</emphasis> We can't do this without operators and developers using and creating the content. Anyone can contribute content. You will need the tools to get started. Go to the <link href=\"operator-getting-started-lab.html#getting-tools-and-accounts\">Getting Tools and Accounts</link> page."
+msgstr ""
+
+#: ./doc/training-guides/bk000-preface.xml:64(para)
+msgid "<emphasis role=\"bold\">Pick a Card:</emphasis> Once you have your tools ready to go, you can assign some work to yourself. Go to the <link href=\"https://trello.com/board/openstack-training/51d6e5fee37248fd5b003de9\">Training Trello/KanBan storyboard</link> and assign a card / user story from the Sprint Backlog to yourself. If you do not have a Trello account, no problem, just create one. Email seanrob@yahoo-inc.com and you will have access."
+msgstr ""
+
+#: ./doc/training-guides/bk000-preface.xml:72(para)
+msgid "<emphasis role=\"bold\">Create the Content:</emphasis> Each card / user story from the KanBan story board will be a separate chunk of content that you will add to the openstack-manuals repository openstack-training sub-project. <link href=\"operator-getting-started-lab.html#operator-add-training-content\"> More details on creating training content here.</link>"
+msgstr ""
+
+#: ./doc/training-guides/bk000-preface.xml:82(para)
+msgid "Here are more details on committing changes to OpenStack <link href=\"operator-getting-started-lab.html#submit-doc-bug\">fixing a documentation bug</link> , <link href=\"https://wiki.openstack.org/wiki/Gerrit_Workflow\">OpenStack Gerrit Workflow</link>, <link href=\"https://wiki.openstack.org/wiki/Documentation/HowTo\">OpenStack Documentation HowTo</link> and , <link href=\"http://git-scm.com/doc\">Git Documentation</link>"
+msgstr ""
+
+#: ./doc/training-guides/bk000-preface.xml:91(para)
+msgid "More details on the OpenStack Training project."
+msgstr ""
+
+#: ./doc/training-guides/bk000-preface.xml:95(para)
+msgid "<link href=\"https://wiki.openstack.org/wiki/Training-manuals\">OpenStack Training Wiki</link> (describes the project in detail)"
+msgstr ""
+
+#: ./doc/training-guides/bk000-preface.xml:99(para)
+msgid "<link href=\"https://blueprints.launchpad.net/openstack-manuals/+spec/training-manuals\">OpenStack Training blueprint</link>(this is the key project page)"
+msgstr ""
+
+#: ./doc/training-guides/bk000-preface.xml:104(para)
+msgid "<link href=\"http://www.meetup.com/openstack/\">Bi-Weekly SFBay Hackathon meetup page</link>(we discuss project details with all team members)"
+msgstr ""
+
+#: ./doc/training-guides/bk000-preface.xml:108(para)
+msgid "<link href=\"https://etherpad.openstack.org/sfbay-openstack\">Bi-Weekly SFBay Hackathon Etherpad</link>(meetup notes)"
+msgstr ""
+
+#: ./doc/training-guides/bk000-preface.xml:112(para)
+msgid "<link href=\"https://wiki.openstack.org/wiki/Meetings/training-manuals\">Core Training Weekly Meeting Agenda</link>(we review project action items here)"
+msgstr ""
+
+#: ./doc/training-guides/bk000-preface.xml:116(para)
+msgid "<link href=\"https://trello.com/board/openstack-training/51d6e5fee37248fd5b003de9\">Training Trello/KanBan storyboard</link>(we develop high level project action items here)"
+msgstr ""
+
+#: ./doc/training-guides/bk000-preface.xml:123(link)
+msgid "Submit a bug. Enter the summary as \"Training, \" with a few words. Be descriptive as possible in the description field. Open the tag pull-down and enter training-manuals."
+msgstr ""
+
+#: ./doc/training-guides/bk000-preface.xml:127(title)
+msgid "Building the Training Cluster"
+msgstr ""
+
+#: ./doc/training-guides/bk000-preface.xml:130(title)
+msgid "Important Terms"
+msgstr ""
+
+#: ./doc/training-guides/bk000-preface.xml:137(title)
+msgid "Building the Training Cluster, Scripted"
+msgstr ""
+
+#: ./doc/training-guides/bk000-preface.xml:144(title)
+msgid "Building the Training Cluster, Manually"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch022-developer-assessment.xml:6(title) ./doc/training-guides/bk001-ch011-associate-assessment.xml:6(title)
+msgid "Assessment"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch022-developer-assessment.xml:8(title)
+msgid "Day 10, 9:00 to 11:00, 11:15 to 12:30, hands on lab 13:30 to 14:45, 15:00 to 17:00"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch022-developer-assessment.xml:12(title) ./doc/training-guides/bk001-ch011-associate-assessment.xml:12(title)
+msgid "Questions"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch022-developer-assessment.xml:14(caption) ./doc/training-guides/bk001-ch011-associate-assessment.xml:14(caption)
+msgid "Assessment Question 1"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch022-developer-assessment.xml:19(th) ./doc/training-guides/bk003-ch022-developer-assessment.xml:40(th) ./doc/training-guides/bk001-ch011-associate-assessment.xml:19(th) ./doc/training-guides/bk001-ch011-associate-assessment.xml:40(th)
+msgid "Task"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch022-developer-assessment.xml:20(th) ./doc/training-guides/bk003-ch022-developer-assessment.xml:41(th) ./doc/training-guides/bk001-ch011-associate-assessment.xml:20(th) ./doc/training-guides/bk001-ch011-associate-assessment.xml:41(th)
+msgid "Completed?"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch022-developer-assessment.xml:26(para) ./doc/training-guides/bk003-ch022-developer-assessment.xml:47(para) ./doc/training-guides/bk001-ch011-associate-assessment.xml:26(para) ./doc/training-guides/bk001-ch011-associate-assessment.xml:47(para)
+msgid "Configure a ...."
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch022-developer-assessment.xml:35(caption) ./doc/training-guides/bk001-ch011-associate-assessment.xml:35(caption)
+msgid "Assessment Question 2"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:8(title)
+msgid "Day 1, 10:40 to 11:00"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:10(title)
+msgid "Associate Training Guide, Getting Started Quiz Questions"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:15(title)
+msgid "What are some of the compelling features of a cloud? (choose all that apply)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:19(para)
+msgid "On-demand self-service"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:22(para)
+msgid "Resource pooling"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:25(para)
+msgid "Metered or measured service"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:28(para)
+msgid "Elasticity"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:31(para)
+msgid "Network access"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:39(title)
+msgid "What three service models does cloud computing provide? (choose all that apply)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:43(para)
+msgid "Software-as-a-Service (SaaS)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:46(para)
+msgid "Applications-as-a-Service (AaaS)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:49(para)
+msgid "Hardware-as-a-Service (HaaS)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:52(para)
+msgid "Infrastructure-as-a-Service (IaaS)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:55(para)
+msgid "Platform-as-a-Service (PaaS)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:63(title)
+msgid "What does the OpenStack project aim to deliver? (choose all that apply)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:67(para)
+msgid "Simple to implement cloud solution"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:70(para)
+msgid "Massively scalable cloud solution"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:73(para)
+msgid "Feature rich cloud solution"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:76(para)
+msgid "Multi-vendor interoperability cloud solution"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:79(para)
+msgid "A new hypervisor cloud solution"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:87(title)
+msgid "OpenStack code is freely available via the FreeBSD license. (True or False)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:102(title)
+msgid "OpenStack Swift is Object Storage. (True or False)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:117(title)
+msgid "OpenStack Networking is now called Quantum. (True or False)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:132(title)
+msgid "The Image Service (Glance) in OpenStack provides: (Choose all that apply)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:136(para)
+msgid "Base Templates which users can start new compute instances"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:139(para)
+msgid "Configuration of centralized policies across users and systems"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:142(para)
+msgid "Available images for users to choose from or create their own from existing servers"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:145(para)
+msgid "A central directory of users"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:148(para)
+msgid "Ability to take store snapshots in the Image Service for backup"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:156(title)
+msgid "OpenStack APIs are compatible with Amazon EC2 and Amazon S3. (True or False)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:171(title)
+msgid "Horizon is the OpenStack name for Compute. (True or False)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:186(title)
+msgid "Which Hypervisors can be supported in OpenStack? (Choose all that apply)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:196(para)
+msgid "bhyve (BSD)"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:199(para)
+msgid "Xen"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:202(para)
+msgid "LXC"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:212(title)
+msgid "Associate Training Guide, Getting Started Quiz Answers"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:216(para)
+msgid "A, B, C, D, E"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:219(para)
+msgid "A, D, E"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:225(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:231(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:240(para)
+msgid "B"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:228(para) ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:237(para)
+msgid "A"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:234(para)
+msgid "A, C, E"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml:243(para)
+msgid "A, B, D, E"
+msgstr ""
+
+#: ./doc/training-guides/bk003-developer-training-guide.xml:5(title)
+msgid "Developer Training Guide"
+msgstr ""
+
+#: ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:6(title)
+msgid "Object Storage Node Lab"
+msgstr ""
+
+#: ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:8(title)
+msgid "Day 9, 13:30 to 14:45, 15:00 to 17:00"
+msgstr ""
+
+#: ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:12(title)
+msgid "Installing Object Node"
+msgstr ""
+
+#: ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:19(title)
+msgid "Configuring Object Node"
+msgstr ""
+
+#: ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:26(title)
+msgid "Configuring Object Proxy"
+msgstr ""
+
+#: ./doc/training-guides/bk002-ch014-operator-object-storage-node-lab.xml:33(title)
+msgid "Start Object Node Services"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:10(title)
+msgid "Day 2, 11:30 to 12:30, 13:30 to 14:45"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:14(title)
+msgid "Introduction to Object Storage"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:21(title)
+msgid "Features and Benefits"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:30(title)
+msgid "Object Storage CLI Commands"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:37(title)
+msgid "Manage Object Storage"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch009-associate-object-storage-node.xml:38(para)
+msgid "Will be included from the swift developer reference"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:27(None)
+msgid "@@image: 'figures/image13.jpg'; md5=94fd9b9a3b33574d85bec7e1ea1675e2"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:71(None)
+msgid "@@image: 'figures/openstack-arch-havana-logical-v1.jpg'; md5=e7acaaee72722626b045eda3fae81841"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:102(None)
+msgid "@@image: 'figures/image10.jpg'; md5=9471047adf0d93713be7f54b9db2b53c"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:8(guilabel)
+msgid "Conceptual Architecture"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:9(para)
+msgid "The OpenStack project as a whole is designed to deliver a massively scalable cloud operating system. To achieve this, each of the constituent services are designed to work together to provide a complete Infrastructure-as-a-Service (IaaS). This integration is facilitated through public application programming interfaces (APIs) that each service offers (and in turn can consume). While these APIs allow each of the services to use another service, it also allows an implementer to switch out any service as long as they maintain the API. These are (mostly) the same APIs that are available to end users of the cloud."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:20(para)
+msgid "Conceptually, you can picture the relationships between the services as so:"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:23(title)
+msgid "Conceptual Diagram"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:33(para)
+msgid "Dashboard (\"Horizon\") provides a web front end to the other OpenStack services"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:37(para)
+msgid "Compute (\"Nova\") stores and retrieves virtual disks (\"images\") and associated metadata in Image (\"Glance\")"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:42(para)
+msgid "Network (\"Neutron\") provides virtual networking for Compute."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:46(para)
+msgid "Block Storage (\"Cinder\") provides storage volumes for Compute."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:50(para)
+msgid "Image (\"Glance\") can store the actual virtual disk files in the Object Store(\"Swift\")"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:54(para)
+msgid "All the services authenticate with Identity (\"Keystone\")"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:58(para)
+msgid "The conceptual diagram is a stylized and simplified view of the architecture. It assumes that the implementer uses all services in the most common configuration. It also shows only the operator side of the cloud; it does not show how consumers might use the cloud. For example, many users directly and heavily access object storage."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:63(guilabel)
+msgid "Logical Architecture"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:64(para)
+msgid "The following diagram is consistent with the conceptual architecture as previously described:"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:67(title)
+msgid "Logical diagram"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:77(para)
+msgid "End users can interact through a common web interface (Horizon) or directly to each service through their API"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:82(para)
+msgid "All services authenticate through a common source (facilitated through keystone)"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:86(para)
+msgid "Individual services interact with each other through their public APIs (except where privileged administrator commands are necessary)"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:91(para)
+msgid "In the sections below, we'll delve into the architecture for each of the services."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:93(guilabel)
+msgid "Dashboard"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:94(para)
+msgid "Horizon is a modular Django web application that provides an end user and administrator interface to OpenStack services."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:98(title)
+msgid "Horizon Dashboard"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:106(para)
+msgid "As with most web applications, the architecture is fairly simple:"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:110(para)
+msgid "Horizon is usually deployed via mod_wsgi in Apache. The code itself is separated into a reusable python module with most of the logic (interactions with various OpenStack APIs) and presentation (to make it easily customizable for different sites)."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:117(para)
+msgid "A database (configurable as to which one) which relies mostly on the other services for data. It also stores very little data of its own."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:122(para)
+msgid "From a network architecture point of view, this service will need to be customer accessible as well as be able to talk to each service's public APIs. If you wish to use the administrator functionality (i.e. for other services), it will also need connectivity to their Admin API endpoints (which should be non-customer accessible)."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:128(guilabel)
+msgid "Compute"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:129(para)
+msgid "Nova is the most complicated and distributed component of OpenStack. A large number of processes cooperate to turn end user API requests into running virtual machines. Below is a list of these processes and their functions:"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:135(para)
+msgid "nova-api accepts and responds to end user compute API calls. It supports OpenStack Compute API, Amazon's EC2 API and a special Admin API (for privileged users to perform administrative actions). It also initiates most of the orchestration activities (such as running an instance) as well as enforces some policy (mostly quota checks)."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:143(para)
+msgid "The nova-compute process is primarily a worker daemon that creates and terminates virtual machine instances via hypervisor's APIs (XenAPI for XenServer/XCP, libvirt for KVM or QEMU, VMwareAPI for VMware, etc.). The process by which it does so is fairly complex but the basics are simple: accept actions from the queue and then perform a series of system commands (like launching a KVM instance) to carry them out while updating state in the database."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:154(para)
+msgid "nova-volume manages the creation, attaching and detaching of z volumes to compute instances (similar functionality to Amazon’s Elastic Block Storage). It can use volumes from a variety of providers such as iSCSI or Rados Block Device in Ceph. A new OpenStack project, Cinder, will eventually replace nova-volume functionality. In the Folsom release, nova-volume and the Block Storage service will have similar functionality."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:164(para)
+msgid "The nova-network worker daemon is very similar to nova-compute and nova-volume. It accepts networking tasks from the queue and then performs tasks to manipulate the network (such as setting up bridging interfaces or changing iptables rules). This functionality is being migrated to Neutron, a separate OpenStack project. In the Folsom release, much of the functionality will be duplicated between nova-network and Neutron."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:174(para)
+msgid "The nova-schedule process is conceptually the simplest piece of code in OpenStack Nova: it takes a virtual machine instance request from the queue and determines where it should run (specifically, which compute server host it should run on)."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:181(para)
+msgid "The queue provides a central hub for passing messages between daemons. This is usually implemented with RabbitMQ today, but could be any AMQP message queue (such as Apache Qpid). New to the Folsom release is support for Zero MQ."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:188(para)
+msgid "The SQL database stores most of the build-time and runtime state for a cloud infrastructure. This includes the instance types that are available for use, instances in use, networks available and projects. Theoretically, OpenStack Nova can support any database supported by SQL-Alchemy but the only databases currently being widely used are SQLite3 (only appropriate for test and development work), MySQL and PostgreSQL."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:198(para)
+msgid "Nova also provides console services to allow end users to access their virtual instance's console through a proxy. This involves several daemons (nova-console, nova-novncproxy and nova-consoleauth)."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:204(para)
+msgid "Nova interacts with many other OpenStack services: Keystone for authentication, Glance for images and Horizon for web interface. The Glance interactions are central. The API process can upload and query Glance while nova-compute will download images for use in launching images."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:209(guilabel)
+msgid "Object Store"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:210(para)
+msgid "The swift architecture is very distributed to prevent any single point of failure as well as to scale horizontally. It includes the following components:"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:215(para)
+msgid "Proxy server (swift-proxy-server) accepts incoming requests via the OpenStack Object API or just raw HTTP. It accepts files to upload, modifications to metadata or container creation. In addition, it will also serve files or container listing to web browsers. The proxy server may utilize an optional cache (usually deployed with memcache) to improve performance."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:224(para)
+msgid "Account servers manage accounts defined with the object storage service."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:228(para)
+msgid "Container servers manage a mapping of containers (i.e folders) within the object store service."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:232(para)
+msgid "Object servers manage actual objects (i.e. files) on the storage nodes."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:236(para)
+msgid "There are also a number of periodic processes which run to perform housekeeping tasks on the large data store. The most important of these is the replication services, which ensures consistency and availability through the cluster. Other periodic processes include auditors, updaters and reapers."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:244(para)
+msgid "Authentication is handled through configurable WSGI middleware (which will usually be Keystone)."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:246(guilabel)
+msgid "Image Store"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:247(para)
+msgid "The Glance architecture has stayed relatively stable since the Cactus release. The biggest architectural change has been the addition of authentication, which was added in the Diablo release. Just as a quick reminder, Glance has four main parts to it:"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:254(para)
+msgid "glance-api accepts Image API calls for image discovery, image retrieval and image storage."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:258(para)
+msgid "glance-registry stores, processes and retrieves metadata about images (size, type, etc.)."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:262(para)
+msgid "A database to store the image metadata. Like Nova, you can choose your database depending on your preference (but most people use MySQL or SQLite)."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:267(para)
+msgid "A storage repository for the actual image files. In the diagram above, Swift is shown as the image repository, but this is configurable. In addition to Swift, Glance supports normal filesystems, RADOS block devices, Amazon S3 and HTTP. Be aware that some of these choices are limited to read-only usage."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:275(para)
+msgid "There are also a number of periodic processes which run on Glance to support caching. The most important of these is the replication services, which ensures consistency and availability through the cluster. Other periodic processes include auditors, updaters and reapers."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:280(para)
+msgid "As you can see from the diagram in the Conceptual Architecture section, Glance serves a central role to the overall IaaS picture. It accepts API requests for images (or image metadata) from end users or Nova components and can store its disk files in the object storage service, Swift."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:286(guilabel)
+msgid "Identity"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:287(para)
+msgid "Keystone provides a single point of integration for OpenStack policy, catalog, token and authentication."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:291(para)
+msgid "Keystone handles API requests as well as providing configurable catalog, policy, token and identity services."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:296(para)
+msgid "Each Keystone function has a pluggable backend which allows different ways to use the particular service. Most support standard backends like LDAP or SQL, as well as Key Value Stores (KVS)."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:302(para)
+msgid "Most people will use this as a point of customization for their current authentication services."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:304(guilabel)
+msgid "Network"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:305(para)
+msgid "Neutron provides \"network connectivity as a service\" between interface devices managed by other OpenStack services (most likely Nova). The service works by allowing users to create their own networks and then attach interfaces to them. Like many of the OpenStack services, Neutron is highly configurable due to its plug-in architecture. These plug-ins accommodate different networking equipment and software. As such, the architecture and deployment can vary dramatically. In the above architecture, a simple Linux networking plug-in is shown."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:317(para)
+msgid "neutron-server accepts API requests and then routes them to the appropriate Neutron plug-in for action."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:321(para)
+msgid "Neutron plug-ins and agents perform the actual actions such as plugging and unplugging ports, creating networks or subnets and IP addressing. These plug-ins and agents differ depending on the vendor and technologies used in the particular cloud. Neutron ships with plug-ins and agents for: Cisco virtual and physical switches, NEC OpenFlow products, Open vSwitch, Linux bridging, the Ryu Network Operating System, and VMware NSX."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:331(para)
+msgid "The common agents are L3 (layer 3), DHCP (dynamic host IP addressing) and the specific plug-in agent."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:335(para)
+msgid "Most Neutron installations will also make use of a messaging queue to route information between the neutron-server and various agents as well as a database to store networking state for particular plug-ins."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:341(para)
+msgid "Neutron will interact mainly with Nova, where it will provide networks and connectivity for its instances."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:343(guilabel)
+msgid "Block Storage"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:344(para)
+msgid "Cinder separates out the persistent block storage functionality that was previously part of OpenStack Compute (in the form of nova-volume) into its own service. The OpenStack Block Storage API allows for manipulation of volumes, volume types (similar to compute flavors) and volume snapshots."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:352(para)
+msgid "cinder-api accepts API requests and routes them to cinder-volume for action."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:356(para)
+msgid "cinder-volume acts upon the requests by reading or writing to the Cinder database to maintain state, interacting with other processes (like cinder-scheduler) through a message queue and directly upon block storage providing hardware or software. It can interact with a variety of storage providers through a driver architecture. Currently, there are drivers for IBM, SolidFire, NetApp, Nexenta, Zadara, linux iSCSI and other storage providers."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:367(para)
+msgid "Much like nova-scheduler, the cinder-scheduler daemon picks the optimal block storage provider node to create the volume on."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:372(para)
+msgid "Cinder deployments will also make use of a messaging queue to route information between the cinder processes as well as a database to store volume state."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch004-openstack-architecture.xml:377(para)
+msgid "Like Neutron, Cinder will mainly interact with Nova, providing volumes for its instances."
+msgstr ""
+
+#: ./doc/training-guides/card009.xml:6(title)
+msgid "Install Ubuntu"
+msgstr ""
+
+#: ./doc/training-guides/bk002-operator-training-guide.xml:5(title)
+msgid "Operator Training Guide"
 msgstr ""
 
 #: ./doc/training-guides/bk003-ch005-developer-apis-day-two-lab.xml:6(title)
@@ -8897,18 +8192,771 @@ msgstr ""
 msgid "Jenkins"
 msgstr ""
 
+#: ./doc/training-guides/module001-ch011-block-storage.xml:7(emphasis)
+msgid "Block Storage and OpenStack Compute"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:9(para)
+msgid "OpenStack provides two classes of block storage, \"ephemeral\" storage and persistent \"volumes\". Ephemeral storage exists only for the life of an instance, it will persist across reboots of the guest operating system but when the instance is deleted so is the associated storage. All instances have some ephemeral storage. Volumes are persistent virtualized block devices independent of any particular instance. Volumes may be attached to a single instance at a time, but may be detached or reattached to a different instance while retaining all data, much like a USB drive."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:19(guilabel)
+msgid "Ephemeral Storage"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:20(para)
+msgid "Ephemeral storage is associated with a single unique instance. Its size is defined by the flavor of the instance."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:22(para)
+msgid "Data on ephemeral storage ceases to exist when the instance it is associated with is terminated. Rebooting the VM or restarting the host server, however, will not destroy ephemeral data. In the typical use case an instance's root filesystem is stored on ephemeral storage. This is often an unpleasant surprise for people unfamiliar with the cloud model of computing."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:28(para)
+msgid "In addition to the ephemeral root volume all flavors except the smallest, m1.tiny, provide an additional ephemeral block device varying from 20G for the m1.small through 160G for the m1.xlarge by default - these sizes are configurable. This is presented as a raw block device with no partition table or filesystem. Cloud aware operating system images may discover, format, and mount this device. For example the cloud-init package included in Ubuntu's stock cloud images will format this space as an ext3 filesystem and mount it on /mnt. It is important to note this a feature of the guest operating system. OpenStack only provisions the raw storage."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:39(guilabel)
+msgid "Volume Storage"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:40(para)
+msgid "Volume storage is independent of any particular instance and is persistent. Volumes are user created and within quota and availability limits may be of any arbitrary size."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:43(para)
+msgid "When first created volumes are raw block devices with no partition table and no filesystem. They must be attached to an instance to be partitioned and/or formatted. Once this is done they may be used much like an external disk drive. Volumes may attached to only one instance at a time, but may be detached and reattached to either the same or different instances."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:49(para)
+msgid "It is possible to configure a volume so that it is bootable and provides a persistent virtual instance similar to traditional non-cloud based virtualization systems. In this use case the resulting instance may still have ephemeral storage depending on the flavor selected, but the root filesystem (and possibly others) will be on the persistent volume and thus state will be maintained even if the instance is shutdown. Details of this configuration are discussed in the<link href=\"http://docs.openstack.org/user-guide/content/\">OpenStack End User Guide</link>."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:59(para)
+msgid "Volumes do not provide concurrent access from multiple instances. For that you need either a traditional network filesystem like NFS or CIFS or a cluster filesystem such as GlusterFS. These may be built within an OpenStack cluster or provisioned outside of it, but are not features provided by the OpenStack software."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:65(para)
+msgid "The OpenStack Block Storage service works via the interaction of a series of daemon processes named cinder-* that reside persistently on the host machine or machines. The binaries can all be run from a single node, or spread across multiple nodes. They can also be run on the same node as other OpenStack services."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:71(guilabel)
+msgid "The current services available in OpenStack Block Storage are:"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:75(para)
+msgid "<emphasis role=\"bold\">cinder-api</emphasis> - The cinder-api service is a WSGI app that authenticates and routes requests throughout the Block Storage system. It supports the OpenStack API's only, although there is a translation that can be done via Nova's EC2 interface which calls in to the cinderclient."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:85(para)
+msgid "<emphasis role=\"bold\">cinder-scheduler</emphasis> - The cinder-scheduler is responsible for scheduling/routing requests to the appropriate volume service. As of Grizzly; depending upon your configuration this may be simple round-robin scheduling to the running volume services, or it can be more sophisticated through the use of the Filter Scheduler. The Filter Scheduler is the default in Grizzly and enables filter on things like Capacity, Availability Zone, Volume Types and Capabilities as well as custom filters."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:99(para)
+msgid "<emphasis role=\"bold\">cinder-volume</emphasis> - The cinder-volume service is responsible for managing Block Storage devices, specifically the back-end devices themselves."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:107(para)
+msgid "<emphasis role=\"bold\">cinder-backup</emphasis> - The cinder-backup service provides a means to back up a Cinder Volume to OpenStack Object Store (SWIFT)."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:112(guilabel)
+msgid "Introduction to OpenStack Block Storage"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:114(para)
+msgid "OpenStack Block Storage provides persistent High Performance Block Storage resources that can be consumed by OpenStack Compute instances. This includes secondary attached storage similar to Amazon's Elastic Block Storage (EBS). In addition images can be written to a Block Storage device and specified for OpenStack Compute to use a bootable persistent instance."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:120(para)
+msgid "There are some differences from Amazon's EBS that one should be aware of. OpenStack Block Storage is not a shared storage solution like NFS, but currently is designed so that the device is attached and in use by a single instance at a time."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:124(guilabel)
+msgid "Backend Storage Devices"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:125(para)
+msgid "OpenStack Block Storage requires some form of back-end storage that the service is built on. The default implementation is to use LVM on a local Volume Group named \"cinder-volumes\". In addition to the base driver implementation, OpenStack Block Storage also provides the means to add support for other storage devices to be utilized such as external Raid Arrays or other Storage appliances."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:133(para)
+msgid "The OpenStack Block Storage system is designed to be used by many different cloud computing consumers or customers, basically tenants on a shared system, using role-based access assignments. Roles control the actions that a user is allowed to perform. In the default configuration, most actions do not require a particular role, but this is configurable by the system administrator editing the appropriate policy.json file that maintains the rules. A user's access to particular volumes is limited by tenant, but the username and password are assigned per user. Key pairs granting access to a volume are enabled per user, but quotas to control resource consumption across available hardware resources are per tenant."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:152(para)
+msgid "Number of snapshots which may be created"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:155(para)
+msgid "Total number of Giga Bytes allowed per tenant (shared between snapshots and volumes)"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:159(guilabel)
+msgid "Volumes Snapshots and Backups"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:160(para)
+msgid "This introduction provides a high level overview of the two basic resources offered by the OpenStack Block Storage service. The first is Volumes and the second is Snapshots which are derived from Volumes."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:165(para)
+msgid "Volumes are allocated block storage resources that can be attached to instances as secondary storage or they can be used as the root store to boot instances. Volumes are persistent R/W Block Storage devices most commonly attached to the compute node via iSCSI."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:170(guilabel)
+msgid "Snapshots"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:171(para)
+msgid "A Snapshot in OpenStack Block Storage is a read-only point in time copy of a Volume. The Snapshot can be created from a Volume that is currently in use (via the use of '--force True') or in an available state. The Snapshot can then be used to create a new volume via create from snapshot."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:176(guilabel)
+msgid "Backups"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:177(para)
+msgid "A Backup is an archived copy of a Volume currently stored in Object Storage (Swift)."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:179(guilabel)
+msgid "Managing Volumes"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:180(para)
+msgid "Cinder is the OpenStack service that allows you to give extra block level storage to your OpenStack Compute instances. You may recognize this as a similar offering from Amazon EC2 known as Elastic Block Storage (EBS). The default Cinder implementation is an iSCSI solution that employs the use of Logical Volume Manager (LVM) for Linux. Note that a volume may only be attached to one instance at a time. This is not a ‘shared storage’ solution like a SAN of NFS on which multiple servers can attach to. It's also important to note that Cinder also includes a number of drivers to allow you to use a number of other vendor's back-end storage devices in addition to or instead of the base LVM implementation."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:192(para)
+msgid "Here is brief walk-through of a simple create/attach sequence, keep in mind this requires proper configuration of both OpenStack Compute via cinder.conf and OpenStack Block Storage via cinder.conf."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:198(para)
+msgid "The volume is created via cinder create; which creates an LV into the volume group (VG) \"cinder-volumes\""
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:202(para)
+msgid "The volume is attached to an instance via nova volume-attach; which creates a unique iSCSI IQN that will be exposed to the compute node"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:207(para)
+msgid "The compute node which run the concerned instance has now an active ISCSI session; and a new local storage (usually a /dev/sdX disk)"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:212(para)
+msgid "libvirt uses that local storage as a storage for the instance; the instance get a new disk (usually a /dev/vdX disk)"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch011-block-storage.xml:217(guilabel)
+msgid "Block Storage Capabilities"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch010-developer-apis-day-four-quiz.xml:6(title)
+msgid "Developer APIs in Depth Day Four Quiz"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch010-developer-apis-day-four-quiz.xml:8(title)
+msgid "Day 4, 16:40 to 17:00"
+msgstr ""
+
+#: ./doc/training-guides/lab002-network-node.xml:28(para)
+msgid "Start your Controller Node the one you setup in previous section."
+msgstr ""
+
+#: ./doc/training-guides/lab002-network-node.xml:68(para)
+msgid "Enable IP Forwarding by adding the following to <filename>/etc/sysctl.conf</filename>:"
+msgstr ""
+
+#: ./doc/training-guides/lab002-network-node.xml:85(emphasis)
+msgid "Open vSwitch"
+msgstr ""
+
+#: ./doc/training-guides/lab002-network-node.xml:88(para)
+msgid "Install Open vSwitch Packages:"
+msgstr ""
+
+#: ./doc/training-guides/lab002-network-node.xml:94(para)
+msgid "Create the bridges:"
+msgstr ""
+
+#: ./doc/training-guides/lab002-network-node.xml:104(para)
+msgid "Neutron:"
+msgstr ""
+
+#: ./doc/training-guides/lab002-network-node.xml:110(para)
+msgid "Edit <filename>/etc/neutron/api-paste.ini</filename>:"
+msgstr ""
+
+#: ./doc/training-guides/lab002-network-node.xml:123(para)
+msgid "Edit <filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename>:"
+msgstr ""
+
+#: ./doc/training-guides/lab002-network-node.xml:147(para)
+msgid "Edit <filename>/etc/neutron/metadata_agent.ini</filename>:"
+msgstr ""
+
+#: ./doc/training-guides/lab002-network-node.xml:163(para)
+msgid "Edit <filename>/etc/neutron/dhcp_agent.ini</filename>:"
+msgstr ""
+
+#: ./doc/training-guides/lab002-network-node.xml:169(para)
+msgid "Edit <filename>/etc/neutron/l3_agent.ini</filename>:"
+msgstr ""
+
+#: ./doc/training-guides/lab002-network-node.xml:177(para)
+msgid "Edit <filename>/etc/neutron/neutron.conf</filename>:"
+msgstr ""
+
+#: ./doc/training-guides/lab002-network-node.xml:194(para)
+msgid "Edit <filename>/etc/sudoers.d/neutron_sudoers:</filename>:"
+msgstr ""
+
+#: ./doc/training-guides/lab002-network-node.xml:201(para)
+msgid "Restart Services:"
+msgstr ""
+
+#: ./doc/training-guides/lab002-network-node.xml:209(para)
+msgid "Edit Network Interfaces file <filename>/etc/network/interfaces</filename>:"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:19(None)
+msgid "@@image: 'figures/image29.png'; md5=ce788bfd80e615104fa1e3257065824a"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:59(None)
+msgid "@@image: 'figures/image27.png'; md5=c144af5cbdee1bd17a7bde0bea5b5fe7"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:200(None)
+msgid "@@image: '../common/figures/nova-weighting-hosts.png'; md5=000eab4cf0deb1da2e692e023065a6ae"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:8(para)
+msgid "Compute uses the nova-scheduler service to determine how to dispatch compute and volume requests. For example, the nova-scheduler service determines which host a VM should launch on. The term host in the context of filters means a physical node that has a <systemitem class=\"service\">nova-compute</systemitem> service running on it. You can configure the scheduler through a variety of options."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:23(para)
+msgid "Just as shown by above figure, nova-scheduler interacts with other components through queue and central database repo. For scheduling, queue is the essential communications hub."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:26(para)
+msgid "All compute nodes (also known as hosts in terms of OpenStack) periodically publish their status, resources available and hardware capabilities to nova-scheduler through the queue. nova-scheduler then collects this data and uses it to make decisions when a request comes in."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:31(para)
+msgid "By default, the compute scheduler is configured as a filter scheduler, as described in the next section. In the default configuration, this scheduler considers hosts that meet all the following criteria:"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:37(para)
+msgid "Are in the requested availability zone (AvailabilityZoneFilter)."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:41(para)
+msgid "Have sufficient RAM available (RamFilter)."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:44(para)
+msgid "Are capable of servicing the request (ComputeFilter)."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:49(guilabel)
+msgid "Filter Scheduler"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:50(para)
+msgid "The Filter Scheduler supports filtering and weighting to make informed decisions on where a new instance should be created. This Scheduler supports only working with Compute Nodes."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:54(guilabel) ./doc/training-guides/module001-ch009-vm-placement.xml:56(title)
+msgid "Filtering"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:63(para)
+msgid "During its work, Filter Scheduler first makes a dictionary of unfiltered hosts, then filters them using filter properties and finally chooses hosts for the requested number of instances (each time it chooses the most weighed host and appends it to the list of selected hosts)."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:68(para)
+msgid "If it turns up, that it can’t find candidates for the next instance, it means that there are no more appropriate hosts where the instance could be scheduled."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:71(para)
+msgid "If we speak about filtering and weighting, their work is quite flexible in the Filter Scheduler. There are a lot of filtering strategies for the Scheduler to support. Also you can even implement your own algorithm of filtering."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:75(para)
+msgid "There are some standard filter classes to use (nova.scheduler.filters):"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:79(para)
+msgid "AllHostsFilter - frankly speaking, this filter does no operation. It passes all the available hosts."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:83(para)
+msgid "ImagePropertiesFilter - filters hosts based on properties defined on the instance’s image. It passes hosts that can support the specified image properties contained in the instance."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:89(para)
+msgid "AvailabilityZoneFilter - filters hosts by availability zone. It passes hosts matching the availability zone specified in the instance properties."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:94(para)
+msgid "ComputeCapabilitiesFilter - checks that the capabilities provided by the host Compute service satisfy any extra specifications associated with the instance type. It passes hosts that can create the specified instance type."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:101(para)
+msgid "The extra specifications can have a scope at the beginning of the key string of a key/value pair. The scope format is scope:key and can be nested, i.e. key_string := scope:key_string. Example like capabilities:cpu_info: features is valid scope format. A key string without any : is non-scope format. Each filter defines its valid scope, and not all filters accept non-scope format."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:110(para)
+msgid "The extra specifications can have an operator at the beginning of the value string of a key/value pair. If there is no operator specified, then a default operator of s== is used. Valid operators are:"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:116(para)
+msgid "* = (equal to or greater than as a number; same as vcpus case)* == (equal to as a number)* != (not equal to as a number)* &gt;= (greater than or equal to as a number)* &lt;= (less than or equal to as a number)* s== (equal to as a string)* s!= (not equal to as a string)* s&gt;= (greater than or equal to as a string)* s&gt; (greater than as a string)* s&lt;= (less than or equal to as a string)* s&lt; (less than as a string)* &lt;in&gt; (substring)* &lt;or&gt; (find one of these)Examples are: \"&gt;= 5\", \"s== 2.1.0\", \"&lt;in&gt; gcc\", and \"&lt;or&gt; fpu &lt;or&gt; gpu\""
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:138(para)
+msgid "Here ram_allocation_ratio means the virtual RAM to physical RAM allocation ratio (it is 1.5 by default). Really, nice and simple."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:141(para)
+msgid "Next standard filter to describe is AvailabilityZoneFilter and it isn’t difficult too. This filter just looks at the availability zone of compute node and availability zone from the properties of the request. Each Compute service has its own availability zone. So deployment engineers have an option to run scheduler with availability zones support and can configure availability zones on each compute host. This classes method host_passes returns True if availability zone mentioned in request is the same on the current compute host."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:151(para)
+msgid "The ImagePropertiesFilter filters hosts based on the architecture, hypervisor type, and virtual machine mode specified in the instance. E.g., an instance might require a host that supports the arm architecture on a qemu compute host. The ImagePropertiesFilter will only pass hosts that can satisfy this request. These instance properties are populated from properties define on the instance’s image. E.g. an image can be decorated with these properties using glance image-update img-uuid --property architecture=arm --property hypervisor_type=qemu Only hosts that satisfy these requirements will pass the ImagePropertiesFilter."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:162(para)
+msgid "ComputeCapabilitiesFilter checks if the host satisfies any extra_specs specified on the instance type. The extra_specs can contain key/value pairs. The key for the filter is either non-scope format (i.e. no : contained), or scope format in capabilities scope (i.e. capabilities:xxx:yyy). One example of capabilities scope is capabilities:cpu_info:features, which will match host’s cpu features capabilities. The ComputeCapabilitiesFilter will only pass hosts whose capabilities satisfy the requested specifications. All hosts are passed if no extra_specs are specified."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:172(para)
+msgid "ComputeFilter is quite simple and passes any host whose Compute service is enabled and operational."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:174(para)
+msgid "Now we are going to IsolatedHostsFilter. There can be some special hosts reserved for specific images. These hosts are called isolated. So the images to run on the isolated hosts are also called isolated. This Scheduler checks if image_isolated flag named in instance specifications is the same that the host has."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:181(guilabel) ./doc/training-guides/module001-ch009-vm-placement.xml:196(title)
+msgid "Weights"
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:182(para)
+msgid "Filter Scheduler uses so-called weights during its work."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:184(para)
+msgid "The Filter Scheduler weights hosts based on the config option scheduler_weight_classes, this defaults to nova.scheduler.weights.all_weighers, which selects the only weigher available – the RamWeigher. Hosts are then weighted and sorted with the largest weight winning."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:189(para)
+msgid "Filter Scheduler finds local list of acceptable hosts by repeated filtering and weighing. Each time it chooses a host, it virtually consumes resources on it, so subsequent selections can adjust accordingly. It is useful if the customer asks for the same large amount of instances, because weight is computed for each instance requested."
+msgstr ""
+
+#: ./doc/training-guides/module001-ch009-vm-placement.xml:204(para)
+msgid "In the end Filter Scheduler sorts selected hosts by their weight and provisions instances on them."
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch012-associate-review-concept.xml:6(title)
+msgid "Review of Concepts"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch012-associate-review-concept.xml:8(title)
+msgid "Day 2, 16:00 to 17:00"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch017-developer-how-to-participate-day-seven-quiz.xml:6(title)
+msgid "Developer How To Participate Day Seven Quiz"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch017-developer-how-to-participate-day-seven-quiz.xml:8(title)
+msgid "Day 7, 16:40 to 17:00"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch011-associate-assessment.xml:8(title)
+msgid "Day 2, 15:00 to 16:00"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:8(emphasis)
+msgid "Network Types"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:9(para)
+msgid "The OpenStack Networking configuration provided by the Rackspace Private Cloud cookbooks allows you to choose between VLAN or GRE isolated networks, both provider- and tenant-specific. From the provider side, an administrator can also create a flat network."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:14(para)
+msgid "The type of network that is used for private tenant networks is determined by the network_type attribute, which can be edited in the Chef override_attributes. This attribute sets both the default provider network type and the only type of network that tenants are able to create. Administrators can always create flat and VLAN networks. GRE networks of any type require the network_type to be set to gre."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:21(emphasis)
+msgid "Namespaces"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:22(para)
+msgid "For each network you create, the Network node (or Controller node, if combined) will have a unique network namespace (netns) created by the DHCP and Metadata agents. The netns hosts an interface and IP addresses for dnsmasq and the quantum-ns-metadata-proxy. You can view the namespaces with the ip netns [list], and can interact with the namespaces with the ip netns exec &lt;namespace&gt; &lt;command&gt; command."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:30(emphasis)
+msgid "Metadata"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:31(para)
+msgid "Not all networks or VMs need metadata access. Rackspace recommends that you use metadata if you are using a single network. If you need metadata, you may also need a default route. (If you don't need a default route, no-gateway will do.)"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:36(para)
+msgid "To communicate with the metadata IP address inside the namespace, instances need a route for the metadata network that points to the dnsmasq IP address on the same namespaced interface. OpenStack Networking only injects a route when you do not specify a gateway-ip in the subnet."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:41(para)
+msgid "If you need to use a default route and provide instances with access to the metadata route, create the subnet without specifying a gateway IP and with a static route from 0.0.0.0/0 to your gateway IP address. Adjust the DHCP allocation pool so that it will not assign the gateway IP. With this configuration, dnsmasq will pass both routes to instances. This way, metadata will be routed correctly without any changes on the external gateway."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:49(emphasis)
+msgid "OVS Bridges"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:50(para)
+msgid "An OVS bridge for provider traffic is created and configured on the nodes where single-network-node and single-compute are applied. Bridges are created, but physical interfaces are not added. An OVS bridge is not created on a Controller-only node."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch002-openstack-networking-concepts.xml:55(para)
+msgid "When creating networks, you can specify the type and properties, such as Flat vs. VLAN, Shared vs. Tenant, or Provider vs. Overlay. These properties identify and determine the behavior and resources of instances attached to the network. The cookbooks will create bridges for the configuration that you specify, although they do not add physical interfaces to provider bridges. For example, if you specify a network type of GRE, a br-tun tunnel bridge will be created to handle overlay traffic."
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch018-developer-how-to-participate-day-eight-lab.xml:6(title)
+msgid "Developer How To Participate Lab Day Eight"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch018-developer-how-to-participate-day-eight-lab.xml:8(title)
+msgid "Day 8, 13:30 to 14:45, 15:00 to 16:30"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:231(None)
+msgid "@@image: 'figures/image33.png'; md5=e9843f38c9b2555e709357a724fc710d"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:9(para)
+msgid "OpenStack Networking provides a rich tenant-facing API for defining network connectivity and addressing in the cloud. The OpenStack Networking project gives operators the ability to leverage different networking technologies to power their cloud networking. It is a virtual network service that provides a powerful API to define the network connectivity and addressing used by devices from other services, such as OpenStack Compute. It has a rich API which consists of the following components."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:20(para)
+msgid "<emphasis role=\"bold\">Network:</emphasis> An isolated L2 segment, analogous to VLAN in the physical networking world."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:25(para)
+msgid "<emphasis role=\"bold\">Subnet:</emphasis> A block of v4 or v6 IP addresses and associated configuration state."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:30(para)
+msgid "<emphasis role=\"bold\">Port:</emphasis> A connection point for attaching a single device, such as the NIC of a virtual server, to a virtual network. Also describes the associated network configuration, such as the MAC and IP addresses to be used on that port."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:38(para)
+msgid "You can configure rich network topologies by creating and configuring networks and subnets, and then instructing other OpenStack services like OpenStack Compute to attach virtual devices to ports on these networks. In particular, OpenStack Networking supports each tenant having multiple private networks, and allows tenants to choose their own IP addressing scheme, even if those IP addresses overlap with those used by other tenants. This enables very advanced cloud networking use cases, such as building multi-tiered web applications and allowing applications to be migrated to the cloud without changing IP addresses."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:50(guilabel)
+msgid "Plugin Architecture: Flexibility to Choose Different Network Technologies"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:52(para)
+msgid "Enhancing traditional networking solutions to provide rich cloud networking is challenging. Traditional networking is not designed to scale to cloud proportions or to configure automatically."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:56(para)
+msgid "The original OpenStack Compute network implementation assumed a very basic model of performing all isolation through Linux VLANs and IP tables. OpenStack Networking introduces the concept of a plug-in, which is a pluggable back-end implementation of the OpenStack Networking API. A plug-in can use a variety of technologies to implement the logical API requests. Some OpenStack Networking plug-ins might use basic Linux VLANs and IP tables, while others might use more advanced technologies, such as L2-in-L3 tunneling or OpenFlow, to provide similar benefits."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:66(para)
+msgid "The current set of plug-ins include:"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:69(emphasis)
+msgid "Big Switch, Floodlight REST Proxy:"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:73(link)
+msgid "http://www.openflowhub.org/display/floodlightcontroller/Quantum+REST+Proxy+Plugin"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:76(emphasis)
+msgid "Brocade Plugin"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:80(para)
+msgid "<emphasis role=\"bold\">Cisco:</emphasis> Documented externally at: <link href=\"http://wiki.openstack.org/cisco-quantum\">http://wiki.openstack.org/cisco-quantum</link>"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:86(emphasis)
+msgid "Hyper-V Plugin"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:90(para)
+msgid "<emphasis role=\"bold\">Linux Bridge:</emphasis> Documentation included in this guide and <link href=\"http://wiki.openstack.org/Quantum-Linux-Bridge-Plugin\">http://wiki.openstack.org/Quantum-Linux-Bridge-Plugin</link>"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:97(emphasis)
+msgid "Midonet Plugin"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:101(emphasis)
+msgid "NEC OpenFlow:"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:104(link)
+msgid "http://wiki.openstack.org/Quantum-NEC-OpenFlow-Plugin"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:107(para)
+msgid "<emphasis role=\"bold\">Open vSwitch:</emphasis> Documentation included in this guide."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:111(emphasis)
+msgid "PLUMgrid:"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:114(link)
+msgid "https://wiki.openstack.org/wiki/Plumgrid-quantum"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:117(emphasis)
+msgid "Ryu:"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:120(link)
+msgid "https://github.com/osrg/ryu/wiki/OpenStack"
+msgstr ""
+
+#. TODO: Update support link, when available
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:124(para)
+msgid "<emphasis role=\"bold\">VMware NSX:</emphasis> Documentation include in this guide, <link href=\"http://www.vmware.com/products/nsx\">NSX Product Overview </link>, and <link href=\"http://www.nicira.com/support\">NSX Product Support</link>."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:132(para)
+msgid "Plugins can have different properties in terms of hardware requirements, features, performance, scale, operator tools, etc. Supporting many plug-ins enables the cloud administrator to weigh different options and decide which networking technology is right for the deployment."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:137(para)
+msgid "Components of OpenStack Networking"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:138(para)
+msgid "To deploy OpenStack Networking, it is useful to understand the different components that make up the solution and how those components interact with each other and with other OpenStack services."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:142(para)
+msgid "OpenStack Networking is a standalone service, just like other OpenStack services such as OpenStack Compute, OpenStack Image Service, OpenStack Identity service, and the OpenStack Dashboard. Like those services, a deployment of OpenStack Networking often involves deploying several processes on a variety of hosts."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:148(para)
+msgid "The main process of the OpenStack Networking server is quantum-server, which is a Python daemon that exposes the OpenStack Networking API and passes user requests to the configured OpenStack Networking plug-in for additional processing. Typically, the plug-in requires access to a database for persistent storage, similar to other OpenStack services."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:155(para)
+msgid "If your deployment uses a controller host to run centralized OpenStack Compute components, you can deploy the OpenStack Networking server on that same host. However, OpenStack Networking is entirely standalone and can be deployed on its own server as well. OpenStack Networking also includes additional agents that might be required depending on your deployment:"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:164(para)
+msgid "<emphasis role=\"bold\">plugin agent (quantum-*-agent):</emphasis>Runs on each hypervisor to perform local vswitch configuration. Agent to be run depends on which plug-in you are using, as some plug-ins do not require an agent."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:171(para)
+msgid "<emphasis role=\"bold\">dhcp agent (quantum-dhcp-agent):</emphasis>Provides DHCP services to tenant networks. This agent is the same across all plug-ins."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:177(para)
+msgid "<emphasis role=\"bold\">l3 agent (quantum-l3-agent):</emphasis>Provides L3/NAT forwarding to provide external network access for VMs on tenant networks. This agent is the same across all plug-ins."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:184(para)
+msgid "These agents interact with the main quantum-server process in the following ways:"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:188(para)
+msgid "Through RPC. For example, rabbitmq or qpid."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:191(para)
+msgid "Through the standard OpenStack Networking API."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:195(para)
+msgid "OpenStack Networking relies on the OpenStack Identity Project (Keystone) for authentication and authorization of all API request."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:198(para)
+msgid "OpenStack Compute interacts with OpenStack Networking through calls to its standard API. As part of creating a VM, nova-compute communicates with the OpenStack Networking API to plug each virtual NIC on the VM into a particular network."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:203(para)
+msgid "The OpenStack Dashboard (Horizon) has integration with the OpenStack Networking API, allowing administrators and tenant users, to create and manage network services through the Horizon GUI."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:207(emphasis)
+msgid "Place Services on Physical Hosts"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:209(para)
+msgid "Like other OpenStack services, OpenStack Networking provides cloud administrators with significant flexibility in deciding which individual services should run on which physical devices. On one extreme, all service daemons can be run on a single physical host for evaluation purposes. On the other, each service could have its own physical hosts, and some cases be replicated across multiple hosts for redundancy."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:216(para)
+msgid "In this guide, we focus primarily on a standard architecture that includes a “cloud controller” host, a “network gateway” host, and a set of hypervisors for running VMs. The \"cloud controller\" and \"network gateway\" can be combined in simple deployments, though if you expect VMs to send significant amounts of traffic to or from the Internet, a dedicated network gateway host is suggested to avoid potential CPU contention between packet forwarding performed by the quantum-l3-agent and other OpenStack services."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:225(emphasis)
+msgid "Network Connectivity for Physical Hosts"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:235(para)
+msgid "A standard OpenStack Networking setup has up to four distinct physical data center networks:"
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:239(para)
+msgid "<emphasis role=\"bold\">Management network:</emphasis>Used for internal communication between OpenStack Components. The IP addresses on this network should be reachable only within the data center."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:246(para)
+msgid "<emphasis role=\"bold\">Data network:</emphasis>Used for VM data communication within the cloud deployment. The IP addressing requirements of this network depend on the OpenStack Networking plug-in in use."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:252(para)
+msgid "<emphasis role=\"bold\">External network:</emphasis>Used to provide VMs with Internet access in some deployment scenarios. The IP addresses on this network should be reachable by anyone on the Internet."
+msgstr ""
+
+#: ./doc/training-guides/module002-ch001-networking-in-openstack.xml:259(para)
+msgid "<emphasis role=\"bold\">API network:</emphasis>Exposes all OpenStack APIs, including the OpenStack Networking API, to tenants. The IP addresses on this network should be reachable by anyone on the Internet. This may be the same network as the external network, as it is possible to create a subnet for the external network that uses IP allocation ranges to use only less than the full range of IP addresses in an IP block."
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch016-developer-how-to-participate-day-seven-lab.xml:6(title)
+msgid "Developer How To Participate Lab Day Seven"
+msgstr ""
+
+#: ./doc/training-guides/bk003-ch016-developer-how-to-participate-day-seven-lab.xml:8(title)
+msgid "Day 7, 13:30 to 14:45, 15:00 to 16:30"
+msgstr ""
+
+#: ./doc/training-guides/bk002-ch009-operator-compute-node-quiz.xml:6(title) ./doc/training-guides/bk001-ch006-associate-compute-node-quiz.xml:6(title)
+msgid "Compute Node Quiz"
+msgstr ""
+
+#: ./doc/training-guides/bk002-ch009-operator-compute-node-quiz.xml:8(title)
+msgid "Days 5 to 6, 16:40 to 17:00"
+msgstr ""
+
 #: ./doc/training-guides/card038.xml:7(title)
 msgid "Install and configure OpenStack Identity Service in the Controller Node"
 msgstr ""
 
-#: ./doc/training-guides/sources/cinder/development.environment.xml:7(title)
-msgid "Development.Environment"
+#: ./doc/training-guides/card025.xml:6(title)
+msgid "Role of the Controller Node"
 msgstr ""
 
-#: ./doc/training-guides/sources/cinder/development.environment.xml:9(title) ./doc/training-guides/sources/cinder/unit_tests.xml:9(title) ./doc/training-guides/sources/cinder/architecture.xml:9(title) ./doc/training-guides/sources/cinder/threading.xml:9(title)
+#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:10(title)
+msgid "Day 1, 11:15 to 12:30, 13:30 to 14:45"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:37(title)
+msgid "Identity CI Commands"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:44(title)
+msgid "Identity User Management"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:51(title)
+msgid "Image CLI Commands"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:58(title)
+msgid "Image List Images"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:65(title)
+msgid "Image Adding Images"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:72(title)
+msgid "Image Manage Images"
+msgstr ""
+
+#: ./doc/training-guides/bk001-ch003-associate-controller-node.xml:79(title)
+msgid "Message Queue Configuration"
+msgstr ""
+
+#: ./doc/training-guides/card043-ovs-in-network-node.xml:7(title)
+msgid "OVS Installation and Configuration in Network node"
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/architecture.xml:7(title)
+msgid "Architecture"
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/architecture.xml:9(title) ./doc/training-guides/sources/cinder/development.environment.xml:9(title) ./doc/training-guides/sources/cinder/unit_tests.xml:9(title) ./doc/training-guides/sources/cinder/threading.xml:9(title)
 msgid "Header"
 msgstr ""
 
+#: ./doc/training-guides/sources/cinder/architecture.xml:10(para)
+msgid "Copyright 2010-2011 United States Government as represented by the Administrator of the National Aeronautics and Space Administration. All Rights Reserved. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License."
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/architecture.xml:26(title)
+msgid "Block Storage System Architecture"
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/architecture.xml:27(para)
+msgid "The OpenStack Block Storage service is intended to run on one or more nodes. Block Storage uses a SQL-based central database that is shared by all Block Storage services in the system. The amount and depth of the data fits into a SQL database quite well. For small deployments this seems like an optimal solution. For larger deployments, and especially if security is a concern, Block Storage will be moving towards multiple data stores with some kind of aggregation system."
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/architecture.xml:33(title)
+msgid "Components"
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/architecture.xml:52(para)
+msgid "DB: SQL database for data storage. Used by all components (LINKS NOT SHOWN)"
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/architecture.xml:56(para)
+msgid "Web Dashboard: potential external component that talks to the API"
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/architecture.xml:60(para)
+msgid "API: component that receives HTTP requests, converts commands and communicates with other components via the queue or HTTP"
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/architecture.xml:64(para)
+msgid "Auth Manager: component responsible for users/projects/and roles. Can use as back-end a database or LDAP. This is not a separate binary, but rather a python class that is used by most components in the system."
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/architecture.xml:70(para)
+msgid "scheduler: decides which host gets each volume"
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/architecture.xml:73(para)
+msgid "volume: manages dynamically attachable block devices."
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/architecture.xml:34(para)
+msgid "Below you will a brief explanation of the different components. /- ( LDAP ) [ Auth Manager ] --- | \\- ( DB ) | | cinderclient | / \\ | [ Web Dashboard ]- -[ API ] -- [ AMQP ] -- [ scheduler ] -- [ volume ] -- ( iSCSI ) \\ / | novaclient | | | | [ REST ] <placeholder-1/>"
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/development.environment.xml:7(title)
+msgid "Development.Environment"
+msgstr ""
+
 #: ./doc/training-guides/sources/cinder/development.environment.xml:10(para)
 msgid ".. Copyright 2010-2011 United States Government as represented by the Administrator of the National Aeronautics and Space Administration. All Rights Reserved. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License."
 msgstr ""
@@ -8977,6 +9025,98 @@ msgstr ""
 msgid "---------------------- Once your work is complete you may wish to contribute it to the project. Add your name and email address to the ``Authors`` file, and also to the ``.mailmap`` file if you use multiple email addresses. Your contributions can not be merged into trunk unless you are listed in the Authors file. Cinder uses the Gerrit code review system. For information on how to submit your branch to Gerrit, see GerritWorkflow_."
 msgstr ""
 
+#: ./doc/training-guides/sources/cinder/unit_tests.xml:7(title)
+msgid "Unit_Tests"
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/unit_tests.xml:14(title)
+msgid "Unit-Tests"
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/unit_tests.xml:15(para)
+msgid "========== Cinder contains a suite of unit tests, in the cinder/tests directory. Any proposed code change will be automatically rejected by the OpenStack Jenkins server [#f1]_ if the change causes unit test failures."
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/unit_tests.xml:23(title)
+msgid "Running-The-Tests"
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/unit_tests.xml:24(para)
+msgid "----------------- Run the unit tests by doing:: ./run_tests.sh This script is a wrapper around the `nose`_ testrunner and the `pep8`_ checker. .. _nose: http://code.google.com/p/python-nose/ .. _pep8: https://github.com/jcrocholl/pep8 Flags ----- The ``run_tests.sh`` script supports several flags. You can view a list of flags by doing:: run_tests.sh -h This will show the following help information:: Usage: ./run_tests.sh [OPTION]... Run Cinder's test suite(s) -V, --virtual-env Always use virtualenv. Install automatically if not present -N, --no-virtual-env Don't use virtualenv. Run tests in local environment -s, --no-site-packages Isolate the virtualenv from the global Python environment -r, --recreate-db Recreate the test database (deprecated, as this is now the default). -n, --no-recreate-db Don't recreate the test database. -x, --stop Stop running tests after the first error or failure. -f, --force Force a clean re-build of the virtual environment. Useful when dependencies have been added. -p, --pep8 Just run pep8 -P, --no-pep8 Don't run pep8 -c, --coverage Generate coverage report -h, --help Print this usage message --hide-elapsed Don't print the elapsed time for each test along with slow test list Because ``run_tests.sh`` is a wrapper around nose, it also accepts the same flags as nosetests. See the `nose options documentation`_ for details about these additional flags. .. _nose options documentation: http://readthedocs.org/docs/nose/en/latest/usage.html#options"
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/unit_tests.xml:58(title)
+msgid "Running-A-Subset-Of-Tests"
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/unit_tests.xml:59(para)
+msgid "------------------------- Instead of running all tests, you can specify an individual directory, file, class, or method that contains test code. To run the tests in the ``cinder/tests/scheduler`` directory:: ./run_tests.sh scheduler To run the tests in the ``cinder/tests/test_libvirt.py`` file:: ./run_tests.sh test_libvirt To run the tests in the `HostStateTestCase` class in ``cinder/tests/test_libvirt.py``:: ./run_tests.sh test_libvirt:HostStateTestCase To run the `ToPrimitiveTestCase.test_dict` test method in ``cinder/tests/test_utils.py``:: ./run_tests.sh test_utils:ToPrimitiveTestCase.test_dict"
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/unit_tests.xml:76(title)
+msgid "Suppressing-Logging-Output-When-Tests-Fail"
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/unit_tests.xml:77(para)
+msgid "------------------------------------------ By default, when one or more unit test fails, all of the data sent to the logger during the failed tests will appear on standard output, which typically consists of many lines of text. The logging output can make it difficult to identify which specific tests have failed, unless your terminal has a large scrollback buffer or you have redirected output to a file. You can suppress the logging output by calling ``run_tests.sh`` with the nose flag:: --nologcapture"
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/unit_tests.xml:90(title)
+msgid "Virtualenv"
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/unit_tests.xml:91(para)
+msgid "---------- By default, the tests use the Python packages installed inside a virtualenv [#f2]_. (This is equivalent to using the ``-V, --virtualenv`` flag). If the virtualenv does not exist, it will be created the first time the tests are run. If you wish to recreate the virtualenv, call ``run_tests.sh`` with the flag:: -f, --force Recreating the virtualenv is useful if the package dependencies have changed since the virtualenv was last created. If the ``requirements.txt`` or ``tools/install_venv.py`` files have changed, it's a good idea to recreate the virtualenv. By default, the unit tests will see both the packages in the virtualenv and the packages that have been installed in the Python global environment. In some cases, the packages in the Python global environment may cause a conflict with the packages in the virtualenv. If this occurs, you can isolate the virtualenv from the global environment by using the flag:: -s, --no-site packages If you do not wish to use a virtualenv at all, use the flag:: -N, --no-virtual-env"
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/unit_tests.xml:113(title)
+msgid "Database"
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/unit_tests.xml:114(para)
+msgid "-------- Some of the unit tests make queries against a SQLite database [#f3]_. By default, the test database (``tests.sqlite``) is deleted and recreated each time ``run_tests.sh`` is invoked (This is equivalent to using the ``-r, --recreate-db`` flag). To reduce testing time if a database already exists it can be reused by using the flag:: -n, --no-recreate-db Reusing an existing database may cause tests to fail if the schema has changed. If any files in the ``cinder/db/sqlalchemy`` have changed, it's a good idea to recreate the test database."
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/unit_tests.xml:128(title)
+msgid "Gotchas"
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/unit_tests.xml:129(para)
+msgid "------- <placeholder-1/> If you are running the unit tests from a shared folder, you may see tests start to fail or stop completely as a result of Python lockfile issues [#f4]_. You can get around this by manually setting or updating the following line in ``cinder/tests/conf_fixture.py``:: CONF['lock_path'].SetDefault('/tmp') Note that you may use any location (not just ``/tmp``!) as long as it is not a shared folder. .. rubric:: Footnotes .. [#f1] See :doc:`jenkins`. .. [#f2] See :doc:`development.environment` for more details about the use of virtualenv. .. [#f3] There is an effort underway to use a fake DB implementation for the unit tests. See https://lists.launchpad.net/openstack/msg05604.html"
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/threading.xml:7(title)
+msgid "Threading"
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/threading.xml:14(title)
+msgid "Threading-Model"
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/threading.xml:18(para)
+msgid "model of threading, implemented"
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/threading.xml:15(para)
+msgid "=============== <placeholder-1/> through using the Python `eventlet [http://eventlet.net/]`_ and `greenlet [http://packages.python.org/greenlet/]`_ libraries. Green threads use a cooperative model of threading: thread context switches can only occur when specific eventlet or greenlet library calls are made. For example, sleep and certain I/O calls. From the operating system's point of view, each OpenStack service runs in a single thread. The use of green threads reduces the likelihood of race conditions, but does not completely eliminate them. In some cases, you may need to use the ``@utils.synchronized(...)`` decorator to avoid races. In addition, since there is only one operating system thread, a call that blocks that main thread will block the entire process."
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/threading.xml:34(title)
+msgid "Yielding-The-Thread-In-Long-Running-Tasks"
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/threading.xml:35(para)
+msgid "----------------------------------------- If a code path takes a long time to execute and does not contain any methods that trigger an eventlet context switch, the long-running thread will block any pending threads. This scenario can be avoided by adding calls to the eventlet sleep method in the long-running code path. The sleep call will trigger a context switch if there are pending threads, and using an argument of 0 will avoid introducing delays in the case that there is only a single green thread:: from eventlet import greenthread ... greenthread.sleep(0)"
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/threading.xml:50(title)
+msgid "Mysql-Access-And-Eventlet"
+msgstr ""
+
+#: ./doc/training-guides/sources/cinder/threading.xml:51(para)
+msgid "------------------------- Queries to the MySQL database will block the main thread of a service. This is because OpenStack services use an external C library for accessing the MySQL database. Since eventlet cannot use monkey-patching to intercept blocking calls in a C library, the resulting database query blocks the thread. The Diablo release contained a thread-pooling implementation that did not block, but this implementation resulted in a `bug`_ and was removed. See this `mailing list thread`_ for a discussion of this issue, including a discussion of the `impact on performance`_. .. _bug: https://bugs.launchpad.net/cinder/+bug/838581 .. _mailing list thread: https://lists.launchpad.net/openstack/msg08118.html"
+msgstr ""
+
 #: ./doc/training-guides/sources/cinder/drivers.xml:6(title)
 msgid "Drivers"
 msgstr ""
@@ -9088,148 +9228,8 @@ msgstr ""
 msgid "If the driver cannot provide a value for <literal>free_capacity_gb</literal> or <literal>total_capacity_gb</literal>, the driver can provide keywords instead. If the array cannot report the value, use <literal>unknown</literal>. If the array has no upper limit, use <literal>infinite</literal>."
 msgstr ""
 
-#: ./doc/training-guides/sources/cinder/unit_tests.xml:7(title)
-msgid "Unit_Tests"
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/unit_tests.xml:14(title)
-msgid "Unit-Tests"
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/unit_tests.xml:15(para)
-msgid "========== Cinder contains a suite of unit tests, in the cinder/tests directory. Any proposed code change will be automatically rejected by the OpenStack Jenkins server [#f1]_ if the change causes unit test failures."
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/unit_tests.xml:23(title)
-msgid "Running-The-Tests"
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/unit_tests.xml:24(para)
-msgid "----------------- Run the unit tests by doing:: ./run_tests.sh This script is a wrapper around the `nose`_ testrunner and the `pep8`_ checker. .. _nose: http://code.google.com/p/python-nose/ .. _pep8: https://github.com/jcrocholl/pep8 Flags ----- The ``run_tests.sh`` script supports several flags. You can view a list of flags by doing:: run_tests.sh -h This will show the following help information:: Usage: ./run_tests.sh [OPTION]... Run Cinder's test suite(s) -V, --virtual-env Always use virtualenv. Install automatically if not present -N, --no-virtual-env Don't use virtualenv. Run tests in local environment -s, --no-site-packages Isolate the virtualenv from the global Python environment -r, --recreate-db Recreate the test database (deprecated, as this is now the default). -n, --no-recreate-db Don't recreate the test database. -x, --stop Stop running tests after the first error or failure. -f, --force Force a clean re-build of the virtual environment. Useful when dependencies have been added. -p, --pep8 Just run pep8 -P, --no-pep8 Don't run pep8 -c, --coverage Generate coverage report -h, --help Print this usage message --hide-elapsed Don't print the elapsed time for each test along with slow test list Because ``run_tests.sh`` is a wrapper around nose, it also accepts the same flags as nosetests. See the `nose options documentation`_ for details about these additional flags. .. _nose options documentation: http://readthedocs.org/docs/nose/en/latest/usage.html#options"
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/unit_tests.xml:58(title)
-msgid "Running-A-Subset-Of-Tests"
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/unit_tests.xml:59(para)
-msgid "------------------------- Instead of running all tests, you can specify an individual directory, file, class, or method that contains test code. To run the tests in the ``cinder/tests/scheduler`` directory:: ./run_tests.sh scheduler To run the tests in the ``cinder/tests/test_libvirt.py`` file:: ./run_tests.sh test_libvirt To run the tests in the `HostStateTestCase` class in ``cinder/tests/test_libvirt.py``:: ./run_tests.sh test_libvirt:HostStateTestCase To run the `ToPrimitiveTestCase.test_dict` test method in ``cinder/tests/test_utils.py``:: ./run_tests.sh test_utils:ToPrimitiveTestCase.test_dict"
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/unit_tests.xml:76(title)
-msgid "Suppressing-Logging-Output-When-Tests-Fail"
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/unit_tests.xml:77(para)
-msgid "------------------------------------------ By default, when one or more unit test fails, all of the data sent to the logger during the failed tests will appear on standard output, which typically consists of many lines of text. The logging output can make it difficult to identify which specific tests have failed, unless your terminal has a large scrollback buffer or you have redirected output to a file. You can suppress the logging output by calling ``run_tests.sh`` with the nose flag:: --nologcapture"
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/unit_tests.xml:90(title)
-msgid "Virtualenv"
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/unit_tests.xml:91(para)
-msgid "---------- By default, the tests use the Python packages installed inside a virtualenv [#f2]_. (This is equivalent to using the ``-V, --virtualenv`` flag). If the virtualenv does not exist, it will be created the first time the tests are run. If you wish to recreate the virtualenv, call ``run_tests.sh`` with the flag:: -f, --force Recreating the virtualenv is useful if the package dependencies have changed since the virtualenv was last created. If the ``requirements.txt`` or ``tools/install_venv.py`` files have changed, it's a good idea to recreate the virtualenv. By default, the unit tests will see both the packages in the virtualenv and the packages that have been installed in the Python global environment. In some cases, the packages in the Python global environment may cause a conflict with the packages in the virtualenv. If this occurs, you can isolate the virtualenv from the global environment by using the flag:: -s, --no-site packages If you do not wish to use a virtualenv at all, use the flag:: -N, --no-virtual-env"
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/unit_tests.xml:113(title)
-msgid "Database"
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/unit_tests.xml:114(para)
-msgid "-------- Some of the unit tests make queries against a SQLite database [#f3]_. By default, the test database (``tests.sqlite``) is deleted and recreated each time ``run_tests.sh`` is invoked (This is equivalent to using the ``-r, --recreate-db`` flag). To reduce testing time if a database already exists it can be reused by using the flag:: -n, --no-recreate-db Reusing an existing database may cause tests to fail if the schema has changed. If any files in the ``cinder/db/sqlalchemy`` have changed, it's a good idea to recreate the test database."
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/unit_tests.xml:128(title)
-msgid "Gotchas"
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/unit_tests.xml:129(para)
-msgid "------- <placeholder-1/> If you are running the unit tests from a shared folder, you may see tests start to fail or stop completely as a result of Python lockfile issues [#f4]_. You can get around this by manually setting or updating the following line in ``cinder/tests/conf_fixture.py``:: CONF['lock_path'].SetDefault('/tmp') Note that you may use any location (not just ``/tmp``!) as long as it is not a shared folder. .. rubric:: Footnotes .. [#f1] See :doc:`jenkins`. .. [#f2] See :doc:`development.environment` for more details about the use of virtualenv. .. [#f3] There is an effort underway to use a fake DB implementation for the unit tests. See https://lists.launchpad.net/openstack/msg05604.html"
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/architecture.xml:7(title)
-msgid "Architecture"
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/architecture.xml:10(para)
-msgid "Copyright 2010-2011 United States Government as represented by the Administrator of the National Aeronautics and Space Administration. All Rights Reserved. Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License."
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/architecture.xml:26(title)
-msgid "Block Storage System Architecture"
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/architecture.xml:27(para)
-msgid "The OpenStack Block Storage service is intended to run on one or more nodes. Block Storage uses a SQL-based central database that is shared by all Block Storage services in the system. The amount and depth of the data fits into a SQL database quite well. For small deployments this seems like an optimal solution. For larger deployments, and especially if security is a concern, Block Storage will be moving towards multiple data stores with some kind of aggregation system."
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/architecture.xml:33(title)
-msgid "Components"
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/architecture.xml:52(para)
-msgid "DB: SQL database for data storage. Used by all components (LINKS NOT SHOWN)"
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/architecture.xml:56(para)
-msgid "Web Dashboard: potential external component that talks to the API"
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/architecture.xml:60(para)
-msgid "API: component that receives HTTP requests, converts commands and communicates with other components via the queue or HTTP"
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/architecture.xml:64(para)
-msgid "Auth Manager: component responsible for users/projects/and roles. Can use as back-end a database or LDAP. This is not a separate binary, but rather a python class that is used by most components in the system."
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/architecture.xml:70(para)
-msgid "scheduler: decides which host gets each volume"
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/architecture.xml:73(para)
-msgid "volume: manages dynamically attachable block devices."
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/architecture.xml:34(para)
-msgid "Below you will a brief explanation of the different components. /- ( LDAP ) [ Auth Manager ] --- | \\- ( DB ) | | cinderclient | / \\ | [ Web Dashboard ]- -[ API ] -- [ AMQP ] -- [ scheduler ] -- [ volume ] -- ( iSCSI ) \\ / | novaclient | | | | [ REST ] <placeholder-1/>"
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/threading.xml:7(title)
-msgid "Threading"
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/threading.xml:14(title)
-msgid "Threading-Model"
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/threading.xml:18(para)
-msgid "model of threading, implemented"
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/threading.xml:15(para)
-msgid "=============== <placeholder-1/> through using the Python `eventlet [http://eventlet.net/]`_ and `greenlet [http://packages.python.org/greenlet/]`_ libraries. Green threads use a cooperative model of threading: thread context switches can only occur when specific eventlet or greenlet library calls are made. For example, sleep and certain I/O calls. From the operating system's point of view, each OpenStack service runs in a single thread. The use of green threads reduces the likelihood of race conditions, but does not completely eliminate them. In some cases, you may need to use the ``@utils.synchronized(...)`` decorator to avoid races. In addition, since there is only one operating system thread, a call that blocks that main thread will block the entire process."
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/threading.xml:34(title)
-msgid "Yielding-The-Thread-In-Long-Running-Tasks"
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/threading.xml:35(para)
-msgid "----------------------------------------- If a code path takes a long time to execute and does not contain any methods that trigger an eventlet context switch, the long-running thread will block any pending threads. This scenario can be avoided by adding calls to the eventlet sleep method in the long-running code path. The sleep call will trigger a context switch if there are pending threads, and using an argument of 0 will avoid introducing delays in the case that there is only a single green thread:: from eventlet import greenthread ... greenthread.sleep(0)"
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/threading.xml:50(title)
-msgid "Mysql-Access-And-Eventlet"
-msgstr ""
-
-#: ./doc/training-guides/sources/cinder/threading.xml:51(para)
-msgid "------------------------- Queries to the MySQL database will block the main thread of a service. This is because OpenStack services use an external C library for accessing the MySQL database. Since eventlet cannot use monkey-patching to intercept blocking calls in a C library, the resulting database query blocks the thread. The Diablo release contained a thread-pooling implementation that did not block, but this implementation resulted in a `bug`_ and was removed. See this `mailing list thread`_ for a discussion of this issue, including a discussion of the `impact on performance`_. .. _bug: https://bugs.launchpad.net/cinder/+bug/838581 .. _mailing list thread: https://lists.launchpad.net/openstack/msg08118.html"
-msgstr ""
-
 #. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
-#: ./doc/training-guides/sources/cinder/threading.xml:0(None)
+#: ./doc/training-guides/sources/cinder/drivers.xml:0(None)
 msgid "translator-credits"
 msgstr ""
 
diff --git a/doc/user-guide-admin/locale/ja.po b/doc/user-guide-admin/locale/ja.po
index b2db35f366..5388c95223 100644
--- a/doc/user-guide-admin/locale/ja.po
+++ b/doc/user-guide-admin/locale/ja.po
@@ -4,7 +4,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: OpenStack Manuals\n"
-"POT-Creation-Date: 2014-06-02 05:42+0000\n"
+"POT-Creation-Date: 2014-06-03 02:30+0000\n"
 "PO-Revision-Date: 2014-06-02 05:11+0000\n"
 "Last-Translator: Tomoyuki KATO <tomo@dream.daynight.jp>\n"
 "Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n"
@@ -14,42 +14,1124 @@ msgstr ""
 "Language: ja\n"
 "Plural-Forms: nplurals=1; plural=0;\n"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml8(title)
-msgid "Create and manage roles"
-msgstr "ロールの作成と管理"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml7(title)
+msgid "Create and manage images"
+msgstr "イメージの作成と管理"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml9(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml8(para)
 msgid ""
-"A role is a personality that a user assumes to perform a specific set of "
-"operations. A role includes a set of rights and privileges. A user assuming "
-"that role inherits those rights and privileges."
-msgstr "ロールは、ユーザーが特定の操作の組を実行すると仮定する人格です。ロールは一組の権利と権限を含みます。そのロールを仮定しているユーザーは、それらの権利と権限を継承します。"
+"As an administrative user, you can create and manage images for the projects"
+" to which you belong. You can also create and manage images for users in all"
+" projects to which you have access."
+msgstr "管理ユーザーとして、所属するプロジェクト用のイメージを作成、管理できます。また、アクセス権を持つすべてのプロジェクトのユーザー用にイメージを作成、管理できます。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml13(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml12(para)
 msgid ""
-"OpenStack Identity service defines a user's role on a project but it is "
-"completely up to the individual service to define what that role means. This"
-" is referred to as the service's policy. To get details about what the "
-"privileges for each role are, refer to the <filename>policy.json</filename> "
-"file available for each service in the "
-"<filename>/etc/<replaceable>SERVICE</replaceable>/policy.json</filename> "
-"file. For example, the policy defined for OpenStack Identity service is "
-"defined in the <filename>/etc/keystone/policy.json</filename> file."
-msgstr "OpenStack Identity は、プロジェクトにユーザーのロールを定義します。しかし、そのロールの意味を定義することは、完全に個々のサービス次第です。これは、サービスのポリシーとして参照されます。各ロールの権限の詳細を取得する場合、各サービスの <filename>/etc/<replaceable>SERVICE</replaceable>/policy.json</filename> ファイルで利用可能な <filename>policy.json</filename> ファイルを参照してください。例えば、OpenStack Identity に定義されているポリシーは、<filename>/etc/keystone/policy.json</filename> ファイルに定義されています。"
+"To create and manage images in specified projects as an end user, see the "
+"<link href=\"http://docs.openstack.org/user-"
+"guide/content/\"><citetitle>OpenStack End User Guide</citetitle></link>."
+msgstr "エンドユーザーとして指定したプロジェクトにイメージを作成、管理する方法は、<link href=\"http://docs.openstack.org/user-guide/content/\"><citetitle>OpenStack エンドユーザーガイド</citetitle></link>を参照してください。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml24(title)
-msgid "Create a role"
-msgstr "ロールの作成"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml17(para)
+msgid ""
+"To create and manage images as an administrator for other users, use the "
+"following procedures."
+msgstr "管理者として他のユーザー向けにイメージを作成、管理するために、以下の手順を使用します。"
 
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml20(title)
+msgid "Create images"
+msgstr "イメージの作成"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml21(para)
+msgid ""
+"For details about image creation, see the <link "
+"href=\"http://docs.openstack.org/image-guide/content/\"><citetitle>Virtual "
+"Machine Image Guide</citetitle></link>."
+msgstr "イメージの作成に関する詳細は<link href=\"http://docs.openstack.org/image-guide/content/\"><citetitle>仮想マシンイメージガイド</citetitle></link>を参照してください。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml27(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml104(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml134(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml125(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml250(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml278(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml20(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml108(para)
+msgid "Log in to the dashboard."
+msgstr "ダッシュボードにログインします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml28(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml105(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml135(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml126(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml251(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml279(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml21(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml109(para)
+msgid ""
+"Choose the <guilabel>admin</guilabel> project from the <guilabel>CURRENT "
+"PROJECT</guilabel> drop-down list."
+msgstr "<guilabel>現在のプロジェクト</guilabel>ドロップダウンリストから <guilabel>admin</guilabel> プロジェクトを選択します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml33(para)
+msgid ""
+"On the <guilabel>Admin</guilabel> tab, click the <guilabel>Images</guilabel>"
+" category. The images that you can administer for cloud users appear on this"
+" page."
+msgstr "<guilabel>管理</guilabel>タブで、<guilabel>Images</guilabel>カテゴリーをクリックします。あなたがクラウドユーザー向けに管理できるイメージが、このページに表示されます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml38(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml94(para)
+msgid "Click <guibutton>Create Image</guibutton>."
+msgstr "<guibutton>イメージの作成</guibutton>をクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml41(para)
+msgid ""
+"In the <guilabel>Create An Image</guilabel> window, enter or select the "
+"following values:"
+msgstr "<guilabel>イメージの作成</guilabel>ウィンドウで以下の値を入力または選択します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml48(guilabel)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml154(guilabel)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml45(guilabel)
+#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml43(para)
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml29(term)
+msgid "Name"
+msgstr "名前"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml49(para)
+msgid "Enter a name for the image."
+msgstr "イメージの名前を入力します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml52(guilabel)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml22(th)
+#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml49(para)
+msgid "Description"
+msgstr "説明"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml53(para)
+msgid "Enter a brief description about the image."
+msgstr "イメージの簡単な説明を入力します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml57(guilabel)
+msgid "Image Source"
+msgstr "イメージソース"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml58(para)
+msgid ""
+"Choose the image source from the dropdown list. Your choices are "
+"<guilabel>Image Location</guilabel> and <guilabel>Image File</guilabel>."
+msgstr "ドロップダウンリストからイメージのソースを選択します。<guilabel>イメージの場所</guilabel>と<guilabel>イメージファイル</guilabel>を選択できます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml63(para)
+msgid "<guilabel>Image File</guilabel> or <guilabel>Image Location</guilabel>"
+msgstr "<guilabel>イメージファイル</guilabel>または<guilabel>イメージの場所</guilabel>"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml66(para)
+msgid ""
+"Based on your selection, there is an <guilabel>Image File </guilabel> or "
+"<guilabel>Image Location</guilabel> field. You can include the location URL "
+"or browse for the image file on your file system and add it."
+msgstr "選択した内容に応じて、<guilabel>イメージのファイル</guilabel>や<guilabel>イメージの場所</guilabel>の項目が表示されます。場所の URL を指定したり、お使いのファイルシステムにあるイメージファイルを参照して追加したりできます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml72(guilabel)
+msgid "Format"
+msgstr "形式"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml73(para)
+msgid "Select the image format."
+msgstr "イメージの形式を選択します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml76(para)
+msgid ""
+"<guilabel>Minimum Disk (GB)</guilabel> and <guilabel>Minimum RAM "
+"(MB)</guilabel>"
+msgstr "<guilabel>最小ディスク (GB)</guilabel> および<guilabel>最小メモリ (MB)</guilabel>"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml78(para)
+msgid "Leave these fields empty."
+msgstr "この項目を空白のままにします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml82(guilabel)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml95(para)
+msgid "Public"
+msgstr "パブリック"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml83(para)
+msgid "Select this option to make the image public to all users."
+msgstr "すべてのユーザーにイメージを公開する場合、このオプションを選択します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml86(guilabel)
+msgid "Protected"
+msgstr "保護"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml87(para)
+msgid ""
+"Select this option to ensure that only users with permissions can delete it."
+msgstr "権限を持つユーザーのみがこのイメージを削除できるようにする場合、このオプションを選択します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml95(para)
+msgid ""
+"The image is queued to be uploaded. It might take some time before the "
+"status changes from queued to active."
+msgstr "イメージがアップロードのためにキューに入れられます。ステータスがキュー済みからアクティブに変更されるまでに少し時間がかかるかもしれません。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml101(title)
+msgid "Update images"
+msgstr "イメージの更新"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml110(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml140(para)
+msgid ""
+"On the <guilabel>Admin</guilabel> tab, click the <guilabel>Images</guilabel>"
+" category."
+msgstr "<guilabel>管理</guilabel>タブで、<guilabel>イメージ</guilabel>カテゴリーをクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml114(para)
+msgid ""
+"Select the image that you want to edit. Click <guilabel>Edit</guilabel>."
+msgstr "編集したいイメージを選択します。<guilabel>編集</guilabel>をクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml118(para)
+msgid ""
+"In the <guilabel>Update Image</guilabel> window, you can change the name for"
+" the image. Select the <guilabel>Public</guilabel> check box to make the "
+"image public. Clear this check box to make the image private. You cannot "
+"change the kernel ID, RAM disk ID, or architecture attributes for an image."
+msgstr "<guilabel>イメージの更新</guilabel>ウィンドウで、イメージの名前を変更できます。イメージをパブリックにする場合、<guilabel>パブリック</guilabel>チェックボックスを選択します。イメージをプライベートにする場合、このチェックボックスを解除します。イメージのカーネル ID、メモリ、RAM ディスク ID、アーキテクチャーの属性は変更できません。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml126(para)
+msgid "Click <guibutton>Update Image</guibutton>."
+msgstr "<guibutton>イメージの更新</guibutton>をクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml131(title)
+msgid "Delete images"
+msgstr "イメージの削除"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml144(para)
+msgid "Select the images that you want to delete."
+msgstr "削除したいイメージを選択します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml147(para)
+msgid "Click <guibutton>Delete Images</guibutton>."
+msgstr "<guibutton>イメージの削除</guibutton>をクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml150(para)
+msgid ""
+"In the <guilabel>Confirm Delete Image</guilabel> window, click "
+"<guibutton>Delete Images</guibutton> to confirm the deletion."
+msgstr "<guilabel>イメージの削除の確認</guilabel>ウィンドウで、削除を確認するために<guibutton>イメージの削除</guibutton>をクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml153(para)
+msgid "You cannot undo this action."
+msgstr "この操作は取り消しできません。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml7(title)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml7(title)
+msgid "Manage project security"
+msgstr "プロジェクトのセキュリティの管理"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml8(para)
+msgid ""
+"Security groups are sets of IP filter rules that are applied to all project "
+"instances, which define networking access to the instance. Group rules are "
+"project specific; project members can edit the default rules for their group"
+" and add new rule sets."
+msgstr "セキュリティグループは、すべてのプロジェクトのインスタンスに適用される、IP フィルター群です。インスタンスへのネットワークアクセスを定義します。グループのルールはプロジェクト固有です。プロジェクトのメンバーは、これらのグループのデフォルトルールを編集し、新しいルール群を追加できます。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml13(para)
+msgid ""
+"All projects have a \"default\" security group which is applied to any "
+"instance that has no other defined security group. Unless you change the "
+"default, this security group denies all incoming traffic and allows only "
+"outgoing traffic to your instance."
+msgstr "すべてのプロジェクトは、他に定義されたセキュリティグループが無いインスタンスに適用されるデフォルトのセキュリティグループがあります。デフォルトを変更していなければ、このセキュリティグループは、すべての入力通信を拒否し、インスタンスの出力通信のみを許可します。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml19(para)
+msgid ""
+"For information about updating rules using the dashboard, see <xref "
+"linkend=\"dashboard_manage_projects_security\"/>."
+msgstr "ダッシュボードを用いたルールの更新方法の詳細は <xref linkend=\"dashboard_manage_projects_security\"/> を参照してください。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml23(para)
+msgid ""
+"You can use the <code>allow_same_net_traffic</code> option in the "
+"<filename>/etc/nova/nova.conf</filename> file to globally control whether "
+"the rules apply to hosts which share a network."
+msgstr "ネットワークを共有しているホストに適用されるルールを全体的に制御するために、<filename>/etc/nova/nova.conf</filename> ファイルで <code>allow_same_net_traffic</code> オプションを使用できます。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml27(para)
+msgid "If set to:"
+msgstr "設定した場合:"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml30(para)
+msgid ""
+"<code>True</code> (default), hosts on the same subnet are not filtered and "
+"are allowed to pass all types of traffic between them. On a flat network, "
+"this allows all instances from all projects unfiltered communication. With "
+"VLAN networking, this allows access between instances within the same "
+"project. You can also simulate this setting by configuring the default "
+"security group to allow all traffic from the subnet."
+msgstr "<code>True</code> (デフォルト)、同じサブネットにあるホストはフィルターされず、それらの間ですべての種類の通信が通過できるようになります。フラットなネットワークでは、これにより、全プロジェクトの全インスタンスが通信をフィルターされなくなります。VLAN ネットワークでは、これにより、同じプロジェクト内のインスタンス間でアクセスが許可されます。デフォルトのセキュリティグループをそのサブネットからのすべての通信を許可するよう設定することにより、この設定と同じ状態にすることもできます。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml41(para)
+msgid "<code>False</code>, security groups are enforced for all connections."
+msgstr "<code>False</code>、セキュリティグループがすべての通信に対して強制されます。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml45(para)
+msgid ""
+"Additionally, the number of maximum rules per security group is controlled "
+"by the <code>security_group_rules</code> and the number of allowed security "
+"groups per project is controlled by the <code>security_groups</code> quota "
+"(see <xref linkend=\"cli_set_quotas\"/>)."
+msgstr "加えて、セキュリティグループごとの最大ルール数は、<code>security_group_rules</code> により制御されます。また、プロジェクトごとに許可されるセキュリティグループ数は、<code>security_groups</code> クォータにより制御されます (<xref linkend=\"cli_set_quotas\"/>参照)。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml51(title)
+msgid "List and view current security groups"
+msgstr "現在のセキュリティグループの一覧表示"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml52(para)
+msgid ""
+"From the command line you can get a list of security groups for the project,"
+" using the nova command:"
+msgstr "コマンドラインから nova コマンドを使用して、プロジェクトに対するセキュリティグループの一覧を取得できます:"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml56(para)
+msgid ""
+"Ensure your system variables are set for the user and tenant for which you "
+"are checking security group rules for. For example:"
+msgstr "セキュリティグループルールを確認したいユーザーとプロジェクト向けのシステム変数をきちんと設定します。例:"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml63(para)
+msgid "Output security groups, as follows:"
+msgstr "以下のとおり、セキュリティグループを出力します。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml73(para)
+msgid "View the details of a group, as follows:"
+msgstr "以下のとおり、グループの詳細を表示します。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml74(replaceable)
+msgid "groupName"
+msgstr "groupName"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml75(para)
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml111(para)
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml174(para)
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml195(para)
+#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml68(para)
+#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml103(para)
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml80(para)
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml100(para)
+#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml16(para)
+msgid "For example:"
+msgstr "例:"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml84(para)
+msgid ""
+"These rules are allow type rules as the default is deny. The first column is"
+" the IP protocol (one of icmp, tcp, or udp). The second and third columns "
+"specify the affected port range. The third column specifies the IP range in "
+"CIDR format. This example shows the full port range for all protocols "
+"allowed from all IPs."
+msgstr "標準で拒否されるので、これらのルールはすべて「許可」形式のルールです。1 番目の項目は IP プロトコル (icmp, tcp, udp のどれか) です。2 番目と 3 番目の項目は影響するポート範囲を指定します。3 番目の項目は CIDR 形式の IP 範囲を指定します。この例はすべての IP から許可される、すべてのプロトコルの全ポート範囲を表します。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml94(title)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml23(title)
+msgid "Create a security group"
+msgstr "セキュリティグループの作成"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml95(para)
+msgid ""
+"When adding a new security group, you should pick a descriptive but brief "
+"name. This name shows up in brief descriptions of the instances that use it "
+"where the longer description field often does not. For example, seeing that "
+"an instance is using security group \"http\" is much easier to understand "
+"than \"bobs_group\" or \"secgrp1\"."
+msgstr "新しいセキュリティグループを追加するとき、説明的ですが、簡単な名前をつけるべきです。この名前はインスタンスの簡単な説明が示されます。より長い説明の項目が使用されないところで使用されます。例えば、インスタンスがセキュリティグループ \"http\" を使用していること、\"bobs_group\" や \"secgrp1\" よりも理解しやすいです。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml102(para)
+msgid ""
+"Ensure your system variables are set for the user and tenant for which you "
+"are checking security group rules for."
+msgstr "セキュリティグループルールを確認したいユーザーとプロジェクト向けのシステム変数をきちんと設定します。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml107(para)
+msgid "Add the new security group, as follows:"
+msgstr "以下のとおり、新しいセキュリティグループを追加します。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml109(replaceable)
+msgid "Group Name Description"
+msgstr "Group Name Description"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml122(para)
+msgid "Add a new group rule, as follows:"
+msgstr "以下のとおり、新しいグループルールを追加します。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml124(replaceable)
+msgid "secGroupName ip-protocol from-port to-port CIDR"
+msgstr "secGroupName ip-protocol from-port to-port CIDR"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml126(para)
+msgid ""
+"The arguments are positional, and the \"from-port\" and \"to-port\" "
+"arguments specify the local port range connections are allowed to access, "
+"not the source and destination ports of the connection. For example:"
+msgstr "引数の順番は決まっています。そして、\"from-port\" と \"to-port\" の引数はアクセスが許可されるローカルのポート範囲を指定し、接続の送信元ポートと宛先ポートではないことに注意してください。より複雑なルールセットが、複数の nova secgroup-add-rule の呼び出しから構成できます。例:"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml139(para)
+msgid ""
+"You can create complex rule sets by creating additional rules. For example, "
+"if you want to pass both http and https traffic, run:"
+msgstr "追加ルールを作成することにより、複雑なルールセットを作成できます。例えば、http と https の通信をどちらも許可したい場合、以下を実行します。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml148(para)
+msgid ""
+"Despite only outputting the newly added rule, this operation is additive "
+"(both rules are created and enforced)."
+msgstr "新しく追加されたルールのみが出力されますが、この操作は追加操作です (どちらのルールも作成され、強制されます):"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml153(para)
+msgid "View all rules for the new security group, as follows:"
+msgstr "以下のとおり、新しいセキュリティグループのすべてのルールを表示します。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml165(title)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml265(title)
+msgid "Delete a security group"
+msgstr "セキュリティグループの削除"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml167(para)
+msgid ""
+"Ensure your system variables are set for the user and tenant for which you "
+"are deleting a security group for."
+msgstr "セキュリティグループを削除したいユーザーとプロジェクト向けのシステム変数をきちんと設定します。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml172(para)
+msgid "Delete the new security group, as follows:"
+msgstr "以下のとおり、新しいセキュリティグループを削除します。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml173(replaceable)
+msgid "GroupName"
+msgstr "GroupName"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml179(title)
+msgid "Create security group rules for a cluster of instances"
+msgstr "インスタンスのクラスター向けにセキュリティグループのルールを作成します。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml181(para)
+msgid ""
+"Source Groups are a special, dynamic way of defining the CIDR of allowed "
+"sources. The user specifies a Source Group (Security Group name), and all "
+"the users' other Instances using the specified Source Group are selected "
+"dynamically. This alleviates the need for individual rules to allow each new"
+" member of the cluster."
+msgstr "ソースグループは許可されたソースの CIDR を動的に定義する特別な方法です。ユーザーがソースグループ (セキュリティグループ名) を指定します。これにより、指定されたソースグループを使用する、ユーザーの他のインスタンスが動的にすべて選択されます。これにより、クラスターのそれぞれの新しいメンバーを許可する、個別のルールの必要性を軽減できます。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml188(para)
+msgid ""
+"Make sure to set the system variables for the user and tenant for which you "
+"are deleting a security group for."
+msgstr "セキュリティグループを削除したいユーザーとプロジェクト向けのシステム変数をきちんと設定します。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml193(para)
+msgid "Add a source group, as follows:"
+msgstr "以下のとおり、ソースグループを追加します。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml194(replaceable)
+msgid "secGroupName source-group ip-protocol from-port to-port"
+msgstr "secGroupName source-group ip-protocol from-port to-port"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml197(para)
+msgid ""
+"The <code>cluster</code> rule allows ssh access from any other instance that"
+" uses the <code>global_http</code> group."
+msgstr "<code>cluster</code> ルールにより、<code>global_http</code> グループを使用する、他のすべてのインスタンスからの SSH アクセスを許可されます。"
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml7(title)
+msgid "Analyze log files"
+msgstr "ログファイルの分析"
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml8(para)
+msgid "Use the swift command-line client to analyze log files."
+msgstr "ログファイルを分析するために swift コマンドラインクライアントを使用します。"
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml9(para)
+msgid "The swift client is simple to use, scalable, and flexible."
+msgstr "swift クライアントは、使用しやすく、拡張可能かつ柔軟です。"
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml9(para)
+msgid ""
+"Use the swift client <option>-o</option> or <option>-output</option> option "
+"to get short answers to questions about logs,"
+msgstr "ログに関する問い合わせの応答を短縮するために、swift クライアントの <option>-o</option> または <option>-output</option> オプションを使用します。"
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml12(para)
+msgid ""
+"You can use the <option>-o —output</option> option with a single object "
+"download to redirect the command output to a specific file or to STDOUT "
+"(<literal>-</literal>). The ability to redirect the output to STDOUT enables"
+" you to pipe (<literal>|</literal>) data without saving it to disk first."
+msgstr "コマンドの出力を特定のファイル、または標準出力 (<literal>-</literal>) にリダイレクトするために、単一オブジェクトのダウンロードで <option>-o —output</option> オプションを使用できます。出力を標準出力へリダイレクトする機能により、最初にディスクに保存することなく、データをパイプ (<literal>|</literal>) できます。"
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml18(title)
+msgid "Upload and analyze log files"
+msgstr "ログファイルのアップロードと分析"
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml20(para)
+msgid ""
+"This example assumes that <filename>logtest</filename> directory contains "
+"the following log files:"
+msgstr "この例は、<filename>logtest</filename> ディレクトリに以下のログファイルが含まれることを仮定しています。"
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml23(title)
+msgid "Example files"
+msgstr "サンプルファイル"
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml27(para)
+msgid "Each file uses the following line format:"
+msgstr "各ファイルは以下の行の形式を使用します。"
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml28(title)
+msgid "Log line format"
+msgstr "ログの行形式"
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml31(para)
+msgid ""
+"Change into the <filename class=\"directory\">logtest</filename> directory:"
+msgstr "<filename class=\"directory\">logtest</filename> ディレクトリに移動します。"
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml35(para)
+msgid "Upload the log files into the <filename>logtest</filename> container:"
+msgstr "<filename>logtest</filename> コンテナーにログファイルをアップロードします。"
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml42(para)
+msgid "Get statistics for the account:"
+msgstr "アカウントの統計情報を取得します。"
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml48(para)
+msgid "Get statistics for the logtest container:"
+msgstr "logtest コンテナーの統計情報を取得します。"
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml56(para)
+msgid "List all objects in the logtest container:"
+msgstr "logtest コンテナーにあるすべてのオブジェクトを一覧表示します。"
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml62(title)
+msgid "Download and analyze an object"
+msgstr "オブジェクトのダウンロードと分析"
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml64(para)
+msgid ""
+"This example uses the <option>-o —output</option> option and a hyphen "
+"(<literal>-</literal>) to get information about an object."
+msgstr "この例は、オブジェクトに関する情報を取得するために、<option>-o —output</option> オプションとハイフン (<literal>-</literal>) を使用します。"
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml67(para)
+msgid ""
+"Use the swift <placeholder-1/> command to download the object. On this "
+"command, stream the output to <placeholder-2/> to break down requests by "
+"return code and the date <literal>2200 on November 16th, 2010</literal>."
+msgstr "オブジェクトをダウンロードするために、swift <placeholder-1/> コマンドを使用します。このコマンドは、リターンコードと日付 <literal>2200 on November 16th, 2010</literal> を用いてリクエストを解釈するために、出力を <placeholder-2/> に渡します。"
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml72(para)
+msgid ""
+"Using the log line format, find the request type in column 9 and the return "
+"code in column 12."
+msgstr "ログ行形式を用いて、9 列目のリクエスト種別と 12 列目のリターンコードを検索します。"
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml74(para)
+msgid ""
+"After <placeholder-1/> processes the output, it pipes it to <placeholder-2/>"
+" and <placeholder-3/> to sum up the number of occurrences for each request "
+"type and return code combination."
+msgstr "<placeholder-1/> が出力を処理した後、それぞれのリクエスト種別とリターンコードの組み合わせの発生数を合計するために、それを <placeholder-2/> と <placeholder-3/> に渡します。"
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml80(para)
+msgid "Download an object:"
+msgstr "オブジェクトをダウンロードします。"
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml113(para)
+msgid "Discover how many PUT requests are in each log file."
+msgstr "何回の PUT リクエストが各ログファイルにあったかを検索します。"
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml114(para)
+msgid ""
+"Use a bash for loop with awk and swift with the <option>-o —output</option> "
+"option and a hyphen (<literal>-</literal>) to discover how many PUT requests"
+" are in each log file."
+msgstr "何回の PUT リクエストが各ログファイルにあったかを検索するために、<option>-o —output</option> オプションとハイフン (<literal>-</literal>) を用いた awk と swift コマンドをループされるために bash を使用します。"
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml119(para)
+msgid ""
+"Run the swift <placeholder-1/> command to list objects in the logtest "
+"container. Then, for each item in the list, run the swift <placeholder-2/> "
+"command. Pipe the output into grep to filter the PUT requests. Finally, pipe"
+" into <placeholder-3/> to count the lines."
+msgstr "logtest コンテナーにあるオブジェクトを一覧表示するために、swift <placeholder-1/> コマンドを実行します。次に、一覧の各項目に対して、swift <placeholder-2/> コマンドを実行します。PUT リクエストをフィルターするために、出力を grep にパイプします。最後に、行数を集計するために <placeholder-3/> にパイプします。"
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml134(para)
+msgid "List the object names that begin with a specified string."
+msgstr "指定した文字列から始まるオブジェクト名を一覧表示します。"
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml136(para)
+msgid ""
+"Run the swift <placeholder-1/> command to list objects in the logtest "
+"container that begin with the <literal>2010-11-15</literal> string."
+msgstr "logtest コンテナーにある <literal>2010-11-15</literal> という文字列から始まるオブジェクトを一覧表示するために、swift <placeholder-1/> コマンドを実行します。"
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml140(para)
+msgid "For each item in the list, run the swift <placeholder-1/> command."
+msgstr "一覧の各項目に対して、swift <placeholder-1/> コマンドを実行します。"
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml142(para)
+msgid ""
+"Pipe the output to <placeholder-1/> and <placeholder-2/>. Use the "
+"<placeholder-3/> command to display the object name."
+msgstr "出力を <placeholder-1/> と <placeholder-2/> にパイプします。オブジェクト名を表示するために、<placeholder-3/> コマンドを使用します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml7(title)
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml7(title)
+msgid "Manage flavors"
+msgstr "フレーバーの管理"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml8(para)
+msgid ""
+"In OpenStack, a flavor defines the compute, memory, and storage capacity of "
+"a virtual server that users can launch. As an administrative user, you can "
+"create, edit, and delete flavors."
+msgstr "OpenStackでは、ユーザーが起動する仮想マシンの CPU、メモリ、ストレージ容量をフレーバーにより定義します。管理ユーザーとして、フレーバーを作成、編集、削除できます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml12(para)
+msgid "Only administrative users can create and manage flavors."
+msgstr "管理ユーザーのみがフレーバーを作成および管理できます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml14(para)
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml19(para)
+msgid "A flavor consists of the following parameters:"
+msgstr "フレーバーには、以下のパラメーターがあります。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml16(caption)
+msgid "Flavor parameters"
+msgstr "フレーバーのパラメーター"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml21(th)
+msgid "Parameter"
+msgstr "パラメーター"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml28(para)
+msgid "Flavor Name"
+msgstr "フレーバー名"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml31(para)
+msgid "The flavor name."
+msgstr "フレーバーの名前。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml36(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml172(guilabel)
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml135(para)
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml35(term)
+msgid "VCPUs"
+msgstr "仮想 CPU"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml39(para)
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml37(para)
+msgid "Number of virtual CPUs to use."
+msgstr "使用する仮想 CPU 数。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml44(para)
+msgid "RAM"
+msgstr "メモリー"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml47(para)
+msgid "Amount of RAM to use, in megabytes."
+msgstr "使用するメモリ量。メガバイト単位。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml52(para)
+msgid "Root Disk"
+msgstr "ルートディスク"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml55(para)
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml49(para)
+msgid "Amount of disk space (in gigabytes) to use for the root (/) partition."
+msgstr "ルート (/) パーティションに使用するディスク容量。ギガバイト単位。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml61(para)
+msgid "Ephemeral Disk"
+msgstr "一時ディスク"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml64(para)
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml56(para)
+msgid ""
+"Amount of disk space (in gigabytes) to use for the ephemeral partition. If "
+"unspecified, the value is 0 by default."
+msgstr "一時パーティションに使用するディスク容量。ギガバイト単位。省略すると、デフォルトで 0 になります。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml67(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml208(para)
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml59(para)
+msgid ""
+"Ephemeral disks offer machine local disk storage linked to the life cycle of"
+" a VM instance. When a VM is terminated, all data on the ephemeral disk is "
+"lost. Ephemeral disks are not included in any snapshots."
+msgstr "一時ディスクは、仮想マシンインスタンスのライフサイクルに一致した、マシンのローカルストレージを提供します。仮想マシンの終了時、一時ディスクにあるすべてのデータは失われます。一時ディスクはスナップショットに含められません。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml76(para)
+msgid "Swap Disk"
+msgstr "スワップディスク"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml79(para)
+msgid ""
+"Amount of swap space (in megabytes) to use. If unspecified, the default is "
+"0."
+msgstr "使用するスワップ容量。メガバイト単位。省略すると、デフォルトで 0 になります。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml85(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml163(guilabel)
+msgid "ID"
+msgstr "ID"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml88(para)
+msgid ""
+"The flavor ID is generated by OpenStack if the option selected is "
+"<guilabel>auto</guilabel>."
+msgstr "選択したオプションが <guilabel>auto</guilabel> の場合、フレーバー ID は OpenStack により生成されます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml90(para)
+msgid "By default, this field is set to <guilabel>auto</guilabel>."
+msgstr "この項目はデフォルトで <guilabel>auto</guilabel> に設定されます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml98(para)
+msgid "Indicates if the flavor is public."
+msgstr "フレーバーがパブリックであることを意味します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml103(para)
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml74(para)
+msgid "The default flavors are:"
+msgstr "デフォルトのフレーバーは以下のとおりです。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml106(para)
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml77(para)
+msgid "m1.tiny (1 VCPU/0 GB Disk/512 MB RAM)"
+msgstr "m1.tiny (1 仮想CPU/0 GB ディスク/512 MB メモリ)"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml109(para)
+msgid "m1.small (1 VCPU/20 GB Disk/2048 MB RAM)"
+msgstr "m1.small (1 仮想CPU/20 GB ディスク/2048 MB メモリ)"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml112(para)
+msgid "m1.medium (2 VCPU/40 GB Disk/4096 MB RAM)"
+msgstr "m1.medium (2 仮想CPU/40 GB ディスク/3072 MB メモリ)"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml115(para)
+msgid "m1.large (4 VCPU/80 GB Disk/8192 MB RAM)"
+msgstr "m1.large (4 仮想CPU/80 GB ディスク/8192 MB メモリ)"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml118(para)
+msgid "m1.xlarge (8 VCPU/160 GB Disk/16384 MB RAM)"
+msgstr "m1.xlarge (8 仮想CPU/160 GB ディスク/16384 MB メモリ)"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml122(title)
+msgid "Create flavors"
+msgstr "フレーバーの作成"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml131(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml256(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml284(para)
+msgid ""
+"On the <guilabel>Admin</guilabel> tab, click the "
+"<guilabel>Flavors</guilabel> category."
+msgstr "<guilabel>管理</guilabel> タブで、<guilabel>フレーバー</guilabel>カテゴリーをクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml135(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml241(para)
+msgid "Click <guibutton>Create Flavor</guibutton>."
+msgstr "<guibutton>フレーバーの作成</guibutton>をクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml139(para)
+msgid ""
+"In the <guilabel>Create Flavor</guilabel> window, enter or select the "
+"following values:"
+msgstr "<guilabel>フレーバーの作成</guilabel>ウィンドウで以下の値を入力または選択します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml148(guilabel)
+msgid "Flavor Info"
+msgstr "フレーバー情報"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml147(th)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml39(th)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml82(th)
+msgid "<placeholder-1/> tab"
+msgstr "<placeholder-1/> タブ"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml157(para)
+msgid "Enter the flavor name."
+msgstr "フレーバーの名前を入力します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml167(para)
+msgid "The flavor ID, generated by OpenStack."
+msgstr "OpenStack により生成されるフレーバー ID。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml175(para)
+msgid "Enter the number of virtual CPUs to use."
+msgstr "使用する仮想 CPU 数を入力します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml181(guilabel)
+msgid "RAM MB"
+msgstr "メモリー MB"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml184(para)
+msgid "Enter the amount of RAM to use, in megabytes."
+msgstr "使用するメモリ量をメガバイト単位で入力します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml190(guilabel)
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml47(term)
+msgid "Root Disk GB"
+msgstr "ルートディスク GB"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml193(para)
+msgid ""
+"Enter the mount of disk space in gigabytes to use for the root (/) "
+"partition."
+msgstr "ルート (/) パーティションに使用するディスク容量をギガバイト単位で入力します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml200(guilabel)
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml54(term)
+msgid "Ephemeral Disk GB"
+msgstr "一時ディスク GB"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml203(para)
+msgid ""
+"Enter the amount of disk space in gigabytes to use for the ephemeral "
+"partition. If unspecified, the value is 0 by default."
+msgstr "一時パーティションに使用するディスク容量をギガバイト単位で入力します。省略すると、デフォルトで 0 になります。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml219(guilabel)
+msgid "Swap Disk MB"
+msgstr "スワップディスク MB"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml222(para)
+msgid ""
+"Enter the amount of swap space (in megabytes) to use. If unspecified, the "
+"default is 0."
+msgstr "使用するスワップ容量をメガバイト単位で入力します。省略すると、デフォルトで 0 になります。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml232(para)
+msgid ""
+"In the <guilabel>Flavor Access</guilabel> tab, you can control access to the"
+" flavor by moving projects from the <guilabel>All Projects</guilabel> column"
+" to the <guilabel>Selected Projects</guilabel> column."
+msgstr "<guilabel>フレーバーアクセス権</guilabel>タブで、<guilabel>すべてのプロジェクト</guilabel>列から<guilabel>選択済みプロジェクト</guilabel>列にプロジェクトを移動して、フレーバーへのアクセス権を制御できます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml236(para)
+msgid ""
+"Only projects in the <guilabel>Selected Projects</guilabel> column can use "
+"the flavor. If there are no projects in the right column, all projects can "
+"use the flavor."
+msgstr "<guilabel>選択済みプロジェクト</guilabel>列にあるプロジェクトだけがこのフレーバーを使用できます。右側にプロジェクトがひとつもない場合は、すべてのプロジェクトがこのフレーバーを使用できます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml247(title)
+msgid "Update flavors"
+msgstr "フレーバーの更新"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml260(para)
+msgid ""
+"Select the flavor that you want to edit. Click <guibutton>Edit "
+"Flavor</guibutton>."
+msgstr "編集したいフレーバーを選択します。<guibutton>フレーバーの編集</guibutton>をクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml264(para)
+msgid ""
+"In the <guilabel>Edit Flavor</guilabel> window, you can change the flavor "
+"name, VCPUs, RAM, root dish, ephemeral disk, and swap disk values.."
+msgstr "<guilabel>フレーバーの編集</guilabel>ウィンドウで、フレーバー名、仮想 CPU 数、メモリ、ルートディスク、一時ディスク、スワップディスクの値を変更できます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml270(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml132(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml197(para)
+msgid "Click <guibutton>Save</guibutton>."
+msgstr "<guibutton>保存</guibutton>をクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml275(title)
+msgid "Delete flavors"
+msgstr "フレーバーの削除"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml288(para)
+msgid "Select the flavors that you want to delete."
+msgstr "削除したいフレーバーを選択します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml292(para)
+msgid "Click <guibutton>Delete Flavors</guibutton>."
+msgstr "<guibutton>フレーバーの削除</guibutton>をクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml296(para)
+msgid ""
+"In the <guilabel>Confirm Delete Flavors</guilabel> window, click "
+"<guibutton>Delete Flavors</guibutton> to confirm the deletion. You cannot "
+"undo this action."
+msgstr "<guilabel>フレーバーの削除の確認</guilabel>ウィンドウで、削除の確認をするために<guibutton>フレーバーの削除</guibutton>をクリックします。この操作を取り消すことはできません。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml11(title)
+msgid "View and manage quotas"
+msgstr "クォータの表示と管理"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml12(para)
+#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml12(para)
+msgid ""
+"To prevent system capacities from being exhausted without notification, you "
+"can set up quotas. Quotas are operational limits. For example, the number of"
+" gigabytes allowed for each tenant can be controlled so that cloud resources"
+" are optimized. Quotas can be enforced at both the tenant (or project) and "
+"the tenant-user level."
+msgstr "通知なしにシステム容量が使い切られてしまうことを避けるため、クォータを設定することができます。クォータは運用上の上限です。例えば、クラウドのリソースが最適化されるように、テナント毎に許容されるギガバイト数を制御できます。クォータは、テナント (プロジェクト) 単位とテナントユーザー単位に適用できます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml17(para)
+msgid ""
+"Typically, you change quotas when a project needs more than ten volumes or "
+"1TB on a compute node."
+msgstr "一般的に、プロジェクトが 1 つのコンピュートノードに 10 以上のボリューム、1TB 以上を必要とするとき、クォータを変更します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml19(para)
+msgid ""
+"Using the Dashboard, you can view default Compute and Block Storage quotas "
+"for new tenants, as well as update quotas for existing tenants."
+msgstr "ダッシュボードを使用して、新しいプロジェクトの Compute と Block Storage のデフォルトクォータ値を表示できます。また、既存のプロジェクトのクォータを更新することもできます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml22(para)
+msgid ""
+"Using the command-line interface, you can manage quotas for the OpenStack "
+"Compute service, the OpenStack Block Storage service, and the OpenStack "
+"Networking service (see <xref linkend=\"cli_set_quotas\"/>). Additionally, "
+"you can update Compute service quotas for tenant users."
+msgstr "コマンドラインインターフェースを用いて、OpenStack Compute、OpenStack Block Storage、OpenStack Networking のクォータを管理できます (<xref linkend=\"cli_set_quotas\"/> 参照)。また、プロジェクトのユーザーに対する Compute のクォータを更新できます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml28(para)
+msgid ""
+"The following table describes the Compute and Block Storage service quotas:"
+msgstr "以下の表は、Compute と Block Storage のクォータを記載しています。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml31(caption)
+msgid "Quota Descriptions"
+msgstr "クォータの説明"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml37(th)
+msgid "Quota Name"
+msgstr "クォータ名"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml38(th)
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml18(th)
+msgid "Defines the number of"
+msgstr "定義する数値"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml39(th)
+msgid "Service"
+msgstr "サービス"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml45(para)
+msgid "Gigabytes"
+msgstr "ギガバイト"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml48(para)
+msgid "Volume gigabytes allowed for each project."
+msgstr "各プロジェクトに許可されるボリュームのギガバイト容量。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml50(td)
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml131(td)
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml149(td)
+msgid "Block Storage"
+msgstr "ブロックストレージ"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml54(para)
+msgid "Instances"
+msgstr "インスタンス"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml57(para)
+msgid "Instances allowed for each project."
+msgstr "各プロジェクトに許可されるインスタンス数。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml59(td)
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml68(td)
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml77(td)
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml86(td)
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml95(td)
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml104(td)
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml113(td)
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml122(td)
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml140(td)
+msgid "Compute"
+msgstr "コンピュート"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml63(para)
+msgid "Injected Files"
+msgstr "注入ファイル"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml66(para)
+msgid "Injected files allowed for each project."
+msgstr "各プロジェクトに許可されるインジェクトファイル数。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml72(para)
+msgid "Injected File Content Bytes"
+msgstr "注入ファイルのバイト数"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml75(para)
+msgid "Content bytes allowed for each injected file."
+msgstr "各インジェクトファイルに許可されるバイト数。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml81(para)
+msgid "Keypairs"
+msgstr "キーペア"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml84(para)
+msgid "Number of keypairs."
+msgstr "キーペア数。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml90(para)
+msgid "Metadata Items"
+msgstr "メタデータ項目"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml93(para)
+msgid "Metadata items allowed for each instance."
+msgstr "各インスタンスに許可されるメタデータ項目数。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml99(para)
+msgid "RAM (MB)"
+msgstr "メモリー (MB)"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml102(para)
+msgid "RAM megabytes allowed for each instance."
+msgstr "各インスタンスに許可されるメモリのメガバイト容量。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml108(para)
+msgid "Security Groups"
+msgstr "セキュリティグループ"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml111(para)
+msgid "Security groups allowed for each project."
+msgstr "各プロジェクトに許可されるセキュリティグループ数。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml117(para)
+msgid "Security Group Rules"
+msgstr "セキュリティグループのルール"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml120(para)
+msgid "Rules allowed for each security group."
+msgstr "各セキュリティグループに許可されるルール数。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml126(para)
+msgid "Snapshots"
+msgstr "スナップショット"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml129(para)
+msgid "Volume snapshots allowed for each project."
+msgstr "各プロジェクトに許可されるボリュームのスナップショット数。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml138(para)
+msgid "Instance cores allowed for each project."
+msgstr "各プロジェクトに許可されるインスタンスのコア数。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml144(para)
+msgid "Volumes"
+msgstr "ボリューム"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml147(para)
+msgid "Volumes allowed for each project."
+msgstr "各プロジェクトに許可されるボリューム数"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml154(title)
+msgid "View default project quotas"
+msgstr "プロジェクトのデフォルトクォータの表示"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml157(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml175(para)
+msgid "Log in to the OpenStack dashboard."
+msgstr "OpenStack Dashboard にログインします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml160(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml178(para)
+msgid ""
+"On the <guilabel>Admin</guilabel> tab, click the "
+"<guilabel>Defaults</guilabel> category."
+msgstr "<guilabel>管理</guilabel> タブで、<guilabel>デフォルト</guilabel>カテゴリーをクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml164(para)
+msgid "The default quota values are displayed."
+msgstr "デフォルトのクォータ値が表示されます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml168(para)
+msgid ""
+"You can sort the table by clicking on either the <guilabel>Quota "
+"Name</guilabel> or <guilabel>Limit</guilabel> column headers."
+msgstr "<guilabel>クォータ名</guilabel>や<guilabel>制限</guilabel>の列ヘッダーをクリックすることにより、表を並び替えられます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml172(title)
+msgid "Update project quotas"
+msgstr "プロジェクトのクォータの更新"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml182(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml188(para)
+msgid "Click the <guibutton>Update Defaults</guibutton> button."
+msgstr "<guibutton>デフォルトの更新</guibutton>ボタンをクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml185(para)
+msgid ""
+"In the <guilabel>Update Default Quotas</guilabel> window, you can edit the "
+"default quota values."
+msgstr "<guilabel>デフォルトクォータの更新</guilabel>ウィンドウで、クォータのデフォルト値を編集できます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml192(para)
+msgid ""
+"The dashboard does not show all possible project quotas. To view and update "
+"the quotas for a service, use its command-line client. See <xref "
+"linkend=\"cli_set_quotas\"/>."
+msgstr "ダッシュボードにすべてのプロジェクトのクォータが表示されるわけではありません。サービスのクォータを表示および更新する場合、コマンドラインクライアントを使用します。<xref linkend=\"cli_set_quotas\"/> を参照してください。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_resources.xml7(title)
+msgid "View cloud resources"
+msgstr "クラウドのリソースの表示"
+
+#: ./doc/user-guide-admin/section_cli_manage_services.xml7(title)
+msgid "Manage services"
+msgstr "サービスの管理"
+
+#. When image changes, this message will be marked fuzzy or untranslated for
+#. you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml93(None)
+msgid ""
+"@@image: '../common/figures/change_instance_state.png'; "
+"md5=d9eef0f7a1f99eee18a99e677c7c710b"
+msgstr "@@image: '../common/figures/change_instance_state.png'; md5=d9eef0f7a1f99eee18a99e677c7c710b"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml11(title)
+msgid "Manage instances"
+msgstr "インスタンスの管理"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml12(para)
+msgid ""
+"As an administrative user, you can manage instances for users in various "
+"projects. You can view, terminate, edit, perform a soft or hard reboot, "
+"create a snapshot from, and migrate instances. You can also view the logs "
+"for instances or launch a VNC console for an instance."
+msgstr "管理ユーザーとして、さまざまなプロジェクトのユーザーのインスタンスを管理できます。インスタンスの表示、終了、編集、ソフトリブート、ハードリブート、スナップショットの作成、マイグレーションを実行できます。また、インスタンスのログを表示することやインスタンスの VNC コンソールを起動することもできます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml17(para)
+msgid ""
+"For information about using the dashboard to launch instances as an end "
+"user, see the <link href=\"http://docs.openstack.org/user-"
+"guide/content/\"><citetitle>OpenStack End User Guide</citetitle></link>."
+msgstr "エンドユーザーとしてインスタンスを起動するために、ダッシュボードを使用する方法は、<link href=\"http://docs.openstack.org/user-guide/content/\"><citetitle>OpenStack エンドユーザーガイド</citetitle></link>を参照してください。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml23(title)
+msgid "Create instance snapshots"
+msgstr "インスタンスのスナップショットの作成"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml26(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml65(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml109(para)
 #: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml27(para)
 #: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml51(para)
 #: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml79(para)
 #: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml24(para)
 #: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml51(para)
 #: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml86(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml26(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml65(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml109(para)
 #: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml66(para)
 #: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml225(para)
 msgid ""
@@ -57,440 +1139,88 @@ msgid ""
 "from the <guilabel>CURRENT PROJECT</guilabel> drop-down list."
 msgstr "ダッシュボードにログインし、<guilabel>現在のプロジェクト</guilabel>ドロップダウンリストから <guilabel>admin</guilabel> プロジェクトを選択します。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml32(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml56(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml84(para)
-msgid ""
-"On the <guilabel>Admin</guilabel> tab, click the <guilabel>Roles </guilabel>"
-" category."
-msgstr "<guilabel>管理</guilabel> タブで、<guilabel>ロール</guilabel>カテゴリーをクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml37(para)
-msgid "Click the <guibutton>Create Role</guibutton> button."
-msgstr "<guibutton>ロールの作成</guibutton>ボタンをクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml38(para)
-msgid ""
-"In the <guilabel>Create Role</guilabel> window, enter a name for the role."
-msgstr "<guilabel>ロールの作成</guilabel>ウィンドウで、ロールの名前を入力します。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml42(para)
-msgid ""
-"Click the <guibutton>Create Role</guibutton> button to confirm your changes."
-msgstr "変更を確認するために、<guibutton>ロールの作成</guibutton>ボタンをクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml48(title)
-msgid "Edit a role"
-msgstr "ロールの編集"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml61(para)
-msgid "Click the <guibutton>Edit</guibutton> button."
-msgstr "<guibutton>編集</guibutton>ボタンをクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml62(para)
-msgid ""
-"In the <guilabel>Update Role</guilabel> window, enter a new name for the "
-"role."
-msgstr "<guilabel>ロールの更新</guilabel>ウィンドウで、ロールの新しい名前を入力します。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml66(para)
-msgid ""
-"Click the <guibutton>Update Role</guibutton> button to confirm your changes."
-msgstr "変更を確認するために、<guibutton>ロールの更新</guibutton>ボタンをクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml72(para)
-msgid "Using the dashboard, you can edit only the name assigned to a role."
-msgstr "ダッシュボードを使用すると、ロールに割り当てる名前のみを編集できます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml76(title)
-msgid "Delete a role"
-msgstr "ロールの削除"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml88(para)
-msgid ""
-"Select the role you want to delete and click the <guibutton>Delete "
-"Roles</guibutton> button."
-msgstr "削除したいロールを選択し、<guibutton>ロールの削除</guibutton>ボタンをクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml4(title)
-#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml5(title)
-msgid "Launch and manage stacks"
-msgstr "スタックの起動と管理"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml5(para)
-#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml6(para)
-msgid ""
-"The Orchestration service provides a template-based orchestration engine for"
-" the OpenStack cloud, which can be used to create and manage cloud "
-"infrastructure resources such as storage, networking, instances, and "
-"applications as a repeatable running environment."
-msgstr "Orchestration により、OpenStack クラウドに対して、テンプレートによるオーケストレーションエンジンが提供されます。これは、繰り返し実行可能な環境として、ストレージ、ネットワーク、インスタンス、アプリケーションなどのクラウドインフラストラクチャーリソースを作成および管理するために使用できます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml10(para)
-#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml11(para)
-msgid ""
-"Templates are used to create stacks, which are collections of resources. For"
-" example, a stack might include instances, floating IPs, volumes, security "
-"groups, or users. The Orchestration service offers access to all OpenStack "
-"core services via a single modular template, with additional orchestration "
-"capabilities such as auto-scaling and basic high availability."
-msgstr "テンプレートは、スタックを作成するために使用される、リソースのコレクションです。例えば、スタックはインスタンス、Floating IP、ボリューム、セキュリティグループ、ユーザーを含むでしょう。Orchestration は、オートスケールや基本的な高可用性などのオーケストレーションの追加機能とともに、単一のモジュール型テンプレート経由で OpenStack のコアサービスへのアクセスを提供します。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml14(para)
-msgid "For information about:"
-msgstr "詳細は以下のとおりです。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml19(para)
-msgid ""
-"There are no administration-specific tasks that can be done through the "
-"dashboard."
-msgstr "ダッシュボードから実行できる、管理者固有の作業はありません。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml18(para)
-msgid ""
-"Administrative tasks on the command line, see <xref "
-"linkend=\"section_cli_admin_manage_stacks\"/>. <placeholder-1/>"
-msgstr "コマンドラインでの管理作業は <xref linkend=\"section_cli_admin_manage_stacks\"/> を参照してください。 <placeholder-1/>"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml22(para)
-msgid ""
-"The basic creation and deletion of Orchestration stacks, refer to the <link "
-"href=\"http://docs.openstack.org/user-"
-"guide/content/dashboard_stacks.html\">End User Guide</link>."
-msgstr "Orchestration スタックの基本的な作成および削除は <link href=\"http://docs.openstack.org/user-guide/content/dashboard_stacks.html\">OpenStack エンドユーザーガイド</link> を参照してください。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml7(title)
-msgid "Manage volumes and volume types"
-msgstr "ボリュームとボリューム種別の管理"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml8(para)
-msgid ""
-"Volumes are the Block Storage devices that you attach to instances to enable"
-" persistent storage. Users can attach a volume to a running instance or "
-"detach a volume and attach it to another instance at any time. For "
-"information about using the dashboard to create and manage volumes as an end"
-" user, see the <link href=\"http://docs.openstack.org/user-"
-"guide/content/\"><citetitle>OpenStack End User Guide</citetitle></link>."
-msgstr "ボリュームは、永続ストレージを使用するためにインスタンスに接続するブロックストレージデバイスです。ユーザーは、ボリュームを稼働中のインスタンスに接続したり切断したりできます。また、いつでも別のインスタンスに接続できます。エンドユーザーとして、ボリュームを作成および管理するためにダッシュボードを使用することに関する詳細は、<link href=\"http://docs.openstack.org/user-guide/content/\"><citetitle>OpenStack エンドユーザーガイド</citetitle></link>を参照してください。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml17(para)
-msgid ""
-"As an administrative user, you can manage volumes and volume types for users"
-" in various projects. You can create and delete volume types, and you can "
-"view and delete volumes."
-msgstr "管理ユーザーとして、さまざまなプロジェクトのユーザーに対する、ボリュームおよびボリューム種別を管理できます。ボリューム種別を作成および削除でき、ボリュームを表示および削除できます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml21(title)
-msgid "Create a volume type"
-msgstr "ボリューム種別の作成"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml30(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml57(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml92(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml32(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml71(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml115(para)
 msgid ""
 "On the <guilabel>Admin</guilabel> tab, click the "
-"<guilabel>Volumes</guilabel> category."
-msgstr "<guilabel>管理</guilabel> タブで、<guilabel>ボリューム</guilabel>カテゴリーをクリックします。"
+"<guilabel>Instances</guilabel> category."
+msgstr "<guilabel>管理</guilabel> タブで、<guilabel>インスタンス</guilabel>カテゴリーをクリックします。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml34(para)
-msgid "Click <guibutton>Create Volume Type</guibutton>."
-msgstr "<guibutton>ボリューム種別の作成</guibutton>をクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml36(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml37(para)
 msgid ""
-"In the <guilabel>Create Volume Type</guilabel> window, enter a name for the "
-"volume type."
-msgstr "<guilabel>ボリューム種別の作成</guilabel>ウィンドウで、ボリューム種別の名前を入力します。"
+"Select an instance to create a snapshot from it. From the "
+"<guilabel>Actions</guilabel> drop-down list, select <guilabel>Create "
+"Snapshot</guilabel>."
+msgstr "スナップショットを作成したいインスタンスを選択します。<guilabel>アクション</guilabel>ドロップダウンリストから、<guilabel>スナップショットの作成</guilabel>を選択します。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml40(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml43(para)
 msgid ""
-"Click <guibutton>Create Volume Type</guibutton> to confirm your changes."
-msgstr "変更を確認するために、<guibutton>ボリューム種別の作成</guibutton>をクリックします。"
+"In the <guilabel>Create Snapshot</guilabel> window, enter a name for the "
+"snapshot. Click <guibutton>Create Snapshot</guibutton>. The dashboard shows "
+"the instance snapshot in the <guilabel>Images &amp; Snapshots</guilabel> "
+"category."
+msgstr "<guilabel>スナップショットの作成</guilabel>ウィンドウで、スナップショットの名前を入力します。<guibutton>スナップショットの作成</guibutton>をクリックします。ダッシュボードの<guilabel>イメージとスナップショット</guilabel>カテゴリーにインスタンスのスナップショットが表示されます。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml46(title)
-msgid "Delete volume types"
-msgstr "ボリューム種別の削除"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml47(para)
-msgid "When you delete a volume type, volumes of that type are not deleted."
-msgstr "ボリューム種別の削除時、その種別のボリュームは削除されません。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml61(para)
-msgid "Select the volume type or types that you want to delete."
-msgstr "削除したいボリューム種別を選択します。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml65(para)
-msgid "Click <guibutton>Delete Volume Types</guibutton>."
-msgstr "<guibutton>ボリューム種別の削除</guibutton>をクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml69(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml51(para)
 msgid ""
-"In the <guilabel>Confirm Delete Volume Types</guilabel> window, click "
-"<guibutton>Delete Volume Types</guibutton> to confirm the action."
-msgstr "<guilabel>ボリューム種別の削除の確認</guilabel>ウィンドウで、操作内容を確認して、<guibutton>ボリューム種別の削除</guibutton>をクリックします。"
+"To launch an instance from the snapshot, select the snapshot and click "
+"<guibutton>Launch</guibutton>. For information about launching instances, "
+"see the <link href=\"http://docs.openstack.org/user-"
+"guide/content/\"><citetitle>OpenStack End User Guide</citetitle></link>."
+msgstr "スナップショットからインスタンスを起動するために、スナップショットを選択し、<guibutton>起動</guibutton>をクリックします。インスタンスの起動方法は、<link href=\"http://docs.openstack.org/user-guide/content/\"><citetitle>OpenStack エンドユーザーガイド</citetitle></link>を参照してください。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml75(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml110(para)
-msgid "A message indicates whether the action succeeded."
-msgstr "操作が成功したかどうかはメッセージでわかります。"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml62(title)
+msgid "Control the state of an instance"
+msgstr "インスタンスの状態の制御"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml81(title)
-msgid "Delete volumes"
-msgstr "ボリュームの削除"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml76(para)
+msgid "Select the instance for which you want to change the state."
+msgstr "状態を変更したいインスタンスを選択します。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml82(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml80(para)
 msgid ""
-"When you delete an instance, the data of its attached volumes is not "
-"destroyed."
-msgstr "インスタンスの削除時、接続されたボリュームのデータは無くなりません。"
+"In the <guilabel>More</guilabel> drop-down list in the "
+"<guilabel>Actions</guilabel> column, select the state."
+msgstr "<guilabel>アクション</guilabel>列の<guilabel>▼</guilabel>ドロップダウンリストで状態を選択します。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml96(para)
-msgid "Select the volume or volumes that you want to delete."
-msgstr "削除したいボリュームを選択します。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml100(para)
-msgid "Click <guibutton>Delete Volumes</guibutton>."
-msgstr "<guibutton>ボリュームの削除</guibutton>をクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml104(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml83(para)
 msgid ""
-"In the <guilabel>Confirm Delete Volumes</guilabel> window, click "
-"<guibutton>Delete Volumes</guibutton> to confirm the action."
-msgstr "<guilabel>ボリュームの削除の確認</guilabel>ウィンドウで、操作内容を確認して、<guibutton>ボリュームの削除</guibutton>をクリックします。"
+"Depending on the current state of the instance, you can choose to pause, un-"
+"pause, suspend, resume, soft or hard reboot, or terminate an instance (items"
+" in red are disabled)."
+msgstr "インスタンスの現在の状態によって、インスタンスを一時停止、一時停止解除、サスペンド、再開、ソフトリブート、ハードリブート、終了できます (赤い項目は無効化されています)。"
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml7(title)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml7(title)
-msgid "Manage flavors"
-msgstr "フレーバーの管理"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml88(title)
+msgid "DashboardInstance Actions"
+msgstr "ダッシュボード － インスタンスの操作"
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml8(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml101(title)
+msgid "Track usage"
+msgstr "使用状況の確認"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml102(para)
 msgid ""
-"In OpenStack, flavors define the compute, memory, and storage capacity of "
-"nova computing instances. To put it simply, a flavor is an available "
-"hardware configuration for a server. It defines the <quote>size</quote> of a"
-" virtual server that can be launched."
-msgstr "OpenStack ではフレーバーにより、nova コンピューティングインスタンスの CPU、メモリ、ストレージ容量を定義します。簡単に言うと、フレーバーはサーバー用に利用可能なハードウェア設定です。起動できる仮想サーバーの<quote>大きさ</quote>を定義します。"
+"Use the <guilabel>Overview</guilabel> category to track usage of instances "
+"for each project."
+msgstr "各プロジェクトのインスタンスの使用状況を確認するために、<guilabel>概要</guilabel>カテゴリーを使用します。"
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml14(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml104(para)
 msgid ""
-"Flavors can also determine on which compute host a flavor can be used to "
-"launch an instance. For information about customizing flavors, refer to the "
-"<link href=\"http://docs.openstack.org/admin-guide-"
-"cloud/content/\"><citetitle>OpenStack Cloud Administrator "
-"Guide</citetitle></link>."
-msgstr "フレーバーは、インスタンスを起動するために使用できるコンピュートホストを決めることもできます。フレーバーのカスタマイズの詳細は、<link href=\"http://docs.openstack.org/admin-guide-cloud/content/\"><citetitle>OpenStack Cloud Administrator Guide</citetitle></link> を参照してください。"
+"You can track costs per month by showing metrics like number of VCPUs, "
+"disks, RAM, and uptime of all your instances."
+msgstr "すべてのインスタンスの仮想 CPU 数、ディスク、メモリ、起動時間のような測定項目を表示することにより、月ごとのコストを確認できます。"
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml19(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml14(para)
-msgid "A flavor consists of the following parameters:"
-msgstr "フレーバーには、以下のパラメーターがあります。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml22(term)
-msgid "Flavor ID"
-msgstr "フレーバー ID"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml24(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml120(para)
 msgid ""
-"Automatically generated by OpenStack. For private flavors, a value from 1 to"
-" 255."
-msgstr "OpenStack により自動的に生成されます。プライベートなフレーバーの場合、1 ～ 255 の値になります。"
+"Select a month and click <guibutton>Submit</guibutton> to query the instance"
+" usage for that month."
+msgstr "その月のインスタンス使用量を問い合わせるために、月を選択し、<guibutton>送信</guibutton>をクリックします。"
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml29(term)
-#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml43(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml45(guilabel)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml154(guilabel)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml48(guilabel)
-msgid "Name"
-msgstr "名前"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml31(para)
-msgid "Name for the new flavor."
-msgstr "新しいフレーバーの名前。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml35(term)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml36(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml172(guilabel)
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml135(para)
-msgid "VCPUs"
-msgstr "仮想 CPU"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml37(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml39(para)
-msgid "Number of virtual CPUs to use."
-msgstr "使用する仮想 CPU 数。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml41(term)
-msgid "Memory MB"
-msgstr "メモリー MB"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml43(para)
-msgid "Amount of RAM to use (in megabytes)."
-msgstr "使用するメモリ量。メガバイト単位。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml47(term)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml190(guilabel)
-msgid "Root Disk GB"
-msgstr "ルートディスク GB"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml49(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml55(para)
-msgid "Amount of disk space (in gigabytes) to use for the root (/) partition."
-msgstr "ルート (/) パーティションに使用するディスク容量。ギガバイト単位。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml54(term)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml200(guilabel)
-msgid "Ephemeral Disk GB"
-msgstr "一時ディスク GB"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml56(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml64(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml125(para)
 msgid ""
-"Amount of disk space (in gigabytes) to use for the ephemeral partition. If "
-"unspecified, the value is 0 by default."
-msgstr "一時パーティションに使用するディスク容量。ギガバイト単位。省略すると、デフォルトで 0 になります。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml59(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml67(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml208(para)
-msgid ""
-"Ephemeral disks offer machine local disk storage linked to the life cycle of"
-" a VM instance. When a VM is terminated, all data on the ephemeral disk is "
-"lost. Ephemeral disks are not included in any snapshots."
-msgstr "一時ディスクは、仮想マシンインスタンスのライフサイクルに一致した、マシンのローカルストレージを提供します。仮想マシンの終了時、一時ディスクにあるすべてのデータは失われます。一時ディスクはスナップショットに含められません。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml67(term)
-msgid "Swap"
-msgstr "スワップ"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml69(para)
-msgid ""
-"Amount of swap space (in megabytes) to use. If unspecified, the value is 0 "
-"by default."
-msgstr "使用するスワップ容量。メガバイト単位。省略すると、デフォルトで 0 になります。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml74(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml103(para)
-msgid "The default flavors are:"
-msgstr "デフォルトのフレーバーは以下のとおりです。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml77(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml106(para)
-msgid "m1.tiny (1 VCPU/0 GB Disk/512 MB RAM)"
-msgstr "m1.tiny (1 仮想CPU/0 GB ディスク/512 MB メモリ)"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml80(para)
-msgid "m1.smaller (1 VCPU/0 GB Disk/1024 MB RAM)"
-msgstr "m1.smaller (1 仮想CPU/0 GB ディスク/1024 MB メモリ)"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml83(para)
-msgid "m1.small (1 VCPU/10 GB Disk/2048 MB RAM)"
-msgstr "m1.small (1 仮想CPU/10 GB ディスク/2048 MB メモリ)"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml86(para)
-msgid "m1.medium (2 VCPU/10 GB Disk/3072 MB RAM)"
-msgstr "m1.medium (2 仮想CPU/10 GB ディスク/3072 MB メモリ)"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml89(para)
-msgid "m1.large (4 VCPU/10 GB Disk/8192 MB RAM)"
-msgstr "m1.large (4 仮想CPU/10 GB ディスク/8192 MB メモリ)"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml92(para)
-msgid "m1.xlarge (8 VCPU/10 GB Disk/8192 MB RAM)"
-msgstr "m1.xlarge (8 仮想CPU/10 GB ディスク/8192 MB メモリ)"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml95(para)
-msgid ""
-"You can create and manage flavors with the nova <placeholder-1/> commands "
-"provided by the <filename>python-novaclient</filename> package."
-msgstr "<filename>python-novaclient</filename> パッケージにより提供される nova <placeholder-1/> コマンドを用いて、フレーバーを作成、管理できます。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml99(title)
-msgid "Create a flavor"
-msgstr "フレーバーの作成"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml102(para)
-msgid ""
-"List flavors to show the ID and name, the amount of memory, the amount of "
-"disk space for the root partition and for the ephemeral partition, the swap,"
-" and the number of virtual CPUs for each flavor."
-msgstr "各フレーバーの ID、名前、メモリ容量、ルートパーティション、一時パーティションのディスク容量、swap 容量、仮想 CPU 数を表示するために、フレーバーを一覧表示します。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml111(para)
-msgid ""
-"To create a flavor, specify a name, ID, RAM size, disk size, and the number "
-"of VCPUs for the flavor, as follows:"
-msgstr "フレーバーを作成するために、以下のとおり、フレーバーの名前、ID、メモリ容量、ディスク容量、仮想 CPU 数を指定します。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml114(replaceable)
-msgid "FLAVOR_NAME"
-msgstr "FLAVOR_NAME"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml114(replaceable)
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml153(replaceable)
-msgid "FLAVOR_ID"
-msgstr "FLAVOR_ID"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml114(replaceable)
-msgid "RAM_IN_MB ROOT_DISK_IN_GB"
-msgstr "RAM_IN_MB ROOT_DISK_IN_GB"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml114(replaceable)
-msgid "NUMBER_OF_VCPUS"
-msgstr "NUMBER_OF_VCPUS"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml116(para)
-msgid ""
-"The flavor ID is a number from 1 to 255 and cannot contain special "
-"characters or spaces."
-msgstr "フレーバー ID は 1 ～ 255 の数値です。特殊文字や空白は含められません。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml120(para)
-msgid ""
-"Here is an example with additional optional parameters filled in that "
-"creates a public \"extra tiny\" flavor that automatically gets an ID "
-"assigned, with 256 MB memory, no disk space, and one VCPU. The rxtx-factor "
-"indicates the slice of bandwidth that the instances with this flavor can use"
-" (through the Virtual Interface (vif) creation in the hypervisor)."
-msgstr "これは、割り当て ID を自動取得し、256MB メモリ、ディスクなし、1 仮想 CPU を持つ、パブリックな「extra tiny」フレーバーを作成するために、追加のオプションパラメーターを用いた例です。rxtx-factor は、このフレーバーのインスタンスが (ハイパーバイザーでの仮想インターフェースの作成により) 使用できる帯域幅を意味します。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml129(para)
-msgid ""
-"If an individual user or group of users needs a custom flavor that you do "
-"not want other tenants to have access to, you can change the flavor's access"
-" to make it a private flavor. See <link "
-"href=\"http://docs.openstack.org/trunk/openstack-ops/content/private-"
-"flavors.html\"> Private Flavors in the OpenStack Operations Guide </link>."
-msgstr "個々のユーザーやユーザーのグループが、他のプロジェクトがアクセス権を持たないカスタムフレーバーを必要とする場合、フレーバーをプライベートフレーバーにするために、アクセス権を変更できます。<link href=\"http://docs.openstack.org/trunk/openstack-ops/content/private-flavors.html\"> Private Flavors in the OpenStack Operations Guide </link> を参照してください。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml136(para)
-msgid "For a list of optional parameters, run this command:"
-msgstr "オプションパラメーターの一覧は、このコマンドを実行します。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml141(para)
-msgid ""
-"After you create a flavor, assign it to a project by specifying the flavor "
-"name or ID and the tenant ID:"
-msgstr "フレーバーの作成後、フレーバー名かフレーバー ID およびプロジェクト ID を指定することにより、フレーバーをプロジェクトに割り当てます。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml144(replaceable)
-msgid "FLAVOR"
-msgstr "FLAVOR"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml144(replaceable)
-#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml346(replaceable)
-#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml350(replaceable)
-#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml370(replaceable)
-#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml375(replaceable)
-msgid "TENANT_ID"
-msgstr "TENANT_ID"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml149(title)
-msgid "Delete a flavor"
-msgstr "フレーバーの削除"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml152(para)
-msgid "Delete a specified flavor, as follows:"
-msgstr "以下のように、指定したフレーバーを削除します。"
+"Click <guibutton>Download CSV Summary</guibutton> to download a CSV summary."
+msgstr "サマリーの CSV をダウンロードするために、<guibutton>サマリー (CSV) のダウンロード</guibutton>をクリックします。"
 
 #: ./doc/user-guide-admin/bk-admin-user-guide.xml9(title)
 msgid "OpenStack Admin User Guide"
@@ -569,6 +1299,481 @@ msgstr "2013-08-31"
 msgid "First edition of this document."
 msgstr "このドキュメントの初版。"
 
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml8(para)
+msgid ""
+"Security groups are sets of IP filter rules that define networking access "
+"and are applied to all project instances. Group rules are project specific; "
+"project members can edit the default rules for their group and add new rule "
+"sets."
+msgstr "セキュリティグループは、ネットワークアクセスを定義し、すべてのプロジェクトのインスタンスに適用される、IP フィルター群です。グループのルールはプロジェクト固有です。プロジェクトのメンバーは、これらのグループのデフォルトルールを編集し、新しいルール群を追加できます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml12(para)
+msgid ""
+"All projects have a default security group that is applied to any instance "
+"that has no other defined security group. Unless you change the default, "
+"this security group denies all incoming traffic and allows only outgoing "
+"traffic to your instance."
+msgstr "すべてのプロジェクトは、他に定義されたセキュリティグループが無いインスタンスに適用されるデフォルトのセキュリティグループがあります。デフォルトを変更していなければ、このセキュリティグループは、すべての入力通信を拒否し、インスタンスの出力通信のみを許可します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml18(para)
+msgid ""
+"For information about updating global controls on the command line, see "
+"<xref linkend=\"nova_cli_manage_projects_security\"/>."
+msgstr "コマンドラインのグローバル制御の更新に関する詳細は、<xref linkend=\"nova_cli_manage_projects_security\"/> を参照してください。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml26(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml54(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml243(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml268(para)
+msgid "Log in to the dashboard as a project member."
+msgstr "プロジェクトのメンバーとしてダッシュボードにログインします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml30(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml58(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml247(para)
+msgid ""
+"On the <guilabel>Project</guilabel> tab, select the appropriate project from"
+" the <guimenu>CURRENT PROJECT</guimenu> drop-down list, and click the "
+"<guimenuitem>Access &amp; Security</guimenuitem> category."
+msgstr "<guilabel>プロジェクト</guilabel>タブで、<guimenu>現在のプロジェクト</guimenu>ドロップダウンリストから適切なプロジェクトを選択し、<guimenuitem>アクセスとセキュリティ</guimenuitem>カテゴリーをクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml37(para)
+msgid ""
+"On the <guilabel>Security Groups</guilabel> tab, click <guibutton>Create "
+"Security Group</guibutton>."
+msgstr "<guilabel>セキュリティグループ</guilabel>タブで、<guibutton>セキュリティグループの作成</guibutton>をクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml42(para)
+msgid ""
+"Provide a name and appropriate description for the group, and click "
+"<guibutton>Create Security Group</guibutton>. By default, the new rule "
+"provides outgoing access rules for the group."
+msgstr "グループに対する名前と適切な説明を入力し、<guibutton>セキュリティグループの作成</guibutton>をクリックします。新しいルールはデフォルトで、グループに対して送信アクセスルールを提供します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml51(title)
+msgid "Add a security group rule"
+msgstr "セキュリティグループのルールの追加"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml65(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml254(para)
+msgid ""
+"On the <guilabel>Security Groups</guilabel> tab, click <guibutton>Edit "
+"rules</guibutton> for the appropriate security group."
+msgstr "<guilabel>セキュリティグループ</guilabel>タブで、適切なセキュリティグループの<guibutton>ルールの編集</guibutton>をクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml70(para)
+msgid ""
+"To add a rule, click <guibutton>Add Rule</guibutton>. Set the attributes for"
+" the rule, and click <guibutton>Add</guibutton>:"
+msgstr "ルールを追加するために、<guibutton>ルールの追加</guibutton>をクリックします。ルールの属性を設定し、<guibutton>追加</guibutton>をクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml113(guilabel)
+msgid "IP Protocol"
+msgstr "IP プロトコル"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml115(para)
+msgid "The IP protocol to which the rule applies:"
+msgstr "ルールを適用する IP プロトコル:"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml119(para)
+msgid ""
+"<guilabel>TCP</guilabel>.Typically used to exchange data between systems, "
+"and for end-user communication."
+msgstr "<guilabel>TCP</guilabel>。一般的にシステム間のデータ通信、エンドユーザーの通信に使用されます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml125(para)
+msgid ""
+"<guilabel>UDP</guilabel>. Typically used to exchange data between systems, "
+"particularly at the application level."
+msgstr "<guilabel>UDP</guilabel>。一般的にシステム間のデータ通信、とくにアプリケーションレベルで使用されます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml131(para)
+msgid ""
+"<guilabel>ICMP</guilabel>. Typically used by network devices, such as "
+"routers, to send error or monitoring messages."
+msgstr "<guilabel>ICMP</guilabel>。一般的に、エラーやモニタリングメッセージを送信するために、ルーターなどのネットワークデバイスにより使用されます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml153(guilabel)
+msgid "Open"
+msgstr "オープン"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml155(para)
+msgid ""
+"For TCP or UDP rules, the <guilabel>Port</guilabel> or <guilabel>Port "
+"Range</guilabel> to open for the rule. Choose to open a single port or range"
+" of ports."
+msgstr "TCP や UDP のルールの場合、ルールがオープンする <guilabel>ポート</guilabel>や<guilabel>ポート範囲</guilabel>。オープンする単一ポートまたはポート範囲を選択します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml160(para)
+msgid ""
+"For a range of ports, enter port values in the <guilabel>From "
+"Port</guilabel> and <guilabel>To Port</guilabel> fields."
+msgstr "ポート範囲の場合、<guilabel>下限ポート番号</guilabel>と<guilabel>上限ポート番号</guilabel>の項目に入力します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml164(para)
+msgid ""
+"For a single port, enter the port value in the <guilabel>Port</guilabel> "
+"field."
+msgstr "単一ポートの場合、<guilabel>ポート</guilabel>の項目にポート番号を入力します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml201(guilabel)
+msgid "Source"
+msgstr "送信元"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml203(para)
+msgid "The source of the traffic for this rule:"
+msgstr "このルールを適用する通信の送信元:"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml207(para)
+msgid ""
+"<guilabel>CIDR</guilabel> (Classless Inter-Domain Routing). IP address "
+"block, which limits access to IPs within the block. Enter the CIDR in the "
+"<guilabel>Source</guilabel> field."
+msgstr "<guilabel>CIDR</guilabel>。このブロック内の IP のアクセスを制限する、IP アドレスのブロック。<guilabel>接続相手</guilabel>の項目に CIDR を入力します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml216(para)
+msgid ""
+"<guilabel>Security Group</guilabel>. Source group that enables any instance "
+"in the group to access any other group instance."
+msgstr "<guilabel>セキュリティグループ</guilabel>。このセキュリティグループにあるすべてのインスタンスは、これ以外すべてのグループのインスタンスにアクセスできます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml240(title)
+msgid "Delete a security group rule"
+msgstr "セキュリティグループのルールの削除"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml259(para)
+msgid ""
+"To delete a rule, select the rule and click <guibutton>Delete "
+"Rule</guibutton>."
+msgstr "ルールを削除するために、ルールを選択し、<guibutton>ルールの削除</guibutton>をクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml272(para)
+msgid ""
+"On the <guilabel>Project</guilabel> tab, select the appropriate project from"
+" the <guilabel>CURRENT PROJECT</guilabel> drop-down list, and click the "
+"<guilabel>Access &amp; Security</guilabel> category."
+msgstr "<guilabel>プロジェクト</guilabel>タブで、<guilabel>現在のプロジェクト</guilabel>ドロップダウンリストから適切なプロジェクトを選択し、<guilabel>アクセスとセキュリティ</guilabel>カテゴリーをクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml279(para)
+msgid ""
+"On the <guilabel>Security Groups</guilabel> tab, select the appropriate "
+"group, and click <guibutton>Delete Security Group</guibutton>."
+msgstr "<guilabel>セキュリティグループ</guilabel>タブで、適切なグループを選択し、<guibutton>セキュリティグループの削除</guibutton>をクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml7(title)
+msgid "Create and manage host aggregates"
+msgstr "ホストアグリゲートの作成と管理"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml8(para)
+msgid ""
+"Host aggregates enable administrative users to assign key-value pairs to "
+"groups of machines."
+msgstr "ホストアグリゲートにより、管理ユーザーがキーバリューペアをマシンのグループに割り当てられます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml10(para)
+msgid ""
+"Each node can have multiple aggregates and each aggregate can have multiple "
+"key-value pairs. You can assign the same key-value pair to multiple "
+"aggregates."
+msgstr "各ノードは複数のアグリゲートを持てます。各アグリゲートは複数のキーバリューペアを持てます。同じキーバリューペアを複数のアグリゲートに割り当てられます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml13(para)
+msgid ""
+"The scheduler uses this information to make scheduling decisions. For "
+"information, see <link href=\"http://docs.openstack.org/trunk/config-"
+"reference/content/section_compute-"
+"scheduler.html\"><citetitle>Scheduling</citetitle></link>."
+msgstr "スケジューラーは、スケジューリングを判断するために、この情報を使用します。詳細は <link href=\"http://docs.openstack.org/trunk/config-reference/content/section_compute-scheduler.html\"><citetitle>Scheduling</citetitle></link> を参照してください。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml18(title)
+msgid "To create a host aggregate"
+msgstr "ホストアグリゲートの作成方法"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml25(para)
+msgid ""
+"On the <guilabel>Admin</guilabel> tab, click the <guilabel>Host "
+"Aggregates</guilabel> category."
+msgstr "<guilabel>管理</guilabel> タブで、<guilabel>ホストアグリゲート</guilabel>カテゴリーをクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml29(para)
+msgid "Click <guibutton>Create Host Aggregate</guibutton>."
+msgstr "<guibutton>ホストアグリゲートの作成</guibutton>をクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml32(para)
+msgid ""
+"In the <guilabel>Create Host Aggregate</guilabel> window, enter or select "
+"the following values:"
+msgstr "<guilabel>ホストアグリゲートの作成</guilabel>ウィンドウで、以下の値を入力または選択します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml40(guilabel)
+msgid "Host Aggregate Info"
+msgstr "ホストアグリゲート情報"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml47(para)
+msgid "The host aggregate name."
+msgstr "ホストアグリゲート名。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml51(guilabel)
+msgid "Availability Zone"
+msgstr "アベイラビリティゾーン"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml53(para)
+msgid ""
+"The cloud provider defines the default availability zone, such as <literal"
+">us-west</literal>, <literal>apac-south</literal>, or "
+"<literal>nova</literal>."
+msgstr "クラウドプロバイダーは、<literal>us-west</literal>、<literal>apac-south</literal>、<literal>nova</literal> のようなデフォルトのアベイラビリティゾーンを定義します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml58(para)
+msgid "You can target the host aggregate, as follows:"
+msgstr "以下のとおり、ホストアグリゲートをターゲットにできます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml62(para)
+msgid ""
+"When the host aggregate is exposed as an availability zone, select the "
+"availability zone when you launch an instance."
+msgstr "ホストアグリゲートがアベイラビリティゾーンとして公開されていなければ、インスタンスを起動するとき、アベイラビリティゾーンを選択します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml67(para)
+msgid ""
+"When the host aggregate is not exposed as an availability zone, select a "
+"flavor and its extra specs to target the host aggregate."
+msgstr "ホストアグリゲートがアベイラビリティゾーンとして公開されていなければ、ホストアグリゲートをターゲットにするために、フレーバーと追加スペックを選択します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml83(guilabel)
+msgid "Host within Aggregate"
+msgstr "アグリゲート内のホスト"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml88(guilabel)
+msgid "Selected hosts"
+msgstr "選択されたホスト"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml90(para)
+msgid ""
+"To assign a host to the aggregate, click <guilabel>+</guilabel> for the "
+"host. The host moves from the <guilabel>All available hosts</guilabel> list "
+"to the <guilabel>Selected hosts</guilabel> list."
+msgstr "ホストにアグリゲートを割り当てるために、ホストの <guilabel>+</guilabel> をクリックします。ホストが、<guilabel>すべての利用可能なホスト</guilabel>一覧から<guilabel>選択済みホスト</guilabel>一覧に移動します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml96(para)
+msgid ""
+"You can add one host to one or more aggregates. To add a host later, edit "
+"the aggregate."
+msgstr "ホストを 1 つ以上のアグリゲートに追加できます。後からホストを追加する場合、アグリゲートを編集します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml106(title)
+msgid "To manage host and aggregates"
+msgstr "ホストとアグリゲートの管理方法"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml113(para)
+msgid ""
+"On the <guilabel>Admin</guilabel> tab, click the <guilabel> Host "
+"Aggregates</guilabel> category."
+msgstr "<guilabel>管理</guilabel> タブで、<guilabel>ホストアグリゲート</guilabel>カテゴリーをクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml117(para)
+msgid "To edit host aggregates:"
+msgstr "ホストアグリゲートの編集方法:"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml120(para)
+msgid ""
+"Select the host aggregate that you want to edit. Click <guibutton>Edit Host "
+"Aggregate</guibutton>."
+msgstr "編集したいホストアグリゲートを選択します。<guibutton>ホストアグリゲートの編集</guibutton>をクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml124(para)
+msgid ""
+"In the <guilabel>Edit Host Aggregate</guilabel> window, you can change the "
+"name and availability zone for the aggregate."
+msgstr "<guilabel>ホストアグリゲートの編集</guilabel>ウィンドウで、アグリゲートの名前とアベイラビリティゾーンを変更できます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml131(para)
+msgid "To manage hosts:"
+msgstr "ホストの管理方法:"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml134(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml151(para)
+msgid ""
+"Select the host aggregate that you want to edit. Click "
+"<guibutton>More</guibutton>."
+msgstr "編集したいホストアグリゲートを選択します。<guibutton>▼</guibutton>をクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml138(para)
+msgid ""
+"In the <guilabel>Add/Remove Hosts to Aggregate</guilabel> window, click "
+"<guilabel>+</guilabel> to assign a host to the aggregate."
+msgstr "<guilabel>ホストのアグリゲートへの追加/削除</guilabel>ウィンドウで、ホストをアグリゲートに割り当てるために <guilabel>+</guilabel> をクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml142(para)
+msgid ""
+"Click <guilabel>-</guilabel> to remove a host that is assigned to an "
+"aggregate."
+msgstr "アグリゲートに割り当てられたホストを削除するために、<guilabel>-</guilabel> をクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml148(para)
+msgid "To delete host aggregates:"
+msgstr "ホストアグリゲートを削除する方法:"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml155(para)
+msgid "Click the <guilabel>Delete Host Aggregate</guilabel> option."
+msgstr "<guilabel>ホストアグリゲートの削除</guilabel>オプションをクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml6(title)
+msgid "View services information"
+msgstr "サービス情報の表示"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml7(para)
+msgid ""
+"As an administrative user, you can view information for OpenStack services."
+msgstr "管理ユーザーは、OpenStack サービスの情報を表示できます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml11(para)
+msgid ""
+"Log in to the OpenStack dashboard and choose the <guilabel>admin</guilabel> "
+"project from the <guilabel>CURRENT PROJECT</guilabel> drop-down list."
+msgstr "OpenStack のダッシュボードにログインし、<guilabel>現在のプロジェクト</guilabel>ドロップダウンリストから <guilabel>admin</guilabel> プロジェクトを選択します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml16(para)
+msgid ""
+"On the <guilabel>Admin</guilabel> tab, click the <guilabel>System "
+"Info</guilabel> category."
+msgstr "<guilabel>管理</guilabel> タブで、<guilabel>システム情報</guilabel>カテゴリーをクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml22(para)
+msgid "<guilabel>Services</guilabel> tab to view services information."
+msgstr "サービスの情報を表示するための、<guilabel>サービス</guilabel>タブ。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml23(para)
+msgid ""
+"The page displays the internal name and the public OpenStack name for the "
+"service, the host where the service runs, and whether the service is or is "
+"not enabled."
+msgstr "サービスの内部名、OpenStack のパブリックな名称、サービスを実行しているホスト、サービスが有効化状態が、このページに表示されます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml27(para)
+msgid ""
+"<guilabel>Compute Services</guilabel> tab to view services specific to the "
+"Compute Service. Both host and zone are listed for each service, as well as "
+"its activation status."
+msgstr "Compute に固有のサービスを表示するための、<guilabel>コンピュートサービス</guilabel>タブ。ホストとゾーンが稼働状態とともに各サービスに対して一覧表示されます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml20(para)
+msgid "Click the:<placeholder-1/>"
+msgstr "次をクリックします:<placeholder-1/>"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml36(guilabel)
+msgid "Availability Zones"
+msgstr "アベイラビリティゾーン"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml39(guilabel)
+msgid "Host Aggregates"
+msgstr "ホストアグリゲート"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml42(guilabel)
+msgid "Network Agents"
+msgstr "ネットワークエージェント"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml34(para)
+msgid ""
+"The <guilabel>System Info</guilabel> window also offers status information "
+"for the following: <placeholder-1/>"
+msgstr "<guilabel>システム情報</guilabel>ウィンドウで、状態に関する以下の情報が提供されます: <placeholder-1/>"
+
+#: ./doc/user-guide-admin/ch_dashboard.xml10(title)
+msgid "Dashboard"
+msgstr "ダッシュボード"
+
+#: ./doc/user-guide-admin/ch_dashboard.xml12(para)
+msgid ""
+"As a cloud administrative user, the OpenStack dashboard lets you create and "
+"manage projects, users, images, and flavors. You can also set quotas and "
+"create and manage services. For information about using the dashboard to "
+"perform end user tasks, see the <link href=\"http://docs.openstack.org/user-"
+"guide/content/\"><citetitle>OpenStack End User Guide</citetitle></link>."
+msgstr "クラウド管理ユーザーとして、OpenStack のダッシュボードにより、プロジェクト、ユーザー、イメージ、フレーバーを作成および管理できます。また、クォータを設定でき、サービスを作成および管理できます。エンドユーザーの作業を実行するために、ダッシュボードを使用する方法の詳細は、<link href=\"http://docs.openstack.org/user-guide/content/\"><citetitle>OpenStack エンドユーザーガイド</citetitle></link>を参照してください。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml8(title)
+msgid "Create and manage roles"
+msgstr "ロールの作成と管理"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml9(para)
+msgid ""
+"A role is a personality that a user assumes to perform a specific set of "
+"operations. A role includes a set of rights and privileges. A user assuming "
+"that role inherits those rights and privileges."
+msgstr "ロールは、ユーザーが特定の操作の組を実行すると仮定する人格です。ロールは一組の権利と権限を含みます。そのロールを仮定しているユーザーは、それらの権利と権限を継承します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml13(para)
+msgid ""
+"OpenStack Identity service defines a user's role on a project but it is "
+"completely up to the individual service to define what that role means. This"
+" is referred to as the service's policy. To get details about what the "
+"privileges for each role are, refer to the <filename>policy.json</filename> "
+"file available for each service in the "
+"<filename>/etc/<replaceable>SERVICE</replaceable>/policy.json</filename> "
+"file. For example, the policy defined for OpenStack Identity service is "
+"defined in the <filename>/etc/keystone/policy.json</filename> file."
+msgstr "OpenStack Identity は、プロジェクトにユーザーのロールを定義します。しかし、そのロールの意味を定義することは、完全に個々のサービス次第です。これは、サービスのポリシーとして参照されます。各ロールの権限の詳細を取得する場合、各サービスの <filename>/etc/<replaceable>SERVICE</replaceable>/policy.json</filename> ファイルで利用可能な <filename>policy.json</filename> ファイルを参照してください。例えば、OpenStack Identity に定義されているポリシーは、<filename>/etc/keystone/policy.json</filename> ファイルに定義されています。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml24(title)
+msgid "Create a role"
+msgstr "ロールの作成"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml32(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml56(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml84(para)
+msgid ""
+"On the <guilabel>Admin</guilabel> tab, click the <guilabel>Roles </guilabel>"
+" category."
+msgstr "<guilabel>管理</guilabel> タブで、<guilabel>ロール</guilabel>カテゴリーをクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml37(para)
+msgid "Click the <guibutton>Create Role</guibutton> button."
+msgstr "<guibutton>ロールの作成</guibutton>ボタンをクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml38(para)
+msgid ""
+"In the <guilabel>Create Role</guilabel> window, enter a name for the role."
+msgstr "<guilabel>ロールの作成</guilabel>ウィンドウで、ロールの名前を入力します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml42(para)
+msgid ""
+"Click the <guibutton>Create Role</guibutton> button to confirm your changes."
+msgstr "変更を確認するために、<guibutton>ロールの作成</guibutton>ボタンをクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml48(title)
+msgid "Edit a role"
+msgstr "ロールの編集"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml61(para)
+msgid "Click the <guibutton>Edit</guibutton> button."
+msgstr "<guibutton>編集</guibutton>ボタンをクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml62(para)
+msgid ""
+"In the <guilabel>Update Role</guilabel> window, enter a new name for the "
+"role."
+msgstr "<guilabel>ロールの更新</guilabel>ウィンドウで、ロールの新しい名前を入力します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml66(para)
+msgid ""
+"Click the <guibutton>Update Role</guibutton> button to confirm your changes."
+msgstr "変更を確認するために、<guibutton>ロールの更新</guibutton>ボタンをクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml72(para)
+msgid "Using the dashboard, you can edit only the name assigned to a role."
+msgstr "ダッシュボードを使用すると、ロールに割り当てる名前のみを編集できます。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml76(title)
+msgid "Delete a role"
+msgstr "ロールの削除"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml88(para)
+msgid ""
+"Select the role you want to delete and click the <guibutton>Delete "
+"Roles</guibutton> button."
+msgstr "削除したいロールを選択し、<guibutton>ロールの削除</guibutton>ボタンをクリックします。"
+
 #: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml6(title)
 msgid "Manage IP addresses"
 msgstr "IP アドレスの管理"
@@ -638,18 +1843,6 @@ msgstr "INTERFACE"
 msgid "RANGE_TO_CREATE"
 msgstr "RANGE_TO_CREATE"
 
-#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml68(para)
-#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml103(para)
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml75(para)
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml111(para)
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml174(para)
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml195(para)
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml80(para)
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml100(para)
-#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml16(para)
-msgid "For example:"
-msgstr "例:"
-
 #: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml70(para)
 msgid ""
 "By default, <placeholder-1/> uses the <systemitem>public</systemitem> pool "
@@ -762,12 +1955,6 @@ msgstr "キーワード引数:"
 msgid "Type"
 msgstr "種別"
 
-#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml49(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml22(th)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml52(guilabel)
-msgid "Description"
-msgstr "説明"
-
 #: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml52(para)
 #: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml66(para)
 #: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml77(para)
@@ -1010,6 +2197,14 @@ msgstr "ユーザーとプロジェクトの組み合わせにロールを割り
 msgid "ROLE_ID"
 msgstr "ROLE_ID"
 
+#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml346(replaceable)
+#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml350(replaceable)
+#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml370(replaceable)
+#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml375(replaceable)
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml144(replaceable)
+msgid "TENANT_ID"
+msgstr "TENANT_ID"
+
 #: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml349(para)
 msgid "To verify the role assignment:"
 msgstr "ロールの割り当てを確認する方法:"
@@ -1030,312 +2225,367 @@ msgstr "ロールの削除を確認するために、以下のコマンドを実
 msgid "If the role was removed, the command output omits the removed role."
 msgstr "ロールが削除されると、コマンドの出力から削除されたロールが消えています。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_resources.xml7(title)
-msgid "View cloud resources"
-msgstr "クラウドのリソースの表示"
+#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml11(title)
+msgid "Manage quotas"
+msgstr "クォータの管理"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml7(title)
-msgid "Create and manage host aggregates"
-msgstr "ホストアグリゲートの作成と管理"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml8(para)
+#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml18(para)
 msgid ""
-"Host aggregates enable administrative users to assign key-value pairs to "
-"groups of machines."
-msgstr "ホストアグリゲートにより、管理ユーザーがキーバリューペアをマシンのグループに割り当てられます。"
+"Using the command-line interface, you can manage quotas for the OpenStack "
+"Compute service, the OpenStack Block Storage service, and the OpenStack "
+"Networking service."
+msgstr "コマンドラインインターフェースを用いて、OpenStack Compute、OpenStack Block Storage、OpenStack Networking のクォータを管理できます。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml10(para)
+#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml21(para)
 msgid ""
-"Each node can have multiple aggregates and each aggregate can have multiple "
-"key-value pairs. You can assign the same key-value pair to multiple "
-"aggregates."
-msgstr "各ノードは複数のアグリゲートを持てます。各アグリゲートは複数のキーバリューペアを持てます。同じキーバリューペアを複数のアグリゲートに割り当てられます。"
+"The cloud operator typically changes default values because a tenant "
+"requires more than ten volumes or 1TB on a compute node."
+msgstr "1 つのプロジェクトが、1 つのコンピュートノードに 10 以上のボリューム、1TB 以上を必要とするので、クラウド運用者は一般的にデフォルト値を変更します。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml13(para)
+#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml26(para)
+msgid "To view all tenants (projects), run: <placeholder-1/>"
+msgstr "すべてのテナント（プロジェクト）を表示するには、以下のコマンドを実行します。<placeholder-1/>"
+
+#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml37(para)
+msgid "To display all current users for a tenant, run:"
+msgstr "現在のテナントの全ユーザーを表示するには、以下を実行します。"
+
+#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml39(replaceable)
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml99(replaceable)
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml114(replaceable)
+msgid "tenantID"
+msgstr "tenantID"
+
+#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml5(title)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml4(title)
+msgid "Launch and manage stacks"
+msgstr "スタックの起動と管理"
+
+#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml6(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml5(para)
 msgid ""
-"The scheduler uses this information to make scheduling decisions. For "
-"information, see <link href=\"http://docs.openstack.org/trunk/config-"
-"reference/content/section_compute-"
-"scheduler.html\"><citetitle>Scheduling</citetitle></link>."
-msgstr "スケジューラーは、スケジューリングを判断するために、この情報を使用します。詳細は <link href=\"http://docs.openstack.org/trunk/config-reference/content/section_compute-scheduler.html\"><citetitle>Scheduling</citetitle></link> を参照してください。"
+"The Orchestration service provides a template-based orchestration engine for"
+" the OpenStack cloud, which can be used to create and manage cloud "
+"infrastructure resources such as storage, networking, instances, and "
+"applications as a repeatable running environment."
+msgstr "Orchestration により、OpenStack クラウドに対して、テンプレートによるオーケストレーションエンジンが提供されます。これは、繰り返し実行可能な環境として、ストレージ、ネットワーク、インスタンス、アプリケーションなどのクラウドインフラストラクチャーリソースを作成および管理するために使用できます。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml18(title)
-msgid "To create a host aggregate"
-msgstr "ホストアグリゲートの作成方法"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml20(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml108(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml125(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml250(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml278(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml27(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml104(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml134(para)
-msgid "Log in to the dashboard."
-msgstr "ダッシュボードにログインします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml21(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml109(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml126(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml251(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml279(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml28(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml105(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml135(para)
+#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml11(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml10(para)
 msgid ""
-"Choose the <guilabel>admin</guilabel> project from the <guilabel>CURRENT "
-"PROJECT</guilabel> drop-down list."
-msgstr "<guilabel>現在のプロジェクト</guilabel>ドロップダウンリストから <guilabel>admin</guilabel> プロジェクトを選択します。"
+"Templates are used to create stacks, which are collections of resources. For"
+" example, a stack might include instances, floating IPs, volumes, security "
+"groups, or users. The Orchestration service offers access to all OpenStack "
+"core services via a single modular template, with additional orchestration "
+"capabilities such as auto-scaling and basic high availability."
+msgstr "テンプレートは、スタックを作成するために使用される、リソースのコレクションです。例えば、スタックはインスタンス、Floating IP、ボリューム、セキュリティグループ、ユーザーを含むでしょう。Orchestration は、オートスケールや基本的な高可用性などのオーケストレーションの追加機能とともに、単一のモジュール型テンプレート経由で OpenStack のコアサービスへのアクセスを提供します。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml25(para)
+#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml15(para)
+msgid "For information about the:"
+msgstr "詳細は以下のとおりです。"
+
+#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml19(para)
 msgid ""
-"On the <guilabel>Admin</guilabel> tab, click the <guilabel>Host "
-"Aggregates</guilabel> category."
-msgstr "<guilabel>管理</guilabel> タブで、<guilabel>ホストアグリゲート</guilabel>カテゴリーをクリックします。"
+"Basic creation and deletion of Orchestration stacks, refer to the <link "
+"href=\"http://docs.openstack.org/user-"
+"guide/content/dashboard_stacks.html\">End User Guide</link>."
+msgstr "Orchestration スタックの基本的な作成および削除は <link href=\"http://docs.openstack.org/user-guide/content/dashboard_stacks.html\">OpenStack エンドユーザーガイド</link> を参照してください。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml29(para)
-msgid "Click <guibutton>Create Host Aggregate</guibutton>."
-msgstr "<guibutton>ホストアグリゲートの作成</guibutton>をクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml32(para)
+#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml23(para)
 msgid ""
-"In the <guilabel>Create Host Aggregate</guilabel> window, enter or select "
-"the following values:"
-msgstr "<guilabel>ホストアグリゲートの作成</guilabel>ウィンドウで、以下の値を入力または選択します。"
+"<systemitem>heat</systemitem> CLI commands, see the <link "
+"href=\"http://docs.openstack.org/cli-reference/content/\"><citetitle> "
+"OpenStack Command Line Interface Reference</citetitle></link>"
+msgstr "<systemitem>heat</systemitem> CLI コマンドは <link href=\"http://docs.openstack.org/cli-reference/content/\"><citetitle> OpenStack Command Line Interface Reference</citetitle></link> を参照してください。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml40(guilabel)
-msgid "Host Aggregate Info"
-msgstr "ホストアグリゲート情報"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml39(th)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml82(th)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml147(th)
-msgid "<placeholder-1/> tab"
-msgstr "<placeholder-1/> タブ"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml47(para)
-msgid "The host aggregate name."
-msgstr "ホストアグリゲート名。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml51(guilabel)
-msgid "Availability Zone"
-msgstr "アベイラビリティゾーン"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml53(para)
+#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml30(para)
 msgid ""
-"The cloud provider defines the default availability zone, such as <literal"
-">us-west</literal>, <literal>apac-south</literal>, or "
-"<literal>nova</literal>."
-msgstr "クラウドプロバイダーは、<literal>us-west</literal>、<literal>apac-south</literal>、<literal>nova</literal> のようなデフォルトのアベイラビリティゾーンを定義します。"
+"As an administrator, you can also carry out stack functions on behalf of "
+"your users. For example, to resume, suspend, or delete a stack, run:"
+msgstr "管理ユーザーとして、ユーザーの役割でスタック機能を実行することもできます。例えば、スタックを再開、サスペンド、削除するために、以下を実行します。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml58(para)
-msgid "You can target the host aggregate, as follows:"
-msgstr "以下のとおり、ホストアグリゲートをターゲットにできます。"
+#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml32(replaceable)
+#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml33(replaceable)
+#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml34(replaceable)
+msgid "stackID"
+msgstr "stackID"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml62(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml6(title)
+msgid "View cloud usage statistics"
+msgstr "クラウドの使用状況の表示"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml7(para)
 msgid ""
-"When the host aggregate is exposed as an availability zone, select the "
-"availability zone when you launch an instance."
-msgstr "ホストアグリゲートがアベイラビリティゾーンとして公開されていなければ、インスタンスを起動するとき、アベイラビリティゾーンを選択します。"
+"The Telemetry module provides user-level usage data for OpenStack-based "
+"clouds, which can be used for customer billing, system monitoring, or "
+"alerts. Data can be collected by notifications sent by existing OpenStack "
+"components (for example, usage events emitted from Compute) or by polling "
+"the infrastructure (for example, libvirt)."
+msgstr "Telemetry モジュールは、OpenStack ベースのクラウドに関するユーザーレベルの使用状況データを提供します。顧客への課金、システム監視、アラートなどに使用できます。データは、既存の OpenStack コンポーネント (例えば、Compute からの使用状況のイベント) により送信された通知、またはインフラストラクチャー (例えば、libvirt) によるポーリングにより収集できます。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml67(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml13(para)
 msgid ""
-"When the host aggregate is not exposed as an availability zone, select a "
-"flavor and its extra specs to target the host aggregate."
-msgstr "ホストアグリゲートがアベイラビリティゾーンとして公開されていなければ、ホストアグリゲートをターゲットにするために、フレーバーと追加スペックを選択します。"
+"You can only view metering statistics on the dashboard (available only to "
+"administrators). The Telemetry service must be set up and administered "
+"through the <placeholder-1/> command-line interface (CLI)."
+msgstr "ダッシュボードでメータリングの統計情報を表示のみできます (管理者のみ利用可能)。Telemetry サービスがセットアップされ、<placeholder-1/> コマンドラインインターフェースにより管理されている必要があります。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml83(guilabel)
-msgid "Host within Aggregate"
-msgstr "アグリゲート内のホスト"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml88(guilabel)
-msgid "Selected hosts"
-msgstr "選択されたホスト"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml90(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml17(para)
 msgid ""
-"To assign a host to the aggregate, click <guilabel>+</guilabel> for the "
-"host. The host moves from the <guilabel>All available hosts</guilabel> list "
-"to the <guilabel>Selected hosts</guilabel> list."
-msgstr "ホストにアグリゲートを割り当てるために、ホストの <guilabel>+</guilabel> をクリックします。ホストが、<guilabel>すべての利用可能なホスト</guilabel>一覧から<guilabel>選択済みホスト</guilabel>一覧に移動します。"
+"For basic administration information, refer to the \"Measure Cloud "
+"Resources\" chapter in the <citetitle>OpenStack End User Guide</citetitle>."
+msgstr "基本的な管理情報は、<citetitle>OpenStack エンドユーザーガイド</citetitle> の「Measure Cloud Resources」の章を参照してください。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml96(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml20(title)
+msgid "View resource statistics"
+msgstr "リソースの使用状況の表示"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml23(para)
+msgid "Log in to the OpenStack dashboard as a user with Admin privileges."
+msgstr "管理権限を持つユーザーとして OpenStack Dashboard にログインします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml25(para)
 msgid ""
-"You can add one host to one or more aggregates. To add a host later, edit "
-"the aggregate."
-msgstr "ホストを 1 つ以上のアグリゲートに追加できます。後からホストを追加する場合、アグリゲートを編集します。"
+"On the <guilabel>Admin</guilabel> tab, click the <guilabel>Resource "
+"Usage</guilabel> category."
+msgstr "<guilabel>管理</guilabel> タブで、<guilabel>リソース使用量</guilabel>カテゴリーをクリックします。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml106(title)
-msgid "To manage host and aggregates"
-msgstr "ホストとアグリゲートの管理方法"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml113(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml31(para)
 msgid ""
-"On the <guilabel>Admin</guilabel> tab, click the <guilabel> Host "
-"Aggregates</guilabel> category."
-msgstr "<guilabel>管理</guilabel> タブで、<guilabel>ホストアグリゲート</guilabel>カテゴリーをクリックします。"
+"<guilabel>Global Disk Usage</guilabel> tab to view disk usage per tenant "
+"(project)."
+msgstr "プロジェクトごとのディスク使用量を表示するための、<guilabel>全体ディスク使用量</guilabel>タブ。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml117(para)
-msgid "To edit host aggregates:"
-msgstr "ホストアグリゲートの編集方法:"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml120(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml32(para)
 msgid ""
-"Select the host aggregate that you want to edit. Click <guibutton>Edit Host "
-"Aggregate</guibutton>."
-msgstr "編集したいホストアグリゲートを選択します。<guibutton>ホストアグリゲートの編集</guibutton>をクリックします。"
+"<guilabel>Global Network Traffic Usage</guilabel> tab to view ingress or "
+"egress usage per tenant (project)."
+msgstr "プロジェクトごとの受信および送信の使用量を表示するための、<guilabel>全体のネットワーク通信使用量</guilabel>タブ。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml124(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml34(para)
 msgid ""
-"In the <guilabel>Edit Host Aggregate</guilabel> window, you can change the "
-"name and availability zone for the aggregate."
-msgstr "<guilabel>ホストアグリゲートの編集</guilabel>ウィンドウで、アグリゲートの名前とアベイラビリティゾーンを変更できます。"
+"<guilabel>Global Object Storage Usage</guilabel> tab to view incoming and "
+"outgoing storage bytes per tenant (project)."
+msgstr "プロジェクトごとのストレージの受信および送信バイト数を表示するための、<guilabel>全体オブジェクトストレージ使用状況</guilabel>タブ。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml131(para)
-msgid "To manage hosts:"
-msgstr "ホストの管理方法:"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml134(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml151(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml35(para)
 msgid ""
-"Select the host aggregate that you want to edit. Click "
-"<guibutton>More</guibutton>."
-msgstr "編集したいホストアグリゲートを選択します。<guibutton>▼</guibutton>をクリックします。"
+"<guilabel>Global Network Usage</guilabel> tab to view duration and creation "
+"requests for networks, subnets, routers, ports, and floating IPs, per tenant"
+" (project)."
+msgstr "プロジェクトごとのネットワーク、サブネット、ルーター、ポート、Floating IP の使用期間および作成リクエスト数を表示するための、<guilabel>ネットワーク全体使用量</guilabel>タブ。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml138(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml38(para)
 msgid ""
-"In the <guilabel>Add/Remove Hosts to Aggregate</guilabel> window, click "
-"<guilabel>+</guilabel> to assign a host to the aggregate."
-msgstr "<guilabel>ホストのアグリゲートへの追加/削除</guilabel>ウィンドウで、ホストをアグリゲートに割り当てるために <guilabel>+</guilabel> をクリックします。"
+"<guilabel>Stats</guilabel> tab to view a multi-series line chart with user-"
+"defined metrics. You group by project, define the value type (min, max, avg,"
+" or sum), and specify the time period (or even use a calendar to define a "
+"date range)."
+msgstr "ユーザー定義の測定項目による他系列の折れ線グラフを表示するための、<guilabel>統計</guilabel>タブ。プロジェクトによるグループ化、値の種類の定義 (最小、最大、平均、合計)、対象期間の指定 (日付の期間を定義するためにカレンダーを使用) をできます。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml142(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml29(para)
+msgid "Click the: <placeholder-1/>"
+msgstr "次をクリックします: <placeholder-1/>"
+
+#: ./doc/user-guide-admin/ch_cli.xml10(title)
+msgid "OpenStack command-line clients"
+msgstr "OpenStack コマンドラインクライアント"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml7(title)
+msgid "Manage volumes and volume types"
+msgstr "ボリュームとボリューム種別の管理"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml8(para)
 msgid ""
-"Click <guilabel>-</guilabel> to remove a host that is assigned to an "
-"aggregate."
-msgstr "アグリゲートに割り当てられたホストを削除するために、<guilabel>-</guilabel> をクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml148(para)
-msgid "To delete host aggregates:"
-msgstr "ホストアグリゲートを削除する方法:"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml155(para)
-msgid "Click the <guilabel>Delete Host Aggregate</guilabel> option."
-msgstr "<guilabel>ホストアグリゲートの削除</guilabel>オプションをクリックします。"
-
-#. When image changes, this message will be marked fuzzy or untranslated for
-#. you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml93(None)
-msgid ""
-"@@image: '../common/figures/change_instance_state.png'; "
-"md5=d9eef0f7a1f99eee18a99e677c7c710b"
-msgstr "@@image: '../common/figures/change_instance_state.png'; md5=d9eef0f7a1f99eee18a99e677c7c710b"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml11(title)
-msgid "Manage instances"
-msgstr "インスタンスの管理"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml12(para)
-msgid ""
-"As an administrative user, you can manage instances for users in various "
-"projects. You can view, terminate, edit, perform a soft or hard reboot, "
-"create a snapshot from, and migrate instances. You can also view the logs "
-"for instances or launch a VNC console for an instance."
-msgstr "管理ユーザーとして、さまざまなプロジェクトのユーザーのインスタンスを管理できます。インスタンスの表示、終了、編集、ソフトリブート、ハードリブート、スナップショットの作成、マイグレーションを実行できます。また、インスタンスのログを表示することやインスタンスの VNC コンソールを起動することもできます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml17(para)
-msgid ""
-"For information about using the dashboard to launch instances as an end "
-"user, see the <link href=\"http://docs.openstack.org/user-"
+"Volumes are the Block Storage devices that you attach to instances to enable"
+" persistent storage. Users can attach a volume to a running instance or "
+"detach a volume and attach it to another instance at any time. For "
+"information about using the dashboard to create and manage volumes as an end"
+" user, see the <link href=\"http://docs.openstack.org/user-"
 "guide/content/\"><citetitle>OpenStack End User Guide</citetitle></link>."
-msgstr "エンドユーザーとしてインスタンスを起動するために、ダッシュボードを使用する方法は、<link href=\"http://docs.openstack.org/user-guide/content/\"><citetitle>OpenStack エンドユーザーガイド</citetitle></link>を参照してください。"
+msgstr "ボリュームは、永続ストレージを使用するためにインスタンスに接続するブロックストレージデバイスです。ユーザーは、ボリュームを稼働中のインスタンスに接続したり切断したりできます。また、いつでも別のインスタンスに接続できます。エンドユーザーとして、ボリュームを作成および管理するためにダッシュボードを使用することに関する詳細は、<link href=\"http://docs.openstack.org/user-guide/content/\"><citetitle>OpenStack エンドユーザーガイド</citetitle></link>を参照してください。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml23(title)
-msgid "Create instance snapshots"
-msgstr "インスタンスのスナップショットの作成"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml17(para)
+msgid ""
+"As an administrative user, you can manage volumes and volume types for users"
+" in various projects. You can create and delete volume types, and you can "
+"view and delete volumes."
+msgstr "管理ユーザーとして、さまざまなプロジェクトのユーザーに対する、ボリュームおよびボリューム種別を管理できます。ボリューム種別を作成および削除でき、ボリュームを表示および削除できます。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml32(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml71(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml115(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml21(title)
+msgid "Create a volume type"
+msgstr "ボリューム種別の作成"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml30(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml57(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml92(para)
 msgid ""
 "On the <guilabel>Admin</guilabel> tab, click the "
-"<guilabel>Instances</guilabel> category."
-msgstr "<guilabel>管理</guilabel> タブで、<guilabel>インスタンス</guilabel>カテゴリーをクリックします。"
+"<guilabel>Volumes</guilabel> category."
+msgstr "<guilabel>管理</guilabel> タブで、<guilabel>ボリューム</guilabel>カテゴリーをクリックします。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml37(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml34(para)
+msgid "Click <guibutton>Create Volume Type</guibutton>."
+msgstr "<guibutton>ボリューム種別の作成</guibutton>をクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml36(para)
 msgid ""
-"Select an instance to create a snapshot from it. From the "
-"<guilabel>Actions</guilabel> drop-down list, select <guilabel>Create "
-"Snapshot</guilabel>."
-msgstr "スナップショットを作成したいインスタンスを選択します。<guilabel>アクション</guilabel>ドロップダウンリストから、<guilabel>スナップショットの作成</guilabel>を選択します。"
+"In the <guilabel>Create Volume Type</guilabel> window, enter a name for the "
+"volume type."
+msgstr "<guilabel>ボリューム種別の作成</guilabel>ウィンドウで、ボリューム種別の名前を入力します。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml43(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml40(para)
 msgid ""
-"In the <guilabel>Create Snapshot</guilabel> window, enter a name for the "
-"snapshot. Click <guibutton>Create Snapshot</guibutton>. The dashboard shows "
-"the instance snapshot in the <guilabel>Images &amp; Snapshots</guilabel> "
-"category."
-msgstr "<guilabel>スナップショットの作成</guilabel>ウィンドウで、スナップショットの名前を入力します。<guibutton>スナップショットの作成</guibutton>をクリックします。ダッシュボードの<guilabel>イメージとスナップショット</guilabel>カテゴリーにインスタンスのスナップショットが表示されます。"
+"Click <guibutton>Create Volume Type</guibutton> to confirm your changes."
+msgstr "変更を確認するために、<guibutton>ボリューム種別の作成</guibutton>をクリックします。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml51(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml46(title)
+msgid "Delete volume types"
+msgstr "ボリューム種別の削除"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml47(para)
+msgid "When you delete a volume type, volumes of that type are not deleted."
+msgstr "ボリューム種別の削除時、その種別のボリュームは削除されません。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml61(para)
+msgid "Select the volume type or types that you want to delete."
+msgstr "削除したいボリューム種別を選択します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml65(para)
+msgid "Click <guibutton>Delete Volume Types</guibutton>."
+msgstr "<guibutton>ボリューム種別の削除</guibutton>をクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml69(para)
 msgid ""
-"To launch an instance from the snapshot, select the snapshot and click "
-"<guibutton>Launch</guibutton>. For information about launching instances, "
-"see the <link href=\"http://docs.openstack.org/user-"
-"guide/content/\"><citetitle>OpenStack End User Guide</citetitle></link>."
-msgstr "スナップショットからインスタンスを起動するために、スナップショットを選択し、<guibutton>起動</guibutton>をクリックします。インスタンスの起動方法は、<link href=\"http://docs.openstack.org/user-guide/content/\"><citetitle>OpenStack エンドユーザーガイド</citetitle></link>を参照してください。"
+"In the <guilabel>Confirm Delete Volume Types</guilabel> window, click "
+"<guibutton>Delete Volume Types</guibutton> to confirm the action."
+msgstr "<guilabel>ボリューム種別の削除の確認</guilabel>ウィンドウで、操作内容を確認して、<guibutton>ボリューム種別の削除</guibutton>をクリックします。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml62(title)
-msgid "Control the state of an instance"
-msgstr "インスタンスの状態の制御"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml75(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml110(para)
+msgid "A message indicates whether the action succeeded."
+msgstr "操作が成功したかどうかはメッセージでわかります。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml76(para)
-msgid "Select the instance for which you want to change the state."
-msgstr "状態を変更したいインスタンスを選択します。"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml81(title)
+msgid "Delete volumes"
+msgstr "ボリュームの削除"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml80(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml82(para)
 msgid ""
-"In the <guilabel>More</guilabel> drop-down list in the "
-"<guilabel>Actions</guilabel> column, select the state."
-msgstr "<guilabel>アクション</guilabel>列の<guilabel>▼</guilabel>ドロップダウンリストで状態を選択します。"
+"When you delete an instance, the data of its attached volumes is not "
+"destroyed."
+msgstr "インスタンスの削除時、接続されたボリュームのデータは無くなりません。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml83(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml96(para)
+msgid "Select the volume or volumes that you want to delete."
+msgstr "削除したいボリュームを選択します。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml100(para)
+msgid "Click <guibutton>Delete Volumes</guibutton>."
+msgstr "<guibutton>ボリュームの削除</guibutton>をクリックします。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml104(para)
 msgid ""
-"Depending on the current state of the instance, you can choose to pause, un-"
-"pause, suspend, resume, soft or hard reboot, or terminate an instance (items"
-" in red are disabled)."
-msgstr "インスタンスの現在の状態によって、インスタンスを一時停止、一時停止解除、サスペンド、再開、ソフトリブート、ハードリブート、終了できます (赤い項目は無効化されています)。"
+"In the <guilabel>Confirm Delete Volumes</guilabel> window, click "
+"<guibutton>Delete Volumes</guibutton> to confirm the action."
+msgstr "<guilabel>ボリュームの削除の確認</guilabel>ウィンドウで、操作内容を確認して、<guibutton>ボリュームの削除</guibutton>をクリックします。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml88(title)
-msgid "DashboardInstance Actions"
-msgstr "ダッシュボード － インスタンスの操作"
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml6(title)
+msgid "Manage Block Storage service quotas"
+msgstr "ブロックストレージのクォータの管理"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml101(title)
-msgid "Track usage"
-msgstr "使用状況の確認"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml102(para)
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml7(para)
 msgid ""
-"Use the <guilabel>Overview</guilabel> category to track usage of instances "
-"for each project."
-msgstr "各プロジェクトのインスタンスの使用状況を確認するために、<guilabel>概要</guilabel>カテゴリーを使用します。"
+"As an administrative user, you can update the OpenStack Block Storage "
+"service quotas for a project. You can also update the quota defaults for a "
+"new project."
+msgstr "管理ユーザーは、プロジェクトの Block Storage のクォータを更新できます。また、新規プロジェクトのクォータのデフォルト値も更新できます。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml104(para)
-msgid ""
-"You can track costs per month by showing metrics like number of VCPUs, "
-"disks, RAM, and uptime of all your instances."
-msgstr "すべてのインスタンスの仮想 CPU 数、ディスク、メモリ、起動時間のような測定項目を表示することにより、月ごとのコストを確認できます。"
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml12(caption)
+msgid "Block Storage quotas"
+msgstr "ブロックストレージのクォータ"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml120(para)
-msgid ""
-"Select a month and click <guibutton>Submit</guibutton> to query the instance"
-" usage for that month."
-msgstr "その月のインスタンス使用量を問い合わせるために、月を選択し、<guibutton>送信</guibutton>をクリックします。"
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml17(th)
+msgid "Property name"
+msgstr "プロパティ名"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml125(para)
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml24(para)
+msgid "gigabytes"
+msgstr "gigabytes"
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml27(para)
+msgid "Volume gigabytes allowed for each tenant."
+msgstr "各プロジェクトに許可されるボリュームのギガバイト容量。"
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml33(para)
+msgid "snapshots"
+msgstr "snapshots"
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml36(para)
+msgid "Volume snapshots allowed for each tenant."
+msgstr "各プロジェクトに許可されるボリュームのスナップショット数。"
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml42(para)
+msgid "volumes"
+msgstr "volumes"
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml45(para)
+msgid "Volumes allowed for each tenant."
+msgstr "各プロジェクトに許可されるボリューム数。"
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml52(title)
+msgid "View and update Block Storage service quotas"
+msgstr "Block Storage のクォータの表示と更新"
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml53(para)
 msgid ""
-"Click <guibutton>Download CSV Summary</guibutton> to download a CSV summary."
-msgstr "サマリーの CSV をダウンロードするために、<guibutton>サマリー (CSV) のダウンロード</guibutton>をクリックします。"
+"As an administrative user, you can view and update Block Storage service "
+"quotas."
+msgstr "管理ユーザーは、Block Storage のクォータを表示および更新できます。"
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml57(para)
+msgid "List the default quotas for all projects, as follows:"
+msgstr "以下のように、全プロジェクトのデフォルトクォータを一覧表示します。"
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml69(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> ファイルのプロパティを更新します。"
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml77(para)
+msgid "View Block Storage service quotas for a project, as follows:"
+msgstr "以下のように、プロジェクトの Block Storage のクォータを表示します。"
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml79(replaceable)
+msgid "TENANT_NAME"
+msgstr "TENANT_NAME"
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml91(para)
+msgid ""
+"To update Block Storage service quotas, place the tenant ID in a usable "
+"variable, as follows:"
+msgstr "Block Storage のクォータを更新するために、以下のとおり、利用可能な変数にプロジェクト ID を置きます。"
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml94(replaceable)
+msgid "tenantName"
+msgstr "tenantName"
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml97(para)
+msgid "Update a particular quota value, as follows:"
+msgstr "指定したクォータ値を更新します。"
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml99(replaceable)
+msgid "quotaName"
+msgstr "quotaName"
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml99(replaceable)
+msgid "NewValue"
+msgstr "NewValue"
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml112(para)
+msgid "To clear per-tenant quota limits, use the <placeholder-1/> command:"
+msgstr "テナントごとのクォータ制限を解除するために、<placeholder-1/> コマンドを使用します。"
 
 #: ./doc/user-guide-admin/section_cli_nova_services.xml6(title)
 msgid "Manage Compute services"
@@ -1365,591 +2615,37 @@ msgstr "サービス一覧を確認します。"
 msgid "Enable the service:"
 msgstr "サービスを有効化します。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml7(title)
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml7(title)
-msgid "Manage project security"
-msgstr "プロジェクトのセキュリティの管理"
+#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml6(title)
+msgid "Select hosts where instances are launched"
+msgstr "インスタンスを起動するホストの選択"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml8(para)
+#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml7(para)
 msgid ""
-"Security groups are sets of IP filter rules that define networking access "
-"and are applied to all project instances. Group rules are project specific; "
-"project members can edit the default rules for their group and add new rule "
-"sets."
-msgstr "セキュリティグループは、ネットワークアクセスを定義し、すべてのプロジェクトのインスタンスに適用される、IP フィルター群です。グループのルールはプロジェクト固有です。プロジェクトのメンバーは、これらのグループのデフォルトルールを編集し、新しいルール群を追加できます。"
+"With the appropriate permissions, you can select which host instances are "
+"launched on and which roles can boot instances on this host."
+msgstr "適切なパーミッションを用いると、インスタンスが起動されるホスト、このホストでインスタンスを起動できるロールを選択できます。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml12(para)
+#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml12(para)
 msgid ""
-"All projects have a default security group that is applied to any instance "
-"that has no other defined security group. Unless you change the default, "
-"this security group denies all incoming traffic and allows only outgoing "
-"traffic to your instance."
-msgstr "すべてのプロジェクトは、他に定義されたセキュリティグループが無いインスタンスに適用されるデフォルトのセキュリティグループがあります。デフォルトを変更していなければ、このセキュリティグループは、すべての入力通信を拒否し、インスタンスの出力通信のみを許可します。"
+"To select the host where instances are launched, use the "
+"<literal>--availability_zone "
+"<replaceable>zone</replaceable>:<replaceable>host</replaceable></literal> "
+"parameter on the <placeholder-1/> command,"
+msgstr "インスタンスが起動するホストを選択するために、<literal>--availability_zone <replaceable>zone</replaceable>:<replaceable>host</replaceable></literal> parameter on the <placeholder-1/> コマンドを使用します。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml18(para)
+#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml20(para)
 msgid ""
-"For information about updating global controls on the command line, see "
-"<xref linkend=\"nova_cli_manage_projects_security\"/>."
-msgstr "コマンドラインのグローバル制御の更新に関する詳細は、<xref linkend=\"nova_cli_manage_projects_security\"/> を参照してください。"
+"To specify which roles can launch an instance on a specified host, enable "
+"the <literal>create:forced_host</literal> option in the "
+"<filename>policy.json</filename> file. By default, this option is enabled "
+"for only the admin role."
+msgstr "指定したホストにインスタンスを起動できるロールを指定するために、<filename>policy.json</filename> ファイルに <literal>create:forced_host</literal> オプションを有効化します。このオプションはデフォルトで、admin ロールのみに対して有効化されます。"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml23(title)
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml94(title)
-msgid "Create a security group"
-msgstr "セキュリティグループの作成"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml26(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml54(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml243(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml268(para)
-msgid "Log in to the dashboard as a project member."
-msgstr "プロジェクトのメンバーとしてダッシュボードにログインします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml30(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml58(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml247(para)
+#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml27(para)
 msgid ""
-"On the <guilabel>Project</guilabel> tab, select the appropriate project from"
-" the <guimenu>CURRENT PROJECT</guimenu> drop-down list, and click the "
-"<guimenuitem>Access &amp; Security</guimenuitem> category."
-msgstr "<guilabel>プロジェクト</guilabel>タブで、<guimenu>現在のプロジェクト</guimenu>ドロップダウンリストから適切なプロジェクトを選択し、<guimenuitem>アクセスとセキュリティ</guimenuitem>カテゴリーをクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml37(para)
-msgid ""
-"On the <guilabel>Security Groups</guilabel> tab, click <guibutton>Create "
-"Security Group</guibutton>."
-msgstr "<guilabel>セキュリティグループ</guilabel>タブで、<guibutton>セキュリティグループの作成</guibutton>をクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml42(para)
-msgid ""
-"Provide a name and appropriate description for the group, and click "
-"<guibutton>Create Security Group</guibutton>. By default, the new rule "
-"provides outgoing access rules for the group."
-msgstr "グループに対する名前と適切な説明を入力し、<guibutton>セキュリティグループの作成</guibutton>をクリックします。新しいルールはデフォルトで、グループに対して送信アクセスルールを提供します。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml51(title)
-msgid "Add a security group rule"
-msgstr "セキュリティグループのルールの追加"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml65(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml254(para)
-msgid ""
-"On the <guilabel>Security Groups</guilabel> tab, click <guibutton>Edit "
-"rules</guibutton> for the appropriate security group."
-msgstr "<guilabel>セキュリティグループ</guilabel>タブで、適切なセキュリティグループの<guibutton>ルールの編集</guibutton>をクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml70(para)
-msgid ""
-"To add a rule, click <guibutton>Add Rule</guibutton>. Set the attributes for"
-" the rule, and click <guibutton>Add</guibutton>:"
-msgstr "ルールを追加するために、<guibutton>ルールの追加</guibutton>をクリックします。ルールの属性を設定し、<guibutton>追加</guibutton>をクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml113(guilabel)
-msgid "IP Protocol"
-msgstr "IP プロトコル"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml115(para)
-msgid "The IP protocol to which the rule applies:"
-msgstr "ルールを適用する IP プロトコル:"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml119(para)
-msgid ""
-"<guilabel>TCP</guilabel>.Typically used to exchange data between systems, "
-"and for end-user communication."
-msgstr "<guilabel>TCP</guilabel>。一般的にシステム間のデータ通信、エンドユーザーの通信に使用されます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml125(para)
-msgid ""
-"<guilabel>UDP</guilabel>. Typically used to exchange data between systems, "
-"particularly at the application level."
-msgstr "<guilabel>UDP</guilabel>。一般的にシステム間のデータ通信、とくにアプリケーションレベルで使用されます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml131(para)
-msgid ""
-"<guilabel>ICMP</guilabel>. Typically used by network devices, such as "
-"routers, to send error or monitoring messages."
-msgstr "<guilabel>ICMP</guilabel>。一般的に、エラーやモニタリングメッセージを送信するために、ルーターなどのネットワークデバイスにより使用されます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml153(guilabel)
-msgid "Open"
-msgstr "オープン"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml155(para)
-msgid ""
-"For TCP or UDP rules, the <guilabel>Port</guilabel> or <guilabel>Port "
-"Range</guilabel> to open for the rule. Choose to open a single port or range"
-" of ports."
-msgstr "TCP や UDP のルールの場合、ルールがオープンする <guilabel>ポート</guilabel>や<guilabel>ポート範囲</guilabel>。オープンする単一ポートまたはポート範囲を選択します。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml160(para)
-msgid ""
-"For a range of ports, enter port values in the <guilabel>From "
-"Port</guilabel> and <guilabel>To Port</guilabel> fields."
-msgstr "ポート範囲の場合、<guilabel>下限ポート番号</guilabel>と<guilabel>上限ポート番号</guilabel>の項目に入力します。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml164(para)
-msgid ""
-"For a single port, enter the port value in the <guilabel>Port</guilabel> "
-"field."
-msgstr "単一ポートの場合、<guilabel>ポート</guilabel>の項目にポート番号を入力します。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml201(guilabel)
-msgid "Source"
-msgstr "送信元"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml203(para)
-msgid "The source of the traffic for this rule:"
-msgstr "このルールを適用する通信の送信元:"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml207(para)
-msgid ""
-"<guilabel>CIDR</guilabel> (Classless Inter-Domain Routing). IP address "
-"block, which limits access to IPs within the block. Enter the CIDR in the "
-"<guilabel>Source</guilabel> field."
-msgstr "<guilabel>CIDR</guilabel>。このブロック内の IP のアクセスを制限する、IP アドレスのブロック。<guilabel>接続相手</guilabel>の項目に CIDR を入力します。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml216(para)
-msgid ""
-"<guilabel>Security Group</guilabel>. Source group that enables any instance "
-"in the group to access any other group instance."
-msgstr "<guilabel>セキュリティグループ</guilabel>。このセキュリティグループにあるすべてのインスタンスは、これ以外すべてのグループのインスタンスにアクセスできます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml240(title)
-msgid "Delete a security group rule"
-msgstr "セキュリティグループのルールの削除"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml259(para)
-msgid ""
-"To delete a rule, select the rule and click <guibutton>Delete "
-"Rule</guibutton>."
-msgstr "ルールを削除するために、ルールを選択し、<guibutton>ルールの削除</guibutton>をクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml265(title)
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml165(title)
-msgid "Delete a security group"
-msgstr "セキュリティグループの削除"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml272(para)
-msgid ""
-"On the <guilabel>Project</guilabel> tab, select the appropriate project from"
-" the <guilabel>CURRENT PROJECT</guilabel> drop-down list, and click the "
-"<guilabel>Access &amp; Security</guilabel> category."
-msgstr "<guilabel>プロジェクト</guilabel>タブで、<guilabel>現在のプロジェクト</guilabel>ドロップダウンリストから適切なプロジェクトを選択し、<guilabel>アクセスとセキュリティ</guilabel>カテゴリーをクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml279(para)
-msgid ""
-"On the <guilabel>Security Groups</guilabel> tab, select the appropriate "
-"group, and click <guibutton>Delete Security Group</guibutton>."
-msgstr "<guilabel>セキュリティグループ</guilabel>タブで、適切なグループを選択し、<guibutton>セキュリティグループの削除</guibutton>をクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml8(para)
-msgid ""
-"In OpenStack, a flavor defines the compute, memory, and storage capacity of "
-"a virtual server that users can launch. As an administrative user, you can "
-"create, edit, and delete flavors."
-msgstr "OpenStackでは、ユーザーが起動する仮想マシンの CPU、メモリ、ストレージ容量をフレーバーにより定義します。管理ユーザーとして、フレーバーを作成、編集、削除できます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml12(para)
-msgid "Only administrative users can create and manage flavors."
-msgstr "管理ユーザーのみがフレーバーを作成および管理できます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml16(caption)
-msgid "Flavor parameters"
-msgstr "フレーバーのパラメーター"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml21(th)
-msgid "Parameter"
-msgstr "パラメーター"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml28(para)
-msgid "Flavor Name"
-msgstr "フレーバー名"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml31(para)
-msgid "The flavor name."
-msgstr "フレーバーの名前。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml44(para)
-msgid "RAM"
-msgstr "メモリー"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml47(para)
-msgid "Amount of RAM to use, in megabytes."
-msgstr "使用するメモリ量。メガバイト単位。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml52(para)
-msgid "Root Disk"
-msgstr "ルートディスク"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml61(para)
-msgid "Ephemeral Disk"
-msgstr "一時ディスク"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml76(para)
-msgid "Swap Disk"
-msgstr "スワップディスク"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml79(para)
-msgid ""
-"Amount of swap space (in megabytes) to use. If unspecified, the default is "
-"0."
-msgstr "使用するスワップ容量。メガバイト単位。省略すると、デフォルトで 0 になります。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml85(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml163(guilabel)
-msgid "ID"
-msgstr "ID"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml88(para)
-msgid ""
-"The flavor ID is generated by OpenStack if the option selected is "
-"<guilabel>auto</guilabel>."
-msgstr "選択したオプションが <guilabel>auto</guilabel> の場合、フレーバー ID は OpenStack により生成されます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml90(para)
-msgid "By default, this field is set to <guilabel>auto</guilabel>."
-msgstr "この項目はデフォルトで <guilabel>auto</guilabel> に設定されます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml95(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml82(guilabel)
-msgid "Public"
-msgstr "パブリック"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml98(para)
-msgid "Indicates if the flavor is public."
-msgstr "フレーバーがパブリックであることを意味します。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml109(para)
-msgid "m1.small (1 VCPU/20 GB Disk/2048 MB RAM)"
-msgstr "m1.small (1 仮想CPU/20 GB ディスク/2048 MB メモリ)"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml112(para)
-msgid "m1.medium (2 VCPU/40 GB Disk/4096 MB RAM)"
-msgstr "m1.medium (2 仮想CPU/40 GB ディスク/3072 MB メモリ)"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml115(para)
-msgid "m1.large (4 VCPU/80 GB Disk/8192 MB RAM)"
-msgstr "m1.large (4 仮想CPU/80 GB ディスク/8192 MB メモリ)"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml118(para)
-msgid "m1.xlarge (8 VCPU/160 GB Disk/16384 MB RAM)"
-msgstr "m1.xlarge (8 仮想CPU/160 GB ディスク/16384 MB メモリ)"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml122(title)
-msgid "Create flavors"
-msgstr "フレーバーの作成"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml131(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml256(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml284(para)
-msgid ""
-"On the <guilabel>Admin</guilabel> tab, click the "
-"<guilabel>Flavors</guilabel> category."
-msgstr "<guilabel>管理</guilabel> タブで、<guilabel>フレーバー</guilabel>カテゴリーをクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml135(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml241(para)
-msgid "Click <guibutton>Create Flavor</guibutton>."
-msgstr "<guibutton>フレーバーの作成</guibutton>をクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml139(para)
-msgid ""
-"In the <guilabel>Create Flavor</guilabel> window, enter or select the "
-"following values:"
-msgstr "<guilabel>フレーバーの作成</guilabel>ウィンドウで以下の値を入力または選択します。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml148(guilabel)
-msgid "Flavor Info"
-msgstr "フレーバー情報"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml157(para)
-msgid "Enter the flavor name."
-msgstr "フレーバーの名前を入力します。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml167(para)
-msgid "The flavor ID, generated by OpenStack."
-msgstr "OpenStack により生成されるフレーバー ID。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml175(para)
-msgid "Enter the number of virtual CPUs to use."
-msgstr "使用する仮想 CPU 数を入力します。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml181(guilabel)
-msgid "RAM MB"
-msgstr "メモリー MB"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml184(para)
-msgid "Enter the amount of RAM to use, in megabytes."
-msgstr "使用するメモリ量をメガバイト単位で入力します。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml193(para)
-msgid ""
-"Enter the mount of disk space in gigabytes to use for the root (/) "
-"partition."
-msgstr "ルート (/) パーティションに使用するディスク容量をギガバイト単位で入力します。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml203(para)
-msgid ""
-"Enter the amount of disk space in gigabytes to use for the ephemeral "
-"partition. If unspecified, the value is 0 by default."
-msgstr "一時パーティションに使用するディスク容量をギガバイト単位で入力します。省略すると、デフォルトで 0 になります。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml219(guilabel)
-msgid "Swap Disk MB"
-msgstr "スワップディスク MB"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml222(para)
-msgid ""
-"Enter the amount of swap space (in megabytes) to use. If unspecified, the "
-"default is 0."
-msgstr "使用するスワップ容量をメガバイト単位で入力します。省略すると、デフォルトで 0 になります。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml232(para)
-msgid ""
-"In the <guilabel>Flavor Access</guilabel> tab, you can control access to the"
-" flavor by moving projects from the <guilabel>All Projects</guilabel> column"
-" to the <guilabel>Selected Projects</guilabel> column."
-msgstr "<guilabel>フレーバーアクセス権</guilabel>タブで、<guilabel>すべてのプロジェクト</guilabel>列から<guilabel>選択済みプロジェクト</guilabel>列にプロジェクトを移動して、フレーバーへのアクセス権を制御できます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml236(para)
-msgid ""
-"Only projects in the <guilabel>Selected Projects</guilabel> column can use "
-"the flavor. If there are no projects in the right column, all projects can "
-"use the flavor."
-msgstr "<guilabel>選択済みプロジェクト</guilabel>列にあるプロジェクトだけがこのフレーバーを使用できます。右側にプロジェクトがひとつもない場合は、すべてのプロジェクトがこのフレーバーを使用できます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml247(title)
-msgid "Update flavors"
-msgstr "フレーバーの更新"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml260(para)
-msgid ""
-"Select the flavor that you want to edit. Click <guibutton>Edit "
-"Flavor</guibutton>."
-msgstr "編集したいフレーバーを選択します。<guibutton>フレーバーの編集</guibutton>をクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml264(para)
-msgid ""
-"In the <guilabel>Edit Flavor</guilabel> window, you can change the flavor "
-"name, VCPUs, RAM, root dish, ephemeral disk, and swap disk values.."
-msgstr "<guilabel>フレーバーの編集</guilabel>ウィンドウで、フレーバー名、仮想 CPU 数、メモリ、ルートディスク、一時ディスク、スワップディスクの値を変更できます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml270(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml132(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml197(para)
-msgid "Click <guibutton>Save</guibutton>."
-msgstr "<guibutton>保存</guibutton>をクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml275(title)
-msgid "Delete flavors"
-msgstr "フレーバーの削除"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml288(para)
-msgid "Select the flavors that you want to delete."
-msgstr "削除したいフレーバーを選択します。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml292(para)
-msgid "Click <guibutton>Delete Flavors</guibutton>."
-msgstr "<guibutton>フレーバーの削除</guibutton>をクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml296(para)
-msgid ""
-"In the <guilabel>Confirm Delete Flavors</guilabel> window, click "
-"<guibutton>Delete Flavors</guibutton> to confirm the deletion. You cannot "
-"undo this action."
-msgstr "<guilabel>フレーバーの削除の確認</guilabel>ウィンドウで、削除の確認をするために<guibutton>フレーバーの削除</guibutton>をクリックします。この操作を取り消すことはできません。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml8(para)
-msgid ""
-"Security groups are sets of IP filter rules that are applied to all project "
-"instances, which define networking access to the instance. Group rules are "
-"project specific; project members can edit the default rules for their group"
-" and add new rule sets."
-msgstr "セキュリティグループは、すべてのプロジェクトのインスタンスに適用される、IP フィルター群です。インスタンスへのネットワークアクセスを定義します。グループのルールはプロジェクト固有です。プロジェクトのメンバーは、これらのグループのデフォルトルールを編集し、新しいルール群を追加できます。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml13(para)
-msgid ""
-"All projects have a \"default\" security group which is applied to any "
-"instance that has no other defined security group. Unless you change the "
-"default, this security group denies all incoming traffic and allows only "
-"outgoing traffic to your instance."
-msgstr "すべてのプロジェクトは、他に定義されたセキュリティグループが無いインスタンスに適用されるデフォルトのセキュリティグループがあります。デフォルトを変更していなければ、このセキュリティグループは、すべての入力通信を拒否し、インスタンスの出力通信のみを許可します。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml19(para)
-msgid ""
-"For information about updating rules using the dashboard, see <xref "
-"linkend=\"dashboard_manage_projects_security\"/>."
-msgstr "ダッシュボードを用いたルールの更新方法の詳細は <xref linkend=\"dashboard_manage_projects_security\"/> を参照してください。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml23(para)
-msgid ""
-"You can use the <code>allow_same_net_traffic</code> option in the "
-"<filename>/etc/nova/nova.conf</filename> file to globally control whether "
-"the rules apply to hosts which share a network."
-msgstr "ネットワークを共有しているホストに適用されるルールを全体的に制御するために、<filename>/etc/nova/nova.conf</filename> ファイルで <code>allow_same_net_traffic</code> オプションを使用できます。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml27(para)
-msgid "If set to:"
-msgstr "設定した場合:"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml30(para)
-msgid ""
-"<code>True</code> (default), hosts on the same subnet are not filtered and "
-"are allowed to pass all types of traffic between them. On a flat network, "
-"this allows all instances from all projects unfiltered communication. With "
-"VLAN networking, this allows access between instances within the same "
-"project. You can also simulate this setting by configuring the default "
-"security group to allow all traffic from the subnet."
-msgstr "<code>True</code> (デフォルト)、同じサブネットにあるホストはフィルターされず、それらの間ですべての種類の通信が通過できるようになります。フラットなネットワークでは、これにより、全プロジェクトの全インスタンスが通信をフィルターされなくなります。VLAN ネットワークでは、これにより、同じプロジェクト内のインスタンス間でアクセスが許可されます。デフォルトのセキュリティグループをそのサブネットからのすべての通信を許可するよう設定することにより、この設定と同じ状態にすることもできます。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml41(para)
-msgid "<code>False</code>, security groups are enforced for all connections."
-msgstr "<code>False</code>、セキュリティグループがすべての通信に対して強制されます。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml45(para)
-msgid ""
-"Additionally, the number of maximum rules per security group is controlled "
-"by the <code>security_group_rules</code> and the number of allowed security "
-"groups per project is controlled by the <code>security_groups</code> quota "
-"(see <xref linkend=\"cli_set_quotas\"/>)."
-msgstr "加えて、セキュリティグループごとの最大ルール数は、<code>security_group_rules</code> により制御されます。また、プロジェクトごとに許可されるセキュリティグループ数は、<code>security_groups</code> クォータにより制御されます (<xref linkend=\"cli_set_quotas\"/>参照)。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml51(title)
-msgid "List and view current security groups"
-msgstr "現在のセキュリティグループの一覧表示"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml52(para)
-msgid ""
-"From the command line you can get a list of security groups for the project,"
-" using the nova command:"
-msgstr "コマンドラインから nova コマンドを使用して、プロジェクトに対するセキュリティグループの一覧を取得できます:"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml56(para)
-msgid ""
-"Ensure your system variables are set for the user and tenant for which you "
-"are checking security group rules for. For example:"
-msgstr "セキュリティグループルールを確認したいユーザーとプロジェクト向けのシステム変数をきちんと設定します。例:"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml63(para)
-msgid "Output security groups, as follows:"
-msgstr "以下のとおり、セキュリティグループを出力します。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml73(para)
-msgid "View the details of a group, as follows:"
-msgstr "以下のとおり、グループの詳細を表示します。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml74(replaceable)
-msgid "groupName"
-msgstr "groupName"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml84(para)
-msgid ""
-"These rules are allow type rules as the default is deny. The first column is"
-" the IP protocol (one of icmp, tcp, or udp). The second and third columns "
-"specify the affected port range. The third column specifies the IP range in "
-"CIDR format. This example shows the full port range for all protocols "
-"allowed from all IPs."
-msgstr "標準で拒否されるので、これらのルールはすべて「許可」形式のルールです。1 番目の項目は IP プロトコル (icmp, tcp, udp のどれか) です。2 番目と 3 番目の項目は影響するポート範囲を指定します。3 番目の項目は CIDR 形式の IP 範囲を指定します。この例はすべての IP から許可される、すべてのプロトコルの全ポート範囲を表します。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml95(para)
-msgid ""
-"When adding a new security group, you should pick a descriptive but brief "
-"name. This name shows up in brief descriptions of the instances that use it "
-"where the longer description field often does not. For example, seeing that "
-"an instance is using security group \"http\" is much easier to understand "
-"than \"bobs_group\" or \"secgrp1\"."
-msgstr "新しいセキュリティグループを追加するとき、説明的ですが、簡単な名前をつけるべきです。この名前はインスタンスの簡単な説明が示されます。より長い説明の項目が使用されないところで使用されます。例えば、インスタンスがセキュリティグループ \"http\" を使用していること、\"bobs_group\" や \"secgrp1\" よりも理解しやすいです。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml102(para)
-msgid ""
-"Ensure your system variables are set for the user and tenant for which you "
-"are checking security group rules for."
-msgstr "セキュリティグループルールを確認したいユーザーとプロジェクト向けのシステム変数をきちんと設定します。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml107(para)
-msgid "Add the new security group, as follows:"
-msgstr "以下のとおり、新しいセキュリティグループを追加します。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml109(replaceable)
-msgid "Group Name Description"
-msgstr "Group Name Description"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml122(para)
-msgid "Add a new group rule, as follows:"
-msgstr "以下のとおり、新しいグループルールを追加します。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml124(replaceable)
-msgid "secGroupName ip-protocol from-port to-port CIDR"
-msgstr "secGroupName ip-protocol from-port to-port CIDR"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml126(para)
-msgid ""
-"The arguments are positional, and the \"from-port\" and \"to-port\" "
-"arguments specify the local port range connections are allowed to access, "
-"not the source and destination ports of the connection. For example:"
-msgstr "引数の順番は決まっています。そして、\"from-port\" と \"to-port\" の引数はアクセスが許可されるローカルのポート範囲を指定し、接続の送信元ポートと宛先ポートではないことに注意してください。より複雑なルールセットが、複数の nova secgroup-add-rule の呼び出しから構成できます。例:"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml139(para)
-msgid ""
-"You can create complex rule sets by creating additional rules. For example, "
-"if you want to pass both http and https traffic, run:"
-msgstr "追加ルールを作成することにより、複雑なルールセットを作成できます。例えば、http と https の通信をどちらも許可したい場合、以下を実行します。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml148(para)
-msgid ""
-"Despite only outputting the newly added rule, this operation is additive "
-"(both rules are created and enforced)."
-msgstr "新しく追加されたルールのみが出力されますが、この操作は追加操作です (どちらのルールも作成され、強制されます):"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml153(para)
-msgid "View all rules for the new security group, as follows:"
-msgstr "以下のとおり、新しいセキュリティグループのすべてのルールを表示します。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml167(para)
-msgid ""
-"Ensure your system variables are set for the user and tenant for which you "
-"are deleting a security group for."
-msgstr "セキュリティグループを削除したいユーザーとプロジェクト向けのシステム変数をきちんと設定します。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml172(para)
-msgid "Delete the new security group, as follows:"
-msgstr "以下のとおり、新しいセキュリティグループを削除します。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml173(replaceable)
-msgid "GroupName"
-msgstr "GroupName"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml179(title)
-msgid "Create security group rules for a cluster of instances"
-msgstr "インスタンスのクラスター向けにセキュリティグループのルールを作成します。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml181(para)
-msgid ""
-"Source Groups are a special, dynamic way of defining the CIDR of allowed "
-"sources. The user specifies a Source Group (Security Group name), and all "
-"the users' other Instances using the specified Source Group are selected "
-"dynamically. This alleviates the need for individual rules to allow each new"
-" member of the cluster."
-msgstr "ソースグループは許可されたソースの CIDR を動的に定義する特別な方法です。ユーザーがソースグループ (セキュリティグループ名) を指定します。これにより、指定されたソースグループを使用する、ユーザーの他のインスタンスが動的にすべて選択されます。これにより、クラスターのそれぞれの新しいメンバーを許可する、個別のルールの必要性を軽減できます。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml188(para)
-msgid ""
-"Make sure to set the system variables for the user and tenant for which you "
-"are deleting a security group for."
-msgstr "セキュリティグループを削除したいユーザーとプロジェクト向けのシステム変数をきちんと設定します。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml193(para)
-msgid "Add a source group, as follows:"
-msgstr "以下のとおり、ソースグループを追加します。"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml194(replaceable)
-msgid "secGroupName source-group ip-protocol from-port to-port"
-msgstr "secGroupName source-group ip-protocol from-port to-port"
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml197(para)
-msgid ""
-"The <code>cluster</code> rule allows ssh access from any other instance that"
-" uses the <code>global_http</code> group."
-msgstr "<code>cluster</code> ルールにより、<code>global_http</code> グループを使用する、他のすべてのインスタンスからの SSH アクセスを許可されます。"
+"To view the list of valid compute hosts, use the <placeholder-1/> command, "
+"as follows:"
+msgstr "有効なコンピュートホストの一覧を表示するために、以下のとおり <placeholder-1/> コマンドを使用します。"
 
 #. When image changes, this message will be marked fuzzy or untranslated for
 #. you.
@@ -2287,260 +2983,6 @@ msgid ""
 "<guibutton>Delete Users</guibutton> to confirm the deletion."
 msgstr "<guilabel>ユーザーの削除の確認</guilabel>ウィンドウで、削除の確認をするために<guibutton>ユーザーの削除</guibutton>をクリックします。"
 
-#: ./doc/user-guide-admin/ch_cli.xml10(title)
-msgid "OpenStack command-line clients"
-msgstr "OpenStack コマンドラインクライアント"
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml6(title)
-msgid "Manage Block Storage service quotas"
-msgstr "ブロックストレージのクォータの管理"
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml7(para)
-msgid ""
-"As an administrative user, you can update the OpenStack Block Storage "
-"service quotas for a project. You can also update the quota defaults for a "
-"new project."
-msgstr "管理ユーザーは、プロジェクトの Block Storage のクォータを更新できます。また、新規プロジェクトのクォータのデフォルト値も更新できます。"
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml12(caption)
-msgid "Block Storage quotas"
-msgstr "ブロックストレージのクォータ"
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml17(th)
-msgid "Property name"
-msgstr "プロパティ名"
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml18(th)
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml38(th)
-msgid "Defines the number of"
-msgstr "定義する数値"
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml24(para)
-msgid "gigabytes"
-msgstr "gigabytes"
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml27(para)
-msgid "Volume gigabytes allowed for each tenant."
-msgstr "各プロジェクトに許可されるボリュームのギガバイト容量。"
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml33(para)
-msgid "snapshots"
-msgstr "snapshots"
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml36(para)
-msgid "Volume snapshots allowed for each tenant."
-msgstr "各プロジェクトに許可されるボリュームのスナップショット数。"
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml42(para)
-msgid "volumes"
-msgstr "volumes"
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml45(para)
-msgid "Volumes allowed for each tenant."
-msgstr "各プロジェクトに許可されるボリューム数。"
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml52(title)
-msgid "View and update Block Storage service quotas"
-msgstr "Block Storage のクォータの表示と更新"
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml53(para)
-msgid ""
-"As an administrative user, you can view and update Block Storage service "
-"quotas."
-msgstr "管理ユーザーは、Block Storage のクォータを表示および更新できます。"
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml57(para)
-msgid "List the default quotas for all projects, as follows:"
-msgstr "以下のように、全プロジェクトのデフォルトクォータを一覧表示します。"
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml69(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> ファイルのプロパティを更新します。"
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml77(para)
-msgid "View Block Storage service quotas for a project, as follows:"
-msgstr "以下のように、プロジェクトの Block Storage のクォータを表示します。"
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml79(replaceable)
-msgid "TENANT_NAME"
-msgstr "TENANT_NAME"
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml91(para)
-msgid ""
-"To update Block Storage service quotas, place the tenant ID in a usable "
-"variable, as follows:"
-msgstr "Block Storage のクォータを更新するために、以下のとおり、利用可能な変数にプロジェクト ID を置きます。"
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml94(replaceable)
-msgid "tenantName"
-msgstr "tenantName"
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml97(para)
-msgid "Update a particular quota value, as follows:"
-msgstr "指定したクォータ値を更新します。"
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml99(replaceable)
-msgid "quotaName"
-msgstr "quotaName"
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml99(replaceable)
-msgid "NewValue"
-msgstr "NewValue"
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml99(replaceable)
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml114(replaceable)
-#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml39(replaceable)
-msgid "tenantID"
-msgstr "tenantID"
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml112(para)
-msgid "To clear per-tenant quota limits, use the <placeholder-1/> command:"
-msgstr "テナントごとのクォータ制限を解除するために、<placeholder-1/> コマンドを使用します。"
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml7(title)
-msgid "Analyze log files"
-msgstr "ログファイルの分析"
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml8(para)
-msgid "Use the swift command-line client to analyze log files."
-msgstr "ログファイルを分析するために swift コマンドラインクライアントを使用します。"
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml9(para)
-msgid "The swift client is simple to use, scalable, and flexible."
-msgstr "swift クライアントは、使用しやすく、拡張可能かつ柔軟です。"
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml9(para)
-msgid ""
-"Use the swift client <option>-o</option> or <option>-output</option> option "
-"to get short answers to questions about logs,"
-msgstr "ログに関する問い合わせの応答を短縮するために、swift クライアントの <option>-o</option> または <option>-output</option> オプションを使用します。"
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml12(para)
-msgid ""
-"You can use the <option>-o —output</option> option with a single object "
-"download to redirect the command output to a specific file or to STDOUT "
-"(<literal>-</literal>). The ability to redirect the output to STDOUT enables"
-" you to pipe (<literal>|</literal>) data without saving it to disk first."
-msgstr "コマンドの出力を特定のファイル、または標準出力 (<literal>-</literal>) にリダイレクトするために、単一オブジェクトのダウンロードで <option>-o —output</option> オプションを使用できます。出力を標準出力へリダイレクトする機能により、最初にディスクに保存することなく、データをパイプ (<literal>|</literal>) できます。"
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml18(title)
-msgid "Upload and analyze log files"
-msgstr "ログファイルのアップロードと分析"
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml20(para)
-msgid ""
-"This example assumes that <filename>logtest</filename> directory contains "
-"the following log files:"
-msgstr "この例は、<filename>logtest</filename> ディレクトリに以下のログファイルが含まれることを仮定しています。"
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml23(title)
-msgid "Example files"
-msgstr "サンプルファイル"
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml27(para)
-msgid "Each file uses the following line format:"
-msgstr "各ファイルは以下の行の形式を使用します。"
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml28(title)
-msgid "Log line format"
-msgstr "ログの行形式"
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml31(para)
-msgid ""
-"Change into the <filename class=\"directory\">logtest</filename> directory:"
-msgstr "<filename class=\"directory\">logtest</filename> ディレクトリに移動します。"
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml35(para)
-msgid "Upload the log files into the <filename>logtest</filename> container:"
-msgstr "<filename>logtest</filename> コンテナーにログファイルをアップロードします。"
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml42(para)
-msgid "Get statistics for the account:"
-msgstr "アカウントの統計情報を取得します。"
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml48(para)
-msgid "Get statistics for the logtest container:"
-msgstr "logtest コンテナーの統計情報を取得します。"
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml56(para)
-msgid "List all objects in the logtest container:"
-msgstr "logtest コンテナーにあるすべてのオブジェクトを一覧表示します。"
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml62(title)
-msgid "Download and analyze an object"
-msgstr "オブジェクトのダウンロードと分析"
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml64(para)
-msgid ""
-"This example uses the <option>-o —output</option> option and a hyphen "
-"(<literal>-</literal>) to get information about an object."
-msgstr "この例は、オブジェクトに関する情報を取得するために、<option>-o —output</option> オプションとハイフン (<literal>-</literal>) を使用します。"
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml67(para)
-msgid ""
-"Use the swift <placeholder-1/> command to download the object. On this "
-"command, stream the output to <placeholder-2/> to break down requests by "
-"return code and the date <literal>2200 on November 16th, 2010</literal>."
-msgstr "オブジェクトをダウンロードするために、swift <placeholder-1/> コマンドを使用します。このコマンドは、リターンコードと日付 <literal>2200 on November 16th, 2010</literal> を用いてリクエストを解釈するために、出力を <placeholder-2/> に渡します。"
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml72(para)
-msgid ""
-"Using the log line format, find the request type in column 9 and the return "
-"code in column 12."
-msgstr "ログ行形式を用いて、9 列目のリクエスト種別と 12 列目のリターンコードを検索します。"
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml74(para)
-msgid ""
-"After <placeholder-1/> processes the output, it pipes it to <placeholder-2/>"
-" and <placeholder-3/> to sum up the number of occurrences for each request "
-"type and return code combination."
-msgstr "<placeholder-1/> が出力を処理した後、それぞれのリクエスト種別とリターンコードの組み合わせの発生数を合計するために、それを <placeholder-2/> と <placeholder-3/> に渡します。"
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml80(para)
-msgid "Download an object:"
-msgstr "オブジェクトをダウンロードします。"
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml113(para)
-msgid "Discover how many PUT requests are in each log file."
-msgstr "何回の PUT リクエストが各ログファイルにあったかを検索します。"
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml114(para)
-msgid ""
-"Use a bash for loop with awk and swift with the <option>-o —output</option> "
-"option and a hyphen (<literal>-</literal>) to discover how many PUT requests"
-" are in each log file."
-msgstr "何回の PUT リクエストが各ログファイルにあったかを検索するために、<option>-o —output</option> オプションとハイフン (<literal>-</literal>) を用いた awk と swift コマンドをループされるために bash を使用します。"
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml119(para)
-msgid ""
-"Run the swift <placeholder-1/> command to list objects in the logtest "
-"container. Then, for each item in the list, run the swift <placeholder-2/> "
-"command. Pipe the output into grep to filter the PUT requests. Finally, pipe"
-" into <placeholder-3/> to count the lines."
-msgstr "logtest コンテナーにあるオブジェクトを一覧表示するために、swift <placeholder-1/> コマンドを実行します。次に、一覧の各項目に対して、swift <placeholder-2/> コマンドを実行します。PUT リクエストをフィルターするために、出力を grep にパイプします。最後に、行数を集計するために <placeholder-3/> にパイプします。"
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml134(para)
-msgid "List the object names that begin with a specified string."
-msgstr "指定した文字列から始まるオブジェクト名を一覧表示します。"
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml136(para)
-msgid ""
-"Run the swift <placeholder-1/> command to list objects in the logtest "
-"container that begin with the <literal>2010-11-15</literal> string."
-msgstr "logtest コンテナーにある <literal>2010-11-15</literal> という文字列から始まるオブジェクトを一覧表示するために、swift <placeholder-1/> コマンドを実行します。"
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml140(para)
-msgid "For each item in the list, run the swift <placeholder-1/> command."
-msgstr "一覧の各項目に対して、swift <placeholder-1/> コマンドを実行します。"
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml142(para)
-msgid ""
-"Pipe the output to <placeholder-1/> and <placeholder-2/>. Use the "
-"<placeholder-3/> command to display the object name."
-msgstr "出力を <placeholder-1/> と <placeholder-2/> にパイプします。オブジェクト名を表示するために、<placeholder-3/> コマンドを使用します。"
-
 #: ./doc/user-guide-admin/section_cli_admin_manage_environment.xml4(title)
 msgid "Manage the OpenStack environment"
 msgstr "OpenStack 環境の管理"
@@ -2549,627 +2991,185 @@ msgstr "OpenStack 環境の管理"
 msgid "This section includes tasks specific to the OpenStack environment."
 msgstr "このセクションは、OpenStack 環境に固有の作業を含みます。"
 
-#: ./doc/user-guide-admin/section_cli_manage_services.xml7(title)
-msgid "Manage services"
-msgstr "サービスの管理"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml7(title)
-msgid "Create and manage images"
-msgstr "イメージの作成と管理"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml8(para)
-msgid ""
-"As an administrative user, you can create and manage images for the projects"
-" to which you belong. You can also create and manage images for users in all"
-" projects to which you have access."
-msgstr "管理ユーザーとして、所属するプロジェクト用のイメージを作成、管理できます。また、アクセス権を持つすべてのプロジェクトのユーザー用にイメージを作成、管理できます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml12(para)
-msgid ""
-"To create and manage images in specified projects as an end user, see the "
-"<link href=\"http://docs.openstack.org/user-"
-"guide/content/\"><citetitle>OpenStack End User Guide</citetitle></link>."
-msgstr "エンドユーザーとして指定したプロジェクトにイメージを作成、管理する方法は、<link href=\"http://docs.openstack.org/user-guide/content/\"><citetitle>OpenStack エンドユーザーガイド</citetitle></link>を参照してください。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml17(para)
-msgid ""
-"To create and manage images as an administrator for other users, use the "
-"following procedures."
-msgstr "管理者として他のユーザー向けにイメージを作成、管理するために、以下の手順を使用します。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml20(title)
-msgid "Create images"
-msgstr "イメージの作成"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml21(para)
-msgid ""
-"For details about image creation, see the <link "
-"href=\"http://docs.openstack.org/image-guide/content/\"><citetitle>Virtual "
-"Machine Image Guide</citetitle></link>."
-msgstr "イメージの作成に関する詳細は<link href=\"http://docs.openstack.org/image-guide/content/\"><citetitle>仮想マシンイメージガイド</citetitle></link>を参照してください。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml33(para)
-msgid ""
-"On the <guilabel>Admin</guilabel> tab, click the <guilabel>Images</guilabel>"
-" category. The images that you can administer for cloud users appear on this"
-" page."
-msgstr "<guilabel>管理</guilabel>タブで、<guilabel>Images</guilabel>カテゴリーをクリックします。あなたがクラウドユーザー向けに管理できるイメージが、このページに表示されます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml38(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml94(para)
-msgid "Click <guibutton>Create Image</guibutton>."
-msgstr "<guibutton>イメージの作成</guibutton>をクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml41(para)
-msgid ""
-"In the <guilabel>Create An Image</guilabel> window, enter or select the "
-"following values:"
-msgstr "<guilabel>イメージの作成</guilabel>ウィンドウで以下の値を入力または選択します。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml49(para)
-msgid "Enter a name for the image."
-msgstr "イメージの名前を入力します。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml53(para)
-msgid "Enter a brief description about the image."
-msgstr "イメージの簡単な説明を入力します。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml57(guilabel)
-msgid "Image Source"
-msgstr "イメージソース"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml58(para)
-msgid ""
-"Choose the image source from the dropdown list. Your choices are "
-"<guilabel>Image Location</guilabel> and <guilabel>Image File</guilabel>."
-msgstr "ドロップダウンリストからイメージのソースを選択します。<guilabel>イメージの場所</guilabel>と<guilabel>イメージファイル</guilabel>を選択できます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml63(para)
-msgid "<guilabel>Image File</guilabel> or <guilabel>Image Location</guilabel>"
-msgstr "<guilabel>イメージファイル</guilabel>または<guilabel>イメージの場所</guilabel>"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml66(para)
-msgid ""
-"Based on your selection, there is an <guilabel>Image File </guilabel> or "
-"<guilabel>Image Location</guilabel> field. You can include the location URL "
-"or browse for the image file on your file system and add it."
-msgstr "選択した内容に応じて、<guilabel>イメージのファイル</guilabel>や<guilabel>イメージの場所</guilabel>の項目が表示されます。場所の URL を指定したり、お使いのファイルシステムにあるイメージファイルを参照して追加したりできます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml72(guilabel)
-msgid "Format"
-msgstr "形式"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml73(para)
-msgid "Select the image format."
-msgstr "イメージの形式を選択します。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml76(para)
-msgid ""
-"<guilabel>Minimum Disk (GB)</guilabel> and <guilabel>Minimum RAM "
-"(MB)</guilabel>"
-msgstr "<guilabel>最小ディスク (GB)</guilabel> および<guilabel>最小メモリ (MB)</guilabel>"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml78(para)
-msgid "Leave these fields empty."
-msgstr "この項目を空白のままにします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml83(para)
-msgid "Select this option to make the image public to all users."
-msgstr "すべてのユーザーにイメージを公開する場合、このオプションを選択します。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml86(guilabel)
-msgid "Protected"
-msgstr "保護"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml87(para)
-msgid ""
-"Select this option to ensure that only users with permissions can delete it."
-msgstr "権限を持つユーザーのみがこのイメージを削除できるようにする場合、このオプションを選択します。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml95(para)
-msgid ""
-"The image is queued to be uploaded. It might take some time before the "
-"status changes from queued to active."
-msgstr "イメージがアップロードのためにキューに入れられます。ステータスがキュー済みからアクティブに変更されるまでに少し時間がかかるかもしれません。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml101(title)
-msgid "Update images"
-msgstr "イメージの更新"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml110(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml140(para)
-msgid ""
-"On the <guilabel>Admin</guilabel> tab, click the <guilabel>Images</guilabel>"
-" category."
-msgstr "<guilabel>管理</guilabel>タブで、<guilabel>イメージ</guilabel>カテゴリーをクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml114(para)
-msgid ""
-"Select the image that you want to edit. Click <guilabel>Edit</guilabel>."
-msgstr "編集したいイメージを選択します。<guilabel>編集</guilabel>をクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml118(para)
-msgid ""
-"In the <guilabel>Update Image</guilabel> window, you can change the name for"
-" the image. Select the <guilabel>Public</guilabel> check box to make the "
-"image public. Clear this check box to make the image private. You cannot "
-"change the kernel ID, RAM disk ID, or architecture attributes for an image."
-msgstr "<guilabel>イメージの更新</guilabel>ウィンドウで、イメージの名前を変更できます。イメージをパブリックにする場合、<guilabel>パブリック</guilabel>チェックボックスを選択します。イメージをプライベートにする場合、このチェックボックスを解除します。イメージのカーネル ID、メモリ、RAM ディスク ID、アーキテクチャーの属性は変更できません。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml126(para)
-msgid "Click <guibutton>Update Image</guibutton>."
-msgstr "<guibutton>イメージの更新</guibutton>をクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml131(title)
-msgid "Delete images"
-msgstr "イメージの削除"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml144(para)
-msgid "Select the images that you want to delete."
-msgstr "削除したいイメージを選択します。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml147(para)
-msgid "Click <guibutton>Delete Images</guibutton>."
-msgstr "<guibutton>イメージの削除</guibutton>をクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml150(para)
-msgid ""
-"In the <guilabel>Confirm Delete Image</guilabel> window, click "
-"<guibutton>Delete Images</guibutton> to confirm the deletion."
-msgstr "<guilabel>イメージの削除の確認</guilabel>ウィンドウで、削除を確認するために<guibutton>イメージの削除</guibutton>をクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml153(para)
-msgid "You cannot undo this action."
-msgstr "この操作は取り消しできません。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml11(title)
-msgid "View and manage quotas"
-msgstr "クォータの表示と管理"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml12(para)
-#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml12(para)
-msgid ""
-"To prevent system capacities from being exhausted without notification, you "
-"can set up quotas. Quotas are operational limits. For example, the number of"
-" gigabytes allowed for each tenant can be controlled so that cloud resources"
-" are optimized. Quotas can be enforced at both the tenant (or project) and "
-"the tenant-user level."
-msgstr "通知なしにシステム容量が使い切られてしまうことを避けるため、クォータを設定することができます。クォータは運用上の上限です。例えば、クラウドのリソースが最適化されるように、テナント毎に許容されるギガバイト数を制御できます。クォータは、テナント (プロジェクト) 単位とテナントユーザー単位に適用できます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml17(para)
-msgid ""
-"Typically, you change quotas when a project needs more than ten volumes or "
-"1TB on a compute node."
-msgstr "一般的に、プロジェクトが 1 つのコンピュートノードに 10 以上のボリューム、1TB 以上を必要とするとき、クォータを変更します。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml19(para)
-msgid ""
-"Using the Dashboard, you can view default Compute and Block Storage quotas "
-"for new tenants, as well as update quotas for existing tenants."
-msgstr "ダッシュボードを使用して、新しいプロジェクトの Compute と Block Storage のデフォルトクォータ値を表示できます。また、既存のプロジェクトのクォータを更新することもできます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml22(para)
-msgid ""
-"Using the command-line interface, you can manage quotas for the OpenStack "
-"Compute service, the OpenStack Block Storage service, and the OpenStack "
-"Networking service (see <xref linkend=\"cli_set_quotas\"/>). Additionally, "
-"you can update Compute service quotas for tenant users."
-msgstr "コマンドラインインターフェースを用いて、OpenStack Compute、OpenStack Block Storage、OpenStack Networking のクォータを管理できます (<xref linkend=\"cli_set_quotas\"/> 参照)。また、プロジェクトのユーザーに対する Compute のクォータを更新できます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml28(para)
-msgid ""
-"The following table describes the Compute and Block Storage service quotas:"
-msgstr "以下の表は、Compute と Block Storage のクォータを記載しています。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml31(caption)
-msgid "Quota Descriptions"
-msgstr "クォータの説明"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml37(th)
-msgid "Quota Name"
-msgstr "クォータ名"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml39(th)
-msgid "Service"
-msgstr "サービス"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml45(para)
-msgid "Gigabytes"
-msgstr "ギガバイト"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml48(para)
-msgid "Volume gigabytes allowed for each project."
-msgstr "各プロジェクトに許可されるボリュームのギガバイト容量。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml50(td)
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml131(td)
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml149(td)
-msgid "Block Storage"
-msgstr "ブロックストレージ"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml54(para)
-msgid "Instances"
-msgstr "インスタンス"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml57(para)
-msgid "Instances allowed for each project."
-msgstr "各プロジェクトに許可されるインスタンス数。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml59(td)
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml68(td)
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml77(td)
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml86(td)
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml95(td)
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml104(td)
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml113(td)
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml122(td)
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml140(td)
-msgid "Compute"
-msgstr "コンピュート"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml63(para)
-msgid "Injected Files"
-msgstr "注入ファイル"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml66(para)
-msgid "Injected files allowed for each project."
-msgstr "各プロジェクトに許可されるインジェクトファイル数。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml72(para)
-msgid "Injected File Content Bytes"
-msgstr "注入ファイルのバイト数"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml75(para)
-msgid "Content bytes allowed for each injected file."
-msgstr "各インジェクトファイルに許可されるバイト数。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml81(para)
-msgid "Keypairs"
-msgstr "キーペア"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml84(para)
-msgid "Number of keypairs."
-msgstr "キーペア数。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml90(para)
-msgid "Metadata Items"
-msgstr "メタデータ項目"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml93(para)
-msgid "Metadata items allowed for each instance."
-msgstr "各インスタンスに許可されるメタデータ項目数。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml99(para)
-msgid "RAM (MB)"
-msgstr "メモリー (MB)"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml102(para)
-msgid "RAM megabytes allowed for each instance."
-msgstr "各インスタンスに許可されるメモリのメガバイト容量。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml108(para)
-msgid "Security Groups"
-msgstr "セキュリティグループ"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml111(para)
-msgid "Security groups allowed for each project."
-msgstr "各プロジェクトに許可されるセキュリティグループ数。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml117(para)
-msgid "Security Group Rules"
-msgstr "セキュリティグループのルール"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml120(para)
-msgid "Rules allowed for each security group."
-msgstr "各セキュリティグループに許可されるルール数。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml126(para)
-msgid "Snapshots"
-msgstr "スナップショット"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml129(para)
-msgid "Volume snapshots allowed for each project."
-msgstr "各プロジェクトに許可されるボリュームのスナップショット数。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml138(para)
-msgid "Instance cores allowed for each project."
-msgstr "各プロジェクトに許可されるインスタンスのコア数。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml144(para)
-msgid "Volumes"
-msgstr "ボリューム"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml147(para)
-msgid "Volumes allowed for each project."
-msgstr "各プロジェクトに許可されるボリューム数"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml154(title)
-msgid "View default project quotas"
-msgstr "プロジェクトのデフォルトクォータの表示"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml157(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml175(para)
-msgid "Log in to the OpenStack dashboard."
-msgstr "OpenStack Dashboard にログインします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml160(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml178(para)
-msgid ""
-"On the <guilabel>Admin</guilabel> tab, click the "
-"<guilabel>Defaults</guilabel> category."
-msgstr "<guilabel>管理</guilabel> タブで、<guilabel>デフォルト</guilabel>カテゴリーをクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml164(para)
-msgid "The default quota values are displayed."
-msgstr "デフォルトのクォータ値が表示されます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml168(para)
-msgid ""
-"You can sort the table by clicking on either the <guilabel>Quota "
-"Name</guilabel> or <guilabel>Limit</guilabel> column headers."
-msgstr "<guilabel>クォータ名</guilabel>や<guilabel>制限</guilabel>の列ヘッダーをクリックすることにより、表を並び替えられます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml172(title)
-msgid "Update project quotas"
-msgstr "プロジェクトのクォータの更新"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml182(para)
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml188(para)
-msgid "Click the <guibutton>Update Defaults</guibutton> button."
-msgstr "<guibutton>デフォルトの更新</guibutton>ボタンをクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml185(para)
-msgid ""
-"In the <guilabel>Update Default Quotas</guilabel> window, you can edit the "
-"default quota values."
-msgstr "<guilabel>デフォルトクォータの更新</guilabel>ウィンドウで、クォータのデフォルト値を編集できます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml192(para)
-msgid ""
-"The dashboard does not show all possible project quotas. To view and update "
-"the quotas for a service, use its command-line client. See <xref "
-"linkend=\"cli_set_quotas\"/>."
-msgstr "ダッシュボードにすべてのプロジェクトのクォータが表示されるわけではありません。サービスのクォータを表示および更新する場合、コマンドラインクライアントを使用します。<xref linkend=\"cli_set_quotas\"/> を参照してください。"
-
-#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml11(title)
-msgid "Manage quotas"
-msgstr "クォータの管理"
-
-#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml18(para)
-msgid ""
-"Using the command-line interface, you can manage quotas for the OpenStack "
-"Compute service, the OpenStack Block Storage service, and the OpenStack "
-"Networking service."
-msgstr "コマンドラインインターフェースを用いて、OpenStack Compute、OpenStack Block Storage、OpenStack Networking のクォータを管理できます。"
-
-#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml21(para)
-msgid ""
-"The cloud operator typically changes default values because a tenant "
-"requires more than ten volumes or 1TB on a compute node."
-msgstr "1 つのプロジェクトが、1 つのコンピュートノードに 10 以上のボリューム、1TB 以上を必要とするので、クラウド運用者は一般的にデフォルト値を変更します。"
-
-#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml26(para)
-msgid "To view all tenants (projects), run: <placeholder-1/>"
-msgstr "すべてのテナント（プロジェクト）を表示するには、以下のコマンドを実行します。<placeholder-1/>"
-
-#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml37(para)
-msgid "To display all current users for a tenant, run:"
-msgstr "現在のテナントの全ユーザーを表示するには、以下を実行します。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml6(title)
-msgid "View cloud usage statistics"
-msgstr "クラウドの使用状況の表示"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml7(para)
-msgid ""
-"The Telemetry module provides user-level usage data for OpenStack-based "
-"clouds, which can be used for customer billing, system monitoring, or "
-"alerts. Data can be collected by notifications sent by existing OpenStack "
-"components (for example, usage events emitted from Compute) or by polling "
-"the infrastructure (for example, libvirt)."
-msgstr "Telemetry モジュールは、OpenStack ベースのクラウドに関するユーザーレベルの使用状況データを提供します。顧客への課金、システム監視、アラートなどに使用できます。データは、既存の OpenStack コンポーネント (例えば、Compute からの使用状況のイベント) により送信された通知、またはインフラストラクチャー (例えば、libvirt) によるポーリングにより収集できます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml13(para)
-msgid ""
-"You can only view metering statistics on the dashboard (available only to "
-"administrators). The Telemetry service must be set up and administered "
-"through the <placeholder-1/> command-line interface (CLI)."
-msgstr "ダッシュボードでメータリングの統計情報を表示のみできます (管理者のみ利用可能)。Telemetry サービスがセットアップされ、<placeholder-1/> コマンドラインインターフェースにより管理されている必要があります。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml17(para)
-msgid ""
-"For basic administration information, refer to the \"Measure Cloud "
-"Resources\" chapter in the <citetitle>OpenStack End User Guide</citetitle>."
-msgstr "基本的な管理情報は、<citetitle>OpenStack エンドユーザーガイド</citetitle> の「Measure Cloud Resources」の章を参照してください。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml20(title)
-msgid "View resource statistics"
-msgstr "リソースの使用状況の表示"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml23(para)
-msgid "Log in to the OpenStack dashboard as a user with Admin privileges."
-msgstr "管理権限を持つユーザーとして OpenStack Dashboard にログインします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml25(para)
-msgid ""
-"On the <guilabel>Admin</guilabel> tab, click the <guilabel>Resource "
-"Usage</guilabel> category."
-msgstr "<guilabel>管理</guilabel> タブで、<guilabel>リソース使用量</guilabel>カテゴリーをクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml31(para)
-msgid ""
-"<guilabel>Global Disk Usage</guilabel> tab to view disk usage per tenant "
-"(project)."
-msgstr "プロジェクトごとのディスク使用量を表示するための、<guilabel>全体ディスク使用量</guilabel>タブ。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml32(para)
-msgid ""
-"<guilabel>Global Network Traffic Usage</guilabel> tab to view ingress or "
-"egress usage per tenant (project)."
-msgstr "プロジェクトごとの受信および送信の使用量を表示するための、<guilabel>全体のネットワーク通信使用量</guilabel>タブ。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml34(para)
-msgid ""
-"<guilabel>Global Object Storage Usage</guilabel> tab to view incoming and "
-"outgoing storage bytes per tenant (project)."
-msgstr "プロジェクトごとのストレージの受信および送信バイト数を表示するための、<guilabel>全体オブジェクトストレージ使用状況</guilabel>タブ。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml35(para)
-msgid ""
-"<guilabel>Global Network Usage</guilabel> tab to view duration and creation "
-"requests for networks, subnets, routers, ports, and floating IPs, per tenant"
-" (project)."
-msgstr "プロジェクトごとのネットワーク、サブネット、ルーター、ポート、Floating IP の使用期間および作成リクエスト数を表示するための、<guilabel>ネットワーク全体使用量</guilabel>タブ。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml38(para)
-msgid ""
-"<guilabel>Stats</guilabel> tab to view a multi-series line chart with user-"
-"defined metrics. You group by project, define the value type (min, max, avg,"
-" or sum), and specify the time period (or even use a calendar to define a "
-"date range)."
-msgstr "ユーザー定義の測定項目による他系列の折れ線グラフを表示するための、<guilabel>統計</guilabel>タブ。プロジェクトによるグループ化、値の種類の定義 (最小、最大、平均、合計)、対象期間の指定 (日付の期間を定義するためにカレンダーを使用) をできます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml29(para)
-msgid "Click the: <placeholder-1/>"
-msgstr "次をクリックします: <placeholder-1/>"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml6(title)
-msgid "View services information"
-msgstr "サービス情報の表示"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml7(para)
-msgid ""
-"As an administrative user, you can view information for OpenStack services."
-msgstr "管理ユーザーは、OpenStack サービスの情報を表示できます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml11(para)
-msgid ""
-"Log in to the OpenStack dashboard and choose the <guilabel>admin</guilabel> "
-"project from the <guilabel>CURRENT PROJECT</guilabel> drop-down list."
-msgstr "OpenStack のダッシュボードにログインし、<guilabel>現在のプロジェクト</guilabel>ドロップダウンリストから <guilabel>admin</guilabel> プロジェクトを選択します。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml16(para)
-msgid ""
-"On the <guilabel>Admin</guilabel> tab, click the <guilabel>System "
-"Info</guilabel> category."
-msgstr "<guilabel>管理</guilabel> タブで、<guilabel>システム情報</guilabel>カテゴリーをクリックします。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml22(para)
-msgid "<guilabel>Services</guilabel> tab to view services information."
-msgstr "サービスの情報を表示するための、<guilabel>サービス</guilabel>タブ。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml23(para)
-msgid ""
-"The page displays the internal name and the public OpenStack name for the "
-"service, the host where the service runs, and whether the service is or is "
-"not enabled."
-msgstr "サービスの内部名、OpenStack のパブリックな名称、サービスを実行しているホスト、サービスが有効化状態が、このページに表示されます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml27(para)
-msgid ""
-"<guilabel>Compute Services</guilabel> tab to view services specific to the "
-"Compute Service. Both host and zone are listed for each service, as well as "
-"its activation status."
-msgstr "Compute に固有のサービスを表示するための、<guilabel>コンピュートサービス</guilabel>タブ。ホストとゾーンが稼働状態とともに各サービスに対して一覧表示されます。"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml20(para)
-msgid "Click the:<placeholder-1/>"
-msgstr "次をクリックします:<placeholder-1/>"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml36(guilabel)
-msgid "Availability Zones"
-msgstr "アベイラビリティゾーン"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml39(guilabel)
-msgid "Host Aggregates"
-msgstr "ホストアグリゲート"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml42(guilabel)
-msgid "Network Agents"
-msgstr "ネットワークエージェント"
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml34(para)
-msgid ""
-"The <guilabel>System Info</guilabel> window also offers status information "
-"for the following: <placeholder-1/>"
-msgstr "<guilabel>システム情報</guilabel>ウィンドウで、状態に関する以下の情報が提供されます: <placeholder-1/>"
-
-#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml6(title)
-msgid "Select hosts where instances are launched"
-msgstr "インスタンスを起動するホストの選択"
-
-#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml7(para)
-msgid ""
-"With the appropriate permissions, you can select which host instances are "
-"launched on and which roles can boot instances on this host."
-msgstr "適切なパーミッションを用いると、インスタンスが起動されるホスト、このホストでインスタンスを起動できるロールを選択できます。"
-
-#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml12(para)
-msgid ""
-"To select the host where instances are launched, use the "
-"<literal>--availability_zone "
-"<replaceable>zone</replaceable>:<replaceable>host</replaceable></literal> "
-"parameter on the <placeholder-1/> command,"
-msgstr "インスタンスが起動するホストを選択するために、<literal>--availability_zone <replaceable>zone</replaceable>:<replaceable>host</replaceable></literal> parameter on the <placeholder-1/> コマンドを使用します。"
-
-#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml20(para)
-msgid ""
-"To specify which roles can launch an instance on a specified host, enable "
-"the <literal>create:forced_host</literal> option in the "
-"<filename>policy.json</filename> file. By default, this option is enabled "
-"for only the admin role."
-msgstr "指定したホストにインスタンスを起動できるロールを指定するために、<filename>policy.json</filename> ファイルに <literal>create:forced_host</literal> オプションを有効化します。このオプションはデフォルトで、admin ロールのみに対して有効化されます。"
-
-#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml27(para)
-msgid ""
-"To view the list of valid compute hosts, use the <placeholder-1/> command, "
-"as follows:"
-msgstr "有効なコンピュートホストの一覧を表示するために、以下のとおり <placeholder-1/> コマンドを使用します。"
-
-#: ./doc/user-guide-admin/ch_dashboard.xml10(title)
-msgid "Dashboard"
-msgstr "ダッシュボード"
-
-#: ./doc/user-guide-admin/ch_dashboard.xml12(para)
-msgid ""
-"As a cloud administrative user, the OpenStack dashboard lets you create and "
-"manage projects, users, images, and flavors. You can also set quotas and "
-"create and manage services. For information about using the dashboard to "
-"perform end user tasks, see the <link href=\"http://docs.openstack.org/user-"
-"guide/content/\"><citetitle>OpenStack End User Guide</citetitle></link>."
-msgstr "クラウド管理ユーザーとして、OpenStack のダッシュボードにより、プロジェクト、ユーザー、イメージ、フレーバーを作成および管理できます。また、クォータを設定でき、サービスを作成および管理できます。エンドユーザーの作業を実行するために、ダッシュボードを使用する方法の詳細は、<link href=\"http://docs.openstack.org/user-guide/content/\"><citetitle>OpenStack エンドユーザーガイド</citetitle></link>を参照してください。"
-
-#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml15(para)
-msgid "For information about the:"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml14(para)
+msgid "For information about:"
 msgstr "詳細は以下のとおりです。"
 
-#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml19(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml19(para)
 msgid ""
-"Basic creation and deletion of Orchestration stacks, refer to the <link "
+"There are no administration-specific tasks that can be done through the "
+"dashboard."
+msgstr "ダッシュボードから実行できる、管理者固有の作業はありません。"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml18(para)
+msgid ""
+"Administrative tasks on the command line, see <xref "
+"linkend=\"section_cli_admin_manage_stacks\"/>. <placeholder-1/>"
+msgstr "コマンドラインでの管理作業は <xref linkend=\"section_cli_admin_manage_stacks\"/> を参照してください。 <placeholder-1/>"
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml22(para)
+msgid ""
+"The basic creation and deletion of Orchestration stacks, refer to the <link "
 "href=\"http://docs.openstack.org/user-"
 "guide/content/dashboard_stacks.html\">End User Guide</link>."
 msgstr "Orchestration スタックの基本的な作成および削除は <link href=\"http://docs.openstack.org/user-guide/content/dashboard_stacks.html\">OpenStack エンドユーザーガイド</link> を参照してください。"
 
-#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml23(para)
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml8(para)
 msgid ""
-"<systemitem>heat</systemitem> CLI commands, see the <link "
-"href=\"http://docs.openstack.org/cli-reference/content/\"><citetitle> "
-"OpenStack Command Line Interface Reference</citetitle></link>"
-msgstr "<systemitem>heat</systemitem> CLI コマンドは <link href=\"http://docs.openstack.org/cli-reference/content/\"><citetitle> OpenStack Command Line Interface Reference</citetitle></link> を参照してください。"
+"In OpenStack, flavors define the compute, memory, and storage capacity of "
+"nova computing instances. To put it simply, a flavor is an available "
+"hardware configuration for a server. It defines the <quote>size</quote> of a"
+" virtual server that can be launched."
+msgstr "OpenStack ではフレーバーにより、nova コンピューティングインスタンスの CPU、メモリ、ストレージ容量を定義します。簡単に言うと、フレーバーはサーバー用に利用可能なハードウェア設定です。起動できる仮想サーバーの<quote>大きさ</quote>を定義します。"
 
-#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml30(para)
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml14(para)
 msgid ""
-"As an administrator, you can also carry out stack functions on behalf of "
-"your users. For example, to resume, suspend, or delete a stack, run:"
-msgstr "管理ユーザーとして、ユーザーの役割でスタック機能を実行することもできます。例えば、スタックを再開、サスペンド、削除するために、以下を実行します。"
+"Flavors can also determine on which compute host a flavor can be used to "
+"launch an instance. For information about customizing flavors, refer to the "
+"<link href=\"http://docs.openstack.org/admin-guide-"
+"cloud/content/\"><citetitle>OpenStack Cloud Administrator "
+"Guide</citetitle></link>."
+msgstr "フレーバーは、インスタンスを起動するために使用できるコンピュートホストを決めることもできます。フレーバーのカスタマイズの詳細は、<link href=\"http://docs.openstack.org/admin-guide-cloud/content/\"><citetitle>OpenStack Cloud Administrator Guide</citetitle></link> を参照してください。"
 
-#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml32(replaceable)
-#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml33(replaceable)
-#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml34(replaceable)
-msgid "stackID"
-msgstr "stackID"
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml22(term)
+msgid "Flavor ID"
+msgstr "フレーバー ID"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml24(para)
+msgid ""
+"Automatically generated by OpenStack. For private flavors, a value from 1 to"
+" 255."
+msgstr "OpenStack により自動的に生成されます。プライベートなフレーバーの場合、1 ～ 255 の値になります。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml31(para)
+msgid "Name for the new flavor."
+msgstr "新しいフレーバーの名前。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml41(term)
+msgid "Memory MB"
+msgstr "メモリー MB"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml43(para)
+msgid "Amount of RAM to use (in megabytes)."
+msgstr "使用するメモリ量。メガバイト単位。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml67(term)
+msgid "Swap"
+msgstr "スワップ"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml69(para)
+msgid ""
+"Amount of swap space (in megabytes) to use. If unspecified, the value is 0 "
+"by default."
+msgstr "使用するスワップ容量。メガバイト単位。省略すると、デフォルトで 0 になります。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml80(para)
+msgid "m1.smaller (1 VCPU/0 GB Disk/1024 MB RAM)"
+msgstr "m1.smaller (1 仮想CPU/0 GB ディスク/1024 MB メモリ)"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml83(para)
+msgid "m1.small (1 VCPU/10 GB Disk/2048 MB RAM)"
+msgstr "m1.small (1 仮想CPU/10 GB ディスク/2048 MB メモリ)"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml86(para)
+msgid "m1.medium (2 VCPU/10 GB Disk/3072 MB RAM)"
+msgstr "m1.medium (2 仮想CPU/10 GB ディスク/3072 MB メモリ)"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml89(para)
+msgid "m1.large (4 VCPU/10 GB Disk/8192 MB RAM)"
+msgstr "m1.large (4 仮想CPU/10 GB ディスク/8192 MB メモリ)"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml92(para)
+msgid "m1.xlarge (8 VCPU/10 GB Disk/8192 MB RAM)"
+msgstr "m1.xlarge (8 仮想CPU/10 GB ディスク/8192 MB メモリ)"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml95(para)
+msgid ""
+"You can create and manage flavors with the nova <placeholder-1/> commands "
+"provided by the <filename>python-novaclient</filename> package."
+msgstr "<filename>python-novaclient</filename> パッケージにより提供される nova <placeholder-1/> コマンドを用いて、フレーバーを作成、管理できます。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml99(title)
+msgid "Create a flavor"
+msgstr "フレーバーの作成"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml102(para)
+msgid ""
+"List flavors to show the ID and name, the amount of memory, the amount of "
+"disk space for the root partition and for the ephemeral partition, the swap,"
+" and the number of virtual CPUs for each flavor."
+msgstr "各フレーバーの ID、名前、メモリ容量、ルートパーティション、一時パーティションのディスク容量、swap 容量、仮想 CPU 数を表示するために、フレーバーを一覧表示します。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml111(para)
+msgid ""
+"To create a flavor, specify a name, ID, RAM size, disk size, and the number "
+"of VCPUs for the flavor, as follows:"
+msgstr "フレーバーを作成するために、以下のとおり、フレーバーの名前、ID、メモリ容量、ディスク容量、仮想 CPU 数を指定します。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml114(replaceable)
+msgid "FLAVOR_NAME"
+msgstr "FLAVOR_NAME"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml114(replaceable)
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml153(replaceable)
+msgid "FLAVOR_ID"
+msgstr "FLAVOR_ID"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml114(replaceable)
+msgid "RAM_IN_MB ROOT_DISK_IN_GB"
+msgstr "RAM_IN_MB ROOT_DISK_IN_GB"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml114(replaceable)
+msgid "NUMBER_OF_VCPUS"
+msgstr "NUMBER_OF_VCPUS"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml116(para)
+msgid ""
+"The flavor ID is a number from 1 to 255 and cannot contain special "
+"characters or spaces."
+msgstr "フレーバー ID は 1 ～ 255 の数値です。特殊文字や空白は含められません。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml120(para)
+msgid ""
+"Here is an example with additional optional parameters filled in that "
+"creates a public \"extra tiny\" flavor that automatically gets an ID "
+"assigned, with 256 MB memory, no disk space, and one VCPU. The rxtx-factor "
+"indicates the slice of bandwidth that the instances with this flavor can use"
+" (through the Virtual Interface (vif) creation in the hypervisor)."
+msgstr "これは、割り当て ID を自動取得し、256MB メモリ、ディスクなし、1 仮想 CPU を持つ、パブリックな「extra tiny」フレーバーを作成するために、追加のオプションパラメーターを用いた例です。rxtx-factor は、このフレーバーのインスタンスが (ハイパーバイザーでの仮想インターフェースの作成により) 使用できる帯域幅を意味します。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml129(para)
+msgid ""
+"If an individual user or group of users needs a custom flavor that you do "
+"not want other tenants to have access to, you can change the flavor's access"
+" to make it a private flavor. See <link "
+"href=\"http://docs.openstack.org/trunk/openstack-ops/content/private-"
+"flavors.html\"> Private Flavors in the OpenStack Operations Guide </link>."
+msgstr "個々のユーザーやユーザーのグループが、他のプロジェクトがアクセス権を持たないカスタムフレーバーを必要とする場合、フレーバーをプライベートフレーバーにするために、アクセス権を変更できます。<link href=\"http://docs.openstack.org/trunk/openstack-ops/content/private-flavors.html\"> Private Flavors in the OpenStack Operations Guide </link> を参照してください。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml136(para)
+msgid "For a list of optional parameters, run this command:"
+msgstr "オプションパラメーターの一覧は、このコマンドを実行します。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml141(para)
+msgid ""
+"After you create a flavor, assign it to a project by specifying the flavor "
+"name or ID and the tenant ID:"
+msgstr "フレーバーの作成後、フレーバー名かフレーバー ID およびプロジェクト ID を指定することにより、フレーバーをプロジェクトに割り当てます。"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml144(replaceable)
+msgid "FLAVOR"
+msgstr "FLAVOR"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml149(title)
+msgid "Delete a flavor"
+msgstr "フレーバーの削除"
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml152(para)
+msgid "Delete a specified flavor, as follows:"
+msgstr "以下のように、指定したフレーバーを削除します。"
 
 #. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
-#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml0(None)
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml0(None)
 msgid "translator-credits"
 msgstr "Tomoyuki KATO <tomo@dream.daynight.jp>, 2013-2014"
diff --git a/doc/user-guide-admin/locale/user-guide-admin.pot b/doc/user-guide-admin/locale/user-guide-admin.pot
index 5b888b5e2f..4c1e8ddf44 100644
--- a/doc/user-guide-admin/locale/user-guide-admin.pot
+++ b/doc/user-guide-admin/locale/user-guide-admin.pot
@@ -1,7 +1,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2014-05-24 06:11+0000\n"
+"POT-Creation-Date: 2014-06-03 06:11+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -9,344 +9,910 @@ msgstr ""
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:8(title)
-msgid "Create and manage roles"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:7(title)
+msgid "Create and manage images"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:9(para)
-msgid "A role is a personality that a user assumes to perform a specific set of operations. A role includes a set of rights and privileges. A user assuming that role inherits those rights and privileges."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:8(para)
+msgid "As an administrative user, you can create and manage images for the projects to which you belong. You can also create and manage images for users in all projects to which you have access."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:13(para)
-msgid "OpenStack Identity service defines a user's role on a project but it is completely up to the individual service to define what that role means. This is referred to as the service's policy. To get details about what the privileges for each role are, refer to the <filename>policy.json</filename> file available for each service in the <filename>/etc/<replaceable>SERVICE</replaceable>/policy.json</filename> file. For example, the policy defined for OpenStack Identity service is defined in the <filename>/etc/keystone/policy.json</filename> file."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:12(para)
+msgid "To create and manage images in specified projects as an end user, see the <link href=\"http://docs.openstack.org/user-guide/content/\"><citetitle>OpenStack End User Guide</citetitle></link>."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:24(title)
-msgid "Create a role"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:17(para)
+msgid "To create and manage images as an administrator for other users, use the following procedures."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:27(para) ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:51(para) ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:79(para) ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:24(para) ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:51(para) ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:86(para) ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:26(para) ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:65(para) ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:109(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:66(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:225(para)
-msgid "Log in to the dashboard and choose the <guilabel>admin</guilabel> project from the <guilabel>CURRENT PROJECT</guilabel> drop-down list."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:20(title)
+msgid "Create images"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:32(para) ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:56(para) ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:84(para)
-msgid "On the <guilabel>Admin</guilabel> tab, click the <guilabel>Roles </guilabel> category."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:21(para)
+msgid "For details about image creation, see the <link href=\"http://docs.openstack.org/image-guide/content/\"><citetitle>Virtual Machine Image Guide</citetitle></link>."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:37(para)
-msgid "Click the <guibutton>Create Role</guibutton> button."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:27(para) ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:104(para) ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:134(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:125(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:250(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:278(para) ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:20(para) ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:108(para)
+msgid "Log in to the dashboard."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:38(para)
-msgid "In the <guilabel>Create Role</guilabel> window, enter a name for the role."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:28(para) ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:105(para) ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:135(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:126(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:251(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:279(para) ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:21(para) ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:109(para)
+msgid "Choose the <guilabel>admin</guilabel> project from the <guilabel>CURRENT PROJECT</guilabel> drop-down list."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:42(para)
-msgid "Click the <guibutton>Create Role</guibutton> button to confirm your changes."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:33(para)
+msgid "On the <guilabel>Admin</guilabel> tab, click the <guilabel>Images</guilabel> category. The images that you can administer for cloud users appear on this page."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:48(title)
-msgid "Edit a role"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:38(para) ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:94(para)
+msgid "Click <guibutton>Create Image</guibutton>."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:61(para)
-msgid "Click the <guibutton>Edit</guibutton> button."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:41(para)
+msgid "In the <guilabel>Create An Image</guilabel> window, enter or select the following values:"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:62(para)
-msgid "In the <guilabel>Update Role</guilabel> window, enter a new name for the role."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:66(para)
-msgid "Click the <guibutton>Update Role</guibutton> button to confirm your changes."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:72(para)
-msgid "Using the dashboard, you can edit only the name assigned to a role."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:76(title)
-msgid "Delete a role"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:88(para)
-msgid "Select the role you want to delete and click the <guibutton>Delete Roles</guibutton> button."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:4(title) ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:5(title)
-msgid "Launch and manage stacks"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:5(para) ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:6(para)
-msgid "The Orchestration service provides a template-based orchestration engine for the OpenStack cloud, which can be used to create and manage cloud infrastructure resources such as storage, networking, instances, and applications as a repeatable running environment."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:10(para) ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:11(para)
-msgid "Templates are used to create stacks, which are collections of resources. For example, a stack might include instances, floating IPs, volumes, security groups, or users. The Orchestration service offers access to all OpenStack core services via a single modular template, with additional orchestration capabilities such as auto-scaling and basic high availability."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:14(para)
-msgid "For information about:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:19(para)
-msgid "There are no administration-specific tasks that can be done through the dashboard."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:18(para)
-msgid "Administrative tasks on the command line, see <xref linkend=\"section_cli_admin_manage_stacks\"/>. <placeholder-1/>"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:22(para)
-msgid "The basic creation and deletion of Orchestration stacks, refer to the <link href=\"http://docs.openstack.org/user-guide/content/dashboard_stacks.html\">End User Guide</link>."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:7(title)
-msgid "Manage volumes and volume types"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:8(para)
-msgid "Volumes are the Block Storage devices that you attach to instances to enable persistent storage. Users can attach a volume to a running instance or detach a volume and attach it to another instance at any time. For information about using the dashboard to create and manage volumes as an end user, see the <link href=\"http://docs.openstack.org/user-guide/content/\"><citetitle>OpenStack End User Guide</citetitle></link>."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:17(para)
-msgid "As an administrative user, you can manage volumes and volume types for users in various projects. You can create and delete volume types, and you can view and delete volumes."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:21(title)
-msgid "Create a volume type"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:30(para) ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:57(para) ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:92(para)
-msgid "On the <guilabel>Admin</guilabel> tab, click the <guilabel>Volumes</guilabel> category."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:34(para)
-msgid "Click <guibutton>Create Volume Type</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:36(para)
-msgid "In the <guilabel>Create Volume Type</guilabel> window, enter a name for the volume type."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:40(para)
-msgid "Click <guibutton>Create Volume Type</guibutton> to confirm your changes."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:46(title)
-msgid "Delete volume types"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:47(para)
-msgid "When you delete a volume type, volumes of that type are not deleted."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:61(para)
-msgid "Select the volume type or types that you want to delete."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:65(para)
-msgid "Click <guibutton>Delete Volume Types</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:69(para)
-msgid "In the <guilabel>Confirm Delete Volume Types</guilabel> window, click <guibutton>Delete Volume Types</guibutton> to confirm the action."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:75(para) ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:110(para)
-msgid "A message indicates whether the action succeeded."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:81(title)
-msgid "Delete volumes"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:82(para)
-msgid "When you delete an instance, the data of its attached volumes is not destroyed."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:96(para)
-msgid "Select the volume or volumes that you want to delete."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:100(para)
-msgid "Click <guibutton>Delete Volumes</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:104(para)
-msgid "In the <guilabel>Confirm Delete Volumes</guilabel> window, click <guibutton>Delete Volumes</guibutton> to confirm the action."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:7(title) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:7(title)
-msgid "Manage flavors"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:8(para)
-msgid "In OpenStack, flavors define the compute, memory, and storage capacity of nova computing instances. To put it simply, a flavor is an available hardware configuration for a server. It defines the <quote>size</quote> of a virtual server that can be launched."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:14(para)
-msgid "Flavors can also determine on which compute host a flavor can be used to launch an instance. For information about customizing flavors, refer to the <link href=\"http://docs.openstack.org/admin-guide-cloud/content/\"><citetitle>OpenStack Cloud Administrator Guide</citetitle></link>."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:19(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:14(para)
-msgid "A flavor consists of the following parameters:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:22(term)
-msgid "Flavor ID"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:24(para)
-msgid "Automatically generated by OpenStack. For private flavors, a value from 1 to 255."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:29(term) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:43(para) ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:45(guilabel) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:154(guilabel) ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:48(guilabel)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:48(guilabel) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:154(guilabel) ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:45(guilabel) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:43(para) ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:29(term)
 msgid "Name"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:31(para)
-msgid "Name for the new flavor."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:49(para)
+msgid "Enter a name for the image."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:35(term) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:36(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:172(guilabel) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:135(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:52(guilabel) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:22(th) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:49(para)
+msgid "Description"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:53(para)
+msgid "Enter a brief description about the image."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:57(guilabel)
+msgid "Image Source"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:58(para)
+msgid "Choose the image source from the dropdown list. Your choices are <guilabel>Image Location</guilabel> and <guilabel>Image File</guilabel>."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:63(para)
+msgid "<guilabel>Image File</guilabel> or <guilabel>Image Location</guilabel>"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:66(para)
+msgid "Based on your selection, there is an <guilabel>Image File </guilabel> or <guilabel>Image Location</guilabel> field. You can include the location URL or browse for the image file on your file system and add it."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:72(guilabel)
+msgid "Format"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:73(para)
+msgid "Select the image format."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:76(para)
+msgid "<guilabel>Minimum Disk (GB)</guilabel> and <guilabel>Minimum RAM (MB)</guilabel>"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:78(para)
+msgid "Leave these fields empty."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:82(guilabel) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:95(para)
+msgid "Public"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:83(para)
+msgid "Select this option to make the image public to all users."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:86(guilabel)
+msgid "Protected"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:87(para)
+msgid "Select this option to ensure that only users with permissions can delete it."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:95(para)
+msgid "The image is queued to be uploaded. It might take some time before the status changes from queued to active."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:101(title)
+msgid "Update images"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:110(para) ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:140(para)
+msgid "On the <guilabel>Admin</guilabel> tab, click the <guilabel>Images</guilabel> category."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:114(para)
+msgid "Select the image that you want to edit. Click <guilabel>Edit</guilabel>."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:118(para)
+msgid "In the <guilabel>Update Image</guilabel> window, you can change the name for the image. Select the <guilabel>Public</guilabel> check box to make the image public. Clear this check box to make the image private. You cannot change the kernel ID, RAM disk ID, or architecture attributes for an image."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:126(para)
+msgid "Click <guibutton>Update Image</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:131(title)
+msgid "Delete images"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:144(para)
+msgid "Select the images that you want to delete."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:147(para)
+msgid "Click <guibutton>Delete Images</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:150(para)
+msgid "In the <guilabel>Confirm Delete Image</guilabel> window, click <guibutton>Delete Images</guibutton> to confirm the deletion."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:153(para)
+msgid "You cannot undo this action."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:7(title) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:7(title)
+msgid "Manage project security"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:8(para)
+msgid "Security groups are sets of IP filter rules that are applied to all project instances, which define networking access to the instance. Group rules are project specific; project members can edit the default rules for their group and add new rule sets."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:13(para)
+msgid "All projects have a \"default\" security group which is applied to any instance that has no other defined security group. Unless you change the default, this security group denies all incoming traffic and allows only outgoing traffic to your instance."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:19(para)
+msgid "For information about updating rules using the dashboard, see <xref linkend=\"dashboard_manage_projects_security\"/>."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:23(para)
+msgid "You can use the <code>allow_same_net_traffic</code> option in the <filename>/etc/nova/nova.conf</filename> file to globally control whether the rules apply to hosts which share a network."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:27(para)
+msgid "If set to:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:30(para)
+msgid "<code>True</code> (default), hosts on the same subnet are not filtered and are allowed to pass all types of traffic between them. On a flat network, this allows all instances from all projects unfiltered communication. With VLAN networking, this allows access between instances within the same project. You can also simulate this setting by configuring the default security group to allow all traffic from the subnet."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:41(para)
+msgid "<code>False</code>, security groups are enforced for all connections."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:45(para)
+msgid "Additionally, the number of maximum rules per security group is controlled by the <code>security_group_rules</code> and the number of allowed security groups per project is controlled by the <code>security_groups</code> quota (see <xref linkend=\"cli_set_quotas\"/>)."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:51(title)
+msgid "List and view current security groups"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:52(para)
+msgid "From the command line you can get a list of security groups for the project, using the nova command:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:56(para)
+msgid "Ensure your system variables are set for the user and tenant for which you are checking security group rules for. For example:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:63(para)
+msgid "Output security groups, as follows:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:73(para)
+msgid "View the details of a group, as follows:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:74(replaceable)
+msgid "groupName"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:75(para) ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:111(para) ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:174(para) ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:195(para) ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:68(para) ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:103(para) ./doc/user-guide-admin/section_cli_cinder_quotas.xml:80(para) ./doc/user-guide-admin/section_cli_cinder_quotas.xml:100(para) ./doc/user-guide-admin/section_cli_nova_specify_host.xml:16(para)
+msgid "For example:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:84(para)
+msgid "These rules are allow type rules as the default is deny. The first column is the IP protocol (one of icmp, tcp, or udp). The second and third columns specify the affected port range. The third column specifies the IP range in CIDR format. This example shows the full port range for all protocols allowed from all IPs."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:94(title) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:23(title)
+msgid "Create a security group"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:95(para)
+msgid "When adding a new security group, you should pick a descriptive but brief name. This name shows up in brief descriptions of the instances that use it where the longer description field often does not. For example, seeing that an instance is using security group \"http\" is much easier to understand than \"bobs_group\" or \"secgrp1\"."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:102(para)
+msgid "Ensure your system variables are set for the user and tenant for which you are checking security group rules for."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:107(para)
+msgid "Add the new security group, as follows:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:109(replaceable)
+msgid "Group Name Description"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:122(para)
+msgid "Add a new group rule, as follows:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:124(replaceable)
+msgid "secGroupName ip-protocol from-port to-port CIDR"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:126(para)
+msgid "The arguments are positional, and the \"from-port\" and \"to-port\" arguments specify the local port range connections are allowed to access, not the source and destination ports of the connection. For example:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:139(para)
+msgid "You can create complex rule sets by creating additional rules. For example, if you want to pass both http and https traffic, run:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:148(para)
+msgid "Despite only outputting the newly added rule, this operation is additive (both rules are created and enforced)."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:153(para)
+msgid "View all rules for the new security group, as follows:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:165(title) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:265(title)
+msgid "Delete a security group"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:167(para)
+msgid "Ensure your system variables are set for the user and tenant for which you are deleting a security group for."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:172(para)
+msgid "Delete the new security group, as follows:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:173(replaceable)
+msgid "GroupName"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:179(title)
+msgid "Create security group rules for a cluster of instances"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:181(para)
+msgid "Source Groups are a special, dynamic way of defining the CIDR of allowed sources. The user specifies a Source Group (Security Group name), and all the users' other Instances using the specified Source Group are selected dynamically. This alleviates the need for individual rules to allow each new member of the cluster."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:188(para)
+msgid "Make sure to set the system variables for the user and tenant for which you are deleting a security group for."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:193(para)
+msgid "Add a source group, as follows:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:194(replaceable)
+msgid "secGroupName source-group ip-protocol from-port to-port"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:197(para)
+msgid "The <code>cluster</code> rule allows ssh access from any other instance that uses the <code>global_http</code> group."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:7(title)
+msgid "Analyze log files"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:8(para)
+msgid "Use the swift command-line client to analyze log files."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:9(para)
+msgid "The swift client is simple to use, scalable, and flexible."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:9(para)
+msgid "Use the swift client <option>-o</option> or <option>-output</option> option to get short answers to questions about logs,"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:12(para)
+msgid "You can use the <option>-o —output</option> option with a single object download to redirect the command output to a specific file or to STDOUT (<literal>-</literal>). The ability to redirect the output to STDOUT enables you to pipe (<literal>|</literal>) data without saving it to disk first."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:18(title)
+msgid "Upload and analyze log files"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:20(para)
+msgid "This example assumes that <filename>logtest</filename> directory contains the following log files:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:23(title)
+msgid "Example files"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:27(para)
+msgid "Each file uses the following line format:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:28(title)
+msgid "Log line format"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:31(para)
+msgid "Change into the <filename class=\"directory\">logtest</filename> directory:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:35(para)
+msgid "Upload the log files into the <filename>logtest</filename> container:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:42(para)
+msgid "Get statistics for the account:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:48(para)
+msgid "Get statistics for the logtest container:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:56(para)
+msgid "List all objects in the logtest container:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:62(title)
+msgid "Download and analyze an object"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:64(para)
+msgid "This example uses the <option>-o —output</option> option and a hyphen (<literal>-</literal>) to get information about an object."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:67(para)
+msgid "Use the swift <placeholder-1/> command to download the object. On this command, stream the output to <placeholder-2/> to break down requests by return code and the date <literal>2200 on November 16th, 2010</literal>."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:72(para)
+msgid "Using the log line format, find the request type in column 9 and the return code in column 12."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:74(para)
+msgid "After <placeholder-1/> processes the output, it pipes it to <placeholder-2/> and <placeholder-3/> to sum up the number of occurrences for each request type and return code combination."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:80(para)
+msgid "Download an object:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:113(para)
+msgid "Discover how many PUT requests are in each log file."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:114(para)
+msgid "Use a bash for loop with awk and swift with the <option>-o —output</option> option and a hyphen (<literal>-</literal>) to discover how many PUT requests are in each log file."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:119(para)
+msgid "Run the swift <placeholder-1/> command to list objects in the logtest container. Then, for each item in the list, run the swift <placeholder-2/> command. Pipe the output into grep to filter the PUT requests. Finally, pipe into <placeholder-3/> to count the lines."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:134(para)
+msgid "List the object names that begin with a specified string."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:136(para)
+msgid "Run the swift <placeholder-1/> command to list objects in the logtest container that begin with the <literal>2010-11-15</literal> string."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:140(para)
+msgid "For each item in the list, run the swift <placeholder-1/> command."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:142(para)
+msgid "Pipe the output to <placeholder-1/> and <placeholder-2/>. Use the <placeholder-3/> command to display the object name."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:7(title) ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:7(title)
+msgid "Manage flavors"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:8(para)
+msgid "In OpenStack, a flavor defines the compute, memory, and storage capacity of a virtual server that users can launch. As an administrative user, you can create, edit, and delete flavors."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:12(para)
+msgid "Only administrative users can create and manage flavors."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:14(para) ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:19(para)
+msgid "A flavor consists of the following parameters:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:16(caption)
+msgid "Flavor parameters"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:21(th)
+msgid "Parameter"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:28(para)
+msgid "Flavor Name"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:31(para)
+msgid "The flavor name."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:36(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:172(guilabel) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:135(para) ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:35(term)
 msgid "VCPUs"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:37(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:39(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:39(para) ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:37(para)
 msgid "Number of virtual CPUs to use."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:41(term)
-msgid "Memory MB"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:44(para)
+msgid "RAM"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:43(para)
-msgid "Amount of RAM to use (in megabytes)."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:47(para)
+msgid "Amount of RAM to use, in megabytes."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:47(term) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:190(guilabel)
-msgid "Root Disk GB"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:52(para)
+msgid "Root Disk"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:49(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:55(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:55(para) ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:49(para)
 msgid "Amount of disk space (in gigabytes) to use for the root (/) partition."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:54(term) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:200(guilabel)
-msgid "Ephemeral Disk GB"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:61(para)
+msgid "Ephemeral Disk"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:56(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:64(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:64(para) ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:56(para)
 msgid "Amount of disk space (in gigabytes) to use for the ephemeral partition. If unspecified, the value is 0 by default."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:59(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:67(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:208(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:67(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:208(para) ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:59(para)
 msgid "Ephemeral disks offer machine local disk storage linked to the life cycle of a VM instance. When a VM is terminated, all data on the ephemeral disk is lost. Ephemeral disks are not included in any snapshots."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:67(term)
-msgid "Swap"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:76(para)
+msgid "Swap Disk"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:69(para)
-msgid "Amount of swap space (in megabytes) to use. If unspecified, the value is 0 by default."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:79(para)
+msgid "Amount of swap space (in megabytes) to use. If unspecified, the default is 0."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:74(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:103(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:85(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:163(guilabel)
+msgid "ID"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:88(para)
+msgid "The flavor ID is generated by OpenStack if the option selected is <guilabel>auto</guilabel>."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:90(para)
+msgid "By default, this field is set to <guilabel>auto</guilabel>."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:98(para)
+msgid "Indicates if the flavor is public."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:103(para) ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:74(para)
 msgid "The default flavors are:"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:77(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:106(para)
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:106(para) ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:77(para)
 msgid "m1.tiny (1 VCPU/0 GB Disk/512 MB RAM)"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:80(para)
-msgid "m1.smaller (1 VCPU/0 GB Disk/1024 MB RAM)"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:109(para)
+msgid "m1.small (1 VCPU/20 GB Disk/2048 MB RAM)"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:83(para)
-msgid "m1.small (1 VCPU/10 GB Disk/2048 MB RAM)"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:112(para)
+msgid "m1.medium (2 VCPU/40 GB Disk/4096 MB RAM)"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:86(para)
-msgid "m1.medium (2 VCPU/10 GB Disk/3072 MB RAM)"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:115(para)
+msgid "m1.large (4 VCPU/80 GB Disk/8192 MB RAM)"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:89(para)
-msgid "m1.large (4 VCPU/10 GB Disk/8192 MB RAM)"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:118(para)
+msgid "m1.xlarge (8 VCPU/160 GB Disk/16384 MB RAM)"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:92(para)
-msgid "m1.xlarge (8 VCPU/10 GB Disk/8192 MB RAM)"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:122(title)
+msgid "Create flavors"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:95(para)
-msgid "You can create and manage flavors with the nova <placeholder-1/> commands provided by the <filename>python-novaclient</filename> package."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:131(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:256(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:284(para)
+msgid "On the <guilabel>Admin</guilabel> tab, click the <guilabel>Flavors</guilabel> category."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:99(title)
-msgid "Create a flavor"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:135(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:241(para)
+msgid "Click <guibutton>Create Flavor</guibutton>."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:102(para)
-msgid "List flavors to show the ID and name, the amount of memory, the amount of disk space for the root partition and for the ephemeral partition, the swap, and the number of virtual CPUs for each flavor."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:139(para)
+msgid "In the <guilabel>Create Flavor</guilabel> window, enter or select the following values:"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:111(para)
-msgid "To create a flavor, specify a name, ID, RAM size, disk size, and the number of VCPUs for the flavor, as follows:"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:148(guilabel)
+msgid "Flavor Info"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:114(replaceable)
-msgid "FLAVOR_NAME"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:147(th) ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:39(th) ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:82(th)
+msgid "<placeholder-1/> tab"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:114(replaceable) ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:153(replaceable)
-msgid "FLAVOR_ID"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:157(para)
+msgid "Enter the flavor name."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:114(replaceable)
-msgid "RAM_IN_MB ROOT_DISK_IN_GB"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:167(para)
+msgid "The flavor ID, generated by OpenStack."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:114(replaceable)
-msgid "NUMBER_OF_VCPUS"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:175(para)
+msgid "Enter the number of virtual CPUs to use."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:116(para)
-msgid "The flavor ID is a number from 1 to 255 and cannot contain special characters or spaces."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:181(guilabel)
+msgid "RAM MB"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:120(para)
-msgid "Here is an example with additional optional parameters filled in that creates a public \"extra tiny\" flavor that automatically gets an ID assigned, with 256 MB memory, no disk space, and one VCPU. The rxtx-factor indicates the slice of bandwidth that the instances with this flavor can use (through the Virtual Interface (vif) creation in the hypervisor)."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:184(para)
+msgid "Enter the amount of RAM to use, in megabytes."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:129(para)
-msgid "If an individual user or group of users needs a custom flavor that you do not want other tenants to have access to, you can change the flavor's access to make it a private flavor. See <link href=\"http://docs.openstack.org/trunk/openstack-ops/content/private-flavors.html\"> Private Flavors in the OpenStack Operations Guide </link>."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:190(guilabel) ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:47(term)
+msgid "Root Disk GB"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:136(para)
-msgid "For a list of optional parameters, run this command:"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:193(para)
+msgid "Enter the mount of disk space in gigabytes to use for the root (/) partition."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:141(para)
-msgid "After you create a flavor, assign it to a project by specifying the flavor name or ID and the tenant ID:"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:200(guilabel) ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:54(term)
+msgid "Ephemeral Disk GB"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:144(replaceable)
-msgid "FLAVOR"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:203(para)
+msgid "Enter the amount of disk space in gigabytes to use for the ephemeral partition. If unspecified, the value is 0 by default."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:144(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:346(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:350(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:370(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:375(replaceable)
-msgid "TENANT_ID"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:219(guilabel)
+msgid "Swap Disk MB"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:149(title)
-msgid "Delete a flavor"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:222(para)
+msgid "Enter the amount of swap space (in megabytes) to use. If unspecified, the default is 0."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:152(para)
-msgid "Delete a specified flavor, as follows:"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:232(para)
+msgid "In the <guilabel>Flavor Access</guilabel> tab, you can control access to the flavor by moving projects from the <guilabel>All Projects</guilabel> column to the <guilabel>Selected Projects</guilabel> column."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:236(para)
+msgid "Only projects in the <guilabel>Selected Projects</guilabel> column can use the flavor. If there are no projects in the right column, all projects can use the flavor."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:247(title)
+msgid "Update flavors"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:260(para)
+msgid "Select the flavor that you want to edit. Click <guibutton>Edit Flavor</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:264(para)
+msgid "In the <guilabel>Edit Flavor</guilabel> window, you can change the flavor name, VCPUs, RAM, root dish, ephemeral disk, and swap disk values.."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:270(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:132(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:197(para)
+msgid "Click <guibutton>Save</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:275(title)
+msgid "Delete flavors"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:288(para)
+msgid "Select the flavors that you want to delete."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:292(para)
+msgid "Click <guibutton>Delete Flavors</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:296(para)
+msgid "In the <guilabel>Confirm Delete Flavors</guilabel> window, click <guibutton>Delete Flavors</guibutton> to confirm the deletion. You cannot undo this action."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:11(title)
+msgid "View and manage quotas"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:12(para) ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:12(para)
+msgid "To prevent system capacities from being exhausted without notification, you can set up quotas. Quotas are operational limits. For example, the number of gigabytes allowed for each tenant can be controlled so that cloud resources are optimized. Quotas can be enforced at both the tenant (or project) and the tenant-user level."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:17(para)
+msgid "Typically, you change quotas when a project needs more than ten volumes or 1TB on a compute node."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:19(para)
+msgid "Using the Dashboard, you can view default Compute and Block Storage quotas for new tenants, as well as update quotas for existing tenants."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:22(para)
+msgid "Using the command-line interface, you can manage quotas for the OpenStack Compute service, the OpenStack Block Storage service, and the OpenStack Networking service (see <xref linkend=\"cli_set_quotas\"/>). Additionally, you can update Compute service quotas for tenant users."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:28(para)
+msgid "The following table describes the Compute and Block Storage service quotas:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:31(caption)
+msgid "Quota Descriptions"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:37(th)
+msgid "Quota Name"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:38(th) ./doc/user-guide-admin/section_cli_cinder_quotas.xml:18(th)
+msgid "Defines the number of"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:39(th)
+msgid "Service"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:45(para)
+msgid "Gigabytes"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:48(para)
+msgid "Volume gigabytes allowed for each project."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:50(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:131(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:149(td)
+msgid "Block Storage"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:54(para)
+msgid "Instances"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:57(para)
+msgid "Instances allowed for each project."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:59(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:68(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:77(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:86(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:95(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:104(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:113(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:122(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:140(td)
+msgid "Compute"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:63(para)
+msgid "Injected Files"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:66(para)
+msgid "Injected files allowed for each project."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:72(para)
+msgid "Injected File Content Bytes"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:75(para)
+msgid "Content bytes allowed for each injected file."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:81(para)
+msgid "Keypairs"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:84(para)
+msgid "Number of keypairs."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:90(para)
+msgid "Metadata Items"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:93(para)
+msgid "Metadata items allowed for each instance."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:99(para)
+msgid "RAM (MB)"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:102(para)
+msgid "RAM megabytes allowed for each instance."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:108(para)
+msgid "Security Groups"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:111(para)
+msgid "Security groups allowed for each project."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:117(para)
+msgid "Security Group Rules"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:120(para)
+msgid "Rules allowed for each security group."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:126(para)
+msgid "Snapshots"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:129(para)
+msgid "Volume snapshots allowed for each project."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:138(para)
+msgid "Instance cores allowed for each project."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:144(para)
+msgid "Volumes"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:147(para)
+msgid "Volumes allowed for each project."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:154(title)
+msgid "View default project quotas"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:157(para) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:175(para)
+msgid "Log in to the OpenStack dashboard."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:160(para) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:178(para)
+msgid "On the <guilabel>Admin</guilabel> tab, click the <guilabel>Defaults</guilabel> category."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:164(para)
+msgid "The default quota values are displayed."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:168(para)
+msgid "You can sort the table by clicking on either the <guilabel>Quota Name</guilabel> or <guilabel>Limit</guilabel> column headers."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:172(title)
+msgid "Update project quotas"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:182(para) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:188(para)
+msgid "Click the <guibutton>Update Defaults</guibutton> button."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:185(para)
+msgid "In the <guilabel>Update Default Quotas</guilabel> window, you can edit the default quota values."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:192(para)
+msgid "The dashboard does not show all possible project quotas. To view and update the quotas for a service, use its command-line client. See <xref linkend=\"cli_set_quotas\"/>."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_resources.xml:7(title)
+msgid "View cloud resources"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_manage_services.xml:7(title)
+msgid "Manage services"
+msgstr ""
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:93(None)
+msgid "@@image: '../common/figures/change_instance_state.png'; md5=d9eef0f7a1f99eee18a99e677c7c710b"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:11(title)
+msgid "Manage instances"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:12(para)
+msgid "As an administrative user, you can manage instances for users in various projects. You can view, terminate, edit, perform a soft or hard reboot, create a snapshot from, and migrate instances. You can also view the logs for instances or launch a VNC console for an instance."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:17(para)
+msgid "For information about using the dashboard to launch instances as an end user, see the <link href=\"http://docs.openstack.org/user-guide/content/\"><citetitle>OpenStack End User Guide</citetitle></link>."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:23(title)
+msgid "Create instance snapshots"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:26(para) ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:65(para) ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:109(para) ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:27(para) ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:51(para) ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:79(para) ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:24(para) ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:51(para) ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:86(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:66(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:225(para)
+msgid "Log in to the dashboard and choose the <guilabel>admin</guilabel> project from the <guilabel>CURRENT PROJECT</guilabel> drop-down list."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:32(para) ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:71(para) ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:115(para)
+msgid "On the <guilabel>Admin</guilabel> tab, click the <guilabel>Instances</guilabel> category."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:37(para)
+msgid "Select an instance to create a snapshot from it. From the <guilabel>Actions</guilabel> drop-down list, select <guilabel>Create Snapshot</guilabel>."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:43(para)
+msgid "In the <guilabel>Create Snapshot</guilabel> window, enter a name for the snapshot. Click <guibutton>Create Snapshot</guibutton>. The dashboard shows the instance snapshot in the <guilabel>Images &amp; Snapshots</guilabel> category."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:51(para)
+msgid "To launch an instance from the snapshot, select the snapshot and click <guibutton>Launch</guibutton>. For information about launching instances, see the <link href=\"http://docs.openstack.org/user-guide/content/\"><citetitle>OpenStack End User Guide</citetitle></link>."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:62(title)
+msgid "Control the state of an instance"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:76(para)
+msgid "Select the instance for which you want to change the state."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:80(para)
+msgid "In the <guilabel>More</guilabel> drop-down list in the <guilabel>Actions</guilabel> column, select the state."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:83(para)
+msgid "Depending on the current state of the instance, you can choose to pause, un-pause, suspend, resume, soft or hard reboot, or terminate an instance (items in red are disabled)."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:88(title)
+msgid "DashboardInstance Actions"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:101(title)
+msgid "Track usage"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:102(para)
+msgid "Use the <guilabel>Overview</guilabel> category to track usage of instances for each project."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:104(para)
+msgid "You can track costs per month by showing metrics like number of VCPUs, disks, RAM, and uptime of all your instances."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:120(para)
+msgid "Select a month and click <guibutton>Submit</guibutton> to query the instance usage for that month."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:125(para)
+msgid "Click <guibutton>Download CSV Summary</guibutton> to download a CSV summary."
 msgstr ""
 
 #: ./doc/user-guide-admin/bk-admin-user-guide.xml:9(title)
@@ -413,6 +979,350 @@ msgstr ""
 msgid "First edition of this document."
 msgstr ""
 
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:8(para)
+msgid "Security groups are sets of IP filter rules that define networking access and are applied to all project instances. Group rules are project specific; project members can edit the default rules for their group and add new rule sets."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:12(para)
+msgid "All projects have a default security group that is applied to any instance that has no other defined security group. Unless you change the default, this security group denies all incoming traffic and allows only outgoing traffic to your instance."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:18(para)
+msgid "For information about updating global controls on the command line, see <xref linkend=\"nova_cli_manage_projects_security\"/>."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:26(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:54(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:243(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:268(para)
+msgid "Log in to the dashboard as a project member."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:30(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:58(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:247(para)
+msgid "On the <guilabel>Project</guilabel> tab, select the appropriate project from the <guimenu>CURRENT PROJECT</guimenu> drop-down list, and click the <guimenuitem>Access &amp; Security</guimenuitem> category."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:37(para)
+msgid "On the <guilabel>Security Groups</guilabel> tab, click <guibutton>Create Security Group</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:42(para)
+msgid "Provide a name and appropriate description for the group, and click <guibutton>Create Security Group</guibutton>. By default, the new rule provides outgoing access rules for the group."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:51(title)
+msgid "Add a security group rule"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:65(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:254(para)
+msgid "On the <guilabel>Security Groups</guilabel> tab, click <guibutton>Edit rules</guibutton> for the appropriate security group."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:70(para)
+msgid "To add a rule, click <guibutton>Add Rule</guibutton>. Set the attributes for the rule, and click <guibutton>Add</guibutton>:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:113(guilabel)
+msgid "IP Protocol"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:115(para)
+msgid "The IP protocol to which the rule applies:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:119(para)
+msgid "<guilabel>TCP</guilabel>.Typically used to exchange data between systems, and for end-user communication."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:125(para)
+msgid "<guilabel>UDP</guilabel>. Typically used to exchange data between systems, particularly at the application level."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:131(para)
+msgid "<guilabel>ICMP</guilabel>. Typically used by network devices, such as routers, to send error or monitoring messages."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:153(guilabel)
+msgid "Open"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:155(para)
+msgid "For TCP or UDP rules, the <guilabel>Port</guilabel> or <guilabel>Port Range</guilabel> to open for the rule. Choose to open a single port or range of ports."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:160(para)
+msgid "For a range of ports, enter port values in the <guilabel>From Port</guilabel> and <guilabel>To Port</guilabel> fields."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:164(para)
+msgid "For a single port, enter the port value in the <guilabel>Port</guilabel> field."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:201(guilabel)
+msgid "Source"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:203(para)
+msgid "The source of the traffic for this rule:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:207(para)
+msgid "<guilabel>CIDR</guilabel> (Classless Inter-Domain Routing). IP address block, which limits access to IPs within the block. Enter the CIDR in the <guilabel>Source</guilabel> field."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:216(para)
+msgid "<guilabel>Security Group</guilabel>. Source group that enables any instance in the group to access any other group instance."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:240(title)
+msgid "Delete a security group rule"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:259(para)
+msgid "To delete a rule, select the rule and click <guibutton>Delete Rule</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:272(para)
+msgid "On the <guilabel>Project</guilabel> tab, select the appropriate project from the <guilabel>CURRENT PROJECT</guilabel> drop-down list, and click the <guilabel>Access &amp; Security</guilabel> category."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:279(para)
+msgid "On the <guilabel>Security Groups</guilabel> tab, select the appropriate group, and click <guibutton>Delete Security Group</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:7(title)
+msgid "Create and manage host aggregates"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:8(para)
+msgid "Host aggregates enable administrative users to assign key-value pairs to groups of machines."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:10(para)
+msgid "Each node can have multiple aggregates and each aggregate can have multiple key-value pairs. You can assign the same key-value pair to multiple aggregates."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:13(para)
+msgid "The scheduler uses this information to make scheduling decisions. For information, see <link href=\"http://docs.openstack.org/trunk/config-reference/content/section_compute-scheduler.html\"><citetitle>Scheduling</citetitle></link>."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:18(title)
+msgid "To create a host aggregate"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:25(para)
+msgid "On the <guilabel>Admin</guilabel> tab, click the <guilabel>Host Aggregates</guilabel> category."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:29(para)
+msgid "Click <guibutton>Create Host Aggregate</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:32(para)
+msgid "In the <guilabel>Create Host Aggregate</guilabel> window, enter or select the following values:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:40(guilabel)
+msgid "Host Aggregate Info"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:47(para)
+msgid "The host aggregate name."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:51(guilabel)
+msgid "Availability Zone"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:53(para)
+msgid "The cloud provider defines the default availability zone, such as <literal>us-west</literal>, <literal>apac-south</literal>, or <literal>nova</literal>."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:58(para)
+msgid "You can target the host aggregate, as follows:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:62(para)
+msgid "When the host aggregate is exposed as an availability zone, select the availability zone when you launch an instance."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:67(para)
+msgid "When the host aggregate is not exposed as an availability zone, select a flavor and its extra specs to target the host aggregate."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:83(guilabel)
+msgid "Host within Aggregate"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:88(guilabel)
+msgid "Selected hosts"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:90(para)
+msgid "To assign a host to the aggregate, click <guilabel>+</guilabel> for the host. The host moves from the <guilabel>All available hosts</guilabel> list to the <guilabel>Selected hosts</guilabel> list."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:96(para)
+msgid "You can add one host to one or more aggregates. To add a host later, edit the aggregate."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:106(title)
+msgid "To manage host and aggregates"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:113(para)
+msgid "On the <guilabel>Admin</guilabel> tab, click the <guilabel> Host Aggregates</guilabel> category."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:117(para)
+msgid "To edit host aggregates:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:120(para)
+msgid "Select the host aggregate that you want to edit. Click <guibutton>Edit Host Aggregate</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:124(para)
+msgid "In the <guilabel>Edit Host Aggregate</guilabel> window, you can change the name and availability zone for the aggregate."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:131(para)
+msgid "To manage hosts:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:134(para) ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:151(para)
+msgid "Select the host aggregate that you want to edit. Click <guibutton>More</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:138(para)
+msgid "In the <guilabel>Add/Remove Hosts to Aggregate</guilabel> window, click <guilabel>+</guilabel> to assign a host to the aggregate."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:142(para)
+msgid "Click <guilabel>-</guilabel> to remove a host that is assigned to an aggregate."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:148(para)
+msgid "To delete host aggregates:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:155(para)
+msgid "Click the <guilabel>Delete Host Aggregate</guilabel> option."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:6(title)
+msgid "View services information"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:7(para)
+msgid "As an administrative user, you can view information for OpenStack services."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:11(para)
+msgid "Log in to the OpenStack dashboard and choose the <guilabel>admin</guilabel> project from the <guilabel>CURRENT PROJECT</guilabel> drop-down list."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:16(para)
+msgid "On the <guilabel>Admin</guilabel> tab, click the <guilabel>System Info</guilabel> category."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:22(para)
+msgid "<guilabel>Services</guilabel> tab to view services information."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:23(para)
+msgid "The page displays the internal name and the public OpenStack name for the service, the host where the service runs, and whether the service is or is not enabled."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:27(para)
+msgid "<guilabel>Compute Services</guilabel> tab to view services specific to the Compute Service. Both host and zone are listed for each service, as well as its activation status."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:20(para)
+msgid "Click the:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:36(guilabel)
+msgid "Availability Zones"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:39(guilabel)
+msgid "Host Aggregates"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:42(guilabel)
+msgid "Network Agents"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:34(para)
+msgid "The <guilabel>System Info</guilabel> window also offers status information for the following: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/user-guide-admin/ch_dashboard.xml:10(title)
+msgid "Dashboard"
+msgstr ""
+
+#: ./doc/user-guide-admin/ch_dashboard.xml:12(para)
+msgid "As a cloud administrative user, the OpenStack dashboard lets you create and manage projects, users, images, and flavors. You can also set quotas and create and manage services. For information about using the dashboard to perform end user tasks, see the <link href=\"http://docs.openstack.org/user-guide/content/\"><citetitle>OpenStack End User Guide</citetitle></link>."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:8(title)
+msgid "Create and manage roles"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:9(para)
+msgid "A role is a personality that a user assumes to perform a specific set of operations. A role includes a set of rights and privileges. A user assuming that role inherits those rights and privileges."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:13(para)
+msgid "OpenStack Identity service defines a user's role on a project but it is completely up to the individual service to define what that role means. This is referred to as the service's policy. To get details about what the privileges for each role are, refer to the <filename>policy.json</filename> file available for each service in the <filename>/etc/<replaceable>SERVICE</replaceable>/policy.json</filename> file. For example, the policy defined for OpenStack Identity service is defined in the <filename>/etc/keystone/policy.json</filename> file."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:24(title)
+msgid "Create a role"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:32(para) ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:56(para) ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:84(para)
+msgid "On the <guilabel>Admin</guilabel> tab, click the <guilabel>Roles </guilabel> category."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:37(para)
+msgid "Click the <guibutton>Create Role</guibutton> button."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:38(para)
+msgid "In the <guilabel>Create Role</guilabel> window, enter a name for the role."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:42(para)
+msgid "Click the <guibutton>Create Role</guibutton> button to confirm your changes."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:48(title)
+msgid "Edit a role"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:61(para)
+msgid "Click the <guibutton>Edit</guibutton> button."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:62(para)
+msgid "In the <guilabel>Update Role</guilabel> window, enter a new name for the role."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:66(para)
+msgid "Click the <guibutton>Update Role</guibutton> button to confirm your changes."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:72(para)
+msgid "Using the dashboard, you can edit only the name assigned to a role."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:76(title)
+msgid "Delete a role"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_roles.xml:88(para)
+msgid "Select the role you want to delete and click the <guibutton>Delete Roles</guibutton> button."
+msgstr ""
+
 #: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:6(title)
 msgid "Manage IP addresses"
 msgstr ""
@@ -461,10 +1371,6 @@ msgstr ""
 msgid "RANGE_TO_CREATE"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:68(para) ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:103(para) ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:75(para) ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:111(para) ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:174(para) ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:195(para) ./doc/user-guide-admin/section_cli_cinder_quotas.xml:80(para) ./doc/user-guide-admin/section_cli_cinder_quotas.xml:100(para) ./doc/user-guide-admin/section_cli_nova_specify_host.xml:16(para)
-msgid "For example:"
-msgstr ""
-
 #: ./doc/user-guide-admin/section_cli_nova_floating_ips.xml:70(para)
 msgid "By default, <placeholder-1/> uses the <systemitem>public</systemitem> pool and <systemitem>eth0</systemitem> interface values."
 msgstr ""
@@ -545,10 +1451,6 @@ msgstr ""
 msgid "Type"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:49(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:22(th) ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:52(guilabel)
-msgid "Description"
-msgstr ""
-
 #: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:52(para) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:66(para) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:77(para) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:88(para)
 msgid "Example:"
 msgstr ""
@@ -745,6 +1647,10 @@ msgstr ""
 msgid "ROLE_ID"
 msgstr ""
 
+#: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:346(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:350(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:370(replaceable) ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:375(replaceable) ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:144(replaceable)
+msgid "TENANT_ID"
+msgstr ""
+
 #: ./doc/user-guide-admin/section_cli_keystone_manage_projects_users_roles.xml:349(para)
 msgid "To verify the role assignment:"
 msgstr ""
@@ -765,218 +1671,280 @@ msgstr ""
 msgid "If the role was removed, the command output omits the removed role."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_resources.xml:7(title)
-msgid "View cloud resources"
+#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:11(title)
+msgid "Manage quotas"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:7(title)
-msgid "Create and manage host aggregates"
+#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:18(para)
+msgid "Using the command-line interface, you can manage quotas for the OpenStack Compute service, the OpenStack Block Storage service, and the OpenStack Networking service."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:8(para)
-msgid "Host aggregates enable administrative users to assign key-value pairs to groups of machines."
+#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:21(para)
+msgid "The cloud operator typically changes default values because a tenant requires more than ten volumes or 1TB on a compute node."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:10(para)
-msgid "Each node can have multiple aggregates and each aggregate can have multiple key-value pairs. You can assign the same key-value pair to multiple aggregates."
+#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:26(para)
+msgid "To view all tenants (projects), run: <placeholder-1/>"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:13(para)
-msgid "The scheduler uses this information to make scheduling decisions. For information, see <link href=\"http://docs.openstack.org/trunk/config-reference/content/section_compute-scheduler.html\"><citetitle>Scheduling</citetitle></link>."
+#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:37(para)
+msgid "To display all current users for a tenant, run:"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:18(title)
-msgid "To create a host aggregate"
+#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:39(replaceable) ./doc/user-guide-admin/section_cli_cinder_quotas.xml:99(replaceable) ./doc/user-guide-admin/section_cli_cinder_quotas.xml:114(replaceable)
+msgid "tenantID"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:20(para) ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:108(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:125(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:250(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:278(para) ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:27(para) ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:104(para) ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:134(para)
-msgid "Log in to the dashboard."
+#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:5(title) ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:4(title)
+msgid "Launch and manage stacks"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:21(para) ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:109(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:126(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:251(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:279(para) ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:28(para) ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:105(para) ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:135(para)
-msgid "Choose the <guilabel>admin</guilabel> project from the <guilabel>CURRENT PROJECT</guilabel> drop-down list."
+#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:6(para) ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:5(para)
+msgid "The Orchestration service provides a template-based orchestration engine for the OpenStack cloud, which can be used to create and manage cloud infrastructure resources such as storage, networking, instances, and applications as a repeatable running environment."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:25(para)
-msgid "On the <guilabel>Admin</guilabel> tab, click the <guilabel>Host Aggregates</guilabel> category."
+#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:11(para) ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:10(para)
+msgid "Templates are used to create stacks, which are collections of resources. For example, a stack might include instances, floating IPs, volumes, security groups, or users. The Orchestration service offers access to all OpenStack core services via a single modular template, with additional orchestration capabilities such as auto-scaling and basic high availability."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:29(para)
-msgid "Click <guibutton>Create Host Aggregate</guibutton>."
+#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:15(para)
+msgid "For information about the:"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:32(para)
-msgid "In the <guilabel>Create Host Aggregate</guilabel> window, enter or select the following values:"
+#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:19(para)
+msgid "Basic creation and deletion of Orchestration stacks, refer to the <link href=\"http://docs.openstack.org/user-guide/content/dashboard_stacks.html\">End User Guide</link>."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:40(guilabel)
-msgid "Host Aggregate Info"
+#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:23(para)
+msgid "<systemitem>heat</systemitem> CLI commands, see the <link href=\"http://docs.openstack.org/cli-reference/content/\"><citetitle> OpenStack Command Line Interface Reference</citetitle></link>"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:39(th) ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:82(th) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:147(th)
-msgid "<placeholder-1/> tab"
+#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:30(para)
+msgid "As an administrator, you can also carry out stack functions on behalf of your users. For example, to resume, suspend, or delete a stack, run:"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:47(para)
-msgid "The host aggregate name."
+#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:32(replaceable) ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:33(replaceable) ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:34(replaceable)
+msgid "stackID"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:51(guilabel)
-msgid "Availability Zone"
+#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:6(title)
+msgid "View cloud usage statistics"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:53(para)
-msgid "The cloud provider defines the default availability zone, such as <literal>us-west</literal>, <literal>apac-south</literal>, or <literal>nova</literal>."
+#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:7(para)
+msgid "The Telemetry module provides user-level usage data for OpenStack-based clouds, which can be used for customer billing, system monitoring, or alerts. Data can be collected by notifications sent by existing OpenStack components (for example, usage events emitted from Compute) or by polling the infrastructure (for example, libvirt)."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:58(para)
-msgid "You can target the host aggregate, as follows:"
+#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:13(para)
+msgid "You can only view metering statistics on the dashboard (available only to administrators). The Telemetry service must be set up and administered through the <placeholder-1/> command-line interface (CLI)."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:62(para)
-msgid "When the host aggregate is exposed as an availability zone, select the availability zone when you launch an instance."
+#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:17(para)
+msgid "For basic administration information, refer to the \"Measure Cloud Resources\" chapter in the <citetitle>OpenStack End User Guide</citetitle>."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:67(para)
-msgid "When the host aggregate is not exposed as an availability zone, select a flavor and its extra specs to target the host aggregate."
+#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:20(title)
+msgid "View resource statistics"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:83(guilabel)
-msgid "Host within Aggregate"
+#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:23(para)
+msgid "Log in to the OpenStack dashboard as a user with Admin privileges."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:88(guilabel)
-msgid "Selected hosts"
+#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:25(para)
+msgid "On the <guilabel>Admin</guilabel> tab, click the <guilabel>Resource Usage</guilabel> category."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:90(para)
-msgid "To assign a host to the aggregate, click <guilabel>+</guilabel> for the host. The host moves from the <guilabel>All available hosts</guilabel> list to the <guilabel>Selected hosts</guilabel> list."
+#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:31(para)
+msgid "<guilabel>Global Disk Usage</guilabel> tab to view disk usage per tenant (project)."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:96(para)
-msgid "You can add one host to one or more aggregates. To add a host later, edit the aggregate."
+#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:32(para)
+msgid "<guilabel>Global Network Traffic Usage</guilabel> tab to view ingress or egress usage per tenant (project)."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:106(title)
-msgid "To manage host and aggregates"
+#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:34(para)
+msgid "<guilabel>Global Object Storage Usage</guilabel> tab to view incoming and outgoing storage bytes per tenant (project)."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:113(para)
-msgid "On the <guilabel>Admin</guilabel> tab, click the <guilabel> Host Aggregates</guilabel> category."
+#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:35(para)
+msgid "<guilabel>Global Network Usage</guilabel> tab to view duration and creation requests for networks, subnets, routers, ports, and floating IPs, per tenant (project)."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:117(para)
-msgid "To edit host aggregates:"
+#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:38(para)
+msgid "<guilabel>Stats</guilabel> tab to view a multi-series line chart with user-defined metrics. You group by project, define the value type (min, max, avg, or sum), and specify the time period (or even use a calendar to define a date range)."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:120(para)
-msgid "Select the host aggregate that you want to edit. Click <guibutton>Edit Host Aggregate</guibutton>."
+#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:29(para)
+msgid "Click the: <placeholder-1/>"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:124(para)
-msgid "In the <guilabel>Edit Host Aggregate</guilabel> window, you can change the name and availability zone for the aggregate."
+#: ./doc/user-guide-admin/ch_cli.xml:10(title)
+msgid "OpenStack command-line clients"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:131(para)
-msgid "To manage hosts:"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:7(title)
+msgid "Manage volumes and volume types"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:134(para) ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:151(para)
-msgid "Select the host aggregate that you want to edit. Click <guibutton>More</guibutton>."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:8(para)
+msgid "Volumes are the Block Storage devices that you attach to instances to enable persistent storage. Users can attach a volume to a running instance or detach a volume and attach it to another instance at any time. For information about using the dashboard to create and manage volumes as an end user, see the <link href=\"http://docs.openstack.org/user-guide/content/\"><citetitle>OpenStack End User Guide</citetitle></link>."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:138(para)
-msgid "In the <guilabel>Add/Remove Hosts to Aggregate</guilabel> window, click <guilabel>+</guilabel> to assign a host to the aggregate."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:17(para)
+msgid "As an administrative user, you can manage volumes and volume types for users in various projects. You can create and delete volume types, and you can view and delete volumes."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:142(para)
-msgid "Click <guilabel>-</guilabel> to remove a host that is assigned to an aggregate."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:21(title)
+msgid "Create a volume type"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:148(para)
-msgid "To delete host aggregates:"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:30(para) ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:57(para) ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:92(para)
+msgid "On the <guilabel>Admin</guilabel> tab, click the <guilabel>Volumes</guilabel> category."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_host_aggregates.xml:155(para)
-msgid "Click the <guilabel>Delete Host Aggregate</guilabel> option."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:34(para)
+msgid "Click <guibutton>Create Volume Type</guibutton>."
 msgstr ""
 
-#. When image changes, this message will be marked fuzzy or untranslated for you.
-#. It doesn't matter what you translate it to: it's not used at all.
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:93(None)
-msgid "@@image: '../common/figures/change_instance_state.png'; md5=d9eef0f7a1f99eee18a99e677c7c710b"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:36(para)
+msgid "In the <guilabel>Create Volume Type</guilabel> window, enter a name for the volume type."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:11(title)
-msgid "Manage instances"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:40(para)
+msgid "Click <guibutton>Create Volume Type</guibutton> to confirm your changes."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:12(para)
-msgid "As an administrative user, you can manage instances for users in various projects. You can view, terminate, edit, perform a soft or hard reboot, create a snapshot from, and migrate instances. You can also view the logs for instances or launch a VNC console for an instance."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:46(title)
+msgid "Delete volume types"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:17(para)
-msgid "For information about using the dashboard to launch instances as an end user, see the <link href=\"http://docs.openstack.org/user-guide/content/\"><citetitle>OpenStack End User Guide</citetitle></link>."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:47(para)
+msgid "When you delete a volume type, volumes of that type are not deleted."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:23(title)
-msgid "Create instance snapshots"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:61(para)
+msgid "Select the volume type or types that you want to delete."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:32(para) ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:71(para) ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:115(para)
-msgid "On the <guilabel>Admin</guilabel> tab, click the <guilabel>Instances</guilabel> category."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:65(para)
+msgid "Click <guibutton>Delete Volume Types</guibutton>."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:37(para)
-msgid "Select an instance to create a snapshot from it. From the <guilabel>Actions</guilabel> drop-down list, select <guilabel>Create Snapshot</guilabel>."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:69(para)
+msgid "In the <guilabel>Confirm Delete Volume Types</guilabel> window, click <guibutton>Delete Volume Types</guibutton> to confirm the action."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:43(para)
-msgid "In the <guilabel>Create Snapshot</guilabel> window, enter a name for the snapshot. Click <guibutton>Create Snapshot</guibutton>. The dashboard shows the instance snapshot in the <guilabel>Images &amp; Snapshots</guilabel> category."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:75(para) ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:110(para)
+msgid "A message indicates whether the action succeeded."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:51(para)
-msgid "To launch an instance from the snapshot, select the snapshot and click <guibutton>Launch</guibutton>. For information about launching instances, see the <link href=\"http://docs.openstack.org/user-guide/content/\"><citetitle>OpenStack End User Guide</citetitle></link>."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:81(title)
+msgid "Delete volumes"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:62(title)
-msgid "Control the state of an instance"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:82(para)
+msgid "When you delete an instance, the data of its attached volumes is not destroyed."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:76(para)
-msgid "Select the instance for which you want to change the state."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:96(para)
+msgid "Select the volume or volumes that you want to delete."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:80(para)
-msgid "In the <guilabel>More</guilabel> drop-down list in the <guilabel>Actions</guilabel> column, select the state."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:100(para)
+msgid "Click <guibutton>Delete Volumes</guibutton>."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:83(para)
-msgid "Depending on the current state of the instance, you can choose to pause, un-pause, suspend, resume, soft or hard reboot, or terminate an instance (items in red are disabled)."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_volumes.xml:104(para)
+msgid "In the <guilabel>Confirm Delete Volumes</guilabel> window, click <guibutton>Delete Volumes</guibutton> to confirm the action."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:88(title)
-msgid "DashboardInstance Actions"
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:6(title)
+msgid "Manage Block Storage service quotas"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:101(title)
-msgid "Track usage"
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:7(para)
+msgid "As an administrative user, you can update the OpenStack Block Storage service quotas for a project. You can also update the quota defaults for a new project."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:102(para)
-msgid "Use the <guilabel>Overview</guilabel> category to track usage of instances for each project."
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:12(caption)
+msgid "Block Storage quotas"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:104(para)
-msgid "You can track costs per month by showing metrics like number of VCPUs, disks, RAM, and uptime of all your instances."
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:17(th)
+msgid "Property name"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:120(para)
-msgid "Select a month and click <guibutton>Submit</guibutton> to query the instance usage for that month."
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:24(para)
+msgid "gigabytes"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_instances.xml:125(para)
-msgid "Click <guibutton>Download CSV Summary</guibutton> to download a CSV summary."
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:27(para)
+msgid "Volume gigabytes allowed for each tenant."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:33(para)
+msgid "snapshots"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:36(para)
+msgid "Volume snapshots allowed for each tenant."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:42(para)
+msgid "volumes"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:45(para)
+msgid "Volumes allowed for each tenant."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:52(title)
+msgid "View and update Block Storage service quotas"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:53(para)
+msgid "As an administrative user, you can view and update Block Storage service quotas."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:57(para)
+msgid "List the default quotas for all projects, as follows:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:69(para)
+msgid "To update a default value for a new project, update the property in the <filename>/etc/cinder/cinder.conf</filename> file."
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:77(para)
+msgid "View Block Storage service quotas for a project, as follows:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:79(replaceable)
+msgid "TENANT_NAME"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:91(para)
+msgid "To update Block Storage service quotas, place the tenant ID in a usable variable, as follows:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:94(replaceable)
+msgid "tenantName"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:97(para)
+msgid "Update a particular quota value, as follows:"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:99(replaceable)
+msgid "quotaName"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:99(replaceable)
+msgid "NewValue"
+msgstr ""
+
+#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:112(para)
+msgid "To clear per-tenant quota limits, use the <placeholder-1/> command:"
 msgstr ""
 
 #: ./doc/user-guide-admin/section_cli_nova_services.xml:6(title)
@@ -1003,440 +1971,24 @@ msgstr ""
 msgid "Enable the service:"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:7(title) ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:7(title)
-msgid "Manage project security"
+#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml:6(title)
+msgid "Select hosts where instances are launched"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:8(para)
-msgid "Security groups are sets of IP filter rules that define networking access and are applied to all project instances. Group rules are project specific; project members can edit the default rules for their group and add new rule sets."
+#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml:7(para)
+msgid "With the appropriate permissions, you can select which host instances are launched on and which roles can boot instances on this host."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:12(para)
-msgid "All projects have a default security group that is applied to any instance that has no other defined security group. Unless you change the default, this security group denies all incoming traffic and allows only outgoing traffic to your instance."
+#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml:12(para)
+msgid "To select the host where instances are launched, use the <literal>--availability_zone <replaceable>zone</replaceable>:<replaceable>host</replaceable></literal> parameter on the <placeholder-1/> command,"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:18(para)
-msgid "For information about updating global controls on the command line, see <xref linkend=\"nova_cli_manage_projects_security\"/>."
+#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml:20(para)
+msgid "To specify which roles can launch an instance on a specified host, enable the <literal>create:forced_host</literal> option in the <filename>policy.json</filename> file. By default, this option is enabled for only the admin role."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:23(title) ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:94(title)
-msgid "Create a security group"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:26(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:54(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:243(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:268(para)
-msgid "Log in to the dashboard as a project member."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:30(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:58(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:247(para)
-msgid "On the <guilabel>Project</guilabel> tab, select the appropriate project from the <guimenu>CURRENT PROJECT</guimenu> drop-down list, and click the <guimenuitem>Access &amp; Security</guimenuitem> category."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:37(para)
-msgid "On the <guilabel>Security Groups</guilabel> tab, click <guibutton>Create Security Group</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:42(para)
-msgid "Provide a name and appropriate description for the group, and click <guibutton>Create Security Group</guibutton>. By default, the new rule provides outgoing access rules for the group."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:51(title)
-msgid "Add a security group rule"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:65(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:254(para)
-msgid "On the <guilabel>Security Groups</guilabel> tab, click <guibutton>Edit rules</guibutton> for the appropriate security group."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:70(para)
-msgid "To add a rule, click <guibutton>Add Rule</guibutton>. Set the attributes for the rule, and click <guibutton>Add</guibutton>:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:113(guilabel)
-msgid "IP Protocol"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:115(para)
-msgid "The IP protocol to which the rule applies:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:119(para)
-msgid "<guilabel>TCP</guilabel>.Typically used to exchange data between systems, and for end-user communication."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:125(para)
-msgid "<guilabel>UDP</guilabel>. Typically used to exchange data between systems, particularly at the application level."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:131(para)
-msgid "<guilabel>ICMP</guilabel>. Typically used by network devices, such as routers, to send error or monitoring messages."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:153(guilabel)
-msgid "Open"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:155(para)
-msgid "For TCP or UDP rules, the <guilabel>Port</guilabel> or <guilabel>Port Range</guilabel> to open for the rule. Choose to open a single port or range of ports."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:160(para)
-msgid "For a range of ports, enter port values in the <guilabel>From Port</guilabel> and <guilabel>To Port</guilabel> fields."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:164(para)
-msgid "For a single port, enter the port value in the <guilabel>Port</guilabel> field."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:201(guilabel)
-msgid "Source"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:203(para)
-msgid "The source of the traffic for this rule:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:207(para)
-msgid "<guilabel>CIDR</guilabel> (Classless Inter-Domain Routing). IP address block, which limits access to IPs within the block. Enter the CIDR in the <guilabel>Source</guilabel> field."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:216(para)
-msgid "<guilabel>Security Group</guilabel>. Source group that enables any instance in the group to access any other group instance."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:240(title)
-msgid "Delete a security group rule"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:259(para)
-msgid "To delete a rule, select the rule and click <guibutton>Delete Rule</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:265(title) ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:165(title)
-msgid "Delete a security group"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:272(para)
-msgid "On the <guilabel>Project</guilabel> tab, select the appropriate project from the <guilabel>CURRENT PROJECT</guilabel> drop-down list, and click the <guilabel>Access &amp; Security</guilabel> category."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_projects_security.xml:279(para)
-msgid "On the <guilabel>Security Groups</guilabel> tab, select the appropriate group, and click <guibutton>Delete Security Group</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:8(para)
-msgid "In OpenStack, a flavor defines the compute, memory, and storage capacity of a virtual server that users can launch. As an administrative user, you can create, edit, and delete flavors."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:12(para)
-msgid "Only administrative users can create and manage flavors."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:16(caption)
-msgid "Flavor parameters"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:21(th)
-msgid "Parameter"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:28(para)
-msgid "Flavor Name"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:31(para)
-msgid "The flavor name."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:44(para)
-msgid "RAM"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:47(para)
-msgid "Amount of RAM to use, in megabytes."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:52(para)
-msgid "Root Disk"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:61(para)
-msgid "Ephemeral Disk"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:76(para)
-msgid "Swap Disk"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:79(para)
-msgid "Amount of swap space (in megabytes) to use. If unspecified, the default is 0."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:85(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:163(guilabel)
-msgid "ID"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:88(para)
-msgid "The flavor ID is generated by OpenStack if the option selected is <guilabel>auto</guilabel>."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:90(para)
-msgid "By default, this field is set to <guilabel>auto</guilabel>."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:95(para) ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:82(guilabel)
-msgid "Public"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:98(para)
-msgid "Indicates if the flavor is public."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:109(para)
-msgid "m1.small (1 VCPU/20 GB Disk/2048 MB RAM)"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:112(para)
-msgid "m1.medium (2 VCPU/40 GB Disk/4096 MB RAM)"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:115(para)
-msgid "m1.large (4 VCPU/80 GB Disk/8192 MB RAM)"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:118(para)
-msgid "m1.xlarge (8 VCPU/160 GB Disk/16384 MB RAM)"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:122(title)
-msgid "Create flavors"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:131(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:256(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:284(para)
-msgid "On the <guilabel>Admin</guilabel> tab, click the <guilabel>Flavors</guilabel> category."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:135(para) ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:241(para)
-msgid "Click <guibutton>Create Flavor</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:139(para)
-msgid "In the <guilabel>Create Flavor</guilabel> window, enter or select the following values:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:148(guilabel)
-msgid "Flavor Info"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:157(para)
-msgid "Enter the flavor name."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:167(para)
-msgid "The flavor ID, generated by OpenStack."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:175(para)
-msgid "Enter the number of virtual CPUs to use."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:181(guilabel)
-msgid "RAM MB"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:184(para)
-msgid "Enter the amount of RAM to use, in megabytes."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:193(para)
-msgid "Enter the mount of disk space in gigabytes to use for the root (/) partition."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:203(para)
-msgid "Enter the amount of disk space in gigabytes to use for the ephemeral partition. If unspecified, the value is 0 by default."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:219(guilabel)
-msgid "Swap Disk MB"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:222(para)
-msgid "Enter the amount of swap space (in megabytes) to use. If unspecified, the default is 0."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:232(para)
-msgid "In the <guilabel>Flavor Access</guilabel> tab, you can control access to the flavor by moving projects from the <guilabel>All Projects</guilabel> column to the <guilabel>Selected Projects</guilabel> column."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:236(para)
-msgid "Only projects in the <guilabel>Selected Projects</guilabel> column can use the flavor. If there are no projects in the right column, all projects can use the flavor."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:247(title)
-msgid "Update flavors"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:260(para)
-msgid "Select the flavor that you want to edit. Click <guibutton>Edit Flavor</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:264(para)
-msgid "In the <guilabel>Edit Flavor</guilabel> window, you can change the flavor name, VCPUs, RAM, root dish, ephemeral disk, and swap disk values.."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:270(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:132(para) ./doc/user-guide-admin/section_dashboard_admin_manage_projects_users.xml:197(para)
-msgid "Click <guibutton>Save</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:275(title)
-msgid "Delete flavors"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:288(para)
-msgid "Select the flavors that you want to delete."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:292(para)
-msgid "Click <guibutton>Delete Flavors</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_flavors.xml:296(para)
-msgid "In the <guilabel>Confirm Delete Flavors</guilabel> window, click <guibutton>Delete Flavors</guibutton> to confirm the deletion. You cannot undo this action."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:8(para)
-msgid "Security groups are sets of IP filter rules that are applied to all project instances, which define networking access to the instance. Group rules are project specific; project members can edit the default rules for their group and add new rule sets."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:13(para)
-msgid "All projects have a \"default\" security group which is applied to any instance that has no other defined security group. Unless you change the default, this security group denies all incoming traffic and allows only outgoing traffic to your instance."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:19(para)
-msgid "For information about updating rules using the dashboard, see <xref linkend=\"dashboard_manage_projects_security\"/>."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:23(para)
-msgid "You can use the <code>allow_same_net_traffic</code> option in the <filename>/etc/nova/nova.conf</filename> file to globally control whether the rules apply to hosts which share a network."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:27(para)
-msgid "If set to:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:30(para)
-msgid "<code>True</code> (default), hosts on the same subnet are not filtered and are allowed to pass all types of traffic between them. On a flat network, this allows all instances from all projects unfiltered communication. With VLAN networking, this allows access between instances within the same project. You can also simulate this setting by configuring the default security group to allow all traffic from the subnet."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:41(para)
-msgid "<code>False</code>, security groups are enforced for all connections."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:45(para)
-msgid "Additionally, the number of maximum rules per security group is controlled by the <code>security_group_rules</code> and the number of allowed security groups per project is controlled by the <code>security_groups</code> quota (see <xref linkend=\"cli_set_quotas\"/>)."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:51(title)
-msgid "List and view current security groups"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:52(para)
-msgid "From the command line you can get a list of security groups for the project, using the nova command:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:56(para)
-msgid "Ensure your system variables are set for the user and tenant for which you are checking security group rules for. For example:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:63(para)
-msgid "Output security groups, as follows:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:73(para)
-msgid "View the details of a group, as follows:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:74(replaceable)
-msgid "groupName"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:84(para)
-msgid "These rules are allow type rules as the default is deny. The first column is the IP protocol (one of icmp, tcp, or udp). The second and third columns specify the affected port range. The third column specifies the IP range in CIDR format. This example shows the full port range for all protocols allowed from all IPs."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:95(para)
-msgid "When adding a new security group, you should pick a descriptive but brief name. This name shows up in brief descriptions of the instances that use it where the longer description field often does not. For example, seeing that an instance is using security group \"http\" is much easier to understand than \"bobs_group\" or \"secgrp1\"."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:102(para)
-msgid "Ensure your system variables are set for the user and tenant for which you are checking security group rules for."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:107(para)
-msgid "Add the new security group, as follows:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:109(replaceable)
-msgid "Group Name Description"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:122(para)
-msgid "Add a new group rule, as follows:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:124(replaceable)
-msgid "secGroupName ip-protocol from-port to-port CIDR"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:126(para)
-msgid "The arguments are positional, and the \"from-port\" and \"to-port\" arguments specify the local port range connections are allowed to access, not the source and destination ports of the connection. For example:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:139(para)
-msgid "You can create complex rule sets by creating additional rules. For example, if you want to pass both http and https traffic, run:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:148(para)
-msgid "Despite only outputting the newly added rule, this operation is additive (both rules are created and enforced)."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:153(para)
-msgid "View all rules for the new security group, as follows:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:167(para)
-msgid "Ensure your system variables are set for the user and tenant for which you are deleting a security group for."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:172(para)
-msgid "Delete the new security group, as follows:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:173(replaceable)
-msgid "GroupName"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:179(title)
-msgid "Create security group rules for a cluster of instances"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:181(para)
-msgid "Source Groups are a special, dynamic way of defining the CIDR of allowed sources. The user specifies a Source Group (Security Group name), and all the users' other Instances using the specified Source Group are selected dynamically. This alleviates the need for individual rules to allow each new member of the cluster."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:188(para)
-msgid "Make sure to set the system variables for the user and tenant for which you are deleting a security group for."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:193(para)
-msgid "Add a source group, as follows:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:194(replaceable)
-msgid "secGroupName source-group ip-protocol from-port to-port"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:197(para)
-msgid "The <code>cluster</code> rule allows ssh access from any other instance that uses the <code>global_http</code> group."
+#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml:27(para)
+msgid "To view the list of valid compute hosts, use the <placeholder-1/> command, as follows:"
 msgstr ""
 
 #. When image changes, this message will be marked fuzzy or untranslated for you.
@@ -1681,218 +2233,6 @@ msgstr ""
 msgid "In the <guilabel>Confirm Delete Users</guilabel> window, click <guibutton>Delete Users</guibutton> to confirm the deletion."
 msgstr ""
 
-#: ./doc/user-guide-admin/ch_cli.xml:10(title)
-msgid "OpenStack command-line clients"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:6(title)
-msgid "Manage Block Storage service quotas"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:7(para)
-msgid "As an administrative user, you can update the OpenStack Block Storage service quotas for a project. You can also update the quota defaults for a new project."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:12(caption)
-msgid "Block Storage quotas"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:17(th)
-msgid "Property name"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:18(th) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:38(th)
-msgid "Defines the number of"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:24(para)
-msgid "gigabytes"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:27(para)
-msgid "Volume gigabytes allowed for each tenant."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:33(para)
-msgid "snapshots"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:36(para)
-msgid "Volume snapshots allowed for each tenant."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:42(para)
-msgid "volumes"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:45(para)
-msgid "Volumes allowed for each tenant."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:52(title)
-msgid "View and update Block Storage service quotas"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:53(para)
-msgid "As an administrative user, you can view and update Block Storage service quotas."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:57(para)
-msgid "List the default quotas for all projects, as follows:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:69(para)
-msgid "To update a default value for a new project, update the property in the <filename>/etc/cinder/cinder.conf</filename> file."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:77(para)
-msgid "View Block Storage service quotas for a project, as follows:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:79(replaceable)
-msgid "TENANT_NAME"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:91(para)
-msgid "To update Block Storage service quotas, place the tenant ID in a usable variable, as follows:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:94(replaceable)
-msgid "tenantName"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:97(para)
-msgid "Update a particular quota value, as follows:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:99(replaceable)
-msgid "quotaName"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:99(replaceable)
-msgid "NewValue"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:99(replaceable) ./doc/user-guide-admin/section_cli_cinder_quotas.xml:114(replaceable) ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:39(replaceable)
-msgid "tenantID"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_cinder_quotas.xml:112(para)
-msgid "To clear per-tenant quota limits, use the <placeholder-1/> command:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:7(title)
-msgid "Analyze log files"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:8(para)
-msgid "Use the swift command-line client to analyze log files."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:9(para)
-msgid "The swift client is simple to use, scalable, and flexible."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:9(para)
-msgid "Use the swift client <option>-o</option> or <option>-output</option> option to get short answers to questions about logs,"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:12(para)
-msgid "You can use the <option>-o —output</option> option with a single object download to redirect the command output to a specific file or to STDOUT (<literal>-</literal>). The ability to redirect the output to STDOUT enables you to pipe (<literal>|</literal>) data without saving it to disk first."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:18(title)
-msgid "Upload and analyze log files"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:20(para)
-msgid "This example assumes that <filename>logtest</filename> directory contains the following log files:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:23(title)
-msgid "Example files"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:27(para)
-msgid "Each file uses the following line format:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:28(title)
-msgid "Log line format"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:31(para)
-msgid "Change into the <filename class=\"directory\">logtest</filename> directory:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:35(para)
-msgid "Upload the log files into the <filename>logtest</filename> container:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:42(para)
-msgid "Get statistics for the account:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:48(para)
-msgid "Get statistics for the logtest container:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:56(para)
-msgid "List all objects in the logtest container:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:62(title)
-msgid "Download and analyze an object"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:64(para)
-msgid "This example uses the <option>-o —output</option> option and a hyphen (<literal>-</literal>) to get information about an object."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:67(para)
-msgid "Use the swift <placeholder-1/> command to download the object. On this command, stream the output to <placeholder-2/> to break down requests by return code and the date <literal>2200 on November 16th, 2010</literal>."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:72(para)
-msgid "Using the log line format, find the request type in column 9 and the return code in column 12."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:74(para)
-msgid "After <placeholder-1/> processes the output, it pipes it to <placeholder-2/> and <placeholder-3/> to sum up the number of occurrences for each request type and return code combination."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:80(para)
-msgid "Download an object:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:113(para)
-msgid "Discover how many PUT requests are in each log file."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:114(para)
-msgid "Use a bash for loop with awk and swift with the <option>-o —output</option> option and a hyphen (<literal>-</literal>) to discover how many PUT requests are in each log file."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:119(para)
-msgid "Run the swift <placeholder-1/> command to list objects in the logtest container. Then, for each item in the list, run the swift <placeholder-2/> command. Pipe the output into grep to filter the PUT requests. Finally, pipe into <placeholder-3/> to count the lines."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:134(para)
-msgid "List the object names that begin with a specified string."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:136(para)
-msgid "Run the swift <placeholder-1/> command to list objects in the logtest container that begin with the <literal>2010-11-15</literal> string."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:140(para)
-msgid "For each item in the list, run the swift <placeholder-1/> command."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_swift_analyze_log_files.xml:142(para)
-msgid "Pipe the output to <placeholder-1/> and <placeholder-2/>. Use the <placeholder-3/> command to display the object name."
-msgstr ""
-
 #: ./doc/user-guide-admin/section_cli_admin_manage_environment.xml:4(title)
 msgid "Manage the OpenStack environment"
 msgstr ""
@@ -1901,484 +2241,144 @@ msgstr ""
 msgid "This section includes tasks specific to the OpenStack environment."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_cli_manage_services.xml:7(title)
-msgid "Manage services"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:14(para)
+msgid "For information about:"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:7(title)
-msgid "Create and manage images"
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:19(para)
+msgid "There are no administration-specific tasks that can be done through the dashboard."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:8(para)
-msgid "As an administrative user, you can create and manage images for the projects to which you belong. You can also create and manage images for users in all projects to which you have access."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:18(para)
+msgid "Administrative tasks on the command line, see <xref linkend=\"section_cli_admin_manage_stacks\"/>. <placeholder-1/>"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:12(para)
-msgid "To create and manage images in specified projects as an end user, see the <link href=\"http://docs.openstack.org/user-guide/content/\"><citetitle>OpenStack End User Guide</citetitle></link>."
+#: ./doc/user-guide-admin/section_dashboard_admin_manage_stacks.xml:22(para)
+msgid "The basic creation and deletion of Orchestration stacks, refer to the <link href=\"http://docs.openstack.org/user-guide/content/dashboard_stacks.html\">End User Guide</link>."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:17(para)
-msgid "To create and manage images as an administrator for other users, use the following procedures."
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:8(para)
+msgid "In OpenStack, flavors define the compute, memory, and storage capacity of nova computing instances. To put it simply, a flavor is an available hardware configuration for a server. It defines the <quote>size</quote> of a virtual server that can be launched."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:20(title)
-msgid "Create images"
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:14(para)
+msgid "Flavors can also determine on which compute host a flavor can be used to launch an instance. For information about customizing flavors, refer to the <link href=\"http://docs.openstack.org/admin-guide-cloud/content/\"><citetitle>OpenStack Cloud Administrator Guide</citetitle></link>."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:21(para)
-msgid "For details about image creation, see the <link href=\"http://docs.openstack.org/image-guide/content/\"><citetitle>Virtual Machine Image Guide</citetitle></link>."
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:22(term)
+msgid "Flavor ID"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:33(para)
-msgid "On the <guilabel>Admin</guilabel> tab, click the <guilabel>Images</guilabel> category. The images that you can administer for cloud users appear on this page."
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:24(para)
+msgid "Automatically generated by OpenStack. For private flavors, a value from 1 to 255."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:38(para) ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:94(para)
-msgid "Click <guibutton>Create Image</guibutton>."
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:31(para)
+msgid "Name for the new flavor."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:41(para)
-msgid "In the <guilabel>Create An Image</guilabel> window, enter or select the following values:"
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:41(term)
+msgid "Memory MB"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:49(para)
-msgid "Enter a name for the image."
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:43(para)
+msgid "Amount of RAM to use (in megabytes)."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:53(para)
-msgid "Enter a brief description about the image."
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:67(term)
+msgid "Swap"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:57(guilabel)
-msgid "Image Source"
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:69(para)
+msgid "Amount of swap space (in megabytes) to use. If unspecified, the value is 0 by default."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:58(para)
-msgid "Choose the image source from the dropdown list. Your choices are <guilabel>Image Location</guilabel> and <guilabel>Image File</guilabel>."
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:80(para)
+msgid "m1.smaller (1 VCPU/0 GB Disk/1024 MB RAM)"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:63(para)
-msgid "<guilabel>Image File</guilabel> or <guilabel>Image Location</guilabel>"
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:83(para)
+msgid "m1.small (1 VCPU/10 GB Disk/2048 MB RAM)"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:66(para)
-msgid "Based on your selection, there is an <guilabel>Image File </guilabel> or <guilabel>Image Location</guilabel> field. You can include the location URL or browse for the image file on your file system and add it."
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:86(para)
+msgid "m1.medium (2 VCPU/10 GB Disk/3072 MB RAM)"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:72(guilabel)
-msgid "Format"
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:89(para)
+msgid "m1.large (4 VCPU/10 GB Disk/8192 MB RAM)"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:73(para)
-msgid "Select the image format."
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:92(para)
+msgid "m1.xlarge (8 VCPU/10 GB Disk/8192 MB RAM)"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:76(para)
-msgid "<guilabel>Minimum Disk (GB)</guilabel> and <guilabel>Minimum RAM (MB)</guilabel>"
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:95(para)
+msgid "You can create and manage flavors with the nova <placeholder-1/> commands provided by the <filename>python-novaclient</filename> package."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:78(para)
-msgid "Leave these fields empty."
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:99(title)
+msgid "Create a flavor"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:83(para)
-msgid "Select this option to make the image public to all users."
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:102(para)
+msgid "List flavors to show the ID and name, the amount of memory, the amount of disk space for the root partition and for the ephemeral partition, the swap, and the number of virtual CPUs for each flavor."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:86(guilabel)
-msgid "Protected"
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:111(para)
+msgid "To create a flavor, specify a name, ID, RAM size, disk size, and the number of VCPUs for the flavor, as follows:"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:87(para)
-msgid "Select this option to ensure that only users with permissions can delete it."
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:114(replaceable)
+msgid "FLAVOR_NAME"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:95(para)
-msgid "The image is queued to be uploaded. It might take some time before the status changes from queued to active."
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:114(replaceable) ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:153(replaceable)
+msgid "FLAVOR_ID"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:101(title)
-msgid "Update images"
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:114(replaceable)
+msgid "RAM_IN_MB ROOT_DISK_IN_GB"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:110(para) ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:140(para)
-msgid "On the <guilabel>Admin</guilabel> tab, click the <guilabel>Images</guilabel> category."
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:114(replaceable)
+msgid "NUMBER_OF_VCPUS"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:114(para)
-msgid "Select the image that you want to edit. Click <guilabel>Edit</guilabel>."
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:116(para)
+msgid "The flavor ID is a number from 1 to 255 and cannot contain special characters or spaces."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:118(para)
-msgid "In the <guilabel>Update Image</guilabel> window, you can change the name for the image. Select the <guilabel>Public</guilabel> check box to make the image public. Clear this check box to make the image private. You cannot change the kernel ID, RAM disk ID, or architecture attributes for an image."
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:120(para)
+msgid "Here is an example with additional optional parameters filled in that creates a public \"extra tiny\" flavor that automatically gets an ID assigned, with 256 MB memory, no disk space, and one VCPU. The rxtx-factor indicates the slice of bandwidth that the instances with this flavor can use (through the Virtual Interface (vif) creation in the hypervisor)."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:126(para)
-msgid "Click <guibutton>Update Image</guibutton>."
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:129(para)
+msgid "If an individual user or group of users needs a custom flavor that you do not want other tenants to have access to, you can change the flavor's access to make it a private flavor. See <link href=\"http://docs.openstack.org/trunk/openstack-ops/content/private-flavors.html\"> Private Flavors in the OpenStack Operations Guide </link>."
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:131(title)
-msgid "Delete images"
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:136(para)
+msgid "For a list of optional parameters, run this command:"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:144(para)
-msgid "Select the images that you want to delete."
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:141(para)
+msgid "After you create a flavor, assign it to a project by specifying the flavor name or ID and the tenant ID:"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:147(para)
-msgid "Click <guibutton>Delete Images</guibutton>."
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:144(replaceable)
+msgid "FLAVOR"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:150(para)
-msgid "In the <guilabel>Confirm Delete Image</guilabel> window, click <guibutton>Delete Images</guibutton> to confirm the deletion."
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:149(title)
+msgid "Delete a flavor"
 msgstr ""
 
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_images.xml:153(para)
-msgid "You cannot undo this action."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:11(title)
-msgid "View and manage quotas"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:12(para) ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:12(para)
-msgid "To prevent system capacities from being exhausted without notification, you can set up quotas. Quotas are operational limits. For example, the number of gigabytes allowed for each tenant can be controlled so that cloud resources are optimized. Quotas can be enforced at both the tenant (or project) and the tenant-user level."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:17(para)
-msgid "Typically, you change quotas when a project needs more than ten volumes or 1TB on a compute node."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:19(para)
-msgid "Using the Dashboard, you can view default Compute and Block Storage quotas for new tenants, as well as update quotas for existing tenants."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:22(para)
-msgid "Using the command-line interface, you can manage quotas for the OpenStack Compute service, the OpenStack Block Storage service, and the OpenStack Networking service (see <xref linkend=\"cli_set_quotas\"/>). Additionally, you can update Compute service quotas for tenant users."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:28(para)
-msgid "The following table describes the Compute and Block Storage service quotas:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:31(caption)
-msgid "Quota Descriptions"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:37(th)
-msgid "Quota Name"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:39(th)
-msgid "Service"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:45(para)
-msgid "Gigabytes"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:48(para)
-msgid "Volume gigabytes allowed for each project."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:50(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:131(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:149(td)
-msgid "Block Storage"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:54(para)
-msgid "Instances"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:57(para)
-msgid "Instances allowed for each project."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:59(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:68(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:77(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:86(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:95(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:104(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:113(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:122(td) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:140(td)
-msgid "Compute"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:63(para)
-msgid "Injected Files"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:66(para)
-msgid "Injected files allowed for each project."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:72(para)
-msgid "Injected File Content Bytes"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:75(para)
-msgid "Content bytes allowed for each injected file."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:81(para)
-msgid "Keypairs"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:84(para)
-msgid "Number of keypairs."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:90(para)
-msgid "Metadata Items"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:93(para)
-msgid "Metadata items allowed for each instance."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:99(para)
-msgid "RAM (MB)"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:102(para)
-msgid "RAM megabytes allowed for each instance."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:108(para)
-msgid "Security Groups"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:111(para)
-msgid "Security groups allowed for each project."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:117(para)
-msgid "Security Group Rules"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:120(para)
-msgid "Rules allowed for each security group."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:126(para)
-msgid "Snapshots"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:129(para)
-msgid "Volume snapshots allowed for each project."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:138(para)
-msgid "Instance cores allowed for each project."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:144(para)
-msgid "Volumes"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:147(para)
-msgid "Volumes allowed for each project."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:154(title)
-msgid "View default project quotas"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:157(para) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:175(para)
-msgid "Log in to the OpenStack dashboard."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:160(para) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:178(para)
-msgid "On the <guilabel>Admin</guilabel> tab, click the <guilabel>Defaults</guilabel> category."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:164(para)
-msgid "The default quota values are displayed."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:168(para)
-msgid "You can sort the table by clicking on either the <guilabel>Quota Name</guilabel> or <guilabel>Limit</guilabel> column headers."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:172(title)
-msgid "Update project quotas"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:182(para) ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:188(para)
-msgid "Click the <guibutton>Update Defaults</guibutton> button."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:185(para)
-msgid "In the <guilabel>Update Default Quotas</guilabel> window, you can edit the default quota values."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_set_quotas.xml:192(para)
-msgid "The dashboard does not show all possible project quotas. To view and update the quotas for a service, use its command-line client. See <xref linkend=\"cli_set_quotas\"/>."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:11(title)
-msgid "Manage quotas"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:18(para)
-msgid "Using the command-line interface, you can manage quotas for the OpenStack Compute service, the OpenStack Block Storage service, and the OpenStack Networking service."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:21(para)
-msgid "The cloud operator typically changes default values because a tenant requires more than ten volumes or 1TB on a compute node."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:26(para)
-msgid "To view all tenants (projects), run: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_keystone_set_quotas.xml:37(para)
-msgid "To display all current users for a tenant, run:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:6(title)
-msgid "View cloud usage statistics"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:7(para)
-msgid "The Telemetry module provides user-level usage data for OpenStack-based clouds, which can be used for customer billing, system monitoring, or alerts. Data can be collected by notifications sent by existing OpenStack components (for example, usage events emitted from Compute) or by polling the infrastructure (for example, libvirt)."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:13(para)
-msgid "You can only view metering statistics on the dashboard (available only to administrators). The Telemetry service must be set up and administered through the <placeholder-1/> command-line interface (CLI)."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:17(para)
-msgid "For basic administration information, refer to the \"Measure Cloud Resources\" chapter in the <citetitle>OpenStack End User Guide</citetitle>."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:20(title)
-msgid "View resource statistics"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:23(para)
-msgid "Log in to the OpenStack dashboard as a user with Admin privileges."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:25(para)
-msgid "On the <guilabel>Admin</guilabel> tab, click the <guilabel>Resource Usage</guilabel> category."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:31(para)
-msgid "<guilabel>Global Disk Usage</guilabel> tab to view disk usage per tenant (project)."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:32(para)
-msgid "<guilabel>Global Network Traffic Usage</guilabel> tab to view ingress or egress usage per tenant (project)."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:34(para)
-msgid "<guilabel>Global Object Storage Usage</guilabel> tab to view incoming and outgoing storage bytes per tenant (project)."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:35(para)
-msgid "<guilabel>Global Network Usage</guilabel> tab to view duration and creation requests for networks, subnets, routers, ports, and floating IPs, per tenant (project)."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:38(para)
-msgid "<guilabel>Stats</guilabel> tab to view a multi-series line chart with user-defined metrics. You group by project, define the value type (min, max, avg, or sum), and specify the time period (or even use a calendar to define a date range)."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_view_cloud_resources.xml:29(para)
-msgid "Click the: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:6(title)
-msgid "View services information"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:7(para)
-msgid "As an administrative user, you can view information for OpenStack services."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:11(para)
-msgid "Log in to the OpenStack dashboard and choose the <guilabel>admin</guilabel> project from the <guilabel>CURRENT PROJECT</guilabel> drop-down list."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:16(para)
-msgid "On the <guilabel>Admin</guilabel> tab, click the <guilabel>System Info</guilabel> category."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:22(para)
-msgid "<guilabel>Services</guilabel> tab to view services information."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:23(para)
-msgid "The page displays the internal name and the public OpenStack name for the service, the host where the service runs, and whether the service is or is not enabled."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:27(para)
-msgid "<guilabel>Compute Services</guilabel> tab to view services specific to the Compute Service. Both host and zone are listed for each service, as well as its activation status."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:20(para)
-msgid "Click the:<placeholder-1/>"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:36(guilabel)
-msgid "Availability Zones"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:39(guilabel)
-msgid "Host Aggregates"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:42(guilabel)
-msgid "Network Agents"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_dashboard_admin_manage_services.xml:34(para)
-msgid "The <guilabel>System Info</guilabel> window also offers status information for the following: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml:6(title)
-msgid "Select hosts where instances are launched"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml:7(para)
-msgid "With the appropriate permissions, you can select which host instances are launched on and which roles can boot instances on this host."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml:12(para)
-msgid "To select the host where instances are launched, use the <literal>--availability_zone <replaceable>zone</replaceable>:<replaceable>host</replaceable></literal> parameter on the <placeholder-1/> command,"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml:20(para)
-msgid "To specify which roles can launch an instance on a specified host, enable the <literal>create:forced_host</literal> option in the <filename>policy.json</filename> file. By default, this option is enabled for only the admin role."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_nova_specify_host.xml:27(para)
-msgid "To view the list of valid compute hosts, use the <placeholder-1/> command, as follows:"
-msgstr ""
-
-#: ./doc/user-guide-admin/ch_dashboard.xml:10(title)
-msgid "Dashboard"
-msgstr ""
-
-#: ./doc/user-guide-admin/ch_dashboard.xml:12(para)
-msgid "As a cloud administrative user, the OpenStack dashboard lets you create and manage projects, users, images, and flavors. You can also set quotas and create and manage services. For information about using the dashboard to perform end user tasks, see the <link href=\"http://docs.openstack.org/user-guide/content/\"><citetitle>OpenStack End User Guide</citetitle></link>."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:15(para)
-msgid "For information about the:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:19(para)
-msgid "Basic creation and deletion of Orchestration stacks, refer to the <link href=\"http://docs.openstack.org/user-guide/content/dashboard_stacks.html\">End User Guide</link>."
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:23(para)
-msgid "<systemitem>heat</systemitem> CLI commands, see the <link href=\"http://docs.openstack.org/cli-reference/content/\"><citetitle> OpenStack Command Line Interface Reference</citetitle></link>"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:30(para)
-msgid "As an administrator, you can also carry out stack functions on behalf of your users. For example, to resume, suspend, or delete a stack, run:"
-msgstr ""
-
-#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:32(replaceable) ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:33(replaceable) ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:34(replaceable)
-msgid "stackID"
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:152(para)
+msgid "Delete a specified flavor, as follows:"
 msgstr ""
 
 #. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
-#: ./doc/user-guide-admin/section_cli_admin_manage_stacks.xml:0(None)
+#: ./doc/user-guide-admin/section_cli_nova_manage_flavors.xml:0(None)
 msgid "translator-credits"
 msgstr ""
 
diff --git a/doc/user-guide/locale/ja.po b/doc/user-guide/locale/ja.po
index 92aa893d85..2cae0b9d5c 100644
--- a/doc/user-guide/locale/ja.po
+++ b/doc/user-guide/locale/ja.po
@@ -6,8 +6,8 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: OpenStack Manuals\n"
-"POT-Creation-Date: 2014-06-02 05:42+0000\n"
-"PO-Revision-Date: 2014-06-02 04:01+0000\n"
+"POT-Creation-Date: 2014-06-03 02:30+0000\n"
+"PO-Revision-Date: 2014-06-02 08:41+0000\n"
 "Last-Translator: Tomoyuki KATO <tomo@dream.daynight.jp>\n"
 "Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n"
 "MIME-Version: 1.0\n"
@@ -16,6 +16,164 @@ msgstr ""
 "Language: ja\n"
 "Plural-Forms: nplurals=1; plural=0;\n"
 
+#: ./doc/user-guide/section_cli_heat.xml8(title)
+msgid "Create and manage stacks"
+msgstr "スタックの管理と作成"
+
+#: ./doc/user-guide/section_cli_heat.xml9(para)
+msgid ""
+"The Orchestration module enables you to orchestrate multiple composite cloud"
+" applications. This module supports use of both the Amazon Web Services "
+"(AWS) CloudFormation template format through both a Query API that is "
+"compatible with CloudFormation and the native OpenStack <glossterm>Heat "
+"Orchestration Template (HOT)</glossterm> format through a REST API."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml14(para)
+#: ./doc/user-guide/section_dashboard_stacks.xml16(para)
+msgid ""
+"These flexible template languages enable application developers to describe "
+"and automate the deployment of infrastructure, services, and applications. "
+"The templates enable creation of most OpenStack resource types, such as "
+"instances, floating IP addresses, volumes, security groups, and users. The "
+"resources, once created, are referred to as stacks."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml19(para)
+#: ./doc/user-guide/section_dashboard_stacks.xml23(para)
+msgid ""
+"The template languages are described in <link "
+"href=\"http://docs.openstack.org/developer/heat/template_guide/index.html\">the"
+" Template Guide</link> in the <link "
+"href=\"http://docs.openstack.org/developer/heat/\">Heat developer "
+"documentation</link>."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml25(title)
+msgid "Create a stack from an example template file"
+msgstr "サンプルテンプレートファイルからのスタックの作成"
+
+#: ./doc/user-guide/section_cli_heat.xml28(para)
+msgid ""
+"To create a stack, or template, from an <link "
+"href=\"https://github.com/openstack/heat-templates\">example template "
+"file</link>, run the following command:"
+msgstr "<link href=\"https://github.com/openstack/heat-templates\">サンプルテンプレートファイル</link>からスタックまたはテンプレートを作成するために、以下のコマンドを実行します。"
+
+#: ./doc/user-guide/section_cli_heat.xml32(replaceable)
+#: ./doc/user-guide/section_cli_heat.xml59(replaceable)
+msgid "PATH_TO_HEAT_TEMPLATES"
+msgstr "PATH_TO_HEAT_TEMPLATES"
+
+#: ./doc/user-guide/section_cli_heat.xml33(replaceable)
+msgid "USERNAME"
+msgstr "USERNAME"
+
+#: ./doc/user-guide/section_cli_heat.xml33(replaceable)
+#: ./doc/user-guide/app_cheat_sheet.xml47(replaceable)
+msgid "PASSWORD"
+msgstr "PASSWORD"
+
+#: ./doc/user-guide/section_cli_heat.xml33(replaceable)
+msgid "HEAT_KEY"
+msgstr "HEAT_KEY"
+
+#: ./doc/user-guide/section_cli_heat.xml34(para)
+msgid ""
+"The <literal>--parameters</literal> values that you specify depend on the "
+"parameters that are defined in the template. If a website hosts the template"
+" file, you can specify the URL with the <literal>--template-url</literal> "
+"parameter instead of the <literal>--template-file</literal> parameter."
+msgstr "指定する <literal>--parameters</literal> の値は、テンプレートで定義したパラメーターに依存します。ウェブサイトがテンプレートファイルを公開している場合、<literal>--template-file</literal> パラメーターの代わりに <literal>--template-url</literal> パラメーターを用いて URL を指定できます。"
+
+#: ./doc/user-guide/section_cli_heat.xml40(para)
+msgid "The command returns the following output:"
+msgstr "このコマンドは以下の出力を返します。"
+
+#: ./doc/user-guide/section_cli_heat.xml48(para)
+msgid ""
+"You can also use the <placeholder-1/> command to validate a template file "
+"without creating a stack from it."
+msgstr "テンプレートファイルからスタックを作成することなく、検証するために <placeholder-1/> コマンドを使用することもできます。"
+
+#: ./doc/user-guide/section_cli_heat.xml52(para)
+msgid ""
+"Previous versions of the heat client used <placeholder-1/> instead of "
+"<placeholder-2/>, but it has been deprecated in favor of <placeholder-3/>."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml58(para)
+msgid "To do so, run the following command:"
+msgstr "そうするために、以下のコマンドを実行します。"
+
+#: ./doc/user-guide/section_cli_heat.xml60(para)
+msgid "If validation fails, the response returns an error message."
+msgstr "検証に失敗した場合、応答がエラーメッセージを返します。"
+
+#: ./doc/user-guide/section_cli_heat.xml66(title)
+msgid "Get information about stacks"
+msgstr "スタック情報の取得"
+
+#: ./doc/user-guide/section_cli_heat.xml67(para)
+msgid ""
+"To explore the state and history of a particular stack, you can run a number"
+" of commands."
+msgstr "特定のスタックの状態と履歴を調査するために、いろいろなコマンドを実行できます。"
+
+#: ./doc/user-guide/section_cli_heat.xml71(para)
+msgid ""
+"To see which stacks are visible to the current user, run the following "
+"command:"
+msgstr "どのスタックが現在のユーザーから参照できるかを確認するために、以下のコマンドを実行します。"
+
+#: ./doc/user-guide/section_cli_heat.xml82(para)
+msgid "To show the details of a stack, run the following command:"
+msgstr "スタックの詳細を表示するために、以下のコマンドを実行します。"
+
+#: ./doc/user-guide/section_cli_heat.xml87(para)
+msgid ""
+"A stack consists of a collection of resources. To list the resources and "
+"their status, run the following command:"
+msgstr "スタックはリソースの集合から構成されます。リソースとその状態を一覧表示するために、以下のコマンドを実行します。"
+
+#: ./doc/user-guide/section_cli_heat.xml97(para)
+msgid ""
+"To show the details for a specific resource in a stack, run the following "
+"command:"
+msgstr "スタックにある特定のリソースの詳細を表示するために、以下のコマンドを実行します。"
+
+#: ./doc/user-guide/section_cli_heat.xml100(para)
+msgid ""
+"Some resources have associated metadata which can change throughout the life"
+" cycle of a resource. Show the metadata by running the following command:"
+msgstr "いくつかのリソースはリソースのライフサイクルを通して変更できるメタデータと関連づけられています。以下のコマンドを実行して、メタデータを表示します。"
+
+#: ./doc/user-guide/section_cli_heat.xml105(para)
+msgid ""
+"A series of events is generated during the life cycle of a stack. To display"
+" life cycle events, run the following command::"
+msgstr "一連のイベントはスタックのライフサイクルを通して生成されます。ライフサイクルイベントを表示するために、以下のコマンドを実行します。"
+
+#: ./doc/user-guide/section_cli_heat.xml116(para)
+msgid "To show the details for a particular event, run the following command:"
+msgstr "特定のイベントの詳細を表示するために、以下のコマンドを実行します。"
+
+#: ./doc/user-guide/section_cli_heat.xml123(title)
+msgid "Update a stack"
+msgstr "スタックの更新"
+
+#: ./doc/user-guide/section_cli_heat.xml124(para)
+msgid ""
+"To update an existing stack from a modified template file, run a command "
+"like the following command:"
+msgstr "修正したテンプレートファイルから既存のスタックを更新する場合、以下のようなコマンドを実行します。"
+
+#: ./doc/user-guide/section_cli_heat.xml135(para)
+msgid ""
+"Some resources are updated in-place, while others are replaced with new "
+"resources."
+msgstr "いくつかのリソースはすぐに更新され、他のものは新しいリソースで置き換えられます。"
+
 #: ./doc/user-guide/section_dashboard_create_networks.xml6(title)
 msgid "Create and manage networks"
 msgstr "ネットワークの作成と管理"
@@ -271,6 +429,2381 @@ msgid ""
 " the <guilabel>Network Topology</guilabel> tab."
 msgstr "正常にルーターを作成しました。<guilabel>ネットワークトポロジー</guilabel>タブから新しいトポロジーを表示できます。"
 
+#: ./doc/user-guide/section_sdk_nova.xml6(title)
+msgid "Compute"
+msgstr "コンピュート"
+
+#: ./doc/user-guide/section_sdk_nova.xml8(para)
+msgid ""
+"To use the information in this section, you must be familiar with OpenStack "
+"Compute."
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_nova.xml10(title)
+#: ./doc/user-guide/section_sdk_neutron.xml14(title)
+msgid "Set environment variables"
+msgstr "環境変数の設定"
+
+#: ./doc/user-guide/section_sdk_nova.xml11(para)
+msgid ""
+"To set up environmental variables and authenticate against Compute API "
+"endpoints, see <xref linkend=\"sdk_auth\"/>."
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_nova.xml16(title)
+msgid "Get OpenStack credentials (API v2)"
+msgstr "OpenStack クレデンシャルの取得 (API v2)"
+
+#: ./doc/user-guide/section_sdk_nova.xml17(para)
+msgid "These example use the <code>get_nova_credentials_v2</code> method:"
+msgstr "これらの例は <code>get_nova_credentials_v2</code> メソッドを使用します。"
+
+#: ./doc/user-guide/section_sdk_nova.xml27(para)
+#: ./doc/user-guide/section_sdk_neutron.xml35(para)
+#: ./doc/user-guide/section_sdk_neutron.xml53(para)
+msgid ""
+"This code resides in the <filename>credentials.py</filename> file, which all"
+" samples import."
+msgstr "このコードは <filename>credentials.py</filename> ファイルにあります。すべてのサンプルがこれをインポートします。"
+
+#: ./doc/user-guide/section_sdk_nova.xml30(para)
+msgid ""
+"Use the <code>get_nova_credentials_v2()</code> method to populate and get a "
+"dictionary:"
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_nova.xml36(title)
+msgid "List servers (API v2)"
+msgstr "サーバーの一覧表示 (API v2)"
+
+#: ./doc/user-guide/section_sdk_nova.xml37(para)
+msgid "The following program lists servers by using the Compute API v2."
+msgstr "以下のプログラムは、Compute API v2 を用いてサーバーを一覧表示します。"
+
+#: ./doc/user-guide/section_sdk_nova.xml40(title)
+msgid "To list servers"
+msgstr "サーバーの一覧表示方法"
+
+#: ./doc/user-guide/section_sdk_nova.xml42(para)
+#: ./doc/user-guide/section_sdk_nova.xml85(para)
+#: ./doc/user-guide/section_sdk_nova.xml162(para)
+#: ./doc/user-guide/section_sdk_nova.xml253(para)
+#: ./doc/user-guide/section_sdk_nova.xml340(para)
+#: ./doc/user-guide/section_sdk_nova.xml401(para)
+#: ./doc/user-guide/section_sdk_nova.xml464(para)
+#: ./doc/user-guide/section_sdk_neutron.xml255(para)
+#: ./doc/user-guide/section_sdk_neutron.xml340(para)
+#: ./doc/user-guide/section_sdk_neutron.xml416(para)
+#: ./doc/user-guide/section_sdk_neutron.xml468(para)
+#: ./doc/user-guide/section_sdk_neutron.xml519(para)
+msgid "Import the following modules:"
+msgstr "以下のモジュールをインポートします。"
+
+#: ./doc/user-guide/section_sdk_nova.xml47(para)
+#: ./doc/user-guide/section_sdk_nova.xml168(para)
+msgid ""
+"Get Nova credentials. See <xref "
+"linkend=\"sdk_compute_get_openstack_credentials_v2\"/>."
+msgstr "Nova クレデンシャルを取得します。<xref linkend=\"sdk_compute_get_openstack_credentials_v2\"/> を参照してください。"
+
+#: ./doc/user-guide/section_sdk_nova.xml52(para)
+#: ./doc/user-guide/section_sdk_nova.xml96(para)
+#: ./doc/user-guide/section_sdk_nova.xml173(para)
+#: ./doc/user-guide/section_sdk_nova.xml277(para)
+#: ./doc/user-guide/section_sdk_nova.xml360(para)
+#: ./doc/user-guide/section_sdk_nova.xml424(para)
+#: ./doc/user-guide/section_sdk_nova.xml485(para)
+#: ./doc/user-guide/section_sdk_neutron.xml268(para)
+msgid ""
+"Instantiate the <literal>nova_client</literal> client object by using the "
+"<literal>credentials</literal> dictionary object:"
+msgstr "<literal>credentials</literal> 辞書オブジェクトを使用して、<literal>nova_client</literal> クライアントオブジェクトのインスタンスを生成します。"
+
+#: ./doc/user-guide/section_sdk_nova.xml59(para)
+msgid ""
+"List servers by calling <literal>servers.list</literal> on "
+"<literal>nova_client</literal> object:"
+msgstr "<literal>nova_client</literal> オブジェクトの <literal>servers.list</literal> を呼び出し、サーバーを一覧表示します。"
+
+#: ./doc/user-guide/section_sdk_nova.xml66(title)
+msgid "List servers code listing"
+msgstr "サーバーの一覧表示のコード全体"
+
+#: ./doc/user-guide/section_sdk_nova.xml79(title)
+msgid "Create server (API v2)"
+msgstr "サーバーの作成 (API v2)"
+
+#: ./doc/user-guide/section_sdk_nova.xml80(para)
+msgid ""
+"The following program creates a server (VM) by using the Compute API v2."
+msgstr "以下のプログラムは、Compute API v2 を用いてサーバー (VM) を作成します。"
+
+#: ./doc/user-guide/section_sdk_nova.xml83(title)
+msgid "To create a server"
+msgstr "サーバーの作成方法"
+
+#: ./doc/user-guide/section_sdk_nova.xml91(para)
+#: ./doc/user-guide/section_sdk_nova.xml419(para)
+#: ./doc/user-guide/section_sdk_nova.xml480(para)
+msgid ""
+"Get OpenStack credentials. See <xref "
+"linkend=\"sdk_compute_get_openstack_credentials_v2\"/>."
+msgstr "OpenStack クレデンシャルを取得します。<xref linkend=\"sdk_compute_get_openstack_credentials_v2\"/> を参照してください。"
+
+#: ./doc/user-guide/section_sdk_nova.xml103(para)
+msgid ""
+"Get the flavor and image to use to create a server. This code uses the "
+"<literal>cirros</literal> image, the <literal>m1.tiny</literal> flavor, and "
+"the <literal>private</literal> network:"
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_nova.xml113(para)
+msgid "To create the server, use the network, image, and flavor:"
+msgstr "サーバーを作成し、ネットワーク、イメージ、フレーバーを使用する方法:"
+
+#: ./doc/user-guide/section_sdk_nova.xml120(para)
+msgid ""
+"Sleep for five seconds and determine whether the server/vm was created by "
+"calling <literal>nova_client.servers.list()</literal>:"
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_nova.xml130(title)
+msgid "Create server code listing"
+msgstr "サーバーの作成のコード全体"
+
+#: ./doc/user-guide/section_sdk_nova.xml156(title)
+msgid "Delete server (API v2)"
+msgstr "サーバーの削除 (API v2)"
+
+#: ./doc/user-guide/section_sdk_nova.xml157(para)
+msgid ""
+"The following program deletes a server (VM) by using the Compute API v2."
+msgstr "以下のプログラムは、Compute API v2 を用いてサーバー (VM) を削除します。"
+
+#: ./doc/user-guide/section_sdk_nova.xml160(title)
+msgid "To delete a server"
+msgstr "サーバーの削除方法"
+
+#: ./doc/user-guide/section_sdk_nova.xml180(para)
+msgid "Determine whether the <literal>vm1</literal> server exists:"
+msgstr "<literal>vm1</literal> サーバーが存在するかを確認します。"
+
+#: ./doc/user-guide/section_sdk_nova.xml184(para)
+msgid "List servers: <literal>servers_list</literal>."
+msgstr "サーバー一覧 <literal>servers_list</literal> を取得します。"
+
+#: ./doc/user-guide/section_sdk_nova.xml188(para)
+msgid ""
+"Iterate over <literal>servers_list</literal> and compare name with "
+"<literal>vm1</literal>."
+msgstr "<literal>servers_list</literal> を反復し、名前を <literal>vm1</literal> と比較します。"
+
+#: ./doc/user-guide/section_sdk_nova.xml194(para)
+msgid ""
+"If true, set the variable name <literal>server_exists</literal> to "
+"<literal>True</literal> and break from the for loop:"
+msgstr "存在すると、<literal>server_exists</literal> 変数が <literal>True</literal> になり、for ループを抜けます。"
+
+#: ./doc/user-guide/section_sdk_nova.xml211(para)
+msgid ""
+"If the server exists, run the <literal>delete</literal> method of the "
+"<literal>nova_client.servers</literal> object:"
+msgstr "サーバーが存在すると、<literal>nova_client.servers</literal> オブジェクトの <literal>delete</literal> メソッドを実行します。"
+
+#: ./doc/user-guide/section_sdk_nova.xml220(title)
+msgid "Delete server code listing"
+msgstr "サーバーの削除のコード全体"
+
+#: ./doc/user-guide/section_sdk_nova.xml247(title)
+msgid "Update server (API v2)"
+msgstr "サーバーの更新 (API v2)"
+
+#: ./doc/user-guide/section_sdk_nova.xml248(para)
+msgid ""
+"The following program updates the name of a server (VM) by using the Compute"
+" API v2."
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_nova.xml251(title)
+msgid "To update a server"
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_nova.xml257(para)
+msgid ""
+"<literal>print_server</literal> is a method defined in "
+"<filename>utils.py</filename> and prints the server details as shown in the "
+"code listing below:"
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_nova.xml272(para)
+msgid ""
+"Get OpenStack Credentials. See <xref "
+"linkend=\"sdk_compute_get_openstack_credentials_v2\"/>."
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_nova.xml284(para)
+msgid ""
+"Get the server instance using <literal>server_id</literal> and print the "
+"details by calling <literal>print_server</literal> method:"
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_nova.xml294(para)
+msgid ""
+"Call <code>server.update</code> on the server object with the new value for "
+"<literal>name</literal> variable:"
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_nova.xml300(para)
+msgid "Get the updated instance of the server:"
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_nova.xml304(para)
+msgid ""
+"Call <literal>print_server</literal> again to check the update server "
+"details:"
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_nova.xml311(title)
+msgid "Update server code listing"
+msgstr "サーバーの更新のコード全体"
+
+#: ./doc/user-guide/section_sdk_nova.xml334(title)
+msgid "List flavors (API v2)"
+msgstr "フレーバーの一覧表示 (API v2)"
+
+#: ./doc/user-guide/section_sdk_nova.xml335(para)
+msgid ""
+"The following program lists flavors and their details by using the Compute "
+"API v2."
+msgstr "以下のプログラムは、Compute API v2 を用いてフレーバーとその詳細を一覧表示します。"
+
+#: ./doc/user-guide/section_sdk_nova.xml338(title)
+msgid "To list flavors"
+msgstr "フレーバーの一覧表示方法"
+
+#: ./doc/user-guide/section_sdk_nova.xml344(para)
+msgid ""
+"The <literal>print_flavors</literal> method is defined in "
+"<filename>utils.py</filename> and prints the flavor details:"
+msgstr "<literal>print_flavors</literal> メソッドは、<filename>utils.py</filename> で定義され、フレーバーの詳細を表示します。"
+
+#: ./doc/user-guide/section_sdk_nova.xml355(para)
+msgid ""
+"Get openStack credentials. See <xref "
+"linkend=\"sdk_compute_get_openstack_credentials_v2\"/>."
+msgstr "OpenStack クレデンシャルを取得します。<xref linkend=\"sdk_compute_get_openstack_credentials_v2\"/> を参照してください。"
+
+#: ./doc/user-guide/section_sdk_nova.xml367(para)
+msgid ""
+"List flavors by calling <literal>list()</literal> on "
+"<literal>nova_client.flavors</literal> object:"
+msgstr "<literal>nova_client.flavors</literal>  オブジェクトの <literal>list()</literal> を呼び出し、フレーバーを一覧表示します。"
+
+#: ./doc/user-guide/section_sdk_nova.xml374(para)
+msgid ""
+"Print the flavor details, id and name by calling "
+"<literal>print_flavors</literal>:"
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_nova.xml380(title)
+msgid "List flavors code listing"
+msgstr "フレーバーの一覧表示のコード全体"
+
+#: ./doc/user-guide/section_sdk_nova.xml395(title)
+msgid "List floating IPs (API v2)"
+msgstr "Floating IP の一覧表示 (API v2)"
+
+#: ./doc/user-guide/section_sdk_nova.xml396(para)
+msgid ""
+"The following program lists the floating IPs and their details by using the "
+"Compute API v2."
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_nova.xml399(title)
+msgid "To list floating IPs"
+msgstr "Floating IP の一覧表示方法"
+
+#: ./doc/user-guide/section_sdk_nova.xml405(para)
+msgid ""
+"The <literal>print_values_ip</literal> method is defined in "
+"<filename>utils.py</filename> and prints the floating_ip object details:"
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_nova.xml431(para)
+msgid ""
+"List floating IPs by calling <literal>list()</literal> on "
+"<literal>nova_client.floating_ips</literal> object:"
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_nova.xml438(para)
+msgid ""
+"Print the floating IP object details by calling "
+"<literal>print_values_ip</literal>:"
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_nova.xml444(title)
+msgid "List floating IPs code listing"
+msgstr "Floating IP の一覧表示のコード全体"
+
+#: ./doc/user-guide/section_sdk_nova.xml458(title)
+msgid "List hosts (API v2)"
+msgstr "ホストの一覧表示 (API v2)"
+
+#: ./doc/user-guide/section_sdk_nova.xml459(para)
+msgid "The following program lists the hosts by using the Compute API v2."
+msgstr "以下のプログラムは、Compute API v2 を用いてホストを一覧表示します。"
+
+#: ./doc/user-guide/section_sdk_nova.xml462(title)
+msgid "To list hosts"
+msgstr "ホストの一覧表示方法"
+
+#: ./doc/user-guide/section_sdk_nova.xml468(para)
+msgid ""
+"The <literal>print_hosts</literal> method is defined in "
+"<filename>utils.py</filename> and prints the host object details:"
+msgstr "<literal>print_hosts</literal> メソッドは、<filename>utils.py</filename> で定義され、host オブジェクトの詳細を表示します。"
+
+#: ./doc/user-guide/section_sdk_nova.xml492(para)
+msgid ""
+"List hosts by calling <literal>list()</literal> on "
+"<literal>nova_client.hosts</literal> object:"
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_nova.xml498(para)
+msgid ""
+"Print the host object details by calling "
+"<literal>print_hosts(host_list)</literal>:"
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_nova.xml504(title)
+msgid "List hosts code listing"
+msgstr "ホストの一覧表示のコード全体"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml10(title)
+msgid "Launch an instance"
+msgstr "インスタンスの起動"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml12(para)
+msgid ""
+"When you launch an instance from an image, OpenStack creates a local copy of"
+" the image on the compute node where the instance starts."
+msgstr "イメージからインスタンスを起動するとき、OpenStack はインスタンスが起動するコンピュートノードにイメージのローカルコピーを作成します。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml14(para)
+msgid "When you launch an instance from a volume, note the following steps:"
+msgstr "ボリュームからインスタンスを起動するとき、以下の手順に注意してください。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml18(para)
+msgid ""
+"To select the volume to from which to launch, launch an instance from an "
+"arbitrary image on the volume. The image that you select does not boot. "
+"Instead, it is replaced by the image on the volume that you choose in the "
+"next steps."
+msgstr "起動するボリュームを選択する場合、ボリュームにある任意のイメージからインスタンスを起動します。選択したイメージは起動しません。代わりに、次の手順で選択したボリュームにあるイメージにより置き換えられます。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml22(para)
+msgid ""
+"To boot a Xen image from a volume, the image you launch in must be the same "
+"type, fully virtualized or paravirtualized, as the one on the volume."
+msgstr "ボリュームから Xen イメージを起動するために、起動するイメージは、ボリュームにあるものと同じ形式、完全仮想化または準仮想化である必要があります。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml27(para)
+msgid ""
+"Select the volume or volume snapshot from which to boot. Enter a device "
+"name. Enter <literal>vda</literal> for KVM images or <literal>xvda</literal>"
+" for Xen images."
+msgstr "起動するためのボリュームまたはボリュームのスナップショットを選択します。デバイス名を入力します。KVM イメージの場合は <literal>vda</literal>、Xen イメージの場合は <literal>xvda</literal> を入力します。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml34(para)
+msgid ""
+"Log in to the dashboard, choose a project, and click "
+"<guilabel>Images</guilabel>."
+msgstr "ダッシュボードにログインし、プロジェクトを選択し、<guilabel>イメージ</guilabel>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml36(para)
+msgid ""
+"The dashboard shows the images that have been uploaded to OpenStack Image "
+"Service and are available for this project."
+msgstr "ダッシュボードは、OpenStack Image Service にアップロードされた、このプロジェクトが利用可能なイメージを表示します。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml39(para)
+msgid ""
+"For details on creating images, see <link href=\"http://docs.openstack.org"
+"/image-guide/content/ch_creating_images_manually.html\">Creating images "
+"manually</link> in the <citetitle>OpenStack Virtual Machine Image "
+"Guide</citetitle>."
+msgstr "イメージの作成に関する詳細は、<citetitle>OpenStack Virtual 仮想マシンイメージガイド</citetitle>の<link href=\"http://docs.openstack.org/image-guide/content/ch_creating_images_manually.html\">イメージの手動作成</link>を参照してください。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml45(para)
+msgid "Select an image and click <guibutton>Launch</guibutton>."
+msgstr "イメージを選択し、<guibutton>起動</guibutton>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml48(para)
+msgid "In the Launch Instance dialog box, specify the following values:"
+msgstr "インスタンスの起動ダイアログボックスで、以下の値を指定します。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml55(guilabel)
+msgid "Details"
+msgstr "詳細"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml60(guilabel)
+msgid "Availability Zone"
+msgstr "アベイラビリティゾーン"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml62(para)
+msgid ""
+"By default, this value is set to the availability zone given by the cloud "
+"provider (for example, <literal>us-west</literal> or <literal>apac-"
+"south</literal>). For some cases, it could be <literal>nova</literal>."
+msgstr "この値はデフォルトで、クラウドプロバイダーにより指定されたアベイラビリティゾーンに設定されます (例えば、<literal>us-west</literal>、<literal>apac-south</literal>)。<literal>nova</literal> となっている場合もあります。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml69(guilabel)
+msgid "Instance Name"
+msgstr "インスタンス名"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml70(para)
+msgid "Assign a name to the virtual machine."
+msgstr "仮想マシンに名前を割り当てます。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml71(para)
+msgid ""
+"The name you assign here becomes the initial host name of the server. After "
+"the server is built, if you change the server name in the API or change the "
+"host name directly, the names are not updated in the dashboard."
+msgstr "ここで割り当てた名前が、サーバーの初期ホスト名になります。サーバー稼働後、API でサーバー名を変更した場合、ホスト名を直接変更した場合、ダッシュボードに表示される名前は更新されません。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml75(para)
+msgid ""
+"Server names are not guaranteed to be unique when created so you could have "
+"two instances with the same host name."
+msgstr "サーバー名は一意性が保証されていません。そのため、同じ名前を持つインスタンスを 2 つ起動する可能性があります。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml82(guilabel)
+msgid "Flavor"
+msgstr "フレーバー"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml83(para)
+msgid "Specify the size of the instance to launch."
+msgstr "起動するインスタンスの大きさを指定します。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml84(para)
+msgid ""
+"The flavor is selected based on the size of the image selected for launching"
+" an instance. For example, while creating an image, if you have entered the "
+"value in the <guilabel>Minimum RAM (MB)</guilabel> field as 2048, then on "
+"selecting the image, the default flavor is <guilabel>m1.small</guilabel>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml94(guilabel)
+msgid "Instance Count"
+msgstr "インスタンス数"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml95(para)
+msgid ""
+"To launch multiple instances, enter a value greater than 1. The default is "
+"1."
+msgstr "複数のインスタンスを起動する場合、1 より大きな値を入力します。初期値は 1 です。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml99(guilabel)
+msgid "Instance Boot Source"
+msgstr "インスタンスのブートソース"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml100(para)
+msgid "Your options are:"
+msgstr "以下のオプションがあります。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml103(guilabel)
+msgid "Boot from image"
+msgstr "イメージから起動"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml104(para)
+msgid ""
+"If you choose this option, a new field for <guilabel>Image Name</guilabel> "
+"displays. You can select the image from the list."
+msgstr "このオプションを選択する場合、<guilabel>イメージ名</guilabel>の新項目が表示されます。この一覧からイメージを選択できます。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml109(guilabel)
+msgid "Boot from snapshot"
+msgstr "スナップショットから起動"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml110(para)
+msgid ""
+"If you choose this option, a new field for <guilabel>Instance "
+"Snapshot</guilabel> displays. You can select the snapshot from the list."
+msgstr "このオプションを選択する場合、<guilabel>インスタンスのスナップショット</guilabel>の新項目が表示されます。この一覧からスナップショットを選択できます。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml115(guilabel)
+msgid "Boot from volume"
+msgstr "ボリュームから起動"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml116(para)
+msgid ""
+"If you choose this option, a new field for <guilabel>Volume</guilabel> "
+"displays. You can select the volume from the list."
+msgstr "このオプションを選択する場合、<guilabel>ボリューム</guilabel>の新項目が表示されます。この一覧からボリュームを選択できます。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml121(guilabel)
+msgid "Boot from image (creates a new volume)"
+msgstr "イメージから起動 (新しいボリュームを作成)"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml122(para)
+msgid ""
+"With this option, you can boot from an image and create a volume by entering"
+" the <guilabel>Device Size</guilabel> and <guilabel>Device Name</guilabel> "
+"for your volume. Click the <guilabel>Delete on Terminate</guilabel> option "
+"to delete the volume on terminating the instance."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml130(guilabel)
+msgid "Boot from volume snapshot (creates a new volume)"
+msgstr "ボリュームのスナップショットから起動 (新しいボリュームを作成)"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml132(para)
+msgid ""
+"Using this option, you can boot from a volume snapshot and create a new "
+"volume by choosing <guilabel>Volume Snapshot</guilabel> from a list and "
+"adding a <guilabel>Device Name</guilabel> for your volume. Click the "
+"<guilabel>Delete on Terminate</guilabel> option to delete the volume on "
+"terminating the instance."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml141(para)
+msgid ""
+"Since you are launching an instance from an image, <guilabel>Boot from "
+"image</guilabel> is chosen by default."
+msgstr "イメージからインスタンスを起動するため、<guilabel>イメージから起動</guilabel>が初めから選択されています。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml147(guilabel)
+msgid "Image Name"
+msgstr "イメージ名"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml148(para)
+msgid ""
+"This field changes based on your previous selection. Since you have chosen "
+"to launch an instance using an image, the <guilabel>Image Name</guilabel> "
+"field displays. Select the image name from the dropdown list."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml155(guilabel)
+msgid "Access &amp; Security"
+msgstr "アクセスとセキュリティ"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml159(guilabel)
+msgid "Keypair"
+msgstr "キーペア"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml160(para)
+msgid "Specify a key pair."
+msgstr "キーペアを指定します。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml161(para)
+msgid ""
+"If the image uses a static root password or a static key set (neither is "
+"recommended), you do not need to provide a key pair to launch the instance."
+msgstr "イメージが固定の root パスワードまたは固定のキーセットを使用する場合 (どちらも推奨されません)、インスタンスを起動するためにキーペアを提供する必要がありません。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml166(guilabel)
+msgid "Security Groups"
+msgstr "セキュリティグループ"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml167(para)
+msgid "Activate the security groups that you want to assign to the instance."
+msgstr "インスタンスに割り当てたいセキュリティグループを有効化します。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml169(para)
+msgid ""
+"Security groups are a kind of cloud firewall that define which incoming "
+"network traffic is forwarded to instances. For details, see <xref "
+"linkend=\"security_groups_add_rule\"/>."
+msgstr "セキュリティグループはある種のクラウドファイアウォールです。どの入力ネットワーク通信がインスタンスに転送されるのかを定義します。詳細は<xref linkend=\"security_groups_add_rule\"/>を参照してください。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml173(para)
+msgid ""
+"If you have not created any security groups, you can assign only the default"
+" security group to the instance."
+msgstr "セキュリティグループを何も作成していなければ、標準のセキュリティグループのみをインスタンスに割り当てられます。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml178(guilabel)
+#: ./doc/user-guide/section_sdk_neutron.xml6(title)
+msgid "Networking"
+msgstr "ネットワーク"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml181(guilabel)
+msgid "Selected Networks"
+msgstr "選択済みネットワーク"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml182(para)
+msgid ""
+"To add a network to the instance, click the <guibutton>+</guibutton> in the "
+"<guilabel>Available Networks</guilabel> field."
+msgstr "インスタンスにネットワークを追加するために、<guilabel>利用可能なネットワーク</guilabel>欄にある <guibutton>+</guibutton> をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml188(guilabel)
+msgid "Post-Creation"
+msgstr "作成後"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml191(guilabel)
+msgid "Customization Script"
+msgstr "カスタマイズ・スクリプト"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml192(para)
+msgid "Specify a customization script that runs after your instance launches."
+msgstr "インスタンスの起動後に実行するカスタマイズスクリプトを指定します。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml196(guilabel)
+msgid "Advanced Options"
+msgstr "高度な設定"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml199(guilabel)
+msgid "Disk Partition"
+msgstr "ディスクパーティション"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml200(para)
+msgid "Select the type of disk partition from the dropdown list."
+msgstr "ドロップダウンリストからディスクパーティションの種類を選択します。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml204(guilabel)
+msgid "Automatic"
+msgstr "自動"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml206(para)
+msgid "Entire disk is single partition and automatically resizes."
+msgstr "ディスク全体が単一パーティションになり、自動的にリサイズされます。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml210(guilabel)
+msgid "Manual"
+msgstr "手動"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml212(para)
+msgid "Faster build times but requires manual partitioning."
+msgstr "構築時間は早いですが、手動でパーティション作成する必要があります。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml231(para)
+msgid "Click <guibutton>Launch</guibutton>."
+msgstr "<guibutton>起動</guibutton>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml232(para)
+msgid "The instance starts on a compute node in the cloud."
+msgstr "インスタンスがクラウドのコンピュートノードで起動します。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml235(para)
+msgid ""
+"The <guilabel>Instances</guilabel> tab shows the instance's name, its "
+"private and public IP addresses, size, status, task, and power state."
+msgstr "<guilabel>インスタンス</guilabel>タブに、インスタンス名、プライベート IP アドレス、パブリック IP アドレス、大きさ、状態、処理、電源状態が表示されます。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml238(para)
+msgid ""
+"If you did not provide a key pair, security groups, or rules, users can "
+"access the instance only from inside the cloud through VNC. Even pinging the"
+" instance is not possible without an ICMP rule configured. To access the "
+"instance through a VNC console, see <xref linkend=\"instance_console\"/>."
+msgstr "キーペア、セキュリティグループ、ルールなどを指定していない場合、ユーザーは VNC 経由でクラウドの中からのみインスタンスにアクセスできます。ICMP のルールを設定していなければ、インスタンスに ping できないでしょう。VNC コンソールからインスタンスにアクセスする方法は、<xref linkend=\"instance_console\"/>を参照してください。"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml6(title)
+msgid "Upload and manage images"
+msgstr "イメージのアップロードと管理"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml7(para)
+msgid ""
+"A virtual machine image, referred to in this document simply as an image, is"
+" a single file that contains a virtual disk that has a bootable operating "
+"system installed on it. Images are used to create virtual machine instances "
+"within the cloud. For information about creating image files, see the <link "
+"href=\"http://docs.openstack.org/image-guide/content/\"><citetitle>OpenStack"
+" Virtual Machine Image Guide</citetitle></link>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml15(para)
+msgid ""
+"Depending on your role, you may have permission to upload and manage virtual"
+" machine images. Operators might restrict the upload and management of "
+"images to cloud administrators or operators only. If you have the "
+"appropriate privileges, you can use the dashboard to upload and manage "
+"images in the <guilabel>admin</guilabel> project."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml22(para)
+msgid ""
+"You can also use the <placeholder-1/> and <placeholder-2/> command-line "
+"clients or the Image Service and Compute APIs to manage images. See <xref "
+"linkend=\"cli_manage_images\"/>."
+msgstr "イメージを管理するために、<placeholder-1/> と <placeholder-2/> コマンドラインクライアントまたは Image Service API と Compute API を使用することもできます。<xref linkend=\"cli_manage_images\"/>を参照してください。"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml28(title)
+#: ./doc/user-guide/section_sdk_manage_images.xml101(title)
+msgid "Upload an image"
+msgstr "イメージのアップロード"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml29(para)
+msgid "Follow this procedure to upload an image to a project."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml33(para)
+#: ./doc/user-guide/section_dashboard_manage_images.xml159(para)
+#: ./doc/user-guide/section_dashboard_manage_images.xml206(para)
+msgid "Log in to the dashboard."
+msgstr "ダッシュボードにログインします。"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml36(para)
+#: ./doc/user-guide/section_dashboard_manage_images.xml162(para)
+#: ./doc/user-guide/section_dashboard_manage_images.xml209(para)
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml216(para)
+msgid ""
+"From the <guilabel>CURRENT PROJECT</guilabel> on the "
+"<guilabel>Project</guilabel> tab, select the appropriate project."
+msgstr "<guilabel>プロジェクト</guilabel>タブの<guilabel>現在のプロジェクト</guilabel>から、適切なプロジェクトを選択します。"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml41(para)
+#: ./doc/user-guide/section_dashboard_manage_images.xml167(para)
+#: ./doc/user-guide/section_dashboard_manage_images.xml213(para)
+msgid ""
+"On the <guilabel>Project</guilabel> tab, click <guilabel>Images</guilabel>."
+msgstr "<guilabel>プロジェクト</guilabel> タブで、<guilabel>イメージ</guilabel>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml45(para)
+#: ./doc/user-guide/section_dashboard_manage_images.xml148(para)
+msgid "Click <guibutton>Create Image</guibutton>."
+msgstr "<guibutton>イメージの作成</guibutton>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml46(para)
+msgid "The Create An Image dialog box appears."
+msgstr "「イメージの作成」ダイアログボックスが表示されます。"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml49(para)
+msgid "Enter the following values:"
+msgstr "以下の値を入力します。"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml56(guilabel)
+msgid "Name"
+msgstr "名前"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml59(para)
+msgid "Enter a name for the image."
+msgstr "イメージの名前を入力します。"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml64(guilabel)
+#: ./doc/user-guide/app_cheat_sheet.xml20(th)
+#: ./doc/user-guide/app_cheat_sheet.xml66(th)
+#: ./doc/user-guide/app_cheat_sheet.xml140(th)
+#: ./doc/user-guide/app_cheat_sheet.xml333(th)
+#: ./doc/user-guide/app_cheat_sheet.xml374(th)
+#: ./doc/user-guide/app_cheat_sheet.xml458(th)
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml43(guilabel)
+msgid "Description"
+msgstr "説明"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml67(para)
+msgid "Optionally, enter a brief description of the image."
+msgstr "オプションとして、イメージの簡単な説明を入力します。"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml73(guilabel)
+msgid "Image Source"
+msgstr "イメージソース"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml76(para)
+msgid ""
+"Choose the image source from the list. Your choices are <guilabel>Image "
+"Location</guilabel> and <guilabel>Image File</guilabel>."
+msgstr "一覧からイメージのソースを選択します。<guilabel>イメージの場所</guilabel>と<guilabel>イメージファイル</guilabel>を選択できます。"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml83(para)
+msgid "<guilabel>Image File</guilabel> or <guilabel>Image Location</guilabel>"
+msgstr "<guilabel>イメージファイル</guilabel>または<guilabel>イメージの場所</guilabel>"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml88(para)
+msgid ""
+"Based on your selection for <guilabel>Image Source</guilabel>, you either "
+"enter the location URL of the image in the <guilabel>Image "
+"Location</guilabel> field. or browse to the image file on your system and "
+"add it."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml97(guilabel)
+msgid "Format"
+msgstr "形式"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml100(para)
+msgid "Select the correct format (for example, QCOW2) for the image."
+msgstr "イメージの適切な形式 (例: QCOW2) を選択します。"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml107(guilabel)
+msgid "Architecture"
+msgstr "アーキテクチャー"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml111(para)
+msgid ""
+"Specify the architecture. For example, <literal>i386</literal> for a 32-bit "
+"architecture or <literal>x86-64</literal> for a 64-bit architecture."
+msgstr "アーキテクチャーを指定します。例えば、32 ビットアーキテクチャーは <literal>i386</literal>、64 ビットアーキテクチャーは <literal>x86-64</literal> です。"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml118(para)
+msgid ""
+"<guilabel>Minimum Disk (GB)</guilabel> and <guilabel>Minimum RAM "
+"(MB)</guilabel>"
+msgstr "<guilabel>最小ディスク (GB)</guilabel> および<guilabel>最小メモリ (MB)</guilabel>"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml122(para)
+msgid "Leave these optional fields empty."
+msgstr "これらのオプション項目を空白のままにします。"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml127(guilabel)
+msgid "Public"
+msgstr "パブリック"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml130(para)
+msgid ""
+"Select this check box to make the image public to all users with access to "
+"the current project."
+msgstr "現在のプロジェクトにアクセス権を持つすべてのユーザーにイメージを公開する場合、このチェックボックスを選択します。"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml137(guilabel)
+msgid "Protected"
+msgstr "保護"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml140(para)
+msgid ""
+"Select this check box to ensure that only users with permissions can delete "
+"the image."
+msgstr "権限を持つユーザーのみがこのイメージを削除できるようにする場合、このチェックボックスを選択します。"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml149(para)
+msgid ""
+"The image is queued to be uploaded. It might take some time before the "
+"status changes from Queued to Active."
+msgstr "イメージがアップロードのためにキューに入れられます。ステータスが Queued  から Active に変更されるまでに少し時間がかかるかもしれません。"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml155(title)
+msgid "Update an image"
+msgstr "イメージの更新"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml156(para)
+msgid "Follow this procedure to update an existing image."
+msgstr "既存のイメージを更新する場合、この手順を実行します。"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml171(para)
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml225(para)
+msgid "Select the image that you want to edit."
+msgstr "編集したいイメージを選択します。"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml174(para)
+msgid ""
+"In the <guilabel>Actions</guilabel> column, click <guilabel>More</guilabel> "
+"and then select <guilabel>Edit</guilabel> from the list."
+msgstr "<guilabel>アクション</guilabel>列の<guilabel>▼</guilabel>をクリックし、一覧から<guilabel>編集</guilabel>を選択します。"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml182(para)
+msgid "Change the name of the image."
+msgstr "イメージの名前を変更します。"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml185(para)
+msgid ""
+"Select the <guilabel>Public</guilabel> check box to make the image public."
+msgstr "イメージをパブリックにするために、<guilabel>パブリック</guilabel>チェックボックスを選択します。"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml189(para)
+msgid ""
+"Clear the <guilabel>Public</guilabel> check box to make the image private."
+msgstr "イメージをプライベートにするために、<guilabel>パブリック</guilabel>チェックボックスを選択解除します。"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml179(para)
+msgid ""
+"In the Update Image dialog box, you can perform the following actions: "
+"<placeholder-1/>"
+msgstr "イメージの更新ダイアログボックスで、以下の操作を実行できます: <placeholder-1/>"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml195(para)
+msgid "Click <guibutton>Update Image</guibutton>."
+msgstr "<guibutton>イメージの更新</guibutton>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml200(title)
+msgid "Delete an image"
+msgstr "イメージの削除"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml201(para)
+msgid ""
+"Deletion of images is permanent and <emphasis "
+"role=\"bold\">cannot</emphasis> be reversed. Only users with the appropriate"
+" permissions can delete images."
+msgstr "イメージの削除は、永続的であり、元に戻せ<emphasis role=\"bold\">ません</emphasis>。適切なパーミッションを持つユーザーのみが、イメージを削除できます。"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml217(para)
+msgid "Select the images that you want to delete."
+msgstr "削除したいイメージを選択します。"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml220(para)
+msgid "Click <guibutton>Delete Images</guibutton>."
+msgstr "<guibutton>イメージの削除</guibutton>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml223(para)
+msgid ""
+"In the <guilabel>Confirm Delete Image</guilabel> dialog box, click "
+"<guibutton>Delete Images</guibutton> to confirm the deletion."
+msgstr "<guilabel>イメージの削除の確認</guilabel>ダイアログボックスで、削除を確認するために<guibutton>イメージの削除</guibutton>をクリックします。"
+
+#: ./doc/user-guide/section_cli_ceilometer.xml7(title)
+msgid "Measure cloud resources"
+msgstr "クラウドのリソースの測定"
+
+#: ./doc/user-guide/section_cli_ceilometer.xml8(para)
+msgid ""
+"Telemetry measures cloud resources in OpenStack. It collects data related to"
+" billing. Currently, this metering service is available through only the "
+"<placeholder-1/> command-line client."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_ceilometer.xml10(para)
+msgid "To model data, Telemetry uses the following abstractions:"
+msgstr "データをモデル化するために、Telemetry は以下の抽象化を使用します。"
+
+#: ./doc/user-guide/section_cli_ceilometer.xml13(emphasis)
+msgid "Meter"
+msgstr "メーター"
+
+#: ./doc/user-guide/section_cli_ceilometer.xml15(para)
+msgid ""
+"Measures a specific aspect of resource usage, such as the existence of a "
+"running instance, or ongoing performance, such as the CPU utilization for an"
+" instance. Meters exist for each type of resource. For example, a separate "
+"<literal>cpu_util</literal> meter exists for each instance. The life cycle "
+"of a meter is decoupled from the existence of its related resource. The "
+"meter persists after the resource goes away."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_ceilometer.xml25(para)
+msgid "A meter has the following attributes:"
+msgstr "メーターは以下の属性を持ちます。"
+
+#: ./doc/user-guide/section_cli_ceilometer.xml28(para)
+msgid "String name"
+msgstr "名称文字列"
+
+#: ./doc/user-guide/section_cli_ceilometer.xml31(para)
+msgid "A unit of measurement"
+msgstr "測定単位"
+
+#: ./doc/user-guide/section_cli_ceilometer.xml34(para)
+msgid ""
+"A type, which indicates whether values increase monotonically (cumulative), "
+"are interpreted as a change from the previous value (delta), or are stand-"
+"alone and relate only to the current duration (gauge)"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_ceilometer.xml42(emphasis)
+msgid "Sample"
+msgstr "サンプル"
+
+#: ./doc/user-guide/section_cli_ceilometer.xml44(para)
+msgid ""
+"An individual data point that is associated with a specific meter. A sample "
+"has the same attributes as the associated meter, with the addition of time "
+"stamp and value attributes. The value attribute is also known as the sample "
+"<emphasis role=\"italic\">volume</emphasis>."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_ceilometer.xml50(emphasis)
+msgid "Statistic"
+msgstr "統計"
+
+#: ./doc/user-guide/section_cli_ceilometer.xml52(para)
+msgid ""
+"A set of data point aggregates over a time duration. (In contrast, a sample "
+"represents a single data point.) The Telemetry service employs the following"
+" aggregation functions:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_ceilometer.xml56(para)
+msgid ""
+"<emphasis role=\"bold\">count</emphasis>. The number of samples in each "
+"period."
+msgstr "<emphasis role=\"bold\">数量</emphasis>。各期間のサンプル数。"
+
+#: ./doc/user-guide/section_cli_ceilometer.xml61(para)
+msgid ""
+"<emphasis role=\"bold\">max</emphasis>. The maximum number of sample volumes"
+" in each period."
+msgstr "<emphasis role=\"bold\">最大</emphasis>。各期間の最大サンプルボリューム数。"
+
+#: ./doc/user-guide/section_cli_ceilometer.xml66(para)
+msgid ""
+"<emphasis role=\"bold\">min</emphasis>. The minimum number of sample volumes"
+" in each period."
+msgstr "<emphasis role=\"bold\">最小</emphasis>。各期間の最小サンプルボリューム数。"
+
+#: ./doc/user-guide/section_cli_ceilometer.xml71(para)
+msgid ""
+"<emphasis role=\"bold\">avg</emphasis>. The average of sample volumes over "
+"each period."
+msgstr "<emphasis role=\"bold\">平均</emphasis>。各期間の平均サンプルボリューム数。"
+
+#: ./doc/user-guide/section_cli_ceilometer.xml76(para)
+msgid ""
+"<emphasis role=\"bold\">sum</emphasis>. The sum of sample volumes over each "
+"period."
+msgstr "<emphasis role=\"bold\">合計</emphasis>。各期間の合計サンプルボリューム数。"
+
+#: ./doc/user-guide/section_cli_ceilometer.xml84(emphasis)
+msgid "Alarm"
+msgstr "アラーム"
+
+#: ./doc/user-guide/section_cli_ceilometer.xml86(para)
+msgid ""
+"A set of rules that define a monitor and a current state, with edge-"
+"triggered actions associated with target states. Alarms provide user-"
+"oriented Monitoring-as-a-Service and a general purpose utility for "
+"OpenStack. Orchestration auto scaling is a typical use case. Alarms follow a"
+" tristate model of <literal>ok</literal>, <literal>alarm</literal>, and "
+"<literal>insufficient data</literal>. For conventional threshold-oriented "
+"alarms, a static threshold value and comparison operator govern state "
+"transitions. The comparison operator compares a selected meter statistic "
+"against an evaluation window of configurable length into the recent past."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_ceilometer.xml96(para)
+msgid ""
+"This example uses the <placeholder-1/> client to create an auto-scaling "
+"stack and the <placeholder-2/> client to measure resources."
+msgstr "この例は、オートスケールするスタックを作成するために <placeholder-1/> コマンドを使用し、リソースを計測するために <placeholder-2/> クライアントを使用します。"
+
+#: ./doc/user-guide/section_cli_ceilometer.xml102(para)
+msgid ""
+"Create an auto-scaling stack by running the following command. The "
+"<literal>-f</literal> option specifies the name of the stack template file, "
+"and the <literal>-P</literal> option specifies the "
+"<literal>KeyName</literal> parameter as <literal>heat_key</literal>."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_ceilometer.xml108(para)
+msgid "List the heat resources that were created:"
+msgstr "作成された heat リソースを一覧表示します。"
+
+#: ./doc/user-guide/section_cli_ceilometer.xml125(para)
+msgid "List the alarms that are set:"
+msgstr "設定されたアラームを一覧表示します。"
+
+#: ./doc/user-guide/section_cli_ceilometer.xml135(para)
+msgid "List the meters that are set:"
+msgstr "設定されたメーターを一覧表示します。"
+
+#: ./doc/user-guide/section_cli_ceilometer.xml146(para)
+msgid "List samples:"
+msgstr "サンプルを一覧表示します。"
+
+#: ./doc/user-guide/section_cli_ceilometer.xml155(para)
+msgid "View statistics:"
+msgstr "使用状況を表示します。"
+
+#: ./doc/user-guide/app_cheat_sheet.xml7(title)
+msgid "OpenStack command-line interface cheat sheet"
+msgstr "OpenStack コマンドラインインターフェース・チートシート"
+
+#: ./doc/user-guide/app_cheat_sheet.xml9(para)
+msgid ""
+"The following tables give a quick reference of the most used command-line "
+"commands."
+msgstr "以下の表は、よく使われるコマンドの簡単なリファレンスです。"
+
+#: ./doc/user-guide/app_cheat_sheet.xml15(caption)
+msgid "Identity (keystone)"
+msgstr "Identity (keystone)"
+
+#: ./doc/user-guide/app_cheat_sheet.xml21(th)
+#: ./doc/user-guide/app_cheat_sheet.xml67(th)
+#: ./doc/user-guide/app_cheat_sheet.xml141(th)
+#: ./doc/user-guide/app_cheat_sheet.xml334(th)
+#: ./doc/user-guide/app_cheat_sheet.xml375(th)
+#: ./doc/user-guide/app_cheat_sheet.xml459(th)
+msgid "Command"
+msgstr "コマンド"
+
+#: ./doc/user-guide/app_cheat_sheet.xml26(td)
+msgid "List all users"
+msgstr "すべてのユーザーの一覧表示"
+
+#: ./doc/user-guide/app_cheat_sheet.xml32(td)
+msgid "List Identity service catalog"
+msgstr "Identity サービスカタログの一覧表示"
+
+#: ./doc/user-guide/app_cheat_sheet.xml38(td)
+msgid "List all services in service catalog"
+msgstr "サービスカタログにある全サービスの一覧表示"
+
+#: ./doc/user-guide/app_cheat_sheet.xml44(td)
+msgid "Create new user"
+msgstr "新しいユーザーの作成"
+
+#: ./doc/user-guide/app_cheat_sheet.xml46(replaceable)
+#: ./doc/user-guide/app_cheat_sheet.xml53(replaceable)
+#: ./doc/user-guide/app_cheat_sheet.xml186(replaceable)
+#: ./doc/user-guide/app_cheat_sheet.xml215(replaceable)
+#: ./doc/user-guide/app_cheat_sheet.xml222(replaceable)
+#: ./doc/user-guide/app_cheat_sheet.xml228(replaceable)
+#: ./doc/user-guide/app_cheat_sheet.xml234(replaceable)
+#: ./doc/user-guide/app_cheat_sheet.xml240(replaceable)
+#: ./doc/user-guide/app_cheat_sheet.xml246(replaceable)
+#: ./doc/user-guide/app_cheat_sheet.xml252(replaceable)
+#: ./doc/user-guide/app_cheat_sheet.xml258(replaceable)
+#: ./doc/user-guide/app_cheat_sheet.xml266(replaceable)
+#: ./doc/user-guide/app_cheat_sheet.xml273(replaceable)
+#: ./doc/user-guide/app_cheat_sheet.xml341(replaceable)
+#: ./doc/user-guide/app_cheat_sheet.xml385(replaceable)
+msgid "NAME"
+msgstr "NAME"
+
+#: ./doc/user-guide/app_cheat_sheet.xml46(replaceable)
+msgid "TENANT"
+msgstr "TENANT"
+
+#: ./doc/user-guide/app_cheat_sheet.xml47(replaceable)
+msgid "EMAIL"
+msgstr "EMAIL"
+
+#: ./doc/user-guide/app_cheat_sheet.xml47(replaceable)
+msgid "BOOL"
+msgstr "BOOL"
+
+#: ./doc/user-guide/app_cheat_sheet.xml51(td)
+msgid "Create new tenant"
+msgstr "新しいテナントの作成"
+
+#: ./doc/user-guide/app_cheat_sheet.xml53(replaceable)
+msgid "DESCRIPTION"
+msgstr "DESCRIPTION"
+
+#: ./doc/user-guide/app_cheat_sheet.xml61(caption)
+msgid "Image Service (glance)"
+msgstr "Image Service (glance)"
+
+#: ./doc/user-guide/app_cheat_sheet.xml72(td)
+msgid "List images you can access"
+msgstr "アクセス可能なイメージの一覧表示"
+
+#: ./doc/user-guide/app_cheat_sheet.xml78(td)
+msgid "Delete specified image"
+msgstr "指定したイメージの"
+
+#: ./doc/user-guide/app_cheat_sheet.xml80(replaceable)
+#: ./doc/user-guide/app_cheat_sheet.xml86(replaceable)
+#: ./doc/user-guide/app_cheat_sheet.xml92(replaceable)
+#: ./doc/user-guide/app_cheat_sheet.xml166(replaceable)
+#: ./doc/user-guide/app_cheat_sheet.xml266(replaceable)
+msgid "IMAGE"
+msgstr "IMAGE"
+
+#: ./doc/user-guide/app_cheat_sheet.xml84(td)
+msgid "Describe a specific image"
+msgstr "指定したイメージの詳細表示"
+
+#: ./doc/user-guide/app_cheat_sheet.xml90(td)
+msgid "Update image"
+msgstr "イメージの更新"
+
+#: ./doc/user-guide/app_cheat_sheet.xml96(th)
+#: ./doc/user-guide/section_sdk_manage_images.xml7(title)
+msgid "Manage images"
+msgstr "イメージの管理"
+
+#: ./doc/user-guide/app_cheat_sheet.xml99(td)
+msgid "Kernel image"
+msgstr "カーネルイメージ"
+
+#: ./doc/user-guide/app_cheat_sheet.xml107(td)
+msgid "RAM image"
+msgstr "RAM イメージ"
+
+#: ./doc/user-guide/app_cheat_sheet.xml115(td)
+msgid "Three-part image"
+msgstr "3 分割イメージ"
+
+#: ./doc/user-guide/app_cheat_sheet.xml124(td)
+msgid "Register raw image"
+msgstr "raw イメージの登録"
+
+#: ./doc/user-guide/app_cheat_sheet.xml135(caption)
+msgid "Compute (nova)"
+msgstr "Compute (nova)"
+
+#: ./doc/user-guide/app_cheat_sheet.xml146(td)
+msgid "List instances, notice status of instance"
+msgstr "インスタンス、その状態の一覧表示"
+
+#: ./doc/user-guide/app_cheat_sheet.xml152(td)
+#: ./doc/user-guide/section_sdk_manage_images.xml11(title)
+msgid "List images"
+msgstr "イメージの一覧表示"
+
+#: ./doc/user-guide/app_cheat_sheet.xml158(td)
+msgid "List flavors"
+msgstr "フレーバーの一覧表示"
+
+#: ./doc/user-guide/app_cheat_sheet.xml164(td)
+msgid "Boot an instance using flavor and image names (if names are unique)"
+msgstr "フレーバーとイメージ名 (名前が一意な場合) を用いたインスタンスの起動"
+
+#: ./doc/user-guide/app_cheat_sheet.xml166(replaceable)
+#: ./doc/user-guide/app_cheat_sheet.xml258(replaceable)
+msgid "FLAVOR"
+msgstr "FLAVOR"
+
+#: ./doc/user-guide/app_cheat_sheet.xml166(replaceable)
+msgid "INSTANCE_NAME"
+msgstr "INSTANCE_NAME"
+
+#: ./doc/user-guide/app_cheat_sheet.xml172(td)
+msgid "Login to instance"
+msgstr "インスタンスへのログイン"
+
+#: ./doc/user-guide/app_cheat_sheet.xml175(replaceable)
+msgid "NETNS_NAME"
+msgstr "NETNS_NAME"
+
+#: ./doc/user-guide/app_cheat_sheet.xml175(replaceable)
+msgid "USER"
+msgstr "USER"
+
+#: ./doc/user-guide/app_cheat_sheet.xml175(replaceable)
+msgid "SERVER"
+msgstr "SERVER"
+
+#: ./doc/user-guide/app_cheat_sheet.xml178(para)
+msgid ""
+"Note, in CirrOS the password for user <literal>cirros</literal> is "
+"\"cubswin:)\" without the quotes."
+msgstr "注: CirrOS の <literal>cirros</literal> のパスワードは「cubswin:)」です。"
+
+#: ./doc/user-guide/app_cheat_sheet.xml184(td)
+msgid "Show details of instance"
+msgstr "インスタンスの詳細表示"
+
+#: ./doc/user-guide/app_cheat_sheet.xml191(td)
+msgid "View console log of instance"
+msgstr "インスタンスのコンソールログの表示"
+
+#: ./doc/user-guide/app_cheat_sheet.xml197(td)
+msgid "Set metadata on an instance"
+msgstr "インスタンスのメタデータの設定"
+
+#: ./doc/user-guide/app_cheat_sheet.xml203(td)
+#: ./doc/user-guide/section_dashboard_launch_instances.xml69(title)
+msgid "Create an instance snapshot"
+msgstr "インスタンスのスナップショットの作成"
+
+#: ./doc/user-guide/app_cheat_sheet.xml210(th)
+msgid "Pause, suspend, stop, rescue, resize, rebuild, reboot an instance"
+msgstr "インスタンスの一時停止、休止、停止、レスキュー、リサイズ、再作成、リブート"
+
+#: ./doc/user-guide/app_cheat_sheet.xml213(td)
+msgid "Pause"
+msgstr "一時停止"
+
+#: ./doc/user-guide/app_cheat_sheet.xml220(td)
+msgid "Unpause"
+msgstr "一時停止解除"
+
+#: ./doc/user-guide/app_cheat_sheet.xml226(td)
+msgid "Suspend"
+msgstr "休止"
+
+#: ./doc/user-guide/app_cheat_sheet.xml232(td)
+msgid "Unsuspend"
+msgstr "休止解除"
+
+#: ./doc/user-guide/app_cheat_sheet.xml238(td)
+msgid "Stop"
+msgstr "停止"
+
+#: ./doc/user-guide/app_cheat_sheet.xml244(td)
+msgid "Start"
+msgstr "開始"
+
+#: ./doc/user-guide/app_cheat_sheet.xml250(td)
+msgid "Rescue"
+msgstr "レスキュー"
+
+#: ./doc/user-guide/app_cheat_sheet.xml256(td)
+msgid "Resize"
+msgstr "リサイズ"
+
+#: ./doc/user-guide/app_cheat_sheet.xml264(td)
+msgid "Rebuild"
+msgstr "再作成"
+
+#: ./doc/user-guide/app_cheat_sheet.xml271(td)
+msgid "Reboot"
+msgstr "リブート"
+
+#: ./doc/user-guide/app_cheat_sheet.xml278(td)
+msgid "Inject user data and files into an instance"
+msgstr "ユーザーデータとファイルのインスタンスへの注入"
+
+#: ./doc/user-guide/app_cheat_sheet.xml280(replaceable)
+msgid "FILE"
+msgstr "FILE"
+
+#: ./doc/user-guide/app_cheat_sheet.xml280(replaceable)
+msgid "INSTANCE"
+msgstr "INSTANCE"
+
+#: ./doc/user-guide/app_cheat_sheet.xml284(para)
+msgid ""
+"To validate that the file is there, ssh into the instance, and look in "
+"<filename>/var/lib/cloud</filename> for the file."
+msgstr "ファイルが注入されたことを確認する場合、インスタンスに SSH し、<filename>/var/lib/cloud</filename> にあるファイルを探します。"
+
+#: ./doc/user-guide/app_cheat_sheet.xml290(th)
+msgid ""
+"Inject a keypair into an instance and access the instance with that keypair"
+msgstr "インスタンスへのキーペアの注入、キーペアを用いたインスタンスへのアクセス"
+
+#: ./doc/user-guide/app_cheat_sheet.xml294(td)
+msgid "Create keypair"
+msgstr "キーペアの作成"
+
+#: ./doc/user-guide/app_cheat_sheet.xml301(td)
+msgid "Boot"
+msgstr "起動"
+
+#: ./doc/user-guide/app_cheat_sheet.xml308(td)
+msgid "Use ssh to connect to the instance"
+msgstr "インスタンスに接続するための SSH の利用"
+
+#: ./doc/user-guide/app_cheat_sheet.xml315(th)
+msgid "Manage security groups"
+msgstr "セキュリティグループの管理"
+
+#: ./doc/user-guide/app_cheat_sheet.xml318(td)
+msgid ""
+"Add rules to default security group allowing ping and SSH between instances "
+"in the default security group"
+msgstr "default セキュリティグループでインスタンス間の ping と SSH を許可するルールの default セキュリティグループへの追加"
+
+#: ./doc/user-guide/app_cheat_sheet.xml328(caption)
+msgid "Networking (neutron)"
+msgstr "Networking (neutron)"
+
+#: ./doc/user-guide/app_cheat_sheet.xml339(td)
+#: ./doc/user-guide/section_sdk_neutron.xml98(title)
+msgid "Create network"
+msgstr "ネットワークの作成"
+
+#: ./doc/user-guide/app_cheat_sheet.xml345(td)
+msgid "Create a subnet"
+msgstr "サブネットの作成"
+
+#: ./doc/user-guide/app_cheat_sheet.xml347(replaceable)
+msgid "NETWORK_NAME"
+msgstr "NETWORK_NAME"
+
+#: ./doc/user-guide/app_cheat_sheet.xml347(replaceable)
+#: ./doc/user-guide/section_dashboard_access_and_security.xml78(literal)
+#: ./doc/user-guide/section_dashboard_access_and_security.xml82(guilabel)
+#: ./doc/user-guide/section_dashboard_access_and_security.xml120(literal)
+#: ./doc/user-guide/section_dashboard_access_and_security.xml123(guilabel)
+msgid "CIDR"
+msgstr "CIDR"
+
+#: ./doc/user-guide/app_cheat_sheet.xml352(td)
+msgid "List network and subnet"
+msgstr "ネットワークとサブネットの一覧表示"
+
+#: ./doc/user-guide/app_cheat_sheet.xml359(td)
+msgid "Examine details of network and subnet"
+msgstr "ネットワークとサブネットの詳細表示"
+
+#: ./doc/user-guide/app_cheat_sheet.xml361(replaceable)
+#: ./doc/user-guide/app_cheat_sheet.xml362(replaceable)
+msgid "ID_OR_NAME_OF_NETWORK"
+msgstr "ID_OR_NAME_OF_NETWORK"
+
+#: ./doc/user-guide/app_cheat_sheet.xml369(caption)
+msgid "Block Storage (cinder)"
+msgstr "Block Storage (cinder)"
+
+#: ./doc/user-guide/app_cheat_sheet.xml380(th)
+msgid "Manage volumes and volume snapshots"
+msgstr "ボリュームとボリュームスナップショットの管理"
+
+#: ./doc/user-guide/app_cheat_sheet.xml383(td)
+msgid "Create a new volume"
+msgstr "新しいボリュームの作成"
+
+#: ./doc/user-guide/app_cheat_sheet.xml385(replaceable)
+msgid "SIZE_IN_GB"
+msgstr "SIZE_IN_GB"
+
+#: ./doc/user-guide/app_cheat_sheet.xml390(td)
+msgid "Boot an instance and attach to volume"
+msgstr "インスタンスの起動およびボリュームの接続"
+
+#: ./doc/user-guide/app_cheat_sheet.xml396(td)
+msgid "List volumes, notice status of volume"
+msgstr "ボリューム、その状態の一覧表示"
+
+#: ./doc/user-guide/app_cheat_sheet.xml402(td)
+msgid ""
+"Attach volume to instance after instance is active, and volume is available"
+msgstr "インスタンス起動後、ボリューム作成後のインスタンスへのボリュームの接続"
+
+#: ./doc/user-guide/app_cheat_sheet.xml405(replaceable)
+msgid "INSTANCE_ID"
+msgstr "INSTANCE_ID"
+
+#: ./doc/user-guide/app_cheat_sheet.xml405(replaceable)
+msgid "VOLUME_ID"
+msgstr "VOLUME_ID"
+
+#: ./doc/user-guide/app_cheat_sheet.xml410(th)
+msgid "Manage volumes after login into the instance"
+msgstr "インスタンスへのログイン後のボリュームの管理"
+
+#: ./doc/user-guide/app_cheat_sheet.xml413(td)
+msgid "List storage devices"
+msgstr "ストレージデバイスの一覧表示"
+
+#: ./doc/user-guide/app_cheat_sheet.xml419(td)
+msgid "Make filesystem on volume"
+msgstr "ボリュームのファイルシステムの作成"
+
+#: ./doc/user-guide/app_cheat_sheet.xml425(td)
+msgid "Create a mountpoint"
+msgstr "マウントポイントの作成"
+
+#: ./doc/user-guide/app_cheat_sheet.xml431(td)
+msgid "Mount the volume at the mountpoint"
+msgstr "マウントポイントへのボリュームのマウント"
+
+#: ./doc/user-guide/app_cheat_sheet.xml437(td)
+msgid "Create a file on the volume"
+msgstr "ボリュームへのファイルの作成"
+
+#: ./doc/user-guide/app_cheat_sheet.xml444(td)
+msgid "Unmount the volume"
+msgstr "ボリュームのアンマウント"
+
+#: ./doc/user-guide/app_cheat_sheet.xml453(caption)
+msgid "Object Storage (swift)"
+msgstr "Object Storage (swift)"
+
+#: ./doc/user-guide/app_cheat_sheet.xml464(td)
+msgid "Display information for the account, container, or object"
+msgstr "アカウント、コンテナー、オブジェクトの情報表示"
+
+#: ./doc/user-guide/app_cheat_sheet.xml467(replaceable)
+msgid "ACCOUNT"
+msgstr "ACCOUNT"
+
+#: ./doc/user-guide/app_cheat_sheet.xml468(replaceable)
+#: ./doc/user-guide/section_cli_swift_howto.xml26(replaceable)
+#: ./doc/user-guide/section_cli_swift_howto.xml45(replaceable)
+#: ./doc/user-guide/section_cli_swift_howto.xml94(replaceable)
+#: ./doc/user-guide/section_cli_swift_howto.xml96(replaceable)
+#: ./doc/user-guide/section_cli_swift_howto.xml101(replaceable)
+#: ./doc/user-guide/section_cli_swift_howto.xml115(replaceable)
+#: ./doc/user-guide/section_cli_swift_howto.xml120(replaceable)
+msgid "CONTAINER"
+msgstr "CONTAINER"
+
+#: ./doc/user-guide/app_cheat_sheet.xml469(replaceable)
+msgid "OBJECT"
+msgstr "OBJECT"
+
+#: ./doc/user-guide/app_cheat_sheet.xml473(td)
+msgid "List containers"
+msgstr "コンテナーの一覧表示"
+
+#: ./doc/user-guide/app_cheat_sheet.xml479(td)
+#: ./doc/user-guide/section_dashboard_manage_containers.xml19(title)
+msgid "Create a container"
+msgstr "コンテナーの作成"
+
+#: ./doc/user-guide/app_cheat_sheet.xml481(replaceable)
+#: ./doc/user-guide/app_cheat_sheet.xml487(replaceable)
+#: ./doc/user-guide/app_cheat_sheet.xml500(replaceable)
+#: ./doc/user-guide/app_cheat_sheet.xml506(replaceable)
+msgid "CONTAINER_NAME"
+msgstr "CONTAINER_NAME"
+
+#: ./doc/user-guide/app_cheat_sheet.xml485(td)
+msgid "Upload file to a container"
+msgstr "コンテナーへのファイルのアップロード"
+
+#: ./doc/user-guide/app_cheat_sheet.xml487(replaceable)
+#: ./doc/user-guide/app_cheat_sheet.xml500(replaceable)
+#: ./doc/user-guide/app_cheat_sheet.xml506(replaceable)
+msgid "FILE_NAME"
+msgstr "FILE_NAME"
+
+#: ./doc/user-guide/app_cheat_sheet.xml492(td)
+msgid "List objects in container"
+msgstr "コンテナーにあるオブジェクトの一覧表示"
+
+#: ./doc/user-guide/app_cheat_sheet.xml498(td)
+msgid "Download object from container"
+msgstr "コンテナーからのオブジェクトのダウンロード"
+
+#: ./doc/user-guide/app_cheat_sheet.xml504(td)
+msgid "Upload with chunks, for large file"
+msgstr "チャンク化した大きなファイルのアップロード"
+
+#: ./doc/user-guide/app_cheat_sheet.xml506(replaceable)
+msgid "SIZE"
+msgstr "SIZE"
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml6(title)
+msgid "Create and manage object containers"
+msgstr "オブジェクトコンテナーの作成と管理"
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml8(para)
+msgid ""
+"OpenStack Object Storage provides a distributed, API-accessible storage "
+"platform that can be integrated directly into an application or used to "
+"store any type of file, including VM images, backups, archives, or media "
+"files. In the OpenStack Dashboard, you can only manage containers and "
+"objects."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml13(para)
+msgid ""
+"In OpenStack Object Storage, containers provide storage for objects in a "
+"manner similar to a Windows folder or Linux file directory, though they "
+"cannot be nested. An object in OpenStack consists of the file to be stored "
+"in the container and any accompanying metadata."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml22(para)
+#: ./doc/user-guide/section_dashboard_manage_containers.xml44(para)
+#: ./doc/user-guide/section_dashboard_manage_containers.xml79(para)
+#: ./doc/user-guide/section_dashboard_manage_containers.xml103(para)
+#: ./doc/user-guide/section_dashboard_manage_containers.xml144(para)
+#: ./doc/user-guide/section_dashboard_manage_containers.xml171(para)
+msgid ""
+"Log in to the dashboard, choose a project, and click "
+"<guilabel>Containers</guilabel>."
+msgstr "ダッシュボードにログインし、プロジェクトを選択し、<guilabel>コンテナー</guilabel>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml26(para)
+msgid "Click <guibutton>Create Container</guibutton>."
+msgstr "<guibutton>コンテナーの作成</guibutton>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml29(para)
+msgid ""
+"In the Create Container dialog box, enter a name for the container, and then"
+" click<guibutton>Create Container</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml34(para)
+msgid "You have successfully created a container."
+msgstr "コンテナーが正常に作成されました。"
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml35(para)
+msgid ""
+"To delete a container, click the <guibutton>More</guibutton> button and "
+"select <guilabel>Delete Container</guilabel>."
+msgstr "コンテナーを削除する場合、<guibutton>▼</guibutton>ドロップダウンボタンをクリックし、<guilabel>コンテナーの削除</guilabel>を選択します。"
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml41(title)
+msgid "Upload an object"
+msgstr "オブジェクトのアップロード"
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml48(para)
+#: ./doc/user-guide/section_dashboard_manage_containers.xml83(para)
+#: ./doc/user-guide/section_dashboard_manage_containers.xml107(para)
+#: ./doc/user-guide/section_dashboard_manage_containers.xml148(para)
+#: ./doc/user-guide/section_dashboard_manage_containers.xml175(para)
+msgid "Select the container in which you want to store your object."
+msgstr "オブジェクトを保存したいコンテナーを選択します。"
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml51(para)
+#: ./doc/user-guide/section_dashboard_manage_containers.xml66(para)
+#: ./doc/user-guide/section_dashboard_manage_containers.xml151(para)
+msgid "Click <guibutton>Upload Object</guibutton>."
+msgstr "<guibutton>オブジェクトのアップロード</guibutton>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml52(para)
+#: ./doc/user-guide/section_dashboard_manage_containers.xml152(para)
+msgid ""
+"The Upload Object To Container: <replaceable>&lt;name&gt;</replaceable> "
+"dialog box is displayed. <replaceable>&lt;name&gt;</replaceable> is the name"
+" of the container to which you are uploading the object."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml59(para)
+#: ./doc/user-guide/section_dashboard_manage_containers.xml159(para)
+msgid "Enter a name for the object."
+msgstr "オブジェクトの名前を入力します。"
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml62(para)
+#: ./doc/user-guide/section_dashboard_manage_containers.xml90(para)
+msgid "Browse to and select the file that you want to upload."
+msgstr "アップロードしたいファイルを選択します。"
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml69(para)
+msgid "You have successfully uploaded an object to the container."
+msgstr "オブジェクトをコンテナーに正常にアップロードしました。"
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml70(para)
+#: ./doc/user-guide/section_dashboard_manage_containers.xml97(para)
+msgid ""
+"To delete an object, click the <guibutton>More</guibutton> button and select"
+" <guilabel>Delete Object</guilabel>."
+msgstr "オブジェクトを削除する場合、<guibutton>▼</guibutton>ボタンをクリックし、<guilabel>オブジェクトの削除</guilabel>を選択します。"
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml75(title)
+msgid "Manage an object"
+msgstr "オブジェクトの管理"
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml77(title)
+msgid "To edit an object"
+msgstr "オブジェクトの編集方法"
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml86(para)
+msgid ""
+"Click <guibutton>More</guibutton> and choose <guilabel>Edit</guilabel> from "
+"the dropdown list."
+msgstr "<guibutton>▼</guibutton>をクリックし、ドロップダウンリストから<guilabel>編集</guilabel>を選択します。"
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml87(para)
+msgid "The Edit Object dialog box is displayed."
+msgstr "オブジェクトの編集ダイアログボックスが表示されます。"
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml93(para)
+#: ./doc/user-guide/section_dashboard_manage_containers.xml162(para)
+msgid "Click <guibutton>Update Object</guibutton>."
+msgstr "<guibutton>オブジェクトの更新</guibutton>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml101(title)
+msgid "To copy an object from one container to another"
+msgstr "コンテナーから別のコンテナーへのオブジェクトのコピー方法"
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml110(para)
+msgid ""
+"Click <guibutton>More</guibutton> and choose <guilabel>Copy</guilabel> from "
+"the dropdown list."
+msgstr "<guibutton>▼</guibutton>をクリックし、ドロップダウンリストから<guilabel>コピー</guilabel>を選択します。"
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml114(para)
+msgid "In the Copy Object: launch dialog box, enter the following values:"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml119(para)
+msgid ""
+"<guilabel>Destination Container</guilabel>: Choose the destination container"
+" from the list."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml123(para)
+msgid ""
+"<guilabel>Path</guilabel>: Specify a path in which the new copy should be "
+"stored inside of the selected container."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml128(para)
+msgid ""
+"<guilabel>Destination object name</guilabel>: Enter a name for the object in"
+" the new container."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml136(para)
+msgid "Click <guibutton>Copy Object</guibutton>."
+msgstr "<guibutton>オブジェクトのコピー</guibutton>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml140(title)
+msgid "To create a metadata-only object without a file"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml141(para)
+msgid ""
+"You can create a new object in container without a file available and can "
+"upload the file later when it is ready. This temporary object acts a place-"
+"holder for a new object, and enables the user to share object metadata and "
+"URL info in advance."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml166(title)
+msgid "To create a pseudo-folder"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml167(para)
+msgid ""
+"Pseudo-folders are similar to folders in your desktop operating system. They"
+" are virtual collections defined by a common prefix on the object's name."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml178(para)
+msgid "Click <guibutton>Create Pseudo-folder</guibutton>."
+msgstr "<guibutton>擬似フォルダーの作成</guibutton>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml180(para)
+msgid ""
+"The Create Pseudo-Folder in Container <replaceable>&lt;name&gt; "
+"</replaceable> dialog box is displayed. <replaceable>&lt;name&gt; "
+"</replaceable> is the name of the container to which you are uploading the "
+"object."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml187(para)
+msgid "Enter a name for the pseudo-folder."
+msgstr "擬似フォルダーの名前を入力します。"
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml189(para)
+msgid ""
+"A slash (/) character is used as the delimiter for pseudo-folders in the "
+"Object Store."
+msgstr "スラッシュ (/) 文字がオブジェクトストアの擬似フォルダーの区切り文字として使用されます。"
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml193(para)
+msgid "Click <guibutton>Create</guibutton>."
+msgstr "<guibutton>作成</guibutton>をクリックします。"
+
+#: ./doc/user-guide/section_sdk_auth_glance.xml6(title)
+msgid "Authenticate against an Image Service endpoint"
+msgstr "Image Service エンドポイントへの認証"
+
+#: ./doc/user-guide/section_sdk_auth_glance.xml7(para)
+msgid ""
+"To authenticate against an Image Service endpoint, instantiate a <link "
+"href=\"http://docs.openstack.org/developer/python-"
+"glanceclient/api/glanceclient.v2.client.html#glanceclient.v2.client.Client\">"
+" glanceclient.v2.client.Client</link> object:"
+msgstr "Image Service エンドポイントに認証するために、<link href=\"http://docs.openstack.org/developer/python-glanceclient/api/glanceclient.v2.client.html#glanceclient.v2.client.Client\"> glanceclient.v2.client.Client</link> オブジェクトのインスタンスを生成します。"
+
+#: ./doc/user-guide/ch_dashboard.xml10(title)
+msgid "OpenStack dashboard"
+msgstr "OpenStack Dashboard"
+
+#: ./doc/user-guide/ch_dashboard.xml12(para)
+msgid ""
+"As a cloud end user, you can use the OpenStack dashboard to provision your "
+"own resources within the limits set by administrators. You can modify the "
+"examples provided in this section to create other types and sizes of server "
+"instances."
+msgstr "あなたはクラウドのエンドユーザーとして、OpenStack Dashboard (ダッシュボード) を使用できます。管理者により設定された制限の範囲内で自身のリソースを展開できます。他の種類や大きさのサーバーインスタンスを作成するために、このセクションで提供される例を変更できます。"
+
+#: ./doc/user-guide/section_sdk_auth_keystone.xml6(title)
+msgid "Authenticate against an Identity endpoint"
+msgstr "Identity エンドポイントへの認証"
+
+#: ./doc/user-guide/section_sdk_auth_keystone.xml7(para)
+msgid ""
+"To authenticate against the Identity v2.0 endpoint, instantiate a <link "
+"href=\"http://docs.openstack.org/developer/python-"
+"keystoneclient/api/keystoneclient.v2_0.client.html#keystoneclient.v2_0.client.Client\">"
+" keystoneclient.v_20.client.Client</link> object:"
+msgstr "Identity v2.0 エンドポイントに認証するために、<link href=\"http://docs.openstack.org/developer/python-keystoneclient/api/keystoneclient.v2_0.client.html#keystoneclient.v2_0.client.Client\"> keystoneclient.v_20.client.Client</link> オブジェクトのインスタンスを生成します。"
+
+#: ./doc/user-guide/section_sdk_auth_keystone.xml18(para)
+msgid ""
+"After you instantiate a <classname>Client</classname> object, you can "
+"retrieve the token by accessing its <literal>auth_token</literal> attribute "
+"object:"
+msgstr "<classname>Client</classname> オブジェクトのインスタンスを生成した後、その <literal>auth_token</literal> 属性のオブジェクトにアクセスすることにより、トークンを取得できます。"
+
+#: ./doc/user-guide/section_sdk_auth_keystone.xml24(para)
+msgid ""
+"If the OpenStack cloud is configured to use public-key infrastructure (PKI) "
+"tokens, the Python script output looks something like this:"
+msgstr "OpenStack クラウドが PKI トークンを使用するよう設定されている場合、Python スクリプトの出力は以下のようになるでしょう。"
+
+#: ./doc/user-guide/section_sdk_auth_keystone.xml35(para)
+msgid ""
+"This example shows a subset of a PKI token. A complete token is over 5000 "
+"characters long."
+msgstr "この例は PKI トークンの一部分を示します。完全なトークンは 5000 文字以上です。"
+
+#: ./doc/user-guide/section_sdk_auth_neutron.xml6(title)
+msgid "Authenticate against a Networking endpoint"
+msgstr "Networking エンドポイントへの認証"
+
+#: ./doc/user-guide/section_sdk_auth_neutron.xml7(para)
+msgid ""
+"To authenticate against a Networking endpoint, instantiate a "
+"<classname>neutronclient.v_2_0.client.Client</classname> object:"
+msgstr "Networking エンドポイントに認証するために、<classname>neutronclient.v_2_0.client.Client</classname> オブジェクトのインスタンスを生成します。"
+
+#: ./doc/user-guide/section_sdk_auth_neutron.xml18(para)
+msgid ""
+"You can also authenticate by explicitly specifying the endpoint and token:"
+msgstr "エンドポイントとトークンを明示的に指定して、認証することもできます。"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml10(title)
+#: ./doc/user-guide/section_dashboard_access_and_security.xml6(title)
+#: ./doc/user-guide/section_sdk_configure_instances.xml6(title)
+msgid "Configure access and security for instances"
+msgstr "インスタンスのアクセスとセキュリティの設定"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml12(para)
+msgid ""
+"When you launch a virtual machine, you can inject a <emphasis "
+"role=\"italic\">key pair</emphasis>, which provides SSH access to your "
+"instance. For this to work, the image must contain the <literal>cloud-"
+"init</literal> package."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml16(para)
+msgid ""
+"You create at least one key pair for each project. You can use the key pair "
+"for multiple instances that belong to that project. If you generate a key "
+"pair with an external tool, you can import it into OpenStack."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml19(para)
+msgid ""
+"If an image uses a static root password or a static key setneither is "
+"recommendedyou must not provide a key pair when you launch the instance."
+msgstr "イメージが固定の root パスワードまたは固定のキーセットを使用する場合、どちらも推奨されませんが、インスタンスを起動するためにキーペアを提供する必要がありません。"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml20(para)
+msgid ""
+"A <emphasis role=\"italic\">security group</emphasis> is a named collection "
+"of network access rules that you use to limit the types of traffic that have"
+" access to instances. When you launch an instance, you can assign one or "
+"more security groups to it. If you do not create security groups, new "
+"instances are automatically assigned to the default security group, unless "
+"you explicitly specify a different security group."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml27(para)
+msgid ""
+"The associated <emphasis role=\"italic\">rules</emphasis> in each security "
+"group control the traffic to instances in the group. Any incoming traffic "
+"that is not matched by a rule is denied access by default. You can add rules"
+" to or remove rules from a security group, and you can modify rules for the "
+"default and any other security group."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml33(para)
+msgid ""
+"You can modify the rules in a security group to allow access to instances "
+"through different ports and protocols. For example, you can modify rules to "
+"allow access to instances through SSH, to ping instances, or to allow UDP "
+"traffic; for example, for a DNS server running on an instance. You specify "
+"the following parameters for rules:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml41(para)
+msgid ""
+"<emphasis role=\"bold\">Source of traffic</emphasis>. Enable traffic to "
+"instances from either IP addresses inside the cloud from other group members"
+" or from all IP addresses."
+msgstr "<emphasis role=\"bold\">トラフィックソース</emphasis>。クラウドの IP アドレスから、他のグループメンバーから、あるいは全 IP アドレスからインスタンスへのトラフィックを可能にします。"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml47(para)
+msgid ""
+"<emphasis role=\"bold\">Protocol</emphasis>. Choose TCP for SSH, ICMP for "
+"pings, or UDP."
+msgstr "<emphasis role=\"bold\">プロトコル</emphasis>。SSH には TCP、ping には ICMP、あるいは UDP を選択します。"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml51(para)
+msgid ""
+"<emphasis role=\"bold\">Destination port on virtual machine</emphasis>. "
+"Define a port range. To open a single port only, enter the same value twice."
+" ICMP does not support ports; instead, you enter values to define the codes "
+"and types of ICMP traffic to be allowed."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml58(para)
+msgid "Rules are automatically enforced as soon as you create or modify them."
+msgstr "ルールは、作成または変更後すぐに自動的に有効になります。"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml61(para)
+msgid ""
+"Instances that use the default security group cannot, by default, be "
+"accessed from any IP address outside of the cloud. If you want those IP "
+"addresses to access the instances, you must modify the rules for the default"
+" security group."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml65(para)
+msgid ""
+"You can also assign a floating IP address to a running instance to make it "
+"accessible from outside the cloud. See <xref "
+"linkend=\"manage_ip_addresses\"/>."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml70(title)
+#: ./doc/user-guide/section_dashboard_access_and_security.xml136(title)
+msgid "Add a key pair"
+msgstr "キーペアの追加"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml72(para)
+msgid "You can generate a key pair or upload an existing public key."
+msgstr "キーペアの生成や既存の公開鍵のアップロードが可能です。"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml75(para)
+msgid "To generate a key pair, run the following command:"
+msgstr "キーペアを生成するために、以下のコマンドを実行します。"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml76(replaceable)
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml98(replaceable)
+msgid "KEY_NAME"
+msgstr "KEY_NAME"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml76(replaceable)
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml87(replaceable)
+msgid "MY_KEY"
+msgstr "MY_KEY"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml77(para)
+msgid ""
+"The command generates a key pair with the name that you specify fir "
+"<replaceable>KEY_NAME</replaceable>, writes the private key to the "
+"<filename>.pem</filename> file that you specify, and registers the public "
+"key at the Nova database."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml84(para)
+msgid ""
+"To set the permissions of the <filename>.pem</filename> file so that only "
+"you can read and write to it, run the following command:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml92(title)
+#: ./doc/user-guide/section_dashboard_access_and_security.xml166(title)
+msgid "Import a key pair"
+msgstr "キーペアのインポート"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml95(para)
+msgid ""
+"If you have already generated a key pair and the public key is located at "
+"<filename>~/.ssh/id_rsa.pub</filename>, run the following command to upload "
+"the public key:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml99(para)
+msgid ""
+"The command registers the public key at the Nova database and names the key "
+"pair the name that you specify for "
+"<literal><replaceable>KEY_NAME</replaceable></literal>."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml104(para)
+msgid ""
+"To ensure that the key pair has been successfully imported, list key pairs "
+"as follows:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml111(title)
+#: ./doc/user-guide/section_sdk_configure_instances.xml72(title)
+msgid "Create and manage security groups"
+msgstr "セキュリティグループの作成と管理"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml114(para)
+msgid ""
+"To list the security groups for the current project, including descriptions,"
+" enter the following command:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml119(para)
+msgid ""
+"To create a security group with a specified name and description, enter the "
+"following command:"
+msgstr "指定された名前と説明を持つセキュリティグループを作成するために、以下のコマンドを入力します。"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml122(replaceable)
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml127(replaceable)
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml147(replaceable)
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml157(replaceable)
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml164(replaceable)
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml177(replaceable)
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml184(replaceable)
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml202(replaceable)
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml214(replaceable)
+msgid "SECURITY_GROUP_NAME"
+msgstr "SECURITY_GROUP_NAME"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml122(replaceable)
+msgid "GROUP_DESCRIPTION"
+msgstr "GROUP_DESCRIPTION"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml125(para)
+msgid "To delete a specified group, enter the following command:"
+msgstr "指定されたグループを削除するために、以下のコマンドを入力します。"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml129(para)
+msgid ""
+"You cannot delete the default security group for a project. Also, you cannot"
+" delete a security group that is assigned to a running instance."
+msgstr "プロジェクトの Default のセキュリティグループは削除できません。また、実行中のインスタンスに割り当てられているセキュリティグループも削除できません。"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml138(title)
+#: ./doc/user-guide/section_sdk_configure_instances.xml97(title)
+msgid "Create and manage security group rules"
+msgstr "セキュリティグループのルールの作成と管理"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml140(para)
+msgid ""
+"Modify security group rules with the <placeholder-1/> commands. Before you "
+"begin, source the OpenStack RC file. For details, see <xref "
+"linkend=\"cli_openrc\"/>."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml145(para)
+msgid "To list the rules for a security group, run the following command:"
+msgstr "セキュリティグループのルールを一覧表示するために、以下のコマンドを実行します。"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml150(para)
+msgid ""
+"To allow SSH access to the instances, choose one of the following options:"
+msgstr "インスタンスへの SSH 接続を許可するために、以下のオプションのどれかを選択します。"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml154(para)
+msgid ""
+"Allow access from all IP addresses, specified as IP subnet "
+"<filename>0.0.0.0/0</filename> in CIDR notation:"
+msgstr "CIDR 表記で IP サブネット <filename>0.0.0.0/0</filename> として指定して、すべての IP アドレスからのアクセスを許可します。"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml160(para)
+msgid ""
+"Allow access only from IP addresses from other security groups (source "
+"groups) to access the specified port:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml164(replaceable)
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml184(replaceable)
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml202(replaceable)
+msgid "SOURCE_GROUP_NAME"
+msgstr "SOURCE_GROUP_NAME"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml169(para)
+msgid ""
+"To allow pinging of the instances, choose one of the following options:"
+msgstr "インスタンスへの ping アクセスを許可するには、以下のオプションのどれかを選択します。"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml173(para)
+msgid ""
+"Allow pinging from all IP addresses, specified as IP subnet "
+"<filename>0.0.0.0/0</filename> in CIDR notation:"
+msgstr "CIDR 表記で IP サブネット <filename>0.0.0.0/0</filename> として指定して、すべての IP アドレスからの ping を許可します。"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml177(para)
+msgid "This allows access to all codes and all types of ICMP traffic."
+msgstr "これにより、すべてのコードとすべての種類の ICMP 通信が許可されます。"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml181(para)
+msgid ""
+"Allow only members of other security groups (source groups) to ping "
+"instances:"
+msgstr "他のセキュリティグループ (ソースグループ) のメンバーのみがインスタンスに ping できるようにします。"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml189(para)
+msgid ""
+"To allow access through a UDP port, such as allowing access to a DNS server "
+"that runs on a VM, choose one of the following options:"
+msgstr "仮想マシンで実行する DNS サーバーにアクセスするなど、UDP ポート経由でのアクセスを許可するには、以下のオプションの 1 つを選択します。"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml194(para)
+msgid ""
+"Allow UDP access from IP addresses, specified as IP subnet "
+"<filename>0.0.0.0/0</filename> in CIDR notation:<placeholder-1/>"
+msgstr "CIDR 表記で IP サブネット <filename>0.0.0.0/0</filename> として指定して、すべての IP アドレスからの UDP アクセスを許可します。<placeholder-1/>"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml199(para)
+msgid ""
+"Allow only IP addresses from other security groups (source groups) to access"
+" the specified port:"
+msgstr "他のセキュリティグループからの IP アドレス (ソースグループ) のみが指定したポートにアクセスできるようにします。"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml208(title)
+msgid "Delete a security group"
+msgstr "セキュリティグループの削除"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml209(para)
+msgid ""
+"To delete a security group rule, specify the same arguments that you used to"
+" create the rule."
+msgstr "セキュリティグループのルールを削除するには、ルール作成に使用したものと同じ引数を指定します。"
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml212(para)
+msgid ""
+"For example, to delete the security group rule that permits SSH access from "
+"all IP addresses, run the following command."
+msgstr "例えば、すべての IP アドレスからの SSH アクセスを許可するセキュリティグループルールを削除する場合、以下のコマンドを実行します。"
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml6(title)
+msgid "Manage IP addresses"
+msgstr "IP アドレスの管理"
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml7(para)
+msgid ""
+"Each instance has a private, fixed IP address and can also have a public, or"
+" floating, address. Private IP addresses are used for communication between "
+"instances, and public addresses are used for communication with networks "
+"outside the cloud, including the Internet."
+msgstr "各インスタンスは、プライベートな固定 IP アドレスを持ちます。また、パブリックな Floating IP アドレスも持てます。プライベート IP アドレスは、インスタンス間の通信に使用されます。パブリックアドレスは、インターネットなどのクラウド外のネットワークと通信するために使用されます。"
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml11(para)
+msgid ""
+"When you launch an instance, it is automatically assigned a private IP "
+"address that stays the same until you explicitly terminate the instance. "
+"Rebooting an instance has no effect on the private IP address."
+msgstr "インスタンスを起動すると、プライベート IP アドレスが割り当てられ、インスタンスを明示的に終了するまで、この IP アドレスは変わりません。インスタンスをリブートしても、プライベート IP アドレスには影響はありません。"
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml15(para)
+msgid ""
+"A pool of floating IP addresses, configured by the cloud administrator, is "
+"available in OpenStack Compute. The project quota defines the maximum number"
+" of floating IP addresses that you can allocate to the project. After you "
+"allocate a floating IP address to a project, you can:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml22(para)
+msgid ""
+"Associate the floating IP address with an instance of the project. Only one "
+"floating IP address can be allocated to an instance at any given time."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml26(para)
+msgid "Disassociate a floating IP address from an instance in the project."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml29(para)
+msgid ""
+"Delete a floating IP from the project; deleting a floating IP automatically "
+"deletes that IP's associations."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml34(para)
+msgid "Use the <placeholder-1/> commands to manage floating IP addresses."
+msgstr "Floating IP アドレスを管理するために、<placeholder-1/> コマンドを使用します。"
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml37(title)
+msgid "List floating IP address information"
+msgstr "Floating IP アドレスの情報の表示"
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml40(para)
+msgid "To list all pools that provide floating IP addresses, run:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml48(para)
+msgid ""
+"If this list is empty, the cloud administrator must configure a pool of "
+"floating IP addresses."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml51(para)
+msgid ""
+"To list all floating IP addresses that are allocated to the current project,"
+" run:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml59(para)
+msgid ""
+"For each floating IP address that is allocated to the current project, the "
+"command outputs the floating IP address, the ID for the instance to which "
+"the floating IP address is assigned, the associated fixed IP address, and "
+"the pool from which the floating IP address was allocated."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml67(title)
+msgid "Associate floating IP addresses"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml68(para)
+msgid "You can assign a floating IP address to a project and to an instance."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml71(para)
+msgid ""
+"Run the following command to allocate a floating IP address to the current "
+"project. By default, the floating IP address is allocated from the "
+"<systemitem>public</systemitem> pool. The command outputs the allocated IP "
+"address."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml81(para)
+msgid ""
+"If more than one IP address pool is available, you can specify the pool from"
+" which to allocate the IP address, using the pool's name. For example, to "
+"allocate a floating IP address from the <literal>test</literal> pool, run:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml88(para)
+msgid ""
+"List all project instances with which a floating IP address could be "
+"associated:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml99(para)
+msgid "Associate an IP address with an instance in the project, as follows:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml100(replaceable)
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml118(replaceable)
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml128(replaceable)
+msgid "INSTANCE_NAME_OR_ID"
+msgstr "INSTANCE_NAME_OR_ID"
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml100(replaceable)
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml118(replaceable)
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml128(replaceable)
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml132(replaceable)
+msgid "FLOATING_IP_ADDRESS"
+msgstr "FLOATING_IP_ADDRESS"
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml101(para)
+msgid "For example:"
+msgstr "例えば"
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml105(para)
+msgid "Notice that the instance is now associated with two IP addresses:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml113(para)
+msgid ""
+"After you associate the IP address and configure security group rules for "
+"the instance, the instance is publicly available at the floating IP address."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml115(para)
+msgid ""
+"If an instance is connected to multiple networks, you can associate a "
+"floating IP address with a specific fixed IP address using the optional "
+"<parameter>--fixed-address</parameter> parameter:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml118(replaceable)
+msgid "FIXED_IP_ADDRESS"
+msgstr "FIXED_IP_ADDRESS"
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml124(title)
+msgid "Disassociate floating IP addresses"
+msgstr "Floating IP アドレスの割り当て解除"
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml127(para)
+msgid "Release a floating IP address from an instance, as follows:"
+msgstr "以下のように、Floating IP アドレスをインスタンスから割り当て解除します。"
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml131(para)
+msgid "Release the floating IP address from the current project, as follows:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_floating_ips.xml133(para)
+msgid ""
+"The IP address is returned to the pool of IP addresses that is available for"
+" all projects. If the IP address is still associated with a running "
+"instance, it is automatically disassociated from that instance."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_manage_instances.xml6(title)
+msgid "Manage instances and hosts"
+msgstr "インスタンスとホストの管理"
+
+#: ./doc/user-guide/section_cli_nova_manage_instances.xml7(para)
+msgid ""
+"Instances are virtual machines that run inside the cloud on physical compute"
+" nodes. The Compute service manages instances. A host is the node on which a"
+" group of instances resides."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_manage_instances.xml11(para)
+msgid ""
+"This section describes how to perform the different tasks involved in "
+"instance management, such as adding floating IP addresses, stopping and "
+"starting instances, and terminating instances. This section also discusses "
+"node management tasks."
+msgstr ""
+
+#: ./doc/user-guide/bk-user-guide.xml8(title)
+msgid "OpenStack End User Guide"
+msgstr "OpenStack エンドユーザーガイド"
+
+#: ./doc/user-guide/bk-user-guide.xml9(titleabbrev)
+msgid "End User Guide"
+msgstr "エンドユーザーガイド"
+
+#: ./doc/user-guide/bk-user-guide.xml17(orgname)
+#: ./doc/user-guide/bk-user-guide.xml22(holder)
+msgid "OpenStack Foundation"
+msgstr "OpenStack Foundation"
+
+#: ./doc/user-guide/bk-user-guide.xml21(year)
+msgid "2014"
+msgstr "2014"
+
+#: ./doc/user-guide/bk-user-guide.xml24(releaseinfo)
+msgid "current"
+msgstr "カレント"
+
+#: ./doc/user-guide/bk-user-guide.xml25(productname)
+msgid "OpenStack"
+msgstr "OpenStack"
+
+#: ./doc/user-guide/bk-user-guide.xml29(remark)
+msgid "Copyright details are filled in by the template."
+msgstr "Copyright details are filled in by the template."
+
+#: ./doc/user-guide/bk-user-guide.xml34(para)
+msgid ""
+"OpenStack is an open-source cloud computing platform for public and private "
+"clouds. A series of interrelated projects deliver a cloud infrastructure "
+"solution. This guide shows OpenStack end users how to create and manage "
+"resources in an OpenStack cloud with the OpenStack dashboard and OpenStack "
+"client commands."
+msgstr "OpenStack は、パブリッククラウドやプライベートクラウド向けの、オープンソースのクラウドコンピューティングプラットフォームです。一連の相互に関連するプロジェクトがクラウドインフラストラクチャーソリューションを提供します。このガイドは、OpenStack のユーザーが、OpenStack のダッシュボードやコマンドラインクライアントを用いて、OpenStack クラウドのリソースを作成および管理する方法について説明します。"
+
+#: ./doc/user-guide/bk-user-guide.xml44(date)
+msgid "2014-05-09"
+msgstr "2014-05-09"
+
+#: ./doc/user-guide/bk-user-guide.xml48(para)
+msgid "Add a command line cheat sheet."
+msgstr "コマンドラインのチートシートを追加しました。"
+
+#: ./doc/user-guide/bk-user-guide.xml55(date)
+msgid "2014-04-17"
+msgstr "2014-04-17"
+
+#: ./doc/user-guide/bk-user-guide.xml59(para)
+msgid ""
+"For the Icehouse release, this guide has been updated with changes to the "
+"dashboard plus the moving of the command reference appendix as indicated "
+"below."
+msgstr "このガイドは Icehouse リリース向けに、ダッシュボードを変更しました。また、以下に示したとおり、付録のコマンドリファレンスを移動しました。"
+
+#: ./doc/user-guide/bk-user-guide.xml69(date)
+msgid "2014-01-31"
+msgstr "2014-01-31"
+
+#: ./doc/user-guide/bk-user-guide.xml73(para)
+msgid ""
+"Removed the command reference appendix. This information is now in the <link"
+" href=\"http://docs.openstack.org/cli-"
+"reference/content/\"><citetitle>OpenStack Command-Line Interface "
+"Reference</citetitle></link>."
+msgstr "付録のコマンドリファレンスを削除しました。この情報は現在 <link href=\"http://docs.openstack.org/cli-reference/content/\"><citetitle>OpenStack コマンドラインインターフェースリファレンス</citetitle></link>にあります。"
+
+#: ./doc/user-guide/bk-user-guide.xml83(date)
+msgid "2013-12-30"
+msgstr "2013-12-30"
+
+#: ./doc/user-guide/bk-user-guide.xml87(para)
+msgid "Added the OpenStack Python SDK chapter."
+msgstr "OpenStack Python SDK に関する章を追加しました。"
+
+#: ./doc/user-guide/bk-user-guide.xml94(date)
+msgid "2013-10-17"
+msgstr "2013-10-17"
+
+#: ./doc/user-guide/bk-user-guide.xml98(para)
+msgid "Havana release."
+msgstr "Havana リリース。"
+
+#: ./doc/user-guide/bk-user-guide.xml104(date)
+msgid "2013-08-19"
+msgstr "2013-08-19"
+
+#: ./doc/user-guide/bk-user-guide.xml108(para)
+msgid "Editorial changes."
+msgstr "編集上の変更。"
+
+#: ./doc/user-guide/bk-user-guide.xml114(date)
+msgid "2013-07-29"
+msgstr "2013-07-29"
+
+#: ./doc/user-guide/bk-user-guide.xml118(para)
+msgid "First edition of this document."
+msgstr "このドキュメントの初版。"
+
 #: ./doc/user-guide/section_cli_nova_migrate_instances.xml7(title)
 msgid "Use snapshots to migrate instances"
 msgstr "インスタンス移行のためのスナップショットの使用"
@@ -387,1026 +2920,6 @@ msgid ""
 "instance:"
 msgstr "新しいプロジェクトやクラウド環境で、新しいインスタンスを作成するためにスナップショットを使用します。"
 
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml6(title)
-msgid "Create and manage volumes"
-msgstr "ボリュームの作成と管理"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml8(para)
-msgid ""
-"Volumes are block storage devices that you attach to instances to enable "
-"persistent storage. You can attach a volume to a running instance or detach "
-"a volume and attach it to another instance at any time. You can also create "
-"a snapshot from or delete a volume. Only administrative users can create "
-"volume types."
-msgstr "ボリュームは、永続ストレージを使用するためにインスタンスに接続するブロックストレージデバイスです。ボリュームを稼働中のインスタンスに接続したり切断したりできます。また、いつでも別のインスタンスに接続できます。ボリュームからスナップショットを作成したり、削除したりできます。管理ユーザーのみがボリューム種別を作成できます。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml15(title)
-msgid "Create a volume"
-msgstr "ボリュームの作成"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml18(para)
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml136(para)
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml170(para)
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml212(para)
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml251(para)
-msgid ""
-"Log in to the dashboard, choose a project, and click "
-"<guibutton>Volumes</guibutton>."
-msgstr "ダッシュボードにログインし、プロジェクトを選択し、<guibutton>ボリューム</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml22(para)
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml124(para)
-msgid "Click <guibutton>Create Volume</guibutton>."
-msgstr "<guibutton>ボリュームの作成</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml23(para)
-msgid "In the dialog box that opens, enter or select the following values."
-msgstr "表示されたダイアログボックスで、以下の値を入力または選択します。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml32(guilabel)
-msgid "Volume Name"
-msgstr "ボリューム名"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml36(para)
-msgid "Specify a name for the volume."
-msgstr "ボリュームの名前を指定します。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml43(guilabel)
-#: ./doc/user-guide/section_dashboard_manage_images.xml64(guilabel)
-#: ./doc/user-guide/app_cheat_sheet.xml20(th)
-#: ./doc/user-guide/app_cheat_sheet.xml66(th)
-#: ./doc/user-guide/app_cheat_sheet.xml140(th)
-#: ./doc/user-guide/app_cheat_sheet.xml333(th)
-#: ./doc/user-guide/app_cheat_sheet.xml374(th)
-#: ./doc/user-guide/app_cheat_sheet.xml458(th)
-msgid "Description"
-msgstr "説明"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml47(para)
-msgid "Optionally, provide a brief description for the volume."
-msgstr "オプションとして、ボリュームの簡単な説明を入力します。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml54(guilabel)
-msgid "Type"
-msgstr "種別"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml58(para)
-msgid "Leave this field blank."
-msgstr "この項目は空白にしておきます。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml64(guilabel)
-msgid "Size (GB)"
-msgstr "容量 (GB)"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml68(para)
-msgid "The size of the volume in gigabytes."
-msgstr "ギガバイト単位のボリュームサイズ。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml75(guilabel)
-msgid "Volume Source"
-msgstr "ボリュームソース"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml79(para)
-msgid "Select one of the following options:"
-msgstr "以下のオプションを選択します。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml82(guilabel)
-msgid "No source, empty volume"
-msgstr "ソースを指定しなければ、ボリュームが空になります"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml83(para)
-msgid "Creates an empty volume."
-msgstr "空のボリュームを作成します。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml84(para)
-msgid "An empty volume does not contain a file system or a partition table."
-msgstr "空のボリュームは、ファイルシステムやパーティションテーブルを含みません。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml88(guilabel)
-msgid "Snapshot"
-msgstr "スナップショット"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml89(para)
-msgid ""
-"If you choose this option, a new field for <guilabel>Use snapshot as a "
-"source</guilabel> displays. You can select the snapshot from the list."
-msgstr "このオプションを選択する場合、<guilabel>ソースとしてスナップショットの利用</guilabel>の新項目が表示されます。この一覧からスナップショットを選択できます。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml95(guilabel)
-msgid "Image"
-msgstr "イメージ"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml96(para)
-msgid ""
-"If you choose this option, a new field for <guilabel>Use image as a "
-"source</guilabel> displays. You can select the image from the list."
-msgstr "このオプションを選択する場合、<guilabel>ソースとしてイメージの利用</guilabel>の新項目が表示されます。この一覧からイメージを選択できます。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml99(para)
-msgid ""
-"Select the <guilabel>Availability Zone</guilabel> from the list. By default,"
-" this value is set to the availability zone given by the cloud provider (for"
-" example, <literal>us-west</literal> or <literal>apac-south</literal>). For "
-"some cases, it could be <literal>nova</literal>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml107(guilabel)
-msgid "Volume"
-msgstr "ボリューム"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml108(para)
-msgid ""
-"If you choose this option, a new field for <guilabel>Use volume as a "
-"source</guilabel> displays. You can select the volume from the list."
-msgstr "このオプションを選択する場合、<guilabel>ソースとしてボリュームの利用</guilabel>の新項目が表示されます。この一覧からボリュームを選択できます。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml114(para)
-msgid ""
-"Options to use a snapshot or a volume as the source for a volume are "
-"displayed only if there are existing snapshots or volumes."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml127(para)
-msgid ""
-"The dashboard shows the volume on the <guilabel>Volumes</guilabel> tab."
-msgstr "ダッシュボードの<guilabel>ボリューム</guilabel>タブにボリュームが表示されます。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml131(title)
-msgid "Attach a volume to an instance"
-msgstr "ボリュームのインスタンスへの接続"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml132(para)
-msgid ""
-"After you create one or more volumes, you can attach them to instances. You "
-"can attach a volume to one instance at a time."
-msgstr "ボリュームを作成した後、それらをインスタンスに接続できます。ボリュームは、同時に 1 つのインスタンスに接続できます。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml140(para)
-msgid ""
-"Select the volume to add to an instance and click <guibutton>Edit "
-"Attachments</guibutton>."
-msgstr "インスタンスに追加するボリュームを選択し、<guibutton>接続の編集</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml144(para)
-msgid ""
-"In the <guilabel>Manage Volume Attachments</guilabel> dialog box, select an "
-"instance."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml148(para)
-msgid ""
-"Enter the name of the device from which the volume is accessible by the "
-"instance."
-msgstr "インスタンスがボリュームにアクセスできる、デバイスの名前を入力します。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml151(para)
-msgid ""
-"The actual device name might differ from the volume name because of "
-"hypervisor settings."
-msgstr "実際のデバイス名は、ハイパーバイザーの設定により、ボリューム名と異なるかもしれません。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml156(para)
-msgid "Click <guibutton>Attach Volume</guibutton>."
-msgstr "<guibutton>ボリュームの接続</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml157(para)
-msgid ""
-"The dashboard shows the instance to which the volume is now attached and the"
-" device name."
-msgstr "ボリュームが接続されたインスタンスとデバイス名がダッシュボードに表示されます。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml161(para)
-msgid ""
-"You can view the status of a volume in the <guilabel>Volumes</guilabel> tab "
-"of the dashboard. The volume is either Available or In-Use."
-msgstr "ダッシュボードの<guilabel>ボリューム</guilabel>にボリュームの状態を表示できます。ボリュームは、利用可能または使用中になります。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml163(para)
-msgid ""
-"Now you can log in to the instance and mount, format, and use the disk."
-msgstr "これでインスタンスにログインでき、ディスクをマウント、フォーマット、利用できます。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml167(title)
-msgid "Detach a volume from an instance"
-msgstr "ボリュームのインスタンスからの切断"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml174(para)
-msgid "Select the volume and click <guibutton>Edit Attachments</guibutton>."
-msgstr "ボリュームを選択し、<guibutton>接続の編集</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml177(para)
-msgid "Click <guibutton>Detach Volume</guibutton> and confirm your changes."
-msgstr "<guibutton>ボリュームの切断</guibutton>をクリックし、変更を確認します。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml181(para)
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml261(para)
-msgid "A message indicates whether the action was successful."
-msgstr "操作が成功したかどうかはメッセージでわかります。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml184(title)
-msgid "Create a snapshot from a volume"
-msgstr "ボリュームからのスナップショットの作成"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml187(para)
-msgid ""
-"Log in to the dashboard, choose a project, and click "
-"<guilabel>Volumes</guilabel>."
-msgstr "ダッシュボードにログインし、プロジェクトを選択し、<guilabel>ボリューム</guilabel>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml191(para)
-msgid "Select a volume from which to create a snapshot."
-msgstr "スナップショットを作成するボリュームを選択します。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml194(para)
-msgid ""
-"From the <guilabel>More</guilabel> list, select <guilabel>Create "
-"Snapshot</guilabel>."
-msgstr "<guilabel>▼</guilabel>リストから、<guilabel>スナップショットの作成</guilabel>を選択します。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml198(para)
-msgid ""
-"In the dialog box that opens, enter a snapshot name and a brief description."
-msgstr "開いたダイアログボックスで、スナップショットの名前と簡単な説明を入力します。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml202(para)
-msgid "Confirm your changes."
-msgstr "変更を確認します。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml203(para)
-msgid ""
-"The dashboard shows the new volume snapshot in <guilabel>Volume "
-"Snapshots</guilabel> tab."
-msgstr "ダッシュボードの<guilabel>ボリュームのスナップショット</guilabel>に新しいボリュームのスナップショットが表示されます。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml209(title)
-msgid "Edit a volume"
-msgstr "ボリュームの編集"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml216(para)
-#: ./doc/user-guide/section_dashboard_manage_images.xml36(para)
-#: ./doc/user-guide/section_dashboard_manage_images.xml162(para)
-#: ./doc/user-guide/section_dashboard_manage_images.xml209(para)
-msgid ""
-"From the <guilabel>CURRENT PROJECT</guilabel> on the "
-"<guilabel>Project</guilabel> tab, select the appropriate project."
-msgstr "<guilabel>プロジェクト</guilabel>タブの<guilabel>現在のプロジェクト</guilabel>から、適切なプロジェクトを選択します。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml221(para)
-msgid ""
-"On the <guilabel>Project</guilabel> tab, click <guilabel>Volumes</guilabel>."
-msgstr "<guilabel>プロジェクト</guilabel> タブで、<guilabel>ボリューム</guilabel>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml225(para)
-#: ./doc/user-guide/section_dashboard_manage_images.xml171(para)
-msgid "Select the image that you want to edit."
-msgstr "編集したいイメージを選択します。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml228(para)
-msgid ""
-"In the <guilabel>Actions</guilabel> column, click <guilabel>Edit "
-"Volume</guilabel>."
-msgstr "<guilabel>操作</guilabel>の列で、<guilabel>ボリュームの編集</guilabel>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml232(para)
-msgid ""
-"In the <guilabel>Edit Volume</guilabel> dialog box, update the name and "
-"description of the image."
-msgstr "<guilabel>ボリュームの編集</guilabel>ダイアログボックスで、イメージの名前と説明を更新します。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml236(para)
-msgid "Click <guibutton>Edit Volume</guibutton>."
-msgstr "<guibutton>ボリュームの編集</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml240(para)
-msgid ""
-"You can extend a volume by using the <guilabel>Extend Volume</guilabel> "
-"option available in the <guibutton>More</guibutton> dropdown list and "
-"entering the new value for volume size."
-msgstr "<guibutton>▼</guibutton>ドロップダウンリストから利用できる、<guilabel>ボリュームの拡張</guilabel>を使用し、新しいボリュームサイズ値を入力して、ボリュームを拡張できます。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml246(title)
-msgid "Delete a volume"
-msgstr "ボリュームの削除"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml247(para)
-msgid ""
-"When you delete an instance, the data in its attached volumes is not "
-"destroyed."
-msgstr "インスタンスの削除時、接続されたボリュームのデータは無くなりません。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml255(para)
-msgid "Select the check boxes for the volumes that you want to delete."
-msgstr "削除したいボリュームのチェックボックスを選択します。"
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml259(para)
-msgid "Click <guibutton>Delete Volumes</guibutton> and confirm your choice."
-msgstr "<guibutton>ボリュームの切断</guibutton>をクリックし、選択内容を確認します。"
-
-#: ./doc/user-guide/section_sdk_manage_images.xml7(title)
-#: ./doc/user-guide/app_cheat_sheet.xml96(th)
-msgid "Manage images"
-msgstr "イメージの管理"
-
-#: ./doc/user-guide/section_sdk_manage_images.xml8(para)
-msgid ""
-"When working with images in the SDK, you will call both "
-"<literal>glance</literal> and <literal>nova</literal> methods."
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_manage_images.xml11(title)
-#: ./doc/user-guide/app_cheat_sheet.xml152(td)
-msgid "List images"
-msgstr "イメージの一覧表示"
-
-#: ./doc/user-guide/section_sdk_manage_images.xml12(para)
-msgid ""
-"To list the available images, call the "
-"<methodname>glanceclient.v2.images.Controller.list</methodname> method:"
-msgstr "利用可能なイメージを一覧表示するために、<methodname>glanceclient.v2.images.Controller.list</methodname> メソッドを呼び出します。"
-
-#: ./doc/user-guide/section_sdk_manage_images.xml18(para)
-msgid ""
-"The <methodname>images</methodname> method returns a Python generator, as "
-"shown in the following interaction with the Python interpreter:"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_manage_images.xml77(title)
-msgid "Get image by ID"
-msgstr "ID によるイメージの取得"
-
-#: ./doc/user-guide/section_sdk_manage_images.xml78(para)
-msgid ""
-"To retrieve an image object from its ID, call the <methodname> "
-"glanceclient.v2.images.Controller.get</methodname> method:"
-msgstr "ID からイメージオブジェクトを取得するために、<methodname> glanceclient.v2.images.Controller.get</methodname> メソッドを呼び出します。"
-
-#: ./doc/user-guide/section_sdk_manage_images.xml88(title)
-msgid "Get image by name"
-msgstr "名前によるイメージの取得"
-
-#: ./doc/user-guide/section_sdk_manage_images.xml89(para)
-msgid ""
-"The Image Service Python bindings do not support the retrieval of an image "
-"object by name. However, the Compute Python bindings enable you to get an "
-"image object by name. To get an image object by name, call the <methodname> "
-"novaclient.v1_1.images.ImageManager.find</methodname> method:"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_manage_images.xml101(title)
-#: ./doc/user-guide/section_dashboard_manage_images.xml28(title)
-msgid "Upload an image"
-msgstr "イメージのアップロード"
-
-#: ./doc/user-guide/section_sdk_manage_images.xml102(para)
-msgid ""
-"To upload an image, call the <methodname> "
-"glanceclient.v2.images.ImageManager.create</methodname> method:"
-msgstr "イメージをアップロードするために、<methodname> glanceclient.v2.images.ImageManager.create</methodname> メソッドを呼び出します。"
-
-#: ./doc/user-guide/section_cli_heat.xml8(title)
-msgid "Create and manage stacks"
-msgstr "スタックの管理と作成"
-
-#: ./doc/user-guide/section_cli_heat.xml9(para)
-msgid ""
-"The Orchestration module enables you to orchestrate multiple composite cloud"
-" applications. This module supports use of both the Amazon Web Services "
-"(AWS) CloudFormation template format through both a Query API that is "
-"compatible with CloudFormation and the native OpenStack <glossterm>Heat "
-"Orchestration Template (HOT)</glossterm> format through a REST API."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml14(para)
-#: ./doc/user-guide/section_dashboard_stacks.xml16(para)
-msgid ""
-"These flexible template languages enable application developers to describe "
-"and automate the deployment of infrastructure, services, and applications. "
-"The templates enable creation of most OpenStack resource types, such as "
-"instances, floating IP addresses, volumes, security groups, and users. The "
-"resources, once created, are referred to as stacks."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml19(para)
-#: ./doc/user-guide/section_dashboard_stacks.xml23(para)
-msgid ""
-"The template languages are described in <link "
-"href=\"http://docs.openstack.org/developer/heat/template_guide/index.html\">the"
-" Template Guide</link> in the <link "
-"href=\"http://docs.openstack.org/developer/heat/\">Heat developer "
-"documentation</link>."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml25(title)
-msgid "Create a stack from an example template file"
-msgstr "サンプルテンプレートファイルからのスタックの作成"
-
-#: ./doc/user-guide/section_cli_heat.xml28(para)
-msgid ""
-"To create a stack, or template, from an <link "
-"href=\"https://github.com/openstack/heat-templates\">example template "
-"file</link>, run the following command:"
-msgstr "<link href=\"https://github.com/openstack/heat-templates\">サンプルテンプレートファイル</link>からスタックまたはテンプレートを作成するために、以下のコマンドを実行します。"
-
-#: ./doc/user-guide/section_cli_heat.xml32(replaceable)
-#: ./doc/user-guide/section_cli_heat.xml59(replaceable)
-msgid "PATH_TO_HEAT_TEMPLATES"
-msgstr "PATH_TO_HEAT_TEMPLATES"
-
-#: ./doc/user-guide/section_cli_heat.xml33(replaceable)
-msgid "USERNAME"
-msgstr "USERNAME"
-
-#: ./doc/user-guide/section_cli_heat.xml33(replaceable)
-#: ./doc/user-guide/app_cheat_sheet.xml47(replaceable)
-msgid "PASSWORD"
-msgstr "PASSWORD"
-
-#: ./doc/user-guide/section_cli_heat.xml33(replaceable)
-msgid "HEAT_KEY"
-msgstr "HEAT_KEY"
-
-#: ./doc/user-guide/section_cli_heat.xml34(para)
-msgid ""
-"The <literal>--parameters</literal> values that you specify depend on the "
-"parameters that are defined in the template. If a website hosts the template"
-" file, you can specify the URL with the <literal>--template-url</literal> "
-"parameter instead of the <literal>--template-file</literal> parameter."
-msgstr "指定する <literal>--parameters</literal> の値は、テンプレートで定義したパラメーターに依存します。ウェブサイトがテンプレートファイルを公開している場合、<literal>--template-file</literal> パラメーターの代わりに <literal>--template-url</literal> パラメーターを用いて URL を指定できます。"
-
-#: ./doc/user-guide/section_cli_heat.xml40(para)
-msgid "The command returns the following output:"
-msgstr "このコマンドは以下の出力を返します。"
-
-#: ./doc/user-guide/section_cli_heat.xml48(para)
-msgid ""
-"You can also use the <placeholder-1/> command to validate a template file "
-"without creating a stack from it."
-msgstr "テンプレートファイルからスタックを作成することなく、検証するために <placeholder-1/> コマンドを使用することもできます。"
-
-#: ./doc/user-guide/section_cli_heat.xml52(para)
-msgid ""
-"Previous versions of the heat client used <placeholder-1/> instead of "
-"<placeholder-2/>, but it has been deprecated in favor of <placeholder-3/>."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml58(para)
-msgid "To do so, run the following command:"
-msgstr "そうするために、以下のコマンドを実行します。"
-
-#: ./doc/user-guide/section_cli_heat.xml60(para)
-msgid "If validation fails, the response returns an error message."
-msgstr "検証に失敗した場合、応答がエラーメッセージを返します。"
-
-#: ./doc/user-guide/section_cli_heat.xml66(title)
-msgid "Get information about stacks"
-msgstr "スタック情報の取得"
-
-#: ./doc/user-guide/section_cli_heat.xml67(para)
-msgid ""
-"To explore the state and history of a particular stack, you can run a number"
-" of commands."
-msgstr "特定のスタックの状態と履歴を調査するために、いろいろなコマンドを実行できます。"
-
-#: ./doc/user-guide/section_cli_heat.xml71(para)
-msgid ""
-"To see which stacks are visible to the current user, run the following "
-"command:"
-msgstr "どのスタックが現在のユーザーから参照できるかを確認するために、以下のコマンドを実行します。"
-
-#: ./doc/user-guide/section_cli_heat.xml82(para)
-msgid "To show the details of a stack, run the following command:"
-msgstr "スタックの詳細を表示するために、以下のコマンドを実行します。"
-
-#: ./doc/user-guide/section_cli_heat.xml87(para)
-msgid ""
-"A stack consists of a collection of resources. To list the resources and "
-"their status, run the following command:"
-msgstr "スタックはリソースの集合から構成されます。リソースとその状態を一覧表示するために、以下のコマンドを実行します。"
-
-#: ./doc/user-guide/section_cli_heat.xml97(para)
-msgid ""
-"To show the details for a specific resource in a stack, run the following "
-"command:"
-msgstr "スタックにある特定のリソースの詳細を表示するために、以下のコマンドを実行します。"
-
-#: ./doc/user-guide/section_cli_heat.xml100(para)
-msgid ""
-"Some resources have associated metadata which can change throughout the life"
-" cycle of a resource. Show the metadata by running the following command:"
-msgstr "いくつかのリソースはリソースのライフサイクルを通して変更できるメタデータと関連づけられています。以下のコマンドを実行して、メタデータを表示します。"
-
-#: ./doc/user-guide/section_cli_heat.xml105(para)
-msgid ""
-"A series of events is generated during the life cycle of a stack. To display"
-" life cycle events, run the following command::"
-msgstr "一連のイベントはスタックのライフサイクルを通して生成されます。ライフサイクルイベントを表示するために、以下のコマンドを実行します。"
-
-#: ./doc/user-guide/section_cli_heat.xml116(para)
-msgid "To show the details for a particular event, run the following command:"
-msgstr "特定のイベントの詳細を表示するために、以下のコマンドを実行します。"
-
-#: ./doc/user-guide/section_cli_heat.xml123(title)
-msgid "Update a stack"
-msgstr "スタックの更新"
-
-#: ./doc/user-guide/section_cli_heat.xml124(para)
-msgid ""
-"To update an existing stack from a modified template file, run a command "
-"like the following command:"
-msgstr "修正したテンプレートファイルから既存のスタックを更新する場合、以下のようなコマンドを実行します。"
-
-#: ./doc/user-guide/section_cli_heat.xml135(para)
-msgid ""
-"Some resources are updated in-place, while others are replaced with new "
-"resources."
-msgstr "いくつかのリソースはすぐに更新され、他のものは新しいリソースで置き換えられます。"
-
-#: ./doc/user-guide/ch_sdk.xml6(title)
-msgid "OpenStack Python SDK"
-msgstr "OpenStack Python SDK"
-
-#: ./doc/user-guide/ch_sdk.xml8(para)
-msgid ""
-"Use the OpenStack Python Software Development Kit (SDK) to write Python "
-"automation scripts that create and manage resources in your OpenStack cloud."
-" The SDK implements Python bindings to the OpenStack API, which enables you "
-"to perform automation tasks in Python by making calls on Python objects "
-"rather than making REST calls directly. All OpenStack command-line tools are"
-" implemented using the Python SDK."
-msgstr "OpenStack クラウドでリソースの作成や管理を自動化する Python ツールを作成するために、OpenStack Python ソフトウェア開発キット (SDK) を使用します。SDK は OpenStack API への Python バインドを実装します。これにより、直接 REST コールを発行する代わりに、Python オブジェクトでコールを発行することにより、Python で自動化タスクを実行できます。すべての OpenStack コマンドラインツールは Python SDK を使用して実装されています。"
-
-#: ./doc/user-guide/ch_sdk.xml15(para)
-msgid "You should also be familiar with:"
-msgstr "以下にも慣れているとよいでしょう。"
-
-#: ./doc/user-guide/ch_sdk.xml18(para)
-msgid "RESTful web services"
-msgstr "RESTful Web サービス"
-
-#: ./doc/user-guide/ch_sdk.xml21(para)
-msgid "HTTP/1.1"
-msgstr "HTTP/1.1"
-
-#: ./doc/user-guide/ch_sdk.xml24(para)
-msgid "JSON and XML data serialization formats"
-msgstr "JSON および XML データシリアライズ形式"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml6(title)
-#: ./doc/user-guide/section_sdk_configure_instances.xml6(title)
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml10(title)
-msgid "Configure access and security for instances"
-msgstr "インスタンスのアクセスとセキュリティの設定"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml8(para)
-msgid ""
-"Before you launch an instance, you should add security group rules to enable"
-" users to ping and use SSH to connect to the instance. To do so, you either "
-"<link href=\"#security_groups_add_rule\">add rules to the default security "
-"group</link> or add a security group with rules."
-msgstr "インスタンスの起動前に、ユーザーがインスタンスに ping と SSH を実行できるよう、セキュリティグループのルールを追加すべきです。そうする場合、<link href=\"#security_groups_add_rule\">default セキュリティグループにルールを追加する</link> か、ルールを持つセキュリティグループを追加します。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml14(para)
-msgid ""
-"Key pairs are SSH credentials that are injected into an instance when it is "
-"launched. To use key pair injection, the image that the instance is based on"
-" must contain the <literal>cloud-init</literal> package. Each project should"
-" have at least one key pair. For more information, see <xref "
-"linkend=\"keypair_add\"/>."
-msgstr "キーペアは、インスタンスの起動時に、インスタンスに注入される SSH クレデンシャルです。キーペアを注入するために、インスタンスがベースとするイメージは、<literal>cloud-init</literal> パッケージを含める必要があります。各プロジェクトは、少なくとも 1 つのキーペアを持つべきです。詳細は <xref linkend=\"keypair_add\"/> を参照してください。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml20(para)
-msgid ""
-"If you have generated a key pair with an external tool, you can import it "
-"into OpenStack. The key pair can be used for multiple instances that belong "
-"to a project. For more information, see <xref "
-"linkend=\"dashboard_import_keypair\"/>."
-msgstr "外部ツールを用いてキーペアを作成しても、OpenStack にインポートできます。キーペアは同じプロジェクトの複数のインスタンスに使用できます。詳細は<xref linkend=\"dashboard_import_keypair\"/>を参照してください。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml25(para)
-msgid ""
-"When an instance is created in OpenStack, it is automatically assigned a "
-"fixed IP address in the network to which the instance is assigned. This IP "
-"address is permanently associated with the instance until the instance is "
-"terminated. However, in addition to the fixed IP address, a floating IP "
-"address can also be attached to an instance. Unlike fixed IP addresses, "
-"floating IP addresses are able to have their associations modified at any "
-"time, regardless of the state of the instances involved."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml35(title)
-msgid "Add a rule to the default security group"
-msgstr "default セキュリティグループへのルールの追加"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml36(para)
-msgid ""
-"This procedure enables SSH and ICMP (ping) access to instances. The rules "
-"apply to all instances within a given project, and should be set for every "
-"project unless there is a reason to prohibit SSH or ICMP access to the "
-"instances."
-msgstr "この手順により、インスタンスに SSH と ICMP (ping) アクセスできるようになります。ルールは、指定されたプロジェクト内のすべてのインスタンスに適用されます。インスタンスへの SSH や ICMP アクセスを禁止する理由がなければ、すべてのプロジェクトに対して設定すべきです。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml41(para)
-msgid ""
-"This procedure can be adjusted as necessary to add additional security group"
-" rules to a project, if your cloud requires them."
-msgstr "この手順は、追加のセキュリティグループのルールをプロジェクトに追加するために、必要に応じて調整できます。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml46(para)
-msgid ""
-"Log in to the dashboard, choose a project, and click <guilabel>Access &amp; "
-"Security</guilabel>. The <guilabel>Security Groups</guilabel> tab shows the "
-"security groups that are available for this project."
-msgstr "ダッシュボードにログインし、プロジェクトを選択し、<guilabel>アクセスとセキュリティ</guilabel>をクリックします。<guilabel>セキュリティグループ</guilabel>タブに、このプロジェクトで利用できるセキュリティグループが表示されます。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml53(para)
-msgid ""
-"Select the <guilabel>default</guilabel> security group and click "
-"<guibutton>Edit Rules</guibutton>."
-msgstr "<guilabel>default</guilabel> セキュリティグループを選択し、<guibutton>ルールの編集</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml58(para)
-msgid "To allow SSH access, click <guibutton>Add Rule</guibutton>."
-msgstr "SSH アクセスを許可するために、<guibutton>ルールの追加</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml62(para)
-#: ./doc/user-guide/section_dashboard_access_and_security.xml105(para)
-msgid "In the Add Rule dialog box, enter the following values:"
-msgstr "ルールの追加ダイアログボックスで、以下の値を入力します。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml69(guilabel)
-#: ./doc/user-guide/section_dashboard_access_and_security.xml111(guilabel)
-msgid "Rule"
-msgstr "ルール"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml71(literal)
-msgid "SSH"
-msgstr "SSH"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml75(guilabel)
-#: ./doc/user-guide/section_dashboard_access_and_security.xml119(guilabel)
-msgid "Remote"
-msgstr "接続相手"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml78(literal)
-#: ./doc/user-guide/section_dashboard_access_and_security.xml82(guilabel)
-#: ./doc/user-guide/section_dashboard_access_and_security.xml120(literal)
-#: ./doc/user-guide/section_dashboard_access_and_security.xml123(guilabel)
-#: ./doc/user-guide/app_cheat_sheet.xml347(replaceable)
-msgid "CIDR"
-msgstr "CIDR"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml84(literal)
-#: ./doc/user-guide/section_dashboard_access_and_security.xml124(literal)
-msgid "0.0.0.0/0"
-msgstr "0.0.0.0/0"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml90(para)
-msgid ""
-"To accept requests from a particular range of IP addresses, specify the IP "
-"address block in the <guilabel>CIDR</guilabel> box."
-msgstr "特定の IP アドレス範囲からのリクエストを許可する場合、<guilabel>CIDR</guilabel> ボックスに IP アドレスブロックを指定します。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml96(para)
-#: ./doc/user-guide/section_dashboard_access_and_security.xml129(para)
-msgid "Click <guibutton>Add</guibutton>."
-msgstr "<guibutton>追加</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml97(para)
-msgid ""
-"Instances will now have SSH port 22 open for requests from any IP address."
-msgstr "インスタンスは、すべての IP アドレスからのリクエストに対して、SSH ポート 22 番をオープンします。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml101(para)
-msgid "To add an ICMP rule, click <guibutton>Add Rule</guibutton>."
-msgstr "ICMP ルールを追加するために、<guibutton>ルールの追加</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml112(literal)
-msgid "All ICMP"
-msgstr "All ICMP"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml115(guilabel)
-msgid "Direction"
-msgstr "方向"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml116(literal)
-msgid "Ingress"
-msgstr "受信"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml130(para)
-msgid "Instances will now accept all incoming ICMP packets."
-msgstr "インスタンスは、すべての ICMP 入力パケットを受け付けます。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml136(title)
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml70(title)
-msgid "Add a key pair"
-msgstr "キーペアの追加"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml137(para)
-msgid "Create at least one key pair for each project."
-msgstr "プロジェクトごとに少なくとも 1 つのキーペアを作成します。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml140(para)
-#: ./doc/user-guide/section_dashboard_access_and_security.xml169(para)
-#: ./doc/user-guide/section_dashboard_access_and_security.xml237(para)
-msgid ""
-"Log in to the dashboard, choose a project, and click <guilabel>Access &amp; "
-"Security</guilabel>."
-msgstr "ダッシュボードにログインし、プロジェクトを選択し、<guilabel>アクセスとセキュリティ</guilabel>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml145(para)
-#: ./doc/user-guide/section_dashboard_access_and_security.xml174(para)
-msgid ""
-"Click the <guilabel>Keypairs</guilabel> tab, which shows the key pairs that "
-"are available for this project."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml150(para)
-msgid "Click <guibutton>Create Keypair</guibutton>."
-msgstr "<guibutton>キーペアの作成</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml154(para)
-msgid ""
-"In the Create Keypair dialog box, enter a name for your key pair, and click "
-"<guibutton>Create Keypair</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml160(para)
-msgid "Respond to the prompt to download the key pair."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml166(title)
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml92(title)
-msgid "Import a key pair"
-msgstr "キーペアのインポート"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml179(para)
-msgid "Click <guibutton>Import Keypair</guibutton>."
-msgstr "<guibutton>キーペアのインポート</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml183(para)
-msgid ""
-"In the Import Keypair dialog box, enter the name of your key pair, copy the "
-"public key into the <guilabel>Public Key</guilabel> box, and then click "
-"<guibutton>Import Keypair</guibutton>."
-msgstr "キーペアのインポートのダイアログボックスで、キーペアの名前を入力します。<guilabel>公開鍵</guilabel>ボックスに公開鍵をコピーします。そして、<guibutton>キーペアのインポート</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml190(para)
-msgid "Save the <filename>*.pem</filename> file locally."
-msgstr "ローカルに <filename>*.pem</filename> ファイルを保存します。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml192(para)
-msgid ""
-"To change its permissions so that only you can read and write to the file, "
-"run the following command:"
-msgstr "あなただけがファイルを読み書きできるようにパーミッションを変更するために、以下のコマンドを実行します。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml195(replaceable)
-#: ./doc/user-guide/section_dashboard_access_and_security.xml211(replaceable)
-msgid "yourPrivateKey"
-msgstr "yourPrivateKey"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml197(para)
-msgid ""
-"If you are using the dashboard from a Windows computer, use PuTTYgen to load"
-" the <filename>*.pem</filename> file and convert and save it as "
-"<filename>*.ppk</filename>. For more information see the <link "
-"href=\"http://winscp.net/eng/docs/ui_puttygen\">WinSCP web page for "
-"PuTTYgen</link>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml209(para)
-msgid "To make the key pair known to SSH, run the <placeholder-1/> command."
-msgstr "キーペアを SSH で利用するために、<placeholder-1/> コマンドを実行します。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml214(para)
-msgid "The Compute database registers the public key of the key pair."
-msgstr "コンピュートのデータベースはキーペアの公開鍵を登録します。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml216(para)
-msgid ""
-"The dashboard lists the key pair on the <guilabel>Access &amp; "
-"Security</guilabel> tab."
-msgstr "ダッシュボードの<guibutton>アクセスとセキュリティ</guibutton>タブにキーペアが一覧表示されます。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml220(title)
-msgid "Allocate a floating IP address to an instance"
-msgstr "インスタンスへの Floating IP アドレスの割り当て"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml221(para)
-msgid ""
-"When an instance is created in OpenStack, it is automatically assigned a "
-"fixed IP address in the network to which the instance is assigned. This IP "
-"address is permanently associated with the instance until the instance is "
-"terminated."
-msgstr "インスタンスを OpenStack に作成したとき、インスタンスに割り当てられるネットワーク上の固定 IP アドレスが自動的に割り当てられます。この IP アドレスは、インスタンスが終了するまで、インスタンスに割り当てられたままです。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml227(para)
-msgid ""
-"However, in addition to the fixed IP address, a floating IP address can also"
-" be attached to an instance. Unlike fixed IP addresses, floating IP "
-"addresses can have their associations modified at any time, regardless of "
-"the state of the instances involved. This procedure details the reservation "
-"of a floating IP address from an existing pool of addresses and the "
-"association of that address with a specific instance."
-msgstr "しかしながら、固定 IP アドレスに加えて、Floating IP アドレスもインスタンスに割り当てられます。固定 IP アドレスと異なり、インスタンスの状態に関わらず、Floating IP アドレスはいつでも割り当てを変更できます。この手順は、既存のアドレスプールから Floating IP を予約し、このアドレスを特定のインスタンスに割り当てることを詳細に説明します。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml241(para)
-msgid ""
-"Click the <guilabel>Floating IPs</guilabel> tab, which shows the floating IP"
-" addresses allocated to instances."
-msgstr "<guilabel>Floating IP</guilabel> タブをクリックします。ここにインスタンスに割り当てられた Floating IP アドレスが表示されます。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml246(para)
-msgid "Click <guibutton>Allocate IP to Project</guibutton>."
-msgstr "<guibutton>Floating IP の確保</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml249(para)
-msgid "Choose the pool from which to pick the IP address."
-msgstr "IP アドレスを確保するプールを選択します。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml253(para)
-msgid "Click <guibutton>Allocate IP</guibutton>."
-msgstr "<guibutton>Floating IP の確保</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml256(para)
-msgid ""
-"In the <guilabel>Floating IPs</guilabel> list, click <guibutton> "
-"Associate</guibutton>."
-msgstr "<guilabel>Floating IP</guilabel> 一覧で、<guibutton>割り当て</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml264(para)
-msgid ""
-"The <guilabel>IP Address</guilabel> field is filled automatically, but you "
-"can add a new IP address by clicking the <guibutton>+</guibutton> button."
-msgstr "<guilabel>IP アドレス</guilabel>の項目は自動的に入力されますが、<guibutton>+</guibutton> ボタンをクリックして、新しい IP アドレスを追加できます。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml271(para)
-msgid ""
-"In the <guilabel>Ports to be associated</guilabel> field, select a port from"
-" the list."
-msgstr "<guilabel>割り当てるポート</guilabel>の項目で、ドロップダウンリストからポートを選択します。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml274(para)
-msgid "The list shows all the instances with their fixed IP addresses."
-msgstr "ドロップダウンに固定 IP アドレスを持つインスタンスがすべて一覧表示されます。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml260(para)
-msgid ""
-"In the Manage Floating IP Associations dialog box, choose the following "
-"options: <placeholder-1/>"
-msgstr "Floating IP の割り当ての管理ダイアログボックスで、以下のオプションを選択します。 <placeholder-1/>"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml281(para)
-msgid "Click <guibutton>Associate</guibutton>."
-msgstr "<guibutton>割り当て</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml285(para)
-msgid ""
-"To disassociate an IP address from an instance, click the "
-"<guibutton>Disassociate</guibutton> button."
-msgstr "IP アドレスをインスタンスから割り当て解除する場合、<guibutton>割り当て解除</guibutton>ボタンをクリックします。"
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml287(para)
-msgid ""
-"To release the floating IP address back into the pool of addresses, click "
-"the <guibutton>More</guibutton> button and select the <guilabel>Release "
-"Floating IP</guilabel> option."
-msgstr "Floating IP アドレスを開放してアドレスプールに戻すために、<guibutton>▼</guibutton>ボタンをクリックし、<guilabel>Floating IP の開放</guilabel>オプションを選択します。"
-
-#: ./doc/user-guide/section_cli_swift_howto.xml6(title)
-msgid "Manage objects and containers"
-msgstr "オブジェクトとコンテナーの管理"
-
-#: ./doc/user-guide/section_cli_swift_howto.xml8(para)
-msgid ""
-"The OpenStack Object Storage service provides the <placeholder-1/> client, "
-"which is a command-line interface (CLI). Use this client to list objects and"
-" containers, upload objects to containers, and download or delete objects "
-"from containers. You can also gather statistics and update metadata for "
-"accounts, containers, and objects."
-msgstr "OpenStack Object Storage は  <placeholder-1/> クライアントを提供します。これはコマンドラインインターフェース (CLI) です。オブジェクトやコンテナーの一覧表示、オブジェクトのコンテナーへのアップロード、オブジェクトのコンテナーからのダウンロードや削除を実行するために、このクライアントを使用します。アカウント、コンテナー、オブジェクトに関する統計情報の収集、メタデータの更新なども実行できます。"
-
-#: ./doc/user-guide/section_cli_swift_howto.xml14(para)
-msgid ""
-"This client is based on the native swift client library, "
-"<literal>client.py</literal>, which seamlessly re-authenticates if the "
-"current token expires during processing, retries operations multiple times, "
-"and provides a processing concurrency of 10."
-msgstr "このクライアントは、ネイティブの swift クライアントライブラリ (<literal>client.py</literal>) をベースとしており、処理中に現在のトークンが失効した場合や、複数回オペレーションを中断した場合、10 個同時に並行処理する場合、シームレスに再認証します。 "
-
-#: ./doc/user-guide/section_cli_swift_howto.xml20(title)
-msgid "Create and manage containers"
-msgstr "コンテナーの作成と管理"
-
-#: ./doc/user-guide/section_cli_swift_howto.xml23(para)
-msgid ""
-"To create a container, run the following command and replace "
-"<replaceable>CONTAINER</replaceable> with the name of your container."
-msgstr "コンテナーを作成するために、以下のコマンドを実行します。<replaceable>CONTAINER</replaceable> をお使いのコンテナーの名前で置き換えます。"
-
-#: ./doc/user-guide/section_cli_swift_howto.xml26(replaceable)
-#: ./doc/user-guide/section_cli_swift_howto.xml45(replaceable)
-#: ./doc/user-guide/section_cli_swift_howto.xml94(replaceable)
-#: ./doc/user-guide/section_cli_swift_howto.xml96(replaceable)
-#: ./doc/user-guide/section_cli_swift_howto.xml101(replaceable)
-#: ./doc/user-guide/section_cli_swift_howto.xml115(replaceable)
-#: ./doc/user-guide/section_cli_swift_howto.xml120(replaceable)
-#: ./doc/user-guide/app_cheat_sheet.xml468(replaceable)
-msgid "CONTAINER"
-msgstr "CONTAINER"
-
-#: ./doc/user-guide/section_cli_swift_howto.xml28(para)
-msgid "To list all containers: run the following command:"
-msgstr "すべてのコンテナーを一覧表示するために、以下のコマンドを実行します。"
-
-#: ./doc/user-guide/section_cli_swift_howto.xml32(para)
-msgid "To check the status of containers, run the following command:"
-msgstr "コンテナーの状態を確認するために、以下のコマンドを実行します。"
-
-#: ./doc/user-guide/section_cli_swift_howto.xml42(para)
-msgid ""
-"You can also use the <placeholder-1/> command with the "
-"<replaceable>ACCOUNT</replaceable> or <replaceable>CONTAINER</replaceable> "
-"names as parameters."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_swift_howto.xml61(title)
-msgid "Manage access"
-msgstr "アクセス権の管理"
-
-#: ./doc/user-guide/section_cli_swift_howto.xml64(para)
-msgid ""
-"Users have roles on accounts. For example, a user with the admin role has "
-"full access to all containers and objects in an account. You can set access "
-"control lists (ACLs) at the container level and support lists for read and "
-"write access, which you set with the <literal>X-Container-Read</literal> and"
-" <literal>X-Container-Write</literal> headers."
-msgstr "ユーザーにはアカウントに対してロールが割り当てられます。例えば、管理者ロールがあると、アカウント内のコンテナーやオブジェクトすべてに完全にアクセスすることができます。 コンテナーレベルでアクセス制御リスト (ACL) を設定できます。読み取り権と書き込み権の一覧表示がサポートされます。<literal>X-Container-Read</literal> と <literal>X-Container-Write</literal> ヘッダーを用いて設定します。"
-
-#: ./doc/user-guide/section_cli_swift_howto.xml70(para)
-msgid ""
-"To give a user read access, use the <placeholder-1/> command with the "
-"<parameter>-r</parameter> parameter. To give a user write access, use the "
-"<parameter>-w</parameter> parameter."
-msgstr "ユーザーに読み取り権を与える場合、<placeholder-1/> コマンドを <parameter>-r</parameter> パラメーターとともに使用します。ユーザーに書きこみ権を与える場合、<parameter>-w</parameter> パラメーターを使用します。"
-
-#: ./doc/user-guide/section_cli_swift_howto.xml73(para)
-msgid ""
-"The following example enables the <literal>testuser</literal> user to read "
-"objects in the container:"
-msgstr "以下の例は、<literal>testuser</literal> ユーザーがコンテナー内でオブジェクトを読み取りできるようにします。 "
-
-#: ./doc/user-guide/section_cli_swift_howto.xml76(para)
-msgid "You can also use this command with a list of users."
-msgstr "また、このコマンドをユーザー一覧とあわせて使用することもできます。"
-
-#: ./doc/user-guide/section_cli_swift_howto.xml79(para)
-msgid ""
-"If you use StaticWeb middleware to enable Object Storage to serve public web"
-" content, use <literal>.r:</literal>, followed by a list of allowed "
-"referrers."
-msgstr "StaticWeb ミドルウェアを使用して Object Storage を有効にし、パブリックの Web コンテンツにサービスを提供する場合、アクセス可能な参照元に対する構文は <literal>.r:</literal> の後に許可済みの参照元の一覧を指定します。 "
-
-#: ./doc/user-guide/section_cli_swift_howto.xml82(para)
-msgid "The following command gives object access to all referring domains:"
-msgstr "以下のコマンドは、参照しているドメインすべてにオブジェクトがアクセスできるようにします。"
-
-#: ./doc/user-guide/section_cli_swift_howto.xml89(title)
-msgid "Manage objects"
-msgstr "オブジェクトの管理"
-
-#: ./doc/user-guide/section_cli_swift_howto.xml92(para)
-msgid "To upload an object to a container, run the following command:"
-msgstr "コンテナーにオブジェクトをアップロードするために、以下のコマンドを実行します。"
-
-#: ./doc/user-guide/section_cli_swift_howto.xml94(replaceable)
-#: ./doc/user-guide/section_cli_swift_howto.xml96(replaceable)
-#: ./doc/user-guide/section_cli_swift_howto.xml101(replaceable)
-#: ./doc/user-guide/section_cli_swift_howto.xml115(replaceable)
-#: ./doc/user-guide/section_cli_swift_howto.xml120(replaceable)
-msgid "OBJECT_FILENAME"
-msgstr "OBJECT_FILENAME"
-
-#: ./doc/user-guide/section_cli_swift_howto.xml95(para)
-msgid "To upload in chunks, for large files, run the following command:"
-msgstr "チャンク化した大きなファイルをアップロードするために、以下のコマンドを実行します。"
-
-#: ./doc/user-guide/section_cli_swift_howto.xml96(replaceable)
-msgid "CHUNK_SIZE"
-msgstr "CHUNK_SIZE"
-
-#: ./doc/user-guide/section_cli_swift_howto.xml99(para)
-msgid "To check the status of the object, run the following command:"
-msgstr "オブジェクトの状態を確認するために、以下のコマンドを実行します。"
-
-#: ./doc/user-guide/section_cli_swift_howto.xml114(para)
-msgid "To list the objects in a container, run the following command:"
-msgstr "コンテナーにあるオブジェクトを一覧表示するために、以下のコマンドを実行します。"
-
-#: ./doc/user-guide/section_cli_swift_howto.xml118(para)
-msgid "To download an object from a container:, run the following command:"
-msgstr "コンテナーからオブジェクトをダウンロードするために、以下のコマンドを実行します。"
-
 #: ./doc/user-guide/section_cli_nova_config-drive.xml10(title)
 msgid "Store metadata on a configuration drive"
 msgstr "コンフィグドライブへのメタデータの保存"
@@ -1699,723 +3212,149 @@ msgid ""
 "drive."
 msgstr "以下の表はコンフィグドライブの全オプションを示します。"
 
-#: ./doc/user-guide/section_sdk_install.xml6(title)
-msgid "Install the OpenStack SDK"
-msgstr "OpenStack SDK のインストール"
+#: ./doc/user-guide/section_dashboard_launch_instances.xml6(title)
+msgid "Launch and manage instances"
+msgstr "インスタンスの起動と管理"
 
-#: ./doc/user-guide/section_sdk_install.xml7(para)
+#: ./doc/user-guide/section_dashboard_launch_instances.xml7(para)
+msgid "Instances are virtual machines that run inside the cloud."
+msgstr "インスタンスはクラウド内で動作する仮想マシンです。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml9(para)
 msgid ""
-"Each OpenStack project has its own Python library. These libraries are "
-"bundled with the command-line clients. For example, the Python bindings for "
-"the Compute API are bundled with the <package>python-novaclient</package> "
-"package."
-msgstr "各 OpenStack プロジェクトは自身の Python ライブラリを持ちます。これらのライブラリはコマンドラインクライアントに同梱されています。たとえば、Compute API の Python バインドは <package>python-novaclient</package> パッケージに同梱されています。"
-
-#: ./doc/user-guide/section_sdk_install.xml11(para)
-msgid ""
-"For details about how to install the clients, see <link "
-"linkend=\"install_clients\">install the OpenStack command-line "
-"clients</link>."
-msgstr "クライアントのインストール方法の詳細は<link linkend=\"install_clients\">OpenStack コマンドラインクライアントのインストール</link>を参照してください。"
-
-#: ./doc/user-guide/section_sdk_auth_neutron.xml6(title)
-msgid "Authenticate against a Networking endpoint"
-msgstr "Networking エンドポイントへの認証"
-
-#: ./doc/user-guide/section_sdk_auth_neutron.xml7(para)
-msgid ""
-"To authenticate against a Networking endpoint, instantiate a "
-"<classname>neutronclient.v_2_0.client.Client</classname> object:"
-msgstr "Networking エンドポイントに認証するために、<classname>neutronclient.v_2_0.client.Client</classname> オブジェクトのインスタンスを生成します。"
-
-#: ./doc/user-guide/section_sdk_auth_neutron.xml18(para)
-msgid ""
-"You can also authenticate by explicitly specifying the endpoint and token:"
-msgstr "エンドポイントとトークンを明示的に指定して、認証することもできます。"
-
-#: ./doc/user-guide/section_sdk_nova.xml6(title)
-msgid "Compute"
-msgstr "コンピュート"
-
-#: ./doc/user-guide/section_sdk_nova.xml8(para)
-msgid ""
-"To use the information in this section, you must be familiar with OpenStack "
-"Compute."
+"You can <link linkend=\"dashboard_launch_instances_from_image\">launch an "
+"instance</link> from the following sources:"
 msgstr ""
 
-#: ./doc/user-guide/section_sdk_nova.xml10(title)
-#: ./doc/user-guide/section_sdk_neutron.xml14(title)
-msgid "Set environment variables"
-msgstr "環境変数の設定"
-
-#: ./doc/user-guide/section_sdk_nova.xml11(para)
+#: ./doc/user-guide/section_dashboard_launch_instances.xml12(para)
 msgid ""
-"To set up environmental variables and authenticate against Compute API "
-"endpoints, see <xref linkend=\"sdk_auth\"/>."
+"Images uploaded to the OpenStack Image Service, as described in <xref "
+"linkend=\"dashboard_manage_images\"/>."
+msgstr "<xref linkend=\"dashboard_manage_images\"/>に記載されているとおり、OpenStack Image Service にアップロードされたイメージ。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml14(para)
+msgid ""
+"Image that you have copied to a persistent volume. The instance launches "
+"from the volume, which is provided by the <systemitem class=\"service"
+"\">cinder-volume</systemitem> API through iSCSI."
 msgstr ""
 
-#: ./doc/user-guide/section_sdk_nova.xml16(title)
-msgid "Get OpenStack credentials (API v2)"
-msgstr "OpenStack クレデンシャルの取得 (API v2)"
+#: ./doc/user-guide/section_dashboard_launch_instances.xml23(title)
+msgid "Connect to your instance by using SSH"
+msgstr "インスタンスへの SSH 接続"
 
-#: ./doc/user-guide/section_sdk_nova.xml17(para)
-msgid "These example use the <code>get_nova_credentials_v2</code> method:"
-msgstr "これらの例は <code>get_nova_credentials_v2</code> メソッドを使用します。"
-
-#: ./doc/user-guide/section_sdk_nova.xml27(para)
-#: ./doc/user-guide/section_sdk_neutron.xml35(para)
-#: ./doc/user-guide/section_sdk_neutron.xml53(para)
+#: ./doc/user-guide/section_dashboard_launch_instances.xml24(para)
 msgid ""
-"This code resides in the <filename>credentials.py</filename> file, which all"
-" samples import."
-msgstr "このコードは <filename>credentials.py</filename> ファイルにあります。すべてのサンプルがこれをインポートします。"
+"To use SSH to connect to your instance, you use the downloaded keypair file."
+msgstr "インスタンスに SSH 接続するために、ダウンロードしたキーペアファイルを使用します。"
 
-#: ./doc/user-guide/section_sdk_nova.xml30(para)
+#: ./doc/user-guide/section_dashboard_launch_instances.xml27(para)
 msgid ""
-"Use the <code>get_nova_credentials_v2()</code> method to populate and get a "
-"dictionary:"
-msgstr ""
+"The user name is <literal>ubuntu</literal> for the Ubuntu cloud images on "
+"TryStack."
+msgstr "TryStack の Ubuntu クラウドイメージのユーザー名は <literal>ubuntu</literal> です。"
 
-#: ./doc/user-guide/section_sdk_nova.xml36(title)
-msgid "List servers (API v2)"
-msgstr "サーバーの一覧表示 (API v2)"
+#: ./doc/user-guide/section_dashboard_launch_instances.xml32(para)
+msgid "Copy the IP address for your instance."
+msgstr "インスタンスの IP アドレスをコピーします。"
 
-#: ./doc/user-guide/section_sdk_nova.xml37(para)
-msgid "The following program lists servers by using the Compute API v2."
-msgstr "以下のプログラムは、Compute API v2 を用いてサーバーを一覧表示します。"
-
-#: ./doc/user-guide/section_sdk_nova.xml40(title)
-msgid "To list servers"
-msgstr "サーバーの一覧表示方法"
-
-#: ./doc/user-guide/section_sdk_nova.xml42(para)
-#: ./doc/user-guide/section_sdk_nova.xml85(para)
-#: ./doc/user-guide/section_sdk_nova.xml162(para)
-#: ./doc/user-guide/section_sdk_nova.xml253(para)
-#: ./doc/user-guide/section_sdk_nova.xml340(para)
-#: ./doc/user-guide/section_sdk_nova.xml401(para)
-#: ./doc/user-guide/section_sdk_nova.xml464(para)
-#: ./doc/user-guide/section_sdk_neutron.xml255(para)
-#: ./doc/user-guide/section_sdk_neutron.xml340(para)
-#: ./doc/user-guide/section_sdk_neutron.xml416(para)
-#: ./doc/user-guide/section_sdk_neutron.xml468(para)
-#: ./doc/user-guide/section_sdk_neutron.xml519(para)
-msgid "Import the following modules:"
-msgstr "以下のモジュールをインポートします。"
-
-#: ./doc/user-guide/section_sdk_nova.xml47(para)
-#: ./doc/user-guide/section_sdk_nova.xml168(para)
+#: ./doc/user-guide/section_dashboard_launch_instances.xml35(para)
 msgid ""
-"Get Nova credentials. See <xref "
-"linkend=\"sdk_compute_get_openstack_credentials_v2\"/>."
-msgstr "Nova クレデンシャルを取得します。<xref linkend=\"sdk_compute_get_openstack_credentials_v2\"/> を参照してください。"
+"Use the <placeholder-1/> command to make a secure connection to the "
+"instance. For example:"
+msgstr "インスタンスにセキュアに接続するために <placeholder-1/> コマンドを使用します。例:"
 
-#: ./doc/user-guide/section_sdk_nova.xml52(para)
-#: ./doc/user-guide/section_sdk_nova.xml96(para)
-#: ./doc/user-guide/section_sdk_nova.xml173(para)
-#: ./doc/user-guide/section_sdk_nova.xml277(para)
-#: ./doc/user-guide/section_sdk_nova.xml360(para)
-#: ./doc/user-guide/section_sdk_nova.xml424(para)
-#: ./doc/user-guide/section_sdk_nova.xml485(para)
-#: ./doc/user-guide/section_sdk_neutron.xml268(para)
+#: ./doc/user-guide/section_dashboard_launch_instances.xml41(para)
+msgid "At the prompt, type <literal>yes</literal>."
+msgstr "プロンプトに <literal>yes</literal> と入力します。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml47(title)
+msgid "Track usage for instances"
+msgstr "インスタンスの使用状況の確認"
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml48(para)
 msgid ""
-"Instantiate the <literal>nova_client</literal> client object by using the "
-"<literal>credentials</literal> dictionary object:"
-msgstr "<literal>credentials</literal> 辞書オブジェクトを使用して、<literal>nova_client</literal> クライアントオブジェクトのインスタンスを生成します。"
+"You can track usage for instances for each project. You can track costs per "
+"month by showing metrics like number of vCPUs, disks, RAM, and uptime for "
+"all your instances."
+msgstr "プロジェクトごとのインスタンスの使用状況を確認できます。すべてのインスタンスの仮想 CPU 数、ディスク、メモリ、起動時間のような測定項目を表示することにより、月ごとのコストを確認できます。"
 
-#: ./doc/user-guide/section_sdk_nova.xml59(para)
+#: ./doc/user-guide/section_dashboard_launch_instances.xml54(para)
 msgid ""
-"List servers by calling <literal>servers.list</literal> on "
-"<literal>nova_client</literal> object:"
-msgstr "<literal>nova_client</literal> オブジェクトの <literal>servers.list</literal> を呼び出し、サーバーを一覧表示します。"
+"Log in to the dashboard, choose a project, and click "
+"<guilabel>Overview</guilabel>."
+msgstr "ダッシュボードにログインし、プロジェクトを選択し、<guibutton>概要</guibutton>をクリックします。"
 
-#: ./doc/user-guide/section_sdk_nova.xml66(title)
-msgid "List servers code listing"
-msgstr "サーバーの一覧表示のコード全体"
-
-#: ./doc/user-guide/section_sdk_nova.xml79(title)
-msgid "Create server (API v2)"
-msgstr "サーバーの作成 (API v2)"
-
-#: ./doc/user-guide/section_sdk_nova.xml80(para)
+#: ./doc/user-guide/section_dashboard_launch_instances.xml58(para)
 msgid ""
-"The following program creates a server (VM) by using the Compute API v2."
-msgstr "以下のプログラムは、Compute API v2 を用いてサーバー (VM) を作成します。"
+"To query the instance usage for a month, select a month and click "
+"<guibutton>Submit</guibutton>."
+msgstr "ある月のインスタンス使用状況を問い合わせるために、月を選択し、<guibutton>送信</guibutton>をクリックします。"
 
-#: ./doc/user-guide/section_sdk_nova.xml83(title)
-msgid "To create a server"
-msgstr "サーバーの作成方法"
-
-#: ./doc/user-guide/section_sdk_nova.xml91(para)
-#: ./doc/user-guide/section_sdk_nova.xml419(para)
-#: ./doc/user-guide/section_sdk_nova.xml480(para)
+#: ./doc/user-guide/section_dashboard_launch_instances.xml63(para)
 msgid ""
-"Get OpenStack credentials. See <xref "
-"linkend=\"sdk_compute_get_openstack_credentials_v2\"/>."
-msgstr "OpenStack クレデンシャルを取得します。<xref linkend=\"sdk_compute_get_openstack_credentials_v2\"/> を参照してください。"
+"To download a summary, click <guibutton>Download CSV Summary</guibutton>."
+msgstr "概要をダウンロードするために、<guibutton>概要 CSV のダウンロード</guibutton>をクリックします。"
 
-#: ./doc/user-guide/section_sdk_nova.xml103(para)
+#: ./doc/user-guide/section_dashboard_launch_instances.xml72(para)
+#: ./doc/user-guide/section_dashboard_launch_instances.xml98(para)
 msgid ""
-"Get the flavor and image to use to create a server. This code uses the "
-"<literal>cirros</literal> image, the <literal>m1.tiny</literal> flavor, and "
-"the <literal>private</literal> network:"
-msgstr ""
+"Log in to the dashboard, choose a project, and click "
+"<guilabel>Instances</guilabel>."
+msgstr "ダッシュボードにログインし、プロジェクトを選択し、<guilabel>インスタンス</guilabel>をクリックします。"
 
-#: ./doc/user-guide/section_sdk_nova.xml113(para)
-msgid "To create the server, use the network, image, and flavor:"
-msgstr "サーバーを作成し、ネットワーク、イメージ、フレーバーを使用する方法:"
+#: ./doc/user-guide/section_dashboard_launch_instances.xml76(para)
+msgid "Select the instance from which to create a snapshot."
+msgstr "スナップショットを作成するインスタンスを選択します。"
 
-#: ./doc/user-guide/section_sdk_nova.xml120(para)
+#: ./doc/user-guide/section_dashboard_launch_instances.xml79(para)
 msgid ""
-"Sleep for five seconds and determine whether the server/vm was created by "
-"calling <literal>nova_client.servers.list()</literal>:"
-msgstr ""
+"In the <guilabel>Actions</guilabel> column, click <guilabel>Create "
+"Snapshot</guilabel>."
+msgstr "<guilabel>操作</guilabel>の列で、<guilabel>スナップショットの作成</guilabel>をクリックします。"
 
-#: ./doc/user-guide/section_sdk_nova.xml130(title)
-msgid "Create server code listing"
-msgstr "サーバーの作成のコード全体"
-
-#: ./doc/user-guide/section_sdk_nova.xml156(title)
-msgid "Delete server (API v2)"
-msgstr "サーバーの削除 (API v2)"
-
-#: ./doc/user-guide/section_sdk_nova.xml157(para)
+#: ./doc/user-guide/section_dashboard_launch_instances.xml83(para)
 msgid ""
-"The following program deletes a server (VM) by using the Compute API v2."
-msgstr "以下のプログラムは、Compute API v2 を用いてサーバー (VM) を削除します。"
+"In the Create Snapshot dialog box, enter a name for the snapshot, and click "
+"<guibutton>Create Snapshot</guibutton>."
+msgstr "スナップショットの作成ダイアログボックスで、スナップショットの名前を入力し、<guibutton>スナップショットの作成</guibutton>をクリックします。"
 
-#: ./doc/user-guide/section_sdk_nova.xml160(title)
-msgid "To delete a server"
-msgstr "サーバーの削除方法"
+#: ./doc/user-guide/section_dashboard_launch_instances.xml85(para)
+msgid "The <guilabel>Images</guilabel> category shows the instance snapshot."
+msgstr "インスタンスのスナップショットが<guilabel>イメージ</guilabel>カテゴリーに表示されます。"
 
-#: ./doc/user-guide/section_sdk_nova.xml180(para)
-msgid "Determine whether the <literal>vm1</literal> server exists:"
-msgstr "<literal>vm1</literal> サーバーが存在するかを確認します。"
-
-#: ./doc/user-guide/section_sdk_nova.xml184(para)
-msgid "List servers: <literal>servers_list</literal>."
-msgstr "サーバー一覧 <literal>servers_list</literal> を取得します。"
-
-#: ./doc/user-guide/section_sdk_nova.xml188(para)
+#: ./doc/user-guide/section_dashboard_launch_instances.xml89(para)
 msgid ""
-"Iterate over <literal>servers_list</literal> and compare name with "
-"<literal>vm1</literal>."
-msgstr "<literal>servers_list</literal> を反復し、名前を <literal>vm1</literal> と比較します。"
+"To launch an instance from the snapshot, select the snapshot and click "
+"<guibutton>Launch</guibutton>. Proceed with <xref "
+"linkend=\"dashboard_launch_instances_from_image\"/>."
+msgstr "スナップショットからインスタンスを起動するために、スナップショットを選択し、<guibutton>起動</guibutton>をクリックします。<xref linkend=\"dashboard_launch_instances_from_image\"/>に進みます。"
 
-#: ./doc/user-guide/section_sdk_nova.xml194(para)
+#: ./doc/user-guide/section_dashboard_launch_instances.xml95(title)
+msgid "Manage an instance"
+msgstr "インスタンスの管理"
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml102(para)
+msgid "Select an instance."
+msgstr "インスタンスを選択します。"
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml105(para)
 msgid ""
-"If true, set the variable name <literal>server_exists</literal> to "
-"<literal>True</literal> and break from the for loop:"
-msgstr "存在すると、<literal>server_exists</literal> 変数が <literal>True</literal> になり、for ループを抜けます。"
+"In the <guilabel>More</guilabel> list in the <guilabel>Actions</guilabel> "
+"column, select the state."
+msgstr "<guilabel>アクション</guilabel>列の<guilabel>▼</guilabel>ドロップダウンリストで状態を選択します。"
 
-#: ./doc/user-guide/section_sdk_nova.xml211(para)
+#: ./doc/user-guide/section_dashboard_launch_instances.xml107(para)
 msgid ""
-"If the server exists, run the <literal>delete</literal> method of the "
-"<literal>nova_client.servers</literal> object:"
-msgstr "サーバーが存在すると、<literal>nova_client.servers</literal> オブジェクトの <literal>delete</literal> メソッドを実行します。"
-
-#: ./doc/user-guide/section_sdk_nova.xml220(title)
-msgid "Delete server code listing"
-msgstr "サーバーの削除のコード全体"
-
-#: ./doc/user-guide/section_sdk_nova.xml247(title)
-msgid "Update server (API v2)"
-msgstr "サーバーの更新 (API v2)"
-
-#: ./doc/user-guide/section_sdk_nova.xml248(para)
-msgid ""
-"The following program updates the name of a server (VM) by using the Compute"
-" API v2."
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_nova.xml251(title)
-msgid "To update a server"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_nova.xml257(para)
-msgid ""
-"<literal>print_server</literal> is a method defined in "
-"<filename>utils.py</filename> and prints the server details as shown in the "
-"code listing below:"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_nova.xml272(para)
-msgid ""
-"Get OpenStack Credentials. See <xref "
-"linkend=\"sdk_compute_get_openstack_credentials_v2\"/>."
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_nova.xml284(para)
-msgid ""
-"Get the server instance using <literal>server_id</literal> and print the "
-"details by calling <literal>print_server</literal> method:"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_nova.xml294(para)
-msgid ""
-"Call <code>server.update</code> on the server object with the new value for "
-"<literal>name</literal> variable:"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_nova.xml300(para)
-msgid "Get the updated instance of the server:"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_nova.xml304(para)
-msgid ""
-"Call <literal>print_server</literal> again to check the update server "
-"details:"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_nova.xml311(title)
-msgid "Update server code listing"
-msgstr "サーバーの更新のコード全体"
-
-#: ./doc/user-guide/section_sdk_nova.xml334(title)
-msgid "List flavors (API v2)"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_nova.xml335(para)
-msgid ""
-"The following program lists flavors and their details by using the Compute "
-"API v2."
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_nova.xml338(title)
-msgid "To list flavors"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_nova.xml344(para)
-msgid ""
-"The <literal>print_flavors</literal> method is defined in "
-"<filename>utils.py</filename> and prints the flavor details:"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_nova.xml355(para)
-msgid ""
-"Get openStack credentials. See <xref "
-"linkend=\"sdk_compute_get_openstack_credentials_v2\"/>."
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_nova.xml367(para)
-msgid ""
-"List flavors by calling <literal>list()</literal> on "
-"<literal>nova_client.flavors</literal> object:"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_nova.xml374(para)
-msgid ""
-"Print the flavor details, id and name by calling "
-"<literal>print_flavors</literal>:"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_nova.xml380(title)
-msgid "List flavors code listing"
-msgstr "フレーバーの一覧表示のコード全体"
-
-#: ./doc/user-guide/section_sdk_nova.xml395(title)
-msgid "List floating IPs (API v2)"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_nova.xml396(para)
-msgid ""
-"The following program lists the floating IPs and their details by using the "
-"Compute API v2."
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_nova.xml399(title)
-msgid "To list floating IPs"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_nova.xml405(para)
-msgid ""
-"The <literal>print_values_ip</literal> method is defined in "
-"<filename>utils.py</filename> and prints the floating_ip object details:"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_nova.xml431(para)
-msgid ""
-"List floating IPs by calling <literal>list()</literal> on "
-"<literal>nova_client.floating_ips</literal> object:"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_nova.xml438(para)
-msgid ""
-"Print the floating IP object details by calling "
-"<literal>print_values_ip</literal>:"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_nova.xml444(title)
-msgid "List floating IPs code listing"
-msgstr "Floating IP の一覧表示のコード全体"
-
-#: ./doc/user-guide/section_sdk_nova.xml458(title)
-msgid "List hosts (API v2)"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_nova.xml459(para)
-msgid "The following program lists the hosts by using the Compute API v2."
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_nova.xml462(title)
-msgid "To list hosts"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_nova.xml468(para)
-msgid ""
-"The <literal>print_hosts</literal> method is defined in "
-"<filename>utils.py</filename> and prints the host object details:"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_nova.xml492(para)
-msgid ""
-"List hosts by calling <literal>list()</literal> on "
-"<literal>nova_client.hosts</literal> object:"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_nova.xml498(para)
-msgid ""
-"Print the host object details by calling "
-"<literal>print_hosts(host_list)</literal>:"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_nova.xml504(title)
-msgid "List hosts code listing"
-msgstr "ホストの一覧表示のコード全体"
-
-#: ./doc/user-guide/section_cli_ceilometer.xml7(title)
-msgid "Measure cloud resources"
-msgstr "クラウドのリソースの測定"
-
-#: ./doc/user-guide/section_cli_ceilometer.xml8(para)
-msgid ""
-"Telemetry measures cloud resources in OpenStack. It collects data related to"
-" billing. Currently, this metering service is available through only the "
-"<placeholder-1/> command-line client."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_ceilometer.xml10(para)
-msgid "To model data, Telemetry uses the following abstractions:"
-msgstr "データをモデル化するために、Telemetry は以下の抽象化を使用します。"
-
-#: ./doc/user-guide/section_cli_ceilometer.xml13(emphasis)
-msgid "Meter"
-msgstr "メーター"
-
-#: ./doc/user-guide/section_cli_ceilometer.xml15(para)
-msgid ""
-"Measures a specific aspect of resource usage, such as the existence of a "
-"running instance, or ongoing performance, such as the CPU utilization for an"
-" instance. Meters exist for each type of resource. For example, a separate "
-"<literal>cpu_util</literal> meter exists for each instance. The life cycle "
-"of a meter is decoupled from the existence of its related resource. The "
-"meter persists after the resource goes away."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_ceilometer.xml25(para)
-msgid "A meter has the following attributes:"
-msgstr "メーターは以下の属性を持ちます。"
-
-#: ./doc/user-guide/section_cli_ceilometer.xml28(para)
-msgid "String name"
-msgstr "名称文字列"
-
-#: ./doc/user-guide/section_cli_ceilometer.xml31(para)
-msgid "A unit of measurement"
-msgstr "測定単位"
-
-#: ./doc/user-guide/section_cli_ceilometer.xml34(para)
-msgid ""
-"A type, which indicates whether values increase monotonically (cumulative), "
-"are interpreted as a change from the previous value (delta), or are stand-"
-"alone and relate only to the current duration (gauge)"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_ceilometer.xml42(emphasis)
-msgid "Sample"
-msgstr "サンプル"
-
-#: ./doc/user-guide/section_cli_ceilometer.xml44(para)
-msgid ""
-"An individual data point that is associated with a specific meter. A sample "
-"has the same attributes as the associated meter, with the addition of time "
-"stamp and value attributes. The value attribute is also known as the sample "
-"<emphasis role=\"italic\">volume</emphasis>."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_ceilometer.xml50(emphasis)
-msgid "Statistic"
-msgstr "統計"
-
-#: ./doc/user-guide/section_cli_ceilometer.xml52(para)
-msgid ""
-"A set of data point aggregates over a time duration. (In contrast, a sample "
-"represents a single data point.) The Telemetry service employs the following"
-" aggregation functions:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_ceilometer.xml56(para)
-msgid ""
-"<emphasis role=\"bold\">count</emphasis>. The number of samples in each "
-"period."
-msgstr "<emphasis role=\"bold\">数量</emphasis>。各期間のサンプル数。"
-
-#: ./doc/user-guide/section_cli_ceilometer.xml61(para)
-msgid ""
-"<emphasis role=\"bold\">max</emphasis>. The maximum number of sample volumes"
-" in each period."
-msgstr "<emphasis role=\"bold\">最大</emphasis>。各期間の最大サンプルボリューム数。"
-
-#: ./doc/user-guide/section_cli_ceilometer.xml66(para)
-msgid ""
-"<emphasis role=\"bold\">min</emphasis>. The minimum number of sample volumes"
-" in each period."
-msgstr "<emphasis role=\"bold\">最小</emphasis>。各期間の最小サンプルボリューム数。"
-
-#: ./doc/user-guide/section_cli_ceilometer.xml71(para)
-msgid ""
-"<emphasis role=\"bold\">avg</emphasis>. The average of sample volumes over "
-"each period."
-msgstr "<emphasis role=\"bold\">平均</emphasis>。各期間の平均サンプルボリューム数。"
-
-#: ./doc/user-guide/section_cli_ceilometer.xml76(para)
-msgid ""
-"<emphasis role=\"bold\">sum</emphasis>. The sum of sample volumes over each "
-"period."
-msgstr "<emphasis role=\"bold\">合計</emphasis>。各期間の合計サンプルボリューム数。"
-
-#: ./doc/user-guide/section_cli_ceilometer.xml84(emphasis)
-msgid "Alarm"
-msgstr "アラーム"
-
-#: ./doc/user-guide/section_cli_ceilometer.xml86(para)
-msgid ""
-"A set of rules that define a monitor and a current state, with edge-"
-"triggered actions associated with target states. Alarms provide user-"
-"oriented Monitoring-as-a-Service and a general purpose utility for "
-"OpenStack. Orchestration auto scaling is a typical use case. Alarms follow a"
-" tristate model of <literal>ok</literal>, <literal>alarm</literal>, and "
-"<literal>insufficient data</literal>. For conventional threshold-oriented "
-"alarms, a static threshold value and comparison operator govern state "
-"transitions. The comparison operator compares a selected meter statistic "
-"against an evaluation window of configurable length into the recent past."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_ceilometer.xml96(para)
-msgid ""
-"This example uses the <placeholder-1/> client to create an auto-scaling "
-"stack and the <placeholder-2/> client to measure resources."
-msgstr "この例は、オートスケールするスタックを作成するために <placeholder-1/> コマンドを使用し、リソースを計測するために <placeholder-2/> クライアントを使用します。"
-
-#: ./doc/user-guide/section_cli_ceilometer.xml102(para)
-msgid ""
-"Create an auto-scaling stack by running the following command. The "
-"<literal>-f</literal> option specifies the name of the stack template file, "
-"and the <literal>-P</literal> option specifies the "
-"<literal>KeyName</literal> parameter as <literal>heat_key</literal>."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_ceilometer.xml108(para)
-msgid "List the heat resources that were created:"
-msgstr "作成された heat リソースを一覧表示します。"
-
-#: ./doc/user-guide/section_cli_ceilometer.xml125(para)
-msgid "List the alarms that are set:"
-msgstr "設定されたアラームを一覧表示します。"
-
-#: ./doc/user-guide/section_cli_ceilometer.xml135(para)
-msgid "List the meters that are set:"
-msgstr "設定されたメーターを一覧表示します。"
-
-#: ./doc/user-guide/section_cli_ceilometer.xml146(para)
-msgid "List samples:"
-msgstr "サンプルを一覧表示します。"
-
-#: ./doc/user-guide/section_cli_ceilometer.xml155(para)
-msgid "View statistics:"
-msgstr "使用状況を表示します。"
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml6(title)
-msgid "Manage IP addresses"
-msgstr "IP アドレスの管理"
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml7(para)
-msgid ""
-"Each instance has a private, fixed IP address and can also have a public, or"
-" floating, address. Private IP addresses are used for communication between "
-"instances, and public addresses are used for communication with networks "
-"outside the cloud, including the Internet."
-msgstr "各インスタンスは、プライベートな固定 IP アドレスを持ちます。また、パブリックな Floating IP アドレスも持てます。プライベート IP アドレスは、インスタンス間の通信に使用されます。パブリックアドレスは、インターネットなどのクラウド外のネットワークと通信するために使用されます。"
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml11(para)
-msgid ""
-"When you launch an instance, it is automatically assigned a private IP "
-"address that stays the same until you explicitly terminate the instance. "
-"Rebooting an instance has no effect on the private IP address."
-msgstr "インスタンスを起動すると、プライベート IP アドレスが割り当てられ、インスタンスを明示的に終了するまで、この IP アドレスは変わりません。インスタンスをリブートしても、プライベート IP アドレスには影響はありません。"
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml15(para)
-msgid ""
-"A pool of floating IP addresses, configured by the cloud administrator, is "
-"available in OpenStack Compute. The project quota defines the maximum number"
-" of floating IP addresses that you can allocate to the project. After you "
-"allocate a floating IP address to a project, you can:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml22(para)
-msgid ""
-"Associate the floating IP address with an instance of the project. Only one "
-"floating IP address can be allocated to an instance at any given time."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml26(para)
-msgid "Disassociate a floating IP address from an instance in the project."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml29(para)
-msgid ""
-"Delete a floating IP from the project; deleting a floating IP automatically "
-"deletes that IP's associations."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml34(para)
-msgid "Use the <placeholder-1/> commands to manage floating IP addresses."
-msgstr "Floating IP アドレスを管理するために、<placeholder-1/> コマンドを使用します。"
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml37(title)
-msgid "List floating IP address information"
-msgstr "Floating IP アドレスの情報の表示"
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml40(para)
-msgid "To list all pools that provide floating IP addresses, run:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml48(para)
-msgid ""
-"If this list is empty, the cloud administrator must configure a pool of "
-"floating IP addresses."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml51(para)
-msgid ""
-"To list all floating IP addresses that are allocated to the current project,"
-" run:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml59(para)
-msgid ""
-"For each floating IP address that is allocated to the current project, the "
-"command outputs the floating IP address, the ID for the instance to which "
-"the floating IP address is assigned, the associated fixed IP address, and "
-"the pool from which the floating IP address was allocated."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml67(title)
-msgid "Associate floating IP addresses"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml68(para)
-msgid "You can assign a floating IP address to a project and to an instance."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml71(para)
-msgid ""
-"Run the following command to allocate a floating IP address to the current "
-"project. By default, the floating IP address is allocated from the "
-"<systemitem>public</systemitem> pool. The command outputs the allocated IP "
-"address."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml81(para)
-msgid ""
-"If more than one IP address pool is available, you can specify the pool from"
-" which to allocate the IP address, using the pool's name. For example, to "
-"allocate a floating IP address from the <literal>test</literal> pool, run:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml88(para)
-msgid ""
-"List all project instances with which a floating IP address could be "
-"associated:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml99(para)
-msgid "Associate an IP address with an instance in the project, as follows:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml100(replaceable)
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml118(replaceable)
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml128(replaceable)
-msgid "INSTANCE_NAME_OR_ID"
-msgstr "INSTANCE_NAME_OR_ID"
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml100(replaceable)
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml118(replaceable)
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml128(replaceable)
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml132(replaceable)
-msgid "FLOATING_IP_ADDRESS"
-msgstr "FLOATING_IP_ADDRESS"
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml101(para)
-msgid "For example:"
-msgstr "例えば"
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml105(para)
-msgid "Notice that the instance is now associated with two IP addresses:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml113(para)
-msgid ""
-"After you associate the IP address and configure security group rules for "
-"the instance, the instance is publicly available at the floating IP address."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml115(para)
-msgid ""
-"If an instance is connected to multiple networks, you can associate a "
-"floating IP address with a specific fixed IP address using the optional "
-"<parameter>--fixed-address</parameter> parameter:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml118(replaceable)
-msgid "FIXED_IP_ADDRESS"
-msgstr "FIXED_IP_ADDRESS"
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml124(title)
-msgid "Disassociate floating IP addresses"
-msgstr "Floating IP アドレスの割り当て解除"
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml127(para)
-msgid "Release a floating IP address from an instance, as follows:"
-msgstr "以下のように、Floating IP アドレスをインスタンスから割り当て解除します。"
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml131(para)
-msgid "Release the floating IP address from the current project, as follows:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_floating_ips.xml133(para)
-msgid ""
-"The IP address is returned to the pool of IP addresses that is available for"
-" all projects. If the IP address is still associated with a running "
-"instance, it is automatically disassociated from that instance."
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_auth_glance.xml6(title)
-msgid "Authenticate against an Image Service endpoint"
-msgstr "Image Service エンドポイントへの認証"
-
-#: ./doc/user-guide/section_sdk_auth_glance.xml7(para)
-msgid ""
-"To authenticate against an Image Service endpoint, instantiate a <link "
-"href=\"http://docs.openstack.org/developer/python-"
-"glanceclient/api/glanceclient.v2.client.html#glanceclient.v2.client.Client\">"
-" glanceclient.v2.client.Client</link> object:"
-msgstr "Image Service エンドポイントに認証するために、<link href=\"http://docs.openstack.org/developer/python-glanceclient/api/glanceclient.v2.client.html#glanceclient.v2.client.Client\"> glanceclient.v2.client.Client</link> オブジェクトのインスタンスを生成します。"
-
-#: ./doc/user-guide/section_sdk_neutron.xml6(title)
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml178(guilabel)
-msgid "Networking"
-msgstr "ネットワーク"
+"You can resize or rebuild an instance. You can also choose to view the "
+"instance console log, edit instance or the security groups. Depending on the"
+" current state of the instance, you can pause, resume, suspend, soft or hard"
+" reboot, or terminate it."
+msgstr "インスタンスのリサイズや再構築をできます。インスタンスのコンソールログを表示するため、インスタンスやセキュリティグループを編集するためにも選択できます。インスタンスの現在の状態によって、インスタンスを一時停止、再開、サスペンド、ソフトリブート、ハードリブート、終了できます。"
+
+#: ./doc/user-guide/ch_cli.xml10(title)
+msgid "OpenStack command-line clients"
+msgstr "OpenStack コマンドラインクライアント"
 
 #: ./doc/user-guide/section_sdk_neutron.xml8(para)
 msgid ""
@@ -2490,11 +3429,6 @@ msgid ""
 "samples import."
 msgstr "このコードは <filename>utils.py</filename> ファイルにあります。すべてのサンプルがこれをインポートします。"
 
-#: ./doc/user-guide/section_sdk_neutron.xml98(title)
-#: ./doc/user-guide/app_cheat_sheet.xml339(td)
-msgid "Create network"
-msgstr "ネットワークの作成"
-
 #: ./doc/user-guide/section_sdk_neutron.xml99(para)
 msgid "The following program creates a network:"
 msgstr "以下のプログラムはネットワークを作成します。"
@@ -2683,6 +3617,51 @@ msgstr "サブネットを一覧表示します。"
 msgid "List subnets: complete code listing"
 msgstr "サブネットの一覧表示: コード全体"
 
+#: ./doc/user-guide/section_sdk_auth_nova.xml6(title)
+msgid "Authenticate against a Compute endpoint"
+msgstr "Compute エンドポイントへの認証"
+
+#: ./doc/user-guide/section_sdk_auth_nova.xml7(para)
+msgid ""
+"To authenticate against a Compute endpoint, instantiate a <link "
+"href=\"http://docs.openstack.org/developer/python-"
+"novaclient/api/novaclient.v1_1.client.html#novaclient.v1_1.client.Client\"> "
+"novaclient.v_1_1.client.Client</link> object:"
+msgstr "Compute エンドポイントに認証するために、<link href=\"http://docs.openstack.org/developer/python-novaclient/api/novaclient.v1_1.client.html#novaclient.v1_1.client.Client\"> novaclient.v_1_1.client.Client</link> オブジェクトのインスタンスを生成します。"
+
+#: ./doc/user-guide/section_sdk_auth_nova.xml18(para)
+msgid ""
+"Alternatively, you can instantiate a "
+"<classname>novaclient.client.Client</classname> object and pass the version "
+"number:"
+msgstr "代わりに、<classname>novaclient.client.Client</classname> オブジェクトのインスタンスを生成し、バージョン番号を渡すこともできます。"
+
+#: ./doc/user-guide/section_sdk_auth_nova.xml28(para)
+msgid ""
+"If you authenticate against an endpoint that uses a custom authentication "
+"back end, you must load the authentication plug-in and pass it to the "
+"constructor."
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_auth_nova.xml31(para)
+msgid ""
+"The Rackspace public cloud is an OpenStack deployment that uses a custom "
+"authentication back end. To authenticate against this cloud, you must "
+"install the <link href=\"https://pypi.python.org/pypi/rackspace-"
+"novaclient/\"> rackspace-novaclient</link> library that contains the "
+"Rackspace authentication plug-in, called <literal>rackspace</literal>. The "
+"following Python code shows the additional modifications required to "
+"instantiate a <classname>Client</classname> object that can authenticate "
+"against the Rackspace custom authentication back end."
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_auth_nova.xml53(para)
+msgid ""
+"If you set the <literal>OS_AUTH_SYSTEM</literal> environment variable, check"
+" for this variable in your Python script to determine whether you need to "
+"load a custom authentication back end:"
+msgstr ""
+
 #: ./doc/user-guide/section_dashboard_stacks.xml6(title)
 msgid "Launch and manage stacks"
 msgstr "スタックの起動と管理"
@@ -2993,266 +3972,812 @@ msgid ""
 "scripts."
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml6(title)
-msgid "Upload and manage images"
-msgstr "イメージのアップロードと管理"
-
-#: ./doc/user-guide/section_dashboard_manage_images.xml7(para)
+#: ./doc/user-guide/section_sdk_manage_images.xml8(para)
 msgid ""
-"A virtual machine image, referred to in this document simply as an image, is"
-" a single file that contains a virtual disk that has a bootable operating "
-"system installed on it. Images are used to create virtual machine instances "
-"within the cloud. For information about creating image files, see the <link "
-"href=\"http://docs.openstack.org/image-guide/content/\"><citetitle>OpenStack"
-" Virtual Machine Image Guide</citetitle></link>."
+"When working with images in the SDK, you will call both "
+"<literal>glance</literal> and <literal>nova</literal> methods."
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml15(para)
+#: ./doc/user-guide/section_sdk_manage_images.xml12(para)
 msgid ""
-"Depending on your role, you may have permission to upload and manage virtual"
-" machine images. Operators might restrict the upload and management of "
-"images to cloud administrators or operators only. If you have the "
-"appropriate privileges, you can use the dashboard to upload and manage "
-"images in the <guilabel>admin</guilabel> project."
+"To list the available images, call the "
+"<methodname>glanceclient.v2.images.Controller.list</methodname> method:"
+msgstr "利用可能なイメージを一覧表示するために、<methodname>glanceclient.v2.images.Controller.list</methodname> メソッドを呼び出します。"
+
+#: ./doc/user-guide/section_sdk_manage_images.xml18(para)
+msgid ""
+"The <methodname>images</methodname> method returns a Python generator, as "
+"shown in the following interaction with the Python interpreter:"
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml22(para)
-msgid ""
-"You can also use the <placeholder-1/> and <placeholder-2/> command-line "
-"clients or the Image Service and Compute APIs to manage images. See <xref "
-"linkend=\"cli_manage_images\"/>."
-msgstr "イメージを管理するために、<placeholder-1/> と <placeholder-2/> コマンドラインクライアントまたは Image Service API と Compute API を使用することもできます。<xref linkend=\"cli_manage_images\"/>を参照してください。"
+#: ./doc/user-guide/section_sdk_manage_images.xml77(title)
+msgid "Get image by ID"
+msgstr "ID によるイメージの取得"
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml29(para)
-msgid "Follow this procedure to upload an image to a project."
+#: ./doc/user-guide/section_sdk_manage_images.xml78(para)
+msgid ""
+"To retrieve an image object from its ID, call the <methodname> "
+"glanceclient.v2.images.Controller.get</methodname> method:"
+msgstr "ID からイメージオブジェクトを取得するために、<methodname> glanceclient.v2.images.Controller.get</methodname> メソッドを呼び出します。"
+
+#: ./doc/user-guide/section_sdk_manage_images.xml88(title)
+msgid "Get image by name"
+msgstr "名前によるイメージの取得"
+
+#: ./doc/user-guide/section_sdk_manage_images.xml89(para)
+msgid ""
+"The Image Service Python bindings do not support the retrieval of an image "
+"object by name. However, the Compute Python bindings enable you to get an "
+"image object by name. To get an image object by name, call the <methodname> "
+"novaclient.v1_1.images.ImageManager.find</methodname> method:"
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml33(para)
-#: ./doc/user-guide/section_dashboard_manage_images.xml159(para)
-#: ./doc/user-guide/section_dashboard_manage_images.xml206(para)
-msgid "Log in to the dashboard."
-msgstr "ダッシュボードにログインします。"
-
-#: ./doc/user-guide/section_dashboard_manage_images.xml41(para)
-#: ./doc/user-guide/section_dashboard_manage_images.xml167(para)
-#: ./doc/user-guide/section_dashboard_manage_images.xml213(para)
+#: ./doc/user-guide/section_sdk_manage_images.xml102(para)
 msgid ""
-"On the <guilabel>Project</guilabel> tab, click <guilabel>Images</guilabel>."
-msgstr "<guilabel>プロジェクト</guilabel> タブで、<guilabel>イメージ</guilabel>をクリックします。"
+"To upload an image, call the <methodname> "
+"glanceclient.v2.images.ImageManager.create</methodname> method:"
+msgstr "イメージをアップロードするために、<methodname> glanceclient.v2.images.ImageManager.create</methodname> メソッドを呼び出します。"
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml45(para)
-#: ./doc/user-guide/section_dashboard_manage_images.xml148(para)
-msgid "Click <guibutton>Create Image</guibutton>."
-msgstr "<guibutton>イメージの作成</guibutton>をクリックします。"
+#: ./doc/user-guide/section_sdk_install.xml6(title)
+msgid "Install the OpenStack SDK"
+msgstr "OpenStack SDK のインストール"
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml46(para)
-msgid "The Create An Image dialog box appears."
-msgstr "「イメージの作成」ダイアログボックスが表示されます。"
-
-#: ./doc/user-guide/section_dashboard_manage_images.xml49(para)
-msgid "Enter the following values:"
-msgstr "以下の値を入力します。"
-
-#: ./doc/user-guide/section_dashboard_manage_images.xml56(guilabel)
-msgid "Name"
-msgstr "名前"
-
-#: ./doc/user-guide/section_dashboard_manage_images.xml59(para)
-msgid "Enter a name for the image."
-msgstr "イメージの名前を入力します。"
-
-#: ./doc/user-guide/section_dashboard_manage_images.xml67(para)
-msgid "Optionally, enter a brief description of the image."
-msgstr "オプションとして、イメージの簡単な説明を入力します。"
-
-#: ./doc/user-guide/section_dashboard_manage_images.xml73(guilabel)
-msgid "Image Source"
-msgstr "イメージソース"
-
-#: ./doc/user-guide/section_dashboard_manage_images.xml76(para)
+#: ./doc/user-guide/section_sdk_install.xml7(para)
 msgid ""
-"Choose the image source from the list. Your choices are <guilabel>Image "
-"Location</guilabel> and <guilabel>Image File</guilabel>."
-msgstr "一覧からイメージのソースを選択します。<guilabel>イメージの場所</guilabel>と<guilabel>イメージファイル</guilabel>を選択できます。"
+"Each OpenStack project has its own Python library. These libraries are "
+"bundled with the command-line clients. For example, the Python bindings for "
+"the Compute API are bundled with the <package>python-novaclient</package> "
+"package."
+msgstr "各 OpenStack プロジェクトは自身の Python ライブラリを持ちます。これらのライブラリはコマンドラインクライアントに同梱されています。たとえば、Compute API の Python バインドは <package>python-novaclient</package> パッケージに同梱されています。"
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml83(para)
-msgid "<guilabel>Image File</guilabel> or <guilabel>Image Location</guilabel>"
-msgstr "<guilabel>イメージファイル</guilabel>または<guilabel>イメージの場所</guilabel>"
-
-#: ./doc/user-guide/section_dashboard_manage_images.xml88(para)
+#: ./doc/user-guide/section_sdk_install.xml11(para)
 msgid ""
-"Based on your selection for <guilabel>Image Source</guilabel>, you either "
-"enter the location URL of the image in the <guilabel>Image "
-"Location</guilabel> field. or browse to the image file on your system and "
-"add it."
+"For details about how to install the clients, see <link "
+"linkend=\"install_clients\">install the OpenStack command-line "
+"clients</link>."
+msgstr "クライアントのインストール方法の詳細は<link linkend=\"install_clients\">OpenStack コマンドラインクライアントのインストール</link>を参照してください。"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml8(para)
+msgid ""
+"Before you launch an instance, you should add security group rules to enable"
+" users to ping and use SSH to connect to the instance. To do so, you either "
+"<link href=\"#security_groups_add_rule\">add rules to the default security "
+"group</link> or add a security group with rules."
+msgstr "インスタンスの起動前に、ユーザーがインスタンスに ping と SSH を実行できるよう、セキュリティグループのルールを追加すべきです。そうする場合、<link href=\"#security_groups_add_rule\">default セキュリティグループにルールを追加する</link> か、ルールを持つセキュリティグループを追加します。"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml14(para)
+msgid ""
+"Key pairs are SSH credentials that are injected into an instance when it is "
+"launched. To use key pair injection, the image that the instance is based on"
+" must contain the <literal>cloud-init</literal> package. Each project should"
+" have at least one key pair. For more information, see <xref "
+"linkend=\"keypair_add\"/>."
+msgstr "キーペアは、インスタンスの起動時に、インスタンスに注入される SSH クレデンシャルです。キーペアを注入するために、インスタンスがベースとするイメージは、<literal>cloud-init</literal> パッケージを含める必要があります。各プロジェクトは、少なくとも 1 つのキーペアを持つべきです。詳細は <xref linkend=\"keypair_add\"/> を参照してください。"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml20(para)
+msgid ""
+"If you have generated a key pair with an external tool, you can import it "
+"into OpenStack. The key pair can be used for multiple instances that belong "
+"to a project. For more information, see <xref "
+"linkend=\"dashboard_import_keypair\"/>."
+msgstr "外部ツールを用いてキーペアを作成しても、OpenStack にインポートできます。キーペアは同じプロジェクトの複数のインスタンスに使用できます。詳細は<xref linkend=\"dashboard_import_keypair\"/>を参照してください。"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml25(para)
+msgid ""
+"When an instance is created in OpenStack, it is automatically assigned a "
+"fixed IP address in the network to which the instance is assigned. This IP "
+"address is permanently associated with the instance until the instance is "
+"terminated. However, in addition to the fixed IP address, a floating IP "
+"address can also be attached to an instance. Unlike fixed IP addresses, "
+"floating IP addresses are able to have their associations modified at any "
+"time, regardless of the state of the instances involved."
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml97(guilabel)
-msgid "Format"
-msgstr "形式"
+#: ./doc/user-guide/section_dashboard_access_and_security.xml35(title)
+msgid "Add a rule to the default security group"
+msgstr "default セキュリティグループへのルールの追加"
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml100(para)
-msgid "Select the correct format (for example, QCOW2) for the image."
-msgstr "イメージの適切な形式 (例: QCOW2) を選択します。"
-
-#: ./doc/user-guide/section_dashboard_manage_images.xml107(guilabel)
-msgid "Architecture"
-msgstr "アーキテクチャー"
-
-#: ./doc/user-guide/section_dashboard_manage_images.xml111(para)
+#: ./doc/user-guide/section_dashboard_access_and_security.xml36(para)
 msgid ""
-"Specify the architecture. For example, <literal>i386</literal> for a 32-bit "
-"architecture or <literal>x86-64</literal> for a 64-bit architecture."
-msgstr "アーキテクチャーを指定します。例えば、32 ビットアーキテクチャーは <literal>i386</literal>、64 ビットアーキテクチャーは <literal>x86-64</literal> です。"
+"This procedure enables SSH and ICMP (ping) access to instances. The rules "
+"apply to all instances within a given project, and should be set for every "
+"project unless there is a reason to prohibit SSH or ICMP access to the "
+"instances."
+msgstr "この手順により、インスタンスに SSH と ICMP (ping) アクセスできるようになります。ルールは、指定されたプロジェクト内のすべてのインスタンスに適用されます。インスタンスへの SSH や ICMP アクセスを禁止する理由がなければ、すべてのプロジェクトに対して設定すべきです。"
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml118(para)
+#: ./doc/user-guide/section_dashboard_access_and_security.xml41(para)
 msgid ""
-"<guilabel>Minimum Disk (GB)</guilabel> and <guilabel>Minimum RAM "
-"(MB)</guilabel>"
-msgstr "<guilabel>最小ディスク (GB)</guilabel> および<guilabel>最小メモリ (MB)</guilabel>"
+"This procedure can be adjusted as necessary to add additional security group"
+" rules to a project, if your cloud requires them."
+msgstr "この手順は、追加のセキュリティグループのルールをプロジェクトに追加するために、必要に応じて調整できます。"
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml122(para)
-msgid "Leave these optional fields empty."
-msgstr "これらのオプション項目を空白のままにします。"
-
-#: ./doc/user-guide/section_dashboard_manage_images.xml127(guilabel)
-msgid "Public"
-msgstr "パブリック"
-
-#: ./doc/user-guide/section_dashboard_manage_images.xml130(para)
+#: ./doc/user-guide/section_dashboard_access_and_security.xml46(para)
 msgid ""
-"Select this check box to make the image public to all users with access to "
-"the current project."
-msgstr "現在のプロジェクトにアクセス権を持つすべてのユーザーにイメージを公開する場合、このチェックボックスを選択します。"
+"Log in to the dashboard, choose a project, and click <guilabel>Access &amp; "
+"Security</guilabel>. The <guilabel>Security Groups</guilabel> tab shows the "
+"security groups that are available for this project."
+msgstr "ダッシュボードにログインし、プロジェクトを選択し、<guilabel>アクセスとセキュリティ</guilabel>をクリックします。<guilabel>セキュリティグループ</guilabel>タブに、このプロジェクトで利用できるセキュリティグループが表示されます。"
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml137(guilabel)
-msgid "Protected"
-msgstr "保護"
-
-#: ./doc/user-guide/section_dashboard_manage_images.xml140(para)
+#: ./doc/user-guide/section_dashboard_access_and_security.xml53(para)
 msgid ""
-"Select this check box to ensure that only users with permissions can delete "
-"the image."
-msgstr "権限を持つユーザーのみがこのイメージを削除できるようにする場合、このチェックボックスを選択します。"
+"Select the <guilabel>default</guilabel> security group and click "
+"<guibutton>Edit Rules</guibutton>."
+msgstr "<guilabel>default</guilabel> セキュリティグループを選択し、<guibutton>ルールの編集</guibutton>をクリックします。"
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml149(para)
+#: ./doc/user-guide/section_dashboard_access_and_security.xml58(para)
+msgid "To allow SSH access, click <guibutton>Add Rule</guibutton>."
+msgstr "SSH アクセスを許可するために、<guibutton>ルールの追加</guibutton>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml62(para)
+#: ./doc/user-guide/section_dashboard_access_and_security.xml105(para)
+msgid "In the Add Rule dialog box, enter the following values:"
+msgstr "ルールの追加ダイアログボックスで、以下の値を入力します。"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml69(guilabel)
+#: ./doc/user-guide/section_dashboard_access_and_security.xml111(guilabel)
+msgid "Rule"
+msgstr "ルール"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml71(literal)
+msgid "SSH"
+msgstr "SSH"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml75(guilabel)
+#: ./doc/user-guide/section_dashboard_access_and_security.xml119(guilabel)
+msgid "Remote"
+msgstr "接続相手"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml84(literal)
+#: ./doc/user-guide/section_dashboard_access_and_security.xml124(literal)
+msgid "0.0.0.0/0"
+msgstr "0.0.0.0/0"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml90(para)
 msgid ""
-"The image is queued to be uploaded. It might take some time before the "
-"status changes from Queued to Active."
-msgstr "イメージがアップロードのためにキューに入れられます。ステータスが Queued  から Active に変更されるまでに少し時間がかかるかもしれません。"
+"To accept requests from a particular range of IP addresses, specify the IP "
+"address block in the <guilabel>CIDR</guilabel> box."
+msgstr "特定の IP アドレス範囲からのリクエストを許可する場合、<guilabel>CIDR</guilabel> ボックスに IP アドレスブロックを指定します。"
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml155(title)
-msgid "Update an image"
-msgstr "イメージの更新"
+#: ./doc/user-guide/section_dashboard_access_and_security.xml96(para)
+#: ./doc/user-guide/section_dashboard_access_and_security.xml129(para)
+msgid "Click <guibutton>Add</guibutton>."
+msgstr "<guibutton>追加</guibutton>をクリックします。"
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml156(para)
-msgid "Follow this procedure to update an existing image."
-msgstr "既存のイメージを更新する場合、この手順を実行します。"
-
-#: ./doc/user-guide/section_dashboard_manage_images.xml174(para)
+#: ./doc/user-guide/section_dashboard_access_and_security.xml97(para)
 msgid ""
-"In the <guilabel>Actions</guilabel> column, click <guilabel>More</guilabel> "
-"and then select <guilabel>Edit</guilabel> from the list."
-msgstr "<guilabel>アクション</guilabel>列の<guilabel>▼</guilabel>をクリックし、一覧から<guilabel>編集</guilabel>を選択します。"
+"Instances will now have SSH port 22 open for requests from any IP address."
+msgstr "インスタンスは、すべての IP アドレスからのリクエストに対して、SSH ポート 22 番をオープンします。"
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml182(para)
-msgid "Change the name of the image."
-msgstr "イメージの名前を変更します。"
+#: ./doc/user-guide/section_dashboard_access_and_security.xml101(para)
+msgid "To add an ICMP rule, click <guibutton>Add Rule</guibutton>."
+msgstr "ICMP ルールを追加するために、<guibutton>ルールの追加</guibutton>をクリックします。"
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml185(para)
+#: ./doc/user-guide/section_dashboard_access_and_security.xml112(literal)
+msgid "All ICMP"
+msgstr "All ICMP"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml115(guilabel)
+msgid "Direction"
+msgstr "方向"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml116(literal)
+msgid "Ingress"
+msgstr "受信"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml130(para)
+msgid "Instances will now accept all incoming ICMP packets."
+msgstr "インスタンスは、すべての ICMP 入力パケットを受け付けます。"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml137(para)
+msgid "Create at least one key pair for each project."
+msgstr "プロジェクトごとに少なくとも 1 つのキーペアを作成します。"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml140(para)
+#: ./doc/user-guide/section_dashboard_access_and_security.xml169(para)
+#: ./doc/user-guide/section_dashboard_access_and_security.xml237(para)
 msgid ""
-"Select the <guilabel>Public</guilabel> check box to make the image public."
-msgstr "イメージをパブリックにするために、<guilabel>パブリック</guilabel>チェックボックスを選択します。"
+"Log in to the dashboard, choose a project, and click <guilabel>Access &amp; "
+"Security</guilabel>."
+msgstr "ダッシュボードにログインし、プロジェクトを選択し、<guilabel>アクセスとセキュリティ</guilabel>をクリックします。"
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml189(para)
+#: ./doc/user-guide/section_dashboard_access_and_security.xml145(para)
+#: ./doc/user-guide/section_dashboard_access_and_security.xml174(para)
 msgid ""
-"Clear the <guilabel>Public</guilabel> check box to make the image private."
-msgstr "イメージをプライベートにするために、<guilabel>パブリック</guilabel>チェックボックスを選択解除します。"
-
-#: ./doc/user-guide/section_dashboard_manage_images.xml179(para)
-msgid ""
-"In the Update Image dialog box, you can perform the following actions: "
-"<placeholder-1/>"
-msgstr "イメージの更新ダイアログボックスで、以下の操作を実行できます: <placeholder-1/>"
-
-#: ./doc/user-guide/section_dashboard_manage_images.xml195(para)
-msgid "Click <guibutton>Update Image</guibutton>."
-msgstr "<guibutton>イメージの更新</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_manage_images.xml200(title)
-msgid "Delete an image"
-msgstr "イメージの削除"
-
-#: ./doc/user-guide/section_dashboard_manage_images.xml201(para)
-msgid ""
-"Deletion of images is permanent and <emphasis "
-"role=\"bold\">cannot</emphasis> be reversed. Only users with the appropriate"
-" permissions can delete images."
-msgstr "イメージの削除は、永続的であり、元に戻せ<emphasis role=\"bold\">ません</emphasis>。適切なパーミッションを持つユーザーのみが、イメージを削除できます。"
-
-#: ./doc/user-guide/section_dashboard_manage_images.xml217(para)
-msgid "Select the images that you want to delete."
-msgstr "削除したいイメージを選択します。"
-
-#: ./doc/user-guide/section_dashboard_manage_images.xml220(para)
-msgid "Click <guibutton>Delete Images</guibutton>."
-msgstr "<guibutton>イメージの削除</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_manage_images.xml223(para)
-msgid ""
-"In the <guilabel>Confirm Delete Image</guilabel> dialog box, click "
-"<guibutton>Delete Images</guibutton> to confirm the deletion."
-msgstr "<guilabel>イメージの削除の確認</guilabel>ダイアログボックスで、削除を確認するために<guibutton>イメージの削除</guibutton>をクリックします。"
-
-#: ./doc/user-guide/ch_cli.xml10(title)
-msgid "OpenStack command-line clients"
-msgstr "OpenStack コマンドラインクライアント"
-
-#: ./doc/user-guide/section_sdk_auth_nova.xml6(title)
-msgid "Authenticate against a Compute endpoint"
-msgstr "Compute エンドポイントへの認証"
-
-#: ./doc/user-guide/section_sdk_auth_nova.xml7(para)
-msgid ""
-"To authenticate against a Compute endpoint, instantiate a <link "
-"href=\"http://docs.openstack.org/developer/python-"
-"novaclient/api/novaclient.v1_1.client.html#novaclient.v1_1.client.Client\"> "
-"novaclient.v_1_1.client.Client</link> object:"
-msgstr "Compute エンドポイントに認証するために、<link href=\"http://docs.openstack.org/developer/python-novaclient/api/novaclient.v1_1.client.html#novaclient.v1_1.client.Client\"> novaclient.v_1_1.client.Client</link> オブジェクトのインスタンスを生成します。"
-
-#: ./doc/user-guide/section_sdk_auth_nova.xml18(para)
-msgid ""
-"Alternatively, you can instantiate a "
-"<classname>novaclient.client.Client</classname> object and pass the version "
-"number:"
-msgstr "代わりに、<classname>novaclient.client.Client</classname> オブジェクトのインスタンスを生成し、バージョン番号を渡すこともできます。"
-
-#: ./doc/user-guide/section_sdk_auth_nova.xml28(para)
-msgid ""
-"If you authenticate against an endpoint that uses a custom authentication "
-"back end, you must load the authentication plug-in and pass it to the "
-"constructor."
+"Click the <guilabel>Keypairs</guilabel> tab, which shows the key pairs that "
+"are available for this project."
 msgstr ""
 
-#: ./doc/user-guide/section_sdk_auth_nova.xml31(para)
+#: ./doc/user-guide/section_dashboard_access_and_security.xml150(para)
+msgid "Click <guibutton>Create Keypair</guibutton>."
+msgstr "<guibutton>キーペアの作成</guibutton>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml154(para)
 msgid ""
-"The Rackspace public cloud is an OpenStack deployment that uses a custom "
-"authentication back end. To authenticate against this cloud, you must "
-"install the <link href=\"https://pypi.python.org/pypi/rackspace-"
-"novaclient/\"> rackspace-novaclient</link> library that contains the "
-"Rackspace authentication plug-in, called <literal>rackspace</literal>. The "
-"following Python code shows the additional modifications required to "
-"instantiate a <classname>Client</classname> object that can authenticate "
-"against the Rackspace custom authentication back end."
+"In the Create Keypair dialog box, enter a name for your key pair, and click "
+"<guibutton>Create Keypair</guibutton>."
 msgstr ""
 
-#: ./doc/user-guide/section_sdk_auth_nova.xml53(para)
-msgid ""
-"If you set the <literal>OS_AUTH_SYSTEM</literal> environment variable, check"
-" for this variable in your Python script to determine whether you need to "
-"load a custom authentication back end:"
+#: ./doc/user-guide/section_dashboard_access_and_security.xml160(para)
+msgid "Respond to the prompt to download the key pair."
 msgstr ""
 
+#: ./doc/user-guide/section_dashboard_access_and_security.xml179(para)
+msgid "Click <guibutton>Import Keypair</guibutton>."
+msgstr "<guibutton>キーペアのインポート</guibutton>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml183(para)
+msgid ""
+"In the Import Keypair dialog box, enter the name of your key pair, copy the "
+"public key into the <guilabel>Public Key</guilabel> box, and then click "
+"<guibutton>Import Keypair</guibutton>."
+msgstr "キーペアのインポートのダイアログボックスで、キーペアの名前を入力します。<guilabel>公開鍵</guilabel>ボックスに公開鍵をコピーします。そして、<guibutton>キーペアのインポート</guibutton>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml190(para)
+msgid "Save the <filename>*.pem</filename> file locally."
+msgstr "ローカルに <filename>*.pem</filename> ファイルを保存します。"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml192(para)
+msgid ""
+"To change its permissions so that only you can read and write to the file, "
+"run the following command:"
+msgstr "あなただけがファイルを読み書きできるようにパーミッションを変更するために、以下のコマンドを実行します。"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml195(replaceable)
+#: ./doc/user-guide/section_dashboard_access_and_security.xml211(replaceable)
+msgid "yourPrivateKey"
+msgstr "yourPrivateKey"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml197(para)
+msgid ""
+"If you are using the dashboard from a Windows computer, use PuTTYgen to load"
+" the <filename>*.pem</filename> file and convert and save it as "
+"<filename>*.ppk</filename>. For more information see the <link "
+"href=\"http://winscp.net/eng/docs/ui_puttygen\">WinSCP web page for "
+"PuTTYgen</link>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml209(para)
+msgid "To make the key pair known to SSH, run the <placeholder-1/> command."
+msgstr "キーペアを SSH で利用するために、<placeholder-1/> コマンドを実行します。"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml214(para)
+msgid "The Compute database registers the public key of the key pair."
+msgstr "コンピュートのデータベースはキーペアの公開鍵を登録します。"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml216(para)
+msgid ""
+"The dashboard lists the key pair on the <guilabel>Access &amp; "
+"Security</guilabel> tab."
+msgstr "ダッシュボードの<guibutton>アクセスとセキュリティ</guibutton>タブにキーペアが一覧表示されます。"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml220(title)
+msgid "Allocate a floating IP address to an instance"
+msgstr "インスタンスへの Floating IP アドレスの割り当て"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml221(para)
+msgid ""
+"When an instance is created in OpenStack, it is automatically assigned a "
+"fixed IP address in the network to which the instance is assigned. This IP "
+"address is permanently associated with the instance until the instance is "
+"terminated."
+msgstr "インスタンスを OpenStack に作成したとき、インスタンスに割り当てられるネットワーク上の固定 IP アドレスが自動的に割り当てられます。この IP アドレスは、インスタンスが終了するまで、インスタンスに割り当てられたままです。"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml227(para)
+msgid ""
+"However, in addition to the fixed IP address, a floating IP address can also"
+" be attached to an instance. Unlike fixed IP addresses, floating IP "
+"addresses can have their associations modified at any time, regardless of "
+"the state of the instances involved. This procedure details the reservation "
+"of a floating IP address from an existing pool of addresses and the "
+"association of that address with a specific instance."
+msgstr "しかしながら、固定 IP アドレスに加えて、Floating IP アドレスもインスタンスに割り当てられます。固定 IP アドレスと異なり、インスタンスの状態に関わらず、Floating IP アドレスはいつでも割り当てを変更できます。この手順は、既存のアドレスプールから Floating IP を予約し、このアドレスを特定のインスタンスに割り当てることを詳細に説明します。"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml241(para)
+msgid ""
+"Click the <guilabel>Floating IPs</guilabel> tab, which shows the floating IP"
+" addresses allocated to instances."
+msgstr "<guilabel>Floating IP</guilabel> タブをクリックします。ここにインスタンスに割り当てられた Floating IP アドレスが表示されます。"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml246(para)
+msgid "Click <guibutton>Allocate IP to Project</guibutton>."
+msgstr "<guibutton>Floating IP の確保</guibutton>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml249(para)
+msgid "Choose the pool from which to pick the IP address."
+msgstr "IP アドレスを確保するプールを選択します。"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml253(para)
+msgid "Click <guibutton>Allocate IP</guibutton>."
+msgstr "<guibutton>Floating IP の確保</guibutton>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml256(para)
+msgid ""
+"In the <guilabel>Floating IPs</guilabel> list, click <guibutton> "
+"Associate</guibutton>."
+msgstr "<guilabel>Floating IP</guilabel> 一覧で、<guibutton>割り当て</guibutton>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml264(para)
+msgid ""
+"The <guilabel>IP Address</guilabel> field is filled automatically, but you "
+"can add a new IP address by clicking the <guibutton>+</guibutton> button."
+msgstr "<guilabel>IP アドレス</guilabel>の項目は自動的に入力されますが、<guibutton>+</guibutton> ボタンをクリックして、新しい IP アドレスを追加できます。"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml271(para)
+msgid ""
+"In the <guilabel>Ports to be associated</guilabel> field, select a port from"
+" the list."
+msgstr "<guilabel>割り当てるポート</guilabel>の項目で、ドロップダウンリストからポートを選択します。"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml274(para)
+msgid "The list shows all the instances with their fixed IP addresses."
+msgstr "ドロップダウンに固定 IP アドレスを持つインスタンスがすべて一覧表示されます。"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml260(para)
+msgid ""
+"In the Manage Floating IP Associations dialog box, choose the following "
+"options: <placeholder-1/>"
+msgstr "Floating IP の割り当ての管理ダイアログボックスで、以下のオプションを選択します。 <placeholder-1/>"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml281(para)
+msgid "Click <guibutton>Associate</guibutton>."
+msgstr "<guibutton>割り当て</guibutton>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml285(para)
+msgid ""
+"To disassociate an IP address from an instance, click the "
+"<guibutton>Disassociate</guibutton> button."
+msgstr "IP アドレスをインスタンスから割り当て解除する場合、<guibutton>割り当て解除</guibutton>ボタンをクリックします。"
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml287(para)
+msgid ""
+"To release the floating IP address back into the pool of addresses, click "
+"the <guibutton>More</guibutton> button and select the <guilabel>Release "
+"Floating IP</guilabel> option."
+msgstr "Floating IP アドレスを開放してアドレスプールに戻すために、<guibutton>▼</guibutton>ボタンをクリックし、<guilabel>Floating IP の開放</guilabel>オプションを選択します。"
+
+#: ./doc/user-guide/ch_sdk.xml6(title)
+msgid "OpenStack Python SDK"
+msgstr "OpenStack Python SDK"
+
+#: ./doc/user-guide/ch_sdk.xml8(para)
+msgid ""
+"Use the OpenStack Python Software Development Kit (SDK) to write Python "
+"automation scripts that create and manage resources in your OpenStack cloud."
+" The SDK implements Python bindings to the OpenStack API, which enables you "
+"to perform automation tasks in Python by making calls on Python objects "
+"rather than making REST calls directly. All OpenStack command-line tools are"
+" implemented using the Python SDK."
+msgstr "OpenStack クラウドでリソースの作成や管理を自動化する Python ツールを作成するために、OpenStack Python ソフトウェア開発キット (SDK) を使用します。SDK は OpenStack API への Python バインドを実装します。これにより、直接 REST コールを発行する代わりに、Python オブジェクトでコールを発行することにより、Python で自動化タスクを実行できます。すべての OpenStack コマンドラインツールは Python SDK を使用して実装されています。"
+
+#: ./doc/user-guide/ch_sdk.xml15(para)
+msgid "You should also be familiar with:"
+msgstr "以下にも慣れているとよいでしょう。"
+
+#: ./doc/user-guide/ch_sdk.xml18(para)
+msgid "RESTful web services"
+msgstr "RESTful Web サービス"
+
+#: ./doc/user-guide/ch_sdk.xml21(para)
+msgid "HTTP/1.1"
+msgstr "HTTP/1.1"
+
+#: ./doc/user-guide/ch_sdk.xml24(para)
+msgid "JSON and XML data serialization formats"
+msgstr "JSON および XML データシリアライズ形式"
+
+#: ./doc/user-guide/section_cli_swift_howto.xml6(title)
+msgid "Manage objects and containers"
+msgstr "オブジェクトとコンテナーの管理"
+
+#: ./doc/user-guide/section_cli_swift_howto.xml8(para)
+msgid ""
+"The OpenStack Object Storage service provides the <placeholder-1/> client, "
+"which is a command-line interface (CLI). Use this client to list objects and"
+" containers, upload objects to containers, and download or delete objects "
+"from containers. You can also gather statistics and update metadata for "
+"accounts, containers, and objects."
+msgstr "OpenStack Object Storage は  <placeholder-1/> クライアントを提供します。これはコマンドラインインターフェース (CLI) です。オブジェクトやコンテナーの一覧表示、オブジェクトのコンテナーへのアップロード、オブジェクトのコンテナーからのダウンロードや削除を実行するために、このクライアントを使用します。アカウント、コンテナー、オブジェクトに関する統計情報の収集、メタデータの更新なども実行できます。"
+
+#: ./doc/user-guide/section_cli_swift_howto.xml14(para)
+msgid ""
+"This client is based on the native swift client library, "
+"<literal>client.py</literal>, which seamlessly re-authenticates if the "
+"current token expires during processing, retries operations multiple times, "
+"and provides a processing concurrency of 10."
+msgstr "このクライアントは、ネイティブの swift クライアントライブラリ (<literal>client.py</literal>) をベースとしており、処理中に現在のトークンが失効した場合や、複数回オペレーションを中断した場合、10 個同時に並行処理する場合、シームレスに再認証します。 "
+
+#: ./doc/user-guide/section_cli_swift_howto.xml20(title)
+msgid "Create and manage containers"
+msgstr "コンテナーの作成と管理"
+
+#: ./doc/user-guide/section_cli_swift_howto.xml23(para)
+msgid ""
+"To create a container, run the following command and replace "
+"<replaceable>CONTAINER</replaceable> with the name of your container."
+msgstr "コンテナーを作成するために、以下のコマンドを実行します。<replaceable>CONTAINER</replaceable> をお使いのコンテナーの名前で置き換えます。"
+
+#: ./doc/user-guide/section_cli_swift_howto.xml28(para)
+msgid "To list all containers: run the following command:"
+msgstr "すべてのコンテナーを一覧表示するために、以下のコマンドを実行します。"
+
+#: ./doc/user-guide/section_cli_swift_howto.xml32(para)
+msgid "To check the status of containers, run the following command:"
+msgstr "コンテナーの状態を確認するために、以下のコマンドを実行します。"
+
+#: ./doc/user-guide/section_cli_swift_howto.xml42(para)
+msgid ""
+"You can also use the <placeholder-1/> command with the "
+"<replaceable>ACCOUNT</replaceable> or <replaceable>CONTAINER</replaceable> "
+"names as parameters."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_swift_howto.xml61(title)
+msgid "Manage access"
+msgstr "アクセス権の管理"
+
+#: ./doc/user-guide/section_cli_swift_howto.xml64(para)
+msgid ""
+"Users have roles on accounts. For example, a user with the admin role has "
+"full access to all containers and objects in an account. You can set access "
+"control lists (ACLs) at the container level and support lists for read and "
+"write access, which you set with the <literal>X-Container-Read</literal> and"
+" <literal>X-Container-Write</literal> headers."
+msgstr "ユーザーにはアカウントに対してロールが割り当てられます。例えば、管理者ロールがあると、アカウント内のコンテナーやオブジェクトすべてに完全にアクセスすることができます。 コンテナーレベルでアクセス制御リスト (ACL) を設定できます。読み取り権と書き込み権の一覧表示がサポートされます。<literal>X-Container-Read</literal> と <literal>X-Container-Write</literal> ヘッダーを用いて設定します。"
+
+#: ./doc/user-guide/section_cli_swift_howto.xml70(para)
+msgid ""
+"To give a user read access, use the <placeholder-1/> command with the "
+"<parameter>-r</parameter> parameter. To give a user write access, use the "
+"<parameter>-w</parameter> parameter."
+msgstr "ユーザーに読み取り権を与える場合、<placeholder-1/> コマンドを <parameter>-r</parameter> パラメーターとともに使用します。ユーザーに書きこみ権を与える場合、<parameter>-w</parameter> パラメーターを使用します。"
+
+#: ./doc/user-guide/section_cli_swift_howto.xml73(para)
+msgid ""
+"The following example enables the <literal>testuser</literal> user to read "
+"objects in the container:"
+msgstr "以下の例は、<literal>testuser</literal> ユーザーがコンテナー内でオブジェクトを読み取りできるようにします。 "
+
+#: ./doc/user-guide/section_cli_swift_howto.xml76(para)
+msgid "You can also use this command with a list of users."
+msgstr "また、このコマンドをユーザー一覧とあわせて使用することもできます。"
+
+#: ./doc/user-guide/section_cli_swift_howto.xml79(para)
+msgid ""
+"If you use StaticWeb middleware to enable Object Storage to serve public web"
+" content, use <literal>.r:</literal>, followed by a list of allowed "
+"referrers."
+msgstr "StaticWeb ミドルウェアを使用して Object Storage を有効にし、パブリックの Web コンテンツにサービスを提供する場合、アクセス可能な参照元に対する構文は <literal>.r:</literal> の後に許可済みの参照元の一覧を指定します。 "
+
+#: ./doc/user-guide/section_cli_swift_howto.xml82(para)
+msgid "The following command gives object access to all referring domains:"
+msgstr "以下のコマンドは、参照しているドメインすべてにオブジェクトがアクセスできるようにします。"
+
+#: ./doc/user-guide/section_cli_swift_howto.xml89(title)
+msgid "Manage objects"
+msgstr "オブジェクトの管理"
+
+#: ./doc/user-guide/section_cli_swift_howto.xml92(para)
+msgid "To upload an object to a container, run the following command:"
+msgstr "コンテナーにオブジェクトをアップロードするために、以下のコマンドを実行します。"
+
+#: ./doc/user-guide/section_cli_swift_howto.xml94(replaceable)
+#: ./doc/user-guide/section_cli_swift_howto.xml96(replaceable)
+#: ./doc/user-guide/section_cli_swift_howto.xml101(replaceable)
+#: ./doc/user-guide/section_cli_swift_howto.xml115(replaceable)
+#: ./doc/user-guide/section_cli_swift_howto.xml120(replaceable)
+msgid "OBJECT_FILENAME"
+msgstr "OBJECT_FILENAME"
+
+#: ./doc/user-guide/section_cli_swift_howto.xml95(para)
+msgid "To upload in chunks, for large files, run the following command:"
+msgstr "チャンク化した大きなファイルをアップロードするために、以下のコマンドを実行します。"
+
+#: ./doc/user-guide/section_cli_swift_howto.xml96(replaceable)
+msgid "CHUNK_SIZE"
+msgstr "CHUNK_SIZE"
+
+#: ./doc/user-guide/section_cli_swift_howto.xml99(para)
+msgid "To check the status of the object, run the following command:"
+msgstr "オブジェクトの状態を確認するために、以下のコマンドを実行します。"
+
+#: ./doc/user-guide/section_cli_swift_howto.xml114(para)
+msgid "To list the objects in a container, run the following command:"
+msgstr "コンテナーにあるオブジェクトを一覧表示するために、以下のコマンドを実行します。"
+
+#: ./doc/user-guide/section_cli_swift_howto.xml118(para)
+msgid "To download an object from a container:, run the following command:"
+msgstr "コンテナーからオブジェクトをダウンロードするために、以下のコマンドを実行します。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml6(title)
+msgid "Create and manage volumes"
+msgstr "ボリュームの作成と管理"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml8(para)
+msgid ""
+"Volumes are block storage devices that you attach to instances to enable "
+"persistent storage. You can attach a volume to a running instance or detach "
+"a volume and attach it to another instance at any time. You can also create "
+"a snapshot from or delete a volume. Only administrative users can create "
+"volume types."
+msgstr "ボリュームは、永続ストレージを使用するためにインスタンスに接続するブロックストレージデバイスです。ボリュームを稼働中のインスタンスに接続したり切断したりできます。また、いつでも別のインスタンスに接続できます。ボリュームからスナップショットを作成したり、削除したりできます。管理ユーザーのみがボリューム種別を作成できます。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml15(title)
+msgid "Create a volume"
+msgstr "ボリュームの作成"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml18(para)
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml136(para)
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml170(para)
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml212(para)
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml251(para)
+msgid ""
+"Log in to the dashboard, choose a project, and click "
+"<guibutton>Volumes</guibutton>."
+msgstr "ダッシュボードにログインし、プロジェクトを選択し、<guibutton>ボリューム</guibutton>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml22(para)
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml124(para)
+msgid "Click <guibutton>Create Volume</guibutton>."
+msgstr "<guibutton>ボリュームの作成</guibutton>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml23(para)
+msgid "In the dialog box that opens, enter or select the following values."
+msgstr "表示されたダイアログボックスで、以下の値を入力または選択します。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml32(guilabel)
+msgid "Volume Name"
+msgstr "ボリューム名"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml36(para)
+msgid "Specify a name for the volume."
+msgstr "ボリュームの名前を指定します。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml47(para)
+msgid "Optionally, provide a brief description for the volume."
+msgstr "オプションとして、ボリュームの簡単な説明を入力します。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml54(guilabel)
+msgid "Type"
+msgstr "種別"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml58(para)
+msgid "Leave this field blank."
+msgstr "この項目は空白にしておきます。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml64(guilabel)
+msgid "Size (GB)"
+msgstr "容量 (GB)"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml68(para)
+msgid "The size of the volume in gigabytes."
+msgstr "ギガバイト単位のボリュームサイズ。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml75(guilabel)
+msgid "Volume Source"
+msgstr "ボリュームソース"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml79(para)
+msgid "Select one of the following options:"
+msgstr "以下のオプションを選択します。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml82(guilabel)
+msgid "No source, empty volume"
+msgstr "ソースを指定しなければ、ボリュームが空になります"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml83(para)
+msgid "Creates an empty volume."
+msgstr "空のボリュームを作成します。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml84(para)
+msgid "An empty volume does not contain a file system or a partition table."
+msgstr "空のボリュームは、ファイルシステムやパーティションテーブルを含みません。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml88(guilabel)
+msgid "Snapshot"
+msgstr "スナップショット"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml89(para)
+msgid ""
+"If you choose this option, a new field for <guilabel>Use snapshot as a "
+"source</guilabel> displays. You can select the snapshot from the list."
+msgstr "このオプションを選択する場合、<guilabel>ソースとしてスナップショットの利用</guilabel>の新項目が表示されます。この一覧からスナップショットを選択できます。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml95(guilabel)
+msgid "Image"
+msgstr "イメージ"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml96(para)
+msgid ""
+"If you choose this option, a new field for <guilabel>Use image as a "
+"source</guilabel> displays. You can select the image from the list."
+msgstr "このオプションを選択する場合、<guilabel>ソースとしてイメージの利用</guilabel>の新項目が表示されます。この一覧からイメージを選択できます。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml99(para)
+msgid ""
+"Select the <guilabel>Availability Zone</guilabel> from the list. By default,"
+" this value is set to the availability zone given by the cloud provider (for"
+" example, <literal>us-west</literal> or <literal>apac-south</literal>). For "
+"some cases, it could be <literal>nova</literal>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml107(guilabel)
+msgid "Volume"
+msgstr "ボリューム"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml108(para)
+msgid ""
+"If you choose this option, a new field for <guilabel>Use volume as a "
+"source</guilabel> displays. You can select the volume from the list."
+msgstr "このオプションを選択する場合、<guilabel>ソースとしてボリュームの利用</guilabel>の新項目が表示されます。この一覧からボリュームを選択できます。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml114(para)
+msgid ""
+"Options to use a snapshot or a volume as the source for a volume are "
+"displayed only if there are existing snapshots or volumes."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml127(para)
+msgid ""
+"The dashboard shows the volume on the <guilabel>Volumes</guilabel> tab."
+msgstr "ダッシュボードの<guilabel>ボリューム</guilabel>タブにボリュームが表示されます。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml131(title)
+msgid "Attach a volume to an instance"
+msgstr "ボリュームのインスタンスへの接続"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml132(para)
+msgid ""
+"After you create one or more volumes, you can attach them to instances. You "
+"can attach a volume to one instance at a time."
+msgstr "ボリュームを作成した後、それらをインスタンスに接続できます。ボリュームは、同時に 1 つのインスタンスに接続できます。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml140(para)
+msgid ""
+"Select the volume to add to an instance and click <guibutton>Edit "
+"Attachments</guibutton>."
+msgstr "インスタンスに追加するボリュームを選択し、<guibutton>接続の編集</guibutton>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml144(para)
+msgid ""
+"In the <guilabel>Manage Volume Attachments</guilabel> dialog box, select an "
+"instance."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml148(para)
+msgid ""
+"Enter the name of the device from which the volume is accessible by the "
+"instance."
+msgstr "インスタンスがボリュームにアクセスできる、デバイスの名前を入力します。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml151(para)
+msgid ""
+"The actual device name might differ from the volume name because of "
+"hypervisor settings."
+msgstr "実際のデバイス名は、ハイパーバイザーの設定により、ボリューム名と異なるかもしれません。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml156(para)
+msgid "Click <guibutton>Attach Volume</guibutton>."
+msgstr "<guibutton>ボリュームの接続</guibutton>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml157(para)
+msgid ""
+"The dashboard shows the instance to which the volume is now attached and the"
+" device name."
+msgstr "ボリュームが接続されたインスタンスとデバイス名がダッシュボードに表示されます。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml161(para)
+msgid ""
+"You can view the status of a volume in the <guilabel>Volumes</guilabel> tab "
+"of the dashboard. The volume is either Available or In-Use."
+msgstr "ダッシュボードの<guilabel>ボリューム</guilabel>にボリュームの状態を表示できます。ボリュームは、利用可能または使用中になります。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml163(para)
+msgid ""
+"Now you can log in to the instance and mount, format, and use the disk."
+msgstr "これでインスタンスにログインでき、ディスクをマウント、フォーマット、利用できます。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml167(title)
+msgid "Detach a volume from an instance"
+msgstr "ボリュームのインスタンスからの切断"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml174(para)
+msgid "Select the volume and click <guibutton>Edit Attachments</guibutton>."
+msgstr "ボリュームを選択し、<guibutton>接続の編集</guibutton>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml177(para)
+msgid "Click <guibutton>Detach Volume</guibutton> and confirm your changes."
+msgstr "<guibutton>ボリュームの切断</guibutton>をクリックし、変更を確認します。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml181(para)
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml261(para)
+msgid "A message indicates whether the action was successful."
+msgstr "操作が成功したかどうかはメッセージでわかります。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml184(title)
+msgid "Create a snapshot from a volume"
+msgstr "ボリュームからのスナップショットの作成"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml187(para)
+msgid ""
+"Log in to the dashboard, choose a project, and click "
+"<guilabel>Volumes</guilabel>."
+msgstr "ダッシュボードにログインし、プロジェクトを選択し、<guilabel>ボリューム</guilabel>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml191(para)
+msgid "Select a volume from which to create a snapshot."
+msgstr "スナップショットを作成するボリュームを選択します。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml194(para)
+msgid ""
+"From the <guilabel>More</guilabel> list, select <guilabel>Create "
+"Snapshot</guilabel>."
+msgstr "<guilabel>▼</guilabel>リストから、<guilabel>スナップショットの作成</guilabel>を選択します。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml198(para)
+msgid ""
+"In the dialog box that opens, enter a snapshot name and a brief description."
+msgstr "開いたダイアログボックスで、スナップショットの名前と簡単な説明を入力します。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml202(para)
+msgid "Confirm your changes."
+msgstr "変更を確認します。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml203(para)
+msgid ""
+"The dashboard shows the new volume snapshot in <guilabel>Volume "
+"Snapshots</guilabel> tab."
+msgstr "ダッシュボードの<guilabel>ボリュームのスナップショット</guilabel>に新しいボリュームのスナップショットが表示されます。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml209(title)
+msgid "Edit a volume"
+msgstr "ボリュームの編集"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml221(para)
+msgid ""
+"On the <guilabel>Project</guilabel> tab, click <guilabel>Volumes</guilabel>."
+msgstr "<guilabel>プロジェクト</guilabel> タブで、<guilabel>ボリューム</guilabel>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml228(para)
+msgid ""
+"In the <guilabel>Actions</guilabel> column, click <guilabel>Edit "
+"Volume</guilabel>."
+msgstr "<guilabel>操作</guilabel>の列で、<guilabel>ボリュームの編集</guilabel>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml232(para)
+msgid ""
+"In the <guilabel>Edit Volume</guilabel> dialog box, update the name and "
+"description of the image."
+msgstr "<guilabel>ボリュームの編集</guilabel>ダイアログボックスで、イメージの名前と説明を更新します。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml236(para)
+msgid "Click <guibutton>Edit Volume</guibutton>."
+msgstr "<guibutton>ボリュームの編集</guibutton>をクリックします。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml240(para)
+msgid ""
+"You can extend a volume by using the <guilabel>Extend Volume</guilabel> "
+"option available in the <guibutton>More</guibutton> dropdown list and "
+"entering the new value for volume size."
+msgstr "<guibutton>▼</guibutton>ドロップダウンリストから利用できる、<guilabel>ボリュームの拡張</guilabel>を使用し、新しいボリュームサイズ値を入力して、ボリュームを拡張できます。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml246(title)
+msgid "Delete a volume"
+msgstr "ボリュームの削除"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml247(para)
+msgid ""
+"When you delete an instance, the data in its attached volumes is not "
+"destroyed."
+msgstr "インスタンスの削除時、接続されたボリュームのデータは無くなりません。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml255(para)
+msgid "Select the check boxes for the volumes that you want to delete."
+msgstr "削除したいボリュームのチェックボックスを選択します。"
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml259(para)
+msgid "Click <guibutton>Delete Volumes</guibutton> and confirm your choice."
+msgstr "<guibutton>ボリュームの切断</guibutton>をクリックし、選択内容を確認します。"
+
 #: ./doc/user-guide/section_sdk_configure_instances.xml7(para)
 msgid ""
 "When working with images in the SDK, you will call "
@@ -3309,11 +4834,6 @@ msgid ""
 " method:"
 msgstr "キーペアを一覧表示するために、<methodname><link href=\"http://docs.openstack.org/developer/python-novaclient/api/novaclient.v1_1.keypairs.html#novaclient.v1_1.keypairs.KeypairManager.list\">novaclient.v1_1.keypairs.KeypairManager.list</link></methodname> メソッドを呼び出します。"
 
-#: ./doc/user-guide/section_sdk_configure_instances.xml72(title)
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml111(title)
-msgid "Create and manage security groups"
-msgstr "セキュリティグループの作成と管理"
-
 #: ./doc/user-guide/section_sdk_configure_instances.xml73(para)
 msgid ""
 "To list security groups for the current project, call the <methodname><link "
@@ -3343,11 +4863,6 @@ msgid ""
 " object or group ID as an argument:"
 msgstr "セキュリティグループを削除するために、<link href=\"http://docs.openstack.org/developer/python-novaclient/api/novaclient.v1_1.security_groups.html#novaclient.v1_1.security_groups.SecurityGroup\">novaclient.v1_1.security_groups.SecurityGroup</link> オブジェクトまたはグループ ID を引数として渡して、<methodname><link href=\"http://docs.openstack.org/developer/python-novaclient/api/novaclient.v1_1.security_groups.html#novaclient.v1_1.security_groups.SecurityGroupManager.delete\"> novaclient.v_1.security_groups.SecurityGroupManager.delete</link></methodname> メソッドを呼び出します。"
 
-#: ./doc/user-guide/section_sdk_configure_instances.xml97(title)
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml138(title)
-msgid "Create and manage security group rules"
-msgstr "セキュリティグループのルールの作成と管理"
-
 #: ./doc/user-guide/section_sdk_configure_instances.xml98(para)
 msgid ""
 "Access the security group rules from the <literal>rules</literal> attribute "
@@ -3364,1522 +4879,7 @@ msgid ""
 " method:"
 msgstr "セキュリティグループにルールを追加するために、<methodname><link href=\"http://docs.openstack.org/developer/python-novaclient/api/novaclient.v1_1.security_group_rules.html#novaclient.v1_1.security_group_rules.SecurityGroupRuleManager.create\">novaclient.v1_1.security_group_rules.SecurityGroupRuleManager.create</link></methodname> メソッドを呼び出します。"
 
-#: ./doc/user-guide/section_cli_nova_manage_instances.xml6(title)
-msgid "Manage instances and hosts"
-msgstr "インスタンスとホストの管理"
-
-#: ./doc/user-guide/section_cli_nova_manage_instances.xml7(para)
-msgid ""
-"Instances are virtual machines that run inside the cloud on physical compute"
-" nodes. The Compute service manages instances. A host is the node on which a"
-" group of instances resides."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_manage_instances.xml11(para)
-msgid ""
-"This section describes how to perform the different tasks involved in "
-"instance management, such as adding floating IP addresses, stopping and "
-"starting instances, and terminating instances. This section also discusses "
-"node management tasks."
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml7(title)
-msgid "OpenStack command-line interface cheat sheet"
-msgstr "OpenStack コマンドラインインターフェース・チートシート"
-
-#: ./doc/user-guide/app_cheat_sheet.xml9(para)
-msgid ""
-"The following tables give a quick reference of the most used command-line "
-"commands."
-msgstr "以下の表は、よく使われるコマンドの簡単なリファレンスです。"
-
-#: ./doc/user-guide/app_cheat_sheet.xml15(caption)
-msgid "Identity (keystone)"
-msgstr "Identity (keystone)"
-
-#: ./doc/user-guide/app_cheat_sheet.xml21(th)
-#: ./doc/user-guide/app_cheat_sheet.xml67(th)
-#: ./doc/user-guide/app_cheat_sheet.xml141(th)
-#: ./doc/user-guide/app_cheat_sheet.xml334(th)
-#: ./doc/user-guide/app_cheat_sheet.xml375(th)
-#: ./doc/user-guide/app_cheat_sheet.xml459(th)
-msgid "Command"
-msgstr "コマンド"
-
-#: ./doc/user-guide/app_cheat_sheet.xml26(td)
-msgid "List all users"
-msgstr "すべてのユーザーの一覧表示"
-
-#: ./doc/user-guide/app_cheat_sheet.xml32(td)
-msgid "List Identity service catalog"
-msgstr "Identity サービスカタログの一覧表示"
-
-#: ./doc/user-guide/app_cheat_sheet.xml38(td)
-msgid "List all services in service catalog"
-msgstr "サービスカタログにある全サービスの一覧表示"
-
-#: ./doc/user-guide/app_cheat_sheet.xml44(td)
-msgid "Create new user"
-msgstr "新しいユーザーの作成"
-
-#: ./doc/user-guide/app_cheat_sheet.xml46(replaceable)
-#: ./doc/user-guide/app_cheat_sheet.xml53(replaceable)
-#: ./doc/user-guide/app_cheat_sheet.xml186(replaceable)
-#: ./doc/user-guide/app_cheat_sheet.xml215(replaceable)
-#: ./doc/user-guide/app_cheat_sheet.xml222(replaceable)
-#: ./doc/user-guide/app_cheat_sheet.xml228(replaceable)
-#: ./doc/user-guide/app_cheat_sheet.xml234(replaceable)
-#: ./doc/user-guide/app_cheat_sheet.xml240(replaceable)
-#: ./doc/user-guide/app_cheat_sheet.xml246(replaceable)
-#: ./doc/user-guide/app_cheat_sheet.xml252(replaceable)
-#: ./doc/user-guide/app_cheat_sheet.xml258(replaceable)
-#: ./doc/user-guide/app_cheat_sheet.xml266(replaceable)
-#: ./doc/user-guide/app_cheat_sheet.xml273(replaceable)
-#: ./doc/user-guide/app_cheat_sheet.xml341(replaceable)
-#: ./doc/user-guide/app_cheat_sheet.xml385(replaceable)
-msgid "NAME"
-msgstr "NAME"
-
-#: ./doc/user-guide/app_cheat_sheet.xml46(replaceable)
-msgid "TENANT"
-msgstr "TENANT"
-
-#: ./doc/user-guide/app_cheat_sheet.xml47(replaceable)
-msgid "EMAIL"
-msgstr "EMAIL"
-
-#: ./doc/user-guide/app_cheat_sheet.xml47(replaceable)
-msgid "BOOL"
-msgstr "BOOL"
-
-#: ./doc/user-guide/app_cheat_sheet.xml51(td)
-msgid "Create new tenant"
-msgstr "新しいテナントの作成"
-
-#: ./doc/user-guide/app_cheat_sheet.xml53(replaceable)
-msgid "DESCRIPTION"
-msgstr "DESCRIPTION"
-
-#: ./doc/user-guide/app_cheat_sheet.xml61(caption)
-msgid "Image Service (glance)"
-msgstr "Image Service (glance)"
-
-#: ./doc/user-guide/app_cheat_sheet.xml72(td)
-msgid "List images you can access"
-msgstr "アクセス可能なイメージの一覧表示"
-
-#: ./doc/user-guide/app_cheat_sheet.xml78(td)
-msgid "Delete specified image"
-msgstr "指定したイメージの"
-
-#: ./doc/user-guide/app_cheat_sheet.xml80(replaceable)
-#: ./doc/user-guide/app_cheat_sheet.xml86(replaceable)
-#: ./doc/user-guide/app_cheat_sheet.xml92(replaceable)
-#: ./doc/user-guide/app_cheat_sheet.xml166(replaceable)
-#: ./doc/user-guide/app_cheat_sheet.xml266(replaceable)
-msgid "IMAGE"
-msgstr "IMAGE"
-
-#: ./doc/user-guide/app_cheat_sheet.xml84(td)
-msgid "Describe a specific image"
-msgstr "指定したイメージの詳細表示"
-
-#: ./doc/user-guide/app_cheat_sheet.xml90(td)
-msgid "Update image"
-msgstr "イメージの更新"
-
-#: ./doc/user-guide/app_cheat_sheet.xml99(td)
-msgid "Kernel image"
-msgstr "カーネルイメージ"
-
-#: ./doc/user-guide/app_cheat_sheet.xml107(td)
-msgid "RAM image"
-msgstr "RAM イメージ"
-
-#: ./doc/user-guide/app_cheat_sheet.xml115(td)
-msgid "Three-part image"
-msgstr "3 分割イメージ"
-
-#: ./doc/user-guide/app_cheat_sheet.xml124(td)
-msgid "Register raw image"
-msgstr "raw イメージの登録"
-
-#: ./doc/user-guide/app_cheat_sheet.xml135(caption)
-msgid "Compute (nova)"
-msgstr "Compute (nova)"
-
-#: ./doc/user-guide/app_cheat_sheet.xml146(td)
-msgid "List instances, notice status of instance"
-msgstr "インスタンス、その状態の一覧表示"
-
-#: ./doc/user-guide/app_cheat_sheet.xml158(td)
-msgid "List flavors"
-msgstr "フレーバーの一覧表示"
-
-#: ./doc/user-guide/app_cheat_sheet.xml164(td)
-msgid "Boot an instance using flavor and image names (if names are unique)"
-msgstr "フレーバーとイメージ名 (名前が一意な場合) を用いたインスタンスの起動"
-
-#: ./doc/user-guide/app_cheat_sheet.xml166(replaceable)
-#: ./doc/user-guide/app_cheat_sheet.xml258(replaceable)
-msgid "FLAVOR"
-msgstr "FLAVOR"
-
-#: ./doc/user-guide/app_cheat_sheet.xml166(replaceable)
-msgid "INSTANCE_NAME"
-msgstr "INSTANCE_NAME"
-
-#: ./doc/user-guide/app_cheat_sheet.xml172(td)
-msgid "Login to instance"
-msgstr "インスタンスへのログイン"
-
-#: ./doc/user-guide/app_cheat_sheet.xml175(replaceable)
-msgid "NETNS_NAME"
-msgstr "NETNS_NAME"
-
-#: ./doc/user-guide/app_cheat_sheet.xml175(replaceable)
-msgid "USER"
-msgstr "USER"
-
-#: ./doc/user-guide/app_cheat_sheet.xml175(replaceable)
-msgid "SERVER"
-msgstr "SERVER"
-
-#: ./doc/user-guide/app_cheat_sheet.xml178(para)
-msgid ""
-"Note, in CirrOS the password for user <literal>cirros</literal> is "
-"\"cubswin:)\" without the quotes."
-msgstr "注: CirrOS の <literal>cirros</literal> のパスワードは「cubswin:)」です。"
-
-#: ./doc/user-guide/app_cheat_sheet.xml184(td)
-msgid "Show details of instance"
-msgstr "インスタンスの詳細表示"
-
-#: ./doc/user-guide/app_cheat_sheet.xml191(td)
-msgid "View console log of instance"
-msgstr "インスタンスのコンソールログの表示"
-
-#: ./doc/user-guide/app_cheat_sheet.xml197(td)
-msgid "Set metadata on an instance"
-msgstr "インスタンスのメタデータの設定"
-
-#: ./doc/user-guide/app_cheat_sheet.xml203(td)
-#: ./doc/user-guide/section_dashboard_launch_instances.xml69(title)
-msgid "Create an instance snapshot"
-msgstr "インスタンスのスナップショットの作成"
-
-#: ./doc/user-guide/app_cheat_sheet.xml210(th)
-msgid "Pause, suspend, stop, rescue, resize, rebuild, reboot an instance"
-msgstr "インスタンスの一時停止、休止、停止、レスキュー、リサイズ、再作成、リブート"
-
-#: ./doc/user-guide/app_cheat_sheet.xml213(td)
-msgid "Pause"
-msgstr "一時停止"
-
-#: ./doc/user-guide/app_cheat_sheet.xml220(td)
-msgid "Unpause"
-msgstr "一時停止解除"
-
-#: ./doc/user-guide/app_cheat_sheet.xml226(td)
-msgid "Suspend"
-msgstr "休止"
-
-#: ./doc/user-guide/app_cheat_sheet.xml232(td)
-msgid "Unsuspend"
-msgstr "休止解除"
-
-#: ./doc/user-guide/app_cheat_sheet.xml238(td)
-msgid "Stop"
-msgstr "停止"
-
-#: ./doc/user-guide/app_cheat_sheet.xml244(td)
-msgid "Start"
-msgstr "開始"
-
-#: ./doc/user-guide/app_cheat_sheet.xml250(td)
-msgid "Rescue"
-msgstr "レスキュー"
-
-#: ./doc/user-guide/app_cheat_sheet.xml256(td)
-msgid "Resize"
-msgstr "リサイズ"
-
-#: ./doc/user-guide/app_cheat_sheet.xml264(td)
-msgid "Rebuild"
-msgstr "再作成"
-
-#: ./doc/user-guide/app_cheat_sheet.xml271(td)
-msgid "Reboot"
-msgstr "リブート"
-
-#: ./doc/user-guide/app_cheat_sheet.xml278(td)
-msgid "Inject user data and files into an instance"
-msgstr "ユーザーデータとファイルのインスタンスへの注入"
-
-#: ./doc/user-guide/app_cheat_sheet.xml280(replaceable)
-msgid "FILE"
-msgstr "FILE"
-
-#: ./doc/user-guide/app_cheat_sheet.xml280(replaceable)
-msgid "INSTANCE"
-msgstr "INSTANCE"
-
-#: ./doc/user-guide/app_cheat_sheet.xml284(para)
-msgid ""
-"To validate that the file is there, ssh into the instance, and look in "
-"<filename>/var/lib/cloud</filename> for the file."
-msgstr "ファイルが注入されたことを確認する場合、インスタンスに SSH し、<filename>/var/lib/cloud</filename> にあるファイルを探します。"
-
-#: ./doc/user-guide/app_cheat_sheet.xml290(th)
-msgid ""
-"Inject a keypair into an instance and access the instance with that keypair"
-msgstr "インスタンスへのキーペアの注入、キーペアを用いたインスタンスへのアクセス"
-
-#: ./doc/user-guide/app_cheat_sheet.xml294(td)
-msgid "Create keypair"
-msgstr "キーペアの作成"
-
-#: ./doc/user-guide/app_cheat_sheet.xml301(td)
-msgid "Boot"
-msgstr "起動"
-
-#: ./doc/user-guide/app_cheat_sheet.xml308(td)
-msgid "Use ssh to connect to the instance"
-msgstr "インスタンスに接続するための SSH の利用"
-
-#: ./doc/user-guide/app_cheat_sheet.xml315(th)
-msgid "Manage security groups"
-msgstr "セキュリティグループの管理"
-
-#: ./doc/user-guide/app_cheat_sheet.xml318(td)
-msgid ""
-"Add rules to default security group allowing ping and SSH between instances "
-"in the default security group"
-msgstr "default セキュリティグループでインスタンス間の ping と SSH を許可するルールの default セキュリティグループへの追加"
-
-#: ./doc/user-guide/app_cheat_sheet.xml328(caption)
-msgid "Networking (neutron)"
-msgstr "Networking (neutron)"
-
-#: ./doc/user-guide/app_cheat_sheet.xml345(td)
-msgid "Create a subnet"
-msgstr "サブネットの作成"
-
-#: ./doc/user-guide/app_cheat_sheet.xml347(replaceable)
-msgid "NETWORK_NAME"
-msgstr "NETWORK_NAME"
-
-#: ./doc/user-guide/app_cheat_sheet.xml352(td)
-msgid "List network and subnet"
-msgstr "ネットワークとサブネットの一覧表示"
-
-#: ./doc/user-guide/app_cheat_sheet.xml359(td)
-msgid "Examine details of network and subnet"
-msgstr "ネットワークとサブネットの詳細表示"
-
-#: ./doc/user-guide/app_cheat_sheet.xml361(replaceable)
-#: ./doc/user-guide/app_cheat_sheet.xml362(replaceable)
-msgid "ID_OR_NAME_OF_NETWORK"
-msgstr "ID_OR_NAME_OF_NETWORK"
-
-#: ./doc/user-guide/app_cheat_sheet.xml369(caption)
-msgid "Block Storage (cinder)"
-msgstr "Block Storage (cinder)"
-
-#: ./doc/user-guide/app_cheat_sheet.xml380(th)
-msgid "Manage volumes and volume snapshots"
-msgstr "ボリュームとボリュームスナップショットの管理"
-
-#: ./doc/user-guide/app_cheat_sheet.xml383(td)
-msgid "Create a new volume"
-msgstr "新しいボリュームの作成"
-
-#: ./doc/user-guide/app_cheat_sheet.xml385(replaceable)
-msgid "SIZE_IN_GB"
-msgstr "SIZE_IN_GB"
-
-#: ./doc/user-guide/app_cheat_sheet.xml390(td)
-msgid "Boot an instance and attach to volume"
-msgstr "インスタンスの起動およびボリュームの接続"
-
-#: ./doc/user-guide/app_cheat_sheet.xml396(td)
-msgid "List volumes, notice status of volume"
-msgstr "ボリューム、その状態の一覧表示"
-
-#: ./doc/user-guide/app_cheat_sheet.xml402(td)
-msgid ""
-"Attach volume to instance after instance is active, and volume is available"
-msgstr "インスタンス起動後、ボリューム作成後のインスタンスへのボリュームの接続"
-
-#: ./doc/user-guide/app_cheat_sheet.xml405(replaceable)
-msgid "INSTANCE_ID"
-msgstr "INSTANCE_ID"
-
-#: ./doc/user-guide/app_cheat_sheet.xml405(replaceable)
-msgid "VOLUME_ID"
-msgstr "VOLUME_ID"
-
-#: ./doc/user-guide/app_cheat_sheet.xml410(th)
-msgid "Manage volumes after login into the instance"
-msgstr "インスタンスへのログイン後のボリュームの管理"
-
-#: ./doc/user-guide/app_cheat_sheet.xml413(td)
-msgid "List storage devices"
-msgstr "ストレージデバイスの一覧表示"
-
-#: ./doc/user-guide/app_cheat_sheet.xml419(td)
-msgid "Make filesystem on volume"
-msgstr "ボリュームのファイルシステムの作成"
-
-#: ./doc/user-guide/app_cheat_sheet.xml425(td)
-msgid "Create a mountpoint"
-msgstr "マウントポイントの作成"
-
-#: ./doc/user-guide/app_cheat_sheet.xml431(td)
-msgid "Mount the volume at the mountpoint"
-msgstr "マウントポイントへのボリュームのマウント"
-
-#: ./doc/user-guide/app_cheat_sheet.xml437(td)
-msgid "Create a file on the volume"
-msgstr "ボリュームへのファイルの作成"
-
-#: ./doc/user-guide/app_cheat_sheet.xml444(td)
-msgid "Unmount the volume"
-msgstr "ボリュームのアンマウント"
-
-#: ./doc/user-guide/app_cheat_sheet.xml453(caption)
-msgid "Object Storage (swift)"
-msgstr "Object Storage (swift)"
-
-#: ./doc/user-guide/app_cheat_sheet.xml464(td)
-msgid "Display information for the account, container, or object"
-msgstr "アカウント、コンテナー、オブジェクトの情報表示"
-
-#: ./doc/user-guide/app_cheat_sheet.xml467(replaceable)
-msgid "ACCOUNT"
-msgstr "ACCOUNT"
-
-#: ./doc/user-guide/app_cheat_sheet.xml469(replaceable)
-msgid "OBJECT"
-msgstr "OBJECT"
-
-#: ./doc/user-guide/app_cheat_sheet.xml473(td)
-msgid "List containers"
-msgstr "コンテナーの一覧表示"
-
-#: ./doc/user-guide/app_cheat_sheet.xml479(td)
-#: ./doc/user-guide/section_dashboard_manage_containers.xml19(title)
-msgid "Create a container"
-msgstr "コンテナーの作成"
-
-#: ./doc/user-guide/app_cheat_sheet.xml481(replaceable)
-#: ./doc/user-guide/app_cheat_sheet.xml487(replaceable)
-#: ./doc/user-guide/app_cheat_sheet.xml500(replaceable)
-#: ./doc/user-guide/app_cheat_sheet.xml506(replaceable)
-msgid "CONTAINER_NAME"
-msgstr "CONTAINER_NAME"
-
-#: ./doc/user-guide/app_cheat_sheet.xml485(td)
-msgid "Upload file to a container"
-msgstr "コンテナーへのファイルのアップロード"
-
-#: ./doc/user-guide/app_cheat_sheet.xml487(replaceable)
-#: ./doc/user-guide/app_cheat_sheet.xml500(replaceable)
-#: ./doc/user-guide/app_cheat_sheet.xml506(replaceable)
-msgid "FILE_NAME"
-msgstr "FILE_NAME"
-
-#: ./doc/user-guide/app_cheat_sheet.xml492(td)
-msgid "List objects in container"
-msgstr "コンテナーにあるオブジェクトの一覧表示"
-
-#: ./doc/user-guide/app_cheat_sheet.xml498(td)
-msgid "Download object from container"
-msgstr "コンテナーからのオブジェクトのダウンロード"
-
-#: ./doc/user-guide/app_cheat_sheet.xml504(td)
-msgid "Upload with chunks, for large file"
-msgstr "チャンク化した大きなファイルのアップロード"
-
-#: ./doc/user-guide/app_cheat_sheet.xml506(replaceable)
-msgid "SIZE"
-msgstr "SIZE"
-
-#: ./doc/user-guide/section_sdk_auth_keystone.xml6(title)
-msgid "Authenticate against an Identity endpoint"
-msgstr "Identity エンドポイントへの認証"
-
-#: ./doc/user-guide/section_sdk_auth_keystone.xml7(para)
-msgid ""
-"To authenticate against the Identity v2.0 endpoint, instantiate a <link "
-"href=\"http://docs.openstack.org/developer/python-"
-"keystoneclient/api/keystoneclient.v2_0.client.html#keystoneclient.v2_0.client.Client\">"
-" keystoneclient.v_20.client.Client</link> object:"
-msgstr "Identity v2.0 エンドポイントに認証するために、<link href=\"http://docs.openstack.org/developer/python-keystoneclient/api/keystoneclient.v2_0.client.html#keystoneclient.v2_0.client.Client\"> keystoneclient.v_20.client.Client</link> オブジェクトのインスタンスを生成します。"
-
-#: ./doc/user-guide/section_sdk_auth_keystone.xml18(para)
-msgid ""
-"After you instantiate a <classname>Client</classname> object, you can "
-"retrieve the token by accessing its <literal>auth_token</literal> attribute "
-"object:"
-msgstr "<classname>Client</classname> オブジェクトのインスタンスを生成した後、その <literal>auth_token</literal> 属性のオブジェクトにアクセスすることにより、トークンを取得できます。"
-
-#: ./doc/user-guide/section_sdk_auth_keystone.xml24(para)
-msgid ""
-"If the OpenStack cloud is configured to use public-key infrastructure (PKI) "
-"tokens, the Python script output looks something like this:"
-msgstr "OpenStack クラウドが PKI トークンを使用するよう設定されている場合、Python スクリプトの出力は以下のようになるでしょう。"
-
-#: ./doc/user-guide/section_sdk_auth_keystone.xml35(para)
-msgid ""
-"This example shows a subset of a PKI token. A complete token is over 5000 "
-"characters long."
-msgstr "この例は PKI トークンの一部分を示します。完全なトークンは 5000 文字以上です。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml6(title)
-msgid "Launch and manage instances"
-msgstr "インスタンスの起動と管理"
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml7(para)
-msgid "Instances are virtual machines that run inside the cloud."
-msgstr "インスタンスはクラウド内で動作する仮想マシンです。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml9(para)
-msgid ""
-"You can <link linkend=\"dashboard_launch_instances_from_image\">launch an "
-"instance</link> from the following sources:"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml12(para)
-msgid ""
-"Images uploaded to the OpenStack Image Service, as described in <xref "
-"linkend=\"dashboard_manage_images\"/>."
-msgstr "<xref linkend=\"dashboard_manage_images\"/>に記載されているとおり、OpenStack Image Service にアップロードされたイメージ。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml14(para)
-msgid ""
-"Image that you have copied to a persistent volume. The instance launches "
-"from the volume, which is provided by the <systemitem class=\"service"
-"\">cinder-volume</systemitem> API through iSCSI."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml23(title)
-msgid "Connect to your instance by using SSH"
-msgstr "インスタンスへの SSH 接続"
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml24(para)
-msgid ""
-"To use SSH to connect to your instance, you use the downloaded keypair file."
-msgstr "インスタンスに SSH 接続するために、ダウンロードしたキーペアファイルを使用します。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml27(para)
-msgid ""
-"The user name is <literal>ubuntu</literal> for the Ubuntu cloud images on "
-"TryStack."
-msgstr "TryStack の Ubuntu クラウドイメージのユーザー名は <literal>ubuntu</literal> です。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml32(para)
-msgid "Copy the IP address for your instance."
-msgstr "インスタンスの IP アドレスをコピーします。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml35(para)
-msgid ""
-"Use the <placeholder-1/> command to make a secure connection to the "
-"instance. For example:"
-msgstr "インスタンスにセキュアに接続するために <placeholder-1/> コマンドを使用します。例:"
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml41(para)
-msgid "At the prompt, type <literal>yes</literal>."
-msgstr "プロンプトに <literal>yes</literal> と入力します。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml47(title)
-msgid "Track usage for instances"
-msgstr "インスタンスの使用状況の確認"
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml48(para)
-msgid ""
-"You can track usage for instances for each project. You can track costs per "
-"month by showing metrics like number of vCPUs, disks, RAM, and uptime for "
-"all your instances."
-msgstr "プロジェクトごとのインスタンスの使用状況を確認できます。すべてのインスタンスの仮想 CPU 数、ディスク、メモリ、起動時間のような測定項目を表示することにより、月ごとのコストを確認できます。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml54(para)
-msgid ""
-"Log in to the dashboard, choose a project, and click "
-"<guilabel>Overview</guilabel>."
-msgstr "ダッシュボードにログインし、プロジェクトを選択し、<guibutton>概要</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml58(para)
-msgid ""
-"To query the instance usage for a month, select a month and click "
-"<guibutton>Submit</guibutton>."
-msgstr "ある月のインスタンス使用状況を問い合わせるために、月を選択し、<guibutton>送信</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml63(para)
-msgid ""
-"To download a summary, click <guibutton>Download CSV Summary</guibutton>."
-msgstr "概要をダウンロードするために、<guibutton>概要 CSV のダウンロード</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml72(para)
-#: ./doc/user-guide/section_dashboard_launch_instances.xml98(para)
-msgid ""
-"Log in to the dashboard, choose a project, and click "
-"<guilabel>Instances</guilabel>."
-msgstr "ダッシュボードにログインし、プロジェクトを選択し、<guilabel>インスタンス</guilabel>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml76(para)
-msgid "Select the instance from which to create a snapshot."
-msgstr "スナップショットを作成するインスタンスを選択します。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml79(para)
-msgid ""
-"In the <guilabel>Actions</guilabel> column, click <guilabel>Create "
-"Snapshot</guilabel>."
-msgstr "<guilabel>操作</guilabel>の列で、<guilabel>スナップショットの作成</guilabel>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml83(para)
-msgid ""
-"In the Create Snapshot dialog box, enter a name for the snapshot, and click "
-"<guibutton>Create Snapshot</guibutton>."
-msgstr "スナップショットの作成ダイアログボックスで、スナップショットの名前を入力し、<guibutton>スナップショットの作成</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml85(para)
-msgid "The <guilabel>Images</guilabel> category shows the instance snapshot."
-msgstr "インスタンスのスナップショットが<guilabel>イメージ</guilabel>カテゴリーに表示されます。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml89(para)
-msgid ""
-"To launch an instance from the snapshot, select the snapshot and click "
-"<guibutton>Launch</guibutton>. Proceed with <xref "
-"linkend=\"dashboard_launch_instances_from_image\"/>."
-msgstr "スナップショットからインスタンスを起動するために、スナップショットを選択し、<guibutton>起動</guibutton>をクリックします。<xref linkend=\"dashboard_launch_instances_from_image\"/>に進みます。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml95(title)
-msgid "Manage an instance"
-msgstr "インスタンスの管理"
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml102(para)
-msgid "Select an instance."
-msgstr "インスタンスを選択します。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml105(para)
-msgid ""
-"In the <guilabel>More</guilabel> list in the <guilabel>Actions</guilabel> "
-"column, select the state."
-msgstr "<guilabel>アクション</guilabel>列の<guilabel>▼</guilabel>ドロップダウンリストで状態を選択します。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml107(para)
-msgid ""
-"You can resize or rebuild an instance. You can also choose to view the "
-"instance console log, edit instance or the security groups. Depending on the"
-" current state of the instance, you can pause, resume, suspend, soft or hard"
-" reboot, or terminate it."
-msgstr "インスタンスのリサイズや再構築をできます。インスタンスのコンソールログを表示するため、インスタンスやセキュリティグループを編集するためにも選択できます。インスタンスの現在の状態によって、インスタンスを一時停止、再開、サスペンド、ソフトリブート、ハードリブート、終了できます。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml10(title)
-msgid "Launch an instance"
-msgstr "インスタンスの起動"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml12(para)
-msgid ""
-"When you launch an instance from an image, OpenStack creates a local copy of"
-" the image on the compute node where the instance starts."
-msgstr "イメージからインスタンスを起動するとき、OpenStack はインスタンスが起動するコンピュートノードにイメージのローカルコピーを作成します。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml14(para)
-msgid "When you launch an instance from a volume, note the following steps:"
-msgstr "ボリュームからインスタンスを起動するとき、以下の手順に注意してください。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml18(para)
-msgid ""
-"To select the volume to from which to launch, launch an instance from an "
-"arbitrary image on the volume. The image that you select does not boot. "
-"Instead, it is replaced by the image on the volume that you choose in the "
-"next steps."
-msgstr "起動するボリュームを選択する場合、ボリュームにある任意のイメージからインスタンスを起動します。選択したイメージは起動しません。代わりに、次の手順で選択したボリュームにあるイメージにより置き換えられます。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml22(para)
-msgid ""
-"To boot a Xen image from a volume, the image you launch in must be the same "
-"type, fully virtualized or paravirtualized, as the one on the volume."
-msgstr "ボリュームから Xen イメージを起動するために、起動するイメージは、ボリュームにあるものと同じ形式、完全仮想化または準仮想化である必要があります。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml27(para)
-msgid ""
-"Select the volume or volume snapshot from which to boot. Enter a device "
-"name. Enter <literal>vda</literal> for KVM images or <literal>xvda</literal>"
-" for Xen images."
-msgstr "起動するためのボリュームまたはボリュームのスナップショットを選択します。デバイス名を入力します。KVM イメージの場合は <literal>vda</literal>、Xen イメージの場合は <literal>xvda</literal> を入力します。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml34(para)
-msgid ""
-"Log in to the dashboard, choose a project, and click "
-"<guilabel>Images</guilabel>."
-msgstr "ダッシュボードにログインし、プロジェクトを選択し、<guilabel>イメージ</guilabel>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml36(para)
-msgid ""
-"The dashboard shows the images that have been uploaded to OpenStack Image "
-"Service and are available for this project."
-msgstr "ダッシュボードは、OpenStack Image Service にアップロードされた、このプロジェクトが利用可能なイメージを表示します。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml39(para)
-msgid ""
-"For details on creating images, see <link href=\"http://docs.openstack.org"
-"/image-guide/content/ch_creating_images_manually.html\">Creating images "
-"manually</link> in the <citetitle>OpenStack Virtual Machine Image "
-"Guide</citetitle>."
-msgstr "イメージの作成に関する詳細は、<citetitle>OpenStack Virtual 仮想マシンイメージガイド</citetitle>の<link href=\"http://docs.openstack.org/image-guide/content/ch_creating_images_manually.html\">イメージの手動作成</link>を参照してください。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml45(para)
-msgid "Select an image and click <guibutton>Launch</guibutton>."
-msgstr "イメージを選択し、<guibutton>起動</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml48(para)
-msgid "In the Launch Instance dialog box, specify the following values:"
-msgstr "インスタンスの起動ダイアログボックスで、以下の値を指定します。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml55(guilabel)
-msgid "Details"
-msgstr "詳細"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml60(guilabel)
-msgid "Availability Zone"
-msgstr "アベイラビリティゾーン"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml62(para)
-msgid ""
-"By default, this value is set to the availability zone given by the cloud "
-"provider (for example, <literal>us-west</literal> or <literal>apac-"
-"south</literal>). For some cases, it could be <literal>nova</literal>."
-msgstr "この値はデフォルトで、クラウドプロバイダーにより指定されたアベイラビリティゾーンに設定されます (例えば、<literal>us-west</literal>、<literal>apac-south</literal>)。<literal>nova</literal> となっている場合もあります。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml69(guilabel)
-msgid "Instance Name"
-msgstr "インスタンス名"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml70(para)
-msgid "Assign a name to the virtual machine."
-msgstr "仮想マシンに名前を割り当てます。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml71(para)
-msgid ""
-"The name you assign here becomes the initial host name of the server. After "
-"the server is built, if you change the server name in the API or change the "
-"host name directly, the names are not updated in the dashboard."
-msgstr "ここで割り当てた名前が、サーバーの初期ホスト名になります。サーバー稼働後、API でサーバー名を変更した場合、ホスト名を直接変更した場合、ダッシュボードに表示される名前は更新されません。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml75(para)
-msgid ""
-"Server names are not guaranteed to be unique when created so you could have "
-"two instances with the same host name."
-msgstr "サーバー名は一意性が保証されていません。そのため、同じ名前を持つインスタンスを 2 つ起動する可能性があります。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml82(guilabel)
-msgid "Flavor"
-msgstr "フレーバー"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml83(para)
-msgid "Specify the size of the instance to launch."
-msgstr "起動するインスタンスの大きさを指定します。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml84(para)
-msgid ""
-"The flavor is selected based on the size of the image selected for launching"
-" an instance. For example, while creating an image, if you have entered the "
-"value in the <guilabel>Minimum RAM (MB)</guilabel> field as 2048, then on "
-"selecting the image, the default flavor is <guilabel>m1.small</guilabel>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml94(guilabel)
-msgid "Instance Count"
-msgstr "インスタンス数"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml95(para)
-msgid ""
-"To launch multiple instances, enter a value greater than 1. The default is "
-"1."
-msgstr "複数のインスタンスを起動する場合、1 より大きな値を入力します。初期値は 1 です。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml99(guilabel)
-msgid "Instance Boot Source"
-msgstr "インスタンスのブートソース"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml100(para)
-msgid "Your options are:"
-msgstr "以下のオプションがあります。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml103(guilabel)
-msgid "Boot from image"
-msgstr "イメージから起動"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml104(para)
-msgid ""
-"If you choose this option, a new field for <guilabel>Image Name</guilabel> "
-"displays. You can select the image from the list."
-msgstr "このオプションを選択する場合、<guilabel>イメージ名</guilabel>の新項目が表示されます。この一覧からイメージを選択できます。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml109(guilabel)
-msgid "Boot from snapshot"
-msgstr "スナップショットから起動"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml110(para)
-msgid ""
-"If you choose this option, a new field for <guilabel>Instance "
-"Snapshot</guilabel> displays. You can select the snapshot from the list."
-msgstr "このオプションを選択する場合、<guilabel>インスタンスのスナップショット</guilabel>の新項目が表示されます。この一覧からスナップショットを選択できます。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml115(guilabel)
-msgid "Boot from volume"
-msgstr "ボリュームから起動"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml116(para)
-msgid ""
-"If you choose this option, a new field for <guilabel>Volume</guilabel> "
-"displays. You can select the volume from the list."
-msgstr "このオプションを選択する場合、<guilabel>ボリューム</guilabel>の新項目が表示されます。この一覧からボリュームを選択できます。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml121(guilabel)
-msgid "Boot from image (creates a new volume)"
-msgstr "イメージから起動 (新しいボリュームを作成)"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml122(para)
-msgid ""
-"With this option, you can boot from an image and create a volume by entering"
-" the <guilabel>Device Size</guilabel> and <guilabel>Device Name</guilabel> "
-"for your volume. Click the <guilabel>Delete on Terminate</guilabel> option "
-"to delete the volume on terminating the instance."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml130(guilabel)
-msgid "Boot from volume snapshot (creates a new volume)"
-msgstr "ボリュームのスナップショットから起動 (新しいボリュームを作成)"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml132(para)
-msgid ""
-"Using this option, you can boot from a volume snapshot and create a new "
-"volume by choosing <guilabel>Volume Snapshot</guilabel> from a list and "
-"adding a <guilabel>Device Name</guilabel> for your volume. Click the "
-"<guilabel>Delete on Terminate</guilabel> option to delete the volume on "
-"terminating the instance."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml141(para)
-msgid ""
-"Since you are launching an instance from an image, <guilabel>Boot from "
-"image</guilabel> is chosen by default."
-msgstr "イメージからインスタンスを起動するため、<guilabel>イメージから起動</guilabel>が初めから選択されています。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml147(guilabel)
-msgid "Image Name"
-msgstr "イメージ名"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml148(para)
-msgid ""
-"This field changes based on your previous selection. Since you have chosen "
-"to launch an instance using an image, the <guilabel>Image Name</guilabel> "
-"field displays. Select the image name from the dropdown list."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml155(guilabel)
-msgid "Access &amp; Security"
-msgstr "アクセスとセキュリティ"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml159(guilabel)
-msgid "Keypair"
-msgstr "キーペア"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml160(para)
-msgid "Specify a key pair."
-msgstr "キーペアを指定します。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml161(para)
-msgid ""
-"If the image uses a static root password or a static key set (neither is "
-"recommended), you do not need to provide a key pair to launch the instance."
-msgstr "イメージが固定の root パスワードまたは固定のキーセットを使用する場合 (どちらも推奨されません)、インスタンスを起動するためにキーペアを提供する必要がありません。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml166(guilabel)
-msgid "Security Groups"
-msgstr "セキュリティグループ"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml167(para)
-msgid "Activate the security groups that you want to assign to the instance."
-msgstr "インスタンスに割り当てたいセキュリティグループを有効化します。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml169(para)
-msgid ""
-"Security groups are a kind of cloud firewall that define which incoming "
-"network traffic is forwarded to instances. For details, see <xref "
-"linkend=\"security_groups_add_rule\"/>."
-msgstr "セキュリティグループはある種のクラウドファイアウォールです。どの入力ネットワーク通信がインスタンスに転送されるのかを定義します。詳細は<xref linkend=\"security_groups_add_rule\"/>を参照してください。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml173(para)
-msgid ""
-"If you have not created any security groups, you can assign only the default"
-" security group to the instance."
-msgstr "セキュリティグループを何も作成していなければ、標準のセキュリティグループのみをインスタンスに割り当てられます。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml181(guilabel)
-msgid "Selected Networks"
-msgstr "選択済みネットワーク"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml182(para)
-msgid ""
-"To add a network to the instance, click the <guibutton>+</guibutton> in the "
-"<guilabel>Available Networks</guilabel> field."
-msgstr "インスタンスにネットワークを追加するために、<guilabel>利用可能なネットワーク</guilabel>欄にある <guibutton>+</guibutton> をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml188(guilabel)
-msgid "Post-Creation"
-msgstr "作成後"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml191(guilabel)
-msgid "Customization Script"
-msgstr "カスタマイズ・スクリプト"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml192(para)
-msgid "Specify a customization script that runs after your instance launches."
-msgstr "インスタンスの起動後に実行するカスタマイズスクリプトを指定します。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml196(guilabel)
-msgid "Advanced Options"
-msgstr "高度な設定"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml199(guilabel)
-msgid "Disk Partition"
-msgstr "ディスクパーティション"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml200(para)
-msgid "Select the type of disk partition from the dropdown list."
-msgstr "ドロップダウンリストからディスクパーティションの種類を選択します。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml204(guilabel)
-msgid "Automatic"
-msgstr "自動"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml206(para)
-msgid "Entire disk is single partition and automatically resizes."
-msgstr "ディスク全体が単一パーティションになり、自動的にリサイズされます。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml210(guilabel)
-msgid "Manual"
-msgstr "手動"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml212(para)
-msgid "Faster build times but requires manual partitioning."
-msgstr "構築時間は早いですが、手動でパーティション作成する必要があります。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml231(para)
-msgid "Click <guibutton>Launch</guibutton>."
-msgstr "<guibutton>起動</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml232(para)
-msgid "The instance starts on a compute node in the cloud."
-msgstr "インスタンスがクラウドのコンピュートノードで起動します。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml235(para)
-msgid ""
-"The <guilabel>Instances</guilabel> tab shows the instance's name, its "
-"private and public IP addresses, size, status, task, and power state."
-msgstr "<guilabel>インスタンス</guilabel>タブに、インスタンス名、プライベート IP アドレス、パブリック IP アドレス、大きさ、状態、処理、電源状態が表示されます。"
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml238(para)
-msgid ""
-"If you did not provide a key pair, security groups, or rules, users can "
-"access the instance only from inside the cloud through VNC. Even pinging the"
-" instance is not possible without an ICMP rule configured. To access the "
-"instance through a VNC console, see <xref linkend=\"instance_console\"/>."
-msgstr "キーペア、セキュリティグループ、ルールなどを指定していない場合、ユーザーは VNC 経由でクラウドの中からのみインスタンスにアクセスできます。ICMP のルールを設定していなければ、インスタンスに ping できないでしょう。VNC コンソールからインスタンスにアクセスする方法は、<xref linkend=\"instance_console\"/>を参照してください。"
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml6(title)
-msgid "Create and manage object containers"
-msgstr "オブジェクトコンテナーの作成と管理"
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml8(para)
-msgid ""
-"OpenStack Object Storage provides a distributed, API-accessible storage "
-"platform that can be integrated directly into an application or used to "
-"store any type of file, including VM images, backups, archives, or media "
-"files. In the OpenStack Dashboard, you can only manage containers and "
-"objects."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml13(para)
-msgid ""
-"In OpenStack Object Storage, containers provide storage for objects in a "
-"manner similar to a Windows folder or Linux file directory, though they "
-"cannot be nested. An object in OpenStack consists of the file to be stored "
-"in the container and any accompanying metadata."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml22(para)
-#: ./doc/user-guide/section_dashboard_manage_containers.xml44(para)
-#: ./doc/user-guide/section_dashboard_manage_containers.xml79(para)
-#: ./doc/user-guide/section_dashboard_manage_containers.xml103(para)
-#: ./doc/user-guide/section_dashboard_manage_containers.xml144(para)
-#: ./doc/user-guide/section_dashboard_manage_containers.xml171(para)
-msgid ""
-"Log in to the dashboard, choose a project, and click "
-"<guilabel>Containers</guilabel>."
-msgstr "ダッシュボードにログインし、プロジェクトを選択し、<guilabel>コンテナー</guilabel>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml26(para)
-msgid "Click <guibutton>Create Container</guibutton>."
-msgstr "<guibutton>コンテナーの作成</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml29(para)
-msgid ""
-"In the Create Container dialog box, enter a name for the container, and then"
-" click<guibutton>Create Container</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml34(para)
-msgid "You have successfully created a container."
-msgstr "コンテナーが正常に作成されました。"
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml35(para)
-msgid ""
-"To delete a container, click the <guibutton>More</guibutton> button and "
-"select <guilabel>Delete Container</guilabel>."
-msgstr "コンテナーを削除する場合、<guibutton>▼</guibutton>ドロップダウンボタンをクリックし、<guilabel>コンテナーの削除</guilabel>を選択します。"
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml41(title)
-msgid "Upload an object"
-msgstr "オブジェクトのアップロード"
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml48(para)
-#: ./doc/user-guide/section_dashboard_manage_containers.xml83(para)
-#: ./doc/user-guide/section_dashboard_manage_containers.xml107(para)
-#: ./doc/user-guide/section_dashboard_manage_containers.xml148(para)
-#: ./doc/user-guide/section_dashboard_manage_containers.xml175(para)
-msgid "Select the container in which you want to store your object."
-msgstr "オブジェクトを保存したいコンテナーを選択します。"
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml51(para)
-#: ./doc/user-guide/section_dashboard_manage_containers.xml66(para)
-#: ./doc/user-guide/section_dashboard_manage_containers.xml151(para)
-msgid "Click <guibutton>Upload Object</guibutton>."
-msgstr "<guibutton>オブジェクトのアップロード</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml52(para)
-#: ./doc/user-guide/section_dashboard_manage_containers.xml152(para)
-msgid ""
-"The Upload Object To Container: <replaceable>&lt;name&gt;</replaceable> "
-"dialog box is displayed. <replaceable>&lt;name&gt;</replaceable> is the name"
-" of the container to which you are uploading the object."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml59(para)
-#: ./doc/user-guide/section_dashboard_manage_containers.xml159(para)
-msgid "Enter a name for the object."
-msgstr "オブジェクトの名前を入力します。"
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml62(para)
-#: ./doc/user-guide/section_dashboard_manage_containers.xml90(para)
-msgid "Browse to and select the file that you want to upload."
-msgstr "アップロードしたいファイルを選択します。"
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml69(para)
-msgid "You have successfully uploaded an object to the container."
-msgstr "オブジェクトをコンテナーに正常にアップロードしました。"
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml70(para)
-#: ./doc/user-guide/section_dashboard_manage_containers.xml97(para)
-msgid ""
-"To delete an object, click the <guibutton>More</guibutton> button and select"
-" <guilabel>Delete Object</guilabel>."
-msgstr "オブジェクトを削除する場合、<guibutton>▼</guibutton>ボタンをクリックし、<guilabel>オブジェクトの削除</guilabel>を選択します。"
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml75(title)
-msgid "Manage an object"
-msgstr "オブジェクトの管理"
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml77(title)
-msgid "To edit an object"
-msgstr "オブジェクトの編集方法"
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml86(para)
-msgid ""
-"Click <guibutton>More</guibutton> and choose <guilabel>Edit</guilabel> from "
-"the dropdown list."
-msgstr "<guibutton>▼</guibutton>をクリックし、ドロップダウンリストから<guilabel>編集</guilabel>を選択します。"
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml87(para)
-msgid "The Edit Object dialog box is displayed."
-msgstr "オブジェクトの編集ダイアログボックスが表示されます。"
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml93(para)
-#: ./doc/user-guide/section_dashboard_manage_containers.xml162(para)
-msgid "Click <guibutton>Update Object</guibutton>."
-msgstr "<guibutton>オブジェクトの更新</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml101(title)
-msgid "To copy an object from one container to another"
-msgstr "コンテナーから別のコンテナーへのオブジェクトのコピー方法"
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml110(para)
-msgid ""
-"Click <guibutton>More</guibutton> and choose <guilabel>Copy</guilabel> from "
-"the dropdown list."
-msgstr "<guibutton>▼</guibutton>をクリックし、ドロップダウンリストから<guilabel>コピー</guilabel>を選択します。"
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml114(para)
-msgid "In the Copy Object: launch dialog box, enter the following values:"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml119(para)
-msgid ""
-"<guilabel>Destination Container</guilabel>: Choose the destination container"
-" from the list."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml123(para)
-msgid ""
-"<guilabel>Path</guilabel>: Specify a path in which the new copy should be "
-"stored inside of the selected container."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml128(para)
-msgid ""
-"<guilabel>Destination object name</guilabel>: Enter a name for the object in"
-" the new container."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml136(para)
-msgid "Click <guibutton>Copy Object</guibutton>."
-msgstr "<guibutton>オブジェクトのコピー</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml140(title)
-msgid "To create a metadata-only object without a file"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml141(para)
-msgid ""
-"You can create a new object in container without a file available and can "
-"upload the file later when it is ready. This temporary object acts a place-"
-"holder for a new object, and enables the user to share object metadata and "
-"URL info in advance."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml166(title)
-msgid "To create a pseudo-folder"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml167(para)
-msgid ""
-"Pseudo-folders are similar to folders in your desktop operating system. They"
-" are virtual collections defined by a common prefix on the object's name."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml178(para)
-msgid "Click <guibutton>Create Pseudo-folder</guibutton>."
-msgstr "<guibutton>擬似フォルダーの作成</guibutton>をクリックします。"
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml180(para)
-msgid ""
-"The Create Pseudo-Folder in Container <replaceable>&lt;name&gt; "
-"</replaceable> dialog box is displayed. <replaceable>&lt;name&gt; "
-"</replaceable> is the name of the container to which you are uploading the "
-"object."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml187(para)
-msgid "Enter a name for the pseudo-folder."
-msgstr "擬似フォルダーの名前を入力します。"
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml189(para)
-msgid ""
-"A slash (/) character is used as the delimiter for pseudo-folders in the "
-"Object Store."
-msgstr "スラッシュ (/) 文字がオブジェクトストアの擬似フォルダーの区切り文字として使用されます。"
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml193(para)
-msgid "Click <guibutton>Create</guibutton>."
-msgstr "<guibutton>作成</guibutton>をクリックします。"
-
-#: ./doc/user-guide/bk-user-guide.xml8(title)
-msgid "OpenStack End User Guide"
-msgstr "OpenStack エンドユーザーガイド"
-
-#: ./doc/user-guide/bk-user-guide.xml9(titleabbrev)
-msgid "End User Guide"
-msgstr "エンドユーザーガイド"
-
-#: ./doc/user-guide/bk-user-guide.xml17(orgname)
-#: ./doc/user-guide/bk-user-guide.xml22(holder)
-msgid "OpenStack Foundation"
-msgstr "OpenStack Foundation"
-
-#: ./doc/user-guide/bk-user-guide.xml21(year)
-msgid "2014"
-msgstr "2014"
-
-#: ./doc/user-guide/bk-user-guide.xml24(releaseinfo)
-msgid "current"
-msgstr "カレント"
-
-#: ./doc/user-guide/bk-user-guide.xml25(productname)
-msgid "OpenStack"
-msgstr "OpenStack"
-
-#: ./doc/user-guide/bk-user-guide.xml29(remark)
-msgid "Copyright details are filled in by the template."
-msgstr "Copyright details are filled in by the template."
-
-#: ./doc/user-guide/bk-user-guide.xml34(para)
-msgid ""
-"OpenStack is an open-source cloud computing platform for public and private "
-"clouds. A series of interrelated projects deliver a cloud infrastructure "
-"solution. This guide shows OpenStack end users how to create and manage "
-"resources in an OpenStack cloud with the OpenStack dashboard and OpenStack "
-"client commands."
-msgstr "OpenStack は、パブリッククラウドやプライベートクラウド向けの、オープンソースのクラウドコンピューティングプラットフォームです。一連の相互に関連するプロジェクトがクラウドインフラストラクチャーソリューションを提供します。このガイドは、OpenStack のユーザーが、OpenStack のダッシュボードやコマンドラインクライアントを用いて、OpenStack クラウドのリソースを作成および管理する方法について説明します。"
-
-#: ./doc/user-guide/bk-user-guide.xml44(date)
-msgid "2014-05-09"
-msgstr "2014-05-09"
-
-#: ./doc/user-guide/bk-user-guide.xml48(para)
-msgid "Add a command line cheat sheet."
-msgstr "コマンドラインのチートシートを追加しました。"
-
-#: ./doc/user-guide/bk-user-guide.xml55(date)
-msgid "2014-04-17"
-msgstr "2014-04-17"
-
-#: ./doc/user-guide/bk-user-guide.xml59(para)
-msgid ""
-"For the Icehouse release, this guide has been updated with changes to the "
-"dashboard plus the moving of the command reference appendix as indicated "
-"below."
-msgstr "このガイドは Icehouse リリース向けに、ダッシュボードを変更しました。また、以下に示したとおり、付録のコマンドリファレンスを移動しました。"
-
-#: ./doc/user-guide/bk-user-guide.xml69(date)
-msgid "2014-01-31"
-msgstr "2014-01-31"
-
-#: ./doc/user-guide/bk-user-guide.xml73(para)
-msgid ""
-"Removed the command reference appendix. This information is now in the <link"
-" href=\"http://docs.openstack.org/cli-"
-"reference/content/\"><citetitle>OpenStack Command-Line Interface "
-"Reference</citetitle></link>."
-msgstr "付録のコマンドリファレンスを削除しました。この情報は現在 <link href=\"http://docs.openstack.org/cli-reference/content/\"><citetitle>OpenStack コマンドラインインターフェースリファレンス</citetitle></link>にあります。"
-
-#: ./doc/user-guide/bk-user-guide.xml83(date)
-msgid "2013-12-30"
-msgstr "2013-12-30"
-
-#: ./doc/user-guide/bk-user-guide.xml87(para)
-msgid "Added the OpenStack Python SDK chapter."
-msgstr "OpenStack Python SDK に関する章を追加しました。"
-
-#: ./doc/user-guide/bk-user-guide.xml94(date)
-msgid "2013-10-17"
-msgstr "2013-10-17"
-
-#: ./doc/user-guide/bk-user-guide.xml98(para)
-msgid "Havana release."
-msgstr "Havana リリース。"
-
-#: ./doc/user-guide/bk-user-guide.xml104(date)
-msgid "2013-08-19"
-msgstr "2013-08-19"
-
-#: ./doc/user-guide/bk-user-guide.xml108(para)
-msgid "Editorial changes."
-msgstr "編集上の変更。"
-
-#: ./doc/user-guide/bk-user-guide.xml114(date)
-msgid "2013-07-29"
-msgstr "2013-07-29"
-
-#: ./doc/user-guide/bk-user-guide.xml118(para)
-msgid "First edition of this document."
-msgstr "このドキュメントの初版。"
-
-#: ./doc/user-guide/ch_dashboard.xml10(title)
-msgid "OpenStack dashboard"
-msgstr "OpenStack Dashboard"
-
-#: ./doc/user-guide/ch_dashboard.xml12(para)
-msgid ""
-"As a cloud end user, you can use the OpenStack dashboard to provision your "
-"own resources within the limits set by administrators. You can modify the "
-"examples provided in this section to create other types and sizes of server "
-"instances."
-msgstr "あなたはクラウドのエンドユーザーとして、OpenStack Dashboard (ダッシュボード) を使用できます。管理者により設定された制限の範囲内で自身のリソースを展開できます。他の種類や大きさのサーバーインスタンスを作成するために、このセクションで提供される例を変更できます。"
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml12(para)
-msgid ""
-"When you launch a virtual machine, you can inject a <emphasis "
-"role=\"italic\">key pair</emphasis>, which provides SSH access to your "
-"instance. For this to work, the image must contain the <literal>cloud-"
-"init</literal> package."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml16(para)
-msgid ""
-"You create at least one key pair for each project. You can use the key pair "
-"for multiple instances that belong to that project. If you generate a key "
-"pair with an external tool, you can import it into OpenStack."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml19(para)
-msgid ""
-"If an image uses a static root password or a static key setneither is "
-"recommendedyou must not provide a key pair when you launch the instance."
-msgstr "イメージが固定の root パスワードまたは固定のキーセットを使用する場合、どちらも推奨されませんが、インスタンスを起動するためにキーペアを提供する必要がありません。"
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml20(para)
-msgid ""
-"A <emphasis role=\"italic\">security group</emphasis> is a named collection "
-"of network access rules that you use to limit the types of traffic that have"
-" access to instances. When you launch an instance, you can assign one or "
-"more security groups to it. If you do not create security groups, new "
-"instances are automatically assigned to the default security group, unless "
-"you explicitly specify a different security group."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml27(para)
-msgid ""
-"The associated <emphasis role=\"italic\">rules</emphasis> in each security "
-"group control the traffic to instances in the group. Any incoming traffic "
-"that is not matched by a rule is denied access by default. You can add rules"
-" to or remove rules from a security group, and you can modify rules for the "
-"default and any other security group."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml33(para)
-msgid ""
-"You can modify the rules in a security group to allow access to instances "
-"through different ports and protocols. For example, you can modify rules to "
-"allow access to instances through SSH, to ping instances, or to allow UDP "
-"traffic; for example, for a DNS server running on an instance. You specify "
-"the following parameters for rules:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml41(para)
-msgid ""
-"<emphasis role=\"bold\">Source of traffic</emphasis>. Enable traffic to "
-"instances from either IP addresses inside the cloud from other group members"
-" or from all IP addresses."
-msgstr "<emphasis role=\"bold\">トラフィックソース</emphasis>。クラウドの IP アドレスから、他のグループメンバーから、あるいは全 IP アドレスからインスタンスへのトラフィックを可能にします。"
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml47(para)
-msgid ""
-"<emphasis role=\"bold\">Protocol</emphasis>. Choose TCP for SSH, ICMP for "
-"pings, or UDP."
-msgstr "<emphasis role=\"bold\">プロトコル</emphasis>。SSH には TCP、ping には ICMP、あるいは UDP を選択します。"
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml51(para)
-msgid ""
-"<emphasis role=\"bold\">Destination port on virtual machine</emphasis>. "
-"Define a port range. To open a single port only, enter the same value twice."
-" ICMP does not support ports; instead, you enter values to define the codes "
-"and types of ICMP traffic to be allowed."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml58(para)
-msgid "Rules are automatically enforced as soon as you create or modify them."
-msgstr "ルールは、作成または変更後すぐに自動的に有効になります。"
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml61(para)
-msgid ""
-"Instances that use the default security group cannot, by default, be "
-"accessed from any IP address outside of the cloud. If you want those IP "
-"addresses to access the instances, you must modify the rules for the default"
-" security group."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml65(para)
-msgid ""
-"You can also assign a floating IP address to a running instance to make it "
-"accessible from outside the cloud. See <xref "
-"linkend=\"manage_ip_addresses\"/>."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml72(para)
-msgid "You can generate a key pair or upload an existing public key."
-msgstr "キーペアの生成や既存の公開鍵のアップロードが可能です。"
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml75(para)
-msgid "To generate a key pair, run the following command:"
-msgstr "キーペアを生成するために、以下のコマンドを実行します。"
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml76(replaceable)
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml98(replaceable)
-msgid "KEY_NAME"
-msgstr "KEY_NAME"
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml76(replaceable)
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml87(replaceable)
-msgid "MY_KEY"
-msgstr "MY_KEY"
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml77(para)
-msgid ""
-"The command generates a key pair with the name that you specify fir "
-"<replaceable>KEY_NAME</replaceable>, writes the private key to the "
-"<filename>.pem</filename> file that you specify, and registers the public "
-"key at the Nova database."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml84(para)
-msgid ""
-"To set the permissions of the <filename>.pem</filename> file so that only "
-"you can read and write to it, run the following command:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml95(para)
-msgid ""
-"If you have already generated a key pair and the public key is located at "
-"<filename>~/.ssh/id_rsa.pub</filename>, run the following command to upload "
-"the public key:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml99(para)
-msgid ""
-"The command registers the public key at the Nova database and names the key "
-"pair the name that you specify for "
-"<literal><replaceable>KEY_NAME</replaceable></literal>."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml104(para)
-msgid ""
-"To ensure that the key pair has been successfully imported, list key pairs "
-"as follows:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml114(para)
-msgid ""
-"To list the security groups for the current project, including descriptions,"
-" enter the following command:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml119(para)
-msgid ""
-"To create a security group with a specified name and description, enter the "
-"following command:"
-msgstr "指定された名前と説明を持つセキュリティグループを作成するために、以下のコマンドを入力します。"
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml122(replaceable)
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml127(replaceable)
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml147(replaceable)
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml157(replaceable)
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml164(replaceable)
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml177(replaceable)
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml184(replaceable)
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml202(replaceable)
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml214(replaceable)
-msgid "SECURITY_GROUP_NAME"
-msgstr "SECURITY_GROUP_NAME"
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml122(replaceable)
-msgid "GROUP_DESCRIPTION"
-msgstr "GROUP_DESCRIPTION"
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml125(para)
-msgid "To delete a specified group, enter the following command:"
-msgstr "指定されたグループを削除するために、以下のコマンドを入力します。"
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml129(para)
-msgid ""
-"You cannot delete the default security group for a project. Also, you cannot"
-" delete a security group that is assigned to a running instance."
-msgstr "プロジェクトの Default のセキュリティグループは削除できません。また、実行中のインスタンスに割り当てられているセキュリティグループも削除できません。"
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml140(para)
-msgid ""
-"Modify security group rules with the <placeholder-1/> commands. Before you "
-"begin, source the OpenStack RC file. For details, see <xref "
-"linkend=\"cli_openrc\"/>."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml145(para)
-msgid "To list the rules for a security group, run the following command:"
-msgstr "セキュリティグループのルールを一覧表示するために、以下のコマンドを実行します。"
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml150(para)
-msgid ""
-"To allow SSH access to the instances, choose one of the following options:"
-msgstr "インスタンスへの SSH 接続を許可するために、以下のオプションのどれかを選択します。"
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml154(para)
-msgid ""
-"Allow access from all IP addresses, specified as IP subnet "
-"<filename>0.0.0.0/0</filename> in CIDR notation:"
-msgstr "CIDR 表記で IP サブネット <filename>0.0.0.0/0</filename> として指定して、すべての IP アドレスからのアクセスを許可します。"
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml160(para)
-msgid ""
-"Allow access only from IP addresses from other security groups (source "
-"groups) to access the specified port:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml164(replaceable)
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml184(replaceable)
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml202(replaceable)
-msgid "SOURCE_GROUP_NAME"
-msgstr "SOURCE_GROUP_NAME"
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml169(para)
-msgid ""
-"To allow pinging of the instances, choose one of the following options:"
-msgstr "インスタンスへの ping アクセスを許可するには、以下のオプションのどれかを選択します。"
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml173(para)
-msgid ""
-"Allow pinging from all IP addresses, specified as IP subnet "
-"<filename>0.0.0.0/0</filename> in CIDR notation:"
-msgstr "CIDR 表記で IP サブネット <filename>0.0.0.0/0</filename> として指定して、すべての IP アドレスからの ping を許可します。"
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml177(para)
-msgid "This allows access to all codes and all types of ICMP traffic."
-msgstr "これにより、すべてのコードとすべての種類の ICMP 通信が許可されます。"
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml181(para)
-msgid ""
-"Allow only members of other security groups (source groups) to ping "
-"instances:"
-msgstr "他のセキュリティグループ (ソースグループ) のメンバーのみがインスタンスに ping できるようにします。"
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml189(para)
-msgid ""
-"To allow access through a UDP port, such as allowing access to a DNS server "
-"that runs on a VM, choose one of the following options:"
-msgstr "仮想マシンで実行する DNS サーバーにアクセスするなど、UDP ポート経由でのアクセスを許可するには、以下のオプションの 1 つを選択します。"
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml194(para)
-msgid ""
-"Allow UDP access from IP addresses, specified as IP subnet "
-"<filename>0.0.0.0/0</filename> in CIDR notation:<placeholder-1/>"
-msgstr "CIDR 表記で IP サブネット <filename>0.0.0.0/0</filename> として指定して、すべての IP アドレスからの UDP アクセスを許可します。<placeholder-1/>"
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml199(para)
-msgid ""
-"Allow only IP addresses from other security groups (source groups) to access"
-" the specified port:"
-msgstr "他のセキュリティグループからの IP アドレス (ソースグループ) のみが指定したポートにアクセスできるようにします。"
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml208(title)
-msgid "Delete a security group"
-msgstr "セキュリティグループの削除"
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml209(para)
-msgid ""
-"To delete a security group rule, specify the same arguments that you used to"
-" create the rule."
-msgstr "セキュリティグループのルールを削除するには、ルール作成に使用したものと同じ引数を指定します。"
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml212(para)
-msgid ""
-"For example, to delete the security group rule that permits SSH access from "
-"all IP addresses, run the following command."
-msgstr "例えば、すべての IP アドレスからの SSH アクセスを許可するセキュリティグループルールを削除する場合、以下のコマンドを実行します。"
-
 #. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml0(None)
+#: ./doc/user-guide/section_sdk_configure_instances.xml0(None)
 msgid "translator-credits"
 msgstr "Tomoyuki KATO <tomo@dream.daynight.jp>, 2013-2014\nmyamamot <myamamot@redhat.com>, 2014\nykatabam <ykatabam@redhat.com>, 2014"
diff --git a/doc/user-guide/locale/user-guide.pot b/doc/user-guide/locale/user-guide.pot
index 061af85606..06532d226d 100644
--- a/doc/user-guide/locale/user-guide.pot
+++ b/doc/user-guide/locale/user-guide.pot
@@ -1,7 +1,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2014-05-30 06:09+0000\n"
+"POT-Creation-Date: 2014-06-03 06:11+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -9,6 +9,118 @@ msgstr ""
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
+#: ./doc/user-guide/section_cli_heat.xml:8(title)
+msgid "Create and manage stacks"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml:9(para)
+msgid "The Orchestration module enables you to orchestrate multiple composite cloud applications. This module supports use of both the Amazon Web Services (AWS) CloudFormation template format through both a Query API that is compatible with CloudFormation and the native OpenStack <glossterm>Heat Orchestration Template (HOT)</glossterm> format through a REST API."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml:14(para) ./doc/user-guide/section_dashboard_stacks.xml:16(para)
+msgid "These flexible template languages enable application developers to describe and automate the deployment of infrastructure, services, and applications. The templates enable creation of most OpenStack resource types, such as instances, floating IP addresses, volumes, security groups, and users. The resources, once created, are referred to as stacks."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml:19(para) ./doc/user-guide/section_dashboard_stacks.xml:23(para)
+msgid "The template languages are described in <link href=\"http://docs.openstack.org/developer/heat/template_guide/index.html\">the Template Guide</link> in the <link href=\"http://docs.openstack.org/developer/heat/\">Heat developer documentation</link>."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml:25(title)
+msgid "Create a stack from an example template file"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml:28(para)
+msgid "To create a stack, or template, from an <link href=\"https://github.com/openstack/heat-templates\">example template file</link>, run the following command:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml:32(replaceable) ./doc/user-guide/section_cli_heat.xml:59(replaceable)
+msgid "PATH_TO_HEAT_TEMPLATES"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml:33(replaceable)
+msgid "USERNAME"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml:33(replaceable) ./doc/user-guide/app_cheat_sheet.xml:47(replaceable)
+msgid "PASSWORD"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml:33(replaceable)
+msgid "HEAT_KEY"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml:34(para)
+msgid "The <literal>--parameters</literal> values that you specify depend on the parameters that are defined in the template. If a website hosts the template file, you can specify the URL with the <literal>--template-url</literal> parameter instead of the <literal>--template-file</literal> parameter."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml:40(para)
+msgid "The command returns the following output:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml:48(para)
+msgid "You can also use the <placeholder-1/> command to validate a template file without creating a stack from it."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml:52(para)
+msgid "Previous versions of the heat client used <placeholder-1/> instead of <placeholder-2/>, but it has been deprecated in favor of <placeholder-3/>."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml:58(para)
+msgid "To do so, run the following command:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml:60(para)
+msgid "If validation fails, the response returns an error message."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml:66(title)
+msgid "Get information about stacks"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml:67(para)
+msgid "To explore the state and history of a particular stack, you can run a number of commands."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml:71(para)
+msgid "To see which stacks are visible to the current user, run the following command:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml:82(para)
+msgid "To show the details of a stack, run the following command:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml:87(para)
+msgid "A stack consists of a collection of resources. To list the resources and their status, run the following command:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml:97(para)
+msgid "To show the details for a specific resource in a stack, run the following command:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml:100(para)
+msgid "Some resources have associated metadata which can change throughout the life cycle of a resource. Show the metadata by running the following command:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml:105(para)
+msgid "A series of events is generated during the life cycle of a stack. To display life cycle events, run the following command::"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml:116(para)
+msgid "To show the details for a particular event, run the following command:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml:123(title)
+msgid "Update a stack"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml:124(para)
+msgid "To update an existing stack from a modified template file, run a command like the following command:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_heat.xml:135(para)
+msgid "Some resources are updated in-place, while others are replaced with new resources."
+msgstr ""
+
 #: ./doc/user-guide/section_dashboard_create_networks.xml:6(title)
 msgid "Create and manage networks"
 msgstr ""
@@ -225,1054 +337,6 @@ msgstr ""
 msgid "You have successfully created the router. You can view the new topology from the <guilabel>Network Topology</guilabel> tab."
 msgstr ""
 
-#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:7(title)
-msgid "Use snapshots to migrate instances"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:8(para)
-msgid "To use snapshots to migrate instances from OpenStack projects to clouds, complete these steps."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:11(para)
-msgid "In the source project, perform the following steps:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:14(link)
-msgid "Create a snapshot of the instance."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:17(link)
-msgid "Download the snapshot as an image."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:21(para)
-msgid "In the destination project, perform the following steps:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:24(link)
-msgid "Import the snapshot to the new environment."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:27(link)
-msgid "Boot a new instance from the snapshot."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:32(para)
-msgid "Some cloud providers allow only administrators to perform this task."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:35(title)
-msgid "Create a snapshot of the instance"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:38(para)
-msgid "Shut down the source VM before you take the snapshot to ensure that all data is flushed to disk. If necessary, list the instances to view get the instance name."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:49(para)
-msgid "Use the <placeholder-1/> command to confirm that the instance shows a <literal>SHUTOFF</literal> status."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:59(para)
-msgid "Use the <placeholder-1/> command to take a snapshot. Use the <placeholder-2/> command to check the status until the status is <literal>ACTIVE</literal>:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:78(title)
-msgid "Download the snapshot as an image"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:81(para)
-msgid "Get the image ID:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:90(para)
-msgid "Download the snapshot by using the image ID that was returned in the previous step:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:94(para)
-msgid "The <placeholder-1/> command requires the image ID and cannot use the image name."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:97(para)
-msgid "Ensure there is sufficient space on the destination file system for the image file."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:103(para)
-msgid "Make the image available to the new environment, either through HTTP or with direct upload to a machine (<placeholder-1/>)."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:109(title)
-msgid "Import the snapshot to new environment"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:110(para)
-msgid "In the new project or cloud environment, import the snapshot:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:112(replaceable)
-msgid "IMAGE_URL"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:115(title)
-msgid "Boot a new instance from the snapshot"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:116(para)
-msgid "In the new project or cloud environment, use the snapshot to create the new instance:"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:6(title)
-msgid "Create and manage volumes"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:8(para)
-msgid "Volumes are block storage devices that you attach to instances to enable persistent storage. You can attach a volume to a running instance or detach a volume and attach it to another instance at any time. You can also create a snapshot from or delete a volume. Only administrative users can create volume types."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:15(title)
-msgid "Create a volume"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:18(para) ./doc/user-guide/section_dashboard_manage_volumes.xml:136(para) ./doc/user-guide/section_dashboard_manage_volumes.xml:170(para) ./doc/user-guide/section_dashboard_manage_volumes.xml:212(para) ./doc/user-guide/section_dashboard_manage_volumes.xml:251(para)
-msgid "Log in to the dashboard, choose a project, and click <guibutton>Volumes</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:22(para) ./doc/user-guide/section_dashboard_manage_volumes.xml:124(para)
-msgid "Click <guibutton>Create Volume</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:23(para)
-msgid "In the dialog box that opens, enter or select the following values."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:32(guilabel)
-msgid "Volume Name"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:36(para)
-msgid "Specify a name for the volume."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:43(guilabel) ./doc/user-guide/section_dashboard_manage_images.xml:64(guilabel) ./doc/user-guide/app_cheat_sheet.xml:20(th) ./doc/user-guide/app_cheat_sheet.xml:66(th) ./doc/user-guide/app_cheat_sheet.xml:140(th) ./doc/user-guide/app_cheat_sheet.xml:333(th) ./doc/user-guide/app_cheat_sheet.xml:374(th) ./doc/user-guide/app_cheat_sheet.xml:458(th)
-msgid "Description"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:47(para)
-msgid "Optionally, provide a brief description for the volume."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:54(guilabel)
-msgid "Type"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:58(para)
-msgid "Leave this field blank."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:64(guilabel)
-msgid "Size (GB)"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:68(para)
-msgid "The size of the volume in gigabytes."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:75(guilabel)
-msgid "Volume Source"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:79(para)
-msgid "Select one of the following options:"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:82(guilabel)
-msgid "No source, empty volume"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:83(para)
-msgid "Creates an empty volume."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:84(para)
-msgid "An empty volume does not contain a file system or a partition table."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:88(guilabel)
-msgid "Snapshot"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:89(para)
-msgid "If you choose this option, a new field for <guilabel>Use snapshot as a source</guilabel> displays. You can select the snapshot from the list."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:95(guilabel)
-msgid "Image"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:96(para)
-msgid "If you choose this option, a new field for <guilabel>Use image as a source</guilabel> displays. You can select the image from the list."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:99(para)
-msgid "Select the <guilabel>Availability Zone</guilabel> from the list. By default, this value is set to the availability zone given by the cloud provider (for example, <literal>us-west</literal> or <literal>apac-south</literal>). For some cases, it could be <literal>nova</literal>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:107(guilabel)
-msgid "Volume"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:108(para)
-msgid "If you choose this option, a new field for <guilabel>Use volume as a source</guilabel> displays. You can select the volume from the list."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:114(para)
-msgid "Options to use a snapshot or a volume as the source for a volume are displayed only if there are existing snapshots or volumes."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:127(para)
-msgid "The dashboard shows the volume on the <guilabel>Volumes</guilabel> tab."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:131(title)
-msgid "Attach a volume to an instance"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:132(para)
-msgid "After you create one or more volumes, you can attach them to instances. You can attach a volume to one instance at a time."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:140(para)
-msgid "Select the volume to add to an instance and click <guibutton>Edit Attachments</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:144(para)
-msgid "In the <guilabel>Manage Volume Attachments</guilabel> dialog box, select an instance."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:148(para)
-msgid "Enter the name of the device from which the volume is accessible by the instance."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:151(para)
-msgid "The actual device name might differ from the volume name because of hypervisor settings."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:156(para)
-msgid "Click <guibutton>Attach Volume</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:157(para)
-msgid "The dashboard shows the instance to which the volume is now attached and the device name."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:161(para)
-msgid "You can view the status of a volume in the <guilabel>Volumes</guilabel> tab of the dashboard. The volume is either Available or In-Use."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:163(para)
-msgid "Now you can log in to the instance and mount, format, and use the disk."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:167(title)
-msgid "Detach a volume from an instance"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:174(para)
-msgid "Select the volume and click <guibutton>Edit Attachments</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:177(para)
-msgid "Click <guibutton>Detach Volume</guibutton> and confirm your changes."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:181(para) ./doc/user-guide/section_dashboard_manage_volumes.xml:261(para)
-msgid "A message indicates whether the action was successful."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:184(title)
-msgid "Create a snapshot from a volume"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:187(para)
-msgid "Log in to the dashboard, choose a project, and click <guilabel>Volumes</guilabel>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:191(para)
-msgid "Select a volume from which to create a snapshot."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:194(para)
-msgid "From the <guilabel>More</guilabel> list, select <guilabel>Create Snapshot</guilabel>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:198(para)
-msgid "In the dialog box that opens, enter a snapshot name and a brief description."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:202(para)
-msgid "Confirm your changes."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:203(para)
-msgid "The dashboard shows the new volume snapshot in <guilabel>Volume Snapshots</guilabel> tab."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:209(title)
-msgid "Edit a volume"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:216(para) ./doc/user-guide/section_dashboard_manage_images.xml:36(para) ./doc/user-guide/section_dashboard_manage_images.xml:162(para) ./doc/user-guide/section_dashboard_manage_images.xml:209(para)
-msgid "From the <guilabel>CURRENT PROJECT</guilabel> on the <guilabel>Project</guilabel> tab, select the appropriate project."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:221(para)
-msgid "On the <guilabel>Project</guilabel> tab, click <guilabel>Volumes</guilabel>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:225(para) ./doc/user-guide/section_dashboard_manage_images.xml:171(para)
-msgid "Select the image that you want to edit."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:228(para)
-msgid "In the <guilabel>Actions</guilabel> column, click <guilabel>Edit Volume</guilabel>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:232(para)
-msgid "In the <guilabel>Edit Volume</guilabel> dialog box, update the name and description of the image."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:236(para)
-msgid "Click <guibutton>Edit Volume</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:240(para)
-msgid "You can extend a volume by using the <guilabel>Extend Volume</guilabel> option available in the <guibutton>More</guibutton> dropdown list and entering the new value for volume size."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:246(title)
-msgid "Delete a volume"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:247(para)
-msgid "When you delete an instance, the data in its attached volumes is not destroyed."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:255(para)
-msgid "Select the check boxes for the volumes that you want to delete."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_volumes.xml:259(para)
-msgid "Click <guibutton>Delete Volumes</guibutton> and confirm your choice."
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_manage_images.xml:7(title) ./doc/user-guide/app_cheat_sheet.xml:96(th)
-msgid "Manage images"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_manage_images.xml:8(para)
-msgid "When working with images in the SDK, you will call both <literal>glance</literal> and <literal>nova</literal> methods."
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_manage_images.xml:11(title) ./doc/user-guide/app_cheat_sheet.xml:152(td)
-msgid "List images"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_manage_images.xml:12(para)
-msgid "To list the available images, call the <methodname>glanceclient.v2.images.Controller.list</methodname> method:"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_manage_images.xml:18(para)
-msgid "The <methodname>images</methodname> method returns a Python generator, as shown in the following interaction with the Python interpreter:"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_manage_images.xml:77(title)
-msgid "Get image by ID"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_manage_images.xml:78(para)
-msgid "To retrieve an image object from its ID, call the <methodname> glanceclient.v2.images.Controller.get</methodname> method:"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_manage_images.xml:88(title)
-msgid "Get image by name"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_manage_images.xml:89(para)
-msgid "The Image Service Python bindings do not support the retrieval of an image object by name. However, the Compute Python bindings enable you to get an image object by name. To get an image object by name, call the <methodname> novaclient.v1_1.images.ImageManager.find</methodname> method:"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_manage_images.xml:101(title) ./doc/user-guide/section_dashboard_manage_images.xml:28(title)
-msgid "Upload an image"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_manage_images.xml:102(para)
-msgid "To upload an image, call the <methodname> glanceclient.v2.images.ImageManager.create</methodname> method:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml:8(title)
-msgid "Create and manage stacks"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml:9(para)
-msgid "The Orchestration module enables you to orchestrate multiple composite cloud applications. This module supports use of both the Amazon Web Services (AWS) CloudFormation template format through both a Query API that is compatible with CloudFormation and the native OpenStack <glossterm>Heat Orchestration Template (HOT)</glossterm> format through a REST API."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml:14(para) ./doc/user-guide/section_dashboard_stacks.xml:16(para)
-msgid "These flexible template languages enable application developers to describe and automate the deployment of infrastructure, services, and applications. The templates enable creation of most OpenStack resource types, such as instances, floating IP addresses, volumes, security groups, and users. The resources, once created, are referred to as stacks."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml:19(para) ./doc/user-guide/section_dashboard_stacks.xml:23(para)
-msgid "The template languages are described in <link href=\"http://docs.openstack.org/developer/heat/template_guide/index.html\">the Template Guide</link> in the <link href=\"http://docs.openstack.org/developer/heat/\">Heat developer documentation</link>."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml:25(title)
-msgid "Create a stack from an example template file"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml:28(para)
-msgid "To create a stack, or template, from an <link href=\"https://github.com/openstack/heat-templates\">example template file</link>, run the following command:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml:32(replaceable) ./doc/user-guide/section_cli_heat.xml:59(replaceable)
-msgid "PATH_TO_HEAT_TEMPLATES"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml:33(replaceable)
-msgid "USERNAME"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml:33(replaceable) ./doc/user-guide/app_cheat_sheet.xml:47(replaceable)
-msgid "PASSWORD"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml:33(replaceable)
-msgid "HEAT_KEY"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml:34(para)
-msgid "The <literal>--parameters</literal> values that you specify depend on the parameters that are defined in the template. If a website hosts the template file, you can specify the URL with the <literal>--template-url</literal> parameter instead of the <literal>--template-file</literal> parameter."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml:40(para)
-msgid "The command returns the following output:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml:48(para)
-msgid "You can also use the <placeholder-1/> command to validate a template file without creating a stack from it."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml:52(para)
-msgid "Previous versions of the heat client used <placeholder-1/> instead of <placeholder-2/>, but it has been deprecated in favor of <placeholder-3/>."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml:58(para)
-msgid "To do so, run the following command:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml:60(para)
-msgid "If validation fails, the response returns an error message."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml:66(title)
-msgid "Get information about stacks"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml:67(para)
-msgid "To explore the state and history of a particular stack, you can run a number of commands."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml:71(para)
-msgid "To see which stacks are visible to the current user, run the following command:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml:82(para)
-msgid "To show the details of a stack, run the following command:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml:87(para)
-msgid "A stack consists of a collection of resources. To list the resources and their status, run the following command:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml:97(para)
-msgid "To show the details for a specific resource in a stack, run the following command:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml:100(para)
-msgid "Some resources have associated metadata which can change throughout the life cycle of a resource. Show the metadata by running the following command:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml:105(para)
-msgid "A series of events is generated during the life cycle of a stack. To display life cycle events, run the following command::"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml:116(para)
-msgid "To show the details for a particular event, run the following command:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml:123(title)
-msgid "Update a stack"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml:124(para)
-msgid "To update an existing stack from a modified template file, run a command like the following command:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_heat.xml:135(para)
-msgid "Some resources are updated in-place, while others are replaced with new resources."
-msgstr ""
-
-#: ./doc/user-guide/ch_sdk.xml:6(title)
-msgid "OpenStack Python SDK"
-msgstr ""
-
-#: ./doc/user-guide/ch_sdk.xml:8(para)
-msgid "Use the OpenStack Python Software Development Kit (SDK) to write Python automation scripts that create and manage resources in your OpenStack cloud. The SDK implements Python bindings to the OpenStack API, which enables you to perform automation tasks in Python by making calls on Python objects rather than making REST calls directly. All OpenStack command-line tools are implemented using the Python SDK."
-msgstr ""
-
-#: ./doc/user-guide/ch_sdk.xml:15(para)
-msgid "You should also be familiar with:"
-msgstr ""
-
-#: ./doc/user-guide/ch_sdk.xml:18(para)
-msgid "RESTful web services"
-msgstr ""
-
-#: ./doc/user-guide/ch_sdk.xml:21(para)
-msgid "HTTP/1.1"
-msgstr ""
-
-#: ./doc/user-guide/ch_sdk.xml:24(para)
-msgid "JSON and XML data serialization formats"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:6(title) ./doc/user-guide/section_sdk_configure_instances.xml:6(title) ./doc/user-guide/section_cli_nova_configure_instances.xml:10(title)
-msgid "Configure access and security for instances"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:8(para)
-msgid "Before you launch an instance, you should add security group rules to enable users to ping and use SSH to connect to the instance. To do so, you either <link href=\"#security_groups_add_rule\">add rules to the default security group</link> or add a security group with rules."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:14(para)
-msgid "Key pairs are SSH credentials that are injected into an instance when it is launched. To use key pair injection, the image that the instance is based on must contain the <literal>cloud-init</literal> package. Each project should have at least one key pair. For more information, see <xref linkend=\"keypair_add\"/>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:20(para)
-msgid "If you have generated a key pair with an external tool, you can import it into OpenStack. The key pair can be used for multiple instances that belong to a project. For more information, see <xref linkend=\"dashboard_import_keypair\"/>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:25(para)
-msgid "When an instance is created in OpenStack, it is automatically assigned a fixed IP address in the network to which the instance is assigned. This IP address is permanently associated with the instance until the instance is terminated. However, in addition to the fixed IP address, a floating IP address can also be attached to an instance. Unlike fixed IP addresses, floating IP addresses are able to have their associations modified at any time, regardless of the state of the instances involved."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:35(title)
-msgid "Add a rule to the default security group"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:36(para)
-msgid "This procedure enables SSH and ICMP (ping) access to instances. The rules apply to all instances within a given project, and should be set for every project unless there is a reason to prohibit SSH or ICMP access to the instances."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:41(para)
-msgid "This procedure can be adjusted as necessary to add additional security group rules to a project, if your cloud requires them."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:46(para)
-msgid "Log in to the dashboard, choose a project, and click <guilabel>Access &amp; Security</guilabel>. The <guilabel>Security Groups</guilabel> tab shows the security groups that are available for this project."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:53(para)
-msgid "Select the <guilabel>default</guilabel> security group and click <guibutton>Edit Rules</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:58(para)
-msgid "To allow SSH access, click <guibutton>Add Rule</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:62(para) ./doc/user-guide/section_dashboard_access_and_security.xml:105(para)
-msgid "In the Add Rule dialog box, enter the following values:"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:69(guilabel) ./doc/user-guide/section_dashboard_access_and_security.xml:111(guilabel)
-msgid "Rule"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:71(literal)
-msgid "SSH"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:75(guilabel) ./doc/user-guide/section_dashboard_access_and_security.xml:119(guilabel)
-msgid "Remote"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:78(literal) ./doc/user-guide/section_dashboard_access_and_security.xml:82(guilabel) ./doc/user-guide/section_dashboard_access_and_security.xml:120(literal) ./doc/user-guide/section_dashboard_access_and_security.xml:123(guilabel) ./doc/user-guide/app_cheat_sheet.xml:347(replaceable)
-msgid "CIDR"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:84(literal) ./doc/user-guide/section_dashboard_access_and_security.xml:124(literal)
-msgid "0.0.0.0/0"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:90(para)
-msgid "To accept requests from a particular range of IP addresses, specify the IP address block in the <guilabel>CIDR</guilabel> box."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:96(para) ./doc/user-guide/section_dashboard_access_and_security.xml:129(para)
-msgid "Click <guibutton>Add</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:97(para)
-msgid "Instances will now have SSH port 22 open for requests from any IP address."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:101(para)
-msgid "To add an ICMP rule, click <guibutton>Add Rule</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:112(literal)
-msgid "All ICMP"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:115(guilabel)
-msgid "Direction"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:116(literal)
-msgid "Ingress"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:130(para)
-msgid "Instances will now accept all incoming ICMP packets."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:136(title) ./doc/user-guide/section_cli_nova_configure_instances.xml:70(title)
-msgid "Add a key pair"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:137(para)
-msgid "Create at least one key pair for each project."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:140(para) ./doc/user-guide/section_dashboard_access_and_security.xml:169(para) ./doc/user-guide/section_dashboard_access_and_security.xml:237(para)
-msgid "Log in to the dashboard, choose a project, and click <guilabel>Access &amp; Security</guilabel>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:145(para) ./doc/user-guide/section_dashboard_access_and_security.xml:174(para)
-msgid "Click the <guilabel>Keypairs</guilabel> tab, which shows the key pairs that are available for this project."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:150(para)
-msgid "Click <guibutton>Create Keypair</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:154(para)
-msgid "In the Create Keypair dialog box, enter a name for your key pair, and click <guibutton>Create Keypair</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:160(para)
-msgid "Respond to the prompt to download the key pair."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:166(title) ./doc/user-guide/section_cli_nova_configure_instances.xml:92(title)
-msgid "Import a key pair"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:179(para)
-msgid "Click <guibutton>Import Keypair</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:183(para)
-msgid "In the Import Keypair dialog box, enter the name of your key pair, copy the public key into the <guilabel>Public Key</guilabel> box, and then click <guibutton>Import Keypair</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:190(para)
-msgid "Save the <filename>*.pem</filename> file locally."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:192(para)
-msgid "To change its permissions so that only you can read and write to the file, run the following command:"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:195(replaceable) ./doc/user-guide/section_dashboard_access_and_security.xml:211(replaceable)
-msgid "yourPrivateKey"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:197(para)
-msgid "If you are using the dashboard from a Windows computer, use PuTTYgen to load the <filename>*.pem</filename> file and convert and save it as <filename>*.ppk</filename>. For more information see the <link href=\"http://winscp.net/eng/docs/ui_puttygen\">WinSCP web page for PuTTYgen</link>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:209(para)
-msgid "To make the key pair known to SSH, run the <placeholder-1/> command."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:214(para)
-msgid "The Compute database registers the public key of the key pair."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:216(para)
-msgid "The dashboard lists the key pair on the <guilabel>Access &amp; Security</guilabel> tab."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:220(title)
-msgid "Allocate a floating IP address to an instance"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:221(para)
-msgid "When an instance is created in OpenStack, it is automatically assigned a fixed IP address in the network to which the instance is assigned. This IP address is permanently associated with the instance until the instance is terminated."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:227(para)
-msgid "However, in addition to the fixed IP address, a floating IP address can also be attached to an instance. Unlike fixed IP addresses, floating IP addresses can have their associations modified at any time, regardless of the state of the instances involved. This procedure details the reservation of a floating IP address from an existing pool of addresses and the association of that address with a specific instance."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:241(para)
-msgid "Click the <guilabel>Floating IPs</guilabel> tab, which shows the floating IP addresses allocated to instances."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:246(para)
-msgid "Click <guibutton>Allocate IP to Project</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:249(para)
-msgid "Choose the pool from which to pick the IP address."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:253(para)
-msgid "Click <guibutton>Allocate IP</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:256(para)
-msgid "In the <guilabel>Floating IPs</guilabel> list, click <guibutton> Associate</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:264(para)
-msgid "The <guilabel>IP Address</guilabel> field is filled automatically, but you can add a new IP address by clicking the <guibutton>+</guibutton> button."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:271(para)
-msgid "In the <guilabel>Ports to be associated</guilabel> field, select a port from the list."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:274(para)
-msgid "The list shows all the instances with their fixed IP addresses."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:260(para)
-msgid "In the Manage Floating IP Associations dialog box, choose the following options: <placeholder-1/>"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:281(para)
-msgid "Click <guibutton>Associate</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:285(para)
-msgid "To disassociate an IP address from an instance, click the <guibutton>Disassociate</guibutton> button."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_access_and_security.xml:287(para)
-msgid "To release the floating IP address back into the pool of addresses, click the <guibutton>More</guibutton> button and select the <guilabel>Release Floating IP</guilabel> option."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_swift_howto.xml:6(title)
-msgid "Manage objects and containers"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_swift_howto.xml:8(para)
-msgid "The OpenStack Object Storage service provides the <placeholder-1/> client, which is a command-line interface (CLI). Use this client to list objects and containers, upload objects to containers, and download or delete objects from containers. You can also gather statistics and update metadata for accounts, containers, and objects."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_swift_howto.xml:14(para)
-msgid "This client is based on the native swift client library, <literal>client.py</literal>, which seamlessly re-authenticates if the current token expires during processing, retries operations multiple times, and provides a processing concurrency of 10."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_swift_howto.xml:20(title)
-msgid "Create and manage containers"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_swift_howto.xml:23(para)
-msgid "To create a container, run the following command and replace <replaceable>CONTAINER</replaceable> with the name of your container."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_swift_howto.xml:26(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:45(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:94(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:96(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:101(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:115(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:120(replaceable) ./doc/user-guide/app_cheat_sheet.xml:468(replaceable)
-msgid "CONTAINER"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_swift_howto.xml:28(para)
-msgid "To list all containers: run the following command:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_swift_howto.xml:32(para)
-msgid "To check the status of containers, run the following command:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_swift_howto.xml:42(para)
-msgid "You can also use the <placeholder-1/> command with the <replaceable>ACCOUNT</replaceable> or <replaceable>CONTAINER</replaceable> names as parameters."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_swift_howto.xml:61(title)
-msgid "Manage access"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_swift_howto.xml:64(para)
-msgid "Users have roles on accounts. For example, a user with the admin role has full access to all containers and objects in an account. You can set access control lists (ACLs) at the container level and support lists for read and write access, which you set with the <literal>X-Container-Read</literal> and <literal>X-Container-Write</literal> headers."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_swift_howto.xml:70(para)
-msgid "To give a user read access, use the <placeholder-1/> command with the <parameter>-r</parameter> parameter. To give a user write access, use the <parameter>-w</parameter> parameter."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_swift_howto.xml:73(para)
-msgid "The following example enables the <literal>testuser</literal> user to read objects in the container:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_swift_howto.xml:76(para)
-msgid "You can also use this command with a list of users."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_swift_howto.xml:79(para)
-msgid "If you use StaticWeb middleware to enable Object Storage to serve public web content, use <literal>.r:</literal>, followed by a list of allowed referrers."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_swift_howto.xml:82(para)
-msgid "The following command gives object access to all referring domains:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_swift_howto.xml:89(title)
-msgid "Manage objects"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_swift_howto.xml:92(para)
-msgid "To upload an object to a container, run the following command:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_swift_howto.xml:94(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:96(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:101(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:115(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:120(replaceable)
-msgid "OBJECT_FILENAME"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_swift_howto.xml:95(para)
-msgid "To upload in chunks, for large files, run the following command:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_swift_howto.xml:96(replaceable)
-msgid "CHUNK_SIZE"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_swift_howto.xml:99(para)
-msgid "To check the status of the object, run the following command:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_swift_howto.xml:114(para)
-msgid "To list the objects in a container, run the following command:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_swift_howto.xml:118(para)
-msgid "To download an object from a container:, run the following command:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:10(title)
-msgid "Store metadata on a configuration drive"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:11(para)
-msgid "You can configure OpenStack to write metadata to a special configuration drive that attaches to the instance when it boots. The instance can mount this drive and read files from it to get information that is normally available through the <link href=\"http://docs.openstack.org/admin-guide-cloud/content/section_metadata-service.html\">metadata service</link>. This metadata is different from the user data."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:18(para)
-msgid "One use case for using the configuration drive is to pass a networking configuration when you do not use DHCP to assign IP addresses to instances. For example, you might pass the IP address configuration for the instance through the configuration drive, which the instance can mount and access before you configure the network settings for the instance."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:24(para)
-msgid "Any modern guest operating system that is capable of mounting an ISO 9660 or VFAT file system can use the configuration drive."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:27(title)
-msgid "Requirements and guidelines"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:28(para)
-msgid "To use the configuration drive, you must follow the following requirements for the compute host and image."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:31(title)
-msgid "Compute host requirements"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:33(para)
-msgid "The following hypervisors support the configuration drive: libvirt, XenServer, Hyper-V, and VMWare."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:37(para)
-msgid "To use configuration drive with libvirt, XenServer, or VMWare, you must first install the <package>genisoimage</package> package on each compute host. Otherwise, instances do not boot properly."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:42(para)
-msgid "Use the <literal>mkisofs_cmd</literal> flag to set the path where you install the <package>genisoimage</package> program. If <package>genisoimage</package> is in same path as the <systemitem class=\"service\">nova-compute</systemitem> service, you do not need to set this flag."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:51(para)
-msgid "To use configuration drive with Hyper-V, you must set the <literal>mkisofs_cmd</literal> value to the full path to an <literal>mkisofs.exe</literal> installation. Additionally, you must set the <literal>qemu_img_cmd</literal> value in the <literal>hyperv</literal> configuration section to the full path to an <literal>qemu-img</literal> command installation."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:62(title)
-msgid "Image requirements"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:64(para)
-msgid "An image built with a recent version of the <package>cloud-init</package> package can automatically access metadata passed through the configuration drive. The <package>cloud-init</package> package version 0.7.1 works with Ubuntu and Fedora based images, such as Red Hat Enterprise Linux."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:72(para)
-msgid "If an image does not have the <package>cloud-init</package> package installed, you must customize the image to run a script that mounts the configuration drive on boot, reads the data from the drive, and takes appropriate action such as adding the public key to an account. See <xref linkend=\"config_drive_contents\"/> for details about how data is organized on the configuration drive."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:82(para)
-msgid "If you use Xen with a configuration drive, use the <literal>xenapi_disable_agent</literal> configuration parameter to disable the agent."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:89(title)
-msgid "Guidelines"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:91(para)
-msgid "Do not rely on the presence of the EC2 metadata in the configuration drive, because this content might be removed in a future release. For example, do not rely on files in the <filename>ec2</filename> directory."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:97(para)
-msgid "When you create images that access configuration drive data and multiple directories are under the <filename>openstack</filename> directory, always select the highest API version by date that your consumer supports. For example, if your guest image supports the 2012-03-05, 2012-08-05, and 2013-04-13 versions, try 2013-04-13 first and fall back to a previous version if 2013-04-13 is not present."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:109(title)
-msgid "Enable and access the configuration drive"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:112(para)
-msgid "To enable the configuration drive, pass the <literal>--config-drive=true</literal> parameter to the <placeholder-1/> command."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:116(para)
-msgid "The following example enables the configuration drive and passes user data, two files, and two key/value metadata pairs, all of which are accessible from the configuration drive:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:121(para)
-msgid "You can also configure the Compute service to always create a configuration drive by setting the following option in the <filename>/etc/nova/nova.conf</filename> file:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:126(para)
-msgid "If a user passes the <literal>--config-drive=true</literal> flag to the <placeholder-1/> command, an administrator cannot disable the configuration drive."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:134(para)
-msgid "If your guest operating system supports accessing disk by label, you can mount the configuration drive as the <filename>/dev/disk/by-label/<replaceable>configurationDriveVolumeLabel</replaceable></filename> device. In the following example, the configuration drive has the <filename>config-2</filename> volume label."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:142(para)
-msgid "Ensure that you use at least version 0.3.1 of CirrOS for configuration drive support."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:145(para)
-msgid "If your guest operating system does not use <literal>udev</literal>, the <filename>/dev/disk/by-label</filename> directory is not present."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:149(para)
-msgid "You can use the <placeholder-1/> command to identify the block device that corresponds to the configuration drive. For example, when you boot the CirrOS image with the <literal>m1.tiny</literal> flavor, the device is <filename>/dev/vdb</filename>:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:157(para)
-msgid "Once identified, you can mount the device:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:164(title)
-msgid "Configuration drive contents"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:165(para)
-msgid "In this example, the contents of the configuration drive are as follows:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:178(para)
-msgid "The files that appear on the configuration drive depend on the arguments that you pass to the <placeholder-1/> command."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:183(title)
-msgid "OpenStack metadata format"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:184(para)
-msgid "The following example shows the contents of the <filename>openstack/2012-08-10/meta_data.json</filename> and <filename>openstack/latest/meta_data.json</filename> files. These files are identical. The file contents are formatted for readability."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:190(para)
-msgid "Note the effect of the <literal>--file /etc/network/interfaces=/home/myuser/instance-interfaces</literal> argument that was passed to the <placeholder-1/> command. The contents of this file are contained in the <filename>openstack/content/0000</filename> file on the configuration drive, and the path is specified as <filename>/etc/network/interfaces</filename> in the <filename>meta_data.json</filename> file."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:201(title)
-msgid "EC2 metadata format"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:202(para)
-msgid "The following example shows the contents of the <filename>ec2/2009-04-04/meta-data.json</filename> and the <filename>ec2/latest/meta-data.json</filename> files. These files are identical. The file contents are formatted to improve readability."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:210(title)
-msgid "User data"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:211(para)
-msgid "The <filename>openstack/2012-08-10/user_data</filename>, <filename>openstack/latest/user_data</filename>, <filename>ec2/2009-04-04/user-data</filename>, and <filename>ec2/latest/user-data</filename> file are present only if the <literal>--user-data</literal> flag and the contents of the user data file are passed to the <placeholder-1/> command."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:221(title)
-msgid "Configuration drive format"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:222(para)
-msgid "The default format of the configuration drive as an ISO 9660 file system. To explicitly specify the ISO 9660 format, add the following line to the <filename>/etc/nova/nova.conf</filename> file:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:228(para)
-msgid "By default, you cannot attach the configuration drive image as a CD drive instead of as a disk drive. To attach a CD drive, add the following line to the <filename>/etc/nova/nova.conf</filename> file:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:233(para)
-msgid "For legacy reasons, you can configure the configuration drive to use VFAT format instead of ISO 9660. It is unlikely that you would require VFAT format because ISO 9660 is widely supported across operating systems. However, to use the VFAT format, add the following line to the <filename>/etc/nova/nova.conf</filename> file:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:242(para)
-msgid "If you choose VFAT, the configuration drive is 64MB."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:247(title)
-msgid "Configuration drive reference"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_config-drive.xml:248(para)
-msgid "The following table shows the configuration options for the configuration drive."
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_install.xml:6(title)
-msgid "Install the OpenStack SDK"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_install.xml:7(para)
-msgid "Each OpenStack project has its own Python library. These libraries are bundled with the command-line clients. For example, the Python bindings for the Compute API are bundled with the <package>python-novaclient</package> package."
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_install.xml:11(para)
-msgid "For details about how to install the clients, see <link linkend=\"install_clients\">install the OpenStack command-line clients</link>."
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_auth_neutron.xml:6(title)
-msgid "Authenticate against a Networking endpoint"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_auth_neutron.xml:7(para)
-msgid "To authenticate against a Networking endpoint, instantiate a <classname>neutronclient.v_2_0.client.Client</classname> object:"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_auth_neutron.xml:18(para)
-msgid "You can also authenticate by explicitly specifying the endpoint and token:"
-msgstr ""
-
 #: ./doc/user-guide/section_sdk_nova.xml:6(title)
 msgid "Compute"
 msgstr ""
@@ -1533,6 +597,438 @@ msgstr ""
 msgid "List hosts code listing"
 msgstr ""
 
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:10(title)
+msgid "Launch an instance"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:12(para)
+msgid "When you launch an instance from an image, OpenStack creates a local copy of the image on the compute node where the instance starts."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:14(para)
+msgid "When you launch an instance from a volume, note the following steps:"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:18(para)
+msgid "To select the volume to from which to launch, launch an instance from an arbitrary image on the volume. The image that you select does not boot. Instead, it is replaced by the image on the volume that you choose in the next steps."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:22(para)
+msgid "To boot a Xen image from a volume, the image you launch in must be the same type, fully virtualized or paravirtualized, as the one on the volume."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:27(para)
+msgid "Select the volume or volume snapshot from which to boot. Enter a device name. Enter <literal>vda</literal> for KVM images or <literal>xvda</literal> for Xen images."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:34(para)
+msgid "Log in to the dashboard, choose a project, and click <guilabel>Images</guilabel>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:36(para)
+msgid "The dashboard shows the images that have been uploaded to OpenStack Image Service and are available for this project."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:39(para)
+msgid "For details on creating images, see <link href=\"http://docs.openstack.org/image-guide/content/ch_creating_images_manually.html\">Creating images manually</link> in the <citetitle>OpenStack Virtual Machine Image Guide</citetitle>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:45(para)
+msgid "Select an image and click <guibutton>Launch</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:48(para)
+msgid "In the Launch Instance dialog box, specify the following values:"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:55(guilabel)
+msgid "Details"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:60(guilabel)
+msgid "Availability Zone"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:62(para)
+msgid "By default, this value is set to the availability zone given by the cloud provider (for example, <literal>us-west</literal> or <literal>apac-south</literal>). For some cases, it could be <literal>nova</literal>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:69(guilabel)
+msgid "Instance Name"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:70(para)
+msgid "Assign a name to the virtual machine."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:71(para)
+msgid "The name you assign here becomes the initial host name of the server. After the server is built, if you change the server name in the API or change the host name directly, the names are not updated in the dashboard."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:75(para)
+msgid "Server names are not guaranteed to be unique when created so you could have two instances with the same host name."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:82(guilabel)
+msgid "Flavor"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:83(para)
+msgid "Specify the size of the instance to launch."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:84(para)
+msgid "The flavor is selected based on the size of the image selected for launching an instance. For example, while creating an image, if you have entered the value in the <guilabel>Minimum RAM (MB)</guilabel> field as 2048, then on selecting the image, the default flavor is <guilabel>m1.small</guilabel>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:94(guilabel)
+msgid "Instance Count"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:95(para)
+msgid "To launch multiple instances, enter a value greater than 1. The default is 1."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:99(guilabel)
+msgid "Instance Boot Source"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:100(para)
+msgid "Your options are:"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:103(guilabel)
+msgid "Boot from image"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:104(para)
+msgid "If you choose this option, a new field for <guilabel>Image Name</guilabel> displays. You can select the image from the list."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:109(guilabel)
+msgid "Boot from snapshot"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:110(para)
+msgid "If you choose this option, a new field for <guilabel>Instance Snapshot</guilabel> displays. You can select the snapshot from the list."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:115(guilabel)
+msgid "Boot from volume"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:116(para)
+msgid "If you choose this option, a new field for <guilabel>Volume</guilabel> displays. You can select the volume from the list."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:121(guilabel)
+msgid "Boot from image (creates a new volume)"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:122(para)
+msgid "With this option, you can boot from an image and create a volume by entering the <guilabel>Device Size</guilabel> and <guilabel>Device Name</guilabel> for your volume. Click the <guilabel>Delete on Terminate</guilabel> option to delete the volume on terminating the instance."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:130(guilabel)
+msgid "Boot from volume snapshot (creates a new volume)"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:132(para)
+msgid "Using this option, you can boot from a volume snapshot and create a new volume by choosing <guilabel>Volume Snapshot</guilabel> from a list and adding a <guilabel>Device Name</guilabel> for your volume. Click the <guilabel>Delete on Terminate</guilabel> option to delete the volume on terminating the instance."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:141(para)
+msgid "Since you are launching an instance from an image, <guilabel>Boot from image</guilabel> is chosen by default."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:147(guilabel)
+msgid "Image Name"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:148(para)
+msgid "This field changes based on your previous selection. Since you have chosen to launch an instance using an image, the <guilabel>Image Name</guilabel> field displays. Select the image name from the dropdown list."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:155(guilabel)
+msgid "Access &amp; Security"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:159(guilabel)
+msgid "Keypair"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:160(para)
+msgid "Specify a key pair."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:161(para)
+msgid "If the image uses a static root password or a static key set (neither is recommended), you do not need to provide a key pair to launch the instance."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:166(guilabel)
+msgid "Security Groups"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:167(para)
+msgid "Activate the security groups that you want to assign to the instance."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:169(para)
+msgid "Security groups are a kind of cloud firewall that define which incoming network traffic is forwarded to instances. For details, see <xref linkend=\"security_groups_add_rule\"/>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:173(para)
+msgid "If you have not created any security groups, you can assign only the default security group to the instance."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:178(guilabel) ./doc/user-guide/section_sdk_neutron.xml:6(title)
+msgid "Networking"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:181(guilabel)
+msgid "Selected Networks"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:182(para)
+msgid "To add a network to the instance, click the <guibutton>+</guibutton> in the <guilabel>Available Networks</guilabel> field."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:188(guilabel)
+msgid "Post-Creation"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:191(guilabel)
+msgid "Customization Script"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:192(para)
+msgid "Specify a customization script that runs after your instance launches."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:196(guilabel)
+msgid "Advanced Options"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:199(guilabel)
+msgid "Disk Partition"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:200(para)
+msgid "Select the type of disk partition from the dropdown list."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:204(guilabel)
+msgid "Automatic"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:206(para)
+msgid "Entire disk is single partition and automatically resizes."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:210(guilabel)
+msgid "Manual"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:212(para)
+msgid "Faster build times but requires manual partitioning."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:231(para)
+msgid "Click <guibutton>Launch</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:232(para)
+msgid "The instance starts on a compute node in the cloud."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:235(para)
+msgid "The <guilabel>Instances</guilabel> tab shows the instance's name, its private and public IP addresses, size, status, task, and power state."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:238(para)
+msgid "If you did not provide a key pair, security groups, or rules, users can access the instance only from inside the cloud through VNC. Even pinging the instance is not possible without an ICMP rule configured. To access the instance through a VNC console, see <xref linkend=\"instance_console\"/>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:6(title)
+msgid "Upload and manage images"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:7(para)
+msgid "A virtual machine image, referred to in this document simply as an image, is a single file that contains a virtual disk that has a bootable operating system installed on it. Images are used to create virtual machine instances within the cloud. For information about creating image files, see the <link href=\"http://docs.openstack.org/image-guide/content/\"><citetitle>OpenStack Virtual Machine Image Guide</citetitle></link>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:15(para)
+msgid "Depending on your role, you may have permission to upload and manage virtual machine images. Operators might restrict the upload and management of images to cloud administrators or operators only. If you have the appropriate privileges, you can use the dashboard to upload and manage images in the <guilabel>admin</guilabel> project."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:22(para)
+msgid "You can also use the <placeholder-1/> and <placeholder-2/> command-line clients or the Image Service and Compute APIs to manage images. See <xref linkend=\"cli_manage_images\"/>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:28(title) ./doc/user-guide/section_sdk_manage_images.xml:101(title)
+msgid "Upload an image"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:29(para)
+msgid "Follow this procedure to upload an image to a project."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:33(para) ./doc/user-guide/section_dashboard_manage_images.xml:159(para) ./doc/user-guide/section_dashboard_manage_images.xml:206(para)
+msgid "Log in to the dashboard."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:36(para) ./doc/user-guide/section_dashboard_manage_images.xml:162(para) ./doc/user-guide/section_dashboard_manage_images.xml:209(para) ./doc/user-guide/section_dashboard_manage_volumes.xml:216(para)
+msgid "From the <guilabel>CURRENT PROJECT</guilabel> on the <guilabel>Project</guilabel> tab, select the appropriate project."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:41(para) ./doc/user-guide/section_dashboard_manage_images.xml:167(para) ./doc/user-guide/section_dashboard_manage_images.xml:213(para)
+msgid "On the <guilabel>Project</guilabel> tab, click <guilabel>Images</guilabel>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:45(para) ./doc/user-guide/section_dashboard_manage_images.xml:148(para)
+msgid "Click <guibutton>Create Image</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:46(para)
+msgid "The Create An Image dialog box appears."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:49(para)
+msgid "Enter the following values:"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:56(guilabel)
+msgid "Name"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:59(para)
+msgid "Enter a name for the image."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:64(guilabel) ./doc/user-guide/app_cheat_sheet.xml:20(th) ./doc/user-guide/app_cheat_sheet.xml:66(th) ./doc/user-guide/app_cheat_sheet.xml:140(th) ./doc/user-guide/app_cheat_sheet.xml:333(th) ./doc/user-guide/app_cheat_sheet.xml:374(th) ./doc/user-guide/app_cheat_sheet.xml:458(th) ./doc/user-guide/section_dashboard_manage_volumes.xml:43(guilabel)
+msgid "Description"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:67(para)
+msgid "Optionally, enter a brief description of the image."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:73(guilabel)
+msgid "Image Source"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:76(para)
+msgid "Choose the image source from the list. Your choices are <guilabel>Image Location</guilabel> and <guilabel>Image File</guilabel>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:83(para)
+msgid "<guilabel>Image File</guilabel> or <guilabel>Image Location</guilabel>"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:88(para)
+msgid "Based on your selection for <guilabel>Image Source</guilabel>, you either enter the location URL of the image in the <guilabel>Image Location</guilabel> field. or browse to the image file on your system and add it."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:97(guilabel)
+msgid "Format"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:100(para)
+msgid "Select the correct format (for example, QCOW2) for the image."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:107(guilabel)
+msgid "Architecture"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:111(para)
+msgid "Specify the architecture. For example, <literal>i386</literal> for a 32-bit architecture or <literal>x86-64</literal> for a 64-bit architecture."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:118(para)
+msgid "<guilabel>Minimum Disk (GB)</guilabel> and <guilabel>Minimum RAM (MB)</guilabel>"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:122(para)
+msgid "Leave these optional fields empty."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:127(guilabel)
+msgid "Public"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:130(para)
+msgid "Select this check box to make the image public to all users with access to the current project."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:137(guilabel)
+msgid "Protected"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:140(para)
+msgid "Select this check box to ensure that only users with permissions can delete the image."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:149(para)
+msgid "The image is queued to be uploaded. It might take some time before the status changes from Queued to Active."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:155(title)
+msgid "Update an image"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:156(para)
+msgid "Follow this procedure to update an existing image."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:171(para) ./doc/user-guide/section_dashboard_manage_volumes.xml:225(para)
+msgid "Select the image that you want to edit."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:174(para)
+msgid "In the <guilabel>Actions</guilabel> column, click <guilabel>More</guilabel> and then select <guilabel>Edit</guilabel> from the list."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:182(para)
+msgid "Change the name of the image."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:185(para)
+msgid "Select the <guilabel>Public</guilabel> check box to make the image public."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:189(para)
+msgid "Clear the <guilabel>Public</guilabel> check box to make the image private."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:179(para)
+msgid "In the Update Image dialog box, you can perform the following actions: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:195(para)
+msgid "Click <guibutton>Update Image</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:200(title)
+msgid "Delete an image"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:201(para)
+msgid "Deletion of images is permanent and <emphasis role=\"bold\">cannot</emphasis> be reversed. Only users with the appropriate permissions can delete images."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:217(para)
+msgid "Select the images that you want to delete."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:220(para)
+msgid "Click <guibutton>Delete Images</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_images.xml:223(para)
+msgid "In the <guilabel>Confirm Delete Image</guilabel> dialog box, click <guibutton>Delete Images</guibutton> to confirm the deletion."
+msgstr ""
+
 #: ./doc/user-guide/section_cli_ceilometer.xml:7(title)
 msgid "Measure cloud resources"
 msgstr ""
@@ -1641,6 +1137,794 @@ msgstr ""
 msgid "View statistics:"
 msgstr ""
 
+#: ./doc/user-guide/app_cheat_sheet.xml:7(title)
+msgid "OpenStack command-line interface cheat sheet"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:9(para)
+msgid "The following tables give a quick reference of the most used command-line commands."
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:15(caption)
+msgid "Identity (keystone)"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:21(th) ./doc/user-guide/app_cheat_sheet.xml:67(th) ./doc/user-guide/app_cheat_sheet.xml:141(th) ./doc/user-guide/app_cheat_sheet.xml:334(th) ./doc/user-guide/app_cheat_sheet.xml:375(th) ./doc/user-guide/app_cheat_sheet.xml:459(th)
+msgid "Command"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:26(td)
+msgid "List all users"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:32(td)
+msgid "List Identity service catalog"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:38(td)
+msgid "List all services in service catalog"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:44(td)
+msgid "Create new user"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:46(replaceable) ./doc/user-guide/app_cheat_sheet.xml:53(replaceable) ./doc/user-guide/app_cheat_sheet.xml:186(replaceable) ./doc/user-guide/app_cheat_sheet.xml:215(replaceable) ./doc/user-guide/app_cheat_sheet.xml:222(replaceable) ./doc/user-guide/app_cheat_sheet.xml:228(replaceable) ./doc/user-guide/app_cheat_sheet.xml:234(replaceable) ./doc/user-guide/app_cheat_sheet.xml:240(replaceable) ./doc/user-guide/app_cheat_sheet.xml:246(replaceable) ./doc/user-guide/app_cheat_sheet.xml:252(replaceable) ./doc/user-guide/app_cheat_sheet.xml:258(replaceable) ./doc/user-guide/app_cheat_sheet.xml:266(replaceable) ./doc/user-guide/app_cheat_sheet.xml:273(replaceable) ./doc/user-guide/app_cheat_sheet.xml:341(replaceable) ./doc/user-guide/app_cheat_sheet.xml:385(replaceable)
+msgid "NAME"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:46(replaceable)
+msgid "TENANT"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:47(replaceable)
+msgid "EMAIL"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:47(replaceable)
+msgid "BOOL"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:51(td)
+msgid "Create new tenant"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:53(replaceable)
+msgid "DESCRIPTION"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:61(caption)
+msgid "Image Service (glance)"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:72(td)
+msgid "List images you can access"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:78(td)
+msgid "Delete specified image"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:80(replaceable) ./doc/user-guide/app_cheat_sheet.xml:86(replaceable) ./doc/user-guide/app_cheat_sheet.xml:92(replaceable) ./doc/user-guide/app_cheat_sheet.xml:166(replaceable) ./doc/user-guide/app_cheat_sheet.xml:266(replaceable)
+msgid "IMAGE"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:84(td)
+msgid "Describe a specific image"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:90(td)
+msgid "Update image"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:96(th) ./doc/user-guide/section_sdk_manage_images.xml:7(title)
+msgid "Manage images"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:99(td)
+msgid "Kernel image"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:107(td)
+msgid "RAM image"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:115(td)
+msgid "Three-part image"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:124(td)
+msgid "Register raw image"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:135(caption)
+msgid "Compute (nova)"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:146(td)
+msgid "List instances, notice status of instance"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:152(td) ./doc/user-guide/section_sdk_manage_images.xml:11(title)
+msgid "List images"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:158(td)
+msgid "List flavors"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:164(td)
+msgid "Boot an instance using flavor and image names (if names are unique)"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:166(replaceable) ./doc/user-guide/app_cheat_sheet.xml:258(replaceable)
+msgid "FLAVOR"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:166(replaceable)
+msgid "INSTANCE_NAME"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:172(td)
+msgid "Login to instance"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:175(replaceable)
+msgid "NETNS_NAME"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:175(replaceable)
+msgid "USER"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:175(replaceable)
+msgid "SERVER"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:178(para)
+msgid "Note, in CirrOS the password for user <literal>cirros</literal> is \"cubswin:)\" without the quotes."
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:184(td)
+msgid "Show details of instance"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:191(td)
+msgid "View console log of instance"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:197(td)
+msgid "Set metadata on an instance"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:203(td) ./doc/user-guide/section_dashboard_launch_instances.xml:69(title)
+msgid "Create an instance snapshot"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:210(th)
+msgid "Pause, suspend, stop, rescue, resize, rebuild, reboot an instance"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:213(td)
+msgid "Pause"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:220(td)
+msgid "Unpause"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:226(td)
+msgid "Suspend"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:232(td)
+msgid "Unsuspend"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:238(td)
+msgid "Stop"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:244(td)
+msgid "Start"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:250(td)
+msgid "Rescue"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:256(td)
+msgid "Resize"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:264(td)
+msgid "Rebuild"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:271(td)
+msgid "Reboot"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:278(td)
+msgid "Inject user data and files into an instance"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:280(replaceable)
+msgid "FILE"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:280(replaceable)
+msgid "INSTANCE"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:284(para)
+msgid "To validate that the file is there, ssh into the instance, and look in <filename>/var/lib/cloud</filename> for the file."
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:290(th)
+msgid "Inject a keypair into an instance and access the instance with that keypair"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:294(td)
+msgid "Create keypair"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:301(td)
+msgid "Boot"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:308(td)
+msgid "Use ssh to connect to the instance"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:315(th)
+msgid "Manage security groups"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:318(td)
+msgid "Add rules to default security group allowing ping and SSH between instances in the default security group"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:328(caption)
+msgid "Networking (neutron)"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:339(td) ./doc/user-guide/section_sdk_neutron.xml:98(title)
+msgid "Create network"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:345(td)
+msgid "Create a subnet"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:347(replaceable)
+msgid "NETWORK_NAME"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:347(replaceable) ./doc/user-guide/section_dashboard_access_and_security.xml:78(literal) ./doc/user-guide/section_dashboard_access_and_security.xml:82(guilabel) ./doc/user-guide/section_dashboard_access_and_security.xml:120(literal) ./doc/user-guide/section_dashboard_access_and_security.xml:123(guilabel)
+msgid "CIDR"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:352(td)
+msgid "List network and subnet"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:359(td)
+msgid "Examine details of network and subnet"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:361(replaceable) ./doc/user-guide/app_cheat_sheet.xml:362(replaceable)
+msgid "ID_OR_NAME_OF_NETWORK"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:369(caption)
+msgid "Block Storage (cinder)"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:380(th)
+msgid "Manage volumes and volume snapshots"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:383(td)
+msgid "Create a new volume"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:385(replaceable)
+msgid "SIZE_IN_GB"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:390(td)
+msgid "Boot an instance and attach to volume"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:396(td)
+msgid "List volumes, notice status of volume"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:402(td)
+msgid "Attach volume to instance after instance is active, and volume is available"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:405(replaceable)
+msgid "INSTANCE_ID"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:405(replaceable)
+msgid "VOLUME_ID"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:410(th)
+msgid "Manage volumes after login into the instance"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:413(td)
+msgid "List storage devices"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:419(td)
+msgid "Make filesystem on volume"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:425(td)
+msgid "Create a mountpoint"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:431(td)
+msgid "Mount the volume at the mountpoint"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:437(td)
+msgid "Create a file on the volume"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:444(td)
+msgid "Unmount the volume"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:453(caption)
+msgid "Object Storage (swift)"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:464(td)
+msgid "Display information for the account, container, or object"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:467(replaceable)
+msgid "ACCOUNT"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:468(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:26(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:45(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:94(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:96(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:101(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:115(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:120(replaceable)
+msgid "CONTAINER"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:469(replaceable)
+msgid "OBJECT"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:473(td)
+msgid "List containers"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:479(td) ./doc/user-guide/section_dashboard_manage_containers.xml:19(title)
+msgid "Create a container"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:481(replaceable) ./doc/user-guide/app_cheat_sheet.xml:487(replaceable) ./doc/user-guide/app_cheat_sheet.xml:500(replaceable) ./doc/user-guide/app_cheat_sheet.xml:506(replaceable)
+msgid "CONTAINER_NAME"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:485(td)
+msgid "Upload file to a container"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:487(replaceable) ./doc/user-guide/app_cheat_sheet.xml:500(replaceable) ./doc/user-guide/app_cheat_sheet.xml:506(replaceable)
+msgid "FILE_NAME"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:492(td)
+msgid "List objects in container"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:498(td)
+msgid "Download object from container"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:504(td)
+msgid "Upload with chunks, for large file"
+msgstr ""
+
+#: ./doc/user-guide/app_cheat_sheet.xml:506(replaceable)
+msgid "SIZE"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:6(title)
+msgid "Create and manage object containers"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:8(para)
+msgid "OpenStack Object Storage provides a distributed, API-accessible storage platform that can be integrated directly into an application or used to store any type of file, including VM images, backups, archives, or media files. In the OpenStack Dashboard, you can only manage containers and objects."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:13(para)
+msgid "In OpenStack Object Storage, containers provide storage for objects in a manner similar to a Windows folder or Linux file directory, though they cannot be nested. An object in OpenStack consists of the file to be stored in the container and any accompanying metadata."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:22(para) ./doc/user-guide/section_dashboard_manage_containers.xml:44(para) ./doc/user-guide/section_dashboard_manage_containers.xml:79(para) ./doc/user-guide/section_dashboard_manage_containers.xml:103(para) ./doc/user-guide/section_dashboard_manage_containers.xml:144(para) ./doc/user-guide/section_dashboard_manage_containers.xml:171(para)
+msgid "Log in to the dashboard, choose a project, and click <guilabel>Containers</guilabel>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:26(para)
+msgid "Click <guibutton>Create Container</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:29(para)
+msgid "In the Create Container dialog box, enter a name for the container, and then click<guibutton>Create Container</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:34(para)
+msgid "You have successfully created a container."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:35(para)
+msgid "To delete a container, click the <guibutton>More</guibutton> button and select <guilabel>Delete Container</guilabel>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:41(title)
+msgid "Upload an object"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:48(para) ./doc/user-guide/section_dashboard_manage_containers.xml:83(para) ./doc/user-guide/section_dashboard_manage_containers.xml:107(para) ./doc/user-guide/section_dashboard_manage_containers.xml:148(para) ./doc/user-guide/section_dashboard_manage_containers.xml:175(para)
+msgid "Select the container in which you want to store your object."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:51(para) ./doc/user-guide/section_dashboard_manage_containers.xml:66(para) ./doc/user-guide/section_dashboard_manage_containers.xml:151(para)
+msgid "Click <guibutton>Upload Object</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:52(para) ./doc/user-guide/section_dashboard_manage_containers.xml:152(para)
+msgid "The Upload Object To Container: <replaceable>&lt;name&gt;</replaceable> dialog box is displayed. <replaceable>&lt;name&gt;</replaceable> is the name of the container to which you are uploading the object."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:59(para) ./doc/user-guide/section_dashboard_manage_containers.xml:159(para)
+msgid "Enter a name for the object."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:62(para) ./doc/user-guide/section_dashboard_manage_containers.xml:90(para)
+msgid "Browse to and select the file that you want to upload."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:69(para)
+msgid "You have successfully uploaded an object to the container."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:70(para) ./doc/user-guide/section_dashboard_manage_containers.xml:97(para)
+msgid "To delete an object, click the <guibutton>More</guibutton> button and select <guilabel>Delete Object</guilabel>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:75(title)
+msgid "Manage an object"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:77(title)
+msgid "To edit an object"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:86(para)
+msgid "Click <guibutton>More</guibutton> and choose <guilabel>Edit</guilabel> from the dropdown list."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:87(para)
+msgid "The Edit Object dialog box is displayed."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:93(para) ./doc/user-guide/section_dashboard_manage_containers.xml:162(para)
+msgid "Click <guibutton>Update Object</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:101(title)
+msgid "To copy an object from one container to another"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:110(para)
+msgid "Click <guibutton>More</guibutton> and choose <guilabel>Copy</guilabel> from the dropdown list."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:114(para)
+msgid "In the Copy Object: launch dialog box, enter the following values:"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:119(para)
+msgid "<guilabel>Destination Container</guilabel>: Choose the destination container from the list."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:123(para)
+msgid "<guilabel>Path</guilabel>: Specify a path in which the new copy should be stored inside of the selected container."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:128(para)
+msgid "<guilabel>Destination object name</guilabel>: Enter a name for the object in the new container."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:136(para)
+msgid "Click <guibutton>Copy Object</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:140(title)
+msgid "To create a metadata-only object without a file"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:141(para)
+msgid "You can create a new object in container without a file available and can upload the file later when it is ready. This temporary object acts a place-holder for a new object, and enables the user to share object metadata and URL info in advance."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:166(title)
+msgid "To create a pseudo-folder"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:167(para)
+msgid "Pseudo-folders are similar to folders in your desktop operating system. They are virtual collections defined by a common prefix on the object's name."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:178(para)
+msgid "Click <guibutton>Create Pseudo-folder</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:180(para)
+msgid "The Create Pseudo-Folder in Container <replaceable>&lt;name&gt; </replaceable> dialog box is displayed. <replaceable>&lt;name&gt; </replaceable> is the name of the container to which you are uploading the object."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:187(para)
+msgid "Enter a name for the pseudo-folder."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:189(para)
+msgid "A slash (/) character is used as the delimiter for pseudo-folders in the Object Store."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_containers.xml:193(para)
+msgid "Click <guibutton>Create</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_auth_glance.xml:6(title)
+msgid "Authenticate against an Image Service endpoint"
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_auth_glance.xml:7(para)
+msgid "To authenticate against an Image Service endpoint, instantiate a <link href=\"http://docs.openstack.org/developer/python-glanceclient/api/glanceclient.v2.client.html#glanceclient.v2.client.Client\"> glanceclient.v2.client.Client</link> object:"
+msgstr ""
+
+#: ./doc/user-guide/ch_dashboard.xml:10(title)
+msgid "OpenStack dashboard"
+msgstr ""
+
+#: ./doc/user-guide/ch_dashboard.xml:12(para)
+msgid "As a cloud end user, you can use the OpenStack dashboard to provision your own resources within the limits set by administrators. You can modify the examples provided in this section to create other types and sizes of server instances."
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_auth_keystone.xml:6(title)
+msgid "Authenticate against an Identity endpoint"
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_auth_keystone.xml:7(para)
+msgid "To authenticate against the Identity v2.0 endpoint, instantiate a <link href=\"http://docs.openstack.org/developer/python-keystoneclient/api/keystoneclient.v2_0.client.html#keystoneclient.v2_0.client.Client\"> keystoneclient.v_20.client.Client</link> object:"
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_auth_keystone.xml:18(para)
+msgid "After you instantiate a <classname>Client</classname> object, you can retrieve the token by accessing its <literal>auth_token</literal> attribute object:"
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_auth_keystone.xml:24(para)
+msgid "If the OpenStack cloud is configured to use public-key infrastructure (PKI) tokens, the Python script output looks something like this:"
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_auth_keystone.xml:35(para)
+msgid "This example shows a subset of a PKI token. A complete token is over 5000 characters long."
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_auth_neutron.xml:6(title)
+msgid "Authenticate against a Networking endpoint"
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_auth_neutron.xml:7(para)
+msgid "To authenticate against a Networking endpoint, instantiate a <classname>neutronclient.v_2_0.client.Client</classname> object:"
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_auth_neutron.xml:18(para)
+msgid "You can also authenticate by explicitly specifying the endpoint and token:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:10(title) ./doc/user-guide/section_dashboard_access_and_security.xml:6(title) ./doc/user-guide/section_sdk_configure_instances.xml:6(title)
+msgid "Configure access and security for instances"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:12(para)
+msgid "When you launch a virtual machine, you can inject a <emphasis role=\"italic\">key pair</emphasis>, which provides SSH access to your instance. For this to work, the image must contain the <literal>cloud-init</literal> package."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:16(para)
+msgid "You create at least one key pair for each project. You can use the key pair for multiple instances that belong to that project. If you generate a key pair with an external tool, you can import it into OpenStack."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:19(para)
+msgid "If an image uses a static root password or a static key setneither is recommendedyou must not provide a key pair when you launch the instance."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:20(para)
+msgid "A <emphasis role=\"italic\">security group</emphasis> is a named collection of network access rules that you use to limit the types of traffic that have access to instances. When you launch an instance, you can assign one or more security groups to it. If you do not create security groups, new instances are automatically assigned to the default security group, unless you explicitly specify a different security group."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:27(para)
+msgid "The associated <emphasis role=\"italic\">rules</emphasis> in each security group control the traffic to instances in the group. Any incoming traffic that is not matched by a rule is denied access by default. You can add rules to or remove rules from a security group, and you can modify rules for the default and any other security group."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:33(para)
+msgid "You can modify the rules in a security group to allow access to instances through different ports and protocols. For example, you can modify rules to allow access to instances through SSH, to ping instances, or to allow UDP traffic; for example, for a DNS server running on an instance. You specify the following parameters for rules:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:41(para)
+msgid "<emphasis role=\"bold\">Source of traffic</emphasis>. Enable traffic to instances from either IP addresses inside the cloud from other group members or from all IP addresses."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:47(para)
+msgid "<emphasis role=\"bold\">Protocol</emphasis>. Choose TCP for SSH, ICMP for pings, or UDP."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:51(para)
+msgid "<emphasis role=\"bold\">Destination port on virtual machine</emphasis>. Define a port range. To open a single port only, enter the same value twice. ICMP does not support ports; instead, you enter values to define the codes and types of ICMP traffic to be allowed."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:58(para)
+msgid "Rules are automatically enforced as soon as you create or modify them."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:61(para)
+msgid "Instances that use the default security group cannot, by default, be accessed from any IP address outside of the cloud. If you want those IP addresses to access the instances, you must modify the rules for the default security group."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:65(para)
+msgid "You can also assign a floating IP address to a running instance to make it accessible from outside the cloud. See <xref linkend=\"manage_ip_addresses\"/>."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:70(title) ./doc/user-guide/section_dashboard_access_and_security.xml:136(title)
+msgid "Add a key pair"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:72(para)
+msgid "You can generate a key pair or upload an existing public key."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:75(para)
+msgid "To generate a key pair, run the following command:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:76(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:98(replaceable)
+msgid "KEY_NAME"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:76(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:87(replaceable)
+msgid "MY_KEY"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:77(para)
+msgid "The command generates a key pair with the name that you specify fir <replaceable>KEY_NAME</replaceable>, writes the private key to the <filename>.pem</filename> file that you specify, and registers the public key at the Nova database."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:84(para)
+msgid "To set the permissions of the <filename>.pem</filename> file so that only you can read and write to it, run the following command:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:92(title) ./doc/user-guide/section_dashboard_access_and_security.xml:166(title)
+msgid "Import a key pair"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:95(para)
+msgid "If you have already generated a key pair and the public key is located at <filename>~/.ssh/id_rsa.pub</filename>, run the following command to upload the public key:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:99(para)
+msgid "The command registers the public key at the Nova database and names the key pair the name that you specify for <literal><replaceable>KEY_NAME</replaceable></literal>."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:104(para)
+msgid "To ensure that the key pair has been successfully imported, list key pairs as follows:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:111(title) ./doc/user-guide/section_sdk_configure_instances.xml:72(title)
+msgid "Create and manage security groups"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:114(para)
+msgid "To list the security groups for the current project, including descriptions, enter the following command:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:119(para)
+msgid "To create a security group with a specified name and description, enter the following command:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:122(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:127(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:147(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:157(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:164(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:177(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:184(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:202(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:214(replaceable)
+msgid "SECURITY_GROUP_NAME"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:122(replaceable)
+msgid "GROUP_DESCRIPTION"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:125(para)
+msgid "To delete a specified group, enter the following command:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:129(para)
+msgid "You cannot delete the default security group for a project. Also, you cannot delete a security group that is assigned to a running instance."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:138(title) ./doc/user-guide/section_sdk_configure_instances.xml:97(title)
+msgid "Create and manage security group rules"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:140(para)
+msgid "Modify security group rules with the <placeholder-1/> commands. Before you begin, source the OpenStack RC file. For details, see <xref linkend=\"cli_openrc\"/>."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:145(para)
+msgid "To list the rules for a security group, run the following command:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:150(para)
+msgid "To allow SSH access to the instances, choose one of the following options:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:154(para)
+msgid "Allow access from all IP addresses, specified as IP subnet <filename>0.0.0.0/0</filename> in CIDR notation:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:160(para)
+msgid "Allow access only from IP addresses from other security groups (source groups) to access the specified port:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:164(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:184(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:202(replaceable)
+msgid "SOURCE_GROUP_NAME"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:169(para)
+msgid "To allow pinging of the instances, choose one of the following options:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:173(para)
+msgid "Allow pinging from all IP addresses, specified as IP subnet <filename>0.0.0.0/0</filename> in CIDR notation:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:177(para)
+msgid "This allows access to all codes and all types of ICMP traffic."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:181(para)
+msgid "Allow only members of other security groups (source groups) to ping instances:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:189(para)
+msgid "To allow access through a UDP port, such as allowing access to a DNS server that runs on a VM, choose one of the following options:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:194(para)
+msgid "Allow UDP access from IP addresses, specified as IP subnet <filename>0.0.0.0/0</filename> in CIDR notation:<placeholder-1/>"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:199(para)
+msgid "Allow only IP addresses from other security groups (source groups) to access the specified port:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:208(title)
+msgid "Delete a security group"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:209(para)
+msgid "To delete a security group rule, specify the same arguments that you used to create the rule."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_configure_instances.xml:212(para)
+msgid "For example, to delete the security group rule that permits SSH access from all IP addresses, run the following command."
+msgstr ""
+
 #: ./doc/user-guide/section_cli_nova_floating_ips.xml:6(title)
 msgid "Manage IP addresses"
 msgstr ""
@@ -1761,16 +2045,488 @@ msgstr ""
 msgid "The IP address is returned to the pool of IP addresses that is available for all projects. If the IP address is still associated with a running instance, it is automatically disassociated from that instance."
 msgstr ""
 
-#: ./doc/user-guide/section_sdk_auth_glance.xml:6(title)
-msgid "Authenticate against an Image Service endpoint"
+#: ./doc/user-guide/section_cli_nova_manage_instances.xml:6(title)
+msgid "Manage instances and hosts"
 msgstr ""
 
-#: ./doc/user-guide/section_sdk_auth_glance.xml:7(para)
-msgid "To authenticate against an Image Service endpoint, instantiate a <link href=\"http://docs.openstack.org/developer/python-glanceclient/api/glanceclient.v2.client.html#glanceclient.v2.client.Client\"> glanceclient.v2.client.Client</link> object:"
+#: ./doc/user-guide/section_cli_nova_manage_instances.xml:7(para)
+msgid "Instances are virtual machines that run inside the cloud on physical compute nodes. The Compute service manages instances. A host is the node on which a group of instances resides."
 msgstr ""
 
-#: ./doc/user-guide/section_sdk_neutron.xml:6(title) ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:178(guilabel)
-msgid "Networking"
+#: ./doc/user-guide/section_cli_nova_manage_instances.xml:11(para)
+msgid "This section describes how to perform the different tasks involved in instance management, such as adding floating IP addresses, stopping and starting instances, and terminating instances. This section also discusses node management tasks."
+msgstr ""
+
+#: ./doc/user-guide/bk-user-guide.xml:8(title)
+msgid "OpenStack End User Guide"
+msgstr ""
+
+#: ./doc/user-guide/bk-user-guide.xml:9(titleabbrev)
+msgid "End User Guide"
+msgstr ""
+
+#: ./doc/user-guide/bk-user-guide.xml:17(orgname) ./doc/user-guide/bk-user-guide.xml:22(holder)
+msgid "OpenStack Foundation"
+msgstr ""
+
+#: ./doc/user-guide/bk-user-guide.xml:21(year)
+msgid "2014"
+msgstr ""
+
+#: ./doc/user-guide/bk-user-guide.xml:24(releaseinfo)
+msgid "current"
+msgstr ""
+
+#: ./doc/user-guide/bk-user-guide.xml:25(productname)
+msgid "OpenStack"
+msgstr ""
+
+#: ./doc/user-guide/bk-user-guide.xml:29(remark)
+msgid "Copyright details are filled in by the template."
+msgstr ""
+
+#: ./doc/user-guide/bk-user-guide.xml:34(para)
+msgid "OpenStack is an open-source cloud computing platform for public and private clouds. A series of interrelated projects deliver a cloud infrastructure solution. This guide shows OpenStack end users how to create and manage resources in an OpenStack cloud with the OpenStack dashboard and OpenStack client commands."
+msgstr ""
+
+#: ./doc/user-guide/bk-user-guide.xml:44(date)
+msgid "2014-05-09"
+msgstr ""
+
+#: ./doc/user-guide/bk-user-guide.xml:48(para)
+msgid "Add a command line cheat sheet."
+msgstr ""
+
+#: ./doc/user-guide/bk-user-guide.xml:55(date)
+msgid "2014-04-17"
+msgstr ""
+
+#: ./doc/user-guide/bk-user-guide.xml:59(para)
+msgid "For the Icehouse release, this guide has been updated with changes to the dashboard plus the moving of the command reference appendix as indicated below."
+msgstr ""
+
+#: ./doc/user-guide/bk-user-guide.xml:69(date)
+msgid "2014-01-31"
+msgstr ""
+
+#: ./doc/user-guide/bk-user-guide.xml:73(para)
+msgid "Removed the command reference appendix. This information is now in the <link href=\"http://docs.openstack.org/cli-reference/content/\"><citetitle>OpenStack Command-Line Interface Reference</citetitle></link>."
+msgstr ""
+
+#: ./doc/user-guide/bk-user-guide.xml:83(date)
+msgid "2013-12-30"
+msgstr ""
+
+#: ./doc/user-guide/bk-user-guide.xml:87(para)
+msgid "Added the OpenStack Python SDK chapter."
+msgstr ""
+
+#: ./doc/user-guide/bk-user-guide.xml:94(date)
+msgid "2013-10-17"
+msgstr ""
+
+#: ./doc/user-guide/bk-user-guide.xml:98(para)
+msgid "Havana release."
+msgstr ""
+
+#: ./doc/user-guide/bk-user-guide.xml:104(date)
+msgid "2013-08-19"
+msgstr ""
+
+#: ./doc/user-guide/bk-user-guide.xml:108(para)
+msgid "Editorial changes."
+msgstr ""
+
+#: ./doc/user-guide/bk-user-guide.xml:114(date)
+msgid "2013-07-29"
+msgstr ""
+
+#: ./doc/user-guide/bk-user-guide.xml:118(para)
+msgid "First edition of this document."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:7(title)
+msgid "Use snapshots to migrate instances"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:8(para)
+msgid "To use snapshots to migrate instances from OpenStack projects to clouds, complete these steps."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:11(para)
+msgid "In the source project, perform the following steps:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:14(link)
+msgid "Create a snapshot of the instance."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:17(link)
+msgid "Download the snapshot as an image."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:21(para)
+msgid "In the destination project, perform the following steps:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:24(link)
+msgid "Import the snapshot to the new environment."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:27(link)
+msgid "Boot a new instance from the snapshot."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:32(para)
+msgid "Some cloud providers allow only administrators to perform this task."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:35(title)
+msgid "Create a snapshot of the instance"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:38(para)
+msgid "Shut down the source VM before you take the snapshot to ensure that all data is flushed to disk. If necessary, list the instances to view get the instance name."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:49(para)
+msgid "Use the <placeholder-1/> command to confirm that the instance shows a <literal>SHUTOFF</literal> status."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:59(para)
+msgid "Use the <placeholder-1/> command to take a snapshot. Use the <placeholder-2/> command to check the status until the status is <literal>ACTIVE</literal>:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:78(title)
+msgid "Download the snapshot as an image"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:81(para)
+msgid "Get the image ID:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:90(para)
+msgid "Download the snapshot by using the image ID that was returned in the previous step:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:94(para)
+msgid "The <placeholder-1/> command requires the image ID and cannot use the image name."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:97(para)
+msgid "Ensure there is sufficient space on the destination file system for the image file."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:103(para)
+msgid "Make the image available to the new environment, either through HTTP or with direct upload to a machine (<placeholder-1/>)."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:109(title)
+msgid "Import the snapshot to new environment"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:110(para)
+msgid "In the new project or cloud environment, import the snapshot:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:112(replaceable)
+msgid "IMAGE_URL"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:115(title)
+msgid "Boot a new instance from the snapshot"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_migrate_instances.xml:116(para)
+msgid "In the new project or cloud environment, use the snapshot to create the new instance:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:10(title)
+msgid "Store metadata on a configuration drive"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:11(para)
+msgid "You can configure OpenStack to write metadata to a special configuration drive that attaches to the instance when it boots. The instance can mount this drive and read files from it to get information that is normally available through the <link href=\"http://docs.openstack.org/admin-guide-cloud/content/section_metadata-service.html\">metadata service</link>. This metadata is different from the user data."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:18(para)
+msgid "One use case for using the configuration drive is to pass a networking configuration when you do not use DHCP to assign IP addresses to instances. For example, you might pass the IP address configuration for the instance through the configuration drive, which the instance can mount and access before you configure the network settings for the instance."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:24(para)
+msgid "Any modern guest operating system that is capable of mounting an ISO 9660 or VFAT file system can use the configuration drive."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:27(title)
+msgid "Requirements and guidelines"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:28(para)
+msgid "To use the configuration drive, you must follow the following requirements for the compute host and image."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:31(title)
+msgid "Compute host requirements"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:33(para)
+msgid "The following hypervisors support the configuration drive: libvirt, XenServer, Hyper-V, and VMWare."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:37(para)
+msgid "To use configuration drive with libvirt, XenServer, or VMWare, you must first install the <package>genisoimage</package> package on each compute host. Otherwise, instances do not boot properly."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:42(para)
+msgid "Use the <literal>mkisofs_cmd</literal> flag to set the path where you install the <package>genisoimage</package> program. If <package>genisoimage</package> is in same path as the <systemitem class=\"service\">nova-compute</systemitem> service, you do not need to set this flag."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:51(para)
+msgid "To use configuration drive with Hyper-V, you must set the <literal>mkisofs_cmd</literal> value to the full path to an <literal>mkisofs.exe</literal> installation. Additionally, you must set the <literal>qemu_img_cmd</literal> value in the <literal>hyperv</literal> configuration section to the full path to an <literal>qemu-img</literal> command installation."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:62(title)
+msgid "Image requirements"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:64(para)
+msgid "An image built with a recent version of the <package>cloud-init</package> package can automatically access metadata passed through the configuration drive. The <package>cloud-init</package> package version 0.7.1 works with Ubuntu and Fedora based images, such as Red Hat Enterprise Linux."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:72(para)
+msgid "If an image does not have the <package>cloud-init</package> package installed, you must customize the image to run a script that mounts the configuration drive on boot, reads the data from the drive, and takes appropriate action such as adding the public key to an account. See <xref linkend=\"config_drive_contents\"/> for details about how data is organized on the configuration drive."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:82(para)
+msgid "If you use Xen with a configuration drive, use the <literal>xenapi_disable_agent</literal> configuration parameter to disable the agent."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:89(title)
+msgid "Guidelines"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:91(para)
+msgid "Do not rely on the presence of the EC2 metadata in the configuration drive, because this content might be removed in a future release. For example, do not rely on files in the <filename>ec2</filename> directory."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:97(para)
+msgid "When you create images that access configuration drive data and multiple directories are under the <filename>openstack</filename> directory, always select the highest API version by date that your consumer supports. For example, if your guest image supports the 2012-03-05, 2012-08-05, and 2013-04-13 versions, try 2013-04-13 first and fall back to a previous version if 2013-04-13 is not present."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:109(title)
+msgid "Enable and access the configuration drive"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:112(para)
+msgid "To enable the configuration drive, pass the <literal>--config-drive=true</literal> parameter to the <placeholder-1/> command."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:116(para)
+msgid "The following example enables the configuration drive and passes user data, two files, and two key/value metadata pairs, all of which are accessible from the configuration drive:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:121(para)
+msgid "You can also configure the Compute service to always create a configuration drive by setting the following option in the <filename>/etc/nova/nova.conf</filename> file:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:126(para)
+msgid "If a user passes the <literal>--config-drive=true</literal> flag to the <placeholder-1/> command, an administrator cannot disable the configuration drive."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:134(para)
+msgid "If your guest operating system supports accessing disk by label, you can mount the configuration drive as the <filename>/dev/disk/by-label/<replaceable>configurationDriveVolumeLabel</replaceable></filename> device. In the following example, the configuration drive has the <filename>config-2</filename> volume label."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:142(para)
+msgid "Ensure that you use at least version 0.3.1 of CirrOS for configuration drive support."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:145(para)
+msgid "If your guest operating system does not use <literal>udev</literal>, the <filename>/dev/disk/by-label</filename> directory is not present."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:149(para)
+msgid "You can use the <placeholder-1/> command to identify the block device that corresponds to the configuration drive. For example, when you boot the CirrOS image with the <literal>m1.tiny</literal> flavor, the device is <filename>/dev/vdb</filename>:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:157(para)
+msgid "Once identified, you can mount the device:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:164(title)
+msgid "Configuration drive contents"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:165(para)
+msgid "In this example, the contents of the configuration drive are as follows:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:178(para)
+msgid "The files that appear on the configuration drive depend on the arguments that you pass to the <placeholder-1/> command."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:183(title)
+msgid "OpenStack metadata format"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:184(para)
+msgid "The following example shows the contents of the <filename>openstack/2012-08-10/meta_data.json</filename> and <filename>openstack/latest/meta_data.json</filename> files. These files are identical. The file contents are formatted for readability."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:190(para)
+msgid "Note the effect of the <literal>--file /etc/network/interfaces=/home/myuser/instance-interfaces</literal> argument that was passed to the <placeholder-1/> command. The contents of this file are contained in the <filename>openstack/content/0000</filename> file on the configuration drive, and the path is specified as <filename>/etc/network/interfaces</filename> in the <filename>meta_data.json</filename> file."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:201(title)
+msgid "EC2 metadata format"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:202(para)
+msgid "The following example shows the contents of the <filename>ec2/2009-04-04/meta-data.json</filename> and the <filename>ec2/latest/meta-data.json</filename> files. These files are identical. The file contents are formatted to improve readability."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:210(title)
+msgid "User data"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:211(para)
+msgid "The <filename>openstack/2012-08-10/user_data</filename>, <filename>openstack/latest/user_data</filename>, <filename>ec2/2009-04-04/user-data</filename>, and <filename>ec2/latest/user-data</filename> file are present only if the <literal>--user-data</literal> flag and the contents of the user data file are passed to the <placeholder-1/> command."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:221(title)
+msgid "Configuration drive format"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:222(para)
+msgid "The default format of the configuration drive as an ISO 9660 file system. To explicitly specify the ISO 9660 format, add the following line to the <filename>/etc/nova/nova.conf</filename> file:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:228(para)
+msgid "By default, you cannot attach the configuration drive image as a CD drive instead of as a disk drive. To attach a CD drive, add the following line to the <filename>/etc/nova/nova.conf</filename> file:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:233(para)
+msgid "For legacy reasons, you can configure the configuration drive to use VFAT format instead of ISO 9660. It is unlikely that you would require VFAT format because ISO 9660 is widely supported across operating systems. However, to use the VFAT format, add the following line to the <filename>/etc/nova/nova.conf</filename> file:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:242(para)
+msgid "If you choose VFAT, the configuration drive is 64MB."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:247(title)
+msgid "Configuration drive reference"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_nova_config-drive.xml:248(para)
+msgid "The following table shows the configuration options for the configuration drive."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml:6(title)
+msgid "Launch and manage instances"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml:7(para)
+msgid "Instances are virtual machines that run inside the cloud."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml:9(para)
+msgid "You can <link linkend=\"dashboard_launch_instances_from_image\">launch an instance</link> from the following sources:"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml:12(para)
+msgid "Images uploaded to the OpenStack Image Service, as described in <xref linkend=\"dashboard_manage_images\"/>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml:14(para)
+msgid "Image that you have copied to a persistent volume. The instance launches from the volume, which is provided by the <systemitem class=\"service\">cinder-volume</systemitem> API through iSCSI."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml:23(title)
+msgid "Connect to your instance by using SSH"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml:24(para)
+msgid "To use SSH to connect to your instance, you use the downloaded keypair file."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml:27(para)
+msgid "The user name is <literal>ubuntu</literal> for the Ubuntu cloud images on TryStack."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml:32(para)
+msgid "Copy the IP address for your instance."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml:35(para)
+msgid "Use the <placeholder-1/> command to make a secure connection to the instance. For example:"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml:41(para)
+msgid "At the prompt, type <literal>yes</literal>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml:47(title)
+msgid "Track usage for instances"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml:48(para)
+msgid "You can track usage for instances for each project. You can track costs per month by showing metrics like number of vCPUs, disks, RAM, and uptime for all your instances."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml:54(para)
+msgid "Log in to the dashboard, choose a project, and click <guilabel>Overview</guilabel>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml:58(para)
+msgid "To query the instance usage for a month, select a month and click <guibutton>Submit</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml:63(para)
+msgid "To download a summary, click <guibutton>Download CSV Summary</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml:72(para) ./doc/user-guide/section_dashboard_launch_instances.xml:98(para)
+msgid "Log in to the dashboard, choose a project, and click <guilabel>Instances</guilabel>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml:76(para)
+msgid "Select the instance from which to create a snapshot."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml:79(para)
+msgid "In the <guilabel>Actions</guilabel> column, click <guilabel>Create Snapshot</guilabel>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml:83(para)
+msgid "In the Create Snapshot dialog box, enter a name for the snapshot, and click <guibutton>Create Snapshot</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml:85(para)
+msgid "The <guilabel>Images</guilabel> category shows the instance snapshot."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml:89(para)
+msgid "To launch an instance from the snapshot, select the snapshot and click <guibutton>Launch</guibutton>. Proceed with <xref linkend=\"dashboard_launch_instances_from_image\"/>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml:95(title)
+msgid "Manage an instance"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml:102(para)
+msgid "Select an instance."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml:105(para)
+msgid "In the <guilabel>More</guilabel> list in the <guilabel>Actions</guilabel> column, select the state."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_launch_instances.xml:107(para)
+msgid "You can resize or rebuild an instance. You can also choose to view the instance console log, edit instance or the security groups. Depending on the current state of the instance, you can pause, resume, suspend, soft or hard reboot, or terminate it."
+msgstr ""
+
+#: ./doc/user-guide/ch_cli.xml:10(title)
+msgid "OpenStack command-line clients"
 msgstr ""
 
 #: ./doc/user-guide/section_sdk_neutron.xml:8(para)
@@ -1829,10 +2585,6 @@ msgstr ""
 msgid "This code resides in the <filename>utils.py</filename> file, which all samples import."
 msgstr ""
 
-#: ./doc/user-guide/section_sdk_neutron.xml:98(title) ./doc/user-guide/app_cheat_sheet.xml:339(td)
-msgid "Create network"
-msgstr ""
-
 #: ./doc/user-guide/section_sdk_neutron.xml:99(para)
 msgid "The following program creates a network:"
 msgstr ""
@@ -1997,6 +2749,30 @@ msgstr ""
 msgid "List subnets: complete code listing"
 msgstr ""
 
+#: ./doc/user-guide/section_sdk_auth_nova.xml:6(title)
+msgid "Authenticate against a Compute endpoint"
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_auth_nova.xml:7(para)
+msgid "To authenticate against a Compute endpoint, instantiate a <link href=\"http://docs.openstack.org/developer/python-novaclient/api/novaclient.v1_1.client.html#novaclient.v1_1.client.Client\"> novaclient.v_1_1.client.Client</link> object:"
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_auth_nova.xml:18(para)
+msgid "Alternatively, you can instantiate a <classname>novaclient.client.Client</classname> object and pass the version number:"
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_auth_nova.xml:28(para)
+msgid "If you authenticate against an endpoint that uses a custom authentication back end, you must load the authentication plug-in and pass it to the constructor."
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_auth_nova.xml:31(para)
+msgid "The Rackspace public cloud is an OpenStack deployment that uses a custom authentication back end. To authenticate against this cloud, you must install the <link href=\"https://pypi.python.org/pypi/rackspace-novaclient/\"> rackspace-novaclient</link> library that contains the Rackspace authentication plug-in, called <literal>rackspace</literal>. The following Python code shows the additional modifications required to instantiate a <classname>Client</classname> object that can authenticate against the Rackspace custom authentication back end."
+msgstr ""
+
+#: ./doc/user-guide/section_sdk_auth_nova.xml:53(para)
+msgid "If you set the <literal>OS_AUTH_SYSTEM</literal> environment variable, check for this variable in your Python script to determine whether you need to load a custom authentication back end:"
+msgstr ""
+
 #: ./doc/user-guide/section_dashboard_stacks.xml:6(title)
 msgid "Launch and manage stacks"
 msgstr ""
@@ -2261,196 +3037,608 @@ msgstr ""
 msgid "Python scripts that use the OpenStack SDK must have access to the credentials contained in the <link linkend=\"cli_openrc\">OpenStack RC file</link>. Because credentials are sensitive information, do not include them in your scripts. This guide assumes that users source the <filename><replaceable>PROJECT</replaceable>-openrc.sh</filename> file and access the credentials by using the environment variables in the Python scripts."
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:6(title)
-msgid "Upload and manage images"
+#: ./doc/user-guide/section_sdk_manage_images.xml:8(para)
+msgid "When working with images in the SDK, you will call both <literal>glance</literal> and <literal>nova</literal> methods."
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:7(para)
-msgid "A virtual machine image, referred to in this document simply as an image, is a single file that contains a virtual disk that has a bootable operating system installed on it. Images are used to create virtual machine instances within the cloud. For information about creating image files, see the <link href=\"http://docs.openstack.org/image-guide/content/\"><citetitle>OpenStack Virtual Machine Image Guide</citetitle></link>."
+#: ./doc/user-guide/section_sdk_manage_images.xml:12(para)
+msgid "To list the available images, call the <methodname>glanceclient.v2.images.Controller.list</methodname> method:"
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:15(para)
-msgid "Depending on your role, you may have permission to upload and manage virtual machine images. Operators might restrict the upload and management of images to cloud administrators or operators only. If you have the appropriate privileges, you can use the dashboard to upload and manage images in the <guilabel>admin</guilabel> project."
+#: ./doc/user-guide/section_sdk_manage_images.xml:18(para)
+msgid "The <methodname>images</methodname> method returns a Python generator, as shown in the following interaction with the Python interpreter:"
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:22(para)
-msgid "You can also use the <placeholder-1/> and <placeholder-2/> command-line clients or the Image Service and Compute APIs to manage images. See <xref linkend=\"cli_manage_images\"/>."
+#: ./doc/user-guide/section_sdk_manage_images.xml:77(title)
+msgid "Get image by ID"
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:29(para)
-msgid "Follow this procedure to upload an image to a project."
+#: ./doc/user-guide/section_sdk_manage_images.xml:78(para)
+msgid "To retrieve an image object from its ID, call the <methodname> glanceclient.v2.images.Controller.get</methodname> method:"
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:33(para) ./doc/user-guide/section_dashboard_manage_images.xml:159(para) ./doc/user-guide/section_dashboard_manage_images.xml:206(para)
-msgid "Log in to the dashboard."
+#: ./doc/user-guide/section_sdk_manage_images.xml:88(title)
+msgid "Get image by name"
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:41(para) ./doc/user-guide/section_dashboard_manage_images.xml:167(para) ./doc/user-guide/section_dashboard_manage_images.xml:213(para)
-msgid "On the <guilabel>Project</guilabel> tab, click <guilabel>Images</guilabel>."
+#: ./doc/user-guide/section_sdk_manage_images.xml:89(para)
+msgid "The Image Service Python bindings do not support the retrieval of an image object by name. However, the Compute Python bindings enable you to get an image object by name. To get an image object by name, call the <methodname> novaclient.v1_1.images.ImageManager.find</methodname> method:"
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:45(para) ./doc/user-guide/section_dashboard_manage_images.xml:148(para)
-msgid "Click <guibutton>Create Image</guibutton>."
+#: ./doc/user-guide/section_sdk_manage_images.xml:102(para)
+msgid "To upload an image, call the <methodname> glanceclient.v2.images.ImageManager.create</methodname> method:"
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:46(para)
-msgid "The Create An Image dialog box appears."
+#: ./doc/user-guide/section_sdk_install.xml:6(title)
+msgid "Install the OpenStack SDK"
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:49(para)
-msgid "Enter the following values:"
+#: ./doc/user-guide/section_sdk_install.xml:7(para)
+msgid "Each OpenStack project has its own Python library. These libraries are bundled with the command-line clients. For example, the Python bindings for the Compute API are bundled with the <package>python-novaclient</package> package."
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:56(guilabel)
-msgid "Name"
+#: ./doc/user-guide/section_sdk_install.xml:11(para)
+msgid "For details about how to install the clients, see <link linkend=\"install_clients\">install the OpenStack command-line clients</link>."
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:59(para)
-msgid "Enter a name for the image."
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:8(para)
+msgid "Before you launch an instance, you should add security group rules to enable users to ping and use SSH to connect to the instance. To do so, you either <link href=\"#security_groups_add_rule\">add rules to the default security group</link> or add a security group with rules."
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:67(para)
-msgid "Optionally, enter a brief description of the image."
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:14(para)
+msgid "Key pairs are SSH credentials that are injected into an instance when it is launched. To use key pair injection, the image that the instance is based on must contain the <literal>cloud-init</literal> package. Each project should have at least one key pair. For more information, see <xref linkend=\"keypair_add\"/>."
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:73(guilabel)
-msgid "Image Source"
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:20(para)
+msgid "If you have generated a key pair with an external tool, you can import it into OpenStack. The key pair can be used for multiple instances that belong to a project. For more information, see <xref linkend=\"dashboard_import_keypair\"/>."
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:76(para)
-msgid "Choose the image source from the list. Your choices are <guilabel>Image Location</guilabel> and <guilabel>Image File</guilabel>."
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:25(para)
+msgid "When an instance is created in OpenStack, it is automatically assigned a fixed IP address in the network to which the instance is assigned. This IP address is permanently associated with the instance until the instance is terminated. However, in addition to the fixed IP address, a floating IP address can also be attached to an instance. Unlike fixed IP addresses, floating IP addresses are able to have their associations modified at any time, regardless of the state of the instances involved."
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:83(para)
-msgid "<guilabel>Image File</guilabel> or <guilabel>Image Location</guilabel>"
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:35(title)
+msgid "Add a rule to the default security group"
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:88(para)
-msgid "Based on your selection for <guilabel>Image Source</guilabel>, you either enter the location URL of the image in the <guilabel>Image Location</guilabel> field. or browse to the image file on your system and add it."
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:36(para)
+msgid "This procedure enables SSH and ICMP (ping) access to instances. The rules apply to all instances within a given project, and should be set for every project unless there is a reason to prohibit SSH or ICMP access to the instances."
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:97(guilabel)
-msgid "Format"
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:41(para)
+msgid "This procedure can be adjusted as necessary to add additional security group rules to a project, if your cloud requires them."
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:100(para)
-msgid "Select the correct format (for example, QCOW2) for the image."
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:46(para)
+msgid "Log in to the dashboard, choose a project, and click <guilabel>Access &amp; Security</guilabel>. The <guilabel>Security Groups</guilabel> tab shows the security groups that are available for this project."
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:107(guilabel)
-msgid "Architecture"
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:53(para)
+msgid "Select the <guilabel>default</guilabel> security group and click <guibutton>Edit Rules</guibutton>."
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:111(para)
-msgid "Specify the architecture. For example, <literal>i386</literal> for a 32-bit architecture or <literal>x86-64</literal> for a 64-bit architecture."
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:58(para)
+msgid "To allow SSH access, click <guibutton>Add Rule</guibutton>."
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:118(para)
-msgid "<guilabel>Minimum Disk (GB)</guilabel> and <guilabel>Minimum RAM (MB)</guilabel>"
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:62(para) ./doc/user-guide/section_dashboard_access_and_security.xml:105(para)
+msgid "In the Add Rule dialog box, enter the following values:"
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:122(para)
-msgid "Leave these optional fields empty."
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:69(guilabel) ./doc/user-guide/section_dashboard_access_and_security.xml:111(guilabel)
+msgid "Rule"
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:127(guilabel)
-msgid "Public"
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:71(literal)
+msgid "SSH"
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:130(para)
-msgid "Select this check box to make the image public to all users with access to the current project."
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:75(guilabel) ./doc/user-guide/section_dashboard_access_and_security.xml:119(guilabel)
+msgid "Remote"
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:137(guilabel)
-msgid "Protected"
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:84(literal) ./doc/user-guide/section_dashboard_access_and_security.xml:124(literal)
+msgid "0.0.0.0/0"
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:140(para)
-msgid "Select this check box to ensure that only users with permissions can delete the image."
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:90(para)
+msgid "To accept requests from a particular range of IP addresses, specify the IP address block in the <guilabel>CIDR</guilabel> box."
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:149(para)
-msgid "The image is queued to be uploaded. It might take some time before the status changes from Queued to Active."
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:96(para) ./doc/user-guide/section_dashboard_access_and_security.xml:129(para)
+msgid "Click <guibutton>Add</guibutton>."
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:155(title)
-msgid "Update an image"
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:97(para)
+msgid "Instances will now have SSH port 22 open for requests from any IP address."
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:156(para)
-msgid "Follow this procedure to update an existing image."
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:101(para)
+msgid "To add an ICMP rule, click <guibutton>Add Rule</guibutton>."
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:174(para)
-msgid "In the <guilabel>Actions</guilabel> column, click <guilabel>More</guilabel> and then select <guilabel>Edit</guilabel> from the list."
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:112(literal)
+msgid "All ICMP"
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:182(para)
-msgid "Change the name of the image."
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:115(guilabel)
+msgid "Direction"
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:185(para)
-msgid "Select the <guilabel>Public</guilabel> check box to make the image public."
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:116(literal)
+msgid "Ingress"
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:189(para)
-msgid "Clear the <guilabel>Public</guilabel> check box to make the image private."
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:130(para)
+msgid "Instances will now accept all incoming ICMP packets."
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:179(para)
-msgid "In the Update Image dialog box, you can perform the following actions: <placeholder-1/>"
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:137(para)
+msgid "Create at least one key pair for each project."
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:195(para)
-msgid "Click <guibutton>Update Image</guibutton>."
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:140(para) ./doc/user-guide/section_dashboard_access_and_security.xml:169(para) ./doc/user-guide/section_dashboard_access_and_security.xml:237(para)
+msgid "Log in to the dashboard, choose a project, and click <guilabel>Access &amp; Security</guilabel>."
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:200(title)
-msgid "Delete an image"
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:145(para) ./doc/user-guide/section_dashboard_access_and_security.xml:174(para)
+msgid "Click the <guilabel>Keypairs</guilabel> tab, which shows the key pairs that are available for this project."
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:201(para)
-msgid "Deletion of images is permanent and <emphasis role=\"bold\">cannot</emphasis> be reversed. Only users with the appropriate permissions can delete images."
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:150(para)
+msgid "Click <guibutton>Create Keypair</guibutton>."
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:217(para)
-msgid "Select the images that you want to delete."
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:154(para)
+msgid "In the Create Keypair dialog box, enter a name for your key pair, and click <guibutton>Create Keypair</guibutton>."
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:220(para)
-msgid "Click <guibutton>Delete Images</guibutton>."
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:160(para)
+msgid "Respond to the prompt to download the key pair."
 msgstr ""
 
-#: ./doc/user-guide/section_dashboard_manage_images.xml:223(para)
-msgid "In the <guilabel>Confirm Delete Image</guilabel> dialog box, click <guibutton>Delete Images</guibutton> to confirm the deletion."
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:179(para)
+msgid "Click <guibutton>Import Keypair</guibutton>."
 msgstr ""
 
-#: ./doc/user-guide/ch_cli.xml:10(title)
-msgid "OpenStack command-line clients"
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:183(para)
+msgid "In the Import Keypair dialog box, enter the name of your key pair, copy the public key into the <guilabel>Public Key</guilabel> box, and then click <guibutton>Import Keypair</guibutton>."
 msgstr ""
 
-#: ./doc/user-guide/section_sdk_auth_nova.xml:6(title)
-msgid "Authenticate against a Compute endpoint"
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:190(para)
+msgid "Save the <filename>*.pem</filename> file locally."
 msgstr ""
 
-#: ./doc/user-guide/section_sdk_auth_nova.xml:7(para)
-msgid "To authenticate against a Compute endpoint, instantiate a <link href=\"http://docs.openstack.org/developer/python-novaclient/api/novaclient.v1_1.client.html#novaclient.v1_1.client.Client\"> novaclient.v_1_1.client.Client</link> object:"
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:192(para)
+msgid "To change its permissions so that only you can read and write to the file, run the following command:"
 msgstr ""
 
-#: ./doc/user-guide/section_sdk_auth_nova.xml:18(para)
-msgid "Alternatively, you can instantiate a <classname>novaclient.client.Client</classname> object and pass the version number:"
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:195(replaceable) ./doc/user-guide/section_dashboard_access_and_security.xml:211(replaceable)
+msgid "yourPrivateKey"
 msgstr ""
 
-#: ./doc/user-guide/section_sdk_auth_nova.xml:28(para)
-msgid "If you authenticate against an endpoint that uses a custom authentication back end, you must load the authentication plug-in and pass it to the constructor."
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:197(para)
+msgid "If you are using the dashboard from a Windows computer, use PuTTYgen to load the <filename>*.pem</filename> file and convert and save it as <filename>*.ppk</filename>. For more information see the <link href=\"http://winscp.net/eng/docs/ui_puttygen\">WinSCP web page for PuTTYgen</link>."
 msgstr ""
 
-#: ./doc/user-guide/section_sdk_auth_nova.xml:31(para)
-msgid "The Rackspace public cloud is an OpenStack deployment that uses a custom authentication back end. To authenticate against this cloud, you must install the <link href=\"https://pypi.python.org/pypi/rackspace-novaclient/\"> rackspace-novaclient</link> library that contains the Rackspace authentication plug-in, called <literal>rackspace</literal>. The following Python code shows the additional modifications required to instantiate a <classname>Client</classname> object that can authenticate against the Rackspace custom authentication back end."
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:209(para)
+msgid "To make the key pair known to SSH, run the <placeholder-1/> command."
 msgstr ""
 
-#: ./doc/user-guide/section_sdk_auth_nova.xml:53(para)
-msgid "If you set the <literal>OS_AUTH_SYSTEM</literal> environment variable, check for this variable in your Python script to determine whether you need to load a custom authentication back end:"
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:214(para)
+msgid "The Compute database registers the public key of the key pair."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:216(para)
+msgid "The dashboard lists the key pair on the <guilabel>Access &amp; Security</guilabel> tab."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:220(title)
+msgid "Allocate a floating IP address to an instance"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:221(para)
+msgid "When an instance is created in OpenStack, it is automatically assigned a fixed IP address in the network to which the instance is assigned. This IP address is permanently associated with the instance until the instance is terminated."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:227(para)
+msgid "However, in addition to the fixed IP address, a floating IP address can also be attached to an instance. Unlike fixed IP addresses, floating IP addresses can have their associations modified at any time, regardless of the state of the instances involved. This procedure details the reservation of a floating IP address from an existing pool of addresses and the association of that address with a specific instance."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:241(para)
+msgid "Click the <guilabel>Floating IPs</guilabel> tab, which shows the floating IP addresses allocated to instances."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:246(para)
+msgid "Click <guibutton>Allocate IP to Project</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:249(para)
+msgid "Choose the pool from which to pick the IP address."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:253(para)
+msgid "Click <guibutton>Allocate IP</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:256(para)
+msgid "In the <guilabel>Floating IPs</guilabel> list, click <guibutton> Associate</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:264(para)
+msgid "The <guilabel>IP Address</guilabel> field is filled automatically, but you can add a new IP address by clicking the <guibutton>+</guibutton> button."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:271(para)
+msgid "In the <guilabel>Ports to be associated</guilabel> field, select a port from the list."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:274(para)
+msgid "The list shows all the instances with their fixed IP addresses."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:260(para)
+msgid "In the Manage Floating IP Associations dialog box, choose the following options: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:281(para)
+msgid "Click <guibutton>Associate</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:285(para)
+msgid "To disassociate an IP address from an instance, click the <guibutton>Disassociate</guibutton> button."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_access_and_security.xml:287(para)
+msgid "To release the floating IP address back into the pool of addresses, click the <guibutton>More</guibutton> button and select the <guilabel>Release Floating IP</guilabel> option."
+msgstr ""
+
+#: ./doc/user-guide/ch_sdk.xml:6(title)
+msgid "OpenStack Python SDK"
+msgstr ""
+
+#: ./doc/user-guide/ch_sdk.xml:8(para)
+msgid "Use the OpenStack Python Software Development Kit (SDK) to write Python automation scripts that create and manage resources in your OpenStack cloud. The SDK implements Python bindings to the OpenStack API, which enables you to perform automation tasks in Python by making calls on Python objects rather than making REST calls directly. All OpenStack command-line tools are implemented using the Python SDK."
+msgstr ""
+
+#: ./doc/user-guide/ch_sdk.xml:15(para)
+msgid "You should also be familiar with:"
+msgstr ""
+
+#: ./doc/user-guide/ch_sdk.xml:18(para)
+msgid "RESTful web services"
+msgstr ""
+
+#: ./doc/user-guide/ch_sdk.xml:21(para)
+msgid "HTTP/1.1"
+msgstr ""
+
+#: ./doc/user-guide/ch_sdk.xml:24(para)
+msgid "JSON and XML data serialization formats"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_swift_howto.xml:6(title)
+msgid "Manage objects and containers"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_swift_howto.xml:8(para)
+msgid "The OpenStack Object Storage service provides the <placeholder-1/> client, which is a command-line interface (CLI). Use this client to list objects and containers, upload objects to containers, and download or delete objects from containers. You can also gather statistics and update metadata for accounts, containers, and objects."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_swift_howto.xml:14(para)
+msgid "This client is based on the native swift client library, <literal>client.py</literal>, which seamlessly re-authenticates if the current token expires during processing, retries operations multiple times, and provides a processing concurrency of 10."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_swift_howto.xml:20(title)
+msgid "Create and manage containers"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_swift_howto.xml:23(para)
+msgid "To create a container, run the following command and replace <replaceable>CONTAINER</replaceable> with the name of your container."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_swift_howto.xml:28(para)
+msgid "To list all containers: run the following command:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_swift_howto.xml:32(para)
+msgid "To check the status of containers, run the following command:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_swift_howto.xml:42(para)
+msgid "You can also use the <placeholder-1/> command with the <replaceable>ACCOUNT</replaceable> or <replaceable>CONTAINER</replaceable> names as parameters."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_swift_howto.xml:61(title)
+msgid "Manage access"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_swift_howto.xml:64(para)
+msgid "Users have roles on accounts. For example, a user with the admin role has full access to all containers and objects in an account. You can set access control lists (ACLs) at the container level and support lists for read and write access, which you set with the <literal>X-Container-Read</literal> and <literal>X-Container-Write</literal> headers."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_swift_howto.xml:70(para)
+msgid "To give a user read access, use the <placeholder-1/> command with the <parameter>-r</parameter> parameter. To give a user write access, use the <parameter>-w</parameter> parameter."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_swift_howto.xml:73(para)
+msgid "The following example enables the <literal>testuser</literal> user to read objects in the container:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_swift_howto.xml:76(para)
+msgid "You can also use this command with a list of users."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_swift_howto.xml:79(para)
+msgid "If you use StaticWeb middleware to enable Object Storage to serve public web content, use <literal>.r:</literal>, followed by a list of allowed referrers."
+msgstr ""
+
+#: ./doc/user-guide/section_cli_swift_howto.xml:82(para)
+msgid "The following command gives object access to all referring domains:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_swift_howto.xml:89(title)
+msgid "Manage objects"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_swift_howto.xml:92(para)
+msgid "To upload an object to a container, run the following command:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_swift_howto.xml:94(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:96(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:101(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:115(replaceable) ./doc/user-guide/section_cli_swift_howto.xml:120(replaceable)
+msgid "OBJECT_FILENAME"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_swift_howto.xml:95(para)
+msgid "To upload in chunks, for large files, run the following command:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_swift_howto.xml:96(replaceable)
+msgid "CHUNK_SIZE"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_swift_howto.xml:99(para)
+msgid "To check the status of the object, run the following command:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_swift_howto.xml:114(para)
+msgid "To list the objects in a container, run the following command:"
+msgstr ""
+
+#: ./doc/user-guide/section_cli_swift_howto.xml:118(para)
+msgid "To download an object from a container:, run the following command:"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:6(title)
+msgid "Create and manage volumes"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:8(para)
+msgid "Volumes are block storage devices that you attach to instances to enable persistent storage. You can attach a volume to a running instance or detach a volume and attach it to another instance at any time. You can also create a snapshot from or delete a volume. Only administrative users can create volume types."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:15(title)
+msgid "Create a volume"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:18(para) ./doc/user-guide/section_dashboard_manage_volumes.xml:136(para) ./doc/user-guide/section_dashboard_manage_volumes.xml:170(para) ./doc/user-guide/section_dashboard_manage_volumes.xml:212(para) ./doc/user-guide/section_dashboard_manage_volumes.xml:251(para)
+msgid "Log in to the dashboard, choose a project, and click <guibutton>Volumes</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:22(para) ./doc/user-guide/section_dashboard_manage_volumes.xml:124(para)
+msgid "Click <guibutton>Create Volume</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:23(para)
+msgid "In the dialog box that opens, enter or select the following values."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:32(guilabel)
+msgid "Volume Name"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:36(para)
+msgid "Specify a name for the volume."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:47(para)
+msgid "Optionally, provide a brief description for the volume."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:54(guilabel)
+msgid "Type"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:58(para)
+msgid "Leave this field blank."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:64(guilabel)
+msgid "Size (GB)"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:68(para)
+msgid "The size of the volume in gigabytes."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:75(guilabel)
+msgid "Volume Source"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:79(para)
+msgid "Select one of the following options:"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:82(guilabel)
+msgid "No source, empty volume"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:83(para)
+msgid "Creates an empty volume."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:84(para)
+msgid "An empty volume does not contain a file system or a partition table."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:88(guilabel)
+msgid "Snapshot"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:89(para)
+msgid "If you choose this option, a new field for <guilabel>Use snapshot as a source</guilabel> displays. You can select the snapshot from the list."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:95(guilabel)
+msgid "Image"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:96(para)
+msgid "If you choose this option, a new field for <guilabel>Use image as a source</guilabel> displays. You can select the image from the list."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:99(para)
+msgid "Select the <guilabel>Availability Zone</guilabel> from the list. By default, this value is set to the availability zone given by the cloud provider (for example, <literal>us-west</literal> or <literal>apac-south</literal>). For some cases, it could be <literal>nova</literal>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:107(guilabel)
+msgid "Volume"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:108(para)
+msgid "If you choose this option, a new field for <guilabel>Use volume as a source</guilabel> displays. You can select the volume from the list."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:114(para)
+msgid "Options to use a snapshot or a volume as the source for a volume are displayed only if there are existing snapshots or volumes."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:127(para)
+msgid "The dashboard shows the volume on the <guilabel>Volumes</guilabel> tab."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:131(title)
+msgid "Attach a volume to an instance"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:132(para)
+msgid "After you create one or more volumes, you can attach them to instances. You can attach a volume to one instance at a time."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:140(para)
+msgid "Select the volume to add to an instance and click <guibutton>Edit Attachments</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:144(para)
+msgid "In the <guilabel>Manage Volume Attachments</guilabel> dialog box, select an instance."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:148(para)
+msgid "Enter the name of the device from which the volume is accessible by the instance."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:151(para)
+msgid "The actual device name might differ from the volume name because of hypervisor settings."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:156(para)
+msgid "Click <guibutton>Attach Volume</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:157(para)
+msgid "The dashboard shows the instance to which the volume is now attached and the device name."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:161(para)
+msgid "You can view the status of a volume in the <guilabel>Volumes</guilabel> tab of the dashboard. The volume is either Available or In-Use."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:163(para)
+msgid "Now you can log in to the instance and mount, format, and use the disk."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:167(title)
+msgid "Detach a volume from an instance"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:174(para)
+msgid "Select the volume and click <guibutton>Edit Attachments</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:177(para)
+msgid "Click <guibutton>Detach Volume</guibutton> and confirm your changes."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:181(para) ./doc/user-guide/section_dashboard_manage_volumes.xml:261(para)
+msgid "A message indicates whether the action was successful."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:184(title)
+msgid "Create a snapshot from a volume"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:187(para)
+msgid "Log in to the dashboard, choose a project, and click <guilabel>Volumes</guilabel>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:191(para)
+msgid "Select a volume from which to create a snapshot."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:194(para)
+msgid "From the <guilabel>More</guilabel> list, select <guilabel>Create Snapshot</guilabel>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:198(para)
+msgid "In the dialog box that opens, enter a snapshot name and a brief description."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:202(para)
+msgid "Confirm your changes."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:203(para)
+msgid "The dashboard shows the new volume snapshot in <guilabel>Volume Snapshots</guilabel> tab."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:209(title)
+msgid "Edit a volume"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:221(para)
+msgid "On the <guilabel>Project</guilabel> tab, click <guilabel>Volumes</guilabel>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:228(para)
+msgid "In the <guilabel>Actions</guilabel> column, click <guilabel>Edit Volume</guilabel>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:232(para)
+msgid "In the <guilabel>Edit Volume</guilabel> dialog box, update the name and description of the image."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:236(para)
+msgid "Click <guibutton>Edit Volume</guibutton>."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:240(para)
+msgid "You can extend a volume by using the <guilabel>Extend Volume</guilabel> option available in the <guibutton>More</guibutton> dropdown list and entering the new value for volume size."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:246(title)
+msgid "Delete a volume"
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:247(para)
+msgid "When you delete an instance, the data in its attached volumes is not destroyed."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:255(para)
+msgid "Select the check boxes for the volumes that you want to delete."
+msgstr ""
+
+#: ./doc/user-guide/section_dashboard_manage_volumes.xml:259(para)
+msgid "Click <guibutton>Delete Volumes</guibutton> and confirm your choice."
 msgstr ""
 
 #: ./doc/user-guide/section_sdk_configure_instances.xml:7(para)
@@ -2489,10 +3677,6 @@ msgstr ""
 msgid "To list keypairs, call the <methodname><link href=\"http://docs.openstack.org/developer/python-novaclient/api/novaclient.v1_1.keypairs.html#novaclient.v1_1.keypairs.KeypairManager.list\">novaclient.v1_1.keypairs.KeypairManager.list</link></methodname> method:"
 msgstr ""
 
-#: ./doc/user-guide/section_sdk_configure_instances.xml:72(title) ./doc/user-guide/section_cli_nova_configure_instances.xml:111(title)
-msgid "Create and manage security groups"
-msgstr ""
-
 #: ./doc/user-guide/section_sdk_configure_instances.xml:73(para)
 msgid "To list security groups for the current project, call the <methodname><link href=\"http://docs.openstack.org/developer/python-novaclient/api/novaclient.v1_1.security_groups.html#novaclient.v1_1.security_groups.SecurityGroupManager.list\">novaclient.v_1.security_groups.SecurityGroupManager.list</link></methodname> method:"
 msgstr ""
@@ -2505,10 +3689,6 @@ msgstr ""
 msgid "To delete a security group, call the <methodname><link href=\"http://docs.openstack.org/developer/python-novaclient/api/novaclient.v1_1.security_groups.html#novaclient.v1_1.security_groups.SecurityGroupManager.delete\"> novaclient.v_1.security_groups.SecurityGroupManager.delete</link></methodname> method, passing either a <link href=\"http://docs.openstack.org/developer/python-novaclient/api/novaclient.v1_1.security_groups.html#novaclient.v1_1.security_groups.SecurityGroup\">novaclient.v1_1.security_groups.SecurityGroup</link> object or group ID as an argument:"
 msgstr ""
 
-#: ./doc/user-guide/section_sdk_configure_instances.xml:97(title) ./doc/user-guide/section_cli_nova_configure_instances.xml:138(title)
-msgid "Create and manage security group rules"
-msgstr ""
-
 #: ./doc/user-guide/section_sdk_configure_instances.xml:98(para)
 msgid "Access the security group rules from the <literal>rules</literal> attribute of a <link href=\"http://docs.openstack.org/developer/python-novaclient/api/novaclient.v1_1.security_groups.html#novaclient.v1_1.security_groups.SecurityGroup\">novaclient.v1_1.security_groups.SecurityGroup</link> object:"
 msgstr ""
@@ -2517,1188 +3697,8 @@ msgstr ""
 msgid "To add a rule, to a security group, call the <methodname><link href=\"http://docs.openstack.org/developer/python-novaclient/api/novaclient.v1_1.security_group_rules.html#novaclient.v1_1.security_group_rules.SecurityGroupRuleManager.create\">novaclient.v1_1.security_group_rules.SecurityGroupRuleManager.create</link></methodname> method:"
 msgstr ""
 
-#: ./doc/user-guide/section_cli_nova_manage_instances.xml:6(title)
-msgid "Manage instances and hosts"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_manage_instances.xml:7(para)
-msgid "Instances are virtual machines that run inside the cloud on physical compute nodes. The Compute service manages instances. A host is the node on which a group of instances resides."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_manage_instances.xml:11(para)
-msgid "This section describes how to perform the different tasks involved in instance management, such as adding floating IP addresses, stopping and starting instances, and terminating instances. This section also discusses node management tasks."
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:7(title)
-msgid "OpenStack command-line interface cheat sheet"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:9(para)
-msgid "The following tables give a quick reference of the most used command-line commands."
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:15(caption)
-msgid "Identity (keystone)"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:21(th) ./doc/user-guide/app_cheat_sheet.xml:67(th) ./doc/user-guide/app_cheat_sheet.xml:141(th) ./doc/user-guide/app_cheat_sheet.xml:334(th) ./doc/user-guide/app_cheat_sheet.xml:375(th) ./doc/user-guide/app_cheat_sheet.xml:459(th)
-msgid "Command"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:26(td)
-msgid "List all users"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:32(td)
-msgid "List Identity service catalog"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:38(td)
-msgid "List all services in service catalog"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:44(td)
-msgid "Create new user"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:46(replaceable) ./doc/user-guide/app_cheat_sheet.xml:53(replaceable) ./doc/user-guide/app_cheat_sheet.xml:186(replaceable) ./doc/user-guide/app_cheat_sheet.xml:215(replaceable) ./doc/user-guide/app_cheat_sheet.xml:222(replaceable) ./doc/user-guide/app_cheat_sheet.xml:228(replaceable) ./doc/user-guide/app_cheat_sheet.xml:234(replaceable) ./doc/user-guide/app_cheat_sheet.xml:240(replaceable) ./doc/user-guide/app_cheat_sheet.xml:246(replaceable) ./doc/user-guide/app_cheat_sheet.xml:252(replaceable) ./doc/user-guide/app_cheat_sheet.xml:258(replaceable) ./doc/user-guide/app_cheat_sheet.xml:266(replaceable) ./doc/user-guide/app_cheat_sheet.xml:273(replaceable) ./doc/user-guide/app_cheat_sheet.xml:341(replaceable) ./doc/user-guide/app_cheat_sheet.xml:385(replaceable)
-msgid "NAME"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:46(replaceable)
-msgid "TENANT"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:47(replaceable)
-msgid "EMAIL"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:47(replaceable)
-msgid "BOOL"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:51(td)
-msgid "Create new tenant"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:53(replaceable)
-msgid "DESCRIPTION"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:61(caption)
-msgid "Image Service (glance)"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:72(td)
-msgid "List images you can access"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:78(td)
-msgid "Delete specified image"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:80(replaceable) ./doc/user-guide/app_cheat_sheet.xml:86(replaceable) ./doc/user-guide/app_cheat_sheet.xml:92(replaceable) ./doc/user-guide/app_cheat_sheet.xml:166(replaceable) ./doc/user-guide/app_cheat_sheet.xml:266(replaceable)
-msgid "IMAGE"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:84(td)
-msgid "Describe a specific image"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:90(td)
-msgid "Update image"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:99(td)
-msgid "Kernel image"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:107(td)
-msgid "RAM image"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:115(td)
-msgid "Three-part image"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:124(td)
-msgid "Register raw image"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:135(caption)
-msgid "Compute (nova)"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:146(td)
-msgid "List instances, notice status of instance"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:158(td)
-msgid "List flavors"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:164(td)
-msgid "Boot an instance using flavor and image names (if names are unique)"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:166(replaceable) ./doc/user-guide/app_cheat_sheet.xml:258(replaceable)
-msgid "FLAVOR"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:166(replaceable)
-msgid "INSTANCE_NAME"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:172(td)
-msgid "Login to instance"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:175(replaceable)
-msgid "NETNS_NAME"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:175(replaceable)
-msgid "USER"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:175(replaceable)
-msgid "SERVER"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:178(para)
-msgid "Note, in CirrOS the password for user <literal>cirros</literal> is \"cubswin:)\" without the quotes."
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:184(td)
-msgid "Show details of instance"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:191(td)
-msgid "View console log of instance"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:197(td)
-msgid "Set metadata on an instance"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:203(td) ./doc/user-guide/section_dashboard_launch_instances.xml:69(title)
-msgid "Create an instance snapshot"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:210(th)
-msgid "Pause, suspend, stop, rescue, resize, rebuild, reboot an instance"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:213(td)
-msgid "Pause"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:220(td)
-msgid "Unpause"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:226(td)
-msgid "Suspend"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:232(td)
-msgid "Unsuspend"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:238(td)
-msgid "Stop"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:244(td)
-msgid "Start"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:250(td)
-msgid "Rescue"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:256(td)
-msgid "Resize"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:264(td)
-msgid "Rebuild"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:271(td)
-msgid "Reboot"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:278(td)
-msgid "Inject user data and files into an instance"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:280(replaceable)
-msgid "FILE"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:280(replaceable)
-msgid "INSTANCE"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:284(para)
-msgid "To validate that the file is there, ssh into the instance, and look in <filename>/var/lib/cloud</filename> for the file."
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:290(th)
-msgid "Inject a keypair into an instance and access the instance with that keypair"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:294(td)
-msgid "Create keypair"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:301(td)
-msgid "Boot"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:308(td)
-msgid "Use ssh to connect to the instance"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:315(th)
-msgid "Manage security groups"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:318(td)
-msgid "Add rules to default security group allowing ping and SSH between instances in the default security group"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:328(caption)
-msgid "Networking (neutron)"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:345(td)
-msgid "Create a subnet"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:347(replaceable)
-msgid "NETWORK_NAME"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:352(td)
-msgid "List network and subnet"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:359(td)
-msgid "Examine details of network and subnet"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:361(replaceable) ./doc/user-guide/app_cheat_sheet.xml:362(replaceable)
-msgid "ID_OR_NAME_OF_NETWORK"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:369(caption)
-msgid "Block Storage (cinder)"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:380(th)
-msgid "Manage volumes and volume snapshots"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:383(td)
-msgid "Create a new volume"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:385(replaceable)
-msgid "SIZE_IN_GB"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:390(td)
-msgid "Boot an instance and attach to volume"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:396(td)
-msgid "List volumes, notice status of volume"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:402(td)
-msgid "Attach volume to instance after instance is active, and volume is available"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:405(replaceable)
-msgid "INSTANCE_ID"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:405(replaceable)
-msgid "VOLUME_ID"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:410(th)
-msgid "Manage volumes after login into the instance"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:413(td)
-msgid "List storage devices"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:419(td)
-msgid "Make filesystem on volume"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:425(td)
-msgid "Create a mountpoint"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:431(td)
-msgid "Mount the volume at the mountpoint"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:437(td)
-msgid "Create a file on the volume"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:444(td)
-msgid "Unmount the volume"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:453(caption)
-msgid "Object Storage (swift)"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:464(td)
-msgid "Display information for the account, container, or object"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:467(replaceable)
-msgid "ACCOUNT"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:469(replaceable)
-msgid "OBJECT"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:473(td)
-msgid "List containers"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:479(td) ./doc/user-guide/section_dashboard_manage_containers.xml:19(title)
-msgid "Create a container"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:481(replaceable) ./doc/user-guide/app_cheat_sheet.xml:487(replaceable) ./doc/user-guide/app_cheat_sheet.xml:500(replaceable) ./doc/user-guide/app_cheat_sheet.xml:506(replaceable)
-msgid "CONTAINER_NAME"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:485(td)
-msgid "Upload file to a container"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:487(replaceable) ./doc/user-guide/app_cheat_sheet.xml:500(replaceable) ./doc/user-guide/app_cheat_sheet.xml:506(replaceable)
-msgid "FILE_NAME"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:492(td)
-msgid "List objects in container"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:498(td)
-msgid "Download object from container"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:504(td)
-msgid "Upload with chunks, for large file"
-msgstr ""
-
-#: ./doc/user-guide/app_cheat_sheet.xml:506(replaceable)
-msgid "SIZE"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_auth_keystone.xml:6(title)
-msgid "Authenticate against an Identity endpoint"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_auth_keystone.xml:7(para)
-msgid "To authenticate against the Identity v2.0 endpoint, instantiate a <link href=\"http://docs.openstack.org/developer/python-keystoneclient/api/keystoneclient.v2_0.client.html#keystoneclient.v2_0.client.Client\"> keystoneclient.v_20.client.Client</link> object:"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_auth_keystone.xml:18(para)
-msgid "After you instantiate a <classname>Client</classname> object, you can retrieve the token by accessing its <literal>auth_token</literal> attribute object:"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_auth_keystone.xml:24(para)
-msgid "If the OpenStack cloud is configured to use public-key infrastructure (PKI) tokens, the Python script output looks something like this:"
-msgstr ""
-
-#: ./doc/user-guide/section_sdk_auth_keystone.xml:35(para)
-msgid "This example shows a subset of a PKI token. A complete token is over 5000 characters long."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml:6(title)
-msgid "Launch and manage instances"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml:7(para)
-msgid "Instances are virtual machines that run inside the cloud."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml:9(para)
-msgid "You can <link linkend=\"dashboard_launch_instances_from_image\">launch an instance</link> from the following sources:"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml:12(para)
-msgid "Images uploaded to the OpenStack Image Service, as described in <xref linkend=\"dashboard_manage_images\"/>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml:14(para)
-msgid "Image that you have copied to a persistent volume. The instance launches from the volume, which is provided by the <systemitem class=\"service\">cinder-volume</systemitem> API through iSCSI."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml:23(title)
-msgid "Connect to your instance by using SSH"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml:24(para)
-msgid "To use SSH to connect to your instance, you use the downloaded keypair file."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml:27(para)
-msgid "The user name is <literal>ubuntu</literal> for the Ubuntu cloud images on TryStack."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml:32(para)
-msgid "Copy the IP address for your instance."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml:35(para)
-msgid "Use the <placeholder-1/> command to make a secure connection to the instance. For example:"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml:41(para)
-msgid "At the prompt, type <literal>yes</literal>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml:47(title)
-msgid "Track usage for instances"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml:48(para)
-msgid "You can track usage for instances for each project. You can track costs per month by showing metrics like number of vCPUs, disks, RAM, and uptime for all your instances."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml:54(para)
-msgid "Log in to the dashboard, choose a project, and click <guilabel>Overview</guilabel>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml:58(para)
-msgid "To query the instance usage for a month, select a month and click <guibutton>Submit</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml:63(para)
-msgid "To download a summary, click <guibutton>Download CSV Summary</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml:72(para) ./doc/user-guide/section_dashboard_launch_instances.xml:98(para)
-msgid "Log in to the dashboard, choose a project, and click <guilabel>Instances</guilabel>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml:76(para)
-msgid "Select the instance from which to create a snapshot."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml:79(para)
-msgid "In the <guilabel>Actions</guilabel> column, click <guilabel>Create Snapshot</guilabel>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml:83(para)
-msgid "In the Create Snapshot dialog box, enter a name for the snapshot, and click <guibutton>Create Snapshot</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml:85(para)
-msgid "The <guilabel>Images</guilabel> category shows the instance snapshot."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml:89(para)
-msgid "To launch an instance from the snapshot, select the snapshot and click <guibutton>Launch</guibutton>. Proceed with <xref linkend=\"dashboard_launch_instances_from_image\"/>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml:95(title)
-msgid "Manage an instance"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml:102(para)
-msgid "Select an instance."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml:105(para)
-msgid "In the <guilabel>More</guilabel> list in the <guilabel>Actions</guilabel> column, select the state."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances.xml:107(para)
-msgid "You can resize or rebuild an instance. You can also choose to view the instance console log, edit instance or the security groups. Depending on the current state of the instance, you can pause, resume, suspend, soft or hard reboot, or terminate it."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:10(title)
-msgid "Launch an instance"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:12(para)
-msgid "When you launch an instance from an image, OpenStack creates a local copy of the image on the compute node where the instance starts."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:14(para)
-msgid "When you launch an instance from a volume, note the following steps:"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:18(para)
-msgid "To select the volume to from which to launch, launch an instance from an arbitrary image on the volume. The image that you select does not boot. Instead, it is replaced by the image on the volume that you choose in the next steps."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:22(para)
-msgid "To boot a Xen image from a volume, the image you launch in must be the same type, fully virtualized or paravirtualized, as the one on the volume."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:27(para)
-msgid "Select the volume or volume snapshot from which to boot. Enter a device name. Enter <literal>vda</literal> for KVM images or <literal>xvda</literal> for Xen images."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:34(para)
-msgid "Log in to the dashboard, choose a project, and click <guilabel>Images</guilabel>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:36(para)
-msgid "The dashboard shows the images that have been uploaded to OpenStack Image Service and are available for this project."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:39(para)
-msgid "For details on creating images, see <link href=\"http://docs.openstack.org/image-guide/content/ch_creating_images_manually.html\">Creating images manually</link> in the <citetitle>OpenStack Virtual Machine Image Guide</citetitle>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:45(para)
-msgid "Select an image and click <guibutton>Launch</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:48(para)
-msgid "In the Launch Instance dialog box, specify the following values:"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:55(guilabel)
-msgid "Details"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:60(guilabel)
-msgid "Availability Zone"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:62(para)
-msgid "By default, this value is set to the availability zone given by the cloud provider (for example, <literal>us-west</literal> or <literal>apac-south</literal>). For some cases, it could be <literal>nova</literal>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:69(guilabel)
-msgid "Instance Name"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:70(para)
-msgid "Assign a name to the virtual machine."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:71(para)
-msgid "The name you assign here becomes the initial host name of the server. After the server is built, if you change the server name in the API or change the host name directly, the names are not updated in the dashboard."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:75(para)
-msgid "Server names are not guaranteed to be unique when created so you could have two instances with the same host name."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:82(guilabel)
-msgid "Flavor"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:83(para)
-msgid "Specify the size of the instance to launch."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:84(para)
-msgid "The flavor is selected based on the size of the image selected for launching an instance. For example, while creating an image, if you have entered the value in the <guilabel>Minimum RAM (MB)</guilabel> field as 2048, then on selecting the image, the default flavor is <guilabel>m1.small</guilabel>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:94(guilabel)
-msgid "Instance Count"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:95(para)
-msgid "To launch multiple instances, enter a value greater than 1. The default is 1."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:99(guilabel)
-msgid "Instance Boot Source"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:100(para)
-msgid "Your options are:"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:103(guilabel)
-msgid "Boot from image"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:104(para)
-msgid "If you choose this option, a new field for <guilabel>Image Name</guilabel> displays. You can select the image from the list."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:109(guilabel)
-msgid "Boot from snapshot"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:110(para)
-msgid "If you choose this option, a new field for <guilabel>Instance Snapshot</guilabel> displays. You can select the snapshot from the list."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:115(guilabel)
-msgid "Boot from volume"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:116(para)
-msgid "If you choose this option, a new field for <guilabel>Volume</guilabel> displays. You can select the volume from the list."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:121(guilabel)
-msgid "Boot from image (creates a new volume)"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:122(para)
-msgid "With this option, you can boot from an image and create a volume by entering the <guilabel>Device Size</guilabel> and <guilabel>Device Name</guilabel> for your volume. Click the <guilabel>Delete on Terminate</guilabel> option to delete the volume on terminating the instance."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:130(guilabel)
-msgid "Boot from volume snapshot (creates a new volume)"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:132(para)
-msgid "Using this option, you can boot from a volume snapshot and create a new volume by choosing <guilabel>Volume Snapshot</guilabel> from a list and adding a <guilabel>Device Name</guilabel> for your volume. Click the <guilabel>Delete on Terminate</guilabel> option to delete the volume on terminating the instance."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:141(para)
-msgid "Since you are launching an instance from an image, <guilabel>Boot from image</guilabel> is chosen by default."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:147(guilabel)
-msgid "Image Name"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:148(para)
-msgid "This field changes based on your previous selection. Since you have chosen to launch an instance using an image, the <guilabel>Image Name</guilabel> field displays. Select the image name from the dropdown list."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:155(guilabel)
-msgid "Access &amp; Security"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:159(guilabel)
-msgid "Keypair"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:160(para)
-msgid "Specify a key pair."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:161(para)
-msgid "If the image uses a static root password or a static key set (neither is recommended), you do not need to provide a key pair to launch the instance."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:166(guilabel)
-msgid "Security Groups"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:167(para)
-msgid "Activate the security groups that you want to assign to the instance."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:169(para)
-msgid "Security groups are a kind of cloud firewall that define which incoming network traffic is forwarded to instances. For details, see <xref linkend=\"security_groups_add_rule\"/>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:173(para)
-msgid "If you have not created any security groups, you can assign only the default security group to the instance."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:181(guilabel)
-msgid "Selected Networks"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:182(para)
-msgid "To add a network to the instance, click the <guibutton>+</guibutton> in the <guilabel>Available Networks</guilabel> field."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:188(guilabel)
-msgid "Post-Creation"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:191(guilabel)
-msgid "Customization Script"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:192(para)
-msgid "Specify a customization script that runs after your instance launches."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:196(guilabel)
-msgid "Advanced Options"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:199(guilabel)
-msgid "Disk Partition"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:200(para)
-msgid "Select the type of disk partition from the dropdown list."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:204(guilabel)
-msgid "Automatic"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:206(para)
-msgid "Entire disk is single partition and automatically resizes."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:210(guilabel)
-msgid "Manual"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:212(para)
-msgid "Faster build times but requires manual partitioning."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:231(para)
-msgid "Click <guibutton>Launch</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:232(para)
-msgid "The instance starts on a compute node in the cloud."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:235(para)
-msgid "The <guilabel>Instances</guilabel> tab shows the instance's name, its private and public IP addresses, size, status, task, and power state."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:238(para)
-msgid "If you did not provide a key pair, security groups, or rules, users can access the instance only from inside the cloud through VNC. Even pinging the instance is not possible without an ICMP rule configured. To access the instance through a VNC console, see <xref linkend=\"instance_console\"/>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:6(title)
-msgid "Create and manage object containers"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:8(para)
-msgid "OpenStack Object Storage provides a distributed, API-accessible storage platform that can be integrated directly into an application or used to store any type of file, including VM images, backups, archives, or media files. In the OpenStack Dashboard, you can only manage containers and objects."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:13(para)
-msgid "In OpenStack Object Storage, containers provide storage for objects in a manner similar to a Windows folder or Linux file directory, though they cannot be nested. An object in OpenStack consists of the file to be stored in the container and any accompanying metadata."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:22(para) ./doc/user-guide/section_dashboard_manage_containers.xml:44(para) ./doc/user-guide/section_dashboard_manage_containers.xml:79(para) ./doc/user-guide/section_dashboard_manage_containers.xml:103(para) ./doc/user-guide/section_dashboard_manage_containers.xml:144(para) ./doc/user-guide/section_dashboard_manage_containers.xml:171(para)
-msgid "Log in to the dashboard, choose a project, and click <guilabel>Containers</guilabel>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:26(para)
-msgid "Click <guibutton>Create Container</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:29(para)
-msgid "In the Create Container dialog box, enter a name for the container, and then click<guibutton>Create Container</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:34(para)
-msgid "You have successfully created a container."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:35(para)
-msgid "To delete a container, click the <guibutton>More</guibutton> button and select <guilabel>Delete Container</guilabel>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:41(title)
-msgid "Upload an object"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:48(para) ./doc/user-guide/section_dashboard_manage_containers.xml:83(para) ./doc/user-guide/section_dashboard_manage_containers.xml:107(para) ./doc/user-guide/section_dashboard_manage_containers.xml:148(para) ./doc/user-guide/section_dashboard_manage_containers.xml:175(para)
-msgid "Select the container in which you want to store your object."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:51(para) ./doc/user-guide/section_dashboard_manage_containers.xml:66(para) ./doc/user-guide/section_dashboard_manage_containers.xml:151(para)
-msgid "Click <guibutton>Upload Object</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:52(para) ./doc/user-guide/section_dashboard_manage_containers.xml:152(para)
-msgid "The Upload Object To Container: <replaceable>&lt;name&gt;</replaceable> dialog box is displayed. <replaceable>&lt;name&gt;</replaceable> is the name of the container to which you are uploading the object."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:59(para) ./doc/user-guide/section_dashboard_manage_containers.xml:159(para)
-msgid "Enter a name for the object."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:62(para) ./doc/user-guide/section_dashboard_manage_containers.xml:90(para)
-msgid "Browse to and select the file that you want to upload."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:69(para)
-msgid "You have successfully uploaded an object to the container."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:70(para) ./doc/user-guide/section_dashboard_manage_containers.xml:97(para)
-msgid "To delete an object, click the <guibutton>More</guibutton> button and select <guilabel>Delete Object</guilabel>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:75(title)
-msgid "Manage an object"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:77(title)
-msgid "To edit an object"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:86(para)
-msgid "Click <guibutton>More</guibutton> and choose <guilabel>Edit</guilabel> from the dropdown list."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:87(para)
-msgid "The Edit Object dialog box is displayed."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:93(para) ./doc/user-guide/section_dashboard_manage_containers.xml:162(para)
-msgid "Click <guibutton>Update Object</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:101(title)
-msgid "To copy an object from one container to another"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:110(para)
-msgid "Click <guibutton>More</guibutton> and choose <guilabel>Copy</guilabel> from the dropdown list."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:114(para)
-msgid "In the Copy Object: launch dialog box, enter the following values:"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:119(para)
-msgid "<guilabel>Destination Container</guilabel>: Choose the destination container from the list."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:123(para)
-msgid "<guilabel>Path</guilabel>: Specify a path in which the new copy should be stored inside of the selected container."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:128(para)
-msgid "<guilabel>Destination object name</guilabel>: Enter a name for the object in the new container."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:136(para)
-msgid "Click <guibutton>Copy Object</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:140(title)
-msgid "To create a metadata-only object without a file"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:141(para)
-msgid "You can create a new object in container without a file available and can upload the file later when it is ready. This temporary object acts a place-holder for a new object, and enables the user to share object metadata and URL info in advance."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:166(title)
-msgid "To create a pseudo-folder"
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:167(para)
-msgid "Pseudo-folders are similar to folders in your desktop operating system. They are virtual collections defined by a common prefix on the object's name."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:178(para)
-msgid "Click <guibutton>Create Pseudo-folder</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:180(para)
-msgid "The Create Pseudo-Folder in Container <replaceable>&lt;name&gt; </replaceable> dialog box is displayed. <replaceable>&lt;name&gt; </replaceable> is the name of the container to which you are uploading the object."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:187(para)
-msgid "Enter a name for the pseudo-folder."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:189(para)
-msgid "A slash (/) character is used as the delimiter for pseudo-folders in the Object Store."
-msgstr ""
-
-#: ./doc/user-guide/section_dashboard_manage_containers.xml:193(para)
-msgid "Click <guibutton>Create</guibutton>."
-msgstr ""
-
-#: ./doc/user-guide/bk-user-guide.xml:8(title)
-msgid "OpenStack End User Guide"
-msgstr ""
-
-#: ./doc/user-guide/bk-user-guide.xml:9(titleabbrev)
-msgid "End User Guide"
-msgstr ""
-
-#: ./doc/user-guide/bk-user-guide.xml:17(orgname) ./doc/user-guide/bk-user-guide.xml:22(holder)
-msgid "OpenStack Foundation"
-msgstr ""
-
-#: ./doc/user-guide/bk-user-guide.xml:21(year)
-msgid "2014"
-msgstr ""
-
-#: ./doc/user-guide/bk-user-guide.xml:24(releaseinfo)
-msgid "current"
-msgstr ""
-
-#: ./doc/user-guide/bk-user-guide.xml:25(productname)
-msgid "OpenStack"
-msgstr ""
-
-#: ./doc/user-guide/bk-user-guide.xml:29(remark)
-msgid "Copyright details are filled in by the template."
-msgstr ""
-
-#: ./doc/user-guide/bk-user-guide.xml:34(para)
-msgid "OpenStack is an open-source cloud computing platform for public and private clouds. A series of interrelated projects deliver a cloud infrastructure solution. This guide shows OpenStack end users how to create and manage resources in an OpenStack cloud with the OpenStack dashboard and OpenStack client commands."
-msgstr ""
-
-#: ./doc/user-guide/bk-user-guide.xml:44(date)
-msgid "2014-05-09"
-msgstr ""
-
-#: ./doc/user-guide/bk-user-guide.xml:48(para)
-msgid "Add a command line cheat sheet."
-msgstr ""
-
-#: ./doc/user-guide/bk-user-guide.xml:55(date)
-msgid "2014-04-17"
-msgstr ""
-
-#: ./doc/user-guide/bk-user-guide.xml:59(para)
-msgid "For the Icehouse release, this guide has been updated with changes to the dashboard plus the moving of the command reference appendix as indicated below."
-msgstr ""
-
-#: ./doc/user-guide/bk-user-guide.xml:69(date)
-msgid "2014-01-31"
-msgstr ""
-
-#: ./doc/user-guide/bk-user-guide.xml:73(para)
-msgid "Removed the command reference appendix. This information is now in the <link href=\"http://docs.openstack.org/cli-reference/content/\"><citetitle>OpenStack Command-Line Interface Reference</citetitle></link>."
-msgstr ""
-
-#: ./doc/user-guide/bk-user-guide.xml:83(date)
-msgid "2013-12-30"
-msgstr ""
-
-#: ./doc/user-guide/bk-user-guide.xml:87(para)
-msgid "Added the OpenStack Python SDK chapter."
-msgstr ""
-
-#: ./doc/user-guide/bk-user-guide.xml:94(date)
-msgid "2013-10-17"
-msgstr ""
-
-#: ./doc/user-guide/bk-user-guide.xml:98(para)
-msgid "Havana release."
-msgstr ""
-
-#: ./doc/user-guide/bk-user-guide.xml:104(date)
-msgid "2013-08-19"
-msgstr ""
-
-#: ./doc/user-guide/bk-user-guide.xml:108(para)
-msgid "Editorial changes."
-msgstr ""
-
-#: ./doc/user-guide/bk-user-guide.xml:114(date)
-msgid "2013-07-29"
-msgstr ""
-
-#: ./doc/user-guide/bk-user-guide.xml:118(para)
-msgid "First edition of this document."
-msgstr ""
-
-#: ./doc/user-guide/ch_dashboard.xml:10(title)
-msgid "OpenStack dashboard"
-msgstr ""
-
-#: ./doc/user-guide/ch_dashboard.xml:12(para)
-msgid "As a cloud end user, you can use the OpenStack dashboard to provision your own resources within the limits set by administrators. You can modify the examples provided in this section to create other types and sizes of server instances."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:12(para)
-msgid "When you launch a virtual machine, you can inject a <emphasis role=\"italic\">key pair</emphasis>, which provides SSH access to your instance. For this to work, the image must contain the <literal>cloud-init</literal> package."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:16(para)
-msgid "You create at least one key pair for each project. You can use the key pair for multiple instances that belong to that project. If you generate a key pair with an external tool, you can import it into OpenStack."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:19(para)
-msgid "If an image uses a static root password or a static key setneither is recommendedyou must not provide a key pair when you launch the instance."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:20(para)
-msgid "A <emphasis role=\"italic\">security group</emphasis> is a named collection of network access rules that you use to limit the types of traffic that have access to instances. When you launch an instance, you can assign one or more security groups to it. If you do not create security groups, new instances are automatically assigned to the default security group, unless you explicitly specify a different security group."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:27(para)
-msgid "The associated <emphasis role=\"italic\">rules</emphasis> in each security group control the traffic to instances in the group. Any incoming traffic that is not matched by a rule is denied access by default. You can add rules to or remove rules from a security group, and you can modify rules for the default and any other security group."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:33(para)
-msgid "You can modify the rules in a security group to allow access to instances through different ports and protocols. For example, you can modify rules to allow access to instances through SSH, to ping instances, or to allow UDP traffic; for example, for a DNS server running on an instance. You specify the following parameters for rules:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:41(para)
-msgid "<emphasis role=\"bold\">Source of traffic</emphasis>. Enable traffic to instances from either IP addresses inside the cloud from other group members or from all IP addresses."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:47(para)
-msgid "<emphasis role=\"bold\">Protocol</emphasis>. Choose TCP for SSH, ICMP for pings, or UDP."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:51(para)
-msgid "<emphasis role=\"bold\">Destination port on virtual machine</emphasis>. Define a port range. To open a single port only, enter the same value twice. ICMP does not support ports; instead, you enter values to define the codes and types of ICMP traffic to be allowed."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:58(para)
-msgid "Rules are automatically enforced as soon as you create or modify them."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:61(para)
-msgid "Instances that use the default security group cannot, by default, be accessed from any IP address outside of the cloud. If you want those IP addresses to access the instances, you must modify the rules for the default security group."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:65(para)
-msgid "You can also assign a floating IP address to a running instance to make it accessible from outside the cloud. See <xref linkend=\"manage_ip_addresses\"/>."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:72(para)
-msgid "You can generate a key pair or upload an existing public key."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:75(para)
-msgid "To generate a key pair, run the following command:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:76(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:98(replaceable)
-msgid "KEY_NAME"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:76(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:87(replaceable)
-msgid "MY_KEY"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:77(para)
-msgid "The command generates a key pair with the name that you specify fir <replaceable>KEY_NAME</replaceable>, writes the private key to the <filename>.pem</filename> file that you specify, and registers the public key at the Nova database."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:84(para)
-msgid "To set the permissions of the <filename>.pem</filename> file so that only you can read and write to it, run the following command:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:95(para)
-msgid "If you have already generated a key pair and the public key is located at <filename>~/.ssh/id_rsa.pub</filename>, run the following command to upload the public key:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:99(para)
-msgid "The command registers the public key at the Nova database and names the key pair the name that you specify for <literal><replaceable>KEY_NAME</replaceable></literal>."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:104(para)
-msgid "To ensure that the key pair has been successfully imported, list key pairs as follows:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:114(para)
-msgid "To list the security groups for the current project, including descriptions, enter the following command:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:119(para)
-msgid "To create a security group with a specified name and description, enter the following command:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:122(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:127(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:147(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:157(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:164(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:177(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:184(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:202(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:214(replaceable)
-msgid "SECURITY_GROUP_NAME"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:122(replaceable)
-msgid "GROUP_DESCRIPTION"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:125(para)
-msgid "To delete a specified group, enter the following command:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:129(para)
-msgid "You cannot delete the default security group for a project. Also, you cannot delete a security group that is assigned to a running instance."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:140(para)
-msgid "Modify security group rules with the <placeholder-1/> commands. Before you begin, source the OpenStack RC file. For details, see <xref linkend=\"cli_openrc\"/>."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:145(para)
-msgid "To list the rules for a security group, run the following command:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:150(para)
-msgid "To allow SSH access to the instances, choose one of the following options:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:154(para)
-msgid "Allow access from all IP addresses, specified as IP subnet <filename>0.0.0.0/0</filename> in CIDR notation:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:160(para)
-msgid "Allow access only from IP addresses from other security groups (source groups) to access the specified port:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:164(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:184(replaceable) ./doc/user-guide/section_cli_nova_configure_instances.xml:202(replaceable)
-msgid "SOURCE_GROUP_NAME"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:169(para)
-msgid "To allow pinging of the instances, choose one of the following options:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:173(para)
-msgid "Allow pinging from all IP addresses, specified as IP subnet <filename>0.0.0.0/0</filename> in CIDR notation:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:177(para)
-msgid "This allows access to all codes and all types of ICMP traffic."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:181(para)
-msgid "Allow only members of other security groups (source groups) to ping instances:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:189(para)
-msgid "To allow access through a UDP port, such as allowing access to a DNS server that runs on a VM, choose one of the following options:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:194(para)
-msgid "Allow UDP access from IP addresses, specified as IP subnet <filename>0.0.0.0/0</filename> in CIDR notation:<placeholder-1/>"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:199(para)
-msgid "Allow only IP addresses from other security groups (source groups) to access the specified port:"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:208(title)
-msgid "Delete a security group"
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:209(para)
-msgid "To delete a security group rule, specify the same arguments that you used to create the rule."
-msgstr ""
-
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:212(para)
-msgid "For example, to delete the security group rule that permits SSH access from all IP addresses, run the following command."
-msgstr ""
-
 #. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
-#: ./doc/user-guide/section_cli_nova_configure_instances.xml:0(None)
+#: ./doc/user-guide/section_sdk_configure_instances.xml:0(None)
 msgid "translator-credits"
 msgstr ""